0% found this document useful (0 votes)

58 views88 pages

TM-1874 AVEVA Everything3D™ (2.1) - Clash Manager Administration Rev 1.0

It is the best source to learn clash manager of e3d.

Uploaded by

majvand

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

58 views88 pages

TM-1874 AVEVA Everything3D™ (2.1) - Clash Manager Administration Rev 1.0

It is the best source to learn clash manager of e3d.

Uploaded by

majvand

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 88

Training TM-1874

AVEVA Clash Manager™ 14.1

Guide Clash Manager Administration
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

Copyright © 2016. 2 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

Revision Log

Date Rev Description Author Reviewed Approved

04/04/2016 0.1 Issued for Review Clash Manager™ 14.1 JD

10/08/2016 0.2 Reviewed JD JG
26/08/2016 1.0 Approved for Training JD JG KB

Updates
Significant changes to content have been made for AVEVA Clash Manager 14.1. Due to the scope and scale
of these changes they have not been highlighted.

For smaller changes, change highlighting will be employed in future revisions. Where new or changed
information is presented section headings will be highlighted in Yellow.

Suggestion / Problems
If you have a suggestion about this manual or the system to which it refers please report it to AVEVA Training
& Product Support at [email protected]

This manual provides documentation relating to products to which you may not have access or which may not
be licensed to you. For further information on which products are licensed to you please refer to your licence
conditions.

Visit our website at http://www.aveva.com

Disclaimer
1.1 AVEVA does not warrant that the use of the AVEVA software will be uninterrupted, error-free or free
from viruses.

1.2 AVEVA shall not be liable for: loss of profits; loss of business; depletion of goodwill and/or similar
losses; loss of anticipated savings; loss of goods; loss of contract; loss of use; loss or corruption of
data or information; any special, indirect, consequential or pure economic loss, costs, damages,
charges or expenses which may be suffered by the user, including any loss suffered by the user
resulting from the inaccuracy or invalidity of any data created by the AVEVA software, irrespective of
whether such losses are suffered directly or indirectly, or arise in contract, tort (including negligence)
or otherwise.

1.3 AVEVA's total liability in contract, tort (including negligence), or otherwise, arising in connection with
the performance of the AVEVA software shall be limited to 100% of the licence fees paid in the year
in which the user's claim is brought.

1.4 Clauses 1.1 to 1.3 shall apply to the fullest extent permissible at law.

1.5 In the event of any conflict between the above clauses and the analogous clauses in the software
licence under which the AVEVA software was purchased, the clauses in the software licence shall
take precedence.

Copyright © 2016. 3 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

All intellectual property rights, including but not limited to, copyright in this Training Guide and the associated
documentation belongs to or is licensed to AVEVA Solutions Limited or its affiliates.

All rights are reserved to AVEVA Solutions Limited and its affiliates companies. The information contained in
this Training Guide and associated documentation is commercially sensitive, and shall not be adapted, copied,
reproduced, stored in a retrieval system, or transmitted in any form or medium by any means (including
photocopying or electronic means) without the prior written permission of AVEVA Solutions Limited. Where
such permission is granted, AVEVA Solutions Limited expressly requires that the Disclaimer included in this
Training Guide and this Copyright notice is prominently displayed at the beginning of every copy that is made.

Licenses issued by the Copyright Licensing Agency or any other reproduction rights organisation do not apply.
If any unauthorised acts are carried out in relation to this copyright work, a civil claim for damages may be
made and or criminal prosecution may result.

AVEVA Solutions Limited and its affiliate companies shall not be liable for any breach or infringement of a
third party's intellectual property rights arising from the use of this Training Guide and associated
documentation.

@AVEVA Solutions Limited 2016

Trademark Notice

AVEVA™, AVEVA Everything3D™, AVEVA E3D™, [AVEVA Tags], Tribon and all AVEVA product and service
names are trademarks of AVEVA Group plc or its subsidiaries

Use of these trademarks, product and service names belonging to AVEVA Group plc or its subsidiaries is
strictly forbidden, without the prior written permission of AVEVA Group plc or AVEVA Solutions Limited. Any
unauthorised use may result in a legal claim being made against you.

Fluent is a trade mark of Microsoft Corporation. The Fluent user interface is licensed from Microsoft
Corporation by AVEVA and use of the Fluent trademark is strictly forbidden.

All other trademarks belong to their respective owners and cannot be used without the permission of the
owner.

Copyright © 2016. 4 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
CONTENTS

1 Introduction ............................................................................................................................ 7
1.1 Aim ..................................................................................................................................................... 7
1.2 Objectives .......................................................................................................................................... 7
1.3 Prerequisites ..................................................................................................................................... 7
1.4 Course Structure ............................................................................................................................... 7
1.5 Using this guide ................................................................................................................................ 8
2 Installation of AVEVA Clash Manager................................................................................... 9
Exercise 1 AVEVA Clash Manager Installation ................................................................................ 12
3 Clash Manager Project Configuration................................................................................. 13
3.1 AVEVA Clash Manager Project creation wizard .......................................................................... 13
Exercise 2 AVEVA Clash Manager Wizard ....................................................................................... 17
4 Clash Manager Settings ....................................................................................................... 19
4.1 Starting AVEVA Clash Manager .................................................................................................... 19
4.2 AVEVA Clash Manager Settings .................................................................................................... 20
4.3 Project Details ................................................................................................................................. 21
5 Security Settings .................................................................................................................. 23
5.1 Security Levels ................................................................................................................................ 23
5.1.1 Clash Status Security Level ....................................................................................................... 24
5.1.2 Discipline Ownership Security Level ......................................................................................... 25
5.1.3 Clash Check Current Element Security Level ........................................................................... 26
5.1.4 Comments Security Levels ........................................................................................................ 26
5.1.5 Custom Security Levels ............................................................................................................. 27
5.2 User Access .................................................................................................................................... 28
5.2.1 Creating Users ........................................................................................................................... 29
5.2.2 Granting Discipline Membership................................................................................................ 29
5.2.3 Granting Discipline Supervision ................................................................................................. 30
5.2.4 Administrator privileges ............................................................................................................. 30
Exercise 3 Security Settings .............................................................................................................. 31
6 Elements and Clash Disciplines.......................................................................................... 33
6.1 Element Discipline Allocation ....................................................................................................... 33
6.1.1 Creating a new Discipline .......................................................................................................... 34
6.1.2 Discipline Allocation Attribute .................................................................................................... 35
6.1.3 Saving new settings ................................................................................................................... 36
Exercise 4 Creating Disciplines ......................................................................................................... 37
6.2 Clash Discipline Assignment ........................................................................................................ 38
6.2.1 Activate and order categories of rules ....................................................................................... 39
6.2.2 Discipline Order ......................................................................................................................... 39
6.2.3 Assignment Rules ...................................................................................................................... 39
6.2.4 Assignment Rules – A Worked Example ................................................................................... 41
6.2.5 Testing the rules ........................................................................................................................ 42
Exercise 5 Assignment Rules ............................................................................................................ 45
7 Clash Priority and Class ...................................................................................................... 47
7.1 The Priority tab ................................................................................................................................ 47
7.1.1 Create a new Priority ................................................................................................................. 48
7.1.2 Ordering the Priorities ................................................................................................................ 48
7.1.3 Priority Lookup Value ................................................................................................................ 48
Exercise 6 Clash Priority .................................................................................................................... 50
7.2 The Class tab ................................................................................................................................... 51
7.2.1 Create a new Class ................................................................................................................... 51
7.2.2 Ordering the Classes ................................................................................................................. 52
7.2.3 Class Lookup Value ................................................................................................................... 52
Exercise 7 Clash Class ....................................................................................................................... 53

Copyright © 2016. 5 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

8 Clash Acceptance ................................................................................................................ 55

8.1 Status Settings ................................................................................................................................ 55
8.1.1 Creating a new status – A Worked Example ............................................................................. 56
8.2 Automatic Clash acceptance ......................................................................................................... 57
8.2.1 Creating an Acceptance Rule – A Worked Example ................................................................. 58
Exercise 8 Clash Acceptance ............................................................................................................ 61
9 Clash Groups........................................................................................................................ 63
9.1 Configuring Clash Grouping ......................................................................................................... 63
9.1.1 Changing the Default Group Level ............................................................................................ 64
9.1.2 Creating a Group Rule ............................................................................................................... 64
9.2 Group Properties ............................................................................................................................ 65
9.3 Clash Level/Type ............................................................................................................................. 66
9.4 Group Changes Policy ................................................................................................................... 67
Exercise 9 Clash Groups .................................................................................................................... 69
10 Miscellaneous Administration ......................................................................................... 71
10.1 Clash Standards Comments ...................................................................................................... 71
10.2 Gtype/Tracking ............................................................................................................................ 72
10.3 Administrator Options ................................................................................................................ 74
Rule Syntax Reference ..................................................................................... 77
Wildcards and Regular Expressions ............................................................... 79
Creating a New Oracle Instance for AVEVA Clash Manager .......................... 81

