RPOC IV contract data and FY22 TOs.pdf

Rendezvous Proximity Operations, and Capture (RPOC IV) Contract Data and Fiscal Year 2022 (FY22) Task Orders (TO) ****The content listed below is not indicative to any new RPOC re-procurement requirements.

The content should only be used for an informational bases of the contract structure, which has been abstracted from the RPOC IV contract.

CONTENT

RPOC IV STATEMENT OF WORK (SOW)

FY22 TASK ORDERS

STANDARD LABOR CATERGORIES (SLC)

JSC DATA REQUIREMENTS LIST (DRL)

DATA REQUIREMENTS DESCRIPTION (DRD)

INSTALLATION ACCOUNTABLE PROPERTY (IAP)

NNJ16582596R

C-1

SECTION C - DESCRIPTION/SPECIFICATION/WORK STATEMENT

1.0 PROJECT OVERVIEW/SCOPE OF WORK

This Statement of Work (SOW) outlines the requirements to provide engineering support services

(research, analysis, design, development, integration, verification, test, evaluation, and operations support) supporting Guidance, Navigation and Control (GN&C), system engineering, and RPOC initiatives. The Contractor shall provide engineering support in projects and technical areas such as those below in support of the NASA Johnson Space Center (JSC) and its external customers:

International Space Station (ISS) Program

Orion Program and related exploration initiatives

Technology Development, Support, and Research

The scope of these tasks encompasses the program architecture definition, analysis and development, as well as the entire spacecraft definition and development process including requirements development, concept development, technology development, system design, system and vehicle evaluation, system and vehicle test, verification, integration and operations support. Examples of tasks to support these systems includes the development of analysis tools, including modeling of space vehicles, vehicle subsystems, dynamics, and environment in a high-fidelity simulation environment, and development of tools to support command and monitoring analysis including high fidelity graphics and user interfaces. The structure of the SOW should not be construed as defining a required organizational configuration. Specific tasks will be authorized on task orders.

NASA will provide facilities for vehicle software and other software required for the effort onsite at

NASA JSC and make it available for use at the Contractor facility through a network server account.

Performance of the work under this contract is subject to the technical direction of the Contracting

Officer’s Representative (COR), who shall be specifically appointed by the Contracting Officer (CO) in writing. "Technical direction" means a directive to the Contractor that approves approaches, solutions, designs, or refinements; fills in details or otherwise completes the general description of work or documentation items; shifts emphasis among work areas or tasks; or furnishes similar instruction to the Contractor. Technical direction includes requiring studies and pursuit of certain lines of inquiry regarding matters within the general tasks and requirements in Section C. Technical direction does not include authorizing contractual instruments.

Contractor personnel may be required to travel to participate in major reviews and technical interchange meetings for many of these tasks. This travel may be both domestic and international.

Details of expected travel will be provided in task orders.

2.0 DESCRIPTION OF WORK

2.1 Project Management

The Contractor shall be responsible for the management of the contract to assure accomplishment of contract work and compliance with contract clauses and Data Requirement Documents (DRDs). The

Contractor shall provide all management, supervision, programming, technical, and administrative

C-2 support, as well as technical disciplines, skills and documentation necessary to ensure effective and efficient accomplishment of the total contracted effort.

The Contractor shall assure that the project management team has the authority necessary to respond to appropriate contractual direction, is responsible for effort relating to technical and administrative functions, and will maintain a focal point for management of all contract data requirements and issues.

The Contractor’s project management shall ensure that there are single point interfaces with the

NASA JSC CO and COR.

2.2 ISS PROGRAM

2.2.1 The Contractor shall support verification of ISS Visiting Vehicles using RPOC related ISS requirements. The analysis of the vehicles, trajectories, and operations includes simulation of the vehicle, the ISS, and the environment. The vehicles included in this effort deliver cargo and crew to the ISS. Visiting Vehicles operations concepts include both capture/berthing and self-docking vehicles. All non-Russian Visiting Vehicles will be assessed. The purpose of these analyses is to ensure each vehicle’s adherence to applicable ISS requirements and Commercial

Crew Transportation Capability (CCtCAP) (when applicable) requirements.

For visiting vehicles in the design phase, the Contractor shall support an assessment of each vehicle’s design to verify that the design meets all applicable ISS and CCtCAP (when applicable) requirements during the ISS rendezvous, proximity operations, docking, undocking, and departure phases of flight.

Work will include development of an independent GN&C simulation for each visiting vehicle, as well as, a review of vehicle design, development, certification, and mission specific products. The

Contractor shall also support the development, test, and verification of the ISS crew monitoring capabilities to be used during the approach, capture or docking maneuver, docking, if applicable, undocking, and departure from the ISS.

The Contractor shall provide NASA with documentation and results to support a recommendation relative to certification of flight readiness (CoFR) for each non-Russian visiting vehicle and shall identify and record any limitations of the content and analysis supporting the recommendation.

2.2.2 The Contractor shall support development of simulation and analysis tools for each of the vehicles using the existing NASA/JSC simulation development environments. These software tools will be used to support independent vehicle design and development evaluations, mission design assessments, ISS requirements analysis and verification, and ISS and crew safety evaluations. Elements of this tool set shall be provided to the ISS Program for integration into the crew and flight controller training simulation tool sets.

2.3 Orion Program and related exploration initiativesThe Contractor shall support

