CS2 FO RFP Sec J Attachment J-10_Final.pdf

QTA-010-CTA-0003

ATTACHMENT J-10

Sample Task Order (STO) #2 - GOVERNMENT EDUCATION AND TRAINING

NETWORK (GETN)

1 GETN BACKGROUND

1.1 The Government Education and Training Network (GETN) is a network of Federal Government agencies using a common satellite carrier1 for interactive standard definition television (1-way video, 2-way audio). The existing Distance Learning Training System (DLTS) for GETN currently supports 12 agencies to provide training to over 2,200 fixed-dish2 downlink sites located throughout the CONUS, Alaska, Hawaii, Virgin Islands and Puerto Rico. GETN meets a wide variety of training & education needs, supporting these agencies in offering courses in subjects such as contract law, acquisition management, environmental law, hazardous waste management, air pollution, safeguards & security, aircraft maintenance, professional military education, professional continuing education, communication courses, air traffic control, equal opportunity training, medical continuing education, terrorism response, veteran health issues, management, and leadership.

1.2 For the encoding and decoding of satellite signals at their remote classroom sites, two standards are currently in use: Digital Video Broadcast – Moving Picture Experts Group (DVB-MPEG 2) for National Television System Committee (NTSC) output, and DVB-S2-MPEG 4 for Internet Protocol (IP) output3. User agencies currently use Scientific Atlanta’s PowerVu series of encoders4 and decoders.

Several agencies have already begun migrating their DVB-S1 system to DVB-S2.

Video is typically broadcast at a rate of 1.5 Mbps, and data throughput may reach 6 Mbps. Some agencies reduce required bandwidth per channel by using multiple channels per carrier (MCPC) technology. To provide the above capabilities, the current system requires 32MHz of dedicated bandwidth. The audio return path from the remote classrooms to the broadcast studio is currently implemented using a wireline- link, and is satisfied under separate contracts.

1.3 Uplinks are capable of being remotely operated from a central Network Operations Center (NOC) by the service provider. Through a conditional access management system (CAMS), downlinks are capable of remote activation by the same NOC.

The NOC provides toll-free help lines for each Federal Government Agency user experiencing technical problems during broadcasts, and the NOC is able to respond immediately to troubleshooting problems during a broadcast.

Ku-band frequency

Sizes range from 1.8m to 2.4m. Dishes are various makes/models configured to receive-only (RO).

IP used for both packetized video and data transport

PowerVu & PowerVu Plus encoders, and IRDs: 9235, 9234, 0934, 9865. The PowerVu Command Center 2000 is being used for management of the GETN system.

1.4 The CAMS includes a provision for the forced tuning of downlinks and receive sites. A downlink may service more than one receive site through the use of multiple integrated receiver decoders (IRDs) at that downlink. The service provider has the capability to remotely activate and deactivate downlinks to ensure downlink sites receive only the broadcast they are authorized to receive.

1.5 To receive a broadcast, a downlink site is authorized to receive that broadcast by the agency controlling the site. A receive site must receive only the broadcast for which it has been authorized and no other broadcast.

1.6 The CAMS allows for any agency to centrally control the scheduling of its own downlinks as a group and any number of subgroups as needed within 24 hours of broadcast, without penalty. CAMS also allows for on-the-spot addition of sites to any reception group.

1.7 The CAMS is able to group for reception any number of specified downlinks from any number of agencies to receive programming from one or more uplinks in the GETN community.

1.8 Additionally, the capability of the uplink locations to control the downlinks is included in the technical solution. This allows uplink locations to activate and deactivate receive site IRDs without going through the NOC.

1.9 The existing service provider is able to operate and conduct remote diagnostics on the satellite uplink equipment. Uplinks are controlled from the central Network Operations Center (NOC) to include forced tuning of downlink receive sites. The NOC has the capability of ensuring that downlink sites receive only the broadcast they are authorized to receive. Government users are provided a centralized capability that is accessible through the Internet to schedule bandwidth.

2 GETN REQUIREMENTS

