Relationships - Intergraph Smart Electrical - Customization - Intergraph

SmartPlant Enterprise SmartPlant Adapter for Smart Electrical

Language
English
Product
Intergraph Smart Electrical
Search by Category
Customization & Programming
SmartPlant Foundation / SDx Version
Smart Electrical Version
2018 (8.0)

There is a MapRelDef object in Smart Electrical Tool Map schema for each type of relation to be published. Each MapRelDef object defines a relation between two MapClassDef objects (directly or using map class interfaces). When Smart Electrical publishes an item, SmartPlant Adapter searches for MapRelDef defined for the MapClass of this object, and if found, searches for related items realizing the interface on the second end of the relation.

General

Property

Value

UID

The UID must be constructed using the following pattern:

UID = SPELREL_<End1ClassName >_<End2ClassName>

Name

The name of the Smart Electrical MapRelDef object

End1MapClass

The class name of the end1 MapClass

End2MapClass

The class name of the end2 MapClass

Select Criteria

<ItemType>@<Foreign key property>

If this field is not empty, SmartPlant Adapter for Smart Electrical will search for related item using this criterion. For example, if the value is Cable@SP_ConnectionSide2ID, in case the current item is a Cable, the software will search for a PlantItem with SP_ID = value of SP_ConnectionSide2ID property value of the current item, otherwise, when the item is not a Cable, the software will search for all the Cables having SP_ID value of this item in their SP_ConnectionSide2ID property.

Process Criteria

A comma separated list of relations names that should be traversed in order to approach the related item.

Mapping Relationships

Relationship

Comment

Maps to

To support the publish operation, a MapRelDef should be related to the corresponding RelDef in the SmartPlant Schema by means of the Maps to relationship.

Note that the order of mapping is important in the map file. The items with the lowest level criteria listed (Type3) must appear first in the list, followed by Type2, and then Type1.

For example, you may have set Type1, Type2, and Type3 values and listed the Type1 value before the Type3 value in the map file. In this case, as soon as the software evaluates the Type1 value, it will use that value, even though you may actually want it to use the Type3 value.