Study guide

12.2 Scheduling and PAC Methods

APICS CPIM Certified in Planning and Inventory Management Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 Current Exam Facts 1.2 ECM 9.0 Domains and Weights 1.3 How to Study for CPIM

2 Supply Chain Strategy Foundations

2.1 Supply Chains, the Environment, and Strategy 2.2 Environment Analysis and Strategic Scope 2.3 Developing and Managing Organizational Strategy 2.4 Competitive Analysis: Five Forces, Benchmarking, and Value Chain

3 Strategy Performance and Operations Choices

3.1 Performance Monitoring and KPIs 3.2 Functional and Operational Strategies 3.3 Environments, Types, and Layouts 3.4 Service Process Design and Product-Process Trade-offs

4 Sales and Operations Planning

4.1 S&OP Purpose and Process 4.2 Aggregate Demand and Supply Plans 4.3 Reconciling S&OP Plans 4.4 Portfolio, New Product Introduction, and Life-Cycle Planning in S&OP 4.5 Strategic Buffers, Bottlenecks, and Capacity-Constrained Resources

5 Plan and Manage Demand

5.1 Demand Management 5.2 Sources of Demand and Forecasting 5.3 Forecast Performance 5.4 Marketing, Promotions, and Product Management 5.5 Qualitative, Associative, and AI-Driven Forecasting

6 Master Scheduling

6.1 Creating the Master Schedule 6.2 Rough-Cut Capacity Planning and MPS Validation 6.3 Using and Maintaining the Master Schedule 6.4 Planning Bills and Two-Level Master Scheduling 6.5 NPI, DFMA, Prototype, and End-of-Life Schedules

7 MRP, CRP, and Supply Disruptions

7.1 Material Requirements Planning 7.2 CRP, Order Promising, and Final Assembly Scheduling 7.3 Changes and Supply Disruptions 7.4 Product Costing and Variance Analysis for Planners

8 External Supply Sources

8.1 Suppliers and Procurement 8.2 Purchasing and Maintenance 8.3 Supply Chain Risk Management 8.4 Sourcing Footprint and Supplier Relationship Types 8.5 Supplier Release Mechanics and Inbound Logistics

9 Sustainability and Reverse Logistics

9.1 Sustainability Strategies 9.2 Waste Hierarchy and Reverse Logistics 9.3 Sustainability Standards, Reporting, and Life-Cycle Assessment

10 Inventory Planning and Costs

10.1 Inventory Planning 10.2 Inventory Costs, Accounting, Costing, and Metrics 10.3 EOQ, Reorder Point, and Safety Stock

11 Inventory Management and Control

11.1 Inventory Management Policies 11.2 Inventory Control 11.3 Service Levels and Inventory Tradeoffs 11.4 MRO Inventory and Maintenance Planning Inputs 11.5 Traceability Standards and Off-Site Inventory

12 Detailed Schedules and PAC

12.1 Planning Detailed Schedules 12.2 Scheduling and PAC Methods 12.3 Creating Production and Service Schedules 12.4 Managing Detailed Schedules and Scheduling Materials 12.5 Sequencing Rules, Lot Splitting, and Overlapped Scheduling 12.6 Capacity Types, Safety Capacity, and Labor Scheduling 12.7 Process Batches, Transfer Batches, and Backflushing

13 Plan and Manage Distribution

13.1 Planning Distribution 13.2 Replenishment and DRP 13.3 Order Management, Trace/Track, and KPIs

14 Quality and Business Investments

14.1 Quality Systems and Tools 14.2 Capital Equipment and Facilities 14.3 Technology in Planning and Inventory 14.4 The Seven Basic and Seven New Quality Tools 14.5 SPC Charts and Variation Types 14.6 Systems Requirements, Master Data, and Emerging Technologies

15 Continuous Improvement

15.1 Continuous Improvement Overview 15.2 Lean, JIT, and the Seven Wastes 15.3 Six Sigma, Kaizen, and Root Cause Tools 15.4 TPM, SMED, Standardized Work, and Visual Management

16 Integration and Exam Readiness

16.1 Planning Hierarchy Integration 16.2 High-Yield Calculations Drill 16.3 Exam Day, Scoring, and Credential Maintenance

12.2 Scheduling and PAC Methods

Key Takeaways Explain This Topic AI

Production Activity Control (PAC) executes, monitors, and adjusts the detailed schedule at the shop or service floor

Push systems release work based on plans and schedules; pull systems authorize work based on downstream consumption signals

Input/output control compares planned versus actual hours into and out of a work center to manage queues and lead time

Dispatching is the short-interval ranking of which job to run next on a resource according to rules and constraints

  • Effective PAC links release, priority, feedback, and corrective action—not paperwork alone
  • Last updated: July 2026

Production Activity Control (PAC) is the execution layer of manufacturing planning and control. After detailed schedules exist, PAC releases orders to the floor, sequences work at resources, tracks progress, and triggers corrective action when actual performance diverges from plan. On CPIM, PAC is not a software brand—it is a management system: authorize work, prioritize work, measure work, and close the loop.

