80JSC020R0031 SF30 Amendment 3.pdf

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing items 8 and 15, and returning or (c) By separate letter or electronic communication which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

E. IMPORTANT: Contractor is not is required to sign this document and return copies to the issuing office.

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. CONTRACT ID CODE

2. AMENDMENT/MODIFICATION NUMBER 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQUISITION NUMBER 5. PROJECT NUMBER (If applicable)

7. ADMINISTERED BY (If other than Item 6) CODE

STANDARD FORM 30 (REV. 11/2016)

Prescribed by GSA FAR (48 CFR) 53.243

FACILITY CODE

9A. AMENDMENT OF SOLICITATION NUMBER

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NUMBER

10B. DATED (SEE ITEM 13)

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers is extended. is not extended.

12. ACCOUNTING AND APPROPRIATION DATA (If required) copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NUMBER AS DESCRIBED IN ITEM 14.

CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER

NUMBER IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation data, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

15C. DATE SIGNED

15A. NAME AND TITLE OF SIGNER (Type or print)

16C. DATE SIGNED

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

PAGE OF PAGES

6. ISSUED BY CODE

8. NAME AND ADDRESS OF CONTRACTOR (Number, street, county, State and ZIP Code) (X)

CODE

15B. CONTRACTOR/OFFEROR

(Signature of person authorized to sign)

16B. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

Previous edition unusable

Ashley H. Chaves

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

The purpose of this amendment is to further clarify the definition of "storage facility" shall be in accordance with SAE AS9100, Quality Management Systems – Requirements for Aviation, Space, and Defense Organizations, not a "bonded storage warehouse" as defined in Title 19, United States Code (U.S.C.), Section 1555. As a result of this clarification, Section B Clause CLIN 0004 OME STORAGE and Attachment J-1, Performance Work Statement, Section 2.4. OME STORAGE (CLIN 0004) has been changed from "Bonded Storage Facility" to "Storage Facility". See the following pages for the updated documents.

All other terms, conditions, and provisions remain unchanged.

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

NASA Johnson Space Center 2101 NASA Parkway Houston TX 77058-3696

80JSC020R0031

1 59

See Block 16C

03/19/2020

4/29/2020

80JSC020R0031

B-5

CLIN 0004 OME STORAGE

In accordance with Attachment J-1, Performance Work Statement, the task ordering procedures and other terms and conditions in the contract, the Contractor shall provide a storage facility in accordance with SAE AS9100, Quality Management Systems – Requirements for Aviation, Space, and Defense Organizations, as initiated by written direction from the Contracting Officer.

Storage facility space under CLIN 0004 will be procured via a FFP task order. No later than 30 calendar days prior to Milestone 2, Pre-Ship Hardware Acceptance Review, NASA will notify the contractor if storage is required. NASA reserves the right to determine, on an as needed basis, if there is a need for the OME(s) to be stored. If it is determined that additional days are required to store the OME prior to DD Form 250 date, the appropriate contract year storage price per day will be multiplied by the number of days of storage needed times the number of engines.

A subsequent amendment to the FFP task order will be executed.

OME Storage CY

CY

CY

CY

CY

CY

CY

CY

Storage Price per day OFI OFI OFI OFI OFI OFI OFI OFI

(End of Clause)

ATTACHMENT J-1

April 23, 2020

PERFORMANCE WORK

STATEMENT

Attachment J-1

Table of Contents

1. INTRODUCTION

2. CONTRACT STRUCTURE

