Master Production Scheduling

Chapter 15
Emerging Models and Future of Master Scheduling

Post Graduate Program in Production Management
Master Production Scheduling   •   Post Graduate

Emerging Models and Future of Master Scheduling

Introduction

Master production scheduling (MPS) has traditionally translated aggregate production plans into time-phased commitments for specific end items, usually over a rolling horizon. Its central questions have been: what should be produced, when, and in what quantity? Contemporary production systems make these questions substantially more difficult. Demand is volatile, products are configurable, supply networks are geographically dispersed, sustainability constraints are increasingly material, and customers may purchase outcomes rather than physical products.

Industry 4.0 technologies, cloud platforms, artificial intelligence (AI), additive manufacturing, digital twins and connected equipment do not eliminate the need for master scheduling. They change its operating logic. The scheduler increasingly becomes the designer and governor of a decision system that combines human judgement, algorithms, real-time data and explicit business rules.

This chapter critically evaluates emerging models of master scheduling. It examines autonomous planning, real-time replanning, additive manufacturing, servitization, circular production, carbon-aware scheduling and resilient supply networks. The emphasis is not technological enthusiasm but managerial usefulness: what these models can achieve, what assumptions they require, and how organisations can implement them responsibly.

Learning objectives

After studying this chapter, the learner should be able to:

  1. Explain how Industry 4.0 changes the role, data architecture and cadence of master scheduling.
  2. Distinguish decision support, semi-autonomous and autonomous planning.
  3. Evaluate real-time replanning without creating schedule instability.
  4. Analyse scheduling implications of additive manufacturing, servitization and circular production.
  5. Incorporate carbon, resilience and service considerations into scheduling decisions.
  6. Critically assess AI governance, cybersecurity, data quality and human accountability.
  7. Construct an implementation roadmap and performance framework for an emerging scheduling system.

1. From periodic MPS to the adaptive production system

A conventional MPS is often generated weekly or monthly using forecasts, customer orders, inventory records, bills of material, capacity information and planning policies. Its output feeds material requirements planning, purchasing, shop-floor control and distribution planning. The model is useful because it creates coordination and protects operations from constant change.

However, a fixed schedule can become obsolete between planning cycles. A machine breakdown, a supplier delay, a quality hold, a sudden order, or a change in energy availability may invalidate the original assumptions. The emerging model is therefore an adaptive production system with three linked layers:

  • Strategic and tactical layer: product–market choices, capacity, postponement, sourcing and sustainability policy.
  • Master scheduling layer: time-phased production commitments, order promising, inventory positioning and constraint reconciliation.
  • Execution layer: dispatching, sequencing, maintenance, quality and material movement.

A digital MPS connects these layers through event-driven data. It does not mean that every event should trigger a complete reschedule. A mature system distinguishes between events that require immediate action and events that should merely be recorded for the next planning cycle.

Important terminology

  • Rolling horizon: a planning window that moves forward as time passes.
  • Frozen zone: a near-term interval in which changes require special authorisation.
  • Slushy or flexible zone: a medium-term interval where limited changes are permitted.
  • Time fence: a rule governing the extent to which the schedule may be changed.
  • Digital twin: a dynamic digital representation of a physical asset, process or network, updated by operational data.
  • Event-driven planning: replanning initiated by a defined business or operational event rather than only by a calendar cycle.
  • Available-to-promise (ATP): uncommitted supply that can be promised against customer demand.
  • Capable-to-promise (CTP): a promise based on checking material, capacity and routing feasibility.

A useful conceptual objective is to balance service, cost, stability, sustainability and risk. One generic formulation is:

Minimise J = w₁C + w₂L + w₃I + w₄S + w₅E + w₆R

where C is production and changeover cost, L is lateness or service penalty, I is inventory cost, S is schedule-instability cost, E is environmental impact, R is risk exposure, and w₁…w₆ are managerial weights. The expression is a decision framework, not a universal law. The variables must be measured consistently or normalised before combining them; for example, monetary cost, hours, kilograms of CO₂ equivalent and risk scores cannot be added directly without scaling or valuation.

