IT Infrastructure: Key to Successful Application of Model-Based Systems Engineering on NASA Programs Jody H. Fluhr August 17, 2010.

IT Infrastructure: Key to Successful Application of

Model-Based Systems Engineering on NASA Programs

Jody H. Fluhr

August 17, 2010

Introduction

Common Principles» Increase Collaboration and Productivity» Improve Integration» Increase effectiveness and efficiency

Constellation Program Systems Engineering»Define and Deploy a Systems Engineering

Capability (People, Processes and Tools) for the program

»Applicable to Agency’s SE Capability» Innovation in Systems Engineering drives greater

innovation in IT

Presentation Title—2—March 5, 2010

AGENCY’S INFORMATION TECHNOLOGY AND AGENCY’S INFORMATION TECHNOLOGY AND ENTERPRISE ARCHITECTURE IS KEY TO ENTERPRISE ARCHITECTURE IS KEY TO

SUCCESSFUL SUCCESSFUL SYSTEMS ENGINEERING ON NASA PROGRAMS.SYSTEMS ENGINEERING ON NASA PROGRAMS.

Constellation Program

Overview IT-Related Directives IT Infrastructure Overview Model-Based Systems Engineering Capability


Constellation Program

Ares I Launch Vehicle

ISS Initial Capability Moon

Lunar Capability

Ares VLaunch Vehicle

Launch Suit EVAOrion Crew Vehicle Altair Lunar Lander

GroundOperations

Mission Operations

SurfaceSystems

Mis

sio

ns

Mis

sio

ns

Sys

tem

sS

yste

ms

Tea

mT

eam

Constellation Program IT-Related Directives

Directive to use an IT collaborative environment for generating, using and managing information assets» End user has immediate access to all authorized

Program/Project data, regardless of their organization (gov’t or contractor)

» Consistent Interface to program/project data» Established best practices » Facilitate Traceability/Compliance across systems

Directive to use a single systems engineering database as the authoritative source for:» Technical requirements, verification data» Design Reference Mission data and Operations Concepts

data» Operational, functional, and physical architecture data» Functional analysis data» Linkage/Traceability of the above


Constellation Leadership recognized the importanceConstellation Leadership recognized the importanceof IT capabilities and the need for clear policies.of IT capabilities and the need for clear policies.

Constellation Systems Engineering Capability

System Engineering tools accessible to nation-wide team (via ICE), configured to support the defined systems engineering process

A Model-Based Systems Engineering Process consisting of:» A tool-agnostic process definition that can be implemented in any

tool of choice» Work Instruction-level procedures to guide engineers in

execution of SE process in program-selected tools» Automated audits/metrics to ensure process compliance and

identification of issues» Work Instruction-level procedures to maintain data integrity

Formal Training organized along systems engineering process areas» Approximately 10 training classes available» Over 100 training classes conducted with hundreds of engineers

trained

Partial List of Constellation Information Assets

Requirements (Architecture/System/Element/Operational) Operational Concepts Design Reference Missions Physical Architecture (Systems, Interfaces) Verification Functional/Performance data Risks Hazards Design Compliance Product Structures Drawings Trade Studies Schedules Models and Simulations Documents


Constellation IT Infrastructure - Integrated Collaborative Environment (ICE)


ICE Portal provides access to applications used ICE Portal provides access to applications used to manage information assets.to manage information assets.

Constellation IT Usage Metrics - Part 1(Tools, Applications, Services and Integrations)

ApplicationDeployed Status

# Users

# Records Related Info

CAIT Production 1048 2083 Includes TDS and BEAs

CxIRMA Production 2116 3904 Includes CxP Risks

Cradle Production1326 382,000

CxP Database only; does not include LMCO/others

CR Pipeline Production50 2824

Includes CRs, Products, Documents and Revisions

MAS-FMEA/CIL

Production114 4759 Includes FMEAs and CILs

MAS-Hazard DB

