How it works
Get the record. Understand the equipment. Then generate everything around it.
Seven steps, each with what goes in, what comes out, and what it does not claim. Every step is marked with its status. The record-keeper exists as a lab preview; nothing is released yet.
The pipeline
01 Get the record Preview
- In
- Everything the building should have on file: station backups, controller programs, drawings, submittals, sequences, commissioning reports, and what the devices say when asked.
- Out
- Every version of everything, with a hash, a time and a name. Delivered or pulled on a cadence; receipts and an overdue list (Phase 3). Read-only reads of the network. Kept encrypted on a server you own; exportable in open formats.
- Never
- A guess at anything the record does not contain. Writing to any device.
02 Import the engineering Planned
- In
- A station backup (.bog, .dist), a controller application file (.caf, .gfx), a Metasys export, an equipment schedule, a register map.
- Out
- Devices, points, units, writability, links, alarm and history configuration, native addresses (BACnet device and object ids), metadata points such as AreaServed. Every fact with a locator back into the file.
- Never
- What a wiresheet means. Control logic. Passwords (redacted and never stored). Anything in modules the importer has no schema for, which it reports as unknown rather than guessing.
03 Discover equipment and relationships Planned
- In
- The imported facts.
- Out
- Equipment instances with a type (VAV with reheat, AHU, FCU) and a confidence; hasPoint from containment; serves from metadata or naming; feeds from trunk and AHU structure where it exists.
- Never
- A relationship with no evidence. Below the confidence threshold it becomes a question, not a fact.
04 Identify equipment-specific differences Planned
- In
- Each instance's points and parameters.
- Out
- Reheat type and stages, fan, interlocks, minimum and maximum airflow, setpoints, served space, serving AHU, each with its own source.
- Never
- A value copied from another box. If the device or the file does not carry it, the field is empty and flagged.
05 Flag what cannot be established Planned
- In
- Conflicts, gaps, low-confidence inferences.
- Out
- A questions queue with the evidence attached. Answering writes a confirmed or rejected fact that supersedes the inference. Open questions are a headline metric.
- Never
- A silent default.
06 Generate equipment views Planned
- In
- A shared template per equipment type and the instance.
- Out
- A view that draws the heating valve because the box has one, the stages because they exist, the interlock because the relationship was established. Point tables, navigation, alarm and history proposals from the same model.
- Never
- A file per box. There is no graphic file to drift.
07 Keep it in sync Planned
- In
- A new import, a live read, the supervisory representation.
- Out
- A diff by component and slot: same persisted identity first, then same name under a matched parent, so a renamed folder's children still line up. Drift between the engineering, the controller, and the supervisor becomes visible.
- Never
- An automatic rewrite. Changes are proposed and reviewed.
A concept walkthrough on eighty synthetic VAV boxes
This is a labeled concept built from synthetic data in your browser. It shows the equipment-instance idea. It is not the importer, which does not exist yet, and it is not connected to anything.
What is real in this walkthrough: the data model (instances, parameters with a source each, questions with evidence, a shared template rendering per instance). What is not: the numbers, the station, the import. When the importer ships, this page will show its actual output on a published synthetic fixture, and the time comparison will be the one we measure on the first authorized pilot.
Where every fact comes from
Four labels, carried by every fact. The model never overwrites: a confirmation supersedes an inference and the chain stays visible. Ask the model why it thinks what it thinks and it answers with the file, the device, the rule, or the person. The provenance model in detail.
From controllers to a generated BAS
Controllers, programmed
Niagara stations, Metasys and Distech controllers, BACnet and Modbus devices. Nothing changes here.
Engineering, imported
Station backups, controller application files, schedules, register maps. Read on your machine. Never uploaded unless you say so.
A model, with provenance
Sites, equipment, points, relationships. Each fact observed, imported, inferred, or confirmed by a person, and labeled as such.
A BAS, generated
Navigation, point tables, equipment views, alarms, histories, an API, and tools an assistant can use. Useful with or without AI.
Nothing changes at stage one. The controllers keep running their programs. The files stay on your machine. Every source, with what it can and cannot tell us.
What we measure, and publish
When the importer and the engine ship, every import prints a report, and the public demo publishes it: import coverage (components typed, points attached to equipment), relationships by confidence band, questions open and answered, unknown types, and an estimated technician time that is labeled as an estimate until the first authorized pilot measures it. We will not publish a time saving we have not measured.