Systems Engineering for future mobility Dr. Siegmar … · Systems Engineering for future mobility...

Systems Engineering for future mobility

Dr. Siegmar Haasis

Daimler AG


1. Engineering Mercedes-Benz Cars

2. Motivation and challenges in automotive Systems Engineering

3. Strategic fields of action

4. Fields of Systems Engineering for future mobility

5. Summary and Outlook

Systems Engineering for future mobility / Dr. Siegmar Haasis / REConf / 02.03.2016 / Page 2

Daimler AG








Daimler AG

Digitization causes a massive change in the mobility market

Systems Engineering for future mobility / Dr. Siegmar Haasis / REConf / 02.03.2016 /

„Sharing Economy“ „Individual“

Autonomous

&

E-Mobility

Ownership

Ve

hic

le c

on

ce

pt

„Evolution“

„Revolution“ Self-driver

&

conventional

drive

Current

conventional

ownership and

usage model

Shared

autonomy

Page 4

Daimler AG

Global Engineering Network


Daimler AG








Daimler AG

Complexity, variant- and configuration management

Safety

technologies

Infotainment Parking

Autonomous

driving

Complexity

• Expanding product portfolio

• Growing process complexity

• Country-specific legislation and laws

• Collaboration with multiple suppliers

• Multi-site development and production networks

• Expanding requirements for the digital dev. Process

Trends

and

Business

Strategy

• Handling the massive increase of complexity

• Traceability of configured artifacts

• Handling hardware and software

configurations

• Reconfiguration of product during lifecycle

• Implement shorter software lifecycles

Challenges


Daimler AG

Demand

Connected Vehicle - Strategic Challenges


Pro

du

ct-

dri

ve

n

Pro

ce

ss-d

rive

n

Strategic Challenges

Autonomous & Electric Drive

Integration of Consumer IT

New Legal Requirements

Serviceability & Upgradability

Car Vulnerability and IT Security

Shorter Develop-ment Phases

Cooperations & Supplier Networks

Global Engineering Interdisciplinarity Standardization

§ IT-Security

+ -

10011101

11000110

Page 9

Daimler AG

Modeling the dependencies of linked vehicle systems

lighting system

air pressure check

braking system

…

infotainment system

head unit

thermal management

(E-)Powertrain

transmission

autonomous driving

assistance systems

chassis control system

steering system

Off-Board Services

Mechatronic & Embedded Systems

Software-Intensive Systems

status app for smartphone

car sharing

car-to-X

- connected systems

- traceability

[Log ical System Element] Batteriekühlsystem Batteriekühlsystemibd [ ]

«Log ical System Element»

Chiller : W ärmetauscher

allocatedFrom = a1

allocatedTo = Kältemittel verdampfen

Kondensator_Front_links : Kondensator

allocatedFrom = a3

allocatedTo = Kältemitteldampf

kondensieren

Klimakompressor : Kompressor

allocatedFrom = a2

allocatedTo = Kältemitteldampf

verdichten


Chillerv orlauf :

Expansionsv entil

allocatedFrom = a4

allocatedTo = Kältemittel

entspannen


: Kältekreislauf

NT_Kühler : Kühler

allocatedFrom = a5

allocatedTo = Wärme tauschen

Satisfies = Kühlleistung


: Kühlerkreislauf

air_out :

Umg ebung sluft

KW_out :

Kühlwasser

Kühlwasserpumpe : elektr.

W asserpumpe

allocatedTo = Verlustwärme

abtransportieren

Flussregler : 3/2-W ege-Ventil

allocatedTo = Volumenstrom

leiten

Kälte3 :

Kältemittel

KW_aus :

Kühlwasser

Luft_warm : Umg ebungsluft

Kälte1 :

Kältemittel

Kälte4 :

KältemittelKälte2 : Kältemittel

Luft_warm :

Umg ebung sluft

kalt :

Kühlwasser

KW_Kühlk_aus :

Kühlwasser

e2 : elektrische

Energ ie

KW_Kältek_aus :

Kühlwasser

Luft_Kältek_ein :

Umg ebung sluft

e1 : elektrische Energ ie

Luft_kühl :

Umg ebung sluft

KW_Kältek_ein :

Kühlwasser

Luft_Kühlk_ein :

Umg ebung sluft

e1 : elektrische Energ ie

Luft_kühl :

Umg ebung sluft

KW_ein : Kühlwasser

heiß :

Kühlwasser

KW_System_ein

: Kühlwasser

KW_Kühlk_ein :

Kühlwasser

KW_Ventil_ein :

Kühlwasser

visualize state of charge function

Battery charging systems


control temperature

authentication

interaction

Daimler AG

Interdisciplinary Collaboration

Challenges: Seamless process- and tool-chains focusing on three main

dimensions:

1. Degree of abstraction

