One model, and every system points at it.
A head-end gives you a tag database and a set of graphics drawn by whoever installed it. Ask it what equipment serves the third floor and you are reading pictures. Ask Indagate and you are reading the model.
Assets, not addresses
An air handler is modelled as an air handler: its type, its points, the zones it serves and the plant it draws from. Its BACnet instance number is an attribute of that model, not the identity of the thing. Every trend, alarm, report and agent addresses the asset, so renaming a point does not orphan four years of history.
Your existing addressing stays valid
The namespace maps onto the BACnet, Modbus and OPC UA addressing you already have. Nothing is renumbered, no controller is reflashed to adopt it, and the mapping is inspectable — you can see which object a modelled point resolves to, and change it without a dealer visit.
New equipment inherits its type
Add a fourteenth VAV box and it arrives with its type’s points, ranges, alarm conditions and graphics already defined. The cost of the fourteenth is not the cost of the first, which is the opposite of how a hand-drawn graphics page behaves.
Specifics
- Modelled entities
- Sites, buildings, floors, zones, equipment, points, meters, cameras, work orders
- Protocol mapping
- BACnet/IP and MS/TP, Modbus TCP and RTU, and OPC UA, mapped to modelled points
- Graphics
- Generated from the model per equipment type, not drawn per site
Common questions
Do we have to re-tag everything to adopt the namespace?
No. The model maps onto your existing point addressing during the survey. Re-tagging is something you can do later for clarity, not something the platform requires to work.
What happens to our existing naming conventions?
They are carried into the model as attributes, so a point your team knows by its site name stays findable by that name while also resolving through the asset model.
Bring your point list.
The first conversation is a survey: what you run today, and what it would look like modelled.