EPFD-01-03 Integrated Data Requirements Description Document Final.pdf

TBD

CONTRACT/BAA

B

ATTACHMENT NUMBER

Electrified Powertrain Flight Demonstration

Project

Integrated Data Requirements Description Document

Doc. #: EPFD-01-03

February 22, 2021

National Aeronautics and Space Administration

National Aeronautics and Space Administration

DOCUMENT CHANGE LOG

DATA REQUIREMENTS

DOCUMENT

NO. ISSUE

INCORPORATED REVISIONS

OUTSTANDING REVISIONS

AS OF:

SUPERSEDING:

PAGE:

AUTHORITY PORTION AFFECTED - PAGE NO. REMARKS

(DRD Revision) INTRO CDRL DRD

TABLE OF CONTENTS

1.0 INTRODUCTION

1.1 Scope

1.2 DRD Description

2.0 APPLICABLE/REFERENCE DOCUMENTS

3.0 GENERAL REQUIREMENTS

3.1 Contract Data Requirements List (CDRL)

3.2 Data Requirements Descriptions (DRDs)

3.3 Document Change Log (DCL)

3.4 DRD Maintenance Procedures

3.5 Data Types for Contractual Efforts

3.6 Subcontractor Data Requirements

3.7 Data Restriction and Markings…………………………...……………………………………….7

3.8 Data Submittals ……………………………………………………………….8

3.9 Data Transmittal

3.10 Document Identification

3.11 Reference to Other Documents and Data Descriptions in Data Submittals

4.0 DATA MAINTENANCE PROCEDURES …….………………………………………………10

4.1 NASA-Initiated Change

4.2 Contractor-Initiated Change

5.0 CONTRACT DATA REQUIREMENTS LIST (CDRL)………………………………..…… 12

6.0 DATA REQUIREMENTS DESCRIPTION (DRDs)…………………………. ……………13-81

1.0 INTRODUCTION

1.1 Scope

Subject to the Rights in Data clause, 52.227-14 Rights in Data-General (MAY 2014) this Integrated Data Requirements Description Document sets forth the Contractor’s data requirements and shall govern the data required by the Data Requirement Description (DRDs) for the contract. The Contractor shall furnish data defined by the DRDs listed on the Contract Data Requirements Lists (CDRL) included in Section 5.0 and attached hereto in Section 6.0 of this document. Such data shall be prepared, maintained, and delivered to NASA in accordance with the requirements set forth within this Integrated Data Requirements Description Document. In cases where data requirements are covered by a Federal Acquisition Regulation (FAR) or NASA FAR Supplement (NFS) clause, that clause shall take precedence over the Integrated Data Requirements Description Document.

1.2 DRD Description

This Integrated Data Requirements Description Document consists of a Document Change Log, an Introduction, Applicable Documents, General Requirements, DRD maintenance procedures, and CDRL, and the DRDs.

2.0 APPLICABLE/REFERENCE DOCUMENTS

a. The applicable and reference documents included in this Integrated Data Requirements

Description Document and each specific DRDs are summarized in the tables 2.1 and 2.2.

b. References to documents other than applicable documents in the data requirements of this

Integrated Data Requirements Description Document may sometimes be utilized. 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 requirements.

Table 2.1 – Technical DRDs Reference Documents Matrix

Table 2.2 – Programmatic DRDs Reference Documents Matrix

SE-01 SE-02 SE-03 SE-04 SE-05 SE-06 TE-01 TE-02 TE-03 TE-04 SM-01 SM-02 SM-03 SM-04 SW-01

Reference Document # Title NPR 7123.1C NASA Systems Engineering Requirements and Processes X X X X X NASA/SP-2016-6105- REV 2 NASA Systems Engineering Hanbook, Rev 2 X X X X NASA/SP-2015-3709 HSI Practitioner s Guide X 14 CFR Parts 23, 25, 33 and 35 Title 14 Code of Federal Regulations (CFR) X ASTM F39 ASTM Committee F39 on Aircraft Systems X SAE-E-40 SAE Electrified Propulsion Committee X EPFD-02-02 EPFD Systems Requirements Document X X X X NPR 7900.3D Aircraft Operations Management X X AFOP-7900.3-023 AFRC Airworthiness And Flight Safety Review Process X EPFD-02-06 Technical Measures of Effectiveness X X X

AIAA

Guidelines for Analysis of Hybrid/Electric Aircraft System Studies Document X

AFRC 8621.1-001 AFRC Center Mishap Preparedness and Contingency Plans X

NPR 8621.1C

NASA Procedure Requirements for Mishal and Close Call reporting, investigating and record keeping X

Form AFRC 802.63 Aircraft Emergency Information X NPR 8715.3D NASA General Safety Program Requirements X NPD 8720.1C NASA Reliability and Maintainability (R&M) Program Policy X NPD 8730.5B NASA Quality Assurance Program X

AFOP 8730.5-007 Rev A Armstrong Flight Research Center (AFRC)Quality Assurance Procedures X

AFOP-8715.3-005 Armstrong Flight Research Center (AFRC) X NPR 7150.2C NASA Software Engineering Requirements X X NASA-STD-8739.8 NASA Software Assurance and Software Safety Standards X

RTCA- DO-178C

Software considerations in airborne systems and equipment certification X

NASA-HNBK-2203 A NASA Software Engineering Handbook X EPFD SOO EPFD Statement of Objectives X NASA SP 20205003605 Technology Readiness Assessment Best Practices Guide X

DRDs REFERENCE DOCUMENTS - MATRIX TECHNICAL DRDs

