Page Comparison

Instruct the user to omit the D as part of the permit number. A "D" at the end of the permit number indicates that CFEC card is a duplicate.

If the processor has done a manual landing, they should enter all the landing data after the manual landing is complete. Make sure the IFQ Reported Manually box is checked and all line items are entered. Please make sure the user does not generate or submit their IFQ report.  The processor should still enter their IFQ permits in the CFEC worksheet, even though they are not submitting their IFQ report.

Instruct the user to enter a disposition code of 62. Then save and click on Add/Edit Comments button and tell the user to utilize the drop-down menu to select an explanation that best describes the cause of the overage. Processors should contact NMFS SF, NMFS Enforcement, or their local office of ADF&G for assistance with overages.

The skipper's NMFS ID should always be used even if he is fishing for a co-op.

Advise the user to submit the initial report and document the landing. Pricing and grading can wait until business hours. Contact eLandings support at eLandings@alaska.gov.

If you have time, tell the user to open their report and click on the Add/Edit Grading/Pricing button. They must enter a full line of text for the grading and pricing to be properly saved (including Sold Condition, Product Type, Size/Grade, Sold Pounds).

First find out what it is they wish to do. If they are trying to use the max-out pounds feature for an IFQ permit in conjunction with CDQ, they can't.

Max-out can only be used for IFQs. If they are trying to allocate pounds to each IFQ permit by disposition code (i.e. deadloss, sold, personal use) direct them to the report builder feature.

If they want to max-out an IFQ permit and don't care if the deadloss, sold and personal use get distributed between all the permits then they should use the max-out field. The user can use the max-out field to indicate the amount of crab they wish to be allocated to a certain permit by entering that amount in the Lbs. to Max Out Permit field of the CFEC permit worksheet section. They must specify an Area/Fishery for the row for which they wish to use the max-out feature, plus they must have a second IFQ and/or IPQ permit though onto which the rest of that weight can go.

The user would enter CDQ catch on a separate permit line since the CFEC permit is different for CDQ fishing. They would select CDQ as management program and go to blue Management Program Codes linkto determine which CDQ management program ID should be documented in that line. CDQ management program ID (51-56) is required when listing CDQ as a management program. No information should be entered in the IFQ worksheet (i.e. NMFS ID, species, IFQ permits, IPQ permits, etc.). Also crab CDQ and ACA permits have an extra letter in the CFEC fishery (ex. T91QA) and all five digits will need to be entered in the CFEC fishery field.

ADF&G staff use various pieces of documentation that verifies where the catch occurred and manually batches reports from the same trip.If the processor wants to revise a landing that ADF&G has edited or wants further information about why the crab landing report looks different, they should contact ADF&G in Dutch Harbor.

Crab must be on the appropriate CFEC card for that species and area even if it is incidental. Some species share the same CFEC card (i.e. bairdi and snow crab) and some don't (i.e. bairdi and red king crab). If the processor doesn't know what this means advise them to create separate tickets and have them call ADF&G in Dutch Harbor during business hours.

We encourage users to report their crab landings on a single landing report, but as a last resort, if the report is complex with multiple stacked permits, the user may need to report the catch in two separate landing reports.

For processors that are completing landing reports, the user would need to get permission from Enforcement to do a manual landing, and then they would enter the landing in eLandings once the web connection is restored. They would need to make sure the IFQ Reported Manually box was checked on their landing report and they enter all line items. The processor should not generate or submit their IFQ report, although they should enter their IFQ permit in the CFEC worksheet. An interim fish ticket must be completed at the time of offload and include a CFEC card imprint and signatures.

Users should contact eLandings support if they wish to delete submitted reports from eLandings. They will pass the request along to State and/or NMFS programmers.  If a user wishes to delete an unsubmitted report, they can login to the web interface and click on the Delete Unsubmitted Report link at the top of the Reports Menu. Information should then be entered about the report they wish to delete and the user should then click on the Delete button.

If any changes must be made to an IFQ report after it has been submitted, they must do so through the Data Technicians and the IFQ changes are made manually by the technicians. However, the user must also make the same changes to the line items on their landing report and submit a revised fish ticket to ADF&G.

This is not an emergency; grading and pricing can be taken out and added later. They can contact eLandings support at 907-586-7462 during normal business hours.

Ask the processor what the error message says. Occasionally, a processor will confuse when they receive a red-colored error message with red-lining on their IFQ report.

First ask how many CFEC permits they have, and how many IFQ permits they have for each CFEC card holder. Verify that the permits they entered are correct, based on values in the Agency Desktop. Sometimes if a company is listed as the permit holder, its permit number will be used by mistake instead of the fishermen's permit number. Make sure that they do not enter the same permit number twice. They may enter multiple IPQ permits for the same IFQ permit, one right underneath the other, instead of reentering the whole line of permit numbers again.

Make sure the processor enters the IFQ weight, the amount of IFQ pounds they wish to come off their IFQ account.

This error could be caused by maintenance of our computer system.  Advise the processor to try again in five minutes.  Then confirm that the IFQ is not being debited each time the processor gets this error message. If the processor receives the error two or three times, after waiting five minutes each time, then I would assume that something has gone wrong with the "brief disruption of connectivity" and the data technicians might want to consider recommending a manual landing. Then inform eLandings@alaska.gov of the potential outage. If you believe there is an outage during the weekend and have not received a response from eLandings support contact Suja Hall directly at 907-321-1578.

