SWO-MOS PWS Base IDIQ KT.pdf

Effective Date: 02/26/2025

Expiration Date: 02/26/2030

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

SWGS-MOS-SOW-0001, Revision -

Space Weather Ground Services, Code 4 2.0

Space Weather Ob ervations

Mission Operations Serv ces

(SWO-MOS)

Base Perform ce Work S atement

U.S. Department of Commerce (DOC)

National Oceanic and Atmospheric Administration (NOAA)

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

National Aeronautics and Space Administration (NASA)

GSFC SWGS CMO

02/26/2025

Released

SW Reviewed – Not S ject to Export Control

DRAFT

SWO-MOS Base PWS SWGS-MOS-SOW-0001, Revision -

Effective Date: February 26, 2025 ii

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

Space Weather Observations

Mission Operations Services

(SWO-MOS)

Base Performance Work Statement

Review/Signature/Approval Page

Prepared by:

David Nguyen

Reviewed by:

Ava Afghahi

Susan Jacobs

Fiza Chaudry

Scott Schnee

Laura Dunlap

Maria Amaro

David Donovan

Brian Frey

Kenneth Jensen

Andrew Royale

Charles Zakrzwski

Katherine Spotz

Eric Tai

Approved by

Jill Taylor iii

Preface

This document provides the Base Performance Work Statement for the Indefinite Delivery /

Indefinite Quantity (IDIQ) for the Space Weather Observations Mission Operations ervices

(SWO-MOS) contract. It is under SWGS configuration control. Once this docum is approved, changes are handled in accordance with Class I and Class II change control req ements as described in the SWGS Configuration Management Procedures, and change his document will be made by complete revision.

Any questions should be addressed to:

SWGS Configuration Management Office

NASA/GSFC

Code 492.0

Greenbelt, MD 20771 iv

Change History Log

Revision Effective

Date

Description of Changes

(Reference the CCR & CCB/ERB Approval Da

Revision - 02/26/2025 Baseline Release following the approval of S GS-CCR-0005 v

Table of TBDs/TBRs/TBSs

Action Item

No.

Location Summary Indivi ual/

Org zation ctionee vi

Table of Contents

1 INTRODUCTION

1.1 NESDIS Overview

1.2 Space Weather Observations Programs Description

1.3 Space Weather Ground Services Overview

1.4 Scope

1.5 Places of Performance

1.6 Terms and Definitions

2 RELATED DOCUMENTATION

3 CONTRACT-WIDE REQUIREMENTS

3.1 Contract Type

3.2 Task Order Administration

3.3 Task Order Management

3.4 General

4 DELIVERABLES

4.1 Data Deliveries

4.2 Deliveries at Factory and Opera nal Sites

List of F ures

Figure 1: SWGS ission Arch Figure 2: Nominal elin round Services Architecture Figure 3: SWO-MOS irements Flow

1 INTRODUCTION

1.1 NESDIS Overview

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

The National Environmental Satellite, Data, and Information Service (N SDIS) sup rts

NOAA’s mission of Science, Service, and Stewardship through satellite missions, dat nters, data and information products and services. It is an end-to-end re nsibility that underp

NOAA’s value to the Nation. The United States depends on N AA to provide satellite data d imagery for meteorological forecasts, space weather warnin and alerts, and emergency servi to support continuity of Government. NESDIS is respon le for the colle tion and provision of the critical satellite observations of Earth and the Earth n system, an ther essential environmental information needed for disaster preparedn all haz s response and recovery and the protection of the Nation’s critical infrastructure and r esources. These products and information enable services used in preparation for events impact our climate, weather, oceans, daily lives, and national safety an rovide essential infor ion for national, regional, and local planners and officials.

1.2 Space Weather Observations Prog ms Descr

The Office of Space Weather Observations WO) und NESD esponsible for advancing space weather observational leadership to me NO programmatic needs. SWO currently is responsible for managem e Space Wea ollow-On (SWFO) program and the Space

