The BMS observes and explains. Every control write is confirmed by a person, carries an actor and a reason, and lands in an audit trail. PLC logic, safety relays and interlocks remain authoritative.
What it is
bms.indagate.ai is the building and plant monitoring product: a multi-organization, multi-site view of equipment and points, with alert rules an engineer would write, monitors that watch trends over time, and Argo, an assistant that answers from the site's own data. It runs on the same identity and control-plane boundaries as the rest of Indagate.
| Surface | What you get | Boundary |
|---|---|---|
| Portfolio dashboard | Cost, energy, emissions and attention across every site, a portfolio trend and a map | Figures are labelled by source; emission factors follow the site's country |
| Sites and equipment | Organization → site → equipment group → equipment → point, with live values and history | Reads only; control points require confirmation |
| Alert rules | Threshold, band, status and change rules scoped to a point, a component or a class of equipment | Each rule states the standard or design value behind its threshold |
| Monitors | Windowed evaluations: value, change, rate, forecast, anomaly, staleness; composites and roll-ups | Deadbands and M-of-N so a monitor on its limit does not chatter |
| Argo | Computed answers from the site's own data first; standards and general practice from the knowledge base | Decision support; human review remains authoritative |
| Reference packs | Fourteen synthetic organizations, one per industry, to evaluate the product in your sector | Synthetic; no claim of conformance |
Architecture
The web app is a React single-page application served from a private S3 origin behind CloudFront. It talks to an AppSync GraphQL API authenticated with Cognito JSON Web Tokens. Device telemetry arrives from BACnet gateways over MQTT into AWS IoT Core; an ingestion function writes readings to DynamoDB and an S3 archive and publishes them to AppSync subscriptions so open pages update live. Historians and other systems reach the same pipeline through a signed HTTP webhook.
- Sign in. Cognito identities and roles: super user, admin, manager, technician. Feature entitlements decide which surfaces an organization sees.
- Choose an organization. Real organizations sit beside the synthetic reference packs, which can be hidden per user.
- Work the estate. Dashboard for the portfolio, a site for its equipment, a point for its history, alerts for what needs attention, Argo for why.
Where to go next
- Data model — organizations, sites, equipment, points and how ids work.
- Alert rules and monitors — the evaluation vocabulary and what makes an alert trustworthy.
- Reference packs — the fourteen industries, the standards they cite, and how to load or bind one.
- Integrations — BACnet gateways, historians, and the webhook contract.
- Simulation and digital twin — sim.indagate.ai.