SWO-MOS-MOSRD-0001_TO-1_SOL-A_02-25-2025.pdf

Absolute Number

ID Object Number OBJTYPE Object Heading Object Text Rationale IsReq Out-links (All modules)

1 MOSRD-1 1 HD Title FALSE 395 MOSRD-395 1.0-1 TXT Functional and Performance Requirements for SWO Mission Operations Services: Task Order #1:

SOL Solution 2 MOSRD-2 1.1 HD Overview FALSE 3 MOSRD-3 1.1.0-1 TXT The Space Weather Next (SW Next) program will develop and operate space weather science observatories at the Sun-Earth Lagrange point 1 (L1) and in geosynchronous (GEO) orbit. To provide continuity of observations that the Space Weather Follow-On (SWFO) L1 satellite collected, the Space weather Observations at L1 (SOL) project, the first project under the SW Next program, will fly a series of observatories with the first launch of SOL-A expected in 2029.

SOL observatories will provide continuous 24/7 solar observations and space weather measurements to enable the generation of critical low-latency products for the space weather user community.

FALSE

4 MOSRD-4 1.1.0-2 TXT SWO observatory operations depend on reliable ground operations services. SWO flight projects delegate their ground requirements to the SWO Space Weather Ground Services (SWGS) organization for implementation. SWGS provides integrated ground systems and services for SWO observatories, leveraging NESDIS infrastructure and services where appropriate. Ground services include Antenna Services (AS) for space-ground communications, Mission Operation Services (MOS) for satellite mission planning and operations, and Product Services for the generation of space weather products needed by the space weather user communities.

FALSE

5 MOSRD-5 1.2 HD Purpose and Scope FALSE 6 MOSRD-6 1.2.0-1 TXT The purpose of this Mission Operations Services Requirements Document (MOSRD) is to define the functional and performance specifications for a scalable, multi-mission MOS capability that satisfies Space Weather Observation (SWO) spacecraft and instrument operations needs.

FALSE

7 MOSRD-7 1.2.0-2 TXT On the Simplified Block Diagram tab is a block diagram showing nominal Ground Services functions for SWO observatories. Ground Services functions are grouped as Antenna Services, Mission Operations Services, and Product Services. Some high level data interfaces are shown.

FALSE

393 MOSRD-393 1.2.0-3 FIG

394 MOSRD-394 1.2.0-4 FIGC SOL Ground Services and Mission Services High Level Data Flow 8 MOSRD-8 1.2.0-5 TXT SWGS is responsible for ensuring a consolidated space weather ground services approach across the loosely-coupled SWO projects while satisfying individual mission requirements and milestones. SWGS will work with NESDIS to identify and use NESDIS and NOAA institutional facilities and leverage NOAA services, partner agency, and commercial services where they are available and meet mission requirements.

FALSE

9 MOSRD-9 1.2.0-6 TXT For each requirement, there exists a unique MOS Requirement ID, the Requirement Text itself, and a Rationale.

FALSE

10 MOSRD-10 2 HD Related Documentation FALSE 12 MOSRD-12 2.0-1 TXT The SWO-MOS Applicable and Reference (A&R) Documents List, SWGS-MS-LIST-0003, provides the full list of applicable and reference documents, including those cited herein, and their sources. In the event of any unresolved conflict, the Contractor must request conflict resolution by the Contracting Officer in advance of work performed.

FALSE

17 MOSRD-17 3 HD Requirements not yet final FALSE

18 MOSRD-18 3.0-1 TXT Open TBD/TBR Items FALSE 19 MOSRD-19 3.0-2 TXT "Mission Operations Services shall be able to defer planned maintenance activities for up to 21

(TBR) days."

SWGS is working to determine if this requirement impacts OSPO operations or other activities. The duration is based on the maximum expected duration of a space weather event.

FALSE

20 MOSRD-20 4 HD System Requirements FALSE 21 MOSRD-21 4.0-1 TXT Section 4 defines the Mission Operations Services requirements for this Task Order. FALSE 22 MOSRD-22 4.0-2 TXT Requirement functions are assumed to apply to each observatory supported by this capability, concurrently, unless specifically written otherwise.

FALSE

23 MOSRD-23 4.1 HD General Requirements FALSE

DRAFT

ID Object Number OBJTYPE Object Heading Object Text Rationale IsReq Out-links (All modules)

24 MOSRD-24 4.1.0-1 REQ Mission Operations Services shall include an Operational Environment that includes all required operations functions and performance.

The Operational environment provides all certified, secure functions necessary for all operations functions, where all requirements are met.

TRUE

25 MOSRD-25 4.1.0-2 REQ Mission Operations Services shall include a factory environment that permits realistic testing of software prior to installation at any mission operations site, continuing through the period of performance.

A "factory" test environment that enables realistic installation and checkout of software and patches before site delivery is a proven way to streamline patch releases and minimize impacts to operational ground sites, systems, and personnel.

TRUE MSRD-39

The Mission Services shall include a factory environment that permits realistic testing of software prior to installation at any NOAA site, continuing through the period of performance.

26 MOSRD-26 4.1.0-3 REQ Mission Operations Services shall be implemented as different software instances for each mission to provide isolation of each mission.

Strategic isolation can limit the impact of anomalies and may also allow activities on one mission capability to be independent of the state or restrictions of another mission capability. This can reduce the scope of potential impact from events such as maintenance, anomalies, and declared critical weather days.

TRUE MSRD-290

The Mission Services shall maintain Mission Services Software without impacting operations.

