NavGuru FAQ

No. Dispatch stays in your TMS and, on Platform Science fleets, in Workflow. Position and vehicle data flow in from Platform Science, Geotab, Samsara, Motive and other supported feeds. NavGuru replaces the navigation task in the cab and adds the trip record; it does not replace the systems around it.

No. Every route is computed against the vehicle profile (height, weight, length, axles, hazmat) and the restriction graph. Change the truck and the route changes, not only the warning: a 13 ft 6 in truck is routed around a 12 ft 6 in structure; an 11 ft van is not. Parkways are excluded for trucks regardless of height.

Tablets or Android devices your drivers already use, a list of vehicle profiles (height, weight, length, axles, hazmat), and one dispatcher and one operations owner. On Platform Science tablets the fleet asks Platform Science to enable NavGuru; on other Android devices it is an app install. No new in-cab hardware, no implementation fee, no fleet-specific code. The full list is on the Get started guide.

Activation is measured in hours on supported tablets. The target from fleet approval to first live driver is 10 business days or less, and most of that is the fleet's own configuration: vehicle profiles, zones, routing policy, a 45-minute dispatcher session and 10-minute driver briefings.

No. Every fleet difference lives in configuration: vehicle profiles, zones, routing policy, alert lead distances, fuel network. Enterprise deployments always involve some customer-side configuration and sign-off; they do not involve MapUp writing code for one fleet.

That is the fleet's choice, set once per vehicle profile. With a hard route lock the driver follows the dispatched route and any departure is rerouted back and scored. With a soft lock the driver can choose among truck-legal options. Fleet mandates (restriction alerts, restricted areas, geofence speed, corridor handling, fuel prescription cards) are locked; conveniences (rest area markers, preferred brands) can be left to the driver.

NavGuru reroutes to the next best truck-legal route from the truck's position within a few seconds. The departure is logged with position, time and distance, the reroute is numbered on the dispatcher's screen, and the post-trip adherence report shows planned against actual. Miles added by a safety reroute (clearance, weight, hazmat, closure) are attributed to the system, not the driver.

Not by default, and large fleets do not want that: a truck leaves its planned line many times a day for a gate, a rest stop or a fuel stop. Configure an alert rule for the events you want in real time (zone entries, corridor departures beyond your threshold) and they go to the dashboard, email and connected systems. Everything else is in the after-trip list under Route compliance.

Planned route against the GPS track, per dispatch: on-route percentage, out-of-route miles, excess miles beyond plan, deviations with cause. Safety reroutes and mandatory dispatch changes re-baseline the route so no deviation is recorded. Driver-initiated deviations and added stops carry detour time, extra miles and a reason code. The dispatcher guide explains the difference between the live on-route figure and the post-trip adherence figure.

From the fleet's own transactions, not a model. Tolls on navigated loads against what the fleet paid on the same lanes before, from its toll history. Fuel from card transactions: gallons in against out of network, prescription compliance, cents per gallon captured. Out-of-route miles avoided from the GPS track. A fleet can audit every number against its own data.

FuelGuru is a separate product that runs inside NavGuru. When it is enabled, the prescribed fuel stop and gallons sit inside the driver's route, priced on the fleet's own card rates (WEX, EFS, Comdata), the state price and tax spread, and the detour cost, constrained to the fleet's network. Without the fleet's rate file and network, prescriptions are not meaningful.

As a spreadsheet or CSV with the zone name, type, geometry or address, and the field you want displayed in the driver's alert. Zones reroute the truck automatically; yard limits are spoken on entry; customer gates and docks appear in the arrival guidance. Your MapUp contact gives you the upload location during onboarding.

A vehicle appears in Live monitoring once its driver starts NavGuru and the truck moves. The dashboard does not show how many tablets have the app deployed; that is managed between the fleet and Platform Science. If your telematics feed is connected, trucks also show as connected units for out-of-route reporting whether or not they ran the app.

A build ships every two weeks. Release notes are in the dashboard sidebar. Driver items raised at the terminal are collected weekly and fixed within the release cycle.

A shared issue log with severity, owner and date; a weekly 30-minute review; and a fix commitment by severity (P0 within five business days, P1 within one sprint). Details and how to raise a ticket are on Troubleshooting and support.

Planned route against what the truck actually drove: planned miles, driven miles, excess miles, on-route percentage, deviations. No, not every deviation counts: the record separates driver deviation, dispatcher change, safety reroute, integration behavior and routing issue. Safety reroutes and mandatory dispatch changes re-baseline the route so no deviation is recorded.

Through Platform Science Workflow: the job arrives on the tablet as it always has, the driver taps Navigate on the stop, and NavGuru opens with it. The dispatch appears in your Dispatches list with its stops in order. Nothing is re-keyed. Dispatches can also be created in the NavGuru dashboard or sent by API. See how a trip reaches the cab.

Yes, in the NavGuru dashboard. Edit the route or the stops and the change reaches the driver's screen in about two seconds without interrupting navigation. Mandatory changes apply after the driver's current maneuver and are announced; optional ones are offered with the added miles and minutes. Changes made in your TMS arrive as a new Platform Science dispatch, because a Platform Science dispatch cannot be edited once created.

On a Platform Science tablet the driver can accept a new dispatch only when the truck is stopped; the tablet blocks app switching while moving. The dispatch is waiting and will be picked up at the next stop. If the truck is already navigating, change the running trip instead of creating a new one.

The live figure measures against the route currently active in the cab. When the driver leaves the route and NavGuru reroutes, the new route becomes the reference. The post-trip adherence figure measures against the route the dispatch was sent with, and you can compare the same drive against each route option in the replay. Both are correct; they answer different questions.

The driver closed the app. On a Platform Science tablet that also means Workflow cannot relaunch it until the truck stops. When the driver reopens NavGuru, a new session starts and tracking resumes; the earlier session stays in Historical with its reroutes and miles. Nothing needs to be recreated.

Open the session in Live monitoring (Live or Historical), then Map controls at the top left, then Places. Turn on the categories you want. To add a stop: the driver taps the place on the tablet (quickest), or you use Dispatch via points, or Dispatches, Details, Add stop with an address or latitude and longitude.

The truck has just left the route and the dashboard is calculating the excess before it redraws. It clears in a few seconds and telemetry keeps updating throughout.

The dashboard reads the engine's fuel sensor through the telematics platform. A float in a moving tank reads a wave, so the raw value moves by several percent on curves and grades, and every telematics vendor filters it. The chart shows the raw series; FuelGuru smooths it before using it. A difference of a few points at one moment is expected.

Under Fleet, in vehicle profiles. Platform Science supplies vehicle ID, VIN and engine data, not dimensions, so the fleet sets the profile. Until it does, a standard 5-axle profile is used. Drivers confirm the profile before each trip.

Yes. Use Routing to plan and price a route for any profile. Zones and restrictions are applied the same way they are for a live dispatch.

Follow the posted restriction and the safe, legal condition. Then report the exact location and direction so the fleet or MapUp can check the data. NavGuru is an aid to safe commercial navigation, not a replacement for signs, on-site instructions or your judgment.

Very little. Turns and warnings are spoken; one alert at a time; a choice, when offered, is one tap; silence never changes your route. Search, comparison and anything that needs reading wait until you stop. Follow your fleet's safety policy and the tablet's own restrictions.

No. Dispatch sends one route. If you leave it, NavGuru gives you a new truck-legal route from where you are. If your fleet allows route choice, you will see the options when the trip starts.

That is the Platform Science tablet's safety lock, not NavGuru. Pull over when safe, then tap Navigate in Workflow again or open NavGuru from the app list. Your trip continues.

Most often the truck is on the default vehicle profile rather than your fleet's. Check the profile shown at the start of the trip and ask dispatch to set yours. Alerts for structures on parallel roads have been scoped down. Your route itself will not take you under a restriction lower than the configured truck.

It speaks turns and warnings. Warnings that matter (low clearance, weight, hazmat, closures) are spoken in stages, timed to the last safe exit. You answer with one tap when a choice is offered, and silence never changes your route.

While moving: one tap on a place on the route adds it as your next waypoint. While stopped: category chips and a comparison list, with out-of-corridor places flagged in amber with the extra miles. Where your fleet runs FuelGuru, the fuel stop is already in your route with the station and gallons. See the driver quick start.

