Every information container in a common data environment carries two codes besides its name: a status (also called suitability), which says what it may be relied on for, and a revision, which says which version it is. ISO 19650 requires both; the codes themselves come from a national annex. The codes below follow the UK National Annex, which many projects worldwide adopt.
At a glance
| Status (suitability) | Revision | |
|---|---|---|
| Answers | What can I use this for? | Which version is this? |
| Examples | S1, S2, S3, A1, CR | P01, P01.1, C01 |
| Changes when | The container moves between CDE states or purposes | The content changes |
| Stored as | Metadata in the CDE, not in the file name | Metadata in the CDE, not in the file name |
Status codes (UK National Annex, simplified)
| Code | State | Meaning |
|---|---|---|
| S0 | Work in progress | Initial status; within the task team only |
| S1 | Shared | Suitable for coordination |
| S2 | Shared | Suitable for information |
| S3 | Shared | Suitable for review and comment |
| S4 | Shared | Suitable for stage approval |
| S6 | Shared | Suitable for PIM authorisation (information model delivery) |
| S7 | Shared | Suitable for AIM authorisation |
| A1, A2… | Published | Authorised and accepted for a stage or purpose (for example construction) |
| B1, B2… | Published | Partially authorised, with comments to resolve |
| CR | Published | As constructed record |
Projects may define their own codes or meanings in the information protocol; always check the project's list.
Revision codes
| Form | Meaning | Example |
|---|---|---|
| P + two digits | Preliminary revision, used while shared | P01, P02 |
| P + digits + point version | A work-in-progress version between shared revisions | P01.1, P01.2 |
| C + two digits | Contractual revision, used when published | C01, C02 |
A container usually starts at P01.1 in work in progress, is shared as P01, revised to P02, and published as C01.
Why codes are metadata
The container name stays the same for its whole life. Status and revision change. Keeping them in metadata lets the CDE show the current version, filter by suitability, and keep the full history, without creating new file names for each issue.
Common mistakes
- Using a container for something its status does not allow, such as building from an S2 drawing.
- Writing the status into the drawing title block but not into the CDE, so the two disagree.
- Skipping preliminary revisions and issuing C01 for coordination.
- Inventing codes per team instead of using the project's list.
Where to read more
The UK National Annex to ISO 19650-2 defines these codes; national guidance explains their use. Your project information protocol is the final word.