Six months ago, Urban Sharing launched Version 2.0 of its on-street operations platform for shared micromobility operators.
The tool – named Urban Crew – uses smart algorithms to automate tasks for field teams and suggests best operational solutions based on historical and real-time data.
Fast forward to today and the fleet management solution has introduced more than 60 new features since the rollout of its second edition last autumn.
“This speed of development is unheard of in shared micromobility,” Urban Sharing Chief Revenue Officer Tom Nutley tells Zag Daily.
“The differentiator is not only the expansiveness of Crew’s features and functionalities. It’s how we’ve understood what shared micromobility operators genuinely need to improve their bottom line, how quickly we’ve been able to give them those features, and the outcome that the operator gets.”
SLA-compliance at the software’s soul
Since launching Version 2.0 last autumn, Urban Sharing has released two new iterations of Crew in just six months: V2.1 and V2.2.
Last month, Zag took a closer look at V2.2’s functionalities – Crew’s latest iteration which officially rolled out at the end of March.
After a three-week tried and tested period with operators on the ground, Urban Sharing has added more features to Crew V2.2’s lineup of capabilities.
These include a deeper integration of Service-Level Agreements (SLAs), which are contractual obligations that shared operators are required to uphold as they serve the tender season.
To suit the unique operational needs of complex shared micromobility systems – think Barcelona’s AMBici or Paris’ Vélib’ scheme for example – Urban Sharing has designed custom plugins which cater for even the most complex SLAs.
“Both large and small-scale systems can often have highly complex SLAs,” says Tom. “Some stations can’t be empty or full for 30 minutes, whilst others might be limited to 60 minutes. Collectively, the limit for all stations may be 120 minutes, meanwhile, operators have to collect every broken bike within 24 hours.
“Operators can use Crew’s custom plugins to meet these unique demands from cities, ensuring that they’re never in breach of their SLA requirements.”
Through visual heat maps, Crew shows SLA compliance across stations, areas and bikes to enable operators to easily spot where service targets are being met and missed. This allows Urban Sharing to understand how the operator is currently performing independently or with another fleet management solution before launching with Crew.
“Not only does this enable us to support operators to tweak their configurations in accordance with SLA gaps, but we can also evaluate the impact of Crew and refine it for the future.”
According to Tom, the constant shaping of fleet management tools is fundamental to intrinsically align the shared micromobility experience of both operators and end-users. He believes that tenders released over the last seven years haven’t truly had end-users or operators in mind.
“Rather than viewing shared micromobility through supply and demand, cities artificially augment systems by requiring an even spread of bikes across the entire scheme, even if the entire scheme isn’t used equally. What this has led to is the penalisation of operators for ‘breaching’ SLAs, even if the action gives end-users a better experience.
“The granularity of Crew lets operators achieve what they’re targeted to achieve whilst meeting SLA requirements, and in turn giving the best experience to the end-user.”
Advanced visuals and controls
Urban Crew 2.2 introduces new tools to help operators see exactly what matters, when it matters, and to turn insights into immediate action.
At the core of this release are live filters which allow operators to dynamically refine the map view in real time. Users can filter stations, vehicles, and areas based on multiple parameters such as SLA breach status, grace periods, occupancy thresholds, or asset IDs.
For example, an operator can highlight all stations with over 80% occupancy or vehicles with low battery levels across the network without needing to refresh or reload the map.
Operators can also select any area on the map to immediately display summary information about the vehicles and stations within it, and then filter their view to focus solely on that area. In addition, vehicles can now be colour-coded based on their operational state, providing visual cues about the health of the fleet.
“The map is no longer just a visualisation tool — it’s an operational command centre where operators can configure, filter, and prioritise tasks in real time based on live network conditions,” says Tom.
Building on these insights, Urban Crew 2.2 introduces the Task Cart for operators to build efficient workflows. Tasks such as battery swaps, station visits, or maintenance jobs can be added to the cart directly from the map. The platform then automatically calculates the optimal route to complete the selected tasks, factoring in distance and estimated task durations. This aims to improve operational efficiency, reduces decision-making time, and helps operators to meet their SLAs more cost-effectively.
Traffic-dependent suggestions
Traffic has always been a big consideration in shared micromobility systems. Stations and areas are frequently analysed for their historic traffic patterns, and operators act in accordance with the predicted impact this has on demand.
But Crew 2.2 takes these insights one step further to help operators balance the impact traffic it has on operational efficiency. It does so by adding road forecasts to every task and route it suggests for operational teams – automatically resorting priorities based on real-time traffic.
“We take the real-time road conditions that drivers have to constantly manage and manipulate and incorporate them into our suggestions. Why is that important? Because the more time field teams are sitting in traffic, the fewer jobs they can complete in an hour,” says Tom.
“We don’t give out ‘priority’ suggestions that end up wasting considerable amounts of their shift – our purpose is to make field teams as efficient as possible. Operators have been asking for something like this for a decade.”
What’s next?
Version 2.3 is scheduled for release at the end of June with a stronger focus on integration. Tom teases some of the features to expect, such as tighter integrations with third-party APIs and a Crew Analytics API for accessing data from Business Intelligence solutions.
Additionally, operators will have more filtering options, improved asset ID information, and more action buttons for operational convenience. One example of a new Crew action button is triggering a broken vehicle to flash or make a noise so that operational staff can easily identify which vehicle it is they need to collect from a station of, say, 50 bikes.
Behind the rapid development of Urban Crew is one fundamental approach: getting the systems into the hands of the people on the ground.
“The best people to test whether our features are working are the people using the system on the street and in the operational warehouse.”
After Urban Sharing tests each new feature itself, it’s passed on to clients as ‘flag features’, which enables operators to leave feedback for Urban Sharing to incorporate before full-scale launch.
Ultimately, Tom believes that it’s a unique combination of knowledge and technical expertise from Urban Sharing – a former operator that helped launch Oslo Bysykkel back in 2016 – and client feedback that has helped make the “impossible possible” for shared micromobility operations.
And it’s a blend that’s proven to be effective with Urban Crew, racking up close to 50,000 assets since its inception three years ago.
“Our experience as an operator means we now build our fleet management solutions to be easy to navigate, simple to dive into detail, and readable by non-technical teams.
“We have a team made up of former operational managers and infrastructure partners, and we have the technical expertise in writing clear channel code. But it’s our close collaboration with operators over the last 10 years and constant client feedback that means our action is first and foremost based on industry needs, rather than us thinking there’s a problem and assuming we know how to solve it.
“That’s the biggest difference between a fleet management solution that works for operators and one that doesn’t.”
