Page 159 of 201
end of the voyage the shipboard app needs to be able to export key data and information collected during the voyage into a whole-of-chain system.
10.7 Learnings from prototype development and feedback
Our purpose in developing prototype applications was to use a range of low cost, prototype solutions in order to demonstrate functionality to potential industry users of such a device,
and capture their feedback.
This section summarises the findings from our experience in designing and developing the prototypes described in this chapter and incorporates feedback from industry stakeholders
derived from hands-on testing of prototypes and from discussion of general functionality.
These points are expected to be useful along with comments earlier on the design attributes and database table structure, if a fully functional mobile application were to be developed.
10.7.1 Support for mobile application
There was good in-principle support for the concept of a mobile application using low-cost hand held devices to capture animal health and other related performance monitoring data
during the voyage.
If a system is designed that is easy to use, efficient and intuitive, it is highly likely to be adopted and is highly likely to result in an improvement in the quality of collected data.
10.7.2 Functionality must not depend solely on the internet
A large number of apps can only function effectively while high speed internet access is available and live. However, on board a livestock vessel even in port and particularly on the
livestock decks it is common for signal degradation to limit receiving of phone calls and data. Once at sea, even if internet is available on the bridge, it is likely to be expensive and
restricted. The p
rimary requirement for an “app” is that it can run completely “stand-alone”, and that it can be backed up during a voyage to a simple but specially configured computer.
This can be achieved very simply by installing a server app on a laptop. It is assumed that every AAV will have a laptop in their cabin.
While the shipboard application must be able to function independently of internet access to allow data collection during the voyage, the ability to link to via internet to a web based
database remains the most effective method for managing data across the supply chain and across multiple separate voyages.
10.7.3 User interface is critical
The biggest benefit of the prototypes was the feedback on user interface. There is no question that the prototypes worked, but early testers of the device provided strong feedback
on the importance of ease of use and the importance of being able to intuitively navigate around the application. Feedback was likely to reflect the fact that the export industry may
not include people with the highest knowledge of apps and hand-held devices in general and this will change over time, however the issue is considered to be fundamental to
development of a successful app.
Page 160 of 201
All aspects of the interface must be intuitive including configuration. It is likely to be used by staff with a wide range of educational backgrounds working in a remote location.
Data entry must be as simple as possible – the use of drop down lists, tick boxes etc to avoid typing is important.
Uncluttered design is vital – low light, difficulty in keeping spectacles clean etc mean that the display must be easy to read.
The minimum required dataset should be small. Overly onerous requirements to complete all fields will prevent user compliance.
From a design perspective this means understanding what activities an AAV will routinely perform and how they expect to be recording data and related information. This process will
guide the design of the application and in particular the user interface – what menu items
should be on what screen and what optionslinks need to be designed so that each routine activity can be achieved with minimal interaction with the hand held device.
10.7.4 The device can’t be precious, but the data is
