For the product post there are the following typical use scenarios, all featuring fast, error-tolerant postal check and address correction:

When building up address databases or transferring data files in a data warehouse project, it is recommended to check and cleanse the addresses before loading them into the database. This is essential for enhancing the data quality. In conjunction with the subsequent two use scenarios, it is thus ensured that only correct postal addresses are to be found in the database.

When entering data, whether independently, interactively or in a batch, new addresses or addresses that are to be changed are run through a postal address check, and if necessary they are automatically corrected as far as possible. This ensures that only correct postal addresses get into the database and that all addresses have a uniform structure and spelling. If an automatic correction is not clear without ambiguity, the user can be shown a selection of possible alternatives to clarify the entry via the record at hand or, for example, directly on the telephone in the call center.

Even if both of the scenarios described above are implemented, it is recommended to check and update the address database periodically. At first glance this may not seem to be absolutely necessary, but it is if value is placed on very high data quality. Towns are constantly being incorcoporated, streets renamed or postal codes changed. Since you can only in the rarest cases assume that your customer will communicate this information to you separately, you should let these changes be carried out automatically by the Uniserv system post.

Sitemap | Webmaster | Disclaimer | Privacy Policy | Imprint | © 2008 Uniserv GmbH