Connect Clash Manager

Delete - deletes the selected connection record from the AVEVA Clash Manager configuration file (does not delete any clash data from the SQL Server database)

•

Add - restores the connection record.

Note:

Details of configured projects are stored in a clash manager configuration file in the Project DFLTS folder: %PROJDFLTS%\clashManager.xml

Delete Project

Deletes the SQL Server data.

Copy Connection

Copies the selected connection.

Use the AVEVA Clash Manager Select Host Database window to select an SQL host sever.

Use the AVEVA Clash Manager SQL Server Instance window to select an SQL Server Instance.

Select from the drop down populated with a list of available SQL server host/instances.

The SQL Server Instance must have been created with a case-insensitive collation.

Note:

Where all instances for a particular host are not show, the instance can ne entered manually, then refresh.

Enter the login details of a user with DBA rights, that is rights to create another user, rights to create tables, indexes and so on.

Use the AVEVA Clash Manager SQL Server Database window to select an SQL Server Database.

Select an existing SQL Server Database found on the selected host, from the Database pane.

Note:

The necessary SQL Server Database must already have been created using the SQL Server Management Studio.

Select a case-sensitive collation for the ClashManager project which is appropriate to the local language.

Note:

That there are two distinct collations used, one for the server instance and one for the project. The collation of SQL Server Instance must be case-insensitive, Latin1_General_CI_AS is a suitable choice. The collation used when creating a project should be case-sensitive as the underlying application is case-sensitive.

The details of the selected SQL Server and connection configuration are displayed.

The major parts of AVEVA Clash Manager comprise the UI (displaying the clash report) and the clasher interface which includes the run process (which runs desclash) and the loader (which loads clash data into the SQL Server/Oracle database). These are separate processes each of which require separate database connections.

The UI uses ADO.NET, three of the available protocols are supported: SQL OLE the ADO clash interface supports the OLE provider Sq101eDB.1

If required the Command Timeout can be modified during the life time of a project if a SQL Server timeout occurs during the load process.

The Connection Alias identifies the particular record where more than one connection is configured, a Login window is displayed where the alias is the identifier. The Login window is also displayed if the automated login process fails as a result for example - a password change on the server.

Note:

A FREE user or a member of the DESADMIN team has an opportunity to edit the connection details by selecting Connection Wizard on the Login window.

The Clash Manager Database Login details relating to the connection configuration are displayed in the AVEVA Clash Manager - Clash Manager Database Login window.

Enter in the New Database Login part of the AVEVA Clash Manager - Clash Manager Database Login window the Username and Password of the new SQL Server user that will own the tables, indexes, clash data and so on.

The default Username is PCLAMxxx and the password is PWxxx, where xxx is the 3D model project code.

Note:

The SQL Server user password can be changed externally, in that case, select Edit Connection from the AVEVA Clash Manager - Clash Manager Project Connections window to update the clash manager configuration.

Populate the AVEVA Clash Manager - 3D Model Login window with the login details for a 3D model.

Enter a 3D Model username and password which will be used to initiate the TTY sessions which will run desclash and load the resulting data. The TTY sessions run with the READONLY flag.

Use the AVEVA Clash Manager - Optional Clash Manager Project Details window to enter the Project Title, Project Number and Client output when a clash report is saved using Save As.

Display units can be fixed to display metric, finch only or user preference.

Use the AVEVA Clash Manager - Confirmation window to review details before selecting Finish to initiate creating the project.

Oracle

Use AVEVA Clash Manager Project Connections window to create an Oracle hosted project.

Create Project

Creates a new Oracle hosted project to hold the clash information.

Note:

Normally only one connection to a database is necessary.

Add Connection

Adds details of an existing Oracle database.

Edit Connection

Changes the connections parameters.

Recreate/Upgrade Database Objects

Use to repair lost database views, indexes or upgrade a non-Unicode project to Unicode.

From the grid pane of the AVEVA Clash Manager Project Connections window populated with a list of connections, use the right click menu to:

