Digital Materials Management & ERP Systems

Chapter 6
Supplier Relationship, Risk and Collaboration Platforms

Post Graduate Programme in Materials Management
Digital Materials Management & ERP Systems   •   Post Graduate

Supplier Relationship, Risk and Collaboration Platforms

Introduction

Materials management has moved from transactional purchasing toward digitally enabled supplier ecosystems. A supplier is no longer assessed only by quoted price. Its contribution may include process capability, design knowledge, delivery flexibility, cybersecurity, carbon performance, financial stability and the ability to recover from disruption. Digital supplier portals, enterprise resource planning (ERP) systems, supplier relationship management (SRM) applications and analytics platforms provide the infrastructure for managing these dimensions systematically.

Supplier relationship management (SRM) is the coordinated process of segmenting suppliers, selecting appropriate relationship strategies, measuring performance, developing capability, managing risk and creating value through collaboration. Its purpose is not to make every supplier a strategic partner. Rather, it is to allocate managerial attention and digital resources according to supply importance, risk and opportunity.

A mature digital approach connects supplier master data, sourcing, contracts, purchase orders, goods receipts, quality records, invoices, sustainability information and external risk signals. This creates a common evidence base for decisions while preserving human judgement where data are incomplete or contextual.

Learning Objectives

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

  1. Explain the role and architecture of supplier portals and collaboration platforms.
  2. Design supplier onboarding, segmentation, scorecards and development programmes.
  3. Apply quantitative methods for supplier performance and supply-risk prioritisation.
  4. Evaluate how ERP and SRM systems support quality, resilience, innovation and responsible sourcing.
  5. Critically assess governance, cybersecurity, ethical and implementation challenges.
  6. Recommend an integrated supplier relationship and risk-management approach.

1. Supplier Relationship Management as a Value System

Traditional procurement often treats the supplier relationship as a sequence of requisition, quotation, purchase order, receipt and payment. This transaction-centred model is appropriate for low-value, standardised purchases but inadequate for critical or technically complex supply. SRM broadens the relationship across the supplier lifecycle:

  • qualification and onboarding;
  • contracting and commercial governance;
  • operational execution;
  • quality and delivery improvement;
  • innovation and joint problem solving;
  • continuity, exit and replacement planning.

The relationship should be designed according to the economic and operational characteristics of the category. A supplier of office stationery may require automated ordering and catalogue controls. A supplier of a safety-critical component may require audits, change notification, validation, dual sourcing and executive review.

Three principles are central:

Differentiation. Suppliers should receive different levels of governance and collaboration according to value, risk and strategic potential.

Transparency. Performance expectations, data definitions, escalation rules and responsibilities should be visible to both parties.

Reciprocity. Collaboration is sustainable when the benefits and burdens of information sharing, investment and improvement are fairly allocated.

Supplier power also matters. Resource-dependence theory suggests that a buyer cannot manage a relationship independently of the supplier’s alternatives, capabilities and bargaining position. Relational views of exchange add that trust, repeated interaction and joint routines can create value that a purely price-based contract cannot capture. These perspectives do not eliminate commercial discipline; they explain why the lowest initial price may not produce the lowest total cost or highest resilience.

2. Digital Supplier Collaboration Architecture

A supplier collaboration platform is a controlled digital environment through which buyers and suppliers exchange master data, transactions, documents, performance information and improvement actions. It may be embedded in an ERP suite or connected to an SRM, e-procurement, quality, product-lifecycle-management or risk-intelligence system.

A typical architecture contains five layers:

LayerTypical information and capability
Identity and accessSupplier accounts, roles, authentication, segregation of duties
Master dataLegal entity, tax status, bank details, sites, products and certificates
Transactional collaborationRFQs, bids, purchase orders, confirmations, advance shipping notices, invoices
Performance and riskQuality, delivery, cost, corrective actions, sanctions, financial and geopolitical signals
Analytics and workflowAlerts, dashboards, approvals, scorecards, escalations and improvement projects

The platform should integrate with ERP rather than become a parallel record system. The ERP normally remains authoritative for financial postings, purchase orders, goods receipts and inventory transactions, while the collaboration layer supports external interaction, workflow and richer supplier information. Application programming interfaces (APIs), event-based integration or batch interfaces can transfer data, but each field requires a named data owner and agreed definition.

