20-5247 RFP AMD3.docx

DOCX document 225 KB Posted

Attached to
PUBLIC SAFETY ANSWERING POINT (PSAP) SYSTEM (UW-MAD)[20-5247]
Solicitation number
20-5247
Issued by
Dane County, Madison City, Wisconsin

About this file

This is Amendment #3 to Request for Proposal (RFP) 20-5247 issued by the University of Wisconsin-Madison Purchasing Services for a Public Safety Answering Point (PSAP) System for the UW Police Department. The amendment was issued on October 23, 2019, with a revised due date of November 5, 2019, at 2:00 PM CST. The RFP seeks proposals for a comprehensive PSAP system to replace or upgrade the University's current public safety dispatch operations. An optional site visit was held on October 2, 2019. Questions and clarifications were submitted by potential bidders, and Amendment #3 addresses these inquiries along with providing Attachment D containing additional technical information about the University's current infrastructure. Proposal prices and terms must remain firm for sixty (60) days from the proposal submission date to opening.

The current environment includes UW-Madison's migration to an on-premise, redundant, and co-located Cisco Unified Communication Manager (CUCM) VoIP system with approximately 18,000 migrated lines, complemented by approximately 5,000 remaining AT&T Centrex analog and ISDN lines. The University operates two on-premise, redundant AudioCodes Mediant 4000 Session Border Controllers (SBCs) connected to AT&T IP Flexible Reach SIP trunking service and subscribes to Intrado Emergency Gateway (EGW) and Intrado Emergency Routing Service (ERS) for 911 call routing and E911 location information. The UWPD dispatch currently uses IDS Mindshare Dispatch Consoles and operates as a secondary PSAP to Dane County. Proposers are invited to submit system options for redundancy, including standalone backup operations, remote call handling capabilities via laptop positions, and disaster recovery solutions. Building UPS power and generator backup are available for system use.

View the file

Other files

File Type Posted
20-5247 Attach C - Specifications.xlsx XLSX spreadsheet
20-5247 RFP AMD1.docx DOCX document
20-5247 RFP.docx DOCX document
20-5247 Attach B Cost Sheet.xlsx XLSX spreadsheet
20-5247 RFP AMD 2.docx DOCX document

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

AMENDMENT #3

Proposal No. 20-5247

UNIVERSITY OF WISCONSIN

MADISON, WISCONSIN 53715-1218

Amendment #3 to Request For Proposal

THIS IS NOT AN ORDER

OFFICIAL SEALED

Proposal Number: 20-5247

NO PUBLIC OPENING

AMD #3 Issue Date: 10/23/2019

Due Date: 11/05/2019 2:00 PM CST Agent: Melissa Viken

Questions regarding this proposal – see Section 2.7 For Submittal Instructions & Proposal Response Format – see Section 2.2 and 2.3

Proposal prices and terms shall be firm for sixty (60) days from the date of the proposal to the opening, unless otherwise specified in this Request for Proposal by the UW-Madison Purchasing Services.

If NO BID (check here) ☐ and return.

20-5247 / AMENDMENT #3 / PUBLIC SAFETY ANSWERING POINT SYSTEM

Amendment #3 is issued to respond to proposer submitted questions and to provide Attachment D – Additional Information.

If this amendment is not returned, it shall be assumed your original bid meets all conditions of the amendment.

All other terms and conditions remain the same. Please revise and submit your bid accordingly.

In signing this bid, we have read and fully understand and agree to all terms, conditions and specifications and acknowledge that the UW-Madison Purchasing Services bid document on file shall be the controlling document for any resulting contract. We certify that we have not, either directly or indirectly, entered into any contract or participated in any collusion or otherwise taken any action in restraint of free competition; that no attempt has been made to induce any other person or firm to submit or not to submit a bid; that this bid has been independently arrived at without collusion with any other bidder, competitor or potential competitor; that this bid has not been knowingly disclosed prior to the opening of bids to any other bidder or competitor; that the stated statement is accurate under penalty of perjury. I certify that the information I have provided in this bid is true and I understand that any false, misleading or missing information may disqualify the bid.

By submitting a bid, the bidder certifies that no relationship exists between the bidder and the University that interferes with fair competition or is a Conflict of Interest, and no relationship exists between such bidder and another person or firm that constitutes a Conflict of Interest. Further, bidder certifies that no employee of the University whose duties relate to this request for bid assisted the bidder in preparing the bid in any way other than in his or her official capacity and scope of employment.

The Bidder certifies by submission of the bid that neither it nor its principals is presently debarred, suspended, proposed for debarment, declared ineligible, or voluntarily excluded from participation in this transaction by any federal department or agency.

Company Name:

Company Street Address:

Company City, State & Zip:
Date:

Signature:

Type or Print Name:

Title:

Telephone Number: ( )
Fax Number: ( )

Email address:

Fein Number :
DUNS #:

AMENDMENT #3 to RFP 20-5247 (PSAP): Questions and Answers

Q1Would the University consider a two-week extension to the RFP Due Date for Proposal No. 20-5247?
A1The RFP due date has been extended to 2:00 PM on Tuesday, November 5, 2019.
Q2Could you please indicate us the model of the Orbacom radio consoles currently in use at your facilities?
A2IDS Mindshare Dispatch Console
Q3Does the University have an onsite ALI database? If not, are there ALI Modems currently in use for ALI dips at the moment? If so, which model is currently used?
A3Please see Attachment D-Additional Information. For the VoIP lines, we have two on-premise, redundant, and co-located Intrado Emergency Gateway (EGW) appliances and we subscribe to the Intrado Emergency Routing Service (ERS) for 911 call routing. For the remaining Centrex lines on campus, we currently upload location information (as room-specific as possible) through our AT&T Centrex service to Intrado via PS-ALI.
Q4Specification No. 16 in the compliance table talks about (sic) “a secondary location in different facility for backup operations”. Does the University have a backup location?
A4Currently the UW-Madison PD has not engaged with having a backup solution, however is looking for all options or parts of a system. Please provide system capabilities or limitations in regards to redundancy to include stand alone and or a backup off site operation. (This could include laptops for offsite work if backend is still intact, it could include full redundant operations, and it could include connections to a cloud based system or connections to another local system.) All proposal options of fulfilling redundancy will be considered.
Q5Is the University requesting remote call handling capabilities provided with use of Laptop positions?
A5Please see Answer 4. If your company has and would provide a line item for a backup solution or laptop position for disaster mode please feel free to include that as an option. All proposal options of fulfilling redundancy will be considered.
Q6In specification No. 19 – Could you please kindly confirm us the following line counts?
A6Administrative analog lines – We have 5 current analog lines, all lines will be ported to VoIP with this project

Ring down lines – We currently have 3 ring down lines, Dane County Communications, UW ER, UWER Prison Ward PBX (Provider)? Please see Attachment D- Additional Information. UW-Madison is currently migrating most of our telephone service to an on-premise, redundant, and co-located Cisco Unified Communication Manager (CUCM) VoIP system. We have migrated approximately 18,000 lines. Most of these lines are for hard phone users. We also have some Cisco Jabber soft phone users. We have approximately 5,000 remaining AT&T Centrex analog and ISDN lines remaining. These remaining lines are primarily for elevator phones, blue light phones, other emergency phones, and fax lines, although we are in the process of moving as many of these lines to VoIP as possible too.

