What are our statuses and what do they do? Only Agency users can change the status of operations. Users cannot see any reports in an archived operation.
What are our authorizations and when does inheritance occur
We need an example operation in each status, and we need to give a user access to each example operation
amackerel
Pending - The Hobbit Loves Halibut
Enabled - King Fish Processing
Operation Status Definitions
...
Status
| Info |
|---|
Operation status represents whether the operation has been approved by agency staff or if has been closed or removed for any reason. Refer to the table below to see details on the various operation status's that exist. |
Status | Definition | How to get to next status |
|---|
| Common usages | |
|---|---|
| Pending | An operation that has been created, but not yet approved by agency staff |
Enabled is the next status
Suja looks at application and changes operation status in agency| . | Initial status upon creation of a new operation. Agency staff will examine the application and change the operation status in the system if application is accepted |
If operation is brand new, users must be authorized/enabled as well
If an operation already exists, they may add as many users as they want
Buying stations are automatically enabled
Custom processing operation creation emails Suja, notifying her, but no form submission is required/approved. Upon creation agency staff must also enable the users. An exception to the rule is that Buying Stations are automatically enabled upon creation, as the parent operation is already approved. To create Custom Processing operations no form submission is required, but agency staff will get an email to review the operation. | |
| Enabled (Open) | An operation that is open for business, with all functionality |
| enabled. | A fully functional operation that has been approved by agency staff and is capable of work. See closed or archived statuses for why and how an operation may be closed or archived | |
| Closed | An operation that was Enabled, but can no longer create reports. The operation may see and edit existing reports |
| . | The business is closed and the harvest history is not sold to anyone and the plant has been completely closed - there are no eLandings users and all record keeping and reporting requirements have been fulfilled |
EG Harbor Crown
What you think of as "out of business"
. Any agency staff with admin rights may close an operation. |
Common reasons |
for closing an operation are restructuring (sold, partnership changes, mergers, closed, etc.), |
and the new owners have a different EIN or Proc Code/permits |
In the future we may wish to consider the difference between closing down and restructuring a business relationship
There are at least two restructuring scenarios
In one, the eLandings reporting history, people and plant go to the new operation
In the other, the plant goes to the new operation. Or going out of business or no longer operating in Alaskan waters. | |
| Archived | An operation that was Enabled, but is no longer accessible by processor users (including reports). Archived operations remain viewable in |
| the system by agency staff. | Agency users may, if necessary, move an Archived operation to Closed status for report viewing and/or editing. Any agency staff with admin rights may archive an operation |
What Is Happening Today
| Pending (Admin users) | Enabled(Open) | Closed | Archived | Can users see operation in 'Administer Operations' screen? | y for admin, n for normal | y | Can users see operation on 'Display Reports' screen? | n | y | Can users see operation on 'Display Reports' screen search for reports section? | n | y | Can users see operation on 'Display Reports' screen 'search for observer fees' section? | n | y | Can users see operation in PTI thumbdrive prep? | y | Can users see operation in PTI LR upload? | y | Can users see operation in PTI operation override? | ? |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Can agency users see operation in Agency desktop? | y | y | y | y | |||||||||||||||||
| Can users see operation in sealandings? | y | n | Is operation selectable as a user's default operation? | n | y | Can users edit operation? | n | y | Can user login? | n | y | Can users see operation dropdown when editing an existing landing report? | n | y | Can user select operation for data extract? | n | y | Can create COAR report from landing report? | n | y . |