SBS0022_PWS_Final_Draft.pdf

SBS0022 PWS

Page 1 of 43 Pages

COMMERCIAL SATELLITE COMMUNICATIONS (COMSATCOM)

PERFORMANCE WORK STATEMENT (PWS)

Satellite Business Solutions (SBS)

SBS0022

As of April 18, 2019

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 DISA COR.

DODAAC:

Address:

Phone Number:

2. Task Order Title.

Commercial Broadband Satellite Program (CBSP) Satellite Services Contract (CSSC II) 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

Page 2 of 43 Pages

(COMSATCOM) services through the existing CBSP Satellite Services (CSSC II) Contract. CBSP delivers connectivity between Navy ships (and other terminals) and Navy Designated Points of Presence (NDP). 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 procures, installs, and maintains 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 maritime, airborne, and ground platforms, as well as commercial teleport (CT) ser-vices, backhaul connectivity, monitoring and control, and operations. The purpose of “and/or” with regard to the identified bands (C-band, X-band, Ku-band and/or Ka-band) refers to a 'combination of all of the identified/listed bands’. However, as this is an 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 the 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. Figure 1 – CSSC II Notional Architecture provides a notional architecture of the

CSSC II.

Page 3 of 43 Pages

Figure 1 – CSSC II Notional Architecture

5. Scope.

The CSSC II shall provide access to an end-to-end service capable of supporting approximately 300 simultaneous full period, full duplex connections between a NDP and the end user terminal through the means of space and terres-trial connectivity. Active CSSC II circuits are defined as end-to-end circuits that are currently terminating an end user to a NDP. Reserve CSSC II circuits are defined as end-to-end circuits that are not currently terminating an end user to a NDP but are available to support missions as directed by the Government. Circuits shall have the capabil-ity of operating as full duplex, symmetric, and asymmetric. Figure 2 – Notional Architecture End-to-End Service Responsibility 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 CFE. While the end user termi-nals are beyond the scope of this PWS, the contractor must thoroughly understand each terminal’s design, capabili-ties, 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.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

Page 4 of 43 Pages 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-preemptable, 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 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.

6.1.1.2 Satellite Coverage

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 sufficient link margins. Solutions must meet the service coverage requirements as defined by the individual task orders throughout the PoP at all times. When requested at the task order level, the contractor shall provide EIRP and 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. 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 – User Terminal Segment Characteristics, at a point within the coverage area with the weakest satellite uplink G/T. The Government understands that space segment resources are limited in some regions.

6.1.1.2.1 Contiguous Bandwidth. The Navy considers contiguous to be multiple transponders on a single satellite to meet the particular network requirement. The contractor shall provide blocks of bandwidth that are no less than 20 megahertz (MHz) in size. Multiple satellites capable of providing coverage of the target area are acceptable; how-ever, 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, it shall be done in accordance with Table 1 – Beam Shaping Response Times, and in support of locations as directed by the Govern-ment. Response is the time allotted to execute the shaping action and begins upon initial notification. When these solutions are employed, the contractor shall provide a Beam Shaping Plan with a detailed description of the beam shaping capabilities and processes for each frequency band.

Action/Response Type Response Times (hours) Routine (new beams) 48 Emergent (new beams) 24 Emergent (pre-planned beams) 2

Table 1 – Beam Shaping Response Times

6.1.1.2.3 Beam Steering. When solutions provide the Government rights to steer satellite beams, it shall be done in accordance with Table 2 – Steerable Beam Response Times, and in support of locations as directed by the Govern-ment. Routine and Emergent response is the time allotted to execute the steering action for beams directly con-trolled by the satellite operator and begins upon initial notification to the contractor. Government controlled refers to beams directly controlled by the Government user/operator via secure connection to the satellite control center without contractor or satellite operator involvement. When these solutions are employed, the contractor shall pro-vide a Beam Steering Plan with a detailed description of the beam steering capabilities and processes for each fre-quency band.

Page 5 of 43 Pages

