How do you program an NFC tag?

Write an NDEF record containing a URL that points back to your asset system, including the tag's identifier, then pair that tag to the specific asset in the system while standing at it. The chip's factory UID is what the record is keyed on; the URL is what makes the tag useful to a phone that does not have your app.

Can an iPhone read these tags?

Not from a web page. Reading NFC in the browser is an Android and Chrome capability. That is why every tag should also carry a printed QR code holding the same identifier, so an iPhone camera produces the same result as an Android tap.

What is asset tagging software actually for?

It links a physical marker on equipment to a record that holds the equipment's type, location, condition, history and ownership — and it captures each scan as evidence of who was where, when. Without the software half, a tag is just a sticker.

Do tags work where there is no mobile signal?

They should. A scan taken in a manhole with no coverage is stored on the handset with a one-time key and uploaded when signal returns, so the record is never lost and never written twice.

What happens when a tag is damaged or lost?

The tag is marked lost or replaced rather than deleted, and a new tag is paired to the same asset. Every scan of the old tag stays in the history, still attached to the asset it identified.

Back to overview

Pairing and programming NFC tags for field assets

Programming an NFC tag for a field asset means writing a stable identifier to the tag, then pairing that identifier to a specific cabinet, joint box, splitter or piece of stock in your asset system, so that a phone held against the tag resolves to one — and only one — record. The writing part takes seconds; the pairing and the audit trail are what make it useful a year later.

What actually gets written to the tag

Every NFC tag ships with a factory UID burned into the chip at manufacture. That UID is unique and cannot be changed, which makes it the right thing to key an asset record against. You do not need to write the asset name, the customer or the coordinates onto the tag itself — the tag is a pointer, not a database.

What you do write is an NDEF record containing a URL that resolves back to your system, so that a phone without your app installed still does something useful when it touches the tag. A tag whose only content is a raw serial number is a dead end for anyone outside the team.

Keeping the payload to an identifier also means a re-tagged asset costs nothing to correct: you retire the old pairing and create a new one, and every historical scan still points at the right history.

Factory UID: the unchangeable chip serial, used as the key in the asset system.
NDEF URL record: a link of the form https://your-domain/scan/<tag-uid>.
Nothing else — no names, no coordinates, no customer data on the tag.

Choosing tags that survive outdoor plant

Tags on fibre plant live in manholes, on poles and inside enclosures that flood, bake and get painted over. A paper label with an inlay is fine on a warehouse shelf and useless on a duct chamber. Look for an on-metal tag where the surface is metallic, because an ordinary inlay laid flat on steel will not read at all.

Chip capacity matters less than people expect. A URL of sixty or so characters fits comfortably in the smallest common chip, so the deciding factors are the housing, the adhesive or mounting method, and the temperature and ingress rating.

On-metal tags for cabinets, ODFs and steel enclosures.
An ingress rating suited to buried chambers, not just splash resistance.
A housing that accepts a printed QR label on the same face.
Enough chips in one order that a whole region uses the same type.

Programming and pairing, step by step

The sequence below is the one a field crew follows the first time an asset is tagged. It is deliberately short, because anything longer gets skipped on a hot afternoon with four more sites to visit.

Stand at the asset and open it in the field app, so the pairing is made against the record you can see in front of you.
Write the tag with the asset URL, using the phone's NFC writer or a desktop encoder for a batch.
Hold the phone to the tag to read it back — the UID is captured by the app, not typed.
Confirm the pairing. The system records who paired it, when, and where they were standing.
Fix the tag in place and stick the matching printed QR label beside it.

Why every tag also carries a printed QR code

Reading an NFC tag from a web page works on Android in Chrome and does not work on iPhone at all. Any tagging programme that assumes NFC everywhere will quietly exclude every technician, contractor or customer engineer carrying an iPhone.

The fix is to dual-code: the same identifier goes on the chip and into a printed QR code on the label. A camera scan of that QR resolves to exactly the same asset page and records exactly the same scan event, so the two paths are interchangeable and reporting does not have to care which was used.

What a scan is worth as evidence

A scan is only useful if it is trustworthy. That means the record is written by the server, not the phone: the time comes from the database, the distance between the scan position and the asset's stored position is computed server-side from the coordinates, and the entry can never be edited or deleted afterwards.

With that in place, a scan becomes real arrival proof. It answers 'was a person physically at this cabinet' rather than 'did somebody tick a box'. It also drives inventory movements — the same scan that proves arrival can assign a splice enclosure to a job or mark a drum of cable as installed.

Who scanned, from the signed-in account — not a typed name.
When, from the server clock.
Where, and how far that is from the asset's recorded position.
Why: identification, arrival proof, an inventory check, a connection trace, or a stock movement.
How: phone NFC, camera QR, a fixed reader, or manual entry as a last resort.

How FiberOps handles tagging

Tagging in FiberOps is part of the repair workflow rather than a separate asset-tagging tool, so a tag is paired by the crew standing at the asset and every later scan lands on the job they are working.

Pair a tag to any of the eight asset types, or to a trackable stock item, from the phone.
Dual-coded by default: the chip and the printed QR resolve to the same record and produce identical scan records.
Distance from the asset is computed by the database from real coordinates, never sent up by the phone.
Scan records are append-only — nobody, including an administrator, can edit or remove one.
Tags are retired by status rather than deleted, so the history of a replaced tag survives.
Scans taken with no signal are held on the handset and upload when coverage returns, without ever duplicating.

Common questions

How do you program an NFC tag?: Write an NDEF record containing a URL that points back to your asset system, including the tag's identifier, then pair that tag to the specific asset in the system while standing at it. The chip's factory UID is what the record is keyed on; the URL is what makes the tag useful to a phone that does not have your app.
Can an iPhone read these tags?: Not from a web page. Reading NFC in the browser is an Android and Chrome capability. That is why every tag should also carry a printed QR code holding the same identifier, so an iPhone camera produces the same result as an Android tap.
What is asset tagging software actually for?: It links a physical marker on equipment to a record that holds the equipment's type, location, condition, history and ownership — and it captures each scan as evidence of who was where, when. Without the software half, a tag is just a sticker.
Do tags work where there is no mobile signal?: They should. A scan taken in a manhole with no coverage is stored on the handset with a one-time key and uploaded when signal returns, so the record is never lost and never written twice.
What happens when a tag is damaged or lost?: The tag is marked lost or replaced rather than deleted, and a new tag is paired to the same asset. Every scan of the old tag stays in the history, still attached to the asset it identified.

More answers are on the fiber operations FAQ.

See it on your own network

We will walk through your plant data, your SLA tiers and your field workflow — not a generic demo dataset.

Request a demo