HC101320R0014 AMD03.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83)

Prescribed by GSA

FAR (48 CFR) 53.243

a. The purpose of this amendment is to provide additional Questions and Answ ers and to incorporate subsequent changes back the RFP as a result.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 53

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 26-May-2021

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X HC101320R0014

X 9B. DATED (SEE ITEM 11)

06-Apr-2021

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

26-May-2021

CODE

DISA/DITCO-SCOTT

2300 EAST DRIVE

BLDG 3600

SCOTT AFB IL 62225-5406

HC1013 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

HC101320R0014

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

MSC NGW FO PWS

COMMERCIAL SATELLITE COMMUNICATIONS (COMSATCOM)

PERFORMANCE WORK STATEMENT (PWS)

Satellite Business Solutions (SBS)

SBS0026

As of May 25, 2021

Contract Number: To be completed at time of award

Task Order Number: To be completed at time of award

Contractor Name To be completed at time of award

Tracking Number: SBS0026

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 indefinite delivery, indefinite quantity (IDIQ) vehicle is to sustain existing KU and

L band equipment and services pending modernization of the NGW satellite communications network supporting

MSC. It is MSC’s objective to leverage the most effective blend of commercially available shared and dedicated services, regardless of frequency, 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 (VoIP) 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. Coverage for Sustainment

Managed Services shall be Ku-Band as stated in PWS

; coverage for Modernized Service does not require Ku-Band as stated in PWS 6.2.2. The band required for coverage for Modernization (PWS 6.2.2) is dependent on the modernization equipment provided in PWS 6.2.2. 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 Attachment 3, Primary and Transit Area Concentrations.

Note: Coordinate Bounds are the requirement. A map is provided in Appendix A, Technical Specification for visual reference only. Government understands existing or future satellite coverage areas may exceed the required coverage areas.

Region Coordinate Bounds

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.32, Lon: 72.42)

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

46.22 -68.10

39.16 -77.44

29.67 -82.93

25.82 -75.84

Primary 9

49.53 -136.59

30.10 -163.80

44.93 160.75

14.98 161.05

15.03 -157.94

28.27 -121.9

Table 1 Primary Regions of Operation

6.1.2.2. Transit Regions

The contractor shall support routes within the boundaries defined below . Coverage for Sustainment Managed

Services shall be Ku-Band as stated in PWS 6.2.1; coverage for Modernized Service does not require Ku-Band as stated in PWS 6.2.2. The band required for coverage for Modernization (PWS 6.2.2) is dependent on the modernization equipment provided in PWS 6.2.2. The contractor shall support routes with continuous coverage between the Primary Regions of Operation. Note: Coordinate Bounds are the requirement. A map is provided in

Appendix A: Technical Specification for visual reference only

- 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 1, 7, and 8.

Region Coordinate Bounds

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

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 70 degrees

North and 70 degrees South. Coverage for Sustainment Managed Services shall be L-Band as stated in PWS 6.2.1;

coverage for Modernized Service does not require L-Band as stated in PWS 6.2.2. The band required for coverage for Modernization (PWS 6.2.2) is dependent on the modernization equipment provided in PWS 6.2.2.

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. When utilizing a geosynchronous satellite, satellite must be station-kept. When proposing MEO or

LEO satellites, constellation must demonstrate persistent coverage of the required location / area." The Government will not accept inclined orbit satellites.

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 Contractor 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:

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.

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.

Terrestrial Segment:

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.

End-to-end latency: Less than or equal to 1.2 seconds, one way.

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.

Terrestrial jitter:

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

Figure 1 – End-to-End Operational Availability

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

o Downtime is defined as the amount of time the service is not operational, which includes services that do not meet the 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. This includes equipment failures within the end-to-end. 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, ship unavailability, repair technician travel, or beam transition for mobile platforms.

When the government utilizes a MILSATCOM service, then the contractor is not responsible for meeting the up time/down time requirements, but is still responsible for maintenance and repair actions of above and below deck satellite equipment integrated with the shipboard NGW network.

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. Access shall be provided via the MDPs designated in 6.1.4.2.2. 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 (ACM), Adaptive TMDA (A-TDMA) protocol, and Direct Sequence Spread Spectrum (DSSS) 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.

