System of Systems Approach to Product Design

CIMdata PLM Road Map NA 2018

System of Systems Approach to Product Design

University of KaiserslauternInstitute of Virtual Product Engineering (VPE)Eigner Engineering Consult, Baden-Baden

Martin Eigner

Agenda

Systems of Systems Approach Drive the Digitalization and a New Design Methodology

Model Based Systems Engineering (MBSE) and the Central System Model (System Architecture)

Resilient Federated Lightweight Backbone above the Traditional Fragmented Legacy Systems

Some Examples from Industrial Research Projects

Needs for an Interdisciplinary Systems Architecture in the Early PDP

Our Understanding of a Seamless Integrated Engineering Process based on MBSE

© Lehrstuhl für Virtuelle Produktentwicklung (VPE) // 2017 Slide: 3

Summary: Benefits of MBSE

Industrial Megatrends 2020

IndustrialMegatrends

2020"

Globalization 2.0Personalization

Total Cost of Ownership

Change of the working

processesCrowd

Engineering

Digitale TransformationSystems of Systems

Engineering 4.0Industrial Internet / Industrie 4.0

New behavior of consumer

Sharing not Owning

CulturalDifferencesTime Zones

Digital LifeConnectivity

Demography

TechnologiesBroadband3D Printing

Big Data/Cloud

FinancingCrowd Funding

CryptocurrenciesMobile Money

© Lehrstuhl für Virtuelle Produktentwicklung (VPE) | 2015 Folie: 5

Description of digital building blocs

#1 Smarter Products

The real value of data arises from interpretation. To generate the

data companies develop intelligent products equipped with sensors.

Example: Machine Tool 4.0

#2 Smarter Production

The connected production of the future will optimize itself with

intelligent and connected machines and equipment. Modern

Companies take a leading role within the own production facilities.

#3 Smarter Processes

Future business processes are characterized that the generated

data can be used across the whole company. We see this as our

task to provide our customers the right information in real time and

we guarantee full traceability of our products.

#4 Smarter Analytics

Data are row materials of the digital world. Due to the combination

and correlation of data we are able to develop and produce better

and more specific solutions for our customers.

#5 Smarter Humans

Also in the digital world the human will play a major role, as an

employee and as user. We have to guarantee their education, we

have to help to support the cultural change and we should gain user

acceptance and therefore we have to provide an optimal user

interface.

Concept: Digital Agenda

Talents

Safety / Security

Big Data Management

#1 Smarter Products

#2 Smarter Production

#3 Smarter Processes

#4 Smarter Analytics

#5 SmarterHumans

Digital Business Scenarios & Solutions

Digital enabled Business Models

A Digital Agenda of a Typical German Company


Smart grid Systems of Systems (SoS) Example

Smart Products and Systems


© Lehrstuhl für Virtuelle Produktentwicklung (VPE) // 2015 Folie: 8

But the The Reality is:


But the The Reality is:

We have to change the traditional more discipline-oriented design methodologies, processes

and organization completely and develop new collaborative, integrated and

interdisciplinary methods and processes for innovative smart product and systems design

ÄModel Based Systems Engineering (MBSE)

Agenda









Extending the Product Lifecycle Upstream and Downstream = More Models and Complex Traceability


SysLM

DRAWING BOARD

2D CAD

3D MCAD/ECAD/CASE

MBSE

§ Highly specialized authoringsystems− System Modeling− Simulation− MCAD, ECAD, Software

§ Missing Interoperabilitybetween the tools− What are the standards?

§ A lot of redundant Information in the different models generated

§ Need: From PLM to SysLM(System Lifecycle Mgmt.)

PDM/PLM

Source: Michael Pfenning VPE

System Model = Meta Model for all discipline models


„System model is the glue“Elsevier Inc. 2012

§ The System Model exists in a formal language such as UML/SysML and describes the system of interest in its:− Structure− Behavior− Requirements− Parameters− Use Cases− Stakeholder− ……

Source: Michael Pfenning VPE

Definitions: System of Systems (SoS), MBSE and PLE


SoS brings together a set of systems for a task that none of the systems can accom-plish on its own. Each constituent system keeps its own management, goals, and re-sources while coordinating within the SoS and adapting to meet SoS goals ISO/IEC/IEEE 15288 Annex G

SoS

Formalized application of digital modeling and seamless integration of a product along the lifcycle to support system requirements, system architecture, design, analysis, verification and validation, process planning and service (Incose).

MBSE

Digital Modelderivate

Digital Twins

Physical Twins

Product line engineering is a multidisciplinary engineering practice that enables strategic reuse throughout the complete lifecycle of products by strategically plat-form, variants and derivates planning and sharing common components ISO/IEC26550

PLE

Configured Virtual and Real Products

The MBSE Process (mecPro²) Feasibility/Requirements

ProductPlanning

