digital mission engineering engineering · digital mission engineering engineering model based...

National Aeronautics and Space Administration

www.nasa.gov

ModelBasedSystemsEngineeringDigital Mission Engineering

Model Based Systems Engineering: A stepping stone on the path to Digital Engineering

Digital Mission Engineering 2019 ForumNovember 19, 2019

David RichardsonNASA – Goddard Space Flight CenterInstrument and Payload Systems Engineering

Model Based Systems EngineeringModel Based Systems Engineering Strategy

2

NEEDS

PHYSICAL SYSTEMS

SOLUTIONS

AS-OFFERED

AS-NEEDED

AS-SPECIFIED

AS-DESIGNED

AS-PLANNED AS-BUILT

AS-TESTED

AS-CERTIFIED

AS-DELIVERED

AS-SUPPORTED

DESIGN

DELIVER

Y

Copyright © 2018 Boeing. All rights reserved.

Q: Do we need to improve [Systems] Engineering?

A: An evolving environment calls for the digital transformation of SE.• Increasing technical complexity, coupled

with • Enhanced partnership and collaboration

Impact: At an ever increasing rate…More decisionsEarlier decisionsMore people & organizations involved in the decisions

Default reality: A failure to evolve Systems Engineering Capability, aligned with the environment of increased complexity will erode effectiveness at performing future missions


3

*What is Digital Mission Engineering?

1. Scoping Digital Transformation – Internal NASA Discussion, March 20182. www.m-w.com: Engineering definition (Modified by 1)3. DE applied to the NASA Mission Statement

1DT: The transformation of an organization’s activities, processes, competencies, capabilities, and products to fully leverage evolving digital technologies

2DE: The design and manufacture of complex products characterized by fully leveraging evolving digital technologies

3DME: The design and manufacture of complex products characterized by fully leveraging evolving digital technologies, to “Drive advances in science, technology, aeronautics, and space exploration to enhance knowledge, education, innovation, economic vitality and stewardship of Earth”

http://www.m-w.com/


4

What are we doing?

Science Concept

Mission Concept of Operations

System Level Specification

System Design

Realization Plan

Realized:• Parts• Subsystems• Systems

Certified System

𝐴 = #𝑓 𝐸𝑥𝑐𝑒𝑙,𝑊𝑜𝑟𝑑, 𝑃𝑜𝑤𝑒𝑟 𝑃𝑜𝑖𝑛𝑡 𝑑𝐸𝑛𝑔𝑖𝑛𝑒𝑒𝑟𝑖𝑛𝑔What does that

look like (system)?

GSFC is about robotic space missions for the purposes of science, exploration and technology development


5

NEEDS

PHYSICAL SYSTEMS

SOLUTIONS

AS-OFFERED

AS-NEEDED

AS-SPECIFIED

AS-DESIGNED

AS-PLANNED AS-BUILT

AS-TESTED

AS-CERTIFIED

AS-DELIVERED

AS-SUPPORTED

DESIGN

DELIVER

Y


Science Concept

Mission Concept of Operations

System Level Specification

System Design

Realization Plan

Realized:• Parts• Subsystems• Systems

Certified System

Description of the System

Use of the System

Engineering: The design and manufacture of complex products…

The Systems Engineering “V”


6

How might NASA fully leveraging evolving digital technologies?

To start, I want to borrow some concepts from the [1]Boeing Corporation, starting with the Digital Value Chain

[1] The System Engineering “V” - Is It Still Relevant In the Digital Age?Daniel Seal, Senior Manager, PLM, Boeing Defense, Space & SecurityGlobal Product Data Summit 2018

The transformation of an organization’s activities, processes, competencies, capabilities, and products to fully leverage evolving digital technologies


DIGITAL TWINS

VIRTUAL CERTIFICATION

VIRTUAL ECOSYSTEM

VIRTUAL OPERATIONS

VIRTUAL PRODUCTION SYSTEM

VIRTUAL QUALIFICATION

BUSINESS MODEL

MODEL BASED PRODUCTION PLANNING

MARKET (MISSION) MODEL

MODEL BASED DEFINITION

MODEL BASED SYSTEMS ENGINEERING

SIMULATIONMODELING

Evolution from SE to MBE

NEEDS SOLUTIONS

PHYSICAL SYSTEMS


Approved for Public Release (RROI 18-00101-BDS)

7

Description of the System

Use of the System

AS-OFFERED

AS-NEEDED

AS-SPECIFIED

AS-DESIGNED

AS-PLANNED AS-BUILT

AS-TESTED

AS-CERTIFIED

AS-DELIVERED

AS-SUPPORTED

The digital system model:• Becomes the digital thread• Coordinates the simulation

environment• Enables the digital analytics


MBSE offers process improvement for SE throughout the entire project lifecycleProcessefficiencies:

Reduced effort, time,and cost in executingSE processes

• Clearly articulated concepts•More rapidcommunicationwithin team

