Attachment 2. Kadena_VoIP_SOO_V1_FINAL_8_24_2023.docx

SOO KADENA AB UC VoIP V1 May 26, 2023

STATEMENT OF OBJECTIVES

KADENA AB

TDM Migration

V1 26 May 2023

Prepared by 38th Engineering Squadron, 38 Cyberspace Engineering & Installation Group

Contents

1.0 SCOPE

2.0 APPLICABLE STANDARDS

3.0 KADENA AB TELEPHONE VOICE BASELINE

4.0 PROJECT DELIVERABLES

5.0 SYSTEM MIGRATION – VOICE CORE SYSTEM UPDATE

6.0 TRUNK MIGRATION - OPERATIONAL TRUNK MIGRATION

7.0 TRAINING REQUIREMENTS

8.0 GENERAL ENGINEERING REQUIREMENTS

9.0 INTEGRATED PRODUCT TEAM

10.0 WEEKLY STATUS REPORT

11.0 SYSTEM TESTING

12.0 GOVERNMENT FURNISHED PROPERTY AND SERVICES (GFP/GFE/GFS)

13.0 PERFORMANCE

14.0 SECURITY

15.0 QUALITY CONTROL

16.0 QUALITY ASSURANCE

17.0 KADENA 18TH CS RESPONSIBILITY

18.0 KADENA SECONDARY CRASH NET

APPENDICES

APPENDIX A PHONE MODEL FEATURES MATRIX

APPENDIX B CDRLs

APPENDIX C FEDERAL GOVERNMENT STANDARDS

APPENDIX D ACRONYMS

1.0 SCOPE

This Statement of Objectives (SOO) defines the requirements for the Contractor to Engineer, Furnish, Install, Test and Place (EFIT&P) into service a Unified Communication (UC) platform to include but not limited to the following:

· Perform an Upgrade of the existing Kadena AB VoIP virtualized CUCUM (Release 11.5) to latest JITC certified (Release 14 or latest JITC certified Version) to support up to 15,000 VoIP and Non-VoIP users – replace and configure two (2) current UCS C220 M4 with two (2) GFE procured BE7M-M5-K9 (in B400) and add two (2) additional BE7M-M5-K9 (in B3518) for full redundancy

· Install GFE procured SBCs (Cisco C4300s) for SIP trunks

· Replace and configure existing two (2) Media Gateways routers (C2951s) with two (2) latest JITC certified C8300s(in B400) and add one (1) additional C8300 (in B3518) for full redundancy

· Enable SIP connection (when SIP trunks are available) with SBCs to Kadena UC system

· Migrate approx. 1,500 TDM users to VoIP

· Replace all existing Voice Gateways (VG-350s, VG-224) with Kadena’s procured new VG-450s latest version.

· EFIT&P additional VG-450s (20) to accommodate 2,880 POTS (non-VoIP) users (to include FAX, Modem, and other analog devices)

· Provide strategic solutions and implementation to support legacy analog system(s)

· Engineer and implement trunk re-homing/configuration of analog systems from MSL-100 to new Gateways (DSN, FTS, Local PSTN…)

· EFIT&P a separate Call Manager BE6K for MECOI unit with 600 users capability with DSN trunk connection to B400 CUCUM.

· Procure 50 UPS in ASLAN location

· Provide training of CUCM, Media Gateways, SBCs, VGs - configuration, troubleshooting and maintenance

· Relocate Secondary Crash system core Forum Alert III suite from B 400 Cabinet MCIF 13 to Building 3409 ITN Room Relay Rack 1 (see Section 18 – Secondary Crash Net)

This SOO will define the Contract EFIT&P responsibilities within a framework contained within separate sections of this document. The Contractor shall integrate, facilitate and engineer a solution that satisfies all system requirements and carrier side requirements that are outlined in this SOO. The Contractor shall provide a technical solution that meets the requirements of this SOO, and provide new equipment, in addition to the procured GFE, to the maximum extent practical as stated above to support the proposed technical solution. The Contractor shall provide and install all necessary equipment and material to upgrade and provide a VoIP backbone solution that is in compliance with the latest version of the Department of Defense (DoD) Unified Communications Requirements (UCR), Risk Management Framework (RMF) and all other references set forth in this SOO.

The overall key UC capabilities and Voice Services required at completion shall include but not limited to the following details:

· Provide an upgrade to Kadena current UC voice Core system capable of supporting 10,000 AFNET and non-AFNET users, including a UC server template capacity to support 5,000 additional AFNET and non-AFNET users for future growth (Total 15,000 users). For the purposes of this document, the Core system is defined as the current JITC approved versions of the Cisco UC Server Platform Release 14 or latest JITC certified Version, Gateway routers and associated modules, Session Border Controllers (SBC) for SIP trunk, Analog Voice Gateways (VGs), and any other hardware platforms that provide services to the UC platform as a whole.

· Install virtual and/or physical server platforms into the UCS to support application services and capabilities; services will include, but not limited to:

· UC based Voicemail capability

· UC based Subscriber-Level Multiuser/Multi Site Voice Conference Service Capability

· User self-service ad-hoc "Meet-Me Conferencing”

· UC based Call Center Services Service Capability

· A "Crash" phone capability

· The ability to process Multi-level Priority & Precedence (MLPP) call traffic (The system shall be compliant with the DoD Multilevel Precedence & Preemption Capability (MLPP) and JITC Certification.)

· Establish a set of operational PRI Tie Trunks between the UC VoIP System and the existing Nortel MSL-100 Telephone Exchange. These trunks will be utilized for cross system phone traffic test during the installation. Once the UC VoIP core is successfully updated, tested and verified, the migration of current TDM users (in specified locations per 18th CS) to UC VoIP will take place.

