Moves objects from one location to another. You specify the original location of
the object and then indicate the destination location. You can move one object or
select multiple objects to move simultaneously.
The software maintains persistent relationships that exist between objects during a move. For example, if a pump has been mated to a surface that relationship continues to exist even after the pump is moved to another location within the workspace. Remember that relationships may prevent you from moving an object to where you want. For example, the pump cannot be moved off the surface, only to another location on the surface. You may need to delete relationships to move an object to its new location.
Reconnecting Route Objects with Unfinished Ends
When you move, or modify a route object in HVAC, Electrical, or Piping, Smart 3D treats any unfinished ends as free end features. An unfinished end is an end with mating parts or a logical data connection with one logical port. You can reconnect using these free end features. This behavior allows you to reuse existing mating parts and connections and reduces wait times.
The software restricts cross project relationships when working with As-Built projects. There are five scenarios where connections are not established during a move operation in the Change Management model. When you encounter one of the scenarios listed below, the software displays a message. Connections cannot be established until you resolve the issue.
-
Performing a move operation with native publishable objects that have a relationship to other project data. For example, performing a move operation on an equipment claimed to Project1 and a pipe run routed in Project2 results in a cross project relationship. To resolve this issue, route the pipe run in Project1, and then perform the move operation again.
-
Performing a move operation with native objects in relation to unclaimed objects (Smart Interop Objects). The software restricts the establishment of connections if you try to move a pipe run that belongs to the active As-Built project to an unclaimed Smart Interop nozzle of an equipment. To resolve this issue, claim the Smart Interop nozzle to the active project, and then perform the move operation again.
-
Performing a move operation without setting the active project. In this scenario, the connection object is not created because project data cannot be created outside a project context. To resolve this issue, set the active project, and then perform the move operation again.
-
Performing a move operation without having permissions on the active As-Built project. To resolve this issue, request that the project administrator assign you the appropriate permissions on the As-built project, and then perform the move operation again.
-
Performing a move operation with native objects in relation to subscribed Smart Interop Objects. The software does not establish connections if you try to move a pipe run that belongs to the active As-Built project to a subscribed Smart Interop nozzle of an equipment. To resolve this issue, release the subscribed object in the primary model, synchronize the related project in the current model, claim the Smart Interop nozzle to the active project, and then perform the move operation again.
-
For information about a message that the software displays, see Error Messages in the Smart 3D Troubleshooting Reference Help. Messages are listed in alphabetical order by the first word of the message.
-
A Change Management model enables you to use the SDx integration commands, such as assigning As-Built projects to Smart 3D or synchronizing Smart Interop Object data between Smart 3D and SDx. See the Smart 3D Project As-Built with HxGN SDx Help.
Command Behavior with SIO Supports
The sections below describe the behavior when you move a Smart Interop Object (SIO) support with regard to its supported and supporting objects. In the scenarios described below, the SIO route is the supported object, and the SIO structure is the supporting object.
Moving a SIO support along the SIO route
When a SIO support is connected to a SIO route and a SIO structure, you can move the SIO support along the supported object (1 in the example below). The software maintains the relationship between the supported object and the supporting object, and does not generate a To Do List (TDL) record.
Moving a SIO support using a point in space
If you select a point outside the supported object (1 in the example below) while moving the SIO support, the software projects the selected point onto the supported object and moves the SIO support to that point. The software maintains the relationship between the supported object and the supporting object, and does not generate a TDL record.
The supporting object is deleted
If you move a SIO support that is connected to a supported object and the supporting object is deleted, the software generates the following TDL record: "Supporting object or face has been deleted or cannot be found. Support is invalid without supporting item. Connect to another supporting object or face." The software maintains the relationship with the supported object, and only guided movement is allowed. After you move the support, the software retains the TDL record until you connect the support to a new supporting object.
Either the supporting or supported object is boundary
Attempting to move a SIO support that is connected to boundary objects generates the following TDL record: "Cannot move selected objects because of their connectivity to Unclaimed Objects. Request to Claim or to Disconnect these connected objects."
The supported object is deleted
If you move a SIO support that is connected to a supporting object and the supported object is deleted, the software deletes the supported object and generates the following TDL record: "The support does not have a supported object. The support should be re-connected or deleted." In this case, you can move the support in free space. However, moving the support away from the connected structure generates the following TDL record: "Support located outside of the Boundaries of the Input Objects."
The software maintains the relationship with the supporting object.
When you reconnect the SIO support to a route, the software removes the following TDL record: "The support does not have a supported object."
Physically connecting the support to a supporting object resolves the following TDL record: "Support located outside of the Boundaries of the Input Objects."
The SIO support is connected to a supported object and the supporting object is an equipment object
Moving the equipment object generates the following TDL record for the SIO support: "Support located outside the Boundaries of the Input Objects." Moving the SIO support does not resolve the TDL record. Physically connecting the support to a supporting object does resolve this TDL record.
Deleting the equipment object generates the following TDL record: "Supporting object has been deleted or cannot be found. Support is invalid without supporting item. Connect to another supporting object or face." The TDL retains this record if you move the SIO support. Connecting the support to a supporting object resolves the TDL record. You cannot move a SIO support that is connected to a SIO turn or bend.
What do you want to do?