We recently embraced a utility computing architecture encompassing approximately 250 servers. While we have reduced the number of applications and vendors through a "like functionality" study, we are now at the point where we want to evaluate whether our traditional "best of breed" approach is really that cost effective or whether we would realize better cost savings through an integrated stack effort. So instead of having three vendor products for the portal/application/web services tier we would have one. Naturally, from a developer community perspective, this assessment would have to consider the training and familiarity, the skill set question, re-code costs and etc. Can someone comment or possibly direct me to information sources that would help me calculate these types of costs and that discusses the benefits of integrated stack products versus "Best of Breed? Saving Changes...
Mark Price PerryBusiness Driven PMO Evangelist| BOT InternationalOrlando, Fl, United States
Dear Anonymous, can you clarify what you mean by "best of breed"? Would not your integrated stack approach consist of "best of breed" components. Or by "best of breed" do you mean, single vendor verses multi-vendor? Also, is your computing utility supporting one company "personality" or is it a compute utitility in support of multiple independent business entities? While there are cost savings associated with reducing redundant vendor packages, it may not be possible or practical to insist upon or enforce one vendor product as a standard if other vendor products are already in use and are in late stages of technology adoption by the business units. For example, if your three independent business units are happily and productively using three packages respectively for their portal/application/web services, would it make sense to rip two out just for the sake of standardization? Maybe yes, maybe no. Typically, most IT strategies have a tactical view and a strategic view. Strategically, there is no doubt value and cost efficiencies associated with package standardization. You also might consider the leverage thath you have with your vendors by at least having two packages amidst your portfolio. Back in the old main-frame days, we called this a dual-vendor strategy. The idea was to get the best possible price, service, and support by having a competitive environment. Regarding calculating the costs and benefits, you find a feasibility study template to be helpful. Let me know if you need one. Cheers. -- Mark Perry, VP of Cuctomer Care, BOT International Saving Changes...
