Import Equipment Data
- Last UpdatedJan 24, 2023
- 4 minute read
The Import Equipment Data functionality imports equipment tags, descriptions and other attributes from a CSV or Excel file.
Import Equipment data pre-populates a database with a list of Equipment data from other Engineering data systems. It is not intended for the transfer of data from one project to another. The geometry of the imported equipment is not defined by this method. It is necessary to complete the definition of the Equipment by using the Equipment GUI.
The import is a two-stage process that initially analyzes the import file, reports errors and identifies if the entry is new or appears to exist already in the database. The second stage is to import those entries that the user requires, based on the results of the analysis.
The content of the import file used as the input for this function must follow certain rules, otherwise the data import is rejected by the system.
Note:
The Lexicon Database must be correctly configured, and the supplied values must be valid for
the User Defined Attribute (UDA) being set.
Once the file has been locate, click Open to display the Equipment Data Import window.
Data Import
Use the Data Import window to import equipment tags, descriptions and other attributes from a CSV or Excel file.
At this stage no data has been loaded into the database. The window allows the user to preview the data being loaded from the import file. When the file is loaded, some preliminary analysis of the data is carried out, and the icons, displayed to the left of the table, indicate the result of that analysis.
|
|
Indicates that an Equipment does not exist in the database. If this window is actioned, then the Equipment is created. |
|
|
Indicates that an Equipment already exists in the database. If the Load All Data function is actioned, then attributes of the Equipment are be modified. No action is taken on rows with this Icon if the Load New Data option is actioned. |
|
|
Indicates that the system has identified a problem with this row of data. No action is taken on rows with this Icon when the Load All Data or Load New Data option is actioned. Selecting the row in the table displays a message in the Messages area of the window indicating why the row cannot be processed. Click Load All Data to process all of the rows that create a new element or modify an existing element. Clicking Load New Data option only processes the rows that create new elements. |
New data is created at the current location in the database if an owning element field is not included in the imported file. Note that the owning element is considered to be the current element when the file was loaded and the rows of data analyzed, not the current element when a Load is started. If an owning element field is provided in the import file, the system attempts to create elements under the specified owner.
The Icons on the window indicate the result of the load operation.
|
|
Indicates that the creation or modification operation was successful. An element has been created or modified in the database. |
|
|
Indicates that the operation has not completed successfully because of an error found while the system was attempting to create or modify an element. If an attribute value is incorrect, the element is created, but not all of its attribute data is loaded. Select Undo to remove all of the changes made by the load operation and revert the database back to its state before the load, or to deal with the erroneous elements individually. |
Import files can be loaded by using the File Open Icon, the Browse option or by typing a name directly into the Filename field on the Equipment Data Import window.
Click Reload Data to reload the current file in the Select File field. The user may find this necessary if the current element was incorrect or an owner element was missing when the file was first loaded.
It is possible to load element types other than Equipment using this function. The example above shows User Defined Element Types (UDETs). If the imported file is carefully constructed it would be possible to import other element types provided that fields in the file contain all of the required data. For example, a nozzle list can be loaded provided that the owning equipment name is provided in an Owner field for each nozzle element, and the Type field identifies the element as a nozzle.