J-2 DRFP Data Procurement Document.pdf

J-2.1

Attachment J-2

December 19, 2019

Data Procurement Document

80JSC020OME

Draft Request for Proposal

Introduction Page 1 of 6

1 INTRODUCTION

1.1 Scope:

Subject to the Rights in Data clause, this Data Procurement Document (DPD) sets forth the data requirements in each Data Requirements Description (DRD) and shall govern that data required by the DPD for the contract. The Contractor shall furnish data defined by the DRD's listed on the Data Requirements List (DRL) by category of data, attached hereto, and made a part of this DPD. Such data shall be prepared, maintained, and delivered to NASA in accordance with the requirements set forth within this DPD. In cases where data requirements are covered by a Federal Acquisition Regulation (FAR) or NASA FAR Supplement (NFS) regulation or clause, the regulation will take precedence over the DPD, per FAR 52.215-8.

1.2 DPD Description

This DPD consists of an Introduction, a Statement of General Requirements, DPD maintenance procedures, a DRL, and the DRD's.

1.2.1 General Requirements:

The general requirements, as specified in paragraph 2.0 of this DPD, prescribe those requirements applicable to the preparation, maintenance, and delivery of data that are better defined in aggregate than in the individual DRD's.

1.2.2 Data Requirements List (DRL)

Throughout the performance of the contract, the DRL provides a listing by data category of the data requirements of the DPD.

1.2.2.1 The DRL and the Data Requirements Matrix (DRM) are the same under this contract.

1.2.2.2 The following definitions apply for submission activities:

• Initial – First release of a document.

• Update – Update to a document.

• Final – Baseline version of the document. The baseline version of the document shall be maintained and updated as required throughout the life of the contract.

