SBS0051 E4B HCX Draft PWS_28 Aug 2025.pdf

SBS0051

PERFORMANCE WORK STATEMENT (PWS)

FOR

United States Air Force Global Strike Command (AFGSC) E-4B High-Capacity Crossover (HCX) Broadband Aero Mobile Satellite Communication (SatCom) Service

AT

PERFORMANCE LOCATION

11 August 2026 Version 1

DRAFT

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

POC: TBD

Contents

SECTION I

1.0 DESCRIPTION OF SERVICES

1.1 General

1.2 Scope

1.3 Background

SECTION II

2.0 TASK DESCRIPTION

SECTION III

3.0 SERVICE SUMMARY

SECTION IV

4.0 DELIVERABLES

SECTION V

5.0 GOVERNMENT FURNISHED PROPERTY

SECTION VI ................................................................................. Error! Bookmark not defined.

6.0 GENERAL INFORMAITON ........................................... Error! Bookmark not defined.

SECTION I

1.0 DESCRIPTION OF SERVICES

1.1 General

The United States Air Force Global Strike Command (AFGSC) requirement is for communications connectivity for the Secretary of Defense and other U.S. Senior Leaders on the E-4B aircraft fleet, as well as for the National Airborne Operations Center and other E-4B missions.

1.2 Scope

The scope includes global, two-way, broadband Military Ka-band High Capacity Crossover (HCX) satellite service subscriptions, with terrestrial communications backhaul to the internet, two U.S. Government Entry Points (GEP) and two Executive Airlift Communications Network (EACN) Points of Presence (PoPs), secure beam steering capability, web-based Network Management System portal software development, managed network services, 24/7 network operations center (NOC) and technical support services, and Host Nation Approval License (HNAL) support and spectrum regulatory technical assistance. The E-4B HCX service is a FAR part 12 commercial SATCOM service. The E-4B HCX Service shall use existing government owned air and ground modems.

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

1.3 Background

This is a follow-on requirement for commercial satellite communications (COMSATCOM) managed network services for Ka-band aircraft terminals. The current contract will be ended on March 31, 2026. There are no known organizational conflicts of interest.

SECTION II

2.0 TASK DESCRIPTION

All performance requirements (tasks) written below are critical, and include the following task(s):

2.1 – General Service and Capability Requirements

2.1.1 Subtask 1.1 – Portability

Portability is not a user requirement for this task order.

2.1.2 Subtask 1.2 – 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.3 Subtask 1.3 – Network Monitoring (NetOps)

The contractor shall be capable of collecting and delivering the near real-time monitoring, fault/incident/outage reporting, and availability consistent with commercial best practice. The contractor shall also immediately report faults, incidents, and outages to the RSSC-West at Peterson Air Force Base, Colorado, and the SSC CSCO COR. The contractor’s NetOps monitoring capability should address the following metrics at a minimum:

• Satellite anomalies likely to disrupt service – Satellite

• Interference Data – Satellite

• Spectrum Data – Satellite

2.2 Task 2 – Technical Performance Requirements

2.2.1 Subtask 2.1 – Required Space Segment Coverage, Capacity, and Quality

2.2.1.1 The E-4B MIL Ka-Band High-Capacity Crossover (HCX) Service shall provide global coverage from approximately 60° north to 60° south latitude (except where the beam footprints cross, e.g. Montana; North Sea; North China, etc.). The service shall support four HCX-capable E-4B aircraft at highest data rates possible (up to an aggregate of 90 Megabits per second [Mbps]) consistent with government furnished terminal performance when aircraft are at or above 10,000 feet Above Ground Level (AGL) and aircraft antenna elevation angles are greater than or equal to 20° degrees. When aircraft antenna elevation angles are below 20° degrees or the aircraft is operating below 10,000 feet AGL, service coverage, data rates and service availability will be on a “best-effort” basis. HCX service to each aircraft shall be in accordance with the approved transmission plan.

The Service component shall include global HCX Service subscriptions supporting four E-4B aircraft. A subscription is defined as a communications connection between an E-4B HCX-capable aircraft terminal and the Government Entry Points (GEPs), EACN PoPs and/or commercial internet via the E-4B HCX Service. E-4B HCX capable aircraft utilize ThinKom antennas, WPM-1000 modems, and other associated components. The service shall be compatible with these previously described components on the E-4B and be HCX-capable. The service shall be capable of supporting multiple aircraft in a single beam but shall only be required to track one aircraft per beam, either autonomously or manually.

