Naming
How files, models, sheets, views, objects and families are named: the rules of the BIM Execution Plan and the shared naming register, in one place.
BBMOffice-ARCDiscipline-DORCategory-DOORS-EXTSGL-LOUVREWhat it is-v01VersionBBMOffice-GENAll disciplines-TMPTemplate-R23Revit 2023-REV05RevisionFrom BBM-STD-10 Office BIM Execution Plan
8.3 Naming conventions#
8.3.1 Document naming convention#
Use a single approved Project Naming Register shared with BBM-STD-01-MANUAL-V0.5 §3.1. External containers use the 8-token CLIENT-ORG-PROJ-VOLUME-LEVEL-TYPE-ROLE-NUMBER.ext grammar (re-affirming); ORG-PROJ-DISC-PHASE-SEQUENCE survives only as a mapped internal WIP alias that is never issued, and the PHASE token is retired. Neither grammar is universally prescribed by ISO. Binding appointment/EIR requirements govern project exchanges within the signed hierarchy. Do not impose two grammars or rename historical issues.
Decision (BIM Manager, 2026-10-14): Use CLIENT-ORG-PROJ-VOLUME-LEVEL-TYPE-ROLE-NUMBER.ext when an appointment supplies no grammar; retain internal Rnn revisions and the suitability list below. Basis: Adopts the Manual/BEP external candidate and existing Rnn convention consistently; appointment requirements take precedence through one recorded mapping G-C. Authority: Clash matrix section 2, the shared naming/revision/suitability list.
The PHASE token is retired. "IFC" never abbreviates construction issue; .ifc remains a format, not construction permission.
| Token / control | Recommended value / example | Validation / required project record |
|---|---|---|
| CLIENT / ORG / PROJ | CLI / OFF / P001 in synthetic examples | Approved code lists and immutable project/appointment identity |
| VOLUME / LEVEL | ZZ / ZZ for whole model only where adopted | Project spatial division and no overlapping scope |
| TYPE / ROLE / NUMBER | M3 / A / 0001 for synthetic architectural model | Controlled document/type code list; 1-letter ROLE from BBM-STD-93-CODE_DICTIONARY-V0.1; unique number namespace |
| Valid synthetic example | CLI-OFF-P001-ZZ-ZZ-M3-A-0001.ifc | Correct tokens + actual schema/profile and metadata checks |
| Invalid example | CLI-OFF-P001-ZZ-M3-A-0001.ifc | Reject missing LEVEL; no implicit token shift |
| Internal aliases | Decision (BIM Manager, 2026-10-14): Retain ORG-PROJ-DISC-PHASE-SEQUENCE only for approved legacy internal WIP aliases with one external identity mapping; retire PHASE from external identity and keep purpose/status as metadata; preserve historic issued names. Basis: One external identity prevents parallel grammars and IFC format/purpose ambiguity G-C. | One mapping to external container ID; preserve historic issues |
| Views / sheets | Decision (BIM Manager, 2026-10-14): Use DISC-LEVEL[-ZONE]-TYPE-DESC for views and DISC-CAT-INDEX for sheet numbers, with separate readable title and revision; register Start View/library exceptions and validate codes. Basis: Retains the shared Manual/BEP convention while separating display from identity S35, G-C. | Same Manual 3.1/12.3 baseline; Start View/library exceptions registered |
| Revision / suitability | Decision (BIM Manager, 2026-10-14): Use R00 for initial WIP, then R01, R02 and never-recycled per-container revisions, expanding digits beyond R99; unchanged containers retain their actual revision; appointment codes override through one approved mapping. Basis: Carries forward O3 Rnn without forcing equal revisions on unchanged content G-C. Decision (BIM Manager, 2026-10-14): Use local SU-WIP = team work, SU-COORD = coordination, SU-INFO = reference, SU-REVIEW = formal review, SU-ISSUE = authorised defined use; record permitted use and recipient acceptance separately; map appointment codes in one register. Basis: The O3 list prevents confusion with S1/S2/S3 severity and RACI G-C, S04. | Revision sequence per changed container; unchanged issue revisions retained |
| Migration | Prior ID → new ID, reason, approver, affected links and effective date | Authorised future issue only; original identity/history retained |
| Register approval | Decision (BIM Manager, 2026-10-14): The project IM maintains one naming/code register, approved by LAP/recipient within appointment powers; validate eight uppercase hyphen-separated tokens, registered volume/level/type/role, four-digit NUMBER and lowercase approved extension; use ISO 8601 dates. Basis: Syntax, dictionaries, uniqueness and permitted use must agree across documents G-C. | Same register ID/revision referenced in BEP and Manual annex |
Decision (BIM Manager, 2026-10-14): The project IM maintains one naming/code register, approved by LAP/recipient within appointment powers; validate eight uppercase hyphen-separated tokens, registered volume/level/type/role, four-digit NUMBER and lowercase approved extension; use ISO 8601 dates. Basis: Syntax, dictionaries, uniqueness and permitted use must agree across documents G-C.
Regex alone is insufficient; dates do not automatically supersede an issue.
8.3.2 System naming convention#
| XX | XX | XXX | XXX | XXX | XXX | XXX |
|---|---|---|---|---|---|---|
| ORIGINATOR | DISCIPLINE | SUB-DISCIPLINE | SYSTEM TYPE | DESCRIPTION | DATA | DATA |
| REQUIRED | REQUIRED | REQUIRED | REQUIRED | REQUIRED | OPTIONAL | OPTIONAL |
8.3.3 Object naming convention#
The system/object tables are legacy internal authoring/library grammars, not alternative external container patterns. Register category/type abbreviations, permitted descriptors and immutable library version separately. Global/system control parameters differ from asset identity; avoid introducing a new live file ID from a family name.
| XX | XX | XXX | XXX | XXX | XXX | XXX |
|---|---|---|---|---|---|---|
| ORIGINATOR | DISCIPLINE | REVIT CATEGORY | DESCRIPTION | DATA | DATA | DATA |
| REQUIRED | REQUIRED | REQUIRED | REQUIRED | OPTIONAL | OPTIONAL | OPTIONAL |
8.3.4 Naming convention general ref#
Code lists are held once: discipline/role, suitability and gate codes in BBM-STD-93-CODE_DICTIONARY-V0.1; project volume, level and type codes in the Project Naming Register (8.3.1). This BEP keeps no separate code table.
From BBM-STD-51 Office standards register naming and rights
4 Shared naming and metadata register#
Retain O3-POL-01 in Clash Matrix section 2 and BEP 8.3 as the existing policy authority. This table implements that decision, rather than establishing another grammar. Register one appointment mapping when the recipient requires different tokens or codes. The eight-token external identity is CLIENT-ORG-PROJ-VOLUME-LEVEL-TYPE-ROLE-NUMBER.ext. Tokens are uppercase, separated by single hyphens; NUMBER has four digits; the approved extension is lowercase. Revision and suitability are metadata.
Code values live in one place: BBM-STD-93 Code dictionary. This section keeps only the token order and validation rules. Short summary for orientation; BBM-STD-93 governs where they differ:
| Token / metadata | Rule (values in BBM-STD-93) |
|---|---|
| CLIENT / ORG / PROJ | Allocated project lists; fictional example CLI / OFF / P001, never a client identity |
| VOLUME / LEVEL | Registered zone and level codes; ZZ only where whole scope is explicitly adopted; never omit a token |
| TYPE | Registered container type codes (e.g. M3 model, DR drawing) |
| ROLE | One-letter ROLE from BBM-STD-93 (A, S, M, E, L, P, F, I, C, G, Q, W, Z). A trade alias is not a role code |
| NUMBER | Four digits, unique in the recorded numbering namespace |
| Extension | Lowercase; same-stem variants map to one logical container and declared source revision |
| Revision | R00 initial WIP, then R01, R02…, expanding beyond R99; per container, never recycled; unchanged containers keep their revision |
| Suitability | SU-WIP, SU-COORD, SU-INFO, SU-REVIEW, SU-ISSUE only; mapping to UK National Annex S0–S7/A/B/CR in BBM-STD-93 |
| CDE state | WIP, Shared, Published, Archive. Distinct from workspace WIP/PRODUCTION/DEPLOYED folders |
| Release evidence | Exact identity/revision, source/export manifest, permitted use, author/checker/authoriser, recipients and separate receiving decision |
These SU codes are local. They are not ISO/national-annex suitability codes, issue severities or RACI letters. SU-ISSUE does not prove statutory approval or recipient acceptance. An.ifc extension does not mean issued for construction.
CAD, Revit and CDE use the same external register. Retain internal view names DISC-LEVEL[-ZONE]-TYPE-DESC (3-letter discipline code from BBM-STD-93), sheet numbers DISC-CAT-INDEX (1-letter ROLE prefix from BBM-STD-93) and the registered STD00-STARTING-VIEW exception under Manual 12.3/BEP 8.3. Preserve approved legacy WIP aliases through a one-to-one alias-to-external-ID map. Never rename issued records to clean up a convention.
4.1 Validation fixtures#
The workbook Test pack specifies positive and adverse cases for a future CAD/Revit/CDE validation implementation. Expected outcomes below are test specifications, not executed host evidence.
| Case | Input | Expected result and reason |
|---|---|---|
| N01 | CLI-OFF-P001-Z01-L01-M3-A-0001.ifc | Accept syntax and dictionary membership when manifest/revision/permission checks also pass |
| N02 | CLI-OFF-P001-Z01-M3-A-0001.ifc | Reject missing LEVEL; no token shift |
| N03 | CLI-OFF-P001-Z01-L01-M3-A-001.ifc | Reject sequence width |
| N04 | CLI-OFF-P001-Z01-L01-M3-A-0001-R01.ifc | Reject revision embedded in external identity |
| N05 | CLI-OFF-P001-Z99-L01-M3-A-0001.ifc | Reject unregistered volume even when a regex matches |
| N06 | Same container and revision, conflicting payload hashes | Reject unrecorded overwrite; investigate source/history |
| N07 | Same stem.rvt and.ifc, same manifest source | Permit declared representations; still test schema and receiver |
| N08 | Revision R02 followed by R01 as new issue | Reject regression unless expressly retrieving retained historical evidence |
| N09 | SU-COORD requested for fabrication | Hold incompatible intended use; naming alone cannot authorise it |
| D01 | Consumer points to an absent dependency ID | Reject release until allocation/source is resolved |
| D02 | Consumer pins old issue, master now newer | Preserve issued pin; assess migration rather than silently upgrade |
A validator checks lexical syntax, code dictionaries, identity/representation uniqueness, metadata, revision history, dependency resolution and intended-use authority separately. Regex alone is insufficient. A future implementation must run every case in all affected tools and record exact versions and actual outputs before claiming enforcement.