Page 146 of 201
and software applications that might be considered for future development. In part this limitation recognised the fact that full development of a read-to-use product would be risky,
because stakeholder acceptance would not be guaranteed and the costs associated with producing a ready-to-use product were considered to be higher than the allocated budget.
10.2 Development approach
The approach used for development of an IMS was based on the following general principles:
The focus was on a system used by an AAV or stockperson during a voyage. Based on a three level framework:
o Secure web-mounted database accessible from any internet-capable device
could receive data directly from remote devices. o
Able to be run as a stand-alone server on a laptop during a voyage, thinking that an AAV would have a laptop running the application in their cabin. The stand-
alone server could wirelessly back up the mobile devices when they are in range. o
Self-contained, mobile app running on a hand-held device such as an Android or iOS device, including smartphones to allow data capture at the point of
observation pen-side or animal-side. User interface must be as simple as possible, intuitive and easy to use including:
o Incorporation of drop down boxes and look-up tables to minimise the need for
typing of information, error checking on data entry where possible and effective table design to ensure information is only entered or captured once.
All components of the system must be relatively cheap, robust, flexible and able to withstand the rigors of the voyage environment.
o Android and iOS based systems were preferred, because there are many options
for developing apps for these systems, they allow choice of many different hand- held devices and the costs for these are relatively low 2011 prices indicated that
devices could be purchased for AUD200 each. o
High specification, military type devices provide a more rugged option, but have much higher costs for purchase AUD 2-5,000 and in many cases for app
development. The minimum outputs were based on regulatory requirements daily voyage reports and
end of voyage reports, recognising that future systems could require the flexibility to add additional output functions based on future quality assurance reporting requirements and
other measures supported by industry. The system should be able to collect and store a variety of media or data types including
simple data text, numbers that are entered or selected, scanned ear tag ID values, photosvideo and audio recordings of observations, as well as importing data from other
devices such as climate log devices. Modification of existing off-the-shelf apps or software products was selected for initial
development of an app, because this allowed relatively low cost development of apps for testing purposes.
The project team developed a database table diagram and accompanying notes on work and data flows that was based around our knowledge of routine data flows on-board an
export ship and reporting requirements. This was used to inform development of all prototypes.
10.3 Prototype systems
