11. Project Risk, Uncertainty and Resilience

Introduction and Context

Projects are temporary systems created to deliver a defined outcome under constraints of time, cost, scope, quality, resources and regulatory requirements. Because projects are unique, they are exposed to events and conditions that may alter their expected results. A supplier may fail, a design assumption may prove incorrect, a regulation may change, demand may decline, or a new technology may create an unexpected opportunity. Project management therefore involves not only planning what should happen, but also preparing for what might happen.

Risk management provides the discipline for dealing with uncertainty. It helps project teams identify threats and opportunities, assess their significance, select appropriate responses and monitor changing conditions. However, risk management is not the same as attempting to eliminate all uncertainty. Some uncertainty is unavoidable, and excessive efforts to control minor risks can consume resources that would be better used elsewhere. The managerial task is to make informed choices about exposure, preparedness and resilience.

For production managers, the subject is particularly important. Production projects often involve expensive equipment, complex supply networks, safety obligations, production ramp-up, technology integration and interdependent schedules. A delay in one component can interrupt commissioning; a quality failure can affect both cost and customer confidence; a disruption in utilities can stop an entire production line. Effective risk practice links project-level analysis with operational continuity and organizational resilience.

Learning Objectives

After studying this chapter, students should be able to:

1. Distinguish risk, uncertainty, issue, assumption, constraint and opportunity.

2. Explain the relationship between risk management, contingency planning, crisis response and resilience.

3. Construct and maintain a useful project risk register.

4. Apply qualitative probability–impact analysis and prioritization methods.

5. Use decision trees, expected monetary value, scenario analysis and Monte Carlo simulation in project decisions.

6. Select suitable responses to threats and opportunities.

7. Evaluate contingency reserves, management reserves and escalation arrangements.

8. Analyse an applied project situation and recommend resilient responses.

9. Recognize ethical, governance, technological and organizational challenges in risk management.

The Nature of Project Risk

A project risk is an uncertain event or condition that, if it occurs, has a positive or negative effect on one or more project objectives. A negative risk is commonly called a threat, while a positive risk is called an opportunity. Risk has two essential characteristics: uncertainty about whether the event will occur and consequences if it does occur.

Risk should be distinguished from an issue. A risk is a possible future event; an issue is a condition that has already occurred or is occurring and requires action. For example, the possibility that a critical motor will arrive late is a risk. A motor that is already three weeks late is an issue. Confusing the two leads to poor records and delayed responses.

An assumption is something accepted as true for planning purposes, although it may not be fully verified. A constraint is a limitation imposed on the project, such as a statutory deadline, fixed budget or restricted production shutdown window. Assumptions generate risks when they are wrong. For instance, assuming that an existing electrical substation has sufficient capacity may create a major risk if the assumption has not been technically validated.

Risk exposure is the combined effect of probability and consequence. In simple cases, it can be represented as:

Risk exposure = Probability of occurrence × Impact if it occurs

This expression is useful for prioritization, but it does not capture every dimension of risk. A low-probability event with catastrophic safety consequences may deserve more attention than a frequent event with minor cost effects. Impacts may occur across several dimensions: cost, schedule, scope, quality, safety, environment, reputation, compliance and stakeholder relationships.

Project risk also exists at different levels. Individual risks concern specific events, such as a supplier delay. Overall project risk is the effect of uncertainty on the project as a whole. Several individually moderate risks may interact and create a serious systemic exposure. For example, late design approval, weak supplier capacity and an inflexible shutdown date may combine to make commissioning failure highly probable.

Risk Management as a Decision Process

Risk management is not a document-production exercise. It is a continuing decision process integrated with project planning, execution, monitoring and control. A practical cycle consists of the following activities:

• establishing the risk context and objectives;
• identifying threats, opportunities, assumptions and sources of uncertainty;
• analysing probability, impact and interrelationships;
• evaluating risk against organizational criteria;
• planning and assigning responses;
• implementing responses and tracking trigger conditions; and
• reviewing exposure, learning from events and communicating decisions.

The process should begin during project initiation and continue through closure. Risks change as the project develops. A construction risk that is critical during design may become irrelevant after equipment has been installed, while operational or safety risks may increase during commissioning. Risk ownership must therefore be explicit. The risk owner is accountable for monitoring and managing a risk, whereas a response owner may be responsible for carrying out a particular action.

The Risk Register

The risk register is the central working record of identified risks. A useful register normally includes:

