A tag on every asset, and one record behind it.

The problem

A vessel's equipment register is a long and detailed document: 1,251 numbered equipment lines in the fleet export we worked from, covering machinery, systems and structure. What it has difficulty doing is answering a simple question in the engine room — which component is this, and what do we know about it?

In the export we received, fewer than five per cent of lines carried a physical location identifier, and most carried no serial number to search on. A line item in a database is only useful to a superintendent, a class surveyor or an assistant engineer if the physical component can be found and identified in the time available: in a dark machinery space, under lagging, after a repaint, with a crew that changes every contract.

What we designed

Three things that only work together: a label on the asset, a platform that resolves the label to a record, and an inspection path that keeps working when the vessel has no connectivity.

• One label, two readers. A passive UHF RFID inlay co-printed with a QR code, both carrying the same short identifier. A phone camera reads the QR without an application install; a handheld reader sweeps a space in one walkaround. Both resolve to the same record.
• The tag is an address, not a dossier. The label carries an identifier only. Maker, serial, condition, certification and location stay in the platform, where they can change without re-tagging anything.
• No re-typing. The existing maintenance export is imported as received and stays the master list. The platform adds identity, condition history, documents and readings against each line; it does not reissue the register's numbering.
• Evidence, not assertion. Every read, inspection and field change is attributable to a person, a device and a time, and is available as the record behind a claim.

Decisions that mattered

1. Two read paths, deliberately not equivalent. The QR path is for a person looking at one asset. The RFID path is for a person who needs to know what is in a space without opening panels. A campaign with only one of them either cannot be verified in bulk, or cannot be read by the crew who happen to be on board.
2. The queue applies once. Inspections and field changes are written to the device first and synchronised later. A repeated upload does not duplicate a record or a reading, and every queued operation carries the user, device, timestamp and prior value.
3. No silent overwrite. If two devices change the same field offline, both values are kept, the conflict is flagged for the office focal point, and the record shows that it happened. A value that disappears without a trace is a data-integrity failure, not a convenience.
4. The register stays the master. Where the source register and the platform disagree, the discrepancy is listed and resolved by a person, rather than corrected quietly in the background.

How the work is phased

The campaign is divided by space and system, so that a defined population is complete and verifiable before the next one begins. A survey phase fixes the label specification, adhesive and placement standard against the surfaces actually present on board before any label is printed. Machinery and electrical spaces follow, then hull, deck, life-saving and accommodation. Readers, maintenance-system integration and reporting come last, once there is something worth reading.

Each phase closes on a gate the client signs, with a verification sample read by a reader other than the one used to tag and by a person other than the one who tagged. Every label is photographed in place, and tag identifiers, register lines and physical assets are reconciled before the gate: no orphan tags, no duplicate identifiers, no line without a decision.

What it does not do yet

• No class certification is claimed. The platform records condition and evidence; it does not replace a class society's survey or its approved documentation.
• Label performance is fixed at survey. Inlay, face material and adhesive are selected against the surfaces on board and signed off before printing. Read range is not stated until that selection is made.
• The tagging campaign is physical work. Software cannot tag a vessel. The labour, the permits and the access windows are part of the delivery, under the vessel's own permit-to-work regime.
• Automated defect detection is not in scope. Condition is recorded by the person inspecting the asset.

A label that carries an address stays correct for the life of the asset. A label that carries the maker's data is wrong the first time a component is replaced.