|By Toddy Mladenov||
|June 16, 2014 11:28 AM EDT||
Last week's Joyent outage brought us thinking how many IT teams make the effort what is the meaningful downtime that will not have significant impact on their business. In this post I will not discuss this particular outage although it is a yet another good example for improving the IT practices and processes but will concentrate on an important step in the Business Impact Analysis (BIA) that is a prerequisite for Disaster Recovery - namely the Cost of Downtime.
Very often because the lack of understanding of the overall IT application portfolio the cost of downtime is calculated using made up numbers or numbers for the whole company. Each application must be considered separately and the analysis must be done per application - there is no one size fits all. For now though let's take a simple example: company that has a revenue of $5o0M and 1500 employees and experiences outage that impacts 50% of it's employees and 30% of their revenue during the downtime.
The first thing you need to do in order to calculate the cost per hour of downtime is to calculate the labor cost per hour. Let's assume that the annual benefits per employee for our fictitious company are $75k and each employee works on average 1,920h per year (assuming 2 weeks vacation and 10 holidays per year). The hourly labor cost for the company will be:
1500 employees X $75K = $112.5M / 1920h = ~$58,600
Because we previously said that only 50% of the employees will be affected the cost per our of downtime will be:
$58,600 X 50% = $29,300
The next thing that you need to do is to calculate the revenue loss per hour of downtime. Another assumption that we need to make here is that our company generates revenue 5 days a week and it is closed only for the holidays, which means that the company generates revenue 2,000 a year. From here our calculation is:
$500M / 2,000h = $250K/h
and we need to multiply this by 30% assumed loss of revenue:
$250K * 30% = $75,000
The total loss to our company for one hour of downtime is determined by combining both numbers above:
$58,000 labor loss per our + $75,000 revenue loss per hour = $133,000
However we do not stop here! Our ultimate goal is to determine how much downtime can we afford for this application. And for that you need to some more financial calculations, which involve not only the revenue but also the profits unless you want to wipe out all the profits with this one downtime. Let's assume that the company's profits are 10% and management decided that the acceptable loss of profits from availability issues with this particular application is 0.1%:
$1B * 10% profits = $100M * 0.1% = $100,000
Dividing both numbers (acceptable loss and cost of downtime per hour) gives us the maximum tolerable downtime (MTD) for the application:
$100,000 / $133,000 = ~0.75 * 60 mins = ~45 min
If you are curious such application must have uptime of 99.991445% in order to satisfy the above requirements.
The overall lesson here is that determining the cost of downtime is not only application dependent but also requires a solid knowledge of the company financials and therefore good collaboration between IT and business owners.
With all the incredible momentum behind the Internet of Things (IoT) industry, it is easy to forget that not a single CEO wakes up and wonders if “my IoT is broken.” What they wonder is if they are making the right decisions to do all they can to increase revenue, decrease costs, and improve customer experience – effectively the same challenges they have always had in growing their business. The exciting thing about the IoT industry is now these decisions can be better, faster, and smarter. Now all corporate assets – people, objects, and spaces – can share information about themselves and thei...
Nov. 30, 2015 10:00 AM EST Reads: 286
Nov. 30, 2015 09:00 AM EST Reads: 505
Nov. 30, 2015 08:00 AM EST Reads: 562
Nov. 30, 2015 07:00 AM EST Reads: 381
Nov. 30, 2015 07:00 AM EST Reads: 466
Nov. 30, 2015 06:00 AM EST Reads: 386
Nov. 30, 2015 05:30 AM EST Reads: 493
Nov. 30, 2015 04:00 AM EST Reads: 348
Nov. 30, 2015 04:00 AM EST Reads: 607
Nov. 30, 2015 03:45 AM EST Reads: 438
Nov. 30, 2015 02:00 AM EST Reads: 448
Nov. 30, 2015 02:00 AM EST Reads: 450
Nov. 30, 2015 12:00 AM EST Reads: 450
Nov. 29, 2015 02:00 PM EST Reads: 488
Nov. 29, 2015 01:00 PM EST Reads: 359
Nov. 29, 2015 12:45 PM EST Reads: 423
Nov. 29, 2015 12:30 PM EST Reads: 429
Nov. 29, 2015 12:00 PM EST Reads: 532
Nov. 29, 2015 11:45 AM EST Reads: 337
Nov. 29, 2015 09:45 AM EST Reads: 456