06-Iw14-Mbse Workshop-Application of Mbse at Jpl Through the Lifecycle-nichols-lin-final

7/23/2019 06-Iw14-Mbse Workshop-Application of Mbse at Jpl Through the Lifecycle-nichols-lin-final

1/53

Integrated Model-Centric

Engineering:

The Application of

MBSE at JPL Throughthe Life Cycle

Dave NicholsChi Lin

INCOSE International WorkshopMBSE Workshop

January 26, 2014


2/53

National Aeronautics and SpaceAdministration

Jet Propulsion Laboratory

California Institute of Technology

Mars

Solar system

Exoplanets

Astrophysics

Earth Science

Interplanetary

network

INCOSE MBSE Workshop January 26, 2014 Page 2


3/53




Strengthen the quality of formulation products by allowing exploration of amore comprehensive option spaceand more rapid analysis of

alternatives

Perform early validation of system designs

Give systems engineers time to do more engineering analysis and less

paper management

Significantly improve the quality of communications and understanding

among system and subsystem engineers

Achieve greater design reuse

Align with the expectations and work habits of the next generation of

engineering talent

this is the way new engineers are being trained and the way many of our earlycareer engineers want to work

But the bottom line is to

Reduce the number of product and mission defects in the face ofgrowing complexity

And increase productivity/reduce costs



4/53




JPL has been:

Developing a Model-Based Systems Engineering infrastructure consisting

of:

Foundational elements of ontologies and recurring modeling patterns

Tooling, consisting of interoperable solutions for a comprehensivemodeling approach and document generation approach

A community of practice nurtured via education and sharing experiences

and solutions

Applying MBSE to real project systems engineering problems across a widelandscape of project types, activities and lifecycle phases

Approximately 20 development tasks are applying MBSE at JPL across

the full lifecycle



5/53






6/53




!"#$!%&'# ) !%&'# ) !%&'# * !%&'# + !%&'# , !%&'# - !%&'# .

!"#$%&'

)'*+,%-

!"#$%&' .

/%$0 1%23

45%6,73

1%-,8#

9,#:6 1%-,8#

. 9:;

'%-' .

?:*#$0

@&- .

)*-':,#7%#'!6"-%"*'

Flight

System

Ground

System

& Ops

Payload

EuropaClipper

DARPA F6

SMAPFSW

Behavior, Electrical, V&VPilots for SMAP

EHMArch.

OPALS

LADWP Smart GridCybersecurity

InSightFlight

System &Science

Ref. Bus

SCaNNetwork

Project

System

MGSS OpsRev, MDAS/ISCA, MPS/SeqR (part of AMMOS)

Science Science Modeling Pilot

OrionEFT-1

OrionEFT-1

DawnGDS

SAR Science Merit Function

Ground System Engineering standard procedures and products

INCOSE MBSE Workshop January 26, 2014

Mars 2020

Page 6


7/53






8/53




Objective: Understand and define thebusiness case for fractionatedspacecraft

Parametric variation is relatively easy e.g. spacecraft bus mass and data link rate or time to

build a given module

For example, software like Phoenix Model Centerprovides for multi-disciplinary parametric variation

Limited architecture variation ability

For example: trade nuclear-powered flightsystems vs. Electric Propulsion FS

The MBSE approach was chosen to facilitateexploration of a greater set of architecturalvariants.

System model captures a rich set of rules &constraints that characterize a produceablearchitecture or set of architectural variants



9/53




Groundstation

Fuel(t)

Power(t)

Datai(t)

Mothership jDaughtership k

Daughtership l

Mothership i

Production lines

LV

SCOPE:

Daughterships Motherships

! Implementation

" Operations

!

"

Payloads

SC Components

F6 Tech PackageINCOSE MBSE Workshop January 26, 2014 Page 9


10/53




4:5:7%'%5

$"##%$A"#'%7&6:'%-


11/53




ASDA was designed to deal with a huge combinatorialspace problem (architectural variation, nominal and off-

nominal scenarios, and also design and economics)

SysML templates have been instrumental in

structuring analyses of architectural options

MBSE has facilitated a fundamentally new capabilitythat did not previously exist.



12/53






13/53




Chemistry:Do red surface depositscontain organics from below?

Energy: Can surface oxidants provideenergy for metabolism?

Chemistry Energy

Water

Habitability

Water:Are a global ocean andlakes hidden by Europas shell of

ice?

January 26, 2014INCOSE MBSE Workshop Page 13


14/53




Managing multiple architectural alternatives

Reliably determining whether design concepts close onkey technical resources

Ensuring correctness and consistency of multiple,disconnected engineering reports

Managing design changes before a full design exists



15/53




The Jupiter Europa Orbiter (JEO) mission concept was deemed tobe of extremely high science value, but un-affordable, by the NRC

