With the built-in ACT_STEPS and ACT_TRANS parameters, what have you all found to be the best way to enable history collection for these? The ability to trace phase paths after the fact is a tremendous boon to troubleshooting bugs, I'm just trying to wrap my head around the best way to build the historian tags. I had hoped I could find a UNIT_NAME/PHASES[x] type parameter, similar to UNIT_NAME/ALARMS[x], but I've been unsuccessful. I'm trying to avoid needing to manually build a tag for every UNIT/UNIT_PHASE combination in the database, not sure if there's something I'm missing or not. Right now my planned solution is to build a classless CM with a dynamic reference to each unit/unit phase ACT_STEPS and ACT_TRANS parameter, with an action block that will conditionally bind the reference if the phase is in memory. When the phase is not in memory, it'll bind to a dummy 0 to keep the trending and memory usage tidy. The history collection will actually be tied to the parameters within this CM.
Has anyone else done something like this?