SWO-MOS PWS IDIQ KT.docx

GSFC SWGS CMO

02/26/2025 Released

SWGS-MOS-SOW-0001, Revision - Space Weather Ground Services, Code 492.0

Space Weather Observations Mission Operations Services

(SWO-MOS)

Base Performance Work Statement

SWO Reviewed – Not Subject to Export Control

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

Space Weather Observations Mission Operations Services

(SWO-MOS)

Base Performance Work Statement Review/Signature/Approval Page

Prepared by:

Reviewed by:

Approved by:

Preface This document provides the Base Performance Work Statement for the Indefinite Delivery / Indefinite Quantity (IDIQ) for the Space Weather Observations Mission Operations Services (SWO-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:

SWGS 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 Figures

Effective Date: 02/26/2025 Expiration Date: 02/26/2030

SWO-MOS Base PWS SWGS-MOS-SOW-0001, Revision - Effective Date: February 26, 2025

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

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

1 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 Description

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 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 observatories to be named Space weather Observations at Lagrange 1 (SOL). The first of these observatories is built as SWFO-L1. The next two independently-launched observatories planned are part of the SWx SOL project are designated SOL-A and SOL-B. SOL-A is planned to be launched no earlier than 2029 and SOL-B no earlier than 2032. Each will be operated in a Lissajous orbit around Sun-Earth L1. Each observatory will host up to six observing instruments. SWO mission operations services will provide the full suite of satellite operations and observatory management for the SOL observatories and process the observations into level 0 space weather products.

SWO also has begun 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 Services will support instrument monitoring sufficient to maintain awareness of SW instrument status and assist partner satellite operations center. SWO-MOS also may receive the NOAA instrument data and telemetry from hosting partners or other SWGS elements and process the observations into level 0 space weather products, if not done so prior to receipt.

Figure 1 below depicts the total envisioned SWO observing architecture.

Figure 1: SWGS Mission Architecture

1.3 Space Weather Ground Services Overview

SWGS is responsible for ensuring a consolidated space weather ground services approach across the loosely-coupled SWO projects that is consistent with broad NESDIS Ground Enterprise (NGE) objectives and implemented to satisfy individual project mission requirements and milestones. SWGS will use NOAA institutional facilities and leverage common SWO services, NOAA agency services, and partner agencies and commercial services where they are available and as they are shown 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 next decade 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 Mission Operations Services capabilities will similarly leverage appropriate 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. 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 Space Weather Prediction Center, 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, and archive 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 the full lifecycle, from observatory development, testing, and other pre-launch activities through launch, operations, and decommissioning. Mission Operations Services also processes raw science data received from Antenna Services to Level 0 data to send to Product Services. In operation of the observatories, Mission Operations Services has interfaces with both Antenna Services and Product Services.

Figure 2 depicts the allocation of space weather ground services in the overall SWO Ground Segment architecture.

Figure 2: Nominal Baseline Ground Services Architecture The Space Weather Observations Mission Operations Services (SWO-MOS) Solution will be operated from the NOAA Satellite Operations Facility (NSOF) in Suitland MD and from the NOAA Consolidated Backup (CBU) facility in Fairmont WV. Solution operational components may be instantiated in a commercial cloud or may be instantiated on Government premises. All components sited on premises at the NSOF will be incorporated within the NOAA5050 Information Technology (IT) Security boundary that is maintained by the NESDIS Office of Satellite and Product Operations (OSPO).

It is SWO’s intention that SWO-MOS 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) Performance Work Statement (PWS) for development and long-term maintenance and sustainment of the SWO-MOS. During the period of performance of this IDIQ contract, through execution of Task Orders, the contractor will 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 scalable to comprehensively support Mission Operations Services typical of Satellite Mission Operations Center for all SWO missions.

During the period of performance of this IDIQ contract, Task Orders may be issued to:

· Assess and 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 into the SWO-MOS or support the use of SWO-MOS capabilities within the NESDIS ground enterprise.

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

· Develop and modify interfaces with Product Services to deliver level 0 science data and auxiliary data for higher-level product generation by NOAA as well as receive hosted instrument housekeeping data, when available.

· Host simulators of NOAA satellites for pre-launch and 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.

· Manage, design, develop, analyze, fabricate, assemble, integrate, checkout, test, evaluate, verify, deliver, transition, document, and support development, operations, sustainment, and maintenance of SWO-MOS and its interfaces.

