Counting the cost of cloud

Summary:IT costs were always a worry, but only an occasional one. Cloud computing has changed that.

This guest post comes courtesy of Chris Harding, Forum Director for SOA and Semantic Interoperability at The Open Group.

By Chris Harding

IT costs were always a worry, but only an occasional one. Cloud computing has changed that.

Here's how it used to be. The New System was proposed. Costs were estimated, more or less accurately, for computing resources, staff increases, maintenance contracts, consultants and outsourcing. The battle was fought, the New System was approved, the checks were signed, and everyone could forget about costs for a while and concentrate on other issues, such as making the New System actually work.

One of the essential characteristics of cloud computing is "measured service." Resource usage is measured by the byte transmitted, the byte stored, and the millisecond of processing time. Charges are broken down by the hour, and billed by the month. This can change the way people take decisions. [Disclosure: The Open Group is a sponsor of BriefingsDirect podcasts.]

"The New System is really popular. It's being used much more than expected."

"Hey, that's great!"

One of the essential characteristics of cloud computing is "measured service."



Then, you might then have heard,

"But this means we are running out of capacity. Performance is degrading. Users are starting to complain."

"There's no budget for an upgrade. The users will have to lump it."


Now the conversation goes down a slightly different path.

"Our monthly compute costs are twice what we budgeted."

"We can't afford that. You must do something!"


Possible and necessary

And something will be done, either to tune the running of the system, or to pass the costs on to the users. Cloud computing is making professional day-to-day cost control of IT resource use both possible and necessary.

This starts at the planning stage. For a new cloud system, estimates should include models of how costs and revenue relate to usage. Approval is then based on an understanding of the returns on investment in likely usage scenarios. And the models form the basis of day-to-day cost control during the system's life.

Last year's Open Group “State of the Industry” cloud survey found that 55 percent of respondents thought that cloud return on investment (ROI)addressing business requirements in their organizations would be easy to evaluate and justify, but only 35 percent of respondents' organizations had mechanisms in place to do this. Clearly, the need for cost control based on an understanding of the return was not widely appreciated in the industry at that time.

For a new cloud system, estimates should include models of how costs and revenue relate to usage.



We are repeating the survey this year. It will be very interesting to see whether the picture has changed.

Participation in the survey is still open. To add your experience and help improve industry understanding of the use of cloud computing, visit: http://www.surveymonkey.com/s/TheOpenGroup_2012CloudROI

This guest post comes courtesy of Chris Harding, Forum Director for SOA and Semantic Interoperability at The Open Group. Copyright The Open Group and Interarbor Solutions, LLC, 2005-2012. All rights reserved.

You may also be interested in:

Topics: Cloud

About

Dana Gardner is president and principal analyst at Interarbor Solutions, an enterprise IT analysis, market research, and consulting firm. Gardner, a leading identifier of software and cloud productivity trends and new IT business growth opportunities, honed his skills and refined his insights as an industry analyst, pundit, and news edito... Full Bio

zdnet_core.socialButton.googleLabel Contact Disclosure

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Related Stories

The best of ZDNet, delivered

You have been successfully signed up. To sign up for more newsletters or to manage your account, visit the Newsletter Subscription Center.
Subscription failed.