Attachment A -FDSSIV_SOW.pdf

DRAFT - ATTACHMENT A

FLIGHT DYNAMICS SUPPORT SERVICES (FDSS) IV

STATEMENT OF WORK (SOW)

1 General Information The Navigation and Mission Design Branch (NMDB) and the Attitude Control Systems Engineering Branch (ACSEB) within the Mission Engineering and Systems Analysis (MESA) Division at Goddard Space Flight Center (GSFC) are responsible for providing analytic and operational expertise for orbit and attitude systems, dynamics modeling, control analyses, and estimation and simulation of space vehicles. The branches create and maintain state-of-the-art analysis tools for mission design, trajectory optimization, orbit analysis, navigation, attitude determination, and controls analysis. The NMDB also provides the expertise to support a wide range of flight dynamics services, such as spacecraft mission design, on-orbit sensor calibration, launch support, and orbit operations (ground and flight). An active technology development program is maintained, with special emphasis on developing new techniques and algorithms for autonomous orbit/attitude systems and advanced approaches for trajectory design.

Specific areas of expertise resident in the branches include but are not limited to:

• Trajectory analysis and control design

• Flight dynamics operations

• Mission design

• Orbit estimation techniques

• Constellation analysis

• Flight dynamics model development

• Flight dynamics ground and flight system development

• Ground attitude determination

• Spacecraft conjunction assessment (CA) and risk analysis

The NMDB provides support for missions from early conception through operations to disposal.

Being customer focused, the branch receives primary direction for these efforts from the science Lines of Business (LOBs), center initiatives, and Agency priorities. From these high-level directives, branch personnel derive flight dynamics requirements through a structured systems engineering process, which interacts with analysis, operations, and software tool development efforts to ensure the requirements are achievable, verifiable, and valid for the mission concept.

Operations and software tool development drive infrastructure needs, and the lessons learned from these activities shape the branch’s strategic direction. The interaction between these activities is shown in the figure that follows, and this Statement of Work (SOW) is structured along these lines.

A more detailed list of the services that NMDB provides to its customer base include but are not limited to flight dynamics planning, designing, implementation, enhancement, evaluation, integration, and testing. The flight dynamics disciplines include spacecraft navigation (orbit determination), surface navigation, trajectory control, mission design, attitude determination, attitude dynamics and attitude control.

Unique mission support and network services are also provided. Flight dynamics mission support efforts involve the determination of mission flight dynamics requirements and the planning necessary to satisfy the mission/project needs.

Technology development is performed in the areas of navigation, trajectory design and flight dynamics automation. Flight regimes supported include single satellite and satellite formations in low-Earth, high-Earth, gravity assist, libration point, lunar/cis-lunar, non-Earth planetary and interplanetary orbit including small bodies (asteroids, comets, and planetary moons). Operational facility modernization planning, development, implementation and sustaining services are also provided.

This Statement of Work (SOW) defines the activities required to provide these flight dynamics services to our customers.

2 Contract Requirements

2.1 Section 508 of the Rehabilitation Act

The contractor shall ensure that all products, platforms, services, and communications delivered as part of this work statement that are Information and Communication Technology (ICT) or contain ICT, must conform to the Revised Section 508 of the Rehabilitation Act Standards, 36

C.F.R. § 1194.1 & Apps. A, C & D. The Standards may be found at Revised 508 Standards and 255 Guidelines (access-board.gov).

The Applicable 508 Chapters for this acquisition are as follows:

Chapter 1: Application and Administration Chapter 2: Scoping Chapter 3: Functional Performance Criteria Chapter 4: Hardware Chapter 5: Software Chapter 6: Support Documentation and Services Chapter 7: Referenced Standards - WCAG 2.0.

2.2 Software Engineering Requirements

A significant fraction of the work in this SOW is related to software services including software modification, development, and maintenance activities and is subject to compliance with NASA Procedural Requirements, NASA Software Engineering Requirements, NPR 7150.2D.

Adherence to the most recent version of the NPR should prevail in individual task orders, as needed. The latest version of the NPR can be found in the NASA Online Directives Information System (NODIS) at https://nodis3.gsfc.nasa.gov/main lib.cfm.

The contractor shall develop the following software plans (stand-alone or condensed into one or more documents) that meet the required content described in Section 2.4.4, Flight Dynamics Software. The contractor shall provide these software plans as required/requested via task ordered issued under this contract. After NASA approval, the software plans will become contractually binding for all software activities in the Work Breakdown Structure tasks of this

SOW:

o Software Development or Management Plan o Software Configuration Management Plan o Software Assurance Plan in compliance with NASA Software Assurance and Software Safety Standard NASA-STD-8739.8A Adherence to later revisions of this document will be called out in the individual task orders, as needed.

2.3 Flow down from other NASA Documents

The work outlined in this SOW have flow down requirements from specific NASA regulations and standards documents including:

• NASA Software Engineering Requirements, NPR 7150.2D

