Failure Reporting, Analysis, Corrective Action System

5,634 views

Published on

FRACAS: A method of analyzing the failure codes assigned to the individual work orders and identifying common themes and trends. The root cause of the high impact items are determined, with a corrective action identified and executed to prevent reoccurrence of the issue.

Published in: Technology, Business
0 Comments
7 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
5,634
On SlideShare
0
From Embeds
0
Number of Embeds
17
Actions
Shares
0
Downloads
623
Comments
0
Likes
7
Embeds 0
No embeds

No notes for slide

Failure Reporting, Analysis, Corrective Action System

  1. 1. Copyright 2009 GPAllied©Failure Reporting, Analysis,Corrective Action SystemPresented by: Ricky Smith, CMRP
  2. 2. Copyright 2009 GPAllied©What is FRACAS?• A Failure Reporting, Analysis, and Corrective ActionSystem (FRACAS)– Process by which failures can be reported in a timely manner– Analyzed so that a Corrective Action System can be put in placeand eliminate or mitigate the recurrence of a failure.• The goal of FRACAS– Help an organization better understand failures– The reporting required to identify failures– Actions required to eliminate or mitigate failures
  3. 3. Copyright 2009 GPAllied©What is FRACAS?
  4. 4. Copyright 2009 GPAllied©Maintenance’s Objective“Mitigate Failures with an effective Maintenance Strategy”- Preventive Maintenance (quantitative inspection, restoration,replace, replenish, etc.)- Condition Monitoring (ID of a Failure early enough a failurecan be mitigated) also known as PdM- Run-to-Failure
  5. 5. Copyright 2009 GPAllied©PF CurvePriority 5 Priority 4Priority2Priority1Ultrasonic EnergyDetectedVibration AnalysisFault Detection Oil AnalysisDetectedAudible NoiseHot to TouchMechanicallyLooseAncillaryDamageFailureInitiatedConditionPRECISION PREDICTIVE PREVENTIVE RUN TO FAILURETimeCatastrophicFailureP-F CurveEquipmentCondition
  6. 6. Copyright 2009 GPAllied©Proactive Maintenance
  7. 7. Copyright 2009 GPAllied©FRACAS? Issues?“A Proactive Reliability Process is a supply chain. If a stepin the process is skipped, or performed at a substandardlevel, the process creates defects known as Failures.The output of a healthy reliability process is optimal assetreliability at optimal cost.”― Ron Thomas, former Reliability Director atDofasco Steel, Hamilton, ON
  8. 8. Copyright 2009 GPAllied©Causes of Failures• No repeatable procedures• Not executing PM to specification• Not performing Corrective Maintenance to specification• Personnel not trained (skills, maintenance, reliability)• Parts not stored to specifications• Not using the right tools• Best Lubrication Practices unknown• RCA is not applied or not known• No auditing of Maintenance Activity or Work
  9. 9. Copyright 2009 GPAllied©Known Best Practice Data• 15% of Maintenance Work is Execution of PM• 15% is the results of the PM ExecutionPM / PdM is a controlled Experiment• 15% of Maintenance is Execution of PdM• 35% is the results of PdM• Emergency Work – Less than 2%• Planned Work – 90%• Scheduled Compliance – 80% (by day by week)
  10. 10. Copyright 2009 GPAllied©Source: John Moubray, Nolan & HeapFailure PatternsTime TimeAge Related = 11% Random = 89%BathtubPattern A = 4%Wear OutPattern B = 2%FatiguePattern C = 5%Initial Break-in periodPattern D = 7%RandomPattern E = 14%Infant MortalityPattern F = 68%“Why is infant mortality so high?”Maybe because we do not apply the PF Curve Philosophy?
  11. 11. Copyright 2009 GPAllied©PF Curve with PrioritiesIdentify defect, Plan and Schedule Work Zone100%ReactiveWork
  12. 12. Copyright 2009 GPAllied©Work Priority DistributionPriority 1 and 2 Work is ReactivePriority 3, 4, and 5 Work is ProactivePM PdM CPM CPdM REQ
  13. 13. Copyright 2009 GPAllied©PF Curve and Managing Proactive MaintenancePoint PPoint F
  14. 14. Copyright 2009 GPAllied©Work Priority Distribution – a Few Simple RulesEMERGENT work is anythingthat is done as a Priority 1 or 2CORRECTIVE work isanything done as a result ofan inspectionCORRECTIVE work shouldnever be done as a P1 or P2ROUTINE work is anythingdone as a PRIORITY 3CORRECTIVE work can bedone as Priority 3CORRECTIVE work should bedone as a Priority 4 and 5Most CORRECTIVE workshould be done as P4 or P5 ifyou embrace P-F mentality
  15. 15. Copyright 2009 GPAllied©FRACAS Enables Success of an Organization
  16. 16. Copyright 2009 GPAllied©“It isn’t what you know that will kill you, it iswhat you don’t know that will”
  17. 17. Copyright 2009 GPAllied©It is all about the Data
  18. 18. Copyright 2009 GPAllied©How do you know where are?How do you know the Direction to reach you objective.?
  19. 19. Copyright 2009 GPAllied©Without good data we are lost!
  20. 20. Copyright 2009 GPAllied©“Bad Data” resulting in High Variation- Variation in your Maintenance Process- PM Program not effective- Variation in PM Compliance- PM program not focused on specific Failure Modes- Repeatable Corrective Maintenance Procedures notavailable or if available not used- Storeroom is a deathtrap for parts, little or no PMprogram on critical spares
  21. 21. Copyright 2009 GPAllied©Definition of Data Quality – ISO 14224Must have Confidence in the collected Reliability andMaintenance data, and hence any analysis, is stronglydependent on the quality of the data collected. High-qualitydata is characterized by:a) completeness of data in relation to specification;b) compliance with definitions of reliability parameters,data types and formats;c) accurate input, transfer, handling and storage ofdata (manually or electronic);d) sufficient population and adequate surveillanceperiod to give statistical confidence;e) relevance to the data users need.
  22. 22. Copyright 2009 GPAllied©
  23. 23. Copyright 2009 GPAllied©The International Standard for Failure Data
  24. 24. Copyright 2009 GPAllied©Failure Data – ISO 14224
  25. 25. Copyright 2009 GPAllied©ISO 14224 Maintenance Taxonomy Standard
  26. 26. Copyright 2009 GPAllied©ISO 14224 Maintenance Taxonomy Applied
  27. 27. Copyright 2009 GPAllied©Effects of Good Data Quality
  28. 28. Copyright 2009 GPAllied©KPI #1 – Asset Health ReportAsset Health Metric - The percent of assets with no identifiable “Defect”
  29. 29. Copyright 2009 GPAllied©KPI #2 – Mean Time Between Failure• Mean Time Between Failures (MTBF) is the average length ofoperating time between failures for an asset or component.(Definition extracted from Published SMRP Metrics)• MTBF is used primarily for repairable assets and components ofsimilar type. (Definition extracted from Published SMRP Metrics)
  30. 30. Copyright 2009 GPAllied©KPI #2 - MTBF Example / Reporting by TaxonomyEquipment Taxonomy (ISO 14224)Systematic classification of equipment into generic groups based on factorspossibly common to several of the itemsArea Level MTBF Component Level MTBF
  31. 31. Copyright 2009 GPAllied©KPI #3 – MTBF / “Equipment Condition Report”Asset Health Metric - The percent of assets with no identifiable “Defect”
  32. 32. Copyright 2009 GPAllied©KPI #4 – “Equipment Condition Report / Equipment Detail”Asset Health Metric - The percent of assets with no identifiable “Defect”
  33. 33. Copyright 2009 GPAllied©KPI #5 – Route Compliance
  34. 34. Copyright 2009 GPAllied©Route Compliance Impact on Asset Health ReportAsset Health Metric - The percent of assets with no identifiable “Defect”
  35. 35. Copyright 2009 GPAllied©KPI #6 – Monthly Maintenance Cost % of RAV• Maintenance Cost- Labor Cost- Material Cost- Contract Maintenance Cost- Overtime Cost• Correlate Cost to Other KPIs
  36. 36. Copyright 2009 GPAllied©Data Accuracy Requirements• Process Map• Roles and Responsibilities Identified
  37. 37. Copyright 2009 GPAllied©The 7 Steps to a Successful FRACAS
  38. 38. Copyright 2009 GPAllied©Step 1 – Determine your end goal.• The beginning of every journey starts with a destination• The beginning of the journey to an effective FRACAS is the same asany other• You must have an end goal in mind• The goal of a FRACAS is not to gather data, but to eliminate failuresfrom the organization• Knowing this helps ensure that every policy, procedure, and activity inthe system is goal oriented• The roles, goals, and responsibilities of everyone involved with thesystem can be focused toward that goal• Having the goal in mind allows you to build the shared vision andvalues that will make the system work successfully for you
  39. 39. Copyright 2009 GPAllied©Step 2 – Create the Data Collection Plan1. Determine the measures you will use– MTBFMean Time Between Failures (MTBF) is the average length of operating timebetween failures for an asset or component. MTBF is used primarily forrepairable assets and components of similar type.– MTTFMean Time to Failure (MTTF) is the average length of operating time to failureof a non-repairable asset or component, i.e., light bulbs, rocket engines. Arelated term, Mean Time Between Failures (MTBF), is the average length ofoperating time between failures for an asset or component. Both terms are ameasure of asset reliability and are also known as Mean Life.
  40. 40. Copyright 2009 GPAllied©Continued2. Determine what data needs to be collected to create the desiredmeasures
  41. 41. Copyright 2009 GPAllied©Continued3. Determine how the data will be collected- There are different types of data that need to be collected- Determine how the data will be collected- Failure data can be collected through the EAM/CMMS, automated processdata systems, or by using checklists4. Determine how data will be analyzed– The best bet is probably to start with Pareto– Just make sure to remember that data analysis - where to apply methodsJDI, RCA and RCM– Do not fall victim to analysis paralysis. Analytical reports are nice, but nostatistic ever solved a problem
  42. 42. Copyright 2009 GPAllied©Keep it simple in the beginning3rd2nd1st# of Failure byarea# of Failures byEquipment# of Failure byComponent or Part
  43. 43. Copyright 2009 GPAllied©Examples – Dominant Failure PatternMTBF –Object Type(Electric Motor)Cause Code=# LOL = 5%# MAERR = 10%# LOP = 20%# OPER = 65%FailurePatternCause Code=# LOL# MAERR#LOP# OPERNew Failure Pattern
  44. 44. Copyright 2009 GPAllied©Example Continues• % of Assets with No Identifiable Defect• Failure Rate for Specific ComponentsDrive Belt-Broken-Ageing Failure Rate0 602.49 1205 1807.5 2410 3012.5 3614.9 4217.4 4819.9 5422.4 6024.9Time00.000106960.000213930.000320890.000427850.000534810.000641780.000748740.00085570.000962660.0010696FailureRateRegionalised rateDistribution rateP0: 0%B20: 3492B15: 3208B10: 2858ε: 0.05664ρ: 0.9781γ: 0β: 3.745η: 5212Median rank2-parameterWeibull
  45. 45. Copyright 2009 GPAllied©Step 3 – Determine Organizational Roles, Goals,and Responsibilities (RACI)• Who collects the data?• Who analyzes the data?• Who takes what action based on analysis results?
  46. 46. Copyright 2009 GPAllied©Develop Process Map / Maps
  47. 47. Copyright 2009 GPAllied©Develop a RACI Chart for each Process MapDecisions/FunctionsMaint.ManagerMaint.SupervisorReliabilityEngineerMaint.PlannerMaint.TechFailure Data Entry I A C I RData Accuracy A R C C CRCA – Invalid Data I A R C RAnalysis of Data A I R C CActions Identified A C R I CActions Taken A R C C IFRACAS Activated A R C C I
  48. 48. Copyright 2009 GPAllied©Step 4 – Create the FRACAS Policies andProcedures Manual• Policies and Procedures Manual that will serve as the basis formanaging and administering the FRACAS system• This is a tedious step, but should not be skipped• This Manual will serve as the basis for developing:– Initial FRACAS Training for all key personnel– Ensuring that new employees understand and participate inFRACAS effectively– Best to develop a FRACAS Management Manual and a pocketsize book that is easy for people to carry around and refer to asrequired
  49. 49. Copyright 2009 GPAllied©What should be in the Manual?• Let’s develop this together to insure we both agree on the content• The manual should have at the minimum– Definition of FRACAS– Benefits of FRACAS– Managements’ Guidance– Managements’ Expectations– Roles and Responsibilities by position– FRACAS reports– Key data which must be input to generate these reports– What these reports will do for the mine– Training Outline for each person based on RACI Charts
  50. 50. Copyright 2009 GPAllied©Step 5 – Develop FRACAS Training Plan• Each person in the organization will need to be trained according totheir level of participation in the FRACAS• Use the Tasks Listed on all RACI ChartsDecisionFunctionMaint.ManagerMaint.SupervisorReliabilitySpecialistMaint.PlannerMaint.TechFailure Data EntryData AccuracyRCA – Invalid DataAnalysis of DataActions TakenFRACAS Activated
  51. 51. Copyright 2009 GPAllied©Training Plan Requirements- Training Plan should consist of the following Position : Maintenance Technician Task: Close out a Work Order Condition: Given 5 Completed Emergency Work Orders Standard: Close out Work Orders to 100% Compliance Method of Training: Lecture, Web, Reading, etc. Method of Validation: Written Test, Web Test, Verbal Recall, etc.
  52. 52. Copyright 2009 GPAllied©Step 6 – Implement FRACAS• Let’s turn it on– Publish FRACAS Policies and Procedures Manual– Train required personnel– Hold required informational meetings– Begin data collection on highest priority area– Analyze data and report results on Public FRACAS InformationBoard– Create corrective actions based on results.• Mitigation of Human Error• Changes to the current maintenance strategy• Changes to how production operates equipment• Resign Equipment
  53. 53. Copyright 2009 GPAllied©Step 7 – Monitor, Show Success, and Adjust• Monitor data quality and resultsDecisionFunctionMaint.ManagerMaint.SupervisorReliabilitySpecialistMaint.PlannerMaint.TechFailure Data Entry I A C C RData Accuracy A R C C IRCA – Invalid Data A C R I CAnalysis of Data A I R C IActions Taken A R C R IFRACAS Activated A R R C I
  54. 54. Copyright 2009 GPAllied©Monitor and Adjust• Good data is the backbone of good decision making• It is important to monitor data quality• Make adjustments to either the data collection plan or the trainingprogram• Insure data is consistent and informative• Many organizations believe they have good data only to find outtheir data collection is inconsistent
  55. 55. Copyright 2009 GPAllied©Questions?

×