Business objects ACE 7.80C User Manual

Download

ACE User’s Guide

ACE 7.80c

June 2007

Contact information Contact us on the Web at http://www.firstlogic.com/customer

If you find any problem with this documentation, please report it to Business Objects in writing at

Patents Business Objects owns the following U.S. patents, which may cover products that are

documentation@businessobjects.com

offered and sold by Business Objects: 5,555,403, 6,247,008 B1, 6,578,027 B2, 6,490,593 and 6,289,352.

Trademarks Business Objects, the Business Objects logo, Crystal Reports, and Crystal Enterprise

are trademarks or registered trademarks of Business Objects SA or its affiliated companies in the United States and other countries. All other names mentioned herein may be trademarks of their respective owners.

Third-party contributors Business Objects products in this release may contain redistributions of software

licensed from third-party contributors. Some of these individual compo nents may also be available under alternative licenses. A partial listing of third-party contributors that have requested or permitted acknowledgments, as well as required notices, can be found at: http://www.businessobjects.com/thirdparty

ACE User’s Guide

Chapter 1:

Introduction to ACE ................................................................................... 11

What is ACE for?...........................................................................................12

Some examples of input and output records ..................................................14

Address input and output................................................................................18

The basic set of input and output fields.................................................. ........19

Codes and components that ACE can add .....................................................20

Overview of ACE products............................................................................22

An in-depth explanation of the assignment process.......................................25

Chapter 2:

Standardization and style options.............................................................. 29

About the Standardization Style options........................................................30

City place names ............................................................................................31

Unit designator standardization......................................................................32

Style of suffix and directionals.......................................................................33

Private mail boxes (PMB)..............................................................................34

Standardize only assigned addresses..............................................................35

Capitalization (case conversion) ....................................................................36

Extraneous information on address lines .......................................................37

Alias and alternate address lines ....................................................................39

Dual address lines...........................................................................................40

Additional options for multiline and two-line addresses ...............................43

Swapping address lines ..................................................................................45

Combine related components onto the same line...........................................47

Updating the ZIP and ZIP+4 in a multiline address.......................................49

Chapter 3:

Reports ......................................................................................................... 51

Executive Summary .......................................................................................52

Job Summary Report, page 1 (setup information) .........................................54

Job Summary Report, page 2 (summary of results).......................................56

Job Summary Report, page 3 (one page per database) ..................................58

Standardization Report (a listing of input and processed data)......................60

Error Report (a listing of unassigned records)...............................................62

Statistics files for custom reporting................................................................64

Job statistics file.............................................................................................65

File statistics file.............................................................................................70

Address Conversion Statistics (ACS) file......................................................78

Chapter 4:

Postal certification and forms .................................................... ................ 85

U.S. Postal Service certification programs: CASS and NDI..........................86

USPS Form 3553................................................................................ ............87

The National Deliverability Index (NDI) report............................................89

Contents

Chapter 5:

View the directories with Show................................................................. 91

Query postal directories.................................................................................92

Most ACE programs include Show...............................................................94

Using Last Line Show for queries in the City/ZCF files...............................95

Using Address Line Show for queries in the ZIP+4 file ...............................96

Chapter 6:

Suggestion lists ............................................................................................ 97

Introduction to suggestion lists......................................................................98

Suggestion lists and CASS certification......................................................100

Chapter 7:

Add-on modules........................................................................................ 101

GeoCensus...................................................................................................102

Mover ID for NCOALink............................................................................104

Z4Change.....................................................................................................105

RapidKey Library........................................................................................106

Delivery Point Validation (DPV) ................................................................108

Residential Delivery Indicator (RDI) ..........................................................109

Early Warning System (EWS).....................................................................111

Enhanced Line of Travel (eLOT) ................................................................112

LACSLink....................................................................................................113

SuiteLink......................................................................................................114

DSF2............................................................................................................116

Appendix A:

Guidelines for input address data ............................................................117

Guidelines for data entry: U.S. addresses....................................................118

Guidelines for multiline addresses...............................................................120

Appendix B:

Status and error codes...............................................................................121

Status codes for assigned addresses.............................................................122

Error codes for unassigned addresses..........................................................124

Appendix C:

How to save processing time.....................................................................131

How to set up your computer for top ACE speed........................................132

Sort the input database by ZIP Code ...........................................................133

Job setup tips for ACE Views and ACE Job ...............................................135

Tips for running batch jobs..........................................................................136

Index............................................................................................................137

ACE User’s Guide

Preface

About ACE ACE stands for Address Correction and Encoding. ACE corrects and

standardizes address data and assigns codes for postal automation, data enrichment, and other purposes.

ACE comes in many forms because there are so many systems in which companies concepts that apply to

ACE is one part of a whole line of programs for data quality and postal automation. For more information about our products, visit

http://www.firstlogic.com/customer.

About this guide This guide explains what ACE can do and how you can apply it in common

situations. We point out the features and options the “how to” details. For specific and feature, see the online product.

need address hygiene or postal coding. This guide explains basic

all forms of ACE.

you need, but we don’t delve into

instructions on how to set up each ACE option

help or reference manual for your particular ACE

Access the latest documentation

You can access product documentation in several places:

 On your computer. Release notes, manuals, and other documents for each

product that you have installed are available in the Documentation folder. Choose Start > Programs > ACE > Documentation.

 On the Customer Portal. Go to www.firstlogic.com/customer, and then

click the Documentation link to access all the latest product documentation. You can view the PDFs online or save them to your computer for viewing or printing.

Preface

Conventions This document follows these conventions:

Convention Description

Bold

Italics

> in menu commands

Screen graphics This guide shows graphics of ACE Views setup windows. ACE Views is a

graphical tool for setting up ACE job

Highlights file names, paths, and text that you should type exactly as shown. For example, “Type

Both emphasizes text and indicates text for which you should substitute your own data or values. For example, “Type a name for your file, and the

Indicates commands that you choose from menus in the following format: Menu Name > Command Name. For example, “Choose File > New.”

Alerts you to important information and potential problems.

Points out special cases that you should know about.

Draws your attention to tips that may be useful to you.

.txt

extension (

testfile

cd\dirs

.txt

).”

.”

files. Job files are organized into groups of parameters called blocks. Each V iews setup window corresponds to a block in the job file. To avoid speaking too specifically about the job file or Views, in this guide we use the term section (for example, “...in the Execution section of your job...”).

ACE User’s Guide

Related guides

This ACE User’s Guide is only one of the guides you’ll need in order to install, learn, and operate ACE.

Installation  T o install your ACE software and support file s, follow the instructio ns in our

System Administrator’s Guide.

 ACE input and output fields are listed and explained in the Quick Reference

for Views and Job-File Products and the Quick Reference for Libraries.

Operating your software

 If you have ACE Views, you should read the Views Quick Start Guide. This

guide will help you understand what to expect from Views.

 If you have ACE Job or ACE Views, you need to read our Database Prep

guide. That guide explains how ACE works with databases, some preparation tasks you must perform, and how to convert databases from one type or format to another. You should read Database Prep before trying to run ACE or any of our batch programs.

 When you have learned what you need from this guide, see the appropriate

ACE reference manual, which contains the “how to” information that you need to run or write your ACE program. There are separate reference manuals for ACE Job, and ACE Library. In ACE Views, the online help serves the purpose of the reference manual.

Official publications  The U.S. Postal Service offers many helpful publications. Ask your

postmaster or USPS account representative. about them. In particular, we recommend USPS Publication 28, Postal Addressing Standards. That document lists most of the guidelines that ACE must follow when it standardizes addresses.

 USPS rules regarding CASS certification, the 3553 form, and more are

published in the Domestic Mail Manual (DMM), the official source of mailing rules.

Preface

Documentation

Complete documentation set

Access the latest documentation

Your complete ACE documentation set includes the following:

 ACE User’s Guide  ACE Job-File Reference (if you use ACE Job)  ACE Library Reference (if you use ACE Library)  Mover ID User’s Guide for NCOA

 Quick Reference for Views and Job-File Products (if you use ACE Views or

NCOA

Link

add-on option)

Link

(if you purchased the Mover ID

Job)

 Quick Reference for Library Products (if you use ACE Library)  System Administrator’s Guide  Edjob User’s Guide  Database Prep  Views Quick Start Guide (if you use ACE Views)

You can access documentation in several places:

 On your computer. Release notes, manuals, and other documents are

available in the Documentation folder. Choose Start > Programs > Firstlogic Applications > Documentation.

 On the Customer Portal. Go to www.firstlogic.com/customer, and then

click the Documentation link to access the latest documentation. You can view the PDFs online or save them to your computer.

ACE User’s Guide

Software versions

About ACE versions Three separate version numbers exists for three separate areas of ACE:

 ACE. This is the overall version of the ACE software.  CASS-certified ACE. This is the most recently CASS-certified version of

ACE. This version may or may not be the same as the ACE version. If the CASS version is less than the ACE version, it is only because the newer version of ACE did not include changes to CASS-related areas of ACE, and so re-certification was not necessary.

 Mover ID. This version applies to ACE’s Mover ID for NCOALink option.

Where version numbers appear

You can see the versions of ACE, CASS-certified ACE, and Mover ID in the following ways:

 Release notes. With each ACE release, the release notes will tell you the

ACE, CASS, and Mover ID version numbers.

 Command line options. Use the command line option pwace /rev or

pwace -rev to see what your installed versions are. Or use t he comma nd li ne option pwace /lib or pwace -lib to see the installed versions for a whole slew of underlying components that make up ACE.

 Help menu. In ACE Views, choose Help > About ACE Views to see what

your installed versions are. Choose Help > Library Version to see the installed versions of the underlying components that make up ACE.

 Library function. In ACE Library, call ace_get_revision to see what your

installed versions are.

 Mover ID Summary. In the Mover ID Summary report header, you can see

the ACE version and the Mover ID version that you used when processing your Mover ID job.

 CASS 3553 report. The CASS report shows the version of ACE that was

most recently CASS-certified.

Preface

ACE User’s Guide

Chapter 1: Introduction to ACE

This chapter explains how ACE works and what you can do with it.

The addresses used in this guide are for example purposes only. Because of the continuous updates to directory data, it is possible that the addresses shown here may be assigned differently in the future.

Chapter 1: Introduction to ACE

What is ACE for?

ACE is an abbreviation for Address Correction and Encoding. ACE does just that: You give ACE an address, and ACE gives you back a corrected, complete, standardized form of that address. At the same time, ACE can assign codes for postal automation and other purposes.

Address hygiene Most ACE users simply want to make sure that their address data is correct and

complete. To deliver this, ACE relies on directories of addresses that are known to the governing postal service.

 ACE verifies that the city, state, and ZIP Code agree with one another. If you

have only a city and state, ACE usually can add the ZIP Code, and vice versa.

 ACE can standardize the address line, too. For example, ACE can correct a

misspelled street name, fill in missing information, and strip out unnecessary punctuation marks.

 If your address list contains any undeliverable addresses (vacant lots,

condemned buildings, and so on), ACE can identify these for you.

 ACE can also assign its own diagnostic codes to help you find out why

addresses were not assigned or how they had to be corrected.

Preparation for matching

Input record Output record

Line1 = 1390 valhalla Line2 = deltona pines fl 32738

Address City State ZIP

= 1390 Valhalla Street = Deltona = FL = 32725

Many of our users take their address data from ACE into some sort of addressmatching or database-consolidation program. When comparing two addresses to see if they match, it’s important to have standardized data—otherwise, the smallest typo might keep you from finding matches you should find. In addition, ACE can break an address down into its smallest component parts—for example, separating the house number from the street name—so that your matching software can compare individual items, apple-to -apple.

Input record Output record

Line1 = 7600 MAINE Line2 = NILES IL 60701

Prim_Range Predir Prim_Name Suffix City State ZIP

= 7600 = W = Main = St = Niles = IL = 60714

Data enhancement With ACE you can app end many useful cod es to yo ur records, such as t he coun ty

number or name, congressional district number, and the 9-1-1 conversion indicator. If you purchase the GeoCensus Option, you can use ACE to assign latitude, longitude, and census tract and block information. That information sets the stage for mapping, demographic marketing, and other applications of your address data.

ACE User’s Guide

Input record Output record

Line1 = route 1 box 44a Line2 = stodard wisc

Address City State ZIP

ZIP4 County_Number County_Name Congress_District 9-1-1 Conversion Latitude Longitude MSA Tract_Block

= RR 1 Box 44A = Stoddard = WI = 54658

= 9610 = 123 = Vernon = 3 = T = 43.693812 = -091.188558 = 0000 = 9607001

For more information about ACE’s optional features, see “Add-on modules”

on page 101.

Postal automation Some companies use ACE to help them qualify for discounted postage on their

mailings. ACE can assign these postal-automation codes to help you qualify mailings for the lowest possible rates.

Input record Output record

Line1 = 1070 shorewood dr Line2 = la crose wi S46Ol

Address City State ZIP

ZIP4 DPBC CAR T CR_Sort_Zn LOT LOT_Order

= 1070 Shorewood Drive = La Crosse = WI = 54601

= 7019 = 70 = C026 = F = 0122 = A

Chapter 1: Introduction to ACE

Some examples of input and output records

Add postal automation codes

The U.S. Postal Service offers very attractive postage discounts to mailers who apply barcodes and presort their mail. To qualify for these incentives, you are not required to standardize your address data. But you need a va riety of postalautomation codes for barcoding and sorting.

Input record Output record

Line1 = 1070 shorewood dr Line2 = la crosse wi

Data hygiene ACE is also used by companies who have no intention of mailing. They simply

Orig_Line1 Orig_Line2 ZIP ZIP4 DPBC CART CR_Sort_Zn LOT LOT_Order

= 1070 shorewood dr = la crosse wi = 54601 = 7019 = 70 = C026 = F = 0122 = A

want assurance of address data integrity and quality, and a way to sift out flawed records. By correcting and standardizing address data, and producing individual components, ACE also can help you improve the performance of recordmatching programs.

Input record Output record

Line1 = 7600 main Line2 = 60701

Prim_Range Predir Prim_Name Suffix City State ZIP

= 7600 = W = Main = St = Niles = IL = 60714

Catch flawed or fraudulent addresses

ACE User’s Guide

ACE helps you detect addresses with critical problems. For example, the address below is marked as unsuitable for delivery of mail. (It is a cemetery.)

Input record Output record

Line1 = 2101 stat rd Line2 = wi 54603

Address Last Line Match_9 Match_Un Err_Stat

= 2101 State Road = La Crosse WI 54601 = T = T

(indicates undeliverable)

= E600

Correct and convert format

In some places, ACE can assign with remarkably little input data. As long as the input postal code is valid, ACE may be able to assign the city and state. In the example below, ACE also corrects the street name and adds the suffix. Also notice the change in field layout. We use ACE components to produce discrete fields in the output record.

Input record Output record

Line1 = apt 5 Line2= 1000 vin Last_Line= 54603

Prim_Addr Sec_Addr City State ZIP10 Err_Stat DPBC CAR T County

= 1000 Vine Street = Apt 5 = La Crosse = WI = 54601-3474 = SF10 = 00 = C019 = 063

Here’s another record in the same file:

Input record Output record

Line1 = Line2 = 1006 bendict ca Last_Line = biv hills calif 90210

Prim_Addr Sec_Addr City State ZIP10 Err_Stat DPBC CART Countyname

= 1006 Benedict Canyon Dr = = Beverly Hills = CA = 90210-2837 = SE90 = 06 = C061 = Los Angeles

Append corrected fields

When ACE corrects an address, t he changes may seem dramatic. In the next example, ACE changes both the city and the postal code. The directory indicates that Edina is a branch post office, and PO boxes are located in the main post office in Minneapolis. Also notice t hat we retain the orig inal fie lds, and use ACE components to append corrected data.

Input record Output record

Line1 = terabyte records Line2 = po box 100 Line3 = edina mn 55424

Orig_Line1 Orig_Line2 Orig_Line3

Extra4 Address City State ZIP10 Rec_Type Match_9 Match_5

= terabyte records = po box 100 = mn 55424

= Terabyte Records = PO Box 100 = Minneapolis = MN = 55440-0100 = P = T = T

Chapter 1: Introduction to ACE

Some examples of input and output records

Rearrange address elements

Puerto Rico (PR) value

In a multiline format of up to 12 lines, ACE can rearrange data extensively to produce a more compact, readable address block.

Input record Output record

Line1 = rob macgregor Line2 = 8 market street n Line3 = #318 Line4 = sycamore building Line5 = boston ma Line6 = 02109

Std_Line1 Std_Line2 Std_Line3 Std_Line4 Std_Line5 Std_Line6 Record_No Congress Countyname CAR T CR_Sort_Zn

= Rob MacGregor = Sycamore Building = 8 N Market St Ste 318 = Boston MA 02109-1609 = = = 384935 = 9 = Suffolk = C038 = F

ACE was the first ZIP+4 program to pass the Postal Service’s tough Puerto Rico (PR) CASS test.

Input record Output record

Line1 = 24 calle 2 Line2 = urb vis del atla Line3 = arecoba 00621

Urb Address City State ZIP ZIP4 Fac_Type

= Urb Vista Del Atlantico = 24 Calle 2 = Arecibo = PR = 00612 = 2959 = U

Update the input file ACE Views and ACE Job offer the option to updat e t he in put file. For example,

suppose we have four million records in the customer database, but only 50,000 of those have been added since the last time we ran ACE. In this sit uation it often makes sense to have ACE update those new records where they are.

Our example is a two-line format, to al low extra room for address-line data. This particular record happens to contain two address lines. The input postal code is valid for PO Boxes, but this PO Box number is bad. So ACE assigns to the street address, and changes the postal code accordingly.

Input record (before) Input record (after update)

Company Line1 Line2 City State ZIP10 DPBC Err_Stat

= riverfront = 944 green bay = po box 8817 = la crosse = wi = 54602 = =

Company Line1 Line2 City State ZIP10 DPBC Err_Stat

= Riverfront = PO Box 8817 = 944 Green Bay St = La Crosse = WI = 54601-6255 = 44 = S91000

ACE User’s Guide

ZIP Code realignment ACE incorporates a feature called ZIP Move, based on a USPS file of the same

name. ZIP Move marks those addresses that are affected when a post office opens or closes, or when the USPS activates a new ZIP Code.

Many times, a ZIP Move address will simply have a change in ZIP Code. However, it is also possible that ACE will change the city name (examples below) or the PO box number. For some users, a change in both the city name and the ZIP may seem alarming, as if an error. But it is a correct standardization, and it does make mail more deliverable.

Input record Output record

Line1 = 6 ginger lake drive w Line2 =

Input record Output record

Line1 = 7806 pine rd Line2 =

edwardsville

philadelphia

62025

19118

Address City State ZIP ZIP4 ZIP_Move

= 6 Ginger Lake Dr W =

Glen Carbon

= IL =

62034

= 3304 = T

