Task Order 3 PWS for Sustainment.pdf

Source Selection Information – See FAR 2.101 and 3.104

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

Office of Satellite and Product Operations (OSPO) and

Office of Satellite Ground Services (OSGS)

Revised-Draft Operations, Maintenance, and Sustainment (OMS) Task Order 3 Performance Work Statement (PWS)

November 22, 2019

DRAFT OPERATIONS, MAINTENANCE, AND SUSTAINMENT

TASK ORDER 3 PWS - SUSTAINMENT SUPPORT

Table of Contents

1.0 Overview 4

2.0 Scope 4

2.1 Place of Performance 6

2.2 References 6

3.0 General Requirements 7

3.1 General Sustainment Requirements 7

3.1.1 System Engineering Support 11

3.1.1.1 Antenna and Radio Frequency Equipment Systems Engineering 12

3.1.1.2 Program Management Support 13

3.1.1.2.1 Contract Transition 14

3.1.2 Technology Sustainment Support 15

3.1.2.1 Software Sustainment Solutions 16

3.1.2.2 System Integration, Installation and Test of Sustainment Solutions 17

3.1.2.3 Hardware Sustainment Solutions 18

4.0 Ground Systems Requirements 19

4.1 Product Processing Sustainment 20

4.1.1 Environmental Satellite Processing Center (ESPC) 20

4.1.1.1 ESPC Product Generation 21

4.1.1.2 ESPC Product Distribution and Access 21

4.1.1.3 ESPC Continuity of Operations 22

4.1.1.4 ESPC Infrastructure Services 22

4.1.1.5 ESPC Supplementary Services 23

4.1.2 ESPC Performance Requirements and/or Performance Standards 23

4.1.3 Product Transition to the Cloud 24

4.2 Legacy Ground System Extended Maintenance 24

4.2.1 Geostationary Satellite Series NOP (GOES N/O/P) Ground System 24

4.2.2 Polar-Orbiting Operational Environmental Satellite (POES) Ground System 25

4.2.3 NOAA Jason-3 Ground System (NJGS) 25

4.2.4 Geostationary Satellite Series Indian Ocean (GOES IO) Ground System 26

4.2.5 Deep Space Climate Observatory (DSCOVR) Ground System 26

4.2.6 Mission Support Local Area Network (LAN) 26

4.2.7 Data Collection System (DCS) Ground System 27

4.2.8 Search and Rescue Satellite Aided Tracking (SARSAT) 27

4.2.9 Antennas and Radio Frequency Equipment 27

4.2.9.1 Antennas 27

4.2.9.2 Radio Frequency Equipment 28

4.2.10 IT Security Sustainment 28

4.2.10.1 IT Security Other Direct Costs 29

5.0 Training 29

6.0 Performance Requirements Summary 30

Appendix A. Deliverables 34

Appendix B. Release Backlog and MoSCow Process 37

Appendix C. Antenna Sustainment Matrix 38

Appendix D. Acronym Listing 41

1.0 Overview

Task Order 3 details Contractor implementation of Sustainment Activities per Indefinite Delivery, Indefinite Quantity (IDIQ) Performance Work Statement (PWS) sections 1.4.6 (Sustainment Tier 3b), 1.4.7 (Integration and Test), 3.1.3 (Contract Transition), 3.4 (Sustainment) and 3.5 (Information Cyber Security and Support) as well as more specific sustainment activities for the systems contained herein. This sustainment task order covers the managed planning, transition/migration, and implementation activities by the Contractor from an incumbent contractor. This Sustainment task order supports:

● Technology refresh (upgrades) to designated legacy ground systems and subsystems

● Technology refresh (upgrades) of legacy infrastructure (e.g. operational tools) applicable to the legacy ground systems and subsystems

2.0 Scope

This sustainment task order addresses scope for sustainment activities and associated deliverables. Sustainment activities include pre-planned activities to develop, modernize, or enhance the applicable legacy ground systems and subsystems. Sustainment efforts provide benefits to extend system life, reduce life cycle costs (or provide the best return on the satellite investment), leverage technology advancements, and improve the capability, reliability and robustness to meet program life requirements.

Sustainment activities for this task order include:

● Provide project management resources to effectively manage, coordinate, and implement all sustainment activities and provide regular reporting of technical, schedule, and financial status to the Government through various means including meetings, written correspondence, and via a list of deliverables.

● Identify legacy ground system and subsystems items for sustainment support/upgrade.

● Prepare and document a plan to develop, integrate, test and implement all sustainment functional capability (hardware and software), or new sub-component(s) of existing systems following rigorous documented procedures.

● Develop detailed cost estimates for all elements of the identified sustainment solutions.

● Perform requirements analysis and design (as required), and conduct the proper reviews for all sustainment solutions (e.g. Preliminary Design Review (PDR)/ Critical Design Review (CDR), action items, etc.) following the review process

● Procure all hardware equipment and software to implement the sustainment solutions.

● Deliver software compliant with approved contractor standards and NOAA/NESDIS standards.

● In concert with the Government, perform all integration and testing and modify and/or port existing software to new hardware platforms that interface with existing operational systems.

● Conduct all required software reviews for sustainment solutions including requirements review, interfaces, software code, testing for planned software release and capability verification (factory acceptance and site acceptance testing, pre-ship review, as required) and (if any) fixes to ensure all the capabilities function as intended.

● Support all sustainment planning, integration and test activities to ensure the requirements, configuration, test, and verification of all capabilities are approved for implementation.

