1. Tripartite meeting Korea, Seoul, 14 – 15 September 2006 Agenda B.10 Sharing information for ships in service (incident information sharing) Konstantin Petrov Manager, External Relations, Lloyd’s Register LR IACS General Policy Group Member Chairman, Small Group on EWS review

2. IACS EWS Review What has triggered the review: – Tripartite in Japan, 2004 Minutes: “ INTERTANKO also asked how are we (IACS) going to use information on damages experienced at shipbuilding or during ship operation as a feedback system and whether this information goes back to the shipyard. IACS Early Warning Scheme is supposed to address cases when damage occurs to trace these issues.” – EMSA report on safety of DH oil tankers : “Additionally, a system of formal communications between owners, operators, class and builders should be established, to enable information on vessels with significant fatigue to be transferred between interested parties, when sister or similar vessels were known to be in service.”

3. IACS EWS Review The task of IACS GPG Small Group on EWS review: Review the current EWS to identify the technical details of the requirements Review the EMSA report on Double Hull Tankers, relevant results from Tripartite 2004 and 2005 meetings and discuss other examples of the need for a workable and robust EWS Redefine “failure incident” and formulate the feasible requirements Discuss the processes involved in each society as regards internal reporting of redefined “failure incidents” Review the IACS process of submission of EWS reports and actions thereon

4. IACS EWS Review Major findings to date: Need to make the EWS “early” Need to define the use of the information put through the Scheme Need to resolve the confidentiality issues within the Scheme Importance of the EWS to the CSR (feedback mechanism)

5. IACS EWS Review “Early Warning” aspect on the Scheme Current schemeRecs under discussion Scope: Serious hull failures, machinery fires and explosions Reactive reporting Action by involved members only Limit to hull failures Both: reactive and proactive reporting 2 steps: report the information for action by members involved with the ship and her sisters AND produce recommendations for IACS to take collectively, where possible

6. IACS EWS Review “Confidentiality” aspect on the Scheme: Members have agreed to put to their governance bodies the following text to be included in their Rules: "Notwithstanding the general duty of confidentiality owed to its clients, clients hereby accept that [IACS Member] will participate fully in IACS' Early Warning System which requires each IACS member to provide its fellow IACS members with information on serious ship failures and engine room fires and explosions and equipment failures, including the name of the ship and its IMO number, to enable such useful information to be shared and utilised to facilitate the proper working of IACS' Early Warning System (which is aimed at enabling (i) "sister" or similar ships to avoid similar problems and (ii) the shipping industry generally to learn from failures and mistakes)."

7. IACS EWS Review Invitation to the Tripartite meeting: IACS would encourage organisations present at the Tripartite meeting to support these efforts through their members’: - positive consideration of the Rule change aimed at addressing confidentiality issues, - direct cooperation in controlled (within the Scheme) sharing of damage information