Production688 381

Hazard database size is rapidly growing

MAS-GMIP Production 267 968

MAS-PRACA Production3891 13308

Includes Cx, ISS, and ARC PRACA

Windchill ProductionTBS TBS

ICE only - does not include center DDMS

High End-User Experience User/Deployment Experience Needed

Constellation IT Usage Metrics - Part 2(Tools, Applications, Services and Integrations)

ApplicationDeployed Status

# Users

# Records Related Info

Link Registry Partially Deployed NA NA

Underlying Architecture Components

NAMS / ICE-LDAP/eAuth

Production

NA NA

Underlying Architecture Components - agency transition to eAuth underway

DAGGER Partially Deployed NA NA

Underlying Architecture Components

SIP Production 20 <100Integration recently rolled out 12/2009

COFR Prototype 0 0Integration - capability demonstrated 03/2010

ADP Prototype 0 0

Integration - capability demonstrated with Contractor test cases

High End-User Experience User/Deployment Experience Needed

Cradle Systems Engineering Tool Metrics

METRIC CRITERION MAY-07 DEC-07 MAY-08 FEB-10

NOTES / COMMENTS

Total Items (includes previous B/L) 90,316 110,000 173,506 381,582

Includes ALL REVISIONS of ALL Items

Frames 410,091 624,000 1,069,453 4,217,386 Pieces of information

Total Cross-References (Links) 464,994 1,000,0004,268,151 9,553,268 Links between items

Operational Concept Statements (OPS CONS) 165 2,682 3,794 4,269

Reflects Projects OCD development

Requirements (REQ-CONST) 25,425 33,000 52,816 90,068

Includes ALL REVISIONS of a Requirement

Verification Requirements 14,397 22,000 35,181 69,574

Includes ALL REVISIONS of a Verification Requirement

Doc Sections 11,634 18,000 23,065 44,643

Includes ALL REVISIONS of a Document Section

Cradle Systems Engineering Tool Metrics

METRIC CRITERION MAY-07 DEC-07 MAY-08 FEB-10 NOTES / COMMENTS

Issues 4,932 7,553 10,735 13,153

Includes ALL REVISIONS of an Issue

Test Verification Reports (TVR) N/A 1,832 7,109 40,223

Reflects Program transition to Design Validation - including below Element DVO content

TEST 129 1,168 3,428 9,034

Reflects Program transition to Design Validation

Analysis (TDS) 0 0 943 3,174

Supplied by CAIT; two-way interchange operational

Architecture Components - ADD 0 0 252 540

Includes Conceptual, Block Configuration, and External Systems

Cradle-EXPL Interfaces to/from other CxP tools/processes 0 2 6 11

ARM, CAIT, CART, DAGGR, IRMA, RID Tool, non-EXPL Project Databases, Primavera, SIP

Number of Audits (Documented) 4 39 114 218

REQ, VR, ISSUES, OPS CON, Generic DB audits

Cradle Processes (Approved) 0 10 25 53

Includes approved Cradle Methodology, Procedures and Tip Sheets

Model-Based Systems Engineering Process & Procedures

Process & Procedures documented and available via Team Wiki

Process involves development in four key areas for each level of the architecture:» Requirements (and

Associated Verifications)

» Mission Definition» Physical Architecture» Functional Architecture


Constellation SE Process Wiki


Detailed Procedures Available via Wiki


MBSE Example – Integrated Mission Model

Current State

Operations ConceptDocument

Lunar Lander Project

International Traffic in Arms Regulations (ITAR) NoticeThis document contains information which falls under the purview of the U.S. Munitions List (USML), as defined in the

International Traffic in Arms Regulations (ITAR), 22 CFR 120-130, and is export controlled. It shall not be transferred to foreign nationals in the U.S. or abroad, without specific approval of a knowledgeable NASA export control official, and/or unless an export license/license exemption is obtained/available from the United States Department of State. Violations of these regulations are punishable by fine, imprisonment, or both.

