AI Physical Security Cooperative Purchasing Vehicles: The 2026 Market Analysis of Sourcewell, OMNIA Partners, NASPO ValuePoint, GSA MAS, and the Procurement Architecture Compressing Public-Sector AI Security Buying Cycles

AI physical security cooperative purchasing has become the procurement architecture that the public-sector AI security market actually runs on, and most security directors are routing their AI gun detection, fall detection, and behavioral analytics buys through a national cooperative contract without thinking of it that way. The State, Local, and Education (SLED) cooperative purchasing market reached $65 billion in 2025 according to GovWin / Deltek's SLED outlook, with projections of $100 billion by 2027. That growth is being driven by exactly the procurement compression that AI physical security vendors and buyers both want: a path from "I have funding" to "we are running a live deployment" that does not pass through a nine-to-fourteen-month traditional RFP.

This briefing maps the six national cooperative vehicles that dominate public-sector AI physical security procurement, the legal mechanics that make piggyback purchasing audit-defensible under state law, the categories that AI security buys actually fit under, and the buyer-side evaluation framework security directors need to pick the right vehicle. The report assumes the reader is procuring an AI security platform for a school district, hospital, municipality, utility, transit authority, or federal facility and wants to know which contract vehicle compresses their cycle without creating procurement risk downstream.

The cooperative purchasing architecture that public-sector AI security buyers already use

Cooperative purchasing is the structural fact that one government agency competitively solicits a contract, and any other eligible government entity can then "piggyback" on that contract to purchase the same goods or services without running their own RFP. The legal authority for this exists in nearly every state, most commonly under interlocal cooperation acts or joint powers statutes, and the federal equivalent runs through the General Services Administration (GSA) cooperative purchasing program and a half-dozen Department of Defense and Department of Homeland Security pass-throughs.

The market has consolidated. GovWin's 2026 SLED outlook places the cooperative purchasing channel at $65 billion in 2025 cooperative volume across state, local, and education buyers, growing toward $100 billion by 2027. That is the total spend running through cooperative contracts across every category, from playground equipment to school buses to AI physical security platforms. AI physical security represents a small but rapidly growing slice of that flow, riding on categories that already exist in cooperative scope (electronic security systems, low-voltage integration, video surveillance, software as a service, IT services) rather than waiting for AI-specific contracts to be solicited.

For the buyer, that matters in three ways. First, the cooperative vehicle was already competitively bid, which satisfies most state and local procurement law without requiring a new solicitation. Second, the awarded supplier list is published and pre-vetted, so the buyer can evaluate vendors without running a discovery RFP. Third, pricing is pre-negotiated at scale, which means the buyer is generally protected from per-buyer pricing variance and the back-and-forth that consumes the most time in a traditional public-sector procurement.

LIVE 18:42:07CAM-N04 / WEST CORRIDOR

Actual IntelliSee detection output. The platform identifies a firearm in real time, draws a bounding box with confidence score, and routes the alert to existing access control, mass notification, and PSAP dispatch integrations within seconds. No facial recognition, no stored video, no PHI collected. Public-sector buyers procure this kind of capability through cooperative purchasing vehicles whose scope language already covers electronic security systems and video analytics software, which is why cooperative procurement has compressed buying cycles for school districts, hospitals, and municipal facilities.

The six national cooperative vehicles AI security buyers actually evaluate

The cooperative purchasing landscape has hundreds of vehicles, but six national programs handle the overwhelming majority of public-sector AI physical security procurement decisions. Knowing which one a vendor has been awarded under, and which one your entity has signed an interlocal agreement with, defines the practical procurement universe before any other variable.

The legal mechanics: piggyback authority, interlocal compacts, and why cooperative contracts hold up under audit

The legal architecture that makes cooperative purchasing audit-defensible varies by state but converges on a common pattern. Most states authorize interlocal cooperation contracts under their version of the Joint Exercise of Powers Act or an Interlocal Cooperation Act. Texas is illustrative because it has the most widely-copied statutory language. Under Texas Government Code Chapter 791, the Interlocal Cooperation Act, "a local government may contract or agree with another local government to perform governmental functions and services," and "administrative functions" expressly include purchasing. That single statutory hook is what lets a Texas school district piggyback on a TIPS, OMNIA Partners, or BuyBoard contract without running its own RFP.

The federal equivalent is the GSA Cooperative Purchasing Program, which extends the federal MAS contracts to state, county, local, town, and city governments, as well as organizations created by state statute including local educational entities and public colleges and universities. The GSA program is what lets a city police department buy from a federally-awarded MAS contract without going through GSA's federal-only procurement rules, and it is the underlying authority for state and local use of GSA Schedule 84 for security purchases.

