Atch_3_SOW.pdf

Atch 3 SOW, FA5270-16-T-0051

FOR OFFICIAL USE ONLY

Statement of Work (SOW) for

Enhanced 911 System at

Kadena Air Force Base, Fire and Emergency Services

17 August, 2016

PR# F2H3A26167AC03

1. PURPOSE

1.1 Scope

This Statement of Work (SOW) provides for the purchase and installation of E911 Emergency Call

Taking Systems that include E911 Intelligent Workstations (IWS), Emergency Dispatch Positions and stand-alone Automatic Location Identification (ALI) databases. The system shall support calls from on base PBX wire-line extensions (TDM and VoIP), commercial wire-line (housing, on-base contractors, vendors, etc.), and commercial wireless sources. Call routing for call from commercial

(non-government) sources shall be based on the associated existing Emergency Service Number, automatically delivering the E911 call to the newly designated on-base Public Safety Answering

Point (PSAP). The system shall provide the direct delivery of E911 calls to a Department of

Defense (DoD) staffed PSAP without the need for intermediate call answering by the local civilian

PSAP.

Any modifications to this SOW must be authorized by a warranted Contracting Officer.

1.2 Objective

The objective of this SOW is to document the requirements to Engineer, Furnish, Install, and Test

(EFI&T) an E911 Emergency System for Kadena Air Force Base (AFB)

1.3 Background

Following the release on Nov 10 of “Air Force (AF) Follow-on Review; Protecting the Force:

Lessons Learned from Fort Hood,” the Secretary of the Air Force, Chief Information Officer

(SAF/CIO) A6 was appointed as the single Air Force office for ensuring Enhanced 911 (E911) technical policy conforms to DoD guidance. SAF/CIO A6 recently signed the Air Force Guidance

Memorandum (AFGM) to AFI 33-111, establishing the responsibilities and requirements for E911 services and emergency call routing IAW DoD guidance (DoDI 6055.17). The Air Force’s analysis and proposed response to its identified deficiencies was documented in its E911 Implementation

Plan (I-Plan). IAW with the SecDef’s directive, the AF HQ/SAF has funded an Air Force–wide

E911 program to address this critical deficiency. The objective of this program is to improve system reliability and interoperability by implementing a common platform throughout the USAF.

Owing to Congressionally mandated base realignments/reductions, the Government retains the right to remove any specific base from this contract.

2. PROGRAM REQUIREMENTS

2.1 Program Requirements

This is a turn-key installation wherein the Contractor shall EFI&T an Enhanced 911 solution at site identified in paragraph 2.2. The Contractor shall engineer, furnish, install, test and make operational newly installed equipment to OEM, industry and/or AF specifications with the appropriate vendor pass through licenses. The Contractor shall provide all hardware, software, licensing, and training required for the use of all systems and equipment installed under this SOW.

The overall objective is to upgrade the E911 infrastructure at Kadena AFB

Contractor shall clearly identify expected government labor, government furnished property (GFP) and allied support required to implement a fully functional solution. This paragraph is applicable to the solution(s) proposed under paragraph 4.

2.2 Place of Performance

The place of performance shall be at Kadena AFB, Okinawa Japan.

2.3 Performance Period

The Government desires delivery of all work to be accomplished within 180 days of contract award. If the Contractor is unable to meet the desired delivery schedule, it may, without prejudicing evaluation of its offer, propose a delivery schedule. However, the Contractor’s proposed delivery schedule must not extend the delivery period beyond 365 days of contract award. Any request or justification for change shall be made to the Contracting Officer in writing and must be approved by the Contracting Officer.

2.4 Joint Interoperability Test Center Approved Product List

The Contractor’s solution(s) shall be on the JITC-certified Approved Product List (APL). The systems shall meet interoperability requirements of the JITC to ensure interface with commercial and military interface standards. Operating Systems and applications shall be configured in accordance with Security Technical Implementation Guides (STIGs). Contractor shall provide a copy of all Interoperability (IO) and Information Assurance (IA) certifications and approval letter as an attachment to the proposal. Proposed solution shall be installed in accordance with the JITC deployment guidelines.

2.5 Certification and Accreditation (C&A)

The Contractor shall assist the base in implementing the Information Assurance (IA) compliance for system C&A. To support the DIACAP process, the contractor shall provide and develop any necessary system documentation, settings, self-assessments and specifications required to support the successful accreditation of the Government DIACAP package. This shall include information in support of Government input into the Enterprise Mission Assurance Support Service (eMASS).

2.6 Schedule

The Contractor shall provide a preliminary Integrated Management Schedule (IMS) at time of contract proposal. Contractor shall provide a Government approved final schedule within 14 working days prior to on-site work.

2.7 Spares

The contractor shall provide equipment spares, listed in the LOM, that are critical to maintain system operation with minimal downtime. Contractor shall include spare hardware for one complete workstation.

3. PROJECT EXECUTION

3.1 Site Coordination

