Cloud • Governance • IT Strategy & Business Alignment

Cloud Contracts – The Hidden Costs & Risks

Cloud Contracts – The Hidden Costs & Risks

This is an audio conversation from the CIO Talk Network podcast. The timestamps in the chapters and transcript below refer to the audio recording.

About this conversation

A CIO Talk Network conversation with John Engates (Rackspace), Thomas Trappler (UCLA), Tom Struan (Army Aviation Center Federal Credit Union), hosted by Sanjog Aul.

What the conversation established

The conversation established that effective cloud use is still in pockets, with John Engates of Rackspace saying startups and smaller companies are often 100 percent cloud while traditional IT shops are at the early stages. Thomas Trappler of UCLA argued the contract tells the story of the relationship, and named the minimums to cover: a security certification such as ISO 27001, SLAs with metrics and remedies on the top 5 to 10 elements, and data access, ownership, and location, plus what your cost is next year and how you get your data back at the end. Tom Struan of Army Aviation Center Federal Credit Union said price is a consideration but not the most important one, cited moving phones to the cloud over SIP trunking with no cost savings, and said he weighs cultural fit, even paying more for it. Engates compared the customer relationship to a marriage, where reaching for the legal document means it is almost too far gone.

Host Sanjog Aul talks with John Engates, Chief Technology Officer at Rackspace, Thomas Trappler, Director of Software Licensing at UCLA, and Tom Struan, Senior Vice President of IS and Chief Information Officer at Army Aviation Center Federal Credit Union, about the hidden costs and risks in cloud contracts. They discuss why the value of cloud can be undermined when procurement turns into a price war, and what minimum terms belong in a contract and SLA. Trappler lays out the categories to cover, from ISO 27001 and SLAs to data ownership, location, and exit terms. Struan explains why he weighs reliability, security, and cultural fit over price, and Engates describes where a provider has to say no.

Contributors

  • John Engates, Chief Technology Officer, Rackspace
  • Thomas Trappler, Director of Software Licensing, UCLA
  • Tom Struan, Senior Vice President of IS and Chief Information Officer, Army Aviation Center Federal Credit Union

Host: Sanjog Aul, Founder and Host, CIO Talk Network

On this page: Key takeaways · Chapters · Explore more · Transcript

Key takeaways

  • John Engates, Chief Technology Officer at Rackspace, says effective cloud use is still concentrated in pockets rather than universal. He points out that many startups and newer web companies are 100 percent cloud, while traditional CIOs and IT shops are still at the early stages of deciding which applications go first.
  • Thomas Trappler, Director of Software Licensing at UCLA, says the contract between a cloud vendor and client essentially tells the story of the relationship going forward. He advises codifying the vendor’s practices and certifications in writing, including a security standard such as ISO 27001, SLA metrics and remedies on the top 5 to 10 elements, and terms for data access, ownership, and location.
  • Tom Struan, Senior Vice President of IS and Chief Information Officer at Army Aviation Center Federal Credit Union, says price is a consideration but by far not the most important one. In his financial services environment reliability and security come first, and he moved phones to the cloud using SIP trunking for resilience rather than for any cost savings.
  • John Engates of Rackspace says a provider sometimes has to tell a CIO no when they try to customize the public cloud too much. He explains that cloud saves money through standardization and automation, so a customer who wants it black or red or painted white with stripes does not fit the public cloud model.
  • Thomas Trappler of UCLA warns against expecting a vendor to grant 100 percent indemnification for all situations. He says any vendor that offered that right off the bat should worry you, because covering every client for every data breach could put the vendor, your partner, out of business.
  • Tom Struan of Army Aviation Center Federal Credit Union says he weighs cultural fit as much as anything else when selecting a cloud provider. He has bypassed cheaper options for a better cultural fit, giving the example that a bank that prides itself on answering the phone does not make callers pass through five touchstones before reaching a person.

Chapters

  • 0:00 Introduction: cloud contracts, hidden costs and risks
  • 3:24 Where cloud is already delivering its benefits
  • 7:41 Trust and transparency with a provider
  • 11:16 Minimum tenets of a cloud contract
  • 13:51 Two customer types and tailored SLAs
  • 19:25 How much assurance is enough
  • 28:31 Reliability and security over price
  • 37:12 Who mediates a stalemate
  • 41:06 Clouds tailored to specific industries
  • 47:39 Gray areas in the handoff
  • 51:59 The shift to a contractually managed solution

Explore more

Transcript

Introduction: cloud contracts, hidden costs and risks 0:00

Sanjog Aul [00:01:00]:
Today’s topic is cloud contracts, hidden costs and risks. And our guests for today’s show are John Engates, who is the chief technology officer with Rackspace. Good morning, John. How are you?

Sanjog Aul [00:01:27]:
So we also have Thomas Trappler, who’s the director of software licensing with UCLA and instructor and contracting for cloud computing services at the UCLA extension. Good morning, Thomas. How are you?

