Import Cables, Cable Sets, and Wires - Intergraph Smart Instrumentation - Help

Intergraph Smart Instrumentation Help

Language
English
Product
Intergraph Smart Instrumentation
Search by Category
Help
Smart Instrumentation Version
13.1
  1. Create a link group for placing the links you are going to create.

  2. On the Link Definitions dialog, create an import link for cables as follows:

    1. In the Link box, type a unique link name, for example Cables.

    2. Under Import method, select Single table.

    3. Under Name of module or table, select CABLE.

    4. Complete the import link creation.

  3. Open the Link Properties dialog, and, on the General tab, do the following:

    1. Make sure that Import to supporting tables is cleared.

    2. Under Undefined NOT NULL fields, select Reject rows.

    SHARED Tip Selecting Reject rows is recommended to set the software to reject all source values that do not match foreign key values in the CABLE table. For example, if a cable manufacturer in your source does not match the manufacturer that already exists in Smart Instrumentation, the software indicates that this manufacturer does not exist. If you select the Use default value, in the CABLE table, the Import Utility will enter 0 (zero) values in all the columns whose values do not match the values in the import source.

  4. If your import source contains device cables, and you need to associate them with instruments that exist in various <units> in Smart Instrumentation, on the Import Level tab, under Hierarchy levels, select Apply and select the lowest plant hierarchy level. For details, see Import Data Into Multiple Plant Hierarchy Items.

    • If your import source contains device cables, we recommend that the target <unit> for importing device cables be the same as the <unit> where the associated instrument tags appear.

    • Although, <plant> is the default import level for wiring data, specifying a <unit> level for wiring items allows you to filter the imported wiring data per <unit> in the Domain Explorer.

  5. In the Import Link window, open the import link.

  6. In the Target pane, define the import mapping as follows:

    1. Select the CABLE_NUM row, and then, from the Source pane, drag the column containing the cable names.

    2. Depending on your source cable type, define a mapping value for the CABLE_CATEGORY column. For example, a Fieldbus Home-Run cable mapping value = H, a Conventional cable mapping value = R. For details, see Mapping Codes for Wiring Data Import.

  7. To determine whether to create imported items as cables or cross cables do one of the following:

    • For the DEF_FLG flag, type N so that in Smart Instrumentation, the imported cables appear in the Domain Explorer in the Cables folder.

    • For the DEF_FLG flag, type C so that in Smart Instrumentation, the imported cables appear in the Domain Explorer in the Cross Cables folder.

      SHARED Tip If you define Y as a mapping value for the DEF_FLG flag, in Smart Instrumentation, the imported items appear in the Reference Explorer.

  8. If needed, complete the import mapping by dragging the appropriate column names from the Source pane or by entering strings or values in the fields in the Target pane.

  9. Repeat Steps 1-8 for creating a Cable Sets link for sable sets by selecting CABLE_SET as the target table and make sure you map all the required columns, which are shown in red bold.

  10. Repeat Steps 1-8 for creating a Wires link for wires by selecting WIRE as the target table and make sure you map all the required columns.

  11. In the link group, prioritize the links so that the Cables link appears at the top, Cable Sets in the middle and Wires at the bottom. For details, see Prioritize Links in a Link Group.

  12. Run the links in this order.

    If you must create a single link for importing cables and their child items, you need to select WIRE as the target table and select Insert data into reference tables check box on the Link Properties dialog. Bear in mind that such a link opens more slowly than a single-table link due to a large number of reference tables that the WIRE table has. Also, when running such a link, you are more likely to come across various errors due to the mapping complexity. Troubleshooting these errors may be time consuming.

See Also

Create a Link Group
Defining Import Link Properties Common Tasks
Mapping Codes for Wiring Data Import
Flow of Activities for Importing Data into Smart Instrumentation