0515 rev comp frzr lgl 110512.ss rev

SUPPORTING STATEMENT

ALASKA INTERAGENCY ELECTRONIC REPORTING SYSTEM (IERS)

OMB CONTROL NO. 0648-0515

This document is a request for comprehensive revision of an existing collection due to a current revision by associated rule, RIN 0648-BB67 and a previous revision by associated rule, RIN 0648-AX89. Ninety-four catcher/processors are removed from the paper logbook collection, OMB Control No. 0648-0213 and added to this collection. Fourteen trawl gear catcher vessels using a pilot electronic logbook are also removed from OMB Control No. 0648-0213 and added to this collection, so that all electronic logbooks are now in the same information collection.

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, Alaska Region (NMFS) 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.

INTRODUCTION

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.

NMFS collects from the Alaska fishing industry groundfish harvest and production data for FMP species in the Exclusive Economic Zone (EEZ). ADF&G collects from the Alaska fishing industry harvest data for groundfish species taken in the State of Alaska waters, and has responsibility for some fisheries in the EEZ, such as lingcod and black rockfish. ADF&G and NMFS cooperatively manage the Crab Rationalization (CR) Program fisheries in the Bering Sea and Aleutian Islands Management Area (BSAI). NMFS and IPHC cooperatively manage Individual Fishing Quota (IFQ) for Pacific halibut and sablefish in both State waters and in the EEZ. In addition, NMFS manages the Western Alaska Community Development Quota (CDQ) halibut, fixed gear sablefish CDQ, and pollock CDQ fisheries.

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 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.

A respondent must obtain at his or her own expense hardware, software, and Internet connectivity to support Internet submissions of commercial fishery landings, production data, and discard or disposition data. It is known that all respondents already use eLandings.

Description of RIN 0648-BB67 Revision

Participation in the BSAI Pacific cod longline catcher/processor sector is limited to holders of License Limitation Program (LLP) licenses authorized under the Consolidated Appropriations Act of 2005. This sector receives a specific allocation of BSAI Pacific cod each year. A sector-specific allocation, in combination with a closed-class of license holders, created an opportunity for these license holders to form a voluntary fishing cooperative, the Freezer Longline Conservation Cooperative (FLCC). The FLCC divides the sector’s allocation of Pacific cod among members of the cooperative through private contractual agreements. The FLCC manages these individual allocations to ensure that individual vessels and companies do not harvest more than their agreed-upon share and represents owners of all 33 of the eligible LLP licenses.

The formation of the FLCC resulted in a significant change in the duration of the Pacific cod fishery, has ended the race for fish, and has increased economic efficiency for the fleet. With increased efficiencies come new demands for enhanced catch accounting, monitoring, and enforcement, so participants must have quick access to catch accounting data so they can monitor their own quotas.

This revision would modify equipment and operational requirements for the owners and operators of 33 freezer longline catcher/processors with an LLP license endorsed for catcher/processor operations, Pacific cod, hook-and-line gear, and BSAI areas (hereafter, eligible catcher/processors). The revisions require eligible catcher/processors to use eLandings or seaLandings electronic logbook (eLog) to record and report catch accounting data. These requirements will increase the speed and accuracy of data transmission to NMFS and will assist in accurate quota monitoring. In addition, these revisions would enhance monitoring and enforcement measures used to verify the harvest of Pacific cod by eligible catcher/processors that operate in the BSAI, the Gulf of Alaska (GOA), or while the vessel is groundfish CDQ fishing. Other benefits of the revisions include: 1) allowing NMFS to enforce Pacific cod catch limits in the presence of a voluntary cooperative; 2) giving freezer longline representatives greater confidence in the accuracy of NMFS Pacific cod catch estimates; and 3) improving the efficacy of the cooperative’s catch share program.

The operator of an eligible catcher/processor must record required information in a NMFS-approved catcher/processor longline and pot gear eLog instead of a paper catcher/processor longline or pot gear daily cumulative production logbook (DCPL) (see OMB Control No. 0648-0213). The operator of each of the eligible catcher/processors is required to electronically submit the eLog information as a file through eLandings; all of the 33 processors currently use eLandings. Thus it is known that all of the eligible catcher/processors have the hardware (computer and printer) and software with the required capabilities to use an eLog.

