Configuration window

AVEVA Clash Manager™ 14.3 User Guide

Clash Manager Configuration : Configuration window

Use the AVEVA Clash Manager Configuration window to window view and to setup facilities for features of clash management.


Clash Management Feature	Associated Tab Titles
Data Access Control	Security
Automatic acceptance of certain clashes	Accept, Class*, Status
Automatic assignment of an owner discipline to a clash	Assign, Class, Discipline, Priority
AVEVA Clash Manager Access Control	Project
Clash details	Comments, Level/Type
Automatic grouping of primitive clashes	Group
Advanced Filtering options for Clash Reports	Class, Priority, Status
MDBs and GTYPEs included in Tracking Changes	Gtype/Tracking

* The Class and Priority tabs are user-definable and can be configured for any attribute or user-defined attribute associated with the clashing elements or their owning hierarchy. (The names Priority and Class illustrate the typical configuration, and are used in this Online Guide for the tabs and for any window elements that display information derived from them.)

Note:

The values of the attributes defined are stored against each clashing element in the AVEVA Clash Manager database. This additional attribute information can be used in the Assign and Accept rules.

Note:

If significant changes are made at this window, a message changes in Configuration require recomputation of Clash & Element Properties is displayed. When this message is accepted, the Clash Recomputation window is automatically displayed, refer to Recomputation for further information.

•

•

•

•

•

•

•

•

•

•

•

Use the functionality to set up details of clashes that can be automatically accepted and automatically set to a given status, such as Approved.

The clash acceptance process checks a number of rules in sequence (from top to bottom as displayed on the window). Each rule consists of a number of rule expressions. The first rule found in which all its rule expressions evaluate true is used by the acceptance process. rule expressions, which are formed of certain keywords, literals and regular expressions (wildcards) refer to Notes on Rules and Rule Expressions for further information.

The status of the clash is set to the status owning that rule. A comment is created showing details of the status and the rule which matched is automatically attached to the clash and or clash group record.

Note:

Acceptance rules may be complicated and time-consuming to develop. A simple method of testing is available to avoid a (very lengthy) Re-Computation option, which may reveal further modifications to the rules are required. The test facilities are available at the AVEVA Clash Manager -Test Rules window, which is accessed by selecting Test. The new configuration does not need to be saved prior to using the test facilities.

The names and purposes of the items on the tab are as follows:

Upper pane showing a
hierarchy with Status as
the primary nodes which,
when expanded, display the
applicable Acceptance
Rules

When an acceptance rule is highlighted, its rule syntax is shown in the lower pane.

A popup menu is available (mouse right-click) with options of Edit, Add and Delete. This is used to edit an existing rule name, add a new rule, or remove an existing rule.

Up and Down

These are used to reposition the highlighted rule in the hierarchy.

Test

Leads to the Test Rules.

Lower pane showing a list
of Rule Expressions under
Element, Attribute and
Value headings

The listing shows the syntax of the acceptance rule that is highlighted in the upper pane.

Popup menus (mouse right-click) are available from the three components of the rule expressions.

Note:

The current options are omitted from the editing options of the displayed menus and that the Esc key can be used to abort the entry in an in-place options box.

The Element Popup Menu options are:

Editing options - @element-1, @element-2, @general
Add Rule
Delete

The Attribute Popup Menu options are:

Editing options - @discipline, @class, @priority, etc, and
@gtype
Edit - leads to in-place editing options box
Add Rule
Delete

The Value Popup Menu options are:

Editing options - @element-2, and so on. Refer to Notes on Rules and Rule Expressions for further information.
Edit - leads to list-of-values
Add Rule
Delete

Assign

Use the functionality to specify the tests and order in which they are to be performed during automatic assignment of an owner discipline to a clash.

The tests can check the relative priority, class and/or discipline of each element of pairs of clashing elements. The tests can also check a number of discipline assignment rules. The testing process proceeds test-by-test until a result indicates the owner discipline of the clash. The testing process then assigns the owner discipline to that clash and continues by testing the next clash.

In the priority and class tests, the owner discipline is set to the element with the higher order. These orders are as set at the priority and class tabs, respectively.

