ERP Strategy, Business Case and System Selection

Introduction

Enterprise resource planning (ERP) investment is not primarily a software-purchasing decision. It is a strategic operating-model decision involving processes, data, governance, technology, people, suppliers, and organizational change. An ERP system can integrate finance, procurement, manufacturing, sales, inventory, logistics, human resources, maintenance, and analytics. However, integration alone does not create value. Value arises when the organization uses integrated information and standardized processes to improve decisions, reduce waste, strengthen control, and execute its operating strategy.

ERP projects are therefore difficult to justify and select. Their benefits may be distributed across departments, while costs and disruption are concentrated during implementation. Benefits may also be uncertain, delayed, or dependent on process redesign. A rigorous business case must distinguish measurable cash benefits from strategic and enabling benefits, account for total cost of ownership, assess organizational readiness, and recognize risk and uncertainty.

This chapter develops a structured approach to ERP strategy, business-case development, and system selection. It addresses deployment and sourcing choices, vendor evaluation, governance, ethical issues, and contemporary developments such as cloud ERP, composable architecture, embedded analytics, and artificial intelligence.

Learning Objectives

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

1. Align ERP investment with competitive and operating strategy.
2. Construct an ERP business case using total cost, benefits, risk, and readiness analysis.
3. Apply discounted cash flow, payback, and sensitivity analysis appropriately.
4. Develop transparent ERP selection criteria and evaluate vendors and implementation partners.
5. Compare on-premises, hosted, public-cloud, private-cloud, and hybrid deployment models.
6. Assess sourcing alternatives, governance requirements, ethical risks, and implementation readiness.
7. Critically evaluate ERP proposals rather than treating vendor claims as evidence.

1. ERP as a Strategic Operating-Model Choice

Strategy describes how an organization creates and captures value. Operations strategy translates that intent into choices about capacity, quality, speed, dependability, flexibility, cost, technology, and supply-network design. ERP should support these choices rather than determine them accidentally.

For example, a manufacturer competing on low cost may need disciplined planning, high inventory accuracy, efficient procurement, and standardized production reporting. A configure-to-order manufacturer may instead require product configurability, rapid quotation, engineering-change control, and reliable available-to-promise information. A professional-services organization may prioritize project accounting, resource scheduling, utilization analysis, and revenue recognition. The appropriate ERP configuration differs in each case.

A useful alignment chain is:

Business strategy → operating capabilities → required processes and information → ERP capabilities → measurable outcomes.

The chain prevents a common error: selecting a system because it contains a long list of features. Features matter only when they support required capabilities and produce outcomes valued by customers, owners, regulators, or employees.

Strategic alignment questions

A strategy-led ERP assessment should ask:

• Which capabilities most strongly support the organization’s competitive position?
• Which processes create unacceptable cost, delay, risk, or customer dissatisfaction?
• Where is common data essential for cross-functional decisions?
• Which processes should be standardized globally, and which require local variation?
• Which capabilities are differentiating and must remain flexible?
• Which activities are routine and suitable for automation or outsourcing?
• What regulatory, audit, cybersecurity, and data-residency obligations apply?

ERP should not automatically standardize every process. Standardization is beneficial when variation adds no customer or regulatory value. It can be harmful when it removes a capability that differentiates the firm or satisfies a legitimate local requirement.

2. The ERP Investment Business Case

The business case is a decision document, not a sales brochure. It explains why investment is needed, what alternatives were considered, how value will be created, what resources are required, and how uncertainty will be managed. A strong business case normally contains:

1. strategic context and problem definition;
2. baseline performance and cost;
3. options, including the option of doing nothing;
4. expected benefits and their owners;
5. total cost of ownership;
6. risk, dependency, and readiness analysis;
7. implementation roadmap and governance;
8. financial and non-financial evaluation; and
9. recommendation with decision gates.

2.1 Baseline before benefits

Benefits should be estimated against a credible baseline. Relevant baseline measures may include:

• inventory accuracy and inventory value;
• forecast error and schedule adherence;
• purchase-order cycle time;
• order-to-cash duration;
• invoice-processing cost;
• month-end closing duration;
• on-time delivery;
• customer-service response time;
• manual journal volume;
• data-quality defects;
• system-support cost; and
• audit findings.

A claim such as “ERP will reduce inventory” is incomplete. The analysis should identify the mechanism, owner, time frame, baseline, target, and measurement method. For example, improved planning may reduce safety stock, but only if lead times, demand data, replenishment policies, supplier performance, and planner behavior are also addressed.

