CS2 RFP Sec J Attachment J-9_Amendment 05.pdf

QTA-010-CTA-0003

ATTACHMENT J-9

Sample Task Order (STO) #1 - MORALE, WELFARE, AND RECREATION

SERVICES (MWR)

1 MWR BACKGROUND

1.1 Historically, deployed service members kept in touch with their family and friends with a letter or an occasional telephone call. With the rapid expansion and availability of the Internet, e-mail is taking the place of these more traditional communication methods. Now, deployed service members will be provided high-speed commercial Internet access supporting communications applications, including e-mail, voice calls and video teleconferencing, to better keep in touch with family and friends.

1.2 The United States Government (USG) intends to provide IP Voice, Video, and Data services via multiple Very Small Aperture Terminal (VSAT) satellite networks to Department of Defense (DoD) and Partner Nation Elements throughout the world. USG requires satellite IP services to support Morale, Welfare, and Recreation (MWR) and other non-Global Information Grid (GIG) operations in the Central Command (CENTCOM), African Command (AFRICOM), European Command (EUCOM), and Pacific Command (PACOM) Areas of Responsibility (AORs), as well as the British Indian Ocean Trust (BIOT) Territory. This Sample Task addresses the general parameters and requirements to provide the required satellite IP services. The system shall be flexible and adaptable to service personnel in the regions cited above, including hostile locations.

2 MWR REQUIREMENTS. A requirement exists to provide an MWR system to support DoD in-theater operations. Include solutions to requirements as part of the following documentation:

2.1 Project Planning: The Contractor shall develop a Service Plan in accordance with Section C. The Service Plan should include a description of the systems, a network diagram, procedures and performance metrics to put in place to assure successful and timely completion of the Task, procedures explaining how subcontractors will be managed (if applicable), a description of how costs will be controlled, and a plan to ensure timely submission of invoices. Additionally, include a description of the process(es) that the Contractor will use to interface with the appropriate Government Representative(s). The Service Plan shall include a project implementation schedule. The Service Plan shall address all assumptions, risks and resultant mitigation plans associated with the proposed solution.

2.2 MWR Infrastructure: The Contractor shall develop and implement the requisite communications infrastructure to support the MWR mission. The Contractor shall select a solution which provides an optimum lifecycle cost-benefit ratio. Identify chosen systems and explain rationale for selection, including lifecycle cost considerations, incorporating lessons learned when possible. Provide a detailed architecture and explain all required interfaces. The Contractor shall provide link budgets, as applicable. A network operations center (NOC) shall be employed to manage connectivity and network assets for the period of performance. The Contractor’s solution shall address reliability, availability, maintainability, and security. The Contractor shall explain what network monitoring and status information will be provided to the Government on a recurring basis, how often it will be provided and in what format. The Contractor shall demonstrate the ability to comply with the Federal Information Security Management Act of 2002 as implemented by National Institute of Standards and Technology (NIST) Special Publication (SP) 800-53, “Recommended Security Controls for Federal Information Systems and Organizations” for a moderate impact information system, specifically addressing the following controls: CA-2, IA-2 and SI-3. Regarding CA- 2, a security assessment plan is not required prior to contract award. The Agency specification for assessment of security controls in the information system is that they must be assessed annually. Regarding IA-2, there is no Agency specification for Control Enhancement (8), so it is per contractor system determination.

Regarding SI-3, there is no Agency specification, so the values are per contractor system determination. The Contractor shall demonstrate the ability to comply with Committee on National Security Systems Policy (CNSSP) 12. See Section J, Attachment J-3 for additional details on Information Assurance.

2.3 Site Configuration and Locations: The MWR system consists of two types of Remote Deployable Units (RDUs). The RDUs shall be comprised of the equipment listed below plus transportable antenna, a temporary shelter with the workstation configurations listed below, 24-hour temporary power backup device plus other equipment the Contractor determines is required. All equipment shall be capable of being easily repacked and shipped by onsite Government personnel, and the overall MWR system shall be capable of supporting site redeployments, including areas outside the initial deployment regions. The contractor shall provide a portability plan for redeployment of sites to other regions in the event the government’s requirements for MWR change.

2.3.1 Large Remote Deployable Units (LRDUs) - Contains 8 VoIP phones, 20 laptop computers w/ webcams. 200 LRDUs are required to be shipped to Iraq, 150 LRDU’s to Afghanistan, 15 LRDUs to Poland, 10 LRDUs to Serbia, 12 LRDUs to Mali and 8 LRDUs to South Korea.

2.3.2 Outpost Remote Deployable units (ORDUs) - Contains 3 VoIP phones, 5 laptop computers w/ webcams. 30 ORDUs are required to be shipped to Iraq and 18 ORDU’s are required to be shipped to Afghanistan and 10 ORDUs shall be shipped to Bangladesh.

2.4 Engineering Support: The Contractor shall provide the results of MWR system engineering studies to provide a clearly explained recommendation for bandwidth and per-site Committed Information Rate (CIR) for each RDU, stating assumptions. The Contractor shall propose the method for implementing Quality of Service (QoS) to ensure prioritization of traffic (VOIP, video and data) categories. The Contractor shall engineer the MWR communications architecture, including capacity planning and preparing and developing designs, plans, and reports. The Contractor shall implement configuration management, prepare engineering documents and reference manuals, and provide engineering, installation, configuration and testing services for the MWR communications infrastructure. Requirements are expected to grow up to 20% over 3 years, and Contractor engineering studies shall articulate how system expansion can be accommodated at minimum costs and support other potential emerging methods for obtaining cost efficiencies. The Contractor is encouraged to suggest alternative, innovative approaches to achieve desired capabilities. The Offeror is encouraged to use non-proprietary solutions when possible.