Sanjog Aul [00:01:59]:
And we have Tom Struan, who’s the senior vice president of IS and the chief information officer for Army Aviation Center Federal Credit Union. Good morning, Tom. How are you doing?

Sanjog Aul [00:02:31]:
So, by the way, the topic that we picked up, the genesis of this topic is because a lot of times when people are talking about cloud, while the value proposition is there from the very offering standpoint when sometimes the devil is in the detail when you start procuring such services. And some people have expressed paranoia and or actual, with their experience said that sometimes SLAs and contracts are the ones where, we have challenges in coming to terms with what we want versus what the provider wants to provide. So with that said, John, you are, the chief technology officer of one of the well known, cloud provider. Now it is supposed to deliver scalability and all the different goodies that is promised. To what degree do you think those goodies are being delivered truly?

Where cloud is already delivering its benefits 3:24

John Engates [00:03:24]:
Well, look, I think that there are plenty of customers that are using cloud effectively. They’re getting the benefits that they seek. They’re looking for low cost. Sometimes they’re looking for agility, the ability to turn things on and off very quickly, pay for what they use. Those things are all very real. The trouble, I think, with the whole thing is that not everyone’s using cloud yet. I think that we’re just sort of at the tip of the iceberg in terms of how much folks out there in IT are using it. And I say IT, but it’s really the startups and the smaller companies that are using it more effectively, because many of them are 100% cloud at this point. Many of the new companies that have new applications meant for the web, those guys are the ones that have gravitated to cloud early. And I think it’s CIOs, it’s the more traditional IT shops that are sort of still at the early stages of cloud computing. And they’re trying really to get their head around what cloud is for, where they should use it, what applications are primed to go to cloud first. And that’s just a journey that I think we all have to go through. So I think effective use of it is in pockets. It’s being used effectively by some, but not everyone.

Sanjog Aul [00:04:40]:
So now with that said, Thomas, the question for you is that as you look across multiple organizations and as you go about doing the research, do you think that we have built something which is like a Ferrari and we want to just go to our offices, which is this that which in a way means that we have built something which is such a huge undertaking, but the usage of that is limited to what we currently had been using. Thus, the value of what we place on what is offered is undermined and that’s why we would get into this price war thing.

Thomas Trappler [00:05:14]:
I think with cloud computing, it’s still a new and evolving market space. Kind of piggybacking on what John is saying, not everyone is in all the way yet. But I think it’s still change, it’s still the name of the game. New vendors are coming and going. Existing vendors are continuously changing their services. I think that’s one of the reasons that I like to think of making sure everyone’s an educated consumer of the cloud, even if they’re just getting their feet wet. That’s why in my class, contracting for cloud computing services, we highlight, for example, the importance of understanding cloud computers infrastructure and security mechanisms and practices before you adopt that service. So going in with your eyes wide open.

Sanjog Aul [00:05:57]:
So Tom Struan, this is a question for you. When you are looking at the overall cloud adoption, do you think we are years away from really making the best use of it?

Tom Struan [00:06:09]:
I don’t know if we’re years away from making the best use of it. I think we’re years away from making a total use of it. Either there are still applications, I’ll say, internally. I’ve got a mainframe computer, and people have talked about the death of the mainframe for 20-something years almost. And here I am sitting in 2012 with a mainframe server sitting in my environment. That said, whenever we’ve looked at new solutions, we are looking to the cloud, partly for scalability, somewhat for cost control or cost containment or even cost stabilization. But you really get out of the cloud what you put into it. And that includes your thought process and looking at how your operations are driven and benefit from the cloud, in general.

Sanjog Aul [00:07:02]:
John, if we were to look at any organization which otherwise had everything captive and traditionally that’s what’s been the case for IT. Now when we are going to cloud, infrastructure, especially with public cloud infrastructure, people are literally giving away their lifeline to someone else. How easy is it being made for someone to be able to sleep at night? And secondly, when somebody else is holding your lifeline, how much are we being like bean counters when you talk about IT leaders versus being an investor and or somebody who says pay more and smile and at least let the cloud provider give me what I want. And in exchange, I give them what they want.

Trust and transparency with a provider 7:41

John Engates [00:07:41]:
Yes. I think you are putting responsibility into the hands of someone else. And in that way, it’s a bit like you have to really trust that other organization, do the right things. You have to have transparency. I think transparency is really the ultimate name of the game, I guess, in terms of a cloud provider’s level of trust that you’re going to place in them. And I think if you’re working with a provider that isn’t transparent, you have a real challenge in understanding what the responsibilities are, who’s going to do what, what are the expectations. So we’ve really, as a company, tried over the years to be extremely transparent, almost at the extreme end of the spectrum. And I think that helps with the trust factor. I think a lot of companies, as they start to think about moving IT out of their own data center, out of the corporate data center into a cloud facility of some sort or into a service provider, they have to really do the diligence. They have to start to think about who they’re doing business with, what kind of track record they have, what kind of level of visibility do they have into the cloud providers’ operations and policies and procedures, what kind of certifications they have. All of that stuff plays into this. But on the other hand, I don’t think it’s all that different than many outsourcing contracts that CIOs have been doing over all these years. We’ve been allowing other companies to run our operations and our processes and our systems for us in outsourcing for decades. And cloud computing is a new flavor of that concept. It’s somebody else running your infrastructure, maybe managing your applications for you, and giving it back to you as a service. But as long as you’re doing the diligence and you have some visibility and some transparency, I think CIOs can get comfortable around it. I think it’s just sometimes fear, uncertainty, and doubt that creeps in. But realistically, if you do the homework, you can get there.

