Sometimes you talk to someone and realize: the future isn’t five years away. It’s already on the road.
This is one of those stories.
I sat down with Justin Arciaga (EASE Logistics) and Maynard Factor (Kratos Defense) to unpack something remarkable: they’re already running autonomous truck platoons on public highways - with drivers still in the loop.
Not in a test lab. Not in simulation. On I-70. Moving real freight.

Source: EASE Logistics
They’ve already completed over 100 deliveries across state lines - and they’re just getting started.
This piece breaks down how they did it - the tech, the training, the challenges, and what other fleets can learn from it.
Let’s dive in 👇
What’s Inside
The Scene → Why EASE Chose Platooning
The Technology → Human-Guided Autonomy
The Deployment → Crawl, Walk, Run
Behind The Rollout → What It Took To Execute
Results & Learnings → After 100+ Deliveries
The Business Case → Why It Was Still Worth It
The Playbook → How to Pilot a Truck Platooning Program
Full Q&A → With Justin and Maynard
Where They Were
When EASE Logistics started exploring autonomous technology, their goal wasn’t to replace drivers - it was to rethink what was possible with a driver still behind the wheel.
That idea led them to truck platooning: a model where two trucks operate as a digitally connected pair.

Source: EASE Logistics
The lead truck is driven by a human. The second follows autonomously, mirroring the movements of the first. There’s still a trained driver in the second cab, but the system handles the driving.
The initiative came out of an $8.8M federal grant to test autonomous freight corridors in real-world conditions - through a partnership between DriveOhio, the Ohio Department of Transportation (ODOT), the Indiana Department of Transportation (INDOT), and private carriers.
EASE became the first over-the-road fleet in the US to operate truck platoons on an interstate highway.
To make it work, they partnered with Kratos Defense, whose tech originated in military and highway maintenance deployments, and was then adapted to support the agriculture industry hauling products across North Dakota and Minnesota.
It was the first time Kratos brought this system into short-haul logistics commercial trucking.
Human-Guided Autonomy, Built For Real Roads
Before thinking about training, deployment, or regulatory hurdles, EASE had to know: would this actually work on their existing fleet, on public highways, in real-world conditions?
Kratos’s system gave them confidence for a few reasons:
1. It works with any truck
The tech is vehicle-agnostic. EASE used Internationals; Kratos had worked with Mack, Freightliner, and Volvo.
“They had integrated on other OEMs... so that was a big deal... we weren’t going to change our whole fleet for this.”
2. It doesn’t rely on maps or advanced AI
The system doesn’t need HD maps or advanced computer vision. The follower truck receives real-time driving data from the lead and mirrors its behavior: steering, braking, and acceleration.
“The lead driver is basically creating the map in real time. That makes the system easier to deploy in dynamic environments.”
3. It’s already been proven elsewhere
Before this project, Kratos had deployed the same tech for highway maintenance fleets and agricultural supply chains—both of which operate in lower-speed, short-haul environments with tough safety demands.
“We’re not coming at this from a clean sheet. We’d already logged thousands of hours with DOTs and private customers before we hit I-70.”
4. It keeps the driver in control
Every platoon still has a lead driver and a trained safety rider in the second vehicle. The goal isn’t to replace the driver - it’s to reduce their workload and make longer routes more manageable.
“Platooning is a good entry point for automation. It’s a very reasonable first step - you don’t need to take the driver out of the seat to start seeing benefits.”

