Cloud Management

This is a continuation (well, at least sort of..) to my previous blog text, Cloud Services – the Business perspective.

Like I wrote, Cloud Services have rushed into the markets relatively rapidly and they have been able to fulfill some key expectations, for example in terms of Cost Efficiency, Scalability etc.

But who actually manages Cloud Services? And if Cloud Services are called “Services”, what kind of services are there available and why should anybody care about them?

From IT Services to DIY approach

According to Wikipedia, “Cloud management is the management of cloud computing products and service”.

 

DIY Cloud ManagementFor more than two decades, IT Service Management has been the way where organizations have striven for. Simply because managing the IT Services has not usually been the core business for organizations. IT Service Management is mainstream nowadays and people seem to be quite confident with it. Someone takes care of your problems (Incident Management) and requests (Request Fulfillment) and you can concentrate on doing what you are being paid for.

if Cloud Services are called “Services”, what kind of services are there available

If so, why is it that I keep hearing from several companies offering Cloud Services: “There is this nice&neat User Interface where you can easily start new virtual servers and also ramp them down when you don’t need ’em anymore”.

Self-provisioning, Self-help, Self-this-and-that?

Now that we have finally reached the level where a user does no longer need to solve his/her IT-related problems on his/her own, for some reason Cloud companies are accelerating the pace with providing more and more tools for the user to start/stop virtual servers and handle storage capacity in Cloud environment!

“It’s easy, just like that.. just click this, define this and that and you’re good to go!”

  • Thanks, I’ll give it a try.. but what if
    • I need an L3 connection from my internal network to this cloud environment which lies in a public internet? I’m not even sure what is the correct source IP-address.
    • I’m not quite sure how much more capacity I need for this certain system?
    • There are 2000 users who should be able to access the system in the cloud environment? Who grants accesses for them and takes care of the overall Access Management?
    • I want a comprehensive, formal report in some other form than the one being available. How do I get it?

Doesn’t seem to be so “easy, just like that.. just click this, define this and that and you’re good to go!”

As long as you are using some software you are buying as an SAAS (Software-as-a-Service) model and you don’t need any integration to your other systems, using Cloud is a trivial thing as everything is usually ready-made for you. You only need to start using the Software (as-a-Service). But when it comes down to integrations, it’s totally different story.

Doesn’t seem to be so “easy, just like that.. just click this, define this and that and you’re good to go!”

User-Friendliness?

In my opinion, the problem with lack of User-Friendliness is built into the history of the IT industry: Too often we tend to take a sole technical viewpoint to new things. Yes, we do recognize the pros and benefits behind a new tech, but we often fail to take the end-user’s perspective into account.

The irony is, that for at least some 20-25 years, the IT Industry has been speaking highly for IT Services, and now we are suggesting that for some unknown reason users should start managing the cloud environment more or less themselves?

Too often we tend to take a sole technical viewpoint to new things.

Who needs Cloud Service Management? No, who doesn’t!?

Ok, say, you have a small IT-company with <10 personnel: in your case it might be a good idea to handle the Cloud Computing issues yourselves. For any other company my suggestion is simple: Use your IT Service Provider’s helping hand! Just like TechTargets puts it, A distinguished IT Services provider can use cloud service management and cloud monitoring tools to maximize performance, reduce costs and differentiate their cloud services.

Services

The Cloud Services Management includes a set of services that are already mostly known from traditional IT Service Management:

 

  • Cloud Service Level Agreement
  • Cloud Capacity Management
  • Change Management
  • Configuration Management
  • Incident Management
  • Access Management
  • Reporting (including billing)
  • etc.

 

Quality Service ProvisionIn other words: Cloud Service Management expands the existing ITSM repertoire. It’s not the 7th wonder of the World, but a significant part of the modern IT Services Package. In short: there’s usually no point in provoking customers try managing the Cloud environment themselves. It just doesn’t pay off the effort.

 

 

 

Common Misconceptions of Cloud Services

