An HF/NFC inlay that works in free air may behave differently after it is attached to a steel cabinet. The purchase decision must cover the whole installed assembly: tag technology, antenna and shielding construction, adhesive or housing, mounting position, asset surface, reader or handset, application and required operation.
This guide is for asset-management integrators, maintenance teams and handheld-terminal buyers. Its pump-cabinet scenario is editorial, not a customer deployment or AIDC GO device test. AIDC GO has not documented HF/NFC support for every handheld model; begin with the product overview, then use Integration Support and Contact to request evidence for an exact candidate configuration.
Separate protocol compatibility from metal compatibility
The tag must first support the required air interface and data operation. The terminal and application must then support that same operation. The HF/NFC compatibility guide explains why 13.56 MHz alone does not establish compatibility across ISO/IEC 14443, ISO/IEC 15693, NDEF and protected application data.
Metal adds a different question. STMicroelectronics' current NFC Touchpoints guidance, read 2026-09-22, says nearby metal can distort the magnetic RF communication and presents ferrite protection as a way to enable a sticker tag on metal. It also recommends evaluating the final touchpoint in situ. This supports testing the mounted construction; it does not establish a universal ferrite thickness, range or handset result.
An ordinary wet inlay plus an improvised spacer is not automatically equivalent to a supplier's on-metal label. Ask for the exact finished part number and layer construction. Shielding material, antenna geometry, adhesive, overlay and housing can all be part of the specified product.
Specify the complete line item
Identiv's RFID Tag on Metal labels datasheet, revision 2022-06-17, describes high-frequency labels for metallic environments with an antenna inlay, chip, ferrite insulator layer, label top, adhesive and liner. It lists ISO/IEC 15693 and ISO/IEC 14443 chip options. That family is a third-party construction example; the selected chip, size, material and option still need an exact orderable reference.
HID's current IQ On-Metal Labels page, read 2026-09-22, separately lists NFC Tag Type 2 and RAIN UHF variants and on- or off-metal versions. The page demonstrates why a family name is insufficient: frequency, protocol and mounting version must remain on the line item. It is not evidence that an AIDC GO reader supports those labels.
| Assembly decision | Evidence to request | What a free-air read cannot prove |
|---|---|---|
| Tag technology and data | Exact chip or tag option, protocol, programmed sample and required operation | That the mounted tag remains readable or that the application accepts its data |
| Metal-control construction | Exact on-metal part, ferrite or other documented structure and supplier drawing | That an ordinary label with an improvised spacer is equivalent |
| Attachment | Approved adhesive, housing or fastener; surface preparation and cure instructions | That the label remains fixed through cleaning, impact or temperature cycles |
| Mounting location | Marked asset drawing, curvature, nearby edges and obstructions | That any position on the same asset produces the same coupling |
| Terminal and application | Exact model, hardware option, OS, API and expected business result | That detecting the tag completes the asset transaction |
Walk through an editorial pump-cabinet trial
Assume a maintenance team wants a tap to open the record for steel pump cabinet P-204. The proposed application expects an NDEF URI on a named NFC tag option. The cabinet has a painted flat face near its service door. These details and outcomes are teaching assumptions.
First, the team reads a loose programmed sample and confirms the expected protocol, payload and asset mapping. That closes the data-path question only. Next, it places an ordinary off-metal sample directly on the cabinet and observes inconsistent detection. The observation is retained; it is not converted into a universal range claim.
The team then installs the exact supplier-specified on-metal label construction at the marked location, following the documented surface preparation and orientation. With the shortlisted terminal and application, the tester approaches from the working direction, detects the tag, reads the expected payload and verifies that it opens P-204 rather than a nearby asset. The test is repeated after the specified installation or cure condition and with the door in representative positions.
If the tag is detected but the wrong record opens, the metal construction is not the correction. Check the payload and asset mapping. If the application receives no tag, compare the raw detection path, tag protocol, terminal option, location and installed construction before blaming one component. The NFC UID mapping guide covers the separate identifier-to-record problem.
Keep mounting changes inside configuration control
Do not approve a sample and then substitute a thinner label, different chip, different adhesive or unrecorded spacer. A change to the shielding or separation can change the antenna environment. A change to chip or data format can change the software path. Record the exact tag reference and mounting revision on the asset configuration.
The asset surface also matters. Painted steel, bare metal, a curved pipe, an aluminium enclosure and a recessed cavity are not interchangeable merely because all are called metal. Record coating, curvature, available flat area, edge distance, cleaning process, impact exposure and whether removal must show evidence or preserve the asset finish.
If the attachment method changes during maintenance, repeat the relevant installed test. The tag-replacement guide addresses retirement and remapping, while the UHF metal-attachment guide deals with UHF tag housings and attachment. Neither result can be copied to an HF/NFC assembly without corresponding evidence.
Test the operation that the project actually needs
A positive test should state more than “tag reads.” Record the mounted asset, exact label, terminal and OS, application build, reader/API path, requested operation, raw result, parsed result and business record. Include the intended approach direction and operator position. Do not publish a distance value unless the actual project has measured it under defined conditions.
Use negative and boundary cases: the same off-metal label attached to metal, an on-metal label with the wrong data, a nearby second asset, a misaligned approach, an unregistered tag and a damaged or partly detached assembly. The application should distinguish detection failure, unsupported technology, invalid payload and unknown record where those outcomes matter.
Environmental suitability requires its own evidence. A supplier's on-metal construction does not automatically establish chemical, wash, outdoor, impact or temperature suitability. Nor does a durable tag rating permit the handheld to enter the same environment. Match each environmental claim to the exact tag and device documentation.
Bring samples and a mounting drawing to the decision
Provide the asset material and finish, photographs, marked mounting location, required data operation, exact candidate label references, attachment constraints, expected service life and replacement procedure. Include non-production samples of every tag variation and the exact terminal/application build.
Ask the tag supplier to confirm the finished on-metal construction and installation instruction. Ask the application owner to confirm protocol, payload and asset mapping. Ask the device supplier for model-specific HF/NFC hardware and interface evidence. Then run the installed test instead of extrapolating from a loose tag.
The defensible purchase result is a reproducible mounted assembly with a bounded operation. It does not claim that every NFC tag works on metal, that every ferrite-backed label works with every device, or that a successful tap proves asset authenticity or business authorization.