1.2.3 Data Requirements Descriptions (DRD's)

1.2.3.1 Each data requirement listed on the DRL is given complete definition by a DRD. The DRD prescribes content, format, maintenance instructions, and submittal requirements.

1.2.3.2 For the purpose of classification and control, DRD's of this DPD are grouped into the following broad functional data categories:

CATEGORY SYMBOL DESCRIPTION

B Business M Management O Operations S Safety T Technical

Introduction Page 2 of 6

1.2.3.3 The symbols representing these data categories form part of the prefix of the DRD identification number. The numerical characters reflect the DPD number.

1.2.3.4 To facilitate the usage and maintenance of the DPD, the DRD's have been divided into sections in accordance with the above data categories.

1.2.3.5 The DRD's are filed by data category and are in alpha-numeric sequence as listed on the DRL pages that precedes the DRD's.

1.3 Data Types for Contractual Efforts:

The types of data and their contractually applicable requirements for approval and delivery are:

Introduction Page 3 of 6

Type Description

1 All issues and interim changes to those issues require written approval from the requiring organization before formal release for use or implementation.

NASA reserves a time-limited right to disapprove in writing any issues and interim changes to those issues. Data shall be submitted to the procuring activity for review not less than 45 calendar days prior to its release for use or implementation.

The Contractor shall clearly identify the release target date in the “submitted for review” transmittal. If the Contractor has not been notified of any disapproval prior to the release target date, the data shall be considered approved. To be an acceptable delivery, disapproved data shall be revised to remove causes for the disapproval before its release.

These data shall be delivered by the Contractor as required by the contract and do not require NASA approval. However, to be a satisfactory delivery, the data must satisfy all applicable contractual requirements.

These data are produced, or used during the performance of the contract, and are made available to NASA via the contractor’s collaborative environment and are retained by the Contractor. They shall be delivered when NASA requests it according to instructions in the request.

These data are incidental to contract performance and are retained by the Contractor in those cases where contracting parties have agreed that formal delivery is not required. However, the Contracting Officer or the Contracting Officer’s Representative (COR) shall have access to and can inspect this data at its location in the Contractor’s or subcontractor’s facilities, or in an electronic database accessible to the Government.

2 STATEMENT OF GENERAL REQUIREMENTS

2.1 Documents:

Documents included in Section 13.2 Documents of each DRD include “Applicable”, “Meets the Intent”, and/or “Informational” documents as defined by Attachment J-3 of this contract. The document versions are the issue specified in the Performance Work Statement and Attachment J3, and form a part of the DPD to the extent specified herein.

Documents listed in Item 13.2 of a DRD apply only to the preparation of the deliverable documentation described by that DRD.

References to documents other than Section 13.2 Documents in the data requirements of this DPD may sometimes be utilized, and shall be indicated in Section 11, Remarks of the DRD. These do not constitute a contractual obligation on the Contractor. These documents are typically, “informational” as defined in Attachment J3 of this contract.

They are to be used only as a possible example or to provide related information to assist the Contractor in developing a response to that particular data requirement.

2.2 Subcontractor Data Requirements

2.2.1 The Contractor shall specify to subcontractors and vendors, if any, the availability source of all data required for the satisfactory accomplishment of their contracts. The

Introduction Page 4 of 6

Contractor shall validate these requirements for documents when appropriate; where the requirement concerns other Contractor data, the Contractor shall provide his subcontractor or vendor with the necessary documents. All such requests shall be accomplished under the auspices of the Contractor.

2.2.2 Reference to subcontractor data in the Contractor’s responses is permissible, providing the references are adequate and include such identification elements as title, number, revision, etc., and a copy of the referenced data is supplied with the response document at time of delivery to NASA.

2.3 Data Distribution, Format and Transmittal

2.3.1 Distribution: Distribution of required documentation shall be in quantities determined by the Contracting Officer. Recipient names and email addresses shall be noted on a separate distribution list to be furnished by the Contracting Officer. The Contracting Officer’s letter may include other information pertinent to delivery of data, as required.

2.3.1.1 Electronic Format:

Electronic submission of data deliverables is required. Electronic deliverables shall be printable where possible. The Contractor will not be required to deliver the data in a printable format for data deliverables such as binary executables, CAD models, mathematical models, etc. which are not printable. The versions of all submittals shall be confirmed prior to delivery such that the delivered version corresponds to the intended delivered version.

Data submittals in MS Word, MS Project, Excel or PowerPoint shall consist of a single, searchable Adobe Acrobat PDF file in addition to the native Word, Excel, Project, or PowerPoint electronic file(s).

Where a single native format file is not possible, multiple files may be integrated into a single ZIP file for submission with the concurrence of NASA. The organization of the contents of the integrated ZIP file must be made readily apparent to the reader, and each file within the integrated product shall be clearly identifiable and traceable within the organization of the integrated product.

All native format files delivered by the Contractor shall be readable by COTS software.

Where the native file formats are not readable by COTS software, and with the concurrence of the NASA COR, the Contractor shall deliver the application (source code and executable) required in order to read the native file format. The preferred format for CAD data will be Creo (formerly called Pro/ENGINEER). The Contractor may request an alternative format.

Introduction Page 5 of 6

2.3.2 Transmittal

2.3.2.1 Type 1, 2, and 3 data shall be transmitted to NASA via the Integrated Collaborative Environment (ICE) in accordance with Attachment J-14, ICE Operating Environment, or other mechanism agreed to by the Contracting Officer, COR, and Project representatives who are responsible to receive, index, and store the data deliverables.

2.3.2.2 Data Transmittal Package: For all DRD’s that are delivered into the ICE Repository, each data transmittal package shall include:

a. Transmittal memorandum that specifies the meta-data below for each data transmittal:

1. Contract number.

2. Data Requirements Description (DRD) number.

3. DRD data type (specified in Item 3 on the DRD).

4. Submission date or milestone being satisfied.

5. Document number and revision.

6. Document title.

7. File names of all files being delivered; multiple files per document must be clearly related to the document.

8. Requested response date.

b. Printable electronic files.

2.3.3 Use of the ICE Repository: See Attachment J-14, ICE Operating Environment for details on using the ICE repository.

2.4 Reserved

2.5 Contractor’s Internal Documents:

The Contractor’s internal documents shall be used to meet the data requirements of this DPD unless a specific format is required by the applicable DRD. The format being used by the Contractor’s internal documents shall be readable by COTS tools.

2.6 Document Identification:

Type 1, 2, and 3 documents published by the Contractor and submitted in response to the data requirements of this DPD shall be identified within an organized identification numbering system prescribed to NASA by the Contractor and, if applicable, as approved by NASA. This number, change legend, date, and title constitute the minimum identification of the specific document and shall appear on the cover and title page. The contract number shall also appear on the cover and title page as separate markings. The originator and organization shall be included on the title page. The document number, change legend, and date shall appear on each page of the document. In the front matter of each document, identify the DPD number and applicable DRD number(s) required for document preparation. Successive issues or revisions of documents shall be identified in the same manner as the basic issue and shall have appropriate change identification.

Drawings and ECP's are excluded from the marking provisions of this paragraph.

2.7 Reference to Other Documents and Data Deliverables in Data Submittals:

All referenced documents shall be made readily available to the cognizant NASA organization upon request. The Contractor should make sure that the references are available to NASA in a manner which does not incur delays in the use of the response

Introduction Page 6 of 6 document. Reference may be made, within one data submittal, to other data submittals delivered in response to this DPD in those cases where the data required by one DRD may have been delivered by the Contractor in response to another DRD. The reference to previously-submitted data shall include the applicable DRD number, data submittal version date, and location within the referenced document.

2.8 Maintenance of Type 1 Document Submittals

2.8.1 Revisions of Type 1 documentation shall be by a complete reissue of the document identified in accordance with requirements of 2.7 above, with the exception of drawings (which shall be revised in accordance with contract configuration management requirements).

OME-B Page 1 of 1

Business Deliverables

OME-B-001 Page 1 of 2

PROJECT: Orion Main Engine 2. DRD NO.: OME-B-001

3. DATA TYPE: 1 4. DATE REVISED: Dec 2019

5. PAGE: 1

6. TITLE: Small Business Subcontracting Plan

7. DESCRIPTION/USE:

To describe the Contractor's planned approach to Small Business Subcontracting and their reporting against this plan.

8. DISTRIBUTION: As determined by the Contracting Officer

9. INITIAL SUBMISSION: Per Data Requirements Matrix

10. SUBMISSION FREQUENCY: Per Data Requirements Matrix

11. REMARKS: N/A

12. INTERRELATIONSHIP

Parent PWS Paragraph(s): 4.12

13. DATA PREPARATION INFORMATION:

13.1 SCOPE:

The Small Business Subcontracting Plan shall be in compliance with FAR 52.219-9.

The Small Business Subcontracting Reporting shall be in compliance with NFS 1852.219-75.

(September 28, 2015)

13.2 DOCUMENTS:

None

13.3 CONTENTS:

The Subcontracting plan must include the approach that the Contractor intends to use in meeting the subcontracting goals. Subcontractors whose bid is part of this proposal should be identified.

For each subcontractor, the percentage of the proposal and any small or small business subcategory classification should be identified. For areas of potential future subcontracting, the Contractor should identify the area of work, the percentage of contract that this is expected to encompass, potential subcontractors and their small business or small business subcategory classification. Describe the management approach to subcontracting with small, small disadvantaged businesses, Women-owned small businesses (WOSB), Historically Underutilized Business Zone (HUBZone), Veteran Owned Small Businesses (VOSB), Service Disabled Veteran Owned Small Businesses, and Historically Black Universities,(HBCU) and Minority Serving Institutions (MSIs).

Reports:

a. All reports shall be submitted in accordance with FAR 52.219-9 and NFS 1852.219-75.

b. Contractors are required to submit subcontracting data in the Electronic Subcontracting

Reporting System (eSRS).

c. All contractors are required to register and file both types of subcontracting reports using the eSRS system. The website to register is www.esrs.gov.

http://www.esrs.gov/

OME-B-001 Page 2 of 2

13.4 FORMAT: Contractor format is acceptable for the plan; reporting shall be in compliance with

NFS 1852.219-75.

13.5 MAINTENANCE: Revisions shall be incorporated by change page or complete reissue.

OME-M Page 1 of 1

Management Deliverables

OME-M-001 Page 1 of 3

1. PROJECT: Orion Main Engine 2. DRD NO.: OME-M-001

3. DATA TYPE: 3 4. DATE REVISED: Dec. 2019

5. RESERVED

6. TITLE: Orion Main Engine Project Management Plan

7. DESCRIPTION/USE:

The Orion Main Engine Project Management Plan (PMP) will describe the scope of the OME Project and the implementation approach, including the systems and processes, to provide overall coordination of management activities under this contract. It describes the structure and environment within which the program operates throughout the phases of the OME Project during DDTE, Production and Sustaining phases..

The OME Project Management Plan will be used to integrate these activities into the broader Orion operational plans. It will be used to identify Contractor management office and systems engineering structure for use by NASA personnel to identify reporting structures, to assist in evaluating performance measurement baseline status, and to ensure appropriate S&MA participation.

11. REMARKS:

12. INTERRELATIONSHIP:

Parent PWS Paragraph(s): 4.1 Referenced from PWS Paragraph(s): 4.3, 4.7, 4.9, 4.10, 9.1, 9.4, 9.5

The Contractor shall provide information giving NASA insight into staffing, organizational structure, management approaches, and processes used across the entire OME Project, including production and operations and DDT&E.

Applicable Documents:

MPCV 72634, Orion Multi-Purpose Crew Exploration Vehicle (MPCV) Program Main Engine (OME) Project Technical Requirement Specification (PTRS)

Informational Documents:

MPCV 72008, Orion MPCV Program Plan

The plan shall be in consonance with the PWS. The plan shall cover all aspects of project management for the Contractor including, but not be limited to, the following:

a. Narrative and graphical descriptions of the management, technical, and business approaches used to accomplish and monitor contractual tasks, as well as the methods

OME-M-001 Page 2 of 3 the contractor will employ to provide government insight, data accessibility, and/or deliverables.

b. Interfaces between the Contractor, NASA centers, and other contractors or entities that are necessary and pertinent to the accomplishment of contractural tasks.

c. Including such things as data, analyses, equipment, and software deliverables, schedules, interfaces, and other technical/managerial interactions.

d. Risk management and methodology and assessment of risks inherent in the management, technical, and business approaches including the process for incorporating lessons learned from previous applicable projects/programs.

e. Narrative description of the contractor’s management approach to defining processes, plans and procedures for project control and systems engineering including such items as specialty engineering, logistics, mass properties, transportation, storage, and integration of government furnished equipment/data and services.

f. Narrative to describe contractor’s insight/oversight implementation plan, including the partnering approach and establishing a cooperative environment that ensures an effective working relationship between NASA and the Contractor dedicated to successful DDTE and Production of an Orion Main Engine. This approach shall provide accommodations for Government personnel and its support services contractor(s), and timely and open access necessary to obtain a working-level understanding into all contractor activities. These accommodations include facility access, data, and any other information including technical and management processes required to meet contract requirements. The Contractor’s insight implementation approach shall identify instructions or training required to allow for meaningful NASA insight and participation (e.g., facility and safety familiarization).

g. Narrative description of the contractor’s acquisition strategy, including make/buy decisions and rationale, and subcontractor management.

h. Planned reporting to NASA of performance to plan in preparation for major milestone reviews and regularly scheduled reviews.

i. Narrative description of contractor controls applicable to any tasks and activities exceeding established cost or schedule plans, including requirements for providing recovery plans.

j. Narrative description of the contractor’s proposed scope and approach implementing cooperative relationships with associate contractors.

k. Approach to data rights and intellectual property (IP) while minimizing the cost to the Government. Address what patents, copyrights, trademarks, and trade secrets will be delivered to the Government in Attachment J25 Limited Rights in Data and Restricted Computer Software. Identify any limited data rights or restricted computer software issues, especially in the context of what the various corporate team members will provide. Explain how licensing agreements will be negotiated with vendors and how that data/IP will be treated, specifically identifying any requested special license agreements.

l. Narrative description of contractor processes and controls for managing export control and technology transfer associated with hardware, software, and data. This includes a description of the contractor Technical Assistance Agreements (TAA) process, in order to share hardware, software and data with international partner contractors.

m. Narrative description of contractor’s approach to implementing efficient and effective management for all phases of the contract. This includes the the period of time in which there is concurrent performance of CLINS and approach to transitioning its organizational structure from a DDT&E environment to a production and operations.

OME-M-001 Page 3 of 3

This approach shall address the Contractor’s approach to mitigating potential cost and schedule impacts of incorporating such knowledge gained from DD&TE into performance under OME.

n. Narrative description of the contractor’s approach/plan to configuration management and data management.

o. Narrative description of the contractor’s approach to providing a collaborative environment for non-data requirement deliverable information. This includes the process for granting NASA users access and the types of information that will be shared in the collaborative environments.

13.4 FORMAT: Electronic format per Section J-2 2.3.1.1.

13.5 MAINTENANCE: Contractor proposed changes to document format shall be submitted to NASA for approval. Complete re-issue of the document is required.

OME-M-002 Page 1 of 3

PROGRAM: Orion Main Engine 2. DRD NO.: OME-M-002

3. DATA TYPE: 3 4. DATE REVISED: Dec. 2019

5. RESERVED

6. TITLE: Integrated Master Schedule (IMS) and Schedule Deliverables

7. DESCRIPTION/USE:

To communicate program schedule information between the prime contractor and the Government. The IMS and other schedule deliverables will be used to provide program managers information to: (1) identify the magnitude and impact of actual and potential problem areas causing significant schedule variances, (2) forecast schedule completions, and (3) provide valid, timely program status information to higher management.

With the proposal:

a. A summary master schedule shall be submitted with the Proposal.

b. A schedule risk summary shall be submitted with the Proposal

No later than 90 days after ATP:

a. IMS

b. Schedule risk list

c. Schedule analysis

The summary master schedule and schedule risk summary shall be submitted with the proposal, and resubmitted as needed.. The IMS, schedule risk list, and schedule anaysis shall be submitted monthly by the 15th working day of the month following the month being reported. The schedule anaysis will be reviewed at the OME Monthly Review. A schedule risk assessment (SRA), and schedule variance reporting shall be submitted on a qurterly basis.

The IMS will be baselined after ATP, as agreed to by both parties, and not to exceed 90 days after ATP. Reference is made to NPR 7120.5 NASA Space Flight Program and Project Management Requirements, NPR 7120.8 NASA Research and Technology Program and Project Management, and SP-2010-3403 NASA Schedule Management Handbook. These documents shall be used as guides in preparation of the IMS and schedule delivery products.

The IMS shall be available for online viewing at any time during the effort by NASA using appropriately protected Internet/Intranet technologies.

Parent PWS Paragraph(s): 4.4

Referenced from PWS Paragraph: 8.1.1

To ensure an integrated approach to risk management, the information within the data provided by this IMS DRD shall be integrated with Schedule Breakdown Structure (if applicable.

OME-M-002 Page 2 of 3

• The summary master schedule is a high level review of the contractors plan from ATP to completion of end item deliverable.

• A schedule risk summary is a high level review communicating and connecting known areas of uncertainty to the summary master schedule.

• The IMS is an integrated logically linked schedule and shall capture the activities described in the Project Management plan..

• The schedule risk list is a list of uncertainty events tied to activities in the IMS that could delay or accelerate discrete milestones within the Project Management Plan.

• The schedule analysis is an electronic report of the health and assessment indicators of the IMS.

• The SRA is a probabailitic model performed by the contractor applying the risks and mitigation plans to the IMS to raise situational awareness for the Government of potential impacts to the schedule.

• The schedule variance report is a review of the IMS and any changes driven by performance, Government directed requirements, risk mitigation, or other causes.

Informational Documents:

NPR 7120.5, NASA Space Flight Program and Project Management Requirements NPR 7120.8, NASA Research and Technology Program and Project Management SP-2010-3403, NASA Schedule Management Handbook

DELIVERABLE INSTRUCTIONS:

The summary master schedule shall include a top level Gantt chart summary that reflects all contract and controlled milestones, major program/project phases (i.e. design, fabrication, integration, assembly, test, etc.) and all end item deliveries. Any tasks related to payment milestones must be clearly identified.

The schedule risk summary shall include all known areas of uncertainty related to the summary master schedule communicating the impact, cause, and potential mitigations.

The IMS shall include all discrete work. The IMS shall contain baseline schedule data, as well as current schedule status. All tasks that are not part of the Contractor scope of work, but could impact the logic driven network (GFE/CFE), will be treated as schedule visibility tasks (SVT's) only. Subcontractors shall be included with sufficient detail to develop a realistic critical path.

The prime and subcontractor (if any) data shall be consistent, statused monthly, and based on the same cutoff date to enable a realistic critical path. Tasks within the IMS shall contain unique identification numbers that will not change between monthly submissions. All discrete tasks/milestones except for the start and end of the contract or for interim receipt and delivery events to/from external entities shall have at least one predecessor and successor. All discrete tasks/milestones shall have durations in day increments. If schedule margin is included in the IMS, it must be as a defined task and clearly labeled as “Schedule Margin” or ”Schedule Reserve”. Any tasks related to payment milestones must be clearly identified.

The schedule risk list shall provide insight to risks associated with the activities within the IMS.

The risks must be statused monthly and based on the same cutoff date as the IMS to enable a realistic risk analysis. All risks within the risk list must include likelihood of impact, consequence of impact, information on mitigation progress, and be clearly related to identifiable tasks within the IMS.

OME-M-002 Page 3 of 3

The schedule analysis and review shall provide the IMS discussion and analysis to include the results of the contractor’s internal health analysis. This analysis shall include counts for the following schedule assessment indicators: 1) the total number of tasks, milestones and non-detail (e.g., summary, hammock, rollup, etc.) activities contained in the schedule, 2) the number of completed tasks and milestones, 3) the number of tasks and milestones to be completed, 4) the number of tasks and milestones that have no predecessor and/or no successor relationships and document why, 5) Negative float identification and key drivers, 6) the total number of tasks and milestones that have constraint (forced or fixed) dates. The IMS discussion shall also include primary, secondary, and tertiary critical path analysis. The review shall take place at the OME Monthly Review.

