12. PPC for Projects and Complex Production Environments

Introduction and Context

Production planning and control (PPC) is most visible in repetitive manufacturing, where demand forecasts, standard routings, bills of material, and stable cycle times support relatively predictable schedules. Projects and complex production environments present a different managerial problem. A bridge, aircraft, power plant, customized machine, software-enabled production system, or engineered industrial installation may be produced only once or in very small quantities. Product specifications can change during execution, activities may be technologically dependent, resources may be shared across projects, and completion dates may carry contractual or strategic significance.

In such settings, PPC cannot be reduced to issuing work orders and comparing output with a daily schedule. It must integrate scope definition, design maturity, procurement, engineering, production, installation, commissioning, risk, cash flow, and stakeholder coordination. The central question changes from “How many units should be produced this period?” to “Which activities must be completed, in what sequence, with which resources and information, to deliver the required outcome by the required date?”

This chapter examines PPC for engineer-to-order (ETO), project, cellular, process, and mass-customization environments. It develops the use of PERT and CPM, critical-chain thinking, resource allocation, capacity and constraint management, and postponement. It also considers how digital systems and analytics can improve visibility without creating a false impression of precision.

Learning Objectives

After studying this chapter, students should be able to:

1. Distinguish the planning and control requirements of project, ETO, cellular, process, and mass-customization operations.

2. Construct and interpret activity networks using CPM and PERT.

3. Explain critical paths, float, resource constraints, feeding buffers, and project buffers.

4. Allocate scarce resources across competing activities and projects.

5. Apply postponement and modularization to reduce variety-related complexity.

6. Evaluate the managerial, technological, ethical, and governance issues associated with complex PPC.

7. Diagnose a project-control problem and recommend an integrated PPC response.

Why Complex Environments Require a Different PPC Logic

A conventional make-to-stock system benefits from repetition. Learning improves estimates, routings stabilize, inventory can decouple stages, and statistical control can be applied to recurring operations. Projects and ETO production have limited repetition. The product may be unique, the design may be incomplete when procurement begins, and the production route may evolve as technical knowledge develops.

Four characteristics are especially important. First, uncertainty exists in activity durations, design changes, approvals, supplier performance, and site conditions. Second, interdependence means that a delayed drawing, inspection, or component can prevent several downstream activities. Third, resource contention occurs when specialist engineers, welders, test facilities, cranes, or commissioning teams are required by several work packages simultaneously. Fourth, financial exposure is high: late delivery may trigger liquidated damages, while premature procurement may create obsolete or non-conforming inventory.

PPC in these environments therefore operates at several levels:

• Strategic level: selection of production technology, capacity, supply-network design, and project portfolio priorities.
• Tactical level: aggregate resource loading, subcontracting, capacity reservations, standardization, and procurement policy.
• Operational level: detailed scheduling, dispatching, progress measurement, issue escalation, and corrective action.

A useful principle is that the plan should become more detailed only as uncertainty is reduced. A fully detailed schedule prepared before design maturity may look sophisticated but will be repeatedly reworked. Conversely, an excessively broad plan provides no reliable basis for coordination. Effective PPC matches planning detail with available knowledge.

The Production Environments and Their Control Problems

Engineer-to-order and project production

In ETO production, the customer order initiates significant engineering activity, and the product is designed or configured for a specific requirement. Examples include industrial machinery, special-purpose vehicles, process equipment, and infrastructure systems. The master schedule must connect contract milestones to engineering releases, long-lead procurement, fabrication, assembly, testing, delivery, and installation.

The primary control problem is often not shop-floor speed but the synchronization of information and physical flow. Manufacturing cannot begin reliably until drawings, specifications, tolerances, and approved changes are available. Engineering change control is therefore part of PPC rather than an administrative activity separate from it.

Cellular manufacturing

Cellular manufacturing groups dissimilar machines and workers to process a family of similar products. Its usual advantages include shorter travel distances, reduced queueing, faster feedback, and clearer ownership. In complex environments, cells may be organized around product families or project modules rather than high-volume parts.

PPC must balance cell autonomy with system coordination. A cell that maximizes its own utilization may produce components before downstream requirements are confirmed, thereby increasing work-in-process. Local efficiency must not undermine the project’s critical flow. Takt-based coordination may be useful where demand is repetitive, but project cells often require finite-capacity scheduling and priority rules based on milestones and constraints.

Process industries