2. Industry 4.0 and the architecture of future MPS

Industry 4.0 refers to the integration of cyber-physical systems, industrial internet of things (IIoT), cloud or edge computing, analytics, automation and interoperable information systems. In master scheduling, its most important contribution is not automation alone but improved visibility of state.

A future-oriented architecture commonly contains:

  1. Data acquisition: sensors, machine controllers, warehouse systems, quality systems, customer orders and supplier feeds.
  2. Data and semantic layer: common identifiers, product structures, units of measure, timestamps, status codes and data governance.
  3. Planning and optimisation layer: MPS, finite-capacity scheduling, inventory logic, simulation, scenario analysis and AI models.
  4. Execution and feedback layer: manufacturing execution systems, operator interfaces, maintenance actions and logistics control.
  5. Governance layer: permissions, audit trails, cybersecurity, model monitoring and human approval.

The architecture creates several advantages. Actual cycle times can replace stale standards; predictive maintenance can inform capacity; quality data can prevent the release of suspect lots; and supplier updates can refine feasible promise dates. Yet connectivity also increases vulnerability. A wrong master-data conversion, duplicated order, sensor drift or cyberattack may propagate rapidly through the planning system.

Digital twins and scenario planning

A digital twin can be used to test alternatives before changing the live schedule. For example, the planner may compare: overtime versus subcontracting; postponement versus finished-goods production; or a low-carbon schedule versus the lowest-cost schedule. The twin is valuable only if its assumptions are transparent and its data are sufficiently current. A visually sophisticated twin that omits labour calendars, quality yield, tooling or changeover constraints is not a valid planning model.

3. Autonomous planning: capability and limits

Autonomous planning exists on a continuum:

LevelPlanning roleHuman responsibility
DescriptiveReports what happenedInterpret information
PredictiveEstimates demand, lead time or failureValidate forecasts and uncertainty
Prescriptive decision supportRecommends a scheduleApprove, modify and explain
Semi-autonomousExecutes within approved rulesGovern exceptions and thresholds
AutonomousActs without routine approvalSet policy, audit and intervene

An AI model may forecast demand, classify disruption severity, estimate remaining processing time or propose a sequence. Optimisation models may then select a plan subject to capacity and material constraints. These are different functions and should not be treated as interchangeable.

A planning recommendation should be evaluated by at least four criteria:

  • Feasibility: Does it respect material, capacity, labour, tooling, quality and regulatory constraints?
  • Robustness: Does a small forecast or processing-time error make it infeasible?
  • Explainability: Can a planner identify the main reason for the recommendation?
  • Value: Does it improve service, cost, resilience or sustainability relative to a credible baseline?

Autonomy is particularly appropriate for repetitive, high-volume and well-instrumented environments. It is less appropriate when products are novel, data are sparse, constraints are tacit, or the cost of an incorrect decision is extreme. Human expertise remains essential for exceptional demand, ethical trade-offs, industrial relations, customer negotiation and strategic changes.

Algorithmic risks

AI systems may inherit bias from historical schedules. If past plans systematically prioritised large customers, a learning system may reproduce that discrimination. A model trained during stable supply conditions may fail during a disruption. Reinforcement learning may discover operationally undesirable strategies if the reward function omits safety, employee welfare or contractual fairness. Consequently, autonomy requires model validation, drift monitoring, override rights, auditability and clear accountability.

4. Real-time replanning and schedule stability

Real-time replanning means updating decisions when new information arrives. It is not synonymous with continuously changing everything. Excessive nervousness creates expediting, setup losses, worker confusion, supplier penalties and loss of credibility.

A disciplined event policy classifies events according to impact and urgency. A critical machine failure affecting a customer shipment within the frozen zone may require immediate intervention. A small forecast revision for a distant week generally should not. Replanning policies should specify trigger thresholds, decision rights, data quality checks and communication requirements.

Schedule instability can be measured as the magnitude of change between successive published plans. One simple index is:

SI = (∑ₜ∑ᵢ |Qᵢₜ,new − Qᵢₜ,old|) ÷ (∑ₜ∑ᵢ Qᵢₜ,old)

Here Qᵢₜ is the planned quantity of item i in period t, and SI is dimensionless when the denominator is non-zero. The index captures quantity movement but not sequence, timing or customer criticality; organisations may therefore supplement it with date-change and priority-weighted measures.

A practical control system uses:

  • frozen, slushy and liquid time fences;
  • minimum run quantities and setup families;
  • pegging of material and customer orders;
  • exception-based rather than universal replanning;
  • robust buffers for uncertain processing and transport times;
  • explicit approval for changes affecting customers or regulated products.

The central trade-off is responsiveness versus stability. A schedule that never changes may be unrealistic; a schedule that changes continuously may be unusable. The correct balance depends on lead times, product variety, changeover economics and customer tolerance.

5. Additive manufacturing and the logic of postponement

Additive manufacturing (AM) produces parts layer by layer from a digital model. It can reduce tooling requirements, enable complex geometries, support mass customisation and make economically viable small batches. Its scheduling implications differ from those of conventional machining or assembly.

Important constraints include build volume, material compatibility, machine qualification, nesting of parts, print duration, thermal or curing cycles, post-processing, inspection and certification. The relevant MPS may schedule not only finished products but also digital work orders, build plates, powder or filament, post-processing capacity and inspection resources.

AM encourages postponement: generic or digital designs are held until demand is clearer, after which production and finishing are completed. This can reduce finished-goods inventory, but it may increase reliance on scarce printers and post-processing stations. The bottleneck may move from printing to heat treatment, surface finishing or certification.

A simplified batch decision illustrates the logic. If a build has fixed preparation cost F, variable cost v per part, and n parts, average cost per part is:

AC = F ÷ n + v

F must be expressed in the same currency as v × n, and n must represent usable, conforming parts rather than merely loaded positions. The formula is a special-case average-cost relationship; it excludes scrap, nesting interaction, post-processing and inventory cost. It shows why combining compatible orders can be attractive, but it does not prove that the largest possible batch is optimal.

AM also raises governance issues. Digital design files are intellectual property and may be altered maliciously. Safety-critical parts require traceability of powder or feedstock, machine parameters, operator qualifications and inspection results. Thus, the MPS must link production identity to quality and cybersecurity controls.

6. Servitization and outcome-based scheduling

Servitization occurs when manufacturers supplement or replace product sales with services, lifecycle contracts or outcomes. Examples include availability guarantees, pay-per-use equipment, predictive maintenance and performance-based contracts.

The scheduling object changes from “produce a unit” to “maintain a service level.” The master schedule may include installation, spare-part positioning, field technicians, refurbishment, remote monitoring and planned maintenance. Demand becomes partly endogenous: reliable equipment reduces emergency demand, while poor maintenance creates failures and urgent work.

For a service contract promising availability, a simple availability measure is:

A = MTBF ÷ (MTBF + MTTR)

MTBF is mean time between failures and MTTR is mean time to repair, both measured in consistent time units. This steady-state relationship assumes failures and repairs are represented adequately by their mean values and excludes planned downtime unless the definition is modified. It is useful for illustration but insufficient for contractual analysis when failure distributions, spares or technician travel are highly variable.

Servitization therefore requires integrated scheduling across production and service operations. A low-cost manufacturing plan may be poor if it creates unreliable equipment and expensive warranty work. Performance measures should include customer uptime, first-time fix rate, spare availability, lifecycle margin and environmental impact, not only factory utilisation.

7. Circular production and closed-loop MPS

Circular production seeks to retain product, component and material value through repair, reuse, remanufacture, refurbishment and recycling. It changes the material flow from a linear sequence into a network containing forward and reverse flows.

The MPS must cope with uncertain return timing, variable condition, inspection outcomes, disassembly effort, component identity and customer willingness to accept recovered products. Returned units cannot be treated as equivalent to predictable virgin material. A practical planning process includes:

  1. forecast return quantities and timing;
  2. inspect and classify returned items;
  3. estimate recoverable components and material yield;
  4. reserve disassembly, repair and testing capacity;
  5. decide whether to remanufacture, harvest parts, recycle or dispose;
  6. integrate recovered supply with new-material requirements.

