[684] in Enterprise Print Delivery Team
Re: Accounting
daemon@ATHENA.MIT.EDU (David F Lambert)
Wed Nov 15 07:39:01 2000
Message-Id: <10011151238.AA16090@MIT.EDU>
Date: Wed, 15 Nov 00 07:32:45 EST
From: David F Lambert <LAMBERT@MITVMA.MIT.Edu>
To: "Lynne E. Durland" <durland@MIT.EDU>,
Enterprise Printing Delivery Project Team <printdel@MIT.EDU>
In-Reply-To: Your message of Tue, 14 Nov 2000 19:28:41 -0500
On Tue, 14 Nov 2000 19:28:41 -0500 you said:
>Greetings Teamies,
>
>I have been slogging through the manual this evening. The accounting exit
>is doing what it was designed to do and there is no apparent way to
>increase or change the information put into the log. We get what we
>get. There is no flag for simplex and duplex.
>
>I am still struggling with the postscript accounting and have exchanged
>more email with Banta to pursue this issue.
>
>One way for us to be able to account for simplex/duplex issue is to set up
>logical destinations, that only allow one or the other......therefore by
>sorting by logical destination, we would know that everything that came out
>of logical destination x, is really npages in report, minus 1 divided by 2
>(a duplex logical destination).
>
>This is an option and possible pain in the cookies to maintain, but I am
>just trying to think some of this through to allow us to be able to
>distinguish simplex, duplex printing to try and provided
>incentives/disincentives for doing same.
>
>I will pursue more of the postscript accounting and printing of copies
>tomorrow.
>
>Lynne
My suggestion would be to:
- clearly understand what data is available from the accounting exit
and elsewhere (such as the logical destination info)
- develop the best cost allocation/chargeback model we can based
on that available data
- develop a list of additional data we would like from the accounting
exit with justification
- petition IBM to enhance the product with the additional requested
accounting information
Dave