Schedule Risk Assessment (SRA): An SRA shall be conducted at the Post-Award Kick off Review, theSystem Requirements Review (SRR), PDR, CDR, and reported quarterly. The Contractor shall integrate risk mitigation activities into the IMS as required by the Contractor’s Risk Management Plan and communicate the risk posture of the plan to the Government A probabilistic result shall be included in this assessment and provide a realistic projection of the critical path..

The Schedule Variance is a review of the IMS and any changes driven by performance, Government directed requirements, risk mitigation, or other causes.

SUBCONTRACTOR REPORTS:

13.4 FORMAT: Electronic format per J-2 2.3.1.1 (Data Distribution, Format and Transmittal).

a. The summary master schedule must be submitted in a human readable format preferable to the contractor.

b. The schedule risk summary must be submitted in a readable human format preferable to the contractor.

c. The IMS shall be submitted in both the native schedule working file and XML.

d. The schedule risk list shall be submitted in XML.

e. The schedule analysis shall be submitted in XML, and reviewed at the OME Monthly

Review.

f. The SRA shall be submitted in a format preferable to the contractor and agreed to by NASA.

The schedule variance review shall be submitted in a readable format preferable to the contractor and agreed to by NASA.

13.5 MAINTENANCE: Contractor-proposed changes shall be submitted to NASA for approval.

