Follow-On Statement of Work SOW.pdf

RFP Section C Advanced Guidance, Navigation and Control (GN&C) and Avionics Technology Development and Analysis

C-1

SECTION C - DESCRIPTION/SPECIFICATION/WORK STATEMENT

C-2

TABLE OF CONTENTS

1.0 INTRODUCTION

2.0 MANAGEMENT, INTEGRATION, AND CONTROL

2.1 PROGRAM MANAGEMENT

2.1.1 Program Management and Administration

2.1.2 Planning and Reviews

2.2 BUSINESS MANAGEMENT

2.2.1 Financial and Resources Management

2.2.2 Organizational Conflict of Interest and Non-Disclosure Agreements

2.2.3 New Technology

2.3 INFORMATION TECHNOLOGY

2.3.1 Information Technology Security

2.3.2 Export Control

3.0 GN&C AND AVIONICS TECHNOLOGY DEVELOPMENT AND ANALYSIS

3.1 INTERNATIONAL SPACE STATION (ISS)

3.1.1 ISS Command and Data Handling and Automation

3.2 MULTI-PURPOSE CREW VEHICLE (MPCV) GN&C

3.2.1 GN&C Flight Software (FSW) Production

3.2.2 Integration, Test & Verification

3.3 ADVANCED GN&C AND AVIONICS

3.4 TECHNICAL REPORTING

4.0 SAFETY AND MISSION ASSURANCE

4.1 QUALITY ASSURANCE

4.2 SAFETY AND HEALTH

C-3

1.0 INTRODUCTION

This statement of work (SOW) identifies the effort to be provided by the contractor for the Aeroscience and Flight Mechanics Division (AFMD) of the National Aeronautics and Space Administration (NASA) Lyndon B. Johnson Space Center (JSC). The scope of the contract consists of engineering design, development, integration, test, analysis, verification and validation, certification, and spaceflight support activities within the areas of Guidance Navigation & Control (GN&C) systems, integrated avionics systems, and autonomous flight operations.

The SOW requirements are Indefinite Quantity/Indefinite Delivery (IDIQ) and the Contracting Officer will direct contractor IDIQ activities through the issuance and modification of task orders. Each IDIQ task order will include a description of the work content as well as the associated milestones and deliverables. Each IDIQ task order will also identify any unique applicable documents in addition to the applicable documents listed in Attachment J-4.

2.0 MANAGEMENT, INTEGRATION, AND CONTROL

The scope outlined in this section should be covered by each individual IDIQ task order that is issued as part of the contract

2.1 Program Management

The contractor shall provide overall management of the contract requirements and tasks necessary for the administration of the contract. The contractor shall perform all business and administrative functions and integrate these functions across all areas of performance.

2.1.1 Program Management and Administration

The contractor shall meet all schedules and provide all deliverables in accordance with the SOW, IDIQ Task Orders, and Data Requirements Descriptions (DRDs).

In support of the scope of work under this contract, the contractor shall ensure all tasks have been completed to meet all flight manifest schedules. The order of precedence for contract requirements is set forth in Section I, Clause 52.215-8.

2.1.2 Planning and Reviews

The contractor shall provide and maintain a Program Management Plan (PMP) per DRD 1 and a Government Property Management Plan (GPMP) per DRD 6. The PMP and GPMP must be reviewed and approved by NASA. The PMP and GPMP shall be updated by the contractor and approved by NASA as required throughout the performance of the contract.

The PMP shall detail the anticipated expenditures and staffing levels for the contract and shall coincide with Government fiscal years. The staffing profile shall include the contractor's proposed staffing per month for each of the major sections of this SOW with authorized IDIQ Task Orders. Any deviations to the approved PMP shall be proposed to the Contracting Officer’s Representative (COR) for review and concurrence prior to

C-4 implementation.

2.2 Business Management

The contractor shall perform all business and administrative functions and services and integrate these functions across all areas of performance. The contractor shall deliver the products described in this Statement of Work (SOW), contract terms and conditions, applicable documents, Data Requirements Descriptions (DRDs), including the Small Business Subcontracting Plan (DRD 8), the Total Compensation Plan (DRD 10), and other plans and sections contained within this contract and as directed through authorized task orders and contract modifications. The contractor shall provide ongoing business analysis, and respond to requests from NASA relating to budget, schedule, and cost performance

2.2.1 Financial and Resources Management

