Common Functionality
Hole Management System : Addition of Managed Holes : Project Configuration for Hole Management
Project Configuration for Hole Management
A project must be correctly configured in order to use the hole management system. Things to consider are:
•
The hole management add-in file
•
Hole management association definitions
•
Configuring catalogues for hole management
•
Configuring equipment for use with the hole management system
•
Storage areas for hole management data
Hole Management Add-in File
The Multi Disciplinary Penetrations and Hole Management application is a PML addin application. If required, this can be disabled by either commenting out the addin commands with the # comment character in the file PMLUI/des/addins/holemanagement or by deleting the file.
Hole Management Association Definitions
The hole management system uses a set of Association Definitions which must be loaded in the project for the system to work. These Association Definitions are provided in the sample master project in Association Definition world (ASDFWL) /HM-ASSDEF.
Configuring Catalogues for Hole Management
The hole management system requires that a set of standard catalogue hole definitions are loaded in the project for the system to work. Standard catalogue hole definitions are provided in the sample master project in part world (PRTWLD) /HM-FIXI-PTWLD and catalogues (CATA) /HM-FIXI-CATA and /HM-FIXI-COAMING-CATA.
Fixings
The hole definitions are accessed from GPART elements with a PURP equal to HOLE and PRITYPE equal to FIXING. The SECTYPE attribute is set to describe the different hole shapes. The description displayed in the window is obtained from the RTEXT of the DETREF of the GPART.
In some cases the hole is rotated around its origin. To allow the orientation of holes a special ppoint has been created. The ppoint needs to have a PURP set to HMOR and can have any ppoint number. If the PURP is not set the ppoint number must be set to 9.
If these criteria for Fixing elements are not met, the hole management system does not function.
Coaming
The coaming definitions are accessed from GPART elements with a PURP equal to HOLE and PRITYPE equal to COAMING. The SECTYPE attribute is set to describe the different hole shapes and must match up with the equivalent FIXING. In some cases the hole is rotated around its origin. To allow the orientation of holes a special ppoint has been created. The ppoint needs to be have a PURP set to HMOR and can have any ppoint number. If the PURP is not set the ppoint number must be set to 9.
If these criteria for Coaming elements are not met, the hole management system still functions but the coaming option is greyed out.
Configure Equipment for Use With the Hole Management System
Equipment penetrations require specific elements to be created within the equipment hierarchy to represent the hole that is required when an equipment item penetrates a panel. The penetration required is represented by an extrusion element (EXTR or NXTR) stored in the equipment hierarchy. The element contains a loop element (LOOP) and vertices (VERT elements) to define the shape of the hole required. Which is called the penetration profile.
The extrusion to be used as the penetration profile is first created in the equipment or design template, and is then identified using the Identify Penetration Shape window. The window creates two elements owned by the equipment or design template element. The first is a Port Set (PORS) element that must have its Purpose attribute set to HOLE, which owns a port (PORI) element which has a reference to the penetration profile extrusion.
Storage Areas for Hole Management Data
Hole management data is stored in various locations in product Design data in order to allow System Administrators to restrict cross-discipline access to Design model data. For example, a piping user can request a penetration in a steel panel, and a structural user can create a hole in response to that request without requiring write access to each others data.
The storage areas required are:
•
Hole Management Associations - the area that records the links between all elements in a penetration
•
Virtual Hole storage area - where data about the shape of a requested penetration is stored
•
Coaming storage area - where the coaming items are stored.
Hole management associations are stored in an Association World that contains an Association Group (ASSOGP) with PURPOSE attribute set to HOLE. Storage of hole management associations can be distributed to different databases by using Data Access Control functions to restrict user access to certain Association Groups. The system stores hole management associations in the first hole management association group (Purpose=HOLE) where you have permission to create Association (ASSOC) elements.
Virtual Holes are stored as FIXING elements under Framework (FRMW) elements. These storage areas are identified by the STRU element having PURPOSE set to HOLE. Coaming is stored in STRU elements with PURPOSE set to HMCM. Storage of Virtual Hole Fixings and Coaming is controlled in the same way as hole management associations.
Note:
Users approving holes must have write access to hole management associations.
Configuring Pipe Penetration Components
Pipe penetrations components are COUP elements. Penetrations components that do not need to be positioned on a penetrated plate surface do not need special treatment, for example a pipe sleeve positioned at the penetration position.
If the component is placed on a surface of the penetrated plate. It must conform to the following rules:
The GTYPE is COUP
The COMPTYPE of the component must be set to ORIC
The component must support four design parameters as follows:
The component must have a P3 pointing in a direct normal to the plate surface. Which points in the direction specified by design parameters 1 to 3.
The offset (design parameter 4) is the distance along the pipe of the arrive and leave p-points from the origin of the COUP which is in the centre of the plate.
In the sample project, an example of a pipe penetration component can be found in category /MACB2OR.
1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.
AVEVA Logo