• NASA Software Assurance and Software Safety Standard, NASA-STD-8739.8A

• NASA Collision Avoidance for Space Environment Protection Requirements, NPR

8079.1

• NASA Procedural Requirements for Limiting Orbital Debris and Evaluating the

Meteoroid and Orbital Debris Environments, NPR 8715.6B

Adherence to the most recent version of these NPRs and standards should prevail in individual task orders, as needed. The latest version of the NPR can be found in the NASA Online Directives Information System (NODIS) at https://nodis3.gsfc.nasa.gov/main_lib.cfm.

2.4 FDSS Work Breakdown Structure

2.4.1 Flight Dynamics Systems Engineering

As described in Section 1 General Information, NMDB supports missions spanning the four science LOBs including Astrophysics, Heliophysics, Earth Science, and Planetary Science.

These missions, alongside other agency and center priorities, embody a wide customer base that requires flight dynamics services as early as the mission proposal and formulation pre-Phase A/Phase A through Phase E operations and Phase F disposal. A systems engineering process is imperative to ensure flight dynamics requirements are developed and implemented to inform analysis, operations, software, and infrastructure to meet mission specific science goals. The contractor shall provide flight dynamics systems engineering support through the development, traceability, and verification of flight dynamics requirements as needed/requested via task orders.

2.4.1.1 Flight Project Support

The contractor shall provide flight dynamics systems engineering services to flight projects from pre-phase A through Phase F as needed/requested via task order. This support may encompass any of the following areas.

2.4.1.1.1 Mission Concepts and Mission Design

Missions require flight dynamics support from their initial conception by ensuring data sufficiency requirements are met. Data sufficiency is the process by which mission designers place the spacecraft in an optimal position with necessary fields-of-view for observing science targets. The contractor shall provide flight dynamics trajectory planning and mission design requirements development as well as consultation with Task Monitors (TMs) and Mission Systems Engineers (MSEs) on data sufficiency and how science requirements influence mission design. The contractor shall provide evaluation and assessment of various technical aspects of the mission or mission concept pertaining to development of mission requirements and implementation concepts including operations concepts.

2.4.1.1.2 Mission Operations and Flight Support

2.4.1.1.2.1 Onboard System Specification

The contractor shall develop onboard system requirements specification in the development, integration, and testing of onboard navigation, guidance, and control flight software. This support includes developing traceable requirements for applicable measurement types, simulations, and core Flight Software (cFS) interfaces.

2.4.1.1.2.2 Ground System Development

The contractor shall develop ground flight dynamics system requirements to inform the design, development, integration, and testing of Flight Dynamics Ground Systems (FDGS) for project mission control centers. The contractor shall support the implementation of these requirements into an FDGS which may include commercial-off-the-shelf (COTS), government-off-the-shelf

(GOTS), automation tools, and glueware. The FDGS may include orbit determination, flight dynamics product generation, flight dynamics scheduling, maneuver planning, reconstruction, & calibration, and flight dynamics trending. In addition, the contractor shall support the enhancement and processing improvement within the FDGS to include support for requirements definition, system design and development, and integration and testing for operations.

2.4.1.1.3 Interfaces

2.4.1.1.3.1 Flight Project Subsystems

The contractor shall support the interaction and overall interface requirements development with other subsystems that include but are not limited to Launch Vehicle providers, attitude determination and control personnel, propulsion personnel, thermal personnel, communications personnel, instrument systems personnel, and Guidance Navigation and Control (GN&C) hardware personnel.

2.4.1.1.3.2 Network Communications

The contractor shall provide systems engineering support in identifying and verifying tracking network communications requirements and tracking network readiness for flight project mission support. This support may include but is not limited to interfacing with the Near Space Network (NSN) and Deep Space Network (DSN) to ensure appropriate integration of the networks with mission spacecraft and launch vehicles.

2.4.1.1.3.3 Crewed Mission Network Communications

The contractor shall provide services for management of mission specific network requirements, assessments of network readiness for mission support and the technical integration of the Near Space Network (NSN) with mission spacecraft and launch vehicles.

2.4.1.2 Conjunction Assessment Risk Analysis (CARA) Systems Engineering The contractor shall provide support for Conjunction Assessment Risk Analysis (CARA) services for all NASA uncrewed spacecraft. The NASA CARA Program assesses the risk of collision between space assets to ensure adherence to NPR 8079.1. CARA maintains a close relationship with the Department of Defense, and support is provided to the military as needed.

CARA provides subject matter expertise to NASA for Conjunction Assessment (CA) and Space Situational Awareness (SSA)-related topics. This element requires the contractor to hold a Top Secret clearance for work performed in government-owned classified facilities.

The contractor shall provide systems engineering support to CARA to ensure requirements are identified, documented, and implemented based upon mission needs and internal NASA NPR

8079.1 and NPR 8715.6B regulations. The contractor shall support the development of accurate and complete requirements specification for real-time processes, algorithm development, software releases, acceptance test planning, and software review briefings. In addition, the contractor shall support the CARA Program in performing requirements analysis for new capabilities and customers.