· If SIP trunks (DISA and Local KDDI) are available, migrate/rehome all trunking from Nortel SL-100 to VoIP Media Gateway routers – physical re-home and program to route traffic of all analog PRIs from MSL-100 to Media Gateways to insure proper VoIP Gateway operation.

· Provide and install 1,500 UC VoIP phone instruments that are JITC compliant at multiple locations designated by 18th SCX on KADENA AB. The models of phone types and capabilities will be defined as: Basic Phones, Mid-end Phones, and High-End Phones (Ref Appendix A).

· Perform the logical migration of a subset of 2,880 analog telephone units to Analog Gateway (VGs) units with minimal disruption. The migrated units will include legacy POTS devices unable to migrate to VoIP devices (i.e. Wall Phones, Hot Lines, Modem, Fax, STEs…), and/or certain locations on the installation where IP connectivity is unavailable or prohibited.

NOTE: The contractor will not be required to physically cut over the individual analog circuits frame cross-connects, but will be required to logically cutover each circuits in coordination with Kadena 18th CS communication team.

· Provide authorized certified training for six (6) KADENA AB personnel as described in this document.

· Ensure that all platforms must be ASLAN Compliant for redundancy/survivability, and cybersecurity hardened in accordance with current DoD STIG (Security Technical Implementation Guide) and MUDG (Military Unique Deployment Guide) criteria. These are CRITICAL security items, compliance must be documented in-detail within the Contractor's proposal, test plan, and implementation plan. Further guidance will be provided in others sections of this document.

NO SIP trunk available to connect – DISA and local KDDI PRI trunks are still connected to MSL-100, providing DSN and local service to all Kadena users. The following progression is suggested.

1. Size and increase PRI trunking between MSL-100 and Media Gateways to support 15k VoIP and non-VoIP users.

2. Configure and install two (2) GFE procured UC cores BE7M-M5-K9, Release 14 or Latest JITC certified Version (in B400) and EFIT&P two (2) additional BE7M-M5-K9 (in B3518) for full redundancy with proper dial plan

3. EFIT&P New Media Gateways C8300s for full redundancy between B3518 (Primary core) and B400 (Secondary core)

4. Install procured GFE SBCs (one for B400 and one for B3518) and size traffic to support up to 15K VoIP users to ready for future SIP

5. Re-home “needed residual PRIs trunks” from MSL-100 to the Gateways and configure for traffic to flow thru Gateways instead of MSL-100.

6. Start migrating remaining ~ 1500 TDM users to VoIP

7. Replace existing VG-350s and VG-224 with new VG-450s

8. EFIT&P new VG-450s to support 2,880 POTS users with 18th SCX coordination

9. EFIT&P a separate Call Manager BE6K for MECOI unit with 600 users capability and DSN trunk connection to B400 CUCUM.

10. Plan and execute remote TDM switches decommissioning – remove remote TDM switches in B626 and B44702 (MUNS) per 18th CS approval Notes: “Needed residual PRIs trunks” are PRIs that are servicing systems that cannot yet be IP (Command Post, Crash system ect…)

2.0 APPLICABLE STANDARDS (Most Current Versions Available)

All installation, network equipment, equipment racks/cabinets, cables (communications, power, grounding, etc.), pathways, wire management, patch panels, etc. shall be IAW standards referenced in paragraph 5, Appendix A and in secure areas comply with AFSSI 7702 “Emission Security Countermeasures”, and NSTISSAM Tempest/2-95 “National Security Telecommunications and Information Systems Security Advisory Memorandum (NSTISSAM) Red/Black Installation Guidelines”

2.1 Joint Interoperability Test Center Approved Product List (JITC APL)

2.2 Cisco Systems Best Practices, Product List and Technical Specifications – Cisco Specific Military Unique Deployment Guide (MUDG)

2.3 Avaya Systems Best Practices, Product List and Technical Specifications – Avaya Specific Military Unique Deployment Guide (MUDG)

2.4 National Electrical Code© NFPA 2018

2.5 BICSI Telecommunications Distribution Methods Manual (TDMM) ©, 13th Edition

2.6 International Standards Organization (ISO) Document: 33.040.35: Telephone networks

2.7 Defense Information Systems Agency (DISA) Defense Switched Network (DSN) Operational Procedures and Standards

2.8 Federal Communications Commission (FCC) Operational Procedures and Standards

2.9 Applicable Air Force Technical Orders including installation grounding, and ESD

2.10 Current DoD-DISA Security Technical Implementation Guide (STIG) and the Unified Capabilities Requirement – ASLAN (UCR 2013 Change 2) – ASLAN Redundancy and Reliability compliance is critical and will be a key factor.

3.0 KADENA AB TELEPHONE VOICE BASELINE (Ref. Fig. B)

3.1 Kadena current TDM switch system

a. Nortel SL-100 Exchange End Office:

The Nortel SL-100 is a legacy Multi-cabinet systems consisting of a Voice Switching Processor XA-Core with software load and limited Tier support from ETAS (Engineering Technical Assistance Support), switch fabric, and trunk/line circuit distributions through Digital line cards housed in Intelligent Peripheral Equipment (IPE) Modules. The System currently provides the functional switch logic and dial plan digit processing for all external trunk and PBX routed calls at KADENA AB. The primary core SL100 system is located within Building 400, and is powered by commercial service with battery room and generators providing emergency service. Station Equipment including many of the SL-100 subsystems operate utilizing -48VDC provided by an in-station rectifier panel. Additionally, the main system supports four (4) remote units located in the following buildings: B44702 (MUNS), B6105 Camp Shields, B626 (MEDCOI), B3518 (VoIP Primary Core).

