How MFAH Navigator supports connected vehicles and in-cab devices: trip context that follows the trip, installable in-cab navigation, and route data shared across phones and tablets.
Connected mobility in MFAH Navigator means the trip — not the device — holds the state. A route planned at a terminal desk opens on the in-cab tablet with the same stops, the same hours-of-service clock and the same cost model.
Navigator installs to the home screen of tablets and phones and runs full-screen, with cached assets so the interface loads immediately at start of shift.
Route geometry, stop sequence, break placement and trip economics are stored with the trip, so switching devices does not lose the plan.
Passenger-vehicle navigation and commercial Truck Mode share the same discovery, weather and emergency layers with different routing rules.
The shell and last-loaded trip data remain viewable without a connection; live routing, place search and weather need connectivity.
Vehicle and load parameters are supplied through the truck profile and trip inputs. Any telematics or ELD integration is scoped case by case, with no certified vendor integration claimed.
Turn-by-turn maneuvers and hours-of-service alerts can be spoken so a driver keeps eyes on the road.
Yes, as an installable web application on in-cab tablets, phones and browser-based displays. Trip context is stored against the trip, so the same plan opens on any signed-in device. MFAH Navigator does not claim OEM head-unit certification.
The application shell and previously loaded trip data are cached for offline viewing. Live routing, weather and place search require a connection.
Yes. The route, stop sequence, hours-of-service clock and trip economics are stored with the trip rather than the device.
Not automatically. Vehicle and load details are entered in the truck profile or trip inputs. Telematics integration is handled case by case and no certified vendor integration is claimed.