RR-07 RR-07-06-01 — Confidential Close Call Reporting
This process documents the confidential close call reporting procedure for a US Class I freight railroad, ensuring that incidents are reported and investigated to enhance safety and regulatory compliance.
🗺 BPMN Process Flow
Click diagram to zoom & pan • Scroll to zoom • Drag to pan • Download SVG
📋 Process Attributes
| Process ID | RR-07-06-01 |
|---|---|
| Domain Family | CORPORATE |
| L1 Domain | Safety & Regulatory Compliance |
| L2 Process Group | Confidential Close Call Reporting |
| Trigger | Detection of a near-miss incident or potential safety hazard during operations |
| Outcome | A detailed report is generated, reviewed, and appropriate corrective actions are taken to prevent future occurrences. |
| Systems | NetControl I-ETMS C3RS Umler PS Technology EHMS |
| Regulatory Hooks | 49 CFR Part 232 GCOR 6.28 |
📋 L4 Process Steps
| Step | Name | Role | System | Input | Output | KPI | Pain Point / Risk | Decision? | Exception? |
|---|---|---|---|---|---|---|---|---|---|
| 1.1 | Incident Detection | Locomotive Engineer | NetControl | Real-time train data and observations | Incident report draft | Time to detect incident < 5 minutes | Delayed detection of incidents | Y | N |
| 1.2 | Initial Reporting | Conductor | C3RS | Incident report draft | Confidential close call report | Report submitted within 30 minutes of incident detection | Incomplete or delayed reporting | Y | Y |
| 1.3 | Review and Classification | Rules Officer | C3RS | Confidential close call report | Classified incident report | Classification completed within 2 hours | Misclassification of incidents | Y | N |
| 1.4 | Investigation Initiation | Chief Safety Officer / VP Safety | C3RS | Classified incident report | Investigation plan | Investigation initiated within 24 hours | Delayed investigation start | Y | N |
| 1.5 | Data Collection | Train Dispatcher | NetControl, I-ETMS | Investigation plan | Collected data and evidence | Data collection completed within 48 hours | Inadequate data collection | N | Y |
| 1.6 | Root Cause Analysis | Efficiency Testing Officer | C3RS, EHMS | Collected data and evidence | Root cause analysis report | Analysis completed within 72 hours | Complex or ambiguous root causes | Y | N |
| 1.7 | Corrective Action Plan Development | Chief Safety Officer / VP Safety | C3RS, Umler | Root cause analysis report | Corrective action plan | Plan developed within 5 days | Insufficient corrective actions | Y | N |
| 1.8 | Implementation of Corrective Actions | Train Dispatcher, Yardmaster | NetControl, PS Technology | Corrective action plan | Action logs and status updates | Actions implemented within 1 week | Non-compliance with corrective actions | N | Y |
| 1.9 | Review of Corrective Actions | Rules Officer | C3RS | Action logs and status updates | Review report | Review completed within 2 weeks | Inadequate review of actions | Y | N |
| 1.10 | Final Reporting and Closure | Chief Safety Officer / VP Safety | C3RS | Review report | Final confidential close call report with closure | Report finalized within 4 weeks | Delayed final reporting | Y | N |
📊 KPIs & Risk Register
KPIs
Time to detect incident < 5 minutes Report submitted within 30 minutes of incident detection Classification completed within 2 hours Investigation initiated within 24 hours Data collection completed within 48 hours Analysis completed within 72 hours Plan developed within 5 days Actions implemented within 1 week Review completed within 2 weeks Report finalized within 4 weeks
Key Risks
Incident not detected or reported in time Inadequate data collection during investigation Complex root causes leading to prolonged analysis Non-compliance with corrective actions Delayed final reporting and closure of the incident
Swim Lanes
Locomotive Engineer · 1.1 Conductor · 1.2 Rules Officer · 1.3, 1.9 Chief Safety Officer / VP Safety · 1.4, 1.7, 1.10 Train Dispatcher · 1.5, 1.8 Yardmaster · 1.8 Efficiency Testing Officer · 1.6