0515 Supporting Statement BF36 resub 031116

0515 Supporting Statement BF36 resub 031116.docx

Alaska Interagency Electronic Reporting System (IERS)

OMB: 0648-0515

Document [docx]
Download: docx | pdf


SUPPORTING STATEMENT

ALASKA INTERAGENCY ELECTRONIC REPORTING SYSTEM (IERS)

OMB CONTROL NO. 0648-0515



This requests revision of this information collection due to an associated rule [RIN 0648-BF36].


The Magnuson-Stevens Fishery Conservation and Management Act (Magnuson-Stevens Act)

16 U.S.C. 1801 et seq. authorizes the North Pacific Fishery Management Council to prepare and amend fishery management plans for any fishery in waters under its jurisdiction. National Marine Fisheries Service (NMFS), Alaska Region manages the crab fisheries in the waters off the coast of Alaska under the Fishery Management Plan for Bering Sea and Aleutian Islands Crab. NMFS manages groundfish under the Fishery Management Plan (FMP) for the Groundfish Fishery of the Bering Sea and Aleutian Islands and the Fishery Management Plan for Groundfish of the Gulf of Alaska (FMPs). Regulations implementing the FMPs appear at

50 CFR parts 679 and 680.


The Interagency Electronic Reporting System (IERS) is the result of a partnership between NMFS, Alaska Department of Fish and Game (ADF&G), and International Pacific Halibut Commission (IPHC). IERS minimizes the burden and maximizes the utility of fisheries information created, collected, maintained, used, disseminated, and retained. The use of IERS incorporates the goals of the Government Paperwork Elimination Act by ensuring that information technology is acquired, used, and managed to improve performance of agency missions, including the reduction of information collection burdens on the public.


The IERS provides the Alaska fishing industry with a consolidated electronic means of reporting production and landings of commercial fish and shellfish to multiple management agencies. eLandings and seaLandings are components of IERS and provide the user with the same benefits only in a different way. Some of the benefits of using IERS include: improved data quality, automated processing of data, improved process for correcting or updating information, availability of more timely data for fishery managers, an electronic record of landings and production that may be extracted by processors and agency staff, and reduction of duplicative reporting of similar information to multiple agencies.


eLandings. A shoreside operation is one in which a shoreside processor or stationary floating processor (SFP) is required to have a Federal Processor Permit (FPP) and that receives groundfish from a catcher vessel issued a Federal Fisheries Permit (FFP). eLandings is used by shoreside processors and SFPs and is accessed over the Internet at http://elandings.alaska.gov by logging on to the eLanding system online.

seaLandings. An at-sea operation is a catcher/processor, mothership, or Community Quota Entity floating processor that is issued an FFP and that receives groundfish from catcher vessels required to have an FFP. seaLandings is accessed through desktop stand-alone software to submit landing reports, production reports, and eLogs by email. Both systems use the same registration process.



Either eLandings or seaLandings. A person who is issued a Registered Buyer permit and who receives Individual Fishing Quota (IFQ) halibut or IFQ sablefish from an IFQ permit holder or who receives Western Alaska Community Development Quota (CDQ) halibut from a CDQ permit holder at any time during the fishing year may use either of these applications.


JUSTIFICATION


1. Explain the circumstances that make the collection of information necessary.


This action requires that the operator of a catcher/processor placed in the partial observer coverage category submit a catcher/processor landing report. This is a new reporting requirement created for this program. The landing report would be generated through eLandings by consolidating the daily production reports for the period the vessel operator defines as the fishing trip for purposes of observer coverage.


2. Explain how, by whom, how frequently, and for what purpose the information will be used. If the information collected will be disseminated to the public or used to support information that will be disseminated to the public, then explain how the collection complies with all applicable Information Quality Guidelines.


a. Catcher/processor Landing Report [NEW]


The operator of a catcher/processor placed in the partial observer coverage category must use eLandings or other NMFS-approved software to submit a catcher/processor landing report to NMFS for each fishing trip conducted while that catcher/processor is in the partial observer coverage category.


NMFS would use information from the catcher/processor landing report to link catch data with observer data, to determine how to appropriately assign at-sea discard rates and PSC rates to unobserved catcher/processors in the partial observer coverage category, and to monitor compliance with the requirement for catcher/processors placed in the partial observer coverage category to log all fishing trips in ODDS.


