We audited every yard in H-E-B’s network, from satellite.
Click any site for its gate, docks, and drop yards. No badge, no NDA, just what a driver sees.
Loading network atlas…
The frame
H-E-B’s stack is connected. The yards never were.
Your TMS runs the road. Your WMS runs the building. The yards are the tier between them, and they were never on the network.
Gate
⊘
Guard
⊘
Dock
⊘
Spotter
⊘
Exit
Every truck gets re-keyed, re-queued, and re-found at each step. The lost time lives between the steps, which is why no single tool ever fixed it. The audit below is that gap, measured on your real yards.
▶ Watch a truck run this yard · H-E-B
A real audited site, played gate→dock→exit on the true yard geometry. Switch sites with the picker.
Movement durations are honest floors set by yard geometry; the uplift lands on the wait fields (queue + dispatch + secondary checkpoints). “Today” timings reflect the radios-and-clipboards world; “With YardFlow” reflects the protocol acting end-to-end. We may be wrong about parts of this — your actual numbers will tell us where.
The silo tax
What the handoffs cost across your network — and what removing them is worth
9
of 16
already run drop yards — drop-and-hook ready
→ where the 48→24 min drop-and-hook win lands
8
of 16
have long entry drives where queues build
→ pre-arrival check-in keeps the queue off the public road
8
of 16
are multi-building campuses where drivers misroute
→ in-cab building + spot assignment on arrival
7
of 16
gated with a guard / booth check-in
→ flowGATE machine-vision check-in automates the gate step
Read from satellite + Street View across all 16 facilities, modeled on the same engine the full calculator opens on. At a comparable network, Primo Brands cut drop-and-hook turns from ~48 to ~24 min. Set your real volumes and margins in the calculator to make it yours.
Are these your yards?
Tell us where we got it wrong, or see what 15 minutes of orchestration looks like on your worst site.
