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

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.”  Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services, which is people. Because the people element adds variability, the service is variable. This holds true, especially for the value proposition—not eve...

What Is A Service Offering?

The ITIL 4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group.   As a service provider, we can’t stop there!   We must know what the contracts of our service offering are and be able to put them into context as required by the customer.     Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include:     Goods, Access to Resources, and Service Actions 1. Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods.   Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.      ...

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

This article was originally published in 2015. With the Introduction of ITIL 4, some of this best practice has changed. See  ITIL 4 and the Evolving Role of Roles . Updated Definitions in ITIL 4: Process Owner: In ITIL 4, the concept of 'processes' has expanded into broader 'practices.' Consequently, the Process Owner is now often referred to as the 'Practice Owner.' This individual is accountable for the overall design, performance, integration, and improvement of a specific practice within the organization. They ensure that the practice achieves its intended outcomes and aligns with the organization's objectives. Process Manager: Now commonly known as the 'Practice Manager' in ITIL 4, this role is responsible for the day-to-day management of the practice. The Practice Manager ensures that activities are carried out as intended, manages resources assigned to the practice, and oversees the practitioners performing the work. Process Practit...