• a unique identification number;
• risk statement, preferably written as cause–event–effect;
• category or source of risk;
• affected objectives;
• probability and impact assessment;
• overall rating or priority;
• proposed response strategy;
• preventive and contingent actions;
• risk owner and response owner;
• early-warning indicators or triggers;
• due dates and status; and
• residual risk after planned responses.

A strong risk statement is specific. “Supply risk” is too vague. “If the sole-source casting supplier cannot meet the revised delivery date, commissioning will be delayed by up to four weeks” provides a basis for analysis and action. Risk registers should be periodically cleansed: closed risks should be archived, duplicated risks combined, obsolete assumptions removed and newly discovered risks added.

The register should not become a static list held by the project manager. Workshops, design reviews, supplier meetings, safety assessments, lessons-learned sessions and frontline observations are all sources of risk information. In production environments, operators and maintenance personnel often identify practical failure modes that are not visible in senior management reports.

Qualitative Analysis: Probability–Impact Methods

Qualitative analysis uses descriptive scales to rank risks. Probability may be expressed as very low, low, medium, high and very high, while impact may be assessed across cost, time, quality, safety and other objectives. The two ratings are then combined in a probability–impact matrix. A red, amber and green classification can support attention, but colour alone is not analysis. The organization must define what each rating means.

For example, a project may define a high schedule impact as a delay exceeding 20 working days and a high cost impact as an increase above 10 per cent of the approved budget. Without explicit thresholds, different assessors may assign inconsistent ratings. A risk rated “high” by one department may be considered “medium” by another because the scales are interpreted differently.

Qualitative analysis is valuable when data are limited, rapid decisions are required or the cost of detailed modelling is not justified. It also supports communication with stakeholders who may not need a numerical simulation. Its limitations include subjectivity, anchoring on initial estimates, optimism bias and the tendency to overlook dependencies between risks.

A useful extension is urgency analysis. Two risks with the same probability and impact may require different responses if one has a trigger tomorrow and the other is unlikely to materialize for six months. Proximity, detectability, manageability and connectivity may therefore be used in addition to probability and impact.

Quantitative Decision Tools

Expected Monetary Value

Expected monetary value (EMV) weights possible financial outcomes by their probabilities:

EMV = Σ (Probability of outcome × Monetary value of outcome)

Suppose a project faces a 30 per cent probability of a ₹2 million loss from a supplier failure and a 70 per cent probability of no loss. The EMV of the threat is ₹0.6 million. If a preventive action costs ₹0.2 million and reduces the probability to 10 per cent, the post-response expected loss is ₹0.2 million. The expected reduction in exposure is ₹0.4 million, so the action has an expected net benefit of ₹0.2 million, before considering non-financial effects.

EMV is an aid to decision-making, not a prediction of the actual result. A project will not experience “0.6 of a failure.” The value represents the long-run average across comparable situations or the rational valuation of uncertain alternatives. EMV can also incorporate opportunities, such as a 40 per cent chance of saving ₹1 million through an alternative process, producing a positive EMV of ₹0.4 million.

Financial estimates should include the time value of money when decisions extend over several years. They should also avoid false precision. A range based on credible assumptions is more useful than a highly precise figure unsupported by evidence.

Decision Trees

Decision trees represent sequential choices and uncertain outcomes. A decision node shows an action under managerial control; a chance node shows uncertain outcomes; terminal branches show consequences. The analyst calculates expected values from the terminal branches backwards toward the initial decision.

Consider a plant expansion with two alternatives. A large installation costs ₹8 million and generates ₹14 million in value if demand is high, with probability 0.6, but ₹5 million if demand is low, with probability 0.4. Its expected value before investment cost is ₹10.4 million, giving an EMV of ₹2.4 million after cost. A modular installation costs ₹5 million and generates ₹9 million under high demand and ₹6 million under low demand. Its expected value is ₹7.8 million, giving an EMV of ₹2.8 million. The modular option has the higher expected value, although management must also consider strategic flexibility, capacity constraints and the consequences of underestimating demand.

Decision trees are especially helpful when information can be purchased or when decisions occur in stages. A firm may first conduct a technical test, then decide whether to proceed with full deployment. The value of the test is the improvement in decision quality minus its cost.

Scenario Analysis

Scenario analysis examines coherent combinations of assumptions rather than isolated events. Typical scenarios may be labelled baseline, constrained supply, accelerated demand, regulatory change or severe disruption. Each scenario should specify its assumptions, operational consequences and management actions.

