CITY OF TUCSON

REQUEST FOR PROPOSAL

270108

RED LIGHT, SPEED AND PHOTO ENFORCEMENT

Due Date: Thursday, October 22, 2026

City of Tucson

255 W Alameda St

Tucson, AZ 85701

Procurement portal https://secure.procurenow.com/portal/tucson-az

Public Portal https://secure.procurenow.com/portal/tucson-az/projects/283759

PUBLISH DATE: September 30, 2026 https://secure.procurenow.com/portal/%7Bproject.government.code%7D https://secure.procurenow.com/portal/%7Bproject.government.code%7D/projects/%7Bproject.id%7D https://secure.procurenow.com/portal/%7Bproject.government.code%7D/projects/%7Bproject.id%7D

CITY OF TUCSON REQUEST FOR PROPOSAL NO. 270108

BUSINESS SERVICES DEPARTMENT Page 2 of 69 SHARED SERVICES PROCUREMENT DIVISION RESPONSIBLE CONTRACT OFFICER: Raquel Duarte

255 W. ALAMEDA, 6TH FLOOR, TUCSON, AZ 85701 PH: (520) 837-4469

Attachments:

A - Offer and Acceptance C - General_Terms_and_Conditions_Data_Protection_and_AI J - Price_Sheet

BUSINESS SERVICES DEPARTMENT Page 3 of 69

A. NOTICE

A.1. CITY OF TUCSON

NOTICE OF REQUEST FOR PROPOSAL NO 270108

TITLE: Red Light, Speed and Photo Enforcement

SUBMITTAL DUE DATE: Thursday, October 22, 2026 AT 2:00 P.M. LOCAL AZ TIME

PRE-SUBMITTAL MEETING DATE: Wednesday, October 7, 2026

TIME: 10:30 am LOCAL AZ TIME

LOCATION: Microsoft Teams meeting Join:

https://teams.microsoft.com/meet/23299346094685?p=bWFD3EZdbFdnaTBDcE Meeting ID: 232 993 460 946 85 Passcode: Sh2Vz79g

QUESTIONS SHALL BE DIRECTED TO: Raquel Duarte

(520) 837-4469 raquel.duarte@tucsonaz.gov

Posted Date: Wednesday, September 30, 2026

Competitive sealed offers for the material or service specified in this solicitation must be submitted through the City’s online bidding system. No late submitted offer will be accepted or considered.

Reponses submitted in physical form or by facsimile or email will not be considered. Offerors are cautioned to commence the submittal process sufficiently ahead of time to allow for unanticipated delays resulting from things like a slow internet connection, internet outage, difficulty uploading large documents, differing system requirements, etc.

Questions about this solicitation must be addressed to the responsible Contract Officer listed herein.

BUSINESS SERVICES DEPARTMENT Page 4 of 69

B. INTRODUCTION

B.1. Summary

The City of Tucson is issuing a Request for Proposal (“RFP”) to qualified companies with applicable expertise to provide an automated traffic enforcement safety device system (“ATESD”) for the City of Tucson. This includes the installation, implementation, and operation of certain aspects of the ATESD, training and continuing performance of the hardware, software and supporting services needed for this system to function properly. The proposals shall be for a complete “turnkey” operation. The ATESD includes two main areas of focus, (1) red light enforcement and (2) speed enforcement.

B.2. Background

Subject to voter approval repealing Proposition 201 during the November 2027 General Election, and prior to the passage and enforcement of the Arizona Prohibit New Photo Traffic Enforcement Systems Measure of 2026, the City of Tucson intends to procure a qualified contractor to implement, operate, maintain, and support a comprehensive automated traffic enforcement program focused on improving roadway safety and decreasing traffic injuries and fatalities. The oversight and administration of this effort will be overseen by the City of Tucson Department of Transportation and Mobility and the Tucson Police Department.

B.3. Contact Information

Raquel Duarte contract officer Email: raquel.duarte@tucsonaz.gov Phone: (520) 837-4469 Department:

Police Department mailto:raquel.duarte@tucsonaz.gov tel:(520)837-4469

BUSINESS SERVICES DEPARTMENT Page 5 of 69

C. SCOPE OF WORK

C.1. Scope of Work (General Requirements)

A. The program shall support enforcement of speeding and/or red-light violations through one or more technologies. The City intentionally does not prescribe specific technology; proposals may include:

1. Fixed pole-mounted systems

2. Mobile camera vehicles

3. Portable trailer systems

4. Corridor speed enforcement

5. Hybrid deployments

6. Emerging technologies with demonstrated operational success

B. Enforcement Capabilities

1. Red-light enforcement, including “Right on Red” enforcement capability

2. Speed enforcement

3. School zone capability

4. Work zone capability (optional)

5. Multiple lane monitoring

6. Day/night operation

7. High evidentiary image quality

8. Capability to record all violations exceeding ten (10) mph over the posted limit (speed systems) or in violation of a solid red ball (red-light systems)

9. Capability to count violations and total through-traffic volumes

C. Camera and Detection System

1. The successful Vendor agrees to provide all necessary labor and equipment for automatic traffic enforcement safety device services with the City of Tucson.

a. Camera System