Source: EASE Logistics
Crawl, Walk, Run
Before launching their platooning pilot on I-70, EASE and Kratos took a deliberate, staged approach.
They called it “Crawl, Walk, Run” - a rollout strategy that prioritized safety, clarity, and system performance.
Each phase had a clear objective:
Reduce uncertainty
Improve calibration
Build confidence across drivers, regulators, and engineering teams.
Here’s how it worked:
1. Crawl: Mapping the Unknown
Before any automation was activated, drivers and system engineers manually drove the route from Columbus to Indianapolis.
The goal: identify GPS dead zones, weak connectivity, and areas where the platoon might need to revert to manual control. Think of this as groundwork - finding the edge cases before they cause issues.
Completed: The team pinpointed where challenges might emerge and established fallback plans for manual driving.
2. Walk: Testing with Unloaded Trailers
Next, the team ran the same route again - this time with the platooning system active, but trailers left empty.
This allowed them to fine-tune software settings and calibrate the hardware under real-world conditions without the pressure of a live freight haul.
Completed: Engineers confirmed that the platooning system functioned as expected under variable but controlled conditions.
3. Run: Real-World Readiness
With calibrations locked in, the final phase tested the system in true working conditions - fully loaded trailers, real shipments, live operations.
This was the moment of truth: could the system safely handle a full load, at highway speeds, across state lines?
Completed: The platoon operated safely and consistently, meeting all requirements for full commercial deployment.
Why This Framework Mattered
The Crawl-Walk-Run approach wasn’t just internal project management - it was critical for gaining trust across multiple layers:
Drivers felt more confident with gradual exposure to the system.
Regulators saw a clear, low-risk path to deployment.
Engineering teams had space to identify edge cases before they became problems.
And perhaps most importantly: this phased deployment gave the U.S. Department of Transportation a model for how autonomy could be introduced safely - one freight corridor at a time.
What It Took To Execute
Alongside this phased framework, EASE’s deployment required deep coordination across the organization and external partners:
1. A strategic route was defined
The project RFP specified I-70 between Columbus and Indianapolis. But for EASE, that route made operational sense too.
“It’s a straight, familiar route. We were already running it. And it lets us build toward bigger targets like Chicago.”
The predictability of the route made it easier to build confidence internally and with regulators.
2. Driver training was in-depth and standardized
Every platoon driver went through a comprehensive training program that included classroom learning, closed-road operational simulations, and then onto open-road deployment. Each logged over 300 hours before operating a live platoon.
Drivers were trained on both lead and follower vehicles
The curriculum was built to build muscle memory and comfort, not just technical knowledge
Feedback from the drivers shaped future iterations
“One driver told me it was boring. That was the best compliment we could get. If it feels boring, it feels safe.”
3. Internal coordination was critical
This wasn’t a driver-only effort. It required full alignment across:
Project management
Regulatory coordination
Legal and risk management
Customer education
Data collection and reporting
“I spent 90% of my time not on trucks and drivers, but on everything else - regulatory, legal, project management, customer education.”
4. External partnerships accelerated the path
EASE worked closely with DriveOhio, INDOT, ODOT, Ohio State Highway Patrol, and private partners like Kratos. Because Kratos had already deployed similar tech with over 30 DOTs, they had credibility that helped speed up approvals.
“Because of our highway maintenance work, we had 30+ DOTs already familiar with the system. That helped a lot when entering the freight space.”

