Equipment Asset Tags: The Manual, the Service Log, and Who to Call
The manual for the machine in front of you is in a binder, in a drawer, in an office two buildings away. The technician who knows its quirks left in March. The last repair is written on a card taped inside the panel, in handwriting nobody can read. This is the normal state of maintenance information, and it is why the same fault gets diagnosed from scratch three times.
An asset tag fixes the geography of the problem. The information does not need to be centralised in a system everyone forgets to open. It needs to be attached to the thing itself.
What belongs behind the code
Keep it to what someone standing at the machine needs, in the order they need it.
- Identity. Model, serial, year, and where it sits. A contractor who has never been in your building starts here.
- The manual. The actual PDF, not a link to a manufacturer site that reorganised its downloads last year.
- Consumables and parts. Filter sizes, belt numbers, oil grade. This is the section that gets scanned most and saves the most time.
- Service history. What was done, when, by whom. Even three lines beats a card taped inside a panel.
- Who to call. The service contract number and the person who holds it.
Resist the urge to put a login in front of this. A code that asks a contractor to create an account is a code that gets ignored while they phone you instead.
Numbering that survives a spreadsheet
Give each asset an ID and use it everywhere: on the tag, in the URL, in the maintenance sheet, on the purchase record. Something like PUMP-014 or HVAC-RT-03 reads better than a serial number and is far easier to say over the phone.
When you create the codes in a batch, name each one by that ID rather than accepting default names. A folder of codes called qr-1 through qr-200 is unusable six months later, and renaming them afterwards is an afternoon you will not get back. Our naming conventions guide covers the patterns that hold up past the first hundred codes.
Labels that survive the room they live in
The code is only as good as the sticker carrying it. Workshops are unkind to adhesive.
| Environment | What fails | What to specify |
|---|---|---|
| Machine shop, oil and coolant | paper, standard vinyl | polyester or polycarbonate with an aggressive adhesive |
| Outdoors, direct sun | inkjet, unlaminated | UV-stable laminate, or engraved metal |
| High heat near an oven or motor | most adhesives above 80 C | ceramic or anodised aluminium plate |
| Cold store and freezer | anything applied cold | low-temperature adhesive, applied at room temperature |
| Washdown, food production | edges lift, water wicks in | sealed edges, or a code engraved rather than printed |
Two practical rules. Print bigger than feels necessary, because the scan happens in poor light by someone holding a torch: a code around 40 mm is a reasonable floor for a tag read at arm's length. And keep the contrast dark on light, which matters more once a label is dusty. The size guide has the distance maths, and the lamination notes explain why a glossy finish under strip lighting can defeat a camera entirely.
Why these codes cannot be static
A static code carries its destination inside the pattern. That is fine for a code you print today and throw away next week. An asset tag is the opposite: it is riveted to a machine you will own for fifteen years, and everything behind it will change.
| Static tag | Dynamic tag | |
|---|---|---|
| Manual moves to a new file | reprint every tag | edit the destination |
| Service contractor changes | reprint | edit |
| You migrate to a new maintenance system | reprint | edit |
| Machine is sold or scrapped | code points at nothing | repoint or retire it |
| Which assets get looked at | no way to know | scan counts per asset |
That last row is the one people do not expect. Scan counts turn into a maintenance signal: the pump that gets scanned eleven times in a quarter is telling you something the maintenance log is not.
Start with the ten machines that break
Do not tag the whole floor first. Take the ten assets that generate the most calls, give them IDs, create one dynamic code each, and put the manual and parts list behind them. Print the tags in polyester, fix them where a person naturally looks, at eye level and not behind a guard, and leave it a month.
Then read the scan counts. They will tell you which asset to tag next better than any plan you write in advance.