i. The Contractor shall provide a turnkey red-light or speed enforcement camera system, by location, capable of capturing digital video images of violators. Desirable features include a scanning LIDAR camera system (speed enforcement), HD video camera or equivalent, and multiple digital still photographs including front and rear scene images capturing the approach and departure of the offending vehicle, and front and rear license plate images. Proposers shall detail all other information produced by the system(s).

ii. In addition, proposals must provide the following information:

I. A complete digital system, including digital camera, housing, poles (if necessary), detection system and equipment, and all hardware and software necessary to produce a violation citation from the video image.

II. Camera housing shall be vandal-proof and securely mounted atop a Contractor-supplied pole, or a City-owned pole where City permission is granted. The Contractor must demonstrate that equipment proposed for installation atop existing City-owned poles meets safety design parameters required by the City.

III. Cameras shall provide sharp, high-definition, well-defined, well-illuminated images yielding the maximum number of recordable violations, with auto aperture

BUSINESS SERVICES DEPARTMENT Page 6 of 69 across the widest possible lighting range; from a black vehicle on black macadam in darkness without streetlights or moonlight, to full sunlight reflecting off a white vehicle against high-contrast surroundings.

IV. Cameras shall record each violation during all periods of light and dark and in varying weather conditions, and shall display current day, date, and time so correct operation can be verified from a remote terminal.

V. Cameras shall collect data on the image including violation number, date, time, direction of travel in which the violation occurred, and vehicle speed (speed systems and red-light “Right on Red” enforcement).

VI. Detection shall be non-invasive. No road surface cutting or disruption to existing detector loops is permitted.

VII. Hardware and software shall allow the City to view color digital HD images of all violations on a computer monitor for violation determination and verification.

VIII. Hardware and software shall facilitate quality control review of images to verify accurate license plate data and shall be capable of attaching vehicle owner information to the violation record.

iii. Environmental and Physical Durability I. Equipment rated for sustained ambient temperature to at least 120 degrees

Fahrenheit under direct solar load II. Ingress rating of IP66 or NEMA 4X for dust and monsoon-driven rain III. Surge and lightning protection IV. Tamper and impact detection with alerting, and a stated repair or replacement interval for a vandalized or disabled unit V. At least two referenceable deployments in a comparable desert climate

D. Installation, and Materials

1. Mounting and Standards

a. All construction and materials shall meet the PAG Standard Specifications for Public Improvements, Vol. 1, 2015.

b. Stationary units shall be mounted on an ‘A’ Pole per PAG Standard Detail T 401.

c. Conduit shall meet Section 732 of the PAG Standard Specifications for Public

Improvements, Vol. 1, 2015.

d. All costs to furnish and install equipment necessary for operation of the devices shall be included in the Contract. No separate or additional payment will be made for this equipment, installation or maintenance during the contract term.

2. Permits, Plans, and Subcontracting

a. The Contractor shall obtain all required permits, agreements, licenses, and insurance for installation. Locations may be on roads maintained and controlled by the City of Tucson; the Contractor is responsible for obtaining all appropriate permissions and permits.

b. The Contractor shall prepare detailed installation plans, which shall become the property of the City.

c. The Contractor may employ subcontractors for portions of its responsibilities, but shall not subcontract any portion of its installation responsibilities without express written City permission. Where consent is granted, the Contractor remains fully responsible to the City for all acts and omissions of its subcontractors.

3. Decommissioning

BUSINESS SERVICES DEPARTMENT Page 7 of 69

a. Decommissioning plan covering equipment removal, pole and foundation removal, and site restoration within sixty (60) days of termination or relocation. Stated cost and lead time to relocate a unit shall be provided; relocation shall not require a new procurement or contract amendment.

b. Traffic Signal Operational Requirements

c. Yellow clearance and red change intervals for through movements shall operate in accordance with 2020 ITE Recommended Practice.

d. Yellow clearance and red change intervals for left turn movements shall operate in accordance with NCHRP Report 731 (2012), Guidelines for Timing Yellow and All Red Intervals at Signalized Intersections.

e. Operation of red-light photo enforcement shall not alter these times.

4. The Contractor shall be responsible for complete installation of each Intersection

Enforcement Camera System except for connections to the City's traffic signal systems made inside a traffic signal cabinet.

a. All installations shall be in accordance with all current professional standards as set forth by the City of Tucson Department of Transportation and Mobility (DTM), the Arizona Department of Transportation, and the Manual on Uniform Traffic Control Devices (MUTCD).

b. The Contractor shall work in conjunction with the City of Tucson Department of Transportation and Mobility and the ITS Signals Supervisor, in all matters related to City traffic signal connections.

c. The Contractor shall ensure that a traffic barricade plan is submitted to the City for approval for any work being performed in the roadway by either the Contractor or its Subcontractor.

d. The Contractor is required to obtain all required work permits and comply with all the requirements set forth in it.

e. Any damage to the roadway caused by the installation (and/or maintenance) of the Contractor’s equipment shall be repaired to the satisfaction of the City of Tucson Department of Transportation and Mobility at the cost of the Contractor.

f. All of the Contractor’s installation processes shall conform to local, state, and federal requirements and guidelines and be approved by the City of Tucson Department of Transportation and Mobility.

g. Installation of loops must be in compliance with ADOT and CALTRANS specifications.

