Guam Phased Array - PWS_DRAFT 2022 0118.pdf

PERFORMANCE WORK STATEMENT

FOR

SARSAT Guam Phased Array Antenna (GPAA)

January 18, 2022

1.0 Scope

The National Oceanic and Atmospheric Administration's (NOAA) National Environmental Satellite, Data, and Information Service (NESDIS) manages the Nation's operational geostationary and polar-orbiting environmental satellites and manages a large collection of atmospheric, geophysical, and oceanographic data.

Within NESDIS, the Office of Satellite and Product Operations (OSPO) manages and directs the operation of the central ground facilities which ingest, process, and distribute environmental satellite data and derived products to domestic and foreign users. The Direct Services Branch of OSPO manages and operates the Search and Rescue Satellite-Aided Tracking (SARSAT) program. The NESDIS SARSAT program and system are part of the international Cospas-Sarsat (C/S) System.

The purpose of the Cospas-Sarsat System is to provide distress alert and location data for search and rescue (SAR), using spacecraft and ground facilities to detect and locate the signals of Cospas-Sarsat distress radio beacons operating on 406 MHz. An earth receiving station in the Cospas-Sarsat System which receives and processes 406 MHz signals relayed by a Medium Earth Orbit satellite is called a MEOSAR Local User Terminal (MEOLUT).

A MEOLUT functions by utilizing antennas to collect data from MEOSAR satellites which is then used by a Location Processor (LP) to generate distress alerts. This contract is to design, procure, install and maintain a Guam Phased Array Antenna (GPAA). The GPAA will be capable of collecting distress alerts from multiple MEOSAR satellites, accurately time and frequency tagging it, and sending it to the US Mission Control Center (USMCC) for location processing.

2.0 Applicable Documents

National and international documents contain additional information on Cospas-Sarsat radio beacon, space, and ground segments. The most current issue and revision of the following documents are applicable to this procurement:

1. C/S T.001, Specification for Cospas-Sarsat 406 MHz Distress Beacons;

2. C/S T.016, Description of the 406 MHz Payloads Used in the Cospas-Sarsat MEOSAR System

3. C/S T.017, Cospas-Sarsat MEOSAR Space Segment Commissioning Standard

4. C/S T.018, Specification for Second-Generation Cospas-Sarsat 406-MHz Distress Beacons

5. C/S T.019, Cospas-Sarsat MEOLUT Performance Specification and Design Guidelines

6. C/S T.020, Cospas-Sarsat MEOLUT Commissioning Standard

7. C/S A.002, Cospas-Sarsat Mission Control Center Standard Interface Description;

8. C/S A.003, Cospas-Sarsat System Monitoring and Reporting;

9. United States Mission Control Center (USMCC) Rescue Coordination Center (RCC) Messages Document;

10. SARSAT System Security Plan; and

11. SARSAT Configuration Management Plan

12. OSPO Configuration Management Plan

13. OSPO Configuration Management Procedures.

14. NIST Special Publication 800-53 Revision 5

15. DOC IT Security Program Policy (ITSPP)

3.0 Guam Phased Array Antenna (GPAA) Requirements

3.1 General Requirements

3.1.1 Receives Commands/Data from USMCC

An essential capability of the GPAA is to be able to receive and process commands and data from the

USMCC.

The GPAA shall be able to receive and react to all commands and data sent from the USMCC within one

(1) minute. The GPAA shall respond to all commands with an appropriate verification message.

3.1.2 Configuration

All configurable items shall be able to be configured via commands from the USMCC and remote terminal (if a contract provides one to meet all requirements).

3.1.3 Cospas-Sarsat Council Requirement Implementation

At times, the Cospas-Sarsat Council may decide to edit or add additional, sometimes critical requirements to these documents. The contractor shall implement any changes made to these documents within the timeframe specified by the Cospas-Sarsat Council.

3.1.4 Alarms

The GPAA shall send an alarm within one (1) minute when it is not collecting data properly or an anomaly has been detected.

3.1.5 Configure What Data is Sent

