Constant data is transmitted from the Tractor ECM unit, and from the Geotab GO Device. The information from the GO Device and Tractor ECM Unit is sent to a Geotab Database. Data that comes from installed GO devices flows to the MyGeotab Database. The Geotab Background Services were built by ASR to allow that data to flow to and from the Eleos Integration background services to be easily useable for customers. After the data is processed, the background service call procedures in the Eleos schema to update tables in TMWSuite.

 


Getting Data to MyGeotab

Before data makes its way to the Eleos Integration, the data needs to safely make it to your MyGeotab Database. There can be issues with capturing data if the below steps are not followed, so we recommend you review the following areas first.

  1. If The Odometer Initialization Process is not followed then miles reported can have issues. Please review this document to initialize the odometer reading before continuing if you haven’t already.

  2. The GO device reads Odometer increments as ECM status data updates and transmits to MyGeotab. If your ECM reading is 0, there is a disconnect in the unit model and how Geotab reads the Odometer values. Geotab can typically enable a “Beta” flag on the GO device that will alter how it listens for ECM readings and corrects the issue allowing for the data to be captured.
     
  3. If a Go9 device is not installed properly, connection issues or that device is not seated properly in the harness, then that data could be incorrect. Please ensure that you installed the device correctly, and have a stable connection.

If all the above is working properly, data is collected and goes to your MyGeotab database.


Data Types and Intervals

Now this is where the background service comes into play, data from MyGeotab gets fed back and forth from the service, and is housed inside your Eleos integration. Different data types run on different timed interval feeds to maximize efficiency since there is so much data from Geotab. These feeds are available to be customized in our appsettings.json file, that allows us to control whether a certain feed is turned off or on, along with the intervals that they run at.

  1. Hours of Service (HOS) – Days’ Hours, Remaining Hours in Cycle, and Changes to last 14 days
    • Runs on a 15-minute interval
    • Gets information about the driver's hours of service, including shift information, hours on/off shift, and time to break.
    • Feed updates the ELEOS.GeotabAvailability, ManPowerProfile, and DriverLogs tables.
  2. Duty Status Logs – Clock changes
    • Since this is tied to availability it runs on a 15-minute interval
    • Gets live updates of driver locations, zones, events, and any malfunctions
    • Feed updates the ELEOS.GeotabDutyStatusLogFeed, Eleos.GeotabClockEvents, and ELEOS.GeotabCurrentDutyStatus tables
  3. Location Data – Current Location, Address, Lat/Long, Odometer, and Fuel Level
    • Runs on a 5-minute interval by default
    • Gets live updates of driver location, vehicle, odometer values, and fuel levels
    • Feed updates the ELEOS.GeotabLocations, CheckCalls, ManPowerProfile, and TractorProfile tables.
  4. Fuel Transaction – Upload of fuel purchases to TMS that are in Geotab, for IFTA processing
    • Runs on hourly interval
    • Monitors if fuel levels change and any fuel transactions, and where they occurred.
    • Feed is saved in the ELEOS.FuelPurchase table.
  5. DVIR Logs – Upload of DVIR Logs along with any defects associated.
    • Runs on 15-minute interval.
    • Pulls any DVIR logs since previous DVIR log. 
    • Feed is saved in the ELEOS.GeotabDVIRLogFeeds table, and defects are saved in the ELEOS.GeotabDVIRDefects table.
    • Creates inspection tickets in TMT when configured by settings.

These five main telematics data types are synchronized to the TMS system, so they are consumable for the company.