The total number of ships in the MSC fleet is 105 with an anticipated 65 portable SATCOM systems. The backhaul should be sized to support all end users and allow for future growth of the MSC fleet. The terrestrial backhaul

CLINs are broken out to cover an aggregate cost per region. Attachment 3 – Primary and Transit Area

Concentrations has been provided as estimate of typical fleet concentration; but operations may require more or less ships in any given region at any time.

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, defined as from the commercial teleport to the MDP.

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 ensuring no gap in service.

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 circuits unless otherwise stated by the

Government at initial request. The contractor shall ultimately size each MDP to support approximately 170 additional modernized 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. Notional Lab and Shipboard connection diagrams listed in Appendix A, Technical

Specification.

Depending on specific mission requirements, the Government may require 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 70 degrees North and 70 degrees South. Sustainment managed services shall remain until such time as modernization efforts occur for each platform ashore and afloat.

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

This section is in reference to the current capability to be sustained before, and during, modernization efforts.

At a minimum, the contractor’s solution shall support the specified full duplex symmetrical CIR, as defined below in kilobits per second (kbps), 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.

An estimated number of terminals is included for planning, but does not limit the Government’s ability to operate terminals in any given region; this estimate includes terminals described in PWS 6.2.1.1.5 and 6.2.1.1.6.

Region CIR MIR Estimated # of Terminals

Primary 1 1024kbps 2048 kbps 10

Primary 2 1024 kbps 2048 kbps 14

Primary 3 1024 kbps 2048 kbps 10

Primary 4 (exclusive of Primary 4A) 1024 kbps 2048 kbps 10

Primary 4A (exclusive of Primary 4) 1024 kbps 2048 kbps 14

Primary 5 1024 kbps 2048 kbps 12

Primary 6 512 kbps 1024 kbps 28

Primary 7 512 kbps 1024 kbps 18

Primary 8 512 kbps 1024 kbps 32

Primary 9 512 kbps 2048 kbps 8

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. An estimated number of terminals is included for planning, but does not limit the Government’s ability to operate terminals in any given region; this estimate includes terminals described in PWS 6.2.1.1.5 and 6.2.1.1.6.

Region CIR MIR Estimated # of Terminals

Transit 1 512 kbps 1024 6

Transit 2 512 kbps 1024 8

Table 4 Transit Regions Service Level Requirements

6.2.1.1.4. Global Services

At a minimum, the contractor shall support secondary, L- Band, 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. The contract shall also provide L-band Voice, and

Integrated Services Digital Network (ISDN) services to support 3.1 kHz services.

The switching between Ku and L band will be automatic and should appear as seamless as possible to the end-users on the ships.

6.2.1.1.5. Military Sealift Operation Center (MSOC) Services

The contractor shall provide service for at least two MSOCs, currently located in the Far East/ Eastern Asian region but capable of deploying globally. The contractor’s service must support dedicated data rates specified for the operating region 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 and configuration support to all terminals supporting MSC, including government small form Carry-On SATCOM capability to the extent detailed in Appendix A, listed as Terminal 3.

Configuration support includes providing option files, IP configurations, and any documentation supporting the

Transmission Plan. MSC shall be responsible for storage of equipment and associated spares listed as Terminal 3.

The contractor’s service must support dedicated data rates of 4Mbps Downlink x 2Mbps Uplink and compatible equipment described in Appendix A, Technical Specification, and not be locked to a single satellite.

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.

There is no Radar Cross Section requirement for radomes or antenna. 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. Contractor 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 SLM-5650Bmodems by encrypting 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 ability for MSC to purchase and install small ship, medium ship, and large ship weight class variants of an X-Band antenna. If exercised, the X-Band antenna must be integrated with the rest of the vendor provided NGW modernization systems.

The Government will not accept X-Band antennas that are not WGS Certified. The government will not sponsor WGS Certification for the X band antennas.

Location of X-band antenna will vary based on the ship class. X-band blockage and safety zones have not been established. A site survey and topside study are required to determine the exact antenna location and permissible exposure limits. ABS approval is required prior to installation. The contractor is responsible to develop deck integration documentation and drawings and submit to MSC. MSC will assist in obtaining final approval from ABS.

