HC101314R0004.doc

Section A - Solicitation/Contract Form

EXECUTIVE SUMMARY

Section A - Solicitation/Contract Form

EXECUTIVE SUMMARY

The purpose for the publication of this Commercial Broadband Satellite Program (CBSP) Satellite Service Contract (CSSC) Draft Request for Proposal (RFP) is to provide potential offerors and other interested parties in the commercial industry sector an opportunity to view the Government’s current intent to obtain the CSSC services in support of the United States Navy. Comments from commercial industry are solicited on the comprehensiveness and practicality of contract execution based on the contents of this CSSC Draft RFP.

At this point, the Government is not looking for, nor does it wish to receive, any type of proposal in response to the CSSC Draft RFP. However, comments to this Draft RFP are encouraged and welcomed. (Additional information is provided below.) Any proposal information received will be returned without review.

Potential offerors interested in the CSSC Draft RFP are reminded that it is to be considered a living document which will be changed and updated as the Government refines its requirements and data. It is suggested that all interested parties check the FedBizOpps website, www.fbo.gov, for posted changes to this CSSC Draft RFP. Vendors can add opportunities to a “watch list” (“favorites” list) and receive email updates anytime the CSSC Draft RFP opportunity is updated. (Refer to the Vendor’s Guide located on the FedBizOpps website for information on establishing a “watch list”).

The documentation contained in the CSSC Draft RFP may not contain sufficient information upon which to base firm cost and pricing estimates. The Government is in the final stages of refining the documents and will publish final documentation as it becomes available. Interested offerors need to be aware that while the Government will publish the most current and accurate data available at the time of publishing, data elements are subject to change throughout the posting life of the CSSC Draft RFP on the FedBizOpps website. It is the Government’s intent to publish as much data as available, as quickly as possible, so offerors can begin preparing their proposals. Everyone is again reminded at this point that the CSSC Draft RFP, being a draft (living) document, is subject to continual and constant change as requirements and data are refined. The final set of hard data facts will be posted on FedBizOpps as a Final RFP.

Comments on the CSSC Draft RFP should be emailed to diane.schooley.civ@mail.mil and jennifer.d.forhy.civ@mail.mil at any time, but no later than 9:00 AM, Central Time, July 1, 2014. Comments received after the deadline may not be addressed by the Government.

PRESOLICITATION INDUSTRY DAY

A 1-day Presolicitation Industry Day for the CSSC requirement is scheduled for June 25, 2014 at the:

Booz Allen Hamilton Building

901 15th St NW

Suite 400

Washington, DC 20005

The CSSC Presolicitation Industry Day will commence at 9:00 AM Eastern, and is expected to adjourn no later than 1500 Eastern. This Presolicitation Industry Day will provide an opportunity for interested offerors to learn more about the CSSC requirement and ask any additional questions they may have.

Prospective offerors that are interested in attending the Presolicitation Industry Day shall pre-register no later than 9:00 AM, Central Time, on June 20, 2014, by submitting an email to diane.schooley.civ@mail.mil and jennifer.d.forhy.civ@mail.mil. The email shall include the following information:

Subject Line: CSSC – Presolicitation Industry Day – June 25, 2014

The body of the email shall include:

Name and address of the company

DUNS/Cage Number

Point of contact information (to include Name, Telephone Number, and email address)

Name of attendees (no more than 2 representatives per prime)

NOTE: Substitutions must be arranged prior to 9:00 AM, Central Time, June 23, 2014. Representatives not on the Government’s list may not be admitted into the Presolicitation Industry Day.

As prescribed in the Federal Acquisition Regulation Clause 52.215-3, the Government will not award a contract on the basis of this CSSC Draft RFP or to otherwise pay for information solicited. This CSSC Draft RFP is issued for the purpose of developing a viable solicitation that will best communicate the Government’s requirements to industry. Response to this CSSC Draft RFP is strictly voluntary and will not affect any corporation’s status as a prospective offeror. It is contemplated that the NAICS Code 517410 (Satellite Communications) will be used for determining size and status for the CSSC requirements.

The Government will not reimburse companies responding to this CSSC Draft RFP nor does it express any guarantees concerning this proposed action.

DISA thanks all interested offerors for their attention and participation in this acquisition process.

Section B - Supplies or Services and Prices

CSSC

FFP

Base Period

FOB: Destination

PURCHASE REQUEST NUMBER: CSSC

MAX

NET AMT

FFP

Option Period 01

MAX

FFP

Option Period 02

MAX

FFP

Option Period 03

MAX

FFP

Option Period 04

MAX

Section C - Descriptions and Specifications

PERFORMANCE WORK STATEMENT

COMMERCIAL SATELLITE COMMUNICATIONS (COMSATCOM)

PERFORMANCE WORK STATEMENT (PWS)

FOR

COMMERCIAL BROADBAND SATELLITE PROGRAM (CBSP)