The Contractor shall coordinate with the identified site POC(s) a minimum of 10 business days prior to arrival on site.

3.2 Multi-Function Team (MFT) Coordination

The MFT members will be identified prior to contract award. The MFT is composed of stakeholders in the acquisition and is responsible for the acquisition throughout the life of the requirement. The goals of the MFT are to manage this contract and to provide an avenue to collectively work together to create a strong working relationship between the using agency, contracting and the contractor and provide the highest level of contract performance and customer service. Prior to any on-site work, the Contractor shall provide the MFT a project coordination call to review all planned efforts and data collection requirements in support of project implementation.

3.3 Project In-Brief

The Contractor shall conduct a project in-brief with MFT. Contractor shall support and respond to questions regarding issues pertaining to this SOW.

3.4 Provisioning Project Owner

The Contractor shall identify by name a Provisioning Project Owner (PPO), who shall be the prime contractor’s employee, responsible as the single point of contact from award to site acceptance with regard to system implementation. The PPO must remain on site as necessary to assure performance of project. The Contractor shall also assign a system engineer to work for the PPO.

The system engineer shall support architectural diagrams, system interface specifications, technical planning, test plans, test procedures, and logistics sustainability. The Contractor shall submit the first Monthly Status Report NLT forty (40) calendar days after contract award and subsequently every month thereafter until all tasks have been completed IAW this SOW and government final acceptance has been completed.

3.5 Government Delays

In the event that a Government-caused delay requires the Contractor to incur schedule delays or additional costs, the Contractor must document and submit these changes to the Contracting

Officer for their review and consideration prior to any change in schedule.

3.6 Routine Working Hours

Routine work efforts shall be performed during normal installation operating hours with exception to the cutover. Cutovers and any other service-affecting actions must be pre-approved by the

Government and scheduled during maintenance windows (Approved Service Interruption – ASI).

3.7 Contractor Supervision

The Contractor shall be responsible for supervision of all contract personnel and performance of all Contractor-related functions.

3.8 Personnel Training and Certifications

All personnel identified to support this requirement must be trained and/or certified on the systems involved in this effort. Personnel identified to support this requirement must be able to provide training certification upon Government request. Project Managers and Systems Engineers shall be critical positions for this project. Project Managers and System Engineers assigned shall be, at minimum, intermediate level experience.

3.8.1 Special Qualifications:

All installers shall be, at minimum, intermediate level of experience on the installation/programming of the proposed E911 system. Upon request, Contractor shall provide proof of certification.

3.9 Security Clearance

All contracted personnel shall comply with established security procedures for entering an installation and its facilities, including special security procedures for entry to restricted or controlled areas. The Contractor shall obtain necessary badges or documents required for entry to restricted or controlled areas, if applicable, to meet the requirements of this SOW. The Contractor shall coordinate with the site POC to obtain and return temporary badges and vehicle registrations.

Contractors working under this SOW, as a minimum, shall have a favorable National Agency

Check. However, if the proposed solution requires a need for access to Government system(s) requiring a higher security level, the Contractor shall ensure personnel have the ability to obtain proper security requirements when requested.

3.10 Safety

No personnel presenting potential threats to the health, safety, security, general wellbeing, or operational mission of the installation and its population shall be employed by the Contractor during the execution of this SOW. Compliance with AFI 91-202, Air Force Mishap Prevention

Program is mandatory.

3.11 Implementation

The Contractor shall have ultimate responsibility for the successful deployment and cutover to the new infrastructure. Any work deemed non-compliant shall immediately be re-worked at the

Contractor’s expense. This task shall include all necessary work required to connect to the existing infrastructure providing a fully functional network solution.

The Contractor shall plan and manage daily operations and activities associated with providing this requirement to ensure necessary processes and activities are performed to provide an effective and acceptable system. The Contractor will employ effective management tools and methods to assure control of cost, schedule and performance.

The Contractor shall conduct, support, or participate in program management and technical reviews, meetings, and conferences, as required, to ensure effective and efficient SOW execution and is required to be present at meetings at Kadena AFB in Okinawa, Japan.

The Contractor shall ensure protection of government property to prevent damage during the period of time the property is under the control or in possession of the Contractor. The Contractor shall ensure that any damages incurred during the execution of this SOW shall be repaired at the

Contractor’s expense.

3.12 Conformance to Standards

All equipment and system solutions shall conform to the applicable industry standards and mil specs as identified in the following table. Also, if any standards aren't identified below but are applicable contractor shall conform to those as well.

TABLE 3.13.1 INDUSTRY STANDARDS ORGANIZATIONS

1. Federal Information Processing Standards (FIPS).

United States Department of Commerce

National Technical Information Service

5285 Port Royal Road Springfield, VA 22161 http://www.itl.nist.gov/fipspubs/

2. Military Standards, Specifications, and Regulations (MIL-STDs, DoD-STDs).