Circularity may lower material consumption but increase lead-time variability and reverse logistics complexity. It can also conflict with high utilisation if recovery work is intermittent. Planners should use scenario ranges and quality grades rather than a single deterministic return forecast.

8. Carbon-aware scheduling

Carbon-aware scheduling incorporates emissions into production decisions. Emissions may arise from electricity, fuel, materials, transport, waste and subcontracting. The planner must define system boundaries and avoid double counting.

For electricity consumption, a simple period estimate is:

CO₂e = ∑ₜ Eₜ × EFₜ

Eₜ is electricity consumed in period t, usually in kWh, and EFₜ is the applicable emissions factor, such as kg CO₂e/kWh. The result is kg CO₂e. The factor may vary by time and location; using an average factor when marginal electricity is relevant can misrepresent the effect of shifting production.

A carbon-aware schedule may shift flexible loads toward periods with lower grid emissions, reduce idle warm-up, consolidate setups, select lower-carbon suppliers or avoid expedited transport. However, carbon reduction is not automatically beneficial if it causes excessive inventory, missed service, unsafe overtime or increased emissions elsewhere. A multi-objective analysis should include cost, customer service, capacity, resilience and emissions.

Carbon accounting also involves organisational boundaries and data quality. Scope classifications, supplier data, renewable-energy claims and recycled-content claims require documented methods. Carbon targets should be supported by auditable factors and not merely by estimated “green” scores in an optimisation dashboard.

9. Resilient supply networks and scheduling under disruption

Resilience is the ability to prepare for, absorb, adapt to and recover from disruption. It differs from efficiency: a highly efficient system may have low inventory and few suppliers but little capacity to absorb shocks.

Resilient MPS uses visibility, alternatives and recovery logic. Measures include strategic safety stock, dual sourcing, qualified substitutes, postponement, regional capacity, supplier collaboration and scenario playbooks. The correct choice depends on disruption probability, impact, recovery time and the economic value of continuity.

A basic expected-loss expression is:

EL = ∑ₖ pₖ × Lₖ

where pₖ is the probability of disruption scenario k and Lₖ is its loss, measured in a consistent unit such as monetary value. This is an expected-value calculation, not a prediction of the actual outcome. It can understate the importance of rare catastrophic events and should be supplemented by stress testing and risk appetite limits.

Resilient scheduling distinguishes three horizons:

  • Absorption: use inventory, alternate routes or capacity already available.
  • Adaptation: change products, suppliers, routings or customer priorities.
  • Recovery: restore normal flows and rebuild buffers without causing a second disruption.

Scenario planning is preferable to relying on one forecast. Scenarios may include a key supplier outage, port closure, cyber incident, demand surge or regulatory change. Each scenario should identify trigger indicators, feasible actions, decision owners and communication protocols.

10. Illustrative integrated case: NovaMed Devices

Background

NovaMed Devices is a fictional manufacturer of diagnostic equipment. It produces standard units, offers uptime contracts for hospitals, uses a certified additive process for selected replacement parts and has a target to reduce operational emissions. Components are sourced globally, while final assembly occurs at one regional plant.

Problem

The company’s weekly MPS is frequently revised. A supplier’s long lead time causes shortages, service technicians compete with production for scarce specialists, and urgent hospital orders generate costly air freight. Management proposes a fully autonomous AI scheduler.

Analysis

An initial audit identifies four root causes. First, the ERP contains duplicate item codes and inconsistent lead-time units. Second, service demand is not integrated with production demand. Third, the planner uses average capacity and ignores qualification constraints for additive builds. Fourth, the company measures utilisation and schedule adherence but not schedule instability, carbon or service availability.

A simulation of three policies is conducted:

PolicyMain characteristicsPrincipal risk
Current practiceWeekly manual plan, limited buffersSlow response and expediting
Aggressive autonomyEvent-driven full reschedulingSchedule nervousness and opaque decisions
Governed adaptive MPSTime fences, scenarios, human approval for exceptionsRequires data and governance investment

The third policy is selected. The company defines a 10-day frozen zone, a 20-day slushy zone and a liquid zone beyond 30 days. A supplier outage affecting less than one day of customer coverage is logged for the next cycle; an outage threatening critical hospital service triggers a controlled exception review.

Approach and solution

NovaMed first cleanses master data and establishes a common item, routing and resource dictionary. It then connects equipment status, service orders, supplier confirmations and energy-intensity data to a planning data store. A digital twin tests alternative schedules. The AI model forecasts service-part demand and predicts selected machine failures, but the optimisation engine must obey explicit constraints for certification, labour qualification and customer priority.

The schedule objective includes cost, lateness, carbon and instability. The weights are reviewed monthly by a cross-functional governance board rather than being hidden in code. Every automatic change generates an explanation: triggering event, affected orders, constraints, expected benefit and residual risk.

Outcome

In the first pilot area, the company reports fewer emergency changes, better visibility of service-part requirements and lower use of premium transport. The improvement is not attributed solely to AI. Data cleansing, time fences, cross-functional ownership and scenario discipline are equally important. The company postpones full autonomy because the additive process remains sensitive to certification and the historical disruption data are limited.

Learning points

  1. Technology cannot compensate for defective master data.
  2. Autonomous planning should begin with bounded decisions and clear escalation rules.
  3. Service obligations must be scheduled as capacity and availability commitments, not treated as incidental demand.
  4. Sustainability and resilience objectives must be measured alongside cost and utilisation.
  5. A pilot should compare performance with a credible baseline and monitor unintended consequences.

11. Implementation roadmap

A robust implementation can proceed in stages:

Stage 1: Define value and boundaries

Identify the business problem, planning scope, decision frequency, constraints, stakeholders and target outcomes. Specify whether the system is optimising factory cost, customer service, emissions, resilience or a documented combination.

Stage 2: Establish data and process foundations

Create ownership for item masters, bills of material, routings, calendars, yields, lead times and supplier data. Reconcile units, timestamps and status definitions. Map current decision processes, including informal workarounds that may contain valuable tacit knowledge.

Stage 3: Build visibility and baseline analytics

Develop dashboards for demand volatility, capacity loading, schedule instability, forecast error, supplier reliability, service availability, inventory, carbon and disruption exposure. Establish baseline performance before introducing automation.

Stage 4: Pilot decision support

Select a bounded product family or bottleneck. Test forecasting, finite-capacity checks, scenario analysis and exception alerts. Retain human approval and record overrides; overrides are learning evidence, not merely user non-compliance.

Stage 5: Introduce governed automation

Automate low-risk, repetitive decisions within thresholds. Use time fences, approval matrices, rollback procedures and audit trails. Validate models on out-of-sample periods and disruption scenarios.

Stage 6: Scale and continuously govern

Extend across plants, suppliers and service operations only when interfaces and definitions are stable. Monitor model drift, cybersecurity, bias, data completeness, constraint violations and business value. Retire models that no longer perform.

Performance scorecard

A balanced scorecard may contain:

  • service: on-time-in-full delivery, promise-date reliability and hospital or customer availability;
  • flow: throughput, lead time, inventory and bottleneck utilisation;
  • stability: schedule-instability index, number of emergency changes and frozen-zone violations;
  • sustainability: kg CO₂e per product, energy intensity, scrap and recovered-material share;
  • resilience: time to detect, time to recover, alternative-source coverage and scenario readiness;
  • governance: override rate, explanation completeness, access violations and data-quality defects.

No single metric should dominate. Maximising utilisation, for example, can increase queueing, lead time and vulnerability. Metrics must be interpreted as a system.

12. Critical issues: ethics, regulation and organisational change

Future scheduling systems make consequential decisions about customer priority, overtime, supplier allocation and resource access. Governance is therefore a management responsibility, not merely an IT concern.

