Splitting Objects and Permission Groups - Intergraph Smart 3D - Help

Intergraph Smart 3D Structural Detailing

Language
English
Product
Intergraph Smart 3D
Subproduct
Structural Detailing
Search by Category
Help
Smart 3D Version
12.1 (2019)

When an object is split, or a split is deleted, the software places the resulting parts in the same permission group as the original parts. In ambiguous cases where you do not have permission to update parts or connections, the software places the original parts on the To Do List in a To Be Deleted state and assigns the new parts to the active permission group. A user with write access to the permission group assigned to the original parts must update the To Do List to delete the original parts.

If the user who performs the To Do List update has write access to both permission groups, you can avoid an iterative update process with multiple users between the two parts.

Example 1

A plate system is defined and the part is detailed. Both the system and the part belong to permission group one. User A has write permission to permission group one, and adds a design seam. The software deletes the original detailed part, creates two new parts, and assigns them to permission group one, because that is the permission group associated with the original part.

Example 2

A plate system is defined in permission group one. The part is moved to permission group two, and detailed. User A has write access to permission group one and read access to permission group two, and adds a design seam. The software places the original detailed part on the To Do List in a To Be Deleted state. The new parts, along with their assembly connections and physical connections are placed in the active permission group. Any features on the original part migrate to the new parts, and therefore are also assigned to the active permission group.

User B has write access to permission group two, so he can update the To Do List which deletes the original part.

User C has write access to both permission group one and two. He can assign the new parts to permission group two. The associated connections and features change to permission group two automatically when the permission group is changed on the part.

Example 3

A plate system is defined in permission group one. The system is split creating parts 1 and 2. Both parts have been assigned to permission group two and detailed. User A, who only has write access to permission group 1, deletes the seam. Parts 1 and 2, and the part level connections between them, go to the To Do List in a To Be Deleted state. The newly created part 3 is assigned to the active permission group, along with any features that migrated from parts 1 and 2.

Example 4

A bulkhead is bounded by a deck. The bulkhead systems are in permission group PGS1. The deck systems are in permission group PGS2. The bulkhead parts are in permission group PGP1. The deck parts are in permission group PGP2. The deck is split by a seam such that the bulkhead will be bounded by two deck parts. If a split is created by a user that only has access to the deck systems (PGS2), the original leaf logical connection, assembly connection and physical connection between the deck and bulkhead (which are children of the bulkhead and are in PGS1 and PGP1) are placed on the To Do List in a To Be Deleted state. The two new leaf logical connections, assembly connections, and physical connections are created in the active permission group.

A user with write access to PGS1 must update the To Do List to remove the To Be Deleted logical connection. A user with write permission to PGP1 must update the To Do List to remove the To Be Deleted assembly connections and physical connections. A user with write access to both PGS1 and the active permission group (or the permission group where the objects were created if the active permission group has changed) must reassign the new logical connections to the bulkhead permission group (PGS1). A user with write access to PGP1, PGP2, and the active permission group must reassign the new assembly connections and physical connections.

Use the Database Integrity Clean command to correct the permission group assignments, or create a filter to select the necessary objects and edit the permission groups.

See Also

Straking Seam by Intersection
Straking Seam by Offset Command
Straking Seam by Projection Command
Straking Seam by Table
Split Physical Connection