EUROPEAN COMMISSION DIRECTORATE-GENERAL FOR MARITIME AFFAIRS AND FISHERIES. Aggregated Catch Data Report (ACDR) Implementation Document v 1.

Transcription

1 Ref. Ares(2015) /12/2015 EUROPEAN COMMISSION DIRECTORATE-GENERAL FOR MARITIME AFFAIRS AND FISHERIES MEDITERRANEAN AND BLACK SEA Integrated Fisheries Data Management THE INTEGRATED FISHERIES DATA MANAGEMENT PROGRAMME Subject: Aggregated Catch Data Report (ACDR) Implementation Document v INTRODUCTION LEGAL BASIS REFERENCES SCOPE PROCEDURES General principles Data exchange workflow Business Rules ACDR Report types and their content requirements Aggregation level, periodicity and submission deadline Submission of empty reports Data correction Reporting of catches still on board Reporting under landing obligation requirements DATA MODEL (XSD) IMPLEMENTATION ACDR Reports Data models ACDR Regional report ACDR Fishing Category report ACDR Fishing Gear report ACDR Vessel and Regional report ACDR Other report General Principle Response XML EXAMPLES CODE LISTS CONTACT VERSIONING... 19

2 1. INTRODUCTION This document describes the implementation within the EU context of the UN/CEFACT standard on the exchange of aggregated catch data 1. The data exchange covers the ACDR Message (5 different types) sent by the flag State to DG MARE Data warehouse (DWH) and the ACDR Response Message sent back from DG MARE to the flag State. The standard is mandatory for use from 01/01/2014. Messages are exchanged using the Transportation Layer (TL). The TL technical and functional documentation is published on the Master Data Register (MDR) page of the European Commission Fisheries website 2. The Transportation Layer is mandatory for use from 01/01/ LEGAL BASIS The legal basis for the aggregated catch data reporting is the Article 33 of the Council Regulation (EC) No 1224/2009 establishing a Community control system for ensuring compliance with the rules of the common fisheries policy, as amended by Regulation (EU) 2015/812. The detailed implementing rules are specified further in the Commission Implementing Regulation (EU) No 404/2011 laying down detailed rules for the implementation of Council Regulation (EC) No 1224/2009, as amended by Regulation (EU) No 2015/1962 of 28 October 2015, and especially Article 146i. Reporting of aggregated catches made outside the EU waters are regulated by the Article 13 of the Council regulation (EC) No 1006/2008 concerning authorisations for fishing activities of Community fishing vessels outside Community waters and the access of third country vessels to Community waters, amending Regulations (EEC) No 2847/93 and (EC) No 1627/94 and repealing Regulation (EC) No 3317/ REFERENCES The following documents and data structures are directly linked and should be read in connection to this Implementation document: FLUX BRS: P1000 1; General principles (version 0.6.5). FLUX BRS: P ; Aggregated Catch Data Report (ACDR) domain (version 0.3.4). ACDR system - set of Business Rules; 1 UN/CEFACT reference "P ; Aggregated Catch Data Report (ACDR) domain

3 A separate XSD for each of the ACDR Report type subsets of the standard used in the EU context: o FLUX_ACDR_RegionalReport_1p1.xsd; o FLUX_ACDR_FishingCategoryReport_1p1.xsd; o FLUX_ACDR_FishingGearReport_1p1.xsd; o FLUX_ACDR_VesselAndRegionalReport_1p1.xsd; o FLUX_ACDR_OtherReport_1p1.xsd. FLUXGeneralPrinciplesResponse_1p1.xsd a subset of the standard used in the EU context. The documents and code lists specific to this domain are published on MDR page of the European Commission Fisheries website. 4. SCOPE This document covers the exchange of aggregated information between flag State and DG MARE about fish caught by the whole flag State s fishing fleet in the Reporting period. DG MARE provides the ACDR Response explaining the data correctness and the performed validation results. ACDR domain overview diagram 3

4 5. PROCEDURES 5.1. General principles Data exchange workflow The activity diagram describes the normal procedure defined for submitting ACDR Messages from a Flag State (Report Provider) to DG MARE (Report User). ACDR domain: Message Transmission activity diagram Business Rules The process "Validate Report" in the diagram above is a validation process on: 1) XML Validation level: Based on the definition in the XSD, the parser validates the structure and cardinality as well as compliance for mandatory elements of the XML provided. In this validation process, the system reads completely the document transmitted and generates an error when, in 4

