Building operator
You inherit documentation you did not write. You go through the same transition as the integrator from the other side. Then, throughout operation, your performance is checked. Verification based on measured data can also become your productivity tool.
Facility managers, technical service providers, maintenance contractors, maintenance managers: you take over the building at the end of the works and you have to prove performance on a contract that will go back out to tender.
The building described once, exhaustively, in a model that every phase of its life reads.
Situations
Every job starts with an investigation. A building model and regenerable documentation say what the installation contains. An assistant connected to the station walks through it, describes it and draws up its inventory and what is missing. It answers your questions in natural language.
See our solutionsYour teams cannot watch thousands of points. Rules that run continuously name the fault: equipment, symptom, probable cause and start date. Network testers tell you whether a device is responding before someone discovers that it is not.
See our solutionsReach stations behind a firewall with no inbound port open and work on them remotely. Send each person only the alarms that concern them (site, severity, on-call duty) and pass them on to your CMMS.
See our solutionsBenefits
Maintenance starts from the installation as it is.
Learn moreA fault named before the complaint and a diagnosis possible without a site visit.
The right alarm reaches the right person in the tool they already work in.
Measured data to document your performance.
In practice
Your teams cannot watch thousands of points, so a fault often comes to light through a complaint. Rules that run continuously name it and give the equipment, the symptom, the probable cause and the start date.
Example
Twelve weeks of operation. A fault appears in week one.
6 weeksbefore the fault is known
The fault lasts until an occupant complains. In the meantime the installation uses energy and wears without anyone knowing.
Service
Between two transitions, three things must run without stopping. The transitions build the model. These three services use it.
A building accepted as compliant does not stay that way. Points drift, sequences are bypassed and a schedule overridden “temporarily” is never restored. The expected sequence is continuously compared with observed behaviour so that any deviation is flagged as it appears.
No one watches thousands of points. A failure often comes to light through a complaint weeks after it started. Rules run continuously on the data and name the fault: which equipment, which symptom, which probable cause and since when.
No one can say which setting will get you to your regulatory targets or prove the claimed gain afterwards. Setpoints, schedules and sequences are adjusted to actual behaviour and occupancy with the before/after difference measured.
Tell us which one and what you were left with. The demo will start from there.
