• Not Answered

Bulk exporting all modules using a specific class

So I currently need to have all of the modules in a system exported and sorted by class. The only way I can see to do this is to go to each process cell and select the modules with each class and export them incrementally for each class and process cell. Is there a way that I can pull all of the modules that use a specific class or a parameter to export so I can export all the modules at once and sort them in excel?

4 Replies

  • Unfortunately there really isn't an easy way to get what you want exactly as stated. Depending on the size of your database, if it is not real big you can select all from all areas by using Select All but if you have a large database it will have issues and you will have to do it by area or couple areas at a time.

    You can export everything selected and even if it doesn't fit in that format file for the class it will still export. Then you can sort afterwards and remove the modules that don't fix. You can use the Sub_Type, FP or other columns that will have <NULL> which means that the item doesn't have that to sort on and make the removing of the items that didn't fit easier.

    If you are doing multiple exports with different formats, click the back button a couple times after the first, select new format and data files and export again. This way you don't have to go thru all the selection again.
  • You can try doing a search from DeltaV Explorer, set the Object Type to "Control Module", select the "Advanced" button, Set Property to "Type" and Value to the string that conforms to the specific class you are looking for. Het the "Add to List" button, and hit "Find Now", the results of the search can be saved or printed. You can do something like this for parameter searches. It's a quick way to dump lists of certain things.

    I set up an export template that has just the basics Module Name, Description, path, class, type, subtype, detail display .. and will run that to get a summary list some times as well.

    There is a way you can do this by dumping the FHX to XML and writing a script but that takes a little time to set up.
  • In reply to MPHymel:

    No way to do it directly, but I have written VBSCRIPT in the past to process a database fhx export which splits and separates each module in to its own fhx. As well spit out a spreadsheet which contains class name as a parameter.

    Took a little bit of time, but it worked really well.

    Good Luck!!

  • In reply to Richard Bruce:

    Hopefully I understand the request correctly.

    I think the only deterministic method of getting this information is with some utilities that were out there in the past or some vb scripting on a fhx file.  I have found that if the configuration is setup well and used consistently, you can get a very good idea from the bulk edit utility, but this infers the class from the module subtype field.  So, if standards weren't well defined and followed, it will not be 100%. 

    Ideally, Emerson will eventually make "Class Parent" a field that can be used as search criteria as well as a field that can be exported along the module (similar to type / subtype).  At least on v13.3.1 I'm not sure how to do that.  But as Class Modules have been out 15 years, I think it is type to make some improvements the bulk edit tool.

    On systems I've supported, I've normally done at least these two things.

    1. CM Listing that provides basic data for all CMs in the system.
    2. CM Listing by SubType with fields specific for that module type.  If things are done correctly, the subtype should reference the Class Parent name (at least in my opinion).

    For the CM listing, I use a simple Format file with module_name, area, description, type, subtype, and scan rate.  

    To report out all CMs associated with a class using bulk edit, I use a User Defined Export with "Search Results" selected. 

    In the Find Dialogue, Select Control Module as Object Type, select "Advanced" button and enter advanced search options.  For the advanced options, select SubType for the Property, Matches for the Condition, and then the text from the SubType field for the modules in that class.  Once you complete the search, select all items in the list and export with a Format specification developed for that module type.