PM-01 PM-02 PM-03 PM-04 PM-05 PM-06 PM-07 PM-08 PM-09

Reference Document # Title NPR 7123.1C NASA Systems Engineering Requirements and Processes X NASA/SP-2016-6105- REV 2 NASA Systems Engineering Hanbook, Rev 2 X ANSI/EIA-478 Earned Value Management Systems X

NFS 1852 234-1

Notice on EVM- NASA FAR Supplement Notice of Earned Value Management System Clause X

NFS 1852 234-2 Earned Value Management Systems Threshold X NASA/SP-2010-3404, Rev 1 NASA Work Breakdown Structure Handbook X IPMDAR Implementation and Tailoring Guide X EIA-649 National Consensus Standard for Configuration Management X

NPR 7120.5E

NASA Space Flight Program and Project Management Requirements X X X X

NASA/SP-2010-3406, Rev 3 NASA Special Publication : INTEGRATED BASELINE REVIEW (IBR) Handbook X

NASA/SP-2014-3705 NASA Space Flight Program and Project Management Handbook X

NFS 1852 204-76

Security requirements for unclassified information technology resources X

NASA/SP-2011-3422 (Version 1) NASA Risk Management Handbook X S3001 (Version G) Guidelines for Risk Management X NPR 8000.4B NASA Risk Management Procedural Requirements X

DRDs REFERENCE DOCUMENTS - MATRIX PROGRAMMATIC DRDs

3.0 GENERAL REQUIREMENTS

The general requirements, as specified herein, prescribes those requirements which are applicable to all the DRDs. This includes the preparation, maintenance, and delivery of the data associated with and defined in each DRD.

3.1 Contract Data Requirements List (CDRL)

Throughout the performance of the contract, the CDRL provides a summary listing of the data submittal requirements for each Data Requirements Description (DRDs). Refer to Tables 5.1 and

5.2 in section 5 for the CDRL.

3.2 Data Requirements Descriptions (DRDs)

Each data requirement listed on the CDRL is given a complete definition by each DRD. The DRD prescribes content, format, maintenance instructions, and submittal requirements. All specific DRDs are included in Section 6.0 of this document.

3.3 Document Change Log (DCL)

The Document Change Log chronologically records all revision actions that pertain to the Integrated Data Requirements Descriptions Document.

3.4 DRD Maintenance Procedures

Maintenance procedures define the detailed methods to be employed in maintaining the DRD.

Detailed maintenance procedures are specified in Section 4 of this document.

3.5 Data Types for Contractual Efforts

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

Definitions - NASA Action Acceptance - All versions of the deliverable requires NASA communique accepting the submittal. NASA reserves a time-limited right to comment in writing any versions and interim changes to those versions.

NASA shall provide inputs no later than 21 days after submittal. Contractor shall proceed upon acceptance notification unless contacted by NASA within the time-limited window. The act of an authorized representative of the Government by which the Government, for itself assumes ownership or accepts specific services rendered, as partial or complete performance of the contract. Examples are reports that will be submitted as deliverables.

Approval - All versions and interim changes that affect the content or intent of those versions of the deliverable require written approval from a NASA representative before formal release to proceed with the approved process, strategy, or procedure. Examples are deliverables associated with airworthiness and hardware certification, technical and programmatic decision gates such as reviews, and other requirements requiring authorization before the contractor can move forward.

Data - Recorded information, regardless of form or the media on which it may be recorded. 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 shall satisfy all applicable contractual requirements. The term includes technical data and computer software. The term does not include information incidental to contract administration, such as financial, administrative, cost or pricing, or management information.

3.6 Subcontractor Data Requirements

Where a Subcontractor is performing any part of the work related to a Data Requirement, the Contractor shall ensure these DRDs are levied on the applicable Subcontractor. The Contractor shall integrate and provide Subcontractor data into the applicable Data Requirement.

Subcontractor integration is the responsibility of the Prime Contractors.

3.7 Data Restrictions and Markings

a. All data produced or delivered under this contract shall be governed by FAR 52.227-14 Rights in Data-General (MAY 2014), Alts. II & III, as modified by NFS 1852.227-14 Rights in Data- General (APR 2015). The Contractor shall determine the data restriction that applies to each data description and mark the data restriction on the data coversheet, or indicate the data restriction in the data transmittal package if the data format precludes identification of data restriction directly in the data. The Contractor shall make a determination for each individual data description item, and shall not apply a default or blanket data restriction marking to all data description (e.g., “data may be export restricted”). If NASA does not agree with the Contractor applied data restriction, the NASA Contracting Officer shall return the data to the Contractor, cancel the markings, or ignore the markings consistent with the procedures set forth in the “data rights” clause(s) contained in the contract.

b. The Contractor shall consider the following data restriction categories, as a minimum, and utilize specified marking statements.

1. If data delivered under this contract is subject to the International Traffic in Arms

Regulations (ITAR), the data shall contain an “ITAR Notice” as follows:

2. If data delivered under this contract is subject to the Export Administration Regulations

(EAR), the data shall contain the “EAR Notice” as follows:

International Traffic in Arms Regulations (ITAR) Notice

This document contains information which falls under the purview of the U.S. Munitions List (USML) as defined in the International Traffic in Arms Regulations (ITAR), 22 CFR §120-130, and is export-controlled. It shall not be transferred to foreign persons in the U.S. or abroad without specific approval of a knowledgeable NASA export control official, and/or unless an export license or license exemption is obtained/available from the Directorate of Defense Trade Controls, United States Department of State.

