This guide answers one question: what is TwinMS, and how does the platform work as a whole? It is the starting point for every operator. You will not learn any single module deeply here — each has its own guide. You will learn the ideas every module shares, so that every screen you open afterwards already looks familiar.
The platform at a glance
TwinMS is an operational intelligence platform built around a live digital twin of your building. Around the twin sits a set of screens — the modules — each answering one operational question: watching the whole operation, exploring the building in three dimensions, tracking assets and sensors, handling alerts and maintenance, analyzing performance, and monitoring cameras. Underneath them all runs the same flow: the building is measured, the measurements reach the model, the platform reads them against memory, and people act. Because every module reads from the same model, information that is usually scattered across separate systems appears in one place, in context — and decisions that once required assembling reports can be made from a single screen. The film below is a short overview of the platform.
The digital twin
TwinMS is built around a digital twin — a live, navigable replica of your real building, created from laser scans and the same certified engineering model the building was constructed from. The twin is not an illustration. Every floor, room and major asset exists in it, and live readings from the building attach to the places they come from. When something changes in the building, the twin shows it; where control is enabled, operators with the right permissions can act on selected building systems from the twin. Every screen in TwinMS is a different way of reading this one model.
From sensor to screen
Sensors throughout the building measure what matters — energy, water, air, temperature, occupancy, the state of machines. Their readings flow into TwinMS continuously and attach to the exact floor, space and asset they describe. That is why every number you see is an address as well as a value: the platform always knows where a reading came from. Screens update automatically as new readings arrive, so what you see reflects the current state of the building. When a reading stops arriving, the platform notices that too.
Baselines
For every metric it tracks, TwinMS keeps a learned baseline built from up to two years of history — what normal looks like for this building, this floor, this hour. Live numbers are always read against that history, which is how the platform distinguishes expected variation, such as a busy day or a seasonal rise, from a genuine deviation. When you see a value flagged as high or low, the comparison behind it is the baseline, not an arbitrary threshold.
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.
Health scores
TwinMS expresses condition in one language: a health score from 0 to 100. Sensors have them. Assets have them. Fleets of both roll up into averages you can read at a glance. A falling score indicates equipment that needs attention before it fails — and because every score belongs to a named item in a known location, you can move from the score to the item itself in one click.
Roles and permissions
Access in TwinMS is governed by roles: what you see and what you may act on depends on your role. Viewing is broad; acting is deliberate — controls that change the physical building are limited to the people responsible for them, and control actions are recorded. If a control does not appear on your screen, it is outside your current role.
Shared controls
TwinMS screens repeat the same small vocabulary, so learning one screen teaches you all of them. A scope selector narrows everything to a building, floor or space. Tabs switch views inside a module. A live indicator confirms the data on screen is current. Date controls move from the present into history, and where a screen offers Export, it saves the current view as a file you can share. Not every screen uses every control, but wherever one appears, it means the same thing and behaves the same way.
Where to go next
From here, go where your work is. Watch the module films to see each screen in motion, then read the guide for the module you will use most — start with the 3D Viewer guide if you navigate the building, or the Operations Hub guide if you watch it. Each module guide builds on this one, and each ends with its own next step.