b. Subscriber Lines:

The MSL-100 system provides phone services to approx. 12,000 end subscribers with phones sets to include digital sets, P-Phones, and analog devices (Wall phones, fax, STE, etc.). Currently there are approximately 5,000 TDM active users on the TDM switch.

c. System Trunking:

External trunking is provided by T1s and PRIs DTCI connecting to the local exchange office. Current CSA and Call Manager data showed three (3) PRIs Local trunks from KDDI and DSN trunks from DISA.

d. Ancillary Services:

The following services are hosted on the SL-100 platform -Local Ad-Hoc Conference service, Motorola VESTA E911 service, Command Post, Entry phones, Elevator Phones.

e. Dial Plan:

KADENA AB resides within a single LATA, and a single leased NNX number block is assigned to the SL-100. Direct-in-Dial (DID) to any base subscriber from external networks is enabled, subscriber external dialing is accessed via three (3) 2- digit prefix access codes (PSTN, DSN, FTS).

3.2 Kadena current VoIP system and proposed upgrade

Kadina current VoIP system support approximately 5,000 users.

a. UC Core system: (Ref. Figure A) Kadena UC VoIP Core systems UCS C220 M4 resides in B3518 and B400 (Dial Central Office). B3518 is designated as Primary VoIP Core and B400 as Secondary core. The VoIP Core has one cluster with two (2) ESXI hosts with the following configuration:

Primary Core B3518 ESXi has:

· CUCM Publisher - System version: 11.5.1.14900-11

· CUCM Subscriber - System version: 11.5.1.14900-11

· CUC Primary (voicemail) - System version: 11.5.1.14900-11

· UCCX Primary (call trees, call service center features) - System version: 11.5.1.11001-34 (ES03-18)

Secondary Core B400 ESXi has:

· CUCM Subscriber - System version: 11.5.1.14900-11

· CUC Subscriber - System version: 11.5.1.14900-11

· UCCX Subscriber (Not operational)

The CUCM is virtualized with VM version is VMware ESXi 5.5 with installation of 2 vCPU Intel(R) Xeon(R) CPU E5-2640 v3 @ 2.60GHz, disk 1: 110Gbytes, 6144Mbytes RAM, Partitions aligned.

Note: CUCM current release 11.5 is upgraded through PACAF procurement program to Release 12.5.

To date, Kadena has received two (2) hardware servers BE7M-M5-K9 with Release 12.5. It is proposed in this SOO to upgrade to latest Release 14 or latest JITC certified Version and add two (2) additional BE7M-M5-K9 servers to be configured for full VoIP redundancy.

b. Media Gateways:

B400 (DCO) has two (2) Media Gateways Cisco 2951 K9 IOS15.6(3)M4 with four (4) T1 cards each.

Note: The Cisco 2951 has EOL 2022 and will need to be replaced.

It is proposed to replace the MGs with JITC certified Cisco C8300s – two (2) in B400 and one (1) in B3518 to be configured for full redundancy with VRRP (Virtual Router Redundancy Protocol) and GLBP (Gateway Load Balancing Protocol).

c. Analog Voice Gateways (VGs):

Kadena currently has ten (10) Voice Gateways – nine (9) VG-350s and one (1) VG-224 supporting approx. 1,100 POTS users. Kadena also has in its inventory nine (9) new VG-450s which will be replacing the aging VG-350s.

Note: The VG-350s and VG-224 are aging and failing and will need to be replaced.

It is proposed to replace the aging VGs with VG-450s and acquire additional VG-450s to support approx. 2,880 POTS users.

d. UPS (Uninterruptible Power Source) Survey has found a numbered of communication switches and routers have no UPS or UPS that are failing or out of services. An uninterruptible power source for the LAN and VoIP infrastructure is a necessity for the continued survivability, availability, and reliability of the VoIP services especially for C2 users in an ASLAN environment. An estimate of 50 UPS will be required to remedy this deficiency. The contractor shall work with 18th CS UPS requirement list to install UPS in required locations.

Fig. A. KADENA AB VoIP current state (18th CS topology)

Fig. B Kadena AB Voice current state

Fig. C Kadena AB Voice proposed End State

3 PROJECT DELIVERABLES (CDRL)

4.1 Project Deliverable Overview:

The contractor shall conduct an engineering site survey at KADENA AB to obtain all information necessary for the requirements in order to develop a System Installation Plan (SIP) to include site survey report, propose equipment/material installation, drawings (including, but not limited to building and room drawings depicting equipment location/rack elevations) test plans, and system cutover plan.

The contractor shall provide a technical solution with all equipment (hardware and software), tools, materials, supplies, transportation, supervision, management, and other incidentals necessary to EFIT&P (Engineer, Furnish, Install, Test, and Place into service) the requirements as stated in this SOO. All equipment, licenses, supplies, and materials provided shall be new with the exception of some operational components that are still serviceable, JITC approved, able to meet the increased load capacity, and are fully supported by the Contractor. All new equipment must comply with FIPS requirements and current United States State Department, DoD, and USAF restrictions on the country of origin. No equipment, even if listed as new, shall have origin as an "open box", "demo" device, or surplus stock from previous contracts. All equipment will be delivered with factory seals intact. Procedural and high level project deliverables are described below with references to any applicable CDRLs (Contract Data Requirement List (DD Form 1423-1)).

a. Provide a detailed Engineering Cutover Installation Plan (CDRL000l). Plan will include line drawings at various phases of installation along with verbiage that presents a logical sequence of installation tasks to meet the objectives of the SOO. The plan should describe compliance with the DoD ASLAN requirements for redundancy and survivability. The reference document is the DoD Unified Communications Requirement 2013 - Change I {UCR) which is assessable through public access at: https:/ /www.disa.mil/~/media/Files/DISA/Services/UCCO/UCR-2013-Change2/UCR- 20 I 3-Change2.pdf. Should a newer or revised versions of the UCR be released, the latest version shall be applicable. ASLAN Compliance, including equipment, power, and system redundancy are key factors.

