Asset Tracking Across the Warehouse Door: Joining Indoor and Yard Records

An asset leaves the warehouse and its indoor marker stops moving. Another device appears on the yard map, but the dispatcher must establish whether it represents the same asset. Two working tracking systems can still leave an incomplete handover.

I. Keep the positioning methods distinct

Indoor RTLS uses installed reception infrastructure and a local spatial reference. Outdoor GPS or GNSS produces geographic coordinates. Doorways, covered areas and other obstructions need separate reception checks.

ORBRO RTLS and outdoor tracking address different environments. Joining their records requires a defined device combination, identity mapping and integration scope; displaying two maps does not create a continuous track.

II. Connect devices through the asset identifier

Use the asset number as the stable identity, mapping indoor tag IDs and outdoor device IDs to it. Record when the relationship changes during device replacement or transfer into a transport container. A container's position does not by itself prove which goods remain inside.

Consider preserving observation time, receipt time, positioning method and validity separately. Align clocks and time zones before interpreting event order.

III. Make the boundary gap visible

Choose test checkpoints at the warehouse exit, external staging area and vehicle handover. Compare the final valid indoor observation with the first valid outdoor one. Show any gap rather than inventing a route through it.

Where reception is difficult, evaluate gate observations or a confirmed operational handover as supplementary evidence. A crossing event and a current yard position answer different questions.

IV. Follow one asset through a complete trial

V. Work through one shipment before scaling up

Consider an illustrative workflow rather than a customer result: a reusable cart moves from an indoor staging lane onto a trailer and then to a yard holding area. Keep the cart's asset number stable. Record the effective periods for its indoor tag and outdoor device associations. If the trailer's position is used as a proxy, a confirmed loading relationship is also needed. A departing trailer does not establish that a particular cart is on board.

For a US distribution center with multiple docks and trailer parking lanes, test the covered dock approach as well as the open yard. These are site conditions to inspect, not assumptions about every American facility. Check whether the device obtains a usable position and whether that observation reaches the operational system. A stalled marker can reflect a measurement gap, a transmission delay or an identity mismatch, which require different remedies.

VI. Define what happens when old observations arrive late

Include delayed delivery in the integration trial. After connectivity returns, earlier observations may arrive after newer ones. Sorting only by receipt time can make an old observation appear current. Agree with the integration team on observation timestamps, clock checks, duplicate handling and update precedence. Treat these as requirements to verify rather than standard capabilities of every tracking product.

Consider displaying the last valid observation with its age. When the site's freshness limit is exceeded, show that the current position is unconfirmed. Set that limit around the task, expected update cycle and asset movement; a parked returnable cart and an actively dispatched vehicle may need different treatment. A visually continuous line through a coverage gap is not evidence of the route actually taken.

VII. Give the dispatcher an exception procedure

Device removal for charging, tag replacement and a mistaken association can interrupt a handover even when reception is good. Before choosing between conflicting positions, verify the physical asset and the attached identifiers. Preserve the correction time and the reason for the change. Keep the handover pending when the asset itself has not been confirmed.

A practical checklist identifies the asset, checks the effective device association, separates observation time from physical handover time, and records the evidence used during the gap. Repeat the procedure on the return journey. The receiving team should be able to follow the same asset without reconstructing its identity from device names.

VIII. Measure identity errors separately from coverage gaps

Record the total number of trial movements alongside the number successfully reconciled. Review coverage gaps, incorrect associations and missing physical handovers as separate categories. Otherwise a better radio installation can conceal an unchanged operating-process problem.

Test loading, doorway passage, yard dwell and return with the same asset. Include a device change and a communication interruption. Ask the dispatcher to decide which record is current enough to act on.

The goal is an understandable asset history, not one positioning technology everywhere. Share the site drawings and device register with ORBRO to define the handover and validation requirements.

Compare trials with similar routes, loads and operating periods. A successful quiet-day demonstration does not settle a busy-dock handover. Bring the route plan, device register, handover procedure and acceptable data-gap criteria to ORBRO so the proposed integration can be checked against the actual workflow.