.
Does SAP R/3 support you to decrease your vehicle fleet size and maintenance costs of rolling stock?
Most public transportation companies are experiencing a more competitive environment due to the increased number of entrants, concessions requirements and more mileage demand with the same or less rolling stock. This negatively affects the maintenance and rolling stock costs. Organizations need to improve the efficiency of their maintenance in order to control the costs of their operation and potentially reduce the fleet size.
Until today there was no overall solution (Process, Organization and IT) for the maintenance units shop floors. Together with leading public transportation companies in the Netherlands, RET Rotterdam and GVB Amsterdam, a new 3 dimensional approach has successfully been developed and implemented.
Customer benefits
Standard SAP R/3 is mainly focused on plant/project maintenance and not on Repetitive Planned Maintenance (RPM). With our newly developed solution, customers experience benefits such as:
- Increased shop floor productivity and efficiency up to 15%
- Decreased (rotation) parts in stock up to 30%
- Enhanced functionality dedicated to RPM for rolling stock, resulting in better visibility into future capacity and material requirements.
- Improved RPM processes within SAP R/3, resulting in less planning FTE’s needed
Automatically synchronized planning boards
Finally, the planning has to be visible in your maintenance unit at several locations and not only in the planning office! Almost all of currently used planning boards are not automatically synchronized with SAP R/3 and lack enhanced planning functionality, such as;
- Shop floor requirements (Support equipments, qualifications, number of tracks)
- Interactive exception messages (Signaling when a maintenance order is too late, components are missing)
- Service level agreement of your customer related to the availability of certain types of rolling stock
- Information available on multiple planning boards
- Identify the best investment to resolve existing bottle necks, increase throughput, achieve minimum throughput rates
*Depending on the maturity of the current way of working.