Lean Supply Chains and Enterprise Integration

Introduction

Lean manufacturing is often introduced as an internal production philosophy, but its strategic effect is greatest when it extends across the entire value network. Materials, information, money, risks, and environmental impacts move across suppliers, manufacturers, logistics providers, distributors, retailers, service partners, and customers. A factory cannot be genuinely lean if it receives unreliable components, orders excessive quantities, transports materials inefficiently, or transfers defects and uncertainty to downstream partners.

A lean supply chain therefore seeks to create customer value with the least total consumption of resources, while preserving the capability to respond to variation and disruption. This requires more than low inventory. It requires synchronized planning, supplier development, stable logistics, transparent information, responsible sourcing, and governance of interorganizational relationships.

The central managerial challenge is balancing efficiency and resilience. Extreme utilization, single sourcing, minimal buffers, and long global supply lines may reduce normal-period cost but increase vulnerability. Contemporary lean supply chains combine waste elimination with risk-based buffers, multiple sourcing where justified, postponement, digital visibility, and collaborative problem solving.

Learning Objectives

By the end of this chapter, the learner should be able to:

1. Explain the principles and boundaries of lean supply-chain management.
2. Analyse supplier, procurement, logistics, and distribution processes using lean concepts.
3. Design collaborative planning, milk-run, postponement, and pull-based arrangements.
4. Evaluate supply-chain performance using operational, financial, resilience, and sustainability measures.
5. Balance efficiency, responsiveness, risk management, and responsible sourcing.
6. Recommend an enterprise-integration roadmap supported by appropriate digital technologies and governance.

1. From Lean Production to Lean Supply Networks

A supply chain is a network rather than a simple linear sequence. A focal firm may simultaneously buy materials from hundreds of suppliers, sell through several channels, outsource logistics, and share customers with competitors. Enterprise integration refers to the coordination of processes, information, decisions, and incentives across organizational boundaries.

Lean supply-chain management applies five related questions:

• What does the customer value?
• Where is value created and where is it delayed, duplicated, or destroyed?
• How can flow be established across organizational boundaries?
• How can demand pull replace unnecessary speculation and overproduction?
• How can continuous improvement be sustained without increasing unacceptable risk?

The classic wastes—overproduction, waiting, transport, overprocessing, inventory, motion, defects, and underused human capability—appear in supply networks in distinctive forms. Examples include duplicated forecasts, supplier queues, emergency freight, excessive packaging, obsolete inventory, repeated inspections, and procurement decisions based only on purchase price.

Lean supply-chain thinking differs from simple cost minimization. A low unit price can be economically inferior if it produces long lead times, poor quality, high minimum order quantities, carbon-intensive transport, or frequent disruption. The relevant object of improvement is total value-stream performance.

Value-stream perspective

A value-stream map should include not only internal operations but also supplier lead times, order transmission, transport, customs, receiving, inspection, storage, production, distribution, and customer replenishment. It should show both material and information flows. Important measures include total lead time, value-added time, queue time, defect loops, changeover constraints, order frequency, and inventory location.

A useful distinction is between internal lean and network lean. Internal lean improves a firm’s processes. Network lean aligns multiple firms around shared demand signals, standard work, synchronized replenishment, joint problem solving, and fair allocation of gains and risks.

2. Procurement and Supplier Integration

Strategic segmentation

Not every supplier requires the same relationship. A practical segmentation considers supply risk and business impact. Routine items may use catalogue purchasing and automated replenishment. Leverage items may be competitively sourced because alternatives exist. Bottleneck items require risk reduction and technical collaboration. Strategic items justify long-term development, joint planning, and senior-level governance.

Segmentation should be dynamic. A low-value component may become strategically important when it is sole-sourced, regulated, capacity-constrained, or difficult to qualify. Supplier classification should therefore incorporate substitutability, geographic concentration, lead time, intellectual-property dependence, financial health, sustainability exposure, and recovery difficulty.

Beyond price: total cost of ownership

Procurement decisions should evaluate total cost of ownership rather than quoted price alone. A simplified annual total-cost model is:

Here, P is purchase price per unit, Q is annual quantity, C_o is ordering and administration cost, C_q is quality-related cost, C_l is logistics and handling cost, C_r is risk or disruption-related expected cost, and C_s is sustainability, compliance, and disposal cost. All terms must be expressed in the same currency and time period. The model is useful for comparing sourcing alternatives, but expected disruption costs are estimates and should be tested through sensitivity analysis.

