This article will help explain why when drilling into a Downtime Pareto chart, the downtime number increases when the user selects to see the Action and Component Pareto.
When calculating the Downtime number for this chart, L2L uses the actual number of minutes for each individual resource event that makes up the data. For instance, if this Pareto chart looked at 10 dispatches with downtime of 100 minutes each, the total number of downtime minutes would be 1000 for the chart on the left.
On the other hand, when drilling into the Action and Component codes, L2L looks at the quantity (not downtime) of Action and Component codes for each dispatch and multiplies them by the downtime for each dispatch, like the chart on the right. For instance, if this Pareto chart looked at 10 dispatches with downtime of 100 minutes each, but each dispatch had 3 Action and Component fields, the total downtime for this Pareto would be 3000 minutes.
Why Is It Calculated This Way?
The main reason this is calculated in this fashion is due to the fact that the Action and Components are always input after the dispatch is complete or at least not in a real-time manner. It would be very time-consuming for the User to stop work and input an Action and Component each time they performed a task on a dispatch event.
- When looking to improve downtime, Leading2Lean recommends using 'arduous' as the basis for your improvement efforts.
- One-time events or irregular events can skew the downtime numbers. While events that reccur on a regular basis are a larger drain on resources and assets and can be easily identified with Occurrence Pareto charts.
- When looking for downtime for a specific Component, start first by drilling down to Actions, then choosing a Component.
- When looking for downtime for a specific Action, start first by drilling down to Components, then choosing an Action.