27 MOSRD-27 4.1.0-4 REQ The Mission Operations Services factory environment shall be able to interface with the Antenna Services factory environment and deployed Antenna Services IT environment.

An early test capability that enables direct testing of the MOS to Antenna Services interfaces prior to deployment of systems will assist in earlier identification of issues before operational resources are involved.

TRUE MSRD-821

The Mission Services factory environment shall be able to interface with the Antenna Services factory environment and deployed Antenna Services IT environment.

28 MOSRD-28 4.1.0-5 REQ Mission Operations Services shall provide the capability to monitor, command/control, and support operations of the first SOL observatory.

This Task Order includes mission operations services for the first of two new SOL observatories.

TRUE MSRD-54

The Mission Services shall support concurrent operations for a minimum of three (3) observatories at L1.

29 MOSRD-29 4.1.0-6 REQ Mission Operations Services shall be designed and delivered to be scalable and extensible for providing full services to additional observatories.

Supports SWO project requirement for ground services to support concurrent operations for a minimum of three observatories at Sun- Earth Lagrange 1. MOS will need to concurrently operate observatories or instruments in a variety of orbits such low-Earth, highly-elliptical, geosynchronous, and planetary orbits.

TRUE MSRD-54

The Mission Services shall support concurrent operations for a minimum of three (3) observatories at L1.

30 MOSRD-30 4.1.1 HD Units, Formats, and Standards

FALSE

31 MOSRD-31 4.1.1.0-1 REQ Mission Operations Services shall account for leap second adjustments without impact to operations.

Leap second adjustments must be accounted for when coordinating with other elements.

TRUE MSRD-41

The Mission Services shall account for leap second adjustments without impact to operations.

32 MOSRD-32 4.1.1.0-2 REQ Mission Operations Services shall use the Coordinated Universal Time (UTC) standard for all ground operations and data products to a minimum accuracy of one millisecond.

The UTC standard is used throughout NOAA's existing ground infrastructure and is the standard used by much of the user community. Ensures that local time is not used and prevents time zone issues by mandating a standard time.

TRUE MSRD-42

The Mission Services shall use the Coordinated Universal Time (UTC) standard for all ground operations and data products to a minimum accuracy of one millisecond.

33 MOSRD-33 4.1.1.0-3 REQ Mission Operations Services shall synchronize an Observatory on-board clock within ±0.95 seconds (TBR) of UTC.

The ability to sync the clock to a reference clock is needed to ensure data are time tagged correctly.

TRUE MSRD-43

The Mission Services shall synchronize the Observatory on-board clock within ±0.95 seconds of UTC.

34 MOSRD-34 4.1.1.0-4 REQ Mission Operations Services shall use the Metric System of Measurements in accordance with NASA Policy Directive (NPD) 7120.4E.

The metric system is used throughout NOAA's existing ground infrastructure and is the standard used by much of the user community. Standardization of unit conventions simplifies operations and reduces operational risk.

TRUE MSRD-44

The Mission Services shall use the Metric System of Measurements in accordance with NASA Policy Directive

(NPD) 7120.4E.

35 MOSRD-35 4.1.1.0-5 REQ Mission Operations Services shall use the Earth?centered J2000 inertial coordinate system and include reference to the World Geodetic System WGS84.

The J2000 Earth Centered Inertial coordinate system is used throughout NOAA's existing ground infrastructure and is compatible with other systems (such as NASA's Flight Dynamics Facility) that may interface with the SWO observatories. WGS84 is required by FDF to achieve the tracking accuracy required at L1.

TRUE MSRD-45

The Mission Services shall use the Earth-centered J2000 inertial coordinate system with reference to the World Geodetic System WGS84.

36 MOSRD-36 4.1.1.0-6 REQ Mission Operations Services terrestrial digital communications shall conform to internet protocol standards per OMB Memorandum M-05-22, USGv6 NIST-SP-500-267, and NIST-SP-800-119.

U.S. Government mandate. The internal infrastructure shall operate per RFC2460 (IPv6). OMB mandates require all applications and networks to only support IPv6. However due to IPv6-only implementation delays and the possibility of waivers, the internal infrastructure shall also support operation based on RFC791 (IPv4).

TRUE MSRD-46

The Mission Services terrestrial digital communications shall conform to internet protocol standards per OMB Memorandum M-05-22, USGv6 NIST-SP-500-267, and NIST-

SP-800-119.

37 MOSRD-37 4.1.1.0-7 REQ Mission Operations Services IT networking equipment shall comply with the USGv6 Profile found in NIST SP-500-267 and NIST SP-800-119.

All IT networking equipment needs to conform to the NOAA/NESDIS internal timetable being developed for IPv6 only implementation for each Autonomous System where equipment will be installed to comply with the NIST requirements. All Mission Operations Systems IT Network equipment (i.e. Routers, switches, firewalls, hubs) must comply with the IPv6 profile specified therein.

TRUE MSRD-47

The Mission Services IT networking equipment shall comply with the USGv6 Profile found in NIST SP-500-267 and NIST SP-800-119.

38 MOSRD-38 4.1.2 HD Design Constraints FALSE 39 MOSRD-39 4.1.2.0-1 REQ Mission Operations Services shall use existing NESDIS telecommunications infrastructure. NESDIS requirement to leverage available infrastructure where it meets requirements.

TRUE MSRD-49

The Mission Services shall use existing NESDIS telecommunications infrastructure.

ID Object Number OBJTYPE Object Heading Object Text Rationale IsReq Out-links (All modules)

40 MOSRD-40 4.1.2.0-2 REQ Mission Operations Services shall be implemented in the existing NOAA facilities: NOAA Satellite Operations Facility (NSOF) in Suitland, Maryland, and the Consolidated Backup (CBU) facility in Fairmont, West Virginia.

Systems and personnel will reside at these locations in order to interface with legacy and current operations as directed by NOAA/NESDIS. NSOF is the primary satellite operations facility.

Capitalizing on existing infrastructure and staff should reduce cost, schedule, and technical risks. Existing infrastructure includes networks, IT security resources, antenna assets, and operational support services.

TRUE MSRD-50

The Mission Services shall be implemented in the existing NOAA facilities in Suitland, Maryland NOAA Satellite Operations Facility (NSOF) and at Fairmont, West Virginia, Consolidated Backup Facility (CBU).

41 MOSRD-41 4.1.2.0-3 REQ Mission Operations Services shall provide the capability for operators to conduct Observatory operations and Ground Services operations from the primary and backup operations facilities.

Functionality and personnel must reside at this location in order to interface with legacy and current operations. Existing infrastructure includes network, communication link, IT security resources, and operation support services.

TRUE MSRD-51

The Mission Services shall provide operators capability to conduct L1 Series Observatory operations and Ground Services operations from the primary and backup operations facilities.

42 MOSRD-42 4.1.2.0-4 REQ Mission Operations Services shall provide the capability to perform all Mission Operations Services functionality remotely from any Mission Operations Services site.

The ability is needed to remotely login to and from any Mission Operations Services site to allow cross-strapping of operator locations to MOS functionality locations and interfaces at any given NESDIS MOS site. For example, operators may be at the NSOF and control MOS sub-elements located at the CBU, or CBU functions will have interfaces to Mission Planning and Flight Dynamics.

TRUE MSRD-52

The Mission Services shall provide the capability to perform all Mission Services functionality remotely from all Mission Services sites.

MSRD-212

The Mission Services shall provide the capability for CBU to interface with FD and MPS capability.

43 MOSRD-43 4.1.2.0-5 REQ Mission Operations Services shall provide the capability for gap-free observatory monitoring during operator transition at a workstation.

Ensures that the capability to monitor health and safety at a workstation is not interrupted by operator shift change or other activity that may lock the screen.

TRUE MSRD-53

The Mission Services shall provide the capability for gap-free observatory monitoring during operator transition at a workstation.

44 MOSRD-44 4.1.2.0-6 REQ Mission Operations Services shall support concurrent operations for a minimum of three (3) observatories in orbit at Lagrange 1.

SWO Concept of Operations goal is to have two operational observatories at L1 for resilience. Third observatory operation capability is needed for overlap period when additional observatory is launched prior to decommissioning of existing on-orbit assets. Two SWO GEO satellites are envisioned. Each observatory could be in a different mission phase, different environment.

TRUE MSRD-54

The Mission Services shall support concurrent operations for a minimum of three (3) observatories at L1.

45 MOSRD-45 4.1.3 HD Mission Lifecycle Support FALSE 46 MOSRD-46 4.1.3.0-1 REQ Mission Operations Services shall support all phases of Observatory life cycle: pre-launch, launch and early-orbit operations, commissioning, operations, decommissioning, and heliocentric transfer.

A successful SWO observatory project will require support from Mission Operations Services throughout all phases of the observatory lifecycle, from mission definition and design through end of life. The SOL observatories must have a 5.5 year design life and carry consummables for five additional years of operations.

TRUE MSRD-56

The Mission Services shall support all phases of the L1 Series Observatory life cycle: pre-launch, launch and early-orbit operations, commissioning, operations, decommissioning, and heliocentric transfer.

47 MOSRD-47 4.1.3.0-2 REQ Mission Operations Services shall support observatory operations for the life of each mission. Given the requirement to support all observatory mission phases, support must include plans and capability for hardware technology refresh, software updates, and obsolecense to be managed during the required lifetime and possibly into a life extension period. As an example, the SOL observatories each have a five year design life and carry consummables for five additional years of operations.

TRUE MSRD-57

The Mission Services shall support L1 Series observatory operations for the life of each mission.

48 MOSRD-48 4.1.4 HD Configuration Management FALSE

49 MOSRD-49 4.1.4.0-1 REQ Mission Operations Services configuration management shall comply with the OSPO Configuration Management Plan and any project-specific configuration management requirements.

The NESDIS satellite operations environment configuration control process is used to control modifications to all system hardware, software, operational products, and documentation.

TRUE MSRD-60

The Mission Services configuration management shall comply with the L1 Series Configuration Management Control Plan.

50 MOSRD-50 4.1.4.0-2 REQ Mission Operations Services software shall be maintained under configuration management control.

Software configuration management processes and tools are needed to control software changes in order to maintain software integrity and traceability throughout the software life cycle.

TRUE MSRD-61

The Mission Services software shall be maintained under configuration management control.

51 MOSRD-51 4.1.4.0-3 REQ Mission Operations Services hardware shall be maintained under configuration management control.

Hardware configuration management processes and tools are needed to track hardware changes to all MOS sub-elements in order to maintain system integrity and traceability throughout the mission life cycle.

TRUE MSRD-62

The Mission Services hardware shall be maintained under configuration management control.

52 MOSRD-52 4.1.4.0-4 REQ Mission Operations Services documentation shall be maintained under configuration management control.

A documentation configuration management process is needed to track documentations changes within all MOS sub-elements in order to maintain system integrity and traceability throughout the mission life cycle.

TRUE MSRD-63

The Mission Services documentation shall be maintained under configuration management control.

53 MOSRD-53 4.1.4.0-5 REQ Mission Operations Services operational products shall be maintained under configuration management control.

An operational products configuration management process is needed to control changes and maintain integrity and traceability of operational products throughout the mission life cycle.

TRUE MSRD-65

The Mission Services operational products shall be maintained under configuration management control.

54 MOSRD-54 4.1.4.0-6 REQ Mission Operations Services shall have the capability to maintain configuration synchronization across all Mission Operations Services sites.

This requirement does not imply automatic synchronization. The Mission Operations Services has to be capable of syncing across sites, but the site specific configurations will be managed by operational processes. The term 'sites' in this requirement includes both physical sites (NSOF and CBU), and environments (OE, ITE, DE).

TRUE MSRD-64

The Mission Services shall have the capability for maintaining configuration synchronization across all Mission Services sites.

ID Object Number OBJTYPE Object Heading Object Text Rationale IsReq Out-links (All modules)

55 MOSRD-55 4.1.4.0-7 REQ Mission Operations Services' operational versions of observatory software, including Mission Operations Database, shall be retained through the mission life of the observatory.

Supports validation capability and regression testing for any project mission by providing access to versions previously used for that mission. The database accompanying the software would be needed to properly recreate the configuration and capability.

TRUE MSRD-66

The Mission Services' operational versions of software including Observatory Mission Operations Database (MODB) shall be retained throughout the mission life of the L1 Series.

56 MOSRD-56 4.1.4.0-8 REQ Mission Operations Services shall provide the capability to implement and manage each observatory-unique Mission Operations Database (MODB).

The Spacecraft contractor will develop an integrated MODB for each observatory with descriptors, commands, parameters, characteristics, scripts, and other data and information required to operate the observatory. The MODB will be used to manage data necessary to develop, test, and perform satellite mission operations activities.

TRUE MSRD-67

The Mission Services shall provide the capability to manage the MODB.

57 MOSRD-57 4.1.4.0-9 REQ Mission Operations Services shall use the MODB to manage data necessary to develop, test, and perform observatory operations activities.

Data for each observatory development and operations should be managed in a controlled, consolidated database.

TRUE MSRD-68

The Missions Services' MODB shall be used to manage data necessary to develop, test, and perform observatory operations activities.

58 MOSRD-58 4.1.4.0-10 REQ Mission Operations Services operator-defined event types shall be maintained in a database. Allows the operator to create and use events based on operator selection in the use of filtering, and evaluating faults and problems.

TRUE MSRD-69

The Mission Services operator-defined event types shall be maintained in a database.

59 MOSRD-59 4.1.4.0-11 REQ Mission Operations Services shall manage and store all operational products for the life of each mission.

Having access to all previous versions of operational products (such as command procedures, telemetry pages, mission plans, manuever plans, anomaly reports, etc.) follows configuration management best practices. This requirement is meant to drive storage size calculations, not functionality.

TRUE MSRD-70

The Mission Services operational products shall be managed and stored for the mission life.

60 MOSRD-60 4.1.5 HD Networks FALSE 61 MOSRD-61 4.1.5.0-1 REQ Mission Operations Services shall implement communication paths and interfaces as needed to connect distributed Ground Services systems to meet mission requirements.

Mission Operations Services will be provided at prime and backup locations and may include on-premises and cloud systems and interfaces. Communications must be implemented to support meeting functional and performance requirements.

TRUE MSRD-72

The Mission Services shall implement communication paths and interfaces as needed to connect distributed Ground Services systems to meet mission requirements.

62 MOSRD-62 4.1.5.0-2 REQ Mission Operations Services shall monitor the quality, health, and status of its communications services.

Monitoring of communications links for both internal systems and external partner resources is required to understand the status of various services and components, notify operators of anomalies, and assist with anomaly resolution.

TRUE MSRD-73

The Mission Services shall monitor the quality, health, and status of its communications links.

63 MOSRD-63 4.1.5.0-3 REQ Mission Operations Services shall have the capability for fault detection and reporting of ground network communications infrastructure status.

Monitoring of lowest-level processes and interfaces, refreshed at reasonable intervals, is necessary to provide operators with information about system and services status and performance.

These data and information can then enable conditional operations and anomaly responses, be logged and stored, be analyzed and trended, and provide content for operator displays. Intended to monitor hardware elements of the communications infrastructure.

TRUE MSRD-74

The Mission Services shall have the capability for fault detection and reporting of L1 Series ground network communications infrastructure status.

64 MOSRD-64 4.1.6 HD Project Management and Policy

FALSE

65 MOSRD-65 4.1.6.0-1 REQ Mission Operations Services shall incorporate a configurable set of international partner organization ground antennas to acquire downlink telemetry from an observatory per International Partner Organization ICD.

International partner antenna assets may be required to successfully meet the requirements of the SOL Observatories. Interface will be defined by the Government for each partner.

TRUE MSRD-76

The Mission Services shall incorporate configurable number of contributed international partner organization resources to acquire Observatory data from the L1 Series Observatories per the International Partner Organization

ICD.

66 MOSRD-66 4.2 HD IT Security FALSE 67 MOSRD-67 4.2.0-1 REQ Mission Operations Services shall implement NIST SP 800-53 Revision 5 and the Department of

Commerce Enterprise Cybersecurity Policy and NOAA IT Security Manual supplements.

Follows the guidelines of the Federal Information Security Modernization Act (FISMA) of 2014, Office of Management and Budget (OMB) Circular A-130: Managing Information as a Strategic Resource, and the NESDIS Risk Management Framework Assessment and Authorization Process Policy and Procedures For Ongoing Authorization.

