Machine or line state downtime, is always assigned to one of the āstatesā, which determines the semantic meaning (e.g. changeover, failure, stop by operator) and influences the root cause analysis. Itās calculated automatically or selected by the user.
If you get a flat tire in your car, the problem is observable: āYou have a flat tireā. The computer in your car probably recognise it based on a low air pressure. Same as PackOS determining that a machine is in some type of Failure.
This situation can be further described with a different level of detail. Here is a guidance how to understand different descriptions of the situation:
1. Reason (WHY HAPPENED?)
Did you bump into a hole?
Was there something sharp on the asphalt?
Maybe the tire was just very old?
These questions are aiming to identify the real reason of the problem which is often hard or impossible to deduce automatically. Reporting reasons helps you avoid problems in the future (e.g. replace your tires more often). This list can grow dynamically, when new reasons are identified.
Note that āOld tireā is a reason specifically related to the problem āFlat tire' - itās part of the list of the potential reasons of that problem.
If you determine that the problem was in fact something else - e.g. āBroken Engineā, the reason needs to be determined and selected again.
2. Corrective Action (HOW SOLVED?)
Did you use a spare tire?
Did you fixed the old tire?
Did you call for a tow track?
Corrective actions describes suggestions how the problem can be solved
Seeing all possible solutions to a problem may help point unexperienced operators to a solution. Reporting which corrective actions are most often selected, how this impacts the duration of the downtime - might be a hint what processes are most optimal and are worth following.
3. Comment (ANYTHING ELSE?)
What was the weather?
Did the tow track arrived quickly enough?
Did you have the spare tire with you?
Anything else, which is worth mentioning should be added as a comment. Going through the comments might help identify potential new reasons or corrective actions. Or highlight issues with the processes.