Technology and method
Connect the evidence. Keep control on site.
Start with the systems you already operate. Robometic brings BMS and DCIM records, maintenance history and targeted condition observations into a structured engineering review. Every assumption, gap and model limitation remains visible.
Five layers, in order.
The order matters. Each layer is agreed before the next one is added.
Existing data
BMS trends, DCIM records, maintenance history, operating logs and the site's own procedures.
Defined gap
A specific question the existing evidence cannot answer, agreed with the site before any measurement is added.
Targeted observation
Selective temporary or permanent measurement where it adds decision value, using the site's access and safety rules.
Dependency model
Which equipment supports which load, where paths and controls are shared, and which constraints apply.
Engineering review
Assumptions, limits and next checks set out in writing for the authorised site team.
Existing systems first
The site's BMS and DCIM already hold much of the operating evidence. The assessment starts there, with read-only access agreed for the engagement.
Where a record is missing or inconsistent, that is an evidence gap. It is recorded, not estimated away.
Selective sensing
Additional sensing is introduced only for a defined question. The choice, placement and method are agreed with the site and are not published as a product specification.
Sensing does not replace protective devices, leak detection or the site's required instrumentation.
Asset and dependency model
The assessment maps the cooling path around the equipment in scope: shared headers, controls, valves, air-side distribution and the loads that depend on them.
The map shows where a single intervention affects more than one part of the system.
Engineering rules before models
Where evidence permits a bounded scenario comparison, it is built on stated engineering rules and assumptions. A model is not presented as the source of truth.
If the evidence does not support the comparison, the pack says so.
Evidence in view
See condition changes in context.
Bring condition observations, operating context and review points into one view. The example below shows how an observed change becomes a focused engineering question.
Maintenance review
From observation to a reviewable request.
The storyboard shows the sequence the site can inspect. It is deliberately plain: observe, corroborate, bound the question, then let the authorised team decide.
The human boundary.
Advisory, not control
No connection that commands equipment. The site keeps control of its systems and its procedures.
Read-only by default
Access is agreed for the engagement, limited to what the question needs, and removed or reviewed at the end.
Authorised people decide
The site's authorised team reviews the evidence, checks the constraints and decides whether the work proceeds.
Data handling
Site-controlled evidence.
Access, storage and handling are written into the engagement agreement. The site's machine data is used for the agreed assessment, not pooled into a shared dataset or used for an unrelated purpose.