OPSCON1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

A B C D E F G H I

Lander attached to EDSDocking in progress

Gear FoldedLIDS Hatch Closed

Crew in CEV

Lander attached to EDSLander mated to CEV via LIDS

Gear FoldedLIDS Hatch Closed

Crew in CEV

Transition to Earth Rendezvous Mode

LEO Rendezvous Prep Docking Operations Post Docking Operations

5 minutesEnd with Docking Mechanisms Latched

30 minutesStart with Docking Mechaisms Latched

MET 000/04:06:00Docking Mechanisms Latched

MET = 000/09:07:00 MET 000/09:37:00

CEVCrew life support

Voice, Cmd, Data w/ Control CenterCmd & Data w/ EDS (RF)

Voice, Cmd, Data w/ Control CenterCrew life support

CEV Equalize Pressure

EDS

Guidance and NavFree Drift At Contact

Cmd & Data w/ Control CenterElec Power Generation

Electrical Power GenerationGuidance and Nav

Trajectory and Attitude Cntl Cmd & Data w/ Control Center

Elec Power Generation

Lander Thermal Control

Monitor and Control Critical Parameters

Control Center Comm Interfaces

Element InterfacesEDS to Lander: Power

EDS - Lander - CEV: Cmd & Data (Hardline)

Power

Comm and Tracking Comm not active Power down comm

CDH

Provide CDH for thermal and ECLSS subsystems

Monitor and control critcal parameters on other subsystems

Route cmds and data to / from EDS and CEV

GNC GNC not active

Thermal

ECLSS

Propulsion

Structures and Mechanisms

Crew Systems

EVA

Activity DurationReference

3 Hours 30 MinutesNext start

1 Hour 26 MinutesNext start

Provide RF comm with CEV

Distribute power from EDS (TBD kW)

EDS to Lander: PowerEDS - Lander: Cmd & Data (Hardline)

CEV - Lander: Cmd & Data (RF)

EDS - Control Center: Cmd & DataCEV - Cntl Center: Voice, Cmd, & Data

EDS - Control Center: Cmd & DataCEV - Cntl Center: Voice Cmd, & Data

Event Time

(MET Referenced to Orion/Ares I Launch)

Proximity Operations

Thermal ControlMonitor and Control Critical Parameters

Visual Nav Aid (TBR)

Operating in LEO as RendezvousChaser

Crew life supportVoice, Cmd, Data w/ Control Center

Cmd & Data w/ EDS (RF)

Guidance and NavTrajectory and Attitude Cntl


Cmd & Data w/ CEV (RF)Maneuver to Docking Attitude

Provide fire detection and supression to modules with powered systemsProvide water to thermal as needed

Provide CDH for thermal and ECLSS subsystemsMonitor and control critcal parameters on other subsystems

Route cmds and data to / from EDS

Operating in LEO as RendezvousChaser

Crew life supportVoice, Cmd, Data w/ Control Center

Lunar suit gear stowed in AM

GNC not activeTo support the RPOD operations of the CEV, the lander will provide a passive reflector. Other than this function, other GNC functions of the mated EDS/LLV stack are maintained by the EDS (instead of the LLV). To support

the RPOD operations with CEV (the chaser vehicle), the EDS will maintain the mated LLV/EDS configuration in a quiescent state.

Monitor and Control Propellant Pressures and Temperatures

Maintain radiator flow to prevent freezeupProvide thermal control to powered subsystems

Provide thermal control to unpowered subsystems to maintain above min temperature

Guidance and NavTrajectory and Attitude Cntl


Thermal ControlMonitor and Control Critical Parameters

EDS to Lander: PowerEDS - Lander: Cmd & Data (Hardline)

Lander Subsystems

Sortie and Outpost Mission - Ares I/Ares V Launch Order, Zero Beta at LLO Undocking for Polar Sortie