Complete re-issue of the documents is required.

OME-M-003 Page 1 of 3

PROJECT: Orion Main Engine 2. DRD NO.: OME-M-003

3. DATA TYPE: 2 4. DATE REVISED: Dec. 2019

5. RESERVED

6. TITLE: OME Work Plan

7. DESCRIPTION/USE:

The OME Work Plan will establish the schedule milestones, payment milestones, and completion criteria for each milestone.

8. DISTRIBUTION: As determined by the Contracting Officer.

Parent PWS Paragraph(s): 7.0

13. DATA PREPARATION INFORMATION:

13.1 SCOPE:

An OME Work Plan will be generated for each task order issued for CLIN 0001 and CLIN 0002.

13.2 DOCUMENTS:

None

Each work plan shall delineate in the title which task order it is in regards to.

For CLIN 0001:

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 EDU and QUAL engine specific hardware and software.

The contractor shall provide input to the weeklyOME 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.

For CLIN 0001, the Contractor shall submit a work plan that contains:

a. Milestone events, by name

b. Number of months after contract ATP (ATP+) and date

c. Milestone amount as a percentage of cost in CLIN 0001

d. Milestone monetary value

OME-M-003 Page 2 of 3

e. An accomplishment criteria narritive (i.e., describe accomplishments and progress in terms of activities completed prior to the payment event).