The element discipline test is normally the last of the sequence and consequently is used when none of the other tests have produced an owner discipline. If the discipline of each clashing element is the same, that discipline is set as the owner. If the disciplines are different, the discipline default (as set at the Discipline) is used. Typically, this is UNALLOCATED.

Each rule in the discipline assignment rules consists of a number of rule expressions'. Rule expressions, which are formed of certain keywords, literals and regular expressions (wildcards), refer to Notes on Rules and Rule Expressions for further information. The first discipline with a rules whose rule expressions all evaluate true becomes the owner discipline, by default. Alternatively a set discipline keyword operator may be used in a rule expression to assign the owner discipline to that of one element or the other, or even to a third unrelated discipline.

A comment is created showing details of the discipline assigned and the rule which matched is automatically attached to the clash and/or clash group record. This comment appears in the Comments section of the Clash Report and on the Comments tab of the Clash Group Properties window.

Note:

Assignment rules may be complicated and time-consuming to develop. A simple method of testing is available to avoid a (very lengthy) re-computation option, which may reveal further modifications to the rules are required. The test facilities are available at the AVEVA Clash Manager -Test Rules window, which is accessed by selecting Test. The new configuration does not need to be saved prior to using the test facilities.

The names and purposes of the items on the tab are as follows:


Order of Application	For selecting which tests are to be performed and the order (from top to bottom) in which they are carried out. The check box against the test is checked, if the test is to be part of the sequence. The records show the name of the tests. Assignment Rules means Apply the Discipline Assignment Rules.
Up and Down	For setting the sequence of records as displayed from top to bottom of the pane and hence the sequence of the tests.

Discipline Assignment Rules pane containing:

Discipline Assignment
Rules pane showing a
hierarchy with Discipline
as the primary nodes
which, when expanded,
display the applicable
Assignment Rules

When an assignment rule is highlighted, its rule syntax is shown in the lower pane.

A Popup menu is available (mouse right-click) with options of Edit, Add and Delete. This is used to edit an existing rule name, add a new rule, or remove an existing rule.

Up and Down

These are used to reposition the highlighted rule in the hierarchy and hence determine the sequence (from top to bottom) in which the rules are applied.

Test

Displays the Test Rules.

Lower pane showing a list
of Rule Expressions under
Element, Attribute and
Value headings

The listing shows the syntax of the assignment rule that is highlighted in the upper pane.

Popup menus (mouse right-click) are available from the three components of the Rule Expressions.

Note:

The current options are omitted from the editing options of the displayed menus and that the Esc key can be used to abort the entry in an in-place options box.

The Element Popup Menu options are:

Editing options - @element-1, @element-2, @general
Add Rule
Delete

The Attribute Popup Menu options are:

Editing options - @discipline, @class, @priority, etc, and
@gtype
Edit - leads to in-place editing options box
Add Rule
Delete

The Value Popup Menu options are:

Edit - leads to list-of-values
Add Rule
Delete

Example of Assignment Rules

The order of the tests is assignment rules, priority, class and finally element discipline, the testing process is as follows:

The assignment rules are applied, the first rule in which all rule expressions evaluate true is used to determine the owner discipline.

If no assignment rule is satisfied, the classes of the elements are checked. If the classes are different, the element with the higher class determines the owner discipline. (The illustration shows this test disabled, because the check box is unchecked.)

If the classes are the same, if the priorities of the clashing elements are different, the element with the higher priority determines the owner discipline. (The illustration shows this test disabled, because the check box is unchecked).

If the priorities are the same, the element disciplines are checked. If the disciplines are different, the default discipline, typically UNALLOCATED becomes the owner discipline. Otherwise, the discipline common to both elements becomes the owner.

Note:

It is useful to apply the tests, even if the discipline of both clashing elements is the same, because the owner discipline highlighted in the Clash Report may well represent the element that must be moved to resolve the clash, based on the relative priorities or classes of the elements.

Class

Use the functionality to specify classes that are used in auto-acceptance and auto-assign-to-discipline rules for clash ownership. The Class tab is also used to set the classes in the order they are to be considered, when the relative importance of the class of each element within a clash is the subject of an automatic acceptance or assignment process

The functionality enables the values of an attribute to be associated with the values of the Plant class attribute for the purpose of automatic assignment of a class to a clash.

Note:

This configuration is separate from the Project Defined Field configuration on the Project tab.

The pane at the top of the tab enables a particular Plant Class Description and its Attribute Value to be selected. A Popup Menu is available (mouse right-click) with options of Edit, Add and Delete. This is used to edit an existing class, add a new class, remove an existing class, or set an existing class as default. The description is user-defined, the attribute value must match the attribute value for the particular class.

The associated Up and Down buttons are for rearranging the order of the classes, from top to bottom. The least important class is at the top; the most important at the bottom. From a pair of clashing elements, the auto-assignment process selects the discipline of the less important element to be the owner of the clash, that is, the element with the class that is nearer to the top of the list.

The Description field is for specifying the text to appear as the report column header for the attribute values.

The Attribute box enables the attribute associated with the selected class attribute value to be specified. AVEVA Clash Manager will search for the attribute on the clashing item, and if not found there, will search the owning hierarchy for it.

Note:

If Not Used is selected, the CLASS attribute does not appear in the AVEVA Clash Manager UI. CLASS is designed to produce a modest number of look-up records, when a value is used as a wildcard. An attribute, such as a NAME that would return a large number of values should not be used.

To automatically produces a list of class descriptions and attributes that are applicable to elements in clashes that have been discovered by AVEVA Clash Manager, select Discover.

Each description of the various classes is formed by a concatenation of the attribute name followed by the particular attribute value. For example, for an attribute type and a value BEND, the description is type BEND. Each listed attribute value is available as a Regular Expression wildcard (refer to Notes on Wildcards for further information) for use in assignment and acceptance rules. The values are preceded by ^ and followed by $ to make sure that only complete strings are matched, for example, ^BEND$.

Comments

The functionality specifies the pre-defined comments that can be assigned to a clash.

The pane on the tab displays Comments associated with a particular Discipline. A Popup Menu is available (mouse right-click) with options of Add, Edit and Delete. This is used to add a new comment, edit an existing comment, or remove an existing comment. The associated Up and Down buttons are for rearranging the sequence of comments.

Discipline

The Discipline tab is concerned with associating the values of a selected attribute with the values of Plant discipline attributes for the purpose of automatic assignment of an owner discipline to a clash.

The pane at the top of the discipline tab displays the list of disciplines and their attribute values and, except for AVEVA Clash Manager, are read-only. For AVEVA Clash Manager, a Popup Menu is available (mouse right-click) with options to Add, Edit, Delete and Set as Default. This is used to add a new discipline, edit an existing discipline, remove an existing discipline and automatically set a discipline as default. Use to create the list of disciplines and their attributes that AVEVA Clash Manager can match with the values of the specified attribute.

It is necessary to tell AVEVA Clash Manager how to identify a discipline from a clashing element’s attributes or its owner’s attributes. The Attribute box enables this functionality by specifying the particular attribute that, when evaluated, matches one of the attribute values shown in the right-hand column in the discipline table. For example, an :MMSDISC value of 'P' would normally correspond to the 'P' set as the attribute of discipline 'Piping'. AVEVA Clash Manager will search for the attribute on the clashing item, and if not found there, will search the owning hierarchy for it.

Note:

If Not Used is selected, the attribute does not appear in the AVEVA Clash Manager GUI, but the default discipline will be UNALLOCATED, unless set otherwise, by the drop-down list.

If a match is found then that discipline is associated with the clashing element, otherwise the clash is assigned to a default discipline selected from the Default drop-down list. If a clashing element does not match any of the specified values then it is set to a special discipline called UNALLOCATED.

Note:

This configuration is separate from the Project Defined Field configuration on the Project tab.

Group

Many clashes may exist between pairs of significant elements. The clashes exist at lower levels in the hierarchy, that is at the primitive level. These low level clashes may be grouped together and selected for viewing, reporting and approval as a single entity, namely, as a clash group.

The functionality specifies aspects of clash groups, and the level in the hierarchy at which the clashes are reported.

The items on the Group tab are as follows:

