Logistical architecture in Turnit Ride platform is built up to maximize flexibility, yet make sure the logical structure of the route network would not be compromised. As one line permit may be linked to several different routes (e.g. on working days and weekends the route of one line can be different) or different travel products, logistical information is managed at three levels:
- Line – A line in Turnit Ride means a permit to provide passenger transportation services on certain route or routes. This level is meant for managing general information about the line - line number, line name, the expiry of line permit, refunding rules, etc.
- Line template – This is where route-specific data is managed - bus stops on the route, time of arrival, and departure, pre-assigned inventory, etc. The primary purpose of Line and Line template is to manage default values of data that are needed to generate actual trips.
- Trip – based on line template, actual departures on specified line with a specific date and time are generated. All sales transactions, including passenger-specific data will be assigned to specific trips, so it is easy to react to any trip-related issues, last-minute dispatching and fare change. Each trip (departure) can be individually managed. For example adding a stop on Mondays and Fridays or limiting the number of seats offered for sale in certain segments.
Each departure can be individually managed. For example, adding a stop on Mondays and Fridays or limiting the number of seats offered for sale in certain segments.
Turnit Ride boasts a powerful multi-leg interconnection capability for operators, who either co-operate with partners to provide multi-modal journeys or want to utilize their own route network more efficiently. Multi-leg functionality allows to:
- Search and display multi-leg trips in all sales channels
- Combine up to ten different legs into one multi-leg trip
- Build the logistical chains and HUB-s visually on a map
- Include partnering operators in the same multi-leg route network
- Improve multi-leg algorithm by assigning different restrictive parameters to the search algorithm, including:
- Maximum tickets sold out per leg (to force multi-leg passengers to use lines with less demand)
- Travel duration ratio compared to the fastest possibility to travel
- Max travel duration
- Transfer time
Stops & Zones
To start describing routes on lines, it is necessary first to define stop information. It requires a meticulous and systematic data structure, to make sure all stops are unique yet include enough parameters to meet operators business requirements. In Turnit Ride, it is possible for operators to describe stops by including the following parameters:
- Location (4-level regional administration – country, county, district, address)
- Alternative names (aliases)
- Language-dependent parameters (name & address), which automatically translate the stop name into the language used in front-end channels
- Stop type and corresponding settings
- GPS coordinates
- Prioritization settings (more important stop than others can be shown first, etc)
If the stop is defined also as a terminal, additional settings can be configured:
- Platform numbers
- Minimum turnover or slot time
- Platform fee set-up
- Display management
Stops can be bundled and arranged into zones, resulting in simpler fare structure and administration effort.