Attachment 5 - Sustainment Functional Area - Sample Task Order.docx

Attachment J-5 Sustainment Functional Area - Sample Task Order

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

Office of Satellite and Product Operations (OSPO) and Office of Common Services (OCS)

NESDIS Consolidated Antenna and Ground System (NCAGSS)

Task Order 4- Antenna Ground System Sustainment

Performance Work Statement (PWS)

April 2026

Prepared by:

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

Table of Contents

1.0 Overview

The purpose of the Statement of Work (SOW) for the base Indefinite Delivery, Indefinite Quantity (IDIQ) is to describe the services the Contractor(s) shall provide to support the NESDIS Antenna as a Service (NAaaS) program. These services are essential to provide NOAA/NESDIS with the flexibility and responsiveness required to support the scope, complexity, and evolution of how NOAA/NESDIS acquires, manages, and operates antenna services. A Program Integrator (PI) Task Order (TO) will be awarded to one vendor and multiple TOs with specific service requirements (i.e., operations, maintenance, and sustainment) will be awarded within the scope of the IDIQ over the period of performance. The PI will ensure integration across all task orders supporting the NAaaS program.

The Antenna Ground System Sustainment TO4 is a sample sustainment TO that details Contractor(s) implementation of sustainment activities per the NESDIS Consolidated Antenna and Ground Systems Services (NCAGSS) (IDIQ SOW) Sections 3.1 (General Requirements) and 3.5 (Sustainment). TO4 covers the managed planning, transition/migration, and implementation activities by the Contractor(s) of legacy and new antenna ground systems from incumbent Contractor(s). Multiple antenna specific sustainment TOs will be awarded over the contract period of performance. This TO4 supports:

· Technology refresh (upgrades) to designated antenna ground systems and subsystems

· Technology refresh (upgrades) of infrastructure (e.g. operational tools) applicable to the NAaaS antenna ground systems and subsystems

· Development and implementation of new (next generation) antenna ground system capabilities

2.0 Scope

The NAaaS objective for using sustainment conducted under this TO is to implement a systematic effort to streamline and optimize the NAaaS antenna ground system enterprise. Sustainment activities include development leveraging technology advancements and improvements to extend the system life to meet program-life requirements.

This Antenna Ground System Sustainment TO addresses scope for technology related sustainment activities and associated deliverables. Sustainment activities include larger scale and pre-planned activities to develop, modernize, or enhance the applicable legacy antenna ground systems and subsystems. The Contractor(s) should demonstrate an ongoing commitment to innovative sustainment solutions, where applicable, that promote NESDIS enterprise architectural goals and streamline services, while minimizing associated costs and risks.

Appendix A, in this TO4, is a subset of the list in the IDIQ SOW Appendix A, which lists the Antenna Ground Systems the Office of Satellite Product Operations (OSPO) currently operates, maintains, and/or sustains. The Office of Common Services (OCS) will manage the development and acquisition of antenna services for the NAaaS program. Appendix B contains the Sustainment deliverables. Appendix C contains three sample sustainment use cases for the Contractor(s) to estimate and provide with the proposal submission. Appendix D contains the acronyms and meaning.

The Appendix A in the base IDIQ SOW contains all the current antenna ground systems that may need sustainment under this contract, however the scope may include other antennas at a future time. This sample TO pertains to general antenna ground systems sustainment requirements used to establish a pool of sustainment Contractor(s). Once the pool is developed separate antenna specific sustainment TOs will be issued based on Government priorities, Contractor(s) capabilities, and funding constraints. Sustainment TOs include designated antenna ground systems, infrastructures, upgrades and new antenna ground systems and components.

A significant focus of the NAaaS Program is the utilization of commercially available services wherever possible. The Contractor(s) shall consider as part of technology refresh analysis the utilization of commercial antenna services. Included in this analysis will be a technology evaluation, a cost benefit assessment, as well as a risk assessment.

Sustainment activities for this TO include:

a. Coordinate sustainment activities with the NAaaS Program Integrator (PI) using meeting forums, reports and an active integrated approach to keeping sustainment information in a PI dashboard.

b. Provide project management resources and commensurate technical subject matter experts (SMEs) 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.

c. Identify NAaaS antenna ground system and subsystems items for sustainment support/upgrade.

d. Perform an analysis of alternatives considering build or buy options and opportunities.

e. 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.

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

g. 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.