Quality-related cost may include inspection, rework, scrap, returns, warranty claims, and customer disruption. Risk cost may be represented by probability-weighted loss, but managers should not treat uncertain estimates as precise facts. Scenario analysis is preferable when disruption probabilities are poorly known.

Supplier development and quality at source

Lean supplier development replaces adversarial inspection with capability improvement. Its practices include:

• shared process audits and capability studies;
• standard specifications and engineering-change discipline;
• supplier training in problem solving and statistical process control;
• first-article approval and traceability for critical parts;
• joint kaizen events;
• rapid escalation and containment of nonconformity;
• supplier feedback based on quality, delivery, responsiveness, cost, and sustainability.

Quality at source does not mean eliminating all incoming controls. Verification should be risk-based. Critical safety or regulatory characteristics may require independent testing even when the supplier is highly capable.

Contracts and relational governance

Contracts must define specifications, service levels, change control, data rights, audit access, ethical requirements, remedies, business-continuity expectations, and exit provisions. However, contracts alone cannot solve coordination problems involving uncertain demand and complex technical dependencies. Relational governance—trust, repeated interaction, transparent performance data, and joint escalation—complements formal agreements.

A lean relationship is not necessarily a single-source relationship. Single sourcing can support learning and standardization, but dual or multiple sourcing may be justified for resilience, competition, or regulatory reasons. The decision should compare the cost of redundancy with the consequence and likelihood of failure.

3. Collaborative Planning and the Bullwhip Problem

The bullwhip effect is the amplification of demand variability as information moves upstream. It can arise from forecast updating, order batching, price promotions, allocation rules, long lead times, and shortage gaming. Its consequences include unstable production schedules, excess inventory, expediting, and poor capacity utilization.

The first response is not merely to improve the forecast. Partners should improve the flow and interpretation of information. Common practices include:

• sharing point-of-sale or consumption data;
• agreeing on a common calendar and unit of measure;
• using collaborative planning, forecasting, and replenishment;
• setting explicit replenishment rules;
• reducing order batching through smaller, more frequent orders;
• stabilizing prices and avoiding unnecessary promotions;
• separating genuine demand changes from inventory corrections;
• using sales and operations planning to reconcile demand, supply, capacity, and financial plans.

Pull and replenishment signals

A pull system authorizes replenishment from actual consumption or a clearly defined downstream requirement. A basic two-bin system is appropriate for stable, repetitive demand. Kanban quantity can be estimated as:

where n is the number of kanban containers or cards, D is demand per unit time, L is replenishment lead time in the same time unit, s is the planned allowance for variability expressed as a decimal, and C is the quantity per container. The result is rounded upward because a fractional container is not operationally possible. The formula assumes reasonably stable average demand, a known replenishment lead time, and a consistent container quantity. Excessive use of s can conceal process problems; it should be reduced through improvement as reliability increases.

For example, if demand is 240 units per day, lead time is 0.5 day, variability allowance is 20%, and each container holds 30 units:

n = (240 × 0.5 × 1.20) ÷ 30 = 4.8

The system requires five containers. This is a starting design, not a substitute for validating actual withdrawal patterns, container availability, quality holds, and replenishment discipline.

Collaborative planning architecture

Effective collaboration has three layers:

1. Operational layer: orders, deliveries, shortages, inventory status, quality alerts, and shipment tracking.
2. Tactical layer: replenishment parameters, capacity plans, promotions, engineering changes, and supplier schedules.
3. Strategic layer: network design, technology standards, sourcing strategy, investment, resilience, and sustainability goals.

The parties must agree who owns data, which signal is authoritative, how exceptions are escalated, and how benefits are shared. Visibility without decision rights creates information overload rather than integration.

4. Lean Logistics: Milk Runs, Cross-Docking, and Flow

Transportation waste includes unnecessary distance, low vehicle utilization, waiting, repeated handling, damage, and emergency freight. Lean logistics designs transport around predictable flow rather than isolated purchase orders.

Milk-run logistics

A milk run is a scheduled route that collects from or delivers to several locations using a planned sequence. Compared with independent supplier-to-plant shipments, it can increase vehicle utilization, reduce receiving peaks, and support smaller, more frequent deliveries. Its success depends on compatible time windows, standardized packaging, accurate quantities, route discipline, and contingency plans.

