This ties into this old thread I did not want to reopen: https://emersonexchange365.com/products/control-safety-systems/f/deltav-discussions-questions/169/exporting-data-from-delta-v
Since DeltaV 12 the MODULEAREA user-defined export improves the export of a large number of modules. Since DeltaV 13 there have been multiple improvements to SAM and now we also have Module_Alarm.fmt and Module_Alarm_ClassBased.fmt which allow a new style of alarm exports, with one alarm per line, instead of one alarm attribute per column of a module export.
What are the current best practices to export alarms from DeltaV? Assume alarms are defined in class-based modules similar to PCSD.
I ran into the following issues:
1. System Alarm Management struggles to load all alarms within an area. It does work for a Unit, and Print to XML produces usable output, but no possibility to reimport.
2. When trying to use User-Defined Export and I search for all objects of Type "Alarm", I get an endless stream of Component Not Found error messages.
Is there some kind of format file similar to the MODULEAREA where I am able to use "Children of Selected objects", select just a few areas, and produce one export for a lot of alarms?
Which format file would you use and how would you produce an export in an efficient way?