Standardization Document Order Desk Bldg. 4, Sec. D, 700 Robbins Ave. Philadelphia, PA 19111-5094

3. National Computer Security Center (NCSC) Documents.

Office of Standards and Products

National Computer Security

Center Fort Meade, MD 20755-

6000 http://www.radium.ncsc.mil/

4. National Institute for Standards and Technology (NIST) (formerly National Bureau of Standards, NBS) Documents.

National Institute for Standards and Technology

US Department of Commerce Washington, DC 20234 http://www.nist.gov/

5. Code of Federal Regulations (CFRs).

Superintendent of Documents US Government

Printing Office Washington, DC 20402 http://www.access.gpo.gov/nara/cfr/

6. American National Standards Institute (ANSI) Documents.

American National Standards Institute

11 West 42nd Street New York NY 10036 http://www.ansi.org/

7. Electronic Industries Association (EIA) Standards.

Electronic Industries Association (Alliance)

2001 Pennsylvania Avenue

NW Washington DC 20006

(202) 457-4942 http://www.eia.org/

8. Institute of Electrical and Electronics Engineers (IEEE) Standards.

Institute of Electrical and Electronics Engineers

445 Hoes Lane

PO Box 1331

Piscataway NJ 08855-1331 http://www.ieee.org/

9. International Standards Organization (ISO) Documents.

American National Standards Institute

1430 Broadway

New York, NY 10018 http://www.iso.ch/iso/en/ISOOnline.openerpage

10. Data Interchange Standards Community (E- Business)

Data Interchange Standards Community

333 John Carlyle Street Suite 600

Alexandria, VA 22314 http://www.disa.org/

11. International Committee for Information Technology Standards

INCITS Secretariat c/o Information Technology Industry Council

1250 Eye Street NW

Suite 200

Washington D.C. 20005 http://www.ncits.org/

12. International Telecommunications Union

ITU

Place des Nations

CH-1211 Geneva 20

Switzerland http://www.itu.int/home/

13Unified Facilities Criteria (UFC) UFC-3-580-01 22

June 2007 Telecommunications Building Cabling

System Planning, Design and Estimating

Whole Building Design Guide http://www.wbdg.org/references/docs_refs.php

14. Telecommunications Industry Association (TIA)

1320 N. Courthouse Rd., Suite 200

Arlington, VA 22201 http://www.tiaonline.org

3.13 System Installation Plan (SIP) / Project Support Agreement (PSA)

A System Installation Plan (SIP) / Project Support Agreement (PSA) is required for this SOW no later than thirty (30) days prior to project installation. The SIP/PSA shall be approved by the base prior to the start of any onsite work. The system must be installed with little or no disruption to existing services. Any disruption of service must be coordinated with the Government.

http://www.radium.ncsc.mil/ http://www.nist.gov/ http://www.nist.gov/ http://www.access.gpo.gov/nara/cfr/ http://www.access.gpo.gov/nara/cfr/ http://www.ansi.org/ http://www.eia.org/ http://www.ieee.org/ http://www.iso.ch/iso/en/ISOOnline.openerpage http://www.iso.ch/iso/en/ISOOnline.openerpage http://www.disa.org/ http://www.ncits.org/ http://www.itu.int/home/

3.14 System Turn Over

The Contractor shall assist the Government in completing the AFTO Form 747, Communications and Information Systems Acceptance Certificate. Configuration Management information shall be provided to AFLCMC/HBZBH and each site awarded as part of this SOW as PDF files. The

Contractor shall provide as-built documentation including, but not limited to:

a) Bayface layout drawings and diagrams of the chassis/shelf/cabinet identifying installed cards , modules, equipment, etc.

b) The as-built documentation shall also include cable and power drawings/specifications, floor plans, and engineering specifications generated in support of the installation of the system.

c) The documentation shall include drawings that depict the overall installed system configuration and network topology.

d) Documentation shall also include an equipment listing with serial/model numbers and manufacturer specifications.

e) The Contractor shall provide an inventory of any newly installed equipment and software, identification of test results, site-specific “as-built” engineering drawings, and a summary of any open items.

f) Completed test results.

All upgrade and reconfigured equipment and material (i.e., cabinets, racks, termination blocks, patching, cables, etc.) shall be permanently identified through stenciling or tags. Hand written tags are not permitted. Red-lined drawings are unacceptable. All network topologies in the Air Force are considered both sensitive and proprietary.

3.15 Associate Contractor Agreements

When applicable, the Contractor shall enter into Associate Contractor Agreements (ACA) with the following Contractors. The agreement is to purchase, license and enable the E911 module to create the NENA file required for populating the ALI database.

The Contractor shall enter into Associate Contractor Agreements (ACA) for any portion of the contract requiring joint participation in the accomplishment of the Government’s requirement. The agreements shall include the basis for sharing information, data, technical knowledge, expertise, and/or resources essential to the integration of the E911 System, which shall ensure the greatest degree of cooperation for the development of the program to meet the terms of the contract.

