TimberJack Case Study

Both the Swedish and US team agreed on the issues leading to the business need of a new software package. The number one issue that pushed the decision to purchase a new software package was the instability of our existing system. The current system would not allow user modification without altering the source code; over the years the changing of source code has lead to frequent system failures. Also due to modification of the source code and system failures the data is not reliable for users. The current system is a Hewlett-Packard’s MM3000 and HP has notified our company to inform that they no longer will support the MM3000 model. Our teams identified a future need for dealer network, parts and service, and integrating manufacturing. Financial data was also at risk using the current system. Although both teams agree there was a need for a new software package; they did not agree on the manner and timeliness of the selection process. Sweden’s team was on a tighter schedule and needed a faster change because operations were effected tremendously. The Atlanta team had more flexible time schedule and wanted to implement a universal system. The members of the Atlanta team compose an RFP with little input from the Swedish team and the Swedish team did not agree with the length of the document or the time frame of composing. The Swedish team was not concerned with customization where as the Atlanta team made this a high priority.
The chosen software package has to:
Run on a UNIX system.
Have strength predominantly in distribution.
Have presence in Europe and North America.
Modification without changing source-code is needed.

Those are a few of the requirement and both Oracle and QAD meet these but the other requirements are where the two packages differ.

QAD: This vendor does not seem to have the best interest of our company, they are not considering time constraints, extra resources if needed, and have a disregard to the fact that many modifications