Badge RFP - Addendum 2.pdf
PDF 69 KB Posted
- Attached to
- GISD Badge System RFP
- Solicitation number
- RFP-GIS-250000002147-3
- Issued by
- Genesee County, Flint City, Michigan
About this file
This document is an Addendum 2 for the Genesee Intermediate School District's (GISD) Badge System Request for Proposals (RFP) for 2025, dated April 25, 2025. The RFP seeks a new badge and door access system, with the bid date remaining unchanged at May 2, 2025, at 3:00 PM. The addendum includes responses to specific questions about the proposed system, covering access protocols, firmware update procedures, and event tracking capabilities.
The document reveals GISD's current practices and requirements for the new badge system, including that staff without normal building access are currently buzzed in by main office personnel, system updates are scheduled with downtime, and they currently do not track specific door events like forced entry or tailgating. For the new system, GISD requires the ability to schedule on-premise updates with the vendor, assumes cloud-hosted systems will be automatically updated, and wants the capability to run on-demand reports for door access and security events.
View the file
Other files
Show all 12
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
Genesee Intermediate School District
Badge System RFP 2025
Addendum 2 dated April 25, 2025
The bid date for this Request for Proposals remains unchanged, May 2, 2025 at 3:00 PM. All other terms and conditions of the bid shall remain in full force and effect.
Questions via Email
1. When someone needs access to a building they don’t normally use, do you usually create a new badge, call the main office, or unlock it remotely from wherever you are?
a. Staff who normally do not access the building are asked to go to main entrance and be buzzed in by main office staff.
2. When your system needs a firmware update, do you usually schedule downtime, push it manually, or let it update automatically in the background?
a. Scheduled downtimes and then updated.
3. How would you want the new door system to work when it needs some kind of update?
a. If on-premise, updates should be scheduled with GISD Team and then the vendor would upgrade the system.
b. Assumption is that cloud hosted systems are updated automatically by the vendor and they would notify the district of updates.
4. Are you currently tracking events like door forced open, tailgating, or doors being held open? If so, how do you usually access that info—do you remote into a server, have someone on-site pull it, or search from your phone? And if you’re not tracking those today, is that something that would be valuable to have visibility into?
a. We have not had a need to track events like this. We currently run reports on demand as needed.
b. In a new system, we will need to be able to run reports on demand.
File details come from the government source that posted it. Updated .