The equipment register: what to record for each asset and how to build one that stays accurate

What an equipment register is, and what it is not

The equipment register is the list everything else in maintenance hangs from. Work orders, breakdown records, preventive maintenance schedules, spare parts lists, meter readings and costs all need to point at something, and that something is a record in the register. If the register is wrong, every report built on it is wrong too, however careful the technicians were when they closed their jobs.

The most common confusion is with the fixed asset register that finance keeps. The two lists answer different questions. Finance asks what the company owns and how much it is worth on the books. Maintenance asks what needs work, where it is and what happens when it stops. That is why they do not line up. A production line bought as one invoice is one line in the finance register but may be twenty records in yours: conveyors, motors, a hydraulic unit, a control panel. The other way round, a leased forklift fleet or a landlord's rooftop chiller may not appear in the finance list at all, yet your team services them every month.

The hard part: deciding what counts as one piece of equipment

Most registers fail at the level of detail, not at the fields. Go too coarse and you get one record called "Line 2", where every failure for a year lands and tells you nothing. Go too fine and you have records for every bearing and sensor, nobody keeps them current, and technicians pick whichever record is nearest the top of the list. The test that works on the shop floor is a question you ask for each candidate item:

• Will we write work orders against it on its own?
• Do we want to see its failures separately from the machine it sits in?
• Does it have its own preventive maintenance schedule, inspection or calibration?
• Can it be removed and fitted somewhere else, or replaced as a unit with its own serial number?

If the answer to any of these is yes, it gets its own record, linked to a parent. If all four are no, it is a part: it goes on the parent's spare parts list and shows up in work orders as a part used, not as an asset. A V belt is a part. The gearbox that belt drives, which you oil on a schedule and which has failed twice, is an asset.

Keep the hierarchy shallow. Three levels cover almost every site: a location or system (Building A, Boiler house, Truck fleet), the equipment (Boiler 1, Truck 34), and the components worth tracking (Burner, Feed pump). Every extra level is another click for a technician on a phone with greasy hands, and another place for a record to be filed wrongly.

The fields to record for each piece of equipment

Fewer fields that are always filled beat many fields that are half empty. The table below is a working set: the first eight are the minimum for a record to be useful, the rest you add when you have a use for them.

Criticality is the field teams skip and later regret. Keep it simple. A three level scale that the whole team can apply in seconds is worth more than a scored matrix nobody revisits. One workable definition, as an example: A stops production, creates a safety or legal risk, or has no backup. B slows work or has a backup that takes effort to bring in. C can wait for the next planned visit. Write your definitions at the top of the register so two people rating the same pump get the same answer.

IDs and tags: why the code should mean nothing

It is tempting to build smart codes such as P1-CR-COMP-02, where every part of the code tells you plant, room and type. It feels organised for about a year. Then compressor 2 moves to Plant 3, and you either change the ID, which breaks the link to every old work order, printed tag and spreadsheet that used it, or you keep it, and the code now says the wrong plant forever.

• Use a plain running number with a short prefix (EQ-00412). Put location, type and parent in their own fields, where they can change without touching the ID.
• Never reuse an ID, even after equipment is scrapped. An old breakdown record must still point to the right machine.
• Pad numbers to a fixed length so lists sort properly; EQ-2 sorting after EQ-10 causes small, constant confusion.
• Put the ID on the equipment itself: a tag with the ID in large print and a QR code that opens the record. Mount it where it can be read without opening a guard, and away from heat, oil and the pressure washer.
• Keep the name field human. Technicians search for "compressor 2", not for EQ-00412.

How to build the register, step by step

Do not start from the purchase records or an old spreadsheet and try to clean it at a desk. Start from what is physically there. Old lists are useful as a checklist during the walk, not as the source.

1. Agree the rules first. Write down the ID format, the hierarchy levels, the criticality definitions and the "own record or part" test before anyone walks the site. Changing rules halfway means redoing the first half.
2. List locations and systems. Buildings, areas, lines, vehicle groups. This is the skeleton the equipment hangs on.
3. Walk the site area by area, starting with the most critical. If the work stops halfway, which it often does, the equipment that matters most is already done.
4. Photograph every nameplate. Typing serial numbers from memory or from a dirty plate in bad light produces errors. A photo lets someone check later, and it belongs in the record as an attachment.
5. Tag as you go. Fit the ID tag during the same visit. A register whose IDs are not on the equipment gets ignored on the floor.
6. Reconcile against the old lists. Anything on the finance list, the preventive maintenance plan or last year's work orders that you did not find is either gone, renamed or hidden. Chase each one.
7. Load it and assign one owner. One named person approves new records and changes. Shared ownership produces duplicates within weeks.

Keeping it accurate after the first month

Every register is accurate on the day it is finished. The ones that stay accurate are tied to work the team already does, so updating them is part of the job rather than an extra task.

• No work order without an asset. If a technician cannot find the equipment, that is a missing record to create, not a reason to pick "General". A catch all record is where your failure history goes to disappear.
• Replacements update the record. When a unit is replaced, close the job with the new serial number. Decide in advance whether a like for like replacement keeps the same record (usually yes for a position) or gets a new one (yes when the old unit goes to the workshop and comes back).
• Retire, do not delete. Set scrapped equipment to inactive. Deleting it orphans its history and skews every report that looks back.
• New equipment is registered before handover. Add it to the purchase or installation checklist: no sign off until it has an ID, a tag and a record.
• Audit a sample, not everything. Each quarter, pick a handful of records at random and check them on the floor: is it there, is the tag readable, is the location right. The error rate in the sample tells you whether a bigger clean up is needed.

Watch for duplicates in particular. They appear when two people create the same asset under different names ("Comp 2" and "Air compressor 2"), and they split the history in half, so the machine looks twice as reliable as it is. A quick sort by serial number usually finds them.

A spreadsheet works for a first register. Once work orders, preventive maintenance and breakdowns need to point at it, a CMMS keeps those links in one place. In Solmex, for example, each piece of equipment has its own record with parent, meters, documents and the full work history attached.

Frequently asked questions