Setup Time Disappears When Changing Manufacturing Orders to "Confirmed" Status

[matteocarcano]

Hi,
I have encountered an issue where the setup time is not retained when changing the status of manufacturing orders (MOs) from "proposed" to "confirmed."

Steps to Reproduce:
Initially, MOs 257 and 337 are correctly planned, including the setup time in both the Setup Duration and Net Duration columns (see Image 1).
When changing these MOs to the "confirmed" status (see Image 2), the setup time disappears from both the Setup Duration and Net Duration columns (see Image 3).
If I rerun the planning engine, the setup time is no longer considered.
However, if I revert the status back to "proposed," the setup time reappears.

Additional Information:
I reproduced this behavior using the example resource setup matrices in Frepple's demo environment.
However, the same issue also occurs when using my own dataset.

Expected Behavior:
I would expect the setup time to be retained even when the MOs are set to "confirmed" since the operation itself has not changed.

Is this the intended behavior, or could it be a bug? Any insights would be appreciated.

Thanks!

[jdetaeye]

First of all, setup times are not really supported in the Community Edition. There are some pieces of the code that have been copied from the Enterprise&Cloud Editions into the Community Edition, but whether it's meeting your expectations isn't sure.

On the actual question:
You are correct that confirmed operationplans don't keep their setup time. They always have a 0 setup time.

[matteocarcano]

If I may ask, what is the reason behind this choice? The setup time for confimed orders is crucial since scheduling them properly is very important

[jdetaeye]

If I may ask, what is the reason behind this choice? The setup time for confimed orders is crucial since scheduling them properly is very important

The setup time depends on what item was produced before. So, a confirmed manufacturing order that we consider fixed/frozen/untouchable all of a sudden would need to change if I plan a different proposed or approved manufacturing order before it.

That was the original thought behind this choice. I agree with you that it's ideal in some situations. Eg if I plan proposed / approved manufacturing orders start-to-end in a sequence there will be some setup time considered in the plan. If I now put that sequence in confirmed status the setup time disappears, and you will see "holes" in your schedule.

You're always free to submit a pull request 😃 It's open source...

[matteocarcano]

ok thank you for reply