Bring Geotab fleet telemetry into OLT TMS

Connect MyGeotab, reconcile equipment and driver identities, and use implemented location, route, odometer, driving-state, and duty-status data in OLT's transportation workflows.

  • Vehicle location OLT normalizes Geotab GPS records into timestamped vehicle positions for mapped equipment in TMS fleet and dispatch views.
  • Route telemetry OLT prunes stored raw GPS position rows after 90 days. For an older date, OLT can make one bounded backfill request to MyGeotab, but exact-day replay is not guaranteed because it depends on MyGeotab returning that range.
  • Odometer handling Geotab odometer diagnostics arrive in metres. OLT converts them to kilometres and can refresh the connected Fleet record even when no new GPS point arrives.
  • Driving-state updates Geotab's current is-driving signal distinguishes equipment that is operationally in use from equipment that is only communicating.
  • Tracked trucks and trailers Mapped trucks and trailers with tracking devices can supply the latest polled positions and route history in OLT TMS.
  • Assets without GPS devices A Geotab asset without a GPS device remains reviewable and individually importable, but it cannot appear on the current-position map or provide route history.

Before you connect

Have the MyGeotab access and OLT permissions needed to verify and save the connection.

  • MyGeotab database and server Each connection targets one named MyGeotab database. The create form shows https://my.geotab.com/apiv1 as a placeholder, and you must enter or confirm the server endpoint before testing.
  • Dedicated API-capable MyGeotab account Use a dedicated MyGeotab username and password that can authenticate to the database and read the devices, positions, odometers, driving state, drivers, and duty-status data your workflow needs. OLT stores the credential set encrypted.
  • TMS write access in OLT Saving and managing the connection or its device and driver mappings requires TMS write access. The separate credential test requires TMS read access.
  • Connection test before save OLT authenticates against MyGeotab and checks the tracked-device response before saving a connection. If that check fails, no connection is stored.

Supported workflow

Provider identities reach OLT records through explicit reconciliation and active mappings.

  • Test and save MyGeotab Enter the server, database, and dedicated account credentials in TMS GPS & ELD Integrations. OLT verifies the connection before it stores it.
  • Decide every device OLT activates deterministic matches to existing Fleet records by VIN, plate, or equipment number. Each remaining MyGeotab device waits for an explicit decision to map it, import it as a new asset, or ignore it.
  • Decide every driver OLT can suggest an active driver by email or unique name, but an administrator must explicitly map that identity or import the driver before duty-status data flows to OLT.
  • Poll active mappings Scheduled polling refreshes positions, kilometre odometers, and driving state for mapped equipment, plus duty status for actively mapped drivers.
  • Keep unmapped records outside telemetry workflows Positions from unmapped devices are ignored, bulk import skips untracked assets unless an administrator includes them, and suggested driver matches do not activate themselves.
  • Keep mapped duty status ELD-managed An active approved driver mapping feeds Geotab duty-status events into the driver's OLT HOS timeline and disables manual OLT duty-status changes while that mapping remains active.

Operating limits

OLT bounds polling and history requests and keeps the MyGeotab side read-only.

  • Polling runs between 5 and 600 seconds OLT clamps the stored polling interval to a minimum of 5 seconds and a maximum of 600 seconds. New connections default to 15 seconds.
  • Sync now makes the next poll due Sync now clears the connection's last-success marker so the next scheduled tick treats it as due immediately; it does not start a separate provider session.
  • Route playback covers one day at a time A playback request must span at least 1 minute and at most 26 hours, covering one organization-timezone day including a 25-hour daylight-saving day.
  • Playback uses stored data first OLT serves stored GPS breadcrumbs first. When they do not cover the requested window, each playback request permits at most one bounded MyGeotab fallback for that range and stores returned points for later requests.
  • Raw position retention is bounded Stored raw GPS position rows are pruned after 90 days. Exact-day playback beyond that retention window depends on MyGeotab returning the requested range and is not guaranteed.
  • Direct history queries are bounded The separate direct provider route-history query accepts a range of at most 40 days; longer ranges are rejected.
  • OLT does not edit MyGeotab records OLT authenticates and reads devices, drivers, positions, odometer diagnostics, driving state, history, and duty-status logs without creating, changing, or deleting records in MyGeotab.

Start with an OLT account, then confirm TMS write access and connect a dedicated MyGeotab account with API access.