SRS 452 Review SRS 452 Mail XML

SRS 452 Review SRS 452 – Mail. XML System Requirements for Summer 2011 Release Full-Service 1

SRS 452 Review OVERVIEW Ø The SRS 452 outlines system requirements for Mail. XML Enhancements for the Summer 2011 Release. Ø The SRS consists of 3 functional groups i. e. FAST, e. DOC, and Data Distribution. Ø FAST System Requirements are documented in SRS 421 – and have already been shared with the FAST User Group and will not be discussed in this presentation. Ø e. Doc and Data Distribution Requirements will be discussed in this presentation. Full-Service 2

SRS 452 Review e. DOC System Requirements Full-Service 3

SRS 452 Review e. Doc System Requirements & Change Requests Ø Piece Data Not Required Prior to Finalization (Req 1 through 14). ü To allow sending Mail. Piece. Create. Request message data before and after the Postage Statement. ü Req 1 through 14 documents all system requirements for PO! and SASP system to remove the validation processes/steps which require piece and physical container data or logical container information to be available at the time of postage filling or finalization. ü The piece count to postage validation needs to be conducted once the piece data upload is completed postage finalization while keeping spoilage tracking separate. Ø Allow Preliminary Postage Payment (Req 15 through 17). ü To allow filing of preliminary postage statement for MLOCR Mailing for verification support. ü The mailer shall use Postage. Statement. Create. Request to file preliminary postage ü The PO! shall display the preliminary postage on dashboard and postage report. ü The mailer must use ‘Estimated. Indicator” field to indicate whether PO! shall generate preliminary postage or finalized postage. Full-Service 4

SRS 452 Review e. Doc System Requirements & Change Requests Ø Implement International Postage Statement (Req 18 through 38). To add support for International Postage Statement feature. ü This requires adding four (4) new messages. ü International. Postage. Statement. Create. Request ü International. Postage. Statement. Create. Response ü International. Postage. Statement. Query. Request ü International. Postage. Statement. Query. Response Full-Service 5

SRS 452 Review e. Doc System Requirements & Change Requests Ø Add Validation on Copy Counts (Req 39 through 41). ü To implement validation to ensure that number of Non. Copies and Sub. Req. Copies combined is always equal to number of Copy count in the Periodical. Line. Item. Data block. ü The changes shall affect Periodical. Statement. Create. Request and Consolidated. Periodical. Statement. Create. Request message. Ø Implement Domestic & International Manifest (Req 42 through 61). ü To add support for Domestic and International Manifest mailing for tracking and possibly postage calculation. ü This change shall require adding of following eight (8) messages: • • Manifest. Create. Request Manifest. Create. Response Manifest. Cancel. Request Manifest. Cancel. Response Manifest. Transportation. Update. Request Manifest. Transportation. Update. Response Manifest. Query. Request Manifest. Query. Response ü The Postal. One! shall build both Domestic and International Manifest functionality but only International Manifest feature shall be activated in next release. Full-Service 6

SRS 452 Review e. Doc System Requirements & Change Requests Ø Implement Support for Piece Lite (Req 62 through 65). ü To allow support for Piece lite Record in Mail. Piece. Create. Request and Mail. Piece. Update Request messages. ü This change requires adding a new complex type “Piece. Lite. Record. Block. Type” (in final definition process with IDEA) ü The Postal. One! shall be modified to enhance performance of loading Piece Lite data with a target of 10 K pieces in seconds. ü The Postal. One! system shall send this data to SASP for Full Service Processing. Ø Support Priority Mail, PMOD, and NSA Mailing (Req 66 through 84). ü To add support for Priority Mail, PMOD, and NSA Mailings. ü The Postal. One! system shall implement support for Priority Mail Postage Statement (Postage Statement Number 3600 -PM) with a form type of PM which includes critical mail as part of the PM Postage. ü The Postal. One! system shall utilize existing Postage Statement messages to support priority mail. ü The Postal. One! system shall allow users to send Priority Mail Postage Statement as part of Combined Mailing Request ü The Postal. One! shall support current Priority Mail Postage Statement Parts A, B, C, D, and S. Whereas: • A = Priority Mail – Permit Imprint Full-Service 7

SRS 452 Review e. Doc System Requirements & Change Requests • • B = Priority Mail – Permit Imprint – Commercial Base/ Commercial Plus – Regional Rate Box A/B C = Priority Mail – Permit Imprint – Commercial Plus Cubic D = Priority Mail – Permit Imprint – Negotiated Service Agreement (NSA) S = Priority Mail – Extra Services • • P 10 = Regional Rate Box A (max weight 15 lbs) P 11 = Regional Rate Box B (max weight 20 lbs) P 12 = Tier 1 (up to. 10 lbs) P 13 = Tier 2 (up to. 20 Lbs) P 14 = Tier 3 (up to. 30 lbs) P 15 = Tier 4 (up to. 40 lbs) P 16 = Tier 5 (up to. 50 lbs) ü The Postal. One! shall process postage statement separately for PMOD Container and separate postage for Handling Units inside PMOD Containers. ü The Postal. One! shall reject transactions when a mailing contains Packages inside PMOD Containers. ü The Postal. One! shall accept new elements IMpb and IMtb in “tray. Handling. Unit. Type”, “bedload. Handling. Unit. Type”, and “maildat. Summary. Type” blocks which shall help identify PMOD Container Barcodes and Tray Barcodes that are as part of Trays, Sacks, Bundles or parcel on a bedload. ü The Postal. One! shall accept new values “ 6, 7, 8, 9, 10, 11” in mail. XMLContainer. Type simple types which stands for “OD Sack”, “OD Parcel”, “OD Full Tray Box”, “OD Half Tray Box”, “Flat Tray”, and “FRE/FRB” respectively. ü The Postal. One! shall accept new values “P 10, P 11, P 12, P 13, P 14, P 15, and P 16” in rate. Category. Type simple types. Whereas: Full-Service 8

