What this looks like when it works
Cycle-count time vs manual counts.
Trailer dwell with live yard visibility.
Dock-door load reconciliation accuracy.
Composite worked example — figures are ranges from comparable programmes, not attributed named-client results. Named references available under NDA. We model your own numbers when you engage.
The challenge
Manual yard checks and clipboard dock audits are slow and error-prone. Trailer dwell eats capacity; reconciliation errors cause claims and rework.
Our approach
- GPS / UWB for yard trailer and shunter location.
- Passive RFID dock-door portals for automatic load/unload reconciliation.
- Geofenced alerts for dwell, detention and mis-spotting.
- Cycle-count automation for inbound/outbound.
- Feed events into WMS / YMS for live visibility.
Technology & integration
Stack deployed: GPS + UWB yard location, Passive RFID dock portals, BLE for returnables.
Integration: WMS, YMS, TMS, carrier / ASN data.
Related: RTLS for logistics · Logistics RTLS · 3PL dock & yard
Baseline, method, period — and what we excluded.
These pages are composite worked examples, not named-client scorecards. Figures are ranges from comparable RTLS/RFID programmes and published industry sources where noted.
- Baseline: Yard moves assigned by radio; dock door status lagged WMS.
- Method: Trailer identity and spot assignment; dock status events; dwell and missed-appointment metrics.
- Period: Busy DC yard through carrier peak.
- Excluded: Pretty maps that dispatch never uses.
Programme pattern for this vertical
Yard-dock automation adds appointment logic, dock assignment and exception bots on top of locating. The locating layer feeds the decision layer — it is not the product.
Pilot one site with messy carrier behaviour.
Outcomes to expect — and how they are earned
Outcomes: dock utilisation up, demurrage down, clearer carrier scorecards.
Lessons from comparable programmes
Lessons: pretty maps unused by dispatch fail; integrate TMS/YMS; measure detention.
Deeper problem framing
Dispatch ignores pretty maps. Appointments and dock assignment need locating as input, not as the product.
Approach
Locate + decide; TMS/YMS; pilot messy carriers; measure detention and demurrage.
Outcomes and measurement
Dock utilisation, detention, carrier scorecards.
Governance, risk and what we refuse to claim
Composite example only. Your payback depends on adoption, integration quality and exception labour — not tag unit cost. Named references under NDA on engagement.
We challenge any vendor who asks you to accept demo-day averages as production truth.
Implementation sequence and change management
Dispatch co-design; appointments + locating; TMS/YMS; messy-carrier pilot; detention metrics. Kill map-only scopes.
KPIs: dock utilisation, demurrage, carrier scorecards used in QBRs.
Buyer checklist, vendor challenges and engagement shape
For yard-dock automation, co-design with dispatch and measure detention — maps without decisions fail.
Buyer checklist before you sign: (1) written system of record for events; (2) acceptance tests with 95th-percentile performance under real interference; (3) integration owner named in IT/OT; (4) privacy or labour consultation path if people are tagged; (5) cybersecurity zoning sketch; (6) five-year TCO including batteries, spares, recalibration and SLA escalations; (7) exit/export terms so you are not hostage to a cloud tenant; (8) a pilot that can fail without political punishment.
Vendor claims to challenge in this pattern: brochure accuracy without production load; 'compliance included' without artefacts; ROI that assumes perfect adoption in 30 days; references that cannot be called under NDA; install partners who have never worked your vertical's overlays; shared support accounts; and any design that dumps locating onto a flat plant or clinical VLAN.
How TRACIO typically engages: stage-1 architecture and measurement design; vendor-neutral shortlist and RFP language; pilot acceptance criteria; then optional implementation oversight or programme rescue if a prior pilot stalled. We stay independent of hardware margin. Composite pages like this one exist so you can prepare the workshop — your numbers replace every planning band when we model payback.
Risk register themes that recur: mute fatigue on alerts; shadow spreadsheets reappearing beside the platform; battery logistics understaffed; master data too weak to support identity; works-council or IG review starting too late; and success declared on demo day before night-shift reality.
Document baseline windows explicitly: what you measured, for how long, which shifts, and what you excluded. Investment committees and auditors both punish fuzzy before/after stories. If your baseline is weak, spend two to four weeks fixing measurement before ordering anchors or portals. That discipline is cheaper than a stranded deployment and is the difference between a locating programme and a technology souvenir.
Training and communications plan: who explains purpose to operators, how often refreshers run, how contractors are inducted, and how successes are fed back without turning safety systems into league tables. Budget a champion network on each shift. Platforms do not adopt themselves. Where unions or works councils exist, share the purpose statement and retention rules early — surprise monitoring is how programmes die. Finally, schedule a formal gate review against the written criteria; celebrate a no-go if evidence is weak. Expanding failure is not delivery.
Governance, risk and what we refuse to claim
Composite example only. Your payback depends on adoption, integration quality and exception labour — not tag unit cost. Named references under NDA on engagement.
We challenge any vendor who asks you to accept demo-day averages as production truth.
Buyer checklist, vendor challenges and engagement shape
For yard-dock automation, co-design with dispatch and measure detention — maps without decisions fail.
Buyer checklist before you sign: (1) written system of record for events; (2) acceptance tests with 95th-percentile performance under real interference; (3) integration owner named in IT/OT; (4) privacy or labour consultation path if people are tagged; (5) cybersecurity zoning sketch; (6) five-year TCO including batteries, spares, recalibration and SLA escalations; (7) exit/export terms so you are not hostage to a cloud tenant; (8) a pilot that can fail without political punishment.
Vendor claims to challenge in this pattern: brochure accuracy without production load; 'compliance included' without artefacts; ROI that assumes perfect adoption in 30 days; references that cannot be called under NDA; install partners who have never worked your vertical's overlays; shared support accounts; and any design that dumps locating onto a flat plant or clinical VLAN.
How TRACIO typically engages: stage-1 architecture and measurement design; vendor-neutral shortlist and RFP language; pilot acceptance criteria; then optional implementation oversight or programme rescue if a prior pilot stalled. We stay independent of hardware margin. Composite pages like this one exist so you can prepare the workshop — your numbers replace every planning band when we model payback.
Risk register themes that recur: mute fatigue on alerts; shadow spreadsheets reappearing beside the platform; battery logistics understaffed; master data too weak to support identity; works-council or IG review starting too late; and success declared on demo day before night-shift reality.
Document baseline windows explicitly: what you measured, for how long, which shifts, and what you excluded. Investment committees and auditors both punish fuzzy before/after stories. If your baseline is weak, spend two to four weeks fixing measurement before ordering anchors or portals. That discipline is cheaper than a stranded deployment and is the difference between a locating programme and a technology souvenir.
Training and communications plan: who explains purpose to operators, how often refreshers run, how contractors are inducted, and how successes are fed back without turning safety systems into league tables. Budget a champion network on each shift. Platforms do not adopt themselves. Where unions or works councils exist, share the purpose statement and retention rules early — surprise monitoring is how programmes die. Finally, schedule a formal gate review against the written criteria; celebrate a no-go if evidence is weak. Expanding failure is not delivery.
Last updated:
Dock, yard, inventory
Independent advisory means the radio is chosen last — after the job, the constraints and the system of record are clear.
The operational bottleneck
Dwell, door assignment and inventory truth beat “coverage map” theatre.
Technology follows the yard
Portals, UWB or RFID only after the flow and WMS events are clear.
WMS is the system of record
We design into it so the yard display is not the only place truth lives.
Measurement
Baseline: gate-to-dock dwell, yard check-in time, and trailer-find tickets for 4–6 weeks. Pilot: one yard zone or dock bank with RFID/RTLS events reconciled to the WMS/YMS. Steady-state: mean dwell, “unable to locate trailer” rate, and dock utilisation on the ops KPIs already used. Bands on this page are programme-type ranges under NDA.