2.2 Total cost of ownership

Total cost of ownership (TCO) captures costs across the system life cycle, not merely the initial license price. A practical model includes:

• software subscription or license fees;
• implementation and configuration;
• data cleansing and migration;
• integration and interface development;
• testing and quality assurance;
• project staffing and backfill;
• training and change management;
• infrastructure, networks, and devices;
• cybersecurity and identity management;
• support, upgrades, and enhancements;
• external consultants and managed services;
• compliance, audit, and business-continuity costs; and
• decommissioning and exit costs.

For a planning horizon of T years, an undiscounted TCO can be represented as:

where C₀ is initial cost and Cₜ is cost incurred in year t. This measure is useful for operational budgeting but does not reflect the time value of money. For investment comparison, discounted costs are more appropriate:

Here, r is the annual discount rate, expressed as a decimal, and T is the number of years. The formula assumes costs occur at the end of each year; if major payments occur at other times, their timing should be modeled accordingly.

Cloud subscriptions may convert capital expenditure into operating expenditure, but they do not eliminate cost. They may introduce recurring subscription escalation, integration charges, premium environments, data-extraction fees, and dependence on vendor release cycles.

2.3 Benefits classification

Benefits should be classified because different benefits require different evidence and ownership.

A productivity improvement is not automatically a cash saving. If employees are redeployed to higher-value work, the benefit is real but should be labeled as capacity or opportunity benefit rather than immediate cost reduction. Benefit owners should be named before approval.

2.4 Financial evaluation

A project’s net cash flow in year t is benefits minus costs. The net present value (NPV) is:

CFₜ is the net cash flow in period t, r is the discount rate, and t = 0 represents the initial investment. A positive NPV indicates that the expected discounted benefits exceed discounted costs at the selected rate, assuming the estimates and risk treatment are credible.

Return on investment (ROI) is often expressed as:

ROI is simple and communicable, but it may ignore timing and risk. Payback period measures how long cumulative net cash flow takes to recover the initial investment. It is useful for liquidity discussions but should not replace NPV because it ignores benefits after payback and usually ignores discounting.

#### Worked example

An illustrative ERP program requires an initial investment of $1.20 million. It is expected to generate net cash benefits of $0.45 million in year 1, $0.60 million in year 2, and $0.70 million in year 3. Assume a discount rate of 10% and no terminal value.

The NPV is:

The present values are approximately $0.409 million, $0.496 million, and $0.526 million. Therefore:

The project has an estimated positive NPV of approximately $231,000. Simple cumulative cash flow becomes positive during year 3: after year 2, cumulative cash flow is −$0.15 million; after receiving $0.70 million in year 3, the fraction of year required to recover it is approximately $0.15 ÷ $0.70 = 0.214. The simple payback period is therefore about 2.21 years. The calculation assumes benefits are evenly received during year 3 and excludes tax, inflation, residual value, and implementation delay; those factors should be included in a formal investment appraisal.

2.5 Risk and uncertainty

ERP estimates contain uncertainty about implementation duration, adoption, data quality, integration complexity, benefit realization, vendor viability, and future pricing. Scenario analysis is more credible than a single-point forecast. At minimum, model conservative, expected, and optimistic cases.

Sensitivity analysis changes one assumption at a time to identify influential variables. For example, NPV may be especially sensitive to subscription escalation, inventory reduction, implementation delay, or the proportion of users adopting a new process. Scenario analysis changes several related assumptions together and is more suitable when variables interact.

Risk-adjusted evaluation should not hide uncertainty inside arbitrary benefit discounts. Instead, document assumptions, probability where defensible, mitigation actions, triggers, and accountable owners. Decision gates can authorize discovery, procurement, implementation, and deployment separately rather than committing the entire program at once.

3. Organizational Readiness and Change Capacity

A technically suitable ERP can fail when the organization is not ready to adopt it. Readiness includes leadership alignment, process ownership, data quality, resource availability, decision rights, digital capability, labor relations, and willingness to change.

Important readiness dimensions include:

• Leadership: visible sponsorship and rapid resolution of cross-functional conflicts.
• Governance: clear authority for scope, design principles, data ownership, and exceptions.
• Process maturity: documented processes, measurable performance, and willingness to remove unnecessary variation.
• Data readiness: defined master-data ownership, quality rules, cleansing resources, and migration accountability.
• People capacity: availability of subject-matter experts without damaging daily operations.
• Change readiness: communication, training, local engagement, and incentives aligned with adoption.
• Technical readiness: network reliability, identity architecture, integration capability, and cybersecurity controls.

A readiness assessment should produce evidence, not only a color-coded score. A “green” rating without documented criteria creates false confidence. Readiness gaps should be treated as work packages in the business case.

4. Developing ERP Selection Criteria

Selection criteria translate strategy and requirements into a transparent comparison. Requirements should be prioritized rather than listed indiscriminately.

A useful classification is:

• Must-have: failure would make the solution unacceptable.
• Should-have: important, but a controlled workaround may exist.
• Could-have: desirable if cost and complexity are reasonable.
• Won’t-have now: explicitly excluded from the current scope.

Requirements should be expressed as outcomes or testable capabilities. “The system must support reliable credit control and automated dunning” is stronger than “the system must have a finance module.” Requirements should distinguish standard functionality, configuration, customization, integration, and manual workarounds.

Weighted scoring

A weighted decision matrix can structure evaluation. For criterion i, let wᵢ be its normalized weight and sᵢⱼ be vendor j’s score. The weighted score for vendor j is:

Weights should sum to 1, or 100%. Scores must use a defined scale, such as 0 to 5, where each point has a documented meaning. The matrix is a decision aid, not a substitute for judgment. A vendor with a high total score may still fail a mandatory requirement, create unacceptable security exposure, or depend on an unrealistic customization program.

The weights must be adapted to the organization. A regulated bank, a project-based engineering firm, and a global manufacturer should not use identical criteria.

Evidence-based evaluation

Vendor demonstrations should use realistic scenarios and the organization’s own data structures. Scripted demonstrations can conceal limitations. Evaluation should include:

• process-based demonstrations from order to cash, procure to pay, plan to produce, and record to report;
• integration and data-migration prototypes;
• security-role and segregation-of-duties tests;
• performance and scalability evidence;
• reference checks with organizations of similar complexity;
• total-cost scenarios over the intended contract period;
• implementation-team qualifications and availability; and
• explicit identification of functions requiring customization or third-party products.

References should be interviewed independently, with questions about actual implementation duration, unresolved defects, adoption, upgrade experience, hidden costs, and vendor responsiveness.

5. Vendor, Deployment, and Sourcing Alternatives

5.1 Deployment models

On-premises ERP provides substantial control over infrastructure, release timing, and data location, but requires capital investment, specialist skills, hardware lifecycle management, and responsibility for resilience and upgrades.

Hosted or managed private-cloud ERP transfers infrastructure operations to a provider while retaining a more dedicated environment. It may offer control and tailored arrangements but can be expensive and may not deliver the innovation pace of public cloud.

Public-cloud ERP typically provides subscription access, vendor-managed infrastructure, frequent releases, standardized architecture, and elastic capacity. It can reduce infrastructure responsibility but raises questions about data residency, integration, customization limits, service dependency, exit, and continuous change management.

Hybrid ERP combines environments. It may be necessary during transition or where regulatory, latency, or specialized-system requirements exist. However, hybrid architecture increases integration, identity, data-governance, and support complexity.

The correct question is not “Which model is modern?” but “Which model provides the required capabilities and control at acceptable risk and lifetime cost?”

5.2 Sourcing choices

Organizations may implement internally, use a systems integrator, adopt a managed service, outsource selected processes, or combine these approaches. Sourcing decisions should consider strategic importance, process codifiability, internal capability, information sensitivity, switching cost, and the organization’s ability to manage suppliers.

A provider should not own decisions that belong to the client, such as operating-model design, data ownership, risk appetite, or acceptance criteria. Excessive dependence on one integrator can create knowledge loss and switching barriers. Contracts should address service levels, security obligations, audit rights, data portability, intellectual property, subcontractors, price changes, upgrade responsibilities, termination assistance, and exit testing.

6. Governance, Ethics, and Regulatory Considerations

ERP concentrates organizational power and information. Governance must therefore extend beyond project scheduling.

Key controls include:

• role-based access and least privilege;
• segregation of duties in purchasing, payments, payroll, and financial reporting;
• approval workflows with documented authority limits;
• immutable or monitored audit trails;
• master-data change controls;
• privacy classification and retention rules;
• backup, recovery, and disaster-recovery testing;
• vulnerability management and incident response;
• third-party risk assessment; and
• compliance with applicable accounting, tax, labor, privacy, records, and sector regulations.