Rendezvous, Proximity Operations, and Docking (RPOD) Operations (LEO) LSC.8Phase Start: Initiation of the First Rendezvous Burn (Orion Chaser, Altair/EDS Target)Phase End: Completion of Post Docking Procedures (EDS Resumes Attitude Control)

Activity

Earth Rendezvous Mode

System Configuration

Lander Mode

Lander attached to EDS (target)Gear Folded

CEV in LEO (chaser)Crew in CEV Suit Configuration 1

LEO Rendezvous

System Functional Allocation

Detailed TimelineFlight Phase Activity Event (L minus), MET Duration Remarks

Issue DD250 Government Acceptance of Contract Deliverable Yellow = trajectory events. Lt. Blue = power transitions

Removal of Flight Hardware from Transportation L-152/00:00:00 002/00:00:00

Transportation of Altair Elements (AM, DM, AL) to Processing Facility

L-150/00:00:00 005/00:00:00Note: All durations are notional. The Total time from the begiining to the end of Ground Processing is the same as for LDAC-2.

Perform NASA-Approved Deferred Work on Vehicle Elements

Unspecified L-150/00:00:00 000/00:00:00 Placeholder. Variable duration. No time allocated.

Perform Corrective Actions on Lander Elements as Required

Unspecified L-150/00:00:00 000/00:00:00 Placeholder. Variable duration. No time allocated.

Install Altair Elements into Respective Test Stands. L-143/00:00:00 003/00:00:00

Element Receiving Inspections L-140/00:00:00 006/00:00:00

Element Non-Hazardous Commodity Servicing and Post-Delivery Testing.

L-134/00:00:00 006/00:00:00

Altair Element Integration & Final Non-Hazardous Servicing.

L-129/00:00:00 007/00:00:00

Element to Element Interface Verification L-122/00:00:00 006/00:00:00

Lunar Surface Systems (LSS) to Altair Integration & Testing.

L-117/00:00:00 007/00:00:00 Cargo DRM Only.

Altair Integrated Systems Testing L-110/00:00:00 010/12:00:00

Lunar Multi-Element Integration Testing (MEIT) L-099/12:00:00 010/12:00:00

Final Internal AM & Airlock Cargo Stowage L-089/00:00:00 010/12:00:00 N/A for Cargo DRM. AM only for Outpost DRM.

Crew Equipment Interface Testing L-078/12:00:00 010/12:00:00 N/A for Cargo DRM

Ascent Module & Airlock Internal Closeouts & Hatch Closure Leak Checks

L-068/00:00:00 006/00:00:00 N/A for Cargo DRM. AM only for Outpost DRM.

Altair Closeouts Altair External Closeouts L-062/00:00:00 006/00:00:00

Transport Altair to Hazardous Processing & Encapsulation Facility

L-056/00:00:00 002/04:00:00

AM/DM Hypergolic Propellant Servicing L-053/20:00:00 014/00:00:00 DM only for Cargo DRM

High Pressure Gas Servicing L-039/20:00:00 007/00:00:00

Encapsulation For Transportation to VAB

Encapsulation of Altair in Ares V Shroud L-032/20:00:00 007/00:00:00

Transportation of Altair to Integration Facility

Transport Altair Elelements to VAB L-025/20:00:00 000/06:00:00

Integrated Vehicle Processing Lander/Shroud Arrival at VAB Transfer Aisle L-025/14:00:00 014/00:00:00

Transportation of Stack to Launch Pad

Transport Altair Stack to Launch Pad L-011/14:00:00 001/00:00:00

Pad Hard Down Operations Pad Hard Down L-010/14:00:00 000/02:00:00

Fuel Cell Cryogenic Servicing L-010/12:00:00 003/12:00:00

Cryogenic Propellant Servicing L-007/00:00:00 004/00:00:00

Call to Stations For Countdown L-003/00:00:00 000/00:00:00

Pre-Tanking Launch Countdown Procedures L-003/00:00:00 002/12:00:00

