Embed Size (px)
Citation preview
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 1.0
1. INTRODUCTION ....................................................................................................... 2
2. LEGAL BASIS ............................................................................................................ 2
3. REFERENCES ............................................................................................................ 2
4. SCOPE ......................................................................................................................... 3
5. PROCEDURES ........................................................................................................... 4
5.1. General principles .............................................................................................. 4
5.1.1. Data exchange workflow ..................................................................... 4
5.1.2. Business Rules ..................................................................................... 4
5.1.3. ACDR Report types and their content requirements ........................... 5
5.1.4. Aggregation level, periodicity and submission deadline ..................... 6
5.1.5. Submission of empty reports ............................................................... 6
5.1.6. Data correction .................................................................................... 6
5.2. Reporting of catches still on board .................................................................... 6
5.3. Reporting under landing obligation requirements ............................................. 7
6. DATA MODEL (XSD) IMPLEMENTATION .......................................................... 7
6.1. ACDR Reports ................................................................................................... 7
6.2. Data models ....................................................................................................... 8
6.2.1. ACDR Regional report ........................................................................ 8
6.2.2. ACDR Fishing Category report ........................................................... 9
6.2.3. ACDR Fishing Gear report ................................................................ 10
6.2.4. ACDR Vessel and Regional report .................................................... 11
6.2.5. ACDR Other report ........................................................................... 12
6.3. General Principle Response ............................................................................. 17
7. XML EXAMPLES .................................................................................................... 18
8. CODE LISTS ............................................................................................................ 19
9. CONTACT ................................................................................................................ 19
10. VERSIONING ........................................................................................................... 19
Ref. Ares(2015)6026067 - 23/12/2015
2
1. INTRODUCTION
This document describes the implementation within the EU context of the
UN/CEFACT standard on the exchange of aggregated catch data1.
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 website2.
The Transportation Layer is mandatory for use from 01/01/2016.
2. 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/94.
3. 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: P1000 – 12; Aggregated Catch Data Report (ACDR) domain
(version 0.3.4).
ACDR system - set of Business Rules;
1 UN/CEFACT reference – "P1000 – 12; Aggregated Catch Data Report (ACDR) domain.
2 http://ec.europa.eu/fisheries/cfp/control/codes/index_en.htm
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
4
5. PROCEDURES
5.1. General principles
5.1.1. 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
5.1.2. 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
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 defined3.
The Response message is returned back to the Report provider
containing the information on the correctness and acceptance or
denial of the ACDR Message.
5.1.3. 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:
5.1.3.1. 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.
5.1.3.2. 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.
5.1.3.3. ACDR-VESSEL
This Report type must contain data on SBF catches
regulated by the CCSBT and CJM catches regulated by
SPRFMO.
5.1.3.4. ACDR-FISHING-CAT
This Report type must include data on all catches MS have
obtained within the SFPAs.
5.1.3.5. 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.
6
5.1.4. 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 15th
of each month – for the
catches made during the previous month.
5.1.5. 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 5.1.3.
In case of an empty report the specific part of the ACDR Message
shall be omitted. For an empty report example see paragraph 7.
5.1.6. 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.
5.2. 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.
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.
5.3. 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.
8
6.2. Data models
6.2.1. ACDR Regional report
ACDR Regional report data model
9
6.2.2. ACDR Fishing Category report
ACDR Fishing category report data model
10
6.2.3. ACDR Fishing Gear report
ACDR Fishing Gear report data model
11
6.2.4. ACDR Vessel and Regional report
ACDR Vessel and Regional report data model
12
6.2.5. ACDR Other report
ACDR Other report data model
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
Description Remarks
min max
General
Principle
Basic
Attributes
1 1 Common entity shared by all
ACDR report messages.
Message
Identification
Identifier 1 1 The Global Unique
Identifier of the ACDR
Message
A GUID as defined in the
RFC 4122
Cf.
http://www.guidgenerator.com
to generate example of a valid
identifier.
Creation DateTime 1 1 The date time UTC
value, according to ISO
8601 format, of the
creation of this FLUX
ACDR Message
document.
A UTC date time according to
ISO 8601 format;
e.g. 2008-10-31T15:07:38Z
(milliseconds can be provided
optionally).
General
Principle
Exchange
Document
Info
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.
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.
Editor Type Text 0 1 Free text to describe the
type of report sender
Action
Reason
Text 0 1 The reason of this
ACDR Message.
Free text that can be used for
communicating the reason
why the report is sent.
Example: "final catch figures
validated by inspectors".
Referenced
Message
Identifier 0 1 The identifier of a
referenced ACDR
Message.
A GUID as defined in the
RFC 4122.
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
14
Entity/Field
Name Type
Cardinality
Description Remarks
min max
Catch Report information of every type of
Aggregated Catch Report
message.
Common entity shared by all
ACDR report messages.
Reporter
Identification
Identifier 1 1 The identifier (ISO-3
country code, XEU for
the Commission) of the
Reporting country.
Use Code CR Reporting
Countries code list in MDR.
Attribute listID=
CR_REPORTING_COUNTRI
ES.
Reporting
Period
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.
The start date according to
ISO 8601 format of the period
in which the fish was caught
covered by this report.
e.g. 2008-10-31T00:00:00.
Time part is ignored.
End Date 1 1 The date, time, date time
or other date time value
for the end of this
delimited period.
The end date according to ISO
8601 format of the period in
which the fish was caught
covered by this report.
e.g. 2008-10-31T00:00:00.
Time part is ignored.
Report Sender
ACDR_ Party
1 1 The party owning this
ACDR Message.
Common entity shared by all
ACDR report messages.
Identification Identifier 1 1 FIDES username of a
person submitting the
report.
The User must have the
appropriate rights to submit
catch reports.
Name Text 0 1 Additional details on the
User (usually name).
Optional.
Free text giving more details
on the User submitting the
report.
Specified
Regional
Report
0 * Information contained in
ACDR report
Can be omitted if reporting
empty value (empty report).
A part of ACDR-REGIONAL,
ACDR-FISHING-GEAR and
ACDR-VESSEL reports.
Regional Area Code 1 1 The code defined by
annual TAC and Quotas
regulations and
specifying an area of the
fish stock.
Attribute listID=
QUOTA_LOCATION.
Regional
Species
Code 1 1 The code defined by
annual TAC and Quotas
regulations and
specifying species of the
stock.
Attribute listID=
QUOTA_OBJECT.
15
Entity/Field
Name Type
Cardinality
Description Remarks
min max
Specified
Fishing
Category
Report
0 * Information contained in
ACDR report
Can be omitted if reporting
empty value (empty report).
A part of ACDR-FISHING-
CAT and ACDR-FISHING-
GEAR report models.
Fishing
Category
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.
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.
Specified
Vessel
Identification
1 1 The vessel transport
means specified in this
FLUX ACDR report.
A part of ACDR-FISHING-
CAT and ACDR-VESSEL
report models.
Regional
Identification
Identifier 1 1 An identifier (CFR
number) of the vessel.
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: LUX123456789
Flag State Code 1 1 Flag State's country ISO-
3 code of the vessel.
Use Code CR Reporting
Countries code list in MDR.
Attribute listID=
CR_REPORTING_COUNTRI
ES.
Specified
Fishing Gear
Report
1 1 A part of ACDR-FISHING-
GEAR report model.
FAO Fishing
Gear
Code 1 1 The FAO code
specifying the fishing
gear.
Gear used for fishing,
according to FAO
International Standard
Statistical Classification.
Use Gear Type code list in
MDR. Attribute listID=
GEAR_TYPE.
Specified
Reported
Area
1 * An entity specifying area
where the reported
catches were taken and
landed.
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.
FAO Area Code 1 1 Geographical area
expressed in FAO code,
Use FAO Major Fishing Areas
code list in MDR. Attribute
16
Entity/Field
Name Type
Cardinality
Description Remarks
min max
where reported catches
were taken.
listID=FAO_AREA.
The most existing detailed
FAO area to be provided.
Sovereignty
Water
Code 1 1 Sovereignty Waters,
where fish has been
caught.
Use CR Sovereignty Waters
code list in MDR. Attribute
listID= CR_SOV_WATERS.
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).
Use CR Landing Place code
list in MDR Attribute listID=
TERRITORY.
Quantifies
Reported
Catch
1 * A catch specified for this
ACDR reported area.
Common entity shared by all
ACDR report messages.
Species Code 1 1 Species code, as defined
in FAO, for reported
catch.
Use Species code list in MDR.
Attribute listID=
FAO_SPECIES.
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.
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).
Landing
Indicator
Code 0 1 The code specifying
whether the reported
catch is of the normal
size, undersize,
discarded, fishmeal, etc.
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.
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
Description Remarks
min max
General
Principle
response
Basic
Attributes
1 1
Message
Identification
Identifier 1 1 The Global Unique
Identifier of the ACDR
Message.
A GUID as defined in the
RFC 4122
Cf.
http://www.guidgenerator.com
to generate example of a valid
identifier.
Creation DateTime 1 1 The date time UTC
value, according to ISO
8601 format, of the
A UTC date time according to
ISO 8601 format;
18
Entity/Field
Name DataType
Cardinality
Description Remarks
min max
creation of this FLUX
ACDR Message
document.
e.g. 2008-10-31T15:07:38Z
(milliseconds can be provided
optionally).
Specified
Response
1 1 The business response to
a received ACDR
Message.
Referenced
Message
Identifier 1 1 The identifier of ACDR
Message, to which this
GP Response is sent.
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.
Status Code 1 1 The code specifying the
general status of the
referenced ACDR
Message after the
validation process has
been applied.
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.
Status
Description
Text 1 1 A general textual remark
related to the Status
code.
ACK = Accepted;
NAK = Refused.
Status Details Text 1 1 Detailed description of
the main reason for
rejection.
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);
19
FLUX General Principles Response messages from the European
Commission to MS:
o An accepted message;
o A refused message.
8. CODE LISTS
listID List reference in MDR
ACTION_TYPE Action Type list
CR_REPORTING_COUNTRIES CR Reporting Countries list
QUOTA_LOCATION -
QUOTA_OBJECT -
CR_FISH_CATEGORY CR Fishing Category list
GEAR_TYPE Gear Type list
FAO_AREA FAO Major Fishing Area list
CR_SOV_WATERS CR Sovereign Waters
TERRITORY CR Landing Places
FAO_SPECIES Species list
CR_UNIT CR Units list
CR_LAND_IND CR Landing Indicator
9. CONTACT
10. VERSIONING4
Version Author Date
0.1 MB 06/07/2015
Notes First draft
0.2 MB 22/12/2015
4 Information is for the European Commission internal use only.
20
Notes Update
1.0 MB 23/12/2015
Notes Final adjustments