h. Loops installed within pedestrian crosswalks shall be done in a manner that does not leave any rough surfaces.

i. The City's traffic signal equipment meets NEMA (National Electrical Manufacturers'

Association) Traffic Control Systems Standards.

j. The City of Tucson uses Econolite Cobalt Controllers.

k. The Contractor's equipment shall meet or exceed present and future NEMA Traffic

Control Systems Standards and be compatible with Econolite Cobalt Controller Standards.

l. The Contractor shall use isolation relays or equivalent to protect traffic signal equipment from noise, transient voltage, and any related remote interconnect or interference problems in accordance with the NEMA standard.

m. The Contractor's system shall provide a convenient means of disconnecting the power for the Photo Enforcement System from the traffic signal system.

BUSINESS SERVICES DEPARTMENT Page 8 of 69

n. The City’s Contract Administrator shall retain the right to disconnect the Contractor's system from the traffic signal system when, in the opinion of the City's Department of Transportation and Mobility, it is in the City's best interest to do so for purposes of maintenance, repair, troubleshooting, or other reasons related to the proper operation of the traffic signal system.

o. The Contractor's camera system shall monitor status of the traffic signal via field terminals (120 VAC).

p. The Contractor shall coordinate with the local utility company in the area of each installation to provide the most convenient and economical source of power.

q. The City agrees to assume any additional expense for power should such a connection be made directly to an existing power source currently located in conjunction with a traffic signal cabinet or street light service.

r. However, the Contractor shall provide a separate circuit breaker should this power originate from the same disconnect as the traffic signal and it shall be well marked.

s. In ground loop placement, maintenance, and timing sequences for camera activation shall be the responsibility of the Contractor at the direction of the City’s Contract Administrator after consultation with the Contractor and Traffic Engineering.

t. Installation shall be accomplished at night and in a manner so as to minimize disruption to traffic flow.

u. The Contractor shall replace any City owned traffic signal equipment damaged by the Contractor or his Subcontractor including loops, controller equipment etc., at the Contractor’s expense.

v. Locating of loops and other underground facilities, as required by Arizona State Law, shall be the responsibility of the Contractor. This is commonly referred to as "Blue Staking” because the one-call system for underground facilities in this area is called “Arizona 811”.

E. Testing, Repair and Maintenance

1. Operations Health and Administration

a. Remote monitoring and device diagnostics

b. Automatic fault notification to appropriate personnel of any system failure, malfunction, or condition rendering the system inoperable

c. Centralized administration

d. Configurable enforcement schedules

e. Geographic deployment management

f. Contractor-performed remote status checks not less than two (2) times daily to verify proper operation, with a log of checks maintained and available for City inspection

2. Maintenance and Service Levels

a. All repair and maintenance of the program and related equipment is the sole responsibility of the Contractor, including maintaining camera casings and all other equipment in reasonably clean and graffiti-free condition.

b. Initial response to any camera or system malfunction within twenty-four (24) hours of detection, with all reasonable efforts to restore full operation within seventy-two (72) hours.

c. Where a system is not fully operational within seventy-two (72) hours of reporting, the Contractor shall credit the monthly invoice in the amount of the prorated Fixed Monthly

BUSINESS SERVICES DEPARTMENT Page 9 of 69

Fee for the downed approach for each day the approach is down, including the initial twenty-four (24) hours.

d. The system shall be designed so that ninety percent (90%) of all system malfunctions can be repaired within four (4) hours.

e. Device-level availability of not less than 98 percent per calendar month measured at the enforced approach, with mean time to repair defined by severity and service credits for missed targets.

f. Scheduled maintenance windows approved by the City in advance.

g. Preventive and corrective maintenance and support.

F. System Operation

1. Processing Capability and Ownership

a. The Contractor must have in-house capability for performing all citation-processing services without third-party assistance or reliance on outsourced third-party processing centers. Preference will be given to contractors that produce and support all software without third-party suppliers and possess the ability to modify software code as necessary. This requirement addresses the review and validation of violations for citation issuance; it does not restrict the use of commercial cloud hosting, infrastructure subprocessors, or federated identity services described in Sections 12.A. and 14, provided such providers meet the security requirements of Section 8.

b. The Contractor must own, or hold documented licensing rights to, all intellectual property.

c. The Contractor shall promptly notify the City of all modifications to the system.

d. Stationary units shall not be mounted on traffic signal poles or arms, or on any other active City traffic control equipment. Mounting on City-owned streetlight poles is permitted only with express written City permission and a demonstration that the proposed equipment meets applicable safety design parameters.

e. A separate metered service (power) pedestal shall be provided for all stationary units per PAG Standard Detail T 801. All costs of establishing a power source, including Tucson Electric Power fees and permits, shall be included in the Contract.

2. Workflow and Timeliness

a. Automated violation workflow with review interfaces for authorized personnel.

b. The system shall process violations from designated enforcement zone approaches and locations into a format reviewable by City personnel.

c. City personnel shall be provided access to review pre-processed violation data within seven (7) days of the violation.

d. Following City authorization to issue a citation, the Contractor shall print and mail the citation within five (5) days of receipt of authorization. Primary mailing shall be by USPS first class mail as required by A.R.S. and City Ordinance. The City may, at its discretion, allow email notification as a supplemental measure subsequent to first class mail.

