SWO-MOS PWS TO2 L5 CCOR-3.docx

GSFC SWGS CMO

Draft

SWGS-MS-SOW-0004, Draft Space Weather Observations (SWO) Code 492

Space Weather Observations Mission Operations Services

(SWO-MOS)

Task Order 02 Performance Work Statement:

Lagrange 5 Vigil Project Compact Coronagraph Operations Services Effective Date: Draft Expiration Date: Draft

SWO-MOS T0-2 PWS L5 CCOR-3 SWGS-MS-SOW-0004 Draft Effective Date: TBD

Check https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

Check FPD BCI Document Management Guidance to verify that this is the correct version prior to use

400-FORM-0002 (4/16/2014)

U.S. Department of Commerce (DOC) National Oceanic and Atmospheric Administration (NOAA) National Environmental Satellite, Data, and Information Service (NESDIS)

SWO Reviewed – Not Subject to Export Control

Space Weather Observations Mission Operations Services

(SWO-MOS)

Task Order 02 Performance Work Statement:

Lagrange 5 Vigil Project Compact Coronagraph Operations Services Review/Signature/Approval Page

Prepared by:

Reviewed by:

NOAA/NESDIS/SWO

NOAA/NESDIS/SWO

Approved by:

NOAA/NESDIS/SWO

Preface This document provides the Task 02 Performance Work Statement for L5 Vigil Mission Compact Coronagraph Services under the Indefinite Delivery / Indefinite Quantity (IDIQ) for the Space Weather Observations Mission Operations Services (SWO-MOS) contract.

This document is under SWO configuration control. Once this document is approved, SWO approved changes are handled in accordance with Class I and Class II change control requirements as described in the SWO Configuration Management Procedures, and changes to this document shall be made by complete revision.

Any questions should be addressed to:

SWO Configuration Management Office

NASA/GSFC

Code 492.0 Greenbelt, MD 20771

Change History Log

(Reference the CCR & CCB/ERB Approval Date)

Table of TBDs/TBRs/TBSs

Table of Contents

List of Tables Table 1. L5 CCOR-3 capability Builds and Releases aligned to Milestone Reviews 8

List of Figures No table of figures entries found.

Check https://ipdtdms.gsfc.nasa.gov to verify that this is the correct version prior to use.

1 Introduction

1.1 Overview

The Government requires that the multi-mission Space Weather Observations Mission Operations Services (SWO-MOS) support the Lagrange 5 (L5) Vigil Project Compact Coronagraph services, in accordance with the CCOR-3 Instrument Monitoring requirements within the Mission Operations Services Requirements Document (MOSRD) and meeting maturity milestone provided in the L5 Project Review Plan.

The SWO L5 project will provide NOAA’s third copy of the Naval Research Laboratory (NRL) Compact Coronagraph (CCOR-3) to the European Space Agency (ESA) to be integrated and flown on the ESA Vigil mission that is planned to launch no earlier than 2031.

The Vigil mission will be developed by the ESA Space Safety Programme, and the Mission Operation Centre (MOC) will be located in the European Space Operations Centre (ESOC). NOAA is responsible for development of the CCOR-3, for assisting with instrument integration onto Vigil and supporting operational preparation, for training and equipping ESOC operators to conduct all CCOR-3 nominal and anomaly operations, and for calibration and validation of the instrument and related products during the Vigil commissioning phase. After commissioning, NOAA will establish responsibility to maintain situational awareness of the health and status of CCOR-3 and will support ESA in the event of any anomalies, including routine trending of CCOR-3 status. NOAA will retain responsibility for routine operational and retrospective processing and distribution of the CCOR-3 science data into products.

ESA’s Space Weather Payload Data Centre (PDC) will provide CCOR-3 telemetry & data, observatory ancillary data needed to process CCOR-3 data, and processed data from the other Vigil instruments. All data will be received within SWO’s Space Weather Ground Services (SWGS) architecture for processing, archive, trending, and distribution.

1.2 Scope

