Draft_ExhibitA_PWS_v11_.pdf

Version 11

EXHIBIT A

NASA Langley Research Center

PERFORMANCE WORK STATEMENT

(PWS)

RESEARCH, SCIENCE, AND ENGINEERING

SERVICES (RSES)

xx/xx/2021

DRAFT

Table of Contents

1.0 INTRODUCTION/BACKGROUND

2.0 SCOPE

2.1 NASA Engineering and Safety Center (NESC)

3.0 CONTRACT MANAGEMENT REQUIREMENTS

3.1 Strategic Management and Innovative Research Plan (SMIRP)

3.2 Langley Contract Management System (LCMS)

3.3 Management Meetings

3.4 Training

3.5 Software Management

4.0 TECHNICAL REQUIREMENTS

4.1 Autonomous Systems

4.1.1 Situation and Self Awareness

4.1.2 Reasoning and Acting

4.1.3 Collaboration and Interaction

4.1.4 System Engineering and Integrity

4.2 Acoustics

4.2.1 Psychoacoustic Testing Systems Support

4.2.2 Acoustics Software Support

4.2.3 Acoustics Research Support

4.3 Aerosciences

4.3.1 Aerothermodynamics

4.3.2 Aeroelasticity

4.3.3 Propulsion Flowpath and Interactions

4.3.4 Advanced Atmospheric Flight Vehicles

4.3.5 Computational Fluid Dynamics

4.3.6 Ground and Flight Experimental Testing

4.4 Avionics Systems

4.4.1 Avionics Systems and Subsystems

4.4.2 Avionics Tools, Models, and Analysis

4.5 Crew Systems & Aviation Operations

4.5.1 Modeling, Simulation and Experimental Support

4.5.2 Avionics Systems Analysis

4.5.3 Human Factors and Behavioral Performance

4.5.4 Flight Systems Guidance and Trajectory Management

4.5.5 Flight Tests and Flight Experiments

4.5.6 Air Traffic Management (ATM) and Range Tracking Systems Research and Support

4.5.7 UAS NAS Integration: Sense and Avoid (SAA) Interactions Support

4.5.8 Visualization of Advanced ATM Concepts of Operations

4.6 Systems Design, Engineering, Modeling, Integration and Flight Hardware Technology Development

4.6.1 Engineering and Development of Systems and Processes

4.6.2 Geometry and Grid Generation Services

4.7 Flight Dynamics and Controls

4.7.1 Modeling, High Fidelity Flight Simulation, and Control of Advanced Vehicle Concepts

4.7.2 Test Systems Support

4.8 Materials and Advanced Processing Technology Development

4.8.1 Advanced Processing Technology Development

4.8.2 Characterization of Advanced Materials

4.8.3 Device Applications

4.9 Structures

4.9.1 Structural Mechanics and Structural Dynamics

4.9.2 Durability, Damage Tolerance and Reliability

4.9.3 Computational Mechanics

4.10 Systems Analysis and Concepts Development

4.10.1 Advanced Mission, System, and Architecture Studies

4.10.2 Aerospace Vehicle and Systems Concept Development and Technology Assessment

4.10.3 Tools and Methods Development

4.11 Measurement Systems

4.11.1 Advanced Measurements for Ground Based/In-Flight Testing

4.11.2 Advanced Nondestructive Evaluation and Health Monitoring

4.11.3 Sensor/Electronic Systems

4.11.4 Electromagnetics and Sensors

4.11.5 Remote Atmospheric and Space-Based Sensing

4.11.6 Science Technology Development

4.11.6.1 Software, Algorithm, and Simulator Systems Development

4.11.6.2 Instrumentation Testbed Sensor Validation and Algorithm Development

4.11.6.3 Instrument Scientist Activities

4.11.6.4 Engineering Technical Management

4.11.6.5 Electronic Parts and Component Engineering

4.11.6.6 Engineering Training

4.11.6.7 Active Measurement Systems Development

4.11.6.8 Passive Measurement Systems Development

4.12 Applied Science

4.13 Science Research and Analysis

4.13.1 Lidar Science

4.13.2 Climate Science

4.13.2.1 Algorithm Development, Data Fusion, and Analysis

4.13.2.2 Cloud and Climate Modeling Analysis

4.13.3 Atmospheric Composition

4.13.3.1 Upper Atmosphere Composition, Cloud, and Aerosol Studies

4.13.3.2 Space Weather Influence on Planetary Atmospheres

4.14 Science Missions

4.14.1 Ongoing Space-Based Science Missions

4.14.1.1 Mission Technical Management

4.14.1.2 Mission Science

4.14.1.3 Mission Logistics

4.14.1.4 Mission Data Management

4.14.1.5 Mission Validation

4.14.2 Airborne and Ground-Based Measurement Systems and Field Campaigns

4.14.2.1 Lidar Field and Laboratory Research

4.14.2.2 Lidar Laser and Detector System Development, Airborne Integration, and Maintenance

4.14.2.3 Passive Remote Sensing Engineering and Science

4.14.2.4 Composition and Air Quality Research and Applications

4.14.2.5 Trace Gas Sensors for Airborne and Ground Measurements

4.14.2.6 In Situ Aerosol Measurements

4.14.2.7 Field Campaign Database Management

4.14.2.8 Field Campaign Support

4.14.3 Science Flight Project Development

