IFC, BCF and IDS are portable. The project memory around them often is not. That memory is where cost, responsibility and legal evidence sit.
The open-standard gap
The construction industry already has strong open standards: IFC for model data, BCF for coordination issues, IDS for machine-checkable requirements, and ISO 19650 for information-management states. Those standards solve the exchange format problem.
They do not define a neutral project memory. In practice, the running conversation lives in vendor portals: issue comments, status changes, permissions, review decisions, uploaded snapshots, approval history and export logs. Exporting a file is possible; exporting the full trace of who did what, when and why is the hard part.
What gets locked in
| Project record | Open format exists? | Typical lock-in point |
|---|---|---|
| Model geometry and properties | IFC | Native authoring model and vendor-specific parameters. |
| Coordination issue | BCF | Live comments, assignment history and status audit. |
| Information requirement | IDS / EIR / AIR | PDF wording, portal-specific checks and approval workflow. |
| Document approval | ISO 19650 process | Sign-off evidence trapped in a CDE account. |
| Handover memory | AIM / BIM2FM | Operation data scattered across exported files and inboxes. |
The five practical pains
The key point is simple: the pain is not that vendor tools are bad. Many are excellent. The problem is that the authoritative record of a public or private building becomes dependent on a commercial account model.
- Subscription math. A project can pay for seats every year while the building itself has a fifty-year life.
- Coordination lock-in. BCF exports exist, but the live thread and audit often stay inside the portal.
- Project memory loss. The person, tenant or subscription that owned a record may disappear long before the building does.
- Client switching cost. A new client platform can mean weeks of migration and provenance loss.
- Public-sector sovereignty. Public data should not require a foreign platform account to remain readable.
What BIM-CVP adds
BIM-CVP does not replace Revit, Archicad, Solibri, BIMcollab, Trimble Connect or ACC. It adds a small signed-record layer below the project workflow and beside the existing file formats.
IFC / BCF / IDS payloads -> file hash and neutral storage reference -> signed Nostr event -> relays mirror the project memory -> export back to openBIM formats stays possible
The result is not a new central platform. It is a portable event graph: every topic, comment, validation result and approval can be verified by signature and traced back to its source file.
Implementation rule
If a record is part of the building memory, it should be exportable, hash-addressed where file-backed, and signed by its author. If a record cannot survive a CDE switch, it is not yet sovereign enough for the BIM-CVP profile.
Read on
- BIM and openBIM — the standard landscape
- BCF — coordination format explained
- Workflow model — how the event graph works
- BCF to Nostr events — detailed mapping