● Provide all training for the sustainment solutions implemented under the task order.

● Conduct product transition sustainment support on ground system components that have migrated to the cloud environment.

Table 2-1 below shows the assigned ground systems supported under Task Order 3 and contained within the body of this task order. Individual Work Assignments will be issued to refine the Statement of Work as specific tasks are identified and funding is provided for the systems under section 4.2 of this PWS.

Most legacy systems detailed in this task order have received a technology refresh and require minimal sustainment support. Table 3.1-1 details technology refresh schedules for each of the legacy ground systems supported by this task order. However, the Contractor is expected to develop an inventory as part of the Sustainment Plan which contains details of specific ground system assets to be refreshed, and system hardware components and software within one (1) year of obsolescence.

Table 2-1 – Legacy Ground Systems & Systems

Ground Systems Acronym FISMA Boundary

Environmental Satellite Processing Center ESPC NOAA 5045

Geostationary Operational Environmental Satellites N/O/P Ground System

GOES NOP NOAA 5003

Polar-orbiting Operational Environmental Satellite Ground System

POES NOAA 5026

NOAA JASON-3 Ground System NJGS NOAA 5046

GOES Indian Ocean GOES I/O NOAA 5003 (Currently

GOES N/O/P)

Deep Space Climate Observatory Ground System DSCOVR NOAA 5003 (Currently

GOES N/O/P)

Mission Support Local Area Network (LAN) MSL NOAA 5044

Data Collection System DCS NOAA 5004

Search and Rescue Satellite Aided Tracking SARSAT NOAA 5023

A detailed list of NESDIS systems is provided in the IDIQ PWS, Appendix A, NESDIS System Boundary General Correspondence to NESDIS Missions/Functions. Individual system inventories, drawings, descriptions and interfaces are available in the OMS Document Library.

Appendix C, Sustainment Antenna Matrix, details what antennas need to be sustained by legacy missions to support the ground systems noted in Table 4.0.

2.1 Place of Performance

The National Environmental Satellite, Data, and Information Service (NESDIS) Ground Enterprise (NGE) primary work locations for this task order include:

● NOAA Satellite Operations Facility (NSOF) located in Suitland, MD

● OSGS Program Offices located in Greenbelt, MD and Silver Spring, MD

● NOAA Center for Weather and Climate Prediction (NCWCP) located in College Park, MD

● The NESDIS Consolidated Backup Unit (CBU) located in Fairmont, WV

● NESDIS Command and Data Acquisition (CDA) Stations located in Wallops, VA

Fairbanks and Utqiagvik, AK

● Lockheed Martin Facility located in Sunnyvale, CA

Equipment that is outside of NGE primary work locations are remote places of performance that include, as required:

● USAF Environmental Satellite Operations Center (ESOC) located at Schriever Air Force Base, Colorado Springs, CO

● Remote Ground System (RGS) located at Dongara, AUS, and other associated sites in Australia

● Equipment located at European Organisation for the Exploitation of Meteorological Satellites (EUMETSAT), Darmstadt, Germany

Additional work locations may be required.

2.2 References

The following reference documents are included in the OMS bidder’s library and apply to this task order:

● Standards for Satellite Product and Services Review Board (SPSRB) Satellite Product Development Projects Memorandum

● Office of Satellite Ground Services (OSGS), Programs, Engineering and Technology Division (PETD) Five-Year Sustainment Plan

● Office of Satellite Ground Services (OSGS), Environmental Satellite Processing Center (ESPC) Five-Year Plan

● Environmental Satellite Processing Center (ESPC) Transitions to PSDI Operations Plan (T2O) June 2019

● Product System Development and Integration (PSDI) Five-Year Plan

● Office of Satellite Architecture and Advanced Planning (OSAAP) Enterprise Algorithm

Implementation Plan

● NESDIS Ground Enterprise (NGE) Technical Architecture (TA)

● NESDIS-PR-1110.1 System Engineering

● NOAA Standard No. S24.806, Software Development, Maintenance, and User

Documentation

● NESDIS Development/External Services Security Requirements

● OSGS Software Development Life-Cycle (SDLC)

● Secure Software Development Life-Cycle (SSDLC) requirements

● ESPC Performance Requirements extracted from Enterprise System Requirements

Document (ESRD) v2.3

● Environmental Satellite Processing and Distribution System (ESPDS) Development

● OSGS-ESPDS-ESRD-R13

● Enterprise System Requirements Document (ESRD) Version 2.3

3.0 General Requirements

Section 3.0 applies to all sustainment areas of support and encompasses the following general sustainment requirements.

3.1 General Sustainment Requirements

PWS-TO3-GS01: The Contractor shall document and deliver a detailed Sustainment Plan [Deliverable] where an initial draft is submitted with the proposal response and a final delivered within 120 days after contract award. The Contractor shall provide monthly updates to the Sustainment Plan.

The exception to the Sustainment Plan deliveries within 120 days is the ESPC Sustainment Phase-In Transition Plan. The ESPC Sustainment Phase-In Transition Plan initial draft shall be submitted with the proposal, a final delivered within 60 days after contract award, and the transition completed within 120 calendar days after contract award.

The Sustainment Plan shall contain plans, documents and reports detailed below:

● Sustainment Project Plan (PWS-TO3-GS02)

● Sustainment Stakeholder Contact List (PWS-TO3-GS03)

