ASAM HMS

ASAM HMS (HEX File Management System) describes a standardized approach for the management of HEX files, which are necessary assets for today’s vehicle development. HEX Files can be everything ranging from coding files up to whole software containers for the vehicle ECUs, which are being used during the development of vehicles. 
 

Motivation

The number of ECUs in vehicles is steadily increasing and their interdependencies become more and more complex. Particularly ADAS and Autonomous Driving require ECUs that work increasingly cooperatively, interdependently, and are interconnected in complex networks.

One significant challenge in developing and test ECUs is to properly select the right HEX file to be flashed to the vehicle's ECU. To obtain correct test results, it is necessary that the correct HEX file which functionally fits to all other ECUs in the network is selected. Metadata could help to choose the correct file. However, the HEX file itself cannot contain meta information. As a result, it is currently difficult to systematically select the correct HEX files for the development and testing of networked and dependent ECUs. Therefore, a HEX file management system is needed to allocate the proper HEX files and their metadata. 
 

Content of the Standard

ASAM HMS defines an interface with the peripheral system that allows to obtain metadata from sources outside the HEX file and to correctly arrange this metadata in a HEX management database. This interface is responsible for linking information between internal and external peripheral systems and exchanging data.

Types of Metadata used to describe HEX files 

• Business Metadata (Product information, etc.) 
• Technical Metadata (E&E system information, etc.) 
• Process Metadata (Milestone information, etc.) 
• Local Metadata (Control information, test results, etc.) 
• Resource Metadata (Organization, person, role, etc.) 
• Governance Metadata (Metadata Standards, Guidelines, etc.) 

Typical systems connected to the interface

• PLM systems for product information
• Measurement and calibration tools for local metadata 
• Project and task management tools to process metadata 

By managing HEX files and their associated files (A2L files, etc.), source files (requirements documents, control specifications, changes requests, etc.), and their results (measurement data files, review documents, CDF data, etc.) in a defined structure, it is possible to record the activities of vehicle development regarding HEX Files. This defined structure and metadata makes HEX files searchable and easy to understand.

The interfaces of ASAM HMS are standardized with the Web API from RESTful and were designed based on the opensource Microsoft REST API Guidelines. Additionally, a YAML file format is provided which can be used for Swagger flameworks and will facilitate the implementation of the system. The data models of the interfaces are described by UML class diagrams. EAP files are also delivered for the UML.

Outlook

The goal of ASAMM HMS is to manage the development of ECUs and to mask HEX files with various metadata to "store" "search" and "comprehend" the files. There are many use cases for HEX file operation, and there are many connections with external systems such as test vehicle / ECU No / CAE / HILS. However, the scope of HMS Version 1.0.0 specifies the management of HEX files only.  For future version of ASAM HMS it is intended to include further use cases to “connect” “spread” and “share” HEX files.  
 

Hino Motors Ltd., Honda R&D Co. Ltd Automobile R&D Center, Toyota Motor Corporation, AVL LIST GMBH, DXC Technology Japan, ETAS GmbH, Vector Informatik GmbH