Glossary

This glossary lists commonly used ioki Platform terms that were verified against the current documentation and codebase.

External services

eos.uptrade. eos.uptrade is a ticketing service used by ioki Platform to issue tickets through provider-configured credentials.
Firebase Realtime Database. Firebase Realtime Database is the channel ioki Platform uses to push real-time ride, task, vehicle, and notification updates to passenger and driver clients.
HAFAS. HAFAS is a public transport information system that ioki Platform uses for selected public transport trip, location, departure board, and station integrations.
High Mobility. High Mobility is a vehicle-data platform that ioki Platform uses for supported vehicle telemetry integrations.
LogPay. LogPay is a payment service provider used to handle digital payments and refunds between passengers and providers.
MENTZ. MENTZ is a public transport timetable and journey information system that ioki Platform uses for selected public transport integrations.
Navitia. Navitia is a public transport data and routing platform that ioki Platform uses for selected public transport trip and location integrations.
Spotler SendPro. Spotler SendPro is the external email delivery service used to send emails with provider-specific sender configuration where required.
Stripe. Stripe is a payment service provider used to process digital payments between passengers and providers.
Thingsboard. Thingsboard is the self-hosted IoT platform used to store telemetry data from vehicles.
Twilio. Twilio is the external communications service the platform uses for phone calls and text messages.
VAO. VAO is the Austrian public transport information platform that ioki Platform uses for selected public transport trip, location, and departure board integrations.
Vesputi. Vesputi is a ticketing service used by ioki Platform to issue tickets.

Integrations

Driver API. The Driver API exposes the primitives needed to build a driver client for operational workflows such as navigation and passenger check-in or check-out.
External ID. An external ID is an additional provider- or product-scoped identifier that external partners can use to reference ioki Platform records.
External payment. External payment is a payment method in which an external client handles the payment while ioki Platform assumes it succeeded.
Operator API. The Operator API is the management API used to create, modify, or delete provider- and product-specific data for organizations and fleets.
Passenger API. The Passenger API is the interface used to build passenger clients that request, book, and manage rides.
Platform API. The Platform API is ioki Platform’s backend-to-backend integration API for creating, updating, and deleting core operational records.
Webhook event. A webhook event is the event record created for a subscribed change and delivered with product, provider, and event metadata to a configured webhook URL.
Webhook. A webhook is a configured outbound integration that posts subscribed ioki Platform events to an external URL.

ioki Platform software products

Control Center. ioki Platform’s web-based administration interface for configuring services and managing day-to-day DRT operations. ioki Operator is the newer operator-facing tool for operational work, but Control Center is still in use—both internally by iokians and by Provider and Product Admins—for configuration and for functionality that ioki Operator does not yet cover.
ioki Booking. The newer web-based booking interface for operator-led bookings, particularly when staff create rides on behalf of users by phone. It has replaced the legacy Booking Wizard. Not to be confused with ioki Web Booking, the passenger-facing web booking channel.
ioki Data Bridge. A web-based tool for importing and exporting service data such as drivers, stations, vehicles, and vehicle plannings.
ioki Operator. The operator-facing web app for configuring services and managing day-to-day DRT operations. It is the successor to Control Center for operational work; Control Center remains in use for configuration and for functionality not yet available in ioki Operator.
ioki Passenger App. A white-label passenger app that users use to register, request, book, and manage rides.
ioki Platform. The core backend system that stores operational data, executes core workflows, and powers the ioki DRT product suite.
ioki Reporting. A web-based application for viewing operational and business data generated by ioki Platform.
ioki Vehicle App. The driver-facing navigation app that drivers use to receive, accept, and complete tasks for an active vehicle planning.
ioki Web Booking. A white-label web booking channel with two parts: a passenger-facing website where users request and manage rides in a browser, and an internal control panel where iokians set up and configure the providers behind those sites. Distinct from ioki Booking, the operator-led booking tool.

Matching algorithm

Candidate. A candidate is one possible matching solution under evaluation before the final result is chosen.
Fingerprint. A fingerprint is the structural insertion pattern of a candidate, defined by where the new pickup and dropoff would be inserted into an existing vehicle planning before final routing is calculated. In matching logs, it can also include a time-offset suffix such as 3-4/+5m or 3-4/-5m when ioki Platform tests the same insertion slightly earlier or later. This suffix is displayed in rounded full minutes.
Matching round. A matching round is one pass through one batch of candidates. Another round starts only if no valid solution was found and more candidate batches are still available.
Matching rank. Matching rank is the priority value on a vehicle planning that can override score during final selection. Lower ranks are preferred.
Negotiation time. Negotiation time is the pickup or dropoff time, or time window, that ioki Platform prepares for the offer shown to the passenger after final matching.
Planning list. A planning list is the internal matching candidate that represents one concrete insertion of a ride into one vehicle planning.
Ride variant. A ride variant is one version of a ride request that matching evaluates. Different ride variants can exist, for example, when public transport alternatives or feeder setups are involved.

