Two years later, the record still answers the question.
A valve is in hand and nobody knows why. The head-end shows the override but not the reason, the historian shows the trend but not the override, and the person who made the call left in March. The record is the product.
One traceable source of truth
The point of the record is not that it audits well. It is that there is one place the answer comes from, where a head-end, a historian, an alarm server and a spreadsheet each held part of it and disagreed about the rest. One asset, one timeline, one answer — traceable back to the evidence and to whoever, or whatever, acted.
What lands on the record
Every alarm transition, control action, override and release, schedule change, and work order — against the asset it happened to, with the actor and, where a person made the call, the reason they gave. Each one carries the trend that evidences it, resolved over the exact interval it happened, so a decision and the data behind it read on one timeline. An agent’s actions land on the same record as a person’s, in the same shape, which is what makes the two comparable.
Retained, not rolled up
The record itself is never thinned. It is small enough that there is no reason to, so every action, reason and release stays whole for as long as you keep the site. Telemetry is kept at collection resolution for a retention you choose, and if a window ever ages out, the entry that referenced it says the evidence is no longer retained rather than showing you nothing. A fault that recurs every eleven months is only visible to someone holding eleven months of unsmoothed data — which makes retention a decision to take deliberately rather than discover afterwards.
Work history beside the telemetry
The work order sits on the same timeline as the trend that triggered it and the alarm that preceded it. “What did we do about this last time” becomes a query against one record rather than a conversation with whoever has been here longest.
Specifics
- Captured
- Trend samples, alarm transitions, control actions, overrides and releases, schedule changes, work orders
- Attribution
- Actor, timestamp and source on every event, whether a person, a schedule or an agent made it
- Export
- Your points, your history, your records, on a documented schema
Common questions
How long is history kept?
The record of what was done and why is kept whole, indefinitely. Telemetry is kept at collection resolution for a retention you set — a decision about storage rather than a limit the platform imposes on you — and tiering it is itself recorded, so the record always tells you what evidence it can still resolve.
Can we get our data out?
Yes, on a documented schema, while you run the platform and on the way out if you ever stop. You are replacing a head-end that made leaving expensive; we are not going to rebuild that.
Bring your point list.
The first conversation is a survey: what you run today, and what it would look like modelled.