Import Systems Hierarchy from Excel Command - Intergraph Smart 3D - Help - Hexagon PPM

Intergraph Smart 3D Systems and Specifications

Language
English
Product
Intergraph Smart 3D
Subproduct
Systems and Specifications
Search by Category
Help
Smart 3D Version
13.1

The Tools > Import System Hierarchy from Excel command creates systems and a system hierarchy based on data from a Microsoft Excel workbook. You can create any type of system. Each system class can have its own set of properties, either default or user-defined.

Two sample workbooks are delivered to [Product Folder]\SystemsAndSpecs\Import as part of the default client setup. These workbooks contain sample template worksheets and sample system data sheets. Each of these worksheets can be modified to reflect the appropriate property values, the system parent, and the allowed specifications for each system you create. See ImportData_Sample Workbook and Pipelines_Sample Workbook for more information.

Each system that you create requires a unique set of properties that includes the software-required properties as defined in the reference data. The workbooks use a different sheet for each different system type. Each column in a particular sheet corresponds to a property.

The utility reads data from the workbook and either creates a new system or updates an existing system, as is explained in the following:

  • If the system does not currently exist in the database but the specified parent system does exist, the new system is created.

  • If the system and the specified parent do not currently exist, the new system is created under the root folder and is highlighted in yellow.

  • If the system already exists, the existing system is updated.

Systems defined in the workbook are created in the order in which they are defined in the workbook (left to right). In turn, each sheet in the workbook is completely processed before the next sheet. On individual sheets, rows are processed in order (from the top down).

In order to function properly, the parent system must be created before the child. For example, the following system types would be on different sheets:

  • Units

  • Piping Systems

  • Piping Systems (sub-systems)

  • Pipelines

The following illustration demonstrates the need for providing an absolute parent tree when specifying the parent system in the workbook.

In this illustration, if you want to update Pipeline AS001, the parent path up to the unit level is required (Parent System=Air System/System 1/Unit 1). If you want to update Pipeline AS003, the path required to find a unique Parent system is Air System/System 1/Unit 2.

Leaving the Allowed Specifications box blank causes the system to use the same values as the Parent system; otherwise, filling in values will set the specifications. For example, if you want to add Pipeline AS0023 to Piping system Air System but do not specify an allowed specification, the system sets the allowed specification of Pipeline AS0023 to the same values as the Parent system (Air System).

Import Systems Hierarchy from Excel Dialog