SFD-01-22 Integrated Data Requirements Description Document-Baseline.pdf

DRAFT

SFD-01-22

Uncontrolled/Unofficial when printed. Official version located on https://nasagov.app.box.com/folder/134104123167?s=o52rjajgrfhqidcb7orodmdojkd3 8qcj

National Aeronautics and Space Administration

Sustainable Flight Demonstration (SFD) Project Integrated Data Requirements Description (DRD) Document

Date: September 15, 2021

SFD Integrated Data Requirements Description Document

Document No: SFD-01-22 Baseline Effective Date: September 15, 2021 Page iii

Uncontrolled/Unofficial when printed. Official version located on https://nasagov.app.box.com/folder/134104123167?s=o52rjajgrfhqidcb7orodmdojkd3 8qcj

TABLE OF CONTENTS

1.0 INTRODUCTION

1.1 Scope

1.2 DRD Content

2.0 GENERAL REQUIREMENTS

2.1 Data Requirements Descriptions (DRDs)

2.2 Document Change Log (DCL)

2.3 DRD Maintenance Procedures

NASA-Initiated Change

Contractor-Initiated Change

2.5 Data Types for Contractual Efforts

2.6 Subcontractor Data Requirements

2.7 Data Restrictions and Markings

2.8 DATA SUBMITTAL

2.9 Data Transmittal

Data shall be transmitted to NASA

Each data transmittal package shall include:

Document and Data Format

2.10 Document Identification

2.11 Reference to Other Documents and Data Descriptions in Data Submittals

3.0 DRD MAINTENANCE PROCEDURES

3.1 NASA-Initiated Change

3.2 Contractor-Initiated Change

4.0 CONTRACT DATA REQUIREMENTS LIST (CDRL)

4.1 Definitions

5.0 DATA REQUIREMENTS DESCRIPTION (DRD)

Effective Date: September 15, 2021 Page iv

APPENDIX A ACRONYMS

APPENDIX B TO BE DETERMINED AND TO BE RESOLVED ITEMS

Effective Date: September 15, 2021 Page v

List of Tables

Table 3 - List of Acronyms Table 5 - To Be Determined Items Table 6 - To Be Resolved Items

Effective Date: September 15, 2021 Page 1

1.0 INTRODUCTION

The Sustainable Flight Demonstration (SFD) Project is an Integrated Aviation Systems Program (IASP) Project in Pre-Formulation/Formulation and is slated for a formal FY22 start. The scope of the SFD Project is the development and flight test of a multi-technology flight demonstrator that enables the next generation single aisle commercial transport to meet global and NASA sustainable aviation goals and objectives. The project is responsive to Strategic Thrust 3, Ultra- Efficient Subsonic Transports Epoch 2, in the ARMD Strategic Implementation Plan and is one of a suite of projects contributing to the ARMD subsonic transport strategy. The ARMD subsonic transport strategy is constructed to align with an identified recapitalization opportunity for single aisle configurations in the early 2030’s. This opportunity requires a FY2026 first flight goal of the subsonic demonstrator. The SFD Project is currently working closely with industry to identify sustainable vision systems for introduction into the U.S. fleet, and associated candidate flight demonstrations needed to reduce barrier risks to introduction of the vision systems. This document will provide the overall guidance for identifying and maturing and retiring specific safety, acquisition, technical, cost and schedule risks associated with the flight demonstrator and the subsequent flight demonstration.

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 4.0 and attached hereto in Section 5.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 Content

This Integrated Data Requirements Description Document consists of a Introduction, General Requirements, DRD maintenance procedures, Contract Data Requirements List (CDRL), Definitions, and the DRDs.

Effective Date: September 15, 2021 Page 2

2.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.

2.1 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 5.0 of this document.

2.2 Document Change Log (DCL)

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

2.3 DRD Maintenance Procedures

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

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.

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.

Effective Date: September 15, 2021 Page 3

2.4 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.

2.5 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.

2.6 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.

Effective Date: September 15, 2021 Page 4

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:

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.

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.

Effective Date: September 15, 2021 Page 5

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.

2.7 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.

Whenever “days” is used throughout this document and the DRDs, we refer to business days.

2.8 Data Transmittal

This section provides additional detail regarding the transmittal and format of the DRDs 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

Effective Date: September 15, 2021 Page 6 who are responsible to receive, index, and store the data. The electronic files shall be in an unlocked, editable and searchable format where appropriate.

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.

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 and searchable, Adobe PDF format or Microsoft Office software (Word, Excel, PowerPoint, and Project).

c) Engineering drawings shall be in accordance with ASME Y14.100.

d) Format for 3D CAD models shall be in accordance with ASME Y14.41 and ASME Y14.47.