Copyright © 2016. 6 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
CHAPTER 1

1 Introduction

AVEVA Clash Manager™ is used to group clashes together and allocate them to owning disciplines for
investigation. Clashes can then be approved or reallocated to other disciplines with comments, for example a
hole in a floor plate may be required so the Pipe to Floor Clash is reallocated from the Piping Department to
the Structural Department.

Clash Manager is not intended to replace good design practice using AVEVA Everything3D™, it is intended
to enhance clash management.

1.1 Aim

The aim of the course is to provide the skills required to install and configure AVEVA Clash Manager with
AVEVA Everything3D.

1.2 Objectives

At the end of this training, the user will have a

 Broad view of AVEVA Clash Manager Installation, Administration & Configuration.

1.3 Prerequisites

 Familiarity with Microsoft Windows.

 Knowledge of AVEVA Everything3D™

 Knowledge of AVEVA Clash Manager™.

1.4 Course Structure

Training will consist of oral and visual presentations, demonstrations and set exercises. Each workstation will
have a training project, populated with model objects. This will be used by the trainees to practice their
methods, and complete the set exercises.

Copyright © 2016.
AVEVA Solutions Limited and its subsidiaries. 7 www.aveva.com
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

1.5 Using this guide

Certain text styles are used to indicate special situations throughout this document, here is a summary;

Menu pull downs and button press actions are indicated by bold dark turquoise text.

Information the user has to key-in will be in bold red text.

Where additional information is presented, or reference is made to other documentation the following
annotation will be used:

 Additional information

 Refer to other documentation

System prompts will be bold, italicised, and presented in inverted commas i.e. 'Choose function'.

Example files or inputs will be in the courier new font.

Copyright © 2016. 8 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
CHAPTER 2

2 Installation of AVEVA Clash Manager

AVEVA Clash Manager is installed from the CD using the On-screen prompts. Make sure that the Clash
Manager is installed from the Setup Wizard.

Click the Next button.

Check the License Agreement textbox and click the Next button.

Copyright © 2016. 9 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

For AVEVA Everything3D, select E3D 2.1 Clash Manager and click the Next button.

Click Install.

Copyright © 2016. 10 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

A Progress bar is displayed.

Click the Finish button.

Copyright © 2016. 11 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

Exercise 1 AVEVA Clash Manager Installation

Install AVEVA Clash Manager.

Copyright © 2016. 12 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
CHAPTER 3

3 Clash Manager Project Configuration

The AVEVA Clash Manager project data is stored in an Oracle or MS SQL Server database. Before starting
the configuration of a new Clash Manager project, the database must be created in the server instance. For
the purpose of this training, an empty database ClashMgrTRA-A has been created.

This chapter will guide the user through the creation and configuration of a new Clash Manager project.

3.1 AVEVA Clash Manager Project creation wizard

The first time AVEVA Clash Manager is started in an AVEVA E3D Project, a dialog is displayed to allow the
creation of a new Clash Manager project, or to use an existing Project.

Start AVEVA Everything3D and enter the

Training Project (TRA) with the
following details:

User : A.MODELADMIN

Password : A

MDB : A-PIPING

Module : Model

 Only Free users or users members

of the DESADMIN team can create
a Clash Manager Project.

Navigate to the HOME tab.

In the Check group, expand the Clashes

options button and select Clash
Manager.

Copyright © 2016. 13 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

The flowing Dialog will be displayed:

Check the Create new Project checkbox and

click OK.

The following will show the configuration of an SQL Server database. The configuration of an Oracle database
is not covered by this guide.

Select the SQL Server option and click

Next.

Select the SQL Server Instance form the

dropdown list.

Enter the DBA login details.

Copyright © 2016. 14 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

Select the database ClashMgrTRA-A

from the Database dropdown list.

Select the collation which should be the

same as the select server collation.

Click Next.

Review the details and click Next.

Check the use defaults checkbox to

create a SQL Server user for the new
database. This will create the default user
PCLAMTRA with password PWTRA.

If a different SQL Server instance is

required, uncheck the use defaults
checkbox then enter the appropriate user
name and password credentials.

Click Next.

Copyright © 2016. 15 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

Enter an AVEVA E3D username and

password for Clash Manager to login to
the E3D project.

Enter:

Design Username: A.MODELADMIN

Design Password: A

Note that the user maybe Read Only as it

will not attempt to write in the AVEVA E3D
project.

Click Next.

In the next screen, enter the following

details for the Clash Manager Project:

Project Title: Clash Manager Training

Project Number: Training

Client: AVEVA

Review the details of the configuration and

click Finish.

Once the schema is created, click Cancel

to close the form.

 Clicking the Next button directly

opens AVEVA Clash Manager.

Copyright © 2016. 16 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

Exercise 2 AVEVA Clash Manager Wizard

Build the AVEVA Clash Manager Schema by working through the above chapter.

Copyright © 2016. 17 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

This page is intentionally left blank.

Copyright © 2016. 18 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
CHAPTER 4

4 Clash Manager Settings

Before AVEVA Clash Manager can be used, defaults settings have to be defined for control, automatic
acceptance of certain clashes, automatic assignment of clash ownership, automatic grouping of clashes, as
well as doing some basic access control.

4.1 Starting AVEVA Clash Manager

Once the database schema has been created for the project, clicking the Clash Manager option in the
Clashes options list from the Check group in the HOME tab will open the main AVEVA Clash Manager
window.

Copyright © 2016. 19 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

4.2 AVEVA Clash Manager Settings

Before AVEVA Clash Manager can be used on a project, it is necessary to perform some configuration
tasks. The focus of these tasks is to produce an organized and structured presentation of clash data that
assists in the management of the clashes. All configuration tasks are carried out in the Configuration form.

The basic configuration tasks are necessary regardless of project size are Project, Discipline, Security, Group
and Assign.

In the Tools menu, selecting the Settings option

will display the Clash Manager Options form.

The AVEVA Clash Manager Configuration form will be displayed:

Copyright © 2016. 20 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

4.3 Project Details

The Project tab is used to specify the details for entering the Project. The Project Title, Client, Project
Number, Project, User ID, and Password textboxes at the top of the tab are for entry of project details.

Apply Group Changes to Clash Detail: This options 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' form to choose whether or not group changes are applied to clash details within a
group. This option will be detail later.

The items in the Project Field frame 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 textbox is for specifying the name of the attribute, e.g. AREA. 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 textbox is for entering the attribute description that appears in the Clash Report.

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

Copyright © 2016. 21 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

This page is intentionally left blank.

Copyright © 2016. 22 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
CHAPTER 5

5 Security Settings

In this chapter the user will learn how to control the ability for users to perform certain tasks on the clashes by
defining security levels and user access rights.

5.1 Security Levels

The Security tab of the Configuration form allows the administrator to update and view the overall security
arrangements for Clash Manager.

The tab essentially displays one of five panels for setting Security Levels. The first four panels allow to set the
security level for four different tasks:

 Status: controls who can change the status of a clash.

 Owner: controls who can change the discipline ownership of a clash.

 Check CE: controls who can check the clashes for the Current Element.

 Comments: controls who can add comments on a clash.

For these panels, a slider control enables the security level to be set to one of the five state, High, Medium
High, Medium, Medium Low and Low, which will define the minimum access rights required for the users to
be allowed to perform the correspondent task.

Copyright © 2016. 23 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

The fifth panel, Users, allows the creation of users and the definition of their access rights by assigning them
to disciplines. When a discipline is assigned to a user, he may be granted two different access levels: member
or supervisor.

The level of control of a clash will then depend on the user’s assignment and level for the clash’s Owner
Discipline, and the security level set for the task.

5.1.1 Clash Status Security Level

Select the Status button to open the Status Security

Level panel.

This panel is used to set the Security Level for changing the status of a clash. The table below describe the
minimum access rights requirement for the user to be able to change the status, depending on the different
security levels.

Security Level - Status

State Access required to change the status of a clash

High Supervisor of the Administrator discipline.

Medium High Supervisor of Owner discipline AND Member of the Administrator

discipline.

Medium (the default) Supervisor of Owner discipline.

Medium Low Member of Owner discipline.

Low Member of ANY discipline involved in the Clash.

Copyright © 2016. 24 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

5.1.2 Discipline Ownership Security Level

Select the Owner button to open the Discipline

Ownership Security Level panel.

This panel is used to set the Security Level for changing the discipline ownership of a clash. The table below
describe the minimum access rights requirement for the user to be able to change the discipline, depending
on the different security levels.

It is important to understand here the terminology for the discipline ownership and how it operates.

A clash is composed of a pair of clashing elements that may belong to two different disciplines. Only one
discipline is assigned to the clash depending on the order of the rules specified in the Assign tab. However,
if the user access allows it, he may manually change the assignment of a clash to other disciplines.

