Search on this blog

Search on this blog

How to Create an Equipment and Systems Naming Framework for Commissioning Projects

Equipment Naming

Commissioning firms manage a tremendous amount of project data: systems, equipment, checklists, functional performance tests, issues, observations, documents, and reports.

When that information is named consistently, teams can find it, filter it, reuse it, and report on it. When naming varies by project manager or project, even basic tasks become harder.

Consider how many ways the same asset might appear across a portfolio:

  • AHU-1
  • AHU 01
  • Air Handler #1
  • Air Handling Unit 1
  • RTU/AHU-01
  • Building 1 AHU 1

A person may recognize that these names refer to similar equipment. Software, reports, integrations, and portfolio dashboards usually treat them as different values.

An Equipment and Systems Naming Framework gives commissioning firms a repeatable method for naming and organizing project assets from kickoff through closeout. It also creates a foundation for standardized templates, issue tracking, testing, reporting, and portfolio analytics.

Why equipment and system naming matters

Naming conventions can look like a minor administrative detail. In practice, they affect nearly every phase of commissioning.

A consistent naming framework helps a commissioning firm:

  • Set up projects more quickly
  • Group equipment under the correct systems
  • Assign the right checklists and functional tests
  • Search and filter project records
  • Connect issues to specific assets
  • Identify missing or duplicated equipment
  • Produce consistent client reports
  • Transfer information into the Systems Manual
  • Integrate commissioning data with BIM, BAS, CMMS, EAM, or reporting platforms
  • Compare performance across projects
  • Reuse templates without rebuilding the project structure
  • Preserve institutional knowledge when team members change

Naming also supports the broader commissioning documentation process. ASHRAE’s commissioning resources emphasize structured documentation throughout the commissioning process, including plans, testing records, issue logs, reports, and other deliverables. A stable asset structure makes those records easier to organize and trace throughout the project lifecycle. See ASHRAE Standard 300 commissioning resources.

The goal is not to invent an elaborate coding system. The goal is to create names that are unique, recognizable, scalable, and useful.

Start with a standard naming structure

The Commissioning Firm Standardization Toolkit recommends beginning with a structure such as:

[System]-[Equipment Type]-[Identifier]

Examples:

  • CHW-CH-01
  • CHW-P-01
  • HVAC-AHU-01
  • ELEC-PNL-LP1
  • PLBG-DHWP-02

For projects where location is important, the format can be expanded:

[Building]-[Floor or Area]-[System]-[Equipment Type]-[Identifier]

Examples:

  • BLDG1-L03-HVAC-AHU-01
  • BLDG2-PH-CHW-P-02
  • BLDG3-B-CHW-CH-03
  • WHSE-A-ELEC-MDP-01

Industrial or campus projects may need an additional process, unit, train, or site field:

[Site]-[Process Area]-[System]-[Equipment Type]-[Identifier]

Examples:

  • SITE1-UTIL-CHW-CH-01
  • PLANT1-AREA200-CDA-AC-02
  • SOLAR1-BLK03-DC-CB-04
  • BESS1-BLK02-HVAC-ACU-01

The exact sequence matters less than using the selected sequence consistently.

Define what each part of the name means

Every field should answer a specific question.

FieldQuestion answeredExample
Site or buildingWhere is the asset located?BLDG1
Floor or areaWhich level, zone, block, or process area contains it?L03
SystemWhich functional system does it belong to?CHW
Equipment typeWhat kind of asset is it?P
IdentifierWhich individual asset is it?01
Qualifier, if neededDoes it have a special role?PRI, SEC, STBY

For example:

BLDG1-L03-CHW-P-02

This can be read as “Building 1, Level 3, chilled-water system, pump 02.”

Avoid adding fields that do not improve identification, filtering, or reporting. Every extra segment increases the chance of inconsistent data entry.

Preserve design-document identifiers without sacrificing consistency

Commissioning teams should not casually rename equipment that already has an established design tag. The equipment name should match the contract documents whenever practical.

