REQUEST FOR INFORMATION

RFI 63-2701

MICROMOBILITY SERVICES PROGRAM

CITY OF PHOENIX

STREET TRANSPORTATION

200 W WASHINGTON STREET, 10TH FLOOR

PHOENIX, AZ

85003

RELEASE DATE: September 4, 2026

DEADLINE FOR QUESTIONS: September 18, 2026

RESPONSE DEADLINE: October 8, 2026, 4:00 pm

City of Phoenix

REQUEST FOR INFORMATION

RFI 63-2701

Micromobility Services Program

1. INTRODUCTION

2. INSTRUCTIONS

3. SCOPE OF WORK

4. EVALUATION PROCESS

5. STANDARD TERMS AND CONDITIONS

6. SPECIAL TERMS AND CONDITIONS

7. DEFENSE AND INDEMNIFICATION

8. INSURANCE REQUIREMENTS

9. SUBMITTALS

10. PRICING PROPOSAL

Attachments:

A - Exhibit A (map)

Request For Information #RFI 63-2701 Title: Micromobility Services Program

1.Introduction

1.1.Summary

This Request for Information (RFI) is issued as a means of discovery and information gathering for a Micromobility Services Program.

The RFI is for planning purposes only and should not be construed as a solicitation nor should it be construed as an obligation on the part of the City to make any purchases.

This RFI should not be construed as a means to pre-qualify vendors.

This is not a formal solicitation, but a request for interested parties to provide information as specified herein.

The City of Phoenix is not responsible for any costs incurred in order to participate in this process. All information provided is at the respondent's own expense. The City of Phoenix intends to issue a formal solicitation in the future based on the RFI responses.

Participation in this RFI is voluntary.

No purchases will be made as a result of this request. Any price information provided shall be used for general comparison purposes only. Do not include applicable state and local taxes.

OBTAINING A COPY OF THE RFI AND ADDENDA

Interested parties may download the complete RFI and addenda from https://procurement.opengov.com/portal/phoenix. Internet access is available at all public libraries.

1.2.Background

The City of Phoenix Street Transportation Department (“City”) is responsible for building and maintaining 5,000 miles of arterial, collector and local streets with the goal of providing a safe environment for all roadway users. The City launched a Shared Micromobility Program

(Program) on January 20, 2023. Over the course of the Shared Micromobility Program, there have been over 1.6 million trips, with an average of over 36,000 trips per month.

The area of operations covers 48 square miles, including 15 square miles that operate under a designated parking model. The current fleet cap is 3,000 devices. The Program has helped support major events in downtown Phoenix including the Super Bowl, the NCAA Women’s Final

Four, the Red Bull Show (Indy cars), among others.

The City seeks to gather industry knowledge, technical capabilities, and operational best practices regarding the delivery of shared pedal bicycles, electric bicycles (e-bikes), electric scooters (e-scooters), adaptive vehicles (e.g., handcycles, trikes, wheelchair attachments), and related mobility services.

https://procurement.opengov.com/portal/phoenix

The City’s objective is to continue improving a safe, dependable shared micromobility program that fits within the broader regional transportation network.

The City is interested in expanding the service area by an additional 20 square miles. The goal is to strengthen multi-modal travel options, improve first and last mile connections, and support trips that reduce reliance on personal vehicles.

1.3.Contact Information

Melodie Mendivil

Procurement Officer

200 W Washington Street, 10th Floor

Phoenix, AZ 85003

Email: melodie.mendivil@phoenix.gov

Phone: (602) 534-7230

Department:

Street Transportation

1.4.Timeline

All times are Local Arizona Time

City reserves the right to change dates and/or locations as necessary. All times are local

Phoenix time.

RFI Posted: September 4, 2026

RFI Inquires Due Date: September 18, 2026, 4:00pm

RFI Submittal Due Date: October 8, 2026, 4:00pm

RFI Electronic Submittal:

melodie.mendivil@phoenix.gov

2.Scope of Work

2.1.Purpose

The City of Phoenix Street Transportation Department ("City") seeks to gather industry knowledge, technical capabilities, and operational best practices, regarding the delivery of shared pedal bicycles, electric bicycles (e-bikes), electric scooters (e-scooters), adaptive vehicles (e.g., handcycles, trikes, wheelchair attachments), and related mobility services. The

