We’d like a mechanism to filter the downtime options that appear when the “Review Downtime” button is selected on the timeline widget. Ideally we’d like to have the ability to customize precisely how it’s filtered, but the two most important filters are:
1) Only show uncategorized downtime
We automatically characterize some time downtime in machine triggers, and this would allow us to make reporting the remainder more user friendly
2) Only show downtime periods greater than X length
On certain equipment, there are short stoppages that we want to record, but don’t necessarily need to have downtime reasons for each.
I see this thread is from a while back, but wondering if there’s been any progress on filtering, or any workaround identified.
Machines generating lots of ‘downtime’ events when changing states - a few seconds at a time - which are not really downtime - and are drowning out real downtime events. Looking for a way to filter.
As far as I’m aware, this has never been resolved.
Our solution has been to modify our machine state trigger(s) and lose a little precision in favor of usability. Not ideal, but it is generally good enough.
If you’re prompting for downtime reasons when downtime happens rather than entering codes retroactively, it’s straightforward enough to wait until the machine has been down for > X seconds before triggering the prompt. You’d likely also want to automatically insert a generic “short stop” code for those small stops and filter them out as noise.
Yes, we’ve gone for the first option here and running our ‘downtime’ state trigger on a 60 second timer. As you say, not idea but generally good enough
Would you mind saying more about your second point? Interested in how you’d prompt for downtime reasons as they happen. Currently we’re using the ‘report downtime’ button on the standard machine timeline widget - but now thinking there may be a better, or at least more flexible way. Any info appreciated.
Hi @steven.kenny thanks for keeping this post alive! We have not made any changes to this widget but are making more general improvements that will help with downtime reporting. I’ll let @Dan answer your other questions; but in case your are not aware, it is possible to listen to machine state changes in any trigger and use that to set the downtime. For example, When machine state changes, if state is ‘Stopped’, show the downtime reason screen.
