Where MFAH Navigator fits in a connected fleet stack: telematics, ELD, dispatch and in-cab navigation working from the same trip data.
A connected fleet stack usually has telematics, an electronic logging device and a dispatch system. MFAH Navigator is the driver-facing planning layer that consumes trip parameters and returns a route, timeline and cost view.
Origin, destination, equipment profile, remaining clock and load economics describe a trip. Any system that can supply those inputs can be reflected in the Navigator plan.
Voice turn-by-turn guidance, hours-of-service prompts and route hazards are delivered in a format usable while driving.
MFAH Navigator does not claim certified integrations with specific telematics or ELD vendors. Integration is discussed on request and only announced when it exists.
Completed trips can be captured as journal entries with revenue, fuel, tolls and net profit for owner-operators tracking their own book.
There are no certified ELD integrations to announce. Hours-of-service inputs are entered or maintained in the driver profile.
Integration is possible in principle through trip inputs and is handled case by case. No vendor partnership is claimed.