April 2014 PSA Visibility and eVS Committee Report By John Medeiros Notes from April 2014 PTR/eVS User Group Call IMpb  Competitive Products only ‐ Adjustment phase in still in pilot – Non Compliance fee $0.20/piece Compliance Thresholds effective July 2014 o 99% Barcode – Unique IMpb or Legacy o 95% Shipping Services File – 1.6 or higher o 95% Addresses and/or Zip +4 in the Shipping Services File  BPM & Priority Mail customers may use IMB and Mail.dat in lieu of Shipping Services File o Priority Mail not eligible for additional insurance with IMB January 2015 o Metered Mailers must meet IMpb requirements for Commercial Pricing o Certified & Registered Mail required to use IMpb in January 2015 Hot Topics  File Timeliness o Heavily discussed at MTAC and Task Team 19, USPS said it had no plans to use latency for assessments. At the time, it was not an issue.  USPS intends to charge for latency even though it is not an element of the requirements. USPS states, latency causes the file and address to fail. They have built their compliance matrix reporting around it based on the First Scan of a package linked to pieces with the same Electronic File Number (EFN). MTAC PTR/eVS Subgroup to form due to Industry pushback starting April 25, 2014 Industry voiced their concerns when USPS disclosed their plans during the April PTR/eVS Users Group Call. We let USPS know we had discussed this at length in Task Team 19 & MTAC Meetings. USPS said they had no plans to make latency part of the elements for Non‐Compliance for the Final Rules on IMpb (meaning not subject to non‐compliance fees). Yes, USPS can make new rules but there is a process to follow and should include feedback from its customers. At first glance there appear to be attributes that would not be favorable for customers. USPS has proposed the following criteria for discussion: File Timeliness Criteria: Valid file received 3 hours before the first USPS physical scan event or Valid file received by 0300 CT the next calendar day and Valid Shipping Partner Event with address information received 3 hours before the first USPS physical scan event There are multiple scenarios where this logic presents issues for Parcel Shippers. Everyone understands the purpose of including addresses and/or Zip + 4s in the Shipping Services File is to add in the sorting of packages when used and needed. Yet as we learn more about the design of the processes and measurement system that have been built there are elements that work to the customer detriment. 

Use of Addresses by PASS/DSS o Only about 30% of packages scanned with PASS/DSS. With a 95% tolerance in July, this leaves a 65% gap, where assessments could take place when addresses are not used or needed.  Is it fair for USPS to issues assessment when addresses are not used to sort packages?  Is there is a revenue loss when USPS opts not to use an address for sorting? Scenarios that play to a customer’s detriment o Customer drops packages at an Acceptance Unit, NDC or SCF and USPS performs an Acceptance Scan or Sort Scan on a package today, USPS receives the file sometime later in the same day, well before its needed for early morning DDU package sorting. Then assess the shipper a non‐compliance fee for the file being late, then have the file in time the next morning to use PASS/DSS to sort the package. USPS gains the benefit of having the address and assesses a non‐compliance fee anyway. Is this fair ?? o Customer drops at a DDU just after 7am Early Bird Cut Off. USPS performs Acceptance Scan(s), file arrives within the next hour. The Acceptance scan trips the late designator to record the file as late. USPS has the file in plenty of time to complete an afternoon or next morning package sort. In this particular scenario this is an office that uses Scheme Clerks to sort packages and does not rely on PASS or DSS for sorting. USPS assesses non‐compliance fee anyway. o
Other possibilities exist where USPS may have received a file in time and it is not consumed by PTR. If a scan takes place 3 hours prior to this occurring, the file is considered late according to USPS’ proposal. Deployment schedule of PASS and DSS Equipment No Non‐Compliance Fees for System Failures or Outages if process is followed  Contingency Plans System Outages – Submit Help Desk Ticket with details of impacted Mailings – files must be submitted within 3 days of systems being restored  Exceptions for IMpb Compliance can be gained through the VP of Sales – Cliff Rucker PTS is now called PTR (Product Tracking & Reporting)  New Subset of ‘Attempted Delivery Events’ provides more detail of the event o 53 – Receptacle Blocked o 54 – Receptacle Full/Oversized Item o 55 – No Secure Location Available o 56 – No Authorized Recipient Available Additional Events added with release 1.8 (April 27th) – geared at better visibility for Institutions  Colleges & Universities  Apartment & Condominiums 
Correction Overlabel functionality is working – Special Thanks to Richard who encouraged USPS not to postpone release until July 2014 
Predictive Delivery on USPS Track & Confirm in Pilot Stage – provides anticipated delivery date for package enroute 
SMS Tracking – enables customer to request tracking event updates to their Smart Phones. Text Tracking Number to 28777 (2USPS). eVS  July 27 2014 – Merchandise Return Service – New Service Type Code in IMpb required  July 27 2014 ‐ Hazmat Indicator – Additional Services Code (857) in Shipping Service file required  January 2015 – Proposed elimination of Business Reply Mail for all parcels Returns for Packages  New MTAC Work Groups in process of being established for: o Round Trip Label & Weigh on the Fly – Industry Co‐Chair, Paul Kovlakas – Pitney Bowes o Return to Sender/UAA – Industry Co‐Chair, Kevin Elkin – RR Donnelley ®
USPS Product Tracking &
R
Reporting™
ti ™
Shi i S i
Shipping Services File Timeliness
Fil Ti li
Shipping Information Systems
April 25, 2014
1
1
Shipping Services File Timeliness
IMpb Working Rules ‐ Proposed
File Timeliness Criteria:
Valid file received 3 hours before the first USPS physical
scan event
or
Valid file received by 0300 CT the next calendar day and
 Valid Shipping