The PAC Loop

A practical PAC cycle has four linked activities:

Order release — Convert planned or firm planned orders into shop packets (or electronic travelers) when materials, tools, and capacity are ready enough to start.

Dispatching — At each work center, decide the next job from the queue using priority rules and constraints.

Data collection and feedback — Capture completions, scrap, labor hours, and delays so status is visible.

Corrective action — Expedite, split, reschedule, add overtime, or stop releasing more work into a choked resource.

If release is undisciplined, queues explode. If dispatching is arbitrary, due dates slip even when capacity exists. If feedback is late, corrective action arrives after the customer already knows. Domain VII items often hide the failure in one of these four links.

Push Versus Pull

Push systems authorize production based on an upstream plan or schedule. MRP-generated planned orders, shop packets released on a weekly schedule, and forecast-driven batch launches are classic push. Push is powerful when lead times are long, product variety is high, and you must coordinate many components. The weakness is that push can flood the floor if the plan is wrong or release ignores current WIP.

Pull systems authorize production based on downstream consumption. Kanban cards, CONWIP (constant work-in-process) limits, and supermarket replenishment are pull mechanisms. Pull limits WIP and makes overproduction harder, which shortens queue time and exposes problems. Pull works best with relatively stable mix, reliable processes, and quick changeovers. Many plants hybridize: MRP plans materials (push planning), while final assembly or a bottleneck cell runs on pull signals.

  • Dimension Push Pull
  • Authorization trigger Plan/schedule Downstream use or empty buffer
  • WIP behavior Can grow with plan error Intentionally capped
  • Strength Coordinates complex BOMs and long leads Controls congestion and overproduction
  • Risk Over-release and long queues Starvation if signals or buffers poorly sized
  • Typical tools MRP release, firm shop orders Kanban, supermarket, CONWIP

Exam tip: “We release everything MRP says on Monday” is push. “We machine the next lot only when the assembly kanban is empty” is pull. Neither word alone proves lean maturity—execution discipline does.

Input/Output Control

Input/output (I/O) control is a PAC technique that manages work-center queues by comparing planned and actual input hours (work arriving) and output hours (work completed) over a period—often a week. The cumulative difference between input and output changes the queue (backlog) at the center.

Key relationships:

If input persistently exceeds output, the queue grows and lead time lengthens.

If output exceeds input, the queue shrinks—good if intentional, dangerous if it starves the next process.

Planned input should be gated by demonstrated output capacity, not wishful release.

A simple weekly I/O report for a grinding cell might show planned input 160 hours, actual input 190, planned output 160, actual output 150. Queue grew by 40 hours. PAC response is not only “work overtime”—it is also to throttle input (delay releasing more grind jobs) until output catches up. I/O control is how finite thinking survives on a floor that still receives MRP pushes.

  • Week Planned input Actual input Planned output Actual output Queue change
  • 1 160 155 160 158 −3
  • 2 160 185 160 150 +35
  • 3 140 130 170 165 −35

In week 2, overload arrived as excess input and weak output. In week 3, PAC cut planned input and raised planned output (overtime or extra shift), recovering queue. That storyline is classic Domain VII reasoning.

Dispatching

Dispatching is the short-horizon decision of which queued job a resource runs next. The dispatcher (human or system) uses a dispatch list ranked by priority rule, due date, setup family, or management override. Dispatching does not replace the detailed schedule; it executes and fine-tunes it under real-time conditions—machine down, operator absent, hot customer call.

Good dispatching practices:

  • Keep the dispatch horizon short (today / this shift) so priorities stay current
  • Respect routing sequence and material readiness before priority cosmetics
  • Limit expedite overrides; every hot job creates a cold job somewhere else
  • Align dispatch rules with the firm’s order winners (speed, due-date reliability, or changeover efficiency)

Poor dispatching looks like tribal knowledge: “Run whatever the supervisor shouts.” CPIM expects a rule-based approach connected to performance measures such as tardiness, flow time, and setup hours.

Connecting PAC Methods in One Flow

Consider a stamping plant. MRP (push planning) creates weekly requirements. PAC releases only what I/O control says the press line can absorb. At the press, dispatching sequences dies by setup family within due-date urgency. Downstream welding pulls stamped blanks from a supermarket. When actual press output falls, I/O control cuts further release, and planners reschedule rather than silently growing queues. That hybrid—push planning, gated release, pull between stages, rule-based dispatch—is the mature PAC picture Domain VII points toward.

  • Common Exam Failure Modes
  • Treating PAC as “printing travelers” with no feedback loop
  • Calling a system pull when kanban cards are ignored and supervisors still push batches
  • Using I/O reports for blame instead of release control
  • Dispatching by whoever complains loudest, destroying schedule integrity

Master the vocabulary, then apply it to vignettes: identify whether authorization is push or pull, whether queues are managed by I/O control, and whether dispatching follows an explicit rule. That triad is the heart of scheduling and PAC methods.