How it Works
Business objects
Loading...
ACE 8.00C
User Manual
736 pgs4.19 Mb0
User Manual
15 pgs560.65 Kb0
User Manual
36 pgs638.24 Kb0
User Manual
200 pgs1.88 Mb0
User Manual
158 pgs1.39 Mb0
User Manual
1 pgs14.11 Kb0
Table of contents
Loading...

Business objects ACE 8.00C User Manual

Download
ACE User’s Guide
ACE 8.00c
September 2009
Contact information Find contact information on the Web at http://service.sap.com.
Copyright information © 2009 SAP® BusinessObjects™. All rights reserved. SAP BusinessObjects owns
USPS information Business Objects is a non-exclusive Interface Distributor Licensee of the United
States Postal Service. The following trademarks are owned by the United States Postal Service: USPS, CASS, Standard Mail, First-Class Mail, DPV, LACS
Link
NCOA
, and United States Postal Services.
Link
,
2
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 need address hygiene or postal coding. This guide explains basic concepts that apply to all forms of ACE.
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 you need, but we don’t delve into the “how to” details. For a complete list of ACE documentation, see “Complete
documentation set” on page 4.
Screen graphics This guide shows graphics of ACE Views setup windows. ACE Views is a
graphical tool for setting up ACE Job Files. Job files are organized into groups of parameters called blocks. Each Views setup window corresponds to a block in the Job File.
Conventions This document follows these conventions:
Convention Description
Bold
Italics
> in menu commands
!
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 substi­tute 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 for­mat: 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
).”
.”
Preface
3
Documentation
Complete documentation set
Cross-product documents
Your complete ACE documentation set includes the following:
! ACE User’s Guide ! ACE Job-File Reference ! ACE Library Reference ! Mover ID User’s Guide for NCOA
NCOA
Link
add-on option)
Link
(if you purchased the Mover ID
You have access to many more documents that are common to our Job File products:
! System Administrator’s Guide ! Views Quick Start Guide ! Database Prep ! Quick Reference for Views and Job-File Products ! Quick Reference for Library Products ! RAPID User’s Guide ! Edjob User’s Guide
Related document For more information about U.S. Postal Service (USPS) rules on address
standardization, refer to USPS publication #28, Postal Addressing Standards. Or, for information about CASS (Coding Accuracy Support Sytem) and MASS (Multiline Accuracy Support System), visit the USPS RIBBS (Rapid Information Bulletin Board System) web site at http://www.ribbs.usps.gov/
.
Access documentation You can access product documentation in different places:
! On your computer. User’s Guides and other manuals for each product that
you have installed are available in the Documentation folder. Choose Start > Programs > Business Objects Applications > Documentation.
Choose from ACE specific documentation or cross-product documentation. Cross-product documentation includes the Quick Reference guides and other general documentation for installing and operating our products.
! On the SAP Corporate Portal. Go to http://help.sap.com/businessobjects/
to access all the latest product documentation.
1. Select All Products at left.
2. Select Data Quality from the All Products drop list.
3. Select ACE from the All Releases drop list.
In addition, ACE Views comes with a built-in help file that provides descriptions of options and steps to perform ACE processes. To access the ACE Views help file, open ACE Views and choose Help > Help Topics.
4
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 NCOA
Link
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 the command line option pwace /lib or pwace -lib to see the installed versions for a complete list 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.
! 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
5
6
ACE User’s Guide

Contents

Chapter 1:
Introduction to ACE ................................................................................... 15
Overview of ACE products............................................................................16
ACE Views ..............................................................................................17
ACE Job File............................................................................................18
ACE Library ............................................................................................18
RAPID .....................................................................................................19
Extra features..................................................................................................20
The CASS bundle ....................................................................................20
For-sale options .......................................................................................20
ACE overview................................................................................................21
Address hygiene.......................................................................................21
Preparation for matching .........................................................................21
Data enhancement....................................................................................22
Postal automation.....................................................................................22
An in-depth explanation of the assignment process.......................................23
Terms for address components ................................................................23
ACE uses postal directories.....................................................................24
Basic directories.......................................................................................24
How ACE works......................................................................................25
Some examples of what ACE does ................................................................26
Add postal automation codes...................................................................26
Data hygiene ............................................................................................26
Catch flawed or fraudulent addresses......................................................26
Correct and convert format......................................................................27
Rearrange address elements.....................................................................28
Puerto Rico (PR) value ............................................................................28
Post back to input.....................................................................................28
ZIP Code realignment..............................................................................29
Address input and output................................................................................30
The basic set of input and output fields..........................................................31
ACE Views and Job File..........................................................................31
ACE Library ............................................................................................31
Codes and components that ACE can add .....................................................32
Codes .......................................................................................................32
Components .............................................................................................32
ACE Views and ACE Job File components ............................................32
ACE Library components........................................................................32
GeoCensus......................................................................................................33
Geographic coding...................................................................................33
ACE forms the basis ...............................................................................33
GeoCensus options: Centroid and Address-Level...................................33
Get the most from the GeoCensus data ...................................................34
Z4Change .......................................................................................................35
How it works............................................................................................35
Contents
7
Use Z4Change to save time.....................................................................35
USPS rules...............................................................................................35
Chapter 2:
Standardization and style options ............................................................. 37
About the Standardization Style options .......................................................38
City place names............................................................................................ 39
Your options............................................................................................ 39
USPS 13-character city name abbreviation ...................................................40
Setting up in Views and Job File.............................................................40
Output fields............................................................................................40
Quick ACE ..............................................................................................40
ACE Library............................................................................................ 40
Non Mailing City setting.........................................................................41
Unit designator standardization .....................................................................42
Your options ...................................................................................... 42
Style of suffix and directionals ...................................................................... 43
Your options .............................................................................. 43
Private mail boxes (PMB).............................................................................. 44
Your options............................................................................................ 44
ACE Views and ACE Job File ................................................................ 44
ACE Library............................................................................................ 44
Standardize only assigned addresses ............................................................. 45
ACE Views and ACE Job File ................................................................ 45
ACE Library............................................................................................ 45
Capitalization (case conversion)....................................................................46
Your options ................................................................................... 46
When you have Mixed Case input ..........................................................46
When you have UPPERCASE input....................................................... 46
Extraneous information on address lines.......................................................47
Your options ........................................................................................ 47
About the Remainder field ...................................................................... 47
ACE Views and ACE Job File ................................................................ 48
ACE Library............................................................................................ 48
Alias and alternate address lines.................................................................... 49
Your options............................................................................................ 49
ACE Views and ACE Job File ................................................................ 49
ACE Library............................................................................................ 49
Dual address lines ..........................................................................................50
What is a dual address? ....................................................................50
One assignment per record...................................................................... 50
Your options............................................................................................ 51
ACE Views and ACE Job File ................................................................ 52
ACE Library............................................................................................ 52
30-character address abbreviation ................................................................. 53
Output fields............................................................................................53
Set up Views............................................................................................53
Quick ACE ..............................................................................................53
ACE Library............................................................................................ 53
Additional options for multiline addresses .................................................... 55
Why are there special options?................................................................ 55
Your options .................................................................................. 55
ACE Views and ACE Job File ................................................................ 55
8
ACE User’s Guide
ACE Library ............................................................................................55
Swapping address lines ..................................................................................56
Your options ..........................................................................................56
Details......................................................................................................57
ACE Views and ACE Job File.................................................................57
ACE Library ............................................................................................57
Combine related components onto the same line...........................................58
Your options ............................................................................................58
Details......................................................................................................59
ACE Views and ACE Job File.................................................................59
ACE Library ............................................................................................59
Updating the ZIP and ZIP+4 in a multiline address.......................................60
ZIP Code location....................................................................................60
Your options ............................................................................................60
Postal discount.........................................................................................60
ACE Views and ACE Job File.................................................................61
ACE Library ............................................................................................61
Guidelines for data entry: U.S. addresses ......................................................62
State abbreviations...................................................................................62
Box numbers............................................................................................62
Rural routes..............................................................................................62
Highway contracts ...................................................................................63
Post office boxes ...............................................................................63
General delivery.......................................................................................63
County roads............................................................................................64
State roads................................................................................................64
Secondary addresses ................................................................................64
Guidelines for multiline addresses .................................................................65
Chapter 3:
Reports ......................................................................................................... 67
Executive Summary .......................................................................................68
Job Summary Report......................................................................................70
Setup Information ....................................................................................70
Auxiliary Files .........................................................................................71
Throughput Summary..............................................................................72
Address Type/Assignment Summary ......................................................73
CASS Qualitative Statistical Summary (QSS) ........................................73
LACSLink Conversion Summary............................................................74
Locatable Address Conversion Summary ...............................................75
Delivery Point Validation Summary (DPV)............................................75
Delivery Point Validation (DPV) Tie-Breaking Summary .....................76
Delivery Point Validation (DPV) Footnote Summary.............................76
GeoCensus Summary...............................................................................77
Postal Code Summary Per File................................................................78
Address Type Summary ..........................................................................79
CASS Qualitative Statistical Summary (QSS) ........................................79
Delivery Point Validation Summary (DPV)............................................79
Delivery Point Validation (DPV) Tie-breaking Summary......................80
Delivery Point Validation (DPV) Footnote Summary.............................81
Error Code Summary...............................................................................81
Standardization Report (a listing of input and processed data)......................82
Limiting the scope and size of your report..............................................82
Contents
9
Error Report (a listing of unassigned records)............................................... 84
Limiting the scope and size of your report..............................................84
Sample report .......................................................................................... 85
Statistics files for custom reporting ............................................................... 86
Job Statistics file ............................................................................................87
File Statistics file ........................................................................................... 93
Address Conversion Statistics (ACS) file....................................................101
Chapter 4:
Postal certification and forms.................................................................. 109
U.S. Postal Service certification programs: CASS and NDI .......................110
CASS.....................................................................................................110
NDI........................................................................................................110
Points to remember................................................................................ 110
Not for interactive programs .................................................................110
CASS self-certification................................................................................111
Static directory names ........................................................................... 111
To obtain static directories....................................................................111
Static directories location......................................................................111
Verification............................................................................................111
ACE Library.......................................................................................... 112
USPS Form 3553 ......................................................................................... 113
How to generate the form......................................................................114
Extended ASCII ....................................................................................114
Data on the form....................................................................................114
Much information is automatic .............................................................114
The National Deliverability Index (NDI) report.......................................... 115
How to generate the form......................................................................115
Report settings.......................................................................................115
Much information is automatic .............................................................116
Chapter 5:
View the directories with Show ............................................................... 117
Query postal directories...............................................................................118
Sample address query............................................................................118
ZIP move component ............................................................................119
Most ACE programs include Show .............................................................120
ACE Views ........................................................................................... 120
ACE Job File and PrintForm ACE........................................................120
ACE Library.......................................................................................... 120
Using Last Line Show for queries in the City/ZCF files............................. 121
Using Address Line Show for queries in the ZIP+4 file .............................122
Chapter 6:
Suggestion lists .......................................................................................... 123
Introduction to suggestion lists....................................................................124
Breaking ties.......................................................................................... 124
You’ll need more information............................................................... 125
This is not a guessing game................................................................... 125
Unresolved suggestions......................................................................... 125
Interactive programs..............................................................................125
Suggestion lists and CASS certification...................................................... 126
The 100% barcode rule .........................................................................126
10
ACE User’s Guide
CASS rule ..............................................................................................126
Tips for using ACE................................................................................126
Chapter 7:
How to save processing time..................................................................... 127
How to set up your computer for top ACE speed ........................................128
Choosing equipment ..............................................................................128
Tips for UNIX and Windows users .......................................................128
Sort the input database by ZIP Code............................................................129
Why? ....................................................................................................129
Why not?................................................................................................129
Options...................................................................................................130
Job setup tips for ACE Views and ACE Job File.........................................131
Job choices that affect speed .............................................................131
Job setup time ........................................................................................131
Tips for running batch jobs ..........................................................................132
Night shift ...................................................................................132
Split and simultaneous...........................................................................132
Chapter 8:
Delivery Point Validation (DPV) ............................................................. 133
Description.............................................................................................134
USPS requirements ......................................................................................135
DPV security..........................................................................................135
Monthly directory updates.....................................................................135
Installing DPV and its directories ................................................................136
DPV directory files................................................................................136
Directory expiration and updates...........................................................136
Performing DPV processing.........................................................................137
DPV output fields ..................................................................................137
Non-CASS mode ...................................................................................137
DPV performance.........................................................................................138
Memory usage .......................................................................................138
Running multiple jobs with DPV ..........................................................138
Windows 98 and ME .............................................................................138
Performing DPV processing on the AIX platform ................................138
Loading DPV directories into system memory............................................139
Job and Views users...............................................................................139
Setting up the Memory Usage block .....................................................139
Job Summary report .....................................................................................140
Job Summary .........................................................................................140
DPV locking.................................................................................................141
Required information in the job setup ...................................................141
Reasons for errors..................................................................................141
DPV false-positive log .................................................................................142
Location for log files .............................................................................142
Log file naming convention...................................................................142
Submit to USPS .....................................................................................142
End users................................................................................................142
Unlocking DPV............................................................................................143
Retrieve code and unlock DPV..............................................................143
DPV No Stats indicators ..............................................................................144
No Stats table.........................................................................................144
Contents
11
No Stats output fields ............................................................................145
DPV Vacant indicators ................................................................................ 146
DPV address-attribute output fields ...................................................... 146
Chapter 9:
Residential Delivery Indicator (RDI)...................................................... 147
What is RDI? ...............................................................................................148
Description ............................................................................................ 148
How does RDI work?............................................................................148
Compatibility......................................................................................... 148
RDI directories............................................................................................. 149
Obtain RDI directories ..........................................................................149
RDI directories ......................................................................................149
Setting up RDI processing ........................................................................... 150
Turn on RDI processing ........................................................................ 150
Specify RDI directory path ...................................................................150
RDI output field ....................................................................................150
Quick ACE ............................................................................................150
RDI in reports .............................................................................................. 151
CASS Statement.................................................................................... 151
Job Summary report ..............................................................................151
Statistics files.........................................................................................151
Chapter 10:
LACSLink.................................................................................................. 153
Overview...................................................................................................... 154
What is LACSLink................................................................................154
Who needs LACSLink .......................................................................... 154
How LACSLink works..........................................................................154
Conditions for LACSLink processing...................................................154
Example................................................................................................. 154
Installing LACSLink and its directories ...................................................... 155
LACSLink directory files......................................................................155
Directory expiration and updates ..........................................................155
Perform LACSLink processing ...................................................................156
LACSLink output fields........................................................................156
LACSLink performance........................................................................ 156
LACSLink locking....................................................................................... 157
Required information in the job setup...................................................157
Reasons for errors..................................................................................157
LACSLink false-positive log.......................................................................158
Location for log files.............................................................................158
Log file naming convention ..................................................................158
Submit to USPS..................................................................................... 158
End users ............................................................................................... 158
Unlocking LACSLink..................................................................................159
Retrieve code and unlock LACSLink ...................................................159
Reports and log file......................................................................................160
Job Summary.........................................................................................160
USPS 3553 Form................................................................................... 161
Pre-LACSLink (APPL) fields......................................................................162
Non APPL fields ................................................................................... 162
12
ACE User’s Guide
Chapter 11:
DSF2 ........................................................................................................... 163
Overview ......................................................................................................164
What is DSF2?.......................................................................................164
ACE’s DSF2 option...............................................................................164
Who needs DSF2? .................................................................................164
Becoming a DSF2 licensee....................................................................165
DSF2 directories ....................................................................................165
Set up DSF2 processing in ACE ..................................................................166
Enable DSF2 processing........................................................................166
Specify the path to DSF2 files...............................................................166
Identify the DSF2 licensee.....................................................................166
Improve processing speed......................................................................167
Include output components....................................................................167
Address attributes.........................................................................................168
DSF2 address-attribute output fields .....................................................168
Walk sequencing ..........................................................................................170
Pseudo sequence ....................................................................................170
Processing notes.....................................................................................170
DSF2 walk-sequence output fields ........................................................171
Reports...................................................................................................171
Statistics files.........................................................................................171
DSF2 Log file ........................................................................................171
Delivery Sequence Invoice report................................................................172
ACE Job Summary report ............................................................................173
Setup Information section......................................................................173
Auxiliary Files section...........................................................................173
DSF2 section..........................................................................................173
DPV Vacant in reports...........................................................................174
Statistics files................................................................................................175
Job and file statistics files......................................................................175
No Stats indicator.........................................................................................176
Vacant indicators..........................................................................................176
Chapter 12:
SuiteLink.................................................................................................... 177
Overview ......................................................................................................178
What is SuiteLink? ................................................................................178
Who needs SuiteLink?...........................................................................178
How SuiteLink works............................................................................178
Install SuiteLink and its directories..............................................................179
SuiteLink directory ................................................................................179
Set up SuiteLink in ACE..............................................................................180
Turn on SuiteLink processing................................................................180
Specify the path to SuiteLink files.........................................................180
Improve processing speed......................................................................180
SuiteLink information in the Job Summary.................................................181
Setup Information section......................................................................181
Auxiliary Files section...........................................................................181
CASS Qualitative Statistical Summary section.....................................181
Statistics files................................................................................................182
File Statistics file ...................................................................................182
ACS file .................................................................................................182
Contents
13
SuiteLink output components ...................................................................... 183
Output information for Customer Service Log (CSL) ..........................183
Appendix A:
Status and error codes............................................................................... 185
Status codes for assigned addresses............................................................. 186
Example................................................................................................. 186
Interpretation .........................................................................................186
What “change” means ........................................................................... 187
ACE Views and ACE Job File .............................................................. 187
ACE Library.......................................................................................... 187
Error codes for unassigned addresses ..........................................................188
Last-line parse error ............................................................................188
Last line look-up errors ......................................................................... 188
Street name look-up errors ................................................................... 190
Primary range errors..............................................................................190
Address-line ties.................................................................................... 191
Other errors ...........................................................................................193
Undeliverable ........................................................................................ 194
14
ACE User’s Guide
Chapter 1: Introduction to ACE
This chapter explains how ACE works and how you can use it to improve the quality of your data. It also contains a brief overview of the ACE products.
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
15

Overview of ACE products

The following ACE products are available.
! ACE Views ! ACE Job File ! ACE Library ! RAPID (not listed in the table below)
ACE products and features
Feature ACE Views ACE Job File PrintForm ACE ACE Library
Batch mode Interactive Suggestion lists
Postal forms Statistical reports and record listings Directory queries
Z4Change option GeoCensus option Delivery Point Validation (DPV) Residential Delivery Indicator (RDI) Early Warning System (EWS) Enhanced Line of Travel (eLOT) Mover ID NCOA
Link
LACS
2
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
# ## # # # ###
16
ACE User’s Guide

ACE Views ACE Views provides a helpful, graphical user interface for setting up ACE jobs.

ACE Views presents easy-to-use, screens with menus, wizards, toolbars, and online 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 quickly.
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 File on another, 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.
Chapter 1: Introduction to ACE
17

ACE Job File ACE Job File is batch software for processing database files. It takes records from

one input database. You can choose either to update the input database or to send ACE output to another database. ACE Job File also produces statistical reports and postal forms.
ACE Job File 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 from a Job File:
BEGIN Auxiliary Files================================== City Directory (path & city10.dir)... = city10.dir
ZCF Directory (path & zcf10.dir)..... = zcf10.dir
ZIP+4 Directory 1 (path & zip4*.dir). = zip4us.dir
To see the entire Job File, see the ACE Job-File Reference.
Start with a command line When your Job File is ready, you start ACE Job File. On most computers you
type a command line; on Windows systems, you may type a command line or double-click the ACE program icon in your file explorer. When ACE Job File 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 File 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. During processing, ACE displays progress messages on your screen. Here is an example of ACE progress messages:
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 Library 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 database­management 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.
18
Library users have access to some information and features that are not available through our ACE applications. However, Library users must provide their own
ACE User’s Guide
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 lets you

integrate technology (ACE, IACE, DataRight IQ, Match/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.
Chapter 1: Introduction to ACE
19

Extra features

Extra features are available for some ACE products (see “ACE products and
features” on page 16). Some are required for CASS and some are optional
features.

The CASS bundle When you purchase the ACE CASS bundle, you receive the following CASS-

required options:
! Delivery Point Validation (DPV) ! LACS
Link
Included in the CASS bundle are the following non CASS-required modules:
! Residential Delivery Indicator (RDI) ! Suite
Link

For-sale options Additional for-sale options include the following:

! GeoCensus ! NCOA ! DSF
Link
2
20
ACE User’s Guide

ACE overview

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 output address data from ACE and process it with BusinessObjects Match/Consolidate program. When Match/Consolidate compares 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 of the same type.
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
Chapter 1: Introduction to ACE
21

Data enhancement With ACE you can append many useful codes to your records, such as flags for

Link
DPV (for valid delivery points), LACS
conversion, move-update, residential indicators, sequence codes, postal codes. For example, ACE can append the following codes:
! DPV ! RDI ! Z4Change ! GeoCensus ! Mover ID NCOA ! LACS ! ANK ! DSF ! Suite
Link
2
Link
Link
Link
For an example of codes assigned to addresses, see “Correct and convert format”
on page 27.
For more information about ACE’s optional features, see “Extra features” on
page 20.

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.
22
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.
We use the same terms as the U.S. Postal Service (USPS). This makes sense when you realize that ACE is subject to many Postal Service rules and regulations.
There is one exception. According to official usage, the ZIP+4 code is a nine-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 f i n d i t m o r e c o n v e n i e n t t o u s e t h e t e r m “ Z I P + 4 ” t o m e a n o n l y t h e l a s t f o u r d i g i t s .
Chapter 1: Introduction to ACE
23

ACE uses postal directories

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.
In the process of looking up someone in the phone book, you might discover that their name is spelled a little differently from the way you thought. 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.

Basic directories ACE needs the directories listed in the table below for processing addresses:

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 720MB.
24
ACE User’s Guide

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 abbreviations, 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 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 confidence 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 Job File).
! Standardized data in discrete components.
! Additional codes and components generated during look-up.
Chapter 1: Introduction to ACE
25

Some examples of what ACE does

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 variety of postal­automation 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 record­matching 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

26
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 corrects the street name and adds the suffix, and adds several address codes to the record. 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= 54601
prim_range prime_name suffix unit_desig sec_range city state zip address prim_addr sec_addr zip4 cart county dpbc aline rec_type city_llidx city_place city_npref chk_digit stat_code err_stat last_line usps_unit zip9 zip10 countyname factype cr_sort_zn fipscode lacscode congress zip_move mother_zip match_9 match_5 match_un std_line1 std_line2
= 1021 = VINE = ST = APT = 5 = LA CROSSE = WI = 54601 = 1021 VINE ST APT 5 = 1021 VINE ST = APT 5 = 3490 =C022 = 063 = 05 = 1021 VINE ST APT 5 = H = LA CROSSE = LA CROSSE = LA CROSSE = 3 = SE9000 = SE9000 = LA CROSSE WI 54601-3490 = APT = 546013490 = 54601-3490 = LA CROSSE = P = D = 55063 = F = 3 = F = 54601 = T = 6 = F = 1021 VINE ST APT 5 = LACROSSE WI 54601-3490
Chapter 1: Introduction to ACE
27

Rearrange address elements

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 CART CR_Sort_Zn
= Rob MacGregor = Sycamore Building = 8 N Market St Ste 318 = Boston MA 02109-1609 = = = 384935 = 9 = Suffolk = C038 = F

Puerto Rico (PR) value

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

Post back to input ACE Views and ACE Job File offer the option to post data back to (or update) the

input file.
28
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
il
pa
62025
19118
Address City State ZIP ZIP4 ZIP_Move
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
29

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 output data. Most people use a combination of them.
Concept Explanation
Multiline The first method is useful when you want to keep output address data in
Discrete The second method is useful when you want the output address broken
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 the way you set the standardization style options.
down into smaller elements than you input. Also, you can retrieve addi­tional 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.
30
ACE User’s Guide

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.
In this manual, we only introduce you to these fields. For full details about these fields see the Quick Reference for Job-File and Views Products.
Each user has their own unique requirements. The task of setting up ACE involves figuring out which fields are most appropriate for the data that you have to process.

ACE Views and Job File

ACE Library ACE Library input fields are lines in the ACE address handle. ACE automatically

ACE Views and Job File input fields are called “PW fields.” For an explanation of PW fields and how to set them up, see the Database Prep manual. If you want, ACE can automatically update 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.
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.
Note: ACE Library does not have a Title field, and does not handle title data.
Chapter 1: Introduction to ACE
31

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 Reference manuals.
There’s an important difference between codes and components and the basic ACE fields. ACE can automatically update the basic fields. ACE does not do anything automatically with codes and components. If you want to use them, then you will have to select and handle them yourself, manually.

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 Views and ACE Job File components

ACE Library components

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).
Call ace_get_component() to retrieve these components. Actual define names are listed in the Quick Reference for Libraries.
32
ACE User’s Guide