The landing report is generated through eLandings by consolidating the daily production reports for the period the vessel operator defines as the fishing trip for purposes of observer coverage. NMFS uses information from the catcher/processor landing report to link catch data with observer data, to determine how to appropriately assign at-sea discard rates and prohibited species catch (PSC) rates to unobserved catcher/processors in the partial observer coverage category, and to monitor compliance with the requirement for catcher/processors placed in the partial observer coverage category to log all fishing trips in ODDS.


The catcher/processor landing report must be submitted online at the Alaska Region Web site at http://alaskafisheries.noaa.gov.


Deadline: The operator of a catcher/processor placed in the partial observer coverage category must submit a catcher/processor landing report to NMFS by 2400 hours, A.l.t., on the day after the end of the fishing trip.

Approximately nine vessels could be affected by this action. Three of these vessels are currently in partial coverage and would be expected to continue to qualify for partial coverage. It is estimated that approximately six new vessels would qualify for partial coverage. It is expected that all of these newly qualified vessels would choose partial coverage for the upcoming fishing year.


Catcher/processor Landing Report

ADF&G number

ADF&G Gear Code

Crew Size

Number of Observers onboard

Date fishing began

Days fished

Date of landing

ODDS trip number (not required)

Port of landing (FCP for floating catcher processors)

Partial delivery (if applicable)

IFQ reported manually- yes or no (if applicable)

ADF&G Processor Code

Federal Permit Number

Registered buyer number (if applicable)

CFEC permits

Management program

Management program ID

NMFS ID and IFQ permits (if applicable)

State statistical areas

Itemized catch information

Species

Weights

condition and disposition codes

IFQ report (if applicable)


Catcher/processor Landing Report, Respondent

Number of respondents

Total annual responses

Frequency of response = 1

Total burden hours (4.5)

Time per response = 30 minutes

Total personnel cost ($37/hr x 5)

Total miscellaneous cost

Online 9 x $0 = 0

9

9


5 hr


$185

$0


Catcher/processor Landing Report, Federal Government

Total annual responses

Total burden hours

Total personnel cost

Total miscellaneous cost

0

0

0

0




b. Registration, eLandings or seaLandings processor [UNCHANGED]


A User is an individual within a processor who is authorized and designated to use a User account. Before using the IERS system to report landings, production, discard, and disposition data, the User must request authorization to use the system, reserve a unique User ID, and obtain a password by using the Internet to complete the eLandings Processor Registration. Prior to obtaining authorization to use the eLandings or seaLandings system, a User must establish an operation account.


An individual User can be associated with one or more operation(s) by having the Administrative user on the account add their unique UserID to each operation. Information collected on registration is necessary to identify the participant and to provide authorization for the participant to use eLandings or seaLandings.


To register for an operation or a sub-operation, the User must use the Internet to register a new operation and to complete the online User Agreement Form at https://elandings.alaska.gov/elandings/Register, print, and sign for each new operation or sub-operation, including tender interface.


The User’s signature on the User Agreement Form confirms that the User agrees to the following terms:


♦ To use eLandings or seaLandings access privileges only for submitting legitimate fishery

landing reports;


♦ To safeguard the UserID and password to prevent their use by unauthorized persons; and


♦ To ensure that the User is authorized to submit landing reports, production reports, and

eLogs for the processor permit number(s) listed.


The User must print and submit the signed copy of the User Agreement Form


By mail to: NMFS Sustainable Fisheries Division

eLandings Registration

P.O. Box 21668

Juneau, AK 99802-1668


By fax to: 907-586-7131, Attn: eLandings Registration


By delivery to: NMFS Sustainable Fisheries Division

eLandings Registration

709 West Ninth Street, Suite 401

Juneau, AK 99801


Upon receipt of the registration information, eLandings verifies that all of the required information is provided in the correct format, and that the requested UserID is not already in use.


Once registered, the User is not required to register again unless ownership changes, because that information is autofilled in subsequent reports by eLandings and seaLandings. The processor may apply for different operations and sub-operations using the same processor identification. Confirmation will be emailed to the User to indicate that the User’s account is enabled. New ownership requires a new Federal permit and ADF&G processor code and must be registered.


The eLandings system provides each user a user profile where they can edit their user information and preferences. The user profile allows the User to set a number of preferences that affect how data and pages are displayed.


Create an entirely new operation

Operation type

Operation name

