SBS0042 PWS (Draft) v3.1 20240709.docx

Attachment 1

FA5000‐XX-X-XXXX

CUI FA2541‐XX-X-XXXX

PERFORMANCE WORK STATEMENT

FOR

Operational Support Airlift/Executive Airlift (OSA/EA) Aircraft Combined Commercial Satellite Communication (COMSATCOM) Services

AT

Scott AFB, IL

21 June 2024

DRAFT

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

The objective is to provide Senior Leaders and their support staff with high throughput COMSATCOM while traveling via equipped Operational Support Airlift/Executive Airlift (OSA/EA) aircraft.

1.2 Scope

The Government requires:

· Global coverage for OSA/EA fleet, (VC-25, C-32, C-40, C-37 & VH-92A)

· Satellite managed subscription services across any required spectrum or orbital constellation (multi-orbit solution)

· Teleport and terrestrial communications backhauls to the U.S. Government’s Executive Airlift Communications Network (EACN) Points of Presence (PoP)

· 24/7/365 vendor reach back for problem resolution

· Television services

· Software integrations of all communications platforms through a single communication Network Management Portal that includes flight planning and Host Nation Agreement Support, and spectrum regulatory licensing services.

The contractor shall offer the Government the opportunity to add additional emerging technology and technical enhancements that are introduced during the contract life cycle, within the scope of this contract.

The Government may require surge support during the base or any option period, and surge modifications will be within the scope of the contract and provide increased support for the defined task areas of this PWS. Surge support over the life of the contract will not exceed 25 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 global communications connectivity for U.S. Senior Leaders on the OSA/EA fleet (VC-25, C-32, C-40, C-37, and VH-92A as equipped). This includes support to the President of the United States, Vice President, Secretary of Defense, Chairman of the Joint Chiefs of Staff, Combatant Commanders, Secretary of State, Secretary of Homeland Security, Director of National Intelligence, and other National Senior Leaders.

SECTION II

2.0 TASK DESCRIPTIONS

All performance requirements (tasks) written below are critical to mission accomplishment. The contractor shall provide support re-grooming efforts at the Government’s request when reconfiguration of the bandwidth is necessary to support evolving mission needs. The performance requirements include the following task(s):

2.1 Task 1 – General Service and Capability Requirements.

2.1.1 Subtask 1.1 – Portability

The Government will purchase a quantity of individual service subscription plans to align with the maximum number of simultaneous operations (SIMOPS) anticipated for the OSA/EA fleet. Quantity will be based on the expected aircraft that will be operational at the same time. To this extent, the term SIMOP is synonymous with service subscription plan. The fleet of aircraft is larger than the quantity of SIMOPs to allow for aircraft to rotate through maintenance and to allow aircraft to support a variety of regional missions. SIMOPs are transferable between aircraft with compatible antenna/modem hardware as determined by Government needs. The contractor shall allow for 20 hours of all services overage per contract Period of Performance, included with each service. Overage is defined as the government using more than the contracted number of SIMOPs at any given time. The contractor shall allow the user to port SIMOP subscriptions from aircraft to aircraft as determined by Government needs.

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

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 report faults, incidents, and outages to the RSSC-West at Peterson Air Force Base, Colorado, the 89 Communication Squadron (CS) Government Security Operations Center (GSOC) 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.. 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

· Ground Station Status – Gateway(s)

· Cloud-based Virtual Software-Defined Networking Service - Gateway(s)

· Airborne SATCOM Terminal Status – Aircraft

2.2 Task 2 – Technical Performance Requirements

