Geotab DVIR Integration
The following document outlines the process for configuring the Geotab DVIR Integration in RTA. More info can also be found at Geotab Telematics Integration
If you want to see how Driver Reports work in RTA, go ahead and take a look at Review Driver Reports
Capabilities
The RTA Geotab integration automatically imports defects and mileage reported by your drivers using the Geotab Drive app. Vehicles are identified via the VIN number (stored in the serial number field in RTA). As status updates are made in RTA, such as notes, Work Order Assignment, or resolution, RTA will update Geotab with that information.
Did you know that you can have the component and location split out and digested by RTA by using a special convention? Simply use a pipe “|” character, and the left side will go into the component field in RTA, and the right side will go into the location field!
For example, take “Fender | Passenger Side”. It would end up like this in RTA:
Component: Fender
Location: Passenger Side
Defects
When your drivers report a defect using the Geotab mobile app, the Geotab RTA Integration will automatically import those defects into RTA using the Driver Reports module.
Which Geotab defects import into Fleet360. Driver Report Maintenance is not a full mirror of every Geotab Asset Inspection row. The integration imports Geotab DVIR defects that are still open and need repair. Defects that Geotab shows as repaired, reviewed, safe or reviewed, not necessary, or otherwise not repair-needed are not expected to create new open Driver Report defects in Fleet360.
If several Geotab DVIRs did not appear in Fleet360, first check their Geotab repair status. Items already marked repaired or not necessary are filtered out by design and are not missing. See Driver Reports (DVIRs) for how defects appear once imported.
Mileage Updates
Mileage updates from Geotab should be handled via Geotab Telematics Integration. However, if you don’t have this setup, no worries! The mileage from the vehicle will be automatically updated when the DVIR is imported into RTA.
Installation
Using the steps provided in Geotab Telematics Integration use the username, password, and database to fill out the form on the RTA Web App. That’s it! We’ll start importing defects into the RTA Driver Report Module.
Deferring of lines that came from Geotab will cause the driver to essentially be locked out. Right now, Geotab only offers 2 resolutions - Fixed, or not necessary for repair. Because we don’t want to convey an inaccurate status to drivers about the vehicle, we opted to leave the defect in progress and add a note so that the driver knows that there is still an outstanding repair. Unfortunately, in Geotab things have to either be resolved or not resolved.
Troubleshooting missing DVIRs
If DVIRs reported in Geotab are not showing in Fleet360, work through the checks below before treating it as a missing import.
Check | What to confirm |
|---|---|
Geotab repair status | Only open, repair-needed defects import. Repaired, reviewed, safe or reviewed, and not necessary items do not create new defects. This is expected, not a missing DVIR. |
Asset match (VIN) | The asset VIN in Geotab must match the VIN stored in the asset serial number field in Fleet360. |
Integration health | Confirm the Geotab integration is connected and running. |
Hardware and app support | The defect must be reported through the Geotab Drive app in a way the integration supports. |
Sync timing | Allow normal sync time before treating a defect as missing. |
Do not treat every Geotab Asset Inspection row as a missing Fleet360 Driver Report defect. Many rows are repaired, reviewed, or not necessary and are filtered out by design.
If a Geotab defect is still marked repair-needed and does not appear in Fleet360, collect the following so it can be traced as an integration issue: asset, inspection date and time, driver, defect or component, and the Geotab repair status.