jump to navigation

Multi Channel Document Management October 2, 2008

Posted by Julian Bradder in call centre document creation, document composition, email campaign management, multi channel documents, publish to email, publish to mobile, publish to web.
Tags: , ,
add a comment

Traditionally, documents were seen as paper based items that get sent to customers. Now, document creation platforms should be able to deliver to a variety of document distribution channels and should be able to render formats viable within those channels.

At the very least, a composition engine that will be a strategic choice for your business should be able to cover the following needs
Publishing To Post
The traditional mail channel remains very important and certainly amongst more traditional customers, the desirable way to communicate with them. Certain documents must travel this route such as those requiring signature e.g. contracts.
Publishing To Email
Many customers now prefer to receive their communcations via email. It is direct and quick and can be dealt with wherever the customer is. Security is a concern with much Email communication so there are two options. Either deliver a PDF document with an email (not very secure) or, drag a link back to the website so that the user can authenticate him/herself before pullng the document down securely from your website
Publishing To Web
In many ways, part of the email strategy above. If you have a secure area within your website, publishing personal documents to your website can be a highly effective way of communicating with customers.
Publishing To Mobile
Mobile is becoming an increasingly important communications device. As mobile telephones become more powerful, in fact just very small computers, thus their importance for communications between company and customers increases.
What should also be ensured is that your document creation platform is capable not only of supporting batch jobs but also capable of allowing users in the front office to add one to one messages to documents, thus getting close to the goal of one to one communications.

The Automated Document Factory – Maintaining Mail Integrity September 25, 2008

Posted by Julian Bradder in adf, automated document factory, banking software, document composition, document integrity, factory workflow, kern, pitney bowes.
Tags: , , , , ,
3 comments

The Automatic Document Factory (ADF) as a concept has been around since at least the mid-90’s. In it’s truest sense, it has been slow to gain ground.

The idea of the ADF is to provide a file oriented check in which the integrity of document factory operation can be assured. In a properly managed ADF, documents should always mail to the individual that they were intended. There should no embarassing errors such as placing another individuals statements in envelope’s. It also ensures that everything is finished and posted. In it’s most advanced state, this tracking then continues into the postal service.

In theory therefore, a individuals document can be tracked from the data inception stage right through to the moment it arrives at the customers letterbox.

Pitney Bowes and Kern, both providers of the large envelope inserter platforms probably have the most significant capabilities. Due to its investment in software companies, Pitney Bowes is likely the most advanced of these two companies.

How is the ADF achieved?

First lets consider the steps in the process in a banking organisation with a print job where the print file is generated by a composition engine.

1. A core banking application kick’s off a batch job, lets call it April Statements. This batch job produces the data necessary to generate 100,000 statements.

2. Using a factory / process workflow tool, the data job is collected and registered as a live job within the ADF. The data job is passed to a document composition engine in line with the factory schedule.

3. On receipt of the data file, the composition engine then recognises the job and starts the process of creating the document print file. Following a set of rules, the documents are generated whilst at the same time, a side file, or integrity file is generated. This is usually a 5 – 7 field file that contains information about each individual mailpiece. Importantly, the composition engine will also apply a mark such as an OMR mark to the document so that downstream hardware is able to recognise the mailpiece utilising camera technology. As each document is generated, the side file is populated.

4. Upon completion of the composition step, the file is then passed to a print server together with it’s side file. The ADF Workflow control software kick’s off a print job. The printer with camera attached checks off each item as it is printed, verifying number of pages printed for each mail item. The side file is checked off to confirm that individual mail pieces have been printed.

5. Once printed, the physical job is then passed to an envelope inserting platform. The job is started within the workflow system and then by using camera technology on board the inserter, each mailpiece is recognised and understood. By understood this means that the inserter recognises the mailpiece and what needs to be done with it. The questions that the inserter will be resolving will be things such as: Do I need to outsort this? What inserts need to go in this mailpiece? How many pages in this mailpiece? With various checks and controls in place, the inserter then processes the job, again doing exactly what the print job was doing evaluating it’s processing of every mailpiece and recording it’s actions in the side/integrity file.