· Perform activities required to support Government-led verification and acceptance of Contractor implementations and integration with all other SWGS services.

· Perform SWO-MOS Solution-related special studies such as, but not limited to, evaluation of candidate technologies, products, or interfaces for inclusion into the Solution.

1.5 Places of Performance

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

· NSOF in Suitland, MD

· CBU in Fairmont, WV

· Contractor Facilities B. Other remote non-MOS work locations may require ad hoc visits and will be identified by the Government, including:

· Wallops Command and Data Acquisition Station (WCDAS) in Wallops, VA

· End-to-end test locations

1.6 Terms and Definitions

The following terms and definitions are used throughout this PWS.

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 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 SWO-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 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 SWO-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 SWO-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 SWO-MOS after transition to operation. Maintenance ensures that the SWO-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.

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

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-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 Contract-Wide Requirements

3.1 Contract Type

This is an Indefinite Delivery Indefinite Quantity (IDIQ) hybrid type contract vehicle with potential for various types of task orders including: Firm-Fixed Price, Cost Plus Fixed Fee, and Time and Materials.

The Government intends that there are three general classes of tasks associated with the IDIQ.

1. Solution Task Orders issued to enhance the multi-mission SWO-MOS Solution to fulfill an enumerated set of requirements according to a specified schedule. An example solution Task Order is a task to develop and/or verify Solution capabilities to meet a set of requirements to support a specific SWO project satellite mission according to the project’s lifecycle milestones. Fulfillment of these requirements may range from simple demonstration, test, and verification that a requirement is already met by the existing Solution to development of new capabilities and features within the Solution.

2. Sustainment and Maintenance Task Orders issued to obtain support to the continued NOAA use of the delivered Solution or any components, hardware, software, services, interfaces, and related systems or subsystems thereof.

3. Study Task Orders that are associated with existing, anticipated, or potential capabilities, features, use, or modification of the SWO-MOS Solution to support SWO or NESDIS objectives. Study Task Orders may inform future modification of the Solution baseline, but generally will not impose specific Solution requirements. Any study that has a clear nexus with the Solution may be approved by the Contracting Officer for issuance as a task. Illustrative Study Task Orders might include (but are not limited to) analysis of how the Solution might interface with a new external system or service, the impact of new security protocols on the Solution, or the impact of replacement of specific Solution capabilities with NESDIS-favored alternatives.

3.2 Task Order Administration

NOAA Acquisition and Grants Office (AGO) will administer this contract and the associated Task Orders on behalf of NESDIS SWO. Tasks may be issued to support any NESDIS Office for work related to the SWO-MOS solution. The contractor shall notify and invite SWO Government representatives to attend reviews pertaining to the performance of the tasks under this contract as well as any overall contract management reviews.

3.3 Task Order Management

The contractor shall provide experienced project managers, engineering, administrative, scientific and technical staff, and development facilities to implement the assigned Task Orders and accept total responsibility for success (i.e., technical, fiscal, schedule). The contractor shall designate a Project Manager for the overall success of the Solution and a Task Lead for each awarded Task 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 scalable to comprehensively support Mission Operations Services typical of Satellite Mission Operations Center for all SWO missions. The contractor shall provide all necessary services (management, engineering, personnel, materials, and equipment) for the design, analysis, development, fabrication, assembly, integration, delivery, verification, validation, anomaly resolution, maintenance, and sustainment of the SWO Mission Operations Service Solution. The contractor shall develop and manage Solution interfaces with Government participation.

2. Management and Reporting The contractor shall establish a comprehensive project management structure to ensure the overall project, consisting of the sum of the Task Orders, remains on schedule and within budget. The contractor shall trend progress, deliver project management reports and hold regular reviews monthly, or at a frequency determined appropriate by the Government.

3. Agile Process The contractor shall implement an Agile process to design and iteratively develop the Solution through program increments, integrating new features and capabilities in accordance with the functional, performance, and schedule requirements of the combined set of Task Orders.

The contractor’s Agile implementation shall clearly delineate between strategic Program Increment (PI) planning and tactical sprint execution. This framework shall ensure Government oversight at the strategic level while providing Government insight and empowering Agile teams with autonomy for efficiency at the sprint level. A PI is a time-boxed release planning and delivery mechanism. Nominally, PI time boxes shall be one calendar quarter. The PI is a strategic planning and alignment phase where teams collaborate to plan and deliver incrementally more useful software. Sprints are time-boxed iterations within a PI, typically lasting 2-4 weeks. Sprints are the tactical execution phase where contractor teams focus on designing, developing, and delivering specific features or capabilities.

