Page 162 of 201
controls in a shared centralised database, such that each user has their own access user name and password and can be restricted to access only those records that are relevant to
their username. Different users may have different levels of authority ability to read but not change any record, ability to change data or enter new data, ability to authorise others and
so on. The levels of security implemented in shared systems can be made as complex and powerful as are required.
We have also developed relational databases where the data tables back end of the database are separated from the user interface and functionality front end of the database.
This allows a common or shared interface front end that can be maintained and updated as required, that could be web-based but that does not store any sensitive data. Individual
users exporters for example could then install their own individual copy of the data tables the back end and store their own data and no-
one else’s data in these tables. Users could then manage their own levels of internet access to their own data tables. When a common or
shared front end is linked to a specific back end then the full functionality of the application is enabled but on
ly for the specific user’s data. Finally, it is possible to develop a software application and associated server a full working
system and have each separate user install their own separate copy. This approach loses much of the benefit of central data storage and requires potentially more investment in
product maintenance and upgrades since they may need to be updated across multiple individual users and each version may need more development to retain backwards
compatibility.
10.7.8 Flexibility vs specificity
Our starting brief was to build a system that would meet current regulatory reporting requirements based on the daily voyage report and end of voyage report.
The data requirements for these regulatory reports also offer considerable strategic and business benefit to the export industry through QA and to individual exporters for fine tuning
business operations to improve performance and profitability.
Any system needs to be sufficiently flexible to allow industry needs to be achieved. If performance monitoring and reporting requirements change then the system needs to be
flexible enough to be capable of changing to meet future needs.
10.7.9 Real time reporting
One of the most significant benefits of the shipboard application is the ease with which regular reports both mandatory and customised can be compiled. Essentially, as long as
the data from devices has been synchronised with the database, any report should require only the push of a button. Such reports could include:
daily voyage reports; end of voyage reports;
company specific reports; autopsy reports;
animal histories; treatment summaries; and
pharmacy inventories.
Page 163 of 201
Regardless of the type and content of the report, the most common user question about using a portable device to record shipboard data was what
’s in it for me? The prospect of
being able to push a button to produce simple, accurate reports was well received. This question also extends to industry decision makers exporters, ship owners who may
make be looking for return on investment in some tangible way reduced costs – including
compliance costs and improved performance reduced morbidity and mortality.
10.7.10 Integration with other systems
The voyage requirements for data collection and monitoring are discrete and defined. They start with loading of livestock onto a vessel and end with unloading at a destination port.
It is possible to develop a shipboard application and web-based server independent of any broader initiatives associated with whole of chain performance monitoring.
If and when whole of chain performance monitoring is implemented, then the shipboard application just needs to be able to communicate at both ends upload loading plans or lists
prior to the voyage starting and download voyage data and unload lists when the voyage ends to allow effective integration across the chain.
There is sufficient knowledge and technology to build a shipboard system now. If a broader, whole of chain performance monitoring system is developed in the future, the
shipboard application will be able to function as one component within that broader system.
10.7.11 Development steps
