Routing past the maintained network
Grade and surface as constraints, not hopes.
Industries · Movement · Whitepaper
The last mile has no pavement.
Fleet operations whose routes end on a lease road, a logging spur or a remote site have a problem commercial telematics does not solve: the road network stops being in the map, and the driver stops being reachable, at exactly the same point.
01 / Problem statement
What actually goes wrong.
Standard fleet telematics assumes a road graph and a cellular modem. Both assumptions fail at the same place.
The graph ends. Once a route leaves the maintained network, commercial routing either refuses or produces a line across ground a loaded vehicle cannot cross. Drivers then navigate from memory, and a new driver has no memory.
The modem stops. Position reporting, dispatch and duty-status all depend on a link that is not there. The gap in the record is not a data problem; in most jurisdictions it is a compliance problem.
The in-cab surface is regulated. Whatever the driver interacts with while moving must be distraction-safe. That constrains the design far more than most fleet software acknowledges.
02 / Mechanism
How NavTrax addresses each one.
Each entry names the mechanism rather than the benefit, so it can be evaluated rather than believed.
- Off-network routing
- Forest service, lease and unmaintained roads route through the trail graph with surface and grade constraints, so a route to a remote site is computed rather than remembered.
- Store-and-forward duty records
- Position and duty-status entries queue durably and replay in causal order when any channel returns. The record has no gap, only a delivery delay that is itself recorded.
- Mesh as a dispatch channel
- Convoy vehicles relay for each other. A vehicle at the site is reachable through the one that is still on the highway.
- Driving-safe in-cab surface
- Six template entries on Android Auto and CarPlay, lists clamped to six rows while moving, canned messages only, and a guarded emergency entry.
- Vehicle telemetry
- OBD-II fault codes, tire pressure, coolant temperature and modeled fuel range, read against the service history rather than in isolation.
- Fleet administration
- Organizations, groups, vehicles, roles and an audit log, with SSO for a driver population that changes.
03 / Capabilities
In the field, this is what you have.
Gapless duty records
Durable queue, causal replay, delivery timestamps recorded.
Convoy relay dispatch
Reach the vehicle that has no signal through the one that does.
Compliant in-cab UI
Certified templates, six rows, no keyboard while moving.
Predictive maintenance signals
A developing fault flagged while the vehicle is still near somewhere that can fix it.
Fleet-scale administration
RBAC, provisioning, audit and SSO.
04 / Reference
| Constraint | Value | Enforced by |
|---|---|---|
| Max list rows while driving | 6 | Shared safety layer |
| Free-text entry while driving | Disabled | Both platforms |
| Destructive actions | Confirmation required | Alert template |
| Entries on the car screen | 6 | Car catalog |
| Template types | 5 | Mapped per platform |
05 / Process
Traced, node by node.
The route does not end where the pavement does.
In-car surfaces and off-network routing are Pro. Fleet administration is Enterprise.