In ISO 19650, every file, model, drawing or document is an information container, and every container has a unique ID. The ID is built from a sequence of short fields, each taking a code from an agreed list.
The usual fields
| Field | Purpose | Example code |
|---|---|---|
| Project | Identifies the project | P2026014 |
| Originator | Organisation that produced the container | NDP |
| Volume / system | Part of the project (building, zone, system) | ZZ = all, XX = none |
| Level / location | Floor or area | 02, B1, RF |
| Type | Kind of information | M3 model, DR drawing, SH schedule |
| Role | Discipline | A, S, M, E |
| Number | Sequential number | 0001 |
Fields are separated by a hyphen: P2026014-NDP-ZZ-02-M3-S-0001. The UK National Annex to ISO 19650-2 publishes recommended codes for several fields; other countries publish their own. The project's information standard, referenced from the BEP, sets the final lists.
- P2026014Project
- NDPOriginator
- ZZVolume / system
- 02Level / location
- M3Type
- SRole
- 0001Number
Not in the name
Status (such as S1 or S2) and revision (P01, C01…) change during a container's life. They are recorded as metadata in the CDE, not in the ID. The ID stays the same from first share to archive.
Common mistakes
- Lowercase codes or extra spaces
- An originator code that isn't on the list (often a subcontractor's own abbreviation)
- Numbers with the wrong number of digits
- Version words in the name:
final,v2,new
Because each field is a code from a list, all of these can be caught automatically before files are shared.