1

MTAC 117Intelligent Mail Barcodes and Electronic

Documentation Workgroup Update

2

Intelligent Mail Tray Barcode and Label

Recommended changes to the IMtb for mailer use Extend the Printer Line across label width

Minimize the 10/24 digit barcode print ratio

Reposition the location of the human readable barcode text information

Define a new Mailers Area to the right of the lower barcode and exclude Postal acronyms in the new Mailers Area (AADC, ADC, etc)

Participating mailers developed sample labels to the proposed specifications

The tray label specifications were revised and final specifications are published for the 10/24 and 24 digit Intelligent Mail Tray label on ribbs.usps.gov

3

Intelligent Mail Container Barcode and Label

Recommended changes to the IMcb to improve scan rates and address mailer requests The barcode size and placement have been enhanced to aid with

recognition and scanning

The barcode specification has been modified to allow for “zeros” and “dashes” as padding values in the serial number field

The pallet label layout has been standardized to enhance identification and enable better recognition of the barcode. Two labels sizes have been identified – 8”x11” and 4”x7” (self adhesive)

Packaging guidelines were updated to mitigate scan performance through layers of stretchwrap

The container label specifications were revised and final specifications are published on ribbs.usps.gov

4

Mailer Identification

Mailer ID Application Process MID Application form was simplified and is posted on

ribbs.usps.gov

Online application for MID was recommended and requirements have been written

CRID Identification CRID is a USPS generated ID that identifies a

company at a unique address

Mail.XML automated data exchange communication

Web interface to request and receive the CRID information

5

By/For Identification

Determined available By/For identification options

Selected options to identify the mail owner and mail preparer in the electronic documentation: Mailer ID, Permit Number, and Customer Registration ID

Support the By/For identification need at different data levels in support of multiple functionalities to be implemented by the industry and the USPS

6

Allows inclusion of full-service, basic and POSTNET mailpieces

Full-service mailpieces qualify for full-service if two conditions met:

1. All requirements for full-service met with exception that basic/POSTNET mailpieces do not require a unique IMB

2. eDoc indicates a “Mixed” mailing

3. Piece electronic documentation submitted for basic/POSTNET mailpieces

Mixed Mailings

7

Allows inclusion of full-service, basic and POSTNET bundles/trays on same pallet

Four scenarios supported:

Periodicals Bundles: copalletized bundles paid by consolidator

Standard Mail Flat Bundles: copalletized bundles paid by consolidator

First-Class Mail Letter or Flat Trays: all trays paid at origin

Standard Mail Letter or Flat Trays: all trays paid at origin

Full-service bundles/trays require all full-service requirements except no handling unit to container nesting required at origin

Requirements for all bundles/trays that will be copalletized

Intelligent Mail barcode on bundles

Unique Intelligent Mail Tray barcode on trays

Electronic documentation for bundle/tray that will be copalletized

No piece level electronic documentation

No handling unit to container nesting required

Copalletized Mailings

8

If entire container not created must remove the container from electronic documentation

Manifest Mailing Environment: Pieces not created or spoiled identified in piece level electronic documentation

Other Environments:

Mailer provides Postage Statement Sequence Number and identifies the specific postage statement to adjust

Mailer provides adjustment amount and USPS adjusts the most recent postage statement that is not finalized

Identify specific rate levels to adjust

Identify piece count and adjustment made to lowest rate

Spoilage/Shortage

9

Data Distribution

ACS Data

Data sent to Mail Owner unless delegated

Start-the-Clock Data

Data sent to Mail Owner and Mail Preparer unless delegated

Confirm

Data sent to subscriber ID on mailpiece

The workgroup defined what data can be sent to whom.

10

Data Distribution (cont) Three methods exist to control distribution:

By/For information in the electronic documentation

Profile set by Mail Owner or Mail Preparer

Cast of Characters

By/For Information CRID

MID

Permit #/ZIP+4

Profile Static Complete: Data for the Mail Owner/Mail Preparer is sent to a specific third-

party designated by Mail Owner/Mail Preparer

Static Partial: Data for the Mail Owner is sent to the Mail Preparer as identified in the profile for only the mail prepared by the Mail Preparer as indicated in the By/For

Partial – MID on Piece: Data for the Mail Owner MID in the profile is sent to the owner of the MID on the mailpiece

Dynamic: Allows parties identified in the profile to receive data controlled by the Cast of Characters file

11

Data Distribution (cont.)

ACS Data Data sent to Mail Owner OR data sent to the party designated by

the Mail Owner in the profile

Example: Mail Owner can identify a third-party service provider to receive all ACS data on behalf of the Mail Owner using a Static Complete Profile

Start-the-Clock Data Data sent to Mail Owner and Mail Preparer OR designees in

profile (and Cast of Characters for Dynamic Profile)

Example: Mail Owner can create Dynamic Profile and submit Cast of Characters to send data to third-party

Confirm Data sent to subscriber ID on mailpiece AND third-party defined

in Cast of Characters

Example: Confirm subscriber can create a Dynamic Profile and submit Cast of Characters to send data to a third-party

12

Data Distribution Methods

13

Electronic Documentation

Electronic Documentation Nesting

Developed separate scenarios for Manifest, MLOCR, and Continuous mailers

Mail.dat and Mail.dat XML Change Requests

Recommended change requests in support of Full Service

Mail.dat 09-1 and Mail.XML 4.1

Specifications will be published by September 2008

14

Outstanding Items

Provide updated version of service type codes

Finalize Customer Supplier Agreement write-up