1
0
-1

while analysing the ReturnQueueEntry JDFs from various DFE, I found two locations for UsageCounterLink in the AuditPool:

  • some DFE wrap it in ResourceAudit
  • some in PhaseTime
  • some in both

What is the recommended way?

    CommentAdd your comment...

    2 answers

    1.  
      1
      0
      -1

      Both are correct:

      Link in PhaseTime: The UsageCounter Stats for an individual phase. The values can be different for each one.

      Link in ResourceAudit. The overall usagecounter consumption. I agree with Brooke that this should be the prime candidate for any costing.

        CommentAdd your comment...
      1.  
        1
        0
        -1

        For the HP Indigo DFE we use both places in different manners.  

        We include the UsageCounterLink for the overall job in the ResourceAudit.  We also include the UsageCounterLink inside of one or multiple PhaseTime elements.  

        Usually the counting all occurs during a single print of the job which would equate to one PhaseTime (to represent printing) with the complete information in the UsageCounter.  But since the HP Indigo DFE can support reprinting the job, it may be that there are multiple PhaseTime elements that represent reprinting the job multiple times and each PhaseTime will reference different UsageCounter amounts (partial or full).  The sum of these referenced UsageCounters would then be reflected as the total UsageCounter referenced by the ResourceAudit.

        If you have a simple case where there is only one UsageCounter for the overall job, I think it makes more sense in the ResourceAudit.  However it is nice to link the UsageCounter to the phase time that the counts happen, like for Printing, so it also could make sense to have it in both.

          CommentAdd your comment...