The contractor shall develop, implement, maintain, and update a Contract Financial System that discretely tracks resources by Work Breakdown Structure (WBS) and individual IDIQ tasks, and provides elements of cost including labor, overhead, other direct costs, and indirect costs. The contractor shall provide cost reporting in accordance with NASA Form (NF) 533 as specified in the NASA Contractor Financial Management Report per DRD 11.

Subcontractor reporting requirements are applicable to all tiers of subcontractors with annual expenditures of exceeding $100,000 per year, or the top eight subcontractors by value for the year, whichever option results in the greater number of reported subcontractors. The Contractor shall document and provide cost performance per DRD 9.

The contractor shall report annually on the status of each of the activities under this contract citing accomplishments, issues and future plans. For each annual planning cycle the contractor, in conjunction with the NASA sponsor, shall identify the specific tasks, milestones and deliverables for each SOW activity. Task values and resources shall be assigned by the contractor and approved by each task sponsor.

Quarterly Progress Reports shall be submitted in accordance with DRD 13. As a reporting function of the Quarterly Progress Reports and in conjunction with the Financial Management Reports, the contract performance metrics shall be provided in the Quarterly Progress Reports.

2.2.2 Organizational Conflict of Interest and Non-Disclosure Agreements The contractor shall work as part of the government team through an established Organizational Conflict of Interest (OCI) Avoidance Plan. The OCI Avoidance Plan shall also document any Non-Disclosure Agreements (NDAs) that are required to execute the contract or may adversely impact the performance of the contractor. The contractor shall provide the OCI Avoidance Plan and NDA documentation relevant to this contract per DRD

C-5

2. The contractor shall maintain and update its OCI Avoidance Plan during the performance of this contract, as necessary.

2.2.3 New Technology

The contractor shall establish and deliver a Technology Commercialization Plan in accordance with DRD 4.

2.3 Information Technology

2.3.1 Information Technology Security

The contractor shall submit for approval an Information Technology (IT) Security Program and Reports per DRD 3 to be consistent, in form and content, with NIST SP 800-18, Guide for Developing Security Plans for Federal Information Systems, and any additions/augmentations described in NASA NPR 2810.1A, Security of Information Technology. The contractor shall maintain and update its IT Security Program, as necessary.

2.3.2 Export Control

The contractor shall control data in compliance with clause NFS 1852.225-70, Export Licenses.

The contractor shall provide an Export Control Plan per DRD 5.

3.0 GN&C AND AVIONICS TECHNOLOGY DEVELOPMENT

AND ANALYSIS

NASA will require contractor support for the research, development, and integration of GN&C and avionics technologies, components, and systems. The scope includes, but is not limited to, the definition, design, analysis, production, testing, verification and validation, certification, and operation of GN&C and avionics systems and associated hardware and software elements for surface, atmospheric, and spaceflight applications. These systems may be fully autonomous, remotely operated, piloted by onboard crew, or a combination of those options. The requirements may involve the modification or upgrade of GN&C and avionics technologies, elements, or systems associated with historical or ongoing NASA projects and missions.

3.1 International Space Station (ISS)

3.1.1 ISS Command and Data Handling and Automation

Software Sustaining Engineering for Timeliner The contractor shall assist the ISS Program with the sustaining engineering Timeliner software Kernel (core features) and Adapter (ISS adaptation) for both the ISS onboard and ground C&DH elements. The contractor’s development activities shall follow the Sustaining Engineering Computer Software Configuration Item (CSCI) Release Process described in the

C-6

ISS Software Management Plan (SSP 50482 Rev A) to provide block updates to the current Timeliner software release. New releases shall incorporate approved solutions to Problem Reports (PRs) generated in the test and integration of the Timeliner software with the Command & Control (C&C) and Payload Multiplexer/Demultiplexers (MDMs) as well as NASA-directed Program Changes and functional enhancements. The contractor shall ensure Timeliner compatibility with ISS Program directed upgrades to operating systems and compilers. The contractor shall support integration of the Timeliner segments into the ISS C&DH ground and onboard systems and end-to-end testing of the results. In addition, the contractor shall provide operations concept analysis, operational tools and training for the development, use, and execution of Timeliner procedure scripts. This effort shall include the design, development, integration and test of onboard and ground ISS software and integrated C&DH systems. These systems are the integrated C&DH architectures, crew Portable Computer System (PCS), telemetry systems, payload/core command and control systems, and ground database systems. The contractor shall provide Timeliner related operational development, integration and sustaining engineering for these systems in the flight hardware/software development, verification and operational environments, as well as the crew/ground operations and training environments.

