Skip to main content

Business Impact Analysis

The resultant impact on the company is measured to determine the perceptive.of the IT customer  Five areas are assessed. Each area has a maximum score of 4 and the classification is the score of all areas represented as a percentage.
  1. Scope - Percentage of customers affected.
  2. Credibility - Internal and external negative consequences in the company.
  3. Operations - Business interference.
  4. Urgency - Time planning.
  5. Prioritization - Resource reaction.
Scope scoring
  • (4) More than 50% of customers affected
  • (3) More than 25% of customers affected
  • (2) Less than 25% of customers affected*
  • (1) Less than 1% of users affected
  • (0) Single IT customer affected
Credibility scoring
  • (4) Areas outside the company will be affected negatively
  • (3) Company affected negatively
  • (2) Multiple business units affected negatively
  • (1) Single business units affected negatively
  • (0) No credibility issue*
Operations scoring
  • (4) Interferes with core business functions
  • (3) Interferes with business activities*
  • (2) Significant interference with completion of work
  • (1) Some interference with normal completion of work
  • (0) No work interference
Urgency scoring
  • (4) Underway and could not be stopped
  • (3) Caused by unscheduled change or maintenance
  • (2) Incident caused by a change
  • (1) Incident caused by scheduled maintenance
  • (0) Completion time not important*
Prioritization scoring
Reviewing the scope , credibility, operations and urgency please classify the priority of the incident.
  • (4) Critical - An immediate and sustained effort using all available resources until resolved. On-call procedures activated, vendor support invoked.
  • (3) High - Technicians respond immediately, assess the situation, and may interrupt other staff working low or medium priority jobs for assistance.
  • (2) Medium - Respond using standard procedures and operating within normal supervisory management structures.
  • (1) Low - Respond using standard operating procedures as time allows. *
  • (0) No prioritization

* - default score
Classification example
  • The scope is rated as 2 – less than 25% of customers affected.
  • The credibility is rated as 4 – Areas outside the company will be affected negatively.
  • The operations is rated as 2 - Interferes with normal completion of work.
  • The urgency is rated as 3 - Caused by unscheduled change or maintenance.
  • The prioritization is rated as 3 – High - Technicians respond immediately, assess the situation, and may interrupt other staff working low or medium priority jobs for assistance.
  • The score is thus 14 out of a max of 20 = 70%.
After a large enough sample pool has been built the averages are calculated. Let's assume the average for classification is 70%. Dependant on the calculate score for a specific major incident the following statements can be made:
  • The incident affected the company less than usual.
  • The incident affected the company the same as usual.
  • The incident affected the company greater than usual.
Read about the Major Incident Process here.


Popular posts from this blog

easywall - Web interface for easy use of the IPTables firewall on Linux systems written in Python3.

Firewalls are becoming increasingly important in today’s world. Hackers and automated scripts are constantly trying to invade your system and use it for Bitcoin mining, botnets or other things. To prevent these attacks, you can use a firewall on your system. IPTables is the strongest firewall in Linux because it can filter packets in the kernel before they reach the application. Using IPTables is not very easy for Linux beginners. We have created easywall - the simple IPTables web interface . The focus of the software is on easy installation and use. Access this neat software over on github: easywall

Why Madge Networks, the token-ring company, went titsup

There I was shooting the breeze with an old mate. The conversation turned to why Madge Networks which I wrote about here went titsup. My analysis is that Madge Networks had a solution and decided to go out and find a problem. They deferred to more incorrect strategic technology choices. The truth of the matter is that when something goes titsup, its not because of one reason only, but a myriad of them all contributing to the negative consequence. There are the immediate or visual ones, which are underpinned by intermediate ones and finally after digging right down, there are the root causes. There is never a singular root cause for anything but I'll present my opinion and encourage everyone else to chip in. All of them together are more likely the reason the company went titsup. As far as technology brainfarts go there is no better example than Kodak . They invented the digital camera that killed them. However, they were so focused on milking people in their leg

Flawed "ITIL aligned"​ Incident Management

Many "ITIL aligned" service desk tools have flawed incident management. The reason is that incidents are logged with a time association and some related fields to type in some gobbledygook. The expanded incident life cycle is not enforced and as a result trending and problem management is not possible. Here is a fictitious log of an incident at PFS, a financial services company, which uses CGTSD, an “ITIL-aligned” service desk tool. Here is the log of an incident record from this system: Monday, 12 August: 09:03am (Bob, the service desk guy): Alice (customer in retail banking) phoned in. Logged an issue. Unable to assist over the phone (there goes our FCR), will escalate to second line. 09:04am (Bob, the service desk guy): Escalate the incident to Charles in second line support. 09:05am (Charles, technical support): Open incident. 09:05am (Charles, technical support): Delayed incident by 1 day. Tuesday, 13 August: 10:11am (Charles, technical support): Phoned Alice.