Skip to main content

Hi,

We had a set up like below on our routings. There were 2 operations – first extruding, second packing. As we did not want to report each operation separately so we chose milestone operation - when we reported second operation the first one was automatically reported.

As extrusion and packing usually happens parallel we changed the parameter on second operation into parallel.

 From that moment automatic reporting of previous operation stopped working. To solve the issue we started using ‘Auto report of operation parameter’ when we completed into stock.

The problem appears if we add one more operation to above connected to finishing. We would like to  have operation first and second reported when we report second operation. However because of parallel parameter operation first is not reported. It is reported when the last (third) operation is reported .That causes issues – especially that components are not buckflused when consumed. Is there any way to solve it?

Best regards,

Bernadeta

The Milestone flag is designed to force consecutive reporting. I.e. if you have two non parallel operations you cannot report that you have completed more on the second than completed on the first. However if the second operation is parallel to the first it means it can be completed without being dependent on the WIP from the first operation. Hence, selecting the Report Previous Operation option on the second operation will and should not report the first operation in the parallel scenario.

If you have a third operation that is not parallel it indicates it needs the WIP from both first and second operations. Hence, reporting previous operation on this will auto report both first and second operation if not already reported. 

So there’s not really any option to auto report first operation when reporting the second operation when it is set to be parallel with the first one. And in my opinion there should not be any such option if they are truly independent.

What you can evaluate is whether the operations should rather be defined as overlapping instead of completely parallel? In below example I have defined an overlap of 50% on the second operation. It means it is scheduled to start when first operation has reach 50% of its duration.

 

Reply


Terms & ConditionsCookie settings