2.4.2 Flight Dynamics Operations

The contractor shall provide analytic and operational support for spacecraft orbit determination;

trajectory control; mission planning product generation; acquisition data generation and transmission; and tracking data evaluation, calibration, and testing. The contractor shall support trajectory determination, monitoring, and network support operations for crewed flight and launch vehicles (LV). The responsibilities include a combination of analytical tasks, critical operations support including launch and early orbit checkout, and routine production activities.

The contractor shall provide the Government with insight into all operational support, product development, test, and maintenance activities. The contractor shall provide the Government with electronic access to documentation generated for or related to flight dynamics operations (e.g., plans, procedures, reports, design documentation, software code, problem reporting data, requirements, and requirements documentation and traceability, test plans, test data, analysis, schedules). The contractor shall conduct all software maintenance and development activities in compliance with NPR 7150.2D. The contractor shall provide quality assurance for all operational products in compliance with NASA-STD-8739.8A.

The contractor shall provide planning support and recommendations for orbit maneuver operations for all orbit regimes and for all types of propulsion including but not limited to low-thrust and chemical propulsion. Maneuver planning, reconstruction, & calibration support is further detailed in Sections 2.4.2.1.5 and 2.4.2.2.3.

The contractor shall provide orbit determination support for all mission types and mission phases including but not limited to Low Earth Orbit (LEO), Medium Earth Orbit (MEO), Geostationary Equatorial Orbit (GEO), Highly Elliptical Orbit (HEO), Libration Orbits, interplanetary, small bodies, and multi-spacecraft Rendezvous, Proximity Operations, and Docking (RPOD). The contractor shall perform orbit determination using a variety of methods and measurement types including but not limited to batch filter, Kalman filter, smoother, Delta-Differential One-way Ranging (DDOR), Differenced One-Way Doppler (DOWD), and Global Positioning System (GPS). The contractor shall perform force model estimation, calibration, and trending, including spacecraft non-gravitational forces (e.g., Solar Radiation Pressure (SRP), thermal re-radiation, momentum desaturations, maneuvers), target body geophysical parameters (e.g., Gravity Model (GM), gravity field, spin state, albedo, etc.), and other environmental parameters (e.g., drag, media delays, etc.). In addition, the contractor shall perform sensor calibration and trending (e.g., antennas, cameras, Light Detection and Ranging (LiDARs)). Orbit determination and analysis support is further detailed in Sections 2.4.2.1.7 and 2.4.2.2.5.

2.4.2.1 Flight Dynamics Facility

Operations support includes but is not limited to support provided within the Flight Dynamics Facility (FDF). The FDF currently provides flight dynamics support for more than 30 spacecraft. Operational support includes orbit determination, acquisition data generation for the space and ground networks, tracking data evaluation and tracking system performance evaluation, maneuver planning and calibration support. The FDF also supports Launch Vehicle (LV) operations and Human Spaceflight analysis and operations to include the International Space Station (ISS) and related cargo and crewed missions, Artemis Program, Gateway

Program, Human Landing System (HLS), as well as other commercial ventures such as SpaceX Starship, Polaris Program, and more.

2.4.2.1.1 Acquisition Data

The contractor shall provide support for the generation of acquisition data (i.e., data needed for a ground- or space-based asset to acquire a signal from a spacecraft) based on mission requirements, which may include launch and ascent, on-orbit, post-maneuver, re-entry, and landing/splashdown. Contract personnel may be required to have US government security clearances.

2.4.2.1.1.1 The contractor shall provide the generation and transmission of pre-mission and real-time support acquisition data, including on-orbit data for various networks.

2.4.2.1.1.2 The contractor shall provide the generation of network pre-mission and real-time network scheduling support data.

2.4.2.1.1.3 The contractor shall provide data quality verification on all acquisition data products generated.

2.4.2.1.2 Anomaly Support and Contingency Analysis

The contractor shall provide contingency analysis and anomaly resolution support including appropriate documentation for mission contingency scenarios and anomalies that occur during operations.

2.4.2.1.3 Human Space Flight

The contractor shall provide support of human spaceflight activities. This support includes pre-launch generation and transmission of acquisition data, processing of launch trajectory data, tracking data evaluation, and post-launch generation and transmission of acquisition data.

Contract personnel may be required to have US government security clearances.

2.4.2.1.3.1 The contractor shall provide ongoing support for the International Space Station (ISS). This support includes generation and transmission of acquisition data and routine orbit determination.

2.4.2.1.3.2 The contractor shall provide analysis and operations support for vehicles visiting the ISS. This support includes generation and transmission of acquisition data and routine orbit determination, as well as support for proximity operations.

2.4.2.1.3.3 The contractor shall provide analysis and operations planning support for future human spaceflight mission programs including but not limited to the Artemis Program, Gateway Program, Human Landing System, and future Commercial Ventures.

2.4.2.1.4 Launch Vehicle Support