Weather Next (SWx) gram, th atter of whi s a loosely-coupled program charged with developing and dep ying space-b d observatio l architecture to maintain space weather environmental o rvation contin y and to exten pace weather observations from all applicable orb These include se tions on the Sun-Earth-Line (SEL) at Lagrange point 1

(L1), geosynchro s orbit ( O), low t (LEO), and other orbits such as highly elliptical orbits (HE SW projects will also collect space weather observations Off-SEL including at Lagrange p t 5 (L5) and other locations in the Heliosphere.

O he Sun-E line, SW developing and deploying a series of observatories to be named pace weather O rvations a grange 1 (SOL). The first of these observatories is built as

SWFO-L1. The nex wo indepen ently-launched observatories planned are part of the SWx

SOL project are desig ted SOL-A and SOL-B. SOL-A is planned to be launched no earlier than

2029 and SOL-B no e ier than 2032. Each will be operated in a Lissajous orbit around Sun-th L1. Each obser ory will host up to six observing instruments. SWO mission operations ser s will provid he full suite of satellite operations and observatory management for the

SOL rvatori nd process the observations into level 0 space weather products.

SWO also egun planning for a series of space weather geosynchronous satellites (SWx

GEO Series) to maintain and extend continuity of the space weather observations that have been established under the Geostationary Operational Environmental Satellite (GOES) program. The first of the SWx GEO Series may launch no earlier than 2032. Two GEO Series satellites are envisioned to operate concurrently, in orbital locations similar to NOAA’s current GOES observatories. The Mission Operations Services will provide the full suite of satellite operations and observatory management for the SWx GEO observatories and process the observations into level 0 space weather products.

SWO will develop instruments such as particle detectors and auroral imagers to be flown as hosted instruments on partner space platforms in various orbits. Mission Operations rvices will support instrument monitoring sufficient to maintain awareness of SW instrumen atus and assist partner satellite operations center. SWO-MOS also may receive the NO A instrument data and telemetry from hosting partners or other SWGS elements and pro observations into level 0 space weather products, if not done so prior to receipt.

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

Figure 1: SWGS Mission Architecture

1.3 Space Weath Ground S vices Overview

SWGS is responsible r ensuring a consolidated space weather ground services approach across e loosely-coupled S O projects that is consistent with broad NESDIS Ground Enterprise

( E) objectives an mplemented to satisfy individual project mission requirements and mil nes. SWGS ll use NOAA institutional facilities and leverage common SWO services, NOAA ency ices, and partner agencies and commercial services where they are available and as th hown to meet mission requirements.

The SWGS is responsible for provisioning comprehensive ground services for all SWO projects according to the project requirements, 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 NGE architecture, evolving over the t decade from a heritage of purpose-built single-mission systems towards consolidated, se es-based multi-mission systems with common core capabilities. In a step toward that ev ual goal, the

SWFO-L1 mission command and control systems were implemented as an ion of the

GOES-R series ground segment mission operations architecture. Future M ssion rations

Services capabilities will similarly leverage appropriate Government i astructure capabilities.

Ground services are divided into three major service categorie Antenna Services, Produc

Services, and Mission Operations Services.

• Antenna Services encompass the provision of sp e-ground comm nication and radiometric tracking services at distributed grou ntry point so known as ground stations. Global Antenna Services will be provided a com nation of NOAA ground antennas, commercial antenna service providers, and U.S. Government assets and partners.

• Product Services encompass the sing of science data higher-level products suitable for use by operational ser ces s s the National W her Service Space

Weather Prediction Center, as well the gene of retrospec e products suitable for research and science. Product Servi includes t a ted functions of science data ingest, storage, dissemination, and ar ve ste rdship.

• Mission Operations S vices encompa ob rvatory health and status monitoring and trending, comm and trol, orbit an ttitude management, mission planning, contingency erations, an nomaly rec ry. Capabilities must support the full lifecycle m observatory evelopment, t ing, and other pre-launch activities through launch erations, and d ommissioning. M sion Operations Services also processes raw scie data receiv Services to Level 0 data to send to Product

Services. In erati of the observator s, Mission Operations Services has interfaces with both Ant Services and Product Services.

gure 2 depict allocatio f space weather ground services in the overall SWO Ground

Segment architect DRAFT

Figure 2: Nominal Baseline Ground rvices Ar tecture

The Space Weather Observations Mission Operations Servic O-MOS) Solution will be operated from the NOAA Satellite Operations Facility (NSOF) uitland MD and from the

