CSS0129 PWS__Lband (Draft).pdf
PDF 697 KB Posted
- Solicitation number
- CSS0129
- Issued by
-
Department of the Air Force
About this file
This is a Performance Work Statement (PWS) for a Blanket Purchase Agreement (BPA) to provide global L-band satellite communications services (LTAC and LAISR) at Joint Base Andrews, Maryland. The BPA requires the contractor to provide commercial satellite L-band bandwidth in the 1525.0-1660.0 MHz frequency range, with the ability to lease contiguous, non-preemptive, non-power sharing 25 kHz L-band channels that can be subdivided into five 5 kHz subchannels.
Key requirements include: 24/7/365 Network Operations Center support with English-speaking technicians; 99.7% link availability for FDMA satellite links; global coverage capability with narrow beam coverage areas between 750-2500 km diameter; EMI/RFI identification and geolocation services; Host Nation Agreement support; terrestrial backhaul services with 99.999% availability; and terminal equipment purchase/lease options including L-TAC hardware kits for UHF radio compatibility. The contractor must maintain a SECRET facility clearance and provide secure communications capabilities. The work includes comprehensive fault management, monthly status reporting, and semi-annual sun transit reporting requirements. The PWS emphasizes high service availability, comprehensive network monitoring, and rapid incident response capabilities.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| CSS0129_RFI Comment Resolution Matrix_Lband.xlsx | XLSX spreadsheet |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
CUI FA2541‐XX-X-XXXX
CUI
PERFORMANCE WORK STATEMENT
FOR
COMSATCOM Bandwidth Blanket Purchase Agreement (BPA) for Global L-band (“LTAC” & “LAISR”) services.
AT
JOINT BASE ANDREWS, MARYLAND
Controlled by: AFDW/PK CUI Categories: PROCURE Distribution/Dissemination Controls:
FEDCON AFTER AWARD
POC: CO NAME (240-612-xxx)
Contents
SECTION I
1.0 DESCRIPTION OF SERVICES
1.1 General
1.2 Scope
1.3 Background
SECTION II
2.0 TASK DESCRIPTIONS
2.1 Task 1 – General Service and Capability Requirements
2.1.1 Subtask 1.1 - Reliability/Availability
2.1.2 Subtask 1.2 – Network Operations Center (NOC) Support and Network Monitoring (NetOps)
2.2 Task 2 - Ancillary Space Service Requirements
2.2.1 Subtask 2.1 – Frequency Clearances (FCs)/Host Nation Agreements (HNAs) .. 6
2.2.2 Subtask 2.2 – Teleport and Terrestrial Backhaul Services
2.2.3 Subtask 2.3 – Portability
2.3 Task 3 – Technical Performance Requirements
2.3.1 Subtask 3.1 – Required Space Segment Coverage
2.3.2 Subtask 3.2 – Required Space Segment Capacity
2.3.3 Subtask 3.3 – Terminal Equipment Purchase and Lease
2.3.4 Subtask 3.4 – L-band Tactical Satellite (L-TAC) Hardware Kits
2.4 Task 4 - Electro Magnetic Interference (EMI)/Radio Frequency Interference (RFI) Identification, Characterization, and Geo-location
2.5 Task 5 – Fault Management
2.5.1 Subtask 5.1 – Fault Reporting
2.5.2 Subtask 5.2 – Service Interruption and Restoration
2.6 Task 6 - Information Assurance (IA)
2.7 Task 7 - Monthly Status Report
2.8 Task 8 - Semi-Annual Sun Transit Reporting
SECTION III
3.0 SERVICE SUMMARY
SECTION IV
4.0 GENERAL INFORMATION
SECTION V
5.0 SECURITY REQUIREMENTS
SECTION I
1.0 DESCRIPTION OF SERVICES
1.1 General
The objective of this BPA is to provide mission partners operating globally with a means of rapidly acquiring commercial satellite L-band bandwidth (L-Band Tactical “LTAC” and L-Band Airborne, Intelligence, Surveillance, and Reconnaissance “LAISR”) and ancillary services to meet enduring and emerging communications needs. The specific Area of Responsibility (AOR) will be determined at the task order level.
1.2 Scope
1.2.1 The Government requires:
Global Commercial Satellite Communications (COMSATCOM) Services for L-band bandwidth (L-Band Tactical “LTAC” and L-Band Airborne, Intelligence, Surveillance, and Reconnaissance “LAISR”) and ancillary services
Managed services solutions to achieve global coverage may include one or more of the following: transponded bandwidth, vendor hosted services and equipment at commercial earth stations, Worldwide Internet Protocol (IP) backhaul from commercial gateways to Government Entry Points (GEP) and to the Department of Defense Information Network (DoDIN), to include Program Management support, bandwidth management and analysis tools, terminal lease and purchase options, and access to provided COMSATCOM network monitoring tools via non-secure and secure networks
Satellite managed subscription services across any required spectrum or orbital constellation (multi-orbit solution), and any additional emerging technology and technical enhancements that are introduced during the contract life-cycle
24/7/365 vendor support for problem resolution
1.2.2. The contractor shall offer the Government within the scope of this contract the opportunity to add surge support to defined task areas of this PWS or add emerging technology and technical enhancements that are introduced during the contract life cycle. These types of support will not exceed 20 percent of the contractor’s total proposed cost/price for the base and all option periods, excluding any six-month extension of services pursuant to Federal Acquisition Regulation 52.217-8.
1.3 Background
The United States Air Force (USAF) OSA/EA COMSATCOM Services requirement is for commercial satellite L-band services to meet various mission requirements.
SECTION II
2.0 TASK DESCRIPTIONS
All performance requirements (tasks) written below are critical to mission accomplishment.
The performance requirements include the following task(s):
2.1 Task 1 – General Service and Capability Requirements
2.1.1 Subtask 1.1 - Reliability/Availability
2.1.1.1. The Contractor shall meet an operational availability for each of the managed subscription services networks, as defined at the call order level.
2.1.1.2. Space segment must be offered on a satellite(s) that is currently on-orbit and operational. The contractor shall meet a link availability of 99.7 percent for frequency division multiple access (FDMA) satellite links.
2.1.1.3. The contractor shall include a Network Availability Report for all required networks in their proposal covering the previous 30 calendar days and the previous year.
Deliverable: Network Availability Report, CDRL – C001
2.1.2 Subtask 1.2 – Network Operations Center (NOC) Support and Network Monitoring (NetOps)
2.1.2.1. The contractor shall staff a 24/7/365 NOC with technicians fluent in the English language. The contractor NOC shall be the focal point to the government, for any/all issues encountered with contractor provided services. The contractor shall be capable of collecting and delivering near real-time monitoring, fault/incident/outage reporting, and availability through a Government identified platform. The contractor shall also immediately report faults, incidents, and outages to the RSSC-West at Peterson Air Force Base, Colorado within five minutes of the incident being identified, and the COR/ACOR(s) as soon as possible within 8-hour window of incident being identified.
2.1.2.2. The contract NOC technicians shall be able to troubleshoot or escalate to the next tier any problems encountered on any of the leased services. Tier 1 support is provided by SMEs with direct mission experience, offering immediate troubleshooting and user support. Tier 2 involves network engineers with direct access to infrastructure, resolving more complex issues and collaborating closely with SMEs to align solutions with mission objectives. Tier 3 is handled by advanced engineers and architects who manage the most intricate network challenges and engage in long-term network planning.
2.1.2.3. 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 - Ancillary Space Service Requirements
2.2.1 Subtask 2.1 – Frequency Clearances (FCs)/Host Nation Agreements (HNAs) The contractor shall support Host Nation Agreement (HNA) efforts in obtaining international approvals for radio spectrum operations under this task order in foreign nations. The contractor shall ensure that international services provided under this task order/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.
2.2.2 Subtask 2.2 – Teleport and Terrestrial Backhaul Services
2.2.2.1 The contractor shall provide leased terrestrial backhaul to the DoD PoP identified at the order level. The commercial teleport shall meet an operational availability of 99.95 percent over each 30-calendar day period. The terrestrial connectivity from the commercial teleport to the Government point of presence shall maintain a 99.999 percent operational availability over each 30-calendar day period. The contractor shall deliver terrestrial segment capabilities that are compatible with and of sufficient quantity, to interface with the applicable space segment and commercial teleports. The contractor shall provide all equipment and services from the closest contractor demarcation point for up and down linking end user terminals. If required by an order, the contractor shall provide the user connection from the teleport to the public Internet via a US-based commercial Internet service provider (ISP). Any additional user requirements may be requested at order level.
2.2.2.2 The contractor shall provide any requested terrestrial connectivity no later than 90 days after a call order for any order requiring terrestrial backhaul. The medium used for any hand-off at the Government point of presence will be identified at the order level.
2.2.3 Subtask 2.3 – Portability
At the order level, the contractor shall offer the opportunity to port bandwidth within the AOR in order to meet mission requirements. The contractor shall invoice ported bandwidth at the appropriate rate for the area and mission, in accordance with the contract line-item number (CLIN) list.
2.3 Task 3 – Technical Performance Requirements
2.3.1 Subtask 3.1 – Required Space Segment Coverage
The contractor shall provide the option to lease contiguous, non-preemptive, non-power sharing 25 kHz L-band channels in the 1525.0-1660.0 MHz frequency range. Contractor shall provide ability to sub divide 25 kHz channel to five 5 kHz subchannels. L-band shall operate 1525.0-1559.0 MHz for space to earth (receive) transmissions and 1626.5-1660.0 MHz for earth to space (transmit) transmissions. Contractors shall offer coverage in L-band channel beams of narrow coverage areas between 750-2500 km diameter.
The contractor shall provide global access to space segment that meets the requirements of each call order submitted. Coverage of all landmasses and the water between those land masses may be requested at the order level. Coverage north of 70° North and south of 70° South may be requested on a best effort basis; the Government understands that resources may be limited in these areas. Coverage shall also include reach-back via satellite to Government defined gateways points of presence (PoPs).
The minimum elevation will be provided at the call order level.
2.3.2 Subtask 3.2 – Required Space Segment Capacity
The contractor shall provide capacity that supports a wide variety of missions. Capacity will be determined at the order level.
When terminal locations are provided with each call order, the contractor shall ensure that links close in those locations. When terminal locations are not provided, the contractor shall ensure links close in the worst-case scenario terminal location within the coverage area specified in the request. The worst-case scenario is defined as the satellite communications link budget with the least amount of link margin when all other factors are considered (terminal specifications, EIRP, G/T, data rate, modulation and coding, etc.). At a minimum, bandwidth shall be capable of closing the specified link(s) with sufficient margin; higher margins may be specified at the order level. Letters of supply will be required at the Task Order level.
2.3.3 Subtask 3.3 – Terminal Equipment Purchase and Lease
The contractor shall make radio frequency, intermediate frequency, baseband, and ancillary equipment available for lease or purchase to the Government. All equipment shall be factory tested and appropriately packed for shipment. There will be two separate Firm Fixed Price (FFP) CLINs for Other Direct Costs (ODCs), an ODC CLIN for shipping, and another ODC CLIN for travel. The contractor shall provide service manuals and operational instructions.
The contractor shall provide warranty maintenance and service plan for contractor-leased terminals. The contractor shall ensure that equipment is certified for use with the specified solution.
2.3.4 Subtask 3.4 – L-band Tactical Satellite (L-TAC) Hardware Kits
The contractor shall provide hardware to support L-TAC operations on Ultra High Frequency (UHF) Government Furnished Equipment (GFE) radios. Contractors shall provide UHF to L-band frequency converter “applique” with battery and power supply, and omni-directional antennas to allow UHF radios to communicate over L-band satellites. Kits shall be offered to support manpack, maritime, vehicle and aero users, as listed in the CLIN List. Additional adapter kits and hardware may be requested at the order level.
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 all EMI/RFI. The contractor shall also immediately report the existence of EMI/RFI to the RSSC-West and the GSOC.
The COR will be notified during normal duty hours at the earliest convenience. Additionally, best effort geo-location of the interfering signal source, spectrum analyzer screenshots, and characterization in accordance with the Reporting Checklist shall be provided within 30 minutes of contractor or Government EMI/RFI detection. Once a quarter the contractor shall support Government exercises focused on the resolution of EMI/RFI interference scenarios.
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 and GSOC.
Deliverable: EMI/RFI Report, CDRL – A001
2.5 Task 5 – Fault Management
The contractor shall monitor and maintain positive control of all services provided. When attempting to access or re-access the satellite, the operator will always contact the 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 NOC shall report fault information to the RSSC-West and GSOC. 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 and GSOC 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-urgent issues regardless of change in status, and daily for serious issues. Urgent issues are those that impact service and cause interruptions or outages. Non-urgent 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 NOC shall provide verbal and written status reports to the RSSC-West and GSOC. 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 and GSOC within 10 minutes of detection. Initial trouble tickets shall be submitted to the RSSC-West and GSOC 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, RSSC-West and GSOC, 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 - A002
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 in the Defense Information Systems Agency (DISA) provided COMSATCOM IA Questionnaire (CIAQ). The contractor shall ensure that for all controls identified as part of the CIAQ, or other cybersecurity requirements, and 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 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 Primary COR, Contracting Officer, Contract Specialist, and the RSSC-West that addresses the following topics:
Number of active terminals using the services leased across all active services Status of active monitoring, management, and control of all services Downtimes for any contracted service (to include and relevant trouble ticket number, carrier, start, and stop time of trouble event in ZULU time, summary of event, and credit given to the customer)
EMI/RFI Incidents for any contracted service 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 HNA issues and number of HNAs filed to date for the current period of performance
Planned Changes, to include proposed timeline
Deliverable: Monthly Status Report, CDRL – B001
2.8 Task 8 - 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.
Deliverable: Semi-Annual Sun Transit Report, CDRL – A003
SECTION III
3.0 SERVICE SUMMARY
The Contractor service requirements are summarized into performance objectives that relate directly to mission essential items. 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
PWS
Para.
Acceptable Quality Level Method of Calculation / Surveillance
Subtask 2.2, 2.3, 2.4, and
2.5 – Required Reliability / Availability
2.2 The Contractor shall meet an operational
availability for each of the managed subscription services networks of at least 99.95 percent as specified over each 30-calendar day period, calculated daily for the previous 30 calendar days. The contractor shall include a Network Availability Report for all required networks in their proposal covering the previous 30 calendar days and the previous year.
100% Inspection of Monthly Status Report and Customer Input
Subtask 2.2.1
– Frequency Clearances and Host Nation Agreement Approvals
2.2.1 The contractor shall support Host Nation
Agreement (HNA) efforts in obtaining international approvals for radio spectrum operations under this contract in foreign nations.
100% Inspection of Monthly Status Report and Customer Input
Subtask 2.4 –
EMI/RFI
Identification, Characterizati on, and Geo- Location
2.4 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 of Monthly Status Report, EMI/RFI Report, and Customer Input
Subtask 2.5.2
– Service Interruption and Restoration
2.5.2 RSSC-West notified within 10 minutes; trouble
ticket is opened within 30 minutes
100% Inspection
Task 6 – Information Assurance
2.6 The contractor shall continually monitor and
verify IA is maintained in accordance with the CIAQ so long as the contract is in effect.
Periodic Inspection, as required
Task 7 – Monthly Status Report
2.7 The contractor shall provide the monthly status
report by the 5th business day of each month.
100% Inspection
Task 8 – Semi- Annual Sun Transit Reporting
2.8 The contractor shall provide the semi-annual
Sun Transit report at least 14 days prior to each seasonal eclipse event.
100% Inspection
Operations Support Requirements
5.1
The contractor shall have appropriately cleared English-speaking technicians available 24 hours a day 7 days a week as the focal point for any problems encountered with the leased services.
Random sampling and Customer Input
SECTION IV
4.0 GENERAL INFORMATION
4.1 Kickoff Meeting/Orientation Meeting
4.1.1 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 require a Quality Assurance Survellance Plan (QASP) to monitor and evaluate the quality of services provided and compliance with the contract terms and conditions at any time.
4.2.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 technicians fluent in English with the requisite security clearances available 24 hours a day 7 days a week as the focal point for any problems encountered with any of 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.
5.2 Facility Security Clearance
The work to be performed under this contract is up to the SECRET level. During the life of this contract, the Government may require the contractor to support the Government in a classified environment. The contractor must have a SECRET Facility Clearance from the Defense Counterintelligence and Security Agency. The contractor is required to hold a DD254 of SECRET at their contract level and have a SECRET facility clearance.
5.3 Security Requirements
This section shall be considered a supplement to Block 13 of the Government provided DD Form 254, Contract Classification Specification. The following security requirements shall apply to this effort.
References:
a. DISA Form 786, DISA Statement of Information System Use and Acknowledgement of User Responsibilities
b. DISA Policy Letter, Unauthorized Connections to Network Devices, 11 September 2013
c. DISA Instruction 240-110-8, Information Security
d. DISA Instruction 240-110-36, Personnel Security
e. DISA Instruction 240-110-38, Industrial Security
f. DISA Instruction 240-110-43, Insider Threat Program
g. DISA Instruction 630-230-19, Cybersecurity
h. DoDM 5200.01, Vol 1-4 Information Security Program, 24 February 2012
i. DOD 5200.02, Procedures for the DoD Personnel Security Program, 3 April 2017
j. DoD Instruction 5200.48, Controlled Unclassified Information (CUI), 6 March
k. DOD 5220.22-M, National Industrial Security Program Operating Manual, February 2006 Incorporating Change 02 May 2016
l. DoDM 5105.21 Sensitive Compartmented Information (SCI) Administrative Security Manual: Administration of Information and Information Systems Security (if applicable)
5.4 Government Furnished Property, Equipment, Material, Information, or Service
5.4.1 The Government will not furnish property or services for this requirement.
5.4.2 The contractor will not be required to acquire any property.
File details come from the government source that posted it. Updated .