Revision 3 Sept 3 2025 Base Cameras SOW Revised 3 Sep 2025.pdf
PDF 206 KB Posted
- Attached to
- Base Cameras, Columbus AFB, MS
- Solicitation number
- FA302225Q0320
About this file
This Statement of Work (SOW) details a security camera system upgrade for Columbus Air Force Base in Mississippi. The project involves replacing 14 existing cameras and installing 11 new cameras across various base buildings, totaling 25 cameras. The system specifications require 4K resolution cameras with AI-driven capabilities, including motion detection, human and vehicle recognition, license plate recognition, and trajectory mapping. The cameras will be a mix of outdoor (23) and indoor (2) installations, with mounting types including wall, pole, and ceiling.
The Video Management System (VMS) must provide a minimum of 30 days of video storage, with options for cloud-based or server solutions. The system must comply with Department of Defense cybersecurity standards, including Risk Management Framework (RMF) and Federal Risk and Authorization Management Program (FedRAMP) requirements. The contractor must integrate up to 40 existing Axis cameras into the new system, with a one-year base contract and four optional 12-month extension years. Installation must be completed within 60 calendar days of contract award, with a comprehensive performance test and training session for base personnel.
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
1 | P a g e
STATEMENT OF WORK (SOW)
FOR
SECURITY FORCES CAMERA
PURCHASE AND INSTALL
AT
COLUMBUS AIR FORCE BASE, MISSISSIPPI
Revised 3 September 2025
2 | P a g e
1. DESCRIPTION OF SERVICES:
Unless otherwise specified, the contractor shall furnish all personnel, transportation, equipment, tools, materials, and other resources required to:
• Provide, install, configure, and integrate a new Video Management System (VMS).
VMS should support the server with remote access or cloud-based video surveillance, enabling secure remote access to both live and archived footage. It should incorporate AI-driven analytics for rapid incident detection and search, as well as robust user management features, including role-based access controls and single sign-on capabilities.
• Provision and install servers or implement a cloud-based storage solution capable of retaining a minimum of 30 days of video recordings. For server-based deployments, equipment shall be housed in a floor-standing rack, supported by an uninterruptible power supply (UPS), with data transmission via fiber-optic connection.
• Install three (3) workstations or provide capability for administrators to log into the system virtually.
• Supply and install a total of 25 new cameras, including the replacement of 14 existing units and the addition of 11 new installations. Of these, 23 will be outdoor cameras and 2 indoor cameras. 16 cameras will be connected via the ethernet and any PoE injectors to the fiber gateway. The remaining 9 cameras will be powered via solar energy or by tapping into light poles with battery backup as needed and connected to the camera network via cellular gateways or point-to-point access points connected to the fiber gateway.
• Supply and install all necessary equipment and perform required configurations to integrate up to 40 existing Axis cameras into the operating system. These cameras will need to meet the requirements listed in paragraph 1.5.2, same as the newly purchased cameras.
1.1 Place of Performance: Columbus AFB, Columbus, MS
1.2. Contractor Required Deliverables
The Contractor shall provide, deliver, install, configure, update, and connect the items listed in Attachment 1 of this Statement of Work
1.3. Hours of Operation
1.3.1. Normal Working Hours.
The Contractor shall perform services under this SOW between the hours of 07:30 to 16:30 local time, Monday through Friday, except on Federal Holidays or when the government facility is closed due to local or national emergencies, administrative closings, or similar government-directed facility closings.
1.3.2. Federal Holidays
The Contractor is not required to perform services on Federal holidays below:
a. 1 January (New Year’s Day)
b. 3rd Monday in January (Martin Luther King, Jr. Day)
c. 3rd Monday in February (Presidents Day)
d. Last Monday in May (Memorial Day)
e. 4 July (Independence Day)
f. 1st Monday in September (Labor Day)
g. 2nd Monday in October (Columbus Day)
3 | P a g e
h. 11 November (Veterans Day)
i. 4th Thursday in November (Thanksgiving Day)
j. 25 December (Christmas Day)
k. Any other day designated by federal statute, executive order or presidential proclamation
1.3.3. Principal Period of Maintenance: Contractor must notify Government Representative via email 48 hours prior to service; response not required
1.4. Equipment Requirements
1.4.1 General Requirements:
1.4.2 The preferred connection type will be hardwired; however, the use of wireless components can be considered only after pre-coordination with both Security Forces and the base Communications Squadron.
1.4.3 The use of cloud-based storage shall meet or exceed all Core DoD Cyber Security Standards: Risk Management Framework (RMF) Compliance DoDI 8510.01 https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/851001p.pdf?ver=5YnACrA lUCPZ_qeq4T5nlg%3d%3d; Security Technical Implementation Guides (STIG) https://stigviewer.com/stigs/network_infrastructure_policy;
1.4.4 Cyber Security Activities Support Procedures DoDM 8530.01 https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodm/853001p.PDF?ver=BFUag WhkQR8fBXzxRjIqxQ%3d%3d ; Zero Trust Architecture; Endpoint and Network Defense.
cybersecurity standards required by the DoD. All cloud-based systems shall be compliant with the Federal Risk and Authorization Management Program (FedRAMP), ensuring adherence to standardized security assessment and authorization protocols for cloud services. For more information, refer to FedRAMP.gov.
1.4.5 The system will interface with the base-wide NIPRNet, maintaining logical separation of data through a Closed Restricted Network (CRN). While data will traverse the existing infrastructure, safeguards will remain in place to preserve its integrity. All components involved must be selected from historically validated Department of Defense technology sources, and the Contractor is responsible for ensuring that all equipment runs a DoD-approved Operating System (OS). The OS authorized for use currently on Columbus AFB is Windows 11 23h2 or Server 2019/2022. An example of a DoD approved OS is Oracle Linux, used in some DoD environments after meeting RMF and STIG requirements. The list of approved operating systems on the DoD network is found at https://aplits.disa.mil/processAPList.
1.4.6 The Contractor shall provide the software license covering all cameras and associated components. Cameras must be accessible from designated network locations via web browser, secured through common access card, PIV, or username and password authentication.
https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/851001p.pdf?ver=5YnACrAlUCPZ_qeq4T5nlg%3d%3d https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/851001p.pdf?ver=5YnACrAlUCPZ_qeq4T5nlg%3d%3d https://stigviewer.com/stigs/network_infrastructure_policy https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodm/853001p.PDF?ver=BFUagWhkQR8fBXzxRjIqxQ%3d%3d https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodm/853001p.PDF?ver=BFUagWhkQR8fBXzxRjIqxQ%3d%3d https://aplits.disa.mil/processAPList
4 | P a g e
1.4.7 Software Licensing Period of Performance (PoP):
One Base Year of 12 months and four12-month option years. The PoP reads as follows:
Base Year:
Option Year 1 Option Year 2 Option Year 3 Option Year 4
1.4.8 The software solution shall incorporate advanced Artificial Intelligence (AI) capabilities to enhance situational awareness and operational efficiency. Core functionalities must include real-time license plate recognition, automated tracking of vehicles and individuals across multiple video feeds. The ability for object detection, re-identification, and trajectory prediction is also preferred.
1.4.9 The cost of all required camera mounting brackets shall be factored into the Contractor’s bid.
1.4.10 Project scope includes work on facilities up to 40 feet, which is the height of the tallest camera placement not accessible by ground or built in platform. The cost of any necessary skylift rentals shall be included in the bid.
1.4.11 All equipment provided must comply with Section 889 of the National Defense Authorization Act (NDAA). BANNED Equipment or components include, but are not limited to, products manufactured by the following plus any affiliate brands:
• Huawei Technologies Company
• ZTE Corporation
• Hytera Communications Corporation
• Hangzhou Hikvision Digital Technology Company
• Dahua Technology Company
1.5 Specific Requirements:
1.5.1 Cameras Specifications Requirements:
Outdoor (23)/Indoor (2)
• A minimum of 4K resolution (3840×2160) with the only exception to this being multi-sensor cameras, which may have resolution no lower than 2688×1944.
• All cameras must operate at a minimum of 24 frames per second (fps)
• Equipped with low-light or no-light functionality providing clear resolution up to a minimum of 50 feet.
• Required features include motion detection, human and vehicle recognition, line crossing alerts, loitering detection, crowd monitoring,
• AI-powered search capabilities, trajectory mapping, and license plate recognition.
• Adaptive video compression may be utilized, provided it dynamically adjusts image quality based on scene activity—allowing greater detail retention in
5 | P a g e high-motion scenes while permitting reduced detail in low-motion environments.
• 360-degree view
• Flexible Mounting: ceiling/wall/pole
• Pan, Tilt, Zoom or telephoto lens
• Storage: Cloud, internal, or server to maintain a minimum of 30 days of footage
• Reliable connectivity
• Wired: (Ethernet/PoE)
• Secure Data Transmission and Storage: Encryption, strong passwords, regular firmware updates
• Wide Dynamic Range
1.5.2 Video Management System (VMS) & Storage:
• VMS can be cloud based or server/computer solutions.
• A minimum of 30 days of video storage must be provided.
• Cloud-based solutions must meet requirements in paragraph 1.4.
• Server based solutions will be housed in a floor standing rack with an uninterruptible power supply (UPS), with data transmission via fiber-optic connection.
• Must be a remote in capable system through use of a common access card or username password/code.
• Must utilize human and vehicle recognition, line crossing alerts, loitering detection, crowd monitoring, AI-powered search capabilities, trajectory mapping, and license plate recognition.
1.5.3 Integration Axis Model Cameras:
The contractor shall integrate in the existing Axis cameras (please see table below) the software solution to incorporate advanced Artificial Intelligence (AI) capabilities to enhance situational awareness and operational efficiency. Core functionalities must include real-time license plate recognition, automated tracking of vehicles and individuals across multiple video feeds. The ability for object detection, re-identification, and trajectory prediction is also preferred. In the following existing cameras
Table: Existing cameras (up to 40 existing) listed below to include the specific models to be integrated:
6 | P a g e
All equipment shall be connected to the fiber highway but physically separated from the Air Force Network. The contractor shall become familiar with the security and network architecture of Columbus AFB to ensure an optimized and efficient system implementation.
1.5.4 Current VMS
• Axis Communications VMS is currently being used and may be integrated into a new system if capable.
• 2 Axis S1264, 144TB each, servers are currently being used for storage.
• 4 Workstations currently operating Axis VMS
• Provides approximately 45 days of video storage.
2. QUALITY CONTROL
The contractor shall develop and maintain an effective quality control program to ensure all work is performed in accordance with commonly accepted commercial practices. The contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective work. The Contracting Officer may request this plan as deemed necessary.
3. INSTALLATION
The Contractor shall provide all necessary labor, tools, equipment, and materials to install and maintain cameras, servers, patch cables (fiber or copper), software, and related components as directed by the 14th Security Forces Squadron. Upon completion of work, the Contractor is responsible for removing all debris, foreign object damage (FOD), tools, and surplus materials from the job site.
3.2. If requested, the Contractor shall conduct a site survey, coordinate with all relevant stakeholders, collect site-specific data, test existing equipment, and identify any operational constraints that could influence system design or recommendations. The Contractor shall also identify any required existing documentation, such as As-Built Drawings.
3.3. The Contractor shall submit manufacturers’ data sheets for all materials, equipment, and software required for implementation of the complete system.
3.4. The Contractor shall perform all cybersecurity hardening tasks in accordance with the most current standards. This includes, but is not limited to, applying patches and updates, Quantity Camera Model Name Minimum Firmware Supported 2 Axis 211 D2110-VE 11.10.61 17 Axis M3027-PVE M3027 5.55.1 12 Axis P-1448-LE P1448-LE 11.10.61 2 Axis P3346 P3346 11.10.61 2 Axis M3007-PVE M3007-PV 5.70.1 & 6.50.5.2 2 Axis P3301 P3301 5.40.9.2 3 Axis Q1765-LE Q1765-LE 11.10.61
7 | P a g e implementing Security Technical Implementation Guides (STIGs) and Security Requirements Guides (SRGs), and configuring systems securely.
3.5. Prior to installation at Government facilities, the Contractor shall submit the following documentation for approval:
• System descriptions and manufacturers’ data
• Network diagrams
• Data flow diagrams
• Hardware and software inventories (per eMASS template requirements)
• Ports, Protocols, and Services (PPS) list
• ACAS vulnerability and SCAP/SCC scan summaries and raw results
• Completed STIG/SRG checklists with comments
• Configuration files for all network devices
• Plan of Action and Milestones (POA&M) or deviations documentation for any unresolved vulnerabilities
3.6. The system shall achieve 100% compliance with ACAS/Nessus and SCAP/STIG requirements. Any deviations must be fully documented and approved by the Government prior to installation.
3.7. Responsibility for system accreditation resides with the Government once cybersecurity hardening is complete and all required documentation has been accepted.
3.8. All personnel requiring base access to perform work shall undergo background checks by the Security Forces. The Contractor shall submit the list of installers at least two (2) weeks prior to the scheduled start date.
3.9. The Contractor shall install the Video Management System (VMS), servers, workstations, and cameras in accordance with the specifications outlined in this Statement of Work.
3.10. All installation activities, including deployment of cameras, servers, workstations, and the VMS, shall be completed within sixty (60) calendar days from the contract award effective date.
3.11. The Contractor shall ensure all system software is updated and that installed cameras are fully configured and integrated with the servers and VMS. A comprehensive performance test shall be conducted with designated representatives from the 14th Security Forces Squadron to verify functionality.
3.12. Prior to final acceptance of the installation, the Contractor shall conduct one (1) training session for up to ten (10) personnel. All access credentials—such as usernames, passwords, and authentication codes—shall be provided at that time to support operational readiness.
4. CONTRACTOR RESPONSIBILIITES.
4.1. Points of Contact The Contractor shall provide a current list of designated points of contact available during standard business hours (Monday through Friday, 07:30–16:30). This list shall be continuously updated and submitted to the 14th Security Forces Squadron via email at 14SFS.S5.ALL@us.af.mil throughout the life of the contract.
8 | P a g e
4.2. Access and Equipment Coordination The Contractor shall coordinate all lift access required for elevated camera servicing. When necessary to minimize disruption to base operations, the Contractor may be required to schedule after-hours work.
4.3. Warranty. The Contractor shall warrant that all surveillance cameras and associated equipment provided under this contract are free from defects in material and workmanship and conform to the specifications set forth in this Statement of Work. The warranty shall remain in effect for the period of September 2025- September 2026.
During the warranty period, the Contractor shall, at no additional cost to the Government, repair or replace any defective equipment or components. This includes all labor, parts, and transportation costs associated with the repair or replacement.
The warranty shall not apply to defects resulting from misuse, abuse, or unauthorized modifications by Government personnel. The Contractor shall respond to warranty claims within 5 business days of notification and complete corrective actions within 15 business days unless otherwise agreed upon.
9 | P a g e
Attachment 1
(14) Existing/Replacing Cameras:
1. Building 95/98 Commercial Vehicle Inspection (CVI): A total of two (2) cameras will be installed via wall mounting, replacing existing cameras, at this location. Two (2) outdoor IP cameras in opposite corners covering the inspection area.
Note: There is no ethernet cable connected to camera 7 (2025 Camera System Upgrade attachment). The ethernet will have to be run and be installed to the switch at the VCC (building 99)
2. Building 99 Visitor Control Center (VCC): A total of one (1) IP indoor 360-degree view camera with sound will be installed via ceiling mounting, replacing an existing camera, at this location.
3. Building 110 East Gate: A total of three (3) outdoor cameras will be installed, replacing existing cameras, at this location. Two (2) IP cameras installed via wall mounting, one
(1) facing inside the base for inbound/outbound traffic, one (1) facing outside the base for inbound/outbound traffic, one (1) IP outdoor 360-degree view camera installed via ceiling mounting.
4. Building 1130 South Gate: A total of three (3) outdoor cameras will be installed, replacing existing cameras, at this location. Two (2) IP cameras installed via wall mounting, one (1) facing inside the base for inbound/outbound traffic, one (1) facing outside the base for inbound/outbound traffic, one (1) IP outdoor 360-degree view camera via ceiling mounting.
5. Building 2006: A total of two (2) cameras will be installed via pole mounting, replacing existing cameras, at this location. One (1) camera will be an outdoor IP camera facing North towards the North Gate. This will need to be able to process precise video approximately 800 meters from mounting location. One (1) camera will be an outdoor IP camera facing West towards the Hot Cargo Pad. This will need to be able to process precise video approximately 1500 meters from mounting location
6. Building 926: Total of one (1) camera will be installed via wall mounting, replacing existing cameras, at this location. One (1) indoor 360-degree cameras with sound with clear view of the SFS armory door and the SFS clearing barrel.
10 | P a g e
7. Building 998: Total of one (1) camera will be installed via wall mounting, replacing existing cameras, at this location. One (1) outdoor IP camera capable of viewing both the SFS ARMAG & flightline ECP.
Note: A longer patch cord is sufficient to install in lieu of installing a new cable from the Comm Cabinet if it is within the recommended length for ethernet Please refer to:
Institute of Electrical and Electronics Engineers (IEEE) 802 Ethernet Standards.
8. Building 2005: A total of one (1) camera will be installed via pole mounting, replacing existing cameras, at this location. One (1) camera will be an outdoor IP camera. This will need to be able to process precise video approximately 1600 meters from mounting location.
11 | P a g e
Attachment 2
(11) New Install Cameras:
1. Building 1805: Total of two (2) cameras will be installed at this location via wall mounting (no previous camera in place). Two (2) outdoor IP camera capable of viewing up to 1600 meters.
2. Building 958: A total of one (1) camera will be installed at this location via pole mounting. The camera will be an outdoor wide-angle camera mounted in the parking lot facing towards the East side of the building. This camera may be required to operate wireless.
3. Building 964: A total of one (1) camera will be installed at this location via pole facing towards the West side of the building. This camera may be required to operate
4. Building 966: A total of one (1) camera will be installed at this location via pole
5. Building 972: A total of one (1) camera will be installed at this location via pole facing towards the East side of the building. This camera may be required to operate
6. Building 972: A total of one (1) camera will be installed at this location via pole
7. Building 958: A total of one (1) camera will be installed at this location via pole mounting. The camera will be an outdoor camera mounted in the open area between buildings 958, 964, & 966. This camera may be required to operate wireless.
8. Building 543: A total of one (1) camera will be installed at this location via wall mounting. One (1) outdoor camera in the Northwest corner of the building. This camera may be required to operate wireless.
9. Building 9113: A total of one (1) camera will be installed at this location via ceiling mounting. One (1) outdoor camera in the center of the building. This camera may be required to operate wireless.
10. Building 348: A total of one (1) camera will be installed at this location via wall mounting. One (1) outdoor IP camera at the center of the building on the West side. This
12 | P a g e camera may be required to operate wireless
| 1. DESCRIPTION OF SERVICES: |
| 1.1 Place of Performance: Columbus AFB, Columbus, MS |
| 1.2. Contractor Required Deliverables |
| 1.3. Hours of Operation |
| 1.3.1. Normal Working Hours. |
| 1.3.2. Federal Holidays |
| 2. QUALITY CONTROL |
| 3. INSTALLATION |
| 4. Contractor responsibiliites. |
File details come from the government source that posted it. Updated .