Map Custom Smart 3D Codelist Table Numbers - Intergraph Smart Interop Publisher - Help

Intergraph Smart Interop Publisher Help

Language
English
Product
Intergraph Smart Interop Publisher
Search by Category
Help
Smart Interop Publisher Version
17

If you have custom code list entries for Smart 3D source files that you published to SmartPlant Foundation, you must do some additional mapping for publishing to HxGN SDx in as-built projects. This is because the schema that integrates with SDx is different from the schema that integrates with SmartPlant Foundation.

HxGN SDx supports the Smart InterOp (SIO) schema that defines all objects and relationships supported for integration. The additional mapping involves any custom code list number from SPF EFSchema mapped to a code list number in SDx SIO schema so that generated Smart Models can be published to a HxGN SDx server.

Smart Interop Publisher provides the SPFSIOCodelistMapping sheet in the delivered default and custom P3DtoR3DMapping.xls file to support codelist number mapping. Follow the steps and example shown below.

  1. Review the codelist mapping that is already available in the default P3DToR3DMapping.xls.

  2. Make a copy of the delivered CustomP3DToR3DMapping.xls.

  3. From your copy of the CustomP3DToR3DMapping.xls file, go to the SPFSIOCodelistMapping sheet.

  4. Type the following column entries for the mapping:

    1. The name of the SPF Codelist Table to map.

    2. The SPF property name under SPF Property for Mapping containing the mapped codelist numbers. If nothing is specified, the software maps all properties that refer to the SPF Codelist table.

      Multiple properties can be mapped using the pipe symbol "|" in between each property: ShipPlate_Tightness | ElectricalPort_Tightness.

    3. Type the SPF Codelist Numbers referenced in the table.

    4. Type the new codelist number to be mapped for the SIO Codelist Number.

    5. (Optional) Type a description of each mapped number under Codelist Value.

    The example below shows the mapping for codelist numbers in the Tightness SPF codelist table.

  5. Save your edits.

  6. Translate the source files using the custom translation setting.