Crew Data - Forums Archive

DaveM

2009-09-21 02:39:32

Crew data...how about a bit of input from the board on what they think about the current ADF&G proposal requiring us to collect economic data on crew members?

As well, what is ATA's stand?

Before I give my 2 cents, hearing from the local fisherman is interesting...so, LETS HERE IT..

or, perhaps you're not familure with this issue? call Dan Bruce. He's the point at ADF&G.

Ocean Gold

2009-11-09 19:35:13

Dan Bruce?? should be Geron Bruce not Dan, and Jan Conitz is the person you want to call and speak too as the point person on this. here is a link to the three options they are considering http://www.admin.adfg.state.ak.us/confluence/display/CREW/Candidate+software+requirements+specifications+for+crew+data+collection

Lets here some opinions on what this will mean

Ocean Gold

2009-11-11 18:34:19

Send comments to oceangold@seafa.org we are thinking about attending the meeting in Anchorage on Jan-12-10 Kathy has been invited to attend so give us what you got, please. The burden will be on you! Here is a summary that went out to the UFA board:

Topic: ADFG Crew Data Project

Issue

ADFG has released the review draft of the feasibility study on 3 possible methods of gathering crew data. They include:

Vessel Operator Report Option – vessel operators will enter crew data after the trip or season. (You would be able to go online and get a summary sheet of each landing report / fish ticket that you would then associate crew data number with each landing)

Could report data after a fishing trip or end of the season

The landing report becomes the main data unit and the crew data is added to it.

Direct reporting reduces the number of hands data passes through (more accurate)

Doesn’t burden processor or tender

Allow the collection of data such as crew share %’s

Direct reporting might require additional prompting to have data turned in/ might be penalty associated for failure to report

Even if you didn’t have crew would need to report

Possible issue of when fish ticket data is entered in the system

Data would only be submitted electronically or maybe an option by telephone IVR system

Would allow for pre-season crew entry

Electronic logbook option – data files from electronic logbooks will be submitted after the end of the fishing season. (You would be logging the comings and goings of a crew member)

Logbook becomes primary data unit and then is associated with landings and/or fish tickets

Direct reporting reduces the number of hands data passes through (more accurate)

Doesn’t burden processor or tender

Allow the collection of data such as crew share %’s

Direct reporting might require additional prompting to have data turned in/ might be penalty associated for failure to report

Even if you didn’t have crew would need to report

Landing Report option – Would capture crew data at the time of the landing on the landing report or fish ticket much as you do the statistical area.

Advantage to this method is that it insures the data is captured

Increases data burden on processors who aren’t involved

Increases duplicative data entry requirements since it would have to be entered for each landing

More prone to entry errors and no verification involved

Similar in all three options are the reports that would be generated and available for review:

STANDARD REPORTS AVAIABLE:

Crew Activity by Community: will summarize the number of fish tickets and number of crew members by community or residence. The report will cover a specific year and contain the following data, residence city; residence state; number of crew members and number of fish tickets for those crew members

Crew Activity by CFEC Fishery: will summarize the number of fish tickets and number of crew members for each CFEC fishery. The report will cover a specific year and contain the CFEC fishery, number of crew members and number of fish tickets for those crew members

Active vs. Inactive crew licenses and permits report: will list communities by state and city and contain the follow data, community, number of ADFG crew licenses registered in that community; number of crew licenses that have actually been reported on landing reports; number of CFEC permits registered in that community; number of CFEC permits that have been reported on landing reports as crew; number of CFEC permits that have been reported on landing reports as fish ticket CFEC permits; number of permits that have been reported both as crew and as fish ticket permit holder;

Fishing Longevity Report: will list fishermen by community. The report will cover a specified set of years and will contain the following data: fishermen CSN (identifying number); year; licenses and or permits held for that year; whether or not the license/permit was involved with any landings

Fishery Crew Statistics: will list the crew activity by fishery and community. The report will contain the following data: CFEC fishery; number of vessels that made landings; average number of crew on each vessel; and number of crew for each community that participated in the fishery.