The Group Clashes between element pairs within +/- field and associated mm/inch dimension radio group are for specifying the proximity of primitive clashes to be reported as a group. Because the specified values are plus or minus, the coordinate dimensions of the volume in which the clashes are considered to be a group are each twice the stated value. The default setting for the group distance between element pairs is 100mm, but it is common practice to have this value changed to 2000mm to make the clash grouping more effective. The decision to change the distance should be done only in consultation with the project discipline lead designers. The distance setting can be changed at any time during the project life cycle, but the clash groups must then be recomputed. Making fundamental changes to the group settings mid-project is not a recommended practice.

The Default Group Level drop-down lists are used to specify the level in the hierarchy at which the clashes are grouped within the appropriate discipline. For example, clashes within a pipe, may be reported at primitive level, at the branch level or at the pipe level. The defaults are PIPE-PIPE, EQUI-EQUI, STRU-SCTN, HVAC-HVAC, REST-REST and normally these are used. Clashes in other disciplines such as Hull and Room Design do not default to single levels and are handled by Group Rules described below.

The pane at the bottom of the Group tab is for specifying exceptions to the default group levels. The exceptions are defined under headings of GTYPE, Attribute, Value and Group Level. A Popup Menu is available (mouse right-click) with options of Add, Edit and Delete, used to add a new GTYPE and details, edit an existing GTYPE details, or remove an existing record. Up and Down buttons at the right-hand side of the pane are used to position the highlighted record in the list and hence determine its priority.

Note:

Before selecting a GTYPE that is not at a group level, make it a Controlled GTYPE first, refer to Test Rules.

A Group Rule with GTYPE * will allow clashes to be grouped at the level of any type entered under Group Level. For example, to group clashes with Hull objects at any of HPANEL, CPANEL, BLEVEL or BBLOCK, create four rules with entries as: GTYPE *, Attribute and Value left blank, Group Level HPANEL in the first rule, Group Level CPANEL in the second rule, and so on.

Other examples for Cableway and Room Design objects are shown in the picture above. The entry with GTYPE * and Group Level CWAY will group all clashes below cableways to the owning cableway. The entry with GTYPE * and Group Level ROOM will group all clashes below rooms to the owning room. The entry with GTYPE CTWALL and Group Level CTWALL will group clashes with constant thickness walls at that level, but note that clashes with CTWALL objects below ROOM objects will be grouped at ROOM level due to the earlier rule.

Contiguous group rules with identical expressions are combined and tested at each level so that if given groups contain one another, the lowest in the hierarchy is used. A group rule with a specific GTYPE or with different expressions will end that combining process (but may begin another).

Gtype/Tracking

The Gtype/Tracking tab enables the administrator to specify which MDBs and controlled GTYPEs are to be included in a Track Changes operation. Additionally, it provides facilities for specifying Tracking Selection Rules that further restrict the range of controlled GTYPEs to be included in the operation.

Controlled GTYPE

The top pane displays a listing under headings of GTYPE and State. The listing is used to present a list of available GTYPEs and to enable certain of them to be made Controlled or Uncontrolled. (Only a Controlled GTYPE is the subject of a Track Changes operation.)

Further GTYPEs can be added at this window and these can be made controlled or uncontrolled, or deleted, as required. A popup menu is available for this purpose. Its options are as follows:


Add	For adding another GTYPE immediately below the currently selected GTYPE. Leads to an in-place edit window at which the GTYPE can be entered. (Note that the Esc key can be used to abort the entry in the in-place window.)
Control	Makes the selected GTYPE controlled or uncontrolled
Delete	Removes the selected GTYPE from the list.

Examples for hull, room design and cableway objects are shown in the picture above, with CPANEL, CTWALL and CWAY made Controlled GTYPEs.

Note:

Make a GTYPE Controlled before selecting it in a Group Rule first, refer to Group for further information.

Tracking Selection Rules

The bottom pane is available for specifying rules that further restrict the range of GTYPES to be included in the Track Changes operation. For the syntax of the Tracking Selection Rules refer to Notes on Element Rule Syntax for further information.

Note:

Any GTYPE (for eaxmple: BBLOCK, BLEVEL) included in a rule must first be added to the GTYPE list even if it is not to be Controlled.

