PlenaryWP3

THEMES – Network meeting 2: 

THEMES – Network meeting 2 Work Package III CHIRP, Voyage Data Recorder, Accident Data Presentations by Pedro Antao - Apostolos Bizakis Svein Kristiansen – Tapio Nyman

Objective: 

Objective Assess the need for accident and incident information State-of-the-art for capture and storage of safety related data Propose a framework for a European database Plan for implementation

WP III within THEMES: 

WP III within THEMES WPIII Database CHIRP Voyage recorder Inspection info WPII European Information System WPIV Human aspects WP V Safety and Environmental assessment methods WPVI Safety Management INTEGRATIVE STUDIES CHIRP Accident/ incident DB

Tasks: 

Tasks Work Package leader T 3.0 - WP coordinator T 3.1 – Accident/ incident database T 3.2 – CHIRP T 3.3 – Voyage data recorder T 3.4 – Ship inspection information SSPA NUST ITEC VTT VTT THRUTH

Report outline: 

Report outline Introduction Safety and learning Sources of information The maritime system Safety management Accident databases Recent R&D projects funded by EC Present data based practices Assessment of the-state-of-the-art

Report outline (cont.): 

Report outline (cont.) CHIRP (Confidential Human Factors Incident Reporting Programme) Relevant EU projects National initiatives Concluding remarks Voyage Data Recorder Ship Inspection Information Sources of ship inspection data Types of information Ways of establishing seamless inspection data exchange

Sources of information: 

Sources of information

Sources of information: 

Sources of information

US Coast Guard Homepage: 

US Coast Guard Homepage

Australian Transport Safety Bureau: 

Australian Transport Safety Bureau

Marine Accident Investigation Branch: 

Marine Accident Investigation Branch

Systemic proceses vs. General Failure Types: 

Systemic proceses vs. General Failure Types

M-SCAT (DnV): 

M-SCAT (DnV)

TRIPOD – Failure state profile: 

TRIPOD – Failure state profile

SYNERGY main window: 

SYNERGY main window

IMO - critique: 

IMO - critique There is only a fairly crude and imprecise quantification of losses / consequences. There is no possibility to code more than 3 casualty events. There is no clear distinction between causes related to the immediate accident process and the basic causal factors. There are ambiguities within the areas of both personal and organisational error There is only a very limited ability to code human factor causes when those causes are external to the ship.

MAIB – Safety Digest: 

MAIB – Safety Digest

Data quality: 

Data quality Reliability Independence of analyst Validity True events and causes Disclosure Distinguish between factors Quantification Estimate frequencies Practicality User-friendly Significance Relative to control & measures

Vision: 

Vision

THEMES WP IIICHIRP, Voyage Data Recorder and Accident data: 

THEMES WP III CHIRP, Voyage Data Recorder and Accident data VTT Contribution 2.2.2001 Compiled by Tapio Nyman and Harri Soininen

National and international initiatives: 

National and international initiatives At least three national and one international confidential incident reporting systems are under development National systems in Europe: Norwegian system Finnish system System of MAIB for UK International system in US: International Maritime Information Safety System IMISS

Planned organisation of the Finnish system: 

Planned organisation of the Finnish system

Existing Marine Reporting Sheme MARS: 

Existing Marine Reporting Sheme MARS Marine Accident Reporting System MARS set up in 1992 the reporters are often those who have managed a near miss which was caused by somebody else the causes of the near miss remain often unclear

General prerequisitites for reporting: 

General prerequisitites for reporting The requirements that a person working in shipping industry decides to report: he recognises that the event he had experienced could end at the worst in disaster he has potential to observe and evaluate the working methods of his work community he is aware of the reporting system and has positive conception of its function he thinks that he has advantage, personal or common, if he reports he has possibility to report

General prerequisitites for reporting (cont.): 

General prerequisitites for reporting (cont.) To fulfill the requirements the following actions are needed: effective training programme and marketing campaign for everybody working in shipping especially in the starting phase of the new system in the professional basic training of the seafarers reporting should be made easy the forms shoul be available everywhere they can be filled the forms shoul be similar for each occupational group the forms should quide the reporter to report all the essential facts language may not be an obstacle for reporting a positive attitude for confidential reporting should be achieved in the shipping industry