The operators of eligible catcher/processors would be required to report all Pacific cod catch at the haul level, using an eLog, so that the data are readily available to NMFS in an electronic format. This requirement is necessary to collect data on the weight of Pacific cod at a finer resolution than the daily total currently required in eLandings or seaLandings production reports. The longline or pot eLogs would be an additional component to eLandings or seaLandings, the program through which the operators of catcher/processors currently submit their daily production reports.

Description of RIN 0648-AX89 Revision

Over the past 15 years, the Council and NMFS have implemented several management measures to limit Chinook salmon bycatch in the BSAI trawl fisheries. The Bering Sea pollock fishery catches up to 95 percent of the Chinook salmon taken incidentally as bycatch in the BSAI groundfish fisheries. In the AX89 rule, NMFS implemented the same method of accounting for Chinook salmon bycatch for all AFA sectors.

The new procedure used a census or a full count of Chinook salmon bycatch in each haul by a catcher/processor and delivery by a catcher vessel to a mothership or catcher/processor as a basis for monitoring and enforcing the Chinook salmon PSC allocations under Amendment 91. This would eliminate the uncertainty associated with observer extrapolating from species composition samples to estimates of the total number of salmon caught in each haul. In addition, it would support the level of precision and reliability that both the vessel owners and NMFS require to monitor and enforce Chinook salmon PSC limits.

Operators of catcher/processors participating in the Bering Sea pollock fishery were required to

accurately count salmon for Chinook salmon PSC allocations and report the salmon bycatch counts by species for each haul or delivery rather than the daily total. This count is submitted to NMFS using a catcher/processor trawl eLog so that the data are readily available in an electronic format. Reporting the count of all salmon by species for each haul does not change or increase the amount of information that is required to be gathered by vessel operators because, vessel operators must obtain a count and identification of salmon in each haul and sum that information to get the daily totals. The eLogs replace the paper daily cumulative production logbooks (DCPLs) required to be submitted by the operators of catcher/processors under § 679.5(c)(4).

JUSTIFICATION

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

When compared with paper forms and conventional logbooks, IERS is a more convenient, accurate, and timely method of fisheries reporting. Some of the benefits of IERS include: improved data quality, automated processing of data, improved process for correcting or updating information, availability of more timely data for fishery managers, and reduction of duplicative reporting of similar information to multiple agencies.

Additionally, eLandings provides continuous online access to individual accounts by participants. These provisions make recordkeeping and reporting requirements less burdensome by allowing participants to more efficiently monitor their accounts and fishing activities.

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. Registration, eLandings or seaLandings processor [REVISED]

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. A User is an individual within a processor who is authorized and designated to use a User 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.

Once registered, the User is not required to register again unless ownership changes; new ownership requires a new Federal permit and ADF&G processor code. All of the eligible catcher/ processors have registered and currently use eLandings or seaLandings to submit production reports. Therefore, no additional charges occur with this project.

The following operations -- determined by the type of permit required to do certain fisheries activities and the capability to access the Internet -- use eLandings, seaLandings, or other NMFS-approved software. These operations are:

♦ 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 (CQE) 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 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

A person who is issued a Registered Crab Receiver (RCR) permit and who receives CR crab from a crab IFQ permit holder or crab IFQ hired master

A Buyer/Exporter operation receives catch from fishers, but exports the catch out of the country, usually to Canada, without processing the catch into other products. Since Buyer/Exporter operations do no processing they cannot do custom processing.

A Catcher Seller operation is a vessel that catches and sells unprocessed or limited processed catch to individuals (e.g. via dockside sales) for personal consumption, or to other fishers for bait, but not for resale.

The following sub-operations are available through eLandings and seaLandings:

♦ Buying Station