4.14.3.1 Space System Development

4.14.3.2 Space System Requirements Development

4.14.3.3 Space System Documentation Development and Analysis

4.15 Atmospheric Science Data Center

4.15.1 Operations and User Services

4.15.2 Advanced Architectures and Engineering

4.15.3 System Engineering and Administration-Enterprise Systems

4.15.4 Software Engineering

4.15.5 System Engineering- ESDIS Core System (ECS)

4.15.6 IT Security

5.0 INDEFINITE DELIVERY/INDEFINITE QUANTITY (IDIQ)

6.0 ACRONYM LIST

1.0 Introduction/Background

This Performance Work Statement (PWS) defines the requirements to support research and technology development in order to meet evolving NASA Langley Research Center (LaRC) mission objectives, along with interrelated mission functions of the Agency and other NASA Centers. The Research, Science, and Engineering Services (RSES) requirements are identified in three sections:

Contract Management; Technical Requirements; and Indefinite Delivery/Indefinite Quantity (IDIQ) requirements. The Contract Management section addresses overall contract level requirements.

Technical requirements are organized into 15 technical service categories that define services to be provided under both the Core Mission Support (Core) and Indefinite Delivery/Indefinite Quantity (IDIQ) requirements. The Core provides discipline-oriented work that includes core technical services as determined by programs, projects, and implementing organizations. In addition, a number of requirements will be issued as IDIQ Task Orders (TOs) to accommodate programmatic uncertainty, and potential new work within the scope of this contract. The Contracting Officer will issue TOs in cases that include, but are not limited to, short term technical efforts and new work where the enduring nature is uncertain. IDIQ work which becomes enduring will be transitioned to Core. The requirements for Core and IDIQ work will be driven by NASA’s adaption of evolving technology development priorities, varying national, international, and ecological concerns.

Core requirements will utilize Technical Direction Notices (TDNs) as defined in the contract. Contract documentation and deliverables are identified in Exhibit B. In addition to Exhibit B, a number of the technical service categories and associated subsections also reference unique deliverables that further enhance the requirements in those areas. An Acronym List for the PWS is included section

6.0 of this document. Applicable Documents, including but not limited to policy, procedures, handbooks, and directives are listed in Attachment # to the PWS. Individual TDNs and TOs will reference other unique documents.

2.0 Scope

NASA's Langley Research Center is comprised of nearly 200 facilities on 764 acres in Hampton, Virginia, and employs about 3,400 civil servants and contractors. Langley works to make revolutionary improvements to aviation, expand understanding of Earth’s atmosphere, and develop technology for space exploration. NASA Langley Research Center develops, demonstrates, and delivers innovative concepts, solutions, and technologies to enable and inspire current and future missions while also addressing national priorities in aeronautics, space exploration and technology, and Earth science applications. In aeronautics, LaRC is enabling On-Demand Mobility through integration of certified vehicle and autonomous systems and improve airspace operations and safety. In space technology and exploration, LaRC plays a central role in the creation of technologies which allow us to travel further into space—from testing the Artemis Orion spacecraft and Space Launch System, assembling and manufacturing structures in space to developing Entry, Descent and Landing technologies for planetary missions. For our home planet, LaRC translates atmospheric investigation into important solutions to protect the Earth and its population. We monitor Earth’s vital signs from land, air, and space with a fleet of orbital satellites and ambitious airborne and ground-based observations. We develop new options to observe and study Earth’s complex interconnected natural systems with the continuous development of long-term climate and weather data records.

LaRC Website: https://www.nasa.gov/langley/overview

RSES will provide specialized research, science, and engineering services supporting these activities and NASA’s mission. Work will include cooperative activities with other contractors, NASA Centers, and Federal Agencies.

Within the scope of this PWS, the performance-based requirements typically address one or more facets of a complex system or assessment, supporting research and technology development programs, or a flight program. The work encompasses the full range of TRL from fundamental research through flight rated hardware design/development. The requirements may depend on specialized skills of a single individual or multi-disciplinary team of individuals; or close integration with tasks performed by NASA personnel, other contractor staff, and/or other Government agency personnel. As such, the contract requires an agile, diverse, integrated, and experienced Contractor and subcontractor workforce.

The contract will provide access to specialized subject matter experts and expertise in US industry and academia across all technical service categories within scope of RSES, including supporting short term NASA requirements, programs on leading edge research supporting NASA’s missions and objectives, as well as enabling the infusion of novel, fundamental methods, and concepts in research.

Due to the dynamic nature of research and development, the contract will experience variations in workload, and offeror shall be able to staff up and staff down quickly to adapt to changing missions, requirements, priorities, workload, attrition, and funding fluctuations to meet Government requirements without adversely affecting ongoing work. The Contractor shall have sufficient flexibility and depth to accommodate RSES requirements in a timely and efficient manner.

2.1 NASA Engineering and Safety Center (NESC)

Included in the scope of this effort is to also provide technical expertise to the NESC to support its mission to provide robust technical solutions to the Agency’s highest-risk and most complex issues.

The NESC activities range from supporting reviews, augmenting project teams, solving problems through independent test and analysis, and exploring alternate design concepts.

The Contractor shall perform the following work in support of the NESC including, but not limited to:

• Provide subject matter experts (SMEs) and technical experts to:

o Perform independent reviews of program technical content o Assist in reviewing, evaluating, and validating project/proposal requirements o Participate in Peer Review Boards and technical discipline teams o Perform scientific investigations, analyses, assessments, studies, reviews, and technology demonstrations.

The NESC’s goal is to perform value-added independent testing, analysis, and assessments of NASA’s high-risk projects to ensure safety and mission success. In support of the NESC’s mission, the Contractor shall also support critical, high risk projects which may be urgent and of a short duration (SME availability within 24 hours of official notification from the CO or COR). High risk projects to be supported by the Contractor include, but not limited to, International Space Station, Soyuz, crew vehicles, launch vehicles, and human exploration.

SMEs and technical experts shall support areas including, but not limited to:

• Guidance, Navigation, and Control (GN&C), Non-Destructive Evaluation (NDE), Propulsion;

Electrical Power; Avionics; Flight Mechanics; Mechanical Systems; Human Factors; Materials;

Structures; Passive Thermal; Environmental Control/Life Support; Software; Loads and Dynamics; Aerosciences; Sensors and Instrumentation; Space Environments; Nuclear Power and Propulsion; Systems Engineering; and Cryogenics.

The Contractor, SMEs, and consultants shall comply with NPR 7120.7.

3.0 Contract Management Requirements

The Contractor shall provide an overall effective, efficient, and responsive management and administrative function to ensure the proper resources are available and allocated, adequate reports and documentation are prepared, and the overall work environment supports the PWS requirements.

The Contractor shall provide an organizational structure with clear lines of authority and clearly identified Government interfaces. The Contractor shall be responsible for ensuring that all contractor and subcontractor personnel engaged in performance of this PWS have appropriate qualifications, knowledge, clearances, certifications, and are free from conflicts of interest, to perform work in accordance with the PWS requirements.

The Contractor shall maintain a Facility Clearance at the Top-Secret level with no safeguarding required in accordance with Exhibit F – Contract Security Classification Specification (DD254). The Contractor will access classified information at a Government facility to be identified on the Department of Defense Contract Security Classification Specification, DD Form 254.

The Contractor shall comply with all U.S. export control laws and regulations including, but not limited to, the International Traffic in Arms Regulations (ITAR), 22 CFR Parts 120 through 130, and the Export Administration Regulations (EAR), 15 CFR Parts 730 through 799, in performance of this contract. In the absence of available license exemptions/exceptions, the Contractor shall be responsible for obtaining the appropriate license or other approvals, if required, for exports of hardware, technical data, and software, or for the provisions of technical assistance. The Contractor shall screen individuals at appropriate times to ensure ITAR compliance and shall insert this requirement in all subcontracts that may involve ITAR or EAR controlled information.

3.1 Strategic Management and Innovative Research Plan (SMIRP)

The Contractor shall provide a Strategic Management and Innovative Research Plan (SMIRP) which demonstrates the continuous strategic management and innovation throughout the life of the contract and defines and integrates contract work activities and requirements across the contract, including subcontractor efforts. The Contractor shall develop the SMIRP and changes thereto in coordination and collaboration with appropriate NASA personnel associated with the contract including, but not limited to, the Contracting Officer (CO), Contracting Officer’s Representative (COR), discipline representatives, Technical Monitors (TMs), and Points of Contact (POCs) referenced in TDNs to ensure focus is placed on defining the requirements and matching those requirements to projected funding levels.

The SMIRP is intended to be a flexible working document, incorporating changes throughout the year (with COR concurrence, and CO approval) to accommodate emerging mission and customer requirements in addition to existing requirements. Government personnel and Contractor will continuously collaborate and coordinate on changes to the SMIRP to ensure a clear understanding of the requirements, the division of roles and responsibilities, and the content that will be included in the SMIRP.

3.1.1 Objectives and Content of the SMIRP

The details and content of the SMIRP are identified DRD #. The SMIRP shall reflect the most efficient operational approach within and across the technical disciplines, given a workforce of civil servants and Contractors. The SMIRP shall detail the Contractor’s overall approach to meet the PWS requirements associated with the successful accomplishment of program/project goals, objectives, and milestones, in accordance with Government provided information as described in Paragraph 3.1.2.

3.1.2 Government Provided Information

The Government will define a current vision and strategic goals with active and continuous participation and communication with the Contractor. At a top level, LaRC will provide technical service focus areas along with required emerging skills/capabilities. The Government will provide the operational and budgetary parameters for inclusion and consideration in development of the SMIRP for the upcoming Government fiscal year. The Government may also include parameters for multiple years. The parameters may fluctuate and will include, but are not limited to:

• Annual projections of requirements by discipline (programs/projects to be supported, mission objectives, major deliverables, and milestones, sustained technical support requirements)

• Performance criteria for functions to be performed by the Contractor

NOTE: The work that the Contractor shall perform is subject to change based on the Government’s workforce strategies.

3.2 Langley Contract Management System (LCMS)

The iSite Contract Management Portal (iSite) will be provided by NASA to facilitate contract administration and oversight for the RSES Contract. iSite is a suite of tools which includes configurable workflows, financial reporting, configurable estimates, document repository, and automated email notifications among other functions based on NASA managed security controls.

More information may be found at the vendor' s website https://www.isitellc.com/icmp/ .

