RCM2 Case Study: Cooling Fan System Maintenance Project Plan

1. RCM2 Case StudyProject Plan Cooling Fan Systemhttp://maintenanceforums.com(topic link) 04 October 2007 Revision 1

2. Content • Introduction • Why this study • Output • Team • Planning • System boundaries • Functional Block diagram & Major Equipment • Key information • Let’s get started

3. Introduction From within the Maintenance Forum the initiative was born to conduct a “Virtual RCM” study to learn and share knowledge in an interactive way. A Case & Operating Context is defined for the Company Ollie’s Olefins based on business impact/criticality. There are a lot of methods which are called RCM In this study the RCM2 methodology of John Moubray will be applied

4. Goal and output Make a maintenance plan which preserve the functions of the chosen Cooling Fan System throughout the technologically useful live by selecting and applying the most cost effective technique for managing failures and their consequences Output: • Maintenance schema • Operator Care Instruction • Modifications (can also be operational procedure)

5. Team Team • Facilitator: Rogier • Team members:(list to be defined)It is nice to have a fixed team giving input during all steps to prevent having discussions all over again.

6. Planning • The project kick-off is in week 41 after publishing project plan on forum • Minimum 1 session a week depending on input • A live chat or telecom can be organised to discuss different views if necessary • Estimated time needed is 11 sessions, completion date end 2007 • Participant are assumed to have basic RCM knowledge starting the study Session Content Kick off – Setup project and team 1 session (WK 42) Functions and performance standards 1 sessions Functional Failures & Failure Modes 2 sessions Failure Effects 2 sessions Failure Consequences 2 sessions The RCM Task Selection Process 3 sessions Spare 2 sessions Finalizing report by facilitator 1 week

7. System Selection (Boundary)

8. Funct. Block diagram & Major Equipement

9. Key information • Plant located on island near to sea • Operation 24h/7 days a week /365 day’s a year • It can sell all product it can make • 30 equal systems in production unit • System supplies ambient air to refrigeration system • Performance indicator: If fan < 200 RPM audible alarm sounds in control room • Revenue loss of $5000 per hour if one system down for > 30 min • System cost a lot of maintenance hours due to breakdown disturbing the process (how much cost / failure history?)

10. Let’s get started • Who is willing to be part of the team? • let share email addresses within the team, mail me your email address please? • When the team is complete I will setup a platform to share / add remark or something to be able to give your input when it suits your agenda • We are in different time zone's I think, so live discussion can be a problem, Can we make an overview of possibilities when to discuss /chat live? • To share learning's everyone get’s read rights on chosen platform and only team member write rights • All information needed for study will documented and posted • Final Result per session will be post on maintenanceforum to share learning • English is not everyone’s native language so can give misunderstanding, treat everyone with respect, lets focus on the big picture and not argue about minor language details.

11. Step 1 functions • Step 1 – Describing functionsWe have enough information to start with defining the function A function statement should consist of a verb, an object and a desired standard of performance If we miss relevant information it will be an action point for someone to retrieve of we make a decision as a group We can use the template supplied by Rolly12 Other steps will be added during the study