✨ Fisheries Software Requirements
3180 NEW ZEALAND GAZETTE, No. 119 15 SEPTEMBER 2010
- Legal Requirements for Software—Any software that is submitted for approval by MFish must comply with and allow the fisher to comply with all current legislative requirements. In particular:
(a) The Electronic Software must comply with the legal requirements of the Fisheries Act 1996, Fisheries (Reporting) Regulations 2001 and any other requirements set out in this circular;
(b) The Electronic Software must allow an Authorised User to enter data into a Catch Effort Form over the course of a day so that they can meet their legislative requirements (for example to enter data "as soon as it becomes available", "on each day at sea", "before the end of the day" or "immediately on landing" or "when information becomes available from an LFR") as appropriate for the form type; and
(c) The Electronic Software must have at least the same fields presented in such manner as to reliably and comprehensibly replicate each form type as specified in Schedule 2 of the Fisheries (Reporting) Regulations 2001.
- Minimum System Requirements—The Electronic Software must:
(a) Comply with the operational workflows specified in Appendix 3 relating to the interaction of the Electronic Software with the FishServe API.
(b) Have at least the same fields presented in such manner as to reliably and comprehensibly replicate form types specified in Schedule 2 of the Fisheries (Reporting) Regulations 2001 (or elsewhere as specified by MFish) and allow data entry into each such field on the relevant Catch Effort Forms. Each form type must be in English, use standard Reference Data, be in a font size large enough to read and allow the collection of at least as many fishing or landing events as the paper form it replicates (although it may allow for more).
(c) Display the unique CE Form Number that has been issued by MFish for each Catch Effort Form created.
(d) Ensure a valid access identifier and password combination has been entered before a user is able to create, endorse, export, import, copy, discontinue, sign or submit a Catch Effort Form.
(e) Display each CE EDT form’s current status when the Catch Effort Form is viewed.
(f) Have the facility to allow the Authorised User to manually save and/or endorse the information they have entered into a Catch Effort Form at any time.
(g) Ensure that the event history of a form can be viewed both before and after a Catch Effort Form has been digitally signed.
(h) Transfer the content of a Catch Effort Form completely and accurately to the API.
(i) Ensure that if a Catch Effort Form is amended and re-signed, all the different versions are identifiable to the Authorised User who made the changes.
(j) Remind the Authorised User that they have legal responsibilities relating to the completion of Catch Effort forms before they digitally sign Catch Effort Forms.
(k) Allow the Authorised User to enter whatever information they wish into a user completed field within the confines detailed in the software development kit.
Next Page →
NZ Gazette 2010, No 119
✨ LLM interpretation of page content
🌾
Fisheries Electronic Software Requirements Circular 2010
(continued from previous page)
🌾 Primary Industries & ResourcesFisheries, Regulations, Electronic Software, Reporting, CE EDT, MFish, FishServe