WO2003102845A2 - System and method for supply chain event management - Google Patents

System and method for supply chain event management Download PDF

Info

Publication number
WO2003102845A2
WO2003102845A2 PCT/US2003/016967 US0316967W WO03102845A2 WO 2003102845 A2 WO2003102845 A2 WO 2003102845A2 US 0316967 W US0316967 W US 0316967W WO 03102845 A2 WO03102845 A2 WO 03102845A2
Authority
WO
WIPO (PCT)
Prior art keywords
event
item
inventory
identifier
tag
Prior art date
Application number
PCT/US2003/016967
Other languages
French (fr)
Other versions
WO2003102845A3 (en
Inventor
Hartmut K. Vogler
Richard J. Swan
Tao Lin
Ye Chen
James Vrieling
Scott R. Beckett
Wouter Van Der Veen
Original Assignee
Sap Aktiengesellschaft
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US10/159,598 external-priority patent/US6681990B2/en
Application filed by Sap Aktiengesellschaft filed Critical Sap Aktiengesellschaft
Priority to EP03756267A priority Critical patent/EP1532560A2/en
Priority to AU2003243340A priority patent/AU2003243340A1/en
Priority to JP2004509857A priority patent/JP4776921B2/en
Publication of WO2003102845A2 publication Critical patent/WO2003102845A2/en
Publication of WO2003102845A3 publication Critical patent/WO2003102845A3/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/08Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/08Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
    • G06Q10/087Inventory or stock management, e.g. order filling, procurement or balancing against orders
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/20Point-of-sale [POS] network systems
    • G06Q20/203Inventory monitoring
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07CTIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C9/00Individual registration on entry or exit
    • G07C9/20Individual registration on entry or exit involving the use of a pass
    • G07C9/28Individual registration on entry or exit involving the use of a pass the pass enabling tracking or indicating presence

Definitions

  • This invention relates to communication in a distributed item tracking system.
  • This invention can serve as an underlying communication infrastructure for a number of higher-level applications including supply chain management (SCM) software.
  • SCM supply chain management
  • SCM software such as the SCM solutions provided by SAP AG of Walldorf, Germany, enable a user to manage materials, information, and finances as they move in a process from a supplier to a manufacturer to a wholesaler to a retailer.
  • the SCM software generally implements algorithms for determining the best means to fill an order and also includes databases for tracking the physical status of the goods, the management of materials, and financial information.
  • Inventory management is a component of most SCM systems. Inventory management enables suppliers to keep track of how much inventory they have and how much inventory they have distributed to particular retailers. Periodically, the retailer reports to the supplier the current inventory level of the store. Based on the report, the supplier determines whether the store inventory needs to be replenished.
  • suppliers and retailers develop a planning schedule of how often the retailers will report to the supplier. For example, every Thursday, the retailer reports the current inventory level of the store and replenishment planning occurs. On Friday, any new inventory arrives at the store in time for the weekend shoppers.
  • the invention features methods and apparatus, including computer program products, for communicating item disposition information in a distributed system.
  • the system includes a monitoring system, one or more subscribers, including a system that tracks tagged items, and one or more event routers.
  • the monitoring system is operable to detect one or more of the tagged items, generate an event, the event including a tag identifier, a reader identifier, and a timestamp, and publish the event to one or more of the event routers.
  • the system for tracking tagged items is operable to subscribe to receive from one or more of the event routers events relating to one or more of the tagged items, and upon receiving events, use the received events to update disposition information for one or more of the tagged items.
  • Each event router is operable to maintain a list of subscribers, receive events from the monitoring system, and send events to the subscribers.
  • a monitoring system monitors the state of tagged items located within an inventory and sends an event to an event router when an item is added to or removed from the inventory.
  • the event router receives the event from the monitoring system and sends the event to one or more item tracking systems.
  • the item tracking systems receive the event and update stored information about the item to reflect the event.
  • a monitoring system monitors the state of tagged items located within an inventory and sends an event to an event router when an item is added to or removed from the inventory.
  • An event router receives the event from the monitoring system and sends the event to a second computer program.
  • the second computer program receives the event and determines whether to send an alert to a first computer program.
  • the first computer program determines whether replenishment of the inventory is needed.
  • a monitoring system monitors the state of tagged items located within an inventory and generates an event when an item is added to or removed from the inventory.
  • the monitoring system sends a unique digital identifier for the item to a mapping component.
  • the mapping component uses the unique digital identifier to locate an event router from among a plurality of event routers.
  • the monitoring system sends the event to the located event router.
  • the event router receives the event and sends the event to one or more subscribers.
  • a monitoring system monitors the state of tagged items located within an inventory and sends an event to an event router when an item is added to or removed from the inventory.
  • the event router receives the event from the monitoring system and sends the event to an item tracking system and to a second computer program.
  • the item tracking system receives the event and updates stored information about the item to reflect the event.
  • the second computer program receives the event and determines whether to send an alert to a first computer program.
  • a monitoring system monitors the state of tagged items located within an inventory and generates an event when an item is added to or removed from the inventory.
  • the monitoring system sends a unique digital identifier for the item to a mapping component.
  • the mapping component uses the unique digital identifier to locate an event router from among a plurality of event routers.
  • the monitoring system sends the event to the located event router.
  • the event router receives the event and sends the event to an item tracking system and to a second computer program.
  • the item tracking system receives the event and updates stored information about the item to reflect the event.
  • the second computer program receives the event and determines whether to send an alert to a first computer program.
  • a system in accordance with the invention enables adaptive real-time inventory management. Instead of receiving periodic reports of aggregated inventory changes, the system enables inventory changes to be reported real-time and without human intervention. Instead of replenishment planning occurring only according to a fixed schedule, the timing of replenishment planning can be adaptive, occurring more or less frequently depending on the reported real-time inventory levels.
  • FIG. 1 is a block diagram of the basic structure of an inventory management system implemented with an item tracking system in accordance with the invention.
  • FIG. 2 is a block diagram of an implementation that uses event routing.
  • FIG. 3 is a diagram of a topic structure for event routing.
  • FIG. 3 A is a diagram of a protocol flow for publication.
  • FIG. 3B is a diagram of a protocol flow for subscription.
  • FIG. 4 is a block diagram of an object naming service for locating event routers.
  • FIG. 5 is an illustration of using an event router to distribute between multiple item tracking systems.
  • FIG. 1 illustrates a retail location in relation to an item tracking system (ITS) used as part of an inventory management system.
  • the retail location is a store.
  • the store has inventory that includes tagged items. When tagged items are brought into or removed from the store, this can be detected by a monitoring system 110.
  • ITS item tracking system
  • a tagged item is a tangible item that carries or is bound to a self-identifying tag.
  • the tag might be associated with a single item or it might be associated with a collection of items, by being bound to a container containing the items, for example.
  • the tag will be an RFID (radio frequency identification) tag, but it need not be based on RF technology. Moreover, the tag can be passive (containing no internal power source for communications and data transmission) or active; and it can have processing capacity or not.
  • a tag is a digitally identifiable tag, meaning that the tag has the property that a unique digital identifier (UID) can be read directly from the tag using some kind of tag reader. Some digitally identifiable tags can also be written to.
  • UID unique digital identifier
  • An UID system is the ePC (electronic product code) system developed by the MIT Auto-ID Center.
  • An ePC is a number that can be used to identify a physical item. As currently defined, an ePC has 96-bits, partitioned into an 8-bit header and three data fields: manufacturer, product class, and serial number. The manufacturer field uniquely distinguish one manufacturer from another. For a given manufacturer, the product class field uniquely distinguish one product class from another. And the serial number field uniquely distinguishes one particular item from another item of the same product class and manufacturer. In this way, the ePC is inherently hierarchical in nature, and certain portions of the ePC number can be masked to control the level of specificity of the ePC number.
  • Tagged items can be tracked using an ITS that maintains information about tagged items including the location, status and attributes of the items.
  • An ITS can receive the information real-time from a variety of sources including other ITSs, other applications, and tag readers located on smart shelves, manufacturing lines, loading docks, and other locations.
  • An ITS maintains a virtual world model where real items and other information are represented and made available for use by other systems and by applications.
  • a local ITS serves a single enterprise or a portion of that enterprise.
  • An ITS can aggregate information from multiple other ITSs.
  • a shared ITS can combine information from multiple ITSs belonging the different enterprises.
  • An ITS includes real time input processing logic, data structures and persistent storage, an interface for queries, and communications connections between the query interface, the persistent storage, and the input processing logic.
  • the real time input processing logic accepts messages from tag readers, existing ERP systems, and other ITS systems.
  • the messages can represent creation of physical or logical items, or changes in the disposition or status of these items.
  • the messages can be in XML or other format.
  • the input processing logic interprets the incoming messages, consults the stored data, undertakes the appropriate action based on the message content and the stored data, updates the data structures as specified, and potentially returns error messages or other reports to the source of the message.
  • the data structures and persistent storage is a combination of software and hardware that records and maintains a representation of the relationships, states and histories of logical and physical items tracked by the ITS.
  • the data structures may record that a certain unique tag corresponds to a specific bottle of detergent.
  • the data structures may also record that the detergent is part of a certain inventory (a logical item with a unique ID)
  • the location of the detergent item may be periodically updated in response to real-time messages and software action from the input processing logic.
  • the data structures and persistent storage preserve the data structures over any hardware of software failures. Any robust method of building persistent storage can be used; for example, one can use software database technology and magnetic disk drives to record information in a non- volatile manner.
  • the interface for queries provides the interface between an ITS and outside enterprise software applications.
  • the monitoring system 110 includes multiple tag readers positioned at one or more locations within the store.
  • the monitoring system 110 also includes memory that stores the current state of each item in the inventory. The state indicates whether the item exists at the given location or has been removed from the location.
  • the monitoring system 110 also includes computer logic that determines when the state of the item has changed, e.g., when the item has been added or removed from the given location.
  • the logic can be further configured to send an update whenever it detects a change in the state of an item.
  • the inventory update can take the form of an event that includes the ePC of the item, the ePC of the tag reader, and a timestamp.
  • the event can also include an EM/OUT parameter that specifies whether the change is an addition or a removal of the item.
  • the monitoring system 110 includes one or more smart shelves.
  • Smart shelves are shelves that are capable of reporting when physical items are added to or removed from the shelf.
  • a smart shelf contains multiple tag readers positioned at one or more locations on the shelf.
  • a smart shelf also includes computer logic for determining whether an item has been added to or removed from the inventory.
  • An ITS 120 maintains tracking information for multiple items including the items belonging to the store inventory. Whenever items enter and leave the store, the ITS receives an event from the monitoring system 110 and updates its data storage to reflect the event.
  • An inventory planner 140 a computer program solution - normally operates on a periodic schedule to perform inventory management functions. In the operations that relate to the store, the inventory planner 140 retrieves inventory data from the ITS 120 and determines whether to replenish the store inventory.
  • the inventory planner 140 can receive alerts from an early warning agent (EWA) 130 that can cause the inventory planner to perform at least some inventory management functions, at least in relation to the store, outside of its normal periodic schedule.
  • EWA 130 can send an alert to the inventory planner 140 to cause the inventory planner to determine whether replenishment of store inventory is needed.
  • the EWA receives an event from the monitoring system 110. Using the information received in such events, the EWA determines when to send alerts to the inventory planner 140.
  • the Early Warning Agent can cause the inventory planner to perform at least some inventory management functions, at least in relation to the store, outside of its normal periodic schedule.
  • the EWA 130 can send an alert to the inventory planner 140 to cause the inventory planner to determine whether replenishment of store inventory is needed.
  • the EWA receives an event from the monitoring system 110. Using the information received in such events, the EWA determines when to send alerts to the inventory planner 140.
  • the Early Warning Agent can cause the inventory planner to perform at least some inventory management functions, at least in relation to the store, outside of
  • the EWA 130 includes logic for determining when to send an alert.
  • the determination of whether to send an alert includes applying one or more rules to the information received in inventory updates.
  • a rule specifies a certain condition and a certain action to be performed when the condition is met. For example, a rule can specify- that an alert should be sent whenever the inventory level drops below a specific value.
  • the EWA 130 can apply a pre-determined set of rules, or alternatively, the EWA 130 can include artificial intelligence logic that enables the EWA 130 to adapt its behavior in response to current or historical inventory patterns.
  • the artificial intelligence logic enables the EWA to estimate potential variation in inventory levels in the near future in order to identify potentially risky situations early enough to allow for corrective measures. For example, initially the rules may specify that an alert should be fired when the inventory drops below 10. However, if the EWA 130 detects that it sends alerts much more frequently during the summer season than during other seasons, the EWA 130 may adapt to this seasonal variation by increasing the threshold from 10 to 20 during the summer season so that the inventory planner 140 is notified earlier of the impending inventory shortage. This adaptive behavior occurs with minimal human intervention, and with minimal need of parameter adjustment or any other kind of manual calibration.
  • the EWA 130 can retrieve and analyze current and historical inventory data to detect trends such as deviations between planned replenishment and actual replenishment and to build a predictive model of future inventory needs. These trends and predictions can be determined using linear regression, classification and regression trees, or other stochastic algorithms.
  • the EWA 130 estimates the potential variation for each planned replenishment or consumption activity that may affect the inventory (e.g., given historical performance data, it estimates that a planned truckload of 12oz Bottles from Bob's Bottles will arrive any time within 4 hours prior to 6 hours after the planned delivery time, with a quantity that is between 95% and 100% of the requested quantity).
  • the EWA 130 compares the promised and actual delivery time for various quantities of inventory delivered in the past to generate predictions for actual delivery dates and quantities for future replenishment activities that are planned but not yet completed.
  • the EWA 130 combines the estimates of potential variation for several individual activities into an estimate of the potential variation for an entire inventory. These algorithms can be implemented using decision trees such as classification and regression trees.
  • the EWA 130 builds the predictive model based on aggregate data that represents cumulative levels of replenishment and consumption.
  • These algorithms can be implemented using a probabilistic inference model such as conditional Gaussian approximation.
  • the inventory planner 140 can be any application that generates inventory replenishment plans.
  • One such inventory planner 140 is the Advanced Planner and Optimizer (APO) available from SAP AG.
  • APO Advanced Planner and Optimizer
  • the inventory planner 140 includes logic for generating replenishment plans.
  • the logic includes logic for receiving an alert from the EWA 130 and, in response to the alert, determining whether replenishment is needed.
  • the inventory planner 140 generates replenishment plans for an entire inventory.
  • An EWA 130 monitors a portion of the inventory. Multiple EWAs 130 can be combined to cover the entire inventory.
  • An alert pertaining to one portion of the inventory triggers the inventory planner 140 to make a determination as to whether the planned replenishment for the entire inventory needs to be re-planned.
  • the determination can include retrieving inventory data from the ITS 120 and determining or forecasting demand based on the retrieved inventory data. For example, a trend of high demand for product X may cause the inventory planner 140 to plan for not only more product X but also more product Y, a product for which product X is known to be a leading indicator.
  • Event routing FIG. 2 is a block diagram of an implementation of the invention that uses event routing. Events are messages that are passed from one software entity to another. Events can be used to notify the recipient of the event about some occurrence or to send a request to the recipient. An event routing middleware such as an event router (ER) 210 can be used distributes events between various entities, for example, between the monitoring system 110, the ITS 120, the EWA 130 and the inventory planner 140.
  • ER event router
  • suitable event routers include the topic-based KnowNow® event router, available from KnowNow Incorporated of Mountain View, California, or the content-based Elvin messaging service available from the Distributed Systems Technology Center of Queensland, Australia.
  • the topic-based and content-based event routers can also be used in combination.
  • messages are routed from the publishers to subscribers based on the content of each message.
  • the content of each message can be partitioned into multiple content fields. For example, a message relating to an item having the ePC, 01.0037F2.001508.000319F827 can be split into the following content fields:
  • a seen@ message is a message reporting that the item has been detected at a particular location.
  • a "request” message is used to send a request to a subscriber and a "response” message is used to publish the requested information.
  • Other message types can also be defined.
  • events can be categorized according to topics.
  • a software entity may only be interested in events pertaining to certain topics.
  • the software entity can subscribe to only certain topics and it will only receive events pertaining to those topics and not to others.
  • FIG. 3 shows a topic structure based on the structure of an ePC.
  • a separate topic can be created for each of the data fields of the ePC, namely, the manufacturer, product class and serial number. For example, for an item having the ePC
  • This topic includes all the events reported to topic 3, and also events relating to other items having the same manufacturer, 0037F2.
  • a topic-based event router has a topic set and each topic has an address, e.g., a URL.
  • An event can be published to a topic by sending the event to the address for that topic.
  • a publishing entity such as the monitoring system 110 ( FIG. 2) can consult an extended object naming service (EONS) 220.
  • EONS 220 maintains mappings between item ePCs (or a reader ePCs) and one or more ERs, along with their corresponding topics.
  • An EONS takes as input an ePC of an item (or reader) and returns the URL(s) for one or more identified topics.
  • the EONS 220 can be implemented by extending a conventional ONS such as the ONS developed by Oat Systems and the MIT Auto-ID Center, which is further described in the Object Name Service Technical Manual (published by MIT Auto-ID Center).
  • Conventional object naming systems are similar to and are based on the well-known Domain Name System (DNS) for the Internet.
  • DNS Domain Name System
  • the monitoring system 110 identifies that an item has been added or removed from the inventory.
  • the monitoring system 110 generates an event which includes a tag identifier, a reader identifier and a timestamp.
  • the tag identifier identifies the item that has changed.
  • the reader identifier identifies the reader that detected the change.
  • the timestamp identifies when the change was detected.
  • the monitoring system 110 then consults the EONS 220 to determine where to send the event.
  • the monitoring system 110 provides the EONS with the ePC of the item and the ePC of the reader and receives back from the EONS the URLs for the item topic and the reader topic.
  • the monitoring system 110 then sends the event to both topics.
  • the ER(s) for the item topic and the reader topic routes the events to one or more subscribers.
  • the ITS can be a subscriber to the item topic and the EWA can be a subscriber to the reader topic.
  • the EWA receives the event from the ER and determines whether to send an alert to the inventory planner.
  • the inventory planner can send an event to the ER requesting inventory data.
  • the ER then routes the event to the ITS, which responds by sending the requested inventory data to the inventory planner. Protocol flow for subscription
  • the subscriber For each topic for which the subscriber wishes to subscribe, the subscriber first consults the EONS to determine the address of the ER for the given topic and then listens for events to be published to the topic.
  • the subscriber can use the reader identifier contained in the event to determine the location of the item.
  • the location can be a physical location
  • an EONS can maintain mappings between multiple tagged items (or readers) and multiple ERs. As discussed above, the mappings support multiple keys, including an item key and a reader key.
  • the EONS can service multiple monitoring systems 110 and other tag reader applications.
  • the EONS is a distributed subsystem that includes mapping information, query servers for responding to queries requesting information location, and name resolvers that can receive an ePC and resolve the ePC into an ER location.
  • a particular ER can distribute to multiple ITSs (as well as to other subscribers) and a particular ITS can subscribe to multiple ERs.
  • a user can define a desired scope for each ITS and configure the distribution scheme accordingly.
  • the invention can be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them.
  • Apparatus of the invention can be implemented in a computer program product tangibly embodied in an information carrier, e.g., in a machine-readable storage device or in a propagated signal, for execution by a programmable processor; and method steps of the invention can be performed by a programmable processor executing a program of instructions to perform functions of the invention by operating on input data and generating output.
  • the invention can be implemented advantageously in one or more computer programs that are executable on a programmable system including at least one programmable processor coupled to receive data and instructions from, and to transmit data and instructions to, a data storage system, at least one input device, and at least one output device.
  • a computer program is a set of instructions that can be used, directly or indirectly, in a computer to perform a certain activity or bring about a certain result.
  • a computer program can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.
  • Suitable processors for the execution of a program of instructions include, by way of example, both general and special purpose microprocessors, and the sole processor or one of multiple processors of any kind of computer.
  • a processor will receive instructions and data from a read-only memory or a random access memory or both.
  • the essential elements of a computer are a processor for executing instructions and one or more memories for storing instructions and data.
  • a computer will also include, or be operatively coupled to communicate with, one or more mass storage devices for storing data files; such devices include magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and optical disks.
  • Storage devices suitable for tangibly embodying computer program instructions and data include all forms of non- volatile memory, including by way of example semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DND-ROM disks.
  • semiconductor memory devices such as EPROM, EEPROM, and flash memory devices
  • magnetic disks such as internal hard disks and removable disks
  • magneto-optical disks and CD-ROM and DND-ROM disks.
  • the processor and the memory can be supplemented by, or incorporated in, ASICs (application-specific integrated circuits).
  • ASICs application-specific integrated circuits
  • the invention can be implemented on a computer having a display device such as a CRT (cathode ray tube) or LCD (liquid crystal display) monitor for displaying information to the user and a keyboard and a pointing device such as a mouse or a trackball by which the user can provide input to the computer.
  • a display device such as a CRT (cathode ray tube) or LCD (liquid crystal display) monitor for displaying information to the user and a keyboard and a pointing device such as a mouse or a trackball by which the user can provide input to the computer.
  • the invention can be implemented in a computer system that includes a back-end component, such as a data server, or that includes a middleware component, such as an application server or an Internet server, or that includes a front-end component, such as a client computer having a graphical user interface or an Internet browser, or any combination of them.
  • a back-end component such as a data server
  • a middleware component such as an application server or an Internet server
  • a front-end component such as a client computer having a graphical user interface or an Internet browser, or any combination of them.
  • the components of the system can be connected by any form or medium of digital data communication.

Abstract

Methods and apparatus, including computer program products, for communicating item disposition information between publishers and subscribers such as RFID tag readers and item tracking systems. Event routers can be used to distribute the information and an extended object naming service can be used to locate event routers. The items being tracked can have a hierarchical relationship with each other. Subscribers can choose to subscribe only to events relating to items at a particular level of the hierarchy. The methods and apparatus can be used to provide real-time inventory management. Changes to the inventory including the addition or removal of an item from the inventory are reported to the item tracking system in real-time.

Description

EVENT-BASED COMMUNICATION IN A DISTRIBUTED
ITEM TRACKING SYSTEM
BACKGROUND This invention relates to communication in a distributed item tracking system. This invention can serve as an underlying communication infrastructure for a number of higher-level applications including supply chain management (SCM) software.
SCM software such as the SCM solutions provided by SAP AG of Walldorf, Germany, enable a user to manage materials, information, and finances as they move in a process from a supplier to a manufacturer to a wholesaler to a retailer. The SCM software generally implements algorithms for determining the best means to fill an order and also includes databases for tracking the physical status of the goods, the management of materials, and financial information.
Inventory management is a component of most SCM systems. Inventory management enables suppliers to keep track of how much inventory they have and how much inventory they have distributed to particular retailers. Periodically, the retailer reports to the supplier the current inventory level of the store. Based on the report, the supplier determines whether the store inventory needs to be replenished.
Typically, suppliers and retailers develop a planning schedule of how often the retailers will report to the supplier. For example, every Thursday, the retailer reports the current inventory level of the store and replenishment planning occurs. On Friday, any new inventory arrives at the store in time for the weekend shoppers.
SUMMARY In general, in one aspect, the invention features methods and apparatus, including computer program products, for communicating item disposition information in a distributed system. The system includes a monitoring system, one or more subscribers, including a system that tracks tagged items, and one or more event routers. The monitoring system is operable to detect one or more of the tagged items, generate an event, the event including a tag identifier, a reader identifier, and a timestamp, and publish the event to one or more of the event routers. The system for tracking tagged items is operable to subscribe to receive from one or more of the event routers events relating to one or more of the tagged items, and upon receiving events, use the received events to update disposition information for one or more of the tagged items. Each event router is operable to maintain a list of subscribers, receive events from the monitoring system, and send events to the subscribers.
In general, in another aspect, a monitoring system monitors the state of tagged items located within an inventory and sends an event to an event router when an item is added to or removed from the inventory. The event router receives the event from the monitoring system and sends the event to one or more item tracking systems. The item tracking systems receive the event and update stored information about the item to reflect the event.
In general, in another aspect, a monitoring system monitors the state of tagged items located within an inventory and sends an event to an event router when an item is added to or removed from the inventory. An event router receives the event from the monitoring system and sends the event to a second computer program. The second computer program receives the event and determines whether to send an alert to a first computer program. Upon receiving an alert from the second computer program, the first computer program determines whether replenishment of the inventory is needed.
In general, in another aspect, a monitoring system monitors the state of tagged items located within an inventory and generates an event when an item is added to or removed from the inventory. The monitoring system sends a unique digital identifier for the item to a mapping component. The mapping component uses the unique digital identifier to locate an event router from among a plurality of event routers. The monitoring system sends the event to the located event router. The event router receives the event and sends the event to one or more subscribers.
In general, in another aspect, a monitoring system monitors the state of tagged items located within an inventory and sends an event to an event router when an item is added to or removed from the inventory. The event router receives the event from the monitoring system and sends the event to an item tracking system and to a second computer program. The item tracking system receives the event and updates stored information about the item to reflect the event. The second computer program receives the event and determines whether to send an alert to a first computer program. In general, in another aspect, a monitoring system monitors the state of tagged items located within an inventory and generates an event when an item is added to or removed from the inventory. The monitoring system sends a unique digital identifier for the item to a mapping component. The mapping component uses the unique digital identifier to locate an event router from among a plurality of event routers. The monitoring system sends the event to the located event router. The event router receives the event and sends the event to an item tracking system and to a second computer program. The item tracking system receives the event and updates stored information about the item to reflect the event. The second computer program receives the event and determines whether to send an alert to a first computer program.
The invention can be implemented to realize one or more of the following advantages. A system in accordance with the invention enables adaptive real-time inventory management. Instead of receiving periodic reports of aggregated inventory changes, the system enables inventory changes to be reported real-time and without human intervention. Instead of replenishment planning occurring only according to a fixed schedule, the timing of replenishment planning can be adaptive, occurring more or less frequently depending on the reported real-time inventory levels.
The details of one or more embodiments of the invention are set forth in the accompanying drawings and the description below. Other features and advantages of the invention will become apparent from the description, the drawings, and the claims.
DESCRIPTION OF DRAWINGS
FIG. 1 is a block diagram of the basic structure of an inventory management system implemented with an item tracking system in accordance with the invention.
FIG. 2 is a block diagram of an implementation that uses event routing. FIG. 3 is a diagram of a topic structure for event routing.
FIG. 3 A is a diagram of a protocol flow for publication.
FIG. 3B is a diagram of a protocol flow for subscription.
FIG. 4 is a block diagram of an object naming service for locating event routers.
FIG. 5 is an illustration of using an event router to distribute between multiple item tracking systems.
Like reference symbols in the various drawings indicate like elements.
DETAILED DESCRIPTION For illustrative purposes, the invention will be described in terms of its use in a specific scenario, an inventory management scenario. FIG. 1 illustrates a retail location in relation to an item tracking system (ITS) used as part of an inventory management system. The retail location is a store. The store has inventory that includes tagged items. When tagged items are brought into or removed from the store, this can be detected by a monitoring system 110.
A tagged item is a tangible item that carries or is bound to a self-identifying tag. The tag might be associated with a single item or it might be associated with a collection of items, by being bound to a container containing the items, for example.
Generally, the tag will be an RFID (radio frequency identification) tag, but it need not be based on RF technology. Moreover, the tag can be passive (containing no internal power source for communications and data transmission) or active; and it can have processing capacity or not. A tag is a digitally identifiable tag, meaning that the tag has the property that a unique digital identifier (UID) can be read directly from the tag using some kind of tag reader. Some digitally identifiable tags can also be written to.
One UID system is the ePC (electronic product code) system developed by the MIT Auto-ID Center. An ePC is a number that can be used to identify a physical item. As currently defined, an ePC has 96-bits, partitioned into an 8-bit header and three data fields: manufacturer, product class, and serial number. The manufacturer field uniquely distinguish one manufacturer from another. For a given manufacturer, the product class field uniquely distinguish one product class from another. And the serial number field uniquely distinguishes one particular item from another item of the same product class and manufacturer. In this way, the ePC is inherently hierarchical in nature, and certain portions of the ePC number can be masked to control the level of specificity of the ePC number. For example, if an application only wants to know about the tracking information at the manufacturer level (e.g., which locations contain products manufactured by Spalding?), then the product class and serial number bits can be masked. UIDs other than ePCs can be used similarly. Tagged items can be tracked using an ITS that maintains information about tagged items including the location, status and attributes of the items. An ITS can receive the information real-time from a variety of sources including other ITSs, other applications, and tag readers located on smart shelves, manufacturing lines, loading docks, and other locations. An ITS maintains a virtual world model where real items and other information are represented and made available for use by other systems and by applications.
Normally, a local ITS serves a single enterprise or a portion of that enterprise. An ITS can aggregate information from multiple other ITSs. A shared ITS can combine information from multiple ITSs belonging the different enterprises. An ITS includes real time input processing logic, data structures and persistent storage, an interface for queries, and communications connections between the query interface, the persistent storage, and the input processing logic.
The real time input processing logic accepts messages from tag readers, existing ERP systems, and other ITS systems. The messages can represent creation of physical or logical items, or changes in the disposition or status of these items. The messages can be in XML or other format. The input processing logic interprets the incoming messages, consults the stored data, undertakes the appropriate action based on the message content and the stored data, updates the data structures as specified, and potentially returns error messages or other reports to the source of the message.
The data structures and persistent storage is a combination of software and hardware that records and maintains a representation of the relationships, states and histories of logical and physical items tracked by the ITS. For example, the data structures may record that a certain unique tag corresponds to a specific bottle of detergent. The data structures may also record that the detergent is part of a certain inventory (a logical item with a unique ID) The location of the detergent item may be periodically updated in response to real-time messages and software action from the input processing logic. The data structures and persistent storage preserve the data structures over any hardware of software failures. Any robust method of building persistent storage can be used; for example, one can use software database technology and magnetic disk drives to record information in a non- volatile manner.
The interface for queries provides the interface between an ITS and outside enterprise software applications.
The monitoring system 110 includes multiple tag readers positioned at one or more locations within the store. The monitoring system 110 also includes memory that stores the current state of each item in the inventory. The state indicates whether the item exists at the given location or has been removed from the location. The monitoring system 110 also includes computer logic that determines when the state of the item has changed, e.g., when the item has been added or removed from the given location. The logic can be further configured to send an update whenever it detects a change in the state of an item. The inventory update can take the form of an event that includes the ePC of the item, the ePC of the tag reader, and a timestamp. The event can also include an EM/OUT parameter that specifies whether the change is an addition or a removal of the item. In one implementation, the monitoring system 110 includes one or more smart shelves. Smart shelves are shelves that are capable of reporting when physical items are added to or removed from the shelf. A smart shelf contains multiple tag readers positioned at one or more locations on the shelf. A smart shelf also includes computer logic for determining whether an item has been added to or removed from the inventory. An ITS 120 maintains tracking information for multiple items including the items belonging to the store inventory. Whenever items enter and leave the store, the ITS receives an event from the monitoring system 110 and updates its data storage to reflect the event. An inventory planner 140 — a computer program solution - normally operates on a periodic schedule to perform inventory management functions. In the operations that relate to the store, the inventory planner 140 retrieves inventory data from the ITS 120 and determines whether to replenish the store inventory. The inventory planner 140 can receive alerts from an early warning agent (EWA) 130 that can cause the inventory planner to perform at least some inventory management functions, at least in relation to the store, outside of its normal periodic schedule. In particular, the EWA 130 can send an alert to the inventory planner 140 to cause the inventory planner to determine whether replenishment of store inventory is needed. Whenever items enter and leave the store, and optionally even when they more from one part of the store to another, the EWA receives an event from the monitoring system 110. Using the information received in such events, the EWA determines when to send alerts to the inventory planner 140. The Early Warning Agent
The EWA 130 includes logic for determining when to send an alert. The determination of whether to send an alert includes applying one or more rules to the information received in inventory updates. A rule specifies a certain condition and a certain action to be performed when the condition is met. For example, a rule can specify- that an alert should be sent whenever the inventory level drops below a specific value.
The EWA 130 can apply a pre-determined set of rules, or alternatively, the EWA 130 can include artificial intelligence logic that enables the EWA 130 to adapt its behavior in response to current or historical inventory patterns. The artificial intelligence logic enables the EWA to estimate potential variation in inventory levels in the near future in order to identify potentially risky situations early enough to allow for corrective measures. For example, initially the rules may specify that an alert should be fired when the inventory drops below 10. However, if the EWA 130 detects that it sends alerts much more frequently during the summer season than during other seasons, the EWA 130 may adapt to this seasonal variation by increasing the threshold from 10 to 20 during the summer season so that the inventory planner 140 is notified earlier of the impending inventory shortage. This adaptive behavior occurs with minimal human intervention, and with minimal need of parameter adjustment or any other kind of manual calibration.
The EWA 130 can retrieve and analyze current and historical inventory data to detect trends such as deviations between planned replenishment and actual replenishment and to build a predictive model of future inventory needs. These trends and predictions can be determined using linear regression, classification and regression trees, or other stochastic algorithms.
In one implementation, the EWA 130 estimates the potential variation for each planned replenishment or consumption activity that may affect the inventory (e.g., given historical performance data, it estimates that a planned truckload of 12oz Bottles from Bob's Bottles will arrive any time within 4 hours prior to 6 hours after the planned delivery time, with a quantity that is between 95% and 100% of the requested quantity). The EWA 130 compares the promised and actual delivery time for various quantities of inventory delivered in the past to generate predictions for actual delivery dates and quantities for future replenishment activities that are planned but not yet completed. The EWA 130 combines the estimates of potential variation for several individual activities into an estimate of the potential variation for an entire inventory. These algorithms can be implemented using decision trees such as classification and regression trees.
In another implementation, instead of considering individual activities, the EWA 130 builds the predictive model based on aggregate data that represents cumulative levels of replenishment and consumption. These algorithms can be implemented using a probabilistic inference model such as conditional Gaussian approximation.
Inventory Planner
The inventory planner 140 can be any application that generates inventory replenishment plans. One such inventory planner 140 is the Advanced Planner and Optimizer (APO) available from SAP AG. The inventory planner 140 includes logic for generating replenishment plans. The logic includes logic for receiving an alert from the EWA 130 and, in response to the alert, determining whether replenishment is needed.
In one implementation, the inventory planner 140 generates replenishment plans for an entire inventory. An EWA 130 monitors a portion of the inventory. Multiple EWAs 130 can be combined to cover the entire inventory. An alert pertaining to one portion of the inventory triggers the inventory planner 140 to make a determination as to whether the planned replenishment for the entire inventory needs to be re-planned.
The determination can include retrieving inventory data from the ITS 120 and determining or forecasting demand based on the retrieved inventory data. For example, a trend of high demand for product X may cause the inventory planner 140 to plan for not only more product X but also more product Y, a product for which product X is known to be a leading indicator. Event routing FIG. 2 is a block diagram of an implementation of the invention that uses event routing. Events are messages that are passed from one software entity to another. Events can be used to notify the recipient of the event about some occurrence or to send a request to the recipient. An event routing middleware such as an event router (ER) 210 can be used distributes events between various entities, for example, between the monitoring system 110, the ITS 120, the EWA 130 and the inventory planner 140. Examples of suitable event routers include the topic-based KnowNow® event router, available from KnowNow Incorporated of Mountain View, California, or the content-based Elvin messaging service available from the Distributed Systems Technology Center of Queensland, Australia. The topic-based and content-based event routers can also be used in combination.
Content-based event routing
In one implementation, messages are routed from the publishers to subscribers based on the content of each message. The content of each message can be partitioned into multiple content fields. For example, a message relating to an item having the ePC, 01.0037F2.001508.000319F827 can be split into the following content fields:
(1) Header : 01
(2) Manufacturer: 0037F2
(3) Product class: 001508
(4) Serial number: 000319F827 (5) Message type: seen@, request, response — A seen@ message is a message reporting that the item has been detected at a particular location. A "request" message is used to send a request to a subscriber and a "response" message is used to publish the requested information. Other message types can also be defined. The subscriber can specify message filters based on the value of the content fields (e.g., manufacturer = 0037F2 & message type^seen®).
Topic-based event routing
In an alternate implementation, events can be categorized according to topics. A software entity may only be interested in events pertaining to certain topics. The software entity can subscribe to only certain topics and it will only receive events pertaining to those topics and not to others.
FIG. 3 shows a topic structure based on the structure of an ePC. A separate topic can be created for each of the data fields of the ePC, namely, the manufacturer, product class and serial number. For example, for an item having the ePC
01.0037F2.001508.000319F827, the following topics can be created:
(1) \centauri\0037F2\001508\000319F827\seen@-This topic covers "seen@" events relating to the item.
(2) \centauri\0037F2\001508\000319F827\*-This topic includes both the events reported to topic 1 and also other kinds of events relating to the item, such as "request" and "response" events.
(3) \centauri\0037F2\001508\*~This topic includes both the events reported to topic 2 and also events relating to other items within the same product class, 001508.
(4) \centauri\0037F2\*-- This topic includes all the events reported to topic 3, and also events relating to other items having the same manufacturer, 0037F2.
Separate topics can also be created for events pertaining to readers. For example, for a reader having the ePC 01.0B39C2. 000815.004711F827, the following topics can be created:
(1) centauri\0B39C2000815004711F827\Have-Seen-ePC~This topic covers events relating to a particular reader having detected a particular ePC.
(2) centauri\0B39C2000815004711F827\*--This topic covers events relating to a particular reader having detected any ePC.
A topic-based event router has a topic set and each topic has an address, e.g., a URL. An event can be published to a topic by sending the event to the address for that topic. To determine the URL of the appropriate topic to publish an event to, a publishing entity such as the monitoring system 110 ( FIG. 2) can consult an extended object naming service (EONS) 220. An EONS 220 maintains mappings between item ePCs (or a reader ePCs) and one or more ERs, along with their corresponding topics. An EONS takes as input an ePC of an item (or reader) and returns the URL(s) for one or more identified topics. The EONS 220 can be implemented by extending a conventional ONS such as the ONS developed by Oat Systems and the MIT Auto-ID Center, which is further described in the Object Name Service Technical Manual (published by MIT Auto-ID Center). Conventional object naming systems are similar to and are based on the well-known Domain Name System (DNS) for the Internet.
Protocol flow for publication
In operation, as shown in FIG. 3 A, the monitoring system 110 identifies that an item has been added or removed from the inventory. The monitoring system 110 generates an event which includes a tag identifier, a reader identifier and a timestamp. The tag identifier identifies the item that has changed. The reader identifier identifies the reader that detected the change. And the timestamp identifies when the change was detected.
The monitoring system 110 then consults the EONS 220 to determine where to send the event. The monitoring system 110 provides the EONS with the ePC of the item and the ePC of the reader and receives back from the EONS the URLs for the item topic and the reader topic. The monitoring system 110 then sends the event to both topics.
The ER(s) for the item topic and the reader topic routes the events to one or more subscribers. For example, the ITS can be a subscriber to the item topic and the EWA can be a subscriber to the reader topic. The EWA receives the event from the ER and determines whether to send an alert to the inventory planner.
If an alert is sent, this triggers the inventory planner to re-plan the replenishment of the inventory. To obtain the current data for the inventory, the inventory planner can send an event to the ER requesting inventory data. The ER then routes the event to the ITS, which responds by sending the requested inventory data to the inventory planner. Protocol flow for subscription
As shown in FIG. 3B, for each topic for which the subscriber wishes to subscribe, the subscriber first consults the EONS to determine the address of the ER for the given topic and then listens for events to be published to the topic.
Upon receiving an event, the subscriber can use the reader identifier contained in the event to determine the location of the item. The location can be a physical location
(e.g., a specific latitude, longitude and altitude) or a logical location (e.g., inside container XYZ or truck ABC). The subscriber can also use the tag identifier to locate additional information about the item. For example, the tag identifier can be used to retrieve a PML (product markup language) document for the item. As shown in FIG. 4, an EONS can maintain mappings between multiple tagged items (or readers) and multiple ERs. As discussed above, the mappings support multiple keys, including an item key and a reader key. The EONS can service multiple monitoring systems 110 and other tag reader applications. In one implementation, the EONS is a distributed subsystem that includes mapping information, query servers for responding to queries requesting information location, and name resolvers that can receive an ePC and resolve the ePC into an ER location.
As shown in FIG. 5, a particular ER can distribute to multiple ITSs (as well as to other subscribers) and a particular ITS can subscribe to multiple ERs. A user can define a desired scope for each ITS and configure the distribution scheme accordingly.
The invention can be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. Apparatus of the invention can be implemented in a computer program product tangibly embodied in an information carrier, e.g., in a machine-readable storage device or in a propagated signal, for execution by a programmable processor; and method steps of the invention can be performed by a programmable processor executing a program of instructions to perform functions of the invention by operating on input data and generating output. The invention can be implemented advantageously in one or more computer programs that are executable on a programmable system including at least one programmable processor coupled to receive data and instructions from, and to transmit data and instructions to, a data storage system, at least one input device, and at least one output device. A computer program is a set of instructions that can be used, directly or indirectly, in a computer to perform a certain activity or bring about a certain result. A computer program can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.
Suitable processors for the execution of a program of instructions include, by way of example, both general and special purpose microprocessors, and the sole processor or one of multiple processors of any kind of computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memories for storing instructions and data. Generally, a computer will also include, or be operatively coupled to communicate with, one or more mass storage devices for storing data files; such devices include magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and optical disks. Storage devices suitable for tangibly embodying computer program instructions and data include all forms of non- volatile memory, including by way of example semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DND-ROM disks. The processor and the memory can be supplemented by, or incorporated in, ASICs (application-specific integrated circuits).
To provide for interaction with a user, the invention can be implemented on a computer having a display device such as a CRT (cathode ray tube) or LCD (liquid crystal display) monitor for displaying information to the user and a keyboard and a pointing device such as a mouse or a trackball by which the user can provide input to the computer.
The invention can be implemented in a computer system that includes a back-end component, such as a data server, or that includes a middleware component, such as an application server or an Internet server, or that includes a front-end component, such as a client computer having a graphical user interface or an Internet browser, or any combination of them. The components of the system can be connected by any form or medium of digital data communication.
The invention has been described in terms of particular embodiments. Other embodiments are within the scope of the following claims. For example, steps of the invention can be performed in a different order and still achieve desirable results.. The invention can be applied to other scenarios besides inventory management. For example, the invention can be applied in the production context where production is planned according to the receipt of customer orders. An EWA can be used to alert the production planner when orders have been made. Accordingly, other embodiments are within the scope of the following claims.

Claims

1. A method to be performed by a system that tracks items, the method comprising: subscribing to receive from one or more event routers events relating to one or more tagged items, each event including a tag identifier for a tag bound to an item, a reader identifier; and a timestamp; receiving from the event router events related to the one or more tagged items; and using the received events to update disposition information for the one or more tagged items.
2. The method of claim 1 , wherein the tagged items have a hierarchical relationship with each other and subscribing includes subscribing only to events relating to items at a particular level of the hierarchy.
3. The method of claim 1 , further comprising: using a mapping service and all or part of the tag identifier to determine which event router to subscribe to.
4. The method of claim 3 , wherein the tag identifier has a first portion that specifies the manufacturer of the item, a second portion that specifies the product class of the item, and a third portion that specifies a serial number of the item.
5. The method of claim 1 , wherein the tag is a radio frequency identification (RFID) tag and the tag identifier is an electronic product code (ePC).
6. A method to be performed by a tag reader, the method comprising: detecting an item; generating an event, the event including a tag identifier associated with a tag bound to the item, a reader identifier, and a timestamp; using a mapping service and either the tag identifier or the reader identifier to identify one or more event routers; and publishing the event to the identified event routers.
7. The method of claim 6, wherein the tag is a radio frequency identification (RFID) tag and the tag identifier is an electronic product code (ePC).
8. A system, comprising: a monitoring system including one or more tag readers; one or more subscribers, including a system that tracks tagged items; and one or more event routers, wherein: the monitoring system is operable to: detect one or more of the tagged items; generate an event, the event including a tag identifier, a reader identifier, and a timestamp; and publish the event to one or more of the event routers; the system for tracking tagged items is operable to: subscribe to receive from one or more of the event routers events relating to one or more of the tagged items; and upon receiving events, use the received events to update disposition information for one or more of the tagged items; and each event router is operable to: maintain a list of subscribers; receive events from the monitoring system; and send events to the subscribers.
9. The system of claim 8, wherein the monitoring system is further operable to: use a mapping service and either the tag identifier or the reader identifier to identify one or more event routers; and publish the event to the identified event routers.
10. The system of claim 8, wherein each subscriber is operable to use a mapping service and all or part of the tag identifier to determine which event router to subscribe to.
11. The system of claim 8, wherein each subscriber is operable to use a mapping service and all or part of the reader identifier to determine which event router to subscribe to.
12. The system of claim 8, wherein the tagged items have a hierarchical relationship with each other and a subscriber is operable to subscribe only to events relating to items at a particular level of the hierarchy.
13. The system of claim 8, wherein the tag is a radio frequency identification (RFID) tag and the tag identifier is an electronic product code (ePC).
14. The system of claim 8, wherein each event belongs to an event type, at least two events belong to different event types and a subscriber is operable to subscribe only to
5 events of a particular event type.
15. Apparatus comprising: a monitoring system including: a tag reader configured to read tags from tagged items located within an inventory; and o means for detecting and reporting that an item has been added to or removed from the inventory; one or more item tracking systems, each item tracking system including: a memory that stores information about tagged items; input processing logic configured to process messages containing information 5 about changes in the location of a tagged item and to store the information in the memory; and a query interface configured to respond to queries about the tagged items; and an event router including: a registry of subscribers, the subscribers including the one or more item tracking 0 systems; and means for receiving an event from the monitoring system and sending the event to the one or more item tracking systems.
16. The apparatus of claim 15, wherein the event includes a unique digital identifier for an item, a unique digital identifier for a reader and a timestamp.
5 17. The apparatus of claim 15, wherein the event further includes a parameter that indicates whether the item has been added to the inventory or whether the item has been removed from the inventory.
18. Apparatus comprising: a monitoring system including: a tag reader configured to read tags from tagged items located within an inventory; and means for detecting and reporting that an item has been added to or removed from the inventory; a first computer program configured to determine whether replenishment of the inventory is needed; a second computer program configured to determine whether to send an alert to the first computer program; and an event router including: a registry of subscribers, the subscribers including the first computer program; and means for receiving an event from the monitoring system and sending the event to the second computer program.
19. The apparatus of claim 18, wherein the event includes a unique digital identifier for an item, a unique digital identifier for a reader and a timestamp.
20. The apparatus of claim 18, wherein the event further includes a parameter that indicates whether the item has been added to the inventory or whether the item has been removed from the inventory.
21. The apparatus of claim 18, wherein the second computer program is configured to apply a pre-determined set of rules to determine whether to send the alert.
22. The apparatus of claim 18, wherein the second computer program is further configured to analyze inventory data to detect trends in the data.
23. Apparatus comprising: a monitoring system including: a tag reader configured to read tags from tagged items located within an inventory; and means for detecting and reporting that an item has been added to or removed from the inventory; a plurality of event routers, each event router including: a registry of subscribers; and means for receiving an event from the monitoring system and sending the event to one or more of the subscribers; and a mapping component including: a memory that stores mappings between an item identifier and an event router and between a reader identifier and an event router; and means for receiving an item or reader identifier from the monitoring system and using the item or reader identifier to locate an event router.
24. Apparatus comprising: a monitoring system including: a tag reader configured to read tags from tagged items located within an inventory; and means for detecting and reporting that an item has been added or removed from the inventory; an item tracking system including: a memory that stores information about tagged items; input processing logic configured to process messages containing information about changes in the location of a tagged item and to store the information in the memory; and a query interface configured to respond to queries about the tagged items; a first computer program configured to determine whether replenishment of the inventory is needed; and a second computer program configured to receive an event from the monitoring system and to determine whether to send an alert to the first computer program.
25. A system comprising: a monitoring system including: a tag reader configured to read tags from tagged items located within an inventory; and means for detecting and reporting that an item has been added to or removed from the inventory; an item tracking system including: a memory that stores information about tagged items; input processing logic configured to process messages containing information about changes in the location of a tagged item and to store the information in the memory; and a query interface configured to respond to queries about the tagged items; a first computer program configured to determine whether replenishment of the inventory is needed; a second computer program configured to receive an event from the monitoring system and to determine whether to send an alert to the first computer program; an event router including: a registry of subscribers, the subscribers including the item tracking system, the first computer program and the second computer program; and means for receiving an event from the monitoring system and sending the event to one or more of the subscribers; and a mapping component including: memory that stores mappings between an item identifier and an event router and between a reader identifier and an event router; and means for receiving an item identifier from the monitoring system and using the item identifier to locate an event router.
PCT/US2003/016967 2002-05-31 2003-05-30 System and method for supply chain event management WO2003102845A2 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP03756267A EP1532560A2 (en) 2002-05-31 2003-05-30 System and method for supply chain event management
AU2003243340A AU2003243340A1 (en) 2002-05-31 2003-05-30 System and method for supply chain event management
JP2004509857A JP4776921B2 (en) 2002-05-31 2003-05-30 Event-based communication in distributed item tracking systems

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US10/159,598 US6681990B2 (en) 2002-05-31 2002-05-31 Item tracking systems and real-time inventory management
US10/159,598 2002-05-31
US10/285,381 2002-10-30
US10/285,381 US6843415B2 (en) 2002-01-11 2002-10-30 Event-based communication in a distributed item tracking system

Publications (2)

Publication Number Publication Date
WO2003102845A2 true WO2003102845A2 (en) 2003-12-11
WO2003102845A3 WO2003102845A3 (en) 2004-02-05

Family

ID=29714715

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2003/016967 WO2003102845A2 (en) 2002-05-31 2003-05-30 System and method for supply chain event management

Country Status (4)

Country Link
US (1) US6843415B2 (en)
EP (1) EP1532560A2 (en)
AU (1) AU2003243340A1 (en)
WO (1) WO2003102845A2 (en)

Cited By (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR2864662A1 (en) * 2003-12-29 2005-07-01 France Telecom Resource e.g. material stock, management system for e.g. enterprise, has prediction unit outputting predicted values of resources modeling functions, and optimization unit managing resources according to predicted values
EP1638046A1 (en) * 2004-09-01 2006-03-22 Microsoft Corporation RFID monitoring schema with AML
JP2006127480A (en) * 2004-09-01 2006-05-18 Microsoft Corp Rule-based filtering and alerting
WO2007106045A1 (en) * 2006-03-14 2007-09-20 St Logistics Pte Ltd A tracking system
US7295116B2 (en) 2004-09-01 2007-11-13 Microsoft Corporation Architecture, programming model and API'S
WO2007139817A2 (en) * 2006-05-24 2007-12-06 Hewlett-Packard Development Company, L. P. Self-referential integrity checking system and method
JP2008504727A (en) * 2004-06-23 2008-02-14 ノキア コーポレイション Method, system, and computer program for enabling inquiry of resource in specific context by defining SIP event package
US7378966B2 (en) 2006-01-04 2008-05-27 Microsoft Corporation RFID device groups
US7382260B2 (en) 2004-09-01 2008-06-03 Microsoft Corporation Hot swap and plug-and-play for RFID devices
US7557707B2 (en) 2004-09-01 2009-07-07 Microsoft Corporation RFID enabled information systems utilizing a business application
US7675418B2 (en) 2006-06-15 2010-03-09 Microsoft Corporation Synchronous command model for RFID-enabling applications
US7701341B2 (en) 2004-09-01 2010-04-20 Microsoft Corporation Device service provider interface
US7756747B2 (en) 2006-03-10 2010-07-13 Microsoft Corporation RFID business process-decoupling of design and deployment time activities
US7868738B2 (en) 2006-06-15 2011-01-11 Microsoft Corporation Device simulator framework for an RFID infrastructure
US7956724B2 (en) 2006-06-15 2011-06-07 Microsoft Corporation Support for reliable end to end messaging of tags in an RFID infrastructure
US8098158B2 (en) 2004-09-01 2012-01-17 Microsoft Corporation RFID server internals design
US8207822B2 (en) 2006-06-15 2012-06-26 Microsoft Corporation Support for batching of events, and shredding of batched events in the RFID infrastructure platform
US8245219B2 (en) 2007-01-25 2012-08-14 Microsoft Corporation Standardized mechanism for firmware upgrades of RFID devices
US9639595B2 (en) 2013-07-12 2017-05-02 OpsVeda, Inc. Operational business intelligence system and method
US9861027B2 (en) 2010-12-08 2018-01-09 Bayer Cropscience, Lp Seed treatment systems and methods
US9877424B2 (en) 2010-12-08 2018-01-30 Bayer Cropscience, Lp Seed treatment facilities, methods and apparatus
US9959511B2 (en) 2010-12-08 2018-05-01 Bayer Cropscience Lp Retail point seed treatment systems and methods
US11213773B2 (en) 2017-03-06 2022-01-04 Cummins Filtration Ip, Inc. Genuine filter recognition with filter monitoring system

Families Citing this family (98)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7586398B2 (en) * 1998-07-23 2009-09-08 Universal Electronics, Inc. System and method for setting up a universal remote control
US7889052B2 (en) 2001-07-10 2011-02-15 Xatra Fund Mx, Llc Authorizing payment subsequent to RF transactions
US8543423B2 (en) * 2002-07-16 2013-09-24 American Express Travel Related Services Company, Inc. Method and apparatus for enrolling with multiple transaction environments
US7725427B2 (en) 2001-05-25 2010-05-25 Fred Bishop Recurrent billing maintenance with radio frequency payment devices
US7360689B2 (en) * 2001-07-10 2008-04-22 American Express Travel Related Services Company, Inc. Method and system for proffering multiple biometrics for use with a FOB
US9024719B1 (en) 2001-07-10 2015-05-05 Xatra Fund Mx, Llc RF transaction system and method for storing user personal data
US20040236699A1 (en) 2001-07-10 2004-11-25 American Express Travel Related Services Company, Inc. Method and system for hand geometry recognition biometrics on a fob
US8001054B1 (en) 2001-07-10 2011-08-16 American Express Travel Related Services Company, Inc. System and method for generating an unpredictable number using a seeded algorithm
US7705732B2 (en) 2001-07-10 2010-04-27 Fred Bishop Authenticating an RF transaction using a transaction counter
US7735725B1 (en) 2001-07-10 2010-06-15 Fred Bishop Processing an RF transaction using a routing number
US9031880B2 (en) 2001-07-10 2015-05-12 Iii Holdings 1, Llc Systems and methods for non-traditional payment using biometric data
US8279042B2 (en) 2001-07-10 2012-10-02 Xatra Fund Mx, Llc Iris scan biometrics on a payment device
US8548927B2 (en) * 2001-07-10 2013-10-01 Xatra Fund Mx, Llc Biometric registration for facilitating an RF transaction
US7503480B2 (en) * 2001-07-10 2009-03-17 American Express Travel Related Services Company, Inc. Method and system for tracking user performance
US7668750B2 (en) 2001-07-10 2010-02-23 David S Bonalle Securing RF transactions using a transactions counter
US9454752B2 (en) * 2001-07-10 2016-09-27 Chartoleaux Kg Limited Liability Company Reload protocol at a transaction processing entity
US7260553B2 (en) * 2002-01-11 2007-08-21 Sap Aktiengesellschaft Context-aware and real-time tracking
US7233958B2 (en) * 2002-02-01 2007-06-19 Sap Aktiengesellschaft Communications in an item tracking system
US7149753B2 (en) * 2002-01-11 2006-12-12 Sap Aktiengesellschaft Providing selective access to tracking information
US20030163364A1 (en) * 2002-02-28 2003-08-28 Piercy Lee W. Net delta change in inventory management
US7725426B2 (en) * 2002-05-29 2010-05-25 Oracle International Corporation Lot/serial engine for a warehouse management system
WO2004021259A1 (en) * 2002-08-30 2004-03-11 Nokia Corporation A method for creating multimedia messages with rfid tag information
US6805287B2 (en) 2002-09-12 2004-10-19 American Express Travel Related Services Company, Inc. System and method for converting a stored value card to a credit card
EP1570417B1 (en) * 2002-11-15 2013-07-24 Sensitech Inc. Apparatus for communicating condition information associated with an item
US7621447B1 (en) * 2003-01-31 2009-11-24 Massachusetts Institute Of Technology Method and apparatus for routing data in an automatic identification system
WO2005024586A2 (en) * 2003-09-05 2005-03-17 Sensitech Inc. Automatic conditioning of data accumulated by sensors monitoring supply chain processes
US20050108324A1 (en) * 2003-10-30 2005-05-19 David Stritzinger Serialized inventory control system and method
WO2005045743A2 (en) * 2003-11-04 2005-05-19 Captech Ventures, Inc. System and method for rfid system integration
JP3644953B1 (en) * 2003-12-12 2005-05-11 秀明 並木 Electronic tag information processing apparatus, POS terminal, and electronic tag information processing program
US7318550B2 (en) * 2004-07-01 2008-01-15 American Express Travel Related Services Company, Inc. Biometric safeguard method for use with a smartcard
JP4501572B2 (en) * 2004-07-20 2010-07-14 富士ゼロックス株式会社 Document management apparatus and document management system
US7778857B2 (en) * 2004-07-20 2010-08-17 Sap Aktiengesellschaft System and method for service parts planning in a multi-echelon network
ZA200506089B (en) * 2004-09-01 2007-04-25 Microsoft Corp Reader application markup language schema
US7614556B2 (en) * 2004-11-05 2009-11-10 Goliath Solutions, Llc Distributed RFID antenna array utilizing circular polarized helical antennas
US20060109125A1 (en) * 2004-11-08 2006-05-25 Goliath Solutions Llc. System for RF detection and location determination of merchandising materials in retail environments
US20070071131A1 (en) * 2004-11-18 2007-03-29 Pyne John W Switched phase receiver for a long range RFID system
US7535337B2 (en) * 2004-11-18 2009-05-19 Goliath Solutions, Llc Systems and methods for monitoring open stock merchandising
US7233241B2 (en) * 2004-11-19 2007-06-19 Goliath Solutions, Llc Low stock alert system
US7205889B2 (en) * 2004-12-08 2007-04-17 Howe Jr Paul E System for monitoring a person's location in a defined area
US20060173728A1 (en) * 2005-01-21 2006-08-03 Lianjun An Adaptive product configuration model
US20060190288A1 (en) * 2005-01-22 2006-08-24 Ims Software Services Ltd. System and method for allocating prescriptions to non-reporting outlets
US8744897B2 (en) * 2005-01-22 2014-06-03 Ims Software Services Ltd. Sample store forecasting process and system
US8078488B2 (en) * 2005-01-25 2011-12-13 Ims Software Services Ltd. System and method for determining trailing data adjustment factors
US7921029B2 (en) * 2005-01-22 2011-04-05 Ims Software Services Ltd. Projection factors for forecasting product demand
US8498891B2 (en) * 2005-01-22 2013-07-30 Ims Software Services Ltd. System and method for product level projections of pharmacy prescriptions within product therapy classes
US7813953B2 (en) * 2005-01-22 2010-10-12 Bank Of America, N.A. System and method for product level projections of pharmacy prescriptions within product therapy classes
US8103539B2 (en) * 2005-01-25 2012-01-24 Ims Software Services Ltd. Sample store forecasting process and system
US7314170B2 (en) * 2005-01-25 2008-01-01 Ims Software Services Ltd. System and method for product imputation relating to sample stores
JP2006235879A (en) * 2005-02-23 2006-09-07 Ricoh Co Ltd Sales planning support system, sales planning support method and sales planning support program
US7389921B2 (en) * 2005-02-28 2008-06-24 Sap Aktiengesellschaft Dynamic component management
US7240834B2 (en) * 2005-03-21 2007-07-10 Mitsubishi Electric Research Laboratories, Inc. Real-time retail marketing system and method
US7570164B2 (en) * 2005-12-30 2009-08-04 Skyetek, Inc. System and method for implementing virtual RFID tags
US7659819B2 (en) * 2005-04-21 2010-02-09 Skyetek, Inc. RFID reader operating system and associated architecture
US20070046467A1 (en) * 2005-08-31 2007-03-01 Sayan Chakraborty System and method for RFID reader to reader communication
US20080001752A1 (en) * 2005-04-21 2008-01-03 Skyetek, Inc. System and method for securing rfid tags
WO2006123920A1 (en) * 2005-05-20 2006-11-23 Lg Electronics Inc. Radio frequency identification data processing system
US20070050305A1 (en) * 2005-08-25 2007-03-01 Elliot Klein RFID system for predictive product purchase date evaluation
US7941448B2 (en) 2005-08-26 2011-05-10 At&T Intellectual Property Ii, Lp System and method for event driven publish-subscribe communications
US20070206786A1 (en) * 2005-08-31 2007-09-06 Skyetek, Inc. Rfid security system
DE202005013842U1 (en) * 2005-09-01 2006-06-01 OCé PRINTING SYSTEMS GMBH Arrangement for detecting storage units
US20070124077A1 (en) * 2005-11-30 2007-05-31 Robert Hedlund An Inventory Stocking and Locating System Utilizing Tags and GPS providing Summarization by Hierarchical Code
US20080042830A1 (en) * 2005-12-30 2008-02-21 Skyetek, Inc. Virtual rfid-based tag sensor
US20080022160A1 (en) * 2005-12-30 2008-01-24 Skyetek, Inc. Malware scanner for rfid tags
US20070206797A1 (en) * 2006-03-01 2007-09-06 Skyetek, Inc. Seamless rfid tag security system
US7679510B2 (en) * 2006-02-06 2010-03-16 Hershey Chocolate And Confectionary Corporation RFID product identification and tracking system
IL174671A0 (en) * 2006-03-30 2006-08-20 Ely Levine A system and case for tracking articles
US7501949B2 (en) * 2006-03-31 2009-03-10 Bea Systems, Inc. RFID bridge for RFID system administration
US7904548B2 (en) * 2006-03-31 2011-03-08 Oracle International Corporation System and method of monitoring an enterprise wide RFID deployment using standards based JMX technology
US20070240068A1 (en) * 2006-03-31 2007-10-11 Bea Systems, Inc. Telemetry viewer for charting RFID events
US20070236351A1 (en) * 2006-03-31 2007-10-11 Bea Systems, Inc. Consolidated RFID alerts
US20070228165A1 (en) * 2006-03-31 2007-10-04 Bea Systems, Inc. Centralized RFID Monitoring
US20080082346A1 (en) * 2006-09-29 2008-04-03 Hoopes John M System and method for automated processing of returns
US20080249994A1 (en) * 2006-11-28 2008-10-09 Calder Group, Inc. System and process for server side stateless data interchange
US8022811B2 (en) * 2007-03-06 2011-09-20 Oki Electric Industry Co., Ltd Wireless tag reader and wireless tag status inference apparatus, system, and program
US9202357B2 (en) * 2007-03-13 2015-12-01 Oracle International Corporation Virtualization and quality of sensor data
US9536215B2 (en) * 2007-03-13 2017-01-03 Oracle International Corporation Real-time and offline location tracking using passive RFID technologies
US7859411B2 (en) * 2007-03-30 2010-12-28 Skyetek, Inc. RFID tagged item trajectory and location estimation system and method
US8042737B2 (en) * 2007-06-05 2011-10-25 Oracle International Corporation RFID key rotation system
US7800499B2 (en) * 2007-06-05 2010-09-21 Oracle International Corporation RFID and sensor signing algorithm
CA2691548A1 (en) * 2007-06-29 2009-01-08 Ims Software Services, Ltd. Systems and methods for projecting sample store activities that are restricted in non-sample stores
US8793705B2 (en) * 2007-08-31 2014-07-29 Red Hat, Inc. Rich internet bus
US9715670B2 (en) 2007-10-12 2017-07-25 Oracle International Corporation Industrial identify encoding and decoding language
US8395508B2 (en) * 2009-09-23 2013-03-12 Wistron Neweb Corporation RFID tag monitoring system
US8280544B2 (en) * 2009-11-02 2012-10-02 Mold Masters (2007) Limited System for use in performance of injection molding operations
US20110106284A1 (en) * 2009-11-02 2011-05-05 Mold-Masters (2007) Limited System for use in performance of injection molding operations
US20110106285A1 (en) * 2009-11-02 2011-05-05 Mold-Masters (2007) Limited System for use in performance of injection molding operations
US20110302264A1 (en) * 2010-06-02 2011-12-08 International Business Machines Corporation Rfid network to support processing of rfid data captured within a network domain
US8145531B1 (en) 2010-07-06 2012-03-27 Target Brands, Inc. Product specific queries to determine presence of bottom-of-basket items
EP2562696A1 (en) * 2011-08-25 2013-02-27 Siemens Aktiengesellschaft Production management for manufacturing execution systems
US9830424B2 (en) 2013-09-18 2017-11-28 Hill-Rom Services, Inc. Bed/room/patient association systems and methods
US9600793B2 (en) * 2013-12-09 2017-03-21 International Business Machines Corporation Active odor cancellation
US10673959B2 (en) * 2015-03-25 2020-06-02 Intel Corporation Accessing service of Internet of Things
SE543243C2 (en) * 2015-10-08 2020-10-27 Stora Enso Oyj System and method for tracking products in open-loop supply or value chain
US10762515B2 (en) * 2015-11-05 2020-09-01 International Business Machines Corporation Product preference and trend analysis for gatherings of individuals at an event
TWI666598B (en) * 2016-12-01 2019-07-21 財團法人資訊工業策進會 Inventory management system and inventory management method
BR112017001012A2 (en) * 2016-12-12 2020-10-27 Sicpa Holding Sa system and method for tracking a product item on a production line
US11911325B2 (en) 2019-02-26 2024-02-27 Hill-Rom Services, Inc. Bed interface for manual location
US11456070B2 (en) * 2020-01-31 2022-09-27 GE Precision Healthcare LLC System and method for identifying healthcare assets

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0913758A2 (en) * 1997-10-31 1999-05-06 Sun Microsystems, Inc. Distributed system and method for controlling access to network resources and event notifications
US6021443A (en) * 1996-01-18 2000-02-01 Sun Microsystems, Inc. Systems, software, and methods for routing events among publishers and subscribers on a computer network
EP1174807A1 (en) * 2000-07-19 2002-01-23 Ford Global Technologies, Inc. Method of providing dynamic production material replenishment information via an internet

Family Cites Families (32)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5166884A (en) 1984-12-24 1992-11-24 Asyst Technologies, Inc. Intelligent system for processing and storing articles
US4974166A (en) 1987-05-18 1990-11-27 Asyst Technologies, Inc. Processing systems with intelligent article tracking
US5662048A (en) 1993-03-08 1997-09-02 Kralj; Nicholas L. Integrated reusable pallet having data collection devices and method for using shipping conveyances
DE4341880A1 (en) 1993-12-08 1995-06-14 Dinkel Doris Objects e.g. clothing item control system
US5950173A (en) * 1996-10-25 1999-09-07 Ipf, Inc. System and method for delivering consumer product related information to consumers within retail environments using internet-based information servers and sales agents
US5469363A (en) 1994-05-19 1995-11-21 Saliga; Thomas V. Electronic tag with source certification capability
US5729697A (en) 1995-04-24 1998-03-17 International Business Machines Corporation Intelligent shopping cart
GB2308947A (en) 1996-01-04 1997-07-09 I D Systems Ltd Identification tag with environmental sensing facility
DE19623893A1 (en) 1996-06-07 1997-12-11 Florian Bischof Transmission process for digitally coded data
US6697702B1 (en) * 1999-03-12 2004-02-24 U.S. Bancorp Shipment transaction system and an arrangement thereof
US6301621B1 (en) 1997-06-19 2001-10-09 International Business Machines Corporation Web server with direct mail capability
US5963134A (en) 1997-07-24 1999-10-05 Checkpoint Systems, Inc. Inventory system using articles with RFID tags
US6038668A (en) 1997-09-08 2000-03-14 Science Applications International Corporation System, method, and medium for retrieving, organizing, and utilizing networked data
JP3465555B2 (en) 1997-10-08 2003-11-10 三菱自動車工業株式会社 Energy absorbing member
US6598783B2 (en) * 1997-10-24 2003-07-29 Tom Brinkman Parcel and object marking and method
US6177860B1 (en) 1997-11-17 2001-01-23 International Business Machines Corporation Method and economical direct connected apparatus for deploying and tracking computers
US6148291A (en) * 1998-01-26 2000-11-14 K & T Of Lorain, Ltd. Container and inventory monitoring methods and systems
US5936527A (en) 1998-02-10 1999-08-10 E-Tag Systems, Inc. Method and apparatus for locating and tracking documents and other objects
DE19844631A1 (en) 1998-09-29 2000-04-06 Gantner Electronic Gmbh Schrun System for monitoring, controlling, tracking and handling objects
US6563417B1 (en) * 1998-10-26 2003-05-13 Identec Solutions Inc. Interrogation, monitoring and data exchange using RFID tags
US6647532B1 (en) 1998-10-29 2003-11-11 Dell Usa L.P. Built-in automatic customer identifier when connecting to a vendor website
AR022299A1 (en) 1999-01-29 2002-09-04 Sensormatic Electronics Corp PRODUCTION AND OPERATION MANAGEMENT USING READING / WRITING RFID LABELS
US6321230B1 (en) 1999-08-11 2001-11-20 I2 Technologies Us, Inc. Binary tree with override nodes for representing a time-varying function in an enterprise model
US6259367B1 (en) 1999-09-28 2001-07-10 Elliot S. Klein Lost and found system and method
DE19955120A1 (en) 1999-11-16 2001-05-23 Meinen Heinz F Product documentation and identification method for transportable objects, by applying data carrier connected to sensors
US6564226B1 (en) * 2000-09-18 2003-05-13 Daimlerchyrsler Corporation Supplier management process with dynamically updated mapping
US6622056B1 (en) * 2000-11-17 2003-09-16 Johan Lindell Method and system for supply chain or supply network control
IL150863A0 (en) 2000-12-07 2003-02-12 Sap Ag System, method, computer program product for communicating data for objects that are transported from first location to second location
US6650225B2 (en) * 2000-12-11 2003-11-18 Asap Automation, Llc Wireless directed inventory system
US6600418B2 (en) * 2000-12-12 2003-07-29 3M Innovative Properties Company Object tracking and management system and method using radio-frequency identification tags
US6557760B2 (en) * 2001-03-30 2003-05-06 Ncr Corporation System and method of managing expired products
US6671698B2 (en) * 2002-03-20 2003-12-30 Deere & Company Method and system for automated tracing of an agricultural product

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6021443A (en) * 1996-01-18 2000-02-01 Sun Microsystems, Inc. Systems, software, and methods for routing events among publishers and subscribers on a computer network
EP0913758A2 (en) * 1997-10-31 1999-05-06 Sun Microsystems, Inc. Distributed system and method for controlling access to network resources and event notifications
EP1174807A1 (en) * 2000-07-19 2002-01-23 Ford Global Technologies, Inc. Method of providing dynamic production material replenishment information via an internet

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
D.L. MARGULIUS: "Dawn of the real-time enterprise" INFOWORLD, 17 January 2002 (2002-01-17), pages 1-2, XP002259980 Internet *
KURT C. HOFFMAN: "Real-time location systems take asset tracking to new level" SUPPLYCHAINBRAIN.COM, October 2001 (2001-10), pages 1-5, XP002259982 *
THE451: "KnowNow unveils 'n-way' EAI over the Internet" SEARCHWEBSERVICES, 28 June 2001 (2001-06-28), pages 1-2, XP002259981 *

Cited By (36)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR2864662A1 (en) * 2003-12-29 2005-07-01 France Telecom Resource e.g. material stock, management system for e.g. enterprise, has prediction unit outputting predicted values of resources modeling functions, and optimization unit managing resources according to predicted values
EP1550974A1 (en) * 2003-12-29 2005-07-06 France Telecom System, method and software for managing resources in a delimited environment
US8903820B2 (en) 2004-06-23 2014-12-02 Nokia Corporation Method, system and computer program to enable querying of resources in a certain context by definition of SIP even package
JP2008504727A (en) * 2004-06-23 2008-02-14 ノキア コーポレイション Method, system, and computer program for enabling inquiry of resource in specific context by defining SIP event package
US7944355B2 (en) 2004-09-01 2011-05-17 Microsoft Corporation Security techniques in the RFID framework
US7701341B2 (en) 2004-09-01 2010-04-20 Microsoft Corporation Device service provider interface
US7204409B2 (en) 2004-09-01 2007-04-17 Microsoft Corporation Reader application markup language schema
US7295116B2 (en) 2004-09-01 2007-11-13 Microsoft Corporation Architecture, programming model and API'S
US8217756B2 (en) 2004-09-01 2012-07-10 Microsoft Corporation Rule-based filtering and alerting
KR101143141B1 (en) 2004-09-01 2012-05-08 마이크로소프트 코포레이션 Rule-based filtering and alerting
US7382260B2 (en) 2004-09-01 2008-06-03 Microsoft Corporation Hot swap and plug-and-play for RFID devices
JP2006127480A (en) * 2004-09-01 2006-05-18 Microsoft Corp Rule-based filtering and alerting
US8098158B2 (en) 2004-09-01 2012-01-17 Microsoft Corporation RFID server internals design
US7533812B2 (en) 2004-09-01 2009-05-19 Microsoft Corporation Reader application markup language schema
US7557707B2 (en) 2004-09-01 2009-07-07 Microsoft Corporation RFID enabled information systems utilizing a business application
EP1638046A1 (en) * 2004-09-01 2006-03-22 Microsoft Corporation RFID monitoring schema with AML
EP1659524A1 (en) * 2004-09-01 2006-05-24 Microsoft Corporation RFID rule engine
US7378966B2 (en) 2006-01-04 2008-05-27 Microsoft Corporation RFID device groups
US7756747B2 (en) 2006-03-10 2010-07-13 Microsoft Corporation RFID business process-decoupling of design and deployment time activities
WO2007106045A1 (en) * 2006-03-14 2007-09-20 St Logistics Pte Ltd A tracking system
US7690559B2 (en) 2006-05-24 2010-04-06 Hewlett-Packard Development Company, L.P. Self-referential integrity checking system and method
WO2007139817A3 (en) * 2006-05-24 2008-06-26 Hewlett Packard Development Co Self-referential integrity checking system and method
WO2007139817A2 (en) * 2006-05-24 2007-12-06 Hewlett-Packard Development Company, L. P. Self-referential integrity checking system and method
US7675418B2 (en) 2006-06-15 2010-03-09 Microsoft Corporation Synchronous command model for RFID-enabling applications
US7956724B2 (en) 2006-06-15 2011-06-07 Microsoft Corporation Support for reliable end to end messaging of tags in an RFID infrastructure
US7868738B2 (en) 2006-06-15 2011-01-11 Microsoft Corporation Device simulator framework for an RFID infrastructure
US8207822B2 (en) 2006-06-15 2012-06-26 Microsoft Corporation Support for batching of events, and shredding of batched events in the RFID infrastructure platform
US8245219B2 (en) 2007-01-25 2012-08-14 Microsoft Corporation Standardized mechanism for firmware upgrades of RFID devices
US9861027B2 (en) 2010-12-08 2018-01-09 Bayer Cropscience, Lp Seed treatment systems and methods
US9877424B2 (en) 2010-12-08 2018-01-30 Bayer Cropscience, Lp Seed treatment facilities, methods and apparatus
US9918425B2 (en) 2010-12-08 2018-03-20 Bayer Cropscience, Lp Seed treatment facilities, methods, and apparatus
US9959511B2 (en) 2010-12-08 2018-05-01 Bayer Cropscience Lp Retail point seed treatment systems and methods
US10212877B2 (en) 2010-12-08 2019-02-26 Bayer Cropscience Lp Seed treatment facilities, methods, and apparatus
US10235644B2 (en) 2010-12-08 2019-03-19 Bayer Cropscience Lp Retail point seed treatment systems and methods
US9639595B2 (en) 2013-07-12 2017-05-02 OpsVeda, Inc. Operational business intelligence system and method
US11213773B2 (en) 2017-03-06 2022-01-04 Cummins Filtration Ip, Inc. Genuine filter recognition with filter monitoring system

Also Published As

Publication number Publication date
US6843415B2 (en) 2005-01-18
AU2003243340A8 (en) 2003-12-19
EP1532560A2 (en) 2005-05-25
AU2003243340A1 (en) 2003-12-19
WO2003102845A3 (en) 2004-02-05
US20030173403A1 (en) 2003-09-18

Similar Documents

Publication Publication Date Title
US6843415B2 (en) Event-based communication in a distributed item tracking system
US6681990B2 (en) Item tracking systems and real-time inventory management
US7222786B2 (en) Inventory early warning agent with correction by error correlation calculation
US7398232B2 (en) Inventory early warning agent in a supply chain management system
AU2006217563B2 (en) Distributed asset management system and method
US7644863B2 (en) Agent using detailed predictive model
US8768777B2 (en) Tracking assets between organizations in a consortium of organizations
US7739121B2 (en) Method and apparatus for providing intelligent and controlled access to supply chain information
US20080215719A1 (en) Data Communication and Coherence in a Distributed Item Tracking System
US20070067773A1 (en) Event management method and system
EP1570384A2 (en) Web service agent
CA2416359A1 (en) Trend detection in an event management system
US20030093307A1 (en) Adaptive networks
US8417854B2 (en) Generic device integration within an auto-id system
US11915187B2 (en) Method and system for tracking inventory including inventory level reconciliation across inventory tracking system
US20080174404A1 (en) Dynamic updates in rfid manager
US20080157930A1 (en) Object name service for RFID tags
KR20150060747A (en) System and method for load distribution in a network
US20060168112A1 (en) Generic integration within an auto-id system
WO2003042793A2 (en) Agent using detailed predictive model
Brückner et al. After-market spare parts inventory centralization at Sandvik Mining and Rock Technology.
CN117473199A (en) Information pushing method and system applied to supply chain logistics system
Uckelmann et al. Limiting Obstacles to Success of RFID and the EPCglobal Network in Logistics
CA2416351A1 (en) Recipient input in an event management system

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NI NO NZ OM PH PL PT RO RU SC SD SE SG SK SL TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 2004509857

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 2003756267

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 2003756267

Country of ref document: EP