ADF&G Processor code

Federal permit number

Registered Buyer number

Registered crab receiver number

Port

Vessel ADF&G vessel number

Vehicle license number (for buying stations)

Physical Operation (for custom processing operation)



eLandings processor registration, Respondent

Number of respondents

Total annual responses

Frequency of response = 1

Total burden hours

Time per response = 15 minutes

Total personnel cost ($37/hr x 3 )

Total miscellaneous cost

Photocopy = 0.05 x 12 = 0.60

Postage = 0.45 x 12 = 5.40

12

12

3 hr


$111

$6




eLandings processor registration, Federal Government

Total annual responses

Total burden hours

Time per response = 15 minutes

Total personnel cost ($37/hr x 3)

Total miscellaneous cost

12

3 hr


$111

0


c. Catcher/processor eLog [UNCHANGED]


NMFS developed the eLog software for eLandings and separate eLog software for seaLandings; use of an eLog is required for processors under certain programs. Currently, the eLog in seaLandings is available for trawl, longline, and pot gear catcher/ processors. Daily eLog entries are submitted to NMFS from seaLandings via email with production or landing report transmissions. Instructions for eLandings, including the eLog are at https://elandings.atlassian.net/wiki/display/doc/eLandings+User+Manual. Instructions for seaLandings, including the eLog are at https://elandings.atlassian.net/wiki/display/doc/seaLandings+User+Manual.


NMFS expects that vessel operators not required to use the eLogs will actually prefer to use eLogs over the paper daily cumulative processing logbooks (DCPLs) because the electronic features generally make recordkeeping and reporting easier for vessel crew. The eLogs increase the speed and accuracy of data transmission to NMFS and assist in accurate quota monitoring.


Before using the eLog to report landings, production, discard, and disposition data, the User must register the eLog as a sub-operation through eLandings or seaLandings. All of the eligible catcher/processors currently use eLandings to submit production reports.


The catcher/processor eLog replaces the paper catcher/processor trawl DCPL and paper catcher/processor longline and pot DCPL. The trawl eLog is required for trawl catcher/processors in the American Fisheries Act fleet, trawl catcher/processors that are fishing CDQ pollock in the Bering Sea, and trawl catcher/processors participating in the rockfish fishery. The operator of some catcher/processors must use a NMFS-approved catcher/processor longline and pot gear eLog to record and report fishery information.


eLogbook

Voyage Information

Operator Name

Crew Size

Start Date

Primary Observer Cruise #

Primary Observer Name

Secondary Observer Cruise #

Secondary Observer Name

Gear Code

Go Active date (the day fishing activity began)

Go Inactive date

Comments - Text or Coded

Moved To Avoid Salmon and enter the time of the haul deploy in which you moved.

Haul Information

Haul Number will autofill

Gear deploy time in military format

Target species.

Begin latitude & begin longitude.

Management Program

Haul Retrieval

Gear retrieval time

End latitude & end longitude

Federal reporting area will autofill

Special area (COBLZ or RKCSA) will autofill

Average sea depth

Average gear depth

Hail weight

Catch Information

IR/IU Species & Salmon PSC

Species Code of IR/IU catch (Pacific cod and pollock)

Weight in metric tons

Disposition code

PSC and discard disposition

Salmon PSC in number of animals

Viewing and Printing Logbook pages

seaLandings creates and saves a PDF in C:\Program Files\seaLandings\reports of each logbook page to view

and print an individual day or a date range

Use Adobe Acrobat to view all the pages in the PDF file and print all pages.

Saving the eLog

every time you click on an "Ok" button in the eLog, the program automatically saves your work.

Submitting the eLog

Go to Reporting...Transmit Reports. Click on the Transmit button to create a zip file and send

Open email program, address it to [email protected], attach the transmission file, and send.

When receive the receipt, open seaLandings program and process it



Catcher/processor eLog, Respondent

Total number of respondents

Longline or pot gear = 33

Trawl gear = 61

Total annual responses (203 x 94)

Average 200 active (fishing or processing) days

Average 3 inactive days

Total Burden Hours (4723.5)

Time per active response (15 min) x 200 x 94 = 4700

Time per inactive response (5 min) x 3 x 94 = 23.5

Total personnel cost

Cost to maintain eLog ($37/hr x 4724)

Total Miscellaneous Cost

94



19,082



4,724 hr



$174,788


0


