1 - AVTPE-GRS-SOWr11.pdf

STATEMENT OF WORK

Commercial Supersonic Technology (CST) – Acoustic Validation, Test Preparation, and Execution (AVTPE) – Ground Recording

System (GRS) Project

National Aeronautics and Space Administration

Armstrong Flight Research Center

Edwards, California 93524

RFP/Contract No. Ground Recording System Statement of Work

April 7, 2020

Table of Contents

1. Background & Introduction

1.1 Supersonic Ground Acoustic Signatures

2. Scope

2.1 GRS Versioning

3. Statement of Work (SOW) Attachments

4. Goals/Objectives

5. Requirements

6. Deliverables & Delivery Schedule

6.1 Hardware

6.2 Documentation

6.3 Software

7. Acceptance Criteria

8. Security / Cybersecurity Requirements

9. Period of Performance (POP)

10. Travel / Meetings

11. Other Special Requirements & Considerations

11.1 GRS Equipment Identification

List of Figures

Figure 1: Mach Cone

Figure 2: Sonic Boom Pressure Wave

List of Tables

Table 1: Schedule of GRS Testing and Use Table 2: Terminology Definitions Table 3: Supporting Documentation

Table 4: GRS Contractor Responsibilities Matrix Table 5: Software Documentation Table 6: GRS Deliveries

Table 7: Hardware Documentation Table 8: GRS Operations Manual(s) Table 9: Travel / Meetings

List of Appendix

A. Appendix – Design Review Requirements B. Appendix – Associate Contractor Agreement

REVISIONS

Revision

Number Date Brief Summary of Changes Author

Base 04/07/2020 Initial Release S.

Yarbrough

1. Background & Introduction

NASA’s Aeronautics Research Mission Directorate (ARMD) strategy is guided by six strategic thrusts identified in response to three overarching drivers that will, in large part, shape the needs of aeronautical research in the coming years. These drivers and thrusts are described in the ARMD Strategic

