In one of our departments we run 3000 sku’s that vary process time per sku. It would be extremely helpful to have a variable timer that could pull in the time routed by sku (based on a lookup) and dynamically update the process timer shown on the step.
4 Likes
Chase,
We are definitely seeing a lot of requests for more dynamic & powerful timer features, and I’m starting to scope out our approach. I’d love to better understand your use case and ideal solution. Does this description match what you are imagining:
Your app dynamically pulls in a value that represents the target process cycle time. The current process timer widget takes that value as an input, and it countdowns as it currently does.
Are there other features related to timers that also would help you better execute your use case? For example we’ve also had requests for timers that count upward, or for visualizations such as bars that fill in.
I’m also curious if you have issues/ideas with how pause currently works and is calculated in analytics? Currently bringing up the menu does not pause the application, a user must explicitly hit the pause button once the menu is up. Perhaps it would be more simple if the menu was by default a paused state.
2 Likes
Mark,
What you explained is exactly what we are looking for. I would like to add on the if the time is exceeded that it continues to show the time past the target time.
I have not used the timer much since it does not have this variable feature. I think both of the examples you have listed would be beneficial. As for the pause feature, I think it would be great if a standard button could pause rather than having to hit the menu button. For the use case I am looking at, if the operator needs to pause the timer, they should be entering data into another step as to why they had to pause.
2 Likes
Any idea when this will be available? We’d like to be able to use the app to build our Lean performance metrics which displays takt time countdown which is obviously different than step cycle time as well as displaying lost time, which is a countup, from pauses or stops.
Thanks,
Audra
4 Likes
A couple extra points on this feature request for our specific asks:
- Ability to “play” & “pause” variable/custom timers
- Ability to specify count down vs. count up
- Ability to write to the timer variable & set it to a specific time
Thanks!
2 Likes
I second this. I would add that having a timer activate a trigger once it counts down could give us a lot more automation abilities.
Hey everyone – thanks for your input here! We definitely see the value in adding timer variable. We’ll circle back and update when we have a plan and timeline to share.
1 Like
Looks like the Tulip engineering wizards will have a pretty solid solution that addresses this exact request. I thought I would offer a suggestion in the meantime - maybe there is a way to make it work with the tools that are available right now?
Here’s an idea but it will only work for takt times that are greater than 30 seconds. Since we have the 30 second timer and the ability to log time stamps, you could pretty easily make a function that checks every 30 seconds to evaluate the difference between the current time and the start of your cycle. This could be displayed and recalculated every 30 seconds. Not perfect, but the great thing is that when you actually complete your cycle you will be able to log the exact time it took relative to the takt time. You could even display it as a chart to sort of gamify the experience for the operator.
It’s not perfect… but it will probably work! Sorry to those with takt times under 30 seconds though! We might need to come up with something different or wait for the new feature to handle those in the fast lane (I have some ideas if you are less than 30 seconds, so let me know!).
Really looking forward to seeing this, it will be really helpful for the operators to be able to compare their progress to the expected process time for that SKU.