The following tasks are used when importing instrument tags and loops.
Enable Creation of Complementary Elements for Instrument Index
If on the Link Definitions dialog, under Import method, the Instrument Index module or instrument index-related table is selected as the import target, the General tab of the Link Properties dialog displays an additional section called Create complementary elements. The options in this section allow you to set the software to import instrument tags according to the instrument type profile definitions. You can enable the following elements for instrument index import:
-
A device panel and a cable for an instrument whose instrument type profile includes wiring, and which has the following default elements: panel, cable, and connection type.
-
A document number row and a default revision row (which is initially empty) in the DRAWING table for a specification, process data sheet and calculation sheet.
-
Instrument associations with the appropriate I/O type, locations and hook-ups.
Set Source Fields as Instrument Type Fields
This procedure is useful if your import source does not contain instrument types or instrument type descriptions and you want to create new instrument types and descriptions in Smart Instrumentation when importing tag numbers. This procedure allows you to define one or more source columns as columns for importing instrument type abbreviations and descriptions. To each field in the source column, you must assign a process function. After that, when you open the Import Link window, you do not have to define mapping for the process function and instrument type fields. The process function macro @PROC_FUNC_NAME appears in the Source Name column mapped to the PROC_FUNC_NAME column. When importing tag numbers, the software runs the macro to import the instrument type abbreviations and descriptions using the fields you set as the instrument type fields and associate the imported tag numbers with the appropriate instrument types.
In Smart Instrumentation, the instrument type of a tag is abbreviated and therefore needs to be associated with a description that provides more information about that instrument type, for example, the default instrument type FV description is Flow Valve. An instrument type abbreviation does not have to be unique. For example, in Smart Instrumentation, FE stands for either Flow Element or Mass Flow Sensor. The combination of the instrument type abbreviation and description provides a unique identifier for a tag instrument type.
Associate Source Fields with Existing Instrument Types
This procedure is useful if your import source does not contain instrument types or instrument type descriptions and all the instrument types and descriptions that you require already exist in Smart Instrumentation. This procedure allows you to set one or more source columns as columns containing instrument type fields and associate each field with a combination of instrument type abbreviation, description, and process function that exists in Smart Instrumentation. After that, when you open the Import Link window, you do not have to define mapping for the process function and instrument type fields. The process function macro @PROC_FUNC_NAME appears in the Source Name column mapped to the PROC_FUNC_NAME column. When importing tag numbers, the software runs the macro and the imported the tag numbers are associated automatically with the appropriate instrument types.
Use this procedure to import instrument tags into Smart Instrumentation using the Module (multiple table) import method. This procedure is useful if you have not yet defined your instrument index in Smart Instrumentation.
Use this procedure to import one or more properties of instrument tag numbers. In this procedure, you use the Single table import method and select the COMPONENT table as the target table for data import. This procedure is useful if you have already created instrument index in Smart Instrumentation and only need to assign certain properties to a large number of existing tag numbers. These properties can be custom field values, supporting table values, or text string properties, such as Service, Note, and so forth.