RR-12 RR-12-06-02 — Field and Mobile Technology
This process outlines the operational steps for managing field and mobile technology systems in a US Class I freight railroad, focusing on ensuring secure-by-design approaches and compliance with industry regulations.
🗺 BPMN Process Flow
Click diagram to zoom & pan • Scroll to zoom • Drag to pan • Download SVG
📋 Process Attributes
| Process ID | RR-12-06-02 |
|---|---|
| Domain Family | CORPORATE |
| L1 Domain | Technology, Data & Cybersecurity |
| L2 Process Group | Field and Mobile Technology |
| Trigger | Initiated by a Train Dispatcher upon receiving a train movement request from the Harriman Dispatching Center. |
| Outcome | Successful completion ensures that all field and mobile technology systems are operational, secure, and compliant with regulatory requirements, enabling efficient train movements and operations. |
| Systems | NetControl I-ETMS Cybersecurity — 'secure-by-design' approach (unbranded) |
| Regulatory Hooks | 49 CFR Part 232 GCOR 6.28 TSA Security Directive 1580/82-2022-01 series (freight + passenger rail cybersecurity) |
📋 L4 Process Steps
| Step | Name | Role | System | Input | Output | KPI | Pain Point / Risk | Decision? | Exception? |
|---|---|---|---|---|---|---|---|---|---|
| 1.1 | Train Movement Request Received | Train Dispatcher | NetControl | Train movement request from Harriman Dispatching Center | Acknowledged train movement request in NetControl | Response time within 2 minutes | Delayed response affecting train schedule | N | Y |
| 1.2 | Secure-by-Design Review | Enterprise Architect / Platform Owner | Cybersecurity — 'secure-by-design' approach (unbranded) | Train movement request details | Security assessment report | Assessment completed within 10 minutes | Potential security vulnerabilities | Y | N |
| 1.3 | System Initialization | Train Dispatcher | NetControl, I-ETMS | Security assessment report | Initialized systems for train movement | Systems initialized within 5 minutes | System failure affecting train operation | N | Y |
| 1.4 | Train Departure Notification | Train Dispatcher | NetControl, I-ETMS | Initialized systems confirmation | Departure notification to Harriman Dispatching Center | Notification sent within 1 minute | Delayed departure affecting train schedule | N | Y |
| 1.5 | Terminal Arrival Notification | Train Dispatcher | NetControl, I-ETMS | Train arrival at terminal | Arrival notification to Harriman Dispatching Center | Notification sent within 2 minutes | Delayed notification affecting terminal operations | N | Y |
| 1.6 | System Shutdown | Train Dispatcher | NetControl, I-ETMS | Arrival notification confirmation | Shutdown of systems post-terminal arrival | Systems shutdown within 5 minutes | System failure affecting terminal operations | N | Y |
| 1.7 | Post-Operation Review | Enterprise Architect / Platform Owner | Cybersecurity — 'secure-by-design' approach (unbranded) | System shutdown confirmation | Post-operation review report | Review completed within 1 hour | Security breaches or vulnerabilities | Y | N |
| 1.8 | Update Security Protocols | Enterprise Architect / Platform Owner | Cybersecurity — 'secure-by-design' approach (unbranded) | Post-operation review report | Updated security protocols | Protocols updated within 24 hours | Ineffective security measures | N | Y |
| 1.9 | System Maintenance | Service Design / Network Planning Analyst | NetControl, I-ETMS | Updated security protocols | Scheduled system maintenance plan | Maintenance plan completed within 1 week | System downtime affecting operations | Y | N |
| 1.10 | Conduct Maintenance | Service Design / Network Planning Analyst | NetControl, I-ETMS | Scheduled system maintenance plan | Maintenance completion report | Maintenance completed within 2 days | System failure during maintenance | N | Y |
| 1.11 | Post-Maintenance Review | Enterprise Architect / Platform Owner | Cybersecurity — 'secure-by-design' approach (unbranded) | Maintenance completion report | Post-maintenance review report | Review completed within 1 day | Security issues after maintenance | Y | N |
| 1.12 | Update Maintenance Schedule | Service Design / Network Planning Analyst | NetControl, I-ETMS | Post-maintenance review report | Updated maintenance schedule | Schedule updated within 1 week | Inefficient maintenance planning | N | Y |
📊 KPIs & Risk Register
KPIs
Response time within 2 minutes Assessment completed within 10 minutes Systems initialized within 5 minutes Notification sent within 1 minute Notification sent within 2 minutes Systems shutdown within 5 minutes Review completed within 1 hour Protocols updated within 24 hours Maintenance plan completed within 1 week Maintenance completed within 2 days Review completed within 1 day Schedule updated within 1 week
Key Risks
Delayed response affecting train schedule Potential security vulnerabilities System failure affecting train operation Delayed notification affecting terminal operations System failure affecting terminal operations Security breaches or vulnerabilities Ineffective security measures System downtime affecting operations System failure during maintenance Security issues after maintenance Inefficient maintenance planning
Swim Lanes
Train Dispatcher · 1.1, 1.3, 1.4, 1.5, 1.6 Enterprise Architect / Platform Owner · 1.2, 1.7, 1.8 Service Design / Network Planning Analyst · 1.9, 1.10, 1.12