Business Context, Transaction Types and Volume
june council meeting pfmc taking up 2009/10 specs for groundfish requested dev and impl of logbook program for Ending overfishing and preventing it from occurring was the highest priority of the reauthorized Magnuson-Stevens Act of 2006 (MSRA), signed by President Bush in January 2007. In the MSRA Congress requires fishery managers to establish science-based, enforceable annual catch limits and accountability measures for all U.S. fisheries with a deadline for implementation of 2010 for all stocks currently subject to overfishing and 2011 for all others. The NMFS Northwest Region has seven or eight overfished stocks. Managment for protection of these overfished stocks is restricting the ability of the fleet to access full optimum yield sector allocations, and the ability to accurately track bycatch of overfished stocks is critical to allowing the fleet to maximize optimum yield.
The Pacific Fishery Management Council in the June 2008 meeting requested implementation of a logbook program for the 2009/10 groundfish fisheries. This logbook requirement would apply to fixed gear groundfish both limited and oa... open access, in other words, all line boats and pot boats
states declined to impl, although they are interested in success
all prior logbook programs on west coast were state
nmfs is going to impl federal logbook, not interested in designing a paper system
500 vessels, reporting daily when they fish, vessels may fish 9 months per year
More.... legislative or other policy mandates. Subsequent to this meeting the States involved declined to implement this logbook requirement, although they expressed support for the concept. As a result of the State's decisions NMFS will be implmenting a federal groundfish logbook. (All prior logbook programs on the West Coast were state programs.)
NMFS is not interested in developing a paper logbook program because the cycle time for getting data into play for management decisions is too long. (Current logbook data from other programs is available in fishery models approximately 1.5 years after the fishing events.)
There are approximately 500 vessels in the fisheries that will be covered by this program. The e-logbook conceptual design would have these vessels reporting daily when they fish. These vessels may fish for up to nine months per year, so transactions volumes could approach 500/day and 135,000/year.
Business Drivers
Near to real-time information on catch and bycatch is required as an element of national standard 1 (reduce bycatch)
have 7 or 8 overfished species, these are restricting ability of fleet to access OY sector allocations, ability to accurately track bycatch is critical to allow fleet to maximze OY
under current system logbook gets plugged into modeling future OY, where fishing is, patterns, and etc. takes 1.5 years to get logbook and observer data into the models
move to e-reporting, gps integration, all thats left is stock comp of hauls
More.... The more could include what business benefit they derive from the permit and what business risk they incur if they break NMFS rules. Is this the spot for cycle times?. An electronic logbook program provides the best mechanism for aquiring near real-time catch and bycatch information. Logbook record-keeping and reporting requires vessel operator signatures for accountability. An e-signature feature is required to make e-logbook reporting feasible.
By near real-time we mean an elapsed time of less than 48 hours from the completion of the vessel fishing activity (retrieving the fishing gear) to data analysis in the agencies catch and bycatch monitoring systems.
Business Risk in the Permit Context
NIST 800-30: Risk Management Guide for Information Technology Systems defines risk as a function of the likelihood of a given threat-source's exercising a particular potential vulnerability, and the resulting impact of that adverse event on the organization. The threat and vulnerability identification process that follows is based on NIST 800-30.
Users and functionality
Trawl fleet (whiting) is most technology sophisticated.
Longline has some 66-70 ft, also some 16' participating in live fishery in CA, no sophistication at all, using rod and reel,
e-reporting from vessel through VMS, but immediate plan is software on a PC that they send as email attachments from the vessel, as required at end of day or trip
some vessels don't currently have email
could accept some info transferred on thumb drive then take to home office and transfer via email
...
Data sensitivity and security FISMA and Privacy Act issues
...
data is confidentialThe longline fleet has some technologically advanced vessels in the 65-70 foot range, but also some small vessels, perhaps as small as sixteen feet, fishing with rod and reel and potentially no technology aboard. The current conceptual design anticipates vessels hosting e-logbook software on a PC onboard the vessel and reporting as required (at the end of a day or trip) via email from the vessel, or alternatively, reporting by email from home after completion of a day-trip. (Media combinations might be acomodated; perhaps capturing the data on a PC, saving it to portable media such as a memory stick, taking the memory stick home after the day-trip, and transmitting the file from home via email.
...
Data sensitivity and security
...
Information collected pursuant to requirements of the MSA, including permit application information, is protected by its confidentiality provisions at § 402 and under its implementing regulations at 50 CFR Part 600 Subpart E, including NOAA Administrative Order (NAO) 216-100. Additional protections of the Privacy Act and FOIA apply to such data as well as those collected under the Halibut Act.
Mitigating controls
Threat and Vulnerability Identification
...