Human accountability: A person or committee must own the policy and have authority to stop automated execution. “The algorithm decided” is not an adequate explanation for a missed safety requirement or unfair allocation.

Privacy and surveillance: Worker-level data may improve capacity estimation but can become intrusive. Data collection should be proportionate, transparent and consistent with employment law and organisational policy.

Cybersecurity: Connected assets, supplier interfaces and digital design files require identity management, segmentation, backups, patching, incident response and tested recovery procedures.

Safety and quality: No schedule benefit justifies bypassing validation, inspection, maintenance or competency requirements. Safety-critical constraints should be hard constraints, not soft penalties.

Change management: Planners may resist systems that appear to replace expertise. Participation, training, explanation quality and preservation of override rights are essential. The future planner is likely to spend less time entering quantities and more time designing policies, interpreting exceptions and negotiating trade-offs.

Contemporary direction and research agenda

Several developments are likely to shape master scheduling. Foundation models may improve interaction with planning data, but their outputs require structured validation because fluent language is not evidence of feasible scheduling. Federated analytics may allow supply-network learning without centralising sensitive data. Edge computing may support rapid local decisions when cloud connectivity is unreliable. Digital product passports may improve traceability for circular production. Carbon-aware optimisation will increasingly require location- and time-specific emissions data.

Research challenges remain substantial: modelling rare disruptions, integrating human judgement, validating AI under distribution shift, measuring circular-material quality, coordinating competing firms and designing fair multi-objective priorities. Scholarly and managerial progress will depend less on adding complexity than on testing whether new models improve outcomes under realistic uncertainty.

Chapter Summary

Master scheduling is evolving from a periodic translation of aggregate plans into an adaptive, connected and governed decision system. Industry 4.0 improves visibility and scenario capability but increases dependence on data quality and cybersecurity. Autonomous planning is best understood as a continuum, with bounded autonomy generally more appropriate than unrestricted automation. Real-time replanning must be controlled through event thresholds, time fences and stability measures.

Additive manufacturing changes batch, postponement, certification and post-processing decisions. Servitization requires scheduling lifecycle availability and service resources. Circular production introduces uncertain returns, inspection and reverse flows. Carbon-aware scheduling incorporates energy and emissions into trade-offs, while resilient scheduling prepares for disruption through alternatives, buffers and scenario playbooks.

Successful implementation begins with objectives, clean master data and process governance. Pilots, transparent models, human accountability, audit trails and balanced performance measures are essential. The future of MPS is therefore not “human versus machine”; it is the disciplined integration of computation, operational knowledge, sustainability and responsible managerial judgement.

Key Terms

Master production scheduling: A time-phased plan specifying what end items are to be produced and when.

Industry 4.0: Integration of connected cyber-physical technologies, data, automation and analytics in production.

Digital twin: A dynamic digital representation of a physical asset, process or network.

Rolling horizon: A planning window that advances as time passes.

Time fence: A rule limiting schedule changes in a defined period.

Autonomous planning: Planning in which software executes decisions within specified authority and rules.

Event-driven planning: Replanning initiated by defined operational or business events.

Schedule instability: The extent to which successive published plans differ.

Additive manufacturing: Layer-by-layer production from a digital design.

Postponement: Delaying final configuration or production until demand information improves.

Servitization: Offering services, lifecycle support or outcomes in addition to products.

Circular production: Production designed to retain product, component or material value through reuse and recovery.

Carbon-aware scheduling: Scheduling that explicitly considers emissions and energy conditions.

Resilience: The capability to prepare for, absorb, adapt to and recover from disruption.

Digital product passport: Structured information supporting product identity, composition, use and recovery.

Available-to-promise: Uncommitted supply that can be allocated to customer demand.

Capable-to-promise: A delivery commitment checked against material, capacity and routing feasibility.

Model drift: Decline in model validity as operating conditions or data relationships change.

Human-in-the-loop: A design in which people review, approve or override automated decisions.

Review Questions

