web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Blogs / udynamics365 / Dynamics 365 Automotive Acc...

Dynamics 365 Automotive Accelerator

Uday Mer Profile Picture Uday Mer 162

The Automotive Common Data Model (CDM) extends the Microsoft Common Data Model for deals, sales contracts, specifications, fleet, warranties, inspection, test drives, branding, business, customer-vehicle relationship, vehicle and equipment, lead, service and after-sales management, and more. The Automotive CDM came from working with some of our top tier partners such as Annata and Oxlo, sitting with, observing, and learning from many of our automotive customers about their desire to quickly drive digital transformation, starting with consumer experience, and the challenges of managing data across many systems of record.

Our approach includes:

  • Create enabling technology that lowers the barrier to entry for vehicle OEMs, mobility providers, dealer groups, and importers, and to introduce standards that make for a richer customer experience.
  • Microsoft partnering with leading thought leaders in the automotive industry as well as a Steering Team comprised of global customers and partners to create an automotive common data model (CDM) that reflects the common automotive scenarios.
  • Learning from data model challenges of the past and design a streamlined, open foundation for customers and partners to rapidly build applications and connectors.
  • Incorporating data standards into the model against widely adopted data standards like STAR.
  • Harnessing the power of our partner solutions, along with the Microsoft technology stack – Azure, Office 365, Power Platform, Dynamics 365, Power BI, Microsoft Connected Vehicle Platform (MCVP), Virtual Assistant, – focused on delivering omnichannel customer experience and streamlining back office operations.

The Microsoft Common Data Model for Automotive is the first of its kind to provide a model that reflects industry best-practices, insight and integration across existing vehicle retail networks, and also incorporating emerging mobility businesses.

Challenges

Some of the key challenges that were considered while creating the Microsoft Common Data Model for Automotive include:

  • Customer Insights: Transform transactional and behavioral omni-channel data into a data estate that enables customer experience management
  • Digital Marketing and Customer Engagement: End-to end customer experience management integrating digital marketing, contact centers, loyalty, mobility, shopping and purchase, service, and lifetime engagement
  • OEM-to-dealer integration: Enable data insights and managed consumer experiences across franchised dealer networks
  • Standards and openness: Establish publicly available standard data schema and integration standards that address the concerns of our vehicle OEM, mobility provider, dealer group, and importer customers, whose legacy systems slow down innovation with limited data transparency and interoperability.

Microsoft Common Data Model and Automotive CDM Integration

Microsoft Common Data Model & Automotive CDM

Entities within the solution

  • 91 Entities (79 new & 12 extensions to existing CDS Core and First Party Application Entities)
BusinessSales & MarketingCustomersService & After-SalesVehicle & Equipment
Aggregate KPIDealCustomer AttachmentService AppointmentAttribute Type
Aggregate KPI ContextDeal CustomerCustomer IdentifierService Appointment TypeConfiguration Code
Aggregate KPI MeasurementDeal DeviceCustomer Identifier TypeService ContractConfiguration Option
BusinessDeal Device Add OnLeadService Contract DetailDealer Plate
Business FacilityDeal File Service Contract TermsDealer Plate Device Assignment
Business OperationDeal Terms Service Contract TypeDevice
Business Operation Customer PreferenceDeal Type Service OrderDevice Brand
Business TypeFinancing Opportunity Service Order GroupDevice Class
Dealer PlateFinancing Opportunity Detail Service Order JobDevice Component
Dealer Plate Device AssignmentLead Service Order Job DetailDevice Generation
Operation CodeLead Device Service Order Job TypeDevice Inspection
Operation TypeLead Device Specification Service Order TypeDevice Inspection Checklist
LeadLead Disposition WarrantyDevice Inspection Checklist Type
Lead Disposition Activity Warranty LimitDevice License Plate
Lead Price Type  Device Measure
Lead Prospect  Device Measurement
Lead Specification Type  Device Meter
Opportunity  Device Model
Sales Contract  Device Model Code
Sales Contract Device  Device Observation
Sales Contract Payment  Device Observation Type
Sales Contract Terms  Device Registration
Sales Contract Type  Device Sensor
Test Drive  Device State
Trade In  Device Style
   Device Type
   Device Variant
   Device Warranty
   Device Warranty Limit
   Fleet
   Fleet Device
   Lead Device
   Specification
   Specification Accessory
   Specification Attribute

Capabilities 

The following represent some sample entity relationship diagrams about how to model key segments of the Automotive Common Data Model.

How to Model Vehicle and Equipment

Vehicles are referred to in the Accelerator as devices, since the accelerator is designed to be more general purpose that simply automotive retail. The device concept is a generic way to capture all the detail of a complex piece of equipment such as cars, RV’s, boats, industrial equipment, and so on. 

The BMW X3 xDrive 30i is an SUV style vehicle manufactured by BMW. The vehicle is one of several available X3 models and this particular model is again available in a number of trim levels, such as the xLine Design. Its design and specifications evolve over time and we are looking at a 2019 model which the manufacturer refers to as the G01 generation.

Example: Technical Specifications of a 2019 BMW xDrive 30i

The BMW X3 xDrive 30i is an SUV style vehicle manufactured by BMW. The specifications for this particular vehicle include engine, transmission, performance and more.

How to model vehicle and equipment

Example: Fleet Management

Contoso has an overview of cars allocated as demos across different locations and groups those cars into fleets with specific purposes. Some of these cars are specifically for test drives and are specified as part of test drive fleets for each location.

How to model fleet

How to Model Business

Example: National Sales Company

A national sales company owns two local dealerships, one in New York and the other in Boston.

How to model Business

Example: Dealer group

The Contoso dealer group consists of a two legal entities, Contoso Seattle and Contoso Denver. Contoso Seattle runs business from two locations: Contoso Seattle Downtown which handles all new car sales and Contoso Seattle University handles used car sales as well as service.

How to model Business - Example 2

How to model Sales and Marketing

Example: Lily Conner is interested in a 2018 BMW X3 xDrive 30i

Lily Conner contacted the Certified Pre-Owned Sales department at Contoso Seattle University because she is interested in a 2018 BMW X3 xDrive 30i. Lily has already booked a test drive for such a vehicle but also indicated that while she is most interested in this particular type of car, she might also consider other options as long as they have automatic transmission and ideally leather interior as well.

How to model Lead

source https://community.dynamics.com/365/b/dynamics365isvsuccess/posts/a-first-look-at-the-dynamics-365-automotive-accelerator


This was originally posted here.

Comments

*This post is locked for comments