Prohibit parallel rides

The product feature prohibit parallel rides (PPR) prevents on-demand rides from being booked when a suitable public transport option is available. This helps public transport providers avoid competing with their own scheduled services.

During matching, ioki Platform compares on-demand solutions with public transport alternatives. If the configured prohibit parallel rides adapter decides that public transport is a good enough alternative, the affected on-demand solution is removed from the offer.

The following is a schematic overview of the process.

graph TD
    classDef iokiBerry color:#d11064,stroke:#d11064,stroke-width:2px
    classDef iokiGrey stroke-width:2px

    A[Ride request]:::iokiBerry --> B[On Demand Request]:::iokiGrey
    A --> C[Request External System]:::iokiGrey
    B --> D[On Demand Solutions]:::iokiGrey
    C --> E[Public Transport Solutions]:::iokiGrey
    D --> F[On Demand Filtering]:::iokiGrey
    F --> G[Offer]:::iokiBerry
    E --> G
    E -. "Scoring-Based Filter" .-> F
    H([Generic Scoring of all Solutions]):::iokiGrey -.-> D
    H -.-> E
    I([Custom Filter Adapter]):::iokiGrey -.-> F

    linkStyle 7 stroke:#d11064

Scope and limitations

To use this feature:

Public transport alternatives must be activated.
An Adapter for Prohibit Parallel Rides must be set in Prohibit parallel rides in the tenant settings of a product.
This feature filters on-demand solutions only through the configured prohibit parallel rides adapter.
The setting Existence of intermodal solutions suppressed DRT-only solutions can still suppress DRT-only solutions independently of the product feature flag.
You can optionally combine this feature with Skip prohibit parallel rides for rides with validated user location to bypass the adapter for specific rides.

Activate this feature

Roles: Super Admin

Navigate to the management settings of the product.
Within the Product features section, select the checkbox Prohibit parallel rides.
Optional: Select Skip prohibit parallel rides for rides with validated user location if rides at validated user locations should bypass the prohibit parallel rides adapter. This requires Preprocess ride requests with snapping user locations in Matching. For details, see Skip prohibit parallel rides for rides with validated user location.
Select Save.

Configure this feature

This feature can be configured within the section Prohibit parallel rides in the tenant settings of a product.

You can optionally combine this feature with Skip prohibit parallel rides for rides with validated user location to bypass the prohibit parallel rides adapter for rides at validated user locations. For regular ride creation, this requires Preprocess ride requests with snapping user locations in Matching.