12.4 Managing Detailed Schedules and Scheduling Materials

Creating a schedule is only half of Domain VII. Managing the detailed schedule—and the materials that feed it—determines whether promised dates survive contact with the floor. This section breaks manufacturing lead time into components, covers staging discipline, and connects bottleneck awareness to Theory of Constraints (TOC) thinking that CPIM expects you to recognize.

Lead-Time Components: Where Time Really Goes

For a manufacturing order, manufacturing lead time is commonly decomposed as:

In many job shops, queue is 80% or more of lead time. That is why infinite loading and uncontrolled release destroy due-date performance even when setup and run standards are accurate. Expeditors who “watch the run” while ignoring queue are optimizing the visible minority of time.

Example: An order needs 2 hours setup + 6 hours run at Cell A, then 1 hour move, then 1 hour setup + 3 hours run at Cell B. Planned interoperation queue allowances are 16 hours before A and 24 hours before B, plus 4 hours wait after A for batch move. Total lead time ≈ 2+6+1+1+3+16+24+4 = 57 hours, of which only 13 hours are setup/run. Cutting run 10% saves 0.9 hours; cutting queue 25% saves 10 hours. Schedule management prioritizes the big rocks.

Managing the Schedule Horizon

Effective schedule management uses time fences:

• Frozen or firm zone (near term) — Limit changes; protect setups already prepared and materials already staged
• Slushy zone — Allow constrained rescheduling when demand or supply shifts
• Free zone — Planning can reshuffle with less disruption cost

Constant churn in the frozen zone creates schedule nervousness: materials are restaged, setups are torn down, and trust in the dispatch list collapses. PAC should require a reason code for hot-list overrides and measure expedite volume as a process failure metric, not a hero metric.

Status feedback closes the loop: percent of operations starting on time, queue hours versus plan, setup variance, and scrap. Without feedback, the detailed schedule becomes wallpaper.

Scheduling Materials: Staging and Kitting

Material staging means positioning the right components, fixtures, and documents at the point of use before the operation’s planned start. Kitting gathers order-specific components into a kit aligned to the shop packet. Scheduling materials is not a separate “warehouse hobby”—it is part of making the detailed schedule feasible.

Practices that support the schedule:

• Peg kits to operation start dates, not merely to order release dates
• Use pick waves timed to the dispatch list so early picks do not clog floor space
• Verify short components before releasing the order into a bottleneck queue
• Separate staging locations for the constraint resource so the bottleneck never waits on a missing washer
• Synchronize outside processing returns with the next internal operation’s start

When materials arrive late to a staged location, the schedule shows green while the resource sits idle. I/O control may still show “output below plan,” but the root cause is supply staging, not operator pace. Domain VII vignettes love that misdiagnosis.

Bottleneck Management and TOC Awareness

A bottleneck (constraint) is a resource whose capacity is less than or equal to demand placed on it, limiting system throughput. Theory of Constraints teaches a simple chain:

1. Identify the constraint
2. Exploit it — never waste constraint time on poor quality, late materials, or unnecessary setups
3. Subordinate everything else — non-constraints work to feed the constraint, not to maximize their own utilization
4. Elevate the constraint — add capacity only after exploitation and subordination
5. Repeat — prevent inertia from creating a new unmanaged constraint

Schedule implications:

• Sequence and material staging favor keeping the bottleneck busy on high-priority mix
• Buffers (time or stock) protect the constraint from upstream variation
• Activating non-bottlenecks to 100% utilization often increases WIP and queue without raising shipped throughput
• Drum-buffer-rope style thinking: the constraint drums the pace; a buffer protects it; the rope limits release

You do not need full TOC software vocabulary for CPIM, but you must recognize that schedule “efficiency” at a non-constraint can be harmful, and that protective control belongs at the constraint.

Integrating Lead Time, Materials, and Constraints

A weekly management routine might look like this:

1. Review constraint I/O and buffer status first
2. Confirm kits for constraint operations over the next frozen horizon
3. Recalculate priorities only outside the freeze unless a true customer or quality break occurs
4. Attack queue drivers (over-release, giant batches, unstable quality) rather than only overtime on run time
5. Audit move/wait policies that batch “for convenience” and inflate lead time

Exam-Ready Synthesis

If a question says jobs are late though run times meet standard, inspect queue and wait. If a cell is idle waiting for parts, inspect staging and release rules. If painting is 100% utilized and assembly still misses shipments because painted parts are late, painting may be the constraint—subordinate assembly schedules and material handlers to painting’s drumbeat. Managing detailed schedules is systems control: time components, materials, and bottlenecks must be managed together or the paper schedule lies.