A small-business Air Force solicitation for MacDill AFB calls for five ALPR deployments, including four fixed locations and one mobile solution, with solar power, battery backup, live video and CJIS-oriented data safeguards.

Key takeaways

  • The Air Force solicitation seeks an enterprise ALPR platform for access control, investigations, force protection and authorized information sharing at MacDill AFB.
  • The requested deployment includes five camera solutions: four fixed installations using government-furnished poles and one mobile deployment.
  • Solar power and battery backup are required because the identified locations do not have alternate power sources.
  • The requirement combines plate recognition, vehicle-attribute recognition, live HD video and digital evidence-management capabilities.
  • A post-solicitation Q&A says the platform will not integrate with the government network; the contractor is not expected to obtain an RMF authorization to operate.

A current Air Force procurement signal for integrated ALPR

The Department of the Air Force is seeking an automated license plate recognition system for MacDill Air Force Base in Tampa, Florida, under solicitation FA481426R0010. The procurement is a total small-business set-aside under NAICS 561621, Security Systems Services, and covers procurement, installation, configuration and sustainment of an enterprise ALPR platform. The base requirement is structured with a base period and four option years that include warranty coverage for supplied equipment and continuing software updates.

The opportunity was initially posted on August 25, 2026. The statement of need and an associated questions-and-answers document carry an August 28, 2026 posting date, making August 28 the appropriate date for the detailed requirements discussed here. As of the solicitation information reviewed, offers are due September 9, 2026. This is a solicitation, not an award announcement; no supplier selection or contract value was identified in the material reviewed.

Five deployments, including a mobile capability

MacDill’s stated package calls for five license-plate camera solutions, five solar-panel kits, five mounting-camera components, five extended battery-and-charger units, one software entitlement and five user licenses. The deployment concept is four affixed camera installations plus one mobile solution. In the Q&A, the government said it will furnish existing poles for the four fixed cameras, while offerors must provide a mobile solution and a fixed pole-mounted solution.

The fixed camera locations are the base’s Main Gate, Bayshore, MacDill and Tanker Way access-control points. The agency outlined inbound and outbound lane counts at those locations, indicating that the design must account for multiple travel lanes rather than a single controlled lane. The solicitation also permits use of nearby light poles where available, but prohibits altering the configuration or wiring of government-furnished infrastructure. Installation and commissioning are expected within 60 days after acceptance.

Solar power turns the requirement into an edge-infrastructure project

The Q&A establishes that alternate power is not available at the designated sites. Accordingly, an offered system must include solar power and battery backup. This pushes the scope beyond camera selection: integrators will need to validate solar exposure, seasonal energy production, battery reserve, enclosure heat load, wireless uptime and mounting constraints at each approved location.

The original statement of need also calls for an IP66 enclosure, operation from minus 22 to 140 degrees Fahrenheit, and ASTM B117 salt-fog resistance. Those conditions are significant for a coastal Florida installation, where moisture, salt exposure, heat and storm readiness can affect both enclosure selection and service planning. The specified communications approach includes an LTE modem with encrypted data transmission and automatic reconnect behavior after power-up.

ALPR is only one part of the requested security workflow

The requested platform must combine ALPR with vehicle-attribute recognition, live HD video, still images, historical tracking and digital evidence management. The statement of need specifies highway-speed, multi-lane capture, day-and-night operation, infrared illumination and a minimum 1080p resolution. It also requests live alerts, GIS mapping, hotlists, audit logs, mobile access and searches using plate numbers, partial plates, vehicle make, model, color, body style, time and location.

The government seeks 90 days of storage for license-plate data and live footage, plus evidence functions supporting retention, chain of custody and case management. The platform is also expected to work within a unified operations-center environment alongside other security systems. For security teams, the procurement illustrates how access-point ALPR projects increasingly span imaging, analytics, video retention, networking, evidence governance and operator workflows rather than operating as isolated cameras.

Security and data controls remain central, with an important clarification

The statement of need requests encrypted communications, multi-factor authentication, role-based access control, audit logging and compliance with FBI CJIS Security Policy expectations. It also references DoD Risk Management Framework and DISA Security Technical Implementation Guide requirements, and bars covered telecommunications and video-surveillance equipment under Section 889 restrictions. The requirement calls for technical capability to support interfaces with NCIC, FCIC, NLETS, CJIS-compliant databases and approved local databases.

However, the August 28 Q&A narrows the implementation expectation. MacDill said the contractor need only demonstrate technical capability for those external interfaces, with government coordination occurring after award. It further stated that the system will not integrate with the government network and that the contractor will not be responsible for obtaining a DoD RMF authorization. If a commercial cloud service is used for ALPR, video or evidence data, the Q&A identifies FIPS 140-3 as the stated cryptographic requirement. Bidders and integrators should therefore distinguish between the statement of need’s general security posture and the clarified boundary of the deployed solution.

What installers and procurement teams should assess

The clearest procurement lesson is that resilience, security architecture and operations are being evaluated together. A compliant response would need to address lane coverage and capture performance, site-specific solar and battery sizing, LTE coverage, high-salinity enclosure durability, secure administration, retention capacity and evidence-management workflow. It must also account for deployment at existing government poles without infrastructure modifications.

The solicitation does not name a preferred manufacturer. It is therefore a requirements-led opportunity rather than a brand-specific replacement project. Teams considering similar ALPR programs should document power autonomy and communications assumptions early, define who owns database and evidence-platform integrations, and verify that access-control, video and cybersecurity requirements are technically consistent before installation begins.