There is no asset
“AHU-2” on the trend, the alarm and the work order are three strings, not one thing.
For critical facilities
Know what changed, who changed it, and why — before anyone asks.
Today those decisions live in four systems nobody can trace. Indagate puts them on one record. Ask it why and get an answer, not a tag list; let agents act on it safely, inside limits you set.
Indagate is the supervisory layer for critical infrastructure — data centers, commercial real estate, power, manufacturing and oil & gas. Every asset modelled once; every setpoint, override and work order on one record with its reason; and agents that act only inside the reach you granted them. Your controllers keep running their sequences. Nothing gets ripped out.
The problem, measured
Uptime Institute, 2025
NERC State of Reliability, 2025
NERC EMS Assessment · 49 of 147
Uptime Institute, 2022–2026
Platform
Four things the layer you run today was never able to hold.
Points, meters and work orders modelled once. The same name resolves in a trend, an alarm and an agent’s reach.
AHU-2 resolves in trend · alarm · work order · agent reach
Every action, override and schedule change against the asset, with who made it and the reason they gave.
What your best operator knows, in front of every shift — acting within a declared reach and landing on the same record.
Why did line 3 lose twenty minutes this morning?
The filler infeed sensor chattered 31 times in nine minutes from 06:40 — each stop under four seconds, none crossing the downtime threshold. Cumulative loss 19 min. Same sensor replaced in May; WO-1187 says “intermittent”.
stop log 06:40–06:49 · WO-1187 · proposes: raise work order
A language model is not deterministic. The envelope around it is: reach admitted before install, life-safety priorities refused by construction.
Product panels are illustrative; the shapes are the real ones.
Demo
Five sites, one console: the trends, the week's decisions with who made them and why, the findings each one explains, and Argo to ask. The building is computed from published data; the other four are modelled and say so.
■ decisions on the record · shaded: unoccupied
AHU-1 is running its chiller on mild days — is the economizer working?
The outside-air damper never leaves 12%. Outside-air fraction computed from the mixing ratio confirms it: the unit holds minimum outside air through every hour when outside air was cooler than return, so mechanical cooling runs against a free-cooling opportunity.
Recommends · Check the damper actuator and linkage on AHU-1 before anything else — the command signal and the measured mixing ratio agree with each other, which points at the mechanism rather than the controller.
read:Outside Air TemperatureReturn Air TemperatureMixed Air TemperatureOutside Air Damper PositionCooling Valve Position
Telemetry from a deterministic physical model of the reference building, published by the product. Determinations and answers are computed by the same code that runs on a real site; the record entries are illustrative.
Outside-air damper position never moves (12.0–12.0%) while measured outside-air fraction holds at 12%. The unit did not economize during 116 hours when outside air was cooler than return.
Evidence
Basis
Outside-air fraction from the mixing ratio (RAT−MAT)/(RAT−OAT), evaluated only when return and outside air differ by ≥3 K. Free-cooling opportunity per ASHRAE Guideline 36 economizer high-limit logic.
The cooling coil and ZN-202 West Perimeter reheat run together in 18.1% of running samples, costing about 405 kWh of reheat over the window.
Evidence
Basis
Samples where the AHU cooling coil is active while a served VAV box is reheating. Guideline 36 sequences are written to avoid this; where it persists, the energy is paid for twice.
Normalised filter ΔP is 212 Pa (85% of the 250 Pa final resistance) and rising 6.0 Pa/day — about 6 days to change-out at this rate.
Evidence
Basis
Filter ΔP normalised to design airflow (ΔP scales with velocity²), trended by least squares and extrapolated to the manufacturer's final resistance. Change-out at final ΔP is standard practice; ASHRAE 90.1 counts the fan energy the loaded filter costs.
The supply fan ran 211 hours outside the building's occupied schedule — 63% of its total run time — using 431 kWh of fan energy.
Evidence
Basis
Fan running hours falling outside the building's occupied schedule, priced at the fan energy actually metered. Schedule drift is the cheapest fault to fix and the most common one to find.
COP has moved from 3.43 to 3.00 across the window (-12.6%) while condenser approach widened 0.19 K/day — consistent with condenser fouling rather than load variation.
Evidence
Basis
Coefficient of performance (cooling delivered ÷ electrical input) at comparable load, trended across the window, read alongside condenser approach temperature. A widening approach with falling COP is the standard signature of a fouled or airflow-restricted condenser.
Zone temperature sits between 22.4 and 25.4 °C in occupied hours; 18.2% of samples fall outside the 21–24 °C band.
Evidence
Basis
Occupied-hour zone temperature against a 21–24 °C band (ASHRAE 55 typical office, still air, normal clothing).
Why nothing you run today can do this
“AHU-2” on the trend, the alarm and the work order are three strings, not one thing.
The alarm server logs the transition, the historian the value, the CMMS the order. Nothing logs the reason.
They know operators with logins, not agents with declared reach.
Per point, per client, per year funds them. A platform that unifies the four competes with their book.
A supervisory system is a tag database and a set of drawings, per site. Adding an asset model to thirty years of installed base means every dealer going back to say what the tags meant — and the lock-in is the revenue.
Who it’s for
Runs beside what you have
Points are polled and writes issued on a gateway in your building; fleet management and history run in a control plane on AWS, in your region or your VPC. The admission record maps to the EU AI Act, CRA, IEC 62443, NIS2, NIST CSF 2.0 and SP 800-82, OSHA 1910, FDA Part 11 and SOC 2 in the security review packet. Support is not certification; none is implied.
Industries
Different equipment, different regulators, the same four problems.
Common questions
No. Controllers keep executing the sequences they were commissioned with. Indagate replaces the supervisory layer above them — the operator workstation, historian, alarm server and the filing cabinet — and runs in parallel until you stop opening the old one.
It is wrong inside an envelope you declared and can inspect. It cannot reach equipment it was not granted, cannot write a life-safety priority, and every action lands on the record with the grant that allowed it — so being wrong becomes something you find and reverse.
A gateway in your building polls points and issues writes, so supervision does not stop when a network does. Fleet management and long-term history run in a control plane on AWS, in your region or in your VPC.
Send the point list, the controller inventory and the history you need to keep. We map what moves, what stays, and what a parallel run would take — free, by an engineer, before anyone talks about a contract.
We will map what moves, what stays on your controllers, and what a parallel run would take — free, and before anyone talks about a contract.