It is important that the Selection Rules, when evaluated, return a list of unique items.

A popup menu is available, the options and their purposes are as follows:

Add

For adding items or expressions to the particular list, displays an in-place edit window, at which the item or expression can be entered.

Note:

The Esc key can be used to abort the entry in in-place windows.

Edit

For editing the selected expression, displays an in-place edit window, at which the expression can be edited.

Browse

For adding elements derived from the hierarchy.

Delete

Deletes the selected item from the list, the item is not deleted from the 3D model.

Evaluate

Evaluates the selection rules for each of the checked MDBs. A window is displayed populated with a consolidated listing of the results. In the absence of any rules, the window displays a list of all SITEs in each of the checked MDBs.

Level/Type

Use the functionality to specify the relative order of clash level/type combinations, the order is used to compute the worst case clash of a Group.

•

•

•

•

•

•

•

Insulation/Insulation

•

Insulation/Soft

•

Soft/Soft

•

Not Proven.

The names and purposes of the items on the tab are as follows:

Pane listing level/type
combinations under Clash
Level and Clash Type

Note:

There is no popup menu available for modification of the pane contents. The selected level/type combination can be moved up or down the list by means of the Up or Down buttons.

Up and Down

For setting the sequence of Level/Type combinations, as displayed in the pane and hence the order of worst case selection. The worst case is at the top of the list. Generally, there is no need to redefine the default order.

Note:

For brevity, Clash Level is abbreviated in the Clash Reports as follows:


Abbreviation	Clash Level Description
HH	Hard/Hard
HI	Hard/Insulation (or Insulation/Hard)
HS	Hard/Soft (or Soft/Hard)
II	Insulation/Insulation
SS	Soft/Soft
NP	Not Proven

Priority

Use the functionality to specify priorities that are used in auto-acceptance and auto-assign-to-discipline rules for clash ownership. It is also used to set the priorities in the order they are to be considered, when the priority of each element within a clash is the subject of an automatic acceptance or assignment process.

The Priority tab enables the values of an attribute to be associated with the values of the Plant priority attribute for the purpose of automatic assignment of a priority to a clash.

Note:

This configuration is separate from the Project Defined Field configuration at the Project tab.

The pane at the top of the tab enables a particular Priority Description and its Attribute Value to be selected. A Popup Menu is available (mouse right-click) with options of Add, Editing, Delete. This is used to add a new priority, edit an existing priority, or remove an existing priority. The description is user-defined, the attribute value must match the attribute value for the particular priority.

The associated Up and Down buttons are for rearranging the order of the priorities, from top to bottom. The least important priority is at the top; the most important at the bottom. From a pair of clashing elements, the auto-assignment process selects the discipline of the less important element to be the owner of the clash, that is, the element with the priority that is nearer to the top of the list.

The Description field is for specifying the text to appear as the report column header for the attribute values.

The Attribute box enables the priority attribute to be selected. AVEVA Clash Manager will search for the attribute on the clashing item, and if not found there, will search the owning hierarchy for it. If Not Used is selected, the PRIORITY attribute does not appear in the AVEVA Clash Manager GUI. Note that PRIORITY is designed to produce a modest number of look-up records, when a value is used as a wildcard. An attribute, such as a NAME that would return a large number of values should not be used.

Discover automatically produces a list of priority descriptions and attributes that are applicable to elements in clashes that have been discovered by AVEVA Clash Manager. Each Description of the various priorities is formed by a concatenation of the attribute name followed by the particular attribute value. For example, for an attribute 'priority' and a value 10, the description is 'priority 10'. Each listed attribute value is available as a Regular Expression wildcard (refer to Notes on Wildcards for further information) for use in assignment and acceptance rules. The attribute values are preceded by ^ and followed by $ to make sure that only complete strings are matched, for example, ^10$.

Following operation of the Discover button to determine all available values, the resultant data can be edited to give acceptable ranges of priorities. For example, returned priorities with values of ^10$ through ^19$ could be edited to a single description Low Priority with a value ^1[0-9]$.

Project

Use the functionality to enter project-wide details.

The Project Title, Client, Project Number, Project, Userid, Password fields at the top of the tab are for entry of those project details.

