RR-11 RR-11-09-01 — Interline EDI Messaging
This process handles the electronic data interchange (EDI) messaging for interline operations between US Class I freight railroads, ensuring seamless communication and coordination of train movements, equipment management, and car hiring.
🗺 BPMN Process Flow
Click diagram to zoom & pan • Scroll to zoom • Drag to pan • Download SVG
📋 Process Attributes
| Process ID | RR-11-09-01 |
|---|---|
| Domain Family | NETWORK & PLANNING |
| L1 Domain | Interline, Equipment & Car Management |
| L2 Process Group | Interline EDI Messaging |
| Trigger | Receipt of a train manifest or equipment list from another railroad via EDI |
| Outcome | Successful completion results in the accurate exchange of train schedules, equipment statuses, and car hire data between railroads, facilitating smooth interline operations. |
| Systems | Interline Settlement System (ISS) / Switching Settlement Data Exchange (SSDX) Umler (Universal Machine Language Equipment Register) CHARM (Car Hire Accounting Rate Master) NetControl (service design use) I-ETMS (Interoperable Electronic Train Management System) |
| Regulatory Hooks | 49 CFR Part 232 AAR Interchange Rules (Rule 88 and related) |
📋 L4 Process Steps
| Step | Name | Role | System | Input | Output | KPI | Pain Point / Risk | Decision? | Exception? |
|---|---|---|---|---|---|---|---|---|---|
| 1.1 | Receive Interline Manifest | Car Hire / Interline Settlement Analyst | Interline Settlement System (ISS) / Switching Settlement Data Exchange (SSDX) | EDI message containing train manifest and equipment list | Acknowledgment of receipt to the originating railroad | Manifest received within 1 hour | Delayed or missing EDI messages | N | Y |
| 1.2 | Validate Manifest Data | Car Hire / Interline Settlement Analyst | Umler (Universal Machine Language Equipment Register) | Received train manifest and equipment list | Validation report | Data validation completed within 30 minutes | Inaccurate or incomplete data entries | Y | N |
| 1.3 | Update Umler Database | Equipment Registration / Umler Data Analyst | Umler (Universal Machine Language Equipment Register) | Validated train manifest and equipment list | Updated Umler database with new or updated records | Database update completed within 1 hour | System downtime affecting database updates | N | Y |
| 1.4 | Generate Car Hire Data | Car Hire / Interline Settlement Analyst | CHARM (Car Hire Accounting Rate Master) | Updated Umler database with new or updated records | Car hire data report | Car hire data generated within 2 hours | Incorrect car hire rates | Y | N |
| 1.5 | Send Car Hire Data to Originating Railroad | Car Hire / Interline Settlement Analyst | Interline Settlement System (ISS) / Switching Settlement Data Exchange (SSDX) | Car hire data report | EDI message containing car hire data | Data sent within 30 minutes | Network connectivity issues | N | Y |
| 1.6 | Review and Confirm Car Hire Data | Car Hire / Interline Settlement Analyst | Interline Settlement System (ISS) / Switching Settlement Data Exchange (SSDX) | Received car hire data from originating railroad | Confirmation of receipt | Review completed within 1 hour | Discrepancies in car hire rates | Y | N |
| 1.7 | Update CHARM Database | Car Hire / Interline Settlement Analyst | CHARM (Car Hire Accounting Rate Master) | Confirmed car hire data | Updated CHARM database with new or updated records | Database update completed within 1 hour | System downtime affecting database updates | N | Y |
| 1.8 | Generate Train Schedule for Dispatching | Train Dispatcher | NetControl (service design use) | Updated Umler and CHARM databases with new or updated records | Train schedule | Schedule generated within 2 hours | Conflicting train schedules | Y | N |
| 1.9 | Dispatch Train | Train Dispatcher | NetControl (service design use) | Generated train schedule | Dispatch order sent to locomotive engineer | Train dispatched within 30 minutes of receiving schedule | Track availability issues | N | Y |
| 1.10 | Monitor Train Movement | Control Operator | I-ETMS (Interoperable Electronic Train Management System) | Dispatch order and train schedule | Train movement data | Movement data updated every 5 minutes | Signal system failures | Y | N |
| 1.11 | Update Train Status in Umler | Equipment Registration / Umler Data Analyst | Umler (Universal Machine Language Equipment Register) | Train movement data | Updated train status in Umler database | Status update completed within 10 minutes of receiving data | System downtime affecting database updates | N | Y |
| 1.12 | Finalize Interline Operation | Car Hire / Interline Settlement Analyst | Interline Settlement System (ISS) / Switching Settlement Data Exchange (SSDX) | Updated train status in Umler database | Completion report | Operation finalized within 1 hour of receiving final data | Settlement discrepancies | Y | N |
📊 KPIs & Risk Register
KPIs
Manifest received within 1 hour Data validation completed within 30 minutes Database update completed within 1 hour Car hire data generated within 2 hours Data sent within 30 minutes Review completed within 1 hour Schedule generated within 2 hours Train dispatched within 30 minutes of receiving schedule Movement data updated every 5 minutes Status update completed within 10 minutes of receiving data Operation finalized within 1 hour of receiving final data
Key Risks
Delayed or missing EDI messages Inaccurate or incomplete data entries System downtime affecting database updates Network connectivity issues Conflicting train schedules Track availability issues Signal system failures Settlement discrepancies
Swim Lanes
Car Hire / Interline Settlement Analyst · 1.1, 1.2, 1.4, 1.5, 1.6, 1.7 Equipment Registration / Umler Data Analyst · 1.3, 1.11 Train Dispatcher · 1.8, 1.9 Control Operator · 1.10