= 7806 Pine Rd =

Glenside

= PA =

19038

= 8527 = T

Because of ZIP Move, ACE may also change a PO box number. This occurs when two post offices are merged, and PO box numbers have to be changed to avoid duplication.

Chapter 1: Introduction to ACE

Address input and output

We’ve been talking about ACE in terms of you presenting raw address data and getting back processed data. There are two ways of handling this. Most people use a combination of them.

Concept Explanation Details

Lines The first method is useful when you want to keep output

Page 19 address data in the same arrangement of fields as were input. ACE applies intelligent abbreviation, when necessary, to keep the data within the same field lengths. Data is capitalized and standardized according to way you set the standardization style options.

Components Choose the second method when you want the output address

Page 20 broken down into smaller elements than you input. Also you can retrieve additional fields created by ACE, such as the error/status code. The style of some components is controlled by the standardization style options; most are not. ACE does not apply any intelligent abbreviation to make components fit your output fields.

Think of ACE as a box with four sections, or quadrants. Each input address is loaded into the first quadrant (upper left corner of diagram). After processing the address, ACE fills in the other three quadrants.

Input Inside ACE Output

StandardizedUnstandardized

aw input data

Lines

Input Lines

• Address

• City, State, Postcode

...

Standardized Lines

•

Address

•

City, State, Postcode

...

Standardized, but in the same format

Components

ACE User’s Guide

Parsed, Unstandardized Components

• City State or province

•

ZIP or Postcode

•

• House number

• Street name

• Suffix (Ave, St, Dr,

...)

• Directional (N, E, ...) Unit (Suite, Apt, ...)

•

Apartment number

Parsed, Standardized Components

• City State or province

•

ZIP or Postcode

•

• House number

• Street name

• Suffix (Ave, St, Dr,

...)

• Directional (N, E, ...) Unit (Suite, Apt, ...)

•

Apartment number

Broken down into components and standardized

Broken down into components, but not standardized (not available in all products)

The basic set of input and output fields

The basic fields give ACE flexibility to work with a wide variety of formats and record layouts.

Input and output fields



Name_Line



Title



Firm



Address



Unit



City



State

In this manual, we only introduce you to these fields. For full details about these fields see the Quick Reference for Views and Job-File Products and the Quick Reference for Libraries (ACE Library customers).

You will not use all of these fields. For any particular job, you’ll select and use perhaps a dozen of these fields at most, usually less. The task of setting up ACE involves figuring out which fields are most appropriate for the data that you have to process.



ZIP



ZIP10



Last_Line



Country



Line1-12



ZIP4CART



DPBC



Chk_Digit



LOT



LOT_Order



County



Urb

ACE Views and Job These are called “PW fields.” PW fields and how to set them up are explained in

our Database Prep manual. If you want, ACE can automatically upda te PW fields in your input database. Or if you prefer, ACE can automatically copy data over to an output file, while updating the address fields. Either way, ACE determines which fields to update based on your setup of PW fields.

ACE Library The fields listed here are lines in the ACE address handle. ACE automatically

updates these lines. To pass input data and get results in the same arrangement of fields, you use ace_set_line() and ace_get_line().

Here, we show these fields by their “English” names; actual symbol names are listed in the Quick Reference for Libraries. ACE Library does not have a Title field, and does not handle title data.

PrintForm ACE PrintForm ACE always uses the input fields Line1 through Line 6. The exact

number of fields used depends on how many lines you enclose when you mark the address block. You do not need to take any other action to set up input fields.

Chapter 1: Introduction to ACE

Codes and components that ACE can add

ACE offers a large set of codes and components. If you want, you may use this information to update or augment your records. Full details about them are covered in the Quick Refer ence for Views and Job-File Products and the Quick Reference for Libraries.

There’s an important dif ference between these components and the basic ACE fields. ACE can automatically update the basic fields. ACE does not do anything automatically with these components. If y ou want to use t hem, then you will have to select and handle them yourself, manually.

Input fields



Address



Aline



Alias Type



CART



Chk_Digit



City



City_LLIDX



City_Place



Congress



County



CountyName



CR_Sort_Zn



DPBC



DPV_cmra



DPV_ftnote



DPV_status



Err_Stat



Error_Code



EWS_match



Extra1-10



Extran_PMB



Extran_Sec



Extraneous



FacT ype



FIPSCODE



Firm



Foreign



LACSCODE



Last_Line



Long Postdir



Long Predir



Long Suffix



LOT



LOT_Order



Match_5



Match_9



Match_Un



NC_Firm



NC_Secaddr



NC_Srange



NC_Unit



Newline



Postdir



Predir



Prim_Addr



Prim_Name



Prim_Range



RDI



Rec_No_Out



Rec_Type



Record_No



Remainder



Sec_Addr



Sec_Range



Stat_Code



State



Std_Line1-12



Suffix



Unit_Desig



Urb



USPS_Unit



ZIP



ZIP4



ZIP9, ZIP10



ZIP_Move



ZIP_Type

Codes When ACE matches an address to the directories, it assigns many codes. Some

are useful for postal automation, while others give status information about the address.

Components Many of the components result from address parsing—breaking down address

data into separate pieces. These components are useful when you want to change the format of database records.

For example, suppose your Address fields contain street and apartment data lumped together, but you would like to convert them into two separate fields. Then you would use the Prim_Addr (primary) and Sec_Addr (secondary) address components.

ACE User’s Guide

ACE Views and ACE Job

The fields listed here are called “AP fields.” (AP is short for “application.”) You may post these fields manually, either to update your input file or to update your output file(s).

ACE Library Call ace_get_component() to retrieve these compone nts. Actu al define names a re

listed in the Quick Reference for Libraries.

PrintForm ACE Some of the fields listed here are available as “DB fields.” (Refer to the

PrintForm User’s Guide for a list.) You can use DB fields as the basis for triggering inserter marks, and for constructing filters and user-defined grou ps.

Chapter 1: Introduction to ACE

Overview of ACE products

The following ACE products are available.

 ACE Job  ACE Library  ACE Views  PrintForm ACE

Overview of ACE products and features

Feature ACE Views ACE Job PrintForm ACE ACE Library

Batch mode Interactive Suggestion lists

Postal forms Statistical reports and record listings Directory queries

Z4Change option GeoCensus option RapidKey option Delivery Point Validation (DPV) Residential Delivery Indicator (RDI) Early Warning System (EWS) Enhanced Line of Travel (eLOT) Mover ID NCOA

Link

LACS

DSF

Link

Suite

Link

     

Can be customized

      

Integral, graphical Show utility



Separate, console Show utility



Separate, console Show utility



Query functions

       

                    

With USPS permis-

sion

        

ACE Job

ACE User’s Guide

ACE Job is batch software for processing database files. It takes records from one input database. Y ou can choose either to update the input database or to send ACE output to another database. ACE Job also produces statistical reports and postal forms.

ACE Job does not directly support the task of job setup. Instead you set up your job in a text file called a job file. You edit the job file with a text editor or word- processing program. Here’s an excerpt:

BEGIN Auxiliary Files================================== City Directory (path & city09.dir)... = city09.dir

ZCF Directory (path & zcf09.dir)..... = zcf09.dir

ZIP+4 Directory 1 (path & zip4*.dir). = zip4us.dir

When your job file is ready, you start ACE Job. On most computers you type a command line; on Windows systems, you may type a command line or doubleclick the ACE program icon in your file explorer. When ACE Job starts, it verifies the entries in your job file. If there is an error, the program reports it and stops. You edit your job file, fix the problem, and start ACE Job again.

Opening the Input file Verification Error Post to Input File Block: 1, Parameter: 2 The copy parameter specifies an invalid destination, <ap.error_code, error_code>

When verification is complete, ACE begins processing your job. Duri ng processing, ACE displays progress messages on your screen. Here is an example of a progress message:

Input File = mailfile.dbf Starting Record = 1 Ending Record = 19693

-------------------------------- = -------------Records Processed = 19000 Records Deleted (but processed) = 0 Records Passed by Input Filter = 19000 Undeliverable Addresses = 58 Foreign Addresses = 0 Other Addresses Not Matched = 2499

-------------------------------- = -------------Addresses Assigned = 16443 Percentage Matched = 86.85

ACE Views ACE Views is a graphical, helpful program for setting up ACE jobs. ACE Views

presents easy-to-use, graphical screens with menus, wizards, toolbars, and onlin e help, which help you to save time and prevent setup errors.

ACE Views can set up some parts of your job automatically, through a wizard. And it verifies your job setup as you go, so errors are caught and corrected more quickly.

Chapter 1: Introduction to ACE

When it’s time to process your job, you simply choose a command from a menu. (There is no command line to memorize.) Many users perform job setup and processing on the same computer. It is also possible to use ACE Views for job setup on one computer, and then process with ACE Job on an other, perhaps more powerful, computer.

ACE Views includes the following features:

 interactive mode for data entry, or for cleaning up addresses that couldn’t be

assigned in batch mode

 Quick ACE, a handy tool for checking an address  interactive, graphical Show programs for querying the postal directories

PrintForm ACE PrintForm ACE is a program for processing print-image files. It is part of the

PrintForm Mailing System, an integrated set of programs that bring postal automation and discounts to forms, statem ents, and other docu ments produced on high-speed laser printers and inserters.

PrintForm ACE assigns postal codes and offers the option of full address standardization. Based on postal codes assigned by ACE, PrintForm can add the Postnet barcode to your documents. This barcode, together with the mailstream preparation of PrintForm Presort, qualifies you for very attractive postage discounts and faster delivery.

ACE Library The ACE Library is a tool for programmers. Programmers can use ACE Library

to build ACE features into their own program, such as a data-entry or databasemanagement program. End users may not even be aware that they are using ACE at all.

ACE Library is a toolkit of callable functions. You link ACE directly into your program, either as a static or (on Microsoft Windows) a dynamic library.

Library users have access to some information and features that are not available through our ACE applications. However, Library users must provide their own support for database or terminal input and output, tallying statistics, and writing reports. (ACE Library does produce postal forms.)

ACE Library supports many languages, compilers, operating systems, and platforms. See the ACE Library Reference for details.

RAPID RAPID stands for Rapid Application Integration Deployment. RAPID l ets you

integrate technology (ACE, IACE, DataRight, DataRight IQ, Mat ch/Consolidate , and Presort) into your own applications.

RAPID comes with several interfaces (namely, C++, Java, and ActiveX). These interfaces let you handle various events, so that you have complete control over the display of the processing output. RAPID interfaces give you all the power of RAPID-enabled job-file products in a way that is easy to integrate into your own applications.

ACE User’s Guide

An in-depth explanation of the assignment process

When ACE assigns an address, it creates a status code that tells you how the input address differs from the “ideal” address. When ACE cannot assign an address, it creates an error code, which tells you why the address could not be assigned.

Terms for address components

The terms used to describe components that make up an address are shown below as they might appear on an address label.

W e use the same terms as th e U.S. Postal Service (USPS). This make s sense when you realize that ACE is subject to many Postal Service rules and regulations.

There is one exception. According to official usage, th e ZIP+4 code is a ni ne-digit number, consisting of the ordinary ZIP Code and a four-digit, add-on code. However, because most users handle ZIP and ZIP+4 as separate data fields, we find it more convenient to use the term “ZIP+4” to mean only the last four digits.

Postal barcode

Firm

Dual address

Assigned address

Last line

29501299173

John Dough, President North American Bakery Supply PO Box 9175 2001 West Harbor Drive North Suite 152 Onalaska WI 54650-4331

StateCity

Postal codes:

54650-4331 01 9

ACE uses postal directories

ZIP ZIP+4 DPBC check-digi

(Together, these four numbers are the basis for the

postal barcode. Usually, only the ZIP and ZIP+4

are printed in numeric form. )

Address-line components:

Secondary addressPrimary address

2001 West Harbor Drive North Suite 152

Primary range

name

Predirectional

PostdirectionalPrimary

Unit designatorSuffix

Secondary range

To correct addresses and assign codes, ACE relies on databases called postal directories. Just to make sure there’s no confusion: We are using the word directory here in the same sense as the telephone directory—not a directory in a

computer’s file system. When ACE uses the postal directories, it’s similar to the way that you use the

telephone directory. A telephone directory is a large table in which you look up something you know—someone’s name—and read off something you don’t know—their phone number. That is sort of how ACE works.

Chapter 1: Introduction to ACE

In the process of looking up someone i n t he phone book, you might discover that their name is spelled a little dif ferently from the way y ou thou ght. That gives you an idea how ACE corrects misspelled street and city names, and other errors.

Sometimes it doesn’t work out. We’ve all had the experience of looking up someone and being unable to find their listing. Perhaps you’ve looked up someone and found several people listed with a similar name—and you didn’t have enough information to tell which listing was the person you wanted to call. Problems just like these can prevent ACE from fully correcting and assigning an address.

Four files are most important

Four of the directories are most important:

Directory Description

City The City directory is a table of city names, states and ZIP Codes. It is orga-

nized by state and city.

ZCF ACE uses the ZCF (ZIP City File) directory. It contains the same data as

the City directory, but is organized by the ZIP Code.

National The National directory is organized by ZIP Code. It lists street names,

ranges of house numbers, and postal and other codes. (We’ll show you the data more closely in a moment.)

RevZIP4 The reverse ZIP+4 directory (

postal codes when the input data includes a unique ZIP Code and valid ZIP+4.

revzip4.dir

) enables ACE to assign more

The first two directories are like a regular phone book and a reverse directory. They are relatively small, because they contain one record per possible combination of city/state/ZIP Code.

The national directories are many times larger because they contain one record per city block, building, or company. The U.S. national directory contains over 30 million records, representing a total of over 130 million places where mail is delivered; the file size about half a gigabyte.

How ACE works There are many kinds of ACE programs, but no matter how different they may

seem, all ACE programs contain the same technology at their core. We call this core the “assignment engine.”

ACE follows these steps when it processes an address:

1. Input. ACE processes one record at a time.

2. Parse. ACE breaks down the address into its components: postal code, city,

state or province, house number, street name, and so on.

3. Pre-standardize. ACE pre-standardizes the parsed components to match to

the patterns of the postal directories. For example, ACE converts the data to full capitals, corrects any nonstandard abbreviatio ns, and strips out punctuation and extra spaces.

4. Match last line. ACE reads the city, state, and ZIP Code. Then ACE searches

for matching data in the City directories.

ACE User’s Guide

ACE looks up the city and state to find all ZIP Codes for the city; then it looks up the input ZIP Code, to find all possible cities for that ZIP Code. By comparing the results of these two look-ups, ACE verifies that the last-line components agree with each other. ACE may also correct the spelling of the city and state.

If the last-line components do not agree, ACE expands the search to encompass a larger metro area.

If matching is successful at Step #4, the address is called a last-line match.

5. Match address line. ACE searches the National directory for records that

might match the input address line, secondary address, and firm. ACE evaluates all potential matches and assigns a confidence score to each

one. ACE then selects the record with the highest confidence score. To be chosen, a record must have a high co nfidence score, and score distinctly higher than any other possible matches.

After ACE chooses a matching record, it finalizes the postal code and assigns other codes.

If matching is successful at Step #5, the address is called an address-line match.

6. Output. ACE offers four types of data for output:

 Standardized data in the same layout as the input fields.  Raw data parsed into discrete components (not available in PWACE).  Standardized data in discrete components.  Additional codes and components generated during look-up.

Chapter 1: Introduction to ACE

ACE User’s Guide

Chapter 2: Standardization and style options

ACE gives you comprehensive control over the extent and style of address standardization. This chapter explains the options.

The addresses used in this guide are for example purposes only. Because of the continuous updates to directory data, it is p ossible that in the future, the addresses use here may assign differently.

Chapter 2: Standardization and style options

About the Standardization Style options

Standardization means that ACE changes your data to conform to the postal directories, standardize your However, if you choose to standardize, ACE can correct many types of data errors. This helps ensure the integrity of your databases, makes mail more deliverable, and gives your communications with customers a more professional appearance.

If you prefer not to standardize your address data—or to standardize only part of it—you can still use ACE to capitalize many fields.

As we go through all the options, we point out when each option does, and does not, take effect. Our goal is to enable you to make your own choices and feel confident that you will achieve the results you intend.

Here is a guideline to remember: If you retrieve a component that is part of something larger , the S tandardization S tyle option will apply. For example, within the Address component, the abbreviated or spelled-out style of suffix and directionals is controlled by those options. The same is true for the p lace-name conversion of city name within the LastLine component.

But if you retrieve the suffix, directionals, or city name by itself, then the Standardization Style option does not apply. Instead, you make your choice by selecting from two or three flavors of components, each with a slightly different name.

and to USPS guidelines for addressing mail. You are not required to

addresses. ACE doesn't require this, nor does the USPS.

Product Description

ACE Views and ACE Job

ACE Library The information in this chapter will help you set parameters when you

PrintForm ACE You control ACE by setting parameters at the Assignment Options

The information in this chapter will help you set parameters in the Standardization Style block and the Multiline Style sections.