5 comparison to what is defined in the XSD. A result with such error implies the entire rejection of the XML transmitted. 2) Business Rules Validation level: a Business Rules Engine validates the content of XML according to, firstly, the General Principles Business Rules definition and, secondly, to all other ACDR Business Rules defined 3. The Response message is returned back to the Report provider containing the information on the correctness and acceptance or denial of the ACDR Message ACDR Report types and their content requirements Depending on species and area where fish was caught, data should be submitted using the data model of the following ACDR Report types: ACDR-REGIONAL This Report type shall contain data of all catches under the annual EU TAC and Quotas regulations, except for catches in Greenland, catches of bluefin tuna (BFT), southern bluefin tuna (SBF) and Chilean jack mackerel (CJM) stocks ACDR-FISHING-GEAR This Report type must contain data on BFT catches regulated by the ICCAT convention, excluding BFT catches made under the framework of SFPAs ACDR-VESSEL This Report type must contain data on SBF catches regulated by the CCSBT and CJM catches regulated by SPRFMO ACDR-FISHING-CAT This Report type must include data on all catches MS have obtained within the SFPAs ACDR-OTHER This Report type must contain data on all other catches MS fishing vessels have obtained, which are not communicated under any other Report type. 3 ACDR system - set of Business Rules document. 5

6 Aggregation level, periodicity and submission deadline The data in report shall be aggregated per month, in which fish was caught. Every month a flag State sends each of 5 different ACDR Report types. Reports should be sent before the 15 th catches made during the previous month. of each month for the Submission of empty reports Empty catch reports for each of 5 different ACDR Report types must be sent in case of non-fishing in the relevant reporting period or for a particular area or species as described in paragraph In case of an empty report the specific part of the ACDR Message shall be omitted. For an empty report example see paragraph Data correction If the Report provider wants to make a correction or a data update for of an earlier submitted and accepted report, the correction report should be submitted. The following rules should be followed: Action Type should be set U (update); Referenced Message Identifier value should contain the Message Identification Identifier of the previously accepted report for the same period and report type. Reports submitted but not accepted should not be considered in this situation. The whole data set should be present in the report, not only the corrected values Reporting of catches still on board The recent amendments of the Control implementing rules (new Article 146i paragraph 3 of the Commission Implementing Regulation 404/2011) stipulate that When a catch report is to be provided in accordance with Article 13(2) of Council Regulation (EC) No 1006/2008, and before the landing takes place, an estimate catch report shall be provided, with the indication "retained on board". A correction with the exact weight and landing place shall be transmitted before the 15th of the month following the landing. The ACDR system allows reporting of fish still on board. In such a case the Landing Place code '*RB' (retained on board) should be used. The report should contain quantities caught during the reference reporting period (month) and still retained on board at the date of reporting. 6

7 When fish is landed or transhipped, the correction (for details see paragraph 5.2) of the catch month s report should be submitted, now reflecting the corrected exact weight and exact Landing Place (country ISO 3-code) or transhipment *TB. After all landings or transhipment have taken place, there should be no *RB quantities remaining in the DWH Reporting under landing obligation requirements The Article 33.2.(a) of the Control Regulation (1224/2009), stipulates that for regulated stocks Member States shall submit aggregated catch quantities including those below the applicable minimum conservation reference size, as a separate entry. For this purpose the data element Landing Indicator' shall be used. The following conditions should be met: The data element is mandatory, when providing data on regulated stocks (Report types ACDR-REGIONAL, ACDR-GEAR, ACDR-VESSEL). For other Report types it is optional; The codes LAN_SOLD (fish caught, landed and sold for human consumption) or LAN_NHUM_S (fish smaller than the conservation reference size caught, landed and sold for purposes other than direct human consumption) is to be provided. 6. DATA MODEL (XSD) IMPLEMENTATION 6.1. ACDR Reports The implementation of the ACDR Data Models should follow the following general constraints at the level of XSD Element attributes: (1) For Code & Identifier DataType: listid or schemeid attribute must be provided if it is not specifically defined in the definition of the element; (2) For DateTime DataType: only xs:datetime choice is used and 'Z' character defining UTC time zone must be set; (3) Measure and Quantity DataType: unitcode attribute should be provided when not correctly explained in the definition. The following paragraphs describe the 5 different data models of various ACDR Messages. 7

8 6.2. Data models ACDR Regional report ACDR Regional report data model 8

9 ACDR Fishing Category report ACDR Fishing category report data model 9

10 ACDR Fishing Gear report ACDR Fishing Gear report data model 10

11 ACDR Vessel and Regional report ACDR Vessel and Regional report data model 11

12 ACDR Other report ACDR Other report data model 12