NOAA Consolidated Backup (CBU) facil in Fairmont WV. Sol n operational components may be instantiated in a commercial clou or m instantiated on ernment premises. All components sited on premises at the NSO will be in ated within t NOAA5050

Information Technology (IT) Security boun ry that is m d by the NESDIS Office of

Satellite and Product Operations (OSPO).

It is SWO’s intention that MOS will lev components of the existing NESDIS enterprise to the greate xtent a opriate, inc ing but not limited to use of OS/COMET® for telemetry and comm nd, the NAS Attitude Gro d System (AGS) for attitude computation and management, an he NASA Gen l Mission Ana is Tool (GMAT), an open-source package for orbit deter ation solution maneuver plannin and related functions.

1.4 Scope

This document define base Indefinite Delivery / Indefinite Quantity (IDIQ) Performance

Wo nt (PWS) f development and long-term maintenance and sustainment of the

O-MOS. D g the per of performance of this IDIQ contract, through execution of Task

Orders, the contra r will dev the SWO-MOS by leveraging the SWFO-L1 Command and

Control (C2) capabi to deliver a true multi-mission operations service Solution that is scalable to comprehensively s port Mission Operations Services typical of Satellite Mission Operations

Center for all SWO m ions.

During e perio f performance of this IDIQ contract, Task Orders may be issued to:

• Asse d leverage the current SWFO-L1 mission operations architecture for use in a multi-mission, scalable operations service architecture.

• Provide a capability for NOAA and NOAA-affiliate operations staff to monitor and 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.

• Design and scale capabilities for capacity growth.

• Implement broader NESDIS ground enterprise applications or requirements o the SWO-

MOS or support the use of SWO-MOS capabilities within the NESDIS g nd enterprise.

• Develop and modify interfaces with the Antenna Services to plan and n Telemetry, Tracking, and to perform Command services.

• Develop and modify interfaces with Product Services to deliver l el 0 scienc ta and auxiliary data for higher-level product generation by NOAA as well as receive h d instrument housekeeping data, when available.

• Host simulators of NOAA satellites for pre-launch and rations use.

Provide test instances and interfaces to support pre-l ch communications with the observatory during observatory development, inte tion, test, and ssion rehearsals.

Provide test instances to support development and olution of a nna services or product services as required.

• Manage, design, develop, analyze, fabricate, assemble, ate, checkout, test, evaluate, verify, deliver, transition, document, and support developm operations, sustainment, and maintenance of SWO-MOS an interfaces.

• Perform activities required to suppo Gov nt-led verificati nd acceptance of

Contractor implementations and inte tion with her SWGS s vices.

• Perform SWO-MOS Solution-related cial studi su but not limited to, evaluation of candidate technologies, products, or erfac or inclusion into the Solution.

1.5 Places of Perf mance

A. Work lo ons for this co act include, bu re not limited to:

• NS in Suitland, M

• CBU i airmont V

• Contract a ties

B Other remote no MOS work locations may require ad hoc visits and will be identified by overnmen cluding:

• Wall Comman d Data Acquisition Station (WCDAS) in Wallops, VA

• End-to d test locat s

6 Terms and De tions

T following terms d definitions are used throughout this PWS.

The “applica documents” denotes Government-prepared and controlled documents and industry nda documents that levy additional requirements on the Contractor. The

Contractor quired 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 terms “will”, “are”, and “is” signate statements of fact.

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

The term “(TBD)” is an acronym for “to be determined” and identifie missing re ement.

