Author
Steve Peregrine BEng Hons, Senior Technical Manager
Project Merging Best Practice Guide
In order to get the best expected results when merging projects in WinCan VX, we must step away from the default merging strategy that is set in the application.
The default strategy is what is commonly known in database merging applications as a ‘Safe’ merge where table objects are not edited, and where the source table and the target table have an object with the same ID, then the merge creates a 2nd record, rather than updating the target record. The problem with this is that (particularly with manholes), you end up with a load of duplicate objects, which then goes on to create all sorts of problems with exports etc.
When we talk about merging, we use the terms ‘Source’ and ‘Target’ to refer to project databases. We always merge the Source project into the Target project, and WinCan VX allows multiple Source projects to be merged into a single Target project in one step.
Good project merging requires good source project data, and too all to often when the merged result is not as expected, it is to easy to blame the merging tool, but when we investigate deeper, we find that the source data was not good before the merge took place.
To improve the merge strategy and protect the target database in case of errors after merge, follow these steps:
Step | Description |
|---|---|
1. | Open the source project(s). |
2. | Launch the Duplicates Finder (in Tools -> Misc Tools) and search for duplicate sections and nodes in the option list in the bottom-left corner:  |
3. | The result will show you where you have duplicated asset IDs in your project. All duplicate instances should be considered carefully, and good engineering judgement made on how to handle each one based on the object ID’s data.
 |
4. | Run the WinCan VX Validation tool and resolve all errors on sections, laterals and nodes. |
5. | Repeat steps 2 – 4 for all the source projects and the target project. |
6. | Backup the target database files (Note – this will be automatically done in WinCan VX from version 8.0 onwards). To do this, simply copy and paste the database files inside the project DB folder to a new location (recommended is [Project Folder] -> Misc -> Backup). This is the save location of the auto-backup feature in v8.0 and higher.
|
7. | Open the Project Merger and go directly to the Wizard Settings from the File menu:  |
8. | In the Section tab, ensure the Section options are set to ‘Standard merging’:  |
9. | In the Node tab, ensure the Node options are set to ‘Standard merging’:  |
10. | In the Lateral tab, ensure the Lateral options are set to ‘Standard merging’:  |
11. | Click the green tick to proceed and go back to the main merging window. |
12. | Select the source project or projects (you can select more than one if you need to):
 |
13. | Click the ‘Next’ button. |
14. | Select the target project (it only needs to be highlighted):  |
15. | Click the ‘Next’ button and you will be presented with a summary of the options that you have selected for review. |
16. | Click the ‘Next’ button again to execute the merge process. |
17. | When the merge has finished, open the target project and repeat steps 2 – 4 again. There are likely to now be some data duplicates in your project, and these can confidently be resolved by clicking the ‘Resolve all’ button this time. |
18. | There are now likely to be multiple inspections of some assets (particularly nodes), where one or more of the inspections are empty with no tangible data attached. To clear out these unwanted inspections, select the ‘Delete empty inspections’ option (in Tools -> Misc Tools, only available in WinCan VX v9.0 and higher) and execute:  |
Note: Once these Wizard merge options have been set, they will remain as the default options until they are changed, or the software is updated.
There are some cases where slightly modifying these settings can give a better result and by rolling back the required databases you can try to merge again to see how the new merged result looks:
8. | In the Section tab, ensure the Section options are set to ‘Differential' merging:  |
9. | In the Node tab, ensure the Node options are set to ‘Differential' merging:  |
10. | In the Lateral tab, ensure the Lateral options are set to ‘Differential' merging:  |