Basic idea of the feedback: 

Basic idea of the feedback Two kinds of feedback: a notification to the reporter that the report has been received information to the whole maritime community from the analysed reports Newsletters, alert messages Feedback is necessary to maintain the motivation to report Conclusions based on the analysis of the reports have to be carefully reasoned in order to invite attention to real problems The system has to search actively solutions to arising problems

Concluding remarcs: 

Concluding remarcs There is a demand of maritime confidential incident reporting system Complement the reporting schemes required by the ISM-code National Initiatives within EU to establish such systems and one in US aiming to be international The need of an EC wide system has been raised within some research projects within the fourth framework The current Thematic network should give an answer if the best option is a wide, common system or a co-operation of national systems that share the information

Voyage Data Recorder: 

Voyage Data Recorder IMO: 1997 adopted recommendations on performance standards for shipborne voyage data recorders the final decision missing Recommendations for EU might be a little bit too early in this phase

Thematic Network on Safety Assessment in Waterborne Transport THEMES (WP3 - T3.4): 

Thematic Network on Safety Assessment in Waterborne Transport THEMES (WP3 - T3.4) Ship inspection information sources

Who is doing what matrix: 

Who is doing what matrix

Class Societies 1: 

Class Societies 1 Classification services through third-party engineering analyses and periodical verification of vessel’s hull structure, mechanical/electrical systems. Class can refuse to issue or can withdraw a certificate Statutory certification in accordance to various international and national requirements on behalf of flag administrations

Port State Control (PSC): 

Port State Control (PSC) Key checking and compliance mechanism aiming at reducing substandard ships by performing scheduled and random onboard inspections PSC inspections deal only with internationally accepted conventions that should be enforced PSC is the only actor in the maritime business that works independently and publicises the results of their inspections

Paris MOU - description of work: 

Paris MOU - description of work 19 participating authorities have agreed upon the implementation of a harmonised system for PSC on: their commitments and the relevant international conventions that should be enforced the inspection procedures and the investigation of operational procedures the exchange of information through an inspection data sharing system and the publication of Annual reports with statistics and monthly updates on detention lists. Representatives from EC/DGVII, IMO, ILO Direct link to EQUASIS

Paris MOU - DB: 

Paris MOU - DB Paris MOU DB Management System IMO Number Name of ship Flag Ship’s particulars: IMO number Call sign Ship owner Ship manager Type of ship Gross tonnage Year of build Classification society Inspection particulars: Date and location of inspection(s) Deficiencies identified per category Days detained (if applicable) All deficiencies rectified (Y/N) Type of ship Gross tonnage Year of build Class Society and/or Time period

EQUASIS: 

EQUASIS Internet based information system supervised and co-funded by EU and the French Maritime Administration Information is provided by public authorities (Paris MOU, Tokyo MOU, USCG) and industry organisations (IACS, INTERTANKO, INTERCARGO)

EQUASIS database: 

EQUASIS database

Conclusions: 

Conclusions General : An integration of accident, incident, inspection and audit information should be the objective of future databases Techniques that support consistent coding should be incorporated Access and data retrieval should be improved Both case information, causal relationships and trends should be retrievable Jointly supporting data formats might be applied Accident data : Some databases are already in use The data quality may be questioned Applications are seen in safety policy planning, FSA and safety management Future databases should be designed to support the applications

Conclusions: 

Conclusions Incident data : CHIRP systems have had various degrees of success in different industries A number of CHIRP initiatives are presently underway in the maritime sector The motivation to report is highly dependent of the organisational climate Voyage data recorder (VDR) : The VDR technology is available IMO has proposed to make VDR mandatory for some ship categories It is still uncertain whether EU will take any initiative to speed up the implementation

Conclusions: 

Conclusions Inspection information : Inspections are undertaken by various parties such as Classification, Port State Control, insurance, ports et. Some inspection information is subject to electronic data processing (EDP) The potential of integrating inspection information with accident information should be studied