Violations of these regulations are punishable by fine, imprisonment or both.

c. Government purpose rights - the rights to —

1. Use, modify, reproduce, release, perform, display, or disclose technical data within the Government without restriction; and

2. Release or disclose technical data outside the Government and authorize persons to whom release or disclosure has been made to use, modify, reproduce, release, perform, display, or disclose that data for United States government purposes.

Unlimited rights - means the rights of the Government to use, disclose, reproduce, prepare derivative works, distribute copies to the public, and perform publicly and display publicly, in any manner and for any purpose, and to have or permit others to do so.

Limited rights data - means data, other than computer software, that embody trade secrets or are commercial or financial and confidential or privileged, to the extent that such data pertain to items, components, or processes developed at private expense, including minor modification.

Sensitive But Unclassified (SBU) - this information may be exempted from disclosure by Statute, including information exempt from disclosure by The Freedom of Information Act exemption. Per new NASA direction, this term will no longer be used after October 1st, 2021.

Controlled Unclassified Information (CUI)- This is information the government creates or possesses, or that an entity creates or possesses for or on behalf of the government, that a law, regulation, or government-wide policy requires or permits an agency to handle with safeguarding or dissemination controls.

3.8 DATA SUBMITTAL

The Contractor shall employ a system for organizing, identifying, and tracking all submittals of DRDs, to include any changes or revisions. At a minimum, this system shall include the mapping of Contractor documents and files submitted in response to each DRD.

The requirement, definition and expectations on submittal of DRDs are outlined in Table 3.9.1 below. Whenever “days” is used throughout this document and the DRDs, we refer to calendar days.

Export Administration Regulations (EAR) Notice

This document contains information within the purview of the Export Administration Regulations (EAR), 15 CFR §730-774, and is export-controlled. It may not be transferred to foreign persons in the U.S. or abroad without specific approval of a knowledgeable export control official, and/or unless an export license or license exception is obtained/available from the Bureau of Industry and Security, United States Department of Commerce. Violations of these regulations are punishable by fine, imprisonment or both.

TABLE 3.9.1- DATA SUBMITTAL REQUIREMENTS DEFINITION

3.9 Data Transmittal

This section provides additional detail regarding the transmittal and format of the DRDs

3.9.1 Data shall be transmitted to NASA via an integrated collaborative environment defined by the Contractor that accommodates sharing of electronic files or other mechanism agreed to by the Contracting Officer, COR, and Project representatives who are responsible to receive, index, and store the data. The electronic files shall be in an unlocked, editable format where appropriate.

3.9.2 Each data transmittal package shall include:

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

a) Contract number

b) Data Requirements Description (DRD) number

c) Submission date or milestone being satisfied

d) Document number and revision

e) Document title

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

g) Distribution (as defined by the Contracting Officer’s letter)

h) Requested response date

2. Printable electronic files.

Initial submittal Final Submittal 28 calendar days ahead- Agenda for review and outline of content including list of deliverables and documentation

1 week ahead- Final presentation and deliverables at required maturity in support of the review (plans, reports, documents, data)

None Final presentation and deliverables due 7 calendar days prior to IBR Event date as specified in DRD-PM-06

None Due at delivery date

None Due 3 calendar days ahead of date

28 calendar days ahead- Agenda for review and outline of content including list of deliverables and documentation

1 week ahead- Final presentation and deliverables at required maturity in support of the review (plans, reports, documents, data)

Pre test documentation 7 calendar days ahead of test N/A

Post Test Data N/A 1 month following event

Post test- Analysis Reports N/A 3 months following event

Deliverable type

Ac tio na bl e Ev en t

Documentation required for each Lifecycle reviews (SRR, PDR, CDR, FRR , PFAR)

Documentation required for Integrated Baseline Review

(IBR)

Monthly Submissions

Quarterly Submissions

EPFD Final Closeout Meeting

3.9.3 Document and Data Format

a. All documents may be formatted using the Contractor’s preferred format except when directed otherwise in the DRD, contract clause, or referenced requirement.

b. All documents, unless otherwise noted within the specific DRD, shall be submitted in electronic format using standard Adobe PDF format or Microsoft Office software (Word, Excel, PowerPoint, and Project).

3.10 Document Identification

Documents published by the Contractor and submitted in response to the data requirements of this Integrated Data Requirements Description Document shall be identified within an organized identification numbering system prescribed to NASA by the Contractor. 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 names 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 of each document, identify the 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 are excluded from the marking provisions of this paragraph.

3.11 Reference to Other Documents and Data Descriptions in Data

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

Reference may be made, within one data submittal, to other data submittals delivered in response to the Integrated Data Requirements Description Document, in 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.

4. DRD Maintenance Procedures

4.1 NASA-Initiated Change

New and/or revised data requirements shall be incorporated by contract modification to which the new or revised portion of the Integrated Data Requirements Description Document shall be appended. The Contractor shall notify the Contracting Officer in the event a deliverable data requirement is imposed and is not covered by a DRD, or when a DRD is changed by a contract modification and for which no revision to the Integrated

Data Requirements Description Document is appended. In such cases, the Contractor shall submit the requested changes to NASA for approval.

4.2 Contractor-Initiated Change

Contractor-proposed data requirements or proposed changes to existing requirements shall be submitted to NASA for approval per Contractor’s Configuration Management Plan and process.

5.0 Contract Data Requirements List (CDRL)

5.1 Definitions

Table 5.1 Programmatic CDRL

"Approach"- provide a high level definition of the methods and processes that provide understanding of the sequence and interactions of these processes as part of the overall project and tehcnical management system.