A route should be evaluated by total route time, distance, capacity, loading constraints, delivery frequency, emissions, and service risk. A route that minimizes kilometres but causes missed production windows is not lean. Likewise, a high-frequency route may reduce inventory while increasing transport cost and emissions; the trade-off must be measured.

Cross-docking and consolidation

Cross-docking transfers inbound goods directly to outbound vehicles with little or no storage. It is suitable when demand, timing, labeling, and quality are sufficiently reliable. Consolidation combines smaller shipments into economical loads. Both methods reduce handling and inventory, but they can propagate errors quickly. Scanning, clear ownership, standardized labels, and exception processes are essential.

Packaging and material handling

Returnable packaging can reduce waste and damage, but it requires reverse logistics, cleaning, asset tracking, and adequate circulation stock. Packaging design should consider ergonomics, cube utilization, product protection, recyclability, and worker safety. A packaging change must be assessed across the entire loop, not only at the point of shipment.

5. Postponement and Distribution Design

Postponement delays product differentiation until demand is more visible. Examples include late-stage configuration, local labeling, final assembly near the customer, or holding generic modules rather than finished variants.

Postponement is attractive when product variety is high, demand is uncertain, common components are stable, and the final customization process is fast and reliable. It is less attractive when customers require immediate availability, customization requires specialized equipment, or late-stage operations are expensive.

A postponement decision should examine:

• the location and capability of the decoupling point;
• commonality of components;
• final-process capacity and lead time;
• inventory value and obsolescence risk;
• transport and customs implications;
• customer service requirements;
• quality and traceability requirements.

Postponement is not simply a reduction in finished-goods inventory. It redistributes inventory and capability. Generic inventory, modular design, flexible labor, and late-stage information accuracy become more important.

Distribution networks should distinguish push, where inventory is positioned from forecasts, from pull, where replenishment responds to consumption. Most practical systems are hybrid: strategic positioning may be forecast-driven, while regional replenishment and final configuration are pull-driven.

6. Measuring Enterprise Integration

A balanced measurement system prevents local optimization. Useful dimensions include:

Metrics need precise definitions. For example, on-time-in-full should specify the promised date, quantity tolerance, shipment scope, and treatment of customer-requested changes. A metric can be mathematically accurate but managerially misleading if definitions vary between firms.

An inventory-turn measure is commonly defined as:

Both numerator and denominator are measured in currency over the same period. High turns may indicate efficient flow, but they can also indicate under-buffering and poor service. The metric must therefore be interpreted alongside service, quality, and resilience measures.

7. Efficiency, Resilience, and Risk Management

Lean systems reduce waste and expose problems; resilient systems maintain or restore acceptable performance under disruption. These goals are complementary when lean removes avoidable complexity and resilience protects against consequential uncertainty. They conflict when managers interpret every buffer as waste or every redundancy as inefficiency.

Risk management should identify hazards, assess exposure, select treatments, and monitor changes. Important treatments include:

• qualifying alternate suppliers or materials;
• maintaining strategic safety stock for high-consequence items;
• regionalizing selected capacity;
• standardizing components;
• designing substitution options;
• establishing emergency logistics contracts;
• conducting disruption simulations;
• documenting recovery priorities and communication protocols.

Safety stock should not be used as a universal remedy. For independent demand and approximately normal demand during replenishment, a commonly used expression is:

Here, SS is safety stock in units, z is the standard-normal service factor, and σ_LT is the standard deviation of demand during lead time. This expression assumes that the relevant demand distribution is reasonably represented by a normal model, lead-time uncertainty is either negligible or incorporated into σ_LT, replenishment is regular, and the service definition corresponds to the selected z. If both demand and lead time vary, σ_LT must be estimated using an appropriate combined-variability model; it should not be obtained by casually adding standard deviations.

Risk-based lean design asks four questions: What can fail? What is the consequence? How quickly can the system detect and recover? What is the least costly control that reduces unacceptable exposure? This approach is superior to applying identical inventory policies to every item.

8. Responsible Sourcing and Ethical Governance

Supply-chain integration creates responsibilities beyond operational performance. Firms may be accountable for labor conditions, forced labor risks, discrimination, unsafe workplaces, environmental damage, corruption, data misuse, and misleading sustainability claims in their supply base.

Responsible sourcing should include:

