Purchase Description FD Dispatch.pdf

Purchase Description

Upgrade The 115th Fighter Wing Fire Department Dispatch Console

Truax Field, WI ANG Building 430, 3110 Mitchell Street Madison, WI 53704-2591

1. All requirement descriptions below state desired functionality. The dealer shall be responsible to determine what additional components, hardware, etc. will be necessary to deliver a fully functional system. This includes mounting hardware, racks, cables, and any other item that may be necessary but is not specifically mentioned. Offers will be evaluated for completeness and quality.

2. Minimum Requirements are listed below:

Replace the core and PC workstation Fire Department Dispatch Console (MCC 5500), with a new system to include adding recorder equipment, integrating pre-existing and additional radios, integrating garage door controls, integrating building PA, and adding digital/analog/VOIP phone lines tied into the system.

Dispatch Console Requirements

- The system shall replace the pre-existing PC Console and Core System.

- This system shall support all legacy and new radio makes and models owned by the government.

- This system shall support analog, digital, and VOIP phone capabilities that will tie into it.

- Replace the non-functional NICE recorder with something equivalent to integrate it into the system to record voice for auditing and investigations.

- The system shall be wired into the building Bogen PA and be activated through the PC console microphone for building announcements.

- The system shall have the Fire truck garage door opener buttons integrated into the PC Console touch screen.

The control panel which operates the doors is located in room 126, Communications closet. Currently, when there is an emergency, the Fire Dispatch operator has to run to the door control panel, leaving the dispatch center, and manually control the doors. This takes a lot of time, and more importantly takes the operator away from critical communications functions at the E911, Monaco, and console position.

To streamline this, the Fire Department leadership would like this functionality and control to be moved to the new console.

- All components of the system that require a Hard Drive shall have Solid State Hard Drives with the maximum recommended Solid State Drive space from the contractor.

- Console software shall operate under Windows 10 64-bit operating systems. The console position equipment shall connect to the system gateway via 100BASE-T Ethernet to access endpoints or other consoles. T1, E1, or other non-Ethernet based connectivity is not acceptable.

- The console GUI shall be configured by administrator software to include system control buttons, audio level controls, and endpoint resources. All aspects of the console presentation and operation parameters shall be configured from the administrator software and downloaded to the console position. Both 4:5 and 16:9 (wide-screen) format displays shall be supported.

- The software IP media processor shall provide the operator audio, all peripheral interfacing for footswitch, headsets, desk microphone, and speaker audio. The IP media processor must be configurable to support interfaces for a select and up to 10 unselect speakers, up to four microphone devices (headset or desk microphones), and a footswitch. The IP media processor shall be capable of processing and presenting 250 channels of audio simultaneously.

- The IP media processor shall be capable of automatically transcoding between different audio CODECs. At a minimum, G.711, G.729a, and G.726 CODECs shall be provided with the system. The media processor shall perform audio mixing for the console patching function. The design shall support a minimum of five (5) simultaneous patches per console. The patch function shall not cause a busy state in the console and shall allow the console operator to perform other duties while the patches are active.

- Audio peripherals shall be connected to the IP media processor using industry standard USB connectors. Additionally, USB connected relays shall be available to provide workstation state indications to external display devices.

- The system shall have a hardware-based radio consolette accessory available as an option. The consolette shall support at least 4 radio endpoints with individual receive volume controls, inbound audio indicators, and PTT switches for each along with a shared microphone and speaker. The consolette shall support transmit and receive audio and PTT on any type of radio endpoint defined in the system and have a programmable display that can be used to identify the endpoints. Power for the consolette shall be PoE to minimize the physical footprint.

- The following native IP-based endpoints shall be supported via direct IP interface from the system gateway to the endpoint.

P25 Conventional radios via the P25 DFSI standard (TIA-102.BAHA);

exclusive use of proprietary protocols will not be acceptable.

P25 Trunked Radio systems via the P25 CSSI standard (TIA-

102.BACA); exclusive use of proprietary protocols will not be acceptable.

MOTOTRBO Conventional radios (IP Site Connect) via direct IP connectivity to the repeaters; control station interfaces are not acceptable.

MOTOTRBO Trunked radios (Linked Capacity Plus), single or multi-site, via direct IP connectivity to the repeaters; control station interfaces are not acceptable.

MOTOTRBO Trunked radios (Connect Plus) via direct IP connectivity to the system controller; control station interfaces are not acceptable.

MOTOTRBO Trunked radios (Capacity Max) via direct IP connectivity to the system controller; control station interfaces are not acceptable.

TaitNET MPT1327 Trunked Radio systems.

Session Initiation Protocol (SIP) telephony directly to Cisco, Avaya, and third-party IP-PBXs.