City’s objective is to continue improving a safe, dependable shared micromobility program that fits within the broader regional transportation network.

mailto:melodie.mendivil@phoenix.gov tel:(602)534-7230 mailto:melodie.mendivil@phoenix.gov

2.2.Goals

The City is particularly interested in receiving responses from qualified operators capable of demonstrating:

• Operational Excellence: Strong operational presence, responsive rebalancing of fleet equipment, rapid resolution of right-of-way (ROW) obstructions and complaints, large event support, and ability to maintain service during extreme weather (e.g., extreme heat, dust storms, etc.).

• Safety & Hardware Integrity: Durable, well-maintained vehicles and hardware equipped with reliable, safety features, thermal management, and accessible mobile application interfaces.

• Access & Pricing: Transparent pricing models, availability of adaptive vehicles, and reliable service delivery in all areas where the Program operates.

• Data Transparency: Compliance with open data standards (MDS/GBFS), real-time reporting, and verifiable performance metrics.

• Community Engagement: Proactive community outreach, rider education, supportive during large events, and collision/complaint mitigation processes.

• Long-Term Viability: Organizational capacity, sound business models, and financial stability capable of sustaining multi-year operations.

2.3.Respondent Instructions

Please provide the following information in your response. Respondents may submit information for all or a subset of the sections listed. If a specific question is not applicable to your operational model, please mark as "N/A – Not Applicable" and provide a brief explanation.

2.4.Request for Information

1. Respondent Qualifications & Organizational Capacity

A. Contact Information: Provide company name, corporate address, primary contact details (name, title, email, phone), and key partner or subcontractor details.

B. Corporate Governance & Financial Capacity: Describe your corporate ownership structure, governance, and financial capability to capitalize and sustain operations in the

Phoenix market.

C. Scope of Services: Detail the core services provided directly or via subcontractors (e.g., dockless e-scooters, docked/dockless bikeshare, adaptive vehicles, transit integration planning).

D. Comparable Market Experience: Provide details on three (3) comparable municipal programs operated within the past three (3) years, including:

1) Municipality name, program start/end dates, and contract/permit status (e.g., renewed, expanded, terminated).

2) Maximum and average deployed fleet size by vehicle type.

3) Average monthly trips and daily utilization rate (trips per device per day).

4) Parking systems, regulations, and/or restrictions.

5) Coverage area of program and density.

2. Defining Success and Key Performance Indicators

A. How do you define a well-functioning shared micromobility program?

B. What strategies do you use to operate and maintain a reliable program?

C. What success measures or indicators do you use to evaluate the program’s performance?

D. What actions or practices help strengthen the program and keep it running effectively?

3. System Operations, Reliability & Resilience

A. Operational Capacity & Demand Forecasting: Describe your methodology for:

1) Fleet sizing and seasonal demand forecasting.

2) Rebalancing operations (fleet redistribution).

3) Determining the density of parking corrals.

4) Describe the criteria used to determine when local staffing is required, including any fleet minimum or trip-volume thresholds. Include in the description how staffing levels, and field coverage would change at different deployment levels.

B. Historical Performance Data: Provide performance data from three (3) comparable operating markets, particularly:

1) Deployed vs. authorized fleet percentages. What factors determine your fleet deployment percentage (seasonality, events, repairs, operations team size)?

2) Device availability vs. downtime (percent of unavailable fleet due to maintenance, low battery, or communication loss). What is your daily average percentage of available vehicles?

3) Average idle time and percent of fleet inactive for more than 24, 48, and 72 hours.

What is the threshold in hours that triggers a vehicle relocation?

C. Describe your operations under extreme heat, severe weather events, emergency situations, and construction detours.

4. Complaint Resolution, Responsiveness & Customer Support

A. Ticket Lifecycle: Describe your workflow for documenting, logging, and resolving reports of improperly parked, damaged, or unsafe vehicles.

B. Verification & Escalation:

1) What mechanisms prevent customer support tickets from being closed without physical or verified corrective action?