A purchase order confirmation is operationally useful only when it updates planning assumptions. An advance shipping notice is valuable when it supports dock scheduling, inbound visibility and exception management. A quality nonconformance is valuable when it links the affected lot, purchase order, inspection result, corrective action and supplier learning record.

Supplier portals

A portal can allow suppliers to:

  • maintain approved organisational and banking information;
  • submit certificates, declarations and insurance evidence;
  • respond to requests for quotation;
  • acknowledge orders and propose dates;
  • submit shipping notices and electronic documents;
  • view forecast information within agreed confidentiality limits;
  • respond to corrective-action requests;
  • participate in innovation, sustainability and continuity assessments.

Portal design must consider supplier capability. Complex interfaces, duplicate data entry and unclear workflows can reduce participation, especially among small suppliers. Responsive design, multilingual support, training, assisted onboarding and alternative channels are therefore part of implementation rather than optional conveniences.

3. Supplier Onboarding and Data Governance

Onboarding is a risk-control process, not merely account creation. It establishes whether the organisation is legally eligible, commercially suitable, operationally capable and digitally trustworthy.

A robust onboarding sequence is:

  1. Pre-screening: identify category fit, ownership, location, sanctions exposure and basic capability.
  2. Due diligence: verify legal registration, beneficial ownership, tax information, insurance, financial indicators and relevant certifications.
  3. Capability assessment: examine capacity, process controls, technology, quality systems, business continuity and subcontracting.
  4. Responsible-sourcing assessment: evaluate labour standards, environmental practices, human rights risks and anti-bribery controls.
  5. Digital registration: establish roles, authentication, data permissions and communication preferences.
  6. Approval and activation: obtain approvals under a documented risk-based workflow.
  7. Pilot and review: test transactions and monitor early performance before full reliance.

Supplier master-data quality is fundamental. Duplicate supplier records can fragment spend and conceal concentration risk. Incorrect bank details create payment-fraud exposure. Missing site identifiers make it difficult to determine whether a certificate applies to the manufacturing location or merely to the corporate parent.

Data governance should define ownership, validation rules, review frequency, retention periods and change approval. Sensitive data should be collected only for a legitimate purpose, accessed on a least-privilege basis and protected in accordance with applicable privacy and cybersecurity requirements. A supplier’s willingness to provide data does not remove the buyer’s responsibility to secure it.

4. Supplier Segmentation and Relationship Design

Segmentation converts a large supplier population into manageable relationship groups. The classic Kraljic purchasing portfolio uses two dimensions: profit or business impact and supply risk. It identifies four broad categories:

CategoryCharacteristicsAppropriate response
Non-criticalLow impact, low riskCatalogue buying, automation and low administrative cost
LeverageHigh impact, low riskCompetitive sourcing, volume aggregation and commercial negotiation
BottleneckLow impact, high riskAvailability protection, alternatives, inventory or technical substitution
StrategicHigh impact, high riskExecutive governance, joint planning, development and innovation

The model is useful but incomplete. Digital segmentation may add dimensions such as switching cost, sustainability exposure, cybersecurity criticality, innovation potential, geographic concentration and supplier financial dependence. Segmentation should be reviewed when demand, technology, regulation or supply conditions change.

A strategic classification does not automatically mean a friendly or informal relationship. It means that the consequence of failure and the potential value of coordinated action justify deeper governance. Conversely, a bottleneck supplier may require intensive risk control even though annual spend is modest.

Relationship design should specify meeting cadence, data sharing, escalation thresholds, performance measures, audit rights, continuity obligations and innovation mechanisms. Governance may include operational reviews, quarterly business reviews, steering committees and executive sponsors. The objective is proportionality: enough control to protect the organisation, but not so much bureaucracy that the relationship becomes uneconomic.

5. Supplier Scorecards and Performance Analytics

A supplier scorecard translates expectations into observable measures. Common dimensions include quality, delivery, cost, responsiveness, innovation, sustainability and compliance. The measures must be defined precisely; otherwise, a dashboard creates an appearance of objectivity without reliable meaning.

A weighted score can be calculated as:

S = ∑(wi xi), i = 1, 2, …, n

where S is the total score, wi is the weight assigned to criterion i, xi is the normalised performance score for criterion i, and n is the number of criteria. The weights must satisfy ∑wi = 1 and each normalised score should use a common scale, such as 0 to 100. The method assumes that criteria are sufficiently comparable and that additive weighting is an acceptable approximation. It does not prove causation or eliminate judgement.