Maintenance, repair, and life cycle support of the hardware associated with the provided systems extends to any antennas integrated with those systems. SATCOM Service and operations of the X-Band antennas will be the responsibility of the Government.

If this option is exercised by the government, the X-Band antennas must be integrated with the rest of the vendor provided NGW modernization systems. Maintenance, repair, and life cycle support of the hardware associated with the provided systems extends to any antennas integrated with those systems. SATCOM Service and operations of the X-Band antennas will be the responsibility of the Government.

6.2.2.1.1. Above Deck Equipment

The government requires several options, as the number of antennas for each weight class is significantly based on the modernization plan proposed by the contractor. The below weight classes represent the maximum weights for any class provided by the contractor. The Contractor shall be allowed to place any antenna configuration on any class as long as it does not exceed weight requirements and meets the throughput and service requirements for all ships. Terminals that are multi-band capable are acceptable, but to ensure redundancy multiple antennas are still required.

Where contractor provides small ship weight class antenna solution:

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.

Where contractor provides medium ship weight class antenna solution:

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.

Where contractor provides large ship weight class solution:

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.

These weight class categories are provided as description only, and do not specify required weight classes. The contractor shall provide antenna options that conform to the weight classes, provided the throughput requirements outlined in PWS 6.2.2.3 are met. Physical size/weight, RF and operational minimum performance is based on the modernization plan as provided; regardless of capability, no antenna can exceed the above specified weight class limits.

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.

The GFE SLM 5650B modems referenced in Attachment 6, Technical Specification must fit within the 12 RUs.

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 to provide better global satellite coverage and data rates

6.2.2.3. Modernized Services

Once modernized equipment is installed and integrated, the contractor shall provide primary and secondary VoIP and data 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 contractor shall provide services to allow remotes to dynamically maintain or exceed throughput requirements through means such as Adaptive Coding and Modulation (ACM), Adaptive TMDA (A-TDMA) protocol, and Direct Sequence

Spread Spectrum (DSSS).

6.2.2.3.1. Primary Region Modernized Service Level Requirements

At a minimum, the contractor’s solution shall support CIR of 4 Mbps Forward Link and 2 Mbps Return Link, per ship, over the entirety of the Primary Operating Regions defined in PWS section 6.1.2.1, to each modernized terminal. All remotes allocated to a network within a Primary Operating Region shall be capable of operating at their allocated CIR simultaneously.

The Government may permit networks of smaller sizes at the task order level based on specific operational requirements. An estimated number of terminals is included in Table 5 for planning, but does not limit the

Government’s ability to operate terminals in any given region; this estimate includes terminals described in PWS

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

6.5.1.

Region Estimated # of Terminals

Primary 1 10

Primary 2 14

Primary 3 10

Primary 4 (exclusive of Primary 4A) 10

Primary 4A (exclusive of Primary 4) 14

Primary 5 12

Primary 6 28

Primary 7 18

Primary 8 32

Primary 9 8

Table 5 Primary Regions Terminals Estimate

6.2.2.3.2. Transit Region Modernized Service Level Requirements

At a minimum, the primary communications service link shall support 4 Mbps Forward Link and 2 Mbps Return

Link 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. An estimated number of terminals is included in Table 6 for planning, but does not limit the Government’s ability to operate terminals in any given region; this estimate includes terminals described in PWS 6.2.2.3.4. The Government reserves the right to request data rate adjustments within the timeframe referenced in 6.5.1.

Region Estimated # of Terminals

Transit 1 6

Transit 2 8

Table 6 Transit Regions Terminal Estimate

6.2.2.3.3. Global Modernized Service Level Requirements

At a minimum, the contractor shall support secondary global satellite communications (as defined in PWS 6.1.2.3) managed services when outside of the above Primary and Transit Regions. The secondary communications service shall enable, at a minimum, each MSC asset to operate at 512 kbps with 95% coverage between 70 degrees North and 70 degrees South.

Requirement Minimum Threshold: 512 Kbps

Requirement Optional Threshold: 1024 Kbps

6.2.2.3.4. Ashore and Afloat Carry-On SATCOM Capabilities

