DOCUMENT NAMING STRATEGY
All information in the PD Revit Template follows PROJECT DESIGN (IO) standards. the For one-page drawing naming strategy, please refer to free download E-5161 OnePage Naming Strategy
Table 1 - Information Container Identifier
| Project No | [1] | Originator | [1] | Functional Breakdown | [1] | Spatial Breakdown | [1] | Form | [1] | Discipline | [1] | Number | [2] | Title / Description |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| XXXX(XX) | - | XX(X) | - | XX | - | XX | - | X(X) | - | X | - | XXYYY | _ | Drawing |
The XX denotes the minimum number of characters for each field, the additional (XX) denotes the additional number of characters, up to the maximum number, for each field.
Note: Although BS EN ISO 19650-2 does not recommend a specific field length PD strategy follow the maximum field restrictions shown in Table 1
Standard delimiters should be used between fields to ensure correct interpretation of the information container ID by software applications.
- [1] Delimiter Hyphen-Minus (U+002D).
- [2] Delimiter Underscore (U+0332).
PROJECT IDENTIFIER
Table 2 - Project Identifier
| Code | Project |
|---|---|
| 8068 | ONE |
This is a single common project identifier, defined at the initiation of the project, to be used by all organizations to identify the project.
ORIGINATOR
Table 3 - Originator
| Code | Organisation Name |
|---|---|
| PD | PROJECT DESIGN (IO) LTD |
PROJECT FUNCTIONAL BREAKDOWN
In the UK National Annex to BS EN ISO 19650-2, Functional Breakdown refers to the decomposition of the facility into its primary operational functions—for example, splitting a hospital into departments like A&E, radiology, and maternity. It provides a logical way to organise information and model elements based on how the asset is used, not just how it’s built.
(Think of it as sorting by what things do, not just where they sit.)
Simultaneous Working
The project can be divided by function and space to allow simultaneous working in all interlocked spaces and information containers (models), and to standardise project drawing production.
Table 4 - Functional Breakdown
| Functional ID | Description |
|---|---|
| ZZ | All spaces/areas |
| XX | Space/Area not applicable |
| 99 | Site |
| Enter ID | |
| Add additional spaces/areas as required |
Functional Federation by Discipline
The Functional Breakdown refers to the decomposition of the facility into its primary operational functions, for example, splitting a hospital into departments like A&E, radiology, and maternity. It provides a logical way to organise information and model elements based on how the asset is used, not just how it’s built. The codes representing the Functional Breakdown must be established per project.for more information please download the Information Protocol from: https://projectdesign.io/downloads/information-protocol/
PROJECT SPATIAL BREAKDOWN
The task teams shall follow the agreed level identification strategy for the project, the two-character alphanumeric identifiers shown in Table 24 to be used.
Table 5 – Spatial Identifier
Identifier | Space ID |
ZZ | Multiple lecels/locations |
XX | No Level/location/space applicable |
B1 | Basement Level -1 |
00 | Base Level/Ground Floor |
01 | Level 01 |
M1 | Mezzanine between Level 1-2 |
RF | Roof Level |
FORM IDENTIFIER (ID)
The Form ID relates to a 2-character alphabetic identifier to identify the type of information held within the information container.
Identifiers defined for the project are shown in Table 25, please note the BS EN ISO 19650-2 NA 2021 Form Identifiers [*] are not used on this project and instead a project specific codes highlighted blue are to be used. The project specific codes are based on Uniclass 2015 FI Tables.
Table 6 - Form Identifier
| ID | Information Container Type |
|---|---|
| D* | Drawing (not used) |
| G* | Diagram (not used) |
| I* | Image (not used) |
| L* | List (not used) |
| M* | Model (not used) |
| T* | Textual (not used) |
| V* | Video/audio (not used) |
| AF | Animation file |
| AF | Animation file |
| AG | Agenda |
| AP | Application |
| BL | Brochure |
| BQ | Bill of quantities |
| CA | Calculations |
| CC | Contract |
| CD | Conversation record |
| CE | Certificate |
| CH | Chart |
| CM | Combined model |
| CO | Correspondence |
| CP | Cost plan |
| CR | Clash rendition |
| CT | Comment |
| DB | Database |
| DE | Diary entry |
| DG | Drawing (not used) |
| DR | Drawing rendition |
| DS | Data set |
| DT | Data sheet |
| DY | Directory |
| EM | |
| ES | Estimate |
| EW | Early warning notice |
| FM | Form |
| FN | File note |
| GU | Guide |
| HS | Health and safety |
| IE | Information exchange file |
| IM | Image |
| IN | Instruction |
| IV | Invoice |
| LF | Leaflet |
| LG | Log |
| LI | List |
| LT | Letter |
| M2 | Model - two-dimensional |
| M3 | Model - three-dimensional |
| MA | Manual |
| ME | Memo |
| MI | Minutes |
| MR | Model rendition |
| MS | Method statement |
| MX | Matrix |
| PC | Procedure |
| PE | Press release |
| PH | Photograph |
| PL | Plan |
| PO | Poster |
| PP | Presentation |
| PR | Programme |
| PS | Proposal |
| PT | Permit |
| PW | Process workflow |
| PY | Policy |
| PZ | Protocol |
| QN | Quotation |
| RD | Room data sheet |
| RG | Register |
| RI | Request |
| RN | Regulation |
| RP | Report |
| RQ | Requisition |
| SA | Schedule of accommodation |
| SC | Schematic |
| SD | Standard |
| SH | Schedule or table |
| SK | Sketch |
| SN | Snagging list |
| SO | Subcontract order |
| SP | Specification |
| ST | Study |
| SU | Survey |
| SW | Scope of works |
| SY | Strategy |
| TE | Template |
| TF | Technology file |
| TG | Training record |
| TL | Transmittal |
| TN | Transfer note |
| TQ | Technical query |
| TR | Test result |
| VA | Variation |
| VL | Valuation |
| VS | Visualization |
DISCIPLINE IDENTIFIER (ID)
The task teams shall use Discipline identifiers shown in Table 31.
Table 7 - Discipline Identifier
| ID | Role |
|---|---|
| A | architecture |
| B | building surveying |
| C | civil engineering |
| D | demolition/dismantling |
| E | electrical engineering |
| F | facilities/asset management |
| G | ground engineering |
| H | highways and transport engineering |
| I | Not used |
| K | Not used |
| L | landscape architecture |
| M | mechanical engineering |
| O | other discipline |
| P | public health engineering |
| Q | quantity surveying / cost consultancy |
| R | project management |
| S | structural engineering |
| T | town and country planning and building control |
| W | water engineering |
| X | non-discipline specific or not applicable |
| Y | topographical surveying |
| Z | multiple disciplines |
DRAWING NUMBER - FIVE-DIGIT NUMBER (XXYYY)
The five-digit drawing number appended to every sheet consists of two parts:
- XX – Series prefix identifies the type of view (overall plan, schematic, detail, etc.) and always follows the master table.
- YYY – System sequence is split into Y = system group and YY = running sequence inside that group.
Put together, they create a compact, machine-sortable code—for example “60100”:
- 60 → Schedules & Diagrams (schematic)
- 1 → System group “Lighting & Lighting Control”
- 00 → First schematic in that group
Important: the full code range is 001-999 inside each series; “000” is reserved and must never be used.
With that context in mind, the detailed rules for XX and YYY are set out below.
Series prefix (XX)
The first two digits[1]:
Table 8 – Series prefix XX
| XX | Sheet type | Typical use in MEP |
|---|---|---|
| 00 | General | Legends, notes, symbols |
| 05 | Large-scale views | Non-detailed plan/elevation/section |
| 10 | Overall plan/layout | Combined-level plans |
| 11 | Part plan | Single-zone plans |
| 12 | Area plan | Zone/sector key plans |
| 15 | Overall RCP | Lighting / services ceilings |
| 16 | Part RCP | Zoned RCPs |
| 20 | Overall elevations | Internal / façade elevations |
| 30 | Overall sections | Building sections |
| 31 | Part sections | Local cut-throughs |
| 40 | User-defined | Spare |
| 50 | Details | Enlarged junctions, schematics if on detail sheets |
| 60 | Schedules & diagrams | All single-line schematics |
| 70 | User-defined | Typical details, mock-ups |
| 80 | User-defined | Reserved – For PD Dashboards, Cover Sheets, Presentations etc, |
| 90 | 3-D | 3-D, perspectives |
Rule – numbering runs 001-999 inside every XX block; 000 is permanently banned.
System sequence (YYY)
System digit Y (first digit of YYY)
Table 9 - digit Y (first digit of YYY)
| Y | System group | System cross-reference |
|---|---|---|
| 1 | Lighting & lighting control | 708033 / 757054 |
| 2 | LV power, small power & data | 703045 / 703080 |
| 3 | Cable containment | 703010 |
| 4 | Fire detection & alarm | 755028 |
| 5 | Security (access, CCTV, intruder) | 754000 |
| 6 | Nurse call & medical locations | 755011 |
| 7 | Earthing, bonding & lightning | 703025 |
| 8 | BWIC / service penetrations | 256030 |
| 9 | Combined-services coordination | 403518 |
| 0 | Reserved (not used) | not used |
The six-digit code is stored in Revit parameters and view-template names; it is not embedded in the sheet number, the numbers are based on the Uniclass “Ss” system codes used here without the prefix and delimiters
Sequence YY (second & third digits of YYY)
Table 10 - second & third digits of YYY
| YY range | Usage guideline |
|---|---|
| 00-09 | Schematic drawings |
| 10-29 | Primary layouts (overall or zone) |
| 30-49 | Secondary/alternate layouts (emergency, low-level, etc.) |
| 50-59 | Security-specific schematics |
| 60-69 | Spare |
| 70-79 | Specialist or tertiary layouts |
| 80-89 | Spare |
| 90-99 | Coordination / multidisciplinary views |
If you need more than one drawing in any band, increment by +1 (e.g. 10111, 10112, …).
Worked examples
The shortened Sheet number is shown here only the Discipline ID and Five Digit Number.
For a more detailed one-page drawing naming strategy, please refer to Appendix A.
Table 11 - Worked examples
| PD(Uniclass) system | Sheet number | Title (truncated) | Meaning |
|---|---|---|---|
| 757054_Lighting control | E-60100 | Lighting Control Schematic | Schematic (60) system (1) seq. (00) |
| 708033_Lighting | E-10111 | Lighting Layout L00 | Overall plan (10) system (1) seq. (11) |
| 708033_Emergency lighting | E-10131 | Emergency Lighting Layout | Overall plan (10) system (1) seq. (31) |
| 703045_LV distribution | E-60200 | LV Riser Schematic | Schematic (60) system (2) seq. (00) |
| 703080_Small power & data | E-10211 | Small Power & Data GA | Plan (10) system (2) seq. (11) |
| 703010_Containment – HL | E-10311 | High-Level Containment | Plan (10) system (3) seq. (11) |
| 703025_Lightning protection | E-10731 | Lightning Protection Layout | Plan (10) system (7) seq. (31) |
| 403518 Coordination RCP | E-15931 | Services Coord. RCP L01 | RCP (15) system (9) seq. (31) |
(Full file name example) 8068-PD-XX-GF-DR-E-10111_Lighting layout
Modeller’s checklist
- Assign the correct System cross-reference (six digits) to every view template and Revit view.
- Choose the XX series that matches the view type.
- Pick Y according to the system group
- Assign YY from the sequence bands.
- Never use YYY = 000.
- Underscore separates the drawing code from the human readable title; no other special characters.
Follow the steps above and the drawing list will self-sort, QA scripts will pass, and every stakeholder will know exactly what they’re looking at.
[1] The numbering system is based on Red Sea Global numbering system
METADATA
The project template has been set up to allow the use of the status, revision and classification attributes as metadata, the attributes used on this project have been based on Table NA.1 of the BS EN ISO 19650-2:2018.
The codes used on this project are shown in Table 31, revisions should be two integers, prefixed with the letter ‘P’, e.g. P01. Information containers in the ‘work in progress’ state should also have a two-integer suffix to identify the version of the preliminary revision, e.g. P02.05.
All Contractual revisions of information containers should be two integers, prefixed with the letter ‘C’, e.g. C01.
STATUS AND USE
| Status Code | Used For | Action by |
|---|---|---|
| Information State (at any project stage): Work in progress (WIP) | ||
| S0 | Information developed within a task team | [C], [B]* |
| Information State (at any project stage): Shared (non-contractual) | ||
| S1 | coordination | [B], [C] |
| S2 | information/reference | [A], [B], [C] |
| S3 | review and comment | [B] |
| S4 | review and authorization | [B] |
| S5 | review and acceptance | [A] |
| Information State (at handover stage 6): Published [1] (contractual) | ||
| A1, An [2] | authorisation or acceptance | [A], [B] |
| B1, Bn | partial-authorisation or acceptance | [A], [B] |
| Action by: [A] Appointing Party, [B] Lead Appointed Party, [C] Appointed Party, [B]* internal LAP process | ||
| [1] A published status code indicates sign-off by either the lead appointed party or the appointing party but did not describe why the information container has been issued—the reasons for issue An status code shall be defined in the project's information standard. | ||
| [2] Examples of the use of status code An | ||
| A0 - BS 8536-2 2016 Work Stage 0 - Strategy, or RIBA [3] Stage 0 - Strategic Definition A1 - BS 8536-2 2016 Work Stage 1 - Brief, or RIBA [3] Stage 1 - Preparation and Briefing A2 - BS 8536-2 2016 Work Stage 2 - Concept, or RIBA [3] Stage 2 - Concept Design A3 - BS 8536-2 2016 Work Stage 3 - Definition, or RIBA [3] Stage 3 - Spatial Coordination A4 - BS 8536-2 2016 Work Stage 4 - Design, or RIBA [3] Stage 4 - Technical Design A4 = information container Authorised and Accepted as suitable for construction A5 - BS 8536-2 2016 Work Stage 5 - Construct and commission, or RIBA [3] Stage 5 - Manufacturing and Construction A5 = Authorized and accepted as suitable as a construction record A6 - BS 8536-2 2016 Work Stage 6 - Handover and Closeout, or RIBA [3] Stage 6 - Handover A7 - BS 8536-2 2016 Work Stage 7 - Operation and End of Life, or RIBA [3] Stage 7 - Use | ||
| [3] RIBA Plan of Work 2020 |
DESCRIPTION
The descriptive text used to aid information container recognition can be used but shall be kept to a minimum, the description should not include information already defined in the other fields, and it shall remain the same on all revisions. To allow human recognition and ease management of information containers outside of CDE, each shared and published information container shall include status and revision reference at the end of description, the revision shall be separated by an underscore.