TRUE MSRD-78

The Mission Services shall implement the NIST SP 800-53 Rev 5 and the DoC ITSPP/NOAA ITSM supplements.

68 MOSRD-68 4.2.0-2 REQ Mission Operations Services shall provide the capability to lock idle operator sessions while retaining visibility to observatory and system monitoring.

Allow visual display of active telemetry and Ground Services status but no mouse/keyboard inputs until an operator logs in.

TRUE MSRD-79

The Mission Services shall provide capability to lock idle user sessions while retaining visibility to observatory and system monitoring.

69 MOSRD-69 4.2.0-3 REQ Mission Operations Services shall install Enterprise Continuous Monitoring and Operations agents on all IT hardware that is capable of having the agent installed.

Follows the architectural decision to use existing NOAA infrastructure and tools.

TRUE MSRD-80

The Mission Services shall install Enterprise Continuous Monitoring and Operations (ECMO) agents on all IT hardware that is capable of having the agent installed.

70 MOSRD-70 4.2.0-4 REQ Mission Operations Services shall install ECMO relays at locations that connect to the Ground Services ECMO server.

Follows the architectural decision to use existing NOAA infrastructure and tools. Locations include site and/or environments.

TRUE MSRD-81

The Mission Services shall install ECMO relays at locations that connect to the Ground Services ECMO server.

71 MOSRD-71 4.2.0-5 REQ Mission Operations Services shall install and use Government-specified Security Information and Event Management tools and forward all software logs collected to the Government-specified repository.

The implementation will use existing NOAA infrastructure and tools, installed at appropriate locations (which includes sites and/or environments). This requirement focuses on forwarding software logs.

TRUE MSRD-82

The Mission Services shall install Splunk appliances and forward all logs collected to the Ground Services Splunk instance.

ID Object Number OBJTYPE Object Heading Object Text Rationale IsReq Out-links (All modules)

72 MOSRD-72 4.2.0-6 REQ Mission Operations Services shall forward all system logs to the Government-specified system repository.

The implementation will use existing NOAA infrastructure and tools, installed at MOS sites and/or environments. This requirement focuses on forwarding system logs.

TRUE MSRD-83

The Mission Services shall forward all system logs to the local Splunk appliance.

73 MOSRD-73 4.2.0-7 REQ Mission Operations Services shall install distributed scanners at locations that connect to the (system) vulnerability scanner.

Follows the architectural decision to use existing NOAA infrastructure and tools. Locations include site and/or environments.

TRUE MSRD-84

The Mission Services shall install distributed scanners at locations that connect to the (system) vulnerability scanner.

74 MOSRD-74 4.2.0-8 REQ Mission Operations Services shall be compliant with NIST SP 800-82 R3 Guide to Operational Technology Security.

Follows the guidelines of OMB Circular A-130: Managing Information as a Strategic Resource and Executive Order 13636: Improving Critical Infrastructure Cybersecurity

TRUE MSRD-85

The Mission Services shall be compliant with NIST SP 800- 82 R3 Guide to Operational Technology (OT) Security.

75 MOSRD-75 4.2.0-9 REQ Mission Operations Services shall implement mechanisms to ensure data identified as requiring Restricted Access can only be accessed by authorized users.

Within the multi-mission system, any data item identified as requiring Restricted Access must be protected to ensure that only authorized users can access proprietary or sensitive information.

Restricted Access data items will be identified by the Government.

These include, but are not limited to, the following: loads, databases, telemetry, trend plots, tasks, reports, documents, and operational products (procedures).

TRUE

76 MOSRD-76 4.2.0-10 REQ Mission Operations Services shall manage a configurable structure to control access on a data item-by-data item basis without hardware or software changes.

Different data items require differing control levels, i.e., more or less restrictions on access. A configurable data management structure provides the Government with flexibility to address evolving needs for controlling various types of data items. These types of data items include, but are not limited to, the following: loads, databases, telemetry, trend plots, tasks, reports, documents, and operational products (procedures).

TRUE

77 MOSRD-77 4.3 HD Availability FALSE 78 MOSRD-78 4.3.0-1 REQ Mission Operations Services shall have a minimum data availability of 99.5 percent as measured over any 30-day period.

For this element, data availability is the ratio of the data delivered to the Product Services interface to the contiguous data that is received at the MOS Element. This includes Level 0 processing, distribution to N-Wave, and the use of N-Wave to transport the data.

TRUE MSRD-87

The Mission Services shall have a minimum Data Availability of 99.5 percent as measured over any 30-day period.

79 MOSRD-79 4.3.0-2 REQ Mission Operations Services shall have a minimum Operational Availability of 98.9 percent as measured over any contiguous 30-day period.

Operational availability includes the availability of all MOS sub-elements other than the Level 0 processing sub-element, sub-elements required for distribution to N-Wave, and N-Wave.

TRUE MSRD-95

The Mission Services shall have a minimum Operational Availability of 98.9 percent as measured over any contiguous 30-day period.

80 MOSRD-80 4.3.0-3 REQ Mission Operations Services shall have a maximum per-event downtime of two (2) hours in Level 0 mission data processing functionality during nominal observatory operations.

This maximum gap requirement aligns to a SOL requirement and applies during normal operations (plus maintenance and failover activities). There is a more stringent gap requirement during Critical Space Weather Days. This is a broad performance requirement on the system and it is desired to minimize all gaps to much less than this in the design and details of failovers and anomaly resolution.

