1. Knowledge requirements for rolling stock maintenance TU Eindhoven – 19th of June 2007 by Bob Huisman (b.huisman@nedtrain.nl) NedTrain - Fleet Management Strategic Development

2. Pagina 2TU Eindhoven - 19th of June 2007 NedTrain is part of the NS Group NedTrain provides Rolling Stock Maintenance, Cleaning and Overhauling

3. Pagina 3TU Eindhoven - 19th of June 2007 Questions & Challenges 1.How to preserve knowledge and experience? Older people retire, but older systems (should) remain operational. 2.How to obtain knowledge about reliable complex technical systems? Configuration, condition, use, contracts, performance? What should be done and when? How? Better system performance means less diagnostic experience! 3.How to share knowledge in a highly flexible organisation? How to deal with different systems over time, at different locations? 4.How to exchange knowledge between companies across borders? Many companies are involved in the life time of a technical system. How to communicate between different local (national) cultures?

4. Pagina 4TU Eindhoven - 19th of June 2007 Double goal: effectiveness and efficiency

5. Pagina 5TU Eindhoven - 19th of June 2007 Goal 1: to maintain system functionality (effectiveness) 100% Time YesterdayTodayTomorrow? How do functions evolute?When is a functional failure to be expected? What maintenance is required? When?

6. Pagina 6TU Eindhoven - 19th of June 2007 Goal 2: to minimize means of production (efficiency) 100% Fleet availability Use of maintenance means of production Past Future

7. Pagina 7TU Eindhoven - 19th of June 2007 Effective maintenance: derive required maintenance from technical condition of individual systems by intelligent reasoning

8. Pagina 8TU Eindhoven - 19th of June 2007 Component Function Use How to predict degradation and failure? 100% Time New Time Functionality Dimension, quantity - Time Cycles, energy Now influences technical condition enables/disables function Extrapolation Cause-effect analysis Wear and tear modelling

9. Pagina 9TU Eindhoven - 19th of June 2007 Component 1Component 2Component 3Component 4 Function AFunction BFunction CFunction D UsageIncidents EnvironmentMaintenance Technical system Complex interaction between use, components and functions

10. Pagina 10TU Eindhoven - 19th of June 2007 Computer system Predictive model (not perfect) Predictive model (not perfect) Mimic model (not perfect) Mimic model (not perfect) Technical system Mimic model (not perfect) Maintainer Observer and interpretator Jobs Technical status Derive required maintenance continuously during operation Measurement Synchronisation Predictive model (not perfect) Expected status Required Maintenance Maintenance plan Maintenance rules and job descriptions Knowledge Configuration Design, Requirements, Environment, Use Configuration Expected use

11. Pagina 11TU Eindhoven - 19th of June 2007 Efficient maintenance: derive maintenance schedule from required maintenance and availability of means of production by intelligent reasoning and negotiation

12. Pagina 12TU Eindhoven - 19th of June 2007 Manufacturing Supplier Backwards scheduling (Pull) Delivery date Quantity Design Quality Price Order Production & Delivery orders Scheduling manufacturing orders New products

13. Pagina 13TU Eindhoven - 19th of June 2007 Maintenance production Supplier Maintenance plan Throughput Quality Price Contract Scheduling (Push) km-counter Local scheduling Technical condition Production order Traditional rolling stock maintenance scheduling Maintained products Arrival & Inspection orders

14. Pagina 14TU Eindhoven - 19th of June 2007 Technical condition Required maintenance Maintenance schedule Maintenance planTransport operations Required staff, shop and stock Availability of staff, shop and stock Future maintenance scheduling

15. Pagina 15TU Eindhoven - 19th of June 2007 Maintenance production Supplier Backwards scheduling (Pull) Technical condition Production & Delivery orders Generate maintenance required Maintenance plan Throughput Quality Price Contract Request Rolling stock condition based maintenance scheduling Maintained products

16. Pagina 16TU Eindhoven - 19th of June 2007 Depot Train Agent (depot ) Agent (train ) Agent (train ) Train Intelligent agent (train ) DepotOperator Intelligent agent (operator ) Intelligent agent (depot ) Configuration Maintenance rules Time table StatusAvailability Work ordersTransport orders Co-ordinationNegotiation Maintenance scheduling by a Multi Agent System (Society)

17. Pagina 17TU Eindhoven - 19th of June 2007 Where do we need knowledge of operation? Tactical (Maintenance Plans, Means of Production, Organisation) Operational (Maintenance Planning and Control) Depot / Workshop (Performing Maintenance) Technical Condition of Rolling Stock Diagnostic Data Operation Data Inspection and Maintenance Orders Maintenance Plans Performance Requirements Performance of Rolling Stock and Maintenance Results Fleet Performance Trains Strategic (Rolling Stock, Locations, Contracts) Trains Railway Operators Government, Authorities Infrastructure Managers Traffic Control Rolling Stock Manufactures

18. Pagina 18TU Eindhoven - 19th of June 2007 Thanks for Your Attention! Any questions?

19. Pagina 19TU Eindhoven - 19th of June 2007 Train Coach Boogie MotorWheel set Consists of Is part of Subsystem Component tree

20. Pagina 20TU Eindhoven - 19th of June 2007 To transport passengers To drive To offer comfort To remain on track To accelerate To offer seats To control climate To decelerate Function tree To inform Requires

21. Pagina 21TU Eindhoven - 19th of June 2007 To transport passengers To drive To remain on track To accelerate Train Boogie Wheel setMotor Energy supply Relations between functions and components

22. Pagina 22TU Eindhoven - 19th of June 2007 Triple valve leaks, caused by dirt Air pressure drops, coach does not brake, causing lower train deceleration Train at 140 km/h does not stop within 1000m Failure does effect safety directly Frequent test of brake system Enable train driver to brake and to stop Function Root failure Failure effect Functional failure Business consequence Maintenance RCM (Reliability-Centred Maintenance) analysis

23. Pagina 23TU Eindhoven - 19th of June 2007 Function Functional failure Failure effect Root failure Functional failure Failure effect Root failure Function Functional failure Failure effect Root failure Functional failure Failure effect Root failure Complex cause-effect relations

24. Pagina 24TU Eindhoven - 19th of June 2007 Design of Technical system Maintenance engineering Maintenance plan Technical system Construction Requirements, Environment, Use Real life Expected conditions and use Phase 1 Phase 2 Phase 3 System design, maintenance engineering and operation

25. Pagina 25TU Eindhoven - 19th of June 2007 Implementation model

26. Pagina 26TU Eindhoven - 19th of June 2007 Ontologies en RDF