Ariba Implementation at MED-X: Managing Earned Value Custom Case Solution & Analysis

1. Evidence Brief: Case Extraction

Financial Metrics

• Budget at Completion (BAC): 3,500,000 USD for the total Ariba implementation.
• Planned Value (PV) at Month 6: 1,750,000 USD (50 percent of the project duration).
• Earned Value (EV) at Month 6: 1,225,000 USD (35 percent of work physically completed).
• Actual Cost (AC) at Month 6: 2,100,000 USD.
• Schedule Performance Index (SPI): 0.70 (EV divided by PV).
• Cost Performance Index (CPI): 0.58 (EV divided by AC).
• Estimate at Completion (EAC): 6,034,482 USD based on current CPI (BAC divided by CPI).
• Variance at Completion (VAC): -2,534,482 USD (Projected overspend).

Operational Facts

• Project Scope: Implementation of SAP Ariba modules: Sourcing, Contracts, P2P (Procure-to-Pay), and Spend Analysis.
• Timeline: 12-month original duration; currently at the end of Month 6.
• Personnel: 12 dedicated internal IT staff, 8 procurement subject matter experts, and 5 external consultants.
• Infrastructure: Integration required with legacy SAP ERP and three disparate inventory management systems.
• Geography: MED-X operates across 14 manufacturing sites in North America and Europe.

Stakeholder Positions

• Chief Procurement Officer (CPO): Demands 100 percent spend visibility by year-end to meet board-mandated savings targets.
• Project Manager: Attributes delays to data cleansing issues and unexpected integration complexity with legacy systems.
• IT Director: Expresses concern over resource drain on other critical maintenance tasks.
• External Consultants: Maintain that the original timeline was aggressive given the state of MED-X master data.

Information Gaps

• Data Quality Audit: The case does not quantify the volume of dirty records in the legacy systems.
• Contractual Penalties: Absence of information regarding late-delivery penalties for the consulting firm.
• Change Management Budget: No specific allocation for user training or organizational transition is listed in the BAC.

2. Strategic Analysis

Core Strategic Question

MED-X must determine how to realign the Ariba implementation to stop the capital drain while securing the spend visibility required for organizational survival. The project is currently 30 percent behind schedule and 42 percent over budget.

Structural Analysis

• Value Chain Analysis: Procurement is the primary bottleneck. Inefficient sourcing and lack of contract compliance are eroding margins. Ariba is not a luxury; it is a structural necessity to maintain competitive pricing.
• Earned Value Management (EVM) Lens: The CPI of 0.58 indicates that for every dollar spent, MED-X only receives 58 cents of value. This is a systemic failure, not a temporary fluctuation. The SPI of 0.70 confirms the project will miss the CPO year-end deadline by at least five months if no intervention occurs.

Strategic Options

• Option 1: Scope Compression (The Descope). Eliminate the P2P module for the initial rollout. Focus exclusively on Sourcing and Spend Analysis.
  • Rationale: Delivers the highest ROI modules (Spend Visibility) fastest.
  • Trade-offs: Sacrifices long-term process automation; creates a fragmented user experience.
  • Resources: Requires immediate pivot of the IT team to data migration for sourcing only.
• Option 2: Resource Crashing (The Acceleration). Double the external consultant headcount to address the data cleansing backlog.
  • Rationale: Maintains full scope and original deadline.
  • Trade-offs: Increases AC significantly; risk of diminishing returns due to Brooks Law (adding manpower to a late software project makes it later).
  • Resources: Requires an immediate 1.5 million USD budget injection.
• Option 3: Re-baselined Phased Rollout (The Pilot). Move from a big bang approach to a site-by-site rollout starting with the most compliant manufacturing site.
  • Rationale: Reduces risk and allows the team to learn from implementation friction in a controlled environment.
  • Trade-offs: Extends the final completion date by 8 months.
  • Resources: Requires sustained commitment of internal staff for a longer duration.

Preliminary Recommendation

MED-X should execute Option 1 (Scope Compression). The primary driver for this project is spend visibility to achieve board-mandated savings. The P2P module is the most complex from an integration standpoint and is the source of the current AC/EV divergence. By deferring P2P, MED-X can stabilize the CPI and deliver the Spend Analysis module within a manageable variance of the original timeline.

3. Operations and Implementation Planner

Critical Path

The path to stabilization requires immediate cessation of P2P integration activities to focus on Master Data Governance (MDG). The sequenced workstreams are:

• Week 1-2: Formal Scope Deletion. Halt all P2P configuration. Re-assign 100 percent of integration consultants to the Spend Analysis data mapping.
• Week 3-6: Data Cleansing Sprint. Execute automated cleansing scripts on legacy vendor masters.
• Week 7-10: User Acceptance Testing (UAT) for Sourcing and Spend modules only.
• Week 11-12: Go-live for Phase 1 (Visibility).

Key Constraints

• Master Data Integrity: The project will fail if the underlying SAP data remains fragmented. This is the primary execution constraint.
• Internal Bandwidth: The 12 IT staff members are nearing burnout. Scope reduction is the only way to retain talent and focus.

Risk-Adjusted Implementation Strategy

The revised plan assumes a 20 percent buffer for UAT cycles. We will implement a frozen period for all other ERP updates during the Week 7-12 window. Contingency includes a fallback to manual data uploads for the top 20 percent of vendors (representing 80 percent of spend) if the automated integration fails during UAT.

4. Executive Review and BLUF

BLUF

The Ariba implementation is in a state of critical failure. With a CPI of 0.58 and SPI of 0.70, the project will exceed budget by 2.5 million USD and miss the deadline by 20 weeks. Current management is treating this as a reporting delay; it is a structural execution crisis. MED-X must immediately descope the Procure-to-Pay (P2P) module and pivot all resources to Spend Analysis and Sourcing. This ensures the CPO receives the visibility required for board-mandated savings while stopping the capital hemorrhage. Failure to descope now will result in a total project write-off by Month 10.

Dangerous Assumption

The analysis assumes that the data cleansing issues are technical rather than organizational. If the manufacturing sites refuse to adopt standardized vendor naming conventions, no amount of scope reduction or consultant spending will fix the Spend Analysis output. The project assumes site-level compliance that has not been tested.

Unaddressed Risks

• Vendor Resistance: High Probability / High Consequence. The transition to Ariba Sourcing requires vendors to use the Ariba Network. If key suppliers refuse, the projected savings will not materialize despite a successful software launch.
• Integration Fragility: Medium Probability / High Consequence. The legacy SAP ERP is aged. The middleware required to connect Ariba may cause system-wide latency, affecting manufacturing operations beyond procurement.

Unconsidered Alternative

The team did not consider a Third-Party Managed Service for Spend Analysis. Instead of implementing Ariba Spend Analysis, MED-X could export raw data to a specialist firm for a one-time cleansing and categorization. This would provide the CPO with the necessary data in 30 days at a fraction of the cost, allowing the Ariba project to be paused entirely until the organizational data strategy is matured.

Verdict