Cloud Computing and SOA Convergence in Your Enterprise: A Step ...
Cloud Computing and SOA Convergence in Your Enterprise: A Step ...
Cloud Computing and SOA Convergence in Your Enterprise: A Step ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
76 Chapter 4 Mak<strong>in</strong>g the Bus<strong>in</strong>ess Case for <strong>Cloud</strong>s<br />
In essence, this is a list of bus<strong>in</strong>ess <strong>and</strong> IT issues we can potentially address<br />
with cloud comput<strong>in</strong>g. Aga<strong>in</strong>, the types of issues you use for your bus<strong>in</strong>ess<br />
case may be very different depend<strong>in</strong>g on the bus<strong>in</strong>ess <strong>and</strong> IT issues<br />
with<strong>in</strong> your enterprises.<br />
<strong>Step</strong> 2: Assign Costs<br />
Now that we know the issues, we need to assign costs. These are typically go<strong>in</strong>g<br />
to be over a 1- or 2-year horizon, but some companies will want a 5-year<br />
horizon, depend<strong>in</strong>g on how they do the plann<strong>in</strong>g. This part of the bus<strong>in</strong>ess<br />
case is really about assign<strong>in</strong>g cost to the def<strong>in</strong>ed issues, thus creat<strong>in</strong>g the case<br />
that there are th<strong>in</strong>gs that can be improved, <strong>and</strong> here is how much we will<br />
benefit if we improve them.<br />
Consider<strong>in</strong>g our example, we could assign yearly costs as follows:<br />
Bus<strong>in</strong>ess<br />
Customer satisfaction is low due to lack<br />
of good sales automation processes.<br />
Sales projections are <strong>in</strong>accurate, thus<br />
caus<strong>in</strong>g projected sales to be overstated<br />
<strong>and</strong> understated.<br />
IT<br />
Exist<strong>in</strong>g hardware <strong>and</strong> software costs<br />
are not <strong>in</strong> alignment with best<br />
practices.<br />
Numerous system performance compla<strong>in</strong>ts<br />
are made by sales staff.<br />
Sales staff is forced to share term<strong>in</strong>als<br />
because of scal<strong>in</strong>g limitations from the<br />
exist<strong>in</strong>g systems.<br />
$500,000 <strong>in</strong> lost sales per year<br />
$750,000 <strong>in</strong> the cost of poor<br />
report<strong>in</strong>g per year<br />
$1,000,000 <strong>in</strong> hardware/<br />
software costs per year<br />
$200,000 <strong>in</strong> the cost of lost<br />
productivity per year<br />
$300,000 <strong>in</strong> the cost of lost<br />
productivity per year<br />
Some of these costs are based on gathered data, others are estimated, <strong>and</strong><br />
some are a mixture of both. Make sure that the cost of each issue is not <strong>in</strong>flated<br />
but is based on reality. Keep <strong>in</strong> m<strong>in</strong>d that this bus<strong>in</strong>ess case will be reviewed<br />
at some time <strong>in</strong> the future <strong>and</strong> therefore should reflect the “real<br />
world” as much as possible.