2.1 A requirement exists for the Contractor to provide a continuing training capability for the existing GETN organization. Starting with the current system capabilities as a baseline, it is required that the Contractor develop, install, and maintain a satellite-based Modernized Distance Learning System (MDLS). Each Federal Agency currently has one or more broadcast studios with an installed set of equipment, and each studio has the capability of producing multiple broadcasts at any time. Instructors must have the ability to transmit video and audio of live courses to the remote sites and receive audio from remote sites (currently, the return audio is received by wireline services under various contracts). Although each agency typically conducts courses internally, the system shall also support the capability of any agency to provide broadcasts to any number of sites belonging to other GETN user agencies. The Contractor shall provide a home channel 24 x 7 that will be viewed by all GETN downlink receive sites when not viewing agency broadcasts.

2.2 Performance will take place at the Contractor’s facilities (CONUS), Government facilities within CONUS including Alaska, Hawaii, Puerto Rico and Virgin Islands.

The base period of performance shall be for three (3) years with two one (1) year option periods for a possible total period of performance of 5 years.

2.3 This effort shall require a solution to requirements as part of the following documentation:

2.3.1 Service Plan - A Service Plan, in accordance with Section C, is required for this initiative. As part of your plan, provide a description of the Systems, Procedures and Performance Metrics which you propose to put in place to assure successful and timely completion of the Task. Additionally, include a description of the process(es) which you as the Contractor will use to interface with the appropriate Government Representative(s), select/partition work among your subcontractors (as applicable), monitor/control cost and the work of your subcontractors (as applicable) and assure timely/complete submission of Task Order Invoices. Your Service Plan shall address all risks and resultant mitigation plans associated with your MDLS solution.

2.3.2 GETN Communications Infrastructure - Develop and implement the requisite communications infrastructure to support the GETN mission. Identify chosen systems and explain rationale for selection including life cycle cost considerations. Provide a detailed architecture and explain operation and performance of 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 NOC shall provide direct interface and reports to GETN Network Operations staff. 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’s solution shall address reliability, availability, maintainability, and security.

2.4 The GETN Communications Infrastructure shall incorporate the following at a minimum:

2.4.1 Audio and Video Support - Video and audio shall be broadcast over satellite from agency uplink broadcast centers to remote downlink receive sites. Using the current return audio solution via wireline as a baseline, capabilities to provide or migrate individual agencies to a 2-way audio over satellite system shall be proposed. The Contractor shall clearly identify and provide all equipment and software required to fully implement the proposed capability.

2.4.2 Anticipated Usage Profiles - Anticipated typical usage profiles for organizations supported by GETN are listed in Table J-10.1. Actual usage demands may differ.

Table J-10.1: Anticipated Usage Profiles (Typical Day) Organization Anticipated

Typical Peak Usage

Anticipated Typical Off-Peak Usage

AF M-F, 6-18 hours/day None ANG M-F, 3-6 hours/day Sat/Sun, 6-14 hours/day

ARNG M-F, 3-6 hours/day Sat/Sun, 6-14 hours/day DOJ M-F, 1-6 hours/day None FAA M-F, 3-8 hours/day None

USF&W M-F, 2-5 hours/day None NPS M-F, 4-8 hours/day None

US Courts M-F, 1-4 hours/day None DLA M-F, 2-7 hours/day None FBI M-F, 3-12 hours/day Sat/Sun, 1-4 hours/day DOE M-F, 1-8 hours/day None USN M-F, 1-8 hours/day None

2.4.3 Digital Compression - The Contractor shall explain how the MDLS will employ digital compression to minimize bandwidth usage.

2.4.4 Scheduling Management System (SMS) - The Contractor shall propose a centrally located SMS which is to be used by Federal Agencies to schedule training broadcasts. The SMS shall also incorporate security mechanisms to ensure that only authorized agency representatives can schedule or view a specific training session. The SMS shall allow each Agency to schedule training course broadcasts between 24 hours and 18 months prior to the start of the session. The SMS shall allow each Agency to delete broadcasts at any time.

The SMS shall allow each agency to add additional receive sites ad-hoc. When reservations are made, the system shall immediately provide email confirmation to the using agency.

2.4.5 Availability - The MDLS shall have a system availability of at least 99.5%.

2.4.6 Billing System - The Contractor shall provide a billing system that allows direct billing to each Federal Agency for services used.