b. Provide a detailed Engineering Cutover Test Plan (CDRL0002). The contractor shall develop and deliver a test plan showing how the system will be evaluated to perform within standards established referenced standards after cutover. The test plan will display how the post cutover trunk system meets the operational and technical criteria established in this document. The Contractor will integrate a pass/fail check list for key items, each item should have a MEASURABLE and APPLICABLE reference that quantifies the pass/fall criteria; (an example would be: is All LAN Cabling properly terminated IAW with TIA/EIA 568B)

c. Provide a detailed System Security Plan (CDRL0003). The Contractor shall develop and deliver a system security plan. The plan will detail all actions taken to harden the system in accordance with the Cisco specific version of the Military Unique Deployment Guide (MUDG). The contractor will also ensure any additional security configurations are performed to provide compliance with the DoD Security Technical Implementation Guide (STIG).

NOTE: Additional local security requirements may be required, please contact the KADENA AB Information Assurance Officer who can provide further clarification on any site-specific requirements during the project walkthrough. (CDRL0003)

d. Provide a Post-Install Test Report (CDRL0004): The contractor shall develop and deliver a test report showing how the system met all of the operational tests described in the test plan.

e. Provide As-Built drawings (CDRL0005): The contractor will provide As-Built drawings documenting all cabling, equipment, and configuration data accomplished post-cutover.

f. Provide Lead Engineer's Certification or credentials (CDRL0006). The assigned Cisco engineer(s) will hold as a minimum level the Cisco Certified Network Professional Collaboration (CCNP-Collaboration) certification with a minimum of three years direct experience with Cisco Unified Communications Platforms, and Cisco Voice Gateway Routers. Extensive experience on these platforms can be substituted in lieu of credentials at the discretion of the assigned USAF Contracting Officer, or the assigned USAF Project Manager. If experience is substituted it must include relevancy to the current software versions, and the personnel listed with this experience must be assigned as part of the on-site team.

g. The Contractor shall label all installed rack, equipment and cables for traceability. Existing rack, equipment, cables and connection shall be identified and labelled for tracking and traceability as directed by the 18th SCX. Contractor shall also provide rack elevation drawings of every system installed identifying equipment installed and connectivity.

3.2 Definitions of UC System Core Components

This section provides a high level description of the new UC System’s core components (Ref. Fig. C) Please note that the contractor submitted design may vary from the components listed in this section.

NOTE: While we request that adherence to our major component list is respected, we acknowledge that other viable options for design and components exist, therefore variance from this list is permissible. The bottom-line goal is to design a system that meets the operational requirements, maximizes efficiency, and yet remains cost effective.

4.2.1 Unified Communication System (UCS) Servers:

The contractor will provide the core processing for all Cisco Voice over Internal Protocol (VoIP) calls at KADENA AB. The UCS core systems are defined and implemented on software created Virtual Machines under control of the physical host platform. The platform shall be JITC approved, robust, and allow the operation of dual independent power supplies required by ASLAN.

4.2.2 Media Gateway Routers:

The contractor will provide an interconnection point to deliver PRI remote trunking to the PSTN, DSN, FTS, and on-base PBX’s. The Media Gateway Routers will provide onboard Digital Signal Processors CODECS to packetize analog voice traffic and PRI ports for physical connectivity, and allow installation of additional PVDM CODECS to both the main chassis and the selected ISDN-PRI Modules. The Media Gateway routers shall be JITC approved, robust, and allow the operation of dual independent power supplies required by ASLAN.

4.2.3 Voice Gateways:

Analog device connectivity will be provided using Cisco Voice Gateway (VG-450) series placed centrally at Kadena DCO B400 and B3518 Primary VoIP Core. The JITC-certified VG Analog Gateways will be used to connect Off Premises Extension (OPX) lines, analog phones, fax machines, modems, and intercom systems to the Unified CUCM Cluster for management and support of legacy services. The contractor shall provide an interconnection point legacy analog phones (Wall phones, fax, STE) and the UC network. The device to perform this function shall capable of supporting at least 144 POTS lines per device.

4.2.4 Subscriber End Instruments:

User end phone instruments will be selected as the latest models available and listed on the DoD JITC System under Test (SUT) for CM version deployed. A mix of different models to be installed are defined as follows (Ref Appendix A):

· High End Models: models with full HD screen, and maximum capacity of hard line buttons.

· Mid End Models: models with and at least a six hard line capacity. Advanced functions are not critical, but features should fit the model range for mid-tier.

· Basic Models: models with and at least a two hard line capacity. This level should have availability to all call virtual services, but does not require advanced features or graphics capability.

· Administrative Assistant Models: models with full HD screen, Bluetooth disabled, and include the optional Sidecar for maximum capacity of hard line buttons.

· Conference Phones: i.e. Conference Polycom model Soundstation IP 6000 or equivalent.

NOTE: The 1,500 VoIP phones units will be installed and 2,880 POTS users will be supported through VG-450s in facilities determined by 18th CS during project walkthrough.

4.3 Ancillary Services: Defined as a capability vs a platform; ancillary services are primary virtualized and provide critical services to the customer.

4.3.1 Tele-Conference Capability:

Conference Capability will be provided by built-in UCS BE7M-M5-K9 Conferencing applications suite.

4.3.2 American with Disabilities Act (ADA) –Title I/II:

The UC system shall have an existing capability to integrate End Instrument IP based communications devices providing ADA “auxiliary aids and services”. These capabilities must include devices or subsystems that permit at a minimum the use of 1) assistive listening systems and devices; 2) open captioning, closed captioning, real-time captioning, and closed caption decoders and devices; 3) telephone handset amplifiers, hearing-aid compatible telephones, text telephones (TTYs) , and other voice telecommunications products. The UC system must be capable of interoperating with the Telecommunications Relay Service (TRS) to enable use of TTY end user equipment. No ADA Devices are implemented in this installation, but the contractor must certify that the UC system is compliant and can directly integrate ADA devices.

5.0 SYSTEM MIGRATION - VOICE CORE SYSTEM UPDATE

The contractor will EFIT&P to update all existing UC Core system equipment and hardware platforms in B400 and B3518, and pre-configure the equipment to facilitate the operational migration tasks in the subsequent stage.

5.1 PHYSICAL CORE EQUIPMENT REQUIREMENTS/LOCATIONS:

5.1.1 Building 400 Dial Central Office:

5.1.1.1 Building 400 installation of Media Gateway Routers.

The contractor will work with Kadena voice technicians to accurately assess the number of PRIs between the MSL-100 and the Media Gateways and also internal Kadena PRIs trunk connected to MSL-100, required for the migration in order to provision sufficient Network Interface Modules (PRIs and T1s NIM) to accommodate future needs. During government survey, it was found that there are 5 existing PRI trunk, two (2) VESTA E911 PRIs, and one (1) FSS Lodging (B332) DSN PRI between the MSL-100 and the 2 Media Gateways.

The suggested design for the contractor to consider is to distribute the PRI’s evenly between B400 (DCO) and B3518 (Primary VoIP Core). Both buildings each will have Media Gateways (two for B400, and one for B3518) equipped with sufficient PRI/T1 interfaces and Digital Signal Processor (DSP) capability to support simultaneous complex bandwidth CODEC voice connections. The Media Gateways must be configured to load balance call loading across individual interfaces, as well as provide failover in the event of a single router failure (Ref. Fig. 1A).

The contractor shall coordinate with 18th SCX to replace the two (2) aging Cisco 2951 Media Gateways with two (2) JITC certified Cisco C8300s with sufficient Digital Signal Processor (DSP) resources, PRI/Clear Channel Modules/Ports, Onboard RAM, and FLASH Memory and ports to support up to 40 T1s/PRIs circuit capacity including Ethernet (for SIP trunking). The Media Gateways shall have approved IOS software with license activated, with installed DoD PKI certificates on all nodes. Both Media Gateways will be configured to connect up to 24+ PRI/T1 connections in addition to the 5 PRIs trunks to the MSL-100, the one (1) VESTA E911 PRI, and FSS Lodging PRI. Each connection shall have description and labeling on each interface to reflect proper connection ID. The Media Gateway will be connected to KADENA AB Local Area Network and current Nortel MSL-100, with all pre-configuration tasks completed to facilitate future PRI trunk cutover.

The contractor shall provide sufficient primary and auxiliary power to meet ASLAN requirements. Each of the voice gateway power supplies should be fed with separate feeder branch circuits from the main panel; different routers may share electrical feeder branch circuits, but in no case should a single chassis have both power supplies on the same branch circuit. Voice Gateway Routers must be properly bonded to the rack grounding system using a separate chassis connection.

NOTE: The Voice Gateways shall also be configured with SIP capability to support DISA and KDDI local SIP trunks.

5.1.1.2 Building 400 installation of UC servers BE7M-M5-K9 Release 14 or Latest JITC certified Version The contractor shall coordinate closely with 18th SCX to replace the existing UC Physical Server with two (2) UC BE7M-M5-K9 Release 12.5 and update it to latest release 14 or latest JITC certified Version. The installed and configured UC Virtual Servers Systems will be configured as the cluster Secondary Core that span between this building and B3518 (Primary Core). This location will provide the UC System with 5,000+ KADENA AB telephone endpoint UC services, voicemail services, and provide the capability to load share with UC servers, and have the capability to absorb full user load should a failure occur to servers located at the Primary Core (Ref. Fig. 1B).

Each of the server platform's power supplies should be fed with separate feeder circuits from the main panel; different servers may share electrical feeder circuits, but in no case should a single chassis have both power supplies on the same circuit. Server Platforms must be properly bonded to the rack grounding system. Server platforms and virtual machines will be connected to KADENA AB Local Area Network with ASLAN redundancy, VLANs configured, Certificates installed, licenses activated.

The contractor will work closely with the 18th SCX administrators to ensure a smooth integration of the platforms into the network domain and security framework.

5.1.1.3 Building 400 installation SBC (Session Border Controller).

To run SIP (Session Initiation Protocol), an SBC (session border controller) is needed to provide JITC certified AS-SIP voice trunks with the purpose of replacing PRI’s. With Kadena in the plan to incorporate SIP trunk in this TDM migration, there is an intent to implement a mix of SIP trunks and PRIs before complete migration to VoIP. However, with an unclear schedule of SIP trunk acquisition from DISA and KDDI, full SIP implementation is not certain. With it, a reliance on a separate Air Force program to implement an IP based VPS (a requirement for AS-SIP trunking) to external service providers may hinder this progress. It is proposed that the contractor to assume availability of SIP trunk and install and configure the procured GFE Cisco 4300 Session Border Controllers (SBC) at this location (B400), with sufficient SIP licensing to accommodate Kadena planned SIP requirements - (2) two DISA SIP Trunks for DSN and 2 KDDI SIP trunks to the CUCM. It is also proposed that the contractor may offer a temporary PRIs solution should SIP trunks are not yet available.

