SOW bldg 673 access control.pdf
PDF 39 KB Posted
- Attached to
- Bldg. 673 Access Control
- Solicitation number
- FA252124QB098
About this file
This document is a Statement of Work (SOW) for an Electronic Access Control System for Building 673 at Patrick Space Force Base in Florida. The key requirements include:
The contractor shall provide and install all necessary hardware and system components to electronically monitor the primary and 3 secondary entrances to Building 673. The access control system shall be stand-alone, electronically identify and record individuals accessing the facility via proximity cards or PIN codes, and allow the user to assign/revoke access. The system must maintain a log of all individuals accessing the facility for at least 30 days and be capable of supporting up to 100 proximity cards/PIN codes. The contractor shall provide all cabling, connectors, and associated hardware, as well as a design plan, project schedule, and user training. A one-year warranty is required on all equipment and 90 days on labor. The project schedule must be pre-approved to work around potential launch operations at the facility.
View the file
Other files
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
Statement of Work (SOW) Electronic Access Control System for
39th RQS, bldg. 673, Patrick space Force Base, Florida
Tasks and Deliverables
1. The Contractor shall purchase and install an electronic access control system capable of supporting Building 673 with the below specifications/details:
1.1. The Contractor shall provide and install all necessary hardware and/or system components to electronically monitor the primary and 3 secondary entrances vicinity Rm
1.2. The access control system shall be stand-alone with no alarms required.
1.3. The access control system shall electronically identify and keep a record of individuals accessing the facility via proximity cards/ assigned PIN codes and when (date and time) they enter.
1.4. The user shall be able to electronically assign/revoke proximity cards/PIN codes for authorized user access from a Contractor provided workstation located in Building 673 Room 102.
1.5. The door strike shall release and allow entry when an authorized user presents their proximity card/ PIN code. All doors must remain secure until authorized user(s) are entering/exiting the facility.
1.6. The access control system shall allow for multiple users to access the facility by allowing them to swipe/tap their card consecutively while keeping a log of all individuals.
1.7. The user shall be able to download, and/or store on the system, an electronic record of individuals who have accessed the facility for a minimum of 30 days.
1.8. The access control system shall be capable of supporting 100 proximity cards/ PIN codes simultaneously.
1.9. The door strike shall remain in the locked position in the event of a power failure and when power is reapplied.
1.10. The existing door handles shall remain and have a key override in the event of power failure. Should any door handles require replacement, they shall be keyed to accept the facility master key.
Statement of Work (SOW) Electronic Access Control System for
39th RQS, bldg. 673, Patrick space Force Base, Florida
2. The Contractor shall install the necessary high and low voltage cabling and connections required to operate the system.
3. The Contractor shall provide all cabling, connectors and associated hardware required for the installation tasks listed above.
4. The Contractor shall deliver a design plan and project schedule with the proposal.
5. The Contractor shall support one (1) design review prior to procurement and installation.
6. The Contractor shall provide a warranty period of no less than 1 year on all equipment and 90 day for labor associated with the new electronic access control system. The Contractor shall include technical support during this warranty period.
7. The contractor shall provide user training for operating the system.
8. The contractor shall provide configuration information for facility documentation.
Additional Consideration:
Project schedule must be pre-approved to work around launch operations which are sometimes fluid. Contractor must remain flexible for potential schedule slips, which may occur with little notice. Installation tasks cannot be performed during launch operations.
File details come from the government source that posted it. Updated .