+5We have started testing MSO and many questions are coming up. One of the questions is whether MSO supports the scheduling of parallel operations. From the initial results, it seems that it does not. Is there a parameter that needs to be set somewhere to enable this? The testing was done in the 25R1 environment.
Best answer by Lakshan Thiranagama
We have started testing MSO and many questions are coming up. One of the questions is whether MSO supports the scheduling of parallel operations. From the initial results, it seems that it does not. Is there a parameter that needs to be set somewhere to enable this? The testing was done in the 25R1 environment.
Hi, In MSO parallel scheduling requirement can be considered as a soft constraint (scheduling goal) and also as a hard constraint (Scheduling rule). When below shown toggle is enabled, MSO will consider the parallel scheduling requirement as a hard rule. And when it is disabled it will not be considered as a rule and it will try to achieve it while fulfilling all other scheduling parameters required to consider when creating a finite schedule. Below image shows how it looks in Finite scheduling basic data page in IFS Cloud version 25R2.
Thanks!
+3
Based on my past experience with MSO, parallel operation scheduling is supported, but there are some important considerations and setup requirements to be aware of. The company i work for doesn’t have manufacturing, so this is based on memory - you should keep that in mind because I might not be remembering correctly.
Key points in parallel operations in MSO:
• Routing Setup: Make sure your routing operations are configured with the correct precedence relationships. Parallel operations should have the appropriate predecessor/successor linkages that allow them to run concurrently.
• Resource Constraints: MSO will respect resource availability - if parallel operations require the same resource, they obviously can't run truly in parallel. Ensure that the parallel operations use different resources or resource groups.
• Work Center Configuration: Check that your work centers support concurrent operations if that's part of your setup. I believe that there have been recent enhancements around work center concurrent operation handling in MSO.
Troubleshooting Steps:
If you're still seeing sequential scheduling when you expect parallel operations, I'd recommend checking the specific routing setup and resource assignments for those operations. The MSO engine should handle parallel operations naturally when the constraints allow for it.
are you seeing any specific error messages or warnings in the MSO scheduling results?
-jason
+5Thank you for your response.
I believe that the operations are set up correctly. The operations are performed by five different labor resources at one work center/resource . The resource is divided in a ratio of 1/5, and the initial planning into infinite capacity is correct. The APB also schedules the operations correctly.
I was interested in the following remark:
“ Resource Constraints: MSO will respect resource availability - if parallel operations require the same resource, they obviously can't run truly in parallel. Ensure that the parallel operations use different resources or resource groups.”
Why is that? If I have a work center (an assembly workshop) where multiple labor classes work simultaneously (mechanic, electrician, painter, etc.), there is no other option than to define multiple operations for one work center with different labor classes. This is a common requirement in manufacturing.
I've been working with MSO for a short time, it's more or less new to me, so I'm discovering the possibilities and limitations. Unfortunately, I've found that sometimes MSO doesn't schedule the operation and doesn't even display the reason.
+7We have started testing MSO and many questions are coming up. One of the questions is whether MSO supports the scheduling of parallel operations. From the initial results, it seems that it does not. Is there a parameter that needs to be set somewhere to enable this? The testing was done in the 25R1 environment.
Hi, In MSO parallel scheduling requirement can be considered as a soft constraint (scheduling goal) and also as a hard constraint (Scheduling rule). When below shown toggle is enabled, MSO will consider the parallel scheduling requirement as a hard rule. And when it is disabled it will not be considered as a rule and it will try to achieve it while fulfilling all other scheduling parameters required to consider when creating a finite schedule. Below image shows how it looks in Finite scheduling basic data page in IFS Cloud version 25R2.
Thanks!
+5
Thanks for the answer. MSO finally scheduled the operations correctly, but the last operation is in the unscheduled state with a short but not clarifying text why the operation was not scheduled - “MSO could not schedule this operation”
Is there a way to find out why MSO did not schedule the operation? Some kind of log?
+7
It is great that you could get them scheduled in Parallel.
You can find the reason for unscheduled operation from PSO workbench. If you are using MSO in Automatic scheduling mode this can be scheduled automatically after certain amount of time since MSO is going continuous optimization in that mode.
But if you are using Manual mode you can try to increase the schedule acceptance quality parameter value to 100 and increase the Generate schedule within time interval. If still it is not scheduling feel free to get support from IFS Support. By configuring MSO advanced parameters you can easily optimize this however in order to do that you need to get help from a MSO/PSO expert.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