5.1.1.4 Building 400 installation Voice Gateways VG-450.

Kadena AB has identified approx. 2,880 POTS users across Kadena facilities. The contractor shall procure, install and configure up to twenty (20) VG-450s and modules with the capability of 144 analog endpoints each, to support POTS users. The JITC-certified VG-450s will be used to connect Off Premises Extension (OPX) lines, analog phones, fax machines, modems, and intercom systems to the Unified CM Cluster for management and support of legacy services. 18 CS shall install sufficient Multi-pair cables with Amphenol RJ21, ready for the contractor to connect to the network Voice Gateway equipment. Although there are ample space available, the exact intra-facility equipment locations, MDF Cable Lengths, and available cable trough/tray availability will be finalized during facility walk-through.

The Voice Gateways VG-450s will also be connected to KADENA AB Local Area Network, VLANs configured, Certificates installed, and licenses activated. Cutover of analog phone circuits will occur with coordination from 18th SCX.

5.1.2 Building 3518 Primary VoIP Core:

5.1.2.1 Building 3518 installation of Media Gateway Router.

The contractor shall coordinate with 18th SCX to install one (1) JITC certified Media Gateway Cisco C8300s with sufficient Digital Signal Processor (DSP) resources, PRI/Clear Channel Modules/Ports, Onboard RAM, and FLASH Memory and ports to support the projected T1s/PRIs circuit capacity including a future expansion of 25%. The Media Gateways shall have approved IOS software with license activated, with installed DoD PKI certificates on all nodes. The Media Gateway will be configured to connect to the two (2) Media Gateways in B400 for redundancy (Ref Fig. 1A). In addition, with the Motorola E911 Core relocated to this location, a VESTA PRI from the E911 Core will be connected to this Media Gateway for redundancy. Each connection shall have description and labeling on each interface to reflect proper connection ID. The Media Gateway will be connected to KADENA AB Local Area Network and current Nortel MSL-100, with all pre-configuration tasks completed to facilitate the future PRI trunk cutover.

The contractor shall provide sufficient primary and auxiliary power to meet ASLAN requirements. Each of the voice gateway power supplies should be fed with separate feeder branch circuits from the main panel; different routers may share electrical feeder branch circuits, but in no case should a single chassis have both power supplies on the same branch circuit. Voice Gateway Routers must be properly bonded to the rack grounding system using a separate chassis connection.

NOTE: The Voice Gateway shall also be configured with SIP capability to support DISA and KDDI local SIP trunks.

Fig. 1A

5.1.2.2 Building 3518 install UC Physical Servers Release 14 (or latest JITC certified version)

Kadena CUCM cluster currently provides call processing, user and extension management, session management, and voice capabilities. The Publisher (PUB), a required server in all CUCM clusters provides database services to all other subscribers in the cluster. The publisher server has full read/write access to the configuration database. In the new cluster configuration, it is proposed to stand up a Dedicated Publisher to prevent administrative operations from affecting telephony services (a Dedicated Publisher does not provide call processing or Trivial or Secure File Transfer Protocol (S/TFTP) services). It is recommended that the Dedicated Publisher for this solution be installed in Building B3518.

The Subscriber server has the Cisco Call Manager Service enabled and subscribes to the Publisher (to obtain a copy of the database information) also perform call-processing function, and can take all the Call Processing load since they will be configured in multiple nodes and backup each other in case of node’s failure. Devices such as phones, gateways and media resources can register and make calls only to servers with this service enabled.

Multiple call processing subscribers can be members of the same cluster. A CUCM cluster can supports up to eight call processing subscriber nodes (with 4 Subscribers in active mode only). The proposed design suggests six (6) call processing subscribers due to the requirement for full load failover between B3518 and B400. The subscribers are sized to support ~ 10,000 users with a 1:2 backup ratio (for every subscriber server there are two backup subscribers) and will support a maximum of 16,000 users.

A SFTP/TFTP subscriber performs file transfer protocol (used by Cisco IP phones) to obtain configuration files, and their softwares – without TFTP services, Cisco IP phones won’t be supported. It is proposed to configure at least two (2) TFTP or SFTP distributed across Physical servers in the cluster for redundancy (Ref. Fig. 1C).

The Cisco UCS servers runs an instance of the VMware ESXi hypervisor software to support the virtual machines that make up the virtual server components of the solution. Virtual machines are spanned across multiple servers and locations (B3518 and B400) for a configuration that provides both logical and geographic redundancy of the system, with no loss of service if one physical server or location suffers an outage.

The proposed solution (Ref. Fig. 1B) comprise of four (4) physical Cisco High Grade Business Edition servers to host all the UC applications and dependency services. The UC hardware virtualization solution will be sized to accommodate 25% expansion. This capacity is important to support future applications deployments and upgrades which may increased computing requirements.

The contractor shall install (in available rack space designated by 18th CS, location TBD) and configure UC Virtual Servers Systems as needed and designate this location as the cluster Primary Core site. The contractor shall coordinate closely with 18th SCX to replace the existing UC Physical Server with two (2) UC BE7M-M5-K9 Release 12.5 and update it to latest release 14 or latest JITC certified Version. The installed and configured UC Virtual Servers Systems will be configured as the cluster Primary Core that span between this building and B400 (Secondary Core). This location will provide the UC System with 5,000+ KADENA AB telephone endpoint UC services, voicemail services, and provide the capability to load share with UC servers, and have the capability to absorb full user load should a failure occur to servers located at the Secondary Core. This site will provide the UC System up to 15,000 KADENA AB telephone endpoint UC services, voicemail services, and provide the capability to load share with other UC servers, and have the capability to absorb full user load should a failure occur to servers located at other sites (Ref. Fig. 1B).