Associate contractors are listed in below.

ACAs shall include the following general information:

Identify the associate contractors and their relationships.

Identify the program involved and the relevant Government contracts of the associate contractors.

Describe the associate contractor interfaces by general subject matter.

Specify the categories of information to be exchanged or support to be provided.

Include the expiration date (or event) of the ACA.

Identify potential conflicts between relevant Government contracts and the ACA; include agreements on protection of proprietary data and restrictions on employees.

The Contractor shall have fourteen (14) days to provide a copy of the agreement to the Contracting

Officer if requested.

The Contractor is not relieved of any contract requirements or entitled to any adjustments to the contract terms because of a failure to resolve a disagreement with an associate contractor.

Liability for the improper disclosure of any proprietary data contained in or referenced by any agreement shall rest with the parties to the agreement, and not the Government.

All costs associated with the agreements are included in the negotiated cost of this contract.

Agreements may be amended as required by the Government during the performance of this contract.

3.16 Performance of Services During Crisis

Performance of Services During Crisis Declared by the National Command Authority or Overseas

Combatant Commander. Services covered by this task are determined to be non-mission essential for performance during crises according to DoDI 3020.37. However, in the event of a crisis, or a significant emergency is declared, the Contracting Officer will contact the Contractor to notify them of the situation and any possible changes to responsibilities. Upon notification, the

Contractor shall perform special event services due to contingencies, natural disasters, including facility operation on an extended basis up to 24 hours per day, etc, as required. In the event of verbal notification, written confirmation of such notification will be provided within 5 calendar days. If addition costs are incurred under this paragraph the Contractor shall have up to 30 calendar days to request equitable contract price adjustment.

4. TECHNICAL REQUIREMENTS

4.1 Baseline

Unless otherwise specified in the following paragraphs, the base shall receive baseline requirements for an E911 system as described in Section 4.2. The Government reserves the right to award all, some or none of the line items listed.

The contractor shall be responsible for providing all premise wiring and networking elements to facilitate the requirements that support the system connectivity from the demarcation or the fiber patch panel.

4.1.1 Kadena AFB

The Contractor shall provide an E911 solution with the minimum requirements as outlined in section 4.2. The existing VESTA E9-1-1 system is under current Airbus DS Communications

Software Support and the contractor shall reutilize existing software licenses, hardware components, cabinets, cabling etc. not subject to wear or at end of life, to the full extent possible to reduce cost to the Government. System components subject to wear or beyond their projected life cycle (i.e. servers, PCs, displays, keyboards, Ethernet switches, etc.) shall be replaced to effectively refresh the system and provide with the full operational capabilities.

The proposal shall include the decommissioning and removal of the existing E911 system and associated equipment/wiring where applicable. Any equipment removal and/or disposal shall be coordinated with a designated official at the host base and disposition thereof shall be in accordance with the host base instructions.

4.2 Baseline Requirement

The minimum requirement is to equip the PSAP with Two (2) Intelligent Call Taker

Workstations/E911 operator consoles. The system shall include all hardware, software, installation, and training services. Unless otherwise specified in Site Survey Data documentation, the Contractor shall perform all tasks (premise and power wiring) as necessary to provide a complete working system. Location for the system equipment will be as follows:

Core Backroom/Server- [Primary ECC Bldg 3489]

Call Taker Consoles-o Primary-[Bldg 3489, Primary ECC]

The system shall provide full redundancy (servers, switches, gateways etc.,) with automatic failover eliminating single points of failure in the call path. The government is to provide diverse fiber paths where applicable to provide redundant connectivity between facilities. The system shall provide flexibility and expansion capability to provide an increase in the number of consoles at each location to support additional technicians, administrators, helpdesk supervisors and calls. The system shall provide, at a minimum, the following features:

Computerized Telephony Integration (CTI) for IWS

Provide the ability to support the base’s migration from legacy TDM platforms to VoIP, regardless of VSS manufacture and without requiring E911 system replacement or major modifications.

Integrated Telecommunication Device for the Deaf (TDD/TTY) capability at each call taker position without need for additional hardware such as phone couplers.

The system shall include a Digital Logging Recorder (DLR) that archives recordings to internal hard disk drive and the ability to transfer recordings to Digital Versatile Disc (DVD) or other portable, digital electronically recorded media and include features to capture of Date/Time, Automatic Number Identification (ANI) / Automatic Location Information (ALI) data associated with each incoming call recorded. All communications at the call taker console level shall be recorded. See Siet Survey Data document for noumber of discreet channel to be recorded.

A single instance of a stand-alone ALI database for all on-base VSS devices.

The system shall provide a management information and reports application shall provide reporting metrics that describe the health of the system. Additionally system shall also track and report call center metrics to include average call volume, duration to answer, lost calls, as well as calls divided by 911 trunk and agent designation.

The system shall have an Environmental Systems Research Institute (ESRI) Geographic

