ISO 19650 explained for freshers: CDE, naming & information levels
ISO 19650 is the international standard for managing information on building projects using BIM. As a junior modeler you will mostly feel it through three things: the Common Data Environment where files live, the naming convention every file must follow, and the information requirements that say how much detail your model needs.
What is ISO 19650?
ISO 19650 is a series of international standards that describe how project information should be specified, produced, shared and approved when BIM is used. It grew out of the UK's BS 1192 and PAS 1192 standards and is now used on projects around the world, especially in the UK, Middle East and Australia.
It is not a software manual. It is a set of rules about process: who needs what information, when, in what format, and how it is checked.
1. The Common Data Environment (CDE)
The CDE is the single source of truth for a project: a shared platform where every model, drawing and document lives. Files move through defined states:
| State | Meaning |
|---|---|
| Work in progress | Your team is still working on it. Not visible to others. |
| Shared | Checked and released to other teams for coordination. |
| Published | Authorised for use, for example for construction. |
| Archived | Kept as a record of what was issued. |
As a junior, the key habit is simple: never share a file that has not been checked, and always work from the latest shared version of other disciplines.
2. File naming containers
Every file follows a field-based naming convention so anyone can tell what it is without opening it. A typical pattern looks like:
PROJECT-ORIGINATOR-VOLUME-LEVEL-TYPE-ROLE-NUMBER
For example, a mechanical model for level 03 might be named something like HSP-BCR-ZZ-03-M3-M-0001, where each field is a code from the project's agreed list. The exact codes are defined in the project's information standard, so always check that document first.
Getting naming wrong sounds minor, but on a project with thousands of files it breaks searches, automated checks and approvals. It is one of the first things a coordinator notices.
3. Information requirements and LOI
ISO 19650 asks the client to define what information they need (the Exchange Information Requirements), and the delivery team to respond with a BIM Execution Plan describing how they will provide it.
Two related ideas you will hear constantly:
- Level of geometry (often described with LOD): how detailed the shape is.
- Level of Information (LOI): how much data the object carries, such as manufacturer, model, airflow or fire rating.
Modeling more than required wastes time; modeling less fails the deliverable. Read our LOD guide for the geometry side.
Documents you will meet on a real project
- EIR – Exchange Information Requirements from the client.
- BEP – BIM Execution Plan from the delivery team.
- MIDP / TIDP – delivery plans listing every deliverable, owner and date.
- Project information standard – naming codes, units, coordinates.
Why freshers should care
Many Indian consultancies deliver models for UK, Middle East and Australian clients where ISO 19650 is expected. A fresher who already understands the CDE, naming and information requirements needs less hand-holding and is trusted with live deliverables sooner.
BIM Crafter teaches ISO 19650 working knowledge alongside the software, and you apply it daily on live international projects during the internship.
Apply for the next batch