e) All MBx models shall be in SysML modeling language.

2.9 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

Effective Date: September 15, 2021 Page 7 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.

2.10 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 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.

3.0 DRD MAINTENANCE PROCEDURES

3.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.

3.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

Effective Date: September 15, 2021 Page 9

DATA REQUIREMENTS DESCRIPTION

1.TITLE

Manufacturing and Assembly Plan

2. NUMBER

DRD-AC-01

3. USE

This document establishes the overall plan, policies, approach, processes, and procedures for manufacturing and assembly of the SFD aircraft systems and subsystems.

4. DATE

July 22, 2021

5. DRD CATEGORY:

Aircraft

6. APPROVED BY

Fay Collier

7. DUE DATE

15 business days prior to Preliminary Design Review (PDR) (Draft) and 15 business days prior to Critical Design Review (CDR) (Baseline)

8. REFERENCES

DRD-SE-11

9. PREPARATION INFORMATION

REFERENCES: DRD-SE-11: Interface Control Documents (ICD)

FIRST SUBMISSION DATE: 15 business days prior to PDR (Draft) and 15 business days prior to CDR (Baseline)

SUBMISSION FREQUENCY: One-time submission, updated as necessary

APPROVED BY: NASA (Chief Engineer, Lead Systems Engineer)

DISTRIBUTION: Contracting Officer, Contracting Officer Representative, Chief Engineer, Lead Systems Engineer

DATA PREPARATION INFORMATION:

CONTENT: The Manufacturing and Assembly Plan shall include, at a minimum, the objectives, scope, manufacturing and assembly processes, flow, and approach (including subcontracted work), roles and responsibilities, materials, test fixtures and supporting hardware, inspection requirements, assembly and integration planned ICD (per DRD-SE-11: ICDs) interfaces verification (as applicable) and proposed delivery dates (overall manufacturing and assembly schedule). The Plan shall provide a description of the contractor’s manufacturing approach to include how the contractor will apply Model Based and Digital Engineering (if applicable).

FORMAT: Agreed to Content, Contractor’s Format, Microsoft Word

END OF DRD

Effective Date: September 15, 2021 Page 10

Aircraft System Performance Documents (ASPDs)

DRD-AC-02

The SFD Project expects that the ASPD and ASD deliverable(s) collectively define the SFD aircraft system and performance predictions.

4. DATE

August 11, 2021

5. DRD CATEGORY:

Aircraft

6. APPROVED BY

Fay Collier

7. DUE DATE

15 business days prior to Life Cycle Reviews as appropriate (as part of review package), or as otherwise requested

8. REFERENCES

9. PREPARATION INFORMATION

REFERENCES:

FIRST SUBMISSION DATE: 15 business days prior to Life Cycle Reviews (as part of review package), or as otherwise requested.

SUBMISSION FREQUENCY: Prior to each Life Cycle Review, or as requested

APPROVED BY: NASA (Chief Engineer, Lead Systems Engineer, Project Manager)

DISTRIBUTION: Contracting Officer, Contracting Officer’s Representative, Chief Engineer, Lead Systems Engineer, Project Manger

DATA PREPARATION INFORMATION:

CONTENT: The contents of the ASPDs should depict a clear characterization of the aircraft, system, and subsystem performance to the level of maturity commensurate to the life review level reached. The contractor shall collaborate with NASA to determine what assessments shall be conducted. (i.e. Aero. and aircraft performance, Propulsion, S&C/HQ, Loads/Stress (Structures), etc.). Provided below are examples of assessment requirements.

a) Aerodynamic/aircraft performance predictions including (trimmed and untrimmed) drag polars at key points within the aircraft operating envelope and potential off-nominal conditions. The Contractor shall include predictions at the predicted/actual range of aircraft weight, trim, altitude, and attitude including the corresponding boundary conditions for propulsion and vent flows. The Contractor shall consider aerodynamic performance variability due to changes in engine operating conditions as well as standard, non-standard, and local atmospheres. The Contractor shall use any combination of existing or proposed Computational Fluid Dynamics (CFD) predictions or wind tunnel testing to validate all aerodynamic performance and Stability and Control (S&C) models. The Contractor shall detail how the multiple data sources were used to arrive at the final performance and S&C data. The Contractor shall provide the wind tunnel model and transportation to and from the test facility. The Contractor shall validate and update, as required, aerodynamic performance and Stability and Control (S&C) models with wind tunnel and flight test data. The Contractor shall provide physics-based uncertainty models for aerodynamic and stability and control data that are compatible with the implementation of the aerodynamic models in the 6- DOF aircraft simulation software and provide a corresponding substantiation document for the delivered uncertainty models.

