Begin with the next operational decision
A vehicle-yard tracking system should help a person find the right vehicle and decide what may happen next. A dot on a map answers only part of that question. The car may be awaiting inspection, held for repair, cleared for dispatch or already collected while its tag remains behind. Start with one costly uncertainty: finding a rental return, locating a finished vehicle, or preventing a held vehicle from entering a shipping queue.
This guide concerns whole vehicles in factory, distribution and rental yards. Write down the decision, its owner and the evidence required before choosing locating equipment. If staff need a staging zone, a highly detailed map may add little. If they must distinguish adjacent bays, zone presence alone may be insufficient. Test against the task that people actually perform.
Keep identity, observation and permission separate
On a narrow screen, scroll the table sideways. Keyboard users can focus the table region and use the arrow keys.
| Record | Example field | Question to resolve |
|---|---|---|
| Vehicle identity | VIN or controlled yard record | Which physical vehicle is this? |
| Tag association | Tag ID, vehicle ID, assignment time | Is this tag still attached to that vehicle? |
| Location observation | Zone or position, observation time, source | Where was it observed, and how recently? |
| Work status | Inspection result, hold reason, responsible team | What work is complete or still required? |
| Release authorization | Approver, release time, destination | Who authorized this vehicle to leave? |
Define which system owns each record. A reader can observe a tag without knowing whether a mechanic completed a repair. Likewise, a completed work order does not prove that the vehicle is at the loading point. Show both facts with their timestamps instead of collapsing them into a single green icon.
At arrival, verify the vehicle-to-tag association. At departure, close it and account for the tag before reuse. Keep a traceable correction process for wrong assignments. The component-level companion, RFID in automotive remanufacturing, applies the same identity discipline to parts and work orders.
Read an event trail without overstating it
Consider this invented training example: a vehicle arrives at 08:00, enters inspection at 08:20, receives a hold at 08:35, is released at 10:05 and exits at 10:20. Arrival-to-exit dwell is 140 minutes; the recorded hold lasts 90 minutes. Those figures describe different intervals. The remaining 50 minutes are not automatically productive work: they also include waiting and movement.
Now suppose the latest location observation is 09:50 in the repair zone. The 10:05 release event does not refresh that observation. Display the observation’s age and request confirmation before sending a driver there. Store the time an event happened separately from the time a delayed message reached the system. Decide how duplicates, out-of-order messages and corrected records affect the timeline.
GS1 EPCIS provides a standardized approach to sharing visibility events across applications. It can inform an integration discussion, but using similar worksheet fields does not make a system EPCIS-compliant. Agree the actual identifiers, event definitions and interfaces with every participating system.
Measure the pilot against independent observations
Choose representative routes, parked densities, indoor transitions and busy periods. Establish ground truth with an independent observer or reconciled movement record. Include a missed observation, an incorrectly assigned tag and a network interruption in the recovery plan. Keep ordinary yard traffic rules in force throughout the trial.
- Successful retrieval: out of all assigned retrieval tasks, how many found the correct vehicle at the displayed location without a second search?
- Freshness: how old was the observation when someone relied on it?
- Recovery: how many tasks required a manual lookup, and how long did recovery take?
- False events: how many arrivals, movements or exits were recorded when they did not occur?
- Work accuracy: did the release queue agree with the authoritative hold and completion records?
Write acceptance thresholds before the trial. Report the denominator, excluded cases and operating conditions alongside each result. A successful manual recovery should remain visible; it should not be relabeled as a successful automatic observation. Compare staff time and operating cost against a measured baseline before projecting savings.
Plan for service life and accountable use
The original 2004 article described WhereNet technology. Zebra’s current WhereNet page carries an end-of-sale notice while indicating continued support for existing customers. For an existing installation, verify the exact hardware, support arrangement and migration options. For a new project, obtain current lifecycle and integration information rather than treating the old announcement as a buying recommendation.
Assign responsibility for tag batteries or replacement, coverage changes, system clocks, exceptions and the manual fallback. Limit location access to operational roles, define retention by the business need and document how corrections are audited. When records can reveal staff movement, explain that use to the people affected and agree appropriate controls before deployment.
Take a usable record away
Download the Vehicle Yard Tracking worksheet (plain text). Save one copy per vehicle, interface or pilot. Record what was observed, who supplied the evidence and what remains unresolved; an empty field is not a passed check.
Explore Autos: vehicle guides, technology and design · Cars: buying, maintenance and ownership