Attachment 7 - Operations Functional Area - Comprehensive Day-1 Task Order.docx

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

NESDIS Consolidated Antenna & Ground System Contract (NCAGSS) Task Order 6 - Operations Performance Work Statement (PWS) April 2026

Prepared by:

U.S. Department of Commerce National Oceanic and Atmospheric Administration (NOAA)

Attachment J-7 Operations Functional Area - Comprehensive Day-1 Task Order 2.2

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

Table of Contents

Attachment J-7 Operations Functional Area - Comprehensive Day-1 Task Order 2.2

1.0 Overview

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 NOAA Antenna as a Service (NAaaS) program. This task order (TO) 2.2 Performance Work Statement (PWS) specifies the operations requirements needed to support the NAaaS antennas ground systems under the NESDIS Consolidated Antenna and Ground Support Services (NCAGSS) Indefinite Delivery, Indefinite Quantity (IDIQ) Statement of Work (SOW).

2.0 Scope

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 NAaaS antenna ground systems include:

a. Satellite antennas and their associated hardware, software, and networks.

b. Antenna control, monitoring, and configuration.

c. Enterprise infrastructure for the NAaaS program.

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.

Individual system inventories, drawings, descriptions and interfaces are available in the NCAGSS Acquisition Document Library. The Contractor must perform operations activities for the systems and interfaces listed in Appendix A Antenna Ground Systems of the IDIQ SOW. Appendix A of this sample TO contains the Operations Deliverables and Appendix B contains acronyms and meanings.

The Contractor shall provide the required subject matter expertise, personnel, material, equipment, services, and facilities to perform and deliver operations support for the NAaaS antenna systems with no interruption of services.

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

2.1 Place of Performance

The primary work location for this TO2.2 (those requiring full-time staffing on an ongoing basis) are:

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

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

The Continuity of Operations (COOP) site locations for this TO (those that may require full time staffing during actual contingency operations or COOP exercises, in addition to infrequent routine and ad hoc visits) are:

a. NESDIS Command and Data Acquisition (CDA) Stations located in Wallops, Virginia

b. NESDIS Command and Data Acquisition (CDA) Stations located in Fairbanks, Alaska

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

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 Procedures

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)

3.0 Requirements

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

3.1 Project Management

Project management for TO2.2 is defined in the IDIQ SOW Section 3.1.1 Program/Project Management. In addition, the following project management requirements apply to TO2.2 for Operations.

PWS-TO2.2-PM01: The Contractor shall provide and follow their project Quality Assurance Plan (QAP) [D-TO2.2-015] and project Quality Assurance Standard Operating Procedures (QASP) [D-TO2.2-016] 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-TO2.2-PM02: The Contractor shall plan and implement technical quality assurance in the project that encompasses hardware, software, and processes.

PWS-TO2.2-PM03: The Contractor shall generate Contractor Metric Performance Reports [D-TO2.2-001] on items in the Performance Requirements Summary (PRS) table in Section 4 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. The report shall include:

a. Hardware and software operations

b. Documentation

c. Performance

d. Product or service evaluations

e. Verification and validation results

f. Incidents and problems from CCR administration.

PWS-TO2.2-PM04: The Contractor shall provide a written Weekly Status Report [D-TO2.2-002] (work status and plan) covering Monday through Sunday no later than the close of business (COB) the second business day of the week and meeting support to include meeting minutes and agendas.

PWS-TO2.2-PM05: The OSPO Configuration Management Process consists of a CM Plan, Procedure, 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 (CCR) and report progress of CCR closure in the Configuration Change Requests Report. 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-TO2.2-PM06: The Contractor shall conduct a monthly NAaaS Contract Review to review operations 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 it aligns with the NAaaS project objectives.

PWS-TO2.2-PM07: The Contractor shall deliver a Monthly Progress Report [D-TO2.2-020] and provide to the Government and 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-TO2.2-PM08: The Contractor shall provide, individually to the contracting officer, a Contract Financial Report [D-TO2-021] from operations to include spend plans, invoicing, fund status, engineering assessments (EAs), and travel management. The 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.

PWS-TO2.2-PM09: The Contractor shall provide an Associate Contractor Agreement (ACA) [D-TO2.2-022] for any portion of the NCAGSS contract requiring joint participation. The agreements shall include the basis for sharing information, data, technical knowledge, expertise, schedules, and risks in accordance with Section H of the IDIQ Contract. The Operations ACAs shall be maintained by the PI.