2) How are unresolved tickets escalated internally?

3) What audit trails, geo-tagged photos, or data feeds do you provide City staff to confirm that issues have been resolved?

4) What evaluations do you perform to identify trends and how do you determine when modifications are needed?

5. Vehicle Hardware, Battery & Thermal Specifications

A. Vehicle Types: Specify the device types you are prepared to operate in the City of

Phoenix (e.g., e-bikes, pedal bikes, e-scooters, seated devices, trikes, adaptive vehicles, cargo devices).

B. Vehicle Specifications:

o Braking mechanisms.

o Wheel diameter, tire type, and suspension features.

o Lighting, reflectors, and other visibility features.

o Kickstand design.

o Onboard location hardware and positioning accuracy tolerances.

o Remote diagnostics, fault detection, and automated lock-out capabilities.

o User feedback capabilities.

o Materials, coatings, and surface treatments used at the rider contact points and how these components are designed to maintain safe and comfortable operation under high temperatures.

C. Battery Technology & Safety:

1. Describe the testing conducted on your device batteries, including evaluations focused on high-temperature performance above 120°F.

2. Explain the active and passive thermal management systems and heat-protection mechanisms used in your devices.

D. Describe your preventive maintenance procedures.

E. Describe your incident & risk mitigation practices.

F. Provide information about safety metrics, including historical averages from three (3) comparable markets within the past three (3) years:

o Mean Distance Between Failures (MDBF) and Mean Time to Repair (MTtR).

o Historical rate of brake, battery, and connectivity failures.

o Vehicle lifespan expectations (expressed in months, total trips, and total miles) and fleet age distribution (percentage over 12, 24, and 36 months).

o Record of thermal related battery incidents over the past five (5) years.

6. Geofencing, Location Technology & Parking Management

A. Geofencing Precision: Describe horizontal location accuracy, entry and exit latency, false-positive and false-negative rates, and methods used to prevent abrupt deceleration when entering low-speed or no-ride zones.

B. Advanced Positioning: Describe the technologies used to improve location accuracy in dense urban or low-signal environments such as Bluetooth beacons, visual positioning/computer vision, or orientation sensors.

C. Parking Compliance & Verification:

o Describe your end-of-trip photo verification workflows, including automated image analysis, human review processes, and accuracy rates.

o Explain the systems you use to prevent corral overcrowding and how to re-route users from a full parking area.

o Describe your response procedures for identifying tipped or fallen vehicles, including how issues are detected and how quickly they are addressed.

D. Infrastructure Requirements: Specify whether your system requires physical infrastructure, charging stations, painted markings, or proprietary hardware in the right-of-way. Clarify whether any recommended hardware presents interoperability barriers for other vendors.

E. Infrastructure Installation: Describe your experience installing shared micromobility parking corrals and related infrastructure in other jurisdictions. Describe your installation capabilities such as bicycle racks, wheel stops, delineators, pavement markings, signage, and decals. Include your typical installation specifications, permitting considerations, maintenance responsibilities, and any applicable design standards or best practices followed during implementation.

F. Explain how you manage shared spaces, such as parks and trails, where shared micromobility users must share a limited space with pedestrians, bicyclists, and others.

Specify your experience, and technology abilities to keep all the users safe. What are the challenges in managing these spaces and how do you overcome them?

7. Operational Flexibility & Turnaround Capabilities

A. Scaling Capacity: Provide a detailed schedule (in calendar days) that includes your timeline required to complete the following potential program modifications:

o Deploying an additional 100 devices.

o Expanding the geofenced service area by 10 square miles.

o Outlining or installing 25 new designated parking corrals.

o Configuring temporary slow-speed, no-parking, or no-ride zones for special events or emergency situations.

B. Right-of-Way (ROW) Management: Describe procedures for mitigating ROW obstructions (e.g., vehicles blocking sidewalks, ADA ramps, driveways, or emergency accesses) and standard response timeframes.

8. Operational Strategies and Programs for Safety, Affordability & Accessibility

A. Area Operations: Describe your operational strategies to ensure consistent vehicle availability, proactive rebalancing, and quality service in all areas, include how these strategies may differ in areas with a special designation, such as Mobility Areas.

