RFP HC101321R0015.pdf

SEE ADDENDUM

(No Collect Calls)

HC101321R0015 01-Jul-2021

b. TELEPHONE NUMBER

618-418-6331

8. OFFER DUE DATE/LOCAL TIME

10:00 AM 10 Aug 2021

5. SOLICITATION NUMBER 6. SOLICITATION ISSUE DATE

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STANDARD FORM 1449 (REV. 2/2012)

Prescribed by GSA – FAR (48 CFR) 53.212

(TYPE OR PRINT)

(SIGNATURE OF CONTRACTING OFFICER)

ADDENDA X ARE

26. TOTAL AWARD AMOUNT (For Gov t. Use Only )

23.

CODE 10. THIS ACQUISITION IS

SUCH ADDRESS IN OFFER

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT

BELOW IS CHECKED

TELEPHONE NO.

HC10139. ISSUED BY

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a. UNLESS BLOCK

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME

THOMAS M. MAGEE

2. CONTRACT NO. 3. AWARD/EFFECTIVE DATE 4. ORDER NUMBER

(TYPE OR PRINT)

30b. NAME AND TITLE OF SIGNER 30c. DATE SIGNED 31b. NAME OF CONTRACTING OFFICER

30a. SIGNATURE OF OFFEROR/CONTRACTOR 31a.UNITED STATES OF AMERICA

1 27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1. 52.212-4. FAR 52.212-3. 52.212-5 ARE ATTACHED.X

25. ACCOUNTING AND APPROPRIATION DATA

1. REQUISITION NUMBER

20.

ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED.

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, AND 30

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

ARE NOT ATTACHED

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA ARE ARE NOT ATTACHED