Process industries such as chemicals, food, cement, paper, and refining operate through continuous or batch transformation. Their constraints include campaign sequencing, cleaning and changeover losses, recipe compliance, tank and pipeline availability, material aging, yield variability, and environmental controls.

In process production, PPC must coordinate material balances, batch genealogy, quality release, and equipment availability. A schedule that is feasible in labor hours may be infeasible because a vessel, furnace, or validated line is unavailable. Product sequencing can reduce contamination and changeover costs, but it may conflict with due-date priorities. The planner must therefore optimize the total system rather than a single performance measure.

Mass customization

Mass customization seeks to offer variety while retaining much of the efficiency of repetitive production. It depends on modular product architecture, common platforms, postponement, configure-to-order processes, and reliable information systems. The challenge is to distinguish meaningful customer variety from unnecessary internal complexity.

PPC must manage option-dependent bills of material, common components, late configuration, and rapidly changing demand. Forecasting at the finished-product level may be unreliable because the number of combinations is large. Forecasting common modules and postponing final differentiation can make capacity and inventory planning more robust.

Project Networks: From Work Breakdown to Schedule Logic

Project planning begins with a work breakdown structure (WBS). The WBS decomposes the project scope into deliverables and work packages. A good work package has a defined output, responsible owner, acceptance criteria, estimated resources, and a basis for measuring progress. Decomposition should be sufficient for control but not so detailed that reporting becomes costly and activity relationships become artificial.

The WBS is not itself a schedule. Scheduling requires logical relationships among activities. A network may use finish-to-start relationships, in which one activity must finish before another begins; start-to-start relationships; finish-to-finish relationships; or controlled overlaps. For example, procurement of standard items may begin before design is fully complete, whereas fabrication of a safety-critical assembly may require an approved drawing.

The schedule should also identify milestones. A milestone has zero duration and represents an important event such as design approval, material receipt, factory acceptance test, shipment, or commissioning. Milestones are valuable for governance because senior stakeholders can understand them more readily than hundreds of detailed activities.

CPM and PERT: Logic, Calculation, and Interpretation

The Critical Path Method (CPM) assumes that activity durations can be estimated with reasonable confidence. For each activity, the planner calculates earliest start (ES), earliest finish (EF), latest start (LS), and latest finish (LF). In a simple finish-to-start network:

• EF = ES + activity duration
• ES of an activity = the largest EF among its immediate predecessors
• LS = LF − activity duration
• LF of an activity = the smallest LS among its immediate successors

Total float is calculated as LS − ES, or equivalently LF − EF. Activities with zero total float form at least one critical path. A delay to a critical activity will delay the project completion date unless corrective action changes the network, duration, or resource arrangement.

Consider the following simplified project:

| Activity | Description | Duration (weeks) | Predecessor |

|---|---|---:|---|

| A | Confirm requirements | 2 | — |

| B | Detailed design | 4 | A |

| C | Procure standard materials | 5 | A |

| D | Fabricate assembly | 6 | B, C |

| E | Test and approve | 2 | D |

| F | Install at customer site | 3 | E |

The paths are A-B-D-E-F = 17 weeks and A-C-D-E-F = 18 weeks. Thus, the procurement path is critical in this simplified network. Design has one week of apparent float, but that float can disappear if design resources are shared or if the activity has underestimated uncertainty. The example demonstrates why a planner must examine the network rather than focus only on the longest individual activity.

PERT is useful where activity duration is uncertain. It uses three estimates: optimistic time (a), most likely time (m), and pessimistic time (b). The expected duration is:

te = (a + 4m + b) / 6

A commonly used variance estimate is:

σ² = [(b − a) / 6]²

PERT encourages explicit discussion of uncertainty, although its statistical assumptions should not be treated as exact facts. Duration estimates may not be independent, and pessimistic values may be influenced by optimism bias. PERT results should therefore support managerial judgment rather than replace it.

CPM and PERT are often misused. A critical path is not necessarily the path containing the most difficult work; it is the path that currently determines the calculated completion date. Criticality can change when durations, logic, calendars, or resources change. A schedule should therefore be updated through disciplined change control and reviewed for emerging critical paths.

Resource-Constrained Scheduling and Critical-Chain Thinking

Traditional network analysis may assume that unlimited resources are available. Real projects rarely satisfy this assumption. One specialist may be assigned to several activities, a test rig may be available only on particular dates, or a supplier may have a fixed production slot. When activities compete for the same resource, the technically logical schedule may be infeasible.

