Scheduled operations scheduled at the same time

Can someone elaborate on how and why this kind of scheduling happens?

Different operations, different products, same resource group. Why does scheduling allow suggestions to appear in the middle of a locked and scheduled work order?

Are you scheduling infinite?

FInite window 360 days. Calendars setup, resources correctly. In most cases it shows correct cascade scheduling, but this one does not. I cannot find why is this different. I mean the suggestion could be done before or after this, but this is overlapping. There is plenty of capacity, but not for this.

I am assuming SUG are unfirm job suggestions. If you firm one does it still try to schedule it where it is suggested?

Well, no, that is not it. I think it is an operational setting. Seems that even different operations can overlap when they do not have finish-to-start on. This for me is illogical a bit because the resource is booked for one operation and then another one is running at the same machine at the same time. Suggestions themselves do look nice:

Another example of which I do not understand the reason for. Same product, but scheduling is making it OK and NOK:

I have gone over all settings and parameters that I could think of and find, but these appear still.

I am adding here some more examples, but hopefully, someone will see. I have 2 different operations, but their setup is identical except for production std, but same resource settings on operations. “Busbar Laser Welding” is one where the schedule shows exactly how it should be and “Filling” shows overlapping operations in work orders and also scheduling several work orders at the same hour. I cannot find the cause for this difference.

  1. Good resource and operation schedule Busbar laser welding:

  2. Bad resource and operation schedule FILLING:


Any chance there is a concurrent capacity set on the resources?

I was wondering if 1282->1287 were for a very small Qty that the board looks wrong, but really cannot show such a small increment of time unless you blow it up to the minute level.

It is very detailed and it is production over weekend - work order starts on Friday and ends on Monday.

Concurrent capacity is set on all resources and BOMs because simply put single machines can only do single units at a time. But this is for all our resources most cases. Only a few operations look off on the scheduling boards.