Skip to content

Free template

Updated

Equipment register template

An equipment register is the master list of the assets a plant maintains: one row for each plant, area, line, machine and component, with a unique ID, where it sits in the hierarchy, what it is, how critical it is and how it is maintained. It is the base for every maintenance plan, spare parts list and work order, and it is the first thing to clean up before a maintenance system is set up. This template has the columns that matter: ID, parent, location, make, model, serial number, year, criticality class A, B or C, PM strategy, PM frequency, owner and documents. The Excel version checks every row for duplicate IDs, missing parents, missing criticality or PM strategy, class A assets on run to failure and missing owners, and summarises the register by level. The PDF has the blank form, the hierarchy, an ID rule and a worked example.

Free to use: print it, copy it and edit it for your team. Enter your name and work email once to download.

Page 1 of the equipment register templateFields for site, area, date and prepared by above a table with columns for asset ID, name, level, parent, location, make and model, serial number, year, criticality, PM strategy, frequency, owner and documents.
Five-level asset hierarchyCriticality A, B and CPM strategy and frequencyPer-row data checkID naming ruleWorked example
Filled-in Equipment register template: sixty made-up assets on two packaging lines
The same sheet filled in with the worked example (page 3 of the PDF, illustrative numbers). Open full size (opens the picture in a new tab)

When to use it

When to use an equipment register

  • Before you load assets into a maintenance system, so that you migrate a clean list and not an old one.
  • When you cannot say how many machines you have, which are critical or which have no maintenance plan.
  • To set up preventive maintenance: you need a list of assets, each with a strategy and a frequency.
  • To prepare for an audit, an insurance review or a spare parts review, which all start from the asset list.
  • Not as a work order log. The register says what exists and how it is maintained; the work done on it goes in the maintenance system or a machine history record.

How to fill it in

  1. 1

    Build the hierarchy first

    List the plant, then areas, lines, machines and components. Give each a unique ID and the ID of its parent. Use short codes that carry the place, such as PK-L1-FIL for the filler on packaging line 1.

  2. 2

    Register what you plan work on

    A machine is on the list if you inspect, service or repair it. A component is on the list if you service or replace it separately. Do not list every bolt and every cable.

  3. 3

    Record the nameplate facts

    Make, model, serial number and year come from the nameplate, not the purchase order. They are what the technician and the supplier need when a part is ordered.

  4. 4

    Set criticality

    Give every machine and component a class: A if a failure stops the line or is a safety, quality or environmental risk, B if it slows the line, C if it has little effect. Use one test, in the same way, across the plant.

  5. 5

    Choose a PM strategy and a frequency

    Run to failure for cheap, safe, quick fixes; time based for a fixed interval; condition based where a reading tells you when to act. Add the frequency and an owner. Class A on run to failure is a flag to review.

  6. 6

    Clear the flags

    Read the data check column and the summary. Fix duplicates, missing parents, missing criticality and missing owners, then repeat until the register is clean.

A filled-in example

Illustrative, not a benchmark

An invented plant has two packaging lines, each with eight machines, and 60 assets on the register in all.

  • The hierarchy runs from the plant and the packaging area to two lines, 16 machines and 40 components, such as the fill pump on each filler.
  • Eight assets are class A: each line's filler and case packer, and the filler's fill pump and servo drive.
  • Three machines or components have no PM strategy: the label head on line 1, and the film carriage and the conveyor drive motor on line 2.
  • The data check flags exactly those three, and the summary shows the register is 57 of 60 rows clean.

The three gaps are the first work: decide a strategy for each, set a frequency and give it an owner. Until then they are maintained by habit, not by plan.

Common mistakes

  • Listing everything

    A register of every bolt cannot be kept up to date. Register what you plan, service or replace as a unit.

  • Reusing IDs

    When an asset is scrapped and its ID is given to a new one, the history of the two is mixed. Mark the old one Decommissioned and give the new one a new ID.

  • Criticality set by loudest voice

    If class A goes to whatever production complains about most, the class means nothing. Agree one test and apply it the same way to every asset.

  • No owner

    An asset with no named owner is not maintained by anyone. Put a person or a role against every machine.

  • Not updating it

    New machines, moves and retirements are the usual drift. Make a register update part of installing or removing equipment.

Download the template

Free to use: print it, copy it and edit it for your team. Enter your name and work email once to download.

Run this template in LeanSuite

LeanSuite works alongside your CMMS rather than replacing it: when a scheduled PM comes due or an operator tags an abnormality it creates the work order and routes it to maintenance, and checklists can be assigned to an asset with a repeat rule.

See it in a 45-minute demo

FAQ

Equipment register template: common questions

  1. An equipment register is the master list of the assets a plant maintains, one row per asset, with a unique ID, its place in the hierarchy, its make and model, its criticality, its PM strategy and its owner. It is the base for maintenance plans, spare parts and work orders.

  2. A register is the list of assets and their facts. A CMMS is the system that schedules work, holds work orders and records history against those assets. A clean register is the first thing a CMMS needs.

  3. Ask what happens if it fails. A is a stopped line or a safety, quality or environmental risk with no quick workaround. B is a slowdown that a spare or manual workaround covers for a shift. C has little effect. There is no standard, so write your test down and use it the same way everywhere.

  4. Use short, unique codes that carry the place, such as the area, line and machine, and add a running number for each component. Never reuse an ID and avoid spaces. Make the ID readable so that a technician knows where an asset is from its tag.

  5. As many as you plan work on, and no more. A machine belongs on it if you inspect, service or repair it; a component belongs on it if you service or replace it as a unit. A list that grows to every bolt is not kept current.

More free templates

All templates
Browse all 236 templates

Can't find the template you need?

Tell us what you're looking for. We'll make it and send it to your inbox, free.

A shift handover sheet, a red tag log, a changeover checklist for one machine: if your team uses it on the floor, ask.

By sending this form you agree to our Terms of Service and Privacy Policy.

Pass it on

We want LeanSuite to be the best place on the internet for lean help. If this was useful, send it to someone on your team or in your network who needs it.