e. The system shall maintain an electronic record of each citation and a log memorializing all pertinent dates and times, including date of violation, date owner information was obtained, date the violation was released for City review, date the violation was accepted and released by the City, date the citation was mailed, and the date and manner of adjudication.

3. Evidence Integrity and Chain of Custody

BUSINESS SERVICES DEPARTMENT Page 10 of 69

a. Secure evidence management, court-ready evidence packages, chain-of-custody documentation, and configurable retention policies.

b. Original captured images and videos shall be preserved unaltered, with a cryptographic hash generated at the point of capture. Any crop, enhancement, redaction, or other derivative prepared by Contractor staff shall be stored as a separate file with its own hash and shall not overwrite or replace the original.

c. An audit record shall exist for every derivative image identifying the individual who created it, the date and time, the action taken, and the source file, retrievable with the evidence package.

4. Pre-Screening and Review Determinations

a. Documented pre-screening criteria used by Contractor staff to determine which captured events are advanced for law enforcement / Courts review. Criteria shall be approved by the City before use, placed under change control, and shall not be modified without prior written City approval.

b. The record of each determination shall capture the reviewing member’s identity, credential used, date and time, decision, and the evidence set presented at the time of the decision, and shall be immutable and exportable.

5. Registered Owner Data

a. The Contractor shall maintain, at its sole cost and expense, access to vehicle owner registration information from the Arizona Department of Transportation / Motor Vehicle Division or equivalent service, and equivalent access to out-of-state vehicle owner registration information, sufficient to issue violation citations as required by A.R.S. and City Ordinance.

b. Identification of the source and legal channel for all registered owner data used to prepare violation packages, for both Arizona and out-of-state plates, including the specific authorization under which the data is obtained and whether any City of Tucson originating agency identifier is used.

c. Registered owner data shall be used solely to prepare and process the specific violation. Such data shall not be retained beyond the citation lifecycle, aggregated, resold, or used for any other purpose.

d. The Contractor shall obtain vehicle registration information to issue citations and traffic violation correspondence.

e. The Contractor shall obtain registration and Driver’s License information after submitting the request through the Motor Vehicle Division of the state of issuance. The requests shall be received within three days of transmittal to the state of issuance – on 90% of requests. This is to meet the requirements of issuing citations promptly which include registration, Driver’s License expiration dates, class, and status, when such information is included in the reply from the state of issuance. Failure to obtain this information may result in liquidated damages and/or may result in a letter of noncompliance.

6. Court Support

a. Bidirectional integration with the Tucson City Court case management system, including filing of citations and evidence to the court and return of hearing dates, dispositions, pleas, judgments, and dismissal reason codes.

b. Ability to produce the citation import file in the schema published by the City as an appendix to this solicitation.

BUSINESS SERVICES DEPARTMENT Page 11 of 69

c. Completion of a successful data transfer test with Tucson City Court technical staff prior to contract execution or notice to proceed.

d. The City may require an “evidence book” for use in court, meeting the specific requirements of the requesting court.

e. For contested citations, the Contractor shall provide expert witness testimony regarding the accuracy and technical operation of the ATESD, in writing or in person as jurisdictional requirements dictate, and shall supply all courts of competent jurisdiction with a statement of technology.

7. Public Inquiry

a. A toll-free telephone number for citizen inquiries.

8. Security, Identity, and Access Management

a. Two-Tier Security Model

i. Tier 1 — Program baseline (entire platform). All program data, including images, video, plate reads, violation records, citation records, and associated metadata, shall be handled as City of Tucson Data Classification Level 3 (Restricted) under Administrative Directive 1.08-7 and protected using controls consistent with the NIST SP 800-53 moderate baseline and NIST SP 800-63B.

ii. Tier 2 — Criminal justice information (CJI) enclave. Any component that receives, stores, processes, or transmits CJI shall comply in full with the FBI CJIS Security Policy. For this program, CJI includes at minimum:

I. Registered owner returns obtained through Nlets, the AAMVA state-to-state exchange, or the Arizona Criminal Justice Information System (ACJIS) II. Any data element returned from ACJIS or NCIC, including stolen vehicle file results III. Any record associated with a criminal charge arising from evidence captured by the system IV. Tier 2 requirements:

I. Execution of the CJIS Security Addendum by the Contractor and by each individual with access to the Tier 2 enclave.

II. Fingerprint-based background checks and CJIS security awareness training for all personnel with Tier 2 access, with records provided to the City on request.

III. Logical and administrative segregation of the Tier 2 enclave from the general platform, with the boundary documented in the system architecture submitted for ITD review.

IV. Where the Contractor performs registered owner lookups or otherwise handles CJI on behalf of the City, the Tier 2 enclave resides in the Contractor environment. The Contractor is responsible for building, operating, and attesting to that enclave, and shall identify the hosting arrangement and every subprocessor within its boundary.

V. FIPS 140-3 validated cryptographic modules for CJI at rest and in transit.

VI. Proposers shall describe how the Tier 2 boundary is defined and enforced, and shall identify any hosting or subprocessor arrangement carrying a current CJIS attestation.

VII. Final CJI scope will be established by written determination of the TPD Local Agency Security Officer and the Arizona Department of Public Safety

BUSINESS SERVICES DEPARTMENT Page 12 of 69

