After you add the new object to the SmartPlant schema, you can use the File > SmartPlant > Compare (Active Tool Schema) with Schema command to perform a comparison between the tool map schema for each of the other authoring tools and the SmartPlant schema. Because the tool map schema and the tool metadata were synchronized at the beginning of the work process, you are essentially comparing the SmartPlant schema with the tool metadata.
The View Comparison Results window uses color coding to show you which objects are the same (green) in both and are completely mapped, which ones are different or have not been completely mapped (blue), and which ones have not been mapped at all (red) in the tool map schema and the SmartPlant schema. By default, the comparison results only show those objects that are different or that are unmapped.
For those objects that appear in blue in the View Comparison Results window, you can resolve these differences by double-clicking the node in the tree view to display the Map Environment. You can use the Publish and Retrieve tabs in the Map Environment to resolve differences by doing the following:
-
Adding objects to tool map schema and metadata using the toolbar on the left side of the tab
-
Mapping between the tool and SmartPlant schema by selecting objects on both sides of the dialog box and clicking the Map button in the middle of the tab.
-
Defining properties that you do not want to map, which means that you do not want them to show up in the Unmapped application properties or the Unmapped SmartPlant properties tables on the Publish and Retrieve tabs
-
Defining properties that you want to ignore during mapping, which can be used for internal application properties that are not required for mapping and that should not be synchronized in the tool map schema
You can also switch between authoring tools for comparison to make adding objects to the tool schema and metadata easier by loading multiple tool map schemas using the File > SmartPlant > Edit Engineering Tool Options and then setting another tool map schema as the active schema file.
You can repeat this process for each integrated authoring tool to propagate the change you made for one tool into all the other authoring tools for which the change is relevant.