Phillip.hall

National Aeronautics and Space Administration

www.nasa.gov

Collaborative Multi-Center Implementation of NPR 7123.1A

Phillip HallNASA MSFC

Nancy McNelisNASA GRC

1Used with Permission


www.nasa.gov

Can Centers Develop “Common” Processes?

• Common Goal is Compliance with NPRs– NASA Procedural Requirements Establish “What” NASA

HQ Expects of the Centers– Center Level Procedural Requirements Establish “How” it is

Done at that Given Center

• Centers Do Not Have Common Organizational Structure

• NPR 7120 Series is Project Focused, Not Organizational Focused

The Question Then Becomes …• Is the Project Structure from Center to Center Similar

Enough to Allow “Common” Processes?2


www.nasa.gov

Can Centers Develop “Common” Processes?G

RC T

ypic

al P

roje

ct S

tru

ctu

re

WBS01Project Manager

Deputy PM

Project Chief Engineer

WBS03Safety & Mission Assurance

Chief Safety Officer

WBS01Business Support Office

Project Support Staff

WBS02Systems Engineering

Lead Systems Eng

WBS04Element 4

Element Lead

WBS05Element 5

Element Lead

WBS (n)Element (n)

Element Lead

WBS (n)Element (n)

Element Lead

Matrix from Space Flight Directorate

Matrix from S&MA

Matrix from Engineering Directorate

Matrix from Other Directorates

3


www.nasa.gov

Can Centers Develop “Common” Processes?

4

MSF

C T

ypic

al P

roje

ct S

tru

ctu

re

NASA AdministratorDeputy Administrator

Associate AdministratorNASA Chief Engineer

MSFC Center Director

MSFC Eng Director

Mission Directorate AA

Program Manager

MSFC Eng Deputy Directors - Senior Eng Management PresenceProgram assigned

MSFC DeputyProgram Manager

Project Manager

MSFC Chief EngManager

MSFC EngDept/Lab Managers

MSFC EngDivision Chiefs

MSFC EngBranch Chiefs

MSFCInstitutional Eng

Cen

ter D

isci

plin

e Le

ads

Inde

pend

ent R

evie

ws

MSFC ProgramChief Eng*

MSFC ProjectChief Eng

MSFC Chief EngManager’s Staff

Independent Reviews

Direct Report

Program AuthorityTechnical Authority

Senior Eng Presence


www.nasa.gov

Common Goals

• Comply with NASA Procedural Requirements (“What”)– Requirements traceability from NPRs to Center Level Procedures

• Provide Sufficient Detail (“How”)– Outline a Step by Step Process of “How” for Project Execution– Define Roles and Responsibilities of the Project Teams– Incorporate Best Practices– Provide Commonality on How Projects Conduct Business within the

Organization

• Prevent Shelf-ware Mentality– Provide Forms/Templates for Project Use

• Templates which are Annotated Outlines of Project Documentation • Forms which are Available Electronically

5

Develop “Common” Processes for the Organizations Rather Than on a Program/Project Basis


www.nasa.gov

Achieving Common GoalsWhere We’ve Been?

• Minimal Confidence in Project Planning and Estimates because assumes LOE-based rather than Task-based

• Lack of “Standard Toolbox”– Inconsistencies in Deliverables and Products– Results in a lot of re-work

• Project-by-Project Approach Rather than Institutionalized

• Unclear Use of Best Practices and Lessons Learned

6


www.nasa.gov

Achieving Common GoalsWhere Are We?

• GRC– Organized Management Steering Group in 2007– Defined and Documented Development Approach– Obtained Executive Sponsorship and Organizational Buy-in– Began Collaborative Development with MSFC– Launched the Space Mission Excellence Program for Systems

Engineering in 2006

• MSFC– Organized Engineering Directorate Management Steering Group in

2008– Leveraging Work Defined at GRC– Gaining Executive Sponsorship and Organizational Buy-in– Working with Office of Strategic Analysis and Communications

(OSAC) to tie into Project Management– Introduction to the MSFC Systems Engineering Leadership

Development program7


www.nasa.gov

GRC Procedural Requirement DocumentsG

RC D

evel

op

men

t &

Imp

lem

enta

tion

