DRAFT RFP UCF 20201013.pdf

SEE ADDENDUM

(No Collect Calls)

HC101320R0014

b. TELEPHONE NUMBER

618-418-6191

8. OFFER DUE DATE/LOCAL TIME

5. SOLICITATION NUMBER 6. SOLICITATION ISSUE DATE

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STANDARD FORM 1449 (REV. 2/2012)

Prescribed by GSA – FAR (48 CFR) 53.212

(TYPE OR PRINT)

(SIGNATURE OF CONTRACTING OFFICER)

ADDENDA ARE

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

23.

CODE 10. THIS ACQUISITION IS

SUCH ADDRESS IN OFFER

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT

BELOW IS CHECKED

TELEPHONE NO.

HC10139. ISSUED BY

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

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME

SIERRA L. BILLHARTZ

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

(TYPE OR PRINT)

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

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

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

25. ACCOUNTING AND APPROPRIATION DATA

1. REQUISITION NUMBER

20.

ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED.

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

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

ARE NOT ATTACHED

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

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

SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:

. YOUR OFFER ON SOLICITATION

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN

% FOR:SET ASIDE:UNRESTRICTED ORX

SMALL BUSINESS

17a.CONTRACTOR/ CODE FACILITY

OFFEROR CODE

DISA/DITCO-SCOTT

2300 EAST DRIVE

BLDG 3600

SCOTT AFB IL 62225-5406

18a. PAYMENT WILL BE MADE BY CODE

RATED ORDER UNDER

DPAS (15 CFR 700)

13a. THIS CONTRACT IS A

13b. RATING

CODE15. DELIVER TO CODE 16. ADMINISTERED BY

SEE SCHEDULE

12. DISCOUNT TERMS11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

14. METHOD OF SOLICITATION

RFQ IFB RFPX

FAX:

TEL: SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

8(A)

HUBZONE SMALL

BUSINESS

SIZE STANDARD:

$35,000,000

NAICS:

517410

X

OFFER DATED

29. AWARD OF CONTRACT: REF.

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

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND

EMAIL:

TEL:

31c. DATE SIGNED

SEE SCHEDULE

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

24.22.21.19.

WOMEN-OWNED SMALL BUSINESS (WOSB)

ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

32g. E-MAIL OF AUTHORIZED GOVERNMENT REPRESENTATIVE

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

(CONTINUED)

PAGE 2 OF148

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

32a. QUANTITY IN COLUMN 21 HAS BEEN

RECEIVED INSPECTED

32b. SIGNATURE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

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

REPRESENTATIVE

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

37. CHECK NUMBER

FINALPARTIALCOMPLETE

36. PAYMENT35. AMOUNT VERIFIED

CORRECT FOR

34. VOUCHER NUMBER

FINAL

33. SHIP NUMBER

PARTIAL

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

41a. I CERTIFY THIS ACCOUNT IS CORRECT AND PROPER FOR PAYMENT

41b. SIGNATURE AND TITLE OF CERTIFYING OFFICER 41c. DATE

42a. RECEIVED BY (Print)

42b. RECEIVED AT (Location)

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

STANDARD FORM 1449 (REV. 2/2012) BACK

Prescribed by GSA – FAR (48 CFR) 53.212

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

SEE SCHEDULE

20.

SCHEDULE OF SUPPLIES/ SERVICES

21.

QUANTITY UNIT

22. 23.

UNIT PRICE

24.

AMOUNT

19.

ITEM NO.

HC101320R0014

Section A - Solicitation/Contract Form

EXECUTIVE SUMMARY

EXECUTIVE SUMMARY

The purpose for the publication of this Military Sealift Command (MSC) Next Generation Wideband

(NGW) Follow-On (FO) Contract 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 MSC NGW FO 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 MSC NGW FO 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 MSC NGW FO Draft RFP. However, comments to this Draft RFP are encouraged and welcomed. (Additional information is provided below.)

Potential offerors interested in the MSC NGW FO 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. Effective November 12, 2019, FBO.gov was retired, and Beta.SAM.gov is now the authoritative source for Contract Opportunities. It is suggested that all interested parties check the

Beta.SAM.gov web site at https://Beta.SAM.gov, for posted changes to this MSC NGW FO Draft

RFP. Visit the Learning Center at Beta.SAM.gov for videos, FAQs and other information!

The documentation contained in the MSC NGW FO 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 data elements are subject to change throughout the posting life of the MSC NGW FO Draft RFP on the Beta.SAM.gov web site. It is the Government’s intent to publish as much data as available, as quickly as possible, so offerors can begin preparing their proposals. However, everyone is again reminded at this point that the MSC NGW FO 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 Beta.SAM.gov web site as a Final RFP.

For instructions for how to submit questions and comments in response to this RFP, please see the

Special Notice announcement document entitled, Presolicitation Conference Announcement.