NASA JSC’s efforts in GN&C areas related to the Orion Program and related exploration initiatives. This effort includes planning, designing, and developing software tools and simulation products to support mission design/evaluation, requirements analysis, strategy development, and safety evaluation. Software, software tools, and simulation products will be used to perform the requirements. This support may include the following–

GN&C requirements development/assessment.

Architecture, mission design, reference mission assessments, GN&C system level evaluation and assessment.

C-3

GN&C technology assessments and evaluations.

Use of software, software tools, and simulation products to conduct mission design/evaluation, requirements analysis and safety evaluation. Legacy software tools rely on the Trick and JSC Engineering Orbital Dynamics

(JEOD) simulation environments.

Hardware, integration, lab maintenance, and simulation development support.

Integration of GN&C related flight software elements for delivery to the

Orion prime Contractor.

2.4 Technology Development, Support, and ResearchThe Contractor shall provide specialized support for development, analysis or research of technologies related to

NASA JSC activities. This support may include the following –

Support development and use of software, software tools, and simulation to support GN&C technologies

Provide specialized support for tool development and/or implementation in NASA/JSC’s development, analysis and test labs. Specialized support includes support unique to the tools and models, analysis, and hardware developed for the JSC activities outlined in Sections 2.2 and 2.3

Support development of prototype tools as required to validate new concepts

Support design and development of guidance and trajectory tools

Perform systems engineering, requirements development and analysis

Support development of ground and on-orbit test and demonstrations designed to investigate and validate new technologies

Leverage existing tools, processes and experience to minimize additional development and analysis effort

2.4.2 The Contractor shall support research and develop prototype GN&C concepts to support improvements in the ascent, rendezvous, on-orbit, entry, and landing phases of flight.

These include related systems/subsystems and software to enhance failure detection, isolation, and recovery (FDIR), command and control, crew visualization and intervention and other vehicle or system/subsystem functions.

3.0 REPORTING REQUIREMENTS

Reporting shall adhere to requirements as defined in the Data Requirements List (DRL).

4.0 QUALITY ASSURANCE

JSC is Society of Automotive Engineers (SAE) AS9100 registered and intends to maintain this certification. The Contractor shall perform all work on-site in accordance with the JSC Quality

Management System. Any work performed off-site, using the JSC network server, shall also comply with the JSC Quality Management System.

5.0 SAFETY AND HEALTH

The Contractor shall perform tasks to ensure the protection of personnel, property, equipment, and the environment in Contractor products and activities generated in support of institutional and spaceflight program objectives. To ensure compliance with pertinent NASA policies, requirements, federal, state, and local regulations for safety, health, environmental protection, and fire protection, the

Contractor will develop and implement a safety and health program per a NASA-approved safety and

C-4 health plan specified in the DRL. The “JSC Safety and Health Handbook” provides detailed requirements and instructions regarding safety and health procedures and policies at JSC and is incorporated by reference into all JSC contracts when performance is on site at a JSC facility. It can be viewed at http://jschandbook.jsc.nasa.gov/.

6.0 REFERENCE DOCUMENTS

The following documents and schedules are applicable for the work to be performed under the

Statement of Work:

Item Document

No. Number Title

1. SSP41000 System Specifications for International Space Station (ISS)

2. SSP41163 Russian Segment Specification

3. SSP50038 Computer Based Control System (CBCS) Requirements

4. SSP50021 ISS Safety Requirements Document

5. SSP50261 ISS Generic Ground Rules, Requirements, and Constraints

– Part 1: Strategic and Tactical Planning

6. SSP50438 ISS to HTV Interface Control Document

7. SSP50273 Segment Specification for the H2 Transfer Vehicle (HTV)

8. SSP50420 H2 Transfer Vehicle (HTV) Bilateral Integration and

Verification Plan

9. SSP50575 Bilateral H2 Transfer Vehicle (HTV) Operations Plan

10. NPR 8705.2 Human-Rating Requirements for Space Systems

11. SSP50808 International Space Station (ISS) To Commercial Orbital

Transportation Services (COTS) Interface Requirements

Document (IRD), Revision A

12. NPR 7150.2B NASA Software Engineering Requirements

13. JPR 7150.2 JSC Software Engineering Procedural Requirements

14. JPR 1280.2E Quality Manual http://jschandbook.jsc.nasa.gov/

Contract 80JSC01D0001 Task Order 36

Period of Performance 10/01/2021 to 9/30/2022

TASK ORDER 36

TASK ORDER TITLE: SpaceX Lander Mission Design - 2022

NASA TASK MANAGER: G. Condon / EG5

PERIOD OF PERFORMANCE: October 1, 2021 to Sep 30, 2022

TASK OVERVIEW

Provide Mission Design and Trajectory Analysis of SpaceX Lunar Lander design

TECHNICAL REQUIREMENTS

(1) Update models and develop analysis related software to support optimization for key elements of Starship mission

a. Develop/modify, as needed, the Initial Guess Generator (IGG) software to support preliminary mission design and trajectory optimization analysis as well as to serve as a seed trajectory generator to enhance/guarantee Copernicus convergence

b. Develop/modify a Rendezvous and Proximity Operations (RPOD) “quick look” performance tool that provides data-informed estimates of RPOD mission performance and flight profiles for rendezvous at the NRHO-Gateway and/or in (circular or elliptical) lunar or Earth orbit.

