[Alarm Summary] How long can save alarms ?

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,
    I'm not sure I understand your question. Can you please clearly state what feature and functionality you require for alarm archive?
    Within the product, there is native alarm archiving within the alarm database (actually the ClearSCADA database). The time the alarm archive remains is controlled via citect.ini parameters as mentioned previously. The alarm history is accessible via standard alarm pages (like SOE or Alarm Summary page) and you can also query the alarm database via SQL type query (see the Example project "Database Access" which demonstrates this capability). There is also the ability to hook directly into the alarm event queue and do anything you want with the information (forward to another database). You mention Process Analyst, it is also capable of displaying the alarm history. So there are lots of options and flexibility in the product. It isn't clear what is missing from your description.
Reply
  • Hi Anton,
    I'm not sure I understand your question. Can you please clearly state what feature and functionality you require for alarm archive?
    Within the product, there is native alarm archiving within the alarm database (actually the ClearSCADA database). The time the alarm archive remains is controlled via citect.ini parameters as mentioned previously. The alarm history is accessible via standard alarm pages (like SOE or Alarm Summary page) and you can also query the alarm database via SQL type query (see the Example project "Database Access" which demonstrates this capability). There is also the ability to hook directly into the alarm event queue and do anything you want with the information (forward to another database). You mention Process Analyst, it is also capable of displaying the alarm history. So there are lots of options and flexibility in the product. It isn't clear what is missing from your description.
Children
No Data