The contractor shall provide support for launch vehicle missions. This support includes generation and transmission of pre-launch acquisition data, processing of launch trajectory data, and generation and transmission of post-launch acquisition data updates. Contract personnel may be required to have US government security clearances.

2.4.2.1.5 Maneuver Planning, Reconstruction, & Calibration

The contractor shall provide operational support to include orbit adjust computations for flight projects during pre-launch and in-flight phases, operational support for ongoing projects involving orbit adjust maneuvers, maneuver reconstruction, calibration, trending, and performing studies to determine the optimum mission profile that satisfies mission objectives considering all spacecraft or other constraints (e.g. ground station visibility and spacecraft performance capabilities, health and safety), expected dispersions, providing in-flight adaptive mission analysis studies, and providing maneuver planning and execution support as requested for collision avoidance maneuvers for in-flight missions.

2.4.2.1.6 Mission Planning and Scheduling Products

The contractor shall provide for the support, generation, and quality assurance of mission planning data products, scheduling products, and related spacecraft products based on individual flight project mission requirements.

2.4.2.1.7 Orbit Determination and Analysis

The contractor shall provide orbit determination support during launch and early orbit periods and as a routine operation to maintain current orbit definitions. This support includes pre-launch error analysis, pre-launch testing, mission support planning and ground and onboard orbit determination and ephemeris generation. Contract personnel may be required to have US government security clearances.

2.4.2.1.7.1 The contractor shall perform orbit determination and related computation activities in support of scientific and applications spacecraft missions. These activities include routine and periodic special orbit determination support and analysis for selected spacecraft. The routine work is done on a regularly scheduled basis. The special support is done on a scheduled and emergency basis depending on the particular spacecraft.

2.4.2.1.7.2 The contractor shall perform analysis related to spacecraft local oscillator frequency. This analysis includes determining local oscillator frequency history and reporting results to users.

2.4.2.1.7.3 The contractor shall support onboard orbit computations as required. This support may include independent verification of onboard navigation solutions and preparing orbit products for uplink to the spacecraft.

2.4.2.1.7.4 The contractor shall perform critical orbit determination computations for payloads during early operations periods and computations after orbit adjust maneuvers, as required.

2.4.2.1.7.5 The contractor shall perform error analysis for upcoming missions and produce formal and predicted uncertainties as needed for operations and science planning. This analysis includes but is not limited to determining amount of tracking data needed, duration of passes, and number of tracking stations needed to satisfy the mission orbit determination and accuracy requirements.

2.4.2.1.8 Tracking Data Evaluation and Calibration

The contractor shall provide support for validation of radiometric tracking data and tracker calibration assistance, and certification of new tracking systems. Contract personnel may be required to have US government security clearances.

2.4.2.1.8.1 The contractor shall provide data validation and calibration support of tracking systems to maintain accurate tracker and network performance values. The contractor shall assess the accuracy and usability of the data for the orbit determination process. The contractor shall conduct noise analysis of the radiometric observations and identify erroneous observations. The contractor shall provide information to the appropriate network concerning a deviation in tracker performance from the predetermined norm.

2.4.2.1.8.2 The contractor shall provide calibration support for modified and/or new tracking systems. This support shall include validation of tracking data and verification/certification of tracking system capability. The contractor shall perform analyses to verify data receipt and correct format for new and/or modified tracking systems.

2.4.2.2 Mission Operations Centers (MOCs)

2.4.2.2.1 Acquisition Data

The contractor shall provide acquisition data as described in Section 2.4.2.1.1 and its subsections

2.4.2.1.1.1 through 2.4.2.1.1.3 in support of MOCs outside the FDF.

2.4.2.2.2 Anomaly Support and Contingency Planning

The contractor shall provide contingency planning and anomaly support as described in Section

2.4.2.1.2 to MOCs outside the FDF.

2.4.2.2.3 Maneuver Planning, Reconstruction, and Calibration

The contractor shall provide maneuver planning, reconstruction, and calibration as described in Section 2.4.2.1.5 for MOCs outside the FDF.

2.4.2.2.4 Mission Planning and Scheduling Products

The contractor shall provide mission planning and scheduling support as described in Section

2.4.2.1.6 to MOCs outside the FDF.

2.4.2.2.5 Orbit Determination and Analysis

The contractor shall provide orbit determination and analysis support as described in Section

2.4.2.1.7 and its subsections 2.4.2.1.7.1 through 2.4.2.1.7.5 for MOCs outside the FDF.

2.4.2.3 CARA Operations

CARA support includes providing real-time operations to perform risk analysis of daily screening results to determine threats posed to mission customers, ascent/deorbit/ disposal/special maneuver operations; assisting missions in planning risk mitigation options; and providing pre-launch analysis of predicted collision threats to mission customers. The contractor shall also support the onboarding of new missions in setting up a CA process and procedure for interfacing in providing real-time CA support. Contract personnel may be required to have US government security clearances.

2.4.3 Flight Dynamics Analysis

