9. REPORTING AT RBD/SUB-UNIT LEVEL FOR RBMP (SCHEMA RBMPPOM)

The River Basin Management Plan (RBMP) is the main tool for the water management of all surface and groundwater bodies within a specified RBD and the contents of the RBMP are outlined in WFD Annex VII. With respect to water governance, the RBMP shall contain: a general description of the RBD; a summary of the significant pressures and impacts on surface and groundwater bodies; a summary of the measures intended to mitigate the impacts identified; a register of any more detailed plans proposed for sub-basins, sectors, management issues or water categories; a summary of public consultation; and, a list of the Competent Authorities including their relationship with other authorities co-ordinated within a Member State, and a summary of institutional relationships established to ensure co-ordination in international RBDs.

Importantly, the WFD sets Environmental Objectives for Member States to attain for surface and groundwater bodies, the default being ‘good status’ by 2015 (unless an exemption applies or the surface water body meets the conditions for an Artificial or Heavily Modified Water Body). The RBMP is the key tool by which the process to achieve such legally binding Environmental Objectives can be formally set out as a roadmap to implementation and be subject to review.

The WFD sets out a stepwise approach for the development of the RBMP, and if one requirement is not complete or correctly carried out, it may pose obstacles for subsequent steps in the implementation process.

A clear and complete RBMP is also important for accountability as it is also the main tool for communicating to interested parties, including the public, how integrated water management is, or will be, carried out. Complete draft RBMPs including, as appropriate, draft background documents, should be made available in a timely manner through the public consultation process, in order to ensure that interested parties are given sufficient information to enable them to express their views in a meaningful way.

Class RBMP

1. Please include here any comments which apply to all the schema elements in this Class.
2. In addition to those general schema element level comments, we welcome your views on: a) whether you think this Class can be simplified;  and b) whether you think the linkages with other reporting Classes or Schemas can be improved, and how;

rbmpName - Required.

Name of the RBMP in English.

rbmpTimetablePublicationDate - Required.

Date of publication of the timetable for the production of the RBMP, in the format YYYY-MM-DD.

rbmpProgrammePublicationDate - Required.(rbmpProgrammePublicationDate)

Date of publication of the work programme for the production of the RBMP, in the format YYYY-MM-DD.

rbmpConsultationPublicationDate - Required.

Date of publication of the consultation measures for the production of the RBMP, in the format YYYY-MM-DD.

rbmpInterimOverviewDate - Required.

Date of publication of the interim overview of the Significant Water Management Issues, in the format YYYY-MM-DD.

rbmpDraftVersionDate - Required.

Date of publication of the draft versions of the RBMP, in the format YYYY-MM-DD.

finalRBMPPublicationDate - Required.

Date of publication of the final RBMP, in the format YYYY-MM-DD.

subPlans - Required.(YesNoCode_Enum)

Indicate whether there are specific sub-plans as mentioned in Article 13.5 of the WFD.

subPlansCoverage - Conditional.(SubPlansCoverage_Enum)

If there are specific sub-plans, select the issues they address from the enumeration list. If ‘Other’ is selected, specify the issue(s) addressed in subPlansCoverageOther.

subPlansCoverageOther - Conditional.

If ‘Other’ is selected from the enumeration list under subPlansCoverage, list the issue(s) addressed.

subPlansReference - Conditional.(ReferenceType)

Provide references or hyperlinks to the documents and sections where relevant information relating to the sub-plans can be found. Links to the sub-plans themselves can be provided.

sea - Required.(YesNoCode_Enum)

Indicate whether Strategic Environmental Assessments (SEA) have been undertaken on the RBMP and PoM. 

seaReference - Conditional.(ReferenceType)

Provide references or hyperlinks to the SEA documents. 

publicConsultationInformation - Required.(PublicConsultationInformation_Enum)

Select the mechanism(s) used for informing the public and interested parties about the consultations on the draft RBMP from the enumeration list. More than one mechanism may be selected. If ‘Other’ is selected, specify the tool(s) used in publicConsultationInformationOther.

