Guide for vendors

We are making the data transfer specification for electronic logbook reporting publicly available. Software developers can then develop an electronic logbook product for capturing and returning logbook data to Australian Fisheries Management Authority (AFMA). AFMA will accept electronic logbook reports provided it meets published specifications.

Vendor process is:

  1. Develop application or modify existing application
  2. Submit applications for validation and certification
  3. Include hash key and certification details in software release
  4. Distribute, sell and support of certified application
  5. Manage certification status and response to requirement changes

Software developers wishing to develop an electronic logbook returns system must provide their software to AFMA for accreditation, a process to ensure that the software will send electronic logbook reports which meet the AFMA specifications.

Developers must register with AFMA prior to lodging software for accreditation.  AFMA is currently developing a series of test scenarios which a software product must pass to be certified before AFMA will accept electronic logbook reports from these software products.

The electronic logbook reporting data specifications are method and or fishery specific. Specifications are developed and schemas released when there is sufficient interest from a fishery.

The current releases and an accompanying information package can be obtained by email application to the Co-ordinator at elogs@afma.gov.au.

Vendors perspective

It is expected that vendors may seek to extend the functionality of their vessel management system software by including in the application a module with the ability to allow fishers to submit electronic logbooks that are compliant with AFMA’s published requirements.

There are a number of steps required by vendors prior to an e-Log app becoming operational in a fishery. Typically the vendor would build an e-Log application that produces a schema consistent with AFMA’s published requirements, the application would be certified by AFMA, incorporate in the product the necessary hash keys and, distribute, sell or upgrade and then support the application to the client base, and manage the certification status of the product consistent with the published terms of certification.

These steps are outlined in further detail below.

elogs - Vendor's perspective

Download Vendors Perspective (58kb)

1 Develop application or modify existing application

This step builds a new application or modifies a current application to meet AFMA published requirements.

Inputs:

AFMA published schema

All approved logbooks both paper and electronic

Outputs:

e-Log application

Resources:

Programmers, developers and testers

2 Submit applications for validation and certification

This stage validates that an application conforms with the published requirements. The vendor’s product is then certified when the application is successful in producing valid schemas over the course of the test plan.

This stage requires the following:

  • Support the testing activity as needed
  • Issue resolution where that might arise
  • The issue of certification by AFMA
  • Acceptance by vendor of conditions of certification
  • Contact AFMA to register intent to submit an application for testing and certification

Inputs:

e-Log test plan

Test data

e-Log application

Outputs:

Test results

Certification (reasons for certification denial)

Resources:

e-Log application

AFMA test team

3 Include hash key and certification details in software release

This step involves the inclusion of the AFMA issued hash key into the certified application.

Inputs:

AFMA issued hash key

Outputs:

Completed application ready for marketing release

Resources:

Programmers, developers and testers

4 Distribute, sell and support of certified application

This step delivers a certified application to fishers. The vendor at this point can advertise their product as being certified as AFMA compliant by fishery, by method and whether for email or web based submission consistent with the certification.

This step might also include managed patch releases of lookup value codes and other products and services to fishers including vessel management software.

Inputs:

Certified e-Log application

Outputs:

Certified application deployed in a fishery

Resources:

Installation and trouble shooting support to fishers

5 Manage certification status and response to requirement changes

These step relate to the actions need to support and maintain the certification status of the application.

The vendor at this point can advertise their product as being certified as AFMA compliant by fishery, by method and whether for email or web based submission consistent with the certification. The vendor might also include managed patch releases of lookup value codes and other products and services to fishers including vessel management software.

Within this step there are three distinct sub steps or scenarios;

  1. The monitoring of AFMA requirement change
  2. Vendor change requests
  3. Obligations under the terms of certification.

The monitoring of AFMA requirement changes. Changes that might be but not limited to the following;

  • The release of a new schema for a fishery or method
  • A change of business rule
  • A code change that might require a patch release but not recertification
  • A change to an existing schema for a method or fishery
  • The expiry of certification status for an application

Inputs:

Expired application certification notices
Code change notifications
Notifications from AFMA regarding new schema releases
Notification of rule changes

Outputs:

New certificates
Application upgrades out to fishers
Patch releases

Resources:

AFMA and RAGs

Vendor change requests

Vendors may need to modify a certified application for a number of reasons including new operating software conflict issues or the new issue of enhanced vessel management software.

Before distributing a modified e-Log application to fishers the vendor must notify the certification delegate at AFMA and outline the changes. AFMA will advise if the extent and nature of the changes would require recertification of the application.

Obligations under the terms of certification

Under the terms of certification there are obligations to advise AFMA if a product is to no longer be supported by the vendor and there would need to be an expiry put on the certification status. There is also the requirement to provide a level of technical expertise on the certified e-Log app product, be that in a litigation sense or even at a Regional Fisheries Management Organisation level.