For a supplier assessed on quality (30%), delivery (30%), cost (20%) and sustainability (20%), with scores of 90, 80, 70 and 60 respectively:

S = (0.30 × 90) + (0.30 × 80) + (0.20 × 70) + (0.20 × 60) = 78

The result is 78 points out of 100. It should not be interpreted without examining the underlying measures. For example, a high average delivery score may conceal repeated failures on a critical part.

Useful operational measures include:

  • On-time-in-full (OTIF): deliveries meeting both the agreed date and required quantity divided by total deliveries, multiplied by 100.
  • Defect rate: defective units divided by total units received, commonly expressed as a percentage or parts per million.
  • Corrective-action closure: corrective actions closed by the agreed due date divided by actions due, multiplied by 100.
  • Invoice exception rate: invoices requiring manual intervention divided by total invoices.

Definitions must state the denominator, time window, exclusions and source system. Delivery performance based on supplier-confirmed dates is not equivalent to performance against the original requested date. Neither measure is inherently correct; each answers a different managerial question.

Scorecards should support dialogue, not punishment alone. A red indicator should trigger diagnosis: engineering change, forecast instability, transport failure, internal receiving delay or supplier process weakness may each produce similar symptoms.

6. Supplier Development and Collaborative Improvement

Supplier development is the buyer’s deliberate effort to improve supplier capability or jointly improve an end-to-end process. It is justified when the supplier is important, alternatives are limited, improvement benefits are material or learning has strategic value.

Typical interventions include process audits, technical assistance, quality-system training, joint value analysis, capacity investment, tooling support, shared forecasts and problem-solving workshops. Lean and Six Sigma methods may be applied, but tools should follow diagnosis. A supplier does not need a sophisticated statistical programme if the immediate problem is an incorrect specification or unstable purchase-order revision process.

A disciplined improvement cycle is:

  1. define the problem and customer impact;
  2. establish a verified baseline;
  3. identify root causes using evidence;
  4. agree countermeasures, owners and dates;
  5. pilot and validate the change;
  6. standardise the successful method;
  7. monitor whether the gain persists.

The buyer should distinguish supplier-caused variation from system-caused variation. Expediting a supplier while frequently changing forecasts may transfer rather than solve the problem. Collaborative planning, forecasting and replenishment can reduce such instability when the parties agree data definitions, horizons and responsibilities.

Innovation collaboration requires protection of intellectual property, clear ownership of jointly developed designs, confidentiality controls and a fair commercial path from idea to adoption. A portal can collect ideas, but innovation depends on evaluation capability, engineering involvement and incentives.

7. Supply Risk Monitoring and Resilience

Supply risk is the possibility that an event will prevent the supply network from meeting required objectives. Relevant risks include financial distress, capacity shortfall, quality failure, cyberattack, geopolitical disruption, natural hazards, regulatory change, labour abuse, transport interruption and dependence on a single site or material.

A simple prioritisation measure is expected loss:

EL = p × I

where EL is expected loss in monetary units per defined period, p is the probability of the event during that period, and I is the monetary impact if it occurs. The estimate assumes that probability and impact are meaningfully defined and that a single-period expected-value approximation is suitable. It does not describe timing, correlation, extreme events or the distribution of outcomes.

If a disruption has an estimated annual probability of 0.15 and an impact of $400,000, then:

EL = 0.15 × $400,000 = $60,000 per year

The figure supports comparison, not automatic acceptance of risk. A low-probability event with catastrophic safety consequences may require action even when expected monetary loss is modest.

Risk platforms combine internal and external information. Internal signals include late confirmations, declining quality, capacity utilisation, overdue corrective actions and unusual payment requests. External signals may include financial filings, sanctions lists, severe-weather alerts, port conditions, political developments, cyber intelligence and adverse media. Automated alerts require verification because external data may be delayed, duplicated or falsely interpreted.

A practical risk register records the risk statement, affected materials and sites, owner, indicators, current controls, residual exposure, contingency action and review date. Scenario analysis should ask:

  • What if the supplier’s primary site is unavailable for four weeks?
  • Which materials share the same sub-tier source?
  • How quickly can an approved alternative be qualified?
  • What inventory, design substitution or capacity reservation is economically justified?
  • Which customer, regulatory or safety obligations cannot be delayed?

Resilience is not synonymous with holding maximum inventory. It can arise from dual sourcing, modular design, qualified substitutes, regional capacity, visibility into sub-tier suppliers, contractual recovery rights, emergency logistics and organisational learning. Each option has cost and may introduce new risks.

