A thousand standards, one anchor: why we are building the standards fabric
A single plant is covered by dozens of standards at the same time, revised on their own schedules. Following that by hand is not difficult — it is impossible. Here is what we are building instead.
Take one building. Building automation, lighting control, connected devices, control systems, networks, access control, cameras, information security. Every category carries standards, usually several, and each is revised on its own schedule. Multiply that by a site, then by an organisation, then by the suppliers in between.
No one is failing at this out of laziness. The volume is beyond what a human can track, and the honest conclusion follows from that: what is inhuman to follow needs something inhuman to follow it.
What we are building. A standards fabric: standards attached to the nodes they actually govern, watched continuously, with the change landing on the node instead of in a newsletter. When a revision is published, the question is not what changed in general. It is which of our assets are affected, who owns them, and what it costs to do nothing.
Why it matters now. Requirements have started to carry dates and personal accountability. A control that cannot say which node it applies to cannot be audited, only described. And a standard nobody can locate on a map is a standard nobody can budget for.
Where we are. The mechanism is in use in our own work and being hardened. Reality first: assets, owners, dependencies. Then the requirements move in, one at a time, starting with those already in force.
We are looking for two or three organisations who want to run their own standard landscape through it while it is still being shaped. If your answer to "which requirements apply to your heaviest site" takes more than a day to produce, that is the conversation.
Where this goes next
Want this applied to your organisation?
One call is enough to know if we're a fit.