Proactive Availability Management Techniques

Proactive Availability Management Techniques - CFIA

Component Failure Impact Analysis (CFIA) is a proactive availability management technique which was developed by IBM in the 1970’s. This technique allows us to predict the impact on our services if any of the individual components fail. It points out our vulnerabilities to single points of failure.

Doing a CFIA is a pretty simple exercise. Here are the steps:

Take certain key Configuration Items (CI)s in the infrastructure and identify the services that they support by researching the Configuration Management System (CMS). If you do not have a CMS, look for paper diagrams, network configurations, any available documentation and general knowledge.
Create a paper or electronic table or spreadsheet. List the CIs in the first column, and the Services in the top row. For every CI, place an “X” in the column below the service if that CI's failure would cause an outage. Mark an “A” when the CI has an immediate backup (hot start) or a “B” when the CI needs a warm start.

The basic CFIA is now completed. Every CI that has an "X" or "B" is a point of concern and represents a vulnerability for that service.

The next step is to answer the following questions about the potential failure of the configuration item:

Is this CI a single point of failure?
What is the business impact if this service fails? How many people will be affected?
What is the cost of unavailability for this service?
What is the likelihood failure will occur?
Are we willing to take the risk of this failed service?
What can we do to improve our vulnerability?
Should we look at CI redundancy options? What would this cost?
Is this cost justified?
Could preventative measures helped avoid the problem?

Performing a Component Failure Impact Analysis can identify and justify significant mprovements without extensive process maturity or expensive supporting software. This technique proactively analyzes and helps to manage risks.

Comments

Bose said…

Enhanced my skills on CFIA. Thanks so much for the efforts in sharing this with me!Business Impact Analysis Template

April 3, 2012 at 2:09 AM

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...

Search