8. Responsible Sourcing and Governance

Responsible sourcing integrates environmental, social and governance concerns into supplier decisions. It includes labour rights, forced-labour prevention, health and safety, freedom of association, environmental emissions, waste, water, anti-corruption and responsible minerals where relevant.

A supplier code of conduct is useful only when linked to due diligence, risk prioritisation, remediation and consequence management. Audits alone are insufficient: announced audits may not reveal actual conditions, and social performance can deteriorate between visits. Effective systems combine documentary review, worker-informed evidence, grievance channels, site assessment, corrective action and escalation.

Governance questions include:

  • Who may approve a high-risk supplier exception?
  • How are conflicts of interest disclosed?
  • How are gifts, facilitation payments and hospitality controlled?
  • Can procurement override a risk hold, and what evidence is required?
  • How are allegations investigated without retaliation?
  • When is disengagement appropriate, and when is responsible remediation preferable?

Digital records improve traceability but can also create surveillance and privacy concerns. Supplier employees should not be exposed to unnecessary monitoring. Data collection should be proportionate, secure and transparent, with retention and access rules that reflect legal obligations.

9. Artificial Intelligence and Advanced Analytics

AI can assist with supplier classification, anomaly detection, document extraction, demand-risk modelling, contract analysis and early-warning alerts. For example, natural-language processing may identify changes in supplier financial disclosures or regulatory notices. Machine-learning models may detect unusual lead-time or invoice patterns.

However, predictive performance depends on data quality, representativeness and changing conditions. A model trained on historical disruptions may underperform during a novel crisis. Supplier risk scores may reproduce geographic or sector bias if proxies are poorly selected. Black-box recommendations can also make it difficult to explain why a supplier was blocked or downgraded.

Responsible deployment requires:

  • a defined business decision and human accountability;
  • validated data lineage and documented model assumptions;
  • testing for bias, false positives and false negatives;
  • explainable alerts and an appeal process;
  • access control and protection of confidential supplier data;
  • monitoring for model drift and periodic recalibration.

AI should prioritise investigation, not silently determine supplier eligibility or terminate relationships. Human expertise remains essential for interpreting context and negotiating corrective action.

10. Implementation Roadmap and Critical Success Factors

A practical implementation can proceed in stages:

Stage 1: Diagnose. Map supplier processes, pain points, systems, data quality and risk exposures. Identify a category or supplier group where measurable value is likely.

Stage 2: Design. Define supplier segments, workflows, roles, measures, integration architecture, security requirements and governance rules.

Stage 3: Clean and standardise data. Remove duplicates, establish site-level records, harmonise units and create controlled vocabularies for commodities, certificates, incidents and performance events.

Stage 4: Pilot. Test onboarding, order confirmation, scorecards and risk alerts with representative suppliers. Measure adoption and process time, not only technical completion.

Stage 5: Integrate and scale. Connect the portal to ERP, quality, finance and planning systems. Extend by category while preserving standards and learning from exceptions.

Stage 6: Improve. Review benefits, supplier experience, cybersecurity events, false alerts, unresolved data issues and relationship outcomes.

Success measures may include reduced cycle time, fewer invoice exceptions, improved OTIF, faster corrective-action closure, reduced premium freight, improved audit remediation and greater visibility of sub-tier exposure. Technology adoption is not itself a benefit. A portal with high login rates but poor data quality may increase administrative work without improving decisions.

Applied Case: Meridian Components (Illustrative)

Background

Meridian Components, a fictional manufacturer of industrial control equipment, purchased a safety-critical electronic module from one approved supplier. Annual spend was moderate, but the module had a six-month qualification cycle and no immediate substitute. The supplier’s delivery score appeared acceptable at 94% based on supplier-confirmed dates.

Problem

A production interruption revealed that the supplier had repeatedly moved confirmation dates after receiving orders. The ERP dashboard did not compare performance against the original requirement date. Meridian also lacked visibility of a sub-tier semiconductor source and had inconsistent records for supplier manufacturing sites.

Analysis

A cross-functional review recalculated performance using the original requested date and found OTIF of 76%. A risk assessment estimated a 20% annual probability of a four-week disruption with an impact of $1.2 million:

EL = 0.20 × $1,200,000 = $240,000 per year

The expected loss justified investigation, but the team also recognised that the estimate excluded safety and customer-reputation effects. The supplier was classified as strategic because business impact and supply risk were both high.

