US Class I Rail Process Wiki Merger & Network Integration › Systems Cutover Planning (TMS, CAD, PTC, car accounting)
🗺 BPMN Process Flow
RR-15-04-01 BPMN Diagram

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

📋 Process Attributes
Process IDRR-15-04-01
Domain FamilyCORPORATE
L1 DomainMerger & Network Integration
L2 Process GroupSystems Cutover Planning (TMS, CAD, PTC, car accounting)
TriggerInitiation by the Integration Program Management Office (PMO) lead following a merger or significant network expansion.
OutcomeSuccessful completion results in fully integrated TMS, CAD, PTC, and car accounting systems with minimal disruption to rail operations and compliance with all relevant regulations.
SystemsNetControl I-ETMS Umler PS Technology EHMS TRAIN II
Regulatory Hooks49 CFR Part 232 GCOR 6.28
📋 L4 Process Steps
StepNameRoleSystem InputOutputKPIPain Point / Risk Decision?Exception?
1.1 Project Initiation Meeting Integration Program Management Office (PMO) lead NetControl / TCS cutover precedent Merger or network expansion proposal Cutover project plan Project initiation within 30 days of trigger Resource allocation and stakeholder buy-in Y N
1.2 System Compatibility Assessment Service Design / Network Planning Analyst NetControl, I-ETMS Cutover project plan Compatibility report Compatibility assessment completed within 60 days Technical integration challenges Y N
1.3 Regulatory Compliance Review Chairman, President and CEO (plan sponsor level) NetControl, I-ETMS Compatibility report Compliance matrix Regulatory compliance review completed within 45 days Navigating complex regulatory requirements Y N
1.4 Training and Documentation Development Train Dispatcher, Control Operator NetControl, I-ETMS Compliance matrix Training materials and documentation Training materials ready within 30 days Effective training program development Y N
1.5 Pilot Testing Chief Dispatcher, Yardmaster NetControl, I-ETMS Training materials and documentation Pilot test report Pilot testing completed within 60 days Identifying and addressing system issues Y N
1.6 Final System Configuration Integration Program Management Office (PMO) lead NetControl, I-ETMS Pilot test report Final system configuration plan Configuration plan finalized within 30 days Optimizing system performance Y N
1.7 Go-Live Preparation Train Dispatcher, Control Operator NetControl, I-ETMS Final system configuration plan Go-live checklist Go-live preparations completed within 10 days Ensuring all systems are ready Y N
1.8 System Go-Live Integration Program Management Office (PMO) lead NetControl, I-ETMS Go-live checklist Go-live confirmation Go-live within scheduled time frame Smooth transition without operational disruption Y N
1.9 Post-Go-Live Monitoring Train Dispatcher, Control Operator NetControl, I-ETMS Go-live confirmation Monitoring report Continuous monitoring for 30 days post-go-live Detecting and resolving any issues promptly Y N
1.10 Final Review and Documentation Update Integration Program Management Office (PMO) lead NetControl, I-ETMS Monitoring report Updated system documentation Documentation update completed within 10 days post-go-live Maintaining accurate and up-to-date records Y N
📊 KPIs & Risk Register

KPIs

Terminal dwell under 24 hours Train speed above 20 mph System uptime above 98% Training completion rate above 95% Pilot test success rate above 90%

Key Risks

Air brake test defect released to the road Regulatory non-compliance during cutover Service disruption affecting critical routes Data loss or corruption during transition Technical integration failures leading to downtime

Swim Lanes

Integration Program Management Office (PMO) lead · 1.1, 1.6, 1.8, 1.10 Service Design / Network Planning Analyst · 1.2 Chairman, President and CEO (plan sponsor level) · 1.3 Train Dispatcher, Control Operator · 1.4, 1.7, 1.9 Chief Dispatcher, Yardmaster · 1.5