Build the view you actually watch
A dashboard is assembled from the events and readings the site already produces, per site, per area or per account. Pin what matters on that floor and leave the rest off it.
Dashboards a site builds for itself, and reports that arrive on a schedule
A control room does not watch the same six numbers as the account manager, and neither of them wants to log in on a Monday to find out how the weekend went.
Reports go out on a schedule
Event volume, what was suppressed and why, response and close times against the clock, and what each operator and each shift handled. Set it once and it arrives.
Scoped to what the reader may see
A customer facing view carries that account's own cabinets, doors and events and nothing else. The same rules that scope the console scope the dashboard and the report.
Power and energy reporting is built from what your sources give us. Where a meter reports per branch circuit we can report per branch circuit; where it reports per board we report per board, and the report says which it was.
Advanced automated analytics
Every event that arrives is counted, classified and measured against the clock running on it. The reporting then shows what the automation resolved on its own, what still needed a person, and what went past its acknowledgement time, for any period you choose.
Events received
14,200
Panels, BMS, cameras, power, cooling, compute
Handled automatically
13,658
Suppressed, de-duplicated, or worked and closed by automation
Needed a person
480
Queued with a procedure and a clock already running
Escalated
62
Acknowledgement timer breached, passed up the tree
This is an example of the reporting view. The figures come from a single 30 day period in a test estate and are there to show what the screen does, so please read them as an illustration rather than as a prediction of what your own site would see.
What runs without an operator
Automate event handling with automation tools, including DAIOS, our automatic engagement AI solution. Events that do not need a person are handled without one, and the ones that do reach an operator with the work already done.
DAIOS automatic engagement
When an event fires, DAIOS engages the right contacts by voice, SMS, chatbot or email, captures their response, and posts the outcome back to the platform. No operator is involved unless one is needed.
Rules and routing
Rules decide which events are handled automatically and which go to the queue, by event type, site, area and time of day. Low value signals are absorbed before anyone sees them.
Automatic closure
Events that restore within a set window, or that are answered and resolved by a contact, close themselves with the reason and the full exchange written to the record.
Scheduled actions
Test modes, maintenance windows and planned suppressions run to a schedule and expire on their own, so nothing stays muted after the work is finished.
Escalation without an operator
Automated engagement follows the same ordered contact list an operator would use, advancing when a contact does not answer and recording every attempt.
Handover to the queue
Anything automation cannot resolve arrives in the operator queue with the engagement history attached, so the operator starts from what has already been tried.