Finite Scheduling Runbook (Short-Term)

Purpose & Scope

This runbook describes a repeatable short-term finite scheduling process for a two-week horizon. It helps planners and production teams create executable schedules that match true capacity, protect bottlenecks, and reduce last-minute firefighting. Use this when making day-to-day release and sequencing decisions, responding to capacity disruptions, or piloting finite scheduling before MES/ERP automation.

When to use

• Creating or validating a two-week capacity-aware production plan.
• Running a pilot to shift from infinite/planned orders to finite, executable schedules.
• Coordinating release rules, sequencing, and escalation across shifts and departments.

Definitions

• Finite schedule: A schedule that respects known, limited capacity (shift hours, machine time, operator availability) rather than assuming unlimited resources.
• Bottleneck/resource constraint: The workstation, machine, or process step that limits throughput for a product family.
• Adherence: Percentage of scheduled start/finish times and quantities executed as planned.
• Protective capacity: Reserved capacity at the constraint to absorb variability and urgent orders.

Runbook Overview

The runbook contains these sections: input checklist, capacity model building, sequencing rules, exception handling, change protocols, communication templates, and a two-week validation experiment.

1) Input checklist (required before creating the schedule)

• Confirmed customer due dates and ship dates (with priority/expedite flags).
• Order list: order ID, part, quantity, routing, and operation-level processing times (standard cycle times and changeover times).
• Inventory on-hand and allocation rules (raw material, WIP, finished goods).
• Resource availability: planned shift hours, planned absences, operator qualifications, and planned maintenance/PM windows.
• Machine constraints and capacity rates (ideal minutes/hour and realistic throughput factors such as OEE).
• Known quality holds, tooling restrictions, and fixture availability.
• Setups and family groupings (which parts can be grouped to reduce changeovers).
• ERP/MRP release status — which orders are released and which are not.
• Business priorities or contractual SLAs that override normal rules.

2) Build the short-horizon capacity model

Goal: produce a realistic, time-bucketed view of available capacity for the two-week horizon.

1. Choose time granularity: shifts (recommended) or days for two-week horizon.
2. Calculate gross available minutes per resource per time bucket: (shift length in minutes) × (number of operators/machines available).
3. Apply realistic utilization & uptime (use recent rolling OEE or an agreed factor). Example: expected productive minutes = gross minutes × 0.85 to reflect breaks, minor stops, and utility time.
4. Subtract committed maintenance/PM windows and planned downtime explicitly.
5. Reserve protective capacity at the primary bottleneck (e.g., 5–15% of available minutes) to absorb variability—adjust based on variability and service requirements.
6. Map each order’s operation times into the model using routing operation times and setup durations. For family setups, include grouping savings when applicable.
7. Identify overloads and slack by bucket; flag any bucket where required time > available time.

3) Sequencing rules (practical heuristics to create an executable sequence)

Use a rule-set rather than only one rule. Define precedence and override conditions.

Base rule set (apply in order, with documented exceptions)

1. Protect the bottleneck: sequence to keep constraint utilized, avoid starving or blocking the constraint. Maintain the protective capacity buffer.
2. Due-date adherence (EDD/CR): use earliest due date (EDD) or Critical Ratio (time remaining / work remaining) for finished goods that affect delivery commitments.
3. Family/setup grouping: where setups are costly, group like families to minimize total changeover time, but do not violate critical bottleneck protection or urgent due dates.
4. Lot-splitting: allow limited splitting to fit remaining capacity but minimize splits that increase handling/WIP unless it improves on-time delivery.
5. Expedites: defined expedite rules (who can declare, costs, and maximum daily expedite count). Expedites override other rules and require an expedite ticket.
6. FIFO at feeder steps: maintain FIFO or first-come sequencing at non-bottleneck feeder steps unless business priority overrides it.

Sequencing examples

Example: If a bottleneck has two candidate jobs, select the one with the earlier due date unless grouping similar setups would reduce downstream changeover cost and not cause late deliveries.

4) Exception handling & escalation

Define detection, immediate actions, and escalation paths.

Common triggers

• Bucket overload detected during modeling.
• Machine breakdown or unplanned downtime affecting the constraint.
• Material shortage or quality hold preventing scheduled work.
• Customer expedite or new high-priority order.
• Schedule adherence drops below threshold (see metrics).