Scenario analysis is not the same as forecasting one most likely future. Its purpose is to test whether the project strategy remains viable under materially different conditions. It is particularly useful for strategic projects, capacity expansion, digital transformation and projects exposed to macroeconomic or geopolitical change. Scenario planning can reveal robust choices: actions that perform acceptably across several futures, even if they are not optimal in one forecast.

Monte Carlo Simulation

Monte Carlo simulation models uncertainty by assigning probability distributions to uncertain variables and repeatedly sampling from those distributions. In a schedule simulation, activity durations may be represented by triangular or beta distributions. In a cost simulation, labour rates, material prices and productivity may be modelled as ranges or distributions. Thousands of iterations produce a distribution of possible completion dates or total costs.

The output may show that the planned completion date has only a 35 per cent probability of being achieved, while a date two weeks later has an 80 per cent probability. This information supports a realistic commitment and the sizing of time contingency. Similarly, a project budget may be set at a percentile of the simulated cost distribution rather than at the simple sum of most-likely estimates.

Simulation quality depends on the quality of inputs. Correlations must be considered: material price escalation and supplier delay may be related, and several activities may share a common productivity risk. A model that assumes independence when risks are connected can significantly understate exposure. Simulation results should be explained in managerial language, including assumptions, sensitivity drivers and confidence levels. They should not be treated as objective truth merely because they are expressed in percentages.

Responses to Threats and Opportunities

Threat responses should be selected according to the nature and importance of the exposure. Common strategies include:

• Avoid: change the plan so that the threat no longer applies, such as removing an unproven technology from a critical path.
• Mitigate: reduce probability or impact, such as conducting early testing or qualifying a second supplier.
• Transfer or share: allocate financial or operational consequences to another party through insurance, contract terms, warranties or partnerships.
• Accept: take no proactive action beyond monitoring, often because the cost of action exceeds the expected benefit. Acceptance may be passive or supported by a contingency plan.
• Escalate: refer the risk to a higher organizational level when it exceeds the project manager’s authority or affects the portfolio or enterprise.

Opportunity strategies include exploit, enhance, share, accept and escalate. Exploiting an opportunity ensures that it occurs, for example by assigning the organization’s most experienced team to a process innovation. Enhancing increases its probability or benefit. Sharing may involve a joint venture or incentive arrangement.

Responses should be proportionate and feasible. A response that creates a larger secondary risk is not necessarily effective. For example, accelerating procurement may reduce schedule exposure but increase quality risk, cash requirements and inspection workload. Every major response should therefore be evaluated for residual risk and secondary risks.

Contingency, Crisis Response and Resilience

Contingency is planned capacity or action reserved for a risk that may occur. A contingency reserve is generally associated with identified, or “known-unknown,” risks. It may be held in time, money, materials, capacity or management attention. Management reserve is intended for unforeseen work within the project’s scope and is controlled at an appropriate management level. The exact treatment depends on organizational governance and accounting rules; reserves should never be hidden padding.

A contingency plan specifies what will be done if a trigger occurs. It should identify the trigger, decision authority, immediate actions, resources, communication requirements and recovery criteria. For example, if a critical supplier misses a milestone by five working days, the plan may activate an approved alternate supplier, authorize expedited logistics and notify the commissioning team.

A crisis is an event requiring urgent coordination because it threatens people, assets, continuity, reputation or the organization’s licence to operate. Crisis response differs from routine risk management. It emphasizes life safety, rapid situational awareness, clear authority, accurate communication and stabilization. A typical sequence is protect people, establish command, contain the event, communicate verified information, restore critical functions and conduct a structured review.

Resilience is the capability of a project or organization to absorb disturbance, adapt while conditions change and recover or transform without losing essential purpose. Resilience is broader than redundancy. A second supplier is one form of redundancy, but resilience may also arise from modular design, cross-trained personnel, strong information flows, flexible contracts, decentralized decision-making and learning after disruption.

Resilience can be assessed through measures such as time to detect, time to respond, time to recover, critical-function availability and the ability to maintain minimum viable operations. In production projects, resilience engineering asks not only how systems fail, but also how normal work succeeds under variable conditions. This encourages attention to interfaces, human judgement and weak signals.

Governance, Ethics and Professional Judgement