Action/Response Type Response Times (hours) Routine (new beams) 24 Emergent (new beams) 8 Emergent (pre-planned beams) 2 Government (User) Controlled 0.25

Table 2 – Steerable Beam Response Times

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 such, the purpose of “and/or” with regard to the identified bands (C-band, X-band, Ku-band and/or Ka-band) refers to a 'combination of all of the identified/listed bands’. However, as this is an IDIQ contract, the specific band, operating region to be covered, and the amount of bandwidth to be provided during the period of performance will be delineated in the individual task orders.

• Region A. Region A shall provide C, Ka, and Ku-band satellite coverage over the North American Operat-ing Region (as defined in Table 3 - Region A) with emphasis over the continental U.S. and its littoral wa-ters, and waters surrounding the Caribbean Islands; 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 Ku and Ka-band satellite coverage over the Continental African Op-erating Region (as defined in Table 4- Region AF) with emphasis over the littoral waters surrounding Af-rica; 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 AG. Region AG shall provide Ku and Ka-band satellite coverage over the Afghanistan Operating

Region (as defined in Table 5 - Region AG) as depicted in Figure 3 – CSSC II Operational Regions Cover-age Graphic.

40 33 58 42 77 38 67 19 40 33

Table 5 – Region AG

• Region E. Region E shall provide Ku and Ka-band satellite coverage over the European Operating Region (as defined in Table 6 - Region E) with emphasis over the Mediterranean Ocean and littoral waters sur-rounding Europe; as depicted in Figure 3 – CSSC II Operational Regions Coverage Graphic.

Page 6 of 43 Pages

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

Table 6 – Region E

• Region G. Region G shall provide Ku and Ka-band satellite coverage over the Saudi Arabian Operating Region (as defined in Table 7 - Region G) with emphasis over the Red Sea, Gulf of Aden, the Gulf of Oman, the Persian Gulf and the littoral waters off the coast of Oman, Yemen, and the Horn of Africa; as depicted in Figure 3 – CSSC II Operational Regions Coverage Graphic.

28 30 36 38 70 25 50 -3 28 30

Table 7 – Region G

• Region H. Region H shall provide Ku and Ka-band satellite coverage over the Hawaiian Islands Operating Region (as defined in Table 8 – Region H) with emphasis over the air and sea transit corridors between the west coast of the U.S. and the waters around the Hawaiian Islands; as depicted in Figure 3 – CSSC II Oper-ational Regions Coverage Graphic.

178 50 -125 50 -100 25 -120 10 178 10 178 50

Table 8 – Region H

• Region NA. Region NA shall provide for 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 Re-gions Coverage Graphic.

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

Table 9 – Region NA

• Region SA. Region SA shall provide Ku and Ka-band satellite coverage over the South American Operat-ing Region (as defined in Table 10 – Region SA) with emphasis over littoral waters surrounding South and Central America; as depicted in Figure 3 – CSSC II Operational Regions Coverage Graphic.

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

-79 -24 -88 5 Table 10 – Region SA

Page 7 of 43 Pages

• Region WP. Region WP shall provide Ku and Ka-band satellite coverage over the Western Pacific Operat-ing Region (as defined in Table 11 – Region WP) with emphasis over waters surrounding Japan, Guam, Philippines, New Zealand, and Australia; as depicted in Figure 3 – CSSC II Operational Regions Coverage Graphic.

85 12 140 54 -155 54 -139 20 -155 -50 97 -50

85 12 Table 11 – Region WP

• Region S1. Region S1 shall provide C, Ka, and X-band satellite coverage over the Atlantic Ocean Operat-ing Region (as defined in Table 12 – Region S1) as depicted in Figure 4 – CSSC II Blue Water Operational Regions Coverage Graphic with emphasis over the blue water areas bounded by 5 degrees North - 50 de-grees North Lat and 105 degrees West - 15 degrees East Long.