However, design documents are not always internally consistent. Mechanical schedules, control drawings, electrical one-lines, submittals, and equipment labels may use different identifiers for the same asset.

A good framework therefore distinguishes between:

  • Commissioning asset ID: The unique, standardized identifier used by the commissioning team
  • Design tag: The identifier shown on the design documents
  • Installed asset tag: The identifier physically applied in the field
  • Manufacturer and model: The product identity
  • External system IDs: BAS, BIM, CMMS, EAM, or owner asset-management identifiers

These values may be identical, but they should not be assumed to be identical.

For example:

FieldValue
Commissioning asset IDBLDG1-L02-HVAC-AHU-03
Design tagAHU-3
Installed labelAHU-03
BAS referenceB1.AHU03
CMMS asset ID1002847

Maintaining cross-references lets the commissioning team standardize its data without losing traceability to the designer’s, contractor’s, controls vendor’s, or owner’s records.

Build an approved abbreviation dictionary

Do not let every project team invent abbreviations independently.

Create a controlled dictionary that records:

  • Approved abbreviation
  • Full term
  • Category
  • Allowed alternatives
  • Prohibited or ambiguous alternatives
  • Definition or intended use
  • Date approved
  • Standard owner
  • Source or reference
  • Revision history

ASHRAE publishes an extensive list of abbreviations used in HVAC&R text, drawings, and computer programs. It also cautions that the same abbreviation can sometimes represent different terms and recommends defining abbreviations in the applicable documentation. Where multiple options exist, ASHRAE generally favors the longer, more descriptive form when practical. See the ASHRAE Handbook chapter on abbreviations and symbols.

That is an important principle for commissioning firms: choose abbreviations that reduce ambiguity, not simply the shortest possible code.

Example systems abbreviation dictionary

The following list is a starting point for a commissioning firm’s internal standard. It incorporates widely used terminology found in ASHRAE references, federal facility standards, design conventions, and common building and industrial practice.

It is not a universal code. Confirm every abbreviation against the project drawings, specifications, owner standards, and applicable asset-management requirements before adoption.

HVAC and mechanical systems

AbbreviationSystem or equipment
HVACHeating, ventilation, and air conditioning
BASBuilding automation system
BMSBuilding management system
CHWChilled-water system
CHWSChilled-water supply
CHWRChilled-water return
CWCondenser-water system
CWSCondenser-water supply
CWRCondenser-water return
HHWHeating hot-water system
HWSHeating-water supply
HWRHeating-water return
LTHWLow-temperature hot water
MTHWMedium-temperature hot water
HTHWHigh-temperature hot water
STMSteam system
HPSHigh-pressure steam
MPSMedium-pressure steam
LPSLow-pressure steam
CDCondensate system
OAOutdoor-air system
SASupply-air system
RAReturn-air system
EAExhaust-air system
MAMixed-air system
TATransfer-air system
DOASDedicated outdoor-air system
CAVConstant-air-volume system
VAVVariable-air-volume system
VRFVariable-refrigerant-flow system
DXDirect-expansion refrigeration
REFRRefrigeration system
HXHeat-exchanger system
HRHeat-recovery system
GEOGeothermal system

HVAC and mechanical equipment

AbbreviationEquipment type
AHUAir-handling unit
ACUAir-conditioning unit
RTURooftop unit
MAUMakeup-air unit
DOASDedicated outdoor-air unit
FCUFan-coil unit
CRACComputer-room air-conditioning unit
CRAHComputer-room air-handling unit
VAVVariable-air-volume terminal unit
FPBFan-powered box
TUTerminal unit
EFExhaust fan
SFSupply fan
RAFReturn-air fan
SAFSupply-air fan
RFRelief fan
CUCondensing unit
CHChiller
BOILBoiler
CTCooling tower
PPump
HWPHeating-water pump
CHWPChilled-water pump
CWPCondenser-water pump
DHWPDomestic hot-water pump
HXHeat exchanger
HPHeat pump
ERVEnergy-recovery ventilator
HRVHeat-recovery ventilator
HUMHumidifier
DHUMDehumidifier
CCCooling coil
HCHeating coil
RHCReheat coil
DAMPDamper
VFDVariable-frequency drive
CVControl valve
PRVPressure-reducing valve
TXVThermal expansion valve