With a big job of say 100,000 mail pieces it is likely that some items will get spoiled. The inserter will know this and will record this in the integrity file. At the end of the job or during the job, those items that haven’t been completed will then be passed back to the start of the process, the documents re-generated, printed and re-inserted. This looped process continues until the ADF software is satisfied that every item has been completed.

In actual fact this integrity can continue either through internal post sorting systems or via the mail. In reality, many postal service providers do not yet have the technology to execute in this area.

The company is assured of reliable delivery of mail whilst there also remains an audited process so that customer complaints and other issues can be identified, verified and resolved.

News Item – ISIS Papyrus September 24, 2008

Posted by Julian Bradder in document composition, fat client, ISIS Papyrus, thin client.
Tags: , ,
add a comment

Papyrus EYE Enables Rich Document-centric Applications with Single Definition for Identical Experience across Browser and Fat Client.
http://www.marketwatch.com/news/story/papyrus-eye-enables-rich-document-centric/story.aspx?guid=%7B15A6652E-23DE-4A19-A9A6-C534490D5A0F%7D&dist=hppr

Content Management September 24, 2008

Posted by Julian Bradder in content management systems, customer service area, document composition, document management.
Tags: , , , , , ,
add a comment

Content Management is a strand of document management that relates to publishing. Content Management is a technology driven process that supports the publishing process whether it relates to new media such as the web or older media such as newspapers and even messages to publishers.

Content Management Systems typically support workflows across key stages of the publishing process. These might include Creation, Editing, Publish, Administration and availablity of the published work to the consumer.

A key strand of an overall enterprise document management approach, Content Management Systems can be utilised to drive customer communications and to facilitate the handling of customer interaction.

Content management can be used to drive customer communications activity across the enterprise via virtually any chosen communication method.

What is Document Composition? September 24, 2008

Posted by Julian Bradder in afp, batch processing, call centre productivity, customer service representative, data matrix, document composition, inserter, legacy software, omr, output management, pcl, print file, xerox metacode.
add a comment

Document Composition was originally designed as a point solution to deliver high volume documents as part of a batch process. Organisations such as banks, telecommunications companies, insurance companies and others that have a requirement to send out high volumes of documents to customers utilised document composition software to overcome heavy deficiencies in the ‘Output Management’ function of their core software application.

In essence, core business application platforms would create a batch data job that provided key data for the document composition platform. Upon receiving and recognising the data that has been sent to it, the document composition platform would then process that data and, following a set of design and rule within it would then convert that data into a customer facing document print file.

The print file is prepared in a way that is governed by the downstream physical printing and mailing processes. The document composition prepares the print stream format e.g. AFP, PCL, Xerox Metacode as appropriate for the downstream printer. In addition, marks such as OMR, Data Matrix and so on are added to the document to enable high volume envelope inserters to understand what needed to be placed within the envelopes contents.

This may reflect the number of pieces of paper for the envelope, any additional inserts (think back to how data could target inserts on a one – one basis) and whether or not a specific envelope needs to be outsorted for manual handling.

So in its simplest form, Document Composition is a process step in a batch production process. It is however an isolated process with an absence of organisational interactivity.

Recent advances in technology means that Document Composition is no longer forms part of a batch process.

The document composition engine is now able to process single jobs as well.

Take for example a customer service centre user. The CSR receives a phone call from a customer with a specific query. In the old days, the CSR may then write a letter manually, print it off, go collect it, stuff it in an envelope and then drop it in the post tray. It works but it deadens that CSR’s produtivity whilst the organisation has no control over the letters content, style or authorisation.

Now, a CSR can write a letter following a company style, set of rules and a authorisation process. The letter is no longer sent via the ordinary ‘office post’ process. It is queued along with other similar one off’s to achieve a batch printing process. This enables organisations to reduce costs, improve quality and raise productivity.

This interactivity and the many ways that it can be applied form key areas of ongoing discussion for this blog. It opens up a wealth of opportunity for organisations and should not be ignored.