How Public Agencies Can Procure Service Robots

What public procurement of service robots actually requires

Public agencies buy service robots the same way they buy other capital equipment that touches daily operations: you define the job, publish requirements, score responses, award a contract, and prove the fleet works before you pay in full. That path applies to cities, counties, special districts, K-12 districts, colleges, and authorities that run campuses, transit properties, or utility sites.

The goal is not to pick a mascot machine. It is to contract for documented performance: square feet cleaned per shift, delivery runs completed, patrol loops with escalation rules, or material moves with safety stops. When the solicitation describes results, interfaces, and service levels, an OEM-neutral integrator can map multiple robot types to the same specification without locking you into one catalog number.

When you need a formal solicitation

Thresholds differ by state, charter, and funding source, but the pattern is consistent. Purchases above your informal limit need advertised competition unless a statute allows a piggyback, emergency, or cooperative award. Robotics bundles that include financing, software, mapping, training, and multi-year maintenance almost always cross those limits, so plan procurement and IT security reviews together from day one.

Document the business case in plain language: which manual tasks repeat nightly, what failure costs in overtime or overtime callouts, and which spaces are public versus restricted. That narrative becomes the backbone of your performance requirements and later defends the award if someone protests.

How do you write performance-based requirements?

Performance-based specifications describe what the robot must accomplish, under which conditions, with what evidence. Instead of naming a model, specify floor types, slope limits, doorway widths, runtime per battery cycle, noise limits for night cleaning, and how the unit behaves around elevators or crosswalks.

Break requirements into modules: autonomous floor care, indoor delivery, outdoor patrol, or warehouse transport. Each module should list measurable acceptance tests, required training hours, spare coverage, and mean time to restore service. NASPO's fourth edition Practical Guide (2024) walks through the procurement cycle steps where those requirements attach to solicitations and contracts.

Require vendors to submit a deployment plan: site survey method, map versioning, cybersecurity controls, data retention, and decommissioning. That plan is scored alongside price so the cheapest quote cannot hide weak support.

• Coverage metrics tied to maps you approve, not vendor marketing ranges
• Escalation paths for stalls, collisions, and off-route events
• Software update policy with maintenance windows
• Insurance and indemnity aligned to public entity risk

How should evaluation committees score robot proposals?

Use a weighted matrix published before quotes arrive. Typical weights split among price, technical fit, deployment schedule, references in similar public settings, cybersecurity responses, and service network reach. Keep oral presentations optional and scored consistently.

Blind scoring helps when vendors bring flashy demos. Require identical demo scripts on your floor when feasible, or score recorded walkthroughs against the same checklist. Document why the winner beat the next ranked offer; that record matters if council or a protest reviewer asks later.

Where cooperative purchasing fits

Cooperative purchasing shares contracts across governments. NASPO defines it as procurement conducted by or on behalf of one or more public procurement units, and notes programs such as NASPO ValuePoint that aggregate demand to cut administrative cost.

Before you piggyback, confirm your state law and local policy allow it, read the lead agency's solicitation for scope limits, and check whether robotics services, software subscriptions, or data processing were in-bounds. Cooperative awards save time only when your use case truly matches the contract's stated commodity or service category.

What cybersecurity and privacy reviews should ask

Connected robots are IoT devices on your network. CISA's December 2023 Connected Communities procurement guidance gives SLTT officials question sets for vendors on confidentiality, integrity, availability, incident response, and supply chain risk.

Fold those topics into attachment requirements: encryption in transit, patch cadence, logging, remote access controls, and where video or lidar data is stored. NIST's Cybersecurity Framework, version 1.1, is a common reference for structuring supplier expectations even when compliance is voluntary.

NIST Special Publication 800-213A catalogs IoT device cybersecurity capabilities federal buyers may require; local teams can adapt that catalog to patrol cameras, cloud dashboards, and fleet APIs without copying federal clauses blindly.

Accessibility, ADA, and public accommodation

Robots that clean lobbies, deliver meals, or patrol plazas interact with the public. Requirements should address audible and visual signals, predictable paths, speed limits near entrances, and procedures when a unit blocks a curb ramp or elevator door.

Involve your ADA coordinator early. Specify how staff override autonomy during events, how maps flag temporary obstructions, and how you communicate robot operations to visitors who use mobility devices or service animals. Accessibility is a design constraint, not a post-award retrofit.

Records retention and transparency

Patrol and cleaning robots generate logs, video, and sometimes audio. Your solicitation should state retention periods, redaction rules for bystanders, public records act handling, and whether data stays on-prem or in vendor cloud regions you approve.

Define export formats for incident investigations and labor grievances. If labor partners will review routes, spell out what the union receives and on what schedule. Clear records language prevents a useful security tool from becoming an unmanaged archive.

Acceptance testing and pilot conversion

Split delivery into factory or warehouse checks plus on-site site acceptance. On-site tests should run on your maps during the shift you intend to automate, including worst-case weather for outdoor patrol units.

Hold back a meaningful retention until tests pass: coverage percentage on agreed zones, successful deliveries with human handoffs, or patrol cycles with scripted anomalies. Pilots belong inside the contract as priced options with identical data and security terms so a successful pilot converts without a new solicitation.

Service Robot Co. often supports public buyers as a vendor-neutral integrator: we align robot types to your performance spec, coordinate financing structures allowed under your rules, and service fleets through a nationwide engineer network so acceptance tests reflect how the units will actually be maintained.