Record Alarm Setpoint history in external database (PI?)

I've got a customer, that wants to have their alarm setpoints (H, HH, L, LL, etc.) from System Platform and Enterprise SCADA (they run both) stored in PI, or some other external database. They also want to keep a history of these setpoints. I'm assuming I can expose these via OPC DA and pull them in with a PI interface, but that would be an insane amount of tags for data that rarely changes. The only alternative I can think of is periodically querying the SQL backend and saving anything that's different. I don't know if there's a way to say "give me all setpoints changed since x time". Has anyone done this before? Any ideas how I can accomplish it? Thanks!

Parents

0 RAINER CARLTON DSOUZA 20 days ago

Hi Damon, I’m familiar with System Platform and Pi , so I’ll give my idea based on this and same could be replicated to Enterprise SCADA. You can write the alarm in System Platform to trigger a REST API put request into Aveva Pi using Pi System Access . This will be event driven. Within System Platform embed the alarm to provide setpoint in the alarm comment. Using Pi Asset framework you could pick this element . All the above can be done using templates and then easily do instances from them
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 RAINER CARLTON DSOUZA 20 days ago

Hi Damon, I’m familiar with System Platform and Pi , so I’ll give my idea based on this and same could be replicated to Enterprise SCADA. You can write the alarm in System Platform to trigger a REST API put request into Aveva Pi using Pi System Access . This will be event driven. Within System Platform embed the alarm to provide setpoint in the alarm comment. Using Pi Asset framework you could pick this element . All the above can be done using templates and then easily do instances from them
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

0 Damon Vinciguerra 19 days ago in reply to RAINER CARLTON DSOUZA

Hey RAINER CARLTON DSOUZA , thanks for the quick response. REST API trigger is interesting! But are you suggesting that I trigger the REST API when an alarm happens? I'm afraid if I rely on alarms, I may get stale info or even no info in some cases. If a certain tag just happens to never alarm, I'll never get the setpoints. Or say someone changes an alarm setpoint in September, but it doesn't alarm until October, I wouldn't know about it until October.

Is there a way to trigger a REST API call when an alarm setpoint is changed?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 RAINER CARLTON DSOUZA 19 days ago in reply to Damon Vinciguerra

Hi Damon, I’m suggesting you trigger an event and REST API in System Platform ( non priority alarm ) when there is a change in alarm setpoint
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 RAINER CARLTON DSOUZA 19 days ago in reply to RAINER CARLTON DSOUZA

We do this a lot of times for auditing and tracking Sequence of events
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Damon Vinciguerra 16 days ago in reply to RAINER CARLTON DSOUZA

RAINER CARLTON DSOUZA , I gotcha, yeah, that sounds exactly what I'm after! I apologize for the delay, I was trying to figure out exactly how to implement this in System Platform. I can't find any literature on triggering off of alarm setpoint changes. Is it Log changes? Or something else? Thanks
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 RAINER CARLTON DSOUZA 15 days ago in reply to Damon Vinciguerra

Hi Damon, so it’s not a out of box feature, you will need to write a script using two attributes, say A as real variable , B as digital variable, if setpoint is not equal to A , trigger B , wait for 5 seconds and then make B =0 , Copy A to B , Done . use variable B as rest client by enabling I/O and pointing to Web services OI server
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel