Detailed view of a vehicle planning

Permissions: read_task_lists to open the view, accept_tasks, reject_tasks, cancel_tasks, complete_tasks to manually act on tasks

Open the detailed view of a vehicle planning by selecting Show in the dropdown menu of the relevant vehicle planning or by selecting the vehicle name in the vehicle planning index. At the top of this view, Control Center shows the label for the vehicle planning state.

This view also makes it clear that a vehicle planning is effectively a list of tasks. It’s organized into the following tabs.

1. Tasks
2. Rides
3. Journey overview
4. Inspect
5. Analysis information

Tasks

The Active Tasks tab shows all tasks in the current vehicle planning that are not yet completed or cancelled.

The Negotiating Tasks tab lists all tasks that are not yet accepted, completed, or canceled, but are still pending, that is, reserved. For more information, see the possible states of a task.

To see all tasks in the vehicle planning, open the All Tasks tab.

All three tables use the same structure and show the following task information:

• ID
• State
• Type
• Ride. If there is a corresponding ride, it’s shown here.
• Location
• Time
• Accepted At
• Completed At
• Reported Completed At
• Cancelled At
• Reported Cancelled At
• Updated At

Using the dropdown menu, you can also manually accept, reject, cancel, or complete the corresponding tasks.

Rides

This view also includes three tabs for rides in the current vehicle planning. As with the tasks, the rides are split into Active Rides, Negotiating Rides, and all Rides. These tabs show the following ride information:

• ID
• User
• State
• Origin
• Origin time
• Delay at origin
• Destination
• Destination time
• Delay at destination
• Vehicle, Driver, and Operator (shown together in one column)
• Show PT Ticket reminder: only shown if the product requires a public transport ticket

Journey overview

The Journey Overview tab shows a technical overview of the journey.

Inspect

The Inspect tab collects technical details about the vehicle planning. It shows:

• An overview of the vehicle planning, including its custom tags when the custom tags for task lists feature is active
• The lead time settings, when the lead time feature is active
• The vehicle planning’s logs
• Repositioning logs, when the vehicle repositioning feature is active
• A technical database overview of the vehicle planning and of the assigned vehicle

Analysis information

Roles: Super Admin

The Analysis Information tab is a diagnostic view of the analysis that the platform generates for a vehicle planning. When a vehicle planning is completed, its planned and actual figures are calculated once and stored, so that they remain available for reporting even after the live data is cleaned up. This tab lets you inspect that stored analysis for a single vehicle planning.

If the vehicle planning hasn’t been analyzed yet, the tab shows Analyzed: not yet. Otherwise, it shows the time at which the analysis was calculated.

The same figures shown here feed the operational reports Completed vehicle legs and Completed vehicle plannings. Use this tab to inspect the raw values behind those reports for one vehicle planning, or to investigate why a planning’s reported distances or durations look unexpected.

This is a read-only inspection view, intended for troubleshooting the analysis data of an individual vehicle planning rather than for day-to-day operations.

Analysis overview

The overview lists the metrics calculated for the whole vehicle planning, each in a planned and an actual variant:

• Shift, service, and pause durations
• Empty, occupied, ride, and passenger distances and durations
• Number of served rides and served passengers

For how the planned and actual variants are defined, see Completed vehicle plannings.

Leg breakdown

The analysis splits the vehicle planning into legs. A leg is the segment between two consecutive tasks. Each leg has its own sub-tab, which shows:

• The start task and end task of the leg, and their task waypoint types (for example pickup or dropoff)
• The number of rides and passengers on the vehicle during the leg
• Diagnostic fields used to judge data quality (described below)

Precision models

For each leg, the tab compares the distance and duration produced by several precision models, together with the routing or map-matching service that was used and any error it returned:

Model	Description
estimated	Straight-line fallback, used when routing is unavailable.
routed	Shortest route between the two tasks, from the routing service.
recorded	Path derived from the vehicle’s recorded positions (GPS).
recorded simplified	The recorded path thinned down before map matching. Shown here for diagnostics only; it isn’t a reporting precision level.
snapped	Recorded positions matched onto the road network.

For the definitions of estimated, routed, recorded, and snapped and how they rank, see the precision level section of Completed vehicle legs.

The table also shows the number of points in each track, so you can see, for example, whether enough vehicle positions were recorded for the recorded and snapped models to be meaningful.

Planned versus actual

Each leg also shows a planned and an actual distance and duration, derived from the models above:

• Planned uses the routed value, falling back to estimated when routing wasn’t available.
• Actual uses the snapped value when it’s trustworthy, falling back to recorded, and finally to the planned value.

Whether the snapped value is trustworthy is decided by the snapped-to-recorded distance ratio, also shown on the leg. A snapped track is only accepted when its length stays close to the recorded track; if the two differ too much, the snap is discarded and the recorded value is used instead. This ratio is the main signal for spotting map-matching problems on a leg.

Geo tracks

For each precision model, the leg exposes its geographic track. Each track has a View on geojson.io link that opens the track in an external map viewer, so you can inspect it visually—for example, to spot gaps in the recorded GPS data or a snapped route that was matched onto the wrong roads.

What you can determine

From this tab you can determine:

• Whether a vehicle planning has been analyzed, and when
• How the planned distance and duration compare to what was actually driven
• Whether routing and map matching succeeded, and which services were used
• Whether enough trustworthy position data was recorded to compute the actual figures
• The ride and passenger load on each leg

This makes the tab a useful starting point for troubleshooting figures that later appear in the operational reports.