For cloud services to deliver their promised value, they must be underpinned by effective and efficient processes.

Transcription

1 Research Publication Date: 15 October 2010 ID Number: G ITIL 'in the Cloud' George Spafford, Ed Holub The cloud-computing delivery model is generating a lot of interest from organizations wishing to effectively and efficiently scale. To achieve desired benefits and properly mitigate risks around these services, supporting processes that are properly designed and implemented are mandatory. Key Findings The ITIL provides guidance on process best practices to improve the quality of service delivery that is equally relevant to cloud services as to traditional service models. Cloud service solution design, implementation and ongoing operation must address requirements not only technically, but also from process and human perspectives. For cloud services to deliver their promised value, they must be underpinned by effective and efficient processes. To adequately support IT services that traverse the cloud and the organization overall, processes must be designed with risks and objectives in mind to avoid creating constraints. Recommendations The design and implementation of cloud services must follow the same rigor as implementing IT operations services using service management. Thus, process requirements that underpin these services must be taken into account. Processes must be optimized for the cloud based on risks and objectives. If not, the processes may create artificial constraints that limit the ability of cloud services to deliver on commitments. Enterprises should take advantage of the potential standardization of services that a cloud environment provides by standardizing the processes that enable these services. Reproduction and distribution of this publication in any form without prior written permission is forbidden. The information contained herein has been obtained from sources believed to be reliable. Gartner disclaims all warranties as to the accuracy, completeness or adequacy of such informatio n. Although Gartner's research may discuss legal issues related to the information technology business, Gartner does not provide legal advice or services and its research should not be construed or used as such. Gartner shall have no liability for errors, omissions or inadequacies in the information contained herein or for interpretations thereof. The opinions expressed herein are subject to change without notice.

2 ANALYSIS The cloud-computing delivery model is generating a lot of interest from firms wishing to take advantage of lower capital costs, greater agility, and the ability to effectively and efficiently scale services. To achieve the desired benefits and properly mitigate risks around these services, supporting processes that are properly designed and implemented are mandatory. Processes that are not designed with cloud requirements in mind could result in suboptimal outcomes. All sustainable solutions that help organizations pursue and protect goals require a blending of people, process and technology elements. The cloud is no different. IT must view cloud offerings as services, because far more than just hardware and software are required to deliver value, and, moreover, these services will be traversing corporate- and noncorporate-controlled systems. All services that IT delivers to the business must be underpinned by processes that create a reasonable assurance of predictable outcomes to both end users and business management. This is done by embedding controls that business management deems necessary to reduce residual risks to acceptable levels. These controls can be manual or automated, depending on requirements, available resources, etc. Services existing in private, public and hybrid clouds will have differing levels of risks, and thus warrant controls that are commensurate to mitigate risks to a level acceptable to business management. A critical business service on a public cloud versus on a private cloud could require different change models to be designed and implemented (for example, in change management). This dynamic view of processes that are adjusted to risk levels, and the fact that they must be tailored to the needs of the business, is just as true for cloud services as anything else. To be clear, the need for processes "in the cloud" isn't eliminated; rather, the processes underpinning the cloud services must be designed to support the cloud delivery model in an effective and efficient manner. Organizations that do not revise existing processes, such as change management, may find they are inadvertently constraining their cloud services, causing suboptimal results. Consider, for example, a needlessly stringent change model designed for a traditional data center model with discrete physical servers that slows down changes due to controls over risks associated with server provisioning that are no longer appropriate. If the risks are determined to be low, given the capabilities of the particular cloud, a new model that automates the creation, updating and closure of change records could potentially be the outcome. This would enable the speed and agility possible with the cloud, while also allowing organizations to later have the information necessary to answer the question, "What changed?" Rather than wait for services to enter production, as cloud services are planned, processes need to be designed as well. In some cases, there will be current service management processes that need to be evaluated and revised as required, such as updating incident management to reflect multisourcing. In other situations, new processes may need to be identified, designed and implemented for the first time. In either situation, the ITIL can provide reference processes that organizations can review and pragmatically adopt to better support their internal and external cloud services. Enterprises should take advantage of the potential standardization of services that a cloud environment provides by standardizing the processes that enable these services. The ITIL should be viewed as guidance, not as a standard that must be strictly adhered to in practice. Organizations need to select, design and implement processes based on need. Based on organization-specific objectives, the above processes will not have equal value. This will affect the selection and prioritization of processes, and the differing risk profiles and objectives will impact the design and implementation. Publication Date: 15 October 2010/ID Number: G Page 2 of 5