The term “(TBR)” is an acronym for “to be refined/reviewed” and dentifies requiremen hat are subject to review for appropriateness and subject to revisio

The term “(GFP/GFI)” is an acronym for “Government-Fu hed Property/Government

Furnished Information” and refers to any Government-f ished hardwar facilities, information, or other resource provided by the Governm t for use in t SWO-MOS.

Government-furnished property means property in the po sion o acquired by the

Government and subsequently furnished to the Contractor fo mance of a contract.

Government-furnished property includes, but is not limited to, s es and property furnished for repair, maintenance, overhaul, or modific n Government-furni d property also includes

Contractor-acquired property that is a de ere der a contract and pted by the

Government for use under the contract.

The term “C” or “CTR” refers to the Contra r.

The term “G” or “Gov” means the federal Go rnm t.

The term “Government” nd G rnment pers nel” mean federal Government employees.

The term “Governm nt representa es” means p onnel designated by the Government to perform work rel ed to this contr t or interface w the deliverables of this contract. These personnel incl federal Gove ment employees, Support Contractors, Government stakeholders, and sonnel overnm tes and Government partner organizations.

The term “Support C ors” means Systems Engineering and Technical Assistance (SETA) supp tractors, Fed lly Funded Research and Development Center (FFRDC) employees, a Governm Cooperati Institutes and Grantee employee.

The term “Solutio includes th tal scope of SWO-MOS architecture and functionality developed, sustaine r maintained under this contract.

The term “Developm ” means the process of defining, designing, testing, and implementing w software applica ns. These efforts, further defined below are the basis of Solution creation, im menting its ca ilities, reliability and robustness, leverage technology advancements inclu agile an loud as appropriate.

The term inment” means activities performed to develop, modernize, or enhance the

SWO-MOS fter 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 retu n on investment.

• Addressing life cycle issues, including the impacts of aging spacecraft h dware and spacecraft anomalies, and the impacts of the gain or loss of data sou o maintain the highest quality (most accurate) products and services.