-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 Regions Coverage Graphic with emphasis over the blue water areas bounded by 55 degrees North - 45 de-grees South Lat and 15 degrees West - 80 degrees East Long.

-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 Op-erational Regions Coverage Graphic with emphasis over the blue water areas bounded by 50 degrees North

- 50 degrees South Lat and 65 degrees East - 150 degrees West Long.

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

Table 14 – Region S3

• Region S4. Region S3 hall provide C, Ka, and X-band satellite coverage over the Eastern Pacific Ocean Operating Region (as defined in Table 15 – Region S2) as depicted in Figure 4 – CSSC II Blue Water Op-erational Regions Coverage Graphic with emphasis over the blue water areas bounded by 55 degrees North

- 45 degrees South Lat and 165 degrees West - 90 degrees West Long.

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

Table 15 – Region S4

Page 8 of 43 Pages

Figure 3 – CSSC II Operational Regions Coverage Graphic

Figure 4 – CSSC II Blue Water Operational Regions Coverage Graphic

Page 9 of 43 Pages

6.1.1.3 Required Space Segment Quality

Technical parameters to be used for link budgets are contained in PWS Appendix A, Technical Specification.

When terminal locations are provided in PWS Appendix A, Technical Specification, the contractor shall ensure that links close in those locations; the contractor shall ensure links close in the worst-case scenario terminal location for terminal locations that are not indicated in the Technical Specification. 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 [ter-minal specifications, effective isotropic radiated power (EIRP), system gain to noise temperature ratio (G/T), data rate, modulation and coding, etc.]. 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, modula-tion, 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. 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, re-gions, and operational capacities as defined in Appendix I– User Terminal Segment Characteristics. 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.

6.1.1.3.1 Satellite Availability. The contractor shall meet an Ao for satellite bandwidth of 99.99 percent, calculated daily and averaged for the previous 30 calendar days. 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.

6.1.2 Subtask 1.2 – Terrestrial and Commercial Teleports.

6.1.2.1 General Characteristics

The contractor shall deliver terrestrial segment capabilities that are compatible with, of sufficient quantity, and in appropriate geographical locations 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 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. Contractor Furnished Equipment (CFE) installed at the NDPs shall be sized to support the number and type of connections described below:

6.1.2.2.1 The CFE installed at each NDP shall be sized to support at least 72 simultaneous serial and 96 simultaneous ethernet circuits.

6.1.2.3 CT Support and Services

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

Page 10 of 43 Pages

6.1.2.3.3 The Government will provide GFE to support up to seven CTs.

6.1.2.3.4 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.5 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 sufficient equipment racks for GFE at the CT. CT racks shall include power to accommodate all CT equipment and

GFE.

6.1.2.3.6 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 COMTECH VIPERSAT Management System (VMS)

GFE operating at Layer 2 at the Governments discretion within 180-days.

6.1.2.3.7 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 a 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 a NDP that is not listed in Appendix III – NDPs is required. If necessary, the Government will provide any additional hardware necessary to interface this type of connection to the contractor CT equipment as specified by the contractor.

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

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

6.1.2.3.10 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.11 The contractor shall follow IA/Cyber security requirements to ensure that all CTs meet the administrative, operational, and physical security requirements in accordance with 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 to Mission Assurance Category (MAC) Level II.

6.1.2.3.12 VMS-Option CLIN - When exercised by the Government, the contractor shall incorporate COMTECH VMS GFE within the contactors architecture. 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. The contractor shall ensure the final design includes the following key features:

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.

Page 11 of 43 Pages

6.1.2.4.3 The terrestrial infrastructure shall support the data throughput requirements of the space segment, 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 at Layer 2 of the OSI Model. The infrastructure shall be scalable to accommodate future surge.

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, 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 and 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 installation completion.

6.1.2.5.3 NDP Installations. At the NDPs, 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 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 shall comply with all requirements listed under Section 6.1.2.5.3, NDP Installations.

6.1.2.5.5 CFE Maintenance and Repair at the NDPs. 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.

