20100210_NGW_Section_J_Attachment_A_SOO_FINAL.doc

Attachment 1

MSC Funding profile

MILITARY SEALIFT COMMAND (MSC)

STATEMENT OF OBJECTIVES (SOO)

Version 3.0 Portfolio ID: 2.2.07005

NEXT GENERATION WIDEBAND (NGW)

1. PURPOSE

Military Sealift Command (MSC) intends to implement the Next Generation Wideband (NGW) system to replace the current MSC Afloat Bandwidth Efficient Satellite Transport (BEST) Commercial Satellite Communications (COMSATCOM) infrastructure.

2. SCOPE

The NGW system solution should provide:

a. End-to-end Internet Protocol (IP) communications pathway linking the globally deployed MSC ship and Mobile Sealift Operations Center (MSOC) van-based voice and data networks to the MSC primary and backup Point of Presence (POP) Network Operations Centers (NOC) located in San Diego, CA, and Pensacola, FL. The pathway includes space segment services and associated Land Earth Station (LES) infrastructure, shipboard terminal hardware, supporting software, and terrestrial backhaul infrastructure connecting the LES infrastructure with the MSC NOCs.

b. Support for seamless transition from existing BEST system to future NGW solution.

c. Worldwide installation services.

d. Worldwide sustainment services.

e. Process for the integration of changes such as parts obsolescence and technology upgrades/enhancements.

3. Period of performance

The period of performance includes a four-year base period plus four 1-year option periods.

4. Background

The BEST system has provided MSC with robust service connectivity for voice, data, and imagery, both secure and non-secure, for both classified and unclassified missions. More than 70 MSC vessels currently have their voice and data networks connected to the MSC Ashore Enterprise via the BEST Wide Area Network (WAN) Satellite Communications (SATCOM) infrastructure. This acquisition is necessitated by BEST infrastructure end-of-lifecycle and capacity shortfall factors.

5. PERFORMANCE OBJECTIVES

The NGW system solution set should meet the following performance objectives:

f. Offers per-ship voice and data communications capacity in an efficient and cost-effective manner to optimize:

i. Service availability and Quality of Service (QoS).

ii. Total primary Committed Information Rate (CIR) and secondary Burstable Information Rate (BIR) bandwidth available to each ship. The preferred per-ship CIR is 64 Kbps (symmetric), ideally providing assured access without contention, whether during session initiation or information transfer. The preferred per-ship minimum for BIR is 256 Kbps downlink/128 Kbps uplink. MSC desires to maximize the amount of BIR bandwidth available within current budget.

iii. The ability to multicast large data packages (estimated maximum size of 500MB) to the fleet (e.g., software updates/patches/service packs).

iv. Worldwide coverage area with emphasis on the ship concentration areas (see section 6.8), commercial sea routes, and areas of publicly disclosed major Naval operations. Land mass coverage is littoral with the exception of the MSOC vans which operate inland occasionally (98% littoral, 2% inland). Best effort coverage provided in all other regions in such a way that performance and costs are optimized.

v. Service delivery, as necessary, to provide highest data rates in the aforementioned concentration areas (see section 6.8), commercial sea routes, areas of publicly disclosed major Naval operations, and land mass coverage where MSOC vans operate. Best effort service delivery provided in all other covered regions.

g. Maximizes flexibility to maintain full service across the MSC fleet as ship deployments change locations (i.e., portability).

h. Offers the means to acquire additional capacity to support unanticipated growth in fleet size or per-ship consumption (i.e., surge).

i. Offers the flexibility to expand or contract service levels and quantities as new budgets are realized in out-years.

j. Minimizes the role of shore and shipboard personnel in SATCOM sustainment activities. Special focus should be placed on minimizing activities associated with SATCOM coverage area and frequency band transitions.

k. Threshold number of platforms to be installed and supported within the first two years following award should be the 68 vessels, 10 MSOC vans, and 2 labs currently equipped with the BEST infrastructure. During the period of performance, 100 platforms may be potentially installed and supported.

l. The proposed solution should provide both operator and train-the-trainer NOC and ship operations and maintenance training on an as needed basis.

m. Provide shipboard post-installation, hands-on systems operations and maintenance training.

n. Provide a configuration baseline that is a top-down breakdown description from the system level down to the Lowest Replaceable Unit (LRU) of the system.

6. Operating CONSTRAINTS The proposed solution shall comply with the following operating constraints.

6.1. Information Assurance

The proposed solution shall comply with all necessary Department of Defense (DoD) Information Assurance (IA) requirements as specified in this section:

o. The contractor shall provide transmission security (TRANSEC) over the satellite infrastructure links as specified by DoD Directive (DoDD) 8581.1, IA Policy for Space Systems Used by DoD (i.e., Federal Information Processing Standard (FIPS) 140-2 Level 2 Advanced Encryption Standard (AES)-2). Anti-jam TRANSEC capability is not required.