Planned ground outages should not be adjacent to or coincide with planned observatory data outages.

TRUE MSRD-88

The Mission Services shall have a maximum consecutive downtime of 2 hours in Level 0 mission data processing functionality during the nominal observatory operations.

81 MOSRD-81 4.3.0-4 REQ Mission Operations Services Solar Wind data gaps shall be less than 20 seconds per day during NWS-declared Critical Space Weather Days.

The 20 seconds is the current MOS allocation of the 5 minute data gap allowable as called out in project requirements. This covers Level 0 science data processing only, not all functions of the Mission Services. Activities like routine maintenance procedures, that could potentially affect system performance, do not occur during Critical Space Weather Days. Critical Space Weather is typically any of the following disturbances: S4-S5 solar radiation storms, R4-R5 radio blackouts, and G4-G5 geomagnetic storms. Intervals of Critical Space Weather Days can last between 3 and 21 days.

TRUE MSRD-89

The Mission Services' in situ Solar Wind data gaps shall be less than 20 seconds per day during the NWS-declared Critical Space Weather Days.

82 MOSRD-82 4.3.0-5 REQ Mission Operations Services shall achieve an availability of 99.5 percent of level 0 data delivery to Product Services during nominal operations, solar radiation storm conditions through a level of S4, solar flare conditions through a level of X50, and during designated Critical Space Weather Days.

This requirement ensures that MOS maintains the same high level of availability during critical space weather days as it does throughout the year. Mission Operations Services do not distinguish between the HAP and non-HAP data hence the same availability requirement applies during all operations. This requirement ensures that the Mission Services is meeting the HAPs data delivery requirement. This requirement also ensures that MOS is meeting the data delivery requirement during solar radiation storm conditions through a level of S4, solar flare conditions through a level of X50 and during Critical Space Weather Days. It also ensures no planned outages are scheduled during critical space weather days.

TRUE MSRD-90

The Mission Services shall achieve a availability of 99.5 percent of level 0 data delivery to Product Services during nominal operations, solar radiation storm conditions through a level of S4, solar flare conditions through a level of X50 and during the NWS-declared Critical Space Weather Days.

83 MOSRD-83 4.3.0-6 REQ Mission Operations Services shall be able to defer planned maintenance activities for up to 21 (TBR) days.

The requirement for availability of High Availability Products and uninterrupted delivery is high during Critical Space Weather Days and for solar flare conditions through a level of X50, so Mission Operations Services must be able to defer activities that could impact availability for a period of time. Intervals of Critical Space Weather Days can last between 3 and 21 days.

TRUE MSRD-93

The Mission Services shall be able to defer planned maintenance activities for up to 21 (TBR) days.

ID Object Number OBJTYPE Object Heading Object Text Rationale IsReq Out-links (All modules)

84 MOSRD-84 4.3.0-7 REQ Mission Operations Services shall execute planned maintenance activities without impact to MOS global data availability.

Space Weather product delivery must be highly reliable, and systems must be designed to minimize the probability and duration of data delivery gaps or outages, within Mission Operations Services or for interfacing systems including Antenna Services and Product Services.

Maintenance activities are necessary for any operational system and ensures that the overall system continues to meet scientific, technical, functional, and performance requirements in addition to availability and reliability requirements. Types of maintenance could include proactive, corrective, science, and limited scope adaptive maintenance. The high availability requirement of this system necessitates the ability to perform these critical maintenance activities while not impacting the performance of the operational environment.

TRUE MSRD-94

The Mission Services shall execute planned maintenance activities without impact to the Mission Services global data availability.

85 MOSRD-85 4.4 HD Observatory Operations FALSE 86 MOSRD-86 4.4.1 HD General Operations FALSE 87 MOSRD-87 4.4.1.0-1 REQ Mission Operations Services shall confirm Telemetry and Command Health of a SWO observatory any time the observatory is in view of an antenna station capable of supporting a command link for nominal operations.

The spacecraft is required to go at least 7 days without ground communication but only a minimum of 4 days for nominal operations. Ensures satellite has updated ephemeris, uploads, and information necessary for science operations and does not enter a safe mode due to lack of ground communication.

TRUE MSRD-98

The Mission Services shall confirm Telemetry and Command Health of the observatory any time the Observatory is in view of an antenna station capable of supporting a command link for nominal operations.

88 MOSRD-88 4.4.1.0-2 REQ Mission Operations Services shall support observatory entry into, activities during, and recovery from Safe Hold mode.

Provide operator awareness, status, and capabilities associated with the Safe Hold configuration and all mode changes to/from Safe Hold mode.

TRUE MSRD-99

The Mission Services shall support observatory entry into, activities during, and recovery from Safe Hold mode.

89 MOSRD-89 4.4.1.0-3 REQ Mission Operations Services shall be capable of using designated U.S. Government partner organization ground antennas for performing SWO observatory command functions.

This applies to NASA or other U.S. Government asset for commanding when NOAA uplinks are unavailable. NOAA will make arrangements and prepare for partner support including Launch and early in-orbit activation, contingency support, and spacecraft health and safety communications.

TRUE MSRD-100

The Mission Services shall be capable of using designated U.S. partner organization resources for performing Telemetry and Command functions per the International Partner Organization ICD.

90 MOSRD-90 4.4.1.0-4 REQ Mission Operations Services shall be capable of using designated non-NOAA antenna resources for downlink telemetry capture functions.

This applies to commercial, international partner, or U.S.

Government assets for receipt of downlink telemetry to augment NESDIS assets for antenna services. NOAA will make arrangements and prepare for authorized partner support including pre-launch testing.

