1 / 9

Damaged/Defective Car Tracking System (DDCTS)

DDCTS is a paperless solution to manage defective/damaged rail cars, providing real-time data exchange, audit logs, and file sharing among stakeholders for efficient tracking, audit, and reporting. Key stakeholders include mechanical, accounting, and ownership teams. Project implementation and progress detailed with a planned June 1, 2009, launch delayed due to interface challenges. Next steps include budget planning, rule changes, testing, and production phase. Presented at RailInc. 2010, the system aims for seamless digital data management in the rail industry.

emcmanus
Download Presentation

Damaged/Defective Car Tracking System (DDCTS)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Damaged/Defective Car Tracking System (DDCTS) ACACSO Meeting Pueblo - May 14, 2009Dale CasselsCSX Transportation

  2. Project Committees: ARB (Arbitration and Rules Committee) EAMWC (Equipment Assets Management Working Committee)

  3. Project Sponsors: Rich DeWitt – TTX Mike Reid – BNSF Mike Partica – CN Robert Sanford – NS

  4. Some History • Arbitration and Rules Committee (ARB) & Car Repair Billing Committee (CRB) implemented changes for all car repair billing to be paperless. • One final change – electronic defect cards • Equipment Assets Management Working Committee (EAMWC) has also been working to reduce paper exchange. • Car Hire Rules 7 & 8 allow relief when specific events occur. Determining those events is labor intensive. • Create a central repository of information related to defective/damaged rail cars.

  5. Project Goals: • Create a web based data exchange for defective and damaged freight cars. • Identify and communicate agreed information in a timely manner to parties that need the data. • Allow data to be updated as the handling of the car progresses. • Provide electronic notices when expected updates are not made. • Maintain user audit logs and historical records. • Provide reports and allow ad hoc inquiries. • Upload and download files between parties involved.

  6. Project Stakeholders: • Mechanical – primary supplier of data • Car Accounting – uses data to calculate and audit car hire and reclaims • Revenue Accounting – sends out freight bills • Property Accounting – maintains inventory for fleets • Car Owners – receives information on damaged or defective cars and provides data and disposition • ARB – rules review • EAMWC – rules review

  7. Some More History Implementation date set for June 1, 2009 Implementation delayed Reason for delay – significant interface work needed Testing continued thru May 2009 “Shrink wrapped” project Presented for RailInc 2010 Capital Budget 7

  8. Next steps: • Budget and support for 2010 project – Phase 2 • Sub-TAG meets in June • Open issues log • Unwrap project in 2010 • Rule Changes • Testing • Production

  9. Questions ???

More Related