We are going over the scope items for 2024.2, and one epic that I have been promoting is a feature called “Dynamic Timefence”…
One of the team members asked “why dont we have any votes for this feature?” and I just realized that it is because it was never a public IDEA for it…
SO… if you like the idea, please vote. If you dont, please dont vote. in any case… feel free to add comments to the idea in Epicor Ideas. It just might make it into the 2024.2 release. https://epicor-manufacturing.ideas.aha.io/ideas/KIN-I-4622
Summary of the idea:
Dynamic TimeFence: Job & PO Automatic time Fence on Locked Schedule for MRP purposes
Create a new concept for TimeFence called Dynamic Timefence which will automatically adjust the timefence used by MRP. Instead of only using the timefence from the Part, it will also use the scheduled completion date of the locked job(s) or locked PO(s) that has the longest leadtime.
I guess I don’t understand the concept that well. If the planner says “We can’t make it, I’m pushing the job out”, then in my head, they need to adjust the order (“demand”) out so that MRP doesn’t try to change it. A setting to tell MRP to ignore a mismatch in dates kind of defeats the purpose doesn’t it?
And while this works with a simple example of one order, what happens when the decision by the planner is because “It’s only 10, it’s not worth the extra work do expedite” so they lock it, but then a NEW order comes in for 80 more and it would be worth the extra work. Do they not get any notification about the change in demand? Or is MRP somehow keeping track of old vs new demand?
the challenge is that CURRENTLY, if you lock a PO or a job’s schedule, the system will then stop recommending that the po/job be changed, but instead will tell you to create a new one. The planner/buyer, will not be told to cancel the existing job/po because it is locked. if the buyer/planner DOES create the new job/po, then you have double the stuff you need. This can even be worse in the case of jobs, since it will create a new unfirm job, with new demands that will cause additional POs to be created.
The entire idea is to help eliminate this chatter when you have intentionally locked the PO.
Yes, PO and JOB Locking can be abused. In my view, locking is used way too much. for example, when you lock a PO/JOB, the system will stop making suggestions, (even cancellation suggestions) when the demand changes.