Checklist for end-to-end diagnostics
Servicexpert - Gesellschaft für Service-Informationssysteme mbH

Checklist for end-to-end diagnostics

Hanser OEM Supplier 2017

28.09. 2017

In the world of the networked vehicle, networking-based functions and access to cloud-based services are understood by the customer as part of the vehicle functionality. Disruptions in the condition of the network are perceived as vehicle problems. For all parties - whether a customer, OEM or service provider - an early detection within the cloud of whether a fault is caused by a vehicle problem or a vehicle-independent failure, is becoming increasingly important.

As networking progresses with new functionalities and services in the vehicle, the challenges of their controllability and diagnostics are also increasing. In order to understand the complexity associated therewith and to be able to derive requirements for future diagnostics of such an infrastructure, ServiceXpert Gesellschaft für Service-Informationssysteme mbH has prepared a checklist in which the aspects of end-to-end diagnostics have been highlighted and recorded.

End-to-end diagnostics

The term "end-to-end diagnostics" describes the ability and necessity to identify events such as malfunctions, abnormalities, or attacks in the "car-to-IT route", ie, between a vehicle at one end and a service provider in the cloud at the other end. In contrast to remote diagnostics, where a vehicle diagnosis is performed over the car-to-IT route, end-to-end diagnostics considers the diagnosis of the car-to-IT routes themselves.

The application scenarios for an end-to-end diagnostic capability range from a vehicle user who detects the fault of a service and uses an on-board diagnostic, through a support service that is required to remedy a fault in a car-to-IT function, to quality assurance, for which precise, evaluable data from the vehicles and all the components involved in a car-to-IT route are required.

All application scenarios lead to a fundamental question as to whether the causes of a car-to-IT problem lie in the vehicle, in a car-to-IT application, in the transmission route, with a service provider or with any number of the components involved.

As the vehicle of the future will be less frequently diagnosed in the workshop and relevant information will be in the cloud, additional challenges and questions arise. Network-supported functions and data flows are not only to be viewed from a functional point of view, but also in times of increasing attacks on automotive IT systems, aspects of security and safety also have to be considered.

Vehicle use itself is also changing. Through car sharing, we move away from a clear classification of owner and vehicle, to a large number of temporary users of a vehicle, resulting in further diagnostic requirements.

Complex requirements

A flood of questions and requirements quickly arise from the circumstances and challenges of end-to-end diagnostics and need to be taken into account. For our considerations, we have identified four levels, in which the aspects of end-to-end diagnostics must be brought together and considered. The following overview identifies the levels and essential aspects to be considered in the context of end-to-end diagnostics:

Diagnostic functionality

·         Diagnostic capability of all components

·         On-board diagnostic unit and architecture

·         Car-to-IT-enabled diagnostic tester

·         Diagnostic communication

·         Preventative diagnostics

Secure diagnostics

·         Secure communication (encryption, authentication, etc.)

·         Security engineering (architecture and design)

·         Secure diagnostic engineering & authoring

Diagnostics as a protective measure

·         Detection of attacks on the IT route

·         Embedded intrusion detection systems

·         Recognition domains

·         Cloud-based reference profiles

Organisation und administration

·         Service concept and process

·         Diagnostics authoring

·         Quality assurance

·         Security management

·         Requirements management

 

Other factors shape the framework conditions of a car-to-IT infrastructure. When considering the different domains and the components involved, their high complexity and overlapping dependencies quickly become apparent.

Checklist

In order to master this complexity, ServiceXpert, which has been dealing with technical systems diagnostics since the nineties and has pooled this know-how in its own DiC diagnosis centre, has developed a checklist that - originating from the various domains and looking at all the levels - records all aspects of end-to-end diagnostics. In this process, structuring and cascading were undertaken and cross-domain dependencies were identified and linked.

The solid technical expertise and many years of project experience form the basis of ServiceXpert's status as a trusted diagnostics partner for OEMs and suppliers. In addition to consulting services in engineering and diagnostics, the team introduces comprehensive process understanding and the necessary passion for E / E development in assigned tasks. The checklist developed against this background supports the evaluation of existing solutions, the establishment of minimum diagnostic scope as well as the derivation and planning of measures to increase diagnostic coverage.

Furthermore, the formulation of the checklist has shown that new standards for data exchange and logging are required for various parts and functions of the car-to-IT route.

ServiceXpert, an ESG-Group company, employs over 85 staff in Hamburg and Munich. ServiceXpert is a Europe-wide operating system and software house with a focused service portfolio for Lifecycle management of EE information for leading manufacturers of commercial vehicle and their supplier industry.

Copyright ServiceXpert Gesellschaft für Service-Informationssysteme mbH 2016. All rights reserved.