Integrating with Ryder Maintenance Platform

Overview

Seamlessly integrate your Samsara eDVIR defect data with the Ryder maintenance platform to streamline maintenance, track defect resolutions, and upkeep for your vehicles and trailers leased or maintained by Ryder.

The Ryder eDVIR integration enables you to:

• Track vehicle and trailer eDVIRs and defects submitted by drivers from Samsara through to Ryder.
  
• Track Ryder defect resolutions in Samsara, including resolution time, status, and mechanic notes.
• Sync Ryder defect status in real-time on Samsara, including Resolved, Unresolved, and Deferred (postpone resolution) defects.

Requirements

Below are the requirements to enable the Ryder eDVIR solution. Please consult ATI for further clarification if needed.

Ryder

• Complete Ryder customer onboarding and obtain your Ryder account number.
• Ensure all Ryder vehicles and trailers are loaded in Ryder systems.
• Ensure all Ryder shops are enabled to receive and process defects sent by Samsara.
• Gather the Ryder vehicle VINs. In rare cases, if the vehicle has a Glider Kit, the VIN may not be auto-detected in Samsara. In that case, you must manually update the VINs in Samsara.
• Gather Ryder trailer VINs to upload in Samsara to enable trailer eDVIR workflow.
• Ensure all Samsara eDVIR defect types are registered in Ryder systems to process incoming defects.

ATI

• Complete the ATI license agreement for the Ryder eDVIR solution.
• Add "Ryder Mechanic" (ryderedvirintegration@assuredtelematics.com) in a "Maintenance" role for the Entire Organization in your Samsara dashboard. For more information about adding users, see Manage Administrators.

Samsara

• Create a Samsara API Token named "Ryder DVIR Integration."

  • If the total asset volume includes non-Ryder assets, you can leverage tags to limit the API token to Ryder assets only. For more information on creating a tag-scoped API token, see API Basics.
  • If you prefer to limit the API token scope to data that is specific to the eDVIR solution and not the ‘Entire Organization,’ then you must enable the following scopes within the API token. Refer to granular scopes for more details.
    
    • Drivers: Read Drivers
    • Maintenance: Read Defects, Write Defects, and Read DVIRs
    • Setup & Administration: Read Users
    • Trailers: Read Trailers
    • Vehicles: Read Vehicles
• If you use tags, ensure the Ryder vehicles and trailers are associated with the tag selected for the Ryder API token.
• If you use Glider Kits, manually update the vehicle VIN on the Samsara dashboard.
• If trailers are in scope, update the trailer VIN in the User Notes field for each trailer, on the Samsara dashboard.

Deployment

ATI manages the integration deployment. Visit www.assuredtelematics.com for more details.

Follow these steps to enable the Ryder eDVIR integration through ATI.

1. Email Survey_EDVIR@ryder.com and your Ryder account owner to request the integration.
   Ryder will register your account in the Ryder Open API gateway portal for ATI can turn on the integration. 
2. Ensure that you have satisfied all of the above integration Requirements.
3. Send the information listed below to the following representatives at ATI: ghoughton@assuredtelematics.com and cmedina@assuredtelematics.com.
   
   • Ryder Account ID
   • Samsara Org ID
     
   • Samsara API access token
     
   • Samsara Tag groups to enable
     
   • Number of assets to be included
     
   • Contact Name for billing
     
   • Contact address for billing
     
   • Your Samsara org URL

ATI integration relies on the VIN data to sync Samsara assets with Ryder assets. Asset and Driver synchronization runs in four-hour cycles.

Upon asset synchronization, ATI fetches the vehicle and trailer eDVIR from Samsara every five minutes and propagates to Ryder.

Ryder mechanic repairs and resolutions are sent back to Samsara every five minutes.

• Defects closed by Ryder mechanic display as Resolved in the Samsara dashboard.
  
• Defects deferred by Ryder mechanic for future resolution display as Unresolved in the Samsara dashboard, with the deferred mention in the mechanic notes.
  

Support Process

Integration support is managed by ATI. For issues with the integration, please email ghoughton@assuredtelematics.com and cmedina@assuredtelematics.com as well as your Samsara representative and Survey_EDVIR@ryder.com.

Troubleshooting

Issue: Some Samsara assets not showing up in Ryder systems

This can be due to any of the following reasons:

• Samsara API token is limited to a certain tag that isn't associated with the respective assets.
• Samsara API token does not include all required read/write scopes.
• If related to trailers, then possibly the trailer VIN is not populated in the User Notes field on the Samsara dashboard.

Issue: Defects that are visible on Samsara are not visible to the Ryder shop

This can be due to any of the following reasons:

• Samsara API token is limited to a certain tag that isn't associated with the respective assets.
• Samsara API token does not include all required read/write scopes.
• If related to trailers, then possibly the trailer VIN is not populated in the User Notes field on the Samsara dashboard.
• Ryder is yet to enable the Ryder shops in question with the eDVIR solution.
• Ryder defect types are out of sync with Samsara defect types, causing such eDVIRs to fail at Ryder processing.

Issue: Some defects that are resolved in the Ryder system still show as Unresolved in Samsara

This can be due to any of the following reasons:

• Ryder shop systems are out of sync with Ryder eDVIR systems.
• A broken integration either on the Samsara-ATI or the ATI-Ryder leg. Contact ATI to investigate further.

Issue: Some defects that are unresolved in the Ryder system show as Resolved in Samsara

This is likely because an administrator or a driver manually resolved the eDVIR from the Samsara dashboard or the Samsara Driver App. Refer to Customizable DVIR Settings to manage driver user-initiated eDVIR resolution.