If a resource group is on finite, but the first op is on infinite (material prep in this case), does Kinetic pull all the parts that have a finite process to be ran immediately on the first op regardless of the actual due date.
if you are set up as backwards schedule, epicor will try to build Just in Time for when the part is needed.
if Op 10 is infinite, it will still schedule based on when the jobs need to start to satisfy the demand dates. if the scheduling engine cant go backwards in time (as it shouldnt because time travel doesnt exist YET) it wil have the jobs start on the date of the Start date in your MRP run.
It will load up Op 10 with all the jobs that need to start and when it gets to a Op that has a resource that is Finite, it will only schedule what that resource can handle.
So depending on how you run your shop you can decide what resources should be Finite.
Me personally for an assembly line i would set an early op as Finite or follow TOC and set your bottleneck Op as finite so you can exploit the bottleneck. but play around with it in a test environment and see what it does to your schedule when you set diffrent resources as finite.
It appears our first resource was flooded when anything that used a finite resource as a second op was scheduled. Kinetic pulled it in regardless of a start date for some reason.
its a process you can run and it matches up Supply and Demand. its not a hard allocation just more of a “this demand is why you are buying/making things” so you can visually see how everything is linked.
You can run the “Pegging” process manually or optionally when running MRP.
In addition to the standard “Multi Level Pegging Display”, I like using custom dashboard views. Here is a VERY simple example, just to give an idea of tables & links involved. CUS-PeggingRawData.dbd (220.7 KB)