Act as a manufacturing operations analyst supporting a plant manager. Analyze [MANUFACTURING DATA] against [TARGETS AND BASELINE] for [PRODUCT OR PROCESS] during [ANALYSIS PERIOD]. Use the operating context in [PLANT CONTEXT] and constraints in [CONSTRAINTS]. First, state the data limitations, missing fields, and any definitions that could change the conclusion. Do not treat correlation as proof of root cause. 1. Calculate or show the logic for the relevant measures: planned versus actual output, attainment, OEE and its availability/performance/quality components where data permits, first-pass yield, scrap/rework rate, downtime Pareto, changeover time, labor productivity, and schedule adherence. Keep units and denominators explicit.
2. Identify the three largest performance gaps by financial, customer, safety, or throughput impact. Separate observed facts from hypotheses. 3. For each gap, give a root-cause investigation path using 5 Whys only after defining the problem precisely; include checks for machine, method, material, manpower, measurement, and environment. Name data needed to confirm or reject each hypothesis. 4. Produce a 30-day action plan in a table: action, owner role, due date, leading measure, expected impact, dependency, and escalation trigger. Favor containment actions before permanent corrective actions. 5. End with a one-page plant-review narrative in plain English. Output sections: Executive summary (150 words maximum), metric table, Pareto findings, root-cause test plan, 30-day action table, and risks. Ask up to 3 clarifying questions only if a required input is missing. Before answering, self-check that every calculation has a stated denominator and that no proposed cause is presented as confirmed without evidence.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [MANUFACTURING DATA] | Paste production, quality, downtime, labor, and schedule data, including column definitions and units. | Line 3, Aug 1-31: planned 48,000 units; actual 41,200; scrap 1,648; downtime 92 hours, with 31 hours feeder jams and 18 hours labeler faults. |
| [TARGETS AND BASELINE] | Enter current targets plus a comparable prior period or standard performance level. | Output target 46,500; scrap target under 2.0%; July actual output 45,900 and scrap 2.3%. |
| [PRODUCT OR PROCESS] | Name the product family, line, cell, or process being analyzed. | 500 ml bottled beverage filling and packaging line |
| [ANALYSIS PERIOD] | Enter the exact dates, shifts, and operating days covered. | August 1-31, 2026; two 10-hour shifts, Monday through Friday |
| [PLANT CONTEXT] | Describe equipment, staffing, demand, routing, quality requirements, and recent changes. | One filler, capper, labeler, and case packer; new bottle supplier began August 8; planned maintenance occurs Sundays. |
| [CONSTRAINTS] | List safety, maintenance windows, budget, supplier, staffing, or customer constraints. | No unplanned shutdown over four hours; maintenance crew has one technician available on weekdays. |
How to use
- Export the relevant line or plant data with dates, units, and definitions, then paste it into the prompt.
- Include the target and a prior comparable period so the analysis can distinguish a real decline from normal variation.
- Check each percentage denominator and make sure hypotheses are not labeled as proven causes.
- Follow up with: “Turn the action plan into a daily tier-meeting board with red/yellow/green thresholds.”
Variations
Downtime Pareto
Use when recurring equipment stops are the main issue.
Analyze [DOWNTIME LOG] for [LINE] from [DATES]. Group stops by equipment, fault code, shift, product, and duration; clean obvious naming duplicates but list the changes made. Produce a Pareto table, the cumulative share of lost minutes, and the five events that deserve investigation. For each priority event, give containment, likely failure modes, evidence needed, owner role, and due date. Do not call a cause confirmed from a fault description alone. Check that total grouped downtime reconciles to the source total.
Quality CAPA
Use when defects, complaints, or rework have increased.
Help me prepare a quality investigation for [DEFECT] affecting [PRODUCT] between [DATES]. Use [QUALITY DATA] and [PROCESS HISTORY]. Write a problem statement with defect rate and denominator, define immediate containment, map possible causes across material, machine, method, measurement, people, and environment, and propose verification tests. Produce a CAPA table with owner, due date, effectiveness measure, and closure evidence. Flag any claim that needs records, samples, or validation before it can be accepted.
Capacity plan
Use when deciding whether the plant can meet expected demand.
Build a capacity assessment for [PRODUCT FAMILY] using [DEMAND FORECAST], [ROUTING AND CYCLE TIMES], [AVAILABLE HOURS], and [CONSTRAINTS]. Calculate required versus available capacity by work center, identify the bottleneck, and show assumptions about yield, changeovers, utilization, and staffing. Give three scenarios: base, recoverable improvement, and constrained. Output a weekly table and a decision list for overtime, sequencing, subcontracting, or capital review. Check that demand quantities flow consistently through yield losses.
Tips
- Use a consistent definition of planned production time before comparing OEE; including breaks or planned maintenance in one month but not another makes the result misleading.
- Keep downtime reason codes specific enough to act on; “mechanical” is usually too broad for a useful Pareto.
- Compare shifts and product runs before blaming operators, because mix, changeovers, and material lots can explain apparent labor differences.
- Make effectiveness measures leading where possible, such as jam events per 1,000 bottles, rather than waiting only for month-end output.
FAQ
Can AI identify the root cause from a downtime log?
It can prioritize hypotheses and tests, but a log alone rarely proves a physical root cause. Confirm conclusions with observations, maintenance records, samples, or controlled trials.
What data should I provide for an OEE analysis?
Provide scheduled time, planned downtime, unplanned downtime, ideal cycle rate, total count, and good count, with the definitions your site uses.
Should corrective actions have named people?
Use accountable owner roles in the analysis, then assign individuals through your plant's normal management process.