Libraries RFID field guide

HF or UHF RFID for libraries: how to assess compatibility

A library frequency decision begins with the installed tag estate, data model and workflows. HF is widely established for close-range circulation and item security; UHF can support rapid inventory and longer controlled zones. Migration and coexistence require explicit compatibility tests, not assumptions.

Tags, self-service stations, staff workstations, gates, handhelds and the library system form one service. Changing frequency may affect every layer and every already-tagged item.

Define the business and engineering decisions first

Before comparing models, frequencies or read ranges, fix the process boundary, accountable owner and evidence the operation must produce. Record these decisions in the project scope.

Inventory the installed tags, data profile and equipment
Define circulation, return, inventory, search and security requirements
Decide whether to retain, migrate or run parallel technologies
Set interoperability and item-conversion rules

Control the failure conditions most often missed

RFID results depend on the item, environment, movement, device configuration and event logic together. Control risk through design constraints and exception handling rather than post-deployment interpretation.

A new device reads the frequency but not the existing data profile
Security behavior differs between old and new equipment
Mixed tags confuse patrons and staff
Migration labor and downtime are omitted from the business case

Validate end to end under representative conditions

Test representative books, discs, media and special items across every required device and library-system transaction. Include old tags, new tags, mixed populations, offline use, security state and failed conversion.

Keep item identity and circulation state authoritative in the ILS. Reader adapters should expose consistent item and security operations while preserving the selected ISO 28560 or regional profile.

How REAOX frames the project decision

First turn the physical read into an explainable, traceable business event; then decide whether it satisfies the target workflow. Results that have not been validated at the target site should not be presented as a universal performance promise.

Review the responsibility boundaries across tags, devices, middleware and business systems together, and support acceptance with a written method, denominator and exception record.

Procurement and pilot checklist

Installed tag frequencies, memory and data profile
Self-service, staff, return, gate and inventory equipment
ILS identifiers, circulation and security operations
Migration, coexistence and item-conversion procedure
Special materials, media and representative collection matrix
Interoperability test and signed acceptance evidence

Questions buyers ask first

Can a UHF reader use existing HF library tags?

No. HF and UHF use different air interfaces and require compatible tags and reader hardware.

Does ISO 28560 require one frequency?

The series addresses library RFID data and implementation. Verify the applicable part, regional profile and chosen air interface with project specialists.

Can two frequencies coexist during migration?

Yes, but every workflow, item status, patron instruction and exception must be designed and tested for the mixed period.

Standards and authoritative references

Continue the project review

Turn the requirement into a verifiable project scope

Share the installed tag estate, equipment, data profile, ILS and migration constraints. REAOX can prepare a compatibility and coexistence test matrix.

Discuss an RFID project