Dock-door and yard visibility for a European 3PL.

Earlier work by our advisers. Client name withheld under NDA. Client name withheld under NDA; figures as reported at the time. Named references available under NDA. We model your own numbers when you engage.

What the engagement delivered.

• Passive RFID dock-door reads with automatic ASN reconciliation
• BLE trailer and yard location
• Blue Yonder and SAP EWM integration

The stack behind it

3PL dock/yard programmes instrument gates, yard slots and dock doors for trailer and pallet flow. Active RFID, UWB, GPS/LTE yard tags and UHF dock portals appear in combinations.

WMS/YMS integration is non-negotiable.

Outcomes: lower dwell, fewer miss-ships, less cycle-count labour.

Lessons: baseline miss-ship and dwell first; weather and metal yards punish naive RF plans; train gate staff.

Yard dwell and miss-ships destroy profit. Cycle counts paper over process wounds.

Gates, slots, dock portals; YMS/WMS join; baseline dwell and miss-ship; weather/metal RF design; train gate staff.

Dwell, miss-ship rate, count labour.

Figures from this engagement only. Your payback depends on adoption, integration quality and exception labour, not tag unit cost. Named references under NDA on engagement.

We challenge any supplier who asks you to accept demo-day averages as production truth.

Baseline dwell and miss-ships; gate/slot/dock design; YMS join; weather week RF tests; gate staff training. Expand yards after exception desks cope.

KPIs: dwell, miss-ship, count labour.

For 3PL yard/dock, baseline dwell and miss-ships first; RF-design for weather weeks, not sunny demos.

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.

Supplier 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; independent shortlist and RFP language; pilot acceptance criteria; then optional implementation oversight or programme rescue if a prior pilot stalled. We don't sell hardware, so our advice stays independent. 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.