1 ANNEX, Decision_act (EU) 2022/39

In forcesince 12 Jan 2022

The work plans and annual reports contain information grouped in tables and text boxes. This annex lists these tables and text boxes, and describes their fields.

Where a Member State does not conduct data collection in sectors covered by certain tables or text boxes, it is not obliged to submit the corresponding tables or text boxes in the work plan (WP) or annual report (AR). Member States shall indicate by (Y/N) in the summary table of the WP which tables and text boxes are included and which are not.

The grey-shaded sections of tables and text boxes relate only to the annual reports. The remaining sections relate to the work plans and must be copied unaltered to the relevant annual report. Columns containing formulas should fill in automatically.

Member States shall first transfer the information from their adopted work plans to each corresponding table and text box in the annual report, and then fill in the additional grey-shaded columns.

When compiling the annual report, Member States shall not edit any values in tables or text boxes that originate from their accepted work plans, with the exception of:

Table 1.2: meetings not included in the work plan may be inserted as additional rows, highlighted in grey, at the end of the table.

Table 1.3: new agreements not included in the work plan may be inserted as additional rows, highlighted in grey, at the end of the table.

Table 2.1: species not included in the work plan may be inserted as additional rows, highlighted in grey, at the end of the table.

Table 2.2: new species, parameters or sampling schemes not included in the work plan may be inserted as additional rows, highlighted in grey, at the end of the table.

Table 2.5: new sampling schemes or frames not included in the work plan may be inserted as additional rows, highlighted in grey, at the end of the table.

Table 1.4 applies only to the annual report. Member States shall use it to specify their follow-up to the recommendations and agreements related to the data collected under the DCF at EU and international level.

Where necessary, Member States shall explain deviations from the work plan in the relevant ‘AR comments’ in the tables, and in the text boxes in the annual report. In the text boxes, they shall specify actions that will be taken to avoid deviations from the work plan in the future.

Member States shall apply consistent naming and coding of gears, species, metiers, fishing grounds and alike throughout the tables and text boxes of the work plans and annual reports.

Where applicable, Member States shall use codes and names from relevant tables in the annexes to the EU MAP decisions and other international conventions, including those agreed by regional coordination groups.

If a Member State operates in several regions, it shall present its data collection activities per region, for biological data, and per supra region, for economic data. The regional stratification is included in Table 2 of the Annex to Commission Implementing Decision (EU) 2021/1168. The Member State shall present its activities outside EU waters grouped in regional sections and within the region, by regional fisheries (management) organisation or other international organisation. The same division shall be maintained throughout the tables and the text boxes in the work plans and annual reports.

General comment: Use this text box to describe how data collection is organised in your Member State (institutions involved, contact information) and in which regional coordination groups (RCG) your Member State participates.

Outline the general framework of the national data collection programme in relation to the relevant sections of the EU MAP. If applicable, indicate major methodological changes in approach compared to previous year(s), and to which section(s) they apply.

Give full name, acronym and contact details of all institutes that contribute to the data collection activities, and describe briefly their role in the work plan.

Provide a link to the national data collection website, if there is one.

(max. 1000 words)

General comment: This table fulfils Article 6(3)(e) of Regulation (EU) 2017/1004. Use this table to provide information on data availability per data set.

Field name | Description

MS | Use ISO 3166-1 alpha-3 code e.g. ‘DEU’. See MasterCodeList ‘MS’.

Region | See MasterCodeList ‘Regions’. If information refers to all regions, use code ‘all regions’.

RFMO/RFO/IO | Enter the acronym of the competent regional fisheries management organisation (RFMO), regional fisheries organisation (RFO) or international organisations (IO) providing management/advice on the species/stock. See MasterCodeList ‘RFMO/RFO/IO’. If no RFMO, RFO or IO is applicable, use ‘NA’ (not applicable).

WP table | Indicate the specific table in the work plan with details of the corresponding data.

Data set | Indicate the data set for which information on availability will be given. See MasterCodeList ‘Data set’.

Data subset | Indicate the subset for which information on availability will be given. See MasterCodeList ‘Data subset’.

Specific item | Free text if needed

Implementation year | Indicate the year or years in which the work plan will be implemented.

Reference year | Indicate the year for which data will be collected (e.g. ‘N’, ‘N-1’). The year of implementation is ‘N’.

Availability of the data | Indicate when the data collected during the reference year is planned to be available. Be as precise as possible (e.g. ‘N+1’, ‘N+1-2nd quarter’, ‘N+1, specific date’, etc.).

WP comments | Any further comments

General comment: Member States should provide information on the data availability per data set. New data not included in the work plan may be added as additional rows, highlighted in grey, at the end of the table.

Time when data were available | Indicate when data were made available.

AR comments | Add comments to clarify any deviation from the work plan.

