draft SWGS Mission Operations Services SOW.pdf

DRAFT

Effective Date: TBD

Expiration Date: TBD + 5 years

NESDIS

Office of Space Weather Observations

(SWO)

Space Weather Ground Services Mission Operations Services (SWGS-MOS)

Statement of Work (SOW)

U.S. Department of Commerce (DOC)

National Oceanic and Atmospheric Administration (NOAA)

National Environmental Satellite, Data, and Information Service (NESDIS)

SWGS MOS Base IDIQ Statement of Work <Doc ID> Rev-ii

Space Weather Ground Services Mission Operations Services (SWGS-MOS)

Statement of Work Review/Signature/Approval Page

Prepared by:

John Bristow SWGS Mission Operations Services Manager

Reviewed by:

TBD

SWO Contracting Officer’s Representative

NOAA/NESDIS/SWO

Susan Jacobs SWGS Lead Ground Systems Engineer (Acting)

Approved by:

Richard Ullman Space Weather Ground Services Manager (Acting) iii

Preface

This document provides the base Indefinite Delivery / Indefinite Quantity (IDIQ) SOW for the Space Weather Ground Services Mission Operations Services (SWGS-MOS) contract. It is under SWGS configuration control. Once this document is approved, changes are handled in accordance with Class I and Class II change control requirements as described in the SWGS Configuration Management Procedures, and changes to this document will be made by complete revision.

Any questions should be addressed to:

SWO Configuration Management Office

NASA/GSFC

Code 490.0 Greenbelt, MD 20771 iv

Change History Log

Revision Effective Date Description of Changes

(Reference the CCR & CCB/ERB Approval Date) v

Table of Contents

1 INTRODUCTION

1.1 NESDIS Overview

1.2 Space Weather Observations Programs

1.3 Space Weather Ground Services

1.4 Scope

1.5 Terms and Definitions

2 RELATED DOCUMENTATION

2.1 SWO Glossary and Acronym Document

2.2 Applicable Documents (TBR)

2.3 Information Documents

3 CONTRACT-WIDE REQUIREMENTS

3.1 Project Management

3.1.1 Business Management

3.1.2 Subcontract Management

3.1.3 Scheduling

3.1.4 Deliverables

3.1.5 Project Information Technology Management and Access

3.1.6 Customer Communications

3.1.7 Post-Award Conference ............................................. Error! Bookmark not defined.

3.1.8 Personnel and Facility Access

3.1.9 Project Management Status Reviews and Reports

3.1.10 Integrated Product Team Participation

3.1.11 Property Management

3.1.12 Capability Maturity Model Integration (CMMI)

3.1.13 Cloud Services

3.2 Risk Management

3.3 Configuration Management

3.4 Systems Engineering

3.4.1 Systems Engineering Management

3.4.2 Requirements Management

vi

3.4.3 Interface Requirements Specifications

3.4.4 Integration and Test

3.4.4.1 Factory Integration and Test

3.5 Information Security

3.6 Mission Assurance

3.6.1 Safety

3.6.2 Quality Assurance

3.6.3 Software Assurance

3.6.4 Reliability, Maintainability, and Availability

3.6.5 Materials and Processes Control Plan

3.6.6 Electrostatic Discharge Control Plan

3.6.7 Failure Modes and Effects Analyses and Critical Item List

3.6.8 Probabilistic Risk Assessment Inputs

3.6.9 Verification Tracking Log

3.6.10 Pre-Mishap Plan

3.7 Design and Implementation

3.7.1 Lifecycle Reviews

3.7.2 Scaled Agile Framework Enterprise (SAFe)

3.7.3 Agile Release Train (ART) Structure

3.7.4 The Systems Architect

3.7.5 SAFe Product Manager (PM) and Product Owner (PO) Representation

3.7.6 Contractor Responsibilities for Government Engagement in SAFe Events

3.7.7 Clone and Own Baseline Approach

3.7.8 Hardware Design and Construction

3.7.9 Software Design and Implementation

3.7.10 Additional Requirements

3.8 Site Installation and Test Coordination

3.8.1 Pre-Ship Review(s)

3.8.2 Site Preparation and Installation

3.8.3 Test and Integration

3.8.4 Release Readiness Reviews

vii

3.8.5 Ground Integration Testing

3.8.6 Ground Segment Tests

3.8.7 End-to-End System Tests

3.9 Transition To Operations

3.9.1 Operator and Other Training

3.9.2 Transition Support

3.9.3 Post-Launch Test

3.10 Maintenance

3.10.1 Hardware Maintenance

3.10.2 Software/Firmware Maintenance

3.11 Logistics Support

3.12 Sustainment

3.12.1 Work Request (WR) Process

3.12.2 Deployed System Support

3.12.3 Factory Reach-back and On-call Support

3.12.4 Factory Environments

3.13 Special Studies

4 CONTRACT TRANSITION

5 ABBREVIATIONS AND ACRONYMS

List of Tables

Table 1: Program and Project Events

List of Figures

Figure 1: SWGS Mission Architecture

Figure 2: Nominal Baseline Ground Services Block Diagram

Figure 3: Requirements Flow from Project to SGWG MOS Solution

Figure 4: Release Integration and Test Process

INTRODUCTION