pp g Partner Event with address information received 3
hours before the first USPS physical scan event
C
Considerations:
id ti
 USPS system delays factored in customers’ favor
 Customer system
y
delays,
y extenuating
g factors
 Force majeure
2
MTAC eVS®/PTR
User Group
Thursday, April 10, 2014
1
Agenda






Welcome (Roll Call)
PTR Update
eVS Update
Industry Feedback
Action Item Review
Questions/Comments
2
PTR Agenda







System Patches and Maintenance
New Features
Feedback on File Naming Proposal
USPS Text Tracking™
IMpb Implementation Progress
Future Releases 1.8 and 1.9
Monthly Webinars for Mailers
3
PTR Patch Updates
March 27, 2014


Implemented from 11:00 pm ET through 3:00 am ET, March 28, 2014
Internal web changes
April 4, 2014



Implemented 11:00 pm ET through 12:15 am ET, April 5, 2014
Updates to internal reference data
Added scripting for First Class International Package Services (FCIPS Labels starting with
LC through LW)


All outbound processing was suspended during these patch periods
USPS Tracking site and Call Center interfaces were fully functioning
4
New Feature
Priority Mail in mail.dat/MAIL.XML files




Allows Priority Mail in mail.dat/MAIL.XML files
Launched April 6, 2014
Translates these files to Shipping Services File v 1.7
Supports use of IMb for Priority Mail flats in a highspeed environment
5
Feedback to New Filename Proposal
 Proposed new file naming convention
 For all customer event extract files
 Example: ‘EWDELIVERY.V10.RPT.MMDDHHMMSS.xxx’ where MM
= month, DD = day, HH = hour, MM = minute, SS = seconds and
xxx = sequential number of indeterminate length
 Responses (8)
 Positive – Several responded ‘No Problem’
 Positive with stipulations
 If necessary, implement in conjunction with software release
-- July 2014 or January 2015
 Not a problem for the vendor, but problematic for customers
6
Feedback for New Filename Proposdal
 Concerns Raised
 Timing if planned for July 2014
 Competing priorities with internal changes already planned
 Replacing “detextro1.V15.rpt.MMDDhhmm”naming
convention
 Effect on vendors’ customers
 Also received suggestions for new naming conventions
7
RIBBS UPDATE
Service Type Codes updated and reposted April 1, 2014
 Banner Text Corrections




STCs 017-018 ‘USPS Parcel Return Service’
STC 795 ‘Parcel Select Returns Insurance >$200’
STCs 829-830 ‘USPS Signature Tracking #’
STC 818 ‘Critical Mail Signature Service’ and ‘USPS SIGNATURE
TRACKING’
 STCs 602-604 ‘USPS COD SIGNATURE TRACKING’
 Changed descriptions ‘Express Mail’ to ‘Priority Mail Express’ on
28 STCs
8
INTRODUCING
USPS
SMS
Tracking™
DELIVERED MARCH 27, 2014!!
9
Device-enabled USPS Text Tracking™
 USPS Text Tracking™ via device-initiated request
 Text tracking number to 28777 (2USPS)
 Enhancements to add keywords and new features – July 27, 2014
 A Progression of six USPS Text Tracking™ messages
10
Device-enabled USPS Text Tracking™
 A Progression of six USPS Text Tracking™ messages
