Common Misconceptions When Building Your Equipment List

Building an equipment list sounds like the most administrative part of getting a maintenance system off the ground. Type out the equipment, give each one a code, paste in a location, done. In practice this is where most CMMS rollouts quietly go wrong, not because the work is hard, but because a few common misunderstandings push teams to do too much, too soon, in the wrong order. Here are three of the most common ones I see, and how to think about them differently.

Misconception 1: Each Engineer Can Handle Their Own Section

Most facility teams split the equipment list by trade. The ACMV engineer handles the air conditioning side, the electrical engineer handles the panels and switchgear, and the civil team takes the building fabric and plumbing. That is a perfectly sensible division of labour. The problem is what happens to the location column.

Each engineer ends up writing locations in their own way. One person writes Level 3 AHU Room, another writes L3-AHU-RM, and a third writes 3rd Floor Plant Room. The three of them are pointing at the same physical space, but when you merge their spreadsheets into a single equipment list, the system sees three different locations. Filters break. Reports double count. Anyone searching for a piece of equipment has to guess which spelling someone used.

Before anyone fills in equipment, the team should sit down together and finalise one location list. Decide how floors, rooms, zones, and plant areas will be named, lock the format, and share it as the single source of truth. Only after that should each trade start populating their portion of the equipment list. It feels like an unnecessary detour at first, but it saves weeks of cleanup later.

Misconception 2: The Equipment Code Needs to Encode Everything

The second misunderstanding is usually about the code itself. Teams spend days debating whether the code should embed the building, the floor, the trade, the manufacturer, the install year, the warranty status, and the serial number. They end up with a 28 character code that looks impressive on a spreadsheet and falls apart everywhere else.

An equipment code has one job. It needs to uniquely identify the equipment. That is it. If you also want to know the building, floor, or trade, that information belongs in its own column where it can be filtered and reported on properly. Stuffing it into the code creates a string that nobody can read and that has to be rewritten every time the equipment moves or the manufacturer changes.

Two rules go a long way here. Keep it short, keep it unique. Excel can help you check uniqueness in seconds with a COUNTIF formula. And avoid punctuation that breaks systems. Forward slashes, backslashes, single quotes, double quotes, and brackets are common offenders. Many systems treat these as control characters and crash, truncate, or escape the value in ways you only discover much later. Dashes and underscores are safe. Spaces are not. A code like P-001 or ACMV_034 is plenty. When you eventually convert these codes to barcodes or QR codes, you will thank yourself for keeping them short enough that the printed sticker still fits on the equipment.

Misconception 3: The Equipment List Is a One Off Exercise

The third misunderstanding is the most damaging because it sets the wrong expectation from day one. Many teams treat the equipment list like a one time data entry project. They block out two weeks, try to list everything in the building, and then declare the list complete.

Two things happen. First, the list bloats with equipment that does not really exist anymore, or that has been replaced, or that was never significant enough to track in the first place. Second, the team burns out trying to chase down every last item before going live, when the system could have started delivering value weeks earlier with a smaller list.

A better way to think about it:

• Start with the equipment that matters most. Critical, mostly stationary assets like lifts, ACMV units, fire systems, generators, and chillers. These are the items that drive your maintenance workload anyway.
• Add equipment that actually has issues. If a piece of equipment is reliable and rarely touched, it can wait. If it generates work orders every month, get it into the list.
• Leave the movable, low priority items for later. Furniture, small fittings, and miscellaneous items are notoriously hard to track because they move around. They are also rarely the source of real downtime.
• Treat the list as a progressive document. Add new equipment as you commission it, retire entries as you decommission, and review the list every quarter.

AI tools have made this even more manageable. You can hand a photograph of a plant room or an inspection report to a modern AI model and have it pull out a draft equipment list for you to review, much faster than typing each row by hand. The same goes for tidying up location names or normalising existing codes. Used carefully, AI turns the progressive update from a chore into a few minutes of work per week.

The Pattern Behind All Three

Each of these misunderstandings comes from the same place. Teams treat the equipment list as a deliverable instead of a living foundation. When you treat it as a foundation, the priorities reorder themselves naturally. Agree on the location list first. Keep codes short, unique, and free of breaking characters. Start small, focus on the equipment that drives real work, and let the list grow with the building.

Get those three right and the rest of your maintenance system, the work orders, the preventive schedules, the reporting, has a clean foundation to sit on. Get them wrong and you will spend the next year fighting your own data.