6.1.2.5.6 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.5.7 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.5.8 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

Page 12 of 43 Pages site or has been replaced shall be shipped to the Government-designated repair facility. The Government will assume all shipping charges.

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 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 III. Each NDP shall be sized to support at least 72 simultaneous serial and 96 simultaneous ethernet circuits unless otherwise amended 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 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 1.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 circuits between an end user terminal and a NDP. Each end-to-end circuit for a single CSSC II user shall have the capability of operating as full duplex, 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, and the terrestrial segment backhaul connectivity between the CT and the NDP.

6.1.3.1 End-to-End Service Performance Requirements

The contractor shall maintain each end-to-end circuit with a threshold operational availability (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. 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 Error Rate (FER): Less than or equal to 1x10-10 as tested in accordance with RFC 2544 defined specifications and Ethernet frame sizes of 64,128,256, 512, 1024, 1280, and 1518 byte frames.

Page 13 of 43 Pages

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 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 of less than or equal to 20 milliseconds.

Figure 5 – End-to-End Operational Availability

6.1.3.1.9 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, pattern loss, 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

Page 14 of 43 Pages values reported and documented in trouble tickets, outage reports, and monthly reports. Downtime values will not include time attributed to Government Furnished Equipment (GFE) failure or beam transition for mobile platforms.

PWS

Task#

Deliverable Ti-tle

Format Due Date Distribu-tion/Copies

Frequency and Remarks

6.1.1.1 Link Budget

Analysis

MS Excel 72 hours after requested by the Government

Standard Dis-tribution*

Frequency is event-driven

6.1.1.2 Satellite Cover-

age Maps

Google Earth 72 hours after requested by the Government

Standard Dis-tribution*

Frequency is event-driven

6.1.1.2.2 Beam Shaping

Plan

Contractor-De-termined Format

5 days after contract award; updated upon change or at Government request

Standard Dis-tribution*

Frequency is event-driven

6.1.1.2.2 Beam Steering

Plan

Contractor-De-termined Format

5 days after contract award; updated upon change or at Government request

Standard Dis-tribution*

Frequency is event-driven

6.1.1.3 Satellite Avail-

ability Report

Contractor-De-termined Format

At Task Award proposal Standard Dis-tribution*

Frequency is event-driven

6.1.2.5.1 Configuration

Management Documentation

In Accordance With (IAW) Shore Installation Process Hand-book (SIPH) Commander Space and Naval Warfare Systems Command

(COMSPAWAR

) M-4720.1.

Within 14 calendar days of initial task order start date

Standard Dis-tribution*

Frequency is event-driven.

6.1.2.5.2 Installation De-

sign Plan

AutoCAD 2016 or above

Within 21 calendar days of initial task order award start date

Standard Dis-tribution*

Required af-ter award and for every change in configuration

6.1.2.5.2 Final As-Built

Drawings

AutoCAD 2016 or above

Within 45 calendar days of initial task order award start date

Standard Dis-tribution*

Required af-ter 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 RSSC-West (rsscwest.commer-cial@us.af.mil), encrypted in accordance with subparagragh 11.2.

6.2 Task 2 – Operational Management.

6.2.1 Subtask 2.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. Within 7 days after initial task order start date, the Government will provide a schedule based on mailto:rsscwest.commercial@us.af.mil

Page 15 of 43 Pages 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 contractor shall develop and present a 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, as well as the locations at the 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 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 thirty (30) SLM-5650B 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) and sent via email or phone (followed by official email notification).

Page 16 of 43 Pages

6.2.2.1.1 Mission Activations/Deactivations. Unless otherwise directed by the NNWC or JFTOC, 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 or JFTOC 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 to conduct an availability analysis of the network assets. Upon the JFTOC 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 2.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 located at a contractor controlled facility. 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 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:

Page 17 of 43 Pages

• 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 satellite terminal type and terminal identifier.

• Operating region and CT.

• Mission type (SCPC, time division multiple access (TDMA), etc.) and activation/deactivation date and time.

