Texas State Agency Procurement of Robots

Establish agency and mission authority

The acquisition should begin with the public function and the agency's authority to perform it. A robot used for public information, infrastructure inspection, care, or law enforcement can raise different operational rules. The purchasing record should identify the responsible program, intended locations, affected people, and the authority for collecting information or taking physical action.

TRAIGA adds particular governmental AI provisions, including consumer-interaction disclosure and targeted prohibitions. The actual definition and provision matter. Purchasing a capable device does not establish that every optional AI feature may be activated without review. [3, §§ 552.001 and 552.051 through 552.054]

Choose the purchasing framework

Chapter 2155 contains the state's general purchasing rules and procedures, including the Comptroller's role and applicable purchasing requirements. Chapter 2157 addresses automated information systems within its scope. An agency should determine which provisions, delegations, contracts, exceptions, and current procurement rules govern the particular package. [1; 2]

The analysis should include the full arrangement rather than hardware alone. A low initial robot price may be accompanied by recurring software, support, cloud, and connectivity commitments. A pilot or donated unit can also create operational costs and legal duties. The approved acquisition method and contract authority should support the actual commitments the agency makes.

Specify measurable performance and safety

Recommended specifications describe the task, environment, loads, operating limits, human controls, safety evidence, data, and support. Acceptance criteria should distinguish demonstrations from delivered performance. NIST test methods can support repeatable assessment of relevant capabilities, but do not establish a universal government certification of robots. [4]

The contract should address unsuccessful tests, corrective work, payment, warranty commencement, and changes. A promised capability should be measurable under the intended conditions. If a robot will work around the public, the acceptance process should assess those interactions rather than rely only on a restricted test area.

Security and sourcing restrictions

Texas prohibited-technology requirements and agency security policies require their own applicability analysis. The current DIR materials identify covered applications, technologies, and policy resources. The agency should identify the actual vendor, components, funding, users, and devices rather than treat a brand statement as the entire review. [5]

FCC equipment authorization and federal drone procurement or grant restrictions address separate issues. A device that may be purchased under one program is not automatically authorized under every other regime. Conversely, a restriction affecting new equipment authorization should not be restated as a blanket ban on possession. The current operative instrument and any exception should be retained in the procurement file. [6]

Data, records, and contract access

Chapter 552 can reach information held by a vendor within the statute's conditions. The agency should secure access to records needed for operations, public-information responses, retention, audits, and investigations. A dashboard subscription without export rights can create a practical gap even when the agency owns the physical machine. [7, § 552.002]

The contract should address formats, assistance, fees, retention, deletion, access logs, confidential information, and transition. A vendor's confidentiality designation does not automatically establish an exception to disclosure. Actual statutory confidentiality and exceptions must be analyzed record by record, including trade-secret and law-enforcement provisions where applicable. [7, §§ 552.101, 552.108, and 552.110]

Support and continuing approvals

The operating model should identify who approves new software, functions, maps, and data uses. A new feature can change the acquisition's assumptions about safety, records, privacy, or mission authority. Support terms should identify vulnerability handling, remote access, spare parts, service interruption, and the end of support.

An exit plan should explain continued access to records, credential revocation, decommissioning, replacement services, and any retained software rights. The agency should know what happens if funding ends or the vendor ceases service. Those are recommended contract controls tied to the public purpose and applicable duties, not a claim that every state robot contract must use identical language.

Hypothetical agency purchase

A state agency buys an inspection robot with cloud storage and optional facial recognition. The purchasing method for the equipment does not answer whether the agency may activate identification, transfer images to the vendor, or retain them indefinitely. The project should evaluate each function and record the approvals and limits before deployment.