Post Processing Session 4 november 2009 Anders Ekström, Alexander Kennard

1. Post Processing Session 4 november 2009 Anders Ekström, Alexander Kennard

2. Who uses the Post Processor? • What are you doing with it? • What values are you achiving by using the post-processor?

3. StreamServe 4.1.1 introduced post processing concept in 2004 • Initial use were for high volume print • StreamServe Post Processor history Before post processing Post processing

4. Vad kan namnet komma ifrån? • Post - Postväsen, organiserade försändelser av brev och paket. • Post-, latinskt prefix som betyder "efter". • The concept of post processing Post Process Process Sorting, Enveloping and driver Layout and document composition • Layout requirements • Business • Marketing • Postal-operator savings • Printer environment • IT-infrastructure

5. Usual project configuration ”Best Practice” Online output connectors in layout projects Fax, email, local print, other Layout project 1 Online channels Online channels Online channels Layout project 1 Post processing Layout project 1 Post processrepository High volumeArchive Business system Common post processing project StreamServe layout projects High volume print & archiving

6. Basic StreamServe flow • The concept in more detail Job Message OutQ Event Process InQ Outconnector SDR-connector Inconnector Postprocessorrepository (device independent) OutQ Inconnector Outconnector PPQ StreamServe Postprocessor flow

7. Why do you want to post process? • Cost reductions • Postage savings • Co-enveloping, less stationery • E-inserts • Discounts on printing • Performance • Environmental savings • Post production functionalities and statistics gathering • Customer experience • “Driver ready packs” • Improve manual handling • Minimize manual handling

8. Capabilities

9. Postprocessor Repository / Job / Runtime • Document Broker • PPQ (Post-Processor Query) • Statistics • Mailmachine (%{TARGET}) • Stored variable / Meta data • Sheet Layout • StreamServe Post Processor Terms and Functions

10. Resource repository • Document trigger • Scripting • StreamServe Post Processor Terms and Functions $doc_id = GetFirstSegDoc(); while (num($doc_id) > 0) { $DocType = GetSegMetadata($doc_id, "DocType"); switch ($DocType) { case "A": $DocTypeA++; break; case "B": $DocTypeB++; break; case "C": $DocTypeC++; break; default: $DocTypeRest++; } $doc_id = GetNextSegDoc($doc_id); }

11. Sending one or more ProductionOrders to StreamServe for further processing. Each ProductionOrder can have 0-many Operational drawings in pdf format that needs to be printed together with the ProductionOrder. • Post Processor scenarios 1

12. One or more ERP systems send xml-invoices for processing in streamserve. The xml-files are divided into smaller files for simpler handling and higher performance. Sending of AFP files to the printshop is done 3/week • Post Processor scenarios 2

13. In this case there are two document types (AccountStatement / Daily) that we would like to send in the same envelope to the customer. • Post Processor scenarios 3

14. In this scenario the customer create PPQ for preview purpose before each batch is sent to the printshop. If ok a new PPQ file is generated and all documents in Postprocessor Repository is selected. • Post Processor scenarios 4

15. Short Demo all components that are included in a PostProcessor project. The sample project have the same architecture as scenario 4. • DEMO