IoT / Energy · Agent Nova · The product we sell

AI agents that keep your facility running using IoT.

Nova reads energy, water, chillers, gensets, and treatment plants from live client dashboards, then opens a ticket your team assigns and verifies. The rest of MatriqGo — helpdesk, assets, attendance — sits on that same loop.

Book an IoT demo How the energy module works

01

Connect the plant

Meters, pumps, chillers, gensets, STP, and solar land next to the asset Atlas already holds.
02

Nova watches

Anomaly detection on load, levels, run-hours, and changeover — continuously, not at month-end.
03

A ticket opens

Orbit assigns the job with the reading attached. Someone owns the spike.
04

Verify the close

Photo evidence plus the same signal. Waste you can show as closed work.

On the phone

The same readings your engineer carries.

Energy dashboards from live client deployments, on the app the plant team already has.

Total energy delivered by tower, WTP, and club — Energy delivered across towers, WTP, and club.

Energy delivered gauges by campus zone — Zone gauges Nova reads in the industrial module.

Energy monitoring — last 24 hours power factor and active power — Power factor and active power on the same energy dashboard.

Where Nova reads

Plant rooms, metered and monitored.

These are the signals the energy module already understands, on dashboards built for the people who answer for them.

Energy & i-EMS

A spike becomes a ticket, with an owner.

Plant-wide load and consumption on the energy dashboard.

Campus and plant electrical systems as live work. Nova highlights the interval, Atlas already has the feeder, Orbit assigns it — so a demand spike is closed against the same meter that raised it.

Energy is where Nova starts. Load, power factor, and consumption sit on the same dashboard your engineer carries, and every exception can open a job.
- Feeder and transformer load with demand windows
- Exception detection on unexplained spikes or idle waste
- Role-scoped views for plant, FM, and leadership
Water level & pumps

Tanks, levels, and pump run-hours without the night walk.

Tank levels and pump state, with alarms that open a ticket.

Level sensors and pump telemetry tell Nova when to run, when to wait, and when a dry-run or overflow is forming — then Atlas gets the pump asset if the hours say a service is due.

Water is a control loop with consequences. The dashboard shows levels; the ticket is what happens when they are wrong.
- Tank and sump levels with hysteresis the operator can see
- Pump starts, run-hours, and trip context
- Dry-run and overflow predictions before the basement call
Chiller automation

Plant-room setpoints with an operator still in charge.

Chiller loops with an operator override, not a locked PLC screen.

Chillers, related pumps, and temperatures are automated with override — so comfort and efficiency do not depend on whoever has the night key.

Chiller automation is useful only if someone can still take the wheel. Nova runs the loop; RBAC decides who may change it; Orbit records the work when the machine disagrees with the plan.
- Supply/return and approach temperature trends
- Staging and setpoint automation with explicit override
- Anomaly cues that open work against the chiller asset
STP automation

Treatment that logs itself.

STP process stages and run-state in one view.

Sewage treatment plants get run-state, levels, and fault cues in the same tenant as the rest of the facility — so a blower trip is a ticket, with the process stage attached.

STP work is often invisible until it is not. Nova keeps the plant on the same board as the people who have to answer for it.
- Process stages and equipment run-state
- Level, blower, and pump exceptions
- Operator notes attached to the plant asset
WTP automation

Incoming water with the same discipline as the rest of the plant.

Treatment plant readings next to the team who answer for them.

Water treatment gets automation and anomaly detection alongside storage and pumping, so quality and availability are operational facts.

WTP is a sibling of STP and pumping, not a one-off SCADA island. Nova treats it as another industrial circuit inside the platform.
- Treatment stages and critical equipment state
- Throughput and trip patterns
- Predictions that feed Atlas service windows

Also in the field

Same agent. Same loop.

Campus services, hybrid power, gensets, and compressors — Nova turns each anomaly into work, with a digital twin sitting over the assets and signals you already have.

Smart campus

How the same IoT / Energy module behaves on a society or mixed campus — plant rooms and towers in one system, not a second product.

Smart campus is how the same industrial module behaves when the site is a society or mixed campus rather than a single factory floor.
DG / solar hybrid

A secondary pattern for sites that blend grid, diesel, and solar — so changeover and contribution stay visible to the roles that pay the bill.

Hybrid power is an accounting and operations problem. Nova records the mix; energy views stay inside the same i-EMS chapter.
Genset

Treat diesel gensets as assets with telemetry — the same anomaly → ticket loop, not a forgotten backyard machine.

Gensets already have nameplates and AMCs. Nova just stops them from being invisible between tests.
Compressor telematics

A secondary pattern for industrial air: run-hours, trips, and load cycles that should have been work orders last quarter.

Compressor telematics is plant hygiene. The point is not another chart — it is a service interval that updates itself.
Digital twin

A view over assets and signals you already have. Not a separate product, and not something we sell in the module grid.

A twin is useful when it is thinner than a simulation project. MatriqGo treats it as platform depth over Atlas and Nova — not a module you buy on its own.