Harley-Davidson Motor Company: Enterprise Software Selection
1. Consider Exhibit 10 on page 22 of the case; does it include the factors you consider most important in the selection process? Which factors would you be inclined to weight most heavily?
Quantitative Criteria
1. Design and Foundation
2. Request Definition
3. Documentation
4. Receiving
5. Supply Management
6. Project Tracking
7. Miscellaneous
8. Interfaces
9. Training
10. Other
Yes. It does include the factors which we consider most important.
Out of these factors, Supply Management, Project Tracking and Receiving are the core functionalities which are anyway required. Design and Foundation, Documentation and Request Definition are the supporting requirements which add value and enhance the quality of service or functionality.
Thus our group would like to divide the whole list of quantitative factors into 4 separate groups:
Group 1: Core Functionality
Receiving, Supply Management, Project Tracking
Group 2: Supporting Functionality
Training, Interfaces
Group 3: Value adding functionalities
Documentation, Design and Foundation, Request Definition
Group 4: Others
Miscellaneous, Other
Enhancement
We would also like to add some more factors viz:
Group 1: Core Functionality
Receiving, Supply Management, Project Tracking, Customer Relationships, Business Intelligence
Group 2: Supporting Functionality
Training, Interfaces, Real time support
Group 3: Value adding functionalities
Documentation, Design and Foundation, Request Definition, User Friendliness, Knowledge Management
Group 4: Others
Miscellaneous, Other
Qualitative Criteria
1. Long term relationship potential
2. Research and Development
3. Training approach
4. Implementation/Education/Change Management Methodology
5. Understanding Harley?s requirement
6. Enabling the SMS
7. Out of the box fit
8. Financial Viability
9. Cost
10. Technical Support Offerings
11. Overall functionality
12. Number of partners included in Solution Proposal
13. Architecture Compatibility
14.
Quantitative Criteria
1. Design and Foundation
2. Request Definition
3. Documentation
4. Receiving
5. Supply Management
6. Project Tracking
7. Miscellaneous
8. Interfaces
9. Training
10. Other
Yes. It does include the factors which we consider most important.
Out of these factors, Supply Management, Project Tracking and Receiving are the core functionalities which are anyway required. Design and Foundation, Documentation and Request Definition are the supporting requirements which add value and enhance the quality of service or functionality.
Thus our group would like to divide the whole list of quantitative factors into 4 separate groups:
Group 1: Core Functionality
Receiving, Supply Management, Project Tracking
Group 2: Supporting Functionality
Training, Interfaces
Group 3: Value adding functionalities
Documentation, Design and Foundation, Request Definition
Group 4: Others
Miscellaneous, Other
Enhancement
We would also like to add some more factors viz:
Group 1: Core Functionality
Receiving, Supply Management, Project Tracking, Customer Relationships, Business Intelligence
Group 2: Supporting Functionality
Training, Interfaces, Real time support
Group 3: Value adding functionalities
Documentation, Design and Foundation, Request Definition, User Friendliness, Knowledge Management
Group 4: Others
Miscellaneous, Other
Qualitative Criteria
1. Long term relationship potential
2. Research and Development
3. Training approach
4. Implementation/Education/Change Management Methodology
5. Understanding Harley?s requirement
6. Enabling the SMS
7. Out of the box fit
8. Financial Viability
9. Cost
10. Technical Support Offerings
11. Overall functionality
12. Number of partners included in Solution Proposal
13. Architecture Compatibility
14.