# CODE_LIST_DO_NOT_MODIFY

lu_ShortDescription:
more stringent nitrogen removal and desinfection


lu_ShortDescription:
more stringent nitrogen and phosphorus removal


lu_ShortDescription:
more stringent nitrogen and phosphorus removal and desinfection


lu_ShortDescription:
any other more stringent treatment (please provide an explantion in the flatpComments field)


lu_ShortDescription:
more stringent phosphorus removal and desinfection


# DEFINITIONS_DATASET_DO_NOT_MODIFY

ds_Name:
Urban Waste Water Treatment Directive reporting under Article 17

ds_Definition:
Data reported by countries under the  UWWT Directive - Article 17 reporting obligation.

ds_Methodology:
The data requested through the Reportnet process should be derived from existing national and/or regional information systems within each Member State and the information and data needed to assess the compliance status for agglomerations and treatment plants under Article 15 reporting.

Member States are asked to provide the information on the status and on the forecasts for implementation of the UWWTD, in particular:

   1.   information on individual agglomerations and urban waste water treatment plants which have to become compliant, and
   2.   aggregated socio-economic information at national level 

No information will be requested for agglomerations or treatment plants which are considered compliant and for which there are no reasons to conclude that this situation would change within the next two years. 
If the reference year used for the article 17 reporting is more recent that this used for article 15 reporting, it could be possible to have new not compliant situations because of a better knowledge of the situation. In the same situation, it is also possible to have less not compliant agglomerations than those identified under article 15 because the work has been achieved between the two reference years. 
If no compliance assessment is yet possible (because the deadline in the Accession Treaties is not yet expired), detailed information showing the status of implementation already achieved or expected should be provided.
Aggregated socio-economic information at national level is requested to all MS, including those that reach very high compliance levels. This information will allow assessing the approach applied by Member States to address the identified problems and the actions needed to keep their achievements (e.g. maintenance/renewal etc). 