Product Development

ProcessPlanning Production Operation/

ServiceRecycling/Disposal

B: BehaviorR: RequirementsF: FunctionsL: Logical SolutionElementsP: Physical Elements

Mechanik

E/E

Software

Modeling and Analysis

Service

PhysicalTests

VirtualTests

R

P

HybridTests

(e.g. HIL)

L

F

MechanicsElectrics/Electronics

Software

Modeling andSpecification

Modeling andFirst Simulation

Discipline-SpecificModeling and Simulation

Syst

em

Inte

grat

ion

Interdisciplinary

Systems Engineering

Property Validation

System Lifecycle Management Backbone

B

Operation/Service

CASE Model

System Model

E-CAD Model M-CAD Model

Simulation Model

Discipline SpecificDesign

Requirements Engineering and Specification(Requirements, Functions and Behavior)

Logical System Design andmultiphysical Simulation

Discipline SpecificDetailling

SimulationTesting

Textual Requirements

Requirement Engineering

Digital ProcessPlanning

PLE SLE

New Business and Cooperation Models based on MBSE

Conceptual Design Management

System Architektur basierend auf SysML

Minimal SysML Profile für Starter

Requirements

Engineering

PLE incl.Variants

Security / Safety

Impact Analysis

Fault Tree

C-FMEA

PLM Backbone = MBSE Enabler

Conceptual Design Management (CDM)

based on a System Model /System ArchitectureWe do not want an isolated elite island

Test / Validation

Stakeholder

Usecases

Context

First Simulation

Conceptual Design Management

System Architecture base on SysMLMinimal SysML/Visio Profile for beginners

Requirements Engineering

PLE incl.Variants

Security / Safety

Impact AnalysisFault Tree

C-FMEA

PLM Backbone = MBSE Enabler

Test / Validation

Stakeholder

Usecases

Context

First Simulation

PLE(f.e. pure systems)

ImpactSafety/Security(f.e. EnCO)

EarlySimulation

Conceptual Design Management (CDM)based on a System Model /System Architecture

We do not want an isolated elite island

Agenda









Problem: Vertical integration is defined but no horizontal integration. With horizontal integration the customer benefit will be 20+30% higher!!!

Complexity of Mechatronic and Cybertronic Systems


Tariq Samad and Thomas Parisini

Problem: Vertical integration is defined but no horizontal integration. With horizontal integration the customer benefit will be 20+30% higher!!!

Complexity of Mechatronic and Cybertronic Systems


Tariq Samad and Thomas Parisini


Upper Level of System Architecture (OEM)

Transfer along the Supply Chainfor Electronic, Software and Embedded Systems



Source: VPE PhD, Julia Seeßle Engineering-IT Standardisierung im Systems Engineering der frühen Phase

AutomotiveSystem Architecture

Communication along the Supply ChainVia System Architecture Model

MBSE to Guarantee Traceability

Mechanics

…

Airplane

WingHydraulic

Electronic

SoftwarePCB

Landing Gear

………

Manuals

…..Purchased Assy

Sensor

AML / AVL

Electric

Landed

ReverseEngine

Aileron

BOM shows the physicalrelationships

Behavior Diagram shows thefunctional relationship

We need both of them!!!© Lehrstuhl für Virtuelle Produktentwicklung (VPE) // 2017 Slide: 23

The SW is responsibleto send a signal“Airplan landed”

based on 16t and torquedetected by sensors

Agenda









qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq

qqqqqqqq

Stakeholder Analyse Use cases Requirements Test cases

Architecture Internal structure

Instances

Design & computation model

Behaviour

Source: „Einsatz von Model-based Systems Engineering in der Automobil Industrie“, Dr. Markus Brandstätter und Carolin Eckl TdSE 2015

Concept for a System Architecture of a Car (ProSTEP)

MBSE to Describe Complex Cybertronic Systems

Vernetzung von Parkhaus, Smartphone und Fahrzeug (SysML)

Academic Version for Teaching OnlyCommercial Development is strictly Prohibited

autonomes Parksystem[Model] bdd Data[ ]

partsDatenbank : Benutzerverwaltung

«Logical System Element»autonomes Parksystem

parts : Einfahrtkontrolle : ParkplatzZuweisung : Einfahrtkontrolle : Fahrzeugleitsystem

«Logical System Element»cybertroninisches Parkhaus

Benutzerdaten Wegpunkteparts

: Antrieb : Lenkung : Bremssystem

«Logical System Element»Fahrzeugsteuerung

WegpunkteKundenID : StringPosition : String

values

«block»ParkhausApp

Benutzerdaten

BMWIPhoneAppParkhaus Kaiserslautern

[Logical System Element] autonomes Parksystemautonomes Parksystemibd [ ]

Parkhaus Kaiserslautern : cybertroninisches Parkhaus

Benutzerdaten