CONTINUED

Effective Date: September 15, 2021 Page 11

1.TITLE:

Aircraft System Performance Documents (ASPDs)

2. NUMBER:

DRD-AC-02

9. PREPARATION INFORMATION – Continued

CONTENT:

b. Demonstrator predictions at key points of the baseline mission profile at cruise Mach, weight, and angle of attack (beginning, middle, and end of cruise). Predictions shall include off-design lift and altitude, non-standard atmospheric conditions, propulsion system off-nominal operating conditions, aeroelastic effects, control surfaces, and controlled turns that might be included as alternates to the baseline mission.

c. Assessment of the integrated propulsion system flow path including installed propulsion system performance predictions at key points within the aircraft operating envelope (including deviations in angle-of-attack, sideslip) and potential off-nominal conditions. The Contractor shall deliver a Numerical Propulsion System Simulation (NPSS) engine deck/model of installed engine performance. The engine model shall include gross thrust, ram drag, and fuel flow. The gross thrust component shall include the effects of throttle-dependent drag, inlet spillage, bleed and bypass drag. The data shall also include Mach number effects from Mach 0.0 to 0.8 at increments of ≤ 0.1. The data shall include the effects of throttle setting for a minimum of 6 power level settings, and at altitudes up to 35,000 feet at increments of ≤ 5,000 feet. The data shall include the effects of temperature corresponding to standard and the AFRC Range Reference Atmosphere (RRA). The contractor shall contact NASA for a copy of the AFRC Range Reference Atmosphere (RRA).

d. Stability & control (S&C) and handling qualities (HQ) assessment and predictions at key points within the aircraft operating envelope and potential off-nominal conditions. The Contractor shall develop and refine a real-time 6 degree-of-freedom simulation capability to conduct the assessment above that also considers off-nominal conditions, including, but not limited to, simulated low-speed and transonic design cruise engine loss and recovery, flight control failures, and the influence of flexible mode dynamics. The Contractor shall use this simulation capability to assess flight control system requirements, architecture, design, weight/CG, and crew station considerations. The Contractor shall develop sufficient simulation fidelity and capability to reduce risks related to S&C / HQs / control laws and aircraft performance and provide the SFD Project with the most current SFD aircraft simulation models (e.g. aerodynamic model) to support the SFD Project simulation development and activities.

The contractor shall deliver a NASA approved standard/guidance (e.g. MIL-STND-1797B for a Class III vehicle) to conduct S&C / HQ / control law assessments and documents the S&C and HQ of the SFD aircraft to include control laws. The Contractor shall validate and update, as required, S&C and HQs predictions/data with Spiral 1 flight test data.

e) Loads and stress predictions at key points within the SFD V-n diagrams will be provided for each review detailing specific load cases considered. The results presented shall include shear, moment and torque plots vs. span and fuselage station or discrete loads for key design conditions and major aircraft components (wing, truss, fuselage, empennage, control surfaces, etc.). The results shall document the Margins of Safety (MS) as applicable. The contractor shall provide complete loads and stress finite element models (FEM) of sufficient accuracy for structural layout and sizing, load path evaluation, design and analysis of structural members, MS calculations, and weight prediction of the SFD aircraft. The contractor shall provide summaries of hand stress calculations as applicable. The Contractor shall include layout details in PATRAN or equivalent agreed to format and the FEM defined as a NASTRAN input deck with input load cases and material properties. The Contractor shall validate and update, as required, loads and stress predictions/data from ground and flight test data.

f) Static and dynamic aeroelasticity and structural dynamics analysis results will be presented for key points within the aircraft operating envelope and potential off-nominal conditions. The Contractor shall provide a structural dynamics FEM, as applicable, to perform a linear and non-linear aeroelastic analysis. Flutter analyses will be performed, as required, and the flutter models shall be provided. The Contractor shall provide flutter predictions, updated with ground vibration test data as applicable. The Contractor shall validate and update, as required, modal and aerodynamic data from ground and flight tests.

Effective Date: September 15, 2021 Page 12

Aircraft System Performance Documents (ASPDs)

2. NUMBER:

DRD-AC-02

9. PREPARATION INFORMATION – Continued

CONTENT:

g) Aeroservoelastic evaluations of sufficient fidelity to provide confidence in meeting margin requirements shall be provided.

f. Summary of updates made since prior delivery

FORMAT: Mutually agreeable format and filetypes.

Effective Date: September 15, 2021 Page 13

Aircraft Simulation Models and Data

DRD-AC-03

To develop a high-fidelity flight simulation.

4. DATE

August 17, 2021

5. DRD CATEGORY:

Aircraft

6. DRD APPROVED BY

Fay Collier