(2) Develop Copernicus template I-decks (preliminary and detailed) for selected mission scenarios and design dates as described below

(3) Perform assessment of Space-X nominal mission profile(s) and all trajectory abort modes

(4) Support development/modification/refinement of nominal mission trajectory design (as required) for both in-space and powered flight trajectories (e.g., descent and ascent)

a. Support both independent (in-space vs powered flight) and integrated (in-space plus powered flight) trajectory development/assessment

(5) Support development/modification/refinement of trajectory off-nominal or abort modes for all flight phases for both in-space and powered flight trajectories (e.g., descent and ascent)

a. Assess/develop abort down-moding plans for abort situations as dictated by vehicle limitations or other constraints

i. Transition from full target line Earth return (e.g., deliver crew to splashdown off the coast of San Diego, CA) to down-mode or alternate Earth return options: full target space, multiple target line options, generalized abort (relaxed target constraint designed to achieve water landing)

b. Assess/develop techniques for identification and trajectory modification with regards to instantaneous impact determination at the intended landing site

(6) Perform detailed trajectory design and optimization for delivery of the Lunar Starship from LEO to Lunar orbit using Starship/Superheavy launch vehicle.

a. Analyze LEO mission scenarios including optimizing LEO Starship Propellant Tanker orbits and contingencies such as Starship tanker launch delays and Lunar Starship launch delays

(7) Analyze LEO-to-Lunar orbit (NRHO, LLO, or other staging orbit) for Orion Rendezvous with Starship (If direct Starship to Orion is used for initial mission)

a. Coordinate Orion Rendezvous orbit options with HLS Program

b. Fast transfer trajectories

c. Ballistic Lunar Capture trajectories (simple and complex)

i. Simple: no outbound lunar flyby

ii. Complex: Utilizing outbound lunar flyby

d. Analyze LEO to rendezvous orbit, coordinated Orion operations, and contingency operations such as Orion launch delays

(8) Analyze LEO-to-rendezvous with Gateway

a. Fast transfer trajectories

b. Ballistic Lunar Capture trajectories (simple and complex)

i. Simple: no outbound lunar flyby

ii. Complex: Utilizing outbound lunar flyby

c. Staged orbits near Gateway to support timing for Orion arrival

d. Staged orbits to Gateway rendezvous and direct to Gateway rendezvous

(9) Analyze trajectories from Orion to lunar surface (If direct Starship to Orion is used for initial mission)

a. Orion-to-Low Lunar Orbit (LLO) and LLO-to-Surface

b. Orion-to-surface direct

c. Optimal (prop and time), fail-safe strategies, contingencies

d. Aborts back to Orion during all phases

(10) Analyze trajectories from Gateway to lunar surface

a. Gateway-to-Low Lunar Orbit (LLO)-to-surface

b. Optimal (prop and time), fail-safe strategies, contingencies

c. Gateway to surface direct

i. Identify landing sites reachable from NRHO

(11) Lunar Surface to Orion (If direct Starship to Orion is used for initial mission)

a. Surface-to-LLO and LLO-to-Orion orbit

b. Aborts for all phases including surface aborts

c. Coordinated Starship/Orion Rendezvous options (nominal and for abort support)

(12) Lunar Surface to Gateway

a. Surface-to-LLO and LLO-to-Gateway orbit

b. Aborts for all phases including surface aborts

c. Coordinated Starship/Orion Rendezvous options (for abort support)

(13) Orion orbit to Post-crew-transfer trajectory (If direct Starship to Orion is used for initial mission)

a. Disposal orbits or other options

(14) Gateway undock to post-crew-transfer trajectory

a. Disposal orbits or other options

(15) Support Copernicus improvements to enable success and efficiency on all forward HLS analysis

a. Execution speed improvements on integrated design reference mission input deck

b. Refinement of LEO, refueling, and TLI portion of the design reference mission

c. Preparing idecks and Python scripts for executing scans

d. Executing Copernicus scans

i. Epoch scans

ii. Lunar surface capability scans

e. Developing automated scripts/tools for performing Quality Control checks on idecks (for things like time/mass/state continuity, and other sanity checks)

(16) Nominal mission scans with mission availability impacts (e.g., due to eclipsing, line of sight AOS/LOS comm., landing sun vectors during landing/approach). Much of this is decision making on approach and post-processing and plug-in development as needed, Integrated mission including powered flight, aborts -- powered descent abort, missed primary burn aborts, underburn recovery.

(17)

a. Identifying and developing any plugins that would add value to our optimization problem

Deliverables

Provide data and reports, and support presentation of the analyses results at HLS required reviews.

Contract 80JSC17D0001 Task Order 37

Period of Performance 10/1/2021 – 9/30/2022

TASK ORDER 37

Gateway Vehicle Insight and Control Software Development & IntegrationTASK ORDER TITLE:

NASA TASK MANAGER: EV3 / Cory Simon

PERIOD OF PERFORMANCE: October 1, 2021 to September 30, 2022

1. Telemetry and Command Server (TCES) Lead Developer

i. Subcontractor(s) shall be responsible for leading development of TCES and ensuring software maturation toward flight for Gateway.

ii. Subcontractor(s) shall be responsible for integrating and testing TCES with

Gateway Flight Software (FSW) development products.

iii. Subcontractor(s) shall be responsible for supporting non project TCES users, including providing documentation of architecture and users guide.