Daniels Universal Interface Card (UIC) protocol.

Harris EDACS via IP connectivity; control station interfaces are not acceptable.

Harris OpenSky via IP connectivity; control station interfaces are not acceptable.

ICOM iDAS Conventional and Trunked radios via direct IP connectivity;

control station interfaces are not acceptable.

Kenwood NEXEDGE Conventional and Trunked radios via direct IP wireline connection; control station interfaces are not acceptable.

Tier II DMR radios via the Application Interface Specification (AIS) standard, control station interfaces are not acceptable Tier III DMR radios via the Application Interface Specification (AIS) standard; control station interfaces are not acceptable.

ED-137 radios via direct IP wireline connection; control station interfaces are not acceptable.

PTT over Cellular via direct wireline connection; control station interfaces are not acceptable. Supported vendors shall include Motorola Wave, AT&T Enhanced PTT, Verizon PTT Plus, and Cisco Instant Connect.

- The following endpoints shall be supported via serial tunneling over IP from the RoIP endpoint to the system gateway.

Sytech iSpace Nextel control station radio Sprint Direct Connect control station radio Harris M7100 control station radio General Dynamics URC-200 radio Motorola XPR 5000 Connect Plus control station radio Motorola APX 1500/4500/6500/7500 P25 control station (conventional and trunked) Tait TM8255 control station radio Tait TM9155 control station radio Tait TM9300 control station radio Tait TM9455 control station radio Kenwood TK-5710 control station radio Kenwood NX-5000 NXDN control station radio (conventional and trunked) Kenwood NX-700/800 NXDN control station radio (conventional and trunked) Kenwood NX-5000 P25 control station radio (conventional and trunked) SmartNet/SmartZone control station radio

- The system shall support direct IP connection to the Harris EDACS system. The proposed system must support the group call, inbound emergency group call, and PTT ID with alias features at a minimum.

- The system shall provide a single administrator software application that provides for remote configuration and diagnostics for consoles, gateways, and endpoints. The administrator software shall support user authentication to prevent unauthorized access. The administrator software shall support live “push” configuration changes from a centralized database to any or all console positions without requiring users to log off. Systems that require individual, local console position configuration shall not be acceptable.

- Every screen element, from graphical backgrounds to pad sizes, colors, and fonts, must be configurable by the administrator software. It shall be easy to design, maintain, and deploy new console screens using the software.

- The administrator software shall provide a user login capability for security. User login authentication shall be maintained with the administrator software, or alternately users can be authenticated using Windows Active Directory. Each configured login shall provide varying levels of access for each component of the maintenance tool. The access levels shall be No Access, Read-only Access, or Full Access.

- As an option, the system shall offer a feature that allows multiple, individual console system deployment sites to be administered from the same centralized software. Administrative access to the different sites shall be set on a per-user basis.

- As an option, the administration software shall offer a tool that allows editing of multiple endpoints at the same time to reduce administrative effort in a large system deployment.

- The proposed system shall generate SNMP traps to enable monitoring by 3rd party SNMP management software. The system shall allow up to four SNMP manager destinations to be configured.

- Support for Session Initiation Protocol (SIP) for connection to VoIP telephony systems and gateways is required for Administrative telephony functions. Both SIP Extensions and SIP Trunks shall be supported. Console positions shall be capable of displaying resource icons on the user interface that map to telephony extensions. Console positions shall treat telephone extensions similarly to radios.

A console may have multiple endpoint (“phone endpoint”) appearances on its screen and allow multiple phone calls to be active simultaneously. Calls may be active, put on hold and patched to other phone endpoints and/or radio endpoints.

Calls shall also be allowed to be monitored in an Unselect speaker without disconnecting the call. Extension status shall be visible to all consoles. Consoles shall not be restricted to one “phone patch.”

- The gateway shall register each endpoint (extension) directly with its corresponding SIP proxy server and provide connectivity to any or all consoles.

Each endpoint may reside on different IP-telephony devices and the gateway shall support multiple proxy servers.

- The console position shall include a contact database with a minimum capacity of 10,000 entries. Contacts may be members of groups, which shall be available to offer quick access to related contacts. Multiple phone number entries shall be supported on a per contact basis. Alpha-numeric search strings shall be supported enabling rapid identification within the contact database. Inbound Caller ID shall be capable of referencing the contact database when displaying the caller’s name and number to obtain the latest information.

- Telephony functions shall include recall dial tone, call initiate, caller ID display (name and number) in the call queue, transmit caller ID, message on hold, missed call callback, and patch status. Definable telephone hunt groups shall be supported on a per-system, per-console and per-contact basis.

- The system shall support the ability for multiple consoles to select the same telephone endpoint. Up to ten consoles shall be able to join the conversation.

