VULCAN · the estate diagnostic
Before the platform, the count. On an operator portfolio estate.
Office, retail, industrial and flex, mixed use, medical office, and data and life science portfolios run on different operating units, calendars and obligations. This is the estate the diagnostic has run on at full scale; the measured output is on the VULCAN page.
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
Operator portfolio
Unit of account
The unit
Carries
The lease and its counterparty
This estate carries the one measured engagement. Every other estate page is a design commitment, not a deployment claim.
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
Management platforms, work orders and inspections, vendor progress feeds, access control and accounting, enumerated with owners and refresh cadence.
Authority registry
Each source scored for authority over the unit record, the obligation and the service event, with the reviewer and basis recorded.
Boundary matrix
Managed and owned entitlements tiered explicitly, so one asset never answers to two ungoverned models.
- 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
- PMS
- CRM
- Finance
- Work orders
OT
Equipment systems
- Building controls
- Access
- Utility meters
- Leak and freeze sensors
The question that needs both
Is the space ready, who authorised the work, and what did the energy cost?
What the count returns here.
- 01A definitive inventory of the estate's datasets, with owners and refresh cadence
- 02The unit established as the unit of account, with the lease and its counterparty attached
- 03A boundary matrix naming what may enter broad pipelines and what stays client-scoped
- 04An ingestion manifest your operations and ownership teams can both diff
This is the estate where the count has been run and measured. Every other estate page on this site is a design commitment; this one carries evidence.
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
Real Estate & Property Management
The sector page covers the operating reality, the application set and the evidence in context for this industry.
Explore Real Estate & Property Management