production-oee

Calculates OEE from availability, performance, and quality data with daily reports and loss analysis.

1|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/tapway/shogun-os --skill production-oee-tapway
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: production-oee
Source: https://github.com/tapway/shogun-os/tree/main/skills/manufacturing/production-oee
Command: npx skills add https://github.com/tapway/shogun-os --skill production-oee-tapway

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Manufacturing teams need a consistent way to measure production efficiency, but manually computing Overall Equipment Effectiveness across shifts, lines, and plants is error-prone and slow. This Skill automates OEE calculation and reporting so production managers can spot losses and track trends without spreadsheet work. ## Core Features & Use Cases - OEE Calculation: Computes Availability × Performance × Quality per shift, line, or plant against a configurable target (default 85% World-Class). - Daily Reports & Trends: Generates daily OEE reports with breakdowns by shift and line, plus multi-day trend tracking. - Top Loss Identification: Ranks the five loss categories (breakdown, setup, idling, speed loss, defects) with Pareto analysis to focus improvement efforts. - Use Case: A production manager asks for yesterday's OEE at PLANT-01 and receives 78.2% against the 85% target, with breakdown time on EQ-001 flagged as the top loss to address. ## Quick Start Ask the agent to generate an OEE report for a specific date and plant, for example: calculate the OEE report for plant-01 on 2026-09-04 and show the top losses.

Frequently Asked Questions about production-oee

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I calculate OEE for a production shift?

Run the calculate subcommand with a shift ID and date, for example: production_oee.py calculate --shift morning --date 2026-01-15. OEE is computed as Availability × Performance × Quality using run time, ideal cycle time, and good count data.

How to identify top OEE loss categories in manufacturing?

Use the top-losses subcommand with a date and optional limit. It ranks the five standard loss categories (breakdown, setup, idling, speed loss, defects) with Pareto analysis showing minutes lost and percentage of total.

What data sources does OEE calculation support?

The OEE_DATA_SOURCE environment variable selects the adapter: csv, api, or database. Data files are read from OEE_DATA_PATH, and shift boundaries come from a YAML shift calendar defined in OEE_SHIFT_CALENDAR.

Why is my OEE result misleading or inaccurate?

Common causes are stale ideal cycle times, miscategorized downtime events, and partial shift data. Review ideal cycle times quarterly, use a 5-minute grace period at shift boundaries, and only run calculations on complete shifts.

When should I not use OEE reporting?

Do not use it for detailed downtime event logging (use maintenance-downtime) or quality defect tracking (use quality-ncr). Also avoid running it on partial shifts where machines are still running, as results will be incomplete.