iv. Subcontractor(s) shall be responsible for communicating with the FSW team to ensure that the Command and Data Dictionary (CCDD) is scripted to output a standards based and compatible XTCE format.

v. Subcontractor(s) shall be responsible for TCES performance improvements including but not limited to support for non-networked telemetry streams, updates to the REST interface for simplified interaction with the Display Webserver (DWS), and streamlining bundled data transfer with the DWS.

vi. Subcontractor(s) shall be responsible for expanded TCES functionality including but not limited to command acknowledgement, configuration options, and updates to triplex flight computer logic.

vii. Subcontractor(s) shall be responsible for re-implementing standard mechanism for telemetry logging and playback.

viii. Subcontractor(s) shall aide in deployment and testing of TCES on Gateway developmental systems and other platforms as necessary.

2. Chisel and Web Server Supporting Developer

i. Subcontractor(s) shall contribute to the deployment, maturation, and testing of the

Chisel tool. Chisel is a web based “What You See Is What You Get” (WYSIWYG) display building tool. It allows users to edit and manipulate display widgets via a drag and drop interface and property editor to quickly and efficiently build displays.

ii. Subcontractor(s) shall aide in the development and deployment of expanded features to the human interface reference architecture and display webserver including but not limited to user access and authentication, and audio and video support.

iii. Subcontractor(s) shall develop, test, and integrate required display widgets. Display widgets are packaged self-contained, reusable code based upon the W3C Web Component Standard.

iv. Subcontractor(s) shall contribute to the deployment, maturation, and testing of the

Contract 80JSC17D0001 Task Order 37

Period of Performance 10/1/2021 – 9/30/2022

Display Web Server (DWS). DWS is path to flight node.js based web server being matured to host crew displays.

3. General Software Support

i. Subcontractor(s) shall advise and support team with general software experience and expertise and assist in integration activities as required.

ii. Subcontractor(s) shall aide in the integrated vehicle testing of the NASA Reference

Architecture

DELIVERABLES

• Software products and real time support for integrated testing with the Gateway

Flight Software Team.

• Turnover of source code and binaries.

• Complete code reviews with oversight provided by Gateway Vehicle Insight and

Control project team.

• Documentation of code and architecture, and Users Guides where relevant.

• Documentation on telemetry and command object (TOCO) format including a user’s guide on creating and modifying the TOCOs.

Contract NNJ16582596L Task Order 10 – SPLICE

Period of Performance 10/01/2021 – 9/30/22

TASK ORDER 38 rev 1

TASK ORDER TITLE: SPLICE GFY 2022 Revision 1

NASA TASK MANAGER: Teming Tse

PERIOD OF PERFORMANCE: October 1, 2021 to September 30, 2022

The objective of this task is to support the NASA SPLICE (Safe & Precise Landing – Integrated Capabilities Evolution) project in the development of: 1) a flight dynamics simulation for generic lander designs; and, 2) implementation of GN&C (guidance, navigation and control) flight software for use on suborbital flight tests. The SPLICE project is developing the simulation to use basic, common models of guidance, navigation and control (GN&C) sensors and algorithms, and plans to evolve these generic models into specific vehicle simulations to perform testing with both hardware-in-the loop (HWIL) sensors and avionics, as well as flight software (FSW). The SPLICE project is also developing FSW for implementation and flight testing of new avionics and GN&C sensors onboard suborbital rocket testbeds, also known as VTBs (Vertical Testbeds).

The simulation should be capable of flying various landing profiles for Earth, Moon, and Mars, as well as ascent profiles for cases where the vehicle is a terrestrial, sub-orbital rocket testbed. The simulation will use Trick and JEOD models, and the framework shall be designed for extension to include HWIL and FSW components. The simulation must have the ability to interchange any basic sensor model with a specific detailed or specialized sensor model, and the ability to switch between various GN&C algorithms.

The FSW will utilize the cFS (core Flight System) framework running onboard the Descent & Landing Computer (DLC) avionics that are in-development within the SPLICE project. Development of the FSW will include involvement with other members of the SPLICE project team.

Flight testing of the FSW is targeted for a future VTB flight onboard the Masten(or similar) VTB in government fiscal year 2023.

Tasks:

• Continue development of generic lander simulation, along with a version specific to the Masten new vehicle.

• Continue to perform testing and revisions to the simulations, including the Precision Landing and Hazard Avoidance (PL&HA) sensor models and Masten new vehicle models, with comparisons against existing flight data or data from other simulations.

o Continue to enhance the fidelity of the Navigation Doppler Lidar (NDL) model and support parametric tuning of the model to provide outputs inline with existing NDL flight test data o Support the enhancement of the camera model to provide images to the TRN system.

o Develop a Hazard Detection Lidar model and support software integration and communication with flight software.

o Support the integration of the Hazard Detection Algorithm into the DLC hardware.

• Continue to document simulation architectures, relative models and interfaces.

• Development of tools to automate testing, software standard assessments and performance metrics

• Continue to support NASA with architectural planning for expansion of the simulation to include HWIL and FSW options for future PL&HA and VTB testing.

o Support enhancement of serial communication architecture between Trick simulation and protocol translator (PT) hardware.

o Development of spacewire simulation communication between Trick simulation and PT or DLC hardware.

o Support the development and implementation of timing architecture between simulation and unit-under-test flight computer.

• Continue to support NASA with architecture of cFS-based FSW.