SRS 452 Review e. Doc System Requirements & Change Requests ü The Postal. One! shall accept new values “O, C, P, F” in flat. Rate. Indicator. Type simple type. Whereas: • • O = Indicates Padded Envelop C = Indicates Critical Delivery Mail P = Priority Mail Legal Flat Rate Envelop F = Priority Mail Critical Delivery Mail Flat ü The Postal. One! shall accept the value of “NSA” in the price. Type simple type to support NSA pricing. ü The Postal. One! shall allow “PMODIndicator” as new element as Boolean type in Document. Version. Data block of Postage Statement message to allow Document Version designation as PMOD Type. ü The Postal. One! shall allow “AS” and “RAS” in Service. Code. Type simple type which stands for “Adult Signature” and “Restricted Adult Signature” respectively. ü The Postal. One! shall allow “FRE/FRB” value in mailxml. Container. Type to support tiers. Whereas FRE is “Flat Rate Envelop” and FRB is “Flat Rate Bundle”. Ø Generic Changes in e. Doc (Req 85 through 87). ü The Postal. One! shall accept new element “Hold. For. Pick. Up” of Boolean type in mail. Piece. Block. Type, Periodical. Line. Item. Data, Postage. Statement. Line. Item. Data, and Line. Item. Summary. Data blocks. ü The Postal. One! shall make ‘Permit. Holder. Data” element as optional in Postage Statement Create Request and Query Response messages. Full-Service 9

SRS 452 Review Data Distribution System Requirements Full-Service 10

SRS 452 Review Data Distribution System Requirements & Change Requests Ø Generic Data Distributions Requirements (Req 91 through 95). ü The Postal. One! shall make ‘Submitting. Party’, ‘Submitting. Software’, ‘User. License. Code’, ‘Maildat. Job. ID’, ‘Customer. Group. ID’, and ‘Mailing. Group. ID’ optional in all Full Service messages wherever it is not currently optional. ü The Postal. One! shall accept new element “Push. Message. ID” in Full. Service. Data. Quality. Verification. Report. Delivery message to standardize the use of this field in all Full Service messages. ü The Postal. One! shall accept new elements “MPAID” and “MAPDescription” in Piece. Info block of the Full. Service. Data. Quality. Verification. Report. Delivery and Query Response messages. Ø Support New Search Filters for Start-The-Clock Report (Req 96 through 98) ü The Postal. One! shall start supporting “Publication Number”, “Permit Number”, “CSA Trip ID”, “Appointment ID”, “MID” filters. ü The Postal. One! shall make all existing filters as optional. Ø Implement Full Service Non-Compliance Messages (Req 99 through 106). ü To allow Postal. One! to identify and list all verification errors that affects the Full Service Postage Discounts. ü This change requires adding four (4) new messages as follows: • Full. Service. Non. Compliance. With. Postage. Owed. Report Query. Request, Query. Response, Notification, and Delivery messages. Full-Service 11

SRS 452 Review Data Distribution System Requirements & Change Requests Ø Support Enhanced By/For Conflict (Req 107 through 112) ü The Postal. One! shall be enhanced to provide by/for conflict in a pair mode i. e. Mailer/Preparer By/For conflict and also for Mail. Owner By/For conflict. ü This change requires modification in By. For. Conclit. Query. Response, By. For. Delivery, and BYFor. Notification messages. Ø Implement Start-The-Clock for Non FS Mailers (Req 113 through 116). ü To allow dissemination of Start-The-Clock data to Non Full Service Mailers. ü This change requires cloning of existing Full. Service. Start. The. Clock messages without the term of “Full. Service” and addition of few elements in new set of messages. ü The changes shall be implemented as per the Mail. XML XSD Ø Implement Support for Start-The-Clock through Postage Statement (Req 117 through 119) ü To allow disemination of Start-The-Clock data at Postage Statement Level for containers and trays, when available. ü This change requires modification of Postage. Statement. Data. Type block of Postage. Statement. Query. Response message where new block “STCFor. Container. Or. Tray” will be added which returns either Container Barcode or Tray Barcode at the postage statement level. Full-Service 12

SRS 452 Review Data Distribution System Requirements & Change Requests Ø Implement Support for e. Induction for Small Mailers (Req 120 through 123) ü To allow small e. Dropship mailers to associate their containers, trays, and PMOD containers information to a Postage Statement ID. ü This change requires adding two (2) new messages as: • • Container. Manifest. Create. Request Container. Manifest. Create. Response ü Only for these sets of messages – Postal. One! system shall allow upload of these message request file through the MDR Client. Full-Service 13