Hi,
Still wrestling with this issue.
The customer has a huge seasonal sales demand in the fourth-quarter, with a curve they call the “hockey stick.” They can’t produce at the hockey stick rate, so need MRP scheduling to push the demand forward to the earlier parts of the year.
We have 10 resources to spread the production over. We’ve set them up as “finite capacity.” We’ve tried both scheduling by resource group and capabilities. Many parts are set up with mfg lot sizes that generate longer-runtime jobs (~40 hours). We have a finished good (packaged item) that gets a job suggestion that drives the demand/required due dates for the semi-finished good parts we’re concentrating on now.
When we look at the MRP-generated schedule for the semi-finished goods we see lots of gaps during the year, and a bunch of late jobs at the end.
I’ve watched job suggestions pop up during a (lengthy) MRP process, and here’s something of what I found:
We have parts A-J to schedule. MRP schedules all of one part at a time, in part number alpha-numeric order.
MRP starts with part A, the first FG due job and schedules the SFG part. Then it gets the next FG due job and schedules a SFG job for it. On into the future until part A is all scheduled. Scheduling the hockey stick demand by due date is no problem, because all the capacity of the SFG resources is untapped at this point.
Same for B. Still plenty of resource capacity left.
And C, D, E, and F.
Part G comes and we get into the higher volume items. Now we have a lot of capacity tied up, but the earlier due dates come out okay, because those dates are from the early months of the year (remember the hockey stick in October). When we hit that, the big chunks of capacity ( for jobs that we want to push back toward the first of the year) where we could put 40 hours-worth of job are gone, so they start going late.
Parts H-J compound upon the disarray.
Instead of scheduling the big jobs way in the future first and working backward to fill the schedule, we’re filling the near-term capacity first by due dates, and then trying to stuff “fifty pounds of mud in a five pound bag” (see Dolly Parton quotes) when we get to the hockey stick demand curve.
After this consideration, I don’t see a way to make MRP do what the customer needs. The move to constraining resources with finite capacity was intended to push the demand back toward the earlier part of the year, but this hasn’t worked out. We’ve tried global scheduling to try to squeeze out the gaps with limited results, and the schedule is distorted anyway, because of the way MRP schedules one part at a time.
Still with me after all this setup? Cool.
I’ve done a customization to let MRP spread jobs out among the resources and then re-sort and reschedule by required due date. The customer would rather MRP handle the scheduling, but I don’t see how to make it do so.
Has anyone encountered this type of seasonal demand and addressed it with Epicor MRP scheduling?
Thanks,
Joe