Plan/Fact

The Plan / Fact section is designed to work with reports that show the accuracy of planning and information about the actual planning indicators.

In this section, you can prepare and download reports and generate graphs.

Report in Excel

For more information on working with reports, see Plan / Fact reports.

Planned values are included in the report from the saved route plan, while actual values come from route data and Track & Trace events of the analytical export. The word "actual" doesn't mean that the order was delivered: the route composition, point visit, and delivery status reflect different properties.

The route date is the date that the route refers to. In Excel, arrival and departure times and time window boundaries are displayed in the time zone of the route's depot. Durations are given in minutes, distances in kilometers. For example, the report displays 90 seconds as 1.5 minutes and 1250 meters as 1.25 km.

An empty cell and zero mean different things. For the "arrival–departure" and "route to point" intervals, the absence of the required time can give 0 minutes. Therefore, zero time doesn't always mean instant completion.

Percentages in the report are calculated as the ratio of a part to the whole. For example, Orders delivered, % is the ratio of the number of delivered orders to the total number of planned orders. If the whole is zero, the percentage isn't calculated and the cell remains empty. It means not "0%" but the absence of a possibility to calculate. For example, if no orders were planned for a day, the share of delivered orders isn't calculated.

The report file consists of the Days, Days-Depots, Routes, and Orders sheets.

On the Days sheet, indicators are grouped by date and company; on the Days-Depots sheet, by date and route depot. Durations, distances, and counters are summed up across the routes of the corresponding row. The number of couriers is counted by unique identifiers. Percentages are recalculated based on the total values rather than output as the average of the percentages of individual routes.

Example of percentages. The plan had 10 orders, the current route has 12. The courier delivered 6 orders in full, 1 partially, canceled 1, rescheduled 1, and 3 orders remained in the Approved status. Delivered: 7 orders, 7 / 12 = 58.33%. Processed: 9 orders, 9 / 12 = 75%. A route is considered active if the statuses of its orders changed (see the Number of active routes field).

Days

A comparison of planned and actual indicators for each day of the selected period.

For example, Planned total mileage, km and Actual total mileage, km.

Description of fields