In the table below, the “current discipline” defines the discipline currently assigned to the clash (owner
discipline), and the “other discipline” is the discipline of the other clashing element.

If the user is member of the current discipline, he may “impose” the ownership, i.e. change the current clash
assignment to the other discipline of which he is not a member of. Conversely, if the user is not a member of
the current discipline, he may “acquire” the ownership, i.e. change the current clash assignment to the other
discipline of which he is a member of.

Security Level - Status

State Access required to acquire or impose discipline ownership

High Supervisor of the Administrator discipline.

Medium High Supervisor of other discipline and Member of the Administrator

discipline may acquire ownership.

Supervisor of current discipline and Member of the Administrator

discipline may impose ownership.

Medium (the default) Supervisor of other discipline and Member of the Administrator
discipline may acquire ownership.

Supervisor of current discipline and Member of the Administrator

discipline 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 the Clash.

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

Copyright © 2016. 25 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

5.1.3 Clash Check Current Element Security Level

Select the Check CE button to open the Clash Check

Current Element Security Level panel.

This panel is used to set the Security Level for checking the Current Element. The table below describe the
minimum access rights requirement for the user to be able to check the Current Element, depending on the
different security levels.

Security Level - Status

State Access required to clash check the Current Element

High Supervisor of the Administrator discipline.

Medium High Supervisor of Owner discipline AND Member of the Administrator

discipline.

Medium (the default) Supervisor of Owner discipline.

Medium Low Member of Owner discipline.

Low Member of ANY discipline involved in the Clash.

 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.

5.1.4 Comments Security Levels

Select the Comments button to open the Enter

Comments Security Level panel.

Copyright © 2016. 26 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

This panel is used to set the Security Level for adding comments to a clash. The table below describe the
minimum access rights requirement for the user to be able to add comments to a clash, depending on the
different security levels.

Security Level - Status

State Access required to add comments to a clash

High Supervisor of the Administrator discipline or

Supervisor of ANY discipline involved in the clash and member of the

Administrator discipline.

Medium High Supervisor of ANY discipline involved in the clash.

Medium (the default) Member of ANY discipline involved in the clash.

Medium Low Member of ANY discipline.

Low Anybody.

5.1.5 Custom Security Levels

The security levels may be customized if the defaults levels do not correspond to the project requirements.

To customize the security level for one task, open the

panel for that task and click the Custom Level button.

Copyright © 2016. 27 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

A form will be displayed to set the required access rights to perform the selected action:

 Change of ownership requires two access right selection for “Acquire” and “Impose”.

5.2 User Access

To create users, assign them to disciplines, and set their membership level i.e. member / supervisor, click the
User button from the Security tab of the Configuration form.

Copyright © 2016. 28 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

5.2.1 Creating Users

In AVEVA Clash Manager, the user credentials are based on the Windows NT authentication. To add a new
user, the provided name must be the Windows login of the user.

Right click the Users label in the explorer tree.

Select Add New User

Enter steve.clashman

Press the <Enter> key to validate.

5.2.2 Granting Discipline Membership

In the Users panel, the Discipline tree below the users tree may be used to assign disciplines to existing users.

The access to a discipline is granted by dragging and dropping the discipline to the user, the user to a
discipline, or by right click on the user’s name.

Expand both the Users tree and the Discipline tree

by clicking the + symbol.

Select the Piping discipline from the Discipline tree

and drag and drop it on the user name.

The user is now a member of the Piping discipline as

indicated in the tree:

Copyright © 2016. 29 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

5.2.3 Granting Discipline Supervision

As seen in the previous section for Security Levels, a user may be supervisor of a discipline which will give
him higher privileges than a simple membership.

To make a user supervisor of a discipline, check the checkbox located next to the discipline name under the
user name.

Check the checkbox located next to the Piping

discipline below the user name.

The user steve.clashman is now supervisor of the

Piping discipline.

If the security level for all the tasks is set to medium, the user steve.clashman:

 Can change the status of all clashes owned by the piping discipline.

 Can assign the ownership of a clash to the Piping discipline if a clash involves a piping element.

 Cannot assign the ownership of a clash to a discipline different than Piping.

 Can run a clash check on the Current Element if this one belongs to the Piping discipline.

 Can add a comment to a clash if this one involves a piping element.

5.2.4 Administrator privileges

Additionally, to the privileges accorded by the selected security

levels, a user Supervisor of the Administrator discipline will be
able to:

 Create, delete and edit Clash sets.

 Change ownership to disciplines that are not involved in a clash.

 Perform any of the four actions: changing status of any clash, changing any clash ownership, checking
the CE, adding comments to any clash.

 AVEVA E3D users that are members of the DESADMIN team have unrestricted access to all AVEVA
Clash Manager features.

Copyright © 2016. 30 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

Exercise 3 Security Settings

Set the security level of the current Windows user so that he will be able to create Clash sets.

Create and run the following Clash Set:

Title: Piping-Area01

Obstructions: /ZONE-PIPING-AREA01, /ZONE-CWAY-AREA01, /ZONE-EQUIPMENT-AREA01, /ZONE-

STRUCTURAL-AREA01

Check: /ZONE-PIPING-AREA01

Option: Map Override

Copyright © 2016. 31 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

This page is intentionally left blank.

Copyright © 2016. 32 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
CHAPTER 6

6 Elements and Clash Disciplines

When a clash check is run, each element of a pair of clashing elements in a clash is allocated to a discipline.
The Discipline tab of the Configuration form allows to create disciplines and define how clashing elements
are allocated to them.

Once clashing elements are allocated to a discipline, AVEVA Clash Manager can automatically assign the
clash ownership to one discipline. This may be the allocated discipline of either one of the clashing elements
in the clash, or any other discipline depending on user defined rules. The automatic assignment of a clash to
a discipline may be configured in the Assign tab.

In this chapter the user will learn how to create new disciplines and modify the automatic discipline assignment
of clashes.

6.1 Element Discipline Allocation

In the Configuration form select the Discipline Tab:

This tab allows:

 The creation, modification and deletion of disciplines.

 The definition of discipline allocation by associating the value of an AVEVA E3D attribute with a Clash
Manager discipline.

Copyright © 2016. 33 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

6.1.1 Creating a new Discipline

At this stage it is decided which disciplines are required in the project (for this training example the standard
disciplines that are loaded by default we be used). Disciplines cannot be deleted once clashes have been
assigned.

Click the Discipline tab. Disciplines may be added and deleted by right clicking in the list gadget and using
the contextual menu.

Right click in the list and select the Add

option.

Enter Other Equipment and press the

<Enter> key.

Select the newly added discipline Other

Equipment, right click in the Attribute
Value column and select the Edit
option.

Copyright © 2016. 34 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

Enter an attribute value of EQP.

6.1.2 Discipline Allocation Attribute

The allocation of discipline to a clashing element is based on the value of an E3D attribute defined at the
bottom of the Discipline panel.

The default Project settings uses the attribute PURP which means for example that a clashing element having
a PURP value of “EQP” will be allocated to the discipline “Other Equipment”.

Whilst it may be better practice to use UDAs for this purpose, the training will use the “PURP” attribute of the
owning zone.

Enter PURP OF ZONE in the Attribute

textbox.

If the attribute values of the clashing items in a clash does not match any of the values defined in the discipline
list, then the element discipline will be set to a default discipline that may be specified in the Default dropdown
list:

Copyright © 2016. 35 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

6.1.3 Saving new settings

Once settings have been modified or created, click Save for the changes to be written in the Clash Manager
database.

Clicking the OK button will then prompt the user to re-compute the clashes to apply the new settings on the
current clashes:

Clicking OK will display the Clash Recomputation form:

Here, as the disciplines have changed the selected options offer to re-evaluate the discipline assignments.
The different options of this form will be described along with the correspondent settings in the next
chapters.

Clicking the Cancel button will not re-compute the clashes.

Copyright © 2016. 36 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

Exercise 4 Creating Disciplines

Set the Attribute to PURP OF ZONE

Add the following Discipline to Clash Manager:

Discipline Attribute Value

Laser Survey LASE

Pending Assignment

Modify the following Disciplines:

Discipline Attribute Value

Elec and Inst Cable Racks CABL

Structural Steel STL

Save the new settings but do no re-compute the clashes.

Copyright © 2016. 37 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

6.2 Clash Discipline Assignment

This section explains how to configure the automatic assignment of clashes to disciplines.

This configuration is done in the Assign tab of the Configuration form:

Disciplines may be evaluated against four categories of rules:

 Assignment Rules may be defined in this tab for elaborated selection criteria.

 Priority may be used to assign the discipline of the element with the highest priority in the clash.

 Class may be used to assign the discipline of the element with the most important class in the clash.

 Element Discipline is one of the two disciplines allocated to the pair of clashing elements.

