The functionality necessary to provide the e-logbook certification is in the final stages of development.
Task/Milestone | Due Date | Staffing |
---|---|---|
finalize draft guidelines |
|
|
reconcile final guidelines with draft regulations |
|
|
regulatory review |
|
|
regulatory notice, comments and responses |
|
|
respond to certification requests | as needed |
|
The functionality necessary to process e-logbook data submitted on portable media was developed during the PIFSC's electronic reporting pilot program which was conducted from 1998-2003. As a result of the pilot, and of this e-signature design effort, requirements have matured and some changes are required. The implementation plan for these changes is:e-fishticket was developed as a pilot project two years ago and has been used in the Pacific whiting fishery for the past two years. It is currently being evaluated by West coast states (Washington, Oregon and California) for broader adoption. The pilot e-fishticket did not include an e-signature, but, technically, e-signature requires only minor enhancements to the existing system.
Task/Milestone | Due Date | Staffing |
---|---|---|
develop specifications for required changes |
|
|
develop test plan |
|
|
Task/Milestone | Due Date | Staffing |
implement changes |
|
|
execute test plan and correct defects |
|
|
production readiness review |
|
|
go live |
|
|
The functionality necessary to process e-logbook data submitted via email was developed in the Alaska Region. The Alaska Region program will need to be adapted to the Hawaii Longline Logbook XML schema. The implementation plan for these changes is:
knowledge transfer to Hawaii developers |
|
|
develop test plan |
|
|
implement changes |
|
|
execute test plan and correct defects |
|
|
production readiness review |
|
|
go live |
|
|