The contractor shall include Government representatives in PI planning, prioritization, and result reporting.

The contractor shall demonstrate each added capability at time of completion.

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

The contractor shall integrate Government and its authorized representatives into the Agile process at an agreed upon level of detail and transparency necessary, including account and sprint artifact access, to provide the government meaningful status and allow timely government guidance.

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 flow them into Solution requirements. This includes the maintenance of traceability from the Government’s Level 3 requirements as given in the Mission Operations Services Requirements Document (MOSRD) and subsequent Task Order amended MOSRD into lower-level requirements or user stories, and acceptance criteria. The contractor shall use a requirements management system to document, track, and manage all requirements. The contractor shall grant Government representatives access to this system to ensure transparency and facilitate collaboration. The figure below illustrates the MOSRD requirement hierarchy:

Figure 3: SWO-MOS Requirements Flow

6. Risk Management The contractor shall implement a Risk Management (RM) plan and systems to identify and mitigate potential risks to safety, cost, schedule, and technical performance. The contractor shall report risks to the Government and get approval for risk acceptance or closures.

7. Configuration Management The contractor 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 lifecycle 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 reviews to establish the maturity of the ground system for each project. The Contractor shall participate, provide, and present SWO-MOS Solution content in these lifecycle reviews as requested by the Government or as identified in each project’s Task Order.

The Government will chair the project lifecycle reviews. The review panel for these reviews will consist of Independent Integrated Review Team members appointed by the Government. Project lifecycle reviews will assess the maturity of the Solution’s capability to meet each project MSRD. Government lifecycle reviews are documented in each project review plan and may include but are not limited to:

· Systems Requirements Review (SRR)

· Preliminary Design Review (PDR)

· Design Modification Review (DMR)

· Critical Design Review (CDR)

· Systems Integration Review (SIR)

· Pre-Ship Review (PSR)

· Operations Readiness Review (ORR)

· Flight Operations Review (FOR)

· Mission Operations Review (MOR)

· Safety and Mission Success Review (SMSR)

· Launch Readiness Review (LRR)

· Handover Readiness Review (HRR)

· Post-Launch Assessment Review (PLAR)

Additional SWO-MOS Solution-level reviews to be conducted by the Contractor will be identified in each project’s Task Order (e.g., Mission Unique Change Review, DMR, CDR).

10. Plans and Reports The contractor shall provide specific deliverables, such as Project Management Plans, Risk Management Plans, and various technical reports, in formats specified or agreed to by the Government. A list of required plans and reports is found in the Contract Data Requirements List (CDRL).

11. Subcontracting The contractor 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 have access to digital resources such as CM systems and virtual meeting systems used in the conduct of work under this contract.

The Government shall be invited to meetings held in the conduct of work under this contract.

13. Information Cyber Security & Support The SWO-MOS and NOAA5050 is rated as a High Risk Information System in accordance with the National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) Publication 199, Standards for Security Categorization of Federal Information and Information Systems. The Contractor shall perform security activities as specified in individual Task Orders. Contractor personnel will be screened in accordance with the requirements for High Risk contracts as specified by Commerce Acquisition Manual (CAM) 1337.70 section 2.2 (Oct 2015); specifically, in accordance with CAR 1352.237-70, Security Processing Requirements—High or Moderate Risk Contracts (April 2010). Any access by contract personnel who are Foreign Nationals shall be in accordance with the requirements of Commerce Acquisition Regulation (CAR) 1352.237-73, Foreign National Visitor and Guest Access to Departmental Resources (APR 2010).

The Contractor shall review all proposed system modifications to ensure the IT security posture is maintained.

The Contractor shall apply IT security requirements for all phases of implementation of the design in accordance with the laws, statutes, and regulations as published in the US Department of Commerce (DOC) Enterprise Cybersecurity Policy (ECP), including IT Security requirements outlined in CAR 1352.239-72, Security Requirements For Information Technology Resources (April 2010). CAR 1352.239-72, section (d) includes the DOC Enterprise Cybersecurity Policy, the NOAA IT Security Manual, and the NESDIS IT Security Handbook.

Any commercial cloud offering shall be instantiated in a Federal Risk and Authorization Management Program (FedRAMP) authorized cloud offering that matches the defined FIPS199 impact level of NOAA5050.