General comment: This table fulfils Article 7(2)(c) of Regulation (EU) 2017/1004. Use this table to provide information on the planned participation of the Member State in meetings relevant for data collection under the DCF.

Field name | Description

MS | Use ISO 3166-1 alpha-3 code e.g. ‘DEU’. See MasterCodeList ‘MS’.

Meeting acronym |

Indicate an official acronym for meetings your Member State plans to attend.

As a minimum, indicate the national coordination meeting even if your Member State decided not to organise it; all RCG meetings where your Member State is involved; annual meetings of the RCG where your Member State is not involved; the Liaison meeting; the National Correspondents’ meeting. If some meetings cannot be planned by the time the WP is submitted, you may add the meetings which your Member State has attended in the AR. Indicate in ‘WP comments’ column if your Member State does not organise a national meeting or does not participate in an RCG.

Name of meeting | Enter the full official name of the meetings that your Member State plans to attend. Do not leave empty cells if you filled the ‘Meeting acronym’ column. Indicate in ‘WP comments’ column if you do not organise a national meeting or do not participate in an RCG.

RFMO/RFO/IO | Enter the acronym of the competent regional fisheries management organisation (RFMO), regional fisheries organisation (RFO) or international organisations (IO) providing management/advice on the species/stock. See MasterCodeList ‘RFMO/RFO/IO’. If no RFMO, RFO or IO is applicable, use ‘NA’ (not applicable).

WP comments | Any further comments.

General comment: Member States should provide information on the number of meetings related to the DCF that they attended. New meetings not included in the work plan may be added as additional rows, highlighted in grey, at the end of the table.

Number of MS participants | Indicate the number of participants from your Member State per meeting. Enter ‘0’ if no participants attended the meeting.

AR comments | Add comments to clarify any deviation from the work plan.

General comment: This table fulfils Article 6(3)(f) of Regulation (EU) 2017/1004. Use this table to provide information on the agreements with other Member States and how European and international obligations are met. List only current and planned agreements. If an agreement expires during a period covered by the WP, mark it as ‘obsolete’ in the ‘AR comments’ for the year in which it is no longer in force.

Field name | Description

MS | Use ISO 3166-1 alpha-3 code e.g. ‘DEU’. See MasterCodeList ‘MS’. Enter all Member States involved in an agreement. Separate multiple entries by a semicolon.

Name of the agreement | Indicate the name of the agreement. The Member States concerned should apply the same name for the same agreement.

Contact persons | Provide the name and email address of the national correspondent from each Member State involved in the agreement.

Content | Describe briefly the aim and content of the agreement. Provide an unambiguous full reference or a valid link to the documentation of the agreement, where relevant, in the ‘WP comments’ column.

Coordination | Describe briefly how the coordination is done/will be done and by whom.

Description of sampling/sampling protocol/sampling intensity | Describe briefly the sampling to be carried out under the agreement.

Data transmission | Indicate which Member State is or will be responsible for submitting which data set.

Access to vessels | Indicate by (Y/N) if the agreement implies any form of access to other partners’ vessels. If access is implied, specify it (boarding, sharing samples at landing etc.) in ‘WP comments’ column.

Validity | Indicate the year when the agreement expires or the year when the agreement was/will be signed, if it is automatically extended annually.

WP comments | Any further comments.

General comment: Member States should provide information on changes to ongoing agreements. New agreements not included in the work plan may be added as additional rows, highlighted in grey, at the end of the table.

AR comments | Add comments if there were any changes to the agreements during the implementation year. Use ‘ongoing’ if the agreement is still operational; ‘obsolete’ if it is no longer in force; ‘new’ if the agreement has been added.

General comment: This table fulfils Article 6(3)(g) of Regulation (EU) 2017/1004. Use this table to provide information on how your Member State plans to fulfil the recommendations and agreements relating to data collection under the DCF at European and international level and how European and international obligations are met.

Field name | Description

MS | Use ISO 3166-1 alpha-3 code e.g. ‘DEU’. See MasterCodeList ‘MS’.

Region | See MasterCodeList ‘Regions’. If information refers to all regions, use code ‘all regions’.

RFMO/RFO/IO | Enter the acronym of the competent regional fisheries management organisation (RFMO), regional fisheries organisation (RFO) or international organisations (IO) providing management/advice on the species/stock. See MasterCodeList ‘RFMO/RFO/IO’. If no RFMO, RFO or IO is applicable, enter ‘NA’ (not applicable).

Source of recommendation/agreement | Indicate the source of the recommendation as an acronym of a relevant Regional Coordination Group (RCG), Liaison Meeting (LM), STECF Expert Working Group (EWG), e.g. ‘LM 2020’, ‘STECF EWG 20-08’.