ASHRAE’s published list specifically includes common forms such as AHU, ACU, BAS, CAV, CH/CHIL, CT, DDC, DX, ERV, FCU, HX, HP, MAU, RTU, VAV, VRF, and others. Commissioning firms can use those conventions as a baseline while documenting any firm-specific additions.

Plumbing and water systems

AbbreviationSystem or equipment
PLBGPlumbing
DCWDomestic cold water
DHWDomestic hot water
DHWRDomestic hot-water return
PWPotable water
NPWNon-potable water
ROReverse-osmosis water
DIDeionized-water system
SANSanitary-waste system
VENTPlumbing vent system
STWStormwater system
RDRoof-drain system or roof drain
ORDOverflow roof drain
GWGraywater system
RWReclaimed-water system
SUMPSump system
SWPSewage pump
SPSump pump
WHWater heater
DWHDomestic water heater
TMVThermostatic mixing valve
RPZReduced-pressure-zone backflow preventer
BFPBackflow preventer
PRVPressure-reducing valve

Use special care with plumbing abbreviations. For example, “CW” may mean cold water on one project and condenser water on another. A firm might therefore reserve CW for condenser water and require DCW for domestic cold water.

Electrical power systems

AbbreviationSystem or equipment
ELECElectrical system
NORMNormal power
EMEREmergency power
STBYStandby power
EPEmergency power
UPSUninterruptible power supply
DCDirect-current system
PVPhotovoltaic system
BESSBattery energy storage system
GENGenerator
XFMRTransformer
SWGRSwitchgear
SWBDSwitchboard
PNLPanelboard
MDPMain distribution panel
MCCMotor-control center
ATSAutomatic transfer switch
MTSManual transfer switch
VFDVariable-frequency drive
CBCircuit breaker
DSDisconnect switch
RPPRemote power panel
PDUPower distribution unit
STSStatic transfer switch
INVInverter
RECTRectifier
BATBattery or battery bank
BCBattery charger
CAPCapacitor bank
GNDGrounding system
LPSLightning-protection system
EPOEmergency power-off system

A federal equipment-numbering standard from Lawrence Livermore National Laboratory illustrates why these relationships matter: its framework combines facility number, equipment type, item number, and—where needed—a system designator. It also calls for cross-referencing related equipment and identifying the electrical circuit serving powered equipment. See the LLNL Equipment Numbering standard.

Lighting and lighting-control systems

AbbreviationSystem or equipment
LTGLighting system
LTGCLighting-control system
ELEmergency lighting
EXT-LTGExterior lighting
INVLighting inverter
LCPLighting-control panel
RLYPRelay panel
OCCOccupancy sensor
VACVacancy sensor
PHSPhotocell or photosensor
DIMDimmer or dimming controller

Fire and life-safety systems

AbbreviationSystem or equipment
FAFire-alarm system
FACPFire-alarm control panel
NACNotification-appliance circuit
EVACEmergency voice/alarm communications
FSFire-suppression system
SPKSprinkler system
FPFire-protection system
FSPFire pump
JPJockey pump
SDCSmoke-control system
SMKFSmoke-control fan
DHDuct smoke detector
SDSmoke detector
HDHeat detector
FSDFire/smoke damper
FDFire damper
SDMPSmoke damper

Controls, monitoring, and communications

AbbreviationSystem or equipment
BASBuilding automation system
BMSBuilding management system
DDCDirect digital control
PLCProgrammable logic controller
SCADASupervisory control and data acquisition
EMCSEnergy-management and control system
EMSEnergy-management system
EPMSElectrical power monitoring system
PMSPower monitoring system
FMSFacility management system
ITInformation technology
LANLocal-area network
WANWide-area network
IDFIntermediate distribution frame
MDFMain distribution frame
NVRNetwork video recorder
CCTVClosed-circuit television
ACSAccess-control system
DASDistributed antenna system