Note:

Each clash set has its own MDB definition used for entry during a clash set run.

Use the Display Units section to select the units in which the values are to be displayed in AVEVA Clash Manager.

The Apply Group Changes to Clash Detail drop-down list enables the administrator to specify the policy for the project. The selection made here determines whether or not the user can use the facility on the AVEVA Clash Manager Options window to choose whether or not group changes are applied to clash details within a group.

The options of the drop-down list are:

•

Always - group changes are always applied and the user cannot change the policy (recommended)

•

Never - group changes are never applied and the user cannot change the policy

•

Free - the user can choose whether or not group changes are applied.

The items in the Project Field are for selecting an attribute, the value of which is to be added to the clash report for each clashing item. This additional data is useful for filtering and sorting purposes in the main body of the report.

The Attribute Name field is for specifying the name of the attribute, for example: AREA. AVEVA Clash Manager will search for the attribute on the clashing item, and if not found there, will search the owning hierarchy for it.

The Description field is for entering the attribute value that appears in the Clash Report.

The Default field is for specifying a default value for the attribute if the attribute is not set.

An example of how an attribute can be used is as follows. Many companies use PURPose as the Attribute Name and the Zone radio button selected for capturing the description of a ZONE’s content over and above the naming convention. The ZONE is named with the Piping Specification PSPE and the Attribute Name PURPose is given a Description PROC for Process Piping and UTIL for Utility Piping. AVEVA Clash Manager then filters the clash report based on these values.

Note:

The Class, Discipline and Priority tabs have groups of items similar to those in the Project Defined Field box and which have similar functionality.

Security

The functionality available enables the administrator to update and view the overall security arrangements for AVEVA Clash Manager. For details of the security arrangements, refer to Access Rights.

The Security tab displays one of four panes for setting Security Levels (namely, Status, Owner discipline, Check CE, Comments and User Access Levels), The particular security level pane is selected by clicking the appropriate icon displayed in the Security tab window.

Status, Owner, Check CE and Comments Panes

The layout of each pane is the same, but the messages displayed are appropriate to the selected Security Level.

Across the top of the pane, the selected icon and a description of the Security Level are displayed.

The elements displayed in the centre of the pane, depend on whether the pre-defined or custom settings are being used. When pre-defined settings are being used, a slider control enables the security to be set to one of the five states namely, High, Medium High, Medium, Medium Low and Low. The name of the selected state and a narrative statement of its effect appear to the right-hand of the slider control. The default state for each security level is Medium. When custom settings are being used, the pane displays the message: 'Custom - To change the settings, click Custom Level - To use the recommended settings, click Default Level'.

At the bottom of the pane are two buttons. The Custom Level button leads to the 'AVEVA Clash Manager - Security Settings' window, at which the pre-defined settings for the particular Security Level can be superseded by custom (user-defined) settings. The Default Level button is for selecting the default state.

For each Security Level there are five pre-defined states namely, High, Medium High, Medium, Medium Low and Low. Each of these states has corresponding settings (minimum requirements). The default State for each Security Level is Medium and this is used as the guideline when access rights are mentioned in the AVEVA Clash Manager Procedures.

As required, the Administrator may override the pre-determined settings by specifying custom settings for one or all of the Security Levels.

The pre-determined States and Settings are detailed in the following tables.


Security Level - Status
State	Setting - description of minimum requirements
High	Supervisor of ADMIN discipline
Medium High	Supervisor of Owner discipline and Member of ADMIN discipline
Medium (the default)
Medium Low	Member of Owner discipline
Low	Member of ANY discipline involved in Clash

Security Level - Owner

State

Setting - description of minimum requirements

High

Supervisor of ADMIN discipline

Medium High

Supervisor of other discipline and Member of ADMIN may Acquire Ownership

Supervisor of current discipline and Member of ADMIN may impose ownership

Medium (the default)

Supervisor of other discipline may Acquire Ownership

Supervisor of current discipline and Member of ADMIN may impose ownership

Medium Low

Supervisor of other discipline may Acquire Ownership

Supervisor of current discipline may impose ownership

Low

Member of ANY discipline involved in Clash

Note:

Only the Supervisor of ADMIN discipline may impose ownership on a discipline not directly involved.

Security Level - Clash Check CE

State

Setting - description of minimum requirement

High

Supervisor of ADMIN discipline

Medium High

Member of ADMIN discipline

Medium (the default)

Supervisor of CE discipline

Medium Low

Member of CE discipline

Low

Member of ANY discipline

Note:

Clash Check CE automatically creates and runs a personal Clash Set. A suitable level of security is important in order to maintain some control of the growth of Clash Sets


Security Level - Comments
State	Setting - description of minimum requirement
High	Supervisor of ADMIN discipline Supervisor of ANY discipline involved in Clash and Member of ADMIN discipline
Medium High	Supervisor of ANY discipline involved in Clash
Medium (the default)	Member of ANY discipline involved in Clash
Medium Low	Member of ANY discipline
Low	Anybody

User Access Levels

The User Access Levels pane of the Security tab enables the selection of Users and their access levels. It displays a single pane on which the access arrangements are shown in tree format. The major nodes of the tree are Users and Disciplines.

User membership of a discipline is granted by dragging the discipline and dropping it onto a user name. Alternatively, the discipline can be selected from a right click menu. Similarly, a user name may be dropped onto a discipline.

A checkbox is located against the left-hand side of each user and discipline symbol. Supervisor rights are shown in the tree by a checked box against the discipline under the user and by a checked box against the user under the discipline.

Security Settings

From the Security tab of the AVEVA Clash Manager - Configuration window, select Custom Level to display the AVEVA Clash Manager - Security Settings window. Use the window to specify custom (user-defined) settings that can take the place of the pre-defined settings for a particular Security Level, refer to Access Rights for further information.

The elements of the window and their purposes are:


Pane displaying a tree of checkboxes	Top check box labelled with the Security Level	To show which security level being customised. The check box is always checked.
	Eight check boxes labelled with combinations of member, supervisor and discipline	These are initially populated as for the settings currently in use. The administrator can select (tick) and deselect (clear) the check boxes to reflect the customised minimum requirements for a user who is allowed to perform tasks at the particular Security Level.
	Check box labelled Nominated Users	This check box can be selected in addition to any selected above. When the check box is ticked, a branch of check boxes labelled with user names is displayed. Ticking a check box in the branch, unconditionally allows the particular user to perform tasks at the particular Security Level. Leaving a check box blank, bars the user from performing the tasks.
	Bottom check box labelled Unrestricted	When this check box is checked, any user can perform tasks at the particular Security Level.
Reset Custom Settings	Reset to:	For selecting the appropriate state, when the custom settings are to be reset to pre-defined settings.
Reset		For resetting the customised settings to the pre-defined settings for the State selected in the drop-down list.

Status

Use the functionality to display a listing of the standard status and enables user-defined status to be entered within the list. It also enables a restriction to be placed on who can update a clash from or to particular status.

Also use to specify the default status to be allocated to new clashes that do not satisfy auto-acceptance rules.

The standard status cannot be removed, and sequence in which they are displayed signifies their order of priority, when 'worst case' clash details are evaluated by the system. The sequence cannot be changed, but user-defined status can be inserted into the list.

The pane at the top of the tab displays the various status details under Description, State and Access. A Popup Menu is available (mouse right-click) with options of Add, Edit, Delete and Set Default.

For standard status, the Description and State entries are identical, namely, Unknown, Unapproved, Pending, Conditional and Approved, and are read-only. The standard status values are explained below:


Unknown	An initial or default status applied to new clashes if none of the automatic acceptance rules are triggered. The default status for a clash can be configured.
Unapproved	The clash has not been reviewed and remains as a valid or outstanding clash for the project
Pending	This status is used to indicate that the clash is currently under review by the design teams
Conditional	This status is used to indicate that the clash has been reviewed and resolved in the 3D model. This also implies that following the next clash run this clash will no longer appear in the clash report. For reporting purposed this status implies a resolved clash.
Approved	This status is used to indicate that the clash has been reviewed and is considered acceptable by the design team. The clash will continue to be reported in subsequent clash runs but its approved status will remain with the clashing items throughout the remainder of the project lifecycle. If an element has only ‘Approved’ clash status in the database then it is considered ‘Clash Free’.

