This application claims priority to U.S. provisional patent application Ser. No. 61/061,987, filed Jun. 16, 2008, entitled “Cash Supply Chain Improvements,” hereby incorporated herein by reference as to its entirety.
The cash supply chain is manual, complex, has inherent risk issues, and is dispersed throughout a network of customers, armored carriers, the Fed (Federal Reserve), and/or a network of client facing devices including but not limited to automatic teller machines (ATMs), vaults, banking centers, safes, cash recyclers, and other cash handling devices. The costs of depositing, distributing, and managing cash across a major bank, as well as the amount of daily excess cash carried by such a bank, can be on the order of billions of dollars.
Today's client deposit process does not adequately allow clients to view the status of their deposit bag as it makes its way from the client's site where the deposit was prepared to the bank or bank's representative who will continue the processing of the deposit. Deposit bags are handled multiple times in the current process (and possibly by many different parties), which increases potential errors and complicates finding missing deposits or understanding where errors occurred and assigning fiduciary responsibility for those errors. Pertinent pieces of deposit data are typically manually entered and reentered into various systems throughout the end-to-end processing of the deposit. The collaboration and sharing of information across multiple organizations and with multiple vendors may make this process very complex and increases risk to the bank and bank clients.
In addition, because cash must be physically transferred along the cash supply chain, there is a risk that the cash may be stolen or otherwise inappropriately handled prior to arriving at its destination.
Aspects as described herein are directed to tracking monetary packages, which may contain monetary items such as foreign and domestic government-issued legal-tender paper currency, coins, checks, coupons, food stamps, credit cards, negotiable money orders, and/or other negotiable instruments as well as non-negotiable collateral information, throughout the cash supply chain. In carrying out daily financial transactions, it is typical for monetary packages to be physically transferred between various parties, such as but not limited to a bank client (or a client of another financial institution who is leveraging the services of the bank), a transporter (e.g., an armored carrier), a bank vault, and even various stations within a bank vault. This transfer amongst various parties is referred to as the cash supply chain. Because many types of cash are reusable/recyclable, the same physical cash is usually cycled through the cash supply chain multiple times.
For transport through the cash supply chain, a financial transaction such as a deposit including one or more monetary items is normally bundled or otherwise packaged together as a monetary package. Depending upon the location within the cash supply chain, the monetary package may maintain together a quantity of monetary items as a single entity by way of, e.g., a bag (in which the monetary items are placed within the bag, which may be sealed), by way of a cassette for holding the monetary items, and/or by way of one or more straps (which may also be within the bag).
While a number of techniques to automate transaction handling have been attempted, there remains a need to increase the efficiency and accuracy of the financial transaction process. Consequently, it is desirable to increase the speed and accuracy of the financial transactions and to reduce the labor required to perform the transactions. It is also desirable to make information relating to the financial transaction rapidly available to the client, third party vendors, and the bank, and to identify more quickly problematic locations in the financial transaction, identify potential theft, fraud or embezzlement, and identify industry trends. Information about a deposit or withdrawal, for instance, should be provided in an expeditious fashion as it is processed along a cash supply chain, where notification/reporting is customizable and automatic for enhancing the client's experience and for improving internal processes of a bank.
According to further aspects, monetary packages are tracked via a centralized tracking system that communicates with the various parties handling the monetary packages throughout the entire supply chain and/or when a carrier is set to arrive. Each time a monetary package changes status in the cash supply chain (e.g., transfers from one party to another or changes physical location), an involved party (e.g., the party receiving the monetary package and/or the party providing the monetary package) updates the centralized tracking system with the status. The centralized tracking system may be updated using a network of automated sensors that do not necessarily require the intervention of a party to create the update. These updates may be communicated to the centralized tracking system (system of record) in real time or near real time. Such a centralized tracking system may allow the bank or other service provider to offer a variety of services to the client.
For instance, centralized monetary package tracking may allow for more accurate reporting of monetary package status. And, by pre-scheduling (initiation) of deposits and change orders into the centralized tracking system, anomalies in the transport of a monetary package (e.g., a lost or delayed cash package) may be recognized much earlier, even prior to actual deposit or arrival of the package at the processing site.
Because monetary packages may now be traceable and accounted for at checkpoints while en route through the cash supply chain, it may further be desirable to add a tamper detection function to monetary packages that allows one to determine at any checkpoint whether the monetary package has been inappropriately tampered with.
Accordingly, still further aspects are directed to providing monetary packages with a tamper detection capability that can determine whether the monetary package may have been handled in such a way that its contents may have been modified. In particular, it may be detected whether the monetary package has been opened in an unauthorized manner, and information about such unauthorized opening may be stored as data in a memory attached to the monetary package. The next time that the monetary package is examined (e.g., scanned by a device capable of reading the stored data), the unauthorized opening may be determined and appropriate actions taken. In contrast, conventionally one will often not know whether the monetary package has been opened until it has reached its destination and the cash contents have been counted. Therefore, such a feature may allow the tampering to be detected much earlier in the cash supply chain and may also allow one to narrow down where in the cash supply chain the tampering occurred. In today's environment, one may never know if some of the notes are removed. A bank would typically take this as a loss or the client would take the difference as a loss.
These and other aspects of the disclosure will be apparent upon consideration of the following detailed description.
A more complete understanding of the present disclosure and the potential advantages of various aspects described herein may be acquired by referring to the following description in consideration of the accompanying drawings, in which like reference numbers indicate like features, and wherein:
Centralized tracking system 101 may include at least one computing device and at least one computer-readable medium that, together, are configured to receive monetary package status reports from parties such as parties 102-106, maintain data representing the monetary package status, and generate reports and alert messages from that monetary package status data. A “computing device” as referred to herein includes any electronic, electro-optical, and/or mechanical device, or system of physically separate such devices, that is able to process and manipulate information, such as in the form of data. Non-limiting examples of a computing device includes one or more personal computers (e.g., desktop or laptop), servers, personal digital assistants (PDAs), ultra mobile personal computers, smart phones, cellular telephones, pagers, and/or a system of these in any combination. In addition, a given computing device may be physically located completely in one location or may be distributed amongst a plurality of locations (i.e., may implement distributive computing). A computing device may even be a mobile device. Centralized tracking system 101 may further support co-operation with other non-bank tracking systems.
A computing device typically includes both hardware and software. The software may be stored on a computer-readable medium in the form of computer-readable instructions. A computing device may read those computer-readable instructions, and in response perform various steps as defined by those computer-readable instructions. Thus, any functions attributed to a computing device as described herein may be defined by such computer-readable instructions read and executed by that computing device, and/or by any hardware (e.g., a processor) from which the computing device is composed.
The term “computer-readable medium” as used herein includes not only a single medium or single type of medium, but also a combination of one or more media and/or types of media. Such a computer-readable medium may store computer-readable instructions (e.g., software) and/or computer-readable data (i.e., information that may or may not be executable).
Referring again to
Deposit location 103 is the location at which client 102 releases custody of the deposit (such as in the form of a monetary package). This custody may be released by, for instance, depositing the monetary into a cash handling device (e.g., a cash recycler, depository, exchange, dispensing machine, or ATM), or at a bank teller, or even at the client's own location where an armored carrier would pick up the deposit from the client. Pickup location 106 is the location at which client 102 receives custody of the monetary items(which may or may not be prepared by client 102 and which may be in the form of a monetary package), such as from an armored carrier, bank teller, or cash handling device.
Vault 105 is typically a secured location or device in a bank or customer's office where the deposit is processed. In the case of a vault in an armored carrier's or bank's facility, once the deposits are processed, currency or other monetary items are strapped for storage and distribution. A vault may not only process incoming monetary items but may also provide monetary items such as currency to clients. These requests for currency, commonly called “change orders,” are generally standing orders for specific amounts that are sent on a specific schedule, but can be on-demand or non-standing orders that are requested for a specific time. With some embodiments, currency may be verified by the one transporting the currency. This may be because the carrier is trusted and in an appropriate liability agreement with the bank, or the bank owns a carrier. In that case, some or all of the funds may be verified (or trusted due to the device the funds came from) and re-used in the cash supply chain without going to the vault. For example, the carrier may use a hand-held device to check the next location to visit or receive notices that a site needs cash. The carrier may use the verified cash to fulfill the order.
Armored carrier 104 (which may be referred to as a “vendor”) transports monetary packages between different stages along the cash supply chain typically in an armored vehicle. The physical transportation could be any type of transportation, however, including a courier or package delivery service with a secured package.
Parties 102-106 may communicate with centralized tracking system 101 over corresponding communications channels. Different types of communications channels may be supported. For example, centralized tracking system 101 may communicate with client 102 through a computer terminal (via the Internet) and/or a wireless telephone, with an armored carrier through a handheld scanner with a wireless communications interface, and with a bank employee through a work station (e.g., via an intranet). A communications channel may utilize different communications media, including a wired telephone channel, wireless telephone channel, and/or wide area channel (WAN).
As can be seen in
Tracking database 302 may be implemented as or otherwise include a computer-readable medium for storing data. This data may be organized, for instance, as a relational database that is responsive to queries such as structured query language (SQL) queries. Tracking database 302 may be distributed and may collaborate with internal and/or external sources to fulfill the completeness of the data utilized for notifications.
In this example, tracking controller 301 may be configured to add, edit, update, delete, and query data stored in tracking database 302. The data stored in tracking database 302 may include, for instance, data indicating the current status of each of a plurality of monetary packages. For example, the data may indicate that a given monetary package is with a particular armored carrier, and that it was transferred to the armored carrier at a certain time on a certain date. The status data may be associated with the unique identifier of the relevant monetary package.
Web server 303 may be configured to generate an Internet web page that is accessible by client 102 and/or other parties. The web page may be used to query tracking database 302 via tracking controller 301. For example, a party using the web page may be able to enter an identifier associated with a monetary package. In response, web server 303 may request tracking controller 301 to query tracking database 302 (or alternatively web server 303 may generate the query itself) for that identifier. The query response is forwarded by tracking controller 301 to web server 303, and displayed on the web page for review by the party. The query response may include, for instance, the status data associated with the identifier. Many other types of query transactions are possible. In addition, updates, deletions, and additions may be made to the data in tracking database 302 via the web page generated by web server 303. For example, a party may desire to update status information about a particular monetary package via the web site, or may desire to add a new monetary package with a new identifier not previously included in tracking database 302.
Tracking interface 304 may be used as an alternative interface into tracking controller 301 and tracking database 302, without the need for an Internet web page. For example, data and queries may be provided to tracking controller 301 via tracking interface 304 using a short messaging system (SMS) message or other type of messaging from a cellular telephone.
RFID tag 309 may be a passive RFID tag that does not contain its own power source. Rather, a passive RFID tag (e.g., its memory, controller, and transmitter) is powered by power inherent to a signal that is received from RFID scanner 306 or another signal source. Alternatively, RFID tag 309 may be an active RFID tag that contains its own power source.
The above discussion in connection with
It should be noted that the divisions between functional blocks in
Controller 401 is configured to control the operations of RFID tag 309, such as storage and retrieval of data in memory 403 and coordination of data received and/or transmitted via RF interface 404. Controller 401 may also receive and process signals from tamper sensor 402. Controller 401 may be, for instance, a processor such as a microprocessor, or another type of circuitry that is commonly used for RFID tag control.
Memory 403 may store any type of data desired, including the identifier discussed previously and data that depends upon signal generated by tamper sensor 402. Tamper sensor 402 may generate these signals based upon sensing an environmental characteristic, such as sensing whether monetary package 307 is in an opened or closed state. For example, tamper sensor 402 may generate a signal (digital data or an analog signal) responsive to monetary package 307 being in an open state, or tamper sensor 402 may generate the signal responsive to monetary package 307 being in a closed state. Alternatively, signal may be generated in both states, except that a value of the signal may depend upon the open/closed state of monetary package 307.
As an alternative to generating an actual signal, tamper sensor 402 may modulate a signal generated by RFID tag 309 (e.g., by controller 401). For example, as will be discussed in further detail, tamper sensor 402 may be considered an electrical load that changes resistance depending upon the open/closed stated of monetary package 307.
In operation, when controller 401 or memory 403 (depending upon whether the embodiment of
Also, after an open state has been detected and an indication thereof has been stored in memory 403, the indication may not be changed responsive to a subsequent closed state being detected. Thus, the stored indication may be an indication of whether an open state has ever occurred during a time period. However, because monetary package 307 may be legitimately in an open state before use (e.g., before filling monetary package 307 with cash and then closing monetary package 307 for transport along the cash supply chain), memory 403 may be configured to be resettable in response to an external input. The resetting of memory 403 may cause the indication of the open/closed state to be set to indicate that an open state has not yet occurred. The external input may be in the form of, for instance, an electrical signal being applied to a hard-wired input of RFID tag 309 and/or an appropriate command via an RF signal wirelessly received at RF interface 404. The input may further indicate a particular identifier to be stored in memory 403, if an identifier is not already assigned or if the identifier is desired to be changed. A security feature may also be used in that the reset function may not be performed unless the input contains a particular set of data such as a password.
In step 603, monetary package 307 is sent en route to another destination in the cash supply chain. In this example, it will be assumed that monetary package 307 is opened at some point along the cash supply chain. Thus, in step 604 this open state is detected by tamper sensor 402, and in step 605 RFID tag 309 stored the indication of the open state in memory 403.
In further embodiments, global positioning system (GPS) technology may be utilized to help detect tampering in real time or near real time. Responsive to tampering being detected, the monetary package may be configured to destroy the contents of the monetary package (e.g., by activating a dye pack) and/or sending an alert message (e.g., wirelessly via a transmitter that is part of the monetary package, such as RF interface 404) to an appropriate party to indicate that tampering has occurred. In addition, a decision may be made as to whether only one monetary package or multiple related monetary packages had been tampered with (based upon the alert messages sent by the monetary packages). If, for example, it is determined that greater than X number of monetary packages (where X is a whole number) were tampered with, the outcome may be different. For example, depending upon how many monetary packages are detected as being tamper with, it may be decided to provide an alert message, to release a dye pack, to turn on a video camera, and/or to lock down an area. These decisions may be made, for instance, by the bank in response to the alert messages sent by the monetary packages.
Returning to
In some embodiments, the open state indication and the identifier may be one and the same. For example, while in some embodiments the open state indication may be a separate bit, in other embodiment, the open state indication may be a bit within the identifier or may be embodied as some other modification to the value of the identifier. For instance, a first range of identifier values may indicate that monetary package 307 has not been opened, whereas a second range of identifier value may indicate that monetary package 307 has been opened. As an example of such a range-based embodiment, where the identifier is a string of bits, the most significant bit of the identifier may be used as the open state identifier. This may be useful where existing RFID scanners are used that are not able to receive data separate from a standard identifier. In such a case, the value of the identifier itself may be used to determine whether monetary package 307 has been opened.
Monetary package 307 may be considered in an “open” state depending upon the configuration of monetary package 307 and the configuration of tamper sensor 402. For example, referring to
Various examples of how tamper sensor 402 may be configured will now be described. Referring to
Contacts A-T, and the conductive lines connecting them, may be made of any conductive material such as metal or conductive ink, and may be applied to respective surfaces of bag 701 and/or embedded therein.
Another example of tamper sensor 402 is shown in
The various conductive lines may be coupled in series or in parallel relative to each other.
For instance, each conductive line 1101 may individually form an electrical loop having nodes coupled to RFID tag 309. Or, conductive lines 1101 may be coupled in series with each other and thus form a single long loop having nodes coupled to RFID tag 309. In a similar manner as discussed previously with regard to
Thus, a variety of illustrative embodiments of a monetary packages have been described that are capable of detecting tampering and of communicating such tampering to an entity separate from the monetary package. Although many of the examples have been directed to monetary packages in the form of bags, it should be understood that the various embodiments may also be applied to other types of monetary packages, such as a box as in the example of
Number | Name | Date | Kind |
---|---|---|---|
3618059 | Allen | Nov 1971 | A |
4352097 | Hamann | Sep 1982 | A |
5453601 | Rosen | Sep 1995 | A |
5689240 | Traxler | Nov 1997 | A |
5952920 | Braddick | Sep 1999 | A |
5953423 | Rosen | Sep 1999 | A |
5963131 | D'Angelo et al. | Oct 1999 | A |
6047807 | Molbak | Apr 2000 | A |
6122625 | Rosen | Sep 2000 | A |
6483433 | Moskowitz et al. | Nov 2002 | B2 |
6633881 | Drobish et al. | Oct 2003 | B2 |
6736314 | Cooper et al. | May 2004 | B2 |
6788203 | Roxbury et al. | Sep 2004 | B1 |
6845905 | Blad et al. | Jan 2005 | B2 |
7042360 | Light et al. | May 2006 | B2 |
7212992 | Kanevsky et al. | May 2007 | B1 |
7348886 | Himberger et al. | Mar 2008 | B2 |
7375638 | Light et al. | May 2008 | B2 |
7474217 | Himberger et al. | Jan 2009 | B2 |
7659816 | Wandel | Feb 2010 | B2 |
7714708 | Brackmann et al. | May 2010 | B2 |
7719423 | Himberger et al. | May 2010 | B2 |
7748610 | Bell et al. | Jul 2010 | B2 |
20010054643 | Siemens | Dec 2001 | A1 |
20020194122 | Knox et al. | Dec 2002 | A1 |
20030011466 | Samuel et al. | Jan 2003 | A1 |
20030050891 | Cohen | Mar 2003 | A1 |
20030061153 | Birdsong et al. | Mar 2003 | A1 |
20030122671 | Jeserpsen | Jul 2003 | A1 |
20030208431 | Raynes et al. | Nov 2003 | A1 |
20030234719 | Denison et al. | Dec 2003 | A1 |
20040056767 | Porter | Mar 2004 | A1 |
20040083149 | Jones | Apr 2004 | A1 |
20040100379 | Boman et al. | May 2004 | A1 |
20050091129 | Tien | Apr 2005 | A1 |
20050108164 | Solafia, III et al. | May 2005 | A1 |
20050183928 | Jones et al. | Aug 2005 | A1 |
20050273347 | Dudley et al. | Dec 2005 | A1 |
20060282277 | Ng | Dec 2006 | A1 |
20070005452 | Klingenberg et al. | Jan 2007 | A1 |
20070008118 | Kassiedass | Jan 2007 | A1 |
20070012602 | Baldassari et al. | Jan 2007 | A1 |
20070034693 | Jouvin et al. | Feb 2007 | A1 |
20070063016 | Myatt et al. | Mar 2007 | A1 |
20070226142 | Hanna et al. | Sep 2007 | A1 |
20070282724 | Barnes et al. | Dec 2007 | A1 |
20080005019 | Hansen | Jan 2008 | A1 |
20080103959 | Carroll et al. | May 2008 | A1 |
20080149706 | Brown et al. | Jun 2008 | A1 |
20080199155 | Hagens et al. | Aug 2008 | A1 |
20080223930 | Rolland et al. | Sep 2008 | A1 |
20080262949 | Bond et al. | Oct 2008 | A1 |
20080265019 | Artino et al. | Oct 2008 | A1 |
20080303903 | Bentley et al. | Dec 2008 | A1 |
20090006249 | Morgan et al. | Jan 2009 | A1 |
20090006250 | Bixler et al. | Jan 2009 | A1 |
20090032580 | Blachowicz et al. | Feb 2009 | A1 |
20090051566 | Olsen et al. | Feb 2009 | A1 |
20090051769 | Kuo et al. | Feb 2009 | A1 |
20090164364 | Galit et al. | Jun 2009 | A1 |
20090187482 | Blount et al. | Jul 2009 | A1 |
Number | Date | Country |
---|---|---|
4019265 | Nov 1991 | DE |
4429815 | Feb 1996 | DE |
19512045 | Oct 1996 | DE |
19846452 | Dec 1999 | DE |
20013021 | Nov 2000 | DE |
102004039365 | Feb 2006 | DE |
102005047711 | Apr 2007 | DE |
1477949 | Nov 2004 | EP |
9933040 | Jul 1999 | WO |
03034359 | Apr 2003 | WO |
2005041385 | May 2005 | WO |
2005106722 | Nov 2005 | WO |
Number | Date | Country | |
---|---|---|---|
20090309722 A1 | Dec 2009 | US |
Number | Date | Country | |
---|---|---|---|
61061987 | Jun 2008 | US |