13 Tables below describes the values that can be used for each fields defined in the ACDR data models (XSD). Entity/Field Name Type Cardinality min max Description Remarks General Principle Basic Attributes Message Identification 1 1 Common entity shared by all ACDR report messages. Identifier 1 1 The Global Unique Identifier of the ACDR Message Creation DateTime 1 1 The date time UTC value, according to ISO 8601 format, of the creation of this FLUX ACDR Message document. General Principle Exchange Document Info A GUID as defined in the RFC 4122 Cf. to generate example of a valid identifier. A UTC date time according to ISO 8601 format; e.g T15:07:38Z (milliseconds can be provided optionally). 1 1 Common entity shared by all ACDR report messages. Action Type Code 1 1 The code specifying the purpose of this ACDR Message. Possible values: C = Create / Original; U = Update / Replace. Editor Type Text 0 1 Free text to describe the type of report sender Action Reason Referenced Message Text 0 1 The reason of this ACDR Message. Identifier 0 1 The identifier of a referenced ACDR Message. Must be either C (create) in case if sending for the first, or U (update) in case if this is an update or the correction of the previously accepted report. Use Action Type code list in MDR. Attribute listid= ACTION_TYPE. Free text that can be used for communicating the reason why the report is sent. Example: "final catch figures validated by inspectors". A GUID as defined in the RFC A GUID number, for which an update is sent. Compulsory if the report is an update (Action Type=U). Aggregated 1 1 Entity contains the general 13

14 Entity/Field Name Type Cardinality min max Description Remarks Catch Report Reporter Identification Reporting Period Identifier 1 1 The identifier (ISO-3 country code, XEU for the Commission) of the Reporting country. information of every type of Aggregated Catch Report message. Common entity shared by all ACDR report messages. Use Code CR Reporting Countries code list in MDR. Attribute listid= CR_REPORTING_COUNTRI ES. 1 1 Common entity shared by all ACDR report messages. Start Date 1 1 The date, time, date time or other date time value for the start of this delimited period. End Date 1 1 The date, time, date time or other date time value for the end of this delimited period. Report Sender ACDR_ Party 1 1 The party owning this ACDR Message. Identification Identifier 1 1 FIDES username of a person submitting the report. Name Text 0 1 Additional details on the User (usually name). Specified Regional Report 0 * Information contained in ACDR report Regional Area Code 1 1 The code defined by annual TAC and Quotas regulations and specifying an area of the fish stock. Regional Species Code 1 1 The code defined by annual TAC and Quotas regulations and specifying species of the stock. The start date according to ISO 8601 format of the period in which the fish was caught covered by this report. e.g T00:00:00. Time part is ignored. The end date according to ISO 8601 format of the period in which the fish was caught covered by this report. e.g T00:00:00. Time part is ignored. Common entity shared by all ACDR report messages. The User must have the appropriate rights to submit catch reports. Optional. Free text giving more details on the User submitting the report. Can be omitted if reporting empty value (empty report). A part of ACDR-REGIONAL, ACDR-FISHING-GEAR and ACDR-VESSEL reports. Attribute listid= QUOTA_LOCATION. Attribute QUOTA_OBJECT. listid= 14

15 Entity/Field Name Type Cardinality min max Description Remarks Specified Fishing Category Report Fishing Category Specified Vessel Identification Regional Identification 0 * Information contained in ACDR report Code 1 1 The code specifying a fishing category, such as the type of vessel, the type of fishing activity or the fishing gear deployed. 1 1 The vessel transport means specified in this FLUX ACDR report. Identifier 1 1 An identifier (CFR number) of the vessel. Flag State Code 1 1 Flag State's country ISO- 3 code of the vessel. Specified Fishing Gear Report FAO Fishing Gear Specified Reported Area Can be omitted if reporting empty value (empty report). A part of ACDR-FISHING- CAT and ACDR-FISHING- GEAR report models. Fishing Category code list in MDR (data based on FAP2 application). Attribute listid= CR_FISH_CATEGORY. Only specific categories (BFT_TARGET, BFT_SPORT or BFT_BYCATCH) can be used in ACDR-FISHING-GEAR report. A part of ACDR-FISHING- CAT and ACDR-VESSEL report models. Country alpha 3 ISO code followed by an identifying series (nine characters). Where a series has fewer than nine characters, additional zeros must be inserted on the left hand side. Example: LUX Use Code CR Reporting Countries code list in MDR. Attribute listid= CR_REPORTING_COUNTRI ES. 1 1 A part of ACDR-FISHING- GEAR report model. Code 1 1 The FAO code specifying the fishing gear. Gear used for fishing, according to FAO International Standard Statistical Classification. 1 * An entity specifying area where the reported catches were taken and landed. FAO Area Code 1 1 Geographical area expressed in FAO code, Use Gear Type code list in MDR. Attribute listid= GEAR_TYPE. Entity must be repeated for each combination of the values in each data element of this entity. Common entity shared by all ACDR report messages. Use FAO Major Fishing Areas code list in MDR. Attribute 15