Risk decisions involve accountability and values, not only mathematics. A project team must not suppress an inconvenient risk to protect a business case or performance report. Deliberately understating probability, hiding safety concerns or transferring a risk contractually without ensuring the other party can manage it violates professional responsibility.

Governance arrangements should define risk appetite, escalation thresholds, approval rights, reporting frequency and reserve authority. Safety, environmental and legal risks may have a low tolerance even when their expected monetary value is small. Compliance cannot be justified away through favourable averages. Stakeholder communication should be timely and honest, particularly when uncertainty affects employees, communities, customers or regulators.

Risk workshops should encourage dissent and psychological safety. Seniority can distort estimates when junior specialists hesitate to challenge a preferred plan. Independent reviews, anonymous input and structured techniques such as the Delphi method can reduce groupthink. Confidential commercial information must also be protected when risk registers are shared across suppliers or partners.

Digital Tools, Data and Emerging Practice

Digital project platforms increasingly connect risk registers with schedules, cost systems, procurement records, quality observations and change-control workflows. Automated alerts can identify overdue responses, expiring contracts, unusual cost trends or repeated equipment failures. Dashboards make risk exposure visible across projects and portfolios.

Artificial intelligence and advanced analytics can support pattern recognition, text classification, anomaly detection and prediction from historical project data. For example, an analytical system may identify that combinations of design changes, late approvals and high subcontractor turnover often precede schedule slippage. However, AI outputs depend on data quality and may reproduce historical bias. They should support, not replace, accountable professional judgement. Sensitive project information also requires cybersecurity controls, access management and clear rules regarding data ownership.

Emerging practice is moving from isolated risk registers toward integrated resilience and enterprise risk management. Climate-related disruption, cyber threats, supply-chain concentration, geopolitical uncertainty and dependence on digital infrastructure require cross-functional analysis. Organizations increasingly use stress tests, digital twins and live operational data to examine how projects perform under extreme but plausible conditions.

Illustrative Case: Resilient Commissioning of an Automated Packaging Line

Background

A food-products manufacturer initiated a project to install an automated packaging line during a planned six-week plant shutdown. The project involved equipment procurement, software integration, building modifications, operator training and regulatory validation. The line was expected to increase capacity and reduce manual handling.

Situation and Problem

The project team identified a single overseas supplier for a specialized servo drive. The supplier had a strong technical reputation but a long lead time. The original plan assumed delivery eight weeks before installation. A probability–impact workshop assessed a 25 per cent probability of a six-week delay, with an estimated schedule impact of ₹3 million because the plant would lose production during the shutdown. The risk register also identified software integration, operator acceptance and electrical-capacity risks.

The project sponsor initially proposed accepting the supplier risk because the component was reliable and the probability seemed moderate. The project manager argued that the risk was connected to the fixed shutdown window and therefore had a disproportionately severe consequence.

Analysis

The initial expected loss was:

0.25 × ₹3 million = ₹0.75 million.

An alternate local supplier could provide a compatible drive, but qualification and testing would cost ₹0.25 million. The alternative reduced the probability of missing the shutdown window to 8 per cent. The residual expected loss would be ₹0.24 million. The expected reduction of ₹0.51 million exceeded the qualification cost, before considering safety and customer-service effects.

A schedule simulation showed that the original plan had a 52 per cent probability of completing commissioning within the shutdown. With early software testing, preassembled electrical panels and the alternate-drive qualification, the probability increased to 84 per cent. The analysis also revealed that software integration, not the drive alone, was the largest remaining schedule driver.

Approach and Response

The team adopted a layered response. It qualified the alternate drive, ordered the original component as a backup, created a hardware-in-the-loop software test environment and moved operator training to a simulated interface before installation. A contingency plan defined escalation triggers: failure to pass the alternate-drive test by a specified date would activate expedited procurement and a revised commissioning sequence.

The project established a daily shutdown control room during installation. The incident structure assigned clear authority for safety, technical decisions, production communication and supplier coordination. A minimum viable production plan allowed a partially automated line to operate if full integration was delayed.

Outcome

In this illustrative case, the original drive was delayed, but the qualified alternative enabled mechanical commissioning to proceed. Software testing identified two interface defects before the shutdown. Full production began four days later than the ideal target but within the approved contingency window. The project avoided a major production interruption and retained the original drive as a tested spare.

Learning Points