● Integrated Sustainment Schedule (PWS-TO3-GS04)

● Sustainment Inventory Baseline (PWS-TO3-GS05)

● Software Sustainment Plan (PWS-T03-SS01)

● Hardware Sustainment Plan (PWS-TO3-HW01)

● Antenna Sustainment Plan (PWS-TO3-SER01)

● Extended Maintenance Plan (PWS-TO3-GS20)

● Sustainment Requirements Baseline (PWS-TO3-SE02)

● ESPC Sustainment Phase-In Transition Plan (PWS-TO3-PM06)

PWS-TO3-GS02: The Contractor shall document and deliver a detailed Sustainment Project Plan [Deliverable] that contains a project plan for each of the legacy ground systems for Government approval. This plan shall include all items for sustainment, proposed hardware/software sustainment solution by subsystem and location, tasks required to implement, and task schedule. Implementation tasks for the Sustainment Project Plan shall include the following:

● Complete an initial draft submitted with the proposal response, and a final document delivered within 120 days after contract award as part of the Sustainment Plan.

● Hardware/firmware sustainment solution (or consolidation approach).

● Approach for all software modifications and migration of all code (commercial off the shelf (COTS) and custom code, as applicable).

● List of documentation impacted (e.g. requirements documentation, support or license agreements, design documentation, testing documentation, updated system baseline documents, or configuration documents, etc.), generated or modified for configuration management purposes.

● Milestones planned for sustainment activities (key reviews, technical reviews supporting code, requirements verification, transition to operations, etc.) as detailed in the Integrated Sustainment Schedule (ISS).

● Testing approach applicable for each sustainment solution.

● Evaluation of proposed sustainment activities covering planned term after sustainment solutions are implemented (support agreement terms for hardware maintenance and software license).

● Travel planned to support sustainment activities.

Sustainment Project Plan Reports (Deliverable) are subsets of the IDIQ Project Management Plan reporting detailed in Task Order 1, and shall include the following for sustainment related activities:

● Sustainment program monthly status report including work performed, status of schedule (indicating completion percentage for each item), sustainment activities status (estimates, percent complete broken out by function level modules/ components), financial data (detailed summary of hours/cost expended by CLIN/WBS), risks (changes/updates to the risk registers, and updated milestones), staffing levels, performance metrics, status of IT security compliance, action items, and issues for NOAA attention.

● The Contractor shall provide one (1) report per month to the Project Manager (PM) or COR. All milestone dates should reflect deliverables, and key decision points.