from “ideation” to final “solutions”

2. Degree of decomposition

from the whole product to single parts and reverse

3. Degree of engineering discipline views

of SW, E/E, Mechanics and Services

within an

• growing and still heterogeneous IT-landscape

• multiple cross company collaboration


Daimler AG

Communication

drive

software developer

project management

chassis electronics

…

battery

@

@

@

fdsfsasdjlas

djsadjasdö

asdaösdma

sdaasdasd

fdsfsasdjlas

djsadjasdö

asdaösdma

sdaasdasd

fdsfsasdjla

sdjsadjasd

öasdaösd

masdaasd

asd

fdsfsasdjla

sdjsadjasd

öasdaösd

masdaasd

asd

fdsfsasdjlas

djsadjasdö

asdaösdma

sdaasdasd

fdsfsasdjlas

djsadjasdö

asdaösdma

sdaasdasd @

@

fdsfsasdjlas

djsadjasdö

asdaösdma

sdaasdasd

fdsfsasdjlas

djsadjasdö

asdaösdma

sdaasdasd

fdsfsasdjlas

djsadjasdö

asdaösdma

sdaasdasd

fdsfsasdjlas

djsadjasdö

asdaösdma

sdaasdasd

Challenge:

Increasing complexity brings a

communication which is mainly

document-based to its limits.


Daimler AG








Daimler AG

Strategic Fields of Action

Engineering IT Mercedes-Benz Cars


Product

Complexity

and Product

Variance

Business

Partner and

Customer

Dedication

Digital

Development

Process

2020

Module-oriented product documentation

and constraint management

E/E documentation and

vehicle-related software development

PDM system landscape 2020

Model-based specification of mechatronic

systems

Consistent digital modelling and validation

for body, chassis and powertrain

Consistent digital validation process

(Digital < Test Bench < Road)

4

2

3

Simplification of engineering processes,

methods and IT systems

End-to-End process integration,

e.g. photorealistic vehicle

Integration of international RD locations

Supporting development cooperations

(Renault/Nissan/Aston Martin)

Future collaboration with suppliers

Internation-

alization and

Collaboration

with Suppliers

1

Model-based specification of mechatronic

systems

Daimler AG

Systems

Engineering

Requirements Behavior

Architecture

Specification

E/E

Mechanics Services

Software

+ -

10011101

11000110

Model-Based Specification of mechatronic Systems


• Massive increase of complexity due to intensive linking of

functions

• Stricter documentation, requirements do increase complexity

• Text based requirement management already reached its limits

• DOORS reaches end of lifecycle

Trends and Business Strategy

• Handling the massive increase of complexity due to intensive linking of

functions and stricter documentation requirements

• Traditional specification shall evolve to systems engineering

specification

• Using model-based methods for specification and validation as a better

understanding, internationalizing and completeness

Fields of Action & Goals

Page 15

Daimler AG

Implementation of Model-Based Systems Engineering


Past Co

mp

lexi

ty

drawing board…

…to CAD

Today - System Engineering Enhancement @ Daimler

…to Model-Based Systems

Engineering

Systems

Engineering

Requirements Behavior

Architecture

Specification

E/E

Mechanics Services

Software

+ -

10011101

11000110

Text-based

requirements

engineering and

management…

t

Page 16

Daimler AG

Enabling Systems Engineering & Business Collaboration The Core of Engineering-IT Standards

• … Enable efficient process chains

• … Improve process quality

• … Raise flexibility

• … Simplify partner integration

• … Accelerate development processes

>> In the jungle of IT formats, Engineering-IT Standards … Core standards in the scope:

• Systems Modeling standard: SysML

• Exchange standards:

System Synthesis:

for textual requirements: ReqIF

for system models: XMI

System Analysis:

for multiphysics simulation models: FMI

• Integration standard: OSLC


Efficient usage of Engineering-IT standards will be a key to enable Systems Engineering &

Business Collaboration. Use the right set of standards -- and get out of the Jungle… Conclusion

Page 17

Daimler AG

CAD, PLM

MBSE

REM

Mechanics Electrics/Electronics

Software

Domains for innovations in future automotive development


Overall

vehicle

Car body

Car

features

Powertrain

Design Safety Chassis Electrics/

Electronics

Digital

Vehicle

e-Drive

Mobility

Business

Innovation

Component oriented

Service oriented

Page 18

CAD – Computer Aided Design

PLM – Product Lifecycle Management

REM – Requirements Management

MBSE – Model-Based Systems Engineering

t

Daimler AG








Daimler AG

Model-Based Systems Engineering V-Model


Cross section and overall processes,

Variant- and change management,

Workflows, Collaboration

Modeling

and

Simulation

Vehicle-Systems

Mechatronic-Systems

Components

Product-Service-Systems

E/E-Systems

Req.

&

Design