GeoCensus

GeoCensus offers geographic and census coding for enhanced sales and marketing analysis.

Geographic coding With GeoCensus, ACE can append latitude, longitude, and census codes such as

Census Tract/Block and Metropolitan Statistical Area (MSA) to your records, based on ZIP+4 codes. MSA is an aggregation of counties into Metropolitan Statistical Areas assigned by the U.S. Office of Management and Budget. You can easily assign the geographic and census codes using ACE.
Through ACE, you can apply the GeoCensus codes during address standardization and ZIP+4 assignment for simple, “one-pass” processing. If you already have good ZIP and ZIP+4 codes in your database, the GeoCensus Option offers a “quick coding” feature for geographic and census coding that uses only the existing ZIP+4 for the match.
The data in GeoCensus is based on geographic information from Tele Atlas. Tele Atlas is nationally recognized for the accuracy of their geo-positional data. Their data has been used in navigational systems, and is now being integrated in automobiles sold across the United States.
The geographical data is based on information gathered by the Census Bureau. Tele Atlas enhances the data in the U.S. Census Bureau’s TIGER/Line (Topologically Integrated Graphic Encoding and Referencing) file to improve accuracy and add demographic coding. TIGER/Line is a registered trademark of the U.S. Department of Commerce, Bureau of the Census.