• Upgrading to new versions of Commercial Off-the-Shelf (COT software a hardware.

• Installing and enabling new enterprise tools.

The term “Maintenance” means activities that are performed to ure the continued oper n of the SWO-MOS after transition to operation. Maintenance en s that the SWO-MOS contin to meet technical, functional, and performance requiremen n addition to availability and reliability requirements. Maintenance also ensures a co nuation of the urity posture and controls.

2 RELATED DOCUMENTATION

This SWO-MOS Base PWS is the parent to all Task Orders under the IDIQ contract.

SWO-MOS Applicable and Reference (A&R) Documents List, SWGS-MS-LIST 03, provides the list of applicable and reference documents for this PWS with their sources the event of any unresolved conflict, the Contractor must request conflict resolution by th ntracting

Officer in advance of work performed.

The SWO-MOS Contract Data Requirements List (CDRL) Docu nt, SWGS-MS-CDR 001, provides an applicability matrix and defines the required cont of document deliverables required for performance of tasks under this contract. The C ntracting Officer Representative responsible for ensuring all deliverables are in complian with the CDRL

The SWO Program Acronym and Glossary List, SWO-MGM LI -0001, defines terminology as used in this document and throughout the SWOPD. In the e of conflict between terminology in this document and any oth dictionary, the SWO inology will take precedence. In the event of any unresolv c t the Contractor m request conflict resolution by the Contracting Officer.

3 CONTRACT-WIDE REQUIREMENTS

3.1 Contract Type

This is an Indefinite Delivery Indefinite Quantity (IDIQ) hybrid type contract veh le with potential for various types of task orders including: Firm-Fixed Price, Cost Pl Fixed Fee, Cost

Plus Incentive Fee, and Time and Materials.

The Government intends that there are three general classes of tasks as iated wi e IDIQ.

1. Solution Task Orders issued to enhance the multi-mission SWO-MOS Solution fulfill an enumerated set of requirements according to a specifi schedule. An example solution Task Order is a task to develop and/or verify lution capabilities to meet a of requirements to support a specific SWO project ellite mission according to the project’s lifecycle milestones. Fulfillment of th requirements y range from simple demonstration, test, and verification that a requir ent is alre met by the existing

Solution to development of new capabilities and fe es w n the Solution.

2. Sustainment and Maintenance Task Orders issued to o support to the continued

NOAA use of the delivered Solution or any components, dware, software, services, interfaces, and related systems or stems thereof.

3. Study Task Orders that are associ d wi isting, anticipate r potential capabilities, features, use, or modification of th WO-MO tion to supp t SWO or NESDIS objectives. Study Task Orders may i orm futur o ion of the Solution baseline, but generally will not impose specific olutio equirement Any study that has a clear nexus with the Soluti may be appro b he Contracting Officer for issuance as a task. Illustrative udy T Orders mig nclude (but are not limited to) analysis of how the Solution ght interfac with a new e rnal system or service, the impact of new security p ocols on the S ution, or the im act of replacement of specific Solution capabil s with NESDIS avored alternati

3.2 Task Orde dminist ion

NOAA Acquisition a ants Office (AGO) will administer this contract and the associated

Task on behalf o ESDIS SWO. Tasks may be issued to support any NESDIS Office for w k related e SWO-M S solution. The contractor shall notify and invite SWO

Government repr ntatives t end reviews pertaining to the performance of the tasks under this contract as wel any overa contract management reviews.

3.3 Task Order M agement

e contractor shall p vide experienced project managers, engineering, administrative, sc ific and techni staff, and development facilities to implement the assigned Task Orders and a pt total r onsibility for success (i.e., technical, fiscal, schedule). The contractor shall designa Pr t Manager for the overall success of the Solution and a Task Lead for each awarded T Order. The Project Manager shall serve as the responsible point of contact for technical, programmatic, and fiscal issues. The contractor shall perform general contract management including preparing progress reports and CDRL deliverables in accordance with

Task Order requirements, summarizing technical performance, identifying risks and associated mitigating actions, and financial status of the Task Order.

3.4 General

1. General Obligations

The contractor shall develop the SWO-MOS by leveraging the SWFO-L1 Command and Control

(C2) capability to deliver a true multi-mission operations service Solution that is s ble to comprehensively support Mission Operations Services typical of Satellite Missi Operations

Center for all SWO missions. The contractor shall provide all necessary serv (management, engineering, personnel, materials, and equipment) for the design, analysis ve ment, fabrication, assembly, integration, delivery, verification, validation, an aly reso on, maintenance, and sustainment of the SWO Mission Operations Service Solution. The ntractor shall develop and manage Solution interfaces with Government p icipation.

2. Management and Reporting

The contractor shall establish a comprehensive project m gement structure to ensure the overall project, consisting of the sum of the Task Ord emains on sch ule and within budget.

The contractor shall trend progress, deliver project mana ent repo and hold regular reviews monthly, or at a frequency determined appropriate by the G rnm nt.

3. Agile Process

The contractor shall implement an Agile s to design and itera ly develop the Solution through program increments, integrating w fea and capabilities ccordance with the functional, performance, and schedule req ements of mbined set f Task Orders.

The contractor’s Agile implementation shall early de eate be n strategic Program

Increment (PI) planning and tactical sprint ex tio This framework shall ensure Government oversight at the strategic ile providing ernment insight and empowering Agile teams with autonomy for eff ency at t print level. PI is a time-boxed release planning and delivery mechanism Nominally, time boxes s l be one calendar quarter. The PI is a strategic plannin and alignment ase where team ollaborate to plan and deliver incrementally e useful softw e S i ts are tim boxed iterations within a PI, typically lasting 2-4 weeks rints ar he tactical n phase where contractor teams focus on designing, developin n elivering specific features or capabilities.

The r shall incl Government representatives in PI planning, prioritization, and result rting.

The contractor sha emonstra ch added capability at time of completion.

The contractor shall p vide transparency to the sprint activities through access to sprint artifacts.

he contractor shall i grate Government and its authorized representatives into the Agile p ess at an agreed on level of detail and transparency necessary, including account and spri rtifact acce to provide the government meaningful status and allow timely government guidan

4. Earned Value Management (EVM)

The contractor shall implement and adhere to an Earned Value Management System (EVMS) and track cost and schedule performance against a baseline.

The Contractor shall implement an EVMS that complies with the Industry Guidelines for Earned

Value Measurement System (ANSI/EIA748) for all cost-type Task Orders.

5. Requirements Management

The contractor shall manage requirements received through Task Orders and fl them into

Solution requirements. This includes the maintenance of traceability from th vernment’s

Level 3 requirements as given in the Mission Operations Services Requi ents cument

(MOSRD) and subsequent Task Order amended MOSRD into lower-l l requirem s or user stories, and acceptance criteria. The contractor shall use a requirements management sy m to document, track, and manage all requirements. The contractor sh grant Government representatives access to this system to ensure transparency a facilitate collaboration. The figure below illustrates the MOSRD requirement hierarchy gure 3: SWO-MOS Requirements Flow

6. Risk Manage nt

The contractor shall i lement a Risk Management (RM) plan and systems to identify and gate potential risk to safety, cost, schedule, and technical performance. The contractor shall rep risks to the G ernment and get approval for risk acceptance or closures.

7. figu ion Management

The contra shall establish a Configuration Management (CM) plan and systems to control the management of Solution baselines, documents, and changes. Consistent with Agile practice, the

CM systems must also track Task Order functional and performance requirements, Agile artifacts, and verification artifacts.

8. Schedule Management

The contractor shall maintain an Agile-appropriate Integrated Master Schedule (IMS) for the complete Solution including all major milestones from all Task Orders and a forecast of capabilities and features by PI is required for tracking project events. Key project lif ycle milestones for all Task Orders must be included in the IMS.

9. SWO & SWGS Lifecycle Review Participation

The Government will conduct SWO project-level and SWGS lifecycle r ws t tablish the maturity of the ground system for each project. The Contractor shall p icipate, pro de, and present SWO-MOS Solution content in these lifecycle reviews as requested by the Go ment or as identified in each project’s Task Order.

The Government will chair the project lifecycle reviews. Th view panel for these reviews consist of Independent Integrated Review Team member ppointed by the Government. Projec lifecycle reviews will assess the maturity of the Soluti capability to et each project

MSRD. Government lifecycle reviews are documented i ch proje eview plan and may include but are not limited to:

• Systems Requirements Review (SRR)

• Preliminary Design Review (PDR

• Design Modification Review (DM )

• Critical Design Review (CDR)

• Systems Integration Review (SIR)

• Pre-Ship Review (PSR)

• Operations Readin view (ORR)

• Flight Operatio Revie FOR)

• Mission Op tions Revie MOR)

