This guide answers one question: how do you watch the whole operation from the Operations Hub? It assumes you have read the Platform Guide. Here you will learn how to read the KPI wall, how to narrow the hub to one floor or space, and how to follow what the building reports — logs, alerts, occupancy and air.
The hub at a glance
The Operations Hub is the live operational control layer of TwinMS: building conditions, systems, alerts, occupancy and environmental data in one contextual interface. Energy, water, occupancy, parking, HVAC, doors and lighting stream into a single wall of live numbers and lines. Its capabilities are not separate widgets — each hands its context to the next, so the distance from noticing a condition to acting on it is measured in seconds rather than systems. The film below shows the hub on a real operation.
Reading a KPI wall
Screens that summarize an operation open with a KPI wall — a row of live figures condensing the current state into a single reading: consumption, occupancy, open tickets, active alerts, active systems. Read it as one pass over the building's present: what is being used, what is running, what needs attention. Every figure is live, belongs to the scope you have chosen, and is judged against the building's own baseline rather than a fixed threshold. When one figure needs explaining, the panels beneath it carry the detail.
The stream, the map and the air
Beneath the wall, Live System Logs stream every sensor event as it happens — time-stamped, tied to its room, filterable to Critical or Warning. Active Alerts stay on screen beside the stream, each with its location and time, until they are dealt with. The Occupancy Map reads the building room by room and level by level, shaded by load, and room-level air quality readings surface conditions in the exact space they occur. Office Select is the hub's scope selector: narrow it to one floor or one space, and every panel follows.
Alerts and their lifecycle
When the platform detects something wrong — a reading out of range, a pattern that breaks the baseline, a device that has stopped reporting — it raises an alert tied to the exact place and asset involved. Every alert moves through the same three states, visible on screen: Created when it is raised, Acknowledged when someone takes ownership, Resolved when the cause is closed. Alerts can become maintenance tickets, so the work that follows stays connected to the signal that started it. Issues are raised by the platform as they are detected, rather than waiting to be found by manual checks.
Where to go next
From here, follow the work the hub surfaces. An alert that needs hands becomes a ticket in Alerts & Maintenance; a number that needs explaining opens in Performance Insights; a place that needs seeing opens in the 3D Viewer. The 3D Viewer guide shows how to move through what the hub is watching.