Sanjog Aul [00:09:45]:
With that said, Thomas, if you look at the trust factor and one of the things which was put forth by John is the transparency, is that alone responsible for instilling trust, or is there something to be said about performance? And especially if it’s a newer field, how does one have a track record so it becomes like a catch? Chicken and egg story for that matter. That while I can open up my what I’m doing, but I still am newbie, I’m new kid on the block, but I have all the best intent. But does that instill trust?

Thomas Trappler [00:10:17]:
Well, I definitely agree that transparency is important. Going in again with one’s eyes wide open, understanding what the cloud vendors’ standard practices, infrastructures, procedures are, but then ultimately understanding those and then codifying them in the contract. The contract between the cloud vendor and the client essentially tells the story of the relationship between the client and the cloud vendor going forward. So it’s essential that it captures in writing who’s responsible for what, who’s going to do what, what are the minimums. That understanding that you had when you were analyzing that service before adopting it, you’ve been told things, you’ve been given certifications, etcetera, then you just want to put them in the contract so everyone’s on the same page going forward and knows what their responsibilities are going forward.

Sanjog Aul [00:11:04]:
So what are the typical tenets of a contract where when you say at least the minimum should be there? So, Thomas, in your view, what should be those minimums?

Minimum tenets of a cloud contract 11:16

Thomas Trappler [00:11:16]:
So you definitely want to think about infrastructure and security, as I mentioned earlier. Perhaps there’s a certification in place, ISO 27001 for example, maybe you make that your minimum. If not, you spell out the elements of that that are important to your use of the service and make those individual elements the minimum. You want to think about SLAs, service level agreements. Think about what are the top 5 to 10 elements of this service that makes it attractive to you as a client and put in their metrics and minimums to measure against to make sure those are met as well as remedies if they’re not met. You want to think about data, data access and storage and ownership and location. As a client, you’re now entrusting the cloud vendor with your data. You want to know that they’re treating it in a secure fashion where you might want to know where they’re keeping it, so you know what laws are applying to it, etcetera. You want to affirm that you own it and the results of any processing of it. And then thinking about this is a long term relationship. Thinking about what is your cost next year? What happens at the end of the contract? How do I get my data back in what format, etcetera? Those are kind of some of the key categories.

Sanjog Aul [00:12:30]:
So question for Tom Struan. When you look at these, different elements that Thomas has listed for us in terms of the bare minimums of what a cloud contract and or SLA can have. Now can you see this being a common denominator across all industries or certain portions are relevant to, say, yours, which is in financial services, and it could be different for a retail or a manufacturing?

Tom Struan [00:12:56]:
I agree with Thomas that there are a lot of common elements. I think there security is definitely one of them. I think every organization, no matter what industry you’re in, you have certain proprietary data that you may want to keep secure. Clearly in financial services dealing with other people’s money, we may prioritize that to a certain extent to where maybe it rates number 1 in our matrix, whereas maybe someone in the industrial sector may classify as a number 5. And so I think there are some common elements where you place those elements may vary.

Sanjog Aul [00:13:31]:
So, if we were to come back to you, John, and say, if you as you look across the customer portfolio, what kind of flavors do you think have been requested of you when it comes down to the SLAs and the terms and the pricing models for that matter?

Two customer types and tailored SLAs 13:51

John Engates [00:13:51]:
Yeah. I think there’s sort of two major categories of customers that we deal with here at Rackspace. I think we have sort of the customer that I would call the do it yourself customer who really wants to buy cloud computing, cloud infrastructure in a more very much a pay as you go. I almost call it the vending machine model, where they wanna walk up to the vending machine and put their money in and get something out immediately, and maybe walk away from that. That’s sort of the public cloud customer, the very lightweight, pay as you go kind of a customer. Then we have the other type of customer that’s more of a longer term customer. They’ve got a very consistent footprint in terms of their infrastructure needs. They’ve got some service and support needs that are ongoing. They want to pay someone to help them with the management of the infrastructures. The access to expertise is important to them. And I think the needs of those two different customers are reflected in the contract and in the SLA expectations. So we certainly tailor our contracts and our SLAs to those different customer bases. I think, because the expectations are different in terms of how they negotiate and how they expect to be compensated for failures and things of that sort, we have to tailor those to those different customer bases. And so, for example, an enterprise CIO would come to us and be much more likely to want to get into the details of the SLA, be much more likely to negotiate different terms based on what’s critical and important to him. He would very likely specify the types of things that, I think Thomas was saying that we need security well defined, we need certain certifications like ISO spelled out, we need locations and specific specifications around what the cloud looks like and how it grows and how it expands. Those are all reflected in contracts and SLAs that we write. And again, they’re very flexible. We have ways of encompassing things that are very important to one specific industry or one specific type of customer. And then again, we on the other end of the spectrum, we have sort of the one size fits all that the do it yourself cloud guy needs. He just many times wants something that protects him but doesn’t really wanna negotiate, doesn’t wanna spend a lot of time on it, just wants to get up and running.