Field name	Explanation
Date	The date that the routes are planned for
Company ID	The unique ID of the company that the data is collected for
Number of couriers	The number of couriers that performed the routes combined into a report row. If one courier performed several routes within one row, they're counted once
Number of routes	The number of routes included in the corresponding report slice
Number of active routes (where order status changed)	The number of routes with at least one order in the Delivered, Partially delivered, Canceled, or Rescheduled status. The counter uses the order status at the time the data is prepared, not the number of status changes in the history. For more information, see Order statuses
Number of active routes, %	Number of active routes / Number of routes × 100%
Number of routes with GPS signal (online)	The number of routes for which Track & Trace registered the tracking start event. The indicator doesn't mean that the courier was continuously online or is online now
Number of routes with GPS signal (online), %	Number of routes with GPS signal (online) / Number of routes × 100%
Number of routes with no GPS signal (offline)	The difference between the total number of routes and the number of routes with GPS signal
Number of routes with no GPS signal (offline), %	Number of routes with no GPS signal (offline) / Number of routes × 100%
Orders processed	The number of orders in the Delivered, Partially delivered, Canceled, and Rescheduled statuses. Each order is counted once
Orders processed, %	Orders processed / Actual number of orders × 100%. The percentage is calculated from the actual route composition, not from the number of orders in the original plan
Orders delivered	The number of orders in the Delivered and Partially delivered statuses. A partially delivered order is counted as one order, not as a share by weight, volume, or order items
Orders delivered, %	Orders delivered / Actual number of orders × 100%
Planned total mileage, km	The total mileage on the routes planned for the day for all couriers
Actual total mileage, km	The actual mileage on the routes for the day for all couriers. For more information, see Route tracking
Actual mileage before route completion, km	The total actual mileage on the routes for the day, calculated before the routes were completed, for all couriers
Planned total transit time, min	The total transit time on the routes planned for the day for all couriers
Actual total transit time, min	The actual transit time for the day for all couriers. For more information, see Route tracking
Planned total handling time, min	The total planned handling time at depots and at order locations
Actual total handling time on orders, min	The total time that couriers spent handling orders (handing over the order, exchange of documents, and parking) at order locations
Actual total handling time at depots, min	The total time that couriers spent at depots loading, reloading, and unloading orders and exchanging documents
Planned total time, min	The total time to complete all routes scheduled for the day. Includes the planned transit time and planned handling time
Actual total time, min	The total time actually spent on completing all routes for the day. Includes the transit time and handling time
Planned number of time window violations	The total number of time window violations in all routes planned for the day
Actual number of time window violations	The total number of time window violations committed during the day while completing routes
Planned number of locations	The number of locations on the routes planned for the day. Includes orders and depots
Actual number of locations	The number of actually visited locations on the routes. Includes orders and depots. For more information, see Detect route point visits
Planned number of orders	The number of orders planned for the day for all couriers
Actual number of orders	The number of orders in the actual route composition for the day
Number of orders with status comments	The number of orders where couriers left comments to the statuses
Number of downtimes during orders	The number of long unplanned downtime situations at order locations. For more information, see Courier downtime.
Total downtime during orders, min	The total amount of long unplanned downtime at order locations
Number of downtimes at depots	The number of long unplanned downtime situations at depots
Total downtime at depots, min	The total amount of long unplanned downtime at depots
Number of downtimes during route	The number of long unplanned stops between route locations
Total downtime during route, min	The total duration of long unplanned stops between route points
Number of signal drops	The number of times when couriers didn't have an internet connection
Total time without network connection, min	The total time when couriers didn't have an internet connection
Number of routes with a logistics coordinator sequence violation	The number of routes for which Track & Trace set the logistics coordinator sequence violation flag. The report uses the ready-made route flag
Courier violated the logistics coordinator sequence	The value of the logistics coordinator sequence violation flag that Track & Trace saved for the route
Plan was changed	The result of comparing the saved plan with the composition and sequence of route points in Track & Trace. A mismatch in the composition or order of orders is considered a violation; there are exceptions for depots and garages in the check. This flag doesn't record deviations in time or mileage
Number of routes with a plan violation	The number of routes for which the plan compliance check found a violation. The indicator is calculated independently of the logistics coordinator sequence violation: a route can violate the plan without violating the logistics coordinator sequence, and vice versa

Days-Depots

A separate comparison of indicators for each depot specified in the routes for the selected period. The indicators for comparison are the same as on the Days sheet, but are linked to a specific depot.

Description of fields

The indicators on the Days-Depots sheet are the same as on the Days sheet, but additionally contain depot fields:

Field name	Explanation
Depot ID	The unique ID of the depot
Depot number	An additional depot ID (the depot.ref field)
Depot name	The name of the depot (the depot.title field)
Depot address	The address of the depot (the depot.address field)

Routes

A comparison of run indicators.

For example, Planned finish time and Actual finish time.

Description of fields

Field name	Explanation
Company ID	The unique ID of the company that the data is collected for
Route ID	The unique run ID
Route number	The run number displayed on the dashboard
Route date	The date that the run is planned for
Route IMEI	The IMEI number of the GPS tracker. For more information, see Setting up data transfer from devices
Route in Routing Workspace	The link to the route on the map in the routing workspace
Courier ID	The unique courier ID
Courier's number	The courier's number (the vehicle.id field)
Courier's name	The courier's name, vehicle name, or number (the vehicle.ref field)
Courier's phone number	The courier's phone number (the vehicle.phone field)
Depot ID	The unique ID of the depot
Depot number	An additional depot ID (the depot.ref field)
Depot name	The name of the depot (the depot.title field)
Depot address	The address of the depot (the depot.address field)
Depot timezone	The name of the depot's timezone
Geolocations on the route	TRUE if at least one courier geolocation was recorded during the run. FALSE if no geolocation was recorded
Courier violated the logistics coordinator sequence	TRUE if the courier violated the planned order sequence during the run. FALSE if there were no violations
Plan was changed	TRUE if deviations from the planned indicators were recorded during the run (the courier_violated_route flag). FALSE if there were no deviations
Planned number of locations	The number of all points in the saved plan: orders, depots, and garages. This is the number of point records, not unique addresses
Actual number of locations	The number of points in the actual Track & Trace route composition, including orders, depots, and garages. The verified export includes all route points, not only visited ones
Planned number of orders	The number of "Order" type points in the saved plan. Depots and garages aren't counted
Actual number of orders	The number of "Order" type points in the actual Track & Trace route composition regardless of the delivery status. For the number of delivered orders, use the separate "Orders delivered" field
Planned total mileage, km	The sum of planned distances to all route points from the saved plan, divided by 1000
Actual total mileage, km	The total route mileage according to Track & Trace data, divided by 1000. This is a separate route indicator. It may not match the sum of distances on the "Orders" sheet, in particular due to the section after the last counted point
Actual mileage before route completion, km	The mileage according to Track & Trace data, calculated before the route was completed, divided by 1000. It differs from the total actual mileage if Track & Trace recorded additional courier geolocations after the route was completed
Planned total transit time, min	The sum of intervals from the planned departure of a point to the arrival at the next one. Transitions within a group of multi-orders aren't counted as separate movement
Actual total transit time, min	The sum of actual transit intervals to points. If tracking isn't complete, Track & Trace uses the courier's last position and adds the interval from the last point time to this position. Downtime en route isn't subtracted from it
Planned total handling time, min	The sum of individual and combined handling of all points. For each group of multi-orders, the maximum combined handling value is counted once
Actual total handling time on orders, min	The total duration of intervals from arrival to departure at order points. Overlapping intervals aren't counted twice. Points without arrival or departure aren't included in the sum
Actual total handling time at depots, min	The total duration of arrival–departure intervals at depot points. Overlapping intervals aren't counted twice. The indicator is calculated separately from orders
Planned start time	The planned arrival at the first route point
Planned finish time	The planned departure from the last point, or, if it isn't set, the planned arrival at it
Planned total time, min	The difference between the planned finish and start. If one boundary is missing or the difference is negative, it's 0. This is a time interval. Don't replace it with the sum of transit and handling time
Actual start time	The earliest of the calculated starts of the route to points: the arrival time at a point minus its actual transit time
Actual finish time	The latest recorded arrival or departure among the points. If tracking isn't complete and Track & Trace loaded the courier's last position, the finish is determined by its time. This isn't necessarily the time when the last order was moved to the Delivered status
Actual total time, min	The interval from the actual start to the actual finish. If one boundary is missing, it's 0
Planned number of time window violations	The number of planned points whose arrival doesn't fall within any of the saved time windows. Arrival exactly at the window boundary isn't considered a violation
Actual number of time window violations	The number of points whose actual arrival violates the window. The verified export counts points of all types with this flag
Orders processed; Orders processed, %	The number of orders where the status has changed; their share in the total number of planned orders
Orders delivered; Orders delivered, %	The number of orders in the Delivered and Partially delivered statuses; their share in the total number of planned orders
Number of downtimes during orders	The number of completed downtime events that Track & Trace attributed to order points. This is the number of events, not orders or routes with downtime. For more information, see Courier downtime
Total downtime during orders, min	The sum of durations of the same completed downtime events, divided by 60
Number of downtimes at depots	The number of completed downtime events that Track & Trace attributed to depot points. This is the number of events, not depots or routes with downtime
Total downtime at depots, min	The sum of durations of the same completed downtime events, divided by 60
Number of downtimes during route	The number of completed downtime events that Track & Trace attributed to the route between points. This is the number of events, not sections or routes with downtime
Total downtime during route, min	The sum of durations of the same completed downtime events, divided by 60
Number of signal drops	The number of completed connection loss events registered by Track & Trace for the route. This isn't an arbitrary number of gaps between GPS points
Total time without network connection, min	The sum of durations of the registered completed connection loss events, divided by 60
Number of orders with status comments	The number of orders with at least one status history record containing a comment field. Each order is counted once regardless of the number of such records