The Contractor shall use the Government provided LCMS to facilitate the contract management process, for both Core and IDIQ work that will: (1) create, schedule, approve, document, track and monitor contract activities; and (2) plan and manage resources. For all PWS areas, TDNs and TOs, the Contractor shall input all applicable fields in LCMS (e.g., period of performance, WYEs, labor categories, total cost, total fee (if applicable), subcontractor data (e.g., labor categories, hours, and costs), government furnished equipment and/or information, customer contact information, travel, and a completed task quality standard metric (if applicable) with customer-feedback and comment input field).

Financial data shall be maintained in LCMS. The Contractor shall notify the CO immediately upon detection of significant errors in its financial data that impact work and/or costs reported. Financial reports shall be generated at multiple levels of detail that include, but are not limited to PWS area, TDNs, and TOs. The Contractor shall provide monthly accumulated expenditures and projections of costs and workforce utilization in accordance with Contractor Financial Management Report, NASA Form 533M. All NF 533 data shall be available in the LCMS database. End of month TDN data must reconcile with the NF 533M.

The LCMS shall capture financial data for tracking work, funding, and costs on the Contract by each TDN and TO. The data include, but are not limited to, funding levels, actual incurred costs, funded through date, and estimated cost to complete.

3.3 Management Meetings

The Contractor shall participate in periodic meetings with the CO to discuss contract performance issues, process improvements, risks and related issues, corrective actions, recovery plans, and other details of contract operations. These informal meetings will be attended by the CO, COR, and TPOCs.

The Contractor shall participate in reviews with the CO to discuss cost planning, phasing, and performance of the overall progress of the Contractor, subcontractors and vendors as required by the CO. These reviews may include both formal and informal discussions with multiple customers requiring multiple products/reports, sometimes due concurrently.

Contractor personnel shall participate in semi-annual meetings with CO, COR, and discipline representatives to discuss SMIRP requirements.

Contractor personnel shall maintain frequent communications with the Government regarding technical challenges, accomplishments, findings, problems, risks, corrective actions, progress, and other details of contract operations. The Contractor shall participate in meetings including, but not limited to, program/project status meetings and teleconferences, team planning meetings, technical interchange meetings, and conferences.

3.4 Training

The Contractor shall provide specialized training to Government personnel regarding products including, but not limited to, tools, methods, procedures, and techniques developed or implemented by the Contractor.

3.5 Software Management

The Contractor shall develop and maintain a Software Management Plan (SMP), including supporting documents, in accordance with NPR 7150.2, NASA Software Engineering Requirements depending on the software class, identified as follows:

Class A: Human-rated Space Software Systems Class B: Non-Human Space Rated Software Systems or Large-Scale Aeronautics Vehicles Class C: Mission Support Software or Aeronautics Vehicles, or Major Engineering / Research Facility Software

Class D: Basic Science/Engineering Design and Research and Technology Software Class E: Small Light Weight Design Concept and Research Technology Software

Based on software class (identified in NPR 7150.2) additional requirements, software products, and documentation contents will be specified by NASA in TDNs or TOs.

3.5.1 Use of Off-the-shelf, Reused, or Open-source Software

The Contractor shall notify the COR whether off-the-shelf, reused, or open-source software will be included in code developed for the project and to obtain all necessary licenses to permit use of such software. The Contractor shall satisfy the following conditions when a Commercial, Government, Modified Off-the-Shelf (COTS, GOTS, MOTS), open source, or reused software component is acquired or used:

• The requirements to be met by the software component are identified

• The software component includes documentation to fulfill its intended purpose (e.g. usage instructions)

• Proprietary rights, usage rights, ownership, warranty, licensing rights, and transfer rights have been addressed to permit use of the software

• Future support for the software product is planned and adequate for project needs

• The software component is verified and validated to the same level required to accept a similar developed software component for its intended use

• The contractor has a plan to perform periodic assessments of vendor reported defects to ensure the defects do not impact the selected software components

For any new off-the-shelf or open source software to be installed on NASA systems, the contractor shall submit an authorization request to IT Acquisition Management (ITAM); only software with approved authorization can be installed on NASA systems.

3.5.2 Automatic Generation of Software Source Code

The Contractor shall define the approach to the automatic generation of software source code including but not limited to:

• Validation and verification of auto-generation tools

• Configuration management of the auto-generation tools and associated data

• Identification of the allowable scope for the use of auto-generated software

• Verification and validation of auto-generated source code

• Monitoring the actual use of auto-generated source code compared to the planned use

• Policies and procedures for making manual changes to auto-generated source code

• Configuration management of the input to the auto-generation tool, the output of the auto-generation tool, and modifications made to the output of the auto-generation tools

3.5.3 Software Cybersecurity

The contractor shall consult with a designated NASA Computer Security Official (CSO) to perform a software cybersecurity assessment on the software components per the Agency security policies and the project requirements, including risks posed by the use of COTS, GOTS, MOTS, OSS, or reused software components.

4.0 Technical Requirements

The Contractor shall provide technical services to accomplish work in the following technical service categories:

4.1 Autonomous Systems