Immediate actions

1. Pause automatic releases to non-critical work if needed to protect the constraint.
2. Re-evaluate the two-week plan focusing on the constraint: can work be moved or swapped to other resources or future buckets?
3. Trigger cross-functional huddle (production planner, supervisor, maintenance, materials).

Escalation matrix (example)

1. Shop floor team solves within shift (tactical fixes, small sequencing adjustments).
2. Supervisor/Planner if impacts across multiple shifts or multiple orders are affected.
3. Operations manager when customer delivery promises are at risk or capacity shortfall > X hours.
4. Supply chain/Commercial for customer notifications and remediation.

5) Change & release protocols

Control who can change the finite schedule, how, and with what documentation.

• Authorized changers: planner and production supervisor can make non-expedite changes within defined limits. Operations manager signs off on major reworks.
• Change request form (minimum fields): requestor, order ID, reason, requested change, impacted resources, required by when, approvals required, timestamp.
• Lead time policy: normal changes must be requested at least one shift ahead unless marked emergency.
• Emergency expedites: must use expedite ticketing, record cost/time impact, and be reviewed in daily huddle.
• Lock-down windows: sections of the schedule may be locked within 4–8 hours of execution to maintain shop stability (define per site).

6) Communication templates

Use simple, repeatable messages so every stakeholder knows the state of the schedule.

Production: Start-of-Shift (sample)

Subject: Start-of-Shift Schedule — Line A — [date/shift]
Body: Planned jobs for shift: [Job IDs, quantities, start times]. Constraint protection: [resource and reserved minutes]. Known issues: [downtime, material]. Contact: [supervisor].

Schedule Change Notification (sample)

Subject: Schedule Change — [Job ID] — [date]
Body: Change requested by [name]. Old plan: [details]. New plan: [details]. Reason: [reason]. Approvals: [names]. Action required: [teams].

Expedite Alert (sample)

Subject: EXPEDITE — [Job ID] — Immediate Action Required
Body: Customer/Commercial flagged order as expedite. Requested completion [date/time]. Impact to other orders: [estimated]. Expedited by: [name].

7) Two-week validation experiment (pilot)

Run a structured two-week pilot to test the runbook and measure benefits. Keep scope small (one product family or one bottleneck area) for the first pilot.

Objectives

• Verify schedule adherence and feasibility using realistic capacity modeling.
• Reduce day-to-day firefighting (measured by number of unscheduled changes per day).
• Establish reliable communication and escalation practices.

Key metrics & acceptance criteria

• Schedule adherence > 80% (start/finish within agreed window) by week two.
• Number of unscheduled changes per day reduced by 30% vs baseline.
• WIP at constraint reduced or stabilized by 10% (or fewer touching events).
• On-time delivery to customer commitments improved or maintained.

Data collection & cadence

1. Daily: production start-of-shift report, actual start/finish times, reasons for deviations (short form).
2. Daily huddle: planner, supervisor, maintenance, materials (15 minutes) to review exceptions and corrective actions.
3. Weekly: review metrics, root causes for missed schedules, and adjust sequencing rules or buffers.
4. End of pilot: formal review with stakeholders, lessons learned, and next steps (scale, tweak, or integrate with MES).

Simple adherence capture form (use a one-line entry per job each shift)

Fields: Job ID, Scheduled start, Actual start, Scheduled finish, Actual finish, Deviation reason code (machine, material, manpower, quality, other), Corrective action.

8) Practical tips & common pitfalls

• Start small: pilot one line or product family and refine rules before scaling.
• Don’t over-automate rules early—focus on predictable heuristics and clear communication.
• Measure variability drivers (setup variation, material shortages) and attack those root causes in parallel.
• Preserve limited protective capacity at the constraint—removing buffers too quickly invites firefighting.
• Keep change control strict during execution windows to maintain trust in the schedule.

9) Next steps & evolution

After a successful pilot, codify the sequencing rules into the ERP/MES or an automated scheduling tool. Consider integrating real-time shop-floor data (OEE, downtime events, material issues) and using the runbook as the human governance layer around automation. Package the runbook into a local team toolkit (checklists, forms, templates) and train planners and supervisors.