The cash supply chain is manual, complex, has inherent risk issues, and is dispersed throughout a network of self-service cash handling devices such as automatic teller machines (ATMs), as well as cash vaults and banking centers. 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 substantial.
Today's client deposit process does not adequately allow clients and internal cash supply chain processing units to view the status of client deposits as the deposits move from deposit site through asset verification and credit. 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 front-end systems throughout the end-to-end process. 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, self-service cash handling devices have improved the clearing speed of checks, enabled cost reductions and delighted customers with deposit photo receipts and immediate funds available for check and cash deposits. However, servicing and processing of self-service cash handling device deposits is an extremely manual process, is labor intensive and time consuming, and provides multiple opportunities for errors that directly impact bank customers and banking center associates. Currently, self-service cash handling device technology and operations do not have electronic tracking and monitoring of cash and check bags from self-service cash handling device deposit pull servicing through asset verification and check storage. Handling of contents from cash and check bags involve manual chain of custody, cash verification and reconciliation processing. Valuable pieces of information are re-keyed into general ledger, cash vault asset management tracking and image check filing and retrieval systems. Data that is relied upon is in paper receipt format, hand written on bags or is non-existent for cash verification and reconciliation.
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 cash 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 cash, 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 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 monetary package) may be recognized much earlier, even prior to actual deposit credit or arrival of the package at the processing site.
Still further aspects are directed to an electronic process to capture, track and monitor unique identifying information regarding check and bags deposited with a self-service monetary item handling device throughout processing, verification, reconciliation, storage and retrieval of bag contents. Self-service monetary item handling devices equipped with radio-frequency identification (RFID) or other remote identification technology may enable the electronic transfer of key data elements to general ledger and asset tracking processing systems. The term “self-service monetary item handling device” as used herein is intended to broadly refer to any self-service devices as found in the financial services and banking industries that can handle monetary items, including but not limited to automated teller machines (ATMs) such as deposit image enabled ATMs, full function envelope ATMs, and cash dispense ATMs; cash recyclers; deposit kiosks; night drops such as receipted night drops; and lock boxes.
By introducing RFID technology into the self-service monetary item handling device process, new tracking and monitoring capabilities may be provided, potentially allowing the bank to view the status of a deposit bag as “In Transit,” “Received,” and/or other status designations as the deposit moves through the deposit verification process. The bank may have tools to control access to the deposit, find and retrieve paper checks, and pull deposits with reduced manual labor. RFID may reduce or even eliminate the need to rely on paper receipts, reports, or manifests by capturing deposit data at the time of the initial touch point and using that captured data to populate all downstream front-end systems.
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 cash into a self-service monetary item handling device, 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 recycler.
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.
The above discussion in connection with
Controller 401 may be or include, for example, a processor such as a microprocessor, or other circuitry, and/or may be embodied as a computing device. Controller 401 may control and/or coordinate the operations of self-service monetary item handling device 400.
Storage 405 may be embodied as any type of computer-readable medium, such as memory, tape drives, and/or hard drives, and may store data and software (computer-executable instructions) for use by controller 401 and/or by any other functional unit of self-service monetary item handling device 400. Any functions attributed to self-service monetary item handling device 400 and/or controller 401 as described herein may be defined by such computer-readable instructions read and executed by controller 401, and/or by any other hardware from which self-service monetary item handling device 400 is composed.
Network interface 409 may be used to communicate uni-directionally or bi-directionally with an external entity. Such communication may be via a direct line, such as a telephone connection, and/or via a network such as the Internet. The external entity may include, for instance, the bank, such as centralized tracking system 101. Thus, any data communicated between self-service monetary item handling device 400 and centralized tracking system 101 as described herein may be performed via network interface 409.
Deposit input 402 may be or include a slot for receiving deposits from self-service monetary item handling device customers. Deposit input 402 may further include a motor system designed to pull paper deposits into self-service monetary item handling device 400. The deposits entering deposit input 402 may pass through a deposit reader 408, which may include an optical imager (e.g., a camera or scanner) and/or a magnetic reader, for scanning/reading the deposits. Deposit reader 408 may recognize the deposits (e.g., what types of bills are being deposited) using known techniques, and may store data about the deposits (including optical images) into storage 405.
Once the deposits have been received and read by deposit reader 408, the deposits may be placed in deposit holding area 407. Deposit holding area 407 may include one or more deposit bins, such as one for paper currency and another for checks.
Printer 406 and display 403 may be used for providing information to the user of self-service monetary item handling device 400, in a conventional manner.
RFID device 404 may include an RFID tag and/or an RFID scanner for reading other RFID tags located within (e.g., for reading RFID tags on the deposit bags in deposit holding area 407) and/or external to self-service monetary item handling device 400 (e.g., for reading RFID badges of armored carriers or other authorized persons servicing self-service monetary item handling device 400).
These transactions may operate as in the following examples. In one example, armored carrier 104 may approach self-service monetary item handling device 400 to begin the servicing process. As armored carrier 104 walks up to self-service monetary item handling device 400, RFID device 404 may capture the data on armored carrier's 104 RF-enabled ID badge 601, which stores an identifier uniquely identifying armored carrier 104. RFID device 404 may read this identifier from badge 601 and associate that identifier with the unique identifier of self-service monetary item handling device 400 (as may be stored in RFID device 404 and/or storage 405), the current date, the current time, an identifier that uniquely identifies self-service monetary item handling device 400 from other self-service monetary item handling devices, and/or the location of self-service monetary item handling device 400, self-service monetary item handling device 400 may also authenticate the servicer such as by comparing the received identifier of badge 601 with a pre-stored set of authorized identifiers (e.g., in storage 405) to determine whether badge 601 identifies armored carrier 104 as being an authorized servicer of self-service monetary item handling device 400. Authentication may also require user input, such as by requiring a pass code entered via keyboard 410. If authenticated, then armored carrier 104 may be allowed to fully access the servicing menu of self-service monetary item handling device 400, and select the deposit pull function from the menu (e.g., using keyboard 410 and/or display 403).
In response to the selection, self-service monetary item handling device 400 may automatically push, via network interface 409, the relevant deposit data collected using RFID device 404 to downstream processes at the bank, such as RFID tag identifiers on the deposit bags in deposit holding area 407 as well as their contents, and the other information collected and associated with the identifier of badge 601. The downstream processes may include, e.g., centralized tracking system 101. All this may occur in response to a simple selection of a function on the servicing menu. Then armored carrier 104 may begin the deposit pull.
Information about the contents of the deposit bags may have been already determined as each deposit is made. This information may be obtained, for instance, using deposit reader 408, which may optically or otherwise read the currency bills, checks, and any other deposits being inserted into deposit input 402. In addition, where deposits already include their own RFID tags, RFID device 404 may read the identifiers from those RFID tags and record the fact that deposits with those particular identifiers have been placed into self-service monetary item handling device 400. All information obtained about the deposits may be stored in storage 405 until it is ready to be output via display 403, via printer 406, via RFID device 404, and/or via network interface 409.
As another example, self-service monetary item handling device 400 may be embodied as a banking center serviced self-service monetary item handling device, i.e., located within a banking center. In this case, a banking center associate (e.g., a banking teller) may approach self-service monetary item handling device 400 to begin the servicing process. Instead of RFID device 404 being located inside self-service monetary item handling device 400 and reading the deposits, an RFID hand held scanner such as RFID scanner 306 may be used by the banking center associate (or armored carrier or other servicer) to read the RFID identifiers from the deposits in deposit holding area 407, and/or the RFID identifier of self-service monetary item handling device 400. Additionally or alternatively, any of the information in the previous example that was transmitted via network interface 409 directly or indirectly to centralized tracking system 101 may instead be transmitted via RFID device 404 to RFID scanner 306. RFID scanner 306 may, in turn immediately or on a deferred basis transfer this information directly or indirectly to centralized tracking system 101 via communications system 305 and tracking interface 304 and/or web server 304. Thus, RFID scanner 306 may be used not only for the previously-described purposes in connection with
As an alternative to using RFID scanner 306, the banking center associate may walk up to self-service monetary item handling device 400, scan his/her RFID-enabled badge, and scan cash replenishment straps, check bags, and monetary items and deposit pull receipts. The resulting scanned identifiers and the data associated with those identifiers may be instantly transmitted to centralized tracking system 101, which may associate the received identifiers and data regarding the banking center associate, self-service monetary item handling device 400 unique identifier, the date, the time, the location, and self-service monetary item handling device cash replenishment and deposit pull contents.
Thus, systems, methods, and software for at least partially automating self-service monetary item handling device servicing has been described. Many variations on the described examples are possible. For example, although RFID has been discussed as a means for communication between two entities, other types of wireless or non-wireless communications are possible, such as BLUETOOTH, infra-red transmissions, or optical bar code reading.
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.
Number | Name | Date | Kind |
---|---|---|---|
3618059 | Allen | Nov 1971 | A |
4352097 | Hamann | Sep 1982 | A |
4443692 | Nishimura | Apr 1984 | A |
5453601 | Rosen | Sep 1995 | A |
5689240 | Traxler | Nov 1997 | A |
5748908 | Yu | May 1998 | A |
5936220 | Hoshino et al. | Aug 1999 | A |
5952639 | Ohki et al. | Sep 1999 | A |
5952920 | Braddick | Sep 1999 | A |
5953423 | Rosen | Sep 1999 | A |
5963131 | D'Angelo et al. | Oct 1999 | A |
6028517 | Sansone et al. | Feb 2000 | A |
6047807 | Molbak | Apr 2000 | A |
6055438 | Winner, Jr. | Apr 2000 | A |
6122625 | Rosen | Sep 2000 | A |
6167378 | Webber, Jr. | Dec 2000 | A |
6255947 | Osawa et al. | Jul 2001 | B1 |
6260024 | Shkedy | Jul 2001 | B1 |
6483433 | Moskowitz et al. | Nov 2002 | B2 |
6487542 | Ebata et al. | Nov 2002 | B2 |
6491216 | May | Dec 2002 | B1 |
6498603 | Wallace | Dec 2002 | B1 |
6526273 | Link et al. | Feb 2003 | B1 |
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 |
7004385 | Douglass | Feb 2006 | B1 |
7015814 | Ireland et al. | Mar 2006 | B2 |
7042360 | Light et al. | May 2006 | B2 |
7076458 | Lawlor et al. | Jul 2006 | B2 |
7143933 | Uematsu et al. | Dec 2006 | B2 |
7149336 | Jones et al. | Dec 2006 | B2 |
7201313 | Ramachandran | Apr 2007 | B1 |
7212992 | Kanevsky et al. | May 2007 | B1 |
7216800 | Ramachandran | May 2007 | B1 |
7243080 | Bhadra | Jul 2007 | B2 |
7248160 | Mangan et al. | Jul 2007 | B2 |
7284692 | Douglass | Oct 2007 | B1 |
7348886 | Himberger et al. | Mar 2008 | B2 |
7350230 | Forrest | Mar 2008 | B2 |
7375638 | Light et al. | May 2008 | B2 |
7461780 | Potts et al. | Dec 2008 | B2 |
7474217 | Himberger et al. | Jan 2009 | B2 |
7537153 | Hurwitz et al. | May 2009 | B2 |
7577612 | Waller et al. | Aug 2009 | B2 |
7623033 | Ainsworth et al. | Nov 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 |
7778456 | Jones et al. | Aug 2010 | B2 |
7883005 | Artino et al. | Feb 2011 | B2 |
7908188 | Flynn et al. | Mar 2011 | B2 |
7965184 | Nichols et al. | Jun 2011 | B1 |
7975911 | Artino et al. | Jul 2011 | B2 |
8078534 | Nichols et al. | Dec 2011 | B1 |
8164451 | Nichols et al. | Apr 2012 | B2 |
20010051922 | Waller et al. | Dec 2001 | A1 |
20010054643 | Siemens | Dec 2001 | A1 |
20020052193 | Chetty | May 2002 | A1 |
20020052794 | Bhadra | May 2002 | A1 |
20020091937 | Ortiz | Jul 2002 | A1 |
20020095588 | Shigematsu et al. | Jul 2002 | A1 |
20020111916 | Coronna et al. | Aug 2002 | A1 |
20020138424 | Coyle | Sep 2002 | A1 |
20020194122 | Knox et al. | Dec 2002 | A1 |
20020195309 | Pope | Dec 2002 | A1 |
20030011466 | Samuel et al. | Jan 2003 | A1 |
20030050891 | Cohen | Mar 2003 | A1 |
20030061153 | Birdsong et al. | Mar 2003 | A1 |
20030083936 | Mueller et al. | May 2003 | A1 |
20030122671 | Jespersen | Jul 2003 | A1 |
20030163710 | Ortiz et al. | Aug 2003 | A1 |
20030177102 | Robinson | Sep 2003 | A1 |
20030208431 | Raynes et al. | Nov 2003 | A1 |
20030213843 | Jackson | Nov 2003 | A1 |
20030234719 | Denison et al. | Dec 2003 | A1 |
20040016796 | Hanna et al. | Jan 2004 | A1 |
20040056767 | Porter | Mar 2004 | A1 |
20040083149 | Jones | Apr 2004 | A1 |
20040100379 | Boman et al. | May 2004 | A1 |
20040111346 | Macbeath et al. | Jun 2004 | A1 |
20040124966 | Forrest | Jul 2004 | A1 |
20040201454 | Waterhouse et al. | Oct 2004 | A1 |
20050027594 | Yasnovsky et al. | Feb 2005 | A1 |
20050077347 | Uematsu et al. | Apr 2005 | A1 |
20050091129 | Tien | Apr 2005 | A1 |
20050108164 | Solafia, III et al. | May 2005 | A1 |
20050183928 | Jones et al. | Aug 2005 | A1 |
20050258234 | Silverbrook et al. | Nov 2005 | A1 |
20050273347 | Dudley et al. | Dec 2005 | A1 |
20060131395 | Potts et al. | Jun 2006 | A1 |
20060247973 | Mueller et al. | Nov 2006 | A1 |
20060271441 | Mueller et al. | Nov 2006 | A1 |
20060282277 | Ng | Dec 2006 | A1 |
20060288233 | Kozlay | 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 |
20070174156 | Emde et al. | Jul 2007 | A1 |
20070198341 | Park | Aug 2007 | A1 |
20070226142 | Hanna et al. | Sep 2007 | A1 |
20070282724 | Barnes et al. | Dec 2007 | A1 |
20080005019 | Hansen | Jan 2008 | A1 |
20080005578 | Shafir | Jan 2008 | A1 |
20080103959 | Carroll et al. | May 2008 | A1 |
20080120237 | Lin | May 2008 | A1 |
20080126515 | Chambers et al. | May 2008 | A1 |
20080149706 | Brown et al. | Jun 2008 | A1 |
20080155269 | Yoshikawa | Jun 2008 | A1 |
20080199155 | Hagens et al. | Aug 2008 | A1 |
20080223930 | Rolland et al. | Sep 2008 | A1 |
20080249934 | Purchase et al. | Oct 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 |
20090065573 | Potts et al. | Mar 2009 | A1 |
20090107800 | Nishida et al. | Apr 2009 | A1 |
20090114716 | Ramachandran | May 2009 | A1 |
20090164364 | Galit et al. | Jun 2009 | A1 |
20090187482 | Blount et al. | Jul 2009 | A1 |
20090216662 | Crist et al. | Aug 2009 | A1 |
20100052844 | Wesby | Mar 2010 | A1 |
20100076853 | Schwarz | Mar 2010 | A1 |
20100274723 | Joao | Oct 2010 | A1 |
20110089230 | Artino et al. | Apr 2011 | A1 |
20110089231 | Artino et al. | Apr 2011 | 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 |
2304953 | Mar 1997 | GB |
9933040 | Jul 1999 | WO |
03034359 | Apr 2003 | WO |
2005041385 | May 2005 | WO |
2005106722 | Nov 2005 | WO |
Entry |
---|
Final Office in U.S. Appl. No. 12/263,041 dated Jan. 26, 2011. |
Final Office in U.S. Appl. No. 12/262,448 dated Feb. 1, 2011. |
Non-final Office in U.S. Appl. No. 12/262,522 dated Feb. 3, 2011. |
Final Office in U.S. Appl. No. 12/262,432 dated Dec. 7, 2010. |
Powerpoint Presentation, DTS Product Overview, IFS, Apr. 2006, 17 pages. |
Durbin, “Ford's F-150 goes high-tech”, retrieved from <http://www.wheels.ca/article/173134>, Feb. 6, 2008, 4 pages. |
Monthly Minutes from Banking Technology Operations Standing Committee (BTO), dated Mar. 20, 2007, 2 pages. |
Hem, “Adaptation/Loomis cashes in on technology/The armored car company defies obsolescence despite a declining use of coins and bills”, Houston Chronicle, retrieved from <http://www.chron.com/CDA/archives/archive.mpl?id=2008—4523451>, Mar. 1, 2008, 2 pages. |
Powerpoint Presentation, Guck, “PakTrak”, Cash Shipment Package Tracking Concept Overview, Draft-Version 1.0, Mar. 14, 2008, 17 pages. |
Powerpoint Presentation, RFID in Banking, May 21, 2008, 12 pages. |
Monthly Minutes for RFIS SIG dated Mar. 19, 2008, 2 pages. |
Office Action from related U.S. Appl. No. 12/262,534 dated Jun. 24, 2010. |
Office Action from related U.S. Appl. No. 12/263,041 dated Mar. 12, 2010. |
Office Action from related U.S. Appl. No. 12/262,908 dated Mar. 8, 2010. |
Final Office Action for U.S. Appl. No. 12/262,908 dated Aug. 18, 2010. |
Non-Final Office Action for U.S. Appl. No. 12/262,432 dated Aug. 18, 2010. |
Non-Final Office Action for U.S. Appl. No. 12/263,041 dated Sep. 2, 2010. |
European Search Report in EP09007879 dated Oct. 1, 2009. |
European Search Report in EP09007878 dated Oct. 1, 2009. |
International Search Report and Written Opinion for PCT/US2009/047452, mailed Aug. 25, 2009. |
Non-Final Office Action for U.S. Appl. No. 12/262,448 dated Sep. 15, 2010. |
Non-Final Office Action for U.S. Appl. No. 12/262,526 dated Sep. 16, 2010. |
Non-Final Office Action for U.S. Appl. No. 12/262,472, dated Oct. 18, 2010. |
Non-Final Office Action for U.S. Appl. No. 12/262,534, dated Oct. 14, 2010. |
Non-Final Office Action in U.S. Appl. No. 12/262,523 dated Nov. 9, 2010. |
Final Office Action in U.S. Appl. No. 12/262,526 dated Nov. 23, 2010. |
Non-Final Office Action in U.S. Appl. No. 12/262,928 dated Nov. 10, 2010. |
Non-Final Office Action in U.S. Appl. No. 12/263,115 dated Nov. 16, 2010. |
Non-Final Office Action in U.S. Appl. No. 12/262,532 dated Nov. 26, 2010. |
Notice of Allowance in U.S. Appl. No. 12/262,502 dated Oct. 19, 2010. |
PR Newswire: “Airborne Express Announces New Pricing”: New York, Jan. 29, 2001. |
Anonymous; “Parcel Pickup now a click away at Canada Post”; Canada Newswire, Aug. 31, 2011. |
Oracle Database SQL Reference, 10g Release 1 (10.1), Part No. B10759-01, Dec. 2003. |
Number | Date | Country | |
---|---|---|---|
20090309694 A1 | Dec 2009 | US |
Number | Date | Country | |
---|---|---|---|
61061987 | Jun 2008 | US |