RFID Tag Commissioning Best Practices

RFID Tag Commissioning Best Practices

Commissioning is the process of encoding a blank or factory-default tag with the correct EPC, writing any required RFID tags." data-category="Data & Encoding">user memory, setting access and kill passwords, and verifying the result before the tag enters service. Poorly commissioned tags cause downstream problems — wrong EPCs, unreadable tags, security vulnerabilities — that are expensive to diagnose and correct after deployment.

What Commissioning Includes

EPC Serialisation Schemes

Before commissioning begins, you must define your EPC structure. Common schemes:

• GS1 SGTIN-96: Retail and supply chain (company prefix + item reference + serial). Encode with the EPC Encoder.
• SSCC-96: Logistics units (pallets, cases) — generated by the WMS.
• GIAI-96: General individual asset identifier — asset tracking, reusable containers.
• DoD UIIdentifier: Defense contractor shipments — see DFARS format.
• Proprietary: Many organisations use a custom encoding; document it in memory planning before deployment.

A commissioning station must receive the correct EPC from the serialisation system for each tag in sequence. Hardcoding or re-using EPCs is a critical error — duplicate EPCs in the field cause incorrect reads and corrupt inventory counts.

Commissioning Station Design

A commissioning station is typically a desktop or conveyor-integrated reader configured to:

1. Singulate: Read only one tag at a time (use a shielded enclosure or close-proximity read zone to prevent adjacent tags from being written).
2. Receive EPC from serialisation system: Via API call, CSV lookup, or direct integration with ERP.
3. Write EPC to tag using the reader's write command (EPC Gen2 UHF standard." data-category="Standards & Protocols">ISO 18000-63 Write to EPC bank).
4. Verify: Immediately re-read the tag and compare the returned EPC bit-for-bit with the intended value.
5. Write user memory if required.
6. Lock relevant memory banks per policy.
7. Record result to commissioning log with: EPC, TID, timestamp, operator ID, result (pass/fail).
8. Reject failed tags — physically route to a reject tray; do not allow a failed tag into the production stream.

Managing Access and Kill Passwords

Passwords default to all-zeros on a new tag, which means any reader can kill or modify the tag. For sensitive deployments:

• Generate a random 32-bit access password per tag or use a master key + TID derivation scheme.
• Store passwords in a Hardware Security Module (HSM) or secure key management system — not in a spreadsheet.
• For retail item-level tagging: set a kill password and record it so the tag can be disabled at point-of-sale.
• For secure asset tags: set an access password so that user memory and EPC cannot be overwritten by unauthorised readers.

The Kill Command permanently and irreversibly disables the tag. Once issued, the tag will never respond again. Use it intentionally; do not issue it during testing or the tag is destroyed.

Batch Commissioning

For high-volume applications (retail apparel, pharmaceutical serialisation), commissioning must be integrated into the production line:

• Source tagging: The manufacturer commissions tags before attaching them to products. This is the most efficient approach — commissioning equipment is built into the production line.
• Commissioning printer: A printer-encoder writes the EPC and prints a human-readable label simultaneously. Output: 20–60 tagged labels per minute.
• Tunnel commissioning: A conveyor system passes tagged items through a read-write enclosure. Throughput: 100–200 items per minute.

All three approaches require the same validation logic: write, verify, log, reject on failure.

Failure Modes and Recovery

Commissioning Quality Metrics

Track these metrics at every commissioning station daily:

If first-pass success rate drops below 98 %, investigate immediately. Common causes: media lot change (different inlay from a new roll), temperature-related antenna detuning in the commissioning environment, or reader port failure.

Commissioning Record Keeping

Every commissioned tag must have a record in the backend system containing:

• EPC (hex, full 96-bit or 198-bit value)
• TID (factory-programmed unique ID — never changes, used for clone detection)
• Commissioning timestamp (ISO 8601 UTC)
• Item master association (SKU, serial number, batch/lot number as applicable)
• Commissioning station ID (for tracing batch issues to a specific station)
• Operator ID (for manual stations)

Retain commissioning records for the lifetime of the tagged item plus the organisation's record retention policy (often 7 years for regulated industries). For pharmaceutical items under DSCSA, these records are part of the serialisation evidence trail.

Re-commissioning Reusable Tags

When a reusable container or asset tag needs a new EPC (item retired, container reassigned), follow a formal re-commissioning procedure:

1. Decommission the old EPC: mark the item as retired in the backend system. Do not delete the record — retain it for audit.
2. Clear the EPC bank: write a null EPC or a specific "unassigned" EPC to indicate the tag is available.
3. Commission the new EPC as if the tag were new: write, verify, associate with the new item master.

Never re-commission a tag by overwriting the EPC without first decommissioning the old record — this creates a ghost record that makes the original item appear still active.

See also: Tag Memory Planning, Understanding EPC, RFID Security Threats.