Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Engineering:
The Application of
MBSE at JPL Through
the Life Cycle
Dave Nichols
Chi Lin
INCOSE International Workshop
MBSE Workshop
January 26, 2014
Mars!
Solar system!
Exoplanets!
Astrophysics!
Earth Science!
Interplanetary
network!
INCOSE MBSE Workshop !
Page 2 !
Page 3 !
Page 4 !
Page 5 !
Project
System
EHM Arch.
Orion EFT-1
DARPA F6
Mars 2020
Flight
System
Europa
Clipper
Ref. Bus
Payload
InSight
Flight
System &
Science
Ground
System
& Ops
Network
Science
SMAP FSW
Orion EFT-1
SCaN
Science Modeling Pilot
SAR Science Merit Function
Pre-Phase
A
Phase A
Phase B
Phase C
Concept
Studies
Concept
&
Tech
Dev.
Prelim.
Design
Final
Design
&
Fab
Phase
D
Assembly,
test
&
Launch
Phase E
Phase F
Ops
&
Sustainment
Closeout
Page 6 !
Page 7 !
!
The MBSE approach was chosen to facilitate
exploration of a greater set of architectural
variants.!
System model captures a rich set of rules &
constraints that characterize a produceable
architecture or set of architectural variants!
Page 8 !
Mothership j
Daughtership k
Fuel(t)
Power(t)
Datai(t)
Daughtership l
Mothership i
SCOPE:
LV
Daughterships
Motherships
Production lines
Payloads
SC Components
F6 Tech Package
Groundstation!
January 26, 2014!
Implementation
Operations
Page 9 !
Parameter
connecAon
templates
Architectural
AlternaAve
Architectural
Analysis
via
SimulaAon
INCOSE MBSE Workshop !
Page 10 !
Page 11 !
Page 12 !
Water
Habitability
Chemistry
Energy
Page 13 !
Page 14 !
Europa Orbiter
January 26, 2014!
Europa Lander
Page 15 !
SysML Models
System, Programmatic, etc.
Block
Diagram
Viewpoints
Mass
Equipment
List
Viewpoints
Mass
Margin
Viewpoints
Power
Equipment
List
Viewpoints
Block Diagram
MEL Table
Mass
Margin
Analysis
&
Report
PEL Table
Power
Scenario
Viewpoints
Data
Margin
Viewpoints
Power
Margin
Analysis
Data
Margin
Analysis
&Report
Near Sci
{0.1}
loop (5)
[]
450
{8}
100%
Pedal 1
90%
Pedal 2
Telecom
{8}
400
80%
Cruise
{0.1}
350
70%
300
60%
Cruise
{2}
TCM
{0.1}
loop (2)
Cruise
Eclipse
{6.5}
[]
Far Sci
{7.9}
Telecom
{8}
Cruise
Power (W)
2: altitude = 66000
250
50%
200
40%
150
Earth
Occultation
Earth
Occultation
[]
Telecom
{8}
Cruise
{8}
4: altitude = 3000
5: periapsis
20%
50
10%
0%
0
20
40
60
80
100
120
140
160
180
200
220
240
260
280
300
320
Timestep (hours)
3: altitude = 66000
30%
100
TCM
{0.1}
loop (3)
Battery %SOC
1: periapsis
Far Sci
{7.9}
Near Sci
{0.1}
Page 16 !
FS + Margin
Flt-Sys CBE
Bus CBE
Instruments CBE
Battery %SOC
Page 17 !
Page 18 !
System
Model:
- Equipment
List
- Demand
vs
Mode
- Scenario
DeniAons
Power
Prole
Analysis
EUROPA STUDY 2012 REPORT
2: altitude = 66000
loop (5)
[]
Far Sci
{7.9}
Cruise
{8}
Telecom
{8}
Cruise
{0.1}
Eclipse
{6.5}
Cruise
{2}
TCM
{0.1}
loop (2)
[]
Telecom
{8}
Cruise
TCM
{0.1}
loop (3)
[]
Telecom
{8}
Cruise
ure C.2.5-2. The flyby concept permits a storeand-forward data-return strategy via at least
daily DSN passes between science operations,
and it also exploits battery use for short intervals with ample time for recharging between
science operations. In addition, because science observations and data collection occur at
different time, instruments
can be fixed
on the
INCOSE
MBSE
spacecraft body. During the downlink and recharging interval, the spacecraft is Earthpointed (except for trajectory correction maneuvers), with science playback, engineering
telemetry, and two-way navigation during
{8}
3: altitude = 66000
Far Sci
{7.9}
Near Sci
{0.1}
Page 19 !
Page 20 !
Page 21 !
Page 22 !
Page 23 !
Page 24 !
Preempting the V&V armageddon at the end of the project 3 test beds running 7 days a
week!
Improving parameter tracking and test correspondence (and visibility by others on this)!
!
Page 25 !
Org Chart
Physical Decomposition, Logical
Decomposition, and WBS
Subset of patterns
are extended from
institutionally-and
Europa derived
patterns
System model provides integrated, consistent, and broadly-accessible design information and change assessment
INCOSE MBSE Workshop !
Page 26 !
The team is seeing value already, particularly in generating artifacts like the
MEL, heritage tables, and interface block diagrams and making them
broadly accessible to the team!
!
Providing mutually-consistent products that are readily updated (e.g., a change to an item
in one place immediately propagates that update to all affected views/products). !
Going through this process is also helping to identify areas of inconsistencies in
separately generated and maintained historical documents, spreadsheets, etc. inherited
from MSL. Getting these into the model is helping us to reconcile these discrepancies.!
Products are being created that are quickly and broadly accessible (e.g., via web
interface) by the wider team (e.g., not having to track down the latest version of an Excel
spreadsheet on an individuals computer). !
This is also helping with increasing the visibility and understanding of the design by the
team.!
Page 27 !
Page 28 !
Motivation:!
The complexity (number of states) of
flight and ground systems is increasing
yet time for V&V is decreasing.!
The complexity of the test environment is
increasing!
Desired Value: Explore a greater state
space in less time!
Pilot task: Generate V&V products such as
test plans and procedures, using the SMAP
antenna spin-up event as a reference case.!
Page 29 !
Page 30 !
MOS
Flight Hardware
Simulators
Page 31 !
Test Procedures
(Activity Diagrams)
Sequence of
Tests
Equipment
and
configuration
System Model
Procedure
Test
Plan
Add detail
Autoscripting
SW Testbed
Procedure
Flat-Sat
Procedure
Requirements
and test
objectives
linked to tests,
results, and
certification
Flight
Vehicle
Procedure
Autoscripting
Autoscripting
Script
Script
Script
Operational
Procedure
January 26, 2014!
Page 32 !
Translate SMAP FP
logical design into
SysML state charts
Explicitly model
behavior as a network
of collaborating state
charts
Provide basis for
checking Fault
Protection Design vs.
Defined Failure Space
Model Checking!
Validate the design of fault protection system against domain specific
constraints!
Example: During ascent, want receiver on, transmitter off!
AIAA CASE August 14, 2013!
33!
All of the above save time and money during the development
cycle and reduce defects!
INCOSE MBSE Workshop !
Page 34 !
Page 35 !
robotic missions!
!
Motivation for Re-architecting Effort!
Ground system and operations design has evolved over the past 30
years!
Need to refactor the system to address pain points, enhance
operations personnel efficiency, and gain higher levels of re-use from
mission to mission.!
Page 36 !
MagicDraw
View Editor
Model Repository
DocGen
Use Cases
System
Composition
Capabilities
Interfaces
Scenarios
Processes
Reports,
Documents, and
Project-specific
Gate Products!
DocWeb
37!
Page 38 !
Page 39 !
Prior to FY09
MBSE started as a grass-roots effort
It was supported and championed by a few senior managers
FY09-FY12
The concept of MBSE was introduced to Executive Management
Integrated Model Centric Engineering (IMCE) initiative was established
with a moderate investment, but many were skeptical about the value
and readiness of MBSE for prime time.!
FY13 Present!
IMCE has gradually being accepted as an institutional strategic initiative!
Some wait and see sentiment still exists!
It is being sought out and used by previously skeptical engineering
leadership because of its demonstrated value.!
!
INCOSE MBSE Workshop !
Page 40 !
Degree of Maturity
Phase 1: Building!
Key Capabilities:
1. Cadre of trained MBSE
modelers
2. Modeling infrastructure that
facilitates collaborative
modeling activities
3. Initial modeling standard
4. Modeling users guide
5. Initial CM-controlled model
repository framework w/
examples
Key Capabilities:
1. MBSE methodology that supports
systems & software development
2. Modeling framework that enables
model/tools integration
3. Standard design views and
viewpoints that support:
capturing technical designs in
formal models
performing reviews based on
formal models
4. Standard set of modeling tools
are established and supported
5. CM-controlled repository
populated with validated reusable
models created from formulation
to implementation
FY09
INCOSE MBSE Workshop !
Key Capabilities:
1. A fully operational modeling
Infrastructure that enables
integration of system models with
domain discipline analytical
models, simulation/visualization
models to support:
Design to cost
Reviews
Trade study
2. A matured model-based
development methodology with
training support
Continuous
Practice
FY16
January 26, 2014!
Page 41 !
Enable
development of
SysML (and other)
project models
Guidance!
Tools!
(e.g., Magic Draw)!
Construct or
translate models
from one form to
another
Provide reusable
model elements
repository!
project models!
model libraries! transforms! analyses!
profiles/plugins!
ontologies!
Explain proper
use and benefits
of institutional
standards and
infrastructure
Secure storage of
project models and
reusable assets
Analyze models for
well-formedness,
completeness,
consistency, V&V
Establish common
concepts for flight
project engineering
Establish consensus
rules for expressing
design
Enable information
exchange
Page 42 !
External Partnership
SE-CAE
Tool
Service
Guidance,
Engagement
Experience
Sharing
Education and
Training
Modeling
Infrastructure
Application on
Target Projects
Feedback,
Validation
(standards, metrics,
reports)
Utilize
Put into
Use
Provide
Tools
Page 43 !
Page 44 !
EVERYONE
MOST
SEs
CORE
TEAM
Unders
ta
concep nd and expre
ts
ss
notatio using SysML
n
sta
ndard
SysML Models
Page 45 !
COMMITMENT TO CHANGE
Internalization
Institutionalization
6
We are here
Phase II:
Adoption
5
Performing MBSE
Initial Use
4
Phase I:
Establishing
Initial capability
Understanding
3
Awareness
2
Contact
1
7
Mechanisms to support
sustaining the change
Mechanisms to support
wider rollout of change
TIME
Adapted from Out from Dependency: Thriving as an Insurgent in a Sometimes Hostile Environment,
SuZ Garcia and Chuck Myers, SEPG Conference, 2001
INCOSE MBSE Workshop !
Page 46 !
IMCE
(Institution)
Tools, profiles,
design patterns,
model library,
guidance
Line Orgs
supplies
experts
supplies
Reference Bus
supplies
Flight Project
Flight Project
Flight Project
Projects
feedback on needs
harvest and standardize
Modeling patterns
Discipline ontologies
INCOSE
ToolsMBSE Workshop !
Message
The line orgs will be
the primary contact
with projects
January 26, 2014!
Page 47 !
!
Carrot!
Rewards and recognition!
!
Stick!
Integrate into standard practices!
!
Evangelism!
A persistent and consistent message from
management!
Provides awareness and distinctions!
* X-Teams: How To Build Teams that Lead, Innovate, and Succeed (Harvard Business School Press, 2007)
INCOSE MBSE Workshop !
Page 48 !
Infusion Success
Its the results
Its the support
Its the people
Page 49 !
!
!
!
!
!
.Thank You!!
Page 50 !
It Enhances Communication!
A single, authoritative source of information keeps team on same page!
Promotes accurate, efficient, consistent communication within a project!
More complete transmission of concepts & rationale from proposal to
implementation!
Based on my task and MBSE experience with the task My first move would be to
develop a system model.!
It Improves Productivity!
Europa team was able to study 3 distinct mission concepts for the resources
usually sufficient to study only 1 or 2, and the high quality of all 3 studies was
lauded by the Hubbard Review Board and by NASA HQ. !
Development of the initial system model took a fraction of the time it would
otherwise have, by reusing modeling patterns and analyses learned earlier on
EHM. !
Time-consuming project documents/reports become trivial to generate!
INCOSE MBSE Workshop !
Page 51 !
It Improves Quality!
Earlier detection of inconsistencies due to clearer semantics!
Example: 35 inconsistencies identified in Exploration Missions E-E Test
One thing that Ive found is that the process of modeling leads to escape
discovery. capturing the details leads to a greater understanding of the system
and makes errors or potential problem areas pop out. !
Promotes early/on-going requirements validation and design verification!
Standard documents are kept consistent and up-to-date!
It Supports Integration!
Provides consistent definition of system to integrate with discipline models,
including cost models and science margin models!
!
Page 52 !
Page 53 !