How do you manage your rail assets? Time-based maintenance or usage-based maintenance? After 38 years with a time-based maintenance approach for their rail car fleet, Washington Metropolitan Area Transit Authority (WMATA) is moving to usage-based preventive maintenance. Moving to usage-based preventive maintenance has enabled WMATA to save $1.2M annually on the road to $3.1M in savings projected in the future. WMATA will also virtually increase the size of their fleet by 2 rail cars every day, by decreasing the amount of cars removed from service for maintenance.
As the second largest transit system in the United States, reliability of transit service matters for the local population of 3.5M. With over 1.5 million trips per year across 106 miles of track using 86 stations, ensuring rail asset availability through effective preventive maintenance helps WMATA optimize it’s business model.
Many of the passengers on WMATA metro have daily commutes similar to George, who shows us just why reliability matters to both transit operators and passengers alike……..
The move to a mileage-based preventive maintenance schedule driven by actual mileage values will enable WMATA to achieve a higher availability of these assets and reduce the overall parts inventory and associated maintenance costs, while proactively improving safety. How do they do it?
In a September 11th webcast, Tara Soesbee, Program Manager at WMATA and Doug Stevenson, Associate Partner at IBM will touch on the end to end solution and projected benefits, including required rail car modifications, maintenance analytical techniques, and automation. All actions that show how WMATA is increasing availability and reliability while reducing costs.
As your moderator for the webcast I will keep things lively and give you teasers on what else is coming up for our activities around enterprise asset management for urban transit. Register today to attend a webcast on September 11 (or to listen on-demand afterwards) here.