Approach and solution

Meridian introduced a portal workflow requiring order acknowledgement within two working days, reason codes for changes, site-level capacity information and advance shipping notices. The scorecard separated requested-date OTIF from confirmed-date adherence. A quarterly business review examined capacity, quality, cyber controls and sub-tier exposure.

The companies jointly mapped the semiconductor sub-tier, created a continuity scenario, qualified a second source for a critical component and agreed a corrective-action plan. Meridian stabilised its own rolling forecast and established an engineering change-notification process. Supplier data access was limited by role, and bank-detail changes required independent verification.

Outcome

After two quarters, requested-date OTIF increased to 92%, overdue corrective actions fell, and Meridian could identify the affected sub-tier site in a disruption simulation. The second source was more expensive on unit price but reduced dependence and shortened recovery time. The project demonstrated that supplier performance was partly a relationship and internal-planning problem, not simply a supplier-effort problem.

Learning points

  1. Metric definitions can conceal operational risk.
  2. Moderate spend does not imply low strategic importance.
  3. Sub-tier visibility is essential for meaningful resilience analysis.
  4. Supplier development is more effective when internal causes are addressed.
  5. Digital controls must be paired with governance, technical qualification and human collaboration.

Challenges and Limitations

Digital supplier management can fail through excessive complexity, poor integration, low supplier adoption, unreliable external data and metric gaming. Small suppliers may lack systems or staff to maintain multiple portals. A buyer that demands extensive information without offering value may drive suppliers away or encourage superficial compliance.

Scorecards can create perverse incentives if buyers reward only price or delivery while ignoring quality and total cost. Risk models can encourage false precision. Supplier segmentation can become static, and strategic labels may be influenced by organisational politics. Audits may measure documentation rather than actual behaviour.

Cybersecurity is a shared concern. Portals should use strong authentication, encryption, secure development practices, logging, vulnerability management, incident response and supplier access reviews. Integration accounts require least privilege, and high-risk changes such as bank-account amendments should use independent verification.

The managerial task is therefore not to maximise data or automation. It is to create a trustworthy decision system in which information is relevant, controls are proportional, exceptions are investigated and commercial relationships remain capable of learning.

Chapter Summary

Supplier relationship management integrates segmentation, onboarding, performance management, development, risk monitoring and collaboration across the supplier lifecycle. Supplier portals provide the interaction layer, while ERP systems provide transaction and financial control. Effective architecture depends on clean master data, integration, role-based access and clear ownership.

Segmentation, especially the distinction between strategic, leverage, bottleneck and non-critical categories, helps allocate governance proportionately. Weighted scorecards convert expectations into comparable measures, but their validity depends on precise definitions and contextual interpretation. Supplier development combines evidence-based diagnosis, joint improvement and responsible commercial governance.

Risk monitoring should combine internal performance data with verified external signals and should consider probability, impact, concentration, recovery time and non-financial consequences. Expected loss is a useful prioritisation tool but cannot represent every severe or correlated event. Responsible sourcing requires due diligence, remediation, ethical controls and privacy-aware data governance. AI can improve detection and prioritisation, but it requires explainability, human accountability and continuous validation.

The central managerial lesson is that digital systems do not replace relationships. They make relationships more visible, measurable and governable; value arises when organisations use that visibility to collaborate, prevent disruption, improve capability and make responsible decisions.

Key Terms

Supplier relationship management: Coordinated management of supplier segmentation, performance, risk and collaboration.

Supplier portal: Controlled digital interface through which suppliers exchange information and transact with a buyer.

Supplier master data: Core identifying, legal, financial, site and classification information about a supplier.

Onboarding: Process of qualifying, registering, approving and activating a supplier.

Supplier segmentation: Grouping suppliers according to value, risk, capability or strategic importance.

Kraljic portfolio: Framework classifying purchases by business impact and supply risk.

Strategic supplier: Supplier with high business impact and high supply risk or collaboration potential.

Supplier scorecard: Structured set of supplier performance measures and ratings.

OTIF: Delivery that meets both the required date and required quantity.

Supplier development: Buyer-supported activity that improves supplier or joint process capability.

Corrective action: Agreed response designed to eliminate the cause of a nonconformance.

Supply risk: Possibility that an event will prevent required supply performance.

Expected loss: Probability of an event multiplied by its estimated impact.

Sub-tier supplier: Supplier that provides goods or services to the buyer’s direct supplier.

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