Go for Tanking L-000/12:00:00 000/00:00:00

Tanking L-000/12:00:00 000/08:00:00

Call To Stations for Final Countdown L-000/04:00:00 000/00:00:00

Final Countdown Procedures L-000/04:00:00 000/04:00:00 Times prior to MET = 000/00:00:00 are Launch Minus (L-) times

Booster Ignition Ares V/Altair/EDS Liftoff 000/01:42:00 000/00:00:01 Ares V T-0. MET = 000/00:00:00 is Ares-I/Orion Liftoff

SRB Separation 000/01:44:00 000/00:00:01

First Stage MECO 000/01:46:00 000/00:00:01

EDS Separation & Ignition 000/01:46:05 000/00:00:05

Shroud Jettison 000/01:46:30 000/00:00:00

Ascent Ops 1 000/01:46:30 000/00:05:30 5 minute 30 second interlude between scheduled events.

Insertion into LEO (EDS burn) 000/01:52:00 000/00:03:00

LEO Cruise Ops 1 000/01:55:00 000/00:27:00 27 minute interlude between scheduled events.

Transfer EDS Power to Altair 000/02:22:00 000/00:05:00

LEO Crew Sleep 1: 000/14:00:00 000/08:00:00

Post-Sleep Activity 000/22:00:00 000/02:00:00

Functional Checkouts

Egress Lander

Post-Sleep Activity 005/02:00:00 000/02:00:00 Hygiene, meal, morning mail & conference.

Altair Lunar Polar Sortie Mission Timeline - Ares I/Ares V Launch Order - Zero Beta at LLO Undocking - With Plane Change in LLO Revisions for RAC-1

Standalone Operations (LSC.1)

Element Arrival Operations

Element Standalone Processing

Altair Integration & Test

Hazardous Offline Processing

Integrated Operations (LSC.2)

Pad Operations (LSC.3)

Pad Operations

Launch (LSC.4)

Call to Stations for Launch Countdown - Pre-Tanking

Procedures

Go for Tanking Call - Cryogenic Propellant Loading

Call to Stations for Final Countdown

Ascent (LSC.5)Powered Flight

LEO Configuration (Post-Insertion)

(LSC.6)

Transition to LEO Config Mode

Summary Timeline

Operational Modelsin SE Tool

Opportunity

Separate Products Incur Substantial Coordination Costs

Operational Models as the Authoritative Integrated Source for Operations Information eliminates

Product Synch

StandAlone

Operations

LSC.1

IntegratedOperations

LSC.2

PadOperations

LSC.3

Launch

LSC.4

Ascent

LSC.5

LEOConfiguration

(Post-Insertion)

LSC.6

LEO Loiter

LSC.7

RPODOperations

(LEO)LSC.8

TLIPreparation

LSC.9

Trans -LunarCruiseLSC.10

LOIOperations

LSC.11

Pre-SurfaceOperations

(LDO)LSC.12

LunarLander

DescentLSC.13

AND AND

SurfaceOperations

LSC.14

LunarOrbit

MaintenanceLSC.15

Lunar Ascentand RPODOperations

(LRO)LSC.16

TEIOperations

LSC.17

Trans-Earth

CruiseLSC.18

EarthArrival

OperationsLSC.19

Re-entry/Entry

LSC.20

Descentand

Landing

LSC.21

Recovery

LSC.22

Post - Flight

Processing

LSC.23

DD250

Transport toIntegration

FacilityComplete

MLP HardDown

LCD CTS

T - 0

OrbitInsertionMNVR

Complete

'Go' for

Orbit Ops

InitiateRendezvous

Burn

DockingComplete

TLI BurnComplete

Start LOIBurn Prep

LOI BurnComplete

PwrdDescentInitiation

Burn

ATPInitiate

Prep

DockingComplete

TEI BurnComplete

FinalEntryPrep

<EI-12>

