Production floor execution (PFE) is a great interface for operators to report progress and consumed material on operations. However, in many occasions it is not wished to capture actual time spent (actually this requirement has been a reality in basically all my projects, at least for some route operations), but rather consume the estimated time from the route.
There has to be a way to define which routes operations that should capture actual time (between start and stop) or to only and automatically register and post time based on the estimate defined in the production route operation. With this solution I believe that there is really nothing that would hinder our customers to use manufacturing execution and PFE anymore and we could offer a very professional and user friendly solution to report on production operations.
The alternative is to not use PFE and report progress in form "current operations" but apart from the fact that this is far from ideal to use on the production floor it does not really support part registrations when quantity is more than one and many operations exist.
Comments
I totally agree with the above comments. It's really not a good user experience, because you need to check the time and attendance module, but mostly it's not used. So the preferred way would be, that it would be available if someone would use it otherwise it wouldn't be used and wouldn't be the key to run production floor execution, those two modules should be separated completely.
Category: Production Control
This will help us to get more customer to choose Production Floor Execution app, as they don't want to use the time and attendance module. for current customers we have developed a solution to delete the journals.
Category: Production Control
Yes please!
Category: Production Control
The limited flexibility of the integration of Manufacturing execution with Time & Attendance has resulted in most implementations selecting alternate processes to manage posting production time, often with substantial negative feedback from production supervisors that Dynamics does not support typical manufacturing scenarios.The ability to selectively report actual time or estimated time on individual operations would be a great feature.A selectable tolerance for the difference between actual report time and estimated time for operations to be 'flagged' when an operation is reported as finished would also be a useful addition.
Category: Production Control
In many implementations we have added a modification to delete associated un-transferred time registrations on ending a production order. As previously mentioned our customers do not want to calculate, approve & transfer time journals. We have also had customers who wish to use MES and backflush standard hours. Resolving these issues would improve the offering.
Category: Production Control
This will help in our implementation as we are not using time and attendance module and to have the ability not to calculate, approve and transfer in TA and not having to sort out related open registrations will make the PFE very appealing.
Category: Production Control
This is an excellent idea! Please give it on the short term roadmap!
Category: Production Control
In addition, I'm aware that one could create a solution where one creates two journals with both actual time and estimated time but then one would have to delete the actual time journal before processing the order which is again is far from a good solution. On top of that the batchjobs need to approve, calculate and transfer time journals. All of this just to report an operation complete.
Category: Production Control
Administrator
Thank you for your feedback. This is a great suggestion!
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.
Sincerely,
Johan Hoffmann
PM, Microsoft