SATELLITE SERVICES CONTRACT (CSSC)

Prepared by

PEO C4I PMW/A 170

TABLE OF CONTENTS

51. COR POC Information.

52. Contract Title.

53. Background.

64. Objectives.

65. Scope.

76. Performance Requirements.

76.1 Task 1 – End-to-End Performance Requirements.

86.1.1 Subtask 1 – End-to-End Service Performance Requirements.

96.1.2 Subtask 2 – Outage Credits.

96.1.3 Subtask 3 – Credit Exceptions.

106.1.4 Subtask 4 – As-Built Drawing Packages.

106.2 Task 2 – Space Segment Technical Performance and Requirements.

106.2.1 Subtask 1 – Satellite Capacity.

116.2.2 Subtask 2 – Required Space Segment Quality.

116.2.3 Subtask 3 – Frequency Ranges.

126.2.4 Subtask 4 – Polarization.

126.2.5 Subtask 5 – Satellite Link Availability.

136.2.6 Subtask 6 – Assured Access.

136.2.7 Subtask 7 – Satellite Hop.

136.2.8 Subtask 8 – Satellite Coverage.

176.3 Task 3 – Terrestrial Services Technical Performance and Requirements.

176.3.1 Subtask 1 – General Characteristics.

176.3.2 Subtask 2 – Network Sizing.

186.3.3 Subtask 3 – Commercial Teleport (CT) Support and Services.

196.3.4 Subtask 4 – DoD Teleport Connectivity.

196.3.5 Subtask 5 – Backhaul and NDP Connectivity.

206.3.6 Subtask 6 – Installation and Maintenance.

216.4 Task 4 – CSSC Transition Support and Implementation.

216.4.1 Transition Plan.

216.4.2 Subtask 1 – Transition Support Plan.

216.4.3 Subtask 2 – System Design and Validation.

226.4.4 Subtask 3 – Final Acceptance Test.

226.4.5 Subtask 4 – Constraints.

226.5 Task 5 – Operational Support to meet CSSC End-to-End Services.

226.5.1 Subtask 1 – Global Schedule of Events (GSOE).

236.5.2 Subtask 2 – Service Interruptions.

236.5.3 Subtask 3 – Standard Operating Procedures.

236.5.4 Subtask 4 – Pre-activation Procedures.

246.6 Task 6 – CSSC Monitoring and Control (M&C) and Web Based Monitoring Tool (Web Tool)

246.6.1 Subtask 1 –M&C System.

246.6.2 Subtask 2 –Web Tool.

306.6.3 Subtask 3 – Navy Cyber Situational Awareness (NCSA) Outbound Interface.

326.7 Task 7 – Management Controls for CSSC Program

326.7.1 Subtask 1 – Project Management

326.7.2 Subtask 2 – Communication.

336.7.3 Subtask 3 – Reporting Requirements.

356.7.4 Subtask 4 – Meetings and Reviews.

366.7.5 Subtask 5 – Meeting and Review Standard Deliverables.

376.8 Task 8 – Testing.

376.8.1 Subtask 1 – Pre-Installation Testing.

376.8.2 Subtask 2 – Post-Installation Testing.

376.8.3 Subtask 3 – Escalation Procedures.

376.9 Task 9 – Frequency Clearance (FC) and Approvals.

376.9.1 Subtask 1 – FC and Host Nation Agreement (HNA).

386.9.2 Subtask 2 – Prior Coordination Notifications (PCN).

386.10 Task 10 - Electromagnetic Interference (EMI)/Radio Frequency Interference (RFI) Identification, Characterization, and Geo-Location.

396.11 Task 11 – Fault Management.

396.11.1 Subtask 1 – Fault Reporting.

396.11.2 Subtask 2 – Service Interruption and Restoration.

396.12 Task 12 – Support for CSSC Security and IA Requirements.

406.12.1 Subtask 1 – Minimum Security Controls.

406.12.2 Subtask 2 – Tracking, Telemetry, and Control (TT&C) Cryptography.

416.12.3 Subtask 3 – EMI/RFI Capability.

416.12.4 Subtask 4 – Personnel/Operations/Communications Security.

426.12.5 Subtask 5 –DIACAP.

436.13 Task 13 – Bandwidth Planning.

436.13.1 Subtask 1 – TP.

456.13.2 Subtask 2 – Frequency Matrix.

456.14 Task 14 – Operational Support Requirements.

456.15 Task 15 – Semi-Annual Sun Transit Reporting.

457. Performance Standards.

498. Incentives.

499. Place of Performance.

5010. POP.

5011. Identification of Possible Future Growth

5012. Delivery Schedule.

5013. Security.

5114. GFE/ GFI.

5315. Other Pertinent Information or Special Considerations.

5315.1 Identification of Potential Organizational Conflicts of Interest (OCI).

5315.2 Identification of Non-Disclosure Requirements.

