Subgroup Mail.dat Status Receipts and Receipt Polling 1 Outcomes and Recommendations
Participants 2 Jim Morton, (industry co-lead) Quad Graphics, Linda Gustason, Quad Graphics Steve Krejcik, PBPS Dave Probst, PBPS Eric Thens, PBPS Steven Filippine, PBPS Rose Flanagan, Data-Mail Lloyd Moss, Windowbook Ruth Schmidt, USPS (co-lead) Phillip Parrish, USPS Kelly Matheis, USPS
Charter 3 Task Team: Mail.dat Status Receipts\Receipt Polling Description: Review current functionality for Status Receipts\Receipt Polling. Review open defects/items and reach consensus on solution approach for each. Solicit industry feedback for simplification and enhancements including: limiting some of the 3 formats (ASCII, XML and enhanced XML), configuration of receipt download enablement, additional notifications or status, other submission or billable filter levels, and additional fields. Open defects/items include: Mail.dat - Receipt files not including transfer-status field Mail.dat - Postage Statement ID is not being populated in the Receipt files for cancel submission Mail.dat - Enhance Container ID returned in receipts Mail.dat - Generate only 1 receipt record for each Job ID for Enhanced XML 6920 – Mail.dat - Mail.dat Mailer Received Incorrect Receipt Information Mail.dat - Group receipt records by Job ID Mail.dat - Postage and Copies/Pieces on receipts not matching the Postage Statement ID Timeframe: 5 meetings Definition of Done: Solution approach for each open defect\item. Additional goals: Updated documentation of Status Receipts in the Postal Service Mail.dat Technical Specification. User Stories for enhancements and simplification.
Recommendations 4 ETR / CR / COM Issue Description Issue Resolution Planned Implementation 5625Postage Statement ID is not being populated in the Receipt files for cancel submission (populated with "N/A"). Populate with the Postage Statement ID in the PS-cancelled event type R Mail.dat Mailer Received Incorrect Receipt Information (server-validation field does not include postage statement errors like 7028 mapping error) ASCII, XML, and Enhanced XML are updated so that,, and fields include Postage Statement failures (ex: Error Code 7028) and only severity ERROR validations R Postage and Copies/Pieces on receipts not matching the Postage Statement ID (Delete event type incorrectly returning receipts for each CON Periodical statement.) Job-deleted event updated to only return Master/Children PE with correct,, and. R Electronic Confirmation Acceptance Notice (ECAN) Barcode for eDoc mailers A new field is added to the Enhanced XML billable level receipt type after the tag. R Receipt files not including transfer-status fieldAdd record-type field to Job-deleted event so all events begin with "transfer-status" and can be parsed correctly R Enhance Container ID returned in receiptsUpdate field so that the value returned is the lowest.csm Container ID that has associated.cqt records on all applicable events within enhanced XML billable receipts. Future 1756Group receipt records by Job ID (currently no ordering set) ASCII, XML, and Enhanced XML receipt records are grouped by Job ID. Future 2413Generate only 1 receipt record for each Job ID for Enhanced XML Close and submit revised requirements as 7459Future 7479Remove “extra” Job-deleted events, limiting event creation to only when a job was actually deleted Discontinue notification informing mailer job has not been deleted. Future
Recommendations (Continued) 5 Recommendation Benefit Consensus EffortTimeframe (7455) Incorporate clarifications into PostalOne! Mail.dat Technical Specification Prerequisite events, Postage statements (master/child) in the billable- level, availability (14 days and intermediate download), summarized receipt fields ClarityNoneMinimalNext Publication (7456) Standardize to single format of “Enhanced XML” Remove ASCII format support, renaming Enhanced XML to XML remove XML, keep Enhanced XML, renaming it “XML” Reduced USPS maint. USPS / UG1 Medium3 month industry lead time (7457) Default receipt generation to disabled Set status.receipt.enabled=Disabled in mdrsettings.conf and incorporate an additional client batch mode which overrides the configuration. Other users can re-enable in settings or mdrsettings.conf. Reduced system load USPS / UG1 Medium3 month industry lead time (7458) Clean up Receipt fields Remove post-processing internal error event across all receipt formats. Remove,, fields across all events/all receipt formats. Modify and fields to only display information with error-level severity (exclude warnings). Add new fields Add and field to display information with warning-level severity across all events/all receipt formats. Add to display first.mpa MPA – Unique Sequence/Grouping ID from job for Enhanced XML billable-level. Re-order fields across all events to be sequential Streamline Receipts USPS / UG1 Large3 month industry lead time
Recommendation Benefit Consensus EffortTimeframe (7459) Suppress prior events and include sequential fields for submission and billable levels with both a result and result timestamp Baseline Enhanced XML submission-level and billable fields to include sequential fields following various statuses of mailing throughout PostalOne! submission. Only download latest aggregate receipt event with the latest receipt event including statuses on all events that have occurred before most recent event. Re-order fields across all events to be sequential Reduced System Load, Reduced ambiguity, additional USPS / UG1 Large6 month industry lead time (7460) Write batch validation failure directly to receipt folder Timely Response USPS / UG1 Medium3 month industry lead time (7478) Override feature to retrieve receipts for specific time period Configure start and end date and download receipts even if the receipt has already been download New feature USPS / UGI Medium1 month industry lead time Recommendations (Continued) 6
Next Steps 7 Review Outcomes and Recommendations with UG1 Next Steps for each Recommendation: Recommendation (7455): USPS incorporate Guide updates into next publication Recommendation (7456): Survey UG1 participants who use ASCII for removal or re-baselining Recommendation (7457, 7458, 7459, 7460, XXXX): Survey UG1 participants for impact and prioritize with other system enhancements Plan delivery of recommendations over next releases