Example: Mapping for Publish - Integration - Update 44 - Help - Hexagon

Integration Help

Language
English
Product
Integration
Search by Category
Help
Smart 3D Version
12.1 (2019)
Smart Construction Version
2019(7.0)
SmartPlant Foundation / SDx Version
10
Smart Electrical Version
2019 (9.0)
Smart Materials/Smart Reference Data Version
2020 (10.0)
Smart P&ID Version
9 (2019)
Smart Review Version
2020 (15.0)
Smart Engineering Manager Version
10 (2019)
Smart Interop Publisher Version
13.1 (2019 R1)
Smart Isometrics Version
7.0(2019)
Spoolgen Version
9.0(2019)

This example describes how to create publish mapping for two properties between SmartPlant Foundation and Smart 3D.

Launch Schema Editor and Load the Smart 3D Tool Map Schema

If you are creating mapping relationships but not extending the SmartPlant Schema, it is not necessary to check out the CMF file. However, you do need to open the CMF file along with the tool map schema to create the mapping relationships.

  1. In the Desktop Client, set your scope for the applicable plant, and then find the CMF file.

  2. Right-click the CMF file, and select Launch Schema Editor.

  3. On the Set Active Configuration dialog, select the version of the schema that you want to view.

  4. Select OK to set the configuration, and open the Schema Editor.

  5. In the Schema Editor, click File > SmartPlant > Edit Engineering Tool Options, and select Smart 3D in the list of authoring tools to load the Smart 3D tool map schema.

  6. Under Startup options, select the Load map schema and Connect to application schema check boxes, and select OK.

  7. In each row in the Synchronize dialog, the values in the tool database and tool map schema columns indicate actions to correct inconsistencies between the tool metadata and tool map schema. Select the appropriate action in each row, and then select OK.

    • Each row represents a discrepancy between the tool database and the tool map schema.

    • Default actions are blue when the Synchronize dialog displays. However, if you select a different option, it will become blue instead.

    • In many cases, only one operation is supported to synchronize the tool database and tool map schema. For example, if a new property was found in the database, the metadata adapter can add the property to the tool map schema, but it cannot remove the property from the tool database.

      12SESynch

Map the New Custom Properties

  1. In the Map Environment, expand SmartPlant 3D > Loaded Map Schemas > SmartPlant 3D Tool Schema.

  2. Expand the Map Classes node, and right-click IUCustom.

  3. On the shortcut menu, select Edit IUCustom.

  4. In the Edit Map Class Definition dialog box, click the browse button beside the Publish to SmartPlant class/interface field.

    IUCustomPublish

  5. Find ICustomInterface, which is the SmartPlant Schema interface definition on which the custom properties are exposed. Select the check box beside ICustomInterface, and click OK.

  6. Select the Publish tab.

  7. Under Unmapped application properties, select EngineeringSystem.

  8. Under Unmapped SmartPlant properties, select EngineeringSys.

    3DMapEngSystem

  9. Click Map .

  10. Repeat steps 7-9 to map the SystemCode property.

    3DMapSystemCode

  11. Confirm that both properties have been mapped at the bottom of the window.

    3DConfirmMap

  12. Click OK.

SHARED Tip To create mapping for correlation in Smart 3D, repeat steps 4 - 12 using the Retrieve from SmartPlant class/interface field and the Retrieve tab.

Save the Tool Map Schema

  • Select File > Save All Modified Files to save the changes to the tool map schema. Because you did not change the SmartPlant schema, you do not need to save the CMF file.

When you close the Schema Editor, the software offers to save your connection information, user interface options, and loaded tool map schemas to a session file. Select Yes in the message box to save the session files so that you can use it to return to this working environment. However, you should not open a session file after launching the CMF file from the Desktop Client.