5316. List of Acronyms and Abbreviations:

APPENDICES

57Appendix I – CSSC User Terminal Segment Characteristics

58Appendix II – CSSC Bandwidth Estimates

59Appendix III – NDPs

60Appendix IV – CONUS C-Band PCN Parameters

LIST OF FIGURES

6Figure 1 – CSSC Notional Architecture

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

8Figure 3 – End-to-End Operational Availability

16Figure 4 – CSSC Operational Regions Coverage Graphic

17Figure 5 – CSSC Blue Water Operational Regions Coverage Graphic

31Figure 6 – M&C Interface to NCSA

LIST OF TABLES

12Table 1 – Frequency Ranges

14Table 2 – Beam Shaping Response Times

14Table 3 – Steerable Beam Response Times

57Table 4 – CSSC User Terminal Segment Characteristics

58Table 5 - Bandwidth Estimates

Contract Number:

Task Order Number:

16. COR POC Information.

a. Primary COR.

Organization:

DoD Activity Address Code (DoDAAC):

Address:

Phone Number:

Fax Number:

E-Mail Address:

b. Alternate COR.

Organization:

DoDAAC:

Address:

Phone Number:

Fax Number:

E-Mail Address:

17. Contract Title.

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

18. Background.

The United States 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 End-to-End Lease Services Contract. CBSP delivers connectivity from Navy ships as well as other terminals to Navy Designated Points of Presence (NDP)s. CBSP provides 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 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.

19. Objectives.

In support of the U.S. Navy’s COMSATCOM requirements, the objective of the CSSC is to acquire worldwide commercial telecommunications services, to include satellite capacity in C, Ku, Ka, and X-band, for mobile and fixed satellite transceivers on maritime, airborne, and ground platforms, as well as CT services, backhaul connectivity, monitoring and control, and operations. CSSC will augment Government-owned and operated telecommunications systems, providing significant improvement in data throughput and capability redundancy to Military SATCOM to meet critical mission requirements. The CSSC will meet the Navy’s increased demand for satellite throughput. Figure 1 provides a notional architecture of the CSSC.

Figure 1 – CSSC Notional Architecture

20. Scope.

The CSSC shall be capable of providing access to an end-to-end service capable of supporting up to 150 full period, full duplex connections between a NDP and the end user terminal through the means of satellite, CT, and backhaul telecommunications connectivity. Each end-to-end connection for a single CSSC user is also referred to as a circuit. Circuits shall have the capability of operating as full duplex, symmetric, and asymmetric. Figure 2 below illustrates a notional CSSC end-to-end architecture, which consists of four parts, and is the focus of this PWS – space, CT, backhaul, and NDP. The space segment is comprised of the commercial satellite resources required to uplink and downlink satellite links. The terrestrial segment is composed of the CT, backhaul, and NDP. 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 contract.

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

21. Performance Requirements.

1.1 Task 1 – End-to-End Performance Requirements.

The CSSC architecture shall consist of end-to-end services, which are defined as one or more full period, full duplex circuit between an end user terminal and a NDP. Each end-to-end circuit for a single CSSC user shall have the capability of operating as full duplex, symmetric, and asymmetric and shall consist of the space segment between the CT and the end user, the uplink and downlink chain of the CT, and the backhaul connectivity between the CT and the NDP.

1.1.1 Subtask 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 3 – End-to-End Operational Availability, while meeting the following performance requirements:

1.1.1.1 Segment S2: Minimum Backhaul sub-segment Ao of 99.99 percent

1.1.1.2 Segment S4A: Minimum CT Outbound Ao of 98.6 percent

1.1.1.3 Segment S4B: Minimum CT Inbound Ao of 98.6 percent

1.1.1.4 Segment S4C: Minimum Satellite Ao of 99.99 percent

1.1.1.5 End-to-end bit error rate (BER): Less than or equal to 1x10-8

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

1.1.1.7 End-to-end 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 end-to-end packet loss calculation.

1.1.1.8 End-to end jitter: Between the CT and NDP of less than or equal to 30 milliseconds.

1.1.1.9 Design solution: The contractor shall provide a solution design document that describes, in detail, how the end-to-end performance requirements listed in Section 6 of this PWS shall be achieved and include a network topology diagram. A draft solution design shall be delivered 7 calendar days after the task order award date. The final solution design shall be delivered 21 calendar days after task order award date.

Figure 3 – End-to-End Operational Availability

6.1.1.10 End-to-End Ao: The end-to-end Ao for each circuit shall be equal to or greater than 97%. 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)

1.1.1.10 Uptime is defined as the amount of time the circuit is operational. This includes the full Period of Performance (POP) of the end-to-end service, whether or not it is being allocated or actively utilized.

1.1.1.11 Downtime is defined as the amount of time the service is not operational, which includes services that do not meet the BER, 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 shall 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 Government Furnished Equipment (GFE) failure or beam transition for mobile platforms.

1.1.2 Subtask 2 – Outage Credits.

An outage is defined as a service disruption that includes, but is not limited to, failure, interruption, delay, fault, interference, or malfunction of service. If service on an end-to-end circuit provided by the contractor is interrupted resulting in an Ao of less than 97 percent, or greater than 21.6 hours for the duration of a month, the contractor shall issue a credit to the Government for each hour and fraction thereof. For each hour of interruption, a credit of 1/720 of the monthly charge shall be deducted from the monthly price, in which 720 hours per month represents 24 hours per day for 30 calendar days. The outage credit is applicable to both the space and terrestrial segment services on an end-to end-circuit that are unavailable or unusable due to the outage during a particular month. The contractor shall include an outage summary report with each Monthly Contract Status Report.

1.1.3 Subtask 3 – Credit Exceptions.

No credit shall be due:

1.1.3.1 If, on each end-to-end circuit, the total downtime in a month is less than or equal to 21.6 hours.

The following formula applies:

(1 – Minimum Ao)(Hours per Month) = Maximum Allowable Outage Hours per Month

Where:

Minimum Ao = 97 percent

(24 hours/day)(30 calendar days/month) = 720 hours/month

(1 – 0.97) x 720 = 21.6 hours

1.1.3.2 For outages due to planned CT antenna re-pointing.

1.1.3.3 In the event the cause of the outage is due to failure of GFE, or GFE limitations such as user terminal antenna blockage and beam transitions for mobile platforms.

1.1.3.4 For preventive maintenance, as defined in Section 6.5.2.

1.1.4 Subtask 4 – As-Built Drawing Packages.

The contractor shall prepare and deliver the as-built drawing packages in AutoCAD 2011 or above. The drawings shall document the terrestrial architecture, to include the interface to the Government equipment or NDP, and shall be fully readable and editable. As-built drawings packages shall be completed in accordance with the latest Shore Installation Process Handbook (SIPH) and delivered within 45 calendar days after installation completion.

1.2 Task 2 – Space Segment Technical Performance and Requirements.

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

1.2.1 Subtask 1 – Satellite Capacity.

The contractor shall provide commercial satellite space segment for full duplex communications in the C, Ku, Ka, and/or X frequency bands free from interference. The Navy will procure varying amounts of satellite capacity over time. The Navy will procure two types of capacity, baseline capacity and non-baseline capacity, described below. The contractor shall demonstrate the ability to provide satellite resources in sufficient quantities to satisfy bandwidth capacity identified in Appendix II.

1.2.1.1 Baseline Bandwidth Requirements. The contractor shall propose solutions which deliver the user terminal data rate requirements shown in Appendix I, while maximizing power and bandwidth efficiency and coverage. The Government intends to procure bandwidth in coverage regions (defined in Section 6.2.8) for the equivalent amount of satellite bandwidth required to support the user terminal data rates shown in Appendix I for the anticipated amounts of active terminals in the regions. The amount of bandwidth will vary over the years based on changing regional concentrations of Navy operations and mission requirements. The current projections of baseline bandwidths are listed in Appendix II. These projections are based on current estimates and are not guaranteed to be procured. Upon contractor receipt of the Commercial Satellite Service Request (CSSR) for Baseline Bandwidth, the contractor shall respond with a completed Link Budget Analysis worksheet within 72 hours after receipt of the request. Bandwidth shall be available for use within 30 calendar days after issuance of the task order.

1.2.1.2 Non-Baseline Bandwidth Requirements. The contractor shall develop plans and be prepared to accommodate non-baseline requirements. The Navy requires the capability to provide non-baseline bandwidth to support short term, heightened operational tempos, or surge requirements for specific operational regions as defined in Appendix II. The duration of non-baseline requirements could range 1 month up to 12 months. Upon contractor receipt of the CSSR for Non-baseline Bandwidth, the contractor shall respond with a completed Link Budget Analysis worksheet within 48 hours after receipt of the CSSR.

1.2.2 Subtask 2 – Required Space Segment Quality.

Technical parameters to be used for link budgets are contained in Appendices I and II. Link budgets shall be submitted with the technical proposal for all modem data rates requested in Appendix II. When terminal locations are not specified, link budgets shall be prepared based on the worst-case scenario, defined as a location within the required coverage area with the lowest satellite effective isotropic radiated power (EIRP), lowest gain-to-noise temperature (G/T), and a 15 degree look angle. The link budget shall support the target BER at the most efficient modulation scheme, with sufficient margin to 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. Satellites shall be either station kept or inclined orbit with an inclination of no greater than +/- 8 degrees.

1.2.2.1 Acceptability of inclined orbit satellites by region may be dependent upon the compatibility of terminals for that region and their operational capacity as defined in Appendix I when purchasing non-baseline capacity.

1.2.3 Subtask 3 – Frequency Ranges.