Reporting under the UWWTD will be carried out by uploading data into WISE via ReportNet (the European Environment Agency's electronic infrastructure for data collection). Member States are asked to upload their data UWWTD Art. 17 data in XML files following the reporting templates into a Central Data Repository (CDR). Additional documents and reports can be uploaded next to data files as well. For this reporting exercise, the European Environment Agency (EEA) provided the access rights to the reporters nominated by the Member States to upload the report in WISE. 

Instructions on “How to use Reportnet for reporting under the Urban Waste Water treatment Directive-National Implementation programme” for the submission of the reports from the Member States in pursuance of UWWTD article 17 are available at http://cdr.eionet.europa.eu/help/UWWTD  (under “Dataflow specific instructions, sub-section Urban Waste Water Treatment Directive – National Implementation Programme-2017 Reporting“). All technical supporting documents are also available via this link.

A technical help desk on the reporting exercise will be provided by the European Topic Centre on Inland, Coastal and Marine Waters (ETC/ICM), and will be available for six months after the launch of the reporting exercise. The helpdesk can be contacted via e-mail on uwwtd.helpdesk@eionet.europa.eu.


# DEFINITIONS_ELEMENTS_DO_NOT_MODIFY

e_Methodology:
This value is required.

Use the format YYYY-MM-DD.


e_Definition:
Specifying the end date of the period for which the data was reported.


e_Definition:
ID of the Agglomeration, as specified by country.

e_Methodology:
This value is required when there is a not compliant situation under the Article 15 reporting.

aggCode must be unique in the table.

First 2 characters must be the 2-alpha character ISO country code (use 'EL' for Greece and 'UK' for the United Kingdom).
Do not use characters with accents and other diacritical marks (national characters). Do not use spaces or other spatial characters. The hyphen '-' and the underscore '_' characters are allowed.
Each aggCode must be reported also in the UWWTD Article 15 dataset.

It is not possible to have the duplication of the same ID code. All the works concerning an agglomeration have to be aggregated under the same ID code.


e_Definition:
Status of the agglomeration at the reference reporting year (Not compliant/Pending deadlines)

e_Methodology:
This value is required.

If the agglomeration is reported in the table, the status is not compliant. The not compliant situations cover all not compliant agglomerations at the chosen reference year even if they are not in any specific infringement procedure. It is a way for MS and EU to better communicate at national and EU level about the identified not compliant situations. See also chapter 2.2 of the Article 17 guidance  document about compliance.

It is also possible for a Member State to have a Compliant situation in the list if there is a need to follow the renovation of this targeted collecting system, the extension of it or the works on collecting systems which are going to replace IAS.

If the agglomeration is under a pending deadline and if doesn't meet the requirements of the Directive yet it has to reported as "PD" - pending deadlines.


e_Methodology:
This value is required for all non-compliant agglomerations. 

If an implementation deadline is pending and the reason is unknown, fill in: not relevant.
 
Examples of answers: 
- absence of collection and IAS
- discharge of untreated wastewater in the collecting system or treatment plant
- excess of storm overflows in the collecting system.


e_Definition:
Measure(s) foreseen to reach compliance with Article 3 (collecting systems and IAS)

e_Methodology:
This value is required.

Examples of answers: 
- building of a collecting system
- renewal of the collecting system
- building of a storage system


e_Definition:
Date or expected date for completion of preparatory measures for the  collecting system or IAS (planning, design, procurement, consents as required at MS level, etc).

e_Methodology:
This value is required.

If there is no clear information regarding the project the cell has to be filled with a date regarding the minimum time needed to achieve the objective. The date should not be before 2000 or after 2030.

Use the format YYYY-MM-DD.


e_Definition:
Start date or expected start date for works on the collecting systems or IAS.

e_Methodology:
This value is required.

If unknown, the date corresponding to the minimum time needed to achieve the objective should be reported. The date should not be before 2000 or after 2030.

Use the format YYYY-MM-DD.


e_Definition:
Expected date of completion of the collecting system or IAS works.

e_Methodology:
This value is required.

If unknown, the date corresponding to the minimum time needed to achieve the objective should be reported The date should not be before 2000 or after 2030.

Use the format YYYY-MM-DD.


e_Definition:
Forecast investment cost for the collecting system or IAS (as in the national plan)

e_Methodology:
This value is required.

If unknown, estimated value should be provided.

Unit: million €


e_Definition:
Name of EU fund planned to be used to complete the collecting system or IAS (if any).

e_Methodology:
If known at the reference date.
European Regional Development Fund (ERDF), Cohesion fund (CF), European Investment Bank (EIB) Loan, European Bank for reconstruction and Development (EBRD) loan, Environmental Protection and Energy Efficiency Fund (EPEEF), European Social Fund (ESF),...


e_Definition:
Amount of (planned)  EU funds likely to be requested to complete the collecting system or IAS (if any).

e_Methodology:
If known at the reference date. 
The amount should not be higher than the forecast investment cost. 

Unit: million €


e_Definition:
Any relevant comment on collecting system or IAS.

e_Methodology:
Examples: 
- problems of implementation of remedial measures
- change of the project
- explanation of the delay of the project
- calculation of the cost


e_Definition:
Expected generated load [p.e.] of the agglomeration at the expected date of compliance.


e_Definition:
Expected rate of the generated load [%] of agglomeration  collected through collecting systems at the expected date of compliance


e_Definition:
Expected rate of the generated load [%] of the agglomeration addressed through IAS at the expected date of compliance.


e_Definition:
Amount of funds to be allocated likely to complete the collecting system or IAS (if any).


e_Definition:
Name of the entity planned to provide fund to complete the collecting system or IAS (if any).


e_Definition:
Amount of loan likely to be granted to complete the collecting system or IAS (if any).


e_Definition:
Name of the entity planned to give loan to complete the collecting system or IAS (if any).


e_Definition:
ID of wastewater treatment plant / collecting system without treatment.

e_Methodology:
This value is required when there is a not compliant situation under the Article 15 reporting.

uwwCode must be unique in the table.

First 2 characters must be the 2-alpha character ISO country code (use 'EL' for Greece and 'UK' for the United Kingdom).
Do not use characters with accents and other diacritical marks (national characters). Do not use spaces or other spatial characters. The hyphen '-' and the underscore '_' characters are allowed.
Each uwwCode must be reported also in the UWWTD Article 15 dataset.

It is not possible to have the duplication of the same ID code. All the works concerning a treatment plant have to be aggregated under the same ID code.


e_Definition:
Name of wastewater treatment plant / collecting system without treatment


e_Definition:
Status of the UWWTP at the reference reporting year (Not compliant/Pending deadlines)

e_Methodology:
This value is required.

By default, if the UWWTP is reported in this table, the status is not compliant (NC). The not compliant situations cover all not compliant UWWTPs at the chosen reference year even if they are not in any specific infringement procedure. It is a way for MS and EU to better communicate at national and EU level about the identified not compliant situations.

It is also possible for a Member State to have a Compliant situation in the list if there is a need to follow the renovation of this targeted treatment plant or the work of a new treatment plant which is going to replace it.

If the UWWTP is under a pending deadline and it doesn't meet the requirements of the Directive yet, it has to be report as "PD" - pending deadlines.


e_Definition:
Identified reason(s) for non compliance of a waste water treatment plant.

e_Methodology:
This value is required.

If under pending deadlines and the reason is unknown, fill in “not relevant".

Examples of answers: 
- discharge of untreated urban waste water from the UWWTP
- absence of UWWTP
- excess of storm overflows in the UWWTP
- absence of secondary/tertiary treatment
- absence of nitrogen/phosphorus removal
- absence of disinfection
- improper design/obsolescence/new requirements/ increase of the load/bad operation


e_Definition:
Measure(s) to reach the compliance needed for UWWTP.

e_Methodology:
This value is required.

Examples of answers: building a new treatment plant/secondary treatment/more stringent treatment, building of a storm storage reservoir in the UWWTP, renewal of the collecting system/treatment plant, extension of the treatment plant, implementation of article 5.4 of the directive.


e_Definition:
Load [p.e.] entering the UWWTP at the expected date of compliance (as planned).

e_Methodology:
This value is required.

Estimation of the load entering the treatment plant at the expected date of compliance of the agglomeration. This load is calculated as regard the requirement of article 4.4 (maximum average weekly load).


e_Definition:
Organic design capacity UWWTP [p.e.] (as planned).

e_Methodology:
This value is required.

If not known, enter estimation regarding the size of the agglomeration served by the UWWTP.


e_Methodology:
This value is required.

Fill in the highest treatment type. The highest (planned) type of treatment should be reported, i.e. if a treatment plant is designed to be equipped with primary, secondary and N and P removal treatment types, only N and P treatment type is reported.


e_Definition:
Date or expected date of completion of preparatory measures (planning, design, etc.)


e_Definition:
Date or expected start date of connstruction works


e_Definition:
Date or expected date of completion of works


e_Definition:
Expected date of compliance (12 months of compliant samples).

e_Methodology:
This value is required.

Usually the 12 months after the former deadline. Can be automatically generated by adding 12 months to the value of "flatpExpecDateCompletion" parameter.

Use the format YYYY-MM-DD.


e_Definition:
Forecast cost investment needed for the UWWTP (as in the national plan).

e_Methodology:
This value is required.

Estimated values have to be provided if not known.

Unit: million €


e_Definition:
Name of the EU fund planned to be used for the UWWTP (if any)


e_Methodology:
If known at the reference date. 
The reported value of the flatpEUFund should not be higher than the forecast value of investment cost.

Unit: million €


e_Definition:
Any relevant comment on particular UWWTP

e_Methodology:
Examples: 
- problems for implementation of remedial measures
- change of the project
- explanation of the delay of the project
- explanation of the "3other" treatment


e_Definition:
Expected rate [%] of entering load transported to this UWWTP by truck at the expected date of compliance.

e_Methodology:
It could have an impact on the design capacity of the treatment. This information has to be know whether or not this UWWTP will receive load coming from trucks.
The value should be between 0 and 100%.


e_Definition:
Amount of funds likely to be given  to complete the UWWTP (if any)


e_Definition:
Name of the entity planned to give fund to complete UWWTP (if any)


e_Definition:
Amount of loan likely to be granted to complete the UWWTP (if any)


e_Definition:
Name of the entity planned to give loan to complete the UWWTP (if any)


e_Definition:
ID Code corresponding to the period covered.

e_Methodology:
This value is required.

soecCode must be unique in the table.

Code has to be generated with the code of the country then 'UWWINV' then the beginning year and if the beginning year of the period is different to the last year it has to be added the last year with '_' before.
Examples: ATUWWINV2014_2016 or CZUWWINV2015


e_Definition:
Start of the Reference period for which the data is provided

e_Methodology:
This value is required.

The investment information is needed per period (e.g. 1 January 2015 to end 2015 or 1 January 2015 to end 2020).
The starting date of each reference period must be in the format  XXXX-01-01.
Each line concerns the starting date of one period. It is possible to have several periods in the reporting.
from 1 January XXXX to end YYYY
from 1 January XXXX to end YYYY
from 1 January XXXX to end YYYY
from 1 January XXXX to end YYYY

As the Commission would like to provide comparison between past/current and expected situations and to aggregate this information at EU level, it will intend to use the information from 2012 to 2016 to consider the past situation, the information from 2017 and 2018 to consider the current situation and from 2019 to 2023 to consider the expected situation. If possible MS are encouraged to provide yearly information from 2012 to 2023.


e_Definition:
End of the Reference period for which the data is provided

e_Methodology:
This value is required.

The investment information is needed per period (e.g. 1 January 2015 to end 2015 or 1 January 2015 to end 2020).
The end date of each reference period must be in the format YYYY-12-31.
Each line concerns the end date of one period. It is possible to have several periods in the reporting.
from 1 January XXXX to end YYYY
from 1 January XXXX to end YYYY
from 1 January XXXX to end YYYY
from 1 January XXXX to end YYYY

As the Commission would like to provide comparison between past/current and expected situations and to aggregate this information at EU level, it will intend to use the information from 2012 to 2016 to consider the past situation, the information from 2017 and 2018 to consider the current situation and from 2019 to 2023 to consider the expected situation. If possible MS are encouraged to provide yearly information from 2012 to 2023.


e_Definition:
Current and / or expected reference period for which the data is provided.


e_Definition:
Current or expected total organic design capacity of all UWWTPs at the end of the period.

e_Methodology:
This value is required.

Unit: p.e. (population equivalent)

For the current situation it can be calculated as a sum of all organic design capacity of the UWWTPs reported under article 15 for compliant and not compliant situations.
The expected total organic design capacity can be calculated as the current total design capacity modified by the information on organic design capacity of individual UWWTPs as planned given in the table FLAUWWTPs. The value should include UWWTPs serving agglomeration of less than 2000 p.e. (if available). Explanation of how it is calculated might be added in the comment cell.


e_Definition:
Current or expected investment costs of the collecting systems (new and renewal).

e_Methodology:
This value is required.

Unit: million euros. 

Values should be reported in euros in current prices. Reference date (in MM/YYYY) and an information whether VAT is included or not should be provided under the “soecInvComments".
All investments have to be taken into account (not only the investments addressing the non-compliant situations under the different EU directives). Renovation costs should be included.
Method of the investment costs calculation can be specified under the “soecInvComments”.


e_Definition:
Current or expected investment costs of the treatment plants (new and renewal).

e_Methodology:
This value is required.

Unit: million euros
 
Values should be reported in euros in current prices. Reference date (in MM/YYYY) and an information whether VAT is included or  not should be provided under the “soecInvComments.
All investments have to be taken into account (not only the investments addressing the non-compliant situations under the EU directives). Renovation costs should be included. Method of the investment costs calculation can be added in the comment cell “soecInvComments”.


e_Methodology:
Examples: calculation of total design capacity, amount of investment whether VAT is included or not,…)


