A comprehensive guide to information container naming conventions in BIM projects, ranging from the international standard ISO 19650 to the Vietnamese legal framework under the TCVN 14177:2024 series issued by the Ministry of Construction.
1. Why is a File Naming Convention Necessary in BIM Projects?
In a BIM project environment, thousands of files are generated by various stakeholders – architects, structural engineers, MEP engineers, and contractors. If each party names files according to their own conventions, searching, exchanging, and controlling document versions becomes chaotic.
ISO 19650 addresses this by defining the concept of an “information container” – any named set of data within a storage system, from Revit files to PDF drawings or Excel spreadsheets. Each container requires a unique and meaningful identifier, independent of its folder location.
Core Principle: The file name must carry sufficient information to identify the content without needing to open the file or understand the folder structure. This is a mandatory requirement for BIM Level 2 and above.
2. Naming Structure According to ISO 19650
ISO 19650 specifies a naming structure consisting of fields separated by hyphens (-). Hyphens are used strictly as field delimiters; within a single field, underscores (_) are used if necessary.
Standard Identifier String: PROJ – ORIG – FUNC – LOC – TYPE – ROLE – NUM – REV
| Field | Name | Description / Notes |
| PROJ | Project Code | 2–6 characters, defined by the Appointing Party, consistent for all stakeholders. |
| ORIG | Originator Code | 3–6 characters, identifying the organization creating the container. |
| FUNC | Function / Zone | System, zone, or design function; use “ZZ” for all. |
| LOC | Location / Level | Spatial partition (floor, area); use “XX” if not applicable. |
| TYPE | Information Type | DR = Drawing, M3 = 3D Model, PM = Project Management document. |
| ROLE | Discipline / Role | A = Architecture, S = Structural, M = MEP, C = Civil. |
| NUM | Sequential Number | 4-digit integer, using leading zeros (0001, 0034…). |
| REV | Revision | P1/P2 = Preliminary; S0/S1/S2 = Shared; A1/A2 = Approved; D = Delivery. |
Practical Example:
Example: 3rd Floor Architectural Floor Plan Drawing
VN2025-VNCC-ZZ-03-DR-A-0012-S2.rvt
-
VN2025 = Project
-
VNCC = Design Consultant
-
ZZ = Entire Building
-
03 = 3rd Floor
-
DR = Drawing
-
A = Architecture
-
0012 = Sequential Number
-
S2 = Shared for Approval
3. Suitability and Revision Codes
The suitability and revision fields reflect the document lifecycle within the Common Data Environment (CDE). ISO 19650 distinguishes between two groups: preliminary documents (P-series) and approved documents (A-series).
| Code | Meaning | CDE State | Revision Prefix |
| WIP | Work In Progress | Work in Progress | P1, P2, P3… |
| S0 | Initial Shared for review | Shared | P-series |
| S1 | Shared for coordination | Shared | P-series |
| S2 | Shared for information approval | Shared | P-series |
| A1 | Approved for construction issue | Published | A1, A2… |
| A4 | Approved for reference | Published | A-series |
| D1 | Project end issue / Handover | Archive | D-series |
Note: Suitability and revision fields are mandatory when the CDE cannot track metadata automatically. When the CDE has full metadata management capabilities, these two fields may be stored in file attributes instead of the file name.
4. TCVN 14177:2024 – Vietnam’s Legal Framework
The Ministry of Construction of Vietnam issued TCVN 14177-1:2024 and TCVN 14177-2:2024 in 2024, compiled by the Vietnam National Construction Consultants Corporation (VNCC). This standard series was developed directly based on references to ISO 19650-1:2018 and ISO 19650-2:2018.
This is a step toward realizing the national BIM roadmap, following Decision 2500/QD-BXD (2016) and Government Decisions 347/348 (2021) regarding BIM application in construction.
Correlation between ISO 19650 and TCVN 14177:2024
| ISO 19650 (International) | TCVN 14177:2024 (Vietnam) |
| General principle framework | Terminology adjusted for the Vietnam context |
| Allows National Annex adjustments | Defines Appointing/Delivery Party roles |
| Specifies file naming field structure | Provides 8-step BIM implementation guide |
| Defines CDE lifecycle | Supplements asset handover requirements |
| No mandatory specific classification system | Integrated into the national BIM roadmap |
TCVN 14177-1:2024 is equivalent to ISO 19650-1 (Concepts and principles). TCVN 14177-2:2024 is equivalent to ISO 19650-2 (Delivery phase of the assets). Regarding file naming rules, BIM projects in Vietnam apply the ISO 19650 structure supplemented by the National Annex where applicable.
5. Practical Application in Vietnam Projects
When implementing BIM according to TCVN 14177, projects in Vietnam must establish naming rules in the BIM Execution Plan (BEP). Below are examples for an office building project in Hanoi:
Example 1 – Architectural Model, WIP, Preliminary Revision
HN25-VNCC-BLD-ZZ-M3-A-0001-P1.rvt
-
HN25 = Hanoi 2025 Project | VNCC = Consultant | BLD = Main Building | ZZ = All Levels | M3 = 3D Model | A = Architecture | 0001 = Sequence | P1 = 1st Preliminary
Example 2 – Basement Structural Drawing, Approved
HN25-KTXD-BLD-B1-DR-S-0034-A2.dwg
-
HN25 = Project | KTXD = Structural Unit | BLD = Building | B1 = Basement 1 | DR = Drawing | S = Structural | 0034 = Sequence | A2 = 2nd Approval
Example 3 – Client’s EIR Document
HN25-CDA-XX-XX-PM-X-0001-S2.pdf
-
HN25 = Project | CDA = Client | XX = Not Applicable (Func) | XX = Not Applicable (Level) | PM = PM Document | X = No Discipline | 0001 = Sequence | S2 = Shared for Approval
6. Implementation Considerations
The current legal system still focuses on paper records and drawings; there are no full regulations yet regarding the legal validity of BIM data and digital signatures. This is a gap that needs to be addressed in subsequent legal documents.
Practical recommendations when setting up naming rules for BIM projects:
-
Establish a code table for all fields at the start of the project within the BEP and ensure all parties commit to consistent compliance.
-
Do not change the Project Code (PROJ) or Originator Code (ORIG) throughout the project lifecycle; these fields are foundational for tracking document origin.
-
When the CDE is capable of managing metadata, prioritize storing suitability and revision in metadata instead of the file name to keep names concise.
-
Use ZZ (multiple zones/levels) and XX (not applicable) appropriately to avoid ambiguous or inconsistent file names.
-
Organize a BIM Kick-off meeting to finalize the code table before any party begins creating files for the project.
References
-
ISO 19650-1:2018 – Organization and digitization of information about buildings and civil engineering works, including BIM – Part 1: Concepts and principles
-
ISO 19650-2:2018 – Part 2: Delivery phase of the assets
-
TCVN 14177-1:2024 – Vietnamese equivalent to ISO 19650-1
-
TCVN 14177-2:2024 – Vietnamese equivalent to ISO 19650-2
-
Guidance for TCVN 14177:2024 Application – Compiled by VNCC, issued by the Ministry of Construction Jan 2025.
-
Decision 2500/QD-BXD – Scheme for BIM application in construction activities and facility management.
