Keda's SAP Implementation Custom Case Solution & Analysis

1. Evidence Brief (Case Researcher)

Financial Metrics

• Keda Ceramics Revenue (2009): 1.63 billion RMB (Exhibit 1).
• Net Profit (2009): 146 million RMB (Exhibit 1).
• IT Budget: Historically kept below 1% of revenue; SAP project budget was 20 million RMB (Para 14).
• Cost of implementation failure: Estimated 20 million RMB sunk cost plus potential operational paralysis (Para 22).

Operational Facts

• Business Model: High-volume manufacturing of building materials; decentralized management structure (Para 3).
• Implementation Scope: SAP ERP rollout across 12 subsidiaries (Para 12).
• Timeline: Pilot project began in early 2008; full rollout targeted for 2010 (Para 15).
• Technology Context: Transitioning from legacy, fragmented systems to a unified SAP environment (Para 10).

Stakeholder Positions

• Bian Cheng (Chairman): Pushing for centralized control and standardized data to manage rapid expansion (Para 5).
• Subsidiary Managers: Resisting standardization; prefer autonomy and legacy systems they control (Para 18).
• SAP Consultants: Advocating for strict process adherence; viewed by staff as rigid and disconnected from local realities (Para 19).

Information Gaps

• Specific cost-benefit breakdown of the SAP system post-implementation.
• Quantifiable impact of system downtime on daily production output.
• Specific turnover rates of IT staff during the implementation phase.

2. Strategic Analysis (Strategic Analyst)

Core Strategic Question

Can Keda enforce top-down ERP standardization across autonomous subsidiaries without destroying the operational agility that fueled its growth?

Structural Analysis (Value Chain & Change Management)

• Fragmented Value Chain: Keda operates as a collection of fiefdoms. The lack of standardized data prevents the Chairman from seeing true enterprise-wide margin performance.
• Cultural Resistance: The primary bottleneck is not the software; it is the loss of power by subsidiary managers who utilized legacy systems to maintain operational opacity.

Strategic Options

• Option 1: Hard Mandate. Enforce SAP adoption with personnel changes. Trade-off: High risk of immediate operational disruption; Resource Requirement: Strong executive backing and HR bandwidth for management replacement.
• Option 2: Hybrid Integration. Standardize financial reporting only, leaving operational modules to subsidiaries. Trade-off: Lower immediate impact; Resource Requirement: Moderate; requires building middleware to bridge legacy systems.
• Option 3: Phased Pilot-Led Expansion. Restart with a single, high-performing subsidiary to prove ROI. Trade-off: Slows down corporate consolidation; Resource Requirement: High patience, low immediate disruption.

Preliminary Recommendation

Proceed with Option 1 but link SAP adoption to subsidiary manager KPIs. The status quo is untenable given the scale of the firm.

3. Implementation Roadmap (Operations Specialist)

Critical Path

1. Data Cleansing: Standardize chart of accounts across all 12 units (Month 1).
2. KPI Realignment: Modify subsidiary manager bonus structures to include system usage targets (Month 2).
3. Super-User Training: Deploy a task force of internal high-performers to assist local teams (Month 3).

Key Constraints

• Talent Gap: Lack of internal IT personnel capable of managing the SAP environment.
• Data Integrity: Dirty data from legacy systems will break the new ERP; manual intervention is mandatory.

Risk-Adjusted Implementation

Assume 30% project delay. Implement a shadow-reporting period where both legacy and SAP systems run in parallel for 60 days to ensure continuity.

4. Executive Review and BLUF (Executive Critic)

BLUF

Keda's SAP implementation is failing because management treated a political transformation as a software upgrade. The Chairman attempts to centralize control over a decentralized culture without addressing the loss of autonomy for subsidiary managers. The current path leads to a 20 million RMB write-down. The project must pivot from a technical rollout to a governance redesign. If subsidiary managers do not perceive a benefit to the new system, they will sabotage it. Stop the rollout. Re-align incentives first. Standardize reporting, then processes. If the culture cannot be shifted, the software is irrelevant.

Dangerous Assumption

The assumption that technical standardization inherently leads to operational efficiency in a decentralized manufacturing firm.

Unaddressed Risks

• Operational Sabotage: Subsidiary managers intentionally providing inaccurate data to maintain operational control (High probability, catastrophic consequence).
• System Failure: The SAP environment is too complex for the current internal skill set (Medium probability, high consequence).

Unconsidered Alternative

The company should consider a Tier-2 ERP solution for smaller subsidiaries that does not require the heavy overhead of SAP, reserving the full suite only for the three largest, most critical units.

Verdict: REQUIRES REVISION. The plan ignores the political economy of the subsidiary structure. Re-evaluate the cost of a partial SAP implementation versus the current all-or-nothing approach.