Patent Application
20090248470
The invention disclosed herein relates generally to mail processing systems, and more particularly to networked mail processing systems that can be utilized to measure the performance of a carrier network.
Numerous postal systems have been developed around the world for the delivery of mail pieces, e.g., letters, flats, packages, and the like. Most postal systems provide guidelines with respect to a time-for-delivery, i.e., the time elapsed between depositing a mail piece with the postal system for delivery and actual delivery of the mail piece to its destination (sometimes also referred to as transit time). For example, the time-for-delivery may be specified as 2-3 days for a specified class of service. This delivery time, however, depends significantly on the origin and destination of the mail piece. It can be easily understood that a mail piece being sent across the country will take more time to be delivered than a mail piece being sent across the same state. In situations where a mailer needs a mail piece to be delivered within a specific time frame, it is difficult, based solely on the estimates provided from the postal system, for a mailer to determine the least expensive class of service that can be used for the mail piece while still meeting the delivery time goal.
It would be desirable, therefore, to be able to determine a time-for-delivery for a mail piece based on the origin and destination of the mail piece.
The present invention alleviates the problems associated with the prior art and provides a system and method for determining time-for-delivery for a mail piece based on the origin location and destination location of the mail piece.
In accordance with the present invention, a mail processing system is utilized by recipients of mail pieces to scan each incoming mail piece. For those incoming mail pieces that are provided with indicators that provide the origin location of the mail piece as well as the date the mail piece was sent, the mail processing system obtains this information from each mail piece. Using the information obtained from the received mail pieces, along with the date of receipt of each of the mail pieces, the mail processing system establishes a record of the time-for-delivery between the origin location for each mail piece and the known location of the mail processing system. The mail processing system periodically sends the records to a data center. The data center aggregates the records from a plurality of different mail processing systems to establish a database that includes an actual value of time-for-delivery based on specific origin and destination locations. Mailers can then query the database maintained at the data center to obtain information concerning actual time-for-delivery statistics based on the specific origin and destination of a mail piece.
Therefore, it should now be apparent that the invention substantially achieves all the above aspects and advantages. Additional aspects and advantages of the invention will be set forth in the description that follows, and in part will be obvious from the description, or may be learned by practice of the invention. Moreover, the aspects and advantages of the invention may be realized and obtained by means of the instrumentalities and combinations particularly pointed out in the appended claims.
The accompanying drawings illustrate presently preferred embodiments of the invention, and together with the general description given above and the detailed description given below, serve to explain the principles of the invention. As shown throughout the drawings, like reference numerals designate like or corresponding parts.
In describing the present invention, reference is made to the drawings, wherein there is seen in
Each of the mailers 12-18 is adapted to communicate with a data center 20. Such communications can be done utilizing any type of communication network 28, such as, for example, the Internet, a telephone network, or the like. Data center 20 preferably includes a control unit 22 and one or more databases 24, as will be described below. Control unit 22 can be, for example, a processing unit or the like that is adapted to control operation of the data center 20. Data center 20 includes a network interface 26 that provides the necessary communication hardware/software required for the data center 20 to communicate via the network 28 with the mail processing systems 30 operated by mailers 12-18.
When processing outgoing mail pieces, the CPU 32 communicates with a postage metering device 42 that is utilized to generate indicia to evidence payment of postage for mail pieces and provide accounting data for communication to the data center 20 via network interface 44. Postage metering device 42 is preferably a secure coprocessor that performs cryptographic operations and keeps track of funds by maintaining a descending register which stores an amount of funds available for use and an ascending register which stores a total amount of funds dispensed over the life of the metering device 42. Funds may be added to the descending register by any conventional means. A printer 38 is used to print information on the mail pieces, such as, for example, indicia generated by the postage metering device 42, address information (either or both of the sender and recipient), ad slogans, and the like. Printer 38 may be, for example, an ink jet printer or other conventional type of printing device. The MPS 30 is adapted to process incoming mail pieces by having a scanning or reading device 40 to scan information printed on the mail pieces that are received by the mailer. A network interface 44 provides the necessary communication hardware/software required for the MPS 30 to communicate via the network 28 with data center 20. A real-time clock 48 provides the current date/time to the CPU 32. MPS 30 also preferably includes a memory or database 46 that is utilized to store information extracted from scanning the received mail pieces and the current date/time as described below.
Removing those mail pieces that do not include an indication of induction date and origin location before feeding into the MPS 30 would require additional sorting on the part of the operator of the MPS 30, and therefore may not be as desirable. Preferably, all of the received mail pieces would be fed into the MPS 30, and after a mail piece is scanned in step 100, then in step 102 it is determined, using for example, one or more processing routines performed by the CPU 32, if the information on the mail piece includes an indication of induction date and origin location. This can be performed, for example, by determining if there is a two-dimensional barcode, as required by the Indicium Specification, provided on the mail piece, or if the mail piece is provided with a stamp that has been canceled. Optical character recognition processing could also be utilized to determine if an induction date is provided on the mail piece in a known format for date representation. If an indication of the induction date and origin location is not provided on a mail piece, then in step 104 no further processing is performed on the mail piece with respect to the present invention, as it typically would not contain suitable information to be of use.
If in step 102 it is determined that a mail piece contains an indication of the date of induction and origin location, then in step 106 the indication information that is provided on the mail piece is obtained. In the case of an IBI indicia, the information is preferably obtained from the two-dimensional barcode, but can also be obtained from the human-readable portion as well. For an IBI, the origin location is deemed to be, for example, the licensing zip code, i.e., the zip code in which the mail processing system that generated the IBI for the mail piece is registered (and typically the origin location where the mail piece was inducted into the carrier network) and the induction date is deemed to be, for example, the date that the IBI was generated (which is included in the IBI). For a cancellation mark, the origin location is deemed to be, for example, the location of the postal facility where the mail piece was inducted (as provided in the cancellation mark) and the induction date is deemed to be, for example, the date of the cancellation mark. Typically, the origin location can be expressed as a postal zip code, but can also be expressed as a geographic location or area as well. Optionally, in step 106 other information that may be provided on the mail piece could also be obtained, such as, for example, class or type of mail, postage amount, etc. for use as described below.
In step 108, the time-for-delivery is determined for the mail piece based on the difference between the induction date obtained from the mail piece and the current date as indicated by the real-time clock 48. Optionally, the determination of the time-for-delivery can take into account weekends, holidays, or other days typically designated as non-business days, such that the time-for-delivery is based only on regular business days, e.g., Monday thru Friday. Thus, for example, if a mail piece is mailed on a Friday and received on a Monday, the time-for-delivery would not include the intervening weekend days (Saturday and Sunday) and would instead be calculated as one day. In some situations, it is possible that more than one mail piece will be received from the same origin location. In most instances, the determined time-for-delivery would be the same, but in the event that differences exist the differences can be reconciled by the CPU 32 taking, for example, an average of the time-for-delivery for each of the mail pieces received from the same origin location. In this manner, there is only a single time-for-delivery value associated with each origin location.
In step 110, CPU 32 will store the obtained and calculated data, or portions thereof, in the database 46. One such way to store this information is to populate the fields in a table maintained in the database 46, including the origin location (e.g., based on the licensing zip code obtained from the IBI), the destination location (known from the location where the mail piece was received and the MPS 30 that is processing the mail piece) and the calculated time-of-delivery. An example of a portion of such a table is provided below as Table 1, which illustrates an example of some mail pieces received on Feb. 27, 2008.
It should be understood, of course, that the table above is exemplary only, and not all of the information need be included, e.g., date mailed or date received. Additionally, if other information was obtained from mail pieces, this other information could also be included if desired, such as, for example, the class of service, type of mail (letter, flat, parcel), postage amount, etc. The location entries in Table 1 are based on zip codes, but other location identifiers could also be provided, e.g., town or city names, other types of postal codes, etc. The entries in Table 1 are also based on the CPU 32 taking into account designated non-business days in the determination of the time-for-delivery. Thus, for the mail piece arriving from California (Origin Zip Code 90012), although the elapsed time from date mailed to date received is seven days, the actual time-for-delivery is only four business days.
In step 112, the MPS 30 sends the data, or portions thereof, to the data center 20 via the network 28. The uploading of the data can occur on a regular basis, e.g., daily, or periodically, e.g., weekly, bi-weekly, monthly, etc. Preferably, the data is uploaded daily to provide real-time data for use by the data center 20. If the data is stored in a table as described above, the table could be uploaded to the data center 20. Optionally, the data being sent from the MPS 30 to the datacenter 20 could be cryptographically protected for privacy or data integrity/authentication purposes, such as, for example, by encryption or use of a digital signature.
In step 136, the time-for-delivery data that has been received from the mail processing systems, and, if applicable, determined by the control unit 22, is stored in the database 24 of the data center 20. Such data could be stored in the form of a look-up table that identifies an origin location, a destination location and the time-for-delivery based on the data received from all of the mail processing systems that are part of the system 10. Optionally, other information obtained from mail pieces could also be included to provide additional data, e.g., class off service, type of mail, etc. In the event that data already exists in the look-up table for a specified origin location to destination location, preferably the time-for-delivery currently in the look-up table would be replaced by the time-for-delivery from the most current data received by the data center 20. In this manner, the time-for-delivery values maintained in the database 24 will be the most up-to-date and accurate. As new data is obtained by the data center 20, additional rows can be added to the look-up table to include the new entries (origin location and/or destination location). Alternatively, information can be aggregated either using an average over a period of time, a sliding window, removal of outliers, or any other suitable method. Over time the number of entries in the table will increase, based on the participation of large numbers of mail processing systems, such that the look-up table can contain the time-for-delivery values for a very large number of origin-to-destination locations. It should be noted that the time-for delivery maintained by the data center 20 will be a very good approximation of actual delivery time, i.e., into the hands of a human recipient, as opposed to delivery times provided by more traditional tracking systems that measure time elapsed between mail items being at two different locations in the postal delivery network.
With the data stored in the database 24, the data center 20 can provide mailers with actual time-for-delivery values.
If in step 152 it is determined that payment is not required, or if in step 156 it is determined that payment is received, then in step 160 the control unit 22 will search the database 24 for data that corresponds to the origin/destination specified in the request. In step 162 the control unit 22 will determine if data that corresponds to the origin/destination specified in the request has been found in the database 24, and if so, then in step 164 the data center 20 will provide the time-for-delivery for the origin/destination that is stored in the database 24. If in step 162 it is determined that there is no data in the database 24 that corresponds to the origin/destination pair specified in the request, then in step 166 the control unit 22 can perform a search of the database 24 for the origin and/or destination that is closest to the origin/destination in the request. For example, there may be data from the actual origin specified in the request, but only to a destination that is near to the actual destination specified in the request. Similarly, there may be data for an origin that is near the actual origin specified in the request to the actual destination specified in the request. Depending upon the proximity of the origin/destination to the origin/destination specified in the request, the time-for-delivery data may still be accurate enough for use. The proximity may take into account the actual postal network as two geographically close locations may be served by postal units with considerably different performance. In step 168, the data center will provide the time-for-delivery for the closest origin/destination stored in the database 24 to the origin/destination included in the request. Preferably, this will also include the specific origin and destination locations, thereby indicating that the time-for-delivery is not actual data for the origin/destination specified in the request. As an alternative to steps 166 and 168, if a corresponding entry for the origin/destination does not exist in the database 24, an error message could be returned, and any payments, if made, can be refunded to the requesting party. Thus, a mailer is able to obtain actual time-for-delivery values based on a specific origin location and destination location for a mail piece.
Thus, according to the present invention, a data center aggregates time-for-delivery values from a plurality of different mail processing systems to establish a database that includes an actual value of time-for-delivery based on specific origin and destination locations. Mailers can then query the database maintained at the data center to obtain information concerning actual time-for-delivery statistics based on the specific origin and destination of a mail piece.
While preferred embodiments of the invention have been described and illustrated above, it should be understood that they are exemplary of the invention and are not to be considered as limiting. Additions, deletions, substitutions, and other modifications can be made without departing from the spirit or scope of the present invention. Accordingly, the invention is not to be considered as limited by the foregoing description but is only limited by the scope of the appended claims.