Sanjog Aul [00:16:22]:
And, this is a question for you, Thomas Trappler, that when we are coming in and we are trying to negotiate these contracts, how much is enough typically for an enterprise IT leader to feel that I got enough assurance and I can feel warm and fuzzy. Is there and, of course, there it cannot be cut and dry, but are there some specific areas in which when you get up to a certain level of assurance that is provided, in numbers and or in terms of how the operations are run, which will allow them to sleep at night.

Sanjog Aul [00:18:54]:
So, Thomas Trappler, the question for you is how much is enough when it comes to laying out the SLAs, the terms, at what point when enterprise IT leader can sleep at night peacefully, and also at what point the provider can also live up to the expectations set by them. Sometimes they could get overaggressive perhaps in terms of giving it away, but then it will be the disaster because they will not be able to live up to it. What’s that fine line? How do we draw that?

How much assurance is enough 19:25

Thomas Trappler [00:19:25]:
In my class, I always tell folks upfront, unfortunately, I’m not giving you the silver bullet answers here. But what I’m trying to do is give you the issues to consider and the questions to ask. And the answers are going to vary on a case by case basis depending upon the client organization’s unique needs and tolerance for risk, as well as the specific parameters of each use case or project that they’re considering moving to the cloud. So what they need to do is think about what kind of data they’re going to put out in the cloud, for example. And it’s somewhere on a spectrum of publicly available data, non sensitive data, all the way to regulated data, sensitive data, health data, secret formula type data. And then the other end of the spectrum is kind of the business criticality. What’s the client’s pain point if this service becomes unavailable? Now could you make do for a couple of days? It’s no big deal? Or does your business come to a grinding halt? The further you are in that kind of sensitive data grinding halt side, the more you need to think about these factors and make sure they meet your needs.

Sanjog Aul [00:20:31]:
So Tom Struan, question for you. What type of an agreement would you like to see and or suppose your buddy CIO in another organization was trying to sign something up? At what point you will caution, hey. You are asking for too much. This is gonna drive the provider down, and they may not be able to deliver. On the other hand, if you were greatest friends with John Engates and he’s signing a contract as a provider, you’d say, you know what? You’re giving him too much, and you may fail because of that.

Tom Struan [00:20:59]:
Oh, clearly, there’s sort of an ongoing battle of sorts. I think a lot of service providers, not all, for cloud services, they don’t like to say no to the customer. They wanna deliver everything. And that’s clearly not entirely possible. At the same time, the customer, they want the moon, they want the stars, but they’re not really necessarily sometimes understanding that all they’re going to get is the moon. And there is that little bit of conflict. I always caution we’ve done a number of cloud deployments here and I always caution other CIOs, other credit unions when they talk to me about going out to the cloud for a service. The number one thing I tell them is, clearly define your expectations and try and live within them. Don’t come back later on to the service provider and say, hey, we thought this was gonna happen. Really define what you’re trying to accomplish, and then live within that. And then later on, it’s clear, it’s perfectly fine to go back to the service provider and say, hey, have you enhanced your service in any way that we can expand X, Y, and Z? But a lot of my peers, they do go in with blinders on and think that they’re gonna get the stars and really all they’re gonna get is the moon.

Sanjog Aul [00:22:15]:
So Tom, again, the follow-up question to this is, we’ve typically seen that CIOs have a specific idea or IT leaders and their lieutenants or a group which is working on procuring the cloud services have an idea what they want. But then comes procurement, who wear a flag on their chest just because they were able to save a nickel. And there, something could be lost in translation. How do you prevent that from happening?

Tom Struan [00:22:49]:
Well, I think one of the ways I prevent that from happening is, when we draw up our contracts, we draw up all the key points first inside of our team. And we sit down with our legal counsel and look at how we want the wording to be structured a little bit. Then when we work out the cloud services agreement, we look and see how closely those two items mesh and then work out an agreement with the cloud services provider to negotiate any unclear points. And there are sometimes when the cloud provider comes back and says, look, we just don’t have that capability or we’re gonna have to sacrifice a little bit on this particular item. And as long as we know that upfront, we’re fine. I think most CIOs are in the same boat.

Sanjog Aul [00:23:41]:
So, John, when you are, say, on the provider side and, depending on what the case is, at what point would you say no to a certain item, and what would those items be when it comes to provisioning under the contract?