GLPR7120.5.10GRC Space Flight Projects

Formulation & Implementation Requirements

- Text in Doc -Operations & Sustainment

SafetyGLPR 8700.4Safety & Mission

Assessment

Reliability & Maintainability

GLPR 1270.1Corrective & Preventative

Action

Quality Assurance

SM&A (NPD 8700.1)

GLPR 7120.5.30Safety & Assurance Requirements (SAR)

GLPD 1410.2GRC Doc

Management

-Text in Doc-Center Doc Training

GLPR 8730.5Quality System

Manual

GLPR7120.5.20 Deviations & Waiver

Center Mgmt (NPR 1400.1)GLPR 1410.1

GRC Directives Management

GLPR 1410.3Lower Level

Document Mgmt

Engineering Management (NPR 7123.1)

GLPR 7123.22Verification &

Validation

GLPR 7123.21Product Transition

GLPR 7123.23Implementation &

Integration

GLPR 7150.1Software

Engineering Requirements

-Text in Doc-6 Sections in

GLPR7120.5.10

GLPR 7123.37Decision Analysis

GLPR7120.0.4Risk Management

GLPR 7123.36Engineering

Review Board

GLPR 7120.5.40GRC Project and

Technical Planning

GLPR 7123.34Project Config Item

& Data Management


& Data Management

GLPR 7123.35Project Technical

Reviews

GLPR 7123.11Requirements Def

& Mgmt

GLPR 7123.12Design

Solutions

GLPR 7123.32Interface

Mgmt

Program/Project Management (NPR 7120.5)


& Data Management

GLPR7120.5.43Acquisition

GLPR7120.5.42Management

Reporting

GLHB-B-7120.1EVM System

Handbook

Text in Doc10 Sections in

GLPR7120.5.10

GLPR7120.5.41Project Review

Board

GLPR 7120.0.6Lessons Learned

GLPR7120.5.40GRC Project and

Technical Planning

GLPD7120.1EVM

https://knowledgeshare-in.grc.nasa.gov/eRoom/NASAc1f1/GRCProjectandSERequirementsWebContent

8


www.nasa.gov

Standard GLPR Architecture

Project Objective

Processes

Activities

Tasks

Project Requirement

Work Products

Process Deliverables

Project Deliverables

Components

Project Results

N PR’s Define “What”

GL PR’s Define “How”

at GRCConcepts

Techniques

Templates

Forms

Lessons Learned

Best Practices

GRC

Dev

elo

pm

ent

& Im

ple

men

tatio

n

9


www.nasa.gov

Standard GLPR Formatting

Activity (Sub-chapter level designee)Grouping of tasks that create a logical deliverable (or group of deliverables)

Flow chart WITH SWIMLANESGraphical illustration relationships of the tasks within an activity

Task (Sub-Sub-chapter level designee)Title of specific work to be performed necessary to build the deliverable. Should follow the Verb-Noun format

Task Descriptor (Letter designee)Specific description of work performed necessary to build the deliverable. • Should begin with the responsible roleWill contain Shall statements if applicable.

Additional Guidance (Not shown)Addition information provided to help the responsible person perform this task

GRC

Dev

elo

pm

ent

& Im

ple

men

tatio

n

10


www.nasa.gov

GLPR Development Procedure

• Identify New Processes or Revision

• Assign Resources

• Use Std Templates

• Leverage SMEs

• Draft Process Flow

• Draft GLPR Document

• Completed GLPR submitted to BMS

• Formal Inspection Process

• Feedback Provided to Inspectors

• Peer Review is Initiated

• Owner Reviews High Level Process

• GLPR Finalized

Identify and Document Procedure

3.1

Owner Review (CEO, M, Q, etc.)

3.2

Peer Review

3.3

MSGInspection

3.4

Executive Presentation

3.5

BMS Submittal

3.6

• Formally Manage Document

• MSG Will Determine Executive Review Readiness

• MSG Leads Will Determine MSG Inspection Readiness

• Owner Review and Concur

• Pre-MSG Inspection Readiness

• Present Completed document to Executives

• Pilot Approved Processes

• Executive Awareness

Success Criteria

GRC

Dev

elo

pm

ent

& Im

ple

men

tatio

n

11


www.nasa.gov