Industrial and process utility systems

AbbreviationSystem or equipment
CDACompressed dry air
IAInstrument air
PAPlant air
NGNatural-gas system
FGFuel-gas system
PGProcess-gas system
VACVacuum system
PVACProcess-vacuum system
CWCooling-water system
PCWProcess-cooling-water system
CHWChilled-water system
ROReverse-osmosis water
DIDeionized water
WFIWater for injection
CIPClean-in-place system
SIPSteam-in-place system
WWWastewater system
IWIndustrial-waste system
CSChemical-supply system
EXHProcess-exhaust system
DCEDust-collection/extraction system
SCRSelective catalytic reduction
CEMSContinuous emissions monitoring system

Resolve abbreviations that can mean more than one thing

Ambiguity is one of the biggest risks in a naming standard.

Common examples include:

AbbreviationPossible meanings
ACAlternating current; air conditioning
ACSAccess-control system; air-conditioning system
CDCondensate drain; construction document
CTCooling tower; current transformer
CUCondensing unit; copper
CWCondenser water; cold water
EFExhaust fan; entrance feeder
FAFire alarm; face area
FCUFan-coil unit; field-control unit
FSDFire/smoke damper; full-scale deflection
HPHeat pump; horsepower; high pressure
LPSLow-pressure steam; lightning-protection system
MAUMakeup-air unit; medical-air unit
MCCMotor-control center; mission-control center
PRVPressure-reducing valve; pressure-relief valve
SDSmoke detector; storm drain
SFSupply fan; square feet; safety factor
SPSump pump; static pressure; setpoint
UPSUninterruptible power supply; not a parcel service in this context
VACVacuum; volts alternating current
VAVVariable air volume; sometimes the terminal unit itself

Do not rely on context to resolve these conflicts automatically. Establish rules such as:

  • One meaning per abbreviation within the company dictionary
  • Longer abbreviations when a short form is ambiguous
  • Separate system and equipment dictionaries
  • Project-specific exceptions documented before project setup
  • No undocumented abbreviations
  • No reuse of an existing abbreviation for a new purpose

For example, use ACU for air-conditioning unit and reserve AC for alternating current. Use PRV-RED and PRV-REL, or different approved codes, if both pressure-reducing and pressure-relief valves are tracked as commissioned assets.

Establish formatting rules

The abbreviation dictionary defines the vocabulary. Formatting rules define how that vocabulary is assembled.

A practical company standard should answer the following:

Delimiters

Choose one delimiter, usually a hyphen.

Preferred:

  • BLDG1-L02-HVAC-AHU-01

Avoid mixing formats:

  • BLDG1_L02-AHU 01
  • BLDG1/L02/AHU-1
  • BLDG1.L02.AHU#01

Capitalization

Use uppercase for system and equipment abbreviations unless an owner standard requires otherwise.

Number padding

Use leading zeros when the expected asset count supports them:

  • AHU-01 through AHU-99
  • VAV-001 through VAV-999
  • PV-MOD-0001 through PV-MOD-9999

Do not mix AHU-1, AHU-02, and AHU-003 within the same naming level.

Special characters

Avoid characters that may cause problems in spreadsheets, URLs, databases, APIs, or file systems. Hyphens are generally safer than slashes, backslashes, ampersands, number signs, or punctuation.

Spaces

Avoid spaces in the unique asset ID. A separate display-name field can contain reader-friendly text.

Sequence rules

Define whether numbering is:

  • Project-wide
  • Building-specific
  • Floor-specific
  • System-specific
  • Area-specific
  • Assigned by the designer
  • Assigned by installation sequence
  • Inherited from the owner’s asset registry

Redundant information

Do not repeat information without a clear benefit. If every asset in a database already has a separate building field, including the building in the display name may be useful—but duplicating it inside multiple hidden IDs may not be.

Connect systems to equipment

A naming framework should describe relationships, not just individual assets.

For example:

