The hours/time field in the routing op is a conversion factor. It is defaulting to 1. This means that the numbers in my time fields are "hours". For short run times we put in 0.0167 . Now my numbers mean "minutes". Maybe in some cases we put in "24" so now the numbers in my time fields stand for calendar days. Processes like curing in ovens etc. But that is about it. No other values should be needed. no other values should be possible. This field should not be wide open for ANY number. We just had somebody put in 300 by mistake. The routing time exploded to a huge number, creating panic in the cost accounting department. The user should be protected against this type of grotesk mistakes. The field should not be a numeric conversion factor. All manufacturing companies in the world can function perfectly with a simple 3 value enum choice here: are you talking hours, minutes or days in your setup and run times? that is it. This would be a step forward for user friendliness.

Needs Votes
Ideas Administrator

Currently this is not in our roadmap; however, we are tracking it and if we get more feedback and votes, we may consider it in the future.


Johan Hoffmann