12-EB-2026 RFP Q A.pdf

PDF 105 KB Posted

Attached to
Integrated Employee Badge Management Solution
Solicitation number
EB-2026 RFP
Issued by
Cherokee County, Georgia

About this file

This document is a Questions and Answers record for RFP 12-EB-2026, an Integrated Employee Badge Management Solution solicitation issued by the Cherokee County School District (CCSD) in Georgia. The project encompasses a comprehensive, district-wide card access badge solution requiring credential production and reissuance for approximately 14,800 employees by June 30, 2026. The scope includes system compatibility verification, reader flashing, badge template design (8 different templates required), and delivery of finished badges for distribution across the district. Vendor Convergint Technologies submitted requests for clarification on March 18, 2026, with responses provided by the District on March 19, 2026. The project involves integration with the District's DNA Fusion identity management system and existing Mercury board infrastructure, which will not be replaced. The District plans to support MIFARE credential technology across MT15 readers, with non-MT15 readers to be addressed as optional pricing items.

The District confirmed no bonding requirements are necessary for this project. The credential system must accommodate multiple applications across the district, including employee ID cards designed to interface with existing systems such as proximity readers, legacy barcode systems (3 of 9 format), Kronos timeclocks, school lunch programs, transportation software, and copier systems. The District will maintain responsibility for ensuring the credential database remains current for each school year. A DTC 4500E badge printer will be utilized, with specifications to be provided separately. A limited number of readers with keypads at gates require PIN replacement as part of this implementation. All questions must be submitted through the Euna Procurement Message Center.

View the file

Other files

Show all 11

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

Generated on Mar 20, 2026 9:27 AM EDT - Paula Hilton

Vendor Discussions

Convergint Technologies

Convergint RFIs

Olivia Beck, Mar 18, 2026 3:43 PM EDT

Please see the following list of questions for the District for this RFP. 1. Is the District's intent to rebadge & reissue credentials for 14,800 employees by June 20th, 2026? 2. Is the District looking to integrate its credential management system into its existing identity management system? If so, what identify management software is the District currently using? 3. Does the District intend to replace existing Mercury boards? (eg. if the Mercury boards are green, they are end of life & must be updated to the latest secure boards.) 4. Do all of the existing MT15 readers support MIFARE credentials? 5. What does the District intend to do with the non-MT15 readers? How many of these readers exist? They will need to be replaced in order to support MIFARE. 6. Will there be any bonding requirements for this project? 7. Do any of the existing readers have key pads to be used for multifactor identification purposes? Will those pins need to be replaced as a part of this project? 8. What credentials are used for other systems in the District - Kronos Timeclocks, school lunch programs, transportation software, district copier systems? How do they communicate? (eg. barcode, prox, mag strike, card access system interface) 9. Who's responsible for ensuring the current credential database is up to date & correct for the next school year? 10. How many different badge templates are required? 11. What features is the existing badge printer capable of? What is the DTC 4500E capable of? Does it encode the cards? Can it print single or double sided?

Paula Hilton, Mar 19, 2026 11:25 AM EDT

1. Yes, by June 30th 2. DNA Fusion 3. No 4. Yes, this is the card we currently have. 5. Please price as optional as a per reader number. Provide this information under Any Misc. & Additional Charges not Listed on Proposal Form. 6. N0 7. Just a few at gates, the pins will need to be replaced. 8. 1. Employee ID, but can vary since we don’t currently use badges on all those systems. The goal is employee ID, and use custom rows/records on the card that can be encoded when needed. 2. Proximity with some legacy time clocks using 3 of 9 barcode. 9. CCSD 10. 8 11. Pull the spec sheet on printer.

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