The contractor shall provide approximately 65 units (in addition to the 105 Fleet SATCOM systems) of small form factor, Carry-On SATCOM capability with at least two Megabits per second (Mbps) forward link and one mbps return link. The Carry-On SATCOM capability shall support ashore activities and afloat vessels. The contractor shall be responsible for storage and maintenance of Carry-On SATCOM and associated spares; upon request, Ashore and Afloat Carry-on SATCOM terminals shall be delivered from storage to the Government within 96 hours. The Government will accept delivery of the terminals at Naval Base San Diego, California, Naval Station

Norfolk, Virginia, or Charleston Naval Shipyard, South Carolina.

The contractor shall provide service and configuration support to all terminals supporting MSC, including Ashore and Afloat Carry-On SATCOM terminals.

The Carry-On SATCOM terminal may be utilized in a variety of environments including land-based use and a variety of different ships. The Government will accept terminals with increased capability and mounting options but it is not required. The Government will accept Power-over-Ethernet (POE) but it is not required.

Once the Government receives and accepts the Carry-On SATCOM Capability terminals they become government property. However, as is required for the shipboard systems, the contractor is still required to perform maintenance and fix-actions on the equipment as part of the contract.

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 options for utilizing future constellations and services or options to purchase additional equipment. The future “To Be Negotiated”

CLINs shall remain within the contract scope of the MSC NGW FO requirement and will be considered logical follow-on work and will be based on the modernization solution provided by the contractor. The timeline is not prescribed per year, however it is specified by capability and maximizing upgrade potential based on capabilities provided. Upon execution of these optional services, link budgets, coverage maps, draft Transmission Plans, a transition plan for the re-configuration of the services, and updates to the CIAQ shall also be included and will be subject to AO approval and acceptance.

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 without gaps in service. 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 contractor shall provide a draft Transition Support Plan with their proposal. 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 each individual end user circuits with no more than 30 minutes of downtime to each of the end users during this one-time transition between vendors. 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 contractor shall develop a plan for contract transition from their services to another entity to support follow on service requirements 90 days prior to conclusion of the contract to meet sustainment service requirements without gaps in service.

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

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 plan should be developed with the assumption that twenty percent of the fleet (approximately 21 ships) will be available for modernization upgrades and installation per year. The contractor will not be held to the

30-minute downtime requirement during installation of modernized equipment.

The 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 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 for modernization.

Once MSC receives and accepts new equipment from the contractor, it becomes government property. The only

CFE the Government expects to remain CFE after equipment delivery will be the terrestrial connections at the MDP.

6.3.3.1. Configuration Management

For all CFE located at the MDPs the contractor shall provide, within 14 calendar days after individual task order start date, configuration management documentation which includes the Integrated Logistics Support Plan (ILSP), in format consistent to industry best practices. 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 existing As-Built drawings will be provided to the contractor when the contract is awarded. The contractor shall prepare and deliver the IDP drawings in accordance with Appendix B. These drawings shall include:

Block Wiring Diagram (BWD)

List of Connections

Arrangement Modifications Drawings

Topside Arrangement Modification Drawings

Fabrication Details

Installation Control Drawings (ICD)

Additional drawings for Antenna Underdeck Support may be required for aluminum vessels (T-EPF/HST).

Drawings shall be defined by ship class. All drawings will be developed to American Bureau of Shipping (ABS) rules for Building and Classing of Steel and High Speed Naval Craft standards. The Contractor will not be required to write the TRANSALT and Work Item for MSC; the contractor shall provide support to MSC in preparing any documentation for the TRANSALT. MSC and ABS will review all drawings and provide final approval within 12 months. ABS approval will be required for each drawing package.

These drawings shall be delivered within 21 calendar days after individual task order start date. These drawings shall be in Adobe Acrobat and AutoCAD 2016 or above, shall document the terrestrial architecture, to include the

CFE and Government-owned equipment interfaces at all the CTs, MDPs 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. The final As-Built Drawings shall be completed and delivered within 45 calendar days after MDP installation completion.

6.3.3.3. Installations

At the MDPs 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 both steel and aluminum welding in accordance with Appendix D. A ship survey will be required prior to any modernization of the capabilities. The contractor may reuse existing racks as part of the installation plan. The contractor will be required to make structural modifications and hot work in accordance with approved TRANSALT requirements. The contractor shall:

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

Identify electrical power and/or HVAC requirements

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…