Each telephone endpoint shall be configurable to allow/disallow the barge-in capability. If configured, consoles shall have the capability to activate a privacy feature to prevent other console from joining the call. Consoles shall have the option to place designated telephone endpoints in a Do Not Disturb mode to silence and re-route inbound calls. Additionally, each telephone endpoint shall be configurable for Push To Speak capability.

- The Message on Hold function shall use a WAV file to play a recorded message to telephone endpoints put on hold. There shall be the ability to change the WAV file to one supplied by the console system administrator. Each telephone endpoint shall be set independently for its message WAV file.

- The system shall support a NENA compatible E911 headset sharing interface on a per console position basis. This shall consist of a dedicated four-wire, 600 ohm audio connection and a signaling input to the console to indicate the telephone desk set is off-hook. The console position shall automatically enable the E911 audio to the operator headset and permit simultaneous radio operation. The NENA headset interface shall incorporate an echo reduction function to eliminate reflected audio on less than optimum telephone connections.

- Additionally, SIP phone endpoints shall be configurable to provide */# keying to support radio operations via telephone connections.

- The dispatch console shall have the capability to transmit different alarm tones, (minimum of three separate tones to choose from), through selected radio channels as well as transmitting alarm tones through the building PA system.

The operator shall be able to separately select or select groups of which equipment that they want the alarm tones to transmit to.

The alarm tones shall be labeled

- When installing the Dispatch Console system, the contractor shall ensure that they do proper cable management practices to include labeling (which include labeling of equipment, cabling, and wires), color coding, and wiring for all cable connections going from the equipment to the demarc. This will ensure that local maintainers can identify cable paths for troubleshooting and upgrades.

Also include reorganizing the layout of the radios and equipment that will be tied into the core system in room 126 so that it is easily maintained by technicians and contractors. Also include the labeling requirements listed above for all radio equipment, paging, and phone systems tied into the core system.

- The Dispatch station shall have the capability to be networked.

- The Fire Department shall have an additional portable PC Console that can be networked to the Core system in the main building from another location incase Fire Department members have to evacuate their facility and go to their secondary location.

Note the customer would like to operate the portable PC Console at the same time as the Main PC Console if required.

The customer would like the Core System to have the capability to be networked to a local base server for backing up historical documentation to include an additional network port to connect the portable PC Console to it.

Dispatch Center, Room 124 Communications Closet, Room 126

Current Core System set up in the Communications Closet room 126

Building Paging (Bogen): located in room 126

Copper wire connections located in the room 126. (Note: Fiber and Ethernet is available)

UPS

Currently, there is an Eaton 9355-30 UPS in the Comms Room 126, which is supplying UPS for the Comms Room and Dispatch Center.

Old logging recorder (NICE): non-functional and is located in room 126.

PC Console: Located in the Fire Department Alarm room 124. (MCC 5500)

- The PC Console Requirements Shall have the latest licensed GUI, operating system (Windows 10 64 bit), and firmware/software updates prior to the installation and setup of the system.

After the system has been installed, future firmware and software updates shall be easily acquired by Communications flight Radio technicians and be installed on the Dispatch Console if required.

The system shall have security software enabled to include, firewall and anti-virus.

Shall be upgradable At a minimum, provide at least one preferably two high quality 21.5”

LCD touch screens for the PC console (16X9) format.

The duel LCD touch screens could show the same information on each display or could be expanded displays to have greater room to show all functionalities of the system.

Shall provide a minimum 9 ft. PTT handset and a wired desktop handset cradle for the PC console

Prefer to have the capability to have two microphones so that multiple operators could communicate on different radios at the same time if needed during a crisis.

Shall provide a USB Desk Mic Shall provide at a minimum, dual speakers

Preferably, have a dedicated speaker assigned to each radio that is wired to the system to have better awareness of radio communications.

Shall have backup operating software disk(s) for GUI, Operating System, and Core System to go back to initial customer configuration incase the system crashes. This backup system software will be managed by the Communications Flight Software Managers.

The contractor shall create a system backup disc after the system has been configured for the customer.

The PC Console shall be tied into the building PA system to make building announcements as required.

The PC Console shall have an easily maintained log entry journal on the main screen for Fire Department member shift change notifications of any new information and can be backed up and archived for historical records.

This shall require a keyboard and mouse integrated into the PC Console besides having touch screen capabilities.

o Also include an additional keyboard and mouse for the portable PC Console.

Critical phone lines shall be integrated into the PC Console for quick communications response.

Preferably, the operator would like a separate speaker and/or handset dedicated to each phone line integrated into the system so it does not tie up the speakers to monitor radio communications.