Notifications

Driver push notification. A driver push notification is a message sent from Control Center to an individual driver and shown as a banner in ioki Vehicle App.
Driver text message. A driver text message is an SMS conversation between an administrator and a driver in Control Center that depends on provider-level Twilio configuration.
Flash message. A flash message is a temporary Control Center message that reports the outcome of an administrator action, such as success or failure.
Mass push notification. A mass push notification is a product-specific broadcast message sent to all users who have at least one ride in that product.
Notification. A notification is a message sent by the platform to administrators, users, or drivers through the relevant app or Control Center.
Phone call. A phone call is a Twilio-mediated connection between a driver and a user in which ioki Platform hides the other party’s real phone number.

Operators

Operator. An operator is an organization within a provider that runs vehicles and can be associated with vehicle plannings and drivers.

Management Area

Management Area. The internal area of ioki Platform for monitoring, managing, and analyzing platform operations. Access is granted through global roles (the access_management_interface permission), so it is used by iokians rather than by a provider’s own Provider and Product Admins—which sets it apart from Control Center, the customer-facing area.

Products

Active vehicle planning. An active vehicle planning is a vehicle planning currently exposed to ioki Vehicle App, usually from 15 minutes before its planned start until 15 minutes after its planned end.
Booking price adapter. A booking price adapter is the fare calculation adapter that determines the base price of a ride before personal discounts are applied and shown during booking.
Booking Wizard. The Booking Wizard is the legacy Control Center flow for operator booking, including defaults such as prebooking selection and copying ride options from the last ride. It is being replaced by ioki Booking.
Booking. A booking is the acceptance of a ride offer that moves a ride into the passenger accepted state.
Cancellation fee adapter. A cancellation fee adapter is the fare calculation adapter that determines whether and how much a user is charged when canceling a ride.
Driver. A driver is the person assigned to operate a vehicle and use ioki Vehicle App.
External pricing. External pricing is a booking price adapter in which ioki Platform does not return a fare and the apps show a configurable custom message instead.
Final price adapter. A final price adapter is the fare calculation adapter that sets the final price of a fare after a ride reaches a final state.
GTFS Flex feed. A GTFS Flex feed is a downloadable GTFS and GTFS-Flex ZIP feed for a product that exposes service data such as stops, routes, schedules, and booking rules.
Intermodal journey. An intermodal journey combines DRT and public transport within one journey, with only the DRT leg booked in ioki Platform.
Journey. A journey is the route information for a vehicle planning, split into legs between consecutive tasks.
Line. A line is a product object that restricts station-based matching to predefined stations, order, and relative times for a vehicle planning.
Matching algorithm. The matching algorithm is the core ioki Platform process that evaluates ride requests and finds the best suitable vehicle planning and task insertion.
Matching configuration. A matching configuration is the set of fundamental matching settings and parameters that also defines a product area.
Matching mode. Matching mode is the matching-configuration setting that determines whether pickup and dropoff are matched by station, address, or a hybrid model.
Matching. Matching is the ioki Platform process that decides whether a ride request can be served and which vehicle planning should serve it.
No-show fee adapter. A no-show fee adapter is the fare calculation adapter that determines whether and how much a user is charged after failing to appear for pickup.
Operator booking. Operator booking is the product feature that lets administrators create rides for users in Control Center.
Passenger option. A passenger option is a per-passenger booking attribute such as a wheelchair or walker that can consume configured vehicle resources during matching.
Passenger type. A passenger type is a per-passenger booking category such as adult, child, or infant that can affect pricing and vehicle resource consumption.
Personal discount. A personal discount is a user-specific price reduction that is applied during booking after the booking fare is calculated.
Place. A place is a geographical point within a product where vehicle shifts can start or end and where pauses can be pre-planned.
Product settings. Product settings are the management and tenant settings that configure how a product operates.
Product. A product is a provider-specific service definition that contains the operational configuration for a service.
Public transport alternative. A public transport alternative is a public transport option that ioki Platform can calculate for a ride request instead of or alongside DRT.
Public transport fallback. Public transport fallback is a product setting that defines a deep link template to a public transport website when no vehicle is available.
Quick booking. Quick booking is the product feature that pre-fills a future booking from an existing ride for one day later, one week later, or a custom date and time.
Rematching attempt. A rematching attempt is the background record created when ioki Platform bulk-rematches rides from a vehicle planning.
Repositioning task. A repositioning task is a manual or automatically spawned task that moves a vehicle to a better waiting location within a vehicle planning.
Ride inquiry. A ride inquiry is a lightweight availability and estimation check that evaluates serviceability before a booking is created.
Ride option. A ride option is a booking option such as booking for others or extra storage that can be configured per product and can consume vehicle resources during matching.
Ride. A ride is the transport record created when a user requests transport, whether it is later accepted, completed, or canceled.
Station. A station is a real or virtual stop within a product that can be used for station-based matching and lines.
Tariff code. A tariff code is a label assigned to a station that a fare calculation adapter can read for a ride’s pickup and dropoff to determine the price. A station can have more than one, and some fare adapters require every station to have at least one.
Task list default properties. Task list default properties are product tenant settings that prefill new vehicle plannings with default places, service times, and matching configuration.
Task list. A task list is the model name in ioki Platform for a vehicle planning and contains the ordered tasks for one vehicle.
Task. A task is an individual operational item within a vehicle planning, such as shift beginning, pickup, dropoff, pause, or repositioning.
User. A user is a passenger account of a provider, including people created in ioki Passenger App, Control Center, or supported integrations.
Vehicle occupation. A vehicle occupation is the assignment that connects a vehicle to a driver.
Vehicle planning. A vehicle planning is the plan of tasks for a single vehicle and is synonymous with task list in ioki Platform.
Vehicle. A vehicle is the transport asset within a product that carries users and is assigned to vehicle plannings.
Zone. A zone is a defined part of a product area that is used for pricing zones and blacklisted travel combinations.

