• Replies 18 replies
  • Subscribers 582 subscribers
  • Views 1181 views
  • Users 0 members are here
Options
Related

[Alarm Summary] How long can save alarms ?

Anton

From the time I started work with Citect in 2010 I remember in Wizard was a parameter "Summary length" in rows (how much alarm can be in Summary? for example we set 10 000, 10 001 alarm will replace the oldest) but in production we want to save alarms in time period ( 3 months or 2 years).

By the reason we didn't use Summary

We used (and using right now) alarm log on web technology: apache + php + SQLite (via ODBC)/ We call it ALARM LOG. At the alarm log page we use an ActiveX element Microsoft Web Browser to display alarms fron our archive/log.

QUESTION: Does Citect in 2019 have any build-in instrument to log/archive alarms for configured period (for example 3 months or 2 years)?

In Citect 2015 help I don't see any descriptions about alarm summary ...... but in Citect 7.1 I remember it was .....

Parents
  • Hi Anton,
    With the change in alarm architecture in V7.30, there have been some subtle changes. It is correct that alarm summary length is no longer available. You can only configure the period after which the alarm history is archived or remains in memory.
    You are also correct that if an alarm has been acknowledged and transitions to off state, it will be removed from the active alarm list. You can still access the alarm history by visiting the Alarm Summary or Alarm SOE page. I'd recommend disabling the alarm summary and just using the SOE page, unless you have specific requirements that only the Alarm Summary can deliver.
    There are a number of ways to log alarm history to another database or archive. A Historian is indeed one solution. Another is custom code to read alarms form the alarm event queue and insert into SQL database. You can also just use Alarm Log device, like you mentioned, which points directly to SQL DB.
Reply
  • Hi Anton,
    With the change in alarm architecture in V7.30, there have been some subtle changes. It is correct that alarm summary length is no longer available. You can only configure the period after which the alarm history is archived or remains in memory.
    You are also correct that if an alarm has been acknowledged and transitions to off state, it will be removed from the active alarm list. You can still access the alarm history by visiting the Alarm Summary or Alarm SOE page. I'd recommend disabling the alarm summary and just using the SOE page, unless you have specific requirements that only the Alarm Summary can deliver.
    There are a number of ways to log alarm history to another database or archive. A Historian is indeed one solution. Another is custom code to read alarms form the alarm event queue and insert into SQL database. You can also just use Alarm Log device, like you mentioned, which points directly to SQL DB.
Children
No Data
© 2025 AVEVA Group Limited or its subsidiaries. All Rights Reserved.