The contractor shall provide commercial satellite space segment for full duplex communications in the C, Ku, Ka, and X frequency bands, free from interference. Transponder frequency ranges shall be completely within the ranges specified by the fielded equipment parameters, as described in Table 1.

Table 1 – Frequency Ranges

1.2.4 Subtask 4 – Polarization.

Appendix I defines the specific polarization by user terminal. The contractor shall use any combination of circular or linear space segment, as long as it supports the operation of terminals listed in Appendix I to support baseline and non-baseline requirements.

1.2.5 Subtask 5 – Satellite Link Availability.

1.2.5.1 Reliability and Bandwidth Assurance. 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 include in each proposal a Satellite Availability Report covering the previous 30 calendar days, the previous year, and the lifetime of the satellite.

1.2.5.2 Bandwidth and Power Optimization.

1.2.5.2.1 Reconfiguration. Reconfiguration of the bandwidth may be required to accommodate routine changes in operations, pre-planned changes in operations, or emergency changes in operations. The Government may require reconfiguration in order to achieve higher operating throughputs and improved operating efficiency. A written request will be submitted to the contractor from the Government. The contractor shall analyze the desired data rates and availability, the operating regions, the terminal variant/modem characteristics, and the satellite characteristics to determine available capacity. If required, the contractor shall conduct link budget analyses and provide the recommended TPs and the corresponding frequency matrices to the CSSC Technical Advisor (TA). The timeline for the contractor to process and disseminate the updated TP and corresponding frequency matrices is 72 hours for Routine requests, 12 hours for Emergency requests, and 4 hours for Pre-Planned requests.

1.2.5.2.1.1 Routine Reconfiguration Request. A routine request is any non-emergency request that requires the development of new TPs that utilize existing bandwidth in order to meet mission parameters.

1.2.5.2.1.2 Emergency Reconfiguration Request. An emergency request is defined as any request that is the result of an unforeseen condition that threatens the national security of the U.S. or its allies. Examples include, but are not limited to, emergent military actions and disaster relief efforts that require a rapid response in order to ensure mission success or preserve life and property. Emergency requests require the development of new TPs that utilize existing bandwidth in order to meet mission parameters.

1.2.5.2.1.3 Pre-planned Reconfiguration Request. A pre-planned request is any request that allows the use of a pre-planned contingency TP. Pre-planned TP means a contingency plan created in coordination with the Navy, utilizing the currently leased bandwidth, created prior to and available for quick transition to a set of expected contingency operations.

1.2.5.2.2 Utilization Monitoring and Optimization. The contractor shall actively monitor the utilization of leased transponder resources, seeking to optimize bandwidth utilization. The contractor shall include in the monthly report to the Navy resource utilization under 80 percent to include proposed solutions to optimize bandwidth.

1.2.6 Subtask 6 – Assured Access.

For space segment procured, the contractor shall provide non-pre-emptible satellite resources in the commercial C, X, Ka, and Ku frequency bands.

1.2.7 Subtask 7 – Satellite Hop.

The contractor shall ensure that each end-to-end circuit has no more than one satellite hop.

1.2.8 Subtask 8 – Satellite Coverage.

The proposed space segment solution shall cover the defined coverage area in accordance with Figure 4, Figure 5, Appendix II, and specific coverage area for Regions A, AF, AG, E, G, H, NA, SA, WP, S1, S2, S3, and S4, as defined in 6.2.8.4. The Government understands that space segment resources are limited in some 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 the user requirement with sufficient link margins. Technical solutions shall include EIRP and G/T coverage maps with clearly depicted and labeled contour lines. When inclined orbit satellites are proposed, technical solutions shall include EIRP and G/T coverage maps clearly depicting the coverage during the period of furthest north and south inclination. The contractor shall provide coverage maps in a format compatible for display on Google Earth. These coverage maps shall also be posted on the Web Tool (further details in Section 6.6). One hundred percent of the coverage area emphasized in each region shall be met throughout the POP at all times. When inclined orbit satellites are proposed, 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, at a point within the coverage area with the weakest satellite uplink G/T.

1.2.8.1 Contiguous Bandwidth. The Navy considers contiguous to be multiple transponders on a single satellite to meet the particular network requirement. The Navy will not accept blocks of non-contiguous bandwidth under 4 MHz in size. Multiple satellites capable of providing coverage of the target area are acceptable; however, it is vital to note that each of the Navy Satellite Communications (SATCOM) terminals can only point to one satellite at a time.

1.2.8.2 Beam Shaping. When solutions provide the Government rights to shape satellite beams, it shall be done in accordance with Table 2 – Beam Shaping Response Times, and in support of locations as directed by the Government. 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 proposed beam shaping capabilities and processes for each frequency band.

Table 2 – Beam Shaping Response Times

