El ingeniero Pawel Chadzynski destaca el creciente desafío de la complejidad de los productos y la necesidad de un enfoque basado en modelos de ingeniería de sistemas (MBSE) para gestionar el diseño y la integración de sistemas complejos. MBSE permite una colaboración transversal entre disciplinas y proporciona herramientas para capturar el comportamiento de los sistemas desde las fases iniciales del diseño, mejorando así la trazabilidad y la gestión de cambios a lo largo del ciclo de vida del producto. Además, enfatiza la importancia de integrar MBSE con prácticas de gestión de configuración y trazabilidad para obtener los beneficios óptimos en el desarrollo de productos.

1. © 2016 Aras aras.com

2. MBSE and the Business of Engineering
Pawel Chadzynski
Sr. Director, Product Management
pchadzynski@aras.com
© 2016 Aras aras.com
MBSE and the Business of Engineering
Pawel Chadzynski

3. Product complexity is increasing
And creating system design challenges
Product
Complexity
Time
2D Mechanical
Electrical
Electronic
Software
Connected
Product as
a Service
3D Mechanical
Systems of
Systems
© 2016 Aras aras.com
Early
Products
Smart
Products
Smart
Connected
Products
Product as
a System

4. 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?
© 2016 Aras aras.com
• Are these cars products
with lots of parts?
• Or is it a system with
behavior working with
lots of other systems
with behaviors?

5. 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?
© 2016 Aras aras.com
• 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

6. CI=103
CI=105
CI=108
Evolution of system complexity
Mechanical
Mechatronic
Mech/Elec/Software/Network
© 2016 Aras aras.com
• Behavior and network connectivity
• Continuous replacement and evolution
• Traceability and re-evaluation
CI = NOC + SLOC
CI – Configuration Items
NOC – Network Operations Center
SLOC – Software Lines Of Code

7. V-Process supports Systems Engineering
© 2016 Aras aras.com
Sub-system
integration
Requirements
System
architecting
System
validation
System
integration
Sub-system
design
Component
test
Component
design
Needs System
Process, manufacture,
assembly
In theory

8. In reality
V-Process supports Systems Engineering
© 2016 Aras aras.com
Sub-system
integration
Requirements
System
architecting
System
validation
System
integration
Sub-system
design
Component
test
Component
design
Needs System
Process, manufacture,
assembly
In theory
Needs System
Requirements
System
architecting
System
validation
System
integration
Sub-system
integration
Sub-system
design
Process, manufacture,
assembly
Component
test
Component
design
Domain
handoff gaps

9. In reality
V-Process supports Systems Engineering
© 2016 Aras aras.com
Sub-system
integration
Requirements
System
architecting
System
validation
System
integration
Sub-system
design
Component
test
Component
design
Needs System
Process, manufacture,
assembly
In theory
Needs System
SEM MES
Requirements
System
architecting
System
validation
System
integration
Sub-system
integration
Sub-system
design
Process, manufacture,
assembly
Component
test
Component
design
Domain silos:
Mechanical
Electronic
Software

10. In reality
V-Process supports Systems Engineering
© 2016 Aras aras.com
Sub-system
integration
Requirements
System
architecting
System
validation
System
integration
Sub-system
design
Component
test
Component
design
Needs System
Process, manufacture,
assembly
In theory
Behavior appears
after integration!!!Needs System
SEM MES
Requirements
System
architecting
System
validation
System
integration
Sub-system
integration
Sub-system
design
Process, manufacture,
assembly
Component
test
Component
design

11. 1. Structure 2. Behavior
3. Requirements 4. Parametrics
From SE to MBSE
© 2016 Aras aras.com
 Specifications
 Interface
requirements
 System design
 Analysis and trade-off
 Test plans
Replacing documents with models,
behaviors, and interfaces

12. MBSE is not MBD/3D Mockup
© 2016 Aras aras.com
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

13. MBSE thrives on cross-discipline
collaboration
© 2016 Aras aras.com
“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.” - INCOSE
Mechanical
System
View

14. V-Process with MBSE
© 2016 Aras aras.com
 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
System
architecting
System
validation
System
integration
Sub-system
integration
Sub-system
design
Process, manufacture,
assembly
SEM MES
Component
test
Component
design
Needs System
Verification
Meets requirements
Validation
Meets the purpose
Behavior part of every
design step
Behavior known
before integration!!!

15. MBSE relies on multiple tools
© 2016 Aras aras.com
REQ model
SysML model
Simulation
AML/Software
MCAD
ECAD
Timing
Thermal
Stress
etc.
Physical test
Hybrid test
QPP
3D Mockup
ERP/MRP
E-M BOM
Change process
Documentation
etc.
Requirements
System
architecting
System
validation
System
integration
Sub-system
integration
Sub-system
design
Process, manufacture,
assembly
SEM MES
Component
test
Component
design
Needs System

16. Requirements
System
architecting
System
validation
System
integration
Sub-system
integration
Sub-system
design
Process, manufacture,
assembly
SEM MES
Component
test
Component
design
Needs System
MBSE implementation challenges
© 2016 Aras aras.com
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

17. Closing traceability gaps &
preventing them from occurring
© 2016 Aras aras.com
MBSE Digital Twin
Links to a
domain structure
Links to the
Systems Engineering
decomposition
Systems Engineering
decomposition
Domain
structure

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

19. MBSE/PLM use cases
The goal is a connected model and product
with full traceability
© 2016 Aras aras.com

20. MBSE/PLM use cases
The goal is a connected model and product
with full traceability
 Top/Down – System model first, then
detailed Product design
© 2016 Aras aras.com
1
1

21. MBSE/PLM use cases
The goal is a connected model and product
with full traceability
 Top/Down – System model first, then
detailed Product design
 Reverse modeling – System model from an
existing Product design
© 2016 Aras aras.com
1
2
1
2

22. MBSE/PLM use cases
The goal is a connected model and product
with full traceability
 Top/Down – System model first, then
detailed Product design
 Reverse modeling – System model from an
existing Product design
 Redesign – System model and Product
design exist, requirements changed
© 2016 Aras aras.com
1
1
2
2
3
3

23. 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
© 2016 Aras aras.com

24. Business of Engineering
 Product complexity continues to rise
© 2016 Aras aras.com

25. Business of Engineering
 Product complexity continues to rise
 MBSE provides powerful tools to synthesize the
design of complex systems
© 2016 Aras aras.com

26. 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
© 2016 Aras aras.com

27. 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
© 2016 Aras aras.com

28. 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
© 2016 Aras aras.com
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 integration
 XPLM/No Magic: MagicDraw
integration
 Aras/Altium: Bringing ECAD into
MBSE
© 2016 Aras aras.com

30. Acknowledgements
 Airbus
 IBM
 Dr. Eigner, TU Kaiserslautern
 Dr. Zhang, AVIC
 Altium
 No Magic
 ProSTEP
 INCOSE
 OMG
 OASIS
 XPLM
© 2016 Aras aras.com

31. © 2016 Aras aras.com