Skip to main content

Concurrent Operations in Parallel when more than one OP is in the clocking seq

  • September 29, 2026
  • 2 replies
  • 8 views

Manxmano
Sidekick (Customer)
Forum|alt.badge.img+7

We have noticed a possible change to the way that concurrent OPs functionality works in Cloud 25R1 compared to Apps 10. The change creates an inefficiency with the shop floor. It is apparently a change from Apps 10 but this might just be people remembering differently.

When several OPs are selected on SFW and Start Production is clicked, a clocking is started for both OPs with one clocking seq ID.

Then, in the same work center, another two OPs are selected and Start Production is clicked again. On the message that pops up regarding concurrent OPs, if you select run in parallel, Cloud stops this and the error message says “Overlapping clocking sequences are not allowed when more than one operation is connected to the sequence”.

 

If you choose the replace option, the clocking is stopped and a new clocking seq started, this is not a problem. 

The error message is only when you want to run the two sequences in parallel.

Has anyone else noticed this and how did you resolve it. Is it a bug or has IFS changed the functionality around concurrent OPs?

2 replies

Björn Hultgren
Hero (Employee)
Forum|alt.badge.img+25

I don’t think this should have been changed from apps 10 to IFS Cloud. Remember that the behavior when selecting and starting multiple operations together in workbench depending on the Concurrent Operations setting on the work center. if you change it to Group Start in Parallel, the logic will handle create separate clocking sequences for each clocking, and instead of distributing the total elapsed time between the clockings, the crew size (for labor) and resource share (for machine) will be split instead.

 


Manxmano
Sidekick (Customer)
Forum|alt.badge.img+7
  • Author
  • Sidekick (Customer)
  • September 29, 2026

Thanks ​@Björn Hultgren , the work centers are all set as Concurrent Operations: Allowed - Group Start in Sequence.

The wording between Group Start in Sequence and Group Start in Parallel is very subtle.

But I now see the difference. Group Start in Sequence uses a single clocking seq for all the clockings started simultaneous.

Group Start in Parallel assigns a unique clocking seq IDs to the OPs started in parallel.

And Group Start in Parallel does allow what I want. Thank you!