...
Back to WinCan VX DDMS User Guide
Chapters
| Page Tree | ||||
|---|---|---|---|---|
|
Page Contents
| Table of Contents | ||||
|---|---|---|---|---|
|
Introduction
Most of the descriptions included in this manual up to this point have been designed to help the guys on site in the CCTV truck work as effectively as possible to maintain efficiency and profitability during the works.
This section will refer the results from a number of other key sections of this manual which would normally be tasks that are completed in the WinCan project before it gets to the site crews, so a smooth and organised process of preparing the data for site from the front end is essential.
It is essential the section Using WinCan VX with WinCan Map is considered in detail before working through this section.
Plotting Uncharted Assets
There will often be instances where you need to create objects (pipes and nodes) in WinCan VX that do not exist in the loaded data, either because there simply is no existing data on the system for the stretch of highway that you are working on or because you because there is data, but you have located uncharted assets.
Creating sections with inspection data in WinCan VX is no different than it is in any other inspection standard and does not need describing here, but how do we plot the manholes quickly and effectively in WinCan Map while on site and avoid the need for paper drawings?
The first thing to remember here for the CCTV operator is that uber-accuracy is not possible or even required at this point. Think of WinCan Map as your paper drawing, and all you need to do is mark it up electronically rather than on a drawing with a pencil.
At a point in the future, during office post processing, we will import the actual GIS coordinates from the GPS team and update the data with accuracy, but at the the stage of van inspection, all we need to do is get it roughly right and try to create a drainage network on screen that is joined up and looks roughly right as to what you can see on the ground. As the on-site team, your eyes on the ground are extremely valuable to the processing team.
This process works best with good quality background tile layers as described in Useful External Files, but can also work at a less effective level with Google-style overhead imagery.
So, imagine this scenario:
You are working in a lane 1 closure on the Southbound side of the motorway and you find a catchpit (CP1) in the verge and the pipe flows across the carriageway to another catchpit in the verge on the other side (CP2) and you complete an inspection of the pipe, like this:
...
A simple 50m inspection across the carriageway from one side.
Now, because of the traffic management controls, you have no access to the verge on the Northbound side so you cannot actually see the catchpit CP2, but you know it’s there because you have seen it on the camera at a distance of 50m.
Also notice that the DDMS reference value is blank because this is an uncharted asset, and also the same in the nodes (maybe).
We already have enough information to plot these catchpits and we know roughly where we are by studying the surrounding features and/or the Nokia tile overhead imagery available in WinCan Map. So, we can plot the catchpits very quickly and draw the pipe in WinCan Map and this is a mock-up of what we might draw on a piece of paper:
...
Drainage layout that we wish to reproduce with coordinates.
Remember, the van is beside catchpit CP1 on the Southbound side. The first step is to plot CP1 as best we can in WinCan Map using a ‘point and click’ on screen, so no GPS equipment needed.
We only need to plot the nodes here. Once the two catchpits CP1 and CP2 are plotted, the pipe will be drawn automatically. WinCan VX joins the dots for you.
...
Activating the un-plotted nodes list.
In the ‘Tools’ ribbon of WinCan Map, click on the ‘Draw’ button and a new panel will open on the right hand side. In this panel there are 3 tabs at the top, click on the ‘Manholes’ tab. This will always show you an alphabetical list of all the nodes in your WinCan project that have no coordinates, so they are uncharted. In this case of course, both of the catchpits are uncharted at this stage.
Select the node that you wish to plot first. In this case it will be CP1 because the van is right next to it right now so we have a good idea of where it is.
In the layers panel on the left hand side, select the ‘WinCan Manholes’ layer.
In the ‘Tools’ ribbon, click on ‘Draw Point’ from the ‘Edit’ panel and then just click once on the screen workspace where you think the chamber is. Remember, it just has to be ‘good enough’ and you do not need to worry about accuracy here.
You will be prompted to create a default node (for non-HADDMS work) or a HADDMS node. Be sure to click on the HADDMS option.
Fill in as much information as you can about this catchpit in the pop up screen that you see:
The node ID (CP1) will be already populated in the field at the top because this is the one that was highlighted in the list on the right before you started.
The X and Y coordinates of where you clicked on the screen will be in the required boxes. You don’t need to worry about these.
Notice that there is no Z value. This is because when we ‘Point & Click’ a node position, we can get extremely accurate X and Y coordinates but we can never get a Z coordinate. It doesn’t matter because remember, at some point in the future, all of the GIS data will be updated during post processing.
Be sure to fill in the ‘Type’ and ‘Node Type’ selection boxes correctly. These fields are very important to get right and they refer to the object types described in Understanding Object Types.
Fill in as much of the other fields as you can, but these are not so important from a data perspective. Notice that the ‘Depth’ field is the depth of the node and not necessarily the depth of the pipe as is the case in a catchpit, so be clear in your mind which depth value goes in the section header pipe depth fields and the node header node depth field.
See the result in the image below ‘First node plotted’ and notice that there is now only one remaining node in the list on the right hand side.
Now, repeat the process and plot the other catchpit CP2 on the other side of the motorway.
When we inspected the pipe in WinCan VX, we created an inspection that was 50m long, so we know roughly how long the pipe is. You can use the ‘Rule’ on the right hand side of the ‘Home’ tab in WinCan Map to measure out a line that is roughly 50m long to get an even better idea of where CP2 really is.
The result is displayed in the image below ‘All finished’. Notice:
There are no more nodes in the panel on the right side.
The pipe section is drawn for you with the inspection line and any observations that you made during the inspection.
This is good enough for the CCTV team to plot a pipe like this and no access was needed to the other side of the carriageway. We are simply using our best engineering judgement to plot these catchpits in the certain knowledge that at a point in the future, the GIS team will update the coordinates with real 3D values from their surveying equipment.
...
Plotting a node in Map.
...
First node plotted.
...
All finished.
...
Connecting a Lateral to a Main
Now, let’s extend the previous inspections so that it has some connection code in the inspection data at 25m (at 2 o’clock) and 32m (at 10 o’clock), and there are some gullies on each side of the central reserve plotted in the data, like this:
...
Extended observations.
...
Connection codes in the inspection and pre-plotted gullies on each carriageway.
...
This field allows us to enter the node ID of the point item that is upstream from the connection or junction, so in the first case of the junction at 2 o’clock it is most likely to be GY1000 and in the second case for the connection at 10 o’clock, it is likely to be GY2000.
From WinCan VX v14.0 this field is mandatory, so how might you handle a connection or junction that is capped off?
You must always consider connectivity, points and lines in DDMS modelling, so the solution is to create a phantom node with a stub lateral that has a nominal length of your choice (say 1m), because even though the connection or junction is capped off and is not being used, it is still there and could be used by a designer to connect a new gully to onto the existing network:
...
In this field you can:
Select a point item that already exists in the data - you must type in the first two characters of the node before the list self-populates.
Enter the node ID of a new point item that currently does not exist in the data.
...
The icon shows you that a lateral is tied in here and double clicking on this link will take you straight to that lateral in the other grid view, and there is also a button with an ‘up’ triangle arrow in the lateral grid view which will bring you bak back to the section that this lateral is linked to.
| Tip |
|---|
Advice - although this technique does not really appear to make a great difference to the data and the drainage network design, it’s power is that because the laterals and the section are now tied together, when we introduce the GIS data at a future point and in that data, the 2 gullies and the 2 catchpits now have new coordinates in 3 dimensions (so far, everything has had no Z value here), the shape geometry of the sections and laterals will be modified and the coordinates of the connector nodes will be replotted, so everything will stay tied together when the new positions are introduced. If you do not make the lateral links, then the lateral pipes will become detached from the section when the new positions are brought in and it becomes very (unnecessarily) time consuming to re-attach them all. |
There are some additional techniques for joining objects together using the snapping tools in WinCan Map, but these are more usually used by data processing teams, and will be described in Snapping Objects in WinCan Map.
Creating New Inspections of Existing Assets
Using the techniques described in Using WinCan VX with WinCan Map, we can quickly and effectively navigate between objects in WinCan VX and WinCan Map without the need for manual searching.
So there is an existing asset that you need to inspect which already exists in the data because it was imported from the HADDMS shapefile at the start of the round tripping process. First, ensure that the section or lateral (or node) is focussed and selected in the grid view.
Because the data was imported, there may or may not be observation codes already attached to this object, but of they were imported then they will be showing greyed out as read-only. They will also likely contain incorrect observation codes from the old WinCan v7 days, but this does not matter as is described in Creating Exports for Delivery.
Now, see the two buttons in the bottom bar of the grid view:
...
The ‘New Inspection’ buttons.
| Note |
|---|
Warning - the big mistake that people make here is working the same way that they did in WinCan v7 (and most likely in WinCan v8). In these versions of WinCan, when you wanted to create a second (or more) inspection of an asset, you simply created a new object with the same details as the first one in the grid view and then carried out a new inspection. !!! THIS MUST NOT HAPPEN IN WINCAN VX !!! See additional info in the next section. |
To create a new inspection of the object, you simply have to click on one of the two buttons shown in the image above. Hovering your mouse over the buttons will tell you what they do:
Create new inspection - this will present with you with a pop up where you can select;
a new blank inspection - you will be taken to the inspection header where you can fill in the required inspection details like your name etc,
a new downstream inspection, or
a new upstream inspection.
Create new inspection from other side - this will create a new inspection record in the opposite direction to the one that is currently selected in the user view (usually the most recent one unless you select to look at a different inspection record).
When you create a new inspection, the software will automatically add the inventory codes from the previous inspection. Theses are:
START and END codes at the zero and the full length of the asset.
All types of junction and connection codes with their clock positions reflected vertically if the inspection is in the opposite direction (so 2 o’clock becomes 10 o’clock).
All types of bending codes with their direction flipped around the vertical clock axis.
The logic here is that if the previous inspection stated that there was a junction at 1 o’clock at 12 m into a 45m section, then on the reverse inspection there must be a junction at 11 o’clock at 33m into the inspection.
Only inventory codes are copied, not defect codes. From here, you can start an inspection in the normal way.
If you subsequently need to abandon this inspection for any reason, then do not worry about the END code that has been automatically added for you. This will be removed when you complete the abandoned code.
...
...
...
The direction of the CCTV survey has no relationship with the section. The section (or lateral) is just a pipe in the ground.
The column on the right hand side of the grid view with the two magnifying glasses at the top shows you how many inspections there are of this object, and if the field is blank, then there is 1 or no inspections of the asset.
If you ignore all of the above advice and carry on regardless with creating duplicate assets, then when you enter the header data and click on the save button at the bottom, you will be prompted with this pop up warning:
...
Warning 1.
This is the first warning that you will receive and it does not take ant consideration for the inspection direction, so just because the last inspection was downstream and this one is upstream, this makes no difference at all to the fact that you have created a duplicate pipe with the same Supplier’s Reference and the same upstream and downstream nodes.
If you wish, you can click ‘Yes’ and you can proceed, but it is NOT recommended. You will now be prompted with this pop up message:
...
Warning 2.
This is your second chance to undo the problems that you are about to create in the data. You can again click on ‘Yes’ if you wish, but this is NOT RECOMMENDED even more strongly than the text just above.
If you continue without following the prescribed process for creating multiple inspections of assets, then you will see something like this in the section/lateral/node grid views - this is what we do not want to see in the data:
...
Poor inspection management with duplicate asset IDs.
See now that we have two pipes in the section grid with the same Supplier’s Reference MH1.1. The knock-on affect of this error is that this pipe will never be rendered in WinCan Map because Map does not know which object to draw and will cause all kinds of validation errors.
If we follow the process correctly and create 2 inspections of the asset, then the result in the grid view will look like this:
...
Good inspection management.
Notice that there is now only one asset record (because there is only one pipe in the ground) with a unique asset reference ID (MH1.1), and that in the column on the right there are 2 inspections of this asset.
Now we have created 2 (or more) inspections of an asset each with their own videos, observation codes and photos, we can review the inspections using the inspection list in the centre of the screen here:
...
Inspection selection.
When you click on the the button in the top left of the lower grid view area, you can see the details of all inspections of the currently selected asset. These include:
The Job Number (Catchment ID) that the inspection is attached to.
The inspection date.
The inspection time.
The inspection direction.
Whether the inspection was completed or abandoned.
Selecting an inspection in this list will take you to the details, video and observations for that inspection.
The default view in WinCan VX for all instances of multiple inspections is that the most recent inspection is always the one that is displayed on screen.
Data Validation
Marking Objects as ‘Inspected’
...
...