1. 1 DELIVERY SEQUENCE FILE 2ND GENERATION WELCOME!!

2. LICENSE AGREEMENT CHANGES 1.2The term “address attributes” shall refer to the data elements derived through the use of the individual tables supplied by USPS to Licensee to perform DSF 2 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. 3 DELIVERY SEQUENCE FILE 2ND GENERATION LICENSE AGREEMENT CHANGES 19.0 Compliance With Coding Accuracy Support System (CASS) Certifications And Periodic Verification Of DSF 2 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 DSF 2 process at any time without advance notice. 19.3 Failure to meet the standards established by the CASS certification process or for DSF 2 processing as defined within the Licensee Performance Requirements may result in suspension or termination of this License.

4. 4 DELIVERY SEQUENCE FILE 2ND GENERATION LICENSE PERFORMANCE REQUIREMENT CHANGES 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. 5 DELIVERY SEQUENCE FILE 2ND GENERATION LICENSE PERFORMANCE REQUIREMENT CHANGES {4.9} Per Paragraph 13.3 in the License Agreement, DSF 2 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: Dsf2stop@email.usps.gov Dsf2stop@email.usps.gov

6. 6 DELIVERY SEQUENCE FILE 2ND GENERATION LICENSE PERFORMANCE REQUIREMENT CHANGES “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. 7 DELIVERY SEQUENCE FILE 2ND GENERATION LICENSE PERFORMANCE REQUIREMENT CHANGES “NO STATS” (Continued 4.11) Example #1 Input = 102 Main St Apt B  DSF 2 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. 8 DELIVERY SEQUENCE FILE 2ND GENERATION LICENSE PERFORMANCE REQUIREMENT CHANGES “NO STATS”

9. 9 DELIVERY SEQUENCE FILE 2ND GENERATION LICENSE PERFORMANCE REQUIREMENT CHANGES “NO STATS” (Continued 4.11) Example #3 Input = 104 Main St  DSF 2 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. 10 DELIVERY SEQUENCE FILE 2ND GENERATION LICENSE PERFORMANCE REQUIREMENT CHANGES “NO STATS” (Continued 4.11) Example #4 Input = 116 Main St  DSF 2 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 A1236-1236 38119 H C001 Main 104-104 Apt B1236-1236

11. 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 1ZIP Code 0501-05 2ZIP Add-on 0406-09 3Primary Number 1010-19 4Secondary Descriptor 0420-23 5Secondary Number 0824-31 6Filler 0932-40 The Licensee must transfer a file containing the affected addresses from each address list to the following address: dsf2nost@email.usps.gov

12. 12 DELIVERY SEQUENCE FILE 2ND GENERATION LICENSE PERFORMANCE REQUIREMENT CHANGES

13. 13 DELIVERY SEQUENCE FILE 2ND GENERATION CERTIFICATION CHANGES 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. 14 DELIVERY SEQUENCE FILE 2ND GENERATION CERTIFICATION CHANGES Second Generation Delivery Sequence File – Licensed Service (DSF 2 ). The USPS has transitioned from the use of the Delivery Sequence File (DSF) data to the new DSF 2 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 DSF 2.

15. 15 DELIVERY SEQUENCE FILE 2ND GENERATION CERTIFICATION CHANGES DSF 2 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. 16 DELIVERY SEQUENCE FILE 2ND GENERATION DSF2 DEVELOPER’S GUIDE CHANGES Interface Developer Guide DSF 2 TABLE ACCESS CODE OVERVIEW and eLOT Pseudo Sequence Numbers

17. 17 DELIVERY SEQUENCE FILE 2ND GENERATION DSF2 DEVELOPER’S GUIDE CHANGES 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. 18 DELIVERY SEQUENCE FILE 2ND GENERATION DSF2 DEVELOPER’S GUIDE CHANGES 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. 19 DELIVERY SEQUENCE FILE 2ND GENERATION DSF2 DEVELOPER’S GUIDE CHANGES (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/eLOThttp://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. 20 DELIVERY SEQUENCE FILE 2ND GENERATION DSF2 DEVELOPER’S GUIDE CHANGES 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. 21 DELIVERY SEQUENCE FILE 2ND GENERATION DSF2 DEVELOPER’S GUIDE CHANGES & PSEUDO SEQUENCE

22. 22 DELIVERY SEQUENCE FILE 2ND GENERATION DSF2 DEVELOPER’S GUIDE CHANGES & PSEUDO SEQUENCE

23. 23 DELIVERY SEQUENCE FILE 2ND GENERATION

24. 24 DELIVERY SEQUENCE FILE 2ND GENERATION DSF2 DEVELOPER’S GUIDE CHANGES & PSEUDO SEQUENCE

25. 25 DELIVERY SEQUENCE FILE 2ND GENERATION DSF2 DEVELOPER’S GUIDE CHANGES & PSEUDO SEQUENCE

26. 26 DELIVERY SEQUENCE FILE 2ND GENERATION DSF2 DEVELOPER’S GUIDE CHANGES & PSEUDO SEQUENCE

27. 27 DELIVERY SEQUENCE FILE 2ND GENERATION DSF2 DEVELOPER’S GUIDE CHANGES & PSEUDO SEQUENCE

28. 28 DELIVERY SEQUENCE FILE 2ND GENERATION DSF2 DEVELOPER’S GUIDE CHANGES & PSEUDO SEQUENCE

29. 29 DELIVERY SEQUENCE FILE 2ND GENERATION DSF2 DEVELOPER’S GUIDE CHANGES & PSEUDO SEQUENCE

30. 30 DELIVERY SEQUENCE FILE 2ND GENERATION DSF2 DEVELOPER’S GUIDE CHANGES & PSEUDO SEQUENCE

31. 31 DELIVERY SEQUENCE FILE 2ND GENERATION SEASONAL

32. 32 DELIVERY SEQUENCE FILE 2ND GENERATION FOOTNOTES

33. 33 DELIVERY SEQUENCE FILE 2ND GENERATION FOOTNOTES

34. 34 DELIVERY SEQUENCE FILE 2ND GENERATION

35. 35 DELIVERY SEQUENCE FILE 2ND GENERATION FALSE POSITIVES

36. 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. 37 DELIVERY SEQUENCE FILE 2ND GENERATION QUESTIONS???

38. 38 DELIVERY SEQUENCE FILE 2ND GENERATION THANK YOU …..