John Engates [00:23:55]:
Yeah. Well, look, I think cloud computing, one of the key tenets of cloud computing is that we’ve got a lot of standardization within the platform. We’ve got some very specific choices in terms of hardware and it’s a menu. It’s a menu that is sort of well predefined and it’s well defined. And I think what we have to do as a provider is keep the CIO or the buyer from trying to take cloud computing and customize it too much or take it and try to turn it into what he’s had all along in his own data center where he’s had ultimate flexibility, ultimate choice, any brand, any model, any piece of equipment or software that he wanted. I think cloud computing, the reason we can save money in cloud computing is because we’ve gone to a bit of standardization and automation and things are prescribed a bit more. And I think that is a bit of a challenge sometimes for a CIO who’s had a carte blanche in terms of being able to choose everything. And so one of the things we have to say no to is sometimes that request that comes across that the customer wants this or that. He wants it black or red or painted white with stripes. And we just can’t do those kinds of things within the cloud computing. The good news is that Rackspace as a company and I think some other vendors in our industry, they do have degrees of what is considered cloud computing. I think from a CIO’s perspective, it depends on maybe what kind of a CIO you are. Sometimes cloud computing can be defined as anything outside my data center that I pay for as a service. I think, if you’re a Silicon Valley startup, I think cloud computing means I pay for it by the hour, and it scales up and down in those very fine grain increments. But many CIOs nowadays really look at it as just some way to get infrastructure out of their data center, stop paying for capital expenditure, start paying for operational expenditure, and get that sort of flexibility and agility that they’re looking for. It doesn’t necessarily have to be pay as you go, pay by the hour. And so when you put it in that context, there is a degree of customization that can be done. There is a degree of tailored, bespoke type offerings that we can offer to customers that maybe aren’t quite fitting the purest’s definition of cloud computing, but certainly are a lot more cloudy than what a CIO might be doing in his own data center. So we don’t have to say no to everyone, but we do have to say no to the guy that wants us to really customize and tailor the public cloud.

Sanjog Aul [00:26:39]:
So, this is for Thomas Trappler. When you are going out and trying to have these students being taught and or at the same time talking to a lot of providers and the enterprise IT folks who are trying to procure the service, what is it that they feel they should be getting which they are not getting today when it comes to an equitable distribution of on one side provider gets what they want in terms of the right number of dollars and the terms. And on the other side, enterprise what’s it wants.

Thomas Trappler [00:27:18]:
Oh, well, I was teaching in the Midwest last month, and one of the participants in the class asked, what contract provisions should I not ask a cloud vendor for? What one should I just not bother? And my response was, the only things you shouldn’t ask for are those that you don’t need. I still think since the cloud is a new and evolving market space that if the clients don’t tell the cloud vendors what they need, the vendors won’t know how to align their services with their clients’ needs. I think it’s new on both sides. Not all vendors understand every client’s needs. And it continues to evolve. And as clients speak up and share the same needs, I think vendors can understand those and try to, when possible, tailor their services to meet those needs and in some circumstances distinguish themselves amongst their competitors in that way.

Sanjog Aul [00:28:07]:
So, Tom Struan, question for you. When you’re going in as a buyer, do you really think or is your community thinking as enterprise CIO that I really need to be equitable or you’re just going out there to get a bad deal? Is it more a price shopping or is it value but at the same time keeping interest? And I’m not trying to generalize and I’m not saying that you’re doing price shopping. What’s the trend out there?

Reliability and security over price 28:31

Tom Struan [00:28:31]:
I would say that amongst most of my peers that I talk to, price is a consideration, but is by far not the most important one. In my line of business, reliability and security are key. We got to keep the lights up no matter what. And that means, between certain hours, we’ve got to have certain functions available. I’ll give you example. Phones, we go to the cloud for our phone using SIP trunking. And it’s not a new technology. It’s not a really old technology. It’s a mid level technology. But those phones about us have to stay up no matter what. It’s a member service issue for us and that’s just part of the industry that we’re in. So we didn’t necessarily look at that as a cost savings. In fact, I would tell you that there really is no cost savings for us. We did it because the cost of deploying a diversified infrastructure using traditional telephony is just phenomenally a challenge. But also the physical infrastructure managing that, aside from a cost viewpoint, is a challenge. So we went to the cloud and it’s been a great decision for us. But we did not go in with blinders on. We knew we weren’t going to be able to have everything that we had before, that there were going to be some sacrifices. And in reality, we ended up getting more than we had before because just the very small incremental cost to add a certain feature is available in the cloud where it wasn’t available by deploying our own infrastructure.

Sanjog Aul [00:30:19]:
John, the question I’d like to put in front of you is that while you are asked, for the moon as a provider that you give me anything that you can and then, of course, they will talk to you about pricing and reliability and everything. But I’m sure there are many times, the failure and or lackluster performance is not only because of a provider. There could be some contribution in a negative way by the very enterprise which is procuring it. So what are those? Where would you, if you had a choice, go and tell some of your customers, guys, if you want my organization to really deliver up to your expectations, then these are the five things I would like you to make sure that you do within the organization.

Sanjog Aul [00:33:01]:
So, John, as I posed the question before, the companies want the world from you. But at some point, you also could perhaps tell them this is what they should be doing differently.