14. Contractor Access to Government Facilities Contractor personnel will be provided appropriate access to Government facilities and Government equipment including information technology equipment, systems, software, or accounts. The contractor shall be responsible to complete any agency-required identity and security-related policies and processes to obtain such access. The contractor shall assure that contractor personnel 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 existing 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 validating the Solution, including hardware, software, and correct interaction with internal and external interfaces and across sites (including contractor development environments), consistent with Government operational testing guidelines and constraints. Testing shall include both nominal and reasonable anomaly and failover scenarios.

The contractor shall provide system support and anomaly resolution during Government testing and pre-launch activities to exercise and validate the Solution.

17. Training The contractor shall perform operator training, including the development of training materials and the conduct of training for contractor, Government, and Government representatives as directed in Task Orders.

18. Maintenance and Sustainment The contractor shall perform maintenance and sustainment that includes preventive and corrective actions, tracking third-party vendor contracts, and ensuring long-term support for the deployed system as directed in Task Orders.

19. CMMI Certification The contractor shall deliver a plan to achieve CMMI Maturity Level 3 certification within 30 days of the award of the first task order and achieve certification within 12 months thereafter. The contractor shall maintain CMMI Level 3 certification spanning the total period of performance of all Task Orders.

20. Mission Assurance The contractor shall:

1. Develop, maintain, and implement an approach to protect the public, Government and contractor workforce, high-value equipment and property, and the environment from potential harm because of Government and contractor activities and operations by factoring safety as an integral feature of programs, projects, technologies, operations, and facilities.

2. Support of institutional and program objectives shall comply with pertinent premises clauses, Government policies and requirements, and Federal, state, and local regulations for safety, health, and emergency preparedness.

3. Provide and 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 anomaly tracking tools.

21. Special Studies The contractor shall conduct special studies as directed by Task Orders. Studies must be clearly associated with existing, anticipated, or potential capabilities, features, use or modification of the SWO-MOS Solution to support SWO or NESDIS objectives.

22. Export Control Some Task Orders may require interaction with foreign nationals or representatives of foreign Governments including personnel representing foreign agencies coordinating under Government international inter-agency agreements. The contractor shall perform all activities necessary for the export/import of these materials and information. In order to protect the national security and to further agency and U.S. foreign policy objectives, export control laws regulate such transfer activities. Relevant export control laws and regulations include the Export Administration Regulations (EAR), 15 CFR 730-774, and the International Traffic in Arms Regulations (ITAR) 22 CFR 120-130 that are administered by the Departments of Commerce and State, respectively. The Contractor shall be responsible for all aspects of the export or import process.

23. Property Management The Contractor shall develop and follow a Property Management Plan and procedures 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 to the Government. The Contractor shall provide personnel to support the Government Property Custodian who is responsible for maintaining and accounting for Government property in accordance with the Department of Commerce property management policies. The Contractor shall enable Government-designated representatives to conduct property inventories including “touch-inventory” at all locations where Government property is located.

24. Government Rights in Data All software and information developed under this contract shall be delivered with full rights for use, modification, reproduction, and the creation of derivative works by the Government. The Government shall have unlimited rights to use, disclose, reproduce, prepare derivative works, distribute copies to the public, and perform and display publicly, in any manner and for any purpose, and to permit others to do so.

The contractor shall ensure that software not developed under this contract and incorporated into the Solution shall 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 Government or successor contractor, providing necessary documentation and system knowledge.

4 Deliverables

4.1 Data Deliveries

The SWO-MOS Contract Data Requirements List (CDRL), SWGS-MS-CDRL-0001, provides an applicability list of data deliverable for requirements in this PWS and requirements of all subsequent project-specific Task Orders PWS’s. Additional deliverable requirements 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 environments necessary to perform development, testing, maintenance and sustainment activities. The contractor shall deliver and install the Solution to multiple Government sites for operation by the Government. Delivery must comply with Government configuration management processes and guidelines, as specified in each Task Order. The deliveries must provide the complete working Solution and include:

· COTS, test, and operational workstation hardware

· Test and operational software, including licenses

· Cryptographic devices for spacecraft communication instances including any required modifications

· NOAA infrastructure-compatible network equipment

· Simulators

· Intra-site network infrastructure

· IT resources

· Documentation image2.png image3.png image4.png image5.png image1.png