A Buying Station is an operation that receives unprocessed catch from vessel for trans-shipment or delivery to a shoreside processing plant or mothership and that does not process those fish (NMFS 679.2 Definitions). A buying station can be considered an annex of the plant or mothership for which it is doing receiving. Buying Stations may be completely shore based, such as a truck being loaded for transport to a distant plant, or may be a scow (a barge-like vessel). Tenders are a special type of buying station that have their own operation type.

♦ Tenders

A tender operation is a vessel that is attendant to catcher vessels and is used to transport or ferry unprocessed fish or shellfish received from another vessel to a shoreside processor or mothership.

♦ Custom Processing Owner

The purchaser/owner of the seafood product may have another processor receive, expedite, or process seafood on their behalf but not own the catch. The operation that is in possession of the seafood product, but not the owner or a direct agent for the owner is a custom processor. The landing reports are created and submitted on the owner’s behalf by the custom processor.

The custom processing relationship must be setup by the purchaser/owner of the catch with the custom processor, who remains the primary User of the operation with full visibility of landing reports sub0mitted. The landing reports are submitted under the ADF&G processor code of this custom processor.

The following applications are accessible through eLandings registration:

♦ tLandings (Tender Interface)

♦ eLog (the eLogbook is an application that is accessed once a user has registered their operation and established a UserID & password)

Data Extract General Information

The eLandings web application provides an interface to search for and retrieve finalized landing report and production report data from the eLandings database. The data is retrieved by the Processor Code or the Federal Permit Number. The Report Extract page provides users with the ability to extract these reports in three different formats, XML, CSV, or EXCEL.

In addition to the report extract feature, users can download and customize fishery specific landing and production report templates, providing a consistent output of the information pertinent to the end users' needs.

User IDs

Each user of eLandings needs a user ID. The user ID identifies the individual and gives them authorization to view and submit reports for specific operations. User IDs should not be shared, each person should have their own user ID. This facilitates the management of users and privileges, and provides for data security. The same user ID may be used for multiple operations.

Establishing Accounts

Before an operation or user ID can be used, it must first be registered with eLandings, and be approved for use.

Register an operation or sub-operation

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 does not need to re-enter this information unless applying for a new operation or sub-operation, because that information is autofilled in subsequent reports by eLandings and seaLandings. The processor applies 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.

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)

User Profiles

The eLandings system provides each user a user profile where they can edit their user information and preferences. The user profile is accessed from the links at the top of most eLandings pages. The user's company name, phone and fax numbers, and email address may be edited. If the user name changes, notify NMFS to make the change. The user profile allows the User to set a number of preferences that affect how data and pages are displayed. The user profile page allows the user to select a default operation that will be automatically selected in the operations selection drop down box on the Reports Menu page.

Currently, there are 760 respondents using eLandings or seaLandings; each processor needs to register only once. However, it is possible that additional Users, new operations, or new sub-operations may be required at each processor. The 33 freezer longline catcher/processors and 61 trawl gear catcher/processors are already registered to use eLandings or seaLandings. Each of the 94 would need to register to use the eLog as an additional sub-operation (see e. below). For this information collection, twelve new registrations are estimated per year to add operations or sub-operations.

eLandings processor registration, Respondent
Number of respondents Additional Users, operations, or sub-operations = 12 Total annual responses Frequency of response = 1 Total burden hours Time per response = 15 minutes Total personnel cost ($25/hr) Total miscellaneous cost Photocopy = 0.05 x 12 = 0.60 Postage = 0.45 x 12 = 5.40	12 12 3 hr $75 $6

eLandings processor registration, Federal Government
Total annual responses Total burden hours Time per response = 15 minutes Total personnel cost ($25/hr) Total miscellaneous cost	12 3 hr $75 0

b. Processor eLog (NEW)

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.

To use an eLog, the respondent using eLandings or seaLandings must:

♦ Register an operation

♦ Login

♦ Register a new eLog as an operation

♦ Open current year eLog and make entries

NMFS expects that vessel operators not required to use the eLogs would actually prefer to use eLogs over the paper 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.

Each of the 94 catcher/processors uses eLandings or seaLandings. Thus it is known that all of the eligible catcher/processors have the hardware (computer and printer) and software with the required capabilities to use an eLog.

