VULCAN · the estate diagnostic
Before the platform, the count. On an industrial estate.
Plant and asset data is rich but fragmented across control systems, historians, maintenance records and crew knowledge. Before any model is built, the count establishes what exists, what is authoritative, and what may enter a governed pipeline.
The unit of account.
The eight gates contain no sector content. What changes between estates is the unit of account and the obligation attached to it, and the diagnostic establishes that first.
This estate
Industrial
Unit of account
The asset and its control loop
Carries
The work order and its permit
A design commitment about where obligation lands, not a deployment claim. No measured evidence from another estate transfers here.
The eight gates, run here.
The gates are the same on every estate. What they touch here is named below; what they return is listed at the end.
Dataset census
Process historians, maintenance and asset records, inspection routes, inventory and crew notes, enumerated dataset by dataset with owners and refresh cadence.
Authority registry
Each source scored for authority: which system is the record of truth for the asset, the work order, the failure code and the permit.
Boundary matrix
Data adjacent to the control network tiered explicitly. What may leave the plant network is listed, never assumed.
- 01
Dataset census
Every dataset enumerated with columns, row volume, owner and last refresh
- 02
Authority registry
Each dataset scored for authority; score, basis and reviewer recorded and reproducible
- 03
Duplicate resolution
Recut datasets identified, the survivor named, lossy recuts flagged
- 04
Identifier profile
Candidate keys profiled; collisions and drift documented, never corrected in silence
- 05
Crosswalk
An explicit bridge between the analytics key and the system-of-record identifier; exceptions quarantined, not merged
- 06
Boundary matrix
Every dataset assigned a tier; those barred from broad pipelines listed explicitly
- 07
Ingestion manifest
A deterministic include, defer or reject call per dataset, diffable between runs
- 08
Expectations suite
Automated expectations that fail the build, not a report read afterwards
The seam.
Business systems do not talk to equipment systems, and the question that matters on this estate needs both. The diagnostic maps both sides before anything is connected.
IT
Business systems
- ERP
- CMMS
- Work orders
- Inventory
OT
Equipment systems
- SCADA
- Historians
- Vibration
- Thermography
The question that needs both
Which asset should this crew touch first tomorrow, and what does deferring it cost?
What the count returns here.
- 01A definitive inventory of the estate's datasets, with owners and refresh cadence
- 02The asset and its control loop established as the unit of account, with the work order and its permit attached
- 03A boundary matrix naming what may enter broad pipelines and what stays at the edge
- 04An ingestion manifest your reliability team can diff between runs
The gates do not change because the estate makes things. The unit of account does.
The full method
The method, and the one measured engagement.
The VULCAN page carries the full argument: the eight gates, the platform path, the scorecard, and the single engagement where the diagnostic has been run and measured at full scale.
Read the full methodThe operating world
Industrial Operations
The sector page covers the operating reality, the application set and the evidence in context for this industry.
Explore Industrial Operations