TDW-11: 24-28th April 2017, Noumea, New Caledonia Data issues for discussion TDW-11: 24-28th April 2017, Noumea, New Caledonia

Data issues for discussion Data access/sharing T2 ‘data-centre’ hosting outside SPC Process to resolve errors in TUFMAN 2 Errors not resolved for a period of time … Verification of shared data… Imported data (e.g. E-Reported, iFIMS) Potential new roles - companies/vessels ? New tools/functionality ? (you tell us !)

Data Access/Sharing    Current data-sharing mechanisms Now, several new mechanisms for sharing data Understanding complexity in the rules… Data-sharing business rules built into DB systems    The same would apply to chartered vessels, and chartering State reporting responsibilities

Data Access/Sharing TUFMAN 2 – how data are shared… Uses NTSA, but with practical considerations (not yet unconditional). Shares other countries’ data … if activity in your EEZ if your flagged vessel Where not NTSA, some sharing relies on licensing US PS Treaty  by EEZ only FSM Arrangement  based on FLAG and EEZ Japan  based on EEZ Countries that have not ratified NTSA data sharing will be restricted under TUFMAN2 and will impact on the sharing to other countries…

Data Access/Sharing Questions to consider… Please consider and discuss … The current data sharing rules (as you understand them…) The pros/cons to your country by sharing How can we improve the situation ? Please discuss and provide a list of (i) issues and (ii) suggestions for improvements

Data-centre hosting outside SPC What is it ? YOUR DATA are stored on secure servers at SPC … … new proposal to use a secure Data Centre outside SPC … PROS Faster access, less down-time, automatic backups, etc… Already good precedents… (e.g. VMS data) CONS Cost ? (.. But not excessive and covered by SPC) Initial arrangements to transfer data (one-off…)

Data-centre hosting outside SPC Questions to consider ? In small working groups, consider… Is data-centre hosting outside SPC feasible for your country ? If not, why not ? List the points you would need to take back to your country to seek authorisation for SPC to move to data-centre hosting outside SPC… Please discuss and provide a recommendation

Process to resolve T2 errors What are the issues ? 1. Errors not resolved for a period of time … ... this is when errors in T2 data entry have not been attended to for more than one month … Potential solution Countries provide authorisation for SPC to resolve these errors (on their behalf) after one month (…or an agreed period of time) Please discuss and provide a recommendation

Process to resolve T2 errors What are the issues ? 2. Verification of shared data… ... data shared to you must be ‘verified’ before it appears in DORADO … … some countries are not ‘verifying’, so data not in their DORADO reports ... Is verification too onerous? Would you rather just trust data entered externally? Or maybe only from certain countries/OFP? Another option is to have all countries considered as verified after only one country has verified the data Other solutions? Please discuss and provide a recommendation

Process to resolve T2 errors What are the issues ? 3. Errors from data imported from other systems ... e.g. errors identified in iFIMS elog data … Proposed solution : Countries use the T2 ‘export errors’ to send back to vessel Vessel revises elog data to correct errors FIMS resubmits elog data to T2 Is this acceptable to countries ? Please discuss and provide a recommendation

Process to resolve T2 errors What are the issues ? 4. Should vessels/companies enter/fix data in T2 directly ? … what data ?  Logsheets and unloadings Questions for discussion : should vessels/companies have a special, but restricted ‘role’ in T2 ? will future CMS/CDS/QMS require this ? What questions need to be taken back to your country… Please discuss and provide a recommendation

New tools/functionality ? What would you like to see ? …you tell us ! “Brainstorm” discussion … what data management tools/functionality are missing from your country ? Please discuss and provide a list of suggestions…