Skip to content
Language: EN

What do you do with a tag that outlives the asset?

Retire the record rather than chasing the tag. A disposed asset whose identifier still resolves is a machine that appears to exist, and eventually somebody schedules maintenance on it or counts it in an audit. Closing the record is the operation that matters.

Retire the record

When an asset is disposed of, close its record and mark the identifier retired. That is a database operation and it takes seconds.

An identifier that still resolves to an active record is worse than a missing tag, because the system asserts the asset exists.

The failure is quiet and delayed: a maintenance schedule includes a machine that was scrapped, or an audit counts an asset nobody can find, and someone spends an afternoon on it.

Make retirement part of the disposal checklist rather than something remembered afterwards, because after the equipment has left nobody is thinking about tags.

The tag leaves with the asset

Most tags go wherever the equipment goes: to a buyer, a scrap merchant or a recycler.

A retired identifier that resolves to nothing useful is harmless. One that still returns your asset record is a small information leak about your site, your equipment and your systems.

Decide what a retired identifier returns. A neutral page is better than an error, and both are better than the record.

Where equipment is sold on, removing the tag is worth doing if it carries printed information about your organisation.

Reusing tags

Technically straightforward if the tag was never locked and the identifier is reassigned in the system.

Physically rarely worth it. A tag removed from equipment has aged adhesive, a bent body and years of environment behind it, and refitting it is a good way to install a failure.

Where tags are in holders and simply unclipped, reuse is reasonable and the tags should be verified before going back into stock.

And never reuse an identifier for a different asset. Reassigning a tag is fine, reassigning a number is how two machines end up sharing a history.

The inverse problem

The commoner case is the opposite: the tag fails and the asset remains.

The replacement must inherit the identifier, so the history follows. A new number means a machine that appears to have been installed yesterday.

Where the chip mirrors its identifier and the system maps it, that means mapping the new tag to the existing asset record rather than creating anything.

Record the replacement with a date. A tag replaced twice in a year is telling you the mounting or the environment specification is wrong.

Frequently asked questions

Should I remove tags from disposed equipment?

Retiring the record matters more. Removing the tag is worth it where it carries printed information about your organisation.

Can I reuse a tag from scrapped equipment?

Rarely worth it. Aged adhesive and a bent body make refitting a way to install a future failure.

What should a retired identifier return?

Something neutral rather than the asset record or an error. Decide it deliberately, since the tag has left your site.

How do I replace a failed tag?

Map the new tag to the existing asset record so the history follows. A new identifier creates a machine with no past.