Autonomous systems (including robotic application) are a critical capability for all NASA's mission areas, including Aeronautics, Earth and Planetary Sciences, and Agency/Commercial Spaceflight operations that will be more pervasive in the future. Current systems are traditionally automated to the extent that they can respond with scripted behaviors to a predicted set of conditions, and often still require some level of human interaction and control. This discipline includes the development of technologies and capabilities that will lead to a range of systems, from cooperative to fully autonomous systems that can learn and adapt to changes in their environment that were not predicted, in order to accomplish the mission goals with minimal or no human involvement. Elements referenced below may be technological agents, either proximal or distal; or humans in the operational context, either proximal or distal.

The discipline of autonomous software systems demands a unique set of tools and development environments. While some systems are windows-based, most are linux-based, require real-time or near real-time operating systems and capabilities, and employ multiple programming languages including but not limited to C/C++, Python, CUDA, Matlab, and Simulink as well as software libraries such as TensorFlow, OMPL, etc. in addition to internally-developed frameworks and tools. Modeling and simulation environments are critical to R&D as well as test and evaluation (T&E) and can range in complexity from Excel files to Matlab to fully instantiated physics-based game engines such as Unity or Unreal. Interoperability and expandability across systems and applications are required capabilities so middleware software such as ROS and DDS are a critical component(s) of any autonomous system.

The Contractor shall perform the following work in support of Autonomous Systems including, but not limited to:

• Situation and Self Awareness - (Section 4.1.1)

• Reasoning and Acting - (Section 4.1.2)

• Collaboration and Interaction - (Section 4.1.3)

• System Engineering and Integrity - (Section 4.1.4)

4.1.1 Situation and Self Awareness

Situation and Self Awareness is defined as the interrogation, identification, and evaluation of both the state of the environment and the state of the system. The Contractor shall perform the following work in support of Situation and Self Awareness including, but not limited to:

4.1.1.1 Sensing and Perception

4.1.1.1.1 Define sensors and sensor architectures to acquire (actively and passively), process and analyze information internal and external to the system.

4.1.1.1.2 Define sensors and sensor architectures to acquire (actively and passively), process and analyze inputs from the devices’ sensors, other system elements, and human behaviors (commanded/communicated or observed/inferred).

4.1.1.1.3 Develop algorithms to intelligently coordinate data threads from varied sources, tempos, and with varied provenance.

4.1.1.1.4 Develop algorithms to monitor data health, maintain data provenance, and carrying attendant uncertainty of data sources and fused data products.

4.1.1.2 State Estimation and Monitoring

4.1.1.2.1 Identify requisite sensors, communication interfaces and algorithms to estimate internal and external states from sensed or designated raw or processed inputs generated by multiple sensors/instruments, acquisition, verification, and continual comparison to expected states.

4.1.1.3 Knowledge and Model Building

4.1.1.3.1 Create information resources characterizing system elements, the environment, predicted mission goals and constraints and the dynamics and interactive effects of these.

4.1.1.4 Hazard Assessment

4.1.1.4.1 Provide algorithms that can evaluate the state of the environment, own state, and the state of other system elements with respect to potential threat to the safety of contemplated actions or inactions.

4.1.1.4.2 Develop systems that can learn from declarative inputs, observations of other systems, and experiential data.

4.1.1.5 Event and Trend Identification

4.1.1.5.1 Identify sensors and develop algorithms and interfaces to provide analyses of environmental or system data to identify events and trends for use in tactical decision-making, as well as strategic and reactive planning.

4.1.1.5.2 Identify patterns and relationships in data, including imagery for the purpose of diagnosticity, forensics, and predictive capabilities

4.1.1.6 Anomaly Detection

4.1.1.6.1 Identify sensors and develop algorithms interfaces to provide analyses of environmental or system data to identify outliers that may be advantageous (e.g., unusual scientific data point) or disadvantageous (anomalous performance data).

4.1.1.7 Object Detection and Characterization

4.1.1.7.1 Identify sensors, interfaces, in situ agent protocols and analyses to support timely object detection and characterization, in consideration of ambient conditions and signal noise environments - for example, to support unanticipated see-and-avoid constraints and weather conditions.

4.1.1.8 Supportive Communications

4.1.1.8.1 Support development of adaptive software/hardware communication protocols and networks to support timely, effective, and secure system interfaces and data/information requirements as necessary for situation awareness, multi-element coordination, and systems-of-systems operability.

4.1.1.9 Deliverables include, but are not limited to, Exhibit B

4.1.2 Reasoning and Acting

Reasoning and Acting is defined as the analysis and evaluation of situations present, future, or past for decision making and for directing actions to achieve a goal or a mission. The Contractor shall perform the following work in support of Reasoning and Acting including, but not limited to:

4.1.2.1 Mission Planning and Scheduling

4.1.2.1.1 Define goals, communicate, and manage goals, objectives, and activities necessary for systems to achieve their missions, with consideration for in situ reconsideration of these, reactive and strategic replanning with varying levels of system autonomy.

4.1.2.2 Activity and Resource Planning and Scheduling

4.1.2.2.1 Select and order activities to be performed while managing system resources to achieve mission goals, with the capability to be reactive to new data received during plan and execution.

4.1.2.2.2 Develop multi-threaded, coordinated reactive plans in response to off-nominal conditions and failures.

4.1.2.3 Motion and Manipulation Planning and Execution

4.1.2.3.1 Generate or modify action plans for elements to achieve the desired target physical location configuration or activity subject to self, system, environment and mission constraints and prioritized objectives.

4.1.2.4 Execution and Control

