68 lines
4.7 KiB
HTML
68 lines
4.7 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
<!DOCTYPE html
|
||
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
<html lang="en-us" xml:lang="en-us">
|
||
|
<head>
|
||
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
<meta name="security" content="public" />
|
||
|
<meta name="Robots" content="index,follow" />
|
||
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
<meta name="DC.Type" content="task" />
|
||
|
<meta name="DC.Title" content="Estimate the value of availability" />
|
||
|
<meta name="abstract" content="No one would argue the importance of availability. However, when asked to justify the cost of additional hardware to support improved availability, many people do not know how to build a case." />
|
||
|
<meta name="description" content="No one would argue the importance of availability. However, when asked to justify the cost of additional hardware to support improved availability, many people do not know how to build a case." />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzalwoverview.htm" />
|
||
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
<meta name="DC.Format" content="XHTML" />
|
||
|
<meta name="DC.Identifier" content="rzalwvalue" />
|
||
|
<meta name="DC.Language" content="en-us" />
|
||
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
<!-- US Government Users Restricted Rights -->
|
||
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
<title>Estimate the value of availability</title>
|
||
|
</head>
|
||
|
<body id="rzalwvalue"><a name="rzalwvalue"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1">Estimate the value of availability</h1>
|
||
|
<div><p>No one would argue the importance of availability. However, when
|
||
|
asked to justify the cost of additional hardware to support improved availability,
|
||
|
many people do not know how to build a case.</p>
|
||
|
<div class="section"><p>The following steps describe how to estimate the value of your
|
||
|
information services:</p>
|
||
|
</div>
|
||
|
<ol><li><img src="./delta.gif" alt="Start of change" /><span> <span class="uicontrol">Develop a list of the major services and
|
||
|
solutions that your system provides.</span> Your system exists so that
|
||
|
end users and solutions can accomplish tasks that are critical to the operation
|
||
|
of your business. The systems provide solutions to a business function. If
|
||
|
the system is unavailable, the business function cannot be completed or is
|
||
|
significantly degraded to the point of causing the business lost revenue or
|
||
|
increased expenses. </span><img src="./deltaend.gif" alt="End of change" /></li>
|
||
|
<li><img src="./delta.gif" alt="Start of change" /><span> <span class="uicontrol">Assess how much it costs you when these
|
||
|
services are unavailable.</span> Each application or service has a direct
|
||
|
affect on business functions. You need to determine how these business functions
|
||
|
would be affected and what would be the overall cost to your business.</span><img src="./deltaend.gif" alt="End of change" /></li>
|
||
|
<li><span> <span class="uicontrol">Look at direct costs versus indirect costs.</span> Direct
|
||
|
costs are losses that can be traced directly to a system being unavailable.
|
||
|
Indirect costs are those that are incurred by another department or function
|
||
|
as a result of an outage.</span></li>
|
||
|
<li><span> <span class="uicontrol">Consider tangible costs versus intangible costs.</span> Tangible
|
||
|
costs are those that can be measured in currency. However, there are other
|
||
|
costs that are not measured with money, such as market share, lost opportunity,
|
||
|
and good will.</span></li>
|
||
|
<li><span> <span class="uicontrol">Analyze fixed costs versus variable costs.</span> Fixed
|
||
|
costs are those that result from a failure and are the same, regardless of
|
||
|
the length of the outage. Variable costs are those that vary, based on the
|
||
|
length of the outage.</span></li>
|
||
|
</ol>
|
||
|
</div>
|
||
|
<div>
|
||
|
<div class="familylinks">
|
||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzalwoverview.htm" title="In today's fast-paced Internet environment, it is crucial that your data and applications be available to you when you need them. If your customers cannot access your Web site because your system is down, they may go to your competitors instead.">Availability roadmap</a></div>
|
||
|
</div>
|
||
|
</div>
|
||
|
</body>
|
||
|
</html>
|