Resource-constrained scheduling begins with a resource-loaded network. Each activity is assigned labor categories, equipment, facilities, materials, and sometimes budget. The planner then identifies periods in which demand exceeds availability. Feasible responses include changing activity sequence, splitting work, adding shifts, subcontracting, cross-training, resequencing non-critical activities, or changing the project completion date.

The critical-chain method, associated with constraint-based project management, extends critical-path thinking by considering both precedence and resource dependencies. It discourages excessive safety time embedded separately in every activity and instead places protection in strategically located buffers. A project buffer protects the committed completion date, while feeding buffers protect the critical chain from delays on non-critical paths. Resource buffers signal that a critical resource must be prepared and available when required.

The method is not a guarantee of shorter projects. Its effectiveness depends on credible estimates, behavioral discipline, realistic buffer sizing, and protection against multitasking. If employees are assigned to too many projects simultaneously, nominally short activities may take much longer because of switching and waiting. Critical-chain control therefore requires management of priorities and work release, not merely a new scheduling formula.

A practical buffer-management approach classifies buffer consumption into zones. Low consumption indicates normal progress; moderate consumption calls for investigation; and high consumption requires corrective action or escalation. The exact percentages should be defined by the organization and the nature of the project. Buffer status should not be used to conceal poor estimates or punish teams for reporting risk.

Allocating Scarce Resources Across Projects

Project portfolios create a second level of complexity. A factory may have several customer projects competing for the same design office, machining center, test laboratory, or installation crew. Prioritizing only by promised date can produce unstable schedules, while prioritizing only by revenue can neglect strategic customers, safety obligations, or contractual commitments.

A resource-allocation decision should consider:

1. contractual due dates and consequences of lateness;

2. strategic importance and customer impact;

3. remaining work and probability of completion;

4. availability of substitutes or subcontractors;

5. technical dependencies and risk reduction opportunities;

6. cash-flow and working-capital implications; and

7. safety, regulatory, and ethical obligations.

Useful methods include finite-capacity scheduling, linear or mixed-integer optimization, priority scoring, simulation, and scenario analysis. Optimization models can represent precedence, capacity, setup, and due-date constraints, but their recommendations are only as reliable as their data and assumptions. In uncertain environments, a robust plan may be preferable to a mathematically optimal plan that fails under minor disruption.

The theory of constraints (TOC) provides a practical managerial sequence: identify the system constraint, exploit it, subordinate other activities to it, elevate the constraint if necessary, and repeat the process when the constraint moves. In a project factory, the constraint may be a test facility rather than a machine. Releasing more work upstream without protecting the constraint increases work-in-process and obscures priorities.

Postponement, Modularity, and Variety Control

Postponement delays final product differentiation until demand or customer information is clearer. It is particularly relevant to mass customization and configure-to-order production. A producer may manufacture a common base unit, hold generic modules, and add customer-specific software, finishes, labels, or accessories only after the order is confirmed.

Postponement can reduce finished-goods inventory and forecast error, but it is not free. It may require flexible equipment, late-stage capacity, modular design, reliable information, and rapid changeovers. The postponement point should be selected by comparing the cost of flexibility with the cost of forecast-driven inventory and obsolescence.

Three design principles support postponement:

• Commonality: use shared components and interfaces across product variants.
• Modularity: separate product functions into modules that can be combined predictably.
• Decoupling: create an operational point at which upstream production can proceed independently of final customer-specific decisions.

In ETO environments, postponement may involve delaying final engineering details until customer requirements are frozen, while releasing long-lead common items earlier. This demands configuration control. A late change that affects interfaces, safety certification, or purchased components can invalidate the expected benefit.

Control Systems for Complex Production

Planning becomes control when actual performance is compared with the approved baseline and decisions are taken. Effective control requires a defined status date, reliable progress rules, current resource information, and an escalation process.

Progress should be measured by objective evidence rather than activity. For design, evidence may include an approved drawing or completed review. For fabrication, it may include accepted units or inspection records. “Ninety percent complete” is weak information unless the basis for the percentage is defined. Earned value management (EVM) can integrate schedule and cost perspectives through planned value, earned value, and actual cost. Schedule performance index and cost performance index may provide signals, but they should be interpreted carefully because aggregate indices can hide critical technical problems.

Short-interval control is useful near constraints and milestones. Daily or weekly coordination meetings should focus on commitments, blockers, decisions required, and changes to the near-term plan. They should not become lengthy reporting rituals. A good control system makes deviation visible early enough for action.

Technology, Analytics, and Digital Integration