• a supplier code aligned with applicable law and recognized labor and environmental principles;
• risk-based due diligence before and during the relationship;
• traceability appropriate to the material and risk;
• worker grievance channels and protection from retaliation;
• corrective action that addresses root causes rather than merely demanding documents;
• credible audit methods, including worker voice and independent verification where necessary;
• transparent escalation and disengagement criteria.

Audits are imperfect. They may miss subcontracting, coached interviews, or conditions between visits. Responsible governance therefore combines audits with purchasing-practice reform, supplier capability building, grievance evidence, transaction monitoring, and board-level accountability.

Commercial pressure can undermine ethical objectives. For example, unrealistic lead times, late engineering changes, and aggressive price reductions may encourage excessive overtime or unsafe shortcuts. Responsible sourcing must therefore examine the buying firm’s own behavior.

9. Digital Technology and Artificial Intelligence

Enterprise integration increasingly depends on shared digital infrastructure. Electronic data interchange, application programming interfaces, supplier portals, cloud planning platforms, barcode and RFID systems, transport-management systems, and control towers can improve transaction accuracy and visibility.

Technology does not create lean flow automatically. Digitizing a fragmented process may simply accelerate bad data and unnecessary approvals. Before automation, organizations should clarify process ownership, standardize master data, remove redundant transactions, and define exception rules.

AI can support demand sensing, anomaly detection, ETA prediction, supplier-risk monitoring, route optimization, and document classification. Its use requires governance of data quality, model drift, explainability, cybersecurity, privacy, and human accountability. AI-generated forecasts should not override operational knowledge without controlled validation. In high-consequence decisions, a human decision-maker should retain authority and a documented audit trail should exist.

Digital integration also increases cyber exposure. Supplier access, shared credentials, ransomware, compromised software, and manipulated shipment data can disrupt physical operations. Cybersecurity must therefore be treated as a supply-chain continuity issue, including access control, segmentation, backups, incident exercises, and supplier security requirements.

10. Implementation Roadmap

A practical enterprise-integration programme can proceed through six iterative stages:

1. Define customer value and boundaries. Select a product or service family and map the end-to-end value stream.
2. Establish a fact base. Measure lead times, demand variability, inventory, defects, supplier performance, transport, emissions, and disruption exposure.
3. Segment relationships and risks. Distinguish strategic, bottleneck, leverage, and routine categories; identify critical dependencies.
4. Design the future flow. Select pull signals, delivery frequency, milk runs, postponement points, packaging standards, and information interfaces.
5. Pilot and learn. Use a limited supplier group or product family; monitor service, cost, quality, people, and risk outcomes.
6. Scale through governance. Standardize successful practices, develop suppliers, align contracts and incentives, and review the system through regular improvement cycles.

Leadership must protect improvement work from short-term functional targets. Procurement should not receive a price-saving target that encourages larger batches while operations is measured on inventory reduction. Shared measures and gain-sharing mechanisms can align decisions, provided benefits and responsibilities are transparent.

Applied Case: Northstar Appliances (Illustrative)

Background

Northstar Appliances assembles premium washing machines in a regional plant. It buys electronic controllers from one qualified supplier, sheet-metal panels from three suppliers, and distributes finished machines through retailers. The plant had acceptable internal productivity but frequent shortages of controllers, high finished-goods inventory, emergency air freight, and retailer stock-outs.

Problem and analysis

A value-stream investigation showed that retailers sent weekly orders, distributors consolidated them into irregular batches, and the plant converted these orders into a monthly forecast. The controller supplier received large, fluctuating releases with a twelve-week lead time. The plant held finished products in many colors and configurations, while demand for individual variants was uncertain. Supplier performance was measured mainly by unit price and monthly delivery, not by total cost or recovery capability.

The team identified four linked causes: demand signals were delayed, order batches were large, product differentiation occurred too early, and the controller was single-sourced without a recovery plan. Emergency freight and shortages were symptoms rather than isolated logistics problems.

Approach

Northstar introduced a common weekly demand and inventory review with the distributor, shared point-of-sale data for major retailers, and defined a frozen short-term schedule plus a flexible planning horizon. It established a smaller, more frequent controller replenishment signal and worked with the supplier to reduce changeover and shipment lead time. A second controller source was qualified for selected models, not to duplicate all volume but to provide competition and recovery capacity.

