TwinEdge OS
- BACnet/IP, Modbus, OPC UA, MQTT
- ONVIF / RTSP cameras, local clips
- Durable log if the WAN drops
TwinEdge Facility OS
See why the room is hot. Send the work. Keep the proof.
TwinEdge OS at the building — including cameras. Historian and cloud for live asset intelligence.
TwinEdge OS sits at the building and reads AHUs, chillers, and meters over BACnet, Modbus, or OPC UA — and ONVIF or RTSP cameras on the same box. Local history and clips keep running if the WAN drops. Facility OS uses that record in the historian and the cloud. A person still approves.
- Speak the building’s protocol. BACnet/IP, Modbus, OPC UA, MQTT — and ONVIF/RTSP cameras on the same box.
- History if the WAN drops. A durable log and local camera clips. Then the historian and cloud catch up.
- The right job. Draft work from a finding. A person still approves.
How live building data reaches TwinEdgeEDGE OS · HISTORIAN · CLOUD
TwinEdge OS sits beside the BMS. It reads named AHUs, chillers, and meters, and ONVIF or RTSP cameras on the same box. Local history and clips stay if the WAN drops, then forward to the historian and the cloud.
Facility OS
- Historian and cloud see the same asset
- Building Twin finds a fault
- Workplace and Energy share the building
Approve the next move
A setpoint change or work draft waits in a queue. Safety envelopes and kill switches stay on.
A person still approves.TwinEdge does not change a setpoint unless you let it. Life-safety points are status only.
THENTwinEdge HistorianCamera evidence on the buildingCMMS work order
START WITHBMS · meters · equipment
TWINEDGE CONNECTSA building that shares its context
MOVE FORWARD WITHComfort + maintenance + energy
THE WORKFLOW
From a BACnet point to a finished job.
Read the equipment
TwinEdge OS speaks BACnet/IP, Modbus, OPC UA, MQTT, and ONVIF/RTSP cameras to named facility assets.
Keep the record
A durable log, local history, and camera clips stay on the box. Then the historian and cloud get the same asset.
Send the work
A person approves. The job and the proof come back to the same building.
Comfort and the machine together
See the room and the AHU on one record.
The right job
Draft work from a finding, not a clipboard.
Proof you can show
Energy, inspection, and closeout stay on the building.
FROM THE PRODUCT
See the work in context.
Select a screen to explore the workflow. Open it for a closer look.
01 / INSIDE TWINEDGE
The equipment on the map
Put the AHU, chiller, and the room it serves on the same map as alarms and work.
BUILT FOR THE OPERATION
What this layer covers.
TwinEdge OS at the building
Native C workers for BACnet/IP, Modbus, OPC UA, MQTT, Sparkplug, and SNMP.
Building Twin, Workplace, Energy
Fault findings, rooms, IEQ, inspections, meters, bills, and ENERGY STAR on the same building record.
Approved work
A person still approves.
GO DEEPER
Details for your operating context.
A hot room is a machine problem, a people problem, and a money problem.
The BMS knows the point. The CMMS knows the job. The bill knows the cost. Facility OS keeps those on one building so the operator, the crew, and finance stop arguing from different screens.
- Building operators. See the floor, the AHU, the comfort finding, and the open job without jumping between BMS, spreadsheets, and tickets.
- Maintenance crews. Take a work order that already names the asset, the room, and why it matters — then bring photos back.
- Energy and compliance. Meters, bills, inspections, and ENERGY STAR sit on the same building you just repaired.
A building layer. not a second BMS.
TwinEdge OS is the edge server. Facility OS is the operating layer that uses its record. Building Twin, Workplace, and Energy are gated modules. It is not a plant OS and it is not a BMS replacement.
- TwinEdge OS owns protocol I/O. Native workers ingest BACnet/IP, Modbus, OPC UA, MQTT, Sparkplug B, and SNMP. Site Vision ingests ONVIF/RTSP cameras and local VMS events. Facility-edge owns the local autonomy loop. It does not reimplement ingest.
- Named facility assets. The OS library types AHUs, VAVs, chillers, cooling towers, boilers, domestic water, emergency power, cold chain, and resident rooms — with units, KPIs, and default alarms. Cameras map to site, zone, privacy mask, and retention. Fire and suppression points are read-only.
- Findings wait for a person. Fault detection drafts a finding. Proposed setpoint changes wait in a queue. BACnet writes go through a commissioning path with readback, not the ingest loop. Kill switches stay on.
One building record across TwinEdge
The value is linking the BMS, the room, the job, and the bill — then carrying the evidence through repair and reporting.
- TwinEdge OS
- BACnet/IP
- Modbus TCP/RTU
- OPC UA
- MQTT
- Sparkplug B
- SNMP
- ONVIF cameras
- RTSP
- Local VMS / NVR
- Local camera evidence
- AHUs and VAVs
- Chillers and boilers
- Durable log
- Local history
- TwinEdge Historian
- Store-and-forward cloud
- Fault detection
- Proposed actions
- Safety envelopes
- IEQ
- Inspections
- CMMS work orders
- ENERGY STAR
CONNECTED BY DESIGN
Fits the systems around it.
Keep source context available as the workflow moves between teams and applications.
One connected record.
TwinEdge Facility OS
- TwinEdge OS native workers read the BMS over BACnet/IP, Modbus, OPC UA, MQTT, Sparkplug B, or SNMP.
- The same edge box takes ONVIF Profile S cameras, direct RTSP, or a local VMS/NVR.
- Readings and camera evidence go into a durable log first.
- When the link is up, the box forwards to TwinEdge Historian and to the cloud so Facility OS sees live asset intelligence.
- Building Twin, Workplace, and Energy share that named building record.
- A person approves.
- Life-safety points are status only.
BEFORE YOU START
A few useful answers.
Is Facility OS a BMS?
No. TwinEdge OS reads your BMS over BACnet/IP, Modbus, OPC UA, or MQTT, and cameras over ONVIF or RTSP. Those systems stay. Facility OS is the TwinEdge building layer that uses the record.
How does TwinEdge OS connect to building equipment?
Native workers on the edge server ingest BACnet/IP (Who-Is, COV, BBMD), Modbus TCP/RTU, OPC UA, MQTT, Sparkplug B, and SNMP. Facility library types name the AHU, chiller, VAV, boiler, meter, and generator. A saved point map is required. Commissioning still validates the live panel.
How do cameras connect at the edge?
Site Vision on TwinEdge OS takes local ONVIF Profile S cameras, direct RTSP streams, or a local VMS/NVR. Discovery, live view, clips, and privacy masks run on the box. Credentials are secret references, not pasted passwords or stream URLs. Cloud doorbell cameras such as Ring are lab-only and are not a production path.
What happens if the internet is down?
Readings still hit a durable log on the box. Camera clips stay in local evidence storage. Local analytics and alerts keep running. When the link returns, store-and-forward sends the backlog to TwinEdge Historian and the cloud.
Does TwinEdge change setpoints on its own?
Not unless a person lets it. Proposed actions wait in an approval queue. BACnet writes go through a commissioning path with readback, not the ingest loop. Safety envelopes and kill switches stay on. Fire and suppression points are never writable.
Does it replace our CMMS?
No. Facility OS uses TwinEdge AssetOps for work orders, or sits beside the CMMS you already run. The finding and the job share the building record.
THE NEXT CONNECTION
Explore the product familyBuild the rest of your loop.
START WITH YOUR OPERATION
Put the next decision in motion.
Discuss your sources, assets, and the outcomes your team wants to improve.