Wegpunkte

Datenbank : Benutzerverwaltung

IPhoneApp : ParkhausApp

KundenkontoBenutzerdaten

BMW : Fahrzeugsteuerung

Wegpunkte

Logische Systemstruktur (SysML)

Partitionierung der Teilmodellefür die Stakeholder (SysML)

Autonomous Parking (Modelica)ParkhausCheck-in-App

Vernetzung von Parkhaus, Smartphone und Fahrzeug (SysML)


autonomes Parksystem[Model] bdd Data[ ]

partsDatenbank : Benutzerverwaltung

«Logical System Element»autonomes Parksystem

parts : Einfahrtkontrolle : ParkplatzZuweisung : Einfahrtkontrolle : Fahrzeugleitsystem

«Logical System Element»cybertroninisches Parkhaus

Benutzerdaten Wegpunkteparts

: Antrieb : Lenkung : Bremssystem

«Logical System Element»Fahrzeugsteuerung

WegpunkteKundenID : StringPosition : String

values

«block»ParkhausApp

Benutzerdaten

BMWIPhoneAppParkhaus Kaiserslautern

[Logical System Element] autonomes Parksystemautonomes Parksystemibd [ ]

Parkhaus Kaiserslautern : cybertroninisches Parkhaus

Benutzerdaten

Wegpunkte

Datenbank : Benutzerverwaltung

IPhoneApp : ParkhausApp

KundenkontoBenutzerdaten

BMW : Fahrzeugsteuerung

Wegpunkte

Logische Systemstruktur (SysML)

„Slot#: 1453“

„EignerBMW Z4“

„length of car < 5 m“

Selection Parking Slot (Modelica)

“Waypoints {(12.4,12.5), …}“

SW Entwicklung Automobilbau

akzeptieren

Guten Tag, Herr EignerFahrzeugdatenubermitteln?

Ihr zugewiesener Parkplatz:1453

Automatisches Einparkenstarten?

Customer Interaction (UML)



ParkhausApp ParkhausApp[Activity] act [ ]

KundenID übermitteln


KundenID übertragen

Standort ermitteln


Anmeldung am Parkhaus

Dauerparker Standardparkplatz

Kundenkonto?

Source: research project mecPro²

Product Engineering

Service EngineeringU#1

Needs for MBSE to describe Product and Service Engineering (Garbage 4.0)

SysML

BPMN

PR = Product ReleasePT = Prototype

PR = ProductionN = Number (Prototype/Serial)

Feedback in Development with impact on the Digital Model

Digital Model and Digital Twin (InnoServPro)Vi

rtual

Wor

ldRe

al W

orld

Digi

tal M

odel

Di

gita

l Twi

nfo

r Pro

toty

pes,

Prod

uctio

nan

d Se

rvice

Prototype Twin

R1a R2a R2c ……………

Product Line A Product Line BRe

al P

rodu

ct

SNx1 a

SNy1 a

SNy1 a

1b 1c 1d

1b………………

………………

Enterprise IoT Plattform (EIP)

2b

PRPR = Product Release 150%

1b 1c 1d

2b 2c

PT Ny9bPTNz8c

SysL

M

?

Production Twin (as built) 100%

PRny1aPRnx1a

Service Twins (as maintained) < 100%

SNx1 a

Agenda









Vision: Digital Models along the Product LifecycleAu

thor

ing

Syste

ms

TDM

/PDM

and

PLM

/Sys

LM

Integration on Authoring System Level

Integration on TDM/ PDM/PLM Level

Digi

tal M

odel


thor

ing

Syste

ms

TDM

/PDM

and

PLM

/Sys

LM



Digi

tal M

odel

MBSE


thor

ing

Syste

ms

TDM

/PDM

and

PLM

/Sys

LM



Digi

tal M

odel

s

The Digital Thread (Traceability)

Engineering Processes (ERM, ECM, CM, Data Exchange, …)

The System Architecture Integration into an PLM/SysLMResearch Project Solution Lab VPE University of Kaiserslautern

CAMEO

Aras Innovator

Source: VPE Torsten Gilz, VPE 2014

Realization of a Graph- and Repository-based ECMResearch Project Solution Lab VPE University of Kaiserslautern

Graphical GUIwith embedded

WEB Services

Graph BasedVisualization

Link Repository (WEB Services, REST)


vis.js

Graph Based Presentation of ‘Affected Items’ for ECM

RequirementsFunctionsLogical ElementsItems and Assemblies (BOM)ProcessesTools and ressourcesDocumentsSupplier


SysLM Backbone Federated Backbone based on Data Linkage

Service

MCAD TDM

Digital FactorySystem Architectur Simulation/TestElectrik/ElektronicMechanicSoftwareRequirements

MRP/ERP

Team DataManagement

AuthoringSysteme

MRP/ERPRM Sy

sML,

…