16 Entity/Field Name Type Cardinality min max Description Remarks Sovereignty Water where reported catches were taken. Code 1 1 Sovereignty Waters, where fish has been caught. Landing Place Code 1 1 Place where the fish has been landed (country ISO-3 code) or whether it has been transhipped (*TB) or retained on board (*RB). Quantifies Reported Catch 1 * A catch specified for this ACDR reported area. Species Code 1 1 Species code, as defined in FAO, for reported catch. Quantity Measure 1 1 The quantity of fish, according to the unit attribute used to declare catches. Possible values for unit attribute: TNE tonnes; KG kilograms; C62 number of fish. Landing Indicator Code 0 1 The code specifying whether the reported catch is of the normal size, undersize, discarded, fishmeal, etc. listid=fao_area. The most existing detailed FAO area to be provided. Use CR Sovereignty Waters code list in MDR. Attribute listid= CR_SOV_WATERS. Use CR Landing Place code list in MDR Attribute listid= TERRITORY. Common entity shared by all ACDR report messages. Use Species code list in MDR. Attribute listid= FAO_SPECIES. Use CR Units code list in MDR. Attribute listid= CR_UNIT. For ACDR-REGIONAL, ACDR-FISHING-GEAR and ACDR-VESSEL reports the unit code should be the one in which the catch limits (quotas) are defined (TNE or C62). In case of TNE, the quantity must contain no more than 3 decimals (0.000). Use CR Landing Indicator code list in MDR. Attribute listid= CR_LAND_IND. Mandatory in ACDR- REGIONAL, ACDR- FISHING-GEAR and ACDR- VESSEL reports. Mandatory in ACDR- FISHING-CAT report when reporting catches in Morocco. 16

17 6.3. General Principle Response The General Principle response message is sent as a reply to any of the received ACDR Message. The following diagram describes the General Principle Response data model. FLUX General Principles Response XSD data model The table below describes for each fields defined in the FLUX GP Response Data Model (XSD) the values that can be used. Entity/Field Name DataType Cardinality min max Description Remarks General Principle response Basic Attributes Message Identification 1 1 Identifier 1 1 The Global Unique Identifier of the ACDR Message. Creation DateTime 1 1 The date time UTC value, according to ISO 8601 format, of the A GUID as defined in the RFC 4122 Cf. to generate example of a valid identifier. A UTC date time according to ISO 8601 format; 17

18 Entity/Field Name DataType Cardinality min max Description Remarks Specified Response Referenced Message creation of this FLUX ACDR Message document. 1 1 The business response to a received ACDR Message. Identifier 1 1 The identifier of ACDR Message, to which this GP Response is sent. Status Code 1 1 The code specifying the general status of the referenced ACDR Message after the validation process has been applied. Status Description Text 1 1 A general textual remark related to the Status code. Status Details Text 1 1 Detailed description of the main reason for rejection. e.g T15:07:38Z (milliseconds can be provided optionally). GUID as defined in the RFC 4122 of the FLUX ACDR Message previously sent. In case, the ACDR Message does not contain the identifier, the Transportation Layer's identifier is used. Possible values: ACK = No error found and message is accepted; NAK = Error(s) found and message rejected. If at least one Business Rule with ERR message fails, the whole ACDR Message is rejected. ACK = Accepted; NAK = Refused. The link to the ACDR report validation results webpage in Catch Reporting user interface is provided. 7. XML EXAMPLES The following examples are generated and available on CIRCABC (MARE / IFDM DEL / Library / Business Layer / ACDR V1): FLUX ACDR Messages from MS to the European Commission: o Regional Report (create message and correction message); o Fishing Category Report (create message); o Fishing Gear Report (create message); o Vessel and Regional Report (create message); o Other Report (create message and empty message); 18

19 FLUX General Principles Response messages from the European Commission to MS: 8. CODE LISTS o An accepted message; o A refused message. listid ACTION_TYPE CR_REPORTING_COUNTRIES List reference in MDR Action Type list CR Reporting Countries list QUOTA_LOCATION - QUOTA_OBJECT - CR_FISH_CATEGORY GEAR_TYPE FAO_AREA CR_SOV_WATERS TERRITORY FAO_SPECIES CR_UNIT CR_LAND_IND CR Fishing Category list Gear Type list FAO Major Fishing Area list CR Sovereign Waters CR Landing Places Species list CR Units list CR Landing Indicator 9. CONTACT MARE-D4-IFDM@ec.europa.eu 10. VERSIONING 4 Version Author Date 0.1 MB 06/07/2015 Notes First draft 0.2 MB 22/12/ Information is for the European Commission internal use only. 19

20 Notes Update 1.0 MB 23/12/2015 Notes Final adjustments 20