Design-partner study. Anonymized at partner's request.
The problem
A field-services org running 240 industrial sites. Each site has its own equipment runbook. Procedures evolve continuously. When something fails, regulators want to know what the runbook said at the time of the failure — not what it says today.
The org had been using a vendor-locked CMS that had no history. They'd been keeping monthly PDF snapshots in S3 as a workaround. Auditors didn't trust the snapshots — couldn't prove the snapshot wasn't tampered with after the failure.
What changed
- StaticOwl with WORM mode and audit chain
- Per-site runbooks live as content types; equipment-specific procedures as nested content
- Time-travel query:
MATCH (r:Runbook {siteId: 'plant-7'}) AT '2026-04-02T15:00:00Z' RETURN r— answers "what did this runbook say at this moment" - Compliance bundle exports per-incident: pull the runbook + every cross-referenced procedure as it existed at the failure time, signed manifest, ready for the auditor
Result
- Auditor satisfaction: regulators accept StaticOwl exports as primary evidence (vs. supplemental, which was the prior vendor's status)
- Incident investigation time: from 4 days to 4 hours
- Compliance review hours / month: -65%