publicConsultationInformationOther - Conditional.

If ‘Other’ is selected from the enumeration list under publicConsultationInformation, list the mechanism(s) used.

rbmpConsultation - Required.(RBMPConsultation_Enum)

Select the tool(s) used to carry out the public consultation on the draft RBMP from the enumeration list. More than one tool may be selected. If ‘Other’ is selected, specify the tool(s) used in rbmpConsultationOther.

rbmpConsultationOther - Conditional.

If ‘Other’ is selected from the enumeration list under rbmpConsultation, list the tool(s) used.

documentProvision - Required.(DocumentProvision_Enum)

Select the method(s) used to provide the public and interested parties with the consultation documents (e.g. draft RBMPs and background documents) from the enumeration list. More than one method may be selected. If ‘Other’ is selected, specify the method(s) used in documentProvisionOther.

documentProvisionOther - Conditional.

If ‘Other’ is selected from the enumeration list under documentProvision, list the method(s) used.

documentAvailability - Required.(YesNoCode_Enum)

Indicate whether the consultation documents (e.g. draft RBMPs and background documents) were made available for 6 months for feedback.

ongoingStakeholderInvolvement - Required.(OngoingStakeholderInvolvement_Enum)

Select the tools(s) used to achieve the continued active participation of stakeholders in the implementation of the WFD from the enumeration list. More than one tool may be selected. If ‘Other outreach activities’ is selected, specify the outreach activities(s) used in ongoingStakeholderInvolvementOtherOutreach. If ‘Other’ is selected, specify the method(s) used in ongoingStakeholderInvolvementOther.

ongoingStakeholderInvolvementOtherOutreach - Conditional.

If ‘Other outreach activities’ is selected from the enumeration list under ongoingStakeholderInvolvement, list the outreach activities(s) used.

ongoingStakeholderInvolvementOther - Conditional.

If ‘Other’ is selected from the enumeration list under ongoingStakeholderInvolvement, list the tool(s) used

stakeholderGroups - Required.(StakeholderGroups_Enum)

Select the stakeholder groups that have been actively involved in the development of the RBMPs from the enumeration list. More than one stakeholder group may be selected. If ‘Other’ is selected, specify the stakeholder group(s) in stakeholderGroupsOther.

stakeholderGroupsOther - Conditional

check: Report if stakeholderGroups is ‘Other’.

impactPublicParticipation - Required.(ImpactPublicParticipation_Enum)

Select the impact(s) of the public participation process on the RBMPs from the enumeration list. This refers to the whole RBMP process, not just the 6 month consultation on the draft plan. More than one impact may be selected. If ‘Other’ is selected, specify the impact(s) in impactPublicParticipationOther.

impactPublicParticipationOther - Conditional.

If ‘Other’ is selected from the enumeration list under impactPublicParticipation, list the impact(s).

internationalCoOrdination - Conditional.(InternationalCoOrdination_Enum)

If the RBD is international, select the type of international co-operation or co-ordination mechanism(s) that exist between neighbouring Member States from the enumeration list. 

internationalCoOrdinationPublicParticipation - Conditional.(YesNoCode_Enum)

If the RBD is international, indicate whether there has been international co-ordination on public participation and the active involvement of interested parties.

publicParticipationReference - Required.(ReferenceType)

Provide references or hyperlinks to the documents and sections where relevant information relating to public participation and its effectiveness can be found including information on international coordination if any.  

consultationResponsesReference - Required.(ReferenceType)

Provide references or hyperlinks to the documents and sections where relevant information on the RBMP public consultation responses can be found.  

integrationFloodsDirective - Required.(YesNoCode_Enum)

Indicate whether RBMPs and Floods Directive Flood Risk Management Plans have been integrated into a single plan. 

coOrdinationFloodsDirective - Required.(YesNoCode_Enum)

Indicate whether joint consultation was carried out on the RBMPs and Flood Risk Management Plans. 

