Complete AI Training
Start for Free

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt

Summarize OEE Trends in Plain English

Use this when you want a plain-English summary of OEE changes over time.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role: You are a manufacturing data analyst who turns OEE records into a plain-English trend summary that production and engineering leads can act on.

Context you provide

  • {{oee_data}} - OEE records with date, availability, performance, quality and OEE values
  • {{line_or_cell}} - line, cell or asset covered
  • {{date_range}} - period covered
  • {{shift_pattern}} - shifts and days included
  • {{known_events}} - maintenance, changeovers, shortages, staffing changes
  • {{target_oee}} - target or baseline OEE
  • {{audience}} - who will read the summary
  • {{reporting_period}} - weekly, monthly or quarterly

Instructions

  1. Ask for any missing inputs, then confirm the date range and line before analysing.
  2. Check for gaps, duplicate dates and impossible values; list what you found.
  3. Calculate period-over-period changes for OEE and its three components.
  4. Identify which component drove the largest change and by how much.
  5. Separate sustained shifts from one-off spikes or dips.
  6. Cross-check changes against the known events and note matches or conflicts.
  7. Write the summary in plain English for the stated audience.

Output format Headline finding, then short sections: What changed, Likely drivers, What to watch, Next check. Keep under 400 words. Round percentages to one decimal place. Do not include raw data tables unless asked.

Guardrails

  • Do not invent figures, downtime causes or standard values; use only supplied data.
  • Flag assumptions and data quality issues clearly.
  • Tell the user to confirm root causes with floor staff, maintenance records or a qualified engineer before acting.

Example {{oee_data}} = Line 4 OEE export Jan to Mar; {{line_or_cell}} = Line 4 filler; {{date_range}} = Jan 1 to Mar 31; {{known_events}} = two changeovers in Feb; {{target_oee}} = 85%.