1. TRAIN II Event Reporting Association of Car Accounting & Car Service Officers May 11 – 13, 2011 Burlington, VT

2. Reasons to Report Facilitate Good Equipment Utilization by Improving Shipment Visibility for: –Customers –Other carriers in waybill route –Equipment Owners Car Hire Responsibility is Assigned Based on Event Analysis by LCS

3. Background TRAIN Stands for Tele Rail Automated Information Network Interchanges Were the First Events Reported - Late 1960’s Multiple Event and Message Syntaxes Developed as Needed Nine Different Message Types are Currently Used for Event Reporting

4. Message Types TRAIN01- Deliveries and Receipts TRAIN02 – Boundary Crossings TRAIN03 – Movement and Status Events

5. Message Types TRAIN31 – Correct Interchange Reports –Delete/Add –Start Haulage –Start Suppression –Accept Liability TRAIN32 – Correct Boundary Crossings –Delete/Add TRAIN33 – Correct Movement Events –Delete/Add

6. Message Types TRAIN06 – Waybill –Used predominantly for local empties –Not distributed and edited by Forward and Store TRAIN08 – Special Event Reporting –Bad Order –Arrival/Departure with Train ID –Rule 5/15 TOL

7. Message Types TRAIN10 – All Event Reporting –Developed in 1997 –New Functionality is Added to Type 10 Messages Intermodal Indicator Time Zone Indicator Advance Reporting Indicator Conveying Equipment on RAMP/DERAMP

8. Event Volumes 107 Reportable Events –75 Locating Events Arrival Departure Place Pull

9. Event Volumes Approximately 7.5 million Events are Received and Posted Daily Event Repository Size Varies from 800 - 900 Million Events Events are Retained in the ER for at Least 90 Days After 90 Days, Events are Retained on History Files

10. Event Volumes 107 Reportable Events –24 Non-locating Events TOLs Car Grade by Waybill Equipment Ordered In –8 Transportation Conditions

12. Questions?