Fishery Crew Effort: will list the crew member fishing days by fishery and community and contain CFEC fishery; number of crew member fishing days (Fishing days will be calculated from the days fishing for each vessel multiplied by the number of crew on the vessel.) Fishing days will be shown by week and by community

Crew Landing Participation Detail: will provide a detailed participation history for each crew member. The report will contain the following data: crew member name and CSN; landings where the crew member was reported as a participant containing the following data: landing date; landing location; and itemized catch that was delivered including species, condition and pounds.

The crew review web function interface will allow a crew member to review the fish ticket data for each fish ticket where the user was listed on the crew license worksheet. The user will be able to review fish tickets for any of their licenses or permits, not just the one they used to login. Te user will provide a year for the fish tickets they want to review and will display each fish ticket with the following information landing report id; fish ticket number; vessel ADFG number and name; date fishing began; date of landing; port of landing; processor name and tender name if applicable. The crew data interface will allow the crewmember to enter a text message notifying ADFG with problems with the data (will be a time frame – won’t be able to notify that you thought there was missing data a couple of years later)

Vessel operators will be able to view only the crew licenses that they have entered or updated.

Vessel operators will be able to look up a crew license number if they do not have the information on hand but must provide the last name, first name or partial first name can be entered. The system will provide a list of individuals whose last name matches the last name entered, and the data displayed will be: first name, last name, age, city and state of residence, crew license number or CFEC permit number.

Action you would like UFA to take

· UFA needs to come up with a recommendation on which option they prefer before the January 12th meeting and other recommendations regarding the project.

More Information

· Feasibility Study: http://www.admin.adfg.state.ak.us/confluence/display/CREW/Candidate+software+requirements+specifications+for+crew+data+collection

·

· Tentative question and answer session with contractor of feasibility study on January 6th

· Tuesday January 12th workgroup meeting in Anchorage to review and provide recommendations to ADFG on project.

Kathy Hansen

SE AK Fishermen’s Alliance

9369 North Douglas Hwy

Juneau, AK 99801

907-586-6652 phone

907-523-1168 fax

seafa@gci.net

http://www.seafa.org

grabber

2010-01-06 16:45:24

what is the purpose of collecting crew member data? Is it to help create a dollar multiplier for commercial fishing? They all ready have access to crew licenses, so they can get a deomgraphic in terms of residency and such. Would it lead to % minimums? Contract requirements? I would just like to know the exact purpose since they have $250,000 budgeted for the program. It would have been handy during the implementation of IFQ's.

Ocean Gold

2010-01-10 04:05:24

comprehensive collection of crew data, attach actual landing data to each crew member in case a Quota Share program comes along in the future.

There is already a federal law that requires a crew contract that spells out how the compensation will be figured at a minimum.

tacorajim

2010-01-10 14:08:34

There is already a federal law that requires a crew contract that spells out how the compensation will be figured at a minimum.

Do you have a link? I couldn't find it on google.

Ocean Gold

2010-01-11 16:13:28

46 USC Section 10601

Sec. 10601. Fishing agreements

(a) Before proceeding on a voyage, the owner, charterer, or managing operator, or a representative thereof, including the master or individual in charge, of a fishing vessel, fish processing vessel, or fish tender vessel shall make a fishing agreement in writing with each seaman employed on board if the vessel is - (1) at least 20 gross tons as measured under section 14502 of this title, or an alternate tonnage measured under section 14302 of this title as prescribed by the Secretary under section 14104 of this title; and (2) on a voyage from a port in the United States. (b) The agreement shall - (1) state the period of effectiveness of the agreement; (2) include the terms of any wage, share, or other compensation arrangement peculiar to the fishery in which the vessel will be engaged during the period of the agreement; and (3) include other agreed terms.

Here's a link to a draft crew agreement https://www.seafa.org/old_site/form/insurance/SEAFARCrewContract.doc

kjwelder

2010-02-06 17:48:05

Thanks for all info

kj