MTAC MAIL IRREGULARITY FEEDBACK WORKGROUP MTAC Presentation May 8, 2003

MTAC MAIL IRREGULARITY FEEDBACK WORKGROUP POSTAL CO-CHAIRPATRICK KILLEEN INDUSTRY CO-CHAIRJOYCE MCGARVY

DESIRED OUTCOME Implement Web Enabled Continuous Process Improvement Capability –Identify; Issues Impacting Efficient Mail Processing of Business Mailings –Inform; Process Owners of Identified Impacts –Improve; Through Information Management and Reporting

DESIRED OUTCOME Business Capability To: – Identify; Via Web 3749 Process – Mailing Identity (Preparer/Owner), Details of Problems, and Processing Impacts – Inform; the Mail Owners, Mail Preparers, and USPS Business Process Owners – Via the Internet (Web Reports), Messaging, and System to System Interfaces – Improve; Through Data Analysis, Information Management, and Continuous Feedback

LATEST STATUS As a Result of Informal Pilot Tests The Following Improvements Have Been Implemented: –Improved Data Collection Process –Improved Data Entry Interface –Issue Status Tracking and Customer Contact for Resolution Interface for the Business Mail Entry Unit (BMEU) –A Data Exchange Interface Between PostalOne! and the Business Service Network (BSN)

CURRENT STATUS Pilot Test Currently in Progress –NJ BMC –Monmouth P&DC –Princeton REC Pilot began May 1 will conclude May 22 Pilot will test functionality of the following enhancements

CURRENT STATUS Data Collection and Data Entry –Data Collection Process that Facilitates the Improved Data Entry Interface Issue Status and Resolution Management –BMEU Issue Status Tracking and Customer Contact Interface PostalOne! / BSN Data Exchange –System to System Data Exchange

Mail Irregularity Data Entry Forms Resolution Search Disposition Report Resolution Forms Reporting –By Container Type –By Package –By Time

DATA ENTRY SCREEN - 1

DATA ENTRY SCREEN - 2

DATA ENTRY SCREEN - 3

RESOLUTION SEARCH

MIR DISPOSITION REPORT

RESOLUTION SCREEN - 1

RESOLUTION SCREEN - 2

MIR by CONTAINER TYPE

MIR by PACKAGE

MIR by TIME

OBSTACLES Business Process Needs to be Defined Outstanding Issues –Identity;  Mailing Identification; Need Process to Accurately Identify the Owner & Preparer  A meeting is scheduled for June 17 at the Chicago office of Crain Publications  Any mail owners or preparers who are interested in attending this meeting, please notify Joyce or Patrick

OBSTACLES Outstanding Issues (continued) –Inform;  Mailer Notification; Who Gets Notified (Owner or Preparer or both) and When  Identification of Urgency and Magnitude of the Problem  A meeting will be scheduled in July to resolve this issue. If you are interested in attending, please notify Joyce or Patrick

Challenges Technical Process –Identity;  Implement intelligent mail capabilities –Improve;  Implement mobile data collection and RF infrastructure

TIMELINE Rollout Of Improved Data Collection And Data Entry Interface ( Nov 2002) A Limited Pilot Test Of The BMEU Interface (Status Indicator and Contact Management) (Nov 2002). Pilot Test Now In Progress – May 2003 Software Modifications – June 2003 Expanded National Pilot Test – August 2003 National Implementation - Fall 2003

Report Card Rollout Of Improved Data Collection And Data Entry Interface ( Nov 2002)  A Limited Pilot Test Of The BMEU Interface (Status Indicator and Contact Management) (Nov 2002).  Expanded Pilot Test Began May 2003  National Implementation Fall 2003 New IBSN implementation June 2003 – possible impacts here 

QUESTIONS ?