Mobility Services Operations Management

BC-3490 Level 1 Automotive & Mobility 12 providers 18 API surfaces 2 rated strong or better

Operations of shared and on-demand mobility services — ride-hailing, car and micromobility sharing, and Mobility-as-a-Service aggregation — including service catalogue, trip operations, fleet rebalancing, driver and rider operations, dynamic pricing, partner integration, and city / regulator engagement.

Mobility Services Operations Management (BC-3490) is a level-1 business capability in the Automotive & Mobility model. The catalog holds 18 API surface(s) from 12 provider(s) that can perform some part of it, 2 of them rated strong or better. Reach is the vendor surface that lands on this capability — it is not a claim about what any particular organisation has deployed.

Where this capability definition comes from. This capability is part of a published business-architecture model that API Evangelist did not author. It is redistributed here under CC-BY-4.0. Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 Changes: Consolidated from 333 per-L1 YAML files into one JSON; English only (upstream i18n/ omitted); descriptions whitespace-normalised. No capability was added, removed, renamed or re-parented. Source repository · NOTICE and third-party framework attributions

Authorities this capability cites

Cited by the capability model itself. These frameworks are referenced, never redistributed, and citing one does not imply its owner endorses this listing.

Sub-capabilities

Mobility Service Catalogue Management BC-3490.10

Definition of mobility service types, pricing plans, and geographic coverage zones.

3 providers, 3 API surfaces

Trip and Booking Operations BC-3490.20

Capture, matching, dispatch, and lifecycle management of mobility bookings and trips.

6 providers, 7 API surfaces

Shared Fleet Operations BC-3490.30

Operational handling of the shared fleet including rebalancing, on-site servicing, and damage control.

1 provider, 1 API surface

Driver and Provider Operations BC-3490.40

Onboarding, compliance, settlement, and performance management of drivers and other service providers.

2 providers, 2 API surfaces

Rider Operations BC-3490.50

Onboarding, support, and trust-and-safety operations for riders and end customers of mobility services.

1 provider, 1 API surface

Dynamic Pricing and Demand Management BC-3490.60

Demand forecasting and operation of dynamic pricing, surge, and promotion engines for mobility services.

no catalog coverage

Multimodal Aggregation and Partner Operations BC-3490.70

MaaS partner aggregation, multimodal trip composition, and inter-operator settlement across mobility partners.

no catalog coverage

Mobility Regulatory and City Operations BC-3490.80

Engagement with cities and regulators on permits, data sharing, and curb / parking operations.

1 provider, 1 API surface

Providers that reach this capability

Ordered by rating band. Reach means a provider publishes an API surface that can perform some part of this capability — it is not a claim that any particular organisation has deployed it.

Strong 2 Solid coverage with minor gaps
AppyWayParking1 API59.5AutopayBooking1 API57.0
Developing 7 Usable, with meaningful gaps to close
CabifyEstimatesJourneys2 APIs52.8UberPartnersRiders2 APIs49.5LyftConcierge RidesCost EstimatesRide TypesRides4 APIs48.2TIERSystemVehicles2 APIs45.4OptibusPrivate Hires1 API45.1DottSystem1 API43.4ParkWhizBookings1 API43.0
Thin 3 Limited public surface area
TicTacTripResults1 API36.9SpotHeroReservations1 API35.1PickerserviceProvider1 API28.9
This page carries no rating. Capabilities are not rated. A capability is a description of what a business does, not a thing a company publishes, so a Kin Score would have nothing to measure.
The edge table is a Pro feature. This page shows which providers and tags reach Mobility Services Operations Management. The underlying tag → capability edges — each with the quoted fragment of the provider's own OpenAPI that evidences it, a calibrated confidence score, and the contract-provenance gate it passed — are available through the API, along with company-level capability maps. Only edges at confidence ≥ 0.7 with evidence found verbatim in the source contract are published at all.

See plans →  ·  How the edges are graded →