3 The following ITIL processes merit review by organizations seeking to better support their cloud services: Change Management Availability, integrity and security all necessitate that risks be properly managed. IT organizations need to reassess their change models to ensure they meet the new demands of the services that may be multisourced (some combination of private and public clouds). It has been argued that change management may slow up cloud work. Actually, change models can be designed to properly balance agility and risk management. For example, there may be a greater number of changes that can be categorized as "standard changes," per the ITIL, to reduce overhead and expedite implementation. If self-service provisioning will be offered, the change management process must take that into account. Service Asset and Configuration Management (SACM) When left unaddressed, complexity and coupling of configuration items in cloud services are increasing, while tolerance for delays in time to market and/or loss of availability are decreasing. The SACM process is tasked with providing timely, accurate and relevant information regarding the IT environment to the various process groups so they can make proper decisions. This includes the planning for new and changed services, as well as understanding what has changed during operational and security-related incidents. Asset management, to aid with license compliance, etc., is also critical in cloud environments. The ITIL's SACM guidance is more applicable to configuration management, whereas comprehensive IT asset management (ITAM) is another discipline. Incident Management Service impairments and outages will happen, and IT needs to work with cloud service providers, both internal and external, to establish roles and responsibilities, how data will be exchanged, escalation protocols, etc. This is even more important when the number of service providers increases the heterogeneity of the technical, process and cultural environments. Problem Management To establish root cause, workarounds and solutions, IT and the cloud service provider must work out data exchanges and how the groups will work together. As the number of vendors/cloud service providers increases, the greater the need to focus on addressing problems and not devolving into low-value blame assignment, where one blames another and nothing is solved. Release and Deployment Management (RDM) This is required to manage the creation, testing and deployment of services into production. As the number of sources of elements in each service increases, the command, control and communication requirements exponentially increase, and need RDM to properly manage risks and coordinate activities, scheduling, etc. Service Catalog Management Both the business and IT need to have effective and efficient means to order business and technical cloud services. Service catalog management could work in conjunction with request fulfillment to automate and optimize the delivery of cloud services on demand. Service-Level Management (SLM) IT and the business must negotiate service-level objectives and the required roles and responsibilities that both have. This clarifies requirements on both sides, plus provides measurable targets that can be reviewed, and when required, service improvement plans are launched. The importance of underpinning contracts that support internal SLAs are critical with external service Publication Date: 15 October 2010/ID Number: G Page 3 of 5

4 providers, whereas internally delivered services will be more SLA-based. Don't assume that putting a service in the cloud will inherently address reliability challenges. Capacity Management No resource is infinitely available, and certainly not in a manner that always makes business sense. Cloud business models continue to evolve and IT must be prepared to optimize utilization of resources so that costs are controlled. For example, if a usage-based cloud model has tiered pricing with commitments, then it may be financially and contractually sound to properly understand what will be required over the term of a contract. Private cloud services must be underpinned with capacity management processes to ensure that resources are available to provide adequate scalability. Event Management IT has monitored systems for decades with mixed results. With the cloud, there must be a clear understanding of what activities the provider will perform, as well as which IT group will be responsible for the cloud services. For example, the cloud provider may only monitor the platform and not details about customer service, including availability and latency. Moreover, IT needs to not only understand what to monitor, but also how to respond. Event management can help enable both effective and efficient monitoring and responses, plus provide a means to enable discussions with service providers. Service Design Life Cycle Phase While not a process per se, the service design phase does present a significant opportunity. All value and significant amounts of risks and costs are borne by the organization once a service is in production. Even in cloud environments, care must be taken to properly design the services to optimize sustainable operations. This will necessitate that development, acquisition, operations and vendor groups work together to design and deliver optimized cloud services, which will also require careful management as the number of providers increases. IT Financial Management (ITFM) Cloud services are neither infinite nor free. Organizations must budget accordingly, understand costs, and, at a minimum, understand who is consuming what resources and what value is derived. This can be done through management reports that provide transparency regarding utilization and costs, or can even be evolved to chargeback models if deemed necessary. Without ITFM discipline and controls in place, the easy scalability of cloud services may result in costs that dramatically exceed estimates and available budgets. The above list isn't exhaustive; however, we feel these processes have the most potential relevance to organizations pursuing cloud-based service deployments. Bottom Line Cloud services be they private, public or hybrid present opportunities for IT organizations to pursue. Not only must the technical side of cloud services be evaluated, planned and implemented, but so too must IT processes and the softer "people" side of the equation. Organizations should use the movement to the cloud as an opportunity to develop standardized IT operations management processes that optimize the delivery of IT services. RECOMMENDED READING "I&O Roles for Private Cloud-Computing Environments" Publication Date: 15 October 2010/ID Number: G Page 4 of 5

5 REGIONAL HEADQUARTERS Corporate Headquarters 56 Top Gallant Road Stamford, CT U.S.A European Headquarters Tamesis The Glanty Egham Surrey, TW20 9AW UNITED KINGDOM Asia/Pacific Headquarters Gartner Australasia Pty. Ltd. Level 9, 141 Walker Street North Sydney New South Wales 2060 AUSTRALIA Japan Headquarters Gartner Japan Ltd. Aobadai Hills, 6F 7-7, Aobadai, 4-chome Meguro-ku, Tokyo JAPAN Latin America Headquarters Gartner do Brazil Av. das Nações Unidas, andar World Trade Center São Paulo SP BRAZIL Publication Date: 15 October 2010/ID Number: G Page 5 of 5