From alert to fixed.
A full alert lifecycle across building systems and locations: prioritized, investigated, ticketed and verified, with nothing lost between systems. Watch one alert live its life below.
Detection is the beginning, not the job.
Above every operation sits a queue of decisions: 20 active alerts — all of them critical — beside 7 open maintenance tickets, 2 already overdue. Alerts & Maintenance is the TwinMS workflow layer that connects what the building detects to the work that fixes it. The demo below replays one alert’s lifecycle.
What detection becomes.
Alerts & Maintenance is the workflow layer of TwinMS, not an alert list, and not a generic ticket dashboard, but the connection between operational evidence and accountable maintenance work. Seven capabilities, one unbroken chain.
The workload at a glance
Four numbers put the operation’s day in order: 20 active alerts — all 20 critical — beside 7 open maintenance tickets, 2 of them overdue. What needs attention and what is already being worked, on one screen.
One alert, with context
Every alert opens into its anatomy: an ID, a plain-language description, the exact location, the linked asset, the related camera feed, and the metric that triggered it. A notification says something happened; an alert here says what, where, and on what evidence.
Evidence before action
The reading that raised the alarm stays attached to it: water flow measured at 3.33 L/min against a 2.5 L/min threshold, with the possible cause stated in plain language. Operators act on measured conditions, not on red icons.
The working queue
Maintenance Tickets turns work into an accountable board: every ticket carries its ID, priority, system, exact location and due date, and one of four honest states: Open, In-Progress, Overdue, Closed. Nothing hides in a backlog.
From alert to ticket
Create Ticket starts with a choice, and the first option is the one that matters: select an active alert, and the interface populates the ticket’s details from it. Detection becomes organized work in one step, with a manual form for everything else.
A ticket has a life
Open a ticket and its history is intact: the description, the work notes as the team writes them — “Certified elevator technician dispatched.”, and a status timeline stamping every stage. Not a disposable task: a documented repair.
Traceable to the origin
The link runs both ways. Alerts carry their maintenance ticket; tickets carry Created From Alert with the originating alert’s ID — beside the asset they serve. Months later, the question “why did we do this work?” still has an answer.
See it working.
A guided film of the real module: from a wall of twenty critical alerts to one expanded ticket carrying its work notes, its status history, and the ID of the alert that started it.
See your operation, alive.
A live demonstration on a real building: your systems, your scale, your questions.