GLPR Development StatusG

RC D

evel

op

men

t &

Imp

lem

enta

tion GLPR # Document Name Owner

Review Peer Review MSG Inspection

Executive Review

BMS Status

Wave One

7123.36 Engineering Review Board (ERB) Complete Complete Complete Complete GLPR

7123.35 GRC Project Technical Reviews Complete Complete Complete Complete GLPR

7123.11 GRC Requirement Development and Management Process

Complete Complete Complete Complete GLID

7120.14 Waivers/Deviations Process Complete Complete Complete Complete Not Submitted

7120.5.40 Project and Technical Planning Complete Complete Complete Complete GLPR

7123.22 Product Verification and/or Validation Complete Complete Complete Complete GLID

7123.34 Data and Configuration Management Complete Pending TBD 1/19/10 Not Submitted

7120.5.10 Space Flight Project Requirements Complete Complete Complete Complete GLID

7123.37 Decision Analysis Complete Complete 10/20/09 11/20/09 Not Submitted

7120.5.41 Project Review Board (PRB) Complete Complete Not Applicable Complete GLPR

7120.5.42 Management Reporting Complete 10/30/09 11/16/09 1/14/10 Not Submitted

7123.33 Risk Management Complete Complete KO 12/7 TBD Not Submitted

7120.5.30 Space Assurance Requirements (SAR) Complete Complete Complete Complete GLPR

8700.5 Problem Reporting and Resolution Complete NA NA NA Not Submitted

7123.32 Interface Management TBD TBD TBD TBD Not Submitted7123.21 Product Transition Wave 3 Wave 3 Wave 3 Wave 3 Not Submitted7123.23 Product Imp and Integration Wave 3 Wave 3 Wave 3 Wave 3 Not Submitted7120.xx EVM Wave 3 Wave 3 Wave 3 Wave 3 Not Submitted7120.5.43 Project Acquisition Wave 3 Wave 3 Wave 3 Wave 3 Not Submitted7123.12 Design Solutions Wave 3 Wave 3 Wave 3 Wave 3 Not Submitted7123.41 Design and As-Built Wave 3 Wave 3 Wave 3 Wave 3 Not Submitted

Review Gates

12


www.nasa.gov

MSFC Doc Tree – BeforeNPR 7123.1

NASA Systems Engineering Processes and Requirements(Requirements [68] / Processes [17] / Best Practices [105] / Reviews [16])

MPR 7123.1 MPR 7123.2MSFC Systems Engineering Technical Reviews and Review Item Discrepancy (RID)

Processes and Requirements Processing, MSFC Programs and ProjectsRequirements [68] / Processes [17] / Best Practices [105] (Reviews [16]) + MSFC RID Process

AS42/Jeff Moore ED10/Phillip Hall PS01/Felecia Wilson ED10/Phillip Hall QD40/William Powell ED11/Amy Hemken ED11/Amy HemkenMWI 6410.1 MWI 8050.1 MPR 5000.1 MWI 7123.1 MWI 7120.6 MPR 8040.1 MWI 7120.2

Handling, Storage, Verification and Purchasing Reqts Development Prog/Proj Risk Configuration Data ReqtPackaging, Preserv., Validation of EM03/Patricia Johnson and Management Mangement Management Ident. / Def

and Delivery (HSPPD) Hardware, Software, MPR 1280.2 (5 of 17 Processes) DA01/Mary Demurray ED11/Eugena Goggansand Ground Support Process Control MPR 1280.1 MWI 7120.4Equipment for MSFC PS01/Felecia Wilson Management Doc. Prep.

MWI 5100.1 Review Prog/ProjInitiating Proc. Req.EI41/Ronie Akins

MWI 1280.1Mechanical Fab.

Request InstructionsSystem Design Processes

1 - Stakeholder Expectations Definition Process2 - Technical Requirements Definition Process3 - Logical Decomposition Process

*4 - Design Solution Definition Process

Product Realization Processes

5 - Product Integration Process

*6 - Product Implementation Process

7 - Product Verification Process8 - Product Validation Process

9 - Product Transition Process

Technical Management Processes

*10 - Technical Planning Process

11 - Technical Requirements Management Process* = 4 additional MWI's needed [4, 6, 10 & 17] 12 - Interface Management Process