2.2.1 Subtask 2.1 - Global High-Capacity Crossover (HCX) Ka-Band Managed Subscription Services At contract start (1 April 2025), the contractor shall provide global Ka-Band HCX managed subscription service plans at the throughput requirements expressed in Table 1, using steerable satellite spot beams centered on a primary terminal in the beam. AMSS-HCX support to fixed wing aircraft shall also support up to 2 additional OSA/EA terminals operating within a 300 nautical mile (NM) distance of the primary terminal. AMSS-HCX shall interoperate with any OSA/EA aircraft configured with Viasat KuKarray Gen II airborne terminals using the M3 series satellite modem. Table 1 specifies the minimum aggregate throughput requirements for 1, 2, or 3 terminals operating within an AMSS-HCX steerable satellite spot beam.

(Center of Beam) Second Terminal * (<300NM from Primary) Third Terminal * (<300NM from Primary)

* 2nd and 3rd terminals within same beam as primary, requirements define minimum ranges that vary with distance from the primary terminal.

Table 1: HCX - Minimum Aggregate Throughput Requirements for fixed wing aircraft

2.2.2 AMSS-HCX shall provide global coverage from approximately 70° north to 70° south latitude (except where the beam footprints cross, e.g. Montana; North Sea; North China, etc.). This throughput and coverage shall be provided when aircraft antenna elevation angles are greater than or equal to 10° degrees. When aircraft antenna elevation angles are lower than 10° degrees, both data rates and coverage shall be “best effort” as depicted by the yellow-shaded areas in Figure 1 below. Data rates are specified for optimum satellite link conditions when aircraft are in flight and operating above 10,000 feet mean sea level (MSL).

Figure 1: HCX Spot Beam Coverage Required

2.2.3 The AMSS-HCX service shall employ three steerable satellite spot beams; 1-AOR, 1-IOR, and 1-POR to provide global coverage and required connections between all OSA/EA equipped KuKarray Gen II and required terrestrial connections to the EACN and/or a US based public internet gateway. An AMSS-HCX SIMOP is defined as a communications connection or network access between a Viasat KuKarray Gen II airborne terminal and a steerable satellite spot beam, resulting in a maximum of six SIMOPs for each steerable satellite beam. The 89 CS GSOC will assign OSA/EA KuKarray Gen II airborne terminals to AMSS-HCX SIMOPs on a mission priority basis.

2.2.4 Table 1 specifies throughput rates for optimum satellite link conditions when aircraft are in flight and operating above 10,000 feet mean sea level (MSL). Service must remain on station-kept satellites throughout the life of the contract. The minimum required service availability shall be 99.5 percent at the highest possible data rates applicable to the service plan with global coverage available from 70° north to 70° south latitude when aircraft are in flight above 10,000 feet MSL. The contractor shall also provide service to aircraft operating below 10,000 feet MSL as well as ground operation at commercial and military airports on a best-effort basis. This service will support rotary wing operations that will routinely operate below 10,000 feet MSL. The contractor shall identify service availability restrictions when operating below 10,000 feet MSL and on the ground to include, but not limited to geographic location, host nation regulations and approvals, airport restrictions, and weather conditions.

2.2.5 The AMSS-HCX service shall use 1 each of non-pre-emptible high-capacity military (HCM) Ka-band steerable spot beams on Viasat Military-Ka (MIL-KA) operational satellites in the Atlantic Ocean Region (AOR), one in the Indian Ocean Region (IOR), and one in the Pacific Ocean Region (POR) satellite footprints. Each HCM spot beam shall be allocated a pair of 100 MHz military Ka-band frequency channels, one supporting the HCM forward link (FL) channel to aircraft operating in the beam and one supporting return link (RL) sub-channels from these aircraft. The HCM channels cross over to commercial Ka-band channels on a MIL-KA gateway spot beam for FL and RL connections to an MIL-KA satellite access stations (SAS). The resulting 100 MHz HCM/HCX channel pairs shall be sufficient to support the Table 1 and 2 throughput requirements while maintaining the 99.5 percent service availability and meeting regulatory requirements. The contractor shall obtain Viasat type approvals as required for the KuKarray Gen II, to interoperate with the HCM beams. Space segment shall be offered on satellites that are currently on-orbit, operational, and station-kept. New satellites and back-up SAS may be incorporated into the contract to replace or augment the service subject to engineering change proposal (ECP) requirements defined in section 2.16 To mitigate weather related service interruptions in CONUS and the broader MIL-KA AOR, the government requires an RF-Over-IP terrestrial connection from the primary MIL-KA AOR SAS in Lino Lakes, Minnesota, to the backup MIL-KA SAS in Winnipeg, Canada. During adverse weather service interruptions at Lino Lakes SAS, the AMSS-HCX AOR gateway RF feeder link shall be alt routed to the Winnipeg SAS, thereby mitigating the AOR service interruption.