It is available near your stop or destination at low speed, where it shows the entrance and the docks. It switches off at higher speeds to save data.

NavGuru asks you to confirm the profile again when it detects a trailer swap or the profile changes. Tell dispatch if the profile on screen is wrong; every clearance warning depends on it.

Dispatch sees the trip: position, speed, fuel level, reroutes and the planned-against-actual result. Safety reroutes and changes dispatch made are attributed to the system or to dispatch, not to you. Your fleet decides whether you are asked for a reason when you add an out-of-corridor stop; if you are, it is asked at your next stop, never while moving.

The app exists for Android and iOS, but whether you may use it in the cab is your fleet's policy, and most fleets prohibit phone use while driving. On Platform Science tablets NavGuru is on the tablet; nothing is needed on a phone.

Because the fastest road for a car is often not a legal road for the truck. A traffic reroute is offered only when a faster truck-legal alternative exists, and it still respects the vehicle profile, fleet zones and routing policy.

In the cab: Platform Science tablets (embedded, fleet toggles it on) and Android devices running the NavGuru app; an iOS build is available through your account team. Position and vehicle data flow in from Platform Science, Geotab, Samsara, Motive and other supported feeds for live monitoring and out-of-route reporting. Other in-cab platforms connect through the same adapter pattern.

Three changes to the fleet's Platform Science configuration: add NavGuru to the status bar availability list, set NavGuru as the navigation app with wheels-in-motion enabled, and point the Workflow Navigate button at NavGuru. Then deploy to the tablets' configuration group. Step by step on Set up NavGuru on Platform Science.

Workflow keeps the job record; NavGuru keeps the trip record. On Platform Science the navigation app takes the job from Workflow and reports to its own back office; that is how Platform Science's own navigation and other navigation apps on the same tablets work. What flows: Workflow to NavGuru (the job and its stops), NavGuru dashboard to tablet (route and stop changes in about two seconds), and NavGuru to its dashboard (position, fuel level, reroutes, adherence). Arrival and departure are marked in Workflow and NavGuru follows them, so the two records line up by dispatch.

Hours-of-service recording is the ELD's job and the ELD app on the tablet does it. NavGuru reads the driver's live remaining hours from the Platform Science ELD, so the plan starts from the actual clock, places rest stops on the route under the selected federal rule (70/8 or 60/7, 11 hours driving, 14 on duty, 30-minute break), and shows the hours on the NavGuru screen.

From the fleet. Platform Science and other telematics feeds supply the vehicle ID, VIN and engine data; height, weight, length, axles and hazmat status are set in NavGuru vehicle profiles. Drivers confirm the profile before each trip, and re-confirm on a trailer swap.

Restrictions come from surveyed and government sources with per-event confidence rules: the National Bridge Inventory, over 120,000 low-clearance records, posted weight, hazmat, length and width limits, and live restriction feeds from more than 100 state and provincial agencies. A restriction alert requires a surveyed or government source with no conflicting data; where sources disagree the app reroutes but says "possible restriction". Traffic and closures are pulled from live sources at every route calculation, so each new route reflects current conditions, and the on-map traffic color layer refreshes on a fixed interval between recalculations.

A proprietary truck routing engine that computes every route against the vehicle profile and the restriction graph, and prices it on the fleet's tolls by vehicle class and transponder, fuel on negotiated rates, and out-of-route penalties. Routes can also originate in the fleet's TMS or PC*MILER geometry and be made executable and measurable in NavGuru.

The Android and iOS apps go through independent penetration tests with retests after remediation. Fleet data is separated per account, and dashboard users have role-based access managed under Members.

Through Platform Science's application management for Platform Science fleets, and through Google Play or the fleet's device management for Android devices. New driver-facing features ship as app builds; iOS builds go through Apple's review before they are available.

Fleet name; vehicle ID, driver ID and the trip or dispatch ID; date and time with the time zone; where the truck was and which direction it was heading; the vehicle profile if it is a restriction question; what you expected and what you saw; a screenshot or photo where safe. A specific trip and location is investigated the same day. Severities and commitments are on Get started, section 12.

Here. Every question answered twice on a fleet's shared channel is added to this page under the asker's group.