Skip to main content

Arrival Monitor. Key Performance Indicators (KPIs)

I
Written by Inna Szpigun
Updated over a year ago

Standard Key Performance Indicators (KPIs) are effortlessly configured to align with customer's unique parameters. Our KPI set empower end users with valuable insights and actionable data, enabling them to enhance efficiency, reduce costs, and maintain a competitive edge in the logistics industry.

Default Key Performance Indicators set:

  • Workload Tracking (Completed/Planned). Gain insights into the total work planned and executed for your chosen locations and time-frame. This capability empowers yard operators and logistics managers to monitor progress effectively

  • Processing Time. Uncover potential issues and risks that impact overall performance, providing valuable insights for proactive decision-making

  • Dwell Time. Assess whether your location's throughput meets your expectations. Optimize operations to reduce on-premises time, increasing truck availability for your carriers, ultimately solidifying your position as the preferred shipper

  • Delayed Vehicles. Stay informed about any late arrivals, helping all stakeholders to proactively manage deviations from the plan. Make necessary adjustments, such as task swapping or re-booking, to ensure smooth operations

  • Waiting Vehicles. Identify carriers on-site for appointments that have not commenced processing, putting you at risk of incurring demurrage costs. Take action to streamline processes and minimize expenses

KPI calculation:

Workload Tracking (Executed/Planned)

Completed = Sum of all transports/visitors where Activity = Delivery or Pickup and last yard status is populated with the timestamp that is inside or outside the nominal planned time (Planned column). Transport with multiple bookings on the yard counted only one time

Planned = Sum of all transport where Activity = Delivery or Pickup for selected location and time period. Transport with multiple activities on the yard is counted only one time

Total planned number is always the plan value, so it is our baseline of comparison. Received/Unloaded/Loaded etc. is the actual processed in the time period selected, irrespective of the original booked time.

Sample: Selected period 29.09.2022 8am – 8pm.

During that period we plan to process 10 trucks (3 inbound and 7 outbound) . As of now only 2 trucks were processed. So in Arrival Monitor we can see 2/10.

At 7 pm 2 trucks arrived without scheduled appointment (not supported in MVP) and 1 arrived earlier then booked time slot (10pm). Overall we were managed to execute those 3 unplanned trucks + planned 10 trucks by 8 pm. So in UI I can see 13/10.

Processing Time

Sum of all time duration detected as (un)loading activities divided by total number of transport included in dock time calculation. Transport with more then one activity assigned counted only ONE time

Sample: Selected period 29.09.2022 8am – 8pm.

During that period I had 3 trucks that (un)loaded and left the yard

Truck 1. Loading start 8:30 am – Loading end 9:30 am. Loading time = 1h

Truck 2. Loading start 8:00 am – Loading end 11:30 am. Loading time = 3h 30 min

Truck 3. Unloading start 11:00 am – Unloading end 1:30pm. Unloading time = 2 h 30 min

Truck 4. Two activities assigned: Delivery (Unloading activity), Pickup (Loading activity)

Unloading starts 1:30 pm - Unloading ends 2:00 pm. Unloading time 30 min

Loading start 2:15 pm - Loading ends 2:50 pm. Loading time 35 m (0,58h)

Calculation: (1 + 3,5 + 2,5 +0,5 + 0,58)/4 = 2,02, translation hours into minutes = 0,2*60 = 12 min final result 2 h 12 min

Rounding:

Minutes after coma are not displayed, they are rounded to the nearest whole minute:

If its 0,50 or above, round up

0,49 or below, round down

Dwell Time

Sum of all times (duration time between first status within the yard (sample: Registered/Arrived) and final yard status (sample: Departed/Completed etc.) divided by total number of transport with final status (Departed/Completed) for selected period. Transport with more then one activity assigned, counted only ONE time

Sample: Selected period 29.09.2022 8am – 8pm.

During that period I had 4 trucks that (un)load and left the yard.

Truck 1. Arrived 8:30 am – Departed 9:30 am. Turnaround time = 1h

Truck 2. Arrived 8:00 am – Departed 11:30 am. Turnaround time = 3h 30 min

Truck 3. Arrived 11:00 am – Departed 4:30pm. Turnaround time = 5 h 30 min

Truck 4. Arrived 5pm – Departed 5:30 pm. Turnaround time 30 min

Dwell Time = (1 + 3,5 + 5,5 + 0,5)/4 = 2,625;

translation hours into minutes 0,625*60 =37,5 rounding up 38

Final result 2 h 38 min

The dwell time measured & included whether the transport is inside the nominal slot time or not. Ultimately dwell time is measuring average performance, not performance for each slot

Sample: Selected period 29.09.2022 8am – 8pm

Truck arrived at 6am (before selected period) but left the yard at 9am (during selected period). Such truck should be included in Turnaround time calculation

Rounding:

Minutes after coma are not displayed, they are rounded to the nearest whole minute:

If its 0,50 or above, round up

0,49 or below, round down

Waiting Vehicles

Sum of all vehicles where:

First customer status on the yard (Arrived/Registered) = On time. If first status timestamp is in the range of (slot start time - 15 min) and (slot start time + 15 min)

First customer status on the yard = Earlier. If first status timestamp < Slot start time - 15 min.

AND LOADING/UNLOADING is not started yet.

Transport with more then one activity assigned counted only ONE time. Vehicle that arrived/registered LATE are excluded from WAITING KPI calculation

In Arrival Monitor view we have two KPIs that can help our users easily spot deviations in planing and avoid potential demurrage costs. Those KPIs are: 'Waiting trucks' and 'Late trucks'.

'Waiting vehicles' activation:

When user clicks 'Waiting vehicles' KPI tile, data in the table is filtered out and only waiting transports are visible in the table. 'Waiting vehicles' KPI tile is active (tile highlighted in yellow)

'Waiting vehicles' deactivation

When user clicked KPI tile one more time, KPI filter is deactivated and all data in the table is available. 'Waiting vehicle' KPI tile is inactive (no color)

Delayed Vehicles

'Delayed Vehicles' KPI provides the number of late vehicles ('ETA late' or first customer status on the yard detected as late or vehicle did not arrive at the agreed time). Number of late vehicles is calculated for location, date and time selected in page Navigation tool bar. Number of late vehicles is calculated whether the truck is inside the nominal slot time or not. Once Loading/Unloading started, truck is removed from Late trucks KPI.

Delayed vehicles = Sum of all vehicles where:

ETA = Late. Follow ETA late logic

or first customer status on the yard = Late. If first status timestamp (Arrived/Registered etc.) > Slot start time + 15 min

No ETA available and no first yard status timestamp available and current timestamp > slot start time + 15 min.

Transport with more then one activity assigned counted only ONE time

Similar to 'Waiting Vehicles', 'Delayed Vehicles' KPI acts as a quick filter, so user can have a fast overview of possible deviations in planning.

'Delayed vehicles' activation:

When user clicks 'Delayed vehicles' KPI tile, data in the table is filtered out and only delayed transports are visible in the table. 'Delayed vehicles' KPI tile is active (tile highlighted in yellow)

'Delayed vehicles' deactivation

When user clicked KPI tile one more time, KPI filter is deactivated and all data in the table is available. 'Delayed vehicle' KPI tile is inactive (no color)

Did this answer your question?