Alternatively to nexidator's hint (one cycle is finished after two parts) you can also use two instances of the Cycle Time Assist add-on and measure both lines independently.
For both solutions you have to keep an eye on the invalid cycles to get a plausible result in the diagram.
Solution 1 (one CTA add-on): If only one part is produced due to missing parts, it is an invalid cycle because it is probably faster than processing two parts.
Solution 2 (two CTA add-ons): If only one part is produced, one instance has a regular cycle and the other instance has an invalid cycle due to missing part.
Handling invalid cycles with the CycleTimeAssistInvalidReasons enum is for example done in the example project Digital Machine: https://developer.bosch.com/products-and-services/sdks/nexeed-automation-downloads/controlplus#samples/digitalmachine
In this project there is also made a difference between TargetCycleTime of Cycle Time Assist (which is the real target cycle time) and the TargetCycleTime of Part Counter (which is actually just an average target cycle time, that means TargetCycleTime x TargetOEE).
... View more