EU MAP section | Indicate to which paragraph in the EU MAP Delegated Decision annex the recommendation relates (e.g. 1. General principles, 5. Socioeconomic data on fisheries, etc.). If a recommendation relates to several sections, indicate all of them. If a recommendation applies to all EU MAP sections, insert ‘all’.

Topic | Indicate the topic to which the recommendation applies, e.g. ‘Data quality’, ‘Surveys’ etc.

Recommendation number |

If applicable, indicate the specific recommendation number.

Otherwise, enter ‘NA’.

Recommendation/Agreement | Refer only to the recommendations and agreements applicable to your Member State. There is no need to list recommendations and agreements that do not apply to your Member State (e.g. on Terms of Reference of expert groups, on actions to be taken by the Commission, etc.). For agreements, the Member States concerned should apply the same description for the same agreement.

Follow-up action | Describe briefly the follow-up actions taken or to be taken.

AR comments | Any further comments.

General comment: This text box fulfils Chapter II, point 1.2 of the EU MAP Delegated Decision annex.

1.

Aim of the test study

2.

Duration of the test study

3.

Methodology and expected outcomes of the test study

(max. 900 words per study)

Brief description of the results (including deviations from the plan and justifications as to why if this was the case).

Achievement of the original expected outcomes of the study and justification if this was not the case.

Incorporation of study results into regular sampling by the Member State.

(max. 900 words per study)

General comment: Use this text box to provide information on other data collection activities that relate to your EMFAF operational programme and need to be included in the work plan and the annual report. Describe activities that are funded by the DCF but fulfil objectives under other EMFAF priorities, like marine knowledge, or activities funded by the DCF, but without a direct link to the EU MAP specific requirements or WP template tables, like freshwater fisheries. You can also include one-off specific studies for a particular end-user need that do not enter the regular data collection.

1.

Aim of the data collection activity

2.

Duration of the data collection activity

3.

Methodology and expected outcomes of the data collection activity

(max 900 words per activity)

Brief description of the results (including deviations from the plan and justifications as to why if this was the case).

Achievement of the original expected outcomes and justification if this was not the case.

Follow-up to the activities (what are the next steps, how the results will be used).

(max 900 words per activity)

General comment: This table fulfils Article 5(2)(a), Article 6(3)(a), (b) and (c) of Regulation (EU) 2017/1004 and Chapter II point 2.1(a) of the EU MAP Delegated Decision annex. This table is intended to specify data to be collected under Table 1 of the EU MAP Delegated Decision annex. Use this table to give an overview of the collection of data at the level of area/stock. All individuals sampled shall be identified to species level and have length measurements taken, where possible. Other biological data different from length are specified in Table 2.2, and may include data collected under the surveys at sea.

Field name | Description

MS | Use ISO 3166-1 alpha-3 code e.g. ‘DEU’. See MasterCodeList ‘MS’.

Reference period |

Indicate the year(s) to which the data actually refer. Select the three most recent representative years before the first year of the WP period (no update of reference period needed within the WP period), with the data available. Give the reference years as e.g. ‘2018-2020’.

When the reference period differs from the most recent three years, clarify it in the ‘WP comments’ column.

Region | See MasterCodeList ‘Regions’. If information refers to all regions, use code ‘all regions’.

RFMO/RFO/IO | Enter the acronym of the competent regional fisheries management organisation (RFMO), regional fisheries organisation (RFO) or international organisations (IO) providing management/advice on the species/stock. See MasterCodeList ‘RFMO/RFO/IO’. If no RFMO, RFO or IO is applicable, enter ‘NA’ (not applicable).

Species |

Indicate the scientific name of all the species/stocks listed in Table 1 of the EU MAP Delegated Decision annex, for all regions and areas where your Member State’s fishing fleet operates.

When the fleet operates in a combined region (e.g. Mediterranean and Black Sea), list all species for that region. You may add additional rows, at the end, for species or stock not included in Table 1 of the EU MAP Delegated Decision annex, for which sampling is required by your Member State, RFMOs or is agreed at marine region level. Justify such an inclusion in the ‘WP comments’ column.

Area | Indicate the area for the mentioned species/stock, in accordance with column 3 of Table 1 of the EU MAP Delegated Decision annex.

Average landings in the reference years (tonnes) | Enter the average landings per year in the statistics reference period for each species and stock. If the species is not landed at all, then enter ‘None’. Provide the exact number of tonnes without decimal positions.

Data source used for average national landings | Enter the data source for the average national landings. See MasterCodeList ‘Data Source’.

EU TAC (if any) (%) |

Only applies to stocks that are subject to TAC and quota regulations.

Enter ‘None’, if your Member State has no share in the EU TAC of the stock concerned.

Enter the percentage of the share (value between 0 and 100) if your Member State has a share in the EU TAC of the stock concerned.