John Engates [00:33:12]:
Yes. So I think Rackspace, as a company, we’ve really tried our best to engage with customers early in terms of their cloud strategy. We have a group here at Rackspace that does advisory services. They spend time with customers upfront. And they try to figure out, with the enterprise, working hand in hand, what kinds of applications are ripe for the cloud, which ones are not so good for cloud computing today, which ones may be ready down the road. My sort of quick and dirty advice to a CIO is that any application that’s in a state of change or potential change, any application that needs a refresh or the infrastructure needs a refresh or there’s updates happening, those are the ones that you should look at as a potential move to cloud computing. There’s really no reason to go and look for applications that are steady state, that don’t really have any change underway. It’s sort of like, if it isn’t broke, don’t fix it kind of mentality. But there is a lot of change going on at an IT department all the time, there’s change. There’s new application patches. There’s updates to software. There’s hardware that’s failing or end of life. And those are all opportunities for an evaluation of cloud computing. And then when you take an application and you sort of evaluate it against the cloud, you sort of can use a fallback strategy. Is this application right to go to software as a service? Well, maybe not. How about platform as a service? Possibly, but maybe I need more customization than that. So then Infrastructure as a Service. If it doesn’t work against Infrastructure as a Service, it may work well in a hosting environment with a dedicated private cloud, or maybe a private cloud on premise, or maybe it just stays put. I think those are all options that a CIO has to sort of weigh when he’s looking at a move to cloud computing. It’s not all the applications all at once. It’s got to be done in a measured way in a pace yourself kind of an approach.

Sanjog Aul [00:35:21]:
Now, with that said, Thomas Trappler, this is the question I would ask you. When you are looking at these enterprise IT folks and you are teaching folks who are students, and I’m sure you’re also being called upon to talk to executives and providers, what is it that you found them to be doing which could be the very reason sometimes or their mindset could be the reason why they are facing more problems than others?

Thomas Trappler [00:35:48]:
Well, I think one of those areas where there’s always two sides of the argument is thinking about if something goes wrong, who’s responsible for the costs, etcetera. So indemnification, limitation of liability. On the client side, and I negotiate these as well as teaching, client 100% indemnification, all the costs are covered. I would tend to think that if any vendor gave you that right away, right off the bat, you should probably worry. Because any vendor who could indemnify all their client base for all situations could be out of business, if one sort of data breach comes up and none of us wants the vendor to be out of business. They’re our partner, we’re going forth, we’re dependent upon their service. So you need to find a balance in that indemnification area.

Sanjog Aul [00:36:41]:
So when we come back and when we actually come back to this point where the CIOs want the most and the providers want to provide the most, but they simply do not have the ability given the price point of the negotiations are forcing them to cut corners, who comes to mediate that? Tom Struan, your question for you here. Who should come to mediate that? Because there could be stalemates, isn’t it?

Who mediates a stalemate 37:12

Tom Struan [00:37:12]:
Oh, goodness. That’s a pretty challenging question. When you’re dealing with two different parties, sometimes if you’re talk about the expectations from like internally from another operating segment of the enterprise and maybe a cloud provider, then clearly the information services area would get involved and try and mediate that. But if you’re just talking about an IS driven decision and then the third party, sometimes that gets a little bit challenging. So we tend to really try to drive that through a third party mediator, an independent person. We always try to make sure that we have those clauses in our contracts and we specify a mediation service in our contracts just because and it’s not necessarily one that we pick, but we find that that really has helped us out in the past because we go to the cloud for a lot of our infrastructure even. And we’ve had hiccups like that. And it’s just been really good for us to have a third party come in and say, look, the contract says it, however, in the interest of fair play, maybe we can work something out. And we come to an agreement that way without getting a bunch of lawyers and a bunch of courtrooms involved.

John Engates [00:38:31]:
Yes. I’d like to add something to that, if I could. This is John Engates. The idea of a contract or an SLA, our philosophy on that is, the relationship between a customer and a provider is a bit like a marriage. If you’re referring to a legal document in a marriage, you’ve got some serious problems, and you really at that point, it’s kind of almost too far gone if you’re at that point. And we sort of think the same way about the relationship between us and our customers. We don’t really want to be referring to the nitpick points inside of a contract or a legal document. We oftentimes on the side of, if the customer thinks we’re wrong, we’re probably wrong. And we don’t really spend a lot of time defending and arguing about who was right, who was wrong. Because at that point, it starts to really have serious ramifications for the relationship between the two parties. And so we don’t really want to get to that point. I think Tom’s right in terms of how it plays out. Sometimes, very rarely do we ever get into a legal situation, but that’s really the exception and not the rule.

