Skip to main content

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:
  1. 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.
  2. 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

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 the

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-that is people. Because the people element adds variability, the service is variable. This holds true especially for th

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service". I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize: SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle. ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with