TRUE

91 MOSRD-91 4.4.1.0-5 REQ Mission Operations Services shall accommodate a minimum of 50 concurrent operator sessions across each Mission Operations Services instance.

Ensures the Mission Operations Services has the capacity (with both connectivity and interactive response performance) to allow a large number of operators to perform all MOS functions at the same time, both commissioning and nominal operations. The number is derived from experience on similar missions.

TRUE MSRD-101

The Mission Services shall accommodate a minimum of 50 concurrent operator sessions across each Mission Services instances.

92 MOSRD-92 4.4.2 HD Mission Planning FALSE 93 MOSRD-93 4.4.2.0-1 REQ Mission Operations Services shall generate an Observatory Operations Timeline for each mission. This time-ordered sequence enables efficient mission planning. The

Timeline is used to generate, for example, a mission commanding absolute time sequence.

TRUE MSRD-103

The Mission Services shall generate an Observatory Operations Timeline.

94 MOSRD-94 4.4.2.0-2 REQ Mission Operations Services shall deconflict mission planning inputs into the Observatory Operations Timeline.

Resources and conflicting commands need to be realized and incorporated into the Operations Timeline.

TRUE MSRD-104

The Mission Services shall deconflict mission planning inputs into the Observatory Operations Timeline.

95 MOSRD-95 4.4.2.0-3 REQ Mission Operations Services shall plan all Observatory events in the Observatory Operations Timeline within Observatory constraints.

The Operations Timeline needs to consider real life constraints of the system it is performing mission planning for.

TRUE MSRD-105

The Mission Services shall plan all Observatory events in the Observatory Operations Timeline within Observatory constraints.

96 MOSRD-96 4.4.2.0-4 REQ Mission Operations Services shall plan all Observatory events in the Observatory Operations Timeline within Ground Services constraints.

The Operations Timeline needs to consider real life constraints of the system it is performing mission planning for. Includes processing operational support requests from other ground elements and incorporating them into operational plans.

TRUE MSRD-106

The Mission Services shall plan all Observatory events in the Observatory Operations Timeline within Ground Services constraints.

97 MOSRD-97 4.4.2.0-5 REQ Mission Operations Services shall have the capability to deconflict observatory operations from interfering with other identified missions using similar frequency bands.

Command uplinks to a SWO observatory have the potential to cause interference with other satellites near the beam if the radiated frequencies are too similar. Mission Planning uses orbital information of designated other satellites to plan command uplink times that avoid this potential interference.

TRUE

98 MOSRD-98 4.4.2.0-6 REQ Mission Operations Services shall upload to an observatory sufficient operations information to enable nominal on-orbit operations without ground contact for a minimum of seven (7) days.

Enables nominal observatory operations and science data collection with ground 8x5 operations efficiency and tolerance for ground anomalies.

TRUE MSRD-107

The Mission Services shall upload to the observatory sufficient operations information to enable nominal on-orbit operations without ground contact for a minimum of seven (7) days.

99 MOSRD-99 4.4.2.0-7 REQ Mission Operations Services shall upload to an observatory sufficient operations information to ensure observatory health and safety in the absence of ground contact for a minimum of seven

(7) days.

Ensures an observatory has updated ephemeris, uploads, and does not enter a safe mode due to lack of ground communication. This is an estimate based on SOL spacecraft requirements, where the spacecraft is required to operate at least 7 days without ground communication but only a minimum of 4 days for nominal science operations.

TRUE MSRD-108

The Mission Services shall upload to the spacecraft sufficient operations information to ensure spacecraft health and safety in the absence of ground contact for a minimum of seven (7) days.

100 MOSRD-100 4.4.3 HD Orbit Management FALSE

ID Object Number OBJTYPE Object Heading Object Text Rationale IsReq Out-links (All modules)

101 MOSRD-101 4.4.3.0-1 REQ Mission Operations Services shall provide observatory orbit determination and management. Orbit knowledge and control enables space-ground communications and observatory science collection. Orbit determination uses radiometric tracking data from various sources.

TRUE MSRD-110

The Mission Services shall provide observatory orbit determination and management.

102 MOSRD-102 4.4.3.0-2 REQ Mission Operations Services (primary and backup) shall receive radiometric tracking data from Antenna Services for NOAA antenna stations.

Tracking data (range, Doppler) from NOAA ground antennas will be used to generate satellite orbit solutions.

TRUE MS-AS-IRD-222

Mission Services shall receive radiometric tracking data from the WCDAS Antenna Services.

MS-AS-IRD-224

Mission Services shall receive radiometric tracking data from the CBU Antenna Services.

MSRD-111

The Mission Services shall receive radiometric tracking data from the Antenna Services in accordance with the

MS-AS IRD.

103 MOSRD-103 4.4.3.0-3 REQ Mission Operations Services (primary and backup) shall receive radiometric tracking data sent from Antenna Services for non-NOAA antenna sites approved to provide tracking services.

Tracking data from non-NOAA ground antennas, especially in the southern hemisphere, will be used to generate satellite orbit solutions.

TRUE MS-AS-IRD-612

Mission Services shall receive radiometric tracking data from non-NOAA stations via Antenna Services.

MSRD-114

The Mission Services (primary and backup) shall receive radiometric tracking data sent from U.S. Partner sites providing tracking services.

104 MOSRD-104 4.4.3.0-4 REQ Mission Operations Services shall process radiometric tracking data to generate satellite orbit solutions and products.

Necessary for observatory orbit management and mission planning. TRUE

