Geometry isn't governance. The twin is a contract.
The industry sells geometry. IFC, COBie, BIM — file formats and federated models, photogrammetry of an asset that already exists. What facility owners actually need is the thing the geometry can't carry: authority over what changes, evidence of who changed it, and proof it still meets the standard it was commissioned to. Essence treats the twin as a governed contract over the asset's lifecycle, not a model of its shape.
Substrate COBie · ASHRAE 223P · IFC · NBIMS · ISO 55000Patents 3 issued, zero prior artStage FCTWIN vertical · active build
Scroll
01 · The shift
What's sold is the model. What's needed is the authority.
A digital twin program today buys you a federated model — geometry, schedules, equipment lists, sometimes sensor feeds. It tells you what's there. It doesn't tell you who is allowed to change it, under which standard the change must be evaluated, what evidence is admissible to prove the change was legitimate, or how any of that propagates across the next thirty years of the asset's life. That's not a software gap. It's an architectural one — the model layer was never the place to put it.
What the industry sells
No lifecycle authority · model alone
A federated model
Geometry · schedules · COBie tables
What it answerswhat's there
What it can'twho decides
Lifecycle horizonhandover
What the owner needs
Aptiv Spec · governed by construction
A governed contract
Authority · evidence · jurisdiction · lifecycle
What it answerswho's authorized
Evidence trailby construction
Lifecycle horizoncommissioning → end-of-life
02 · The standards
The substrate the contract enforces against.
A governed twin is only as good as the standards it grounds in. FCTWIN's Aptiv Specs are written against the documents owners and AHJs already accept as authoritative — not invented schemas, not vendor proprietaries. Each spec carries the source it grounds in, the evidence span it cites, and the jurisdiction it applies under. Add a new standard, the contract knows. Update a clause, the contract revalidates.
COBie 2.4
Construction Operations Building Information Exchange
The handover spec. What gets delivered to facilities at substantial completion — equipment lists, warranties, spares, maintenance schedules. The contract knows when handover is complete.
ASHRAE 223P
Semantic Data Model for Buildings
The vocabulary HVAC, lighting, and BAS systems use to describe themselves. The contract enforces that controls intent maps to validated semantic relationships, not vendor naming.
IFC 4.3
Industry Foundation Classes — Infrastructure
The interoperable model schema across architecture, infrastructure, and rail. Geometry plus typed properties plus relationships. The contract treats it as the authoritative cross-discipline model.
NBIMS PBR · BEP · BUD
National BIM Standard — Plans, Execution, Use
Project Build Requirements, BIM Execution Plan, and Build-Up Document. Owner-side governance for what the BIM is for, who delivers what, and what proves it.
ISO 55000:2024
Asset Management Systems
The international standard for managing physical assets across their full life. Aligns the twin's governance to the same vocabulary executive auditors and insurers already use.
NFPA 72 · Ch. 17
National Fire Alarm and Signaling Code
Initiating device requirements — the kind of clause where "is this twin still compliant" must be answerable on demand. The contract knows when a sensor's coverage zone changed.
9 Aptivs committed in aptiv-shard-deep-analysis.jsBIM scraper · operationalGrounded against source · zero fabrication
03 · The contract
What an Aptiv Spec carries that a model can't.
A model holds geometry and typed data. A contract holds what is allowed to happen. The difference looks small in isolation and becomes the entire ballgame across an asset's lifecycle. Below is the asymmetry — and why digital twin programs that stop at the model layer keep finding themselves rebuilding the governance layer in spreadsheets, ticketing systems, and PDF approvals.
Authority — who is allowed to propose, approve, and commit a change. Named human principals, not roles in a wiki.
Evidence — the source span, hash, and jurisdiction every claim grounds in. Audit trail by construction.
Standards binding — which clause of which document the action is being evaluated against, version-stamped.
Lifecycle scope — design, commissioning, operations, retrofit, decommissioning — each phase has its own admissible actions.
Detection ≠ determination — the contract surfaces conditions; the named principal decides. Always.
04 · The gap
Substrate-level governance is categorically different.
Twin programs that bolt governance onto the model layer pay a tax at every handoff — design to construction, construction to commissioning, commissioning to operations, operations to retrofit. Each handoff translates between vocabularies the next phase doesn't share. Essence resolves intent once, in Synergy, then enforces across every phase. The numbers below are the architectural consequence.
Fabricated source claims
0
Every Aptiv Spec grounded · BIM scraper verified · creator-reviewed
Aptivs come up governed by construction · spec-defined, not bolted on
Twin programs
Governance lives in spreadsheets, ticketing systems, and PDF approvals — outside the model. Every handoff between project phases is a translation step where authority and evidence get reconstructed by hand.
Twin programs
Standards compliance is checked at gates, not enforced continuously. A retrofit that quietly violates ASHRAE 223P semantic relationships or NFPA 72 coverage rules can pass through commissioning before anyone notices.
Essence
The Aptiv Spec is the contract. Standards, authority, evidence, and lifecycle scope are constitutive — an action that violates the spec doesn't fail at audit, it fails at proposal. There is no separate "time to govern" step.
Essence
Synergy resolves intent once, then the same governed action propagates across every lifecycle phase — design model, construction record, operations system, retrofit baseline. The twin doesn't need to be re-translated between phases. It's the same contract throughout.
05 · What's next
FCTWIN is an active build.
The first nine standards Aptivs are committed. The BIM scraper is operational. Owner-side, AHJ-side, and integrator-side conversations are open. The full briefing — architecture, patents, performance evidence — lives in the investors section on mindaptiv.com.