Enabling Technologies for Leveraging Model Based System ... · company clarify its systems...
17
3DS.COM/SIMULIA © Dassault Systèmes | Confidential Information | 11/12/2014 | ref.: 3DS_Document_2014 1 Enabling Technologies for Leveraging Model Based System Engineering Bill Brothers
Transcript of Enabling Technologies for Leveraging Model Based System ... · company clarify its systems...
3DS
.CO
M/S
IMU
LIA
© D
assa
ult S
ystè
mes
| C
onfid
entia
l Inf
orm
atio
n | 1
1/12
/201
4 |
ref.:
3D
S_D
ocum
ent_
2014
1
Enabling Technologies for Leveraging
Model Based System Engineering
Bill Brothers
3DS
.CO
M/S
IMU
LIA
© D
assa
ult S
ystè
mes
| C
onfid
entia
l Inf
orm
atio
n | 1
1/12
/201
4 |
ref.:
3D
S_D
ocum
ent_
2014
2
Systems Engineering Systems engineering is a methodical, disciplined
approach for the design, realization, technical
management, operations, and retirement of a system.
A “system” is a construct or collection of different
elements that together produce results not obtainable
by the elements alone.
3DS
.CO
M/S
IMU
LIA
© D
assa
ult S
ystè
mes
| C
onfid
entia
l Inf
orm
atio
n | 1
1/12
/201
4 |
ref.:
3D
S_D
ocum
ent_
2014
3
Simple System Can you predict if a full water bottle will
fail when dropped onto the floor…
by examining only the cap?
Can you predict the product cost…
by inspecting only the bottle?
3DS
.CO
M/S
IMU
LIA
© D
assa
ult S
ystè
mes
| C
onfid
entia
l Inf
orm
atio
n | 1
1/12
/201
4 |
ref.:
3D
S_D
ocum
ent_
2014
4
Before jumping into Model Based System Engineering
(MBSE) and it’s myriad of acronyms and jargon, let’s
first consider:
What is a system model?
3DS
.CO
M/S
IMU
LIA
© D
assa
ult S
ystè
mes
| C
onfid
entia
l Inf
orm
atio
n | 1
1/12
/201
4 |
ref.:
3D
S_D
ocum
ent_
2014
5
System Model
What is a system model?
Element
Attribute 1
Attribute 2
Attribute 3
Attribute n…
Element
Attribute 1
Attribute 2
Attribute 3
Attribute n…
Element
Attribute 1
Attribute 2
Attribute 3
Attribute n…
Input Output
3DS
.CO
M/S
IMU
LIA
© D
assa
ult S
ystè
mes
| C
onfid
entia
l Inf
orm
atio
n | 1
1/12
/201
4 |
ref.:
3D
S_D
ocum
ent_
2014
7
Why have a system model? The goal of the system model is to understand the
relationship between all inputs and outputs, that
is, to understand the response space.
The system response space incorporates
engineering as well as business dimensions.
Cost
Stack Strength
Bottle
Volume
3DS
.CO
M/S
IMU
LIA
© D
assa
ult S
ystè
mes
| C
onfid
entia
l Inf
orm
atio
n | 1
1/12
/201
4 |
ref.:
3D
S_D
ocum
ent_
2014
8
Why a system model?
Understanding and
quantification of
uncertainty.
Understanding the response space is good, but it
is not good enough…
Cost
Stack Strength
Bottle
Volume
3DS
.CO
M/S
IMU
LIA
© D
assa
ult S
ystè
mes
| C
onfid
entia
l Inf
orm
atio
n | 1
1/12
/201
4 |
ref.:
3D
S_D
ocum
ent_
2014
9
Why a system model?
Understanding and
quantification of
uncertainty.
Knowing the limits
of model validity.
Calculation of
confidence.
Knowing the response space, the accuracy of
your prediction, and the limits of your model
validity are key to maximizing the value of your
system model.
SIMULIA provides Isight to enable you to
maximize the value of your system models.
Cost
Stack Strength
Bottle
Volume
3DS
.CO
M/S
IMU
LIA
© D
assa
ult S
ystè
mes
| C
onfid
entia
l Inf
orm
atio
n | 1
1/12
/201
4 |
ref.:
3D
S_D
ocum
ent_
2014
10
Now that you know what a system model is, and how
SIMULIA’s Abaqus and Isight products add value, let’s
add engineering to consider:
The application of System Engineering
3DS
.CO
M/S
IMU
LIA
© D
assa
ult S
ystè
mes
| C
onfid
entia
l Inf
orm
atio
n | 1
1/12
/201
4 |
ref.:
3D
S_D
ocum
ent_
2014
11
Systems engineering starts with Requirements • Requirements
• Provide focus ensuring the relevance of models
• Are used to design validation testing
• Guides the creation of model elements and system model assembly
• Verification and Validation
• Did you model it correctly? (Verification)
• Did you model the correct things? (Validation)
• Complete V&V provides trust in model based system engineering
• Requirements are dynamic
• SLM provides real time guidance on the a success of a design by incorporating requirements management with verification and validation of the systems model.
3DS
.CO
M/S
IMU
LIA
© D
assa
ult S
ystè
mes
| C
onfid
entia
l Inf
orm
atio
n | 1
1/12
/201
4 |
ref.:
3D
S_D
ocum
ent_
2014
12
Legacy System Engineering Process
Ad-Hoc Collaboration
Requirement Engineering
Customer
Needs
Functional
Delegation
Logical Design
Costing
Logical Design
Engineering Domain 1
Logical Design
Engineering Domain 2
Logical Design
Engineering Domain n
Iterative
Domain Integration
Physical
Simulation
Failed
Test
Verification & Validation
Integration (Tests)
Product “As
System”
Physical Design
Regulatory
Standards
Some domains are
not modeled and go
straight to test and
failure
Significant
information is
transmitted on an
ad-hoc basis, at
the water cooler,
over the cubical
walls, etc.
When success
depends on
knowing who to
go to, you have
an ad-hoc
process.
3DS
.CO
M/S
IMU
LIA
© D
assa
ult S
ystè
mes
| C
onfid
entia
l Inf
orm
atio
n | 1
1/12
/201
4 |
ref.:
3D
S_D
ocum
ent_
2014
13
When you remove
Requirement Engineering
Customer
Needs
Functional
Delegation
Logical Design
Costing
Logical Design
Engineering Domain 1
Logical Design
Engineering Domain 2
Logical Design
Engineering Domain n
Iterative
Domain Integration
Physical
Simulation
Failed
Test
Verification & Validation
Integration (Tests)
Product “As
System”
Physical Design
Regulatory
Standards
Ad-hoc
information
contains critical
IP, but is lost
when people
change roles or
leave the
company.
In an ad-hoc
engineering
environment,
Integration is
achieved by luck
and hope when
experts leave or
change roles.
3DS
.CO
M/S
IMU
LIA
© D
assa
ult S
ystè
mes
| C
onfid
entia
l Inf
orm
atio
n | 1
1/12
/201
4 |
ref.:
3D
S_D
ocum
ent_
2014
14
Requirements Engineering
Collaboration Environment
• Capture, Store, Access
• Configure
• Trace
• Reuse
• Accumulate Technology
3D EXPERIENCE Platform
System Engineering,
System Model Assembly -> System Realization
Functional Decomposition -> System Elaboration
Domain Integration
Recommended
Verification & Validation
Integration (Tests)
Virtual Product
Engineering Domain 1
(Model Element)
Engineering Domain 2
(Model Element)
Engineering Domain 3
(Model Element)
Engineering Domain n
(Model Element)
Customer
Needs
Regulatory
Standards
Derived
Requirements
Business
Needs
Product
correlation prior
to physical build
Simulation
Lifecycle
Management
(SLM) provides
the critical tools
necessary to
manage your
systems
engineering
process.
Technology is
retained,
accumulated
and made
reusable – even
when experts
change roles.
Integration is part
of a formal
systems
engineering
process.
3DS
.CO
M/S
IMU
LIA
© D
assa
ult S
ystè
mes
| C
onfid
entia
l Inf
orm
atio
n | 1
1/12
/201
4 |
ref.:
3D
S_D
ocum
ent_
2014
15
Example: SE of a Car • How do I approach a problem of this
magnitude? • Transportation
• Comfort
• Safety
• Efficiency
• Ability to comply with traffic system
• Exterior Lighting
• Interior Lighting
• Stopping Distance
• Acceleration
• Stability
• Noise
• Vibration
• Turning radius
• Operational feedback
• And much more…
3DS
.CO
M/S
IMU
LIA
© D
assa
ult S
ystè
mes
| C
onfid
entia
l Inf
orm
atio
n | 1
1/12
/201
4 |
ref.:
3D
S_D
ocum
ent_
2014
16
L Logical:
How does the product
behave?
• AC/Heating power requirements (function of exterior temp & sunlight)
• Battery discharge/recharge models
• Propulsion motor behaviors
• Mathematical cost models
• Control software psuedocode
• Increased accuracy
using multi domain
simulation
P Physical:
How is the product
built?
• Position motor above drive wheels
• Thickness of brackets
• Control software architecture
• AC/Heat passenger compartment air flow
• Physical definition of the
product
R Requirement:
What does the
customer want?
• Transportation around my town, state, and interstate highways
• Passenger comfort and safety
• A customer target price of $25,000
F Functional:
What does the
product do?
• Keep passenger compartment at comfortable temperature
• Provide power to various systems
• Protect occupant in various crash scenarios
• Illuminate roads at night
• Define relationships
between functions
The RFLP Approach
3DS
.CO
M/S
IMU
LIA
© D
assa
ult S
ystè
mes
| C
onfid
entia
l Inf
orm
atio
n | 1
1/12
/201
4 |
ref.:
3D
S_D
ocum
ent_
2014
18
Example: SE of a Car • Utilizing the RFLP approach makes even complex
systems tractable
• Start with Requirements
• Map out the Functions
• Search and reuse
• Decompose functions into behavior models
• Search and reuse
• Behaviors decompose to physical models
• Search and reuse
• Assemble model elements into system models
• Explore system models to understand system behavior space
3DS
.CO
M/S
IMU
LIA
© D
assa
ult S
ystè
mes
| C
onfid
entia
l Inf
orm
atio
n | 1
1/12
/201
4 |
ref.:
3D
S_D
ocum
ent_
2014
20
Model Based System Engineering
Maturity Assessment Consulting Service
• The MBSE Assessment is a comprehensive series of interviews and workshops
addressing the executive through subject matter expert user groups to determine
your company’s MBSE capabilities.
• The assessment provides a gap analysis between your company’s current and
future capabilities against an industrial benchmark. This is intended to help your
company clarify its systems engineering needs and provides a roadmap to assure
alignment of investments with enterprise business goals.
• The Assessment focuses on identifying capabilities in 10 MBSE domains to enable your company’s system engineering deployment.
• The execution of the data gathering phase is conducted in 3 steps:
• Executive Interviews to determine business goals as related to SE business needs and deployment strategy
• Subject matter expert workshops to capture current and needed levels of capability/maturity to illuminate gaps
• A detailed workshop capturing today’s behavior model usage and exploring what is needed to construct comprehensive systems
models
• Deliverable of the MBSE Assessment is an implementation roadmap with business justification for specific project initiatives.
