5th Regional Observer Programme Intersessional Working Group: Full Annotated Agenda

  • 1. Opening of Meeting

    The Chair of the ROP-IWG, Mr Lucas Tarapik, (Papua New Guinea) will open the meeting and invite the meeting to confirm the draft agenda.

    A copy of the Chairs Communication, of 18 February 2025, related to the Proposed 2025 Workplan can be found here 

  • 2. Introduction and Opening Remarks

    Participants in ROP-IWG05 will be invited to provide brief opening remarks.

  • 3. Revisit Annex 1/1A table presenting some updates to the WCPFC Minimum Standard Data Fields (MSDFs) for observer monitoring on purse seine, longline and pole and line vessels

    The WCPFC21 update paper on intersessional activities of the ROP-IWG (WCPFC21-2024-16) included two attachments that each contains suggested changes to the MSDF:

    •            Annex 1 - paper (SC20-ST-WP-04) had proposed changes to the WCPFC Minimum Standard Data Fields (MSDFs) for observer monitoring on purse seine, longline and pole and line vessels provided by the Secretariat and ROP-IWG participants prior to July 2024. 

    •            Annex 1A – a supplementary paper presenting some additional and supplementary draft suggested amendments to the MSDF, prepared by the ROP-IWG Chair and Secretariat between TCC20 and WCPFC21. 

    The Secretariat has prepared a consolidated version of suggested changes to the MSDF, which were contained in Annex 1 and Annex 1A to the WCPFC21 paper 16 (Working Paper 02 for this meeting)

    • Working Paper 02 Annex A includes the additional suggestions and comments of ROP-IWG participants that were received in 2024.  There are also notes and placeholders to recognize further work is required by the ROP-IWG, for example additional discussions and additional amendments are expected to the data fields for Observer Trip Monitoring Summary, and Species of Special Interest (these data fields will be further discussed under Agenda Item 4).  
    • Working Paper 02 Annex B provides a concise version highlighting the suggested changes to the MSDF only.

    Participants in the virtual meeting will be invited to provide feedback and comments.  The Chair will also lead a discussion on the next steps and planned 2025 programme of work for the review of the WCPFC Minimum Standard Data Fields (MSDFs) for observer monitoring on purse seine, longline and pole and line vessels.

     

  • 4. Developing a standardized solution to use ROP data in the CCFS and CMS process

    The ROP was established pursuant to Article 28 of the Convention “to collect verified catch data, other scientific data and additional information related to the fishery from the Convention Area and to monitor the implementation of the conservation and management measures adopted by the Commission.”  The ROP has at its core, the collection of independent, verified catch and scientific data at-sea which can also be used for compliance purposes in monitoring CCMs’ implementation of CMMs.

    The primary use of ROP data in the Compliance Monitoring Scheme (CMS) to date, has been as an independently collected data source.  Since 2016, ROP data has been used in the online Compliance Case File System (CCFS).  The stated purpose is that the CCFS is to be maintained “as a secure, searchable system to store, manage and make available information to assist CCMs with tracking alleged violations by their flagged vessels.” (CMM 2023-04) A paper that provides further background information on the Use of ROP data in the CMS can be found here.

    There are two topics proposed for discussion under Agenda Item 4.

    • 4.1 Review of Observer Trip Monitoring Summary data fields and current pre-notification process and challenges

      Within the CCFS, there are three types of cases that are based on Observer Trip Monitoring Summary Data:

      • OAI: Observer Obstruction Alleged Infringements which have a clear link to CMM 2018-05 15(g)).

      • POL: Marine Pollution Alleged Infringements which link to marine pollution CMM 2017-04 02 or 03-07.

      • PAI: The remaining ROP Pre-notification data elements (other than alleged observer obstruction incidents (OAI) and marine pollution incidents (POL)) that were answered in the affirmative by a ROP observer on the WCPFC Observer Trip Monitoring Summary.

      The reason that the OAI, POL and PAI cases are notified through the CCFS stems from a previous Commission decision from WCPFC12 (December 2015).  This was the Commission Adopted pre-notification process from observer providers to flag CCMs of possible alleged infringements by their vessels and to coastal State CCMs of possible alleged infringements in their waters” (WCPFC12 Summary Report paragraph 569, Attachment U. This decision tasks the SPC-OFP and the Secretariat to prioritise data entry for the observer trip monitoring data and to facilitate the notification of any affirmative answers on the Observer Trip Monitoring Summary to the responsible flag CCM with a view to providing flag CCMs earlier notification of potential alleged infringements by their vessels. 

      Some current issues identified include, but are not limited to:

      • The remaining Observer Trip Monitoring Summary Data Fields codes presently don’t have a clear link to an obligation in a WCPFC CMM or a specific requirement in the Convention;
      • The Commission has acknowledged the PAI cases are an issue and at WCPFC14 accepted the TCC13 recommendation that TCC not consider the information contained in the ROP Pre-notification List for the purpose of assessing any obligations for which it was relevant, except for those cases related to observer interference or obstruction in future years;
      • Noting the scale of PAI cases in the CCFS, resolving the issue of PAI cases is a priority task for the ROP-IWG in its 2023-2025 workplan;
      • In practice, the current Observer Trip Monitoring Summary Data Fields do not provide sufficient information necessary to support data management procedures used to define if the observed trip should be classified as ROP or non-ROP data.  Consequently, the earlier notification to flag CCMs that was envisaged has not been practical to implement.
      • In 2024, some suggestions were made as part of ROP-IWG discussions of ways to utilise debriefing information in supporting reviews of PAI cases, these are noted in Working Paper 02, Annex A.

      Participants in the virtual meeting will be invited to share views, proposals and comments.  The Chair will lead a discussion on the next steps.

    • 4.2 Considerations for defining scientific interactions for SSI and potential violations of SSI related obligations

      Within the CCFS, there are two types of SSI related cases that are based on ROP set-level data: 

      • SHK: Shark Catch Alleged Infringements. These are Cases for alleged infringements related to retention of oceanic white tip or silky sharks, or shark fining activity identified in ROP observer data (obligations in CMM 2022-04).

        SHK cases are generated where a ROP observer has reported instances during a WCPFC ROP trip where 

        • fishing vessel has caught an oceanic white tip or silky shark as identified by a specific species code (SP_code) in combination with an observed fate code (FATE_code) indicating retention is whole or in part.
        • fishing vessel has caught shark as identified by a species code (SP_code) in combination with an observed fate code (FATE_code) indicating fining activity.

      • CWS: Cetacean and Whale Shark Interactions.  Relevant WCPFC requirements prohibit purse seine vessels from setting if a whale shark or cetacean is sighted prior to the commencement of the set; required reporting of any incidents of unintentional encircling; and guidelines for safe release (obligations in CMM 2011-03 and CMM 2022-04). 

        CWS cases are generated where a ROP observer has reported instances during a WCPFC ROP trip where a cetacean or whale sharks as identified by a specific species code (SP_code) in combination with an observed fate code (FATE_code) indicates an interaction with the fishing vessel’s activity.

      Some current issues identified include, but are not limited to:

      • The Commission has acknowledged that the CWS cases in CCFS are an issue and TCC17 (2021) agreed this data would be excluded from consideration of the current trial process of reviewing the Aggregated Tables in the Compliance Monitoring Scheme (CMS).
      • The CCFS CWS instances currently reflect a recording by the observer of interactions between the vessel and marine mammals or with whale sharks (an observer on a purse seine vessel has reported a cetacean or whale sharks, as identified by a specific species code (SP_code) in combination with an observed fate code (FATE_code)).  Currently the ROP data fields do not permit the observer to categorise the data fields that are inputs to the CCFS to distinguish between interactions where there is no alleged infringement and that are of scientific interest, with those interactions or actions by the crew that could indicate a potential infringement has occurred.
      • As is noted in  Working Paper 02 Annex A, there are a number of other SSI obligations in CMMs (seabirds (CMM 2018-03), sea turtles (CMM 2018-04), mobulids (CMM 2019-05)) and potentially refinements for sharks (CMM 2024-05) and cetaceans (CMM 2024-07), which would facilitate the creation of additional types of observer-initiated cases in the CCFS, but the ROP data fields need to be reviewed to support more clear identification of potential violations of SSI related obligations.  
      • In 2024, some suggestions were made as part of ROP-IWG discussions of data fields that will support the review of implementation of seabird mitigation measures under CMM 2018-03, these are provided in Working Paper 02 Annex A and Annex B.

      Participants in the virtual meeting will be invited to share views, proposals and comments.  The Chair will lead a discussion on the next steps.

  • 5. Review of the Minimum Data Fields for Observer Transhipment Monitoring, including to consider data fields related to Non-Fish Transfers

    The Commission at WCPFC21 in December 2024, tasked the ROP-IWG to discuss adding non-fish transfers to the observer minimum data fields for monitoring transshipment (WCPFC21 Summary Report paragraph 511).  This task stemmed from some discussions around the review of the Transhipment CMM (CMM 2009-06), which recognized the challenges in identifying and understanding these transfers during transhipment and identified that enhanced reporting mechanisms were critical for validating and verifying activities within the Convention Area. 

    Specifically, a proposal was made to the Transhipment IWG during 2024, that Annexes I and III of the Transhipment CMM, that set out information to be included in WCPFC Transhipment Declaration and Notices (Notifications) to the Executive Director should include the following:

    • In Annex 1 declaration - “7. Did non-fish transfer occur? (yes or no”) If yes, provide details of this non-fish transfer, including the exchange of crew (numbers) and provision of supplies between vessels. “
    • In Annex 3 notification – “7. Will non-fish transfers occur? (“Yes” or “No”). If yes, provide details of this proposed non-fish transfer, including the exchange of crew (numbers) and provision of supplies between vessels.”
    • To support this requirement, a definition of non-fish transfer could be included in a footnote which draws on the definition from the North Pacific Fisheries Commission (NPFC) CMM – ““means a transfer of fuel, gear, materials, or other supplies, or a transfer of at least one person, from one fishing vessel to another fishing vessel in the Convention Area”

    The basis for this proposal underlined the importance of verifying instances where carrier and fishing vessels met but no transhipment notification was reported to the Secretariat (i.e. no catch transferred – but where there was potentially a non-fish transfer between vessels). This information should reduce the number of potential compliance enquiries, especially as the Secretariat has developed tools to identify when vessels are in close proximity.

    Participants in the virtual meeting will be invited to share views, proposals and comments on the task of defining non-fish transfers and the supporting data fields that would be added to reflect non-fish transfers in the observer minimum data fields for monitoring transshipment. The Chair will lead a discussion on the next steps.

  • 6. Updating the 2023-2025 ROP-IWG workplan and next steps

    The Chair will lead a discussion to review the 2023-2025 workplan and to consider next steps and phasing for the planned 2025 programme of work, including whether to hold a second virtual meeting before TCC21. 

  • 7. Summary and Close of Meeting

    A Chair’s Summary Report will be prepared as the record of the discussion and outcomes.