Thomas Trappler [00:39:47]:
Sanjog, I was just going to also chime in that the challenge, and you touched on this earlier, is that there aren’t always really two parties. Even though there’s a client and you consider them one party, the client is made up of a business process owner who probably really wants that cloud service right away because they’ve got a business need to fulfill. But it’s also made up of their procurement folks and their legal folks and their risk management folks who are only thinking about the risk side and not the benefit side. And then there’s the IT folks who are thinking about the technical side and the vendor management folks, etcetera. So I always try to tell my folks, have a team in place on your side. Each one of those folks is going to be like the blind men and the elephant seeing different parts of it. And that’s their jobs and that makes sense. But they have to come to a consensus of all those different parts to be able to speak with one voice to the vendor. But that’s just an additional challenge.

Sanjog Aul [00:40:44]:
Now with all the challenges that you’re finding, do you think we are somehow able to get by? So, John, a question for you. Do you think with all the different instances that you might hear, whether with you as a cloud provider or anyone else, somehow, do you think the cloud is getting provisioned and life is beautiful?

Clouds tailored to specific industries 41:06

John Engates [00:41:06]:
Well, we’re always getting better. We’re always improving. We’re always learning. Every day, every new customer we interact with, we learn something new and we adapt. And I think the cloud is the same. The cloud is, at the beginning, it is relatively plain vanilla. There’s 1 or 2 providers with 1 or 2 service offerings. They look pretty much the same. I think what happens over time is that we start to see specific service offerings that are tailored to a specific customer. You might have a cloud that’s well suited for one industry, maybe government, maybe banking, maybe health care. You start to see people create clouds and create service offerings that are really tailored to those industries. And that will help with the adoption of cloud computing. I think we can’t assume that the whole world is going to go to a plain vanilla cloud. It’s a little bit like Henry Ford’s car back in the early 1900s. It was 1 car, 1 color. And over time, what we’ve seen is that people need different kinds of cars. They need trucks, they need SUVs. And I think the cloud is a bit the same as that. We need to have different flavors and different offerings to suit the different needs.

Tom Struan [00:42:21]:
And this is Tom Struan. I just want to interject something there a little bit. We typically look as much at cultural fit when we select a cloud provider as anything else. And we have bypassed others that have come in much cheaper, but who we felt didn’t fit our culture and gone with someone who’s been a little bit more expensive, but has a little bit better cultural fit for us as an organization.

Sanjog Aul [00:42:47]:
Now what do you mean, if somebody were to ask, what does cultural fit have to do with someone who’s not gonna touch your organization inside? They may be just to provide a delivery service.

Tom Struan [00:42:56]:
If you’re providing me a service, you’re touching my organization whether you, whether it’s at multiple points in many cases. So I’ll give you an example, for Internet banking. It’s somewhat of a commodity now. There’s a number of providers and you can go with a number of different players. But really when it comes on to it, your customers have a huge reliance on that product and there are multiple pain points to be experienced. So you need someone who’s got a similar culture to you. If you’ve got an organization that really prides itself on picking up that phone, you’re not gonna get five touchstones before you hit a person. If that’s the kind of organization you are internally, which we are, then that’s the kind of cultural fit that you need to seek in the cloud. And that’s just one example.

Sanjog Aul [00:43:59]:
Now with that said, now when we are looking at the evolution of this relationship and expectation setting, what is the next frontier? What are you expecting? What’s not there today? Or the level of sophistication or the level of detail that we’re looking at? Tom Struan, this is a question for you. What is left to be desired?

Tom Struan [00:44:21]:
I’d say the one thing that we’re looking for, going forward from our cloud providers is that not necessarily the flexibility. There’s this whole be all and end all kind of approach. But we’re really looking for, how can the cloud provider become more of a partner with us and really consider our pain their pain. The evolution of that relationship is more important to us from that point of view than it is the technology that they provide. Because the technology is going to continue to evolve. That is just the nature of the beast. Because if it doesn’t, if that provider doesn’t continue to evolve technologically, you’ll be forced to leave them no matter what kind of relationship you have with them. But the relationships for us are more important in terms of the evolution of it.

Sanjog Aul [00:45:18]:
Now would you think, and Thomas Trappler, this is question for you. Do you think there are standards and benchmarks and other yardsticks, if you will, that people have at least started working towards developing so that while one is to deliver technology as a cloud provider and also to consume it as an enterprise out there, do you think we are moving towards standardization of the procurement process as well where both sides eventually meet? And also the risks are highlighted versus leaving it to individuals or that particular group’s awareness from what the best is out there?

Thomas Trappler [00:45:57]:
Again, it comes back to this list of questions to ask. And is there a way that each of us don’t have to ask the same questions over and over again and the cloud vendor doesn’t have to answer them over and over again. There are some standards evolving in terms of questionnaires for infrastructure and security. The Cloud Security Alliance has a questionnaire in this area and there’s a shared assessments group has a questionnaire in this area. And for example, about certifications for security and infrastructure. Cloud vendor doesn’t want every one of their clients coming out there and auditing in person probably. But the client wants to know that what the vendor says they have in place, they do have in place. Is there sort of third party certification? There’s no one standard but some of them that are servicing are the ISO 27001, 27002 for the federal government folks that FIPS 200 is one example. And even if you’re not in the government, you can still leverage that certification as knowing, maybe that still meets my needs even if I’m not in the government and not required to go that route. And then there’s audits like the SSAE16. Whichever one of those certifications or audits are happening, they all result in a report with details behind it, not just a seal of approval. So the client organization always wants to make sure that they have the right to get a copy of that report and review it to again know at a granular level that the vendor’s infrastructure and security and practices etcetera are meeting their needs.