After 100+ Deliveries
After completing nearly 100 platooned deliveries between Ohio and Indiana, EASE has surfaced some powerful lessons.
1. Customer trust has to be earned
Many brands say they love innovation. But when asked to put their freight on an autonomous truck? The answer was often no - at least during the first deployment.
“Everyone thinks it’s a great idea... but then when it comes time to actually load your freight, they go ‘Eh, maybe next time.’”
The second deployment was easier. With data, delivery history, and known brands (under NDA) already onboard, newer customers were quicker to say yes.
2. Driver adoption is possible, but it takes structure
Most drivers were skeptical at first. But with proper training and the ability to opt in, adoption grew.
EASE trained 8 platoon drivers from a 40-driver fleet
All drivers cross-trained on both vehicles
Internal communication helped reduce the fear of job loss
“We didn’t approach it like ‘this is going to replace you, because it is not.’ - this is just a new skill you can learn.”
3. Organizational readiness matters more than truck readiness
What made the project successful wasn’t just the tech - it was the time EASE invested in planning, coordination, and internal alignment.
“You need one person owning everything. If it’s someone’s side project, it’s not going to get done.”
4. Early deployments are an investment, not a cost-saver
EASE didn’t go into this expecting cost savings. What they got instead was strategic:
Credibility with shippers and regulators
Experience with multiple autonomy platforms (Bosch and Kratos)
A voice in shaping future CDL and HOS standards
A long-term edge if platooning sees broader adoption
“The ROI is strategic... We’re not making money on it right now, but we’re positioning ourselves for what’s coming.”
Why It Was Still Worth It
So what’s the ROI on platooning?
The numbers didn’t pencil out immediately. But EASE sees this as an investment in future capability - and in credibility with customers and policymakers.
The returns:
Brand trust: Customers are more likely to believe EASE’s innovation story —with proven success on the road
Regulatory influence: Participation gives EASE a say in the next generation of standards
Team development: Drivers now have real experience with emerging systems
Customer differentiation: When the industry shifts, EASE is ready
“We’d rather be at the table when the rules get written rather than scrambling to follow them later.”
How To Pilot A Truck Platooning Program
Let’s be honest - this kind of initiative isn’t for everyone.
It’s resource-intensive. It touches every part of your org: legal, operations, drivers, compliance, engineering, customer success. And the returns - at least at first - are strategic, not financial.
But if you're a fleet operator who sees autonomy on the horizon and wants to prepare, not react, a platooning pilot can give you a real edge.
Here’s what it takes to pull one off - based on EASE Logistics’ real-world experience.
1. Evaluate Whether You’re the Right Kind of Fleet
Not every carrier is built for this. Start with a gut check:
Do you run structured, repeatable lanes
Do you have in-house drivers you can train, retain, and build trust with?
Do you control your fleet assets and route planning?
Do you have the bandwidth to run this like a core initiative, not a side experiment?
If the answer isn’t “yes” across the board, hit pause. This playbook assumes operational maturity, cultural alignment, and internal muscle.
2. Assign a Full-Time Internal Lead
This is your program’s single point of success or failure.
You need someone to:
Own cross-functional coordination (legal, ops, tech, drivers, compliance)
Manage vendor and agency partnerships (hardware, DOTs, patrol units)
Lead execution, timelines, approvals, and communication
Navigate roadblocks and chase signatures, not just truck schedules
“You need someone on this full-time. There are too many moving parts for it to be just another thing on someone’s plate.”
Choose someone senior enough to unblock the path, and focused enough to stay in the weeds.
3. Design a Real Driver Training Program
This isn’t a slide deck and a ride-along.
EASE ran a four-week curriculum that included:
Classroom instruction on systems, safety, and protocols
Closed-road testing to build muscle memory
Open-road platoon driving with instructor oversight
Emergency simulations to practice edge cases and failures
Every driver was cross-trained on lead and follower roles. That flexibility built confidence - and reduced friction when reassigning routes.
“Once they saw the system work, most were onboard. But you need to let them experience it - don't just talk about it.”
4. Build Buy-In - Especially From Drivers
Technology alone won’t get you adoption. Culture will.
What worked for EASE:
Transparent messaging from day one: “This won’t replace you — it will expand what you can do.”
Voluntary participation: No one was forced in. Interest grew with each successful trip.
Clear framing: It’s a skill upgrade, like a HAZMAT endorsement — not a layoff warning.
This is how you get long-term adoption, not short-term resistance.
5. Prepare Legal, Regulatory, and Customer Messaging Early
Don’t wait until go-live to tackle legal. The earlier, the better.
You’ll need:
Internal FAQs for legal, sales, and driver teams
Customer-ready boilerplates covering insurance, liability, and pilot scope
Agency coordination with state DOTs, highway patrol, and permitting bodies
Customer education to preempt objections and build confidence
Start these processes in parallel with training. They’ll take longer than you expect.
6. Build Operational and Technical Infrastructure
Even with plug-and-play systems, ops and tech need to be tightly integrated.
Set up:
Fleet consistency (stick to 1–2 OEMs for install and maintenance)
Telemetry and performance tracking systems
Support protocols for real-time troubleshooting (in-house or partner-led)
Standardized install/inspection process to keep trucks platoon-ready
This is where many early pilots stall — don’t underestimate the lift.
7. Follow a Phased Deployment: Crawl, Walk, Run
Going live too early is a mistake. EASE followed a smart phased model:
Crawl: Run the full route manually, identify GPS dead zones, overpasses, blind spots
Walk: Deploy platoons with unloaded trailers to calibrate systems
Run: Move actual customer freight with loaded trailers under real conditions
Treat each phase like a milestone. Don’t advance until it’s working.
8. Track and Report the Right Metrics
Internal credibility and external trust depend on data.
Here’s what EASE tracked:
Zero-incident safety events
System uptime and failure rates
Driver feedback and engagement
Fuel efficiency and spacing data
Customer trust indicators (repeat bookings, hesitation, escalation)
Don’t just report success - prove it with numbers.
9. Set Strategic ROI Expectations
This isn’t a 12-month payback project.
Here’s how EASE thought about returns:
Strategic positioning: Are regulators calling you for feedback?
Customer loyalty: Are shippers engaging more deeply, not less?
Workforce development: Are you building the kind of driver base others can’t match?
Future readiness: Is your team learning what works before others catch up?
“We’re not making money on this pilot. But we’re building capability and trust that will matter later.”
10. Document Everything
This isn’t a one-off. Treat your pilot like version one of a playbook you’ll use again.
Document:
What worked, what didn’t
Internal SOPs and escalation paths
Contract language and customer objections
DOT feedback and compliance learnings
Training protocols and driver feedback loops
When you expand to a second lane or new customers, this becomes your blueprint.
Final Thoughts
If you're serious about autonomy, don’t wait for perfect conditions.
EASE Logistics didn’t chase moonshots. They started small, built internal alignment, and proved autonomy can augment drivers, not replace them.
This playbook is the result of that journey - and a roadmap for any fleet ready to lead, not follow.
Q&A With Justin Arciaga and Maynard Factor
If you want to go deeper on this project, here’s the full conversation I had with Justin Arciaga (EASE Logistics) and Maynard Factor (Kratos Defense).
We cover the entire journey - from why EASE chose platooning over full autonomy, to how they adapted military-grade technology for commercial logistics, trained drivers across both trucks, and navigated regulatory complexity to deploy a human-guided autonomous convoy on I-70.
It’s a detailed look at what it really takes to bring advanced autonomy into live supply chain operations, without removing the driver.
Table of Contents:
This conversation has been edited for length and clarity.
1. Why Platooning?
Justin, what made EASE Logistics explore platooning over full driverless autonomy?
Justin Arciaga (EASE Logistics): We’ve always prioritized innovation, but we never saw full autonomy, completely removing the driver, as the path forward for our company. What attracted us to platooning is that it strikes a balance between embracing cutting-edge technology and keeping drivers in the loop. Our drivers value being home daily. Most of them don’t want to be out on the road for days at a time. Platooning gives us a way to extend route length without compromising that.
Instead of taking the human out of the equation, we enhance what the driver can do. This creates a new set of opportunities, not threats, for our team. We’re thinking about this as a way to collect data, train drivers, and prepare for what’s next.
Maynard, how does platooning differ from traditional autonomous trucking models?
Maynard Factor (Kratos Defense): Most autonomous systems aim to replace drivers altogether. We don’t. Our system is designed around a "human-guided automation" concept. A professional driver leads in the first truck, and our tech powers the following truck, which drives itself—but with a safety rider on board.
This approach brings three benefits:
It keeps quality jobs in place.
It’s safer because there’s a human decision-maker up front.
It allows us to deploy the tech faster since we aren’t trying to solve every edge case.
We’re not trying to reinvent the highway—we’re helping businesses maintain operations and address workforce gaps without going all-in on driverless tech.
2. From Military to Commercial
Maynard, can you walk us through the tech’s journey from the military to logistics?
Maynard Factor: Our roots are in the U.S. military. We developed vehicle-agnostic autonomy kits that could be bolted onto virtually anything: Humvees, T72 tanks, SUVs, even commercial vehicles. The military gave us whatever they had, and we had to make it autonomous.
We built a core electronic package—a set of computers, navigation, and communications systems—and then customized the mechanical components for each platform, whether it was a rotary steering system in a Humvee or linear actuators in a tank. That’s how we perfected our bolt-on, modular system.
When we looked to commercialize it, we started with highway maintenance. There are these trucks called crash attenuators that follow roadwork crews. Their job is to act as human shields. These drivers are at risk of serious injury when struck from behind by high-speed traffic. We automated that task first. From there, agriculture, energy, and logistics companies reached out.
Today, we’re running 24/7 autonomous platoons—short hauls around 200–300 miles—for industries facing major driver shortages.
3. Deployment Details – Route, Training, Setup
Justin, why was I-70 chosen for your second deployment?
Justin Arciaga: It was part of the next phase in our RFP (Request for Proposal). Our first deployment was focused solely within Ohio. After proving the tech on that initial route, we asked the Ohio State Patrol and DOT if we could expand to more state roads within Ohio. The I-70 TAC (Truck Automation Corridor) project was already an existing separate deployment that we were lucky enough to be chosen for. It was a nice way to leverage what we learned on our 1st deployment to help prep and accelerate us for success on the second deployment.
I-70 is a critical freight corridor for us—it connects Ohio to Indiana and, longer term, Chicago. It’s straight, well-known, and gives us a good testing ground for things like potholes, construction zones, GPS connectivity gaps, and weather impacts. It also allows us to see how the tech performs across state lines, which is the next logical step toward nationwide viability.
How many trucks are involved, and what’s the driver setup?
Justin Arciaga: Each deployment involves two trucks: a lead vehicle with a human driver, and a follower vehicle controlled autonomously by Kratos’ system but also equipped with a trained safety driver. Both vehicles have highly trained operators. Our drivers undergo a four-week training program that includes closed-track testing, road testing, and emergency response drills.
Both drivers are cross-trained, so they can switch roles. It’s designed to be boring, on purpose. We want the system to feel safe and predictable. Drivers say it feels like glorified cruise control, and that’s exactly the point.
Are you reducing headcount with this tech?
Justin Arciaga: Not at all. If anything, we’re upskilling our drivers. Think of it like adding a HAZMAT endorsement—this is a new credential. Eventually, we’d love to see a “platooning certified” badge as part of CDL licensing. Our goal is to prepare our team for the future, not replace them.
4. Safety, Regulations & Road Conditions
Does platooning affect driver HOS regulations?
Justin Arciaga: Not yet. But that’s the hope. We’re collecting data that might support exemptions. For instance, if a driver is in the follower vehicle and effectively being “towed,” maybe their clock shouldn’t be running.
Right now, everything follows existing regulations, but the endgame is to influence how those regulations evolve.
Maynard, what role do weather and road conditions play?
Maynard Factor: Weather and environment matter a lot. For example, in North Dakota, we won’t operate in whiteout conditions. We work with clients to clearly define when, where, and how to use the system.
That’s the beauty of platooning—it’s flexible. The human driver in front makes real-time decisions. If a road changes or weather turns bad, they adjust, and the autonomous follower adapts instantly. There’s no need for complex AI route planning. It’s a simple and resilient approach.
5. Business Case & ROI
Justin, what does the ROI look like for EASE so far?
Justin Arciaga: The first deployment was a pure investment - no direct financial return. But the ROI came in other ways:
It educated our team and customers
It gave us a real innovation story to tell
It built credibility for future partnerships
Now, we’re in a position to say: “We’ve done 100+ autonomous deliveries, no incidents, and we’re working with top-tier tech partners.” That’s incredibly valuable.
Was federal funding involved?
Justin Arciaga: Yes, partially. Some of it was grant-subsidized. But we also contributed our own trucks, drivers, and project management resources. It’s a cost-share. We’re not trying to make a profit on the deployment—we’re trying to build something for the future.
What about customer acceptance? Were brands on board?
Justin Arciaga: Initially? No. Everyone liked the idea of innovation—until it was their freight on the truck. There was legal risk, perception issues, and general hesitation.
But after proving ourselves with a successful deployment and no incidents, we’re seeing real traction. Even some well-known brands are now involved, though we can’t name names due to NDAs.
6. Lessons Learned
Maynard, what kind of feedback do you get from the logistics industry?
Maynard Factor: Executive teams usually get it right away - they see the labor gap, and they want to protect their supply chains.
Operators are more skeptical at first. But once they use the system, it clicks. These are people with 20–30 years behind the wheel. They’re analytical. They want to know if this helps or hurts their job. Once they see that it helps—and that they’re still in control—they often become our biggest advocates.
We also get great ideas from them. They show us how to deploy or tweak the system in ways we hadn’t even thought of.
Justin, what internal changes did you need to make this work?
Justin Arciaga: It’s a huge lift. You need cross-functional alignment across operations, legal, project management, customer success, and compliance. I spent 90–110% of my time on this.
We also needed project management tools, legal oversight for customer contracts, and systems for training and evaluation. Thankfully, we had strong executive support. Innovation isn’t just a buzzword for us—it’s something we back with time and money.
If you’re a logistics company looking to try this, know that it’s not just a tech project. It’s a full organizational commitment.