e_Definition:
Current of expected Investment costs of the IAS

e_Methodology:
Unit: million euros.

Values should be reported in euros in current prices. Reference date (in MM/YYYY) and an information whether VAT is included or not should be provided under the “soecInvComments".
The value may be added if not included in the "current or expected costs of the collecting systems (new and renewal)".


e_Definition:
Current or expected operating costs of the collecting systems and UWWTPs without amortization of investments.

e_Methodology:
Unit: million euros

Values should be reported in euros in current prices. Reference date (in MM/YYYY) and an information whether VAT has been included or not should be provided under the “soecInvComments".


e_Definition:
Current or expected EU funds (if applicable)


e_Definition:
Current or expected number of Jobs in the waste water field.

e_Methodology:
If not known only for urban waste water policy, use Eurostat statistic on waste water management in the goods and services sector: http://ec.europa.eu/eurostat/web/environment/environmental-goods-and-services-sector/database


e_Methodology:
Provide the number of IAS included those for isolated areas


e_Definition:
Population of the country at the reference year

e_Methodology:
Provide the population of the country at the reference year.


# DEFINITIONS_TABLES_DO_NOT_MODIFY

tbl_Definition:
Basic Information: information on the reporting authority.

tbl_Methodology:
Table FLAContact should contain one contact record only. It has to follow the same format than the format requested under Article 15 reporting (reporter, report period, contact).


tbl_Definition:
Forward looking aspects-agglomerations: Disaggregated information on actual nature of the problems faced at agglomeration level, planned measures, expected compliance dates and support (to be) provided.

tbl_ShortDescription:
Information on non-compliant agglomerations or agglomerations under pending deadlines that do not meet the UWWTD requirements.


tbl_Definition:
Forward looking aspects-UWWTPS: Disaggregated information on actual reason of non-compliance, specific measures to be taken, expected treatment type and capacity, as well as planned funds.

tbl_ShortDescription:
Information on treatment plants which are considered non-compliant, or the treatment plants under pending implementation deadlines that do not meet the UWWTD requirements.


tbl_Definition:
Forward looking aspects: annual information on the cost of implementation, total size of the urban waste water treatment plants, current and expected number of related jobs and other aggregated information.

tbl_ShortDescription:
Aggregated annual information on the cost of implementation.


