BPK-18-166-RFB-Questions and Answers from Vendors.pdf
PDF 91 KB Posted
- Solicitation number
- BPK-19-166
- Issued by
- Wisconsin
About this file
This document is a Questions and Answers record from a Request for Bid (RFB# BPK-18-166) issued by the University of Wisconsin Oshkosh for a comprehensive parking management system. The project requires vendors to provide a License Plate Recognition (LPR)-based parking management system with permit management, mobile LPR enforcement capabilities, online and mobile payment processing, and system management accessible remotely. Key equipment and service deliverables include equipping two vehicles (one 2017 Suzuki Busy Badger and one 2013 or newer Ford Interceptor SUV) with LPR hardware and software, providing enforcement licensing for two LPR-equipped vehicles and two Android-compatible devices, supplying four thermal printers compatible with handheld mobile ticketing devices, and providing a minimum of six licenses for parking management software. The RFB specification requires that all work be performed within the United States, which is a mandatory compliance requirement for bidders.
The current parking management environment at the University utilizes EDC-AIMS software (implemented since 2011) for parking system management and Total Parking Solutions Cale pay stations for payment processing. The RFB indicates that data conversion may be requested, potentially encompassing multiple years of historical parking data. Vendors must ensure the system includes electronic help functionality, geotag capability to track vehicle locations and identify parking trends by lot and time of day, automated citation and warning issuance integrated with LPR cameras, ticket book inventory controls, and system-wide alert capabilities for permit holders via email and text messaging. The incumbent vendor is EDC-AIMS, which previously performed data migration services during the current contract award.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| BPK-18-166-RFB-Parking Management System for UWO Parking Office_06_15_2018.pdf |
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
RFB# BPK-18-166 PARKING MANAGEMENT SOFTWARE
VENDOR QUESTIONS/ANSWERS
1. Can you please confirm 6.8 Purchased Service-USA Requirement. would disqualify any vendor from bidding since there would be work performed outside of the United States?
ANSWER: This is a requirement of the bid.
2. Please explain the status of the RFP released in 2017?
ANSWER: The University did not release an RFP for a Parking Management System in 2017.
3. What is the make and model of both the smart phone and the in-car laptop?
ANSWER: Smart phone should be any Android mobile device, we currently have Google Pixel phones. Our current in-car laptop is a Panasonic Toughbooks (CF-31)
4. Does the University have a preference of a one piece handheld with an integrated printer, handheld and separate printer or a smart phone and separate printer?
ANSWER: Yes, the specified Bluetooth printer must sync to an android mobile phone device.
5. How many tickets are written annually?
ANSWER: This varies annually, included in the RFB document (Attachment C) is data from July 1, 2016-June 30, 2017.
6. Who is the current vendor?
ANSWER: EDC – AIMS.
7. If data conversion is requested, how many years?
ANSWER: We currently use EDC-AIMS software (since 2011). EDC migrated our T2 data into the current database when awarded the current contract.
8. Whose pay stations are in use today?
ANSWER: Total Parking Solutions – Cale.
9. Please explain what you mean by, Available electronic resources for system functionality.
ANSWER: We expect that the system has an electronic help functionality to clarify information and troubleshoot the system.
10. Please explain the process you need to facilitate tracking officer’s daily activities, work output with associated hour per task or activity. Would a generated report meet this need?
ANSWER: Tickets issued should have a geotag enabling us to track, show and display where a vehicle was parked, or is parked at the time of citation. Geotags should also allow for us to identify trends in which lots are full depending on time of day and where a specific vehicle tends to park.
11. Please explain how you want to utilize the location of plates on campus based on geo-tags.
ANSWER: See answer to question 10.
12. Please explain what you mean by automated citation and warning issuance with integrated cameras.
ANSWER: A full functioning LPR system can automatically fill out the vehicle information so the officer only needs to select the ticket and print.
13. Please explain how you would use the ticket book inventory and control.
ANSWER: To track issuance and ticket rolls.
14. Please explain the process in which you would want the system wide alerts to go out to permit holders. Via text, email or both.
ANSWER: We would like to be able to send out email reminders to purchase permits. We would also want the ability to text our permit holders should there be a lot closure due to maintenance, weather or some other type of short-term issue that affects their ability to park.
15. Please clarify the number of each below:
• Equip two (2) LPR vehicles with necessary hardware/software:
o 2017 Suzuki Busy Badger (also known as Suzuki Hustler) street legal automobile o 2013 (or newer) Ford Interceptor SUV
• Enforcement licensing for two (2) LPR equipped vehicles and two (2) android compatible devices o Four (4) thermal printers that work with handheld mobile ticketing devices (specifications in 6.4)
• Minimum of six (6) licenses for parking management software
ANSWER: Vendor must provide the Parking Marking functionality with the specifications identified within the bid document, including the above requirements.
File details come from the government source that posted it. Updated .