I was participating the annual Social & Healthcare ICT Conference here in Finland on May this year. There were a large number of phenomenal speeches from heavy-duty ICT Healthcare professionals. But I also happened to hear some basic-level Misconceptions of the Cloud -related issues when speaking with Healthcare professional on the corridors.. To this end I’d like to take the chance to address ’em and provide some corrections. So here we go:

  • Data Centres? We don’t need data centres at all any more because we are using Cloud Services!
  • – Ehm.. what do You think, where’s the actual computing done, and where’s the Storage? Somewhere over the rainbow, in the Stratosphere perhaps?
  • – Seriously speaking, computing, storage services, database operations etc. are still taking place in some physical place and that is a surprise for some people.
  • We are only using Virtual Servers, we don’t need to deal with hardware servers on any level any more.
  • Yeah, right.. At the end of the day also Virtual Servers are running on physical servers and not in an empty space..
  • I can take everything to the Cloud – there’s no need for an on-premise solution whatsoever.
  • Not so fast.. Some of the computing must still happen on-premise. For example Network latency might hinder you from using an autopiloted car and that’s why the AI service must be placed somewhere in the car and not in some Cloud Environment (Data Centre) some ~10000kms away from your car.

I know, it’s so easy to laugh at people’s misunderstandings and misconceptions. Even though I listed those three examples above with a little bit of sarcastic touch on them, I definitely absolutely don’t want to laugh at anyone. Given the way in which Cloud Services are advertised nowadays, it’s not so surprising. Maybe we Service Providers could be more clear in Cloud Services advertising and communications..

 

Pictures are from Pixabay.

Consumerization: Customer satisfaction surveys

Consumerization: Customer satisfaction surveys

Everybody receives ‘em, from every kind of services: whether it was a hotel accommodation or a booking of concert tickets or anything.. In the era of consumerization the end customer is a king and their opinion counts. But what’s the point of customer satisfaction surveys if they fail to reach the most crucial thing: customer satisfaction?

My case: Invoicing gone bad

Last week I received an invoice concerning the maintenance service of my car. I knew for sure I had paid the bill in question already a month ago.

I called to the service desk and after waiting for around 10 minutes (I was not happy with 10 minutes response time!) my call was answered. The customer support person was polite and yes, the invoice was a double invoice and according to the customer support person I could just ignore it. There would not be a reminder of an unpaid bill coming afterwards.

When the phone call ended, it took less than 1 minute to receive a customer satisfaction survey (later on just “Css”) as an SMS. I could either answer Y(es) or N(o) to let the service provider know if my case was solved or not.

So let’s wrap up what really happened:

  • I got an unfounded invoice concerning a service I had already paid for.
  • I waited for ~10 minutes on the phone for response.
  • I got a Css in less than 1 minute.
  • I could just answer “(Y)”es or “(N)”o describing about my satisfactory on my case.

When the phone call ended, it took less than 1 minute to receive a customer satisfaction survey as an SMS.

Case closed?

The customer support person told me on the phone that the unfounded invoice had already been credited. However, it took three more days until I got the credit note and a so-called explanation of what had happened. Until I finally received it, I didn’t want to answer the survey: I had no tools to verify if they really had handled my case properly or not – and what’s even more serious: I didn’t trust them at this point.

By the way, do you want to know the root cause for the incident in this case? 

Ta-da-daa… Surprisingly: “system failure”! That’s really enlightening and I’m sure their customers can feel themselves relieved now..

Measuring customer satisfaction?

It’s interesting that the only answering option I got was a binary 0 or 1 (Yes or No) to the Css.

What’s the point of conducting Css’s if the only information you get is just Yes or No? Sure, you can do advanced mathematics and calculate the percentage of all the Css’s and compare the Yes-No results. That gives you something, but it’s almost nothing.

Wouldn’t you like to receive even a little bit more information? For example:

  • How likely would you be to recommend our customer service to your colleagues and friends [0-10]?
  • How would you rate your experience of our customer service in general [0-10]?
  • How quickly did you get through to a customer service specialist [0-10]?
  • ..

There are loads and loads and loads of examples of the Css questions in the internet, so there’s no need to list more of them here.

My point is: why to conduct Css’s if the only measure is a percentage of solved cases vs. all the cases?

Timing is everything

And finally, about getting the Css in advance: the problem is that if you answer to the Css too early (= before you are certain your case is handled properly and closed), you might

  • give unnecessarily good feedback of the service, if it later on turns out that your case was actually still unresolved
  • have to go your problem all over again, calling or otherwise contacting the service desk and dealing with yet another customer support specialist, because your earlier incident has already been closed and thus is not active any more.

Why? Because you answered Yes to the Css you received too early.

There is a collision between the Service Desk’s point of view and the end customer’s experience: from SD’s point of view the case is closed, but the end customer has no possibility to verify if the case is solved, they can only trust the Service Desk.