The contractor shall provide integration support and flight software sustaining engineering for the automated procedure executor component of Timeliner.

The contractor shall provide required inputs to the ISS software change reports documenting anomalies in the Timeliner software flight and ground software and for product improvement SCR’s.

The contractor shall assist the ISS Prime Contractor for flight software in the integration of the updated Timeliner software into release of the command and control software CSCL and the payload processor CSCI, including resolving problem reports (PRs) generated in the test and integration of the Timeliner software into the command and control software CSCI and payload executive processor CSCI.

The contractor shall assist the NASA-JSC Flight Operations Directorate (FOD) in the integration and testing of the Timeliner Compiler at JSC.

The contractor shall assist the NASA Marshall Flight Center (MSFC) in the integration and testing of the Timeliner compiler located at MSFC.

The contractor shall ensure Timeliner compatibility with upgrades to operating systems and compilers directed by the ISS Program.

The contractor shall conduct training for the development, use and execution of Timeliner procedure scripts, as required by NASA.

The contractor shall support the Timeliner Roundtable User telephone conference that is conducted on a regular basis.

ISS Autonomous Operations Development The contractor shall develop advanced concepts and tools for autonomous operation of the ISS. These tools shall support increased automation for both Core and Payload systems. The

C-7 tools shall be derived from current ISS capabilities, specifically the Timeliner automated procedure language. The contractor shall create ground development tools to provide the necessary development and verification capabilities for flight operations. The contractor shall support the application of the ISS as a testbed for exploration system automation concepts.

The products of this task are the concept analyses and advanced automation tools and capabilities.

ISS Milestones Date Timeliner Updates As Required

ISS Deliverables Date

Memos, Briefings, and Presentations As Required Release Notes As Required

3.2 Multi-Purpose Crew Vehicle (MPCV) GN&C

The Orion GN&C team operates under a Multiple Organizational Design and Engineering (MODE) team agreement between NASA and the prime contractor. MODE team responsibilities are divided by flight phase (Ascent/Abort, Orbit and Entry), with three exceptions (Navigation, Integration, and Fault Detection Isolation and Recovery) whose responsibilities span flight phases.

The contractor shall leverage its experience from the Apollo and Space Shuttle programs, as well as MPCV program, to continue to develop, implement, test and support the flight of the Orion GN&C system, including sensors, algorithms and software. These efforts will be coordinated through the AFMD Ascent/Abort, Orbit, Entry, Navigation, Fault Detection, Isolation and Recovery (FDIR), and Integration and Test (I&T) MODE teams. In addition, the contractor shall utilize its unique set of tools, algorithms and software developed under previous NASA contracts for these tasks as discussed in the sections below. Finally, the contractor shall provide systems engineering and program management for its activities.

The contractor shall support the MPCV Program including all activities described below for Artemis missions.

3.2.1 GN&C Flight Software (FSW) Production

Orbit MODE Team (OMT) The contractor shall define requirements and preliminary design for orbit GN&C algorithms.

This will include the development of graphical Simulink algorithm components and analysis of algorithm performance, as well as analysis of integrated on-orbit performance for vehicle-level design trades.

The contractor shall provide GN&C systems engineering analysis for the European Service Module (ESM) concepts, to include RCS thruster configuration analyses, delta-V or

C-8 propellant analysis, thrust vector control analysis or other ESM GN&C systems definition analyses as directed.

Entry MODE Team (EMT) The contractor shall provide a graphical implementation of its unique predictive guidance (PredGuid) algorithm as Entry guidance for the Orion spacecraft. PredGuid shall include versions capable of flight test vehicle entry, entry from Low Earth Orbit, and entry from exo- LEO orbits. The contractor shall assist in the integration of PredGuid into the GN&C FSW architecture and will provide guidance expertise for the integration of GN&C FSW into Orion hardware test facilities and flight test vehicles. Additionally, the contractor shall perform entry guidance verification by analysis and shall support entry guidance verification by test in Orion HWIL test facilities.

Navigation MODE Team (NMT) The contractor shall provide review and upgrades for the Orion absolute navigation algorithms. The upgrades shall consist of modifications to the graphical navigation implementation to meet evolving requirements, facilitate integration into the GN&C partition, provide initialization and commanding capabilities, etc.

The contractor shall assist the NMT to integrate the navigation software algorithms into the GN&C partition software. Assistance shall also be provided to integrate the navigation sensors into the avionics hardware in test facilities and on flight test vehicles. This effort will include assessment of navigation performance in real time, HWIL tests.