Providers

Booking transaction. A booking transaction is a debit- or credit-type financial transaction linked to a purchasable item such as a booking, tip, or voucher.
Client-app configuration. Client-app configuration is the provider-level support and help information shown in ioki Passenger App that products can override with product-specific values.
Payment service provider (PSP). A payment service provider, or PSP, is the external payment company that processes digital payments between passengers and the provider.
Payment transaction. A payment transaction is a payment- or refund-type financial transaction that records how money was charged or refunded for a user.
Promo code. A promo code is a provider feature that lets administrators grant users a personal discount or service credits under configurable validity and usage rules.
Provider settings. Provider settings are the management and tenant settings that configure provider-wide behavior and branding.
Provider. A provider is the company that offers one or more products in ioki Platform.
Receipt. A receipt is the generated payment or refund document that can be emailed to users when receipt creation and the relevant user-segment email settings are enabled.
Ride payment recovery. A ride payment recovery is a single payment attempt that bundles multiple rides with failed payment for one user into one recovery amount.
Service credits. Service credits are provider-bound internal credit that users can purchase or receive and then spend on rides and personal discounts.
User segment. A user segment is a provider-level grouping assigned at registration that controls default email and notification settings and can restrict client access to users.

Role-based access control

Administrator. An administrator is a Control Center account that can be assigned access to providers or products and receives permissions through roles.
Permission. A permission is an RBAC authorization that is assigned to roles rather than directly to administrators.
Role-based access control (RBAC). Role-based access control is the permissions model that grants Control Center access through roles assigned to administrators.
Role. A role is a collection of permissions that can be assigned to administrators.
Super Admin. A Super Admin is a global administrator with unrestricted access across the platform.

Transport concepts

This section defines general public-transport and demand-responsive-transport concepts as shared vocabulary. Some describe the wider industry and are not features of ioki Platform.