Catcher/processor eLog, Federal Government

Total annual responses

Total Burden Hours (1590.17)

Time per response (5 min x 19082)

Total Personnel cost ($37/hr x 1590)

Total Miscellaneous Cost

19,082

1,590 hr


$58,830

0


d. Mothership eLog [UNCHANGED]


The operator of a mothership that is required to have an FFP under § 679.4(b) must use a combination of NMFS-approved mothership eLog and seaLandings to record and report daily processor identification information, delivery information, groundfish production data, and groundfish and PSC data.


In addition, motherships must use a NMFS-approved eLog to daily record and report the results and timing of daily scale tests to NMFS. The respondent must enter the following information from all scale tests, including failed tests, within 24 hours of the testing using the eLog.


Daily flow scale test information entered into eLog

Time of test

Platform scale weight (kg)

Flow scale weight (kg)

Percent error

Comments (optional)



Mothership eLog, Respondent

Total number of respondents

Total annual responses (203 x28)

Average 200 active (receiving or processing) days

Average 3 inactive days

Total Burden Hours

Time per active response (15 min x 200 x 28 = 1400)

Time per inactive response (5 min x 3 x 28 = 7)

Total personnel cost ($37/hr x 1407)

Miscellaneous cost

28

5,684



1,407 hr



$ 52,059

0


Mothership eLog, Federal Government

Total annual responses

Total Burden Hours

Time per response (5 min x 28 = 2.33)

Total Personnel cost ($37/hr x 2)

Total Miscellaneous Cost

28

2


$74

0


e. eLandings or seaLandings landing report [UNCHANGED]


A landing report records the initial or first exchange of seafood product from the harvester to a second party. The second party may be a buyer, receiver, processor, or expediter. Information collected on a landing report is needed to identify the participant, to monitor the deliveries to the facility, to record discard and disposition of species, and for management of various fisheries. The User must be registered and activated to create a landing report in the eLandings or seaLandings system.


Information collected on a landing report is needed to identify the participant, to monitor the deliveries to the facility, record discard and disposition of species, and for management of various fisheries.


From the registration records, eLandings or seaLandings autofills some of the information required to create a landing report and production report. The User must review the User information and autofilled operation information before beginning the new report to ensure that they are accurate for the landing that is taking place, and to correct or modify any appropriate elements.


In addition to the autofilling of certain fields from the registration process, another time-saving feature is available in the Alaska Commercial Fisheries Entry Commission (CFEC) permit card. A CFEC permit is required by the State. The State of Alaska requires that any vessel involved in any fishing activity, catching, processing, or transshipping of raw product must have a CFEC permit. Every respondent who uses eLandings or seaLandings must possess a State or Federal permit.


The CFEC permit cards have a magnetic stripe embedded with permit information that can be used with the eLandings and seaLandings to facilitate more efficient electronic capture of CFEC permit data. A respondent can enter CFEC permit information into the eLandings system by swiping the card through a magnetic stripe card reader. Magnetic stripe card readers can be purchased as an add-on to most contemporary computers and are available for purchase at most computer and electronic stores and Internet sites. The eLandings system does not require the purchase and use a magnetic stripe card reader.


The parties to the information must acknowledge the accuracy of the printed reports by signing them and entering date signed. If the mag-strip reader is used, no imprint is necessary.


eLandings/seaLandings landing report, Respondent

Number of respondents

37 groundfish motherships

58 groundfish shoreside processors or SFPs

Total annual responses

37 x (200 + 15 as Registered Buyer (RB) or Registered Crab Receiver (RCR)) fishing days = 7,955 MS days/year

58 x (200 + 15 as RB or RCR) fishing days = 12,470 SS/SFP days/year

Total burden hours (3404.16)

complete & print receipts (5 min x 20425 = 1702..08)

electronically submit (5 min x 20425 = 1702..08)

Total personnel cost ($37/hr x 3404)

Total miscellaneous cost (1021.25)

Internet = 0 x 20,425 = 0

Copies = 0.05 x 20,425 = 1021.25

95



20,425




3,404 hr



$125,948

$1,021



eLandings/seaLandings landing report, Federal Government

Total annual responses

Total burden hours

Total personnel cost

Total miscellaneous cost

0

0

0

0


e. eLandings or seaLandings production report [UNCHANGED]


