SAP Digital Vehicle Hub

[JohannesReichel]

SAP has just launched the new product SAP Digital Vehicle Hub.

In this blog post we present the key features and capabilities of SAP Digital Vehicle Hub 1.0 and introduce a series of blog posts with deep dive sessions on various topics around SAP Digital Vehicle Hub.

Overview

The SAP Digital Vehicle Hub is an integral part of the future SAP Automotive Industry Cloud, representing the central vehicle repository along the automotive value chain, based on SAP Cloud Platform. It manages all types of vehicle related data, such as master data, transactional data and usage data.

The SAP Digital Vehicle Hub is powered by the SAP Asset Intelligence Network, which enables sharing concepts for vehicle data between players in the automotive value chain e.g. OEMs, distributors, dealers or 3^rd party service providers.

SAP Digital Vehicle Hub addresses the business challenge that currently process and information silos (systems) around the vehicle are disconnected and not automated within the value chain. The various stakeholders have relied on the model of "request / receive" which is no longer efficient. Large amounts of data need to be continuously exchanged with OEMs, automotive suppliers, dealers, service providers, and end customers.

SAP Digital Vehicle Hub solving current business challenges

Therefore, the SAP Digital Vehicle Hub enables the creation of a digital twin of each vehicle and provides 360-degree view on the entire vehicle lifecycle.

Key Features

SAP Digital Vehicle Hub is the central repository for all vehicles and vehicle related information:

SAP Digital Vehicle Hub as a repository for vehicle lifecycle data

In addition, SAP Digital Vehicle Hub includes the following features:

• Search and analyze the entire vehicle fleet (Fiori apps to search and view vehicles based on UI5 standard)


• REST APIs to create, update, search and read vehicles for external consumption


• Ready-to-use through pre-delivered content for vehicle modelling with custom extension capabilities


• Easy adaptation to company specifics via customizable vehicle attributes and attachment of unstructured data, such as signed lease agreements or certificates


• Role-based access allows to control who is accessing which vehicle objects and data fields


• APIs are secured via the OAuth 2.0 authorization framework of SAP Cloud Platform UAA service supporting both client access and user access


• Using SAP Enterprise Messaging for event driven communication


• Capability to integrate with SAP Analytics Cloud to enable reporting on the vehicle fleet

Another key feature of SAP Digital Vehicle Hub is the ability of sharing vehicles and vehicle information. With SAP Digital Vehicle Hub it is possible to share with your business partners vehicle related data within the network.

Building an Automotive Ecosystem based on SAP Digital Vehicle Hub

The sharing concept of SAP Digital Vehicle Hub allows to specify what vehicles and what kind of information (e.g. only maintenance information) will be shared with business partners. This enables the creation of a digital automotive ecosystem based on SAP Digital Vehicle Hub.

Key Integration Capabilities

SAP Digital Vehicle Hub provides an out-of-the box integration from SAP S/4HANA SAP Vehicle Management System (VMS) enabling customers to easily upload and transfer vehicle data from the SAP Vehicle Management System into SAP Digital Vehicle Hub. This includes:

• Transfer vehicle object with configuration


• Transfer transactional data (sales order, purchase order, incoming and outgoing invoices)


• Transfer vehicle status and location


• Configuration in SAP S/4HANA for mapping of material, classification, characteristics and VLCVEHICLE to corresponding SAP Digital Vehicle Hub data objects


• Data transfer via standard CPI iFlow

The system prerequisites for the VMS integration are as follows:

• SAP S/4HANA on-premise 2020 system or higher.


• You have implemented the following SAP Notes: 2949130, 2958457, 2957704

System Landscape with SAP DVH

 

From a system landscape perspective, the SAP Digital Vehicle Hub is the central repository for vehicle related information coming either from SAP S/4HANA VMS via CPI or from external systems via the provided APIs. In addition, SAP Enterprise Messaging can be used to capture changes in SAP Digital Vehicle Hub for further processing in other applications.

More Information

Product homepage: SAP Digital Vehicle Hub.

SAP Help Portal: https://help.sap.com/viewer/product/SAP_DIGITAL_VEHICLE_HUB

Blog series from SAP Automotive Industry Business Unit: https://blogs.sap.com/2020/10/02/automotive-industry-trends-the-digital-twin-of-the-vehicle-part-1/

Community homepage (IAM): https://community.sap.com/topics/intelligent-asset-management

 

Blog Series

In the following blog series, we would like to provide deep-dive sessions for customers and consultants that are implementing SAP Digital Vehicle Hub.

Throughout the blog series we will create a vehicle in SAP Digital Vehicle Hub and explain the necessary steps. As an example we will us the Rinspeed MetroSnap model which is a concept-car designed as a modular vehicle system for innovative mobility solutions.

Example: Rinspeed MetroSnap in SAP DVH

The following topics are planned on a weekly basis until end of November:

• Introduction to SAP Digital Vehicle Hub (this blog)


• Data Model of SAP Digital Vehicle Hub