105 MOSRD-105 4.4.3.0-5 REQ Mission Operations Services shall use the NASA General Mission Analysis Tool (GMAT) for orbit determination and navigation.

The multi-mission, open source software system used by many NOAA missions for space mission design, optimization, and navigation.

TRUE MSRD-116

The Mission Services shall use the NASA General Mission Analysis Tool (GMAT) for orbit determination and navigation.

106 MOSRD-106 4.4.3.0-6 REQ Mission Operations Services shall send data and files to the NASA Goddard Flight Dynamics Facility.

Flight Dynamics will provide support during early mission operations.

MOS will send spacecraft orbit information, maneuver requests, tracking data, etc. to support Flight Dynamics design, analysis, and mission support. Files will be sent via designated NOAA-NASA network and the Flight Dynamics Facility Customer Interface.

TRUE MSRD-112

The Mission Services shall send data and files to NASA Flight Dynamics in accordance with the TBD IRD/ICD.

107 MOSRD-107 4.4.3.0-7 REQ Mission Operations Services shall have the capability to receive and use information and files from the NASA Goddard Flight Dynamics Facility.

Provides the capability to receive Flight Dynamics-generated mission plans, maneuver plans, orbit solutions, or other information per support agreement. Files will be sent via designated NOAA-NASA network and the Flight Dynamics Facility Customer Interface.

TRUE MSRD-113

The Mission Services shall have the capability to receive and use NASA Flight Dynamics information and files.

108 MOSRD-108 4.4.3.0-8 REQ Mission Operations Services shall provide the capability to acquire orbital elements from external sources, including satellite telemetry.

External system source examples include post injection updates from the launch vehicle provider and external inputs for collision/proximity analyses. In addition, satellites may use space-based navigation systems and provide their own orbit information in downlinked telemetry.

TRUE MSRD-115

The Mission Services shall provide the capability to acquire orbital elements from external sources.

109 MOSRD-109 4.4.4 HD Attitude Management FALSE 110 MOSRD-110 4.4.4.0-1 REQ Mission Operations Services shall provide the capability for observatory attitude determination and management.

Attitude knowledge and control enables space-ground communications and observatory science collection. The satellite provides attitude information in telemetry. Attitude management is required in order to maintain spacecraft operation and allow the collection of accurate scientific data. Observational product accuracy requirements cannot be met without adequate Observatory attitude management. Attitude management includes at least processing telemetry to determine observatory attitude and the capability to monitor, trend, and manage observatory attitude for calibration activities, momentum management (monitoring and dumps), and other operations.

TRUE MSRD-118

The Mission Services shall provide the capability for observatory attitude determination and management.

111 MOSRD-111 4.4.4.0-2 REQ Mission Operations Services shall use the NASA Attitude Ground System (AGS) tool. AGS is used at NASA/Goddard Space Flight Center to support a wide variety of missions and other NOAA missions. AGS is MATLAB-based with a library of functionalities and core software. Use includes sending and receiving data from the tool, reading and writing to the life of mission storage, etc.

TRUE MSRD-119

The Mission Services shall use the NASA Attitude Ground System (AGS) tool.

112 MOSRD-112 4.4.5 HD Command Operations FALSE 113 MOSRD-113 4.4.5.0-1 REQ Mission Operations Services shall use a Level 1 certified uplink security system, per NIST SP 800-

38D Galois/Counter Mode with FIPS PUB 140-3 (or later version), that uses a FIPS PUB 197-certified Advanced Encryption Standard 256 bit key algorithm to generate encrypted and authenticated commands.

Encryption of uplink command is required. NIST standards tell how to put together the encryption and authentication using the approved NIST standards and how that is combined with the RF error control coding.

TRUE MSRD-121

The Mission Services shall generate encrypted Observatory command uplink per FIPS PUB 140-3 (or later version).

114 MOSRD-114 4.4.5.0-2 REQ Mission Operations Services and encryption/decryption devices shall be configurable to operate with a non-standard spacecraft security process.

Ground systems will need to be compatible with the approach implemented for spacecraft communication if the spacecraft vendor chooses not to follow the uplink security standard.

TRUE

115 MOSRD-115 4.4.5.0-3 REQ Mission Operations Services spacecraft communications, including encryptors for command uplink, shall use GSFC-STD-8012 Bulk Security Standard for Spacecraft Communication as a guide for implementing the security.

Standard to define a bulk security (encryption and authentication) standard for NASA missions, to perform the error correction/detection decoding prior to processing the security at the receive end and other updates.

TRUE

ID Object Number OBJTYPE Object Heading Object Text Rationale IsReq Out-links (All modules)

116 MOSRD-116 4.4.5.0-4 REQ Mission Operations Services shall send encrypted command uplink to the Antenna Services. The spacecraft is required to not transmit an unencrypted CLTU or telecommand transfer frame in telemetry.

TRUE MSRD-122

The Mission Services shall send the encrypted command uplink to the Antenna Services in accordance with the MS-

AS IRD.

117 MOSRD-117 4.4.5.0-5 REQ Mission Operations Services shall transmit real time commands within 1 second of execution by the operator.

Performance requirement constraining command delays to 1 second.

"Execution" here means the point at which the operator initiates execution of the command.

TRUE MSRD-123

The Mission Services shall transmit real time commands within 1 second of execution by the operator.

118 MOSRD-118 4.4.5.0-6 REQ Mission Operations Services shall generate stored command processor scripts from Observatory delta?V maneuver plans.

Required to execute maneuvers that keep the Observatory in a stable…