7. DUE DATE

NLT 40 business days prior to PDR (Draft) NLT 40 business days prior to CDR (Update) NLT 120 business days prior to FRR (Baseline) Updates as requested

FIRST SUBMISSION DATE: As indicated in “DUE DATE”

SUBMISSION FREQUENCY: As indicated in “DUE DATE”

APPROVAL: NASA (Contracting Officer Representative, Chief Engineer)

DISTRIBUTION: NASA (Contracting Officer, Contracting Officer Representative, Project Manager, Chief Engineer)

DATA PREPARATION INFORMATION: The Contractor shall deliver physics-based uncertainty models for aerodynamic and stability and control data that are compatible with the implementation of the aerodynamic models in the 6-DOF aircraft simulation software necessary for the development of a NASA operated, nonlinear, piloted, Hardware-in-the-Loop (HIL) simulation of the aircraft and its relevant subsystems. The models shall account for modeling uncertainty and include provisions for modeling key failure modes. Along with the models the contractor shall provide corresponding manuals and documentation on the formulation and verification and validation of the models delivered, including any lower level models (CFD, FEM, etc.)

or data used to generate the simulation models.

CONTENT: These data shall include models and data needed for implementation into a simulation environment and shall include but are not limited to the following:

a) Aerodynamic models and formulation

b) Engine model and formulation, which includes engine dynamics and relevant failure modes

c) Integrated performance data (installed engine/aero effects)

d) Sensor models, including relevant failure modes, anticipated noise levels, and anticipated response lags

e) Flight Control System model along with latency maps and relevant failure modes

f) Actuator models including relevant failure modes and hinge moment effects

g) Cockpit displays models

h) Landing gear model

i) Pilot inceptor model which documents forces, gradients, feel system dynamics, dead band, breakout forces, functionality, etc.

j) Structural models including structural dynamics and loads

k) Mass properties models

l) Fuel system transfer models

Effective Date: September 15, 2021 Page 14

Aircraft Simulation Models and Data

DRD-AC-03

9. PREPARATION INFORMATION – Continued

CONTENT:

a) Cockpit layout, CAD models of structure and interior of cockpit

b) Outer mold line model

c) Hydraulics systems models and relevant failure modes

d) Electrical systems models and relevant failure modes

e) Avionics and vehicle management system models including but not limited to:

a. Fault detection and Isolation functions including a Built-In-Test (BIT) function

b. Interface Control Documents (ICD)

c. Communication and intersystem wiring diagrams

d. Communication protocols (1553, ARINC-429, CAN, etc.) and interactions between major avionics subsystems

(Air data computer, Flight Control Computers, Mission Computers, ect.)

f) Uncertainty modeling for mass properties model, aerodynamic model, engine model, sensor models, and actuator models

g) Test cases by which Government simulations can be compared against contractor simulations. These test cases shall support point comparisons of aerodynamics, mass properties, and aircraft trim states, as well as dynamic time history and frequency response comparisons

FORMAT: The format(s) shall be mutually agreed upon by NASA and the contractor.

Effective Date: September 15, 2021 Page 15

Hardware-in-the Loop Simulation Representative Aircraft Hardware

2. NUMBER

DRD-AC-04

3. USE

For integration into the NASA simulator for hardware-in-the-loop testing.

4. DATE

August 6, 2021

5. DRD CATEGORY:

Aircraft Design

6. APPROVED BY

Fay Collier

7. DUE DATE

180 business days before FRR

8. REFERENCES

DRD-SE-11

9. PREPARATION INFORMATION

REFERENCES: DRD-SE-11 Interface Control Documents (ICD)

FIRST SUBMISSION DATE: As specified in “DUE DATE”

SUBMISSION FREQUENCY: As specified in “DUE DATE”

APPROVAL: NASA (Contracting Officer Representative, Chief Engineer)

DISTRIBUTION: NASA (Contracting Officer, Contracting Officer Representative, Project Manager, Chief Engineer)

DATA PREPARATION INFORMATION: The Contractor shall deliver engineering test units representative of the flight units used in the SFD Demonstrator aircraft along with documentation and any software required for NASA to integrate into closed-loop simulations, run hardware-in-the-loop simulations, and interface with the test units.

CONTENT: This deliverable shall include the hardware system (flight-like configuration) and software for use in the NASA simulator for hardware-in-the-loop testing. Contractor shall provide a list of cockpit hardware. Hardware items to be delivered for incorporation into the simulation shall be negotiated with NASA. Examples of cockpit hardware of interest include but are not limited to: mission control computers, flight management system, autopilot(s), actuators, flight control computers, air data computer, cockpit display components, etc.

FORMAT: Agreed upon format

