MBSE and the Business of Engineering

© 2016 Aras aras.com

MBSE and the Business of Engineering

Pawel ChadzynskiSr. Director, Product Management

[email protected]


MBSE and the Business of Engineering

Pawel Chadzynski

mailto:[email protected]

Product complexity is increasingAnd creating system design challenges

Product Complexity

Time

2D Mechanical

Electrical

Electronic

Software

Connected

Product as a Service

3D Mechanical

Systems of Systems


Early Products

Smart Products

Smart Connected Products

Product asa System

Product vs. Behavior

Is plane a product with lots of parts?

Or is it a system with behavior working with lots of other systems with behavior?


• Are these cars products with lots of parts?

• Or is it a system with behavior working with lots of other systems with behaviors?

Product vs. Behavior

Is plane a product with lots of parts?

Or is it a system with behavior working with lots of other systems with behavior?


• Are these cars products with lots of parts?

• Or is it a system with behavior working with lots of other systems with behaviors?

Forces new organizational thinking

CI=103CI=105

CI=108

Evolution of system complexity

Mechanical

Mechatronic

Mech/Elec/Software/Network


• Behavior and network connectivity• Continuous replacement and evolution• Traceability and re-evaluation

CI = NOC + SLOCCI – Configuration ItemsNOC – Network Operations CenterSLOC – Software Lines Of Code

V-Process supports Systems Engineering


Sub-systemintegration

Requirements

Systemarchitecting

System validation

Systemintegration

Sub-systemdesign

Componenttest

Componentdesign

Needs System

Process, manufacture, assembly

In theory

In reality




Requirements

Systemarchitecting

System validation

Systemintegration

Sub-systemdesign

Componenttest

Componentdesign

Needs System


In theory

Needs System

Requirements

Systemarchitecting

System validation

Systemintegration


Sub-systemdesign


Componenttest

Componentdesign

Domain handoff gaps

In reality




Requirements

Systemarchitecting

System validation

Systemintegration

Sub-systemdesign

Componenttest

Componentdesign

Needs System


In theory

Needs System

SEM MES

Requirements

Systemarchitecting

System validation

Systemintegration


Sub-systemdesign


Componenttest

Componentdesign

Domain silos:MechanicalElectronicSoftware

In reality




Requirements

Systemarchitecting

System validation

Systemintegration

Sub-systemdesign

Componenttest

Componentdesign

Needs System


In theory

Behavior appears after integration!!!Needs System

SEM MES

Requirements

Systemarchitecting

System validation

Systemintegration


Sub-systemdesign


Componenttest

Componentdesign

1. Structure 2. Behavior

3. Requirements 4. Parametrics

From SE to MBSE


Specifications

Interface requirements

System design

Analysis and trade-off

Test plans

Replacing documents with models, behaviors, and interfaces

MBSE is not MBD/3D Mockup


Both eliminate paper documents/drawings but only

MBSE captures system behavior

MBD – Model Based Drawing/DesignMBSE – Model-Based Systems Engineering

1. Structure 2. Behavior

3. Requirements 4. Parametrics

MBSE thrives on cross-discipline collaboration


“Model-Based Systems Engineering

(MBSE) is the formalized application

of modeling to support system

requirements, design, analysis,

verification and validation activities

beginning in the conceptual design

phase and continuing throughout

development and later life cycle

phases.” - INCOSEMechanical

System View

V-Process with MBSE


Moves creative design work to the left

Repeats in each domain

Repeats cross-domains

Requires new tools

Verification

Meets requirements

Validation

Meets the purpose

Requirements

Systemarchitecting

System validation

Systemintegration


Sub-systemdesign


SEM MES

Componenttest

Componentdesign

Needs SystemVerification

Meets requirements

Validation

Meets the purpose

Behavior part of every design step

Behavior known before integration!!!

MBSE relies on multiple tools


REQ modelSysML model

SimulationAML/Software

MCADECAD

TimingThermal

Stressetc.

Physical testHybrid test

QPP3D MockupERP/MRPE-M BOM

Change processDocumentation

etc.

Requirements

Systemarchitecting

System validation

Systemintegration


Sub-systemdesign


SEM MES

Componenttest

Componentdesign

Needs System

Requirements

Systemarchitecting

System validation

Systemintegration


Sub-systemdesign


SEM MES

Componenttest

Componentdesign

Needs System

MBSE implementation challenges


Managing MBSE model versions and revisions

(change)Linking discipline-specific Design models to MBSE

models for V&VLinking Simulation models to MBSE models

for V&V

Linking Test results to MBSE models for V&V

Managing model lifecycles, approval and

change processes, access

Requirements continually evolving

during design process

It took Thales 10 years from first consideration to company-wide deployment of MBSE Source: 25th Annual INCOSE

International Symposium, 7/2015

Closing traceability gaps & preventing them from occurring


MBSE Digital Twin

Links to a domain structure

Links to theSystems Engineering

decompositionSystems Engineering

decomposition

Domain structure

ALMStructure

MBSE Logical to Physical

Create design

Create design

Create design

MCADStructure

ECADStructure

Reference RL from SE

Create structures & link to Logical

Blocks


Blocks


Blocks

SELogical

SE Requirements

Reference domains

Create SE structure



Create a model


SE/MBSE ALM/CAD/MBSE

ALM Requirements

MCAD Requirements

ECAD Requirements

PLM –Product and MBSE

Integrating MBSE models with PLM product structures

ALM

SEMCAD

ECAD

MBSE/PLM use cases

The goal is a connected model and product with full traceability


MBSE/PLM use cases


Top/Down – System model first, then detailed Product design


1

1

MBSE/PLM use cases



Reverse modeling – System model from an existing Product design


1

2

1

2

MBSE/PLM use cases



Reverse modeling – System model from an existing Product design

Redesign – System model and Product design exist, requirements changed


1

1

22

33

Benefits of MBSE/PLM integration

Persistent administration in an extended PLM and/or ALM System for MBSE artifacts

Integration of MBSE into the enterprise ECM (Engineering Change Management) and CM (Configuration Management) processes

Managed access control

Visualization of the MBSE artifacts

Data exchange in the early phase based on standards


Business of Engineering

Product complexity continues to rise




MBSE provides powerful tools to synthesize the design of complex systems





MBSE needs to be part of an overall traceability and configuration management philosophy






Strong, foundational CM throughout product lifecycle is a REQUIREMENT to realize MBSE benefits






Strong, foundational CM throughout product lifecycle is a REQUIREMENT to realize MBSE benefits


Aras architecture provides Future Proof Enterprise PLM

with industry leading CM capability

Partnering with

TU Kaiserslautern: Proof of Concept (MagicDraw)

Airbus/IBM/Aras: OSLC-based ALM/PLM integration

XPLM/No Magic: MagicDraw integration

Aras/Altium: Bringing ECAD into MBSE


Acknowledgements

Airbus

IBM

Dr. Eigner, TU Kaiserslautern

Dr. Zhang, AVIC

Altium

No Magic

ProSTEP

INCOSE

OMG

OASIS

XPLM



Technology

MBSE and the Business of Engineering