how to integrate mb(s)e and plm · © lehrstuhl für virtuelle produktentwicklung | 2015 mme folie:...

© Lehrstuhl für Virtuelle Produktentwicklung | 2015 MME Folie: 1

How to integrate MB(S)E and PLM

University of Kaiserslautern Institute for Virtual Product Engineering

Prof. Dr.-Ing. Martin Eigner


Why we need Model Based (Systems) Engineering (MBSE) and Digitalization


Industrie 4.0 / Industrial Internet

WLAN comunication car system [Image Source: Motorauthority.com]

Industrial Internet is the next generation of the Internet. It is a global system based from networked computers, sensors, actuators, machinery and equipment. Merging the physical world with the virtual world of the Internet and the software allows to develop and apply Internet-based business models and new services..

The term industry 4.0 was coined in Germany and is initially very strong production oriented. In English-speaking countries, the term Industrial Internet is common. It supplements the terms Internet of Things (IoT) and Internet of Services (IoS)


Glucose Sensors can reduce the morbidity due to Gla ucoma

* Industrial Internet Consortium (IIC), http://www.iiconsortium.org/.


Cybertronical System – Example: Autonomous Parking

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

Wegpunkte

KundenID : StringPosition : String

values

«block»ParkhausApp

Benutzerdaten

BMWIPhoneApp

Parkhaus Kaiserslautern

[Logical System Element] autonomes Parksystem autonomes Parksystemibd [ ]

Parkhaus Kaiserslautern : cybertroninisches Parkhau s

Benutzerdaten

Wegpunkte

Datenbank : Benutzerverwaltung

IPhoneApp : ParkhausApp

KundenkontoBenutzerdaten

BMW : Fahrzeugsteuerung

Wegpunkte

Logische Systemstruktur (SysML)

Partitionierung der Teilmodelle für die Stakeholder (SysML)

Autonomous Parking (Modelica)

Parkhaus Check-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

Wegpunkte

KundenID : StringPosition : String

values

«block»ParkhausApp

Benutzerdaten

BMWIPhoneApp

Parkhaus Kaiserslautern

[Logical System Element] autonomes Parksystem autonomes Parksystemibd [ ]

Parkhaus Kaiserslautern : cybertroninisches Parkhau s

Benutzerdaten

Wegpunkte

Datenbank : Benutzerverwaltung

IPhoneApp : ParkhausApp

KundenkontoBenutzerdaten

BMW : Fahrzeugsteuerung

Wegpunkte

Logische Systemstruktur (SysML)

„Slot#: 1453“

„Eigner BMW Z4“

„length of car < 5 m“

Selection Parking Slot (Modelica)

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

SW Entwicklung Automobilbau

akzeptieren

Guten Tag, Herr Eigner Fahrzeugdaten

ubermitteln? Automatisches

Einparken starten?

Customer Interaction (UML)


ParkhausApp ParkhausApp[Activity] act [ ]

KundenID übermitteln


KundenID übertragen

Standort ermitteln


Anmeldung am Parkhaus

Dauerparker Standardparkplatz

Kundenkonto?

Source: research project mecPro²


Product- und Process Complexity

Challenges for the Industry

Connectivity

Industrial Internet (IoT, IoS, Industrie 4.0)

Regulation /Compliance/ International Laws

Digitization

Personalisation

Globalisation

More Software and Electronic in Products

Datability

Interdisciplinarity

Simulation Visualisation

Increased Functionality in Products

Design for X

Demography

Consumer Behavior


Product- und Process Complexity

Challenges for the Industry Industrial Engineering is a Driver

Connectivity

Industrial Internet (IoT, IoS, Industrie 4.0)

Regulation /Compliance/ International Laws

Digitization

Individualisierung

Globalisation

More Software and Electronic in Products

Datability

Interdisciplinarity

Simulation Visualization

Increased Functionality in Products

Design for X

Demography

Consumer Behavior


Source: Discussions with Chris Paredis, Georgia Tec h

Engineering Models Must be Administrated by PLM?


syst

em in

tegr

atio

n

Mechanik

E/E

Software

interdisciplinary system

design

Modelling and model analysis

physical tests

virt

ual t

ests

hybrid tests

(e.g. HIL)

R

P

L

F

Mechanic

E/E

Software

Service

Modelling and specification

Modelling and first simulation

Discipline-specific modelling und simulation

The Engineering Prozess is Based on Digital Models

SysML

Simulink/Modelica

Matlab

A N T E N N A

B O X 2 P 2 C O N T R O LP A N E L

B O X 3

34

56

P 4

P O W E RP A N E L11

PW R 1P W R 1-P 1

2 8 V O L T S P O W E R56

P 5

G R O U N D

C O N T R O LU N IT

1234

B O X 4

P 5