Validation

&

Integration

Requirements

& Design

Requirements

&

Design

Validation

&

Integration

MBSE Environment

Valid.

&

Integ.

Daimler AG

Daimler „V“ for Systems Engineering

We either standardize -- or we will be standardized | Get involved Conclusion

System Requirements

System Design&Simulation

E/E Requirements&Design E/E Integration

Production Electric/Electronic & Mechanical Components

System Integration

System Signoff Test Standard: Var. Standards

Software Implementation - Application Lifecycle Management

Mechanical Detailing Mechanical Component Test

FMI FMI

FMI


Daimler AG

Enforcing Engineering-IT Standardization

ISO JT Standard for 3D-Data as a Blueprint for ReqIF

Engineering-IT Standardization of ISO JT Standard (3D-Data) as a Blueprint for ReqIF.

Set up of new ReqIF Workflow Forum for Use Cases and user-driven Guidance. Conclusion

What we‘ve achieved… As a Blueprint for ReqIF…

Workflow

Forum

Implementor

Forum

Application

Benchmark


Daimler AG

Example 1 - Automatic Tailgate System

Tools/Software

System- &

Requirement

models

(Modeler)

Behavior

simulation

FEA

Simulation

System integration

& requirement verification


User Interface &

Customer demand Automatic tailgate: open an

close with key and smartphone

System requirements

Component

requirements

• Lock

• Seal

• SAM

• Motor

Cost

Calculation

CAD

Geometry

Visuali-

zation

…

Daimler AG

Example 2 - Headup-Display System


88:88

Impact of a part change due to technical

requirements because of interdependency

between the components

Challenges

• Establish interfaces to adjacent system

• Enable continuous parameter adjustments

• Assemble a warning function in case of conflicts

Field of view

Sitting

position

Seat rail

Angle of the

windshield

Page 24

Daimler AG

1. Identified requirements

confirmed by KeyUsers

2. Developed solutions

agreed with KeyUsers

(demonstrators)

3. Implemented solution in

the productive system in

collaboration with

KeyUsers

4. Rollout of the released

systems in collaboration

with the KeyUsers

Use Case based approach

for introduction of Model-Based Systems Engineering


Lab based on Scrum

Requirements

Engineering Modeling

Platform and Tools

Business Case

Method integration

Collaboration Configuration &

Variant Mgt.

Methods & Communication

Integration Process & IT

Rollout Preparation

Process Management

Use Cases for

MBSE

IT Architecture

MBSE UseCase - Knowledge Areas

Daimler AG

Examplary UseCases for MBSE


Administration of behavioral models in

the MBSE-environment

Ensure a consistent signal information

among E/E-architecture and text-based

requirements

Model-Based specification and

multiphysical simulation of a regulated

oil circuit

Integration of behavioral models in the

requirements of driver assistance

functions

Assist the workflows for the creation of

Model-Based specifications

Concept for lightweight systems

modeling in automotive powertrain

domain

Use Cases for

MBSE

Software Vendor:

• Commercial of the shelf

products

• Customization

Consulting:

• Several partners

Research:

• mecpro²

• CRYSTAL

Page 26

Daimler AG

Use Case Example: Ensure a consistent signal information

among E/E-architecture and text-based requirements


Function modeling System Requirements

ECU-SW

EE Architecture

Systems Engineering ECU Development

Fetch

Signals

2

Signal Change Control

3 Identify missing

interfaces

6 Model function

Functional behavior

Specifies

Requirements 1

4 Request new signals

5 Modify architecture

Challenges in this use case:

• Consistency of interfaces and

parameters between EE Architecture and

System requirements

• Workflow support for signal definition

& change

• Integration of signal data out of formal

models with (textual) specification

Potentials in this use case:

• Faster system specification & design

• Higher quality of implemented

functions

E/E-System Speaker Function

engineer

EE Architect

SW engineer

(ECU)

Diagnostics

engineer

System network

Component contributions

Busses

Daimler AG








Daimler AG

Summary and Outlook

• Model-Based Systems Engineering is one key pillar to handle the complexity in automotive development

and a step towards Digital transformation

• Integration of the Systems Engineering environment in the current IT-system landscape is essential

• The available tools are not sufficient enough to enable the future Model-Based Systems Engineering

• Engineering IT standards are foundation – we either standardize or we will be standardized

The evolution from text-based engineering to

MBSE is imperative to master the future

challenges in automotive development

… We have taken up the challenge ...


Daimler AG

Thank you for your attention

Dr. Siegmar Haasis

CIO Research & Development Mercedes-Benz Cars

Daimler AG

Date post:	11-Apr-2018
Category:	Documents
Upload:	dodien
View:	244 times
Download:	1 times

Systems Engineering for future mobility Dr. Siegmar … · Systems Engineering for future mobility...

Documents