ISO 19650 implementation guide
ISO 19650 reads like a 60-page standard and lands as one sentence: agree what information you need, when you need it, in a shape you can hand off. This guide collects the playbooks teams actually used to get there — without buying a consultancy programme.
90 days is the right window
Anything shorter and people fake adoption; anything longer and the new BEP gets diluted by the next deadline. Three months gives a project enough information exchanges to verify the standard is real.
LOIN beats LOD for handover
LOD answered the wrong question (how detailed?) and missed the right one (what does the receiver need?). LOIN forces the conversation that prevents COBie mismatches at handover.
The BEP sections that earn their keep
Information exchange schedule, model federation strategy, naming conventions, common data environment workflow, deliverables matrix, and the audit cadence. Everything else is decorative.
Articles included in this guide
ISO 19650 in 90 days: a practical onboarding plan
ISO 19650 is 200+ pages of process. A 90-day plan that turns the spec into a working practice — without freezing the studio for a quarter.
LOD vs LOIN: a practical reading of ISO 19650
LOD is geometry only; LOIN is geometry plus information. ISO 19650 picked LOIN. What changes for your delivery contracts.
BIM Execution Plan: the 6 sections that actually get used
Most BEPs are 40 pages, used twice. The six sections that drive day-to-day delivery decisions on the project floor.
Federated model governance: who owns what when something breaks
When a clash crosses two consultants, the answer "fix it" isn't enough. A RACI for the federation prevents the silent stand-off.
A BIM-to-COBie mismatch that cost a project six weeks
COBie data validation failed at handover. The root cause was inconsistent equipment-type classification across four consultants. What we learned.