CJIS Systems Officer. The Contractor shall comply with that determination at no additional cost.

9. Authentication and Access Control

a. Authentication, access control, and logging shall meet or exceed the FBI CJIS Security

Policy and NIST SP 800-63B, including identity proofing, authenticator strength, and session management.

b. Multifactor authentication is mandatory — not optional — for all administrative, violation review, and Contractor support accounts.

c. Phishing-resistant authentication methods preferred, consistent with CJIS advanced authentication requirements.

d. Single sign-on federated to the City of Tucson Microsoft Entra ID tenant using SAML 2.0 or OIDC, with SCIM 2.0 provisioning, automated deprovisioning, and role assignment mapped to Entra security groups.

e. Named user accounts only. No shared or generic accounts for human access, and no Contractor use of City credentials.

f. Role-based access control.

g. Configurable session timeout, account lockout, and failed logon handling meeting City standards.

h. City personnel access via secure, encrypted connection using a confidential user account, a high-speed Internet connection, and an approved web browser.

i. Personnel security screening for all Contractor staff with access to City data, at a level consistent with the applicable tier above.

10. Encryption and Audit Logging

a. Encrypt data in transit and at rest min of AES 256bit and FIPS140-3 endpoints per

CJIS.

b. Detailed audit logging consistent with the FBI CJIS Security Policy and the NIST SP 800-53 AU control family, capturing authentication events, authorization and role changes, evidence access and export, violation review determinations, configuration changes, and deletions.

c. Audit records shall identify the user, IP, date and time, source, event type, and outcome, and shall be protected against modification and deletion by any account, including Contractor administrators.

d. Audit records retained not less than three (3) years and available to the City through API or syslog export to the City security information and event management (SIEM) platform at no additional cost.

11. Payment Card Handling

a. Payment processing shall keep City systems outside PCI DSS scope, with the

Contractor or its processor as merchant of record and a current PCI DSS v4.0 Attestation of Compliance provided annually. No cardholder data shall traverse or be stored on City infrastructure.

12. Hosting, Architecture, and Integration

a. Platform and Availability

i. Commercially proven solution.

ii. Software-as-a-Service operation preferred, accessible via web-based interfaces and existing CSARC / TPD / DTM technology solutions.

BUSINESS SERVICES DEPARTMENT Page 13 of 69

iii. Administrative, violation review, and back-office citation processing interfaces shall not be openly reachable from the public internet. Access shall be restricted by private connectivity (dedicated circuit, site-to-site VPN, or cloud private endpoint), enforced source-IP allowlisting, or a demonstrated equivalent approved by the City.

Proposers shall describe the connectivity model and any reliance on public endpoints, including identity provider endpoints.

iv. Minimize City-hosted infrastructure.

v. Meet high availability objectives and support disaster recovery.

vi. Stated recovery time objective (RTO) and recovery point objective (RPO) for the hosted platform, with annual evidence of disaster recovery testing.

vii. Non-production sandbox environment with representative data for City integration testing and training.

viii. Not less than ninety (90) days written notice of any change to authentication methods, API contracts, or data schemas.

13. Network and Documentation

a. Field communications provided by the Contractor and independent of the City network.

Any proposed use of City fiber or network transport requires ITD approval, a dedicated network segment, documented ports and protocols, and no Contractor-managed devices on the City enterprise network.

b. Back office citation processing communications shall be point-to-point over secure, dedicated communication using a City-approved internet protocol, with no public web access, or a demonstrated equivalent approved by the City.

c. Network diagrams, data flow diagrams, and system architecture documentation provided for ITD review prior to installation.

14. Required Integrations

a. Integration capability with existing City of Tucson technology and systems, including but not limited to:

i. AXON FUSUS

ii. Motorola CommandCentral Aware

iii. Verkada Command

iv. SQL / Snowflake (City of Tucson data warehouse), including secure data share

v. Microsoft Entra ID for single sign-on and SCIM provisioning

vi. Amazon S3 within the City of Tucson AWS environment

vii. City of Tucson GIS and ArcGIS Online

viii. City of Tucson SIEM platform

ix. Tucson City Court case management system

x. Citation tracking and management systems, interfaces, and reports managed by any

City department (TPD, DTM, Courts, CMO, ITD, etc.)

xi. Documented APIs shall be provided for future City integration.

15. Applicable City Standards

a. Conformance with City of Tucson information technology, data, and technology safety and security standards, governance, policies, and procedures, including but not limited to camera/VMS standards:

i. Policy No. IT-STD-003A CW, Video Technology Standards

ii. Policy No. IT-STD-003B CW, Video Technology Deployment Standards

iii. Policy No. AD 1.08-8, Artificial Intelligence Policy

BUSINESS SERVICES DEPARTMENT Page 14 of 69

16. Data Delivery, Analytics, and Reporting

a. Analytical Content

i. Violations; daily data availability

ii. Crash trends

iii. Speed compliance

iv. Citation outcomes

v. Equipment uptime

vi. Public safety performance

vii. Program ROI

viii. Equity analysis by deployment area

ix. Reporting by location, approach, movement type (through, left turn, right turn), and hour of day

x. Repeat vehicle counts at one, two, three, and four or more citations