The contractor shall provide flight dynamics analysis services to flight projects from pre-Phase A (formulation) through Phase E (operations) and Phase F (disposal). The contractor shall also provide research and technology development services as needed/requested via task order. The contractor shall provide maintenance and development of flight dynamics software use for analysis that is consistent with the requirements laid out in Section 2.4.4. Flight dynamics analysis tasks may include topics such as orbit determination, trajectory control, mission design, trajectory optimization, Monte Carlo analysis, covariance analysis, and measurement models.

The contractor shall provide the Government with insight into all flight dynamics analysis, product development, and test and maintenance activities. The contractor shall provide the Government with electronic access to documentation generated for or related to flight dynamics analysis (e.g., plans, procedures, reports, design documentation, software code, problem reporting data, requirements, and requirements documentation and traceability, test plans, test data, analysis, schedules, etc.). The contractor shall conduct all software maintenance and development activities in compliance with NPR 7150.2D. The contractor shall provide quality assurance for all operational and analysis products.

2.4.3.1 Attitude Determination Analysis

The contractor shall provide ground or onboard attitude determination analysis and consultation to flight projects. The contractor shall provide ground or onboard attitude system development.

The ground or onboard attitude system development may be a combination of the multi-mission ground Attitude Determination System (ADS) and mission specific code or onboard flight software.

2.4.3.2 Maneuver Modeling, Planning, Reconstruction, & Calibration The contractor shall provide pre-mission planning and consultation concerning deterministic, statistical, and contingency orbit maneuvers that accomplish selected mission objectives for flight projects. This support shall include orbit adjust computations for flight projects that take into account propulsion system modeling (chemical and electric) and mission constraints, analysis to determine how to reconstruct and calibrate executed maneuvers, and the performance studies to determine the optimum maneuver scenarios that satisfy mission objectives considering all spacecraft or other constraints. This support includes but is not limited to the development of an overall mission Delta-V budget with appropriate margins.

2.4.3.3 Navigation Analysis

The contractor shall provide analysis and consultation for planning onboard and/or ground-based orbit determination support of flight projects. This support includes, but is not limited to requirements analysis, covariance analysis, feasibility studies and consultation on network support, tracking infrastructure, measurement models, measurement accuracies, support scenarios, inputs into sensor hardware requirements, and concept of operations development.

2.4.3.4 Product Generation and Scheduling

The contractor shall provide consultation on the generation of products that support science data collection and analysis and flight operations. Analyses include determining: the time step for an ephemeris (variable or fixed), acceptable interpolation error for science data collection planning and scheduling, accuracy needed for science data processing, accuracy for generating acquisition data, and accuracy for maneuver planning and scheduling.

2.4.3.5 Trajectory Design, Optimization, and Control

The contractor shall provide flight dynamics trajectory planning and mission design consultation for flight projects. This support includes but is not limited to 1. Pre-launch planning for nominal, contingency, and end of life; 2. Pre-launch planning in the areas of trajectory design, launch window analysis and trajectory optimization analysis; 3. Deterministic, statistical, and contingency maneuver planning; 4. Launch support planning and testing in all areas as required;

and 5. Pre-mission end-of-life trajectory planning.

2.4.3.6 CARA Analysis

CARA support includes offline analysis and in-depth research to develop algorithms and procedures for improving the CARA operations process, Associated software development and maintenance, especially using Python and MATLAB, may be required. Contract personnel may be required to have US government security clearances.

2.4.4 Flight Dynamics Software

The contractor shall provide software systems development required for flight dynamics support.

Software Development activities are informed by requirements developed during the project systems engineering process and include capturing the way the software is configured and the processes utilized from software formulation to release and customer usage. Also included are the development of scripts, ‘glueware’, and other interface software that may be required to utilize Commercial-off-the shelf (COTS) or Government-off-the shelf (GOTS) software in GSFC flight dynamics computations. Both onboard and ground software development may be required.

The contractor shall provide the following plans in Section 2.4.4.1.1, and Sections 2.4.4.2.1 through 2.4.4.2.3, and develop software in accordance with NASA Software Engineering Requirements, NPR 7150.2D.

2.4.4.1 Configuration Management

The contractor shall configuration manage the flight dynamics software and documentation. The contractor shall provide documentation regarding the software configurations of the FDF, MOCs, and other flight dynamic operations systems (e.g. Constellation Coordination System) including diagrams of the systems, their interconnections, and details of all of the hardware comprising the system.

2.4.4.1.1 Configuration Management Plan

The Configuration Management Plan identifies the items associated with a software development project life cycle, captures the way these items evolve over time, and provides a means for stakeholders to ensure the items are stored, managed, and documented correctly. The Configuration Management Plan can be a part of the Software Management or Software Development Plan. This plan identifies the required coordination of software configuration management activities with other activities of the project.

The Software Configuration Management Plan shall contain:

a. References to the software configuration management policies and directives that apply to the project.

