(Informative)

Since the first Motorwagen saw the light in 1886, many inventions have transformed automobiles making them easier to use and more responsive to human needs. A short list includes electric ignition starter, car radio, car key, power steering, cruise control, electric windows, intermittent windshield wipers, anti-lock braking system (ABS), digital dashboard displays, electromagnetic parking sensors, on-board diagnostics, mobile connection, satellite navigation, reversing camera, automatic parking, driver assistance features, etc.

Starting from the first experiments in 1939 , many efforts have further transformed automobiles from passive machine to machines with some “self-driving” capabilities. Recently, the Society of Automotive Engineers (SAE) in the USA has developed a Level-based classification of cars that have “self-driving” capabilities. Today, self-driving cars are not only technically possible, but to some extent commercially available. They promise to bring benefits that will positively affect industry, society, and the environment, such as:

  1. Replacing human error with a machine less prone to errors.
  2. Giving humans more time for rewarding activities, such as interpersonal communication.
  3. Optimising the use of vehicles and infrastructure.
  4. Reducing congestion and pollution.
  5. Supporting elderly and disabled people.

Therefore, the transformation of today’s “niche market” into tomorrow’s vibrant “mass market” is a high profile goal whose achievement will positively impacts society and individuals. The goal could be achieved just waiting for market forces to produce cars with progressively higher SAE Levels at more affordable prices. MPAI believes that a component-based standardisation process will accelerate the achievement of the goal.

Standardisation should be achieved as an open process implemented in four steps:

  1. Partition a car into subsystems and components.
  2. Define a Reference Model specifying functions and interfaces of subsystems and components.
  3. Develop Functional Requirements of the Data Types and Qualifiers exchanged by subsystems and components.
  4. Specify to efficiently process Data Types.

This approach offers various advantages:

  1. Research can:
    • Concentrate on different individual components.
    • Optimise components while keeping unchanged the Functional Requirements of interfaces.
  2. Industry can promote the definition of Data Formats when:
    • Research results are mature.
    • A component is needed.
  3. Component manufacturers can:
    • Develop optimised component solutions based on publicly available specifications.
    • Bring their standard-conforming components to market.
  4. Car manufacturers can:
    • Access an open global market of components.
    • Benefit from components with standard functions and interfaces.
    • Test components for conformance using standard procedures.
  5. Regulators can use better tools to oversee the development of the market.
  6. Users can rely on CAVs whose operation they can explain.

In this Introduction and in the following Chapters, the following conventions apply:

  1. Capitalised Terms are defined in Table 1 if they are specific to this Technical Specification and in Table 2 if they are shared with other MPAI Technical Specifications.
  2. Words beginning with a capital letter that have an equivalent word beginning with a small letter represent the “digital twin” of that word.
  3. Chapters and the Annexes are Normative unless they are labelled as Informative.