xi. Out-of-state, leased, and rental vehicles where enforcement was unsuccessful

17. Event-Level Data Delivery

a. Event-level data delivered daily to City-controlled storage in the City of Tucson data warehouse environment (Snowflake). A user-initiated export function, report download, or dashboard extract does not satisfy this requirement.

b. Delivery by Snowflake secure data share or to a City-controlled Amazon S3 landing zone within the City of Tucson AWS environment, at the City’s election.

c. One record per detection, per review action, and per citation state change.

d. All detections that did not result in a citation, delivered with standardized rejection reason codes. Rejected events are required for false-positive measurement, image and plate read quality analysis, and equity analysis by deployment area.

e. Standardized code sets for rejection, dismissal, and non-service reasons, supplied as documented reference data rather than free text.

f. Parquet or CSV for tabular data; JSON for nested structures.

g. Versioned data dictionary and schema, with not less than ninety (90) days written notice before any breaking schema change.

h. Documented REST API with an OpenAPI 3.x specification, scoped service credentials, published rate limits, and webhook or event notification for citation lifecycle changes.

i. Geospatial attributes on every event, including latitude, longitude, approach, lane, and direction of travel, in a form publishable to City GIS and ArcGIS Online.

j. City-supplied identifiers carried through the record, including City Court citation number, DTM intersection or signal identifier, and TPD case number where applicable, so that records join to City systems without fuzzy matching where possible.

k. Service level and uptime performance computable by the City from the delivered data rather than reported only by the Contractor.

18. Methodology Disclosure

a. Documented methodology for any before-and-after safety analysis, including crash data source, comparison sites, and treatment of regression to the mean, with the underlying analysis dataset and queries provided to the City.

b. Methodology disclosure for data preparation in crash analysis, speed studies, and other data upon request.

19. Recurring Reporting

BUSINESS SERVICES DEPARTMENT Page 15 of 69

a. Monthly performance reports, with content and timing mutually agreed upon by the City and the Contractor. Agreed reports shall be continuously and automatically updated and available for City review at the City’s discretion.

b. Financial, program progress, monitoring, evaluation, and other reports as required by the City or state law.

c. Authorized City personnel shall be permitted to generate reports directly from the Contractor’s system, and the Contractor shall work with City personnel to create reports satisfying A.R.S. and City of Tucson Ordinance requirements.

d. Annual program reviews and reporting.

e. The Contractor shall maintain and permit on-site inspection of property, personnel, financial, and other records and reports as required by the City to assure proper accounting for all compensation paid.

20. Operational Performance Measures

a. Reduction in speeding violations

b. Reduction in red-light violations

c. Reduction in severe crashes at monitored locations

d. Reduction in fatalities and serious injuries

e. Citation processing efficiency

f. Public transparency metrics

g. Community awareness of enforcement

h. Program expansion readiness

i. Service level agreements, including:

j. System uptime and system availability

k. Mean time to repair

l. Image capture success rate

m. Citation processing turnaround

n. False-positive rates

o. Preventive maintenance intervals

G. Public Trust, Privacy, and Records

1. Privacy and Transparency

a. Data collection minimization

b. Defined retention and destruction schedules

c. Privacy-by-design architecture

d. Public transparency reporting

e. Independent auditing capability

f. Clearly documented evidence handling

g. Cybersecurity controls

h. Protection against unauthorized data use

i. Clear identification of all data collected, retained, shared, and destroyed

2. Data Ownership and Residency

a. Affirmative confirmation that:

i. All images, metadata, citations, reports, analytics, and derivative data remain the exclusive property of the City of Tucson.

ii. All such data shall remain within systems located within, and accessible only from, the United States, and shall not be exported.

BUSINESS SERVICES DEPARTMENT Page 16 of 69

iii. All such data in the Contractor’s possession shall be destroyed upon contract termination.

3. Public Records and Retention

a. Compliance with applicable Arizona public records requirements.

b. The Contractor shall provide a data and information storage solution compliant with

A.R.S., City of Tucson Ordinances, and additional City cybersecurity requirements.

c. The Contractor shall maintain all books, records, documents, data, and other materials relating to the Contract. All documents, records, correspondence, email, notes, audio and video recordings, reports, and other materials relating to the Contract may be public records and shall be submitted to the City upon request. All materials shall be retained until the City advises that retention is no longer required.

4. Algorithmic Transparency

a. Disclosure of:

i. AI use

ii. Automated decision making

iii. Human review process

iv. Bias testing

v. Equity considerations

H. Managed Services and Project Delivery

1. Managed Services Scope

a. System design and site evaluation

b. Project management

c. Deployment strategy, comprising project schedule, milestones, critical path, staffing plan, acceptance testing, cutover plan, and rollback strategy

d. Communications infrastructure

e. Cloud-hosted software

f. Citation processing support

g. System monitoring

h. Hardware and system procurement, deployment, relocation, and maintenance

i. Preventive and corrective maintenance and support

j. Reporting and analytics, and annual program reviews

k. Public information support

2. Advisory Services

a. At the City’s request, the Contractor shall provide advice and counsel regarding ATESD operation, site selection, implementation and administration, public awareness campaigns, and other subjects of mutual interest.

3. Public Information and Education