b. All functions and tasks required to manage the configuration of the software and its products, including configuration identification, configuration control, status accounting, and configuration audits and reviews.

c. Schedule information, which establishes the sequence and coordination for the identified activities and for all events affecting the plan's implementation.

d. Resource information, which identifies the software tools, techniques, and hardware necessary for the implementation of the plan’s activities.

e. Plan maintenance information, which identifies the activities necessary to ensure continued adherence to the plan during the life cycle of the project.

f. Release management and delivery.

2.4.4.1.2 Backup, Restoration Testing, and Archiving

The contractor shall provide support for periodic backup, confirmation that backups can be restored, and archiving of designated systems and data that is used for flight dynamics operations, analysis, and support.

2.4.4.2 Development Process

The contractor shall provide the processes utilized to design, implement, test, and release of both institutional (multi-mission) and mission unique software across the software life cycle. Each software development project contains unique ways of ensuring quality software with the necessary plans and activities that encompass those processes captured in the following sections.

2.4.4.2.1 Development and Management Plan

The Software Development or Management Plan provides insight into, and a tool for monitoring, the processes to be followed for software development, the methods to be used, and the approach to be followed for each activity. The Software Management Plan will be supplemented with project schedules, organization, and resources for each subsequent task order requiring software development or maintenance activities.

The Software Management Plan shall contain:

a. Project organizational structure showing authority and responsibility of each organizational unit, including external organizations.

b. The safety criticality and classification of each of the systems and subsystems containing software.

c. Tailoring compliance matrix for approval by the designated Engineering Technical Authority, if the project has any waivers or deviations from NPR 7150.2D.

d. Engineering environment (for development, operation, or maintenance, as applicable), including test environment, library, equipment, facilities, standards, procedures, and tools.

e. Work breakdown structure of the life cycle processes and activities, including the software products, software services, non-deliverable items to be performed, budgets, staffing, acquisition approach, physical resources, software size, arid schedules associated with the tasks.

Note: Item e. above is not required for initial submittal. The contractor shall deliver supplemental updates addressing the above information for specific contract Task Orders as required.

f. Management of the quality characteristics of the software products or services.

g. Management of safety, security, privacy, and other critical requirements of the software products or services.

h. Verification and Validation (V&V), which includes the identification of the V&V method used across the life cycle, products subject to V&V, and V&V environments.

i. User, acquirer, and subcontractor involvement/management.

j. Risk management.

k. Approval required by such means as regulations, required certifications, proprietary, usage, ownership, warranty, and licensing rights.

l. Process for scheduling, tracking, and reporting.

m. Training of personnel, including project unique software training needs.

n. Software life cycle model, including description of software integration and hardware/software integration processes, software delivery, and maintenance.

o. Configuration management. See Section 2.4.4.1.1.

p. Software peer review/inspection process of software work products.

q. Process for early identification of testing requirements that drive software design decisions (e.g., special system level timing requirements/checkpoint restart).

r. Software metrics.

s. Content of software documentation to be developed on the project and the relationships amongst the documents.

t. Management, development, and testing approach for handling any commercial-off-the¬ shelf (COTS), government-off-the-shelf (GOTS), modified-off-the-shelf (MOTS), reused, or open-source software that are included within a NASA system or subsystem.

2.4.4.2.2 Maintenance Plan

The contractor shall provide a plan to maintain flight dynamics software released to the customer and used for technology, analysis, and mission support. This plan includes the modification of in-house software and updating to new versions of off-the-shelf software to account for bug fixes, new customer requirements, adjustments due to new computing platforms, and other adjustments from deployment to the customer location. Flight dynamics tools consist of a combination of in-house developed systems, commercially available products, and extensions to commercially available products developed and/or procured in support of flight dynamics engineers.

2.4.4.2.3 Assurance Plan

The contractor shall provide a plan to assure the software is at a level of confidence that is free from vulnerabilities, either intentionally designed into the software or accidentally inserted at any time during its life cycle, that the software functions in an intended manner, and that the software does not function in an unintended manner. The Software Assurance Plan documents the developers' compliance with NASA-STD-8739.8A.

2.4.4.2.4 Design

2.4.4.2.4.1 Design Methodology

The contractor shall provide a design methodology for software development in support of flight dynamics analysis, technology development, and mission support. These methodologies could include but are not limited to agile, spiral, waterfall, etc. The contractor shall include rationale for choosing a specific approach, provide guidelines for the software decision-making process to meet mission requirements and obtain concurrence on the selection of the methodology from the customer.

2.4.4.2.4.2 Commercial off the Shelf (COTS) and Government off the Shelf (GOTS) Evaluation The contractor shall provide evaluation of COTS and GOTS flight dynamics software for use in mission analysis and operations. This support includes development of evaluation criteria, evaluation and reporting of results, and integration of COTS software for analysis and operations.

2.4.4.2.5 Documentation

The contractor shall maintain and deliver software development documentation to include the requirements as listed in the Software Configuration Management (Section 2.4.4.1.1), Development and Management (Section 2.4.4.2.1), Maintenance (2.4.4.2.2), and Assurance plans (2.4.4.2.3).