"Preliminary" - is the documentation of information as it stabilizes but before it goes under configuration control. It is the initial development leading to a baseline. Some products will remain in a preliminary state for multiple reviews. The initial preliminary version is likely to be updated at a subsequent review but remains preliminary until baselined.

"Baseline" indicates putting the product under configuration control so that changes can be tracked, approved, and communicated to the team and any relevant stakeholders. The expectation on products labeled "baseline" is that they will be at least final drafts going into the designated review and baselined coming out of the review. Baselining a product does not necessarily imply that it is fully mature at that point in the life-cycle. Updates to baselined documents require the same formal approval process as the original baseline.

"Update" is applied to products that are expected to evolve as the formulation and implementation processes evolve. Only expected updates are indicated. However, any document may be updated as needed.

"Final" is applied to products that are expected to exist in this final form, e.g., minutes and final reports.

P= Preliminary B= Baseline U= Update F= Final A= Approach

DRD # DRD Title

Initial Delivery Update/Frequency

DRD-PM-01 Insight Implementation Plan Preliminary with Proposal Baseline - NLT 60 calendar days after ATP DRD-PM-02 IPMDAR See DRD Monthly (see DRD) DRD-PM-03 Earned Value Management Plan (EVM) Baseline at proposal 60 calendar days after exercising significant contract DRD-PM-04 Configuration and Data Management Plan Outline- 28 calendar days prior to IBR Baseline- 7 calendar days prior to IBR DRD-PM-05 JCL Analysis Due at proposal Updates at each life cycle review

DRD-PM-06 Integrated Baseline Review (IBR) Agenda/Outline - 28 calendar days prior to IBR Presentation material- 7 calendar days prior to IBR

DRD-PM-07 IT Security Management Plan Preliminary - 30 Calendar days after contract award Baseline- 90 calendar days after contract award DRD-PM-08 Risk Exposure-Posture and Reserve (REPR) Due at proposal Updates at each life cycle review

DRD-PM-09 Risk Score card, Risk Registry and Risk reports Due at proposal

Registry and Reports: Monthly (see DRD) Risk Scorecard and Process: May be updated at lifecycle reviews or by request (see DRD)

Table 5.2 Technical CDRL

6.0 Data Requirements Description (DRD)

DRD DRD Title

At proposal submission

SRR PDR CDR FRR PFAR

Component and Subsystem Ground Test(s) Integrated Ground Test(s)

DRD-SE-01 Human Systems Integration Approach and Plan

Approach, no more than 10 pages B U U U

DRD-SE-02

EAP Regulations And Stds Gap Analysis, Closure Approach and Resultant Stds Development

Preliminary, no more than 15 pages P B U U U U U

DRD-SE-03

System and Subsystem Requirements Documents

System Level Requirements Preliminary, no limit P B U U U U System Specifications P B U U U

Subsystem Requirements P B U U U U U

DRD-SE-04 Systems Engineering Approach and Processes

Approach, no more than 10 pages B U U DRD-SE-05 Verification and Validation Plan P B U U U U

DRD-SE-06

Airworthiness Approach, Airworthiness Plan and Airworthiness Products

Airworthiness Approach, Airworthiness Plan and Airworthiness Products

Preliminary, no more than 15 pages Airworthiness Plan P B U U U

Airworthiness Products F

DRD-TE-01 Vision Vehicle Description and Validation Report

Preliminary, no more than 5 pages P B U U U U U

DRD-TE-02 Capability and Technology Development Plan

Preliminary, no more than 15 pages P B U U U U U DRD-TE-03 Data Requirements And Reporting Plan

Technical Data Report Preliminary, no more than 15 pages P B U U U U Master Measurement List P B

Contractor Analysis Report P F DRD-TE-04 Technology Maturation Report P

DRD-SM-01

Mishap Preparedness and Contingency Plan

(MPCP) P B U U

DRD-SM-02

Safety and Mission Assurance Approach and Processes

Approach, no more than 10 pages P B U DRD-SM-03 Hazard Analysis Products

Preliminary Hazard List P Hazard Analysis SEE DRD P B U Hazard Reports P F SEE DRD SEE DRD

DRD-SM-04 Software Quality Assurance Plan P B U U DRD-SW-01 Software Management and Development Plan P B U

Major Actionable Events - Significant series of events such as tests that may occur in between life cycle reviews and its completion triggers an assessment of TPMs as required per DRD-TE-03: Technical Data Requirements and Reporting

DATA REQUIREMENTS DESCRIPTION

1.TITLE

Insight Implementation Plan (IIP)

2. NUMBER

DRD-PM-01 Rev A

3. USE

NASA will utilize the Contractor’s Insight Implementation Plan to ensure NASA personnel and its support services contractors can perform their insight.

4. DATE

February 19, 2021

5. DRD CATEGORY:

Program Management

6. DRD APPROVED BY

Gaudy Bezos-O’Connor

7. DUE DATE

Preliminary version with the Proposal (limit of 15 pages with proposal).

Baseline version no later than 60 days after ATP.

8. REFERENCES

NPR 7123.1C – NASA Systems Engineering Processes and Requirements, NASA/SP-2016-6105 Rev 2 – NASA Systems Engineering Handbook

9. PREPARATION INFORMATION

REFERENCE: NPR 7123.1C – NASA Systems Engineering Processes and Requirements, NASA/SP-2016-6105 Rev 2 – NASA Systems Engineering Handbook

FIRST SUBMISSION DATE: Preliminary with the Proposal (limit of 15 pages with proposal); Baseline version no later than 60 days after ATP.