Enterprise resource planning (ERP) systems, manufacturing execution systems (MES), product lifecycle management (PLM), project-management platforms, and supplier portals can connect engineering, procurement, production, and finance. PLM manages product definitions and revisions; ERP manages orders, materials, capacity, and costs; MES records shop-floor execution; and project systems manage network logic, milestones, risks, and issues.

Digital twins and simulation can test alternative schedules, capacity expansions, and disruption scenarios. Advanced analytics may estimate completion risk from historical duration, change, and supplier data. Machine learning can support anomaly detection, but it does not remove the need for causal analysis. A model trained on incomplete or biased historical data may systematically underestimate risk for new products, new suppliers, or unusual projects.

Automation is most valuable when it improves data quality and decision speed. Examples include automatic status capture from connected equipment, alerts for overdue approvals, finite-capacity rescheduling, and visual dashboards showing constraint loading and buffer status. However, excessive dashboard metrics can encourage local optimization. Digital governance must address access rights, version control, cybersecurity, data ownership, auditability, and human approval of high-impact decisions.

Illustrative Case: The Delayed Modular Processing Plant

Background

A fictional equipment manufacturer, Meridian Process Systems, receives an order to design, fabricate, test, and install a modular water-treatment plant. The project includes four process skids, control panels, pumps, piping, software configuration, factory testing, transport, and site commissioning. The promised delivery date is ten months after contract award.

Situation and problem

After three months, engineering drawings are incomplete, two long-lead pumps have not been released, and the electrical test area is booked by another project. Fabrication supervisors report that work is available for some trades but not for others. Management responds by authorizing overtime and releasing partially defined work to keep the workshop busy. Work-in-process rises, engineering changes multiply, and the installation team later discovers interface mismatches between piping and control panels.

Analysis

A cross-functional review constructs a WBS and resource-loaded network. It identifies the following interacting constraints: design approval, pump availability, a single electrical test area, and a specialist controls engineer shared with two projects. The original schedule treated engineering as nearly complete and assumed unlimited access to testing. It therefore understated both precedence and resource dependencies.

The review also finds that project progress had been reported by labor hours spent rather than accepted deliverables. Fabrication hours were high, but several assemblies could not be closed because inspection records and revised drawings were missing. The project was busy but not advancing proportionately toward customer acceptance.

Approach and solution

Meridian takes five actions. First, it establishes configuration control and divides the design into released, pending, and prohibited work. Second, it protects the test area as the system constraint and sequences projects through it using a finite-capacity schedule. Third, it assigns the controls engineer to the project’s critical chain during defined windows and creates a resource buffer before testing. Fourth, it postpones non-essential cosmetic customization while completing common skid structures and interfaces. Fifth, it introduces weekly milestone reviews based on objective evidence: approved drawings, received pumps, accepted weld records, completed software tests, and passed factory tests.

A project buffer is placed before the committed delivery milestone, and feeding buffers protect the critical chain from procurement and software activities. Procurement expediting is directed only at components that threaten the network, rather than at every late item. The project manager also negotiates an approved sequence change with the customer so that documentation and training can proceed in parallel with selected installation work.

Outcome

The project does not recover every lost week, but the revised plan makes the remaining risk visible. Fabrication work-in-process declines, test-area utilization becomes predictable, and engineering changes are concentrated before release rather than discovered during assembly. The customer receives a transparent forecast and accepts a staged handover with defined acceptance criteria.

Learning points

The case illustrates that overtime cannot solve an information or constraint problem by itself. Project control requires integration of engineering maturity, resource capacity, material availability, and acceptance evidence. It also demonstrates that postponement is effective only when interfaces are standardized and configuration is controlled. Finally, a project may show high activity and poor progress simultaneously; control must measure completed value, not busyness.

Challenges, Risks, and Common Mistakes

Complex PPC is exposed to several recurring risks. Scope ambiguity creates disputes and rework. Optimistic duration estimates hide uncertainty. Excessive multitasking increases completion time. Releasing work without approved information creates inventory that may be unusable. Local utilization targets encourage production of items not needed by the current constraint. Supplier schedules may be accepted without checking capacity, quality, logistics, or engineering dependencies.

Other mistakes include treating the baseline as immutable even when scope changes, updating dates without updating logic, reporting percentages without evidence, and confusing a schedule variance with the root cause of a problem. A further danger is “schedule padding” by every participant. When all activities contain hidden safety time, management cannot see where protection is actually located, and teams may delay starting work because early completion brings no recognized benefit.