Where we refer to “default” settings, we mean the initial settings that we provide in the master job file ( job file in ACE Views. Please do not interpret “default” to mean that you can leave a parameter blank, because all the parameters discussed here require some entry .

call ace_set_option() or set up your ACE_Options_Config_File (

aceopts.cfg

window. However, the style options described in this chapter are pre set and you cannot adjust them. PrintForm uses the default values for ACE style options.

master.ace

) or when you start a new

ACE User’s Guide

City place names

A place name is a geographical name for an area that does not have its own post

Place names are an issue because, according to the U.S. Postal Service, the

office. city name is located. This minds of many people, It’s a matter of perception and vanity. That’s why place names are also called vanity addresses .

For example, Hollywood, California is served by the Los Angeles post office. The USPS says mail to Hollywood residents should be addressed to Angeles post office. Of course, Hollywoo d residents might prefer that their address be used.

The City directory lists many place names with a code that indicates that they are not suitable for mailing purposes. That’s how ACE detects place names in your input data.

Your options When we undergo CASS testing, we have to prove that ACE can convert place

names. However, you don’t have to convert when processing your own records. You might prefer to retain place names, to avoid offending your customers. With ACE, you have the option either to preserve place names or to convert them to postal city names:

printed on a mail piece is supposed to be the city where the post office

is not necessarily the city where the recipient lives. Yet in the

their mail should be addressed to the city whe re th ey live.

the Los

vanity

Option Description

Preserve If the input city name is a place name, correct its spelling if neces-

sary, but preserve it in the output address. Given ACE produces

Convert If the input city name is a place name, replace it with the city name

chosen by the postal service. Given duces

Los Angeles

Hollywood

as output. (default setting)

as output.

Hollywood

as input, ACE pro-

as input,

ACE ignores this option when the Assign City from Input/LL Idx option is enabled.

Chapter 2: Standardization and style options

Unit designator standardization

A unit designator is usually a word such as apartment, suite, floor, room. A secondary address usually consists of a unit designator and a secondary range (for example, “Apt. 210” or “Ste. 300” or “Rm. 72”).

Your options ACE can standardize unit designators in your choice of two ways:

Option Description

Directory ACE converts the unit designator to match the USPS directory. For exam-

ple, if your input is “APT”, but the directory lists only suites at that address, then ACE would change the unit designator from “APT” to “STE.”

Current ACE corrects any spelling errors in the existing unit designator (for exam-

ple, changing SUIT 5 to STE 5).

See USPS Publication 28 for a complete listing of valid unit designators.

ACE User’s Guide

Style of suffix and directionals

Your options By default , ACE pr oduces abbreviated forms of suffixes (Ave, St, Blvd, and so

on) and directionals (N, NE, SW). However, you may choose either to abbreviate them, spell them out as full words, or preserve the style of the input data. For example:

Option Description

Short ACE converts suffixes and directionals to official abbreviations (for exam-

ple, “Cedar Street West” becomes “Cedar

Long ACE converts suffixes and directionals to full English words (for example,

“Cedar St W” becomes “Cedar

Preserve ACE preserves the style of suffixes and directionals as they were input (for

example, “Cedar Street W” remains “Cedar misspellings are corrected; for example, ACE would correct “Cedar Valley

Rood

” to “Cedar Valley Rd.”

Street West

If you select the Short or Long style for directionals, this may also affect how ACE standardizes some street names. Here’s why: In the USPS directory, street names that contain a directional word (for example, North Carolina) are stored as a predirectional (N) and primary name (Carolina). In this situation you might prefer the Long style, so that you will get “North Carolina St”. In the Short style, you would get “N Carolina St”; many people consider that just too terse.

St W

”).

Street W

”). However, some

Chapter 2: Standardization and style options

Private mail boxes (PMB)

Private mail boxes are like post-office boxes, except that they are hosted by private companies. ACE can recognize certain forms of private mail box (PMB) data when it appears in an address line. You have the option of keeping address and PMB in the same field, or breaking the PMB off to a separate field.

The list at right shows forms of input that ACE recognizes. These may be followed by a punctuation mark such as the pound sign (#). All forms will be standardized to “PMB” followed by a space and the box number.

PMB P M B PRIVATE MB PRIVATE MAIL PRIVATE MAILBOX PRIVATE MAIL BOX

Your options ACE can do one of the following when it recognizes a private mail box:

 Keep the PMB on the address line.  Break the PMB off to a separate field.

ACE Views and ACE Job

To keep the PMB on the address line, set the parameter in the Standardization Style block: Append PMB to Address Line. By default it is turned on (Yes).

To separate the PMB into a separate field, turn off this option a nd post to your output file the new output field AP.NP_SecAddr. The maximum length of this data is 20 characters. It contains both the designator PMB and the box number.

If you wish to keep the designator and the bo x numb er in separate field s, p ost the new output fields AP.NP_Unit and AP.NP_SRange. Both fields have a maximum length of 10 characters.

ACE Library To keep the PMB on the address line, call ace_set_option() with the option

symbol ACE_OPT_APPEND_PMB. For the value symbol, use either TRUE or FALSE. The default is TRUE.

T o break the PMB of f to a separate field, call ace_get_component() to retrieve the new output component ACE_NP_SECADDR. The maximum length of this data is 20 characters plus null. It contains both the designator PMB and the box number.

If you wish to keep the designator and t he bo x number in separate fields, retrieve the new output components ACE_NP_UNIT and ACE_NP_SRANGE. Both fields have a maximum length of 10 characters plus null.

ACE User’s Guide

Standardize only assigned addresses

By default, ACE will not standardize an y unassigned address. If you wan t ACE to standardize unassigned addresses, you must set the option provided for this purpose, as described below.

ACE Views and ACE Job

When an address is not assigned, ACE will produce unstandardized data, just as it was input, for all output fields.

To standardize unassigned addresses, turn on the Standardize Unassigned Address option in the Standardization Style section. With this option enabled, ACE will do the best possible job of parsing and standardizing any unassigned addresses. (By default, this option is turned off.)

ACE Library Call ace_set_option() with the symbol ACE_OPT_STND_UNASSIGNED_ADDR.

For the value symbol, use either

TRUE or FALSE.

The default setting is FALSE. When an address is not assigned, ACE will produce unstandardized data, just as it was input, for lines and components. However, address components (such as house number, street name, suffix, etc.) will not be available via ace_get_component().

To standardize unassigned addresses, set this to TRUE. With that setting, ACE will do the best possible job of parsing and standardizi ng any unassigned addresses.

Chapter 2: Standardization and style options

Capitalization (case conversion)

Thi

Your options ACE offers three styles of case conversion:

Option Input Output

UPPERCASE 100 Main St 100 MAIN ST Mixed Case 100 Main St 100 Main St lowercase 100 Main St 100 main st

When you have Mixed Case input

When you have

UPPERCASE input

When your input data is in mixed case and you choose Upper and Lower for ACE’s Case setting, ACE leaves your name and firm data as t hey were input, and standardizes only the address fields.

s example shows how an address with mixed case data is affected when the Case setting is set to Upper and Lower.

Name and firm data stays the same. The mixed case of the data is unchanged.

Address data is standardized to correct mixed case.

You might run into occasional capitalization errors if you ask ACE to co nvert

UPPERCASE to Mixed Case. ACE is good at this, but not fool-proof. Tha t’s

from because Mixed Case is subject to exceptions. These include abbreviations that should be in full caps (especially firm names such as

MCA Records) and words

that include an internal capital (MacArthur).

ACE User’s Guide

For guidance about exceptions , ACE relies on internal software and a capitalization dictionary (pwcas.dct) of known exceptions.

If your full-caps data includes an exception that is not listed in the dictionary, ACE may not capitalize the word correctly. For example, if you input

RECORDS

Records. For this situation, we recommend that you use our DataRight IQ

and MCA is not listed in the dictionary, the result would be Mca

MCA

program. Its specialty is name, title, and firm processing. It capitalizes data based on an exceptions dictionary that you can customize.

Extraneous information on address lines

Some people try to squeeze additional data into their address fields. So when

matches an address line to the ZIP+4 directory, ACE may find that your

ACE input includes example:

more information than the directory says is necessary. For

Original input ZIP+4 directory record

100 Market St., Attn Mktg 100 Market St

In this case, the USPS prefers that the additional information be stripped off. In

when we undergo CASS testing, we have to prove that ACE can do this.

fact, However, you your own records. because it may be useful for

Your options With ACE, you may choose either to retain or discard extra data in address lines.

are not required to strip off the additional data when processing

Most ACE users prefer to retain additional information,

internal mail routing.

The options are explained below. Note that these options apply only to address-line fields. ACE will always

remove extraneous information from last-line fields. Conversely, ACE will not even notice “extraneous” data in a name or firm line.

Option Description

Loose ACE retains any additional data found in the address line, even

though that data may not be necessary for mail delivery.

Strict ACE conforms to USPS guidelines and strips off any additional data.

ACE determines what is “additional” by comparing your input with the matching record in the ZIP+4 directory. Any components not listed in the ZIP+4 record will be removed from your address line.

The removed data is available as a separate output component, called Remainder.

About the Remainder field

As noted above, when ACE removes extraneous data from an address line, you still can retrieve that information through an output co mponen t called Remaind er.

Remainder is sometimes confused with another component, called Dual_Line. The difference is that Remainder usually contains extraneous data (such as an attention line), while Dual_Line pertains only to a record that contains a second, recognizable delivery address. See

“Dual address lines” on page 40 for

information about dual addresses. Remainder has also been confused with other components called Extra1-10. Extra

data is found above or below an address line. If you are processing multiline records, you might be interested in reading about the Extra components in the

Quick Reference for Views and Job-File Products or Quick Reference for Libraries.

Chapter 2: Standardization and style options

ACE Views and ACE Job

T o sele ct loose or strict standardiza tion, go to the Standardization Style block and set the Address Line Standardization parameter.

This parameter will affect your results if you use automatic posting. However, it will not affect your results if you manually post AP.Address or AP.Prim_Addr. These AP fields are always standardized in the Strict style, no matter how you set the style parameter.

If you want to retain the data that was stripped off, post AP.Remainder. For example, you could merge (concatenate) AP.Address and AP.Remainder. See the Quick Reference for Views and Job-File Products for details.

ACE Library The default style is Strict. Call ace_set_option() if you prefer the Loose style.

That call will affect your results if you retrieve the address line via ace_get_line(). However, it will not affect most components that you retrieve from ace_get_component(). Most of those components are always standardized in the Strict style.

If you want to retain the data that was stripped off, call ace_get_component() to retrieve

ACE_ADDRESS and ACE_REMAINDER. See the Quick Reference for Libraries

ACE_REMAINDER. For example, you could concatenate

for details.

ACE User’s Guide

Alias and alternate address lines

Of the 32 million records in the national ZIP+4 directory, about one million are aliases.

An alias is an alternative form of a primary address line. Aliases apply only to primary

For example, here in La Crosse, there’s a bank at the Valley View Mall, which is located “Valley View Road 16” is the might give its address as address be standardized to “3500

54601 3500 3500 VALLEY VIEW MAL ---- ---- CØØØ CØØØ PF E ALIAS FOR: STATE ROAD 16

Your options

Option Description

Convert By default, ACE converts input addresses to USPS-preferred aliases. We

Preserve You have the option to turn off alias conversion for everyday processing.

addresses (usually streets), not secondary addresses or last lines.

on State Road 16. The ZIP+4 directory record (below) indicates that

Mall” and “State Road 16” are aliases for each other , and that “S tate

form that the USPS prefers. In other words, though the bank

have to do this for the purpose of CASS testing.

Some users might be alarmed by a dramatic change such as the example above, even though it is a correct standardization. To reassure users, ACE offers the output component Alias Type (APA.Type). The value of this code indicates when a correct alias conversion has occurred.

“3500 Valley View Mall,” the USPS prefers that this

State Road 16.”

ACE Views and ACE Job

To control whether ACE will convert alias addresses, go to the Standardization Style block and set the Address Line Alias parameter. That parameter will affect

your results if you turn on automatic posting. If you post manually, you may choose either AP or APA fields:

Field type Description

AP fields Whether or not an alias is converted depends on how you set the

Line Alias

APA fields When a USPS-preferred alias is available it is produced, no matter how

the parameter was set.

ACE Library If you retrieve the processed address line via ace_get_line(), then you may control

parameter.

Address

alias conversion by calling ace_set_option(). If you retrieve the address line via ace_get_component(), then alias conversion will depend on which component you select; see the Quick Reference for Libraries for details.

Chapter 2: Standardization and style options

Dual address lines

What is a dual address?

A dual address occurs when a database record contains two address lines. Two combinations are typical:

PO box and street address: 1000 Main Street, Suite 51

PO Box 2342

Rural route or Highway Contract and street address

RR 1 Box 345 12784 Old Columbus Road

ACE can detect a dual address whether the addresses are input in the same field or in separate fields. Here are just two possibilities:

Address = RR 1 Box 345, 12784 Old Columbus Road Line1 = RR 1 Box 345

Line2 = 2784 Old Columbus Road Notice we’re talking about two address lines for the same destination. This does

not apply to a record that contains two whole addresses, such as a college database (example below). A record like this requires two passes throug h ACE, if you want to process both addresses.

Permanent address (parents) 7600 W Main St

Niles IL 60714

At-school address 6 Hairpin Dr

South Illinois Univ IL 62026

One assignment per record

ACE makes only one assignment per record. One address line will be the basis for postal coding. The other address will be parsed, but not looked up or assigned. W e call the first one the assigned addr ess, and the ot her the dual addr ess. You can get postal codes only for the assigned address.

ACE can fully standardize the assigned address. ACE can perform only very limited standardization of the dual address.

ACE User’s Guide

Effects on address layout and ZIP

ACE may switch address lines

When two addresses are input on the same line, ACE may switch them. ACE will place the assigned address on the left, and the dual address on the right.

Assigned to street address: Assigned to PO box:

100 Main St, PO Box 297 PO Box 297, 100 Main St

Swap address lines If you tu rn on ACE’s “Swap Lines” feature (see “Swapping address lines” on

page 45), ACE will move the assigned address into position immediately above the last line. For example:

Assigned to PO box: Assigned to street address:

ABC Company, Inc. ABC Company, Inc. 4439 Mormon Coulee Rd PO Box 2589

PO Box 2589 4439 Mormon Coulee Rd

La Crosse WI 54602-2589 La Crosse WI 54601-8231

In larger post offices, a separate ZIP Code often is set aside for PO boxes. As a result, ACE may change the ZIP Code when it assigns a dual-address record. For example, notice the different ZIPs in the example just above.

Your options You may express a preference about which type of address ACE should use for

assignment. You have three options

Option Description

Mailing ACE will try to assign based on the mailing address (rural route, Highway

Contract, or PO box). If the mailing address cannot be assigned, ACE will try to assign based on the street address.

Street ACE will try to assign based on the street address. If the street address cannot

be assigned, ACE will try to assign based on the mailing address (rural-route or PO box).

Position

the data is arranged in the input fields. (Think for a moment of address data as a block of data like an address label.) ACE first tries to assign the address line that is closest to the the street address; it depends entirely on how the data was entered. If the first address fails assignment, ACE will try the second address.

is the default option. ACE will select an address line based on how

lower left

corner. That might be either the mailing or

Even though you might print both add ress lines on your mail, the barcode (based on ZIP+4) often will determine where your mail is actually delivered. Now suppose you are mailing to a company that has a PO Box and a street address. Would you rather send your mail to the PO Box or to the front door? In some places, the USPS does not offer carrier delivery to street addresses, and in those areas, a PO Box address must be used.

If you use the GeoCensus Option, you should give preference to street addresses. GeoCensus information may be inaccurate or unavailable when the ZIP+4 is assigned to a mailing address.

Chapter 2: Standardization and style options

Remember that you are expressing a preference only. You may not get your preference every time. If ACE can’t assign the address type that you prefer, it tries the other address. We believe it is better to assign the non-preferred address than not to assign at all.

For example, suppose you prefer street addresses. You won’t get your preference on the address line shown below. ACE assigns based on the rural-box address, because the street address is flawed (no house number).

RR 1 Box 345, Old Columbus Road

ACE Views and ACE Job

The default way of handling dual addresses is by Position. To set your preference, go to the Standardization Style block and set the Dual Address parameter. That parameter will affect your results if you turn on automatic posting. If you post manually, you may choose a combination of AP and APD fields (see the Quick Reference for Views and Job-File Programs for details):

AP fields The assigned address will output as AP fields. APD fields The dual address will be output as APD fields.

ACE Library The default way of handling dual addresses is by Posit ion. To set your preference,

call ace_set_option(). That call will affect your results when you retrieve data with ace_get_line(). ACE also produces standardized components of each address; you may retrieve these by calling ace_get_component(). See the Quick Reference for Libraries.

ACE User’s Guide

Additional options for multiline and two-line addresses

The rest of this chapter applies to you only if you a re pro cessing mul tilin e or two-

addresses. If you’re not sure, check the examples below to see if they

line resemble your records, even loosely.

Why are there special options?

Multiline

Two-line

Your options and procedures will be different from those that you would use when processing discrete fields. When you process discrete fields, you can pick and choose which fields ACE will update. With multiline data, you can’t do this as much. So you must give ACE some instructions and let ACE handle the rest.

For example, if you had discrete City and State fields, you could update them yourself, by placing the updated City and State components exactly where you want them in your record. But in a multiline address “block,” you can’t be sure where the City and State components appear (figure below). So you can’t give ACE specific instructions about exactly where to place the updated city and state. Instead, you have to be content to tell ACE that you want the city and state standardized. Internally, ACE “knows” where the city and state appear in each address, so it can update them for you.

Possible locations of city and state data

Line1

John Smith

Line2

Acme Tools

Line3

Suite 152

Line4

308 2nd Ave

Line5

Possible arrangements of the address-line data

Ames IA 50014

Acme Tools ATTN J. Smith 308 2nd Ave, #152 Ames IA 50014

J. Smith, Acme Tools 308 2nd Ave #152 Ames IA 50014

How to control standardization of multiline address

Name Firm Line1 Line2

City State ZIP

Ste 152 308 2nd Ave

John Smith Acme Tools 308 2nd Ave Ste 152

Ames IA 50014

308 2nd Ave, Ste 152

Standardization means that ACE changes your data to conform to the postal directories, and to USPS guidelines for addressing mail. You are not required to standardize your addresses. However, if you do so, ACE can help you ensure the integrity of your databases, make mail more deliverable, and give your communications with customers a more professional appearance.

Chapter 2: Standardization and style options

Your options If your address data is i n a multi line forma t, then you hav e four options t o choose

from. If you are processing a two-line format, then only the first two of those options pertain to you.

Option Description

None Don’t standardize the address line, city, or state. (If you select this

option, you still can update the ZIP Code, if you want; see “Updating the ZIP and ZIP+4 in a multiline address” on page 49.)

Address Standardize the address line (street, PO box, rural route, and so on.),

but do not standardize the city or state. City and State Standardize the city and state, but don’t standardize the address line. Both Standardize the address line, city, and state.

ACE Views and ACE Job

ACE Library By default, ACE fully standardizes as much as possible. To set your preference,

By default, ACE fully standardizes as much as possible. To set your preference, go to the Multiline Style block and set the Standardize parameter.

call ace_set_option().

ACE User’s Guide

Swapping address lines

By default, ACE rearranges address lines to conform with USPS guidelines. ACE

eliminates any blank lines within the multiline address. Thi s feature is cal led

also Multiline Swap Lines. For example:

Input data: Result of swapping:

Line1 100 Market Street Sycamore Building Line2 Suite 202 Suite 202 Line3 Sycamore Building 100 Market St Line4 Boston MA 02109 Line5 Boston MA 02109

As you can see here, ACE moves the primary address into position immediately

the last line. The secondary address is placed above the primary, and other

above lines are order to eliminate

Your options You have three options for the Swap Lines feature.

placed above the secondary address. ACE also repositions the last line in

the blank line.

These examples show the effects of Combine Lines (next page) and Swap Lines. Most users turn on both features.

Option Description

None Don’t swap; keep components on the same lines they were input. Top Rearrange line(s) as necessary. If there are any blank lines, move them to the

bottom, and move the data to the top.

Line1 Line2 Line3 Line4 Line5 Line6

Bottom Rearrange line(s) as necessary. If there are any blank lines, move them to the

top, and move the data to the bottom.

Line1 Line2 Line3 Line4 Line5 Line6

Before

Bob Smith 2100 Market Street Suite 202 Sycamore Building Boston, MA 02109

Before

Bob Smith 100 Market Street Suite 202 Sycamore Building Boston, MA 02109

After

Bob Smith Sycamore Building

100 Market St Ste 202 Boston MA 02109

After

Bob Smith Sycamore Building 100 Market St Ste 202 Boston MA 02109

Chapter 2: Standardization and style options

Details You must standardize unassigned addresses to swap unassigned-address lines.

You may use line swapping with or without using the Combine Lines feature. ACE will perform line swapping only when the input multiline fields (Line1,

Line2, and so on.) are the same length. If even one of these fields is sho r ter or longer than the others, ACE reports an error. You either have to change your field lengths or turn off line swapping.

If the record contains two address lines, ACE will place the assigned address line just above the last line. It will pl ace th e dual address (see

“Dual address lines” on

page 40) above the assigned address.

ACE Views and ACE Job

ACE Library By default, line swapping is turned off. To turn it on, call ace_set_option().

By default, line swapping is turned on. T o set your preference, go to the Multiline Style block and set the Swap Address Lines parameter.

ACE User’s Guide

Combine related components onto the same line

ACE can rearrange some components within multiline addresses. This feature,

Multiline Combine Lines, results in a more compact address that is easier

called to read. For

Line1 Bob Smith Bob Smith Line2 100 Market Street Line3 Apt 202 100 Market St Apt 202 Line4 Boston MA Boston MA 02109 Line5 02109

Your options If your address data is in a multiline format, then you have four o ptions to choose

from. If you are processing a two-line format (examples below), then only the first two of those options pertain to you.

Option Description

None Don’t combine at all. Address line Combine address line components. If there is enough room, place the

example:

Original data: Combined lines:

secondary address on the same line as the primary. Do not combine the last-line data.

ACE handles the blank line if you turn on the Swap Lines feature.

Last line Combine the city, state, and ZIP Code onto one line. Do not combine

the address line.

Both Combine as much as possible: Address-line components onto one

line, and last-line components on another line.

The other options (Last line and Both) do not apply to you if your records look like either of these:

Two-line format: Two-line format:

Name Bob Smith Name Bo b Smith

Line1 100 Market Street Line1 100 Market Street Line2 Apt 202 Line2 Apt 202

City Boston Last_Line Boston MA 02109 State MA ZIP 02109

Chapter 2: Standardization and style options

Details You do not have to standardize your address data to use Combi ne Lines. You may

use Combine Lines with or without using the Swap Lines feature. When combining the last line, ACE usually moves the state and ZIP Code to be

on the same line as the city name.

Acceptable input: Bad input:

Line1 Bob Smith Bob Smith Line2 100 Market Street 100 Market Street Line3 Apt 202 Apt 202 Line4 Boston MA Boston Line5 02109 MA Line6 02109

ACE Views and ACE Job

By default, ACE combines as much as possible. To set your preference, go to the Multiline Style block and set these two parameters: Combine Address Line Info and Combine Last Line Info.

ACE Library By default, ACE combines as much as possible. To set your preference, call

ace_set_option().

ACE User’s Guide

Updating the ZIP and ZIP+4 in a multiline address

When you are processing multiline addresses, it’s difficult—if not impossible—to update the ZIP and ZIP+4 codes yourself. This is because you can’t be sure

these codes will appear (below). So you can’t give ACE specific

where instructions about exactly where to place the updated ZIP and ZIP+4. Instead, you tell ACE whether you Assignment features. in each address, so it can

Possible locations of ZIP Code

Line1

John Smith

Line2

Acme Tools

Line3

Suite 152

Line4

308 2nd Ave

Line5

Your options You have two separate options because we think ACE should be a little more

Ames IA

conservative with ZIP Codes.

Option Description

want the ZIP and ZIP+4 updated, by setting the Multiline Internally, ACE “knows” where the ZIP and ZIP+4 appear

update them for you.

50014

Acme Tools ATTN J. Smith 308 2nd Ave #152 Ames IA

50014

J. Smith, Acme Tools 308 2nd Ave, #152 Ames IA

50014

Include/Update ZIP Code

Include/Update ZIP+4?

Postal discount The USPS requires that the ZIP and ZIP+4 numbers in the address block match

ACE will place the assigned ZIP Code inside your multiline address block. If ACE cannot assign a ZIP Code, it will keep the ZIP Code that was in the input record (if there was one).

If you turn off this option, ACE will not touch the ZIP Code inside the multiline block. The assigned ZIP Code will still be available as a sep arate component.

ACE will place the assigned ZIP+4 inside your multiline address block. If ACE cannot assign a ZIP+4, you have the option either to keep the input, unverified ZIP+4 (if there was one), or suppress the input ZIP+4. A bad ZIP+4 can result in mail being delivered to the wrong address.

If you turn off this option, ACE will not touch any ZIP+4 in the multiline address block. The assigned ZIP+4 is still available as a separate component.

the Postnet barcode. This means that if you do not allow ACE to update the ZIP and ZIP+4 inside the

address block, you give up your barcoding discount.

Chapter 2: Standardization and style options

ACE Views and ACE Job

By default, ACE updates the ZIP and adds the ZIP+4 to multiline addresses. To set your preference, go to the Multiline S tyle blo ck and set th ese two para meters: Include ZIP and Include ZIP+4.

When ACE cannot assign a ZIP, it passes along the original ZIP. We figure that an unverified ZIP is better than no ZIP at all. However, we take a different view of the ZIP+4 code. When ACE cannot assign a ZIP+4, then by default, ACE suppresses any ZIP+4 that may have appeared in the input data.

You do have the option to retain the original ZIP+4 when AC E cannot assign one. Refer to the Unverified Postal Code parameter in the Input File block.

ACE Library By default, ACE updates the ZIP and adds the ZIP+4 to multiline addresses.

Also by default, ACE suppresses any ZIP+4 code in the original data. If ACE can’t assign a ZIP+4 code, then the resulting multiline address will not contain any ZIP+4 code at all. To set your preference, call ace_set_option().

ACE User’s Guide

Chapter 3: Reports

This chapter explains reports and statistics files that you can request from ACE. These reports and statistics files contain information about your ACE jobs and your processed data.

ACE V iews and ACE Job of fer all of the re ports shown in this chapter. PrintForm ACE offers only the Job Summary Report.

If you use ACE Library, these reports are not available. But you might evaluate these reports and use them as a model for your own reports. However, you can produce the ACS statistics file with ACE Library. See Statistics (ACS) file” on page 78 for details.

“Address Conversion

Chapter 3: Reports

Executive Summary

ACE Views and ACE Job offer an Executive Summary Report. This is a concise statement of the most crucial information about your ACE job. We’ve designed it to meet the information needs of managers and clients.

Usually, the Executive Summary will be a single page. If you produce more than five output files, the report might extend to a second page.

Executive Summary Page 1

-----------------------------------------------------------------------------Job Description (Title) Input File -----------------------------------------------------------------Input File Name: C:\PW\ACE\SAMPLES\DOGS.DAT Total Input Records : 442 Less Records Dropped by Delete Mark : 0 Less Records Dropped by Input Filter : 2 Less Records up-to-date per Z4 Change : 0 Net Input Records to be Processed : 440 Statistics ----------------------------------------------------------------- Address Types Records %

------------------------------------------ -------- -----Street 346 78.64 PO Box 29 6.59 Rural Route 20 4.55 Military 0 0.00 Assigned, No Delivery 1 0.23 Other Assigned Address Types 28 6.36 Foreign 0 0.00 Other Unassigned Address Types 16 3.64

-------- -----Total 440 100.00

Addresses That Require LACS Conversion: 0

Input File After Processing -------------------------------------------------

Postal Code Assignment:

No information available, the input file was not updated in this job. Output File(s) -----------------------------------------------------------File Name and Location Records Postal Codes Assignment Percentages Output ZIP ZIP4 DPBC CART

------------------------- -------- -------- -------- -------- -------C:\PW\ACE\SAMPLES\output1.TXT 423 100.00 100.00 100.00 100.00 C:\PW\ACE\SAMPLES\output2.TXT 17 70.59 0.00 0.00 5.88

Job Description Just below the report header, ACE prints the Job Description that you entered in

the General block of your job file.

Total Input Records This is always the total number of records in the input file. The Starting and

Ending Record parameters are not reflected.

Less Records Dropped by Delete Mark

Less Records Dropped by Input Filter

This is zero unless you set Process Deleted Records to No. Then this number reflects those records that were ignored because they were marked for deletion.

This is the number of records that were excluded because you used any of the following features: Input Filter, Starting Record Number, Ending Record Number, or Assign Which Records = Unassigned. Also counted are any records that were not processed because you interrupted the job.

Less Records up-to-date per Z4 Change

ACE User’s Guide

This shows the number of records that Z4 Change detected as not needing to be updated. If you do not have the Z4 Change option, this numb er will be zero.

Net Input Records to be Processed

Address Types If you sum up the numbers on the first six lines (Street through Other Assigned

This is the number of records that ACE tried to assign.

Address Types), you get the total number of successful assignments (9-digit matches). Note that this includes undeliverable records (see error code E600) which are bad for mailing, but successful assignments.

If you sum up the numbers on the next two lines (Foreign and Other Unassigned Address Types), you get the total number of assignment failures (records on which a 9-digit match was not achieved).

The percentages shown in this section are based on the number of Net Input Records to be Pr ocessed. They are not based on the number of records in the input file.

Addresses That Require LACS Conversion

Input File After Processing If you choose not to update the input file, this section will say so. If you do

ACE will count addresses that requi re LA CS con ve rsi on wh ether or not you post the LACS flag (

AP.LACSCODE) to your database.

update, this section contains the percentage of records that were assigned ZIP, ZIP+4, DPBC, and CART. Note that the percentages reflect your posting. If you do not post a particular code, the percentage will be zero.

Output Files The percentages shown in this section are based on the number of Records

Output. They are not based on the number of records in the input file, nor on the

number of records that ACE processed. Note that the percentages reflect your posting. If you do not post a particular code, the percentage will be zero.

Chapter 3: Reports

Job Summary Report, page 1 (setup information)

We recommend that you produce a Job Summary from every ACE job. It is a concise statement of your job setup, input data, and re sults. The report consists of three sections; each one starts on a new page

Job Summary ACE (version no.) Page 1

-------------------------------------------------------------------------------

Setup Information -------------------------------------------------------------

Job Name quikwin.ace Job Description QUICK START JOB Job Owner SAMPLE JOB

Starting Record Number 1 Ending Record Number 445

Assign Which Records: All Assignment Mode: Assign Enable Non-CASS: N Geo Mode: N/A Enable EWS: Y Enable eLOT: Y Enable DPV: Y Enable RDI: Y Enable LACSLink: Y Enable SuiteLink: N DSF2 Mode: None

Address Line Alias: Preserve Dual Address Assignment: Position Address Line Standard: Strict Unit Standardization: Directory Suffix Style: Short Directional Style: Short Append PMB To Address: Yes Std Unassigned Address: No

Asgn City By Inp/LLIdx: Yes Unverified Postal Codes: Erase Non-Mailing City Names: Convert Case Standardization: Upper PW Fld Standardization: n/a

Multiline Standard: n/a Swap Address Lines: n/a Preserve Dual Order: n/a Combine Address Line: n/a Combine Last Line: n/a Include ZIP: n/a Include ZIP+4: n/a

Accept Input ZIP+4: n/a Inexact ZIP Forwarding: n/a ZIP4 non-DPV Confirmed: n/a

Auxiliary Files ---------------------------------------------------------------

File Description Date File Name

------------------------- ---------- ----------------------------------------Firm Line Dictionary 01/2007 E:\working\780c\firmln.dct Address Line Dictionary 01/2007 E:\working\780c\addrln.dct Last Line Dictionary 01/2007 E:\working\780c\lastln.dct Capitalization Dictionary 01/2007 E:\working\780c\pwcas.dct ZCF Directory 01/2007 ..._data\rel_dir\us_comm2006\jan\zcf09.dir City Directory 01/2007 ...data\rel_dir\us_comm2006\jan\city09.dir ZIP+4 Directory 1 01/2007 ...data\rel_dir\us_comm2006\jan\zip4us.dir ZIP+4 Directory 2 Reverse ZIP+4 Directory 01/2007 ...ata\rel_dir\us_comm2006\jan\revzip4.dir Reverse Soundex Directory 01/2007 ...r_data\rel_dir\drs9.xx\Jan07\zip4us.rev ZIP4 SHS Directory 01/2007 ...r_data\rel_dir\drs9.xx\Jan07\zip4us.shs EWS Directory 01/25/2007 ...ra-d1\dir_data\rel_dir\ews\ew070125.dir eLOT Directory 01/2007 ...r_data\rel_dir\us_comm2006\jan\elot.dir DPV Directory 01/2007 E:\dirs\dpv RDI Directory LACSLink Directory 01/15/2007 E:\dirs\lacslink SuiteLink Directory Z4 Change Directory NCOALink Directory Name Parsing Files Centroid Geo Dir

Throughput Summary ------------------------------------------------------

ZIP Sort Start Time: ZIP Sort End Time: Records Sorted Per Hour:

Batch Start Time: 06/03/2004 16:09:12 PM CDT Batch End Time: 06/03/2004 16:09:42 PM CDT Records Assigned Per Hour: 123960

Total Records Processed Per Hour: 119961 Total Processing Time: 00:00:31

ACE User’s Guide

PW Fld Standardization This indicates whether or not you chose to update the inpu t file. If you did not

update, this will be marked “n/a” (not applicable).

Multiline Standard If your input addresses were in a multiline format (using the PW fields Line1,

Line2, and so on.), these lines will show the choices that you made in the Multiline Style block. If your input records were not multiline, these lines will be marked “n/a.”

Auxiliary Files For the dictionary files, ACE reports the date according to the file’s date stamp

(the date as figured by the operating system). For directories, ACE gets the date from inside the file. This is the date that the directory was made at Business Objects, not the date stamp.

Total Processing Time ACE combines the time of the ZIP-sort and assignment processes. It does not

include the time taken to generate or print reports. The Total Processing Time is not equal to the elapsed time of the job. A brief

period—usually a few seconds—of uncounted time occurs between the end of the ZIP-Sort process and the start of the batch process.

Chapter 3: Reports

Job Summary Report, page 2 (summary of results)

The second page of the Job Summary provides more details on your input records

how they fared in the assignment process. At the bottom, this page merely

and touches on how your records were output. More details on that appear on page 3.

Job Summary ACE [version] Page 2

-------------------------------------------------------------------------

Input File --------------------------------------------------------------

Filter: n/a Records Net File Database Deleted Filtered Skipped Input Name Date Type Records Records Records by Z4C Records

---- ------------------- ------ -------- -------- -------- -------- ------ smk_asgn.dbf 08-28-2003 13:15:34 DBASE3 1033 0 0 0 1033

Address Type Summary Assignment Summary Count % Count %

-------------------------------- ------------------------------------ Street 112 22.13 ZIP Codes 978 94.68 PO Box 13 2.57 ZIP+4 Codes 506 48.98 High Rise 195 38.54 DPB Codes 506 48.98 Rural Route 119 23.52 Carrier Route Codes 524 50.73 Firm 25 4.94 LOT Codes 506 48.98 General Delivery 10 1.98 LOT Order Codes 506 48.98 Military 13 2.57 County Codes 978 94.68 Unique 19 3.75 Assigned/No Delivery 10 0.97 Foreigns 2 0.19 Others Not Assigned 515 49.85 LACS Convertible 38 3.68 Addr Level Geo Codes 0 0.00 Centroid Geo Codes 0 0.00 RDI Matches 401 38.82 Mover ID Matches 0 0.00

------------------------------- Total ZIP+4 Codes: 506 100.00

CASS Qualitative Statistical Summary (QSS) (Percentages based on # of records passing the filter) Count % Count %

---------------------------------- -------------------------------- High Rise Default 147 14.23 Rural Route Default 81 7.84 High Rise Exact 48 4.65 Rural Route Exact 38 3.68 EWS Match 120 11.62 LACS Convertible 38 3.68 DPV Confirmed 175 16.94 RDI 401 38.82 LACSLink Conversions 0 0.00

Delivery Point Validation Summary (DPV) (Percentages based on # of records passing the filter) Confirmed Not Confirmed Count % Count %

---------------------------------- -------------------------------- Confirmed 168 16.26 Primary Not Confirmed 695 67.28 CMRA Confirmed 7 0.68 Secondary Not Confirmed 53 5.13 Secondary Missing 110 10.65

---------------------------------- -------------------------------- Total Confirmed: 175 16.94 Total Not Confirmed: 858 83.06

Delivery Point Validation (DPV) Tie-breaking Summary (Percentages based on # of records passing the filter) Count %

------------------------------------ Ties Resolved by DPV 5 0.48

PW Fields ----------------------------------------------------- PW Fields = Database Fields name_line = name firm = firm urb = urb line1 = addr_1 line2 = addr_2 last_line = last_line

ACE User’s Guide

Database Records This shows the total number of records in the input file. The Starting and Ending

Record parameters are not reflected.

Deleted Records This shows zero unless, in the Input File block, you have set Process Deleted

Records = No. Then this number will reflect those records that were ignored because they were marked for deletion.

Filtered Records This shows the number of records that were excluded because you used any of the

following features: Input Filter, Starting Record Number, Ending Record Number, or Assign Which Records = Unassigned. Also counted are any records that were not processed because you interrupted the job.

Records Skipped by Z4C This shows the number of records that Z4 Change detected as not needing to be

updated. If you do not have the Z4 Change Option, this number will be zero.

Net Input Records This shows the number of records that ACE tried to assign.

Address Type Summary This shows a breakdown of the processed records into address categories. This

summary does not describe any particular output file. Nor does it consider what you may or may not have actually posted to your input file. For a tally of address types based on the data actually posted, see page 3 of the report.

Assignment Summary This section is based on the codes that ACE was able to assign. It does no t reflect

what you may or may not have actually posted to your in put file. For a tally of postal codes based on the data actually posted, see page 3 of the report.

Total ZIP+4 Codes The number is based only on net input records that were fully assigned. Records

that were skipped, ignored, or unassigned will not be included in this count. If you append records to the end of an existing database, these numbers will

reflect only the records appended. They will no t equal the to tal number of re cords in the database. See the Ex isting File parameter in the Post to Output File block.

Qualitative Statistical Summary (QSS)

The USPS requires this information on PS Form 3553. Information in the QSS section of the Job Summary corresponds to the QSS section of PS Form 3553. This section shows the number and percentage of matches in a number of categories.

Delivery Point Validation Summary (DPV)

This section lists the number and percentage of addresses that are confirmed and not confirmed. The percentages are based on the number of records passing the filter.

Delivery Point Validation (DPV) Tie-Breaking Summary

This section lists the number and percentage of address ties that were resolved by DPV. The percentages are based on the number of records passing the fi lter.

Chapter 3: Reports

Job Summary Report, page 3 (one page per database)

Page 3 gives statistics for one particular input or output file. Your report may include more than one such page.

Job Summary Page 3

----------------------------------------------------------------------------Postal Code Summary Per File --------------------------------------------------File Name: C:\PW\ACE\SAMPLES\GOOD_DOG.TXT Filter: ap.match_9 = "T" .and. ap.match_un = "F" Records Passed by Filter: 423

Postal Assigned Corrected Corrected Codes Count % Count % Components Count %

------ --------------- --------------- --------------- --------------ZIP 423 100.00 0 0.00 City 2 0.47 ZIP+4 423 100.00 423 100.00 State 0 0.00 DPBC 423 100.00 0 0.00 Trunc Addresses 0 0.00 CART 423 100.00 423 100.00 Trunc Cities 0 0.00 County n/a n/a n/a n/a

Address Type Summary

----------------------------------------------------------------------------Street 346 81.80 Firm 2 0.47 PO Box 29 6.86 General Delivery 0 0.00 High Rise 26 6.15 Military 0 0.00 Rural Route 20 4.73 Unique 0 0.00

Error Code Summary ---------------------------------------------------------Error Description Count %

----- --------------------------------------------------- -------- -----E101 Last line is bad or missing 0 0.00 E212 No city and bad ZIP 0 0.00 E213 Bad city and no ZIP 0 0.00 E214 Bad city and bad ZIP 0 0.00 E216 Bad ZIP, can't determine which city match to select 0 0.00 E302 No primary address line parsed 0 0.00 E412 Street name not found in directory 0 0.00 E413 Possible street name matches too close to choose 0 0.00 E420 Primary range is missing 0 0.00 E421 Primary range is invalid for street/route/building 0 0.00 E422 Predirectional needed, input is wrong or missing 0 0.00 E423 Suffix needed, input is wrong or missing 0 0.00 E425 Suffix & directional needed, input wrong or missing 0 0.00 E427 Postdirectional needed, input is wrong or missing 0 0.00 E428 Bad ZIP, can’t select an address match 0 0.00 E429 Bad city, can’t select an address match 0 0.00 E430 Possible addr. line matches too close to choose one 0 0.00 E431 Urbanization needed, input is wrong or missing 0 0.00 E500 Other error 0 0.00 E501 Foreign address 0 0.00 E502 Input record entirely blank 0 0.00 E503 ZIP not in area covered by partial ZIP+4 directory 0 0.00 E504 Overlapping ranges in ZIP+4 directory 0 0.00 E600 Marked by USPS as unsuitable for delivery of mail 0 0.00

-------- -----Total Error Codes: 0 0.00

Address Type After LACSLink Pre- High- Rural General LACSLink Street PO Box Rise Route Firm Delivery Unique Total

-------- ------- ------- ------- ------- ------- -------- ------- -------Street 52 0 8 0 0 0 0 60 PO Box 0 12 0 0 0 0 0 12 Highrise 7 0 7 0 0 0 0 14 Rural Rt 30 0 0 0 0 0 0 30 Firm 0 0 0 0 0 0 0 0 Gen. Del 0 0 0 0 0 0 0 0 Unique 0 0 0 0 0 0 0 0

-------- ------- ------- ------- ------- ------- -------- ------- -------Total: 89 12 15 0 0 0 0 116

(Percentages based on # of records passing the filter) Converted Not Converted Count % Count %

------------------------------------ ------------------------------------Converted (A) 63 69.23 No Match (00) 25 27.47 Secondary Dropped (92) 0 0.00 Can't Convert (14) 2 2.20

------------------------------------ ------------------------------------Total Converted: 63 69.23 Total Not Converted: 27 29.67

Locatable Address Conversion Summary (LACSLink)

ACE User’s Guide

Postal Code Summary Per File

This page gives statistics for one particular input or output file. Your report may include more than one such page. You can control whether ACE reports on how it updated the input file, each out put file, or both . The para meter is called Repo rt on Files, and it is located in the Report: Job Summary block.

If you do not update your input file (ei ther auto matic all y or manu ally), t hen A CE will automatically suppress the page about the input file, no matter how the Report on Files parameter was set.

Records Passed By Filter When the page describes an output file, this secti on will reflect the act ual number

of records written or appended to the output file. When the page pertains to input file, this section shows th e number of records that

were put through the assignment process. Remember that this number wi ll be affected by your use of any of the following features: Input Filter, Starting

Record Number , Ending Recor d Numb er , Assign Which Records = Unassigned, or Process Deleted Records =No.

Postal Codes Assigned The numbers in this section reflect what was actually p osted. If you choose no t to

post a code, ACE will print “n/a” on that line.

Postal Codes Corrected In this section, a code is counted as corrected if it was wrong in the input record,

or did not appear in the input at all.

Trunc “Trunc” is short for “Truncated.” These numbers reflect address lines and city

names that were too long to fit into the database field, even after ACE tried to abbreviate.

Address Type Summary This section is based only on records that were fully assigned. Records that were

unassigned will not be included in these counts. This sample report is based on a job in which we created two output files. The

page shown here reflects an output file that w as limi ted to assign ed records. Page 4 of our report (not shown) indicated that 17 unassigned records were written to the other output file.

Address Type After

Link

LACS

Locatable Address Conversion Summary

The Address Type After LACS

Link

through LACS

, and the address type before and after LACS

Military records are not shown, as LACS

The Locatable Address Conversion Summary table lists the count and percentages of records that were converted and the number and percentages of addresses that were not converted through LACS

Link

table lists the number of addresses converted

Link

does not include military records.

Link

processing.

Chapter 3: Reports

Standardization Report (a listing of input and processed data)

The Standardization Report has a horizontal format. Each record listed requires just three lines: one for the original data, one for the standardized data, and a blank line to easy to compare the “before” and “after” versions of each record.

Standardization Report Page 1

----------------------------------------------------------------------------------------------------Reporting on: C:\PW\ACE\SAMPLES\DOGS.DAT

In Code Address City St Zip

7 S884 1720 WINEBAGO ST LA CROSSE WI 54601 1720 Winnebago Street La Crosse WI 54601

10 SA04 2621 29TH ST S LA CROSS WI 54601 2621 29th Street South La Crosse WI 54601

-----------------------------------------------------------------------------------------------------

Changed Component List : PRIM_NAME, CITY, STATE, ZIP Start Report at Record # : 1 Max # of Records to Print : 442 Nth Select : 1.00 Report Type : Custom

1st Digit 2nd Digit 3rd Digit 4th Digit

-------------------------- ----------------------------- ------------------------------- --------------------S Status 0 No Change 0 No Change 0 No Change A Address Truncation 1 ZIP 1 Suffix 1 Unit C City Truncation 2 City 2 Predir 2 DPBC B Address/City Truncation 3 City ZIP 3 Predir Suffix 3 DPBC Unit 4 State 4 Postdir 4 CART 5 State ZIP 5 Suffix Postdir 5 CART Unit 6 City State 6 Predir Postdir 6 CART DPBC 7 City State ZIP 7 Predir Postdir Suffix 7 CART DPBC Unit 8 ZIP4 8 Pname 8 County 9 ZIP4 ZIP 9 Pname Suffix 9 County Unit A ZIP4 City A Predir Pname A County

separate it from the next record. This format makes it

Limiting the scope and size of your report

You may instruct ACE to report every standardized address but, if you do, the report file will probably be far too large and take too much time. There are two ways to limit the scope of the report:

 You can select by address component. For example, if you select city, then

ACE will include in the report only those reco rds in wh ich the city n ame was changed. This is handy because you can focus the report on critical address components and ignore minor changes.

 You can limit the report to a certain number of records, or perform “every

nth” sampling.

To save space, our sample shows just two records plus the legend.

Reporting On The Standardization Report is always based on the input file. ACE accepts one

input file so it always prepares one Standardization Report, no matter how many output files you might create.

ACE User’s Guide

In, Code, Address, City St, and ZIP

Notice that we included the input record number and the status code. Each record in the report occupies three lines (two data, one blank). The first line is the raw data as it was input. The second line is the standardized data that ACE produced. Please note, ACE is showing you what could be done to the address if you output standardized data. If you choose not to post standardized data, then this report will not match your output file (or your updated input file).

Report Type This sample was prepared using the Custom formatting option. We chose the

fields, set the width of each column, and selected the title over each column.

Legend (1st Digit through 4th Digit)

The legend contains your report parameters and a table that makes it easier to interpret status codes. When you print this report, ACE will start a separate page for the legend.

4th Digit “Unit” means the unit designator (Apt, Ste, Rm, Flr, #), not the unit number.

Chapter 3: Reports

Error Report (a listing of unassigned records)

The Error Report shows which records were assigned error codes during processing. ACE uses these error codes to indicate why it was unable to match the address in the USPS directories. By reading these codes, you might be able to correct the data in specific records or find a pattern of incorrect data entry.

Whereas the Job Summary Report tallies how often error codes occur, the Error Report goes one step further and lists the actual addresses that were assigned those codes.

Error Report Page 1

-----------------------------------------------------------------------------Reporting on: All

In Out Code Address City St Zip

1 1 E702 N2000 Orchard Valley Dr 2 2 E421 29 Farnam St La Crosse WI 54601 3 3 E600 1501 La Crosse St La Crosse WI 54601 4 4 E421 2600 Timber Ln La Crosse WI 54601 5 5 E427 501 15th St La Crosse WI 54601 9 6 E421 1060 Cedar Rd La Crosse WI 54601 14 7 E412 618 Cliff Ln La Crosse WI 54601 125 8 E411 1911 Ankomis Ave La Crosse WI 54603 160 9 E421 0357 Edgewater Ln La Crosse WI 54603 182 10 E421 113 N 4th St Galesville WI 54630 200 11 E421 718 W Clark Ave Galesville WI 54630 328 12 E421 113 Kneeland Ave Galesville WI 54630 338 13 E412 664 Parklawn Estates St Onalaska WI 54650

--------------------------------------------------------------------------Error Code List : ALL

----------------------Portions omitted for illustration----------------------------------

Error Description Error Description

----- --------------------------------------------------- ----- ------------------------------------------

E428 Bad ZIP, can't select an address match E429 Bad city, can't select an address match E430 Possible addr. line matches too close to choose one E431 Urbanization needed, input is wrong or

E439 Address found in Early Warning System directory E500 Other Error E501 Foreign Address E502 Input record entirely blank E503 ZIP not in area covered by partial ZIP+4 directory E504 Overlapping ranges in ZIP+4 directory E505 Matched to undeliverable default record E600 Marked by USPS as unsuitable for delivery

E601 Primary number does not DPV confirm, ZIP+4 removed

missing

of mail

Limiting the scope and size of your report

ACE User’s Guide

You may instruct ACE to report every unassigned address but, if you do, the report file may be too large. For example, if you had one million records and five percent were reported unassigned, at one line each, ACE would produce a report with 50,000 lines! Think about this before you set the parameters for the Error Report. There are two ways to limit the size and scope of the report:

 You can limit the report to a certain number of records, or perform “every

nth” sampling.

 You can select by error code. For example, if you select code E411, then

ACE will include in the report only those records that were assigned E411. This is handy because you can focus the report on certain types of errors, an d ignore other errors.

You can create more than one file to select by error code. So, if you selected one file for error code E411 but wanted to keep E704 errors separate, repeat the block, but change the code and the report file name.

The sample report T o save space in this document, our sample shows just 13 records plus the legend.

The legend contains your report parameters and a table that makes it easier to interpret error codes.

When you print this report, ACE will start a separate page for the legend. The page size of this manual doesn’t permit us to show you the full width of this

report, which is at least 132 characters. Be assured that when you print your report (using landscape mode, condensed print, wide paper, and so on.), you should see the full report.

Reporting on ACE can produce separate Error Reports for the input file, the outpu t file(s), or all

input and output files. You can control this through the Report on File parameter.

Report Type The sample was prepared using the Custom formatting option. We chose the

fields, set the width of each column, and selected the title over each column.

In, Out, Code, Address, City, St, and ZIP

We included the input record number, the output record number, and the error code.

Chapter 3: Reports

Statistics files for custom reporting

With ACE, you can create statistics files, which contain much of the same information as the ACE Job Summary Report and the Customer Service Log (for Mover ID NCOA without special formatting. This such as spreadsheets, report writers, or accounting systems.

You can use statistics files to create custom reports, either about one job or, by accumulating, about several jobs.

With ACE, you can create the following statistics files:

 Job (see “Job statistics file” on page 65)  File (see “File statistics file” on page 70)  ACS (see “Address Conversion Statistics (ACS) file” on page 78)

The Job and File statistics files are available with ACE Views and Job only, not with ACE Library.

Link

users). However, statistics files contain only the numbers,

makes them easier to import into other programs,

You can produce the ACS statistics file with ACE Library, Views, or Job, only if you own the Mover ID for NCOA

Link

, DSF2, and Suite

Link

add-on

options.

ACE User’s Guide

Job statistics file

T o produce the Job statistics file, you must also produce the Job Summary Report. You can produce the Job statistics file with ACE Views or Job, not with ACE Library.

The Job statistics file contains much of the same information that appears on pages 1 and 2 of the Job Summary Report. It consists of a single record with the following fields.

Field Length Description

firmln 7 Date of firm line dictionary ( addrln 7 Date of address line dictionary ( lastln 7 Date of last line dictionary ( cap 7 Date of capitalization dictionary ( zcf 7 Date of ZCF directory ( city 7 Date of City directory ( zip1 7 Date of ZIP+4 directory ( zip2 7 Date of other ZIP+4 directory. revzip4 7 Date of Reverse ZIP+4 directory ( zip4us 7 Date of the reverse soundex directory ( zip4us 7 Date of the SHS directory ( z4change 7 Date of z4change directory. CGeo 7 Date of Centroid-level GeoCensus directory. AGeo 7 Date of Address-level GeoCensus directories. zips_start 26 ZIP sort start time. zips_end 26 ZIP sort end time.

firmln.dct

lastln.dct

zcfxx.dir

cityxx.dir

zip4us.dir

zip4us.shs

addrln.dct

pwcas.dct

)

revzip4.dir

zip4us.rev)

)

bth_start 26 Batch start time. bth_end 26 Batch end time. tpt 8 Total processing time. db_recs 10 Database records. del_recs 10 Deleted records. filt_recs 10 Filtered records. z4c_recs 10 Records skipped by Z4change. inp_recs 10 Net input records. street_at 10 Number of records with a street address type. street_p 6 Percentage of records with a street address type. po_at 10 Number of records with a post office box address type. po_p 6 Percentage of records with a post office box address type.

Chapter 3: Reports

Field Length Description

hr_at 10 Number of records with a highrise address type. hr_p 6 Percentage of records with a highrise address type. rr_at 10 Number of records with a rural route address type. rr_p 6 Percentage of records with a rural route address type. f_at 10 Number of records with a firm address type. f_p 6 Percentage of records with a firm address type. gd_at 10 Number of records with a general delivery address type. gd_p 6 Percentage of records with a general delivery address

type. m_at 10 Number of records with a military address type. m_p 6 Percentage of records with a military address type. u_at 10 Number of records with a unique address type. u_p 6 Percentage of records with a unique address type. zip_cnt 10 Number of records assigned a ZIP Code. zip_p 6 Percentage of records assigned a ZIP Code. zip4_cnt 10 Number of records assigned a ZIP+4. zip4_p 6 Percentage of records assigned a ZIP+4. dpb_cnt 10 Number of records assigned delivery point barcode. dpb_p 6 Percentage of records assigned delivery point barcode. cart_cnt 10 Number of records assigned carrier route codes. cart_p 6 Percentage of records assigned carrier route codes. lot_cnt 10 Number of records assigned Line-of-Travel (LOT) codes lot_p 6 Percentage of records assigned LOT codes. loto_cnt 10 Number of records assigned LOT Order codes. loto_p 6 Percentage of records assigned LOT Order codes. cnty_cnt 10 Number of records assigned county codes. cnty_p 6 Percentage of records assigned county codes. undel_cnt 10 Number of records that are not deliverable addresses.

(These records receive error code E600.) undel_p 6 Percentage of records that are not deliverable addresses.

(These records receive error code E600.) for_cnt 10 Number of foreign addresses.

for_p 6 Percentage of foreign addresses. na_cnt 10 Number of records not assigned, not including foreign

records.

ACE User’s Guide

Field Length Description

na_p 6 Percentage of records not assigned, not including foreign

records. lacs_cnt 10 Number of records that are LACS convertible. lacs_p 6 Percentage of records that are LACS convertible. lacsl_cnv 10 Number of LACS lacsl_c_p 6 Percentage of records converted through LACS

Link

conversions.

Link

ageo_cnt 10 Number of records assigned address-level GeoCensus

codes. ageo_p 6 Percentage of records assigned address-level GeoCensus

codes. cgeo_cnt 10 Number of records assigned Centroid-level GeoCensus

codes. cgeo_p 6 Percentage of records assigned Centroid-level GeoCen-

sus codes. mid_cnt 10 Number of Mover ID matches. mid_p 6 Percentage of Mover ID matches. qss_hr_at 10 Number of highrise exact matches.

This statistic corresponds to USPS-required information

in the Qualitative Statistical Summary (QSS) section of

PS Form 3553. qss_hr_p 6 Percentage of highrise exact matches.

This statistic corresponds to USPS-required information

in the QSS section of PS Form 3553. qss_hrd_at 10 Number of highrise default matches.

This statistic corresponds to USPS-required information

in the QSS section of PS Form 3553. qss_hrd_p 6 Percentage of highrise default matches.

This statistic corresponds to USPS-required information

in the QSS section of PS Form 3553. qss_rr_at 10 Number of rural route exact matches.

This statistic corresponds to USPS-required information

in the QSS section of PS Form 3553. qss_rr_p 6 Percentage of rural route exact matches.QSS qss_rrd_at 10 Number of rural route default matches.

This statistic corresponds to USPS-required information

in the QSS section of PS Form 3553. qss_rrd_p 6 Percentage of rural route default matches.

This statistic corresponds to USPS-required information

in the QSS section of PS Form 3553. qss_lacs_at 10 Number of LACS convertible addresses.

This statistic corresponds to USPS-required information

in the QSS section of PS Form 3553.

Chapter 3: Reports

Field Length Description

qss_lacs_p 6 Percentage of LACS convertible addresses.

This statistic corresponds to USPS-required information in the QSS section of PS Form 3553.

ews_match_at 10 Number of Early W arning System (EWS) matches.

This statistic corresponds to USPS-required information in the QSS section of PS Form 3553.

ews_match_p 6 Percentage of EWS matches.

This statistic corresponds to USPS-required information in the QSS section of PS Form 3553.

dpv_str_cnt 10 Number of records that were Delivery Point Validation

(DPV) confirmed. dpv_str_p 6 Percentage of records that were DPV confirmed. dpv_cmra_cnt 10 Number of records that were DPV confirmed as a Com-

mercial Mail Receiving Agency (CMRA). dpv_cmra_p 6 Percentage of records that were DPV confirmed as a

CMRA. dpv_prim_no_cnt 10 Number of records that could not be confirmed during

DPV processing because the primary range could not be

confirmed. dpv_prim_no_p 6 Percentage of records that could not be confirmed during

DPV processing because the primary range could not be

confirmed. dpv_sec_no_cnt 10 Number of records that could not be confirmed during

DPV processing because the secondary range could not

be confirmed. dpv_sec_no_p 6 Percentage of records that could not be confirmed during

DPV processing because the secondary range could not

be confirmed. dpv_sec_miss_cnt 10 Number of records that could not be confirmed during

DPV processing because the secondary range was miss-

ing. dpv_sec_miss_p 6 Percentage of records that could not be confirmed during

DPV processing because the secondary range was miss-

ing. dpv_ties_cnt 10 Number of ties resolved through DPV processing. rdi_cnt 10 Number of Residential Delivery Indicator (RDI)

matches. rdi_p 6 Percentage of RDI matches. ste_match 10 Number of Suite ste_p 6 Percentage of Suite dsf_drop 10 Number of DSF dsf_drop_p 6 Percentage of DSF dsf_business 10 Number of DSF

Link

matches.

Link

matches.

drop matches.

business matches.

ACE User’s Guide

Field Length Description

dsf_business_p 6 Percentage of DSF2 business matches. dsf_throwback 10 Number of DSF dsf_throwback_p 6 Percentage of DSF dsf_seasonal 10 Number of DSF dsf_seasonal_p 6 Percentage of DSF dsf_educational 10 Number of DSF dsf_educational_p 6 Percentage of DSF dsf_vacant 10 Number of DSF dsf_vacant_p 6 Percentage of DSF dsf_lacs 10 Number of DSF dsf_lacs_p 6 Percentage of DSF dsf_curb 10 Number of DSF dsf_curb_p 6 Percentage of DSF dsf_ndcbu 10 Number of DSF

throwback matches.

seasonal matches.

educational matches.

vacant matches.

LACS matches.

curb matches.

NDCBU (Neighborhood Delivery Cen-

tralized Box Unit) matches. dsf_ndcbu_p 6 Percentage of DSF dsf_central 10 Number of DSF dsf_central_p 6 Percentage of DSF dsf_slot 10 Number of DSF dsf_slot_p 6 Percentage of DSF

NDCBU matches.

central matches.

doorslot matches.

eor 1 or 2 End of record, present only in ASCII files.

1 byte (LF) on UNIX and VMS.

2 bytes (CRLF) on Windows.

Chapter 3: Reports

File statistics file

The File statistics file contains much of the same information that appears on page 3 and subsequent pages of the Job Summary Report.

The File statistics file describes your input and/or output files. The scope of this statistics file is governed by the Report on Files parameter in the Job Summary Report block. You can choose to include the input file, the output file(s), or both.

To produce the File statistics file, you must also produce the ACE Job Summary report. You can produce the File statistics file with ACE Views or Job, not with ACE Library.

This statistics file contains one re cord per database file, with th e following fields. If you choose to report on both the input and output file, then these fields are repeated.

Field Length Description

filename 80 Path and name of your input or output file. i_o 1 “i” for input; “o” for output. records 10 Number of input or output records, depending on which

statistics you’re viewing (see “i_o” above). zip_cnt 10 Number of records assigned ZIP Codes. zip_p 6 Percentage of records assigned ZIP Codes. zip4_cnt 10 Number of records assigned ZIP+4 codes. zip4_p 6 Percentage of records assigned ZIP+4 codes. dpb_cnt 10 Number of records assigned delivery point barcodes. dpb_p 6 Percentage of records assigned delivery point barcodes. cart_cnt 10 Number of records assigned carrier route. cart_p 6 Percentage of records assigned carrier route. lot_cnt 10 Number of records assigned Line-of-Travel (LOT)

codes. lot_p 6 Percentage of records assigned LOT codes. loto_cnt 10 Number of records assigned LOT Order codes. loto_p 6 Percentage of records assigned LOT Order codes. cnty_cnt 10 Number of records assigned county codes. cnty_p 6 Percentage of records assigned county codes. ageo_cnt 10 Number of records assigned Address-level GeoCensus

codes.

ageo_p 6 Percentage of records assigned Address-level GeoCen-

sus codes. cgeo_cnt 10 Number of records assigned Centroid-level GeoCensus

codes.

ACE User’s Guide

Field Length Description

cgeo_p 6 Percentage of records assigned Centroid-level GeoCen-

sus codes.

zip_cor 10 Number of records whose ZIP Codes were wrong or

missing on input, and were corrected or added on output.

zip_cp 6 Percentage of records whose ZIP Codes were wrong or

missing on input, and were corrected or added on output.

zip4_cor 10 Number of records whose ZIP+4 codes were wrong or

missing on input, and were corrected or added on output.

zip4_cp 6 Percentage of records whose ZIP+4 codes were wrong

or missing on input, and were corrected or added on output.

dpb_cor 10 Number of records whose delivery point barcodes

(DPBC) were wrong or missing on input, and were corrected or added on output.

dpb_cp 6 Percentage of records whose DPBCs were wrong or

missing on input, and were corrected or added on output.

cart_cor 10 Number of records whose carrier route codes were

wrong or missing on input, and were corrected or added on output.

cart_cp 6 Percentage of records whose carrier route codes were

wrong or missing on input, and were corrected or added on output.

lot_cor 10 Number of records whose Line-of-Travel (LOT) codes

were wrong or missing on input, and were corrected or added on output.

lot_cp 6 Percentage of records whose LOT codes were wrong or

missing on input, and were corrected or added on output.

loto_cor 10 Number of records whose LOT Order codes were

wrong or missing on input, and were corrected or added on output.

loto_cp 6 Percentage of records whose LOT Order codes were

wrong or missing on input, and were corrected or added on output.

cnty_cor 10 Number of records whose county codes were wrong or

missing on input, and were corrected or added on output.

cnty_cp 6 Percentage of records whose county codes were wrong

or missing on input, and were corrected or added on output.

Chapter 3: Reports

Field Length Description

ageo_cor 10 Number of records whose Address-level GeoCensus

codes were wrong or missing on input, and were cor-

rected or added on output. ageo_cp 6 Percentage of records whose Address-level GeoCensus

codes were wrong or missing on input, and were cor-

rected or added on output. cgeo_cor 10 Number of records whose Centroid-level GeoCensus

codes were wrong or missing on input, and were cor-

rected or added on output. cgeo_cp 6 Percentage of records whose Centroid-level GeoCensus

codes were wrong or missing on input, and were cor-

rected or added on output. city_cor 10 Number of records whose city data was corrected. city_cp 6 Percentage of records whose city data was corrected. state_cor 10 Number of records whose state data was corrected. state_cp 6 Percentage of records whose state data was corrected. a_trunc 10 Number of records whose address data was truncated. a_trunc_cp 6 Percentage of records whose address data was trun-

cated. c_trunc 10 Number of records whose city data was truncated. c_trunc_cp 6 Percentage of records whose city data was truncated. street_at 10 Number of records with a street address type. street_p 6 Percentage of records with a street address type. po_at 10 Number of records with a post office box address type. po_p 6 Percentage of records with a post office box address

type. hr_at 10 Number of records with a highrise address type. hr_p 6 Percentage of records with a highrise address type. rr_at 10 Number of records with a rural route address type. rr_p 6 Percentage of records with a rural route address type. f_at 10 Number of records with a firm address type. f_p 6 Percentage of records with a firm address type. gd_at 10 Number of records with a general delivery address type. gd_p 6 Percentage of records with a general delivery address

type. m_at 10 Number of records with a military address type.

m_p 6 Percentage of records with a military address type. u_at 10 Number of records with a unique address type. u_p 6 Percentage of records with a unique address type.

ACE User’s Guide

Field Length Description

qss_hr_at 10 Number of highrise exact matches.

This statistic corresponds to USPS-required information in the Qualitative Statistical Summary (QSS) section of PS Form 3553.

qss_hr_p 6 Percentage of highrise exact matches.

This statistic corresponds to USPS-required information in the QSS section of PS Form 3553.

qss_hrd_at 10 Number of highrise default matches.

This statistic corresponds to USPS-required information in the QSS section of PS Form 3553.

qss_hrd_p 6 Percentage of highrise default matches.

This statistic corresponds to USPS-required information in the QSS section of PS Form 3553.

qss_rr_at 10 Number of rural route exact matches.

This statistic corresponds to USPS-required information

in the QSS section of PS Form 3553. qss_rr_p 6 Percentage of rural route exact matches.QSS qss_rrd_at 10 Number of rural route default matches.

This statistic corresponds to USPS-required information

in the QSS section of PS Form 3553. qss_rrd_p 6 Percentage of rural route default matches.

This statistic corresponds to USPS-required information

in the QSS section of PS Form 3553. qss_lacs_at 10 Number of LACS convertible addresses.

This statistic corresponds to USPS-required information

in the QSS section of PS Form 3553. qss_lacs_p 6 Percentage of LACS convertible addresses.

This statistic corresponds to USPS-required information

in the QSS section of PS Form 3553. dpv_str_cnt 10 Number of records that were Delivery Point Validation

(DPV) confirmed. dpv_str_p 6 Percentage of records that were DPV confirmed. dpv_cmra_cnt 10 Number of records that were DPV confirmed as a Com-

mercial Mail Receiving Agency (CMRA). dpv_cmra_p 6 Percentage of records that were DPV confirmed as a

CMRA. dpv_prim_no_cnt 10 Number of records that could not be confirmed during

DPV processing because the primary range could not be

confirmed. dpv_prim_no_p 6 Percentage of records that could not be confirmed dur-

ing DPV processing because the primary range could

not be confirmed.

Chapter 3: Reports

Field Length Description

dpv_sec_no_cnt 10 Number of records that could not be confirmed during

DPV processing because the secondary range could not be confirmed.

dpv_sec_no_p 6 Percentage of records that could not be confirmed dur-

ing DPV processing because the secondary range could not be confirmed.

dpv_sec_miss_cnt 10 Number of records that could not be confirmed during

DPV processing because the secondary range was missing.

dpv_sec_miss_p 6 Percentage of records that could not be confirmed dur-

ing DPV processing because the secondary range was

missing. dpv_ties_cnt 10 Number of ties resolved through DPV processing. rdi_cnt 10 Number of Residential Delivery Indicator (RDI)

matches. rdi_p 6 Percentage of RDI matches. ste_match 10 Number of Suite ste_p 6 Percentage of addresses that had Suite dsf_drop 10 Number of DSF dsf_drop_p 6 Percentage of DSF dsf_business 10 Number of DSF dsf_business_p 6 Percentage of DSF dsf_throwback 10 Number of DSF dsf_throwback_p 6 Percentage of DSF dsf_seasonal 10 Number of DSF dsf_seasonal_p 6 Percentage of DSF dsf_educational 10 Number of DSF dsf_educational_p 6 Percentage of DSF dsf_vacant 10 Number of DSF dsf_vacant_p 6 Percentage of DSF dsf_lacs 10 Number of DSF dsf_lacs_p 6 Percentage of DSF dsf_curb 10 Number of DSF dsf_curb_p 6 Percentage of DSF dsf_ndcbu 10 Number of DSF

Link

matches.

Link

matches.

drop matches.

business matches.

throwback matches.

seasonal matches.

educational matches.

vacant matches.

LACS matches.

curb matches.

NDCBU (Neighborhood Delivery

Centralized Box Unit) matches. dsf_ndcbu_p 6 Percentage of DSF dsf_central 10 Number of DSF

NDCBU matches.

central matches.

ACE User’s Guide

Field Length Description

dsf_central_p 6 Percentage of DSF2 central matches. dsf_slot 10 Number of DSF dsf_slot_p 6 Percentage of DSF

doorslot matches.

e101 10 Number of records assigned error code E101:

Last line is bad or missing e101_p 6 Percentage of records assigned error code E101. e212 10 Number of records assigned error code E212:

No city and bad ZIP e212_p 6 Percentage of records assigned error code E212. e213 10 Number of records assigned error code E213:

Bad city and no ZIP e213_p 6 Percentage of records assigned error code E213. e214 10 Number of records assigned error code E214:

Bad city and bad ZIP e214_p 6 Percentage of records assigned error code E214. e216 10 Number of records assigned error code E216:

Bad ZIP, can't determine which city match to select e216_p 6 Percentage of records assigned error code E216. e302 10 Number of records assigned error code E302:

No primary address line parsed e302_p 6 Percentage of records assigned error code E302. e412 10 Number of records assigned error code E412:

Street name not found in directory e412_p 6 Percentage of records assigned error code E412. e413 10 Number of records assigned error code E413:

Possible street name matches too close to choose e413_p 6 Percentage of records assigned error code E413. e420 10 Number of records assigned error code E420:

Primary range is missing e420_p 6 Percentage of records assigned error code E420. e421 10 Number of records assigned error code E421:

Primary range is invalid for street/route/building e421_p 6 Percentage of records assigned error code E421. e422 10 Number of records assigned error code E422:

Predirectional needed, input is wrong or missing e422_p 6 Percentage of records assigned error code E422. e423 10 Number of records assigned error code E423:

Suffix needed, input is wrong or missing e423_p 6 Percentage of records assigned error code E423.

Chapter 3: Reports

Field Length Description

e425 10 Number of records assigned error code E425:

Suffix & directional needed, input wrong or missing e425_p 6 Percentage of records assigned error code E425. e427 10 Number of records assigned error code E427:

Postdirectional needed, input is wrong or missing e427_p 6 Percentage of records assigned error code E427. e428 10 Number of records assigned error code E428:

Bad ZIP, can't select an address match e428_p 6 Percentage of records assigned error code E428. e429 10 Number of records assigned error code E429:

Bad city, can't select an address match e429_p 6 Percentage of records assigned error code E429. e430 10 Number of records assigned error code E430:

Possible addr. line matches too close to choose one e430_p 6 Percentage of records assigned error code E430. e431 10 Number of records assigned error code E431:

Urbanization needed, input is wrong or missing e431_p 6 Percentage of records assigned error code E431. e439 10 Number of records assigned error code E439:

Exact match in EWS directory e439_p 6 Percentage of records assigned error code E439. e500 10 Number of records assigned error code E500:

Other Error e500_p 6 Percentage of records assigned error code E500. e501 10 Number of records assigned error code E501:

Foreign e501_p 6 Percentage of records assigned error code E501. e502 10 Number of records assigned error code E502:

Input record entirely blank e502_p 6 Percentage of records assigned error code E502. e503 10 Number of records assigned error code E503:

ZIP not in area covered by partial ZIP+4 Directory e503_p 6 Percentage of records assigned error code E503. e504 10 Number of records assigned error code E504:

Overlapping ranges in ZIP+4 directory e504_p 6 Percentage of records assigned error code E504.

ACE User’s Guide

e505 10 Number of records assigned error code E505:

Matched to undeliverable default record e505_p 6 Percentage of records assigned error code E505.

Field Length Description

e600 10 Number of records assigned error code E600:

Marked by USPS as unsuitable for delivery of mail e600_p 6 Percentage of records assigned error code E600. eor 1 or 2 End of record, present only in ASCII files.

1 byte (LF) on UNIX and VMS.

2 bytes (CRLF) on Windows.

Chapter 3: Reports

Address Conversion Statistics (ACS) file

Compare to CSL The NCOA

run of address conversion processes, such as NCOA and DPV. The USPS requires this information in this single-file format. However , because of the large file size, it can be difficult to find specific information contained in the CSL.

The ACS file contains all the same information that’s in the CSL, plus additional information (such as licensee name, input database name, and Mover ID “00” matches). Unlike the CSL, the ACS file contains information about only the last run. You can name the file whatever you like, choose its format, and easily find information about your most recently processed data.

When you process a job using an assignment mode of Geo or Parse, ACE does not produce the ACS file.

To generate the ACS file, perform Mover ID NCOA which is available in ACE as an add-on options. You can produce the ACS file with ACE Library, Views, or Job depending on what add-on option you have.

It is possible to generate the ACS file through ACE Library without performing NCOA ACS file is about move updates, if you produce the ACS file without performing NCOA

The ACS file contains a single record with the following fields:

Link

-required customer service log (CSL) contains a record for each

Link

processing. However , because most of the data in the

Link

processing, most of the data in the file will be zeroes.

Link

, LACS

or Suite

Link

, ANK

Link

processing,

Link

Field Length Description

LICEN_ID 5 Licensee ID (USPS assigned). LIST_SIC 7 List Owner North American Industry Classification System (NAICS). FREQ_PROC 4 Frequency of Processing. LIST_ID 7 List ID (Licensee assigned). PROC_CAT 10 The type of processing performed. ADD_NOTES 2 Additional notes. “A” in this field means that the customer provided written

request for a longer processing period.

PROC_PRE 2 Preprocessing performed.

N None Y Yes, but with no data modifications D Yes, data modifications from sources other than postal data P Yes, data modifications from postal data only (for example, ZIP+4 or DPV) B Yes, data modifications from postal and other sources

PROC_CON 2 Concurrent processes performed.

ACE User’s Guide

Field Length Description

PROC_POST 2 Post-processes performed.

N None Y Yes, but with no data modifications D Yes, data modifications from sources other than postal data P Yes, data modifications from postal data only (LACS B Yes, data modifications from postal and other sources.

Link

)

STD_OUTPUT 2 Standard output returned.

Y All NCOA

Link

-required output returned to client N Post-processes modified return information (updates applied to list) B Post-processes modified return information; however, separate file containing

all required output data was also returned

MTCH_LOGIC 2 Matching logic applied.

S Standard (business, individual, and family matches) I Individual only B Business only C Individual and business only

DATA_RET 2 Data returned.

C COA data returned (inc luding footnotes and processing statistics) F Footnotes (no COA data included; may include processing statistics) S Statistics only (no COA data or footnotes provided)

NO_MON_REQ 3 Number of months requested. By request of list owner, number of months for

which COA data accepted.

CLASS_MAIL 2 Class of mail to be used for mailings produced from customer mailing list.

A First-Class only B Periodicals only C Standard Mail only D Package Services only E First-Class and Periodicals F First-Class and Standard Mail G First-Class and Package Services H Periodicals and Standard Mail I Periodicals and Package Services J Standard Mail and Package Services K First-Class, Periodicals, and Standard Mail L First-Class, Periodicals, and Package Services M First-Class, Standard Mail, and Package Services N Periodicals, Standard Mail, and Package Services O First-Class, Periodical, Standard Mail, and Package Services

LIST_REC 9 Date list received from customer. PRO_BEGIN 9 Date NCOA PRO_END 9 Date NCOA

Link

processing began.

Link

processing was complete. LIST_RET 9 Date list returned to customer. RECS_PROC 11 Total number of records processed. NCOA_QURY 11 Total number of NCOALink queries performed.

Chapter 3: Reports

Field Length Description

PROC_POST 2 Post-processes performed.

Link

)

STD_OUTPUT 2 Standard output returned.

Y All NCOA

Link

-required output returned to client N Post-processes modified return information (updates applied to list) B Post-processes modified return information; however, separate file containing

all required output data was also returned

MTCH_LOGIC 2 Matching logic applied.

S Standard (business, individual, and family matches) I Individual only B Business only C Individual and business only

DATA_RET 2 Data returned.

C COA data returned (inc luding foot notes and processing statistics) F Footnotes (no COA data included; may include processing statistics) S Statistics only (no COA data or footnotes provided)

NO_MON_REQ 3 Number of months requested. By request of list owner, number of months for

which COA data accepted.

CLASS_MAIL 2 Class of mail to be used for mailings produced from customer mailing list.

LIST_REC 9 Date list received from customer. PRO_BEGIN 9 Date NCOA PRO_END 9 Date NCOA

Link

processing began.

Link

processing was complete. LIST_RET 9 Date list returned to customer. RECS_PROC 11 Total number of records processed. NCOA_QURY 11 Total number of NCOALink queries performed.

ACE User’s Guide

Field Length Description

RECS_MTCH 11 Total number of records matched. Results returned indicate return codes A, 91, 92,

01, 02, 03, 05, 14, and 19.

RECS_REJ 11 Total number of matches rejected. Results discarded based on Move Effective

Date: Return code 00 generated due to age of COA. RECS_ZIP4 11 Total number of records ZIP+4 coded. RECS_DPV 11 Total number of records DPV confirmed. SW_NAME 31 ZIP+4 software name. SW_VERSION 13 ZIP+4 software version. Z4_DIRDATE 9 ZIP+4 directory release date. NCO_SWNAME 31 NCOA NCO_SWVER 13 NCOA NCO_DIRDAT 9 NCOA

Link

software name.

Link

software version.

Link

data release date. DPV_SWNAME 31 DPV software name. DPV_SWVER 13 DPV software version. DPV_DIRDAT 9 DPV data release date. ZIP4_POBOX 11 ZIP+4 match statistics. Total matched to PO box. ZIP4_HCBOX 11 ZIP+4 match statistics. Total matched to HCR exact. ZIP4_RR_DF 11 ZIP+4 match statistics. Total matched to RR default. ZIP4_FIRM 11 ZIP+4 match statistics. Total matched to firm. ZIP4_GD 11 ZIP+4 match statistics. Total matched to general delivery. ZIP4_HR_DF 11 ZIP+4 match statistics. Total matched to highrise default. ZIP4_MIL 11 ZIP+4 match statistics. Total matched to military. ZIP4_NONDE 11 ZIP+4 match statistics. Total matched to nondeliverable. ZIP4_RRBOX 11 ZIP+4 match statistics. Total matched to RR exact. ZIP4_ST 11 ZIP+4 match statistics. Total matched to street. ZIP4_HCDEF 11 ZIP+4 match statistics. Total matched to HCR default. ZIP4_HRSEC 11 ZIP+4 match statistics. Total matched to highrise exact. ZIP4_OTHER 11 ZIP+4 match statistics. Total matched to other. ZIP4_LACS 11 ZIP+4 match statistics. Total matched to positive LACS. ZIP4_EWS 11 ZIP+4 match statistics. Total matched to EWS. RETCODE_A 11 NCOA

Link

return code A. NCOA

Link

match. New address provided by NCOA

Exact match.

RETCODE_91 11 NCOA

ink

. Input record was missing secondary address and matched NCOA

Link

return code 91. NCOA

Link

match. New address provided by NCOA

that had a secondary address.

Link

record

L-

Chapter 3: Reports

Field Length Description

RETCODE_92 11 NCOA

Link

ink

. Input record contained secondary address and matched NCOA

return code 92. NCOA

was missing secondary address. RETCODE_00 11 NCOA RETCODE_01 11 NCOA RETCODE_02 11 NCOA RETCODE_03 11 NCOA RETCODE_04 11 NCOA

Link

return code 00. No NCOA

Link

return code 01. NCOA

Link

return code 02. NCOA

Link

return code 03. NCOA

Link

return code 04. No NCOA

with secondary. RETCODE_05 11 NCOA

Link

return code 05. NCOA

(DPBC) is ambiguous. RETCODE_06 11 NCOA

Link

return code 06. No NCOA

match. RETCODE_07 11 NCOA RETCODE_08 11 NCOA RETCODE_09 11 NCOA

Link

return code 07. No NCOA

Link

return code 08. No NCOA

Link

return code 09. No NCOA

default. RETCODE_10 11 NCOA

Link

return code 10. No NCOA

highway contract default. RETCODE_11 11 NCOA

Link

return code 11. No NCOA

name data. RETCODE_12 11 NCOA RETCODE_13 11 NCOA RETCODE_14 11 NCOA RETCODE_15 11 NCOA

Link

return code 12. No NCOA

Link

return code 13. No NCOA

Link

return code 14. NCOA

Link

return code 15. No NCOA

input to match. RETCODE_16 11 NCOA RETCODE_17 11 NCOA RETCODE_18 11 NCOA

Link

return code 16. No NCOA

Link

return code 17. No NCOA

Link

return code 18. No NCOA

Delivery. RETCODE_19 11 NCOA RETCODE_20 11 NCOA

Link

return code 19. NCOA

Link

return code 20. No NCOA

directions. RETCODE_66 11 NCOA

Link

return code 66. No NCOA

Delete” suppression file.

Link

match. New address provided by NCOA

Link

match.

Link

match. Foreign move.

Link

match. Moved Left No Address (MLNA).

Link

match. Box Closed No Order (BCNO).

Link

match. Family move from street address

Link

match. New 11 digit delivery point barcode

Link

match. Middle names or initials don’t

Link

match. Genders don’t match.

Link

match. Conflicting new addresses.

Link

match. Family move from highrise

Link

match. Family move from rural route or

Link

match. Individual move, insufficient

Link

match. Middle name test failed.

Link

match. Gender test failed.

Link

match. New address would not convert.

Link

match. Individual name insufficient on

Link

match. Secondary number discrepancy.

Link

match. Different first name.

Link

match. Family move from General

Link

match. New address not ZIP+4 codable.

Link

match. Multiple response, conflicting

Link

match. Input address appears in “Daily

Link

record that

L-

DPV_AA 11 DPV footnotes. ZIP+4 match. DPV_A1 11 DPV footnotes. No ZIP+4 match. DPV_M1 11 DPV footnotes. Primary number missing. DPV_M3 11 DPV footnotes. Primary number invalid.

ACE User’s Guide

Field Length Description

DPV_P1 11 DPV footnotes. Missing PO, RR, or HC Box number. DPV_P3 11 DPV footnotes. Invalid PO, RR, or HC Box number. DPV_BB 11 DPV footnotes. DPV matched (all components). DPV_RR 11 DPV footnotes. DPV matched to Commercial Mail Receiving Agency (CMRA). DPV_CC 11 DPV footnotes. Primary number match; secondary present but invalid. DPV_N1 11 DPV footnotes. Primary number match. Secondary missing. DPV_R1 11 DPV footnotes. DPV matched to CMRA. Personal Mail Box (PMB) number not

present.

ADD_MON_0 ADD_MON_48

through

11 Total number of matches made with Move Ef fective Date (MED) corresponding to

the process date. Addresses matched month 0 – 48. OPER_ID 7 Operator ID. Identification code for the operator who processed this list. BUY_CO_NAM 31 Buyer company name. If the processed list was for rent, sale, or lease, this is the

name of the company (or individual) purchasing the list. MAIL_ZIP 6 Mailing ZIP Code. ZIP Code of Business Mail Entry Unit (BMEU) or post office

at which mail will be submitted for mailing. DPV_ST_VAL 11 DPV statistics. Street (S) records validated. DPV_ST_CP 11 DPV statistics. Street (S) records validated. CMRA presented. DPV_ST_CV 11 DPV statistics. Street (S) records validated. CMRA validated. DPV_HIR_RV 11 DPV statistics. Highrise (H) records validated. DPV_HIR_CP 11 DPV statistics. Highrise (H) records validated. CMRA presented. DPV_HIR_CV 11 DPV statistics. Highrise (H) records validated. CMRA validated. DPV_POB_RV 11 DPV statistics. PO box (P) records validated. DPV_RR_RV 11 DPV statistics. RR/HC (R) records validated. DPV_RR_CP 11 DPV statistics. RR/HC (R) records validated. CMRA presented. DPV_RR_CV 11 DPV statistics. RR/HC (R) records validated. CMRA validated. DPV_FRM_RV 11 DPV statistics. Firm (F) records validated. DPV_FRM_CP 11 DPV statistics. Firm (F) records validated. CMRA presented. DPV_FRM_CV 11 DPV statistics. Firm (F) records validated. CMRA validated. DPV_GD_R V 11 DPV statistics. General delivery (G) records validated. DPV_PE_TOT 11 DPV statistics. Total primary number error. DPV_PE_ST 11 DPV statistics. Street (S) records with primary number error. DPV_PE_HIR 11 DPV statistics. Highrise (H) records with primary number error. DPV_PE_POB 11 DPV statistics. PO box (P) records with primary number error. DPV_PE_RR 11 DPV statistics. RR/HC (R) records with primary number error. DPV_PE_FRM 11 DPV statistics. Firm (F) records with primary number error. DPV_SE_TOT 11 DPV statistics. Total secondary number error.

Chapter 3: Reports

Field Length Description

DPV_SE_ST 11 DPV statistics. Street (S) records with secondary number error. DPV_SE_HIR 11 DPV statistics. Highrise (H) records with secondary number error. DPV_SE_FRM 11 DPV statistics. Firm (F) records with secondary number error. LAC_SWNAME 31 LACS LAC_SWVER 13 LACS LAC_DIRDAT 9 LACS LAC_RET_A 11 LACS LAC_RET_00 11 LACS LAC_RET_14 11 LACS LAC_RET_92 11 LACS

Link

software name.

Link

software version.

Link

data release date.

Link

return codes. LACS record match.

Link

return codes. No match.

Link

return codes. Found LACS record. New address would not convert.

Link

return codes. Match with secondary number dropped on input. DPV_RET_F1 11 DPV additional return codes. Military. DPV_RET_U1 11 DPV additional return codes. Unique ZIP Code. DPV_RET_G1 11 DPV additional return codes. General delivery. DPV_RET_NL 11 DPV additional return codes. New address not DPV confirmable with vendor soft-

ware.

ANK_RET_A, ANK_RET_00

through

11 ANK

Link

return codes. ANK

codes. See “RETCODE_A” on page 81 through “RETCODE_66” on page 82.

Link

return codes are the same as NCOA

Link

return

ANK_RET_20, ANK_RET_66, ANK_RET_92, ANK_RET_91,

TOT_ANKMAT 11 Total records matched using ANK LAC_RET_09 11 LACS TOT_LACCON 11 Total records LACS

Link

Return Codes. Old address highrise default, no new address.

Link

converted.

Link

MLIST_NAME 31 User given list name. LIC_NAME 31 Licensee name. INP_DB 200 Input file. CUST_CONAM 51 Customer company name.

ACE User’s Guide

Chapter 4: Postal certification and forms

The United States Postal Service (USPS) tests and certifies the accuracy of address software. They do this because, for their own efficiency, they want to make sure that the mail they receive is accurately addressed and barcoded.

For you, the ACE user, there are two issues to be aware of:

 Maintaining your certified status.  Handling the postal forms that ACE provides you.

Chapter 4: Postal certification and forms

U.S. Postal Service certification programs: CASS and NDI

CASS ACE is certified by the USPS and meets the Coding Accuracy Support System

(CASS) result, ACE may produce a facsimile of USPS Form 3553, the CASS Summary Report. You will need a 3553 form to qualify mailings for postage discounts.

For more information about CASS, call the USPS National Customer Support Center (NCSC), CASS department, at 1-800-238-3150 or write to:

You’ll also find information about CASS in the USPS’s Domestic Mail Manual.

NDI The National Deliverability Index is a program of the USPS. It is a method of

measuring and scoring the quality of address lists. The measuring and scoring are performed during processing by ZIP+4 matching software such as ACE. The result is a printed report, called the NDI Report. The USPS uses the NDI Report to verify that the software is capable of determining the input-record quality.

You mig ht use the NDI report to gauge the quality of address lists before you purchase or lease them. You’ll be wise to ask the list broker to supply an NDI report for the mailing list in which you’re interested. Better yet, ask competitive list brokers to supply NDI reports on their lists. Consider the NDI results when choosing which list to purchase.

standards for accuracy of postal coding and address correction. As a

CASS/ZIP+4 Matching National Customer Support Center 6060 Primacy Parkway, Suite 101 Memphis, Tennessee 38188-0001

If you’re a list broker, NDI can be used to assure potential clients of the quality of your lists.

Points to remember The important points to remember about CASS and NDI are:

 CASS and NDI certification are given to softwar e programs. The CASS and

NDI reports pertain to address lists.

 CASS certification proves that the software can assign and standardize

addresses correctly. NDI certification simply means that the software can produce correct statistics about assignment and standardization.

 Software vendors are the primary candidates for NDI certification. As an e nd

user, you are not required to obtain either certification. Only a handful of mailers will need end-user CASS or NDI certification. For example, Optional Procedure mailers working toward Stage 2 System Certification will apply for NDI certification.

 Unlike the CASS Report (Form 3553), the NDI Report is not required to be

submitted with a mailing.

Not for interactive programs

Per U.S. Postal Service rules, ACE can generate USPS forms only after a batch process.

We are not permitted to give you a 3553 form when you operate ACE

interactively.

For example, ACE will not generat e a 3553 form when you operate ACE Views in Interactive mode, or when RapidKey Library is used.

ACE User’s Guide

USPS Form 3553

|------------------------------------------------------------------------------| | | A1. CASS | | |--------------------------------------------------------------------------| | | CASS Certified Company Name Configuration | | | Business Objects STD | | | CASS Certified Software Name & Version | | | ACE 7.80.01.L | | | Z4Change Certified Company Name Configuration | | | N/A | | | Z4Change Software Name & Version | | S | | | O | eLOT Certified Company Name Configuration | | F | Business Objects STD | | T | eLOT Software Name & Version | | W | ACE 7.80.01.L | | A |--------------------------------------------------------------------------| | R | A2. MASS | | E |--------------------------------------------------------------------------| | | MASS Certified Company Name | | | | | | MASS Certified Software Name & Version | | | | | | Configuration MLOCR Serial Number | | | | |---|--------------------------------------------------------------------------| | | B1. LIST PROCESSOR | B2. DATE LIST PROCESSED | B3. DATE OF DATABASE | | | | | | | | ACE PT Team | MASTER FILE: 27-Mar-2006 | ZIP+4 FILE: 02/2006 | | L | | DPV: | DPV: | | I | | Z4CHANGE: | Z4CHANGE: | | S | | eLOT: 27-Mar-2006 | eLOT: 02/2006 | | T | | CRIS: | CRIS: | | |------------------------|--------------------------|----------------------| | | B4. ADDRESS LIST NAME | B5. NUMBER OF LISTS | B6. TOTAL ADDRESSES | | | rpt005.txt | 1 | 896 | |---|--------------------------------------------------------------------------| | | | | VALIDATION PERIOD | | O | CASS OUTPUT RATING | TOTAL CODED | FROM TO | | U |-------------------------------|--------------|---------------------------| | T | C1. RECORDS ZIP4/DPV Confirmed| 567 | 03/27/2006 | 09/23/2006 | | P | C2. RECORDS Z4CHANGE PROCESSED| 0 | XXXXXXXXXX | XXXXXXXXXX | | U | C3. RECORDS DPBC CODED | 567 | 03/27/2006 | 09/23/2006 | | T | C4. RECORDS 5-DIGIT CODED | 842 | 03/27/2006 | 03/27/2007 | | | C5. RECORDS CR RT CODED | 582 | 03/27/2006 | 06/25/2006 | | | C6. RECORDS eLOT ASSIGNED | 567 | 03/27/2006 | 06/25/2006 | |---|--------------------------------------------------------------------------| | | D1. SIGNATURE OF MAILER | D2. DATE SIGNED | | | | | | M | | | | A | ----------------------------------| | | I | I certify that the mailing |--------------------------------------| | L | submitted with this form has been | D3. NAME & ADDRESS OF MAILER | | E | ZIP+4 coded (as indicated above) | Accounting Department | | R | using CASS certified software | 100 Harborview Plaza | | | meeting all requirements of | La Crosse WI 54601 | | | Domestic Mail Manual 708. | United States | |---|--------------------------------------------------------------------------| | | For Informational Purposes Only: QSS is solely made available for the | | | list processor's review and analysis. This information is not to be | | | considered by the Postal Service personnel in determining rate | | Q | eligibility under any circumstances. | | S |--------------------------------------------------------------------------| | S | High Rise | High Rise | Rural Route | Rural Route | LACSLink | | | Default | Exact | Default | Exact | | | |--------------|--------------|--------------|--------------|--------------| | | ############ | ############ | ########### | ########### | ############ | | |--------------|--------------|--------------|--------------|--------------| | | EWS | SuiteLink | | | | | | | | |--------------|--------------| | | | ############ | ############ | |

-------------------------------------------------------------------------------Busniess Objects(54601-4071) Form 3553, (certification date)

How to generate the form

Product Action

Chapter 4: Postal certification and forms

ACE Views and ACE Job Include the Report: USPS Form 3553 block in your job. ACE Library Call ace_3553() or ace_3553_file().

Extended ASCII How capable is your report printer? If your printer can print characters in the

extended ASCII set, ACE will draw the 3553 form with smooth lines. If you indicate that you can’t print extended ASCII, ACE will use hyphens and pipes instead, like the sample on the previous page. If you’re not sure, please check your printer manual.

Data on the form Some parts of the form require information from you, through parameters that

you set. CASS Certified Company Name (A1). By default, ACE prints “Business

Objects” on the form, indicating that Business Objects has ven dor-level CASS certification. If you have end-user CASS certification, you may enter your own company name through a parameter.

CASS Certified Software Name & Version (A1). By default, ACE prints “ACE,” version number, and date of certification. If you have end-user CASS certification, you may enter your own product name, version number, and date through a parameter.

List Processor’s Name (B1). Enter your company name.

Much information is automatic

List Name (B4). This is the name of the database you are processing. ACE View and ACE Job automatically use the pathname of the input file or output file (whichever the report covers). ACE Library users must provide the file name as a parameter.

Name & Address of Mailer (D2). Enter the company name and address. This might be your own company, if you are preparing your own mail. If you’re processing a database for another company, enter their name and address. Generally, this name and address should match those listed on your other mail ing forms, such as the Statement of Postage.

ACE produces most of the dates and statistics automatically: Date List Processed: This is the date of the ACE run, based on the system's time-

of-day clock. Date of ZIP+4 Database: This is derived from a timestamp inside your ZIP+4

directory . It is the date that th e directo ry file was produced at Business Objects. It is not the file timestamp provided by the operating system.

Records Coded: The statistics here are tallied by ACE.

ACE User’s Guide

The National Deliverability Index (NDI) report

NATIONAL DELIVERABLITY INDEX CUSTOMER RATING COMPANY: IDENTIFICATION NUMBER: DATE PROCESSED: 04/22/2004 FILE DATE: 04/20/2004 CLASSIFICATION

----------------------------------------------------------------------------| (1) | % OF TOTAL ADDRESSES CONTAINING CORRECT ZIP+4 CODES | | | | IN ACCORDANCE WITH THE CURRENT USPS ZIP+4 FILE. | 63.73 % | |-----|-------------------------------------------------------|-------------| | | % OF ADDRESSES CONTAINING APARTMENT NUMBERS FOR | | | (2) | ADDRESSES DESTINED TO APARTMENT BUILDINGS IDENTIFIED | | | | IN THE CURRENT USPS ZIP+4 FILE. | 36.36 % | |-----|-------------------------------------------------------|-------------| | | % OF ADDRESSES CONTAINING BOTH RURAL/HIGHWAY CONTRACT | | | (3) | ROUTE AND BOX NUMBERS FOR ADDRESSES DESTINED TO | | | | RURAL/HIGHWAY CONTRACT ROUTES. | 38.83 % | |-----|-------------------------------------------------------|-------------| | | % OF TOTAL ADDRESSES CONTAINING CORRECT ZIP CODES IN | | | (4) | ACCORDANCE WITH THE CURRENT USPS CITY/STATE AND | | | | 5-DIGIT FILE. | 93.86 % | |-----|-------------------------------------------------------|-------------| | | % OF ADDRESSES CONTAINING CORRECT CARRIER ROUTES IN | | | (5) | ACCORDANCE WITH THE CURRENT USPS CRIS FILE. | 65.51 % | |-----|-------------------------------------------------------|-------------| | | MOST RECENT DATE THE LIST WAS PROCESSED AND UPDATED | | | (6) | THROUGH A USPS APPROVED ADDRESS CORRECTION PROCESS. | N/A | |-----|-------------------------------------------------------|-------------| | | ALL "MOVED LEFT NO FORWARDING ADDRESS" RECORDS HAVE | | | (7) | BEEN DELETED. | YES |

-----------------------------------------------------------------------------

How to generate the form

Product Action

ACE Views and ACE Job Include the Report: NDI block in your job. ACE Library Call ace_ndi() or ace_ndi_file().

Report settings You must enter the following information, which will appear on the report.

Option Description

Company Name Enter your company name. The maximum length is 40 characters. Company ID Enter the identification number that was assigned to you by the NCSC.

The maximum length is 20 characters. If you leave this parameter blank, nothing will be printed.

MLNFA Deleted

MLNF A is an abbreviation for “Moved Left No Forwarding Address.” When records are processed through the National Change of Address (NCOA) system, some MLNFA records are bound to result. If you delete all MLNFA records, select this option.

Extended ASCII

Note that NCOA

If your printer supports the extended ASCII character set, be sure to select this option. ACE will produce smooth lines when it prints the

MLNFA

Link

return codes.

sometimes appears as

MLNA

, notably in

NDI report. If you choose not to print extended ASCII, ACE will pro duce dashed lines within the form.

Chapter 4: Postal certification and forms

Much information is automatic

ACE produces most of the dates and statistics automatically, including the Date Processed, File Date, and fields #1 through #5.

ACE always prints “N/A” (not applicable) in field #6, since ACE cannot determine this date. You must write this date on the report.

The NCSC ignores the last two entries on the report, fields #6 and #7. These are useful to you when analyzing the results of an NDI report generated by a list broker.

ACE User’s Guide

Chapter 5: View the directories with Show

With ACE you also receive tools for looking inside the postal directories. Most often, our customers use these tools to find out why an address didn’t assign, or to better understand how the address was matched and standardized.

This chapter explains general information about the p ostal d irectori es and how to search them. We also present a quick look at Views Show, our directory-query tool.

Chapter 5: View the directories with Show

Query postal directories

When ACE users want to look into the postal directories, it’s usually for one of

reasons:

these

 ACE standardized the address in an unexpected way. Why?  ACE didn’t assign the address. Why not?  ACE’s error code indicates a flaw in the input address. What’s wrong?

Questions like these are by far the most common ACE questions coming into our Help Desk. But you will probably save time, and learn more, if you use th e Show tools to find your own answers to these questions.

The Show programs are for looking inside the postal directories. There’s LastLine Show for looking at city-state -ZIP data in the City and ZCF directories. And there’s Address-Line Show for looking at the national directory.

Sample address query Here is an example of using Show to investigate an address question. Use the

Show program to see discover why ACE changed the city and the ZIP Code for this address.

Let’s take a look at the original and standardized addresses:

Input record Output record

Line1= 6 ginger lake drive w Line2= edwardsville il 62025

Line1 = Line2 = Err_Stat =

6 Ginger Lake Dr W

Glen Carbon

SB00

62034

The Err_Stat field indicates that ACE changed the city and ZIP. This might seem like a place to use Last Line Show. But in fact, our suggestion is

to look up the address line with Address Line Show. When ACE changes two last-line components so drastically, it may be a ZIP

Move record. ZIP Move enables ACE to assign a new last line when a post office closes or a new office opens. Remember, the USPS says the address should be based on the city where the serving post office is located, not necessarily the city where the recipient lives.

ACE User’s Guide

Here’s what the query looks like in one of our Show programs.

The “T” for True means that indeed this record is affected by a post-office change.

When you suspect a ZIP Move, look up the address using the old ZIP Code, not the ZIP Code ACE assigned.

ZIP move component ACE offers an output component (AP field) called ZIP_Move. When ZIP_Move

= T, it means that there’ s a ZIP Move c ha nge an d AC E ha s produc ed th e new last line for this address.

If you set up ACE to standardize your last-line data, then it will automatically produce the new last line for any ZIP Move record. There is no option to turn off ZIP Move conversions.

Of course, if you choose not to standardize last-line information, then ACE cannot give you the new, correct last line. However, you can still use the ZIP_Move output component to detect ZIP Move reco rds.

Chapter 5: View the directories with Show

Most ACE programs include Show

ACE Views ACE Views includes Address and Last Line Show

programs. They’re instantly menu. On the next two pages, you’ll find pictures and samples

of Views Show.

ShowA and ShowL are not available in Remote Views.

accessible at the Tools

For detailed information about Views Show, please refer to the online help.

ACE Job and PrintForm ACE

ACE Job and PrintForm ACE do not, by themselves, perform directory queries. However, when you buy these programs, you also receive two Show programs.

 ShowA (showa.exe) for address-line queries in the ZIP+4 directory.  ShowL (showl.exe) for last-line queries in the City and ZCF directories.

These programs give you the same directory access as Views Show. You can use all the same query fields, and you have the option to vie w resul ts on you r screen, write them to an output file, or both.

Unlike Views, ShowA and ShowL do not present graphical displays. So you can use these programs on non-graphical systems such as DOS, UNIX, and so on.

You control ShowA and ShowL by setting parameters in a text configuration file (showa.cfg and showl.cfg). Y o u may enter your query data as options on your command line, or let the program prompt you to enter your query one line at a time.

For information on ShowA and ShowL, see the ShowA/ShowL User’s Guide.

ACE Library ACE Library offers two sets of functions for directory queries. The first set is

used for querying the ZIP+4 directory about address-line data. The second set is for querying the City and ZCF directories ab out last-line data. These are described in an appendix of the ACE Library Reference.

On most—not all— platforms ACE Library comes with ready-to-run executables for the same ShowA and ShowL programs that ACE Job users receive (described above). We also provide source code for two sample programs, showtest.c and shwlltst.c.

For user interface ideas, look over Views Show on the next two pages.

ACE User’s Guide

Using Last Line Show for queries in the City/ZCF files

Using the ACE Views tool, Last Line Show, is easy. There are just two windows—one for you to set up your query results.

You have the option to view results on your screen, write them to an output file, or both. You can see this option on the setup window (shown at right).

You can perform queries either in the City or in the ZCF file. If you choose ZCF, ACE will display each ZIP Code in ZIP Code order . If you query the City fil e, your results will be more compressed (fewer records per city) and sorted alphabetically by city name.

The window below shows how ACE displays results on your screen. If you elect to send output to a file, you’ll see the same fields in the same order.

query and another where ACE displays

The on-screen display has a couple of nice features for smaller screens. Click on the “Size” button and ACE scrunches the d isplay horizont ally, to fit more on your screen. You can manually adjust column widths and drop columns yo u’re not interested in, too.

Chapter 5: View the directories with Show

Using Address Line Show for queries in the ZIP+4 file

The Address Line Show program is very similar to Last Line Show, in terms of

you operate it. You can see here the query-setup and results windows.

how Here, too, you have the option to view

results on screen, write an output file, or both.

The main differences are the fields on which you can base your query, and the fields ACE displays in your results. The more query fields you set, the more you focus the search and the fewer records you will have to view.

The window below shows how ACE displays results on your screen. If you elect to send output to a file, you’ll see the same fields in the same order.

Address Line Show displays so much information that it can be a challenge to find enough room on your screen. To use the full area of your screen (that is, to maximize), click on the arrow button at the upper right corner of the window. Also you’ll probably use the “Size” button often, to display results in “scrunch mode.”

ACE User’s Guide

Chapter 6: Suggestion lists

This chapter explains what suggestion lists are, when they occur, and how to respond to them.

This chapter may be easier to understand if you first skim the previous chapter on Show queries. When you know a little about the postal directories and what they contain, it’s easier to understand why and how ACE produces suggestion lists.

ACE Views and ACE Job ACE Views offers suggestion lists when you use ACE in Interactive mode, or

when you use the Quick ACE tool. ACE Job does not support suggestion lists.

PrintForm ACE PrintForm ACE does not support suggestion lists.

ACE Library In the ACE Library, you turn suggestions on or off by a parameter that you set

each time you process an address. See the ACE Library Reference for details.

RAPID RAPID does not support suggestion lists.

Chapter 6: Suggestion lists

Introduction to suggestion lists

Ideally, when ACE looks up an address in the postal directories, it finds exactly one matching record. When the input data is good, ACE should be able to determine exactly one matching record—one combination of city, state, and ZIP Code—in the City/ZCF directories. Then, during the look-up in the national ZIP+4 directory, ACE should find exactly one record that matches the address.

Many times, ACE can do this even when the input data is not complete. In many places, all ACE needs in order to assign an address is the right ZIP Code, house number, and some of the street name.

Input record Output record

Line1 = 1000 vin Line2 = 54603

Breaking ties Sometimes, it’s impossible to pinpoint one matching record in the directory.

Other times, ACE may find several directory records that are near matches to the input data.

When ACE gets close to a match, but not quite close en ough, it assembles a list of the near matches—the suggestions. ACE presents its suggestions, you pick one, and ACE tries again to assign the address.

Prim_Addr City State ZIP10

= 1000 Vine Street = La Crosse = WI = 54601-3474

For example, given the incomplete last line be low, ACE could not reliably choose one of the four cities. But if you choose one, ACE ca n proceed with t he rest of the assignment process.

Input record Possible matches in the City/ZCF directories

Line1= 1000 vine Line2=

lac wi

La Crosse, WI 54601 Lac du Flambeau, WI 54538 Lac Courte Oreilles Indian Reservation, WI 54806 Lac du Flambeau Reservation, WI 54806

The same can happen with address lines. A common problem is a missing directional. In the example below, there is an equal chance that the directional could be North or South. ACE has no basis for guessing one way or the other.

Input record Possible matches in the ZIP+4 directory

Line1 = 615 losey blvd Line2 = 54601

600-699 Losey Blvd North 600-699 Losey Blvd South

A missing suffix would cause the same problem.

Input record Possible matches in the ZIP+4 directory

Line1 = 121 dorn Line2 = 54601

100-199 Dorn Place 100-199 Dorn Street

ACE User’s Guide

A badly misspelled street name could also cause a “tie.”

Input record Possible matches in the ZIP+4 directory

Line1 = Line2 = minneapolis mn

4101 mar

3900-4199 Marschall 55379 4000-4199 Maryland 55427

You’ll need more information

This is not a guessing game

Unresolved suggestions

When ACE produces a suggestion list, you need some basis for sel ecting one of the possible matches. Perhaps you can come up with some additional or better data. For example, perhaps you are using ACE to capture address data while the customer is still on the phone. Or you might be taking data from a consu m er coupon, a little smudged—but if ACE gives you a clue what information is needed, perhaps you could figure out the address.

If you don’t know, and guess, what’s the price of guessing wrong? Consider this address, which needs a directional:

Input record Possible matches in the ZIP+4 directory

Line1 = Line2 = minneapolis mn

5231 penn ave

5200-5299 Penn Ave 5200-5299 Penn Ave

North South

(ZIP 55430) (ZIP 55419)

If you were to guess the directional, and guess wrong, then your mail to this customer would go through the wrong post office, about 10 miles away. At a minimum, it’s going to be badly delayed. It might never be delivered.

If ACE produces a suggestion list, but you have already given all the data available to you, then the process is complete. You may have to accept that the address simply cannot be assigned, or can be assigned only at the ZIP level (a five-digit match).

Interactive programs In our experience, suggestion lists can be useful tools when you are processing

addresses “live” in an interactive program—for example, ACE Views (Interactive Mode or Quick ACE).

When you process a whole file in batch mode, our ACE Views and ACE Job programs run with suggestion lists turned off. Whenever ACE runs into an address that would otherwise invoke a suggestion list, it simply leaves the address unassigned.

Chapter 6: Suggestion lists

Suggestion lists and CASS certification

The 100% barcode rule

There is a strong incentive to use ACE interactively to assign every possible address. The USPS requires complete separation of the automation mail stream from other mail. So mailers have two incentives to barcode every possible piece: First, in order to get automation discounts, you’ll need barcodes. Second, splitti ng the mail into automation and non-automation streams causes hassles and inefficiency in mail preparation. To keep your operation running smoothly, you have to reduce the non-automated portion as much as you can.

CASS rule The USPS does not permit us to generate a 3553 form when suggestion lists are

used in address assignment. The USPS suspects that users may be tempted to guess. Misrouted mail is expensive for the USPS to handle.

Therefore, when you use ACE Views in Interactive mode, you cannot get a 3553 form covering the addresses that you assign. Th e form is available o nly when you operate ACE Views or ACE Job in batch mode.

In the ACE Library , you turn suggestions on or of f by a parameter that yo u set each time you process an address. If you process even one address with suggestions turned on, ACE will prevent generation of the 3553 form. This is true whether or not a suggestion list is actually generated or used.

Tips for using ACE Some customers run their database through ACE Views or Job in batch mode,

then go back and clean up in Interactive mode. Often, suggestion lists will come up during that Interactive session. This can help you to assign the addresses that were not assigned in the batch run.

Interactive mode is available only in ACE Views, not in ACE Job or Remote Views.

Because of the CASS rule explained above, you must run another batch process after your Interactive session. Then you will get a 3553 form that covers your entire mailing database.

Some customers prefer to have ACE perform the bare minimum of processing during that second batch run. That minimum is that ACE must update the ZIP+4 field. All other fields can go untouched, but ACE must post the ZIP+4 code or it will not generate the 3553 form.

100

ACE User’s Guide

Business objects ACE 7.80C User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Contents

Preface

About ACE ACE stands for Address Correction and Encoding. ACE corrects and

About this guide This guide explains what ACE can do and how you can apply it in common

Access the latest documentation

Installation  T o install your ACE software and support file s, follow the instructio ns in our

Operating your software

Official publications  The U.S. Postal Service offers many helpful publications. Ask your

Complete documentation set

What is ACE for?

Address hygiene Most ACE users simply want to make sure that their address data is correct and

Preparation for matching

Data enhancement With ACE you can app end many useful cod es to yo ur records, such as t he coun ty

Postal automation Some companies use ACE to help them qualify for discounted postage on their

Some examples of input and output records

Add postal automation codes

Data hygiene ACE is also used by companies who have no intention of mailing. They simply

Catch flawed or fraudulent addresses

Correct and convert format

Append corrected fields

Rearrange address elements

Puerto Rico (PR) value

Update the input file ACE Views and ACE Job offer the option to updat e t he in put file. For example,

ZIP Code realignment ACE incorporates a feature called ZIP Move, based on a USPS file of the same

Address input and output

The basic set of input and output fields

ACE Views and Job These are called “PW fields.” PW fields and how to set them up are explained in

ACE Library The fields listed here are lines in the ACE address handle. ACE automatically

PrintForm ACE PrintForm ACE always uses the input fields Line1 through Line 6. The exact

Codes and components that ACE can add

Codes When ACE matches an address to the directories, it assigns many codes. Some

Components Many of the components result from address parsing—breaking down address

ACE Views and ACE Job

ACE Library Call ace_get_component() to retrieve these compone nts. Actu al define names a re

PrintForm ACE Some of the fields listed here are available as “DB fields.” (Refer to the

Overview of ACE products

ACE Job

ACE Views ACE Views is a graphical, helpful program for setting up ACE jobs. ACE Views

PrintForm ACE PrintForm ACE is a program for processing print-image files. It is part of the

ACE Library The ACE Library is a tool for programmers. Programmers can use ACE Library

RAPID RAPID stands for Rapid Application Integration Deployment. RAPID l ets you

An in-depth explanation of the assignment process

Terms for address components

ACE uses postal directories

Four files are most important

How ACE works There are many kinds of ACE programs, but no matter how different they may

About the Standardization Style options

City place names

Your options When we undergo CASS testing, we have to prove that ACE can convert place

Unit designator standardization

Your options ACE can standardize unit designators in your choice of two ways:

Style of suffix and directionals

Your options By default , ACE pr oduces abbreviated forms of suffixes (Ave, St, Blvd, and so

Private mail boxes (PMB)

Your options ACE can do one of the following when it recognizes a private mail box:

ACE Views and ACE Job

ACE Library To keep the PMB on the address line, call ace_set_option() with the option

Standardize only assigned addresses

ACE Views and ACE Job

ACE Library Call ace_set_option() with the symbol ACE_OPT_STND_UNASSIGNED_ADDR.

Capitalization (case conversion)

Your options ACE offers three styles of case conversion:

When you have Mixed Case input

Extraneous information on address lines

Your options With ACE, you may choose either to retain or discard extra data in address lines.

About the Remainder field

ACE Views and ACE Job

ACE Library The default style is Strict. Call ace_set_option() if you prefer the Loose style.

Alias and alternate address lines

Your options

ACE Views and ACE Job

ACE Library If you retrieve the processed address line via ace_get_line(), then you may control

Dual address lines

What is a dual address?

One assignment per record

Your options You may express a preference about which type of address ACE should use for