13 - Technical Risk Management Process

Existing MWI's replacement [in future] 14 - Configuration Management Process

15 - Technical Data Management Process

16 - Technical Assessment Process

*17 - Decision Analysis Process

We developed 3 MSFC documents to fill in the gaps

shown by the initial compliance analysis

MSF

C D

evel

op

men

t &

Imp

lem

enta

tion

13


www.nasa.gov

MSFC Doc Tree - ProposedNPR 7123.1

NASA Systems Engineering Processes and Requirements( Requirements [68] / Processes [17] / Best Practices [105] / Reviews [16] )

MPR 7123.1MSFC Systems Engineering Processes and Requirements( Requirements [68] / Processes [17] / Best Practices [105] )

MPR 7123.2Technical Reviews and Review Item Discrepancy (RID)

Processing, MSFC Programs and Projects( Reviews [16] ) + MSFC RID Process

Specific Practice

Templates

Checklists

Forms

Roles & Responsibilities

Process Metrics

Technical Management Processes

Product Realization ProcessesSystem Design Processes

MWI 7123.1MSFC Systems Engineering Processes

MSE 7123.1Stakeholder Expectation Definition

MSE 7123.10Technical Planning

MSE 7123.2Technical Requirements Definition

MSE 7123.3Logical Decomposit’n

MSE 7123.4Design Solution Definitions

MSE 7123.11Requirement Management

MSE 7123.12Interface Management

MSE 7123.13Technical Risk Management

MSE 7123.14Technical ConfigManagement

MSE 7123.15Technical Data Management

MSE 7123.16Technical Assessment

MSE 7123.17Decision Analysis

MSE 7123.5Product Implementat’n

MSE 7123.6Product Integration

MSE 7123.7Product Verification

MSE 7123.8Product Validation

MSE 7123.9Product Transition

MSF

C D

evel

op

men

t &

Imp

lem

enta

tion

14


www.nasa.gov

Content Structure

15

MSF

C D

evel

op

men

t &

Imp

lem

enta

tion MWI 7123.1 MSE 7123.1

MSE Process

NASA SE Engine

1 MSE for each of the 17 SE Processes

MWI Groups the 17 SE Processes

MSE 7123.2

MSE Process

MSE Primary ContentProcess Overview

Process Objectives

Process Metrics

Points to ToolboxesSpecific Practice (steps) (including R&R)

Templates

Checklists

• MWI 7123.1 will contain information common to all MSEs

• MSEs set the standards for complying with NPR 7123.1 requirements

• Process metrics to allow for continuous improvement

• Specific Practices will contain recommended implementation guidance

• Augmented by toolbox containing templates & checklists

• Format allows for seamless import into SEG


www.nasa.gov

(1) Perform Literature Search

(2) Develop Process Flow

(3) Review Process Flow

(4) Review with Stakeholders

(5) Develop Document

Collect and outline industry and SE discipline best practices.

Develop top-level data flow for the MSE and IDEF0 for the Specific Practices.

Internal review of proposed process flow.

Coordinated effort to obtain stakeholder buy-in on how MSFC is going to proceed in doing business

Develop detailed content for the MSE and Specific Practices.

(6) Develop Toolbox

(7) Conduct Mgmt Inspection of Doc

(8) Finalize Document

(9) Implement into SEG

(10) Submit Doc for Formal Release

Develop the associated Templates and Checklists (artifacts)