4.1.2.4.1 Change system state or execute a command to a coordinating element to meet mission goals and objectives, according to a plan or schedule, subject to control authority and permission, and based on mission phase, environment, or system state

4.1.2.5 Fault Diagnosis and Prognosis

4.1.2.5.1 Identify and characterize system faults, develop fault prediction capabilities, develop models of and methods for conveying system capability and limitations given failed (or prognosticated to fail) components.

4.1.2.6 System Resilience

4.1.2.6.1 Determine best possible system configuration and operations after a fault given situational constraints and task requirements, and capabilities to reconfigure responsively when necessary to achieve this with regard to ownship and mission level objectives (i.e., system resilience may result in self-safing, but could also result in sacrifice of some elements to benefit the mission as performed by remaining).

4.1.2.6.2 Develop strategies for graceful degradation of system performance when necessary and function reallocation to other system elements or other systems/humans.

4.1.2.7 Learning and Adapting

4.1.2.7.1 Enable adaptation to changing environments and conditions without necessitating externally provided interventional reprogramming, using experiential knowledge collected, or knowledge provided from other system elements. Conduct hypothesis testing and experimentation.

4.1.2.8 Deliverables include, but are not limited to, Exhibit B

4.1.3 Collaboration and Interaction

Collaboration and Interaction is defined as two or more elements or systems working together to achieve a defined outcome. The Contractor shall perform the following work in support of Collaboration and Interaction including, but not limited to:

4.1.3.1 Joint Knowledge and Understanding

4.1.3.1.1 Collect, assemble, share, and interpret information and intent among elements to solve problems, plan actions/responses; and develop improved models of own and other system elements and the operating environment.

4.1.3.2 Behavior and Intent Prediction

4.1.3.2.1 Forecast actions of other elements or systems to support collaboration and coordinated behavior.

4.1.3.3 Goal and Task Negotiation

4.1.3.3.1 Articulate, share and negotiate elements’ goals, tasking, resources, status, and constraints for coordinated behavior among a collection of elements, especially where these must dynamically respond to changing mission objectives, threats and/or health status.

4.1.3.4 Trustworthy Performance

4.1.3.4.1 Provide relevant data, metrics, processes, training and interfaces to permit sponsors/certifiers (during validation and verification) and in situ interfacing agents (human or technological) to accurately assess and predict the trustworthiness of element operations, and operational boundary conditions for trusted performance.

4.1.3.5 Human/Autonomous System Teaming

4.1.3.5.1 Provide human interface concepts (storyboard through executable hardware) to support effective human teaming that ensures effective situation awareness and commanding of integrated multi-agent systems, including Autonomous Systems;

and interface features to support appropriate trust calibration (e.g., transparency, explainability, and inspectability).

4.1.3.6 Deliverables include, but are not limited to, Exhibit B

4.1.4 System Engineering and Integrity

Engineering and Integrity is defined as design considerations, processes, and properties necessary to implement autonomy. The Contractor shall perform the following work in support of System Engineering and Integrity including, but not limited to:

4.1.4.1 Verification and Validation

4.1.4.1.1 Provide data, metrics, methods, and assessment methodologies to support assessment of the degree to which systems meet the requirements (verification) and fulfill intended purposes (validation in the anticipated operational interfacing humans and other technology) and environmental contexts.

4.1.4.2 Test and Evaluation

4.1.4.2.1 Provide data, metrics, methods, and assessment methodologies to support assessment of the degree to which systems meet performance and usability requirements in anticipated representative operational and environmental dynamic contexts, and in nominal and off-nominal conditions.

4.1.4.3 Operational Assurance

4.1.4.3.1 Provide data, data provisioning architectures, and interfaces for stakeholders to confidently place system in operation; providing assurance that it will operate safely, effectively and in a manner that does not adversely affect other systems as defined in the actual operational and environmental contexts.

4.1.4.4 Modeling and Simulation

4.1.4.4.1 Develop architectural, mathematical, and executable representations of complex systems including autonomous system modules, and executable models of autonomous system modules – including interfaces to other elements for use in system design, evaluation, operator training, and operational assessment/assurance.

4.1.4.5 Architecture and Design

4.1.4.5.1 Develop methods and tools describing system architecture and interfaces to the environment and other systems, the interconnectivity of system components, and the derived functionality of components and systems of systems. Such methods and tools shall further support characterization of emergent system properties (e.g., resilience, robustness, scalability, safety, reliability) and propagation of failures based on all forms of connectivity among components (e.g., proximity, data connectivity)

4.1.4.6 Certification and Adoption

4.1.4.6.1 Provide data, data provisioning architectures, models/simulations, and interfaces for regulatory entities to confidently certify systems for operation.

4.1.4.6.2 Define and construct training facilities and platforms, curricula, operational experiences, and testing to foster in situ accurate trust calibration and, therefore, appropriate adoption and use by any interfacing humans during mission planning and operations.

4.1.4.7 Deliverables include, but are not limited to, Exhibit B

4.2 Acoustics

This technical service category includes, but is not limited to, research to understand and control noise generated from flight vehicles (crewed and uncrewed) as well as its effects on aircraft, rotorcraft, and spacecraft structures, on passengers and crew, and on airport communities. The work involves theoretical, analytical, computational, and experimental acoustics research, including both fundamental as well as applied research that includes, but is not limited to, validation of analytical models of sound generation and transmission/propagation as well as active and passive noise control concepts, along with research aimed at understanding, predicting, and controlling/reducing the noise of fixed-wing and rotary-wing aircraft.

