Pie’s Application Separation

Interestingly when I first read Pie’s tweet to advertise this post I thought it was going to be focussed on Content Enabling applications. I suppose it is but some of the applications he talks about content enabling are very close to the platform services being provided, e.g. WebPublisher and Centerstage. Does this mean I think it is wrong? No, not at all. Pie has exposed a model which is very interesting. With the Core Server customers would buy the platform and a way to interact with the basic services the platform provides, it would be interesting to understand where the line is drawn on Basic Content Services…e.g. is MOSS in this group?

For Applications Pie adds the likes of WebPublisher and Centerstage, the Documentum apps. In this space I see some separation between these style of products and the more vertically focussed implementations. Something more akin to:

– Extended Content Applications – those applications which are still focussed on providing horizontal content solutions but with enriched services focussed on a specific ECM Use Case such as Web Content Managment or Digital Asset Management;

– Business Solution Content Applications – those applications which are taking a specific business solution where there is a need to interact with unstructured content and providing the application to perform these tasks;

It is the latter which I am becoming increasingly interested in, I’m making some notes on a post about Case Management which I hope to post this side of Christmas.

So will Pie’s model work? Yes. Do I think the market is ready for this? Not yet, and I think it is the vendors who are the farthest away from this concept although CMIS should provide a vehicle for them to provide this. Take Documentum for example, with their CMIS release they have some very basic content services which they can expose…the decision they need to make now is which services form the rest of the platform services and how can they expose these in a way which enables CMIS to develop.

There is also a certain amount of kudos which is taken from having your app used by customers at the front end, moving ECM closer to being an infrastructure may not be something the vendors will necessarily embrace. But then how many times will you hear people say things such as “Documentum is a really annoying product” (Quote taken from a quick search of Twitter for Documentum)? The answer is quite high, and this is something which creates a poor reflection on Documentum as the users are typically complaining about the way they interact with the services and not necessarily the services themselves.

Any vendor that can shape themselves to providing the most scalable, performant, secure and compliant unstructured store which provides a rich set of services which can be used will be one step to establishing a differentiator for themselves. The second step will be to get a strong strategy of working with partners to use those services in business focussed applications such as Contract Management, Case Management and Purchase to Pay applications.