jump to navigation

Postal and Telephone Communication Compliance – Mailing Supression Files (MPS) and Telephone Supression Files (TPS) October 30, 2008

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

In both the US and UK, mailers are required and if not required, advised to check their address files against a number of key database files. These files are in place to protect the consumer against unsolicited mail.

There are numerous files available but, the key files that you should be implementing to ensure compliance include:

Telephone Preference Service (TPS) – This is a list maintained whereby the consumer can register her desire to be on the list. In theory at least, the customer should not then receive sales calls to their phone line.  Companies are liable to fines if they do not adhere to the Telephone Preference Service.

Mailing Preference Service (MPS) – This works in exactly the same way as the Telephone Preference Service and when pursuing direct mail activities, companies should check their print streams to exclude any individuals whose names are on the register.

National Change of Address File (NCOA) – The national change of address file records data where postal providers such as the USPS and Royal Mail have been advised by customers that they have moved house.

Deceased – Both the US and the UK offer deceased files in order that you can exclude causing offence by mailing the deceased. In the US there are even files that offer predictions for deceased. Now there is an idea!

There are various other files available but the list above perhaps represent the most important ones.

Quite apart from the potential for a fine, it is just good business practice to observe and respond to the data in these files.

In respect of implementing the software, there are a number of approaches.

Suppressing Telephone Calls – Validation software can operate and integrate live with your customer relationship management application. As an agent calls up a customer to call, there can be a real-time check against the database and the agent can be disallowed from making the call.

Suppressing Mail – This can happen at a number of points within the organisation. If you are operating a MDM policy, it may be worth considering the age of the data before it is turned into a document. If there is a significant lapse here then you will almost certainly want to implement the suppression at the automated document factory level to maximise your compliance opportunity. If the data is drawn from the MDM platform and turned to documents instantly, then managing the quality of the data at the early stages of the process will probably suffice.

If delivering the suppression at the automated document factory then, if the documents are generated by an in-house document composition platform you will be able to perform the various database look-ups as the documents are composed and as part of the composition application.

If the documents are generated by a business applications (perhaps you should look at customer communications management solution and its advantages) then you may need to implement a print stream engineering solution such as that offered by Streamserve or Pitney Bowes Emtex to ‘post-process’ the files and execute the suppression.

There are many suppliers of these suppression files and a simple internet search will realise plenty of people you can talk to. This requirement is not just for big business and smaller companies should also consider their compliance position.

Pitney Bowes Emtex announce P/I Wizard Solution October 23, 2008

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

Under the guise of a fairly unintelligible press release, Pitney Bowes Emtex have announced their P/I Wizard intelligence solution.

From what I can decipher from the press release, the new software appears to provide capability to establish jobs and related workflows from a browser GUI. It appears  to offer some print stream engineering and management capabilities as well.

Apparently, the software will allow the addition and removal of barcodes, and will allow the creation of integrity files for production processing.

Other than that,  “The P/I Wizard helps to ensure applications are properly aligned for data capture and process control”. Eh?

Sounds like it could be print stream engineering with a GUI and some process control around print stream engineering steps.

Answers on a postcard please!

Legacy Print Streams – There are solutions! October 10, 2008

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

In order to establish smooth and effective operations, simplicity is the key. Whilst in this blog we have talked about the utopian document factory, the reality is that in order to achieve that utopia, we need to start from a greenfield position or, have endless amounts of cash and time to buy our way out of legacy.

One of the key striking points for legacy is in the print stream. This is the print file that a document composition engine would generate. It may also be generated by older legacy business applications.

Analysis of these legacy applications may bring business justification to migrate a certain percentage to a newly installed document composition platform. However, it is unlikely that every single print stream can justify this migration.

Therefore, we have built a document factory, with big investment in high speed printers that for the sake of argument come from IBM. Therefore, the print stream is probably AFP.

The problem is that we have 10 applications coming from an old Windows platform that is outputing PCL. What can we do about this?

Companies such as Emtex, Levi Ray & Shoup and others all offer technology known as Print Stream Transformation. Through this technology a file can be converted from a Type A to a Type B. This technology is pretty good and pretty reliable these days. The main thing to plan for is the extra processing time to do this conversion. Don’t understimate this as processing 500k documents in this fashion can take a considerable chunk of processing and server time and this may be competing with other jobs which may have a higher priority.

This area may be one of the more challenging problems that you face in the development of your automated document factory. There is much that can be done to ease this transition. Be creative in your approach to legacy document migration and remember that a new document migration may mean the engagement of yet another company business team!