How it works · Building data
A building's data, tied to the contract and place that govern it.
When a building goes up in your moku, its contract says what records it must keep. Mokunet uses an open buildingSMART standard called IDS — a precise list of what a building's digital model must contain — to capture exactly those requirements. Every list is tied to a real facility, so it traces back to the contract, the moku, and the place that govern the site, and a finished model can be checked automatically against what the contract actually requires.
Two ways an IDS gets created
Facility-governed
The facility already exists in the system, tied to one or more contracts. The editor reads its official details — moku, location, GS1 global location number, facility type — and writes them into the requirements for the building's data. Documents are filed under a stable, place-based path.
Planning (ad hoc)
No facility exists yet. The editor creates a readable moku-based name and files the document under a planning path. Once the facility is created, that planning document can move to its governed home.
The contract bridge. A governance contract is what links a legal agreement to building-data requirements a computer can check. When a facility has a contract but no list yet, the editor creates a starting point for one — so every list has a governed origin rather than floating free.
What the list specifies
A facility's list is built from its own details and its contract. Four families of requirements are common.
Site governance
When a facility is linked, the building's record must carry its moku, location, the area it governs, and the SDG goal it serves — so the building traces back to the district responsible for it.
Identification
If the facility has a GS1 Global Location Number, the record 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.
Every piece of the record carries where it came from — the architect's design, the construction model, commissioning, or day-to-day operations — and the role that last touched it, from designer and contractor to commissioning agent and district facilities crew. Together with site governance, that history is what lets a delivered model be trusted as a real, governed record rather than an ungoverned file.
Validation, not assertion
The point of an IDS is that compliance is checked, not claimed.
A delivered building model is checked against its list using the official buildingSMART tools. Results come back grouped by requirement, with a clear pass or fail and the exact elements that fell short — so a model can be confirmed to carry everything the contract requires before it is formally accepted.
Grounded in:buildingSMART IDS 1.0Digital building modelsGS1 location identityGovernance contractsThe shared map
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 requirements on demand and sets up a facility's list with you — rather than asking you to read a manual before you begin.
This is where the standards meet a real building: a contract becomes a checkable data requirement, tied to a moku on the shared map. See the standards it draws on, or how the same facilities take part in supply-chain governance.