MSO: Forward and Backward scheduling

Hi ​@FleVidurK ,

If you are using a cloud version older than 25R2 EA, MSO will automatically include past orders in the scheduling process. The logic is as follows: if the scheduling horizon is X days, then orders from up to 10X days in the past will be considered.

If you are using 25R2 EA or a later version, there is an option to manually configure the past order selection window (in number of days) from the Basic Data page.

Regarding how these orders are scheduled: in general, they will be planned after the current date and time. However, if an order has an earliest start date that is later than the current date, it will be scheduled based on that constraint.

Hi Pavani,
 

Thanks for the explanation regarding the selection of past orders.
However, my question is more about the scheduling logic:

When a shop order is already tardy (need date in the past), does MSO automatically switch to forward scheduling from the earliest start date without manually touching these shop orders, or does it still follow the scheduling direction defined on the shop order header?

kind regards


 

• Hi ​@FleVidurK , since the Need date is already passed, MSO will no longer follow the scheduling direction. Instead, MSO will follow below logics. 
  • During scheduling, orders where the need date is not passed will be prioritize. (Reason: Before 25R2, MSO was always trying to reduce the number of tardy orders.) Then past due orders will be scheduled. Since the need date is already passed, it will be always try to keep more closer to current date or earliest start date (if it is in future).
  • But if you need to prioritize past due orders, then there’s a toggle in basic data page,  where you can ask MSO to prioritize past due orders.  

Also, ​@FleVidurK can I know the cloud version that you are working with? 25R2 EA & later versions have a more improved version where MSO will reduce the overall tardiness instead of number of tardy orders.