US Class I Rail Process Wiki Engineering: Track, Structures & Signals › PTC Wayside Assets and Subdivision Track Data File Management
🗺 BPMN Process Flow
RR-06-07-03 BPMN Diagram

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

📋 Process Attributes
Process IDRR-06-07-03
Domain FamilyOPERATIONS
L1 DomainEngineering: Track, Structures & Signals
L2 Process GroupPTC Wayside Assets and Subdivision Track Data File Management
TriggerDetection of a discrepancy or failure in PTC wayside equipment by Track Supervisor or Signal Maintainer during routine inspections or through automated systems like Wabtrax or ATIP.
OutcomeSuccessful completion results in the accurate and timely update of PTC wayside assets and subdivision track data files, ensuring safe and efficient train operations.
SystemsNetControl I-ETMS PTC Back Office Server (BOS) Wabtrax Umler
Regulatory Hooks49 CFR Part 236 49 CFR Part 1180
📋 L4 Process Steps
StepNameRoleSystem InputOutputKPIPain Point / Risk Decision?Exception?
1.1 Identify Discrepancy or Failure Track Supervisor Wabtrax Automated inspection report Discrepancy log Time to identify discrepancy < 1 hour False positives from automated systems Y N
1.2 Notify PTC Field Engineer Track Supervisor NetControl Discrepancy log Work order Time to notify engineer < 30 minutes Delayed notifications affecting maintenance schedules N Y
1.3 Inspect and Diagnose Issue PTC Field Engineer / PTC Technician I-ETMS Work order Diagnosis report Time to diagnose issue < 2 hours Complex issues requiring multiple diagnostic steps Y N
1.4 Update PTC Wayside Assets PTC Field Engineer / PTC Technician I-ETMS Diagnosis report Updated asset data Time to update assets < 4 hours Inaccurate data entry affecting system integrity N Y
1.5 Verify Data Update Track Supervisor I-ETMS Updated asset data Verification report Time to verify update < 30 minutes Manual verification errors Y N
1.6 Update Subdivision Track Data File Track Supervisor PTC Back Office Server (BOS) Verification report Updated track data file Time to update track data < 1 hour Data synchronization issues between systems N Y
1.7 Notify Control Operator Track Supervisor NetControl Updated track data file Notification to Control Operator Time to notify operator < 10 minutes Delayed notifications affecting train schedules N Y
1.8 Review and Approve Changes Chief Engineer / VP Engineering PTC Back Office Server (BOS) Updated track data file Approval document Time to approve changes < 2 hours Complexity in reviewing large datasets Y N
1.9 Implement Changes Control Operator NetControl Approval document Implemented changes Time to implement changes < 30 minutes System downtime during implementation N Y
1.10 Monitor System Performance Track Supervisor Wabtrax Implemented changes Performance report System uptime > 99% Monitoring false negatives Y N
1.11 Review and Document Incident Track Supervisor Umler Performance report Incident report Time to document incident < 2 hours Detailed documentation requirements N Y
1.12 Close Incident Track Supervisor Umler Incident report Closed incident record Time to close incident < 30 minutes Lack of clear closure criteria N Y
📊 KPIs & Risk Register

KPIs

Time to identify discrepancy < 1 hour Time to notify engineer < 30 minutes Time to diagnose issue < 2 hours Time to update assets < 4 hours Time to verify update < 30 minutes Time to update track data < 1 hour Time to notify operator < 10 minutes Time to approve changes < 2 hours Time to implement changes < 30 minutes System uptime > 99% Time to document incident < 2 hours Time to close incident < 30 minutes

Key Risks

Data entry errors affecting system integrity Delayed notifications impacting maintenance schedules Complex issues requiring multiple diagnostic steps Inaccurate data synchronization between systems System downtime during implementation

Swim Lanes

Track Supervisor · 1.1, 1.2, 1.5, 1.6, 1.7, 1.10, 1.11, 1.12 PTC Field Engineer / PTC Technician · 1.3, 1.4 Chief Engineer / VP Engineering · 1.8