Operation Types and Requirements

CATCHER SELLER (CS)

1. Use eLandings to report their own landings and dockside sales - may include CDQ groups.
2. Catcher sellers NOT using eLandings that are filling out a paper fish ticket which is manually entered by ADF&G staff in the Agency desktop application. 
   1. An operation is then created for them. If they use eLandings in the future, they're added to the existing operation.
   2. Ex. A CS that is catching and selling bait, these fish tickets are almost always done as paper tickets.

1. Always a C-code
2. Sometimes a FFP if fishing in federal waters
3. Sometimes a RB if they fish IFQ

CATCHER VESSEL (CV)

1. Use eLandings to fill out elogbook (CV ELB)
2. The ONLY report they have to submit is elogbook, No LR's, No PR's

1. Always ADFG vessel #
2. Sometimes a FFP if fishing in federal waters
3. No Port Code
4. No FCode

BUYER EXPORTER (BE)

1. Use eLandings to set up Custom Processing operations

1. Always an FCode (issued by DOR)
2. No federal permits
3. No ADFG Vessel #
4. No Port Code

1. Uses eLandings to report fish that they catch and they can sell this catch out of state
2. Allowed to have someone else custom process for them.
   1. Not allowed to process their own catch. This is the primary difference of a Direct Marketer operation.
   2. Federal regulations classify freezing as processing. If exporting frozen catch a Direct Marketer operation may be more suitable.

1. Always an Fcode (issued by DOR)
2. Always an ADF&G vessel #
3. Sometimes FFP
4. Sometime Registered Buyer permit if catch sold is IFQ

DIRECT MARKETER      (DM)

1. Uses eLandings to report fish that they catch and they can sell this catch out of state
2. They often have someone else custom process for them

1. Always an FCode (issued by DOR)
2. Always ADFG Vessel #
3. Sometimes a FFP
4. Sometimes a RB if they fish IFQ

1. Use elandings to report catcher vessel harvest

1. Always an FCode
2. Sometimes has a FPP
3. Sometimes has a RB
4. No ADF&G #
5. Always a Port Code

1. Catches and processes fish while at-sea
2. Sometimes a catcher/processors "acts" as a mothership and takes unsorted codends from catcher vessels or other catcher/processors (called "bags over the side")
3. If a CP is not going to have any fishing and processing activity in state waters, they can be an EEZ operator only.  They get a ZCode from ADFG (instead of FCode from DOR).  There are different tax rates for the 2 permit types so there is financial incentive to document activity under the 2 permit types.
   1. Sometimes vessels will want to change this permit in the middle of year.  
   2. And sometimes vessels want to retain both permits and fish under 1 for some activity and the other for other activity.  

1. Always a FFP
2. Always a state permit -  either FCode or ZCode
3. Sometimes RB for IFQ
4. Port Code is used to identify CP vs Mothership
5. Port code always = FCP, (however, sometimes the same boat can act as Mothership & then port code = FLD
6. Always an ADFG Vessel #

1. Receive deliveries from CV's and process fish onboard (offload finished product).
2. Sometimes Mothership activity comes from CP's that are "acting" as motherships

1. Always a FFP
2. Port Code is used to identify CP vs Mothership
3. Always have a state permit - could be either FCode or ZCode
4. Never RB
5. Port code always = FLD
6. Always has ADFG vessel number

1.  Recieve fish from CV's and tenders.  Basically similar to a shoreside processing plant – but they are semi-permanently moored close to land and can move.
2. Different from a mothership because these boats achor up close to shore when taking deliveries (vs mothership that takes deliveries out on the fishing grounds and move around)
3. Examples of IFPs are: Northern Victor, RM Throrstenson, Gordon Jensen

1. Always have an Fcode
2. Sometimes has a FPP if taking deliveries from vessels with FFP
3. Sometimes has a RB permit if taking IFQ
4. Sometimes has RCR if taking crab
5. Always has ADFG #
6. Always has a Port Code = IFP

1. This operation type connects 2 unique operations together to document an owner and processor of the fish.
   
   1. Example: Unisea custom processing crab for NSEDC
2. Custom processing relationships can include tenders and buying stations as agents for the owner or processor.
   1. Example:  AK General Seafoods Ketch and Seafood Producers Coop in Sitka each with tenders and buying stations, AND a custom processing relationship for each other.

1. Always has 2 FCodes: primary is the owner; secondary is the custom processor.
2. Sometimes has a FPP (if taking groundfish) and FPP is the processing entity.
3. Sometimes has a RB permit (if taking IFQ) and RB permit is the processing entity.
4. Sometimes has RCR (if taking crab) and the RCR is unique to the custom processing relationship.  Owner gets the RCR permit and identifies the processing location.
5. Sometimes has ADFG # (e.g. IFP)
6. Always has a Port Code = location or operation type of the processing entity.

1. Receives fish at a shoreside location for a plant/receiver at a different location. The buying station does NOT process fish.
2. Classic buying station example: Icicle Seafoods buying station in Homer. They buy fish and then truck it to the plant in Seward.
3. There can be tenders association with the buying station

1. Always has an FCode that is always the same as the parent plant operation
2. Sometimes has FPP if the process fedeaqlly managed groundfish. and this will always be the same as the parent.
3. Sometimes has a RB permit if they process IFQ. The RB permit is sometimes the same as the parent OR it can be a separate RB permit - whether the have the same or different RB permit depends on OLE
4. Always has a port code and this can be same or different from port code of parent.
5. Never has a ADFG vessel number, but might have a vehicle number.
6. Has the idea of a buying station name - which processors want to show on the fish ticket.