BBM-STD-93-CODE_DICTIONARY-V0.2 | Office standard | 5 November 2026 | V0.2 | Private controlled WIP draft for office review
| Version | Date | Change |
|---|---|---|
| V0.1 | 2026-11-04 | First issue: closes rows,,,,,, §1.3 "Single code dictionary" and the §1.4 contradictions on discipline/role codes, suitability codes, gate outcome, review tiers, gate list and approval status vocabulary (104, 107, 108, 109, 110, 113) + cross-doc pointer pass (gate map to the eight Manual §2.1 gates and BBM-STD-12 C5 short form, trade-alias map incl. DU/WU -> C/CIV per, ISO 13567 agent code, Superseded aligned with BBM-STD-12 C4) + template alignment (..148) + folder names without dots |
| V0.2 | 2026-11-05 | §2.2 container-name token lists CLIENT, ORG, PROJ, VOLUME, LEVEL, TYPE with patterns, office rules and validity; §2.3 QMS checklist workbook codes |
1 Purpose and authority#
This is the ONE office code dictionary. It replaces the code lists in BBM-STD-51 §4 (ROLE and suitability rows), BBM-STD-66 §1 (discipline designators), and Manual V0.5 §12.1 (folder discipline codes) and §12.3 (view and sheet discipline tokens); BBM-STD-50 and BBM-STD-68 use these codes. Those documents keep a pointer to this dictionary and, where needed, the local subset they use; they define no code of their own. The BIM Manager maintains this dictionary; a new code or meaning needs a ChangeID in BBM-STD-51 and a revision here.
Codes in this document are office codes. When a client or authority imposes another code set, the project records a one-to-one mapping in the BEP using the mapping columns below; issued literals are never renamed.
2 Discipline and role codes#
| Discipline | 3-letter code (views, folders, clash sets, QA, issue tracker) | 1-letter ROLE (file names, sheet prefix) | Folder code | Sheet prefix | Issue-tracker value | When a client imposes the UK National Annex role codes |
|---|---|---|---|---|---|---|
| Architecture | ARC | A | 00-ARC | A | ARC | A |
| Structure | STR | S | 01-STR | S | STR | S |
| Mechanical | MEC | M | 02-MEC | M | MEC | M |
| Electrical | ELE | E | 03-ELE | E | ELE | E |
| Landscape | LSC | L | 04-LSC | L | LSC | L |
| Plumbing / public health | PLU | P | 05-PLU | P | PLU | P |
| Fire & Life Safety | FLS | F | 06-FLS | F | FLS | Y (specialist designer): in the UK National Annex "F" means facilities manager, so FLS is not sent as F |
| Interiors | INT | I | 07-INT | I | INT | I |
| Civil | CIV | C | 08-CIV | C | CIV | C |
| Survey | SUR | G | 09-SUR | G | SUR | G |
| Cost / quantities | QTY | Q | 10-QTY | Q | QTY | Q |
| Contractor | CON | W | 11-CON | W | CON | W |
| General / multi-discipline | GEN | Z | 12-GEN | Z | GEN | Z |
Rules:
- Published library family names keep their own tokens (BBM-STD-69 §2): the G in title blocks BBM-G-TTB-A0…A3 is the library's general token, not the Survey ROLE G.
- LSC = Landscape and FLS = Fire & Life Safety everywhere. "LSC: Life Safety and Code" is wrong and is not used.
- Extra disciplines are added per project at the next free code (next free 3-letter code, 1-letter ROLE not yet used in the table, next folder number), recorded here before first use.
- The UK National Annex column is a mapping for appointments that impose it; letters other than FLS are sent unchanged, checked against the client's annex code list at appointment.
- Legacy aliases map one-to-one and are not used for new work: MECH → MEC; ELEC (view root and folder 03-ELEC) → ELE / 03-ELE; LND → LSC; ID → INT; "MEP" is an umbrella label for MEC + ELE + PLU, not a code; a legacy MEP view root maps to MEC, ELE or PLU per view content.
- Folder numbers 00–04 keep the existing project folder order; 05–12 are allocated by this dictionary. The table lists disciplines in folder-number order.
- Folder codes are written NN-CODE with a hyphen, never a dot. They sit, with the same numbers in the same order, under every data type in every state of the one project folder tree in Manual V0.5 §12.1.
- File names: the 8-token external identity CLIENT-ORG-PROJ-VOLUME-LEVEL-TYPE-ROLE-NUMBER.ext uses the 1-letter ROLE. View names DISC-LEVEL[-ZONE]-TYPE-DESC use the 3-letter code (e.g. ARC-L02-PLAN-LAYOUTS, MEC-Z03-3D-COORD). Sheet numbers DISC-CAT-INDEX use the sheet prefix.
- ISO 13567 agent responsible (2 characters, BBM-STD-66 §1.1 export mapping): the 1-letter ROLE followed by a hyphen (e.g. "A-", "F-"), unless the recipient's mapping table defines other values.
2.1 Clash trade aliases#
The BBM-STD-50 office trade codes are selection aliases, not ROLE codes. Each maps to exactly one code here; the selection scope of each trade stays in BBM-STD-50 §4.
| Trade alias | Meaning | ROLE | 3-letter code |
|---|---|---|---|
| AR | Architecture | A | ARC |
| ID | Interiors | I | INT |
| ST | Structure | S | STR |
| ME | Mechanical | M | MEC |
| EL | Electrical | E | ELE |
| LI | Lighting | E | ELE |
| WS | Water services | P | PLU |
| DR | Drainage | P | PLU |
| FF | Fire protection | F | FLS |
| LS | Landscape | L | LSC |
| CI | Civil | C | CIV |
| DU | Dry utilities (external networks) | C | CIV |
| WU | Wet utilities (external networks) | C | CIV |
DU and WU are external utility networks and take the civil role C / CIV. Where a building-services team produces a utility network, the project annex records the override against this table. A new trade alias needs a row here before it is used in a clash set.
2.2 Container name tokens#
The external container name CLIENT-ORG-PROJ-VOLUME-LEVEL-TYPE-ROLE-NUMBER.ext (Manual V0.6 §12.3) takes its token values from these lists. The information manager records every allocated value in the project naming register at mobilisation. Each token is valid from mobilisation (the first container, Stage 0/1); a value is never changed or reused after first issue (the principle). A client- or authority-imposed list replaces a token list for that project through a one-to-one mapping in the BEP. Examples are synthetic.
| Token | Pattern | Office rule | Example |
|---|---|---|---|
| CLIENT | ^[A-Z0-9]{2,6}$ | The client's own code where the appointment gives one; otherwise three letters allocated at mobilisation from the client's registered name, unique in the office project register | CLI |
| ORG | ^[A-Z0-9]{2,6}$ | Originator of the container. This office is BABOOM (the office prefix of every BBM-STD document and of the published library series); every other appointed party gets one code in the project naming register | BABOOM |
| PROJ | ^[A-Z0-9]{2,6}$ | The client's project code where given; otherwise the office job number P001–P999 from the office project register, never reused | P001 |
| VOLUME | ZZ, XX or [0-9]{2} | ZZ = all volumes / whole project; XX = no volume applies; 01–99 = a building, block, zone or system listed with its name in the project volume register | 01 |
| LEVEL | ZZ, XX, GF, RF, [0-9]{2}, B[0-9]{1,2} or M[0-9]{1,2} | ZZ = multiple levels; XX = no level applies; GF = ground; 01–99 = floors above ground; B1, B2 … = basements; M1, M2 … = mezzanines; RF = roof. Each value is listed with its Revit level name and elevation in the project level register. The view LEVEL token (L01, LRF, ALL) is a separate grammar | 03 |
| TYPE | ^[A-Z0-9]{2}$, from the list below | Information type of the container. A new type needs a row here before use | M3 |
| ROLE | ^[ASMEPFLICGQWZ]$ | §2 | A |
| NUMBER | ^[0-9]{4}$ | Sequence per CLIENT-ORG-PROJ-VOLUME-LEVEL-TYPE-ROLE, from 0001, never reused | 0001 |
Validator regexes: VOLUME ^(ZZ|XX|[0-9]{2})$; LEVEL ^(ZZ|XX|GF|RF|[0-9]{2}|B[0-9]{1,2}|M[0-9]{1,2})$; CLIENT, ORG and PROJ ^[A-Z0-9]{2,6}$. The Manual §12.3 container regex checks lengths; these lists check values.
Information types (UK National Annex information-type list via the IMI Framework, adopted as office list):
| Code | Information type | Code | Information type |
|---|---|---|---|
| AF | Animation | MI | Minutes / action notes |
| BQ | Bill of quantities | MR | Model rendition |
| CA | Calculations | MS | Method statement |
| CM | Combined (federated) model | PP | Presentation |
| CO | Correspondence | PR | Programme |
| CP | Cost plan | RD | Room data sheet |
| CR | Clash rendition | RI | Request for information |
| DB | Database | RP | Report |
| DR | 2D drawing | SA | Schedule of accommodation |
| FN | File note | SH | Schedule |
| HS | Health and safety | SN | Snagging list |
| IE | Information exchange file (e.g. COBie) | SP | Specification |
| M2 | 2D model | SU | Survey |
| M3 | 3D model | VS | Visualisation |
Example container name (synthetic): CLI-BBM-P001-01-03-M3-A-0001.ifc.
2.3 QMS checklist workbook codes#
Checklist IDs read <workbook>-<sheet>-<nn>. The workbook codes and their folders in 07-QA-QC:
| Code | Workbook | Folder | Procedure owner |
|---|---|---|---|
| DR | Design review | 02-DESIGN-REVIEW | BBM-STD-97 QP-03 / QP-04 |
| PR | Proposals | 03-PROPOSALS | BBM-STD-97 |
| SP | Specifications | 04-SPECIFICATIONS | BBM-STD-97 |
| SU | Sustainability | 05-SUSTAINABILITY | BBM-STD-97 |
| SB | Authority submissions | 06-SUBMISSIONS | BBM-STD-97 |
| SV | Site supervision | 07-SUPERVISION | BBM-STD-97 |
| DC | Document control | 08-DOCUMENT-CONTROL | BBM-STD-97 |
| QA | QMS audit | 09-AUDIT | BBM-STD-96 |
The BIM checklist in 01-BIM (BBM-STD-68) keeps its sheet prefixes MH, IC, DS, DI, AR, ID, LS, ST, ME, AU and IS. SU here is a workbook code, never a suitability code (SU-…, §3).
3 Suitability codes#
Office suitability codes are SU-WIP, SU-COORD, SU-INFO, SU-REVIEW and SU-ISSUE only. "S1"-style codes are not office suitability codes (in this office "S1" is issue severity, §8).
| Office code | Meaning | CDE state where used | Maps to UK National Annex code when a client imposes it |
|---|---|---|---|
| SU-WIP | Team work in progress | WIP | S0 |
| SU-COORD | Shared for coordination | Shared | S1 |
| SU-INFO | Shared for information / reference | Shared | S2 |
| SU-REVIEW | Shared for review and comment, or submitted for stage, PIM or AIM authorisation | Shared | S3; S4 when the client's annex calls the purpose stage approval; S6 / S7 when submitted for PIM / AIM authorisation |
| SU-ISSUE | Authorised for the defined use (tender, construction, record) | Published | A1…An (authorised and accepted) or B1…Bn (partially authorised, with comments) per the recipient's decision; CR for an as-constructed record |
The meaning of each UK National Annex code is taken from the edition named in the client's appointment, checked at appointment and recorded in the BEP. SU-ISSUE does not prove statutory approval or recipient acceptance.
Revision forms: office revisions are per container, R00 initial WIP, then R01, R02 onward; never recycled; an unchanged container keeps its revision; no pack-wide monotonic revision. When a client imposes the UK National Annex forms, the project alias table maps each office revision to the client form (preliminary P-series for Shared, contractual C-series for Published, with any sub-version form the client specifies); the mapping is recorded once and never recalculated.
4 CDE states#
| State | Meaning |
|---|---|
| WIP | Work in progress inside the task team |
| Shared | Checked and shared with other task teams or the appointing party for the stated suitability |
| Published | Authorised for use; formal delivery is the transition to Published after authorisation |
| Archive | Retained record of superseded or completed information (one spelling: Archive, folder 04-ARCHIVE) |
Each state has one state folder in the project folder tree: 01-WIP, 02-SHARED, 03-PUBLISHED, 04-ARCHIVE (Manual V0.5 §12.1). A folder location alone does not prove the state, and the state is distinct from the suitability code.
5 Gate outcomes#
| Letter | Meaning |
|---|---|
| A | Accepted for the stated purpose without required changes |
| B | Accepted for the stated purpose with listed non-blocking comments, owners and dates; B cannot cover a mandatory failure |
| C | Rejected: revise and resubmit; affected use held |
Gate outcomes are letters A/B/C everywhere (meaning per Glossary V0.3 §1.5). The wording "gate decisions are words" is retired. Each outcome records scope, actual acceptor, authority, evidence and permitted use.
6 Gate families#
Three gate families exist. They are different decisions and are never merged; the table shows their typical alignment, and each project records its actual alignment in the BEP.
| Office stage gate (Manual V0.5 §2.1, eight gates) | Basis-of-design gate (BBM-STD-12 C5) | Authority gate (BBM-STD-57 §4) |
|---|---|---|
| Strategic Need / Business Case (RIBA 0) | G0 Basis | none |
| Brief / Information Requirements Approval (RIBA 1) | G0 Basis | none |
| Concept Design Approval (RIBA 2) | G1 Concept/planning | Concept / planning |
| Coordination Freeze (RIBA 3) | G2 Permit/start activity (package preparation) | Permit / final design (preparation) |
| Issue for Review (RIBA 4) | G2 Permit/start activity (submission) | Permit / final design |
| Verified Construction Information Exchange (RIBA 5, procurement-dependent) | G3 Construction | Construction activity |
| Handover Data Acceptance (RIBA 6) | G4 Completion/occupancy | Completion / operation |
| Operational Trigger / AIM Update Acceptance (RIBA 7) | G5 Use/renewal (e.g. Dubai Law 3/2026 quality and safety certificate) | none (owner renewal routes, BBM-STD-85) |
Short form used in BBM-STD-12 C5: G1 = Concept/planning, G2 = Permit/final design, G3 = Construction activity, G4 = Completion/operation; G0 and G5 have no authority-gate equivalent.
Every gate outcome in all three families is a letter A/B/C (§5). Authority gates also record the authority's approval status (§7); an A/B/C outcome never replaces or proves an authority approval.
7 Approval status vocabulary#
The BBM-STD-57 §2/§4 set is canonical. BBM-STD-12 C4 statuses are detail values that map to it.
| Canonical status (BBM-STD-57) | BBM-STD-12 C4 statuses mapped to it | Rule |
|---|---|---|
| Unverified | Pending screening | Applicability not yet established; silence is not exemption |
| Planned | Not started; In preparation | No submission made |
| Submitted | Submitted; Under review | Needs the actual receipt or application number |
| Conditionally approved | Approved with conditions | Activity released only when the relevant conditions are checked closed |
| Approved | Approved | Needs the authority's exact decision and scope |
| Rejected | Rejected; Revise/resubmit | Resubmission is a new submission record linked to the rejected one |
| Expired | Expired; Superseded | Revalidation trigger recorded. Superseded = no longer valid because a later submission replaced it; keep the Superseded flag and link to the replacing record |
One C4 value is not an approval status: Not applicable is an applicability decision in the BBM-STD-57 §2 Codes table (needs signed reason and authority).
8 Review tiers and issue severity#
| Tier | Scope |
|---|---|
| L1 | Discipline review inside the task team |
| L2 | Cross-discipline review (coordination) |
| L3 | Committee review (design/quality committee) |
The BIM Manager is a role, not a tier. Issue severity (BBM-STD-50 §7) is separate: S1 Critical, S2 Major, S3 Minor. S codes are severity, SU codes are suitability, A/B/C are gate outcomes, L1–L3 are review tiers; none is a RACI letter.
9 Acceptance#
| Check | Evidence |
|---|---|
| One dictionary | 51, 66, Manual, 50, 68 carry a pointer to this document and no competing list |
| Validation | File-name, view-name, sheet and folder validators read their code lists from this dictionary's current revision |
| Project mappings | Every client-imposed code set has a one-to-one mapping in the BEP |
References#
- ISO 19650-1:2018 (information states and suitability concepts): https://committee.iso.org/standard/68078.html, checked 2026-11-04.
- ISO 19650-2:2018 (delivery phase; formal delivery, authorisation and acceptance): https://committee.iso.org/standard/68080.html, checked 2026-11-04.
- IMI Framework (formerly UK BIM Framework, renamed May 2025), resources including the Information Protocol template for BS EN ISO 19650-2 (Ed 6) and the UK National Annex code context: https://ukbimframework.org/resources/, checked 2026-11-04.
- Office sources mapped: Manual V0.5 §2.1, §12.1, §12.3; Glossary V0.3 §1.5; BBM-STD-12 V0.2 C4, C5; BBM-STD-50 V0.3 §2, §7; BBM-STD-51 V0.2 §4; BBM-STD-57 V0.2 §2, §4; BBM-STD-66 V0.2 §1; BEP V0.5.