Ethical issues include employee monitoring, algorithmic profiling, opaque automated decisions, unequal access to training, forced standardization of local practices, and the use of personal data beyond its legitimate purpose. AI-enabled ERP features may recommend suppliers, forecast demand, detect anomalies, or automate invoice handling. Their use requires data-quality controls, explainability appropriate to the decision, human oversight, bias testing, access control, and clear accountability when recommendations are wrong.

A vendor’s claim that an AI feature is “intelligent” is not evidence of business value. Evaluation should ask what data the feature uses, how it was validated, how errors are detected, whether customer data is used for model training, where processing occurs, and how users can challenge or override outputs.

7. Implementation Strategy and Decision Gates

Selection and implementation should be treated as a connected but staged portfolio of decisions. A typical sequence is:

1. establish strategic case and executive sponsorship;
2. document baseline processes, pain points, and data risks;
3. define target principles and requirements;
4. conduct market analysis and shortlist suppliers;
5. issue a structured request for proposal;
6. evaluate demonstrations, prototypes, references, and commercials;
7. negotiate contract and implementation plan;
8. design, configure, integrate, and cleanse data;
9. test end-to-end processes and controls;
10. train users and rehearse cutover;
11. deploy with stabilization support; and
12. measure benefits and retire obsolete systems.

Decision gates should have entry and exit criteria. For example, a go-live gate may require critical defects below a defined threshold, successful financial reconciliation, validated migration, tested recovery procedures, trained role populations, signed business acceptance, and an operational support model.

Implementation approaches include a big-bang deployment, phased rollout, pilot, or a minimum viable template followed by expansion. Big-bang deployment can reduce prolonged coexistence but concentrates risk. Phased deployment can reduce exposure and enable learning but may require temporary interfaces and duplicate processes. The choice should reflect organizational capacity, process coupling, regulatory constraints, and the quality of preparation.

Illustrative Case: Northstar Components

Background

Northstar Components is a fictional mid-sized manufacturer operating three plants and selling through distributors in four countries. It uses separate finance, purchasing, production-planning, warehouse, and sales systems. Each plant maintains its own item codes and spreadsheets.

Problem

Management reports declining on-time delivery, excess safety stock, slow month-end closing, and inconsistent profitability information. A vendor proposes a cloud ERP with rapid implementation and claims a 20% inventory reduction.

Analysis

The steering group first established baselines: inventory was $18 million, inventory-record accuracy was 82%, month-end close required 15 working days, and on-time delivery was 86%. Interviews showed that planners distrusted system forecasts because supplier lead times and item attributes were unreliable. The problem was therefore not only software fragmentation; it also involved data ownership, planning discipline, and inconsistent processes.

The team defined strategic priorities: dependable delivery, controlled working capital, and common profitability reporting. It identified mandatory capabilities including multi-site planning, governed item and supplier masters, available-to-promise visibility, intercompany accounting, role-based controls, and integration with a specialized manufacturing-execution system.

Three options were compared: retain and improve existing systems, implement a cloud ERP in phases, or implement a highly customized private environment. The cloud option had the strongest fit, but its business case was revised. Instead of accepting the vendor’s 20% claim, the team modeled a conservative 8% inventory reduction after data remediation and policy redesign, with benefits beginning after stabilization.

Approach and solution

Northstar established data owners, created a global item-code standard, and selected one plant as a pilot. The contract included price protections, data-extraction rights, security obligations, implementation acceptance criteria, and named integration responsibilities. Benefits were assigned to the supply-chain, finance, and plant managers rather than to the IT department alone.

The rollout used a common template with justified local variations. A readiness gate required inventory accuracy above 97%, completed role testing, reconciled opening balances, and evidence that planners could execute the new planning cycle. Training used realistic production and purchasing scenarios instead of generic software demonstrations.

Outcome

The pilot initially exposed poor bills of material and inaccurate supplier calendars, delaying deployment by six weeks. After correction, Northstar achieved a shorter close, improved inventory visibility, and higher schedule adherence. The inventory reduction was 6% in the first year, below the original vendor claim but sufficient to support the revised business case. The case illustrates why benefit ownership, baseline measurement, data preparation, and staged decision gates are more reliable than optimistic feature-based justification.

