Blulefin Tuna Catch and Effort Reports for Pelagic Longline and Purse Seine Vessels

Electronic Monitoring Systems for Atlantic Highly Migratory Species (HMS)

VMS Bluefin catch report info

Blulefin Tuna Catch and Effort Reports for Pelagic Longline and Purse Seine Vessels

OMB: 0648-0372

Document [docx]
Download: docx | pdf

Page 10 -11 of NMFS OLE Southeast Division VMS Forms Requirements document; (10/1/14 version)

General Processing:


  1. Drop down menus are preferred for Area selection (GOM, ATL, NED).

    1. For transmission purposes, GOM = 1, ATL = 2, NED = 3.


  1. Date to be manually entered or drop down menu:



  1. The fields ‘MONTH’ and ‘DAY’, should be limited to two (2) numeric characters each. ‘Month’ and ‘Day’ should be appropriately range checked; 01 - 12 for month and 01 - 31 for day; employ a drop-down date menu, if feasible. The field “YEAR” should be limited to four (4) numeric characters. “Year” should be appropriately range checked; 2014 or higher year.


  1. Set to be manually entered or drop down menu:


    1. Set Number on Trip: (1-60)

      1. Type: Numeric, 1 or 2-Digits

      2. Valid values: 0-9

      3. Range Checks: 1-60


  1. Pelagic Longline or Purse Seine selection with Pelagic Longline reported as “1” and Purse Seine reported as “2”.

    1. If Pelagic Longline selected, number of Hooks must be manually entered:

      1. Number of hooks: (100-5000)

        1. Type: Numeric, 3 to 4-Digits

        2. Valid values: 0-9

        3. Range Checks: 100-9999

    2. If Purse Seine selection, Number of Hooks should default to “0”.



  1. Were there Bluefin interactions on this set?”

    1. If YES block checked, continue with remaining form.

    2. If NO block checked, populate remaining form with zeros.

  1. ALIVE, DEAD, DISCARDED LIVE, DISCARDED DEAD, RETAINED entries:

    1. Type: Numeric, 1 to 3-Digits

    2. Valid values: 0-9

    3. Range Checks: 0-200

    4. Items not entered would populate with “O” for reporting purposes.

    5. TOTAL NUMBERS should add ALIVE entry fields to populate Discarded Alive field, should add DEAD entries to populate Discarded Dead field, and should add NUMBER RETAINED entries to populate Retained field.


Any commas placed in an entry field by user must be stripped out prior to transmission. Fields without a value provided by the vessel should be zero filled when sent to NMFS.


General Processing:


First eight (8) fields are mandatory for the user to fill in and send the form. (Area, Month, Day, Year, Set Number, Pelagic Longline/Purse Seine, Hook Number, Bluefin Interaction).



Vendor Processing/Transmission format:

If the BLUEFIN INTERACTION (Yes/No) is filled with a NO, then remaining fields are not required to be completed and shortened report will be sent as identified below.


(Date, Time Sent, Latitude, Longitude, Area, Date of Set, Set Number, Pelagic Longline/Purse Seine, Number of Hooks, No Bluefin Interactions)


Example: 12/03/2014 16:04:00, 27.7578333,-82.636,1,12/03/2014,1,1,1800,N


If the BLUEFIN INTERACTION (Yes/No) is filled with a YES, then remaining fields are required to be completed and full report will be sent. Fields not manually entered will be populated with a “0” for reporting purposes.


(Date, Time Sent, Latitude, Longitude, Area, Date of Set, Set Number, Pelagic Longline/Purse Seine, Number of Hooks, Yes Bluefin Interactions, < 27 (Alive/Dead), 27 – 47 (Alive/Dead), 47 – 59 (Alive/Dead), 59 – 73 (Alive/Dead), 73 – 81 (Alive/Retained), > 81 (Alive/Retained)


Example: 12/03/2014 16:04:00, 27.7578333,-82.636,1,12/03/2014,1,1,1800,Y,0/0,0/1,1/2,2/0,0/0,1/1

The form name should be FORM.SER.HMS_BLUEFIN.1. Current form transmission and delivery procedures will not change and should follow existing delivery procedures for standard vessel positional data.



File Typeapplication/vnd.openxmlformats-officedocument.wordprocessingml.document
AuthorThomas Warren
File Modified0000-00-00
File Created2021-01-14

© 2024 OMB.report | Privacy Policy