2.2.6 AMSS-HCX space segment requirements include the operation and maintenance of a secure command and control (SCC) capability for each HCX steerable spot beam. The SCC capability receives secure latitude and longitude position reports from the primary OSA/EA aircraft terminal assigned by the 89 CS GSOC. The SCC capability shall command and control the associated HCM center of beam position to be co-located with the primary OSA/EA aircraft terminal position.

2.2.7 AMSS-HCX teleport requirements shall include management of integrated mobile broadband router hubs and terrestrial communication backhaul circuits at each primary MIL-KA SAS. The contractor shall ensure hub equipment at the SAS interfaces appropriately with the commercial teleport and 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 hubs shall provide interoperability with the OSA/EA aircraft types (VC-25, C-32, C-40, C-37) and associated KuKarray Gen II modifications and an M3 Modem. Primary SAS locations include: Fucino, Italy (supporting IOR), Lino Lakes, Minnesota USA (supporting AOR), and Auckland, New Zealand (supporting POR).

NOTE: The C-37 aircraft will be supported when compatible equipment is installed later.

2.2.8 On a daily basis the 89 CS GSOC will assign OSA/EA aircraft to AMSS-HCX SIMOPs by region, time, and beam on a mission priority basis.

2.2.9 The contractor’s service shall support a minimum of three (3) forward link (FL) Quality of Service (QoS) IP traffic priority queues for the aircraft. These QoS IP traffic priority queues shall be defined by mapping IP packet differentiated services code point (DSCP) field values marked by the Government network. DSCP class marks and associated priority levels are to be provided by the Government.

2.3 SubTask 2.2 - Star Shield SIMOP Subscription Services

2.3.1 SpaceX Star Shield Subscription Space Segment

At contract start (1 April 2025), the contractor will provide Star Shield Global coverage as a managed SIMOP service plan for OSA/EA aircraft (VC-25, C-32, C-40, C-37, and VH-92A) configured with Star Shield Aero terminals at the throughput requirements expressed in Table 2 below. SIMOPs designated for systems testing platforms, System Integration Labs (SIL) platforms configured with Star Shield Aero terminals will be consistent with aircraft configuration, but only need CONUS coverage with “Best Effort” service level. Host Nation Agreements (HNAs) are not needed for the SIL service.

SIMOP Service Level Tier Throughput (Mbps)

Table 2: Star Shield – Minimum Aggregate Throughput Requirements and CLIN Schedule NOTE: This table will be updated at RFP release with up-to-date information/requirements.

2.4 SubTask 2.3 – Viasat Global VGNet SIMOP Managed Subscription Services

2.4.1 Viasat Global Ku/Ka SIMOP Managed Subscription Services Starting 1 September 2026, the contractor shall provide access to satellite communications services using service subscription plans. Each plan shall be characterized by a service level tier and an associated target data rate or range of target data rates for both forward link (FL) to the aircraft and return link (RL) from the aircraft. Data rates are specified for optimum satellite link conditions when aircraft are in flight and operating above 10,000 feet mean sea level (MSL). Space segment 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. The minimum required service availability shall be 99.5 percent at the highest possible data rates applicable to the service plan with maximum global coverage available when aircraft are in flight above 10,000 feet MSL. The contractor shall also provide service to aircraft operating below 10,000 feet MSL as well as ground operation at commercial and military airports on a best-effort basis. The contractor shall identify service availability restrictions when operating below 10,000 feet MSL and on the ground to include, but not limited to geographic location, host nation regulations and approvals, airport restrictions, and weather conditions.

