1. Technical Background of UWWTD Software
Johann Weigl
Katharina Lenz
Michael Nagy

2. UWWTP Requirements
Software tool supporting data collection according to Directive UWWTD 91/271/EC
Software supports manual data input by a MS
Software supports semi automatic data input (text file import functions)
Software supports mixed mode data input (file import and manual input)
Multiple reporting periods
Single user PC-based software
GUI: uniform & harmonised layout, structured according to business case
ensure high quality of data in DB

3. Software environment
MS Access 2003 as relational database management system
ODBC-API (open database connectivity - application program interface) is used to access the database from the application
MS Visual Studio 2005 as integrated software development platform with programming languages Visual Basic, C/C++, J# – development of standalone applications, web applications & services running on platforms supporting .Net framework

4. System requirements To run the application you need:
PC with Win-XP SP2 operating system
(alternatively Windows 2000)
MS .Net Framework (installed by installation tool)
Crystal Reports for .Net (installed by installation tool)
Free disk space of 150 MB for the software to be installed
Internet access

5. Test Environment Software has been tested on
PC: Pentium 4, 3 GHz, 512 MB RAM
WinXP – SP2 (DE)
Alternatively WinXP – SP2 (EN)
Windows Vista: According to documentation, the application should run on Vista as well

6. Core Components Installation tool UWWTD2007 software
Import and export tools

7. Installation tool 1
Is provided as zipped collection of files comprising:
Setup.exe
UWWTD2007.MSI
Data Base file UWWTD2007.mdb
MS .Net files (dotnetfx.exe, instmsia.exe, langpack.exe, WindowsInstalle.exe)
Crystal Reports Files (CRRedist2005_x86.msi, CRRedist2005_x86_en.msi)

8. Installation tool 2
Creates the following subfolders in the application‘s root directory „..\UWWTD2007“:
Data_Application
Data_Export
Data_Import
Documents
GIS

9. Installation tool 3
Installs the following components in the application‘s root directory:
Application UWWTD2007.exe in root (2MB)
Data Base UWWTD2007.mdb in subdirectory Data_Application
MS .Net Framework 2.0 (100MB)
Crystal Reports for .Net Framework 2.0 (35MB)

10. Data Base after installation
The installed data base contains the following data sets
List of Member States
List of Big Cities
NUTS (list of level 3 regions)
Other LOVs (Branch of Industry, etc)

11. Deinstallation
To delete installed components the following steps are necessary
Deinstall Application UWWTD2007 in the control panel (under software)
Deinstall Crystal reports for .Net Framework 2.0 (control panel)
Deinstall Microsoft .Net Framework 2.0 (control panel)
Deinstallation removes all folders except import/export folders if there are files

12. UWWTD2007 Context Import Files UWWTD2007 Software Export Files
Templates
Member State
Software
Office Software
Manually generated files (optional)
Machine generated files (optional)
Import Files
Validated
Data
UWWTD2007
Software
Export Files

13. UWWTD2007 MS identification (Reporter, Report Period, Contact)
Data import
Prepare import files
Start import
Evaluate error log
Data input
Data modification
Data export
Start export
Check exported files
Check error log
Validation checks upon import and export

14. UWWTD Data Model BigCity Reporter Agglomeration UwwtpAgglo NUTS
ReportPeriod
UWWTP
Contact
DischargePoint
MSLevel
LOV
Industries
ReceivingArea

15. Import Tool Lets user define the import directory
Searches for import files user in defined directory
Processes content file by file in well defined order
Processes the individual data entries in each file line by line
Writes correct data sets into DB
Entry into error log for incorrect data sets (wrong data type, missing obligatory field, missing links)
Evaluation Report

16. Data Import Checks and Validation
Consistency of reporter and report ID - Import terminated if files/info missing or inconsistent
Master data check (minimum requirements for import are ID and name) – if an ID or name is missing, the record will not be imported; if an obligatory field according to DD is missing, the record will be imported and there will be an entry into the error log;
Syntax checks (data type, field length) according to Data Dictionary – a field with a wrong data type will not be imported, strings with length exccedence will be truncated
Reference Checks
For every Agglo-UWWTP link there must be a valid agglomeration and UWWTP,
every agglomeration must be linked to a UWWTP,
every UWWTP to a DP,
every catchment to a sensitive area

17. Error log structure ErrorID Error code Table Record Count DB Field
Value
Comment
Date

18. Export Tool Validation (check of missing links)
Processes content table by table in well defined order
Processes the individual data entries line by line
Stores export files user defined export directory
Entry into error log for incorrect data sets (wrong data type, missing obligatory field, missing links)
Valuation Report

19. Data Export Checks and Validation
Upon error, data will still be exported and there will be an entry into the error log
Master data check
Syntax checks according to Data Dictionary
Reference Checks
Validation Timestamp in file ReportPeriod