Message from discussion orange bar code
From: mstr_o...@yahoo.com (my2cents)
Subject: Re: orange bar code
Date: 24 Jun 2004 07:33:15 -0700
References: <%74Cc.3500$BV.firstname.lastname@example.org> <email@example.com> <896Cc.firstname.lastname@example.org> <email@example.com> <NLhCc.246277$hY.firstname.lastname@example.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Trace: posting.google.com 1088087602 6807 127.0.0.1 (24 Jun 2004 14:33:22 GMT)
NNTP-Posting-Date: Thu, 24 Jun 2004 14:33:22 +0000 (UTC)
the piece processed at 0500 would have the # 10 for the time and piece
25000. the piece processed at 0800 would have the # 16 for the time
and piece 25000.
Basically no one machine can process more than 25000 per half hour
increment. So each half hour, the counter resets to 0. Most automation
platforms process 25 -30K per hour. Max throughput I've ever seen is
45K per hour. That was using a test deck, not live mail.
"dbriggs" <dbrig...@rochester.rr.com> wrote in message news:<NLhCc.246277$hY.email@example.com>...
> "my2cents" <mstr_o...@yahoo.com> wrote in message
> > The ID tag (image record descriptor) is made of the following information.
> > Machine ID - 4 digit # that relates to the image lift equipment and plant
> > Mailpiece # - 1 to 24999
> > Time stamp - in 1/2 hour increments
> > Date
> > and lastly, mail class
> > Unfortunately, there is no simple decode process as with postnet barcodes.
> Interesting. What happens after machine x runs 25,000 pieces? Does the
> timestamp differentiate piece #512 @ 5:00 vs piece # 512 @ 8:00?