Presentation is loading. Please wait.

Presentation is loading. Please wait.

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

Similar presentations


Presentation on theme: "Full-Service 1 SRS 452 – Mail.XML System Requirements for Summer 2011 Release SRS 452 Review."— Presentation transcript:

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

2 Full-Service 2 OVERVIEW SRS 452 Review  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, eDOC, 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.  eDoc and Data Distribution Requirements will be discussed in this presentation.

3 Full-Service 3 eDOC System Requirements SRS 452 Review

4 Full-Service 4 eDoc System Requirements & Change Requests  Piece Data Not Required Prior to Finalization (Req 1 through 14). To allow sending MailPieceCreateRequest 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 post 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 PostageStatementCreateRequest to file preliminary postage The PO! shall display the preliminary postage on dashboard and postage report. The mailer must use ‘EstimatedIndicator” field to indicate whether PO! shall generate preliminary postage or finalized postage. SRS 452 Review

5 Full-Service 5 eDoc 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. InternationalPostageStatementCreateRequest InternationalPostageStatementCreateResponse InternationalPostageStatementQueryRequest InternationalPostageStatementQueryResponse SRS 452 Review

6 Full-Service 6 eDoc System Requirements & Change Requests  Add Validation on Copy Counts (Req 39 through 41). To implement validation to ensure that number of NonCopies and SubReqCopies combined is always equal to number of Copy count in the PeriodicalLineItemData block. The changes shall affect PeriodicalStatementCreateRequest and ConsolidatedPeriodicalStatementCreateRequest 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: ManifestCreateRequest ManifestCreateResponse ManifestCancelRequest ManifestCancelResponse ManifestTransportationUpdateRequest ManifestTransportationUpdateResponse ManifestQueryRequest ManifestQueryResponse The PostalOne! shall build both Domestic and International Manifest functionality but only International Manifest feature shall be activated in next release. SRS 452 Review

7 Full-Service 7 eDoc System Requirements & Change Requests  Implement Support for Piece Lite (Req 62 through 65). To allow support for Piece lite Record in MailPieceCreateRequest and MailPieceUpdate Request messages. This change requires adding a new complex type “PieceLiteRecordBlockType” (in final definition process with IDEA) The PostalOne! shall be modified to enhance performance of loading Piece Lite data with a target of 10K pieces in seconds. The PostalOne! 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 PostalOne! 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 PostalOne! system shall utilize existing Postage Statement messages to support priority mail. The PostalOne! system shall allow users to send Priority Mail Postage Statement as part of Combined Mailing Request The PostalOne! shall support current Priority Mail Postage Statement Parts A, B, C, D, and S. Whereas: A = Priority Mail – Permit Imprint SRS 452 Review

8 Full-Service 8 eDoc 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 The PostalOne! shall process postage statement separately for PMOD Container and separate postage for Handling Units inside PMOD Containers. The PostalOne! shall reject transactions when a mailing contains Packages inside PMOD Containers. The PostalOne! shall accept new elements IMpb and IMtb in “trayHandlingUnitType”, “bedloadHandlingUnitType”, and “maildatSummaryType” 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 PostalOne! shall accept new values “6, 7, 8, 9, 10, 11” in mailXMLContainerType simple types which stands for “OD Sack”, “OD Parcel”, “OD Full Tray Box”, “OD Half Tray Box”, “Flat Tray”, and “FRE/FRB” respectively. The PostalOne! shall accept new values “P10, P11, P12, P13, P14, P15, and P16” in rateCategoryType simple types. Whereas: P10 = Regional Rate Box A (max weight 15 lbs) P11 = Regional Rate Box B (max weight 20 lbs) P12 = Tier 1 (up to.10 lbs) P13 = Tier 2 (up to.20 Lbs) P14 = Tier 3 (up to.30 lbs) P15 = Tier 4 (up to.40 lbs) P16 = Tier 5 (up to.50 lbs) SRS 452 Review

9 Full-Service 9 eDoc System Requirements & Change Requests The PostalOne! shall accept new values “O, C, P, F” in flatRateIndicatorType 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 PostalOne! shall accept the value of “NSA” in the priceType simple type to support NSA pricing. The PostalOne! shall allow “PMODIndicator” as new element as Boolean type in DocumentVersionData block of Postage Statement message to allow Document Version designation as PMOD Type. The PostalOne! shall allow “AS” and “RAS” in ServiceCodeType simple type which stands for “Adult Signature” and “Restricted Adult Signature” respectively. The PostalOne! shall allow “FRE/FRB” value in mailxmlContainerType to support tiers. Whereas FRE is “Flat Rate Envelop” and FRB is “Flat Rate Bundle”.  Generic Changes in eDoc (Req 85 through 87). The PostalOne! shall accept new element “HoldForPickUp” of Boolean type in mailPieceBlockType, PeriodicalLineItemData, PostageStatementLineItemData, and LineItemSummaryData blocks. The PostalOne! shall make ‘PermitHolderData” element as optional in Postage Statement Create Request and Query Response messages. SRS 452 Review

10 Full-Service 10 Data Distribution System Requirements SRS 452 Review

11 Full-Service 11 Data Distribution System Requirements & Change Requests  Generic Data Distributions Requirements (Req 91 through 95). The PostalOne! shall make ‘SubmittingParty’, ‘SubmittingSoftware’, ‘UserLicenseCode’, ‘MaildatJobID’, ‘CustomerGroupID’, and ‘MailingGroupID’ optional in all Full Service messages wherever it is not currently optional. The PostalOne! shall accept new element “PushMessageID” in FullServiceDataQualityVerificationReportDelivery message to standardize the use of this field in all Full Service messages. The PostalOne! shall accept new elements “MPAID” and “MAPDescription” in PieceInfo block of the FullServiceDataQualityVerificationReportDelivery and Query Response messages.  Support New Search Filters for Start-The-Clock Report (Req 96 through 98) The PostalOne! shall start supporting “Publication Number”, “Permit Number”, “CSA Trip ID”, “Appointment ID”, “MID” filters. The PostalOne! shall make all existing filters as optional.  Implement Full Service Non-Compliance Messages (Req 99 through 106). To allow PostalOne! to identify and list all verification errors that affects the Full Service Postage Discounts. This change requires adding four (4) new messages as follows: FullServiceNonComplianceWithPostageOwedReport QueryRequest, QueryResponse, Notification, and Delivery messages. SRS 452 Review

12 Full-Service 12 Data Distribution System Requirements & Change Requests  Support Enhanced By/For Conflict (Req 107 through 112) The PostalOne! shall be enhanced to provide by/for conflict in a pair mode i.e. Mailer/Preparer By/For conflict and also for MailOwner By/For conflict. This change requires modification in ByForConclitQueryResponse, ByForDelivery, and BYForNotification 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 FullServiceStartTheClock messages without the term of “FullService” 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 PostageStatementDataType block of PostageStatementQueryResponse message where new block “STCForContainerOrTray” will be added which returns either Container Barcode or Tray Barcode at the postage statement level. SRS 452 Review

13 Full-Service 13 Data Distribution System Requirements & Change Requests  Implement Support for eInduction for Small Mailers (Req 120 through 123) To allow small eDropship mailers to associate their containers, trays, and PMOD containers information to a Postage Statement ID. This change requires adding two (2) new messages as: ContainerManifestCreateRequest ContainerManifestCreateResponse Only for these sets of messages – PostalOne! system shall allow upload of these message request file through the MDR Client. SRS 452 Review


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

Similar presentations


Ads by Google