The ownership of a clash will be set to the first discipline that will match a rule in one of the categories described
above. If the category does not produce a result, the next category in the Application Order list will be
evaluated. For example, in the configuration shown above, Clash Manager will:

1. Check each discipline in the order defined in the Discipline Order / Assignment Rules list. If a
rule exists it will be evaluated for the corresponding discipline, and will assign the clash to that
discipline if the result is positive.

2. If no assignment rule is found or no rule has a positive result, the owner discipline will be set to
the element with the highest priority as defined in the Priority tab.

3. If the disciplines of the two clashing elements have the same priority, then the owner discipline
will be set to the element with the most important class as defined in the Class tab.

4. If the disciplines of the two clashing elements have the same class importance, the owner
discipline will be set to the one having the highest rank in the Discipline Order / Assignment

Copyright © 2016. 38 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

Rules list (top to bottom). If the two clashing elements are allocated to the same discipline, the
owner discipline will be set to the first clashing element.

Note that the category “Element Discipline” should always appear at the bottom of the Application Order
list as it will always return a result.

6.2.1 Activate and order categories of rules

The activation and order of application of the four categories of rules may be specified in the top part of the
tab by using the arrow buttons located on the right of the list.

Check the Priority checkbox and the Class checkbox.

Select the Class item in the list and use the top arrow to
order the Class category in second position.

6.2.2 Discipline Order

The lower part of the tab allows to order the disciplines and to create assignment rules.

The order of discipline may be modified by selecting the name of a discipline in the Discipline Order /
Assignment Rules list then clicking the arrows located on the right of the list. This will specify in which order,
from top to bottom, the disciplines will be evaluated against the “Assignment Rules” and “Element
Discipline” categories activated in the top part of the tab.

6.2.3 Assignment Rules

When particular conditions are met for a pair of clashing elements involved in a clash, the discipline assigned
to the clash may be different from the one defined by the Element Discipline. In this case, it is possible to
create specific rules to assign another discipline.

An Assignment Rule is created by right clicking a discipline in

the list and selecting Add.

Then a name may be given to the rule in the displayed textbox.

Once created, the list of rules assigned to the discipline will appear in the tree below the discipline node.
Clicking one of the rules will display the list of criteria in the area below the discipline list:

Copyright © 2016. 39 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

To create a new criteria for the selected rule, right

click in the criteria area and select Add Rule.

The user must then set values to the three columns Item, Attribute and Value to define the criteria.

Item: right clicking in this column allows to select between

@element1, @element2 or @general. The first two choices allow
the user to select attributes that are related to a clashing element.
Note that the element suffix “1” or “2” does not reflect the order of
elements in the clash, but to distinguish between “one element” and
the “other element”. The @general allows to test general attributes of
the clash.

Attribute: right clicking in this columns allows to select the attribute

to test.

When the selected item is an element, the user may choose keywords
like @discipline, @gytpe, @treeType, to return the properties of the
element. It is also possible to manually enter the name of an AVEVA
E3D attribute by selecting the Edit option. Attribute expressions may
be extended to related elements with the OF keyword, for example
NAME OF HREF.

When the selected item is general, the user may choose a keyword
like @status, @level, @type, @setDiscipline to return the
properties of the clash.

Value: right clicking in this column allows to edit the value to be

compared with the selected attribute of the selected item. Selecting
the Edit options will either display a list of pre-defined values for the
selected attribute, or display a textbox for free entry. When an
attribute expression has been entered in the Attribute column, it may
be evaluated against other elements, for example @element-2.

Copyright © 2016. 40 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

The user may enter multiple criteria for a rule. All the criteria must be true for the rule to be positive and the
clash assigned to the discipline associated with the rule.

 Refer to APPENDIX A for the expression syntax reference.

6.2.4 Assignment Rules – A Worked Example

With the current configuration and no rule defined, if a clash involves an element allocated to the Piping
discipline and an element allocated to the Structural Steel discipline, then the assigned discipline will be
Piping because it has the highest rank in the discipline order. However, the project requires to implement an
exception: if the clash is of type “Touch” and the name of the structural element contains “PIPERACK”, then
the assigned discipline should be “Pending Assignment” so that the clash is pending a manual assignment
after further discussions.

In the Assign tab, select the discipline “Pending

Assignment” and using the arrows, place it in
second position after the UNALLOCATED
discipline.

This is to ensure that any rule assigned to the

Structural Steel or Piping discipline will be
overridden by the Pending Assignment rule.

Right click the Pending Assignment discipline in

the list and select Add.

Enter:

Pipes touching PIPERACK

Right click in the table below the Discipline Order list

and select Add Rule.

Copyright © 2016. 41 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

Select @element-1

Right click in the Attribute column and select

@discipline

Right Click in the Value column and select Edit.

Then select the Structural Steel discipline so that the

rule is:

Create 3 additional criteria to obtain the list shown.

 The values are regular expressions that may

contain wildcards. In this case, all element
containing ‘PIPERACK’ in their names will be
true.

6.2.5 Testing the rules

The rules may be evaluated without modifying the current assignments.

 Click the Save button before testing the rule.

Click the Save button.

Click the Test button.

Copyright © 2016. 42 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

Select the Group option to display the existing

groups.

 The created rule will only affect Group

elements as the name PIPERACK is set
on a STRU element type.

Enter % in the textbox and click the Query

button to populate the list with all existing
clashing elements.

Click the Evaluate Rules button.

The New Discipline column will display the

details of the new assignments according to
the new rules.

Close the Test Rules form.

Click Save then OK.

After saving and closing the Configuration form, a dialog will offer the user the possibility to re-compute the
existing clashes using the new configuration.

Clicking the OK button will not launch the

design clasher again but re-evaluate a
panel of selected assignment options for
the existing clashes, which may be defined
in the Clash Recomputation form:

Copyright © 2016. 43 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

The options are automatically selected depending on the new settings. Select the Element Properties or Clash
Properties to re-evaluate, and click OK.

Copyright © 2016. 44 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

Exercise 5 Assignment Rules

Create an assignment rule named “Panel penetrations” so that every clash involving a Piping element and
a Structural Steel element will be assigned to the Structural Steel discipline if the structural element has a
GTYPE value equals to PANE.

Evaluate the rules for Detail elements in the Test Rules form.

Re-compute the clashes.

Note that as this rule will test detail elements (PANE) the results will be visible by selecting the
View > Summary Display > Clash Detail option.

Copyright © 2016. 45 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

This page is intentionally left blank.

Copyright © 2016. 46 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
CHAPTER 7

7 Clash Priority and Class

A priority or a class may be assigned to clashing elements by changing the value of an attribute in Model.

The Priority and Class may be used in the Order of Application list of the Assign tab to automatically assign
the discipline of either one of the clashing elements in a clash, based on the rank of its assigned priority or
class.

Priority and class may also be used in rule expressions for automatic discipline assignment and automatic
clash acceptance, with the use of the @priority and @class keywords available for an element.

7.1 The Priority tab

The Priority tab of the AVEVA Clash Manager Configuration form allows to create, modify, delete Clash
Manager Priorities, and to define how these priorities are assigned to clashing elements by specifying an E3D
Attribute and lookup values.

Copyright © 2016. 47 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

7.1.1 Create a new Priority

To create a Priority, right click in the Priority list and

select Add.

Enter a description for the new priority.

 This description will be available when using the

@priority keyword in a rule.

For the new priority to be available in other tabs of the form, click the Save button.

7.1.2 Ordering the Priorities

The rank of priorities is important as assignment rules based on Priority will return the element having the
priority with the highest position in the list.

To order the priorities, select an item in the list and

use the arrows located on the right of the list.

7.1.3 Priority Lookup Value

A lookup E3D attribute has to be specified in the lower part of the tab so that elements will be assigned the
priority having a value matching the one in the specified attribute.

For the purpose of this training the lookup attribute will be set to Description, but in production it is
recommended to create a specific UDA with valid values for the clash priority.

Enter Description in the Attribute textbox.

Copyright © 2016. 48 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

The lookup values can then be specified in the list by selecting a priority, right clicking in the Attribute Value
column and selecting the Edit option.

Select the priority “one”, right click the Attribute

Value column, select Edit and enter 1.

It is important to understand that the lookup value is not a simple text entry but actually a regular expression
that may contain wildcards. In the example above, entering simply “1” in the Attribute Value will in fact return
a true result for all Description containing the character “1” for example “102” or “B-1” etc.

More thoroughly, to match exactly the character “1” the value to enter should be the regular expression “^1$”,
which means all values starting with “1” and ending with “1”.

 Refer to APPENDIX B for the use of Wildcards and Regular Expressions.

In a clash, when the value of the lookup

attribute is not set for both clashing elements,
then the priority will be set to the Default which
may be specified the corresponding list at the
bottom of tab:

Copyright © 2016. 49 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

Exercise 6 Clash Priority

1. Set the Attribute to Description.

2. Set a value for all the other priorities except “unknown” in the Priority list. For instance, set the value ^2$
for the priority “two”, value ^3$ for priority “three” etc.

3. Re-Order the priorities so that “unknown” is at the bottom of the list.

4. In the Assign tab, activate the Priority check and ensure it is in second position below Assignment
Rules. Save the new settings and click OK. Do not re-compute the clashes.

5. In Model, navigate to /P1502A and change the Description value to “2”. Savework.

6. As the Model data has changed, re-run the Clash Set to reflect the modifications in the clashes.

Because the pump /P1502A has a higher priority (two) than the other clashing elements (unknown), the 5
clashes involving the pump are now re-assigned to the Proc Vessels and Facilities discipline:

Copyright © 2016. 50 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

7.2 The Class tab

The Class tab of the AVEVA Clash Manager Configuration form allows to create, modify, delete Clash
Manager Classes, and to define how these classes are assigned to clashing elements by specifying an E3D
Attribute and lookup values.

Note that working with Classes is based on the exact same workflows as for the Priorities explained in the
previous section.

7.2.1 Create a new Class

To create a Class, right click in the Class list and

select Add.

Enter a description for the new priority.

 This description will be available when using the

@class keyword in a rule.

For the new class to be available in other tabs of the form, click the Save button.

Copyright © 2016. 51 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

7.2.2 Ordering the Classes

The rank of classes is important as assignment rules based on Class will return the element having the class
with the highest position in the list.

To order the classes, select an item in the list and use

the arrows located on the right of the list.

7.2.3 Class Lookup Value

A lookup E3D attribute has to be specified in the lower part of the tab so that elements will be assigned the
class having a value matching the one in the specified attribute.

For the purpose of this training the lookup attribute will be set to Function, but in production it is recommended
to create a specific UDA with valid values for the required clash class.

Enter Function in the Attribute textbox.

The lookup values can then be specified in the list by selecting a class, right clicking in the Attribute Value
column and selecting the Edit option. As for the Priorities, a regular expression should be entered.

Select the class “Fabricated”, right click the Attribute

Value column, select Edit and enter ^Fabricated$.

 Refer to APPENDIX B for the use of Wildcards and Regular Expressions.

In a clash, when the value of the lookup

attribute is not set for both clashing elements,
then the class will be set to the Default which
may be specified the corresponding list at the
bottom of tab:

Copyright © 2016. 52 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

Exercise 7 Clash Class

1. Set the Attribute to Function.

2. Set values for all the other classes in the list except the Unknown class. Use the same text as description
with the prefix ^ and the suffix $, for example ^Procurement$

3. Ensure the Unknown class is at the bottom of the list.

4. In the Assign tab, activate the Class check and ensure it is in third position below Priority. Save the
new settings and click OK. Do not re-compute the clashes.

5. In Model, navigate to /EQUIP_SUPPORT and change the Function attribute value to “Fabricated”.
Savework.

6. As the Model data has changed, re-run the Clash Set to reflect the modifications in the clashes.

Check the comments in the Group Clash Report.

Because the structure /EQUIP_SUPPORT has a higher class (Fabricated) than the other clashing elements
(Unknown), the 13 clashes involving the structure are now re-assigned to the Structural Steel discipline:

Copyright © 2016. 53 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

This page is intentionally left blank.

Copyright © 2016. 54 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
CHAPTER 8

8 Clash Acceptance

AVEVA Clash Manager is supplied with standard clash status descriptions and states to assign an acceptance
level manually or automatically to a clash.

In this chapter, the user will learn how to create new statuses, and to define rules for the automatic assignment
of clash statuses.

8.1 Status Settings

In the AVEVA Clash Manager Configuration form, the Status tab allows the creation, modification and
deletion of clash statuses.

The standard statuses Approved, Conditional, Pending, Unapproved, Unknown are available for all
disciplines, and cannot be modified or deleted.

Additional custom statuses may be created for specific disciplines to suit the project requirements. When
creating a new status, the following fields must be specified:

Description: Enter a short description for the status, this description will appear in the reports and may be
used in rules via the keyword @status. Custom statuses are generally discipline specific so a typical custom
status description may be “Piping Approved”.

State: Select a standard status that will represent the acceptance level of the clash on the Clash Charts and
Summaries.

Copyright © 2016. 55 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

Access: This will define which discipline will have access to the custom status. This can also be set to “Any”
for a general access.

When new clashes are found, the status is set to a

default value if the clash is not automatically assigned
an acceptance level. The default status may be set at
the bottom of the Status tab:

8.1.1 Creating a new status – A Worked Example

Right click in the status list and select Add to create

a new status.

Enter Piping Approved and press Enter.

Right click in the State column for the selected status.

Select Edit.

Select the Approved status in the list of standard

statuses.

Right click in the Access column for the selected

status.

Select Edit.

Copyright © 2016. 56 www.aveva.com

AVEVA Solutions Limited and its subsidiaries.
All rights reserved.
AVEVA Clash Manager™ 14.1
Clash Manager Administration TM-1874

Select the Piping discipline.

Click Save for the new status to be available in other

tabs.

8.2 Automatic Clash acceptance

As for the disciplines, the clashes may be assigned an acceptance level automatically by using assignment
rules.

The acceptance assignment rules may be created in the Accept tab of the AVEVA Clash Manager
Configuration form:

When the clashes are checked, the rules are evaluated in the order shown on the Status list, from top to
bottom. The clash will be assigned the status associated with the first rule that will return a positive result.

The application order of the acceptance rules may be changed by selecting a status in the list and
clicking the arrows at the right.

To associate a rule to a status, select the status in the

list, right click and select Add. A new rule will be
created below the selected status, and criteria may
be added to it by right clicking in the list at the bottom
of the tab.

Several criteria may be added to the Rule by following

the same workflow as for the Discipline assignment
rules.

It is important to note that rules are evaluated against the clashing elements, not groups. The acceptance
value of a group will take the acceptance value of the clashing element having the worst status in the group.
A typical case is a rule checking that the two clashing elements are in the same Pipe. Entering the rule
@element-1, NAME, @element-2 will not work because this will return the name of the clashing elements
which generally are not named, e.g. an elbow. The correct expression would be @element-1, NAME OF
PIPE, @element-2.

8.2.1 Creating an Acceptance Rule – A Worked Example

In this example, a rule will be created to automatically approve the clashes with the following conditions:

- The discipline of both clashing elements is Piping.

- The level of the clash is HH.

- The type of the clash is TOU.

When those conditions are met, the clash should be assigned the “Piping Conditional” status.

Right click the Piping Approved status and select

Add.

Enter Pipe against Pipe then press Enter.

Right click in the list at the bottom of the tab and

select Add Rule.

Select @element-1

Right click in the Attribute column select

@discipline.

Right click in the Value column, select Edit, then

select Piping.

Create 2 other criteria to obtain the following:

Click Save then click OK to close the form. The following dialog will be displayed to re-compute the clashes
with the new rules.

Click OK.

Click OK to re-compute the clashes

using the new Clash Acceptance rules.

This new setting should result in the following summary:

Exercise 8 Clash Acceptance

1. Create a new status For Design Review with the base state Pending and accessible for Any discipline.

2. Create a new acceptance rule Same Pipe that will automatically assign clashes to the “For Design
Review” status when the following conditions are met:

- Element 1 is in the Piping discipline

- The two elements are owned by the same PIPE : @element-2 / NAME OF PIPE / @element-1

- The level of clash is Hard/Soft

3. Order the rules so that the For Design Review status is evaluated before the Piping Approved status,
because the rule for Piping Approved would include all the elements of the rule For Design Review.

4. Re-Compute or re-run the clash set.

The chart and clash summary should now look like this:

This page is intentionally left blank.

9 Clash Groups

Many clashes may exist between pairs of significant elements. The clashes exist at lower levels in the
hierarchy i.e. 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.

In this chapter, the user will learn how to configure the grouping of clashes, how groups are assigned a
discipline, status, Level/Type, and how to control the change policy when the group status in changed
manually.

9.1 Configuring Clash Grouping

Clash groups may be configured in the Group tab of the AVEVA Clash Manager Configuration form.

Default Group Level: these 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.

Group Clashes between element pairs within +/-: is 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.

Exceptions list: The pane at the bottom of the tab is for specifying exceptions to the default group levels
specified in the drop-down lists above. The user may specify a GTYPE and associate it with a rule for the
elements to be grouped within a specific Group Level.

 Changing the group settings in mid project will not modify the existing groups.

9.1.1 Changing the Default Group Level

The Default Group Level may be changed for any

element under the GTYPES PIPE, EQUI, STRU,
HVAC and REST.

As an example, if all Sections under a STRU element

have to be grouped by Section, click the options list
next to STRU and select SCTN.