Each of the server platform's power supplies should be fed with separate feeder circuits from the main panel; different servers may share electrical feeder circuits, but in no case should a single chassis have both power supplies on the same circuit. Server Platforms must be properly bonded to the rack grounding system. Server platforms and virtual machines will be connected to KADENA AB Local Area Network with ASLAN redundancy, VLANs configured, Certificates installed, licenses activated.

The contractor will work closely with the 18th SCX administrators to ensure a smooth integration of the platforms into the network domain and security framework.

Fig. 1B

Fig. 1C

5.1.2.3 Building 3518 Building installation SBC (Session Border Controller).

To run SIP (Session Initiation Protocol), an SBC (session border controller) is needed to provide JITC certified AS-SIP voice trunks with the purpose of replacing PRI’s. With Kadena in the plan to incorporate SIP trunk in this TDM migration, there is an intent to implement a mix of SIP trunks and PRIs before complete migration to VoIP. However, with an unclear schedule of SIP trunk acquisition from DISA and KDDI, full SIP implementation is not certain. With it, a reliance on a separate Air Force program to implement an IP based VPS (a requirement for AS-SIP trunking) to external service providers may hinder this progress. It is proposed that the contractor to assume availability of SIP trunk and install and configure the procured GFE Cisco 4300 Session Border Controllers (SBC) at this location (B3518), with sufficient SIP licensing to accommodate Kadena planned SIP requirements - (2) two DISA SIP Trunks for DSN and 2 KDDI SIP trunks to the CUCM. It is also proposed that the contractor may offer a temporary PRIs solution should SIP trunks are not yet available.

5.1.2.2.1 Unity Voicemail Services on the new CUCM system

The contractor shall Configure Unity Voicemail application system utilizing virtual machines, the virtual machines will be on separate UCS platforms for redundancy. The contractor shall install GFE licensing, required DoD PKI certificates, and configure and activate integration with the new Call Manager. The contractor will also configure user Database integration, Auto-Attendant, Directory Handlers, Voice mail default (may modify as advises by the local system admins), and implement Information Assurance (IA) hardening actions identified in the MUDG. The contractor will insure that dial peers between the CM and Unity Voicemail (VM) system are sufficient to support the full VM user load.

5.1.3 Building 3518 Rm Tech Control area:

5.1.3.1 Install and configure Media Gateways in available rack/cabinet.

5.1.3.2 Remove existing VG-350s and install new VG-450 Analog Gateways. Install and configure Analog Gateway and modules with the capability to support 144 analog endpoints.18th CS shall install sufficient Multi-pair cables with Amphenol RJ21, ready for the contractor to connect to the network Voice Gateway. Exact intra-facility equipment locations, MDF Cable Lengths, and available cable trough/tray availability will be finalized during facility walk-through.

The Analog Gateway will also be connected to KADENA AB Local Area Network, VLANs configured, Certificates installed, licenses activated. Cutover of analog phone circuits will occur with coordination from 18th CS.

5.1.4 Building B626 MEDCOI

5.1.4.1 Building 626 installation UC BE6K Call Manager

The MEDCOI Unit in B626 has almost completely been VoIPed. 18th CS which served and maintained MEDCOI VoIP indicated MEDCOI has specialized Voice Application needs (T-Metrics system, Paging System, Admin users assessment and others) which create challenging tasking for the 18th CS to accomplish with limited manpower resources. As a result, it is proposed a solution which requires a method to form a separate VoIP enclave with MEDCOI and connect the enclave back to Kadena CUCM with security separation.

The contractor will EFI&P a JITC certified Cisco BE6K Call manager in MEDCOI B626 Remote TDM switch location with capacity approx. 600 users (a survey will be done by 18th CS to validate VoIP user and POE’s switch count). MEDCOI’s DSN connection will trunk back to B400 for DSN service and may likely involve firewall/Gateway equipment for security. As MEDCOI will O&M the Call Manager and associate equipment (switches, VoIP phones and other supporting equipment) an MOA will be needed to further define responsibility between MEDCOI and 18th CS prior to contract implementation.

6.0 TRUNK MIGRATION- OPERATIONAL TRUNK MIGRATION

6.1 Physical T1/PRI Circuit Re-home:

Currently all external T1/PRI trunks (DSN, FTS, Local KDDI) entered thru DISA PoP in B400, to the Main Distribution Frame (MDF), traverse the VPS System, the DSX Patch Panel, and terminate in the Nortel SL-100 system via wire wrap terminals (in the DTCI Cabinets Line Modules). These trunks support external Local PSTN, DSN, FTS long distance…to bring voice services to Kadena AB. As Part of the TDM Migration, these endpoints may be rehomed to the Voice Media Gateways routers if SIP trunks are not yet available.

If SIP trunks are unavailable, the contractor will coordinate with 18th CS to engineer and carefully plan the migration/rehome of external DSN trunk from MSL-100 to the VoIP Gateway(s) router to insure proper VoIP Gateway operation.

In addition to external PRI trunks, the contractor will also coordinate with 18th CS to engineer and carefully plan the migration/rehome of internal PRIs/T1s from MSL-100 to Voice Media Gateways – It is the responsibility of 18th CS to provide all active trunk cut-sheet (to and from MSL-100) for the contractor to evaluate and engineer the re-homing solution.

Re-homing task for the contractor involves configuring descriptions on each T1/DS1 interface reflecting circuit ID, configure PRI and analog station ports accordingly, update Call Manager dial plan, implementing Information Assurance (IA) identified in MUDG meeting UCR 2013 Errata 1 IA and STIG requirements (Network and VVOIP) and performing Operational and Compliance tests with Checklist verifications.