For CLIN 0001, NASA will provide the propellants required for testing. The Contractor shall submit a propellant plan for CLIN 0001 that contains:

a. Propellant type

b. Amount of propellant

c. Propellant delivery location

d. Propellant delivery date

For CLIN 0002:

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.

For each engine in CLIN 0002, the Contractor shall submit a work plan that contains:

a. Milestone events, by name

b. Number of months after contract ATP (ATP+) and date

c. Milestone amount as a percentage of cost in CLIN 0002

d. Milestone monetary value

e. An accomplishment criteria narritive (i.e., describe accomplishments and progress in terms of activities completed prior to the payment event).

Note: Post-Flight Assessment Review to be performed only after the first two Artemis flights.

For CLIN 0002, NASA will provide the propellants required for testing. The Contractor shall submit a propellant plan for CLIN 0002 that contains:

a. Propellant type

b. Amount of propellant

c. Propellant delivery location

d. Propellant delivery date

OME-M-003 Page 3 of 3

13.5 MAINTENANCE: Contractor-proposed changes shall be submitted to NASA for approval.

Complete re-issue of the documents is required.

OME-M-004 Page 1 of 3

1. PROJECT: Orion Main Engine 2. DRD NO.: OME-M-004

3. DATA TYPE: 1 4. DATE REVISED: Dec. 2019

5. RESERVED

6. TITLE: Information Technology Security Management Project Plan

7. DESCRIPTION/USE:

To ensure that IT security reporting requirements are met for all IT systems utilized during work associated with this contract.

10. SUBMISSION FREQUENCY: Per Data Requirements Matrix