1.2.8.3 Beam Steering. When solutions provide the Government rights to steer satellite beams, it shall be done in accordance with Table 3 – Steerable Beam Response Times, and in support of locations as directed by the Government. Response is the time allotted to execute the action steering action and begins upon initial notification. When these solutions are employed, the contractor shall provide Beam Steering Plan with a detailed description of the proposed beam steering capabilities and processes for each frequency band.

Table 3 – Steerable Beam Response Times

1.2.8.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. While the Navy prefers the use of global beams, any solution that meets the satellite bandwidth requirements for the coverage areas described below is acceptable.

1.2.8.4.1 Region A. The basic requirement is for C, Ka, Ku, and/or X-band bandwidth over the North American region (Decimal Long -136.00, Lat 63.00, Long -150.00, Lat 60.00, Long -118.00, Lat 19.00, Long -86.00, Lat 2.00, Long -54.00, Lat 13.00, Long -70.00, Lat 24.00, Long -47.00, Lat 52.00, Long -115.00, Lat 52.00, Long -136.00, Lat 63.00) with emphasis over the continental U.S. and its littoral waters, and waters surrounding the Caribbean islands; as depicted in Figure 4.

1.2.8.4.2 Region AF. The basic requirement is for C, Ka, Ku, and/or X-band bandwidth over the Continental African region (Decimal Long -15.00, Lat 38.00, Long 12.00, Lat 40.00, Long 32.00, Lat 35.00, Long 60.00, Lat 2.00, Long 60.00, Lat -25.00, Long 32.00, Lat -37.00, Long 15.00, Lat -38.00, Long 2.00, Lat -2.00, Long -15.00, Lat 0.00, Long -25.00, Lat 15.00, Long -15.00, Lat 38.00) with emphasis over the littoral waters surrounding Africa; as depicted in Figure 4.

1.2.8.4.3 Region AG. The basic requirement is for C, Ka, Ku, and/or X-band bandwidth over the Afghanistan region (Decimal Long 40.00, Lat 33.00, Long 58.00, Lat 42.00, Long 77.00, Lat 38.00, Long 67.00, Lat 19.00, Long 40.00, Lat 33.00) as depicted in Figure 4.

1.2.8.4.4 Region E. The basic requirement is for C, Ka, Ku, and/or X-band bandwidth over the European region (Decimal Long -16.00, Lat 33.00, Long -17.00, Lat 54.00, Long -7.00, Lat 64.00, Long 35.00, Lat 64.00, Long 14.00, Lat 49.00, Long 41.00, Lat 35.00, Long 34.00, Lat 25.00, Long -16.00, Lat 33.00) with emphasis over the Mediterranean Ocean and littoral waters surrounding Europe; as depicted in Figure 4.

1.2.8.4.5 Region G. The basic requirement is for C, Ka, Ku, and/or X-band bandwidth over the Saudi Arabian region (Decimal Long 28.00, Lat 30.00, Long 36.00, Lat 38.00, Long 70.00, Lat 25.00, Long 50.00, Lat -3.00, Long 28.00, Lat 30.00) 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 4.

1.2.8.4.6 Region H. The basic requirement is for C, Ka, Ku, and/or X-band bandwidth over the Hawaiian Islands region (Decimal Long 178.00, Lat 50.00, Long -125.00, Lat 50.00, Long -100.00, Lat 25.00, Long -120.00, Lat 10.00, Long 178.00 Lat 10.00, Long 178.00, Lat 50.00) with emphasis over the air and sea transit corridors between the west coast of the United States and the waters around the Hawaiian Islands; as depicted in Figure 4.

1.2.8.4.7 Region NA. The basic requirement is for C, Ka, Ku, and/or X-band bandwidth over the Northern Atlantic region (Decimal Long -50.00, Lat 65.00, Long 00.00, Lat 65.00, Long 5.00, Lat 45.00, Long 2.00, Lat 22.00, Long -80.00, Lat 22.00, Long -50.00, Lat 65.00) as depicted in Figure 4.

1.2.8.4.8 Region SA. The basic requirement is for C, Ka, Ku, and/or X-band bandwidth over the South American region (Decimal Long -88.00, Lat 5.00, Long -77.00, Lat 14.00, Long -52.00, Lat 13.00, Long -27.00, Lat -5.00, Long -51.00, Lat -59.00, Long -82.00, Lat -59.00, Long -79.00, Lat -24.00, Long -88.00, Lat 5.00) with emphasis over littoral waters surrounding South and Central America; as depicted in Figure 4.

1.2.8.4.9 Region WP. The basic requirement is for C, Ka, Ku, and/or X-band bandwidth over the Western Pacific region (Decimal Long 85.00, Lat 12.00, Long 140.00, Lat 54.00, Long -155.00, Lat 54.00, Long -139.00, Lat 20.00, Long -155.00, Lat -50.00, Long 97.00, Lat -50.00, Long 85.00, Lat 12.00) with emphasis over waters surrounding Japan, Guam, Philippines, New Zealand, and Australia; as depicted in Figure 4.

