Disconnect Command - Intergraph Smart 3D - Help - Hexagon

Intergraph Smart 3D Piping

Language
English
Product
Intergraph Smart 3D
Subproduct
Piping
Search by Category
Help
Smart 3D Version
13.1
SmartPlant Foundation / SDx Version
10

Disconnects a section of route network, and enables you to modify its topology without disturbing the rest of the network. The software disconnects the selection at boundary connections, and deletes any mating parts and transitions at the boundaries. The software also removes all the relationships of the selection with the rest of the network. You access this command using Tools > Utilities > Disconnect (CTRL+ALT+D).

PPM recommends that you reconnect objects after modifying the selection to avoid topological errors.

You can disconnect the following route objects:

  • a pipeline

  • a pipe run

  • a set of features

  • a feature such as a turn feature, a component type along-leg feature, or a straight feature.

In the following example, the pipeline has four boundary connections:

Permission Group (PG), Approval Status, and Global Workshare Conditions

If you select route objects that belong to a permission group (PG) to which you have full control permission, the software disconnects the selected objects at boundary connections. You can also disconnect at a PG boundary connection if you do not have access to one side of the connection. But, you must have full control permissions to the objects that you select for disconnection.

If an object at the other end of the boundary connection is in a non-working approval state, the software generates a To Do Record for that object. Also, the software generates a To Do Record if the non-working object is in a different workshare location.

Olets

When you disconnect a branch at an olet, the olet remains with the header. The software only disconnects the branch. In the following example, the disconnected branch has been moved to show that the olet stays with the header.

If the header is at a different workshare location or is in a non-working approval state, the software disconnects the header side objects from the branch, when you disconnect the branch. The software generates To Do Records for the olets, and the software deletes the records only when you update the To Do Record.

Limitations

  • You cannot disconnect a branch feature, or an end feature.

  • To disconnect a feature on a leg, you must have full control permission to that leg.

  • If the selection includes equipment, the software does not disconnect the selection from the equipment nozzle.

  • You cannot disconnect a surface-mounted component.

See Disconnecting pipe runs using Move for information on how the software disconnects objects at boundary connections.

What do you want to do?