The options on this tab allow you to import source tables defined per plant hierarchy item (for example, per <plant> or per <unit>) when your target domain contains more than one plant hierarchy item at a particular level.
As Smart Instrumentation tables are defined per plant hierarchy item, these tables contain data unique on a specific level. For example, the CABLE table is defined per area; therefore, this table contains data unique only on the area level of the domain.
When importing from a domain containing more than one plant hierarchy item, some of the source rows may recur due to the existence of several plant hierarchy items. In this case, you can set your import link properties so that the Import Utility differentiates the rows of different plant hierarchy items, thus importing the data into the appropriate plant hierarchy items.
Hierarchy levels
You can also specify the plant hierarchy level when importing data into additional plant hierarchy item if your domain includes more than one <plant>, <area>, and <unit>.
Apply
Enables you to select a hierarchy level. If you do not select any hierarchy level, the Import Utility rejects all the recurring source rows, as it does not differentiate between the rows of different plant hierarchy items. The Import Utility also rejects all the recurring rows on the plant hierarchy levels that is lower than your selection if you import data on the highest plant hierarchy levels.
Data import level
Select the plant hierarchy level at which you want to import data, for example, plant, area, and unit. All recurring rows on lower hierarchy levels will be rejected.
Import unit data using
Unit number
Allows you to use the unit number data column as the key for importing data.
Unit name
Allows you to use the unit name data column as the key for importing data.
Specify target projects in link
Allows you to import data into several projects at a time if the current domain type is Owner operator. In the Import Link window, if your import method is Single table, when defining target table definition, you must provide the table definition for the ENGINEER NAME/ENG PROJ ID field in the Target Name column; if your import method is Module (multiple tables), when defining target table definition, you must provide the table definition for the Engineering Project Name field in the Target Name column. Also, make sure you define the correct hierarchy levels for data import.