1.1Container Manifest Based eInduction
1.1.1Description and Priority
Seamless Acceptance eInduction shall provide the capability to mailers to link postage with barcodes and possibly with appointments or their locale keys in a multi-party business transaction. In this specific case, the main role played by the postage payer is either through Postal Wizard or the postage payer used hard copy postage statements which were then manually entered by the PostalOne! BME personnel. Once Postage is paid through PW or through PO! Manual interface the postage statement ID is passed to the Consolidator by the originator. Consolidator generates the IMcbs, labels the containers, links the container barcodes with the statement Id and passes to the PO! System through Mail.XML web services or through Mail.dat Client manual upload of a Mail.XML message file.
Figure 1.0
Figure 1.1 – Container manifest Message
1.1.2Stimulus/Response Sequences
- Mailer prepares a mailing and file postage through paper or PW interface.
- Mailer Receives a postage Statement ID
- Mailer takes the mail to a consolidator
- Consolidator creates a FAST appointment
- Consolidator creates IMcbs, labels the pallets, creates the Container Manifest with postage statement ids, adds appointment data (optional) and sends to PO!
- PO! Runs eInduction pre-induction validations and sends the data to SV for scanning and shares the data with SASP
- SV performs scanning and closeout upon shipment arrival
- SV sends the san data to SASP for non compliance validations
- SASP sends the data to PO! Near real time to make operational reports available
1.1.3Functional Requirements
REQ 1.:The eInduction system shall receive the Container manifest create request through the Mail.XMLweb services layer as well as through the mail.dat client upload.
REQ 2.:The eInduction system shall validate the data in the container manifest message is valid and shall generate a Container manifest report with Container grouping ID, Appointment ID (optional for pre induction, required for post induction), Entry Facility Name, facility Type, Locale key (shall send to all Locale keys valid for the logical Entry point, if physical Locale key is not provided), shall get the Entry Point Zip code from the postage statement if not available in the Container Manifest Create request, shall show pre induction (status), Induction (status), container count, extra container count, type (container), estimated Arrival date, Scheduled Arrival Date/time, Closeout Date/time,StartTheClock date, and Postage paid (postage statement link.
The eInduction system shall validate entry point discount, postage finalized, barcode valid and missing validations, barcode on a single appointment before releasing the containers to SV for induction.
REQ 3.:The eInduction system shall release containers to all valid locale keys tied to the Entry point zip code in the postage statement, if specific locale is not present in the Container manifest create request.
REQ 4.:The eInduction system, in case of mail directions to multiple facilities, shall send the e8125/e8017 to both facilities; the original and the redirected when appointment data or locale key is provided as part of the Container Manifest create request.
REQ 5.:The eInduction system shall receive all post-induction scan data from SASP and shall report post-induction validations to identify discrepancies such as: missing, misshipped, misscheduled, extra, and entry point discount errors in the container detail report accessible through the container count link in the Container manifest report
REQ 6.:The eInduction system shall only make the container scan data available to paid service subscribers (TBD) on the container manifest report.
REQ 7.:The eInduction system shall make the Container manifest report available to the Owner of the postage statement, to the Container Manifest create request submitter, and to the preparer identified on the postage statement.