10.08.2013 Views

Metrolink peer review report - Ventura County Star

Metrolink peer review report - Ventura County Star

Metrolink peer review report - Ventura County Star

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

METROLINK COMMUTER RAIL SAFETY PEER REVIEW PANEL<br />

Final Report – January 5, 2009<br />

Executive Summary<br />

Enhanced Safety Action Plan are implemented, then those improvements will replace the “second set of<br />

eyes”.<br />

d. DigiCon Dispatch Issue: The Panel recommends that SCRRA expedite plans to transition from the<br />

DigiCon system and develop an action plan for maintenance and other emergencies in the interim.<br />

e. Annual Medical Evaluations: Implement medical evaluations prior to placement of contractor employees<br />

in a safety covered position and at least every three years.<br />

f. Hours of Service/Split Shift Issue: Since SCRRA’s Transportation Contractor uses split shift assignments<br />

in its train and engine crew schedules, it is the Panel’s recommendation that SCRRA participate actively<br />

on the Hours of Service issue as part of the Federal Railroad Administration (FRA) Rail Safety Advisory<br />

Committee (RSAC) process.<br />

g. Hours of Service Study: The Panel also recommends that SCRRA, in cooperation with its operating<br />

contractor, conduct a <strong>review</strong> of its contractor’s Hours of Service Split Shift schedules for their train and<br />

engine crews and determine if fatigue is a factor in the use of Split Shifts. In addition, SCRRA should<br />

evaluate whether any relevant rules and their particular application require any short term measures<br />

pending the results of the FRA RSAC process regarding Hours of Service.<br />

7. Strategic Plan<br />

<strong>Metrolink</strong>’s current strategic plan centers primarily on its capital improvement programs and to a lesser degree on<br />

its SSPP. Review of the current SCRRA strategic plan reveals the agency’s process of prioritizing capital<br />

improvements, the funding of these projects, and the documentation of improvement benefits.<br />

The Panel has observed that <strong>Metrolink</strong> staff sees the strategic plan as a forecast of capital improvements to be<br />

undertaken within the specific areas of each of the Member Agencies. As a result, the plan is looked upon as a<br />

summary of project plans developed by the Member Agencies rather than a regionally-oriented plan for the<br />

<strong>Metrolink</strong> system.<br />

It is recommended that SCRRA develop a comprehensive strategic plan that identifies goals, the desired safety<br />

culture, capital improvement plans and the overall agency mission. This document should be dynamic, visited<br />

regularly and be developed by a team consisting of members from all levels and departments within SCRRA and<br />

the Board.<br />

8. Governance<br />

Governance means the Board’s role in promoting safe and secure commuter rail operations, fostering a top-tobottom<br />

safety culture, and exercising appropriate oversight of safety and operational performance.<br />

The Panel recommends that the Board conduct a self-assessment of its performance with particular emphasis on<br />

safety and operational oversight. This assessment should lead to a more explicit definition of Board and Board<br />

member responsibilities and actions. The Panel lists several actions for the Board.<br />

Enhanced Safety Action Plan and Milestones: The Panel developed a milestone action plan organized by the<br />

eight major issues. Specific recommendations for improvement in each area were provided, and categorized as to<br />

their implementation timeframe: short-term (six months), intermediate-term (18 months), or long-term (up to<br />

four years). This plan is presented as Chart 1 on the following pages.<br />

4

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!