ACE forms the basis

GeoCensus options: Centroid and Address­Level
ACE cannot, by itself, append demographic data to your records. ACE simply lays the foundation by giving you Census coordinates. To append demographic information, you need a demographic database from another vendor. When you get that, we suggest that you use one of our Match/Consolidate programs to match your records to the demographic database and transfer the demographic information into your records. (In technical terms, you would use the MSA and Census block/tract information as match fields, then use the Group Posting feature to transfer income and other information. See the Match/Consolidate documentation for details and examples of group posting.)
Likewise, ACE does not draw maps. However, you can use the latitude and longitude assigned by ACE as input to third-party mapping software. Those programs enable you to plot the locations of your customers and filter your database to cover a particular geographic area.
Two GeoCensus options are available:
! Address-Level. Latitude and longitude are based on an individual address.
ACE assigns to the individual dwelling or not at all.
! Centroid. Latitude and longitude are based on the 9-digit ZIP code, so
precision of assignment is typically at the block-face level. In some areas where the data is less extensive, the precision of assignment may fall back to the 7-digit or 5-digit level.
Chapter 1: Introduction to ACE
33

Get the most from the GeoCensus data

You can combine GeoCensus with the functionality of mapping software to view your geo-enhanced information. It will help your organization build its sales and marketing strategies. Here are some of the ways you can use the GeoCensus data, with or without mapping products.
Information type
How GeoCensus can help
Market analysis You can use mapping applications to analyze market penetration, for
instance. Companies striving to gain a clearer understanding of their markets employ market analysis. This way they can view sales, mar­keting, and demographic data on maps, charts, and graphs. The result is a more finely targeted marketing program. You will under­stand both where your customers are and the penetration you have achieved in your chosen markets.
Predictive mod­eling and target marketing
You can more accurately target your customers for direct response campaigns using geographic selections. Predictive modeling or other analytical techniques allow you to identify the characteristics of your “ideal” customer. This method incorporates demographic information used to enrich your customer database. From this analy­sis, it is possible to identify the best prospects for mailing or tele­marketing programs.
Media planning For better support of your advertising decisions, you may want to
employ media planning. Coupling a visual display of key markets with a view of media outlets can help your organization make more strategic use of your advertising dollars.
Territory man­agement
GeoCensus data provides a more accurate market picture for your organization. It can help you distribute territories and sales quotas more equitably.
Direct sales Using GeoCensus data with market analysis tools and mapping soft-
ware, you can track sales leads gathered from marketing activities.
34
ACE User’s Guide

Z4Change

The ACE option called Z4Change is based on a USPS directory of the same name.

How it works The Z4Change directory lists all the ZIP and ZIP+4 codes in the country. A

record in this file is tagged if it has changed within the last 12 months. The change might be a postal-code change (ZIP, ZIP+4, or CART), or even a change in the standardized form of the address line or city name.
When you use Z4Change, ACE processes records differently. First, ACE checks the ZIP and ZIP+4 in the input record. If both are available, ACE looks them up in the Z4Change file.
Most often, the matching Z4Change record will show that the address is not affected by any change. In that case, there is no need for further processing and ACE goes on to the next record. That’s how you get a performance benefit from Z4Change.
Note: ACE does not send records to the output file that do not need to be updated by Z4Change. Therefore, If you want to send all of your input records to output, run ACE without Z4Change processing enabled.
If the Z4Change file indicates that the address is affected by some change, then ACE performs its normal process (parsing the address data and looking it up in the City, ZCF, and ZIP+4 directories).

Use Z4Change to save time

Using the Z4Change Option can save some customers a lot of processing time, compared with running all records through the normal ZIP+4 assignment process.
Z4Change is most cost-effective for databases that are large and fairly stable—for example, databases of regular customers, subscribers, and so on. In our tests, based on files in which five percent of records were affected by a ZIP+4 change, total batch processing time was just one third of a normal ACE job.
When you are using ACE interactively—that is, processing one address at a time—there is less benefit from using Z4Change. ACE Views, when operated in Interactive mode, does not use Z4Change.

USPS rules Use Z4Change to update a database that has previously been put through a full

ACE process. The USPS requires that the mailing list be put through a complete assignment process every three years.
Chapter 1: Introduction to ACE
35
36
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 possible that in the future, the addresses use here may assign differently.
Chapter 2: Standardization and style options
37

About the Standardization Style options

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. ACE doesn't require this, nor does the USPS. 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 Standardization Style option will apply. For example, within the Address component, the abbreviated or spelled-out style of suffix and directionals is controlled by the Standardization Style options. The same is true for the place-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 types of components, each with a slightly different name.
Product Description
ACE Views and ACE Job File
ACE Library The information in this chapter will help you set parameters when you
The information in this chapter will help you set parameters in the Standardization Style and the Multiline Style blocks.
Where we refer to “default” settings, we mean the initial settings that we provide in the master Job File ( new Job File in ACE Views. Please do not interpret “default” to mean that you can leave a parameter blank, because all the parameters dis­cussed here require some entry.
call ace_set_option() or set up your ace_options_config_file (
aceopts.cfg
).
master.ace
) or when you start a
38
ACE User’s Guide

City place names

A place name is a geographical name for an area that does not have its own post office. Place names are an issue because, according to the U.S. Postal Service, the city name printed on a mail piece is supposed to be the city where the post office is located. This is not necessarily the city where the recipient lives. Yet in the minds of many people, their mail should be addressed to the city where they live. 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 the Los Angeles post office. Of course, Hollywood residents might prefer that their vanity 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 to either preserve place names or to convert them to postal city names by setting the Non Mailing City Name parameter to Preserve or Convert:
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.
Hollywood
as output. (default setting)
Hollywood
as input, ACE pro-
as input,
Note: ACE ignores the Non Mailing City Name setting when the Assign City from Input/LL Idx option is enabled.
Chapter 2: Standardization and style options
39

USPS 13-character city name abbreviation

The USPS has a 13-character city name for many cities in the city/state file. With CASS Cycle M, ACE is required to provide a 13-character city name, upon your request, if one exists. If the input city name is not valid (for example, it is a non mailing city name), ACE relies on other settings in the job to determine what to output for city.
When the Use USPS City Abbreviation option is activated in your job, and if the city name is longer than 13 characters, the software will return an abbreviation that is 13 characters or less. If the city name is already 13 characters or less, the software will not abbreviate it.
This option isn’t required for CASS mailings, but if you are testing for CASS certification, you must enable this option.
This option is available in ACE Job File, Views, Quick ACE, and Library.

Setting up in Views and Job File

The parameter, Use USPS City Abbreviation, is found in the Standardization Style block. Enable the option by setting the parameter to Y, or by selecting it in Views. The default setting is N, or not selected in Views.
If you have a multiline input, set the Standardize parameter in the Multiline Style block to City_St or Both.

Output fields If you have chosen to abbreviate the city name, the abbreviated city name appears

in these output fields.
Field name Length Description
AP.Last_Line 28-43 Contains the abbreviated city name. If a 13-character city
AP.Std_Line## up to 60

