From reading the building to running it.
System Control is the operational control layer of the twin: one-tap building modes, device-level commands and IF/THEN automation rules — every action scoped to a building, governed by role, and confirmed by the system that received it. The panel below behaves like the real module.
Monitoring becomes a decision, then an action.
System Control is the TwinMS layer where the twin connects to the operational control layer of the asset: connected building systems, their live states, and the authorized actions that change them. Six capabilities, one closed loop.
One tap, one building mode
Preset Scenarios bundle many device commands into a single operating mode: Morning Warmup pre-warms the floor to 22°C at 07:00 on weekdays; Open for Business brings lights and HVAC to a comfortable 22°C; Good Night locks every door and turns all lights off; Eco Mode reduces power by dimming lights and ventilating. A scenario is previewed before it is applied, and the result is reported device by device. Custom scenarios are built for the way a specific asset runs.
Device-level control
Each device carries its own control surface: an on/off toggle, a level slider where the equipment supports one, its live power draw and the floor it sits on. A fixture reading 85% brightness at 24W is the physical device reporting itself, and the slider that changes it is the command going back. Devices that are disconnected are marked as such, with their last-seen time, so the controller knows which commands cannot land.
System-level action
Devices are grouped the way the building is engineered — lighting, HVAC, security, elevators, energy, network, water — each with its own count, so thousands of devices stay navigable. A system panel shows how many of its devices are active and how many are disconnected, and can be switched on or off as one system rather than one device at a time.
Rules the building runs on
Automation Rules are readable IF/THEN logic rather than hidden scripting: a trigger, the actions it fires, and the record of how it has performed — executions and measured energy saving per rule. Rules are grouped by what triggers them: time, occupancy or environmental conditions. The engine reports on itself too: executions today, success rate, and the rules that need attention.
Every command answers back
Control is two-way or it is guesswork. A command carries an average latency in the low hundreds of milliseconds, and the state shown afterwards is the state the system reported, not the state that was requested. Manual overrides and failed commands are counted and surfaced, so an action that did not take effect is visible immediately instead of being assumed. Scenarios that overlap are flagged before anything runs: a second scenario is held while the first is still being applied, and every device it could not reach is listed.
Authority, not just access
A page that issues real commands to physical systems is governed by role: Admin, Operator, Technician, Viewer and Tenant see and do different things, and control actions stay with the roles entitled to them. Scope is explicit — Office Select keeps every command bound to the building and area in view — and a kiosk lock guards a screen left open on an operations floor against unintended input.
Three layers, one asset.
System Control does not replace the modules that read the building; it acts on what they establish. Each layer hands its context to the next.
3D Viewer — understand the asset
The navigable twin establishes where everything is: the fixture, the unit, the room, the floor. Control is meaningless without that spatial truth — a command belongs to a place, not to a row in a list. Explore 3D Viewer →
Operations Hub — understand what is happening
The live control room reads the whole operation: consumption, alerts, occupancy, active systems, room-level conditions. It establishes the condition that justifies an action, and localizes it to the exact space. Explore Operations Hub →
System Control — act on it
The condition becomes a command: a mode applied across the building, a system switched, a device set to a level, or a rule that will handle the same condition next time without anyone watching. The result is reported back into the twin.
See it working.
A guided film of the control layer on a real estate of connected systems: 411 devices in one panel, a whole-building scenario previewed and applied, a conflicting scenario held back, an automation rule built in three steps, and device-level control across seven systems.
See the twin act.
A live demonstration on a real building: your systems, your roles, your control workflows.