11
Online USPS Text Tracking™
Choose update
preference
Enter text-enabled US
phone number
Choose update preference
12
IMpb Commercial Adoption By Product
Adoption Metrics for March 1-31, 2014
Class of Mail
PS LightWeight
First-Class Mail
Parcel Select
Priority Mail
Bound Printed Matter
Unspecified
Media Mail
Standard Mail Marketing
Standard Mail
Priority Mail Express
Standard Post
Critical Mail
Library Mail
Total
* Barcoded Volume Only
Source: Product Tracking & Reporting
% IMpb
97.91%
92.87%
96.99%
99.14%
97.71%
39.38%
98.88%
96.32%
96.43%
65.56%
96.97%
100.00%
57.00%
95.57%
% Address or
ZIP+4
82.78%
93.77%
93.31%
96.39%
60.85%
0.54%
92.57%
59.89%
30.84%
79.90%
91.32%
93.86%
91.25%
87.13%
% Compliant
SSF
March File Timeliness = 82.67%
96.53%
89.55%
96.54%
97.39%
70.65%
0.39%
92.88%
98.14%
28.16%
64.89%
90.46%
99.16%
50.34%
91.58%
13
IMpb Commercial Compliance
2013-2014 IMpb Commercial Transition
100%
95.94%
90%
89.60%
86.70%
80%
4/6 Address Only
83.41%
70%
60%
50%
IMpb
40%
Legacy Barcode
ALL PIECES WITH ZIP+4 AND/OR ADDRESS
30%
Compliant SHIPPING SERVICES FILE
20%
10%
4.06%
0%
14
PTR Release 1.8
 Enhancements to support visibility at institutions
 Colleges and Universities
 Callers
 Apartments and
condominiums, etc.
 New Event Codes
 Introduces Delivery Partner Event file to receive back tracking
events at USPS
 Leverages Electronic Firm Sheet to provide tracking numbers
electronically to Delivery Partners
 Will pilot with several universities in May/June 2014
15
PTR Release 1.8
Automatically Generate Second Notices and Return
Reminders


Automate the printing of PS Form 3849 (second notices)
PTR will send tracking numbers information to Post Offices via
internal My Post Office (MyPO) application
Offices will automatically print PS Form 3849 for the respective
delivery employee


Help ensure notices and returns
are processed timely


Second Notice generated
 5 days for all classes of mail
 3 days for PME/International PME
Return to Sender message generated
 15 days for all classes of mail
 5 days for PME/International PME
 30 days for certain other International
16
PTR Release 1.8
 Predictive Delivery Date Enhancements




Internal only
Reveal date in USPS.com Tracking TBD
Display Delivery Time for Priority Mail Express
Display ‘ON TIME’ when Scheduled or Expected Delivery Day equals
Predicted Delivery Day
 Predictive Delivery Day for International Packages





Internal only
Reveal date in USPS.com Tracking TBD
Expanded for Inbound international packages only
Package’s likely delivery date calculated based on enroute scans
Available for packages with electronic ZIP Code information only
 Data Distribution to additional Mailer IDs
 Extracts can be transmitted to 3 additional MIDs
 Confirmation Error/Warning reports
 Scan event extract files
17
 Link PS Form 3849 to USPS Tracking™ numbers when notice left
 Will allow tracking using the PS Form 3849 (‘Sorry We Missed You!’)
barcode # on USPS Tracking™ site and on USPS.com
 Back-end changes implemented to support future improvements
 Assists in automating the second notice
 Future launch after successful piloting
 Updates to external tracking website
 Eliminate ‘Restore’ feature for archived data
 All tracking event results seamlessly provided to customer without
18
additional steps
PTR Release 1.9
PTR Release 1.9 – July 27, 2014
 Replace Track & Confirm with USPS Tracking™
 Update Proof of Delivery letters, Return Receipt Electronic and email
notifications
 Tracking number hyperlinked directly to USPS Tracking™ results page on
USPS.com
 Replace PTS-II with PTR
 PTS-II rebranded as Product Tracking & Reporting™ (PTR)
 All references to PTS, PTS-II or Product Tracking System will be changed to
PTR™ or Product Tracking & Reporting™
 USPS Tracking search function
expanded
 Search up to 35 tracking numbers
(from 10)
 Increased by 25!!
19
PTR Release 1.9
PTR Release 1.9 – July 27, 2014
 New scan event – In Process Acceptance
 Based on enroute or Arrival at Unit event
 PTR calculates a ‘UA’ event if no Manifest or other Acceptance event
 USPS Text Tracking™ enhancements
 Adds Keywords
 All = Provides the user with the latest event and all subsequent events
 When = Provides the user with the Predicted/Expected/Guaranteed Delivery Date if