p. All satellite infrastructure devices (e.g., IP modems) that directly support the IP protocol suite shall be ports, protocols, and services-compliant as defined by DoD Instruction (DoDI) 8551.1, Ports, Protocols, and Services Management (PPSM).

q. The contractor shall ensure that the proposed LES infrastructure meets all administrative, operational, and physical security requirements in accordance with DoDI 8500.2, IA Implementation, for Mission Assurance Category (MAC) II.

r. The Government requires NGW contractor support to make the appropriate MAC and classification/sensitivity level (no higher than SECRET) determination consistent with DoDD 8500.01E and DoDI 8500.2.

s. The Government requires contractor support in the development of the DoD IA Certification and Accreditation Process (DIACAP) package be prepared and delivered to support the Certification and Accreditation (C&A) of the NGW capability consistent with DoDI 8510.01. The DIACAP package is to include: System Identification Package; DIACAP Implementation Plan; supporting certification documentation (IA control validation results, IA control artifacts); Information Technology (IT) security Plan of Action and Milestones (POA&M); and DIACAP scorecard.

t. The Government requires that the NGW solution meets all administrative, operational, and physical security requirements in accordance with the NGW DIACAP Implementation Plan and the DoDI 8500.2. This includes, but is not limited to, ensuring that all personnel have the required security clearances (no higher than SECRET), authorization, need-to-know, have been indoctrinated, and are familiar with the internal security practices of all proposed NGW facilities.

6.2. Service Characteristics

The proposed solution shall provide a centrally managed IP-over-satellite voice and data SATCOM solution for the MSC fleet as specified in this section:

u. Compatible with IP version 6 (DoD Chief Information Officer (CIO) Memorandum “IPv6, June 9, 2003”)

v. Compatible with the existing fixed IP addresses and subnetting assigned to the MSC NOCs and the MSC fleet/MSOC vans.

w. Centrally/automatically managed transition between satellite coverage areas.

x. Centrally managed per-ship CIR modification.

y. Centrally managed per-ship QoS modification. Note that QoS for Open Systems Interconnection (OSI) layers three through seven traffic is applied and managed by the MSC Expand Network IP Accelerator infrastructure as the accelerators tunnel this traffic through the SATCOM infrastructure. The tunnel end-points are Expand model 6840 accelerators located at the MSC NOCs and Expand model 4820 accelerators onboard the ships and MSOC vans.

z. Centrally managed SATCOM system status and performance monitoring. Minimum monitoring capability to include:

i. Alarm (audio/visual) upon link disconnect or major throughput degradation.

ii. Data transmission performance information (minimum/maximum/average throughput) system uptime statistics.

iii. Centrally managed configuration management (hardware and software).

aa. Provide the tools, equipment, and support services necessary for the MSC management and monitoring of the SATCOM infrastructure from primary and backup MSC NOCs.

ab. Support a minimum end-to-end (MSC NOC border/gateway router to MSC ship border/gateway router) system-wide service availability of 95% to include terrestrial circuits.

ac. Support a minimum SATCOM (LES modem to MSC ship modem) system-wide service availability of 97%.

6.3. NOC Interfaces

The proposed solution shall comply with the NOC interface requirements as specified in this section:

ad. Interconnect the proposed LES infrastructure and the NOCs with circuits meeting NOC building facility requirements for termination in effect at the time of installation.

ae. The proposed solution shall not support or provide any direct external commercial data interfaces to the fleet (i.e., Internet/World Wide Web connectivity). The only allowed external commercial data interfaces to the fleet shall be provided at the primary and backup NOCs by MSC.

af. At the NOCs, the proposed solution shall separate, via contractor-supplied equipment, the Voice over IP (VOIP) content of the IP data stream originating from the fleet and pass on the separated voice traffic to the existing NOC Mitel SX200 Private Branch Exchange (PBX) equipment (utilizing media and voice format compatible with the fleet-facing incoming and outgoing 24 voice channel T-1 PBX interface cards). The remaining non-VOIP IP fleet data traffic will be passed on, utilizing 10/100BaseT Ethernet, to the existing NOC gateway “ships” router (Cisco model 7603).

Conversely, voice traffic from the NOC PBX (destined for the fleet) shall be converted, via the same contractor-supplied equipment, into VOIP and combined with the fleet-destined IP traffic from the NOC “ships” router for subsequent transport to the fleet.

6.4. Ships

6.4.1. Physical Characteristics

ag. The terminal equipment shall comply with the physical requirements as specified in this section.