Short Answer Questions

  1. What is the difference between a frozen zone and a liquid planning zone?
  2. Why does Industry 4.0 increase both visibility and operational risk?
  3. Define schedule instability and give one reason it matters.
  4. Identify two scheduling constraints specific to additive manufacturing.
  5. Why is human accountability necessary in autonomous planning?

Long Answer Questions

  1. Critically evaluate the benefits and limitations of autonomous master scheduling.
  2. Explain how servitization changes the scope and performance measures of an MPS.
  3. Discuss the planning implications of circular production and uncertain product returns.
  4. Compare efficiency-oriented and resilience-oriented supply-network scheduling.
  5. Propose an implementation roadmap for a carbon-aware MPS in a multi-plant manufacturer.

Analytical / Application Questions

  1. A factory is considering full real-time replanning after every machine status update. Design an event policy that preserves responsiveness without causing excessive schedule instability.
  2. A medical-equipment producer uses additive manufacturing for spare parts and promises high equipment availability. Develop an integrated schedule structure covering production, inspection, post-processing and field service.
  3. A plant can shift flexible electricity demand between two periods with different emissions factors. Explain the data, constraints and governance required before approving a carbon-aware shift, and identify circumstances in which the shift may be undesirable.

Multiple Choice Questions with Answers

Question 1

Which feature best distinguishes event-driven planning from a purely calendar-based MPS?

A. It eliminates the need for a planning horizon.

B. It initiates review when defined operational events occur.

C. It always reschedules every order immediately.

D. It uses no human approval.

Correct Answer: B. It initiates review when defined operational events occur.

Question 2

What is the principal purpose of a frozen zone?

A. To prohibit all production.

B. To ensure that near-term schedule changes are controlled.

C. To increase forecast error.

D. To remove capacity constraints.

Correct Answer: B. To ensure that near-term schedule changes are controlled.

Question 3

In autonomous planning, which criterion asks whether a recommendation respects material, capacity and routing constraints?

A. Explainability

B. Robustness

C. Feasibility

D. Autonomy

Correct Answer: C. Feasibility

Question 4

For additive manufacturing, why can combining compatible orders reduce average cost per part?

A. It removes all post-processing requirements.

B. It spreads fixed preparation cost over more usable parts.

C. It guarantees zero scrap.

D. It eliminates inspection.

Correct Answer: B. It spreads fixed preparation cost over more usable parts.

Question 5

Servitization most directly requires the MPS to include which additional concern?

A. Only finished-goods packaging.

B. Lifecycle service, spare parts and availability commitments.

C. Elimination of maintenance capacity.

D. Removal of customer priorities.

Correct Answer: B. Lifecycle service, spare parts and availability commitments.

Question 6

In the expression CO₂e = ∑ₜ Eₜ × EFₜ, what does EFₜ represent?

A. Finished inventory in period t

B. Energy failure in period t

C. The emissions factor applicable in period t

D. Expected forecast error in period t

Correct Answer: C. The emissions factor applicable in period t

Question 7

Which practice best supports resilient master scheduling?

A. Using one supplier for every critical component

B. Eliminating all inventory buffers

C. Developing qualified alternatives and disruption scenarios

D. Ignoring recovery time

Correct Answer: C. Developing qualified alternatives and disruption scenarios

Question 8

What is a major governance risk when AI learns only from historical schedules?

A. It cannot calculate quantities.

B. It may reproduce historical allocation bias.

C. It automatically improves data quality.

D. It makes cybersecurity unnecessary.

Correct Answer: B. It may reproduce historical allocation bias.

Question 9

A schedule changes substantially after every minor data update. What problem is most likely present?

A. Excessive schedule nervousness

B. Perfect robustness

C. Excessive postponement only

D. Zero event sensitivity

Correct Answer: A. Excessive schedule nervousness

Question 10

Which implementation action should generally precede large-scale autonomous scheduling?

A. Remove audit trails.

B. Clean and govern master data.

C. Disable human overrides.

D. Ignore baseline performance.

Correct Answer: B. Clean and govern master data.

Master Production Scheduling
Chapter 15 of 15