Track & Trace creates downtime events taking into account the company settings. The report sums up already prepared events. In the handling time mode, the expected end of order handling includes individual and combined handling. In the delivery time mode, the start of the window is also taken into account. In the window end mode, the end of the order window and the visit time are taken into account. Therefore, the fact that a courier stood for 30 minutes doesn't mean that a downtime event will appear in the report.

Multi-order example. Two orders have individual handling of 3 and 4 minutes and combined handling of 5 and 7 minutes. In the total planned handling, the group gives 3 + 4 + max(5, 7) = 14 minutes.

Handling overlap example. Two orders were handled in the intervals 11:00–11:10 and 11:05–11:15. The order rows will each show 10 minutes, while the route total will be 15 minutes, since the overlap isn't counted twice.

Orders

A comparison of indicators for each individual order.

For example, Planned distance to the point, km and Actual distance to the point, km.

The report matches the planned and actual parts of a row by position in the sequence, aligning the first order. Therefore, one row doesn't necessarily describe the same order on the left and right. When the sequence changes, one order can end up in different rows of the planned and actual parts. To compare a specific order, additionally check its number.

Description of fields

Field name	Explanation
Company ID	The unique ID of the company that the data is collected for
Route ID	The unique run ID
Route number	The run number displayed on the dashboard
Route date	The date that the run is planned for
Courier ID	The unique courier ID
Courier's number	The courier's number (the vehicle.id field)
Courier's name	The courier's name, vehicle name, or number (the vehicle.ref field)
Depot ID	The unique ID of the depot
Depot number	An additional depot ID (the depot.ref field)
Depot name	The name of the depot (the depot.title field)
Planned location type; Actual location type	Possible values: Order or Depot (the actual location type isn't specified for depots)
Planned order sequential number	The point's position in the saved route plan. Numbering starts with 0 and counts points of all types: orders, depots, and garages
Actual order sequential number	The point's position in the sequence built by the time of the registered arrival. Numbering starts with 0. If the time is the same, the order of points in the route is used. Points without arrival come after points with arrival, in route order. The initial garage without a visit remains at the beginning. In the verified export, all point types are included in the numbering
Actual order sequential number approved by the logistics coordinator	The saved position of the point in the Track & Trace route. Allows comparing the order in Track & Trace with the original plan and with the sequence of registered arrivals
Planned number	Consists of the location.id field and the planned date of the order visit, or of the depot.id field for a depot
Actual number	Consists of the location.ref field and the actual date of the order visit. Not specified for depots
Actual status	The point status from Track & Trace at the time the data is prepared. The delivery status should be analyzed separately from arrival and departure events. For more information, see Order statuses
Planned address; Planned latitude; Planned longitude	The address and coordinates of the point from the saved plan
Actual address; Actual latitude; Actual longitude	The address and coordinates of the point itself in Track & Trace. These aren't the courier's coordinates when handing over the order
Courier-specified latitude; Courier-specified longitude	The refined coordinates from the corresponding order fields. They're output separately from the main point coordinates
Detection radius, m	The radius selected for the point when preparing the report. For an order, the explicitly set order radius is used first, then the route depot radius, then the company radius. For a depot point, the start radius of its depot is used; for a garage, 100 m. This is the selected setting, not the measured GPS error and not necessarily the historical value at the time of the visit. For more information, see Detect route point visits
Client's planned name; Client's actual name	The name from the saved plan and the current name in the order card, respectively
Client's actual number	The client number from the Track & Trace order card at the time the data is prepared
Planned time of arrival; Planned time of departure	The arrival and departure time saved in the plan for this point
Actual time of arrival; Actual time of departure	The time from the last registered arrival and departure events of the point. These are the times of event registration, not the time of the order status change. If there's no event, the corresponding time is absent. The technical zero time of manual visit registration isn't output as a real date
Order completion time	The time when the order was moved to the final status from the Track & Trace status history. This is the status change time, not the arrival or departure registration time
Courier latitude at order completion; Courier longitude at order completion	The courier's coordinates at the moment of order completion
Actual order visit time	The time of the registered visit to the order point
Courier latitude at automatic order visit detection; Courier longitude at automatic order visit detection	The courier's coordinates at the moment of automatic detection of the order point visit
Planned handling time, min	The individual handling time of the point saved in the plan. Combined handling for several orders is output separately in the combined handling field
Planned combined handling time at the destination, min	The combined handling time saved in the plan, for example, for parking or document work. In the total route indicator, the maximum combined time of a multi-order group is counted once
Actual handling time, min	The interval from the registered arrival to the registered departure: (departure − arrival) / 60. This is the entire recorded interval of staying at the point; downtime isn't subtracted from it separately. If one boundary is missing or the departure is earlier than the arrival, the value is 0
Actual downtime at location, min	The sum of durations of completed downtime events that Track & Trace attributed to this visited point. This is an independent indicator, not the difference between actual and planned handling
Planned transit time to location, min	The interval from the planned departure of the previous point to the planned arrival at this point. For the first point or if one of the boundaries is missing, it's 0. A negative interval is also replaced with zero
Actual transit time to location, min	The interval from the previous available departure to the arrival at this point in the actual sequence. For the start of the route, the start event time may be included in the calculation. If there's no source time or arrival, the value is 0. Downtime en route isn't subtracted from the interval separately
Actual downtime on the way to location, min	The sum of durations of completed downtime events that Track & Trace attributed to the route before this visited point
Planned distance to the location, km	The distance of the section to the point saved in the plan, divided by 1000
Actual distance to the location, km	The distance of the section that Track & Trace calculated from the courier's coordinates, divided by 1000. The calculation is tied to the registered point visits and uses coordinate filtering. If the section distance isn't defined, 0 is passed to the export. The presence of a track by itself doesn't guarantee a non-zero distance for each point
Planned order volume, m³	The volume saved in the plan. When importing the planning result, the explicitly set shipment_size.volume_cbm is used; if it's absent, the product of depth, height, and width from shipment_size.volume. If the volume and dimensions are absent, the value isn't filled in
Planned order weight, kg; Planned order size	The weight and number of units saved in the plan
Actual order volume, m³; Actual order weight, kg; Actual order size	The current volume, weight, and number of units in the Track & Trace order card at the time the data is prepared. The report doesn't measure them by track and doesn't calculate them automatically by the partial delivery status
Planned time window start date; Planned time window start time; Planned time window end date; Planned time window end time	The window boundaries from the saved plan. If several windows are saved for a point, the first one is used
Planned delivery time window violation	TRUE if the planned arrival is earlier than the start or later than the end of the specified planned window, FALSE if it falls within the window, including the boundaries. If there's no arrival or window, the check returns FALSE. A violation is allowed only for a soft time window
Actual time window start date; Actual time window start time; Actual time window end date; Actual time window end time	The window boundaries of the point in Track & Trace that are used to check the actual arrival. For an order, the first saved window is used. This is the delivery window, not the interval of the courier's actual stay. For a depot, the window is built by its schedule, time zone, and arrival date; if there's no arrival, by the route date
Actual delivery time window violation	TRUE if the registered actual arrival is earlier than the start or later than the end of the used actual window, FALSE if it falls within the window, including the boundaries. If there's no arrival or window, the check returns FALSE, which by itself doesn't confirm timely delivery
Actual comment	The comment from the order card
Status comments	The comments from the order status history. In the Excel export, a separate column is provided for each status: Not approved, Approved, Delivered, Partially delivered, Canceled, Couldn't reach by phone. For each status, the first found comment of this status is output

Example. Window 10:00–12:00: arrival exactly at 12:00 doesn't violate the window; at 12:01 it does. Handling or a coefficient isn't added to the arrival. The planned and actual values are checked independently.

Handling example. Arrival at 11:00, departure at 11:20. The actual handling is 20 minutes, even if the planned one is 5 minutes. A separate downtime value can't be added to these 20 minutes as additional time: it may already be included in the stay interval.

Charts

In this section, you can plot graphs by the number of routes or orders completed for one or more depots. You can also compare charts for different periods with each other and download a report on the selected depot.

For more information on working with graphs, see Plan / Fact graphs.