VULCAN · the estate diagnostic
Before the platform, the count. On a commercial estate.
Program cost, schedule, risk, staffing and change live in separate tools, and the review is reconstructed by hand every cycle. The count establishes which system is authoritative for each fact before variance can carry a cause.
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
Commercial
Unit of account
The suite
Carries
The lease clause and its obligation
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
Financial systems, schedules, contracts and change orders, risk registers and staffing plans, enumerated with owners and refresh cadence.
Authority registry
Cost, schedule and scope each scored to their authoritative source, so a variance has one cause, not three opinions.
Boundary matrix
Client, program and contract data tiered explicitly, with access scoped per engagement.
- 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
- Financials
- Schedules
- Contracts
- Change orders
OT
Equipment systems
- Building systems where the programme is physical
The question that needs both
Does this change order move the critical path, and what will it cost to run?
What the count returns here.
- 01A definitive inventory of the estate's datasets, with owners and refresh cadence
- 02The suite established as the unit of account, with the lease clause and its obligation attached
- 03A boundary matrix naming what may enter broad pipelines and what stays program-scoped
- 04An ingestion manifest your program and finance teams can both diff
The gates do not change because the estate runs programs. 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
Commercial Operations
The sector page covers the operating reality, the application set and the evidence in context for this industry.
Explore Commercial Operations