2.1. OME CERTIFICATION (CONTRACT LINE ITEM NUMBER (CLIN 0001)

2.2. OME PRODUCTION (CLIN 0002)

2.3. SPECIAL TASKS AND STUDIES (CLIN 0003)

2.4. OME STORAGE (CLIN 0004)

3. RESERVED

4. PROJECT MANAGEMENT, SYSTEMS, PLANNING AND REPORTING

4.1. PROJECT MANAGEMENT PLAN

4.2. EXTERNAL RELATIONSHIPS: ESA AND ESA RELATED ENTITIES

4.3. INSIGHT/OVERSIGHT IMPLEMENTATION

4.4. INTEGRATED SCHEDULE MANAGEMENT

4.5. RESERVED

4.6. INFORMATION TECHNOLOGY SECURITY MANAGEMENT

4.6.1. INFORMATION TECHNOLOGY MANAGEMENT

4.6.2. INFORMATION TECHNOLOGY (IT) SECURITY MANAGEMENT PROJECT COMPLIANCE

4.6.2.1. IT SECURITY PROJECT MANAGEMENT PLAN

4.6.2.2. IT SECURITY PLAN

4.6.2.3. EMPLOYEE IT SECURITY AWARENESS TRAINING

4.6.2.4. IT SECURITY ROLE-BASED TRAINING

4.6.2.5. INFORMATION ON EMPLOYEES IN SENSITIVE POSITIONS/ASSIGNMENTS REPORTS

4.6.2.6. INTERNAL IT SECURITY PLAN AUDITS

4.6.2.7. IT SECURITY POINT-OF-CONTACT

4.6.2.8. IT CERTIFICATION AND ACCREDITATION

4.6.2.9. WIRELESS LOCAL AREA NETWORKS

4.7. RESERVED

4.8. RESERVED

4.9. CONFIGURATION MANAGEMENT

4.10. DATA MANAGEMENT

4.11. RISK MANAGEMENT

4.12. BUSINESS MANAGEMENT

5. OME INTEGRATION MANAGEMENT

5.1. MASTER VERIFICATION PLAN

5.2. FRACTURE CONTROL

5.3. ELECTRICAL, ELECTRONIC, AND ELECTROMECHANICAL PARTS MANAGEMENT

5.4. OME DESIGN DATABOOK

5.5. MODELS, SIMULATIONS, AND INTEGRATED SUPPORT PLAN

5.6. OME STRESS ANALYSIS REPORTS

5.7. ALTERNATE STANDARDS

6. ENGINE INTEGRATION SERVICES

7. OME CERTIFICATION AND ENGINE PRODUCTION MANAGEMENT

7.1. OME CERTIFICATION MANAGEMENT

7.2. PRODUCTION MANAGEMENT

8. FORMAL MEETINGS AND REVIEWS

8.1. MEETINGS

8.1.1. OME QUARTERLY PROJECT MEETINGS

8.1.2. OME WEEKLY WORKING MEETINGS

8.1.3. OME WEEKLY INTEGRATION WORKING GROUP MEETINGS

8.2. TECHNICAL MILESTONE REVIEWS (OME CERTIFICATION)

8.2.1. CERTIFICATION MILESTONE 1 - SRR

8.2.2. CERTIFCATION MILESTONE 2 - PDR

8.2.3. CERTIFICATION MILESTONE 3 - CDR

8.2.4. CERTIFICATION MILESTONE 4 - DCR

8.3. TECHNICAL MILESTONE REVIEWS (OME PRODUCTION - DELIVERY)

8.3.1. PRODUCTION MILESTONE 1A – PRR #1

8.3.2. PRODUCTION MILESTONE 1B – PRR #2

8.3.3. PRODUCTION MILESTONE 2 – PRE-SHIP HAR

8.3.4. PRODUCTION MILESTONE 3 – POST-SHIP HAR

9. OME SYSTEMS ENGINEERING AND INTEGRATION

9.1. SYSTEM ENGINEERING & INTEGRATION MANAGEMENT AND ADMINISTRATION

9.2. REQUIREMENTS DEFINITION AND MANAGEMENT

9.3. INTEGRATION AND INTERFACES MANAGEMENT

9.4. OME INTEGRATED ANALYSIS

9.5. SPECIALTY ENGINEERING

9.5.1. NATURAL AND INDUCED ENVIRONMENTS

9.5.2. MICROMETEOROID AND ORBITAL DEBRIS ENVIRONMENTS

9.5.3. MATERIALS AND PROCESSES

9.5.4. ELECTRO-MAGNETIC INTERFERENCE/ELECTRO-MAGNETIC INTERFERENCE

9.5.5. EEE PARTS

10. SAFETY AND MISSION ASSURANCE

10.1. S&MA MANAGEMENT AND ADMINISTRATION

10.2. SYSTEM SAFETY

10.3. SAFETY AND HEALTH

10.4. RELIABILITY AND MAINTAINABILITY

10.5. HARDWARE QUALITY ASSURANCE

11. ORION MAIN ENGINE DESIGN, DEVELOPMENT, PRODUCTION AND SUSTAINING

ENGINEERING

11.1. ENGINE DEVELOPMENT, ASSEMBLY, AND TEST

11.2. OME TEST AND VERIFICATION

11.2.1. OME VERIFICATION MANAGEMENT

11.2.2. OME HARDWARE CERTIFICATION TESTING

11.2.3. OME INTEGRATED TESTING WITH AVIONICS, POWER AND SOFTWARE

11.3. OME ASSEMBLY INTEGRATION AND PRODUCTION

11.4. OME SUSTAINING ENGINEERING

12. OME OPERATIONS

12.1. FLIGHT OPERATIONS

12.1.1. FLIGHT OPERATIONS PREPARATION AND EXECUTION

12.1.2. TRAINING

12.2. OME GROUND OPERATIONS

12.2.1. GROUND OPERATIONS PREPARATION AND EXECUTION

12.2.2. GROUND STORAGE

12.2.3. HANDLING AND TRANSPORTATION

12.2.4. FACILITIES AND FACILITY SYSTEMS

13. OME GROUND SYSTEMS SUPPORT EQUIPMENT

1. INTRODUCTION

This Performance Work Statement (PWS) and all exhibits and documents attached or referenced herein define the National Aeronautics and Space Administration (NASA) requirements for the Contractor to provide the Orion Main Engine (OME) that will replace the

Orion Multi-Purpose Crew Vehicle (MPCV) Orbital Maneuvering System-Engine that was repurposed to support the Orion spacecraft on Artemis I through Artemis V. The OME

Contractor will be responsible for ensuring the OME meets the European Service Module

(ESM) interfaces and that required ground support equipment is provided to integrate the OME into the ESM.

The OME shall be integrated into the European Space Agency (ESA) supplied ESMs, which will constrain the OME within the existing ESM interface, performance, and functional requirements. The OME will be disposed of after each mission and will be designed, developed, built, and certified for flight consistent with NASA and MPCV/ESM program design, construction, workmanship, qualification standards, and other technical and programmatic requirements associated with human rating considerations. This includes configuration management, reliability analysis, and safety assessment processes. NASA will consider use of the OME Contractor company and/or industry standards so long a NASA agrees that these company and/or industry standards meet the intent of the standards contained in Attachment J-3, Applicable, Meet the Intent, Informational, and Tailored Documents List, as meet-the-intent documents.

NASA will provide access to detailed design information for components associated with

OME to fulfill this PWS as defined in the clause entitled USE OF GOVERNMENT

PROPERTY, FACILITIES, ASSETS, OR SERVICES. This includes hardware drawings, acceptance test procedures, test equipment designs, and data for the contractor’s use in procuring these items. The Contractor shall perform all tasks necessary to ensure the delivery of safe reliable engines.

The Contractor shall provide the necessary services, test hardware and software, and engine specific elements required to certify, produce, and deliver the OME.

2. CONTRACT STRUCTURE

2.1. OME CERTIFICATION (CONTRACT LINE ITEM NUMBER (CLIN 0001)

The Contractor shall perform design, development, test, and evaluation (DDT&E) activities and provide the required data for certification of the OME for both the baseline schedule certification date in SUB CLIN 0001a and the accelerated schedule certification date in SUB CLIN 0001b. The Contractor shall be responsible for the following four aspects of OME certification for both the baseline and accelerated certification dates:

a. Design – The design activities will consist of a series of NASA mandatory interim reviews to include a System Requirements Review (SRR), a Preliminary Design

Review (PDR), a Critical Design Review (CDR), a Design Certification Review

(DCR), and Contractor proposed and approved milestone reviews. Design

Analysis Cycles and a Verification Analysis Cycle should be aligned to support these technical reviews.

b. Engineering Development Unit (EDU) components that will be assembled into an

EDU OME that will be hot fired to validate the functional and performance requirements of the engine. As a risk mitigation for the OME qualification test, qualification level environmental testing on the EDU components shall be conducted to inform the development of the qualification engine.

c. Qualification – Qualification activities shall consist of the procurement, buildup, and testing of the qualification engine components and fully assemble engine.

Engine level environmental testing to qualification levels and a hot-fire test shall be performed.

d. Certification – Certification activities shall consist of the DCR leading to final certification of the engine design and associated support equipment.

Work associated with OME Certification (CLIN 0001) includes the work required to support the NASA mandatory interim reviews (SRR, PDR, CDR, and DCR), the

Contractor proposed and approved milestone reviews, and the associated data deliverables defined in Attachment J-2, Data Procurement Document, and delivered per Attachment

J-2-A, DRD Submission Matrix, for the Submission Events of SRR, PDR, CDR, DCR, and any required updates.

2.2. OME Production (CLIN 0002)

The Contractor shall perform production activities and provide the required data for

Government review and subsequent transfer of property accountability to NASA for both the baseline need dates in Attachment L-9a, OME Baseline Need Dates, SUB CLIN 0002a and accelerated need dates in Attachment L-9b, OME Accelerated Need Dates, SUB CLIN

0002b. The Contractor shall be responsible for the following four aspects of OME production for both the baseline and accelerated need dates:

a. Production Reviews - After authority to proceed for the production engines, a

Production Readiness Review (PRR) will be held to ensure any changes to the

OME design are incorporated and that the OME Contractor is ready to proceed with production. DDT&E will run concurrent with production and will require the start of the first production lot shortly after PDR. An initial PRR (PRR#1) shall be held concurrent with PDR to give an authority to proceed with production long-lead procurements and then a final PRR (PRR#2) shall be held concurrent with

CDR to give an authority to proceed with full production. For the accelerated schedule, the Contractor shall conduct both a PRR#1 and a PRR#2 for the second production lot. For future lot buys, only a single PRR shall be held that combines the entrance and accomplishment criteria of PRR#1 and PRR#2.

b. Acceptance Test – The OME Contractor shall perform an acceptance test on each engine. Engine level environmental testing to acceptance levels and a hot-fire test shall be performed. Then the engine shall be decontaminated in preparation for shipment to the ESM integration site.

c. Pre-Ship Hardware Acceptance Review – After successful acceptance testing, a

Hardware Acceptance Review (HAR) will be conducted. This Pre-Ship HAR will act as preliminary HAR in order for the Government to understand the scope of any open work both prior to shipment and leading up to the Post-Ship Hardware

Acceptance Review. This Pre-Ship HAR will also serve as a Pre-Ship or Storage

Review for the engine depending whether it will be shipped right away or will be stored for later shipment.

d. Post-Ship HAR – The scope of this review is twofold,

1. Disposition any and all open work documented in the Pre-Ship HAR and any new open work documented since the Pre-Ship HAR, and

2. Review the OME receiving inspection results after the hardware is received at the ESM integration site.

If the engine was in storage, then a Pre-ship Review shall be held prior to shipment.

After successful completion of the Post-Ship HAR, the OME and associated property will be transferred to NASA via a DD Form 250.

For the first four flown missions, a Post-Flight Assessment Review (PFAR) shall be submitted per Attachment J-2, Data Procurement Document, and delivered per

Attachment J-2-A, DRD Submission Matrix.

Work associated with OME Production (CLIN 0002) includes the work required to support the NASA mandatory interim reviews and reports (PRRs #1, PRRs #2, Pre-Ship

HARs, and Post-Ship HARs), the Contractor proposed and approved milestone reviews, and the associated data deliverables defined in Attachment J-2, Data Procurement

Document, and delivered per Attachment J-2-A, DRD Submission Matrix, for the

Submission Events of PRR #1, PRR #2, Pre-Ship HAR, Post-Ship HAR, and any required updates.

Work associated with OME Production (CLIN 0002) also includes the post-delivery (DD

Form 250) Operations Preparation and Execution support defined in PWS section 12.2.1 and the Flight Operations support defined in PWS section 12.1.1.

2.3. SPECIAL TASKS AND STUDIES (CLIN 0003)

The Contractor shall perform special studies and analyses, provide materials, and fabricate incidental hardware in support of this contract. These tasks include advance planning and feasibility studies in support of future contemplated engines; development, fabrication, and test of hardware/software to support planning studies or special tests; engine unique studies; providing or supplying materials (parts and components); preparing the OME

Post-Flight Performance Reconstruction Analysis Report and conducting the OME Post-

Flight Assessment Review; and implementation of changes required due to changes in requirements.

2.4. OME STORAGE (CLIN 0004)

In the event NASA delays the OME on-dock delivery date to the ESM integration site, or the engine is ready to ship prior to the delivery date, the contractor shall arrange a storage facility in accordance with SAE AS9100, Quality Management Systems – Requirements for Aviation, Space, and Defense Organizations. This effort shall include both electronic and paper document control, maintenance of OME, and control of secure physical access.

The contractor shall perform inventory control validation and record keeping for OME certified hardware in accordance with SAE AS9100 standards, and assure all OME procedures for quality control testing are adhered to.

The Contracting Officer shall notify the Contractor in writing 60 days in advance of planned on-dock delivery date with an updated delivery date as required. The OME storage requirements will be procured via FFP task order. NASA reserves the right to determine, on an as needed basis, if there is a need to procure storage facilities using CLIN

0004. If it is determined that the on-dock delivery date will be extended, the appropriate tier will be selected and both parties agree, a subsequent amendment to the FFP task order will be executed.

3. RESERVED

4. PROJECT MANAGEMENT, SYSTEMS, PLANNING AND REPORTING

Project Management includes development, implementation and maintenance of common

Project management processes, systems and data deliverables to be utilized throughout the life of the contract.

4.1. PROJECT MANAGEMENT PLAN

The Contractor shall establish an organizational structure for the management, coordination, and control of contract activities including the Project’s cost, schedule, performance, risks, contracts, and subcontracts using as guidance ISO 14300-1, Space

Systems - Project Management - Part 1: Structuring of a Project.

The Contractor shall develop and implement the Orion Main Engine Project Management

Plan, DRD OME-M-001, which covers all aspects of Project management for the Orion

OME Project including approaches for Government insight/oversight and integrated logistics. The MPCV 72008, Orion Multi-Purpose Crew Vehicle (MPCV) Program Plan provides information to help the contractor formulate the Project Management Plan.

The Contractor shall provide all program management functions required to deliver the

OME to satisfy the engine requirements for each Artemis mission. The program management function of this contract shall provide insight to NASA for technical and programmatic activities performed under this contract.

The Contractor shall develop, maintain and implement a process to verify engine readiness. This auditable approach shall verify that all engine preparation responsibilities and requirements have been met and that all problems have been dispositioned prior to delivery. Prior to each property transfer of accountability to the Government via a DD

Form 250, the Contractor shall certify engine readiness per the Pre-Ship and Post-Ship

HARs.

Deliverables

DRD OME-M-001, Orion Main Engine Project Management Plan

4.2. EXTERNAL RELATIONSHIPS: ESA AND ESA RELATED ENTITIES

The Contractor shall establish cooperative relationships with ESA and ESA related entities to support the implementing arrangement between NASA and ESA for the development of the ESM.

The Contractor shall perform technical interactions with ESA and ESA related entities that are necessary for exchange of data, hardware, and software.

For the export of hardware, software, and data, the contractor shall comply with the United

States export control regulations:

International Traffic in Arms Regulations, Title 22 Foreign Relations, Volume 1, Chapter 1, Parts 120-130, and

Export Administration Regulations, Title 15 Commerce and Foreign Trade, Volume 1, Subtitle B, Chapter VII, Subchapter C, Part 730-774.

It shall be the responsibility of the Contractor to seek and obtain Technical Assistance

Agreements (TAAs) for technical interactions with any international partners as required.

The Contractor shall provide a copy of the approved TAA to the NASA Contracting

Officer upon TAA final approval.

For the export of hardware, NASA will be responsible for obtaining the export licenses for OME shipments.

4.3. INSIGHT/OVERSIGHT IMPLEMENTATION

The Contractor shall establish a partnership and working relationship between the

Government and the Contractor, and the level of insight/oversight the Government will have into the Contractor activities in accordance with DRD OME-M-001, Orion Main

Engine Project Management Plan.

Deliverable

4.4. INTEGRATED SCHEDULE MANAGEMENT

The Contractor shall develop, maintain, and provide NASA access to an OME Integrated

Master Schedule (IMS) in accordance with DRD OME-M-002, Integrated Master

Schedule (IMS) and Schedule Deliverables.

Deliverable

DRD OME-M-002, Integrated Master Schedule (IMS) and Schedule Deliverables

4.5. RESERVED

4.6. INFORMATION TECHNOLOGY SECURITY MANAGEMENT

The Contractor shall protect the integrity, availability, and confidentiality of the information resources transiting the interface between the Contractor, NASA, ESA, and

ESA’s Contractor. The Contractor shall perform the following aspects of Information

Technology (IT) Security Management.

4.6.1. INFORMATION TECHNOLOGY MANAGEMENT

The NASA Integrated Collaborative Environment (ICE) is the primary means of sharing, reporting, collecting, recording, and accessing Project information between NASA, the OME Contractor, subcontractors and authorized Government personnel connected with the Orion Program. ICE provides secure, real-time collaborative access to a single source of management information, product information, and technical data. ICE is the principal mechanism for integrating a project's digital information management environment.

The Contractor shall use ICE for delivery of all data unless data is defined as make-available.

The Contractor shall use the interactive collaborative configuration management and document management environments of ICE for configuration management of

Orion MPCV Program directives and change control activities.

The Contractor shall comply with Attachment J-14, ICE Operating Environment.

The Contractor’s collaborative environment shall be available within 30 days of contract award.

The Contractor’s collaborative environment shall be updated with the Type 4 data requirement deliverables per Attachment J-2, Data Procurement Document and any other data required to be made available in this PWS.

The Contractor shall transmit non-data requirement deliverable information, such as week-to-week coordination, working level analysis, action item responses, etc., via a contractor-established data sharing system.

4.6.2. INFORMATION TECHNOLOGY (IT) SECURITY MANAGEMENT

PROJECT COMPLIANCE

Contractors who purchase, lease, network to, or otherwise utilize Government-funded IT (Clinger-Cohen Act of 1996 and referenced by Office of Management and Budget (OMB) Circular A-130, Managing Information as a Strategic

Resource) shall comply with NPR 2810.1A, Security of Information Technology.

4.6.2.1. IT SECURITY PROJECT MANAGEMENT PLAN

The Contractor shall submit DRD OME-M-004, Information Technology

Security Management Project Plan for its unclassified IT resources. The

Contractor’s IT Security Management Project Plan shall be compliant with

Federal and NASA policies as referenced in OMB Circular A-130, Managing

Information as a Strategic Resource and NPR 2810.1, Security of Information

Technology.

4.6.2.2. IT SECURITY PLAN

The Contractor shall have an Information Systems Security Officer (ISSO) who is responsible for the Contractor’s system(s) in accordance with the definitions set forth in NPR 2810.1A, Security of Information Technology.

4.6.2.3. EMPLOYEE IT SECURITY AWARENESS TRAINING

Contractor employees performing work under this contract shall complete the

NASA-provided IT Security Awareness Training annually. The Government shall track completion within Systems for Administration, Training, and

Education Resources for NASA (SATERN). Completion dates are issued annually by the Government with access repeal for non-completion. The IT

Security Awareness Training is delivered via desktop workstation and takes approximately 1 hour to complete.

4.6.2.4. IT SECURITY ROLE-BASED TRAINING

Contractor employees performing work under this contract shall complete

NASA role-based training in accordance with the NASA Information Technology

Security Handbook, IT Security Awareness Training, ITS-HBK-2810.06-2B for the following roles: IT Security Manager, Information Security Officer, ISSO, and Organizational Computer Security Official Representative.

4.6.2.5. INFORMATION ON EMPLOYEES IN SENSITIVE

POSITIONS/ASSIGNMENTS REPORTS

The Contractor shall provide information reporting annually for personnel screening as required by NPR 2810.1A, Security of Information Technology, and

NPR 1600.1, NASA Security Project Procedural Requirements on position risk.

4.6.2.6. INTERNAL IT SECURITY PLAN AUDITS

The Contractor shall proactively protect sensitive data as defined by system IT

Security Plans in accordance with DRD OME-M-004, Information Technology

Security Management Project Plan.

4.6.2.7. IT SECURITY POINT-OF-CONTACT

The Contractor shall identify a point-of-contact that NASA may reach, during that point-of-contact’s normal business hours, in its attempt to address IT and IT security issues. The point-of-contact shall have the authority to ensure appropriate actions occur.

4.6.2.8. IT CERTIFICATION AND ACCREDITATION

For IT systems delivered to NASA, the contractor shall develop and deliver systems following NFS 1852.204-76, Security Requirements for Unclassified

Information Technology Resources.

4.6.2.9. WIRELESS LOCAL AREA NETWORKS

Wireless Local Area Networks (WLAN) requirements shall be applicable for systems on NASA facilities utilizing NASA wireless networks. The contractor shall meet the facility requirements for WLAN implementation.

WLAN requirements shall meet the intent of the hosting Center’s WLAN requirements for wireless systems located on a NASA facility and utilizing the

Contractor’s wireless network. WLAN requirements for wireless implementations on a contractor’s facility shall be based on the contractor’s existing policies and procedures to meet the intent of NPR 2810.1A, Security of

Information Technology.

DRD OME-M-004, Information Technology Security Management Project Plan

4.7. RESERVED

4.8. RESERVED

4.9. CONFIGURATION MANAGEMENT

The Contractor shall develop and implement Configuration Management (CM) processes and systems in accordance with DRD OME-M-001, Orion Main Engine Project

Management Plan.

The Contractor CM process and system shall use SAE EIA-649-2, Technical Report, Configuration Management Requirements for NASA Enterprises.

The Contractor shall integrate the CM system across the OME Project, including modeling and simulation, engineering drawing development and release, manufacturing, test equipment and test articles, operations, and quality, as well as acquisition organizations, including customer and vendor CM systems.

The Contractor shall implement and maintain a configuration status accounting system that provides information defining, maintaining, and reconciling the As-Designed versus

As-Built configuration of the hardware and software, including the status of changes to this configuration.

4.10. DATA MANAGEMENT

The Contractor shall develop and implement Data Management (DM) processes and systems in accordance with DRD OME-M-001, Orion Main Engine Project Management

Plan.

The Contractor DM process and systems shall use SAE GEIA859, Technical Report, Data

Management as guidance.

The Contractor’s DM process and system shall implement the following functions: (1) data identification and definition, (2) data acquisition and preparation, (3) data control, (4) data status accounting and disposition, (5) data management verification and audits, and

(6) data archiving.

The Contractor shall use the MPCV deliverables process for acceptance and release of contractor data, defined in MPCV 72523 Orion MPCV Program Configuration and Data

Management Plan.

The Contractor shall integrate the DM system across the OME Project such as modeling and simulation, engineering drawing development, manufacturing, test equipment and test articles, operations, and quality, as well as acquisition organizations including customer and vendor DM systems to successfully complete Project acceptance and Certification of

Flight.

4.11. RISK MANAGEMENT

The Contractor shall identify, evaluate, manage, and control the safety, technical, cost, and schedule-related risks associated with all aspects of the OME Project in accordance with MPCV 72091, Orion MPCV Project Integrated Risk Management Plan. Project risks will be reviewed at the OME Monthly Project Meeting. The contractor shall also status candidate risks starting at the first OME Monthly Project Meeting. These candidate risks are risks, that if accepted, will impact requirements or design and test of a safe and reliable engine.

4.12. BUSINESS MANAGEMENT

The Contractor shall provide their planned approach to small business subcontracting and their reporting against this plan per DRD OME-B-001, Small Business Subcontracting

Plan.

The contractor shall provide an Organizational Conflicts of Interest Plan in accordance with DRD OME-M-012, Organizational Conflicts of Interest (OCI) Plan.

The Contractor shall identify all third-party proprietary information per Attachment J-25, Limited Right in Data and Restricted Computer Software.

DRD OME-B-001, Small Business Subcontracting Plan

DRD OME-M-012, Organizational Conflicts of Interest (OCI) Plan

5. OME INTEGRATION MANAGEMENT

5.1. MASTER VERIFICATION PLAN

The Contractor shall specify, produce, and deliver integration testing assemblies and flight test articles necessary to develop the OME Master Test Plan in accordance with DRD

OME-T-015, Master Verification Plan (MVP).

DRD OME-T-015, Master Verification Plan (MVP)

5.2. FRACTURE CONTROL

The Contractor shall implement a fracture control program and identify fracture critical parts to protect against catastrophic structural hazards associated with flaw presence, fatigue crack propagation, and fracture.

The Contractor shall develop, implement, and maintain the Fracture Control Plan, DRD

OME-T-069, and deliver DRD OME-T-070, Fracture Control Summary Report.

DRD OME-T-069, Fracture Control Plan

DRD OME-T-070, Fracture Control Summary Report

5.3. ELECTRICAL, ELECTRONIC, AND ELECTROMECHANICAL PARTS

MANAGEMENT

The Contractor shall develop and implement an Electrical, Electronic, and

Electromechanical (EEE) parts plan that is required by MPCV 72634, Orion MPCV

Program OME PTRS.

The Contractor shall develop, implement, and maintain DRD OME-T-027, Electrical, Electronic, and Electromechanical Management and Implementation Plan, and deliver

DRD OME-T-028, As-Built EEE Parts List.

DRD OME-T-027, Electrical, Electronic, and Electromechanical Management and

Implementation Plan

DRD OME-T-028, As-Built EEE Parts List

5.4. OME DESIGN DATABOOK

The Contractor shall document the engine and component design, operational limits, significant analyses, trade studies, and developmental testing performed to determine the engine and component design in DRD OME-T-071, OME Design Databook.

The Contractor shall document the engine passive thermal design details, analysis, operational limits, trade studies, developmental testing, and data to determine the engine and component design in DRD OME-T-071, OME Design Databook.

The Contractor shall collaborate with NASA and ESA, their suppliers, and their affiliated stakeholders to ensure successful coordination of the highly integrated ESM system on interface requirements, design, verification, testing, integration, and delivery logistics.

The Contractor shall provide analysis of OME performance for transient and steady-state conditions using a suitably anchored engine performance model, for the full range of operating conditions defined in MPCV 72634, Orion MPCV Program OME PTRS.

DRD OME-T-071, OME Design Databook

5.5. MODELS, SIMULATIONS, AND INTEGRATED SUPPORT PLAN

The Contractor shall develop and deliver thermal analytical models to support integrated

Orion vehicle analyses per DRD OME-T-001, Models, Emulators/Simulators, Simulations.

The Contractor shall develop models to support integrated Orion loads and stress analyses.

The Contractor shall deliver DRD OME-T-001, Models, Emulators/Simulators, Simulations, which will deliver and describe the mathematical models used in the engine and component loads and stress analyses.

DRD OME-T-001, Models, Emulators/Simulators, Simulations

5.6. OME STRESS ANALYSIS REPORTS

The Contractor shall perform stress and fatigue analyses and document the results in DRD

OME-T-062, Stress Analysis Report.

DRD OME-T-062, Stress Analysis Report

5.7. ALTERNATE STANDARDS

The Contractor shall provide any alternate standard that will be implemented to meet the intent of the NASA standards listed in the Meet the Intent section of Attachment J-3, Applicable, Meet the Intent, Informational and Tailored Documents, and document the details in DRD OME-T-094, Alternate Standards.

The Contractor shall plan to support a meeting with the Government no later than 45 days prior to SRR to review any Government issues or concerns with the Contractor provided alternate standards submitted in Volumes I and II of DRD OME-T-094, Alternate

Standards.

DRD OME-T-094, Alternate Standards

6. ENGINE INTEGRATION SERVICES

The Contractor shall ensure the safe integration and transport of the OME to the ESM integration site. The Contractor shall put in place and support an Integration and Operations process for all OME deliveries. The Contractor shall provide integration support for

OME/ESM and perform analysis.

7. OME CERTIFICATION AND ENGINE PRODUCTION MANAGEMENT

The Contractor shall perform OME certification and engine production tasks in accordance with DRD OME-M-003, OME Work Plan.

7.1. OME CERTIFICATION MANAGEMENT

The Contractor shall provide a technical representative to work technical details for certification (design and development layout, analytical products, schedules, etc.).

The technical representative shall track development status of and resolve issues associated with Engineering Development Unit (EDU) and Qualification (QUAL) engine specific hardware and software.

The contractor shall provide input to the weekly OME integration working group meetings to successfully plan, schedule, and manage integration analyses required to define and verify compatibility with the interface requirements and environments of the

ESM.

The contractor shall manage the design, development, qualification, testing, and integration of engine unique requirements.

7.2. PRODUCTION MANAGEMENT

The contractor shall provide a production manager for each engine lot.

The production manager shall coordinate support from all technical disciplines and management during the engine production process.

The contractor shall provide a technical representative for each engine as a focal point to work technical details for each engine (engine layout, analytical products, schedules, etc.).

The technical representative shall track development status of and resolve issues associated with engine specific hardware and software.

The contractor shall continue providing inputs to the OME weekly integration working group meetings to successfully plan, schedule, and manage integration analyses required to define and verify compatibility with the interface requirements and environments of the ESM.

The contractor shall manage the design, development, acceptance, testing, and integration of engine unique requirements.

8. FORMAL MEETINGS AND REVIEWS

The intent of the formal reviews is to provide a forum for open dialog between NASA and the

OME Contractor with respect to OME certification and production.

The Contractor shall send a review invitation to the NASA OME Project Manager, who will forward to the NASA OME team as required.

The Contractor shall make available to NASA the Review Item Description/Request for Action

(RID/RFA) process at least 30 days prior to the SRR.

The Contractor shall submit a final electronic copy of the presentation material to NASA at least one (1) week before the review is held.

The Contractor shall provide minutes that include a list of attendees, agreements and action items resulting from each review to NASA within one week after the review; the payment milestone will not be considered complete until the minutes are provided and any actions identified as required to be completed for completion of the milestone are accomplished.

The Contractor shall maintain and update the action item developed during the review. The list shall include:

a. Closure Date

b. Action item description

c. Closure Plan

d. Assigned tracking number for each action item,

e. Person or organization responsible for completing the action,

f. Status of action (i.e., open, closed, or deleted).

8.1. MEETINGS

8.1.1. OME QUARTERLY PROJECT MEETINGS

During the task order performance period, the Contractor shall conduct OME Quarterly

Project Meetings (OQPMs) with NASA, beginning at task order start, to report on the topics listed below:

a. The status, closure plan and schedule for remaining OME certification and production compliance tasks, or tasks to be repeated in the event of changes to the design baseline. This shall be the focus of the meeting when tasks are open.

b. The integrated schedule and status for all engines given authority to proceed.

c. Key schedule items from other contractor or international partners activities that may affect the technical, cost and schedule risk to NASA missions, such as, but not limited to, other program milestones, mission dates of other contractors utilizing test site, etc.

d. Schedule and technical risks, including risk statements, mitigation plans and mitigation schedules.

e. Summary status of the special task assignments (under CLIN 0003) that were started, in-work, or completed since previous review.

f. Action items from previous meetings and technical reviews, including their status, closure plan, and closure rationale.

The contractor shall publish minutes within one week of the meeting and make them available on the Contractor collaborative environment.

NASA will provide status of program direction at the meetings.

These meetings are expected to last no longer than 2.0 hours.

8.1.2. OME WEEKLY WORKING MEETINGS

The contractor shall provide input to the weekly NASA OME certification and engine production working meetings through delivery of the first two engines. For subsequent engine orders, the contractor shall provide input to the bi-weekly working meeting through the life of the contract, with a focus on working technical issues, forward planning, and contractual modifications, if applicable. The frequency of the meetings may increase if time-critical issues are identified and require expedited resolution. The meeting is intended to be a technical status and not a design review or additional technical panel. The objective is to provide technical insight to engine activities and allow for early identification of risk items or changes required. These meetings are expected to last no longer than 1.5 hours per week and the Contractor shall cover the following topics:

a. Requirements

1. At risk requirements – a listing of the requirements that are at risk of having a negative margin to its requirement. The expected values are to be derived from analysis/test data at the time and could change as new data is obtained.

2. Standards Baselining Status – a status progress made to obtain mutual agreement on alternate standards.

3. Open Change Requests (CRs) – status of requirements CRs under review.

These CRs could be either applicable to OME requirements or CRs against other program level requirements that OME is reviewing for impacts.

b. Design/Analysis

1. Completed design/analysis activities/results

2. Status of in-work design/analysis activities

3. Review of upcoming scheduled analysis

c. Test

1. Completed test activities/results (test activities are all test processes such as planning, testing, reporting, issue resolution)

2. Status of in-work test activities

3. Review of upcoming scheduled test activities

d. Issues

1. Open non-conformances

2. Hardware failures or test issues

3. Contractor approved changes to baselined standards/plans. Any changes to the baselined standards or plans baselined on the contract, made at a contractor review board (such as Fracture Control Board, Contractor Material Control

Board, or EEE Parts Control Board) shall be listed along with any dissenting opinions. Any changes after baselining may require equitable adjustment of contract value.

4. Upcoming OME Safety Panel Reviews (either contractor Safety Review or

NASA Safety Panel reviews).

e. Schedule

Impacts to near term schedule from above topics

f. Actions Item Review

1. Review of new actions

2. Status of in-work actions

Meeting minutes shall be assembled by the contractor covering items discussed, a brief discussion of topic discussions, decisions/agreements made, links to meeting presentation(s), and a link to the action item list. The Contractor shall post the minutes electronically no later than three working days after the meeting is held.

8.1.3. OME WEEKLY INTEGRATION WORKING GROUP MEETINGS

The contractor shall provide input to the weekly Integration Working Group that focuses on integration of the OME with the rest of the Orion vehicle. As the engine development proceeds, and actual engine performance is established, this forum will be used as an avenue to communicate topics pertinent to the propulsion sub-system, the ESM Integration

Office, the Vehicle Integration Office, and the Safety community. The objective is to provide a forum to discuss technical subjects having potential impacts that span the engine interfaces to the rest of the spacecraft, determine actions needed to address the issues, and track those actions with the respective organization. These meetings are expected to average no longer than 2 hours per meeting, however, individual meeting lengths may vary due to the nature of the topic.

8.2. TECHNICAL MILESTONE REVIEWS (OME CERTIFICATION)

The Technical Milestone Reviews consist of the major interim milestone reviews covered in this section and OME Contractor proposed interim milestone reviews in accordance with DRD OME-M-003, Work Plans.

The certification and production milestone entrance criteria, accomplishment criteria, and applicable products are defined in the tables below. The entrance criteria are the minimum accomplishments that the OME Contractor shall fulfill prior to the respective technical milestone review. The accomplishment criteria are the specific accomplishments that the

OME Contractor shall satisfactorily demonstrate to meet the objectives of the review so that the technical effort can progress further in the life cycle. The applicable products are the deliverables that the OME Contractor shall use to verify the accomplishment criteria was met.

The Contractor shall conduct technical reviews to status the end-to-end certification of the

OME. The Contractor shall allow NASA to participate in reviews to allow NASA to assess the progress towards meeting the OME certification requirements.

The Contractor shall deliver review data packages to NASA for review per Attachment J-

2-A, DRD Submission Matrix.

Data Requirement Documents (DRDs) delivered for technical milestones reviews (SRR, PDR, CDR, and DCR) identified in Attachment J-2, Data Procurement Document, shall be reviewable documents as part of the review data package at the associated review.

8.2.1. CERTIFICATION MILESTONE 1 - SRR

The OME SRR evaluates whether the functional and performance requirements defined for the engine are responsive to the project’s requirements and ensures the preliminary project plan and requirements will satisfy the end item deliverables. The SRR shall be completed before PDR and PRR#1. Table 1 shows the entrance criteria, accomplishment criteria, and applicable products for the SRR.

Table 1 SRR ENTRANCE AND ACCOMPLISHMENT CRITERIA AND PRODUCTS

Entrance Criteria Accomplishment Criteria Applicable Products

1. A preliminary SRR agenda, success criteria, and instructions to the review board have been agreed to by the technical team, project manager, and review chair prior to the SRR.

2. OME products are ready for review at the maturity levels stated in the governing J-

2-A submission matrix.

3. OME requirements are available to the cognizant participants prior to the review and are ready to be baselined after the review. Preliminary requirements allocation to the next lower level has been performed.

4. Other SRR work products have been made available to the cognizant participants:

a. Updated parent requirements (if required to be provided by NASA)

b. Risk management plan ready to be baselined after review comments are incorporated.

c. Updated risk assessment and mitigations.

d. Initial document tree and model structure.

e. Initial verification and validation method identified for each requirement.

f. Initial system safety analysis.

g. Other specialty discipline analyses, as required.

h. Updated schedule for the OME project implementation.

The functional and performance requirements defined for the engine are responsive to the parent requirements and represent achievable capabilities

OME <Level>

Requirements

OME Specification and

Drawing Trees

OME Ground Support

Equipment Requirements and Plans

The maturity of the requirements definition and associated plans is sufficient to begin the next phase.

OME <Level>

Requirements

OME Data Specification and Drawing Trees

OME Ground Operations and Logistics

Requirements Document

OME Ground Support

Equipment Requirements and Plans

The project utilizes a sound process for the allocation and control of requirements throughout all levels, and a plan has been defined to complete the requirements definition at lower levels within schedule constraints

OME <Level>

Requirements

OME Specification and

Drawing Trees

OME Ground Operations and Logistics

Requirements Document

OME Ground Support

Equipment Requirements and Plans

Integrated Master

Schedule

The interface requirements defined for the engine are responsive to the parent requirements and represent achievable capabilities.

OME <Level>

Requirements

OME Ground Operations and Logistics

Requirements Document

OME CAD models

i. Initial Updated OME Ground

Operations and Logistics

Requirements Document and OME

Ground Support Equipment

Requirements and Plans

j. System safety and mission assurance plan ready to be baselined after review comments are incorporated.

k. Preliminary engineering development assessment and technical plans to achieve what needs to be accomplished in the next phase.

l. Design and Construction standards have been identified and agreed upon by the NASA customer.

OME Interface Simulator

Plan (Models, Simulations, and

Integrated Support Plan)

Preliminary approaches have been determined for how requirements will be verified and validated.

Master Verification Plan

Major risks have been identified and technically assessed, and viable mitigation strategies have been defined

Risk Plan

To Be Determined (TBD) and To Be

Revised (TBR) items are clearly identified with acceptable plans and schedule for their disposition

All items

Design and Construction standards have been agreed upon by the NASA customer.

Alternate Standards

8.2.2. CERTIFCATION MILESTONE 2 - PDR

The OME PDR demonstrates that the preliminary design meets all engine level requirements with a risk score of 1-10, based on the ESD Risk Scorecard found in

Appendix C of ESD 10003, Exploration System Development Risk Management Plan, and within schedule constraints and establishes the basis for proceeding with detailed design.

The PDR shall be completed between SRR and CDR and before PRR #1. Table 2 shows the entrance criteria, accomplishment criteria, and applicable products for the PDR.

Table 2 PDR ENTRANCE AND ACCOMPLISHMENT CRITERIA AND PRODUCTS

1. The project has successfully completed the previous planned milestone reviews, and responses and have been made to all

RFAs and RIDs or a timely closure plan exists for those remaining open.

2. A preliminary PDR agenda, success criteria, and instructions to the review board have been agreed to by the technical team, project manager, and review chair prior to the PDR.

3. All planned lower level PDRs and peer reviews have been successfully conducted, and RID/RFA/Action Items have been addressed with the concurrence of the originators.

4. Programmatic products are ready for review at the maturity levels stated in the governing PWS/DRDs.

5. The following primary products are ready for review:

a. A preliminary detailed design that can be shown to meet requirements.

b. Updated trending information from the OME Design Databook.

6. Other PDR technical work have been made available to the cognizant participants prior to the review:

a. Component design specifications, with supporting trade-off analyses and data, as required, that are ready to be baselined after review comments are incorporated.

b. Updated risk assessment and…