o Support porting of SPLICE cFS FSW to different versions of the DLC hardware platform.

o Work with application developers to improve the quality of software code.

o Implement and test input and output (I/O) apps that communicate with hardware using the DLC data transport protocol o Update as required for the Masten-DLC interface including the testing and verification of telemetry and commands with host vehicle.

• Support NASA in the implementation of cFS-based software applications that implement the SPLICE GN&C algorithms, interface with PL&HA sensors, and support overall VTB flight test operations.

o Perform integrated testing of SPLICE cFS FSW with the Masten host vehicle or host vehicle emulator.

Masten host simulation.

o Support third-party software integration and testing with the DLC/cFS architecture.

o Support the performance measurement of flight software executing on the DLC/cFS architecture.

o Support testing of Dual Quaternion Guidance(DQG)and Terrain Relative Navigation (TRN) within the DLC/cFS architecture

• Support flight activities at Masten facility at Mojavo, CA

• Continue to development and improve COSMOS ground display system for laboratory and flight testing for future uses.

o Build COSMOS displays for the development, integration and flight testing of DLC flight software.

o Configurate COSMOS to support integrated testing in the lab and flight test environment.

o Test and debug sub-system COSMOS displays.

• Support the integration and testing of simulation with new version of the Descent and Landing Computer (DLC ETU).

• Work alongside NASA, third party companies and team members to implement and test the SPLICE flight software architecture and cFS applications.

Travel

- No travel expected.Two trips to Mojave, CA for a duration of approximately 5 days for each trip.

1. Attend SPLICE project meetings and provide status of activities at those meetings.

2. Updated test procedures for integration to new version of DLC (ETU version).

3. Software Documentation for each software release

a. Provide updates to the release notes/documentation of each software release

b. Preliminary FSW Updated (Mar 2022)

c. Critical FSW Updated (Sept 2022)

4. Demonstrate previous features and capabilities are intact.

As noted within individual deliverables, this work will be performed closely with the SPLICE team, so some target dates are dependent on deliveries external to this task order.

Contract 80JSC017D0001 Task Order 38 – SPLICE

TASK ORDER 38

TASK ORDER TITLE: SPLICE GFY 2022

NASA TASK MANAGER: Teming Tse

The objective of this task is to support the NASA SPLICE (Safe & Precise Landing – Integrated Capabilities Evolution) project in the development of: 1) a flight dynamics simulation for generic lander designs; and, 2) implementation of GN&C (guidance, navigation and control) flight software for use on suborbital flight tests. The SPLICE project is developing the simulation to use basic, common models of guidance, navigation and control (GN&C) sensors and algorithms, and plans to evolve these generic models into specific vehicle simulations to perform testing with both hardware-in-the loop (HWIL) sensors and avionics, as well as flight software (FSW). The SPLICE project is also developing FSW for implementation and flight testing of new avionics and GN&C sensors onboard suborbital rocket testbeds, also known as VTBs (Vertical Testbeds).

The simulation should be capable of flying various landing profiles for Earth, Moon, and Mars, as well as ascent profiles for cases where the vehicle is a terrestrial, sub-orbital rocket testbed. The simulation will use Trick and JEOD models, and the framework shall be designed for extension to include HWIL and FSW components. The simulation must have the ability to interchange any basic sensor model with a specific detailed or specialized sensor model, and the ability to switch between various GN&C algorithms.

The FSW will utilize the cFS (core Flight System) framework running onboard the Descent & Landing Computer (DLC) avionics that are in-development within the SPLICE project. Development of the FSW will include involvement with other members of the SPLICE project team.

Flight testing of the FSW is targeted for a future VTB flight onboard the Masten(or similar) VTB in government fiscal year 2023.

• Continue development of generic lander simulation, along with a version specific to the Masten new vehicle.

• Continue to perform testing and revisions to the simulations, including the Precision Landing and Hazard Avoidance (PL&HA) sensor models and Masten new vehicle models, with comparisons against existing flight data or data from other simulations.

o Continue to enhance the fidelity of the Navigation Doppler Lidar (NDL) model and support parametric tuning of the model to provide outputs inline with existing NDL flight test data o Support the enhancement of the camera model to provide images to the TRN system.

o Develop a Hazard Detection Lidar model and support software integration and communication with flight software.

o Support the integration of the Hazard Detection Algorithm into the DLC hardware.

• Continue to document simulation architectures, relative models and interfaces.

• Development of tools to automate testing, software standard assessments and performance metrics

• Continue to support NASA with architectural planning for expansion of the simulation to include HWIL and FSW options for future PL&HA and VTB testing.

o Support enhancement of serial communication architecture between Trick simulation and protocol translator (PT) hardware.

o Development of spacewire simulation communication between Trick simulation and PT or DLC hardware.

o Support the development and implementation of timing architecture between simulation and unit-under-test flight computer.

• Continue to support NASA with architecture of cFS-based FSW.

o Support porting of SPLICE cFS FSW to different versions of the DLC hardware platform.

o Work with application developers to improve the quality of software code.

o Implement and test input and output (I/O) apps that communicate with hardware using the DLC data transport protocol o Update as required for the Masten-DLC interface including the testing and verification of telemetry and commands with host vehicle.

• Support NASA in the implementation of cFS-based software applications that implement the SPLICE GN&C algorithms, interface with PL&HA sensors, and support overall VTB flight test operations.

Masten host vehicle or host vehicle emulator.