SUBMISSION FREQUENCY: After baseline, updates to be submitted as needed.

ACCEPTANCE: Project Manager, Chief Engineer, Deputy Project Manager-Technology, Lead Systems Engineer

DISTRIBUTION: CO, COR

DATA PREPARATION INFORMATION

SCOPE:

The Contractor’s Insight Implementation Plan shall describe the partnering approach and establish a cooperative environment ensuring an effective working relationship between NASA and the Contractor dedicated to a successful EPFD demonstration during all phases of the project.

CONTENT:

The Contractor’s Insight Implementation Plan shall provide a description of the Offeror’s proposed approach to communications and coordination with NASA. The Insight Implementation Plan shall also describe the accommodations for providing Government personnel and its support services contractor(s) timely and open access to relevant data and information necessary to obtain a working-level understanding into Contractor’s activities. These activities include the approach to accommodating Government insight of technical and programmatic performance, including safety and mission assurance while allowing the Contractor to maintain the efficiencies and effectiveness of their normal commercial processes. The Insight Implementation Plan will describe approaches supporting Project Management and Technical Management, and establish processes and mechanisms for NASA to provide feedback and communicate issues and concerns for consideration and resolution.

Insight Implementation Plan (IIP)

2. NUMBER

DRD-PM-01 Rev A

The Insight Implementation Plan shall describe accommodating Government Insight while maintaining the efficiencies and effectiveness of Contractor established processes on the following:

1. Approach and content for NASA participation in Contractor-Led quarterly Project Management Reviews (PMR). The PMR will provide NASA with understanding and status on overall progress of contract activities including updates on programmatic cost and schedule, cost share burn down rate, progress on technical design and Technical Measurements (reference - Technical Measures of Effectiveness; EPFD-02-06) of the demonstration, awareness of waivers and deviations, and status of systems engineering, risk management, safety, quality assurance, flight operations, and airworthiness.

2. Approach for providing NASA participation and support of Contractor-Led Lifecycle Reviews and content for these reviews:

a. Contractor-Led Lifecycle Reviews will be conducted for the purpose of assessing programmatic and technical progress, plans and performance at key decision points and phases in the lifecycle. The reviews, to be defined by the EPFD provider, will be attended by the Government at the Contractor specified location.

b. Lifecycle reviews should include: System Requirements Review (SRR), System Definition Review (Optional and can be combined with SRR), Preliminary Design Review (PDR), Critical Design Review (CDR), Flight Readiness Review (FRR) (demonstrate airworthiness compliance prior to this review), Post Flight Assessment Review (PFAR) at the EPFD system and lower levels. If the lifecycle review has already been conducted, NASA will require evidence of completion of the review and delivery of associated DRDs through the appropriate review.

i. It is anticipated that offerors may be at various stages of design maturation, NASA will hold a SRR, regardless of the design maturation state and may reserve the right to conduct a review of an offerors said design maturation state.

c. Definition and execution of the Lifecycle reviews shall be in accordance with NPR 7123.1C – NASA Systems Engineering Processes and Requirements tailored utilizing industry practices and for application to a flight test demonstration.

d. The Contractor Lifecycle reviews should be tied to the project phases enabling the assessment of the project management and engineering design in each phase of the project lifecycle.

e. The Contractor-Led Lifecycle Reviews should be included in the Integrated Master Schedule.

f. As part of the review process, the Contractor shall provide a process for NASA to provide feedback and for the Contractor to respond.

g. Data Requirement Descriptions (DRDs) identified as deliverables during a particular phase

(Preliminary; Detailed Design; Fabrication, Build, Assembly and Test; and Integration and Demonstration) identified in the Integrated Data Requirements Description Document shall be provided as reviewable documents at the Contractor-Led reviews for the associated phase regardless of the data type assigned to the document.

h. Systems Engineering status to include systems requirements (new, modified, retired) and drawing metrics : plan vs actuals to date (these two metrics are GAO requirements)

3. Approach and content for bi-weekly Project Status meetings with the NASA Technical Monitor and EPFD Executive Team to status contract activities, highlighting changes in risk, cost, or schedule; present progress of key activities associated with the design, development, manufacture, integration, test, and verification for the demonstration; and provide updates in technical performance maturation of the Technical Measures of Effectiveness.

4. Approach for providing interaction at the WBS level (working level) to establish a strong partnership and NASA awareness on progress of systems engineering, risk management, safety, quality assurance, flight operations, and airworthiness activities. The Contractor defines frequency.

5. Approach for NASA to participate in critical configuration control and risk management boards.

Insight Implementation Plan (IIP)

2. NUMBER

DRD-PM-01 Rev A

6. Approach for NASA SME awareness and participation in key technical interactions such as critical engineering review boards, system integration reviews, test readiness reviews, post-test reviews, lower level design reviews, timely status/resolution of integration and test issues or anomalies, waivers and deviations, and timely status/resolution of issues or anomalies occurring during flight operations.

7. Approach for NASA SMA engagement and participation in critical safety & mission assurance review boards including mishap investigation boards, and processes to develop and outcomes of Contractor systems safety and hazards analysis.

8. Approach and content for the EPFD Final Closeout Meeting. The intent of this meeting is to report the overall progress and outcomes of the contract activities, the plan to move the resulting technology to a Vision Vehicle product, and the final assessment of the benefits of the technology demonstrated against the ARMD metrics in the Vision Vehicle implementation.

9. Approach and content for generation and delivery of the Monthly Progress Report (MPR) delivered monthly within 14 calendar days after end of the month and in MS Word format including the following content:

