Thanks Steve - seeing we are the only ones currently participating i suggest looking at Trevors and assessing whether the ones he's listed are already covered by mine (good effort though Trevor) and if not then including them using the RCM2 protocol.
Functions must be described using verb then object and incl. performance standard if one exists.

Rogier perhaps you can jump in here and critique mine and Trevors lists and if everyone is in agreeance - perhaps lets set a deadline of 24 hours (hopefully all particpants look at the board at least once a day) then lets at least have all the functions listed by next week.

Mike.

Yes - its time for the facilitador.
Come in Rogier

Wow we have started

I have updated the rcm2 template with a extra tab for discussion and my remarks and questions concerning the functions.
Team members please prefer do do your remarks directly in a collumn in the excel sheet. the public file is direcly updated for everyone to read. And every week I will post the result in this forum.

Extra info for functions:

Primary functions: What's the main reason the asset exist?
Secondary functions: Asset is expected to fulfill one ore more functions in addition to their primary function

To help none of these functions is overlooked they are diveided in 7 categories (ESCAPES):
- Environmental integrity
- Safety/structural integrity
- Control/containment/comfort
- Appearance
- Protection
- Economy/Efficiency
- Superfluous functions

All, please check if these are covered

One of the most mistakes in the RCM process is carrying out the analysis on too low level in the equipment hierarchy. This results in the same failure modes and consequences at different functions making it a time consuming process, demotivating the team.

public documents (links will remain the same during this excercise):
Updated projectplan V2
RCM2 template

For people who have no access to public docs? I have also attached the document.

RCM2_Worksheet.xls (51 KB, 121 downloads)

I have been asked two questions about the following
Mesh
FN 10.To prevent foreign objects from entering the duct.
Q performance standard? i.e. particles > X mm, Steve advise

I think the mesh is there to stop people - it is rather wide spaced mesh - like about 100mm. I dont know exacly - I didnt design the thing and there is no manual for the complete assembly. It stops rubbish too - but some still gets through - like chip packets. I dont think these are a problem; they just shoot out the other end. I guess small birds could go up the chute - I guess it would keep out an emu unless it stuck its head in. But to get to the fan, the emu would have to climb the steps cos they dont fly.... sorry - got carried away.

FN 9.To lock the fan in position
Q No indication this functionality is available / needed; Steve advise

This bolt is referred to as the Geez nut pin. It is similar to the geez nut pin used in helicopter rotors - you know the one that stops the rotor nut from comming loose. Like if the Geez nut comes off, the rotor comes off and the crew go Geeeeez. Now the bolt should not unwind on its own - unless it is not tightened properly in the first place. In this case the designers have installed this locking device to double secure the fan hub nut.

FN 20 To provide a reduction in speed & transfer torque
Q Range; Steve please advise

I dont know off hand - I can find out but not just now. Cant see why it matters - we have a 20 hp motor and if you got the amps I guess you could figure out the power consumption... might be getting analysis paralysis. Let me know if you want me to spend a few hours to chase this one up.

Rogier - agree with Steve - its either transfering torque or failed - don't get bogged down with performance standards on secondary functions as a rule.

Mike.

Rogier, Steve, Mike and all

Excellent - I love the Google docs - have never used them before.

I would like to suggest two online briefings held on the same day 12 hours apart - example 9 am EST (GMT- 5) and 9 pm EST some day next week - preferably Thursday to give me time to extend invitations to a wider audience.

We have an online meeting platform for 1000 people and I can hand the presentation to Rogier and Steve - and they can present anything that can see on their monitors.

Participants dial in using the telephone to a USA based number (so long distance may be an issue for International callers) to hear presenters.

If you think it would be beneficial I think we can involve a lot more people if we take some time to lay a little more groundwork before it gets too deep.

Rogier and Steve - I will wait to hear from you re:

1) If you think I should facilitate a live briefing (held twice in the same day 12 hours apart to allow everyone to attend)

2) If you agree that Thursday November 1 would work

Terry O

Hi Terrence,

It's a nice initiative, I hope it will result in a bigger response. The discussion per session must be limited because it's during working hours although it's a cheap education for the boss . For me the international dial in will be a problem. A search on the net give me a few free alternatives with local dial in like http://www.powwownow.com/ maybe it's a nice alternative?

It might be a bit hard for a live briefing and in some ways restrictive - if you miss the briefing does that mean you miss out?
The case study I posted has a good narrative and I have data I can post at the right time. It would be good to store all the info on one notice board so it is all in one, easy to find place.

Rogier - the meeting system we use has its own dial in feature so I do not think the powwownow will work - but thank you for the link as I think myself and others may be able to use it in the future.

Steve - OK if not "live briefing" can you and Rogier simply "record" audio explanations of this project and how novices should participate? I can post them and announce them.

Does that sound OK?

Terry O

PS: This suggestion is not meant to slow things down and I hope it is not a distraction. Feel free to ignore and proceed.

Hello all,

I see almost no remarks on the functions of friday last week. Everyone agreed with them, to busy or on holiday? A reply once a week would be nice to keep this excercise going on. I hope we can still make progress this week. Please share your view and don't bother to be critical.
Let us all learn from each other.