Masten host simulation.

o Support third-party software integration and testing with the DLC/cFS architecture.

o Support the performance measurement of flight software executing on the DLC/cFS architecture.

o Support testing of Dual Quaternion Guidance(DQG)and Terrain Relative Navigation (TRN) within the DLC/cFS architecture

• Support flight activities at Masten facility at Mojavo, CA

• Continue to development and improve COSMOS ground display system for laboratory and flight testing for future uses.

o Build COSMOS displays for the development, integration and flight testing of DLC flight software.

o Configurate COSMOS to support integrated testing in the lab and flight test environment.

o Test and debug sub-system COSMOS displays.

• Support the integration and testing of simulation with new version of the Descent and Landing Computer (DLC ETU).

• Work alongside NASA, third party companies and team members to implement and test the SPLICE flight software architecture and cFS applications.

- No travel expected.

1. Attend SPLICE project meetings and provide status of activities at those meetings.

2. Updated test procedures for integration to new version of DLC (ETU version).

3. Software Documentation for each software release

a. Provide updates to the release notes/documentation of each software release

b. Preliminary FSW Updated (Mar 2022)

c. Critical FSW Updated (Sept 2022)

4. Demonstrate previous features and capabilities are intact.

As noted within individual deliverables, this work will be performed closely with the SPLICE team, so some target dates are dependent on

Task Order 39

Period of Performance 10/1/21 – 9/30//22

TASK ORDER 39 Orion BFS Development

TASK ORDER TITLE: Orion BFS Development - 2022

NASA TASK MANAGER: Elisabeth Gambone?

PERIOD OF PERFORMANCE: October 1, 2021 to September 30, 2022

TASK OVERVIEW

The primary objective of this task is to support all lifecycle phases of the Orion Backup Flight Software (BFS) software for use on the Orion Artemis 2 flight. Orion Backup Flight Software is Class A safety-critical software that will control the Orion spacecraft in the event of a primary flight software failure. It is a mitigation to the risk of software common cause failure in the primary flight system. The contractor shall provide incremental services for the definition, design, development, analysis, testing, and simulation support of software relating to the BFS project.

SubTask #1: Provide Software Verification Support

The BFS will utilize several test and simulation environments. Support for RAMTARES simulation testing with the BFS applications outside of the CFS environment shall be provided.

This task will work with other developers to develop PLATO tests in the OrionSim simulation environment. These PLATO scripts, written in Python, will be used to verify BFS software requirements in SOC-Lite, SOC-Heavy, and/or VTB test environments.

Specific tasks include the following:

- Verification of integrated BFS GN&C system software requirement specification requirements.

- Support of BFS GN&C Build 204 Verification by Analysis Cycle (VAC)

- Verification of NASA Docking System Heartbeat requirements

- Verification of Artemis 3 BFS GN&C interfaces to propulsion hardware

- Verification of Artemis 3 integrated BFS GN&C performance requirements

SubTask #2: Develop Software Tests

The BFS project is utilizing a development methodology of “test-driven development”. The task to develop software unit tests with GoogleTest will focus on creating tests for comprehensive coverage of SRS-level software requirements. The vision is to build these tests up-front even if they fail, and progressively mature code until all tests successfully pass. Support for verification and validation of BFS applications using the appropriate verification and validation approach (test, analysis, inspection). The contractor shall deliver all required artifacts associated with verification and validation (documentation, test reports, software tests) to satisfy the requirements for Class A flight software.

SubTask #3: Integrated BFS Support

Provide support to the BFS team for ad hoc BFS meetings, reviews, review code merge requests, attending meetings with external stakeholders as required, attending the weekly BFS team coordination meeting, and attending BFS subteam meetings as needed. Provide weekly written status reports via Slack or other reporting mechanism as directed. Updates GitLab Issue status regularly to support project management tracking.

SubTask #4: BFS Simulation Support

Provide support to the BFS team to support integration and testing of the BFS with the ANTARES Trick-based simulation environment to support BFS GN&C simulation analysis. Provide troubleshooting of simulation model issues, logging, input scenario development, post-processing, and data analysis.

SPECIAL SKILLS REQUIRED

Proficient C, C++, and Python language programming, experienced embedded real-time safety-critical systems programming for spacecraft, and an expert knowledge of CFS and how to maintain a mission build for integration roles. Knowledge of Trick-based simulations, VERAS framework, PLATO testing, TIAMAT post-processing, and Pandas timeseries framework processing for supporting verification.

Knowledge of end-to-end software lifecycle development, simulation and test systems. Proficient in the use of configuration management systems such as Git and continuous integration systems. Knowledge of spacecraft command and data handling principles and end-to-end vehicle integration as well as space-to-ground communications is required. For the BFS project, there is a goal to maximize dissimilarity with the Primary flight software, so in that regard, experience on the Orion primary flight software system is discouraged.

DELIVERABLES & SCHEDULES

All flight software deliverables will be documented through monthly progress reports. These report deliverables will contain a status associated with each of the Technical Requirements above along with a listing of technical documents and/or reports made available during that specific month. The culmination of this effort, should it progress for the entire year, should be completion of specified products by the end of the fiscal year. Incrementally and monthly, the contractor shall deliver a progress report and provide related artifacts corresponding to that progress.

Task Deliverable Description Milestone Dates (no later than)

All Tasks Monthly Progress Report Monthly All Tasks Support Artemis 2 Build 204 Release of

