2-Request for Information Questionnaire-Algo.docx
DOCX document 46 KB Posted
- Solicitation number
- TCH2133145F1
- Issued by
- Florida
About this file
This Request for Information (RFI) Questionnaire document, issued by a Florida county government entity, seeks to determine the availability of an Airport Mass Notification System from Algo Communications and whether comparable alternatives exist that would satisfy the county's operational requirements. The RFI is explicitly designated as a Notice of Intent to Sole Source/Sole Brand procurement and is not a formal request for pricing or a binding purchase commitment. The questionnaire format is designed to gather information from potential vendors regarding product availability, compatibility, and alternative solutions rather than to solicit formal bids or pricing proposals.
The document does not specify item quantities, response deadlines, site visits, bidders' conferences, award dates, or contract terms and renewal options. Similarly, no pricing information, set-asides, incumbent vendor details, funding sources, or budget amounts are disclosed in this preliminary information-gathering phase. As an exploratory procurement document, the RFI serves solely to establish whether sole-source justification is warranted before the county proceeds with formal acquisition procedures for the mass notification system.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 1-Supporting Documentation for Request for Information (RFI)-Algo.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 Algo Communications – Airport Mass Notification 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. System Compatibility & Integration
| 1a |
| Does the product integrate directly with Cisco Call Manager and the existing Algo VoIP/SIP infrastructure without middleware? |
| ☐ Yes |
☐ Partially ☐ No
| Click or tap here to enter text. |
| 1b |
| Is the hardware fully backwards-compatible and capable of direct integration with the 800+ existing Algo endpoints already deployed? |
| ☐ Yes |
☐ Partially ☐ No Click or tap here to enter text.
| # |
| Differentiating Requirement |
| Response |
| Vendor Explanation |
| 1c |
| Does the system support a unified native multicast architecture that maintains consistency with existing paging zones? |
| ☐ Yes |
☐ Partially ☐ No
| Click or tap here to enter text. |
| 2. Centralized Management |
| 2a |
| Can all deployed audio and visual endpoints be centrally monitored, configured, upgraded, and diagnosed through the Algo Device Management Platform (ADMP)? |
| ☐ Yes |
☐ Partially ☐ No
| Click or tap here to enter text. |
| 2b |
| Does the platform allow for complete lifecycle control of all devices from a single, centralized cloud interface? |
| ☐ Yes |
☐ Partially ☐ No
| Click or tap here to enter text. |
| 3. Hardware & Life-Safety Capabilities |
| 3a |
| Does the vendor offer unified audio/visual synchronization across mixed endpoints for high-noise environments? |
| ☐ Yes |
☐ Partially ☐ No
| Click or tap here to enter text. |
| 3b |
| Does the hardware feature deterministic failover paging and strobe activation profiles that align with airport engineering specifications? |
| ☐ Yes |
☐ Partially ☐ No
| Click or tap here to enter text. |
| 3c |
| Are the endpoints available in a unified, standards-based ecosystem that includes touchscreen-enabled emergency intercoms and satellite speaker technology? |
| ☐ Yes |
☐ Partially
Click or tap here to enter text.
| # |
| Differentiating Requirement |
| Response |
| Vendor Explanation |
| 3d |
| Can the hardware be deployed interchangeably in both indoor and outdoor terminal environments? |
| ☐ Yes |
☐ Partially ☐ No
| Click or tap here to enter text. |
| 4. Operational Impact & Risk |
| 4a |
| Can the new equipment be deployed without requiring the airport to re-engineer existing paging zones, reprogram controllers, or revise emergency workflows? |
| ☐ Yes |
☐ Partially ☐ No
| Click or tap here to enter text. |
| 4b |
| Will the deployment of these devices eliminate the need to introduce multiple separate software management tools? |
| ☐ Yes |
☐ Partially
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 .