2.4.2 Viasat Ku/Ka Space Segment Service Tiers

The contractor shall provide service that is compatible with the aircraft mission design series (MDS) and antenna models identified in Table 3 below. SIMOPs designated for aircraft equipped with the KuKarray antenna shall include both Ku- and Ka-band service to provide maximum global coverage (defined as coverage between 65 degrees North and 65 degrees South) at the highest possible data rates applicable to the service plan. SIMOPs designated for systems testing platforms, System Integration Labs (SIL), with the Viasat KuKarray antenna shall include both Ku and Ka-Band services to provide coverage for CONUS only. SIMOPs designated for systems testing platforms, SILs, with the Viasat VR-12H antenna shall include only Ku Band services to provide coverage for CONUS only. Host Nation Agreements (HNAs) are not needed for the SIL service.

Viasat VR-12H

(KuKarray) Ku Only

(VR-12H)

MBR-4020

MBR-4020

MBR-4020

SIMOP Service Tier **

VR-12

* Modem(s) may be replaced by functionally equivalent products (i.e., future modem upgrades) ** SIMOP Service Tiers are transferable between aircraft with compatible antenna/modem hardware

Table 3. Aircraft Hardware

2.4.3 The contractor’s global managed subscription service shall provide coverage between 65 degrees North and 65 degrees South latitude. The Government requires high throughput broadband airborne service where available worldwide. The contractor shall provide subscription service plans at the threshold throughput requirements expressed in megabits per second (mbps) in Table 4 below. The contractor may propose additional geographic specifications and performance categories for the coverage regions identified in Table 5, however, the final contract data rates shall be identified on coverage maps provided by the contractor. The contractor shall ensure the aircraft has service even when minimum forward link (FL), to the aircraft, and return link (RL), from the aircraft, data rates cannot be met if service at lower levels is available. Likewise, the contractor shall ensure the aircraft receives the highest service level available for that tier in the area the aircraft is operating; that is, the contractor shall not throttle service levels or implement maximum information rates below the maximum level for that tier. Service tier names are designated by the primary band that is expected to be used; however, SIMOPs designated for aircraft equipped with the KuKarray antenna shall include both Ku- and Ka-band service. The contractor shall provide a means to continually identify geographic regions where service is available, achievable information rates, and available burst or priority information rates. NOTE: In Table 5, the objective thresholds are listed based on Viasat-3 (VS-3) constellation availability along with Ku-band expansion. The Ku-band expansion requirement may be replaced by global Ka coverage when VS-3 service is available.

Threshold Service Level Tier Throughput (Mbps)

VR-12H

* Contingent upon Ku-Band Expansion

Table 4. Threshold Service Tiers

Objective Service Level Tier Throughput (Mbps)

VR-12H

Objective service levels contingent upon Ku-Band Expansion and VS-3 availability

Table 5. Objective Service Tiers

2.4.4 Table 6 below specifies a service tier contract line-item number (CLIN) schedule and planned service subscription quantities. All quantities are subject to change via surge increase or de-scoping (decrease) at the unit NRC/MRC price specified in the pricing table. However, the government intends to phase out the Priority service tier quantities after the base period as indicated in Table 5. As indicated in Table 1, SIMOP Service Tier CLINs are transferable between OSA/EA aircraft with compatible antenna/modem hardware. That is, the contractor shall provide the ability to transfer and assign SIMOPs to any supported aircraft to ensure the service level is appropriate to the current mission. Transfer of SIMOPs is subject to the constraint that the aircraft antenna/modem hardware must be able to support the service tier. For example, the nominal VC-25 MDS SIMOP service tier is the “Priority” tier, however, a “Plus” service tier, nominally assigned to the C-32 MDS can be transferred to a VC-25 MDS to support the 2nd Viasat KuKarray antenna/modem system in parallel with the “Priority” SIMOP tier assignment to the 1st Viasat KuKarray system. Similarly, all Priority-Ku SIMOP service tiers are transferrable between MDS aircraft with Ku-only compatible antenna/modem systems. In addition, the Government requires that SIMOP SIL CLINs are transferable between SIL terminals where the contractor provides the ability to transfer and assign SIL SIMOPs to any SIL terminal to ensure the service level is appropriate to the current mission.