Quick ACE The option appears in the Options window in Quick ACE.

ACE Library The ACE_OPT_STND_CITY_ABBR supports the 13-character city

abbreviation does not exist, the full city name is output to the Last_Line and Std_Line## fields when you include them in your output setup.
abbreviation. Use it with the ace_set_option() or ace_get_option().
40
ACE User’s Guide
Option Value Description
ACE_OPT_STND_CITY_ABBR
T/F Provides an abbreviation of the city name
if it exceeds 13 characters and if one is available from the USPS.

Non Mailing City setting

When Use USPS City Abbreviation is enabled, it takes precedence over a setting of Preserve for the Non-Mailing Cities parameter.
For example, in the job setup below, ACE outputs the 13-character city abbreviation (if one exists) even though the Non-Mailing Cities parameter is set to Preserve and the Assign City From Input/LL Idx is set to N.
Assign City From Input / LL Idx (Y/N) = N Non-Mailing Cities (CONVERT/PRESERVE) = Preserve
Use USPS City Abbreviation (Y/N)..... = Y
Note: The software will only override the Non-Mailing Cities parameter if the non-mailing city name is over 13 characters. If the non-mailing city name is over 13 characters, then ACE overrides the Preserve setting and converts the city name to the mailing name. If the mailing name is also over 13 characters, then the abbreviated city name is returned.
Also in this job setup, when the non-mailing city is 13 characters or less, and the Assign City from Input/LL IDX parameter is set to N, the non-mailing city name is preserved.
Example In this example, a 13-character city abbreviation exists and the Use USPS City
Abbreviation parameter is set to Y.
Input address:
7311 BLACK OAK LN YOSEMITE NATIONAL PARK CA 95389
Output address:
7311 BLACK OAK LN YOSEMITE NTPK CA 95389-9102
Chapter 2: Standardization and style options
41

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 With the Unit Designator parameter, ACE can standardize unit designators in

your choice of three ways:
Option Description
# ACE converts the unit designator to the pound sign.
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.
42
ACE User’s Guide

Style of suffix and directionals

Your options By default, ACE produces 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 by setting the Suffix Style parameter. Your options are:
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
When you select the Short or Long style for Directional Style, it may 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
43

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 below shows forms of input that ACE recognizes:
! PMB ! P M B ! PRIVATE MB ! PRIVATE MAIL ! PRIVATE MAILBOX ! PRIVATE MAIL BOX
These may be followed by a symbol such as the pound sign (#). All forms will be standardized to “PMB” followed by a space and the box number.

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 File

To keep the PMB on the address line, activate the Append PMB to Address Line parameter in the Standardization Style block. By default it is set to Y in Job File or selected in Views.
To separate the PMB into a separate field, turn off this option and post the output field AP.NP_SecAddr to your output file. 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 box number in separate fields, post the 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.
To break the PMB off 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 the box number in separate fields, retrieve the output components ACE_NP_UNIT and ACE_NP_SRANGE. Both fields have a maximum length of 10 characters plus null.
44
ACE User’s Guide

Standardize only assigned addresses

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

ACE Views and ACE Job File

When an address is not assigned, ACE will produce non standardized 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
The default setting is
FALSE. When an address is not assigned, ACE will produce
TRUE or FALSE.
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 standardizing any unassigned addresses.
Chapter 2: Standardization and style options
45

Capitalization (case conversion)

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 your input data is in mixed case and you choose Upper and Lower for ACE’s Casing setting, ACE leaves your name and firm data as they were input, and standardizes only the address fields.
Example: This example shows how an address with mixed case data is affected when the Casing setting is set to Upper and Lower.
Input address:
boB mcFARland mY vEry oWn Company pO box 9222 2900 maiN sT La cRosse WI 54601
Output address:
boB mcFARland mY vEry oWn Company PO box 9222 2900 Main St La Crosse WI 54601-3990
! Name and firm data stays the same. The mixed case of the data is unchanged. ! Address data is standardized to correct mixed case.
When you have UPPERCASE
46
ACE User’s Guide
input
You might run into occasional capitalization errors if you ask ACE to convert
UPPERCASE to Mixed Case. ACE is good at this, but Mixed Case is often
from 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).
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 MCA RECORDS and MCA is not listed in the dictionary, the result would be Mca Records. For this situation, we recommend that you use our DataRight IQ 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 ACE matches an address line to the ZIP+4 directory, ACE may find that your input includes more information than the directory says is necessary. For example:
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 fact, when we undergo CASS testing, we have to prove that ACE can do this. However, you are not required to strip off the additional data when processing your own records. Most ACE users prefer to retain additional information, because it may be useful for internal mail routing.

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

through settings in the Address Line Standardization parameter:
Option Description

About the Remainder field

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.
Note: 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.
When ACE removes “non-address” type data from an address line, you still can retrieve that information through an output component called Remainder.
Remainder has 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
47

ACE Views and ACE Job File

To select loose or strict standardization, 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.
48
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 addresses (usually streets), not secondary addresses or last lines.
For example, here in La Crosse, there’s a bank at the Valley View Mall, which is located on State Road 16. The ZIP+4 directory record indicates that “Valley View Mall” and “State Road 16” are aliases for each other, and that “State Road 16” is the form that the USPS prefers. In other words, though the bank might give its address as “3500 Valley View Mall,” the USPS prefers that this address be standardized to “3500 State Road 16.”

Your options

Option Description
Convert By default, ACE converts input addresses to USPS-preferred aliases. This is
the CASS compliant option.
Preserve You have the option to turn off alias conversion for everyday processing.
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.

ACE Views and ACE Job File

To control whether ACE will convert alias addresses, go to the Standardization Style block and set the Address Line Alias parameter to Convert to output the USPS-preferred address, or to Preserve to keep the input address as is (non­CASS).

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

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
49

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:
RR1 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 through ACE if you want to process both addresses.
! Permanent address (parents):

One assignment per record

7600 W Main St Niles IL 60714
! At-school address:
6 Hairpin Dr South Illinois Univ IL 62026
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. We call the first one the assigned address, and the other the dual address. 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.
50
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:
100 Main St, PO Box 297
! Assigned to PO box:
PO Box 297, 100 Main St
Swap address lines If you turn on the software’s Swap Lines feature (see “Swapping address lines”
on page 56), ACE will move the assigned address into position immediately
above the last line. For example:
! Assigned to PO box:
ABC Company, Inc. 4439 Mormon Coulee Rd
PO Box 2589 La Crosse WI 54602-2589
! Assigned to street address:
ABC Company, Inc. PO Box 2589
4439 Mormon Coulee Rd
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 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
Position
is the default option. ACE will select an address line based on how 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
lower left
corner. That might be either the mailing or the street address; it depends entirely on how the data was entered. If the first address fails assignment, ACE will try the second address.
Even though you might print both address 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.
Chapter 2: Standardization and style options
51
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.
Tip: 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.
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 File

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 Position. 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.
52
ACE User’s Guide

30-character address abbreviation

CASS requires that ACE has the option to output addresses of 30 characters or less when the output address will exceed 30 characters. The abbreviated version of the address only occurs when the output address is greater than 30 characters. If the output address is 30 characters or less, the street name is not abbreviated.
This is optional, but the option must be enabled while performing CASS testing.
If the Use USPS street abbreviation parameter is set to Y (selected in Views), it affects the following address components on output:
! Suffix Style: The style will be short. ! Directional Style: The style will be short. ! Address Line Alias: The setting of Preserve may be overridden.

Output fields The following output fields hold the abbreviated form of the address if one is

available:

ACE Views/Job File ACE Library

Address ACE_ADDRESS
Prim_Addr ACE_PRIM_ADDR
Aline ACE_ALINE
Std_Line1-12 (multiline) ACE_STD_LINE1-12

Set up Views Set the 30-character address abbreviation in your job setup in the Standardization

Style window. Select the parameter, Use USPS Street Abbreviation to activate it.
If you have a multiline input, the Standardize parameter in the Multiline Style block needs to be set to Address or Both.

Quick ACE The Use USPS Street Abbreviation option is present in the Quick ACE tool when

you click the Options button.
ACE Library Enable the 30-character street abbreviation option in ACE Library by using the
following option with the ace_set_option( ) or ace_get_option( ):
Option Value Description
ACE_OPT_STND_STREET_ABBR T/F Standardizes addresses that contain
30 characters or less, if one is avail­able.
Chapter 2: Standardization and style options
53
Example In this example, the input address contains more than 30 characters. Therefore,
the Use USPS Street Abbreviation option setting of Y overrides the Address Line Alias option setting of Convert or Preserve. The 30-character or shorter alias address is returned.
Input address:
100 Tyngsboro Business Pk Unit 1 Tyngsboro MA 01879
Output address:
100 Business Park Dr Unit 1 Tyngsboro MA 01879-1071
54
ACE User’s Guide

Additional options for multiline addresses

The rest of this chapter applies to you only if you are processing multiline or dual addresses. If you’re not sure, check the examples below to see if they resemble your records, even loosely.

Why are there special options?

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. 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.
How to control standardization of multiline address
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.

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

from. If you are processing a dual 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 60.)
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 File

By default, ACE fully standardizes as much as possible (option is set to Both). Open the Multiline Style block and set the Address/City/State Standardization parameter to set your preference.

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

call ace_set_option().
Chapter 2: Standardization and style options
55

Swapping address lines

By default, ACE rearranges address lines to conform with USPS guidelines. ACE also eliminates any blank lines within the multiline address. This feature is called Swap Address Lines. Here is an example of how ACE swaps address lines:
As you can see, ACE moves the primary address into position immediately above the last line. The secondary address is placed above the primary, and other lines are placed above the secondary address. ACE also repositions the last line in order to eliminate the blank line.

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

These examples show the effects of Combine Lines (next page) and Swap Address 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.
Before
Line1 Line2 Line3 Line4 Line5 Line6
Bob Smith 2100 Market Street Suite 202 Sycamore Building Boston, MA 02109
After
Bob Smith Sycamore Building
100 Market St Ste 202 Boston MA 02109
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 100 Market Street Suite 202 Sycamore Building Boston, MA 02109
After
Bob Smith Sycamore Building 100 Market St Ste 202 Boston MA 02109
56
ACE User’s Guide

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 shorter 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 place the dual address above the assigned address.

ACE Views and ACE Job File

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

By default, line swapping is turned on. To set your preference, go to the Multiline Style block and set the Swap Address Lines parameter.
Chapter 2: Standardization and style options
57

Combine related components onto the same line

ACE can rearrange some components within multiline addresses. This feature, called Multiline Combine Lines, results in a more compact address that is easier to read.
! Original data:
Line 1 Bob Smith Line 2 100 Market Street Line 3 Apt 202 Line 4 Boston MA Line 5 02109
! Combined lines:
Line 1 Bob Smith Line 2 100 Market St Apt 202 Line 3 Boston MA 02109
Note: ACE handles the blank lines if you turn on the Swap Lines feature.

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

from. If you are processing a dual 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
secondary address on the same line as the primary. Do not combine the last-line data.
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:
Record 1 Record 2
Name Bob Smith Name Bob Smith
Line1 100 Market Street Line1 100 Market Street
Line2 Apt 202 Line2 Apt 202
City Boston Last_Line Boston MA 02109
State MA
58
ZIP 02109
ACE User’s Guide

