Build a process FMEA for a new or changed production step
A process FMEA table with failure modes, effects, causes, current controls, and severity/occurrence/detection ratings, plus prioritized actions.
The prompt
Help me build a process FMEA (PFMEA) for a production step.
Process step(s): [e.g. "Op 30: press-fit bearing into housing"]
What changed or why now: [new line / new part / process change / customer complaint / annual review]
Product requirements this step must deliver: [special or critical characteristics, tolerances, torque, dimensions]
Equipment and controls in place today: [machines, fixtures, poka-yokes, gauges, inspection frequency]
Known history: [past defects, scrap reasons, complaints, or "none"]
Rating scale we use: [AIAG-VDA 2019 with Action Priority / classic RPN / our own 1-10 tables]
Work through the step like a cross-functional team would:
1. Break the step into its process functions and requirements.
2. For each, list realistic failure modes (what goes wrong at this step), the effect on the next operation, the end customer, and safety or regulatory compliance, and the causes at the 4M level (man, machine, method, material) plus environment and measurement.
3. List current prevention controls and detection controls separately. Do not count an operator visual check as strong detection.
4. Suggest severity, occurrence, and detection ratings with a one-line reason each, and mark every rating [TEAM TO CONFIRM].
5. Rank by Action Priority (High/Medium/Low) or RPN, whichever scale I named.
Return:
- A table: Function/requirement | Failure mode | Effect | S | Cause | Prevention control | O | Detection control | D | AP or RPN | Recommended action | Owner | Due date.
- The top 5 risks with an action that lowers occurrence or improves detection, preferring error-proofing over added inspection.
- Questions the team must answer on the floor before finalizing.
Do not invent defect rates or history. A PFMEA is a team document: treat this as a first draft for the team review, not a finished analysis.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- e.g. "Op 30: press-fit bearing into housing"
- machines, fixtures, poka-yokes, gauges, inspection frequency
- past defects, scrap reasons, complaints, or "none"
- TEAM TO CONFIRM
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Redesign a process for speed and quality with a future-state mapRedesigns a current process into a faster, higher-quality future-state workflow and compares the two side by side so you can get approval.
- Turn my project plan into an Excel task tracker with owners and dependenciesBreaks a project or plan into a task tracker with owners, dates, dependencies, and status columns you can paste into Excel.
- Run a health check on my project and find what is going wrongScores your project across scope, schedule, budget, risk, team, and stakeholders, and pinpoints the real problems behind the noise.
- Audit my project plan for missing owners, deadlines, and unaddressed risksChecks your plan or tracker for tasks with no owner, no deadline, vague deliverables, and risks nobody is managing.