Note that selecting the SCTN means that all the

GTypes at SCTN level will be grouped.

9.1.2 Creating a Group Rule

To create a custom group rule, right click in the list at

the bottom of the Group tab and select Add.

GTYPE: select the type of clashing element that needs to be grouped under the GTYPE specified in the Group
Level column. The types available in the drop-down list are the ones created in the Gtype/Tracking tab.
Select * for any type of element.

Attribute: specify an attribute name to filter the clashing elements with the attribute value specified in the
Value column.

Value: specify a value which will be checked against the attribute value of the clashing elements to apply the
grouping under the specified Group Level.

Group Level: specify the type of element which the specified clashing element type should be grouped under.
The selected Group Level must be either the same GTYPE as the clashing element or any legal parent.

9.2 Group Properties

Like detail clashes, clash groups have their own properties like Status, Discipline and Level/Type, which
may be set independently from the detail clashes. Manual changes to group properties may be achieved in
the Clash Group Properties form:

When the group properties are set to Auto rules, the following process is applied:

Group Discipline: the automatic assignment of a discipline to a group follows the rules defined in the Assign
tab of the Configuration form, applied to the group level element e.g. a STRU.

Group Status: when the clashes are recomputed, the group is assigned the status of the detail clash having
the worst status as defined in the order shown on the Status tab, from bottom to top. For example, if a group
contains two clashes, one is approved and one is unapproved, then the group status will be unapproved.

 The Test button available in the Accept tab allows to evaluate the rules for groups. In this case, the Test
Rule evaluates the rule on group elements but does not override the new group status with the new detail
status. This means that re-computing the rules might not generate the same results as the Test feature.

Note that for custom statuses, the group status will

consider the base state to define the worst case.

For example, with the settings on the right, if a group

contains two clashes, one is Piping Approved and one is
For Design Review, then the group will be assigned the
Pending status because it is worse than Approved.

Level/Type: the clash level and type of a group is defined by the detail clash having the worst Level/Type as
defined in the Level/Type tab of the Configuration form, from top to bottom. For example, if a group contains
two clashes, one being HS/CLA and the other being SS/CLA then the Level/Type of the group will be HS/CLA.

9.3 Clash Level/Type

The “worst case clash” is defined by the order of the pair of Clash Level and Clash Type in the Level/Type tab
of the configuration form.

This order may be modified by using the arrows on the right of the list. However, it is recommended to keep
the default order.

9.4 Group Changes Policy

When the status of a group is modified manually by a user, the changes may be propagated to all the clashes
in the group. This behaviour may be controlled by the user, by changing the “Apply Group Changes to Clash
Detail” policy. If set to true, changing the status of a group will be propagated to its clash members. If set to
false, only the group status will be changed. This policy is available in the Customise form, or on the Group
Properties form.

The administrators may prevent the users to change this policy by using the “Apply Group Changes to Clash
Detail” option in the Project tab of the AVEVA Clash Manager Configuration form.

Three options are available:

- Always: the policy in the Customise form will be set to true and the user will not be able to modify it.
Changing the status of a group will always be propagated to its members.

- Never: the policy in the Customise form will be set to false and the user will not be able to modify it.
Changing the status of a group will never be propagated to its members.

- Free: the users will be able to change the policy freely.

The administrator must be aware of the consequence of the policy:

When the policy is set to true, the group acts as a “Master”, i.e. if its properties have been modified manually,
the properties of the detail clashes will always be updated to be the same as their owning group.

However, if the policy is set to false, the group properties will be set automatically according to the rules, and
this may depend on the owned detail clashes. So if a group property is changed manually, it may be overridden
by a detail clash property after re-computation of the clashes.

Exercise 9 Clash Groups

1. Change the clash grouping distance to 2000mm.

2. Change the Default Level for all elements in a STRU to be grouped at SCTN level.

3. Add an exception so that the supports are grouped at STRU level. This may be done by creating a rule
where the attribute PURP of a ZONE has the value SUPP.

 These changes will only affect the new clashes but will not modify the existing clash groups. It is
recommended to define these settings once and for all before running the first Clash Set in the project.
Otherwise, the administrator will have to delete all Clash data using the Administrator Options form as
described in section 10.3.

This page is intentionally left blank.

10 Miscellaneous Administration

10.1 Clash Standards Comments

The Comments tab of the Configuration form allows to add standard clash comments the designer may wish
to add to a clash for a given discipline.

These predefined comments will be available in the list shown when clicking the Quick Comment button in
the Comments tab of the Clash Property form.

To add a pre-defined comment, right click in the list

and select Add.

The text of the comment may be entered.

Right click in the Discipline column for the selected

comment to change the discipline access.

10.2 Gtype/Tracking

The Gtype/Tracking tab of the Configuration form allows to create GTypes and to make them controllable
for the tracking utility.

A GType may be created by right clicking in the

list in the top part of the tab.

The name of the GTYPE may then be entered in

the textbox.

Once created, the new GType will be available in the rule editors for automatic assignment, acceptance, and
grouping.

A Gtype may be made controllable for tracking by

right clicking it in the list and selecting Control.

Also, rules may be created to filter the tracked elements.

Rules may be simply the name of an element to be included. The name of an element may also be
preceded with a ! character to be excluded.

More advanced rules may be created using PML expressions, and may be extended with regular
expressions to widen text criteria.

For example, to include all the Pipes with a diameter greater than 100mm, the rule to enter would be:

BORE OF PIPE GT 100mm

To include all the element in zones with a name ending with “AREA01” the rule would be:

NAME OF ZONE LIKE AREA01$

10.3 Administrator Options

Specific administrator tasks are available for users that are either supervisors of the Administrator discipline
or free users.

To access these tasks, select Tools > Administrator

Options…

The following form will be displayed:

Lock Database: Lock the Clash Manager database to prevent non-administrative users
from entering Clash Manager during administrative work. When this
button is selected, you will be prompted to enter a reason, which will be
displayed to users who attempt to enter the Clash Manager project.

Evaluate Element Properties: Re-compute the properties of the clashing elements like Class, Priority,
Area code and Discipline. This is typically performed after model or
configuration changes.

Evaluate Clash Properties: Re-compute the properties of the clashes like grouping, ownership,
acceptance, level/Type and status.

Track Changes: Initiates saving the current discipline/status/counts. This has the effect
of adding another point in the history shown on the Clash Manager
form. 'New' clashes are tracked from this point. You will be prompted to
enter a description for the new period or point (milestone).

Manually Load Clash Files: Loads a desclash output files to replace any that are partially loaded
following a system failure.

Delete unreferenced data: Removes from the clash report data any groups or elements that are
no longer involved with clashes.

Removes all clash report data from the database, but not
Delete ALL Clash data including configuration data. Therefore, clash set definitions, check list,
Comments and History: obstruction list and so on remain, but can be deleted manually. The
clash history is deleted.

Export Configuration Data: Saves the current AVEVA Clash Manager configuration to a file.

Import Configuration Data: Restores the AVEVA Clash Manager configuration from a file.

Database Maintenance: Options to manage the AVEVA Clash Manager project database.

This page is intentionally left blank.

Rule Syntax Reference

Assignment & Acceptance Rules

Element Attribute Value

@element-1 @class A Defined Class

@element-2 (field name is project defined)
@priority A Defined priority
(field name is project defined)
@areacode Regular expression
(field name is project defined)
@discipline A defined discipline

Any E3D attribute eg NAME Regular expression or keyword

@element-2 or @element-1 which
evaluates true if the given attribute has
the same value as element-1 or element-
2 respectively, or one of the keywords
listed below.
Expression can include one of the
comparison operators >, >=, < or <=
together with a value, and will evaluate
true if the condition is met for the given
attribute value.
Other keywords may be (where N is 1 or
2):
@ref-of-element-N replaced with the
reference of the clashing element,
@ref-of-owner-ele-N replaced with the
reference of the owner of the element,
@first replaced with the first member of
the clashing element
@first+n replaced with the nth member of
the clashing element, e.g. @first+1
@last replaced with the last member of
the clashing element
@last-n replaced with nth from last
member, e.g. @last-1

@gtype A GTYPE selected from list. (This list

originates from the Clash Manager
Configuration form - Gtype/Tracking tab.)

Element Attribute Value

@general @status A defined status

@level Clash Level, one of HH, HS, HI, II, IS,

SS, NP selected from a drop-down list
@type Clash Type, one of CLAsh, CLEarence,
TOUch selected from a drop-down list
@setDiscipline Keyword @element-1 or @element-2.
(Assignment rules only)
The owner discipline is set to that of
element-1 or element-2 respectively.

Wildcards and Regular Expressions

Clash Manager uses two different styles of wildcards:

• In the configuration, standard Regular Expression syntax is used exclusively.
• In the GUI filters, Oracle/SQLServer style wildcards ( "%" and "_" ) are used exclusively.

