Integration - Intergraph Smart 3D - Troubleshooting

Intergraph Smart 3D Troubleshooting Reference

Language
English
Product
Intergraph Smart 3D
Subproduct
Troubleshooting
Search by Category
Troubleshooting
Smart 3D Version
11 (2016)

This section contains troubleshooting tips for integration.

Registering Your Model with another SmartPlant Foundation Plant

If you want to register your model with a different SmartPlant Foundation plant, you can run the Remove Design Basis custom command, which removes all correlation relationships and deletes all design basis objects in the 3D model.

Then, you can register the model. You must retrieve all of the data again, and re-correlate objects.

You must run the Remove Design Basis command from a task in the model, not from Project Management.

  1. Start the software.

  2. Click Tools > Custom Commands.

  3. Click Add on the dialog box.

  4. In the Command ProgID box, type IMSEngFrameworkCmd.RemoveDsgnBasis.

  5. In the Command name box, type text such as Remove Design Basis.

  6. Click OK on the Add Custom Command dialog box.

  7. Select the command name, and click Run.

  8. Click Yes on the message boxes.

  • After running this command, register the model, retrieve information, and re-correlate objects.

  • For more information about other custom commands, see the Common User's Guide, available from Help > Printable Guides in the software.

Retrieving and Viewing Piping from SmartPlant P&ID

To ensure that piping properties are passed correctly from SmartPlant P&ID to Smart 3D, you must specify the value SmartPlant 3D for the Use Piping Specification property in SmartPlant P&ID Options Manager.

Verifying P&ID Integrity

If there is a problem displaying a P&ID or selecting objects on a P&ID, you can run a custom command to troubleshoot the connections between the objects on the P&ID and the objects in the Model database. The ProgID for this command is SP3DDisplayPIDService.VerifyPIDCmd, and it provides the following statistics for a selected P&ID:

  • Design Basis Objects: The total number of design basis objects that have a relationship to the P&ID document object. The number should be the same as what is seen in the P&ID Viewer.

  • 3D Objects: The number of design basis objects that have a correlated relationship between the P&ID document and the Smart 3D object. The current correlation status is also reported.

  • P&ID Objects (Total Identified): This count is the total number of RAD objects that have a drawing ID in the P&ID document. The total identified should match the number of Design Basis Objects. These objects are displayed with their representation ID.

  • P&ID Objects (contained in Design Basis): The number of RAD objects that have a graphic OID that will map to drawing representation design basis objects. This number should match the Design Basis Object count. A mismatch most likely means that the objects were deleted. The difference is the number of Deleted P&ID OIDs.

  • Deleted P&ID OIDs: The number of RAD objects that have a graphic OID but do not exist in the model.

  • Duplicate OIDs: The number of multiple RAD objects with the same graphic OID. Most likely, there is a problem with the P&ID file or with the integrated environment.

  • Miscellaneous Errors: Any errors not defined above are in this category.

Accessing Map Files

When running the Compare Design Basis command, the software looks for the map file on the SharedContent share. If you do not have access to this share or to the map file, you will see an error message. Ask your administrator to grant you access privileges to the SharedContent share.

Mapping Enumerated Lists

To use an enumerated list (also called codelist or select list) in an integrated environment that includes Smart 3D, you must map the list in the SmartPlant schema. If the list does not already exist in the SmartPlant schema, then it has to be created there and mapped. If it already exists in the SmartPlant schema, then you must define the mapping between the SmartPlant schema and the tool map schema.

Enumerated lists in Smart 3D are not mapped in the Schema Editor. These lists use the index number defined in the enumerated definition to map from the tool to the SmartPlant schema.

For example, if you want to add Fluid System values, modify the SmartPlant schema to include the fluid codes that are missing. You can examine the catalog data in the Catalog task or in the Excel .xls files that were bulk loaded to find out which fluid codes to add and their numbers. You must also generate component schemas to create a new P3DComponent.xml file, which is part of the SmartPlant schema.

For publishing operations, you will need to make the corresponding changes and additions in the publish map. 

User reference data codes start at 10,000. Values less than 10,000 are reserved for use by Intergraph.

Here are some important points to check when troubleshooting the mapping of enumerated lists for publishing:

  • Did you extend the enumerated list in the SmartPlant schema?

  • Did you extend the Smart 3D publish map?

  • Have you used the same value in both the SmartPlant schema and the Smart 3D publish map?

  • Have you regenerated component schemas?

  • Have you regenerated the views on the Model database? You can use the View Generator at [Product Folder]\Core\Tools\Administrator\Bin for this purpose. The schema to use is the Catalog Schema database.