Learning points

1. ERP value depends on operating discipline as well as technology.
2. Vendor benefit claims must be converted into organization-specific assumptions.
3. Data governance is a business responsibility.
4. A pilot can reveal risks that procurement documents conceal.
5. Contractual and exit protections are strategic controls, not legal formalities.

Challenges and Limitations of ERP Evaluation

ERP evaluation is affected by incomplete information, political behavior, vendor-controlled demonstrations, changing technology, and uncertainty about future organizational strategy. Weighted matrices can create an appearance of precision even when scores are subjective. Financial models can overstate benefits by counting the same improvement in several departments. TCO comparisons may be distorted when suppliers use different implementation assumptions or exclude integration and change-management work.

ERP also creates standardization trade-offs. A common template can improve control and comparability, but excessive centralization may undermine local responsiveness. Cloud releases can provide innovation but increase the need for continuous testing and release governance. Customization can preserve competitive capability but increase cost, technical debt, and upgrade difficulty. Conversely, forcing every process into standard functionality can produce hidden workarounds and user resistance.

Managers should therefore combine quantitative analysis with process evidence, user research, technical assurance, independent reference checks, and explicit judgment about uncertainty.

Contemporary Developments and Best Practices

Current ERP programs increasingly involve cloud subscriptions, application programming interfaces, event-driven integration, process mining, low-code extensions, mobile workflows, embedded analytics, and AI-assisted automation. These developments can improve responsiveness but also create fragmented ecosystems and unclear accountability.

Best practices include:

• begin with strategic capabilities and measurable outcomes;
• include the do-nothing and improvement-of-existing-systems options;
• separate mandatory requirements from preferences;
• compare lifetime cost rather than license price;
• model conservative, expected, and optimistic scenarios;
• validate benefits with process owners and finance;
• use realistic demonstrations and proof-of-concept testing;
• protect data portability, security, and exit rights;
• establish master-data ownership before migration;
• design controls and privacy into the target model;
• treat adoption and training as core work, not optional support;
• use independent assurance for major risks; and
• measure benefits after go-live against the approved baseline.

Chapter Summary

ERP investment should be aligned with business strategy, operating capabilities, process requirements, and measurable outcomes. A credible business case defines the baseline, compares alternatives, identifies benefit owners, and includes the full life-cycle cost of software, implementation, data, integration, people, support, compliance, and exit. NPV, ROI, and payback provide useful but different perspectives; financial results must be supplemented with risk, readiness, strategic capability, and control analysis.

System selection requires prioritized, testable criteria and evidence from realistic demonstrations, prototypes, references, security assessments, and commercial analysis. Deployment and sourcing choices should be evaluated according to lifetime value, control, capability, integration complexity, and dependency risk rather than fashion. Governance must address access, segregation of duties, privacy, cybersecurity, data ownership, supplier accountability, and AI oversight. Finally, ERP success depends on process discipline, organizational readiness, change leadership, and post-implementation benefit realization as much as on software functionality.

Key Terms

Business case: Structured justification for an investment, including alternatives, costs, benefits, risks, and implementation requirements.

Benefit owner: Person accountable for realizing and measuring a defined ERP benefit.

Cloud ERP: ERP software delivered through cloud infrastructure, commonly through a subscription model.

Deployment model: The way ERP software and infrastructure are hosted and operated.

Discount rate: Rate used to convert future cash flows into present values.

ERP: Integrated information system supporting multiple organizational functions and shared data.

Exit rights: Contractual and technical rights enabling an organization to change or leave a provider.

Master data: Core entities such as customers, suppliers, materials, products, employees, and accounts.

Net present value: Present value of benefits and costs, including the initial investment.

Operating model: Design of processes, responsibilities, governance, technology, and capabilities used to execute strategy.

Payback period: Time required for cumulative cash flows to recover an initial investment.

Readiness assessment: Evidence-based evaluation of an organization’s ability to implement and adopt ERP.

Reference check: Independent inquiry into another customer’s actual experience with a vendor or integrator.

Segregation of duties: Control that separates incompatible responsibilities to reduce error or fraud.

Sourcing model: Arrangement for obtaining, implementing, operating, or supporting ERP capabilities.

Total cost of ownership: Full life-cycle cost of acquiring, implementing, operating, changing, and retiring ERP.

Weighted decision matrix: Evaluation method combining criterion weights and scored alternatives.