Effective Date: September 15, 2021 Page 16

Aircraft Specification Documents (ASDs)

DRD-AC-05

The SFD Project expects the ASD and ASPD deliverable(s) to collectively define the SFD aircraft systems, subsystems and performance predictions

4. DATE

July 22, 2021

5. DRD CATEGORY

Systems Engineering

6. APPROVED BY

Fay Collier

7. DUE DATE

15 business days prior to a Life Cycle Review (as part of review package) or as requested

FIRST SUBMISSION DATE: 15 business days prior to first Life Cycle Review (as part of review package), or as otherwise requested

SUBMISSION FREQUENCY: 15 business days prior to each Life Cycle Review, or as requested

APPROVED BY: NASA (Chief Engineer, Lead Systems Engineer, Lead Operations Engineer)

DISTRIBUTION: Contracting Officer, Contracting Officer Representative, Chief Engineer, Project Manager, Lead System Engineer, Lead Operations Engineer

OTHER DELIVERABLES:

DATA PREPARATION INFORMATION:

CONTENT: The contents of the ASD’s will depict a clear characterization of the aircraft, system and subsystem to the level of maturity commensurate to the life cycle review level reached and shall include at a minimum:

a) Concept renderings, three view images with dimensions (as appropriate), and internal arrangement drawings for open dissemination.

All associated models used in the assembly model.

b) Outer/inner Mold Lines (OML/IML) - watertight computer-aided design (CAD) solids/surfaces in .step, .iges, and CAD native file formats with fewer than 100 surface patches. These CAD solids/surfaces shall include a triangulated surface mesh of the OML with defined propulsion and other boundary conditions required for computational assessments or validations.

c) Data provided shall be delivered for the SFD Project to have sufficient insight to conduct independent analyses, operate, and make modifications, as needed, over the life of the contract. This shall include engineering models in agreed-upon formats for the systems in the aircraft.

Effective Date: September 15, 2021 Page 17

Aircraft Specification Documents (ASDs)

2. NUMBER:

DRD-AC-05

d ) CAD-driven drawings and drawing files of the design/modifications to the assembly level suitable for a fabricator. Drawing tree structure and list of configuration items (CIs).

e) Computer-aided engineering (CAE) (e.g. finite element method [FEM] or finite element analysis [FEA], etc.), and computer-aided manufacturing (CAM) models shall be prepared and delivered in their agreed to filetype, standards, and templates.

f) Mass properties documents and aircraft weight statement that include center of gravity position and moments of inertia at any fuel state. The weight statement shall track predicted/actual weights, margins, and document the source and fidelity of the weights.

g) Master Equipment List (MEL) including all replaceable components used on the aircraft including their manufacturer, model, and serial and part number. This includes any GFE and Contractor-procured support equipment.

h) List of all reference coordinate systems used in the development of the aircraft system. This would include structural, aerodynamic, navigation, and other references used for the various aircraft systems, disciplines, sets of analyses, or manufacture and assembly.

i) Internal/external interface definition(s) as requested and defined in DRD-SE-11: Interface Control Documents.

j) Contractor provided structural and static/dynamics loads/stress analyses and models (Finite Element Modeling (FEM), and Finite Element Analysis (FEA)), for the aircraft and subsystems and any unique support equipment built by the Contractor for the SFD aircraft system.

k) Flight control design including at least diagrams and source code (e.g., C++ or Simulink models) sufficient for conducting control system analyses and studies. The control system definition shall include all flight control functions from pilot inputs to control surface deflections, including feedbacks, regulators, autopilots, control allocation / mixer, and models used in the flight controls. Models used in the flight controls shall include onboard aerodynamic models, scheduled flight control system parameters, flight control system gains, filters, and sensor and actuator models.

l) Contractor provided subsystem data resulting from ground tests and simulations as specified in DRD-SE-14: Post Test Reports to include test data, test plans, reports, and “as run” procedures produced during subsystem design, development and verification phases as requested by NASA (e.g., subsystem environmental test, software tests, hardware-in-the-loop tests, structural tests).

m) Summary of updates made since prior delivery.

n) The Contractor shall use the United States Customary Units (USCU) – length (ft), force (lbf), temperature (deg F), mass (slug), and time (s) as the primary set of units. Equivalent SI units can accompany the USCU unit, but it shall be shown in parentheses (i.e 3.0m).

FORMAT: Format for CAD models/drawings shall be in accordance with ASME Y 14.24, Y14.35, Y14.41 and Y14.47, 14.5 and delivered in Government’s specified native and neutral formats.

All engineering drawings shall be delivered in native CAD, machine-readable, searchable, portable document format (PDF), and agreed to neutral formats.

