Mapping Rules and Limitations - Intergraph Smart 3D - Administration & Configuration - Hexagon

Intergraph Smart 3D Integration - SmartPlant Foundation

Language
English
Product
Intergraph Smart 3D
Subproduct
Integration
Search by Category
Administration & Configuration
Smart 3D Version
13
SmartPlant Foundation / SDx Version
10

Schema mapping in Smart 3D has some important limitations that you need to know.

Per Model Limitation

Smart 3D does not support mapping per model, just per catalog. SmartPlant Foundation does support mapping per model. If you want to map per model in Smart 3D, set up your project so that you have one catalog per model.

Publish Limitations

Mapping for publish carries the following limitations:

  • The mapping is done against the P3D Component only.

  • The Schema Editor does not currently show the properties for mapped edge definitions. Any mapping spreadsheet generated using the Schema Editor will not have all the mappings.

  • Some properties are set in the publish code and cannot be changed. The following table lists these properties.

    Tool Class/Map Edge

    Tool Property

    SmartPlant ClassDef/EdgeDef

    SmartPlant PropertyDef

    IJDObject

    OID

    P3DEquipment

    UID

    IJNamedItem

    Name

    P3DEquipment

    Name

    IJRange

    Low_x

    P3DEquipment

    Range1X

    Low_y

    P3DEquipment

    Range1Y

    Low_z

    P3DEquipment

    Range1Z

    High_x

    P3DEquipment

    Range2X

    High_y

    P3DEquipment

    Range2Y

    High_z

    P3DEquipment

    Range2Z

When you use the Schema Editor to update the publish mapping and Catalog Schema, the following limitations exist:

  • It is not possible to create a new MapClassDef (tool map object for a class in Smart 3D) using the Schema Editor. However, you can create new user-defined classes with the Excel workbooks and the Bulkload utility. These new classes are then added to the tool map schema (SP3DPublishMap.xml) during the synchronize step in the Schema Editor.

  • Adding or deleting properties on a system interface is not permitted. Only properties in the user-defined package can be modified.

  • Modifications to certain system select lists are not allowed. You can open the AllCodeLists.xls workbook delivered with Smart 3D to determine what select lists can be modified. There is a note at the top of each sheet telling you if the list can be modified, and if so, what parts of the list can be modified. Alternatively, you can open and review the AllNonEditableSystemCodeListTables.txt file delivered to [Product Folder]\CatalogData\BulkLoad\Bin. This file lists the codelists that are not editable.

  • Creating a new MapUoMDef in the tool map schema does not create a new UnitType in Smart 3D.

Retrieve Limitations

During a retrieve operation, the adapter assumes that the data it receives is synchronized with the metadata defined in the Catalog Schema. The map file cannot have a one-sided definition. That is, a class or property must exist both in the SmartPlant schema and in the Smart 3D Catalog Schema. The map file is responsible for making this connection between the two definitions.

An important limitation of the retrieve process is that shared objects (objects that contain information from two or more tools) are completely deleted when a single tool deletes an object.

Select List (Enumerated List) Limitations

There are different kinds of select lists; one type is system lists. Most system select lists are not extensible. You can view explanations of the restrictions in the AllCodeLists.xls workbook.

Another type of select list is a hierarchical (multi-level) list. You can have duplicated values in another level within a hierarchical list. However, you cannot have duplicated values at the same level in a hierarchical list, or in a list with just one level.

User reference data codes start at 10,000. Values less than 10,000 are reserved for use by Hexagon. When you extend a select list, you should start with values greater than or equal to 10,000.

Limitation on the SmartPlant Schema

The retrieve map is updated directly from the contents defined in the SmartPlant schema. In rare cases, if an entry is removed from the SmartPlant schema, you may need to edit the retrieve map file to remove the deleted entry. You should use the Schema Editor delivered with the Schema Component for this purpose.

See Also

Schema Mapping Rules