h. Review all hardware on site for inclusion in sustainment planning and incorporated into the Integrated Sustainment Plan authored by the PI.

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

j. Deliver software compliant with NOAA/NESDIS standards and approved Contractor(s) standards.

k. Working 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.

l. Conduct all required hardware/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.

m. Deliver a Transition to Operations package [D-TO4-041] for new sustainment solutions.

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

o. Provide all training for the sustainment solutions implemented under the TO.

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

q. Investigate, evaluate and recommend new antenna ground system capabilities aligned with enterprise objectives to include adoption of pertinent commercial capabilities.

r. Align cybersecurity practices and compliance with Department of Commerce IT Security laws, regulations and standards to protect sensitive data and information systems from cyber threats.

s. Implement and demonstrate IT security controls that ensure data confidentiality, integrity and availability thereby reducing legal, financial and reputational risks.

Develop an inventory of parts to be included in the TO4 sample Sustainment Plan and the NAaaS Integrated Sustainment Plan authored by the PI. The inventory shall include details of specific antenna ground system assets to be refreshed, plans for new antenna ground system and antenna development, and system hardware and software components within three (3) years of obsolescence. Individual system inventories, drawings, descriptions, interfaces and recommendations are available in the NCGASS Acquisition Document Library.

The PI will be developing a Release Backlog detailing future modifications, enhancements, and features and the priority for implementing sustainment activities within funding constraints, government priorities, discretion and/or timing. Sustainment Contractor(s) are expected to coordinate sustainment activities with the Government and NAaaS PI and keep the Release Backlog up to date.

2.1 Place of Performance

The National Environmental Satellite, Data, and Information Service (NESDIS) Ground Enterprise (NGE) primary work locations are listed below but additional locations/sites such as CONUS and OCONUS may be added.

a. NOAA Satellite Operations Facility (NSOF) located in Suitland, Maryland

b. The NESDIS Consolidated Backup Unit (CBU) located in Fairmont, West Virginia

c. NESDIS Command and Data Acquisition (CDA) Station located in Wallops, Virginia

d. NESDIS Command and Data Acquisition (CDA) Station located in Fairbanks, Alaska

e. McMurdo Station located on Ross Island, Antarctica

f. NASA White Sands Complex (WSGT/WSC) Les Cruces, New Mexico

2.2 References

The most current edition of the following reference documents is included in the NCGASS Acquisition Document Library and apply to this TO:

a. OSPO System Descriptions

b. OSPO System Inventories

c. OCS Change and Configuration Management Process

d. OCS Systems Engineering Process Document, OCS 5820.01A October 3, 2016, Version 0.5

e. Satellite Products and Services Review Board Process

f. NESDIS Ground Enterprise (NGE) Technical Architecture (TA) User’s Guide, Version 2.0, 03 April 2019

g. NESDIS Antenna RF Handbook (Redacted)

h. NESDIS IT Systems Component Inventory Management Policy and Procedures

i. OCS Systems Engineering Process Document, OCS 5820.01A October 3, 2016, Version 0.5

j. NESDIS Ground Enterprise (NGE) Technical Architecture (TA) User’s Guide, Version 2.0, 03 April 2019

k. NESDIS Antenna RF Handbook (Redacted)

l. OSPO Configuration Management Plan

m. NESDIS Antenna-as-a-Service (NAaaS) Requirements Document

3.0 Requirements

In addition to the requirements in the IDIQ SOW Section 3.1 (General Requirements) and 3.5 (Sustainment) the following requirements are specific to this TO.

3.1 Project Management

Project management for TO4 is defined in the IDIQ SOW Section 3.1.1 (Program/Project Management). In addition, the following project management requirements apply to TO4 for Antenna Ground System Sustainment:

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

PWS-TO4-PM02: The Contractor(s) 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 Sustainment Deliverables in Appendix B.

PWS-TO4-PM03: Achieving the desired goals for the contract will require joint coordination between the Contractor(s), Government team, and NAaaS PI. The Government will provide a set of priorities, as part of the NCAGSS transition. The Contractor(s) shall coordinate with the NAaaS PI Release Backlog activities detailing sustainment future modifications, enhancements, and features. All planned implementation of priorities from the Release Backlog shall be reflected in the Antenna Systems Sustainment Project Plan and the status of implementations shall be reported monthly.

