Field guide · Supply chain and logistics
Reusable Asset Tracking: Design for Return, Not Just Detection
A successful RTI system connects each read to custody, dwell time, and recovery decisions rather than accumulating location pings.
The Decision Is About the Loop
Reusable totes, pallets, cages, cylinders, tools, and containers create value only when they are available in the right place and condition. Tracking technology can show that an asset crossed a point, but it does not decide who should return it, when dwell becomes abnormal, or how a disputed handoff is resolved.
RAIN RFID is based on the GS1 Gen2 UHF air interface, standardized as ISO/IEC 18000-63. The RAIN Alliance overview explains that the name describes interoperable UHF technology rather than a single vendor product. That common air interface is a useful foundation, but an asset program still needs a common identity and event model.
Checkpoint or Continuous Location
For many returnable transport item programs, the valuable event is a transition: leaving a plant, arriving at a distribution center, entering a wash process, or returning to a pool. Fixed readers at controlled points can capture those transitions without requiring a battery on every asset.
If the requirement is to locate an asset continuously within a large site, a checkpoint architecture may be insufficient. BLE, ultra wideband, active RFID, or a hybrid may be more appropriate, with different infrastructure, battery, precision, and maintenance tradeoffs. Buyers should resist a specification that says “real time” without defining the location precision and update interval needed for an actual decision.
Identity and Custody
The automotive sector’s Returnable Transport Items Identification guideline, published by AIAG, Odette, JAMA, and JAPIA, illustrates why shared identification matters across organizations. A tag identifier should resolve to an asset record with owner, type, status, and lifecycle information. The physical handoff should create an event that both parties can interpret.
Closed loop does not mean simple. Partners may disagree about when custody transfers, which read point is authoritative, and who owns missing or damaged units. These rules should be explicit before a dashboard displays a loss estimate.
Engineer the Tag for the Asset Life
The tag must survive the asset, not merely the pilot. Evaluate mounting, impact, abrasion, washdown, chemicals, temperature, repair, and replacement. Metal assets require purpose built tag structures and mounting. Plastic containers may change RF behavior when filled or nested. Placement must preserve both radio performance and the handling process.
Measure the whole cycle: commissioning, outbound movement, partner receipt, dwell, return, cleaning or maintenance, and retirement. A successful read at dispatch does not prove that the return loop is under control.
Start reporting with an aging distribution rather than a map covered in dots. Show how many assets are within the normal cycle, which have exceeded a defined dwell threshold, where responsibility currently sits, and whether a recovery action was completed. This connects observations to intervention. It also exposes a common limitation: seeing an asset at its last checkpoint may narrow a search, but it does not prove the asset is still there.
Commissioning and retirement deserve equal attention. Reusing an identifier after an asset is scrapped can attach a new object to old history. Define who may create, replace, suspend, and retire records, then test those controls during the pilot.
Buyer Questions
- Which transitions create an operational decision?
- Is checkpoint evidence enough, or is continuous position genuinely required?
- Who owns the identifier and asset master record?
- How is custody transferred and disputed?
- What conditions must the tag survive over the expected asset life?
- How are unreturned, unreadable, retired, and duplicate records resolved?
- Can partners exchange events through a documented interface?
Limitations
Published loss rates and savings are often vendor or program specific. They can suggest where to investigate but should not become universal assumptions. Establish the current pool size, replacement spend, dwell distribution, and search labor before forecasting recovery. The strongest business case may be improved availability rather than a dramatic reduction in nominal asset loss.