VULCAN · the estate diagnostic
Before the platform, the count. On a logistics estate.
Spend, suppliers, inventory, contracts and field urgency are decided in separate systems, and the exposure hides between them. The count establishes which system is authoritative for each fact before risk and savings can be read as one question.
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
Logistics
Unit of account
The node and its dock
Carries
The throughput commitment
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
Purchase orders and invoices, supplier and contract records, inventory positions, work orders and budgets, enumerated with owners.
Authority registry
Spend, demand and stock each scored to their authoritative source, so a disagreement between them is a finding, not a surprise.
Boundary matrix
Supplier, contract and pricing data tiered explicitly, with commercial sensitivity 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
- POs
- Invoices
- Contracts
- Inventory
OT
Equipment systems
- Material handling
- Dock and yard equipment
The question that needs both
Is this lead time a supplier problem or an equipment problem?
What the count returns here.
- 01A definitive inventory of the estate's datasets, with owners and refresh cadence
- 02The node and its dock established as the unit of account, with the throughput commitment attached
- 03A boundary matrix naming what may enter broad pipelines and what stays commercially scoped
- 04An ingestion manifest your procurement and operations teams can both diff
The gates do not change because the estate moves 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
Logistics & Supply Chain
The sector page covers the operating reality, the application set and the evidence in context for this industry.
Explore Logistics & Supply Chain