7.0 TRAINING REQUIREMENTS:

The Contractor will provide on-site delivered training to Communications Squadron Personnel.

Training will be delivered by a Certified Instructor. On-Site Classroom Facilities will be provided by the 18th Communications Squadron. Classroom Student size will be 6 seats minimum.

Recommended topics should cover basic and advanced operation of the CUCM, Media Gateway router, Session Border Controller, Voice Gateways to include but not limited to:

· Move-adds-changes of telephone instruments

· Performing backups, restoring from backup

· Configuring Voicemail boxes

· High level troubleshooting techniques

· Performing administration of system records

· Configuration of Analog/Digital trunking, SIP trunking

· Advanced dial plans

· Command line advanced troubleshooting

· ESXi Kernel configuration

· VMware Virtual Machine creation using Vendor Templates, and the software upgrade process.

To comply with the on-site delivery, the following are required from 18th CS:

- Kadena AB will provide the classroom with projector, which includes all power and network connectivity requirements.

- A remote lab will be used for this delivery and will require an internet connection. Connectivity test will be conducted prior to the start of the class.

- The contractor will provide a Certified Instructor, all authorized learning materials, and access to lab equipment.

- Cisco’s standard format is digital copies of course material.

- Scheduling to be determined jointly by The contractor and 18th CS

8.0 GENERAL ENGINEERING REQUIREMENTS

Upon contract award and in response to this SOO, the contractor shall engineer the physical and logical modifications and connectivity described herein. The Contractor shall provide basic engineering and development. This includes any needed drawings and plans.

Final installation configuration shall meet best practices following telecommunications industry standards, best practices specified in the BICSI TDMM, standards of the National Electrical Code NFPA 2018 or latest version, and strict adherence of all vendor equipment installation practices.

8.1 Base Support

The Contractor shall identify any base support requirements (for example, power requirement, lay-down and storage areas) necessary to complete this project in their proposal. The Contractor shall return all government furnished lay-down and storage areas to their original condition upon completion of the project.

Kadena AB Points of Contact (POC):

Name: MSgt Wilkinson, Brian Organization: 18th NCOIC, KADENA AB Phone: 315-632-3215 or DSN 634-7999 Email: brian.wilkinson.6@us.af.mil Address: Bldg 3417, Kadena AB, Kadina Cho Okinawa, Japan 904 0200

9.0 INTEGRATED PRODUCT TEAM

The contractor shall chair a weekly IPT meeting consisting that includes Contractor representatives, the Government Contracting Officer (CO), the CSI-B, the System Engineer(s), Kadena POCs, Kadena CS Project Manager and other base personnel as required. The Contractor shall provide an agenda and a worldwide “Meet Me” teleconference capability for the duration of the projectand government representatives. The purpose of this meeting is to discuss project progress, problems being encountered, and other discussions necessary/beneficial to ensure success and timely completion of the Task Order. The contractor shall be responsible for the taking and distributions of the meeting minutes within one workday of each meeting. A copy of the minutes shall be provided to each attendee and disseminated via e-mail addresses.

9.1 Service Outage Coordination

The Contractor shall be responsible for preventing any unscheduled Contractor-caused interruptions of service. The Contractor shall coordinate planned outages with the site POC at least 2 workdays in advance of the outage if the implementation necessitates disruption of service, (e.g., communications, electrical, or other utilities).

9.2 Project Management

The Contractor shall provide a Project Manager (PM) who is a US citizen responsible for contract performance and continuity. The Project Manager shall physically be on-site for the duration of the project. The Contractor shall identify the Project Manager’s range of authority to act for the Contractor relating to daily contract operation.

9.3 Site Point of Contact (POC)

The Contractor shall designate the Contractor's on-site team leader and alternate(s) as the Site POC for individual projects in their Site Visit Request Letter. The Site POC or alternate(s) shall be on site during duty hours until project completion. The Site POC shall be the interface for all work site communications with the Government, including quality, safety, and discrepancy matters. The site POC and PM may be the same individual.

9.4 Personnel Requirements

The Project Manager, Site POC, and respective alternate(s) shall be able to read, write, speak, and understand English.

The Contractor shall ensure their employees and those of their subcontracts have the proper credentials allowing them to work in Okinawa, JP. Persons later found to be undocumented or illegal aliens will be remanded to the proper authorities.

10.0 WEEKLY STATUS REPORT

Contractor activities shall be documented weekly and submitted in a weekly Status Report (WSR). The WSR shall include but is not limited to the contract number, task order number, project number, brief task description, a narrative review of work accomplished during the reporting period and/or significant events, damaged utility occurrences, deliverable process, any problems areas and anticipated activity for the next reporting period. Contractor format for the WSR is acceptable, subject to Government acceptance. Distribution of the WSR shall be made to those individuals of the weekly IPT Meetings. (CDRL A003)

· Meetings Minutes & WSR IPT Agenda:

Contractor shall record minutes from weekly IPT meetings. Minutes should include any communication involving action items, resolved issues, and unresolved issues not already recorded in the WSR Agenda. The contractor will also submit the Weekly WSR Agenda in conjunction with the weekly IPT minutes. (CDRL A004)

11.0 SYSTEM TESTING

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's installation manuals, practices and the appropriate vendor's test procedures.

After appropriate corrective action has been taken, all tests including those previously completed related to the failed test and the corrective action shall be repeated and successfully completed prior to government acceptance.

Pre-cutover inspections shall consist of verification of all testing completed by the contractor such that the system is deemed ready for functional cutover.

Acceptance test shall verify that all post-cutover testing has been performed satisfactorily in accordance with the standard practices and identify those tests.

The contractor shall provide a logical test process that minimizes…