====================================================================== ===== FLUX Readme first document ===== ===== ===== ===== Version: 1.1 ===== ===== Author: E. HONORE ===== ===== Date: March 2017 ===== ====================================================================== Copyright (C) UN/CEFACT (2016). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to UN/CEFACT, except as needed for the purpose of developing UN/CEFACT specifications, in which case the procedures for copyrights defined in the UN/CEFACT Intellectual Property Rights document must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by UN/CEFACT or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and UN/CEFACT DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. ====================================================================== ===== Version changes ===== ====================================================================== V1.1: Included in CCL16B Changes in the following sub-domains: - P1000-2: Vessel v3.2: > Avoid repetition of Validator ID for every Vessel Events provided. - P1000-3: Fishing Activity (FA) v1.1: > Adding new Assoc. from FA Report Document -> Related Flux Location for providing vessel position when declaring a fishing activity. > Changing vessel details as optional in case of deletion report. > Adding new Assoc. from FA Catch -> Specified FLAP Document to allow catches being reported under different licenses within one haul. > Adding new Assoc. from FLUX Characteristic -> Specified Flux Location to provide a positions as a type of FLUX Characteristic. - P1000-5: Sales v1.1: > Changing sales report details as optional in case of deletion report. > Changing cardinality of Sales Document ID to allow providing an invoice number as Sales document identifier. > Adding new Qualified Assoc. (origin;destination) to FLUX Location for specifying destination & origin Location in Sales Document. - P1000-9: Fishing Licence; Authorizations & Permits (FLAP) v1.1 > Adding new elements in Contact Party entity for specifying Applicant birth date & place. v1.0: Included in CCL15B. Based on the following sub-domains BRS: - P1000-1: General Principles v2.1 - P1000-2: Vessel v3.1 - P1000-3: Fishing Activity (FA) v1.0 - P1000-5: Sales v1.0 - P1000-7: Vessel Position v2.0 - P1000-9: Fishing Licence; Authorizations & Permits (FLAP) v1.0 - P1000-10: Master Data Management v2.0 - P1000-12: Aggregated Catch Data Report (ACDR) v2.0 ====================================================================== ===== Preamble ===== ====================================================================== This file aims to introduce the principles of the FLUX (Fisheries Language for Universal eXchange) standard and help to read the different Bussiness Requirements Specification (BRS) documents associated to the description of the standard. The first objective of the FLUX standard is to facilitate the exchange of information related to the management and the control of fisheries. For doing that, the project aims: • to detail and standardise the description of each and any data element needed; • to standardise the grouping of those data elements in messages required by the business for exchanging data between parties. ====================================================================== ===== Logical domain structure & documents list ===== ====================================================================== FLUX standard is based on individual stand-alone business modules that allow parties to implement only the modules they need. The UN/CEFACT standardization approach guarantees that modules are compatible. Each business domain is an understanding and explanation of information and behaviors in the specified problem domain. Each sub-domains have been identified and numbered as follows: P1000 – 1; General Principles (this document should be read prior to all others!): this document describes generalities common to all other specific sub-domains. P1000 – 2; Vessel: The vessel domain contains all information related to the identification and the description of the vessel itself. P1000 – 3; Fishing Activity: Contains all information related to a fishing trip. This domain includes all data concerning landings of fish. A transshipment is considered as a special “landing” involving a second vessel and is also included in this domain. P1000 – 4; Not Allocated (NA) yet! P1000 – 5; Sales: Sales: The sales domain includes all transmission of information concerning first sales of fish since a landing operation, as well as all information concerning transportation of fish between landing and first sale. P1000 – 6; Not Allocated (NA) yet! P1000 – 7; Vessel Position: Contains all information exchanges related to the position of the vessel. P1000 – 8; Not Allocated (NA) yet! P1000 – 9; Fishing Licence; Authorisation & Permit: Includes national as well as international fishing licences, authorisations and permits. P1000 – 10; Master Data Management: support domain for exchanging information about list of code. P1000 – 11; Not Allocated (NA) yet! P1000 – 12;Aggregated Catch Data Report: This domain describes the catch data, which was originally gathered from vessels by Flag States, which is aggregated and exchanged with International parties.