Extracting History Collection Data

Hi,

I have been given the task of documenting a number of modules. To be included in this documentation is the History Collection settings for each module.

I haven't come across a way of exporting this info. It is clearly stored in the database somewhere. Does anyone know how i can get this information without having to manually gather and check each module's configuration.

Any help in speeding up this process would be much appreciated.

Thanks,

6 Replies

  • You can bulk export the historical collection configuration for a node. I believe it is an out of the box format spec file located in the bulk export directory.

     

    Youssef El-Bahtimy | Systems Integration Technologist
    PROCONEX | 103 Enterprise Drive | Royersford, PA 19468 USA
    Proconex Office: 610 495 2970 | Cell: 267 275 7513
    Youssef.El-Bahtimy@ProconexDirect.com

    ------ Click to show quoted text
    Original message ------
    From: superstec
    Date: 2013/11/26 18:49
    To: DeltaV@community.emerson.com;
    Subject:[EE365 DeltaV Track] Extracting History Collection Data

    Hi,

    I have been given the task of documenting a number of modules. To be included in this documentation is the History Collection settings for each module.

    I haven't come across a way of exporting this info. It is clearly stored in the database somewhere. Does anyone know how i can get this information without having to manually gather and check each module's configuration.

    Any help in speeding up this process would be much appreciated.

    Thanks,

     
  • What are you using at the moment:  Legacy Historian (PI) or DVCH?  History collection settings for all  DeltaV control modules that exist in the active database are stored in a file called PHIST.scr (the one you are after is the one in the Historian server itself).  Can be opened using Notepad (and hence can be placed in an Excel spreadsheet).  Alternatively, if you have PI Datalink, you can query the tag attributes of each History Collection tag as well.
     
    From: superstec [mailto:bounce-superstec@community.emerson.com]
    Sent: Wednesday, 27 November 2013 12:50 p.m.
    To: DeltaV@community.emerson.com
    Subject: [EE365 DeltaV Track] Extracting History Collection Data
     

    Hi,

    I have been given the task of documenting a number of modules. To be included in this documentation is the History Collection settings for each module.

    I haven't come across a way of exporting this info. It is clearly stored in the database somewhere. Does anyone know how i can get this information without having to manually gather and check each module's configuration.

    Any help in speeding up this process would be much appreciated.

    Thanks,

  • Slight clarification:  Alternatively, if you have PI Datalink, you can query the tag attributes of each History Collection tag as well.
     
    Only if you are using Legacy Historian with DeltaV.
     
    From: fabuid [mailto:bounce-fabuid@community.emerson.com]
    Sent: Wednesday, 27 November 2013 1:52 p.m.
    To: DeltaV@community.emerson.com
    Subject: RE: [EE365 DeltaV Track] Extracting History Collection Data
     
    What are you using at the moment:  Legacy Historian (PI) or DVCH?  History collection settings for all  DeltaV control modules that exist in the active database are stored in a file called PHIST.scr (the one you are after is the one in the Historian server itself).  Can be opened using Notepad (and hence can be placed in an Excel spreadsheet).  Alternatively, if you have PI Datalink, you can query the tag attributes of each History Collection tag as well.
     
    From: superstec [mailto:bounce-superstec@community.emerson.com]
    Sent: Wednesday, 27 November 2013 12:50 p.m.
    To: DeltaV@community.emerson.com
    Subject: [EE365 DeltaV Track] Extracting History Collection Data
     

    Hi,

    I have been given the task of documenting a number of modules. To be included in this documentation is the History Collection settings for each module.

    I haven't come across a way of exporting this info. It is clearly stored in the database somewhere. Does anyone know how i can get this information without having to manually gather and check each module's configuration.

    Any help in speeding up this process would be much appreciated.

    Thanks,

  • Use the bulk edit file "HistoryDataPoint_NonModule.fmt" on the entire database to perform a user defined export. This is available as system default in the DVDATA/Bulk Edit folder.

  • In reply to amodbobade:

    Detailed description:

    1. Select the top level of the Database in DV Explorer.  Select file-->export-->user defined

    2. Select Search Results.  Pick Search Results and Next.

    3. In the find dialog Select  Control Module from the Type field and select find. (If you need to see historization for anything other than control modules, change this search criteria).

    4. Highlight the entire list (click the first entry, and press ctrl+shift+end) and press select.  This will take a few minutes.

    5. From the Format Source  dialog, Select the  HistoryDataPoint.fmt  or HistoryDataPoint_NonModule.fmt file. Select next.

    6. From the export target dialog, select a new file to create. Select next and export.

    7.  The output file will populate.  Open the new file in excel or access for post processing.

  • In reply to Youssef.El-Bahtimy:

    HI,

    Thanks for the help on this. I wasn't aware of that .fmt file. Did the trick.

    Thanks to all who contributed YesYesYesYesYesYesYesYesYesYesYesYes