• Improved support for program reviews,decision milestones, etc.

• Improved reuse ofknown-good designs and exiting architecturalelements

• Faster convergence on multi- discipline /multi-organizational problems

• Automatic generation of documents,briefing materials, etc.

•Ready availability of information onsystem baselines

Leadingto:Enhancedquality and integrity

in system architectures

• Improved communicationand sharedunderstanding among disciplines, teams, and stakeholders

• Improved and earlier detection of design errors, wrong or missing requirements, conflicting interface definitions, etc.

• Improved tools for requirements analysis, allocation,andtracing

• Architecture Re-use -Abstraction/Inheritance, Modularity,Loose Coupling, Interface Management,and others

• Framework for modeling and simulation at multiplelevels

Enabling:Efficient and robust

Mission Development and Execution• Model reuse for detailed and informed candidateconcepts

• Embedded lessons learned facilitatinginformed decision making

• “Digital twin” –enablingautomatic interface verifications

• Engineering efficiency through digital-centric certification processes to inform andreduce cost for physical certification

• More timely identification of discrepancies between elements, improving design closure for major gate reviews

• “Real-time review”,with interactiveinformation

• Recovers ability to understand systemsacross disciplines and subsystems in the context of growingcomplexity

What’s in it for the SE team? What’s in it for the Program/Project?

8

What’s in it for the Enterprise?


9

So…what is MBSE…?Systems Engineering•Technical System Development•Technical Information Management•…a methodical, multi-disciplinary approach for the design, realization, technical management, operations,and retirement of a system.

•System Engineering Description: NPR 7123

System Architecture (Product Architecture)•Description of the System•System Structure, System Functions/Behaviors, System Requirements [For operation and development]•Precise language for description of systems to perform tasks•Mathematical abstractions for analysis•Architecture Organization (NASA Architecture Framework)

Digital System Model•Modeling Language (e.g. SysML) A modeling language specific to engineering systems•Appropriate level of rigor for the task at hand•Supports the analysis, design and verification of complex systems•“Rule set” for model elements•Architecture Organization (NASA Architecture Framework)

Modeling Engine•“Modeling Tool” – Cameo Systems Modeler (MagicDraw ) is one (of many)•Enables creation of models•Provides display and export of “model artifacts”


10

Pre-A A B C D E

MBP

EM

ulit-

Phas

e To

ols

MBS

E an

d IM

JWST ISIM

Thermal Desktop, NASA JSC DAC, Star-CCM+, Surface Evolver, ANSYS-CFX, …

GMAT, STK, FreeFlyer, ODTK, EMTG, GEONS, …

42, Freespace, Matlab Simulink, …

PACE

Subsystems/Branches Example Tools

cFS, GMSEC, GDS, µFE, …Flight S/W Systems:

Nav/Mission Design:

Propulsion:

ACS:

JPSS Ground

ICESat-2

NASTRAN, FEMAP, PATRAN, Mechanica, ...Structural:

IDC

MMS

RESOLVE (XRISM)

JWST Sub-Sys

MEME-X

Sounding Rockets

cFS/cFE

WFIRST

GMSEC

SCaN

OST

L’Ralph

ALICE

Gateway

Funded – aspect of their job Learning opportunity, not Project critical

Project specific

Engineering Discipline


Institutional Foundation• Training

– GSFC Mission Specific– Early lifecycle

• Architectural Framework– Common architecture descriptions– Enables better collaboration and re-use

• Design Reference Architecture (Kick-starter models to flatten learning curve)– Instrument Architectures– Spacecraft bus

• Physics based integrated modeling / Discipline models11


Examples

12


Mission System Model

13

All the information for a “ConOps” document is in the model.

This document is typically made up of information pulled from many different SE work products. (i.e. many other documents)

The System Model is built and managed such that the information is consistent across all elements, and used in multiple “artifacts”.


14

Improved Quality: Achieving consensus through

the rigorous process of creating diagram drives thorough

conversation


15

Ask the model: What are all the

behaviors the MOC is expected to

perform?

Inherit/re-useentire system

elements (rigor), and then modify as

appropriate.

Single Source of Technical Truth: Build the model in one environment,

publish to multiple reports, consistently.


16

“Enterprise” Architecture Framework

ViewpointWork

Products


17

MBSE needs:• A clear and consistent definition of what is expected by reviewers, and from presenters• This definition is the basis of communication with partners

MBSE Value Proposition: Work products span across multiple criteria / key documents.

• Re-use• Consistency• Document

Generation

E.1 MCR Criteria

SMAF Work Products: Review Criteria: a. Sci-1 Science Concept MCR.EC.03B, MCR.EC.05.A, MCR.EC.05.D,

MCR.SC.01 b. Sci-2 Science Traceability Matrix MCR.EC.03.C, MCR.EC.05.A c. Sci-3 Concept Study Report MCR.EC.03.B, MCR.EC.05.B, MCR.EC.05.D,