The Guam Phased Array Antenna shall be able to be configured to send or suppress alarms, warnings, notifications, and self-test or test PN coded bursts.

3.1.6 Warm Restart and Cold Reboot

The GPAA shall be capable of receiving a command from the USMCC to execute a warm restart in which the Operating System (OS) remains running but services are restarted. The GPAA shall also be capable of receiving a command from the USMCC to execute a cold reboot in which the OS and hardware is completely restarted. The GPAA shall be able to execute and begin collecting and processing data again within one (1) minute of a warm restart and within five (5) minutes of a cold reboot.

3.1.7 System Tests

The GPAA shall be capable of receiving a command from the USMCC to execute various system tests and report back the results to the USMCC. These tests shall include antenna tests, radio frequency (RF) reception tests, communication tests and any other appropriate tests the contractor has implemented.

3.1.8 Destination to Send Data

The GPAA shall be able to send data to the various USMCC destinations. The GPAA shall be able to be commanded to send data to these different locations individually or concurrently.

3.1.9 Orbit Vectors

The GPAA shall be able to receive new Orbit Vectors from the USMCC and use this for pass scheduling (e.g. following satellite maneuvers). The GPAA shall also be able to receive orbit information from the MEOSAR constellations in order to maintain accurate orbit vectors and hence time and frequency tagging.

3.1.10 Autonomous Operation

The GPAA shall be designed so that it can operate autonomously after it has been properly initialized.

Initialization may include items such as providing Orbit Vector data, antenna biases and any other data the GPAA may need to establish a proper working configuration.

3.1.11 Recovery from Anomalies

The GPAA shall be designed to recover from anomalies automatically whenever possible. For recoverable anomalies, the GPAA should recover within five (5) minutes of detecting the anomaly or receiving the command from the USMCC or contractor.

3.1.12 Second Generation Beacon (SGB) Processing Capability

The GPAA shall be able to receive and process SGBs with any Pseudo Random Noise (PRN) sequence defined in C/S T.018. This includes both normal and self-test PRN sequences as defined in Table 2.2 of C/S T.018.

3.1.13 Meets all applicable requirements of Cospas-Sarsat

The GPAA shall meet all requirements and specifications of the following Cospas-Sarsat documents:

C/S T.019, Cospas-Sarsat MEOLUT Performance Specification and Design Guidelines C/S T.020, Cospas-Sarsat MEOLUT Commissioning Standard

As the GPAA is not a full MEOLUT, not all requirements of T.019 and T.020 are applicable. However, all requirements for networking MEOLUT data and MEOLUT channels are applicable and required of the GPAA systems.

3.1.14 Tracking Satellites

