Workflow for Predictive Maintenance in Connected Vehicles

Permissions and Access

Make sure Automotive, Automotive Scheduler, Actionable Event Orchestration, Context Definitions, and Connected Vehicle Services are enabled in your org.

Your Salesforce admin must have the Automotive Foundation User, Vehicle Connected Services, Automotive Scheduler, Context Service Admin, Rule Engine Designer, and Actionable Event Orchestration Designer permission sets assigned to them.

Key Steps

Here are the steps for predictive maintenance.

• When a critical event is received by the sensors in a vehicle, a diagnostic trouble code is shared by the telematics system with the driver. If the resolution is provided to the driver, there’s no further action taken. For issues that aren’t resolved, the diagnostic trouble code (DTC) and other diagnostic details are shared to MuleSoft.
• MuleSoft APIs use the source system identifier to get the vehicle identification number of the corresponding Vehicle record in Automotive Cloud. MuleSoft then passes on the diagnostic information to the actionable event orchestration framework in Automotive Cloud and a record alert, an asset milestone, and a case is created with the diagnostic details.
• Qualcomm sends a request to MuleSoft to get the list of nearby service centers for the identified fault along with the estimated cost to repair and time to repair. MuleSoft uses the information in the custom metadata types set up in Salesforce to identify the corresponding work type record in Salesforce for the identified fault.
• Qualcomm sends a request to MuleSoft to get the list of nearby service centers for the identified fault along with the estimated cost to repair and time to repair. MuleSoft uses the information in the custom metadata types set up in Salesforce to identify the corresponding work type record in Salesforce for the identified fault.
• Automotive Cloud triggers the Salesforce Scheduler APIs to get a list of service territories based on the vehicle’s location details shared by MuleSoft. The service territories are also queried based on the work type performed at the location. The Service Territory IDs are passed to MuleSoft.
• Automotive Cloud also uses the decision matrix and the expression set to find the estimated repair cost and time based on the DTC code. The information is passed to MuleSoft.
• MuleSoft consolidates the list of available service territories, the estimated cost, and time to repair and shares the information with Qualcomm. After the driver selects a service center based on their preference or proximity, the service territory ID is shared back to MuleSoft, and MuleSoft passes the information to Automotive Cloud.
• Automotive Cloud triggers the Salesforce Scheduler APIs to get the list of available time slots and agents at the selected service territory for the specific work type. The list of service resources (agents) who can perform the service for the specific work type and their available time slots is passed to MuleSoft.
• MuleSoft shares the time slot and service resource information with Qualcomm. The driver selects a service resource and their preferred time slot. The selections are passed to MuleSoft and MuleSoft uses the vehicle identification number to get the Asset ID in Automotive Cloud.
• Automotive Cloud triggers the Salesforce Scheduler APIs to schedule the appointment with all the required inputs. The Service Appointment ID is passed to MuleSoft and Mulesoft further shares it with Qualcomm. The driver is notified about the service appointment confirmation.