One of the key success factors in moving to the Cloud is developing a robust business case. The business case provides the rationale, benefits, and costs, as well as the expected results for investments by organizations.
This is the first in a three-part series on the importance of a business case, budgets; operating vs. capital, and expected results of a successful business case. Today’s blog will cover the need for business case, followed by a deeper dive into how you allocate your budget of operating (OPEX) vs. capital (CAPEX) and finally, how to determine if you are meeting your business case objectives.
Cloud is another form of outsourcing. The discussion of the ROI should follow a similar thought process as outsourcing, contracting out or for that matter many other IT decisions. This starts with the business case. The business case has established itself as the primary tool in sourcing decisions.
The IT business case typically has seven components: Background, current state and options; financial review; risk management; strategic fit; execution plan; and ongoing management. In addition, there are four major steps in developing a business case: scope identification; data collection; market pricing; and contracting.
Not all business cases need each of the steps. At the very least, though, a financial review commonly referred to as a cost/benefit analysis should be done. The cost/benefit analysis is a comparison of the options a company has to support its IT requirements. The benefits of Cloud-based infrastructure (or Infrastructure as a Service, IaaS) need to be clearly identified and quantified to the extent possible. In addition, one-time costs for activities such as transition need to be included. Last, the financial implications of risk need to be woven into the business case. While the risk (which revolves around security and privacy that is frequently associated with Cloud) should be identified and their probability and priority to the organization needs to be assessed, the financial review focuses on the cost of reducing or eliminating such risk. For Infrastructure as a Service, IaaS (which are virtualized servers, storage and networking hardware delivered as a service) examples include the cost for data replication, mirrored sites and any cost differences for in-Canada solutions that address potential risk and concern.
Regardless of whether a full business case or cost/benefit analysis is done, the exercise really starts with a discussion between the business and IT. The business case is heavily dependent on communication between management, IT leaders and sourcing decision makers. These discussions should focus on a common understanding of the company's future direction and what will be required from IT to meet the corporate goals. These conversations will help form the scope of infrastructure services being considered for the Cloud.
Cloud is one option. And within IaaS there are various choices between Public and Private models. While Public IaaS offers many benefits, such as potential cost savings and the ability to scale, it does provide somewhat limited options on how infrastructure resources can be configured. Public IaaS is a one-to-many model and customization comes at a price. Public IaaS also has to be managed, whether by the service provider or internally. These costs have to be addressed in the ROI calculation. Cloud also introduces the discussion of operating (Opex) vs. capital (Capex). My next blog will discuss this in more detail.
In the meantime, is your company thinking about moving to the Cloud but you don’t know where to start? Do you think a business case would be the first step or have you done one already?
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This is the first in a 3 part series about the Business Case for Cloud by Mark Schrutt. Director, Services & Enterprise Applications. IDC Canada