Lifetime Citizen Portal Access — AI Briefings, Alerts & Unlimited Follows
TAPS advances shared micromobility licensing update; vendors must reapply and meet performance standards
Loading...
Summary
Staff reviewed Aurora's licensed shared micromobility program, explaining permit terms, fleet caps (initial cap of 300 devices), operator reserve requirements and geofencing/response rules; the committee agreed to move the program forward to a study session for further Council consideration.
Scott Baumann, Parking and Mobility Services Manager for Public Works, presented an update on Aurora's shared micromobility licensing program and the committee agreed to advance the program to a future study session for further Council discussion.
Baumann described the program as a licensure model that has existed since devices first appeared in 2017. He said the city issues one‑year licenses, monitors vendor performance and can withhold renewal for operators that fail to meet standards. Baumann said the initial fleet cap for incoming vendors was lowered from an earlier cap and that the current initial license allows vendors to deploy 1–300 devices; staff may authorize increases if an operator demonstrates sustained high utilization.
On financial safeguards, Baumann said the program requires an infrastructure fee per ride and an operator reserve to cover device retrieval and storage if a vendor exits the market. He said the operator reserve requirement was reduced to $15,000 (previously $25,000). Paul Walter Browett, senior transportation planner, described operational requirements: devices must carry a contact number and vendors must respond to business‑hour requests to move improperly parked devices within four hours; staff can also require digital dashboard access to monitor fleets in real time.
Baumann and Browett described program management tools including geofencing to create slow zones and no‑ride/no‑park areas (medical campuses and select commercial properties), incentives/disincentives for correct parking and a rebalancing plan to position devices near transit. The presenters said vendors typically have offsite maintenance warehouses in the metro area but the city does not require a local warehouse.
On operator history, staff said Bird left Aurora after reporting operational challenges (staff said Bird did not provide a formal explanation; staff believe maintenance/hiring challenges contributed) and that Lime's application was put on hold; if Lime or another vendor wishes to return they must reapply and complete the current application review.
Committee members asked about device deployment areas, geofencing, complaint tracking and whether devices can be used on trails; staff said devices are currently prohibited on city trails and that the city will need to coordinate with Parks for any change. When asked whether the committee supported continuing the program and moving it to a study session for further Council discussion, members agreed to advance the item.
The committee's action was to send the program forward for continued Council consideration; no final Council decision was made at the meeting.
