Shift Monitoring shows a scissors icon and a shorter downtime than the log

[LogicAutomation]

Our press line had a long stop that started at about 21:40 and ended around 22:35. Our shift change is at 22:00. When I open SHIFT MONITORING for the evening shift, the stop is listed with an end time of 22:00 and a duration of about 20 minutes, and there is a small scissors icon next to the end time. When I switch to the night shift, the same stop appears again starting at 22:00, also with a scissors icon.
On the DOWNTIMES page it is a single record of about 55 minutes. Our supervisors are confused because they think the stop was counted twice. Is this a bug, or is the downtime really split between the two shifts? Which number should we use when we compare shifts?

[Technical Support]

This is the intended behavior, and the stop is not counted twice.
What the scissors icon means
SHIFT MONITORING always shows one shift window. When a downtime crosses the shift boundary, the page shows only the part that falls inside the selected shift and marks the cut side with the scissors icon. If you hover over the row, the tooltip shows "Clipped at shift boundary. Full event:" followed by the real start, end and total duration of the record.
So in your example:
- Evening shift: 21:40 – 22:00 (about 20 min, clipped at the end)
- Night shift: 22:00 – 22:35 (about 35 min, clipped at the start)
The two pieces add up to the single 55-minute record you see on the DOWNTIMES page. The same rule applies to the job orders table: a job order running across the shift change shows only the production of the selected shift in "Shift Production", with the scissors icon next to its name.
Which number to use
- To compare shifts, use the clipped values on SHIFT MONITORING (or the By shift view on the REPORT page). Each shift is only charged for the minutes that belong to it, which keeps Availability fair.
- To analyze the stop itself (root cause, total repair time, MTTR), use the full record on the DOWNTIMES page.
The reason is entered only once on the original record, so whichever shift's view an operator uses, the cause appears in both pieces.
Documentation: https://greensoft.ai/documentation/p...ser-interface/