Details You do not have to standardize your address data to use Combine 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.

ACE Views and ACE Job File

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().
Chapter 2: Standardization and style options
59

Updating the ZIP and ZIP+4 in a multiline address

ZIP Code location 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 where these codes will appear (see below). So you can’t give ACE specific instructions about exactly where to place the updated ZIP and ZIP+4. Instead, you tell ACE whether you want the ZIP and ZIP+4 updated, by setting the Multiline Assignment features. Internally, ACE “knows” where the ZIP and ZIP+4 appear in each address, so it can update them for you.
Record 1 Record 2 Record 3
Line1 John Smith Line1 Acme Tools Line1 J. Smith, Acme Tools
Line2 Acme Tools Line2 ATTN J. Smith Line2 308 2nd Ave, #152
Line3 Suite 152 Line3 308 2nd Ave #152 Line3 Ames, IA
Line4 308 2nd Ave Line4 Ames IA
Line5 Ames IA

Your options You have two separate options so that ACE can be a little more conservative with

50014
Line5 Line5
50014
Line4
50014
ZIP Codes.
Option Description
Include/Update ZIP Code
Include/Update ZIP+4?
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 multi­line address block. The assigned ZIP+4 is still available as a separate component.

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

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.
60
ACE User’s Guide

ACE Views and ACE Job File

By default, ACE updates the ZIP and adds the ZIP+4 to multiline addresses. To set your preference, go to the Multiline Style block and set these two parameters: Include ZIP and Include ZIP+4.
When ACE cannot assign a ZIP, it passes along the original ZIP. The logic here is 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 ACE 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().
Chapter 2: Standardization and style options
61

Guidelines for data entry: U.S. addresses

When data-entry staff prepare addresses that will be processed by ACE, they can use any of the formats listed below. If data is typed in other formats, ACE may not be able to interpret data correctly. We offer these guidelines to help make your ACE processing more successful.
Note: For consistency, all formats below are shown in upper case. You can use any combination of upper and lower case, however, because ACE ignores the case of input data.

State abbreviations If you store state data in a separate field, use official USPS two-letter

abbreviations (MN, CA). ACE recognizes some other abbreviations (Minn., Calif.) when they appear in a Last_Line field (combined city-state-ZIP) or in a multiline address. However, it is much better to use standard USPS state abbreviations.

Box numbers When an address includes a box number on a rural or contract route, the box

number may either follow or precede the route or contract number. ACE accepts box numbers in two formats:
! BX 59A ! BOX 59A
Box numbers are standardized to: BOX 59A

Rural routes ! R 2

! RTE 2 ! R2 ! RT 2 ! RR2 ! RD 2 ! RR 2 ! RD2 ! RR 2 ! RFD 2 ! R.R. 2 ! RURAL 2 ! ROUTE 2 ! RURAL ROUTE 2
Rural routes are standardized to: RR 2 Rural routes with a box number are standardized to: RR 2 BOX 59A
62
ACE User’s Guide

Highway contracts ! CONTRACT 3

! HIGH CONTRACT 3 ! HGWY CONTRACT 3 ! HIGHWAY CONT 3 ! HGWY CONT 3 ! HWY CONT 3 ! H. C. 3 ! HY CONT 3 ! H.C. 3 ! HY CONTRACT 3 ! H CONTRACT 3 ! HIGHWAY CONTRACT 3 ! H CONT 3 ! HIGH CONT 3 ! HCR 3 ! STAR ROUTE 3 ! HC 3
Highway contracts are standardized to: HC 3 Highway contracts with a box number are standardized to: HC 3 BOX 43

Post office boxes ! P O BOX 29

! POST BX 29 ! BOX 29 ! POST OFFICE BOX 29 ! P.O . B OX 29 ! POSTOFFICE BOX 29 ! BX 29 ! POST OFFICE BX 29 ! P BOX 29 ! POSTOFFICE BX 29 ! P BX 29 ! POSTAL BOX 29 ! PO BX 29 ! POSTAL BX 29 ! PO BOX 29 ! POST BOX 29 ! PO DRAWER 29
Post office boxes are standardized to: PO BOX 29
General delivery ! GENERAL DEL
! GEN D ! GENERAL D ! G DELIVERY ! GEN DELIVERY ! G DEL ! GEN DEL ! GENERAL DELIVERY

General deliveries are standardized to: GENERAL DELIVERY

Chapter 2: Standardization and style options
63

County roads ! COUNTY RD 20

! CTY RD 20 ! COUNTY HWY 20 ! COUNTY TRUNK 20 ! COUNTY TRK 20 ! COUNTY 20
County roads are standardized to: COUNTY RD 20

State roads ! STATE 20

! STATE ROAD 20 ! STATE HWY 20 ! ST ROAD 20 ! ST RD 20 ! STATE RD 20
State roads are standardized to: STATE RD 20

Secondary addresses ACE processes secondary addresses more reliably when you furnish a

