Out
Stop lists to drivers
Push the new stop order to the driver app with a short reason.
Routite Edge · Driver and robot execution
Edge is the last step: approved stops reach driver apps, arrival and service times come back. Robot and AMR task dispatch on NVIDIA Jetson is planned.
Out and back
Driver app · Van 4
ExampleStop 01 · Capabilities
Out
Push the new stop order to the driver app with a short reason.
Back
Record arrival, service and departure at every stop.
Exceptions
Drivers report a blocked street or a closed site in two taps.
Connect
Write to the driver app you already use, where it has an API.
Offline
The current stop list stays on the phone if signal drops.
Robots
Dispatch tasks to robots on Jetson with the same plan.
Stop 02 · How it works
Approved changes go to affected drivers only.
Arrival, service and departure are logged with GPS.
Outcomes flow to Twin and retrain ETA models.
Stop 03 · Specification
| Item | Detail | Status |
|---|---|---|
| Driver app | Routite app or your app via API | In build |
| Offline mode | Current route cached on device | In build |
| Proof of delivery | Photo and signature through your app | Planned |
| Robot dispatch | Jetson edge agents, Isaac and ROS | Planned |
Stop 04 · Place in the loop
Edge closes the loop: it executes what Copilot approved and returns what really happened to Twin.
Return leg Edge sends real arrival and service times back to Twin. ETA and demand models retrain on them, so tomorrow's first plan starts closer to reality.
Stop 05 · Questions
Not if your app can take a stop list through an API. Otherwise the Routite app is available for the pilot.
Only when an approved change affects them, with a short reason.
It is planned and depends on design partners with robot fleets.
Stop 06 · Destination
Next step
A replay of one past day shows what this product would have done, with every assumption written down.