V O LU M E C O N T R O L

S Q U E LC H

T O N E

C H A N N E L

B O X 5P 7

T R A N S M IT /R E C E IV E

P 6

A N T E N N AA N T E N N A

B O X 2 P 2B O X 2 P 2 C O N T R O LP A N E L

C O N T R O LP A N E L

B O X 3

34

56

34

56

P 4


PW R 1P W R 1-P 1

2 8 V O L T S P O W E R56

P 5

G R O U N D


PW R 1P W R 1-P 1

P O W E RP A N E L


PW R 1P W R 1-P 1

2 8 V O L T S P O W E R5656

P 5

G R O U N D

C O N T R O LU N IT

C O N T R O LU N IT

1234

1234

B O X 4

P 5


S Q U E LC H

T O N E

C H A N N E L


S Q U E LC H

T O N E

C H A N N E L

B O X 5P 7

T R A N S M IT /R E C E IV E

P 6

MCAD ECAD

CASE

CAE CAM/DF

CAT

PLMLM Backbone


A: Anforderung F: Funktion L: logisches Lösungselement P: physikalisches Element

Sys

tem

inte

grat

ion

Mechanik

E/E

Software

Interdisziplinäre

System

entwicklung

Modellbildung und -analyse

Dienst-leistung

Physische Tests

Virtuelle Tests

Eigenschaftsabsicherung

A

P

Hybride Tests

(z.B. HIL)

L

F

Mechanik

E/E

Software

PLM Backbone

Modellbildung und Spezifikation

Modellbildung und erste Simulation

Disziplinspezifische Modellbildung und Simulation

The Engineering Prozess is Based on Interdisciplina ry Processes


Unlocking Engineering Knowledge

Future Product & Systems Lifecycle Management

�Data is stored and maintained by the tool that is best suited for those data

�Other tools to gain access via linked data methods built on openstandards for data sharing, not proprietary interfaces and databases

�Provides an open environment where engineers have access to all relevant information needed, regardless of source

Today’s typical Product Lifecycle Management

Physical Assembly, Document &

Bill of Materials (BoM) Centric Approach to drive the Supply Chain

Mechanical Engineering

Software Engineering

Electrical Engineering

System Engineering along the lifecycle(s)

Integrated Electronic, Mechanical, and Software Engineering

� Modern systems and products now more software intensive, more complex delivery & management

� Relationship between engineering & software orgs is often loosely connected

� Current solutions typically require all lifecycle data to be physically located in PLM/PDM tools

� Requires data to be replicated across multiple tools or data stores, complex to manage

Source IBM


The Role of PLM and ALM In the product Lifecycle


Requirements BOM Requirements BOM System / Functional BOM System / Functional BOM Engineering BOM Engineering BOM Simulation/Testing BOM Simulation/Testing BOM Manufacturing BOM Manufacturing BOM Service BOM Service BOM

Production Systems (ERP/MES)


Product Lifecycle Management (PLM)


The Product Lifecycle Process

Vision: The integrated ECM Process?







What is the role of PLM/ALM? Solution 1: PLM is dominant

MBSE Authoring Systems


TDM 1 TDM 1 TDM2 TDM2 TDMn TDMn

CAD-x Authoring Systems


CAE/SIM Authoring Systems


OSLC, PLCS, AP242XML,…..







What is the role of PLM? Solution 2: PLM and ALM are co-existent (my favori te solution)



TDM1-n TDM1-n TDM1-n TDM1-n






Gate (slider depending when admin is necessary)

OSLC Based ALM Solutions

f.e. RELM


f.e. RELM







What is the role of PLM? Solution 3: ALM is dominant



TDM 1-n TDM 1-n TDM 1-n TDM 1-n







f.e. RELM


f.e. RELM


What are the Prerequisites for a Integration of PLM in the Early Design

Phase


What ´s about Standardization

[imag

e so

urce

: Loo

f, C

.: E

ntw

ickl

ung

eine

s H

ydro

kera

tom

s fü

r di

e LA

SIK

-Chi

rurg

ie, K

IMA

, Kai

sers

laut

ern/

Ger

man

y, P

hD

The

sis,

200

8.]

SE- Process

SE- Data Model for System and Simulation

Functional System and Simulationmodel

SE - Profile

Source: VPE Research Project mecPro² (T. Gilz)


The MBSE Process

B: Behavior R: Requirements F: Functions L: Logical Solution Elements P: Physical Elements

Mechanik

E/E

Software

Modeling and Analysis

Service

Physical Tests

Virtual Tests

R

P

Hybrid Tests

(e.g. HIL)

L

F

Mechanics

Electrics/Electronics

Software

Modeling and Specification

Modeling and First Simulation

Discipline-Specific Modeling and Simulation

Sys

tem

