What does S+S mean to the customer?

This is my problem for the next few weeks...

S+S and the other software and services initiatives from Google et al may well take away a fair chunk of the work needed to manage an effective IS service.  If we can do that we can devote our efforts away from the day-to-day ops and into making a difference elsewhere.  Sure there will still be challenges, but hopefully most of the operational overhead will be focused on service management and commercials than day-to-day technical design and admin.  So...  If I'm an enterprise customer planning my IS architecture for my business over the next few years what should I be thinking about?

The first thing that comes to mind is the cloud where all these services will live...  Where is it, and how do I get to it?  How do my users authenticate to it?  How is my information secured between the cloud and desktop?  How do my customers feel about having their data in a cloud somewhere in Redmond or Mountain View?  Might I be part of the cloud for my customers? 

The software side shouldn't too much of a problem (famous last words!)... getting software to people we can do, but the more I can move that into the cloud the happier I'll be!

Related posts:

  1. Exchange 14
  2. Continuous Services | Connected Devices
  3. Barriers to the Cloud
  4. S+S
  5. Cloudy IT

Post a Comment

Your email is never published nor shared. Required fields are marked *

*
*