BIM Coordinator Essentials

Finish all 13 lessons to download a certificate of completion.

1. Chapter 1. Information management basics

   0/3 done
   • 1.1 What ISO 19650 asks of a project teamISO 19650 is less about software and more about agreeing who needs what information, when, and in what form.
   • 1.2 EIR, BEP, MIDP and TIDP explainedFour acronyms, one conversation. Requirements go down, plans come back up.
   • 1.3 The CDE and its statesWork in progress, shared, published and archived. Each state is a promise about how far you can trust the information.
   • Chapter recap

2. Chapter 2. Coordination

   0/3 done
   • 2.1 Setting up clash tests that matterTen thousand clashes help nobody. A good test matrix produces a short list of real problems with a clear owner.
   • 2.2 Running a coordination meetingA good coordination meeting is short, visual and ends with decisions that have owners and dates.
   • 2.3 Tracking issues to closureAn issue log is only useful if every issue moves towards closed, and everyone agrees what closed means.
   • Chapter recap

3. Chapter 3. Model requirements

   0/3 done
   • 3.1 LOD vs LOINLOD describes how developed and reliable an element is. LOIN describes exactly what information is needed for a purpose.
   • 3.2 Writing an LOD matrix your team will useShort, specific and owned. A practical way to build an LOD matrix that survives contact with the project.
   • 3.3 Writing IDS requirements and reading the resultsTurn “the model must contain fire ratings” into a rule software can check — and know what a pass or fail actually tells you.
   • Chapter recap

4. Chapter 4. Files, names and coordinates

   0/3 done
   • 4.1 Naming information containersA good naming convention makes every file findable, sortable and checkable by a machine. Here is how the fields fit together.
   • 4.2 Shared coordinates and georeferencingModels only line up if everyone agrees where zero is. Georeferencing ties that zero to the real world.
   • 4.3 Checking an IFC file before you share itFive minutes of checks on an IFC export saves a week of confusion in the federated model.
   • Chapter recap

5. Chapter 5. Handover

   0/1 done
   • 5.1 Asset information at handoverAsset data is planned at the start, filled in as the design develops and checked at every milestone — not collected in a rush at practical completion.
   • Chapter recap