The GPAA shall detect 406 MHz emergency beacons and transmit their associated data to the USMCC operated by NOAA at Suitland, Maryland. The GPAA shall be capable of receiving all L-Band downlinks from GNSS satellites that are equipped with a 406 MHz SAR repeater (Reference, C/S T.016 Description of the 406 MHz Payloads Used in the C/S MEOSAR System (Feb 2018).

The GPAA and associated components shall measure the Frequency of Arrival (FOA) and Time of Arrival (TOA) of detected beacon [Reference, C/S T.001 Specification for C/S 406 MHz Distress Beacons (Feb 2018) and C/S T.018 Specification for Second-Generation C/S 406 MHz Distress Beacons (Feb 2018)] messages within the performance parameters defined by C/S T.019, Cospas-Sarsat MEOLUT Performance Specification and Design Guidelines (Feb 2018).

This method of beacon location will be referred to in this document as Frequency Difference of Arrival/Time Difference of Arrival (FDOA/TDOA) location.

The GPAA shall be able to track MEOSAR satellites from local horizon to local horizon regardless of site masking. If there is a local site masking present, the GPAA shall be able to acquire a signal as soon as the satellite is above that site mask.

The GPAA shall be capable of simultaneously tracking and receiving data from at least 10 GNSS satellites equipped with SAR instruments as specified in C/S T.016 while meeting all requirements.

3.1.15 Receive Pass Schedules

The GPAA shall be capable of receiving a pass schedule from the USMCC in the formats that are currently utilized. The GPAA shall implement a received schedule within five (5) minutes after receiving it from the USMCC or after Loss of Signal (LOS) of a pass that is currently being taken.

3.1.16 Generate Pass Schedule

The GPAA shall be able to generate a pass schedule that optimizes the geometry of MEOSAR satellites that are above the local horizon. The GPAA shall be able to do this as commanded or automatically at a set time. The GPAA shall be able to generate a schedule for the following 48 hours.

3.1.17 Self-test Bursts

A self-test burst is a burst with inverted frame sync. The GPAA shall be able to suppress or process self-test bursts based on configuration.

3.2 Installation and Infrastructure

3.2.1 Electrical and Communications

The contractor shall provide the infrastructure to support the antennas’ power and communication lines from the Navy JRM building located in Yigo, Guam. The work will require interfacing with the NAVFAC and building manager and shall consist of (but is not limited to);

A. Investigate site, conduct site survey, & develop engineer plans for proposed conduit and cable routing

B. Develop necessary construction notes C. Design equipment and conduit layout D. Provide Equipment and conduit details E. Provide Electrical schematic for new circuits F. Update existing electrical, layout and elevation drawings G. Provide cable acquisition and installation schedule H. Submit final outside plant design for excavation permit, signed by a licensed engineer I. Finalize as-built drawings per project completion J. All drawings will be CAD based K. Installing or Upgrading HVAC System

3.3 Commissioning

The GPAA shall be commissioned into the C/S Ground Segment by demonstrating compliance with C/S T.019 Cospas-Sarsat MEOLUT Performance Specification and Design Guidelines. following the procedures defined in C/S T.020, Cospas-Sarsat MEOLUT Commissioning Standard.

The GPAA shall be commissioned to Initial Operating Capability (IOC) criteria and SGB requirements within 365 days of contract award. This shall include completion of commissioning testing, submission of the commissioning reports, and integration into operations.

Commissioning of the GPAA will be accomplished by providing the data to an existing, commissioned MEOLUT Location Processor.

3.3.1 C/S T.019, Cospas-Sarsat MEOLUT Performance Specification and Design Guidelines

The GPAA will supplement existing MEOLUTs that are commissioned into the C/S Ground System.

Downtime is calculated as per section TBD.

At times the C/S Council may amend document T.019 to address critical or important matters. In such cases, the GPAA shall be modified and tested to meet the amended specifications within 1 year of the Council decision or before the implementation date, whichever is sooner.

3.3.2 Utilize methods to reduce TOA/FOA Bias

The GPAA shall utilize methods to detect and reduce Time and Frequency measurement bias or errors.

3.3.3 Channel Capacity

The GPAA must be able to continuously detect and process at least 100 active beacons or meet the capacity requirements in T.019, whichever is greater.

3.3.4 Data Format

The GPAA and shall be capable of sending MEOLUT data using the format specified in Figure C.1: XML Schema for the Transfer of TOA/FOA Data Between MEOLUTs, in C/S A.002 - Cospas-Sarsat Mission Control Centres Standard Interface Description (SID).

4.0 Contractor Requirements

4.1 Project Management

The contractor shall designate a Project Manager for this contract. The contractor can designate different Project Managers for each task if they choose. The Project Manager will act as a main point of contact and interface for the NOAA SARSAT Program Contracting Officer’s Representative (COR).

4.1.1 Monthly Operations and Engineering Meeting

The Project Manager shall schedule and lead a monthly meeting where operations and engineering efforts of the GPAA are discussed. This meeting shall cover any anomalies that have occurred, tickets that have been raised, future engineering efforts, and any outstanding actions.

The contractor shall provide meeting minutes to the COR within 3 working days of the meeting. Meeting minutes shall document main discussion points and any outstanding questions and actions. Actions shall include the person responsible for the action, a description of the action, and an estimated date of completion.

4.1.2 Participation in SARSAT Configuration Management Process

The contractor shall participate and follow the SARSAT Configuration Management process by documenting configuration change requests, submitting implementation plans, submitting test plans, and participating in the review process.

All configuration changes of the GPAA shall be done in accordance with the latest versions of the OSPO CM Plan and OSPO CM Procedures.

4.1.3 Technical Working Groups

The Project Manager and/or a technical subject matter expert shall participate in Technical Working Groups held once every 2 – 4 weeks as required. The contractor shall take actions and follow up on actions regarding analysis, questions, or performance within the mutually agreed upon timeframe.

4.2 Operations and Maintenance

4.2.1 Performance Metrics

The GPAA shall miss no more than 1% of all scheduled passes.

4.2.2 Missed Passes

A GPAA is deemed to be down when it does not receive any new valid data from a MEOSAR satellite, or meet the requirements of PWS Section XX, which it was scheduled to track. This will only apply to scheduled passes in which the MEOSAR satellite rises above the local site mask horizon.

A pass for tracking a MEOSAR satellite is defined as any uninterrupted ten minute period where the GPAA is scheduled to track a MEOSAR satellite. A pass is deemed to have been missed when it does not receive any valid data from any known reference beacons or meet all other MEOLUT requirements of PWS Section XX.

4.2.3 Uptime and Downtime

A successful pass is a pass in which all performance requirements are met, and is not considered to be “missed” as defined in Section 4.3.2.

Uptime is calculated as the number of successful passes divided by the total number of passes as per Section 4.3.2

Downtime is calculated as the number of missed passes divided by the total number of passes as per

Section 4.3.2.

The contractor shall ensure the GPAA is “up”, 99% of the time.

4.2.4 Anomaly Response

Missed passes shall be promptly investigated by the contractor (within 10 minutes) and remedied as soon as possible. If a GPAA misses two or more passes in a row, it is deemed to be “down.”

After the GPAA goes down, the contractor shall notify the COR within 15 minutes by email and provide details on the anomaly investigation including but not limited to:

1. What is known about the anomaly

2. Who is investigating/working on resolving the anomaly

3. Expected recovery time

4. Impacts of the outage

5. Any proposed methods to mitigate and/or resolve outage

The Contractor shall continue to provide updates to the COR regarding the above topics until the anomaly is resolved and the system is back “up”. At a minimum, the Contractor shall provide updates every 12 hours. The system will be considered “up” when it successfully tracks a pass or successfully receives data from a MEOSAR satellite for 10 minutes.

4.2.5 Spares/Backup

Due to the nature of the SARSAT program and mission, recovering from system component failures in a timely manner is very important. As such, the contractor shall be able to rectify most anomalies or failures of the GPAA within 12 hours by utilizing remote support, spare parts stored onsite, and onsite personnel as defined in PWS section XX. The contractor shall develop a list of critical spare parts to be maintained at each site which will allow them to rectify most anomalies within 12 hours.

The contractor shall maintain a complete set of replacement components (or system) at the location of their choice. If the GPAA is down for longer than 24 hours, these components or entire system shall be sent to the site to recover or replace the system and bring it back up within 96 hours of the initial missed pass, while any additional troubleshooting of the failed system or components is done.

4.2.6 Software Updates

The Contractor shall utilize a test system, parallel system or other methodology to ensure the updates and patches will not affect system performance. Updates and patches include Operating System or any third party software that is installed on the system. After validating the system functionality, the Contractor shall apply all software updates and patches onto the operational system within four weeks of their release.

If a piece of software is no longer supported by the contractor, it is a security vulnerability and shall be removed or replaced with a version that is supported within 1 month of identification of this vulnerability.

4.2.7 Outdated Hardware

If a hardware component replacement cannot be procured from an original equipment manufacturer

(OEM) source within one month, it is deemed to be outdated and obsolete, and shall be upgraded by the contractor to a newer version within the timeframe specified by the Government. The contractor shall provide a cost and schedule proposal to replace the obsolete equipment within 14 days of notification by the COR or contractor identification of an obsolete part. The replacement of the obsolete part will be considered engineering support (T&M).

4.2.8 On-site Operations

The contractor shall maintain at least one point of contact (POC) that is able to provide 24/7 emergency on-site support. The POC(s) shall be knowledgeable of the GPAA design, hardware, software, and functions. The POC(s) shall also have the sufficient knowledge and training to perform the work defined in this section.

The POC(s) shall obtain and maintain an Alternative ID to access the system if Administrator privileges are required for them to do the work defined in this contract.

The POC(s) shall maintain access to the site where the system is installed. The NOAA SARSAT program will assist whenever needed for the POC(s) to obtain this access.

4.2.8.1 Monthly Site Visits

The POC(s) shall perform at least one site visit a month to the site to perform preventative maintenance and routine maintenance. The site visit should occur within the first 2 weeks of the month. The POC(s) shall locate and document the spare parts, making note of any missing spare parts.

During the monthly site visit, the POC(s) shall assist the NOAA SARSAT personnel in performing a router swap if it is needed. The router will be shipped to the POC(s) in advance with instructions and a return shipping label. The NOAA SARSAT program will provide guidance during the router swap. The POC(s) will ship back the router that was replaced using the box and return label that was provided to them. This router swap will typically only occur 1-2 times per year.

The POC(s) shall also assist the contractor in installing or patching as needed to reduce the likelihood of down time caused by patches.

The POC(s) shall provide a report to the contractor Project Manager who shall then use this as input for the Monthly Report.

4.2.8.2 Site Testing

Once a year, the contractor shall conduct testing to ensure Uninterruptible Power Supplies (UPS) are able to maintain system operations for power outages of at least 15 minutes.

The contractor shall also test to ensure the system is automatically and carefully shut down when the UPS can no longer provide adequate power. The contractor shall test that the systems fully recover automatically once power is restored after power outages that require an automatic shutdown.

The contractor shall provide results of these tests to the Government within two weeks of test completion.

4.3 Deliverables

4.3.1 Anomaly Reports (Down Longer Than a Day)

The contractor shall provide the COR an anomaly report anytime the GPAA is considered down for longer than a day. The contractor shall provide this anomaly report within two weeks of the GPAA going down.

The contractor shall present this anomaly report at the CCB meeting after the report has been provided to the COR.

The Anomaly Report shall contain a timeline of alarms, events, and logs related to the anomaly. The Anomaly Report shall contain a section regarding the investigation and analysis of the root cause. The Anomaly Report shall contain a section regarding strategies for mitigating the problem and duration of the GPAA being down in the future.

4.3.2 Monthly Reports

The contractor shall provide the COR a monthly report which shall be provided with the monthly invoice.

The Monthly Report shall contain a report detailing the number of successful and the number of missed passes during the month. The Monthly Report shall contain a section which details anomalies throughout the month (an anomaly is anytime the GPAA is considered “down” as per section 4.3.3). The Monthly Report shall contain a section detailing the spare parts operationalized during the month, an inventory and status of spare parts remaining at each site, and any plans to replenish spare parts. The Monthly Report shall also contain a section detailing tickets that were opened, closed, or remained open throughout the month. The Monthly Report shall also contain sections that document software patches applied, configuration changes and any other information found during the monthly site visits.

4.3.3 Optional Technical Studies

The contractor shall provide technical studies and reports reimbursable on a Time and Materials basis as requested by the Government.

4.4 Projects

4.4.1 Project Status Report

The contractor shall provide detailed Project Status Reports on the status of any GPAA upgrades that are in progress. These detailed reports shall be provided on a monthly basis while upgrades are in progress.

These reports shall be provided as a separate report from the Monthly Reports which deals with operations.

These reports shall be provided within one week of the start of the calendar month.

The Project Status Report shall contain a section for each project. Each section shall contain a detailed status update, work to be performed over the next month, and long term plan for project completion.

4.4.2 Project Review Meeting

The contractor shall provide a Project Review on the status of the ongoing projects. The contractor shall hold Project Review meetings at least every month while any projects are being performed but may be as often as every 2 weeks if the COR determines more frequent reviews are necessary.

The contractor shall provide information to be presented at this review no later than 3 working days before the review. This review shall be conducted either at the NSOF or remotely using any technology that is made available to the SARSAT program. The contractor shall take minutes of the meeting and provide them within 2 weeks of the Project Review.

4.5 Testing/Commissioning of GPAA After System Changes

If re-commissioning of the GPAA is deemed necessary due to system changes, within 60 days of modification the contractor shall perform necessary testing of the GPAA to be commissioned into the C/S System as specified in C/S T.020 Cospas-Sarsat MEOLUT Commissioning Standard. The contractor shall draft and submit a working paper to commission the GPAA to the next Joint Committee meeting. This working paper shall be distributed to the USA delegation for review no later than 2 weeks before the working paper deadline. The contractor shall attend the Joint Committee meeting, or next relevant C/S meeting, and present the papers.

4.6 Engineering Support – Time and Materials

The contractor shall provide optional engineering support for the LUTs not considered routine operations and maintenance on a time and materials basis.

5.0 Performance Requirements Summary

PWS

Section

Performance Objectives

Minimum Acceptable Quality Level

Incentive/Disincentive

4.3.1, 4.3.2, and

4.3.3

Meets performance and missed pass requirements

As defined in PWS Section Monthly performance-based payment reduction per Section

4.3.4 Provides required

anomaly responses

Meeting the timeframes defined in PWS Section 4.3.4, 90% of the time.

CPARS ratings;

positive/negative Government correspondence

4.3.6 Performs software

updates

Within timeframes specified in PWS Section 4.3.6, 95% of the time.

CPARS ratings;

positive/negative Government correspondence

4.3.8 Perform all on-site

visits and testing

Visits and tests performed within timeframes specified in PWS Section 4.3.8, 99% of the time

CPARS ratings;

positive/negative Government correspondence

4.6 Perform testing and

successful re-commissioning of GPAA as needed

Within 60 days of required MEOLUT LP modifications, 90% of the time

CPARS ratings;

positive/negative Government correspondence

5.1 Missed Pass Disincentives

The contractor is required to ensure the GPAA meets the uptime requirements of sections 4.3.3. If the

GPAA experiences less than 98% uptime, there will be a reduction in the Firm Fixed Price O&M monthly payments.

Uptime Calculation Less than 98% Uptime = 5% reduction of monthly O&M Less than 90% Uptime = 50% reduction of monthly O&M

6.0 Schedule of Deliverables

All deliverables shall be emailed to the COR with a courtesy copy to the Contracting Officer (CO) and Contract Specialist (CS).

PWS Section

Deliverable Frequency/Date

4.1.1 Operations and Engineering

Meeting Minutes

Weekly, within 3 working days after meeting

4.3.1 Anomaly Reports As required, within 2 weeks any time GPAA is considered down for longer than a day

4.3.2 Monthly Report and Invoice Monthly, due by 10th day of the month

4.4.1 Project Status Report The first week of each month while upgrades are in progress

4.4.2 Project Review Meeting Materials

and Minutes

Presentation material due 3 working days before the review, and meeting minutes within 2 weeks of the review

4.5 Recommissioning Working Paper As required after C/S Ground System changes

4.2.8.2 On-site Testing Results Yearly, within 2 weeks of test completion

4.3.3 Technical Studies As required

7.0 IT Security Requirements

The contractor shall comply with all IT Security Requirements listed in this section while performing all work under this contract.

7.1 Timely Response to Tickets Related to Detected Vulnerabilities

Per DOC requirements, the contractor must mitigate all IT Security vulnerabilities within 30 calendar days of detection.

7.2 NIST 800-53 Standard

The contractor shall maintain all systems to NIST Special Publication 800-53 Revision 5 Standard, and the NOAA IT Security Manual (ITSM), based on the Government’s approved FIPS 200 analysis document.

7.3 HSPD-12 Alternative Tokens

Any contractor personnel or subcontracts that require administrator access to the GPAA must obtain and use HSPD-12 alternative tokens to gain VPN access.

7.4 Provide for VPN Access to Government-Provided Laptops Monthly for Scanning/Patching

Any government-provided laptops must be connected via VPN monthly for scanning/patching. This should be done within 24 hours of the request to do so.