• Create and Update vehicles using APIs


• Integration of SAP Digital Vehicle Hub with SAP Vehicle Management System


• Integration of SAP Digital Vehicle Hub and SAP Analytics Cloud


• SAP Digital Vehicle Hub and SAP Cloud Platform Enterprise Messaging


• CX use cases and architecture

There will probably be more blog articles published on SAP Digital Vehicle Hub than those listed here. Therefore, please check regularly for updates and subscribe to this blog post!

Thank you.

 

A big thank you goes to our colleagues from SAP Digital Vehicle Hub, who are giving us great support for this blog series: Karin Rombach (Product Manager), Rochak Agarwal, (Product Owner), Adarsh Harindra Nath (Architect) and Sebastian Scharfenberger (Solution Manager)

[pardhreddyc]

Dear Reichel,

Thanks a lot for sharing the latest update on SAP DVH...

Oh my Gosh!...this is what exactly we need for logistic companies to handle fleet...I am just going back in times and remembering the efforts that took to develop Liasioning activities/Driver Management - Tagging the pay to their performance with time-in & time out at each plant/Operations/Fleet management & maintenance etc., on custom developments...which was really a tough job to cover every thing on custom code...I am very happy to see this development by SAP...when I was negotiating on licenses for one of my logistic provider with SAP licensing account head, I was sharing my thoughts and was asking about the same thing "Why SAP is not really looking in to logistic organizations where they have Liasioning/Driver Management tagging their performance to their monthly pay/Operations and Fleet maintenance etc., Now I feel my wish came true... Thanks a lot SAP... I wish this would help logistic companies to monitor their fleet life cycle....

--

Sincerely,

Pardha Reddy.C

[JohannesReichel]

Dear Pardha,

 

Thanks for your comment. SAP DVH could be the first step towards your wish. The first version of SAP DVH is really focusing on creating the repository of vehicle related information. Let's stay tuned what else will come in future releases of SAP DVH.

 

Best regards,

Johannes

[wwooding]

Johannes,

Looks very promising to automotive customers. Have you considered integrating connected data from the vehicle itself? Usage data, diagnostics data?

Thanks,

Wayne

[sscharfenberger]

Hi Wayne,

thank you for your question. I am the responsible solution manager within SAP for the Digital Vehicle Hub.

Yes, we will definitely integrate telemetry data into the solution. In one of our next releases we will normalize the telemetry data structure across OEM's and telemetry information provider to deliver a standardized set of indicators that can be integrated via SAP IoT. Timing TBD, but have a look into SAP Road Map Explorer as we will post the updates on roadmap there first.

Looking further into the future we will deliver standardized adaptors for OEMs and information provider and will build predefined use cases on top of the data.

So stay tuned!

[S0024369567]

Sound good. You mean that solutions like Geotab API Adapter will be available out of the box? Will be good to at least recognize ODBII and J1939 CAN data out of the box into SAP DVH.

https://www.sapappcenter.com/en/product/display-0000059356_live_v1/Geotab%20Telematics%20and%20Fleet...

[sscharfenberger]

Hi Patricio, that is one vendor we are looking at. I did not want to mention it explicitly in my previous post, because we are looking at a wide range to partner with. But you perfectly got the point!

[kiranshankar369]

Dear johannesreichel84 & sscharfenberger,

I have a query on assigning Indicators to vehicle. Referring to the blog on creating / updating vehicle using SAP DVH API and we could able create / update them. After which those vehicles are appearing in "View Vehicle" & "Modify Vehicle" Fiori app in SAP DVH. Now our aim is to assign Indicators to vehicle to replicate the digital twin of vehicle sensor sending various telemetric data (ex., Engine Temperature, Tire pressure etc.,).

Now we have created Indicators, assigned them to an indicator group. Created model template & assigned indicator group to this model template. Finally created model with model template.

Next, we are updating the vehicle with Model ID using API (which is the only way possible). As soon as we assign Model ID to vehicle using API, the Vehicle is being deleted from "View Vehicle" & "Modify Vehicle" Fiori apps and it is only appearing in "Equipment" fiori app. The Vehicle view (tabs such as Insurance, usage, Warranty, Insurance etc.,) is lost & we are getting only the equipment view for that vehicle, which should not have happened.

Can you please help us here to assign indicators to Vehicle without losing the Vehicle view?

Regards,

Kiran

[former_member585451]

Hello Kiran,

 

Please follow these steps to ensure that the vehicle is created with correct indicator details.

 

Create Indicators
Create Indicator group
Add indicators to Indicator Group
Create a new Model Template, like IND_MOD_TEMP.
Add, Indicator group into template IND_MOD_TEMP.
Using model templates, DVH_MT_MODEL_SPECIFICATION & IND_MOD_TEMP, create a Model  master
Using the Model master ID, create a vehicle.

With that you should be able to see the vehicle in view and modify apps and you would also be able to see the indicators in the list too.

 

I hope that helps.

Thanks and Regards,

Harsha