Regards Rogier

quote:

Originally posted by Rogier:
Hello all,

I see almost no remarks on the functions of friday last week. Everyone agreed with them, to busy or on holiday? A reply once a week would be nice to keep this excercise going on. I hope we can still make progress this week. Please share your view and don't bother to be critical.
Let us all learn from each other.

Regards Rogier

Hi Rogier
Apologies for the delay in providing comments on the proposed list of functions.

Having previously submitted some additional functions at component level I am now starting to wonder whether we are going to end up attempting an analysis of the functions at the component level rather than attempting an analysis of the functions at the Cooling Fan System level and what , if any difference it would make , in terms of time taken and quality of outcome .

If we were to attempt the analysis at the equipment system level then i would perhaps only identify the following two functions .
1.To provide cooling air at x m3 / hour
2.To provide cooling air at the required performance level in a safe manner

The next step would be to identify the typical functional failures for each function ie
Cannot provide the function at all ,
Cannot provide the function at the required performance level ,
Provides the function in excess of the required performance level , and
Does provide the function at the required performance level but in an unsafe manner

The next step after that would be to identify the component failure modes that cause each of the functional faiures identified above eg seized bearings, loose drive belts, emergency stop switch failure etc

At this stage I think it would be usefull to gain agreement on the level at which we should be attempting to do the analysis ( component level vs equipment level) before we progress any further

Your thoughts ?

Trevor

Agree Trevor,
I think there should be a lot more discussion about the functions. I have asked Rogier - off line - to attach the spreadsheet to the post so that we can all easily see the spreadsheet.
Rgds
Steve

This message has been edited. Last edited by: Steve Turner,

To get this discussion as clear as possible below my reply to to Steve's off line mail.
-------------
Hi Steve,

Thanks for your reply.
It's no problem at all to post the latest excel sheet, that exactly what I told I would do.
Having comments from only Mike and Steve when having 7 active team members I was awaiting more response before updating and post the sheet.

Josh suggested a special platform to be set to do the online RCM, you suggested SharePoint of something similar what I think was a good idea.
I choose google docs which have great functionality for this type of group work.
People not having access or finding it too difficult can post the remarks of course also on this forum, but putting it directly in excel saves me time and remarks are far more clear for everyone to read then posting them separate.
-------------

In the mean time trevor als thanks for your reply. Is it possible for the others to share their view before sunday when I will have time to update?

What do you think of the google docs sheet, keep or kill? No use keeping it alive if no one uses it.

Regards,

Rogier

The google docs is blocked by our firewall, thus I am limited during working hours. I think others also experienced this. On the other end it is very functional. Keeping the docs and regularly posting the update on this forum would be the best way. I think the functions of the cooling system as an entity has been described sufficiently, and IMO it is time to move to the next step.

Regards

Hi - good to hear from Trevor and Steven - Yousiff,Johnny and Bruno are conspicuous by their absence - hopefully we will hear from them in due course even if it is only to agree with what has already been said.
As for myself as I felt I had said enough and wanted to stand back a little I agree with Steven - we should move on.
I think Trevor is right - we need to decide level - I think component would give us a more intensive analysis - I would prefer this level even at risk of repetition purely on the basis of not missing anything. When we get to failure modes we can just say "see 1B" or something like that.
Lets not get silly though - no need for example to look at the failure modes of a bearing.



Mike.

I always like to go at the highest level that will accommodate the needs.

OK, sorry to be so conspicuous through absence. When we kicked this thing off, I had yet to pick up an extra persons worth of duties.
I have tried to keep up and really don't have anything to add. I think everything is going well so have just been observing. Without making a long discussion of MTBF source, I hope to contribute during the task analysis/ P-F/ analysis results and implementation plan aspects of this exercise.

Best Regards:

Johnny W. Campbell

Did I miss something or are we still on functions?

quote:

Originally posted by Johnny W. Campbell:
Did I miss something or are we still on functions?

I have added my thoughts to the Google spreadsheet on Functions , functional failures and failure modes working at the system level rather than the component level.

Guys,
Here are my suggestions for the functions:
1.To provide constant airflow to the heat exxhanger by rotating at a speed of at least 200RPM
2.To allow access to the fan for maintenance
6.To stop fan in the event of an emergency
7.To contain oil in the gearbox
8.To direct the airflow and prevent flow losses at the blade tips
9.To prevent the fan blades coming off in the event that the hub is incorrectly installed
10.To prevent rubbish, foreign objects and people from entering the duct when the fan is in motion.
11.To support the fan and associated components.
15.To shut down the fan when access door is opened without first shutting down the fan
16.To shut down the fan in the event of abnormal vibrations.
22.To shut down the fan motor in the event of the motor overheating.
26.To sound an alarm in the control room if the fan belt comes off.
To minimise shocks and vibrations prematurely wearing the coupling, and other rotating components


I think that the spreadsheet should be attached to the thread as well as in google docs. This means it is easy to get a hold of.

Rgds
Steve