KPI tree builder
Break a plant goal such as on-time delivery down into the KPI that drive it, and those into the KPI one team can change on its own: OEE per line, changeover time, scrap of one part. Each KPI gets a unit, target, actual value, direction and owner.
The tree shows at every level whether a KPI is on target, close to it or off, how many red KPI sit below each node, and where to start: the red KPI whose own drivers are not red.
Worked example: KPI Tree
- 01GoalOTD 95.5 %target 98 %
- 02DriversOEE, FPY, materialsecond level
- 03LinesOEE L2 66 %off target
- 04Startchangeover L2red driver without red children
01Method
A KPI is on target when the actual value meets the target in the right direction (higher or lower is better), close to target when it misses it by no more than the set tolerance (5 % by default, relative to the target), and off target otherwise.
Parents are chosen from the list; removing a KPI moves its children up one level. A KPI whose parent does not exist is shown as a separate tree and listed in the verdict.
02When to use it
Use it for goal deployment from the plant objectives to the team boards, to find which line or driver pulls a plant KPI down, and to prepare the KPI part of a management review.
PDF report in one click
Export the indented KPI tree with actual, target, owner and status as a PDF for the management review or the plant board.
Private: runs in your browser
The tree is kept in your browser only.
How to build a KPI tree
- Start at the top with the goal the customer or the business cares about, such as on-time delivery.
- Ask “what drives it?” and add the second level: OEE, first pass yield, material availability.
- Go down until each KPI belongs to one team or one person, such as the changeover time of line 2.
- Enter target, actual and direction and read the status at every level.
- Start where it is red at the bottom: a red driver whose own children are not red.
Example
On-time delivery is at 95.5 % against 98 %. Below it, OEE of line 2 is 66 % against 80 %, driven by a changeover time of 48 minutes against 30, while line 1 is on target. Scrap of cover 4715 is twice its target, but first pass yield overall is still green. The tree points to two places to start: the changeover on line 2, with the SMED analysis, and the cover scrap, with a Pareto chart.
Show the lowest KPI on the team boards. All tools: shop floor management.
Frequently asked questions
›What is a KPI tree?
A breakdown of one goal into the measures that drive it, level by level, until each measure can be influenced by one team. It shows everybody how their daily KPI contributes to the plant goal.
›How many levels should it have?
Usually three or four: plant goal, department or value stream, line or cell, and sometimes a specific driver such as changeover time. More levels make the tree hard to read; fewer leave the teams without a KPI they can change.
›What does “close to target” mean?
The actual value misses the target by no more than the tolerance you set, 5 % of the target by default. It is a warning: watch the trend before it turns red.
›Is this the same as hoshin kanri?
A KPI tree is one part of goal deployment. Hoshin kanri adds the breakthrough objectives, the improvement projects and the catchball between levels, often in an X-matrix.