The eLandings and seaLandings production reports are required for groundfish and are additional to the landing reports. Information collected on a production report is necessary to identify the participant; to monitor the discards and disposition product; and to monitor the product leaving the facility. All of the eligible catcher/processors currently submit production reports through eLandings.


To create an eLandings production report, the User must login to the eLandings Internet location at: http://elandings.alaska.gov. To create a seaLandings production report, the User must login to seaLandings software. User must be a registered and activated User.




eLandings & seaLandings production report, Respondent

Number of respondents

37 groundfish mothership

94 groundfish catcher/processors

58 shoreside and SFPs

Total annual responses

At-sea: 14,378

Shoreside: 10,048

Total burden hours (2035.5)

Burden to complete & print receipts

At-sea or shoreside = 5 minutes x 24,426

Total personnel cost ($37/hr x 2036)

Total miscellaneous cost (1221.3)

Photocopy = 0.05 x 24426 = 1221.30

Internet = 0 x 24426 = 0

189




24,426



2,036 hr



$75,332

$1,221



eLandings production report, Federal Government

Total annual responses

Total burden hours

Total personnel cost

Total miscellaneous cost

0

0

0

0


g. Catcher vessel pilot trawl eLog [UNCHANGED]


A pilot electronic logbook for a catcher vessel using trawl gear was created for use by selected vessels during a pilot fishery project to replace the trawl daily fishing logbook (DFL) for a limited time. While not designed by NMFS, the pilot eLog includes computer data entry and daily printed paper copies for viewing by authorities. The information recorded in the pilot eLog is submitted to NMFS through a processor of the catcher vessel’s choice on a disc at the end of each fishing trip. An estimated 14 catcher vessels still use this electronic method instead of the DFL. The catcher vessel operator using the pilot eLog is not required to submit quarterly logsheets to NMFS. The estimated time for an operator to complete the pilot eLog is about the same as completion of the DFL.


The voluntary catcher vessel eLog is still in use today but does not require any registration, because no additional participants may volunteer to use the software. This software is mostly outdated and does not work with eLandings. The software is minimally maintained by private industry. Currently, NMFS is working on replacement software that could be used by either catcher vessels using trawl gear. When that software becomes available, a catcher vessel trawl eLog will be required and this pilot eLog will be removed.


Catcher Vessel trawl gear eLog

Identification

Page number

Date

Vessel name and ADF&G vessel registration number

Federal fisheries permit number

Name and signature of operator

If inactive, enter start date, end date, and reason for inactivity

Gear type

Federal reporting area of catch

Whether harvest occurred in COBLZ or RKCSA

Number of observers onboard

Name and cruise number of each observer aboard

Crew size

If in a separate management program, mark appropriate box and enter identification number

Catch by haul information

Haul number

Time and begin position of gear deployment

Date, time, and end position of gear retrieval

Average sea depth and average gear depth

Target species code

Hail weight (lb or mt)

Discard/disposition information

Whether deliveries are unsorted cod ends or presorted at sea

If presorted at sea, enter discard/disposition species information

whether records in pounds or metric tons

daily total, balance forward, and cumulative total since last delivery

species and product codes

Delivery information

Delivery date

ADF&G fish ticket number

Recipient’s name and ADF&G processor code



Catcher vessel trawl eLog, Respondent

Number of respondents

Total annual responses

Average 34 active days x 14 = 476

Average 3 inactive days x 14 = 42

Total burden hours (146.3)

Time/active response

(18 min) x 476 = 142.8

Time for inactive response

(5 min) x 42 = 3.5

Total personnel cost ($37/hr x 146)

Total miscellaneous cost

14

518



146 hr





$5,402

0


Catcher vessel trawl eLog, Federal Government

Total annual responses

Total burden hours (25.9)

Review, data entry, and filing quarterly = 3 min

Total personnel cost ($37/hr x 26)

Total miscellaneous cost

518

26 hr


$962

0


h. Tender Interface [UNCHANGED]


The buying station or tender interface (also referred to as tLandings) is a voluntary process used with eLandings and seaLandings. The tLandings was created by ADF&G to allow processors to receive electronic landing files created on board associated tenders. Upon completion of receipt of deliveries from catcher vessels, the operator of a tender will provide the electronic landing reports to the processor directly from a thumb drive or by email. When the processor operator receives the landing reports on a thumb drive, the landing reports may be downloaded directly to the processor’s database through eLandings, which allows the processor to have immediate access to the data.

