We encourage industry integration with eLandings. Currently at least two processors generate and submit XML reports directly into our system, and other processors extract XML reports from our system for import into their systems. We are planning to add vessel logbook reporting to eLandings, and anticipate accepting logbook reports from multiple independent software vendors. We expect these types of system-to-system data exchange and integration to increase in number and importance over time.
When outside parties interface with our system unanticipated failures occur due to specification misunderstandings, ambiguities, and error.
This section documents ideas and notes pertaining to a test and certification service for eLandings interface consumers. This service will allow these outside parties to exercise our interfaces and discover points of failure in the context of an interface test system. This service will also provide the technical components of a certification process such that outside parties can submit a specified suite of test transactions, and our system can judge whether their test transactions interacted with our system precisely according to our specifications.
When our interface test and certification service is operational we will encourage outside parties to use it during development of interfacing software, we will allow independent software vendors to use it to certify software which they wish to represent to industry as compliant with our specifications, and eLandings support staff will use it for troubleshooting production problems.
Contents
Resources
Thanks to Tom Kagehiro for this reference to the Australian Fisheries Management Authority (AFMA) guide to e-Logbooks for vendors, including performance measures to certify software products.