Regular Expression Summary

Value Meaning

^ Matches the start of a line

$ Matches the end of a line

. Matches any character
* Matches zero or more occurrences of the previous
expression
[string] Matches any one of the characters listed in string
In addition to the standard Regular Expression syntax there is a simple NOT operator <!>. If the
exclamation mark is the first character of the Regular Expression, the rule evaluates TRUE if the
expression fails.

Examples of Regular Expression Syntax

Example Matches Result of Example

Expression Expression
^[AB]305$ A string beginning with ‘A’ or ‘B’ A305 or B305
and ending with ‘305’
[AB]305 A string containing ‘A’ or ‘B’ IBMA305HAL or
followed by ‘305’ PQRB305LMN
!TEMP45 Any string that does NOT contain /THIS/string/Matches
‘TEMP45’
^/S45/.*/ A string beginning /S45 and /S45/ABCanythinggoeshere
TEMP45$ ending with 345/TEMP45
TEMP45
!^/S45 Any string that does not begin
with /S45

Oracle/SQLServer Wildcard Summary

Value Meaning

% Any number of characters of any value

_ Each underscore represents a single character of any value

Examples of Oracle/SQLServer Wildcard Syntax

Example Expression Matches

%pipe% Any string of any number of characters that contains

'pipe'
pipe_ Any string that starts 'pipe' and ends with a single
character

Creating a New Oracle Instance for AVEVA Clash Manager

Select All Programs > Oracle – OraDb10g_home2 > Configuration and Migration Tools > Database
Configuration Assistant

This launches the following forms:

Click Next >

Select Create a database and

click Next >

Select Custom Database and

click Next >

Enter Database Name and

click Next >

Click Next >

Enter required passwords and

click Next >

Select option Register this

database with all the
listeners then click Next >

Select option File System

then click Next >

Select option Use Database

File Locations from
Template then click Next >

Select default options as

above and click Next >

Select default options as

above then click Next >

Select Memory tab and enter

defaults as given then select
the Sizing tab

Enter default values as given

and select Character Sets
tab.

Enter values as above and

select Connection Mode tab

Select option Dedicated

Server Mode and select Next

Select Tablespaces and click

the Create button

Enter the details as given

above and click on Create
button.

Repeat the same process to

create INDEX_SEGS
tablespace and then click Next.

Select option Create Database

then press Finish.

Click the OK button, a Progress

bar will be displayed as below.

