1 DELIVERY SEQUENCE FILE 2ND GENERATION WELCOME!!.
-
Upload
briana-hampton -
Category
Documents
-
view
215 -
download
0
Transcript of 1 DELIVERY SEQUENCE FILE 2ND GENERATION WELCOME!!.
1
DELIVERY SEQUENCE FILE 2ND GENERATION
WELCOME!!
LICENSE AGREEMENTCHANGES
• 1.2 The term “address attributes” shall refer to the data elements derived through the use of the individual tables supplied by USPS to Licensee to perform DSF2 processing. Address attributes are specifically considered to include: a. Seasonal indicator b. Vacant indicator c. Delivery mode type indicator d. Residential indicator (reference Figure 4 in the Licensee Performance Requirements) e. Business indicator f. Drop indicator g. Drop count h. Locatable Address Conversion System (LACS) indicator I. No-stat(istics) indicator j. Address throwback indicator
3
DELIVERY SEQUENCE FILE 2ND GENERATION
LICENSE AGREEMENTCHANGES
19.0 Compliance With Coding Accuracy Support System (CASS) Certifications And Periodic Verification Of DSF2 Matching Capability
19.1 Licensee shall maintain current Coding Accuracy Support System (CASS) certification for ZIP+4 Coding and Delivery Point Coding. To meet this requirement Licensee must be re-certified at each CASS cycle or as specified by USPS.
19.2 This required test shall be performed in conjunction with the CASS certification. In addition to the CASS certification, USPS shall have the right to test the accuracy of the DSF2 process at any time without advance notice.
19.3 Failure to meet the standards established by the CASS certification process or for DSF2 processing as defined within the Licensee Performance Requirements may result in suspension or termination of this License.
4
DELIVERY SEQUENCE FILE 2ND GENERATION
LICENSE PERFORMANCE REQUIREMENTCHANGES
3.6 Copies of this document file and all associated documents will be published on the RIBBS website at http://ribbs.usps.gov/dsf 2nd Generation.
5
DELIVERY SEQUENCE FILE 2ND GENERATION
LICENSE PERFORMANCE REQUIREMENTCHANGES
{4.9} Per Paragraph 13.3 in the License Agreement, DSF2 shall not be used to facilitate the artificial creation of address lists. To detect conditions when address records appear to be the result of artificial manufacture and not legitimately obtained addresses, a “seed” table of artificially manufactured addresses is provided as part of the DPV System. These seed addresses reside in the False Positive table. For each negative response that occurs in a query of the DPV hash table (Table A), a query must be made to the False Positive table. Anytime an address encounters a hit in the False (hsf) table, the Licensee should continue processing, but must notify the USPS of the customer’s name and address (using the file layout below) and shall withhold update to the customer until approval from the USPS is provided. The Licensee must transfer a file containing the affected addresses from each address list to the following address: [email protected]
6
DELIVERY SEQUENCE FILE 2ND GENERATION
LICENSE PERFORMANCE REQUIREMENTCHANGES
“NO STATS”
4.11 “No Stat” addresses: The Licensee shall capture those addresses with a “No Stat” flag that do not result from a default-level match and submit them to the USPS for review. License shall compile and forward monthly to the USPS the file that contains the “No Stat” values. See record layout for the 9-digit ZIP+4 Code and the associated primary and secondary address values that produced the “No Stat” value. The report should only be sent for highrise exact records that have a “No Stat” flag (see example #1 and #2) and confirmed S records that are flagged as “No Stat” and have no associated highrise records at the same primary address (see example #3 and #4).
7
DELIVERY SEQUENCE FILE 2ND GENERATION
LICENSE PERFORMANCE REQUIREMENTCHANGES
“NO STATS”
(Continued 4.11)
Example #1
Input = 102 Main St Apt B
DSF2 reports 102 Main St Apt B is a “No Stat” record
38119-1236 has DPV confirmed
Since the address is not a default record, it should be reported.
8
DELIVERY SEQUENCE FILE 2ND GENERATION
LICENSE PERFORMANCE REQUIREMENTCHANGES
“NO STATS”Example #2Input – 102 Main St Apt C DSF2 reports 102 Main St Apt C is a “No Stat” record 38119-1235 has DPV confirmed Since the address matched to the highrise default record in ZIP+4, it should not bereported.
No ZIP Rec Primary Sec Sec ZIP+4Stat Default Code Type CRID Street Low/High Abbrev No Low/High
X X 38119 S C001 Main 100-198 1234-1234 X X 38119 H C001 Main 102-102 1235-1235 38119 H C001 Main 102-102 Apt A 1236-1236 X 38119 H C001 Main 102-102 Apt B 1236-1236
9
DELIVERY SEQUENCE FILE 2ND GENERATION
LICENSE PERFORMANCE REQUIREMENTCHANGES
“NO STATS”(Continued 4.11)
Example #3
Input = 104 Main St
DSF2 reports 104 Main St is a “No Stat” record
38119-1234 has DPV confirmed
Since there are associated highrise records at the address, it should not be reported.
10
DELIVERY SEQUENCE FILE 2ND GENERATION
LICENSE PERFORMANCE REQUIREMENTCHANGES
“NO STATS”(Continued 4.11)
Example #4
Input = 116 Main St
DSF2 reports 116 Main St is a “No Stat” record
38119-1234 has DPV confirmed
Since there are no associated highrise records address, it should be reported.
No ZIP Rec Primary Sec Sec ZIP+4 Stat Default Code Type CRID Street Low/High Abbrev No Low/High
X X 38119 S C001 Main 100-198 1234-1234
38119 H C001 Main 104-104 Apt A 1236-1236
38119 H C001 Main 104-104 Apt B 1236-1236
11
DELIVERY SEQUENCE FILE 2ND GENERATION
LICENSE PERFORMANCE REQUIREMENTS CHANGES
“NO STATS”(Continued 4.11)
The layout for reporting “No Stats” to the USPS is as follows:
Field Relative Reference Logical Position Numbers Field Description Length From/Thru
1 ZIP Code 05 01-05
2 ZIP Add-on 04 06-09
3 Primary Number 10 10-19
4 Secondary Descriptor 04 20-23
5 Secondary Number 08 24-31
6 Filler 09 32-40
The Licensee must transfer a file containing the affected addresses from each address list to the following address: [email protected]
12
DELIVERY SEQUENCE FILE 2ND GENERATION
LICENSE PERFORMANCE REQUIREMENTCHANGES
Field Size Example Field Begin Field EndDSF2 Licensee Name Pic x (40) OmniFax 1 40DSF2 License Number Pic x (04) 1234 41 44Year/Month/Day Report Date Pic 9 (08) 20010912 45 52Year/Month/Day Customer FileReceived
Pic 9 (08) 20010901 53 60
Year/Month/Day Customer FileProcessed
Pic 9 (08) 20010903 61 68
Filler Pic x (10) 69 78Access Mode Pic x (01) B 79 79
O – Online InquiryProcessingB – Batch Processing
Customer Name Pic x(40)
NationalGeographic
80 119
Customer Tax IdentificationNumber (TIN)
Pic x (12) 123456789012
120 131
Customer Standard Industry Code*(SIC/NAICS)
Pic x (06) 442299 132 137
Customer Number Pic x (06) 123456 138 143Filler Pic x (20) 144 163
13
DELIVERY SEQUENCE FILE 2ND GENERATION
CERTIFICATIONCHANGES
Delivery Point Validation Product (DPV)
The United States Postal Service (USPS) has developed a new technology product that will help mailers validate the accuracy of their address information, right down to the physical delivery point. Mailers will be able to identify individual addresses within a mailing list that are potentially undeliverable-as-addressed due to an addressing deficiency.
14
DELIVERY SEQUENCE FILE 2ND GENERATION
CERTIFICATIONCHANGES
Second Generation Delivery Sequence File – Licensed Service (DSF2). The USPS has transitioned from the use of the Delivery Sequence File (DSF) data to the new DSF2 Product. Where DSF was licensed to a network of commercial firms (DSF Licensees) that provided address list processing services for the mailing community, the USPS has substituted the DSF data with the new DPV Product and additional data sets to fully replicate the DSF services. Through a network of licensed service providers, the mailer can also obtain unique address attributes such as, “Is the delivery address a business location?” or “Is the delivery address currently vacant?” To help distinguish the services available under the original DSF license agreement from the new services based upon the DPV Product, the USPS will refer to the new service as Second Generation Delivery Sequence File – Licensed Service or by its service mark DSF2.
15
DELIVERY SEQUENCE FILE 2ND GENERATION
CERTIFICATIONCHANGES
DSF2 Licensed Service contains the same data found in the Basic DPV Product along with additional address-attribute data. Address-attribute data are additional intelligence flags not directly related to the address format or content: instead they tell the mailer something more about an address. An example of address-attribute data would be, “Is this address vacant?” or, “Is this address a business delivery address?” or, “Is this address delivered into a curb-side mailbox or a Collection Box Unit (CBU)?” The address-attribute data provides the mailer with knowledge about the address, above and beyond what is necessary to accurately format the address. Address-attribute data allows mailers to produce more targeted mailings. An example might be a mailer who wants to send out a coupon for lawn care services – this mailer may only want to mail to residential addresses that are not centralized, because apartment dwellers do not have lawns.
16
DELIVERY SEQUENCE FILE 2ND GENERATION
DSF2 DEVELOPER’S GUIDECHANGES
Interface Developer Guide DSF2 TABLE ACCESS CODE
OVERVIEW and eLOT Pseudo Sequence Numbers
17
DELIVERY SEQUENCE FILE 2ND GENERATION
DSF2 DEVELOPER’S GUIDECHANGES
4) If RAM is a concern, consider using the 100 file split version. (See Title 4, Testing the hash table for SHA'd EMDP using Split Files.)
18
DELIVERY SEQUENCE FILE 2ND GENERATION
DSF2 DEVELOPER’S GUIDECHANGES
Finally test the secondary number’s first position for a ‘1’ and the second position for a non-digit or non-alpha, and the third position for a ‘2’, and the fourth and subsequent positions are spaces. If this pattern is found, replace the positions containing the ‘1’ and ‘2’ with ‘9’. The purpose of this test is to locate ½ and change it to 9/9.
19
DELIVERY SEQUENCE FILE 2ND GENERATION
DSF2 DEVELOPER’S GUIDECHANGES
(8) Enhanced Line-of-Travel (eLOT)
The eLOT sample data, file layout, and directions on how to use the eLOT file are located on the web at the following address: http://ribbs.usps.gov/files/eLOT
The process to create the Pseudo Delivery Sequence Numbers require the following steps:
1) The file should first be sorted by eLOT in the following sequence: ZIP Code; Carrier ID, eLOT Sequence, ZIP+4 code and DPC, then ascending or descending based on the flag in the eLOT Master file.
If your input data element was not located, the software will assign a default of “0000D”. Please refer to DMM M050 1.2 for sorting in this case.
20
DELIVERY SEQUENCE FILE 2ND GENERATION
DSF2 DEVELOPER’S GUIDECHANGES
Continued (8)
2) At the beginning of each ZIP Code and Carrier Route, begin re-sequencing with Pseudo Delivery Sequence Number of ‘0001’. For each additional delivery point within the ZIP Code and Carrier Route, increment the Pseudo Delivery Sequence Number by one until you get to the end of that Carrier Route ID. At the beginning of the next ZIP Code or Carrier Route, begin re-sequencing with the Pseudo Delivery Sequence Number of ‘0001’. Perform this process until you have reached the end of the customer file.
3) Remove the eLOT Delivery Sequence Number and the Ascending/Descending Code from the customer’s final file.
21
DELIVERY SEQUENCE FILE 2ND GENERATION
DSF2 DEVELOPER’S GUIDE CHANGES& PSEUDO SEQUENCE
01/23/03
The following is an example of addresses processed through DSF2 and eLOT:
CASS Standardized Address ZIP Code CarrierRoute
eLOTSequence
ZIP+4 DPC A/D CASSRecord
Type
CASSDefault Flag
DSF2
ValidateCode
PseudoSequenceNumber
Assigned
123 MAIN ST 19401 C005 0001 1225 23 A S Y 0001
134 MAIN ST 19401 C005 0005 1238 34 D S Y 0002
132 MAIN ST 19401 C005 0005 1238 32 D S Y 0003
186 MAIN ST 19401 C005 0032 1431 86 A S Y 0004
103 KING ST 19401 C011 0004 0115 03 A S Y 0001
199 OAK ST 19408 C031 0001 6778 99 D S Y 0001
201 POPLAR 19501 C025 0005 4438 01 A S Y 0001
203 POPLAR 19501 C025 0005 4438 03 A S Y 0002
22
DELIVERY SEQUENCE FILE 2ND GENERATION
DSF2 DEVELOPER’S GUIDE CHANGES& PSEUDO SEQUENCE
CASS Standardized Address ZIP Code CarrierRoute
eLOTSequence
ZIP+4 DPC A/D CASSRecord
Type
CASSDefault Flag
DSF2
ValidateCode
PseudoSequenceNumber
Assigned
1123 MAIN ST 38106 C026 0004 2729 99 A H Y D 0000
1123 MAIN ST APT 1 38106 C026 0004 2729 99 A H Y S 0000
1123 MAIN ST APT 2 38106 C026 0004 2729 99 A H Y S 0000
1123 MAIN ST STE 1 38106 C026 0004 2729 99 A H Y S 0000
1123 MAIN ST STE 2 38106 C026 0004 2729 99 A H Y S 0000
1123 MAIN ST BSMT 38106 C026 0004 2729 99 A H Y S 0000
1123 MAIN ST LOWR 38106 C026 0004 2729 99 A H Y S 0000
1123 MAIN ST UPPR 38106 C026 0004 2729 99 A H Y S 0000
1125 MAIN ST 38106 C026 0004 2729 99 A H Y D 0000
1125 MAIN ST APT 1 38106 C026 0004 2729 99 A H Y S 0000
23
DELIVERY SEQUENCE FILE 2ND GENERATION
CASS Standardized Address ZIP Code CarrierRoute
eLOTSequence
ZIP+4 DPC A/D CASSRecord
Type
CASSDefault Flag
DSF2
ValidateCode
PseudoSequenceNumber
Assigned
123 MAIN ST APT 1 38118 C001 0006 3413 01 A H Y 0001
123 MAIN ST APT 2 38118 C001 0006 3413 02 A H Y 0002
123 MAIN ST APT 3 38118 C001 0006 3413 03 A H Y 0003
125 MAIN ST APT 1 38118 C001 0007 3414 01 A H Y 0004
24
DELIVERY SEQUENCE FILE 2ND GENERATION
DSF2 DEVELOPER’S GUIDE CHANGES& PSEUDO SEQUENCE
CASS Standardized Address ZIP Code CarrierRoute
eLOTSequence
ZIP+4 DPC A/D CASSRecord
Type
CASSDefault Flag
DSF2
ValidateCode
PseudoSequenceNumber
Assigned
RR1 BOX 200 53821 R001 0001 9801 00 A R Y N 0000
RR 1 53821 R001 0001 9801 99 A R Y N 0000
RR 1 53821 R001 0001 9801 99 A R Y N 0000
RR 1 BOX 298 53821 R001 0001 9801 98 A R Y N 0000
RR 1 BOX 262 53821 R001 0292 9615 62 A R Y 0001
RR 1 BOX 262A 53821 R001 0294 9614 62 A R Y 0002
RR 1 BOX 263 53821 R001 0296 9616 63 A R Y 0003
RR 1 BOX 261 53821 R001 0349 9614 61 A R Y 0004
25
DELIVERY SEQUENCE FILE 2ND GENERATION
DSF2 DEVELOPER’S GUIDE CHANGES& PSEUDO SEQUENCE
CASS Standardized Address ZIP Code CarrierRoute
eLOTSequence
ZIP+4 DPC A/D CASSRecord
Type
CASSDefault Flag
DSF2
ValidateCode
PseudoSequenceNumber
Assigned
PO BOX 1 53821 B001 0001 0001 01 A P Y 0001
PO BOX 2 53821 B001 0001 0002 02 A P Y 0002
PO BOX 91 53821 B002 0001 0091 91 A P Y 0005
PO BOX 92 53821 B002 0001 0092 92 A P Y 0006
PO BOX 23 53821 B002 0001 0023 23 A P Y 0001
PO BOX 24 53821 B002 0001 0024 24 A P Y 0002
PO BOX 25 53821 B002 0001 0025 25 A P Y 0003
PO BOX 26 53821 B002 0001 0026 26 A P Y 0004
26
DELIVERY SEQUENCE FILE 2ND GENERATION
DSF2 DEVELOPER’S GUIDE CHANGES& PSEUDO SEQUENCE
CASS Standardized Address ZIP Code CarrierRoute
eLOTSequence
ZIP+4 DPC A/D CASSRecord
Type
CASSDefault Flag
DSF2
ValidateCode
PseudoSequenceNumber
Assigned
GENERAL DELIVERY 02564 G001 0001 9999 99 A G Y 0001
GENERAL DELIVERY 02564 G001 0001 9999 99 A G Y 0001
27
DELIVERY SEQUENCE FILE 2ND GENERATION
DSF2 DEVELOPER’S GUIDE CHANGES& PSEUDO SEQUENCE
CASS Standardized Address ZIP Code CarrierRoute
eLOTSequence
ZIP+4 DPC A/D CASSRecord
Type
CASSDefault Flag
DSF2
ValidateCode
PseudoSequenceNumber
Assigned
836 COLLEGE BLVD 60101 C005 0246 1560 99 A H Y D 0000
836 COLLEGE BLVD 60101 C005 0246 1560 99 A H Y D 0000
836 COLLEGE BLVD UNIT 11 60101 C005 0246 1560 99 A H Y S 0000
836 COLLEGE BLVD APT 20 60101 C005 0246 1560 99 A H Y S 0000
836 COLLEGE BLVD UNIT 303 60101 C005 0246 1560 99 A H Y S 0000
836 COLLEGE BLVD LOWR 60101 C005 0246 1560 99 A H Y S 0000
836 COLLEGE BLVD UNIT 304 60101 C005 0246 1560 99 A H Y S 0000
836 COLLEGE BLVD BSMT 60101 C005 0246 1560 99 A H Y S 0000
836 COLLEGE BLVD APT 101 60101 C005 0247 1560 26 A H Y 0001
836 COLLEGE BLVD APT 201 60101 C005 0248 1560 51 A H Y 0002
836 COLLEGE BLVD APT 300 60101 C005 0249 1560 75 A H S 0000
836 COLLEGE BLVD APT 301 60101 C005 0249 1560 76 A H Y 0003
836 COLLEGE BLVD APT 105 60101 C005 0250 1560 30 A H S 0000
836 COLLEGE BLVD APT 106 60101 C005 0250 1560 31 A H S 0000
836 COLLEGE BLVD APT 202 60101 C005 0251 1560 52 A H Y 0004
836 COLLEGE BLVD APT 202 60101 C005 0251 1560 52 A H Y 0004
836 COLLEGE BLVD APT 205 60101 C005 0251 1560 55 A H S 0000
836 COLLEGE BLVD APT 205 60101 C005 0251 1560 55 A H S 0000
836 COLLEGE BLVD APT 207 60101 C005 0251 1560 57 A H S 0000
836 COLLEGE BLVD APT 207 60101 C005 0251 1560 57 A H S 0000
836 COLLEGE BLVD APT 208 60101 C005 0251 1560 58 A H S 0000
836 COLLEGE BLVD APT 302 60101 C005 0252 1560 77 A H Y 0005
28
DELIVERY SEQUENCE FILE 2ND GENERATION
DSF2 DEVELOPER’S GUIDE CHANGES& PSEUDO SEQUENCE
CASS Standardized Address ZIP Code CarrierRoute
eLOTSequence
ZIP+4 DPC A/D CASSRecord
Type
CASSDefault Flag
DSF2
ValidateCode
PseudoSequenceNumber
Assigned
146 N SCHOOL ST 60101 C006 0000 3579 46 S N 0000
148 N SCHOOL ST 60101 C006 0000 3579 48 S N 0000
150 N SCHOOL ST 60101 C006 0000 3579 50 S N 0000
29
DELIVERY SEQUENCE FILE 2ND GENERATION
DSF2 DEVELOPER’S GUIDE CHANGES& PSEUDO SEQUENCE
CASS Standardized Address ZIP Code Carrier Route eLOT Sequence
ZIP+4 DPC A/D CASSRecordType
CASS DefaultFlag
DSF2 ValidateCode
PseudoSequenceNumber
Assigned
141 N SCHOOL ST 60101 C018 0151 3549 41 A S Y 0001
143 N SCHOOL ST 60101 C018 0151 3549 43 A S N 0000
145 N SCHOOL ST 60101 C018 0151 3549 45 A S N 0000
144 N SCHOOL ST 60101 C018 0152 3550 44 D S N 0000
142 N SCHOOL ST 60101 C018 0152 3550 42 D S N 0000
140 N SCHOOL ST 60101 C018 0152 3550 40 D S Y 0002
138 N SCHOOL ST 60101 C018 0152 3550 38 D S N 0000
136 N SCHOOL ST 60101 C018 0152 3550 36 D S Y 0003
134 N SCHOOL ST 60101 C018 0152 3550 34 D S N 0000
132 N SCHOOL ST 60101 C018 0152 3550 32 D S Y 0004
130 N SCHOOL ST 60101 C018 0152 3550 30 D S N 0000
128 N SCHOOL ST 60101 C018 0152 3550 28 D S Y 0005
126 N SCHOOL ST APT 3 60101 C018 0152 3550 26 D S N 0000
124 N SCHOOL ST 60101 C018 0152 3550 24 D S Y 0006
124 N SCHOOL ST LOWR 60101 C018 0152 3550 24 D S S 0000
124 N SCHOOL ST APT A 60101 C018 0152 3550 24 D S S 0000
124 N SCHOOL ST APT B 60101 C018 0152 3550 24 D S S 0000
120 N SCHOOL ST 60101 C018 0152 3550 20 D S N 0000
* 120 N SCHOOL ST APT A 60101 C018 0152 3550 20 D S Y 0008
* 120 N SCHOOL ST APT B 60101 C018 0152 3550 20 D S Y 0007
124 N SCHOOL ST APT 1 60101 C018 0152 3550 24 D S S 0000
124 N SCHOOL ST APT 2 60101 C018 0152 3550 24 D S S 0000
* **Optional eLOT calculation for saturation rates**
Optional Pseudo Sequence Number Assignment on Street Records.
These records are defined as:
Street Records that contain the same ZIP, Carrier, eLOT sequence number, plus 4, DPC code, primary number and address elements, but have different
standardized addresses and DSF2 Validate with a code of 'Y'.
If the standardized addresses were the same, the pseudo sequence number would be the same, if the addresses were different the pseudo sequence
numbers would be different.
30
DELIVERY SEQUENCE FILE 2ND GENERATION
DSF2 DEVELOPER’S GUIDE CHANGES& PSEUDO SEQUENCE
CASS Standardized Address ZIP Code Carrier Route eLOTSequence
ZIP+4 DPC A/D CASSRecordType
CASS DefaultFlag
DSF2 ValidateCode
PseudoSequenceNumber
Assigned
20W526 BELMONT PL 60101 C039 0147 1955 26 D S Y 0001
20W526 BELMONT PL 60101 C039 0147 1955 26 D S Y 0001
20W526 BELMONT PL APT A 60101 C039 0147 1955 26 D S S 0000
31
DELIVERY SEQUENCE FILE 2ND GENERATION
SEASONAL
32
DELIVERY SEQUENCE FILE 2ND GENERATION
FOOTNOTES
The following standard footnotes shall be provided to customers upon their request:
AA Input Address Matched to the ZIP+4 fileA1 Input Address Not Matched to the ZIP+4 fileBB Input Address Matched to DPV (all components)CC Input Address Primary Number Matched to DPV but Secondary Number not Matched
(present but invalid)N1 Input Address Primary Number Matched to DPV but Highrise Address Missing Secondary
NumberM1 Input Address Primary Number MissingM3 Input Address Primary Number InvalidP1 Input Address PO, RR, or HC Box number MissingP3 Input Address PO, RR, or HC Box number InvalidRR Input Address Matched to CMRA and PMB designator present (PMB 123 or #123)R1 Input Address Matched to CMRA but PMB designator not present (PMB 123 or #123)
33
DELIVERY SEQUENCE FILE 2ND GENERATION
FOOTNOTES
**** No Delivery Type on Match –
If you get a DPV confirm (BB) or (CC) Input Address Matched toDPV (all components) and no delivery type, you need to move (N1)Input Address Primary Number Matched to DPV but HighriseAddress Missing Secondary Number to the footnote code, replacing BBor CC with N1.
DPV validates the address when there is a Highrise record missingfrom the database. If there are only records with secondary informationand no Highrise default, DPV will make a Highrise default record with nodelivery type and validate that record.
34
DELIVERY SEQUENCE FILE 2ND GENERATION
“How are residential addresses determined?”
Not a Business record, check the following:
DPV Confirmation indicator is a ‘Y’ Not in the Business table Not a General Delivery Not in the No Stat table
35
DELIVERY SEQUENCE FILE 2ND GENERATION FALSE POSITIVES
4.9 Per Paragraph 13.3 in the License Agreement, DSF2 shall not beused to facilitate the artificial creation of address lists. To detectconditions when address records appear to be the result of artificialmanufacture and not legitimately obtained addresses, a “seed” table ofartificially manufactured addresses is provided as part of the DPV System.These seed addresses reside in the False Positive table. For eachnegative response that occurs in a query of the DPV hash table(Table A), a query must be made to the False Positive table.
Anytime an address encounters a hit in the False (hsf) table, theLicensee should continue processing, but must notify the USPS of thecustomer’s name and address (using the file layout below) and shallwithhold update to the customer until approval from the USPS is provided.The Licensee must transfer a file containing the affected addresses fromeach address list to the following address: [email protected]
36
DELIVERY SEQUENCE FILE 2ND GENERATION
FALSE POSITIVES vs.MATCH RATES
These results came from an actual file that was submitted for processing…
Input Record Count: 703,156
3.7% match rate to DSF2: 26,679
99.9% match rate to ZIP+4: 703,055
Number of ZIP Codes on file: 8
There were 3 false positives on this file.
37
DELIVERY SEQUENCE FILE 2ND GENERATION
QUESTIONS???
38
DELIVERY SEQUENCE FILE 2ND GENERATION
THANK YOU …..