Q7Does the University want 3rd Party SIP integration? Or PRI integration?
A7We intend to convert administrative and non-emergency lines to the UW-Madison VoIP system (they are currently Centrex analog and ISDN lines) and will want to integrate these lines with your system.PRI integration should not be needed.
Q8In specification No. 25 – What is meant by “ … central network management software.”?
A8We are requesting that the system in some way or shape including audibly have the ability to notify our stations that there is an outage. If there is a main system that is monitored or connected to remotely for more information please include this as well. Our onsite setup calls for the core of the system to reside in a completely separate area, separated by floors and isn’t readily accessible by dispatchers.
Q9In specification No. 39 – Is this request for CPE System Monitoring? Typically we would see network monitoring request with a multi-site or ESInet proposal.
A9We have some capability to do that internally with our Cisco VOip System. Describe your solution’s capability in this regard.
Q10No. 61 – Could you please kindly expand on what is requested, the request seems unfinished. What does “…C.O. based Centrex On-Line Help” means in this context?
A10Centrex is a specific name of our phone line system, we are requesting the ability for each workstation to have a form of online or hard coded help in case of issue where the dispatcher could look.
Q11Does the University require a geo-diverse solution? This would be a redundant system installed in two different locations. In Attachment C – Specifications, number 16 states there is a backup site; however, number 19 states that the solution should be for one (1) PSAP location.
A11Please see Answer 4 above. All proposals and costs for potential redundancy will be considered.
Q12Are light towers required?
A12Light towers are currently in place by our radio vendor, if those cannot be utilized then yes we would like light towers
Q13Is a KVM (keyboard and mouse arbitrator) required?
A13Not necessary
Q14Are Genovation keypads required?
A14Yes
Q15Is a printer required?
A15This is not necessary as long as reports from the system can be saved in a standard file type for printing elsewhere.
Q16Are calls recorded digitally, via analog, or both?
A16Currently calls and Radio traffic is recorded using MacTek Highergrounds technology.
Q17Is call recording line-based, position-based, or both?
A17Current call recording is line based and will continue to be line based, however post vendor picked for this RFP, a new recording system will be bid on to be compliant with our PSAP Provider.
Q18Is there a building UPS available for use?
A18Yes, and it would be on a plug that has UPS power. The department also has a generator. Please indicate in your RFP response if your system would need specialty power sources.
Q19Who is the Local Exchange Carrier (LEC) for the University?
A19See Attachment D- Additional Information. AT&T is the LEC. UW-Madison subscribes to AT&T IP Flexible Reach Session Initiation Protocol (SIP) trunking service. AT&T provides our Centrex service for remaining analog and ISDN lines. UWPD dispatch is connected via AT&T CAMA Trunk to receive E911 location information.
Q20Who is the ALI database provider for the University?
A20See Attachment D- Additional Information. For the VoIP lines, we have two on-premise, redundant, and co-located Intrado Emergency Gateway (EGW) appliances and we subscribe to the Intrado Emergency Routing Service (ERS) for 911 call routing. For the remaining Centrex lines on campus, we currently upload location information (as room-specific as possible) through our AT&T Centrex service to Intrado via PS-ALI.
Q21Is the database NENA-compliant? Is the ALI database local?
A21See Attachment D- Additional Information. The database is NENA-compliant. For the VoIP lines, we have two on-premise, redundant, and co-located Intrado Emergency Gateway (EGW) appliances and we subscribe to the Intrado Emergency Routing Service (ERS) for 911 call routing. For the remaining Centrex lines on campus, we currently upload location information (as room-specific as possible) through our AT&T Centrex service to Intrado via PS-ALI.
Q22Will the University please provide additional details regarding the actual number of ‘other lines’ in the police department:
A22Please see above
Q23Is there a requirement for SIP integration to a separate admin phone system? Or T1/PRI integration?
A23For the remaining Centrex lines on campus, we currently upload location information (as room-specific as possible) through our AT&T Centrex service to Intrado via PS-ALI.
Q24Does the University require any administrative/business phones to be served by the 911 solution? If so, how many?
A24Please see above
Q25Does the University plan on moving the PSAP in the near future (one to two years after installation)?
A25No

AMENDMENT #3 to RFP 20-5247 (PSAP):

Attachment D: Additional Information Campus Telephone System:

· UW-Madison is currently migrating most of our telephone service to an on-premise, redundant, and co-located Cisco Unified Communication Manager (CUCM) VoIP system. We have migrated approximately 18,000 lines. Most of these lines are for hard phone users. We also have some Cisco Jabber soft phone users.

· UW-Madison currently uses two on-premise, redundant, and co-located AudioCodes Mediant 4000 Session Border Contollers (SBCs).

· UW-Madison subscribes to AT&T IP Flexible Reach Session Initiation Protocol (SIP) trunking service with two redundant and co-located trunks that connect to our two redundant and co-located AudioCodes SBCs. (NOTE: Our Intrado ERS service described below currently does not use these trunks.)

· We have approximately 5,000 remaining AT&T Centrex analog and ISDN lines remaining. These remaining lines are primarily for elevator phones, blue light phones, other emergency phones, and fax lines, although we are in the process of moving as many of these lines to VoIP as possible too.

VoIP E911 Location Information with Intrado EGW and ERS

· For the VoIP lines, we have two on-premise, redundant, and co-located Intrado Emergency Gateway (EGW) appliances and we subscribe to the Intrado Emergency Routing Service (ERS) for 911 call routing.

· Our network switches are scanned and location information (as room-specific as possible) is uploaded to the EGWs throughout the day.

· For most WiFi users, location is specific to the location of the WiFi router that they are using.

· NOTE: Currently, our voice calls and location information are sent to Intrado via our campus Wide Area Network (WAN) and the commodity Internet, and not via our AT&T IP SIP trunking service.

AT&T Centrex E911 Location information with AT&T/Intrado PS-ALI

· For the remaining Centrex lines on campus, we currently upload location information (as room-specific as possible) through our AT&T Centrex service to Intrado via PS-ALI.

UWPD and AT&T CAMA Trunk

· UW-Madison Police Department (UWPD) dispatch is connected via AT&T Centralized Automatic Message Accounting (CAMA) Trunk to receive E911 location information from the 911 Selective Router.

· UWPD dispatch is a secondary Public Safety Answering Point (PSAP) to Dane County which is the primary PSAP. E911 calls and location information must be able to be transferred between PSAPs, and Dane County PSAP is the backup for UWPD PSAP.

image2.png image1.png

File details come from the government source that posted it. Updated .