The server today has only layer 1, and even that is used inconsistently. Most systems stop at layers 1 and 2. What makes BABOOM better is that the four layers check each other: the folder must agree with the name, the name must agree with the register, and the register must agree with the state.
| State | Read | Write |
|---|---|---|
| WIP | Own task team | Own task team |
| SHARED | All project teams | Information manager only |
| PUBLISHED | Project + recipients | Nobody (append only) |
| ARCHIVE | Project | Nobody |
This is the existing BABOOM/D21 grammar. Two codes in the name must match the folder: the type code must match the data-type folder, and the role code must match the discipline folder. A file named …-M3-ARC-… that sits in 1.DWG\01.STR is wrong, and the checker flags it.
Revision and status are not in the file name. They live in layer 3, so the name never changes when the file is revised.
| Code | Meaning | State |
|---|---|---|
| S0 | Work in progress | WIP |
| S1 | Fit for coordination | SHARED |
| S2 | Fit for information | SHARED |
| S3 | Fit for review and comment | SHARED |
| S4 | Fit for stage approval | SHARED |
| A1, A2… | Authorised and accepted for a stage | PUBLISHED |
| CR | As constructed record | PUBLISHED |
Revisions: P01.01 while in WIP, P01 when shared, C01 when contractually published. These are the UK national annex codes to ISO 19650. Projects can map them to a client's own codes in the BEP.
There is one container register per project, in 01.SHARED\21.RECORD. It has one row per file and is updated at every state change. This register replaces the PC-to-PC “FROM / TO” folders.
| Container name | Type | Role | State | Suitability | Revision | Author | Checker | Approver | Date | Transmittal | SHA-256 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| PRJ01-ORG01-ZZ-L01-M3-ARC-00001 | 0.RVT | ARC | SHARED | S1 | P02 | … | … | … | … | TR-0012 | … |
Moving a file to the next state counts only when a register row is added for it. The SHA-256 proves that the file in PUBLISHED is the exact file that was approved.
| Check | Fails when |
|---|---|
| Name grammar | The name breaks the D21 pattern or uses a code that is not on the list |
| Folder ↔ name | The type or role code doesn't match the folder the file sits in |
| Folder ↔ register | A file in SHARED or PUBLISHED has no register row, or a row points to a missing file |
| Register ↔ state | The suitability code doesn't belong to the folder's state (e.g. S0 in PUBLISHED) |
| Integrity | A PUBLISHED file's hash doesn't match its register row |
| Hygiene | A path is over 180 characters, or the tree holds backups, temp folders or personal folders |
This checker is the Naming Check and Startup Check buttons already on the BABOOM ROAD MAP. It runs on demand and before every issue.