PWS-TO2.2-PM10: The Contractor shall provide an Operations Contractor Spend Plan [D-TO2.2-023] as detailed in the IDIQ SOW Section 3.1 (General Requirements) k.

PWS-TO2.2-PM11: The Contractor shall develop and deliver a NAaaS Operations Project Management Plan (PMP) [D-TO2.2-024] and coordinate with the PI.

PWS-TO2.2-PM12: The Contractor shall provide, report, and track contract performance metrics on items detailed in the Contractor’s Service Level Agreement (SLA) as part of the monthly Project Management Review (PMR) 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-TO2.2-PM13: The Contractor shall conduct a Project Management Review [D-TO2.2-011] mid-month on a monthly basis that provides status of technical, schedule and cost performance, risks and issues to the Government and PI. The PMR package shall be provided to the Government and PI 10 days prior to the review.

PWS-TO2.2-PM14: The Contractor shall conduct a project Kickoff meeting [D-TO2.2-027] 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-TO2.2-PM15: The Contractor shall ensure the design manuals, and hardware/users manuals, and Operations and Maintenance manuals are kept up to date based on changes to the system design or maintenance approach.

PWS-TO2.2-PM16: The Contractor 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-TO2.2-PM17: The Contractor shall support the PI in the preparation, documentation, and implementation of a Reliability, Maintainability, and Availability (RMA) program.

3.2 Contract Transition

PWS-TO2.2-CT01: The Contractor shall provide a Contract Phase-In Transition Plan [D-TO2.2-018] in accordance with the IDIQ SOW Section 3.1.2 (Incoming and Outgoing Contract Transitions) 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 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.

m. Management of hardware and software licenses and warranty activity for Contractor managed property coordinated with the PI.

n. Lessons Learned.

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

3.3 Operations

High level operations functions and requirements are provided in Section 3.3 (Operations) of the IDIQ SOW. Additional operations requirements are provided in the following sections.

3.3.1 Satellite and Antenna Operational Support

The Contractor shall provide all processes and resources to implement and deliver products and services supporting the efficient and effective operations of NOAA mission critical NAaaS antenna systems. Antenna activities and software lists are located in the NCAGSS Acquisition Document Library.

PWS-TO2.2-OP01: The Contractor shall provide all required resources for performing operational activities to include:

a. Document updates of requirements, planning events, system configuration, and Standard Operating Procedures (SOP) [D-TO2.2-003].

b. Provide accurate input to the Daily Log Report [D-TO2.2-004].

c. Detect, identify, assess and resolve system anomalies and document in a government-provided tool (currently ECMT) and/or in the Operations Event Report [D-TO2.2-010].

d. Provide notifications to stakeholders and users (e.g. for outages, etc.).

e. Support activities and agreements for system components and services.

f. Ensure the secure operational environments for the NAaaS antenna systems.

g. Establish, monitor, report, and track metrics on Contractor Metric Report [D-TO2.2-001] and provide to the Government and PI.

h. Concur periodic masking antenna updates and document in Operations Event Report or Government provided operations event tracking tool.

i. Coordinate with the Government meetings with working groups, product teams, and vendor partners.

j. Participate in Government required meetings or working groups as directed by the Government.

k. Adhering to the NAaaS Safety Program 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-TO2.2-OP02: The Contractor shall support the antenna ground systems listed in the IDIQ SOW Appendix A, activities include:

a. Load and maintain the tracking controller of each system with current, accurate, and validated ephemeris data to provide antenna tracking to a minimum of 99% operational capability.

b. Perform pointing adjustments and signal peaking of the antennas to maintain data reception.

c. Re-point antennas to different spacecraft, when approved by the Government.

d. Coordinate the work required to recover from outages using the CM process and inform the Shift Supervisor on duty before beginning and after completing the work.

e. Report antenna outages in operations daily log, in the TO weekly report, and tracked in the monthly Contractor metric report.

f. Monitor pass schedules to ensure all missions are scheduled as expected.

g. Provide software and hardware support for all antenna applications as detailed in the NAaaS Antenna Activities and NAaaS Software lists located in the NCAGSS Acquisition Document Library.

h. Provide NAaaS antenna ground systems support for antenna monitor and control, and configuration of network and software.