Risk management should identify events, causes, consequences, owners, responses, and trigger conditions. Quantitative risk analysis can use scenario planning or simulation, but the quality of the result depends on the quality of estimates and correlations. Risk registers should be integrated with the schedule rather than maintained as isolated documents.

Governance, Ethics, and Professional Responsibility

Project PPC decisions have ethical consequences. A planner should not conceal a forecast delay by changing the baseline without authorization, report incomplete work as complete, or release a product without required inspection and regulatory evidence. Safety-critical activities must not be compressed merely to protect a commercial milestone. Suppliers and subcontractors should not be pressured into unsafe work or unrealistic commitments.

Governance requires clear authority for scope changes, schedule baselines, technical approvals, acceptance, and escalation. Audit trails are particularly important where digital systems automatically alter priorities or generate risk scores. Confidential customer data, design intellectual property, and supplier information must be protected. Professional judgment remains essential when algorithmic recommendations conflict with safety, quality, contractual, or social responsibilities.

Current Developments and Best Practices

Current practice is moving toward integrated planning across product lifecycle, project, supply chain, and shop-floor systems. Modular product platforms, digital work instructions, collaborative planning, probabilistic forecasting, and scenario-based capacity analysis are becoming more prominent. Artificial intelligence is increasingly used for schedule-risk prediction, document classification, resource matching, and anomaly detection, but adoption should be accompanied by validation, explainability, and human oversight.

The following practices provide a sound managerial foundation:

• build the schedule from a controlled WBS and explicit logic;
• distinguish technical precedence from resource precedence;
• plan at the level of detail justified by design maturity;
• identify and actively manage the system constraint;
• use objective completion criteria and evidence-based progress;
• protect critical work from uncontrolled multitasking;
• integrate engineering change, procurement, quality, and production control;
• reserve capacity for testing, commissioning, and other scarce stages;
• use buffers to absorb uncertainty without hiding problems;
• review alternative scenarios before committing to recovery actions; and
• treat safety, compliance, data integrity, and truthful reporting as non-negotiable.

Chapter Summary

PPC for projects and complex production environments must coordinate technical scope, information release, materials, resources, capacity, quality, and customer milestones. ETO and project production depend on controlled engineering and network logic; cellular systems require coordination between local flow and overall priorities; process industries require attention to campaigns, recipes, equipment, and quality release; and mass customization benefits from modularity and postponement.

CPM identifies schedule logic and float, while PERT represents duration uncertainty. Resource-constrained scheduling and critical-chain thinking recognize that scarce people, equipment, and facilities can create dependencies not visible in a purely technical network. Buffer management, constraint management, finite-capacity planning, and evidence-based progress reporting strengthen control. Digital systems can integrate PLM, ERP, MES, and project data, but technology cannot compensate for poor logic, weak governance, or unreliable data. Effective managers balance efficiency with resilience, and speed with safety, quality, transparency, and professional responsibility.

Key Terms

Work Breakdown Structure: Hierarchical decomposition of project scope into deliverables and work packages.

Engineer-to-Order: Production in which significant design and engineering begin or are completed after receiving a customer order.

Milestone: A zero-duration event representing an important achievement or decision point.

Critical Path: The sequence of activities determining the calculated project completion date.

Critical Chain: The longest resource- and precedence-constrained sequence in a project schedule.

Total Float: The time an activity can be delayed without delaying the calculated project completion date.

PERT: A scheduling method using optimistic, most likely, and pessimistic duration estimates.

Resource Loading: Assignment of labor, equipment, facilities, materials, or budget to scheduled activities.

Finite-Capacity Scheduling: Scheduling that respects actual limits on available resources.

Project Buffer: Time protection placed before the committed project completion date.

Feeding Buffer: Protection placed where a non-critical path feeds the critical chain.

Resource Buffer: A signal or time allowance ensuring that a critical resource is ready when required.

Theory of Constraints: An approach that improves system performance by managing its most restrictive constraint.

Postponement: Delaying final differentiation or configuration until demand information is clearer.

Modularity: Designing a product from relatively independent, standardized modules and interfaces.

Mass Customization: Providing substantial customer variety while retaining efficient repetitive operations.

Configuration Control: Formal management of product definitions, revisions, interfaces, and approved changes.

Earned Value Management: A method integrating scope, schedule, and cost performance through value-based measures.

Short-Interval Control: Frequent operational review focused on near-term commitments, blockers, and corrective actions.

Digital Twin: A digital representation used to monitor, analyze, or simulate a physical product, process, or system.

Review Questions

Short Answer Questions

