Service scope and asset register · Lesson 2

An asset register that supports location and maintenance

6 min read

Lesson objectives

  • Create register rows for similar assets with unique IDs, location, boundary, evidence source, and verification status; detect duplicates and missing data.
Reading tools

An asset register is neither a purchasing list nor a collection of equipment names. Its operational purpose is to answer a work request: which asset is affected, where can it be found, what lies inside its boundary, and which maintenance history belongs to it? Two devices may both be labelled ‘air unit 1’ on different floors, while a supplier uses another name on an invoice. If the team relies on names alone, it can attach failures to the wrong machine and order incompatible parts. Begin by declaring the register's scope: which equipment or components need separate records because they have independent maintenance, condition, or replacement decisions? A small building may record an air-handling unit as one asset and its filters as replaceable components linked to it. The appropriate detail follows the decision the team must make; another organization's hierarchy should not simply be copied.

A durable internal identifier should not be built solely from location, since an asset may move. Assign a code that will not be reused. Record the current building, floor, room or area; functional name; equipment type and model; serial number where verified; installation date when supported; service state; responsible owner; and evidence source for each consequential field. Link a child to its parent, such as a pump within a pumping set, when that relationship explains service interruption. Distinguish ‘unknown after review’ from an empty field: the first reports a search without conclusive evidence, while the second may mean no one looked. If a rating plate cannot be read safely, mark it ‘awaiting qualified verification.’ A photograph of a similar machine cannot establish its serial number.

Reconcile evidence from an authorized site walk, asset plate, handover record, manufacturer document, and prior work order. For each conflict preserve both values, their sources and collection dates, then name who will resolve the issue. Search for duplicates using a physical identifier, location, and model together, but never merge records automatically: similar numbers can describe separate machines. Retain location and name changes as events rather than erasing an earlier identity that connects old work orders. After a plate or major component changes, review whether the whole asset remains or has been replaced under the organization's rule. That decision affects performance history and warranty tracking. The principle of managing an asset through its life cycle does not turn an operational register into an accounting valuation or a financial recognition decision; those belong to other qualified roles.

Review the register when an event affects a decision: installation, relocation, withdrawal from service, maintenance that reveals a plate discrepancy, or a conflict between an occupant's and a technician's account. Measure completeness against fields needed for use, not the percentage of cells filled with any text. If a hundred location cells merely say ‘building,’ the technician still cannot find the device. Test a site sample: does an ID lead to one physical asset? Does a work order return to the right history? Can the source of a disputed serial number be retrieved? If not, the improvement may be a location naming rule or a post-visit update step, not a new software purchase. Connect the register to the service card and work order so data quality has a visible effect on diagnosis and maintenance decisions. Apply appropriate access to photographs and site plans; giving every provider a detailed location register without a work need can expose sensitive site information.

Lesson summary

Create register rows for similar assets with unique IDs, location, boundary, evidence source, and verification status; detect duplicates and missing data.