Fiber asset management

Assets need a physical identity, not just a database row

A record is only as good as the crew's ability to confirm it in the field. Two joint boxes fifteen metres apart, in a trench with no landmarks, are indistinguishable on a phone map when GPS accuracy is twenty metres. The result is work logged against the wrong asset, and a record that quietly becomes fiction.

Physical tagging closes that gap. An NFC tag or a printed QR code on the enclosure means the crew reads the identity from the asset itself instead of inferring it. Dual-encoding matters in practice: NFC reading from a browser is currently an Android capability, so every tag should also carry a scannable code that works on any camera phone.

Scanning as arrival proof

The same scan answers a second question that contractor management depends on: did the crew actually reach the site, and when? A scan recorded with its own timestamp, the scanning user and the device's position produces arrival evidence that does not rely on anybody's word.

The distance between where the scan happened and where the asset is recorded should be calculated server-side from the stored geometry. A distance computed on the device is a number the device chose, which is exactly the wrong property for something used in a contractor review.

Consumables move through states, not spreadsheets

Splice enclosures, pigtails, patch cords, cable by the metre and connectors are where material loss accumulates. Tracking them as a list of quantities in a spreadsheet tells you what was bought, never where it went.

Treating each trackable item as a record with an enforced state machine — in warehouse, on truck, on ticket, installed, returned, lost or retired — means the question 'where is it' always has an answer, and the transitions themselves are the audit. A technician can move their own assigned items forward through the states they are allowed to use; they cannot quietly move an item back into the warehouse.

• In warehouse to on truck, then on ticket when it is committed to a job.
• On ticket to installed, returned or lost — a decision that has to be made, not left blank.
• Retired is terminal; nothing is hard-deleted, so the history stays intact.

An audit trail you can hand to someone else

The test of an asset system is whether a third party — a regulator, a customer's technical team, a finance reviewer questioning a contractor invoice — can follow what happened without asking anyone to explain. That requires events that are written once and never edited, evidence that carries its own location and timestamp, and vocabularies that mean the same thing in every region.