Working capital: Short-term resources tied up in operating assets and liabilities, including inventory and receivables.

Review Questions

Short Answer Questions

1. Why should ERP selection begin with operating strategy rather than software features?
2. List four components of ERP total cost of ownership.
3. What is the difference between a cashable benefit and a productivity benefit?
4. Why is data governance important before ERP migration?
5. Identify two risks associated with public-cloud ERP.

Long Answer Questions

1. Explain how an organization can align ERP capabilities with competitive priorities and operating-model design.
2. Compare NPV, ROI, and payback period as ERP investment measures, including the limitations of each.
3. Describe a rigorous process for developing ERP selection criteria and evaluating vendors.
4. Compare on-premises, public-cloud, and hybrid ERP deployment models.
5. Discuss the governance, ethical, privacy, and cybersecurity controls required for ERP.

Analytical / Application Questions

1. An organization has unreliable inventory records, inconsistent item codes, and poor planning performance. Develop a readiness assessment and recommend the first five actions before ERP implementation.
2. Construct a weighted ERP selection matrix for a regulated multinational organization. Justify the criteria, weights, scoring scale, and treatment of mandatory requirements.
3. A vendor promises a 20% reduction in inventory and a 30% reduction in administrative effort. Explain how you would validate these claims, model uncertainty, assign benefit ownership, and design post-go-live measurements.

Multiple Choice Questions with Answers

Question 1

Which statement best describes the strategic role of ERP?

A. ERP replaces the need for operating strategy.

B. ERP aligns integrated processes and information with operating capabilities.

C. ERP is primarily a hardware procurement decision.

D. ERP creates value automatically when all modules are installed.

Correct Answer: B. ERP aligns integrated processes and information with operating capabilities.

Question 2

Which item is normally included in total cost of ownership?

A. Only the initial software license

B. Only annual infrastructure depreciation

C. Implementation, migration, support, training, and exit costs

D. Only the vendor’s demonstration expenses

Correct Answer: C. Implementation, migration, support, training, and exit costs

Question 3

Using NPV, what is the principal purpose of applying a discount rate?

A. To increase all future cash flows

B. To convert future cash flows into present values

C. To remove implementation risk completely

D. To calculate the number of system users

Correct Answer: B. To convert future cash flows into present values

Question 4

In a weighted decision matrix, what should normally be true of all criterion weights?

A. They must sum to 1 or 100%.

B. They must all be equal.

C. They must be negative for cost criteria.

D. They must be based only on vendor recommendations.

Correct Answer: A. They must sum to 1 or 100%.

Question 5

Which is the strongest evidence for evaluating a vendor’s claimed capability?

A. A generic brochure

B. A scripted demonstration using only vendor data

C. A realistic proof of concept and independent customer references

D. The length of the vendor’s website

Correct Answer: C. A realistic proof of concept and independent customer references

Question 6

Why is a productivity benefit not automatically a cash saving?

A. Productivity cannot be measured.

B. Released capacity may be redeployed rather than removed from payroll.

C. Productivity benefits occur only in manufacturing.

D. Cash savings do not require benefit owners.

Correct Answer: B. Released capacity may be redeployed rather than removed from payroll.

Question 7

Which control is designed to prevent one person from initiating and approving the same payment?

A. Data compression

B. Segregation of duties

C. Load balancing

D. Version numbering

Correct Answer: B. Segregation of duties

Question 8

What is a major risk of excessive ERP customization?

A. It always eliminates integration requirements.

B. It can increase cost, technical debt, and upgrade difficulty.

C. It guarantees higher user adoption.

D. It removes the need for process ownership.

Correct Answer: B. It can increase cost, technical debt, and upgrade difficulty.

Question 9

In the Northstar Components case, why was the vendor’s 20% inventory-reduction claim revised?

A. The organization had no inventory.

B. The team replaced an unsupported claim with a conservative, evidence-based assumption.

C. Cloud ERP cannot affect inventory.

D. Inventory benefits are never measurable.

Correct Answer: B. The team replaced an unsupported claim with a conservative, evidence-based assumption.

Question 10

Which issue is especially important when evaluating AI-enabled ERP features?

A. Whether the user interface uses a particular color

B. Whether recommendations are explainable, governed, and subject to human oversight

C. Whether the vendor offers printed manuals

D. Whether all decisions can be fully automated

Correct Answer: B. Whether recommendations are explainable, governed, and subject to human oversight