Platform

Intelligence across your mobility operation

Five capabilities, one system. A forecast made in one part of the platform reaches the vehicle it concerns in another — no export, no second tool.

Forecasting

Demand forecasting

MobilitiQ learns how each zone behaves by hour of day and day of week, then projects the trips it should expect. Forecasts run several hours ahead, so an operator can prepare for a peak rather than react to it.

Planners see where riders are likely to be before the peak, instead of reconstructing it afterwards.

Zone detail · demand forecastIllustrative interface
Zone 14 · CommercialTrips per hour
Coverage 0.82
666 AM10 AM2 PM5 PM
Observed Next-hour forecast

A demand choropleth beside a zone chart of observed trips per hour with the next-hour forecast appended.

  1. Ingest

    Past trips grouped into zones and hourly buckets.

  2. Learn

    How demand moves with the hour, day and week.

  3. Predict

    Expected trips for every zone, hour by hour.

  4. Act

    Predictions guide relocation ahead of demand.

Typical useA weekday evening peak that shifts between neighbourhoods.

Dynamic Routing

Routing that adapts in real time

Routes are planned over the real road network, so distances and travel times reflect how vehicles actually move through a city. A new request goes to the vehicle that can take it, and its stops are fitted in without breaking commitments to riders already on board.

Routes stay workable as conditions change, rather than being fixed at the moment of dispatch.

Dispatch · route recalculationIllustrative interface
Real-time operationsLive
  1. t=612sRequest r-208 received · zone 7
  2. t=613sVehicle v-031 assigned · ETA 3 min
  3. t=615sRoute recalculated · 2 stops inserted
  4. t=640sVehicle v-063 relocating to zone 9
  5. t=655sRequest r-204 completed

An operational map showing an active route across the network, beside a live feed of requests, assignments and route recalculations.

  1. Request

    A rider submits a pickup and drop-off.

  2. Match

    Nearby vehicles compared to find the best fit.

  3. Insert

    New stops sequenced into that vehicle's route.

  4. Track

    Every assignment and update hits the live feed.

Typical useAbsorbing new demand mid-shift without disrupting assigned trips.

Fleet Management

Live fleet monitoring and dispatch

One map carries the whole fleet: idle, heading to a pickup, passengers on board, relocating, or at a charger. Select any vehicle for its assignment, remaining stops, charge level and range. Idle vehicles can relocate automatically toward expected demand, with the operator in control.

Dispatch, relocation and charging are decided against the same picture, not three separate ones.

Fleet managementIllustrative interface
Fleet5 active · 1 idle
  • v-014Passenger onboard2 riders · stop 3 of 471%
  • v-027Passenger onboard1 rider · stop 2 of 254%
  • v-031Driver to pickupETA 3 min88%
  • v-063RelocatingTarget zone 946%
  • v-084To chargerStation 1 · queue 012%
  • v-052IdleAwaiting assignment

A coverage overlay beside a fleet roster listing vehicle state, current task and battery charge level.

  1. Observe

    Vehicle status and open requests update live.

  2. Compare

    Coverage shows vehicles against predicted demand.

  3. Relocate

    Idle vehicles guided toward under-served zones.

  4. Review

    Per-vehicle activity kept for the service day.

Typical useRebalancing a fleet that has drifted to one side of the service area.

Ride Pooling

Shared ride matching

Riders can travel alone or share. Two riders heading the same way are combined into a single trip, with pickups and drop-offs ordered so both journeys still make sense, and detour limits bounding how far a shared trip may deviate.

More riders are served per vehicle without the shared trip becoming unpredictable.

Ride pooling · shared tripIllustrative interface
Request A1 seat
Request B1 seat
Shared trip1 vehicle · 2 riders
  1. 1Pickup A
  2. 2Pickup B
  3. 3Dropoff B
  4. 4Dropoff A
Your rideCo-rider

Two ride requests merging into one shared trip with an ordered pickup and drop-off sequence across two rider lanes.

  1. Offer

    The rider chooses a private or shared ride.

  2. Group

    Compatible riders paired into one trip.

  3. Sequence

    Stops ordered so both journeys work.

  4. Bound

    Detour limits keep the shared route reasonable.

Typical useCorridor demand where many riders travel the same direction.

Sustainability

Built for electric fleets

Electric and conventional vehicles run side by side. Battery level and remaining range are tracked per vehicle, stations show how busy they are, and vehicles running low are sent to charge as part of normal dispatch. With pooled trips, that is how the platform supports lower-emission service.

Electrification is planned into the operating day instead of interrupting it.

Charging operationsIllustrative interface
Charging operationsLive
  1. t=708sVehicle v-084 low charge · routing to station 1
  2. t=712sStation 1 queue length 0
  3. t=744sVehicle v-014 stop 3 of 4 reached
  4. t=766sVehicle v-052 signed in · available
  5. t=781sCharging session started · v-084

A map with charging stations marked, beside a live feed of low-charge vehicles routing to stations and charging sessions starting.

  1. Track

    Battery level updates as vehicles operate.

  2. Trigger

    Low vehicles flagged and routed to a station.

  3. Queue

    Station availability stays visible to the operator.

  4. Return

    Charged vehicles rejoin the available fleet.

Typical useRunning a mixed electric and conventional fleet through a full day.

See the platform on your network.

We will walk through the platform against a service area you actually operate.