# Introduction **ClashManager** provides high-level functions for PDS® interference checking. It has been developed to save time and money when clashes in a plant design need to be identified and resolved. **ClashManager** fully supports SmartPlant® Review version 5.0.1 or later. Clashes can be examined directly in SmartPlant Review or MicroStation®. A new tool, `ClashViewControlCube`, makes it much easier to select viewing directions while working in SmartPlant Review. **ClashManager** is designed to identify large numbers of incorrect clashes and to approve them automatically. This makes it much easier for the user to identify real clashes. Depending on the project size and program configuration, the number of collisions that need to be examined can be reduced by a factor of 10 to 50. Filter functions and detailed configuration options allow clashes to be preselected before visual examination takes place. This reduces the number of collisions in a project to a level at which the user can examine and handle the remaining real clashes in the viewer. A tabular representation with a wide range of filter functions considerably improves the detection of incorrect clashes. A graphical viewer makes this even easier and offers the possibility of immediate intervention. The software is closely integrated with PDS, which means that the results can be written back to PDS for further use. Previously configured test mechanisms are stored and loaded with the next test procedure of the project. This substantially improves the identification of new collisions during the planning process. It is also possible to cancel all changes and restore the original status of all clashes, as well as to delete the list of collisions in PDS. The envelope builder and interference checker can also be run directly from **ClashManager**. Parallel batch processing increases file-building speed. # Installation ## Setup Requirements: - Supported operating systems: - Microsoft Windows XP - Microsoft Windows Server 2003 - Microsoft Windows Vista - Microsoft Windows 7 or later - PDS version 6.4 or later - MicroStation SE or later - Microsoft Excel 2000 or later - SmartPlant Review 5.0.1 or later # Envelope Builder & Interference Checker module ## Envelope Builder The envelope builder receives element attributes from the database and generates envelope files, `*.env`. Envelope calculation is required for collision detection. ![](./media/ClashManager_image11.png) Envelope files that are already up to date are ignored during an envelope builder run. All other envelope files are generated again. This is especially useful for large projects, see also the PDS documentation from Intergraph. Choose all models and interference areas in the **Envelope Builder & Interference Checker** window for which you want to generate envelope files. The colour marking for processed items is as follows: - Green: envelope files are up to date, or the batch process was successful - Yellow: data are currently being updated - Red: the envelope builder process finished unsuccessfully > You can drop a plain ASCII file with model and drawing names (separated by line breaks) onto the tree view to automatically tick the check boxes of these models/drawings. Wildcards (\*, ?) may be used to define the model/drawing names in the ASCII file. The **Start** button starts the envelope generation and interference checking. In Intergraph Batch Manager, **Disable Job Inflow while Running Job** may not be ticked (if it is ticked it would block sending of several jobs at once): ![](./media/ClashManager_image12.png) Envelope Builder processes can work in parallel. **Run Limit** is a program-defined limit, while the practical limit is determined by the number of available licences. We recommend that you set the scheduling properties for the `pdclash_server` queue in Intergraph Batch Manager to up to 60 parallel processes in order to speed up envelope building. > The number of parallel processes depends on the number of available PDS licences. Setting of queue properties in Batch Manager/pdclash_server: ![](./media/ClashManager_image13.png) ## Interference Checker The Interference Checker receives the attributes from the files created by Envelope Builder and calculates the collisions, see also the PDS documentation from Intergraph. ![](./media/ClashManager_image14.png) PDS collision detection after envelope generation can be activated by selecting **Run Interference Checker**. Effective analysis in **ClashManager** is possible only if both processes finish successfully for all elements. The **Selected areas** option limits the Interference Checker run to the selected areas. If **Complete project** is enabled, checking the whole project can take a long time. ## Menu bar ### File #### Select PDS project #### Load settings from file Load/import options from a configuration file. #### Save settings to file Save/export options to a configuration file. #### Switch to approval module... Click **Switch to approval module...** to view and approve or unapprove clashes, see the **Approval module** section below. #### Most recently used projects Shows the most recently used projects which can be loaded directly (if still available). #### Exit Terminates **ClashManager.** ### View #### Event window Toggles the display of the event window. ### Tools #### Report status of envelope files for selected models Generates an Excel report for all selected models with envelope file status (green -- up to date, yellow -- not up to date, red -- envelope file is missing). ![](./media/ClashManager_image15.png) #### Clean history of all clashes in PDS Cleans the Clash History Table (pdtable_135). This speeds up loading and saving of clashes in **ClashManager**. Clash Review History Information (pdtable_135): One record per clash is created when it is reviewed after a run. Each time this clash is reviewed using **ClashManager**, the record in pdtable_135 is updated. If the same clash is present on the next run of Interference Checker, a new record is created in pdtable_135 with the same unique_clash_id. If a clash is never reviewed using **ClashManager**, no record will be created for this clash. #### Delete all clashes from PDS Deletes all clash entries from the PDS database. **This is required only in the event of errors in PDS and should not normally be needed by the user.** #### Options ![](./media/ClashManager_image16.png) ![](./media/ClashManager_image17.png) You should also make the following settings in Intergraph Batch Manager: - \'Disable Job Inflow while Running Job\' in properties of \'pdclash_server\' queue may not be ticked - \'Run Limit\' in scheduling properties of \'pdclash_server\' queue should be increased. The number of parallel processes is depending on the number of available PDS licences! If the job is not responding and the timeout is reached, the Envelope Builder or Interference Checker process will be killed automatically. Once a clash is found, it will always belong to the design area or project marker file in which it was found. It is therefore important to use either the \'Complete project\' option or the \'Selected areas\' options consistently for the life of a project. Please refer to the Intergraph `PD_Clash User's Guide` for additional information. #### Privilege manager The **Privileges manager** allows you to lock functions for specific users/groups. The assignment of privileges is based on the Windows (domain) users and groups. This means that you do not have to establish a new privileges management system. Group and user rights are linked by an OR operation: If a group has a certain privilege in **ClashManager**, every user in this group will have this privilege, even if this privilege is not explicitly stated in the settings for this user. The access rights are stored in an Access database (**ClashManager**.mdb). This is located in the proj_file directory. The privileges are thus the same for all the projects in a proj_file. Access to the Access database should be controlled using the Windows access rights. Privilege manager is not available when the user works in offline mode of **ClashManager** (offline mode means that **ClashManager** has no connection with the PDS database of the project reviewed). The default setting is "Allow" for every user and group. ### Language You can use the **Language** menu command to switch between languages at any time. You do not have to restart **ClashManager**. The most recent language setting is saved automatically. #### Language editor The **Language editor** allows you to translate the interface into other languages or to modify the existing translation tables. ![](./media/ClashManager_image18.png) - Select source language - Select target language Select the source and target language. You can then translate the individual items. If the required target language does not exist, you can add it by clicking the \"Add\" button. Save the completed translation by clicking the **Save** button. ### Help #### Contents Opens the **ClashManager** online documentation (Contents tab). #### Index Opens the **ClashManager** online documentation (Index tab). #### Search Opens the **ClashManager** online documentation (Search tab). #### Update licence See the **Licence** section. #### About **About** shows version and copyright information about the software. # Command line mode The **ClashManager Envelope Builder & Interference Checker module** can also be started from the command line. Use the following syntax: \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-- CAXperts **ClashManager** \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-- Command-line arguments for `ClashManager.exe`: `/Mode mode` - Running modes: APPROVE - Approval module CHECK - Envelope Builder and Interference\ Checker module `/CMD control_file.cmd` - Path to the control file. If control file is not defined, last control file will be used. `/Project project_name` - PDS project name. If project name is not defined, last project will be used. `/Config config_file.ini` - Configuration file. If not defined, last configuration file\ will be used. `/batch` - If defined, Envelope Builder and Interference Checker will be run in\ batch mode Example: `ClashManager.exe /Mode check /CMD control_file.cmd /Project project_name /Config config_file.ini /batch` # Approval module ![](./media/ClashManager_image19.png) The main window consists of - menu bar - tool bar - list of clashes - log - status bar There are three ways to load a list of clashes: 1. from PDS 2. from an Access database (project schema available) 3. from an Access database, project schema not available, that is, `offline mode`, which is also displayed in the window caption > In offline mode, only Save to Microsoft Access database is available; additionally Show clashes in MicroStation, Automated generation of SmartPlant Review session and Privileges Manager will not be available. The main window shows all clashes in the selected PDS project. The **Approve** and **Unapprove** buttons on the tool bar assign the corresponding status to the selected clashes. The columns *review_comment* and *action_discipline* may be edited by the user. > To select more than one clash at once, press down the Ctrl key or Shift key like in Windows Explorer while clicking on the rows. #### Order of columns Column order may be changed by dragging & dropping column headers (left mouse button). #### Sort If you click on a column header, the list will be sorted depending on this column. Click once more to toggle between ascending and descending sort. #### Filter The yellow row is for entering filter conditions. The conditions may be selected from combo boxes or also be directly entered. All lines that do not match the conditions will be hidden. Example: selecting **Piping** in column **discipline_a** and **Piping** in column **discipline_b** shows clashes between piping elements. > The filter can be reset by clearing the filter field. #### Group ![](./media/ClashManager_image20.png) You may drag & drop column headers to the dark grey area above to group by these columns. The order may be also changed via drag & drop. Example: Use models (model_a) as first group and discipline (discipline_a) as second one. ![](./media/ClashManager_image21.png) More useful collision filters and sorts: - Filter by status: Unapproved\ All approved clashes (usually a large number) will be hidden. - Filter by type of clash: If not already set in the approval filter, you could filter by "Hard-Hard", most "real" collisions are of this type. ## Menu bar ### File #### Load clashes from PDS #### Load clashes from file Loads a database file (\*.mdb) which contains a **ClashManager** list of clashes.
You can review the clashes in these databases without having PDS installed on your system.
If a project schema from an Access database does not exist, the privilege manager will not be available and therefore no user restrictions will apply.
#### Load settings from file Load/import options and approval filter settings from a configuration file. #### Save settings to file Save/export options and approval filter settings to a configuration file. #### Save changes ![](./media/ClashManager_image22.png) Saves all changes from **ClashManager** to PDS or Access database. Changes will be only written back to PDS if the *recent_review_date* is newer as in the project schema. > In offline mode, only **Save to Microsoft Access database** is available. #### Switch to Envelope Builder & Interference Checker module Click on **Switch to Envelope Builder & Interference Checker...** to generate envelopes of models and detect collisions. The **Envelope Builder & Interference Checker** will show up (see chapter **Envelope Builder & Interference Checker** above) #### Most recently used projects Shows the most recently used projects which can be loaded directly (if still available). #### Exit Terminates **ClashManager.** ### Clash #### Approve selected clashes Sets the state of selected clashes to "Approved" (same as "Approve False Clash" in PD_Shell Interference Approval Manager). If necessary, the description dialogue window will show up. #### Unapprove selected clashes Sets the state of selected clashes to "Unapproved". If necessary, the description dialogue window will show up. #### Show selected clash Shows a clash in MicroStation or SmartPlant Review, the viewer may be selected in this form: ![](./media/ClashManager_image23.png) > Only standard PDS disciplines (piping, equipment, structural) can be shown in SmartPlant Review. Select a clash and click on **Show selected clash** to display the clash in MicroStation or SmartPlant Review. If MicroStation was selected, the display will look like this: If SmartPlant Review was selected and the automated generation of the SmartPlant Review session is switched on (default) **ClashManager** will configure the session on-the-fly based on the clashes displayed in its list of clashes. If no SmartPlant Review session configuration file is defined and the automated generation of the SmartPlant Review session is switched off, the **Configuration Wizard** will show up: 1. Click **Yes** to configure a Design Review session:\ ![](./media/ClashManager_image25.png) ```{=html} ``` 4. To create a new session, select the first option and click **Next** (to use an existing session tick the second option, click **Next**, select the session file an skip the rest of this enumerated list)\ ![](./media/ClashManager_image26.png) 5. You may choose now between express or complete configuration. Complete configuration means that database information (DRV files) is generated, which may take some time.\ ![](./media/ClashManager_image27.png) 6. Select a SmartPlant Review interface file (using the **Browse...** button) and click **Next**:\ ![](./media/ClashManager_image28.png) 7. Remove ticks on models you don't want to use, tick **Add weld graphics** (available in complete configuration only) if you want to do so and click **Next**:\ ![](./media/ClashManager_image29.png) 8. **ClashManager** will now configure the session (this may take some time) and finally display this window:\ ![](./media/ClashManager_image30.png) The Design Review session is now ready: The main window will disappear and a toolbar showing a single row from the list of clashes will appear. The buttons on this toolbar allow you to navigate through the individual clashes from the clash list. Any selected clash will immediately be displayed in MicroStation or SmartPlant Review. The toolbar will always stay on top of all windows. The toolbar shows these buttons: - ![](./media/ClashManager_image32.png) Approve selected clash - ![](./media/ClashManager_image33.png) Unapprove selected clash - ![](./media/ClashManager_image34.png) Go to first clash - ![](./media/ClashManager_image35.png) Go to previous clash - ![](./media/ClashManager_image36.png) Go to next clash - ![](./media/ClashManager_image37.png) Go to last clash - clash_id textbox and **OK** button: go to the clash ID entered - ![](./media/ClashManager_image38.png) Refresh/Reset display - ![](./media/ClashManager_image39.png) Zoom in - ![](./media/ClashManager_image40.png) Zoom out - ![](./media/ClashManager_image41.png) Show ClashViewControl (common views), only for SmartPlant Review - ![](./media/ClashManager_image42.png) Create report ### View #### Event window Toggles the display of the event window. ### Tools #### Report ![](./media/ClashManager_image43.png) **ClashManager** supports these file types for reporting clashes: - XLS (Microsoft Excel) - HTML (web browsers) - DOC (Microsoft Word) - PDF (Adobe Acrobat Reader)\ Saves a report with collision data and four views from MicroStation or SmartPlant Review: Isometric View, Top View, Back View and Left View - Clashes quantity per area (Microsoft Excel) - MDB (Microsoft Access) Use the options at the top of the dialogue to decide if all or only selected elements of the list will appear in the report. ##### Template Select a template file (\*.xls) to add your company logo or branding to the Excel export (Only available if **Use Excel template file** is checked and an Excel report type is selected). To save a report, it is necessary to select a target file name and directory. The report will be displayed by the Windows standard application after its creation. (e.g. usually Adobe Acrobat or Adobe Acrobat Reader for PDF and Microsoft Excel for XLS files) ![](./media/ClashManager_image45.png) #### Approval filter In the **Approval filter** window of **ClashManager** you may choose several filter criteria to set the status of clashes to *Approved*. ##### Selection of models ![](./media/ClashManager_image46.png) You can select here any models which may get the **Approved** attribute without further reviewing (e.g. test files, mesh reinforcement). ##### Selection of components ![](./media/ClashManager_image47.png) When you select the **Components** tab, three further tabs appear with the following component categories: - Piping - Equipment - Structural Within these three categories, you select the components which are **not** to be taken into account during clash checking, e.g. pipe clamps, verification equipment (person, truck, auxiliary lines etc.), floor slab etc. - The list on the left shows all available components. - The list on the right is used to enter all the components for which clashes are not to be taken into account. Use the **\>\> \> \<\< \<** buttons to move the components between the two lists. You can select components even more quickly by entering the first letters of the components in the filter fields above the lists. ##### Options Approve clashes which match the rules defined in **Options**. ![](./media/ClashManager_image48.png) ###### Clashes within same discipline This approves clashes in which both elements are within the same discipline (e.g. Architecture). ###### Clashes within same model/discipline Clashes within a single model will be approved for the selected discipline. ###### Approve clashes with type A selection list allows you to exclude certain types of clashes in the filter: - Hard = Component - Soft = Insulation - Construction = Equipment removal space, escape route, \... > If the clash types were not defined in the ClashManager configuration file, this list only shows numbers which correspond to the PDS clash types. ###### Clashes within same line in same model This option approves clashes where the components lie within the same line (same line number label, the line clashes with itself). ###### Clashes within same equipment This option approves clashes where the components lie within the same equipment element (the equipment element clashes with itself). #### Privilege manager The **Privileges Manager** allows you to lock functions for specific users/groups. The assignment of privileges is based on the Windows (domain) users and groups. This means that you do not have to establish a new privileges management system. Group and user rights are linked by an OR operation: If a group has a certain privilege in **ClashManager**, every user in this group will have this privilege, even if this privilege is not explicitly stated in the settings for this user. The access rights are stored in an Access database (**ClashManager**.mdb). This is located in the proj_file directory. The privileges are thus the same for all the projects in a proj_file. Access to the Access database should be controlled using the Windows access rights. The default setting is "Allow" for every user and group. #### Options ##### General On the **General** tab you may decide if **ClashManager** should show the clashes in Bentley MicroStation or Intergraph SmartPlant Review. It is also possible to decide every time individually (to do so, tick the checkbox at the bottom of the tab). ![](./media/ClashManager_image49.png) If you want to use MicroStation, select the ustation.exe of your MicroStation installation in the combo box and a seed file (DGN format) in the textbox in the middle of the tab (you may use the **Browse** buttons to select the files). The seed file will be used as a template for the display of the clashes in MicroStation. ![](./media/ClashManager_image50.png) Automated generation of the SmartPlant Review session is switched on by default: **ClashManager** will configure the session on-the-fly based on the clashes displayed in its list of clashes. This happens, if the SmartPlant Review session working directory is defined: - **ClashManager** will check if the models in this directory are up-to-date. Up-to-date models will be immediately used in the SmartPlant Review session, out-of-date model files will be copied from the original model file location. - All files from this working directory will also be reused at the next start of **ClashManager**. If the working directory is not defined all SmartPlant Review session files will be stored in the TEMP directory and will be deleted on program exit. The user may also choose to use an existing SmartPlant Review session which will be displayed independently of clashes shown in the list of clashes. ##### Clash description ![](./media/ClashManager_image51.png) The **Clash description** tab offers you textboxes to key in user specific comments for approve/unapprove actions. Example for user-specific comments: Approved by constructor A or Unapproved by project manager B If the checkbox **Let me input the description** is checked, a dialogue will show up every time the status of an item has changed, otherwise the default text will be used. ##### Volume filter ![](./media/ClashManager_image52.png) The volume filter defines the volume in which clashes are shown: You may select an interference area in the combo box or enter the corner points of the filter volume. Press **Set Design Volume Coordinates System Monument** to edit these settings: ![](./media/ClashManager_image53.png) ##### Advanced filter ![](./media/ClashManager_image54.png) This filter may be set to display only clashes within a model, discipline, area or SiteID (or a list of them). The clash will be shown if one of its components fulfils the condition. ##### Advanced ![](./media/ClashManager_image55.png) ###### Component name split This text field may contain one or more characters which will split the component's name in the list of clashes (the separator characters must be valid; otherwise the separator will be ignored). - Example:\ Component: PIPE-100 GSC FT U1CD1Q-0\ Separator: - - Appearance in Clash Viewer list:\ Column comp_a\_0: PIPE\ Column comp_a\_1: 100 GSC FT U1CD1Q\ Column comp_a\_2: 0 ###### Display of unapproved clashes You may choose to show unapproved clashes only by ticking the checkbox. If you tick **Ask me,** **ClashManager** will ask you on certain occasions (program start etc.) how it should display unapproved clashes: ![](./media/ClashManager_image56.png) ###### Colours Clashes are marked up by colours (in PDF reports and SmartPlant Review sessions) which you can choose by clicking on the coloured areas next to the Component A/Component B labels. A Windows standard colour selection dialogue will show up: ![](./media/ClashManager_image57.png) ###### Start-up options You may select here, if **ClashManager** should show a tip of the day window on start-up and if the last project should be automatically reloaded. ### Language You can use the **Language** menu command to switch between languages at any time. You do not have to restart **ClashManager**. The most recent language setting is saved automatically. #### Language editor The **Language editor** allows you to translate the interface into other languages or to modify the existing translation tables. ![](./media/ClashManager_image18.png) - Select source language - Select target language Select the source and target language. You can then translate the individual items. If the required target language does not exist, you can add it by clicking the \"Add\" button. Save the completed translation by clicking the **Save** button. ### Help #### Contents Opens the **ClashManager** online documentation (Contents tab). #### Index Opens the **ClashManager** online documentation (Index tab). #### Search Opens the **ClashManager** online documentation (Search tab). #### Update Licence See the **Licence** section. #### About **About** shows version and copyright information about the software. ## Tool bar The toolbar contains select commands from the menu bar: - ![](./media/ClashManager_image32.png) Approve selected clash(es) - ![](./media/ClashManager_image33.png) Unapprove selected clash(es) - ![](./media/ClashManager_image58.png) Approval filter - ![](./media/ClashManager_image59.png) Show selected clash - ![](./media/ClashManager_image42.png) Create report - ![](./media/ClashManager_image60.png) Save changes ## Log files ![](./media/ClashManager_image61.png) **ClashManager** creates a log file, `*.log`, in a subfolder of the Windows® temporary folder, usually `c:\temp\ClashManager`, for debugging purposes. This log file records the date and time of every action carried out during a **ClashManager** session. It can be opened by clicking the log section of the **ClashManager** main form. Naming of the log files follows this rule: YYYY-MM-DD_hhmmss_projectname.log Example: 2005-07-27_110408_pdstest.log So the list of log files can be easily sorted and analysed. To open a log file in Windows Editor click on the event log textbox in the **ClashManager** main window. ![](./media/ClashManager_image62.png)