Responsible sourcing: Integration of ethical, social, environmental and governance considerations into supply decisions.

Data lineage: Traceable record of where data originated, how it changed and how it is used.

Least privilege: Restricting access to only the information and actions necessary for a role.

Review Questions

Short Answer Questions

  1. What is the purpose of supplier segmentation?
  2. Distinguish a supplier portal from an ERP system.
  3. Define OTIF and explain why its denominator and date basis matter.
  4. What information should a supplier risk register contain?
  5. Why is human judgement still required when AI is used for supplier risk monitoring?

Long Answer Questions

  1. Explain how a digital supplier collaboration architecture can support the complete supplier lifecycle.
  2. Critically evaluate the strengths and limitations of the Kraljic portfolio for modern supplier segmentation.
  3. Discuss the design principles of an effective supplier scorecard, including measurement validity and behavioural consequences.
  4. Explain how supplier development can improve quality, resilience and innovation while maintaining commercial accountability.
  5. Analyse the ethical, cybersecurity and governance requirements of responsible supplier-data management.

Analytical / Application Questions

  1. A supplier has quality, delivery, cost and sustainability scores of 85, 75, 90 and 65. The weights are 35%, 30%, 20% and 15%. Calculate the weighted score and recommend one managerial action, explaining your reasoning.
  2. A critical supplier has a 10% annual probability of disruption causing an estimated $2 million loss. Identify the expected loss, explain two limitations of this estimate and propose three resilience actions.
  3. Design a supplier-monitoring dashboard for a strategic supplier of a safety-critical component. Specify at least six measures, their data sources, escalation thresholds and the governance meeting at which each measure should be reviewed.

Multiple Choice Questions with Answers

Question 1

Which supplier category normally combines high business impact with high supply risk?

A. Non-critical

B. Leverage

C. Bottleneck

D. Strategic

Correct Answer: D. Strategic

Question 2

In a weighted supplier score, what condition must the weights satisfy?

A. They must all be equal

B. They must sum to 1

C. They must be greater than 1

D. They must be measured in currency

Correct Answer: B. They must sum to 1

Question 3

A disruption has probability 0.25 and impact $200,000. What is its expected loss?

A. $50,000

B. $80,000

C. $200,025

D. $800,000

Correct Answer: A. $50,000

Question 4

Which activity is most directly associated with supplier onboarding?

A. Verifying legal registration and banking information

B. Increasing finished-goods inventory automatically

C. Replacing all strategic suppliers

D. Removing quality inspections

Correct Answer: A. Verifying legal registration and banking information

Question 5

Why should OTIF definitions specify the date basis?

A. To ensure all suppliers use the same currency

B. Because performance against the requested date differs from performance against a later confirmed date

C. To eliminate the need for receipts

D. Because dates cannot be stored in ERP systems

Correct Answer: B. Because performance against the requested date differs from performance against a later confirmed date

Question 6

Which is an example of supplier development?

A. Joint root-cause analysis and process-capability improvement

B. Deleting overdue corrective actions

C. Ignoring sub-tier suppliers

D. Paying every supplier earlier regardless of performance

Correct Answer: A. Joint root-cause analysis and process-capability improvement

Question 7

What is a major limitation of using expected loss alone for risk decisions?

A. It cannot include probability

B. It always overestimates catastrophic risk

C. It may conceal low-probability events with severe safety or strategic consequences

D. It can be used only for inventory calculations

Correct Answer: C. It may conceal low-probability events with severe safety or strategic consequences

Question 8

Which control best reflects the principle of least privilege?

A. Giving every supplier administrator access

B. Allowing users only the data and actions required for their roles

C. Sharing all forecasts publicly

D. Disabling access reviews

Correct Answer: B. Allowing users only the data and actions required for their roles

Question 9

What is the principal purpose of a supplier scorecard?

A. To replace all supplier discussions

B. To translate agreed expectations into observable performance measures

C. To guarantee that the lowest-price supplier is selected

D. To eliminate the need for contracts

Correct Answer: B. To translate agreed expectations into observable performance measures

Question 10

Which statement about AI in supplier risk management is most appropriate?

A. AI recommendations never require human review

B. Historical data guarantee accurate predictions during novel crises

C. AI can prioritise investigation but requires validation, explainability and accountability

D. AI removes the need for data governance

Correct Answer: C. AI can prioritise investigation but requires validation, explainability and accountability

Digital Materials Management & ERP Systems
Chapter 6 of 15