All the data used in this study was generated manually, and is in no way representative of any company in particular.
The fictitious factory that wwe chose has three product lines, each containing a few workstations (who are themselves made of many sub-stations, or step). This data has been generated without a final product in mind, and thus the amount and lengths of breakdowns are just for information.
The method is of course relevant for any product and can be adapted to any product line structure
This dashboard displays the frequencies and the impacts of disturbances in a production warehouse.
Our factory is fictitious, and is built so that each product line is made up of numerous workstations, which are also broken down into sub-stations (or steps). Each of the three menus (one for each product) contains a tab with global information about the specific product line, as well as one tab for each workstation within it. The different tabs are organized in the same fashion :
More information on these elements can be found by clicking the and the help tabs.
The opposite and below graphs were computed by using data from all product lines / workstations together
We chose to display 2 usual quality control metrics, the MTBF and the MTTR :
MTTR stands for Mean Time To Repair, where the Time To Repair is the mean time elapsed between the emergence of a disturbance and its resolution. This time is often subdivided into different phases (time elapsed before finding technical support, time elapsed before finding a solution, time elapsed before implementing the solution for example) but to keep the graphs as simple as possible we only used the time to repair.
On the x-axis are the serial numbers of the products, and on the y-axis the down time due to disturbances on the given product line and period.
For readability, the types of issues can be visualized stacked (by default) or individually, by manually unticking the unwanted disturbances.
MTBF means Mean Time Between Failures, where the Time Between Failure is the time elapsed between two breakdowns due to an issue.
It can be computed in different ways depending on the metric of interest; we chose here to compute MTBFs on sub-stations, which means we computed the mean time between the emergence of two problems on each step, for a types of issues. Consequently the steps for which the MTBF is not zero are those which broke down at least twice, whatever the issue was.
Other examples would also work, like :
The mean time between failures for the same component, which means the time elapsed between two same issues, for a given step (to underline a systematically failing component)
The mean time between the emergence of issues of the same type, but taking into accounts al product lines together
At higher levels (product line or overall), MTBFs are computed by taking the mean of the MTBFs of its elements.
For readability, the types of issues can be visualized stacked (by default) or individually, by manually unticking the unwanted disturbances.
We chose to display 2 usual quality control metrics, the MTBF and the MTTR :
MTTR stands for Mean Time To Repair, where the Time To Repair is the mean time elapsed between the emergence of a disturbance and its resolution. This time is often subdivided into different phases (time elapsed before finding technical support, time elapsed before finding a solution, time elapsed before implementing the solution for example) but to keep the graphs as simple as possible we only used the time to repair.
On the x-axis are the serial numbers of the products, and on the y-axis the down time due to disturbances on the given product line and period.
For readability, the types of issues can be visualized stacked (by default) or individually, by manually unticking the unwanted disturbances.
MTBF means Mean Time Between Failures, where the Time Between Failure is the time elapsed between two breakdowns due to an issue.
It can be computed in different ways depending on the metric of interest; we chose here to compute MTBFs on sub-stations, which means we computed the mean time between the emergence of two problems on each step, for a types of issues. Consequently the steps for which the MTBF is not zero are those which broke down at least twice, whatever the issue was.
Other examples would also work, like :
The mean time between failures for the same component, which means the time elapsed between two same issues, for a given step (to underline a systematically failing component)
The mean time between the emergence of issues of the same type, but taking into accounts al product lines together
At higher levels (product line or overall), MTBFs are computed by taking the mean of the MTBFs of its elements.
For readability, the types of issues can be visualized stacked (by default) or individually, by manually unticking the unwanted disturbances.
We chose to display 2 usual quality control metrics, the MTBF and the MTTR :
MTTR stands for Mean Time To Repair, where the Time To Repair is the mean time elapsed between the emergence of a disturbance and its resolution. This time is often subdivided into different phases (time elapsed before finding technical support, time elapsed before finding a solution, time elapsed before implementing the solution for example) but to keep the graphs as simple as possible we only used the time to repair.
On the x-axis are the serial numbers of the products, and on the y-axis the down time due to disturbances on the given product line and period.
For readability, the types of issues can be visualized stacked (by default) or individually, by manually unticking the unwanted disturbances.
MTBF means Mean Time Between Failures, where the Time Between Failure is the time elapsed between two breakdowns due to an issue.
It can be computed in different ways depending on the metric of interest; we chose here to compute MTBFs on sub-stations, which means we computed the mean time between the emergence of two problems on each step, for a types of issues. Consequently the steps for which the MTBF is not zero are those which broke down at least twice, whatever the issue was.
Other examples would also work, like :
The mean time between failures for the same component, which means the time elapsed between two same issues, for a given step (to underline a systematically failing component)
The mean time between the emergence of issues of the same type, but taking into accounts al product lines together
At higher levels (product line or overall), MTBFs are computed by taking the mean of the MTBFs of its elements.
For readability, the types of issues can be visualized stacked (by default) or individually, by manually unticking the unwanted disturbances.
We chose to display 2 usual quality control metrics, the MTBF and the MTTR :
MTTR stands for Mean Time To Repair, where the Time To Repair is the mean time elapsed between the emergence of a disturbance and its resolution. This time is often subdivided into different phases (time elapsed before finding technical support, time elapsed before finding a solution, time elapsed before implementing the solution for example) but to keep the graphs as simple as possible we only used the time to repair.
On the x-axis are the serial numbers of the products, and on the y-axis the down time due to disturbances on the given product line and period.
For readability, the types of issues can be visualized stacked (by default) or individually, by manually unticking the unwanted disturbances.
MTBF means Mean Time Between Failures, where the Time Between Failure is the time elapsed between two breakdowns due to an issue.
It can be computed in different ways depending on the metric of interest; we chose here to compute MTBFs on sub-stations, which means we computed the mean time between the emergence of two problems on each step, for a types of issues. Consequently the steps for which the MTBF is not zero are those which broke down at least twice, whatever the issue was.
Other examples would also work, like :
The mean time between failures for the same component, which means the time elapsed between two same issues, for a given step (to underline a systematically failing component)
The mean time between the emergence of issues of the same type, but taking into accounts al product lines together
At higher levels (product line or overall), MTBFs are computed by taking the mean of the MTBFs of its elements.
For readability, the types of issues can be visualized stacked (by default) or individually, by manually unticking the unwanted disturbances.
We chose to display 2 usual quality control metrics, the MTBF and the MTTR :
MTTR stands for Mean Time To Repair, where the Time To Repair is the mean time elapsed between the emergence of a disturbance and its resolution. This time is often subdivided into different phases (time elapsed before finding technical support, time elapsed before finding a solution, time elapsed before implementing the solution for example) but to keep the graphs as simple as possible we only used the time to repair.
On the x-axis are the serial numbers of the products, and on the y-axis the down time due to disturbances on the given product line and period.
For readability, the types of issues can be visualized stacked (by default) or individually, by manually unticking the unwanted disturbances.
MTBF means Mean Time Between Failures, where the Time Between Failure is the time elapsed between two breakdowns due to an issue.
It can be computed in different ways depending on the metric of interest; we chose here to compute MTBFs on sub-stations, which means we computed the mean time between the emergence of two problems on each step, for a types of issues. Consequently the steps for which the MTBF is not zero are those which broke down at least twice, whatever the issue was.
Other examples would also work, like :
The mean time between failures for the same component, which means the time elapsed between two same issues, for a given step (to underline a systematically failing component)
The mean time between the emergence of issues of the same type, but taking into accounts al product lines together
At higher levels (product line or overall), MTBFs are computed by taking the mean of the MTBFs of its elements.
For readability, the types of issues can be visualized stacked (by default) or individually, by manually unticking the unwanted disturbances.
We chose to display 2 usual quality control metrics, the MTBF and the MTTR :
MTTR stands for Mean Time To Repair, where the Time To Repair is the mean time elapsed between the emergence of a disturbance and its resolution. This time is often subdivided into different phases (time elapsed before finding technical support, time elapsed before finding a solution, time elapsed before implementing the solution for example) but to keep the graphs as simple as possible we only used the time to repair.
On the x-axis are the serial numbers of the products, and on the y-axis the down time due to disturbances on the given product line and period.
For readability, the types of issues can be visualized stacked (by default) or individually, by manually unticking the unwanted disturbances.
MTBF means Mean Time Between Failures, where the Time Between Failure is the time elapsed between two breakdowns due to an issue.
It can be computed in different ways depending on the metric of interest; we chose here to compute MTBFs on sub-stations, which means we computed the mean time between the emergence of two problems on each step, for a types of issues. Consequently the steps for which the MTBF is not zero are those which broke down at least twice, whatever the issue was.
Other examples would also work, like :
The mean time between failures for the same component, which means the time elapsed between two same issues, for a given step (to underline a systematically failing component)
The mean time between the emergence of issues of the same type, but taking into accounts al product lines together
At higher levels (product line or overall), MTBFs are computed by taking the mean of the MTBFs of its elements.
For readability, the types of issues can be visualized stacked (by default) or individually, by manually unticking the unwanted disturbances.
We chose to display 2 usual quality control metrics, the MTBF and the MTTR :
MTTR stands for Mean Time To Repair, where the Time To Repair is the mean time elapsed between the emergence of a disturbance and its resolution. This time is often subdivided into different phases (time elapsed before finding technical support, time elapsed before finding a solution, time elapsed before implementing the solution for example) but to keep the graphs as simple as possible we only used the time to repair.
On the x-axis are the serial numbers of the products, and on the y-axis the down time due to disturbances on the given product line and period.
For readability, the types of issues can be visualized stacked (by default) or individually, by manually unticking the unwanted disturbances.
MTBF means Mean Time Between Failures, where the Time Between Failure is the time elapsed between two breakdowns due to an issue.
It can be computed in different ways depending on the metric of interest; we chose here to compute MTBFs on sub-stations, which means we computed the mean time between the emergence of two problems on each step, for a types of issues. Consequently the steps for which the MTBF is not zero are those which broke down at least twice, whatever the issue was.
Other examples would also work, like :
The mean time between failures for the same component, which means the time elapsed between two same issues, for a given step (to underline a systematically failing component)
The mean time between the emergence of issues of the same type, but taking into accounts al product lines together
At higher levels (product line or overall), MTBFs are computed by taking the mean of the MTBFs of its elements.
For readability, the types of issues can be visualized stacked (by default) or individually, by manually unticking the unwanted disturbances.
We chose to display 2 usual quality control metrics, the MTBF and the MTTR :
MTTR stands for Mean Time To Repair, where the Time To Repair is the mean time elapsed between the emergence of a disturbance and its resolution. This time is often subdivided into different phases (time elapsed before finding technical support, time elapsed before finding a solution, time elapsed before implementing the solution for example) but to keep the graphs as simple as possible we only used the time to repair.
On the x-axis are the serial numbers of the products, and on the y-axis the down time due to disturbances on the given product line and period.
For readability, the types of issues can be visualized stacked (by default) or individually, by manually unticking the unwanted disturbances.
MTBF means Mean Time Between Failures, where the Time Between Failure is the time elapsed between two breakdowns due to an issue.
It can be computed in different ways depending on the metric of interest; we chose here to compute MTBFs on sub-stations, which means we computed the mean time between the emergence of two problems on each step, for a types of issues. Consequently the steps for which the MTBF is not zero are those which broke down at least twice, whatever the issue was.
Other examples would also work, like :
The mean time between failures for the same component, which means the time elapsed between two same issues, for a given step (to underline a systematically failing component)
The mean time between the emergence of issues of the same type, but taking into accounts al product lines together
At higher levels (product line or overall), MTBFs are computed by taking the mean of the MTBFs of its elements.
For readability, the types of issues can be visualized stacked (by default) or individually, by manually unticking the unwanted disturbances.
We chose to display 2 usual quality control metrics, the MTBF and the MTTR :
MTTR stands for Mean Time To Repair, where the Time To Repair is the mean time elapsed between the emergence of a disturbance and its resolution. This time is often subdivided into different phases (time elapsed before finding technical support, time elapsed before finding a solution, time elapsed before implementing the solution for example) but to keep the graphs as simple as possible we only used the time to repair.
On the x-axis are the serial numbers of the products, and on the y-axis the down time due to disturbances on the given product line and period.
For readability, the types of issues can be visualized stacked (by default) or individually, by manually unticking the unwanted disturbances.
MTBF means Mean Time Between Failures, where the Time Between Failure is the time elapsed between two breakdowns due to an issue.
It can be computed in different ways depending on the metric of interest; we chose here to compute MTBFs on sub-stations, which means we computed the mean time between the emergence of two problems on each step, for a types of issues. Consequently the steps for which the MTBF is not zero are those which broke down at least twice, whatever the issue was.
Other examples would also work, like :
The mean time between failures for the same component, which means the time elapsed between two same issues, for a given step (to underline a systematically failing component)
The mean time between the emergence of issues of the same type, but taking into accounts al product lines together
At higher levels (product line or overall), MTBFs are computed by taking the mean of the MTBFs of its elements.
For readability, the types of issues can be visualized stacked (by default) or individually, by manually unticking the unwanted disturbances.
We chose to display 2 usual quality control metrics, the MTBF and the MTTR :
MTTR stands for Mean Time To Repair, where the Time To Repair is the mean time elapsed between the emergence of a disturbance and its resolution. This time is often subdivided into different phases (time elapsed before finding technical support, time elapsed before finding a solution, time elapsed before implementing the solution for example) but to keep the graphs as simple as possible we only used the time to repair.
On the x-axis are the serial numbers of the products, and on the y-axis the down time due to disturbances on the given product line and period.
For readability, the types of issues can be visualized stacked (by default) or individually, by manually unticking the unwanted disturbances.
MTBF means Mean Time Between Failures, where the Time Between Failure is the time elapsed between two breakdowns due to an issue.
It can be computed in different ways depending on the metric of interest; we chose here to compute MTBFs on sub-stations, which means we computed the mean time between the emergence of two problems on each step, for a types of issues. Consequently the steps for which the MTBF is not zero are those which broke down at least twice, whatever the issue was.
Other examples would also work, like :
The mean time between failures for the same component, which means the time elapsed between two same issues, for a given step (to underline a systematically failing component)
The mean time between the emergence of issues of the same type, but taking into accounts al product lines together
At higher levels (product line or overall), MTBFs are computed by taking the mean of the MTBFs of its elements.
For readability, the types of issues can be visualized stacked (by default) or individually, by manually unticking the unwanted disturbances.
We chose to display 2 usual quality control metrics, the MTBF and the MTTR :
MTTR stands for Mean Time To Repair, where the Time To Repair is the mean time elapsed between the emergence of a disturbance and its resolution. This time is often subdivided into different phases (time elapsed before finding technical support, time elapsed before finding a solution, time elapsed before implementing the solution for example) but to keep the graphs as simple as possible we only used the time to repair.
On the x-axis are the serial numbers of the products, and on the y-axis the down time due to disturbances on the given product line and period.
For readability, the types of issues can be visualized stacked (by default) or individually, by manually unticking the unwanted disturbances.
MTBF means Mean Time Between Failures, where the Time Between Failure is the time elapsed between two breakdowns due to an issue.
It can be computed in different ways depending on the metric of interest; we chose here to compute MTBFs on sub-stations, which means we computed the mean time between the emergence of two problems on each step, for a types of issues. Consequently the steps for which the MTBF is not zero are those which broke down at least twice, whatever the issue was.
Other examples would also work, like :
The mean time between failures for the same component, which means the time elapsed between two same issues, for a given step (to underline a systematically failing component)
The mean time between the emergence of issues of the same type, but taking into accounts al product lines together
At higher levels (product line or overall), MTBFs are computed by taking the mean of the MTBFs of its elements.
For readability, the types of issues can be visualized stacked (by default) or individually, by manually unticking the unwanted disturbances.
We chose to display 2 usual quality control metrics, the MTBF and the MTTR :
MTTR stands for Mean Time To Repair, where the Time To Repair is the mean time elapsed between the emergence of a disturbance and its resolution. This time is often subdivided into different phases (time elapsed before finding technical support, time elapsed before finding a solution, time elapsed before implementing the solution for example) but to keep the graphs as simple as possible we only used the time to repair.
On the x-axis are the serial numbers of the products, and on the y-axis the down time due to disturbances on the given product line and period.
For readability, the types of issues can be visualized stacked (by default) or individually, by manually unticking the unwanted disturbances.
MTBF means Mean Time Between Failures, where the Time Between Failure is the time elapsed between two breakdowns due to an issue.
It can be computed in different ways depending on the metric of interest; we chose here to compute MTBFs on sub-stations, which means we computed the mean time between the emergence of two problems on each step, for a types of issues. Consequently the steps for which the MTBF is not zero are those which broke down at least twice, whatever the issue was.
Other examples would also work, like :
The mean time between failures for the same component, which means the time elapsed between two same issues, for a given step (to underline a systematically failing component)
The mean time between the emergence of issues of the same type, but taking into accounts al product lines together
At higher levels (product line or overall), MTBFs are computed by taking the mean of the MTBFs of its elements.
For readability, the types of issues can be visualized stacked (by default) or individually, by manually unticking the unwanted disturbances.