one is available
 Delivery = same as When
 Date = same as When
 Update = If the Predicted Delivery Date has changed, it will be provided
 Quiet = Allows the user to specify a range of hours during which the user does not
wish to receive USPS Text Tracking™ updates
 Awake = Cancels the ‘Quiet’ command
 Expand to other USPS mobile platforms
20
PTR Release 1.9
 By/For Enhancement
 Identifies mail owner
 Will provide extract back to parent MID without Shipping Service File if
scan event occurs before file is received by USPS
 Duplicate PICs
 New Event Code 46
 Scanner will allow packages with the same tracking number to be
delivered in the same transaction
 IMD will prompt employee ‘Is this the same mailpiece? 1: Yes 2: No’ message
 eVS will display duplicate events for each package with delivery
information
 Will be charged for unpaid duplicates per eVS rules
 Geo-location Coordinates
 Includes latitude and longitude for tracking events
 Wireless on-street users
21
PTR Release 1.9
Call Tag Service
 Allows merchant to request return label for their customer
through the Business Customer Gateway
 Two returns options
 Parcel Return Service (PRS)
 USPS Returns (Scan-Based Payment)
 First-Class Parcel Return Service
 Priority Mail Return Service
 Ground Return Service
 Options for receipt of label
 Delivery to customer’s address
 Pickup at Post Office
 Available at Self-Service Kiosk (future enhancement)
22
Delivered Subset Events
On The Horizon…
 Captures delivery location for packages
 No new event codes
Event Code will remain ‘Delivered’ (‘01’)
 Delivery location attribute
 Event description in extract file will change to identify location
 PTR will incorporate the information in scripting on the internet and
intranet web-sites
 Proposed Location Attributes
Delivery Attributes
In/At Mailbox
Front Door/Porch
Parcel Locker
Left with Individual (at Address)
Front Desk/Reception
Other at Address (Garage/Side or Back Door/Porch)
Neighbor (by Request)
23
Delivered Subset Events
Benefits of Subset Events
 Informs customers of delivery location when
package is not in mailbox
 Delivered on Sunday or holiday
 Improves customer experience
Give Us Your Feedback, Please!!
 Helpful or not?
 Comments
 Respond by COB Tuesday, April 15, 2014
24
IMpb Information for Mailers
Monthly Webinars
 Presented by Product Information and Shipping Products
 MARCH – IMpb Impacts on Returns
 APRIL – Transitioning BRM parcels to MRS
MAY – Hazardous Materials Returns (HAZMAT)
JUNE – Returns using Scan Based Payment (SBP)
JULY – IMpb Overview
AUGUST – IMpb Impact on Market Dominant products
SEPTEMBER – IMpb Impact on Extra Services
OCTOBER – IMpb Compliance
25
IMpb Information for Mailers
Webinar Schedule
All times Tuesday 10:00 am – 11:00 am EDT
For event numbers and dial-in information, visit
https://ribbs.usps.gov/index.cfm?page=industryoutreach
 MARCH 11 – IMpb Impacts on Returns
 APRIL 8 – Transitioning BRM parcels to MRS
MAY 13 – Hazardous Materials Returns (HAZMAT)
JUNE 10 – Returns using Scan Based Payment (SBP)
JULY 8 – IMpb Overview
AUGUST 12 – IMpb Impact on Market Dominant products
SEPTEMBER 9 – IMpb Impact on Extra Services
OCTOBER 14 – IMpb Compliance
26
eVS agenda
 Release schedule
 Adjustments
 Duplicate EFNs/Manifest Errors
 IMpb Assessment
 Releases




April (Patch) Release
July fixes
July Release
October Release
 eVS/PRS Dashboard
 Mailer ID
 Pub 205 updates
27
Upcoming eVS PostalOne!® Releases
2014 Planned Release Schedule
 July 13, 2014
 July 27, 2014
 October 26, 2014
TEM Release
Major Release
Minor Release
28
Duplicates EFN
 EFN must remain unique for 180 days
 Duplicate EFN with unique PICs will be populated in the Manifest
Errors Report (Jan. 26, 2014)
 The error code on the Manifest Detailed Report “Unpaid due to
Header Error”
 Manifest Errors Report (will be fixed in July)
 Number on landing page for 3c doesn’t match number of PICs on
manifest detail error report
 Manifest Detail Error Report for Duplicate EFN PICs




Entry zip always blank
Sub EFN always blank
Postage amount is $0
Some PICs are listed more than once
 The adjustment postage will be verified and calculated through manual