1.2.8.4.10 Region S1. The basic requirement is for C, Ka and/or X-band bandwidth over the Atlantic Ocean region (Decimal Long -100.00, Lat 65.00, Long 10.00, Lat 65.00, Long 10.00, Lat -65.00, Long -100.00, Lat -65.00, Long -100.00, Lat 65.00) as depicted in Figure 5 with emphasis over the blue water areas bounded by 5 degrees North - 50 degrees North Lat and 105 degrees West - 15 degrees East Long.

1.2.8.4.11 Region S2. The basic requirement is for C, Ka and/or X-band bandwidth over the Indian Ocean region (Decimal Long -10.00, Lat 65.00, Long 100.00, Lat 65.00, Long 100.00, Lat -65.00, Long -10.00, Lat -65.00, Long -10.00, Lat 65.00) as depicted in Figure 5 with emphasis over the blue water areas bounded by 55 degrees North - 45 degrees South Lat and 15 degrees West - 80 degrees East Long.

1.2.8.4.12 Region S3. The basic requirement is for C, Ka, and/or X-band bandwidth over the Western Pacific Ocean region (Decimal Long 80.00, Lat 65.00, Long -170.00, Lat 65.00, Long -170.00, Lat -65.00, Long 80.00, Lat -65.00, Long 80.00, Lat 65.00) as depicted in Figure 5 with emphasis over the blue water areas bounded by 50 degrees North - 50 degrees South Lat and 65 degrees East - 150 degrees West Long.

1.2.8.4.13 Region S4. The basic requirement is for C, Ka, and/or X-band bandwidth over the Eastern Pacific Ocean region (Decimal Long 170.00, Lat 65.00, Long -80.00, Lat 65.00, Long -80.00, Lat -65.00, Long 170.00, Lat -65.00, Long 170.00, Lat 65.00) as depicted in Figure 5 with emphasis over the blue water areas bounded by 55 degrees North - 45 degrees South Lat and 165 degrees West - 90 degrees West Long.

Figure 4 – CSSC Operational Regions Coverage Graphic

Figure 5 – CSSC Blue Water Operational Regions Coverage Graphic

1.3 Task 3 – Terrestrial Services Technical Performance and Requirements.

1.3.1 Subtask 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 space segment described in Section 6.2 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 13.

1.3.2 Subtask 2 – Network Sizing.

The contractor shall provide backhaul capacity to support all end user circuits. The contractor shall design and deliver a network scaled to support both serial EIA-530 and 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:

The CFE is installed at the Naval Computer and Telecommunications Area Master Station (NCTAMS) in Norfolk (LANT), Wahiawa (PAC), and Naval Computer and Telecommunications Station (NCTS) Bahrain. Each NDP shall be sized to support at least 48 simultaneous serial and 48 simultaneous Ethernet circuits.

