Back to WinCan VX DDMS User Guide
...
| Table of Contents | ||||
|---|---|---|---|---|
|
...
Export Hierarchy
There are a number of things to consider that all affect the results that are output from WinCan VX during the export process, and they are almost all handled automatically in the background during the data exchange routine without any user options available to the user.
Theses are driven by:
The difference in core data structures between HADDMS and WinCan where HADDMS stores all of its asset and inspection data in a single file (i.e. continuous, point and region etc) but WinCan VX (unlike WinCan v7) stores these very different types of data in different tables in its database.
The round tripping process where any assets imported into WinCan Vx at the start of the round tripping process that are not inspected are simply returned back out of the database and back into HADDMS via the shapefiles without any modification.
So, if we just import some HADDMS shapefiles and then export them back out again, there will be no changes in the data.
If we import 1,000 sections in a catchment and then only inspect 40 of them on a job, then we will export the new data for the 40 inspected objects and the remaining 960 sections will just be exported back out again without edit.
This is why it is crucial that sections laterals and nodes that were imported at the start of the process are not deleted from the WinCan VX project, and also why good use of the ‘Inspection Status’ field is crucial to managing the data efficiently.
In the HADDMS data files, there is only ever one combined inspection and asset data record of each object, but of course, WinCan VX has the concept of ‘multiple inspections’ and ‘combined inspections’, so how do we decide which inspection to export when there are several to chose from? This is where the Export Hierarchy comes into play, and the selected export order of the one inspection record to be exported (applies to all object types) is like this:
Combined inspection - if a combined inspection record exists on an object then it is exported and no other inspection data is exported for the current asset.
A complete inspection from end to end - this might not be the most recent inspection because maybe there was am abandoned inspection carried out after the complete one, but this does not matter under HADDMS rules - a complete inspection trumps an abandoned inspection regardless of date and time.
An abandoned inspection - the most recent abandoned inspection will be exported. Of course if there was at least one abandoned inspection from each end then there should be a combined inspection, so we are back up this tree to option 1.
The original imported data.
So, at the end of this export process, every asset has an inspection record exported into the data regardless of whether it was inspected by the contractor during this package of work or not.
...
Creating HADDMS Exports
...
Understanding the Outputs
...