The firm moved final labeling and selected configuration activities closer to regional distribution centers. It redesigned packaging for standardized modules and introduced a scheduled milk run for nearby panel suppliers. Procurement evaluated suppliers using total cost, quality, delivery, risk, and responsible-sourcing criteria. A joint escalation process was created for shortages and engineering changes.

Outcome

In the illustrative scenario, finished-goods variety at the plant was reduced, controller release variability fell, and emergency freight declined. Retail availability improved even though total finished-goods inventory decreased. Some inventory moved upstream into common modules, and the distribution centers required new skills and information systems. The second source increased apparent unit cost for a portion of purchases, but scenario analysis showed lower expected disruption exposure and stronger recovery capability.

Learning points

1. Internal productivity cannot compensate for unstable interorganizational flow.
2. Postponement changes the location and capability of inventory; it does not eliminate all inventory.
3. Supplier collaboration requires shared data, clear decision rights, and mutual investment.
4. Resilience may require deliberate redundancy that is not visible in a unit-price comparison.
5. Outcomes must be judged across service, total cost, risk, sustainability, and people—not by one metric.

Challenges and Limitations

Lean supply-chain programmes face several limitations. First, supply networks have power imbalances; a dominant buyer may impose changes without sharing benefits, causing supplier financial distress. Second, global networks may be too complex for complete visibility. Third, demand data can be biased by promotions, stock-outs, and channel incentives. Fourth, local optimization may reappear when departments retain conflicting targets.

Fifth, reducing inventory without reducing variability can damage service and employee well-being. Sixth, digital systems can create surveillance, cybersecurity, privacy, and algorithmic-bias concerns. Seventh, responsible sourcing may raise short-term cost or reveal problems that are expensive to remediate. These are not reasons to abandon lean integration; they are reasons to use disciplined governance, transparent assumptions, and staged experimentation.

Chapter Summary

Lean supply-chain management extends value creation and waste reduction beyond the factory to suppliers, procurement, logistics, distribution, and customers. Its essential mechanisms include end-to-end value-stream analysis, supplier segmentation and development, total-cost evaluation, collaborative planning, pull replenishment, milk-run logistics, cross-docking, postponement, and balanced performance measurement.

Effective integration is not synonymous with minimum inventory, single sourcing, or maximum asset utilization. Lean systems must be designed for variation and disruption through risk-based buffers, alternate sources, modularity, recovery planning, and visibility. Responsible sourcing adds ethical, environmental, labor, and governance obligations, while digital technologies provide value only when processes, data, accountability, and cybersecurity are sound.

At postgraduate level, the central managerial insight is systemic: a decision is lean only when it improves total network performance without exporting cost, risk, waste, or harm to another participant. Enterprise integration therefore combines operational excellence with strategic coordination, resilience, and responsible leadership.

Key Terms

Lean supply chain: A network designed to deliver customer value while reducing avoidable resource consumption and delay.

Enterprise integration: Coordination of processes, information, decisions, and incentives across organizational boundaries.

Value stream: The complete sequence of activities and information required to deliver a product or service.

Total cost of ownership: The full relevant cost of acquiring, using, supporting, and disposing of an item.

Supplier segmentation: Classification of suppliers according to business impact, supply risk, and relationship requirements.

Supplier development: Joint activity to improve supplier capability, quality, delivery, cost, or sustainability.

Quality at source: Designing and controlling work so that defects are prevented or detected where they are created.

Bullwhip effect: Amplification of demand variation as information moves upstream.

Collaborative planning: Joint coordination of forecasts, replenishment, capacity, and operational decisions.

Pull system: A replenishment system triggered by downstream consumption or an authorized requirement.

Kanban: A visual or electronic authorization for production, movement, or replenishment.

Milk run: A scheduled route serving multiple suppliers or customers.

Cross-docking: Transfer of inbound goods to outbound flow with minimal storage.

Postponement: Delaying product differentiation until demand is more certain.

Decoupling point: The location where forecast-driven activity changes to demand-driven activity.

Resilience: The ability to absorb, adapt to, and recover from disruption.

Responsible sourcing: Procurement that addresses legal, ethical, environmental, labor, and social impacts.

Control tower: A coordinated visibility and exception-management capability for a supply network.

Total cost to serve: The complete cost of fulfilling a customer, channel, or product requirement.

Review Questions

Short Answer Questions