VR-12H

* Considering SBS0042 Service Start Date of 01 Apr 2025, Viasat services are provided on SBS0019 until 31 August 2026, so Viasat services will not start on SBS0042 until 01 September 2026.

Table 6. Contract Schedule and SIMOP Service Tier CLIN Quantities

2.4.5 The contractor’s service shall support a minimum of three (3) forward link (FL) Quality of Service (QoS) IP traffic priority queues. These QoS IP traffic priority queues shall be defined by mapping IP packet differentiated services code point (DSCP) field values marked by the Government network. DSCP class marks and associated priority levels are to be provided by the Government.

2.5 SubTask 2.4 - Teleport and Terrestrial Services

2.5.1 The Contractor shall ensure that all satellite communications (SATCOM) services provided under this contract, regardless of service provider, connect to two designated EACN points of presence, to provide diverse and redundant pathways.

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

2.5.3 All terrestrial services required for connectivity between respective required teleports to the EACN points of presence must be active on the first day of its respective service start date. HCX and Star Shield services start 01 April 2025, and Viasat service starts 01 September 2026.

2.6 Subtask 2.5 Reliability/Availability

The Contractor shall meet an operational availability for each of the subscription services networks, defined as satellite service to and from aircraft to the satellite gateway, of at least 99 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 in their proposal covering the previous 30 calendar days and the previous year.

2.7 SubTask 2.6 - Web-Based Network Management System (NMS) Software Portal for System Control and Mission Planning The Contractor shall:

a) Provide a singular web-based software network management system (NMS) portal for flight tracking and performance measurement that allows personnel on board the aircraft and in the 89 CS GSOC to view near real-time situational awareness of all aircraft equipped for the any of the SATCOM services, active or inactive in the network.

b) Provide within the software portal all forward link (FL) data rates to the aircraft, return link (RL) data rates from the aircraft, aircraft antenna pointing angles and airframe geometric blockage indication (e.g. aircraft tail and/or attitude induced antenna pointing blockage) in near real time.

c) Provide within the software portal a user scalable global map viewer with geographically registered satellite coverage/capacity overlays and performance parameters for each aircraft including tail number identifier, aircraft position, FL/RL energy per bit to noise ratio (Eb/No), and FL/RL throughput estimates in near real time. Included within this will be an overlay showing map zones where HNAs have been approved shaded in Green, and zones where HNAs are not approved shaded in Red, for quick reference by aircraft Communication System Operators (CSO) and mission planning personnel at the GSOC.

d) Provide the APIs required for any service provider platform to be integrated into a single GUI application for communications control across all systems aboard the aircraft, to include importing flight plans and Host Nation Agreement (HNA) filing support.

e) Allow masking or suppression of locations for certain Government-specified aircraft tail numbers within the NMS portal.

f) Provide a network mission planning capability that supports selection and plotting of standard area navigation waypoints and custom defined waypoints on the service provider’s geographic coverage maps with the ability to zoom the view.

g) Provide the Government the ability to plan flight paths to maximize performance and minimize in flight communication disruptions with automatic system fail-over and interference safeguards.

2.8 SubTask 2.7 - Television Services

The Contractor shall:

a) Provide a means for television service on the aircraft as part of each service included with the SIMOPs services, regardless of the service that is online at any given time. The television service may be implemented as an in-band IPTV service (i.e. Youtube TV) with on-aircraft web-based media players. That is, overlaid, out-of-band TV services requiring the splitting of the forward link RF feed and additional airborne integrated receiver decoders (IRDs) are not required. Users can then selectively coordinate the use of in-band two-way capacity for their mission.

b) At a minimum, the contractor provided television service shall include, major network channels (ABC, CBS, NBC, & Fox) and CNN, MSNBC, Fox News, and the Weather Channel programs regardless of the service that is online at any given time.

2.9 SubTask 2.8 – Frequency Clearances (FCs) and Host Nation Agreement 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 will provide a single process for all services. Additionally, 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. FC request process shall be required at service start. If host nation support becomes necessary for additional locations 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 service provider’s coverage area, as needed by the user. FCs shall be requested for the maximum time-period allowed by the host nation, up to the 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. Contractor shall process all requested HNAs annually, at no additional cost to the government. Contractor shall provide weekly status of total numbers of HNAs processed. The contractor shall provide the ability to automatically suspend service to aircraft operating below 10,000 feet when there is no host nation authorization to do so.

Deliverable: Host Nation Agreement Report, CDRL – C001

2.10 Task 3 - 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 EMI/RFI detection or Government request if events are detected by the Government. The contractor shall support Government exercises focused on the resolution of EMI/RFI interference scenarios as directed, no more frequently than quarterly. 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 Report, CDRL – A001

2.11 Task 4 – 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 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.11.1 Subtask 4.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.11.2 Subtask 4.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 Security 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.12 Task 5 - 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, 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.13 Task 6 - Monthly Status Report

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

0. Number of active terminals using the services leased across all active services

0. Status of active monitoring, management, and control of all services

1. 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)

1. 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)

0. Troubleshooting and customer assistance provided

0. HNA issues and number of HNAs filed to date for the current Period of Performance

0. Planned Changes, to include proposed timeline

0. SIMOPs Planned and Executed: The monthly status report shall demonstrate the planned SIMOP usage versus the executed mission SIMOP usage. This section of the report shall demonstrate the total usage for each SIMOP including total uptime and outage times for each service provided.

0. Status of SIMOP Overage Hours Bank for each service provided, including number of overage hours used this month, cumulatively, and number of overage hours remaining for the Period of Performance.

Deliverable: Monthly Status Report, CDRL – B001

2.14 Task 7 - 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

2.15 Engineering Changes

In the event 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 Engineering Change Proposal (ECP). The ECP shall include but is not limited to link budgets, updated 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 Security Operations Center (SOC), an updated COMSATCOM IA Questionnaire (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.

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.

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.

0. Introduction of personnel

0. Overview of project tasks

0. Review of organization (complexity)

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

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

0. Travel notification and processes

0. Government-furnished information (GFI)

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

0. Analytical Support Status Accreditation (ASSA) Documentation

0. Invoice procedures

0. Monthly meeting dates

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

0. POCs

0. Roles and Responsibilities

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

0. Prioritization of Contractor activities

0. Any initial deliverables

0. Other logistic issues

0. Quality Control Plan (QCP)

0. Sensitivity and protection of information

0. 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.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 Task 14 - 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 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. TOP SECRET/ Sensitive Compartmentalized Information (TS/SCI) voice capability and personnel with U.S. TOP 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 Top-Secret level and will require Sensitive Compartmented Information (SCI) access eligibility for some personnel. During the life of this contract, the Government may require the contractor to support the Government in a classified environment. Therefore, the company must have a final Top Secret Facility Clearance from the Defense Counterintelligence and Security Agency. As such, the contractor is required to hold a DD254 of TOP SECRET at their contract level and have a TS/SCI facility clearance, which will remain applicable on this contract.

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 2020

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.

CUI

image1.jpeg