1.1 NESDIS Overview

The National Oceanic and Atmospheric Administration (NOAA) mission is to understand and predict changes in climate, Earth, atmosphere, oceans and coasts, and space weather to share that knowledge and information with others for the protection of life and property, as the Nation’s authoritative source for environmental data.

The National Environmental Satellite, Data, and Information Service (NESDIS) supports NOAA’s mission of Science, Service, and Stewardship through satellite missions, data centers, data and information products and services. It is an end-to-end responsibility that underpins NOAA’s value to the Nation. The United States depends on NOAA to provide satellite data and imagery for meteorological forecasts, space weather warnings and alerts, and emergency services to support continuity of Government. NESDIS is responsible for the collection and provision of the critical satellite observations of Earth and the Earth/Sun system, and other essential environmental information needed for disaster preparedness, all hazards response and recovery and the protection of the Nation’s critical infrastructure and natural resources. These products and information enable services used in preparation for events that impact our climate, weather, oceans, daily lives, and national safety and provide essential information for national, regional, and local planners and officials.

1.2 Space Weather Observations Programs

The Office of Space Weather Observations (SWO) under NESDIS is responsible for advancing space weather observational leadership to meet NOAA programmatic needs. SWO currently is responsible for management of the Space Weather Follow-On (SWFO) program and the Space Weather Next (SWX) program, the latter of which is a loosely coupled program charged with developing and deploying space-based observational architecture to maintain space weather environmental observation continuity and to and extend space weather observations from all applicable orbits. These include observations on the Sun-Earth-Line (SEL) at Lagrange-Point 1 (L1), Geosynchronous orbit (GEO), Low Earth Orbit (LEO), and other orbits such as highly Elliptical Orbits (HEO). SWO projects will also collect space weather observations Off-SEL including at Lagrange Point 5 (L5) and other locations in the Heliosphere.

On the Sun-Earth line, SWO is developing and deploying a series of Space weather Observatories at Lagrange point 1 (SOL). The first of these observatories is built as SWFO-L1.

The next two observatories planned are part of the SWO L1 Series project are designated L1-A and L1-B. The L1 Series L1-A is planned to be launched in mid-2029 and the L1-B may launch in 2032. Each will be operated in a Lissajous orbit around Sun-Earth Lagrange point 1. Each observatory will host up to six observing instruments. The SOL observatories have a design life of five years and are planned to have five additional years of consumables at end-of-design-life.

Each observatory will collect the full set of NESDIS-required L1 measurements at the required cadence. SWO observation availability requirements require concurrent operation and management of a minimum of two spacecraft. SWO mission operations services will provide the full suite of satellite operations and observatory management for the SOL observatories.

SWO also has begun planning for a series of geosynchronous satellites (SWX GEO Series) to maintain and extend continuity of the space weather observations that have been established under the Geostationary Operational Environmental Satellites (GOES). The first of the SWX GEO Series may launch in 2032. Two GEO Series satellites are envisioned to operate concurrently, in orbital locations similar to NOAA’s GOES observatories. SWO intends that the SWGS Mission Operations Services will provide the full suite of satellite operations and observatory management for the SWX GEO observatories.

SWO also will build instruments to be hosted by partner satellites to collect space weather measurements in other orbits. The first of these is a compact coronagraph provided by SWO to fly on the European Space Agency (ESA) Vigil mission OFF-SEL at Lagrange L5. SWO project will develop instruments such as particle detectors, auroral imagers to be flown as hosted instruments on partner space platforms in various orbits. SWGS Mission Operations Services will receive the NOAA instrument data from hosting partners, will support instrument operations by the host and will process the observations into space weather products.

Error! Reference source not found. below depicts the total envisioned SWO observing architecture.

Figure 1: SWGS Mission Architecture

1.3 Space Weather Ground Services

SWGS is responsible for ensuring a consistent space weather ground services approach across the loosely-coupled SWO programs and consistent with broad NESDIS Ground Enterprise objectives to satisfying individual project mission requirements and milestones. SWGS will use

NOAA institutional facilities and leverage common SWO services, NOAA agency services, and partner agency and commercial services where they are available and as they are shown to meet mission requirements.

The SWGS is responsible to provision comprehensive ground services for all SWO projects, ensuring successful implementation and operation of space assets and ensuring the continuity of space weather measurements used by NOAA. SWGS strives to optimize the use of resources and services, aiming to balance efficiency and cost-effectiveness of service provision with a primary emphasis on maintaining schedules necessary for project success. Timely delivery is essential, ensuring that services are deployed, integrated, and tested promptly to support each project’s goals.

NESDIS is working towards a comprehensive NESDIS Ground Enterprise (NGE) architecture, evolving from a heritage of purpose-built single-mission systems towards consolidated, services-based multi-mission systems with common core capabilities. In a step toward that eventual goal, the SWFO-L1 mission command and control systems were implemented as an extension of the GOES-R series ground segment mission operations architecture. Future SWGS Mission Operations Services capabilities will similarly leverage Government infrastructure and capabilities.

Ground services are divided into three major service categories: Antenna Services, Product Services, and Mission Operations Services.

