Before a receiver, buyer, or processor of seafood products can use the eLandings system to submit reports they must establish a user account. A user is an individual that has been designated to use the eLandings System to record seafood landings and production. Each individual that will use the eLanding System must be identified by name. The user management subsystem of eLandings is based on user Accounts and Operations. Each user must have a user ID, and must be authorized to make reports for at least one operation. Before a user ID or operation can be utilized both the User and the Operation must be registered.
An operation is defined, for the purposes of the eLandings System, as an entity that will receive seafood product and will complete landing and production reports, as well as IFQ reports. A landing report is defined as 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 expeditor. The landing report will document one or more ADF&G fish ticket(s), and may also generate a NMFS production report, and one or more IFQ report(s).
Depending upon your type of operation, that is, the range of seafood you receive and process, a number of different licenses and permits may be required. The State of Alaska requires that all buyers of seafood product obtain an annual Intent to Operate license, commonly referred to as the ADF&G Processor License Code. Processors or receivers of federally managed fisheries much also obtain a Federal Processors Permit. Buyers or receivers of IFQ halibut or sablefish must obtain a Federal Registered Buyers Permit; and each receiver of rationalized crab must first obtain a Registered Crab Receiver Permit (RCR). The Crab Rationalization Program is exclusive to the Bering Sea and Aleutian Island (BSAI) king and tanner crab fisheries.
As stated above, an entity that is licensed to receive seafood product with the State of Alaska can register an operation. Most buyers, receivers or processors of seafood product have only one operation. In some cases, a business may establish a separately licensed or permitted enterprise. A unique operation is defined as having a distinct combination of any of the following: ADF&G processor code, Federal Processing Permit number, Federal Registered (Halibut/Sablefish IFQ) Buyer number (if applicable), or a Federal Registered (Rationalized BSAI crab) Crab Receiver number (if applicable).
If the combination of any of these permits differs, then the operation is unique.
Image82 – Several Operations
The eLandings system defines several types of operations that have different characteristics. Each operation registered must be one of these types. If you want to register an operation that does not seem to fit one of these descriptions contact eLandings support for help with your registration.
A plant/receiver is a shorebased processing plant or seafood receiver. Plant/Receiver operations are the most common type, and are able to do custom processing or receiving on behalf of another operation.
An At-Sea operation is a Catch/Processor, Mothership, or floating processor that is doing processing or receiving away from an established port. At-Sea operations can also do custom processing or receiving for another operation.
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.
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.
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.
The purchaser/owner of the seafood product may have another processor or operation receive, expedite or process seafood on their behalf. The operation that is in possession of seafood product, but not the owner or a direct agent for the owner is a Custom Processor. The eLandings interagency working group define a Custom Processor as a processor, business, or entity that provides the service of seafood receiving, expediting, or processing but has not purchased (does not own) the seafood, and is not acting as an agent for the owner.
The owner of the catch must establish a custom processing owner operation for each plant that does the actual processing. This allows the owner of the catch to maintain visibility and control of the landing reports, though the landing reports are usually done on their behalf by users at the plant doing the custom processing. The owner of the seafood product must have a valid license with the State of Alaska, and may have their own receiving permits from NMFS. These permits are used to establish the custom processing owner operation. The users at the custom processing facility can then be authorized to make landing reports for the custom processing owner operation. This is akin to providing the custom processor with the metal process code plate to create paper fish ticket records.
The advantage of establishing the custom processing owner operation is that it gives the owner the ability to electronically review and access landing reports created by custom processors as soon as they have been successfully submitted to the Interagency Server. They can also remove the authorization to access those reports should the business relationship be terminated.
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. User IDs can be given access to an operation when appropriate, and have their access privileges for that operation revoked, without affecting the user ID, the data about the individual, or its access to other operations.
Before an operation or user ID can be used, it must first be registered with eLandings, and must be approved for use.
If your facility has never used eLandings and you do not have a eLandings user ID you can create a completely new operation and user account with one form. Access the Register page from the link on the http://elandings.alaska.gov home page, or at https://elandings.alaska.gov/elandings/Register. The Register page allows you to enter all the information needed for both the operation registration and the user ID registration.
[PIC Image 81. - RegistrationRegister, operation section]
We highly recommend contacting eLandings support for help in setting up a completely new operation. The relationship of the permit numbers is important, and is much easier to get right the first time with a little help than it is to correct it after the fact.
Before you begin the process of establishing a new Operation, you should have gathered the following information together, as they pertain to your operation:
ADF&G Processor Code
Federal Processor Permit Number
Federal Buyer Number
Registered Crab Receiver Number
ADF&G Vessel Number (if you operation is a Catcher Processor or Floating Processor
[PIC – Image 83 – Blank Operations Window]First enter the operation information
Operation Type:
Select the operation type for the new operation from the dropdown list.
Operation Name:
Give the name that you will use to refer to the operation. It should be descriptive, and should include your company name as well as the location of the operation. For example, if your company is East Pacific Seafoods and you are registering your plant in Kodiak you should name the operation something like “East Pacific Seafoods – Kodiak”, rather than something like “Kodiak Plant”. This will reduce confusion, since many processors might have a Kodiak Plant. If your operation is a Custom Processing Owner then the operation name should reflect the relationship between your company and the custom processor. For example, if you are setting up a Custom Processing Owner operation for your fish to be custom processed at The Fish Factory in Homer you might name it “East Pacific Seafoods @ The Fish Factory”.
ADF&G Processor Code:
Enter the ADF&G Intent to Operation processor code for your facility or business. This is also known as your F-code. The processor code is required for all operations, except if you are registering an At-Sea operation that is a catcher/processor that only fishes groundfish and never acts as a mothership.
Federal Permit Number:
If your operation will process groundfish enter your Federal Processor Permit if you are registering a shoreside plant, or your Federal Fisheries Permit if you are registering an At-Sea operation.
Registered Buyer Number:
If you will be receiving or processing Halibut or IFQ Sablefish, you must provide a NMFS registered buyer number so that you can submit IFQ transactions.
Registered Crab Receiver Number:
If you will be receiving or processing IFQ crab you must provide a NMFS registered crab receiver number so that you can submit IFQ transactions.
Port:
Enter the ADF&G port code for your operation. The port code you enter will provide the default on your landing reports.
Vessel ADF&G Number:
For At-sea, tender, and catcher-seller operations, enter the ADF&G number of your vessel.
Vehicle License Number:
For buying station operations, enter the vehicle license number of your truck, if applicable.
Physical Operation
The Physical Operation information is required if you are registering a Tender, Buying Station, or Custom Processing Owner operation. The physical operation identifies the operation where the processing actually takes place. You must obtain the Operation Type, Proc Code, Federal Permit Number, Registered Buyer Number, and Registered Crab Receiver Number from the primary user of the physical operation, which must already be setup on eLandings.
[PIC Register, Image 84 – Operation Registration operation section filled in]
Once you have entered the operation information you must provide the user information. The user account you create will be the primary user for the new operation, and will be in charge of managing other users for the operation.
User ID:
Enter the user ID that you would like to create. The user ID must be unique across eLandings, if you enter a user ID that is already in use you will have to pick another one. The user ID can be up to 32 characters long. It may contain blanks. It will automatically be converted to uppercase, even if you enter it in lower or mixed case.
Password:
Enter the password that you would like to use with the user ID. The password must be at least 6 characters long, but no more than 16 characters long. It cannot be all numbers and it cannot contain the user ID. For example, if the user ID is “AMARX”, the password cannot be “AMARX12” or “ZAMARXB”. You will be prompted to change your password once your user ID is enabled, so we recommend using a temporary password for the registration.
Company Name:
The company name should be your employer, or the name of the organization that owns the operation, either the common name or legal name. For example, if you are registering an operation named “East Pacific Seafoods – Kodiak”, your company name should probably be “East Pacific Seafoods”.
User Name:
The user name is your given name, or the name of the person who will use the user ID. It should accurately identify the person, so that in the event of a system problem, if eLandings support contacts your plant by phone they will be connected to the right person by asking for the user by name.
City:
The City should be the city where the operation is located, which is not necessarily the city where you are right now.
State:
The State should be the State where the operation is located, which is not necessarily the State where you are right now. In most cases the State will be AK, for Alaska.
Telephone Number:
The Telephone Number is the number that will be used to contact you in the event of any problems with your operation or landing reports. Telephone number is required.
Fax Number:
The Fax Number that can be used to communicate with you in the event of any problems with your operation or landing reports. Fax number is not required.
Email Address:
The Email Address that the eLandings system and eLandings support personnel can use to communicate important information about eLandings to you. Elandings uses this email address to send you your password if you forget it and request recovery. It is also used to send important information such as schedules of planned system outages and notification of new features and capabilities. Email Address is required.
Security Question:
The Security Question and the Secret Answer are used if you forget your password, and are not able to recover it by email, or if you forget your user ID. Elandings help desk personnel will ask you the security question, and will expect that you know the secret answer. The secret question should ask about something that anyone besides you would be unlikely to know. For example, “What is your favorite sport?” would not be a good security question since many of your co-workers might know that you really like golf or football. Something like “What was your sister’s favorite dog’s name when you were a child?” is much better because only you (or your sister) would be likely to know the answer.
Secret Answer:
The Secret Answer is the answer to the security question. The answer should be something that only you are likely to know, and are unlikely to forget.
[PIC Register, Image 85 - Secretsuser section filled in]
Once you have entered all operation and user data click the Register button to submit the registration. If there are any problems you will receive error messages prompting you to correct them. If the registration is accepted you will be prompted to print and fax in your registration.
[PIC – Image 86 – Registration Button Register page PDF link]
Click the Display and Print link to display your registration form. Print in, sign it, and fax it to the eLandings help desk at the number given on the page. Once the registration has been received and reviewed your user ID will be enabled. You will be notified by email that your user ID is ready to use. Login to eLandings and change your password. You will then be ready to enter and submit landing reports.
Creating a new operation is easier if you already have an eLandings User ID and are logged in. On your User Profile, click the New Operation button. This displays the Register page, with only the new operation fields.
First enter the operation information
Operation Type:
Select the operation type for the new operation from the dropdown list.
Operation Name:
Give the name that you will use to refer to the operation. It should be descriptive, and should include your company name as well as the location of the operation. For example, if your company is East Pacific Seafoods and you are registering your plant in Kodiak you should name the operation something like “East Pacific Seafoods – Kodiak”, rather than something like “Kodiak Plant”. This will reduce confusion, since many processors might have a Kodiak Plant. If your operation is a Custom Processing Owner then the operation name should reflect the relationship between your company and the custom processor. For example, if you are setting up a Custom Processing Owner operation for your fish to be custom processed at The Fish Factory in Homer you might name it “East Pacific Seafoods @ The Fish Factory”.
ADF&G Processor Code:
Enter the ADF&G Intent to Operation processor code for your facility or business. This is also known as your F-code. The processor code is required for all operations, except if you are registering an At-Sea operation that is a catcher/processor that only fishes groundfish and never acts as a mothership.
Federal Permit Number:
If your operation will process groundfish enter your Federal Processor Permit if you are registering a shoreside plant, or your Federal Fisheries Permit if you are registering an At-Sea operation.
Registered Buyer Number:
If you will be receiving or processing Halibut or IFQ Sablefish, you must provide a NMFS registered buyer number so that you can submit IFQ transactions.
Registered Crab Receiver Number:
If you will be receiving or processing IFQ crab you must provide a NMFS registered crab receiver number so that you can submit IFQ transactions.
Port:
Enter the ADF&G port code for your operation. The port code you enter will provide the default on your landing reports.
Vessel ADF&G Number:
For At-sea, tender, and catcher-seller operations, enter the ADF&G number of your vessel.
Vehicle License Number:
For buying station operations, enter the vehicle license number of your truck, if applicable.
Physical Operation
The Physical Operation information is required if you are registering a Tender, Buying Station, or Custom Processing Owner operation. The physical operation identifies the operation where the processing actually takes place. You must obtain the Operation Type, Proc Code, Federal Permit Number, Registered Buyer Number, and Registered Crab Receiver Number from the primary user of the physical operation, which must already be setup on eLandings.
[PIC Register, Image8 7 – Physical Operation operation section filled in]
Once you have entered all the operation data click the Register button to submit the registration. If there are any problems you will receive error messages prompting you to correct them. If the registration is accepted you will be prompted to print and fax in your registration.
[PIC Operation – Image88– Operation Information completed]
[PIC – Image89 - Register page PDF link]
Click the Display and Print link to display your registration form. Print in, sign it, and fax it to the eLandings help desk at the number given on the page. Once the registration has been received and reviewed your new operation will be enabled. Until your operation is enabled you will not be able to enter and submit landing reports for it. However, you are able to authorize other users for the operation. Once the operation is enabled they will be able to use it.
[PIC – Image 90 – Registration Page]
Creating an new user ID for an existing operation is easier than creating an entire new operation, but you must be an administrative user for the operation involved. First, login to eLandings. On your User Profile, scroll down to your operations. The operation name should be a link, and will take you to the operation maintenance page. If the operation name is not a hotlink, i.e. it is plain text, that means you are not an administrative user for that operation and cannot add or disable users. Contact eLandings support if you believe that you should be an administrative user, they will be able to direct you to the primary user for the operation, and they will be able to give you administrative privileges.
[PIC Image 92]
On the operation maintenance page, scroll down to the Authorized Users section. Enter the new user ID that you want to create in the User ID field, and click the Register New User button. If the user ID is already in use you will get an error message and can change the user ID and try again. Otherwise, the Register User page will be displayed.
Enter the user information:
Company Name:
The company name should be your employer, or the name of the organization that owns the operation, either the common name or legal name. For example, if you are registering an operation named “East Pacific Seafoods – Kodiak”, your company name should probably be “East Pacific Seafoods”.
User ID:
The user ID that you requested to create. The user ID will be filled in, and in most cases you should not change it.
Password:
Enter the password that you would like to use with the user ID. The password must be at least 6 characters long, but no more than 16 characters long. It cannot be all numbers and it cannot contain the user ID. For example, if the user ID is “AMARX”, the password cannot be “AMARX12” or “ZAMARXB”. The user will be prompted to change the password once the user ID is enabled, so we recommend using a temporary password for the registration.
User Name:
The user name is the name of the person who will use the user ID. It should accurately identify the person, so that in the event of a system problem, if eLandings support contacts your plant by phone they will be connected to the right person by asking for the user by name.
City:
The City should be the city where the operation is located, which is not necessarily the city where you are right now.
State:
The State should be the State where the operation is located, which is not necessarily the State where you are right now. In most cases the State will be AK, for Alaska.
Telephone Number:
The Telephone Number is the number that will be used to contact the user in the event of any problems with landing reports. Telephone number is required.
Fax Number:
The Fax Number that can be used to communicate with the user in the event of any problems with landing reports. Fax number is not required.
Email Address:
The Email Address that the eLandings system and eLandings support personnel can use to communicate important information about eLandings to the user. Elandings uses this email address to send the user their password if they forget it and request recovery. It is also used to send important information such as schedules of planned system outages and notification of new features and capabilities. Email Address is required.
Security Question:
The Security Question and the Secret Answer are used if the user forgets their password, and is not able to recover it by email, or if they forget their user ID. Elandings help desk personnel will ask the user their security question, and will expect that they will know the secret answer. The secret question should ask about something that anyone besides the user would be unlikely to know. For example, “What is your favorite sport?” would not be a good security question since many of the user’s co-workers might know that they really like golf or football. Something like “What was your sister’s favorite dog’s name when you were a child?” is much better because only the user (or their sister) would be likely to know the answer.
Secret Answer:
The Secret Answer is the answer to the security question. The answer should be something that only the user is likely to know, and is unlikely to forget.
[???PIC Register, Image 11 user section filled in???]
Once you have entered all user data click the Register button to submit the registration. If there are any problems you will receive error messages prompting you to correct them. If the registration is accepted you will be prompted to print the form, have the user sign it, and fax in the registration.
Click the Display and Print link to display the registration form. Print in, have the user sign it, and fax it to the eLandings help desk at the number given on the page. Once the registration has been received and reviewed the user ID will be enabled. The user will be notified by email that the user ID is ready to use. They should login to eLandings and change their password. They will then be ready to enter and submit landing reports.
The eLandings system allows users to self-manage operations and users authorized to submit reports for those operations. In addition to registering new operations and users, the rights to view and edit reports may be granted and revoked.
[Image 93 – Authorized Users]
To provide security and control of user and operations management, only administrative users may authorize other users for operations. When a user registered an operation they automatically become an administrative user for that operation. They can then add authorizations for other users to use the operation, and can revoke those authorizations. An administrative user can also grant administrative privileges to other users for an operation, making them administrative users also.
Each operation requires a primary user. The primary user is an administrative user for the operation, and cannot have its administrative privileges removed. Each operation has only one primary user. An administrative user may change who is the primary user for an operation. Therefore, if the primary user of an operation has left the company’s employment, then another user must first become the primary user of the operation, then the original user can be disabled.
Administrative users may authorize other users for an operation. To authorized a user, first go to your user profile.
[PIC – Image 20 – User Profile menu links, user profile circled]
On your user profile page your authorized operations are listed. Operations for which you are an administrative user have their Operation Name displayed as a link. If the Operation Name is not a linked, then you do not have administrative privileges for that operation.
[Image 21 – Hot Link – User Maintain]
Click on the Operation Name for the operation where you want to add the user. This will display the Operation Information and User Maintenance page. At the bottom of the Authorized Users section is a User ID field. Enter the User ID of the user that you wish to add to the operation and click the Add Existing User button. The user will be added to the operation.
[PIC – Image 22 – Add existing user] operations maintenance, user id field and add button annotated]
[Image 23 – New existing user added]
If the newly added user should have administrative rights for the operation, then check the Admin checkbox for the user and click the Save button. In this example, Audrey Marx is the primary user, with administrative rights. Bertha Crabs also has administrative rights. Bertha added the new user, Mat Mulligan. He has a limited account.
[Image 25 – Authorized users]
A user’s ability to view and edit reports is limited to reports that have the ADF&G Processor Codes, Federal Permit Numbers, Registered Buyer Numbers, and Registered Crab Receiver Numbers that are setup on the operations for which they are authorized. A user’s access to reports can be further limited. The eLandings system allows you to restrict users to only those reports that they create, and that have not been edited by someone else. Users that have these restricted access privileges are known as Limited Users. Note in the example above that Mat Mulligan is a limited user for Kruse Seafoods, Inc.
There are typically two situations where you might want to use the Limited User capability. One is for dock foremen, or other users who are responsible for unloading catch from delivering vessels, but who are not responsible for submitting fish tickets and landing reports. The dock foreman can be authorized as a limited user on eLandings. They will be able to create a new landing report when a vessel arrives, entering the vessel ADF&G number, date of landing, etc., and the CFEC and IFQ permits. Office staff can come in later and fill in the itemized catch, grading and pricing information, and IFQ reports. Once the office staff begins to work on the landing report the limited user will no longer be able to edit that report.
[Image 24 – Users Admin thru limited]
Another case where you might want to have a limited user is where you use an agent who is not an employee of your company. If they were not a limited user they would be able to view all the landing reports for your operation. By making them a limited user they will only be able to view and edit landing reports that they themselves created for you. However, once you or other office staff members have made additional edits to a landing report they will lose the ability to view or edit that landing report.
To set a user as a limited user, first go to your user profile.
[PIC – Image 26 – User Profile link menu links, user profile circled]
On your user profile page your authorized operations are listed. Operations for which you are an administrative user have their Operation Name displayed as a link (blue text). If the Operation Name is not a link then you do not have administrative privileges for that operation.
[Image 27 – Administrative Rights]
[PIC Image 28 Admin rights – link – profile operations section, operation name circled]
Click on the Operation Name for the operation where you want to limit the user. This will display the Operation Maintenance page. The Authorized Users section will show the users authorized for the operation. Click the Limited checkbox for the user you want to limit and click the Save button.
[PIC Image 29 – operations maintenance, user limited checkbox annotated]
An administrative user may revoke a user’s authorization to view and edit reports for an operation. A user’s authorization may be revoked in two ways. The authorization may be temporarily disabled, but left in place so that it can be restored in the future, or it may be completely removed. The disable method would typically be used for seasonal employees who are leaving the operation, but are expected back the next season. The remove method is used for users who are not expected back, such as employees who are fired.
To disable or remove a user’s authorization for an operation, first go to your user profile.
[PIC Image 26 – User Profile link – menu links, user profile circled]
On your user profile page your authorized operations are listed. Operations for which you are an administrative user have their Operation Name displayed as a hotlink. If the Operation Name is not a hotlink then you do not have administrative privileges for that operation.
[Image 28]
Click on the Operation Name for the operation where you want to revoke the user’s authorization. This will display the Operation Maintenance page. The Authorized Users section will show the users authorized for the operation. Click the Disabled checkbox for the user if you want to leave them on the operation, or click the Remove checkbox if you want to remove them from the operation permanently. Click the Save button to save your changes. In the example below, the user, Mat Mulligan has been disabled as a user, at the end of the season. If an employee with a User Account has resigned or been terminated, a user with administrative privileges can select, Remove.
[PIC – Image 30 removed operations maintenance, delete and remove checkbox annotated]
The eLandings system requires custom processing relationships to be setup as operations in order to report correctly. The custom processing relationship is setup by the owner of the catch. They are known as the Custom Processing Owner, and are the client of the company that is processing the catch as a custom processor. This gives visibility of the landing reports to the entity whose Processor Code is being used to submit the reports. The Custom Processing Owner in turn authorizes users at the custom processor to submit reports on their behalf. Typically the Custom Processing Owner authorized one user at the custom processor as an administrative user. That user then manages other users at the custom processor who edit and submit landing reports. The Custom Processing Owner remains the primary user of the operation, and has full visibility of reports submitted.
To setup a custom processing relationship the purchaser/owner of the catch must first make the requisite business relationship with the custom processor. The custom processor needs to already have their plant or vessel setup on eLandings as a Plant/Receiver or At-Sea operation. The custom processor should give the purchaser/owner of the catch the identifying codes for their operation. The codes needed are the Operation Type, ADF&G Processor Code, Federal Permit Number, Registered Buyer Number, and Registered Crab Receiver (RCR) Number, as they apply to the operation. If the operation does not have one or more of these codes that is OK, but if they do have a code registered on their operation they should provide it, even if it will not be used in the custom processing operation. For example, if the plant will be custom processing groundfish, and on their operation registration they have a Registered Crab Receiver Number, that RCR should be provided, even though they will not be custom processing any crab.
[Image 32 – Custom Processing Relationship]
Once the purchaser/owner has the needed information they can register the new Custom Processing Owner operation. If the user making the registration is already an eLandings user they should follow the steps in Creating a New Operation for an Existing User. If they are not already an eLandings user they should follow the steps in Creating a Completely New User Account and Operation.
Operation Type:
The operation type should be Custom Processing Owner.
Operation Name:
The operation name should reflect the relationship between the purchaser/owner and the custom processor. For example, if you are setting up a Custom Processing Owner operation for your fish to be custom processed at The Fish Factory in Homer you might name it “East Pacific Seafoods @ The Fish Factory”.
ADF&G Processor Code:
The processor code should be the ADF&G Proc Code of the purchaser/owner.
Federal Permit:
You need to enter the federal permit number if the custom processing operation will process groundfish. If the custom processor is a shoreside plant, enter their Federal Processor Permit number. If the custom processor is an At-Sea operation, enter their Federal Fisheries Permit numberer thierIf the custom processor is an lant, eh.
Registered Buyer Number:
If the custom processing operation will be receiving or processing Halibut or IFQ Sablefish, you must provide a NMFS registered buyer number of the custom processor so that IFQ transactions can be submitted.
Registered Crab Receiver Number:
If you will be receiving or processing IFQ crab you must provide a NMFS Registered Crab Receiver (RCR) number so that IFQ transactions can be submitted. An RCR number is unique to each location where crab is being received, so you will more than likely need to apply for a new RCR number specific to the custom processing operation.
Port:
Enter the ADF&G port code provided by the custom processor.
Physical Operation
The Physical Operation information identifies the custom processing operation. Fill in the Operation Type, ADF&G Processor Code, Federal Permit Number, Registered Buyer Number, and Registered Crab Receiver (RCR) Number provided by the custom processor.
[Image 33 – physical operation]
When the new Custom Processing Owner operation is created, eLandings automatically adds the primary user of the physical operation as an administrative user of the custom processing owner operation. The purchaser/owner user who created the custom processing owner operation is also an administrative user for the new operation. Either can then add or remove other users as needed.
The eLandings system allows seafood processors to define grading and pricing defaults for specified species and delivery conditions. Grading and Pricing templates are displayed on the Operation Maintenance page.
[Image 34 – User Profile]
[Image 35 – Select the operation for grading and pricing template]
The condition, size, grade, and price values are displayed on the landing report grading and pricing page. The Species displayed for each grading and pricing template is a link to the Grading and Pricing Template Maintenance page. This page can also be displayed for a new template by entering a species code and condition code, and clicking on the New Template button.
The user created a specific grading and pricing template for Eastern Cut Sablefish. The grading and pricing categories are now ready to be established in this template.
[Image 36 – sablefish template]
[Image 37 – sablefish template 2]
[Image 38 – completed templates]
[Image 38 a – template displayed in a landing report]
The eLandings system allows seafood processing companies that capture landing data in their own systems during the landing process to create data files that can be imported into the system. If the processing company’s system requires fish ticket numbers during data entry they can be obtained from the eLandings Importable Fish Ticket Numbers page. The Importable Fish Ticket Numbers page is accessed from the Operation Maintenance page by clicking on the Importable Fish Ticket Numbers button.
[PIC Image 60 – Importable Fish Ticket Numbers importable numbers button]
The Importable Fish Ticket Numbers page displays fish ticket numbers that have been issued to the operations, but not yet used in a landing report import file. Operations may have up to 25 fish ticket numbers issued at any one time. To obtain more fish ticket numbers enter a number to get in the quantity field and click the Get More Numbers button.
[PIC Image 61 - importable numbers page]
The Importable Fish Ticket Numbers page has two forms of output of fish ticket numbers. The Download Selected Numbers as XML gets the fish ticket numbers as XML that is suitable for importing into a seafood processing company’s system. The Download Selected Numbers as PDF gets the fish ticket numbers as a PDF file of fish ticket worksheets.
[PIC – Image 62 fish ticket worksheet]
[Image 63 PDF fish ticket]
The fish ticket worksheets can be used along with dock tally sheets as a part of the processors workflow prior to data entry into the company system.
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.
[PIC – Image 64 common links, user profile circled]
The user’s company name, phone and fax numbers, and email address may be edited. If the user name changes, for example in the case of marriage or divorce, you must contact eLandings support and they must make the change.
The user profile allows you to set a number of preferences that affect how data and pages are displayed.
[PIC – Image 65user profile, entry fields]
[Image 66]
Number of decimals to display for weights:
This specifies the number of zero filled decimal places that eLandings will display in weight fields. Weights are tracked and stored to 4 decimal places. Significant digits are always displayed. For example, 1324.0423 pounds will always be displayed as 1324.0423. However, 205 pounds will display as 205.0000 if the Number of decimals to display for weights is set to 4 and will display as 205 if the Number of decimals to display for weights is set to 0.
[Image 68 – four decimals]
[Image 70 – zero decimal]
Number of decimals to display for prices:
This specifies the number of zero filled decimal places that eLandings will display in price fields. Most processors track price to the cent, using 2 decimals, but some price in tenths of cents, so price needs 3 decimal places. The eLandings system allows the number of decimals for price to be set to as many as 4 decimal places, or as few as zero.
Number of CFEC Permit lines:
This specifies the number of CFEC Permit lines initially displayed on the CFEC permit worksheet. You can always click the “More CFEC Permits” button to get more lines, but if you frequently have a large number of CFEC permits on landings you can set a number here that will give enough lines on the initial display of the worksheet. Likewise, if you never have more than a couple of CFEC permits on a landing report you can set this number lower to avoid taking up space on the page with blank lines.
[Image 67 – 4 CFEC Permits]
[Image 69 – 2 CFEC Permits]
Number of IFQ Permit lines:
This specifies the number of IFQ Permit lines initially displayed on the IFQ permit worksheet. You can always click the “More IFQ Permits” button to get more lines, but if you frequently have a large number of stacked IFQ permits on landings you can set a number here that will give enough lines on the initial display of the worksheet. Likewise, if you never do IFQ landings you can set this number to 1, to avoid taking up space on the page with IFQ entry lines that will never be used.
Number of Stat Area Worksheet lines:
This specifies the number of Statistical Area Worksheet lines initially displayed on the Statistical Area worksheet. You can always click the “More Stat Areas” button to get more lines, but if you frequently have a large number of Statistical Areas on landings you can set a number here that will give enough lines on the initial display of the worksheet. Likewise, if you never have more than a couple of Statistical Areas on a landing report you can set this number lower to avoid taking up space on the page with blank lines.
Number of Itemized Catch lines:
This specifies the number of itemized catch lines initially displayed on the itemized catch entry page. You can always click the “More Lines” button to get more lines, but if you frequently need to enter a large number of itemized catch lines on reports you can set a number here that will give enough lines on the initial display of the page. Likewise, if you typically enter very few itemized catch lines you can set this number lower to avoid taking up space on the page with blank lines.
Number of Grading/Pricing lines:
This specifies the number of grading and pricing lines, per itemized catch line, initially displayed on the Grading and Pricing entry page. You can always click the “More Lines” button to get more lines, but if you have a large number of grades you can set a number here that will give enough lines on the initial display of the page. Likewise, if you have don’t have multiple grades you can set this number lower to avoid taking up space on the page with blank lines.
Number of Production Report lines:
This specifies the number of product lines initially displayed on the production report entry page. You can always click the “More Lines” button to get more lines, but if you frequently need to enter a large number of products on reports you can set a number here that will give enough lines on the initial display of the page. Likewise, if you typically enter very few products you can set this number lower to avoid taking up space on the page with blank lines.
Number of Discard lines:
This specifies the number of discard lines initially displayed on the production report entry page. You can always click the “More Lines” button to get more lines, but if you frequently need to enter a large number of discards on reports you can set a number here that will give enough lines on the initial display of the page. Likewise, if you typically enter very few discards you can set this number lower to avoid taking up space on the page with blank lines.
The user profile page allows you to select a default operation that will be automatically selected in the operations selection dropdown box on the Reports Menu page.
[PIC Image 71 – Update button. user profile, operations section]