If any changes must be made to an IFQ report after it has been submitted, they must do so through the Data Technicians who make the IFQ changes manually. However, they still need to make the same changes to the line items on their landing report. They would need to make sure the IFQ Reported Manually box was checked on their landing report.

Instruct the user to enter a disposition code of 62. Then save and click on Add/Edit Comments button and tell the user to utilize the drop-down menu to select an explanation that best describes the cause of the overage. Processors should contact NMFS SF, NMFS Enforcement, or their local office of ADF&G for assistance with overages.

Users should contact eLandings support if they wish to delete submitted reports from eLandings. They will pass the request along to State and/or NMFS programmers.  If a user wishes to delete an unsubmitted report, they can login to the web interface and click on the Delete Unsubmitted Report link at the top of the Reports Menu. Information should then be entered about the report they wish to delete and the user should then click on the Delete button. For at-sea processors, they may need to refrain from entering their ADF&G Processor Code before they click on the Delete button.

If the report is complex with multiple stacked permits, the user may report the catch in two separate landing reports.

If the processor is trying to create a landing report, the user would need to get permission from Enforcement to do a manual landing, and then they would enter the landing in eLandings once the web connection is restored.

They need to make sure the IFQ Reported Manually box was checked on their landing report and they still need to enter all line items.

The processor should not generate or submit their IFQ report although they still need to enter their IFQ permit in the CFEC worksheet area. 

If the processor is trying to create a production report, direct the caller to eLandings support for instructions about how to proceed.

Inform elandings support of any potential outages. If you believe there is an outage during the weekend, and have not received a response from eLandings support, contact Suja Hall directly if it is a weekend outageat 907-321-1578. 

Advise the user to submit the initial report and document the landing. Pricing and grading can wait until business hours. Contact eLandings support.

If you have time, tell the user to open their report and click on the Add/Edit Grading/Pricing button. They must enter a full line of text for the grading and pricing to be properly saved (including Sold Condition, Product Type, Size/Grade, Sold Pounds).

This feature can be used to 'max-out' a specific amount of pounds the fisher wants assigned to an IFQ permit.
After entering their CFEC permit information and IFQ permit information, they need to enter the pounds they want debited from that specific permit under the "max-out" column on the report screen.

They must specify an IPHC Area/Fishery for the row they are using the max-out feature on and they must have a second IFQ permit for the same Area so the remaining IFQ landed pounds can be allocated accordingly.

Ask the processor what the error message says. Occasionally, a processor will confuse when they receive a red-colored error message with red-lining on their IFQ report.

First ask how many CFEC permits they have, and how many IFQ permits they have for each CFEC card holder. Verify that the permits they entered are correct, based on values in the Agency Desktop. Sometimes if a company is listed as the permit holder, its permit number will be used by mistake instead of the fishermen's permit number.  Make sure that they do not enter the same permit number twice. They may enter multiple IFQ permits for the same CFEC permit one right underneath the other, instead of reentering the whole line of CFEC permit numbers again.

When a mistake has been made in entering a permit and if the user has already generated their IFQ report, in order for the report to go through the user first must click on Edit IFQ Reports and delete the unsubmitted IFQ reports.  Then the user should go back and make the edit to the permit and then regenerate the IFQ report.

Make sure the processor enters the IFQ weight, the amount of IFQ pounds they wish to come off their IFQ account.

Open the halibut IFQ report and click Partial Delivery box. Then create a sablefish landing report and add the sablefish line items. Tell the processor to check the Partial Delivery box. If the processor manually landed the sablefish, tell them to check the IFQ Reported Manually box and tell the processor to not generate the IFQ report. They should still enter their IFQ permits in the CFEC worksheet.

This error could be caused by maintenance of our computer system.  Advise the processor to try again in five minutes.  Then confirm that the IFQ is not being debited each time the processor gets this error message. If the processor receives the error two or three times, after waiting five minutes each time, then I would assume that something has gone wrong with the "brief disruption of connectivity" and the data technicians might want to consider recommending a manual landing. If you believe there is an outage contact eLandings support at elandings@alaska.gov or 907-586-7462. If it is during the weekend also contact Suja Hall directly so she contact developers and send a email to all eLandings users of the outage.

The user needs to log into the eLandings system, locate the report, find the Edit Vessel, Permit, and Location Information tab and click on it. The user needs to find and check the box that has IFQ Reported Manually right next to it. Now they need to click on "save". Next they will click on the button that says "Submit Final Report" which will finalize the landing report.

A stat area is ambiguous if an IPHC regulatory line transects it (ex. 2C/3A). If you try to submit an IFQ report without specifying a stat area you will receive an error. Find and click on the Edit IFQ Reports button, locate the line item that did not have a stat area specified, click on the drop down list and make your selection.

Direct the caller to contact eLandings support elandings@alaska.gov or 907-586-7462 during regular business hours.

The user will need to close the sealandings program and locate the logbook folder in C:\ProgramData\sealandings\reports\logbook and delete the file that reads "LB2018.xml" (or whatever the current year is) that is in the folder. If they have another file in that folder that looks like LB123456.xml, they should be able to make logbook entries in sealandings.

The user needs to have Administrative rights to be able to make logbook entries. They will need to call their home office and have the user with Admin rights give them the same authorization.

eLogbook does not allow for deletions, only edits can be made to existing entries. User's can always enter a comment documenting what mistakes occurred.

All other eLogbook questions should be addressed by eLandings support 907at eLandings@alaska.gov or 907-586-7642 during regular business hours.