PWS-TO4-PM04: The Contractor(s) shall generate Contractor Metric Performance Reports [D-TO4-008] on items in the Performance Requirements Summary (PRS) table in Section 5 of this TO. The Contractor Metric Performance Report shall be delivered to the Government and PI as part of the weekly status report and aggregated in a monthly report.

a. Hardware and software sustainment

b. Documentation

c. Performance

d. Product or service evaluations

e. Verification and validation results

f. Incidents and problems from CCR administration.

PWS-TO4-PM05: The Contractor(s) shall deliver a Monthly Progress Report [D-TO4-029] and provide it to the PI. The report shall include:

a. Executive summary

b. Project details

c. Project scope and adjustments

d. Progress updates and milestones

e. Review of key performance indicators

f. Risk and opportunity management

g. Budget and financial performance

h. Stakeholder communications

i. Next steps and action items

j. Ground systems and antenna anomalies, incidents, and discrepancies as defined in the OSPO Incident Report Plan

PWS-TO4-PM06: The Contractor(s) shall provide, individually to the contracting officer, a Contract Financial Report [D-TO4-030] from sustainment task orders toinclude spend plans, invoicing, fund status, engineering assessments (EAs) and travel management. The Contractor(s) may adjust cost performance data from prior months only for a) the correction of administrative errors, b) routine accounting adjustments, or c) customer-directed changes. All such prior months’ adjustments shall be implemented in the current month and addressed in that month’s Consolidated Contract Financial Report by the PI.

PWS-TO4-PM07: The Contractor(s) shall provide an Associate Contractor Agreement (ACA) [D-TO4-031] for any portion of the NCAGSS contract requiring joint participation in the NAaaS related activities. The agreements should include the basis for sharing information, data, technical knowledge, expertise, schedules, and risks in accordance with Section H of the NCAGSS IDIQ Contract. The Sustainment ACAs shall be maintained by the PI.

PWS-TO4-PM08: The Contractor(s) shall provide an antenna ground system Sustainment Contractor Spend Plan [D-TO4-032] as detailed in the IDIQ SOW Section 3.1 k (General Requirements).

PWS-TO4-PM09: The Contractor(s) shall notify the Government of conduct project kickoff meetings reporting on progress, punch lists, schedule, sustainment activities, contract transition and provide meeting notes within 5 business days.

PWS-TO4-PM10: The Contractor(s) shall provide, report, and track contract performance metrics on items detailed in the Contractor(s)’s Service Level Agreement (SLA) as part of the monthly program management review conducted by the PI. Metrics shall be mutually agreed at the start of the contract, and may include modified or new metrics, as required, to accurately reflect contract performance.

PWS-TO4-PM11: The Contractor(s) shall conduct a monthly NAaaS Contract Review to review sustainment TO contracts planned or in work. The Contract Review shall be coordinated with the PI and involves analyzing the contract's language, assessing its enforceability, and confirming that it aligns with the NAaaS project objectives.

PWS-TO4-PM12: The Contractor(s) shall submit Class I and II changes to the Government for approval prior to implementation of change in accordance with the OSPO CM Plan.

PWS-TO4-PM13:. The Contractor(s) shall conduct studies and analyses on topics identified by the Government throughout the period of performance. The Contractor(s) shall document the results of the study tasks through a NAaaS Study Report [D-TO4-046).

PWS-TO4-PM14: The Contractor(s) shall conduct a project Kickoff meeting [D-TO4-047] within 10 days of the NCAGSS award. The project Kickoff meeting shall be conducted in person at the NOAA-Satellite-Operations-Facility (NSOF) and facilitate virtual participation

PWS-TO4-PM15: The Contractor(s) shall coordinate with the Government meetings with working groups, product teams, and vendor partners.

PWS-TO4-PM16: The Contractor(s) shall participate in Government required meetings or working groups as directed by the Government.

PWS-TO4-PM17: The Contractor shall conduct engineering peer reviews (EPR) on technical topics with participation with the Government and PI.

PWS-TO4-PM18: The Contractor(s) shall adhere to the NAaaS Safety Program as developed by the PI in accordance with the NOAA Safety and Environmental Compliance (SECO). Information can be found at https://sites.google.com/noaa.gov/occupational-safety-health /home?pli=1

PWS-TO4-PM19: The Contractor(s) shall conduct a Project Management Review [D-TO4-048] mid-month on a monthly basis that provides status of technical, schedule and cost performance, risks and issues to the Government. The PMR package shall be provided to the Government and PI 10 days prior to the review.

