Permission Group Behaviors Between Tasks - Intergraph Smart 3D - Help

Intergraph Smart 3D Molded Forms

PPMProductFamily
3D Design and Visualization
PPMProduct
Intergraph Smart 3D
PPMCategory
Help
Version_S3D
10.1(2014R1)

Permission groups provide controls for when, where, and by whom the model can be updated. Permission groups are assigned according to several common types of workflow. They typically fall into the following categories:

  • By Function: such as Outfitting versus Structure, or Piping versus Equipment versus Molded Forms versus Structural Detailing.

  • By System: such as Hull versus Deck1 versus TransvBhd1. This includes the ability to place the hull system (and its child leaf systems, seams, connections related seams, reference curves and openings) in a different permission group than the hull detailing objects and other connected objects.

  • By Area: Fwd versus Aft, or by block or assembly.

  • Combinations: for example, By Function and By Area (Molded Forms for Block1 versus Detailing for Block1).

The permission group of an object is not modified regardless of the Active Permission Group unless the permission group is explicitly changed on the Configuration tab of the Properties dialog box as described under the change propagation sections below.

Molded Forms Behavior

Plate systems and profile systems are assigned to the Active Permission Group.

Leaf systems, light parts, reference curves, and logical connections are assigned the permission group of their parent.

Seams and openings are assigned to the permission group of the plate or profile system they cut. You must have write access to the root plate system being cut when placing an opening or design seam.

In the Execute Split command, seams and knuckles that you do not have permission to modify are not selectable in the table.

Logical connections between profile systems and plate systems are in same permission group as the profile systems.

Logical connections between different root systems are created as children of the bounded or penetrated system.

Summary of Molded Forms permission behaviors:

Object

Permission Group

Comments

Root plate system

Active Permission Group

Leaf plate system

Same as root plate system

Root and child logical connections

Same as dependent root plate system

Reference curve

Same as root plate system

Design seam, intersection seam

Same as root plate system

Must have write access to root plate system

Opening

Same as root plate system

Must have write access to root plate system

Manual logical connection

Permission group of system for which you have write access, use first system selected if you have write access to both systems

Must have write access to at least one of the systems being connected

Root profile system

Active Permission Group

Profiles are handled similarly to plates

Logical connection between stiffener or edge reinforcement and the plate being stiffened

Same permission group as root profile system

Beam

Active Permission Group

Molded Forms Change Propagation

The root system and its child leaf system, logical connections, reference curves, seams and openings always have the same permission group. When the permission group is changed for any of these objects, the permission group is also changed for the other objects.

If plate system A is bounded by plate system B, you can modify A without write access to B. Plate System B is placed on the To Do List as Out of Date if the change to A impacts B.

Structural Detailing Behavior

The detailed part permission group is not assigned from the parent system permission group. Detailed parts created with Execute Detailing are assigned to the Active Permission Group. You can modify this assignment. You must have write permission to the part to detail the part.

If a detailed part is deleted, the resulting light part maintains the permission group of the detailed part.

You can assign different permission groups to parts sharing the same leaf system as created by a planning seam.

You can only add seams and features to a part if you have write permissions to the part.

Summary of Structural Detailing permission behaviors:

Object

Permission Group

Comments

Light Root Plate Part (before detailing)

Same as plate system at creation

Detailed Root Plate Part

Active Permission Group when detailed. Part keeps this permission group if the detail part is deleted.

Must have write access to the light part

Leaf part

Same as root part

Straking seam

Same as root part

Must have write access to root part

Feature placed by command (edge, corner, sketched, free edge treatment)

Same as root part

Must have write access to root part

Assembly Connection

Same as dependent part

Feature, part, physical connection created by assembly connection

Same as assembly connection

Free end cut object and its features

Same as root part

Standalone part

Active Permission Group

Structural Detailing Change Propagation

The detailed part, its child leaf parts, features and straking seams always have the same permission group. Assembly connections always have the same permission group as the dependent part in the connection. Assembly connection children always have the same permission group as the assembly connection. Standalone parts plus associated features and connections always have the same permission group. When the permission group is changed for any of these objects, the permission group is also changed for the other objects.

If you do not have write access to a part, the part is placed on the To Do List as Out of Date if a change is made to the part. Assembly connections and features are also not created until the part is updated on the To Do List by someone with write access.

Hole Management Behavior

Hole traces and outfitting catalog hole fittings are assigned to the Active Permission Group.

Hole cuts and structural hole fittings are assigned the permission group of their parent structural part (plate or profile).

Summary of Hole Management permission behaviors:

Object

Permission Group

Comments

Hole trace

Active Permission Group

Hole cut

Same as root plate part

Must have write access to parent plate part. Root plate part must be detailed in the Structural Detailing task.

Outfitting catalog hole fitting

Active Permission Group

Structural hole fitting

Active Permission Group

Must have write access to parent plate part. Root plate part must be detailed in the Structural Detailing task.

Hole Management Change Propagation

The permission group of an outfitting catalog hole fitting can be changed without changing the permission group of the hole trace.

The permission group of a structural hole fitting can be changed without changing the permission group of the hole cut or parent plate part.

A hole cut and its parent plate part always have the same permission group. When the permission group is changed for one of these objects, the permission group is also changed for the other object.

Planning Behavior

Planning permission group behavior is related to Molded Forms and Structural Detailing behavior because planning seams split leaf systems.

When Manage Intersections is run and an intersecting part is set to Split or Offset, planning seams are created in the Active Permission Group. You must have write access to the root system.

Summary of Planning permission behaviors:

Object

Permission Group

Comments

Planning seam

Active Permission Group

Must have write access to the root system of the parts being split.

Block or assembly

Active Permission Group

Planning Change Propagation

Write access is required to both parts to remove a planning split using Flatten Assembly or Manage Intersections. The resulting new part is assigned to the same permission group as the original parts if they belonged to the same permission group. The new part is assigned to the Active Permission Group if the original parts were in different permission groups.

Global Workshare Behavior

Global Workshare allows managed replication of the model at several sites. One of the restrictions of a Workshare configuration is that you only have Read access to objects that are controlled by non-local permission groups.

A system is a logical grouping of sub-systems. When you add or remove a sub-system, you are modifying the definition of the parent system. Therefore, you must have write access to the parent system. You do not need write access to the grandparent system.

When participating in a Global Workshare Configuration, you must manage all permission groups at the host site. The sub-system requirement to have write access to its parent system is not possible if the sub-system's permission group is created at the satellite site and the parent system's permission group is created at the host site.

For example, your host site is Houston and your satellite site is London. You create a system named "Midbody", and its controlling permission group is in Houston. You assign John, who works in London, write access. During the workshare replication process, the Midbody system and permission group is replicated in London. In London, John can add systems, plates, profiles and whatever else he wants to the Midbody system because John was given write access to the system's permission group in Houston. John cannot delete or change any of the properties of the Midbody system in London because the host site, Houston, owns it. He can only add objects to the system. If John were to travel to Houston and log on there, he could delete or change any of the properties of the Midbody system because the Houston host site owns it.