Alarms Export to Excel

Good day everyone, I trust you are well. How can one archive the process of downloading a list of configured alarms Current/Historical alarms data from Aveva HMI (Managed App, Version: 2017 Update 3, OS: Windows 10Pro, using Rockwell's Allen Bradley Compact Logix PLC as control system),
Can this be achieved, is there a script?
The client would like to download these alarms to excel.
Thanks.

Parents
  • Moises,

    Trying to make sure we understand your question, are you trying to capture the configuration or the actual historical alarms? 

  • Hi Scott and  thanks very much for your feedback, according to the client they are trying to download the total alarms configuration file in excel possibly, and the actual historical alarms too. The reason is that, as part of industry standard for alarms management, they need to perform a rationalization exercise for all configured alarms and perform daily bad actor analysis. For these exercises to be possible we need to extract all configured alarms and be able to also export daily alarm logs to an excel worksheet for analysis. 

  • Thanks for clarifying.

    As mentioned, the best approach would be to set up logging to a database, this will allow for many ways of analyzing the alarms based on the customer need.

    If you have AVEVA Historian in your setup it is fairly simple in the later versions, where integration with Historian is built in to the configuration and supported by the alarm components for historical retrieval.

    And you could log the necessary context to make analysis easier (batch start and stop time, equipment state and so on).

    But if Historian is not an option, you could also check out the Alarm DB Logger Manager utility, this will save all alarms (and events) to a database, where analysis can be made based on the data saved.

    A third trick would be to save all alarms to a csv file using the Alarm printer utility.

    But there is no built in option, to export data visible in the alarm component, that will export the content to a excel file.

    As mentioned I have created some applications that keep track of the Query used in the alarm component, such as start and stop time, any filter etc. and the based on this, apply the same filter options as a Query against the alarm database, exporting data to a file for analysis.

    Also it is possible to get data from a row in the alarm component, and there might be some additional ways using scripting, perhaps some one else has some idea, since there are some undocumented script commands available in the alarm component.

Reply
  • Thanks for clarifying.

    As mentioned, the best approach would be to set up logging to a database, this will allow for many ways of analyzing the alarms based on the customer need.

    If you have AVEVA Historian in your setup it is fairly simple in the later versions, where integration with Historian is built in to the configuration and supported by the alarm components for historical retrieval.

    And you could log the necessary context to make analysis easier (batch start and stop time, equipment state and so on).

    But if Historian is not an option, you could also check out the Alarm DB Logger Manager utility, this will save all alarms (and events) to a database, where analysis can be made based on the data saved.

    A third trick would be to save all alarms to a csv file using the Alarm printer utility.

    But there is no built in option, to export data visible in the alarm component, that will export the content to a excel file.

    As mentioned I have created some applications that keep track of the Query used in the alarm component, such as start and stop time, any filter etc. and the based on this, apply the same filter options as a Query against the alarm database, exporting data to a file for analysis.

    Also it is possible to get data from a row in the alarm component, and there might be some additional ways using scripting, perhaps some one else has some idea, since there are some undocumented script commands available in the alarm component.

Children