The Contractor shall perform the following work in support of Acoustics including, but not limited to:

• Psychoacoustic Testing Systems Support - (Section 4.2.1)

• Acoustics Software Support - (Section 4.2.2)

• Acoustics Research Support - (Section 4.2.3)

4.2.1 Psychoacoustic Testing Systems Support

LaRC is involved in research to assess noise impact due to air vehicle noise, including interior noise, flyover noise, and sonic boom. The work is supported by projects within the Aeronautics Research Mission Directorate. One aspect of this research is to assess community noise impact and understand human response to aviation noise through subjective testing. As field tests with air vehicles are expensive and make it difficult to provide certain test controls, psychoacoustic testing in a laboratory environment or controlled home or office environment through remote means is required. NASA uses a variety of software tools and hardware to provide an immersive acoustic-visual environment for presenting synthesized and recorded air vehicle sounds to a listener for use in subjective testing. The software tools include the Community Noise Test Environment (CNoTE), Aircraft Source Noise Generator (ASoNG) and NASA Auralization Framework (NAF). NASA uses additional software to calculate metrics on sound stimuli presented to listeners, including specialized sonic boom and sound quality metrics.

The Contractor shall perform the following work in support of Psychoacoustic Testing Systems Support including, but not limited to:

4.2.1.1 Provide support for testing, maintenance of existing psychoacoustic testing capabilities, and develop additional sound generation, human response measurement, and other subjective test functionality as needed for future program requirements.

4.2.1.2 Maintain operability of the existing code base as needed for updates to operating systems, device drivers, third-party software development tools, libraries, and applications software.

4.2.1.3 Modify the existing code base to provide improvements to source noise synthesis and propagation routines, including interface(s) to noise prediction programs such as Aircraft Noise Prediction Program 2 (ANOPP2). Improvements also include new subjective response input formats, upgrades to metrics computation codes, and maintenance of testing functionality needed to support different subjective testing facilities.

4.2.1.4 Develop and configure psychoacoustic testing systems for human response studies in onsite facilities such as the Exterior Effects Room, Interior Effects Room, small anechoic chamber, and Sonic Boom Simulator, as well as offsite tests using a remote testing platform.

4.2.1.5 Ensure all developed code is compatible with current NASA software tools used for psychoacoustic testing such as CNoTE, ASoNG, NAF and metrics calculation codes.

4.2.1.6 Ensure all code development is performed in accordance with established software development plans that include bug tracking, configuration management, documentation of code changes, and documentation for users.

4.2.1.7 Ensure all code changes are archived in a repository on a government-furnished computer.

4.2.2 Acoustics Software Support

LaRC specializes in aircraft vehicle noise research and assessment. To perform studies of noise generation and propagation, acoustic tools in the form of software are often employed. These tools are continuously developed and improved as the understanding of noise generation and propagation improves. The tools used to predict aircraft noise often need to be updated, verified, validation, and distributed across many different software and hardware configurations and include various programming languages such as modern Fortran, C++, shell scripting, and legacy Fortran 77 code.

The Contractor shall perform the following work in support of Acoustics Software Support including, but not limited to:

4.2.2.1 Provide software, platform, distribution, and verification support for the suite of acoustic tools employed by the vehicle assessment team of the aeroacoustics branch that will include Aircraft Noise Prediction Program (ANOPP and ANOPP2), Automated testing of ANOPP2 via Cruise Control, and Automated documentation and distribution for ANOPP2 via Cruise Control.

4.2.2.2 Analyze and resolve any software failure or performance degradation.

4.2.2.3 Obtain and install software updates and upgrades from the vendor or public domain sources as required to ensure that systems are operating at the current IT Security posture and verify that systems are operational following software upgrades.

4.2.2.4 Perform full system, file, and data backup prior to software upgrades.

4.2.2.5 Preserve and restore all files and data during software upgrades.

4.2.3 Acoustics Research Support

This technical service category includes, but is not limited to, research to understand and control noise generated from air vehicles including individual noise sources on a vehicle, interactions between noise sources, and interactions between noise sources and the airframe. Research also includes the effect of noise of air and launch vehicles on structures, on passengers and crew, and on communities. The work involves theoretical, analytical, computational, and experimental acoustics research, including both fundamental as well as applied research. This research includes, but is not limited to, development and validation of analytical and numerical models of sound generation, sound transmission, scattering of sound, propagation through the atmosphere, active and passive noise control concepts, and research to understand, predict, and mitigate the noise of fixed-wing and rotary-wing aircraft and its impact on communities. The Acoustics Research Laboratory of Building 1208 provides one focus area for acoustics research at NASA Langley Research Center (LaRC), containing a suite of experimental laboratories including the Quiet Flow Facility, Structural Acoustics Loads and Transmission Facility, Exterior Effects Room, Interior Effects Room, and the Sonic Boom Simulator.

Additional dedicated acoustic facilities include the Liner Technology Facility, Jet Noise Laboratory (e.g., Low Speed Aeroacoustic Wind Tunnel and Small Anechoic Jet Facility/Small Hover Anechoic Chamber), and Thermal Acoustic Fatigue Apparatus. Acoustic tests may be conducted in the LaRC 14- by 22-Foot Subsonic Tunnel or other large local wind tunnels, as well as at remote facilities and field test locations across the country, often utilizing the Mobile Acoustics Facility, and overseas.