Figure 1: HCX service coverage area Inner ring depicts coverage at a 15⁰ antenna elevation angle off the aircraft Outer ring depicts coverage at a 10⁰ antenna elevation angle off the aircraft Solutions shall offer links capable of supporting the user requirement with link margins that are adequate to overcome degradation that may be caused by equipment or the local environment.

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

The Service shall be offered on satellites that are currently on-orbit, operational, and station-kept.

Service must remain on station-kept satellites throughout the life of the contract. New satellites and back-up satellite access stations (SAS) may be incorporated into the contract subject to engineering change proposal (ECP) requirements defined in section 2.11.

2.2.1.3 E-4B HCX space segment requirements include a secure beam steering capability for each HCX spot beam. The service will point the spot beam antenna to the appropriate latitude and longitude using government provided aircraft location sent via a contractor provided application program interface (API). The government shall provide near real-time access to aircraft information necessary for steerable beam flight following (e.g. location, heading, and altitude) and to meet the requirements for a web-based portal displaying aircraft location/trajectory, altitude, and other functions required to ensure a reliable COMSATCOM service. The service will also include a manual steering capability.

Subtask 2.2.2 – NOC, Network Monitoring, and Situational Awareness Requirements.

2.2.2.1 The contractor shall provide a web-based E-4B HCX Service software portal for network monitoring and global situational awareness. The contractor shall provide current E-4B HCX Service information via the software portal, including contour maps depicting coverage areas and known restrictions when operating below 10,000 feet AGL (including ground operations). The portal will allow personnel on E-4B aircraft, in the NOC and in the E-4B POC to view near real-time flight tracking and situational awareness of MIL Ka-Band HCX-capable E-4B aircraft. The portal shall provide a global map viewer with satellite coverage overlays. The contractor shall restrict portal access to those contractor and government users who have the appropriate clearance and a valid need to know for the information available on the portal. The government shall provide to the contractor a list of authorized government users, including Operational Support Airlift/Executive Airlift (OSA/EA) operators, Diversity Visa travel team members and required staff members and will update the USG access list as needed.

2.2.2.2 The contractor NOC shall collect and track near real-time MIL Ka-Band HCX Service status, fault/outage updates and on-going and planned activities to ensure effective and efficient operations, performance, and availability of the Service, consistent with commercial best practices. The NOC will monitor and track the following information at a minimum:

• Satellite anomalies likely to disrupt service

• Satellite Interference data

• Network infrastructure status

• Secure Commanding infrastructure status

• Maintenance activities

2.2.2.3 The E-4B POC shall be the 24x7 government E-4B HCX focal point. The POC will assign HCX beams to E-4B aircraft on a mission priority basis with the primary aircraft within a beam having steering control of the beam. The contractor NOC shall track which aircraft has been assigned to each HCX beam via a contractor-provided situational awareness portal. The POC is the contractor’s focal point for scheduled maintenance coordination and its authorization.

2.2.3 Subtask 2.4 – Teleport and Terrestrial Connectivity

2.2.3.1 The contractor shall provide access from the E-4B MIL Ka-Band HCX Satellite Access Station (SAS) locations to government network(s) via a global multi-protocol layer switch (MPLS) network. The government will acquire and maintain necessary approvals to connect the E-4B MIL Ka-Band HCX service with government network(s). Terrestrial connectivity from the teleport shall be sufficient to support the operational subscriptions and be routed via separate and geographically diverse contractor MPLS circuits to two GEPs at Offutt AFB, NE and at Colorado Springs, CO and government provided EACN circuits, to enable detailed monitoring, control and optimize the service delivery. The service shall also provide commercial internet access via U.S.-based internet gateways.

