Key takeaways
Short answer: An asset tag is the unique, durable identity for a machine. Every work order, failure record, spare part and OEE number attaches to it. When tags are missing, duplicated or inconsistent, all of that data fragments — and no software can fix a broken foundation. Tagging is the cheapest reliability investment and the most commonly skipped. See also maintenance engineer vs reliability engineer.
A tag is not a sticker; it is the primary key for everything you will ever know about a machine. Lose it or duplicate it and every downstream record loses its anchor.
If the same machine is recorded under two tags, its history splits and its real failure rate hides — each "half" looks reliable while the asset is actually a bad actor. If a tag is missing, work gets logged to "the line" instead of the asset, and asset-level analysis becomes impossible. The software is only as good as the identity underneath it.
A pump is tagged P-204 in the CMMS but technicians sometimes log work against the generic "Line 2 pump." Over a year the failures split across two identities, so neither shows an alarming failure rate and the pump never makes the bad-actor list. Only when someone manually merges the records does it become obvious P-204 failed nine times — more than any other asset in the plant. One inconsistent tag hid the single biggest reliability problem on the line.
Tagging is unglamorous, and the cost of skipping it is invisible until you try to analyse failures and find the data fragmented. By then it is expensive to fix retroactively — which is exactly why it keeps being deferred, and exactly why it should not be.
1. Duplicate identities for one asset. Failure history splits and bad actors hide.
2. Generic logging ("the line"). Asset-level analysis becomes impossible.
3. Tags that differ between CMMS and OEE. The two systems cannot be joined.
4. Fragile labels. Tags that wear off in a harsh environment defeat the purpose.
OEE is reported per asset. Without clean tags, OEE rolls up to meaningless line totals and you cannot find the bad actor dragging the number down. The tag is what makes per-asset OEE — and therefore targeted improvement — possible at all.
Fabrico keys OEE, downtime and work orders to a consistent asset identity, so per-machine analysis actually works. Book a demo to see asset-level OEE and failure history done right.
Yes — it is the identity every other record depends on. Broken tags mean broken data, whatever software you run.
Unique, durable, consistent structure, one per asset, identical in CMMS and OEE.
Yes, but retroactive cleanup is costly and error-prone; do it early.
The CMMS and the OEE system must use identical IDs, or the two cannot be joined.
A machine failure history splits across identities, hiding bad actors and understating real failure rates.
Programați o întâlnire individuală cu experții noștri sau înscrieți-vă direct în planul nostru gratuit.
Nu este nevoie de card de credit!
Login
Blog