PWS-TO4-PM20: The Contractor(s) shall coordinate with the PI to ensure requirements from all NAaaS performance work statements, functional and performance specifications, contract deliverables, and any applicable documentation are flowed down to subcontractors performing work under each task order.

PWS-TO4-PM21: The Contractor(s) shall develop and deliver a NAaaS Sustainment Project Management Plan (PMP) [D-TO4-051] and coordinate with the PI.

3.1.1 Quality Assurance

PWS-TO4-QA01: The Contractor(s) shall provide and follow their project Quality Assurance Plan (QAP) [D-TO4-035] and project Quality Assurance Standard Operating Procedures (QASP) [D-TO4-036] when performing activities detailed in this TO. The QASP is coordinated with the PI, and explicitly describes Contractor processes and measures for subcontractor/ vendor performance and deliverables

PWS-TO4-QA02: The Contractor(s) shall plan and implement technical quality assurance in the project that encompasses hardware, software, and processes.

PWS-TO4-QA03: The Contractor(s) shall provide Quality Assurance Standard Operating Procedures (SOP) [D-TO4-037] at the start of the contract and update it annually or as requested by the CO.

PWS-TO4-QA04: The Contractor(s) shall provide, report, and track contract performance metrics as part of the monthly program management review conducted by the PI. Metrics shall be mutually agreed at the start of the contract, and may include modified or new metrics, as required, to accurately reflect contract performance.

PWS-TO4-QA05: The Contractor(s) shall participate in the Government’s process improvement activities. The Government will provide a SharePoint-based Action Information Management System (AIMS) or like system, for organizing its data calls, as well as Government approved tools such as JIRA for the Integrated Master Schedule (IMS).

PWS-TO4-QA06: The Contractor(s) shall support organizational data call requests.

PWS-TO4-QA07: The Contractor(s) shall follow NESDIS processes for sustainment activities closure to include removal of all items, to include equipment cabling after a sustainment refresh, upgrade or new development has been completed.

PWS-TO4-QA08: The Contractor(s) shall decommission, excess, or dispose of NAaaS ground system accountable hardware following refresh in accordance with the NOAA Property Manager and in coordination with the PI.

PWS-TO4-QA09: The Contractor(s) shall maintain reports and other data electronically on a Government system such a JIRA, or similar tool, that is interfaced with the Program Integrator dashboard to ensure collaboration and coordination of activities.

3.2 Contract Transition

Transition related requirements for TO4 activities are specified and to be managed by the Contractor(s) under the IDIQ SOW Section 3.2.8 and Program Integrator TO1.

PWS-TO4-CT01: The Contractor(s) shall provide a Contract Phase-In Transition Plan [D-TO4-002] with a checklist for the PI of all required tasks and activities to complete the transition successfully. The initial Phase-in Transition Plan shall be submitted with the proposal response, and a final after contract award. Transition plans shall include:

a. Proposed Contractor Staffing and Government support staffing levels.

b. Staffing, including Government site access, as appropriate.

c. Training and general knowledge transfer.

d. Process for completion of in-progress Work Requests under development by the incumbent contractor.

e. Transfer of operations, inventory, and assets.

f. Transfer of accounts, passwords, and permissions.

g. Access to Government Configuration Management systems.

h. Transfer and establishment of a controlled Factory baseline representing the deployed system

i. Configuration control, administration, software scripts, documentation, procedures, and checklists.

j. Establishment, installation, and checkout of a Contractor Operational Support Location (OSL), Factory Development Environment (FDE), and Factory Test Environment (FTE).

k. Confirmation of the ability of the Contractor OSL to interface with the Government system at the deployed sites.

l. Confirmation of the ability of the FDE and FTE to test new or modified software with the return of test data back to NAaaS.

m. Management of hardware and software licenses, warranty and recommended spares activity for Contractor managed property.

n. Monitoring of sustainment activities to include IT security activities

1. List of existing sustainment efforts addressed (completed or in work) in NCAGSS contract

2. List of sustainment efforts addressed (completed or in work) by legacy contracts

3. List of new sustainment efforts addressed in NCAGSS contract

PWS-TO4-CT02: The Contractor(s) shall deliver a preliminary Contract Phase-Out Transition Plan [D-TO4-003] with a checklist and final plan submitted to Government and PI for approval one year prior to the end of the contract to the PMO.

3.3 Sustainment

3.3.1 General