1. Why is engineering information release a PPC concern in engineer-to-order production?

2. Define total float and explain its significance in CPM.

3. What is the purpose of a feeding buffer in critical-chain planning?

4. How does postponement support mass customization?

5. Why can high labor utilization coexist with poor project progress?

Long Answer Questions

1. Explain how CPM and PERT differ in their treatment of activity duration and uncertainty.

2. Discuss the principal PPC challenges of engineer-to-order and project production.

3. Explain how resource constraints alter a technically logical project schedule.

4. Evaluate the role of modularity, commonality, and postponement in mass customization.

5. Describe how ERP, PLM, MES, and project-management systems can be integrated for complex PPC.

Analytical / Application Questions

1. Construct the critical paths for the six-activity project in this chapter and identify which activity has apparent float. Explain why that float may not be dependable in a resource-constrained environment.

2. A factory has one test laboratory shared by three projects. Design a priority and capacity-control approach that protects contractual commitments without encouraging excessive work-in-process.

3. Using the Meridian Process Systems case, diagnose why overtime failed to solve the project problem and recommend two additional controls that would reduce recurrence risk.

22. Multiple Choice Questions with Answers

Question 1

In a CPM network, which condition identifies an activity as having zero total float?

A. Its duration is the longest individual duration in the project.

B. Its earliest start equals its latest start.

C. It uses the most expensive resource.

D. It has no predecessor activity.

Correct Answer: B. Its earliest start equals its latest start.

Question 2

What is the principal purpose of a feeding buffer in critical-chain management?

A. To increase the utilization of non-critical resources.

B. To protect the critical chain from delays on a feeding path.

C. To replace all activity duration estimates.

D. To eliminate the need for project milestones.

Correct Answer: B. To protect the critical chain from delays on a feeding path.

Question 3

A project schedule is technically feasible, but two activities require the same specialist at the same time. What should the planner do first?

A. Release both activities and allow informal prioritization.

B. Ignore the conflict because precedence logic is satisfied.

C. Resource-load the schedule and revise sequence or capacity assumptions.

D. Add inventory without examining the specialist constraint.

Correct Answer: C. Resource-load the schedule and revise sequence or capacity assumptions.

Question 4

Which practice best supports postponement in a mass-customization system?

A. Completing all product differentiation before receiving customer orders.

B. Using common modules and delaying final configuration.

C. Increasing the number of unique components for every option.

D. Eliminating configuration control to accelerate changes.

Correct Answer: B. Using common modules and delaying final configuration.

Question 5

In PERT, which estimate receives the greatest weighting in the expected-duration formula?

A. Optimistic estimate

B. Most likely estimate

C. Pessimistic estimate

D. Average of optimistic and pessimistic estimates only

Correct Answer: B. Most likely estimate

Question 6

In the illustrative Meridian case, why did high fabrication activity fail to demonstrate equivalent project progress?

A. Fabrication was completed without any labor input.

B. Progress was measured by hours spent rather than accepted deliverables.

C. The project had no customer requirements.

D. The test area had unlimited capacity.

Correct Answer: B. Progress was measured by hours spent rather than accepted deliverables.

Question 7

Which situation most clearly represents a process-industry PPC constraint?

A. A customer requests a unique product color.

B. A validated vessel is unavailable for the required batch sequence.

C. An engineer has excess design float.

D. A project milestone has zero duration.

Correct Answer: B. A validated vessel is unavailable for the required batch sequence.

Question 8

What is the main risk of releasing manufacturing work before drawings and interfaces are approved?

A. It necessarily reduces all work-in-process.

B. It guarantees earlier customer acceptance.

C. It can create rework, obsolete inventory, and interface mismatches.

D. It eliminates the need for engineering change control.

Correct Answer: C. It can create rework, obsolete inventory, and interface mismatches.

Question 9

Which action is consistent with the theory of constraints?

A. Maximize output at every workstation regardless of the bottleneck.

B. Identify, exploit, subordinate to, and elevate the system constraint.

C. Release as much upstream work as possible.

D. Prioritize only the shortest activities.

Correct Answer: B. Identify, exploit, subordinate to, and elevate the system constraint.

Question 10

Why should AI-generated schedule-risk predictions be subject to human oversight?

A. Digital systems cannot store schedule data.

B. Algorithms always produce identical recommendations.

C. Historical data may be incomplete or biased, especially for unusual projects.

D. Human oversight prevents any use of automation.

Correct Answer: C. Historical data may be incomplete or biased, especially for unusual projects.