a. Project Manager’s overall status summary (technical, financial, schedule).

b. EVM overall status, variance explanations and corrective actions (for Cost Share only).

c. Updated cost share burn down rate.

d. Status of Measures of Performance (MOP) and Technical Performance Measures (TPMs) and any proposed corrective actions.

e. Summary of planned versus actual accomplishments since the previous report.

f. Overview of the requirement verification status (after CDR only).

g. Technical and programmatic issues and anticipated approaches for resolution.

h. A list of the waivers/deviations and the current status.

i. Status of open issues and problems from prior reporting periods.

j. Risk status for top 10 overall risks and their mitigations (with a 5x5 risk matrix and score sheets).

k. Status of action items with a focus on actions that are not closing in a timely manner.

l. Financial liens summary of encumbrances (realized liens), hard liens and soft liens.

m. Lower Tier Supplier status (performance, issues, risks, plans, surveillance audits).

n. Contractor Configuration Control Board (CCB) activities and status summary, including a summary of all Class I in-process and approved changes, and changes to the Applicable Documents List.

o. Integrated Master Schedule summary of current activities, critical path(s) and status.

p. DRD product status (product; status; baseline and actual (or planned) dates).

q. DRD products planned for delivery during the next reporting period.

r. Status on Lessons Learned, best practices and discoveries

s. Significant plans and activities for the next reporting period.

10. Plan for Strategic Communication and Public Outreach in partnership with NASA including the following elements:

a. Work closely with NASA to provide support for communications activities, including strategic communications, public affairs, media relations, employee communications, social media, public outreach, industry conferences and exhibit development.

b. Work closely with NASA to research, plan and implement communications or STEM engagement plans, products and campaigns, developing themes and messages to provide effective communication between NASA’s Aeronautics Research Mission Directorate, the EPFD project, and its stakeholders.

c. Work closely with NASA to plan and coordinate engagement activities, such as media or outreach events, attending them as needed and providing talking points or media facilitation support.

d. Biweekly or monthly imagery (video and photos) deliverable that can be used by NASA with proper credit.

e. Development of scale models of the contractors EAP testbed aircraft and a description of the model for delivery to NASA.

Insight Implementation Plan (IIP)

2. NUMBER

DRD-PM-01 Rev A

11. Approach and content for capturing Lessons Learned, best practices and discoveries throughout the lifecycle of the project including:

- Technical/ Technology Findings: Component design and development, sub-system and system design, development and integration

- Ground Demonstration Operations

- Flight Demonstration Operations

- Human System Integration

- Technical Performance (KPPs, TPMs, System Analysis)

- IT&E Operations

- Partnerships/Collaborations

- Airworthiness, Safety & Mission Assurance- Requirements, Reviews, Approvals

- Systems Engineering

- Communication & Organization

- Programmatic (contractual performance: cost, schedule and risk management)

- Formulation Activities and Reviews

- Procurement

- Project Unique

Note: The intent is to not execute more than one major review per month (Life-cycle Reviews and PMR). The PMR will be foregone when a life-cycle review and PMR occur on the same month. This does not preclude delivery of the MPR.

END OF DRD-PM-01 Rev A

Integrated Program Management Data Analysis Report (IPMDAR)

2. NUMBER

DRD-PM-02

3. USE

The IPMDAR is the primary means of communicating and reporting program cost and schedule information between the Contractor and the Government. The IPMDAR focuses on data, which can be used to regenerate human readable reports such as the NASA 533M and 533Q reports and IPMR/CPR Formats 1-4, as well as project management artifacts such as the Control Account Plan (CAP), Responsibility Assignment Matrix (RAM), WBS and OBS Structures and even to reconcile Work Authorization Documents (WAD), budget logs and the basis for integration.

4. DATE

February 11, 2021

5. DRD CATEGORY:

Program Management

6. DRD APPROVED BY

Gaudy Bezos-O’Connor

7. DUE DATE

See details within this DRD

8. REFERENCES

IPMDAR Implementation & Tailoring Guide, NPR 7120.5E, NASA/SP-2010-3404

9. PREPARATION INFORMATION

