Hi All,
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.
I hope that makes sense.
-Jeff
Capacity lives at the resource. Are you saying that the first op has a resource that is infinite?
Yes this is the case.
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.
do you run Multi level pegging? you can see what epicor thinks that supply job is going to.
We do not run multi level pegging.
We are having scheduling issues as well in Kinetic. Trying to pinpoint what is going on. What is Multi-pegging and how do I know if we have it to use?
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)
Good Morning –
I know this topic is from a while ago, but I’m curious if you ever found a way to prevent your stock room op from wanting to start today when the finite capacity resource can’t start for a week (for example)? We are new to Kinetic and are running into this exact issue, I’m hoping you have come up with a solution that you can share!
Thanks in advance!
We’ve been coming across this. Try changing the scheduling to Start to Start instead of the default for the OP.
Are you allowing “Historical scheduling”? if so this can cause interesting results. if you turn off historical, then the system will push out the work into the future if it runs into challenges.
We don’t do historical. It was scheduling us to start on day 1 of scheduling even if the next operation wasn’t until Feb 2026.
AH.. there is a “Minimize Wip” setting available in the Scheduling Priority Codes table… yours is probably turned off for your “normal” scheduling just like mine is. If you turn it ON, then after the system does a forward schedule (due to not allowing historical schedules), the system will do one final pass on the schedule, and will backward schedule it from the final finite capacity schedule.
In other words… if you have a due date of Nov 1, and you schedule the job finitely, and the system says “no, you cant have that until January 1”.. the system will then turnaround and do a backward schedule with a finish date of Jan 1, and will compress all the operations to be completed as late as possible while still meeting the January 1 date.
This didn’t help our situation. It actually made it worse because with that box checked, I cannot manually schedule operations in the various scheduling boards. Now if I try to move one operation in early and leave the remaining ops where they were, the system has all ops “locked” together. we use this to run jobs on our finite resources if we have a gap, but we don’t want the subsequent infinite resources scheduled earlier than need be to meet customer demand. Not to mention, when we ran MRP last night our original problem of the big gap between to first two operations is still there on MRP jobs.
Has this helped your situation? and do you set the “start to start” option on the first op or second op?
Still seeing the same thing:
The first op is supposed to take 13 minutes.
Looking at the shop load for that week ( the 22nd ), there are 2.87 hours remaining. I don’t understand why it’s putting this op “today” and not on the day in question (1 hour available on that day).
I put the “Start to Start” on the first op.
You would want to make the second op Start to Start. That field interacts with the prior operation, not the following.
