PBX ITN Specifications 042023.docx

USF Private Branch Exchange (PBX) Invitation to Negotiate

ITN #2023-076-ITN-PRO

1. Introduction In order to maintain university operations, the OneUSF Information Technology (IT) Telecommunications team needs to provide operable telephony services to multi-Campus users while meeting regulatory requirements for life and safety. Given the current age of the USF Private Branch Exchange (PBX), the USF IT team has identified the need to conduct research for a modern PBX.

The university began using Microsoft Teams for individual user phone capability nearly two years ago. There are currently approximately 7,000 Teams users. These users do not need to be supported by the proposed PBX solution. Users not in the Microsoft Teams environment include approximately 1,000 VoIP users and 2,500 analog users split into roughly 1,300 phone users, roughly 200 elevator lines, roughly 270 fire panel lines, roughly 150 security alarm lines, and roughly 700 fax lines.

Presently, USF has an on-premises PBX running Avaya System Manager 6.3. The university operates dual Oracle Enterprise Communications Broker (ECB) and Oracle Session Border Controller (SBC) in a high availability instance. Voicemail for analog users is provided by the university via Cisco Call Manager. The USF IT Telecommunications team is piloting analog media gateways capable of operating with any PBX.

Therefore, USF is seeking a replacement PBX, whether on-premises or cloud-based with on premises backup capabilities for E911 and essential services, that will provide the following:

· Integration with existing ECB and SBC appliances

· Integration with SIP supported vendor-agnostic media gateways/analog telephone adaptor (ATA)

· Call tracing to include malicious call tracing

· Analog dial tone

· Voicemail

· Automatic Call Distribution (ACD) with remote agent capability

· Limited on-premises survivability during internet outage and/or power outage

· Number masking

· Call logging

· Robust suite of analytics and reporting tools

· Call Detail Reporting

· Contact Center/Agent Statistical Reporting

· Robust troubleshooting and system log analysis tools

· Advanced Diagnostics Tools

· Bulk request support and/or Application Programming Interface (API)

· Configuration management auditing

· Class of restriction/cost group policy

· Support for legacy and modern trunking Other considerations that could be supported including but not limited to:

· Cradle-to-grave call tracing to include call transfers

· Bulletin announcements of pre-recorded messages accessible by call-in number

· Emergency notifications I.e., panic button notifications, public address announcements

· Support for long distance/international user access codes for billing purposes

· Customizable music/announcements while call is on hold

2. Information Requested Please provide a detailed description of the following in your responses:

A. Firm’s approach to integration of legacy analog telephony technology with modern unified communications capabilities.

B. Firm’s approach to availability of life safety phone lines C. General requirements for proposed solution(s)

1. Analog dial tone

2. Voicemail

3. Survivability D. Technology requirements, i.e., hardware and software.

E. Technology used in proposed solution(s) F. Hosting options, cost benefit analysis, and advantages and disadvantages of each.

G. Overview of recommendations on the timeline and resources needed on part of both USF and firm for implementation.

H. Firm’s background and at least 3 applicable references for solutions presented, preferably from an institution similar in size to USF.

I. Detailed price/fee structure (estimated) for each recommended solution.

1. Hardware

2. Software

3. Maintenance

4. One Time Costs

5. Annual Costs J. Additional comments, suggestions, recommendations, and creative ideas.

K. Interface requirements and ability for optional solutions. Name particular telephony systems for which your firm has implemented such interfaces.

L. Insurance maintained

3. Evaluation Criteria – Not Weighted A. Price/fee structure B. Responses to additional information requested in section 2