PWS-TO4-GS01: The Contractor(s) shall provide a general Sustainment Plan [D-TO4-033] where an initial draft is submitted with the proposal response and a baseline of the individual plans comprising it shall be delivered after contract award. The Contractor(s) shall provide quarterly updates to the individual deliverables that comprise the general Sustainment Plan. The general Sustainment Plans will be incorporated into the TO1, PI Integrated Sustainment Plan. The general Sustainment Plan shall contain the following deliverables detailed below:

a. Sustainment Project Milestone Plan [PWS-TO4-GS04]

b. Software Sustainment Plan [PWS-T04-SS01]

c. Hardware Sustainment Plan [PWS-TO4-HW01]

d. Obsolescence Management Plan [PWS-TO4-SER02] PWS-TO4-GS02: In collaboration with the PI, the Contractor(s) shall document and deliver a detailed Antenna Systems Sustainment Project Plan [D-TO4-001] that contains a project plan for each of the antenna 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. With collaboration from the PI, implementation tasks for the Antenna Systems Sustainment Project Plan shall include the following:

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

b. Hardware/firmware sustainment solution (or consolidation approach; build vs. buy).

c. Approach for all software modifications (Commercial Off the Shelf (COTS) and custom code, as applicable).

d. 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.

e. Develop test procedures and seek Government approval within 30 days of testing.

f. 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).

g. Testing approach applicable for each sustainment solution.

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

i. Travel planned to support sustainment activities.

PWS-TO4-GS03: The Contractor(s) shall receive sustainment requirements exclusively from the NAaaS program. Government points of contacts may include international partners. The Contractor(s) shall establish a Sustainment Stakeholder Contact List [D-TO4-004] as part of the general Sustainment Plan where an initial draft is submitted with the proposal response in the general Sustainment Plan, and a final delivered after contract award.

PWS-TO4-GS04: The Contractor(s) shall create and maintain a three to five-year Sustainment Project Milestone Plan (PMP) [D-TO4-016] for planned work. The initial draft is submitted with the proposal response and a final delivered after contract award. The PMP is a separate deliverable from the TO1 Program Integrator, Integrated Master Schedule (IMS) but critical sustainment milestones from the PMP shall be integrated into the TO1 IMS. Factors to be considered for the PMP are those that impact system availability to include critical weather days, launch and post-launch checkout, IT-related “hard and soft” system freezes, and COOP exercises.

The ISS shall encompass the five-year period of performance for TO4. 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(s) shall provide an Integrated Sustainment Schedule [D-T04-005] per month to the Government Project Manager (PM) and Contracting Officer’s Representative (COR), and PI, 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-TO4-GS05: The Contractor(s) shall conduct a Sustainment Inventory Baseline [D-TO4-006] of sustainment assets for each of the antennas ground systems detailed in Appendix A of this TO. This information shall be documented in the general Sustainment Plan where an initial draft is submitted with the proposal response and a final delivered after contract award. The Contractor(s) 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 TO. The Contractor shall coordinate with the PI to support the program NAaaS Asset Inventory Report.

PWS-TO4-GS06: The Contractor(s) shall prepare and deliver documentation and services listed in Appendix B, Deliverables List for TO4, as scheduled.

PWS-TO4-GS07: The Contractor(s) shall plan and execute sustainment transition activities detailed in Section 3.5 of the IDIQ SOW.

PWS-TO4-GS08: The Contractor(s) shall coordinate migration of sustainment requirements for ground systems with existing contracts.

PWS-TO4-GS09: The Contractor(s) shall provide sustainment and sustainment planning of ground station antennas and support antenna equipment at the primary and work locations/sites detailed in Section 2.1 of this TO.

PWS-TO4-GS10: The Contractor(s) shall plan for, and sustain software as needed at all locations/sites identified in Section 2.1 of this TO.

PWS-TO4-GS11: The Contractor(s) shall plan for, and sustain hardware as needed at all locations/sites identified in Section 2.1 of this TO.

PWS-TO4-GS12: The Contractor(s) shall coordinate with Government facility owners using the OCS Change and Configuration Management Process before implementation of new hardware, software or firmware, networks, antennas and RF equipment.

PWS-TO4-GS13: The Contractor(s) shall provide management support for the sustainment of continuity of operations (COOP) assets of this TO.

PWS-TO4-GS14: The Contractor(s) shall meet or exceed existing Ground System performance standards and requirements for all sustainment activities conducted under TO4, Section 4.0.

