Active loads in transit
28
4 with an active exception
D-ONE / Demo workspace
D-ONE Tracking & Mobile Operations
D-ONE demo / sample data — not connected to live records
Stage 4 / movement workspace
A visual blueprint for D-ONE-owned shipment visibility and the Driver Companion workflow, from first departure signal to final proof of delivery.
ELOHM Command Signal
Next driver action summarized
ELOHM turns movement, stop, ETA, document, and communication signals into the next clear Driver Companion handoff.
Review movement Stage 4D-ONE demo / sample data — not connected to live records
Tracking that keeps the whole move in view.
D-ONE turns movement signals into an owned operating history. Dispatch sees the board, drivers see the next action, and customers see a clear milestone trail.
On-time pickup rate
96.2%
up 1.8 pts · sample week
On-time delivery rate
94.8%
up 2.1 pts · sample month
ETA accuracy
91.4%
within 30 min · sample week
Active drivers
41 / 48
7 available in roster
POD capture rate
87.6%
42 of 48 sample deliveries
Open alerts
07
2 high · 5 monitor
Control plane / sample snapshot
Live shipment visibility board
| Load / customer | Lane | Driver / truck | Status | Current location | Next stop | ETA | Signal |
|---|---|---|---|---|---|---|---|
| DL-2048 Northstar Foods | Newark → Atlanta | Marcus Reed DT-048 | In transit | I-85 · Charlotte, NC | Atlanta DC | Today · 18:40 | On schedule |
| DL-2043 Morrow Retail | Chicago → Dallas | Alicia Grant DT-031 | Delayed | I-35 · Fort Worth, TX | Dallas receiver | Tomorrow · 07:57 | 42 min late |
| DL-2039 Cedar & Co. | Savannah → Memphis | Jon Bell DT-017 | At delivery | Memphis, TN | Memphis receiver | Today · 16:10 | POD due |
| DL-2034 Meridian Supply | Dallas → Phoenix | Priya Shah DT-022 | At pickup | Dallas, TX | Phoenix DC | Aug 21 · 14:05 | On schedule |
Showing 4 of 28 active sample loads · no location is liveOpen Loads
D-ONE Driver Companion / mobile concept
A clear next move in the cab.
Active loads
One load, one next action
A driver sees the assigned load, route context, contact, and status without hunting through a dispatch thread.
Timeline
Pickup complete
08:18 · Chicago, IL
08:18 · Chicago, IL
In transit
Current milestone
Current milestone
Delivery next
Dallas, TX · 07:57
Dallas, TX · 07:57
9:41 AMD-ONE● ●
Good morning, Alicia
Your next move
DL-2043
Morrow Retail · Chicago → Dallas
Fort WorthDallas
Next: send ETA update to dispatcher
Messaging
Dispatcher thread
“Traffic near Fort Worth is adding time. I’ve shared the updated ETA with the receiver.”
Jordan · 11:29 AM · sample
Documents + status updates
Rate confirmationReady
BOL / consigneeView
HOS status04:18 left
Every mobile action becomes a D-ONE-owned event. Buttons above are visual references only; no status is changed and no message is sent.
D-ONE event model
Milestones become a traceable history.
| Event family | Sample event | Time | Owner / source |
|---|---|---|---|
| Load event | DL-2048 assigned to Marcus Reed | 08:34 | D-ONE record |
| HOS event | 04:18 drive time remaining at departure | 09:02 | Driver signal |
| Geofence event | Entered Charlotte service area | 11:26 | Location signal |
| ETA recalculation | Arrival moved from 18:10 to 18:40 | 11:28 | D-ONE event |
| Notification trigger | Dispatcher + customer update queued | 11:29 | Workflow rule |
Delivery closeout
Proof-of-delivery capture
▧
Dock photo
DL-2039 · signed pallet count visible
Aug 18 · 15:42
J. Bell
Receiver signature
Signed by J. Bell · no exceptions
Aug 18 · 15:44
Memphis, TN
35.1495° N
35.1495° N
Location + notes
“No visible damage. 24 pallets received.”
35.1495 · −90.0490
POD record model: photo · signature · notes · timestamp · geolocation · load milestone. D-ONE owns the record even when capture devices or map providers are optional.
Audience controls
Communications + preferences
| Audience | Trigger types | In-app | SMS / email | Owner |
|---|---|---|---|---|
| Driver | Next action · HOS · document | Driver | ||
| Dispatcher | ETA · delay · geofence · POD | Dispatch | ||
| Customer | Pickup · ETA · delivery · POD | Relationship |
Preference toggles are visual references only. No notifications are sent from this showcase.
Stage 4 gate
Readiness checklist
Event vocabulary
ReadyLoad, driver, geofence, ETA, HOS, notification, and POD events have named states.
Milestone ownership
ReadyD-ONE owns pickup, departure, arrival, delivery, and exception history.
Driver Companion flow
ReadyThe mobile concept covers active loads, actions, messaging, documents, and status updates.
Proof of delivery
ReadyPhoto, signature, notes, timestamp, and geolocation are captured in one record.
Notification policy
In reviewDriver, dispatcher, and customer preferences are modeled by event type.
Optional connections
DefinedELD, GPS, and mapping providers remain replaceable input sources.
Offline behavior
NextQueue and sync rules for low-connectivity driver workflows still need definition.
Production controls
Demo onlyAuthentication, persistence, integrations, and live analytics are intentionally disabled here.
Operations workspace map
Open the connected surface
System boundary / important
D-ONE owns the workflow. Connections add context.
D-ONE owns tracking events, milestones, proof-of-delivery records, driver history, and the Driver Companion workflow. ELD devices, GPS providers, and mapping services are optional enhancements only.
Demo boundary
No authentication, real storage, persistence, imports, API calls, live analytics, or external service behavior is enabled.
Sample period · Aug 2026
Stage 5 / finalD-ONE demo / sample data — not connected to live records
D-ONE Optional Outside Connections.
Stage 5 keeps ELD, GPS, mapping, navigation, fuel, rates, and payment services optional around D-ONE-owned events, driver workflow, documents, and proof-of-delivery history.
Open Stage 5 showcaseMovement boundary
D-ONE owns tracking events. Outside signals may inform the view; disconnecting them does not stop the operating network.