Inte

grat

ion

Interdisciplinary

System

s Engineering

Property Validation

Product Lifecycle Management Backbone

B

Operation/ Service

CASE Model

E-CAD Model

M-CAD Model

Discipline Specific Design

Requirements Engineering and Specification (Requirements, Functions and Behavior)

Logical System Design and multiphysical Simulation

Discipline Specific Detailling

Simulation Testing


Detailed MBSE Method

SFN



The MBSE Profile for SysML (Example) Absolute Prerequisite for the Standardization of Sy sML

Stereotypes for specific modeling concepts − System Requirements − System Functions − Logical System Elements

− Behavior Elements − Test Cases − Allocations (R-F, R-B, F-L, F-B, R-L, L-P)

System Modeling Language (SysML)

Defines validation rules

Customizes diagrams

− System Requirement Diagram (SRD) − System Definition Diagram (SDD) − Function Network Diagram (FND)

− Behavior Network Diagram (BND) − System Architecture Diagram (SAD)

+

+

+

[Wei

lkie

ns, T

im: S

yste

ms

engi

neer

ing

with

Sys

ML/

UM

L, M

odel

ing,

an

alys

is, d

esig

n. M

orga

n K

aufm

ann,

Bur

lingt

on, M

A/U

SA

, 200

8.]

MBSE Profile



� Map R, F, B, L to discipline specific parts and assemblies

Functional Breakdown

Requirements Breakdown

Logical System Breakdown

E-BOM structure

The MBSE Data Model for ALM and PLM

MBSE model edited in a SysML editor Simulated in Modelica, Simulink, VHDL, SystemC, Verilog,…. Edited in CAD-M, CAD-E and CASE Tools

(Physical System Elements)


CAD-Model

Simulation-Model

Extended PLM Model

System Model


Interdisciplinarity on CAD Level

E-BOM

Std Parts

Discloses & Declarations

Analysis

Requirements

CAD Model

Data Sheets

Viewables

Housing

Product

PCA

Schematic

Firmware Assy

Software

Component

ASICs

Mechanical Parts

Software

Battery

Purchased Assy

Approved Suppliers

Classified Component Attributes

AVL

AML / AVL

AML / AVL

PCB

Manual


Different Levels of Integration SysML to ALM/PLM


Alternatives for Publishing MBSE Models

� Managing SE artifacts: − Alternative A: Managing SE-project modules (files) − Alternative B: Managing model elements with structure − Alternative C: Managing model elements with structure, ports and topology

B: published SE-structure

C: published C1: SE-topology ports C2: SE-topology ports/relations (NR)

A: published SE-project modules

FP

D M

odel

P

LM

F L P


B and C1 are my favorite solutions


An ECM/CM process must be established for the SysML artifacts

in ALM/PLM


Managing MBSE Models Based on Adapted ECM

� FPD model is partial model inside a SysML model in a CASE tool and managed in Team Data Management (TDM) tool

� PLM backbone controls FPD model items after commit

FPD model under TDM control

FPD model under PLM control

1

4

4.1

5

6

8

9

A

4.2

A

10

7

branch

trunk

master B

2 3 1

prelimnary released

In c

hang

e

A

1

released

11 12 13

2 3

4.3

A

2 SysLMID 5456

ElementID 12356

Team Data Management

(TDM)

Product/Appication Lifecycle Management

(ALM/PLM)

Marc (System Architect)

Jule (System Engineer)

Philipp (System Engineer)

review



An easy Visualization must be established

for the affected Items in an ECM Process


Visualization with a Browser


System Requirements Functions Logic E-BOM


Graph Representation of Affected Items

� Graph representation of affected item based on MBSE Datamodel stored in PLM and MRP (SAP)

Requirements

Functions

Logical Elements

Items and Assemblies (E-BOM) )

Processes

Tools and ressources

Documents

Supplier


Summary


Some Thoughts: We need Standardization but…… .

� Persistent Administration in an extended PLM and/or ALM System for the following MBSE artefacts: − Requirements, Functions, Behavior and Logical Elements two levels hierarchy and network

� Version/revision control, ECM and Configuration Management needed for traceability (product reliability, ISO 9001, ISO 262606,….)

� Seamless Integration into existent Enterprise ALM/PLM solution � One single source of truth � Integration of MBSE in the enterprise ECM (Engineering Change Management) and CM (Configuration

Mgmt) � Version and Revision Management as basis for CM � Integration of the MBSE Authoring Systems via TDM into PLM and ALM

� 4 Level VDA concept � Security, Safety and common access rights � Visualization of the MBSE artifacts � Data Exchange in the early phase based on Standards (OSLC is not designed as a data exchange

standard) � Eventual co-existence between OSLC (integration) and PLCS (data exchange)


Thank You and Questions?