OME_Management_white_paper.pdf

OME Project Management White Paper Crew and Service Module Office

5-29-2019

SUITABLE for Public Release

OME Project Management White Paper

Table of Contents

1.0 Background

2.0 Purpose

3.0 Management

3.1 OME Contractor Roles and Responsibilities

3.2 OME Project

3.3 External OME Project Stakeholders

4.0 OME Change Authority

5.0 Business Rhythm

1 | P a g e

1.0 Background

The Orion OME Project will develop, design and qualify a new Orion Main Engine (OME) for Exploration Mission 6. The OME will be delivered to the European Space Agency (ESA) to be integrated into the European Service Module (ESM). EM-1 through EM-5 will fly repurposed Space Shuttle Orbital Maneuvering System Engine (OMS-E).

2.0 Purpose

The purpose of this paper is to augment the MPCV 72008, MPCV Program Plan providing industry insight into MPCV’s management plan for the OME Contractor.

3.0 Management

NASA Plans to manage the OME Project and Contract differently than a traditional NASA Project. The OME project will minimize oversight while focusing on the successful acceptance and certification of a safe and reliable engine that integrates into the current Orion vehicle design. NASA will rely on a cooperative, robust and risk balanced insight model to inform milestone review and certification criteria.

The OME Project will reside under the Crew and Service Module Office or Control Account Manager (CAM). The OME Project consists of personnel required to manage the OME technical, cost and schedule throughout the life of the Project. The OME Project Manager reports directly to the CSM CAM.

The NASA CSM OME Project is the single principal interface to the OME Contractor, which establishes the contract and technical direction path forward. The intent of this organization is to minimize the number of external organization interfaces with NASA and minimizes OME Contractor integration costs.

The NASA OME Project will bridge the gap between the Orion traditional System Engineering process and the OME Contractor. The NASA OME Project will coordinate and integrate with the existing Orion System Manager, Specialty Engineering workforce as Subject Matter Experts on requirements, design and standards.

3.1 OME Contractor Roles and Responsibilities

The J-3 is the official place for a complete contractor responsibility listing, but the intent of this section provides a high-level summary. The OME Contractor will be responsible to provide Program Management, System Engineering & Integration, SR&QA as it relates to the Orion Main Engine. The OME Contractor will be responsible for the entire design, development, qualification and delivery of the OME. In addition, the OME Contractor will provide support during OME installation and integration, ground operations and in-flight operations.

Due to reduced Oversight on the OME Project, throughout the entire phase of the project it is the contractor’s role to enable NASA insight into issues that may impact requirements or design and test of a safe and reliable engine. It is important for the contractor to identify risks early and throughout the Project. This will enable the OME Project and Orion Management to evaluate and possibly buy-off on early risk acceptance. NASA would like to retain a greater level of insight of development efforts regarding combustion stability and injector performance, isolation valve design, and external interfaces, which are considered high risk areas.

2 | P a g e

3.2 OME Project

The intent of the NASA OME Project is to run a lean and efficient team. The OME Project will consist of the following members to interface with the OME Contractor and the rest of the Orion Program:

• OME Project Manager

• OME Systems Engineering Lead

• OME Chief Engineer

• OME Safety Lead

• OME External Integration

The OME Project Organizational structure & WBS is depicted in Figure 1.

Figure 1. OME Project Organizational Structure & WBS

3.3 External OME Project Stakeholders

Although the primary communication path is through the OME Project, as cited in the J-3, there are instances when the OME Contractor will need to attend and support ESA Integration Office, Orion Prime Contractor and ESA Contractor meetings. The interaction with external stakeholders will support the needs of ESM Integration, Ground and Flight Operations. Unplanned interfacing with external

3 | P a g e stakeholders will take place when changes, non-conformances or anomalies affects PTRS requirements, ESM or Integrated Spacecraft, depicted in Figure 2.

Figure 2 OME Project External Coordination

4.0 OME Change Authority

The NASA OME Project is responsible for maintaining the technical, cost and schedules changes. The technical baseline reflects the design as specified by the MPCV 72634, MPCV OME PTRS. All product descriptions and deliveries delivered per the J-X. In Table 1, there are a list of examples where NASA maintains change authority and decision ownership.

Examples of Decisions Requiring NASA Approval NASA