PWS-TO4-GS15: The Contractor(s) shall identify, plan for, and execute a refresh of each asset itemized in the Sustainment Inventory Baseline, in accordance with the refresh timeline as established in the general Sustainment Plan.

PWS-TO4-GS16: The Contractor(s) shall employ deployment strategies that will minimize the risk of interference, loss of downtime (to include critical weather days), or compromise system operations while performing sustainment activities.

PWS-TO4-GS17: The Contractor(s) shall be compliant with IT security requirements and follow 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-TO4-GS18: The Contractor(s) shall obtain approval from the PI, for changes and implementation through an approved NESDIS CM process. NAaaS antenna ground systems that have been changed shall be scanned for vulnerabilities and corrected prior to connecting back into an operational network. Input to required IT security documentation, such as changes to any security documentation, shall be provided by the Contractor(s). If the change results in a recertification of the system, then the Contractor(s) shall provide supporting documentation.

PWS-TO4-GS19: The Contractor(s) shall provide a weekly and monthly sustainment status report and include the following for sustainment related activities:

a. Sustainment Weekly Status Report [D-TO4-034] describes activities and accomplishments, planned activities, technical issues, risk register, sustainment integrated schedule, resource planning and action items.

b. Sustainment Monthly Status Report [D-TO4-038] shall provide one report per month that is an aggregate of the weekly reports to provide management level security review of status and trending of near-term activities, issues, and risks. The monthly report shall also contain project plan schedule, work performed, status of schedule (indicating completion percentage for each item), sustainment activities status (estimates, percent complete broken out by function level modules/components), detailed financial data, 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. All milestone dates should reflect deliverables and key decision points.

c. The Contractor(s) shall conduct monthly and weekly sustainment status report meetings. The Contractor(s) shall also provide meeting support to include meeting minutes and agendas [D-TO4-039].

PWS-TO4-GS20: The Contractor(s) shall conduct a Technology Refresh Analysis [D-TO4-007] as needed, to include an analysis of commercial services options, technology evaluation, cost benefit assessment and a risk assessment.

PWS-TO4-GS21: The Contractor(s) shall provide a Transition to Operations package to the Government and PI when a sustainment development activity is complete. The package shall include:

a. As Built vendor information

b. Recommended maintenance procedures

c. Operations manual

d. Training documentation

e. Part inventory

f. Preventative Maintenance Instructions

g. Recommended Maintenance Procedures

PWS-TO4-GS22: Appendix C contains three sample sustainment use cases representing an antenna upgrade, build out, and decommission; transitioning to a service based Software Defined Radio (SDR), and assessing the feasibility of exploring phased array antenna technology. For all use cases, the Contractor(s) shall provide, with the proposal submission, a fully burdened cost estimate [D-TO4-043] for all labor, material, and other direct costs. Please list all assumptions in these efforts.

PWS-TO4-GS23: The Contractor shall recommend or use a Government defined requirements management system to define, implement and maintain NAaaS requirements with PI and Government coordination.

PWS-TO4-GS24: The Contractor shall ensure User and Design manuals are kept up to date.

3.3.2 Antenna and Radio Frequency (RF) Equipment

The general Sustainment Plan shall include engineering sustainment processes specific to antennas and radio frequency equipment for ground stations and sites.

3.3.2.1 Antenna Equipment

PWS-TO4-AN01: The Contractor(s) shall conduct all sustainment activities necessary for antennas identified in this TO Appendix A.

PWS-TO4-AN02: The Contractor(s) shall execute the construction of any new antenna assets and related RF ground system support equipment as required by the Government and tied to the general Sustainment Plan.

PWS-TO4-AN03: The Contractor(s) shall provide sustainment support of obsolete antenna systems, or subsystems and/or components by reverse engineering, or other engineering methods. Equivalent Commercial Off-the-Shelf (COTS) products or prototyping the latest technology for replacement shall be specified. This task includes development or procurement of prototype units, testing and integration.

PWS-TO4-AN03: The Contractor(s) shall conduct removal and safe disposal of identified antenna assets in compliance with all pertinent Government regulations, guidelines and safety standards.

PWS-TO4-AN04: The Contractor(s) shall conduct regular antenna calibration intervals verifying an antenna's performance and accurately measuring its signal characteristics. The calibration intervals shall occur at a minimum every [12 or 18] months.

3.3.2.2 RF Equipment

