SOW 143 eLib.pdf

Statement of Work Task: Lunar Communication Relay and Navigation Service (LCRNS)

Task Order: 143 Task Modification: 4

I. Summary of Changes in this Task Modification

• Updated SOW to add aONS support as Subtask 3.

• Added funding for aONS support.

II. Summary of Work

This task is designed to provide Flight Dynamics support to the Navigation & Mission Design Branch (Code 595) at GSFC for the Lunar Communication Relay and Navigation Systems (LCRNS) project, including the LCRNS Position, Navigation, and Timing Instrument

(LPI).

The LCRNS project is an initiative from SCaN to deploy relays at the Moon that will provide communication and navigation services in support of the Artemis program, especially the Human Landing System missions, lunar science missions, and space technology missions.

These relays are envisioned as nodes in a larger architecture referred to as LunaNet, governed by interoperability standards and fulfilled by commercial providers, governments agencies, and international providers.

This LCRNS task is focused on defining PNT Instrument requirements, developing broader operations concepts, and assessing overall mission feasibility. Furthermore, Subtask 3 supports the development of the autonomous Navigation, Guidance, and Control Onboard Navigation System (aONS) which is a subsystem of the LPI.

The purpose of this task is to provide systems engineering and flight dynamics support to further define user needs and mission requirements for initial and future LCRNS navigation services. The contractor shall expect to work in collaboration with NASA as well as NASA’s partners in other government agencies, industry, academia, and other contractors in the accomplishment of the technical objectives of the task. As work results are evaluated or changes to mission trades occur, work priorities may change. The contractor shall be expected to provide timely support of unplanned high-priority actions as circumstances dictate to support the LCRNS mission, as negotiated with the TM.

III. Period of Performance November 1, 2023 – September 30, 2024

IV. Task Description Subtask 1: Navigation Analysis Scope: Under this subject area, the contractor shall provide navigation consultation and engineering analysis support for the LCRNS project. LCRNS is evaluating various orbits and observables in support of potential users including the Human Landing Systems (HLS), Lunar Terrain Vehicle (LTV) and science missions under the CLPS program.

Technical Requirements: This subject area will provide general navigation analysis support including but not limited to:

• Assess expected user navigation performance for different relay and user configurations, including available timing & frequency references, different observable sets, orbit or location options, and maneuvers or attitude changes.

• Assess expected lunar relay navigation performance depending on the available observables. Observables may include data from direct to Earth metric tracking (1-way uplink and 2-way), opnav (optical navigation, including limb/centroiding and terrain relative navigation or TRN), lunar surface elements, weak-signal Earth-based GNSS, accelerometers, and star trackers.

• Determine minimum set of LCRNS services and node performance needed to meet user performance requirements.

• Perform covariance and sensitivity analyses.

• Simulate environmental effects, maneuvers, and modeling error.

• Define interface requirements, possibly between LPI subsystems, between LPI and the LCRNS Service Provider (LNSP) spacecraft, and between LNSP nodes and external entities.

• Define use cases and associated operational concepts.

• Identify assumptions and risks.

• Identify and analyze initial contingency scenarios.

• Define PNT-related message content, format, and associated parameters.

• Develop a verification and validation (V&V) plan for the PNT Instrument, in collaboration with the TM.

• Develop tools for PNT Instrument V&V.

Skill Requirements:

This subtask requires technical writing skills, subject matter expertise in navigation as well as experience with GEONS 3.0 and Orbit Determination ToolBox (ODTBX) along with modeling of specific observables such as Global Navigation Satellite Systems (GNSS) and optical navigation (such as passive and active TRN). Flight project operations experience with previous weak-signal GPS missions and navigation hardware knowledge is strongly desired. Skill requirements may be negotiated with the TM.

Subtask 2: Mission Design Analysis Scope: LCRNS project is defining the desired orbits for an initial node and following nodes and their associated fuel budget and maneuver operations concept. This subtask shall provide support for the reference orbit design as well as the derived flight dynamics products, such as shadow, contact, navigation performance metrics, or evaluation of other subsystem constraints as directed by the TM.

Technical Requirements: This subject area will provide general mission design support including but not limited to:

• Define flight dynamics performance and functional requirements for LCRNS.

• Orbit optimization & metrics definition for one and multiple nodes:

o constellation contact analysis and modelling, and o constellation design and assessment tool development.

• Constellation initialization analysis, for example:

o launch vehicle insertion as a secondary payload, and o orbit transfer design & associated maneuver corrections.

• Constellation maintenance analysis, for example:

o orbit station keeping design, o momentum maintenance impacts, o delta-V budget analysis and overall maneuver ops con, and o burn modeling and initial dispersion evaluation.

• Evaluate decommissioning options.

• Provide update, maintenance, and technical support for Constellation Tool software.

Skill Requirements:

This subtask requires subject matter expertise in mission design for cislunar and lunar orbits. Overall guidance, navigation, and control (GNC) experience and overall spacecraft systems expertise are strongly desired. Experience with STK, FreeFlyer, or GMAT is preferred. Experience with EMTG is also valuable for the transfer trajectory design. Skill requirements may be negotiated with the TM.

Subtask 3: autonomous Navigation, Guidance, and Control – Onboard Navigation System (autoNGC-ONS) Scope: The scope of this subtask is to support the development of the autoNGC-ONS subsystem which is a subsystem of the LCRNS PNT Instrument (LPI).

Technical Requirements:

