The Role of a Cloud-based Server in Service Workshops

August 1, 2024

Peter Subke

Figure 1: Typical setup of a workshop tester. (SOFTING)

Usage of cloud technology is essential for after-sales tester providers. It eases the rollout of new tester content — for example, diagnostic data of new vehicle types, updated repair manuals or ECU software for flash programming. Cloud technology also implements security services such as user authentication information.

Figure 1 shows a typical setup as it is implemented for the service of vehicles such as trucks and buses. The vehicle is parked (vehicle speed = zero) in the service workshop, and its E/E system is connected to the vehicle communication interface (VCI) via CAN or Ethernet. On the tester (TST) side, the TST-to-VCI connection is either USB or WiFi.

The TST is connected to a cloud-based server using the workshop’s WiFi infrastructure. The router that connects the workshop’s WiFi with the internet and thus the cloud server is not shown.

For the purpose of diagnostics, the TST sends diagnostic service requests to the vehicle, which answers with positive or negative diagnostic service responses — and action if required. ISO 14229 (Unified Diagnostic Services, UDS) contains the specification of 26 diagnostic services that can be parameterized by data identifier (DID) or sub-function bytes.

Examples for such diagnostic service requests include “Read Data By Identifier” with the data identifier for the vehicle identification number (VIN), Diagnostic Session Control Request with the sub-function byte 0x04 for the Safety System Diagnostic Session or the set of services to reprogram an ECU, namely the flash job.

Cloud infrastructure

Figure 2: Main use cases of a central data platform. (SOFTING)

To enable this procedure, a wide variety of information (Figure 2) must be made available in the cloud. There are two user groups that access information: at the OEM, the employees who create and roll out the tester, and the workshops that use the tester and report back test results.

Access options and available licenses are managed in User Management so that only permitted actions are executed. The “Tester” area is used to precisely control the rollout of the tester software, but also independently of repair documents and diagnostic tasks. “Vehicle” is used to control which software is programmed into control units for specific vehicles, while diagnostic reports also can be used to generate a vehicle history. There are also support options via remote access and a ticket system.

Figure 3: Aggregation of data from multiple sources. (SOFTING)

Such a data platform is a centralized system that processes (collects, stores and analyzes) data from multiple sources (Figure 3). This also means that once information has been created, it does not have to be entered again.

It provides a secure and scalable infrastructure for managing large volumes of data and allows organizations to gain insights and make informed decisions based on that data. A well-designed data platform can help to improve operational efficiency, reduce costs and drive innovation.

The server comes with an SQL database where all relevant data is being stored centrally as a “single point of truth.” Once the system has been set up, no other sources are required by its users.

Technology view

Besides its own SQL database, the server has immense capabilities in integrating and adapting to existing IT infrastructures, meaning that almost any system can be integrated as a data source by means of “connectors,” such as Java Database Connectivity (JDBC), Open Data Protocol (OData) and Connector API.

The server can integrate user management systems — e.g., Active Directory refers to existing user credentials but also document management systems.

For CRM (customer relationship management, e.g., Salesforce) or ERP (enterprise resource planning) systems, there are connectors that make the platform ready for immediate use. The JDBC connector makes it possible to integrate almost any database. An interface is created that is independent of the database manufacturer and allows both reading of and writing to the database. Supported database types are MS-SQL, Postgres and Maria-DB, but also IBM DB2 and all other databases for which a JDBC driver exists.

With the connector for OData, data can be integrated and processed quickly and easily via HTTPS/REST. The connector allows access to OData V2 and V4 compliant REST services. OData is the most widely used standard for this kind of communication and more comfortable to use than SOAP web services, for example, because the protocol is based on known http requests. For authentication, OAuth2 is being used.

In addition, customized systems can be integrated using the connector API. If a suitable connector is not available, it can be created quickly. Furthermore, the server comes with a Web API to extract and load the data for further processing and analysis. The Web API provides read and write access to the connected databases.

The server can be run as a Platform as a Service (PaaS) solution on platforms such as Microsoft Azure, AWS, or be installed on premises. This flexibility makes the solution highly scalable. New data sources can be connected at any time without having to redesign the platform.

In conclusion, the server not only serves as a backbone and IT integration layer; it also provides all necessary functions and tools to setup and maintain aftersales environments and processes. Mainly, it serves as a central connection node to all diagnostic testers located in the field, the content development tools and customer internal databases and management systems.

Peter Subke, business development manager, and Markus Steffelbauer, head of product management, Softing Automotive Electronics GmbH , wrote this article for Truck & Off-Highway Engineering.