Attachment 6 - Program Integration - Comprehensive Day 1 Task Order.docx

Attachment J-6 Program Integration Functional Area - Comprehensive Day-1/Sample Task Order

Attachment J-6 Program Integration Functional Area - Comprehensive Day-1/Sample Task Order

National Environmental Satellite, Data, and Information Service (NESDIS) Office of Satellite and Product Operations (OSPO) and Office of Common Services (OCS)

NOAA Consolidated Antenna & Ground Systems Contract (NCAGSS)

Program Integration Task Order 1 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 IDIQ is to describe the services the Contractor shall provide to support the National Environmental Satellite, Data, and Information Service (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. The 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 SOW contract over the period of performance. The PI will ensure integration across all task orders supporting the NAaaS program.

The Office of Satellite and Product Operations (OSPO) and the Office of Common Services (OCS) have shared responsibilities in managing satellite antenna ground systems under the NAaaS program. This PI TO details NAaaS PI contractor performance work statement (PWS) requirements related to managing and integrating multiple NAaaS operations, maintenance and sustainment task order activities. The Government's intent is for the NAaaS PI contractor to deliver NAaaS integrated products, analysis and recommendations to the Government supporting the NAaaS program. The PI serves as a central communication hub, facilitating collaboration, while also identifying and mitigating risks related to cost, schedule and performance to achieve NAaaS program objectives.

2.0 Scope

A single NAaaS TO will be issued for the PI, and multiple operations, maintenance, and sustainment TOs within the scope of the base IDIQ SOW contract over the period of performance. All TO activities include project management, system engineering and system integration efforts coordinated with the NAaaS PI. Figure 2.0-1 depicts the NAaaS TO1 integration functions of the NAaaS PI.

Figure 2.0-1 Phase 2 NAaaS PI Task Order Integration Functions

The NAaaS PI ensures smooth execution alignment of overall NAaaS program goals and is the central point of contact bringing communication and collaboration between the TO contractors and government. This includes support for the following, but is not limited to:

a. NAaaS program execution

b. Stakeholder communication

c. Documentation and reporting

d. Risk Management

e. Performance monitoring

f. Conflict resolution

g. TO integration when activities impact more than one TO

h. Financial management The antenna ground system supports spacecraft in various orbital regimes including Geostationary Earth Orbit (GEO), Low Earth Orbit (LEO), and Space Weather Operations (SWO) Lagrange Point Orbits used by both NOAA and its partners. Appendix A in the IDIQ SOW 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.

The term NAaaS antenna portfolio includes but is not limited to the items in Appendix A, Antenna Ground Systems in the IDIQ. Examples of the NAaaS antenna portfolio contents include the frequency bands, Interface infrastructure, Low Noise Amplifiers (LNAs), High Power Amplifiers (HPAs), Front End Processors (FEPs)/radios, and matrix switches. The NCAGSS Acquisition Document Library will provide additional details.

NOAA currently has partnership agreements with National Aeronautics and Space Agency (NASA), U.S. Space Force, Kongsberg Satellite Systems (KSAT) and Norway to provide antenna services that currently fall outside of the NAaaS portfolio of antennas and outside of the IDIQ SOW. While all antennas ground systems listed in Appendix A in the IDIQ shall be operated and maintained, there are a subset of antennas and systems that will be initially sustained and are defined in Sustainment (TO4). In addition, Operations (TO2) and Maintenance (TO3) antennas and ground system interfaces are applicable to NSOF, CBU and McMurdo Station. Partnership agreements, individual system inventories, drawings, descriptions and interfaces are available in the NCAGSS Acquisition Document Library. Appendix A contains the PI TO1 deliverables and Appendix B contains acronyms and meanings.

2.1 Place of Performance

The primary work locations for this TO are:

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

· Contractor facilities

The Contractor may need to conduct authorized site visits during project integration activities.

2.2 References

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

a. OSPO System Descriptions

b. OSPO System Inventories

c. OSPO Incident Reporting Policy

d. NESDIS Incident Response Plan

e. OCS Change and Configuration Management Process

f. OSPO Configuration Management Process

g. OSPO Configuration Control Board Charters

h. OSPO System Inventories

i. NESDIS IT System Component Inventory Management Policy and Procedures

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

k. Satellite Products and Services Review Board Process

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

m. NESDIS Antenna RF Handbook (Redacted)

n. NASA Systems Engineering Processes and Requirements (NPR 7123.1D) NESDIS Antenna-as-a-Service (NAaaS) Requirements Document (OSPO-REQ-55XX.1)

3.0 Requirements

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

3.1 Program Management

The PI TO will be awarded to one vendor and multiple TOs with specific service requirements (i.e., operations, maintenance, and sustainment) awarded within the scope of the IDIQ SOW contract over the period of performance. While all TOs have program management (PM) performance work statements (PWS), the PI has the additional responsibility of overseeing other TO PM activities, compiling, and reporting to the Government to ensure integration across all TOs supporting the NAaaS program. The PI shall ensure all technical and functional aspects of the NAaaS program work together, overseeing costs, schedule and performance baselines, and acting as a liaison between the various operations, maintenance and sustainment TO stakeholders to deliver on NAaaS program commitments. In addition to the IDIQ SOW PM requirements, the following support PM requirements apply to the PI role.

PWS-TO1-PM01: The Contractor shall follow their Quality Assurance Plan and Quality Assurance Standard Operating Procedure (SOP) when performing activities detailed in this TO.

PWS-TO1-PM02: The PI shall compile Contractor Metric Performance Reports [D-TO1-027] from operations, management and sustainment contractors on items in Section 4, Performance Requirements Summary (PRS) table of the operations, maintenance and sustainment TOs. The Contractor Metric Performance Reports shall be delivered to the Government and PI as part of the weekly status report and aggregated in a monthly report. The report shall include:

a. Hardware and software operations, maintenance and sustainment

b. Documentation

c. Performance

d. Product or service evaluations

e. Verification and validation results

f. Incidents and problems from CCR administration

PWS-TO1-PM03: The Contractor shall provide a written Weekly Status Report (work status and plan) covering Monday through Sunday no later than the close of business (COB) the second business day of the week [D-TO1-010] and shall provide meeting support to include meeting minutes, agendas, action items, lessons learned, etc. [D-TO1-013].

PWS-TO1-PM04: The OSPO Configuration Management Process consists of a Configuration Management (CM) Plan, Procedures, and Configuration Control Board (CCB) Charters that will be provided in the NCAGSS Acquisition Document Library. The Contractor shall provide weekly updates for all open Configuration Change Requests (CCRs) [D-TO1-014] and report progress of CCR closure in the Configuration Change Requests Report [D-TO1-015]. The Contractor 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.

PWS-TO1-PM05: The Contractor shall provide weekly updates to the System Maintenance Schedules [D-TO1-026] to include major hardware or software implementations, scheduled activities such as vulnerability scans and security patching, and planned system outages.

PWS-TO1-PM06: The Contractor shall conduct monthly NAaaS Program Management Review (PMR) meetings with the Government and Operations, Management and Sustainment TOs leadership to report all pertinent activities. PMR information shall be provided to the Government 10 days prior to the meeting.

PWS-TO1-PM07: The Contractor shall provide an Associate Contractor Agreement (ACA) [D-TO1-035] for any portion of the NCAGSS contract requiring joint participation with the Government. The agreements should include the basis for sharing information, data, technical knowledge, expertise, schedules and risks in accordance with IDIQ SOW Section 3.1 (General Requirements).

PWS-TO1-PM08: The Contractor shall work with the Government to define, document, and create a dashboard for tracking NAaaS Key Performance Indicators (KPIs), metrics, status and performance for all TOs.

PWS-TO1-PM09: The Contractor shall maintain the NAaaS antenna portfolio for compliance with technical, functional, performance, availability, reliability, and security requirements and specifications.

PWS-TO1-PM10: The Contractor shall conduct a Program Integration Kickoff meeting [D-TO1-040] 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-TO1-PM11: The Contractor shall coordinate with the Government meetings with working groups, product teams, and vendor partners.

PWS-TO1-PM12: The Contractor shall participate in Government required meetings or working groups as directed by the Government.

3.2 Program Management and Integration

3.2.1 Management Plans and Integration

PWS-TO1-PI01: The Contractor shall develop and deliver a NAaaS Program Management Plan (PMP) [(D-TO1-001]) covering the NCAGSS SOW IDIQ contract and all maintenance, operations and sustainment TOs project plans.

PWS-TO1-PI02: The Contractor shall plan, coordinate with the Government, and execute Program Management in accordance with the Contractor’s NAaaS PMP.

PWS-TO1-PI03: The Contractor shall integrate and execute NAaaS Program Management and Integration activities for all maintenance, operations and sustainment TOs.

PWS-TO1-PI04: The Contractor shall develop, coordinate with the Government, deliver, and maintain NAaaS program management products on designated Government information systems.

PWS-TO1-PI05: The Contractor shall develop and maintain a contract Phase-In Transition Plan [D-TO1-033] and contract Phase-Out Transition Plan [D-TO1-034]. Transition plans shall include:

a. Proposed Contractor Staffing and Government support staffing levels.

b. Proposed Contractor Staffing and Government support staffing levels.

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

d. Training and general knowledge transfer.

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

f. Transfer of operations, inventory, and assets.

g. Transfer of accounts, passwords, and permissions.

h. Access to Government Configuration Management systems.

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

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

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

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

m. Confirmation of the ability of the FDE and FTE to test new or modified software.

n. Management of hardware and software licenses and warranty activity for Contractor managed property.

o. Ensure Lessons Learned have been documented.

PWS-TO1-PI06: The Contractor shall be responsible for consolidating and reporting all operations, maintenance and sustainment TOs’ Contract Phase-In Transition and Contract Phase-Out Transition plans as detailed in the IDIQ SOW Section 3.1.2 (Incoming and Outgoing Transitions). As part of the Contract Phase-Out Transition plans, incumbent operations, maintenance and sustainment TOs shall provide a checklist to the PI for V&V.

PWS-TO1-PI07: The Contractor shall be responsible for development and update to an Integrated Sustainment Plan [D-TO1-030] that addresses the Sustainment TOs issued under the NCAGSS contract. The PI Integrated Sustainment Plan shall include, but not limited to:

a. Sustainment Stakeholder Contact List

b. Integrated Sustainment Schedule

c. Sustainment Inventory Baseline

d. Sustainment Requirement Baseline

e. Inventory from the Sustainment TOs containing details of specific antenna ground system assets to be refreshed, and system hardware and software components within one (1) year of obsolescence.

PWS-TO1-PI08: The Contractor shall be responsible for development and update to an Integrated Obsolescence Plan [D-TO1-031] that addresses the obsolescence plans in the Sustainment TOs issued under this contract.

PWS-TO1-PI09: The Contractor shall deliver a Consolidated Monthly Progress Report [D-TO1-032] from program integration, and all operations, maintenance and sustainment task orders. The report shall include: to include issue resolution and root cause determination

a. Executive summary

b. Project details

c. Project scope and adjustments

d. Project work breakdown structures

e. Progress updates and milestones

f. Review of key performance indicators

g. Risk and opportunity management

h. Budget and financial performance

i. Stakeholder communications

j. Issue resolution and root cause determination

k. Next steps and action items

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

PWS-TO1-PI10: The Contractor shall coordinate with the Sustainment teams to develop a Release Backlog [D-TO1-008]. The Government will provide a set of sustainment priorities, as part of the NCAGSS transition. The Release Backlog shall detail future modifications, enhancements, and features and shall be reviewed monthly with the Sustainment teams. 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 OCS Change and Configuration Management Process and OCS Systems Engineering Process Document, OCS 5820.01A October 3, 2016, Version 0.5.

All planned implementation of priorities from the Release Backlog shall be reflected in the IMS and the status of sustainment implementations shall be reported monthly and reviewed with the Sustainment teams monthly. 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. A Release Backlog Report [D-TO1-009] shall be submitted weekly.

PWS-TO1-PI11: The Contractor shall coordinate with the Maintenance TO contractor the creation and management a list of preventative maintenance activities (i.e. job plans) using the Government provided enterprise asset management system, Maximo, or other Government tool, used to manage physical assets and maintenance operations.

PWS-TO1-PI12: The Contractor shall coordinate with operations, maintenance and sustainment TO contractors a NAaaS Asset Inventory Report [D-TO1-037] detailing NAaaS program assets. The report shall include asset inventories from Enterprise Configuration Management System (ECMT), Sunflower, or designated Government asset management application to include:

a. Accountable property inventories

1. Operations TOs: Government equipment spares inventory

2. Maintenance TOs: IT Asset Management HW/SW inventory reports

b. Capital property inventories – maintained in Sunflower

1. Sustainment TOs: Inventory baseline, identified in the Sustainment Plan and additional inventory of specific antenna ground systems assets to be refreshed to include HW/SW components within (3) year of obsolescence.

2. Maintenance TOs: IT Asset Management HW/SW inventory items deemed as capital property

PWS-TO1-PI13: The Contractor shall work with the Government to ensure the TOs decommission, excess, and dispose of NAaaS ground system accountable hardware in coordination with the NOAA Property Manager.

PWS-TO1-PI14: The Contractor shall 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-TO1-PI15: The Contractor shall establish and conduct a system safety program that encompasses all activities related to NAaaS, and describe those tasks and activities in a NAaaS Safety Plan [D-TO1-040]. The safety program shall be in compliance 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-TO1-PM16: The Contractor shall ensure task order vendors are complying with each site's environmental and hazardous materials requirements identified in the NAaaS Technical Document Library.

PWS-TO1-PM17: The Contractor shall oversee any necessary transition support agreements established by NESDIS offices.

PWS-TO1-PM18: The Contractor shall establish and maintain support agreements with vendors and subcontractors to ensure provisions are in place to ensure maintenance, operations, and sustainment support across the NAaaS ground systems.

PWS-TO1-PM19: The Contractor shall identify the technical requirements, timing, and required durations of hardware and software support agreements required to support the sustainment of the NAaaS ground systems.

PWS-TO1-PM20: The Contractor shall monitor compliance with the technical requirements of the support agreements and licenses.

PWS-TO1-PM21: The Contractor shall coordinate license management with the TOs and provide access to an online inventory of the system licenses, including:

a. Identification of all licenses required including source (e.g., company, vendor, provider); contract number; license or agreement number; and expiration date, of all software licenses, and software support contracts throughout the period of performance of the contract.

b. Documented plan for license acquisition and renewal.

c. Consolidated schedule of the expiration of software licenses, software support contracts, hardware warranties, and service agreements.

PWS-TO1-PM22: The Contractor shall coordinate with the Sustainment contractor the review of software delivery packages delivered for software releases and patches.

3.2.2 Financial Management

PWS-TO1-FM01 The Contractor shall establish, implement, and maintain a comprehensive cost management system for planning, authorizing, and controlling the total expenditures for each task and for providing visibility into cost performance.

PWS-TO1-FM02 The Contractor shall provide Contract Funds Status Report (NASA 533) [D-TO1-007] financial cost reporting documentation.

PWS-TO1-FM03: The Contractor shall report financial and cost data as a part of each Program Management Review (PMR).

PWS-TO1-FM04: The Contractor shall provide a Consolidated Contract Financial Report [D-TO1-004] from operations, maintenance and sustainment task orders to include spend plans, invoicing, fund status, engineering assessments (EAs) and travel management.

PWS-TO1-FM05: The Contractor shall develop and maintain monthly a Staffing Plan [D-TO1-011] to include a Staff List, as part of the PMR Package and brief as appropriate at a suitable forum.

PWS-TO1-FM06: The Contractor shall provide a Consolidated Contractor Spend Plan [D-TO1-036] from Program Integration, Operations, Management and Sustainment task orders as detailed in the IDIQ SOW contract Section 3.1k (General Requirements). The Operations, Maintenance, and Sustainment contractor 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.

3.2.3 Property Management

PWS-TO1-PMG01: The Contractor shall provide a monthly Property Audit Report [D-TO1-020]

PWS-TO1-PMG02: The Contractor shall provide a Discrepancy Property Audit Report [D-TO1-021]

3.2.4 Earned Value Management (EVM)

PWS-TO1-EV01: The Contractor shall use an Earned Value Management System (EVMS) which has been determined by the Cognizant Federal Agency (CFA) to be compliant with the guidelines contained in Electronic Industries Alliance (EIA)-748-D and FAR 52.234-4.

PWS-TO1-EV02: The Contractor shall identify for government direction, EVM requirements applicable to subcontractor/suppliers from all operations, maintenance and sustainment TOs that meet the application thresholds.

PWS-TO1-EV03: The Contractor shall submit a monthly Earned Value Management (EVM) report [D-TO1-005].

PWS-TO1-EV04: The Contractor Project Manager shall complete an EVMS course per Code of Federal Regulations (CRF) Part 1334.

3.2.5 Integrated Baseline Review (IBR)

PWS-TO1-IB01: The Contractor shall conduct an IBR [D-TO1-006] with active Government participation after contract award for TOs that meet or exceed the EVM application thresholds.

PWS-TO1-IB02: The Contractor shall collaborate with all operations, maintenance and sustainment TOs for the IBR.

PWS-TO1-IB03: The Contractor shall conduct IBRs, annually, and following major changes to the baseline, such as significant contract option issuance or other major contract modifications.

PWS-TO1-IB04: The Contractor shall report risks and opportunities associated with the Performance Measurement Baseline (PMB) at IBRs and to the Government NAaaS Risk Management Lead.

3.2.6 Schedule

PWS-TO1-SC01: The Contractor shall update, manage and deliver the NAaaS Integrated Master Schedule (IMS) [D-TO1-003] that includes all TOs. The IMS shall include operations, maintenance and sustainment TO interdependencies, TO execution status, and sustainment Release Backlog activities. The Contractor shall obtain approval from the Government prior to making changes which affect scheduled deliverables, integration/test activities, or key milestones. The initial NAaaS IMS is in the NCAGSS Acquisition Document Library.

3.2.7 Metrics

PWS-TO1-ME01: The Contractor shall support development, maintenance, and usage of metrics and tools for monitoring and reporting all TO metrics.

3.2.8 NAaaS Program Management Reviews and Other Reviews

PWS-TO1-PR01: The Contractor shall deliver a NAaaS Program Management Review package [D-TO1-002] and support executive level quarterly Program Management Reviews (PMRs). This review will provide status, schedule, visibility, and insight into program finance, schedule, estimates at completion (EAC), performance, earned value, manpower, security status, quality assurance, risk review, action items reviews and additional topics as designated by the Government across all operations, maintenance, and sustainment TOs.

PWS-TO1-PR02: The Contractor shall conduct a monthly NAaaS Contract Review [D-TO1-028] to review all operations, maintenance, and sustainment TO contracts planned or in work. The NAaaS Contract Review involves analyzing the contract's language, assessing its enforceability, and confirming that it aligns with NAaaS program objectives.

3.2.9 Document Management

PWS-TO1-DM01: The Contractor shall ensure that all approved and current program documentation is available to TO contractors, government employees and mission partners as appropriate. The Contractor shall create and maintain a comprehensive file management structure for documents it delivers to the Geostationary Ground System Sustainment (GGSS) Government-managed document portal by TO within one (1) month after contract award. The Contractor shall place on the Government-managed document portal, the latest version of all technical and programmatic documentation as generated or changed within the project. Program documentation includes but is not limited to:

a. Integrated Master Schedules

b. Processes/Work Instructions

c. User Manuals

d. Standard Operating Procedures

e. Plans

f. Technical Baseline

g. Risks

h. Studies

i. Technical Papers

PWS-TO1-DM02: The Contractor shall generate a Document Tree [D-TO1-038] that shows the NAaaS documentation and requirements hierarchy.

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

3.2.10 Quality Assurance

PWS-TO1-QA01: The Contractor shall plan and implement an organized technical quality assurance program in a Quality Assurance Plan (QAP) [D-TO1-024] that encompasses hardware, software, and processes from project initiation through deployment and operations to assure the integrity and safety of items critical for mission success.

PWS-TO1-QA02: The Contractor shall be responsible that enterprise quality assurance is consistent among the TOs QAPs and Quality Assurance Surveillance Plans (QASP). The QASP explicitly describes Contractor processes and measures for subcontractor/ vendor performance and deliverables.

PWS-TO1-QA03: The Contractor shall provide Quality Assurance Standard Operating Procedures [D-TO1-018] and update it annually or as requested by the CO.

PWS-TO1-QA04: The Contractor shall provide, report, and track contract performance metrics as part of the monthly program management review. Metrics shall cover all TOs. 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-TO1-QA05: The Contractor shall participate in the Government’s process improvement activities. The Government will provide a government tool, Action Information Management System (AIMS) for organizing data calls.

PWS-TO1-QA06: The Contractor shall support organizational data call requests.

PWS-TO1-QA07: The Contractor shall prepare, document and implement a Reliability, Maintainability, and Availability (RMA) program for all TOs under the PI purview, and describe its plan and processes in a Mission Quality Assurance Implementation Plan (MAIP) [D-TO1-041].

PWS-TO1-QA08: The Contractor shall continue RMA activities throughout the period of performance in accordance with the MAIP, replacing or comparing predictions with analysis of the actual statistics, as well as updating analyses to cover any changes in configuration, hardware, or software as a part of the RMA Report [D-TO1-042).

3.2.11 Training

PWS-TO1-TR01: The Contractor shall provide qualified personnel with professional and technical expertise commensurate with their responsibilities, and any certifications in accordance with NCAGSS IDIQ Attachment J-2 Labor Categories Descriptions.

PWS-TO1-TR02: The Contractor shall assist the Government in identifying training for Government and Contractor personnel that will improve operations, maintenance and sustainment of antenna systems.

PWS-TO1-TR03: The Contractor shall coordinate training with the TO awardees and the government on substantive changes made to antenna systems during the contract.

PWS-TO1-TR04: The Contractor shall maintain a repository of training materials from other NAaaS TO training, to include updates to existing training materials.

3.2.12 Cybersecurity

Cybersecurity related requirements for TO 1 activity are specified and are to be managed by the Contractor under the IDIQ SOW Section 3.1.4 (Cybersecurity).

PWS-T01-CS01: Contractor shall support annual IT security audits and collect, manage and integrate, all requested Security Control Assessment (SCA) artifacts [D-TO1-022] requested by the audit team across all operations, maintenance, and sustainment TOs.

PWS-T01-CS02: Contractor shall provide a monthly Plans of Action and Milestones (POA&M) Milestone Status Report [D-TO1-023] outline all corrective actions, development and deployment efforts across all operations, maintenance and sustainment TOs resulting from annual IT security audits.

PWS-TO1-CS03: Contractor shall provide the Government all passwords associated with firmware and software that is non-proprietary.

PWS-TO1-CS04: The Contractor shall ensure that the appropriate security posture is maintained for each system/subsystem. The Contractor shall therefore ensure system owners implement, sustain, and provide continuous monitoring on IT Security, via Continuous Monitoring Reports, in accordance with NOAA/NESDIS policy.

3.3 System Engineering (SE)

3.3.1 General

PWS-TO1-SE01: The Contractor shall support NAaaS approach to SE and SE Management in accordance with the OCS Systems Engineering Process Document, OCS 5820.01A October 3, 2016, Version 0.5.

PWS-TO1-SE02: The Contractor shall support Design Modification Reviews (DMR) with the Government to present significant changes to the design baseline. The DMR shall include details on architectural impacts, security impacts, software/hardware impacts, deployment plans and operational impacts from the change under review in accordance with the OCS Systems Engineering Process Document, OCS 5820.01A October 3, 2016, Version 0.5.

3.3.2 SE Management Planning

PWS-TO1-SM01: The Contractor shall document a NAaaS enterprise System Engineering Management Plan (SEMP) [D-TO1-017].

PWS-TO1-SM02: The Contractor shall organize and conduct NAaaS enterprise management and engineering peer reviews (EPR) on technical topics with participation from the Government and applicable TOs.

3.3.3 Requirements Management

PWS-TO1-RQ01: The Contractor shall support NOAA Administrative Orders (NAO) 216-108 Requirements Management Process which specifically enables the Government to gather, analyze, allocate, decompose, and validate requirements.

PWS-TO1-RQ02: The Contractor shall update and manage the baselined NAaaS Requirements Document, to include requirements impacted by other NAaaS task orders.

PWS-TO1-RQ03: The Contractor shall perform system analysis and systems engineering to derive lower-level requirements specifications, interface requirements, and design specifications in response to new or changing mission requirements.

PWS-TO1-RQ04: The Contractor shall recommend or use a Government defined requirements management system to define, implement, and maintain NAaaS requirements.

3.3.4 Architecture

PWS-TO1-AR01: The Contractor shall update and manage the NAaaS CONOPS technical baseline provided in the NAaaS Acquisition Document Library. The CONOPS serves as a top-level view of the proposed NAaaS architecture, describing how the architecture will be used. It serves as a bridge between the statement of need and the technical requirements needed to develop the architecture.

PWS-TO1-AR02: The Contractor shall update and manage the NAaaS system architecture technical baseline provided in the NAaaS Acquisition Document Library. The system architecture design defines system behavior and structure characteristics in accordance with derived requirements.

3.3.5 Strategic Planning and Roadmap

PWS-TO1-SP01: The Contractor shall provide approaches to understand future technology capabilities, evaluate the applicability to NAaaS needs, and integrate technology maturation into a NAaaS technology roadmap.

3.3.6 Trade Studies

PWS-TO1-TS01: The Contractor shall perform NAaaS enterprise engineering analyses, assessments, trade analysis and studies, evaluations, and gap analysis of deficiencies as directed by the Government.

3.3.7 Configuration Management

PWS-TO1-CM01: The Contractor shall plan and execute NAaaS enterprise configuration management supporting NAaaS antenna operations, maintenance, sustainment, site support, and integrated product support in accordance with the Contractor’s NAaaS Configuration Management Plan [D-TO1-029] and OSPO Configuration Management Process.

PWS-TO1-CM02: The Contractor shall coordinate with the Government updates to the NCAGSS Acquisition Document Library.

3.3.8 Integration Testing

PWS-TO1-IT01: The Contractor shall provide coordination and support of integration testing allocated with all TOs.

3.3.9 Risk Management

PWS-TO1-RM01: The Contractor shall comply with the OSPO Risk Management Plan.

PWS-TO1-RM02: The Contractor shall prepare a Consolidated Risk Management Report [D-TO1-019] listing the Contractor’s view of initial operations, maintenance and sustainment risks for review and consideration by the Government with recommended mitigations as part of its proposal submission. Subsequent updates to be coordinated with the Government monthly.

PWS-TO1-RM03: The Contractor shall support the Government in the risk management activities and maintaining risk related data in the Government-provided risk management tool.

PWS-TO1-RM04: The Contractor shall collaborate with the Government on risk management activities and report risk status at the monthly NAaaS Contract Review and Program Management Review.

PWS-TO1-RM05: The Contractor shall coordinate with the Sustainment Contractor to develop a Supply Chain Risk Assessment Plan [D-TO1-039] to ensure the integrity of changes to the process and/or tools used in development to enable accurate assessments and mitigations to track authorized changes and prevent unauthorized changes.

4.0 Contract Line Item Number (CLIN) 0001 - Study Tasks

PWS-TO1-CL01: The Contractor shall conduct studies and analysis on topics identified by the Government throughout the period of performance.

5.0 Performance Requirements Summary

PWS Section

Performance Objectives

Minimum Acceptable Quality Level (AQL)

Monitoring Method

98% submitted on time per invoice period

Inspection/review of deliverables in accordance with Appendix A

No missing data or miscalculations

Inspection/review of deliverables in accordance with Appendix A

90% of all identified Program Integration solutions (by dollar value) are closed within 10% of the original estimate

Tracking monthly expenditures against the plan

tracking performance in anticipating and resolving problems and recovering from delays

Appendix A: Program Integration Deliverables

Deliverable

ID #

Deliverable

Frequency

Distribution TO Reference Section(s) (Requirement ID)

3.2.1 Management Plans and Integration

(PWS-TO1-PI01)

and Other Reviews

(PWS-TO1-PR01)

(PWS-TO1-SC01)

(PWS-TO1-EV03)

(PWS-TO1-IB01)

(PWS-TO1-FM02)

D-TO1-008

D-TO1-009

Documentation Repository

3.2 Program Management and Integration (PWS-TO1-PI10)

(PWS-TO1-PM03)

Final consolidated plan within 5 business days after contract award

Subsequent updates provided at each PMR and upon issuance of new TOs and as required when key personnel or organizational changes occur Electronic Documentation Repository

3.2.2 Financial Management

(PWS-TO1-FM05)

D-TO1-012

Deleted

(PWS-TO1-PM03)

(PWS-TO1-PM04)

(PWS-TO1-PM04)

D-TO1-016

(PWS-TO1-SM01)

(PWS-TO1-QA03)

(PWS-TO1-RM02)

(PWS-TO1-PMG01)

(PWS-TO1-PM02)

(PWS-TO1-CS01)

(PWS-TO1-CS02)

(PWS-TO1-QA01)

D-TO1-025

(PWS-TO1-PM05)

(PWS-TO1-PM02)

(PWS-TO1-PR02)

(PWS-TO1-CM01)

(PWS-TO1-PI07)

(PWS-TO1-PI08)

(PWS-TO1-PI09)

SOW Ref 3.1.2

D-TO1-033

SOW Ref 3.1.2

D-TO1-034

SOW Ref 3.1

D-TO1-035

SOW Ref 3.1f

D-TO1-036

(PWS-TO1-FM06]

(PWS-TO1-PI12)

(PWS-TO1-DM02)

(PWS-TO1-RM05)

(PWS-TO1-PI15)

(PWS-TO1-QA07)

Appendix B: Acronyms

image1.png image2.png