Importing Data into Multiple Plant Hierarchy Items or Projects - Intergraph Smart Instrumentation - Help

Intergraph Smart Instrumentation Help

Language
English
Product
Intergraph Smart Instrumentation
Search by Category
Help
Smart Instrumentation Version
13.1

You use the Import Level tab options to import source data to a domain with multiple plant hierarchy items or to an owner operator domain that has As-Built and multiple projects. In your import source, you need to define the projects names and the plant hierarchy items exactly as they appear in your target domain. In an owner operator domain, projects are always implemented per <plant>. Several projects can be associated with the same <plant> and even share the same hierarchy levels or belong to different plants in the domain.

When importing data that includes 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 instruct the Import Utility to differentiate rows of different plant hierarchy items during the import process, thus importing data into the appropriate plant hierarchy items. When you select to import data into multiple plant hierarchy items, you can also specify the level of import, for the Import Utility to differentiate rows per <plant>, per <area> or per <unit>.

If you select to import data per <plant> or per <area>, the Import Utility rejects rows defined per <unit>. If you do not specify a plant hierarchy level, the Import Utility rejects all recurring source rows during the import process. In this case, the Import Utility does not differentiate between rows of different plant hierarchy items. After you select the level for which the Import Utility distinguishes unique data during the import process, you need to select the naming convention to be used during the import process.

In Smart Instrumentation, database tables are defined per plant hierarchy item. When a table is defined at a specified level, it contains data which is unique at that level.

Data Import at the Highest Level

If you select to import data per <plant>, the Import Utility distinguishes only rows of different <plants> during the import process. The Import Utility rejects rows of different <areas> and <units> if a plant contains more than one <area> and <unit>. For example, the CABLE table is defined per <plant>. Therefore, the CABLE table contains data that is unique only at the plant level.

Data Import at the Intermediate Level

If you select to import data per <area>, the Import Utility distinguishes only rows of different areas during the import process. The Import Utility rejects rows of different <units> if an <area> contains more than one <unit>.

Data Import at the Lowest Level

The target table is CHANNEL (a table defined per <plant>) and you select on the Import Level tab the <unit> level. In this case the AREA_ID and UNIT_ID table columns become Foreign Key columns in the CHANNEL Table.

Primary Key and the Foreign Key Column Definitions

The Import Utility defines the Primary Key and the Foreign Key columns of the target table, which you selected on the Link Definitions dialog, in three possible ways:

You select the same import level as the level of the target table (this is the default option): in this case only the table columns regarding this level (for example, UNIT_ID, AREA_ID, and so forth) is automatically defined by the Import Utility as a Primary Key in the target table.

For example:

The target table is COMPONENT (a table defined per <unit>) and you select on the Import Level tab the <unit> level: the UNIT_ID table column is also defined as a Primary Key column in the target table.

You select a higher import level than the level of the target table: in this case all the table columns regarding the level of the target table and the levels above (for example, PLANT_ID, AREA_ID) will be automatically defined as Primary Key columns in the target table.

For example:

The target table is COMPONENT (a table defined per <unit>) and you select on the Import Level tab the <area> level. In this case both the AREA_ID table column and the UNIT_ID table column become Primary Key columns in the COMPONENT Table.

You select a lower import level than the level of the target table: In this case all the table columns regarding the level you select and the levels below will be automatically defined as Foreign Key columns in the target table.