• Safety an Mission Succe Review (SMS

• Launch adiness Revie LRR)

• Handover adiness iew (H

• Post-Launch e ment Review (PLAR)

A na O-MOS So on-level reviews to be conducted by the Contractor will be entified in ea roject’s T Order (e.g., Mission Unique Change Review, DMR, CDR).

10. Plans and R rts

The contractor shall p vide specific deliverables, such as Project Management Plans, Risk

Management Plans, a various technical reports, in formats specified or agreed to by the

G rnment. A list o equired plans and reports is found in the Contract Data Requirements List

(CD )

11. S on cting

The contrac r shall be responsible for the performance of any subcontractors, ensuring that subcontractors meet all technical, cost, and schedule performance metrics. All contract clauses including and not limited to security clauses and rights in data requirements shall be passed down to subcontractors.

12. Government Representatives’ Contractor Facility and Virtual Access

The contractor shall ensure that Government personnel and authorized representatives can access contractor and subcontractor facilities, and the contractor shall allow Government equipment into these locations.

The contractor shall ensure that Government and authorized representatives hav ccess to digital resources such as CM systems and virtual meeting systems used in th nduct of work under this contract.

The Government shall be invited to meetings held in the conduct of w k under this ntract.

13. Information Cyber Security & Support

The SWO-MOS and NOAA5050 is rated as a High Risk Info ation System in accordance h the National Institute of Standards and Technology (NIST) deral Information Processing

Standards (FIPS) Publication 199, Standards for Securit ategorization f Federal Information and Information Systems. The Contractor shall perform curity activi as specified in individual Task Orders. Contractor personnel will be scre d in ac dance with the requirements for High Risk contracts as specified by Comm quisition Manual (CAM)

1337.70 section 2.2 (Oct 2015); specifically, in accordance with AR 1352.237-70, Security

Processing Requirements—High or Mod te Risk Contracts (Apr 010). Any access by contract personnel who are Foreign Nati als be in accordance the requirements of

Commerce Acquisition Regulation (CAR) 352.237 Foreign Nation Visitor and Guest

Access to Departmental Resources (APR 2 0).

The Contractor shall review all proposed sys mod cations to ensure the IT security posture is maintained.

The Contractor shall ly IT sec ty requirem s for all phases of implementation of the design in accordan with the law tatutes, and ulations as published in the US Department of Commerce (D C) Enterprise C bersecurity Pol (ECP), including IT Security requirements outlined in CA 352.239-72 u it Requiremen s For Information Technology Resources

(April 2010). CA 352.239 2, section ( des the DOC Enterprise Cybersecurity Policy the NOAA IT Secur M ual, and the NESDIS IT Security Handbook.

Any ial cloud o ing shall be instantiated in a Federal Risk and Authorization

M nagement ram (Fed MP) authorized cloud offering that matches the defined FIPS199 mpact level of N A5050.

14. Contractor Ac s to Government Facilities

C ractor personnel ill be provided appropriate access to Government facilities and

Go ment equip nt including information technology equipment, systems, software, or accoun The c ractor shall be responsible to complete any agency-required identity and security-r policies and processes to obtain such access. The contractor shall assure that contractor p rsonnel follow such policies in a timely manner such that work is not impaired.

15. Supply Chain Risk Management (SCRM)

The contractor shall develop a program of Supply Chain Risk Management for all purchases of

IT equipment and software compliant with Government policies. The contractor shall ensure that any third-party vendors or subcontractors involved in the supply chain also comply with contract security requirements. The Contractors SCRM program shall follow exiting SCRM policies defined in the DOC Enterprise Cyber Security Policy and the NOAA IT Security Manual.

16. System Integration and Testing

The contractor shall be responsible for integrating, testing, verifying and validat g the Solution, including hardware, software, and correct interaction with internal and extern nterfaces and across sites (including contractor development environments), consistent w h ernment operational testing guidelines and constraints. Testing shall include both ominal reasonable anomaly and failover scenarios.

The contractor shall provide system support and anomaly resolu n during Government ing and pre-launch activities to exercise and validate the Solution

17. Training

The contractor shall perform operator training, includin he developm of training materials and the conduct of training for contractor, Government, a Govern nt representatives as directed in Task Orders.

18. Maintenance and Sustainment

The contractor shall perform maintenanc an tainment that inclu preventive and corrective actions, tracking third-party ve or contr nd ensuring l term support for the deployed system as directed in Task Order

19. CMMI Certification

The contractor shall deliv to achieve C I Maturity Level 3 certification within 30 days of the award of th first task der and achi e certification within 12 months thereafter.

The contractor shal maintain CM Level 3 cer cation spanning the total period of performance of Task Orders.

20. Mission surance

The contractor shall

1 velop, tain, and lement an approach to protect the public, Government and ontractor workf e, high-va equipment and property, and the environment from potential harm because of G rnment an contractor activities and operations by factoring safety as an integral feature of pr ams, projects, technologies, operations, and facilities.

Support of instituti al and program objectives shall comply with pertinent premises clauses, G nment policie nd requirements, and Federal, state, and local regulations for safety, healt nd emerg cy preparedness.

3. Provide maintain proper Environment, Health, and Safety functions in accordance with

Federal, State and NASA/NOAA policies, directives, and requirements.

4. Apply safety and mission assurance requirements to the extent necessary to ensure that the delivered product or service meets performance and safety requirements.

5. Meet ground services Mission Assurance requirements in accordance with the applicable documents listed in this base PWS and in subsequent Task Orders.

6. Provide the Government access to Contractor anomaly review boards and anom tracking tools.

21. Special Studies

The contractor shall conduct special studies as directed by Task Orders Studies mus clearly associated with existing, anticipated, or potential capabilities, fea s, use or modificati of the

SWO-MOS Solution to support SWO or NESDIS objectives.

22. Export Control

Some Task Orders may require interaction with foreig ationals or rep entatives of foreign

Governments including personnel representing foreign ag cies coor ating under Government international inter-agency agreements. The contractor shall for ll activities necessary for the export/import of these materials and information. In order otect the national security and to further agency and U.S. foreign policy objectives, export contr aws regulate such transfer activities. Relevant export control laws d lations include the E ort Administration

Regulations (EAR), 15 CFR 730-774, an he Int i nal Traffic in A s Regulations (ITAR)

22 CFR 120-130 that are administered by Departme f Commerce and State, respectively.

The Contractor shall be responsible for all a ects of th xpo port process.

23. Property Management

The Contractor shall d lop an llow a Prop y Management Plan and procedures to identify and account for Gov nment prop y in the poss ion of the Contractor from the time the property is acqui until it is form ly delivered t e Government. The Contractor shall provide person to support the overnment Prop y Custodian who is responsible for maintaining and ounting f erty in accordance with the Department of

Commerce property ana ment policies. The Contractor shall enable Government-designated representatives to con property inventories including “touch-inventory” at all locations wh ment prop is located.

24. Governm Rights in ta

All software and in mation dev loped under this contract shall be delivered with full rights for use, modification, rep duction, and the creation of derivative works by the Government. The

Government shall hav unlimited rights to use, disclose, reproduce, prepare derivative works, ribute copies to th public, and perform and display publicly, in any manner and for any pur e, and to per others to do so.

The co ctor ll ensure that software not developed under this contract and incorporated into the Soluti all be clearly delineated with all associated rights and restrictions disclosed.

The contractor shall deliver all source code, object code, configuration files, third party package specifications, installation procedures, other artifacts, and documentation necessary for the installation, use, modification, and maintenance of the software at the Government-designated sites.

The contractor shall warrant that the software delivered is free from any claims of infringement of any intellectual property rights of third parties.

25. Contract Transition and End-of-Life Management:

At the end of the contract, the contractor shall support a smooth transition to the G rnment or successor contractor, providing necessary documentation and system knowledg

4 DELIVERABLES

4.1 Data Deliveries

The SWO-MOS Contract Data Requirements List (CDRL), SWGS-MS-CDRL-0 1, provides an applicability list of data deliverable for requirements in this PWS and requi ments of all subsequent project-specific Task Orders PWS’s. Additional deliverable req nts applicable for each Task Order will be provided in the Task Orders.

4.2 Deliveries at Factory and Operational Sites

The contractor shall develop, maintain, and operate factory envi ments necessary to pe m development, testing, maintenance and sustainment activities he contractor shall deliver a install the Solution to multiple Government sites for opera n by the Government. Delivery must comply with Government configuration managem processes and uidelines, as specified in each Task Order. The deliveries must provide the co ete workin lution and include:

• COTS, test, and operational workstation hardware

• Test and operational software, including licenses

• Cryptographic devices for spacecr ft communication insta s including any required modifications

• NOAA infrastructure-compatible n work eq ent

• Simulators

• Intra-site network infrastructure

• IT resources

• Documentation