2.4.4.2.6 Implementation

The contractor shall provide the coding and integration of flight dynamics software into the mission workflow. This support includes but is not limited to development, installation, training, monitoring, and maintenance.

2.4.4.2.7 Testing

The contractor shall provide the testing of flight dynamics software through evaluation, validation, and verification to ensure successful implementation. The contractor shall produce software test plans, follow test procedures, and provide test reports for flight dynamics software releases. The contractor shall also conduct regression testing as need to ensure defects have not been introduced into previously integrated or tested intermediate builds or software releases.

2.4.4.2.8 Software Release

The contractor shall follow NASA GSFC’s Software Release process for all flight dynamics software developed in support of missions, which includes the submission of New Technology Reports (NTRs) through http://invention.nasa.gov/ as needed.

2.4.4.3 Specific Considerations

2.4.4.3.1 Flight Software

The contractor shall support the development, integration, and testing of flight software to support missions. Efforts include working with flight software developers to adapt ground-based algorithms for flight taking into account considerations such as word size and floating-point representations, performance and memory management, and development of codecs for navigation hardware.

2.4.4.3.1.1 Hardware Procurement

The contractor shall support the hardware-in-the-loop testing required to verify flight software appropriately runs on compute boards in support of onboard navigation. In addition to laboratory experiments, this support may include the procurement of testing instruments (e.g., oscilloscopes and logic analyzers), proof-of-concept testing machines (e.g., Raspberry Pi, Beagle Bone, Ardunio). and miscellaneous ground support equipment needed to test, verify, and debug compute boards.

2.4.4.3.2 CARA Software

In support of Conjunction Assessment, the contractor shall perform ground systems architecture and software development functions that are covered by the CARA Software Acquisition Management Plan (SAMP). Associated software development and maintenance, especially using C#, Python and MATLAB, expertise in Cloud architecture and maintenance using Amazon Web Services (AWS), especially using MATLAB, may be required. The contractor shall also support the onboarding of new missions in setting up the associated interfaces including reviewing requirements and modifying software and databases to handle new missions. Software support also includes software deployments to the Conjunction Assessment System (CAS).

2.4.5 Infrastructure

The contractor shall support the software and hardware maintenance and engineering in support of the FDF, CARA, and the Flight Dynamics Ground Systems collocated with Mission Operations Control Center (MOCC) environments. This support includes but is not limited to integration into operations of software and hardware systems, software and hardware maintenance, facility maintenance, and user support.

2.4.5.1 FDF Facilities and Maintenance

The FDF is a multi-mission operations facility that is located on the second floor, north wing in Building 28 at GSFC, and an annex area in Building 13 for the Near Space Operations Control Center (NSOCC). The FDF consists of mission operations areas and computer rooms at both primary and alternate processing facilities (APF). The general operations area covers approximately 1,320 square feet, the mission operations area covers approximately 2,660 square feet, and the computer room covers approximately 3,360 square feet. Office space to house support personnel is provided adjacent to the FDF and is considered part of the facility.

Additionally, there are two conference rooms that are part of the FDF area. The FDF has approximately 100 computers that are used for operations support in a virtualized environment. These computers consist of server class machines that provide data storage and processing, external communications, and mission support and workstation class machines that are used for critical and mission support. These machines use Windows, UNIX and LINUX operating systems.

2.4.5.1.1 Facility Engineering Support

The contractor shall support operations systems monitoring for the FDF computing systems. This support includes, but is not limited to, coordination of facility operations schedule, coordination of facility maintenance schedule, provide data monitoring for incoming data to the facility, monitoring the FDF HVAC systems, and coordinating maintenance with GSFC facility maintenance organizations.

2.4.5.2 Systems Facilities Sustaining Engineering

The contractor shall provide system sustaining engineering support for computing facilities, equipment and network, and engineering support for system design.

2.4.5.2.1 Model Maintenance

The contractor shall provide the maintenance of various databases and customer interfaces used to perform flight dynamics functions and products.

2.4.5.2.1.1 Customer Interface Maintenance

The contractor shall maintain the customer interfaces used for the delivery of flight dynamics information and products.

2.4.5.2.1.2 Attitude and Orbit Models and Database Maintenance The contractor shall provide analysis and enhancement support needed to update and disseminate attitude and orbit models, and databases. Typical activities may include, but are not limited to, the creation and maintenance of comprehensive and custom star catalogs; maintenance and update of solar flux data; geopotential data; timing coefficients data; tracking data; ground station locations and horizon masking; assignment of station IDs; and the development of analysis specifications for, and enhancements to, attitude and orbit modeling software.

2.4.5.2.1.3 Database Support

The contractor shall provide maintenance and enhancement support for operational databases.

2.4.5.3 Ground Systems Infrastructure Development

The contractor shall provide the IT systems support for the computer systems used for the flight dynamics ground system in the FDF. This support includes the configuration of new specialized hardware arid software systems, system monitoring, and troubleshooting.