Software Verification Products December 31, 2021

All Tasks Support Artemis 2 Build 204 Verification Analysis Cycle (VAC)

December 31, 2021

All Tasks Support Artemis 2 Build 205 Release of Software Verification Products

September 30, 2022

SubTask #1 Verification of NASA Docking System interface and BFS SRS requirements

September 30, 2022

Table 1 – Task Order Deliverables Schedule

Interim schedule requirements are to be identified by the NASA Task Order Manager based on current BFS programmatic milestones and maintained in the BFS Gitlab issue tracking system.

DEPENDENCIES

Development resources including workstations, laptops, network infrastructure, processor hardware, and software licenses for supporting tools will be provided by NASA as part of this task. In some cases, model and/or data deliveries from other organizations and contractors will be necessary to complete specific task order subtasks.

SURVEILLANCE

Task order surveillance will include technical performance, cost performance, schedule response, and significant achievements. Technical performance is based on the contractor’s ability to develop, deliver, integrate, test, and demonstrate flight software product releases on schedule. Cost performance is based on the contractor’s ability to manage cost within the authorized task order value and perform accurate and timely cost reporting.

Significant achievements for this task include: (1) process and/or procedure improvements, (2) breakthrough software technologies, and/or (3) enhanced software tools and simulation environment capabilities.

Documentation of task status will be through monthly progress reports. Monitoring and assessing contractor performance shall consist of team meetings and meetings between the NASA Task Order Manager and the contractor’s Project Lead.

Task Order 40 - Copernicus

Period of Performance 10/01/21 – 9/30/22

TASK ORDER 40

TASK ORDER TITLE: Copernicus Support - 2022

Provide Mission Design and Analysis and Tool/Simulation development support to human exploration related activities. Ref. SoW 2.3.

(1) Provide analyses of on-orbit trajectory design for NASA planned / future missions.

(2) Technical support in the production of reports and conference papers.

(3) Create, update, and maintain the Copernicus software including:

a. Development/maintenance of finite burn algorithms including long duration (low thrust) burns, as requested

b. Continue to support generic Auto Burn Plan (ABP) tool development.

c. Utilize ABP in support of Orion specific analyses

d. Add additional features to ABP such as trajectory sensitivity and stability reports

e. Initial guess generator algorithm(s)

f. Inclusion on collocation based optimization capability

g. Improvement of Indirect Optimization module in Copernicus

h. Provide updates intended to address optimization of EM-1/2/3 exo-atmospheric performance and Human Landing System (HLS) mission performance

i. Production of video training series for Copernicus version 5.x

j. Other plug-in or Copernicus feature additions to support human exploration

(4) Technical support for EG Copernicus users, as requested.

(5) Support continued development of Genesis simulation with integration of guidance algorithms and generation of tests cases for various flight phases. Support enhancement of user interface to improve ease of use

(6) Provide Copernicus technical interchange meeting support, as required by the NASA task manager.

Task Order 41

Period of Performance 10/1/21 – 9/30/22

TASK ORDER 41

TASK ORDER TITLE: Orion Support - 2022

The primary objectives of this task are to provide support to the Orion Program.

The work in this task order is performed under the contract Statement of Work paragraph 2.3 Orion Program and Exploration Initiatives.

A. GN&C Support -- NASA Task Manager Jason Arnold

(1) JSC Engineering Orbital Dynamics (JEOD) Version Migration

Provide support to the ANTARES development team for upgrades to JEOD_3.x release lines including model modification, development, integration and testing.

(2) Trick Simulation Environment Version Migration

Provide support for migrating ANTARES from Trick 17.x to Trick 19.x release lines, including integration and testing on CentOS 7.x

(3) GN&C Modeling Support

Provide support to the ANTARES development team in integration, testing, validation and verification of MPCV GN&C owned software models used for analysis and development of MPCV GN&C FSW algorithms, trajectory release products and design reviews. Support Integrated Product Board integration, testing and releases of ANTARES including modification and debugging of Matlab/Simulink models and their autocode, python scripting and Jenkins/Gitlab toolset interaction webhook through API’s.

(4) Git Configuration Management System Migration

Provide support to the ANTARES development team for maintaining the Git configuration management system including integration, testing and user support of Git and Gitlab

(5) FDIR Performance Metrics Development

Provide support to the development of FDIR performance metrics for use during software development analysis and requirements verification, including the Time to Criticality/Time to Catastrophic Failure analysis and other analysis metrics derivation.

(6) FDIR Tool Development and Analyses Execution

Provide support to the development of FDIR analysis tools, production of the subsequent data, and application of the results to the FDIR software design. This will include development of simulation requirements, modification of simulation tools, creation of analysis tools and scripts, execution of analyses, and support of resulting design changes.

Development of a time to criticality analysis capability compatible with Antares sensor and effector models, including a front end fault injection capability, post processor, and data analyzer.

(7) FDIR Architecture and Design

Provide support to the FDIR team for the formulation of the FDIR software architecture and design and assessment of implementation proposals, including requirements implementation, sensor-software integration, and software unit design.

(8) FDIR & Safety Integration

Provide support to the FDIR team for integration of design constraints and Safey products development with appropriate individuals and organizations, including other Orion Engineering disciplines, Orion Systems Engineering, Cross-Program and Orion Safety & Reliability, European Space Agency organizations, Operations, and Crew.

