<ProjectNumber>_<Client>_<ProjectName>_<ProjectCityCounty>_<RevitVersion2Digit><DisciplineAbbreviation>.rvt

Token definitions:

Token     Description 

• <ProjectNumber> S3 CMAP project number; “.00” pre-CMAP, single-letter post-CMAP for same-site/different-contract continuation.

• <Client> Client name or approved short client name

• <ProjectName> Approved project name

• <ProjectCityCounty> Project city or county. Use the project location naming approved for the project.

• <RevitVersion2Digit> Two-digit Revit version year, such as "24 "or "27"

• <DisciplineAbbreviation> Approved discipline abbreviation, such as `A`, `S`, `M`, `P`, `E`, `FP`, or other approved project discipline code

Rules:

• Use underscores between major name fields.

• Do not use spaces in Revit model filenames.

• Keep client and project name values consistent across all discipline models.

• Use the same two-digit Revit version for all models created in the same Revit project version.

• Do not rename active cloud workshared models without BIM manager approval.

Examples:

24001_S3Design_YogaJoint_Braintree_26A.rvt

24001a_S3Design_YogaJoint_Braintree_26A.rvt

24001b_S3Design_YogaJoint_Braintree_26A.rvt

Revit model files must use the following naming pattern unless the project BIM Execution Plan defines an approved exception:

<ProjectNumber>_<Client>_<ProjectName>_<ProjectCityCounty>_<RevitVersion2Digit><DisciplineAbbreviation>.rvt

Token definitions:

Token     Description 

• <ProjectNumber> S3 project number

• <Client> Client name or approved short client name

• <ProjectName> Approved project name

• <ProjectCityCounty> Project city or county. Use the project location naming approved for the project.

• <RevitVersion2Digit> Two-digit Revit version year, such as "24 "or "27"

• <DisciplineAbbreviation> Approved discipline abbreviation, such as `A`, `S`, `M`, `P`, `E`, `FP`, or other approved project discipline code

Rules:

• Use underscores between major name fields.

• Do not use spaces in Revit model filenames.

• Keep client and project name values consistent across all discipline models.

• Use the same two-digit Revit version for all models created in the same Revit project version.

• Do not rename active cloud workshared models without BIM manager approval.

Example:

24001_S3Design_YogaJoint_Braintree_26A.rvt

Rule Number 1

• Be consistent

• Consistency is the primary naming rule. Names must be predictable, readable, and structured the same way across families, types, parameters, reference planes, files, and supporting BIM content.

Prefix

• All new S3 standard content names must begin with:

• "S3_"

  • "S3_" indicates that the item has been developed as part of the new S3 standard and differentiates it from older content.

Macro-to-Micro Structure

• Names must progress from general to specific, also known as macro to micro.

• This structure helps sort list as the sorting as like categories self sort.

Example structure:

S3_Category_Item_Subtype_Descriptor

Separators

• Use underscores ("_") to separate hierarchy levels.

• Underscores help with parsing, sorting, and organizing files and content consistently across projects.

Abbreviations

• Abbreviations are preferred to be all caps, but all caps are not required in every case.

Example:

S3_AOR_License_No

CamelCase

• Use CamelCase by capitalizing the first letter of each word for readability.

Example:

SemiRecessed

Spaces

• Spaces are not allowed in names except when writing feet and inches.

• For all non-dimensional names, use CamelCase instead of spaces.

Dimension rules

• Use spaces only for feet-and-inches formatting.

• Do not use decimal units in names.

• Use fractional units only.

• Use inches only if the dimension is less than `12"` or `1' 0"`.

• If one value in a multi-value name is less than `12"`, still use feet-and-fractional-inch formatting so units remain consistent in the name.

Correct and incorrect examples:

• ✅ 2' 8" ❌ 2'8"

• ✅ 2' 8"_0' 8" ❌ 2' 8"_8"

• ✅ 1 1/2" ❌ 11/2"

All other names must have no spaces.

Scales

• When family or type names include scales, add the scale factor as a prefix so scale values sort in a usable order.

Required scale format:

ScaleFactor_FractionScale"

Correct and incorrect examples:

• ✅ 008_1 1/2" ❌ 1 1/2"

Underscores

• Use underscores only as hierarchy separators or intentional placeholders.

Dashes

Do not use dashes.

Correct and incorrect examples:

• ✅ BiPass ❌ Bi-Pass

• ✅ SemiRecessed ❌ Semi-Recessed

• S3_Default

• S3_SemiRecessed_LifeSafety_Top

• S3_Length

• S3_Bowl_Interior_Length

• S3_Center_Left.Right

• S3_Drain_Center_Front.Back

• View names must be clear, consistent, and coordinated with sheet presentation.

• All linked views must use the following suffix in the Revit view name: "_Linked View"

• <ViewName>_Linked View

• Example: FirstFloorPlan_Linked View

• The suffix is required in the Revit view name for linked views.

• The sheet `Title on Sheet` must not include the `_Linked View` suffix.

• Linked view naming must remain consistent across all disciplines using linked views.

Recommended family file/type naming structure:

• • S3_<RevitCategory>_<SearchKeyword>_<SecondaryDescription>_<Size>_<HostType>_<MasterSpecSectionName>_<DivisionSection6Digits>

Examples:

• • S3_SpecialtyEquipment_FireExtinguisher_Cabinet_Wall_104400

  • S3_FireExtinguisherCabinet_Wall_FireProtectionSpecialties_104400

Host type values:

• • None

  • Wall

  • Floor

  • Roof

  • Level

  • Face

  • Line

  • Ceiling

  • System

  • Adaptive

  • CurtainPanel

Rules:

• • Use the six-digit division section number when available.

  • Manufacturer, client, or brand references may be used as secondary descriptions when they help users identify the content.

  • Family names, type names, and file names should be searchable by Revit category, noun / keyword, host type, and specification section where applicable.