Process History View Export

Hi,

At present we are exporting our process history view as an XML file at the start of each month. This is to assist with operations and their alarm management.

At present we use a the manual export at the start of each month to gather the previous months data. Would it be possible to automate this, either through Process History View, or through another method?

I’ve explored books online but can’t seem to find a way to carry this out.

 

Thanks.

 

Mike.

 

  • I believe the proper way is to use OPC Events Server. See PDS:

    www2.emersonprocess.com/.../PDS_OPC_EventsServer.pdf

    The other proper way is manually like you do now.

    A semi-automated way is to enable the automatic export option for A&E's and automatically process the exported data-files.

    The not so proper way is extract the data straight from the SQL server (DELTAV_CHRONICLE), but I'm not sure atm if you need the right login details to access the database. Also a correction for the time-zone may be needed.

  • In reply to Robert Rijnders:

    Process History View is just a project of a data from MS SQL database, see DELTAV_CHRONICLE instance. You could do it from there if necessary.

    Another option is to use to DeltaV Excel Reporter. You can probably create a VBA macro that can pull everything from that interface.

  • In reply to Lun.Raznik:

    The 'Export Alarm Summary to XML' button on the alarm list fires a application called 'AlarmSummaryUtility.exe' in the DV/bin folder. This program has many options (see /?). A simple command like: AlarmSummaryUtility.exe 100 /export will export the 100 most important alarms to a file. The resulting file can be timestamped, converted to Excel and compressed. Can be done in a windows batch file which can be scheduled as well.

    Also on the LinkedIn group there is a discussion about this topic. The suggestion there is to use XLReporter.

    www.linkedin.com/.../Im-looking-way-capture-DeltaV-1270757.S.46220538

  • In reply to Robert Rijnders:

    The DeltaV Analyze product provides many alarm analysis features, and is layered on the Event Chronicle database.  Data can be analyzed in many different ways, including by Operator.  

    Analyze continually polls the Even Chronicle to determine how long alarms are active, the time to acknowledge, the frequency of alarms and the alarm load on operators.  The data is read and analyzed before being stored separately form the Event Chronicle.  IT comes with standard reports for bad actors.

    The Export Alarm Summary to XML uses the local alarm summary of the workstation and will be based on the currently logged on User's span of control.  This is a good tool to view the standing alarms at an Operator station at any given time.  But as alarms are acknowledged and go inactive, they drop of this list.  The Event Chronicle is the permanent record.

    A search of the Event Chronicle database reveals many alarm state messages, ACT/UNACK, ACT/ACK, INACT/ACK, INACT/UNACK, SUPP, etc. You have to look at all of these to know how an alarm behaved and how many alarms were active at any given time.  DeltaV Analyze does all of this for you and based on the plant Areas, can report on any workstation or Operator's alarm load.  

    www2.emersonprocess.com/.../PDS_DeltaV_Analyze.pdf

    Andre Dicaire

  • In reply to Andre Dicaire:

    Wow - Wasn't expecting such quick replies. I'm going to investigate using XLReporter as a potential way of resolving this as it is something that we use quite regularly but for some reason I never even thought of utilising this!

    I'll also try and do a bit more digging on the AlarmSummaryUtility.exe to see if I can knock up a little script to do what we need to do.

    Really apprecaite everyones help!

    Thanks!

  • In reply to Robert Rijnders:

    After a bit of further research it would seem that the AlarmSummaryUtility.exe requires a few more parameters to be defined before it will work. I have managed to get it working in a fashion but not to the level that I would like. I have access to all alarms and windows destop but cannot get the alarm summary working via this method. The information given seems very limited on this (but then its not a program normally run!). I may have to go down the XLReporter route to see if I can get this automated.

  • In reply to myk:

    Great problem solving. Thanks, Robert, Lun, Andre, and  Mike!

    Best Regards,

    Rachelle McWright: Business Development Manager, Dynamic Simulation: U.S. Gulf Coast