Nobody should have to draw a building twice.
The graphics are the part of a head-end operators actually touch, and they are the part a dealer hand-drew during commissioning. Which is why changing one is a call, a quote and a visit — for a picture of a building you own.
Drawn per type, not per site
An air handler view is defined once for the type. Every air handler in the estate renders through it, populated from its own points. Change the type and every instance changes with it, in every building, without anyone opening a drawing tool.
The fourteenth costs what the first did
Adding equipment adds it to the model, and the view follows. There is no commissioning step where someone places rectangles on a canvas and binds them to point addresses, which is also the step where the drawing and the plant quietly diverge.
A view cannot disagree with the model
Because the view is generated, it cannot show a point that no longer exists or miss one that was added last month. The most common failure of a hand-drawn graphics estate is not that it is ugly — it is that it is out of date and nobody knows which parts.
Specifics
- Defined
- Per equipment type, in the asset model
- Rendered
- Per instance, from that instance’s own points
- Changed by
- Your team, without a dealer visit
Common questions
What happens to the graphics our dealer drew?
They are reference during the survey, not something you have to carry. What they encode about your plant goes into the asset model, where it can be maintained by whoever owns the building.
Can we still get a custom view for an unusual plant room?
Yes. A one-off view is defined the same way a type is; it simply has one instance. The difference from a head-end is that this is the exception rather than how every screen gets made.
Bring your point list.
The first conversation is a survey: what you run today, and what it would look like modelled.