Skip to main content

Dear all, 

We are facing an IFS behaviour we actually can’t deal with. 

We have routings with “not parallel operation” folowing each other. 

Some of the “not parallel operations” have “parallel operations” connected to them. 

If the “non parallel operation” is closed, a new scheduling of the shop order will move the non closed “parallel operations” to another “not parallel operation”, which is completely modifying the sequence of work. 

 

Is there any way in IFS cloud to take into account the presence of a “non parallel operation” during a Shop order scheduling, even if this “not parallel operation” is closed ? 

The parallel operation should execute in parallel with the previous open operation regardless of if it is parallel or non- parallel. If you have a non-parallel operation preceding the parallel operation it would act like the next sequence until it is closed and then the parallel would be parallel with the next previous operation. I believe this is what you are describing. As such the parallel operation would appear resequenced because the full quantity in the next sequence parallel operation would be available to report regardless of what was reported in the previous operation. 

Exactly how you see this would depend on what screen you are using or how you are filtering or sorting in the various screens in IFS. 

I would try to solve this a few different ways. 
1. Try setting the milestone flag on the non-parallel operation and see if it maintained the sequence

2. Leave the operation open until all the parallel operations are complete

These options my introduce unwanted consequences depending on the details of your operation reporting, but most of those consequences can be managed through backlash operations or custom events to close the non parallel operation after the last parallel operation is complete  


 

 

Reply


Terms & ConditionsCookie settings