Download Alternative Procurement ADDENDUM Number 3 TITLE: Enterprise

ALTERNATIVE PROCUREMENT
ADDENDUM Number 3
TITLE:
Enterprise Telephone System Upgrade/Replacement
DATE ALTERNATIVE
PROCUREMENT OPENED:
April 13, 2012
DATE ADDENDUM NO. 3
ISSUED:
May 2, 2012
CONTACT PERSON:
Eric Fullar
Information Services
Phone: (541) 346-1015
Email: [email protected]
PURPOSE OF THIS ADDENDUM:
The purpose of this Addendum is to provide answers to the following questions that have been
received:
Question 1: Does the University have a preferred approach to this upgrade?
Answer 1:
We don't. However, the responses will be reviewed based on the criteria listed in the
solicitation. You are welcome to submit multiple responses that reflect different strategies.
Question 2: Can you provide me a layout of where the cabinets are on campus?
Answer 2:
Four MCC cabinets are at the same site, one is at a different site. All but two of the
G650 stacks are at different sites. None of the G650 stacks are colocated with MCC cabinets.
Typically, each G650 or MCC site serves a number of nearby buildings. Switching from Avaya analog
circuit packs to newer analog gateways might introduce some challenging technical hurdles in that the
TN764 analog ports have a range exceeding 10kft and newer analog gateways are typically less and
might not be rated for use on OSP cable runs. The University runs alarm panel reporting on analog
circuit packs and has NFPA requirements for backup power. We want to avoid having to install new
DC power systems with long run times in more locations.
Question 3:
Answer 3:
Are the analog circuit packs spread across the 650's and MCC's?
Yes.
Question 4: Do you want to migrate to 6.0 or go to 5.2.1?
Answer 4:
The University has an ESLP/SS agreement with Avaya that expires in September of this
year. Barring an immediate forklift upgrade to a different platform, we were anticipating a CM 6.x
upgrade this summer, but await the outcome of this procurement before making a final decision.
Addendum 3 – Enterprise Telephone System Upgrade/Replacement
Page 1 of 3
Question 5: Are you using fiber connectivity between the cabinets? Where are the 700's located,
what physical locations etc.?
Answer 5:
All MCC cabinets, G650 stacks and G700s are connected with an IP network. The
G700s are located at three remote sites. Specific details will be shared with vendors who submit
responses the University decides to investigate further.
Question 6: Will all the digital phones be retained?
Answer 6:
That depends on the vendor responses we receive. Our overall priorities are discussed
in the procurement document. As far as the digital sets and circuit packs — the TN2224 circuit packs
are still supported by Avaya, as are the 2420 sets. The 6400 and 8400 sets are not. If we decide to
replace digital sets, we will start with the 8400 and 6400 sets. Typically, we'll convert a building at a
time to IP phones and then re-deploy the 2420 sets to whichever buildings remain without IP sets.
Question 7: How are DS1 circuits distributed between MCC cabinets and G650 stacks?
Answer 7:
(1) is in a G700 gateway
(8) is in a single G650 stack
(18) are in MCC cabinets
Some Trunking circuit packs were added as the procurement document was being assembled. Please
use the larger number. We also use DS1 circuit packs as backplane synchronization sources for MCC
and G650 cabinets that don't have trunking. Those circuit packs are not included in these numbers.
Question 8: Do you have a drawing of the existing network?
Answer 8:
No — the campus data network includes many hundreds of devices and is a little
difficult to squeeze into a single drawing. From a security perspective, it's also not information we want
to share as part of a public procurement process. If there are specific network configuration questions
which have a bearing on your response, we will try to get you answers to those questions. Please see
the original procurement document for details on network switches and security devices.
Question 9: Are you currently direct with Avaya or are using a vendor partner? If you are using a
vendor partner, can you share their name?
Answer 9: We currently have a maintenance agreement directly with Avaya, but it expires in
September of this year.
Question 10: Who are your main data providers for your network?
Answer 10:
We use a combination of Cisco, Juniper and HP network equipment.
Question 11: Is your data network virtualized?
Answer 11: Vlans are in use on our campus data network.
Question 12: Who is the University's Internet transit provider?
Answer 12:
Internet services, point-to-point data network services and SIP trunking services are not
included as part of this procurement. Our Internet transit and peering relationships should not have a
bearing on this telephone system procurement.
Question 13: If we aren't proposing a non-Avaya Solution, how would the requirement for options to
output E911 PS/ALI records be applicable?
Answer 13: The University needs to generate PS/ALI records for E911 reporting for all of its stations.
We already have a solution in place to generate PS/ALI records for Avaya Communication Manager
stations. We would need to install a similar solution for stations on a non-Avaya system.
Addendum 3 – Enterprise Telephone System Upgrade/Replacement
Page 2 of 3
Question 14: How many voice mail ports are active on the current AVST CallXpress system?
Answer 14: 69 DS0s with PRI signaling.
Question 15: Is it possible to get a breakdown of the number of analog devices (fax, modem) per
location?
Answer 15: It varies by building. We have 150 or more buildings. What we suggest is that vendors
provide some examples to give us a sense for costs to provision analog dial-tone using the solution that
is being proposed.
Question 16: Will the University issue LOA's to Avaya and/or the University's telecommunications
carriers so more details regarding existing telecommunications services and systems can be
researched?
Answer 16: No. The University feels it has provided sufficient detail in the original documents and this
Addendum to assemble initial responses. We anticipate that responses would need to be adjusted to
reflect detailed engineering work if the University decides to follow up on one or more responses. If
and when we get to this stage, we can reopen the question of LOAs for detailed engineering work.
The goal is for the University to get a good understanding of the overall technical capabilities,
advantages and costs of various solutions without requiring each vendor spend a great deal of time and
effort engineering a detailed solution.
With this in mind, responders are welcome to include caveats, assumptions and/or options in their
responses to reflect the absence of technical reports, traffic studies, telephone counts per building and
network configuration details. If there are more questions along the lines of what has been answered
here, please submit them to [email protected]<mailto:[email protected]> prior to the
close of this procurement.
Addendum 3 – Enterprise Telephone System Upgrade/Replacement
Page 3 of 3