Filetypes are to be agreed upon unless otherwise stated. Documents are in a mutually agreeable format.

Effective Date: September 15, 2021 Page 18

Aircraft System Description Document (ASDD)

2. NUMBER

DRD-AC-06

3. USE

This document is intended to present/describe the relevant features of the SFD demonstrator aircraft system. This includes a high-level view of the features, capabilities, schematics, illustrations, system-level architecture, interfaces, and related performance.

4. DATE

July 22, 2021

5. DRD CATEGORY

Systems Engineering

6. APPROVED BY

Fay Collier

7. DUE DATE

60 business days following PDR (Draft), 15 business days prior to CDR (Baseline), updates as needed or requested by NASA

FIRST SUBMISSION DATE: 60 business days following PDR (Draft), 15 business days prior to CDR (Baseline), updates as needed and as requested by NASA SUBMISSION FREQUENCY: submitted once then updates as requested APPROVED BY: NASA (Chief Engineer, Lead System Engineer, Lead Operations Engineer) DISTRIBUTION: Contracting Officer, Contracting Officer Representative, Chief Engineer, Lead Systems Engineer, Lead Operations Engineer

DATA PREPARATION INFORMATION:

CONTENT: The System Description Document describes the design goals and considerations, provides a high-level overview of the system architecture (hardware and software) and traceability to the requirements, and describes the data associated with the system, as well as a high level description of the of the interfaces and operational scenarios. At a minimum, the ASDD shall include:

Section 1 Scope

1.1 Introduction

1.2 Aircraft System Overview/Purpose/Features

Section 2 Referenced Documents

2.1 Government References

2.2 Non-Government References

Section 3 Aircraft System Design

3.1 Aircraft System Architecture

3.2 Aircraft Product Hierarchy (i.e Product Breakdown Structure (PBS))

3.3 Interface Design

3.4 Design traceability to System Requirements

Effective Date: September 15, 2021 Page 19

Aircraft System Description Document (ASDD)

DRD-AC-06

Section 4 Aircraft System Elements Section 5 Appendices

• Appendix A – Definitions

• Appendix B - Acronyms, Abbreviations

EXAMPLE Table of Contents (ASDD)

1 Scope

1.1 Introduction

1.2 Aircraft System Overview/Purpose/Features

2 Reference Documents

2.1 Government References

2.2 Non-Government References

3 Aircraft System Design

3.1 Aircraft System Architecture

3.2 Aircraft Product Hierarchy (i.e Product Breakdown Structure (PBS))

3.3 Interface Design

3.3.1 Internal Descriptions

3.3.2 External Descriptions

3.4 Design Traceability to System Requirements

4 Aircraft System Elements

4.1 Auxiliary Power Subsystem (APS)

4.2 Hydraulic Subsystem (HYD)

4.3 Lighting Subsystem (LGT)

4.4 Fire Protection Subsystem (FPS)

4.5 Environmental Control Subsystem (ECS)

4.6 Propulsion Subsystem (PRP)

4.7 Vehicle Management Subsystem (VMS)

4.8 Fuel Subsystem (FLS)

4.9 Electrical Power Subsystem (EPS)

4.10 Cockpit Systems (CSS)

4.11 Airframe Subsystem (ARF)

4.12 Avionics Subsystem (AVS)

4.13 Landing Gear Subsystem (LDG)

5 Appendix Appendix A Acronyms Appendix B Definitions

FORMAT: Contractor’s format, Filetype: Microsoft Word

Effective Date: September 15, 2021 Page 20

Aircraft Subsystem Description Document (SSDD)

2. NUMBER

DRD-AC-07

3. USE

This document is intended to present/describe the relevant features of the Sustainable Flight Demonstrator (SFD) Aircraft Subsystems. This includes a high level overview of the SFD Subsystem, major components, equipment information ,etc., schematics, illustrations, capabilities, which provides the reader with a general understanding of the SFD subsystems and its traceability to subsystem requirements and to the to the overall system architecture.

4. DATE

July 22, 2021

5. DRD CATEGORY:

Aircraft

6. APPROVED BY

Fay Collier

7. DUE DATE

60 business days following PDR (Draft), 15 business days prior to CDR (Baseline), updates as needed and as requested by NASA.

FIRST SUBMISSION DATE: 60 business days following to PDR (Draft), 15 business days prior to CDR (Baseline), updates as needed and as requested by NASA

SUBMISSION FREQUENCY: Once, updates as needed/requested

APPROVED BY: NASA (Chief Engineer, Lead System Engineer, Lead Operations Engineer)

DISTRIBUTION: Contracting Officer, Contracting Officer Representative, CF, Lead Systems Engineer, Lead Operations Engineer

