Leave feedback
  • Discussion

    Print Shop - Advanced Co-enveloping Statistics

Enter a new topic
  • Vyv Lomax Vyv Lomax Administrator
    0 likes 3839 views

    I need to create an advanced set of statistics for co-enveloping with Post Processing.

    I have a customer that collects print jobs for a range of other customers and sends them to a print shop for print. All of the customers share the same customer register and they hope to gain efficency by co-enveloping common customers. They then get an invoice for the amount of print.

    The co-enveloping is working yet the issue is - who pays for what? The savings in postage needs to be sent on to the end customer.

    How can co-enveloping be shown in statistics? E.g.

    1) Customer A has 1 000 envelopes

    2) Customer B has 1 000 envelopes

    3) Customer C has 20 000 envelopes

    4) Common customers reduce the total 22 000 to 12 000 envelopes - where 90% of A's envelopes are inserted into C's. (As well as efficiency on C's and some minor for B's).

    So who should get the rebate? How can we calculate the amount of co-envelopes? The total is easy to calculate yet the total by customer would be very interesting to know.

    A discussion please.

    Monday 18 January, 2010
  • Jacob Granert Jacob Granert StreamServe Employee

    At a customer I worked with there were rather complex requirements for statistics.
    They have many customers, with many different print jobs with documents that shall be delivered in multiple channels, and some documents that shall or ought to be co-enveloped.
    They print in many locations in Europe and use many different postal companies.
    So, there is a many-to-many relationship between input and output documents.
    The production in different channels also has different timing. For instance, they want to run the archiving jobs during night time since they have free capacity then.
    Another example, the print shop must get the print job that shall be sent with priority mail at twelve noon at latest, but the economy mail can be delivered until five o'clock.

    So, they have many post processors. And each one shall deliver structurally identical statistics.
    That circumstance drives design requirement 1, namely - it shall be very easy to implement advanced statistics in a post processor.

    We ended up with a design like the picture. Everything within the dotted square is implemented as a global resource set and a StreamServe project. From the post processor there are circa 10 possible functions to call in the API.



    Monday 18 January, 2010
  • Vyv Lomax Vyv Lomax Administrator

    I would like to focus on the actual details a bit more:

    I guess it would be easy to identify the unique number of Envelopes by the unique total of $DOC_TRIGGER. Yet knowing if there is only 1 document in an envelope or if there are 4 will have to be done in another stage by crunching the numbers.

    Costs could be distributed by:

    ·Startup fee (usually fixed)

    ·Administration costs (dynamic)

    ·Paper used

    ·Envelopes used


    Has anyone made a calculation based on items like these?


    Monday 18 January, 2010
  • Jacob Granert Jacob Granert StreamServe Employee

    We found that is necessary to separate the final cost calculations from the actual gathering of statistics since the cost calculations can, and will, vary depending on many things that you don't want to hardcode into the pre processing solution.

    Besides, we found out that we really wanted to have the meta data ENVELOPE_TRIGGER, and not rely on the document trigger. There are a number of good reasons for it. Consider it.

    Postal base cost vary typically on envelope size (S65, C5, C4, Small Box, Large Box or whatever), weight (in grams), mail class (economy, international, express, …), destination (domestic, international, ...) and postal company. Then you of course have the sorting and optimization that might yield in different rebates, but those tend to be calculated very late in the process, sometimes not until the postal company calculates the invoices.

    So, what can you keep track of in the post processor?

    -The customer

    -The destination. A comment on this one. We found out that it is important that you keep track of where the stuff is printed and delivered to the postal company, since that will ultimately decide what is domestic. We had a case with the Norwegian branch of the company having customers actually living in Sweden, and the Norwegian branch invoices was printed in Norway, so the customers living in Sweden got international mail delivered by the Norwegian post. We considered splitting jobs on destination so as much as possible would be printed locally, but it turned out to be too complex given physical inserts, pre printed papers and envelopes.

    -The weight (including inserts, and only counting inserts once when co-enveloping)

    -The envelope size

    -The mail class

    -The postal company

    -The number of pages

    -The number of sheets

    -The number of envelopes

    The final rating of the cost per customer is done in the economy system.

    Monday 18 January, 2010


Latest from the blogs