B. Affordability Programs: Describe how your affordability program is structured to serve all users, including:

o Qualification criteria, enrollment, and renewal processes.

o Discount structure (e.g., waived unlock fee, reduced per-minute rates, capped price per day/month).

o Non-smartphone and cash-based payment options.

o Program retention rates and historical utilization (percent of total trips taken using affordable or reduced-fare options in other markets).

C. Community Engagement: Detail your community outreach strategy, including enrollment events, safety demos, rider education, and partnerships with local community-based organizations.

D. Safety Promotion: Describe any successful and innovative approaches to encourage safe riding practices and helmet use.

E. Adaptive Vehicles Integration: Describe options you intend to provide for adaptive vehicles, include booking methods, delivery models, and maintenance support.

9. Pricing, Fare Structures & Pass Products

A. Rate Structure: Describe your pricing models, include pay-as-you-go, daily/monthly passes, user unlock fees, per-minute rates, and dynamic pricing (if applicable).

B. Interoperability & Transit Integration:

o Are passes or memberships portable across different municipalities served by your company?

o Describe capabilities for integration with regional transit fare cards, mobility-as-a-service (MaaS) apps.

C. Incentives: Describe the promotional pricing you intend to implement, including any loyalty programs, or parking incentives (e.g., ride credits for parking in designated corrals).

D. Describe any business-to-business (B2B) models you currently implement (e.g. selling monthly/ annual passes in bulk for employees of a company, guests of hotels, students or staff at universities, etc.).

10. Data Standards, Privacy & Reckless Riding Mitigation

A. Open Data Specifications: Describe your capability to stream real-time data compliant with the latest version of the Open Mobility Foundation (OMF): Mobility Data Specification

(MDS) and General Bikeshare Feed Specification (GBFS).

B. Reckless Riding Prevention: Detail the technologies or methods you use to detect sidewalk riding, tandem riding, or illegal stunt maneuvers (e.g., onboard accelerometer monitoring, sidewalk-detection sensors) and associated disciplinary policies.

C. Consumer Privacy & Security:

o Specify what user data you collect and your retention schedule.

o Explicitly state whether Personally Identifiable Information (PII) or telemetry data is shared, commercialized, or sold to third parties.

o Outline your cybersecurity measures used to prevent unauthorized access to customer data.

11. Local Context – Phoenix Operations & Economic Model

A. Service Area & Scale: Provide recommendations regarding optimal fleet sizes, device density, and phasing expansion areas for the City’s 48 square mile operational footprint.

B. Labor Model: Specify your operational staffing model (e.g., direct W-2 employees vs.

1099 independent contractors vs. third-party logistics subcontractors) for rebalancing, maintenance, and field operations.

C. Zero-emission Fleet Logistics: Describe your local operational fleet (e.g., rebalancing vans/trucks/ cargo bikes). What percentage of your rebalancing and operational fleet consists of electric vehicles (EVs) or cargo bikes?

D. Environmental sustainability: Describe your end-of-life battery recycling programs and vehicle disposal or decommissioning practices. What percentage of vehicle components are recyclable?

E. Financial Viability & Revenue Streams:

o Detail your primary revenue streams (e.g., user fares, corporate sponsorships, advertising, transit subsidies).

o Discuss the conditions required for your financial viability in a competitive, multi-vendor municipal regulatory environment.

12. Special Events Provide any documentation of your processes and protocols for special events, including:

1. What level of involvement have you had when planning for large events, such as World

Cup matches, Olympic Games, large festivals, Super Bowl? Describe the event, plan and experience. What would you have done differently?

2. How do you determine the placement and capacity of the temporary corrals?

3. Have you implemented bike/scooter valet services? Describe your experience.

4. What are the elements of your emergency protocols. Provide examples.

5. What elements do you use to communicate with the public during events (IAM, A-frame signs, wayfinding, staff on-site)?

6. How do you ensure clear pedestrian pathways?

7. Provide an example of a post-event report that you have generated.

13. Program expansion: The City has approved two additional expansion phases. Phase 2 adds

11.32 square miles to the service area, and Phase 3 adds another 9.3 square miles. (See attached map)