2.2.3.2 E-4B HCX teleport requirements shall include management of Government owned ground modems, and terrestrial communication backhaul circuits at each primary Ocean Region SAS. The government shall provide, install and maintain Government owned modems at the SASs in sufficient quantity to support the government’s readiness requirements, sparing considerations and the contractor’s remote monitoring capability. The Government owned ground modems shall provide interoperability with the E-4B Government owned HCX-capable aircraft terminal (ThinKom antenna and Government owned modem). The contractor shall ensure Government owned equipment at the SAS interfaces appropriately with the commercial teleport and terrestrial backhaul services. This includes technical support to make physical connections and perform appropriate operation and maintenance, as well as ensuring hub radio frequency (RF) equipment interfaces with satellites, commercial intermediate frequency (IF) equipment, backhaul, and Internet services at each SAS. The government shall provide the Contractor with training on the Government owned modems and modem management GUI to support MIL Ka-Band HCX Service operations. The Contractor shall develop and deploy an E- 4B HCX Service remote monitoring capability to support Government owned ground modems.

2.2.3.3 The contractor shall provide teleport services to support the transport of voice, video, and data, as well as access to the public internet. Public internet points of presence (PoPs) shall be U.S.-based; users should reach U.S. websites regardless of their location globally.

2.2.4 Subtask 2.5 – 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 Approval Licenses (HNALs) 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, satellite landing rights, operating agreements, site licenses, and frequency clearances. If host nation support becomes necessary during the life of the contract, Contract Line-Item Numbers (CLINs) will be added to the contract at the time they are required and shall be invoiced at pass-through rates on a cost reimbursable basis. The contractor may be required to provide HNALs 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 in order to meet the service start date requirement while the permanent or long-term license is processed. In order to avoid continual changes to the FC request, the contractor shall procure a license which covers the entire leased bandwidth for the maximum time period allowed by the

Carrigan, John W CIV USSF SSC (USA) Is this true? Did the Govt really supply Govt owned equipment for the SAS ground terminals?

Wes Devine We’d need to verify this with the MP. Or possibly the vendor on the current contract?

HARMON, DEAN W CIV USAF AFGSC AFGSC/A5AN

The government supplied WPM-1000 modems for use in the ground.

Carrigan, John W CIV USSF SSC (USA) We should verify the equipment used on the aircraft, also this is redundant to the previous section 2.2.1

Wes Devine Need verification from MP.

HARMON, DEAN W CIV USAF AFGSC AFGSC/A5AN

The equipment used on the aircraft is the WPM-1000, ThinKom antennas and associated equipment for HCX services.

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

When applicable, the contractor shall include a list of countries within the proposed coverage within 60 days of award. This list shall include the frequency licensing requirements and operating restrictions for each of those countries, to include operation below 10,000 feet and on the ground. When applicable, the contractor shall include with the monthly report a table of all restricted zones and status of frequency licenses by country. The contractor shall provide the ability automatically suspend service to aircraft operating below 10,000 feet when there is no host nation authorization to do so.

Deliverable: Host Nation Approval License Report, CDRL – A001

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 Up-channel 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 SSC CSCO COR.