Although not required by NMFS, the tender interface is reportedly used by all processors to receive information from tenders and the buying station report is no longer used. The buying station report was operationally replaced by tLandings accessed through eLandings.


Tender Interface, Respondent

Number of respondents

Tenders 150

Land-based buying stations 25


Total annual responses

Responses per respondent: 10

Total burden hours (670.83)

Time/active response

(23 min) x 1750 = 670.83

Total personnel cost ($37/hr x 671)


Total miscellaneous cost

175




1750



671 hr



$24,827


0


Tender Interface, Federal Government

Total annual responses

Total burden hours

Total personnel cost

Total miscellaneous cost

0

0

0

0


i. Temporary Interruption from Internet or Computer (UNCHANGED)


A User who for any reason is unable to properly submit a landing report through eLandings or seaLandings must enter the information onto a temporary interim form for reference until network connections are restored.


NMFS recommends the User wait for an hour or so after the Internet has disconnected; most disconnects last less than an hour. However, when the Internet connection is not available for a longer time and a landing includes IFQ halibut, IFQ sablefish or IFQ crab, the appropriate temporary form must be used to document the landing. The respondent must keep several blank, printed copies of the appropriate temporary form on hand, so it is available to record data when the Internet connection is not working. No cost or burden is estimated for the interim reports, because they are so infrequently required.


Three types of temporary landing forms are available.


Non-IFQ Groundfish and Non-IFQ Crab Interim Landing Report

