Draft CTC0388 PWS 20250602_OTTI.docx

Attachment 1

FA5000‐XX-X-XXXX

CUI CTC0388

PERFORMANCE WORK STATEMENT (PWS)

FOR

United States Space Force Operational Test & Training Infrastructure (OTTI) Program Executive Office (PEO) & Delta 11 COMSATCOM Satellite Bandwidth Support

14 May 2025 Version 1

DRAFT

Controlled by: Commercial Satellite Communications Office (CSCO) CUI Category: PROCURE Distribution: NONE

POC: TBD

SECTION I

1.0 DESCRIPTION OF SERVICES

1.1 General

United States Space Force Operational Test & Training Infrastructure (OTTI) Program Executive Office (PEO) and Delta 11 Satellite Communications Services Contract is required to provide Ku and C Band Bandwidth to support Delta 11 testing and evaluation for the Continental United States (CONUS) and Hawaii.

1.2 Scope

The Government requires a minimum of 144 megahertz (MHz) Ku-band bandwidth and 72 MHz C-band bandwidth for Delta 11 testing and evaluation for CONUS and Hawaii.

This task order will also include the option to activate additional Ku-band and C-band commercial satellite bandwidth, as needed, in support of emergent and contingency mission directives. The additional capacity will be used to supplement existing bandwidth by filling gaps in coverage and capacity to any location within the provide Ku and C Band Bandwidth to support testing and evaluation for CONUS and Hawaii.

The Government may require surge support during the duration of the contract, and surge modifications will be within the scope of the task order and provide increased support for the defined task areas of this PWS. Surge support over the life of the task order will not exceed 30 percent of the contractor’s total quoted price for the base and all option periods, excluding any 6-month extension of services pursuant to FAR 52.217-8. The Contractor shall provide a witting letter for surge bandwidth requirements as needed, specific to each transponder, satellite, and vendor, upon Government request.

1.3 Background

Delta 11 operates the National Space Test and Training Complex (NSTTC) to provide Department of Defense (DoD) customers with a safe and secure environment in support of counter-space technique development and space test, training and exercise activities. A key element of that support is continuous access to satellite communications for the use of the NSTTC in accomplishing its mission.

SECTION II

2.0 TASK DESCRIPTION

All performance requirements (tasks) written below are critical to the requested services. The contractor shall provide contiguous, non-preemptible, commercial Ku-band and C-band satellite bandwidth supporting mission requirements. The performance requirements include the following tasks:

2.1 Task 1 - General Service and Capability Requirements

2.1.1 Subtask 1.1 – Flexibility/Optimization

