Naming Standards

Consistent naming standards are essential for keeping the CDE organized, searchable, and reliable.
They ensure that all members can quickly identify and work with the correct documents, while maintaining structured and traceable information across the project.

Why Naming Standards Matter

• Prevent confusion between similar or duplicate files

• Improve search and filtering with predictable naming

• Support compliance with standards such as ISO 19650

• Enable structured collaboration across teams and stakeholders

Important: If a file does not comply with the naming standard applied to a folder, it is automatically redirected to the Holding Area until corrected.

1.     Managing Naming Standards

a.     In the desired project, go to Naming Standards in Project Settings

b.     In the ribbon, click +

c.      Enter a name and an optional description, then click Apply

d.     Under Naming Convention, click Select Attributes

e.     The panel displays all attributes assigned to the CDE module

f.       Select the attributes in the naming structure

g.     Click Apply

h.     Reorder attributes by dragging them

i.       Choose a delimiter: hyphen (-), underscore (_) or dot (.)

j.       (Optional) Add Related Attributes –fields that may appear in the file name but are not required for identification

Typical Naming Convention Structure

Each project may define its own rules. A common example:

[Project ID]-[Role]-[Document Type]-[Description]-[Revision]

Required Attributes:

• Project ID - Unique project identifier (e.g., 1234)

• Role - Discipline or specialty (e.g., ARCH, STR, MEP)

• Document Type - Category (e.g., DR, SP)

• Content - Short file description

Related Attribute:

• Revision – Identifies the revision (e.g., R00, R01)

How it Works

When a file is uploaded:  
1234-ARCH-DR-FloorPlans-R00

BIMWorkplace interprets:

·        File identity: 1234-ARCH-DR-FloorPlans

·        Revision: R00

If a new file is uploaded:
1234-ARCH-DR-FloorPlans-R01

The platform recognizes:

·        Same file identity

·        Updated revision (R01)

·        New version recorded in version history

This ensures that revisions are structured while version control is managed automatically by the system.

👉 For more information on version control, see the Version Control article.