Antenna Services encompass the provision of space-ground communication and radiometric tracking services at distributed ground entry points, also known as ground stations. SOL satellites will continuously downlink space weather measurements. Global Antenna Services will be provided by a combination of NOAA ground antennas, commercial antenna service providers, and other U.S. Government assets and partners.

Product Services encompass the processing of science data into higher-level products suitable for use by operational services such as the National Weather Service, as well as the generation of retrospective products suitable for research and science. Product Services includes the associated functions of science data ingest, storage, dissemination, archive, and stewardship.

Mission Operations Services encompass observatory health and status monitoring and trending, command and control, orbit and attitude management, mission planning, contingency operations, and anomaly recovery. Capabilities must support from observatory development, testing, and other pre-launch activities through launch, operations, and decommissioning. Mission Operations Services also processes raw science data to level 0 to send to Product Services. In operation of the observatories, Mission Operations Services has interfaces with both Antenna Services and Product Services.

SWGS Mission Operations Services will be built and operated within the NOAA Satellite Operations Facility (NSOF) and the NOAA Consolidated Backup (CBU) facility and will be incorporated within the NOAA5050 Information Technology (IT) Security boundary that is maintained by NESDIS Office of Satellite and Product Operations (OSPO).

Mission Operations Services will leverage components of the existing NESDIS enterprise to the greatest extent appropriate, including but not limited to use of OS/COMET® for telemetry and command, the NASA Attitude Ground System (AGS) for attitude computation and management, and the NASA General Mission Analysis Tool (GMAT) an open-source package for orbit determination solutions, maneuver planning, and related functions.

1.4 Scope

This document defines the base Indefinite Delivery / Indefinite Quantity (IDIQ) Statement of Work (SOW) for development and long-term sustainment of mission operations services for the Space Weather Observations (SWO) programs. The goal of the contract is to manage the development and sustainment of the SWGS-MOS.

SWGS-MOS will evolve the current SWFO-L1 mission operations architecture into a true multi-mission operations service architecture to support all SWO space weather environmental observations.

SWO will deploy environmental monitoring instruments on NESDIS satellite observatories.

NOAA will be responsible for operation of these satellites and for ensuring that NOAA instrument data are processed to higher-level space weather products per stringent latency and availability requirements. This contract will provide development of the SWGS Mission Operations Services capabilities to support these observatories.

NOAA may partner with external organizations to provide NOAA environmental monitoring instruments to be hosted on partner missions. In such cases, NOAA retains the responsibility and ownership of the instrument, and does not have responsibility for the satellite observatory. This contract will provide development of the SWGS MOS capabilities to support these instruments including for example: establishing interfaces to receive instrument engineering telemetry for monitoring and trending and to exchange data to support the partner in mission operations related to instrument commanding.

The first observatory project of the SWX program is the L1 Series described above. A block diagram showing SWGS MOS in the context of the L1 Series is shown in Error! Reference source not found. below. This same architecture must be extensible and scalable with minimal modification to support potential future satellite series and instruments. The first hosted instrument is expected to be the Vigil L5 project partnership with the European Space Agency (ESA), planned to launch by 2031.

The SWGS MOS will:

Provide a capability for NOAA and NOAA-affiliate operations staff to operate SWO observatories during all mission operations phases.

Provide a capability for NOAA and NOAA-affiliate operations staff to monitor SWO instruments and to support the operations of hosted instruments flown and operated by NOAA partners.

Be designed and implemented for capacity growth. By launch of the first L1 Series observatory, provide capacity to operate at least two observatories at L1 simultaneously. Be able to scale without redesign to provide commensurate simultaneous operational capacity as additional observatories are defined and brought into service.

At the time of the ESA Vigil mission launch, provide capacity to support the CCOR-3 instrument hosted on the Vigil satellite with instrument monitoring and trending. Be able to scale without fundamental redesign as additional SWO instruments are developed and hosted on external organization spacecraft. Over the period of performance of this contract the Government may exercise options to add requirements for additional host partnerships.

Interface with the SWGS Antenna Services to plan and obtain Telemetry, Tracking, and Command services.

Interface with SWGS Product Services to deliver level 0 science data and auxiliary data for higher-level product generation by NOAA.

Interface with partner agencies that host NOAA instruments to obtain housekeeping and instrument science data.

Host simulators of NOAA satellites for pre-launch and post launch operations use.

Provide test instances and interfaces to support pre-launch communications with the observatory during observatory development, integration, test, and mission rehearsals.

Provide test instances to support development and evolution of antenna services or product services as required.

Figure 2: Nominal Baseline Ground Services Block Diagram

This SOW defines the tasks to design, develop, analyze, fabricate, assemble, integrate, checkout, test, evaluate, verify, deliver, transition, document, and support development, operations, sustainment, and maintenance of SWGS MOS and interfaces. This SOW also specifies activities required to support Government verification and acceptance of Contractor implementations and integration with all other SWGS services.

Work locations for this contract include, but are not limited to:

NOAA Satellite Operations Facility (NSOF) in Suitland, MD Wallops Command and Data Acquisition Station (WCDAS) in Wallops, VA Consolidated Backup Facility (CBU) in Fairmont, WV Contractor Facility

1.5 Terms and Definitions

The following terms and definitions are used throughout this SOW.

The term “applicable documents” denotes Government-prepared and controlled documents and industry standards documents that levy additional requirements on the Contractor. The Contractor is required to comply with the documents, or the tailored version of the documents provided by the Government.

The term “reference documents” denotes documents that amplify or clarify the information presented in this document, and the Contractor is not required to meet any requirements listed within these documents.

The term “(CDRL)” refers to the Contract Data Requirements List (CDRL) of enumerated deliverables. References in the format of [xx-##] (e.g., [SE-01]) within this document correlate with the data items listed in the CDRL document.

The term “shall” indicates a contract requirement. The term “must” indicates a required condition. The terms “will”, “are”, and “is” designate statements of fact.

The term “(TBS)” is an acronym for “to be supplied” and identifies missing or incomplete information, values, or data needed to fulfill a requirement.

The term “(TBD)” is an acronym for “to be determined” and identifies a missing requirement.

The term “(TBR)” is an acronym for “to be refined/reviewed” and identifies requirements that are subject to review for appropriateness and subject to revision.

The term “(GFP/GFI)” is an acronym for “Government-Furnished Property/Government Furnished Information” and refers to any Government-furnished hardware, facilities, information, or other resource provided by the Government for use in the SWGS MOS.

Government-furnished property means property in the possession of or acquired by the Government and subsequently furnished to the Contractor for performance of a contract.

Government-furnished property includes, but is not limited to, spares and property furnished for repair, maintenance, overhaul, or modification. Government-furnished property also includes Contractor-acquired property that is a delivered under a contract and accepted by the Government for use under the contract.

The term “C” or “CTR” refers to the Contractor.

The term “G” or “Gov” means the federal Government.

The term “Government” and “Government personnel” mean federal Government employees.

The term “Government representatives” means personnel designated by the Government to perform work related to this contract or interface with the deliverables of this contract. These personnel include federal Government employees, Support Contractors, Government stakeholders, and personnel of Government-affiliates and Government partner organizations.

The term “Support Contractors” means Systems Engineering and Technical Assistance (SETA) support Contractors, Federally Funded Research and Development Center (FFRDC) employees, and Government Cooperative Institutes and Grantee employee.

The term “Solution” includes the total scope of SWGS MOS architecture and functionality developed, sustained, or maintained under this contract.

The term “Development” means the process of defining, designing, testing, and implementing new software applications. These efforts, further defined below are the basis of Solution creation, implementing its capabilities, reliability and robustness, leverage technology advancements including agile and cloud as appropriate.

The term “Sustainment” means activities performed to develop, modernize, or enhance the SWGS-MOS after delivery to the Government, including addressing obsolescence. Sustainment is conducted to extend the life of the Solution and improve its capabilities, reliability and robustness, leverage technology advancements, or reduce life-cycle costs. These activities may include:

Developing, integrating, testing, and implementing new or improved telemetry processing or application capability, or a new sub-component.

Enhancing operations by improving components or capabilities.

Adding new capabilities to meet NOAA requirements to provide the best return on investment.

Addressing life cycle issues, including the impacts of aging spacecraft hardware and spacecraft anomalies, and the impacts of the gain or loss of data sources to maintain the highest quality (most accurate) products and services.

Upgrading to new versions of Commercial Off-the-Shelf (COTS) software and hardware.

Installing and enabling new enterprise tools.

The term “Maintenance” means activities that are performed to ensure the continued operation of the SWGS-MOS after transition to operation. Maintenance ensures that the SWGS-MOS continues to meet technical, functional, and performance requirements in addition to availability and reliability requirements. Maintenance also ensures a continuation of the security posture and controls.

RELATED DOCUMENTATION

The latest versions of all documents listed below should be used. SWGS documents have a document identifier starting with SWGRDS indicating the governing Configuration Control Board (CCB) that has the control authority of the document.

1.6 SWO Glossary and Acronym Document

The SWO Glossary and Acronym Document (SWO-MGMT-SPEC-0001) defines terminology as used in this document and throughout the SWO. 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.

1.7 Applicable Documents (TBR)

Below are documents applicable to this SOW. In the event of conflict between an Applicable Document and the content of this document, the SWGS Configuration Control Board has the final authority for conflict resolution.

Document Number Applicable Document Title

TBS SWGS Mission Operations Service Requirements Document

TBS SWGS Mission Operations Service Contract Data Requirements List

TBS SWGS Mission Operations Service Government-Furnished Property (GFP) and Government-Furnished Information (GFI) List

TBS SWGS Mission Operations Service to Antenna Services Interface Requirements Document

TBS SWGS Mission Assurance Requirements

TBS SWGS Work Breakdown Structure and Dictionary

SWGS-MGMT-PLAN-

SWGS Risk Management Plan

TBS NESDIS Common Cloud Framework (NCCF) Ingest and Dissemination Interface Control Document

Department of Defense, Defense Research and Engineering Technology Readiness Assessment (TRA) Deskbook, July 2009

NOAA Cybersecurity Standard: POA&M Management Process

NPR 7150.2D NASA Software Engineering Requirements

GSFC-STD-1001

Version A

Criteria for Flight and Flight Support Systems Lifecycle Reviews

NPR 7123.1D NASA Systems Engineering Processes and Requirements

Document Number Applicable Document Title

NIST-SP-800-53

Revision 5

Security and Privacy Controls for Federal Information Systems and Organizations

FIPS PUB 199 Federal Information Processing Standards for Security Categorization for Federal Information and Information Systems

FIPS PUB 200 Minimum Security Requirements for Federal Information and Information Systems

NIST-SP-800-37 Risk Management Framework for Information Systems and Organizations

Department of Commerce (DOC) Enterprise Cybersecurity Policy, September 2022

DoD 5220.22-M National Industrial Security Program Operating Manual (NISPOM), February 28, 2006

212-1301 NOAA IT Security Manual

1.8 Information Documents

The following documents amplify, clarify, or provide context for the information presented in this document. These documents are not binding on the content of this document.

Document Number Information Document Title

SWO-MGMT-SPEC-

SWO Glossary and Acronym Document

CONTRACT-WIDE REQUIREMENTS

The Contractor shall provide all management and engineering services, personnel, materials, and equipment, not otherwise listed in the SWGS Mission Operations Services GFP/GFI List, necessary to design, analyze, validate, develop, fabricate, assemble, integrate, checkout, test, evaluate, verify, deliver, transition, document, and support operations and maintenance of the SWGS Mission Operations Service Solution and its interfaces in accordance with this SOW, the SWGS Mission Operations Services IRDs, the SWGS Mission Assurance Requirements (GMAR) (Doc# TBD), documents specified in individual task SOWs, and applicable documents specified in Section 1.7.

1.9 Project Management

The Contractor shall establish and maintain a management structure responsible for overall project control to assure all requirements of this contract and attachments are accomplished within cost and on schedule.

The Contractor shall perform project management functions described in the Project Management Plan [PM-01] that are necessary to execute the total effort required by this contract.

The Contractor shall designate a Project Manager to manage day-to-day activities and to act as the primary interface with the Government's Contracting Officer's Representative (COR).

The Contractor shall provide the Project Manager sufficient corporate authority to assure that the contract cost, schedule, and technical requirements are fully met.

The Contractor shall follow an Earned Value Management System (EVMS) and provide the related EVMS Plan [PM-11].

The Contractor shall execute an Integrated Baseline Review (IBR) and provide an IBR Data Package [PM-12].

1.9.1 Business Management

The Contractor shall effectively administer the contract and manage contract costs.

The Contractor shall establish, implement, and maintain a comprehensive Resource Management System (RMS) for planning, authorizing, and controlling the total resource effort for each Work Breakdown Structure (WBS) element and for providing timely and adequate visibility into labor, materials, cost, schedule, travel, and subcontract performance delivered in a Contract Performance Report (CPR) [PM-10]

The Contractor shall deliver the Contract Work Breakdown Structure (CWBS) [PM-13] once it is baselined and after any significant changes due to project changes or contract modifications.

The Contractor shall assure that the RMS is consistent with the CWBS, provide timely and traceable incorporation of contract changes, and document the effect of changes on the resource management baseline.

Significant changes to the baseline must be approved by the COR. For the purposes of this section, “significant changes” means a change which alters either the Total Director Hours

(prime and subcontractor) and/or Total Estimated Cost for a Level 3 WBS by plus or minus 5 percent. Formats for baseline changes are described in the Financial Reports [FM-01].

The Contractor shall deliver monthly financial reports per the format and content described in the Financial Reports [FM-01].

The Contractor shall deliver monthly financial reports (formats 1, 2, and 5 of the MPM Contractor Performance Report) no later than the 30th day after the close of the reporting period.

The Contractor shall deliver cost baseline data as part of each PMSR delivery [PM-04] in PowerPoint format.

1.9.2 Subcontract Management

The Contractor shall be responsible for performance, including the technical, cost, and schedule performance, of all subcontractors.

The Contractor shall provide technical and management oversight and status reporting for subcontract activities.

The Contractor shall ensure requirements from this SOW, the MOSRD, IRDs, CDRL, MAR, and applicable documents are flowed down to the subcontractors.

1.9.3 Scheduling

The Contractor shall establish an Integrated Master Schedule (IMS) [PM-03] consistent with the Contractor’s RMS to manage and report the project schedule.

The Contractor shall ensure that the IMS includes the events identified in the applicable project Lifecycle Review Plans and also include events listed in Table 1 below:

Table 1: Program and Project Events

Event [4] Date

Establishment [1] Date

Control [2] Event

Approval [3]

Post Award Conference NLT Contract Award + 2 months

C G

SWGS Mission Operations Service Requirements Initial Review

NLT Contract Award + 6 months

C G

Release Pre-ship Reviews Dates per Release C G

Release Readiness Reviews Dates per Release C G

SWGS Mission Operations Service Requirements Modification Reviews

Dates per Task C G

GFP/GFI Delivery and Acceptance events

Dates per Task G G/C

Design Modification Reviews Dates per Task C G

Project Lifecycle Reviews Dates per Task G G

Event [4] Date

Establishment [1] Date

Control [2] Event

Approval [3]

Mission Operations Tests Dates per Task G G

Ground Readiness Tests Dates per Task G G

Mission Rehearsals Dates per Task G G

Training Events and Activities Dates per Task G G/C

Security Tests Dates per Task G G

[1] Dates not specified by the Government shall be established by the Contractor.

[2] All dates not specified as Government-controlled are under Contractor control.

[3] Event approval indicates which events are subject to Government approval. All other events approvals are left to the Contractor. For events not requiring Government approval, supporting documentation and Government review may be required.

[4] For multiple deliveries, per Release or per Task, the events listing shall apply to each delivery as appropriate.

1.9.4 Deliverables

The Contractor shall prepare and conduct a Post-Award Conference (PAC) within two months after contract award to review of the contract schedule and clauses, SOWs, MOSRD, MSRDs, IRDs, WBS, MAR and CDRL.

The Contractor shall provide deliverables as required by this SOW, the CDRL list, and each Task Order SOW.

The Contractor shall provide data and documentation deliverables in accordance with the SWGS Mission Operations Services CDRL (Doc# TBD).

The Contractor shall not use any GFP/GFI provided or acquired under this contract for any purpose other than in the performance of this contract. The Government will document GFP/GFI in the SWGS Mission Operations Services GFP/GFI List (Doc# TBD).

1.9.5 Project Information Technology Management and Access

The Contractor shall provide a Program Security Administrator who is knowledgeable in the Government’s requirements for public trust programs.

The Contractor shall provide the information technology resources to perform all work required by this contract.

The Contractor shall work with the Government to define mutually agreeable processes for protected email, transmission of Contractor, subcontractor, and vendor proprietary data, International Traffic in Arms Regulations (ITAR)/ Export Administration Regulations (EAR) Controlled information and Controlled Unclassified Information (CUI). The Government will define the interfaces and processes for delivery of CDRL data items.

The Contractor shall provide appropriate SAFe tool and process privileges to Government representatives to enable customer/stakeholder insight and feedback on content such as user stories, design documents, test plans, and retrospective reports throughout the development process.

The Contractor shall support the configuration management and exchanging of documentation and the Government review processes specified in this contract.

1.9.6 Customer Communications

The Contractor shall provide administrative support for reviews and meetings with Government representatives related to the work of this contract conducted at the Contractor's facility. Reviews and meetings will be held at the Contractor's facilities unless otherwise requested by the Government.

The Contractor shall provide, use, and maintain video conferencing, telephone conferencing, and internet conferencing at the Contractor's facilities for reviews and meetings with Government representatives related to the work of this contract.

The Contractor shall record and make available Meeting Minutes [PM-07] for reviews and meetings with Government representatives related to the work of this contract.

1.9.7 Personnel and Facility Access

The Contractor shall ensure unencumbered non-escort access by the Government and Government support personnel to all Contractor and subcontractor facilities where program work is performed.

The Contractor shall allow Government representatives to bring Government or Government-affiliate-owned computers, laptops, and smartphones, into and out of Contractor and subcontractor facilities where program work is performed.

The Contractor shall provide the training for the visiting Government representatives if required for entry into Contractor and subcontractor facilities where program work is performed.

1.9.8 Project Management Status Reviews and Reports

The Contractor shall prepare, deliver, and brief monthly Program Management Status Review (PMSR) data packages for the purpose of reviewing the technical, risk, schedule, and cost status of the contract [PM-04].

The Contractor shall hold the first PMSR no later than sixty (60) days after contract award and monthly thereafter at a location coordinated between the Government and the Contractor.

1.9.9 Integrated Product Team Participation

The Contractor shall participate in IPTs as directed. The Government may form Integrated Product Teams (IPTs) consisting of Government agency staff and affiliate representatives including support Contractors, and partner agencies as well as participants from the user community; the Contractor and relevant subcontractors; and any necessary vendors to provide decisions and recommendations for complex technical and programmatic issues.

1.9.10 Property Management

The Contractor shall develop and use a Property Management Plan [PM-09] to identify and account for Government property in the possession of the Contractor from the time the property is acquired until it is formally delivered.

1.9.11 Capability Maturity Model Integration (CMMI)

The Contractor shall be registered with Information Systems Audit and Control Association (ISACA) as Capability Maturity Model Integration (CMMI) CMMI Maturity Level 3 or higher.

The Contractor shall deliver a plan, within 30 days of contract award, to achieve CMMI certification.

The Contractor shall achieve CMMI certification within twelve (12) months of contract award.

1.9.12 Cloud Services

The Contractor shall use only Government-approved contract vehicles to procure cloud services.

The Contractor shall define, plan, document, implement, test, and verify all cloud implementation requirements.

The Contractor shall coordinate with the cloud provider, and monitor (via metrics) cloud performance and provide such reports to the Government upon request.

1.10 Risk Management

The Contractor shall establish, implement, and maintain a Risk Management (RM) System for identifying, analyzing, planning, tracking, controlling, and communicating the risks associated with program safety, cost, schedule, and technical performance.

The Contractor shall develop the risk management process (that includes integrated risk management planning) to be consistent with the Space Weather Next Program Risk Management Plan (TBD).

The Contractor shall document the specific implementation of the continuous RM process in a Risk Management Plan [RM-01], to be maintained by the Contractor.

The Contractor shall establish a Risk Management Board in accordance with their Risk Management Plan and include Government representation on that board.

The Contractor shall develop and maintain a Risk List [RM-02] (e.g., database or spreadsheet), throughout the contract period of performance, listing all risks along with potential impacts to the program/projects.

The Contractor shall prioritize the Risk List to indicate which risks have the highest probability, which have the highest consequences, and which risks represent the greatest threat to mission success.

The Contractor shall inform the Government of all identified risks as part of the RM process.

The Contractor shall provide status of the items on the Contractor Risk List in the PMSR [PM- 04].

The Contractor shall obtain Government concurrence for risk acceptance or closure of items in the Contractor Risk List.

The Contractor shall retain due date, status information, and justification for acceptance or final closure, and date closed in the Contractor Risk List.

1.11 Configuration Management

The Contractor shall develop, deliver, and maintain a Configuration Management Plan [CM-01] that describes the approach for control and management of:

a. All Solution project and engineering documentation

b. Mission Operations Data Base (MODB) configuration items (e.g., spacecraft command procedures, the Observatory Command and Telemetry Database, and Flight Software)

c. Solution hardware/firmware/software baseline

d. Solution configuration items

e. Control, management, and reporting/notification of anomalies.

f. Help Desk

g. System History Accounting and Auditing

h. Software License Management

The Contractor shall follow NESDIS operational configuration management processes for all modifications to the Solution operational baseline and for Solution deliveries to operational locations.

The Contractor shall describe in its Configuration Management Plan [CM-01] the transition process from any Contractor-controlled CM and anomaly tracking tools and processes and Government-controlled operational CM and anomaly tracking tools and processes.

The Contractor shall provide Government representatives with remote access to any Contractor-controlled CM or anomaly tracking systems beginning at contract award.

The Contractor shall make configuration-controlled items available to Government representatives for the purpose of support to interface integration, test, maintenance, and support responsibilities.

The Contractor shall ensure vendors with access to the Contractor-controlled CM or anomaly tracking systems will not have access to information or data that is considered proprietary to another vendor.

The Contractor shall provide training on any Contractor-controlled CM or anomaly tracking systems for Government-representatives.

The Contractor shall develop, deliver, and maintain a baseline Document Tree [CM-02], and a baseline Drawing Tree [CM-03].

The Contractor shall establish a Contractor-controlled CCB, associated with any Contractor-controlled CM process, to review and approve changes to the Solution hardware and software and controlled documents.

The Contractor shall include non-voting Government representatives on any Contractor CCBs.

The Contractor shall make Contractor-controlled Configuration Control Board (CCB) Documentation [CM-06] available for review by Government representatives.

The Contractor shall make the Configuration Item Identification List [CM-05] available for review by Government representatives.

The Contractor shall generate, accept, disposition, and maintain Configuration Change Requests (CCRs) [CM-07] for requested modifications to documents and drawings under CM.

The Contractor shall identify and obtain Government approval for Class I changes.

The Contractor shall re-categorize a Class II change to Class I if so, directed by the Government.

The Contractor shall participate in Government CCB processes including providing technical inputs regarding actions coming before Engineering Review Boards (ERBs) and CCBs.

The Contractor shall configuration-manage received GFP/GFI items.

The Contractor shall manage Solution software licenses.

1.12 Systems Engineering

1.12.1 Systems Engineering Management

The Contractor must perform systems engineering and integration functions necessary to execute this contract, including supporting the requirements development, definition, design, integration, and testing of the Solution, the associated GFP/GFI within the Solution, and with all external interfaces (Antenna Services, Product Services, etc.).

The Contractor shall establish a comprehensive systems engineering program, described in the Systems Engineering Management Plan [SE-01].

The Contractor shall ensure that the systems engineering program is compliant with NASA Systems Engineering Processes and Requirements (NPR 7123.1).

The Contractor shall designate a chief systems engineer to conduct and coordinate day-to-day systems engineering activities, oversee implementation of the systems engineering program, and act as the technical interface with the Government's systems engineering group.

1.12.2 Requirements Management

The Solution functional and performance specifications are maintained in a document titled the Mission Operations Services Requirements Document (MOSRD) [SE-03]. This document is maintained as under Contractor configuration control. For each SWO project or IDIQ task, the Government will provide a project Mission Services Requirements Document (MSRD) that represents the requirements for a SWO project mission or Task Order. Additional requirements may be discerned through analysis of Solution objectives or constraints or may be revealed through the incremental development process. The figure below shows the relationship between project MSRDs and the SWGS MOSRD.

Figure 3: Requirements Flow from Project to SGWG MOS Solution

The Contractor shall define, implement, and maintain a requirements management system to capture, link, trace, analyze, and manage changes to the Solution requirements.

The Contractor shall prepare, maintain, and deliver the SWGS Mission Operations Service Requirements Document [SE-03], the Design Description Document [SE-07], the Operations Concept [SE-02], and the Mission Operations Database Design Descriptions [SE-13].

The Contractor shall perform studies and trades, including associated risk assessments and life cycle cost implications, characteristics of GFP/GFI, and external interfaces to derive requirements for the MOSRD.

The Contractor shall trace each MSRD and IRD requirement to the MOSRD with associated attributes to facilitate project and task-specific verification events.

The Contractor shall assess and document the comprehensive allocation of requirements to lower-level specifications, showing the up/down traceability of requirements including performance and design drivers, and explicitly identifying any derived requirements.

The Contractor shall perform systems analyses and systems engineering to define internal and external interface requirements/user stories and to validate interface design details.

The Contractor shall maintain a dynamic Solution Backlog that evolves based on architectural priorities, technical debt reduction, Solution performance enhancements, and adherence to architectural principles to ensure a robust and sustainable system design.

The Contractor shall use the MOSRD as a foundational document to derive User Stories for incorporation into the Solution Backlog within the SAFe framework.

The Contractor shall manage the Solution Backlog in collaboration with the Government to prioritize deliverables and ensure stakeholder satisfaction.

Requirements and Solution Backlog satisfaction is accomplished through User Story Acceptance Criteria. Once the User Story Acceptance Criteria are met the associated MOSRD requirements are provisionally satisfied.

The Contractor shall incrementally derive and/or refine User Stories derived from the MOSRD to enhance the Solution architecture, address technical challenges, improve performance, and ensure alignment with architectural objectives within each PI. New User Stories may reveal new requirements or modification of requirements. Upon Government approval, these changes will be incorporated into the MOSRD under the control of the Government CCB.

Regular Inspect and Adapt sessions will focus on evaluating architectural decisions, identifying opportunities for architectural and requirements enhancements, and ensuring that each iteration contributes to achieving the desired architectural outcomes.

The Contractor shall integrate regression testing into each phase of the PI and Sprint cycle to ensure that satisfied MOSRD requirements continue to be satisfied. Regression Test procedures, automated when practical, or otherwise manual will be exercised through development, feature testing, integration, and capability and system testing.

The Contractor shall also design tests demonstrating satisfaction of project MSRD requirements for a mission to be conducted by the Contractor and witnessed by the Government as part of launch readiness acceptance test milestones for that mission.

The Contractor shall produce and deliver verification artifacts as documentation that each project MSRD requirement is met.

1.12.3 Interface Requirements Specifications

The Contractor shall prepare and deliver the MOS External Interface Requirements Specification

[SE-04].

The Contractor shall prepare and deliver the Mission Operations Services to Enterprise Management Interface Requirements Specification [SE-06].

The Contractor shall use the GFP/GFI NESDIS Common Cloud Framework (NCCF) Interface Control Document to define the interface to SWGS Product Services hosted within the NCCF.

The Contractor shall prepare and deliver the Mission Operations Services to Antenna Services Interface Control Document (ICD) [SE-08].

The Contractor shall prepare and deliver the Mission Operations Services Internal Interface Control Document (ICD) [SE-10].

The Contractor shall prepare and deliver the Mission Operations Services Software Requirements Specification [SE-11].

The Contractor shall prepare and deliver the Mission Operations Services Software Design Description [SE-12].

The Contractor shall coordinate with observatory vendors for development of the space-to-ground ICDs.

The Contractor shall coordinate with the Government and external entities for development of ICDs to define any additional external interfaces.

The Contractor shall work with GFP/GFI vendors to coordinate interface, hosting requirements, testing procedures, and anomaly resolution for all GFP/GFI incorporated into the Solution.

The Contractor shall establish a SWGS Mission Operations Services Integration, Test, and Verification Plan [IT-01] documenting the overall SAFe verification and validation plan to include interfaces and integrated GFP/GFI software.

The Contractor shall develop and maintain procedures to validate that the Solution satisfies ICDs and meets user needs and to verify that the Solution meets all requirements described in:

SWGS MOSRD

Project MSRDs Interface Requirement Documents Solution Hardware and Software Implementation Specifications

MAR

The Contractor shall perform and document analyses of the data and information from the design, development, qualification testing, integration testing, and on-orbit testing using the Solution hardware and software that are required to ensure that the Government will meet mission specifications and objectives.

The Contractor shall map requirements to specific verification and validation activity details and results.

1.12.4 Integration and Test

The Contractor shall provide integrated plans, procedures, manuals, and other materials necessary for installation, integration, and test (I&T), verification, transition, and operations support for systems and services developed or deployed under this contract.

The Contractor shall work with Government-designated vendors, service providers, and system providers in coordination with the Government, to ensure that the Solution implemented under this contract operates correctly in installation, integration and test, verification, transition, and operations phases and that all interfaces are correctly documented in support plans, procedures, and manuals. The Release Integration and Test process is illustrated in Figure 3.

Figure 4: Release Integration and Test Process

The Contractor shall provide necessary hardware and software to accomplish integration and testing.

The Contractor shall be responsible for ensuring the performance and readiness of the Solution for operations and mission data distribution for each observatory prior to the respective launch freeze dates.

The Contractor shall identify, develop, and execute interface compatibility testing by working with GFP/GFI services, eternal interfaces, and vendors, in coordination with and as directed by the Government.

The Contractor shall identify, develop, and implement interface simulation requirements, data sets, and tools necessary to support design and development activities by working with GFP/GFI services and vendors, in coordination with the Government.

The Contractor shall ensure that the Integration, Test, and Verification Plan [IT-01] and Transition and Operations Support Plan [TO-01] are consistent and provide a complete set of activities necessary to deploy, install, and ensure readiness of the Solution to support operations for each observatory.

The Contractor shall incorporate Government-provided test data in their verification activities.

The Contractor shall provide test data for Contractor test and verification efforts when such data is not provided by the…