1. The Contractor shall complete the implementation of the GEONS 2-way DTE measurement processing including unit, functional, and system testing with simulated and real data.

2. The Contractor shall implement the improved relativity modeling in GEONS as specified in the Government-provided Algorithm Description Document or Math Specification Document and perform unit and system level testing.

3. The Contractor shall update the Finite State Machine (FSM) with autoNGC-ONS fault management in the core Flight System (cFS) environment.

4. The Contractor shall perform software integration and test activities, including making updates to the ground, cFS flight, and test software as needed.

5. The Contractor shall perform system engineering activities as directed by the Government including requirements development and management, requirements verification and validation, ensuring NPR 7150.2 Class B compliance, configuration management, risk management, and assistance with project management.

6. The Contractor shall continue to support software-in-the-loop (SIL), processor-in-the-loop (PIL), and hardware-in-the-loop (HIL) tests as needed.

7. The Contractor shall support reviews as directed by the Government.

Skill Requirements:

• Expert knowledge of GEONS

• Expert in navigation and estimation theory

• Expert in C and C++ programming

• Expert in MATLAB programming

• Expert in Python programming

• Experience with the Core Flight System

• Experience with GSFC systems engineering practices

• Expertise in navigation algorithms and measurements

• Experience conducting navigation analysis

• Experience in software systems engineering, particularly in requirements management, interface definition and software V&V

• Experience in design and development of software in C, Python, MATLAB for flight software

• Experience in software testing

• Knowledge of NPR 7150.2 requirements for flight software

• Knowledge of fault management

• Experience with the autoNGC-ONS finite state machine development

• Experience with autoNGC-ONS software integration and test documentation as required

• Customer technical support

Finite State Machine Design and Software Update

Incremental with flight software (FSW) releases as directed by the FSW Lead throughout the period of performance (PoP)

• FSM software and associated design documents

• Unit, functional, and system test artifacts

Integration and test documentation

Incremental with FSW releases as directed by the FSW Lead throughout the PoP

• Software updates as needed for successful I&T

Documentation of I&T

Updates to System Engineering Documents

Periodic based on reviews throughout the PoP

Updates to system engineering documentation such as:

• Verification and Validation Plan of autoNGC for the LCRNS use case

• Integrated System Test Procedure

Document

• FDIR Table

• Fault Management Document

• Operations Concept Document

• Software ICDs

• Requirements Table, including

Verification Matrix

• Risk Table

• Software Development Plan

• Project Management Plan

• Configuration Management Plan

• Review RFA responses, as needed

• NPR 7150.2 compliance matrix

• Review material

Table of Milestones Milestone Due Date Description

CVM-1 Service Concept Review

January 2024 Initial vendor design to be evaluated as to whether it can meet driving PNT requirements. Constellation and SISE/Navigation Tools will be used for this.

Vendor hardware interface

One month after CVM- 1 (tentatively Feb

Information exchange with vendor on potential role of PNT Instrument definition 2024) and relevant interfaces.

PNT Instrument Delta SRR

Three months after CVM-1 (tentatively April 2024)

Follow up from the SRR/SDR held in August 2023

CVM-2 Service Requirements Review

April 2024 (TBR) Vendor solution requirements review

VI. Management Approach

a. Staff Allocation, Expertise, and Skill Mix

The contractor shall staff this work item with the appropriate skill mix and staffing level for the work.

b. Configuration Management

Systems and documents will be covered under the LCRNS Configuration Management Plan.

c. Facilities

Appropriate IT devices to support the analyses, specification development, and report development are required. It shall be the contractor’s responsibility to provide and set up local workstations and network connections at the contractor’s off-site facilities as required, and to install any required tools and utilities on the contractor’s equipment.

d. Risk Management and Best Practices

The contractor shall manage schedule, cost, and technical risk through monitoring and reporting of progress and performance metrics, identifying issues well in advance of negative consequences, recommending corrective action to the TM, and implementing corrective actions with the concurrence of the TM.

VII. Performance Metrics

N/A

VIII. Travel There is no travel for this SOW.

IX. Work Location This work shall be performed primarily at the contractor’s facility, but the contractor may be required to perform some work at the Goddard Space Flight Center.

X. Reporting Requirements

The contractor shall report status in person or via teleconference to the TM or designated alternates on a monthly basis. Reports shall include informal presentation of interim results, status of development activities, and action item status. The contractor shall provide all reports at least one day in advance of the monthly meeting via email, and maintain an email distribution list with the concurrence of the TM. The contractor shall also support the TM in the preparation of status reviews for internal and external funding agencies. The contractor shall comply with any and all additional requests for status meetings and reports. The contractor shall deliver all documents in portable document format (PDF) electronic form to the GSFC NMDB online library, as directed by the TM.

XI. Security Requirements This task shall comply with IT security requirements as documented in the FDF IT security plan for all systems located in the FDF. FDF systems shall be maintained under the FDF Sustaining Engineering Task. Systems located outside of the FDF shall be covered under the Code 590 security plan and the Code 590 sustaining engineering support or the contractor sustaining engineering support depending on system location.

XII. Rights REQUIRED: The Contractor shall adhere to the RIGHTS IN DATA – special works

(FAR 52.227-17) (2007). OR

REQUIRED: The Contractor shall adhere to the RIGHTS IN DATA – general (FAR 52.227-14) Alternate II (2007 and Alternate III (2007), as modified by NFS

1852.227-14 (APR (2015).

XIII. References