fdCoordinationReference - Required.(ReferenceType)

Provide references or hyperlinks to the documents and sections where relevant information on the coordination of the RBMP with the Floods Directive implementation can be found.  

coOrdinationMSFD - Required.(YesNoCode_Enum)

Indicate whether joint consultation was carried out on the RBMPs and Marine Strategy. 

msfdCoordinationReference - Required.(ReferenceType)

Provide references or hyperlinks to the documents and sections where relevant information on the coordination of the RBMP with the Marine Strategy Framework Directive implementation can be found.  

Class InputInventory

1. Please include here any comments which apply to all the schema elements in this Class.
2. In addition to those general schema element level comments, we welcome your views on: a) whether you think this Class can be simplified;  and b) whether you think the linkages with other reporting Classes or Schemas can be improved, and how;

euSubUnitCode - Conditional.

If applicable, report the unique EU code of the Sub-unit. If there are no sub-units this element does not need to be reported and the reporting of the information is done at RBD level.

inputInventoryReference - Required.(ReferenceType)

Provide references or hyperlinks to the documents and sections where any other relevant information relating to the estimation of the inputs of pollutants can be found.  Guidance on what should be included in this document is provided in Section 9.3.3.3. 

Class InputPollutant

1. Please include here any comments which apply to all the schema elements in this Class.
2. In addition to those general schema element level comments, we welcome your views on: a) whether you think this Class can be simplified;  and b) whether you think the linkages with other reporting Classes or Schemas can be improved, and how;

chemicalSubstance - Required. (ChemicalSubstances_Union_Enum)

Select each EQSD Annex I substance in turn to provide the information detailed in the following schema elements.

chemicalSubstanceOther - Conditional.

Conditional if ‘chemicalSubstance’ is ‘EEA_00-00-0 Other chemical parameter’ please indicate in this field the CAS number (if relevant) and the name of the pollutant or indicator.

inventory - Required.(YesNoCode_Enum)

Indicate if an inventory of emissions, discharges and losses has been completed for this substance. 

reportedUnderSoEEmissions - Conditional.(YesNoCode_Enum)

Has the two-step approach in CIS-Guidance No 28 been followed? Step 1 requires an assessment of the current relevance of the substance at the RBD level. Step 2 requires a more detailed analysis for the substances which pass the relevance criteria given in Step 1 (i.e. they are relevant at the RBD level). For those substances that are of minor relevance at the RBD scale (i.e. do not meet Step 1 criteria), MS should try to provide a basic estimation of emissions, discharges and losses from point and diffuse sources: this is particularly important for Priority Hazardous Substances. Together with Schema element relevanceRBDScale this element determines the data-set to be reported for each substance.

twoStepApproach - Conditional.(YesNoCode_Enum)

Has the two-step approach in CIS-Guidance No 28 been followed? Step 1 requires an assessment of the current relevance of the substance at the RBD level. Step 2 requires a more detailed analysis for the substances which pass the relevance criteria given in Step 1 (i.e. they are relevant at the RBD level). For those substances that are of minor relevance at the RBD scale (i.e. do not meet Step 1 criteria), MS should try to provide a basic estimation of emissions, discharges and losses from point and diffuse sources: this is particularly important for Priority Hazardous Substances. Together with Schema element relevanceRBDScale this element determines the data-set to be reported for each substance.

relevanceRBDScale - Conditional.(YesNoNotApplicable _Enum)

To be answered for reported substances. "Yes" if proceeding to second step of two-step approach. (See criteria on pages 9-10 of the CIS-Guidance No 28.) "No" leads to optional point source assessment. Any knowledge of quantifiable inputs of priority hazardous substances should be reported. “Not applicable” if the Two Step Approach has not been used.

inventoryMethodology - Required (InventoryMethodology_Enum)

Required for all substances reported. Indicates the approach used to determine the reported inputValue (and inputCategoryValue if reported). Further descriptions of Tiers 1-4 in CIS Guidance Document 28. Other methodology to be detailed (see inputMethodReference). May be different for different substances and individual input categories. Tier 1 automatic if "No" re "relevanceRBDScale".

