Cooperative Purchasing for Security Cameras: How to Buy AI Video Analytics Without an RFP
The most common objection to buying security technology through a cooperative contract is that it feels like skipping competition. It is worth stating plainly that the opposite is true. Under federal grant rules, a documented purchase made through an intergovernmental or cooperative agreement does not bypass the competition requirement, it satisfies it. That single misunderstanding sends school districts, cities, and county agencies into nine-month formal solicitations they were never required to run.
If you are evaluating cooperative purchasing security cameras or the AI video analytics layered on top of them, the questions that actually matter are which dollar threshold your purchase falls under, which contract vehicle your entity is legally allowed to use, and what has to be in the file when an auditor asks why you did not competitively bid. This guide covers all three.
Featured image: a synthetic illustration created to depict the scenario described here. It is not a real detection capture.
Key takeaways
- Cooperative and intergovernmental procurement actions meet the competition requirements of the federal Uniform Guidance when they are documented. They are not an exception to competition.
- The federal micro-purchase threshold is $15,000 and the simplified acquisition threshold is $350,000 as of August 2026. Many security purchases never reach the formal-procurement tier at all.
- Your state or local procurement law, not the federal rule, is what most often disqualifies a piggyback purchase.
- Buying analytics software that runs on existing cameras changes the procurement category and frequently the threshold tier, because there is no hardware replacement in the scope.
What cooperative purchasing security cameras really means
Cooperative purchasing is the practice of buying from a contract that another public agency already competitively solicited and awarded, rather than running your own solicitation. A lead agency publishes a solicitation, evaluates responses, and awards a contract written so that other eligible public entities can purchase from it on the same terms. The competitive work is done once, and it is done in public.
The federal authority for this sits in the Uniform Guidance at 2 CFR 200.318(e), which encourages recipients and subrecipients to enter into state and local intergovernmental agreements or inter-entity agreements for procurement transactions. The operative sentence is short and unambiguous: documented procurement actions of this type "will meet the competition requirements of this part."
The load-bearing word there is documented. The rule does not say that cooperative purchases are exempt from scrutiny. It says a properly documented one clears the competition bar. What auditors find when a cooperative buy goes wrong is almost never a bad contract vehicle. It is an empty file.
The thresholds that decide whether you need a contract vehicle at all
Before choosing a cooperative contract, determine which procurement tier your purchase falls into, because a meaningful share of security technology buys sit below the level where formal competition is required in the first place. The Uniform Guidance defines three procurement methods at 2 CFR 200.320: informal methods for micro-purchases and simplified acquisitions, formal methods through sealed bids or proposals, and noncompetitive methods.
Two details in that ladder are routinely missed. First, a micro-purchase may be awarded without soliciting competitive price or rate quotations at all, provided the recipient considers the price reasonable based on research, experience, or purchase history and keeps documents supporting that conclusion. Second, a recipient may self-certify a micro-purchase threshold as high as $50,000 on an annual basis, with a written justification and supporting documentation such as qualification as a low-risk auditee or an annual internal risk assessment.
In the simplified acquisition tier, the requirement is price or rate quotations from an adequate number of qualified sources, and unless a federal agency specifies otherwise, the recipient exercises judgment about what number is adequate. That is a materially lighter lift than a sealed-bid process, and it is where a large share of single-building and single-campus security projects land.
The contract vehicles public buyers actually use
Most public entities have access to several cooperative contract vehicles at once, and eligibility differs by entity type and by state. The table below covers the vehicles that appear most often in K-12, higher education, municipal, and healthcare security purchases.
| Vehicle | Type | Typically used by | Notes |
|---|---|---|---|
| GSA Federal Supply Schedules | Federal, opened to state and local | States, counties, cities, tribal governments, school districts, higher education | Authorized by statute for specific product groups only. See the section below. |
| NASPO ValuePoint | Multi-state, led by state chief procurement officials | State agencies and their authorized political subdivisions | Participation is state by state. Your state must have a participating addendum. |
| OMNIA Partners | National cooperative | Public agencies and education | Contracts are competitively solicited by a lead public agency. |
| TIPS | National cooperative, education service center led | Schools, higher education, municipalities, nonprofits | Membership required before purchase. |
| E&I Cooperative Services | Member-owned, education focused | Colleges, universities, K-12 | Member institutions only. |
| PEPPM | Technology bidding cooperative | K-12 and public entities nationally | Technology-specific. IntelliSee holds an AI weapons detection agreement here. |
| State-specific programs | Statewide contracts | Entities within that state | Examples include COSTARS in Pennsylvania and BuyBoard in Texas. |
| Group purchasing organizations | Sector cooperative | Hospitals and health systems | IntelliSee holds a weapons detection agreement with Premier Inc. |
A vehicle only helps if the vendor you want is actually on it. This is the practical constraint that decides most cooperative buys: you are not selecting from the whole market, you are selecting from the awarded suppliers on contracts your entity may use. Confirm both halves before you build a project timeline around a piggyback purchase.
GSA cooperative purchasing: the federal schedule state and local buyers can use
State and local governments may buy security equipment and related services from GSA Federal Supply Schedules, but only within the product categories Congress specifically authorized. The authority is 40 U.S.C. 502(c), which permits state or local use of federal supply schedules for two groups: automated data processing equipment, software, supplies, support equipment, and services in Federal supply classification group 70; and alarm and signal systems, facility management systems, firefighting and rescue equipment, law enforcement and security equipment, and related services in group 84.
Three points in that statute matter to a security buyer. Group 70 and group 84 together cover both the software and the security hardware side of a typical video project. The definition of state or local government explicitly includes local educational agencies and institutions of higher education, so districts and colleges qualify directly rather than by extension. And vendor participation is voluntary: a company selling to the federal government through a schedule is not obligated to sell to you through it, so confirm willingness before you plan around it.
The state-law layer that voids more piggyback buys than any federal rule
Federal permission is necessary but not sufficient, because your own state and local procurement law governs whether you may use a cooperative contract at all. The Uniform Guidance says so directly at 2 CFR 200.318(a): documented procurement procedures must be consistent with state, local, and tribal laws and regulations. Federal rules set a floor, not a ceiling.
The most common failure mode. A buyer confirms the vendor is on a national cooperative contract, confirms the federal rules allow cooperative purchasing, and never checks whether their state authorizes piggybacking onto that specific cooperative. Some states publish an approved list of cooperatives and consortiums and permit nothing outside it. Others require the original solicitation to have contemplated cooperative use in its terms. Others cap the dollar value or the contract term. A purchase that clears every federal test can still be void under state law.
Check three things with your procurement office or counsel before committing: whether your state maintains an approved cooperative list and whether your chosen vehicle is on it, whether the lead agency's original solicitation expressly allowed other entities to purchase from the resulting award, and whether any local board policy imposes a stricter bid threshold than state law does. That last one catches people constantly, because a board can always be more restrictive than the state.
Where AI video analytics changes the procurement math
A software layer that analyzes feeds from cameras you already own is a different procurement object than a camera replacement project, and that difference often moves the purchase into a lighter tier. A rip-and-replace deployment is an equipment purchase with installation labor, priced per camera, and it climbs past formal-procurement thresholds quickly. Analytics software that runs on the cameras you already own has no hardware line, no conduit, and no installation schedule, which is why it frequently lands in the simplified acquisition tier where a comparable hardware refresh would not.
Above: a synthetic illustration created to depict an after-hours door event on a school exterior camera. It is not a real detection capture.
This also lines up with an instruction most buyers never read. 2 CFR 200.318(d) requires procurement procedures to avoid acquiring unnecessary or duplicative items, and directs that consideration be given to consolidating or breaking out procurements to obtain a more economical purchase. If your existing cameras produce usable video and the gap is that nobody is watching them, replacing working hardware is the harder position to defend in an audit file, not the safer one.
What the software layer adds is detection that does not depend on a person watching a monitor. IntelliSee analyzes existing camera feeds for weapons, unauthorized access, loitering, falls, crowd conditions, vehicle events, cell phone use, slip and fall risk, rooftop intrusion, and smoke and fire, and sends alerts within seconds. It does this without facial recognition, which is deliberate: for public agencies facing community scrutiny over surveillance, the absence of biometric identification is frequently the difference between a project that gets board approval and one that stalls. IntelliSee also holds full DHS SAFETY Act QATT designation, the same federal tier as other designated weapons detection providers, which is a documentable data point for the responsible-contractor determination required at 2 CFR 200.318(h).
Funding and procurement are separate questions, and they compound. A cooperative contract determines how you are allowed to buy. Security camera grant programs and the grant funding hub determine where the money comes from, and for private-sector buyers the Section 179 deduction for security systems determines what the purchase costs after tax. Sequence them in that order and you avoid the common trap of winning an award with a spend deadline you cannot procure against in time.
The documentation file that survives an audit
2 CFR 200.318(i) requires records sufficient to detail the history of each procurement transaction, and it names four elements specifically: the rationale for the procurement method, the contract type selection, the contractor selection or rejection, and the basis for the contract price. Build the file as you go rather than reconstructing it during a monitoring visit.
- The method rationale. One page stating the estimated value, the tier it falls into, and why a cooperative purchase was chosen. Cite 2 CFR 200.318(e) by name.
- Proof the vehicle is usable by you. The cooperative's award documents, your entity's membership or participating addendum, and the state authorization if your state maintains an approved list.
- Evidence the original solicitation was competitive. The lead agency's solicitation and award notice. This is the document that carries your competition requirement, so keep the actual file, not a link.
- Basis for price. The contract pricing you are purchasing at, plus whatever you used to conclude it is reasonable. For a micro-purchase this can be research, experience, or purchase history, but it has to be written down.
- Responsible-contractor determination. A short record addressing integrity, public policy compliance, past performance, and financial and technical resources, per 2 CFR 200.318(h). Certifications and designations belong here.
- Conflict of interest check. Your written standards of conduct and confirmation that nobody in the selection had a disqualifying interest, per 2 CFR 200.318(c).
- Scope and acceptance. What was purchased, what was delivered, and who confirmed it. This closes the loop the monitoring visit will open.
Before any of it, run a physical security risk assessment. It produces the needs statement that makes the rest of the file coherent, and it is the difference between a purchase that reads as a considered response to identified risk and one that reads as a vendor-driven buy.
Frequently asked questions
Is cooperative purchasing legal for federal grant funds?
Yes. 2 CFR 200.318(e) encourages intergovernmental and inter-entity agreements for procurement transactions and states that documented procurement actions of this type will meet the competition requirements of the Uniform Guidance. The purchase still has to comply with your state and local procurement law.
Do I still need three quotes if I buy from a cooperative contract?
Not as a federal requirement. The competition was performed by the lead agency that awarded the cooperative contract. Some states and many local board policies impose their own quote requirements regardless, so verify locally before you skip the step.
What is the current micro-purchase threshold for security equipment?
$15,000 under FAR 2.101 as of August 2026, with a simplified acquisition threshold of $350,000. A recipient may self-certify a micro-purchase threshold up to $50,000 annually under 2 CFR 200.320(a)(1)(iv) with documented justification.
Can a school district buy security cameras off a GSA schedule?
Yes, within the authorized categories. 40 U.S.C. 502(c) permits state and local governments, explicitly including local educational agencies and institutions of higher education, to use federal supply schedules for Federal supply classification groups 70 and 84, which cover information technology and security and alarm equipment respectively. Vendor participation in those sales is voluntary.
Does buying AI video analytics require replacing our cameras?
No. Analytics that run on existing camera infrastructure require no hardware replacement, which keeps the purchase scoped as software and services rather than equipment and installation.
The bottom line
Cooperative purchasing is not a loophole, and treating it like one is what gets buyers in trouble. It is a documented, statutorily supported method that moves the competitive work to a lead agency that already did it in public. The work left to you is confirming your entity may use the vehicle, confirming the vendor is on it, and building a file that answers the four questions the Uniform Guidance says an auditor will ask.
The mission has not changed: turning passive cameras into proactive protectors, on the infrastructure you already paid for. If you want to know which cooperative vehicles fit your entity and what a deployment on your existing cameras would involve, start a conversation with our team. If you are still assembling funding, the grant funding resources are the place to begin.