Yard Network System (YNS)
Six Modules.
One Network.
YardFlow isn't a YMS. It's a standardized operating protocol. Same driver journey at every facility. Same steps. Same sequence. Same proof requirements.
The protocol is the product.
The Flow
One Continuous Driver Journey
flowDRIVER
Verify
flowBOL
Document
flowSPOTTER
Execute
flowTWIN
Model
flowAI
Orchestrate
flowNETWORK
Scale
flowDRIVER standardizes entry and exit, flowBOL records proof, flowSPOTTER executes moves, flowTWIN maps yard state, flowAI coordinates actions, and flowNETWORK scales alerts and simulations across sites. Same flow, every time, every yard, you define.
Facility Install
Every Facility Gets the Same Stack
Deploy all six modules together. Each solves a specific variance type. Together, they create a predictable yard network.
Module 1
flowDRIVER
Digital driver journey
Check-in to check-out journey powered by FreightRoll ID wallet, lane logic, and standardized handoff evidence.
dock
Module 2
flowBOL
flowBOL repository
flowBOL creation with signed, timestamped, and searchable proof across handoffs and claims workflows.
Module 3
flowSPOTTER
Spotter execution app
Task queue + execution app for spotter teams, with assignment clarity and move completion telemetry.
Module 4
flowTWIN
Machine vision + GPS twin
Machine vision and GPS-enabled digital twin of your yard for location, queue, and dwell truth in real time.
Module 5
flowAI
AI orchestration agent
AI agent that uses flowTWIN and operational inputs to orchestrate flowDRIVER, flowSPOTTER, and flowBOL actions.
Module 6
flowNETWORK
Network control layer
Network-wide command view, alerting, and simulations to coordinate standards, rollouts, and response across all yards.
network
Network Intelligence
Standards Compound. Adoption Accelerates. Data Patterns Emerge.
As more facilities deploy, data compounds. One site creates proof. 50 sites create benchmarks. >200+ sites create cross-facility learning that single-site data cannot reveal.
1
Site
Local proof
2×
25% Adoption
Network benchmarks
4×
50% Adoption
Predictive patterns
>200+
Full Network
Cross-site learning
“It is accurate that your software has enabled us to take on additional volume while remaining headcount neutral in the dock office.”
— Dock Operations Leadership, Top CPG Shipper
Operating Model
Recording vs Enforcing
This isn't feature-bingo. It's: do you have a control loop, and can you make timestamps defensible?
YardFlow vs Legacy YMS
Legacy systems record events. YardFlow enforces workflows.
Where legacy often breaks
- ✗Data entry is inconsistent under pressure
- ✗Exceptions become free-text (no reason-code truth)
- ✗Visibility is retrospective, not operational
- ✗Multi-site rollout becomes a config swamp
What YardFlow optimizes for
- ✓Repeatable check-in/out with minimal friction
- ✓Defensible timestamps (audit trail mindset)
- ✓Exception workflow that produces usable truth
- ✓Network standardization (the multiplier)
YardFlow vs Spreadsheets + Radio
Spreadsheets can track. They can't enforce.
What manual tracking gets wrong
- ✗Timestamps are delayed, approximate, or missing
- ✗Exception reasons are inconsistent and hard to analyze
- ✗Knowledge lives in people, not systems
- ✗Network reporting becomes a reconciliation project
What changes with a control loop
- ✓Standard check-in/out and exception workflow
- ✓Reason codes that power analytics and action
- ✓Operational truth that can be shared cross-site
- ✓Board-ready reporting: assumptions + defensibility
Integrations
Fit Into Enterprise Reality
Partial data. Mixed systems. Operational nuance. We integrate around the workflow, not the other way around.
Connectivity Surface
Integration Path
Start fast, scale deliberately
Pilot
Minimal Integration
Manual appointment entry. File upload for trailer inventory. No TMS/WMS dependency required.
Wave 1
Core Integration
Appointment sync from TMS. Event webhooks to WMS. Scheduled data exports to BI.
Scale
Full Integration
Real-time bidirectional sync. SSO/SCIM. Network-level visibility. Enterprise reporting.