NFI Industries · 16 of 300+ yards, mapped from satellite
The Yard Network System, by FreightRoll.
Your yards are the gap in your supply-chain stack. YardFlow fills it.
You have said the goal is a fully autonomous yard. Check the driver in, drop the trailer, pick the next one, route the driver, and validate the load on the way out, with no one in the loop. We want that for you too.
Here is the part nobody says out loud. A yard cannot run itself while it still runs on paper at the gate, radios in the lot, and people walking the rows. You cannot automate what the system cannot see. YardFlow is the Yard Network System, the software bridge between your TMS and your WMS. It makes every trailer legible first, which is the foundation the autonomous yard is built on. At Primo, drop-and-hook turns fell from 48 minutes to 24.
- The gapYour TMS runs the road, your WMS runs the building, nothing runs the yards.
- The bridgeYardFlow is the Yard Network System between the two, on one standard across all 300 sites.
- The foundationAutonomy needs eyes and memory. flowGATE sees the trucks, the console remembers every trailer.
- The proofPrimo: turns 48 to 24 min, first ever to commit ~260 sites. Your Allentown yard already runs our BOL.
Already live at scale · the Primo Brands network
The Yard Network System runs the yards behind these household brands. Live today, rolling to all ~260 sites.
The modeled prize
Proven at Primo, modeled for your 16 US plants
The problem
The autonomous yard cannot run on paper, radios, and people.
You run about 300 yards on roughly 70 million square feet.
Most of them still check trucks in by hand, move trailers by radio, and track them in someone's head. Six of the 16 we mapped sit open to the road. A spotter cannot self-drive what the system cannot see.
The lost time lives in the gaps. Now multiply it across ~300 plants, each running its own version. YardFlow runs the whole network as one chain.
Why now
You set the goal. The substrate has to come first.
The goal is a yard that checks in, drops, picks, routes, and validates on its own.
That future is real, and it is close. It does not arrive as one magic spotter. It arrives when every trailer, gate, and move is already digital, so a machine can act on it. The freight cycle adds urgency. Pricing power is swinging back to carriers, and the yards that burn a driver's day will pay for it in spot rates. Build the digital yard now and you cut that cost today while you lay the track autonomy runs on tomorrow.
The Yard Network System
One standard between your TMS and your WMS, on every yard NFI runs.
Every yard runs the same three jobs: check the driver in, place the trailer, turn the load. You run them mostly by hand today, with a local YMS here and there. The Yard Network System runs all three on one standard across all 300 sites. flowDRIVER pulls the paper and radio out of the driver journey. The operator console is a modern YMS your Manhattan WMS can read and write. flowGATE reads the truck and chassis at the gate and updates the console on its own. Those cameras are the eyes autonomy needs. We keep PINC or any YMS you have and run in parallel, no rip and replace.
flowDRIVERflowDRIVER
The driver journey, standardized at every yard. No paper, no radio, no app to install.
Open live
flowGATEflowGATE
Cameras read the truck and chassis at the gate and update the YMS. The eyes an autonomous yard needs.
Open live
flowTWINOperator console
Every trailer on one live map. The modern YMS the gate and the driver journey both feed.
Open liveThe proof · already at scale
No company had ever put its whole yard network on one system. Primo just did. You already run a piece of it.
Primo Brands committed all ~260 of its sites to the Yard Network System. That has never happened before, a national network standardizing every yard on one protocol instead of one flagship at a time. Live at 24 sites today, rolling to the rest. Where it runs, drop-and-hook turns fell from 48 minutes to 24, and Primo took on more volume on flat dock-office headcount. NFI already runs our digital BOL at the Allentown yard you operate for Primo.
“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.”
Figures from the YardFlow deck and the live network. 24 sites live today, rolling out across the ~260-site commitment.
Sized conservatively, on purpose
We modeled it across your 300 yards at a fraction of the gain Primo measured.
Primo measured the full turn-time gain. We booked a conservative slice of it across your network and counted a plain $1,000 a load. The headline number is the floor, not the ceiling, and it grows with every yard you automate.
Every figure is the YardFlow ROI engine output, the same one /demo/nfi renders, not a slide number. The paper-only row in the table below is the conservative floor.
| Scenario | Payback | Monthly IRR |
|---|---|---|
| Paper-only savings | 20.0 mo | 3.46% |
| Hard savings | 7.0 mo | 24.47% |
| Full modeled value | 3.4 mo | 104.28% |
Monthly IRR from the YardFlow ROI model: monthly cash flows net of subscription, 24-month horizon. The paper-only scenario is the conservative floor.
What it touches
A new layer, not a new migration.
YardFlow runs in the yard and talks to the systems you already have. Your Manhattan WMS and your TMS 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. Your spotters and gates keep working.
- Keep your YMSRun alongside PINC, Caleris, or any local YMS. Switch only if and when you decide to.
- ReadsYour TMS appointments, over standard API or EDI.
- WritesGate and turn events back to your Manhattan WMS, so dock and inventory stay current.
- IT liftOne connection per system. No rip-and-replace, no platform migration.
- Week 0Network audit from satellite. No IT lift.
- Weeks 1-2One yard live. One TMS read, one WMS write.
- Day 60First measured turn-time win, on your dock.
- ThenStandardize across the network, on proven economics.
Your own audit
This is NFI's own audit, not a generic benchmark. We mapped 16 of your largest yards from satellite. Here is what the manual handoffs cost today, and where the standard lands first.
- 16 of 16
- Run drop yardswhere the 48 to 24 minute drop-and-hook win lands
- 10 of 16
- Gated, only 4 staffedflowGATE automates the check-in step the booth does by hand
- 16 of 16
- Long entry drives where queues buildpre-arrival check-in keeps the queue off the road
See all 16 sitesOpen the audit →Easy
Start at one yard. Pull the paper first. Measure the turn.
Nothing gets ripped out to start. Pick one Lehigh Valley yard, pull the paper and radios out of the driver journey, and measure the turn in 30 to 60 days. Then the same standard rolls across the network, on economics a per-site YMS never allowed. As the work goes digital, your people move up to the roles you already need to fill.
A goal you already set, a fix proven at Primo, a prize modeled at $633.9M a year, and a first step that risks nothing. That is the brief.