jump to navigation

IBM unveil new ECM (Enterprise Content Managment) Suite at IOD October 28, 2008

Posted by Julian Bradder in Uncategorized.
Tags: , , , , , ,
add a comment

IBM have unveiled the latest in their Enterprise Content Management (ECM) offering. The suite marries process management, content and compliance managemengt capabilties.

IBM ECM utilses a flexible SOA (service oriented architecture) which IBM claim can be deployed within days, not weeks.

“Organizations need information to innovate and optimize their businesses, but many struggle with how to manage all the information that they have,” said Ken Bisconti, vice president, products and strategy, IBM Enterprise Content Management. “IBM’s focus on agility with ECM software helps clients address many important challenges, such as how to globally integrate solutions with immense volumes of information and optimize their processes while managing regulatory requirements.”

IBM cite an interesting example of how construction worker personnel can benefit from their ECM software:

For example, construction field personnel have frequent interaction with multiple contractors, inspecting their work and documenting their progress on various projects. Many documents are necessary for the accurate record keeping and reporting of all construction activity. Information captured on paper forms, which are then filed in a project book or transcribed into an online data storage system, can be flawed by delays in data entry, damaged paper forms and errors during transcription. With an agile, end-to-end ECM business process, these documents can be digitally authored and managed and contextual information, such as maps and equipment inventory, can now be electronically delivered to the contractors in the field instantly, improving speed, reducing errors as well as reducing overall project costs.

The IBM Enterprise Content Management Suite comprises of IBM Business Process Manager 4.5, IBM Filenet Content Manager 4.5, IBM Content Manager 8.4.1 and IBM Content Manager On Demand.

Customer Data Integration. How CDI drives the customer communication process October 15, 2008

Posted by Julian Bradder in Uncategorized.
Tags: , , , , , , , ,
add a comment

Customer Data Management and integration is in many ways the cornerstone of a companies customer communications management approach. It is the difference between a sloppy and inefficient set of processes and one which serves the organisation well, giving the business more for less.

The acquisition of data may come from multiple systems. Much is said in respect of the “Relationship Statement”, a consolidated presentation of all of a customers product relationships. Bad data management could result in you only ever presenting half of the ‘relationship’.

For smart customer communications and the data that drives them, there needs to be commitment. Sales, Marketing, Customer Service and IT all need to get involved and work closely together.

The impact of poor data in the context of customer communications management can strike in many ways. The customer ‘conversation’ may become irrelevant and this may impact key performance measures in respect of customer retention, share of wallet and so on. It may result in a company sending confusing messages to customers across different communication channels. This is points to a need for a centralised approach to data management. It also suggests that this is an area where a Service Oriented Architecture has real merit.

Equally serious is the sheer volume of mail that goes to recipients that do not reside at the address. This is quite simply a waste of resource. Its treatment is at the down stream elements of the customer communications process. The treatment should be applied either pre-document composition whilst the data remains data or as part of postal hygiene steps at the composition or print stream engineering stage of document creation, it is important to use the available hygiene files available comercially.

An organisation takes in data from many different sources. Customer service may take address change notification over the phone. Customers may go into branches and change there information. They may change their information on the internet or at a point of sale location.

With so many sources of data the key is to try and maintain a standard. Good data quality tools will allow the creation of these standards across the enterprise and across inbound information channels. As a customer service representative makes changes at the clients instruction, the address can be validated against mail operator approved postal data and only an approved address can be entered into the database. That same service can also be integrated into the internet channels, and at retail locations.

Ah, but from here stems another problem, a customer walks into a store and makes an enquiry. He then goes home does some internet research and enters his data into the website. Later he makes his order by telephoning the call centre sales operation, his data is recorded once more. No we have duplicates across company systems. THis is where Customer Data Integration comes in. A process for deduplication can be established and we can avoid the potential of delivering any number of mail pieces to a single customer.

THe key with data quality is to persist. It is essential that a company persists at both upstream and downstream processes.

There must be data quality management processes both in front office and back office operations. It takes a considerable will for a company to effectively manage its data and it is a process whereby the ball simply should not be dropped – ever.

Document Composition – Participative Document Creation October 13, 2008

Posted by Julian Bradder in Uncategorized.
Tags: , , , , , , , , , , , , , , , ,
add a comment

There used to be only one method of inputting to document creation / composition tools. It was a case of throw some defined data at the composition engine and then execute a script. Out of the other end of the process comes a printable print stream to by physically printed and finished.

Now, some vendors have moved and other vendors are moving in the direction of participative document composition. New technology means that users within the business can write documents of their own and have them processed as part of the overall organisation document production activities.

But why do this? Well, clasically, if you wanted to create customer documents you would need to establish a project. That project will involve people from a number of groups. The project team would likely carry a Project Manager, technical resource from IT, a representative or two from the business, a compliance office and perhaps many more people – I’ve sat in meetings with 25 people discussing the evolution of a single document!

To put it mildly, it has always been a slightly baffling process particularly if you are a non-technical business user. Why so much to create a single document?

The reason is that customer facing documents are important and you can’t afford to get them wrong. The second reason were the limitations of what technology can do. This has changed now with the advent of object oriented systems and service oriented architecture. Now, reusable blocks of enterprise code can be made widely available to any number of mission critical business processes.

So for example there may be a standard way of performing a calculation or rendering and displaying images on a document. Whereas before, these bits of code and rules would sit on an isolated server in some IT backroom, this code is now available really to anybody that needs it!

Much of a documents construction is now pre-defined. Where the address will go, where marketing message can appear, what legal lines can be used and so on. This means the overall format of say a letter can be established early on. If a change is needed to company letter formats, this can be done globally across all letters. Before, every application would have to be changed and tested individually!

So the business user now becomes concerned only with the content. They can enter their content on a Word Processor style interface, perhaps even following content standard rules, enter the document into an authorisation procedure and track the document until it leaves the organisations door. It’s really that easy now.

The advent of the application service oriented architecture in document creation and distribution is bringing about a sea change in the way that companies now communicate with their customers. It’s saving money, accelerating time to market and directly improving those classic customer churn prevention, retention, satisfaction and acquisition goals.

A major breakthrough in customer communications management technique, I would urge all my readers to investigte the business case for this approach as soon as possible.