MCR.SC.02, MCR.SC.05X d. Reqt-1 System Requirements Document MCR.EC.03.C e. Proj-1 Stakeholder Expectations Document MCR EC.03.A f. Proj-2 Project Plan (including Project Control Plan WPs) MCR.EC.04, MCR.EC.05.K, MCR.SC.07, MCR.SC.08 g. Proj-3 Technical, Schedule, and Cost Control Plan MCR.EC.05.C, MCR.SC.06 h. Proj-5 Risk Management Plan MCR.EC.05.E i. Real-6, Verification and Validation Plan MCR.EC.05.F j. Soln-1 Systems Engineering Management Plan MCR.EC.05.G, MCR.EC.05.J

Viewpoints to MCR Entrance and Success Criteria

MCR

.EC.

00 M

CR E

ntra

nce

Crite

ria

MCR

.EC.

01 A

gend

a

MCR

.EC.

02 R

evie

ws

MCR

.EC.

03 P

rimar

y Pr

oduc

ts

MCR

.EC.

03.A

Sta

keho

lder

s and

Exp

ecta

tions

MCR

.EC.

03.B

Miss

ion

Conc

ept

MCR

.EC.

03.C

Key

Per

form

ance

Par

amet

ers

MCR

.EC.

04 P

rogr

amm

atic

Prod

ucts

MCR

.EC.

05 T

echn

ical P

rodu

cts

MCR

.EC.

05.A

Goa

ls an

d O

bjec

tives

MCR

.EC.

05.B

Alte

rnat

ive

Conc

epts

MCR

.EC.

05.C

Cos

t and

Sch

edul

e Es

timat

es

MCR

.EC.

05.D

Des

cope

Opt

ions

MCR

.EC.

05.E

Risk

Ass

essm

ent a

nd M

itiga

tion

MCR

.EC.

05.F

V a

nd V

App

roac

h

MCR

.EC.

05.G

SEM

P

MCR

.EC.

05.H

Tec

hnol

ogy

Deve

lopm

ent P

lan

MCR

.EC.

05.I

TRL A

sses

smen

t

MCR

.EC.

05.J

Engi

neer

ing

Deve

lopm

ent A

smt

MCR

.EC.

05.K

Sup

port

Str

ateg

y

MCR

.EC.

05.L

Sof

twar

e Pr

oduc

ts

MCR

.SC.

00 M

CR S

ucce

ss C

riter

ia

MCR

.SC.

01 M

issio

n O

bjec

tives

MCR

.SC.

02 C

once

pt M

eets

Exp

ecta

tions

MCR

.SC.

03 F

easib

ility

MCR

.SC.

04 E

valu

atio

n Cr

iteria

MCR

.SC.

05 N

eed

MCR

.SC.

06 C

ost a

nd S

ched

ule

Estim

ates

MCR

.SC.

07 C

ompl

ianc

e w

ith G

uida

nce

MCR

.SC.

08 T

BD/T

BR D

ispos

ition

MCR

.SC.

09 A

ltern

ativ

e Co

ncep

ts

MCR

.SC.

10 T

echn

ical P

lann

ing

MCR

.SC.

11 R

isk A

sses

smen

t and

Miti

gatio

n

MCR

.SC.

12 S

oftw

are

Science Viewpoint X X X X X X X X XRequirements Viewpoint XTechnical Solution Viewpoint X X X X X X X X X X X X X X X XProduct Realization Viewpoint X XProject Implementation Viewpoint X X X X X X X X XMission Operations Viewpoint XEnterprise Viewpoint X


• Flexible… data integration and interoperability– Industry standard approach to integration of data– Data resides and is maintained by the accountable party, including SE– No dedicated army of tailoring and tooling and personnel, COTS implementation

• Re-use of models … more efficient product generation and knowledge transfer – More rapid start-up and improved efficiency over time– Models flow across, and mature with, system life-cycle– Validated models offer future opportunity for higher fidelity early life-cycle

• Models provide “baseline” for other discipline integration– Traditional SE Products (Stakeholder Integration and SE response)– More efficient “automation” of trades and tracking of sensitivities– Integration of Analytics (CAD, Loads, PRA, FT, Future SE, etc.)– Manufacturing (Additive)

MBSE helps focus the art of SE to Design and Realize the System

Lessons Learned: Benefits


§ Process (e.g. Project Start Up)– Consistent approach to System Architecture Description and Model Architecture Description

• Coordinating models between different cross-Center organizations is a challenge • Early adopters are not necessarily coordinated even within a Center (lack of standard

approach/architecture framework)– Model Architecture is as important as System Architecture

• Need to develop model philosophy (what do we want this model to do for us?)• Critical to develop data strategy at project inception

– Implementation and broader MBSE infusions needs to be deliberate– Component level/physical performance modeling approach is currently driven by component level

manager (no driving need to coordinate with system level until information is shared)

19

Lessons Learned

digital mission engineering engineering · digital mission engineering engineering model based...

Documents