Back to Inspection Merging
...
| Page Tree | ||||
|---|---|---|---|---|
|
...
Inspection Merging in WinCan VX
Running the inspection merger with these default rules could not be easier and only takes three mouse clicks. In the shortest possible description, all you have to do is:
...
Figure 13: Quick and easy inspection merging with default settings.
...
The results may look like Figure 24:
...
Figure 24: Inspection combining results.
...
Let’s look at the options in the inspection merger panel more closely in Figure 35:
...
Figure 35: The control panel.
As stated already, the pipes in the list will only be those that are eligible for combining based on the golden rule of at least one abandoned inspection from each end. Each line of data in the box represents one pipe with two selected inspections, and the most recent selected inspections have been selected automatically.
...
The first one ‘Show only most recent inspections’ is on by default. Go back to the scenario No. 6 earlier in this document. In a case like this, there are two possible combining situations – we could combine inspection 1 and 3, or 2 and 3. As described already, the default will be 2 and 3 because 2 was done after 1. Unchecking this user option will show a 2nd line in the data grid and you will be able to select which one of the 2 options you wish to combine.
The second checkbox ‘Auto-calculate new length’ is off by default. When this option is selected, the total pipe length is not considered, and the 2 inspections are just glued together back-to-back, which then modifies the total length of the pipe. This option is not recommended to be selected, but some central European countries like Germany and Austria prefer the combined inspection to be represented this way, even if it make the pipe much longer or much shorter than it actually is, and there may be observation code of the same defect at different positions along the pipe.
The third option ‘Show modified inspections (changed since previous merge)’ is off by default. There may be a situation where the user has created combined inspections, but then has subsequently made edits on one or both of the inspections that were used to create the combined inspections. Checking this box will list objects that are eligible to be re-combined again following edits of the source inspections.
The last option ‘Mark abandoned inspections as deleted’ is off by default. When active, the 2 inspections that are used to make the combined inspection will be deleted after the merge. This may be useful in some scenarios but the overall advice is not to select it, because it is a good idea for the contractor to keep a full record of every inspection that they actually did on site, and the combined inspection is not one of these, it is a ‘calculated’ inspection record derived by the software application.
...