Prepare for Downtime

It's obvious that downtime is bad for business.

Here are some suggestions for calculating the likely costs of downtime:

* Detail the number of users for each application and the number of hours that they would use it in a normal day.
* Add a rough valuation of the cost per hour for that group.
* Downtime is a major variable in terms of risk and likely cost, so calculate a number of them: 15, 30, 60 minutes; 4, 8, 16, 24, and 48 hours.
* Calculate the total lost hours of productivity and the direct costs for each downtime period.
* The real cost is in the lost productivity and time sensitivity of the user and that depends on the use of the application. For example, a sales operation may go offline for a day. That is lost time that cannot be "caught up" and would represent a loss of 0.4 percent of revenue per year from this source alone.
* Put an estimate of loss against the lost productivity of those unproductive hours based on the purpose and use of the software application and user feedback.

Therefore, you have to a strategy and solution in place in your organization to mitigate any consequences of downtime.

For more details, read
http://mspro.advisorguide.com/doc/17912