1 / 17

Linda Wright ProRail

A PROMISE for improvement: the ProRail Management Information for Safety and Environment database. Linda Wright ProRail. Overview. Background to the PROMISE database and role in the SMS Purpose of PROMISE The generic framework for a reporting system (decisions at each stage)

wanda-beard
Télécharger la présentation

Linda Wright ProRail

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. A PROMISE for improvement: the ProRail Management Information for Safety and Environment database Linda Wright ProRail

  2. Overview • Background to the PROMISE database and role in the SMS • Purpose of PROMISE • The generic framework for a reporting system (decisions at each stage) • Implementation of the database • Reliability of the data • Evaluation of the database 2

  3. Background PROMISE and role in the SMS • SMS introduced in 2004 – reporting and investigation of incidents is a central function in the SMS • Old database did not fulfill the requirements of the SMS • Minimum requirement was the continuation of a recently introduced monthly report 3

  4. 4

  5. Purpose of PROMISE • Monitoring of incidents: gain statistically reliable quantitative insight into factors or combination of factors that give rise to incidents • Register and analyse data on cause and context • Help the regions to learn from each other and identify countermeasures • Evaluate the functioning of the SMS via the monthly reports and subsequent analyses 5

  6. Algemeen: in vergelijking tot afgelopen maand is er weer lichte verbetering te zien. Er zijn meer positieve dan negatieve ontwikkelingen te zien. Verbetering (van rood naar geel) op Ontsporing (1.1.4), Bijna-aanrijdingen derden (3.2.1) en (geel naar groen) Botsing obstakel (1.1.3), TOBS (1.2.4, vorige maand nog in kritisch gebied) en Aanrijding personeel/gereedschap (4.1.1). Positieve trendwijzigingen bij: Botsing stootjuk (1.1.2), Afvallen sein (1.2.3), Spoorstaafbreuk (1.2.8) en Gevaarlijke situaties werkzaamheden (4.2.2). Nieuwe rode vlakken zijn Gescheurde tong/puntstuk (1.2.6 – de negatieve trend van de afgelopen maanden heeft doorgezet), Vandalisme (3.2.4) en Lekkage ballast (5.1.1 – echter zeer laag aantal in absolute zin). De grafieken 1.2.7, 2.1.4, 3.2.4 en 4.2.2 zijn in vrijwel alle regio’s “rood”. Negatieve trends gesignaleerd bij Wissel open gereden (1.2.7) en Vee op baan (1.2.12). Opvallend is dat “Niveau I” bij overwegen wat slechter uitziet, vooral door de gevolgen van incidenten (doden/gewonden), terwijl “Niveau II” een overwegend positievere trend laat zien t.o.v. afgelopen maand. 6

  7. The generic framework for reporting • Comprises 7 modules which should be prepared and planned prior to launching the system. Each will be discussed with reference to how ProRail implemented PROMISE 7

  8. Type of reports Publicity & training Design reporting route Accidents, near misses, dangerous situations None required Use of current reporting route 1. Detection and reporting 8

  9. Rules required Based on potential rather than actual consequenses Certain incidents always investigated Events per month – Severity/ Frequency matrix; Training of safety advisors in S/F matrix 2. Selection of events for investigation 9

  10. Select a method (e.g. Fault tree analysis) Detailed investigation necessary – training of investigators Causal trees Training in two levels of investigation – facts gathering & analysis 3.Detailed description & deeper study 10

  11. Select a taxonomy (the minimal requirements) Training Inter-rater reliability Set of root causes & not simply “the main cause” PRISMA-Rail (trial before implementation) Training for analysts Demonstrated on a small scale Database designed for multiple causes 4. Classification of root causes 11

  12. Design for statistical analyses Perform analysis Able to extract what is entered in different forms. Graphs, tables, word & excel files Monthly & quarterly reports, causal analysis 5. Computation: recognise patterns 12

  13. Recommendations are data driven Feasibility group Feedback channel for organisational learning Based in monthly reports and supplemental analysis by the Regions LCV & RVC Safety advisors monthly meeting, Management team, LCV & RVC 6. Interpretation & implementation recommendations 13

  14. How to evaluate the recommendations Specific action fields in PROMISE Over time evaluate relationship between countermeasures, causes and events. 7. Evaluation 14

  15. Implementation of PROMISE • Introduced January 2005 • Incorporated in the SMS • Training sessions in input & output • 2 administrators • Users group once a month • PRISMA-Rail support group • Quality control 15

  16. Reliability of the database • 3 steps to data entry: Selection, assigning case type and incident category • Inter-rater reliability of the incident types: showed good reliability for all steps • Plans to perform same test 2 x year • Small scale PRISMA-Rail reliability trial showed good reliability between 2 raters • Larger scale inter-rater reliability for PRISMA-Rail planned for next year 16

  17. Evaluation of PROMISE • Audit currently being performed • New data source being implemented from November • New training in Severity/ Frequency Matrix • New inspection module for proactive information • Better and faster management reports 17

More Related