About

My name is Seth Gottlieb. I have been working in the field of content management for the better part of 15 years. During that time I have worked for CMS customers, CMS implementers, a CMS vendor, and as a CMS industry analyst. Now I work for Lionbridge Technologies helping companies increase the efficiency and effectiveness of their content strategy execution. See my full bio and my Linked In profile for more.

Writing this blog has been a tremendously rewarding experience for me. It has enabled me to share concepts that I have learned and connect with people. In 2007, Content Here became my business and for 5 years I delivered vendor neutral consulting services to help clients select and maximize the benefit of their content technologies. There is a wealth of information here and I hope you find it useful.

Get in touch

Tuesday, December 28, 2004

Wachovia "Content Access Services" Case Study

This case study by Gilbane's Content Technology Works (CTW), other than being an advertisement for IBM, shows a successful execution of a content integration strategy. The client is Wachovia, a very large financial services company (4th in the US), that grew out of acquisitions and, consequently, had several document repositories based on different technologies: IBM ImagePlus, FileNet, and Mobius. Libraries of digitized forms and documents are a huge deal in financial services companies because they need to keep every interaction with their customers at hand for customer service and regulatory reasons. As an aside, I once had a client that knew they had to do something major with imaging when the weight of their paper archives started to bow the floors and break the windows of their building.

In order to integrate the business operations of the merged companies, Wachovia employees needed to work with information about their customers from multiple sources. Projects requests started surfacing about building desktop applications that integrated customer information from multiple departments. Rather than trying to migrate all the content over into one system, Wachovia started building a common content access layer with adaptors for different document management systems. The core technology they used was IBM's DB2 Information Integrator Content Edition which already came with a FileNet adaptor. Wachovia also built new adaptors for ImagePlus and Mobius and then added their own XML-based API to insulate Wachovia's client applications from the Information Integrator API.

From reading the case study a couple of really good decisions stand out.

Rather than adopt a strategy of migrating all content into a single system such as FileNet, Wachovia chose an integration approach where heterogeneous systems could coexist. This makes sense for several reasons:

It is cheaper. Migrating terrabytes of content from one format to another has a huge up front cost.

It leverages existing investments. Not just licensing but also customization, integration and training.

It is lower risk. Wachovia does not have to bet the business on one technology. There is so much volatility in the marketplace that no one knows what is going to be a market leader and what will fall behind.

It allows best of breed selection. Different groups may have different needs that are best satisfied with different technologies.

Rather than have their client applications access the Information Aggregator API directly, Wachovia added an abstraction layer. This will enable Wachovia to more easily swap out Information Aggregator if a better technology comes along.

In all, I think this is an excellent approach to the vision of "Enterprise Content Management." It is practical, cost effective and reduces dependency on a single provider.