Guidance for reviewing CEMP Appendices
The Coordinated Environmental Monitoring Programme (CEMP) Appendices are reviewed and if necessary revised, on an annual basis to ensure they are kept up to date.
The Table below is designed to provide Guidance to Contracting Parties carrying out the annual review and revision. The 'Validated Entry' column within each appendix should be reviewed against information in the Guidance column below and populated using fields in the Enumeration Tables . The green rows are OSPAR specific fields.
(For information on the alignment process that OSPAR undertook to align with the EC MSFD Art.11 monitoring programmes reporting tables, please see Background ).
|[Table title]||Name of monitoring programme||Required||Short name that reflects main focus of the programme, such as e.g. ecosystem elements, pressures and associated policy, e.g. OSPAR CEMP contaminants monitoring, Habitats Directive Posidonia monitoring. An indicative list of names is provided in Annex III.|
|[ProgrammeDescription]||Description of the monitoring programme||Optional||Free text (max. 2500 characters).|
|[OtherPoliciesConventions]||Monitoring for other Union legislation or international agreements that contributes to the programme.||Required||In addition to the MSFD, state to which other EU policies and international agreements (including Regional Sea Conventions), this programme contributes. Enter as many Directives and Conventions as necessary from list: 'DirectivesConventions_enum '|
|[Contracting Parties monitoring]|
Which other countries are involved in practical implementation of this monitoring programme, and what is the degree of cooperation.
Provide a list of countries involved in the programme (from List ‘CountryCode_enum ’).
|[Contracting Parties supplying data]||OSPAR-specific||Contracting Parties supplying data to the monitoring (from List 'CountryCode_enum ')|
|[Contracting Parties with an "opt out"]||OSPAR-specific|
Contracting Parties opting out from the monitoring (from List 'CountryCode_enum ')
|[Temporal scope]||Start (and end) date of the programme.||Required||YYYY-YYYY (if the end date is unknown, provide ‘9999’ as end-date)|
|[Spatial scope]||Spatial coverage of the programme according to the jurisdictional zones of marine waters.||Required|
Select one (or more) option(s) from list:
|[Aggregation of Data]||At which scale can the data from the sub-programme be aggregated for environmental assessments?||OSPAR-specific||This refers to the ability to aggregate the data (in raw or processed form) from several sources (different Member States) so that it can be used/interpreted/mapped at a scale beyond the source scale, e.g. to contribute to an indicator assessment at (sub)regional scale. This ability to aggregate indicates that the data format has been agreed with other countries (e.g. for submission to international databases or for use in (sub)regional indicator assessments).|
|[MarineReportingUnit]||Area(s) where the programme takes place.||Required||Enter all relevant Marine Reporting Units for the [MS marine waters] [entire monitoring programme] where the programme takes place (MarineUnitID, as reported by MS in 4geo.xml file).|
|Purpose of the programme aimed at collecting data and information.||Required|
Select one (or more) option(s) from list:
|[MonitoringType]||Type of monitoring (in-situ, remote sensing, etc.).||Required|
Select relevant options from list:
|[Indicator Metric]||Feature(s) monitored (ecosystem components, pressures, activities).||Required||Enter the codes of the feature(s) from list ‘Feature_enum ’.|
|[Elements]||Element(s) monitored (e.g. species, habitats, contaminants).||Required|
For each feature, enter the corresponding element(s) expected to be monitored:
To be selected from the list 'Elements_enum '. If the list does not contain the elements needed, contact firstname.lastname@example.org.
|[Parameter Measured]||Parameter(s) monitored.||Required||Enter the relevant parameter(s) monitored from list ‘Parameters_enum ’. If the list does not contain the parameters needed, contact email@example.com.|
|[Monitoring Guidelines/Monitoring Method in place]||Guidelines/protocols describing the method for monitoring.||Required||Enter corresponding method code from list ‘MonitoringMethod_enum ’.|
|[MonitoringMethodOther]||Guidelines/protocols describing the method for monitoring.||Conditional (if MonitoringMethod is ‘Other’)||Free text (max. 2500 characters) or URL web link.|
|[Quality Assurance Procedures in Place]||In addition to a specified method, is there any additional Quality Assurance used?||OSPAR-specific||QA can be considered as the guidance on procedures (how to collect the data) put in place before monitoring is started, whilst QC is undertaken during/afterwards to check if the outcomes of the monitoring (the data or products) are of sufficient quality.|
|[Quality Control]||What type of Quality Control is used?||Required||Free text (max. 2500 characters) or URL web link.|
|[Data submission Frequency (and deadline)]||Frequency of the monitoring||Required||Enter corresponding frequency from list ‘Frequency_enum ’.|
|[Applicable MSFD GES Criteria]||Indicator(s) to which the programme contributes.||Required (where available)||Enter as many indicator codes as necessary (as reported by MS under the schema ‘Indicators’ used in the 2018 update of Articles 8 and 10). (This field needs splitting as includes criterion and indicator)|
|[Data Depository]||Link to where monitoring data can be accessed (Art. 19(3)||Required||Provide URL link (s).|
|[Data Custodian]||OSPAR-specific||Name of responsible data manager|
|[Assessment Guidelines]||OSPAR-specific||Provide URL link (s).|
|[Assessment tools available]||OSPAR-specific||Provide URL link (s).|
|[Nature of data]||OSPAR-specific||Choose from: Unprocessed, Processed, Product, Unknown|