(see Procedures for Outages at https://elandings.atlassian.net/wiki/display/doc/Procedures+for+Outages) is to be used for groundfish and non-IFQ crab data.


When the Internet connection is temporarily not available, or the landing occurs when the processor’s office is closed, the processor must:


● Manually enter non-IFQ groundfish and non-IFQ halibut/sablefish landings data onto a paper interim landing report.


● When the network is restored, login to the eLandings website and enter the manually recorded information into eLandings as a new landing report.


● Print out the eLandings report, attach it to the manually recorded interim landing report, and submit these documents to the local office of ADF&G within seven days of the date of landing.


IFQ/CDQ Halibut, Sablefish, or CR Crab Landing Report


● ADF&G

When the Internet connection is temporarily not available and the landing includes IFQ halibut, IFQ sablefish or IFQ crab, the processor must use an IFQ Interim Landing Report (groundfish or crab) to document the landing with ADF&G.


The IFQ Interim forms are available in a booklet that may be obtained from ADF&G. These tickets are uniquely numbered and provide space to record the transaction number(s) provided when a manual IFQ landing is completed. This number is located in the upper right hand side of the form and begins with the format: GI07, followed by the unique number in pink text.


Print out the fish ticket(s) from the eLanding System. Attach the ADF&G copy of the signed Interim eLanding Ticket to the eLanding System printed fish ticket(s)


● NMFS

When the Internet connection is temporarily not available and the landing includes IFQ halibut, IFQ sablefish or IFQ crab, the processor must use a Crab Manual Landing Report or Manual Landing Report Halibut & Sablefish IFQ/CDQ to document the landing with NMFS.


(see Crab Manual Landing Report at http://www.alaskafisheries.noaa.gov/rr/forms/crabmanualanding.pdf)


(see Manual Landing Report Halibut & Sablefish IFQ/CDQ at http://www.alaskafisheries.noaa.gov/rr/forms/ifqlandrpt.pdf)


Contact the NMFS Data Clerk at 1-800-304-4846, Option #1, explain the situation and the need to submit a manual landing report, Data Clerk will contact NOAA Fisheries Office of Law Enforcement (OLE) to authorize the manual landing


Fax the manual landing report to the NMFS Data Clerk. The NMFS Data Clerk will enter the landing information into the IFQ Data Base, provide the transaction number(s), sign the manual landing report, and fax it back to respondent.


When the Internet is again available, login to the eLandings website and enter the Interim eLanding information in the system. Locate the “Manual IFQ Done” checkbox in the IFQ section of the eLandings System. Click this button. DO NOT submit an IFQ report. The IFQ report was entered for this landing by the NMFS Data Clerk based on the information that you provided on the Manual Landing Report.


j. Out-of-state Landing Report (UNCHANGED)


Each year a few shoreside processors in the state of Washington receive fish that were harvested in Alaska. Shoreside processors in Alaska are required to use eLandings to report landings and production. The out-of-state shoreside processors are required to record and report fish received from Alaska, but are not required to use eLandings. They use instead an out-of-state landing report that is available on the NMFS website at http://www.alaskafisheries.noaa.gov/rr/forms/outofstateelandings.pdf.


The manager of a shoreside processor must record information onto the out-of-state landing report for each groundfish delivery (other than IFQ sablefish) provided by the operator of a catcher vessel, the operator or manager of an associated buying station, and from processors for reprocessing or rehandling product into eLandings or other NMFS-approved software. In addition, the manager must record discard or disposition of fish that occurred on and was reported by a catcher vessel; that occurred on and was reported by a buying station; and that occurred prior to, during, and/or after production of groundfish at the shoreside processor must be recorded on the out-of-state landing report. Discards and dispositions also must be recorded when no groundfish are delivered but the blue DFL is submitted by a catcher vessel containing records of discards or disposition.


A person who is issued a Registered Buyer permit and who receives IFQ halibut or IFQ sablefish from an IFQ permit holder or who receives CDQ halibut from a CDQ permit holder at any time during the fishing year is required to use eLandings or other NMFS-approved software to submit landings reports. If the processor is not located in Alaska, the Registered Buyer must complete and submit a separate out-of-state landing report for each shipment of halibut or sablefish.


Deadline: enter information from a specific vessel by noon of the day following completion of the delivery and submit the completed Out-of-State Landing Report to NMFS by fax to:

907-586-7131.


The cost and burden for this report is included in the cost for processors using eLandings.


It is anticipated that the information collected will be disseminated to the public or used to support publicly disseminated information. NMFS will retain control over the information and safeguard it from improper access, modification, and destruction, consistent with National Oceanic and Atmospheric Administration (NOAA) standards for confidentiality, privacy, and electronic information. See response to Question 10 of this Supporting Statement for more information on confidentiality and privacy. The information collection is designed to yield data that meet all applicable information quality guidelines. Prior to dissemination, the information will be subjected to quality control measures and a pre-dissemination review pursuant to Section 515 of Public Law 106-554.

3. Describe whether, and to what extent, the collection of information involves the use of automated, electronic, mechanical, or other technological techniques or other forms of information technology.


This collection is estimated to be 99 percent electronic. The eLandings registration, landings report, production report, eLog, and catcher/processor landing report are submitted by Internet data entry at http://elandings.alaska.gov/. For catcher/processors and motherships that do not have Internet service, a Desktop Client Application (seaLandings) can be used to generate files for submitting via email.


4. Describe efforts to identify duplication.


None of the information collected as part of this information collection duplicates other collections.


5. If the collection of information involves small businesses or other small entities, describe the methods used to minimize burden.


This collection-of-information does not impose a significant impact on small entities.


Even though small numbers of directly regulated vessels and entities may be described as small with respect to their own gross revenues, when affiliations among entities are considered, as required under the RFA, there are no small entities in this fishery. The directly regulated vessels in this fleet have formed a fisheries cooperative that effectively allocates to each vessel a share of the Pacific cod TAC and of the available halibut PSC. These vessel-specific individual quotas are enforced under a private contract among the entities. Therefore, for the purpose of this analysis, the directly regulated entities are all affiliated, with all the entities that would otherwise be characterized as small, having affiliations with larger entities.


6. Describe the consequences to the Federal program or policy activities if the collection is not conducted or is conducted less frequently.


This action is necessary to improve recordkeeping and reporting efficiency for processors and to improve the quality of data obtained by NMFS, ADF&G, and IPHC for fishery management purposes. Advances in technology, public expectations, Congress’s mandate in the Government Paperwork Elimination Act, and Administration policy all require that agencies of the United States government move expeditiously to adopt electronic processes. If this collection were not conducted, NMFS fishery data collection would be set back.


7. Explain any special circumstances that require the collection to be conducted in a manner inconsistent with OMB guidelines.


Not Applicable.


8. Provide information on the PRA Federal Register Notice that solicited public comments on the information collection prior to this submission. Summarize the public comments received in response to that notice and describe the actions taken by the agency in response to those comments. Describe the efforts to consult with persons outside the agency to obtain their views on the availability of data, frequency of collection, the clarity of instructions and recordkeeping, disclosure, or reporting format (if any), and on the data elements to be recorded, disclosed, or reported.


A proposed rule (RIN 0648-BF36) was published in the Federal Register on (80 FR 81262, December 29, 2015; corrected January 22, 2016 (81 FR 3775)) to solicit public comment.

The comment period closed on January 28, 2016.


NMFS received three comment letters from the public that contained three substantive comments; however, they pertained only to 0648-0318.


9. Explain any decisions to provide payments or gifts to respondents, other than remuneration of contractors or grantees.


No payment or gift is provided under this program.


10. Describe any assurance of confidentiality provided to respondents and the basis for assurance in statute, regulation, or agency policy.


The information collected is confidential under section 402(b) of the Magnuson-Stevens Act. It is also confidential under NOAA Administrative Order 216-100, which sets forth procedures to protect confidentiality of fishery statistics.


11. Provide additional justification for any questions of a sensitive nature, such as sexual behavior and attitudes, religious beliefs, and other matters that are commonly considered private.


This information collection does not involve information of a sensitive nature.


12. Provide an estimate in hours of the burden of the collection of information.


Total estimated unique respondents: 378 (37 mothership, 94 catcher/processors, 58 shoreside and SFPs, 14 catcher vessels, 175 tenders) an increase from 139. Total estimated responses: 71,906, an increase from 71,299. Total estimated burden: 12,396, a decrease from 25,588 hr. Total estimated personnel cost: $458,652, a decrease from $945,656


13. Provide an estimate of the total annual cost burden to the respondents or record-keepers resulting from the collection (excluding the value of the burden hours in Question 12 above).


Total estimated miscellaneous costs: $2,248, a decrease from $4,765.






14. Provide estimates of annualized cost to the Federal government.


Total estimated responses: 19,649, an increase from 16,196. Total estimated annual burden: 1,725, an increase from 1,438 hr. Total estimated personnel cost: $63,825, an increase from $53,280.


15. Explain the reasons for any program changes or adjustments.


Changes:


This action requires that the operator of a catcher/processor placed in the partial observer coverage category submit a catcher/processor landing report, a new reporting requirement. The landing report would be generated through eLandings by consolidating the daily production reports for the period the vessel operator defines as the fishing trip for purposes of observer coverage.



Catcher/processor landing report (NEW)

an increase of 9 respondents and responses, 9 instead of 0

an increase of 5 hours burden, 5 hr instead of 0

an increase of $185 personnel costs, $185 instead of $0


Adjustments:


Adjustments are made due to changes in participants.


IERS Processor registration

a decrease of 7 respondents and responses, 12 instead of 19

a decrease of 2 hours burden, 3 instead of 5

a decrease of $74 personnel costs, $111 instead of $185

a decrease of $4 miscellaneous costs, $6 instead of $10


eLandings/seaLandings Landing report

a decrease of 44 respondents, 95 instead of 139

a decrease of 1,198 responses, 20,425 instead of 21,623

a decrease of 9,209 hours burden, 3,404 instead of 12,613

a decrease of $340,733 personnel costs, $125,948 instead of $466,681

a decrease of $1,141 miscellaneous costs, $1,021 instead of $2,162


eLandings Production report

a decrease of 57 respondents,189 instead of 246

a decrease of 1,500 responses, 24,426 instead of 25,926

a decrease of 4,806 hours burden, 2,036 instead of 6,842

a decrease of $177,822 personnel costs, $75,332 instead of $253,154

a decrease of $1,372 miscellaneous costs, $1,221 instead of $2,593




Catcher/processor eLog

an increase of 17 respondents, 94 instead of 77

an increase of 3,451 responses, 19,082 instead of 15,631

an increase of 855 hours burden, 4,724 hr instead of 3,869

an increase of $31,635 personnel costs, $174,788 instead of $143,153



16. For collections whose results will be published, outline the plans for tabulation and publication.


The information collected will not be published.


17. If seeking approval to not display the expiration date for OMB approval of the information collection, explain the reasons why display would be inappropriate.


Not Applicable


18. Explain each exception to the certification statement.


Not Applicable



B. COLLECTIONS OF INFORMATION EMPLOYING STATISTICAL METHODS


This collection does not employ statistical methods.



26


File Typeapplication/vnd.openxmlformats-officedocument.wordprocessingml.document
AuthorPatsy Bearden
File Modified0000-00-00
File Created2021-01-24

© 2024 OMB.report | Privacy Policy