(9) Orion Guidance and Targeting Flight Software Support

Provide support to the Orion orbit guidance and targeting team for trade studies, algorithm formulation, implementation, testing, and documentation.

(10) Orion Controls Team Flight Software Support

Provide support to the Orion orbit controls team for trade studies, algorithm formulation, implementation, testing, and documentation.

(11) VERAS development and support

Provide support for the development and check out of the VERAS post processing tool.

Includes initial development of capabilities and support of any required changes.

(12) Transition to Flight Science Lab

Provide support for full lab transition from AGDL to FSL (Flight Sciences Lab) which includes an OS, Trick, and JEOD upgrade in Ramtares source code as well as a complete rebuild of the Jenkins CI system. This also includes support for compilation and building in singularity containers to support EM1 development and integration on older OS versions (ex. CentOS 6.10)

B. Flight Software Integration – NASA Task Manager Michael Buttacoli

(1) Review of FSW related & contractor documents

Provide technical review of FSW related documents including, but not limited to, Orion Software Requirements Specifications, Software Design Document, Software Inspection and Peer Review Reports, Software Test Plan, Software Test Procedures, Software Verification and Validation Plan/Report, and other Orion Project Documents.

(2) Insight into Lockheed Development Life Cycle

Provide NASA with insights into how the prime contractor’s execution of their flight software development process compares to (a) their documented Software Development Plan, and (b) the latest Capability Maturity Model Integrated (CMMI) standards and practices, commensurate with the prime contractor’s rated level (level 3 is the NASA minimum requirement). This can be a cumulative observation, based on supporting insight and oversight tasks, and can be reported in monthly status reports on an ongoing basis.

(3) Inline Development Support

Provide development support to the prime contractor in any ad hoc software development efforts that could lead to more robust software design or testing processes. Actively participate in any trade or optimization studies dealing with GN&C FSW related issues such as throughput, memory footprint, test rig creation, data and command handling, scheduling, etc.

(4) Sustaining Development of GN&C FSW Diagrams

Support the efforts to maintain the software design documentation and models based on the existing EM1/2 Orion GN&C requirements, while adhering to the existing LM Modeling standards. Provide training to the larger GN&C community when necessary to disseminate the prime contractors preferred diagraming standards and techniques.

(5) Interact with the GNC Engineering community

Interact with the Orion GN&C Engineers to ensure that requirements, and systems models are accurate and understandable. This entails scheduling and moderating reviews for models, as well as providing any training needed by the Engineers in order to understand the approved modeling syntax.

(6) Support weekly GN&C team meetings

Attend and participate in the weekly GN&C FSW team meetings.

(7) ER Orion weekly team meeting

Attend and participate in the weekly ER Orion weekly team meetings. Status of daily work is to be provided in support of this meeting.

(8) FSPT & SCB

Attend the weekly FSPT and SCB decisional meetings when topics of importance to GN&C FSW development tasks are put on the agenda.

(9) GN&C SPT

Attend and participate in the weekly GNC SPT meetings. Provide support when technical topics or debriefs of trade studies need to be delivered to the wider GN&C community.

(10) Support ad hoc FSW-related meetings

Attend and participate in any meetings that arise during situational periods of the Orion program. This includes major milestone meetings such as FSW PDR/CDR, as well as any technical meetings or training sessions which may occur. Status or documentation of the proceedings from these meetings should be given either verbally at the weekly team meetings or by email.

C. GN&C Navigation Hardware Support - NASA Task manager David Saley

(1) Orion Optical Navigation Support

Design, Develop, and Update the Star Tracking Code for Star tracking functionality for the Optical Navigation Team. Perform and Complete Code Coverage Testing, Algorithm updates and improvements. Complete Software and Hardware Testing as required, and provide support for integration efforts.

Support the Optical Navigation Team which includes simulation development, testing and analysis. Attend weekly meeting and the daily tagup when needed. Support team as needed for ISS DTO analysis, live sky testing, Hardware in the Loop testing, and all associated tasks to the Op nav star tracking capability.

D. Rendezvous, Docking and Proximity Operations (RPOD) Support - NASA Task manager Pete Spehar

(1) Requirements and Manual Control Mode Definitions

Provide support to the RPOD Team for generation of requirements and manual control mode definitions, including analysis and report generation

(2) Manual Control Evaluation via simulation

Support the production of a manual control simulation environment for the evaluation of piloted capability of Orion System. This work will include development of the necessary simulation architecture elements, adaptation and changes to the Orion GN&C design to support manual control modes, execution and support for pilot in the loop studies, and analysis of results.

(3) Integrated RPOD Support

Provide support to the RPOD team for ad HOC meetings, integration topics with other subsystems and vehicles including SLS/EUS, Gateway, and HLS. This may include performing analysis, creating documentation, supporting reviews, and attending other meetings as required..

(4) RPOD Simulation Development and Verification

Support the development and verification of RPOD simulation tools. This work will include but not limited to the continued development of the RPOD GNC Antares/Ramses simulation software, development of scenarios, configuration of EDGE graphics, and simulation component and system verification for both the realtime pilot-in-the-loop and batch Monte Carlo capability.

E. APS ITL/HOTH Support -- NASA Task manager Michael Buttacoli

1) Kedalion Provide GN&C support of Orion assets and testing in the Kedalion Laboratory in support of integrated testing requirements.

2) HOTH

Provide…