TG1119-AA0-C01 - AVEVA™ Administration (1.9) Administration Fundamentals Rev 1.0
No ratings yet
TG1119-AA0-C01 - AVEVA™ Administration (1.9) Administration Fundamentals Rev 1.0
184 pages
Gafanhoto
No ratings yet
Gafanhoto
10 pages
TM-3445 AVEVA PID (12.1) User Training Rev 5.0 PDF
100% (2)
TM-3445 AVEVA PID (12.1) User Training Rev 5.0 PDF
160 pages
AVEVA - E3D - Stairs, Ladders and Handrail Administration
No ratings yet
AVEVA - E3D - Stairs, Ladders and Handrail Administration
227 pages
TM-1861 AVEVA Administration (1.4) System Administration Rev 1.0
100% (3)
TM-1861 AVEVA Administration (1.4) System Administration Rev 1.0
106 pages
TM-1860 AVEVA Administration (1.4) Fundamentals Rev 2.0
No ratings yet
TM-1860 AVEVA Administration (1.4) Fundamentals Rev 2.0
156 pages
Aveva
100% (1)
Aveva
134 pages
TM-1822 AVEVA Everything3D™ 2.1 Mining 1.0
No ratings yet
TM-1822 AVEVA Everything3D™ 2.1 Mining 1.0
58 pages
TM 3652 Aveva Engineering 142 Engineering Administration Rev30 AYUDA
No ratings yet
TM 3652 Aveva Engineering 142 Engineering Administration Rev30 AYUDA
329 pages
TM-6101 AVEVA Instrumentation (12.1) Administration Rev 6.0 PDF
No ratings yet
TM-6101 AVEVA Instrumentation (12.1) Administration Rev 6.0 PDF
150 pages
E3d Complete Guide
No ratings yet
E3d Complete Guide
1,228 pages
TM-1801 AVEVA™ E3D Design (2.1) Foundations Rev 4.0
100% (4)
TM-1801 AVEVA™ E3D Design (2.1) Foundations Rev 4.0
197 pages
AVEVA - E3D - Schematic 3D Integrator
No ratings yet
AVEVA - E3D - Schematic 3D Integrator
76 pages
TM-3650 AVEVA Engineering (14.2) Engineering User Training Rev 3.0 PDF
100% (3)
TM-3650 AVEVA Engineering (14.2) Engineering User Training Rev 3.0 PDF
226 pages
TM-1300 AVEVA Plant 12.1 System Administration Basic 1.0
No ratings yet
TM-1300 AVEVA Plant 12.1 System Administration Basic 1.0
117 pages
TM-3652 AVEVA Engineering 15.1 Administration 1.0
100% (1)
TM-3652 AVEVA Engineering 15.1 Administration 1.0
380 pages
Project Drawing Administration
100% (4)
Project Drawing Administration
227 pages
E3d Migration
0% (2)
E3d Migration
115 pages
TM-1811 AVEVA™ E3D Design (2.1) Equipment Modelling Rev 5.0
No ratings yet
TM-1811 AVEVA™ E3D Design (2.1) Equipment Modelling Rev 5.0
135 pages
TM 1308 Lexicon Rev 1 0 PDF
No ratings yet
TM 1308 Lexicon Rev 1 0 PDF
91 pages
Lexicon Rev 1.0
75% (4)
Lexicon Rev 1.0
91 pages
TM-3650 AVEVA Engineering 15.1 User 1.0
No ratings yet
TM-3650 AVEVA Engineering 15.1 User 1.0
201 pages
TM-6101 AVEVA Instrumentation (12.1) Administration Rev 6.0 (Watermarked)
No ratings yet
TM-6101 AVEVA Instrumentation (12.1) Administration Rev 6.0 (Watermarked)
150 pages
TM-1800 AVEVA E3D Design (2.1) Training Setup Rev 3.0
100% (1)
TM-1800 AVEVA E3D Design (2.1) Training Setup Rev 3.0
33 pages
System Administration
100% (1)
System Administration
77 pages
TM-3534 AVEVA Diagrams (14.1.SP3) Diagrams - Administration Rev 4.0
No ratings yet
TM-3534 AVEVA Diagrams (14.1.SP3) Diagrams - Administration Rev 4.0
218 pages
TM-1855 AVEVAEverything3D™ (2.1) Schematic 3D Integrator Rev 1.0 PDF
No ratings yet
TM-1855 AVEVAEverything3D™ (2.1) Schematic 3D Integrator Rev 1.0 PDF
117 pages
TM-1104 AVEVA Plant (12.1) Equipment Modelling Rev 1.0
100% (1)
TM-1104 AVEVA Plant (12.1) Equipment Modelling Rev 1.0
128 pages
TM-1104 AVEVA Plant (12.1) Equipment Modelling Rev 2.0 PDF
No ratings yet
TM-1104 AVEVA Plant (12.1) Equipment Modelling Rev 2.0 PDF
128 pages
TM-1000 AVEVA Plant (12.1) PDMS Hands-On Overview Rev 1.0
100% (1)
TM-1000 AVEVA Plant (12.1) PDMS Hands-On Overview Rev 1.0
92 pages
TM-1873 AVEVA Everything3D™ (2.1) Isodraft Administration Rev 2.0
83% (6)
TM-1873 AVEVA Everything3D™ (2.1) Isodraft Administration Rev 2.0
66 pages
TM-1403 AVEVA Plant (12.1) PML Applied Rev 1.0
100% (5)
TM-1403 AVEVA Plant (12.1) PML Applied Rev 1.0
55 pages
TM1830 - AVEVA Everything 3D - DRAW
67% (3)
TM1830 - AVEVA Everything 3D - DRAW
375 pages
TM 1870 Aveva Everything3d 2 1 Draw Administration Rev 20pdf
No ratings yet
TM 1870 Aveva Everything3d 2 1 Draw Administration Rev 20pdf
206 pages
Aveva Everything3d 11 Pipework Modellin
100% (2)
Aveva Everything3d 11 Pipework Modellin
309 pages
TM-2268 AVEVA (12 Series) .Net Customisation Training Rev 4.0
No ratings yet
TM-2268 AVEVA (12 Series) .Net Customisation Training Rev 4.0
74 pages
TM-1402 AVEVA Plant (12.1) PML Form Design Rev 3.0
100% (1)
TM-1402 AVEVA Plant (12.1) PML Form Design Rev 3.0
116 pages
E3d Book
67% (3)
E3d Book
179 pages
LEXICON Command Reference Manual
No ratings yet
LEXICON Command Reference Manual
68 pages
TM-1840 AVEVA Catalogue (2.1) Piping Catalogues and Specifications Rev 6.0
100% (7)
TM-1840 AVEVA Catalogue (2.1) Piping Catalogues and Specifications Rev 6.0
296 pages
11 E3D Training Slides Week1
100% (4)
11 E3D Training Slides Week1
71 pages
APS Project
50% (2)
APS Project
40 pages
PML Manual PDF
100% (2)
PML Manual PDF
178 pages
Manual of E3D
100% (1)
Manual of E3D
125 pages
100 PML's Tips and Tricks
100% (7)
100 PML's Tips and Tricks
28 pages
Equipment Modelling E3D
100% (10)
Equipment Modelling E3D
104 pages
TM-1801 AVEVA Everything3D™ (2.1) Foundations Rev 3.0
100% (4)
TM-1801 AVEVA Everything3D™ (2.1) Foundations Rev 3.0
146 pages
TM-1400 AVEVA Plant (12.1) Administering Global Projects Rev 2.0
No ratings yet
TM-1400 AVEVA Plant (12.1) Administering Global Projects Rev 2.0
76 pages
TM-1832 AVEVA Everything3D Area-Based Automatic Drawing Production Rev2.0
100% (1)
TM-1832 AVEVA Everything3D Area-Based Automatic Drawing Production Rev2.0
42 pages
TM 1831 AVEVA Everything3D™ Draw Automatic Drawing Production Rev
No ratings yet
TM 1831 AVEVA Everything3D™ Draw Automatic Drawing Production Rev
54 pages
Aveva P&id
100% (5)
Aveva P&id
814 pages
AVEVA - E3D - Supports Administration
No ratings yet
AVEVA - E3D - Supports Administration
193 pages
PML Animation Guide for Aveva E3D/PDMS
100% (1)
PML Animation Guide for Aveva E3D/PDMS
13 pages
TM-1803 AVEVA Everything3D™ (1.1) Reporting Rev 1.0-1-55
No ratings yet
TM-1803 AVEVA Everything3D™ (1.1) Reporting Rev 1.0-1-55
55 pages
Cechinel Et Al., 2016
No ratings yet
Cechinel Et Al., 2016
15 pages
Ei027 000 Ed Pi Mto 527 R0
No ratings yet
Ei027 000 Ed Pi Mto 527 R0
3 pages
Chen Et Al., 2015
No ratings yet
Chen Et Al., 2015
8 pages
Lecture 1b
No ratings yet
Lecture 1b
66 pages
Exercise 3 2024 Solutions
No ratings yet
Exercise 3 2024 Solutions
6 pages
Beldean-Galea Et. Al, 2013
No ratings yet
Beldean-Galea Et. Al, 2013
9 pages
Xianling Et Al., 2005
No ratings yet
Xianling Et Al., 2005
5 pages
Zhang Et. Al 2019
No ratings yet
Zhang Et. Al 2019
9 pages
Zhu Et Al., 2013
No ratings yet
Zhu Et Al., 2013
9 pages
LECTURE2 Heat Exchangers
No ratings yet
LECTURE2 Heat Exchangers
29 pages
ORC Example Solution
No ratings yet
ORC Example Solution
6 pages
Exercise 4 2024 Solutions
No ratings yet
Exercise 4 2024 Solutions
4 pages
Proposed Project Topics in MSK550
No ratings yet
Proposed Project Topics in MSK550
1 page
Exercise 3 2024
No ratings yet
Exercise 3 2024
3 pages
Exercise 2 2024
No ratings yet
Exercise 2 2024
2 pages
LECTURE7 Marine and Automotive
No ratings yet
LECTURE7 Marine and Automotive
37 pages
Enzymes WWT
No ratings yet
Enzymes WWT
46 pages
LECTURE1 Introduction
No ratings yet
LECTURE1 Introduction
44 pages
Answers Enzymes
No ratings yet
Answers Enzymes
2 pages
Lecture4 Orc
No ratings yet
Lecture4 Orc
44 pages
Chap 7.2 Numerical Control
No ratings yet
Chap 7.2 Numerical Control
34 pages
Design Optimization Techniques Explained
No ratings yet
Design Optimization Techniques Explained
59 pages
Chap 5.3 Structural Optimization & Introduction To Search Methods
No ratings yet
Chap 5.3 Structural Optimization & Introduction To Search Methods
28 pages
Chap 8 Automation in Manufacturing
No ratings yet
Chap 8 Automation in Manufacturing
31 pages
Introduction to Optimization in Engineering
No ratings yet
Introduction to Optimization in Engineering
29 pages
IOTAFLOW Profile NEW
No ratings yet
IOTAFLOW Profile NEW
14 pages
LED Lighting Control Station DIN
No ratings yet
LED Lighting Control Station DIN
2 pages
Electromagnetic Theory Course Overview
100% (1)
Electromagnetic Theory Course Overview
2 pages
Cambium Spectrum Analyzer
100% (1)
Cambium Spectrum Analyzer
7 pages
Bella's Employee Satisfaction Insights
No ratings yet
Bella's Employee Satisfaction Insights
5 pages
Procedure For Cleaning An Engine Lubrication System When Contaminated With Engine Coolant Containing Antifreeze (1000, 1348, 1395) (M0107162-01)
No ratings yet
Procedure For Cleaning An Engine Lubrication System When Contaminated With Engine Coolant Containing Antifreeze (1000, 1348, 1395) (M0107162-01)
2 pages
SAP Letter of Credit Accounting Guide
No ratings yet
SAP Letter of Credit Accounting Guide
8 pages
Cambridge O Level Mathematics Mark Scheme
No ratings yet
Cambridge O Level Mathematics Mark Scheme
8 pages
Professional Regulation Commission Table of Specifications
100% (1)
Professional Regulation Commission Table of Specifications
8 pages
04 Check List For Fire Extinguisher - pdf-1
91% (11)
04 Check List For Fire Extinguisher - pdf-1
1 page
Aerial Photography and Photogrammetry Guide
No ratings yet
Aerial Photography and Photogrammetry Guide
21 pages
Polarisation, Arrogance, and Dogmatism: Philosophical Perspectives (Routledge)
No ratings yet
Polarisation, Arrogance, and Dogmatism: Philosophical Perspectives (Routledge)
15 pages
New Functions Manual 3 - 5 - 3
No ratings yet
New Functions Manual 3 - 5 - 3
8 pages
1980 - Nisbet - History of The Idea of Progress
100% (1)
1980 - Nisbet - History of The Idea of Progress
380 pages
Oilfield Tubular Inspection Services
No ratings yet
Oilfield Tubular Inspection Services
7 pages
Lawton Tubes Medical Copper Catalogue
No ratings yet
Lawton Tubes Medical Copper Catalogue
12 pages
Quiz - 03 - Self Review Quiz - Acad - Sle201v15 Courseware - SUSE Academy
No ratings yet
Quiz - 03 - Self Review Quiz - Acad - Sle201v15 Courseware - SUSE Academy
3 pages
Cs302 Current Final Term Papers
100% (1)
Cs302 Current Final Term Papers
6 pages
Dakiou Py Series Die Cutting Machine Manual
100% (1)
Dakiou Py Series Die Cutting Machine Manual
25 pages
Porsche Boxster Technical Manual
100% (2)
Porsche Boxster Technical Manual
136 pages
AIM:-Service Positive Crankcase Ventilation System: Practical - 3
No ratings yet
AIM:-Service Positive Crankcase Ventilation System: Practical - 3
6 pages
MERLO - ROTO 45.21 MCSS Product Sheet518
No ratings yet
MERLO - ROTO 45.21 MCSS Product Sheet518
4 pages
1 s2.0 S2590123023007557 Main
No ratings yet
1 s2.0 S2590123023007557 Main
8 pages
Mã học phần: - Số tín chỉ (hoặc đvht) : Lớp: Họ, tên thí sinh:..................................................................... Mã sinh viên: ............................
No ratings yet
Mã học phần: - Số tín chỉ (hoặc đvht) : Lớp: Họ, tên thí sinh:..................................................................... Mã sinh viên: ............................
2 pages
Pesticide Residues in French Soils
No ratings yet
Pesticide Residues in French Soils
10 pages
Feasibility Report Urja
No ratings yet
Feasibility Report Urja
23 pages
2013 02 Seisspace Promax Data Sheet
No ratings yet
2013 02 Seisspace Promax Data Sheet
4 pages
Sist en 10216 1 2014
No ratings yet
Sist en 10216 1 2014
11 pages
VWR Gravity Convection Incubator Manual
No ratings yet
VWR Gravity Convection Incubator Manual
19 pages
Your Inner Edge Your Inner Edge: The Big Idea The Big Idea
No ratings yet
Your Inner Edge Your Inner Edge: The Big Idea The Big Idea
8 pages