Please refer to MAGNET Explorer user guide
to get the feeling of main user interface elements in Explorer
. In this tutorial we try to keep the workflow as simple as possible and focus only on those tools that we currently use. To start creating a new project, you can click on New
button or simply go to Explore
Open the project: 01_ClashDetection/Combined-04_Start.vmpx (or the project file that you saved at the end of 02 Combined VDC model, do not use/open model package this time)
Before you start clash analysis, you can check your model visually, turning it upside-down, showing/hiding various sub-models and by that way getting a feeling what you have, and what you may be missing. Also you may notice some problems already by a simple navigation workflow.
An example image, while looking the model from the proposed bridge location upside-down. It can be seen that proposed pipeline is colliding with bridge support.
Saving a model state
Before we start a clash detection analysis, let's save our current model state. This workflow can be used for any model state/viewpoint saving for later reuse. Check that in your Explorer palette you see group view and click on the eye symbol to hide the following groups:
You can save this state by accessing Topics list tools. It should be opened by default, but if you do not see a separate Topics list palette that is down below your model viewport, go to Explore tab > Topics List.
You should now see a separate palette below your model viewport.
In here, after picking a new viewing angle and also showing/hiding various groups or sub-groups, you can click on binoculars button and save your viewpoint with valid show/hide settings. Click on it and you can rename it directly from the default name location.
Give a new name as: Proposed Design.
If you now do a simple test and re-navigate your model to a different viewing angle and also hide some more groups/sub-groups, then a simple click on button (on your Proposed Design button) you can easily get back to the saved viewpoint/view state.
Note: If you do changes in your model content, or want to re-save the same topic from a different angle, you can simply do a right click on that specific topic preview image and select appropriate command.
Topics are also used during collaboration stages. Where you add comments with your generated topic, or answer to somebody's topics/comments. We look those workflows in later sections.
Please save your project before moving on. The previous step has been saved as: Combined-05_Topics.vmpx
Clash detection analysis
Clash detection tools can be accessed from the ribbon tab: Analyze > Clash Detection.
Note: If you see a blue shadow below Clash Detection tool, it means that this palette is already open on your user interface. Typically, when you click on Clash Detection, the new palette will appear on the left hand side (where your Explorer palette is located as well).
To use automated clash detection tools, you start by selecting groups in where you want to check, if those collide. You have First Selection and Second Selection where you assign one or more groups. To add a group into your First Selection, click on a green plus symbol. The following dialog opens:
Select: Design/Structure/E1R2 Bridge (its our proposed bridge group). Click OK.
To add a group into your Second Selection, click on a green plus symbol. The following dialog opens:
Select: Design/Utilities/Road drainage (its our road drainage group under VT7 road). Click OK.
Because we want to make a quick clash detection analysis, just hit Calculate.
Clash detection analysis will be carried out and results are shown in the Topics list area as a separate tab, called Clash Results.
You can see, that in current the analysis, only one clash was found. Do a double-click on that clash row and you will be navigated to the location of the clash.
The clash can not be followed easily, therefore click on Show only selected groups to hide away everything else that is not part of a clash group.
Now the area of the clash can be more easily followed. Due to a different project partners, who designed a bridge and who did the new pipeline, the collision was not noticed during their own design work. Maybe it was due to wrong coordination work, or missed conversation - in any case, this could be a major issue at construction site, when it will be discovered during the construction. Because sewer pipelines needs some slopes, it is not so easy to rearrange the piping during the construction. This may raise the project cost. If such analysis has been made during the design work, the fix could be more easily established.
You are free to navigate you model view from different angles. Once finished you can click on a button Create topic and the new viewpoint will be saved under Topics list, from where you can start collaboration (we look those possibilities later).
Go to Topics list tab, and rename you clash as: Bridge vs DRN
Please save your project before moving on. The previous step has been saved as: Combined-06_ClashDetection.vmpx
Value based clash detection analysis
In previous example it was quite an easy task to find one particular clash. But usually we do not check clashes between two groups, but include other groups as well. Also, a typical infrastructure project has many groups to check and it will be time consuming to check those one-by-one. Quite often we are more interested about those clashes that may affect project cost and easy fix on the construction site is not available or causing costly request for information (RFI). Therefore, in Explorer you prioritize some groups during the whole clash detection analysis, or include an average repair cost if the clash is found between those particular objects.
Please continue from the previous exercise, or open: Combined-06_ClashDetection.vmpx
Please add: Design/Utilities.
Note: Pay attention while selecting groups. If you select a main group, all sub-groups will be automatically added. No need to select those. Therefore, if you select Design/Utilies, it actually includes the previously selected Road drainage as well. So, in general you do not need to have that Road drainage at all, and can delete it from the list. But just to let you know that you can select multiple groups if you want to.
Click on Group properties button.
Dialog Group Priority opens. In here you see two columns. In Value column you can add an additionl value parameter by which you can easily sort your most valuable clashes before the others (value based clash detection). Tolerance column is used when you want to carry out so called soft clash detection studies, in where you need ensure that some objects do have enough clearance in between. Let's assume that our road drainage network has a Value = 1000. Close the dialog by hitting OK.
Run again your clash analysis. Click on Calculate button. You will see that you have more clashes. It is much easier to start from those clashes that may affect the project cost tremendously. Therefore you can click on Value column header, and sort your results based on the value (note: values are calculated based on settings in Group Priority dialog).
You can also sort your results based on other column headers, like Size, Tolerance, Risk value. Size gives an indication of how large the clash is, Tolerance is calculated based on safe clearance and Risk value is calculated as Value * Tolerance%.
Please save your project. The previous step has been saved as: Combined-07_ValueBasedClashDetection.vmpx
You can continue by evaluating other clash results, and creating topics for those as well. You can create multiple topics if you first hold CTRL or SHIFT key and then select those clash rows that interests you. After that click on Create topic. Each clash result generates its own topic. Default name includes the clash ID value. Clash results can be marked based on its Resolution. If you rerun clash analysis, you also see additional information under Status column.
You can also perform a clash analysis between existing utilities and proposed utilities.