Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 37 Next »

Back to WinCan VX DDMS User Guide

Chapters

Change Log

This page contains information regarding data entry fixes and updates between WinCan VX release versions. These do not include bug fixes or feature developments, only fixes to captions and list items as required to either remove conflicting information or as a result of updates to the standard.

These types of changes are most often driven either by a published data format update from Mott MacDonald or from an understanding that something is ambiguous or unclear in our project template.

WinCan VX v9.0

  • Connector Node list item changed to Modelling Node in the ‘Asset Style’ drop down list of the node header.

    • In previous versions, we had the list item ‘Connector Node’ in both the ‘Asset Style’ drop down list and the ‘Node Type’ drop down list. The differences between these are described in the chapter Understanding Object Types, but essentially the first one is a WinCan object type and the second one is a HADDMS object type.

    • There is no change to any data formats, database keys or validation rules with this edit. The change is cosmetic only and removes the confusion where the list item ‘Connector Node’ could appear in both fields in previous versions.

  • Highways England list option added to ‘Node Ownership’ and ‘Land Ownership’ field list options.

    • In line with the recently published latest version of the HADDMS Drainage Data Formats Issue2 file as described on the landing page under the Documentation section at WinCan VX DDMS User Guide, this new list item is added.

    • The database key behind it for GIS data collection purposes is HE.

    • Validation rules are updated to accept this value HE.

  • Instrumented Gully added to the ‘Node Type’ list options.

    • In line with the recently published latest version of the HADDMS Drainage Data Formats Issue2 file as described on the landing page under the Documentation section at WinCan VX DDMS User Guide, this new point item is added.

    • The database key for this is IG.

    • An ‘Instrumented Gully’ is any gully that has instrumentation device(s) in it. Some gullies have devices inside that can monitor the amount of silt and report the data back to the client via the web. This type of gully is an ‘Instrumented Gully’ rather than just a ‘Gully’.

    • Validation rules are updated to accept this value IG.

  • Vortex Separator added to the ‘Node Type’ list options.

    • In line with the recently published latest version of the HADDMS Drainage Data Formats Issue2 file as described on the landing page under the Documentation section at WinCan VX DDMS User Guide, this new point item is added.

    • The database key for this is VS.

    • There is still a Yes/No field also for ‘Vortex Separator’, just like there always was. This has not been removed in the new data formats document. The difference now is that a Vortex Separator is now a point item in its own right, but it can also still be a sub-element of a larger point item, so it is still possible to have a manhole with a vortex separator inside it.

    • Validation rules are updated to accept this value VS.

WinCan VX v10.0

  • Highways Agency list option removed from ‘Node Ownership’ and ‘Land Ownership’ field list options.

    • In line with the recently published latest version of the HADDMS Drainage Data Formats Issue2 file as described on the landing page under the Documentation section at WinCan VX DDMS User Guide, this list item is no longer valid.

    • Validation rules are modified to reject this value HA.

    • Node templates are modified to deliver the new value to VX from Map.

  • All ‘Historical Data’ list options are removed from the ‘Strategic Importance’ list options.

    • In line with the recently published latest version of the HADDMS Drainage Data Formats Issue2 file as described on the landing page under the Documentation section at WinCan VX DDMS User Guide, these list items are no longer valid.

    • Validation rules are modified to reject these values A, B, C, Z.

  • Node part list items extended to use all available parts in WinCan VX.

    • This makes no difference to the data exchange with the HADDMS shapefiles, because the shapefiles only have data fields for 1 cover, 1 shaft and 1 chamber. This allows users to make detailed manhole cards for client printing and extends the functionality with CleverScan.

    • New parts added - Frame, Seal, Bearing, Insert, Valve, Trap and Other.

    • Note - all measurement fields for all node parts are in metres, not mm. This is inline with the existing and published fields for the HADDMS shapefiles for consistency.

  • Node inspection printing report extended to print multiple node parts of the same part type.

    • Also extended to print the new node parts described above.

  • In the Node Header list for ‘Node Type’, each list item has had [point] or [region] added as a suffix.

    • This helps the user to identify which shapefile the node exchanges with, because all point items and region items from the HADDMS shapefiles are stored in the Node area of WinCan VX.

    • There are no changes to any underlying data, exchanges or validation rules.

    • All the region items are at the bottom of the list.

  • Shapefile data consolidation tools added to WinCan Map.

WinCan VX v10.2

  • Job Checker tool fixed and working correctly.

    • The Job checker tool was first published in VX v10.0 but had some bugs so is not recommended for use in v10.0 or v10.1.

WinCan VX v11.0

  • Import/Export mapping editor tool improvements.

  • Simplification of the continuous asset dimension fields.

    • The asset dimension fields have been reduced from 5 to 3 and now have a direct one-to-one mapping with the relevent shapefile fields.

    • Before v11.0:

    • v11.0 onwards:

    • There are a number of rules in HADDMS concerning when each of these fields is valid and when they are not based on other criteria in the data including the asset type. Previously, VX was manipulating these values automatically in the background and the result was that sometimes after export, the data was in the wrong fields in the shapefile.

    • This background manipulation has been removed and the transfer of data is now clear and direct between the WinCan database fields and the shapefile fields.

    • The contractor should understand from the HADDMS documentation when and how to use these fields appropriately.

    • The WinCan VX validation files and import mapping files have been modified to match this change.

    • Please use the tip text in WinCan VX that appears when you hover over the field caption.

    • See also additional information here - The Section/Lateral Header - Service & Support - Confluence (atlassian.net)

  • New features added to the ‘Import from GIS’ tool as described https://cdlabdev.atlassian.net/wiki/spaces/FAQ/pages/1201569843/WinCan+VX+Project+Setup#Update-in-WinCan-VX-v11.0

  • Imported reference fields added to the node and section headers for error checking.

  • PLR Suffix field removed.

    • The PLR Suffix concept is not relevent in HADDMS data and never has been. It is a WRC inspection standard that has no place in HADDMS data and causes problems with data management, so it hasbeen removed. It is now the responsibility of the operator to ensure that they have specified a unique Supplier’s Reference for each asset at all times, and the value will not be edited by the software.

  • Node Header field name changes to simplify field links between HADDMS shapefiles and WinCan and minor changes made to import and export to ensure good mapping of cover level values.

  • Not related to WinCan VX, but changes made in this manual:

    • New ‘Support’ section added to the front cover page of this manual.

    • References to Highways England changed and/or modified to National Highways throughout this manual.

    • New chapter Connectivity & Asset Uses added regarding connectivity and asset types.

Back to the top.

  • No labels