VULCAN · the estate diagnostic
Before the platform, the count. On an energy and utilities estate.
Operations depend on telemetry, network topology, maintenance, outage plans, crews, weather and finance, kept in different tools by different teams. The count establishes what exists and what is authoritative before the storm clock starts.
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
Energy and utilities
Unit of account
The meter and its circuit
Carries
The tariff and the billback
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
Telemetry and control systems, network topology, asset and maintenance records, outage plans, crew schedules and weather feeds, enumerated with owners.
Authority registry
Each source scored for authority over topology, condition, consumption and crew qualification.
Boundary matrix
Metering and customer data tiered explicitly, with the regulatory boundary named rather than implied.
- 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
- Outage plans
- Crew schedules
- GIS
- Finance
OT
Equipment systems
- SCADA
- Substation telemetry
- Metering
The question that needs both
Which feeders get hardened before the storm, and who is qualified to do it?
What the count returns here.
- 01A definitive inventory of the estate's datasets, with owners and refresh cadence
- 02The meter and its circuit established as the unit of account, with the tariff and the billback attached
- 03A boundary matrix naming what may enter broad pipelines and what stays inside the control environment
- 04An ingestion manifest your operations and compliance teams can both diff
The gates do not change because the estate keeps the lights on. 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
Energy & Utilities
The sector page covers the operating reality, the application set and the evidence in context for this industry.
Explore Energy & Utilities