How it works · Facility IDS
A building's data, tied to the contract and place that govern it.
An Information Delivery Specification (IDS) is the buildingSMART standard for stating exactly what data a building model must contain — and checking that it does. In Mokunet, every IDS is scoped to a facility on the governance graph, so its data requirements trace back to the contract, the moku, and the place index that govern the site. The result: model deliverables can be validated automatically against what the contract actually requires.
Two ways an IDS gets created
Facility-governed
The facility already exists on the governance graph, bound to one or more contracts. The editor reads its authoritative properties — moku, place index, GS1 location number, facility type — and embeds them as site-governance requirements in the specification. Documents are stored under a stable, place-aligned path.
Planning (ad hoc)
No facility exists yet. The editor generates a readable moku-reference name and stores the document under a planning path. When the facility is later created on the graph, the planning document can be promoted to its governed location.
The contract bridge. Governance contracts are what connect a legal agreement to machine-checkable model requirements. When a facility is bound by a contract but has no specification yet, the editor creates the anchor for one — so every IDS has a governed point of origin rather than floating free.
What an IDS specifies
A facility's specification is assembled from its graph properties and its contract. Four families of requirements are common.
Site governance
When a facility is linked, the model's site is required to carry its moku, place index, governed-area description, and SDG alignment — so the building traces back to the district that governs it.
Identification
If the facility has a GS1 Global Location Number, the model must carry it — connecting the physical site to supply-chain traceability.
Equipment & assets
Contract-required manufacturer data, model and serial numbers, and asset identifiers for the equipment a facility operates and maintains.
Facility-type extensions
Additional requirements driven by what the facility is — food-manufacturing hygiene ratings, agricultural material properties, and similar type-specific data.
Provenance tightens across the lifecycle
Beyond what data must be present, the specification tracks where data came from and who changed it — and that audit requirement gets stricter as a contract advances.
1
Design / Construction / Handoff
Each maintained element must record its source system and the role that last updated it. A timestamp is encouraged but not yet required.
2
Operations
Full enforcement: source system, updating role, and update timestamp are all required — so the operating record stays continuously auditable.
Provenance records carry the originating system — design authoring, construction BIM, commissioning, or facilities management — and the role that last touched each element, from designer and contractor to commissioning agent and district facilities manager. Together with site governance, this is what lets a delivered model be trusted as a governed record rather than an unverified file.
Validation, not assertion
The point of an IDS is that compliance is checked, not claimed.
A delivered IFC model is validated against its specification using the buildingSMART reference tooling. Results come back grouped by requirement, with per-specification pass/fail and the specific failing elements — so a model can be confirmed to carry everything the contract requires before it is formally accepted.
Grounded in:buildingSMART IDS 1.0IFC building modelsGS1 location identityGovernance contractsThe spatial backbone
Guided in the app, not gated by a wall of text
Honest framing:facility-scoped IDS, contract bridging, and automated model validation are operational in the platform's Facility IDS Editor today. The page you are reading is the conceptual reference; inside the app the work is increasingly guided by an agent that explains these property sets on demand and sets up a facility's specification with you — rather than asking you to read a manual before you begin.
Facility IDS is where the standards meet a real building: a contract becomes a checkable data requirement, anchored to a moku on the spatial backbone. See the standards it draws on, or how the same facilities participate in supply-chain governance.