Previously, Amendment 91 to BSAI FMP required that the operator of an AFA catcher/processor or any catcher/processor harvesting pollock CDQ must use a combination of NMFS-approved catcher/processor trawl gear eLog and eLandings or seaLandings to record and report groundfish and PSC information. This meant that the trawl catcher/processors should have been moved from the OMB 0648-0213 collection to this collection, OMB 0648-0515. With this action, the 61 trawl catcher/processors are added to this collection.

The operator of each of the 33 longline or pot gear catcher/processors and of the 61 trawl gear catcher/processors is required to submit information to NMFS in a catcher/processor eLog instead of a paper catcher/processor longline or pot gear daily cumulative production logbook (DCPL) or catcher/processor trawl gear DCPL (see OMB Control No. 0648-0213) during the entire year for reporting required information.

Therefore, all 94 catcher/processors are removed from the paper logbook collection, OMB Control No. 0648-0213, and added to this collection (Control No. 0648-0515).

1. eLog registration

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, so this eLog registration will not cause additional charges (see question 2a of this support statement).

2. Catcher/processor eLog

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 AFA fleet, trawl catcher/processors that are fishing CDQ pollock in the Bering Sea, and trawl catcher/processors participating in the rockfish fishery. The revision adds requirements for the Freezer Longline Catcher/processors to use an eLog instead of a DCPL. The operator of a catcher/processor subject to 50 CFR part 679.100(b) must use a NMFS-approved catcher/processor longline and pot gear eLog to record and report fishery information.

The procedures for data entry in the eLandings eLog and seaLandings eLog are different from each other. eLandings eLog uses tabs at the top of the screen to move through the data entry screens. Navigating and doing data entry in the seaLandings eLog is done by a panel on the left side of the eLog screen, called the left-hand navigation pane, which provides a way to get to the sections of the eLog to create voyages, hauls, add catch, and make edits. The left-hand navigation pane is hierarchical and if there is a + sign next to an item, the User can click on the + sign to see all of the contained items. At the highest level of the hierarchy is the logbook. Within the logbook are voyages. Within voyages are days; and within days are hauls. Click on each of these levels in the eLog to obtain different options.

Voyages: click on a voyage, there are 3 options

Add or Edit voyages

Add your fishing gear information

Go active / inactive

Days: click on a particular day in a voyage, there are 3 options

Add hauls

View and print your logbook page

Add comments

Hauls: click on a particular haul within a day, there are 2 options

Edit hauls

Add or Edit catch 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 ($25 x 4724) Total capital cost (18,800/3) Software acquisition and training ($200 x 94)

94 19,082 4,724 hr $118,100 $6,267

Catcher/processor eLog, Federal Government
Total annual responses Total Burden Hours (1590.17) Time per response (5 min x 19082) Total Personnel cost ($25 x 1590) Total Initial Cost Software development (between $30,000 and $100,000) = $65,000 Distribution, installation, & training = $2,800 Total Miscellaneous Cost	19,082 1,590 hr $39,750 $67,800 0

c. Differences between eLandings and seaLandings

1. eLandings Landing Report Data Screens.

The web-based application provides industry with the ability to submit landing reports (fish tickets), IFQ fisher/processor quota harvest, and processor production information from a single location. The information submitted via the web application, eLandings, is stored in a single repository database. ADF&G, IPHC, and NMFS-AK copy data submitted by industry to their individual data systems.

The eLandings system provides multiple data entry screens for a landing report.

The main pages of an eLandings landing report may be moved through randomly or in sequential order, as follows:

♦ Landing Report, Vessel, Permit, and Location Information.

This page is designed to identify the vessel that fished, the individual(s) and associated IFQ permit(s) selling catch, the location(s) of fishing activity, and the effort associated with that harvest.

♦ Add/Edit Itemized Catch.

This page is designed to record the species, delivery condition, and disposition of the catch.

♦ Add/Edit Grading and Pricing.

This page is designed to record the size and grade, sold poundage, and price per pound.

