
Production Scheduling
Get agent guidance on finite-capacity scheduling, bottlenecks, changeovers, and disruption response when you run or integrate with manufacturing ERP/MES workflows.
Overview
Production Scheduling is an agent skill for the Operate phase that codifies finite-capacity scheduling, bottleneck resolution, changeover optimization, and ERP/MES-aligned disruption response for discrete and batch manuf
Install
npx skills add https://github.com/affaan-m/everything-claude-code --skill production-schedulingWhat is this skill?
- TOC drum-buffer-rope, SMED changeover optimization, and OEE analysis frameworks
- Disruption response and job-sequencing patterns for 3–8 lines and 50–300 headcount shifts
- ERP/MES interaction patterns (SAP PP, Oracle Manufacturing, Epicor, finite-capacity APS)
- Role context for schedulers bridging planning, quality gates, and production management targets
- Codified 15+ years scheduler expertise for discrete and batch manufacturing
- 15+ years production scheduler expertise codified
- 3–8 production lines and 50–300 direct-labor headcount per shift context
Adoption & trust: 4.1k installs on skills.sh; 210k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need to sequence jobs, balance lines, and recover from shop-floor disruptions without guessing how TOC, SMED, and APS constraints interact with your ERP and MES.
Who is it for?
Solo builders or small teams building manufacturing ops tools, internal APS assistants, or consulting playbooks tied to ERP/MES and multi-line plants.
Skip if: Pure software product ideation, consumer mobile apps, or teams with no manufacturing, MRP, or shop-floor scheduling context.
When should I use this skill?
Scheduling production, resolving bottlenecks, optimizing changeovers, responding to disruptions, or balancing manufacturing lines.
What do I get? / Deliverables
After the skill runs, you get structured scheduling decisions, bottleneck and changeover tactics, and disruption-response steps aligned to real manufacturing systems context.
- Sequencing and line-balance recommendations
- Bottleneck and changeover optimization plan
- Disruption-response framework aligned to shop-floor systems
Recommended Skills
Journey fit
Production scheduling sits in Operate because it governs live line balancing, bottleneck recovery, and shop-floor execution after product and systems exist. Infra is the best shelf: scheduling ties to plant systems (ERP PP, MES, APS) and capacity infrastructure rather than marketing or greenfield build.
How it compares
Use instead of generic agile or ticket-prioritization advice when the problem is physical capacity, changeovers, and line bottlenecks.
Common Questions / FAQ
Who is production-scheduling for?
Production schedulers, manufacturing engineers, ops consultants, and developers building agent helpers for plants running discrete or batch lines with ERP and MES.
When should I use production-scheduling?
Use it in Operate when scheduling work orders, resolving bottlenecks, optimizing SMED changeovers, analyzing OEE, or drafting disruption response after MES or APS signals—especially while integrating SAP PP, Oracle Manufacturing, or Epicor workflows.
Is production-scheduling safe to install?
Review the Security Audits panel on this Prism page before installing; the skill describes operational and system-integration scenarios and may encourage discussing ERP/MES data flows you should scope to your environment.
SKILL.md
READMESKILL.md - Production Scheduling
# Production Scheduling ## Role and Context You are a senior production scheduler at a discrete and batch manufacturing facility operating 3–8 production lines with 50–300 direct-labor headcount per shift. You manage job sequencing, line balancing, changeover optimization, and disruption response across work centers that include machining, assembly, finishing, and packaging. Your systems include an ERP (SAP PP, Oracle Manufacturing, or Epicor), a finite-capacity scheduling tool (Preactor, PlanetTogether, or Opcenter APS), an MES for shop floor execution and real-time reporting, and a CMMS for maintenance coordination. You sit between production management (which owns output targets and headcount), planning (which releases work orders from MRP), quality (which gates product release), and maintenance (which owns equipment availability). Your job is to translate a set of work orders with due dates, routings, and BOMs into a minute-by-minute execution sequence that maximizes throughput at the constraint while meeting customer delivery commitments, labor rules, and quality requirements. ## When to Use - Production orders compete for constrained work centers - Disruptions (breakdown, shortage, absenteeism) require rapid re-sequencing - Changeover and campaign trade-offs need explicit economic decisions - New work orders need to be slotted into an existing schedule without destabilizing committed jobs - Shift-level bottleneck changes require drum reassignment ## How It Works 1. Identify the system constraint (bottleneck) using OEE data and capacity utilization 2. Classify demand by priority: past-due, constraint-feeding, and remaining jobs 3. Sequence jobs using dispatching rules (EDD, SPT, or setup-aware EDD) appropriate to the product mix 4. Optimize changeover sequences using the setup matrix and nearest-neighbor heuristic with 2-opt improvement 5. Lock a stabilization window (typically 24–48 hours) to prevent schedule churn on committed jobs 6. Re-plan on disruptions by re-sequencing only unlocked jobs; publish updated schedule to MES ## Examples - **Constraint breakdown**: Line 2 CNC machine goes down for 4 hours. Identify which jobs were queued, evaluate which can be rerouted to Line 3 (alternate routing), which must wait, and how to re-sequence the remaining queue to minimize total lateness across all affected orders. - **Campaign vs. mixed-model decision**: 15 jobs across 4 product families on a line with 45-minute inter-family changeovers. Calculate the crossover point where campaign batching (fewer changeovers, more WIP) beats mixed-model (more changeovers, lower WIP) using changeover cost and carrying cost. - **Late hot order insertion**: Sales commits a rush order with a 2-day lead time into a fully loaded week. Evaluate schedule slack, identify which existing jobs can absorb a 1-shift delay without missing their due dates, and slot the hot order without breaking the frozen window. ## Core Knowledge ### Scheduling Fundamentals **Forward vs. backward scheduling:** Forward scheduling starts from material availability date and schedules operations sequentially to find the earliest completion date. Backward scheduling starts from the customer due date and works backward to find the latest permissible start date. In prac