SWO-MOS_MOSRD_TO-2-CCOR_draftRFP_v04-08-2025.pdf

Space Weather Observations - Mission Operations Services (SWO-MOS)

Mission Operations Services Requirements Document (MOSRD)

IDIQ Contract -- Task Order 2 for CCOR-3 Instrument Monitoring -- Draft Version SWO Reviewed – Not Subject to Export Control

ID Object Object Object Text Rationale

4.4.15 CCOR-3 Instrument Monitoring

TBD Mission Operations Services shall receive CCOR-3 instrument telemetry data

(housekeeping and engineering data).

CCOR-3 will be hosted on the European Space Agency Vigil satellite, with mission operations conducted from the European Satellite Operations Center (ESOC). CCOR-3 unprocessed telemetry and Vigil auxiliary data are expected to be provided to NOAA for product generation and to support instrument health and status monitoring. CCOR-3 non-science telemetry includes both housekeeping telemetry data types (constant downlink) and engineering telemetry data types (on demand).

Mission Operations Services shall receive CCOR-3 telemetry (engineering data and housekeeping data) in accordance with the Data Exchange ICD

(TBC).

The telemetry data, content, and formatting will be described in the Data Exchange ICD (TBC) to be developed jointly by the host ESOC and the SWO L5 project.

Mission Operations Services shall receive and process CCOR-3 playback telemetry data and ground telemetry retransmissions without interference to routine data processing and operations.

Telemetry stored onboard and played back to the ground later or retransmitted from the ESOC can fill telemetry gaps, but such telemetry must be identified as such and handled without impact to other activities.

Mission Operations Services shall provide CCOR-3 housekeeping and engineering data handling, processing, distribution, storage, and display capabilities.

Housekeeping data are necessary to understand and trend instrument status. Asynchronous engineering data are commanded on and are necessary to understand detailed instrument status and investigate anomalies.

Mission Operations Services shall provide authorized instrument engineers with remote access to CCOR-3 telemetry and telemetry data analysis tools for instrument monitoring.

Allows engineers to review instrument health and status when not located at a MOS-authorized site, but from within the NOAA corporate network, which helps to quickly identify any faults or problems. This requirement applies only to NOAA-secured terminals outside of the MOS security boundary. Existing NOAA VPN systems would be used to access the NOAA corporate network from the Internet.

Mission Operations Services shall display CCOR-3 telemetry data in either raw or engineering units based on engineer's selection.

Allows the engineer to choose what units they want displayed depending on what is most useful to monitoring and analysis.

Mission Operations Services shall display a new page complete with CCOR-3 housekeeping data within 3 seconds (TBR) of its selection.

This ensures the Graphical User Interface is responsive to an information request in near real-time, which is most useful.

Mission Operations Services shall refresh CCOR-3 telemetry data displays no faster than twice per second.

This ensures the person can read and process rapidly changing information, rather than just seeing a stream of information.

Mission Operations Services shall provide the capability to display This provides the engineer with plots based on instrument housekeeping data rates.

Mission Operations Services shall identify gaps in the contiguous housekeeping data stream.

The system needs to identify missing instrument telemetry data in order for the engineer to assess and to request a retransmission if necessary.

Mission Operations Services shall generate a notification as soon as a gap is identified in the contiguous housekeeping data stream.

Notification begins the process of fault identification and resolution to minimize data gaps and ensure continuity of health and safety data for status monitoring. If any housekeeping data frame is missing when data is consolidated, then it is considered a gap.

Mission Operations Services shall import CCOR-3 Telemetry Databases. The solution needs the ability to ingest the databases delivered by the CCOR-3 vendor. The CCOR-

3 telemetry database is delivered in accordance with the CCOR-3 CDRL Data Item Description.

Mission Operations Services shall implement CCOR-3 Telemetry Databases. The solution must implement and use the CCOR-3 telemetry database for required instrument monitoring and CCOR-3 operations support.

1 of Export of Draft MOSRD requirements for SWO-MOS TO-01 *** SOURCE SELECTION SENSITIVE ***DRAFT

Mission Operations Services shall provide the capability to support the plans and procedures for CCOR-3 calibration activities.

Necessary to maintain the instrument in a fully calibrated state.

Mission Operations Services shall provide the capabilit to monitor and assess the results of CCOR-3 calibration activities.

Necessary to maintain the instrument in a fully calibrated state.

Mission Operations Services shall provide data to non-MOS tools identified for use in CCOR-3 calibration activities.

Necessary to maintain the instrument in a fully calibrated state.

Mission Operations Services shall provide the capability for CCOR-3 engineering analysis, which includes telemetry data analysis, trending, and visualization.

The capability for large-scale data analysis, trending, and visualization of results allows engineers to understand instrument state and anticipate the need for any corrective actions.

Mission Operations Services shall make all CCOR-3 telemetry (housekeeping and engineering) data available for engineering analysis.

The capability for large-scale data analysis, trending, and visualization of results allows engineers to understand instrument state and anticipate the need for any corrective actions.

Mission Operations Services shall support engineering analysis for the life of the mission.

Engineering analysis allows engineers to identify potential performance issues, understand system degradation, and develop mitigation plans. Access to telemetry data across the mission life enables long-term trending.

Mission Operations Services shall identify telemetry data that is invalid. Data flagged or otherwise marked as invalid may not be appropriate to use for data analysis functions. Examples of invalid data could include stale data or data that does not correctly convert into engineering values.

Mission Operations Services engineering analysis shall account for invalid data.

Capability will not be impacted by invalid or out-of-range data, and invalid data will not be discarded. Knowledge of invalid data supports identifying potential performance issues, understanding system degradation, and developing mitigation plans.

Mission Operations Services shall provide the capability to search and retrieve CCOR-3 telemetry data from storage.

Necessary for analysis, trending, and fault management.

Mission Operations Services shall provide the capability to define and automate the generation of telemetry data trends.

This potentially reduces cost through automation. Intent is configurable automation of engineer-defined trending reports.

Mission Operations Services shall incorporate CCOR-3 playback data and ground retransmitted data into the instrument trending archive.

Provides a more complete data repository for trending and analysis.

Mission Operations Services shall have the capability to display all CCOR-3 trended data, even if the data has not changed.

Provides situational awareness of CCOR-3 status and data.

SWO Reviewed – Not Subject to Export Control

2 of Export of Draft MOSRD requirements for SWO-MOS TO-01 *** SOURCE SELECTION SENSITIVE ***DRAFT