US Class I Rail Process Wiki Merger & Network Integration › Reporting Mark and Equipment Registry Transition
🗺 BPMN Process Flow
RR-15-05-01 BPMN Diagram

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

📋 Process Attributes
Process IDRR-15-05-01
Domain FamilyCORPORATE
L1 DomainMerger & Network Integration
L2 Process GroupReporting Mark and Equipment Registry Transition
TriggerInitiated by the Chairman/CEO or Integration Program Management Office (PMO) lead upon the announcement of a merger or significant network integration project that involves changes to reporting marks and equipment registry.
OutcomeSuccessful completion results in the updated reporting marks and equipment registry being fully integrated into all relevant systems, ensuring compliance with regulatory standards and operational efficiency.
SystemsNetControl I-ETMS Umler EHMS TRAIN II CHARM
Regulatory Hooks49 CFR Part 1180 GCOR 6.28
📋 L4 Process Steps
StepNameRoleSystem InputOutputKPIPain Point / Risk Decision?Exception?
1.1 Initiate Transition Plan Integration Program Management Office (PMO) lead NetControl / TCS cutover precedent Merger & Network Integration plan Transition plan document Plan completion within 30 days Resource allocation for the transition team Y N
1.2 Update Umler Database Service Design / Network Planning Analyst Umler Updated reporting marks and equipment details Umler database update report Database update completed within 10 days Data integrity during the update N Y
1.3 Review and Approve Changes Chairman, President and CEO (plan sponsor level) NetControl Umler database update report Approval document Approval within 5 days of submission Complexity of changes requiring multiple reviews Y N
1.4 Update EHMS System VP Network Planning & Operations EHMS Approved reporting marks and equipment details EHMS update report System update completed within 7 days Integration with other systems N Y
1.5 Update TRAIN II System Service Design / Network Planning Analyst TRAIN II Approved reporting marks and equipment details TRAIN II update report System update completed within 7 days Data synchronization issues N Y
1.6 Update CHARM System VP Network Planning & Operations CHARM Approved reporting marks and equipment details CHARM update report System update completed within 7 days Data consistency across systems N Y
1.7 Update Interline Settlement System Service Design / Network Planning Analyst Interline Settlement System Approved reporting marks and equipment details ISS update report System update completed within 7 days Impact on existing settlement processes N Y
1.8 Update Harriman Dispatching Center Train Dispatcher Harriman Dispatching Center Approved reporting marks and equipment details Dispatch center update report System update completed within 7 days Operational disruptions during the update N Y
1.9 Conduct Training Sessions Integration Program Management Office (PMO) lead NetControl Updated system configurations and procedures Training completion report Training sessions completed within 10 days of update Variability in learning speeds among staff Y N
1.10 Monitor and Validate Systems Service Design / Network Planning Analyst NetControl, I-ETMS Updated system configurations Validation report System validation completed within 5 days of training Identifying and resolving post-update issues Y N
1.11 Final Review and Sign-Off Chairman, President and CEO (plan sponsor level) NetControl Validation report Sign-off document Sign-off within 3 days of validation Final approval delays Y N
1.12 Communicate to Stakeholders Integration Program Management Office (PMO) lead NetControl Sign-off document Stakeholder communication report Communication completed within 2 days of sign-off Effective communication strategy N Y
📊 KPIs & Risk Register

KPIs

Plan completion within 30 days Database update completed within 10 days Approval within 5 days of submission System update completed within 7 days (4 systems) Training sessions completed within 10 days of update System validation completed within 5 days of training Sign-off within 3 days of validation Communication completed within 2 days of sign-off

Key Risks

Data integrity during the Umler database update Integration issues with other systems (EHMS, TRAIN II, CHARM) Operational disruptions during system updates at Harriman Dispatching Center Variability in learning speeds among staff during training sessions Final approval delays

Swim Lanes

Integration Program Management Office (PMO) lead · 1.1, 1.9, 1.12 Service Design / Network Planning Analyst · 1.2, 1.4, 1.5, 1.7, 1.10 VP Network Planning & Operations · 1.3, 1.6, 1.8 Train Dispatcher · 1.10