Skip to main content

Cloud Services and Warranty Processes

As business organizations opt for support from the cloud to provision Software, Platform, or Infrastructure services the need for warranty through the service value chain becomes paramount. Service warranty is gained by achieving specified levels of availability, capacity, continuity, and security. 
The dynamic, nature of the business and varied demand from multiple customers and user profiles must be considered when defining and investing in cloud architectures.  Each customer will expect that only their application or service will be delivered to users when in fact multiple customer and user communities could be leverage from the scalability and shared resources in the cloud.

Availability/Capacity and the Cloud

Service providers must gain assurance that multiple instances of the same application are delivered in a scalable manner.  In order to ensure availability and leverage capacity on demand additional tools and technologies such as load balancing, server virtualization, application delivery controllers and more will be necessary to integrate deep into the infrastructure, back end systems and network.   All of this is disguised or invisible to the customer as the “Cloud”.  Considerations from the business side will have to ensure that the transition of any new or changed services are enabled via a combination of both internal and external services.  Therefore; designing, delivering and managing the end to end service delivery through the value chain still needs to be addressed. 

Service Level Management and the Cloud

The Service Level agreements will only deliver if underpinning contracts for cloud services support business and customer requirements.  With cloud computing the responsibility and integration points shift.  Internal sourcing shifts to the cloud provider.   Metrics for scalability, availability and security will require monitoring and reporting on caching, compression, rate shaping and other cloud unique elements in order to ensure availability and Service Level Requirements.  Inaccurate or incomplete contracts with the cloud provider could jeopardize the cost savings, business benefit and value that is expected from the cloud.

Cloudy days ahead

The flight to the cloud continues to evolve as an advantageous means of sourcing.  When managed correctly cloud services can increase the cadence and velocity of service delivery to meet dynamic business demand.   Even though cloud computing in all its variants is still evolving, unified Service Level Agreements and Underpinning Contracts with a focus on people and relationship management  help ensure the cloud computing environment is always fast, secure, and highly available. The heart of service management withstands evolution and is still vital. The accountability for provisioning Availability, Capacity, Continuity and Security still lies with the service provider.



Comments

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables.  An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and th

The ITIL® Maturity Model

Most organizations, especially service management organizations, strive to improve themselves. For those of us leveraging the ITIL® best practices, continual improvement is part of our DNA. We are constantly evaluating our organizations and looking for ways to improve. To aid in our improvement goals and underscore one of the major components of the ITIL Service Value System , Continual Improvement .   AXELOS has updated the ITIL Maturity Model and is offering new ITIL Assessment services. This will enable organizations to conduct evaluations and establish baselines to facilitate a continual improvement program. A while back I wrote an article on the importance of conducting an assessment . I explained the need to understand where you are before you can achieve your improvement goals. Understanding where you are deficient, how significant gaps are from your maturity objectives, and prioritizing which areas to focus on first are key to successfully improving. One method many organi

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem