Introduction to Hole Management

PDMS controls and manages holes using the Hole Management application which facilitates:

• Communication of hole data between disciplines including Request and Approval processes.

• Ensuring holes are only created by users with appropriate write access permissions.

• Performing validation checks on managed holes and providing feedback to users on the hole status.

• Generation of reports for managed holes.

Generally in AVEVA Plant projects discipline Designers do not have write access to items created by other disciplines, i.e. a Piping Designer does not have write access to Structural elements and Structural Designers do not have write access to Piping elements, etc.

With Hole Management penetration holes are specified and requested by the penetrating discipline, normally piping, HVAC or equipment designers and approved by the penetrated discipline, normally structural Designers. For cases where a penetration is required, say, for a steel section through a deck/floor plate, the hole would be specified, requested and approved by the structural discipline.

The specification of a penetration hole by the relevant discipline in the appropriate Design application creates a ‘virtual hole’ in the panel element, consisting of a FRMW and two FIXING elements. Each fixing element has a Specification Reference (Spref) attribute that points to the hole definition in the catalogue. An Association (ASSOC) element that references all of the hole elements is also created.

Once the ‘virtual hole’ has been created the penetrating discipline enters the Hole Management application and requests the hole. The owner of the panel, normally the Structural discipline, then reviews and approves (or rejects) the hole request using the mechanism provided by the Hole Management application.

The act of approving the request creates the ‘actual’ hole as a PFIT owned by the PANE element. The Hole Management application checks and validates the hole using the association restrictions and stores data on the hole history and status. Only valid holes may be approved. For a structural penetration the Structural Designer may be both the requester and approver, although specific company procedures, controlled by DAC, may be required if the Originator and Reviewer need to be different.

www.aveva.com

7.1.1 Hole Element Storage

The ‘virtual hole’ FIXING elements are stored in a FRMW owned by a STRU whose Purpose attribute is set to HOLE, for example:

The STRU element is normally pre-defined by the System Administrator in the specific Design database.

If a suitable STRU does not exist, the following error message is displayed:

The Hole Management associations are stored in an Association Group (ASSOGP) element owned by an Association World (ASSOWL) element. The ASSOGP must also have its Purpose attribute set to HOLE.

The ASSOWL and ASSOGP elements are normally pre-defined by the System Administrator. An association is created for each hole and named on a simple sequential numbering system.

Each association has several members of different element types that are not within the scope of this training guide. The Design Explorer may look like this:

If no ASSOGP element with the Purpose set to HOLE can be found, the Hole Management application will create an ASSOGP in the first writeable ASSOWL element and set the Purpose attribute.

If no writeable ASSOWL element can be found the following error message is displayed.

7.1.2 Request and Approval Workflow

Once the penetration hole has been specified and the ‘virtual’ hole created, the Hole Management application provides a series of tasks for the Originator (Penetrating discipline) and Reviewer (Structural discipline). These tasks are:

Originator Tasks Reviewer Tasks

Request Approve Redundant Reject Cancel Request Agree Redundant Delete Entry

There are three main workflow scenarios for the request/approval cycle that are detailed in the following sections.

www.aveva.com

7.1.2.1 Hole Creation/Modification Workflow

In this workflow the Originator creates the ‘virtual’ hole and then either requests it or deletes the entry.

Once requested, the Originator may cancel the request and delete the entry prior to it being reviewed.

If rejected by the Originator

If requested and not cancelled or deleted, the Reviewer checks the hole details and, if OK, approves the hole, thereby creating the ‘actual’ hole.

If the Reviewer rejects the hole then the Originator can either modify the ‘virtual’ hole and re-request the hole or cancel the request and delete the entry.

7.1.2.2 Redundant Hole Workflow

In this workflow the ‘actual’ hole has been created. The Originator decides that the hole is now redundant and sets its status to Redundant.

Before the Originator can delete the entry the Reviewer must agree that the hole is redundant.

www.aveva.com

7.1.2.3 Rejected Hole Workflow

In this workflow the ‘actual’ hole has been created. The Reviewer, possibly due to changed conditions, decides to reject the hole. The Originator has the option to:

• Modify the hole and re-request it, whereby it will go through the normal review and approval cycle.

• Cancel the request, in which case the ‘virtual’ hole details remain

• Delete the entry, in which case the entire hole is deleted and the ‘virtual’ hole and association deleted.

The ‘actual’ hole is deleted and the panel restored to its original state.

7.1.3 Non-penetration Managed Holes

In addition to penetration holes, the Hole Management application enables creation of non-penetration holes in structural panels. These holes fall into two general categories:

• Holes that are required, say, for access to a piece of equipment, a valve or other design item.

• Holes that are created by a panel fitting, e.g. a hatch, door, window, etc.

For non-penetration managed holes that are not created by a fitting, with the exception of a User Defined hole type, the ‘virtual’ hole is created as a single FIXING in a new FRMW, as described for penetration holes. This fixing has a Specification Reference (Spref) attribute that points to the hole definition in the catalogue. An Association (ASSOC) element that references all of the hole elements is also created.

Approving the hole creates an SFIT owned by the PANE.

User Defined hole shapes are created using a template and negative extrusion in a similar way as described below for Fitting holes.

For non-penetration holes that are created by a panel fitting, the ‘virtual’ hole is created as a single FIXING in a new FRMW. The fixing owns a Template (TMPL) element that owns a negative extrusion (NXTR) whose vertices describe the required hole shape. The fitting is created as a FIXING element owned by the PANE whose Spref attribute points into the catalogue to the selected fitting. An Association (ASSOC) element that references all of the hole elements is also created. Approving the hole creates an NXTR owned by the PANE that is a copy of the ‘virtual’ hole NXTR.

Non-penetration managed holes, of either type, may be associated with any other element in Design. The holes have the same request/approval process as penetration holes, however, as they are created solely by the structural discipline the Structural Designer may be both the requester and approver.

www.aveva.com

7.1.4 Use of the Hole Management Application

The Hole Management application, as with other applications that use associations, is passive, i.e. the user is not alerted if a hole association is broken or invalidated. The user must enter the Hole Management application and actively verify if the association is still valid.

The use of the application will vary from company to company. In some it may be down to the individual Designers to request and approve holes, whilst in others it may be the discipline lead Designer or a designated user who performs the tasks.

7.2 Creating the Fixing Area

The information about the hole size and position is held in a FIXIng which is held in a STRU with the purp of the STRU set to Hole, on a project this design area would be created by the project administrator.

For the purposes of the training the fixing area will need to be created.

Navigate to the SITE STABILIZER

Display the command line Display > Command Line

NEW ZONE /HOLE-MANAGEMENT PURP HOLE

NEW STRU /HOLES PURP HOLE