CHW-01: Chilled-Water System 01

  • CHW-CH-01
  • CHW-CH-02
  • CHW-CHWP-01
  • CHW-CHWP-02
  • CHW-CWP-01
  • CHW-CWP-02
  • CHW-CT-01
  • CHW-CT-02

Or:

AHU-03 Air System

  • HVAC-AHU-03
  • HVAC-VAV-03-001
  • HVAC-VAV-03-002
  • HVAC-VAV-03-003
  • HVAC-EF-03A
  • BAS-CTRL-AHU-03

This hierarchy makes it easier to assess readiness. A team can see whether all upstream and downstream assets have completed startup, pre-functional checklists, controls checkout, and functional testing before attempting an integrated test.

Treat the framework as governed company data

Naming standards deteriorate when no one owns them.

Assign a person or small group to maintain the framework. That owner should:

  • Approve new abbreviations
  • Resolve conflicts
  • Maintain the master dictionary
  • Review project exceptions
  • Coordinate with template owners
  • Track revisions
  • Publish the current version
  • Incorporate lessons learned
  • Prevent project-specific terms from becoming company standards without review

Project teams should be allowed to adapt the framework when required by an owner or contract. Those changes should flow back into the company standard only after review.

Test the framework before rolling it out

Before adopting the standard company-wide, test it against several real projects:

  • A typical commercial building
  • A central utility plant
  • A project with multiple buildings
  • A project with repeated equipment on many floors
  • A controls-intensive project
  • An industrial or renewable-energy project
  • A project that must integrate with an owner’s CMMS or EAM

Ask whether the proposed names are:

  • Unique
  • Easy to read
  • Easy to enter correctly
  • Compatible with project documents
  • Useful for grouping and filtering
  • Stable when an asset is replaced
  • Scalable to the expected asset count
  • Compatible with software field-length limits
  • Clear to both commissioning staff and project stakeholders

If a new team member cannot interpret a typical asset name using the written standard, the framework probably needs refinement.

A practical implementation sequence

Commissioning firms can implement a naming framework in five steps.

1. Inventory current practices

Collect equipment lists, issue logs, test forms, reports, and project templates from several completed projects. Identify duplicate abbreviations, conflicting meanings, and inconsistent formats.

2. Select the core structure

Decide which fields are mandatory and which are optional. Keep the core structure as simple as possible.

3. Create the abbreviation dictionary

Start with the most frequently commissioned systems and equipment. Document ambiguous terms and prohibited alternatives.

4. Build the framework into project templates

Configure system names, equipment types, checklist assignments, issue fields, and reports so that the standard is applied during project setup—not corrected at closeout.

5. Govern and improve it

Review the dictionary after major projects. Add useful terms, retire confusing ones, and record the reason for every material change.

Standardization starts with a common language

The strongest naming framework is not necessarily the most technically elaborate. It is the one that project teams can understand and use consistently.

When systems and equipment follow a predictable structure, commissioning firms can build better templates, apply repeatable testing processes, produce clearer reports, and learn across their entire project portfolio.

Equipment and system naming is only one component of a standardized commissioning operation. Project setup, documentation, checklists, functional testing, issues management, meetings, reporting, closeout, lessons learned, template governance, roles, and KPIs must work together.

The Commissioning Firm Standardization Toolkit provides a practical framework for doing exactly that. It includes an Equipment & Systems Naming Framework along with a standard project lifecycle, setup checklist, documentation structure, checklist and functional-test guidance, issue-management workflow, reporting framework, closeout checklist, template-library model, KPI scorecard, and 90-day implementation roadmap.

Download the Commissioning Firm Standardization Toolkit below to evaluate your current processes, establish company-wide standards, and create a repeatable framework for managing commissioning projects from kickoff through closeout.

Commissioning Firm Standardization Toolkit

Additional resources:

Case Studies

Learn how Bluerithm's customers have used the software

Read

Guides

Learn more about commissioning and related topics

Read

Videos

Learn how Bluerithm can help you by viewing these videos

View

Webinars

Recordings of previous webinars

View