i. The MSC fleet has a standardized shipboard terminal mount (currently used for the existing BEST system), which is available for transformation into a mounting platform for the NGW Above Deck Equipment (ADE). Utilizing this mount will reduce/eliminate the need to conduct structural, blockage, and emitter interference analysis prior to ADE installation. ADE utilizing the existing mount shall comply with the following specifications:

· Dish radome equator diameter of 1.5 m or less.

· Dish (with integrated positioner, Radio Frequency (RF) equipment, and radome) shall not exceed a weight of 250 lbs.

ii. If the offeror determines that it is necessary to specify an additional (secondary) terminal to meet MSC NGW requirements then the same Below Deck Equipment (BDE) and ADE requirements that apply for the primary terminal will apply to the secondary terminal. However, it is the responsibility of the offeror to appropriately position the secondary terminal antenna on deck based on ship class information provided by MSC.

ah. The contractor shall provide a standalone Military Standard (MIL-STD)-167-1A vibration-compliant 19-inch rack for installation of the fleet SATCOM system BDE. Installation shall require the integration to the shipboard Local Area Network (LAN). This shall be accomplished in coordination with the designated MSC representative.

6.4.2. Interfaces

The terminal equipment shall meet the interface requirements as specified in this section.

ai. Shipboard power in accordance with Institute of Electrical and Electronic Engineers (IEEE) Std 45-2002.

aj. Grounding and bonding in accordance with MIL-STD-1310H.

ak. IP data (non-VOIP) via 10/100BaseT Ethernet to the ship Cisco IP gateway router.

al. VOIP conversion to 4 RJ-45/RJ-11 analog phone jacks for ship PBX/phone utilization.

6.5. MSOC Vans

The MSOC van consists of an International Organization for Standardization (ISO) shipping container equipped with the systems necessary to support its role as a mobile command and control operations center. As the position of the MSOC van is fixed during SATCOM terminal operation, there is no requirement for a stabilized satellite-tracking terminal platform.

6.5.1. Physical Characteristics

am. The terminal equipment shall comply with the physical requirements as specified in this section.

i. Portable fly-away antenna system requiring no more that two persons (utilizing muscle power only) for assembly and setup. The setup location will either be on the ground or on the roof of the MSOC van.

ii. Dish diameter of 1.8 m or less.

an. The contractor shall provide a standalone MIL-STD-167-1A vibration-compliant 19-inch rack for installation of the SATCOM system BDE. Installation shall require the integration to the MSOC van LAN. This shall be accomplished in coordination with the designated MSC representative.

6.5.2. Interfaces

The terminal equipment shall meet the interface requirements as specified in this section.

ao. IP data (non-VOIP) via 10/100BaseT Ethernet to the MSOC Cisco IP gateway router.

ap. VOIP conversion to 4 RJ-45/RJ-11 analog phone jacks for MSOC phone utilization.

6.6. Deployment/Installation

BEST system shipboard drawings and above-deck/below-deck space arrangement diagrams will be provided to aid in removal, installation, and deployment planning. The proposed NGW solution shall meet all applicable fleet removal, installation, and deployment requirements as specified in Section L. All installations on the BEST-equipped platforms shall be completed by end of calendar year 2012, with ships within the Mediterranean and Contiguous United States (CONUS) areas given preference for earliest installation.

6.7. Maintenance

The proposed NGW solution shall meet all applicable fleet maintenance requirements as specified in this section.

aq. All contractor-provided equipment shall have a minimum 2-year warranty effective from System Operation Verification Test (SOVT)/Government acceptance.

ar. Organizational Level (O-level): Corrective maintenance is characterized by the use of both preventive maintenance procedures and corrective maintenance actions that provide for the rapid detection, localization, and isolation of failure to the defective LRU. Maintenance concept for repair of failures shall be the replacement of LRUs to restore the equipment to operational readiness. System Built-In Test (BIT) or online diagnostics shall be used to assist the maintainer with isolating failures. For LRUs located within the antenna radome, maintainer access is required to support at-sea repairs. If the antenna radome cannot be removed and easily secured by a single individual, an access hatch or panel shall be required to provide maintainer access. LRU removal and replacement procedures shall be included in the equipment technical manuals, as well as casualty restoration and system testing methods.

as. There shall be no preventive maintenance task for the system required more frequently than semi-annually (if it takes any equipment offline) and total preventive maintenance shall not exceed 6 man-hours annually.

at. Depot Level (D-level): Corrective maintenance consists of contractor field engineering services for maintenance beyond the O-level, or Intermediate Level (I-level) if proposed, for depot repair of defective LRUs, and for equipment overhaul as needed. During the warranty period, the contractor shall maintain required D-level maintenance personnel and materials to repair failed LRUs and for overhaul of components. Identification of the level of stock, repair components, and the maintenance of that inventory shall be the responsibility of the contractor.

6.8. MSC Global Coverage Area/Ports/Areas of Concentration

PAGE