i. Provide support for all antenna components to include but not limited to: HPA (High Power Amplifier). LNA (Low-Noise Amplifier), ACS (Antenna Control Systems, Tracking Receivers, SDR (Software Define Radios), Telemetry Receivers, High Data Rate Receivers, Satellite Command Generators, Ranging Systems, Telemetry Processing Equipment, High Data Rate Recorders

PWS-TO2.2-OP03: The Contractor shall perform operator support for system components. This typical support includes:

a. Monitor all mission passes ensuring successful completion of pre-pass, pass and post- pass activities complete successfully

b. Monitor and report status and health of system components on 24/7 operations.

c. Monitor and report system workflow and resource management daily on weekdays.

d. Detect, analyze, and resolve system component or service problems and discrepancies.

e. Resolve problems in NAaaS antenna systems as soon as possible if it affects the ability to control and monitor the spacecraft.

f. Resolve problems for data, systems software, and networking systems.

g. Report system problems and discrepancies as soon as detected.

h. The response time for mission critical issues shall not exceed 15 minutes during business hours and 2 hours during non-business hours. The Contractor shall document and submit a monthly report with the following details - total mission-critical incidents, individual response times, detailed timeline to resolution, and overall SLA compliance percentage

i. Report upgrades and related activities and provide a schedule to stakeholders and users for the activity.

j. Implement system updates, optimizations, and upgrades to operational components and services, in coordination with the Government. Operational components are defined as the hardware, software, communication devices, operating systems, documentation, licenses, and agreements necessary to support operational services.

k. Coordinate corrective maintenance activities and report to PI

l. Support integration and test (I&T) and submit test plans [PWS-TO2.2-008] to the Government and PI as required.

m. Support software reviews and testing to include setup and configuring test environments, verify configuration for the test, and verify that modifications provide the intended functionality.

n. Formulate and draft a Regression Test Plan [D-TO2.2-026] that include options for not impacting antenna down time.

o. Provide 24/7 on call support. The nature of the mission of NOAA satellite operations occasionally requires planned support outside of normal business hours for special events, or the need to perform activities during off business hours so that they do not adversely impact operations or so that work can be done in conjunction with persons in other time zones. Normally, most work will take place during normal business hours and weekdays. However, system issues can arise at any time with the potential to impact operations.

p. Document system outages in the Operations Event Reports when they occur.

q. Plan alternate activities for Critical Weather Days when a waiver to perform work is not granted (the Contractor must plan for alternate work on days when a Critical Weather Day is declared so that schedules can continue to be met). For example, the Contractor might work on systems not affected by Critical Weather Day declaration such as development or test systems or work on activities offline such as documentation or training.

r. Ensure that redundant systems used for operations are always ready for immediate use.

s. Replace hardware used for repair or maintenance with Government provided spares within two (2) hours of receiving the request (defective workstations shall be repaired and placed in the accountable property Government Equipment Spares Inventory).

t. Complete repairs and replacements of Mission Critical equipment; return equipment to Government inventory no later than 4:30 p.m. local time on the business day following the date of receipt of the maintenance request.

u. Return repaired workstations and printers to Government Equipment Spares inventory for use as replacement equipment. Return any repaired device (i.e. workstations, server, printers…) to Government Equipment Spares inventory for use as replacement equipment.

v. Coordinate with the PI inventory management of system licenses.

PWS-TO2.2-OP04: The Contractor shall coordinate technical issues between the Government and Contractor support teams, and across internal and external stakeholder organizations.

PWS-TO2.2-OP05: The Contractor shall provide input to the status reports on NAaaS antenna systems performance to the Government as scheduled and fully coordinate on testing, maintenance, and release of upgrades, anomaly investigations, and implementing modifications to operational systems.

PWS-TO2.2-OP06: The Contractor shall provide support to meet mission critical operational availability requirements in accordance with the NAaaS Requirements Document (OSPO-REQ-55XX.1). Mission critical incidents, including availability, and notification escalation levels are listed in the OSPO Incident Reporting Policy.

3.3.1.1 Operations Training and Presentation Support

PWS-TO2.2-OP07: The Contractor shall:

a. Provide training, as needed, to staff on functionality and execution of NAaaS antenna systems (including automated, manual anomaly, contingency, and recovery procedures).

b. Provide current training material and media for operations [D-TO2.2-005] for NAaaS Antenna Ground Systems listed in the IDIQ SOW, Appendix A and coordinate with the PI to include in a training material repository.

c. Maintain a training log by employees and provide an Employee Training Log/Status Report monthly [D-TO2.2-006].

d. Provide IT support training activities as required, develop training curriculums, conduct classes; monitor and track current training technology, analyze training requirements, and recommend purchase of training materials.

e. Training activities may include formal or informal training. Formal training is generally conducted in a classroom setting with prepared training materials (e.g. handouts, presentations), scheduled in advance with advanced notification, and conducted at a time convenient to most attendees, or as directed by the Government. Informal training may require less preparation and scheduling (e.g. brown bag seminars, drop-in unstructured training sessions, sessions used to convey information not crucial to mission performance, or training that could not be reasonably performed as formal training).

f. Provide the Government video and audio recordings of training for use by those who could not attend the training in person.

g. Provide support for preparing presentations, graphics, automated forms creation and maintenance, PowerPoint presentations, word processing documents, and spreadsheets for presentation.

h. Provide application support, including business presentations, and digital image scanning, capture, enhancement, compression, and conversion.

3.3.1.2 Meetings & Data Call Support

PWS-TO2.2-OP08: The Contractor shall participate in the meetings shown below for designated operational meetings at the Governments’and PI requests.

a. Operations Stand Up Meetings (Daily: Monday - Friday)

b. Helpdesk Stand Up and Ticket Review (Daily: Monday - Friday)

c. Configuration Control Board (CCB) Meetings (Weekly)

d. Inventory Review Board (Weekly)

e. Technical Review Meetings (As Required)

f. Weekly TO Status Meetings (Weekly)

g. Plan of Action and Milestones (POA&M) (Weekly)

h. Executive Review Board (Monthly) PWS-TO2.2-OP09: The Contractor shall facilitate and document meeting minutes, action items, and lessons learned IDIQ SOW Section 3.1.1 (Program/Project Management), to the Government for the following meetings:

a. Operations Stand Up

b. Helpdesk Stand Up and Ticket Review

c. Inventory Review Board

d. Technical Review Meetings

PWS-TO2.2-OP10: The Contractor shall respond to Data Call support requests including organizational and technical queries. The schedule or the completion of these requests is on a case-by-case basis.

3.3.1.3. Satellite Launch and Special Activity Support

PWS-TO2.2-OP11: The Contractor shall respond to Government request for satellite launch and special activity support, to include:

a. Provide on-site operational support 24 hours per day x 7 days per week for specific launch operations and special events (to include subject matter expertise and number of personnel on each shift requested by the Government). Typical coverage begins 1-3 days prior to launch and lasts 1-3 days after launch.

b. Load and maintain antenna systems tracking controllers with ephemeris data (provided by spacecraft navigators) during and after satellite maneuvers.

PWS-TO2.2-OP12: The Contractor shall provide and maintain a current Satellite and Special Support Staffing Report/List [D-TO2.2-007] for satellite launch and special activity support prior to the event and/or as requested by the Government.

3.3.1.4 Operations Electronic Call Tracking and Reporting

PWS-TO2.2-OP13: The Contractor shall perform electronic call tracking and reporting activities in the Government-provided tool (currently ECMT), including the accurate population of all required fields in log requests covering maintenance, upgrade, de-installation, installation, relocation, and preventative maintenance. The data fields include:

a. Date and time of the request for service

b. Unique tracking number

c. Equipment type

d. Mission

e. Equipment serial number and DOC inventory barcode number

f. Name of person(s) requesting service

g. Description of services requested

h. Description of resolution actions taken for maintenance requests

i. Required staff to resolve the maintenance request

j. Time required to resolve the request (to the nearest 30 minutes)

k. Completion date and time

l. Spare parts used to complete repair

3.3.2 Systems Analysis and Resolution Support

3.3.2.1 Operational and Back-up Sites

PWS-TO2.2-OP14: The Contractor shall provide support for systems analysis and problem resolution to operational and back up sites. This includes personnel to address problem resolutions in antenna systems, data, product applications, systems software, and networking systems.

3.3.2.2 Facilities Change Configuration Management

PWS-TO2.2-OP15: The Contractor shall conduct Configuration Control Boards (CCB) that address changes impacting NAaaS antenna systems. The Contractor shall complete Contractor Configuration Change Requests (CCR) that address any change impacting NAaaS antenna systems (e.g. domain policy changes, add/remove services or servers on the Mission Support LAN, firewall or switch configuration change, or modification of the physical plant (i.e. adding an equipment rack) and coordinate with the PI.

PWS-TO2.2-OP16: The Contractor shall submit CCRs to the facilities CCB, address questions, and provide any clarification requested.

3.3.2.3 Cable Plant Management

PWS-TO2.2-OP17: The Contractor shall provide support in cable plan management activities:

a. Build/terminate/test/verify any required IT-related cabling. Examples of cabling include CAT6, coaxial, serial, and fiber optic cables.

b. Build/terminate low voltage wiring connections, including serial cables from systems to appliances, or antennas.

c. Provide cable management support for all NAaaS antenna systems, cable connections, and maintenance.

d. Manage all infrastructure cable connections using a cable database application (iTRACS) which contains a graphical interface and output to facilitate the making and tracking of connections.

e. Coordinate all repairs for problems found on infrastructure cabling.

3.3.3 Network and Security Operations

Network and security operations monitoring staff work side-by-side to ensure the reliability, availability, and integrity of the operational networks.

PWS-TO2.2-OP18: The Contractor shall provide resources supporting network, application, systems engineering, and security engineering, to include:

a. Manage enterprise tools to support security operations. This includes system administration activities, installation, patching, updates, troubleshooting issues, configure tools used in the NESDIS environment, parameter modification, and script and middleware code writing.

b. Provide an Enterprise Tools Status Report [D-TO2.2-009] weekly supporting security operations.

c. Ensure 24/7 network availability. Monitoring system networks across internal and external connections

d. Provide daily reports to Government on network statistics (to include but not limited to systems uptime, network availability, open network trouble tickets)

e. Support IT security scans.

PWS-TO2.2-OP19: The Contractor shall formulate and draft a plan for security patching [D-TO2.2-025] to include antenna and enterprise infrastructures for implementation after concurrence with the OSPO Cybersecurity Division.

3.3.3.1 Security Configuration Management

PWS-TO2.2-OP20: The Contractor shall support Security Configuration Monitoring activities of security systems for all relevant devices and applications, and report security configuration status relevant to security configuration baselines. Contractor activities include:

a. Monitor systems using OSPO-approved monitoring tools, Security Content Automation Protocol (SCAP), content, and processes.

b. Evaluate any identified security configuration settings against relevant OSPO and NOAA security configuration baseline.

c. Provide electronic transfer of results of all security configuration monitoring using OSPO standard tools and processes, per the agreed schedule, to the OSPO authoritative security risk management repository.

d. Coordinate with information systems owners, Information System Security Officers (ISSO), and system administrators to report and clarify any identified deviations from security configuration baselines.

e. Ensure all Configuration Items (CI) are properly managed in alignment with the OSPO Configuration Management Plan.

3.3.3.2 Security Data Analysis Services

PWS-TO2.2-OP21: The Contractor shall provide security data analysis services and perform security data analytics services of the IT security incidents and operational anomalies. Services include:

a. Configure, fine-tune, and monitor Security Information Management (SIM) or Security Information and Event Management (SIEM) solutions.

b. Proactively monitor environments using data mining and other advanced data analytic techniques.

c. Review information in NOAA’s security repositories (such as ArcSight) to determine patterns, trends, security vulnerabilities.

d. Provide Security Incident Summary Reports [D-TO2.2-012].

e. Provide trend analysis.

f. Provide anomaly detection.

g. Provide root cause analysis.

h. Monitor network trends.

i. Monitor system and network device behaviors to establish and maintain a baseline of normal patterns and trends for all networks.

j. Report network activities that diverge from normal network patterns or trends.

k. Correlate data from multiple log sources to validate potential intrusions or assess system risk. Examples of relevant log sources include centralized log system, patch status reporting system, vulnerability scanning system, firewall logs, full packet capture system, and web content filtering system.

l. Support annual IT security audits and collect, manage and integrate, all requested Security Control Assessment (SCA) artifacts with the PI and audit team.

3.3.3.3 Communications Security (CEC) Key Loading and Technical Support

PWS-TO2.2-OP22: The Contractor shall provide Communications Security (CEC) key loading and technical support. The government utilizes various Communication Encryption Devices for satellite command and control and payload processing. The devices are vital to ensure accurate, secure communication with satellites and remote ground stations. Encryption keys of these devices must be kept up to date and synchronized with remote encryption devices.

Contractor support to this TO is at the NSOF. Government operations at this facility shall require personnel to have a security clearance at the SECRET level and be a U.S. citizen. The SECRET clearance is issued by the DOC Office of Security.

The communication security activities include:

a. Perform scheduled activities (weekly, monthly, and quarterly) loading of CNCAGSSEC keying material at the scheduled times.

b. Coordinate all performed loads on encryption devices, with Government satellite operations staff and remote CEC technicians, to verify loads do not interrupt or interfere with satellite operations.

c. Ensure CEC loads are performed to an operational capability of no less than 99% as measured by circuit connectivity and availability.

d. Troubleshooting and diagnosis requests of CEC equipment problems (by the CEC Account Manager (CAM))

e. Repair/replace/configure/ test/verify operations of any CEC equipment failure and respond within 15 minutes via phone or email during normal business hours and within 4 hours during non-business hours. The Government will provide a replacement unit(s).

f. Assist with packaging and shipment of failed unit(s) for depot repair.

g. Proper safeguard of all CEC material in Contractor possession in accordance with CEC requirements.

3.3.4 Continuity of Operations (COOP)

PWS-TO2.2-OP23: The Contractor shall provide support and services required for Continuity of Operations (COOP) during OSPO COOP exercises or activations. The Government also participates in these activities. The level of support, at NSOF and the backup site(s), is the same regardless of whether the NSOF is untenable or cannot be used for all, or part, of normal operations. COOP event activation, activities include:

a. Deployment to remote COOP sites for the duration of the event.

b. Support of maintenance COOP and disaster recovery plan/procedures to address the immediate and longer-term needs of the Government.

c. Provide any updates to the Continuity of Operations Plan [D-TO2.2-013] annually.

d. Assess vulnerability to significant service interruptions for NOAA missions and projects.

e. Identify and analyze budgetary, service, and other impacts of extended service disruptions.

f. Provide a comprehensive schedule of all systems, devices, and disk volumes that require disaster recovery backups, the size of the data to be backed up, and the total size of the device or disk volume. The schedule includes both complete and incremental/partial backups, the location of the backup media, how often the backup media is to be rotated, and when the backup media is to be retired.

g. Provide a System Backup Schedule Report [D-TO2.2-014].

h. Maintain disaster recovery backups of all systems, devices, and disk volumes.

i. Perform disaster recovery restorations during COOP exercises.

3.3.5 Information & Cybersecurity Support

PWS-TO2.2-S01: All IT security requirements from Section 3.1.4 (Cybersecurity) of the IDIQ SOW apply to TO2.

PWS-TO2.2-S02: 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 [D-TO2.2-028], in accordance with NOAA/NESDIS policy.

3.3.6 Risk Management

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

PWS-TO2.2-RM02: The Contractor shall prepare a Risk Management Report [(D-TO2.2-017) listing the Contractor’s view of initial operational 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-TO2.2-RM03: The Contractor shall support the Government in the risk management activities and maintain risk related data in the Government-provided risk management tool, Active Risk Manager (ARM), similar tool provided by the Government.

PWS-TO2.2-RM04: The Contractor shall collaborate with the Government on risk management activities and report risk status at the monthly risk review.

4.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 the Appendix A

No missing data or miscalculations

Inspection/review of deliverables in accordance with Appendix A

3.3.1 Satellite and Antenna Operational Support

PWS-TO2.2-OP03

tracking performance in anticipating and resolving problems and recovering from delays

Appendix A: Operations Deliverables

(Requirement ID)

D-TO2.2-001

(PWS-TO2.2-OP18)

D-TO2.2-010

D-TO2.2-011

(PWS-TO2.2-PM13)

SOW Ref 3.1.2

D-TO2.2-018

Contract Phase-In Transition Plan

(PWS-TO2.2-CT01)

SOW Ref 3.1.2

D-TO2.2-019

(PWS-TO2.2-CT01)

(PWS-TO2.2-PM07)

(PWS-TO2.2-PM08)

SOW Ref 3.1

D-TO2.2-022

SOW Ref 3.1 k.

D-TO2.2-023

(PWS-TO2.2-PM10)

(PWS-TO2.2-PM11)

(PWS-TO2.2-OP19)

(PWS-TO2.2-PM14)

(PWS-TO2.2-S02)

Appendix B: Acronyms

image1.png