If CMMS system users are complaining that they can’t find the information they’re looking for, it usually means that an effective asset-naming convention hasn’t been put into place. Creating an asset-naming convention involves defining and formatting the way assets are named within your system. It is essential to follow consistent naming standards when entering data into your equipment maintenance software so that assets can be identified and data can be retrieved quickly.
Asset-naming conventions help you search for records and maintain the integrity of data. Standardized naming conventions also aid in data reporting and analysis. Come up with a useful naming convention before you go live with your CMMS system because it can be difficult to change later. Even if you manage to change it, your archived report data could become invalid. Small businesses should look at the big picture when establishing naming conventions, so they don’t have to alter their naming conventions later if their businesses grow and they purchase new assets.
Asset naming doesn’t have to be complex, but it needs to be consistent and logical. The goal is to adopt a naming convention that allows users to recognize an asset’s location and purpose at a glance. Once you determine the structure of your naming convention, record it in your maintenance policy document so that everyone in your organization adheres to it when entering data or assets into your equipment maintenance software.
Asset-Naming Convention Best Practices
In a manual maintenance management system, you may be as descriptive as you like when naming an asset, but in a cmms maintenance connection system, you must use naming conventions that communicate the same amount of information in a concise manner. Numbers have less meaning, so it’s ideal to maximize the use of letters to make naming conventions more intuitive.
An asset-naming convention should be easy for maintenance technicians to deconstruct and derive meaning from. Furthermore, the codes you use should have a consistent number of characters. For example, if you pull a list of your assets, asset 1, asset 3, and asset 13 would be ordered 1,13,3. If you name the assets 01, 03, and 13, however, they will appear in the proper order.
You might want to alternate numeric characters with alphabetic characters to make naming conventions easier to read and identify. Ideally, naming conventions should drill down, with each component of the code being a subset of the previous. When deciding on an asset-naming convention, consider the hierarchical structure of your assets, which may look something like this:
- Asset type
- Asset number
Come up with a naming convention that fits all of the required information into just a few characters. For example, the code for air conditioning unit number 4 in building three at your US site could be US03ACUN04. This code describes the country (US), building number (03), asset type (ACUN), and asset number (04). ACUN is a logical code for an air conditioning unit because it is more identifiable than a random code like XYZ, for example. You can increase or reduce the number of characters in asset codes, depending on your organization’s requirements.
The task of establishing an asset-naming convention for your organization is simpler than you’d imagine. Developing an appropriate naming convention for your organization will likely require you to focus on certain components while ignoring others. While maintenance technicians might think that an asset-naming convention looks complicated at first, they tend to adapt quickly.
DPSI works closely with customers to guide them in establishing proper asset-naming conventions and supports them through all phases of the CMMS system implementation process. Contact DPSI today for more information about our products and services!