Comments on the MSC NGW FO Draft RFP should be emailed to sierra.l.billhartz.civ@mail.mil and kathryn.v.koerkenmeier.civ@mail.mil at any time. Comments received after the deadline may not be addressed by the Government.

mailto:sierra.l.billhartz.civ@mail.mil

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

MSC NGW FO

FFP

Base Period

POP: April 22, 2021 - April 21, 2024

FOB: Destination

NET AMT

OPTION MSC NGW FO

Option Period 1

POP: April 22, 2024 - April 21, 2026

OPTION MSC NGW FO

Option Period 2

POP: April 22, 2026 - April 21, 2028

OPTION MSC NGW FO

Option Period 3

POP: April 22, 2028 - April 21, 2030

OPTION MSC NGW FO

Option Period 4

POP: April 22, 2030 - April 21, 2031

CONTRACT MINIMUM/MAXIMUM QUANTITY AND CONTRACT VALUE

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

MINIMUM

QUANTITY

MINIMUM

AMOUNT

MAXIMUM

QUANTITY

MAXIMUM

AMOUNT

$25,000.00 $571,365,460.60

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

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

CLIN

MINIMUM

QUANTITY

MINIMUM

AMOUNT

MAXIMUM

QUANTITY

MAXIMUM

AMOUNT

SECTION B

Section B Pricing Worksheet: See Attachment 1

Section C - Descriptions and Specifications

MSC NGW FO PWS

COMMERCIAL SATELLITE COMMUNICATIONS (COMSATCOM)

PERFORMANCE WORK STATEMENT (PWS)

Satellite Business Solutions (SBS)

CTC/CSS/CS2/CS2SB/SBSXXXX

As of [Publish Date]

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:

(If this is a follow-on order, insert the contract number and the

TO number to which it is a follow-on. If this is not for a follow-on order, state “Not Applicable”)

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

Name: To be completed at time of award

Organization:

DODAAC:

Address:

Phone Number:

Fax Number:

E-Mail Address:

2. Contract or Task Order Title.

Military Sealift Command (MSC) Next Generation Wideband (NGW) Follow-On (FO)

3. Background.

MSC has a need for Commercial Satellite Services in support of mission requirements.

4. Objectives.

The goal of this MSC NGW FO vehicle is to sustain and modernize the current NGW satellite communications network supporting MSC. It is MSC’s objective to leverage the most effective blend of commercially available shared and dedicated services to support MSC satellite requirements.

This modernized network should economically optimize the throughput capabilities to MSC remotes and improve on the coverage of the existing network.

5. Scope.

The Government requires a commercially managed global capability with failover coverage to support current and future MSC ships and land based capabilities with connectivity to commercial teleports (CTs) and terrestrial backhaul that will provide internet access and Voice over IP services in accordance with terms and conditions provided in paragraph 6 and in the technical specification. The government requires a modernization of the MSC fleet, allowing the fleet to leverage technologies, which are more efficient, economical, and offer increased capability, as they become available to market. The contractor shall maintain and operate commercial communications infrastructure, which includes satellite systems, teleport services, and terrestrial services.

6. Performance Requirements.

6.1. Global Network

6.1.1. Portability

The contractor shall provide the ability to relocate or “port” COMSATCOM services as user requirements change.

When portability is exercised, evidence of equivalent net present value shall be provided by the contractor. Subject to availability, the ported bandwidth/throughput shall be available for use within fourteen (14) calendar days of the formal initial notification by MSC for routine operations and within 48 hours for emergency or critical operations.

Portability shall consist of redeployment of the following:

• One transponder/satellite to another

• Between beams or transponders on a single satellite

• One frequency band to another

• One region to another

6.1.2. Space Segment Coverage

The contractor shall provide managed services to the coverage areas defined below. Coverage requirements are broken into two distinct categories, Primary and Transit Regions. Primary Regions of Operation are regions where the space segment must be covered in full over the entirety of the region with higher information rate requirements.

The areas defined as transit areas specify a set of boundaries where the contractor shall supply sufficient coverage, to support continuous communications to an asset traveling a route between primary regions of operations on lesser information rate requirements. The transit regions do not need to be covered in full, however they shall support constant communications over a continuous route between the prescribed primary regions. Finally, the global coverage requirement requires the lowest information rate requirements.

6.1.2.1. Primary Regions of Operations

The contractor shall provide coverage for the primary regions defined below in full. The required information rates for each region are specified in section 6.2.1.1.2. The contractor shall support each coverage area within the constraints, polarity, min elevation angle etc. of the terminals included in Appendix A, Technical Specification.

Region Coordinate Bounds Visual

Lat Lon

Primary 1 33.11 -12.10

28.87 33.72

45.47 45.29

59.84 3.96

60.11 -13.65

33.11 -12.10

Primary 2 10.10 41.38

11.27 63.17

24.99 65.86

30.52 50.56

29.09 32.52

10.10 41.38

Primary 3 100 nautical mile radius around Diego