The contractor shall support re-grooming efforts at the Government’s request when reconfiguration of the bandwidth is necessary to support evolving mission needs. The Government will submit an updated Technical Specification to the contractor via the Regional Satellite Support Center (RSSC)-West (rsscwest.commercial@us.af.mil. The timeline for the contractor to process and disseminate the updated Transmission Plans is 3 calendar days from receipt of updated Technical Specification. Further information on Transmission Plan requirements is found in subparagraph 2.8.

2.1.2 Subtask 1.2 – Network Monitoring (NetOps)

The contractor shall collect and deliver the near real-time monitoring, fault/incident/outage reporting, and availability consistent with commercial best practice. The contractor shall also report faults, incidents, and outages to the RSSC-West at Peterson Air Force Base, Colorado, and the COR within ten (10) minutes of the fault, incident, or outage. The contractor’s NetOps monitoring capability should address the following metrics at a minimum:

0. Satellite anomalies likely to disrupt service – Satellite

0. Interference Data – Satellite

0. Spectrum Data – Satellite

2.2 Task 2 – Technical Performance Requirements

2.2.1 Subtask 2.1 – Required Space Segment Coverage and Quality

2.2.1.1 Ku-Band Space Segment Coverage

The Ku-Band space segment coverage area for this requirement shall include CONUS. and Hawaii. The satellite uplink (G) to noise temperature (T) ratio (G/T) must be no less than -4 dB/K for the required coverage area. The effective isotropic radiated power (EIRP) footprints must be no less than 39dBW for the required coverage area. Colorado Springs, CO shall be within 3dBW EIRP and 3 G/T of the maximum EIRP and G/T of the entire coverage area. The minimum look angle shall be no less than 11 degrees for the entire coverage area.

The desired satellite uplink G/T is 1 dB/K and an EIRP of 41dBW for the required coverage areas.

2.2.1.2 C-Band Space Segment Coverage

The C-Band space segment coverage area for this requirement shall include CONUS and Hawaii. The satellite uplink (G) to noise temperature (T) ratio (G/T) must be no less than -3 dB/K for the required coverage area. The effective isotropic radiated power (EIRP) footprints must be no less than 36dBW for the required coverage area. Colorado Springs, CO shall be within 3dBW EIRP and 3 G/T of the maximum EIRP and G/T of the entire coverage area. The minimum look angle shall be no less than 11 degrees for the entire coverage area.

The desired satellite uplink G/T is 1 dB/K and an EIRP of 41dBW for the required coverage areas.

2.2.1.3 Coverage extending from the California border west into the pacific at a distance of 600 miles is desirable for both the Ku Band and C Band Coverage areas, including the W-291 Special Use Airspace.

W-291 Special Use Airspace San Diego, CA Boundaries. Beginning at lat. 33°12’30”N., long. 117°58’48”W.; to lat. 32°53’00”N., long. 117°41’43”W.; to lat. 32°36’50”N., long. 117°32’57”W.; to lat. 32°35’00”N., long. 117°32’00”W.; to lat. 32°26’24”N., long. 117°32’30”W.; to lat. 32°13’00”N., long. 117°32’00”W.; to lat. 32°11’00”N., long. 117°17’30”W.; to lat. 29°35’00”N., long. 116°02’30”W.; to lat. 29°35’00”N., long. 118°15’00”W.; to lat. 24°00’01”N., long. 125°00’03”W.; to lat. 27°30’00”N., long. 127°10’04”W.; to lat. 30°40’00”N., long. 120°50’03”W.; to lat. 30°50’00”N., long. 120°40’03”W.; to lat. 31°50’00”N., long. 119°42’03”W.; to lat. 32°12’15”N., long. 119°42’03”W.; to lat. 32°44’30”N., long. 119°07’03”W.; to lat. 33°16’35”N., long. 118°25’03”W.; to the point of beginning.

2.2.1.4 The satellites may have an inclined orbit with a maximum satellite inclination no greater than 1.5 degrees for the life cycle of the task order. Station kept satellites are desirable for the lifetime of the task order.

2.2.2 Subtask 2.2 – Required Space Segment Capacity

2.2.2.1 Ku-band Specification

Ku-band space segment shall consist of a minimum of 144 MHz non-preemptible contiguous capacity on cross polarized transponders. The bandwidth will be provided as entire transponders. The bandwidth provided will have a minimum frequency overlap of 54 MHz between polarizations. The bandwidth must be within the transmit frequency range of 13.75 – 14.5 gigahertz (GHz) and receive frequency range of 10.7 – 12.8 GHz.

2.2.2.1 C-band Specification

C-band space segment shall consist of a minimum of 72 MHz non- preemptible contiguous capacity on cross polarized transponders. The bandwidth will be provided as entire transponders. The bandwidth provided will have a minimum frequency overlap of 18 MHz between polarizations. The bandwidth must be within the transmit frequency range of 5.925 – 6.425 gigahertz (GHz) and receive frequency range of 3.7 – 4.2 GHz.

2.2.3 Subtask 2.3 - Additional Service Requirements

2.2.3.1 Bandwidth Support

The vendor shall provide the Space craft Technical User Guide and a Witting Letter clearly state the satellite provider understands that testing and evaluating tactics, techniques, and procedures for identification of and responding to/resolving realistic interfering signals. The witting letter shall acknowledge that all the activities mentioned above will only be conducted on assigned/leased transponders and will not cause harmful interference to other customers.

The vendor will provide engineering support enabling the establishment of authorized power spectral density (PSD) limits, EIRP Limits, and Access Procedures. The vendor shall provide support to transponder saturation testing.

The vendor shall support EMI resolution assistance to include reports upon request.

The Government will be allowed to perform activities that will include the testing and evaluation of counterspace systems, which will involve realistic friendly and interfering signals. The Government will also be allowed to saturate transponders.

Additionally, the test and assess tactics, techniques, and procedures designed to enhance the rapid recognition, response, and resolution of suspected purposeful interference affecting friendly signals. Furthermore, the government will provide education and training for personnel who are involved in identifying, responding to, and assisting in the resolution of suspected purposeful interference impacting friendly signals.

The Government will be allowed to leave unattended carriers, signals, or networks on the bandwidth for operational security, test setup, or event setup.

The Government will be allowed to change signal plans and carrier architecture as desired. The Government will be allowed to peak and pol their users in place of the owner/operator/ bandwidth managers Network Operations Center (NOC).

Satellite coverage maps with clearly depicted and labeled effective isotropic radiated power (EIRP), gain to noise temperature ration (G/T) for the United States, including Hawaii.

2.2.3.2 Link Budget Tool

The vendor shall provide a link budget tool for calculating Link Budgets, such as software like Satmaster Pro or Excel based spreadsheet capable of generating link budgets. The vendor shall provide a link budget tool capable of use on Non-secure Internet Protocol Router (NIPR) Network. The link budget tool shall be capable of running instances on air gapped stand-alone machines. The Link Budget tool will allow for additional terminals and carrier types to be included spontaneously.

2.2.4 Subtask 2.4 – Reliability/Availability

The contractor shall meet an operational availability for transponded bandwidth of 99.999 percent as specified over each 30-day period, calculated daily for the previous 30 days. For each satellite proposed, the contractor shall include a Satellite Availability Report in their quote covering the previous 30 days, the previous year, and/or the lifetime of the satellite.

2.3 Task 3 – Frequency Clearance (FC) and Approvals

The contractor shall support Host Nation Agreement (HNA) efforts in obtaining international approvals for radio spectrum operations under this contract in foreign nations. The contractor shall ensure that international services provided under this contract may be provided as scheduled with the full approval of each affected host nation. Typical services may include, but are not limited to host nation approvals, landing rights, operating agreements, site licenses, and frequency clearances. If host nation support becomes necessary during the life of the task order, contract line-item numbers will be added to the order at the time they are required and shall be invoiced at pass-through rates. The contractor may be required to provide HNAs for any nation covered within the limits defined in the coverage area, as needed by the user. When requested, a temporary FC shall be obtained to meet the service start date requirement while the permanent license is processed. To avoid continual changes to the FC request, the contractor shall procure a license which covers the entire leased bandwidth. For example, should the awarded solution include a 54 MHz transponder, the contractor shall request frequency clearance for the Center Frequency of the transponder +/- 27 MHz. FCs shall be requested for the maximum time period allowed by the host nation, up to the remaining life of the contract. The contractor shall provide the Government with copies of regulatory licenses and approvals obtained to operate and use the spectrum for countries within the required service region.

2.4 Task 4 – Electro Magnetic Interference (EMI)/Radio Frequency Interference (RFI) Identification, Characterization, and Geo-location

The contractor shall provide legible EMI/RFI identification, characterization, and geo-location in accordance with the EMI/RFI Reporting Checklist. Such services include the ability to identify and characterize sub-carrier EMI/RFI being transmitted underneath an authorized carrier, and the ability to geo-locate the source of any and all EMI/RFI. The contractor shall also immediately report the existence of EMI/RFI to the RSSC-West and the COR. Additionally, the contractor shall make best efforts to geo-locate the source of the interference and report findings in accordance with the EMI/RFI Reporting Checklist. The contractor shall support Government exercises focused on the resolution of EMI/RFI interference scenarios as directed, no more frequently than quarterly. The contractor (and/or subcontractors) shall provide initial acknowledgement of EMI/RFI to the RSSC-West by telephone within 10 minutes. Best effort geo-location of the interfering signal source, spectrum analyzer screenshots, and characterization in accordance with the EMI/RFI Reporting Checklist shall be provided within 30 minutes of contractor EMI/RFI detection or Government request if events are detected by the Government. Updates of such information shall be provided to the Government upon change, upon request, or every 2 hours from initial report, until incident resolution. If secure email and/or voice communications are not available, the contractor (and subcontractors) shall use a mutually agreed upon media and voice communications capability capable of protecting sensitive but unclassified data. Upon incident resolution, the contractor shall provide a Summary of Action Report, summarizing the incident, corrective actions taken, and incident resolution, to the RSSC-West. (A A001 – A002)

2.5 Task 5 – Fault Management

The contractor shall monitor and maintain positive control of services provided. When attempting to access or re-access the satellite, the operator will always contact the Network Operations Center (NOC) for the lease at the contact information provided on the Transmission Plan and conduct a peak and polarity adjustment prior to accessing the satellite.

2.5.1 Subtask 5.1 – Fault Reporting

For all services being provided, the contractor shall report fault information to the RSSC-West. Fault information includes but is not limited to: detection, identification, and isolation of faults; and initiation, tracking, and completion of corrective actions. The contractor shall electronically report fault information with the associated signal parameters for out-of-tolerance alarms and carrier-related alarms via trouble tickets to the RSSC-West as well as provide a summary of fault trends and detailed statistics in its Monthly Status Report. Trouble tickets shall be updated every 2 calendar days for non-serious issues regardless of change in status, and daily for serious issues. Serious issues are those that impact service and cause interruptions or outages. Non-serious issues are those that cause no service interruption or outage but hinder the ability to establish new service.

2.5.2 Subtask 5.2 – Service Interruption and Restoration

For service outages, the contractor shall provide verbal and written status reports to the RSSC-West. These reports are in addition to all electronic reports and monthly reports. These reports shall identify the affected service(s) and the cause of outage if known, and the actions already taken and planned to correct the outage. Initial reports shall be provided by phone to the RSSC-West within 10 minutes of detection. Initial trouble tickets shall be submitted to the RSSC-West within 30 minutes and updated hourly thereafter until service is restored. For outages known to be due to failures in contractor-provisioned elements, the contractor shall initiate conference calls between the contractor’s operation center, the COR, the RSSC-West, and for satellite related issues, the applicable satellite operations center (SOC) supporting the contractor’s service. For outages lasting 120 minutes or more, the contractor’s Program Manager (PM) shall participate in the conference calls. For outages lasting 240 minutes or more, the contractor’s senior management shall participate in the conference calls.

2.6 Task 6 – Information Assurance (IA)

IA is applicable to Satellite Access Center, Satellites, and Contractor Enclave controlling/managing satellite communications resources. Details of the contractor solution IA security posture shall be documented and provided COMSATCOM IA Questionnaire (CIAQ). The contractor shall ensure that for all controls identified as part of the CIAQ, or other cybersecurity requirements, the implementation of the controls or mitigations identified are in place at the period of performance start date. The contractor shall continually monitor and verify IA is maintained in accordance with the CIAQ so long as the task order/contract is in effect. The contractor may be subject to Government and/or independent verification.

2.7 Task 7 – Monthly Status Report

The contractor shall deliver a Monthly Status Report to the COR, Contracting Officer, Contract Specialist, and the RSSC-West that addresses the following topics:

· Number of active terminals using the services leased

· Status of active monitoring, management, and control

· Downtimes (to include relevant trouble ticket number, carrier, start, and stop time of trouble event in ZULU time, summary of event.)

· EMI/RFI Incidents regardless of whether downtime was incurred (to include any relevant trouble ticket number, carrier, start and stop time of incident in ZULU time, and summary of event)

· Troubleshooting and customer assistance provided

· Planned Changes (C C001)

2.8 Task 8 – Transmission Plan

The contractor shall operate services in accordance with the contractor submitted and satellite operator approved Transmission Plan provided within 5 calendar days of award and at least 24 hours prior to the start of the lease. Timeline for contractor to process and disseminate updated Transmission Plans is 3 calendar days from receipt of updated Technical Specification. A copy of all such plans shall be provided to the COR and the RSSC-West. The Transmission Plan shall be submitted electronically in MS Excel format and XML format. The Government will provide the tool required to build and convert the Transmission Plan to the XML format. Information to be contained in the Transmission Plan is as follows.

General Information:

· Contractor name/logo

· Tracking number

· Date of Transmission Plan

· Transmission Plan revision

· Contractor PM contact information (name, phone number, and email)

· Contractor NOC contact information (phone number and email)

· Satellite Owner/Operator(s) Operations Center contact information

· Lease begin and end date

· Satellite(s) name and orbital position included on lease

· Transponder(s) included on lease

· Beacon(s) center frequency and polarization for each satellite

Transponder Technical Characteristics Table:

· Satellite name and position (degrees)

· Transponder identification (ID)

· Transponder bandwidth MHz

· Usable bandwidth MHz

· Leased bandwidth MHz

· Saturated flux density at 0 Db per degree Kelvin (Db/K)

· Uplink Center Frequency MHz, Polarization, Antenna/Beam

· Downlink center frequency MHz, polarization, antenna/beam

· Transponder translation frequency

Technical Parameters Table:

· Carrier ID (CXR ID)

· Lineup reference ID

· Transmit and receive terminal ID

· Data rate

· Reed-Solomon code (n,k)

· Modulation and forward error correcting rate

· Symbol rate

· Allocated bandwidth

· Allocated power-equivalent bandwidth

· Transmit center frequency

· Receive center frequency

· Required Energy per bit to Noise ratio (Eb/No) value

· Target Eb/No value

· Uplink EIRP

· Carrier input back off

· Carrier output back off

· Percentage leased bandwidth, leased power, transponder bandwidth, and transponder and transponder power (B B001)

2.9 Task 9 – Operations Support Requirements

The contractor shall have English speaking technicians available 24 hours a day 7 days a week as the focal point for any problems encountered with the leased services. The technicians shall be able to troubleshoot or escalate to the next tier any problems encountered on the leased services.

2.10 Task 10 – Semi-Annual Sun Transit Reporting

The contractor shall provide semi-annual sun transit reports at least 14 calendar days prior to each seasonal eclipse event.

2.11 Task 11 - Witting Letter

The Witting Letter will clearly state that the satellite provider understands the importance of testing and evaluating tactics, techniques, and procedures for identifying and responding to realistic interfering signals. EMI resolution assistance will include reports upon request. The Government activities will involve testing and evaluating counterspace systems, incorporating realistic friendly and interfering signals. Additionally, the tactics, techniques, and procedures will be assessed to enhance the rapid recognition, response, and resolution of suspected purposeful interference affecting friendly signals. The government will also provide education and training for personnel involved in identifying, responding to, and resolving suspected purposeful interference impacting friendly signals. The Witting Letter must acknowledge that all activities will be conducted only on assigned or leased transponders and will not cause harmful interference to other customers. Satellite coverage maps should clearly depict and label effective isotropic radiated power (EIRP) and gain-to-noise temperature ratio (G/T) for the United States, including Hawaii.

SECTION III

3.0 SERVICE SUMMARY

The Contractor service requirements are summarized into performance objectives. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement and will be assessed on an “Acceptable” or “Unacceptable” basis. These thresholds are critical to mission success.

SECTION IV

4.0 DELIVERABLES

The Contractor shall provide deliverable(s) in a format mutually agreed upon by the Government and the Contractor.

The following enumerated deliverables are not expected to change. Due Date intervals are not expected to change but actual dates may need to be revised depending on actual contract start date.

2.5.1 2.5.2

*Standard Distribution: 1 copy of the transmittal letter without the deliverable to the Contracting Officer; 1 copy of the transmittal letter with the deliverable to the Primary COR and RSSC-West.

SECTION V

5.0 GOVERNMENT FURNISHED PROPERTY

5.1 Government Furnished Property, Equipment, Material, Information, or Services The Government will not furnish property or equipment for this requirement.

SECTION VI

6.0 GENERAL INFORMAITON

6.1 Place of Performance

The primary places of performance are:

0. Service to be provided to Government terminals, locations identified within PWS subparagraph 2.2.1. Government terminals shall be operated by Government personnel; the contractor is not required to perform any tasks at Government terminal locations.

0. The contractor’s NOC, to be identified in the contractor’s technical solution.

0. The satellite owner’s/operator’s SOC, to be identified in the contractor’s technical solution

0. The monitoring and control terminal must be located within the satellite footprint and identified in the technical solution.

6.2 Period of Performance

The period of performance is a 12-month base followed by two 6-month option periods. As directed by the Contracting Officer, the contractor shall continue performance in emergency or mission essential conditions. Additionally, the contractor may be required to account for the whereabouts of their personnel should this information be requested by the COR. Service is required and shall be provided immediately upon the period of performance start date.

6.4 Communication and Data Protection Using External Certificate Authority (ECA) PKI

The DoD Cyber Exchange (Public) has established the ECA program to support the issuance of DoD-approved certificates to industry partners and other external entities and organizations. The ECA program is designed to provide the mechanism for these entities to securely communicate with the DoD and authenticate to DoD Information Systems. Contractors shall digitally sign all contract related correspondence transmitted via email. Contractors shall obtain this capability within 10 business days after award of contracts, task orders, or Blanket Purchase Agreements for satellite services.

To obtain certificates visit: https://public.cyber.mil/eca/obtain-an-eca-certificate.

Technical quotes shall acknowledge compliance with this requirement.

6.5 Other Pertinent Information or Special Considerations

6.6 Incentives

Both positive and negative performance will be documented in the Contractor Performance Assessment Reporting System, as appropriate, and will be taken into consideration for follow-on work. Service interruptions, outages, or other conditions resulting in the customer/user not being able to access the service may, at the sole discretion of the Government, result in invoice adjustments after review of Monthly Status Report (PWS subparagraph 2.7), in accordance with G23 Outage Credits.

6.7 Engineering Change Proposals (ECPs)

In the event that a re-configuration of services is proposed by the contractor, a minimum 30-day advance notice shall be provided to the Government and evidence of equivalent net present value shall be provided by the contractor. The notification shall consist of an ECP. The ECP shall include but is not limited to link budgets, coverage maps, draft Transmission Plan, a transition plan for the re-configuration of the service, and a description of the impact to the services if the ECP is not accepted. In situations where the ECP includes a change to a different satellite, NOC, or SOC, an updated CIAQ shall also be included with the ECP and the ECP may be subject to Authorizing Official (AO) approval and acceptance. The ECP will not be accepted by the Government until the Government determines that the action is in the Government’s best interest.

Software beam configuration shall not require contract modification. The contractor shall accommodate user request for software beam reconfiguration with approval from customer.

6.8 Identification of Possible Organizational and Consultant Conflicts of Interest (OCCI)

In accordance with Acquisition Regulation Supplement 52.209-9000, each contractor shall immediately notify the Contracting Officer if/when any potential or actual OCCI, as described in Federal Acquisition Regulation Subpart 9.5, exists for this this procurement.

6.9 Identification of Non-Disclosure Requirements

No sensitive or proprietary information will be made available to the contractor during contract/task order execution.

CUI