The Solution for support of the Vigil-hosted CCOR-3 instrument must modify and interface with the multi-mission SWO-MOS Solution. It must outline and establish the interfaces between ESA’s PDC, NOAA’s Product Services, or a combination of the two that is necessary to provide CCOR-3 health and safety data to the MOS. The Solution must satisfy the Government’s Mission Operations Services Requirements Document (MOSRD) as updated by this Task Order. The working Solution must be demonstrated to achieve L5 project lifecycle maturity milestones in accordance with the L5 Project Review Plan document. The Contractor must:

· Create the Contractor SWO-MOS programmatic structures to manage this task

· Develop and deliver updates to all documents as necessary to support this task and in accordance with the CDRL document

· Iteratively evolve the Solution to fulfill L5 CCOR-3 requirements according to Agile development principles

· Test, deploy, and verify the Solution for Government operation from Government facilities

The Solution must provide NOAA engineers with the services, capabilities, and features needed to ensure support to ESA for instrument test, checkout, operations, health, and safety for the full operation lifecycle of the CCOR-3 instrument. Timely and correct services must be deployed to support prelaunch end-to-end testing of the instrument, as well as post-launch commissioning, nominal operations and analyses, and anomaly resolution activities. Functional capabilities and features including the following:

· Receiving housekeeping and mission data from CCOR-3

· Storing housekeeping data (temporary and life-of-mission)

· Processing (extracting, applying unit transformations, etc.) housekeeping data for monitoring and trending

· Trending and analyzing data

1.3 Period of Performance

From Task authority to proceed through March 31, 2032 (six months past the notional Vigil launch readiness date.)

1.4 Places of Performance

A. Mission Operations Services locations for this task order include:

· NOAA Satellite Operations Facility (NSOF) in Suitland, MD

· NESDIS Consolidated Backup Facility (CBU) in Fairmont, WV

· Contractor Facilities B. Other remote work locations may require ad hoc visits and will be identified by the Government. These may include sites such as,

· Goddard Space Flight Center in Greenbelt, MD

· ESA Vigil project sites, as requested and approved by the COR or CO. These may include, but are not limited to:

a. European Space Research & Technology Centre (ESTEC), Noordwijk, The Netherlands

b. European Space Operations Centre (ESOC), Darmstadt, Germany

· End-to-end test locations

· ESA's Payload Data Center

2 Related Documentation This task order adds project requirements to the development and sustainment of the multi-mission SWO-MOS Solution. The SWO-MOS Base PWS is the parent to this task order and all documents referenced in the Base PWS are applicable.

The SWO-MOS Applicable and Reference (A&R) Documents List, SWGS-MS-LIST-0003, provides the list of applicable and reference documents for this PWS with their sources. In the event of any unresolved conflict, the Contractor must request conflict resolution by the Contracting Officer in advance of work performed.

The SWO-MOS Contract Data Requirements List (CDRL) Document, SWGS-MS-CDRL-0001, provides an applicability matrix and defines the required content of document deliverables required for performance of tasks under this contract. The Contracting Officer Representative is responsible for ensuring all deliverables are in compliance with the CDRL.

The SWO Program Acronym and Glossary List, SWO-MGMT-LIST-0001, defines terminology as used in this document and throughout the SWOPD. In the event of conflict between terminology in this document and any other dictionary, the SWO terminology will take precedence. In the event of any unresolved conflict, the Contractor must request conflict resolution by the Contracting Officer.

3 REQUIREMENTS

3.1 Implement SWO-MOS Capabilities for the L5 Compact Coronagraph-3 The Contractor shall decompose requirements and derive user stories from the MOSRD sufficient to describe the full scope of the capability.

The Contractor shall develop and deliver a SWO-MOS Solution that meets the MOSRD requirements and the L5 CCOR-3 ion needs, consistent with the L5 CCOR-3 timeline.

The Contractor shall develop and use verification, validation, and regression tests of SWO-MOS capabilities appropriate to L5 CCOR-3.

The Contractor shall develop, deliver, integrate, test, and validate capabilities and features to fulfill user stories and thereby satisfy MOSRD requirements through Program Increments.

3.2 Establish Concept and Development Roadmap