The contractor shall support the maintenance and upgrades of specialized hardware and software systems used for the flight dynamics ground systems in the FDF. This support includes coordinating and procuring hardware or part replacement, installing new hardware and troubleshooting hardware problems, maintaining a list of hardware support contracts, maintaining an inventory of operational hardware and equipment, procuring and installing specialized flight dynamics application software, and developing custom flight dynamics software applications. This support also includes the identification and requirements analysis for hardware and software upgrades and providing appropriate logistics services.

2.4.5.4 CARA Infrastructure

In support of CARA operations, the contractor shall provide Operations Ground System maintenance and develop new operational capabilities to meet changing demands of the CA Space environment.

2.4.6 Strategic Initiatives

The contractor shall provide strategic support associated with the development of new algorithms, techniques, operations concepts, and methodologies to improve capabilities, reliability, compliance, and cost for flight dynamics services. In addition, the contractor shall provide research into new mission types through the development of new or improved orbits, control techniques, optimization strategies, and onboard orbit/attitude computations. The technologies, models, and techniques developed provide immediate results for mission support, thus enhancing center participation in proposals while expanding capabilities in GSFC strategic thrust areas such as commercialization and Distributed Systems Missions (DSM). The contractor shall tailor its support to these efforts as needed.

2.4.6.1 Commercialization

The Contractor shall provide support for preparing existing software product lines (e.g., GPS Enhanced Onboard Navigation System (GEONS), autonomous Navigation, Guidance, and Control (autoNGC)) for commercialization, by improving code readability, modularity, and by preparing supporting documentation.

2.4.6.2 Automation and Autonomy Techniques

The contractor shall provide research into advance automation and autonomy techniques.

Analyses includes the use of classic (e.g., computational decision making) and modern algorithms (artificial intelligence and machine learning), for onboard and ground systems, that provide more intelligent monitoring, decision-making, and response. The available use cases include onboard data classification, prioritization, and processing; fleetwide replanning of a distributed systems; fault anticipation, detection, and mitigation; and intelligent ground system processing and product generation.

2.4.6.3 Alternative/Enterprise Flight Dynamics Ground System Infrastructures The contractor shall provide research into alternative flight dynamics ground systems infrastructures to determine opportunities for flight dynamics ground system architecture improvements to effectively achieve operational and science objectives. These alternatives include moving to cloud-based architectures, parallel processing, and similar advanced computing strategies.

2.4.6.4 Advanced Flight Dynamics Techniques

2.4.6.4.1 Attitude

The contractor shall provide investigation of improvements in the methods by which spacecraft attitude sensor/actuator measurements and reference data are efficiently processed to determine attitudes. With a view to improve mission support and as needed/requested via task order, the contractor shall develop new algorithms in the areas of attitude determination, attitude dynamics, attitude modeling, and calibration of attitude actuators and attitude sensors (e.g., gyros and magnetometers). The contractor shall provide services associated with the development of attitude determination, calibration and control software, attitude-analysis software, including, but not limited to attitude dynamics simulators and error analysis tools.

2.4.6.4.2 Mission Design

The contractor shall provide research and analysis into new approaches to designing trajectories for differing problems including but not limited to low-thrust spiral trajectories, 3-body space, or chaotic systems and for differing mission types including but not limited to distributed systems, landers, and probes (e.g., atmospheric modeling).

2.4.6.4.2.1 Distributed Systems

The contractor shall provide research, as needed/requested via task order, for the design, control and management of multiple spacecraft flying in formation or as part of a constellation. Required services may include the development of control algorithms for flight or ground use, the development of constellation maintenance approaches, collision avoidance and formation flying strategies, and support to formation flying and constellation management test beds.

2.4.6.4.3 Navigation

The contractor shall provide support for research, analysis, and related engineering services to support advanced navigation technology initiatives. The contractor shall provide analysis services for assessing the feasibility of state-of-the-art navigation concepts and algorithms;

engineering services for developing, documenting, maintaining, and testing simulation and ground/flight software to implement these advanced concepts; validating the concepts with high-fidelity simulations and flight-data analysis; transitioning the concepts to a mission analysis support environment, and infusing the concepts into mission operations. The navigation concepts to be supported will provide navigation for a wide range of missions including single satellites and satellite formations in low-Earth, high-Earth, gravity assist, libration point, lunar/cis-lunar, non-Earth planetary and interplanetary orbit including small bodies (asteroids, comets, and planetary moons). These concepts will use radiometric, optical, altimetric, and inertial navigation resources (e.g. GPS technology, Doppler, and range data from the TDRSS or ground station communication links, satellite cross-link measurements, and near- and far-field observations of celestial objects) to estimate onboard or on the ground the absolute and relative navigation and attitude states of one or more satellites, as well as other parameters necessary for navigation.

2.4.6.4.3.1 Relative Navigation

The contractor shall provide services for the development, analysis, implementation, testing and…