...
Old Model
The current old model of searching for root causes relies relied on checking the time when a Holdup/Idle state began and then checking another machine if it was not in the Failure/Lack of Components/Stopped by Operator state in the same period of time, regardless of the moment in which that state began.
...
All the other states are “transparent”. There is no “bouncing” the other way: if we are looking for the cause of a holdup, we never look at the machines before the Base Availability machine even if one of the downstream machines is in the Idle state.
...
If there is was no breakdown at this point of time, the Holdup state will would not find any root cause.
...
Setting the buffer time allows allowed you to “target” a different spot. The buffer time is was actually the “reaction time”. If your machines always work with transporters that are full or they work synchronously, the buffer time equals 0s despite the fact that it takes some time for the product to be moved between machines.
...
On the other hand, it may also create a problem if a state is slightly misaligned in relation to a specific buffer. The farther from the source, the bigger the probability of “mistargeting” if the specified buffer time between machines is different from what it actually is (for example, that time can be greater due to slower work or shorter because of the bigger dimensions of products).
...
Improvements
In order to take into account full buffers / shorter reaction times, you should take into consideration the entire period starting from the maximum reaction time (x- which is currently configurable) and ending in the moment when a stoppage began - or even a while after the stoppage started ( y ) which would let you spot a situation when a driver did not “report” a breakdown as fast as it should have:
...