PWS-T04-RF01: The Contractor(s) shall provide all system engineering and technical support to sustainment activities for RF equipment. This includes integration and upgrade of High-Power Amplifiers (HPAs), Low Noise Amplifiers (LNAs), Low Noise Block Down Convertors (LNBs), Antenna Control Systems (ACS), RF fiber optic transceivers, RF components, receivers, command modulators, antenna-tracking receivers, antenna mechanical and drive components and any other associated antenna equipment as directed by the Government.

PWS-TO4-RF02: The Contractor(s) shall provide support to test and calibrate all intended RF equipment for sustainment prior to being integrated into the operational system. The Contractor(s) shall make the types of measurements and calibrations pertinent to the equipment installed. Typical measurements and calibration include, but are not limited to frequency, attenuation, gain, bandwidth, noise figure, and antenna noise temperature. Test and Calibration Reports [D-TO4-040] of all testing and calibration conducted shall be delivered to the Government no more than two weeks after acceptance by the Government.

PWS-T03-RF03: The Contractor(s) shall verify that electromagnetic emissions from any newly installed RF equipment for the purposes of sustainment conform to all applicable National Telecommunication and Information Administration (NTIA)/ Federal Communication Commission (FCC) and the International Telecommunication Union (ITU) regulations.

3.3.2.3 Antenna and RF Equipment Systems Engineering

PWS-TO4-SER01: The Contractor(s) shall detail in the general Sustainment Plan all prioritized support for engineering expertise, labor, materials, documentation services, and calibration required for the installation, test, and checkout (ITCO) in accordance with the OSPO CM Plan 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. The Contractor(s) shall deliver to the Government test deliverables 30 days before the tests.

PWS-TO4-SER02: The Contractor(s) shall work with the Government and PI to manage, monitor and forecast hardware and software obsolescence and document the approach in an Obsolescence Management Plan [D-TO4-023]. The Contractor(s) shall:

a. Develop a Computerized Maintenance Management System (CMMS) or similar tool, approved by the Government, to manage obsolescence software or to manage End-of-Life cycles of other physical assets.

b. Maintain an active list of the hardware and software deployed in the NAaaS program with associated end-of-support (EOS) and end-of-life (EOL) dates.

c. Notify the Government when vendors provide notification of changes in EOS and EOL dates.

d. Present to the Government and PI a quarterly summary of the NAaaS assets obsolescence, including the status of upcoming EOS and EOL dates, and recommendations for a path forward on each item with an EOS date within the next three (3) years. Recommended options should include acceptance with risk mitigation, replacement, or retirement.

e. Review obsolescence items by priority with the Government and develop and deploy replacement components, as directed by the Government.

f. In coordination with the Government, identify obsolescence and technology refresh trades as a part of the Common Ground System (CGS) system recapitalization and refresh.

g. Assess each system component for technology refresh necessity on a case-by-case basis.

h. The general Sustainment Plans will be incorporated into the TO1, PI Integrated Sustainment Plan.

PWS-TO4-SER03: The Contractor(s) 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-TO4-SER04: The Contractor(s) 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-TO4-SER05: The Contractor(s) 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-TO4-SER06: The Contractor(s) shall perform RF analysis and feasibility studies as required by the Government necessary to define upgrade requirements for antennas supporting future missions and new capabilities such as phased arrays and optical link technologies.

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

PWS-TO4-SER08: The Contractor(s) shall perform risk analysis and mitigation planning on antenna subsystems.

PWS-TO4-SER09: The Contractor(s) shall obtain all approvals in accordance with local, state, federal, international laws and regulations, including those affecting local labor mandates, any tariffs imposed on materials and labor. The Contractor(s) shall deliver regulatory reports to include references, regulations, and approval.

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

PWS-TO4-SER11: All RF sustainment equipment installations must comply with applicable international, national, state, and local codes and ordinances. The Contractor(s) 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 approval from responsible Government organizations. The Contractor(s) shall take all necessary actions to ensure compliance and approval. This includes obtaining and maintaining any NTIA, FCC, or other governmental, or international authorizations for the operation of any communications network installed to support a sustainment solution.

3.3.3 Technology Sustainment

Sustainment activities include the modernization (or refreshing) of existing hardware and software and adding new capabilities to meet Government requirements. Activities include support for software and hardware sustainment solutions depending on the scope and magnitude of the need. Sustainment activities may also encompass agile development of cloud-based software.

3.3.3.1 Software Sustainment