Conduct internal review within ED10 and applicable stakeholders (e.g., a pre-established review team of SMEs to review and provide comments on each MSE before finalizing

Incorporate Review Team comments

Post and make content available to MSFC programs & projects

Update SEG, as required

MSFC Procedure

16

MSF

C D

evel

op

men

t &

Imp

lem

enta

tion


www.nasa.gov

MSFC Systems Engineering Framework

17

MSF

C D

evel

op

men

t &

Imp

lem

enta

tion Process Tools Training People Time

Agency NPR’sNID’s, etc.

NENMBSE

APPELNPR Training

Human CapitalStrategy &

Investments

National VisionMission NeedsAgency Goals

Mar

shal

l Inc

MSFC Enterprise

DCB, DGAProcesses

RID, ICEAPPEL

UAH, etc.CMS

Center StaffCenter Goals &

Missions Objectives

SMASafety/Reliability St

andardsQuality Standards

ARM/IRMA (Risk)Reliability & Other Analytical Tools

SMA Specialty Courses

Integrated Staff w/in

Programs/ProjectsProduct Life-Cycle

Programs/Projects

7120 ProcessesARM/IRMA (Risk)

ScheduleEVM

APPEL Project Offices Product Lifecycle

Engineering 712317 Processes

SEG, Cradle,DOORS

SE Leader Development

ProgramAPPEL

Engineering Directorate

System Lifecycle

DesignDomain Processes

(Bluebook)CAD/Pro-E, EMC,

MAT LabCDMS, Thermal

APPELLine EngineersLab Personnel

Major Milestones

Across Centers


www.nasa.gov

Achieving Common GoalsWhere Are We? (Continued)

• Establish MOU Between GRC and MSFC Focused at Developing “Common” Center Level Procedures

• Benefits of the Collaborative Effort Between GRC and MSFC– Establishing common terminology and definitions– Consistency in process steps leading to product and design

solutions with tighter integration – Consistency in templates and checklists leading to less time

to translate between common products – Better understanding of process interrelationships, leading to

more efficient analysis of inputs and outputs that support other teams

– Consistency in the quality of work products or artifacts– Better understanding of each centers’ governance processes

and associated roles & responsibilities

18


www.nasa.gov

Achieving Common GoalsWhere Are We? (Continued)

• Specific Goals and Objectives of the Collaboration:

– Review of current development processes – Share development processes and tools– Provide access to or make center procedural requirement

documents available– Create a common Project Asset Repository– Participate in each other’s peer reviews– Participate in each other’s procedural formal inspections– Co-develop (and delivery) training, communication,

continuous improvement and plans

19


www.nasa.gov

Achieving Common GoalsWhere Do We Want To Be?

• Institute a Holistic, Systems Approach to Develop Procedures and Processes within NASA– Gain Consensus Between Multiple Centers to Accomplish

Common Goals– Build Sponsorship from the Respective Engineering

Directorates– Leverage the Collective Intellect Across NASA– Common workforce development strategies for Systems

Engineering

• Define, Develop and Maintain Consistent Capabilities and Competencies Across NASA

• Provide Process to NASA Enterprise Architecture

20

Key to Fostering Future Collaborative Programs/Projects between NASA Centers


www.nasa.gov 21

Questions


www.nasa.gov 22

Back Up


www.nasa.gov 23


www.nasa.gov

Iterative Nature of MSFC System Design Process

24

MSE 7123.4

Design Solutions Definition

MSE 7123.3

Logical Decomposition

MSE 7123.1

Stakeholder Expectations

Definition

(1.2) Identify Later MSE 7123.3 Process Artifact (Output)

Technical Requirements

Definition

Allocated Reqs

Derived Reqs

MSE 7123.2

(2.2) Use insight from Later MSE 7123.3 Artifact (as Input) to Update Earlier Artifacts

Itera

te(3.1) Updated Earlier Artifacts Drives Updates to Later Artifacts

Typical Artifacts• Stakeholder

Expectations• MOEs• ConOps• Context Diagram• Design Reference

Mission• Mission Phase / Sub-

Phases• Operational Scenarios• States & Modes• Enabling Product

Support Strategies

Typical Artifacts• Physical Architecture

(top level showing Context Diagram)

• Functional Architecture (top level)

• Operational Architecture (complete)

• MOPs• TPMs• Technical Requirements

(top level)

Typical Artifacts• Physical Architecture

(decomposed-complete)• Functional Architecture

(decomposed-complete)• Derived Technical

Requirements (decomposed - lower levels)

Typical Artifacts• System-Specified

Requirements• End-Product-Specified

Requirements• Initial Subsystem

Specification• Enabling Product

Requirements• Product Verification Plan• Product Validation Plan• Logistics and Operate

To Procedures





(3.2a) Updated Earlier Artifacts Drives Updates to Later Artifacts

(3.2b) Updated Earlier Artifacts Drives Updates to Later Artifacts

Itera

te

Itera

te

Technology

Phillip.hall