For buyers, the audit-defensibility of a cooperative purchase rests on four conditions: the underlying contract was competitively solicited under public procurement rules, the buyer's entity is statutorily authorized to participate, the buyer signed an interlocal or membership agreement before issuing the PO, and the buy stays within the awarded contract scope. A purchase that fails any of those four conditions is not a cooperative purchase; it is a sole-source buy dressed in cooperative language, and state auditors and inspectors general have repeatedly flagged exactly that pattern in technology procurements.

How AI gun detection, fall detection, and behavioral analytics fit into existing cooperative scope

The most common buyer-side confusion in AI physical security cooperative purchasing is the assumption that there must be an "AI security" category in the contract scope. There usually is not. AI gun detection, AI fall detection, perimeter intrusion analytics, and behavioral analytics platforms are procured under cooperative contracts whose scope language was written for electronic security systems, video surveillance equipment, low-voltage integration services, IT services, or software as a service. The AI capability rides on the existing scope because the deliverable is a video analytics platform (covered), a software subscription (covered), or a managed security service (covered).

The practical mapping looks like this. K-12 AI gun detection deployments usually procure under Sourcewell, TIPS, or BuyBoard contracts in the "electronic security systems," "video surveillance," or "technology solutions" category, with the awarded supplier installing cameras and software under a unified scope. Higher education campuses lean on Sourcewell or OMNIA Partners contracts in the same categories, sometimes routing through the institution's existing IT services cooperative. Hospital security buyers route AI gun detection and AI fall detection through OMNIA Partners or Premier (a healthcare-focused cooperative not detailed in this analysis) under the "security services" or "technology solutions" categories. Municipal and county buyers use Sourcewell, NASPO ValuePoint, or OMNIA Partners for citywide or county-jail surveillance and analytics. Transit authorities frequently use NASPO ValuePoint state-led contracts because their funding is state-allocated and the audit trail follows state procurement officials. Critical infrastructure operators with DOD or DHS involvement route through GSA MAS or the DOD 1122 Program for the federal compliance overlay.

The cooperative scope question matters because the procurement attorney's job is to map the AI security deliverable to the contract's scope language. When that mapping is clean, the buy proceeds. When the mapping requires the attorney to argue that AI gun detection software is in scope for an "electronic security systems" contract that does not mention AI, the procurement attorney will usually win that argument, but only if the awarded vendor is the prime contractor and the AI capability is delivered as part of the integrated system. When a vendor tries to sell its AI software separately under a contract scope that does not cover software-only buys, the procurement will get pushed back into a traditional RFP.

The 90-day decision: cooperative procurement vs. traditional public-sector RFP

The procurement compression is the entire reason the cooperative purchasing channel has grown to $65 billion in SLED volume. A traditional public-sector RFP for an AI physical security platform typically runs nine to fourteen months from internal need definition to executed contract. A cooperative purchase using a pre-awarded contract typically runs thirty to ninety days from internal need definition to executed PO. The difference is not technique. It is the number of process steps that have already been completed by the lead agency under the cooperative model.

The procurement compression is not the only economic benefit. Traditional RFPs concentrate vendor variance at the proposal stage, where every responding vendor prices to win and the buyer ends up evaluating wildly different pricing structures. Cooperative purchases use pre-negotiated pricing or pricing methodologies, which compresses variance and removes the back-and-forth that often surfaces late in traditional RFPs.

The trade-off is that the buyer is choosing from the awarded supplier list. If the AI security vendor the buyer wants is not on a contract the buyer can access, the cooperative path will not work. That is where the buyer-side evaluation framework starts.

The buyer-side evaluation framework for picking the right cooperative vehicle

The framework is a four-question filter. Run an AI physical security cooperative purchase through these four questions in order, and the answer to "which vehicle do we use" becomes a one-meeting decision rather than a procurement department research project.

The four questions are sequenced for a reason. Question one determines whether a cooperative path exists. Question two determines whether your entity can use it. Question three is where most procurement disputes originate, and where the scope-to-deliverable mapping has to be airtight. Question four is the one that gets missed and creates problems during deployment when a contract sunsets mid-implementation.

For AI physical security buys specifically, the scope question (Q3) is the one to spend the most time on. Cooperative contracts written for "video surveillance equipment" cover camera hardware but may not cover standalone AI software subscriptions. Contracts for "technology solutions" or "IT services" tend to cover SaaS-delivered AI analytics but may not cover integrated camera-plus-software bundles. Contracts for "electronic security systems" cover the integrated system in most jurisdictions but may not cover ongoing software maintenance or cloud inference licensing. The mapping is straightforward when the AI vendor is selling an integrated system through a single awarded supplier, and complex when the AI vendor is software-only and the buyer is trying to bundle it with hardware bought under a different contract.

