2-Request for Information Questionnaire-GENEA.docx
DOCX document 45 KB Posted
- Solicitation number
- TCH2133147F1
- Issued by
- Florida
About this file
This is a Request for Information (RFI) Questionnaire issued by a Florida county to evaluate the Genea Security Access Controls System and determine whether the specified commodity is available from multiple providers or if alternate solutions exist that would meet the county's needs. The RFI is not a request for pricing or a purchase commitment. Vendors are instructed to complete the questionnaire through the BPRO Requested Information section, providing responses to differentiating requirements across four primary categories: badging integration, hardware and camera interoperability, system architecture and future-proofing capabilities, and operational redundancy. Vendors must identify their role (manufacturer/developer, authorized reseller, or other), propose their product or service, and include relevant specifications and supporting documentation. The questionnaire requires vendors to indicate whether their systems can meet specific requirements (Yes, Partially, or No) and provide explanatory details regarding any gaps or exceptions.
The RFI focuses on an airport security environment and evaluates vendor solutions against specific technical requirements, including integration with legacy security badges, compatibility with Amico brand readers and Cisco Meraki cameras, native integration with Splunk SIEM and OpenEye on-premise NVR systems, hardware-independence for future vendor flexibility, cloud-based architecture with disaster recovery capabilities, non-disruptive upgrade functionality, and scalability for future airport expansions. Vendors must also identify any material differences between their proposed solution and the identified product or service. No pricing information, contract term, renewal options, set-asides, incumbent information, or funding sources are specified in this questionnaire document.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 1-Supporting Documentation for Request for Information (RFI)-Genea.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
Request for Information Questionnaire Genea Security Access Controls System Vendor Instructions:
Provide responses to the questions below through the BPRO Requested Information section. Include any relevant specifications and/or supporting documentation related to the product you are offering. This information will be used by the County to determine if the specified commodity or service is available from multiple providers, or if an alternate commodity or service is available that would meet the County’s needs.
Response Information
| Vendor Name: |
| Click or tap here to enter text. |
| Proposed Product/Service: |
| Click or tap here to enter text. |
| Manufacturer/Developer: |
| Click or tap here to enter text. |
| Vendor Role: |
| ☐ Manufacturer/Developer ☐ Authorized Reseller ☐ Other: Click or tap here to enter text. |
| # |
| Differentiating Requirement |
| Response |
| Vendor Explanation |
1. Badging
| 1a |
| Can the platform integrate directly with the airport's existing legacy security badges. |
| ☐ Yes |
☐ Partially ☐ No
| Click or tap here to enter text. |
| 1b |
| Has the system been field-tested and verified within an airport's environment? |
☐ Yes ☐ Partially ☐ No
| Click or tap here to enter text. |
| 2. Hardware & Camera Interoperability |
| 2a |
| Does the software support the specific Amico brand readers required to read existing airport access cards and perform biometric functions? |
| ☐ Yes |
☐ Partially ☐ No
| Click or tap here to enter text. |
| 2b |
| Does the access control system natively integrate with the existing Cisco Meraki cameras deployed at the airport's security checkpoints? |
| ☐ Yes |
☐ Partially ☐ No
| Click or tap here to enter text. |
| 2c |
| Does the platform seamlessly integrate with the airport's existing security stack, including Splunk SIEM and OpenEye on-premise NVR systems? |
| ☐ Yes |
☐ Partially ☐ No
| Click or tap here to enter text. |
| 3. Architecture & Future-Proofing |
| 3a |
| Is the system non-proprietary and hardware-independent, allowing the airport to switch hardware vendors in the future without replacing the central management software? |
| ☐ Yes |
☐ Partially ☐ No
| Click or tap here to enter text. |
| 3b |
| Is the platform natively cloud-based, enabling seamless transition to backup locations for disaster recovery without moving physical hardware? |
| ☐ Yes |
☐ Partially ☐ No
| Click or tap here to enter text. |
| 4. Operation & Redundancy |
| 4a |
| Does the solution provide non-disruptive software upgrades that prevent system downtime during critical airport security functions? |
| ☐ Yes |
☐ Partially ☐ No
| Click or tap here to enter text. |
| 4b |
| Can the platform scale to support future airport expansions without requiring additional hardware expansion or infrastructure replacement? |
| ☐ Yes |
☐ Partially ☐ No
| Click or tap here to enter text. |
| 4c |
| Does the system combine cloud agility with on-premise backup to provide fine-grained, user- and group-based access control with real-time alerting? |
| ☐ Yes |
☐ Partially ☐ No Click or tap here to enter text.
Overall Equivalency / Exceptions Identify any requirement the proposed product/service does not fully satisfy and describe any material differences from the product/service identified in the RFI.
Click or tap here to enter text.
File details come from the government source that posted it. Updated .