Information System (GIS) based map application. The system shall provide a means of distributing and synchronizing map data updates across all system CPUs (server and position) from a dedicated administrator workstation.

The system shall provide a Network Time Protocol (NTP) server to synchronize the time on all system CPUs (servers, workstations, logger/archiver, etc.). The NTP server shall derive system time from the Global Positioning Satellite (GPS) system. This system shall include a GPS receiver and GPS antenna with associated cabling. Signal amplifiers may be used when required. A surge protection device shall be installed to protect the NetClock receiver and connected devices from lightning damage.

All E911 call data shall display on the operator workstations including the calling party’s

Automatic Number Identification (ANI) and the location of the caller (ALI). Call data shall be displayed textually and plotted to the map. Based on the call source ANI, the Automatic Location

Information (ALI) shall be derived from a current data directory provided as follows:

a. DSN PBX/VSS Call Source: This system shall provide a private ALI database system

(hardware and software) to store phone set location information associated with the appropriate

PBX extension number. This private ALI database system shall be installed on the Air Force premises. Note: The source for this ALI data shall be provided by the Government in the form of a compatible extract file format.

Except where indicated, the Contractor shall be required to provide all services, equipment, and associated materials in the form of installation, setup, test, commissioning, and end user training for the new system. The Contractor shall provide all labor, parts, tools, supervision, and skill/expertise necessary to meet the requirements defined in this SOW.

4.2.1 System Requirements

The E911 system shall meet the following minimum performance and physical requirements.

4.2.1.1 Performance

The following performance requirements shall be met.

4.2.1.1.1 Voice Switching System Interoperability

The system shall be interoperable with and directly interconnect to Kadena AFB Host Voice

Switching Systems (VSS) that performs the base level voice communications and unified capabilities. At a minimum the system shall directly interface with Multi-Function Soft

Switches (MFSS), WAN Soft Switches (WANSS), Multi-Function Switches (MFS), Local

Session Controllers (LSC), End Offices (EOs), and PBXs without use of phone set interface/emulation or the addition of a PBX. It is acceptable for the proposed system to offer soft-phone application that is integrated with the system.

4.2.2 Physical Characteristics

The system shall meet all of the following requirements:

4.2.2.1 Dimensions

The core backroom/server equipment shall be 19–inch rack mountable to the maximum extent possible. The equipment shall adhere to best commercial practices when not rack mountable.

4.2.2.2 [Server Uninterrupted Power Supply (UPS)]

Unless otherwise specified, a minimum of 15 minutes of backup power is required through battery strings or UPS systems.

4.2.3 System Capabilities

The system capabilities shall meet the following functional requirements:

4.2.3.1 Call Taker Workstation

The call taker workstation shall utilize Computerized Telephony Integration (CTI) to present

E911 calls with ANI and ALI to the screen. Each call taker position shall provide:

4.2.3.1.1 PSAP Equipment Compatibility

Call taker positions shall be NENA2-compliant Intelligent Workstations (IWS). IWS shall be compatible with the NENA-compliant PSAP core backroom system servers and is a current production product from the same manufacturer.

The minimum requirements for the workstations shall meet the following specifications:

Case Style / Units Small Form Factor

Chip Set Intel® C226 Chipset

CPU Intel Core i7-3770 processor, 3.4/3.9 GHz, 77W, 8MB cache, 1600 memory, Quad-Core

Optical Drive 16X DVD+/-RW SATA Super Multi