1.3.3 Subtask 3 – Commercial Teleport (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:

1.3.3.1 Within 120 calendar days after task order award, 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.

1.3.3.2 The government will provide GFE to support up to seven CTs.

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

1.3.3.4 The contractor shall equip the CT antennas with 1:1 redundant frequency converters and High Power Amplifiers that are 1:1 redundant with automatic switchover.

1.3.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 diverse power to accommodate all CT equipment and GFE.

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

1.3.3.6.1 SCPC operations shall be supported in all regions.

1.3.3.6.2 The dynamic bandwidth management system shall incorporate the use of COMTECH Vipersat Management System (VMS) GFE to support operations in Regions A, G, and WP.

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

1.3.3.8 When requested by the Government, the CTs shall be able to provide public internet access connection services to end user terminals.

1.3.3.9 The contractor shall ensure the CTs are able to support unannounced security inspections and scheduled GFE inventories by Government personnel or their representatives.

1.3.3.10 The contractor shall provide a Stratum 1 clock source to the CFE and GFE at each CT supporting the end-the-end CSSC service. Stratum 1 source shall be redundant and compatible with both CFE and GFE.

1.3.3.11 The contractor shall follow IA requirements to ensure that all CTs meet the administrative, operational, and physical security requirements in accordance with DIACAP Instruction and transition to 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.

1.3.4 Subtask 4 – 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 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 satellite service. The contractor shall maintain a continuous monitor of all uplinks and downlinks using the CSSC space segment. When notified that a DoD teleport will be accessing CSSC 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 TA. The contractor shall not be responsible for the DoD teleport’s compliance with international and federal guidelines, for the required terrestrial connectivity from the DoD teleport to the NDPs, for the Host Nation Agreement (HNA) or costs associated with landing rights at Government or DoD teleport sites.

1.3.5 Subtask 5 – Backhaul and NDP Connectivity.

The contractor shall provide backhaul connectivity to the NDPs no later than 120 calendar days after task order award. The contractor shall ensure the final design includes the following key features:

1.3.5.1 The backhaul segment shall meet the performance requirements as set forth in Section 6.1 – End-to-End performance requirements.

1.3.5.2 The contractor shall provide backhaul connectivity to meet terrestrial requirements in all regions as noted in Appendix II.

1.3.5.3 The backhaul infrastructure shall accommodate the baseline data throughput requirements, non-baseline requirements, M&C traffic, and any data management overhead. The infrastructure shall be scalable to accommodate future growth.

1.3.6 Subtask 6 – Installation and Maintenance.

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

1.3.6.1 Configuration Management. For all CFE located at the NDPs, the contractor shall provide, within 14 calendar days after task order award, configuration management documentation which includes the Integrated Logistics Support (ILS) Plan. Upon Government acceptance of the network architecture, the contractor shall provide configuration management documentation in accordance with the Shore Installation Process Handbook (SIPH) COMSPAWAR M-4720.1.

1.3.6.2 Equipment Specifications. The contractor shall provide technical specifications for all proposed CFE.

1.3.6.3 Installations at NDPs. At the NDPs, the contractor shall install and maintain all CFE and equipment interfaces to GFE in accordance with the SIPH. The contractor shall:

1.3.6.3.1 Perform a pre-installation site survey.

1.3.6.3.2 Develop an Installation Design Plan (IDP).

1.3.6.3.3 Install equipment and cables in accordance with the IDP.

1.3.6.3.4 Label equipment and cables in accordance with the IDP.

1.3.6.3.5 Remove all packing and waste materials from the premises.

1.3.6.3.6 Activate and configure the CFE.

1.3.6.4 Equipment Refresh. At the Government’s direction, the contractor shall optimize the network by employing more bandwidth efficient equipment. The contractor shall install, configure, operate, and maintain the equipment through the life of the contract. Any equipment refresh shall comply with all requirements listed under Section 6.3.6.3 – Installation at NDPs. At the close of the contract, the equipment shall revert to Government ownership.

1.3.6.5 CFE Maintenance and Repair at the NDPs. The contractor shall perform all maintenance and repair of CFE. Visitor Access Request (VAR) for maintenance personnel shall be provided and kept current on file at NDPs.

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

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

1.3.6.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 site or has been replaced shall be shipped to the Government-designated repair facility. The Government shall assume all shipping charges.

1.4 Task 4 – CSSC Transition Support and Implementation.

In support of the transition, the contractor shall develop, as part of their proposal, a plan and schedule for the implementation of the terrestrial standup and cutover to new services. The contractor shall demonstrate the ability to provide those services in accordance with the below paragraphs.

1.4.1 Transition Plan.

The Government will provide a transition plan within 7 days after task order award. It will include a schedule that illustrates the sequence and start dates of events based on the contractor’s provided durations of events.

1.4.2 Subtask 1 – Transition Support Plan.

The contractor shall develop and present a transition support plan within 14 days after award for transition at the Kickoff Meeting, referenced in Section 6.7.1.3.1. The plan shall detail the steps required to accomplish tasks listed in Sections 6.3.5, 6.3.3.1, and 6.4.1, 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 solution, performance and acceptance testing, performance and acceptance reporting, cutover of end user terminals onto the CSSC architecture, and dual illumination of the space segment when applicable. The plan shall demonstrate cutover of active CBSP circuits with no more than 30 minutes of downtime to the end users. The transition to CSSC architecture shall be ready to support GFE installation, light-off, and testing within 120 days after task order award. The plan shall support full operational capability on the new system within 180 days after issuance of the task order.

1.4.3 Subtask 2 – System Design and Validation.

The contractor shall provide drawings that illustrate the overall CSSC architecture. 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 test procedures for Government approval that validate the system design.

1.4.4 Subtask 3 – Final Acceptance Test.

The contractor shall develop and deliver a System Operational Verification Test (SOVT) document that will be used for the final acceptance testing at each NDP. The document shall meet the requirements of the SOVT Preparation and Execution Guide (SPEG) SPAWAR Instruction 3084.1. The SOVT document shall be provided 30 calendar days after award of the basic contract for review and approval by the Government. The SOVT, also referred to as the Final Acceptance Test, shall verify proper installation, operation of equipment, and performance of end to end connectivity.

1.4.5 Subtask 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 TA to ensure that existing services are not disrupted during the phased migration of GFE equipment from old to new CSSC 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. Fifteen MD-1366/U and 30 SLM-5650A GFE modems will be provided to the contractor to start the initial transition.

1.5 Task 5 – Operational Support to meet CSSC End-to-End Services.

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:

1.5.1 Subtask 1 – Global Schedule of Events (GSOE).

The GSOE provides the 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).

1.5.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 continuity test (Connectivity Tests Section 6.5.4.1) with the JFTOC and the end user terminal operator.

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