2.4.7 FISMA Compliance - The Contractor shall demonstrate the ability to comply with the Federal Information Security Management Act (FISMA) of 2002 as implemented by Federal Information Processing Standards Publication 200 (FIPS 200), “Minimum Security Requirements for Federal Information and Information Systems and Organizations” for a low impact information system specifically addressing the following controls: AC-17, CP-9 and IR-5. Regarding CP-9, the Agency specification for backups is at least daily incremental and weekly full. The Contractor shall demonstrate the ability comply with Committee on National Security Systems Policy (CNSSP) 12, to the maximum extent practicable. See attachment J-3 for additional details on Information Assurance.

2.4.8 Bandwidth Access - The system shall be designed such that a minimum of 7 courses can be conducted simultaneously during typical peak usage periods and a minimum of 2 courses during typical off-peak usage periods. The Contractor shall assess scheduling algorithm alternatives versus the cost of bandwidth and propose a recommendation covering instances where additional simultaneous sessions are requested (e.g. block or schedule using ad-hoc bandwidth) that maximizes system capabilities while minimizing typical monthly costs.

2.4.9 Site Locations - A file containing the locations of sites and organizational assignments is included as Section J, Attachment J-11. The contractor shall provide a portability plan for relocation of any broadcast uplink and associated downlink receive sites to other teleports or satellites within the current regions, in the event an Agency has the need to relocate.

2.5 Engineering Support - Contractor shall engineer the GETN communications architecture, including capacity planning and preparing and developing designs, plans, and reports. Contractor shall implement configuration management, prepare engineering documents and reference manuals, and provide engineering, installation, configuration and testing services for the GETN communications infrastructure. The Contractor is encouraged to use non-proprietary solutions when possible.

2.6 Sustainment - Contractor shall implement and execute logistics, fielding, training, and O&M support. A phased approach can be considered. The sustainment concept must take into account any existing sustainment capabilities/strategies using both COTS and GOTS. The Contractor shall provide an approach for full lifecycle management.

2.6.1 Integrated Logistics Support - Develop and implement a maintenance and supply concept necessary to insure the order, receipt, delivery and accountability of systems required materials necessary to support delivery of the project within the schedule identified by the Government. Logistics support shall include all hardware/software elements and ancillary items necessary for maintaining an operational schedule. The Contractor shall use available commercial and other materials to the maximum extent possible.

2.6.2 Training – Provide training to downlink managers of newly installed receive sites and to agency uplink engineers for any newly purchased equipment or service.

2.6.3 Operations and Maintenance - Provide qualified technical support for the duration of the task’s period of performance. Maintenance support shall include the replacement of defective components, upgrades to include COTS technology insertion, and any software updates, as required. The maximum allowed time to replace defective components from the time it is reported or diagnosed is 24 hours, with critical spare components located onsite. Operations support includes 24/7 NOC support. The Contractor shall address the ability to identify and resolve EMI/RFI issues as the Government places a high priority on training since this impacts operational mission capabilities.

2.6.4 Migration Plan - The Contractor shall clearly articulate its migration plan for providing encrypted, compressed digital satellite service for the Federal Government. This solution shall clearly outline a detailed migration plan for existing system components to a technologically current solution, including costs and milestones. The Contractor should reference lessons learned when possible.

2.6.5 Recovery Plan - Provide a recovery plan to describe the process and timeline in the event that the communications path being used by the Contractor suffers any failure that disrupts service to Federal Government users.

2.7 Delivery Schedule - The Contractor shall implement the core architecture and transition at least the Air Force users (see Section J, Attachment J-11) to the MDLS within the standard 30 day delivery schedule. All agencies shall be transitioned within 4 months.

2.8 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.8.1 Commercial satellite communications infrastructure per unit cost. For space segment pricing, proposals shall include monthly recurring pricing (on a per year basis) in 0.5 and 1 MHz increments as applicable.

2.8.2 Network operations center (NOC) operations cost

2.8.3 Gateway Site terminal cost

2.8.4 Remote Site terminals cost per unit

2.8.5 Engineering Support cost per month

2.8.6 Sustainment support cost per month

2.8.7 Travel can be charged as ODC and is not required as part of the STO pricing.

(END OF ATTACHMENT J-10)