Could you expand on why you prefer transaction groups over tag histories for this use case?
I’ve found a couple different use cases for different scenarios. For example, when I am looking to calculate event duration, downtime, etc. on a line or area involving more complex logic to define the event, I prefer to use UDTs and transactions groups. However, if I am only interested in the event duration of a single machine instance; I’ve found point count query bindings of 1 with an aggregation mode of duration on/off to be reliable or alternatively I’ve have been using jython script transforms to do the same for different dashboard scenarios.
To add context: I’m new to SCADA, new to Ignition, new to anything OEE, and generally new to the OT space. I’m mostly working in piecemeal on downtime dashboards and I am at a crossroads now moving forward with a more systemic approach. Using UDTs/Transaction Groups to write event data to normalized downtime tables is probably where I will land long term. It seems to allow me the most flexibility to incorporate planned DT reasons, schedules, etc.
But, I am just curious if there are additional performance issues I should be aware of with tag history bindings and script transforms.
Thanks for your help!