PWS-TO4-SS01: The Contractor(s) shall deliver a Software Sustainment Plan [D-TO4-009] where the initial draft is submitted with the proposal response in the general Sustainment Plan, and a final delivered after contract award. The Software Sustainment plan shall detail software support of the following including existing source code modifications. The Contractor(s) 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 the OCS Change and Configuration Management Process and OCS Systems Engineering Process Document, OCS 5820.01A October 3, 2016, Version 0.5.

Test and baseline of all changes shall be in accordance with a Government approved source code control sustainment standard operating procedure and approved by the PI. Sustainment test plans and modified source code [D-TO4-013] shall be delivered as required 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(s) is allowed to implement any modified code in the operations environment. The Contractor(s) shall submit Configuration Change Requests (CCRs) [D-TO4-014] with all required documentation for all changes made during sustainment of any software and coordinate with the PI. The Contractor(s) shall document operational impacts for any CCR that affects operations and immediately report these impacts to the Project Manager and COR.

PWS-TO4-SS02: The Contractor(s) shall provide weekly updates for open CCRs and report progress of CCR closure in the Configuration Change Requests Report under [D-TO4-015). The Contractor(s) shall perform all required activities to close CCRs per the agreed schedule and elevate or expedite any activities required to maintain the CCR closure schedule. Ninety percent (90%) of CCRs shall have no open problem reports (PRs) at an ORR; any open PRs shall have an approved resolution plan.

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

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

PWS-TO4-SS05: The Contractor(s) shall follow a documented development process for approved software changes that:

a. Explicitly addresses security requirements.

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

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

d. 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.

e. Supply chain risk assessments and mitigations need to be coordinated with the Government and PI.

PWS-TO4-SS06: Software development and test for NAaaS antenna systems sustainment shall be in accordance with a Contractor(s) general Sustainment Plan as defined in PWS-TO4-GS01.

PWS-TO4-SS07: The Contractor(s) 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(s) shall give an overview of how builds will be distributed and patches applied.

PWS-TO4-SS08: The Contractor(s) 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-TO4-SS9: The Contractor(s) shall request permission from the Government prior to using open source, shareware or freeware software in any product or system delivered under this contract. The Contractor(s) 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-TO4-SS10: The Contractor(s) shall ensure that all provided or developed source code undergoes static or dynamic code scanning for security vulnerabilities as part of Security Test and Evaluation (ST&E) testing. Identified vulnerabilities shall be remediated, and the final scan results shall be submitted to the Information System Security Officer (ISSO) for approval prior to the code's operational deployment.

PWS-TO4-SS11: The Contractor(s) shall plan for and sustain software licenses in coordination with the PI, supporting NAaaS ground systems as well as at locations and backup sites. For new antennas, software licenses information shall be coordinated with the PI and Maintenance Contractor’s (TO3) Software and Hardware License Status reporting.

PWS-TO4-SS13: The Contractor(s) shall support new software sustainment code reviews and testing for scheduled sustainment related software releases, and any fixes to ensure they function as intended PWS-TO4-SS14: The Contractor(s) shall support deployment and checkout operations, beginning with deployment to the on-site I&T environment and provide software releases and patches as a Software Delivery Package [D-TO4-049] and coordinated with the PI.

3.3.3.2 System Integration, Installation, and Test

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

a. Targeted ST&E at the Contractor(s) site, prior to the Pre-shipment Test (PST)

b. PST at the Contractor(s) site

c. Integration Level Test (ILT) at the NOAA site

d. Parallel Operations Testing (POT) at the NOAA Site

e. Final Acceptance Test (FAT) The Government may determine that its best interests are served by having the Contractor(s) perform some or all this work remotely when appropriate. On a case-by-case basis, the Contractor(s) shall provide justification and shall obtain written Government approval prior to conducting any/all remote testing.

PWS-TO4-SI02: The Contractor(s) shall submit sustainment Integration and Test (I&T) Plans [D-TO4-017] to manage and execute system level requirements driven I&T tasks as applicable. The Contractor(s) shall deliver the I&T plan for Government review and approval. Initial drafts shall be submitted two weeks prior to the sustainment solution technical review meeting (e.g. CDR). Any Government comments shall be submitted to the government 30 days prior to the test and Government comments shall be incorporated into the final test two weeks prior to test. Each test plan shall comply with the following:

a. All requirements being tested have clearly identified success criteria.

b. All requirements have an associated verification method.

c. 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.

d. Input data shall…