Decadal Survey, which requested a de-scoped option

A one year study developed mission options (Orbiter, multiple flyby

[Clipper], and Lander) that retain high science value at significantly

reduced cost

Europa LanderEuropa Orbiter

Multiple-Flyby in Jupiter Orbit

(The Europa Clipper)



16/53




SysML ModelsSystem, Programmatic, etc.

/&'' /&"01231#456127'

/&'' /&"012)2&89'1' : ;#56"7

/&'' -#27?1'7 31#456127'

/-? @&A8#

,&7& /&"01231#456127'

,&7& /&"012)2&89'1' :;#56"7

!64#" -#27

?1'7 31#456127'

!-? @&A8#

*86BC ,1&0"&>31#456127'

*86BC ,1&0"&>

l y t mL v l c n ri l y t mL v l c n ri[ I nt rc t in]d [ ]

Power LoadProduct

FlybyFlight System : Flight System

NearSci

{0.1}

FarSci

{7.9}

Cruise

{8}

Telecom

{8}

Cruise

{0.1}

Eclipse

{6.5}

Cruise

{2}

TCM

{0.1}

Telecom

{8}

Cruise

{8}

TCM

{0.1}

Telecom

{8}

Cruise

FarSci

{7.9}

NearSci

{0.1}

[]

loop (3)

[]

loop (5)

[]

loop (2)

Allunits areinhours.

periapsis1:

altitude=660002:

periapsis5:

altitude=660003:

altitude=30004:

!64#" DB#2&"1631#456127'

!64#" /&"012)2&89'1'

0%

10%

20%

30%

40%

50%

60%

70%

80%

90%

100%

0

50

100

150

200

250

300

350

400

450

500

0 20 40 60 80 100 120 140 160 180 200 220 240 260 280 300 320

ae

Power(W)

Timestep(hours)

7 day PedalScenario

r u rc u t u t

+ r in

l t y

u

I n t ru n t

ttry

Pedal 2Pedal 1

EarthOccultation

EarthOccultation



17/53






18/53






19/53




D9'7#> /6E#8FB CD*,&7%#' ?,-'

B

1%7:#+ 2- E"+%

B )$%#:5," 1%F#,A"#-

D=A'9'7#> !64#" /6E#8'B 4"G%5 )"*5$% E"+%6-

B

H:I%5= E"+%6-

B ?":+ 45"F6% ),7*6:A"#

G27#0"&7#E !64#"H-2#"09 )2&89'1'

4"G%5

45"F6%


20/53






21/53






22/53




Communication of technical information within project and amongdisciplines is more efficient and accurate Not limited by foreseeable levels of increasing system complexity Easily integrated with existing discipline tools (MBSE is the keystonefor full Model Based

Engineering)

Re-use and evolution of alternate system design elements

3 full mission studies in the time it usually takes for 1 or 2

5 parallel configurations maintained

Improved control over the evolution of system designs

Consistent, rapid generation of technical margins and normalization of

risk assessment

Identical automated analyses are applied to all configurations and versions

Efficient generation of project documentation Ensuring consistency of documentation by drawing from same system model

Bridges from college education to project best practices Recent graduates are arriving with knowledge of and expectation of using MBSE methods

January 26, 2014

INCOSE MBSE Workshop Page 22


23/53





Page 23


24/53




/&"' IJIJ B%&88#20#F -2012##" &2 12%#"#2789

B6>58#K >1''162 &2E '9'7#> 417% 864#" B6'7&2E B%&20#' 76 'B1#2B# &2E "6L#" 5&986&E'

)88 4# %&L# 76 E6 1' "#5#&7 7%# >1"&B8# M&7

#L#2 864#" B6'7NO

January 26, 2014



25/53




Mars 2020 is not a typical Pre-Phase A project Effectively in Phase C+ for much of the H/W and S/W design

However, new mission, science objectives, and instruments

Highly cost-constrained

Leverage heritage via build-to-print philosophy

Need to modify the SE approach to address experiences on the MSLproject

Keep SE products updated with the ongoing design/developments/tests

Sharing information across a diverse team avoiding information silos

Improving the flow and traceability of design decisions and tests

Managing cross-cutting complexity and understanding of scope

Preempting the V&V armageddonat the end of the project 3 test beds running 7 days aweek

Improving parameter tracking and test correspondence(and visibility by others on this)

January 26, 2014



26/53




Physical Decomposition, LogicalDecomposition, and WBS

Org Chart

Resource Tracking (e.g., subsetof web-accessible MEL)

Assessment of Key & DrivingRequirements

System Block Diagramsand Interfaces

Linking information to corecomponents (Reference Designators)

System model provides integrated, consistent, and broadly-accessible design information and change assessment