o The handset shall have a PTT button to secure background sensitive communications in the Fire Department Alarm room.

The system shall have the capability to either support analog, digital, and VOIP phone capabilities.

Due to multitasking, the customer could miss which radio did the last transmission. The customer would like an indication on the GUI of the PC Console to identify which radio(s) transmitted last in the order from latest to last. Would like a list that would populate up to the last 5 transmissions. In that list, it would identify which radio transmitted.

The customer would like the capability to continuously record the previous last five transmissions and be able to replay them if it was missed.

- Core System Shall have the latest licensed GUI, operating system, and firmware/software updates prior to the installation and setup of the system.

After the system has been installed, future firmware and software updates can be easily acquired by Communications flight Radio technicians and be installed on the Dispatch Console if required.

The Core System shall be upgradable The Core System shall be installed in a rack or case in the communications closet and shall be in the highest point to prevent dust and debris kick-up to maintain longevity of the system.

The case or rack can be anchored in the floor of the Communications closet.

The Following phone lines and radios listed below shall be integrated into the Core System and can be easily operated from the PC Console.

This system shall support P25 and legacy and new radio makes and models.

Radios o The MCC 5500 currently has 11 radio and IP assets which will include two additional radios during this installation.

Tactical Air (General Dynamics URC-200, [New Radio requirement]) Adam County (Motorola APX 7500, [New

Radio requirement]) Fire Dispatch (Tied to the Motorola Quantar repeater through copper wire)

Civil Engineers (Tied to the Motorola GTR 8000 repeater through copper wire)

Aircraft Maintenance (Tied to the Motorola GTR 8000 repeater through copper wire)

Security Forces (Tied to the Motorola GTR 8000 repeater through copper wire)

PA System (Tied to the Bogen Paging System through copper wire)

County Paging Radio Air-Rad Ops Airport airfield operations

(Motorola XPR 4350) MSN airport Tower (IC-A210 Radio) MSN airport Ground (IC-A110 Radio) City Madison Admin (Motorola 700/800 Mhz

APX 7500 consolette) City Madison MED TAC ORG (Motorola

700/800 Mhz APX 7500 consolette)

Currently, the 115th Fire Department does not have any telephony integration, but would like the following to be integrated into the new system and also tied into the new logging recorder.

o Secondary Crash o Army Crash (tied to Army Guard unit adjacent to the

115th, but still on Truax Field) o Security / BDOC o Airport Operations o Munitions Storage Area (MSA) o Another line (245-4561) which occasionally gets emergency calls These phone lines are currently on the Avaya phone system

- Recorder The current NICE recorder has been inoperable for many years, but as a part of the new console upgrade, the Fire Department needs to implement a new logging recorder. Although they had used NICE in the past, they are not partial to NICE because of costs, and are open to other manufacturers.

Preferably, this recorder shall be integrated into the PC Console touch screen for ease of use by the customer. If so, the main recorder equipment shall be installed in the Communications closet with the core system.

If the recorder cannot be integrated into the PC console, Then the main recorder equipment shall be installed in the Communications closet and tied into a kiosk that will be stationed in the Fire Department Alarm room with the PC Console.

The recorder shall have a main Solid State Hard Drive, (SSHD), with the maximum recommended space to record voice communications for multiple radios and/or phone lines that will be tied into the Dispatch Console.

The recorder shall have a backup SSHD within the system to store voice recordings and for redundancy.

The voice recordings shall be easily edited through tools within a GUI and extracted by the customer via thumb drive or CD/DVD rom disc for historical record and audit tracking on a different computer if required.

Training shall be provided to include step for step training documentation for the customer doing this task.

Spare Equipment

- Additional speakers or Dual speaker kit

- USB Desk Mic

- Spare handsets for the phone support

- Any other backup/redundant equipment recommended by the contactor

Technical Support

- Shall have no charge software maintenance

- Shall have 24/7 technical support and web portal access. This is due to 24/7 fire department operations and affects safety of life.

- Shall have a maintenance program by the contractor for all hardware acquired by the customer in this contract.

- Shall have a factory warranty on all components acquired for this contract.

Operator and Maintenance Training o The contractor shall provide clear-cut step for step hands on training and digital documentation for all equipment provided in this contract. All digital documentation will stay with the customer(s) for reference and continued operator and maintenance training in PDF format to the following groups.

- Operator Training Fire Department users

Step for step Operator documentation and hands-on training

- Maintenance Training

Communications Flight Radio Technicians

Step for step Operator operation documentation and hands-on training

Step for step maintenance Documentation and hands-on Maintenance Training o This will include annual Preventive maintenance training of the system.

Step for step operator Documentation and hands-on System Administration Training o To include admin and additional passwords

Critical Items:

a. None