Problem
What this replaces on site
BMS screens and IoT portals show a live picture and stop there. The person who can fix the feeder or the chiller is in a WhatsApp group, and the close is never verified against the signal that started it.
Who uses it
The people on this module
-
Plant operators
Watch feeders, water, chillers, and treatment plant in the same tenant as the work.
-
Facility managers
Receive exceptions as tickets they can assign, not as screenshots in a chat.
-
Technicians
Get an assigned job on the asset Nova flagged, with the reading attached.
-
Energy / estate leads
Verify that the waste or the alarm actually closed.
How to use
Three steps to start
-
Step 01
Nova reads the signal
Energy, water, chillers, STP, WTP — the series lands next to the asset Atlas already holds.
-
Step 02
An anomaly opens a ticket
Orbit gets a job with an asset and a suggested assignee. Someone owns it.
-
Step 03
Act, then verify
The technician closes with evidence. The signal and the ticket meet again so you know the waste stopped.
Built as an IoT operating system, not a chart pack
Anomaly → ticket → assign → verify. The dashboard is how you see it. The ticket is how you close it.
IoT is the product MatriqGo leads with. Nova interprets the series. Atlas already has the asset. Orbit opens the job. Energy, water, chillers, hybrid power, gensets, and treatment plants all run this loop — and the longer catalogue lives on the IoT / Energy hub.