The case demonstrates that risk exposure depends on context, not probability alone. A fixed shutdown window amplified the effect of a supplier delay. Quantitative analysis supported investment in mitigation, while scenario and simulation methods exposed schedule interactions. Resilience came from technical redundancy, early testing, skilled people, clear triggers and a recovery plan—not from the risk register alone.

Common Errors and Limitations

Several failures recur in project risk practice. Teams may identify risks only at project start, use vague statements, assign ownership to an entire department rather than an individual, or record responses without funding and deadlines. They may focus on threats and ignore opportunities, treat the highest numerical score as automatically dominant, or assume that risks are independent when they are connected.

Another error is confusing a contingency allowance with permission to exceed the budget. Reserves must be governed and released against defined conditions. Excessive reliance on averages can hide extreme outcomes, particularly in safety, cyber and environmental contexts. Conversely, excessive conservatism can make valuable projects appear unattractive.

Risk analysis also suffers from cognitive biases. Optimism bias leads teams to underestimate duration and cost; availability bias causes recent or memorable events to receive disproportionate attention; anchoring makes early estimates difficult to revise; and confirmation bias encourages selective use of evidence. Independent challenge, reference-class information, ranges, sensitivity analysis and periodic reassessment help counter these weaknesses.

Best Practices for Production Project Managers

Effective practice is characterized by a few disciplined habits. Define risk appetite and rating scales before assessment. Write risks in cause–event–effect form. Link significant risks to schedule activities, cost accounts, requirements and contracts. Assign owners with authority and resources. Record triggers and residual risks, not merely initial ratings. Use qualitative methods for routine prioritization and quantitative methods where exposure, complexity or decision value justifies them.

Test contingency plans through workshops or exercises. Conduct pre-mortems by asking why the project has failed and then examining the imagined causes. Maintain alternative suppliers or design options where interruption costs are high. Integrate safety and operational personnel into project reviews. Report uncertainty transparently, including confidence ranges and assumptions. Finally, treat every disruption and near miss as a source of learning rather than merely an occasion for blame.

Chapter Summary

Project risk is the effect of uncertainty on objectives and may create either threats or opportunities. It differs from an issue, assumption and constraint. Risk management is a continuous process of identification, analysis, evaluation, response, monitoring and communication. The risk register provides a living record of causes, events, effects, owners, triggers, responses and residual exposure.

Probability–impact analysis supports qualitative prioritization, while EMV, decision trees, scenario analysis and Monte Carlo simulation provide progressively richer quantitative insight. These tools aid decisions but do not replace judgement or ethical responsibility. Threat responses include avoidance, mitigation, transfer, acceptance and escalation; opportunities may be exploited, enhanced, shared, accepted or escalated.

Contingency plans and reserves prepare the project for identified uncertainty. Crisis response focuses on safety, command, containment, communication and recovery. Resilience is the broader capability to absorb disturbance, adapt and maintain essential functions. In production projects, resilience depends on technical flexibility, supplier diversity, capable people, reliable information and effective governance. Digital tools and AI can improve visibility and prediction, but their outputs require quality data, cybersecurity and accountable human oversight.

Key Terms

Risk: An uncertain event or condition that may affect project objectives.

Threat: A risk with a potentially negative effect.

Opportunity: A risk with a potentially positive effect.

Issue: A condition or event that has already occurred and requires action.

Assumption: A proposition accepted as true for planning purposes.

Constraint: A limitation imposed on project choices or execution.

Risk exposure: The combined significance of probability and impact.

Risk register: A controlled record of identified risks, analysis, ownership and responses.

Risk owner: The person accountable for monitoring and managing a risk.

Risk trigger: An observable condition indicating that a risk is occurring or becoming imminent.

Residual risk: Exposure remaining after responses are implemented.

Secondary risk: A new risk created by implementing a response.

Expected monetary value: The probability-weighted average financial consequence of uncertain outcomes.

Decision tree: A graphical model of sequential decisions and uncertain outcomes.

Scenario analysis: Evaluation of project performance under coherent alternative sets of assumptions.

Monte Carlo simulation: Repeated probabilistic sampling used to produce a distribution of possible outcomes.

Contingency reserve: Time, money or capacity allocated for identified uncertainty.

Crisis response: Coordinated urgent action to protect people, assets and continuity during a severe event.

Resilience: The capability to absorb disturbance, adapt and recover while maintaining essential purpose.

Risk appetite: The amount and type of uncertainty an organization is willing to accept.

Review Questions

Short Answer Questions

