RR-07-06-02 — US Class I Freight Railroad Process Wiki

🗺 BPMN Process Flow

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

📋 Process Attributes

Process ID	RR-07-06-02
Domain Family	CORPORATE
L1 Domain	Safety & Regulatory Compliance
L2 Process Group	Confidential Close Call Reporting
Trigger	A crew member or supervisor identifies a potential safety hazard or incident that does not meet the criteria for a formal accident but requires immediate attention.
Outcome	The confidential close call is documented, reviewed, and addressed to prevent similar incidents in the future. The railroad ensures compliance with relevant regulations and internal policies.
Systems	NetControl C3RS Umler
Regulatory Hooks	49 CFR Part 217 GCOR

📋 L4 Process Steps

Step	Name	Role	System	Input	Output	KPI	Pain Point / Risk	Decision?	Exception?
1.1	Identify Close Call	Locomotive Engineer	NetControl	Incident report form	Reported incident details	Time to identify and report a close call under 10 minutes	Delayed reporting can lead to oversight of potential safety issues.	Y	N
1.2	Report Close Call	Train Dispatcher	C3RS	Reported incident details	Confidential close call report	Close call reports submitted within 24 hours of occurrence	Missing or incomplete reports can hinder safety investigations.	N	Y
1.3	Review Close Call	Chief Safety Officer / VP Safety	C3RS	Confidential close call report	Reviewed incident summary	Incident review completed within 48 hours of reporting	Delayed reviews can delay necessary corrective actions.	Y	N
1.4	Determine Root Cause	Rules Instructor / Rules Officer	Umler	Reviewed incident summary	Root cause analysis report	Root cause identified within 72 hours of review completion	Inaccurate root cause identification can lead to ineffective corrective measures.	Y	N
1.5	Develop Corrective Actions	Service Design / Network Planning Analyst	NetControl	Root cause analysis report	Corrective action plan	Corrective actions developed within 1 week of root cause identification	Lack of effective corrective actions can result in recurring incidents.	N	Y
1.6	Implement Corrective Actions	VP Network Planning & Operations	NetControl	Corrective action plan	Implemented corrective actions	Corrective actions implemented within 2 weeks of development	Delayed implementation can prolong the risk period.	Y	N
1.7	Monitor Corrective Actions	Train Dispatcher	NetControl	Implemented corrective actions	Monitoring report	Corrective actions monitored weekly for effectiveness	Inadequate monitoring can lead to unaddressed issues.	N	Y
1.8	Review and Update Policies	Chief Safety Officer / VP Safety	C3RS	Monitoring report	Updated safety policies	Policies reviewed and updated within 1 month of monitoring completion	Outdated policies can fail to address emerging safety concerns.	Y	N
1.9	Notify Affected Parties	Rules Officer	C3RS	Updated safety policies	Notification of affected parties	Notifications sent within 2 weeks of policy update	Non-communication can lead to confusion and non-compliance.	N	Y
1.10	Close Incident Case	Chief Safety Officer / VP Safety	C3RS	Notification of affected parties	Closed incident case	Incident cases closed within 3 months of initial report	Open cases can lead to ongoing safety risks.	Y	N
1.11	Conduct Post-Incident Review	Rules Instructor / Rules Officer	Umler	Closed incident case	Post-incident review report	Post-incident reviews conducted biannually	Lack of periodic reviews can miss evolving safety issues.	Y	N
1.12	Update Training Programs	Service Design / Network Planning Analyst	NetControl	Post-incident review report	Updated training programs	Training programs updated within 6 months of post-incident review	Outdated training can result in staff not being adequately prepared.	N	Y

📊 KPIs & Risk Register

KPIs

Time to identify and report a close call under 10 minutes Close call reports submitted within 24 hours of occurrence Incident review completed within 48 hours of reporting Root cause identified within 72 hours of review completion Corrective actions developed within 1 week of root cause identification Corrective actions implemented within 2 weeks of development Corrective actions monitored weekly for effectiveness Policies reviewed and updated within 1 month of monitoring completion Notifications sent within 2 weeks of policy update Incident cases closed within 3 months of initial report Post-incident reviews conducted biannually Training programs updated within 6 months of post-incident review

Key Risks

Delayed reporting can lead to oversight of potential safety issues. Missing or incomplete reports can hinder safety investigations. Inaccurate root cause identification can lead to ineffective corrective measures. Lack of effective corrective actions can result in recurring incidents. Non-communication can lead to confusion and non-compliance.

Swim Lanes

Locomotive Engineer · 1.1 Train Dispatcher · 1.2, 1.6, 1.9 Chief Safety Officer / VP Safety · 1.3, 1.8 Rules Instructor / Rules Officer · 1.4, 1.11 Service Design / Network Planning Analyst · 1.5, 1.12

Independently compiled from public sources. Not affiliated with, sponsored by, or endorsed by Union Pacific or any other railroad. Illustrative of US Class I practice; every system, regulation, role and metric named here traces to a sourced entry in registries/.

RR-07 RR-07-06-02 — Confidential Close Call Reporting