Addendum No 2.pdf
PDF 143 KB Posted
- Attached to
- Fence Detection System
- Solicitation number
- 60486
- Issued by
- Prince George County, Virginia
About this file
This document is Addendum No. 2 to Request for Proposal (RFP) #878-24 issued by the Riverside Regional Jail Authority for a Fence Detection System. The addendum responds to questions from offerors regarding the project requirements. The system is required to provide zone-based intrusion detection along a fence line, with zones ranging from 100 to 175 feet. The system must integrate with existing video management or intrusion detection systems, or be priced as a standalone option. The customer does not require a mapping tool or graphical user interface, but the system must be capable of tuning out false alarms, autoconfiguring for different weather conditions, and having an open API for integrations. The system must also be deployable without requiring power along the fence perimeter.
The pricing and contractual terms are not explicitly detailed in this addendum. However, the addendum indicates that all other specifications and general terms and conditions remain the same, and the offeror must acknowledge receipt of the addendum in their proposal. Failure to do so may result in the proposal being deemed non-responsive.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Sign In.pdf | ||
| jail layout.png | PNG image | |
| 878_24 Fencing.pdf | ||
| Addendum No 1.pdf | ||
| Addendum No 3.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
Addendum No. 2
Date: March 19, 2024
Request for Proposal (RPF) # 878-24: Fence Detection System for the Riverside Regional
Jail Authority
Reponses to Questions Asked by Offeror:
1. Does the customer want a “zone” based system or a “pinpoint” intrusion detection system? If zone, what length or distance would be considered a reasonable zone? Zones will range between 100 feet and 175 feet.
2. Will the security fence detection system be integrated into an existing video management system (VMS) or intrusion detection system (IDS) for alarm notifications and response? If so, what VMS or IDS will the sensor need to integrate into? Integration with existing systems or as a stand alone system will be priced as options.
3. Does the customer require a mapping tool or graphical user interface (GUI) to manage the system? No, the proposed system will be referring to designated zones by existing building nomenclature.
4. Does the detection system need to be immune to radio frequency interference (RFI), electromagnetic interference (EMI), and lightning? Yes
5. Does the system need to be capable of tuning out false/ nuisance alarms (wind and rain) while maintaining the capability to detect climbs, cuts, and lifts? Yes
6. Does the system require “autoconfiguration” capabilities without the need for manual tuning and adjustments for different weather conditions and seasons? Yes
7. Does the system require an open application programming interface (API) to allow for easy integrations and interoperability between systems? Yes
8. Does the fence intrusion detection sensor need to be capable of being deployed in the field (along the fence line) without requiring power along the perimeter? Yes
9. Can we get a simple drawing of the facility? Such as the picture on the wall in the conference room that you use for a reference. See Attachment
All other specifications and General Terms and Conditions shall remain the same.
Proposers must take due notice and be governed accordingly. Acknowledgement of the receipt of this addendum shall be made in your proposal. Failure to acknowledge this addendum may result in your proposal being declared non-responsive
Acknowledgement
Signature: ____________________________________
Print Name: ____________________________________
Company: ____________________________________
Date: ____________________________________
File details come from the government source that posted it. Updated .