For user-defined status, the Description can be any text; the State must represent a standard status.

The Access defines who can apply the particular status to a clash or change a clash from the particular status to another. This access restriction is in addition to any set at the Security tab. Access can be set to a discipline, in which case, only a user who has supervisor rights to that discipline can change the status. The alternative access settings are blank or 'Any', both of which signify that there is no access restriction, other than that set at the Security tab.

The Default Status (for New Clashes) drop-down list is for specifying the status to be applied to new clashes that are not automatically accepted.

Test Rules

Use the AVEVA Clash Manager - Test Rules window to test assignment and acceptance rules before they are applied to the whole 3D model by the Recomputation process. The window enables a subset of existing clash records to be selected in order to display what would happen if the current rules were applied to the 3D model. The window is intended to aid configuration; it does NOT allow the evaluated status or discipline of the selected clash records to be saved.

A group of elements at the top of the window enables the selection of the clash groups or details and then apply the new rules to them. The main area of the window is occupied by tabulated records showing the results of the selection and evaluation.

The elements at the top of the window and their purposes are:


Group / Detail radio group and Element Name % Wildcard	For selection of the subset of clash records. The radio group is for selection of whether clash groups or details are to be tested. The entry in the field determines the range of clashing elements. Oracle style wildcards are used (refer to Notes on Wildcards for further information).
Query	Interrogates the 3D model and displays records of the clash groups or details that match the entry in the 'Element Name % Wildcard' field.
Evaluate Rules	Applies the new rules to the displayed records and shows the new owner disciplines and status.

The tabulated records show, for each clash group or clash detail that satisfies the selection criteria, information under the following headings:


Group	The group identification. Populated after Query.
Index (clash details only)	Clash identification number. Populated after Query.
Element 1	First element of the clash. Populated after Query.
Element 2	Second element of the clash. Populated after Query.
Discipline	Owner discipline according to existing rules. Populated after Query.
Status	Status according to existing rules. Populated after Query.
New Discipline	Blank after Query. Populated after rule evaluation. Shows owner discipline as assigned by the new rules. The name of the rule is shown for NEW clashes only.
New Status	Blank after Query. Populated after rule evaluation. Shows the status as applied by the new acceptance rules. The name of the rule is shown for NEW clashes only.
CLevel	Populated after Query, shows the clash level.
CType	Populated after Query, shows the clash type.
Discipline 1	Discipline of first element, populated after Query.
Discipline 2	Discipline of second element, populated after Query.
Remarks	Blank after Query. Populated after rule evaluation, shows a narrative description of the clashing elements.

A popup menu is available from the tabulated records. The options and their purposes are as follows:


Query	Interrogates the 3D model and displays records of the clash groups or details that match the entry in the 'Element Name % Wildcard' field.
Evaluate Rules	Applies the new rules to the displayed records and shows the new owner disciplines and status.
Properties	Available only when a record is selected. Leads to the 'AVEVA Clash Manager - Clashing Elements - Properties' window, which displays values of all attributes that may be involved in the setting of discipline or status of the elements in the selected record.

The procedure for using the window is firstly to select clash group or detail and enter an element name and wildcard to represent elements that will be affected by the updated rules. Initiate the Query and then check the displayed records to make sure that they represent the required typical elements. If they do not, re-enter element and wildcard details and re-query the data. When the records are as required, apply the new rules and check whether the results are as required. Close the window by clicking on the X at the top right-hand corner. Take action at the AVEVA Clash Manager - Configuration window to correct or implement the new rules, as appropriate.

Note:

A rule such as "@element-2 NAME @element-1" will only ever be true for Group elements, for example PIPE against PIPE, as that is the only case where NAMES could be the same or a rule such as "@element-2 NAME of PIPE @element-1" is effective for any element in the hierarchy at or below a PIPE so will work equally well for Group and Detail.

Note:

The TEST evaluation of group status applies the rules against the given pair of group elements. However, that during an actual clash run, the status of all clash detail belonging to the group is also evaluated. The status of a group may be overridden by a detail status if it is worse than the given group status.