Subset of patternsare extended frominstitutionally-and

Europa derivedpatterns

Page 26


27/53




The team is seeing value already, particularly in generating artifacts like theMEL, 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 itemin 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. inheritedfrom 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 webinterface) by the wider team (e.g., not having to track down the latest version of an Excelspreadsheet on an individuals computer).

This is also helping with increasing the visibility and understanding of the design by theteam.

The model will help us with knowledge transfer and continuity aspersonnel come in and out of the project over the coming years.


Page 27


28/53





Page 28


29/53




Pilot task: Generate V&V products such astest plans and procedures, using the SMAPantenna spin-up event as a reference case.


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 isincreasing

Desired Value: Explore a greater state

space in less time

Page 29


30/53





The high level test plan evolves with increasing

detail to become the test procedure

Page 30


31/53




Flight Hardware SimulatorsMOS


Page 31


32/53




TestPlan

SW Testbed

ProcedureScript

Autoscripting

Equipment

andconfiguration

Sequence of

Tests

Requirements

and test

objectives

linked to tests,

results, and

certification

Test Procedures

(Activity Diagrams)

Flat-Sat

Procedure

Flight

Vehicle

Procedure

Script

Autoscripting

Script

Autoscripting

System Model

Procedure

Add detail

Operational

Procedure

Supporting Tools and Infrastructure:

MagicDraw

DocWeb

IMCE

Autoscript tool

!


Page 32


33/53




Executable state charts

Fault injection testing

Create scenarios of Fault Protection behaviors

Model Checking Validate the design of fault protection system against domain specific

constraints

Example: During ascent, want receiver on, transmitter off

Translate SMAP FPlogical design into

SysML state charts

Explicitly modelbehavior as a network

of collaborating state

charts

Provide basis for

checking Fault

Protection Design vs.

Defined Failure Space

33

AIAA CASE August 14, 2013

MBSE Through The Product Life Cycle


34/53




Simulations derived directly from models enable us tovalidateoperations concepts and validate scenariosearly in the projectlifecycle, reducing the cost of later remediation

Validate the model itself

Validate the design

V&V products developed as views developed from an integratedmodel

provide greater inheritance from plans, to testbed procedures, through integrationprocedures, to operational procedures than existing products

are more intuitive to modify and execute than text based procedures

The procedure can become the script for configuring and running the unit under

test

All of the above save time and money during the development

cycle and reduce defects


Page 34


35/53





Page 35


36/53




AMMOS - Adaptable tools and services for operating NASAsrobotic missions

Motivation for Re-architecting Effort

Ground system and operations design has evolved over the past 30years

Need to refactor the system to address pain points, enhanceoperations personnel efficiency, and gain higher levels of re-use frommission to mission.

Motivation for applying MBSE

Promote architectural integrity

Provide single source of design reference

Provide rigorous, non-ambiguous description of system design

Requirements

Interfaces

Operations processes


Page 36


37/53




37

DocGen

Modeling the MOS

Reports,Documents, and

Project-specific

Gate Products

Model Repository

DocWeb

MagicDraw View Editor

Use Cases

System

Composition

Capabilities

Interfaces

Scenarios Processes

AIAA CASE August 14, 2013

MBSE Through The Product Life Cycle


38/53




For Operations, MBSE Facilitates:

The ability to accurately depict relationships between capabilities,processes, and the exchange of information that supports those

relationships.

The ability for operations personnel to better define the system

functionalitythey need

Understanding of how changes impact each part of the system

Exposure of the connection between engineering products (artifacts) and

system elements, many of which have been implicit.

January 26, 2014

INCOSE MBSE Workshop

Control System As-Is To-Be: A Timeline Based Control System

Page 38


39/53





Page 39


40/53




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 establishedwith a moderate investment, but many were skeptical about the valueand 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 engineeringleadership because of its demonstrated value.


Page 40


41/53




DegreeofMaturity

Key Capabilities:1.

MBSE methodology that supportssystems & software development

2. Modeling framework that enablesmodel/tools integration

3. Standard design views andviewpoints that support:

capturing technical designs in

formal models

performing reviews based on

formal models4.

Standard set of modeling toolsare established and supported

5. CM-controlled repositorypopulated with validated reusablemodels created from formulation

to implementation

Key Capabilities:1.

Cadre of trained MBSEmodelers

2.

Modeling infrastructure that

facilitates collaborativemodeling activities

3.

Initial modeling standard4. Modeling users guide

5.

Initial CM-controlled modelrepository framework w/

examples

Key Capabilities:1.

A fully operational modelingInfrastructure that enables

integration of system models withdomain discipline analytical

models, simulation/visualization

models to support: Design to cost

Reviews

Trade study!

2.

A matured model-baseddevelopment methodology with

training support