If the TAC refers to several combined species, enter the percentage of the share in the TAC for each species and indicate the combination in the ‘WP comments’ column. In case of a significant quota swap (more than 50 % of the TAC share), indicate the volume of the swap in the ‘WP comments’ column.

Enter ‘NA’ if the stock is not managed by TAC. In this case fill in the ‘Share (%) in EU landings’ column.

Share (%) in EU landings | Applies to all stocks for which no TACs have been defined (yet). Enter ‘None’, if your Member State has no landings of the stock concerned. Enter the percentage of the share (value between 0 and 100), if your Member State has landings of the stock concerned.

Data source used for EU landings | Enter the data source for EU landings. See MasterCodeList ‘Data source’.

Threshold rules used |

Indicate which threshold rules apply, when a species is not selected for sampling. For species that are selected for sampling enter ‘None’. For diadromous species enter ‘None’, as no thresholds apply to them under the EU MAP. Use the hierarchy of rules: 1) ‘TAC < 10 %’, 2) ‘Landings < 10 %’, 3) ‘Landings < 200t’.

If your Member State has no landings/catches in a given ‘species*area’, enter ‘Landings < 200 t’.

See MasterCodeList ‘Threshold rules used’.

Regional coordination agreement at stock level | Enter ‘Y’ (yes) or ‘N’ (no) if there is a regional agreement on sampling the stock. If there is a regional agreement, refer to the name of the agreement in Table 1.3. If different multispecies sampling schemes apply to the same stock and not all of them are regionally coordinated, explain the situation in the ‘WP comments’ column.

Covered by a commercial sampling scheme for length | Enter ‘Y’ (yes) or ‘N’ (no) if the species/stock is covered by a commercial sampling for length. A stock is considered to be covered by sampling if length structures have been sent to end users routinely during the last three years, or if it is covered by a new sampling frame with a plan to send the length structure to the relevant RFMO/RFO/IO in the future.

Selected for sampling of biological variables | Enter ‘Y’ (yes) if the species/stock has been selected for sampling for at least one variable of Table 2.2 of the work plan, and enter ‘N’ (no) if otherwise. Make sure that all stocks marked by a ‘Y’ in this field have an entry in Table 2.2.

WP comments | Any further comments.

General comment: Member States should provide information on the number of fish individuals measured for each species/stock. New species/stock, not included in the work plan, may be inserted as additional rows highlighted in grey, at the end of the table.

Achieved number of individuals measured for length at national level from commercial sampling | Indicate the total number of fish individuals measured for length at national level from commercial fisheries.

Achieved number of samples for length at national level from commercial sampling | Indicate the number of samples (primary sampling units – PSUs) from commercial fisheries from which the number of individuals was obtained. Even when a species is not selected for sampling, but data are collected, put the number of samples here.

AR comments | Add comments to clarify possible differences between the achieved numbers compared to the expectations based on the protocol. Indicate in this column if extended comments are given in Text Box 2.1. You may add any further comments.

General comment: This text box fulfils Article 5(2)(a), Article 6(3)(a), (b) and (c) of Regulation (EU) 2017/1004 and Chapter II point 2.1(a) of the EU MAP Delegated Decision annex. This text box applies to the annual report and complements Table 2.1.

List the deviations (if any) in the achieved data collection (lengths only) compared to what was planned.

The general reasons for deviations from the work plan in terms of planned vs. achieved data collection should be summarised in this section, while detailed comments on deviations on particular species/stocks should be included in the ‘AR comments’ column in Table 2.1.

Describe the actions that will be considered/have been taken to avoid deviations in the future and when these actions are expected to produce an effect. If there are no deviations, then this section is not applicable.

(One text box of max. 1000 words per region/RFMO/RFO/IO)

General comment: This table fulfils Article 5(2)(a), Article 6(3)(a), (b) and (c) of Regulation (EU) 2017/1004 and Chapter II point 2.1(a) of the EU MAP Delegated Decision annex. This table is intended to specify biological data (other than length) to be collected under Table 1 of the EU MAP Delegated Decision annex. For species listed in this table, biological variables (age, weight, sex ratio, maturity and fecundity) that are planned to be collected shall be shown. The table shall also include data collected under the surveys at sea specified in Table 2.6, and from recreational fisheries specified in Table 2.4. For commercial fisheries, this table should be consistent with Table 2.1.

Field name | Description

MS | Use ISO 3166-1 alpha-3 code e.g. ‘DEU’. See MasterCodeList ‘MS’.

Implementation year | Indicate the year in which the activity will be implemented. Enter one row per implementation year and include all years from the work plan period.

Region | See MasterCodeList ‘Regions’. If information refers to all regions, use code ‘all regions’.

This article is long: the rest is at the official publication.