CASE

MCA

D 1 Di

Fa

MCA

D 2

ECAD

2

SIM

2

ECAD TDM

Sim PDM

ECAD

1

SIM

2

System Lifecycle Management (SysLM)Engineering

Backbone

Serv

ice

Enterprise ServicePlatform

SIM

1MES

Authoring Systems via TDM integrated TDM SystemsAuthoring Systems direct integriert

OSLC / REST Technology API/Web Servic based Integration via Data Link or Exchange


All r

ight

s res

erve

d to

Sch

aeffl

erAG

, in

part

icula

r in

case

of g

rant

of a

n IP

righ

t.

Strategic Target Architecture (With markers) Architecture PLM Cockpit

Aut

horin

g-Sy

stem

sTD

M/P

DM

-Sy

stem

sPL

M

Bac

kbon

e

IoT

Ente

rpris

ePl

attfo

rm

ProjectManagement

SystemsEngineering

SoftwareEngineering

Virt. & Phys.Validation

MechanicalEngineering

IOT

Con

tent

Serv

er

E/EEngineering

Industrial Engineering

Sales/Service

IBM

Strategically not supported Should be supported as global solution

Requirement & Test Engineer.

Business Logic & Integration

Graphical User Interface (role based Apps)Service Request

ManagementReporting

Engi

neer

ing

Coc

kpit

(AR

AS)

Search and Browse

Dig

ital P

latfo

rm (I

BM

)

EPLA

N

Altiu

m

Men

tor

Cre

oD

elm

iaPr

oces

s En

g. V

6Pl

an

Sim

ulat

ion

Ente

rpris

e Ar

chite

ct

Inte

grity

Mod

eler

Rha

psod

y

Inte

grity

Life

cycl

e M

ger

Doo

rs +

RQ

M +

C

hang

eR

eqM

anPlan

isw

are

PSR

(P

roje

ct S

tatu

s R

epor

ting)

MS

Proj

ect

Inte

grity

Life

cycl

e M

ger

Syne

rgy

and

Cha

nge

Suite

Oth

ers

Sale

sfor

ce /

Med

ias

Maß

blat

t

SVN

SAP

Cre

oC

onfig

urat

or

WT

TLD

B, o

ther

s

SAP

…

Matlab, Bearinx, Famos,

Abaqus…H

yper

tes

tER

S

Enov

ia

SAP?

Workflow EngineApplication Integration

(Webservice, REST, OSLC, …)Federated Repository

(Data Backbone)

Change Management

ConfigurationManagement

B

Source: Schaeffler, Fabrice Mogo Nem

All r

ight

s res

erve

d to

Sch

aeffl

erAG

, in

part

icul

ar in

cas

e of

gra

nt o

f an

IP ri

ght.

The Engineering Cockpit – architecture & design principles

PEP

EngineeringCockpit

Project

Product

PEP GW/Evidences

Product

Configuration Management

Project Request

Drawing

Mechanical Eng. ERP

Component

PDM

Product

Product

Project

Documents

Project

Product

Schedule

Project

Documents

Collaboration

Project Management RE Other

Referenced to

40

SE SW E/E

Milestone Milestone Milestone

Model

…

Change Management

Service Request Mgmt.

ManagementReporting

ConfigurationManagement

Production BoM

etc.

Project Order

Project Closure

CRS

PRS

DRS

Source: Schaeffler, Dirk Spindler

Agenda









No specification errors

Goal

Agile implementable

Implementation errors

are reduced

Collaboration in the company

Collaboration over development sectionsand supplier

Describing models and optional executable models

Provision of an MBSE platform for the Functional Prototype (FPT)= the first Digital Twin

Qualification and support for the RD developers

Fully integrate the functional dependencies of all systems

Conflict-free developed First Prototype

MBSEVision

The Benefits of MBSE

MBSE in the Automotive Industry - Potentials and Benefits | J. Rambo/Huwig | ProSTEP IViP 2017

Based on: Implementing Model Based Systems Engineering – Human Centricity through Agility J. Epple, E. Weißschuh, F. Arbes, Daimler AG & S. Blankenburg, M. Keckeisen, TWT GmbH

Interdisciplinarity is

guaranteed

Traceability among all disciplines,

along the full Product Lifecycle and

based on physical and logical references

Model Integration is

supported

Professor Dr.-Ing. Martin Eigner

Thank You! TU Kaiserslautern Lehrstuhl für Virtuelle Produktentwicklung (VPE)

Postfach 304967653 KaiserslauternGottlieb-Daimler Straße 4467663 Kaiserslautern

Tel. +49 (0) 631 - 205 3873Fax: + 49 (0) 631 - 205 3872

[email protected] http://vpe.mv.uni-kl.de

Höllhäuserweg 38 a // 76534 Baden-BadenMobil: +49 172 152 4406http://[email protected]