Garcia (Lat: 7.32S, Lon: 72.42E)

Primary 4

(exclusive of

Primary 4A)

-3.07 106.00

-5.66 106.14

-8.23

116.65

-0.16

159.90

22.33 162.21

22.17 115.65

19.74 93.03

5.75 94.81

-3.07 106

Primary 4A

(exclusive of

Primary 4)

19.1695 147.35

19.39 143.76

14.36 139.20

10.23 144.15

12.42 150.09

19.17 147.35

Primary 5 22.53 162.01

44.96 160.64

44.91 136.63

42.67 133.52

35.06 119.40

22.44 116.99

22.53 162.01

Primary 6 50.42 -122.27

49.61 -136.85

28.24 -121.84

27.99 -114.13

50.42 -122.27

Primary 7 18.37 -97.24

17.25 -77.40

17.45 -63.74

19.40 -64.03

30.27 -84.06

31.18 -99.32

18.37 -97.24

Primary 8 25.82 -75.84

43.26 -58.43

17.45 -63.74

46.22 -68.10

39.16 -77.44

29.67 -82.93

25.82 -75.84

Table 1 Primary Regions of Operation

6.1.2.2. Transit Regions

The contractor shall support routes within the boundaries defined below. The contractor shall support routes with continuous coverage between the Primary Regions of Operation.

- Transit Region 1: At a minimum, the contractor shall support a transit route between Primary Regions 2 and 4.

- Transit Region 2: At a minimum, the contractor shall support a transit route between Primary Regions 4, 5, and 6.

- Transit Region 3: At a minimum, the contractor shall support a transit route between Primary Regions 6, 7, and 8.

Region Coordinate Bounds Visual

Lat Lon

Transit 1 14.99 64.10

0.05 61.01

-0.05 95.31

15.07 93.35

14.99 64.10

Transit 2 49.53 -136.59

30.10 -163.80

44.93 -199.25

14.98 -198.05

15.03 -157.94

28.27 -121.9

49.53 -136.59

59.85 -14.07

43.23 -58.64

25.72 -76.01

19.41 -63.93

32.92 -12.21

59.85 -14.07

Transit 3 59.85 -14.07

32.92 -12.21

19.41 -63.93

25.72 -76.01

43.23 -58.64

59.85 -14.07

Table 2 Transit Regions of Operation

6.1.2.3. Global Maritime Coverage

At a minimum, the contractor shall also provide global coverage defined as 95% coverage between 80 degrees North and 80 degrees South.

6.1.3. Required Space Segment Quality

The contractor shall provide managed network services in accordance with Appendix A, Technical Specification.

6.1.3.1.

The contractor shall provide managed network services for remote terminals described in Appendix A, Technical

Specification. Managed network services include space segment, CT services, and connection via commercial backbone from the teleport to the access point for the leased terrestrial line(s) described in PWS paragraph 6.1.4.2.

The contract shall provide solutions with links capable of supporting the regional user requirement with link margins that are adequate to overcome degradation that may be caused by equipment or the local environment. Network requirements are defined under 6.1.3.

6.1.3.2.

When terminal locations are provided in 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

