Patent Application
20060133277
Financial institutions have established various processes and associations related to the exchange of documents evidencing monetary transactions. Such documents have generally been encoded with magnetic ink so that information from the documents can be read by machine. Such documents have thus become known as magnetic ink character recognition (MICR) documents. Item processing and sorting systems have also been developed in which a check or similar MICR document has its image captured and stored electronically.
In a typical item processing environment, based on the read of the MICR data, items are sorted into pockets as “on-us” items or “transit” items. An on-us item is an item that is drawn on the financial institution doing the processing. On-us items will typically be forwarded to other locations within the financial institutions own franchise. Transit items are checks drawn on other financial institutions, and are pocketed for delivery to those institutions. Images are also stored and indexed for retrieval. Historically, these images have been used mainly for archival purposes; however, the image is gradually replacing the physical item for more and more purposes. For example, customers can retrieve images of their checks on-line as opposed to obtaining a copy of the actual paper item. Legislation has also been promulgated in some jurisdictions that will allow banks to reconcile accounts using electronic images instead of paper items. Thus, correct indexing and identification of images relative to corresponding MICR data can be very important.
In a modern, computerized item sorting facility, an item processing computer system controls the operation of a sorter or sorters, and the storage of data and images. Images are stored in a check image archive. Each image is indexed according to an image key which typically includes the date, sorter information, and an item sequence number (ISN). In a typical system the ISN is restricted to a specific number of digits or places. Thus, when the number of checks to be processed on a sorter in one day (also called a “cycle”) includes more than the number that can be counted with that number of digits, the ISN will begin to repeat, resulting in duplicate keys, mismatched images and other errors which disrupt the sorting operation.
Embodiments of the present invention provide for overrun prevention and management in an item processing system. In example embodiments, a buffer size is determined, wherein the buffer size is indicative of how close a current item sequence number (ISN) is permitted to be to an overrun value. The buffer size can be set by user input, either in real-time, or in advance. In the latter case the buffer size would be stored and read by the system software in order to calculate an ISN buffer value. A fixed buffer size may also be built into the system. When the current ISN reaches the ISN buffer value, new entries (stacks or batches) of documents will be prevented or at least restricted from being processed. It should be noted that in a typical system, a new cycle or day's entries of documents does not necessarily start with an ISN of zero, but may start with the ISN value corresponding to the end of the last cycle. Thus, a rollover of the ISN can be permitted, but not an overrun, wherein an ISN occurs that was previously used in the same cycle. Since other portions of the image key change with each new cycle, item sequence numbers from the last cycle can be re-used.
In some embodiments, a “force mode” is provided in which a sorter can be made to start a new entry even if the ISN buffer value has been exceeded during a cycle. In such an embodiment, the system can be set up so that the force mode is not available when the ISN is within a certain range of the overrun value. In such an embodiment, a hard stop value for the ISN is calculated based on the known overrun value and this desired “hard stop” range. The hard stop range can be stored in the system and/or entered by a user in a similar manner to that of the buffer size. In some embodiments, status indications and/or hard stop warnings can be provide to users via an attached user interface or terminal.
In at least some embodiments, internal calculations of buffer values, hard stop values, and status information are facilitated by the use of a modified ISN. Since the ISN is a portion of an image key that is defined and recognized by banks according to agreed standards, it typically cannot be changed. However, a modified ISN can be created and used internally by an item processing system in order to facilitate calculations. In example embodiments, the modified ISN includes the standard ISN and an ISN modifier. The ISN modifier provides an indication of how the ISN is positioned in relation to its rollover value, and can be used for calculations. The ISN modifier is maintained internally to the system in a fashion similar to that of the buffer size, hard stop range, and other numerical data needed for operation. In a practical system, this data can be maintained in a computer readable memory system in an ISN control file (ICF) and/or an ISN memory area (IMA). A MICR subsystem within the item processing system can house some or all of the computer program code instructions necessary to carry out embodiments of the invention using this data. Such computer program code instructions can be stored and transported as part of a computer program product. In such an embodiment, the memory system, MICR subsystem, user terminals, and other computing resources can provide the means for carrying out the processes of the invention.
The present invention will now be described in terms of specific, example embodiments. It is to be understood that the invention is not limited to the example embodiments disclosed. It should also be understood that not every feature of the methods and systems described is necessary to implement the invention as claimed in any particular one of the appended claims. Various elements and features of various embodiments are described to fully enable the invention. In addition, throughout this disclosure, where a process or method is shown or described, the steps of the method may be performed in any order or simultaneously, unless it is clear from the context that one step depends on another being performed first. Also, time lags between steps can vary. With respect of flow charts, block diagrams and flow diagrams, not every possible signal flow, data path, or process block is shown. Rather, for clarity, only those important to the inventive concepts being discussed relative to the drawing may be illustrated, although others may be discussed in this description.
The meaning of certain terms as used generally in the context of this disclosure should be understood as follows. Terms such as “document,” “item” or “check” and the like are meant to refer to any document which tends to be handled and sorted in large volumes based on MICR information printed thereon. In the typical context, such documents are checks which order a bank to pay a certain sum to the order of another individual or entity. However, other documents evidencing financial transactions relating to banking, and for that matter, other kinds of documents, can be processed according to the invention. Even in the typical banking context for example, deposit slips are sometimes MICR encoded, and could be read, sorted, and imaged in a fashion similar to checks. Thus, a system which processes such documents can be referred to as an item processing system, a check processing system, or a document processing system.
The term “bank” and any similar terms are used herein in their broadest sense. Financial institutions that process transactions and documents of the types discussed can include stock brokerages, credit unions, and other types of institutions which are not strictly banks in the historical sense. The use of terms such as bank, “institution” or “franchise” herein is meant to encompass all such possibilities.
Much of the terminology herein refers to the processing of information about MICR encoded documents. This information can be stored in a data processing system, in computer memory and media for retrieval and manipulation. There are many ways to design a system to accommodate the storage of this information, as well as the storage of electronic images of documents such as checks. In example embodiments, this terminology refers to information stored in what is commonly known as a “check image management system” (CIMS) and within a “check processing control system” (CPCS). Such systems are well known within the banking industry by those who work in the financial data processing fields. Such data processing systems have historically been produced by the International Business Machines (IBM) Corporation. CPCS is still produced by IBM, while CIMS is today produced and marketed by Carreker Corporation of Dallas, Tex., U.S.A. Through the use of such systems, check images and index information referring to the check images, which typically includes the MICR data, can be stored according to any of various industry standard formats, such as the “common import format file” (CIFF). Such systems have been used for many years by many banks to archive check images. Images and index information in such a system can be stored in the same file or separated. In some environments, the index information is separated and stored in an electronic cash letter (ECL) for communicating between financial institutions for the purpose of settlement. Index information can also be stored with electronic images in an “image cash letter” (ICL) to provide for the truncation of the paper documents. Again, these systems and techniques are well known by those of ordinary skill in the financial information technology arts.
It should be assumed for example purposes that a CPCS system like that typically supplied by the International Business Machines Corporation is being used to implement the embodiments described herein. With such a system, a user can add software to the standard CPCS software through the use of user exit programs. A “user exit” within the software causes the standard CPCS software to trigger custom software installed by the user of the check processing system. This arrangement is well-known to those in the industry who use CPCS software. The logic described herein that implements item sequence number (ISN) management can be, in example embodiments, implemented in CPCS user exit programs.
Embodiments of the invention will now be described as follows. An overview of a process and system of embodiments of the invention will be described with reference to
By way of further introduction, a standard CPCS system, when processing documents which are imaged, assigns a check image management system (CIMS) key to each item. This CIMS key, also referred to as simply an “image key” or a “key” includes a processing cycle number, a processing cycle date and an item sequence number (ISN). Processing cycles and entries have already been discussed. For example purposes, the ISN discussed herein includes a 6-digit rolling number that can be at any value when the processing cycle begins. If more than one million items are captured on a single sorter machine, the ISN will overrun the starting number, as previously discussed. It should be noted that the ISN of an image key actually can include an item type, sorter number, and region number as well as the six digit rolling number. In some circles, all of these items together are referred to as the ISN. For purposes of this disclosure, however, the concern is with the trailing, rolling, six digits, which can be treated as the “ISN” herein for discussion and illustrative purposes unless otherwise noted. Thus, the ISN as used herein, is relevant primarily on a sorter by sorter basis, since the CIMS key also includes a sorter number. It should be noted that the invention would be relevant no matter how many rolling digits are used in the ISN, any time the number of items to be processed on a sorter exceeds the number that can be accounted for by the ISN's available digits. At least some CPCS systems today allow for 8 rolling digits in the ISN.
Turning to
The buffer size referred to above specifies a buffer representing the number of ISN's before the overrun value where entries will begin to be restricted from initial processing. For example, if the system can be set up so that beginning new entries is restricted when the ISN is within 100,000 of its overrun value, than the buffer size is 100,000. A buffer size of 100,000 is used as an example herein. However, note that a system can be set up so that entries can continue to run but not be started if it is known that all entries are smaller in size than this number. The HS range is similar, except that it specifies, in example embodiments, how many sequence numbers before the overrun value that entries will be completely blocked from either starting or running. For purposes of the examples presented herein, an HS range of 10,000 is used and all processing ceases at a hard stop. In example embodiments, the buffer value or simply the “buffer” for brevity is a calculated ISN which matches the current ISN when the number of items is within the buffer size of the overrun value. The HS value, or for brevity simply the “HS” is similar.
The ISN in the above calculations as viewed externally is simply the standard ISN. However, for the internal calculations, a modified item sequence number (ISN) can be used. The modified ISN is the current standard ISN adjusted internally for overrun calculation purposes. In example embodiments it consists of the ISN and an ISN modifier. In example embodiments, the ISN modifier is a value based flag to track the forward progress of an ISN in a specific cycle for a specific sorter. It provides context of where the ISN has been in relation to passing one million. It can be used to increase the current ISN internally by 1,000,000 during calculations for a 6-digit ISN, by 10,000,000 for a 7-digit ISN, by 100,000,000 for an 8-digit ISN, etc. In the example embodiments, the numerical values discussed above, as well as additional information needed for embodiments of the invention, can be semi-permanently stored in an ISN control file on a media as appropriate and loaded into an ISN memory area for use when sorting is actually taking place.
Returning to
During operation, in this example embodiment, a modified ISN greater than or equal to the HS value as shown at block 117 will stop the sorter. Also, during operation, a modified ISN greater than or equal to the buffer value as shown at element 118 will trigger sub-process or element 120 which can issue a warning message at block 122 if the modified ISN is close to the HS value. The ISN and the modified ISN are continuously adjusted as needed during sorting at element 124. A status information display can also continuously updated in this example as shown at element 126. Note that the numerical tests specified above are expressed as “greater than or equal to” tests. The system can also be set up to use “greater than” tests and the latter is considered herein to encompass both possibilities.
In the example of
It cannot be overemphasized that the system of
Some embodiments of the invention can be implemented through extensive use of computer program products, or computer program instructions to carry out methods according to the invention. These instructions in combination with a computing platform processor and other devices form the means to carry out embodiments of the invention. These computer program instructions may be part of a computer program or multiple programs which are supplied as a computer program product. Such a computer program product may take the form of a computer readable media that allows computer program instructions to be loaded into computing platforms. In the example operating environment of
In addition to being supplied in the form of a machine readable medium or media, computer program instructions which implement the invention can also be supplied over a network. In this case the medium is a stream of information being retrieved when the computer program product is downloaded. Computer programs which implement embodiments of the invention can reside on any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with any computing platform or instruction execution system, apparatus, or device. The medium may be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system or device. For example, the computing platform, storage mediums, connectivity, and sorting machine, can all be combined into one large device and the computer program instructions could be stored within an optical, magnetic, or electronic module type storage devices.
Much of the remainder of this detailed description will illustrate details of how to implement an embodiment of the invention using CPCS user exit programming. Again, it cannot be overemphasized that this material is presented as an example only in order to fully enable the invention. Software and systems can be architected in numerous ways in order to create an embodiment of the invention that is within the spirit and scope of the appended claims.
In example embodiments of the sequence number management system, startup user exit programming allocates memory for the system information and establishes addressability to the memory area so other programs running in the CPCS address space can find the information. The programming then verifies that no changes have occurred in relation to the sorters defined to the CPCS. If changes were made, the ISN control file is recreated to include accurate sorter information. The ISN memory area is then populated and if necessary, the ISN control file is built or rebuilt. The ISN memory area is populated using data from the ISN control file, and other standard CPCS data, such as the data in the image sequence file and CPCS MICR control blocks.
In example embodiments, the following data maintained in the ISN control file:
One of the following for each cycle (cycles 0 through F):
In example embodiments, the following data maintained in the ISN memory area:
In example embodiments, a sorter operator typically enters or verifies information at a user screen on an attached terminal. This information includes sorter information, the type of documents to be processed, etc. The system read routine performs start of entry validation based on the ISN the sorter plans to use to begin the entry. If an ISN overrun condition is near, the read routine will prevent the sorter operator from starting the new entry unless force mode has been engaged and the HS value has not been surpassed. The read routine also manages ISN tracking for the sorter when a new entry begins.
Since the current entry may be the first entry of a new cycle, element 306 performs a check for a new processing cycle on this sorter. If the date of the cycle has changed, then a flag will be set to indicate a possible new cycle. Note that a cycle could be initiated with tracer tickets, documents that are not real documents but rather items to be read by the sorter to enter data in the system. A new cycle cannot be confirmed at this point because real items must be processed through the sorter. If this entry does not represent a possible new cycle, element 307 determines the current modified ISN (the current ISN with the ISN modifier applied in the millions position). Element 308 checks the force mode status. If the sorter is in force mode, an entry will be allowed to start if the modified current ISN is beyond the buffer value ISN. In these example embodiments, force mode will not allow the entry to start if the modified current ISN is greater than the hard stop value ISN. If force mode is enabled, processing proceeds to element 309 to determine if the modified current ISN is greater than the hard stop ISN. Note that if the date of the cycle had changed at element 306, a first cycle entry flag would have been set at element 310.
If the sorter is not in force mode for logic 300, the modified current ISN is reviewed to see if it is less than the buffer value at block 311. Note that if the system is in “restart” (being re-initialized after any kind of suspension of processing during an entry, including, but not limited to a planned suspension, a crash or a power failure) at block 313, the hard stop is disabled at element 314 and the entry begin process stops at block 315 when HS processing is disabled. If the system is not in restart at block 313, then the entry will be prevented starting at element 316. Otherwise, HS processing will be disabled for the restart and allow the entry to continue.
The ISN modifier validity check referred to at element 304 of
(1)ISN rolled past one million outside of modified ISN visibility;
(2)ISN rolled past one million outside of MICR (or possibly CPCS) with a CPCS “bounce,” that is, the ISN memory area does not reflect the previous entry;
(3)ISN ran over one million in a null entry during tracer processing, where the modified ISN incremented the ISN Modifier, but now the entry is starting at an ISN less than one million, so that the ISN modifier must be reset to prevent a double increment;
(4)CPCS has gone down in the middle of an entry and the restart fails, so that the CPCS image sequence file reflects the ISN prior to the entry involved (to be resolved with image system initialization procedures.
The final condition listed above reflects the fact that if the recovery is done outside of the restart mechanism, it will be outside the visibility of the modified ISN system. If a rollover occurs that either increments the ISN past or decrements the ISN past the rollover value, the ISN modifier will not be correct if the modifier is not adjusted for these events.
Logic for the modifier validity check referred to above can be implemented as follows. If this entry is a new entry and no other conditions have been detected, a “rollover during this entry” flag is reset. If a restart is in process the flag is not reset. To implement the above tests, the system determines if a “rollover during this entry” flag is on. If so, the current sorter ISN is stored as the current ISN. The last known ISN is retrieved from the ISN memory area and stored as the previous ISN. In example embodiments, a determination is made as to whether previous ISN is less than 300. If so, a determination is made as to whether the current ISN is greater than 999,000. If so, the ISN modifier is decremented if it is greater than 0 for all cycles of this sorter. The “rollover during this entry” flag is cleared and written to the ISN control file. A “rollover flag changed” indicator is set and the current MICR ISN is set up for the rest of the begin processing.
If the previous ISN was not less than 300 or the current ISN was not greater than 999,000, then a determination is made as to whether the current entry is a restart entry. If the entry is not in restart, a check is made for an ISN modifier equal to one. If the modifier is one, a determination is made as to whether the current ISN is greater than 900,000. If so, a determination is made to determine if the current ISN is greater than or equal to the cycle starting ISN. If the current ISN is greater than or equal to the starting ISN, a process to decrement the ISN modifier commences. Otherwise, another determination is made as to whether the entry is in restart. If not, the “rollover during this entry” flag is cleared and written to the ISN control file. A “rollover flag changed” indicator is set. If it was previously determined that the rollover flag was off, the current sorter ISN is obtained and set as the current ISN.
If the current ISN is less than 5000, the last known ISN from the ISN memory area is saved as the previous ISN. If the previous ISN is greater than 995,000, the system will increment all of the ISN modifiers that are less than nine. The system sets the “rollover during this entry” flag and saves the data to the ISN control file. A “rollover Flag changed” indicator is also set. If it is found that the current ISN was not less than 5000, it is again verified that the entry is not in restart. If the current ISN is less than 5000, a determination is made as to whether the cycle starting ISN is greater than the current ISN plus 5000. If so, the current cycle's ISN modifier for this sorter is set equal to zero, and the ISN modifier is incremented, the appropriate flags are set, and the data is saved to the ISN control file as previously described.
If the system is at an enhanced prime entry break, a check is made for modified ISN tracking at element 406. In element 407, a determination is made to see if processing of real items has begun. If so, element 408 performs a modified version of the begin logic for the new entry. Otherwise, processing continues to element 409, where the first entry of a new cycle is verified. If the entry is the first of a new cycle, element 410 verifies that a real item has been processed through the sorter as part of this entry. If one has, the new cycle information is set up in the ISN memory area and in the ISN control file, as shown at element 411, and discussed in further detail below with respect to
The modified version of the begin logic performed pursuant to element 408 of
Referring again to
Element 601 determines if the entry is in a restart status. If the entry is not in restart, element 602 determines if this entry has rolled over the one million ISN value before. If not, element 603 determines if the current ISN being processed is equal to 0. Element 604 determines if the previous ISN is greater than 999,600 and element 605 determines if the current ISN is less than 300. If the ISN is 0, element 606 will set the “rollover during this entry” flag, and element 607 will increment all ISN modifiers that are less than 9 and write the data to the ISN control file. If element 603 determined that the current ISN is not 0, and the previous ISN is greater than 999,600, element 605 will determine if the current ISN is less than 300. If the current ISN is less than 300, then elements 606 and 607 will set the rollover flag and increment the modifier. If element 602 determined that this entry has previously encountered an ISN rollover, element 608 will determine if the current ISN is greater than 5000. If the current ISN is greater than 5000, element 609 will determine if a real item was processed during this entry. Processing a real item is the point of no return that makes this entry permanent from a CPCS perspective. If so, element 610 will clear the “rollover during this entry” flag, effectively making the rollover permanent for this sorter. Logic process 600 exits at block 611.
During operation, ISN memory area 727 exists as part of system 702. Otherwise, data that needs to be preserved is kept in ISN control file 728. The CPCS application, 702, in this embodiment also includes ISN inquiry task 730 to query the status of other elements in response to user input, a file maintaining a history of ISN's used, 732, and a terminal, 734, for a check operations supervisor. Supervisor terminal 734 is used to monitor all sorters and all aspects of the system; hence its interface is integral to the CPCS application. A CPCS MICR terminal, 738, is provided as a separate entity. Terminal 738 connects to the MICR subsystem. Check reader/sorter 742 also connects to the MICR subsystem. An operator enters setup data and receives status and warning messages via terminal 738.
As previously suggested, the user terminals shown in
Note that in this example, the current ISN for all cycles is “0560712956.” The last six digits of this number represent the rolling “ISN” that has been discussed throughout this disclosure. As previously discussed, the complete ISN is of the format “ssrtnnnnnn” where ss is the sorter number, r is the region code, t is the item type, and nnnnnn is the rolling number that is referred to as the “ISN” for purposes of this disclosure. In the example of
Specific embodiments of an invention are described herein. One or ordinary skill in the financial data processing arts will quickly recognize that the invention can take many forms. For example, a sorting system can easily be designed which departs from the standard IBM CPCS system in many ways, but still maintains the use of industry standard image keys, with six, or more rolling digits where an overrun needs to be accounted for. An embodiment of the invention could still find use in such a system, but may not be implemented by user exit programming. Additionally, user screens and displays, nature and form of status information and warning messages, and the organization of software and hardware elements can have infinite variations. In fact, many embodiments and implementations are possible. The following claims are in no way intended to limit the scope of the invention to specific, example embodiments described herein.