● Weekly status reports [Deliverable see TO1] describing problems/delays (causes, corrective actions taken/planned, impact to schedule, planned efforts for next week.

PWS-TO3-GS03: The Contractor shall interface with stakeholder groups within NOAA- NESDIS to determine sustainment needs for diverse legacy ground systems. Government point of contacts may include international partners. The Contractor shall establish a Sustainment Stakeholder Contact List [Deliverable], as part of the Sustainment Plan where an initial draft is submitted with the proposal response in the Sustainment Plan, and a final delivered within 120 days after contract award.

PWS-TO3-GS04: The Contractor shall create and maintain an Integrated Sustainment Schedule (ISS) [Deliverable] for planned work and applied skilled resources where an initial draft is submitted with the proposal response and a final delivered within 120 days after contract award.

The ISS is a separate deliverable from the IDIQ PWS Integrated Master Schedule (IMS) but critical sustainment milestones from the ISS shall be integrated into the IDIQ PWS IMS. Factors to be considered for ISS that impact system availability include: critical weather days, launch and post-launch checkout, IT-related “hard and soft” system freezes and COOP exercises.

The ISS shall span the entire contract period of performance. Sustainment milestones shall include (but not be limited to) contract deliverables, engineering assessment dates, sustainment solution development and implementation key dates, technology refresh dates, license and maintenance agreement renewals, software releases, testing dates or periods, key technical review dates (e.g. pre-ship, factory acceptance, site acceptance, Operational Readiness Review (ORR)’s etc.).

The Contractor shall provide one (1) sustainment schedule per month to the Government Project Manager (PM) and Contracting Officer Representative (COR), or as requested. Critical milestone dates should reflect key deliverables, key decision points, system readiness or availability. All milestones having external dependencies shall reflect a readiness date relative to the actual completion of the external dependency.

PWS-TO3-GS05: The Contractor shall conduct a Sustainment Inventory Baseline [Deliverable] of sustainment assets for each of the ground systems detailed in Table 2-1. This information shall be documented in the Sustainment Plan where an initial draft is submitted with the proposal response and a final delivered within 120 days after contract award. The Contractor shall document the schedule and status of the technology refresh for each of the hardware, software and firmware components of the ground systems to the end of the sustainment task order.

PWS-TO3-GS06: The Contractor shall prepare and deliver documentation and services listed in Appendix A. Deliverables List for Task Order 3, as scheduled.

PWS-TO3-GS07: The Contractor shall plan and execute sustainment transition activities per Section 3.1.3 of the OMS IDIQ PWS and Section 2.2 (Contract Transition) of Task Order 1.

PWS-TO3-GS08: The Contractor shall coordinate migration of sustainment requirements for ground systems with existing contracts.

PWS-TO3-GS009: The Contractor shall plan sustainment activities for legacy ground systems as well as subsystems that support joint international partnership agreements processing legacy data. Beyond the end of the POES mission, there are several subsystems that may need to be sustained supporting exchanges of equipment and global data based on joint international partnerships agreements. These include the Initial Joint Polar-orbiting satellite system (IJPS), and Satellite Operations Management Subsystem (SOMS) supporting SARSAT.

PWS-TO3-GS10: The Contractor shall provide sustainment and sustainment planning of ground station antennas and support antenna equipment at the primary and remote work locations detailed in Section 2.1 of this task order.

PWS-TO3-GS11: The Contractor shall plan for and sustain software as needed at all primary and remote locations identified in Section 2.1 of this task order.

PWS-TO3-GS12: The Contractor shall plan for and sustain hardware as needed at all primary and remote locations identified in Section 2.1 of this task order.

PWS-TO3-GS13: The Contractor shall coordinate with Government facility owners configuration management processes before implementation of new ground system hardware, software or firmware, networks, antennas and RF equipment.

PWS-TO3-GS14: The Contractor shall provide support for the sustainment of continuity of operations (COOP) assets as detailed in Section 4.1.1.3 of this task order.

PWS-TO3-GS15: The Contractor shall meet or exceed existing Ground System performance standards and requirements for all sustainment activities conducted under Task Order 3.

PWS-TO3-GS16: The contractor shall identify, plan for and execute a refresh of each asset itemized in the Sustainment Inventory Baseline as detailed in PWS-T03-GS05, in accordance with the refresh timeline as established in the Sustainment Plan.

PWS-TO3-GS17: The Contractor shall develop and deliver a legacy ground system Extended Maintenance Plan [Deliverable] within 120 days of contact award for Government approval for each legacy ground system other than ESPC needing sustainment.

PWS-TO3-GS18: The Contractor shall not interfere with or compromise system operations while performing sustainment activities.

PWS-TO3-GS19: The Contractor shall be compliant with IT security requirements and follow the configuration management (CM) practices to sustain building out any additions with the mandated security controls in place including, but not limited to hardening the system to required standards, applying anti-malware, closing unused ports, and applying the principles of least access.

PWS-TO3-GS20: The Contractor shall obtain approvals for changes and implementation through an approved NESDIS CM process. Legacy ground systems shall be scanned for vulnerabilities and corrected prior to connection to an operational network. Input to required IT security documentation, such as changes to any security documentation, shall be provided by the Contractor. If the change results in a recertification of the system, then the Contractor shall provide supporting documentation.

3.1.1 System Engineering Support

The Contractor shall implement disciplined, repeatable System Engineering (SE) processes to ensure that sustainment projects remain compliant within budget, schedule, performance requirements and/or performance standards. Contractor processes shall employ a methodical, multi-disciplinary approach for the design, implementation, technical management, operations and maintenance, and retirement of a ground system. SE processes shall also be applied to antenna and radio frequency (RF) equipment supporting ground systems.

PWS-TO3-SE01: The Contractor shall ensure that sustainment projects remain within their commitments and constraints in terms of budget, schedule, technical scope and quality in accordance with NESDIS procedural requirements per NESDIS-PD-1111.1.

PWS-TO3-SE02: The Contractor shall provide and maintain requirements management process and related documentation. A Sustainment Requirements Baseline [Deliverable] shall be delivered as an initial draft submitted with the proposal response and a final delivered within 120 days after contract award. The Sustainment Requirements Baseline shall include performance requirements established and maintained throughout the contract period of performance. This baseline shall contain performance requirements and/or performance standard, security requirements, and facilities requirements for each ground system detailed in the scope of this task order.

PWS-TO3-SE03: The contractor shall provide an enterprise level System Engineering Management Plan (SEMP), and an initial tailored SEMP to the OMS contract addressing sustainment activities, with the proposal. A final tailored SEMP to OMS shall address sustainment processes covering operations, integration and test of hardware and software items, approved change requests, and testing (including regression, functional, stress, and system and end-to-end testing), and shall be delivered within 60 days after contract award.

PWS-TO3-SE04: The Contractor shall provide a Sustainment Life-Cycle Cost Prediction Report [Deliverable] for sustainment ground systems to be delivered within 120 days after award. The Contractor shall support OSGS in supplying data and artifacts when requested.

PWS-TO3-SE05: The Contractor shall identify ground system components that may have become obsolete to reduce ongoing costs, and/or other opportunities to reduce the operational cost. These items shall be coordinated with and approved by the Government.

PWS-TO3-SE06: The Contractor shall assist the Government with the support of interface control documents (ICD) and provide ICD updates and/or modification information [Deliverable] within 45 days from the implementation of sustainment capabilities. At a minimum, each ICD shall define:

● Interface mechanisms

● Network connectivity

● Protocols, error recovery, and security

● Any applicable file naming conventions

● Transaction content and formats

● Confirmation and reconciliation reporting

PWS-TO3-SE07: The Contractor shall provide artifacts that support engineering assessment (EA) and cost estimation, if requested. EAs identified and approved by the COR shall include details related to system performance analysis, capacity planning, and related cost over the performance period. Deliverables from engineering assessments may result in technical direction letters or contract modifications depending on the scope and magnitude of the request.

PWS-TO3-SE08: The Contractor shall develop work requests and configuration change requests for sustainment hardware solutions for primary and remote work locations detailed in Section 2.1 in this task order.

3.1.1.1 Antenna and Radio Frequency Equipment Systems Engineering

The Sustainment Plan shall include system engineering processes as applicable to antennas and radio frequency equipment for ground stations.

PWS-TO3-SER01: The Contractor shall deliver an Antenna Sustainment Plan [Deliverable] as an initial draft in the Sustainment Plan submitted with the proposal response and a final delivered within 120 days after contract award. The Antenna Sustainment plan will provide all prioritized support for engineering expertise, labor, materials, documentation services, and calibration required for the installation of new or replacement equipment, modification, major repair, and/or overhaul of existing equipment, alteration and construction to accomplish the specified technical refresh sustainment objectives.

PWS-T03-SER02: The Contractor shall conduct antenna design, RF link analysis, system architecture revision activities, including detailed block diagrams, interface specifications, cabling diagrams, component recommendations, and obtaining vendor pricing necessary to support sustainment requirements.

PWS-TO3-SER03: The Contractor shall perform analysis and assessment of all RF Ground System network infrastructure, provide network optimization recommendations, and proposed solutions for implementation that improve network data routing, data transfer efficiency, data integrity and delivery assurance via NOAA N-Wave-to-SOCC, ESPC and NOAA data centers (i.e., data compression, network accelerator, data transfer assurance algorithm or protocol etc.).

PWS-T03-SER04: The Contractor shall support the government by performing trade studies, technical feasibility of proposed solutions based on reliability and past performance of similar development tasks and/or delivered products. Additional tasks may be assigned as new requirements are defined and funded.

PWS-T03-SER05: The Contractor shall perform RF analysis and feasibility studies as required by the Government necessary to define upgrade requirements for antennas supporting future missions, such as Space Weather Follow-On mission (SWFO) and Metop Second Generation.

PWS-TO3-SER06: The Government may identify antenna assets for removal predicated on mission EOL, antenna utilization, study findings, obsolescence or other relevant factors.

PWS-T03-SER07: The Contractor shall perform risks analysis and mitigation planning on antenna subsystems.

PWS-T03-SER08: The Contractor shall obtain all approvals in accordance with local, state, federal, and international laws and regulations, including those affecting local labor mandates, any tariffs imposed on materials and labor. The Contractor shall deliver Regulatory reports [Deliverable} to include references, regulations and approvals.

PWS-T03-SER09: The Contractor shall identify, prepare, and obtain permission from the appropriate regulatory bodies for any required on-site construction permits in fulfillment of sustainment requirements.

PWS-T03-SER10: All RF sustainment equipment installations must comply with applicable international, national, state, and local codes and ordinances. The Contractor shall advise the Government, on a site-by-site basis, of the specific codes to which compliance is proposed and must be responsible for obtaining all required approvals from facilities and responsible Government organizations. The Contractor shall take all necessary actions to ensure compliance and approval. This includes obtaining and maintaining any National Telecommunication and Information Administration (NTIA)/Federal Communication Commission (FCC), or other governmental, or international authorizations for the operation of any communications network installed to support a sustainment solution.

3.1.1.2 Program Management Support

Program Management for Task Order 3 are specified under Task Order 1, Program Management.

In addition, the following requirements shall apply to Task Order 3 for Sustainment.

PWS-TO3-PM01: The Contractor shall ensure that sustainment projects comply within the Government constraints in terms of cost, schedule and technical scope.

PWS-TO3-PM02: (Ref. Task Order 1, PWS-TO1-QA01) The contractor shall follow their Quality Assurance Plan when performing sustainment activities detailed in this task order.

PWS-TO3-PM03: The Contractor shall manage all sustainment activities to ensure work is completed in a timely manner. This includes documenting all work performed, staff management communications (e.g., ensuring correct skill mix assignments, correct understanding of risks, etc.) per the deliverables in Appendix A.

PWS-TO3-PM04: Achieving the desired goals for the contract will require joint coordination between the Contractor and Government team. The Government will provide a set of priorities, as part of the OMS transition, which the Contractor shall use to establish a Release Backlog [Deliverable] and deliver within 120 days after award, detailing future modifications, enhancements and features. The release backlog shall be reviewed monthly. The implementation of changes from the release backlog provides the priority for implementing sustainment activities within funding constraints. The release backlog implementations shall follow established change management and release process as detailed in Task Order 1, Section 3.1.1

All planned implementation of priorities from the Release Backlog shall be reflected in the ISS and the status of implementations shall be regularly reported in the monthly Program Status Review Package detailed in Task Order 1. The release backlog process is detailed in Appendix B, Release Backlog and MoSCow Process. Modifications to the Release Backlog process may be recommended to the Government, and, if approved, reflected in a modified process document.

The final release backlog process, if modified, shall be approved no later than 1 month after contract start. Release Backlog reporting [Deliverable] shall be weekly as part of the weekly status and monthly reporting detailed in Task Order 1.

3.1.1.2.1 Contract Transition

Transition of sustainment activities to the contract is a programmatic activity managed by the Contractor and incumbent contractor(s), in coordination with the Government.

The dates and timelines of work scope transition herein represent planning timelines only. The Government reserves the right to extend the performance period of any existing legacy sustainment contract. These activities may impact actual timelines for new contract transition activities. Should this occur, the Contractor shall capture and reflect these activities within the OMS IMS under Task Order 1.

PWS-TO3-PM06: The Contractor shall develop and deliver an ESPC Sustainment Phase-In Transition Plan [Deliverable] as an initial draft submitted with the proposal Sustainment Plan and a final delivered within 60 days of contract award. The ESPC Sustainment Phase-In Plan shall support and the Contractor shall execute the transition within 90 calendar days of award.

The elements identified in the ESPC Sustainment Phase-In Transition Plan shall be fully managed and dispositioned to include, but not limited to:

● Sustainment Concept

● Sustainment Performance Requirements

● Sustainment Acquisition Strategy

● Sustainment Design Characteristics (e.g. including ground system and design specifications)

● List by ground system of hardware, software, firmware ground support elements and sustainment needs

● Integrated Sustainment Schedule

● List of high-risk areas that could impact system sustainment

● Special Interest Items

PWS-TO3-PM07 (Ref. Task Order 1, PWS-TO1-CT02): The Contractor shall transition work performance from any incumbent contractor(s) to itself for all ground system elements. The Contractor shall manage the transition with no interruption in ongoing services. Typical activities occurring in transition include:

● Staffing

● Training

● Transfer of operations, inventory, and assets

● Transfer of accounts, passwords, and permissions

● Monitoring of maintenance and sustainment activities

● Configuration control, administration, Book Boss custodianship of data sets, software scripts, documentation, procedures, and checklists

● IT Security activities

● Hardware and software license management, and warranty activity

PWS-TO3-PM08: The Contractor shall document and report verbally the ESPC Sustainment Phase-In Transition Plan Reports [Deliverable] status report to the Government PMO weekly and monthly at the OMS program review meeting.

PWS-TO3-PM09: The Contractor shall provide all labor, resources, and material necessary to sustain the legacy ground systems.

PWS-TO3-PM10: The Contractor shall keep metrics on any item in the Task Order 3 Performance Requirements Summary (PRS) table in Section 6 of this Task Order.

PWS-TO3-PM11: The Contractor shall develop and deliver an initial ESPC Sustainment Phase-Out Transition Plan [Deliverable] outline one year before the end of the task order for Government approval. The Contractor shall deliver the final Plan 60 days before the end of the task order for Government approval. The Phase-Out Transition Plan shall include the following:

● Workforce Transition

● Work execution during transition

● Subcontract transitions

● Property transition (GFE, user accounts & passwords)

● Knowledge transfer

● Schedule

● Handover and acceptance

3.1.2 Technology Sustainment Support

Sustainment activities include the modernization (or refreshing) of existing hardware and software and adding new capabilities to meet Government requirements. Sustainment support activities include support for software and hardware sustainment solutions depending on the scope and magnitude of the need.

3.1.2.1 Software Sustainment Solutions

PWS-TO3-SS01: The Contractor shall deliver a Software Sustainment Plan [Deliverable] where the initial draft is submitted with the proposal response in the Sustainment Plan, and a final delivered within 120 days after contract award. The Software Sustainment plan shall detail software support of the following including existing source code modifications. The Contractor shall identify source code and/or database changes, ensure a clean software compile, and fully document the changes per the configuration management processes detailed in Task Order 1, Section 3.3.1. Test and baseline of all changes shall be in accordance with a Government approved source code control sustainment standard operating procedure. Sustainment test plans and submitted code [Deliverable] shall be delivered as needed and reviewed by the Government.

Testing shall be in accordance with an approved software development guide prior to submitting modified code for integration and test. The Government will perform an ORR before the Contractor is allowed to implement any modified code in the operations environment. The Contractor shall document operational impacts for any Configuration Change Requests (CCR) that affect operations and immediately report these impacts to the Project Manager and COR.

PWS-TO3-SS02: The Contractor shall provide weekly updates for open CCRs and report progress of CCR closure in the Configuration Change Requests Report (Task Order 1 Section

3.1.1 Configuration and Document Management (PWS-TO1-CM02); Deliverable ID XX).

Perform all required activities to close CCRs per the agreed schedule, and elevate or expedite any activities required to maintain the CCR closure schedule.

PWS-TO3-SS03: The Contractor shall deliver a Software Sustainment Life-Cycle Plan [Deliverable] supporting software development and test to be delivered within 120 days after award as part of the Software Sustainment Plan. Software assurance practices must address trustworthiness, dependability (correct and predictable execution), conformance, and survivability.

● Software delivered shall conform to NOAA Standard No. S24.806, Software Development, Maintenance, and User Documentation, and shall be consistent with the contractor-approved standards and practices as well as the requirements of 1.5.3.1, NESDIS Development/External Services Security Requirements. In addition, the contractor shall comply with all OSGS Software Development Life-Cycle (SDLC) and SDLC requirements.

PWS-TO3-SS04: The Government will review the Contractor developer’s process, standards, tools, and tool options/configurations to determine if the process, standards, tools, and tool options/configurations selected and employed can satisfy the requirements for a system test and development environment.

PWS-TO3-SS05: The Contractor shall follow a documented development process for approved software changes that:

● Explicitly addresses security requirements.

● Identifies the standards and tools used in the development process (for example, programming languages).

● Documents the specific tool options and tool configurations used in the development process.

● Documents, manages, and ensures the integrity of changes to the process and/or tools used in development to enable accurate supply chain risk assessment and mitigation, and requires robust configuration control throughout the lifecycle (including design, development, transport, delivery, integration, and maintenance) to track authorized changes and prevent unauthorized changes.

PWS-TO3-SS06: Software development and test for legacy ground systems sustainment shall be in accordance with a contractor generated Sustainment Plan as defined in PWS-TO3-GS01.

PWS-TO3-SS07: The Contractor shall define software builds at the key sustainment solution review (e.g. CDR, if applicable) in a logical sequence for implementation. Each build shall meet a specific and identifiable set of requirements and provide capabilities that can be demonstrated to the Government via a comprehensive build test. A description of all associated binaries, libraries, and scripts shall be included. The contractor shall give an overview of how builds will be distributed and patches applied.

PWS-TO3-SS08: The Contractor shall use established NESDIS, NOAA, and Department of Commerce (DOC) Enterprise licensing agreements for COTS products. There are also mandatory use policies in place for some products. The determination of use for a particular software package will be made on a case-by-case basis, with an emphasis toward meeting established Enterprise-wide software mandates.

PWS-TO3-SS09: The Contractor shall request permission prior to using open source, shareware or freeware software in any product or system delivered under this contract. The contractor shall identify any project dependencies on such software. Any request to use any unsupported software should include a statement of risk incurred by its use. The statement of risk shall at a minimum address options for licensing and maintenance support. Whenever possible, shareware and freeware should be compiled from source code and delivered to NOAA.

PWS-TO3-SS10: The contractor shall plan for and sustain software licenses supporting legacy ground systems as well as at the remote and backup facilities.

PWS-TO3-SS11: The Contractor shall support new software sustainment code reviews and testing for scheduled sustainment related software releases, and any fixes to ensure they function as intended.

3.1.2.2 System Integration, Installation and Test of Sustainment Solutions

PWS-TO3-SI01: The Contractor shall conduct a program to test and demonstrate system compliance through verification and validation of requirements. Following the contractor’s internal test plan and procedures, the contractor shall perform the following formal tests during the acceptance of the developed/re-hosted software/hardware elements:

● Targeted Security Test & Evaluation (ST&E) at the Contractor site, prior to Pre-shipment Test (PST)

● PST at the Contractor site

● Integration Level Test (ILT) at the NOAA site

● Parallel Operations Testing (POT) at the NOAA Site

● Final Acceptance Test (FAT)

The Government may determine that its best interests are served by having the contractor perform some or all of this work remotely when appropriate. On a case-by-case basis, the contractor shall provide justification and shall obtain written Government approval prior to conducting any/all remote testing.

PWS-TO3-SI02: The Contractor shall submit test plans (Deliverable) for Government review and approval addressing the sustainment related testing. Initial drafts shall be submitted two weeks prior to the sustainment solution technical review meeting (e.g. CDR). Any Government comments will be incorporated into the final test plan, which is due no later than 2 weeks prior to the test.

Each test plan shall comply with the following:

● All requirements being tested have clearly identified success criteria.

● Testing performed from accounts with “least privilege” and using the account profile expected to be used by the end-user of the function being tested or demonstrated.

● Input data shall be actual operational data, wherever possible.

● Include a description of the impact on site operations and personnel during the installation, ILT and FAT phases.

● Identify all NOAA facilities and personnel support required to perform the tests.

PWS-TO3-SI03: The contractor shall submit a draft Sustainment Installation Plan [Deliverable] two weeks prior to the sustainment solution technical review meeting, and at a minimum, include:

● Installation timeline

● Procedures to be followed

● Coordination with the Government System Engineer regarding facilities availability

3.1.2.3 Hardware Sustainment Solutions

Ground station antennas enable satellite mission communications to Ground Systems via Radio Frequency (RF) equipment and supporting ground infrastructure.

PWS-TO3-HW01: The Contractor shall deliver a Hardware Sustainment Plan [Deliverable] where an initial draft is submitted with the proposal response in the Sustainment Plan, and a final delivered within 120 days after contract award. The Hardware Sustainment Plan captures sustainment support of hardware items to include antennas, RF equipment and facilities including but not limited to those defined in Section 2.0, Table 2-1 Ground Systems & Systems.

PWS-TO3-HW02: The Contractor shall provide procurement support to purchase all hardware to implement sustainment solutions.

PWS-TO3-HW03: The Contractor shall perform (in concert with the Government) all integration and testing, modifications and/or porting of existing software to new hardware platforms that interface with existing operational systems.

PWS-TO3-HW04: The Contractor shall provide support in the development of any acquisition packages necessary to acquire hardware for sustainment solutions and technology refreshes, as needed.

PWS-TO3-HW05: The Contractor shall support the planning for sustainment activities for hardware licenses for ground systems, for all identified work sites under section 2.1.

PWS-TO3-HW06: The Contractor shall support new hardware item technical reviews and testing for scheduled deployments, and provide any required fixes to ensure the solution for deployment functions as intended.

PWS-TO3-HW07: The Contractor shall support sustainment activities related to reconfiguration of hardware and/or network devices, if needed.

PWS-TO3-HW08: The Contractor shall provide power, cooling, and weight estimates for any sustainment hardware solution to the government for approval. The contractor shall develop work requests and all configuration change requests required to install equipment in NOAA facilities.

PWS-TO3-HW09: For satellites identified as reaching the end of operational life (EOL), the Contractor shall provide planning for and execute decommissioning activities of the associated ground system hardware. This includes execution of the removal and disposal of ground infrastructure equipment in accordance with all pertinent Government regulations, guidelines and safety standards.

4.0 Ground Systems Requirements

Legacy missions are supported by satellites superseded by newer satellites. However, satellite data and ground system transitions can take years to migrate to the new systems. Sustainment activities ensure that legacy data is accessible to the user community until full transition to replacement systems has occurred. Legacy ground system sustainment covers items including antennas and ground support equipment, mission control, ground networks and remote infrastructure. For many missions, some sustainment has recently occurred in technology refreshes that has minimized sustainment needs. ESPC is the exception, in that it processes legacy and newer mission data.

ESPC is the primary product processing ground system to be sustained and some capabilities may involve product transition to a NOAA Cloud service provider. The remaining OSPO ground systems sustainment are detailed in this section of the task order under legacy ground system extended maintenance and special projects.

The legacy systems for Task Order 3 sustainment are detailed in Table 4.0.

Table 4.0 Legacy Ground Systems & Systems Details

Legacy System Transition to Operations

Technology Refresh Planned Completion

Dates

Mission End

ESPC January 2020 [TBD] N/A

GOES N/O/P Month 2025 November 2019 2026 Q2

POES January 2017 [TBD] 2021 Q1

NJGS February 2020 February 2020 2025 Q1

GOES I/O November 2022 December 2019 N/A

DSCOVR July 2021 December 2020 2024 Q4

MSL September 2019 FY22 Q1 N/A

DCS April 2021 March 2019 N/A

SARSAT Month 2021 [TBD] N/A

4.1 Product Processing Sustainment

4.1.1 Environmental Satellite Processing Center (ESPC)

The requirements in the following sections cover sustainment of the Environmental Satellite Processing Center (ESPC) bounded by the Federal Information Security Management Act

(FISMA) System NOAA5045 per the IDIQ PWS. ESPC processes NOAA polar and geostationary environmental satellite data and products, as well as data and products received from non-NOAA satellite assets. ESPC subsystems include data ingest, product generation (PG), product distribution and access (PDA), continuity of operations, and infrastructure hardware, software and services. Different parts of the ESPC enterprise hardware and software were acquired over different periods of time over the period of performance of the contract. The Contractor shall establish a cadence in the Sustainment Plan on which subsystems and components will need a technology refresh necessary to replace software and hardware that is considered end-of-life and no longer supported by the manufacturer.

PWS-TO3-E01: The Contractor shall provide sustainment support for ESPC data ingest, product generation, services, data and system access in accordance with sustainment activities as developed in the Sustainment Plan and conducted in accordance with Section 3.1 of this task order.

4.1.1.1 ESPC Product Generation

ESPC PG receives ancillary data, which includes output of NOAA weather models and other geophysical parameters through file transfers from external sources. PG provides the ESPC capability, based upon the Suomi National Polar-Orbiting Partnership (S-NPP) Data Exploitation (NDE) software. The NDE product management services provide foundational infrastructure capabilities upon which the other NDE services rely. These include product management, monitoring and control, and infrastructure utilities.

PWS-TO3-E02: The Contractor shall provide sustainment support for ESPC PG development and operational environments which includes data generation capabilities for ground systems.

Service elements of PG include:

● NDE Business Services provide the core business logic capabilities associated with NDE product generation. These include job factory (PG master/scheduling functionality), processing node, and algorithm execution capabilities.

● NDE Data Receive/Delivery Services provide services that enable data ingest from data providers and delivery of data to ESPC access PDA services for distribution to consumers.

● NDE Gateway Services provide operator/administrator-facing services to enable monitoring of the NDE data ingest and product generation functions via the ESPC Product Management Portal.

4.1.1.2 ESPC Product Distribution and Access

ESPC product distribution is comprised of two components, the PDA and High Rate Information Transmission / Emergency Managers Weather Information Network (HRIT/EMWIN). The PDA segment provides timely distribution of environmental satellite data, data products, and ancillary data, provided by multiple remote-sensing projects to the near real-time user community. The HRIT/EMWIN acquires satellite images from the PDA, along with EMWIN data products like storm warnings, surface weather maps, and tropical advisories from the National Weather Service. PDA equipment includes:

● PDA/HRIT hardware

● PDA hardware

● PDA software

● PDA licenses

PWS-TO3-E03: The Contractor shall provide sustainment support for ESPC PDA development and operational environments which includes data distribution and access capabilities for legacy systems. Elements of the PDA include: Jason 3, GOES/POES products, and ancillary data, as well as users of this data to include the NOAA Line Offices, Department of Defense (DoD), and the Comprehensive Large-Array Data Stewardship System (CLASS).

PWS-TO3-E04: The Contractor shall provide hardware and software sustainment support for ESPC HRIT/EMWIN. The HRIS/EMWIN provides the ability to interface with the legacy GOES Low-Rate Information Transmission (LRIT) and GOES-R HRIT antenna systems in order to uplink DCS data, EMWIN data, National Hurricane Center (NHC) data, and certain product files for transmission via the Legacy GOES and GOES-R satellites to LRIT and HRIT users.

Sustainment includes specialized hardware known as Uplink Processors to interface with the Legacy GOES and GOES-R antenna systems for LRIT/HRIT uplink and downlink that are found at the following sites:

● Wallops Command and Data Acquisition Station (WCDAS) in Wallops Island, VA (primary Legacy GOES LRIT and GOES-R HRIT)

● Fairbanks Command and Data Acquisition Station (FCDAS) in Fairbanks, AK (backup Legacy GOES West LRIT)

● GOES-R CBU in Fairmont, WV (backup GOES-R HRIT)

4.1.1.3 ESPC Continuity of Operations

In the event of a catastrophic failure of the NSOF that causes all or part of ESPC processing to fail, a failover of all ingest, product generation and distribution to the CBU occurs.