Performance of acoustics research requires proficiency in aeroacoustics and structural acoustics, including expertise in disciplines including, but not limited to, materials development and characterization; advanced manufacturing techniques; dynamic data acquisition, reduction, and analysis; use of software tools (e.g., NASTRAN, Abaqus, COMSOL, LabVIEW, Python, SOLIDWORKS, computational fluid dynamics (CFD) codes, and MATLAB®); experimental process control; and analytical and computational modeling of both individual noise sources and complete vehicle systems, including an understanding of the underlying fluid dynamics contributing to the sound generation.

The Contractor shall perform the following work in support of Acoustics Research Support including, but not limited to:

4.2.3.1 Develop integrated noise prediction capabilities based on models including, but not limited to, computational fluid dynamics (CFD), vibro-acoustics, flow interaction and propulsion, at both the component and system level.

4.2.3.2 Develop noise control methodologies for reducing noise sources and the analytical framework for their evaluation.

4.2.3.3 Develop, validate, and compare structural acoustic models (e.g., finite element analysis and statistical energy analysis) of vibro-acoustic behavior for aerospace structures. The composition of the structure(s) may be of metallic, non-metallic materials or a combination of both.

4.2.3.4 Develop methodologies using validated models via parametric or optimization studies to minimize noise transmission without sacrificing strength, durability or adding weight.

4.2.3.5 Support human response studies of aircraft interior and community noise including response to sonic booms and advanced air mobility vehicles, which includes urban air mobility vehicles.

4.2.3.6 Support human response studies by providing test subjects from the community in accordance with NASA criteria which may include audiograms, audiometric records, and classification of human test subjects.

4.2.3.7 Design test articles and associated support equipment and instrumentation for acoustic testing.

4.2.3.8 Provide technician support for test article and support equipment fabrication and/or modification, equipment maintenance and repair, and operational support specific to unique acoustical ground and field testing.

4.2.3.9 Develop, integrate, and operate data acquisition, control systems, ground-based systems for flight test measurements, and analysis software to acquire, process, and analyze acoustic data obtained in experimental facilities and field tests. State and measurement data shall be obtained in ground and field testing from systems and methods including, but not limited to, acoustic arrays, static and dynamic pressure transducers, particle image velocimetry (PIV), and optical and discrete vibration sensors.

Data acquisition systems are typically programmed in LabVIEW and/or MATLAB®. Data processing and analysis may include real-time, near-real-time, and post-test activities.

4.2.3.10 Ensure new and existing data acquired are properly archived on the appropriate archival backup systems.

4.2.3.11 Develop, implement, and validate computational prediction capabilities into software tools for system noise prediction (e.g., ANOPP and ANOPP2), nonlinear sound propagation through the atmosphere (e.g., PCBoom), scattering from surfaces (e.g., TD- FAST), auralization of noise source (e.g., NAF), and other specialized software tools for acoustical analysis developed for NASA.

4.3 Aerosciences

Aerosciences is the prediction of vehicle and component atmospheric flight performance and flow qualities to enable robust and efficient flight vehicle development, achieving performance requirements while minimizing environmental impacts. The technologies involved in Aerosciences require development of analytical and empirical systems; computational and uncertainty analyses;

ground testing technologies in wind tunnels, arc jets, ballistic ranges, water channels; and flight technologies in specific technical areas. Example technologies include flow characterization through analysis and testing, with prediction and characterization of unsteady separated flow being a primary technology challenge; target vehicles include aircraft, launch vehicles, Entry, Descent, and Landing (EDL) systems, abort systems, parachutes, and inflatable decelerators across all speed regimes from subsonic to hypersonic; characterization of subsonic, transonic, supersonic, and hypersonic flows, junction flows, aero surface designs (wings, nacelles, etc.), inlets, nozzles, propulsion system installations, propulsion airframe integration, landing gear, high lift systems, and innovative control effectors; new technologies to predict and analyze the underlying unsteady flow characteristics driving buffet for aircraft, launch vehicles and spacecraft; advanced aerodynamic predictive capability required to enable efficient atmospheric flight vehicle designs.

The Contractor shall perform the following work in support of Aerodynamics including, but not limited to:

• Aerothermodynamics - (Section 4.3.1)

• Aeroelasticity - (Section 4.3.2)

• Propulsion Flowpath and Interactions - (Section 4.3.3)

• Advanced Atmospheric Flight Vehicles – (Section 4.3.4)

• Computational Fluid Dynamics – (Section 4.3.5)

• Ground and Flight Experimental Testing – (Section 4.3.6)

4.3.1 Aerothermodynamics

Aerothermodynamics utilizes computational analysis, ground test, and flight to predict vehicle and component aeroheating environments and flow qualities (e.g. chemically reacting, convective and radiative heating, surface temperature, heat flux, interactions with vehicle components like thermal protection systems). Example technologies include Surface heating and chemical flow composition predictions for high speed atmospheric entry vehicles in laminar, turbulent, and separated flows;

Shock layer radiation prediction and characterization; Advanced predictive computational technologies in hypersonic flow environments.

The Contractor…