♦ CFEC Permit Worksheet

This page is designed to record CFEC permit information.

♦ IFQ Permit Worksheet

This page is designed to record IFQ halibut, sablefish, and crab. This page is available after the landing report is initially submitted, and allows one to submit the IFQ report.

♦ ADF&G Statistical Area Worksheet

This page is designed to record the six-digit ADF&G statistical area denoting the actual area of catch. Groundfish/shellfish statistical area charts may be obtained from local ADF&G office, or at http://www.cf.adfg.state.ak.us/geninfo/maps.php#shellfish.

2. seaLandings Landing Report Data Screens

The seaLandings User's Guide contains chapters that explain how to transmit catch data using the stand-alone client, also called seaLandings. This software is used by crews who do not have internet capabilities on their vessels and who transmit their data via email. The ability to email and receive attachments is necessary to use seaLandings.

Chapters in the seaLandings User's Guide explain how to create production reports, consolidated reports and landing reports; how to archive reports; how to transmit reports and process return receipts; how to install seaLandings; and how to obtain more report numbers and fish ticket numbers.

The seaLandings system provides multiple data entry screens for a landing report that may be moved through randomly or in sequential order, as follows:

seaLANDINGS REPORTING SEQUENCE

Vessel/location/status information

↓

Permits & Pounds

Add CFEC permit information, management program,

NMFS ID, and IFQ permits (if applicable)

Add stat areas (when species harvest

is proportional in all areas)

Enter itemized catch information

↓

IFQ Reports

Generate IFQ report(s) if crab, halibut, or sablefish

was harvested

↓

Summary

Check report for errors, Save, and close

↓

Transmit

Create a Report Transmission file,

attach to and submit by email

↓

Save email report receipt in Transmissions folder,

open seaLandings and Process Receipt

The main pages of a seaLandings landing report are as follows:

♦ Vessel/location/status information

This page is designed to identify the vessel that fished, the individual(s) and associated IFQ permit(s) selling catch, the location(s) of fishing activity, and the effort associated with that harvest.

♦ Permits & Pounds

This page is designed to record the CFEC permit information, management program, NMFS ID, stat areas (when species harvest is proportional in all areas), and itemized catch information.

♦ IFQ Reports

Generate IFQ report(s) if crab, halibut, or sablefish was harvested

♦ Transmit

Create and transmit Report by email

3. Generic formats

In order to simplify the presentation of the two data submittal systems, a generic format is used to describe the reports.

d. eLandings or seaLandings landing report [REVISED]

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. The additional 33 longline or pot gear and 61 trawl gear participants are catcher/processors, and catcher/processors are not required to submit landing reports. Therefore, no additional charges occur.

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.

1. Autofill from Registration.

During registration, the User lists the processor operation identification and all of the Federal and State permits associated with the operation. From those registration records, eLandings of seaLandings autofills some of the information required to create a landing report and production report. The User reviews 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.

2. Autofill from CFEC Permit Card with Magnetic Stripe (Optional)

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 for all vessel operators and for any individual(s) who will be fishing and selling seafood product as an IFQ shareholder, on behalf of the actual allocation holder, the hired master of a CR crab cooperative, anyone fishing and selling product under a CDQ allocation, and individuals fishing for golden king crab allocation to the Community of Adak, Alaska. 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.

Beginning in 2008, the CFEC added to all CFEC permit cards 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.

Enter all CFEC permits that pertain to the landing. The information may be data entered onto the screen or entered with the use of a magnetic stripe reader. The CFEC permit card contains the name of the individual, the specific fishery, the permit number, and a Permit Sequence. If entering the data using the magnetic strip, place the cursor in the next blank CFEC Permit field and swipe the permit card through the magnetic stripe reader. The magnetic stripe data will be entered in the permit field. The eLandings System allows the recording of all CFEC and IFQ permits on one landing report. If more than one CFEC permit is recorded in eLandings, a unique fish ticket number is assigned for each CFEC permit.

3. Obtain Signatures and CFEC Card Imprint

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.

