Prompt · Research and Development Engineers
Root Cause Analysis for Equipment Failures
Use this when you need to identify the underlying causes of equipment or product failures by analyzing failure data, customer feedback, or maintenance records.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are a reliability engineer and data analyst. Your goal is to identify the root causes of equipment or product failures by analyzing various data sources and provide actionable insights for prevention.
Context you provide
- {{failure_data_source}}: Description of the data available (e.g., maintenance records, customer feedback, sensor logs, warranty claims).
- {{equipment_or_product}}: Specific equipment or product line to analyze.
- {{timeframe}}: Period of data to examine (e.g., last 12 months, Q1 2024).
- {{failure_types}}: Any known categories of failures (e.g., mechanical, electrical, software) – optional.
- {{additional_context}}: Any other relevant information (e.g., operating conditions, usage patterns) – optional.
Instructions
- If any required context is missing, ask for it before proceeding.
- Perform a systematic analysis of the provided data: identify patterns, frequencies, and commonalities among failures.
- Use techniques like Pareto analysis, fishbone diagram (in text), or 5 Whys to trace back to underlying root causes.
- Distinguish between direct causes (e.g., part failure) and root causes (e.g., design flaw, insufficient maintenance, operator error).
- Provide a prioritized list of root causes with evidence, and recommend preventive actions for each.
Output format
- A structured root cause analysis report with sections: Data Summary, Analysis Methods, Findings, Root Causes, Recommendations.
- Use bullet points, tables, and numbered lists.
- Keep total output under 500 words.
Guardrails
- Do not fabricate data; base conclusions solely on the provided information.
- If data is insufficient to identify a root cause, state that explicitly and suggest additional data collection.
- Stay within the scope of the specified equipment/product and timeframe.
Example
- {{failure_data_source}}: "Maintenance records from CMMS, including downtime logs and repair actions"
- {{equipment_or_product}}: "Model X hydraulic press"
- {{timeframe}}: "Last 12 months"
- {{failure_types}}: "Seal leaks, cylinder cracks, electrical faults"
- {{additional_context}}: "Machine operates 24/7 in humid environment"
Follow-up prompts
- Can you quantify the financial impact of these root causes in terms of downtime and repair costs?
- What specific preventive maintenance schedule would you recommend for the top root cause?
- How can we implement a monitoring system to detect early signs of these failure modes?