Accessibility. How easily riders can reach transit stops and move through the transit system, including riders with disabilities or other mobility needs. It is a core measure of an equitable, high-quality transport service.
Active transportation. Human-powered travel such as walking and cycling. Also called active travel.
ALT (Anruflinientaxi). A demand-responsive service form in German public transport that runs along a fixed line and timetable but only when a trip is booked, serving the line’s stops at the normal line fare. A taxi or minibus replaces the scheduled bus on demand. It is the line-based counterpart to the AST and works like a virtual line.
AST (Anrufsammeltaxi). A demand-responsive service form in German public transport that runs to a schedule but only when booked, carrying passengers from designated stops to any destination in a defined service area, usually for a surcharge. It gives area-wide, door-to-door coverage where a fixed bus line is not viable.
Campus shuttle. A shared transport service for a university’s students, staff, and faculty that circulates around the campus and nearby areas.
Commingling. The practice of carrying more than one service type in the same vehicle at the same time. The common case is a commingled fixed-route and paratransit service, where general fixed-route passengers and paratransit passengers share one vehicle. Commingling mixes service types; pooling shares one service type across several bookings.
Connected and autonomous vehicle (AV). A self-driving vehicle that can navigate safely with little or no human input.
Corner-to-corner. A shared on-demand model where the vehicle serves nearby points rather than a rider’s exact door, so riders walk a short distance to a virtual stop. It is more efficient than door-to-door and is a form of stop-to-stop service.
Corporate shuttle. A dedicated shared-ride service for a company’s employees, carrying them to and from the workplace and around corporate campuses. It is closely related to a campus shuttle.
Curb-to-curb. An on-demand model where the vehicle serves the rider’s exact origin and destination, but the rider makes their own way between the vehicle and the door.
Deadhead. Vehicle movement without passengers, such as driving to the first pickup or back to the depot. In ioki this is handled through repositioning.
Demand-responsive transport (DRT). A transport model in which rides are requested as needed instead of following fixed routes or timetables.
Dial-a-ride. An early form of demand-responsive transport, usually booked by phone in advance; a legacy term for DRT.
Dispatching. The operational process of managing rides, vehicles, and service changes while a service is running.
Door-to-door. An on-demand model where the vehicle serves the rider’s own origin and destination. In its highest-touch form the driver also helps the rider between the vehicle and the door; the lighter form, where the rider makes their own way, is curb-to-curb.
Dynamic routing. Routing that an algorithm recalculates in real time as demand, traffic, and road conditions change.
Feeder. A feeder is a demand-responsive leg that carries passengers to or from a public transport stop for the first or last mile of an intermodal journey.
First and last mile. The first or last part of a journey between a passenger’s origin or destination and a public transport stop, often served by a demand-responsive leg.
Fixed route. A service that follows a set route and timetable, with vehicles stopping at predetermined stops regardless of demand.
Fleet. The complete set of vehicles that a transport service operates.
Flex route. A hybrid of fixed-route transit and paratransit that runs a general or partly fixed route but can deviate from it, adjusting its stops, timing, or path, including leaving the route within a limited area to serve a booked request before returning, in response to booked demand. Also called route deviation, deviated route, deviated fixed route, or flexible route. It is often used to stretch limited resources in low-density or rural areas.
Headway. The scheduled time between vehicle arrivals at a single transit stop, and thus the maximum time riders must wait. It is most commonly used for fixed routes. Also called maximum wait time.
Intermodal. A journey that combines two or more modes of transport in a single trip and requires the traveler to transfer between vehicles, such as a demand-responsive leg feeding into a train.
Micromobility. Small, lightweight vehicles for short trips, such as bicycles and e-scooters.
Microtransit. A technology-enabled shared transport model that uses dynamically generated routing and pooling to serve variable, on-demand travel demand. It is a form of demand-responsive transport.
Mobility as a Service (MaaS). Mobility as a Service, or MaaS, is a mobility model in which a third-party app combines booking, ticketing, or payment across one or more transport services, including integrations with ioki Platform.
Multi-leg. A single trip plan made up of several legs across different modes or providers. See intermodal.
Multimodal. Describes a service or platform that offers several modes of transport, whether or not a single journey combines them. Unlike intermodal, it does not require a transfer within one trip.
Off-peak. Times of day when demand for public transport is relatively low, outside the busy commuting peaks. Demand-responsive transport is often used to cover off-peak periods where a fixed line would run largely empty.
On-demand. Describes transport that operates only when a passenger requests it, rather than on a fixed schedule. See demand-responsive transport.
Paratransit. A flexible, often door-to-door transport service for people with disabilities or reduced mobility who are unable to use fixed-route public transport.
Pooling. The practice of serving multiple individually booked rides or passengers in the same vehicle during overlapping segments of a journey.
Pre-scheduled booking. A ride booked for a set time in the future, rather than requested for immediate travel. Also called prebooking.
Stop-to-stop. An on-demand model where riders board and alight only at designated stops, physical or virtual, with the order of stops set by demand. Corner-to-corner is the variant where riders walk to a nearby virtual stop.
Transit desert. An area with little or no access to public transport, where residents struggle to reach jobs, services, and other destinations.
Virtual line. A demand-responsive service presented as a line, where vehicles serve a corridor of virtual stops on request instead of running a physical fixed route.
Virtual stop. A pickup or drop-off point with no physical infrastructure, such as a street corner, chosen by the routing system and shown only in the app.
Wheelchair-accessible vehicle (WAV). A vehicle equipped to safely board and secure a passenger who uses a wheelchair.
White labelling. Delivering a product that a partner rebrands as its own; ioki’s passenger app is delivered this way.

User deletion

User deletion. User deletion / anonymization is the privacy process that deletes or anonymizes a user’s personal data while retaining required operational and financial records.