(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:

. YOUR OFFER ON SOLICITATION

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN

% FOR:SET ASIDE:UNRESTRICTED ORX

SMALL BUSINESS

17a.CONTRACTOR/ CODE FACILITY

OFFEROR CODE

DISA/DITCO-SCOTT

2300 EAST DRIVE

BLDG 3600

SCOTT AFB IL 62225-5406

18a. PAYMENT WILL BE MADE BY CODE

RATED ORDER UNDER

DPAS (15 CFR 700)

13a. THIS CONTRACT IS A

13b. RATING

CODE15. DELIVER TO CODE 16. ADMINISTERED BY

SEE SCHEDULE

12. DISCOUNT TERMS11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

14. METHOD OF SOLICITATION

RFQ IFB RFPX

FAX:

TEL: SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

8(A)

HUBZONE SMALL

BUSINESS

SIZE STANDARD:

$35,000,000

NAICS:

517410

X

OFFER DATED

29. AWARD OF CONTRACT: REF.

DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND

EMAIL:

TEL:

31c. DATE SIGNED

SEE SCHEDULE

SCHEDULE OF SUPPLIES/ SERVICESITEM NO. QUANTITY UNIT UNIT PRICE AMOUNT

24.22.21.19.

WOMEN-OWNED SMALL BUSINESS (WOSB)

ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

32g. E-MAIL OF AUTHORIZED GOVERNMENT REPRESENTATIVE

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

(CONTINUED)

ACCEPTED, AND CONFORMS TO THE CONTRACT, EXCEPT AS NOTED: ______________________________________________________

32a. QUANTITY IN COLUMN 21 HAS BEEN

RECEIVED INSPECTED

32b. SIGNATURE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32c. DATE 32d. PRINTED NAME AND TITLE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32e. MAILING ADDRESS OF AUTHORIZED GOVERNMENT REPRESENTATIVE 32f . TELEPHONE NUMBER OF AUTHORIZED GOVERNMENT REPRESENTATIVE

37. CHECK NUMBER

FINALPARTIALCOMPLETE

36. PAYMENT35. AMOUNT VERIFIED

CORRECT FOR

34. VOUCHER NUMBER

FINAL

33. SHIP NUMBER

PARTIAL

38. S/R ACCOUNT NUMBER 39. S/R VOUCHER NUMBER 40. PAID BY

41a. I CERTIFY THIS ACCOUNT IS CORRECT AND PROPER FOR PAYMENT 41b. SIGNATURE AND TITLE OF CERTIFYING OFFICER 41c. DATE

42a. RECEIVED BY (Print)

42b. RECEIVED AT (Location)

42c. DATE REC'D (YY/MM/DD) 42d. TOTAL CONTAINERS

STANDARD FORM 1449 (REV. 2/2012) BACK

Prescribed by GSA – FAR (48 CFR) 53.212

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

SEE SCHEDULE

20.

SCHEDULE OF SUPPLIES/ SERVICES

21.

QUANTITY UNIT

22. 23.

UNIT PRICE

24.

AMOUNT

19.

ITEM NO.

HC101321R0015

Section B - Supplies or Services and Prices

SECTION B NARRATIVE

B.1. CONTRACT MINIMUM AND MAXIMUM VALUE.

a. The Commercial Broadband Satellite Program (CBSP) Satellite Services Contract (CSSC II) will provide complex and worldwide end-to-end commercial satellite communications services following the expiration of the CSSC contract.

b. This is an Indefinite-Delivery, Indefinite Quantity contract against which it is planned to award Firm Fixed Price (FFP) type task orders in accordance with Federal Acquisition Regulation Subpart 16.5 – Indefinite Delivery Contracts.

c. The guaranteed minimum amount is $25,000.00 during the base period only. There is no guaranteed minimum for any of the option periods.

d. Maximum Contract Value: The total amount for all orders placed against the contract resulting from this solicitation shall not exceed $979,844,090.00 over a 10-year period:

1. One 3-year base period

2. Three 2- year option periods

3. One 1-year option period

e. The Government anticipates a single contract award resulting from this unrestricted competitive solicitation.

ITEM NO SUPPLIES/SERVICES MAX

QUANTITY

UNIT UNIT PRICE MAX AMOUNT

0001 1 Lot CSSC II - Base

FFP

Base Period FOB: Destination

PSC CD: DG11

MAX

NET AMT

UNIT UNIT PRICE MAX AMOUNT

1001 1 Lot

OPTION CSSC II - OP1

FFP

Option Period 1

UNIT UNIT PRICE MAX AMOUNT

2001 1 Lot

OPTION CSSC II - OP2

FFP

Option Period 2

UNIT UNIT PRICE MAX AMOUNT

3001 1 Lot

OPTION CSSC II - OP3

FFP

Option Period 3

UNIT UNIT PRICE MAX AMOUNT

4001 1 Lot

OPTION CSSC II - OP4

FFP

Option Period 4

CONTRACT MINIMUM/MAXIMUM QUANTITY AND CONTRACT VALUE

The minimum quantity and contract value for all orders issued against this contract shall not be less than the minimum quantity and contract value stated in the following table. The maximum quantity and contract value for all orders issued against this contract shall not exceed the maximum quantity and contract value stated in the following table.

MINIMUM

MINIMUM

AMOUNT

MAXIMUM

QUANTITY

MAXIMUM

AMOUNT

$25,000.00 $979,844,090.00

CLIN DELIVERY/TASK ORDER MINIMUM/MAXIMUM QUANTITY AND CLIN ORDER VALUE

The minimum quantity and order value for the given Delivery/Task Order issued for this CLIN shall not be less than the minimum quantity and order value stated in the following table. The maximum quantity and order value for the given Delivery/Task Order issued for this CLIN shall not exceed the maximum quantity and order value stated in the following table.

CLIN

MINIMUM

QUANTITY

MINIMUM

AMOUNT

MAXIMUM

QUANTITY

MAXIMUM

AMOUNT

Section C - Descriptions and Specifications

CSSC II PWS

COMMERCIAL SATELLITE COMMUNICATIONS (COMSATCOM)

PERFORMANCE WORK STATEMENT (PWS)

SBS0022 Satellite Business Solutions (SBS)

SBS0022

As of June 22, 2021

Contract Number: To be completed at time of award Task Order Number: To be completed at time of award Contractor Name To be completed at time of award Tracking Number: (completed by the KO when complete package is received) Follow-on to Previous Contract and Task Order Number: HC1013-15-D-0002 (SBS0005)

1. Contracting Officer’s Representative (COR).

1.1. Primary COR.

Name: To be completed at time of award Organization:

Department of Defense Activity Address Code (DODAAC):

Address:

Phone Number:

Fax Number:

E-Mail Address:

1.2. Alternate Navy COR.

DODAAC:

Address:

Phone Number:

1.3. Alternate Air Force Space Command AFSPC COR.

DODAAC:

Address:

Phone Number:

2. Task Order Title.

Commercial Broadband Satellite Program (CBSP) Satellite Services Contract (CSSC II).

3. Background.

The United States (U.S.) Navy leases commercial telecommunications services to augment Government-owned and operated telecommunications systems. Currently the Navy acquires Commercial Satellite Communications (COMSATCOM) services through the existing CBSP Satellite Services (CSSC) Contract. CBSP delivers connectivity between Navy and Military Sealift Command (MSC) ships (and other terminals including air and ground) and Navy Designated Points of Presence (NDP) or MSC Designated Points of Presence (MDP). CBSP provides satellite communication (SATCOM) services, monitors the integrity of the end-to-end system, enables bandwidth management to optimize the use of leased SATCOM capabilities, and accounts for security and information assurance (IA) requirements in support of Naval operations. Additionally, the CBSP mission is dynamic, with rapid resource alignment to support mobility requirements. As a separate effort, the Navy and MSC procure, install, and maintain the end user terminals.

4. Objectives.

In support of the U.S. Navy’s COMSATCOM requirements, the objective of the CSSC II is to acquire worldwide commercial telecommunications services, to include satellite capacity in C, Ku, Ka, and/or X-band, for mobile and fixed satellite transceivers on manned and unmanned maritime, airborne, and ground platforms, as well as commercial teleport (CT) services, backhaul connectivity, monitoring and control, and operations. As this is an Indefinite Delivery Indefinite Quantity (IDIQ) contract, the specific band, operating region to be covered and the bandwidth (MHz) to be provided during the period of performance (PoP) will be delineated in individual task orders. CSSC II will augment Government-owned and operated telecommunications systems, providing redundancy and additional capability to Military SATCOM to meet critical mission requirements. The CSSC II will meet the Navy’s increased demand for satellite throughput. The CSSC II will provide the design, integration, support and continuous optimization of the aforementioned objectives. Figure 1 provides a notional architecture of the CSSC II.

Figure 1 – CSSC II Notional Architecture

5. Scope.

The CSSC II shall provide access to an end-to-end service capable of supporting approximately 400 simultaneous full period, full duplex, simplex, and simplex broadcast connections/modems between a NDP/MDP and the end user terminal through the means of space and terrestrial connectivity. Active CSSC II circuits are defined as end-to-end circuits that are currently terminating an end user to a NDP/MDP. Reserve CSSC II circuits are defined as end-to-end circuits that are not currently terminating an end user to a NDP/MDP but are available to support missions as directed by the Government. Each CSSC II circuit will require a Government Furnished Equipment (GFE) modem at each CT. Circuits shall have the capability of operating as full duplex, simplex, symmetric, and asymmetric.

Figure 2 illustrates a notional CSSC II end-to-end architecture, which consists of two parts, and is the focus of this performance work statement (PWS) – space and terrestrial. The space segment is comprised of the commercial satellite and teleport resources required to uplink and downlink satellite links, from GFE modem to GFE Terminal.

The terrestrial segment is composed of the network equipment, backhaul, and NDP Contractor Furnished Equipment (CFE). While the end user terminals are beyond the scope of this PWS, the contractor must thoroughly understand each terminal’s design, capabilities, and interfaces in order to meet the Government’s objectives for the CSSC II

Figure 2 – Notional Architecture End-to-End Service Responsibility

6. Performance Requirements.

6.1 Task 1 – Operations and Architecture.

6.1.1 Subtask 1 – Space Segment.

CSSC II space segment is defined as the commercial teleport and satellite resources needed to establish connectivity between the user terminal and the GFE modem in the commercial teleport. Satellite resources, expressed in terms of power and bandwidth, are the key characteristics that enable the CSSC II space segment to satisfy user terminal data throughput and quality of service requirements. Other important space segment characteristics include quantity of satellites, orbital positions, operating frequency bands, coverage areas and CTs.

6.1.1.1 Satellite Capacity

The contractor shall provide commercial satellite space segment for full duplex communications in the C, Ku, Ka, and X frequency bands; all space segment procured shall be non pre-emptble, and free from interference. The specific band and capacity will be provided at the individual task order level. The amount of capacity will vary over the years based on changing regional concentrations of Navy and MSC operations and mission requirements. When requested by the Government, or upon contractor receipt of a Commercial Satellite Service Request (CSSR), the contractor shall respond with a completed Link Budget Analysis worksheet within 72 hours.

Satellite Availability. The contractor shall meet an operational availability (Ao) for satellite bandwidth of 99.99 percent, calculated daily and averaged for the previous 30 calendar days for all satellites included in active task orders. The contractor shall provide a Satellite Availability Report (SAR) covering the previous 30 calendar days, the previous year, and the lifetime of the satellite for each proposed satellite, to include each frequency band utilized on that satellite. The only exception to providing a SAR is for satellites not yet operational.

The contractor shall provide a Letter of Supply from the satellite operator in response to each task order request for each satellite proposed. The Letter of Supply must indicate the amount of bandwidth provided on the satellite as well as the duration it will be available.

6.1.1.2 Satellite Coverage and Quality

The space segment solution shall provide service to the operational regions as defined in Section 6.1.1.2.4, Operating Regions. Solutions shall offer robust links with optimized satellite G/T and EIRP footprints whenever possible, along with efficient modulations and coding schemes capable of supporting user connectivity requirements with link margins as specified in the CSSR at the task order level. Solutions must meet the service coverage requirements as defined by the individual task orders throughout the Period of Performance (PoP) at all times.

When requested at the task order level, the contractor shall provide Equivalent Isotropically Radiated Power (EIRP) and gain-to-noise-temperature (G/T) satellite coverage maps in a format compatible for display on Google Earth for review, concurrence, and approval by the Government. When inclined orbit satellites are used, there will be no concessions for the variable coverage of the period of the orbit. Meeting the coverage area is defined as closing the satellite link and meeting the elevation angle requirement for all terminals operating within the defined coverage area. Technical parameters to be used for link budgets will be provided at the task order level. For response to the initial task order, the specifications are provided in PWS Appendix A, Technical Specification. When terminal locations are provided in the task order CSSR or the PWS Appendix A, Technical Specification, the contractor shall ensure that links close in those locations. When terminal locations are not specified, meeting the coverage area can be demonstrated by closing the satellite link and meeting the elevation angle requirement for terminals defined in Appendix I – RF Terminal Specs, at the points within the coverage area with the weakest satellite G/T on the uplink and weakest EIRP on the downlink. The link margin shall be sufficient to support the target bit error rate, enhance link robustness, and counter the effect of rain and other propagation effects as well as antenna pointing errors and collateral degradations. Solutions shall offer robust links with an optimized balance of power, bandwidth, modulation, and coding trade-offs to support the user’s requirements. Space segment must be offered on a satellite(s) that is currently on-orbit, and operational. Geosynchronous satellites shall be either station kept or inclined orbit with an inclination of no greater than +/- 6 degrees. If inclined satellites are utilized, then they shall be compatible with the terminals, regions, and operational capacities as defined in Appendix I– RF Terminal Specs.

The contractor shall meet a link availability of 99.7 percent for frequency division multiple access (FDMA) satellite links and 99.5 percent for time division multiple access (TDMA) satellite links.

The Government understands that space segment resources are limited in some regions. Current user terminals require Geosynchronous Earth Orbit (GEO) satellites. The contractor shall be able to provide Highly Elliptical Orbit (HEO), Medium Earth Orbit (MEO), and Low Earth Orbit (LEO) satellite solutions at the task order level as the Government may have terminals able to operate with HEO, LEO and MEO Satellites during the contract lifecycle.

CLINs for other than GEO satellites will be negotiated at the time of the request.

6.1.1.2.1 Contiguous Bandwidth. For task orders requiring 20 MHz of bandwidth or greater, the contractor shall provide blocks of contiguous bandwidth that are no less than 20 MHz in size when able. When Navy bandwidth on a satellite equals or exceeds the full transponder size of that satellite, the contractor should provide the full transponder. Solutions including multiple satellites capable of providing coverage of the target area may be acceptable at the task order level acceptable; however, it is vital to note that each of the Navy SATCOM terminals can only point to one satellite at a time.

6.1.1.2.2 Beam Shaping. When solutions provide the Government rights to shape satellite beams, the beams will be Government controlled. Government controlled refers to beam shaping controlled directly by the Government user/operator via secure connection to the satellite control center without contractor or satellite controller involvement. When these solutions are employed, the contractor shall provide a detailed description of the beam shaping capabilities and processes for each frequency band.

6.1.1.2.3 Beam Steering. When solutions provide the Government rights to steer satellite beams, the beams will be Government controlled. Government controlled refers to beams directly controlled by the Government user/operator via secure connection to the satellite control center without contractor or satellite controller involvement. When these solutions are employed, the contractor shall provide a detailed description of the beam steering capabilities and processes for each frequency band.

6.1.1.2.4 Operating Regions. To minimize potential obstruction by adjacent facilities, equipment, and/or terrain, the elevation angle from each terminal to the satellite shall be no lower than 15 degrees at all locations within the Operating Region. While the coverage requirement for any region may be satisfied with one satellite, a satellite coverage solution using more than one satellite for a particular region, while still meeting the requirements for the Operating Regions described below, is acceptable. This is an overarching PWS which includes operating regions as set forth below. As this is an IDIQ contract, the specific band, operating region to be covered, and the amount of bandwidth to be provided during the PoP will be delineated in the individual task orders.

• Region A. Region A shall provide X, Ka, and Ku-band satellite coverage over the North American Operating Region (as defined in Table 3 - Region A) as depicted in Figure 3 – CSSC II Operational Regions Coverage Graphic.

Longitude Latitude Longitude Latitude Longitude Latitude

-150 60 -54 13 -115 52 -118 19 -70 24 -136 63 -86 2 -47 52

Table 3 – Region A

• Region AF. Region AF shall provide X, Ku and Ka-band satellite coverage over the African Operating Region (as defined in Table 4- Region AF) as depicted in Figure 3 – CSSC II Operational Regions Coverage Graphic.

-15 38 12 40 32 35 60 2 60 -25 32 -37 15 -38 2 2 -15 0

-25 15 -15 38 Table 4 – Region AF

• Region ME. Region ME shall provide X, Ku and Ka-band satellite coverage over the Middle East

Operating Region (as defined in Table 5 - Region ME) as depicted in Figure 3 – CSSC II Operational

28 30 58 42 50 -3 38 36 77 38 28 30

Table 5 – Region ME

• Region E. Region E shall provide X, Ku and Ka-band satellite coverage over the European Operating Region (as defined in Table 6 - Region E) as depicted in Figure 3 – CSSC II Operational Regions Coverage Graphic.

-16 33 -17 54 -7 64 35 64 14 49 41 35 34 25 -16 33

Table 6 – Region E

• Region H. Region H shall provide X, Ku and Ka-band satellite coverage over the Hawaiian Operating Region (as defined in Table 8 – Region H) as depicted in Figure 3 – CSSC II Operational Regions Coverage Graphic.

160 50 -125 50 -100 25 -120 10 160 10 160 50

Table 8 – Region H

• Region NA. Region NA shall provide for X, Ku and Ka-band satellite coverage over the Northern Atlantic Operating Region (as defined in Table 9 – Region NA) as depicted in Figure 3 – CSSC II Operational

-50 65 0 65 5 45 2 22 -80 22 -50 65

Table 9 – Region NA

• Region SA. Region SA shall provide X, Ku and Ka-band satellite coverage over the South American Operating Region (as defined in Table 10 – Region SA) as depicted in Figure 3 – CSSC II Operational

-88 5 -77 14 -52 13 -27 -5 -51 -59 -82 -59 -79 -24 -88 5

Table 10 – Region SA

• Region WP. Region WP shall provide X, Ku and Ka-band satellite coverage over the Western Pacific Operating Region (as defined in Table 11 – Region WP) as depicted in Figure 3 – CSSC II Operational

85 12 140 54 160 50 160 -50 97 -50

Table 11 – Region WP

• Region S1. Region S1 shall provide C, Ka, and X-band satellite coverage over the Atlantic Ocean Operating Region (as defined in Table 12 – Region S1) as depicted in Figure 4 – CSSC II Blue Water Operational Regions Coverage Graphic

-100 65 10 65 10 -65 -100 -65 -100 65

Table 12 – Region S1

• Region S2. Region S2 shall provide C, Ka, and X-band satellite coverage over the Indian Ocean Region Operating (as defined in Table 13 – Region S2) as depicted in Figure 4 – CSSC II Blue Water Operational

-10 65 100 65 100 -65 -10 -65 -10 65

Table 13 – Region S2

• Region S3. Region S3 shall provide C, Ka, and X-band satellite coverage over the Western Pacific Ocean Operating Region (as defined in Table 14 – Region S3) as depicted in Figure 4 – CSSC II Blue Water Operational Regions Coverage Graphic.

80 65 -170 65 -170 -65 80 -65 80 65

Table 14 – Region S3

• Region S4. Region S4 shall provide C, Ka, and X-band satellite coverage over the Eastern Pacific Ocean Operating Region (as defined in Table 15 – Region S4) as depicted in Figure 4 – CSSC II Blue Water Operational Regions Coverage Graphic.

170 65 -80 65 -80 -65 170 -65 170 65

Table 15 – Region S4

Figure 3 – CSSC II Operational Regions Notional Coverage Graphic

Figure 4 – CSSC II Blue Water Operational Regions Coverage Graphic

6.1.2 Subtask 2 – Terrestrial and Commercial Teleports.

6.1.2.1 General Characteristics

The contractor shall deliver terrestrial segment capabilities that are of sufficient quantity, in appropriate geographical locations, and able to interface with CSSC II space segment described in PWS 6.1.1 – Space Segment and terminations at NDPs. The contractor shall provide all equipment and services at the CTs for up and down linking to the Navy end user terminals, connecting to the furnished terrestrial infrastructure, and transmitting and receiving each circuit to the appropriate NDP. The contractor shall provide all equipment and services to implement an end-to-end solution, with the exception of the GFE listed in Section 12, GFE/Government Furnished Information

(GFI).

6.1.2.2 Network Sizing

The contractor shall provide backhaul capacity to support all end user circuits. The contractor shall design and deliver a scalable network to support both serial EIA-530 and Layer 2 Ethernet baseband interfaces at the CTs and NDPs/MDPs. CFE installed at the NDPs/MDPs shall be sized to support the number and type of connections described below:

6.1.2.2.1 The CFE installed at each NDP/MDP shall be sized to support at least 72 simultaneous serial and 96 simultaneous ethernet circuits. BCA sites shall only be sized to support at least 36 simultaneous serial and 48 simultaneous ethernet circuits.

6.1.2.3 CT Support and Services

For the purpose of this PWS, CT services are defined as all the services and equipment required to uplink and downlink data to the end user terminal and connections to the contractor furnished terrestrial infrastructure. The contractor shall ensure the CT includes the following key features:

6.1.2.3.1 Within 120 calendar days after initial task order start date, the contractor shall install all CFE and be prepared to provide services for uplinking and downlinking at the end user terminal and contractor provided terrestrial infrastructure at the CT.

6.1.2.3.2 The Government will provide GFE to support up to seven CTs. The contractor shall be responsible for monitor and control of the GFE at the CTs.

6.1.2.3.3 CT services shall include the capabilities to transmit and receive multiple carriers through the uplink and downlink chains to access leased satellite resources. The contractor shall ensure the CTs are fully compatible with space segment provided by the space segment solution.

6.1.2.3.4 The contractor shall ensure each CT has a Power Management Plan that will prevent a single point of failure and provide continuous operations in the event of a main power failure. The contractor shall provide equipment racks sufficient in number and size for GFE at the CT. CT racks shall include power and ground to accommodate all CFE and GFE.

6.1.2.3.5 Installations at CTs. The contractor shall provide all signal and power cables for the GFE equipment installed at the CTs. Cables and connectors shall be constructed and installed in accordance with the equipment manufacturer’s specifications.

6.1.2.3.6 GFE Maintenance at CTs. The contractor shall perform quarterly inspections and cleaning of GFE ventilation filters and airways to ensure adequate equipment cooling.

6.1.2.3.7 GFE Troubleshooting and Repair at CTs. The contractor shall identify any faulty GFE and report such status to the Government. The contractor shall make minor repairs or replace equipment at the direction of the Government. Examples of such repairs would be, but not limited to, replacement of blown fuses, modules, or circuit cards. Repair parts and replacement equipment will be provided by Government. GFE that cannot be repaired on site or has been replaced shall be shipped to the Government-designated repair facility. The Government will assume all shipping charges.

6.1.2.3.8 The contractor shall provide a comprehensive system supporting both static and dynamic operations while maximizing use of available CSSC II resources. Static operations are defined as dedicated single channel per carrier (SCPC) links, whereas dynamic operations refers to shared managed networks.

• SCPC operations shall be supported in all regions.

• The contactor’s solution shall allow for the use of the COMTECH VIPERSAT Management System

(VMS) GFE operating at Layer 2 at the Governments discretion within 180-days of notification. The contractor shall be responsible for operations and maintenance of the COMTECH VMS.

6.1.2.3.9 When requested by the Government, the contractor shall provide the ability to make external connections from any CT to a Government provided connection. A Government provided connection is defined as one that is provisioned by the Government to connect an NDP to a CT and is used to transport CSSC II Internet Protocol Data.

This type of connection would only be implemented when a connection to an NDP that is not listed in Appendix II – NDPs is required. If necessary, the Government will provide any additional hardware as GFE as necessary to interface this type of connection to the contractor CT equipment as specified by the contractor.

6.1.2.3.10 When requested by the Government, the CTs shall provide unclassified public internet access connection services to end user terminals.

6.1.2.3.11 The contractor shall support unannounced security inspections and scheduled GFE inventories by Government personnel or their representatives.

6.1.2.3.12 The contractor shall provide a stratum 1 clock source to the CFE and GFE at each CT supporting the end-to-end CSSC II service. Stratum 1 source shall be redundant and compatible with both CFE and GFE. This shall include any serial to ethernet adaptation devices used to meet the EIA-530 serial connection requirements.

6.1.2.3.13 The contractor shall follow Cyber security requirements to ensure that all CTs meet the administrative, operational, and physical security requirements in accordance with Department of Defence (DoD) Instruction (DoDI) 8510.01 – Risk Management Framework (RMF) for DoD Information Technology (IT). The contractor shall include CT facilities that are located in a physically secure commercial facility with the required level of positive control of access and security, supported by system type of IS Major Application ISO National Institute of Standards and Technology, Special Publication 800-53rev4 with Confidentiality, Integrity Availability and Overall Impact of moderate, low, moderate and moderate.

6.1.2.3.14 VMS-Optional CLIN – If/when exercised by the Government, the contractor shall incorporate the COMTECH VMS GFE within the contractor’s architecture. The contractor shall be responsible for operation of the VMS Network.

6.1.2.4 Backhaul and NDP Connectivity

6.1.2.4.1 The contractor shall provide terrestrial connectivity to the NDPs no later than 120 calendar days after initial task order start date.

6.1.2.4.2 The terrestrial segment shall meet the performance requirements as set forth in Section 6.1.3– End-to-End Service Performance Requirements.

6.1.2.4.3 The terrestrial infrastructure shall support the data throughput requirements of the space segment, monitor and control (M&C) traffic, and any data management overhead as well as provide Advanced Encryption Standard (AES)-256 encryption across the backhaul. The terrestrial segment shall support delivery of user data to the NDP/MDP at Layer 2 of the Open System Interconnection (OSI) Model. The infrastructure shall be scalable to accommodate future surge. The infrastructure shall support IPv4 and IPv6 dual stack capabilities.

6.1.2.5 Installation and Maintenance

The contractor shall install and maintain all CFE and equipment interfaces to GFE in accordance with the below requirements.

6.1.2.5.1 Configuration Management. For all CFE located at the NDPs/MDPs, the contractor shall provide, within 14 calendar days after initial task order start date, configuration management documentation which includes the Integrated Logistics Support Plan. The contractor shall provide technical specifications for all proposed CFE. Upon Government acceptance of the network architecture, the contractor shall provide configuration management documentation in accordance with the Shore Installation Process Handbook (SIPH) Commander Space and Naval Warfare Systems Command (COMSPAWAR) M-4720.1.

6.1.2.5.2 Installation Design Plan (IDP) and As-Built Drawing Packages. The contractor shall prepare and deliver the IDP drawings in accordance with the latest SIPH Guidelines. These drawings shall be delivered within 21 calendar days after initial task order start date. These drawings shall be in AutoCAD 2016 format or above, shall document the terrestrial architecture, to include the CFE and GFE interfaces at all the CTs and NDPs, and shall be fully readable and editable. The IDP shall be submitted to the Government for submission to the Fleet Readiness Certification Board in order to obtain approval to proceed with the installation. Final As-Built Drawings shall incorporate all red-line changes and reflect the state of the completed installation at the CTs and NDPs. The final As-Built Drawings shall be completed and delivered within 45 calendar days after NDP/MDP installation completion.

6.1.2.5.3 NDP/MDP Installations. At the NDPs/MDPs, the contractor shall install all CFE and equipment interfaces to GFE in accordance with the SIPH. The contractor shall:

• Perform a pre-installation site survey and In/Out Brief.

• Install equipment and cables in accordance with the IDP.

• Label equipment and cables in accordance with the IDP.

• Remove all packing and waste materials from the premises.

• Activate and configure the CFE.

6.1.2.5.4 Equipment Refresh. At the Government’s direction, the contractor shall procure and employ newer technology or more efficient equipment. The contractor shall install, configure, operate, and maintain the equipment through the life of the contract. Equipment refreshes at the NDP/MDP shall comply with all requirements listed under Section 6.1.2.5.3, NDP/MDP Installations.

6.1.2.5.5 CFE Maintenance and Repair at the NDPs/MDPs. The contractor shall perform all maintenance and repair of CFE. Visitor Access Request for maintenance personnel shall be provided and kept current on file at NDPs/MDPs.

6.1.2.6 Network Scalability

6.1.2.6.1 Contractor shall have the ability to scale port densities at the CTs and NDPs/MDPs to accommodate future surge and provide technical refresh capabilities to accommodate new technologies introduced by the Government.

6.1.2.6.2 The Government may stand up additional NDPs in service regions not listed in Appendix II. The contractor shall support the additional network components and each NDP shall be sized to support at least 72 simultaneous serial and 96 simultaneous ethernet circuits unless otherwise stated by the Government at initial request.

6.1.2.7 DoD Teleport Connectivity

The contractor shall develop plans and be prepared to accommodate the user’s occasional use of DoD teleports. In the event a CSSC II satellite service will be up and down linked at a DoD teleport, the contractor shall work with the Government to determine changes or additions to the CSSC II satellite service. The contractor shall maintain a continuous monitor of all uplinks and downlinks using the CSSC II space segment. When notified that a DoD teleport will be accessing CSSC II satellite fleet, the contractor shall maintain a continuous monitor on the teleport’s transmit carrier to ensure that it is operating correctly, maintaining compliance, and not causing interference to other satellite users, and report any anomalies and/or outages to the CSSC II Technical Authority (TA). The contractor will not be responsible for the DoD teleport’s compliance with international and federal guidelines or for the required terrestrial connectivity from the DoD teleport to the NDPs.

6.1.3 Subtask 3 – End-to-End Performance Requirements.

The CSSC II architecture shall consist of end-to-end services, which are defined as one or more full period, full duplex or simplex circuits between an end user terminal and an NDP/MDP. Each end-to-end circuit for a single CSSC II user shall have the capability of operating as full duplex, simplex, symmetric, and/or asymmetric links as defined in the task order. Each Circuit shall consist of the space segment between the CT and the end user, including the uplink and downlink chain of the CT, the CFE network equipment located at the CT and NDP/MDP, and the terrestrial segment backhaul connectivity between the CT and the NDP/MDP. It is understood that it will be up to the Government to inform the contractor of issues with simplex circuits in a shore to ship direction as the Ao cannot be monitored by the contractor..

6.1.3.1 End-to-End Service Performance Requirements

The contractor shall maintain each end-to-end circuit with a threshold Ao of 97 percent or greater, as shown in Figure 5 – End-to-End Operational Availability, while meeting the following performance requirements:

6.1.3.1.1 Terrestrial Backhaul Segment: Minimum Backhaul Ao of 99.99 percent. The terrestrial backhaul segment includes the connections between the CFE network equipment at the CTs and NDPs/MDPs. See Figure 5.

6.1.3.1.2 Space Segment: Minimum Ao a link availability of 99.7 percent for frequency division multiple access (FDMA) satellite links and 99.5 percent for time division multiple access (TDMA) satellite links. The space segment includes the satellites and Earth Station terminals to include the uplink and downlink chain and all interfaces to GFE modems at the CTs. See Figure 5.

6.1.3.1.3 Terrestrial Segment Serial connection bit error rate (BER): Serial BER test must meet the following requirements within a 12-hour contiguous period as tested with a 223 -1 test pattern.

• Less than or equal to 1x10-8 error rate. (less than or equal to 1 bit error in 100,000,000 bits)

• Less than or equal to 2 pattern loss events (hits)

6.1.3.1.4 Layer 2 Ethernet Frame Loss Rate: Less than or equal to 1.5% Frame Loss Rate of the Throughput Rate as tested in accordance with RFC 2544 defined specifications and Ethernet frame sizes of 64, 128, 256, 512, 1024, 1280, and 1518 byte frames.

6.1.3.1.5 End-to-end latency: Less than or equal to 1.2 seconds.

6.1.3.1.6 Terrestrial packet loss: Between the CT and NDP/MDP less than or equal to 1 percent. Packet loss due to satellite beam transitions shall not be included in the terrestrial packet loss calculation.

6.1.3.1.7 Terrestrial jitter: Between the CT and NDP/MDP of less than or equal to 20 milliseconds.

Figure 5 – End-to-End Operational Availability

6.1.3.1.8 End-to-End Ao: The end-to-end Ao for each circuit shall be equal to or greater than 97 percent. The end-to-end performance Ao shall be averaged over a 30-day period, calculated daily for the previous 30 calendar days. The contractor shall use the following formula to calculate Ao:

End-to-End Ao = Uptime/(Uptime+Downtime)

• Uptime is defined as the amount of time the circuit is operational and meeting all requirements. This includes the full period of performance (POP) of the end-to-end service, whether or not it is being allocated or actively utilized.

• Downtime is defined as the amount of time the service is not operational, which includes services that do not meet the BER, frame loss rate, packet loss, jitter, and latency performance requirements in this section. This includes the full POP of the lease whether or not it is being allocated or actively utilized.

Upon activation of end-to-end services during the scheduled cutover period, any service delays or disruptions caused by the contractor to any segment of the end-to-end network will be considered downtime. After an outage event has occurred, the Government and contractor will both verify and agree to the downtime values reported and documented in trouble tickets, outage reports, and monthly reports.

Downtime values will not include time attributed to GFE failure or beam transition for mobile platforms.

Deliverables:

PWS

Task#

Deliverable Title Format Due Date Distribution/Cop ies

Frequency and Remarks

6.1.1.1, 6.1.1.2

Link Budget Analysis

MS Excel 72 hours after requested by the Government

Standard Distribution*

Frequency is event-driven

6.1.1.2 Satellite

Coverage Maps

Google Earth 72 hours after requested by the Government

Standard Distribution*

Frequency is event-driven

6.1.1.1 Satellite

Availability Report

Contractor- Determined Format

At Task Award proposal

Standard Distribution*

Frequency is event-driven

6.1.2.5.1 Configuration

Management Documentation

In Accordance With (IAW) Shore Installation Process Handbook

(SIPH)

Commander Space and Naval Warfare Systems Command

(COMSPAWAR

) M-4720.1.

Within 14 calendar days of initial task order start date

Standard Distribution*

Frequency is event-driven.

6.1.2.5.2 Installation

Design Plan

AutoCAD 2016 or above

Within 21 calendar days of initial task order award start date

Standard Distribution*

Required after award and for every change in configuration

6.1.2.5.2 Final As-Built

Drawings

AutoCAD 2016 or above

Within 45 calendar days after installation is complete.

Standard Distribution*

Required after award and for every change in configuration

*Standard Distribution: 1 copy of the transmittal letter without the deliverable to the Contracting Officer; 1 copy of the transmittal letter with the deliverable to the Primary COR and designated Navy POC, All deliverables will be encrypted in accordance with subparagragh 11.8.

6.2 Task 2 – Operational Management.

6.2.1 Subtask.1 – CSSC II Transition Support and Implementation

The contractor shall develop a plan for the implementation of the terrestrial standup and transition to new services for the end users in the initial IDIQ contract proposal. Within 7 calendar days after initial task order start date, the Government will provide a schedule based on the contractor’s proposed plan. This schedule will illustrate the sequence and start dates of events based on the contractor’s provided durations of events. The contractor shall demonstrate the ability to provide those services in accordance with the below paragraphs.

6.2.1.1 Transition Support Plan

The Government will provide the contractor with feedback on the draft Transition Support Plan included within their proposal within 7 days after contract award (ACA). The contractor shall update and present the final Transition Support Plan within 14 calendar days after initial task order start date at the Kick-Off Meeting, referenced in PWS 6.2.4.4.1, Post-Award Kick-Off Meeting. The plan shall detail the steps required to accomplish tasks listed in this section as well as PWS 6.1.2.4 – Backhaul and NDP Connectivity and PWS 6.1.2.3 – CT Support and Services, to include a detailed list of the CFE to be installed in each of the NDPs. The plan shall include stand-up of the terrestrial network and CT facilities to support the CSSC II solution, performance and acceptance testing, performance and acceptance reporting, cutover of end user terminals onto the CSSC II architecture, and dual illumination of the space segment. The plan shall demonstrate cutover of active CBSP circuits with no more than 30 minutes of downtime to the end users. The plan shall support transition to full operational capability on the new CSSC II system within 180 calendar days after initial task order start date.

6.2.1.2 System Design and Validation

The contractor shall provide IDP drawings that illustrate the overall CSSC II architecture. IDP drawings shall show all CFE and GFE that will be installed at the NDPs, CTs and other contractor facilities where GFE will be installed.

The contractor shall provide pre-installation test results as required in PWS 6.2.5.1 – Pre-Installation Testing for Government approval.

6.2.1.3 Final Acceptance Test

The contractor shall develop and deliver a System Operational Verification Test (SOVT) document within 21 calendar days after initial task order start date that will be used for the post-installation and transition testing of the end-to-end service. The document shall meet the requirements of the SOVT Preparation and Execution Guide (SPEG) Space and Naval Warfare Systems Command (SPAWAR) Instruction 3084.1. The SOVT, also referred to as the Final Acceptance Test, shall verify proper installation, operation of equipment, M&C functionality and performance of end-to-end connectivity. The successfully completed SOVT report shall be delivered within 180 calendar days after initial task order start date.

6.2.1.4 Constraints

Due to a limited number of GFE modems available at the time of contract award, the transition must take place in phases. The contractor shall plan and coordinate with CSSC II TA to ensure that existing services are not disrupted during the phased migration of GFE equipment from old to new CSSC II architecture. Existing CFE CBSP equipment located at the NDPs/MDPs shall not be disturbed during this transition as this equipment will continue to be used to support active circuits until the transition is complete. The Government will provide the GFE necessary to complete the CT post installation testing prior to transition. Fifteen (15) MD-1366/U and eighty (80) SLM- 5650A/B GFE modems will be provided to the contractor to start the initial transition.

6.2.2 Subtask 2 – Operational Support.

The contractor shall establish and maintain all end-to-end services to ensure operational integrity of the entire system. The contractor shall support the following operational functions:

6.2.2.1 Global Schedule of Events (GSOE)

The GSOE provides the service type, date, time, and users that are authorized to access leased services. The contractor shall utilize the GSOE to operate and manage all scheduled services. The GSOE will be provided daily from the Naval Network Warfare Command (NNWC) via email. Changes to the GSOE may be made by the Joint Fleet Telecommunications Operations Center (JFTOC) or MSC and sent via email or phone (followed by official email notification).

6.2.2.1.1 Mission Activations/Deactivations. Unless otherwise directed by the NNWC, JFTOC or MSC, the contractor shall activate/deactivate circuits in accordance with the current GSOE. The contractor shall coordinate the activation of the end-to-end circuit, including conducting pre-activation check in accordance with the User’s Guide.

6.2.2.1.2 Mission Changes. While a circuit is operational, the NNWC, JFTOC or MSC will request in writing any changes to the end-to-end circuit configuration to support the end user’s needs. The contractor shall coordinate with the JFTOC or MSC to conduct an availability analysis of the network assets. Upon the JFTOC or MSC authorization of the mission change, a revised GSOE will be generated to reflect the changes.

6.2.2.2 Service Interruptions

Corrective maintenance is action performed as a result of failure in order to return or restore equipment to acceptable performance levels. Planned maintenance is action intended to prevent failures. Scheduled service interruptions will be allowed for the purpose of performing planned maintenance. The contractor shall provide notification to the CSSC II TA and NNWC of a planned maintenance event at least 30 calendar days in advance and provide primary and secondary dates and times of the maintenance. The contractor shall not proceed with the planned maintenance outage prior to Government approval. Should the contractor fail to provide the proper notification in the prescribed time frame and decides to proceed with the maintenance, the Navy will treat the maintenance as corrective maintenance and any service interruption incurred will be considered an outage. The contractor shall include in the notification the purpose, date, time, and duration for the planned maintenance. The contractor shall provide notification to the CSSC II TA and NNWC of a corrective maintenance event as soon as the event is planned. The contractor shall report the start and completion of the corrective and preventative maintenance. Any outages occurring outside the authorized scheduled service interruption timeframe shall be considered downtime as stated in Section 6.1.3.1.9.

6.2.2.3 User’s Guide

Within 30 calendar days after initial task order start date, the contractor shall develop and deliver a draft User’s Guide for CSSC II operations to ensure consistency of operations across the CSSC II architecture. The contractor shall support a working group session with the Government to finalize the User’s Guide. The finalized User’s Guide shall be required for delivery no later than 90 calendar days after initial task order start date. Once finalized the User’s Guide will be incorporated in Section J of the contract.

6.2.3 Subtask 3 – M&C and Web Tool.

6.2.3.1 M&C System

The contractor shall have continuous, uninterrupted, near real time M&C of the CSSC II end-to-end solution.

6.2.3.2 Web Tool

The contractor shall provide a web based monitoring tool. The Web Tool is a contractor provided web-based graphical user interface that provides a means for continuous, uninterrupted monitoring and display of mission and equipment status data of the contractor’s CSSC II end-to-end solution for the life of the contract. The Web Tool shall reside on contractor provided and managed servers. The contractor shall manage user access to the Web Tool for the Government and shall provide access only to users approved by the designated Government Point of Contact (POC). The Government POC will be provided upon contract award. The Web Tool is owned and maintained by the contractor and does not become Government property at the close of the contract. In the event of a Web Tool outage, the contractor shall provide all required reporting via email to designated Government contacts until the Web Tool is restored.

6.2.3.2.1 Web Tool Features. The Web Tool shall include, but is not limited to, the following features:

• Automatically displays the current end-to-end status of all CSSC II missions.

• Automatically displays the current status of all CFE and GFE being used in support of CSSC II missions.

• Allows for manual refresh of the displayed data.

• Accommodates a minimum of 200 simultaneously logged on users.

• Contains an historical database of monitored data collected and stored over the life of the contract as described in Section 6.2.3.2.5, Web Tool Historical Database.

• Allows the user to view the status and performance of all segments, as illustrated in Figure 5 – End-to-End

Operational Availability.

• Allows for the posting and downloading of files for the purpose of disseminating information pertinent to

CSSC II users. Information includes but is not limited to all deliverable reports, operating procedures, usage reports, and satellite footprint files in a format that will allow for display with Google Earth Software, transmission plans and frequency matrices.

• Includes a trouble reporting system that shall automatically generate an email ticket that will be forwarded to a Government designated distribution list. The trouble reporting system shall also store all tickets for the life of the contract. All tickets, closed/stored shall be viewable to all Web Tool users.

• Provides the user with the ability to search and view trouble tickets by mission and ticket number.

• Allows the user to print and export Web Tool screen shots, generated data queries, and reports as image files, Microsoft Excel compatible files, and text files as requested by the Government.

• Accessible through the public internet network with security requirements detailed in Section 6.2.3.2.6, Web Tool Security.

6.2.3.2.2 Web Tool Dashboard. The Web Tool shall provide a single page dashboard display that provides a summarized graphical representation of the end-to-end status of each CSSC II mission. The following mission summary information shall be provided:

• Mission number (mission numbers will be provided by the Government).

• End user…