inputDataQuality - Optional.(InputDataQuality_Enum)

It can be reported if quantitative data for this substance is reported. To reflect the reliability and variance of the data provided, taking into account issues such as the availability of monitoring data, the reliability of emission factors used in calculations, the difficulty of taking account of seasonal influences in areas with high seasonal variation etc. E.g. very good would imply a substantial monitoring basis, very uncertain would imply a very weak or absent monitoring basis (heavy reliance on estimation).

inputMethodReference - Conditional.(ReferenceType)

Required if "Other" methodology is specified under inventoryMethodology. Desirable if approaches in CIS-Guidance Document 28 have been elaborated or described in an electronic freely accessible version of the national emission inventory for EQSD Annex I substances, in specific documents as part of RBMP reporting, in international seas convention guidance documents or similar. URL-Reference to specific documents.

inputTotalType - Conditional.(InputTotalType_Enum)

Required for all EQSD Annex I substances reported. Optional for other substances/parameters. Distinction between total point and total diffuse expected for EQSD Annex I substances.

inputTotalValue - Conditional.

Required for all EQSD Annex I substances reported. Optional for other substances/parameters. Input = emissions, discharges and losses.

inputTotalUnit - Conditional.(UnitOfMeasure_Enum)

Required if inputTotalValue is reported.

inputYearPeriod - Conditional.

4-digit number (should ideally be 2008, 2009 or 2010 as reference year) required for EQSD Annex I substances and for other substances for which an inputValue is reported. Calendar year to which the load applies. A period of up to six years within the relevant RBMP period may be indicated by a start and end year, separated by a double hyphen ( yyyy--yyyy ).

inputTrend - Optional. 

For each chemical substance a trend (positive or negative) can be reported directly (self-assessed), independently of any trend that might be calculated directly from the datasets reported for those years.

inputTrendPeriod - Conditional.

If inputTrend is reported, report first and last years of trend assessment.

Class InputCategory

1. Please include here any comments which apply to all the schema elements in this Class.
2. In addition to those general schema element level comments, we welcome your views on: a) whether you think this Class can be simplified;  and b) whether you think the linkages with other reporting Classes or Schemas can be improved, and how;

inputCategoryCode - Required.(InputCategory_Union_Enum)

Allows apportionment of inputs between different sources/pathways. 

inputCategoryScheme - Required.(InputCategoryScheme_Enum)

Identifies the type of emmissions apportionement being used.

inputCategoryValue - Required.

The multiplicity of the whole Class InputCategory is 0 to many. If the class is reported, this schema element must be included.

inputCategoryUnit - Required.(UnitOfMeasure_Enum)

The multiplicity of the whole Class InputCategory is 0 to many. If the class is reported, this schema element must be included.

inputUWWTPCoverage - Conditional.(InputUWWTPCoverage_Enum)

If categories for Urban Waste Water Treatment Plants are reported please indicate the coverage. Please note that under WISE SoE specific categories exist for this purpose (U11, U12, U13, U14, U21, U22, U23, U24).

inputIndustryCoverage - Conditional.(InputIndustryCoverage_Enum)

If categories for Industrial Waste Water Treatment plants are reported please indicate the coverage. “E-PRTR” means large facilities with releases to water reported in E-PRTR; “national business registers” means including also medium size facilities with emission data in registers; “all manufacturimg industries” means including also small size facilities with direct discharges based on economic activity extrapolations. 

riverineLoadMonitoringSite - Optional.

If reporting inputCategoryValues as riverine loads, provide the code of the monitoring station used as a basis.

Guidance on the contents of RBMPs/background documents

(Please see the full text of this sub-section in the WFD Reporting Guidance 2016 or above chapter)

Include here any comments that relate to the information contained in this sub-section of the Reporting Guidance, namely concerning information you think could/should be reported electronically and information which you believe should not be included in the River Basin Management Plans or background documents.