Sanjog Aul [00:47:30]:
Now, if I were to come back to you, John, and say, tell me two or three gray areas which you still persistently struggle with.

Gray areas in the handoff 47:39

John Engates [00:47:39]:
Well, I think the number one gray area is always the handoff between a customer and Rackspace and really any provider, not just Rackspace, but any provider within sort of that level of responsibility. A lot of customers bring an application to us. They own the application. They wrote it or a third party wrote it. But there’s a touch point between an application and infrastructure that sometimes it’s at the operating system level, sometimes it’s at the application server, sometimes it’s where the database and the application server talk to one another. And code that a customer brings to a cloud may perform differently than it did in house. It may perform differently than it does at another cloud. And so that is probably the number one gray area is that level of the gray area between what customer responsibility ends and where provider begins. I think clearly spelling out that stuff upfront is important. Having clear guidelines between the two parties or multiple parties, if there’s a third party developer in the relationship as well. Also, kind of who does what in terms of a response. Like, if a failure happens at 3 in the morning, what do you want us to do? How do you want us to respond? And I think getting that defined, documented, and codified upfront is the key to a successful relationship there. And it’s something that we do with all of our large customers, our customers that have managed services with us. And we found that that’s the secret to success.

Sanjog Aul [00:49:31]:
So when you say that these are the gray areas now, do you think as your service offering or your other cloud provider community service offering is changing, do you think there are some areas that you already see are gonna become pain points which you yourself will have to grapple with and or educate the customers with? Because I’m sure there are nuances in the way different service offerings are procured as well as provisioned. And then you will see that those will start creating. So can you proactively prepare for something like this? For both sides.

John Engates [00:50:06]:
Look, I think what you have to have in place is sort of a philosophy around how this stuff is going to work between you and your customer. I think if you’ve got a general set of guidelines about how you want to operate, how you want to be transparent, how you want to communicate, any new offering that you create is sort of going to fall in line. I think, if you’re a company that has the right culture, I love that the topic of culture came up because culture is extremely important to us. It’s something that we spend a lot of time on here at Rackspace, and we do think that it leads to a better outcome. And so once you have that foundation of culture in place, once you have some guiding principles and some things that your company is going to do no matter what kind of a service offering you have or what changes in the environment, well, that starts to give you those guideposts and those pillars that are going to stand strong no matter what changes in the environment. And I think that’s what leads to great customer outcomes. Again, having the frontline employees knowing what to do in a situation, knowing how the CEO would respond because he knows the core values of the company, those are gonna be helpful. If you’re a company that is not very transparent, if you’re a company that doesn’t like to open the kimono and show what’s going on behind the scenes and a company that doesn’t really communicate with customers, then, in a situation where things go wrong, you’re really at a loss because you don’t have a relationship with a customer. You don’t have a way to really communicate well with a customer. There’s no trust in place. And I think that’s really where you’re going to see a difference between different providers.

The shift to a contractually managed solution 51:59

Thomas Trappler [00:51:59]:
From folks who are new to this arena, it’s important to keep in mind that adopting a cloud computing service does entail a paradigm shift from a technically managed solution where we build and maintain it ourselves on the client side to a contractually managed solution where we’re now paying someone else to do it for us. And this does serve as a new set of risks requiring IT vendor management skills on the client side and understanding new methodologies to mitigate these risks.

Sanjog Aul [00:52:26]:
Thank you so much, Thomas, Tom and John for sharing your thoughts. I’m sure there are a number of nuances which still we need to hash out, and there will be gray areas. But overall, it looks like the provider and the consumer community, which is enterprise IT, are trying to work together to make this a successful affair. Thank you so much again.

Contributors

Thomas Trappler

Thomas Trappler, Director of Software Licensing, UCLA; Instructor, Contracting for Cloud Computing Services, UCLA Extension

Thomas Trappler has extensive experience leading enterprise-wide IT procurement and vendor management initiatives and negotiations. He is a nationally recognized expert in cloud computing risk mitigation via contract negotiation and vendor ... More   View all posts
Thomas Struan

Thomas Struan, Chief Information Officer (CIO), Army Aviation Center Federal Credit Union

Thomas Struan is the Chief Information Officer (CIO) for Army Aviation Center Federal Credit Union where he is responsible for Enterprise Risk Management, Information Services & Security, Risk and Security Strategy, and ATM/Payment Card... More   View all posts
John Engates

John Engates, CTO, Rackspace

John Engates is CTO of Rackspace. He joined the company in August 2000, just a year after it was founded, as VP of Operations, managing the datacenter operations and customer service teams. Two years later, when Rackspace decided to add new... More   View all posts
Add Comment
Click here to post a comment

Advertisement

RCN 1 MPU 300X250
Thomas Trappler