LogConsult Academy · F11
Logistics KPIs and Control Tower
The numbers the board asks for and how to build them.
Lessons are recorded in Portuguese with Portuguese subtitles. Every lesson comes with its full text in English.
about US$ 240 · Prices in Brazilian reais (BRL), paid through Mercado Pago (Pix, credit card in up to 12 installments, or boleto). The checkout page is in Portuguese.
Program
5 video modules, 17 min, 5 exercises
- Logistics KPI tree
- OTIF, lead time and service level
- Cost per ton and per order
- Control tower routine
- The weekly report that drives decisions
What you build
KPI dashboard with targets and routine
Free sample: the first 2 minutes of module 1
Lesson text in English · 1
Logistics KPI tree
Logistics KPI tree. Hi, I'm Lia, the virtual presenter of LogConsult Academy. This is the first module of the course Logistics KPIs and Control Tower. Here you will learn to organize logistics KPIs in the form of a tree, linking what happens in the yard and on the road to the result that the board tracks. And you will leave knowing how to choose which numbers deserve a place on your dashboard.
The problem of loose numbers. In the diagnostics we run, it is common to find reports with dozens of numbers, with each department measuring in its own way. Transport tracks freight, the warehouse tracks productivity, and sales complains about delays. When the board asks why cost went up, no one can show which operational number pushed the result up. The KPI tree exists to solve this linkage problem.
How the tree works. The tree starts at the top with a few KPIs, usually total logistics cost and customer service level. Each of them branches into area KPIs, such as transport, warehousing and inventory. And each area KPI branches into day-to-day operational numbers, such as loading time or vehicle fill rate. This way, a variation at the top can be traced back to its origin.
The cost branch. In the cost branch, the top is usually logistics cost compared with company revenue. Below it appear the major expense groups, which are freight, warehousing and the cost of holding inventory. Each group branches into unit KPIs, such as cost per ton transported or cost per order shipped. These unit KPIs are what allow comparing months with different volumes.
The service branch. In the service branch, the top measures whether the customer received what they ordered, on time and in the agreed quantity. Below come the order fulfillment time, from entry to delivery, and the quality KPIs, such as damage, shortages and returns. At the base are numbers such as orders picked per hour and vehicles loaded on schedule, which show where the delay began.
An example. Let's look at an example, always with illustrative numbers. A company's cost per ton rose eight percent in one month. Going down the tree, the team saw that warehousing was stable and that the increase came from freight. In freight, the average vehicle fill rate had dropped. At the base, the reason appeared, because sales had started accepting smaller orders with immediate delivery.
Fewer KPIs, better. The temptation is to measure everything, but a good tree is lean. At the top, two or three KPIs are usually enough. In each area, three to five KPIs are usually sufficient to explain the result. Every KPI needs an owner, a defined data source and a written formula. If no one makes a decision based on a number, it can come off the dashboard with no loss.
Module exercise. Now it's your turn to apply what we covered in this module. List all the KPIs that your logistics area already tracks today. Place each one in the tree, separating top, area and base, in the cost and service branches. Flag those that have no owner, source or written formula, and those that no one uses to make decisions. In the next module, we will detail the lead time and service level KPIs. See you then.
Lessons are presented by Lia, a virtual presenter generated by AI. The content is written and reviewed by LogConsult.