As my colleague Bobby Neil and I wrote earlier this year, if you’re looking to buy Software as a Service (SaaS), it takes diligence. It’s important to understand whether you’re buying a true SaaS solution or simply a repackaged, “on-demand” version of the software. The same can be said for Infrastructure as a Service (IaaS). A true IaaS service can, at times, be difficult to discern from a more traditional managed service.

Unfortunately, many vendors continue to market and sell their legacy services as Cloud technology simply by retooling certain components. This is most commonly accomplished by repackaging the service to align more closely with some of the key features Cloud customers desire most; for example, usage-based pricing and the capability of rapid, self-service provisioning. This technique is known as “Cloud Washing.”

Buying Cloud-washed software or infrastructure creates risk for both the information technology department and for the organization as a whole. For example, take a quick look at the TPI Top 5 "Software as Service: Caveat Emptor," and turn each point on its head. You’ll quickly see that if you’re trying to buy Cloud technology but unknowingly buy legacy technology, you may end up with dated features, limited access, significant up-front investment and, potentially, a slew of customizations.

However, there’s also a contractual risk that has not received much attention. If you are not really buying a Cloud service, why should your contract include Cloud-like terms, which are typically very provider-friendly? There is a real risk here for enterprise buyers – a double whammy, if you will: You’re potentially buying legacy technology, and you’re getting unfavorable terms to boot. No CIO wants to be in this position.

How can you avoid this sticky situation? Given that there continues to be extensive debate about what is “true” Cloud technology, it helps to dispense with the term “Cloud” and instead think of the technology as a continuum, as shown here:

Stantonbloggraphic

As you can see, if you’re buying a custom solution, you should fully expect a more customized agreement. As the technology solution you’re considering becomes more standardized, so should the terms and service levels. It’s a fair trade-off, as long as you have all the information you need to make a rational decision. As expected, service providers have a lot more information about the solution than you do, so it’s up to you to dig for more.

A great starting point is the National Institute of Standards and Technology (NIST) definition of Cloud Computing. The industry has (for the most part) agreed to this definition, so pull it out when you’re talking to your salesperson — but don’t stop there. Ask your Cloud provider other, more-probing questions. For example, does the provider’s application programming interface (API) framework remain stable when rolling out new features? What level of automation is in place for provisioning and failover? Answers to these questions will help you to understand where the service sits on the continuum.

Remember: the more Cloud-like the service, the more you should expect to see contractual terms and service levels that favor the service provider.

Bottom line: Dig deep into the nuts and bolts of the service you’re considering so that you don’t end up buying legacy technology underpinned with a Cloud-like contract.

Originally posted by Stanton Jones, Vice President & CIO, TPI on Consider the Source


Cloud-Washed Contracts: You Could Be at Risk

Categories

All

General

Accessibility

Business events

Business innovation

Cloud computing

Communications

Copyright

Data centers

Digital economy strategy

Economic development Canada

eCommerce

eHealth

eLearning

Enterprise Resource Planning (ERP)

Gadgets

Geo-blocking

Green technology

Investment

Mashups

Mobility

New technologies

Olympic technology

Outsourcing

Project management

Sales and marketing

Security

SMB

Social media

Social networking

Software as a Service (SaaS)

Speakers Corner

Start Up Innovation Campaign

Tech events

Technology law

Technology start-ups

Trends

Unified Communications

Usage based billing

Web 2.0

Wireless


Archives

May 2012

April 2012

March 2012

February 2012

January 2012

December 2011

November 2011

October 2011

September 2011

August 2011

July 2011

June 2011

May 2011

April 2011

March 2011

February 2011

January 2011

December 2010

November 2010

October 2010

September 2010

August 2010

July 2010

June 2010

May 2010

April 2010

March 2010

February 2010

January 2010

September 14, 2011 8:15 AM

As my colleague Bobby Neil and I wrote earlier this year, if you’re looking to buy Software as a Service (SaaS), it takes diligence. It’s important to understand whether you’re buying a true SaaS solution or simply a repackaged, “on-demand” version of the software. The same can be said for Infrastructure as a Service (IaaS). A true IaaS service can, at times, be difficult to discern from a more traditional managed service.

Unfortunately, many vendors continue to market and sell their legacy services as Cloud technology simply by retooling certain components. This is most commonly accomplished by repackaging the service to align more closely with some of the key features Cloud customers desire most; for example, usage-based pricing and the capability of rapid, self-service provisioning. This technique is known as “Cloud Washing.”

Buying Cloud-washed software or infrastructure creates risk for both the information technology department and for the organization as a whole. For example, take a quick look at the TPI Top 5 "Software as Service: Caveat Emptor," and turn each point on its head. You’ll quickly see that if you’re trying to buy Cloud technology but unknowingly buy legacy technology, you may end up with dated features, limited access, significant up-front investment and, potentially, a slew of customizations.

However, there’s also a contractual risk that has not received much attention. If you are not really buying a Cloud service, why should your contract include Cloud-like terms, which are typically very provider-friendly? There is a real risk here for enterprise buyers – a double whammy, if you will: You’re potentially buying legacy technology, and you’re getting unfavorable terms to boot. No CIO wants to be in this position.

How can you avoid this sticky situation? Given that there continues to be extensive debate about what is “true” Cloud technology, it helps to dispense with the term “Cloud” and instead think of the technology as a continuum, as shown here:

Stantonbloggraphic

As you can see, if you’re buying a custom solution, you should fully expect a more customized agreement. As the technology solution you’re considering becomes more standardized, so should the terms and service levels. It’s a fair trade-off, as long as you have all the information you need to make a rational decision. As expected, service providers have a lot more information about the solution than you do, so it’s up to you to dig for more.

A great starting point is the National Institute of Standards and Technology (NIST) definition of Cloud Computing. The industry has (for the most part) agreed to this definition, so pull it out when you’re talking to your salesperson — but don’t stop there. Ask your Cloud provider other, more-probing questions. For example, does the provider’s application programming interface (API) framework remain stable when rolling out new features? What level of automation is in place for provisioning and failover? Answers to these questions will help you to understand where the service sits on the continuum.

Remember: the more Cloud-like the service, the more you should expect to see contractual terms and service levels that favor the service provider.

Bottom line: Dig deep into the nuts and bolts of the service you’re considering so that you don’t end up buying legacy technology underpinned with a Cloud-like contract.

Originally posted by Stanton Jones, Vice President & CIO, TPI on Consider the Source

Blogger Profile: Consider the Source
TPI is the leader in guiding organizations through effective, lasting transformation of their business support operations. Around the globe we have helped hundreds of clients reduce operating risks, streamline complex operations, improve the cost of support functions, achieve sustainable improvements and make competitive gains. Decisions to change and successful transition of existing operations to new service delivery models is hard — and replete with risks. While the decisions are never formulaic, the hard-earned lessons of hundreds of prior evaluations are invaluable.

Posted by Sue Ansell at September 14, 2011 8:15 AM

Categories: Cloud computing Outsourcing

Comments

Name
URL (remove the http://)
Email
Comments (field is limited to 2000 characters)
   

TrackBack Link

Bookmark and Share           Print Page          Email To A Friend
Start Me Up Innovation Campaign winner

WCIT C200 Investment Forum


Insightful business speaker Jim Harris talks innovation in 
Speaker's Corner 

Backbone magazine Speakers' Corner 

Backbone magazine latest digital issue

Backbone's Cloud Portal

Backbone's Digital Economy Acceleration Committee

Backbonemag on Twitter