IT Security Program Management Plan

a. Initial: At proposal

b. Final: 30 days post ATP

c. Updates: Annually by September 30

IT Security Plan(s)

a. Initial: Assume maintenance of existing plans (for Government-owned and Contractor-managed systems) at proposal; IT Security Plan(s) for contractor-owned systems due at proposal

a. Final: 30 days post ATP

b. Updates: Shall be kept up-to-date as changes to the baseline configuration of the system(s) occur

11. REMARKS:

Information Technology Security Management Project Plan is Type 1 Clauses:

NFS 1852.204-76(c)(3) FAR 52.204-21, Basic Safeguarding of Covered Contractor Information Systems NFS NFS 1852.204-76, Security Requirements for Unclassified IT Resources NFS 1852.223-75, Major Breach of Safety or Security NFS 1852.237-72, Access to Sensitive Information NFS 1852.237-73L, Release of Sensitive Information

Parent PWS Paragraph(s): 4.6.2.1, 4.6.2.4

All contracts that purchase, lease, network to, or otherwise utilize Government-funded IT (as defined by the Clinger-Cohen Act of 1996 and referenced by OMB Circular A-130) must comply with NASA IT Security Requirements.

OME-M-004 Page 2 of 3

NPR 2810.1, Security of Information Technology

Informational Documents:

OMB Circular A-130, Managing Resources as a Strategic Resource ITS-HBK-2810.06-2B, NASA Information Technology Security Handbook, IT Security Awareness Training,

a. IT SECURITY MANAGEMENT PROJECT PLAN:

The Contractor shall submit an IT Security Management Project Plan for its unclassified technology information resources. This project plan shall describe the policy, processes, and procedures that will be followed to ensure appropriate security of IT resources that are developed, processed, or used under this contact. The Contractor’s IT Security Management Project Plan shall be compliant with the IT security requirements in accordance with Federal and NASA policies as referenced in OMB Circular A-130 and NPR2810.1(series).

b. IT SECURITY PLAN:

The Contractor shall have Information Systems Security Officer (ISSO) who is responsible for the contractor’s system(s) in accordance with the definitions set forth in NPR2810.1(series). The IT security plan shall be kept up to date as changes to the baseline configuration of the system occur and shall be documented in the IT Security Plan. Note: An IT Security Plan is specific to a system or group of systems, while an IT Security Management Project Plan is defined as the elements a contractor has outlined to meet the IT Security requirements for interfacing with other contractors and NASA, training requirements and meeting the requirements in NPR 2810.1(series).

c. IT SECURITY AWARENESS TRAINING:

Employees subject to this contract shall complete the NASA approved IT Security Awareness Training annually. The contractor shall provide evidence that periodic IT security awareness training has been met for all employees subject on this contract. The contractor shall submit periodic reports (as required by the CO) detailing the overall status of the annual training program. The annual training program is defined as the period from October 1st through September 30th.

d. 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:

OME-M-004 Page 3 of 3

a. IT Security Manager

b. Information System Owner (ISO)

c. Information Systems Security Officer (ISSO)

d. Organizational Computer Security Official – Representative (OCSO-

R)

The Contractor shall provide evidence that initial and periodic IT security training has been met for all employees subject on this contract. Contractor provided IT security awareness training may be substituted but must be approved annually by the Government (via the JSC Center IT Security Officer [CISO]) as an acceptable substitute. The Contractor shall submit periodic reports (as required by the CO) detailing the overall status of the annual training program. The annual training program is defined as the period from October 1st through September 30th.

e. INFORMATION ON EMPLOYEES IN SENSITIVE POSITIONS/ASSIGNMENTS

REPORT:

The Information on Employees is Sensitive. ITS Positions/Assignments Report shall provide information annually for personnel screening as required by NPR 2810.1(series), and NPR 1600.1 on position risk.

f. IT POINT OF CONTACT:

The contractor shall identify a point of contact that NASA may reach in its attempt to address IT and IT Security issues. The point of contact shall have the authority to ensure appropriate actions occur.

A list of all lead system administrators shall be updated by September 30 of each year. This list will be used to ensure the Contractor, as outlined in PN 04-03, has met the system administrator certification requirements.

13.5 MAINTENANCE: See Data Matrix

OME-M-005 Page 1 of 1

OME-M-005

RESERVED

OME-M-006 Page 1 of 1

OME-M-006

OME-M-007 Page 1 of 1

OME-M-007

OME-M-008 Page 1 of 1

OME-M-008

OME-M-009 Page 1 of 3

1. PROJECT: Orion Main Engine 2. DRD NO.: OME-M-009

5. RESERVED

6. TITLE: Government Property Management Plan

7. DESCRIPTION/USE:

To describe the method of administering and controlling Government personal property and submitting proposed property manager qualifications.

Parent PWS Paragraph(s): 4.5

13. DATA PREPARATION INFORMATION:

13.1 SCOPE:

The Government Property Management Plan defines the Contractor's use, maintenance, repair, protection, and preservation of Government personal property. It shall describe the Contractor's approach to receiving, handling, stocking, maintaining, protecting and issuing Government property (equipment and material). The Plan should include interaction and Department/ Office responsibilities. The Contractor shall submit to the delegated Government Property Administrator (GPA) detailed supplemental property procedures, which are separate from the Property Management Plan, within 60 days after the contract start date.