1. What conditions do you consider necessary for successful operation in the new service areas? Please address:

o Number of parking corrals to serve the new areas.

o Number of additional devices required to maintain reliable operations.

o Examples of cities with similar operating conditions.

o The key factors you consider necessary to support this expansion.

3.Submittal Requirements

Consultants shall create a FREE account with OpenGov Procurement by signing up at https://procurement.opengov.com/signup. Once you have completed account registration, browse back to this page, click on "Submit Response", and follow the instructions to submit the electronic response.

An electronic PDF copy of the material shall be submitted following the outline provided herein.

The submittal shall include:

• A one-page cover letter prepared on the company’s letterhead and signed by an authorized employee of the company Provide primary contact information and contact person’s telephone number, e-mail address, and company webpage. A brief summary shall be included in the cover letter that provides information on the company’s background and expertise as relates to this RFI.

https://procurement.opengov.com/signup

• Each submittal should clearly mark which problem statements are addressed with the solution being proposed. They should be marked using the problem statement designation number provided in the scope of work. Solutions can be proposed for one or more problem statements. Vendors do not have to propose solutions to all problem statements.

4.Instructions to Vendor

4.1.PREPARATION OF RESPONSE

It is the responsibility of all vendors to examine the entire RFI and seek clarification of any requirement that may not be clear and to check all responses for accuracy before submitting a response.

1. The City does not reimburse the cost of developing, presenting or providing any response to this RFI. Responses submitted for consideration should be prepared simply and economically, providing adequate information in a straightforward and concise manner. The vendor is responsible for all costs incurred in responding to this RFI. All materials and documents submitted in response to this RFI become the property of the

City and will not be returned.

4.2.SUBMISSION OF INFORMATION

Responses must be in possession of the Department on or prior to the exact time and date indicated in the Schedule of Events. Late submittals may not be considered. The prevailing clock will be the City Department’s clock.

Offers should be submitted electronically via the City’s e-Procurement Portal by clicking on

“Draft Response” via https://procurement.opengov.com/portal/phoenix/projects/288995. Offerors that are unable to submit electronically should contact the Procurement Officer to discuss the logistics of hard copy submittals. Offerors must be registered with OpenGov by signing up via https://procurement.opengov.com/signup. Vendor training guides can be found at: https://opengov.my.site.com/support/s/article/ca6d1285-1e48-4a21-bb0d-715edb7794ed

It is the responsibility of the Offeror to ensure that the Offer is timely and to confirm that there are no technical reasons that any Offer submitted electronically may be delayed. The date and time on the upload as received/stamped by the City’s e-Procurement Portal will provide proof of submission and verification whether the Response was received on or prior to the exact time and date indicated in the Schedule of Events.

Please DO NOT submit links to Google Docs, Dropbox Paper, or similar services. Your offer may be deemed non-responsive if your offer is supplied utilizing these services.

4.3.WITHDRAWAL OF SUBMITTAL

https://procurement.opengov.com/portal/phoenix/projects/288995 https://procurement.opengov.com/signup https://opengov.my.site.com/support/s/article/ca6d1285-1e48-4a21-bb0d-715edb7794ed

At any time prior to the solicitation due date and time, an Offeror (or designated representative) may withdraw the Offer by clicking “Unsubmit Response” on the Offer submission via the City’s e-Procurement Portal.

4.4.INQUIRIES

All questions that arise relating to this solicitation should be directed via City’s OpenGov e-

Procurement Portal and must be received by the due date indicated in the Schedule of Events.

The City will not consider questions received after the deadline. All questions concerning or issues related to this solicitation must be presented in writing.

The Procurement Officer will answer written inquiries in an addendum and publish any addenda on the City’s OpenGov e-Procurement Portal.

4.5.PUBLIC RECORD

All submittals in response to this RFI shall become the property of the City and become a matter of public record available for review pursuant to Arizona State law.

If a vendor believes that a specific section of its response is confidential, the vendor shall isolate the pages marked confidential in a specific and clearly labeled section of its response. The vendor shall include a written statement as to the basis for considering the marked pages confidential including the specific harm or prejudice if disclosed and the Procurement Officer will review and make a determination.