Three patterns that signal a cooperative vehicle is the wrong fit for an AI security buy

Cooperative purchasing is the right answer most of the time for public-sector AI security procurement, but it is not universally the right answer. Three buyer-side patterns reliably indicate that a traditional RFP, sole-source justification, or grant-driven procurement is the better fit.

Pattern one: the buyer needs vendor-specific architecture decisions baked into the procurement. Cooperative contracts award vendors on the basis of pricing and category fit, not architecture. If the buyer's procurement needs to specify edge-versus-cloud inference, retention period, integration depth with a specific access control or VMS platform, or specific compliance requirements like NDAA Section 889 camera supply-chain restrictions, the cooperative scope may not let the buyer specify those requirements clearly. A traditional RFP with technical specifications is the cleaner path.

Pattern two: the deployment is grant-funded and the grant requires a specific procurement methodology. Many federal and state physical security grants require open competitive procurement, sometimes specifically excluding cooperative purchases. The federal and state grant funding landscape for AI physical security includes COPS School Violence Prevention Program awards, FEMA Nonprofit Security Grant Program awards, and state-specific safety grants. Buyers using grant funding need to read the grant's procurement requirements before defaulting to a cooperative vehicle.

Pattern three: the vendor is not on any cooperative contract and is unlikely to pursue one in the buyer's procurement window. The cooperative path requires an awarded supplier. If the buyer's preferred AI security vendor is not awarded under any accessible cooperative and the buyer's deployment timeline is shorter than the typical 12-to-18 month cooperative solicitation cycle, the buyer either has to pick a different vendor or go through a traditional procurement. Forcing a non-cooperative vendor into a cooperative buy through paperwork manipulation is the pattern that gets flagged by state auditors.

What this means for the AI physical security buyer in 2026

Cooperative purchasing has structurally reshaped how public-sector AI physical security gets bought. The buyer who maps their deployment to an awarded cooperative contract before the procurement department gets involved has a 90-day path to PO. The buyer who treats cooperative purchasing as an afterthought, or who picks a vendor first and then tries to find a cooperative vehicle that fits, ends up either back in a traditional RFP or in an audit-flagged procurement.

The market intelligence that matters for the AI security buyer in 2026 is therefore not the size of any single cooperative or the number of vendors on any single contract. It is the four-question evaluation framework and the scope-to-deliverable mapping. The cooperative architecture exists. The contracts are pre-awarded. The legal authority is in place under state interlocal acts and the GSA Cooperative Purchasing Program. The only remaining buyer-side variable is whether the AI security deployment fits cleanly into an existing cooperative scope, and that is a question the buyer can answer in a single afternoon if they ask the right four questions in order.

For AI security vendors, the corresponding intelligence is that cooperative-awarded status is increasingly a precondition for public-sector deals rather than a nice-to-have. The vendor that is not on Sourcewell, OMNIA Partners, NASPO ValuePoint, TIPS, GSA MAS, or a regional cooperative is competing against vendors who are, and is asking the buyer to absorb a 9-to-14-month procurement timeline that the cooperative-awarded competitor does not impose. That gap will keep widening through 2027 as the SLED cooperative market grows toward $100 billion.

Frequently asked questions on cooperative purchasing for AI physical security

Continue the research

• Federal and State Grant Funding for AI Physical Security: The 2026 Procurement Intelligence Briefing — the funding-side counterpart to the cooperative procurement architecture covered here
• AI Physical Security Total Cost of Ownership: The 2026 Buyer's Pricing Intelligence Report — how pricing structures in cooperative contracts compare to direct procurement
• AI Physical Security Procurement Compliance: The 2026 Federal and State Regulatory Framework — regulatory overlay across procurement methodologies
• NDAA Section 889 and FAR 52.204-25: The 2026 Camera Supply-Chain Compliance Briefing — supply-chain compliance that intersects with federal cooperative purchases
• How to Evaluate an AI Gun Detection System: The 2026 Procurement and Proof-of-Concept Methodology — vendor evaluation framework that pairs with cooperative path selection
• K-12 AI Gun Detection: The 2026 Sector Playbook for Schools and Districts — the buyer segment that uses cooperative purchasing most heavily
• How IntelliSee Works — the platform architecture available through cooperative contracts
• Request a Risk Assessment — map your facility's needs to a cooperative procurement path