Harley-Davidson Motor Co.: Enterprise Software Selection Custom Case Solution & Analysis

1. Evidence Brief

Financial Metrics

• Revenue Growth: 15 percent annual increase through the mid-1990s.
• Market Performance: Demand consistently exceeded supply; production capacity lagged behind consumer interest.
• Project Scope: Estimated investment for enterprise software exceeded 30 million dollars.
• Inventory Management: Legacy systems prevented real-time tracking of parts, leading to excess safety stock and capital tie-up.

Operational Facts

• Legacy Infrastructure: Over 300 disparate, non-integrated systems across departments.
• Data Integrity: Sales, Finance, and Manufacturing utilized separate databases, resulting in conflicting reports for the same metrics.
• Procurement Process: Purchasing was decentralized, preventing the company from negotiating volume discounts with shared suppliers.
• IT/Business Alignment: The selection process utilized a Siamese leadership model, pairing a business executive (Garry Berryman) with an IS leader (Dave Zeiger).

Stakeholder Positions

• Garry Berryman (VP Purchasing): Advocated for a solution that forced process discipline and supplier consolidation.
• Dave Zeiger (IS Director): Focused on technical scalability and reducing the maintenance burden of homegrown code.
• Functional Managers: Expressed concern regarding the loss of unique Harley-style workflows and autonomy.
• Executive Leadership: Demanded a solution that supported rapid growth without disrupting the current production of 125,000 plus motorcycles annually.

Information Gaps

• Total Cost of Ownership: The case lacks detailed five-year maintenance and consulting fee projections.
• Customization Limits: Specific technical boundaries for modifying the software to fit the York or Tomahawk plant requirements are not defined.
• Vendor Financial Health: Long-term stability metrics for the finalists during the late 90s market volatility are omitted.

2. Strategic Analysis

Core Strategic Question

• Should Harley-Davidson prioritize a rigid, process-driven software package to force organizational discipline, or a flexible technology platform that adapts to its unique, consensus-based culture?

Structural Analysis

The Value Chain analysis reveals that the primary bottleneck is the lack of information flow between inbound logistics and operations. The current system is a collection of silos that cannot support the 15 percent growth rate. Porter’s Five Forces indicates that while buyer power is low due to brand loyalty, supplier power is higher than necessary because decentralized purchasing prevents volume-based negotiation. The enterprise software must transform Purchasing from a clerical function into a strategic asset.

Strategic Options

Option 1: SAP R/3 Implementation (Standardization)

• Rationale: SAP offers the most durable manufacturing modules and forces the adoption of industry-standard processes.
• Trade-offs: High cultural resistance due to the rigid nature of the software; requires significant change management.
• Resource Requirements: Heavy reliance on external consultants and a dedicated internal team for a multi-year rollout.

Option 2: Oracle Applications (Flexibility)

• Rationale: Oracle provides a more flexible architecture that can be tailored to existing Harley-Davidson workflows.
• Trade-offs: Risk of over-customization, which increases long-term maintenance costs and complicates future upgrades.
• Resource Requirements: High internal developer involvement to manage the customization layers.

Option 3: Best-of-Breed Hybrid (Delayed Integration)

• Rationale: Select the best individual packages for finance, HR, and manufacturing.
• Trade-offs: Rejected due to the extreme complexity of building and maintaining interfaces between different vendors.

Preliminary Recommendation

Select SAP R/3. The primary objective is not to digitize existing chaos but to replace it with disciplined, scalable processes. SAP’s rigidity is a feature, not a bug, for an organization that has outgrown its informal roots. The financial risk of a failed integration is lower than the operational risk of continuing with fragmented data.

3. Implementation Roadmap

Critical Path

• Phase 1 (Months 1-3): Finalize contract and establish the Joint Project Office. Define the global template for manufacturing processes.
• Phase 2 (Months 4-9): Pilot implementation at a single site (e.g., Tomahawk). This serves as the proof of concept for the Harley-style adaptation.
• Phase 3 (Months 10-18): Sequential rollout to York and Milwaukee facilities. Data migration must occur during planned maintenance shutdowns.

Key Constraints

• Organizational Absorptive Capacity: The consensus-driven culture will slow down the thousands of micro-decisions required during configuration.
• Technical Debt: Extracting clean data from 300 legacy systems is the most likely source of schedule slippage.

Risk-Adjusted Implementation Strategy

The plan assumes a 20 percent buffer in the timeline for the pilot phase. If the pilot exceeds the nine-month window, the enterprise rollout must be paused to prevent compounding errors. Success depends on the Siamese leaders remaining empowered to overrule functional heads who attempt to revert to legacy processes.

4. Executive Review and BLUF

BLUF

Select SAP R/3 immediately. Harley-Davidson’s 15 percent growth is unsustainable under the current fragmented IT infrastructure. The company must transition from a collection of independent plants to a unified enterprise. SAP provides the necessary structural discipline to centralize purchasing and synchronize manufacturing. While the cultural shift is significant, the cost of maintaining 300 legacy systems poses a greater threat to long-term margins. Implementation should follow a phased pilot-to-enterprise approach to mitigate operational friction.

Dangerous Assumption

The most consequential unchallenged premise is that functional managers will actually adopt standardized processes once the software is live. The analysis assumes the Siamese leadership model can overcome decades of localized autonomy without causing a middle-management revolt.

Unaddressed Risks

Unconsidered Alternative

The team did not fully evaluate a phased outsourcing of the manufacturing process itself. If capacity is the problem, moving to a contract manufacturing model for certain components would reduce the immediate need for a massive internal ERP overhaul, allowing for a slower, less risky software transition.

MECE Analysis Verdict

APPROVED FOR LEADERSHIP REVIEW

• Mutually Exclusive: The options clearly distinguish between standardization and flexibility.
• Collectively Exhaustive: All viable vendor paths and the do-nothing risk have been addressed.