2.5 Satellite Access: The Contractor shall provide USG with recommendations for which satellite to use for commercial satellite spectrum. The Contractor shall provide a satellite network availability of at least 99.7%. The Contractor shall propose additional metrics to confirm service levels. The availability will be calculated based on the number of satellite network availability minutes during any calendar month divided by the number of total minutes during the same month.

Periods of unavailability include unscheduled events such as network outages, rain fade, and network hardware/software failures. The 99.7% availability is for the entire network to the remote switch, excluding the VOIP phones and personal computers (local area network suite). The period of unavailability is measured across all sites.

2.6 Sustainment: The Contractor shall explain a plan to implement and execute logistics, fielding, training, and O&M support. A phased approach can be considered.

2.6.1 Integrated Logistics Support - Develop and implement a maintenance and supply concept necessary to ensure the order, receipt, delivery and accountability of materials necessary to support delivery of the project within the schedule and budget identified by the Government. Logistics support shall include all hardware/software elements and ancillary items necessary for maintaining an operational schedule.

2.6.2 Training - Explain the required operator and maintenance training plans and courses for the Government.

2.6.3 Operations and Maintenance - The Contractor shall provide qualified technical support for the duration of the task’s period of performance. Maintenance support shall include the replacement of defective components, onsite technical support, upgrades to include COTS technology insertion, and any software updates, as recommended by the Contractor engineering support. Operations support includes 24/7 NOC support. The NOC shall support site commissioning by Government personnel with a 4-hour notification period maximum.

2.6.4 EMI/RFI Identification and Resolution - Implement and support EMI/RFI identification and resolution procedures. The Contractor shall explain how EMI/RFI identification and resolution will be communicated to the Government.

The Government prefers the Contractor have access to media and voice communications capability capable of protecting “Sensitive, but Unclassified” data.

2.6.5 Network Monitoring - Establish, and provide the USG access to, a common Net Ops web portal to present the health of the entire solution in a consolidated view using data from multiple sources. The USG prefers the capability to receive alarms (e.g., interference, anomalies) in an automated way, vice a trouble ticket from an operations center.

2.6.5.1 NetOps metrics shall be collected, at a minimum, on the following network segments:

2.6.5.1.1 Gateway (e.g., Hub throughput, link latency, bit error rate, packet delay variation/jitter, service specific quality of service (QoS), packet loss, transmit power level, receive power level, signal-to-noise ratio (Eb/No), link status;

Gateway Terminal high power amplifier (HPA) status, Low Noise Amplifier (LNA) status, converter status, up convert (U/C) attenuator);

2.6.5.1.2 Satellite (e.g., anomalies likely to disrupt service, interference data, spectrum data); and

2.6.5.1.3 Remote (e.g., Remote Terminal HPA status, LNA status, converter status, U/C attenuator; Remote Modem transmit power level, receive power level, Eb/No, link status, throughput, link latency, bit error rate, jitter, service specific QoS, packet loss).

2.6.5.2 The Contractor shall recommend the Net Ops metrics to be collected for each network segment and explain their rationale for including those metrics. The Contractor shall specify the frequency of delivery, retrieval method, and data units (e.g., kbps, dB) and format (e.g., XML, SNMP trap) of each Net Ops metric selected.

2.7 Delivery Schedule: The Government desires that the ORDUs arrive in-country and be commissioned by Contractor personnel within 90 days, and that the LRDUs arrive in-country and be commissioned by Contractor personnel within 180 days.

2.8 Period of Performance: The Period of Performance for MWR is 3 base years, with two 1 year options.

2.9 Priced Line Items: At a minimum, pricing is required for the following line items.

The Contractor shall note if certain line items are not separately priced. All prices shall be fixed price.

2.9.1 Commercial satellite communications infrastructure (including satellite bandwidth and terrestrial connections) per unit cost – Africa per month

2.9.2 Commercial satellite communications infrastructure (including satellite bandwidth and terrestrial connections) per unit cost – Africa per year

2.9.3 Commercial satellite communications infrastructure (including satellite bandwidth and terrestrial connections) per unit cost – Southwest Asia / Middle East per month

2.9.4 Commercial satellite communications infrastructure (including satellite bandwidth and terrestrial connections) per unit cost – Southwest Asia / Middle East per year

2.9.5 Commercial satellite communications infrastructure (including satellite bandwidth and terrestrial connections) per unit cost – Central Asia per month

2.9.6 Commercial satellite communications infrastructure (including satellite bandwidth and terrestrial connections) per unit cost – Central Asia per year

2.9.7 Commercial satellite communications infrastructure (including satellite bandwidth and terrestrial connections) per unit cost – Pacific per month

2.9.8 Commercial satellite communications infrastructure (including satellite bandwidth and terrestrial connections) per unit cost – Pacific per year

2.9.9 Commercial satellite communications infrastructure (including satellite bandwidth and terrestrial connections) per unit cost – Europe per month

2.9.10 Commercial satellite communications infrastructure (including satellite bandwidth and terrestrial connections) per unit cost – Europe per year

2.9.11 Network operations center (NOC) operations cost

2.9.12 Gateway Site terminal cost

2.9.13 Remote Site terminals cost per unit

2.9.14 Engineering Support cost per month

2.9.15 Sustainment support cost per month (excluding Onsite Technical Support)

2.9.16 Onsite Technical Support – Africa per day

2.9.17 Onsite Technical Support – Southwest Asia / Middle East per day

2.9.18 Onsite Technical Support – Central Asia per day

2.9.19 Onsite Technical Support – Pacific per day

2.9.20 Onsite Technical Support – Europe per day

2.9.21 Travel can be charged as Other Direct Costs (ODC) and is not required as part of the STO pricing.

(END OF ATTACHMENT J-9)