OME

Project

NASA

Board

1 PTRS Requirement (Include interface requirements) updates, deviations or waivers

2 Design requirements or changes impacting PTRS requirements, OME external interfaces, SM Performance or Spacecraft Performance

4 Hardware non-conformances that meet PMRB criteria in CxP 70059 ● ●

4 | P a g e

5 Investigation and resolution of non-conformances and anomalies that impact PTRS

6 Hazard Reports, FMEA/CIL, per DRD Schedule ● 7 OME Test and Verification Plan, per DRD Schedule ● 8 Qual/Acceptance Test Plans, per DRD Schedule ● 9 OME Test Requirements or procedure updates for activities during ESM

Installation and testing, O&C testing and operations and following handover to EGS

10 Decisions outside of OME Technical Scope and Cost ● ● 11 Schedules Changes to contractual negotiated dates ● ●

Table 1 Decision Authority Examples

5.0 Business Rhythm

On a weekly basis, the OME Contractor will participate in a weekly tag-up with the NASA OME Project to discuss weekly accomplishments, technical, cost and schedule issues and preparations for next milestone. During hardware production, the OME Contractor will provide insight to production issues and insight into any MRBs conducted.

A Board Meeting, Co-Chaired by NASA and OME to approve change examples listed in Section 4.0, Change Authority. Topic dependent, some Board Meetings, may require ESA and Orion Prime Contractor members. The Contractor will present briefings on the requested change or hardware non-conformance. Changes to the OME PTRS will controlled and approved at this meeting.

An OME Monthly Review (OMR) between the NASA and Contractor Project will compile and review OME Project technical, cost and schedule performance. During this meeting, the contractor will provide a updated technical, cost and schedule risk, threats and opportunities. Data from this forum will be provided to the CSM CAM. Every quarter, EVM information will be reviewed in the same meeting.

As needed, for issues or other general vehicle level integration, the OME contractor will need to support external integration meetings on the average of 6 hours per month until the end of production.

5 | P a g e

Accessibility Report

Filename:

OME Management white paper.pdf

Report created by:

Organization:

[Enter personal and organization information through the Preferences > Identity dialog.]

Summary

The checker found problems which may prevent the document from being fully accessible.

Needs manual check: 0

Passed manually: 2

Failed manually: 0

Skipped: 1

Passed: 26

Failed: 3

Detailed Report

Document

Rule Name Status Description

Accessibility permission flag Passed Accessibility permission flag must be set

Image-only PDF Passed Document is not image-only PDF

Tagged PDF Passed Document is tagged PDF

Logical Reading Order Passed manually Document structure provides a logical reading order

Primary language Passed Text language is specified

Title Passed Document title is showing in title bar

Bookmarks Passed Bookmarks are present in large documents

Color contrast Passed manually Document has appropriate color contrast

Page Content

Rule Name Status Description

Tagged content Passed All page content is tagged

Tagged annotations Failed All annotations are tagged

Tab order Passed Tab order is consistent with structure order

Character encoding Passed Reliable character encoding is provided

Tagged multimedia Passed All multimedia objects are tagged

Screen flicker Passed Page will not cause screen flicker

Scripts Passed No inaccessible scripts

Timed responses Passed Page does not require timed responses

Navigation links Passed Navigation links are not repetitive

Forms

Rule Name Status Description

Tagged form fields Passed All form fields are tagged

Field descriptions Passed All form fields have description

Alternate Text

Rule Name Status Description

Figures alternate text Passed Figures require alternate text

Nested alternate text Passed Alternate text that will never be read

Associated with content Passed Alternate text must be associated with some content

Hides annotation Passed Alternate text should not hide annotation

Other elements alternate text Failed Other elements that require alternate text

Tables

Rule Name Status Description

Rows Passed TR must be a child of Table, THead, TBody, or TFoot

TH and TD Passed TH and TD must be children of TR

Headers Failed Tables should have headers

Regularity Passed Tables must contain the same number of columns in each row and rows in each column

Summary Skipped Tables must have a summary

Lists

Rule Name Status Description

List items Passed LI must be a child of L

Lbl and LBody Passed Lbl and LBody must be children of LI

Headings

Rule Name Status Description

Appropriate nesting Passed Appropriate nesting

Back to Top