1

Services, Software and the Car:

Dealing with the next wave of complexity

Jean-François Lalande

Solution Director Intelligent Systems,

Altran Technologies, Sophia Antipolis

June 2016

Automotive industry challenges 2015-2025

2

Context : • The automotive world is facing a major shift in

market, technology complexity, and consumer expectations.

• The demand for Vehicle internet connectivity, Advanced Driving Assistance Systems (ADAS), Autonomous Driving is challenging existing vehicle software and electronics architectures.

• Automotive players must deal now with this increased technology complexity, safety and cyber-security implications, while always reducing costs and time to market. - 2015

3

Market trends: • the portion of cars equipped with ADAS

features is expected to grow from 8% in 2015 to 62% in 2025 cars

• the market size for new hardware and software for Autonomous Driving is $0.5billion in 2015 and will reach $60billion in 2030

• the timeframe for new vehicle launch is 3 to 4 years … whereas the cycle for new vehicle software is measured in months.

- 2015

- 2015

Towards a generalized ADAS market

4

How to build sophisticated behavioural strategiesbased on multiple ADAS intelligences, combined ?

• Connectivity

• Sensor fusion

• Centralized Processing

• Upgradability

• Learning capabilities

• Simulated/proven

Reuse ?

From specialized ADAS to self driving capabilities

5

Automation

Medical

Rail

Automotive

ADAS

Automated

driving

Electric

Hybrid

Infotainment

Increasing complexity

…more complex feature requests

Complex existing

system architectures…

Today’s patchwork approach of adding ECU’s

for each new feature is no longer sustainable

Expecting a “Tsunami” of software in electronics systems

1

2

3

Fast backbone network

Concentrated CPU Power

Hypervisor

Virtual

ECU

Virtual

ECU

Service Oriented Architecture for Software

SW service

SW service

The Feature Paradigm

• Lego-based feature model

• Model based system engineering

• ‘Bondage’ development at syntax & semantics

(API, and assumptions)

• COTS interactions with suppliers and ecosystem

• Increased certification against standards

but also against platform definition

• Extended inventory management

• Modelling collateral creation

• Security from specification to delivery

Which solutions to rationalize ?

7

Strenghtening the System Engineering

Software

Provisioning

Feature Platform

Configuration

Resource Map

Standard Lifecycle

End-to-end Security

Standard Error

Data Plane

Feature Interaction Plane

Arbitration

Modular Safety Cases

Declarative Policy

COTS-style Integration

Tooling

The need for a Vehicle level architecture

8

CoherenSE® - System Engineering

• A SW Middleware (runtime) for intelligent vehicles and machines

• Tooling (MBSE)• Application development• System topology definition

Aimed at providing coherence to the engineering of increasingly complex intelligent systems.

• Bringing SOA principles and methods of the consumer technology and IT industry to the embedded world :the Micro SOA concept

Altran approach: CoherenSE®, an embedded S.O.A

Hardware

OS

CoherenSE

SW service

SW service

SW service

Services

High speed Backbone

PlatformCAN

RTOS LINUX

Flexray

AUTOSAR RTOS LINUX

CAN

HW

Hardware

RTOS

Hardware

Hypervisor

Hardware

Hypervisor

CoherenSEInfrastructure

Example:New variant

CoherenSECoherenSECoherenSE CoherenSE CoherenSE CoherenSE

9

• Use of fewer computers combined with

powerful network will reduce wiring,

weight, bill of materials…

• Reduced costs of system integration and

variants management through

model based engineering

and higher level of re-use

• Improved time-to-market for software

features

• Higher reliability through built-in safety

and security

• Allow progressive deployment by dealing

with legacy sub-systems …

full compliance with automotive industry

standards including Autosar, ISO26262

CoherenSE – the benefits

By 2025, according to industry benchmarking, the

centralisation of ECUs, driven by a « centralized per-

domain » approach, will provide:

• Integration savings: from 15% to 25 %

• Cabling weight/length reduction up-to 35 %

• Product derivatives: savings on reuse

• Creation of new complex features

PRODUCT LIFECYCLE DEFINITION

Domain Controller Approach

System Architecture definition

ECU development

Integration at ECU level

System Integration

SoP

Service Definition

ECU & Service Dev

Integration at ECU level

System definition & Integration

SoP

Change Request at system level

Change Request at system level

TODAY

With CoherenSE

10

Sclability of the solution : the Domain approach

Domain

Controller

Centralized

supervision

2015

2020

2025

• Progressive deployment

• Target specific domains where impactful

• Open platform

• Cross domain and RTE

• Scalable (transport agnostic, multi-nodes..)

• Compliant AUTOSAR

• ISO-26262

• Model Based

The vehicle becomes a device

The vehicle connects devices

The vehicle controls devices

11

• The definition of ‘system’ in the new world will go well beyond ECU

• The definition of architecture will be ‘the machine which allows the instantiation

of systems and their development deployment and management across the lifecycle’

• Functional safety, security and vehicle lifecycle will be at the base of the system

and not encrusted on the top

• The key up skilling will be around software and system engineering

• The supply chain and procurement will be challenged by business model,

process and scope management

• Any solution will need to take into account AUTOSAR and GENIVi

CoherenSE - Game-changing

12