Momentum 2010 – Cloud Strategy for xCP

Apologies for the delay in this post but following Momentum I had a week off to spend time with the family, and I wanted to make sure that time was spent with them and not writing more blog posts.

This is the last post on a specific session and covers a session which was presented by Randy Hodge on Wednesday, it was a late session but was still relatively well attended. Randy is a knowledgeable guy and the presentation was good in that it came across as someone who knows their stuff and not necessarily someone who has been presented with a message to give.

Firstly I must say that this was really a presentation on strategy so there is no commitment that what was presented will actually come to fruition.

Firstly Randy justified the move to cloud as a need to reduce the pain which customers feel and to reduce the crippling TCO. Reducing this TCO of services will stop the current situation of too much money being spent on maintenance and not enough on investment opportunities.

In talking about Cloud Randy then talked about how to consider the EMC IIG stack and the message I took is that xCP is PaaS and something like the Investigative Case Management solution is SaaS. Generally I agreed with the messaging here but there were a few things which we could quibble about, e.g. where does Captiva fit in. EMC are seeing customer demand for the cloud especially in xCP and customers are making moves to deploy xCP applications to the cloud in areas such as Justice, FS and Health. Similarly IIG want to move customers to the cloud.

xCP for the cloud will:

  • evangelise xCP on VMWare;
  • drive down TCO and increase agility;
  • revolutionise the way applications are developed and deployed;
  • evolve the ecosystem model;

He then announced that xCP is now VMWare ready.

He described how xCP in the cloud will drive down costs, Virtualisation can do this too but Cloud can further drive down costs.

The characteristics of a successful cloud solution, as defined by NIST, are:

  • Rapid elasticity;
  • Resource Pooling (multi-tenancy);
  • Measured Service;
  • On demand self service;
  • Ubiquitous network access

He then talked about multi-tenancy and how that can be achieved. This was interesting as Randy and I had discussed this earlier in the week and I think this still needs a bit of refinement, my belief that the number of tenants does not drive whether a solution should be considered multi-tenant or not although it is one factor. Imagine a scenario with two organisations wanting to share an ECM repository but with different business processes yet the content subject to the same Policies for retention. Randy talked about the Dedicated Repository Model or the Shared Repository Model, my problem below would need some thinking about how to resolve (perhaps Federated RM is the way forward there?).

Another interesting statement was that EMC want to provide services which can be consumed elsewhere, so the EMC app may not be the primary application which users interact with but could provide an element of the overall business process. I am seeing this more and more and the introduction of CMIS will, I think, increase the number of scenarios where this is applicable.

Finally Randy showed a diagram and used it to explain the various models which xCP in the Cloud will be delivered. Unfortunately my notes do not do justice to the diagram so I will attempt to describe it instead:

  • Traditional model where SI’s build an application based on xCP and deploy it to the Cloud which is then accessed by end users;
  • A model where ISV’s develop apps built on xCP and deploy these to an App Store from where they are purchased and accessed by users;
  • A model where xCP is deployed within the Cloud and the services are exposed and then consumed through custom applications which may or may not be deployed in another cloud.

As I say that doesn’t really do the session justice, I felt as though it was an interesting session and given that I have asked EMC before about Cloud it is something they need to get moving on and get moving quickly.