recognizable unit designator such as # or APT, SUITE, ROOM, FLOOR, BLDG, and so forth. For example, “77 County Road #11” is better input than just “77 County Road 11.”
If you use a pound sign (#) to mark apartment, suite, or room numbers, you do not need a space between the # and the number. However, a space is necessary if you use words or abbreviations. For example, ACE will correctly interpret “APT 1,” but not “APT1.”
Note: See USPS Publication 28 for a complete listing of valid unit designators.
64
ACE User’s Guide

Guidelines for multiline addresses

You may or may not have any control over the quality and layout of input address data. To the extent that you do, please ensure that input data conforms to the guidelines listed below.
Generally, address components should appear in the same arrangement that you would use on an address label. This will ensure that ACE can parse the data most reliably and efficiently.
1. Name. Place name data above the company (firm) line. Don’t place it beside
or below the company (firm) name.
2. Company. If you have a firm or company name, be sure to place it
immediately above the mailing address line. Ace uses firm names to assign more specific ZIP+4 codes to firms.
3. Address Line. Place the primary address immediately above the city-state-
ZIP line.
If there is a secondary address (an apartment or suite number) field, place it above or to the right (never to the left) of the primary address.
When you have two address lines (for example, a street address and a PO box), place the delivery address immediately above the city-state-ZIP line.
4. Last Line. The ZIP Code must be on the last valid line of address data. It can
be followed by a country name. If at all possible, place the ZIP Code on the same line as the city and state. If you have an input ZIP+4 code, place it on the same line and to the right of the ZIP Code.
City and state fields must be on the same line. They may be on the same line as the ZIP Code or on the line above it. Use the arrangement city-state-ZIP. Do not use state-ZIP-city!
5. Country. If there is a country name, place it on the bottom line, by itself. Do
not place city, state, or postal code on the same line with country name.
6. Unused lines. You do not have to use all 12 lines. Also, it does not matter if
you fill the lines from the top down or bottom up.
7. Max length. All lines should be the same length. The maximum length is 60
characters.
Chapter 2: Standardization and style options
65
66
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 Views and ACE Job File offer all of the reports 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. You can produce the ACS statistics file with ACE Library. See “Address Conversion Statistics (ACS)
file” on page 101 for details.
Chapter 3: Reports
67

Executive Summary

ACE offers an Executive Summary Report. This is a concise statement of the most crucial information about your ACE job. It is designed 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
68
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 number 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 Processed. 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 require LACS conversion whether 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
69

Job Summary Report

We recommend that you produce a Job Summary for every ACE job. It is a concise statement of your job setup, input data, and results.
JOB SUMMARY ACE <version> PAGE 1
------------------------------------------------------------------------------
SETUP INFORMATION ------------------------------------------------------------
JOB NAME /MOUNTS/TESTCOMP/ACE/JOBFILE/TESTCASES/NCOA/ NCOAL020.ACE JOB DESCRIPTION NCOA/LINK TESTING JOB OWNER ACE PT TEAM
STARTING RECORD NUMBER 1 ENDING RECORD NUMBER 200
ASSIGN WHICH RECORDS: ALL ASSIGNMENT MODE: ASSIGN ENABLE NON-CASS: N GEO MODE: N/A ENABLE EWS: N ENABLE ELOT: N ENABLE DPV: Y ENABLE RDI: N 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 ENABLE STREET ABBR: NO ENABLE CITY ABBR: NO
ASGN CITY BY INP/LLIDX: YES UNVERIFIED POSTAL CODES: ERASE NON-MAILING CITY NAMES: CONVERT CASE STANDARDIZATION: UPPER/LOWER 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

Setup Information The first section of the Job Summary shows how you set up the job.

PW Fld Standardization This indicates whether or not you chose to update the input file. If you did not
choose to 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.”
70
ACE User’s Guide
AUXILIARY FILES ---------------------------------------------------------------
FILE DESCRIPTION DATE FILE NAME
------------------------- ---------- ----------------------------------------­ FIRM LINE DICTIONARY 01/2007 ...8_64/EXECUTABLE/POSTWARE/ACE/FIRMLN.DCT ADDRESS LINE DICTIONARY 01/2007 ...8_64/EXECUTABLE/POSTWARE/ACE/ADDRLN.DCT LAST LINE DICTIONARY 01/2007 ...8_64/EXECUTABLE/POSTWARE/ACE/LASTLN.DCT CAPITALIZATION DICTIONARY 01/2007 ..._8_64/EXECUTABLE/POSTWARE/ACE/PWCAS.DCT ZCF DIRECTORY 03/2009 /MOUNTS/TESTCOMP/DEVDIRS/US/ZCF10.DIR CITY DIRECTORY 03/2009 /MOUNTS/TESTCOMP/DEVDIRS/US/CITY10.DIR ZIP+4 DIRECTORY 1 03/2009 /MOUNTS/TESTCOMP/DEVDIRS/US/ZIP4US.DIR ZIP+4 DIRECTORY 2 REVERSE ZIP+4 DIRECTORY 03/2009 /MOUNTS/TESTCOMP/DEVDIRS/US/REVZIP4.DIR REVERSE SOUNDEX DIRECTORY 03/2009 /MOUNTS/TESTCOMP/DEVDIRS/US/ZIP4US.REV ZIP4 SHS DIRECTORY 03/2009 /MOUNTS/TESTCOMP/DEVDIRS/US/ZIP4US.SHS EWS DIRECTORY ELOT DIRECTORY DPV DIRECTORY 03/2009 ...ACE/JOBFILE/PLATFORMS/SOL_8_64/DIRS/DPV RDI DIRECTORY LACSLINK DIRECTORY 03/15/2009 ...BFILE/PLATFORMS/SOL_8_64/DIRS/LACS_LINK SUITELINK DIRECTORY Z4 CHANGE DIRECTORY NCOALINK DIRECTORY 05/08/2006 ...BFILE/PLATFORMS/SOL_8_64/DIRS/NCOA_LINK NAME PARSING FILES N/A ...S/SOL_8_64/EXECUTABLE/POSTWARE/NCOALINK CENTROID GEO DIR

Auxiliary Files The next section lists the auxiliary files and the locations that you set up in the

job.
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.
The Auxiliary Files section may extend to page 2, which also contains the Throughput Summary.
Chapter 3: Reports
71
THROUGHPUT SUMMARY ------------------------------------------------------------
ZIP SORT START TIME: ZIP SORT END TIME: RECORDS SORTED PER HOUR:
BATCH START TIME: 03/10/2009 22:36:37 PM CDT BATCH END TIME: 03/10/2009 22:37:16 PM CDT RECORDS ASSIGNED PER HOUR: 18461
TOTAL RECORDS PROCESSED PER HOUR: 18000 TOTAL PROCESSING TIME: 00:00:40
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
---- ------------------- --------- -------- -------- -------- -------- -------­ /MOUNTS/TESTCOMP/ACE/JOBFILE/INPUT/NCOA/NCOANEW2.DBF 07-10-2006 09:48:30 DBASE3 2979 0 2779 0 200
ADDRESS TYPE SUMMARY ASSIGNMENT SUMMARY COUNT % COUNT %
------------------------------------- ------------------------------------­ STREET 13 43.33 ZIP CODES 199 99.50 PO BOX 4 13.33 ZIP+4 CODES 30 15.00 HIGH RISE 7 23.33 DPB CODES 30 15.00 RURAL ROUTE 0 0.00 CARRIER ROUTE CODES 176 88.00 FIRM 0 0.00 LOT CODES 0 0.00 GENERAL DELIVERY 6 20.00 LOT ORDER CODES 0 0.00 MILITARY 0 0.00 COUNTY CODES 199 99.50 UNIQUE 0 0.00 ASSIGNED/NO DELIVERY 146 73.00 FOREIGNS 0 0.00 OTHERS NOT ASSIGNED 24 12.00 LACS CONVERTIBLE 3 1.50 ADDR LEVEL GEO CODES 0 0.00 CENTROID GEO CODES 0 0.00 RDI MATCHES 0 0.00 MOVER ID MATCHES 46 23.00 ANKLINK MATCHES 0 0.00
------------------------------------­ TOTAL ZIP+4 CODES: 30 100.00

Throughput Summary

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.
Database Records column This shows the total number of records in the input file. The Starting and Ending
Record parameters are not reflected.
Deleted Records column 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.
72
ACE User’s Guide
Filtered Records column 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 column
Net Input Records column This shows the number of records that ACE tried to assign.

Address Type/ Assignment Summary

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.
After the Throughput Summary is a summary that provides more details on your input records and how they fared in the assignment process. At the bottom, this section provides an overview about how your records were output.
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 not reflect
what you may or may not have actually posted to your input 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 not equal the total number of records in the database. See the Existing File parameter in the Post to Output File block.

CASS Qualitative Statistical Summary (QSS)

CASS QUALITATIVE STATISTICAL SUMMARY (QSS) (PERCENTAGES BASED ON # OF RECORDS PASSING THE FILTER) COUNT % COUNT %
------------------------------------- -------------------------------------­ HIGH RISE DEFAULT 7 3.50 RURAL ROUTE DEFAULT 0 0.00 HIGH RISE EXACT 0 0.00 RURAL ROUTE EXACT 0 0.00 EWS MATCH 0 0.00 LACS CONVERTIBLE 3 1.50 DPV CONFIRMED 30 15.00 RDI 0 0.00 LACSLINK CONVERSIONS 2 1.00 SUITELINK MATCHES 0 0.00
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 at the job level. Later in the Job Summary, a similar section appears but it is reporting at the file level.
Chapter 3: Reports
73
Link
LACS Summary
Conversion
LACSLINK CONVERSION SUMMARY-----------------------------------------------------
ADDRESS TYPE AFTER LACSLINK PRE- HIGH- RURAL GENERAL LACSLINK STREET PO BOX RISE ROUTE FIRM DELIVERY UNIQUE TOTAL
-------- -------- -------- -------- -------- -------- -------- -------- -------­ STREET 0 0 0 0 0 0 0 0 PO BOX 0 0 0 0 0 0 0 0 HIGHRISE 0 0 0 0 0 0 0 0 RURAL RT 2 0 0 0 0 0 0 2 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: 2 0 0 0 0 0 0 2
This section shows the address types after the records have been through
Link
LACS
processing.
Address Type After
Link
LACS
The Address Type After LACS
Link
through LACS
, and the address type before and after LACS
Link
table lists the number of addresses converted
Military records are not shown because LACS records.
Link
Link
does not include military
processing.
74
ACE User’s Guide
Job Summary ACE <version> Page 4
-------------------------------------------------------------------------------­LOCATABLE ADDRESS CONVERSION SUMMARY (LACSLINK) (PERCENTAGES BASED ON # OF RECORDS PASSING THE FILTER) CONVERTED NOT CONVERTED COUNT % COUNT %
------------------------------------- -------------------------------------­ CONVERTED (A) 2 1.00 NO MATCH (00) 13 6.50 SECONDARY DROPPED (92) 0 0.00 CAN'T CONVERT (14) 0 0.00 HIGH-RISE DEFAULT (09) 0 0.00
------------------------------------- -------------------------------------­ TOTAL CONVERTED: 2 1.00 TOTAL NOT CONVERTED: 13 6.50 JOB SUMMARY ACE <version> PAGE 3
--------------------------------------------------------------------------------

DELIVERY POINT VALIDATION SUMMARY (DPV)

NO STATS PROCESSED: Y VACANT PROCESSED: Y CMRA DPV DPV DPV STATUS CODE COUNT CONFIRMED NO STAT VACANT
-------------------------------- --------- --------- --------- --------­ PRIMARY/SECONDARY CONFIRMED (Y) 21 0 3 0 SECONDARY NOT CONFIRMED (S) 2 0 0 0 SECONDARY MISSING (D) 7 0 0 0
-------------------------------- --------- --------- --------- --------­ TOTAL: 30 0 3 0 TOTAL NOT CONFIRMED: 170

Locatable Address Conversion Summary

Delivery Point Validation Summary (DPV)
The Locatable Address Conversion Summary table lists the count and percentages of records that were converted and the number and percentages of
Link
addresses that were not converted through LACS
.
This section lists the number and percentage of addresses that are confirmed and not confirmed at the job level. Later in the Job Summary a similar section appears but the information is reported at the file level. The percentages are based on the number of records passing the filter.
Chapter 3: Reports
75
DELIVERY POINT VALIDATION (DPV) TIE-BREAKING SUMMARY (PERCENTAGES BASED ON # OF RECORDS PASSING THE FILTER) COUNT %
------------------------------------­ TIES RESOLVED BY DPV 0 0.00
DELIVERY POINT VALIDATION (DPV) FOOTNOTE SUMMARY -------------------------------
DPV FOOTNOTE COUNT %
--------------------------------- ---------- -----­ AA - ZIP+4 MATCH 176 88.00 A1 - NO ZIP+4 MATCH 24 12.00 BB - ALL COMPONENTS MATCH DPV 15 7.50 CC - SECONDARY INVALID 2 1.00 F1 - MILITARY ADDRESS 0 0.00 G1 - GENERAL DELIVERY 6 3.00 M1 - PRIMARY MISSING 1 0.50 M3 - PRIMARY INVALID 143 71.50 N1 - SECONDARY MISSING 7 3.50 P1 - MISSING RR/HC 4 2.00 P3 - INVALID PO/RR/HC 2 1.00 RR - CMRA MATCH 0 0.00 R1 - CMRA MATCH - NO SECONDARY 0 0.00 U1 - UNIQUE ADDRESS 0 0.00
--------------------------------- ---------- ------
PW FIELDS ----------------------------------------------------------------
PW FIELDS = DATABASE FIELDS
NAME_LINE = NAME ADDRESS = ADDRESS LAST_LINE = LAST_LINE
OUTPUT FILE(S) -----------------------------------------------------------------
RECORDS PASSED FILE NAME DATE TYPE BY FILTER
---------------------------------- ------------------- --------- -------------­ /MOUNTS/TESTCOMP/ACE/JOBFILE/PLATFORMS/SOL_8_64/OUTPUT/NCOA/DATA/NCOAL020.TXT 03-10-2009 22:37:16 ASCII 200
Delivery Point Validation (DPV) Tie­Breaking Summary

Delivery Point Validation (DPV) Footnote 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 filter based on the job level. A similar section appears later in the report but the information is reported at the file level.
The Delivery Point Validation (DPV) Footnote Summary includes the following information:
! footnote and description ! number of records found for each footnote ! percentage of records found for each footnote
Note: A single record can have multiple DPV footnotes (up to 12 characters).
This section reports on records at the job level. A similar section appears later in the Job Summary that is based on records at the file level.
76
ACE User’s Guide
Job Summary ACE <version> Page 5
--------------------------------------------------------------------------------
Geocensus Summary --------------------------------------------------------------
Net Input Records: 646 Less 5 Digit Failure Records: 0
---------­Net Input Records For Geo Processing: 646
Address Level Geo Centroid Geo
Count % Count %
------------------------------------- ------------------------------------­(0) Matched 559 86.53 (1) Street Seg Match 7 1.08 (8) Non Matched 0 0.00 (4) 7 Digit Centroid 4 0.62 (5) 5 Digit Centroid 76 11.76 (9) Non Match 0 0.00
------------------------------------- ------------------------------------­Input Records: 559 86.53 Input Records: 87 13.47
PW Fields ----------------------------------------------------------------
PW Fields = Database Fields
name_line = name firm = firm address = apaddr last_line = last_ln
Output File(s) -----------------------------------------------------------------
Records passed File Name Date Type by Filter
---------------------------------- ------------------- --------- -------------­/mounts/testcomp/ace/jobfile/platforms/sol_8_64/output/ncoa/data/ncoae020.txt 03-10-2009 21:43:40 ASCII 646

GeoCensus Summary The GeoCensus Summary reports the counts for each GeoCensus mode. The

GeoCensus Summary is included in the Job Summary when you choose any of the mode options; Centroid, Address, Best, or All.
Chapter 3: Reports
77
Job Summary ACE <version> Page 6
--------------------------------------------------------------------------------
Postal Code Summary Per File ---------------------------------------------------
File Name: ...tcomp/ace/jobfile/platforms/sol_8_64/output/ncoa/data/ncoae020.txt Filter: n/a Records Passed by Filter: 646
Postal Assigned Corrected Corrected Codes Count % Count % Components Count %
------ --------------- --------------- --------------- --------------­ZIP 646 100.00 0 0.00 City 0 0.00 ZIP+4 71 10.99 533 82.51 State 0 0.00 DPBC n/a n/a n/a n/a Trunc Addresses 0 0.00 CART n/a n/a n/a n/a Trunc Cities 0 0.00 LOT n/a n/a n/a n/a LOT Or n/a n/a n/a n/a County n/a n/a n/a n/a AGeo 559 86.53 0 0.00 CGeo 87 13.47 0 0.00
Address Type Summary (Percentages based on # of records assigned) Count % Count %
------------------------------------- -------------------------------------­Street 49 69.01 Firm 0 0.00 PO Box 9 12.68 General Delivery 10 14.08 High Rise 3 4.23 Military 0 0.00 Rural Route 0 0.00 Unique 0 0.00
CASS Qualitative Statistical Summary (QSS) (Percentages based on # of records passing the filter) Count % Count %
------------------------------------- -------------------------------------­High Rise Default 3 0.46 Rural Route Default 0 0.00 High Rise Exact 0 0.00 Rural Route Exact 0 0.00 EWS Match 0 0.00 LACS Convertible 38 5.88 DPV Confirmed 71 10.99 RDI 56 8.67 LACSLink Conversions 4 0.62

Postal Code Summary Per File

Delivery Point Validation Summary (DPV)
No Stats Processed: Y Vacant Processed: Y CMRA DPV DPV DPV Status Code Count Confirmed No Stat Vacant
-------------------------------- --------- --------- --------- --------­Primary/Secondary Confirmed (Y) 64 0 9 0 Secondary Not Confirmed (S) 4 0 0 0 Secondary Missing (D) 3 0 3 0
-------------------------------- --------- --------- --------- --------­Total: 71 0 12 0 Total Not Confirmed: 575
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 output file, or both. The parameter is called Report on Files, and it is located in the Report: Job Summary block.
If you do not update your input file (either automatically or manually), then ACE will automatically suppress the page about the input file, no matter how the Report on Files parameter was set.
78
ACE User’s Guide
Records Passed By Filter When the page describes an output file, this section will reflect the actual number
of records written or appended to the output file.
When the page pertains to input file, this section shows the number of records that were put through the assignment process. Remember that this number will be affected by your use of any of the following features: Input Filter, Starting
Record Number, Ending Record Number, Assign Which Records = Unassigned, or Process Deleted Records =No.
Assigned Count column The numbers in this column reflect what was actually posted. If you choose not to
post a code, ACE will print “n/a” on that line.
Corrected Count column In this column, a code is counted as corrected if it was wrong in the input record,
or did not appear in the input at all.
Corrected Components column

Address Type Summary

CASS Qualitative Statistical Summary (QSS)

Delivery Point Validation Summary (DPV)

This contains totals for Trunc Addresses and Trunc Cities.
“Trunc” is short for “Truncated.” The counts for these rows reflect address lines and city names that were too long to fit into the database field, even after ACE tried to abbreviate.
This section is based only on records that were fully assigned. Records that were unassigned will not be included in these counts.
The counts and percentages in this section are based on the number of records that passed the filter at the file level. For a description, see “CASS Qualitative
Statistical Summary (QSS)” on page 73.
This summary is based on records at the file level. For a description, see “Delivery Point Validation Summary (DPV)” on page 75.
Chapter 3: Reports
79
Job Summary ACE <version> Page 7
--------------------------------------------------------------------------------
Delivery Point Validation (DPV) Tie-breaking Summary (Percentages based on # of records passing the filter) Count %
------------------------------------­Ties Resolved by DPV 0 0.00
Delivery Point Validation (DPV) Footnote Summary -------------------------------
DPV Footnote Count %
--------------------------------- ---------- -----­AA - ZIP+4 Match 597 92.41 A1 - No ZIP+4 Match 49 7.59 BB - All Components Match DPV 54 8.36 CC - Secondary Invalid 4 0.62 F1 - Military Address 0 0.00 G1 - General Delivery 10 1.55 M1 - Primary Missing 0 0.00 M3 - Primary Invalid 515 79.72 N1 - Secondary Missing 3 0.46 P1 - Missing RR/HC 12 1.86 P3 - Invalid PO/RR/HC 11 1.70 RR - CMRA Match 0 0.00 R1 - CMRA Match - No Secondary 0 0.00 U1 - Unique Address 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 28 4.33 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 3 0.46 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 E439 Exact match in EWS directory 0 0.00 E500 Other Error 0 0.00 E501 Foreign 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 E505 Matched to undeliverable default record 18 2.79 E600 Marked by USPS as unsuitable for delivery of mail 0 0.00 E601 Primary number does not DPV confirm, ZIP+4 removed 526 81.42
-------- -----­Total Error Codes: 575 89.01
Delivery Point Validation (DPV) Tie­breaking Summary
80
ACE User’s Guide
This section is similar to an earlier DPV Tie-breaking Summary, except this section is based on records at the file level. For a description, see “Delivery Point
Validation (DPV) Tie-Breaking Summary” on page 76.

Delivery Point Validation (DPV) Footnote Summary

Error Code Summary This contains a complete list of existing error codes, descriptions for each code,

This section is similar to an earlier DPV Footnote Summary (“Delivery Point
Validation (DPV) Footnote Summary” on page 76).
and counts and percentage amounts for the job.
Chapter 3: Reports
81

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 separate it from the next record. This format makes it 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

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 records in which the city name 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.
82
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
83

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 matchE429Bad city, can't select an address match E430 Possible addr. line matches too close to choose oneE431Urbanization needed, input is wrong or
E439 Address found in Early Warning System directoryE500Other Error E501 Foreign AddressE502Input record entirely blank E503 ZIP not in area covered by partial ZIP+4 directoryE504Overlapping ranges in ZIP+4 directory E505 Matched to undeliverable default recordE600Marked 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

84
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, and 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.

Sample report To 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 output 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
85

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 makes them easier to import into other programs, 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 87) ! File (see “File Statistics file” on page 93) ! ACS (see “Address Conversion Statistics (ACS) file” on page 101)
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,
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.
86
ACE User’s Guide

Job Statistics file

To 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 File, but 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 (
zip4shs 7 Date of the SHS directory.
revsndx 7 Date of the reverse soundex directory.
z4change 7 Date of z4change directory.
CGeo 7 Date of centroid-level GeoCensus directory.
AGeo 7 Date of address-level GeoCensus directory.
zips_start 26 ZIP sort start time.
zips_end 26 ZIP sort end time.
firmln.dct
lastln.dct
zcfxx.dir
cityxx.dir
zip4us.dir
).
addrln.dct
).
pwcas.dct
).
).
).
revzip4.dir
).
).
).
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
87
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.
na_p 6 Percentage of records not assigned, not including foreign records.
lacs_cnt 10 Number of records that are LACS convertible.
88
ACE User’s Guide
Field Length Description
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 GeoCensus 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 Statisti­cal Summary (QSS) section of USPS Form 3553.
qss_hr_p 6 Percentage of highrise exact matches.
This statistic corresponds to USPS-required information in the QSS section of USPS Form 3553.
qss_hrd_at 10 Number of highrise default matches.
This statistic corresponds to USPS-required information in the QSS section of USPS Form 3553.
qss_hrd_p 6 Percentage of highrise default matches.
This statistic corresponds to USPS-required information in the QSS section of USPS Form 3553.
qss_rr_at 10 Number of rural route exact matches.
This statistic corresponds to USPS-required information in the QSS section of USPS Form 3553.
qss_rr_p 6 Percentage of rural route exact matches.
This statistic corresponds to USPS-required information in the QSS section of USPS Form 3553.
qss_rrd_at 10 Number of rural route default matches.
This statistic corresponds to USPS-required information in the QSS section of USPS Form 3553.
qss_rrd_p 6 Percentage of rural route default matches.
This statistic corresponds to USPS-required information in the QSS section of USPS Form 3553.
qss_lacs_at 10 Number of LACS convertible addresses.
This statistic corresponds to USPS-required information in the QSS section of USPS Form 3553.
qss_lacs_p 6 Percentage of LACS convertible addresses.
This statistic corresponds to USPS-required information in the QSS section of USPS Form 3553.
ews_match_at 10 Number of Early Warning System (EWS) matches.
This statistic corresponds to USPS-required information in the QSS section of USPS Form 3553.
Chapter 3: Reports
89
Field Length Description
ews_match_p 6 Percentage of EWS matches.
This statistic corresponds to USPS-required information in the QSS section of USPS 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 Commercial 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 missing.
dpv_sec_miss_p 6 Percentage of records that could not be confirmed during 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 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 Percent of DSF
Link
matches.
Link
matches.
2
drop matches.
2
drop matches.
2
business matches.
2
business matches.
2
throwback matches.
2
throwback matches.
2
seasonal matches.
2
seasonal matches.
2
educational matches.
2
educational matches.
dpv_vacant 10 Number of DPV vacant matches.
dpv_vacant_p 6 Percentage of DPV vacant matches.
dsf_lacs 10 Number of DSF
90
ACE User’s Guide
2
LACS matches.
Field Length Description
dsf_lacs_p 6 Percentage of DSF2 LACS matches.
dsf_curb 10 Number of DSF
dsf_curb_p 6 Percentage of DSF
dsf_ndcbu 10 Number of DSF
2
curb matches.
2
curb matches.
2
Neighborhood Delivery Centralized Box Unit (NDCBU)
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
2
NDCBU matches.
2
central matches.
2
central matches.
2
doorslot matches.
2
doorslot matches.
dpv_aa 10 DPV footnote AA: Number of ZIP+4 matches.
dpv_aa_p 6 DPV footnote AA: Percentage of ZIP+4 matches.
dpv_a1 10 DPV footnote A1: Number of non-ZIP+4 matches.
dpv_a1_p 6 DPV footnote A1: Percentage of non-ZIP+4 matches.
dpv_bb 10 DPV footnote BB: Number of DPV matches (all components).
dpv_bb_p 6 DPV footnote BB: Percentage of DPV matches (all components).
dpv_cc 10 DPV footnote CC: Number of invalid secondary number matches.
dpv_cc_p 6 DPV footnote CC: Percentage of invalid secondary number matches.
dpv_f1 10 DPV footnote F1: Number of military addresses.
dpv_f1_p 6 DPV footnote F1: Percentage of military addresses.
dpv_g1 10 DPV footnote G1: Number of general delivery addresses.
dpv_g1_p 6 DPV footnote G1: Percentage of general delivery addresses.
dpv_m1 10 DPV footnote M1: Number of addresses with the primary number missing.
dpv_m1_p 6 DPV footnote M1: Percentage of addresses with the primary number missing.
dpv_m3 10 DPV footnote M3: Number of addresses with invalid primary number.
dpv_m3_p 6 DPV footnote M3: Percentage of addresses with invalid primary number.
dpv_n1 10 DPV footnote N1: Number of
dpv_n1_p 6 DPV footnote N1: Percentage of
primary number matches; secondary missing.
primary number matches; secondary missing.
dpv_p1 10 DPV footnote P1: Number of addresses missing the RR or the HC number.
dpv_p1_p 6 DPV footnote P1: Percentage of addresses missing the RR or the HC number.
dpv_p3 10
DPV footnote P3: Number of addresses with invalid PO, RR, or HC number.
dpv_p3_p 6
dpv_rr 10
dpv_rr_p 6
DPV footnote P3: Percentage of addresses with invalid PO, RR, or HC number.
DPV footnote RR: Number of addresses that DPV matched to Commercial Mail Receiving Agency (CMRA).
DPV footnote RR: Percentage of addresses that DPV matched to CMRA.
Chapter 3: Reports
91
Field Length Description
dpv_r1 10 DPV footnote R1: Number of addresses that DPV matched to CMRA. No second-
ary address.
dpv_r1_p 6 DPV footnote R1
:
Percentage of addresses that DPV matched to CMRA. No sec-
ondary address.
dpv_u1 10
dpv_u1_p 6
DPV footnote U1: Number of addresses that are unique.
DPV footnote U1: Percentage of addresses that are unique.
eor 1 or 2 End of record: Present only in ASCII files.
1 byte (LF) on UNIX and VMS. 2 bytes (CRLF) on Windows.
92
ACE User’s Guide

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 record per database file, with the 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 GeoCensus codes.
cgeo_cnt 10 Number of records assigned centroid-level GeoCensus codes.
cgeo_p 6 Percentage of records assigned centroid-level GeoCensus codes.
zip_cor 10 Number of records with wrong or missing ZIP Codes on input, which were cor-
rected or added on output.
Chapter 3: Reports
93
Field Length Description
zip_cp 6 Percentage of records with wrong or missing ZIP Codes on input, which were cor-
rected or added on output.
zip4_cor 10 Number of records with wrong or missing ZIP+4 codes on input, which were cor-
rected or added on output.
zip4_cp 6 Percentage of records with wrong or missing ZIP+4 codes on input, which were
corrected or added on output.
dpb_cor 10 Number of records with wrong or missing delivery point barcodes (DPBC) on
input, which were corrected or added on output.
dpb_cp 6 Percentage of records with wrong or missing DPBC on input, which were cor-
rected or added on output.
cart_cor 10 Number of records with wrong or missing carrier route codes on input, which were
corrected or added on output.
cart_cp 6 Percentage of records with wrong or missing carrier route codes on input, which
were corrected or added on output.
lot_cor 10 Number of records with wrong or missing Line-of-Travel (LOT) codes on input,
which were corrected or added on output.
lot_cp 6 Percentage of records with wrong or missing LOT codes on input, which were cor-
rected or added on output.
loto_cor 10 Number of records with wrong or missing LOT Order codes on input, which were
corrected or added on output.
loto_cp 6 Percentage of records with wrong or missing LOT Order codes on input, which
were corrected or added on output.
cnty_cor 10 Number of records of which county codes were wrong or missing on input, and
were corrected or added on output.
cnty_cp 6 Percentage of records of which county codes were wrong or missing on input, and
were corrected or added on output.
ageo_cor 10 Number of records with wrong or missing Address-level GeoCensus codes on
input, which were corrected or added on output.
ageo_cp 6 Percentage of records with wrong or missing Address-level GeoCensus codes on
input, which were corrected or added on output.
cgeo_cor 10 Number of records with wrong or missing Centroid-level GeoCensus codes on
input, which were corrected or added on output.
cgeo_cp 6 Percentage of records with wrong or missing Centroid-level GeoCensus codes on
input, which were corrected or added on output.
city_cor 10 Number of records with corrected city data.
city_cp 6 Percentage of records with corrected city data.
state_cor 10 Number of records with corrected state data.
state_cp 6 Percentage of records with corrected state data.
a_trunc 10 Number of records with truncated address data.
a_trunc_cp 6 Percentage of records with truncated address data.
c_trunc 10 Number of records with truncated city data.
94
ACE User’s Guide
Field Length Description
c_trunc_cp 6 Percentage of records with truncated city data.
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.
qss_hr_at 10 Number of highrise exact matches.
This statistic corresponds to USPS-required information in the Qualitative Statisti­cal Summary (QSS) section of USPS Form 3553.
qss_hr_p 6 Percentage of highrise exact matches.
This statistic corresponds to USPS-required information in the QSS section of USPS Form 3553.
qss_hrd_at 10 Number of highrise default matches.
This statistic corresponds to USPS-required information in the QSS section of USPS Form 3553.
qss_hrd_p 6 Percentage of highrise default matches.
This statistic corresponds to USPS-required information in the QSS section of USPS Form 3553.
qss_rr_at 10 Number of rural route exact matches.
This statistic corresponds to USPS-required information in the QSS section of USPS Form 3553.
qss_rr_p 6 Percentage of rural route exact matches.
This statistic corresponds to USPS-required information in the QSS section of PS Form 3553.
qss_rrd_at 10 Number of rural route default matches.
This statistic corresponds to USPS-required information in the QSS section of USPS Form 3553.
Chapter 3: Reports
95
Field Length Description
qss_rrd_p 6 Percentage of rural route default matches.
This statistic corresponds to USPS-required information in the QSS section of USPS Form 3553.
qss_lacs_at 10 Number of LACS convertible addresses.
This statistic corresponds to USPS-required information in the QSS section of USPS Form 3553.
qss_lacs_p 6 Percentage of LACS convertible addresses.
This statistic corresponds to USPS-required information in the QSS section of USPS 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 Commercial 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 missing.
dpv_sec_miss_p 6 Percentage of records that could not be confirmed during 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 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
Link
matches.
Link
matches.
2
drop matches.
2
drop matches.
2
business matches.
2
business matches.
2
throwback matches.
2
throwback matches.
2
seasonal matches.
2
seasonal matches.
96
ACE User’s Guide
Field Length Description
dsf_educational 10 Number of DSF2 educational matches.
dsf_educational_p 6 Percentage of DSF
2
educational matches.
dpv_vacant 10 Number of DPV vacant matches.
dpv_vacant_p 6 Percentage of DPV vacant matches.
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
2
LACS matches.
2
LACS matches.
2
curb matches.
2
curb matches.
2
Neighborhood Delivery Centralized Box Unit (NDCBU)
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
2
NDCBU matches.
2
central matches.
2
central matches.
2
doorslot matches.
2
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: Last line is bad or missing.
e212 10 Number of records assigned error code E212: No city and bad ZIP.
e212_p 6 Percentage of records assigned error code E212: No city and bad ZIP.
e213 10 Number of records assigned error code E213: Bad city and no ZIP.
e213_p 6 Percentage of records assigned error code E213: Bad city and no ZIP.
e214 10 Number of records assigned error code E214: Bad city and bad ZIP.
e214_p 6 Percentage of records assigned error code E214: Bad city and bad ZIP.
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: Bad ZIP, can't determine which
city match to select.
e302 10 Number of records assigned error code E302: No primary address line parsed.
e302_p 6 Percentage of records assigned error code E302: No primary address line parsed.
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: Street name not found in direc-
tory.
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: Possible street name matches too
close to choose.
e420 10 Number of records assigned error code E420: Primary range is missing.
Chapter 3: Reports
97
Field Length Description
e420_p 6 Percentage of records assigned error code E420: Primary range is missing.
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: Primary range is invalid for street/
route/building.
e422 10 Number of records assigned error code E422: Pre-directional needed, input is
wrong or missing.
e422_p 6 Percentage of records assigned error code E422: Pre directional needed, input is
wrong or missing.
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: Suffix needed, input is wrong or
missing.
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: Suffix & directional needed, input
wrong or missing.
e427 10 Number of records assigned error code E427: Post directional needed, input is
wrong or missing.
e427_p 6 Percentage of records assigned error code E427: Post directional needed, input is
wrong or missing.
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: Bad ZIP, can't select an address
match.
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: Bad city, can't select an address
match.
e430 10 Number of records assigned error code E430: Possible address line matches too
close to choose one.
e430_p 6 Percentage of records assigned error code E430: Possible address line matches too
close to choose one.
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: Urbanization needed, input is
wrong or missing.
e439 10 Number of records assigned error code E439: Exact match in EWS directory.
e439_p 6 Percentage of records assigned error code E439: Exact match in EWS directory.
e500 10 Number of records assigned error code E500: Other Error.
e500_p 6 Percentage of records assigned error code E500: Other Error.
98
ACE User’s Guide
Field Length Description
e501 10 Number of records assigned error code E501: Foreign.
e501_p 6 Percentage of records assigned error code E501: Foreign.
e502 10 Number of records assigned error code E502: Input record entirely blank.
e502_p 6 Percentage of records assigned error code E502: Input record entirely blank.
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: ZIP not in area covered by partial
ZIP+4 Directory.
e504 10 Number of records assigned error code E504: Overlapping ranges in ZIP+4 direc-
tory.
e504_p 6 Percentage of records assigned error code E504: Overlapping ranges in ZIP+4
directory.
e505 10 Number of records assigned error code E505: Matched to undeliverable default
record
e505_p 6 Percentage of records assigned error code E505: Matched to undeliverable default
record.
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: Marked by USPS as unsuitable
for delivery of mail.
e601 10 Number of records assigned error code E601: Primary number does not DPV con-
firm, ZIP+4 removed.
e601_p 6 Percentage of records assigned error code E601: Primary number does not DPV
confirm, ZIP+4 removed.
dpv_aa 10 DPV footnote AA: Number of ZIP+4 matches.
dpv_aa_p 6 DPV footnote AA: Percentage of ZIP+4 matches.
dpv_a1 10 DPV footnote A1: Number of non-ZIP+4 matches.
dpv_a1_p 6 DPV footnote A1: Percentage of non-ZIP+4 matches.
dpv_bb 10 DPV footnote BB: Number of DPV matches (all components).
dpv_bb_p 6 DPV footnote BB: Percentage of DPV matches (all components).
dpv_cc 10 DPV footnote CC: Number of invalid secondary number matches.
dpv_cc_p 6 DPV footnote CC: Percentage of invalid secondary number matches.
dpv_f1 10 DPV footnote F1: Number of military addresses.
dpv_f1_p 6 DPV footnote F1: Percentage of military addresses.
dpv_g1 10 DPV footnoteG1: Number of general delivery addresses.
dpv_g1_p 6 DPV footnote G1: Percentage of general delivery addresses.
dpv_m1 10 DPV footnote M1: Number of addresses with the primary number missing.
dpv_m1_p 6 DPV footnote M1: Percentage of addresses with the primary number missing.
Chapter 3: Reports
99
Field Length Description
dpv_m3 10 DPV footnote M3: Number of addresses with invalid primary number.
dpv_m3_p 6 DPV footnote M3: Percentage of addresses with invalid primary number.
dpv_n1 10 DPV footnote N1: Number of
dpv_n1_p 6 DPV footnote N1: Percentage of
primary number matches, secondary missing.
primary number matches, secondary missing.
dpv_p1 10 DPV footnote P1: Number of addresses missing the RR or the HC number.
dpv_p1_p 6 DPV footnote P1: Percentage of addresses missing the RR or the HC number.
dpv_p3 10
dpv_p3_p 6
DPV footnote P3: Number of addresses with invalid PO, RR, or HC number.
DPV footnote P3: Percentage of addresses with invalid PO, RR, or HC num­ber.
dpv_rr 10
DPV footnote RR: Number of addresses that DPV matched to Commercial Mail Receiving Agency (CMRA).
dpv_rr_p 6
DPV footnote RR: Percentage of addresses that DPV matched to CMRA.
dpv_r1 10 DPV footnote R1: Number of addresses that DPV matched to CMRA, no second-
ary address.
dpv_r1_p 6 DPV footnote R1
:
Percentage of addresses that DPV matched to CMRA, no sec-
ondary address.
dpv_u1 10
dpv_u1_p 6
DPV footnote U1: Number of addresses that are unique.
DPV footnote U1: Percentage of addresses that are unique.
eor 1 or 2 End of record: Present only in ASCII files.
1 byte (LF) on UNIX and VMS. 2 bytes (CRLF) on Windows.
100
ACE User’s Guide
Loading...
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use