DATA PREPARATION INFORMATION:

One SSDD per aircraft subsystem. Describes capabilities, functions, interfaces, schematics, illustrations and any other pertinent information to describe the subsystem.

CONTENT: The Subsystem Description Document describes each subsystem design goals and considerations, provides a high-level overview of the subsystem architecture (hardware and software) and traceability to the requirements, and describes the data associated with the subsystem, as well as a high level description of the interfaces and operations that impact that subsystem. At a minimum the SSSD should include:

1.0 Scope

1.1 Introduction

1.2 Subsystem Overview/Purpose/Features

2.0 Reference Documents

2.1 Government References

2.2 Non-Government References

3.0 Subsystem Design

3.1 Subsystem Architecture

3.2 Concept of Subsystem Operations

3.3 Major Subsystem Capabilities

Effective Date: September 15, 2021 Page 21

Aircraft Subsystem Description Document (SSDD)

DRD-AC-07

3.4 Subsystem Component Descriptions

3.5 Interface Design

4.0 Appendices

Appendix A Definitions Appendix B Acronyms

An example of a Fuel System SSDD Table of Contents is provided below:

EXAMPLE Table of Contents (SSDD) 1 Scope

1.1 Introduction

1.2 Subsystem Overview/Purpose/Features

2 Reference Documents

2.1 Government References

2.2 Non-Government References

3 Subsystem Design

3.1 Design Decisions Made

3.2 Subsystem traceability to Subsystem Requirements

Subsystem Architecture

3.2 Where it fits within the Aircraft Architecture

3.3 Subsystem Architecture

3.4 Concept of Subsystem Operation

3.3 Major Subsystem Capabilities

3.3.1 Fuel Storage

3.3.2 Fuel Pressurization

3.3.3 Refuel/Defuel

3.3.4 Engine Feed

3.3.5 Fuel Transfer

3.3.6 Fuel Quantity System.

3.3.7 Fuel Balance Control

3.4 Subsystem Component Descriptions

3.4.1 Fuel Boost Pump

3.4.2 Electric Fuel Transfer Pump

3.4.3 Motive flow transfer Pumps

3.4.4 Vent & Pressurization Valve

3.4.5 Overpressure Relief

3.4.6 Negative Pressure Relief

3.4.7 Fuel Flow Proportioner

3.4.8 Refuel and Defuel Receptacle

Effective Date: September 15, 2021 Page 22

Aircraft Subsystem Description Document (SSDD)

DRD-AC-07

CONTENT: Continued

3.4.9 Wing Fuel/Water drain

3.4.10 Fuselage Fuel/Water Drain

3.4.11 Refuel Shutoff Valve Set

3.4.12 Motor Operated Shutoff Valve

3.4.13 Solenoid operated Control valves

3.4.14 Fuel Flow Transmitter

3.4.15 Fuel Flow Indicator

3.4.16 Fuel/Oil Heat Exchanger

3.4.17 Fuel Diverter valve

3.4.18 FADEC cooling shutoff valve

3.4.19 Hot Fuel Temp Sensor

3.4.20 Fuel Quantity Probes

3.4.21 Fuel Quantity Conditioner

3.4.22 Fuel Low Level Sensing System

3.4.23 Cockpit Systems

3.5 Interface Design

3.5.1 Internal Descriptions

3.5.2 External Descriptions

4 Appendices A Definitions B Acronyms, Abbreviations

FORMAT: Contractor’s format; Microsoft Word

Effective Date: September 15, 2021 Page 23

Cockpit Design Documentation

2. NUMBER

DRD-AC-08

3. USE

For building up the AFRC training sim to match the as-built aircraft.

4. DATE

August 6, 2021

5. DRD CATEGORY:

Aircraft Design

6. APPROVED BY

Fay Collier

7. DUE DATE

NLT 24 months before FRR

DRD-SE-11

REFERENCES: DRD-SE-11 Interface Control Documents (ICD)

FIRST SUBMISSION DATE: As specified in “DUE DATE”

SUBMISSION FREQUENCY: As specified in “DUE DATE”

APPROVAL: NASA (Contract Officer Representative, Chief Engineer)

DISTRIBUTION: NASA (Contract Officer, Contract Officer Representative, Project Manager, Chief Engineer)

DATA PREPARATION INFORMATION: The Contractor shall deliver initial designs/documentation of the aircraft cockpit with notional part numbers and functionality. Regular updates with any changes to the design or function of the cockpit shall also be provided through the course of the simulator and aircraft buildup.

CONTENT: This deliverable shall include but not limited to: 3D models, ICDs and parts lists along with any other design documentation used to finalize the design/function of the cockpit. Any custom made parts or parts with lead times greater than 8 weeks required for the simulator (as determined by NASA) shall be provided for simulation use.

