Implementation
Open schema instead of a black-box database
Most tools hide their data model behind a login. You only see UI fields and vendor exports, so you cannot inspect, improve, or exit cleanly.
Steps
-
Explore the public contract
Open schema.pragmaticbim.ch with no account. Inspect classes, relations, and versioned releases before you buy or integrate.
-
Map your entities once
Align projects, spaces, requirements, performance, and change records to the published classes instead of inventing a private product model.
-
Run products on the same contract
{yourcompany}os and iterthink use this open pragmaticBIM Schema, so process and BIM data share one vocabulary instead of three silos.
-
Improve it in the open
File gaps, propose entities, and open pull requests on the Pragmatic BIM Data Contract. Open source collaboration makes the shared schema better for everyone, not only for one vendor roadmap.
Opaque product database vs open schema
|
Typical SaaS tool
|
Open pragmaticBIM Schema
|
Why it matters
|
|
|---|---|---|---|
| See the model | Behind login / sales call | Public docs, no account | Audit before commitment |
| Improve the model | Vendor roadmap only | Issues, PRs, shared releases | You help shape the contract |
| Linked data | Proprietary tables per tool | Graph-first shared contract | Reuse meaning across products |
| Exit / sovereignty | Schema lock-in by default | Inspect, export, version-pin | You know what "your data" is |