Hi all,
To give context for this post, we currently have multiple machines reporting OEE through the machine tables and I am getting complaints of there’s a lot of ‘Null’ downtime being reported, where the operator has not entered a code or has entered a code later and its not filled in previous records. We have the machine state change once an hour for accuracy, meaning if a machine is down for 3 hours and a code is not entered until the second hour, the first one will be classed as null. To fix that, I want to give the makers the opportunity to go back and update the previous downtimes.
That being said, I think it would be a good option to have the machine timeline ‘Review Downtime’ button as a separate entity. Currently it is fixed and does not allow resizing to occur which makes it difficult for our makers to interact with the button on something like an iPad.
Making it a separate button would allow for it to be resized and more easily clickable.
Another option could be to have the machine table be an option in the interactive table widget, where uncategorized downtime can be selected and updated. I believe this would be the way our team would want to go, and also allows for further machine table manipulation, should it need to be done (incorrect job selections or downtime code etc.)
Thanks!
Dan