3. A fully CM controlled operational

model repositories thatcollaboratively managed by

projects, lines and Institution

Continuous

Practice

Phase 1: Building

Phase II: Maturing

Phase III: Integrating

FY09 FY16


Page 41


42/53




model libraries transforms analyses

profiles/plugins

ontologies

Tools(e.g., Magic Draw)

Guidance(e.g., SysML modelingGuide; MBSE based

life-cycle methodology)

repository

project models

Secure storage ofproject models and

reusable assets

Enabledevelopment of

SysML (and other)

project models

Establish commonconcepts for flight

project engineering

Establish consensus

rules for expressing

design Enable information

exchange

Customize SysML toolswith ontologies

Add user interface

helpers

Provide reusablemodel elements

Construct ortranslate models

from one form to

another Analyze models forwell-formedness,

completeness,

consistency, V&V

Explain properuse and benefits

of institutionalstandards and

infrastructure

January 26, 2014



43/53




External Partnership

(DVS, Lockheed Martin, GIT,

ESA/ESTEC, INCOSE/OMG)

SE-CAETool

Service

Education andTraining

Application onTarget Projects

ModelingInfrastructure

(standards, metrics,

reports)

Technical

Collaboration

Experience

Sharing

Guidance,

Engagement

UtilizePut into

Use

Feedback,

Validation

Provide

Tools


Page 43


44/53





Educate and train an initial cadre of modelers

Pair domain experts with early career hires

Build on grass-roots efforts

Work with strong advocates and advisors consisting ofinternational and national experts

Establish an institutionally-supported modeling environment

Define modeling standards, enable collaborative modeling effort, build areusable model repository; provide support to system model developers

Address usability issues with SysML and modeling tools

Identify and build applications Develop system models that have immediate benefits to projects needs

Put training into practice

Modelers partner with projects system engineers to get early buy in Use the initial application to validate the reusable modeling environment

Partner with industry, INCOSE, academia and OMG to learn,contribute and stay current

January 26, 2014

Page 44


45/53




SysML Models


UnderstandandexpressconceptsusingSysMLstandard

notation

EVERYONE

Collaborate and developmodels with help from core

team

MOST

SEs

CORETEAM

Appliesbe

stpractices

,

contribute

stoproduc

tion

models

January 26, 2014

Page 45


46/53




Phase I:Establishing

Initial capability

Phase II:

Performing MBSE

Phase III: full MBSE

ContactAwareness

Understanding

Initial Use

Adoption

1

2

3

4

5

6

7

COMMITMENTTOCHANGE

TIME

Mechanisms to supportsustaining the change

Mechanisms to supportwider rollout of change

Mechanisms to support measuredsuccess in piloting(i.e., initial operational environment )

Mechanisms to assure understanding(training, piloting)

Mechanisms to promote awareness(e.g., seminars, Modeling Early Adopter Group)

Adapted from Out from Dependency: Thriving as an Insurgent in a Sometimes Hostile Environment,

SuZ Garcia and Chuck Myers, SEPG Conference, 2001

Institutionalization

Internalization

We are here

January 26, 2014

MBSE Infusion Model and WhereWe Are



47/53




Line Orgs

Flight ProjectFlight Project

IMCE(Institution)

Tools, profiles,

design patterns,

model library,guidance

Reference Bus

Flight ProjectProjectssupplies supplies

feedback on needs

harvest and standardize

Modeling patterns Discipline ontologies

Tools

expertssupplies

Message

The line orgs will be

the primary contact

with projects



48/53




Carrot

Rewards and recognition

Stick

Integrate into standard practices

Evangelism

A persistent and consistent message frommanagement

Provides awareness and distinctions

The X-Team* approach

Go outside make external outreach a modus

operandi from day 1

* X-Teams: How To Build Teams that Lead, Innovate, and Succeed (Harvard Business School Press, 2007)


Page 48


49/53




Its the people

Its the support

Its the results

Infusion Success


Page 49


50/53




.Thank You!


Page 50


51/53




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 toimplementation

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 waslauded 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 onEHM.

Time-consuming project documents/reports become trivial to generate


Page 51


52/53




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 escapediscovery. 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


53/53




It Helps Manage Complexity

We are able to evaluate 100s-1000s of consistent, structured, and transparentdesign options and explicitly compare cost/benefit in a fraction of the time and

cost of conventional methods.

Different views address the concerns of different stakeholders

It Enables Reuse of Institutional Knowledge

MBSE enhances reuse of intellectual property (model elements embody hard-

earned technical expertise)

It Attracts Early Career Talent

MBSE forms a bridge from college education to JPL best practices

MBSE methods are beginning to be taught in universities to engineering students

Early adopters are dominated by the early career hires

INCOSE MBSE Workshop January 26 2014 Page 53