ALPR_pre-response_information_session_-_vendors.pptx

Market research discussion

August 2026

Parking Enforcement Technology Modernization Request for Information • Vendor Conference

PURPOSE

Today’s Conversation

SEATTLE POLICE DEPARTMENT • ALPR RFI VENDOR CONFERENCE

Context What we are trying to improve and why.

Future state How a connected enforcement environment could work.

What we need from you Show us how your technology solves the problem.

Questions Clarify the RFI and response expectations.

MARKET RESEARCH

Why We’re Here

SEATTLE POLICE DEPARTMENT • ALPR RFI VENDOR CONFERENCE

We want to understand how technology can make the process itself better.

CURRENT ENVIRONMENT

Today: Uneven System Connectivity

SEATTLE POLICE DEPARTMENT • RFI VENDOR CONFERENCE

Parking Enforcement information exists across multiple systems — some connections are partial, manual, or siloed.

PARKING

PAYMENTS

integrated today

ALPR

operational use; no citation handoff

COURT

one-way citation transfer

PERMITS

partial files / manual lookup

GIS +

CURB RULES

separate reference

COMPLAINTS /

MOTOROLA

separate workflow

TOWING

manual / separate

OPERATIONAL

ANALYSIS

manual / separate

PARKING ENFORCEMENT

OPERATIONS

Field

Citation

Back Office integrated one-way partial / manual siloed / separate Not a technical architecture diagram

FUTURE STATE. OUTCOME BASED

A More Connected Parking Enforcement Environment Bring the right information and capabilities together at the right time, while preserving flexibility in how the solution is delivered.

OPERATIONAL CONTINUITY

OPERATIONAL INSIGHT

SEATTLE POLICE DEPARTMENT • ALPR RFI VENDOR CONFERENCE

Native capabilities Integrations Consolidated functions Allow information to follow the work across field, supervisory, back-office, and partner processes.

Reduce manual handoffs

Avoid duplicate entry

Visibility into the status of related workflows and actions Turn operational information into better deployment, compliance and management decisions.

Understand compliance patterns

Deploy resources where needed

Interpret citation volume appropriately A user-friendly experience and intuitive operational decisions for the officer and management.

FIELD OPERATIONS

Help PEOs quickly determine whether a vehicle is complying and what action, if any, is appropriate.

Understand what applies

Identify what needs attention

Verify and take action efficiently

Leverage GIS data

Native capabilities and integrations

Imagine an officer beginning an enforcement area and the system already understands the relevant curb regulations and parking restrictions. As the officer moves through the area, ALPR identifies vehicles where legally permitted. The system evaluates relevant information such as parking restrictions, payment status, permits, time limits, and other applicable rules. If something requires action, the officer receives useful, actionable information rather than simply another data point. Where appropriate, the citation workflow could already contain available information for the officer to verify. If the situation involves a scofflaw vehicle, towing, or a complaint, the appropriate downstream workflow could be initiated or updated.

MANAGEMENT + ANALYTICS

From Activity to Operational Insight

SEATTLE POLICE DEPARTMENT • ALPR RFI VENDOR CONFERENCE

WE WANT TO UNDERSTAND:

CITATION VOLUME IN CONTEXT

Analysis on citation levels compared with actual parking conditions in each area, including the amount of regulated parking, parking activity, time of day, day of the week, and other variables.

Meaningful insight combines enforcement activity with curb rules, GIS, deployment and other operational data.

The goal is not more citations – it is better information, more effective deployment, and improved parking compliance.

When and where parking regulations or compliance issues exist so they can be prioritized by the officer and operation

Enforcement and compliance trends related to regulations in the area

That operational data is being used deploy PEO resources effectively

MANDATORY CAPABILITY

ALPR Compliance Is a Design Requirement

SEATTLE POLICE DEPARTMENT • ALPR RFI VENDOR CONFERENCE

NO-COLLECTION ZONES

Use City-provided mapping to prevent collection where ALPR use is restricted.

EDGE CONDITIONS

Prevent capture inside restricted areas even when the enforcement vehicle is outside the boundary.

OPERATOR CONTROL

Suspend and resume collection when operationally necessary, with appropriate controls.

RETENTION + AUDIT

Support required deletion, access controls, logging and demonstrable compliance.

Do not just tell us you can comply, explain how the controls work in practice.

WHAT WE WANT TO LEARN

What We Want to Learn From the Market

SEATTLE POLICE DEPARTMENT • ALPR RFI VENDOR CONFERENCE

Officer Experience What does a shift look like using your solution?

Integration & Compliance How does information move across the parking ecosystem and comply with the law?

Process Improvement How does your solution streamline enforcement workflows?

Municipal Lessons What have you learned from implementing in other municipalities?

Emerging Capability What should Seattle consider that is not outlined in the RFI?

Future Flexibility How does the solution adapt as laws, operations, and integrations change?

Tell us how your system modernizes a parking enforcement operation.

RFI PROCESS

Response + Next Steps

SEATTLE POLICE DEPARTMENT • ALPR RFI VENDOR CONFERENCE

SUBMISSION REMINDER

Use the attached RFI Response Template.

Questions due 8/18/2026.

Proposals due 8/27/2026.

Do not use the system’s “Submit Draft Response” feature to prepare your response.

Additional technical materials may be submitted in addition to the completed template.

WHAT HAPPENS NEXT

City reviews RFI responses

Clarification or additional information may be requested

Demonstrations / follow-up discussions may be conducted

Findings inform requirements and potential future direction Questions & discussion image1.jpeg image2.png image3.png