1. Distinguish a project risk from an issue, using one example of each.

2. What information should a well-constructed risk register contain?

3. Define expected monetary value and state its principal limitation.

4. Differentiate contingency reserve from management reserve.

5. Why is resilience broader than redundancy?

Long Answer Questions

1. Explain the complete project risk-management cycle and its relationship with project governance.

2. Compare probability–impact analysis, EMV, decision trees, scenario analysis and Monte Carlo simulation.

3. Discuss the major response strategies for threats and opportunities, including residual and secondary risks.

4. Explain how contingency planning and crisis response should be designed for a production project.

5. Analyse the role of ethics, organizational culture, data quality and professional judgement in risk decisions.

Analytical / Application Questions

1. A project has a 20 per cent probability of a ₹4 million supplier-loss consequence. A mitigation costing ₹0.3 million reduces probability to 5 per cent. Calculate the expected reduction in loss and recommend whether the mitigation is financially justified, noting non-financial considerations.

2. Design a risk-register entry for a production-line commissioning risk. Include the cause, event, effect, probability, impact, owner, trigger, preventive action, contingency action and residual risk.

3. A project has a fixed plant shutdown date, several interdependent suppliers and uncertain software integration. Propose a resilience strategy using at least three methods discussed in the chapter and explain how success would be monitored.

22. Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes a project risk from an issue?

A. A risk is always negative, whereas an issue is always positive.

B. A risk is a possible future event, whereas an issue has already occurred or is occurring.

C. A risk belongs to senior management, whereas an issue belongs to the project team.

D. A risk is financial, whereas an issue is operational.

Correct Answer: B. A risk is a possible future event, whereas an issue has already occurred or is occurring.

Question 2

A risk has a 30% probability of causing a ₹2 million loss. What is its expected monetary value?

A. ₹0.06 million

B. ₹0.30 million

C. ₹0.60 million

D. ₹2.60 million

Correct Answer: C. ₹0.60 million

Question 3

Which response strategy changes the project plan so that a threat no longer applies?

A. Accept

B. Transfer

C. Mitigate

D. Avoid

Correct Answer: D. Avoid

Question 4

What is the principal purpose of a risk trigger?

A. To calculate the project’s final profit

B. To indicate that a risk is occurring or becoming imminent

C. To replace the risk owner

D. To eliminate the need for contingency reserves

Correct Answer: B. To indicate that a risk is occurring or becoming imminent

Question 5

A decision tree is most useful when a project decision involves:

A. Only fixed costs and no uncertainty

B. Sequential choices and uncertain outcomes

C. Only qualitative stakeholder opinions

D. A completed project with no remaining decisions

Correct Answer: B. Sequential choices and uncertain outcomes

Question 6

What does Monte Carlo simulation generally provide?

A. A single guaranteed completion date

B. A distribution of possible outcomes based on repeated probabilistic sampling

C. A list of project stakeholders

D. A contractual transfer of all risks

Correct Answer: B. A distribution of possible outcomes based on repeated probabilistic sampling

Question 7

Why can a low-probability safety risk require more attention than a high-probability minor cost risk?

A. Safety risks are never measurable.

B. Probability–impact scores are irrelevant to all projects.

C. The severity and ethical significance of the consequence may be substantially greater.

D. Cost risks cannot be recorded in a risk register.

Correct Answer: C. The severity and ethical significance of the consequence may be substantially greater.

Question 8

Which characteristic most directly demonstrates project resilience?

A. Maintaining a static risk register without review

B. Absorbing disruption, adapting and maintaining essential functions

C. Avoiding all changes to the original plan

D. Transferring every risk to a supplier

Correct Answer: B. Absorbing disruption, adapting and maintaining essential functions

Question 9

In the illustrative packaging-line case, why did the fixed shutdown window increase the significance of supplier delay?

A. It made the supplier contract unnecessary.

B. It linked the delay to a severe and time-sensitive production consequence.

C. It guaranteed that the component would be defective.

D. It removed the need for software testing.

Correct Answer: B. It linked the delay to a severe and time-sensitive production consequence.

Question 10

Which statement about AI-based risk analytics is most appropriate?

A. AI outputs are objective regardless of data quality.

B. AI eliminates the need for risk owners.

C. AI can support pattern recognition but requires quality data and accountable human judgement.

D. AI should be used only after project closure.

Correct Answer: C. AI can support pattern recognition but requires quality data and accountable human judgement.