AnsweredAssumed Answered

Avoid Saving Values at Same Timestamp, Instead Save at Next Available

Question asked by AlexPoe on Oct 11, 2018
Latest reply on Mar 11, 2019 by AlexPoe



To preface my question, we have 5 alarm PI tags for our system. These tags are being populated with values from our EMS. From those alarm tags, I am using the Analysis function for String Search (InStr) to find specific alarms that are then used in some filtering equations I have set up. Essentially, if there is maintenance work going on, then there will be an alarm that comes in before the circuit gets de-energized. I have alarms set up to send alerts when circuits are de-energized and I am using the alarms to filter out the planned outages.


The issue I'm having is that it is entirely possible (and common) to receive multiple alarms at the same timestamp, even down to the millisecond level. The way our interface and tags are set up is that it saves all of those values at the same timestamp. The functions for the analysis are only able to handle one value per timestamp (KB01667). Thus, if there is an alarm I want, but is stored at the same timestamp as another, the one I am looking for is ignored by the analysis, and as a result I get an alert for an outage that was planned.


I've done some looking and found a discussion on maybe changing the config to ARCAPPEND or something like that, but I haven't been able to quite understand how to implement it (How to avoid two values with same timestamp ).


Ideally, what I want it to do is to check if a value exists at that timestamp, then if one does, it will add one millisecond and try again. Is that doable via a setting change somewhere? Or would I need to use some other method such as PI ACE?


Any help would be appreciated, I'm fairly new to this Admin role so I'm still trying to learn all the ropes with the configuration stuff.