MBSE and the Business of Engineering

Transcription

1

2 MBSE and the Business of Engineering Pawel Chadzynski Sr. Director, Product Management

3 Product complexity is increasing And creating system challenges Product Complexity 2D Mechanical Early Products Electrical Smart Products 3D Mechanical Electronic Smart Connected Products Connected Software Product as a Service Product as a s of s Time

4 Product vs. Behavior Are these cars products with lots of parts? Or is it a system with behavior working with lots of other systems with behaviors? Is plane a product with lots of parts? Or is it a system with behavior working with lots of other systems with behavior?

5 Product vs. 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 Is plane a product with lots of parts? Or is it a system with behavior working with lots of other systems with behavior?

6 Evolution of system complexity Behavior and network connectivity Continuous replacement and evolution Traceability and re-evaluation Mechatronic Mech/Elec/Software/Network Mechanical CI=10 3 CI=10 5 CI = NOC + SLOC CI Configuration Items NOC Network Operations Center SLOC Software Lines Of Code CI=10 8

7 V-Process supports s Engineering Needs Requirements architecting validation test Process, manufacture, assembly In theory

8 V-Process supports s Engineering Needs Needs Requirements validation Requirements validation architecting architecting test Process, manufacture, assembly Domain handoff gaps test Process, manufacture, assembly In theory In reality

9 V-Process supports s Engineering Needs Needs Requirements validation Requirements validation architecting architecting test Process, manufacture, assembly In theory Domain silos: Mechanical Electronic Software In reality M E S S test E Process, manufacture, assembly M

10 V-Process supports s Engineering Needs Needs Behavior appears after!!! Requirements validation Requirements validation architecting architecting test Process, manufacture, assembly M E S S test E Process, manufacture, assembly M In theory In reality

11 From SE to MBSE 1. Structure 2. Behavior Specifications Interface requirements Analysis and trade-off Test plans Replacing documents with models, behaviors, and interfaces 3. Requirements 4. Parametrics

12 MBSE is not MBD/3D Mockup MBSE Model-Based s Engineering 1. Structure 2. Behavior MBD Model Based Drawing/Design 3. Requirements 4. Parametrics Both eliminate paper documents/drawings but only MBSE captures system behavior

13 MBSE thrives on cross-discipline collaboration Model-Based s Engineering (MBSE) is the formalized application of modeling to support system requirements,, analysis, verification and validation activities beginning in the conceptual phase and continuing throughout development and later life cycle phases. - INCOSE View Mechanical

14 V-Process with MBSE Moves creative work to the left Repeats in each domain Repeats cross-domains Requires new tools Behavior part of every step Needs Requirements architecting Behavior known before!!! M E S S Process, manufacture, assembly validation test E M Verification Meets requirements Validation Meets the purpose

15 MBSE relies on multiple tools Needs REQ model SysML model Simulation AML/Software MCAD ECAD Timing Thermal Stress etc. Requirements architecting M E S S Process, manufacture, assembly validation test E M Physical test Hybrid test QPP 3D Mockup ERP/MRP E-M BOM Change process Documentation etc.

16 MBSE implementation challenges Requirements continually evolving during process Managing MBSE model versions and revisions (change) Linking Simulation models to MBSE models for V&V Needs Requirements architecting M E S S Process, manufacture, assembly validation test E M It took Thales 10 years from first consideration to company-wide deployment of MBSE Linking Test results to MBSE models for V&V Linking discipline-specific Design models to MBSE models for V&V Managing model lifecycles, approval and change processes, access Source: 25 th Annual INCOSE International Symposium, 7/2015

17 MBSE Digital Twin Closing traceability gaps & preventing them from occurring s Engineering decomposition Links to the s Engineering decomposition Links to a domain structure Domain structure

18 MBSE Logical to Physical ALM Requirements ALM Structure Reference RL from SE ALM Create a model SE SE/MBSE Create SE structure Reference domains SE Requirements SE Logical PLM Product and MBSE MCAD Requirements ECAD Requirements MCAD Structure ECAD Structure Create structures & link to Logical Blocks Reference RL from SE Create structures & link to Logical Blocks Create ALM/CAD/MBSE MCAD Create Integrating MBSE models with PLM product structures Reference RL from SE Create structures & link to Logical Blocks ECAD Create

19 MBSE/PLM use cases The goal is a connected model and product with full traceability

20 MBSE/PLM use cases The goal is a connected model and product with full traceability 1 Top/Down model first, then detailed Product 1

21 MBSE/PLM use cases The goal is a connected model and product with full traceability 1 Top/Down model first, then detailed Product 2 Reverse modeling model from an existing Product 1 2

22 MBSE/PLM use cases The goal is a connected model and product with full traceability 1 Top/Down model first, then detailed Product 2 Reverse modeling model from an existing Product 3 Re model and Product exist, requirements changed 1 2 3

23 Benefits of MBSE/PLM Persistent administration in an extended PLM and/or ALM 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

24 Business of Engineering Product complexity continues to rise

25 Business of Engineering Product complexity continues to rise MBSE provides powerful tools to synthesize the of complex systems

26 Business of Engineering Product complexity continues to rise MBSE provides powerful tools to synthesize the of complex systems MBSE needs to be part of an overall traceability and configuration management philosophy

27 Business of Engineering Product complexity continues to rise MBSE provides powerful tools to synthesize the 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

28 Business of Engineering Product complexity continues to rise MBSE provides powerful tools to synthesize the 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 Aras architecture provides Future Proof Enterprise PLM with industry leading CM capability

29 Partnering with TU Kaiserslautern: Proof of Concept (MagicDraw) Airbus/IBM/Aras: OSLC-based ALM/PLM XPLM/No Magic: MagicDraw Aras/Altium: Bringing ECAD into MBSE

30 Acknowledgements Airbus IBM Dr. Eigner, TU Kaiserslautern Dr. Zhang, AVIC Altium No Magic ProSTEP INCOSE OMG OASIS XPLM

31