[terminal 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 greater than 0.5 decibels (dB) 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. Space segment must be offered on a satellite(s) that is currently on-orbit, operational, and station-kept; inclined orbit satellites will not be considered.

6.1.3.2.1. End-to-End Performance Requirements.

The MSC architecture shall consist of end-to-end services, which are defined as one or more full period, full duplex or simplex circuits between an end user terminal and an MSC Dedicated Point of Presence (MDP). Each end-to-end circuit for a single MSC user shall have the capability of operating as full duplex, simplex, symmetric, and/or asymmetric links as defined in the task order. Each Circuit shall consist of the space segment between the CT and the end user, including the uplink and downlink chain of the CT, the Customer Furnished Equipment (CFE) network equipment located at the CT and MDP, and the terrestrial segment backhaul connectivity between the CT and the

MDP.

6.1.3.2.1.1. End-to-End Service Performance Requirements:

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

6.1.3.2.1.2. 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 MDPs. See Figure 1.

6.1.3.2.1.3. Space Segment:

Minimum Ao a link availability of 99.7 percent for FDMA satellite links and 99.5 percent for TDMA satellite links.

The space segment includes the satellites and Earth Station terminals to include the uplink and downlink chain and all interfaces to CFE modems at the CTs. See Figure 1.

6.1.3.2.1.4. 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.2.1.5.

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

6.1.3.2.1.6. End-to-end latency:

Less than or equal to 1.2 seconds.

6.1.3.2.1.7. Terrestrial packet loss:

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

6.1.3.2.1.8. Terrestrial jitter:

Between the CT and MDP of less than or equal to 20 milliseconds.

Figure 1 – End-to-End Operational Availability

6.1.3.2.1.9. End-to-End Ao:

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

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

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

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

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

Downtime values will not include time attributed to Government-owned equipment failure or beam transition for mobile platforms.

6.1.4. Network Infrastructure

The contractor shall provide access to a global terrestrial network, which integrates all required CTs and MSC points of presence. The contractor shall manage a global network management system to integrate all aspects of the global infrastructure; specific requirements for these elements are defined below. The contractor’s global network shall maintain definitions for all Government elements and nodes across all teleports including their operational parameters, compatible with the network. The contractor’s global infrastructure shall enable utilization of emerging technology as it becomes available.

6.1.4.1. Teleport Service Requirements

The contractor shall provision sufficient teleport services, so that the combined teleport infrastructure is capable of integrating all remote terminals into an integrated network supporting transport of voice, video and data.

The commercial teleport solution must support the Primary regions, Transit regions and global coverage requirement defined in 6.1.2 at the primary, transit and global service levels, defined in 6.2.1.1 or (if modernized) 6.2.2.3.1, to the respective MSC end user terminals.

The contractor shall provide teleport services that support the total aggregate information rate of each Primary and

Transit regions defined in 6.1.2 and global coverage networks supporting transport of voice, video, and data, as well as access to the public Internet. The contractor shall ensure redundant capabilities are utilized to meet the availability parameters defined in 6.1.3.2.1.1.

The contractor shall establish and adhere to Quality of Service (QoS) policies for traffic management and optimization technologies that maximize end-user Quality of Experience (QoE) in accordance with Government requirements. The Government will work with the contractor to define and update the QoS policies based on operational needs as necessary.

The networks supporting the Primary operating regions shall be configured in a manner which:

allows remotes to maintain or exceed throughput requirements through means such as Adaptive Coding and

Modulation and/ or Adaptive TMDA (A-TDMA) protocol, allows for remotes to meet required regional data rates when located within the regions defined in 6.1.2.1

The network or networks supporting the Transit regions defined in 6.1.2.2 shall be configured to provide the required Committed Information Rate (CIR) to each end user terminal regardless of which Transit region the terminal is operating under.

The network or networks supporting the global coverage requirement defined in 6.1.2.3 shall be configured to provide the required CIR to each end user terminal regardless of which region the terminal is operating under.

6.1.4.2. Network Backhaul Requirements

The contractor shall provide a global terrestrial backbone used to deliver secure and reliable voice, video, and data services on demand, anywhere at any time. The contractor shall deliver the terrestrial network backhaul segment for

MDPs, terrestrial segment capabilities, appropriate network sizing and scalability, terrestrial connectivity, and required end-to-end performance as described below.

6.1.4.2.1. MSC Designated Points of Presence (MDPs)

The contractor shall deliver the terrestrial network backhaul segment to the four MSC Points of Presence.

Contractor-provided circuits and CFE installed at the Points of Presence shall be capable of supporting the full aggregate information rate associated to all space segment services landing at Points of Presence. The backhaul infrastructure must provide Advanced Encryption Standard (AES-256) encryption across the entire backhaul.

1. Wahiawa, HI

2. Pensacola, FL

3. Norfolk, VA (planned)

4. Norfolk, VA MCEL

The specific addresses for each MDP will be provided in Appendix C.

6.1.4.2.2.

The contractor shall deliver terrestrial segment capabilities that are compatible with and of sufficient quantity, to interface with the applicable space segment and commercial teleports. The contractor shall provide all equipment and services from the closest contractor demarcation point for up and down linking the MSC end user terminals, connecting to the contractor-furnished terrestrial infrastructure, and transmitting and receiving each circuit to the

MSC Points of Presence. The contractor shall provide all equipment and services to implement an end-to-end solution.

At Government’s discretion, requirement to host Government Furnished Equipment (GFE) may be introduced as mission requirements change.

6.1.4.2.3. Network Sizing

The contractor shall have the ability to support a minimum of aggregate demand of 105 end user circuits simultaneously. The contractor shall design and deliver a scalable network to support future increased data requirements, approximately an aggregate demand of 170 end user circuits, at the CTs and MDPs.

The terrestrial backhaul terminating at each MDP shall be capable of supporting the aggregate throughput of all remotes plus any additional required overhead.

6.1.4.2.4.

The contractor shall provide terrestrial connectivity no later than 90 days after the initial order start date and 90 days for any order requiring terrestrial thereafter.

6.1.4.2.5. Network Scalability

Contractor shall have the ability to scale port densities at the CTs and MDPs to accommodate future increases in demand or service levels and provide technical refresh capabilities to accommodate new technologies introduced by the Government.

The Government may stand up additional MDPs in service regions. The contractor shall support the additional network components and each MDP shall be sized to support at least 105 ethernet circuits unless otherwise stated by the Government at initial request. The contractor shall ultimately size each MDP to support approximately 170 additional modernized ethernet circuits.

6.1.4.3. Ship Failover Capability

At a minimum, the contractor shall provide the capability to prioritize at least three Internet Protocol (IP) sources/

Wide Area Network ports to a given MSC asset. These services consist of the Primary and Secondary service offered by the contractor and a Government owned and operated network with Government-owned and managed equipment.

The contractor shall provide the capability to automatically failover to lower priority IP sources/ WAN ports if the higher priority IP sources/ WAN ports is unable to close. The contractor shall provide the highest prioritization to the IP source with the highest data rates and lower prioritization to the secondary IP source with lower data rates.

The contractor shall provide the capability to automatically return to the higher priority IP source once the link is again operational.

Depending on specific mission requirements, the Government may be required satellite services to operate solely on the Government owned equipment set already installed on several MSC assets. The contractor’s failover capability shall interface with this Government equipment set and shall enable the Government to force the sole utilization of the Government equipment and network, listed in Appendix A, Technical specification.

6.2. NGW FO Service Requirements

The contractor shall provide access to a global managed network capable of supporting the requirements enumerated in the remainder of this section. The contractor shall ensure the managed service is capable of providing the specified coverage, service levels, quality, teleport, and network backhaul and terrestrial requirements prescribed below.

At contract start, the contractor shall provide sustainment level primary and secondary communications services to each MSC asset.

6.2.1. Sustainment Managed Services

The primary Ku-Band service shall be designed to provide the service level requirements stated in PWS section

6.2.1.1.2 to each asset while operating in the primary areas of operation as stated in PWS section 6.1.2.1. The primary Ku-Band services shall provide the service level requirements stated in PWS section 6.2.1.1.3 to each asset along a route within the boundaries of the transit regions between the primary areas of operation as stated in PWS section 6.1.2.2,. The secondary L- Band communications service shall be designed to enable each MSC asset to operate at the service levels stated in PWS section 6.2.1.1.4, with 95% coverage between 80 degrees North and 80 degrees South.

6.2.1.1. Service Level Requirements

6.2.1.1.1. Teleport Service Level Requirements

The contractor shall provide services to allow for the oversubscription of services, with specific authorization from the Government. The contractor shall provide services to allow remotes to dynamically maintain or exceed throughput requirements through means such as Adaptive Coding and Modulation and/ or A-TDMA protocol.

6.2.1.1.2. Primary Region Services

At a minimum, the contractor’s solution shall support the specified full duplex symmetrical CIR, as defined below, over the entirety of the Primary Operating Regions defined in PWS section 6.1.2.1, to each terminal specified in

Appendix A, Technical Specification. All remotes allocated to a network within a Primary Operating Region shall be capable of operating at their allocated CIR simultaneously. Additionally, the contractor shall process requests from the Government to enhance CIRs to specific remotes while, accordingly within the total network size, decreasing CIRs to other remotes within the same network.

The contractor shall provide minimum acceptable network sizes capable of achieving the specified full duplex symmetrical Maximum Information Rate (MIR) detailed in Table 3, over the entirety of the Primary Operating

Regions as specified in PWS section 6.1.2.1, to each terminal specified in Appendix A, Technical Specification. The

Government may permit networks of smaller sizes at the task order level based on specific operational requirements.

Region Committed Information Rate (CIR) Maximum Information Rate (MIR)

Primary 1 1024 kilobits per second (kbps) 2048 kbps

Primary 2 1024 kbps 2048 kbps

Primary 3 1024 kbps 2048 kbps

Primary 4

(exclusive of

Primary 4A)

1024 kbps 2048 kbps

Primary 4A

(exclusive of

Primary 4)

1024 kbps 2048 kbps

Primary 5 1024 kbps 2048 kbps

Primary 6 512 kbps 1024 kbps

Primary 7 512 kbps 1024 kbps

Primary 8 512 kbps 1024 kbps

Table 3 Primary Regions Service Level Requirements

6.2.1.1.3. Transit Region Services

At a minimum, the primary communications service link shall support the specified full duplex symmetrical CIR, as defined below, to each asset along a route, within the boundaries of the transit regions, as stated in PWS section

6.1.2.2, between the primary areas of operation. Transit areas may operate in contention with areas of concentration in order to optimize the network performance.

Region CIR

Transit 1 512 kbps

Transit 2 512 kbps

Transit 3 512 kbps

Table 4 Transit Regions Service Level Requirements

6.2.1.1.4. Global Services

At a minimum, the contractor shall support global satellite communications (as defined in PWS 6.1.2.3) managed services at minimum data rates of 64 kbps with options for enhanced data rates of 128 kbps and 256 kbps when outside of the above Primary and Transit Regions.

6.2.1.1.5. Military Sealift Operation Center (MSOC) Services

The contractor shall provide service for at least two MSOCs located in the Far East/ Eastern Asian region. The contractor’s service must support dedicated data rates and compatible equipment described in Appendix A, Technical Specification.

6.2.1.1.6. Carry On Satellite Communications (SATCOM) Capabilities

The contractor shall provide service for a small form Carry On SATCOM capability to the extent detailed in

Appendix A. MSC shall be responsible for storage of Carry On SATCOM and associated spares. The contractor’s service must support dedicated data rates and compatible equipment described in Appendix A, Technical

Specification.

6.2.2. NGW Modernization

6.2.2.1. Modernized Equipment

The contractor shall provide maritime ruggedized terminals that will be fully capable and protected by radome. The contractor shall provide up to three antennae to meet the constraints defined below. The contractor shall notify MSC of emerging technologies to ensure utilization of latest and most efficient technology. MSC shall be responsible for storage of associated above and below deck equipment.

If requested by the Government, the contractor shall provide the capability to enable transmission security

(TRANSEC) over the modernized modem by encrypting commands to the satellite (Telemetry, Tracking and

Control - TT&C) and commands to the user terminals (signaling channels) at the Government’s request.

In addition to equipment to support the modernized services, the contractor shall provide the option for MSC to purchase and install small, medium, and large weight class variants of an X-Band antenna.

6.2.2.1.1. Above Deck Equipment

The contractor shall provide a small weight class primary antenna less than 285 pounds

The contractor shall provide a small weight class secondary antenna less than 55 pounds

The contractor shall provide a small weight class tertiary X-Band antenna less than 55 pounds.

The contractor shall provide a medium weight class primary antenna less than 510 lbs.

The contractor shall provide a medium weight class secondary antenna less than 220 lbs.

The contractor shall provide a medium weight class tertiary X-Band antenna less than 220 pounds.

The contractor shall provide a large weight class primary antenna less than 615 lbs.

The contractor shall provide a large weight class secondary antenna less than 350 lbs.

The contractor shall provide a large weight class tertiary X-Band antenna less than 350 pounds.

The contractor shall also be capable of installing foundation and mounts, which may require installations in accordance with Appendix D.

6.2.2.1.2. Below Deck Equipment

The contractor shall provide aggregate small weight class below deck equipment less than 350 lbs.

The contractor shall provide aggregate medium weight class below deck equipment less than 525 lbs.

The contractor shall provide aggregate large weight class below deck equipment less than 700 lbs.

The contractor shall provide corresponding below deck equipment to fit within 12 Rack Units (RUs) including space requirements of the Uninterruptible Power Supply (UPS). The UPS must support a minimum of 45 minutes run time and must be full power conditioning with bypass capability. The UPS shall support 240 Volts/ 60 Hertz input.

6.2.2.2. Modernized Coverage

The contractor shall support Primary (as defined in PWS 6.1.2.1) and Transit regions (as defined in PWS 6.1.2.2) as well as a global coverage (as defined in PWS 6.1.2.3) with managed services with options for enhanced data rates compatible with the modernized equipment installed on the modernized MSC vessel.

6.2.2.3. Modernized Services

Once modernized equipment is installed and integrated, the contractor shall provide primary and secondary communications services via bands that correspond with the modernized equipment. The modernized managed service does not require utilization of Ku-Band and L-Bands as previously outlined in 6.2.1. The primary service shall provide, at a minimum, the service level requirements, stated in PWS section 6.2.1.1.2, to each asset while operating in the primary areas of operation as stated in PWS section 6.1.2.1. The primary communications link shall provide, at a minimum, the service level requirements, stated in PWS section 6.2.1.1.3, to each asset along a route, within the boundaries of the transit regions, as stated in PWS section 6.1.2.2, between the primary areas of operation. The secondary communications service shall enable, at a minimum, each MSC asset to operate at the service levels stated in PWS section 6.2.1.1.4, with 95% coverage between 80 degrees North and 80 degrees South.

6.2.2.3.1. Modernized Service Level Requirements

At a minimum, the contractor shall support 4 Mbps Forward Link and 2 Mbps Return Link with options for enhanced data rates compatible with the modernized equipment installed on the modernized MSC vessel. The

Government reserves the right to request data rate adjustments within the timeframe referenced in 6.5.1.

6.2.2.3.2. Ashore and Afloat Carry On SATCOM Capabilities

The contractor shall provide approximately 65 small form factor, Carry On SATCOM capability with at least two

Megabits per second (Mbps) forward link and one mbps return link. MSC shall be responsible for storage and maintenance of Carry On SATCOM and associated spares. The Carry On SATCOM capability shall support ashore and afloat vessels.

6.2.2.4. Optional Modernized Services

The contractor shall provide pricing for future “To Be Negotiated” Contract Line Item Numbers (CLINs) at the request of the Government. These future CLINs may include but are not limited to providing pricing options for utilizing future constellations and services or options to purchase and integrate TRANSEC capable equipment. The future “To Be Negotiated” CLINs shall remain within the scope of the MSC NGW FO requirement.

6.3. Operational Management & Web Tool

6.3.1. Transition Support Plan

The contractor shall develop a plan for contract transition from MSC’s previous contractor’s services to support the initial service requirement, such as terrestrial infrastructure, and also develop a plan for the implementation of the terrestrial infrastructure and transition to meet sustainment service requirements. Within 7 calendar days after initial task order start date, the Government will provide a schedule based on the contractor’s proposed plan. This schedule will illustrate the sequence and start dates of events based on the contractor’s provided durations of events. The contractor shall demonstrate the ability to provide those services in accordance with the below paragraphs.

The Government will provide the contractor with feedback on the draft Transition Support Plan included within their proposal within 7 days after contract award. The contractor shall update and present the final Transition

Support Plan within 14 calendar days after initial task order start date at the Kick-Off Meeting, referenced in PWS

6.5.5.1. The plan shall detail the steps required to accomplish tasks listed in PWS 6.1 as well as PWS 6.2.1 to include a detailed list of the CFE to be installed in each of the MDPs. The plan shall include stand-up of the terrestrial network and CT facilities to support the MSC solution, performance and acceptance testing, performance and acceptance reporting, and notional cutover of end user terminals onto the MSC NGW FO solution. The plan shall demonstrate cutover of active end user circuits with no more than 30 minutes of downtime to the end users.

The plan shall support transition to full operational capability to meet the sustainment requirements of the MSC

NGW FO system within 120 calendar days after initial task order start date.

The Government reserves the right to provide updates and approval of updates to the Transition Support Plan at each

Program Management Review (PMR) based on evolving mission requirement

6.3.2. Modernization Plan

The contractor shall develop a plan and timeline for the MSC NGW FO transition from MSC’s sustainment service levels to the modernized service level requirement defined in 6.2.2.3.1. The plan shall include stand-up of the modernized terrestrial network and CT facilities to support the MSC modernized solution, performance and acceptance testing, performance and acceptance reporting, and notional cutover of end user terminals onto the modernized MSC NGW FO solution. The plan shall demonstrate cutover of active end user circuits with no more than 30 minutes of downtime to the end users. The plan shall detail the steps required to accomplish tasks listed in section 6.2.2.

The updated Modernization Plan will be delivered and briefed at each scheduled PMR. The Government will provide the contractor with feedback and schedule updates on the proposed Modernization Plan within 30 days of the PMR. This feedback will illustrate the sequence and start dates of events based on the contractor’s provided durations of events. The contractor shall update and deliver the updated Modernization Plan within 14 calendar days of receipt of Government feedback. The plan shall support transition to full operational and modernized capability to meet the modernized requirements of the MSC NGW FO system within 3 years after initial task order start date.

The Government reserves the right to provide updates and approval of updates to the Modernization Plan based on evolving mission requirements.

6.3.3. Installation

The contractor shall install all CFE and equipment interfaces to Government-owned equipment in accordance with the below requirements.

6.3.3.1. Configuration Management

For all CFE located at the MDPs or fleet concentration area, 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 equipment. The contractor shall provide system and network configurations to the Government for the purpose of system fault isolation, troubleshooting, cybersecurity/data protection, network management/monitoring and system transition. Upon

Government acceptance of the network architecture, the contractor shall provide configuration management documentation in accordance with Appendix B.

6.3.3.2. Installation Design Plan (IDP) and As-Built Drawing Packages

The contractor shall prepare and deliver the IDP drawings in accordance with Appendix B. These drawings shall be delivered within 21 calendar days after initial task order start date. These drawings shall be in Adobe Acrobat or

AutoCAD 2016 or above, shall document the terrestrial architecture, to include the CFE and Government-owned equipment interfaces at all the CTs, MDPs or fleet concentration area, and shall be fully readable and editable.

Submit a minimum of two electronic copies and three paper copies of the Final As-Built drawings. All drawings shall be submitted on CD-ROM in AutoCAD and Adobe Acrobat format. The IDP shall be submitted to the

Government for submission in accordance with Appendix B in order to obtain proper 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, MDPs or fleet concentration area. The final As-Built Drawings shall be completed and delivered within 45 calendar days after MDP or fleet concentration area installation completion.

6.3.3.3. Installations

At the MDPs or fleet concentration area, the contractor shall install all CFE and equipment interfaces to

Government-owned equipment in accordance with Appendix B. The contractor shall be capable of new terminal installation requiring aluminum welding in accordance with Appendix D. 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.3.3.4. Equipment Refresh

At the Government’s direction, the contractor shall procure and employ newer technology or more efficient equipment. The contractor shall install, configure, operate, and maintain the equipment through the life of the contract. Equipment refreshes at the MDPs or fleet concentration area shall comply with all requirements listed under Section 6.3.3.3.

6.3.4. Maintenance

The contractor shall maintain all CFE and equipment interfaces to Government-owned equipment in accordance with the below requirements.

6.3.4.1. Maintenance, Repair, and Modernization

The contractor shall provide logistics and operations support in scheduling and conducting various required maintenance, repair, and modernization actions. As directed by the Government, the contractor shall perform all maintenance, repair, and upgrade of above and below deck equipment supporting the MSC network solution. The contractor shall be capable performing no less than three simultaneous break fix/ installation activities at fleet concentration areas globally. The contractor shall be captable 6 able of supporting 30-40 maintenance and/ or modernization actions year. Visitor Access Request for maintenance personnel shall be provided and kept current on file at MDPs.

6.3.5. Testing.

The contractor shall provide testing reports in support of validation and verification testing after maintenance, repair or upgrade of a vessel’s equipment.

6.3.5.1. Pre-Installation Testing

The contractor shall provide a pre-installation test report 21 calendar days after initial task order start date that validates system design, configuration and performance. The contractor shall conduct interoperability testing at the

Government designated test facilities. Testing shall include, but not be limited to, CFE configuration and operation and CFE interoperability with Government-owned equipment, and CFE/Government-owned equipment. Testing shall also include performance verification. The contractor shall demonstrate that End-to-End Service Requirements are within contract specifications. The contractor shall provide the necessary test equipment with performance results. To allow for adequate time and tests, testing shall be planned as a multi-day event. The test facilities will be identified by the Government during the Kick-Off meeting.

6.3.5.2. Post-Installation Systems Operational Verification and Test (SOVT)

The contractor shall conduct post-installation testing on leased lines between CT and the MDP in accordance with the SOVT. Testing shall include test results that meet OSI Model Layer 2 Ethernet criteria as described in section

6.1.3.2.1.

6.3.6. Network Operations Center (NOC) Requirements

The contractor shall staff their NOC with cleared Systems Operators and Engineers specially trained to monitor and troubleshoot satellite networks. The contractor’s NOC staff shall monitor the delivered spectrum to detect immediately any outages or indications of interference that might impact Government end-user operations. The contractor’s NOC staff shall be co-located with the NOC and provide support as the Tier 2 and 3 escalation points for issues from the NOC. Required skills at the NOC are as follows:

• Space and Teleport Engineering – is responsible for the proper operation of all satellite space segment, carriers and teleport. Tier 2 and 3 issues isolated to space, teleport or remote terminal equipment are escalated to the Space and Teleport Engineering group.

• Network Engineering – is responsible for all IP networking equipment at all locations including routers, switches, firewalls, Intrusion Detection System/Intrusion Prevention System (IDS/IPS), Virtual Private Network (VPN) equipment and terrestrial circuits. Tier 2 and 3 issues isolated to IP networking including routing/IP addressing and IP QoS are escalated to the Network Engineering group.

• Network Services Engineering – is responsible for operation of the contractor’s datacenter services including reporting and monitoring systems and VoIP services. Tier 2 and 3 issues related VoIP services are escalated to the Network Services Engineering group.

The contractor’s NOC staff shall utilize a trouble ticketing system to track issues to final resolution. The contractor shall employ systems in place for network monitoring, ticket management and tracking, scheduling, and material tracking.

6.3.6.1. Operations Support Requirements.

The contractor shall have English speaking technicians available 24 hours a day 7 days a week as the focal point for any problems encountered with the leased services. The technicians shall be able to troubleshoot or escalate to the next tier any problems encountered on the leased services. The contractor shall provide an overarching Operators’

Manual including standard operating procedures, points of contact, and the maintenance schedule which will include breakouts of maintenance activities performed by crew and activities performed by contractor.

6.3.7. Training

The contractor shall provide classroom and computer-based operations and maintenance training as required. The contractor’s hands-on classroom training shall utilize a lab environment designed to simulate real-world operational conditions and scenarios.

After each training, the contractor shall provide a Classroom Training Report that includes the following.

Man hours used

Daily activity report

Copies of all training documents

List of all students attending

Location of training visit

Copies of any certificates issued

6.3.7.1. Maintenance and Installation Training

The contractor shall provide shipboard hands-on systems operations and maintenance training immediately following each shipboard installation to ensure that shipboard personnel understand how to perform their duties with respect to the NGW system network

6.3.7.2. Operations Training

The contractor shall provide hands-on NOC systems operations and maintenance training immediately following each NOC installation to ensure that NOC personnel understand how to perform their duties with respect to the

NGW system network. The contractor shall provide both operator and train-the-trainer training on an as needed basis for NOC operations and maintenance.

6.3.7.3. Web Portal Training

The contractor shall provide training to Network Security Operations Center (NSOC) and TAC personnel to ensure complete understanding of web portal processes and procedures uniquely established to support NGW FO.

6.3.8. Monitoring and Situational Awareness Web Portal

The contractor shall have continuous, uninterrupted, near real time transparency via a monitoring and situational awareness portal.

6.3.8.1.

The Contractor shall provide a portal accessible to the Contracting Officer’s Representative (COR) and MSC Planners and Technical Team via Hyper Text Transfer Protocol with Secure Sockets Layer (HTTPS).