Modify the Smart Instrumentation Tool Schema for a Custom Plant Hierarchy - 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)
  1. Create a hierarchy in Smart Instrumentation that contains the same number of levels as the one defined in the SmartPlant Foundation custom hierarchy. For details, see Create a Plant Hierarchy.

  2. Modify the following information in the delivered INtoolsMap.xml file to map it to the levels in the example custom hierarchy.

    • The INtoolsMap.xml file is installed by default in the path <Smart Instrumentation home folder>\XML\.

      INtoolsMap.xml File Level

      Mapped To

      Custom Hierarchy Level

      TEFRetrieve_PBSDocument_Plant

      County

      Top level

      TEFRetrieve_PBSDocument_Area

      City & District

      Intermediate levels

      TEFRetrieve_PBSDocument_Unit

      Precinct

      Lowest level

    • The values in the Mapped To column are for this example only. You should substitute the appropriate values for your hierarchy.

    • You will need to create new map classes ICity, IDistrict, and IPrecinct. For details of the procedure, see Create New Schema Objects.

  3. Launch Schema Editor.

  4. On the Workflows dialog box, click the Tool Schema tab.

  5. Click Open.

  6. Navigate to the file path: Program Files > Common Files > Intergraph > EFSchema > EFSchema.xml.

    SHARED Tip The file may take some time to open.

  7. Click Open to select the tool schema file.

  8. Navigate to the INtoolsMap.xml file.

  9. Click View.

  10. On the View Tool Schema dialog box, from the Form list, select Tree/Table Horizontal, and then click OK.

  11. In the tree view, expand the SPMapClassDef node.

  12. Scroll down to the TEFRetrieve_PBSDocument_Plant node.

  13. Right-click this SPMapClass and on the shortcut menu, click Edit INTL_TEFRetrieve_PBSDocument_Plant.

  14. On the Edit Map Class Definition dialog box, under the Retrieve map section, clear the value IPlant and click the ellipsis button as shown:

  15. On the dialog box Possible ClassToMapClass\Classes for TEF Retrieve_PBSDocument_Plant, in the Search box, type iplant.

  16. Select IPlant as shown and click OK.

    SHARED Tip The top level interface (IPlant in this example) cannot be renamed. Therefore in the custom hierarchy, the top level will always be mapped to IPlant. Consequently, the IPlant interface remains mapped to the IPlant interface (as shown in the graphic) and no mapping changes are required.

  17. Click OK to close the Edit Map Class Definition dialog box.

  18. Right-click the TEFRetrieve_PBSDocument_Area node, and on the shortcut menu, click the Edit option.

  19. On the Edit Map Class Definition dialog box, under the Retrieve map section, clear the value IFunctionalArea and click the ellipsis button.

  20. On the dialog box Possible ClassToMapClass\Classes for TEF Retrieve_PBSDocument_Area, map the intermediate level interface to ICity and IDistrict.

  21. Click OK to close the Edit Map Class Definition dialog box.

  22. Right-click the TEFRetrieve_PBSDocument_Unit node, and on the shortcut menu, click the Edit option.

  23. On the Edit Map Class Definition dialog box, under the Retrieve map section, clear the value IFunctionalUnit and click the ellipsis button.

  24. On the dialog box Possible ClassToMapClass\Classes for TEF Retrieve_PBSDocument_Unit, map the lowest level interface to IPrecinct.

  25. Click OK to close the Edit Map Class Definition dialog box.

  26. Click File > Save.

  27. Close the Schema Editor, and at the prompts to save the data and to load the changes to the SmartPlant Foundation Server, click Yes.