The contractor shall provide software, tools and support for the analysis of absolute navigation algorithms and flight software. Products will include automated tools for reducing Monte Carlo analysis data, as well as analysis reports and other performance verification artifacts.

Ascent Abort MODE Team (AAMT) The contractor shall lead the integration of the end-to-end abort simulation to perform aborts that use the Orion European Service Module (ESM). The integration effort will include ESM effector models for the simulation as well as ESM control and guidance algorithms for the flight software. The contractor shall also assist with the integration of Launch Abort System (LAS) models and software to perform early ascent abort simulations for future Orion flight tests and missions.

3.2.2 Integration, Test & Verification

The contractor shall provide leadership, tools and skills in the production of GN&C flight software for Orion Exploration Mission vehicles. The contractor shall apply graphical tools, and documents developed in conjunction with AFMD on previous tasks including Shuttle Upgrades, Graphical Integrated Development Environment (GIDE), and MPCV, as well as unique graphical process tools, standards and artifacts developed on other NASA-sponsored projects.

C-9

As Orion vehicles enter the production phase, the contractor shall leverage its extensive experience with integration development and test (IDT) of NASA crewed vehicles and other spacecraft, to plan and execute hardware-in-the-loop IDT. This will include developing schedules, negotiating deliveries and leading teams to integrate GN&C sensors, sensor test hardware, and GN&C software into Orion testbed facilities. Additionally, the contractor shall support the development and execution of verification and validation test plans and analysis. The contractor shall provide coordination and real-time support for dry runs and runs for record of the GNC verification test cases in HWIL facilities including the Integrated Test Laboratory (ITL) in Denver. The contractor shall provide tools, coordination and leadership for post processing ITL test cases and producing verification reports.

The contractor shall provide simulation models and dynamics for use in development and integration of GN&C algorithms and flight software. The contractor shall provide experienced leadership in the development and execution of GN&C simulation validation, and configuration management processes.

3.3 Advanced GN&C and Avionics

As required the contractor shall:

• Assess, develop, and apply GN&C and avionics technologies to support NASA requirements

• Perform the design, development, and integration of GN&C and avionics hardware and software associated with real-time, embedded vehicle systems

• Conduct systems engineering analysis, trade studies, design analysis, and technology demonstrations for vehicle GN&C and avionics using new or existing hardware and software technologies or capabilities

• Provide system engineering and technology studies, reports, and documentation

• Support the development and application of NASA GN&C and avionics simulation environments for crewed, cargo, and robotic vehicles

• Perform sensitivity analyses and linear covariance analyses

• Assess, develop, and apply fault tolerance and fault detection, isolation, and recovery (FDIR) strategies for vehicle GN&C and avionics systems

• Provide integration and flight test support services related to assessment of Entry Decent and Landing, Guidance Navigation and Control, or other space exploration and utilization technologies

• Utilize the knowledge, tools, and capabilities developed during prior NASA programs

• Provide a conduit to advanced GN&C and avionics technologies developed through the contractor’s participation in other government programs

• Facilitate technology insertion into advanced space demonstration and operational systems

C-10

Many of the tasks above will support the Safe & Precise Landing – Integrated Capabilities Evolution (SPLICE) Project and Gateway Program.

3.4 Technical Reporting

The contractor shall document and deliver engineering documentation and reports for IDIQ tasks and in accordance with Technical Reports, DRD 12.

4.0 SAFETY AND MISSION ASSURANCE

4.1 Quality Assurance

The contractor shall have a quality program that complies with the AS9100C, Quality Management Systems Requirements for Aviation, Space and Defense Organizations. The contractor shall develop a Quality Plan specifically for this contract in accordance with DRD 11.

The contractor shall define its Software Assurance Plan per DRD 14.

For activities performed onsite at JSC, the contractor shall adhere to the JSC Quality Management System.

4.2 Safety and Health

The contractor shall develop, document, and implement a Safety and Health Plan per DRD 7 in which activities are assessed for hazards, and in which personnel and property will be protected from injury or harm resulting from exposure to these hazards. As specified within DRD 7, the Contractor shall prepare and deliver Accident/Incident Summary Reports as defined in JSC Form 288, Statistical Information – Contractor Safety and Health Program. The contractor’s safety and health approach shall include both design and procedurally controlled activities. The contractor’s Safety and Health Plan shall include auditable approaches to achieve safe operations and ensure flight safety. The contractor shall report and investigate accidents, mishaps, anomalies and close calls in accordance with the most recent JPR 1700.1, JSC Safety and Health Handbook.