a. The Contractor shall assist the City in public information and education efforts, including development of artwork for press releases and schedules for any public launch of the program. Actual print and production costs remain the sole responsibility of the City.

4. Training

a. Administrator / super user / subject matter expert training

b. Officer training

c. Court personnel training, including strategies for presenting violations data in court and judicial proceedings and review of the Enforcement Documentation

BUSINESS SERVICES DEPARTMENT Page 17 of 69

d. Technical staff training on maintenance and field troubleshooting of components and systems

e. Refresher training and documentation

f. Minimum aggregate hours: sixteen (16) hours for system and software operation; eight

(8) hours for maintenance and field troubleshooting

g. Additional training provided upon City request at no additional cost

h. Updated and current training materials, manuals, and service bulletins as systems are updated or changed during the life of operation

i. Annually, if required or necessary, the Contractor shall work with the City to arrange a

City representative visit to Contractor headquarters for operational audit purposes I. Commercial Terms

1. The City shall pay a monthly fee for the services provided related to system operation.

2. The City may elect, at its discretion, to pay a monthly rental or lease for installed and operating equipment.

3. All costs for equipment, installation, power service establishment, permits, and utility fees shall be included in the Contract; no separate or additional payment will be made.

1.

C.2. Photo Enforcement Systems

A. Each photo enforcement camera system shall be equipped to detect a violating vehicle, activate the camera system, and produce color images of the vehicle front and rear.

B. Digital camera technology is required.

C. Each system must be capable of clearly photographing and recording the identification of the driver of the vehicle that is reasonably believed to have been operating the vehicle in a manner violating the posted speed limit or failing to stop for a red traffic signal.

D. Cameras shall be capable of consistently obtaining an image of the front of those vehicles so as to clearly identify any driver.

E. Cameras must also obtain a clear image of the rear of vehicles so as to clearly identify the rear license plate.

F. Images shall be clearly discernible and visible to the naked eye without the use of enhancement equipment.

G. Each system must be capable of consistently photographing drivers and license plates regardless of glare or materials used to obscure the license plate from clear view at various viewing angles.

H. Each system must be capable of performing internal calibration tests for speed measurement accuracy and functionality for both mobile and fixed sites.

I. Test failures must prevent further operation of the unit, until the unit is properly functioning.

J. The internal test shall provide a visual and/or auditory signal clearly indicating the operational accuracy or lack thereof.

K. A series of error messages must be displayed to inform the operator of the problems with the system, while in the deployment mode.

L. The City’s Contract Administrator must be immediately (same day) notified of any problems with cameras including down time, inability to upload data, or errors that could impact the validity of the citation(s).

M. The Contractor shall be responsible for all actual costs to the City attributable to Contractor error.

BUSINESS SERVICES DEPARTMENT Page 18 of 69

N. Each speed and red light system shall be capable of accurately measuring speeds and recording clear images of vehicles and drivers either approaching or driving away from the camera.

O. Each system shall be capable of gathering detailed computer data for statistical analysis and histograms for submission at hearings.

P. The Contractor shall produce monthly reports of activity and individual histograms for court and contract oversight purposes.

Q. Each system shall be capable of accurately monitoring several traffic lanes at once.

R. The City, at its sole discretion, reserves the right to reject any equipment that does not meet adequate technical standards.

S. Cameras shall have the ability to operate effectively during periods of nighttime operation and all-weather conditions, including extreme heat as experienced in Tucson with summer ambient temperatures reaching upwards of 120º degrees Fahrenheit.

T. There shall be no minimum number or quota of violations to be generated through the use of photo enforcement technology.

U. For red light camera systems, the delay shall be set to take photographs of vehicles which enter the intersection at a length of time (after the signal light has turned red) as determined by the City’s Contract Administrator.

C.3. Intersection Enforcement Camera Systems (Speed and Red Light)

A. The City has not determined the number of desired intersections, but expects to install a minimum of 5 intersections.

B. Each system shall be defined as inclusive of all equipment and personnel required to complete the operation of an intersection camera enforcing Speed and Red-Light violations.

C. The Contractor shall install all hardware, including the traffic loops or sensor array.

D. The required hardware shall include, at a minimum, all computer interfaces, software, cameras, flash strobes, sensor arrays or loops, wiring, and any necessary appurtenances to provide a fully functional system.

E. The Contractor shall provide intersection enforcement camera systems for all lanes of one (1) approach to a minimum of five (5) intersections, subject to the City’s right to determine the number of sites per Section 2.7.

F. The Contractor shall provide the appropriate number of camera sets to monitor those five (5) systems.

G. The City reserves the right to determine the location and number of sites as it may deem appropriate at the commencement of the Contract. In addition, the City reserves the right to move/relocate existing systems during the life of the Contract, upon request of the Contract Administrator.

H. The Contractor shall provide additional Intersection Enforcement Camera System(s) upon request of the City of Tucson Contract Administrator subject to Contract pricing.

I. One camera system shall be capable of monitoring all through traffic in one direction at one intersection.

J. Each camera system shall also have sufficient computer and any other associated equipment necessary to record, document, and track for record keeping and court purposes, a vehicle and driver entering an intersection against a red traffic signal in violation of ARS 28-645A3(a)

BUSINESS SERVICES DEPARTMENT Page 19 of 69