4. Maps and coordinates of the special areas and reporting areas may be found at http://alaskafisheries.noaa.gov/rr/figures.htm.

Landing reports are submitted to NMFS by 37 motherships, 58 shoreside processors or stationary floating processors, 1042 IFQ/CDQ halibut/sablefish Registered Buyers, and 30 CR crab Registered Crab Receivers. However, a Registered Buyer or Registered Crab Receiver is an additional permit issued to motherships, shoreside processors, or SFPs. These processors are already counted, for a total of 95 respondents.

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 RB or 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.66) complete & print receipts (5 min x 20425 = 1702.33) electronically submit (5 min x 20425 = 1702.33) Total personnel cost ($25/hr) Total miscellaneous cost (2042.50) Internet = 0.05 x 20,425 = 1021.25 Copies = 0.05 x 20,425 = 1021.25

95 20,425 3,405 hr $85,100 $2,043

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 [REVISED]

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. Therefore, no additional changes occur with this project.

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 ($25/hr) Total miscellaneous cost (2442.60) Photocopy = 0.05 x 24426 = 1221.30 Internet = 0.05 x 24426 = 1221.30	189 24,426 2,036 hr $50,900 $2,443

eLandings production report, Federal Government
Total annual responses Total burden hours Total personnel cost Total miscellaneous cost	0 0 0 0