•

Delete - deletes the selected connection record from the AVEVA Clash Manager configuration file (does not delete any clash data from the Oracle database)

•

Add - restores the connection record.

Note:

Details of configured projects are stored in a clash manager configuration file in the Project DFLTS folder: %PROJDFLTS%\clashManager.xml

Delete Project

Deletes the Oracle data.

Copy Connection

Copies the selected connection.

Use the AVEVA Clash Manager Select Host Database window to select an Oracle host database.

Use the AVEVA Clash Manager Oracle Database Connection Configuration window to enter the details of the selected Oracle database and connection configuration.

The Connect String identifies the Oracle instance and this should be configured in the Oracle tnsname.ora configuration file.

The major parts of AVEVA Clash Manager comprises the UI displaying the clash report and the clash interface which includes the run process which in turn runs the desclash. The loader loads clash data into the Oracle database.

These separate processes each require separate connections: the UI uses ADO.NET, three protocols are supported which are Oracle, SQL and OLE.

For Oracle hosted projects, the Native Oracle Pro*C is the only supported Clasher Interface. The 32bit Oracle client version 12c must also be installed to support that interface.

The OLE providers OraOLEDB.Oracle and sq101eDB.1 are supported.

The Connection Alias identifies the particular connection record where more than one connection is configured, a Login window is displayed, where the alias which is the identifier is displayed. The Login window is also displayed if the automated login process fails, this could for example, be due a password change on the server.

Note:

A FREE user or a member of the DESADMIN team can edit the connections, by selecting Connection Wizard on the Login window.

The Clash Manager Database Login details relating to the connection configuration are displayed in the AVEVA Clash Manager - DBA Login window.

Enter in the DBA Login part of the AVEVA Clash Manager - Clash Manager DBA Login window the Username and Password of the new Oracle user with the rights to create another user, create tables, indexes and so on.

Use the AVEVA Clash Manager Oracle Tablespaces window to select the tablespaces from the drop downs populated with a list of available existing tablespaces in which AVEVA Clash Manager will store data.

Note:

The advice of the administrator of an existing Oracle database may be required in order to select the correct tablespace in a personal oracle environment the defaults ought to be suitable.

The Clash Manager Database Login details relating to the connection configuration are displayed in the AVEVA Clash Manager - Clash Manager Database Login window.

Enter in the New Database Login part of the AVEVA Clash Manager - Clash Manager Database Login window the Username and Password of the new Oracle user that will own the tables, indexes, clash data and so on.

The default Username is PCLAMxxx and the password is PWxxx, where xxx is the 3D model project code.

The Oracle user password can be changed externally, in that case, select Edit Connection from the AVEVA Clash Manager - Clash Manager Project Connections window to update the clash manager configuration.

Populate the AVEVA Clash Manager - 3D Model Login window with the login details for a 3D model.

Enter a 3D Model username and password which will be used to initiate the TTY sessions which will run desclash and load the resulting data. The TTY sessions run with the READONLY flag.

Use the AVEVA Clash Manager - Optional Clash Manager Project Details window to enter the Project Title, Project Number and Client output when a clash report is saved using Save As.

Display units can be fixed to display metric, finch only or user preference.

Use the AVEVA Clash Manager - Confirmation window to review details before selecting Finish to initiate creating the project.

DBA Login

During project creation, where a DBA login is required, it’s possible to provide a ‘DBA’ login with insufficient rights, that is with rights to create some parts of the schema and not others.

This can lead to the user being unable to edit or delete the connection using ClashManager options. If this occurs, the incomplete database username should be removed using DBA admin tools and the failed connection removed from the ClashManager configuration file (in the 3D project DFLTS folder).

If there is at least one other correctly configured database connection, it may be used together with the Administrator Options in ClashManager to remove the failed connection from the ClashManager configuration file.

If there are no other correctly configured database connections, the ClashManager configuration file may simply be deleted.