VULCAN · the estate diagnostic
Before the platform, the count. On a facilities and field estate.
The field is where the value is created and where the context is thinnest. The count establishes which record is authoritative for the asset, the job and the closeout before the model tries to put them in the technician's hands.
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
Facilities and field
Unit of account
The facility and its service route
Carries
The work order and its service level
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
Job plans, asset history, field reports, safety procedures and closeout records, enumerated with owners and refresh cadence.
Authority registry
The asset record scored against the field report, so a disagreement between them has a named survivor and a flagged exception.
Boundary matrix
Occupant, client and site data tiered explicitly, with least privilege named per dataset.
- 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
- Job plans
- Asset history
- Closeout records
OT
Equipment systems
- Building controls
- BMS
- Access
- Meters
The question that needs both
Is this space ready, and can we prove it was when someone asks?
What the count returns here.
- 01A definitive inventory of the estate's datasets, with owners and refresh cadence
- 02The facility and its service route established as the unit of account, with the work order and its service level attached
- 03A boundary matrix naming what may enter broad pipelines and what stays client-scoped
- 04An ingestion manifest your facilities and field leadership can both diff
The gates do not change because the estate is walked rather than watched. 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
Facilities & Field Operations
The sector page covers the operating reality, the application set and the evidence in context for this industry.
Explore Facilities & Field Operations