8 replies
It seems to me that the whole selection process has been done backwards. The people who are going to use the software should have done the research and presented you with a short list. You would then evaluate the system requirements of each and rate each of the candidates by the amount of effort that would be required to implement each. Then the managers make the final decision.
SAP, as you know, is a very complicated highly integrated system. Evaluating the replacement is best done by a business analyst. It makes no more sense to ask a computer system administrator to select a replacement for SAP than it would be to ask a baggage handler what model of new aircraft an airline should buy.
As I said, the only part of the process that you should have been asked to play in this process would be to list the system requirements and other implementation considerations each of a short list of candidates would require. In my opinion a computer support person does not typically have the knowledge to select complicated business software. It doesn't make any sense to me.
by choppit
by hal 9000
But when it doesn't work perfectly for everyone which it doesn't have a hope in hell of doing you'll know who will wear the blame?
For any SAP installation I'd leave it to the Business Adviser and Management and then set about cleaning up the mess after wards that way I would not constantly be bearing the brunt of the complaints about the system.
Do you realize that any complaints will adversely reflect on you no matter what?
Col ]:)
by choppit
by choppit
If you give your opinion to all of the managers involved in the decision and give them a chance to think about it you could then hold a couple of meetings with everyone attending. All of the managers would hear what all of the other managers would say. Eventually a decision would be made. I think that it can be done if all of the managers are in the same room at the same time.
The trick at that point is to make the decision process stop. I once worked at a place that had to change hardware. Every week we would have a meeting about this issue. Every week the lead manager would start the meeting by saying "Let's rethink this whole situation." Eventually that manager was fired, and rightly so. We would never had moved past the decision phase of the project if he had remained in charge.
Again, though, the responsibility for making these things happen is with the managers. Try to find a diplomatic way of saying that your role is strictly advisory and that it is THEIR responsibility to see that this project is completed.
by choppit
The shortlisting meeting today went well. The group easily came to a decision as to which 2 systems to shortlist based on business fit. I now find myself in exactly the position that I suspected I would be (and hence the original post).
The management team has voted in favour of a Linux Server, MySQL based system accessed via terminal/thin client. The MD has voted in favour of a Windows Server, SQL based thick client solution.
I have stated that in my opinion either solution will be a good fit and I will run with whatever decision the team makes.
The MD has agreed that the Linux solution is functionally as good, if not better than the Windows solution. I then asked him why he appeared to be dead set against the Linux solution and this is basically what he said;
1) Because the solution has no GUI, it looks old, if it looks old then it must be old, if it is old it will soon be obsolete......
2) Linux is based on Unix, and Unix is old........
This discussion is closed to new replies.
Trending Community archive posts
Sort by Trending