Consistent naming standards are essential for keeping the CDE organized, easy to navigate, and free from confusion.
They ensure that all members can quickly identify, locate, and work with the correct version of each document.
Why Naming Standards Matter
- Avoid version mix-ups by clearly identifying each file
- Improve search results with predictable, uniform naming
- Ensure compliance with industry standards (e.g., ISO 19650)
- Streamline collaboration between teams and stakeholders
Important: If a file does not follow the naming standard applied to a folder, it will be automatically redirected to the Holding Area until corrected
1 – Managing Naming Standards
- In the desired project, go to Naming Standards in Project Settings
- In the ribbon, click Create
- Enter a name and an optional description, then click Apply
- Under Naming Convention, click Select Attributes
- In the tab that opens, you will see all custom attributes that have been applied to the CDE Module (click here to remember how to create them)
- Check the attributes you want to include as mandatory in the naming structure.
- Click Apply – these attributes will now be required when naming a file
- Reorder the attributes by dragging them into position
- Choose a delimiter – either a dot (.) or a hyphen (-)
- (Optional) Add Related Attributes –fields that may appear in the file name but are not required for identification
Typical Naming Convention Structure
(Example of Required vs. Related Attributes)
Each project may define its own rules, but a common structure looks like this:
[Project ID]-[Role]-[Document Type]-[Description]-[Revision]
Required Attributes:
- Project ID – Unique identifier for the project (e.g., 1234)
- Role – Team or specialty (e.g., ARCH for Architecture, STR for Structure, MEP for Mechanical / Electrical / Plumbing)
- Document Type – Category (e.g., DR for Drawing, SP for Specification)
- Content – Short description of the file
Related Attribute:
- Revision – Identifies the revision of the file (e.g., R00, R01)
How it Works
If a user uploads this file:
1234-ARCH-DR-FloorPlans-R00
BIMWorkplace interprets it as:
- Version 1 of file 1234-ARCH-DR-FloorPlans
- Revision R00 stored in the Revision column
If a new file is uploaded:
1234-ARCH-DR-FloorPlans-R01
BIMWorkplace recognizes it as:
- Version 2 of the same file
- Revision R01 stored in the Revision column
This structure ensures consistency while allowing revisions to be tracked cleanly and automatically.
👉 For more information on how to work with document versions, click here.