K. Each camera system shall also be capable of detecting and generating color images of a vehicle and driver entering the intersection on a green or yellow signal light in violation of ARS 28-701(A) (Speed Greater than Reasonable and Prudent).

L. Each system shall also have sufficient computer and any other associated equipment necessary to record, document, and track, for record-keeping and enforcement purposes, the vehicle and driver detected committing a speed violation.

M. The City shall have sole and final authority to designate intersections and the approaches to be monitored.

N. The Intersection Enforcement Camera Systems shall be monitored, calibration checked, and serviced by the Contractor’s technicians as directed by the City’s Contract Administrator.

O. The Contractor’s technicians must be prepared to testify in City Court at the expense of the Contractor.

P. Each Intersection Enforcement Camera System shall have the capability of generating color images of both the front and rear of a vehicle that is believed to have entered an intersection on a red traffic signal while traveling straight through the intersection.

Q. Each Intersection Enforcement Camera System shall have the capability of providing a video recording of each violation to be used by police during review.

R. Each of the camera systems placed at locations shall be operated on a twenty-four (24) hour basis, barring downtime for repairs and maintenance.

S. Malfunctions in the Intersection Enforcement Camera Systems shall not interfere with the continued operation of any traffic control system.

T. Monthly, the Contractor shall physically inspect each approach and site for proper signage, visibility, and functionality. All signs must comply with the City’s Design Standards & Policies Manual. Any deployment not in compliance will be suspended pending proper signage compliance and approval by the City’s Contract Administrator.

U. The Contractor shall also conduct a minimum of one (1) independent speed verification at each site every 90 days.

V. The Contractor’s independent speed verification shall be done with a certified and calibrated instrument and be performed in a manner agreed upon by the City’s Contract Administrator.

W. The Contractor’s independent speed verification tests must confirm the accuracy of the system in accordance with the Contractor’s system specifications.

X. The Contractor shall immediately shut down enforcement of any lane or approach that does not pass the speed verification tests.

Y. The City’s Contract Administrator shall be notified the same day.

Z. The Contractor shall not re-open a lane or approach for speed capture until problems are resolved and the lane or approach has been re-verified for speed capture.

C.4. Portable Speed (Non-Vehicle) Photo Radar Units

A. The portable speed photo radar units shall be deployed in areas identified by the City as directed by the Contract Administrator.

B. The Contractor shall not be required to provide an operator for a deployed portable speed photo radar unit.

C. The portable speed photo radar units cannot block traffic, walkways, or driveways.

D. The portable speed photo radar units must be secure from tampering and damage to the Units, camera, and other hardware.

BUSINESS SERVICES DEPARTMENT Page 20 of 69

E. The portable speed photo radar units must be easily moved to be deployed from location to location.

F. The portable speed photo radar units , depending on the design, may be left on site. The City of Tucson shall have the final opinion on whether any part of the portable speed photo radar units can be left on site.

G. The City will determine the number of portable speed photo radar units to be requested from the Contractor.

H. The portable speed photo radar units shall be capable of performing calibration tests.

I. The portable speed photo radar unit calibration tests shall be required at the start and end of each deployment. If a manual tuning fork is not used to calibrate the speed radar equipment, the alternative method should be explained and directly compared to manual tuning fork methodology in the vendor’s RFP response.

J. The portable speed photo radar unit calibration test documentation shall include the Serial Number of each unit being tested and the serial number of the tuning fork, if used.

K. Each portable speed photo radar unit shall be capable of providing a video recording of each violation to be used by police during review.

L. Each portable speed photo radar unit shall be capable of photographing the rear and front of the vehicle to include the driver.

M. The Contractor’s technicians must be prepared to testify to the accuracy, calibration, maintenance, repair records, technical operation, and effectiveness of the portable speed photo radar unit.

N. The City’s contract administrator will notify the Contractor of all accepted deployment locations seven (7) calendar days prior to actual deployment.

O. Deployment shall mean the portable speed photo radar unit is at a specified deployment site, is operational, and capable of registering violation images.

P. The City intends to deploy portable speed photo radar units twenty-four (24) hours a day, seven (7) days a week, three hundred sixty-five (365) days a year, not including established or needed maintenance. The City’s Contract Administrator will determine the exact location(s) and deployment hours, as needed.

Q. The City may choose to deploy portable speed photo radar units in varying time lengths, anywhere from one (1) to thirty (30) days at a time. The City intends to schedule deployment location changes on Mondays and Fridays but may be subject to change at any time.

R. The City’s contract administrator, in cooperation with Traffic Engineering, will select the specific locations to be monitored based on criteria related to high collision locations, school zones, and citizen complaints.

S. The Contractor shall provide additional portable speed photo radar units upon request of the City of Tucson at Contract pricing.

T. Portable speed photo radar units shall have the ability to operate effectively during periods of all weather conditions, including extreme heat as experienced in Tucson with summer ambient temperatures reaching upwards of 120 degrees Fahrenheit.

C.5. Mobile Speed Radar Systems

A. Mobile Speed (Vehicle) Photo Radar Unit

1. The Contractor shall deploy a mobile speed photo radar unit in complaint areas and areas directed by the Contract Administrator in and around the City.

BUSINESS SERVICES DEPARTMENT Page 21 of 69

2. The mobile speed photo radar unit shall have the…