ArchHubBABOOMDownload

BABOOM information system

The folder tree is one of four layers. All four work together, and one checker ties them. Data type before discipline, always.

The four layers

LAYER 1

Place

One tree. Its folders show state → data type → discipline.
LAYER 2

Name

The file name says what the file is, wherever it travels.
LAYER 3

Status

Suitability and revision say how far you can rely on it.
LAYER 4

Record

One register logs every container and every move between states.

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.

Layer 1 · The tree

P-XXX (template: 00.FOLDER-STRUCTURE\01.PROJECT-ROOT-TEMPLATE) ├─ 0.0 PIM │ ├─ 00.WIP one team, read-write │ │ ├─ 0.RVT ──── 00.ARC · 01.STR · 02.MEP · 03.LSC │ │ ├─ 1.DWG ──── (same 4) │ │ ├─ 2.RENDER ─ (same 4) │ │ ├─ 3.PSD │ │ ├─ 4.PPT │ │ ├─ 5.PHOTOS │ │ ├─ 6.IFC │ │ ├─ 7.NWC │ │ ├─ 8.NWD │ │ ├─ 9.PDF │ │ └─ 10.DATA │ ├─ 01.SHARED all teams read · IM writes │ │ ├─ 0.RVT … 10.DATA ── 00.ARC … 03.LSC same tree as WIP │ │ ├─ 20.REPORTS (planning · model health · clashes) │ │ ├─ 21.RECORD (register · transmittals in/out · log) │ │ ├─ 22.LIBRARY (title blocks · project families) │ │ └─ 23.DOCUMENTS (RFP · scope · standards · task team · kickoffs │ │ · BEP · classifications · QA-QC · LOIN · TIDP · MIDP) │ ├─ 02.PUBLISHED read-only │ │ └─ 00.SD … 07.U \ YYYY-MM-DD-DESCRIPTION │ │ ├─ 0.RVT … 10.DATA ── 00.ARC … 03.LSC │ │ └─ 99.TRANSMITTAL │ └─ 03.ARCHIVE read-only │ ├─ 00.SD … 07.U (superseded packs, same tree as PUBLISHED) │ └─ 99.LESSONS-LEARNED ├─ 0.1 ADMIN contract · fees · procurement · site ├─ 0.2 REG permits · submissions · RFI · MOMs ├─ 0.3 EI presentations · analytics └─ 0.4 DOCS brief · BOD · specs · specialists

What changes from BABOOM 12.1 today

  • The type list is one fixed list (0–10), the same in WIP, SHARED, PUBLISHED and ARCHIVE. A file keeps its place and only the state folder changes.
  • Numbers 0–10 are file types and 20–22 are functions, so a number never means two things.
  • A dated pack holds the same type tree, with 99.TRANSMITTAL at the end.
  • Max depth is 5 levels. Revit and Windows break near 260 characters, so a path budget of 180 characters is enforced.
  • No MISC, no personal folders, no backups.

Who can do what

StateReadWrite
WIPOwn task teamOwn task team
SHAREDAll project teamsInformation manager only
PUBLISHEDProject + recipientsNobody (append only)
ARCHIVEProjectNobody

Layer 2 · The name

PRJ01project-ORG01originator-ZZvolume-L01level-M3type-ARCrole-00001number

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.

Layer 3 · Status (how far you can rely on it)

WIP
S0 · P01.01, P01.02…
check →
SHARED
S1–S4 · P01
authorise →
PUBLISHED
A1… · C01
supersede →
ARCHIVE
history
CodeMeaningState
S0Work in progressWIP
S1Fit for coordinationSHARED
S2Fit for informationSHARED
S3Fit for review and commentSHARED
S4Fit for stage approvalSHARED
A1, A2…Authorised and accepted for a stagePUBLISHED
CRAs constructed recordPUBLISHED

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.

Layer 4 · The record

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 nameTypeRoleStateSuitabilityRevisionAuthorCheckerApproverDateTransmittalSHA-256
PRJ01-ORG01-ZZ-L01-M3-ARC-000010.RVTARCSHAREDS1P02…………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.

The checker that ties the layers

CheckFails when
Name grammarThe name breaks the D21 pattern or uses a code that is not on the list
Folder ↔ nameThe type or role code doesn't match the folder the file sits in
Folder ↔ registerA file in SHARED or PUBLISHED has no register row, or a row points to a missing file
Register ↔ stateThe suitability code doesn't belong to the folder's state (e.g. S0 in PUBLISHED)
IntegrityA PUBLISHED file's hash doesn't match its register row
HygieneA 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.

Based on ISO 19650-1 / -2 (CDE states, information containers), the UK BIM Framework guidance on the CDE (Guidance C) and on status/revision codes, and the BABOOM D02 12.1–12.3 and D21 pages. Once it is settled, this replaces the content of D02 12.1–12.3 in place.