US Class I Rail Process Wiki Safety & Regulatory Compliance › Accident and Incident Reporting
🗺 BPMN Process Flow
RR-07-04-01 BPMN Diagram

Click diagram to zoom & pan • Scroll to zoom • Drag to pan • Download SVG

📋 Process Attributes
Process IDRR-07-04-01
Domain FamilyCORPORATE
L1 DomainSafety & Regulatory Compliance
L2 Process GroupAccident and Incident Reporting
TriggerDetection of an accident or incident by any crew member during operations.
OutcomeA detailed report is generated and filed, contributing to continuous improvement in safety practices and regulatory compliance.
SystemsNetControl I-ETMS Umler EHMS TRAIN II C3RS
Regulatory Hooks49 CFR Part 217 GCOR 6.28
📋 L4 Process Steps
StepNameRoleSystem InputOutputKPIPain Point / Risk Decision?Exception?
1.1 Identify the Incident Locomotive Engineer NetControl Incident details from crew member Initial incident report Time to identify and report an incident < 5 minutes Delayed reporting due to unclear communication channels N Y
1.2 Notify the Dispatcher Train Dispatcher I-ETMS Initial incident report Dispatcher notification Time to notify dispatcher < 3 minutes Dispatcher unavailability during peak hours N Y
1.3 Assess Incident Severity Chief Safety Officer / VP Safety C3RS Dispatcher notification Severity assessment Time to assess severity < 10 minutes Subjectivity in assessing incident severity Y N
1.4 Initiate Safety Investigation Rules Officer Umler Severity assessment Investigation plan Time to initiate investigation < 2 hours Resource allocation for investigations N Y
1.5 Gather Incident Data Car Inspector (Carman) EHMS Investigation plan Incident data Data collection completeness > 90% Inconsistent data reporting N Y
1.6 Review Incident Data Efficiency Testing Officer TRAIN II Incident data Data review report Time to review data < 4 hours Complexity in reviewing large datasets Y N
1.7 Draft Incident Report Rules Instructor NetControl Data review report Draft incident report Report accuracy > 95% Technical errors in reporting N Y
1.8 Review and Approve Report VP Network Planning & Operations I-ETMS Draft incident report Approved incident report Time to approve report < 24 hours Delays in approval due to high volume Y N
1.9 File Incident Report Chief Dispatcher Umler Approved incident report Filed incident report Time to file report < 2 hours System downtime affecting filing N Y
1.10 Notify Affected Parties Service Design / Network Planning Analyst NetControl Filed incident report Notification to affected parties Time to notify parties < 4 hours Inaccurate notification lists N Y
1.11 Update Safety Protocols Chairman, President and CEO C3RS Incident report Updated safety protocols Number of protocol updates per year > 5 Resistance to change in safety protocols Y N
1.12 Monitor and Review VP Safety TRAIN II Updated safety protocols Monitoring report Incident recurrence rate < 5% Inadequate monitoring tools Y N
📊 KPIs & Risk Register

KPIs

Time to identify and report an incident < 5 minutes Time to notify dispatcher < 3 minutes Data collection completeness > 90% Report accuracy > 95% Time to approve report < 24 hours Time to file report < 2 hours Time to notify parties < 4 hours Number of protocol updates per year > 5 Incident recurrence rate < 5%

Key Risks

Delayed reporting due to unclear communication channels Dispatcher unavailability during peak hours Resource allocation for investigations Inconsistent data reporting Complexity in reviewing large datasets

Swim Lanes

Locomotive Engineer · 1.1 Train Dispatcher · 1.2 Chief Safety Officer / VP Safety · 1.3 Rules Officer · 1.4 Car Inspector (Carman) · 1.5 Efficiency Testing Officer · 1.6 Rules Instructor · 1.7 VP Network Planning & Operations · 1.8 Chief Dispatcher · 1.9 Service Design / Network Planning Analyst · 1.10 Chairman, President and CEO · 1.11 VP Safety · 1.12