Patent Application
20070098217
This disclosure is directed to the field of processing delivery items. More particularly, this disclosure relates to methods and systems for processing mail and other delivery items within a universal coding system.
Conventional systems for identifying and processing delivery items, including mailpieces, require both manual and mechanical operations. The manual operations are initially required to load the mail from a mail delivery repository into a mechanical identification and mail processing system. Mechanical operations then attempt to identify the delivery address for each mailpiece and, if successful, to then process each mailpiece based on the delivery address. Processing a mailpiece can be, for example, sorting the mailpiece, batching the mailpiece, applying a code to the mailpiece, etc. If there is a failure to identify the delivery address of a mailpiece mechanically, human operators are required again to identify the delivery address. Likewise, if there is a failure to process the mailpiece based on the delivery address, human operators are also required again to process the mailpiece. Therefore, conventional systems for identifying and processing mail depend on human operators if mechanical systems are unable to identify or process a mailpiece.
To identify mail in conventional systems, mail is loaded into a mechanical identification system, which automatically feeds each mailpiece into an optical character reader (OCR) machine. The OCR machine then attempts to electronically “read” the delivery address from the mailpiece in order to place the delivery address ZIP™ Code in a computer. If the OCR machine cannot read the delivery address (e.g., the ZIP™ Code), the mechanical device rejects the mailpiece. The rejected mailpiece may then be fed into another mechanical device, which presents the mailpiece to a human operator, who physically reads the delivery address off the mailpiece and enters the delivery address into a computer. Once the delivery address has been placed either electronically or physically into a computer, the computer prints delivery information on the mailpiece, using a special code (e.g., a bar code, such as a POSTNET code).
The majority of conventional mechanical processing systems sort each mailpiece based on a special code, such as a ZIP™ Code or POSTNET code. These mechanical processing systems may contain an optical character reader (OCR) that can read and sort a mailpiece based on its ZIP™ Code. These mechanical processing systems may also contain a Bar Code Sorter (BCS) function, which can read and sort a mailpiece based on the bar code such as the POSTNET code. If the mechanical processing system cannot read either the ZIP™ Code or the POSTNET code, the system rejects the mailpiece. The rejected mailpiece may then be processed by a human operator. The human operator may then determine why the mechanical processing system rejected the mailpiece, solve the problem (e.g., determine the ZIP™ Code or reaffix the POSTNET code to the mailpiece), and then reload the mailpiece into the mechanical processing system for processing.
To improve upon conventional systems for identifying and processing mail, the United States Postal Service developed an automated sorting system, described in U.S. Pat. No. 4,992,649 (the '649 patent). One embodiment of the system disclosed in the '649 patent is a Remote Bar Code System (RBCS). The embodiment of the RBCS described in the '649 patent provides for the electronic sorting of mail using a bar code that is placed on the front of each mailpiece, known as the POSTNET code, and another bar code that is placed on the back of each mailpiece, known as the identification tag (ID Tag).
In RBCS, the POSTNET code corresponds to the delivery address for the mailpiece, and the ID Tag corresponds to the unique identity of the mailpiece itself (i.e., the ID Tag code is a way to “identify” each particular mailpiece). The POSTNET code represents a copy of the ZIP™ Code in bar code format, and the POSTNET code can be used to route a mailpiece, if the ZIP™ Code cannot be read. The ID Tag represents a unique code in bar code format, and the ID Tag can be used to identify each particular mailpiece, if the RBCS cannot otherwise identify the mailpiece. For example, in the RBCS, the ID Tag can be linked to an electronic image of the mailpiece marked with the ID Tag and/or POSTNET code by the RBCS. So, if the RBCS cannot identify a mailpiece, the RBCS can recall the electronic image of the mailpiece, which contains a destination address, including the POSTNET code.
The identification and processing of mail in the RBCS is dependent upon the use of either the POSTNET code or the ID Tag. When each mailpiece is identified by the RBCS, the ID Tag is first stored temporarily until the mailpiece receives the POSTNET code and has been processed by the RBCS. If the POSTNET code becomes illegible during processing, the ID Tag may be used to obtain the POSTNET code. The ID Tag is used to store the POSTNET code in a short-term memory until the RBCS has processed the mailpiece based on the POSTNET code. However, once the mailpiece has been processed and sorted based on the POSTNET code, the RBCS can no longer access the ID Tag, because the RBCS cannot store unlimited ID Tags locally.
Thus, in certain situations, the POSTNET code cannot be read by the automated mail processing equipment. For instance, the POSTNET code on a mailpiece might be illegible as soon as it is applied due to the color or pattern of the mailpiece. If so, the mailpiece may be fed into a letter mail labeling machine that applies a white label to cover the illegible POSTNET code, and then, the mailpiece may be again fed into the RBCS for identification (and printing of a new POSTNET code on the white label). Additionally, the POSTNET code might be legible when applied, but become illegible during subsequent processing of the mailpiece. Because the ID Tag is only stored until the completion of the initial processing, the RBCS cannot use the ID Tag to identify the POSTNET code during subsequent processing and sorting. Therefore, if the POSTNET code becomes illegible during subsequent processing, the mailpiece can no longer be sorted automatically by the RBCS. This diminishes the efficiency of the systems for identifying and processing mail and requires excessive human intervention.
Methods and systems are disclosed for processing mailpieces. Images of mailpieces processed by a first mail processing device and a second mail processing device are captured. The images are stored in a coding system at a mail processing plant, and the images are sorted at the coding system according to characteristics of the images. The images are transmitted from the mail processing plant to a remote location. An encoding center at the remote location processes the images to obtain mail processing data from the images. Mail processing data is transmitted from the encoding center to the mail processing plant, and the mail processing devices process the mailpieces using the mail processing data from the encoding center.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed.
Reference will now be made in detail to exemplary embodiments of the invention, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts. Although embodiments consistent with the invention are described with reference to a mail system, the invention is not so limited. Rather, the invention may also be employed in other types of delivery systems.
I. Overview of Universal Coding System
To provide improved performance in the RBCS, the United States Postal Service developed the Identification Code Sorting (ICS) system, which is described in U.S. Pat. No. 6,894,243, and the Universal Coding System (UCS). These systems identify and process mail and other items such as forms using a redundant identification code within a global identifying and processing system. Embodiments of the present invention may be practiced with systems such as the RBCS, ICS systems, and UCS.
A. POSTNET Code
B. Identification Tag (ID Taq)
As shown in
If POSTNET code 202 is not legible, UCS 500 may use a special machine or method to identify and process mailpiece 100 to a destination address based on ID Tag 204. If ID Tag 204 is legible, UCS 500 can obtain POSTNET code 202 from a database and thereby identify and continue to process mailpiece 100 to the destination address. If this occurs, UCS 500 may reapply POSTNET code 202 to mailpiece 100 and again attempt to identify and process mailpiece 100 to the destination address 200.
II. Detailed Description of Universal Coding System
Mail processing devices and systems process a variety of mailpieces, also referred to as delivery items, and other items, such as letters, flats, packages, bundles, scanned forms, etc. Part of this processing often involves automated reading by, for example, a bar code reader or optical character reader, etc. When a mailpiece cannot be processed in this way, an image of the mailpiece is used to complete processing. In the Universal Coding System (UCS), the image may be presented to an operator at an image encoding center, such as a Remote Encoding Center (REC), for data entry. The REC, also referred to as a REC UCS, may be at a location remote from the processing facility where the actual mailpiece is being processed. Once the address of the image is resolved, i.e., once the operator obtains the needed information from the mailpiece image, the delivery information is returned to the processing facility and the mailpiece is further processed. Often, the delivery information, also referred to as mail processing data or item processing data, needs to be returned within a matter of minutes or seconds to keep pace with the mail processing equipment handling the physical mailpiece.
Prior to processing these images, the Plant UCS 502 may create a specific coding strategy to determine which coding steps should be performed for an image based on the image attributes. The coding strategy drives the depth of code, for example, a certain number of digits of a delivery point code, that is required to sort some mailpieces, and in some instances, the Plant UCS 502 may send the coding strategy or sort plan to the REC UCS 504. To process the images, the Plant UCS may communicate with Output Subsystems (OSS) 558 to determine information required for Output Subsystem (OSS) processing. In addition, after processing, the OSS may apply a POSTNET code corresponding to the result data provided by the REC UCS to the mailpiece.
The Plant UCS may also be connected to: User Interfaces (UI) 524 to provide access to system functionality and statistical displays; Remote Computer Readers (RCR) 526 for optical character recognition; an interface to the National Directory Support System (NDSS) 532 for directory downloads; a Tray Management System (TMS) 534 to synchronize timing of processing; additional offline optical character reader systems, such as a Future Reader Pool 546; and a Local Keying function 560 for manual entry of delivery address data to obtain delivery information. The Plant UCS may also interface with an Integrated Data System (IDS) 544 which collects data from mail processing equipment.
The Plant UCS may include: Image Handlers (IH/AFR) 528 to control the handling/processing of the image files; Image and Result Managers (IRM) 530 to handle results of the encoding and OCR processes. The Plant UCS 502 may also include interfaces with other sorting systems, including Identification Code Sorting (ICS) 536, Flats Identification Code Sorting (FICS) 538, APPS Identification Code Sorting (AICS) 540, and Change of Address Record Server (CARS) 542. For example, the UCS 500 may process and identify mailpieces and other items for these other sorting systems. One having skill in the art will appreciate that UCS 500 may be capable of interfacing with additional form and data servers and systems. For example, the UCS 500 may send incomplete forms to a REC for keying additional data elements and forward the resulting information to a non UCS database. In one embodiment, Plant UCS 502 may also be able to communicate with one or more other Plant UCS.
The Plant UCS 502 may communicate with, and transmit images to, the REC UCS 504 via T1, MNS+, vBNS or other Wide Area Network, such as the Internet. At the REC UCS 504, mailpiece images may be received from one or more Plant UCS such as Plant UCS 502 and are processed by operators who view the mailpiece images and enter information about the corresponding mailpiece into a computer. The images are thus processed at the encoding center at the remote location in the sorted order to obtain mail processing data from the images.
The REC UCS 504 may also receive test harness images, which are images tagged by ILUs at mail processing equipment and which set the value within the image header providing details of the required encoding devices. REC UCS 504 will receive tagged test harness images only if the value set within the header requires the image to be keyed by the REC UCS. The test harness images will be sent to a REC UCS even if the image is finalized by another device, such as a MPE or a RCR.
The REC UCS 504 may include Supervisor User Interface computers 548 and Universal Coding Desks 550, also referred to as universal video display terminals. In one embodiment, REC UCS can process mailpiece images from all types of mail processing equipment. REC UCS Image and Result Manager IRM 552 controls the results handling of the encoding or OCR process and the REC UCS Image Handler (IH/AFR) 554 controls the handling/processing of image files. The REC UCS 504 may communicate with Web Remote Encoding Center Operations Analysis Database System (WebROADS) 556 to provide analysis of REC UCS processing. REC UCS 504 may also include a Video Coding System (VCS) for controlling image flow, a reader pool for character recognition, a connection to a Change of Address Record Server (CARS), and a connection to the National Directory Support System (NDSS).
In UCS 500, unresolved images (e.g., mailpiece images or form images) are captured from mail processing equipment, also referred to as mail processing devices, within a plant. The images are sent to Plant UCS, such as Plant UCS 502, where the images are stored and then sent to one or more Remote Encoding Centers (REC UCS) such as REC UCS 504 for processing. In an embodiment, unresolved images, partially resolved images, and finalized results are received by the Plant UCS. The images may also be sent to a reader pool within Plant UCS 502 or to the Local Keying function 560 before they are sent to REC UCS 504. Within REC UCS 504, the REC operators, or keyers, may be presented with images based on prioritization of the recognition system, as well as the total number of images of the mailpiece. REC operators at Universal Coding Desks 550 view the unresolved images and input mailpiece address data into the Universal Coding Desks 550. The mailpiece address data may be, for example, a full or partial ZIP™ Code, name, street address, city, or state, or some combination of these, and may be input by keying or by voice encoding. Universal Coding Desks 550 may have the capability to process images captured by multiple types of Input Subsystems 506-522, and in one embodiment, Universal Coding Desks 550 have the ability to process images captured by all types of Input Subsystems 506-522 and including letters, flats, parcels, address block, Region Of Interest (ROI), Postal Automated Redirection System (PARS), and ECM and COA forms. A Universal Coding Desk display may include the site name, machine type, machine number that lifted the image, and if applicable, induction/feeder number and/or camera number.
After a REC operator has input address data, the REC UCS 504 further processes the images by querying information databases, such as address information databases, using the address data to resolve the image. Resolving the image may involve providing a POSTNET code, providing a ZIP™ Code, or providing a delivery point code which has been processed to achieve the most information about the address (the finest depth of code) that can be obtained from the database for that address. The REC UCS 504 may then store the result information, also referred to as mail processing data or sorting data, and then returns the needed information to the Plant UCS 502, the Output Subsystem 558, or to the Input Subsystems 506-522. The mail processing data may be a graphical code, a delivery point code, a ZIP™ Code, or a POSTNET code. If REC UCS 504 provides the sorting information to the Plant UCS 502, Plant UCS may then send the sorting information to the Output Subsystem 558, the Input Subsystems 506-522, or to an identification code server for local access by a sorter if the identification code server is not integrated into UCS. In one embodiment, Plant UCS 502 sends sorting information, also referred to as mail or item processing data, to the Output Subsystem 558 or the Input Subsystems 506-522 in response to a request or query for the mail processing data sent by the mail processing device, such as the Output Subsystem 558 or the Input Subsystems 506-522.
The UCS may also support remote OSS capability, or the ability to provide output data such as the delivery point code to a different plant than the plant from which the image was sent and ultimately to a different mail processing device than that which captured the image. In this manner, the mailpiece can be transported to a final destination or an intermediate processing hub based on available address data while the delivery point code is determined to the finest depth of code possible by the REC.
In one embodiment, Plant UCS 502 and REC UCS 504 may have overload protection mechanisms to control or stop image transfer should the image storage capacity be reached at either. The UCS may also have image result management capabilities, such as, for example, the ability for a user to add, update, delete, view and print processing result entries.
Different pieces of mail processing equipment at a single Plant UCS may send images to different RECs for resolution. In addition, any image or type of image may be sent to many REC sites. Further, images from many different mail processing locations may be sent to the same REC for processing.
Problems can arise when different quantities of images come from different plants. For example, a single REC might handle thousands of images from a New York City plant and only a few hundred from a plant in Reading, Pa. The smaller plant may end up waiting long periods of time for its images to be processed because the REC operators are overwhelmed with images from the larger plant. Other problems can arise when images represent different product types (e.g., letters or flats) because the mail processing machines handling the mailpieces, such as the Input Subsystems 506-522, may need very different response times from the REC operators. For example, some types of mail (e.g., flats, parcels) need to be resolved within 90 seconds (on-line processing) while others (e.g., letters, forms, international mail) can wait longer (off-line processing).
Thus, it is desirable to develop methods for controlling the processing of mailpiece images at Remote Encoding Centers (REC) and mail processing and distribution facilities. In particular, load balancing methods may utilize configuration data with REC, Mail Processing Equipment (MPE), and Time Value information for controlling the processing order of mailpiece images.
III. FIFO Load Balancing
One method of load balancing at a REC uses First In First Out (FIFO) processing. In one embodiment, FIFO processing utilizes data containing time values, or time characteristics, to control the order of mailpiece image processing at mail processing facilities and RECs. These time characteristics may include, for example, image capture times and image receipt times.
Load balancing based on FIFO Processing Management may utilize time characteristics such as time values entered into a table to determine the processing order of a particular mailpiece image. As mail is processed on First Mail Processing Equipment 606 at a plant UCS (Step 700), an Identification Tag (ID Tag) is applied to each mailpiece, an image of each mailpiece is captured, and header information along with the ID Tag is associated with the image. If the mailpiece address cannot be resolved by the MPE (Step 702), the MPE forwards the image to the plant UCS (Step 704). As the image enters the plant UCS, the plant UCS records the entry time and header information in a table for use with FIFO Processing Management in determining the order of image processing based on a First In First Out algorithm (Step 706).
The plant UCS sorts the images at the coding system according to time characteristics such as an image capture time or an image receipt time. Once the plant UCS determines the next image to be processed, the image is forwarded to a REC, such as REC UCS 604, for encoding (Step 708). Using First In First Out processing, this determination is based on the capture time of the image. Alternately, this determination may be based on the time of receipt of the image at the Plant UCS so that the first image received by the UCS is the first image sent to the REC for encoding. In this manner, the images are transmitted from the mail processing plant to a remote location. At the remote location, the images are processed at an encoding center, also referred to as REC UCS, in the sorted order to obtain mail processing data from the images. As the image enters the REC UCS, the entry time is recorded (Step 710). The entry time, as recorded in the REC UCS table, is used to determine the order in which the mailpiece image is presented to an encoding device, such as Universal Coding Desks 550, for processing (Step 712). At the encoding device, a REC operator views the mailpiece image and enters address data about the mailpiece (Step 714). The UCS REC provides mail processing data such as a POSTNET code using the data entered by the REC operator. In this manner, the images are processed at an encoding center at the remote location in the sorted order to obtain mail processing data from the images.
The results of the encoding processes are then forwarded back, or transmitted, from the encoding center to the plant UCS such as Plant UCS 602 (Step 716). The plant UCS receives the mail processing data (Step 718) and sends the data or makes it available to the MPE. The mail processing device then uses the mail processing data, such as the POSTNET code, to process, or sort, the mail. In one embodiment, the plant UCS keeps a count of images it sends to an encoding center and thus knows when it has received all the result data, or mail processing information, from each REC UCS. In this manner, the plant UCS can make the result data, or mail processing information, available to the mail processing equipment as soon as it receives the last image from the REC UCS.
Thus, a first image of a first delivery item to be processed at a first mail processing device, the image of letter A (LA) is captured, and a second image of a second delivery item to be processed at a second mail processing device (LB) is captured and sent to a coding system. In this manner, mailpieces processed by the First Mail Processing Equipment 606 and the Second Mail Processing Equipment 608 may be of different types (ex. letters and parcels), and First Mail Processing Equipment 606 and Second Mail Processing Equipment 608 may be different types of mail processing equipment.
The coding system, and specifically the Plant UCS 602, receives the images in image data 802, 804, and 806 from Mail Processing Equipment 606, 608, and 610. Plant UCS 602 may then accumulate the images in image data 802, 804, and 806 in combined images 810, which Plant UCS may place in a data table 812 based upon the order the images were received by the Plant UCS 602. For example, combined images 810, and data table 812, include the image of letter A (LA), then the image of parcel A (PA), then the image of parcel B (PB) because this is the order the Plant UCS 602 received these images. Plant UCS 602 may also store additional data along with the image, such as an ID Tag, the source of the image, the image product type, and the age of the image.
The Plant UCS 602 then determines the next image to be sent to the REC UCS 604 by sorting the images according to time characteristics of the images. The time characteristics may include the timestamp of the image or data table 812 so that the first image received by the UCS is the first image sent to the REC for encoding. One of skill in the art will note that the time characteristics could include the capture time of the image at the Mail Processing Equipment 606, 608, and 610, image receipt times at the Plant UCS 602, or both. Alternately, Plant UCS 602 could order at least a portion of or all of the images to be in Last In First Out (LIFO) order before sending the images to the REC UCS 604.
The Plant UCS then sends the images to the REC UCS 604 for encoding according to the sending order to obtain mail processing data. The images are received at the REC UCS 604, and the entry time, as recorded in the REC UCS table, is the time the REC UCS 604 receives an individual image such as image LA. The entry time is used to determine the order 814 in which the mailpiece image is presented to an encoding device, such as Universal Coding Desks 550, for processing. In addition, the REC UCS 604 may distribute the images to encoding devices and operators at the encoding center based on priority data.
The images are processed at the image encoding center to obtain mail processing data such as a POSTNET code. Specifically, at Universal Coding Desks 550, a REC operator views an image, such as image LA, and enters address data about letter A based on the image such as a partial address or a ZIP™ Code. After a REC operator inputs address data, the REC UCS 604 further processes the images by querying information databases using the address data to resolve the image. In this manner, the images are processed at the encoding center, or REC UCS 604, in the sorted order to obtain mail processing data from the images. Thus, a first image such as image LA is processed to obtain first mail or item processing data, and a second image such as image PA is processed to obtain second mail or item processing data. Resolving the image may involve providing a POSTNET code, providing a ZIP™ Code, or providing a delivery point code. REC UCS 604 may create result data 816. In one embodiment, the Universal Coding Desks 550 have different modes allowing REC Operators to enter different information. For example, the Universal Coding Desks 550 may allow REC Operators to enter only numeric information, address information, or name information, or some combination of this information. REC UCS 604 may receive images from up to 450 plant sites and may include up to 4500 Universal Coding Desks.
One having skill in the art will note that the UCS may use an authorized commercial names database as part of the processing used in determining the final resolution of an address. This database may be stored at a REC UCS, plant UCS or any other authorized location accessible via Wide Area Network.
In one embodiment, the UCS periodically notifies the REC UCS of the status of operation of each mail processing equipment. This may include, for example, the minimum depth of sort required, the mode of operation, and the machine number.
IV. Product Type Processing
One method of load balancing at a REC uses Product Type processing. Load Balancing Based on Product Type utilizes data including mail processing equipment (MPE) type, mail product type, and expected turnaround time for each product type at the plant to determine the order and priority of image processing. This data determines which MPE or mail product type can be sent to which REC and the expected turnaround time for each product type. The MPE type could indicate, for example, whether the mailpiece corresponding to an image is being processed on letter processing equipment or flats processing equipment. The mail product type may indicate the type of item that corresponds to the image, such as letter, flat, parcel, bar-coded, and form, etc. The expected turnaround time could represent the image processing time needed by a certain MPE, by a plant, or by a product type, and may begin when an image arrives at a REC and end when the result is received at the plant. Each plant UCS may maintain an individual plant turnaround table and may sent this to each of the RECs which processes images from that plant UCS. Each plant may alternately have multiple turnaround tables, such as one for each day of the week. In one embodiment, plant personnel manually configure these values, providing a great deal of flexibility and configurability in the system.
Images may then be sent, or transmitted, to a remote location and processed at an encoding center at the remote location, such as REC UCS 604, in timestamp order or according to the processing order (Step 1008). As the REC UCS receives images, another timestamp is applied and associated information is entered into REC tables (Step 1010). The REC UCS may use a Product Type Automatic Load Balancing (ALB) method to process the images, or to determine the processing order of each mailpiece image such as the first image and the second image (Step 1012). For example, the order for image processing may be based on a turnaround time value for a product type corresponding to the image. In one embodiment, images corresponding to parcels would be sent for processing first, followed by images corresponding to flats, followed by images corresponding to scanned forms, followed by images corresponding to letters.
After the processing order is determined, the images are presented to an encoding device, such as Universal Coding Desks 550, for encoding. At the encoding device, a REC operator views and enters address data from the mailpiece image (Step 1014). Thus, the first and second images are processed at an encoding center at the remote location in the sorted order, also referred to as the processing order and which may be FIFO order, to obtain mail processing data, also referred to as item processing data, from the images. Further, at least a portion of the images may be transmitted to a second remote location for processing the images at an encoding center at the second remote location. The results of the encoding processes are then transmitted from the encoding center to the coding system, and may be sent specifically to the originating plant UCS (Step 1016). When received at the plant UCS (Step 1018), the data may then be provided to a MPE or OSS. Specifically, the mail processing data may be sent to a first mail processing device and a second mail processing device, where a first mailpiece and a second mailpiece may then be processed using the mail processing data.
Load Balancing based on Product Type provides the capability to determine the destination REC based on source MPE or product type and the capability to configure and send images from a particular MPE or product type to one or many REC(s). Further, it provides the capability to configure an expected turnaround time for each MPE or product type and to integrate other load balancing methodologies such as FIFO Image Processing Management to determine the order of image processing.
In
The entry time, as recorded in the REC UCS table, is the time the REC UCS receives an individual image such as image LA. The entry time is used to determine the order 1106 in which the mailpiece image is presented to an encoding device, such as Universal Coding Desks 550, for processing. At Universal Coding Desks 550, a REC operator views an image, such as image LA, and enters address data about letter A based on the image, such as a partial address or ZIP™ Code. After a REC operator inputs address data, the REC UCS 604 further processes the images by querying information databases using the address data to resolve the image. Resolving the image may involve providing a POSTNET code, providing a ZIP™ Code, or providing a delivery point code. REC UCS 604 may create mail processing data, or result data, 1116. The results of the encoding processes, the result data 1116, may then be forwarded back to the originating plant UCS and ultimately to the proper mail processing equipment in a similar manner to that shown in
One having skill in the art will appreciate that the Plant UCS 602 could also use different data within data table 1102 to reorder the images. For example, Plant UCS 602 could use mail product type data to reorder the images, to thereby send all of the images of a particular type (letters, parcels, flats, forms) to be processed in a FIFO manner. For example, all flats may be processed before the letters are processed. Plant UCS 602 could also use expected turnaround time data to reorder the images to accommodate mail processing equipment having particular turnaround times. Alternately, Plant UCS 602 could use priority data to reorder the images.
V. Load Balancing
One method of load balancing at a REC uses an integrated load balancing management system.
In
In certain embodiments, static configuration data may be assigned to images and processing the images may include checking for this static configuration data. Static configuration data may include, for example, priority data, image source information, such as information regarding which MPE captured the image, or product type information. For example, images corresponding to parcels or to Priority Mail items may be marked for processing before any other types of images. If static configuration data is present (Step 1310), then images are distributed accordingly to a specific encoding device or devices. For example, if First REC UCS 1204 detects that an image includes static configuration data indicating that an image corresponds to a mailpiece that is Priority Mail, the First REC UCS 1204 may select a specific encoding device, also referred to as a first encoding device, such as Universal Coding Desk 1250, to receive the images having this static configuration data (Step 1312). In this manner, images are forwarded to the Universal Coding Desks based on priority. If static configuration data is not present, the REC UCS tables along with plant product type expected turnaround time tables and available encoding resource tables are used by the REC UCS to determine the processing order of a mailpiece image. The REC UCS utilizes dynamic data, such as the information in the tables, to determine the order in which the mailpiece images will be presented for encoding and which encoding device will encode the mailpiece images. For example, a table showing current available resources may show that every encoding station at one REC UCS, such as First REC UCS 1204, is busy, so images may be sent to a different REC UCS, such as Second REC UCS 1212, that has idle encoding stations.
After the processing order and encoding devices, or encoding resources, for the images are determined, the images are distributed accordingly to the encoding devices (Step 1314). REC operators view mailpiece images and enter address data about the mailpiece based on the image (Step 1316). The results of the encoding processes are then forwarded back to the originating plant UCS (Step 1318). After the data is received at the plant UCS (Step 1320), it is sent to an MPE (for example, when performing on-line processing) or made available to the MPE upon request.
Using integrated Load Balancing, encoding resources may be dynamically allocated at the REC UCS based on dynamic data including encoding resources, such as REC operator productivity data and available coding desks data, and configuration data, such as mail processing device data, and expected turnaround data for each MPE, product type, and plant. The dynamic data may be changed at the encoding center or at the plant UCS. For example, dynamic data may include a plant product type expected turnaround table that specifies how quickly mailpiece images should be processed for a certain mailpiece type based on the MPE handling that type of mailpiece. In another example, dynamic data includes uses encoding resource data such that, for example, an administrator at First REC UCS 1204 or First Plant UCS 1202 may change information stored in the dynamic data to redirect images to one REC if another REC is experiencing technical difficulties. Encoding resources may also be allocated based on the source of the image, e.g., images for a plant that is behind in its mail sorting runs may be processed after images for other plants. In yet another example, an individual REC operator with demonstrated high productivity may be given more images to encode, or may be given images of a particular product type if the operator demonstrates productivity on a particular product. In another embodiment, an administrator may assign plants to individual REC operators (Plant Mode), in which case load balancing may not be proportioned equally with respect to plant turnaround time.
In addition, processing may involve using product pools and a priority matrix. Specifically, REC operators may be pooled into product pools based on a predefined strategy. The REC operators may then be reallocated from one product pool to another product pool based upon a priority matrix, which clarifies which REC operators can be pulled from other product pools at what times. For example, the UCS 500 will look for REC operators working on the lowest priority products for reallocation. In one embodiment, an administrator at First REC UCS 1204 or First Plant UCS 1202 may write over this priority matrix to provide additional flexibility. Further, in one embodiment, the Universal Coding Desk may smoothly transition from one product pool to another product pool without drawing this to the REC operator's attention.
Second Plant UCS 1214 received an image of letter A (L2A), an image of letter B (L2B), and an image of letter C (L2C) from First Mail Processing Equipment 1216, an image of flat A (F2A), an image of flat B (F2B), and an image of flat C (F2C) from Second Mail Processing Equipment 1218, and an image of parcel A (P2A), an image of parcel B (P2B), and an image of parcel C (P2C) from Additional Mail Processing Equipment 1220. Second Plant UCS 1214 also records the time of receipt of the image, as well as the image header information.
First Plant UCS 1202 then uses configuration data 1404 to sort the images, or determine the order and priority of image processing. Configuration data 1404 might include data pertaining to, for example, the type of MPE that captured the image, the product data such as the type of mail, priority data, or an expected turnaround type for the type of MPE that captured the image or the product type. One having skill in the art will appreciate that configuration data could further include other types of data, such as an applicable day of the week, a REC assignment based on product type, a REC assignment based on MPE, expected turnaround time, percentage of resources at REC for each plant UCS, number of operators assigned, etc. First Plant UCS 1202 may also use the time of receipt of the image at the UCS REC and the time of capture of image at the MPE to order the images in a FIFO order.
As shown in
Similarly, Second Plant UCS 1214 uses configuration data 1406 to determine to which REC UCS it will send the images from each MPE. Second Plant UCS 1214 transmits images L2A, L2B, and L2C received from the First Mail Processing Equipment 1216 to the same REC, First UCS REC 1204. Second Plant UCS 1214 sends images F2A, F2B, and F2C received from the Second Mail Processing Equipment 1218 to the same REC, Second REC UCS 1212. Second Plant UCS 1214 sends images P2A, P2B, and P2C received from the Additional Mail Processing Equipment 1220 to the same REC, Additional REC UCS 1402. In this manner, a first image may be sent to and received at a first remote image encoding center, and a second image may be sent to and received at a second remote image encoding center.
When an image is received by the REC UCS, the entry time value and associated image information such as the ID Tag, source of an incoming image, image product type (e.g., letter, flat, PARS, Parcel, Form, etc.), and age of image is entered into REC UCS tables. The images are then load balanced at the First REC UCS 1204 using dynamic data.
One having skill in the art will appreciate that each Plant UCS could select the REC to send the images to based on additional static data, such as a time period. For example, First REC UCS 1204 could receive images only during a specific time period, could receive images of a certain type (such as letters, flats, parcels, etc.), or could receive images from selected plants, etc. One having skill in the art will also appreciate that each plant need not send its images to more than one REC, and that the encoding center need not be at a remote location.
In certain embodiments, static configuration data may be assigned to images. Static configuration data may include, for example, image source information, such as information regarding which MPE captured the image, or product type information. For example, images corresponding to parcels or to Priority Mail items may be marked for processing before any other types of images. If static configuration data is present, then images are distributed accordingly to a specific encoding device, or coding desk, for processing. An image encoding center determines if, for example, a first and second image has static configuration data. If a first image has static configuration data, the encoding center may select a first video display terminal for processing; if the first image does not have static configuration data, the encoding center may select a different video display terminal, such as a second video display terminal, for processing using dynamic data. For example, if First REC UCS 1204 detects that an image includes static configuration data indicating that an image corresponds to a mailpiece that is Priority Mail, the image may be directed to a specific encoding device such as Universal Coding Desk 1250. If Static configuration data is not present, the REC UCS uses dynamic data, including, for example, plant product type expected turnaround time tables and available encoding resource tables to determine the processing order of a mailpiece image. The REC UCS utilizes the dynamic data to determine the order in which the mailpiece images will be presented for encoding and which encoding device will encode the mailpiece images. For example, dynamic data may include current available resources, such that if every encoding device at one REC UCS, such as First REC UCS 1204, is busy, so images may be sent to a different REC UCS, such as Second REC UCS 1212, that has idle encoding devices. This dynamic transfer of images between RECs may be made while maintaining one plant's images in FIFO order.
At Universal Coding Desks 1506,1508, and 1510, REC operators view each image and enter address data. The Additional REC UCS 1402 further processes the images by querying information databases using the address data to resolve the image and therefore obtain mail processing data. The results of the encoding processes may then be forwarded back to the originating plant UCS and to the proper mail processing equipment in a similar manner to that shown in
Using integrated Load Balancing, encoding devices and resources may be dynamically allocated at the REC UCS based on the expected turnaround times for each MPE, product type, and plant. Therefore, an administrator at a REC UCS or plant UCS may change the dynamic data to manage the workload of the REC operators and the REC as a whole, and integrate and manage the workload of image processing for other products, such as form processing, images of foreign mail, electronic custom manifesting, etc. For example, dynamic data 1502 may include a product type expected turnaround table that may specify how quickly mailpiece images should be processed for a certain mailpiece type based on the MPE handling that type of mailpiece. In yet another example, an administrator at a REC or plant UCS such as First Plant UCS 1202 or Second Plant UCS 1214 may change information stored in the dynamic data to redirect images to Second REC UCS 1212 if First REC UCS 1204 is experiencing technical difficulties or is overloaded. Encoding resources may also be allocated based on the source of the image, e.g., images for a plant or a specific mail processing equipment that is behind in its mail sorting runs may be processed after images for other plants or mail processing equipment.
One having skill in the art will further note that the present invention may not only involve multiple mail processing plants, but that the REC UCS may handle different modes for each plant UCS or each product type. For example, a plant may have a wait mode, which requires the mailpiece images to first go to a reader pool prior to being sent to a REC, a no wait mode, which does not require prior reader pool processing, and an off mode, wherein a plant will not send any mailpieces to the reader pool. Alternately, images of one type of mail, such as letters, may be in no wait mode while images of another type of mail, such as parcels, are in wait mode.
One having skill in the art will also note that when images are sent to more than one REC, a first REC determines if a first image has static configuration data and selects a first video display terminal for processing the first image if static configuration data is present. If static configuration data is not present, the first REC uses first dynamic data comprising productivity data to select a second video display terminal for processing the first image. The first image is then processed to create first item processing data, and the first item processing data is sent to a coding system, and then sent to a first mail processing device, where a first delivery item is sorted using the first item processing data. A second REC may further check a second image for static configuration data, select a third video display terminal for processing an image if static configuration data is present, or use second dynamic data comprising productivity data to select a fourth video display terminal for processing the second image if static configuration is not present. The second image is then processed to create second item processing data, and the second item processing data is sent to a coding system, and then sent to a second mail processing device, where the second delivery item is sorted using the second item processing data.
Although the foregoing text describes systems and methods for processing mail, embodiments of the present invention may be applied to systems and methods for processing other delivery items as well. For example, using systems and methods consistent with the invention, forms may be sorted, processed, and delivered using one or more codes, such as bar codes, printed on the forms. One skilled in the art will recognize that other delivery items could also be processed and delivered using methods and systems consistent with the universal coding system disclosed herein.
Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.
This application claims the benefit of the filing date of U.S. Provisional Application No. 60/731,858, filed Nov. 1, 2005, titled “Method and System for Load Balancing Remote Image Processing in a Universal Coding System,” of Kuldip K. Goyal, David E. Williams, Brenda M. Weeks, Linda M. Malone, and Thomas Addams, incorporated in its entirety herein by reference. This application also claims the benefit of the filing date of U.S. Provisional Application No. 60/731,859, filed Nov. 1, 2005, titled “Method and System for Image Processing Based on Product Type in a Universal Coding System,” of Kuldip K. Goyal, incorporated in its entirety herein by reference. This application also claims the benefit of the filing date of U.S. Provisional Application No. 60/731,860, filed Nov. 1, 2005, titled “Method and System for FIFO Image Processing in a Universal Coding System,” of Kuldip K. Goyal, incorporated in its entirety herein by reference.
| Number | Date | Country | |
|---|---|---|---|
| 60731858 | Nov 2005 | US | |
| 60731859 | Nov 2005 | US | |
| 60731860 | Nov 2005 | US |
