Completed vehicle legs
This report contains details and metrics on distance driven and passenger transport performance for each vehicle leg of all completed vehicle plannings.
- The period type is monthly.
- The default query timeframe is one day.
- The row access mode is
product and operator based.
Permissions:
access_reports
A vehicle planning must be fully completed to be considered. Past tasks that have not been marked as completed by the driver can be retroactively marked as completed in ioki Operator under vehicle planning details and ride details. Be sure to set a realistic past timestamp to ensure the most accurate calculation of distances and durations.
The metrics are provided for each individual leg of the vehicle planning. Two consecutive tasks in a vehicle planning form a leg.
All completed or considered completed tasks are taken into account. Tasks considered as completed include no-shows and other cancellations at fault of the passenger where the vehicle had already reached the pickup location. Operationally mandated legs are also factored in, such as repositioning, as well as breaks and shift ends.
Driver/vehicle changes: A leg is assigned to the vehicle, driver, and operator in service at the endpoint of the leg.
The metrics are calculated in two variants: actual and plan.
Actual metrics
The actual metrics are based on the actual time and location at which a task was marked as completed.
The actual distance of a leg is based on all position data recorded between task completion at the start and the end of the leg. Actual distances are used to assess the distance driven, passenger transport performance and the efficiency of a service.
Plan metrics
The plan metrics are based on the planned times and locations of tasks in a vehicle planning.
Plan distances are calculated by default as the shortest route between the tasks of a vehicle planning. The type of routing can be adjusted to your needs. Plan distances are frequently used for billing purposes because they are well-suited to measure the commissioned passenger transport. They are verifiable and independent of traffic conditions.
Location-bound pause and shift end: If you want to operate on plan distances, you should always define a place for pause and shift end tasks in the vehicle planning.
Report columns
| Field name | Definition |
|---|---|
| Task list ID | Identifier of the vehicle planning (task list) the leg belongs to. |
| Task list planned start time | Planned start time of the vehicle planning. |
| Product name | Name of the product the vehicle planning belongs to. |
| Vehicle nickname | Nickname of the vehicle assigned at the endpoint of the leg. |
| Start task waypoint type | Type of the task at the start of the leg (for example pickup, dropoff, start of shift or start of pause). |
| End task waypoint type | Type of the task at the end of the leg (for example pickup, dropoff, end of shift or end of pause). |
| Actual start time | Time at which the task at the start of the leg was marked as completed. |
| Actual end time | Time at which the task at the end of the leg was marked as completed. |
| Rides boarded | Number of individually booked rides on the leg of the journey. |
| Passengers boarded | Number of passengers on the leg of the journey. |
| Actual or plan vehicle-distance [m] | Actual distance traveled or plan distance on the shortest route. |
| Occupied distance [m] | Vehicle-distance on legs with at least one passenger. |
| Empty distance [m] | Vehicle-distance on legs without passengers. |
| Ride-distance [m] | Vehicle-distance x number of rides boarded on each leg of the journey. |
| Passenger-distance [m] | Vehicle-distance x number of passengers boarded on each leg of the journey. |
| Starting point or endpoint time deviation [s] | Time difference between task completion in ioki Vehicle App and the planned task time. If the deviation is positive, the task was completed later than planned. |
| Starting point or endpoint local deviation [m] | Linear distance between the vehicle’s position at task completion and the planned task location. Only calculated if a vehicle position is available near the time of task completion. |
| Precision model | Specifies the model used for calculating distances and durations, indicating how accurate the data is. Planned data uses up to the routed precision level, while actual data uses up to snapped. For further explanation, see section below. |
The occupancy rate, bundling rate, passenger pooling rate and rides pooling rate are not columns of this report. They are reported at the vehicle planning level in /jCGekyy7mN3VkD6m8AnLJ2JQrkN4S6xb/main/docs/reporting/operational-reports/completed-vehicle-plannings/.
Calculation example
The vehicle planning:
- A → B: Actual vehicle-distance = 3 km, empty leg
- B → C: Actual vehicle-distance = 2 km, 2 rides boarded: 1 x 1 passenger and 1 x 2 passengers
results in the following metrics:
- Actual vehicle-distance = 3 km + 2 km = 5 km
- Actual occupied distance = 2 km
- Actual rides-distance = 2 trips x 2 km = 4 km
- Actual passenger-distance = 3 passengers x 2 km = 6 km
- Occupancy rate = actual occupied distance / actual vehicle-distance = 2 km / 5 km = 40%
- Bundling rate = actual passenger-distance / actual vehicle-distance = 6 km / 5 km = 1.2
- Passenger pooling rate = actual passenger-distance / actual occupied distance = 6 km / 2 km = 3.0
- Rides pooling rate = actual ride-distance / actual occupied distance = 4 km / 2 km = 2.0
Precision level
Depending on the data available, one of four models is used to determine the distances with the highest possible accuracy. For actual distances, the following models are applied (in decreasing order of precision):
- snapped – Based on received vehicle positions (typically every 5 seconds), the distance is calculated along the local road network.
- recorded – If alignment with the road network fails, the linear distance between the received vehicle positions is used. As this underestimates the true distance, an empirically determined markup of 3% is applied.
If no vehicle positions are available or if they aren’t accurate enough, the actual distance is determined in the same way as the planned distance:
- routed – The distance on the shortest route between the planned starting point and endpoint.
- estimated – If routing fails, the linear distance between the planned starting point and endpoint is used. An empirically determined markup of 48% is applied.
How can I verify the planned distance?
The routing for this report uses the start time and start location of the vehicle planning and assumes a continuous journey along all relevant tasks of the vehicle planning. The routing is optimized by default for the shortest route. The start date and time are important because the shortest route may change at times, for example, due to altered road layout.
What happens if the driver marks tasks as completed late? Why are planned distances sometimes longer than actual distances?
If the driver does not mark the task as completed on time when picking up or dropping off passengers, a portion of the actual distance between consecutive legs may shift. However, the actual distance for the entire vehicle planning remains the same. If the beginning of the shift is confirmed too early or too late and the vehicle is already in motion, this will lengthen or shorten the actual distance for the entire vehicle planning. The same applies to the end of the shift.