FORMAT: Agreed upon format

Effective Date: September 15, 2021 Page 24

Digital Mock-up Unit (DMU)

2. NUMBER

DRD-AC-09

3. USE

Digital Mock-Up (DMU) is a term that refers to a full product description usually as a 3D model in an engineering environment and spans the whole product lifecycle: design, test, manufacturing, inspection and QA, installation, maintenance, disposal, etc. The DMU can involve checking the overall geometry with regard to dimensions and shape, interference checks, and collision checks for assembly and disassembly, as well as design space checks.

A distinction is made between static and dynamic DMU analysis. In the case of static DMU, an examination of the static parts is performed. In the case of dynamic DMU, the dynamic parts or assemblies are examined.

4. DATE

August 17, 2021

5. DRD CATEGORY:

System Engineering

6. APPROVED BY

Fay Collier

7. DUE DATE

DMU: 40 business days prior to CDR (initial); Final As part of the Data Acceptance Package. The light-weight viewable is due 40 business days prior to CDR, SAR and as requested by NASA.

8. REFERENCES

DRD-SE-03, DRD-SE-04

9. PREPARATION INFORMATION:

REFERENCES: DRD-SE-03 MBE and MBSE Data Requirements Description, DRD-SE-04 MBx Modeling Plan

FIRST SUBMISSION DATE: DMU 40 business days prior to CDR (initial); Light-weight viewable 40-business day prior to CDR.

SUBMISSION FREQUENCY: 40 business days prior to CDR (initial); Final As part of the Data Acceptance Package. The light-weight viewable is due 40 business days prior to CDR, SIR, SAR and as requested

APPROVED BY: NASA (Chief Engineer, Project Manager, Lead Operations Engineer)

DISTRIBUTION: Contracting Officer, Contracting Officer Representative, Chief Engineer, Project Manager, Lead Operations Engineer

DATA PREPARATION INFORMATION:

CONTENT: The integrated system DMU assembly model shall be an independent model that combines elements from the installation model and the Contractor’s end item models. The integrated system, subsystem, or element top assembly DMU model shall not contain simplified model representations. The integrated system of systems DMU (highest level assembly) model shall use a common skeleton structure definition for placement of major elements and their derivative model representations, i.e. a simplified representation. A simplified representation is not a Creo Parametric™ (or other CAD) native simple representation (however, these may be created from a simple representation) but is an accurate single surface, water-tight contiguous body representing the nominal “as-designed” configuration or structure. A simplified representation used for space and weight shall determine weight and center of gravity (cg), either as computed or assigned. Keep-out zones and other volume simulators shall be separate models located per the common skeleton structure. The contractor shall deliver a light-weight viewable derived from the integrated top assembly model set. The light-weight viewable format shall be jointly agreed to.

FORMAT: Jointly agreed to.

Effective Date: September 15, 2021 Page 25

SFD Environmental Specifications of Electronics (SESE)

2. NUMBER

DRD-OP-01

3. USE

This document is used to identify the environmental specifications for uncertified FAA electrical/electronic components used in the SFD aircraft. This document will identify the design specifications of a component or assembly and document the temperature, pressure, and vibrational environments it will be installed and used for.

4. DATE

July 29, 2021

5. DRD CATEGORY:

Systems Engineering

6. APPROVED BY

Fay Collier

7. DUE DATE

15 business days prior to CDR (Draft) and 15 business days prior to System Acceptance Review (SAR) (Baseline)

FIRST SUBMISSION DATE: 15 business days prior to CDR (Draft) and 15 business days prior to System Acceptance Review (SAR) (Baseline)

SUBMISSION FREQUENCY: One-time submission, updated as necessary

APPROVED BY: NASA (Lead Operations Engineer, Chief Engineer, Lead Systems Engineer)

DISTRIBUTION: Contracting Officer, Contracting Officer Representative, Chief Engineer, Lead Systems Engineer, Lead Operations Engineer

DATA PREPARATION INFORMATION:

CONTENT: The contractor shall provide a list of electrical/electronic components that have not been certified via the appropriate FAA approval process for use in an aircraft or in an uncertified application. This list shall have as a minimum the environmental specifications or qualification data for temperature, pressure, and vibration that have been met and the anticipated operational environment of the component for temperature, pressure and vibration. In addition, the list shall state the anticipated environment in the zone (place) where the electrical/electronic component is installed.

The Environmental requirements are located in the contractor’s SFD Detailed Ground Test Plan (DRD-SE-12).

FORMAT: Contractor format in Microsoft Word

Effective Date: September 15, 2021 Page…