Introduction

The Danish version of WinCan VX has got particular features implemented just for pipe inspection companies located in Denmark. So projects are able to follow the rules which are required by the Danish damage assessment standards DANDAS 2.5 and DANDAS 2.6.

After validation of a project based on the DANDAS standard(s) the data are also properly exported. Always mind that a project can contain different objects like section, lateral and manhole data. The Danish version is using the following terms for them:

• Sections = Ledning (Straekning)

• Laterals= Stik

• Manholes= Brönd

The following chapters summarize and describe the usage of these specific features in WinCanVX.

Data Entry

• The section field Straeknings-ID (section name) must follow the naming convention Upstream Manhole-Downstream Manhole-Suffix:

Open

• Select one of the naming conventions under Home > Settings to have the inspection field Rapport Nummer (INS_RapportNumber) properly filled out:

Open

When entering and saving new section data or refresh the project and re-open the input mask the naming conventions are automatically applied in the corresponding section and inspection fields:

• The lateral name must follow the predefined naming convention DanDas that the user must select under Home>Settings > PlugIns > AutoCreateConnections > DanDas:

When creating new laterals or refresh the project and re-open the input mask for laterals the naming conventions are automatically applied in the corresponding lateral section and inspection fields.

The lateral field Straeknings-ID (lateral name) must follow the naming convention DownstreamManhole-Distance-ClockPosition-UpstreamManhole-Distance-ClockPosition-Suffix as illustrated in the example above.

Recording videos and taking pictures

• A videoclip is recorded for each section as usual.

• A photo is going to be taken automatically depending on the damage code (OP-Code) the user entered. This is controlled by a formula in the background.

• The photo must show the corresponding observation text. The duration of the observation text display thus should be controlled accordingly in the background.

• OP-Codes referring to material changes will automatically send the new pipe material to the project bar text during recording.

Data Output

Hit the command Print > Printing Panel and select the report layout SEC-Inspection_WinCan in the corresponding list box.

This is going to print the default WinCan inspection report (with pipeline graph) that is also used in other countries:

Select the report layout SEC_Inspection or SEC_Inspection_DANDAS in the corresponding list box, if you need to print the inspection report in the DANDAS format:

The DANDAS inspection report (table report in landscape format) must look as illustrated below:

Summary reports

Besides the inspection report pages Danish inspection companies have to handout two specific types of summary reports. This chapter describes how the operator has to proceed to print these reports in WinCan VX:

Defect summary report (Analyseskema):

Select the report type Project Summary and activate the option Defect Summary:

This table report summarizes all defects (represented by their OP-Code) which have been detected inside the inspected sections within a project:

Job summary report (Produktionsskema)

This table report summarizes all projects/jobs done by a specific operator during one month.

This report has to take into account a group of projects and thus must be created via the separate module WinCan Meta DB the user can launch under START > WinCanVX > WinCan Meta DB.

Next proceed as follows to create the job summary report:

• Open the index file MetaDB.db3 located in the subfolder C:\Users\Public\Documents\CDLab\Common\Resources\sqlCE:

• Make sure this index file is used per default when opening the module WinCan Meta DB:

• Run the command Edit > Index editor and make sure the following database fields are indexed and visible for the Danish version:

SECTION.OBJ_Key

SECTION.OBJ_Length

SECINSP.INS_VideoRef

OPERATOR.OP_Name1

SECINSP.INS_StartDate

SECINSP.INS_InspectedLength

Besides the fields listed above you may also add additional (optional) fields like OBJ_Type, OBJ_City, OBJ_Street etc.

• Confirm all changes and run the command Tools > Print Operator Summary Report:

• Enter the period of time (month) and the name of the operator whose job summary you want to print:

• Save the PDF-file into a specific sub-folder on your local hard drive:

Make sure you have previously registered the projects in WinCanVX. The module WinCan Meta DB then is able to show the updated field contents of the corresponding projects. You may choose between two possibilities of project registration.

Activate the option Home > Settings > Presets > Update Meta DB tool when project closes to register each project automatically in the Meta DB:

You may also hit the command Home > Update Meta Database to register each project individually in the Meta DB.

DanDas Export

Data recorded with the Danish standard DANDAS 2.5 or DANDAS 2.6 must be exported in WinCan VX and handed out to the local water authorities or engineer offices that have got their own software to re-import these data.

Hit the command button Data Exchange > Export and select the corresponding export standard in the dialogue box below:

Click on the button NEXT and confirm the settings below:

Click on the button NEXT and make sure the media files are exported (1) and properly renamed (2):

Click on the button NEXT and wait until the data export has been finished:

Open the project subfolder \Misc\Exchange and check the structure of the exported data that must look as illustrated below:

Especially mind the following items:

• The sub-folders Picture and Video contain all media files which are referenced in the project database.

• The data for all inspected objects per category (i.e. Leding, Stik, Broend) are summarized in 3 separate XML files accordingly (1).

• The data for each single object (Ledning (section), Stik (lateral), Broend (manhole/connection point)) are exported into separate XML files (2).