REFERENCE: Integrated Program Management Data Analysis Report (IPMDAR) Implementation & Tailoring Guide, 28 Oct 2020 (https://www.acq.osd.mil/evm/#/policy-guidance/guides-references), NPR 7120.5E NASA Space Flight Program and Project Management Requirements, NASA/SP-2010-3404 NASA Schedule Management Handbook (https://www.nasa.gov/sites/default/files/atoms/files/nasa_schedule_management_hand_book.pdf), , and IPM Policy & Guidance (www.acq.osd.mil/evm/#/policy-guidance/ipmdar-dei-ffs)

DATA ITEM DESCRIPTION:

See IPMDAR – Integrated Program Management Data and Analysis Report DID; DEI – Data Exchange Instructions: these documents are intended as a technical reference for computer programmers implementing software to support the exchange of data composing the IPMDAR datasets; and FFS – File Format Specification:

these documents provide specific direction for using the File Format Specification for the IPMDAR Contract and Schedule Performance Datasets to exchange performance data. (https://www.acq.osd.mil/evm/#/policy-guidance/ipmdar-dei-ffs) FIRST SUBMISSION DATE: The first submission in JavaScript Object Notation (JSON) format of CPD, SPD, and IMS in native schedule file, Latest Revised Estimate (LRE) and subcontractor reports are due within 15 calendar days after the end of the second full accounting period following the contract authority to proceed (ATP).

SUBMISSION FREQUENCY: Monthly for CPD, SPD and IMS in native schedule file, LRE and subcontractor reports by the 15th calendar day after the close of the Contractor's accounting month. Monthly Flash Formats of CPD, SPD and native scheduling file by the 10th calendar day after the close of the Contractor's accounting month;

and final monthly formats of CPD, SPD, and native scheduling file by the 15th calendar day after the close of the Contractor’s accounting month.

Planning Packages (ref: 2.3.2.1.7) Require submission of planning packages, if any.

Identify Summary Level Planning Packages (SLPPs), if any.

Control Account List (ref: 2.3.2.1.3.1) NASA has the option to determine custom field 1-10 field usage for Control Accounts to allow for integration and visibility determined by the program office.

Work Packages (ref: 2.3.2.1.4) NASA has the option to determine custom field 1-10 field usage for Work Package to allow for integration and visibility determined by the program office.

Detail Data (ref: 2.3.2.3) Report by work package, planning package, and summary level planning package.

Monthly deliverables will include time phased historical data from contract award.

SCHEDULE PERFORMANCE DATASET (SPD) INSTRUCTIONS:

Task/Activities (ref: 2.4.2.3) Task/Activity ID's must remain constant month over month and must be unique to all other ID's and not null. This is typically the case using the source scheduling software's Unique/Activity ID field, but if contractors’ processes allow for these ID's to change over time then contractor must resolve with appropriate workaround.

Custom/User-Defined Fields (2.4.3.1) NASA has the option to determine custom field 1-10 field usage for tasks to allow for integration and visibility determined by the program office.

Resources (ref: 2.4.3.2) If the contractor's internal process is to resource load the IMS then resource and assignment details are required in the Schedule Performance Dataset deliverable.

Relationships/Dependencies: 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. Reasons for exceptions related to predecessor and successor relationships other than “As soon as Possible” and, fixed dates and constraints other than "Finish to Start" shall be documented in a report.

Level of Effort (LOE) in the Schedule: If LOE tasks are excluded from the schedule, the Contractor must clearly document in an appropriate location how the cost and schedule for LOE effort is being planned and performance is being measured.

Schedule Margin: If schedule margin is included in the IMS, it must be as a defined task and clearly labeled as "Schedule Margin" or contingency. The number of schedule margin tasks should be minimal with most of the margin duration placed as the last task before the ending contract event or the end item delivery. Other acceptable locations for placing smaller amounts of schedule margin are prior to high-level project milestones, such as PDR, CDR, First Flight, etc.

Contractor's IMS health analysis. Use the Defense Contract Management Agency (DCMA) 14-point assessment and provide data/information to cover logic, leads, lags, Finish-Start relationships, hard constraints, high float, negative float, high duration tasks, invalid dates, resources, missed tasks, critical path test, critical path length index, and Baseline Execution Index

DATA REQUIREMENTS DESCRIPTION

1.TITLE

Integrated Program Management Data Analysis Report (IPMDAR)

2. NUMBER

DRD-PM-02

Earned Value Management (EVM) Plan

2. NUMBER

DRD-PM-03 Rev A

3. USE

The EVM Plan provides a description of the Project’s execution of the Integrated Program Management and Data Analysis Report (IPMDAR) specific to the EPFD Project.

4. DATE

February 19, 2021

5. DRD CATEGORY:

Project Management

6. DRD APPROVED BY

Gaudy Bezos-O’Connor

7. DUE DATE

Baseline due at proposal submission.

8. REFERENCES

ANSI/EIA-748, NFS 1852.234-1

NFS 1852.234-2

9. PREPARATION INFORMATION

REFERENCE: American National Standards Institute/Electronic Industries Alliance standard ANSI/EIA-748 Earned Value Management Systems (EVMS), NASA FAR Supplement (NFS) 1852.234-1 Notice of Earned Value Management System (APR [NOV] 2015) [(DEVIATION)], 1852.234-2 Earned Value Management System (APR [NOV] 2015) [(DEVIATION)]

FIRST SUBMISSION DATE: Baseline due at proposal.

SUBMISSION FREQUENCY: 60 calendar days after exercising significant contract options or a significant funding or work scope realignment.

ACCEPTANCE: CO, Project Planning & Control (PP&C) Lead

DISTRIBUTION: CO, COR, P&C Lead

DATA PREPARATION INFORMATION: The EVM Plan shall describe in narrative format the Contractor’s IPMDAR implementation.

CONTENT: The EVM Plan shall describe implementation plan to ensure accuracy and timeliness of Integrated Program Management Data Analysis Reports (IPMDAR) data, the management system to be used to generate cost/schedule performance measurement information, and how the plan is integrated with the IPMDAR cost and schedule management control system including configuration control of the baseline. The EVM Plan shall include the management IPMDAR procedures that are tailored for the applicability to the individual project needs to support effective decision making by both Contractor and EPFD Project Management.

The contractor EVM system that provides IPMDAR data from the contractor shall be Government-validated and a copy of the validation documentation is required. A contractor that proposes to use an EVMS previously accepted by the Government (compliance with NASA FAR Supplement (NFS) 1834) satisfy this requirement by citing the Advance Agreement (AA) or Letter of Acceptance (LOA) and providing a copy of the approved system description. A contractor not having a previously accepted system shall submit a Contractor EVMS Validation Plan to obtain EVM validation (refer to DFARS Clause 252.234- 7001 “Notice of Earned Value Management System” for a description of the plan).

CONTINUED

Earned Value Management (EVM) Plan

2. NUMBER

DRD-PM-03 Rev A

9. PREPARATION INFORMATION – Continued

For Firm Fixed Priced contract that are part of a NASA project valued at $100M or more, NASA will require appropriate data to fulfill project management needs and comply with NPR 7120.5e.

For Cost Share contract, NASA requires the use of an EVMS on acquisition for development work, including development or production work for flight and ground support systems and components, as specified below:

• For cost share contract valued at $100M or more, the contractor shall have an EVMS compliant with EIA- 748 determined by the cognizant Federal agency, e.g., DCMA

• For cost share contract valued at $20M or more, and less than $100M, the contractor shall have an EVMS compliant with EIA-748 determined by the Contracting Officer

• For cost share contract valued at less than $20M, EVM is optional and it will be a risk-based decision at the discretion of the NASA Project Manager

The Contractor shall submit a list of major (or critical) subcontractors and major (or critical) vendors that will include:

• Subcontract/Vendor Name

• Description of Product and Delivery Schedule

• Applicable WBS Code

• Purchase Order/Subcontract Value

• Subcontract Management Plan

Plan content shall include, but not limited to following:

• Introduction. Use of the IPMDAR as the primary means of communicating program cost and schedule information between the prime contractor and the Government

• Tailoring o Discuss how the IPMDAR can be tailored to meet the needs of EPFD o Show how the contractor is inputting and analyzing the data as a project management dataset to manage the contract’s performance Reporting discussion, at a minimum to include monthly, quarterly, and upon reaching a cost share burn down rate of 75% of NASA’s total cost share allocation, a joint Contractor-NASA Technical and Programmatic Work to Complete Review will be conducted.

• Discussion on the IPMDAR three components: Contract Performance Dataset (CPD), the Schedule Performance Dataset (SPD)), and the Performance Narrative o CPD discussion, at a minimum to include: WBS, Estimates at Completion, Cost Variance, Schedule Variance, Variance at Completion o SPD discussion, at a minimum to include: Milestones, critical paths, schedule drivers, schedule margin o Performance Narrative discussion, at a minimum to include: Executive Summary, Integrated Baseline Review, detailed analyses, cost share burn down rate, mitigation, descopes.

o Contractor Roles (including prime, subs, intra-government) o Electronic submission and files

FORMAT: MS Word.

END OF DRD-PM-03 Rev A

Configuration and Data Management Plan

2. NUMBER

DRD-PM-04 Rev A

3. USE

To describe the Contractor's method for accomplishing the configuration and data management requirements of the contract.

5. DRD CATEGORY:

Project Management

6. DRD APPROVED BY

Gaudy Bezos-O’Connor

7. DUE DATE

Outline version 28 days prior to IBR and Baseline version no later than 7 days prior to Integrated Baseline Review (IBR). Updates as needed/requested.

8. REFERENCES

EIA-649 National Consensus Standard for Configuration Management NPR 7120.5E NASA Space Flight Program and Project Management Requirements

9. PREPARATION INFORMATION

REFERENCE:

FIRST SUBMISSION DATE: Outline version 28 days prior to IBR and Baseline version no later than 7 days prior to Integrated Baseline Review (IBR). Updates as needed/requested.

SUBMISSION FREQUENCY: As indicated under due date. Updates as needed/requested.

ACCEPTANCE: PM, CE, CM/DM

DISTRIBUTION: CO, COR, PP&C Lead

DATA PREPARATION INFORMATION

SCOPE:

The Configuration and Data Management Plan (CDMP) describes the functions, responsibilities, and authority for the accomplishment and implementation of hardware, firmware and software configuration management to be performed during the hardware and software life cycles. This plan identifies the required coordination of configuration management activities with other activities of the project. This plan also identifies the tools and the physical and human resources required for the execution of the plan and should follow EIA-649 and NPR 7120.5E.

CONTENT:

The CDMP shall include, at a minimum:

1. Relationship of the Contractor’s management, organization and planning to the data management program and the

Contractor's other administrative and technical organizations.

2. Key elements of the configuration management process, including configuration change process, configuration item list, procedures for discrepancy reporting and tracking, process for waivers and deviations, documentation and data management, drawing control, configuration control boards and board processes, configuration management forms (e.g. configuration change request) and tools for tracking, reviews, and audits.

3. Integration of the Configuration Management (CM) and Data Management (DM) systems across all pertinent project elements such as modeling and simulation of vision product system and demonstration MW-class powertrain system , technical performance measures and test data measurements, systems engineering requirements, fabrication, component, sub-system and integrated MW-class powertrain system ground test and flight test configurations, ground and flight test operations, hardware and software quality control , as well as acquisition organizations’, including customer and vendors, Configuration and Data Management (CDM) systems.

1.TITLE:

Configuration and Data Management Plan (CDMP)

2. NUMBER

DRD-PM-04 REV A

4. Specific management policies, practices and work instructions to be used in implementing the data management program include the following elements:

a. Control procedures

b. Storage and retrieval procedures

c. Government access to data generated during contract performance using an interactive collaborative environment (or equivalent)

d. Preliminary and final data submittal schedules for fulfilling submittal of DRD data in the specified quantities, specific media (electronic, paper, other), and due dates required.

5. Records retention approach: The process includes a current Applicable Documents List and provides, at a minimum, reference to the Document Number, Document Title, Document Revision/Date, and source of direction to implement the document version (i.e. Contract, NASA directive, etc.). Changes to the Applicable Document List shall be submitted to the Government for awareness.

FORMAT: All configuration managed data should be tracked and recorded in Excel (ADL should be in Excel), the master CM plan can be provided in MS word or PDF.