1 / 10

MARINE STRATEGY FRAMEWORK DIRECTIVE (MSFD) COMMON IMPLEMENTATION STRATEGY

MARINE STRATEGY FRAMEWORK DIRECTIVE (MSFD) COMMON IMPLEMENTATION STRATEGY. MSFD regional data work flow: schema and examples. Document: DIKE TSG1 WP4 MSFD data workflow. MSFD DATA FLOWS: SUMMARY. WHAT: An approach to an agreed workflow between EU, MS, RSC, EMODnet , etc. HOW:

zlhna
Télécharger la présentation

MARINE STRATEGY FRAMEWORK DIRECTIVE (MSFD) COMMON IMPLEMENTATION STRATEGY

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MARINE STRATEGY FRAMEWORK DIRECTIVE (MSFD) COMMON IMPLEMENTATION STRATEGY MSFD regional data work flow: schema and examples • Document: DIKE TSG1 WP4 MSFD data workflow WG-DIKE/MODEG 04 JULY 2013 Neil Holdsworth, ICES

  2. MSFD DATA FLOWS: SUMMARY • WHAT: • An approach to an agreed workflow between EU, MS, RSC, EMODnet, etc. • HOW: • Mapping out the necessary components, actors and agreements needed to provide the workflow (collection to assessment) • WHY: • To achieve greater regional coherence AND ensure efficient use of resources • WHO: • MS through TSG- and WG-DIKE • WHEN: • 2013 i.e. now! WG-DIKE/MODEG 04 JULY 2013 Neil Holdsworth, ICES

  3. MSFD DATA FLOWS: COHERENCY • MS to achieve coherence and consistency within and between MSFD regions/sub-regions • Regional coordination not so evident from 2012 reporting • Need for support from Regional Sea Conventions • Streamline data/information management WG-DIKE/MODEG 04 JULY 2013 Neil Holdsworth, ICES

  4. MSFD DATA FLOWS: SCHEMAS • Mapping out components • DIKE has the remit to tackle parts of the MSFD puzzle • DIKE needs to know how all the pieces fit though WG-DIKE/MODEG 04 JULY 2013 Neil Holdsworth, ICES

  5. MSFD DATA FLOWS: SCHEMAS • Mapping out components • Split out the processes and components • Provide the linkages • Allow for regional/descriptor variation WG-DIKE/MODEG 04 JULY 2013 Neil Holdsworth, ICES

  6. MSFD DATA FLOWS: SCHEMAS • Structural and Process Elements Data Collection Data Assembly Indicator provision Assessment EU Process governance Methodology Operational basis Operators WG-DIKE/MODEG 04 JULY 2013 Neil Holdsworth, ICES

  7. MSFD DATA FLOWS: SCHEMAS 2015 2014 • Structural and Process Elements 2016 Data Collection Data Assembly Indicator provision Assessment EU Process governance Methodology Operational basis Operators WG-DIKE/MODEG 04 JULY 2013 Neil Holdsworth, ICES

  8. WG-DIKE/MODEG 04 JULY 2013 Neil Holdsworth, ICES

  9. MSFD DATA FLOWS: QUESTIONS • Do you agree to the model proposed where indicators are a central component? • Does it correctly reflect the roles and existing working arrangements among MS and RSC? If not, how should it be changed, or do we need to make it more regionally specific? • Does the model presented represent the desired continued working arrangements for fulfilling the MSFD obligations under article 19.3? If not, how should it be changed? WG-DIKE/MODEG 04 JULY 2013 Neil Holdsworth, ICES

  10. MSFD DATA FLOWS: QUESTIONS • How can this be made operational per descriptor and region? • Another central component of the model is sharing of observations. If other operators than the MS are to support the work under art 19.3, then relevant observations need to be made available by MS. What are barriers to sharing data? WG-DIKE/MODEG 04 JULY 2013 Neil Holdsworth, ICES

More Related