Additionally, the contractor shall make best efforts to geo-locate the source of the interference and report findings in accordance with EMI/RFI guidance (as documented in the Up-channel 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 EMI/RFI guidance (as described in the Up-channel 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.

Deliverable: EMI/RFI Summary of Action Report, CDRL – B001

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

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.

Deliverables: Trouble Ticket, CDRL - B002

2.6 Task 6 – Information Assurance (IA)

The contractor shall monitor and maintain positive control of all IA aspects and monitor and report all cybersecurity incidents.

2.6.1 Subtask 6.1 – Information Assurance (CIAQ)

Information Assurance (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 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.

Deliverable: CIAQ, CDRL – C001

2.6.2 Subtask 6.2 – Cyber Incident Response/External Reporting IAW DoD Instruction 8530.03 CYBER INCIDENT RESPONSE, 09AUG2023, within 72 hours of the discovery, the contractor shall report confirmed Covered Defense Information (CDI) cyber incidents on cleared contractor classified systems and system components to the Defense Counterintelligence and Security Agency (DCSA), and report confirmed CDI cyber breach on unclassified contractor systems and system components to the DoD Cyber Crime Center’s (DC3). Further, IAW Defense Federal Acquisition Regulation Supplement clause 252.204-7012, the contractor shall report cyber incidents involving CDI to the DoD within 72 hours of discovery. Additionally, the contractor shall report all cyber incidents within 72 hours of discovery to the USAF PMO, SSC CSCO COR, and SSC CMK.

The vendor shall, within fifteen (15) days of discovering the cyber incident (inclusive of the 72-hour reporting period), deliver all data used in performance of the contract that the vendor determines is impacted by the incident and begin assessment of potential warfighter/program impact. Incident data shall be delivered in accordance with the Department of Defense Cyber Crimes Center (DC3) Instructions for Submitting Media, available at http://www.acq.osd.mil/dpap/dars/pgi/docs/Instructions_for_Submitting_Media.docx. In delivery of the incident data, the vendor shall, to the extent practical, remove vendor-owned information from Government covered defense information. If the vendor subsequently identifies any such data not previously delivered to DC3, then the vendor shall immediately notify the contracting officer in writing and shall deliver the incident data within ten (10) days of identification. In such a case, the vendor may request a delivery date later than ten (10) days after identification. The contracting officer will approve or disapprove the request after coordination with DC3.

Deliverable: Cyber Security Vulnerability Report (CVR), CDRL – D001

2.7 Task 7 – Monthly Status Report

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

• Number of active terminals using the services leased during the reporting period

• Status of active monitoring, management, and control during the reporting period

• Downtimes within the current reporting period, to include relevant trouble ticket numbers, carrier, start & stop times of trouble events in Zulu time, summary of circumstances of the event, status of reimbursable credits calculated back to the customer because of the event, and additional credit information to include total amount of credit back to the customer by CLIN for each individual trouble ticket resulting from downtime

• EMI/RFI Incidents during the reporting period, regardless of whether downtime was incurred, to include any trouble ticket number, carrier, start and stop times of the incident in Zulu time, and summary of the event (For situational awareness only, and will not supersede the EMI/RFI CDRL requirement) http://www.acq.osd.mil/dpap/dars/pgi/docs/Instructions_for_Submitting_Media.docx.

Carrigan, John W CIV USSF SSC (USA) Added this Cyber Security Vulnerability reporting section. Please review if this is sufficient.

Downs, Stephen Robert (41220) CIV USN NIWC ATLANTIC VA (USA) Added the reporting to include COR and USN PMO. This would cover ensuring the SMEs for NSLC-A get the reports/information as well.

• Troubleshooting and customer assistance provided during the reporting period

• HNAL issues encountered during the reporting period. (For situational awareness only, and will not supersede the HNAL Report CDRL requirement)

• Any changes, including software pushes that were completed in the reporting period

• Summarize any changes, including software pushes planned during future reporting period

• Recap of any and all CyberSecurity incidents that happened in the reporting period (CyberSecurity Vulnerability Reports, CVRs), as well as any additional findings from ensuing CyberSecurity investigation(s) known at the time of MSR submission to the Government. (For situational awareness only, and will not supersede the CVR CDRL requirement)

Deliverable: Monthly Status Report, CDRL – E001

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.

The contractor shall support U.S. SECRET voice capability and personnel with U.S. SECRET security clearances to discuss sensitive information. The reliance of the contractor on a business partner with appropriate clearances and security devices to supply this capability or use of appropriate commercial standard encryption devices and NATO or allied cleared personnel is acceptable.

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.

Deliverables: Semi-Annual Sun Transit Report, CDRL – B004

2.11 Task 11 – 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 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. In the event that the ECP is not accepted by the Government, the contractor is still obligated to provide service at the rates specified in the contract.

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.

Performance Standard

Acceptable Quality Level Method of Surveillance

PWS 2.2.1 – Space Segment Quality

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.

100% Inspection of Monthly Status Report and Customer Input

PWS 2.3 –

Host Nation Approval Licenses

The contractor shall support Host Nation Approval License (HNAL) efforts in obtaining international approvals for radio spectrum operations under this contract in foreign nations.

As required, & 100% Inspection of periodic HNAL Report

PWS 2.4 – EMI/RFI

Identification, Characterization, and Geo-Location

RSSC-West notified within 10 minutes of detection; best effort geo-location of the interfering signal source, spectrum analyzer screenshots, and characterization provided to the RSSC-West within 30 minutes

100% Inspection

PWS 2.5.2 – Service Interruption and Restoration

RSSC-West notified within 10 minutes; trouble ticket is opened within 30 minutes 100% Inspection

PWS 2.6 –

Information Assurance

The contractor shall continually monitor and verify IA is maintained in accordance with the CIAQ so long as the task order is in effect.

Periodic Inspection, as required

PWS 2.6.2 – Cyber Incident

The contractor shall continually monitor and verify Cyber Incidents are identified and reported so long as the

Periodic Inspection, as

Response/External Reporting contract is in effect. required

PWS 2.7 – Monthly Status Report

The contractor shall provide the monthly status report by the 5th business day of each month. 100% Inspection

PWS 2.8 –

Transmission Plan

The contractor shall provide the initial transmission plan 5 days or less after award; at least 24 hours prior to service start date. Subsequent transmission plans shall be provided within 3 days or less from receipt of user requested configuration changes.

100% Inspection

PWS 2.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.

Customer Input

PWS 2.10 – Semi- Annual Sun Transit Reporting

The contractor shall provide the semi-annual Sun Transit report at least 14 days prior to each seasonal eclipse event. 100% Inspection

SECTION IV

4.0 General Information

4.1.1 – Kickoff Meeting.

The Contractor shall schedule and coordinate a Project kick-off Meeting no later than (NLT) five

(5) calendar days after contract award at the location approved by the Government. The meeting will provide an introduction between the Contractor personnel and Government personnel who will be involved with the contract. The meeting will provide the opportunity to discuss technical, management, and logistic issues; travel authorization; communication process between Government and Contractor; and reporting procedures. At a minimum, the attendees shall include key Contractor personnel, OFFICE (SAF/# or AF/#), key Government representatives, and the COR. The Contractor shall provide a Kick-Off Meeting Agenda that will include, but not be limited to, the following.

• Introduction of personnel

• Overview of project tasks

• Review of organization (complexity)

• Schedule (shows major tasks, milestones, and deliverables; planned and actual start and completion dates for each)

• Communication Plan/lines of communication overview (between both Contractor and Government)

• Travel notification and processes

• Government-furnished information (GFI)

• Security requirements (Building access, badges, Common Access Cards (CAC))

• Analytical Support Status Accreditation (ASSA) Documentation

• Invoice procedures

• Monthly meeting dates

• Reporting Requirements, e.g. Monthly Status Report (MSR)

• POCs

• Roles and Responsibilities

• Overview of incoming Transition Plan to include process, timeframes, and status

• Prioritization of Contractor activities

• Any initial deliverables

• Other logistic issues

• Quality Control Plan (QCP)

• Sensitivity and protection of information

• Additional issues of concern (Leave/back-up support)

4.1.2 The Contractor shall provide a draft copy of the agenda NLT 3 days after contract award for review and approval by the COR prior to finalizing. The Government will provide the Contractor with the number of participants for the kick-off meeting and the Contractor shall provide sufficient copies of the presentation for all present.

4.1.3 The Kickoff Meeting location will be held at the (Government's or Contractor’s) facility or another designated location and the date and time will be mutually agreed upon by both parties.

4.2 – Quality Control.

4.2.1 - Quality Assurance. The Government shall rely on the Contractors’ existing quality assurance system as the method to ensure that the requirements of the contract and performance thresholds are met; however, the Government reserves the right to monitor and evaluate the quality of services provided and compliance with the contract terms and conditions at any time.

4.1.2 - Quality Control Plan (QCP). The Contractor shall develop and maintain an effective quality control program to ensure services are performed IAW this PWS, applicable laws and regulations, and best commercial practices. The Contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services with special emphasis placed on those services listed in this PWS. The Contractor’s quality control program is the means by which it assures itself that the work complies with the requirement of the contract.

SECTION V

5.0 Security Requirements

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

5.2 – Security Requirements.

The work performed for this contract will be at the UNCLASSIFIED level.

The following security requirements shall apply to this effort.

References:

a. DoDM 5200.01, Vol 1-4 Information Security Program, 24 February 2012

b. DOD 5200.02, Procedures for the DoD Personnel Security Program, 3 April 2017

c. DoD Instruction 5200.48, Controlled Unclassified Information (CUI), 6 March 2020

d. DOD 5220.22-M, National Industrial Security Program Operating Manual, February

2006 Incorporating Change 02 May 2016

e. DoDM 5105.21 Sensitive Compartmented Information (SCI) Administrative Security

Manual: Administration of Information and Information Systems Security (if applicable)