Page 155 of 201
Each entity is generally depicted with a first attribute row indicating the primary key for that entity
– a unique identifier for every record in that entity. In some cases a primary key may be based on more than one attribute. The relational nature of these entities allows efficient
and consistent storage of data that may be stored in multiple separate tables linked together. When a sick animal or mortality is recorded in a specific pen on a specific day, it will
automatically be linked to consignment, vessel, location and other data. Data entities are the core tables into which raw data and information is captured during normal operations, such
as details on deck conditions and events mortalities, animal treatments etc. Data entered in one table is related to all the data entered in other tables through the relational linkages
between tables.
Reference entities contain pre-entered information that can be referenced or linked to reduce requirements for data entry during routine operations. For example, lists of species and
breed and class of animal can be pre-defined and entered into reference tables and information about each ship number of decks, rows, pens etc can be similarly pre-entered.
The table structure diagram shown here does not indicate data type for each attribute. Attributes may be based defined on as text string records, characters text, numbers,
spaces, punctuations, etc, dates andor times, boolean values yes or no true or false or any of many different types of numeric fields.
10.5 Application functions
A variety of information is intended to be entered into reference tables prior to a voyage. It is expected that this level of data entry would occur through a computer laptop or desktop
working either through an internet link to a central database or working on a standalone installation on that computer.
Pre-loaded information is likely to include information about loading and discharge ports name, location, country, latitude, longitude, ship specifications, animal details species,
breed and class, exporter details, climate attributes, lists of specific diseases disease, syndrome, species affected, etc and information on medicines and other products or
equipment that may be loaded onto the ship in preparation for a voyage drugs, syringes, veterinary equipment and consumables.
Some of this information may be entered once and then may not change port names and locations. Other information may need to be entered at the time of loading medication
inventory.
Multiple portable devices could synchronise with a single server at any time, allowing any number of users to merge their data prior to daily reports being generated from the server
and also allowing mobile devices to be synchronised, so they always carry the most current form of the database, allowing users to look up information anywhere on the ship. This has
the dual benefits of ensuring consistent data capture and allowing the user to access any prior data from anywhere on the vessel.
At loading, the application is intended to be able to receive data as an electronic file of individual animal records based on individual animal ID records for cattle or to accept
Page 156 of 201
entered counts of groups of animals under a mob identification system as is used for sheep.
The shipboard app hand-held interface is designed to allow simple wharf-side collection of data on start times time and date and end times for loading, and numbers of head loaded.
Events sick or injured animals and mortalities that may occur during loading can also be recorded using the app.
Once the ship sets sail, it is assumed that the on-board application will be running as a server app on a laptop likely to be managed by the AAV without any requirement for
connection to the internet. The laptop server app provides a fully functional version of the application with the added benefit that it is more suited to keystroke data entry. The laptop
server app can then be synchronised to a hand-held device running a mobile version of the application.
The intention is that the AAV will carry a hand-held device on their person at all times, so that data can be entered at any time and at any location on the ship. It also allows the user
to lookup an individual animal or pendeck to review observations or entries for that animalpendeck.
An important part of the design of the interface is to ensure that when a user AAV interacts with the device to enter data as part of a routine task, that the screen interface, navigation
and data entry procedures are all designed to be as easy and intuitive to use as possible and to minimise the number of times the user has to select an option or manually enter a
value. Key data entry tasks should be on the main menu. Each time a user initiates a key entry task the layout should be aligned to the way users think and work through the data
collection process. When an AAV approaches a dead animal to do a necropsy for example, we expect the AAV might start with recording basic information about the timing of death,
location of the dead animal on board the ship and animal descriptor information ID, species, breed, class, sex, body condition. The AAV may then record clinical signs or history, if
available. Then if a necropsy is done, findings from the gross necropsy are recorded and lastly a syndrome or one or more possible diagnoses, ranked in order of likelihood. While
different individuals may perform some of these tasks in a different order, the general pattern will be similar. The interface for the shipboard application needs to be designed with thought
given to the way that users actually perform their day to day tasks and which pieces of data might be entered at the same time. In this way the experience that users have with the
device will be aligned to the way they expect to routinely go about their job and the device will be more likely to be adopted and used.
The device is intended to be able to receive information via bluetooth or wifi linkage so that an animal RFID tag number may be scanned and imported into a record and then updated
with other information such as treatments, morbidity information or post-mortem information. Animal ID information could also be manually entered with real-time look-up functionality to
search through pre-loaded lists of animal ID records so that nearest matches can be displayed and selected at any time.
The AAV can then use the hand held device as the major data recording device for any information that needs to be recorded, reducing the need for transcription of data, and the
associated risk of errors.
Page 157 of 201
The AAV has responsibilities to submit a daily voyage report as per ASEL and the EC Animals Order 2004. The shipboard app is intended to allow collection of:
observations per day and deck on climate measures; observations at any location on animal health events any observation related to an
individual animal, pen of animals or on any relevant matter such as pen or deck conditions;
records of any treatments applied to individual animals or to pens or animals; records of any mortalities including post-mortem findings, if a post-mortem is completed;
general deck level observations on measures such as faeces, respiratory patterns, heat stress, feed and water consumption and other information;
observations about position latlong, sea and general climate conditions. The hand-held device can be synchronised with the laptop server application at any time.
The application will be able to automatically generate pre-defined reports such as the daily voyage report including where required generation or aggregated or other summary
calculations cumulative and daily counts of mortalities by deck and expressed by class, breed and species. Ad hoc queries and data exports for analysis using spreadsheet or
statistical packages will also be possible through the laptop server application.
At a destination port, observations can be collected on time and date for start and end of unloading, counts of animals unloaded and any events illness, injury, death or other
observations that may occur during unloading.
The server application can be used to generate an end of voyage report using a pre-defined format.
Finally, when internet connectivity is available the application can synchronise with a web server to upload all records into a secure archive. This will allow additional and more
detailed analyses as required and will allow operators and relevant industry bodies with appropriate authorities to use the data either for commercial business management
purposes or for whole of industry aggregate analyses and reporting.
10.6 Additional functionality