spreadsheet
IMpb Assessment:
 Currently still in Pilot.
 eVS is validating the data and expect to
charge on non-Compliant pieces
 The IMpb Compliance Report may not be
viewable/downloadable for some mailers
(Scheduled TBD).
 If a file is submitted after an acceptance scan
event, PTR considers that PIC to be IMpb
noncompliant.
30
April (Patch) Release
 Mail.dat now able to create Shipping Service Files
 Postage Statement Detail shall display sub-headers
 Presort Eligibility Report shall display when changing
month
 Printable Landing Page shows start/end dates based on
Calendar Month instead of Fiscal Month
 Monthly Account and Sampling Summary will accurately
reflect correction files on Line 1d
 Correct spelling issues in open adjustment notification
emails
31
July Fixes
 System shall not accept piece weight of more than 70 lbs for PM
Flat Rate Envelope and Small Box
 Presort Adjustment shall populate proposed number of pieces
 Average Per Piece Postage link on Landing Page shall be
displayed correctly
 Reconciliation report shall not include files with zero bytes
 Ineligible Content Postage Adjustment Report will be fixed to
display data
 Manifest Errors display on the landing page shall reflect pieces
associated with filtered headers
32
July Release
Proposed (for July 2014)






Update Content Eligibility calculation
Enhance Duplicate validation
Enhance POS Sampling acceptance
Enhance reconciliation email notification
Enhance the Dispute Queue
Any reversal adjustments will be displayed
on the Monthly Adjustment Summary Tab
July Release
Duplicate PICs Report link from the Report Menu
July Release
On the dispute queue landing page, the VAE
can view all the case numbers
July Release
The VAE can view details of the case, including adding
additional attachment
July Release
The VAE can attach additional files and include
comments
July Release
Displayed any Reversal Transactions
October Release
Proposed (for October 2014)
 Enhance Manifest Search Report and
enable a global PIC search functionality
 Enhance Duplicate Report to include Single
Package Search functionality
 Enhancement to extract reports
 eVS End to End Plan
eVS/PRS Dashboard
Mailer ID (MID)
 Mailers are expected to have a separate
MID for each client
 Mailers need to manage their Child/Client
MIDs
 Obtaining and issuing the MIDs
 Managing that relationship with clients
 Reporting to Postal Inspector if fraudulent
activity is suspected.
eVS RIBBS Updates
PUB 205 updates
Currently Available on RIBBS
Last Update Publication 205 – February 14, 2014
Next Update – August 8, 2014
42
Industry Feedback
Q: A HAZMAT change that was scheduled for implementation
in 2015 has been rescheduled for 2021. Can you tell us when
this will be part of a Federal Register Notice?
A: No, it will not be a Federal Register item. It was published in
the March 20, 2014 Postal Bulletin, page 4, PB#22385
43
Industry Feedback
 What is the trigger that produces the ‘Status Not Updated’ event?
 Other than the Federal Register Notice published in Dec 2013, what
publications or documents can customer find the Compliance Categories and
their corresponding compliance thresholds ?
 USPS discussed with its customers during the PTS/eVS User Group and MTAC
Meetings that file timeliness (latency) was not a significant issue and would
not be one of the 3 elements used to determine non-compliance. Why has
USPS built latency as a 4th element into its tools as a determinate for
noncompliance when it agreed it would not do so??
 Is there a timeline on when USPS anticipates using this modified process ?
 What scan event(s) trigger that a file may be considered late ?
44
Industry Feedback
 How much time prior to this scan event does USPS need the file?
 What happens when a Post Office triggers this scan event well before the
sorting of packages?
 How/when are files time stamped ?
 How much processing time does PTR need to consume a file and make it
available for use on PASS/DSS and related package routing systems ?
45
®
Shipping Services File Timeliness
IMpb Working Rules – Proposed
File Timeliness Criteria:
Valid file received 3 hours before the first USPS physical
scan event
or
Valid file received by 0300 CT the next calendar day and
 Valid Shipping Partner Event with address information
received 3 hours before the first USPS physical scan event
Considerations:
 USPS system delays factored in customers’ favor
 Customer system delays, extenuating factors

Force majeure
Action Items
1. Work Group request for Parent Control of Child Mailer IDs
2. Work Group request for File Timeliness agreement
3. Where else can the IMpb Compliance Thresholds and
general Federal Register Notice information be posted for
the benefit of new mailers?
4. Does a Delivery Attribute need to be selected? Is there a
default?
5. Canvassed members regarding Delivery Attributes
6. New filename convention – can the MID be placed in the
filename?
47
Questions?
Questions??
48