• Assigned satellite, assigned transponder slot, and assigned transmit and receive data rate.

• Assigned CT modem identifier and type.

• Modem signal-to-noise level shown as energy per bit to noise power spectral density ratio (Eb/No).

• Status of the end-to-end data path for each mission, to include status indicators for modem synchronization and data port type and activity along the path so that any interruption in end-to-end service can be readily observed and localized. Minor summary faults that do not impact overall end-to-end service shall not be included.

• Status of all terrestrial connections between all CT and NDP nodes. If multiple terrestrial connections are available between the CT and NDP then each terrestrial line shall be represented separately. Terrestrial connections that impact end-to-end service shall be linked to each individual circuit.

• The contractor shall provide a visual alert to the network operator of a disruption, failure or degradation anywhere in the network that impacts an active mission.

• GSOE. The dashboard shall display mission scheduling information as provided by the current GSOE, as described in Section 6.2.3.2.4, Web Tool GSOE. The dashboard shall list missions that are scheduled to be activated within 24 hours and missions that have been deactivated in the preceding 24 hours.

• Open Trouble Ticket Report. The dashboard shall include a display of all open trouble tickets. This report shall include ticket number, date of incident, type of incident, and a brief description of the issue.

• Monthly Trouble Ticket Status Summary. The dashboard shall display a list by ticket type of the number of tickets that remain outstanding or have been closed over the last 30 calendar days.

• Scheduled Maintenance. The dashboard shall display a summary of all ongoing and scheduled maintenance events.

6.2.3.2.3 Web Tool M&C Status and Performance Information. The contractor shall continuously monitor and display on the Web Tool the following status and performance information for all end-to-end CSSC II services:

Page 18 of 43 Pages

• Terrestrial Performance. The following information shall be provided:

o Internet Service Provider status: Connections that have been provisioned in accordance with Section

6.1.2.3.8 shall be reported and refreshed at least once every 5 minutes.

o External Government Terrestrial Connection status: Connections that have been provisioned in accordance with Section 6.1.2.3.7 shall be reported and refreshed at least once every 5 minutes.

o Status and performance of all CT to NDP backhaul connections, to include the performance metrics described in Sections 6.1.3.1.5, 6.1.3.1.6, and 6.1.3.1.7. BER, packet loss, and jitter measurements shall be refreshed at least once every 5 minutes. End-to-end latency shall be measured and displayed at least once every 24 hours.

o Status of all the data ports at each CT and NDP, to indicate whether the data port is active and passing data or administratively down but available for use. An indication shall also be provided to show when a data port is logged out of service or undergoing testing. Port status shall be refreshed at least once every 5 minutes.

o Total number of modems available for use at each CT. This report shall include modem designator and serial number. Modem availability status shall be updated daily.

o The status of any CFE or GFE that is logged out of service shall be displayed on the Web Tool and provided in the Daily Service Report. The information shall include equipment description, location, operational impact, and estimated time to repair.

o Access to spectrum analysis of all leased bandwidth on a near-real time basis.

• Modem and radio frequency (RF) link status and performance information shall be refreshed at least once every 5 minutes. The following information shall be provided:

o Modem synchronization status.

o Modem signal-to noise level, shown as Eb/No. A running data log for the minimum, maximum, and average levels recorded over the length of each mission shall be provided.

o Modem transmit power level.

o Modem embedded Transmission Security (TRANSEC) AES-256 synchronization status (when embedded modem encryption is enabled).

o Modem receive buffer fill level status.

o Modem carrier out of lock status.

o Modem transmit and receive alarm status.

o Modem transmit and receive fault status.

• Interference Information. The contractor shall provide as part of the Daily Service Report the following information:

o Date/time stamp when an interference event occurs.

o Date/time stamp when circuit returned to service.

o Time stamped spectrum analyzer plots.

o Summary of the cause of interference and the actions taken to resolve detected interference and to prevent future interference issues from occurring.

• Utilization Information…