Expansion Bays 2 (1 Internal 3.5", 1 External 5.25)

RAM 4GB 1600 nECC Unbuffered DIMMS

Hard Drive 250.0GB SATA/300 7200rpm 1" Hard Drive

Keyboard USB Standard Keyboard

Mouse USB optical 2-button scrolling mouse carbon

NIC Integrated Intel 82579LM PCIe GbE Controller

4.2.3.1.2 Displays

Unless otherwise specified in Site Survey Data documentation, the displays shall be minimum 20-inch, maximum 24-inch touch screen for the E911 call data screen. Displays shall support stand alone or multi- display mounting.

4.2.3.1.3 Login

The dispatch workstations shall utilize operator unique usernames and passwords.

4.2.3.1.4 [Uninterrupted Power Supply (UPS)]

A minimum of 15 minutes of backup power is required through battery strings or UPS systems.

4.2.3.1.5 Integrated Telecommunication Device for the Deaf (TDD/TTY)

The system shall provide an Integrated Telecommunication Device for the Deaf (TDD/TTY) capability. TDD/TTY capability shall be a fully embedded, native function of the IWS. Use of external coupling devices, third party software or hardware applications shall not be permitted.

4.2.3.1.6 Instant Recall Recorder

Each call taker position shall have the ability to record and instantly replay voice conversations. This position level audio recorder shall instantly replay telephone and/or radio conversations from compatible radio consoles, to aid in interpreting difficult to understand callers. The audio recording shall be stored on the call taker’s workstation CPU. This capability is above and beyond the system-wide archiving, digital logging recording capability.

4.2.3.1.7 Headsets

The system shall include compatible headsets for each workstation.

4.2.3.1.8 System Fall Back

The system shall have fall-back capability to answer an E911 call in the event of server or call taker workstation failure. In the event of a server failure, system operation shall automatically transfer to the backup server with no lost calls. In the event of a call taker workstation failure, the system shall automatically re-route the call to an alternate workstation.

4.2.3.1.9 Call Handling

The System shall be capable of capturing ANI/ALI information in the event a caller disconnects before dispatcher answers. The system shall indicate the call was abandoned and display the ANI/ALI related to that call.

The system shall automatically deliver E911 calls to the call taker position(s) with originating ANI data. If the caller hangs up (abandoned call), the system shall allow the call taker via single key command, to perform an abandoned call “call back” function. The abandoned call capability shall be a fully embedded, native function of the systems and the use of external, dedicated devices (abandoned call phone sets, abandoned call printers etc), Third party software or hardware applications shall not be permitted.

The system shall be capable of transferring PSTN (commercial) originated 911 calls to a designated civilian PSAP via the LEC selective tandem router, with ANI data using a one button transfer provision on the call takers screen. The solution shall have the capability of receiving a call from a designated civilian PSAP with ANI via the LEC selective tandem routing network (CONUS only).

4.2.3.1.10 Push-to-Talk

The system shall have the capability of talking to E911 callers without a push-to-talk function.

4.2.3.1.11 PBX/VSS Line Features

The system shall support, at a minimum, the following PBX/vss line types and system features:

DN, uniquely appearing Directory Numbers

ACDDN, designated to receive inbound ACD calls

AUL, Ring-down Lines

GIC, Group Intercom Calling

3WC; 3-Way Conferencing

Trunk Steering/Dual Location Information Providers

RAG; Ring Agent

Transfer

4.2.3.1.12 Keypads

The system shall provide a minimum of 24 key dialer keypads.

4.2.3.1.13 Modular Expansion

The system shall provide modular expansion capability to support future Session Initiation

Protocol (SIP) trunks and multimedia emergency message content display.

4.2.4 E911 PSAP Common Equipment

4.2.4.1 PSAP Servers

The system shall support the following ALI server requirements:

Case Style RACK (2U)

Cache 15MB (1x15MB) Level 3 Cache

CPU Intel® Xeon® E5-2640 (2.6GHz/6-Core/15MB/7.2GT-s

QPI/95W, DDR3-1333, HT, Turbo 2-3/3/4/4/5/5) Processor

CD-ROM Slim SATA DVD-ROM Optical Drive

Chipset Intel C600 Chipset

Controller Smart Array P410i/1GB FBWCRAID 0/1/1+0/5/5+0

Expansion Bays 13

Expansion Slots 6 (1 PCI-Ex16 Gen 2 (x16 speed); 1 PCI-E x8 Gen2

(x8 speed), 4 PCI-E x8 Gen 2 (x4speed)

Hard Drive Listed in Quote

Management Integrated Lights-Out 2 (iLO) Management

NIC Dual Port Gigabit NIC

Ports 0 Parallel (25-pin)/1 Serial (9-Pin), 6 USB (2 rear, 2 front, 2 internal)

Power Supply One (1) 460W Hot Plug (Redundancy enabled) power supply

RAM 16 GB (4 x 4GB) PC3-10600R DDR3-1333 Registered

DIMMS

Video Integrated Matrox G200 video standard

Weight/Dimensions 54lbs (one HD, PS and processor installed); 18.5"H x 8.59"W x 23.46"D

Expansion One (1) PCI-X Expansion Kit (HP #488413-B21)

Keyboard One (1) PS/2 Black (Microsoft #ZG6-00006)

Mouse One (1) PS/2 Black Mouse 2-Button (HP #537748-001)

Power Cord Two (2) NEMA 5-15P low voltage (HP #AF556A)

Power Supply One (1) Redundant HS Power Supply 750W (HP #512327-

B21)

4.2.4.2 E911 PSAP Server Cabinet

The Common PSAP server cabinet shall have the following requirements:

Monitor/Keyboard 19-inch Flat Panel, Fold Out

Remote Access Modem Package

Patch Panel 24-Port Patch Panel

Arbitrator 4-Port KVM Arbitrator

Time Sync Network time protocol server

911 Trunk Converter

WAN Gateway Demark

PRI Gateway Interface

24-Port Ethernet switches with Fiber Interface, JITC

Approved/Certified Layer 2 Switch

4.2.5 TMS Interface

The system shall support manual ALI record updates from the base PBX/VSS extensions with future capability for automatic updates from the base TMS records.

4.2.6 Single Number Dialing

The E911 system shall be implemented with a single three-digit number of 9-1-1 at all locations.

The Contractor shall be responsible for updating the routing and translations in the Voice

Switching System (VSS) to support three-digit translations of 9-1-1 without delay and digit collection timeout.

4.2.7 Site Telephone Switch Integration

The system shall be compatible with site telephone switch topology. The E911 call taking system shall provide the direct delivery of E911 calls to a DoD-staffed PSAP without the need for intermediate call answering by the local civilian PSAP. The system shall be approved to interconnect directly with the PBX/VSS equipment via PRI with ability to support migration to

SIP based trunking in the future with minimum reconfiguration requirements.

The Contractor shall perform all telephone switch programming necessary to accommodate the routing of calls to the system and network. Programming shall include the base host switch and any PBX attached that is maintained by the host maintenance unit.

4.2.8 Additional E911 Workstation/Console

The proposal shall include the price for one licensed workstation/console position and all associated equipment for networking and recording capability. This option may require a return trip. Contractor shall provide all services, equipment, and associated materials in the form of installation, setup, test, commissioning and end user training for the new console. The

Government reserves the right to declare the number to purchase at time of execution. This is

NOT a spare.

4.3 Total Cost of Ownership

Except where specified in Section 4.1.1 of this SOW, the solution shall minimize total cost of ownership to the E911 and VSS infrastructure. The system shall leverage existing base level VSS;

E911 system; and equipment, switches, and infrastructure to the greatest degree. The proposed solution shall provide the ability to support the base’s migration from legacy TDM platforms to

VoIP, regardless of VSS manufacture, without requiring E911 system replacement or major modifications.

4.4 Single System Management Solution

The Contractor shall provide a single system management solution that shall be capable of managing all IWS positions settings, mapping updates, and stand-alone ALI database from dedicated administrator workstations. To better secure sensitive audio recordings and associated data, it is acceptable to provide a dedicated DLR playback/administrator workstation, restricting access to fire protection and law enforcement administrators.

5. TESTING REQUIREMENTS

5.1 General Testing Requirements

The Contractor shall perform testing and inspections of all systems solutions to ensure the technical adequacy and accuracy of all work, including reports and other documents required in support of that work. The Contractor shall conduct on-site testing in accordance with the Original

Equipment Manufacturer (OEM) installation manuals, practices, and the appropriate vendor’s test procedures. The testing shall ensure the cabling is fully functional and meets the user requirements. All work shall be accomplished IAW E911 System Test and Acceptance Plan. The

Site MFT member shall be on-site during the entire testing procedure.

The Contractor shall provide preliminary Installation and Test Acceptance Plan to the Government

60 days prior to installation start for review and approval. The Government will have 10 days to review and provide comments to the contractor. The Contractor shall update changes and provide to Government for final review and approval. The Contractor shall conduct with the Government testing of the complete Enhanced 911 system, which may include premise equipment, distribution systems, or any additional telecommunications/network equipment or operating support systems identified in the SOW. Pre-cutover audits shall consist of verification of all testing completed by the Contractor such that the system is deemed ready for functional cutover. Post-cutover audits shall verify that all cutover acceptance testing has been performed satisfactorily in accordance with the standard practices and identify those tests, if any, which have not been successfully completed and shall be re-tested prior to acceptance.

Testing shall be performed in two steps: System testing (all equipment assembled and operating correctly) and Operational testing (real world). The Contractor shall provide a logical test process that minimizes interruptions and avoids sustained downtime and presents a contingency procedure to be implemented in the event of systems failure during testing.

5.1.1 Test Results

Test results shall be reviewed upon test completion, and a Government POC member shall sign the system test acceptance upon complete satisfaction that the system has passed all the required test procedures. Test results shall be included with the as-built documentation.

5.1.2 Site Acceptance/Project Completion

Site acceptance and project completion shall be considered as accepted/completed and the successful testing of the installation. Only a Government POC shall authorize site acceptance showing the site agrees that all testing, implementation, and training was successful. Site acceptance is required prior to invoicing.

The Government POC will be the final signatory on the site acceptance form or DD Form 250.

The Contractor shall notify the Government upon completion of all tasks. The Government reserves the right to refuse final acceptance until all discrepancies have been resolved to the satisfaction of the Government. The Contractor shall prepare a project discrepancy list, report detected issues during meetings, and track all discrepancies until resolved. The Government will review and monitor all discrepancies and deliverables. The discrepancy list shall include any problem(s) detected and identified during the upgrade. The Contractor shall retain a history of discrepancies. Problems identified during the upgrade period shall be documented, provided to the Government, and corrected prior to final acceptance.

Site acceptance shall conclude upon successful installation, commissioning, connecting and testing of the system, and receipt of all deliverables. The Contractor’s task completion form or a

DD Form 250 shall be used to document this completion.

6. LOGISTICS SUPPORT

6.1 Warranty

The Contractor shall provide warranty services for workmanship deficiencies and equipment provided or installed as described and in accordance with Section 52.246-17 WARRANTY OF

SUPPLIES OF A NONCOMPLEX NATURE (JUN 2003) ; 52.246-19 WARRANTY OF

SYSTEMS AND EQUIPMENT UNDER PERFORMANCE SPECIFICATIONS OR DESIGN

CRITERIA (MAY 2001) ; 52.246-20 WARRANTY OF SERVICES (MAY 2001). Warranty period shall begin upon site acceptance (reference paragraph 5.1.2 of this SOW). The Contractor shall provide warranty services for workmanship deficiencies and equipment installed for a period of two (2) calendar years. The Contractor shall provide written procedures and required information (24/7 contact number) for sustainment and warranty services prior to cutover in the site acceptance form or as an attachment to the site acceptance form. This information shall include, but is not limited to, written confirmation of the warranty period and phone numbers and contact information/procedures for technical support, troubleshooting assistance, and replacement of faulty cards/equipment. The Contractor shall notify the site and Program Manager ninety (90) days prior to warranty expiration.

6.2 Local Onsite Support and Response Requirements

Kadena AFB seeks to avoid additional cost to the government, longer time out of service, and inefficiencies for the end users. As such, Contractor must have a Federal Depot staffed with technical employees domiciled in Okinawa and mainland Japan. The technicians must be capable of performing functions such as:

o Perform routine maintenance and repair of the system o Certify and maintain operation and integration with dispatch consoles and logging recorders o Provide 24x7 technical support.

o On Site infrastructure response (24x7, 2 hour maximum response time)

6.3 Software Patching

Contractor support shall include all Original Equipment Manufacturer (OEM) software patches and vulnerability fix solutions as provided by the OEM that occur during the course of the warranty period at no additional cost to the Government.

6.4 Remote Access

Remote access shall be coordinated with the Multi-Function Team. Remote access shall be required to support sustainment of the systems. The Government will provide remote access for

Contractors that meet the personnel and IA requirements of the USAF.

6.5 Packaging, Handling, Storage, and Transportation.

The Contractor shall be responsible for packaging, handling, storage, transportation, staging, and deployment of any equipment and materials provided as part of this SOW. The Contractor shall be responsible for the removal and disposal of items installed/replaced under this installation and shall comply with all applicable industry rules and regulations. Any equipment removal and/or disposal shall be coordinated with a designated official at the host base communications squadron.

6.6 Training

The Contractor shall provide training on the E911 system for the number of Government representatives. Training shall include manuals or materials appropriate to the curriculum. The

Contractor shall provide a DVD-ROM of the training.

6.6.1 Training Development

The Contractor shall provide on-site training on all systems installed in accordance with SOW.

The E911 system shall be designed to be operated by personnel with a minimum of a

Journeyman level. The Contractor shall develop supervisory and technician system operational training IAW the Government-approved Training Plan. The object of supervisory training is to provide supervisory personnel (Supervisors, Administrators, Crew Commanders) and

Government E911 System Trainers with the knowledge necessary to support, manage, and operate the system’s hardware and software tools to perform their jobs. The object of technician training is to provide Journeyman level agents and Government E911 System Trainers with the knowledge necessary to operate the E911 system. Training shall be instructor-led, classroom training; in lecture, demonstration, and performance formats. The Contractor shall develop end-of-course critiques to be distributed to attendees of all training.

The following are the training requirements and minimum number of personnel at each base:

Operations and Maintenance (O&M) training to provide system technicians with necessary skills to perform Tier 1 maintenance. (5 people)

User/Agent training focusing on daily operation of the E911 system. (10 people)

System Administrator training to provide administrators the ability to manage users and groups, setting preferences, updating the mapping. (5 people)

6.7 Commercial Off-the-Shelf

Contractor shall provide two (2) copies of the OEM’s manuals for all equipment installed for this project (PDF format preferred) with copyright releases. The manuals shall include user guides, description, installation, test, operation and maintenance. The Contractor is not responsible for existing commercial equipment manuals. The Contractor is required to be able to show the inter-connections both hardware and software between the present and future systems.

6.8 Equipment Removal

When applicable, Contractor shall be responsible to decommission and remove all wiring, equipment and associated hardware identified by the Government or site survey. Removal of the equipment must be coordinated prior to cut-over with the local CS and/or MDG to ensure that the equipment is packaged/palletized for ease of transport to the base Defense Reutilization Marketing

Office (DRMO) before completion of the project.

Contractor shall be responsible for decommissioning and palletizing equipment. Base ADPE

(Automated Data Processing Equipment) custodians of said equipment will be responsible for the paperwork and transportation of items for DRMO.

7. ALLIED SUPPORT REQUIREMENTS

7.1 Allied Support Requirements (Base Requirements)

Allied support requirements will include the following unless otherwise noted:

Providing outside plant infrastructure between facilities.

TMS (TOSS) data supplied by site in NENA2 compliant format – software updates required to facilitate the delivery of the data must be indicated at the time of site survey as GFP

POC for base interaction and access

Personnel required for training to maintain local operation of the system including system administrators and operators

System scanning for vulnerability determination and mitigation for accreditation purposes.