1. Why is a supply chain better understood as a network than as a linear chain?
2. State two limitations of using purchase price as the sole procurement criterion.
3. What is the purpose of a milk run?
4. Explain the difference between postponement and finished-goods inventory reduction.
5. Why must lean supply chains include resilience measures?

Long Answer Questions

1. Explain how supplier segmentation can guide sourcing, development, governance, and risk treatment.
2. Discuss the causes of the bullwhip effect and evaluate methods for reducing it.
3. Compare push, pull, and hybrid replenishment systems in a multi-echelon distribution network.
4. Analyse the relationship between lean logistics, milk runs, packaging, and cross-docking.
5. Discuss how responsible sourcing changes the design of procurement performance systems.

Analytical / Application Questions

1. Daily demand is 300 units, replenishment lead time is 0.75 day, the variability allowance is 15%, and each container holds 40 units. Calculate the required number of kanban containers using the formula in this chapter, round upward, and state two assumptions that should be validated.
2. A firm is considering a low-price overseas supplier and a higher-price regional supplier. Design a total-cost and resilience comparison that includes logistics, quality, disruption exposure, sustainability, and recovery capability. Explain what evidence would be required before making the decision.
3. A distributor has frequent stock-outs despite high total inventory. Diagnose the likely information, batching, postponement, and governance problems, then propose a 90-day pilot for collaborative planning and replenishment.

Multiple Choice Questions with Answers

Question 1

Which statement best describes enterprise integration in a lean supply chain?

A. Reducing every supplier to the lowest possible unit price

B. Coordinating processes, information, decisions, and incentives across organizational boundaries

C. Moving all inventory to the manufacturer

D. Replacing suppliers with internal production

Correct Answer: B. Coordinating processes, information, decisions, and incentives across organizational boundaries

Question 2

In the total-cost model, which item is explicitly included beyond purchase price and quantity?

A. Only advertising expense

B. Only employee wages

C. Quality, logistics, risk, and sustainability-related costs

D. Only the supplier’s profit margin

Correct Answer: C. Quality, logistics, risk, and sustainability-related costs

Question 3

A milk run is primarily designed to:

A. Create a separate direct truck for every supplier

B. Collect from or deliver to several locations on a planned route

C. Eliminate all delivery schedules

D. Increase emergency freight frequency

Correct Answer: B. Collect from or deliver to several locations on a planned route

Question 4

If daily demand is 240 units, lead time is 0.5 day, variability allowance is 20%, and container capacity is 30 units, how many kanban containers are required after rounding upward?

A. 4

B. 4.8

C. 5

D. 6

Correct Answer: C. 5

Question 5

Postponement primarily involves:

A. Completing all product differentiation before demand is known

B. Delaying differentiation until demand is more visible

C. Eliminating modular design

D. Increasing finished-goods variety at the factory

Correct Answer: B. Delaying differentiation until demand is more visible

Question 6

Which situation is most likely to intensify the bullwhip effect?

A. Frequent small replenishment orders based on consumption

B. Shared point-of-sale data

C. Large order batches and unstable promotions

D. A common planning calendar

Correct Answer: C. Large order batches and unstable promotions

Question 7

Which statement about safety stock is most accurate?

A. It is always waste and should be eliminated

B. It should be identical for every stock-keeping unit

C. It can protect against uncertainty but should be based on risk and variability

D. It removes the need for supplier development

Correct Answer: C. It can protect against uncertainty but should be based on risk and variability

Question 8

Why can single sourcing conflict with resilience?

A. It always produces poor quality

B. Failure at one source may interrupt the entire supply of a critical item

C. It prevents all collaborative improvement

D. It necessarily increases transportation distance

Correct Answer: B. Failure at one source may interrupt the entire supply of a critical item

Question 9

Which is an example of responsible sourcing?

A. Ignoring subcontractors outside the first-tier supplier

B. Evaluating labor, environmental, legal, and ethical risks in the supply base

C. Selecting suppliers solely by quoted price

D. Using audits without corrective action

Correct Answer: B. Evaluating labor, environmental, legal, and ethical risks in the supply base

Question 10

What is a key governance requirement when AI is used for supply-chain decisions?

A. Remove all human review

B. Allow the model to operate without data controls

C. Provide accountability, validation, cybersecurity, and monitoring for model drift

D. Use AI only for increasing order batch sizes

Correct Answer: C. Provide accountability, validation, cybersecurity, and monitoring for model drift