Connected service categories
08
Cataloged for optional use
D-ONE / Demo workspace
Stage 5 / connections workspace
A self-sufficient D-ONE operating network with optional outside services as enhancements only. D-ONE owns the record; connections add context where useful.
ELOHM Command Signal
Outside context stays scoped
ELOHM may enrich D-ONE records through Stage 5 connections; D-ONE remains the system of record.
Open connectionsD-ONE owns its complete operating network: workflow, records, partner history, tracking events, documents, billing, compliance, and intelligence. DAT, Fleetio, Trucker Path, ELD devices, GPS providers, mapping, fuel, payment services, Sequence, and Lettuce can add useful context—but they never become the system of record.
Connected service categories
08
Cataloged for optional use
Active integrations
00
Sample state · none enabled
Data-sync readiness
84%
Boundary and ownership model mapped
Optional services enabled
00
D-ONE operates without them
D-ONE-owned records protected
100%
Core history remains the system of record
Independence model
Every optional service has a useful edge, but none of them carries the operating network. D-ONE remains usable before, during, and after any connection.
D-ONE owns the history; outside services enhance it.
Optional service catalog
Market context can sharpen qualification and lane intelligence.
Reference load-board availability and market context.
D-ONE remains fully usable without this service.
Optional load search and rate intelligence enhancement.
D-ONE remains fully usable without this service.
Compare historical market rate context by lane.
D-ONE remains fully usable without this service.
Add deeper market intelligence to D-ONE analysis.
D-ONE remains fully usable without this service.
Give a dispatcher a quick external rate reference.
D-ONE remains fully usable without this service.
Outside maintenance context can enrich a D-ONE-owned fleet record.
Bring service reminders and equipment context into view.
D-ONE remains fully usable without this service.
Navigation tools can inform route decisions without owning the movement record.
Add driver-facing route, parking, and navigation context.
D-ONE remains fully usable without this service.
Vehicle signals may enrich events, while D-ONE keeps the accountable history.
Reference hours-of-service and movement signals.
D-ONE remains fully usable without this service.
Optionally inform location and arrival context.
D-ONE remains fully usable without this service.
Route calculations can support planning, not replace D-ONE milestones.
Offer distance, route, and stop planning context.
D-ONE remains fully usable without this service.
Spend and fuel context can make owned margin and fleet records more useful.
Enrich cost and fuel planning for a lane or asset.
D-ONE remains fully usable without this service.
Provide optional payment and settlement context.
D-ONE remains fully usable without this service.
Optional finance execution and contractor tax support around D-ONE-owned history.
Optional payment execution and finance support around D-ONE-owned records.
Outside the D-ONE automation engine; D-ONE owns billing history.
D-ONE remains fully usable without this service.
Optional tax and accounting support for independent contractors and drivers.
Outside the D-ONE automation engine; D-ONE owns settlement history.
D-ONE remains fully usable without this service.
Future connections should make the operating picture clearer, never more fragile.
Leave room for carefully scoped operational enhancements.
D-ONE remains fully usable without this service.
Connection readiness
| Category | Sample status | Data-flow direction | Disconnect impact |
|---|---|---|---|
| Load boards & rates | Catalog mapped | Reference context → D-ONE lane intelligence | No impact — D-ONE keeps operating history |
| Fleet maintenance | Ready to connect | Service context → D-ONE truck record | No impact — maintenance views remain available |
| Navigation tools | Optional | Route context → D-ONE movement planning | No impact — dispatch and driver flow continue |
| ELD & telematics | Not connected | Signals → D-ONE events / HOS review | No impact — live tracking is disabled in demo |
| Mapping & routing | Optional | Travel estimates → D-ONE ETA context | No impact — D-ONE milestones remain owned |
| Fuel & payments | Optional | Cost context → D-ONE margin / settlement history | No impact — billing remains D-ONE-owned |
| Finance automation | Ready to connect | Execution / tax context → D-ONE finance history | No impact — D-ONE billing remains available |
| Other enhancements | Not connected | Scoped source context → labeled D-ONE records | No impact — core workflow is self-sufficient |
Migration & enhancement path
Optional services become useful after D-ONE has a stable record to enrich—not before.
Create the D-ONE load, truck, maintenance, event, document, or settlement record first.
Open owned surface 02Bring in a labeled source value only when it helps a team qualify, plan, monitor, or settle.
Open owned surface 03Store the decision, owner, status, and result in the D-ONE operating history.
Open owned surface 04Remove the enhancement and continue with the complete D-ONE workflow and records.
Open owned surfaceMarket rates
Inform lane intelligence; D-ONE owns the decision history.
Maintenance reminders
Enrich fleet records; D-ONE owns the service timeline.
Location signals
Inform ETA context; D-ONE owns the movement events.
Stage 5 gate
Ownership boundary
ReadyD-ONE workflow, operational history, partner network, tracking events, documents, billing, compliance, and intelligence are named as core.
Service inventory
ReadyOptional services are grouped by category with purpose, role, data exchange, and sample connection state.
Source labeling
ReadyReference values stay labeled as outside context and never overwrite the D-ONE system of record.
Data direction
ReadyEach category has an intentional flow into a D-ONE-owned record or intelligence view.
Privacy posture
Demo referenceFuture connections are scoped, permissioned, reviewable, and disabled in this visual blueprint.
Disconnect behavior
ReadyRemoving any optional service has no impact on D-ONE workflow continuity.
Migration path
ReadyTeams can add enrichment after the owned record exists and keep history portable.
Production controls
Demo onlyAuthentication, storage, imports, API calls, live tracking, and analytics remain disabled.
D-ONE workspace
Complete D-ONE stage path
Stage 5 finishes the showcase with an optional outside layer around a complete D-ONE operating core.