Predictive Maintenance with Qualcomm Car to Cloud in Automotive Cloud

Connected Vehicle in Automotive Cloud works seamlessly with the Qualcomm Car to Cloud (C2C) telematics system and uses Mulesoft integrations to help automotive manufacturers build predictive maintenance for vehicles. Use the Predictive Maintenance integration app to sync vehicle event data with Automotive Cloud. Qualcomm C2C captures the event data in real time and sends it to Mulesoft for further processing. Prebuilt integrations in Mulesoft parse and transform the data in a format that’s actionable by Automotive Cloud. Based on the diagnostic code, Automotive Cloud sends a repair estimate and list of service appointment centers to the customer. Customers can select the date and time of the appointment and schedule a vehicle service appointment at their convenience.

Required Editions

Available in: Enterprise, Unlimited, and Developer Editions.

Note The predictive maintenance use case in Connected Vehicles is preconfigured to work with Qualcomm’s Car to Cloud native APIs and Mulesoft integrations. If you want to recreate the process with a different telematics provider and integration provider, contact your Salesforce admin and work with your integrations team to customize the APIs.

• Workflow for Predictive Maintenance in Connected Vehicles
  Review the high-level workflow before you plan and implement the predictive maintenance workflow for connected vehicles in Automotive Cloud.
• Deploy the Mulesoft App for Predictive Maintenance
  Turn on Automotive Cloud Integrations and use the predefined app and its named credential to connect your external telematics system to Salesforce. Use the app to connect Qualcomm Car to Cloud with Automotive Cloud and execute the processes for predictive maintenance.
• Create Custom Metadata Types for Predictive Maintenance
  Create a custom metadata type to represent work types and work type groups. Mulesoft retrieves the Work Type ID and Work Type Group ID from the custom metadata type to categorize the type of service required for a vehicle. For example, if the Diagnostic code represents an engine malfunction, Mulesoft can map the work type group as Critical Services and the work type as Engine Repair.
• Create a Custom Object to Store Predictive Maintenance Information
  Create a custom object in Automotive Cloud that stores key information related to a diagnostic code and its related information, such as the estimated time required for repair, maximum and minimum cost of repair, and the type of issue. When Qualcomm Car to Cloud shares event data, Mulesoft uses the information in this custom object to share details about an estimated repair with the customer.
• Create a Decision Matrix For Predictive Maintenance
  Create a decision matrix that maps the estimated time, maximum cost, and minimum cost of repairs to specific diagnostic trouble codes (DTC). The decision matrix uses the DTC details sent by Mulesoft as input and triggers an expression set that maps each code to the relevant cost and time estimate. The output is sent to Mulesoft by Automotive Cloud and is in turn shared by Car to Cloud to the driver’s human machine interface (HMI).
• Create an Expression Set for Predictive Maintenance
  Create an expression set that filters the estimated cost and time required for a repair based on the diagnostic trouble code (DTC) shared by Qualcomm’s Car to Cloud system via Mulesoft. The result is shared with the driver in real time based on which the driver can request for available slots at their nearest service center.