Implementation Plan (SIP) (http://www.aeronautics.nasa.gov/strategic-plan.htm).

In the near term (2015–25), Strategic Thrust 2, Innovation in Commercial Supersonic Aircraft, outlines the ARMD objective of enabling the establishment of a standard for acceptable overland supersonic flight, in cooperation with international standards organizations. ARMD will develop and validate analysis tools and technologies intended to enable the design and development of supersonic aircraft with low sonic boom. In the longer term (2025–35), ARMD will continue research on technologies required to meet the desired boom level in larger aircraft but will also conduct research in areas related to other challenges to successful supersonic transports.

Under NASA ARMD’s Advanced Air Vehicles Program (AAVP), the Commercial Supersonic

Technology (CST) Project provides the research and leadership to achieve ARMD’s objectives in

Strategic Thrust 2. ARMD has formed research themes that support the desired outcomes for this strategic thrust (see the ARMD SIP link above). Within these research themes, the CST Project focuses a majority of its research on certain key Technical Challenges that are viewed as enabling to the

Strategic Thrust 2 near-term outcomes. The recent Technical Challenges are:

1. LBFD Prediction Validation Tools (ProViT) (CST TC 1.2);

2. Community Response Metric & Methodology (CST TC 2.1); and

3. Community Test Planning and Execution (CST TC 2.2)

Based on the long trajectory of supersonic research over the past few decades, a consensus has emerged that the next required step towards achieving the goals of the Strategic Thrust 2 near-term objective and

CST Project Technical Challenges is to design, build and test a large-scale flight demonstrator.

To that end, the Low-Boom Flight Demonstration mission (LBFD) is comprised of work conducted by the Low Boom Flight Demonstrator project and CST Projects, combined with key capabilities and assets from the Flight Demonstration and Capabilities (FDC) Project. The LBFD project objectives will be achieved through the design, construction, and flight validation of a research aircraft called the X-59

Quiet SuperSonic Technology (QueSST) demonstration aircraft with the capabilities required to conduct effective community response studies. The X-59 will create a shaped sonic boom signature with a calculated loudness level of 75 PLdB (Perceived Level dB) or less during supersonic cruise (Mach ≥

1.4) flight. Although the aircraft will be smaller in size than future supersonic airliners, its sonic boom ground signature will be traceable to that of the larger aircraft. The X-59 will be capable of meeting the

LBFD mission requirements of performing multiple supersonic overflights of a single community with passes that are nominally 50 miles in length, and up to 20 minutes apart on a single flight.

The LBFD mission consists of three phases. The first phase, currently in progress, focuses on the design, fabrication and initial flight testing of the X-59 research aircraft. The second phase, anticipated to start early in calendar year (CY) 2022, will focus on validating the supersonic acoustic characteristics of the X-59. The third phase, anticipated to start early in CY2023 and conclude in 2026, will consist of a series of community test campaigns in different locations in the US and potentially internationally.

The CST Acoustic Validation, Test Preparation, and Execution (AVTPE) effort is the data collection component to complement Phase 2 of the LBFD project. The primary objective of LBFD Phase 2 is to verify that the boom loudness on the ground is acceptable for community response testing and to gather airborne and ground data that will be used to validate sonic boom propagation and acoustics models in a real atmosphere. LBFD Phase 2 will be broken up into three sub-phases, A, B and C.

In preparation for the LBFD mission community response testing in Phase 3, NASA will conduct a flight research campaign named Phase 2B to verify the loudness levels of the X-59 and to validate low-noise sonic boom design tools. The results of this effort will go toward determining the readiness for community response testing. LBFD Phase 2B is where large numbers of GRS units are required.

The CST Community Test Planning and Execution (CTPE) technical challenge is focused on Phase 3 of the LBFD mission. The primary objective of LBFD Phase 3 is to collect a database of community response/annoyance to boom loudness, which will be used to develop models of how human annoyance grows as a function of loudness level. To collect the data, the National Aeronautics and Space

Administration (NASA) is planning a national campaign of 4 to 6 community overflight tests using the

X-59 aircraft. Each community overflight test will last about a month. The test series will occur in approximately the 2023 to 2026 timeframe, with approximately two tests in different locations per year.

1.1 Supersonic Ground Acoustic Signatures

An aircraft flying at supersonic speeds generates a pattern of shock waves that travel away from the aircraft in all directions. The intersection with the ground of the shock pattern existing at a specific instant is hyperbolic in shape (figure 1). As time elapses, this intersection travels along the ground behind the supersonic aircraft making a two-dimensional effected region known as the carpet.

Atmospheric factors and flight conditions affect size and position of the carpet relative to the flight path of the aircraft. Typically, the carpet can be up to 50 miles wide and is centered along the full length of the supersonic flight path.

The ground overpressure signature for current supersonic aircraft in cruise is called an N-wave because the shape of the pressure wave is similar to the capital “N” letter. All the shock waves coalesce into two pressure jumps separated by an expansion before reaching the ground. A U-wave shape is produced during the acceleration and maneuvers. When either wave form propagates through turbulence in the atmosphere, noise is added to the wave forms sometimes rounding the sharp edges making them quieter and sometimes spiking them louder.

In cruise, all existing supersonic aircraft generate N waves, often with a lower amplitude U wave after. In linear acceleration and maneuvering, a U wave can be produced which can be louder, sometimes 10 times the amplitude of the N wave, when the N and U wave combine to make a focused boom. Aircraft shaped to lessen the intensity of the pressure wave produce more of a sinusoidal with a much lower amplitude (see figure 2). It is intended that the GRS will record all of these variations in waveforms.

2. Scope

NASA - Armstrong Flight Research Center (AFRC) requires a specialized audio recording system capable of capturing high resolution acoustic data from sonic booms or waveforms with characteristics similar to sonic booms except with significantly lower amplitudes. Multiple units of this system

(Ground Recording System; referred to as ‘GRS units’ in the remainder of this document) will be deployed outdoors and mostly unattended at different test sites throughout the USA in support of

NASA’s LBFD mission. There may be occasions where the GRS units may be deployed outside the

USA.

Figure 1: Mach Cone

Figure 2: Sonic Boom Pressure Wave

Deployment environments will range from hot and dry (e.g. the Mojave Desert in California) to hot and humid (e.g. southern Florida) to cold and dry or humid (e.g. the northern Midwest or Northeast). The

GRS units will be set up and left in these environments for days or weeks at a time.

While LBFD Phase 2B and LBFD Phase 3 will depend on rapidly and efficiently acquiring ground signature data from supersonic overflight of existing supersonic military aircraft and the X-59 Quiet

Supersonic Technology (QueSST) aircraft, the requirements for the GRS units in the two phases differ;

LBFD Phase 2B requiring a base GRS unit with LBFD Phase 3 requiring GRS units with significant upgrades dealing with communications and data processing.

For LBFD Phase 2B the intent is to use GRS units to capture detailed acoustic data from the full width of the carpet of the X-59 aircraft. LBFD Phase 2B will deploy multiple GRS units in a 30-mile linear array in the Mojave Desert, perpendicular to the aircraft’s flight path. Additional GRS units will be deployed parallel to the flight path to capture variation in the ground signature due to atmospheric turbulence. The acoustic signal will reach each GRS in the array at a different time requiring either a different recording initiation time or sufficient recording duration to capture the entire waveform and ambient noise before and after the event. Seventy (70) GRS units will be used for the LBFD Phase 2B ground measurements.

Prior to LBFD Phase 2B testing, NASA plans two developmental test campaigns for the GRS units

Carpet Determination In Entirety Measurements (CarpetDIEM) and LBFD Phase 2 Dry Run. These tests will take place out of NASA-AFRC and will use an existing NASA supersonic aircraft to generate the acoustic signals.

To accomplish LBFD Phase 2B testing within our timeline and to prepare for LBFD Phase 3, we require the GRS units be delivered in incremental deliveries starting with an initial GRS unit we are calling

Version 1 for LBFD Phase 2B then increasing in capabilities to the final production GRS unit called

Version 2. By final delivery, as shown in Table 6: GRS Deliveries, all GRS units will be upgraded / modified to be at the same version. The versions are described in Section 2.1 GRS Versioning.

For LBFD Phase 3, the intent is to use up to 150 GRS units to record the detailed acoustic data generated by the X-59 aircraft over an area of up to 2500sq miles. In support of the deployed GRS units will be 25 spare units as backups, for a grand total of 175 GRS units needed for a full deployment.

2.1 GRS Versioning

LBFD Phase 2B and LBFD Phase 3 have different demands of the GRS units. LBFD Phase 2B only requires the core essentials of the GRS units; while LBFD Phase 3 requires increased computing, long-haul communications and full remote operations. To allow incremental testing throughout the development of the GRS units, a staged approach will be taken. To best define this staged development, we are calling LBFD Phase 2B GRS capabilities as GRS units Version 1 and LBFD Phase 3 GRS capabilities as GRS units Version 2. In Table 1: Schedule of GRS Testing and Use our development and testing is laid out in seven (7) stages. Prior to Stages 1 & 4 NASA will require the contractor to conduct a CDR (Critical Design Review). After Stages 1 & 4 requirements validation testing, but before

Stages 2 & 5, NASA will hold a Post Test Review with the contractor to discuss test results and findings. The version requirements and delivery schedule are presented in Table 6: GRS Deliveries.

The GRS units shall have the ability to record sonic boom signatures in an accurate, precise, secure (data storage) and timely fashion at ground level. Fast easy access (either human retrieval or a high bandwidth link) to the boom recording files is required so the acoustic data profiles can be available for timely analysis. A crucial data point required for accurate analysis is the GRS units own precise geographic location.

The GRS will be operated in a wide range of environmental conditions, defined in the GRSSRD as

“harsh environments,” heavy rainfall, “severe weather conditions,” etc.

GRS units shall be capable of maintaining a proper charge to its power system to continue to operate and communicate without the need of human intervention to change out a power pack for an extended period of time. When deployed, the GRS units shall be unattended making security of the enclosure(s) and ability to anchor the items crucial.

The GRS units shall have the capability for expansion. Examples being; larger disks, more disks, more modules or expansion cards for more channels. The system should allow for more computational software demands without having to upgrade the GRS processor(s).

Users shall be configuring the units operational parameters to best capture acoustic data from the day’s flight operations. This shall require changing configuration files and manipulating settings, either at the unit itself or remotely by way of a Master Measurement List (MML) text file.

Configurations for the GRS units may initially be done on a local dedicated test unit. Once the configuration is confirmed and tested, the configuration file(s) shall be saved and distributed/uploaded to the operational field units.

Once configured and placed in operation the unit will be triggered via whatever method the user programmed into it and shall capture a buffered previously pre-determined duration of microphone input, continue recording through the boom and record a pre-determined duration of microphone input after being triggered to stop. In the end, a fully mature GRS unit shall be able to be commanded remotely to manipulate the recorded data, create output files, etc. and then send them to the MOF.

NASA intends to develop specialized software that will be installed on each analysis processor on each

GRS at a later date.

The analysis processor shall have "placeholder" software for each of the NASA-developed software modules/programs listed below. The “placeholder” software shall have the inputs/outputs necessary to allow verification of the GRS Version 2 requirements with a Host Station. The Host Station testing software shall be provided by the contractor. That software will in turn be provided to the CTPE contractor for additional development (Reference: B. Appendix).

NASA provided software will include:

1. Boom Finder - The software will search microphone measurement data to find a sonic boom time-pressure signature.

2. Metric calculation - This software will receive the results from the Boom Finder, window a sonic boom time-pressure signature and calculate various noise metrics (PLdB, ASEL, CSEL, etc.). It will also create an image of the sonic boom time-pressure signature. The outputs of this software will be sent to a remote Host Station.

3. End-to-end functional check analysis - Perform a spectral analysis of a pre-determined audio signal generated by the GRS. The outputs of this software will be sent to a remote Host Station.

4. ADS-B trigger - This software will read ADS-B messages to estimate sonic boom arrival times, then send a command to the GRS to trigger a recording.

Some software modules/programs will be executed by commands from a remote Host Station.

Table 4: GRS Contractor Responsibilities Matrix

6. Deliverables & Delivery Schedule

6.1 Hardware

Table 6: GRS Deliveries, below, shows the staged GRS unit delivery schedule. A description of the deliverables follows. Specifics for shipping will be detailed in the purchase order.

ITEM-001 through ITEM-003: GRS units Version 1’s

All units shall satisfy all requirements covered by Goals 1 through 4, Objectives 1.1 thru 4.3 listed in “GRS System Requirements Document” (AVTPE-GRSSRD-2020-001) Sections 7-Goals & 8-

Objectives, and all associated Requirements. No deviations from a stated Goal, Objective or

Requirement are authorized unless approved by NASA prior to implementation.

1. Documentation to be delivered with ITEM-001 shall be at least in draft form.

2. Documentation to be delivered with ITEM-002 shall be in final draft form.

3. Documentation to be delivered with ITEM-003 shall be updated documents based upon redlines provided by NASA.

2. For subsequent GRS deliveries; V&V testing will be done on 20% of the units, chosen at random by

NASA. Any discrepancies will be handled as stated above in section 7.1, a through e.

8. Security / Cybersecurity Requirements

NASA and its partners have a responsibility to protect the confidentiality, integrity and availability of IT related systems/products, its data and the integrity of computing assets belonging to or connecting to each organization's network, etc., as it is related to this SOW. Its purpose is to defend those assets against all threats throughout the system/product acquisition life-cycle.

1. The Contractor shall submit an organizational level IT Security Management Plan (ITSMP) –

This plan shall describe the processes and procedures the partner will follow to ensure appropriate security of IT resources that are developed, processed, or used under this contract.

Unlike the IT system security plan (SSP), which addresses the IT system or product, the ITSMP addresses how the contractor will manage personnel and processes associated with IT Security of the overall contract from an organizational perspective.

2. The Contractor shall provide an IT System Security Plan (SSP). This is a Federal Information

Security Management Act (FISMA) requirement and will meet the intent of NASA ITS-HBK-

2810.02-05A, Security Assessment and Authorization: External information Systems, available at: https://www.nasa.gov/content/security-requirements-policies. The SSP is specific to the IT system/product delivered under this SOW and not the company’s organizational SSP. Within 30 days after award, the contractor shall develop and deliver an IT Security Management Plan to the

Contracting Officer. All contractor personnel requiring physical or logical access to NASA IT resources shall complete NASA's annual IT Security Awareness training. Refer to the IT

Training policy located in the IT Security Web site at https://www.nasa.gov/content/security-requirements-policies.

3. The security categorization for the system/product delivered or supporting is considered

“Moderate” in accordance with National Institute of Standards and Technology, NIST 800-60, Guide for Mapping Types of Information and Information Systems to Security Categories and

FIPS Pub 199, Standards for Security Categorization of Federal Information and Information

Systems. The security categorization is used to determine the recommended security control baseline. This is based on the information types relevant to securing federal information and information systems for three objectives (i.e., loss of confidentiality, integrity, and availability).

4. The company/partnership will maintain ongoing communication with the Contracting Officer

(with guidance and assistance from the project’s Information System Owner (ISO) and

Information Security System Officer (ISSO)) ensuring special handling requirements involving

EAR, ITAR, Proprietary and/or Intellectual Property are considered.

The project’s ISO and ISSOs will review all deliverables and will work closely with the company/partnership representative throughout the Assessment and Authorization (A&A) phases and will seek the assistance of AFRC Code 640 (IT Security Team) for Authorization to Operate (ATO) governance.

A. Appendix – Design Review Requirements

Two Critical Design Reviews are required, one prior to the builds of GRS units Version 1 prototypes and GRS units Version 2 prototypes. The GRS Design Review Requirements are derived from the preliminary and critical design review entrance criteria in AFG-7120.5-001 and NPR7120.5 Table I-4.

(both publicly available on the WWW). The following items shall be presented during the GRS design reviews. The presentation materials outlined below shall be provided to NASA 5 days prior to the design review.

1. Detailed design documentation that can be shown to meet requirements and key technical performance measures with targets

a. Recording sample frequency

b. Recording dynamic range

c. Power lifespan

d. Weight

e. Size

2. Technical, cost, schedule, and safety risks with mitigation plans

3. Schedule

4. Cost estimate

5. Component test results

6. Fabrication, assembly, integration, and test plans

7. Technical data package with Interface Control Documents

8. Define operational limits and constraints

9. Environmental test plans

10. Master Measurement List

11. Requirements verification plan

12. GRS Concept of Operations and Timeline document validation plan

13. Operator interface description

14. Software development plan

B. Appendix – Associate Contractor Agreement

The contractor shall engage in a cooperative relationship with the ‘Community Test Planning and

Execution’ contractor (yet to be named) that will work with NASA to plan and execute the LBFD Phase

3 community tests; with the goal that facilitates effective remote operations of the GRS units through the

MOF. Accordingly,

1. The Contractor shall enter into Associate Contractor Agreements (ACA) for any portion of the contract requiring joint participation in the accomplishment of the Government’s requirements.

The contractor shall establish the means for coordination and exchange of information with the associate contractor (to be named later). The information to be exchanged shall be that required by the contractor and associate contractor in the execution of their respective contract requirements. The contractors shall pursue and foster cooperative efforts and goodwill in a manner that will benefit NASA with increased safety, efficiency, and productivity in the complete remote operations of the GRS units via the MOF. The agreements shall also include the basis for sharing information, data, technical knowledge, expertise, and/or resources essential to the integration of the GRS units with the MOF.

2. ACAs shall include the following general information:

a. Identify the associate contractors and their relationships.

b. Identify the program involved and the relevant Government contracts of the associate contractors.

c. Describe the associate contractor interfaces by general subject matter.

d. Specify the categories of information to be exchanged or support to be provided.

e. Include the expiration date (or event) of the ACA.

f. Identify potential conflicts between relevant Government contracts and the ACA; include agreements on protection of proprietary data and restrictions on employees.

3. A copy of such agreement shall be provided to the Contracting Officer for review before execution of the document by the cooperating contractors.

4. Nothing in the foregoing shall affect compliance with the requirements of the contract clause entitled, Organizational Conflict of Interest.

5. The Contractor is not relieved of any contract requirements or entitled to any adjustments to the contract terms because of a failure to resolve a disagreement with an associate contractor.

6. Liability for the improper disclosure of any proprietary data contained in or referenced by any agreement shall rest with the parties to the agreement, and not the Government.

7. All costs associated with the agreements are included in the negotiated cost of this contract.

Agreements may be amended as required by the Government during the performance of this contract.

8. The following contractors are:

CONTRACTOR ROLE DETAILS OF ACA

GRS > TBD Prime

CTPE > TBD Associate