Daimler Truck North America · 16 NA sites, mapped from satellite
The Yard Network System, by FreightRoll.
You are automating the road. The yards are the half that is left.
You picked Innoviz as the LiDAR partner for series production of your Level 4 autonomous Freightliner Cascadia, the road answered. Every one of those trucks still has to start and end its run in a yard, and your own plants run that same yard problem twice over. Supplier parts arrive on one clock, much of it on rail, and finished trucks stage drive-away on another. The one place both clocks clog is the yard. One slow gate decides which queue stalls first.
YardFlow is the Yard Network System, the software layer between your TMS and your WMS. The lane you are automating begins and ends in a yard. That is the half the autonomy roadmap does not cover. Primo Brands has implemented the driver journey system wide, cut trailer turn times by 50%, and shipped about 5% more volume on the same dock-office headcount. The audit shows where the same gain sits in your network.
- The gapYour TMS runs the road, your WMS runs the building, nothing runs the yards.
- What we doOne digital standard for all sites. EZ-Pass at the gate, air-traffic control for the trailers.
- The proofPrimo: about 5% more volume on flat headcount, turns cut 48 to 24, and 100% of the network committed.
- The payoffReduce turn times, gain 5% capacity per location. Eliminate paper and detention expenses. No change to headcount.
Already live at scale · the Primo Brands network
The Yard Network System runs the yards behind these household brands. Live today, rolling to 100% of the network.
Using actual results from Primo Brands, we modeled the potential prize for Daimler Truck North America.
Proven at Primo, modeled across the network
The problem
Every yard "does it their own way." That is not strategy. That is drift.
Ask two of your plants and we would expect the same line: our yards are different.
In our experience they are not. Same trucks, same trailers, same moves. What differs is the workaround each site improvised, hardened into a process nobody chose. Cleveland NC builds the Cascadia and Western Star across 200 acres, with 60 dock doors and a rail-served drop yard. Parts sit in one queue, finished trucks in the other. One slow gate decides which of those two queues stalls first, and the line waits on whichever one loses. An autonomous Cascadia can hold a lane for hundreds of miles. The gate at the end of it is where that gain is kept or given back. Legacy YMS was built to run one site, not a network. Our read is that the gap shows up everywhere except your biggest plant.
Why now
You solved the lane. The yards at each end are the half that is left.
Series production of Level 4 Cascadias is now on the roadmap, with deployment planned across highway and regional routes.
A driverless lane only pays off if the yard at each end keeps pace. A supplier part that misses its window can idle an assembly line worth millions an hour. Sequenced inbound leaves no slack for a gate that cannot keep up. Across the 16 sites we mapped, we count 562 dock doors and almost 2,000 trailer positions. We cannot see from orbit what runs them. You are building trucks that drive themselves. The yards they clear through are the half nobody automated. Detention starts at hour two and runs $50 to $100 an hour, and carriers now pick their shippers. Every printed BOL, every forced check-in, every trailer your driver hunts down is added cost. Fix the yards and the capacity you could not see starts to surface, which is more trucks out the same gates. You sell turn time to every fleet you build for. Run it in your own yards first.
The Yard Network System
A new layer of your stack, between the TMS and the WMS.
Every yard runs the same jobs, and the same people run them. The Yard Network System gives each of them one standard across every site. The driver checks in from their phone with flowDRIVER. The spotter moves the trailer while a cab camera maps the yard with flowTWIN. The dock coordinator assigns the door from flowYMS. The dock office signs the BOL with flowBOL. The executive watches every yard on flowNETWORK. Under all of it, machine vision reads the truck at the gate and an agent dispatches the next move. Think EZ-Pass at the gate and air-traffic control for your trailers.
The proof · already at scale
No company had ever put its whole yard network on one system. Primo just did.
The point is not faster trucks. It is realized production capacity: 5% more volume out the door on the same headcount, capacity those plants could not ship before.
Primo started with one layer: the driver journey. Text the truck instead of checking it in. Paper out of the gate. No more driver-to-dock-office handoff. Across the 24 sites where it went live, those yards shipped about 5% more volume than the sites without it, on the same dock-office headcount. That alone is why Primo committed all ~260 sites to the full Yard Network System, the first national shipper to standardize every yard on one protocol. The YMS is rolling now. Live at 10 plants, every production site by the end of Q3. The highest-volume campus is going fully automated end to end, on a trailer map that updates itself in real time. The 5% came from the lightest touch. The rest is still ahead. Daimler Truck North America would be the first truck OEM to run inbound and outbound yards on one protocol.
“Your software enabled us to take on additional volume while remaining headcount neutral in the dock office. That was an integral part of our strategy, and it has been proven.”
Result measured on the driver-journey layer, before the YMS rollout. Primo is live at 10 plants today, every production site by the end of Q3.
What it touches
A new layer, not a new migration.
YardFlow runs in the yard and talks to the systems you already have. Your TMS and WMS stay the systems of record. Nobody is ripping anything out.
Built for enterprise infosec review. We connect over your standard API or EDI and scope to yard operations, not your ERP of record. Full integration and security review happen in the audit.
- In the yardflowDRIVER (driver app, no install) and flowGATE (camera gate) run on YardFlow. Nothing changes on the plant floor.
- ReadsYour TMS appointments and supplier inbound schedule, over standard API or EDI.
- WritesGate and turn events back to your WMS, so dock and inventory stay current.
- IT liftOne connection per system. No rip-and-replace, no platform migration.
Your own audit
This is Daimler Truck North America's own audit, not a generic benchmark. We mapped 16 NA sites from satellite. Here is what the handoffs cost today, and where the standard lands first.
- 12 of 16
- Already run drop yardswhere the 48 to 24 minute drop-and-hook win lands
- 7 of 16
- Gated with a guard or boothflowGATE automates the check-in step
- 11 of 16
- Long entry drives where queues buildpre-arrival check-in keeps the queue off the road
See all 16 sitesOpen the audit →We are not asking for a pilot. We are asking for a conversation.
A 30-minute call, direct with Casey. We show you what we found on your network, you tell us straight where it fits. We will not tell you which site to start at. We have only seen your yards from orbit. You run them, so you already know which one goes first. If the call goes well, we talk about where that is. If the call does not land, you keep the analysis.
None of these times work? Email me at casey@freightroll.com or call or text me at 410-236-7434, and we’ll find one.
Casey Larkin, YardFlow. Jake, our founder, joins when it helps.