The Contractor shall assess the GFP Mission Operations Services capability relative to the requirements of this Task Order. The contractor shall propose an interface solution to provide all necessary data to the MOS. The Contractor shall present any required baseline and mission unique changes in a Contractor-hosted Mission-Unique Concept Review (MUCR) for assessment by a Government-designated board. The MUCR assessment for this task order shall include, but is not limited to:

1) Cost and schedule assessment for all proposed options

2) Evaluate and propose an interface solution involving and coordinating with ESA’s PDC and NOAA’s Product Services that achieves the following at a minimum:

a) CCOR-3 Health & Safety telemetry received by MOS

b) CCOR-3 Health & Safety telemetry received by Product Services

c) CCOR-3 Level 0 product data (provided by ESA) received by Product Services

d) Vigil observatory ancillary data needed to process CCOR-3 data received by Product Services

e) Other Vigil instrument processed data received by Product Services

3) Assess security impacts and mitigation within and across all interface boundaries

4) Address risks for shared infrastructure and partitioning between missions.

5) Evaluate all equipment (routers, switches, modems, servers, etc.) that can be expanded for CCOR-3 data and re-used or would require replacement to meet overall objectives.

6) Define constraints and limitations of expandability to multiple missions with various orbits in line with MOSRD requirements.

The Contractor shall prepare a development roadmap that defines the plans and priorities for establishing an initial baseline capability for the Mission Operations Services and incremental buildup of capability for the CCOR-3 Monitoring system. The Contractor shall identify design modifications required to evolve the SWO-MOS capability for CCOR-3 health monitoring. The Contractor shall present the roadmap and plan for modifications in a Contractor-hosted Design Modification Review (DMR) for assessment by a Government-designated board. The DMR shall satisfy PDR and CDR requirements as specified in the SWO-MOS CDRL.

3.3 Deploy Operational and Backup Solution Instances

The Contractor shall deliver the SWO-MOS Solution to meet MOSRD TO-2 requirements to Government facilities.

3.4 Deploy Solution Instances to Support Interfacing Developments The Government together with ESA will develop Vigil flight and ground elements external to the SWO-MOS. In the course of these developments, the elements will require functional and interface testing with the Solution.

· The Contractor shall prioritize capabilities and functions necessary to support the development, integration, and test requirements and schedules of external elements.

· The Contractor shall make instances of the Solution available with capabilities to support instrument end-to-end testing after installation on observatory.

· The Contractor shall make instances of the Solution available with capabilities to support SWGS Product Services development and test.

· The Contractor shall make instances of the Solution available with capabilities to support ESA telemetry interface development and test.

3.5 Sustain All Solution Instances

The Contractor shall sustain the SWO-MOS Solution for TO-2 at factory and Government facilities. Sustainment shall include activities to enhance, modernize, and address obsolescence. Sustainment shall include performing or responding to regular security scans with expedited security patching for all high vulnerability findings and at least quarterly security updates for all other findings. Sustainment activities shall extend the life of the Solution and improve its capabilities, reliability and robustness, leverage technology advancements, or reduce life cycle costs

4 Deliverables The Contractor shall develop and deliver all documents in accordance with the CDRL document and the L5 Project Review Plan or as modified under the Contractor’s document delivery plan. The following table lists selected L5 CCOR-3 lifecycle reviews as of the issuance of this Task Order that are most relevant to this Task. Changes to this schedule are at the Government’s sole discretion and will effectively result in changes to this task.

Table 1. L5 CCOR-3 capability Builds and Releases aligned to Milestone Reviews

Factory Baseline

12/15/2026

Features to simplify the configuration; fix discrepancies; and implement new features identified in Project MUCR and DMR

3/15/2027

MOST Access for MOCI Development

6/15/2027

9/15/2027

12/15/2027

3/15/2028

6/15/2028

9/15/2028

12/15/2028

03/15/2029

06/15/2029

09/15/2029

12/15/2029

18 months ahead of launch, NSOF Government site Solution install; Solution includes all features necessary to support End to End Testing

CBU Government site Solution install with failover capability demonstrated; Solution includes all features necessary to support End to End Testing

3/15/2032 image2.png image1.png image3.png