Using Delivery Point Validation - VeriMove - 4.0

VeriMove Guide
Product type
Software
Portfolio
Verify
Product family
Data Quality - Postals
Product
VeriMove
Version
4.0
Language
English
Product name
VeriMove
Title
VeriMove Guide
Copyright
2023
First publish date
2002
Last updated
2024-05-15
Published on
2024-05-15T01:25:15.950712

To use Delivery Point Validation (DPV) to verify that an address is a deliverable address, follow these steps.

  1. In the VeriMove main window, double-click the job you want.
  2. Click the DPV/LACSLink /SuiteLink tab.
  3. Check the box Use Delivery Point Validation (DPV) to enable DPV.
    Note: USPS CASS regulations require Delivery Point Validation (DPV) processing. If you do not perform DPV processing, the internal CASS engine does not generate the USPS Form 3553 (USPS CASS Summary Report).
  4. Indicate whether you will be performing internal DPV processing or external DPV processing. Internal DPV processing is only available if you are going to execute the job on Windows, Unix, or Linux and if internal CASS processing is selected on the CASS tab. External DPV processing is only available if external CASS processing is selected on the CASS tab.
    • To perform DPV processing using VeriMove, select Internal DPV processing. In the USPS DPV Data field, enter the path to the USPS DPV data. This option is only available if you will run the job on Windows, Unix, or Linux.

      The DPV file must be from the same month as the ZIP+4 file (city.dir).

    • To perform DPV processing using another software package, select External DPV processing. You must select this option if you will run the job on z/OS or IBM i.
  5. If you choose Internal DPV processing:
    1. From the USPS DPV File Type drop down list, select the DPV File Type that you have installed for DPV processing.

Table 1. DPV File Types
DPV File Type Description
HASH Perform Delivery Point Validation (DPV) processing with the DPV Hash database (dpvh.db). The default value is HASH.
FLAT Perform Delivery Point Validation (DPV) processing using the DPV Flat database (dpv.db). Use the DPV Flat File for improved batch performance. This file is in excess of 2.1GB. This is an optimal solution if you have less than 100MB of RAM/Memory available.

NOTE: For best CASS processing performance, the recommended value is FLAT. If you prefer to use the DPV Flat File for processing, you will need to install DPV flat databases (available in a separate download or media), point your DPV File Path to the location of the DPV Flat database, and change the DPV File Type for your jobs from the default value (HASH) to FLAT.
SPLIT Perform Delivery Point Validation (DPV) processing using the DPV Split database (dpvs.db). Split File processing separates the DPV Data File into 100 smaller segments based on the first two digits of the ZIP Code. The Split File segment associated with the first two digits of the ZIP Code is loaded into memory. If you sort your mailing file by ZIP Code, you can bring the relevant portion of the DPV file into memory. This process reduces the number of I/O requests that normally occurs when you use the Hash DPV database. Use this option if your file is sorted by ZIP Code. This is the optimal solution for customers having at least 100MB, but no more than 650MB, of RAM/Memory.
  1. If you want to perform DPV No Stat processing, check the DPV No Stat box. The USPS has added a No-Stat Table for DPV processing to identify deliveries that are not valid for Computerized Delivery Sequence (CDS) pre-processing. VeriMove counts the occurrences of DPV No Stat flags and reports that statistic in NCOA monthly reports.

    Full Service Providers, Limited Service Providers, and End Users are required to use DPV No Stat processing. If you are a Full Service Provider, Limited Service Provider, or End User, the DPV No Stat option is automatically enabled on the DPV/LACSLink/SuiteLink tab and cannot be disabled.

  2. If you want to perform DPV Vacant Table processing, check the DPV Vacant box. The USPS has added the Vacant Table for DPV processing to identify delivery addresses that have been active in the past but, according to USPS data, have not been occupied within the last 90 days. VeriMove counts the occurrences of DPV Vacant flags and reports that statistic in NCOA monthly reports.

    Full Service Providers, Limited Service Providers, and End Users are required to use DPV Vacant Table processing. If you are a Full Service Provider, Limited Service Provider, or End User, the DPV Vacant Table option is automatically enabled on the DPV/LACSLink/SuiteLink tab and cannot be disabled.

  3. Full Service Providers, Limited Service Providers, and End Users are required to use DPV DNA, NSL, NDD, and NSR tables for reporting statistics. These are automatically enabled.
  1. If you choose External DPV processing, in the Statistics Source area, select the method you want to use to provide DPV statistics from the external DPV processor to VeriMove. The options are:
    • Use Statistics In Input Field(s) — When you select this option you must add the CASS - Detail Result Indicators field to your input definition (using the Input Definition tab). For more information, see Configuring Your External CASS Product.
    • Use Manually Registered Statistics — This option is most useful if your external CASS product cannot produce the output layout required by the Detail Results Indicators field. When you select this option you must add the CASS - DPV Footnote field to your input definition (using the Input Definition tab). Optionally, you can also add the CASS - DPV CMRA field and/or the CASS - DPV Delivery Point Info field. For more information, see Configuring Your External CASS Product.
      Note: If you choose Use Manually Registered Statistics you must manually update the date of the USPS data each time you update the data. You also must manually update the name and version of the external DPV product whenever these items change.