SM

Separation

Fwd BayCover

Jettison

Touchdown

ArrivalPost - Flight

ProcessingFacility

Pre-Descent

start

Activity Model & Definitions(including attributes like durations, resource

usage, etc.)

Phase Model & Write-ups

DRM Model

Simulation

Desired State

Detailed Timeline

Summary Timeline

Reports from Simulation

Operations ConceptDocument

Lunar Lander Project

International Traffic in Arms Regulations (ITAR) NoticeThis document contains information which falls under the purview of the U.S. Munitions List (USML), as defined in the

International Traffic in Arms Regulations (ITAR), 22 CFR 120-130, and is export controlled. It shall not be transferred to foreign nationals in the U.S. or abroad, without specific approval of a knowledgeable NASA export control official, and/or unless an export license/license exemption is obtained/available from the United States Department of State. Violations of these regulations are punishable by fine, imprisonment, or both.

OPSCON Compiled from Phase Models

Published from SE Tool

Existing Products are created by Extracting Reports from SE Tool

Models

Report Generation

Conclusion - Pushing the Envelope As NASA continues to develop its Systems Engineering

capabilities, greater demands will be placed on the IT and the Enterprise Architecture

While benefits have been realized, more needs to be accomplished:» Utilizing tools to develop and manage authoritative

information is a big step forward, it’s possible to have program authoritative information locked in “tool silos”.

» Tool-to-Tool integrations have been accomplished but has its limits.

» Maximizing the value of the authoritative information requires better Data Integration – Timely, customized and accessible.


Backups


Systems Engineering Processes – NASA SE Handbook

Figure 2.1-1 The systems engineering engine

Model-Based Systems Engineering

An approach to systems engineering where information about the system is:

» Contained in an accessible database or repository

» Captured in a standardized, methodical manner

» Captured in graphical models when appropriate

» Related and linked in standardized ways

» Capable of being queried and reported

Contrast to “Document-Based” Systems Engineering» Equivalent of data ‘silos’

» Manual correlation of data

What are the benefits?» Improved Traceability of Mission Definition, Requirements, Verification and

Architecture

» Improved Data Management, Accessibility and Quality

» Improved Integration and Insight

• Capabilities to query the data, do advanced checks, improve integration

» Reduced cost of documentation• Data is captured once in an authoritative data source (repository/database) and is

extracted to produce the content of a document• Content integrity between documents and artifacts.

Information Integration Needs

21

Problems DB(CxPRACA)

Schedules DB(Primavera)

Risks DB(IRMA)

Hazards DB(cxHazard)

CoFR DB(CxOW) Others …

Additional sources: Cradle, CAIT, Windchill Products Structure, Windchill Documents

IS Services, Link Manager, Security, CDM ….IS Services, Link Manager, Security, CDM ….

Data Consumers

Underlying Architecture

Data Sources(MAS, JSC, ICE, Others)

……

Data is pulled from authoritative sources

Read Only

If one end of the data is modified then the end user is notified

On Demand CoFR System The CoFR System enables continuous

monitoring of flight readiness status for decision makers by dynamically integrating data from engineering databases

» All CoFR processes pull together diverse information to inform decision making

The CoFR System provides interactive overviews of pertinent data and enables drilldown for more detailed analysis

» Provides a view into the status of tasks and products per each organization that lead up to endorsements for a mission or program event

The CoFR System can provide views to meet specific needs of NASA:» Programs (Launch Vehicles, elements, etc) » Milestones (FRR, DOL Review, etc.) » Organizations (MOD, SR&QA, etc.) » Roles (Mission Manager, Chief Engineer,

Project Managers, etc.)

IT Infrastructure: Key to Successful Application of Model-Based Systems Engineering on NASA Programs Jody H. Fluhr August 17, 2010.

Documents

successful systems engineering

systems directive

constellation program

constellation program

constellation leadership

process compliance

authorized programproject

data integrity formal