The Contractors submitting an initial Property Management Plan as part of their reply to the Request for Proposal in accordance with Contracting Officer direction, will also submit proposed property manager qualifications and experience as specified below.

Management Qualifications/Experience:

The Offeror/Contractor shall specify the name and the qualifications of the proposed property manager.

a. List the Federal agencies or departments supported in managing Government property and the corresponding number of years of experience.

b. List completed personal property management training courses.

c. Specify the level of professional property management certification obtained by the proposed property manager.

d. List professional personal property management organizations in which the proposed property manager has an active current membership.

This qualification data shall be a one-time submittal from the Offerors with their initial Property Management Plan (PMP) when the plan is requested by the Contracting Officer.

Insert that data as a separate tab after that PMP.

OME-M-009 Page 2 of 3

This qualification data shall be excluded from the final PMP from the awarded Contractor.

13.3 CONTENTS:

This plan shall reference those policies and procedures which are part of the Contractor's Property Management System and shall include at a minimum, but not limited to, the following functions/outcomes/activities:

a. Property Management

a. Voluntary consensus standards, industry-leading practices and standards, customary commercial practices

b. Periodic internal reviews, surveillances, self-assessments, and audits

c. Written procedures

b. Acquisition of Property

a. Acquisition authority

b. Classification of property

c. Receipt of Government Property

a. Receiving

b. Identification

d. Records of Government Property

e. Physical Inventory

f. Subcontractor Control

a. Flow down of property clauses to subcontractors

g. Reports

a. Loss, Theft, Damage, Destruction reports

b. Physical Inventory reports

c. Audits and self-assessment reports

d. Corrective Action reports

h. Relief of Stewardship Responsibility and Liability

a. Loss, Theft, Damage, Destruction of property

b. Consumed property

c. Delivered property

d. Contractor Inventory Disposal of property

1) In-house screening of excess

2) Disclosure of excess

e. Abandonment of Government property (if directed by the Government)

i. Utilizing Government Property

a. Utilization

b. Consumption

c. Movement

d. Storage

j. Maintenance

a. Preventive maintenance

b. Rehabilitation

c. Calibration

k. Property Closeout

OME-M-009 Page 3 of 3

a. Screening for further use

b. Final physical inventory

c. Transfers off the contract

d. Final NASA Form 1018

l. Reconcile Contractor Records with NASA Financial Property Records [NASA Form 1018 and the Contractor-Held Asset Tracking System (CHATS) if applicable]

m. JSC-Unique Considerations (as they arise or known now)

13.4 FORMAT: The Contractor’s format is acceptable. Electronic format per J-2 2.3.1.1.

13.5 MAINTENANCE:

Changes to the Government Property Management Plan shall be incorporated by change pages or complete reissue after coordination with the Government Property Administrator.

OME-M-010 Page 1 of 1

OME-M-010

OME-M-011 Page 1 of 1

OME-M-011

OME-M-012 Page 1 of 2

1. PROJECT: Orion Main Engine 2. DRD NO.: OME-M-012

5. RESERVED

6. TITLE: Organizational Conflicts of Interest (OCI) Plan

7. DESCRIPTION/USE:

To document the Contractor’s comprehensive management approach and implementation methods for avoiding, neutralizing, mitigating, or waiving organizational conflicts of interest.

11. INITIAL SUBMISSION: Per Data Requirements Matrix

10. SUBMISSION FREQUENCY: Per Data Requirements Matrix

11. REMARKS:

NASA Guide on Organizational Conflicts of Interest (March 2010) Clauses:

FAR Subpart 9.5, Organizational and Consultant Conflicts of Interest NFS 1852.237-72, Access to Sensitive Information NFS 1852.237-73, Release of Sensitive Information

Parent PWS Paragraph(s): 3.7

The OCI Plan describes the Contractor’s comprehensive management approach and implementation methods for avoiding, neutralizing, mitigating, or waiving organizational conflicts of interest. After approval, the OCI Plan will become part of the contract as Attachment J-35.

The OCI Plan shall discuss the following:

Purpose:

A summary of the Contractor’s rationale for instituting and applying the OCI Plan;

Update Criteria:

A description of the criteria and process for determining when an update to the plan is required;

Contractor’s OCI Assessment Methodology:

A summary of the general methodology used to identify, avoid, neutralize, or mitigate OCI issues. Define company roles, responsibilities, and procedures for screening (i.e., identifying/recognizing, analyzing/evaluating, resolving, and reporting) existing and new

OME-M-012 Page 2 of 2 business opportunities for actual/potential OCIs. Include any Contractor policies defining organizational or employee sanctions for violations of Contractor’s OCI procedures or requirements. Identify any Contractor recordkeeping or self-audit requirements related to Contractor’s OCI program. Identify any affiliated companies/entities (e.g., a parent company or a wholly-owned subsidiary) and procedures for coordinating OCIs with such affiliated companies/entities. Explain how the Contractor will flow down the provisions of this mitigation plan to any subcontractor that may have a conflict with regard to performing the requirements of this contract;

Contractor’s OCI Response Procedures:

A summary of the steps that the Contractor will take when an OCI has been identified or when circumstances have changed such that an OCI issue is probable. Include Contractor procedures for reporting of all potential/actual OCIs during performance of the contract and the point of contact for OCI reports;

Identified OCI Risks:

Provide a description of identified potential OCI risks, due to the Contractor’s relationships or potential relationships with the Government, other companies, and other contracts. The description shall characterize the risk and measures to avoid, neutralize, or mitigate each OCI threat. If using a firewall, explain how these actions will operate to successfully address a conflict without adversely affecting performance of the contract.

Additionally, Contractor shall identify any potential OCIs created by the requirements of this RFP which the Contractor intended to resolve using methods other than mitigation;

Personnel Clearance Procedures:

A description of the procedures the Contractor will use if needed to identify and partition Contractor personnel requiring access to or participation in activities that would otherwise create an OCI issue; and

OCI Training:

A description of the training to be provided to a Contractor personnel regarding potential OCIs on this contract.

13.4 FORMAT: The Contractor’s format is acceptable. The electronic format shall be compatible with Microsoft Office. Electronic format per J-2 2.3.1.1.

13.5 MAINTENANCE:

Revisions to this DRD shall be incorporated by change page or complete reissue. The Contractor shall review the OCI Plan on an annual basis or as directed by the Contracting Officer to revise the OCI Plan if necessary. Revisions are subject to Contracting Officer approval.

OME-M-013 Page 1 of 1

OME-M-013

OME-O Page 1 of 1

Operations Deliverables

OME-O-001 Page 1 of 1

OME-O-001

OME-O-002 Page 1 of 2

1. PROJECT: Orion Main Engine 2. DRD NO.: OME-O-002

3. DATA TYPE: 2 4. DATE REVISED: Dec.2018

5. RESERVED

6. TITLE: OME Ground Operations and Logistics Requirements Document

7. DESCRIPTION/USE:

• To define the process for developing and delivering the OME operations and maintenance requirements.

• To identify the ground operations resources required by the OME Contractor to process the OME flight hardware.

Parent PWS Paragraph(s): 12.2.1 Referenced from PWS Paragraph(s): 12.2.2, 12.2.3

The OME Ground Operations and Logistics Requirements Document defines the requirements for the OME ground operations. The Document describes the Contractor’s approach to define requirements necessary for the development of safe and effective operational procedures.

The document also defines the integration and launch site support requirements, including transportation and storage, needed by the OME hardware integrator and ground operations personnel for work to be done at both Airbus Bremen and KSC facilities.

The OME Ground Operations and Logistics Requirements Document shall:

• Define the plan for decontamination of the engine after ATP hotfire that meets the hazardous material requirements at the ESA site(s) receiving the flight engine.

• Define transportation plan to transport from Contractor facility to Airbus facility at Bremen, Germany.

• Define requirements necessary to develop NASA ground processing, and launch operations procedures for the OME at the Airbus Bremen and KSC processing facilities such as limited-life, time and cycle limits, expected operational limits for ground processing (e.g., temperature, pressure, humidity, voltage, current, preventive maintenance), packaging, handling, transportation, and storage requirements.

OME-O-002 Page 2 of 2

• Define facility requirements for processing and storing OME at the facilities where OME will be processed, i.e Airbus Bremen and KSC locations.

Identify requirements for transporting and storage of Contractor-provided flight hardware and logistical spares.

Each requirement shall include technical rationale, derivation of operational limits and tolerances, and, if reusable, the fair wear and tear criteria. The OME Ground Operations Requirements Document shall include detail at a level commensurate with the state of the system design at the time of document delivery.

13.5 MAINTENANCE: Changes shall be incorporated by complete reissue.

OME-O-003 Page 1 of 1

OME-O-003

OME-O-004 Page 1 of 1

OME-O-004

OME-O-005 Page 1 of 1

OME-O-005

OME-O-005 Page 1 of 1

OME-O-006

OME-O-007 Page 1 of 1

OME-O-007

OME-O-008 Page 1 of 2

1. PROJECT: Orion Main Engine 2. DRD NO.: OME-O-008

3. DATA TYPE: 2 4. DATE REVISED: Dec. 2019

5. PAGE: 1

6. TITLE: OME Ground Support Equipment Requirements and Plans

7. DESCRIPTION/USE:

• Volume I: Design data for OME Contractor-provided OME GSE end items to support ground operations in preparation for flight.

• Volume II: Document the operations and maintenance plan and requirements for OME Contractor-provided GSE necessary for OME ground operations.

• Volume III: Document the sustaining engineering plan for OME Contractor-provided GSE necessary for OME ground operations.

10. SUBMISSION FREQUENCY: Per Data Requirements Matrix

11. REMARKS:

Plan and Requirements will be Data Type 2.

May reference OME-T-031 for the same OME GSE design data.

Parent PWS Paragraph(s): 13.0 Referenced from PWS Paragraph(s): 12.2.3, 12.2.4

Provide design and development details of OME Contractor-provided GSE, and operations, maintenance, and sustaining engineering plans/requirements for OME Contractor-provided GSE.

Meet the Intent Documents:

MPCV 72506, Orion Multi-Purpose Crew Vehicle (MPCV) Standard for the Design and Fabricaiton of Ground Support Equipment

OME Ground Support Equipment Requirements and Plans shall consist of three volumes, each providing the Contractor’s requirements, plan or approach to a different aspect of

GSE.

Volume I. OME GSE End Item Implementation Plan Volume II. OME GSE Operations and Maintenance Plan and Requirements Documentation Volume III. OME GSE Sustaining Engineering Plan

The…