f. Catcher vessel trawl eLog (CHANGED: Moved from OMB Control No. 0648-0213, with burden 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 or catcher/processors using trawl gear. When that software becomes available, this pilot eLog will be removed.

This item, the catcher vessel trawl eLog was formerly in OMB Control No. 0648-0213. With this action, the electronic logbook for catcher vessel trawl gear is moved to this collection, 0648-0515. The paper catcher vessel trawl daily fishing logbook remains in the 0648-0213 collection-of-information.

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 ($25/hr) Total miscellaneous cost	14 518 146 hr $3,650 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 ($25/hr) Total miscellaneous cost	518 26 hr $650 0

g. Tender Interface (NEW: no burden. Already registered as sub-operations)

The buying station or tender interface (also referred to as tLandings) is a voluntary process used with eLandings and seaLandings developed by ADF&G. Although not required by NMFS, the tender interface is reportedly used by all processors. To use this system, a processor would register each associated tender or buying station as a sub-operation. The User must be registered and activated to use the Tender Interface. When landing reports are submitted from the tender to the processor’s database, a processor can immediately access the data from the eLandings web page.

The Tender Interface provides processors with a tool to receive electronic landing report files created aboard associated tenders during deliveries from catcher vessels and to upload those electronic landing reports to the processor’s eLandings. This software is intended for use on board tenders where a reliable Internet connection is not available. One part of the software, processor tender interface (PTI), is onboard the processor and is used to prepare files for and to read files on a thumb drive from the tenders. The other part of the software, tender work station (TWS), is onboard the tender and is used to prepare landing reports/fish tickets and create simple reports while on the fishing ground. The diagram below illustrates the flow of data from the database to PTI to TWS and back again.

When a tender returns from taking deliveries on the fishing grounds it will have the landing reports and fish tickets in electronic form on its Tender Workstation. The tender operator will use the export function of the tender workstation to create a zip file of the landing reports. This zip file can be emailed to the processor or read directly from the thumb drive.

From the Reports Menu, the processor will import this file and upload the landing reports to eLandings. Once the files are received from the tender operator, on a flash drive or through other means, start the PTI software and select the Import tender reports item on the file menu. All valid landing report files will initially have their Select checkbox checked, and will be imported when the processor clicks the Import button.

PTI will search all available drives at expected locations for landing reports. It will then list any drives that contain landing reports that can be imported. If the thumb drive is inserted after displaying the selection dialog, click the Refresh button to look on the thumb drive for landing reports. Select the drive to import landing reports from and click Next. The Import display window will show the landing reports received from the tender.

The window shows the UserID of the tender User who prepared the files, the name of the tender operation, and information about each landing report. The window allows the processor to select the status that will be assigned to the landing report when uploaded to eLandings. The processor can also open and edit landing reports imported from tenders. The processor’s view of the landing reports in PTI is the same as what tenders saw in TWS when they created the landings.

h. Temporary Disconnect 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 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.

i. 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 Registered Buyer or manager of a shoreside processor must 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.

Groundfish

The manager of a shoreside processor that is required to have an Federal Processor Permit (FPP) under 50 CFR part 679.4(f) and that receives groundfish from a catcher vessel issued a Federal Fisheries Permit (FFP) under 50 CFR part 679.4(d) must use eLandings or other NMFS-approved software to submit a daily landings report to NMFS during the fishing year. If the processor is not located in Alaska, the manager of a shoreside processor must complete and submit to NMFS a separate out-of-state landing report for each shipment of groundfish and donated prohibited species caught in the groundfish fisheries.

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.

IFQ Halibut, IFQ Sablefish, and CDQ Halibut

A person who is issued a Registered Buyer permit under 50 CFR part 679.4(d)(3) and who receives Individual Fishing Quota (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.

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, and electronic logbook 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 (software package) 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. Thus, there are no directly regulated small entities under this action.

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.

NMFS Alaska Region published a proposed rule, RIN 0648-BB67, on June 15, 2010 (77 FR 35925), soliciting public comments on this revision. No comments that impacted this collection-of-information were received.

The final rule published on September 26, 2012 (77 FR 59053).

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.

As stated on the forms, 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: 203, a decrease from 287. Total estimated responses: 64,463, an increase from 46,064. Total estimated burden: 10,314, a decrease from 19,084 hr. Total estimated personnel cost: $257,825, a decrease from $477,108.

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: $10,759, an increase from $4,612.

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

Total estimated annual burden: 1,622, an increase from 4 hr. Total estimated personnel cost: $40,550, an increase from $100. Total annualized capital costs: $67,800.

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

Changes:

NMFS is adding a new program for catcher/processors using longline or pot gear with a requirement to use an eLog instead of a paper DCPL. In addition, a correction is made to add the trawl gear catcher/processors that were required under BSAI Amendment 91 to use an eLog instead of a paper DCPL

A change is made by moving a pilot eLog for catcher vessel trawl vessels from OMB Control No. 0648-0213 to this collection, so that all electronic logbooks will be in the same collection.

In addition, the description of eLandings is updated to include new features, i.e., tender exchange, permit magnetic strip which automatically provides information on the permit holder, out-of-state landing report, and the enhanced use of processor registration to include sub-operations.

eLog, Catcher/processor (NEW)

an increase of 94 respondents, 94 instead of 0

an increase of 19,082 responses, 19,082 instead of 0

an increase of 4,724 hours burden, 4,724 instead of 0

an increase of $118,100 personnel costs, $118,100 instead of $0

an increase of $6,267 annualized capital costs, $6,267 instead of $0

eLog, Catcher vessel trawl (ADDED) (NO CHANGES)

an increase of 14 respondents, 14 instead of 0

an increase of 518 responses, 518 instead of 0

an increase of 146 hours burden, 146 instead of 0

an increase of $3,650 personnel costs, $3,650 instead of $0

Adjustments:

eLandings Processor registration of operation and sub-operation (ADJUSTMENT)

a decrease of 3 respondents and responses, 12 instead of 15

a decrease of 1 hour burden, 3 instead of 4

a decrease of $25 personnel costs, $75 instead of $100

a decrease of $1 miscellaneous costs, $6 instead of $7

eLandings Landing report (ADJUSTMENT; changed estimated time to print from 30 min to 5 min; removed duplicate respondents)

a decrease of 144 respondents,95 instead of 239

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 $230,225 personnel costs, $85,100 instead of $315,325

a decrease of $119 miscellaneous costs, $2,043 instead of $2,162

eLandings Production report (ADJUSTMENT; changed estimated time to submit and print from average of 15 minutes to 5 minutes)

an increase of 11 respondents,189 instead of 178

a decrease of 4,431 hours burden, 2,036 instead of 6,467

a decrease of $110,783 personnel costs, $50,900 instead of $161,683

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.

30