HK1148097B - Beverage dispenser - Google Patents

Description

Beverage dispenser

Trade mark

COCA-Is a registered trademark of Coca-Cola corporation, Atlanta, Georgia, USA. Other names, symbols, patterns or logos used herein may be registered trademarks, trademarks or product names of the Coca-Cola company or other companies.

Technical Field

The present invention relates to product dispensers (product dispensers), and more particularly, to systems and methods for dispensing consumable products.

Background

Conventional beverage dispensers may fill the beverage by combining syrup, sweetener, and/or water. To create a limited variety of beverage options, different types of syrups may be provided. This typically results in only a limited number of branded and non-branded beverage choices being offered. By way of example, a single prior art dispenser using several syrups may offer limited options: COCA-COLA^TM、DIETCOCA-COLA^TM、SPRITE^TMAnd several other brands or non-branded beverage choices.

One problem with these types of conventional beverage dispensers is that only a limited number of beverages can be provided. Thus, conventional beverage dispensers may be limited in their ability to provide consumers with the beverage they desire. In this regard, consumers desire a broader menu of beverage selections and the ability to customize their beverages. Studies suggest that they wish to have more drinks even for traditional brands of beveragesThe material changes. For example, COCA-COLA is provided^TMCOCA-COLA containing lime^TM、CHERRYCOCA-COLA^TM、VANILLACOCA-COLA^TMAnd many other types of COCA-COLA^TMThe beverage changes. For a single beverage brand such as COCA-COLA^TMIt is impractical to provide all of the possible variations in conventional beverage dispensers, in part because of the limited capacity and selection capabilities of conventional beverage dispensers. They are unable to offer the consumer a full range of options that they want, i.e., offer all types of branded and non-branded beverages.

Summary of The Invention

Some or all of the above needs and/or problems may be addressed by embodiments of the invention. Certain embodiments of the invention may include systems and methods for dispensing consumable products. One embodiment of the present invention may provide a product dispenser. The product dispenser may include an ingredient matrix (ingredient matrix) operable to hold a plurality of product ingredients. Additionally, the product dispenser may include a controller in communication with the ingredient matrix and operable to execute a set of instructions to receive product data associated with the plurality of product ingredients. Additionally, the controller may include a set of instructions to track usage of the plurality of product ingredients as at least one product is dispensed. Additionally, the controller may further include a set of instructions to update the product data during or after dispensing of the product or installation of one or more product ingredients in the ingredient matrix.

In another embodiment, a method for operating a beverage dispenser may be provided. The method may include receiving product data associated with a plurality of product ingredients. Additionally, the method may include tracking usage of the plurality of product ingredients as at least one product is dispensed. Further, the method may include updating the product data during or after dispensing of the product or installation of one or more product ingredients in the ingredient matrix

In another embodiment, a method for managing a product dispenser may be provided. The method may include receiving product data associated with a plurality of product ingredients installed within an ingredient matrix. Additionally, the method may include tracking usage of the product ingredients of the step as at least one product is dispensed. Further, the method may include estimating when at least one of the product ingredient or the actual ingredient will be depleted. Further, the method may include transmitting an order for any depleted product component over the network.

Another embodiment may provide a system for managing product ingredients. The system may include an ingredient matrix operable to hold a plurality of product ingredients. Additionally, the system can include a controller in communication with the ingredient matrix and operable to execute a set of instructions operable to receive product data associated with a plurality of product ingredients installed within the ingredient matrix. The controller may also include a set of instructions operable to track usage of the plurality of product ingredients when at least one product is dispensed. Additionally, the controller may further include a set of instructions operable to estimate when at least one of the plurality of product ingredients will be depleted. Further, the controller may also include a set of instructions operable to send an order for any depleted product component via the network.

Additional systems, methods, distributors, features and aspects may be realized through the techniques of different embodiments of the present invention. Other embodiments and aspects of the invention are described in detail herein and are considered a part of the claimed invention. Other aspects and features may be understood with reference to the detailed description and the accompanying drawings.

Brief Description of Drawings

The subject matter which is regarded as the invention is particularly pointed out and distinctly claimed in the claims at the conclusion of the specification. The above and other objects, features and aspects of the present invention are apparent from the following detailed description taken in conjunction with the accompanying drawings, in which:

FIG. 1 illustrates an example system including a product dispenser and associated network according to one embodiment of this disclosure.

FIG. 2 illustrates an example of a consumer update network according to one embodiment of the invention.

FIG. 3 illustrates an example of an enhanced view graphical user interface according to an embodiment of the present invention.

FIG. 4 shows an example of a classic view graphical user interface according to an embodiment of the invention.

Fig. 5 shows an example of a method of creating a database of product composition data records (product composition data records) according to an embodiment of the present invention.

FIG. 6 illustrates one example of a method of using a virtual component matrix to track component provisioning and order restock components when virtual components are below a threshold level according to one embodiment of the invention.

FIG. 7 illustrates one example of a method of determining a depletion rate for each component in a component matrix, predicting when each component will be empty based in part on an estimated volume or quantity of each remaining component, and ordering a restocked component when a virtual component is below a threshold level, according to one embodiment of the invention.

FIG. 8 illustrates one example of a method of synchronizing virtual component matrix component volume or quantity levels to match the restored actual component matrix component volume or quantity levels in accordance with one embodiment of the present invention.

FIG. 9 illustrates one example of a method for determining an optimized component matrix using, in part, component depletion rate calculations, in accordance with one embodiment of the present invention.

Fig. 10 illustrates one example of a method of determining a total amount of ingredient volumes and/or amounts remaining in a consumed and/or ingredient package (ingredient package), according to one embodiment of the invention.

Fig. 11 shows an example of a method according to an embodiment of the invention that reads the consumed or remaining volume or quantity from the component packaging (incoming packaging), adjusts this volume or quantity by processing the product composition data record, and passes the data back and/or writes the result back to the component packaging.

FIG. 12 illustrates one example of a method of updating a recipe/prescription database in a product dispenser, according to one embodiment of the invention.

The detailed description explains various embodiments of the invention, together with aspects and features, by way of example with reference to the drawings.

Detailed description of embodiments of the invention

As used herein, the terms "beverage forming dispenser," "product dispenser," "beverage dispenser," "dispenser apparatus," and "dispenser" refer to an apparatus that dispenses a product, such as a beverage, can, bottle, or container.

As used herein, the terms "product" and "beverage," and their plural forms, are used synonymously, and embodiments of the invention should not be limited in scope to the use of any one of the terms.

As used herein, the terms "product data" and "product composition data," and their plural forms, may be used synonymously and refer to data associated with a product or beverage.

As used herein, the terms "virtual ingredient matrix level," "virtual ingredient," and their plural forms, refer to data representing electronics or storage associated with an actual ingredient matrix level or actual ingredient in a product dispenser, such as an ingredient matrix in a beverage dispenser.

Turning now to a more detailed portion of the drawings, an example product dispenser system 100 according to one embodiment of the present invention is shown in FIG. 1. The present example system, such as 100, may operate in a networked computer environment including at least one network in communication with a product dispenser. For example, in fig. 1, a product dispenser 102A is shown in communication with a communication network 104. In this embodiment, at least one product dispenser, such as 102A, may be connected to a consumer, customer, or other user. Other example environments or systems for a product dispenser according to one embodiment of the invention may include non-network configurations.

An example product dispenser, such as 102A shown in fig. 1, may be a client-type device. Each of the product dispensers 102A-N may be a computer or processor-based device capable of communicating with the communication network 104 via signals, such as radio frequency signals or direct wired communication signals.

Each product dispenser, such as 102A, may include a processor or controller 106, an identification reader/scanner device 106A, a composition matrix 108, a computer readable medium, such as Random Access Memory (RAM)110, coupled to the processor or controller 106, and an input/output device, such as a display device 112. A processor or controller, such as 106, may execute computer-executable program instructions stored in a memory, such as 110. The computer-executable program instructions stored in the memory, such as 110, may include any number of modular applications, such as a consumer interaction engine or modules, such as 114. A consumer interaction engine or module, such as 114, may be adapted to implement various methods for consumer-dispenser interaction. Additionally, a consumer interaction engine or module, such as 114, may be adapted to receive one or more signals from one or more consumers, remote and/or local servers or data processing resources, and client type devices or wireless communication devices. Other examples of the functionality and aspects of embodiments of the consumer interaction engine or module, such as 114, are described below.

The identification reader/scanner device 106A shown in fig. 1 may be in communication with the controller 106 and may receive or otherwise obtain identification information from any number of devices or apparatuses associated with a consumer. For example, the identification reader/scanner device such as 106A may include machine-readable code technology such as bar codes, or may include any wireless communication technology such as RFID, reflected light frequency, optical, and the like.

As shown in fig. 1, a processor or controller, such as 106, may communicate with the component matrices, such as 108, to control, monitor and track the addition, flow and removal of some or all of the components to or from the matrices, such as 108. For example, the ingredient matrix may be a series of containers or accessories capable of holding or mounting to respective product ingredient packages or other product ingredient supplies. For example, product component packages such as 116A may be made as liquid pouches held in plastic ridged containers (plastic ridge containers) to allow insertion into a matrix of components such as 108. When inserted into the ingredient matrix such as 108, the bag such as 116A or pouch may be pierced by at least one associated fitment that allows the liquid in the bag such as 116A or pouch to be pumped or otherwise metered by the controller such as 106 or the matrix such as 108 and associated equipment in precise proportions to form the desired product such as a beverage. In one embodiment, one or more product component packages, such as 116A-116Q, may be inserted into a component matrix, such as 108. The component matrix 108 in this embodiment may hold some or all of the product component packages, such as 116A-116Q. In one embodiment, one or more product packages, such as 116O, 116P, 116Q, may be supplied directly rather than in the form of a package. For example, a product package such as 116O may be a continuous supply of soda provided from a soda water source; product packages, such as 116P, may be sweeteners provided from sweetener sources, such as non-nutritive sweeteners (NNS) or High Fructose Corn Syrup (HFCS); and product packs such as 116Q, may be a continuous supply of water from a faucet, purified or distilled water source. In any embodiment, the ingredients, compositions, or product additives may be in the form of a pouch, or may be in other configurations suitable for access to a matrix of ingredients such as 108.

In the embodiment shown in FIG. 1, a product dispenser such as 102A having a matrix of components such as 108 may include one or more machine code readers such as 118A-118Q that utilize machine code technology such as bar codes, RFID, reflected light frequencies, optical, and the like. In one embodiment, at least one machine readable code reader, such as 118A-118Q, may be associated with a location associated with an ingredient matrix, such as 108, wherein some or all of the product ingredient packages, such as 116A-116Q, may be scanned, read, or otherwise identified prior to insertion into or connection with the ingredient matrix, such as 108. In this regard, a processor or controller, such as 106, may receive or obtain information regarding some or all of the product component packages, such as 116A-116Q, and use this information to identify an optimal or other desired location within a component matrix, such as 108, within the component matrix, such as 108, to position the product component package, such as 116A. For example, data from a product component package, such as 116A, may be read, scanned, or identified with a serial number or identification code associated with the product component package, such as 116A. This data may be used alone or in association with information previously stored in at least one database described below, such as 128A-128C, or in association with data otherwise available or stored by a data processing resource or server described below, such as 126, which may identify one or more components associated with a product component package, such as 116A. In another example, data from a product component package, such as 116A, may be a component code or identifier and may be used alone or associated with information previously stored in a database, such as 128A-128C, or with data otherwise available or stored by a data processing resource or server, such as 126, that may identify one or more components associated with the product component package, such as 116A.

In the embodiment shown in FIG. 1, a product dispenser such as 102A having an ingredient matrix such as 108 may include one or more pumps and/or valves such as 120 and 122, respectively, and a nozzle such as 124. In this example, each of the pumps, such as 120, and valves, such as 122, may be controlled by a product dispenser, such as 102A. For example, a processor or controller such as 106 may be in communication with some or all of a pump such as 120 and a valve such as 122. In this regard, some or all of the pumps, such as 120, and/or valves, such as 122, may be selectively operated by a processor or controller, such as 106, to pump, meter, or otherwise obtain respective products or ingredients from certain product ingredient packages, such as 116A-116Q, to dispense a consumable product or beverage.

In one embodiment, an ingredient matrix such as 108 may have a plurality of product ingredient packages such as 116A-116Q inserted into the ingredient matrix such as 108, where each package may contain different or unique ingredients. The varying proportions of ingredients from some or all of the product ingredient packages, such as 116A-116Q, may be selectively combined to form various types of products, such as beverages, by way of one or more commands or instructions from a processor or controller, such as 106, to one or more pumps, such as 120, and/or valves, such as 122, associated with the ingredient matrix, such as 108. Examples of ingredients may include, but are not limited to: seasonings, concentrates, syrups. Sweetener, water, soda, lime, vanilla, CHERRY, and any component part of a branded or non-branded beverage, such as CHERRY COCA-COLA^TM、VANILLA COCA-COLA^TM、COCA-COLA^TM、DIET COCA-COLA^TMAnd FANTA^TM。

In one embodiment, one or more product component packs such as 116A-116Q may contain a component called "pungency" that may restrict its position within a matrix of components such as 108. The spicy type ingredient may be relatively strong such that once the spicy ingredient is pumped or otherwise drawn through a particular portion of the product dispenser, such as 102A, any associated pathway, such as a conduit in the product dispenser, such as 102A, through the dispenser, such as 102A, may be permanently flavored, and any subsequent ingredient or liquid pumped or drawn through that pathway or conduit may be tainted with the flavor of the spicy type ingredient. Thus, once a spicy type component is used in the component matrix such as 108, the associated processor or controller such as 106 may track or otherwise store information to control or limit the replacement and/or addition of other spicy components to certain locations of the component matrix such as 108 to avoid mixing spicy type components or contaminating non-spicy components to maintain product or beverage quality.

In another embodiment, one or more product component packages, such as 116A-116Q, may require shaking to keep the relevant components sufficiently mixed. In this case, the position of the constituent in the constituent matrix such as 108 may be limited to a position within the constituent matrix such as 108, which may be agitated as may be needed and/or desired in a particular implementation.

In another embodiment, ingredients from one or more product ingredient packages, such as 116A-116Q, may be dispensed through an antimicrobial tubing and/or dispenser piece. These ingredients may include, but are not limited to: milk, dairy products, soy sauce, and/or other types and kinds of product components. In such cases, the location of the ingredients in the ingredient matrix such as 108 may be limited to locations within the ingredient matrix such as 108 that utilize appropriate antimicrobial tubing and/or dispenser features as may be needed and/or desired in particular embodiments.

In another embodiment, a one-to-one relationship may be established between a particular product ingredient package, such as 116A, and at least one pump and/or valve, such as 120 and/or 122, respectively. In some cases, utilizing more than one pump and/or valve for a single product component package, such as 116A, a relatively high volume of the component may be drawn from the package, such as 116A, in a relatively short period of time. For example, a product ingredient packet such as 116P containing a sweetener such as a sweetener may utilize more than one pump and/or valve to draw a relatively high volume of the ingredient from the packet such as 116P in a relatively short period of time.

Returning to FIG. 1, any number of other product dispensers, such as 102A-102N, may also be in communication with a network, such as 104. In one embodiment, a communication network such as 104 shown in FIG. 1 may be a Local Area Network (LAN). In another embodiment, the communication network may be a wireless communication network capable of transmitting voice and data signals, including image data signals or multimedia signals. Other networks may include, but are not limited to: the internet, a local area network, a Wide Area Network (WAN), a LON WORKS network, a wired network, a wireless network, or any combination thereof.

A network, such as 104 shown in fig. 1, is also shown in communication with at least one data processing resource, such as a server (e.g., 126), and at least one database, such as 128A. In this embodiment, a server such as 126 may be a processor-based device capable of communicating with some or all of the product dispensers such as 102A-102N via a communication network such as 104 in the form of signals such as radio frequency signals or direct wired communication signals. In addition, data processing resources or servers such as 126 may be used to assist or assist in preparing recipes, methods of products or beverages, provide operational data processing, perform data processing related to consumer interaction, and/or perform other data processing as may be needed and/or desired in a particular embodiment. The operational data processing may include, for example and without limitation, device status, maintenance, service alert, pre-save (predictive restore), and/or other types and kinds or types of operational data processing as may be needed and/or desired in a particular embodiment. Such consumer interaction support may include, for example and without limitation, consumer preferences, consumer product or beverage preferences, loyalty, countermeasures, prizes, media content, customization, and/or other types and kinds of consumer interaction and/or data processing support as may be required and/or desired by a particular implementation.

The server, such as 126 in fig. 1, may include a processor, such as 130, and a computer-readable medium, such as Random Access Memory (RAM)132, coupled to the processor, such as 130. The processor such as 130 may execute computer-executable program instructions stored in the memory such as 132. The computer-executable program instructions stored in the memory, such as 132, may include any number of modular applications, such as a consumer interaction engine or module similar to 114. A consumer interaction engine or module similar to 114 may be adapted to perform different methods for consumer interaction. Additionally, a consumer interaction engine or module similar to 114 may be adapted to interact with one or more consumers and one or more servers or data processing resources. Other examples of functions and aspects of embodiments of a consumer interaction engine or module similar to 114 are described below.

Through a network, such as 104 in fig. 1, some or all of the product dispensers, such as 102A-102N, may retrieve, receive, or otherwise access information stored in some or all of the databases, such as recipes, and methods of making product or beverage databases, such as 128A, operational databases, such as 128B, and consumer databases, such as 128C. In any case, the one or more databases can include product or beverage formation information, such as one or more product or beverage recipes, and methods of product or beverage preparation. Such product or beverage formulations, recipes, and methods of product or beverage preparation may include a list of ingredients, proportions of each ingredient, a list of how a consumer may customize a product or beverage, and/or other types and kinds of product or beverage formulations, recipes, and methods of product or beverage preparation as may be required and desired for a particular embodiment.

In one embodiment, a product dispenser such as 102A may be configured to print coupons (coupon) or other documents. In the illustrated embodiment, an associated printer or other output device, such as 136, may be in communication with a product dispenser, such as 102A. In other embodiments, a printer or other output device may communicate with a product dispenser, such as 102A, via a network, such as 104.

An example environment or system, such as 100 shown in FIG. 1, may facilitate customer, consumer, and user interaction with product dispensers and networks. For example, and not by way of limitation, a user, such as a consumer, may make a product or beverage type selection at a product dispenser, such as 102, via an input/output device, such as display device 112. An associated processor or controller, such as 106, may assist a user in selecting a particular recipe via a display device, such as 112, to form a selected product, such as a beverage. The processor or controller such as 106 may display one or more products or beverages for selection via a display device such as 112. The user may use the display device such as 112 to select at least one of the products or beverages, for example, pressing a button set by the display device such as 112 or a button associated with the display device such as 112. A processor or controller, such as 106, may obtain the respective ingredients and/or proportions of ingredients for forming the selected product or beverage from a local memory, such as 110, or may communicate with at least one database via a network, such as 104, or may communicate with at least one data processing resource, such as server 126, to obtain the respective ingredients and/or proportions of ingredients for forming the selected product or beverage. The processor or controller, such as 106, may utilize the information to operate one or more pumps, such as 120, and/or valves, such as 122, to form and dispense a product or beverage into a cup or other container, such as 136, by way of a nozzle, such as 124.

In another example, a user, such as a customer or package installer, may easily scan or read one or more product component packages, such as 116A-116Q, when the product component packages 116A-116Q are inserted into a component matrix, such as 108, associated with a product dispenser, such as 102A. A processor or controller such as 106 associated with the product dispenser such as 102A may identify an optimal or selected location within the composition matrix such as 108. A user, customer, or package installer can be notified by way of an input/output device, such as a display device, such as 112, where a particular product component package, such as 116A, will be located in a component matrix, such as 108. Examples of display devices may include, but are not limited to: light Emitting Diode (LED) display indicators, LCD screens, input/output (I/O) interfaces, audio interfaces, or other types and kinds of displays or indicators as may be needed and/or desired in a particular embodiment.

In one embodiment, insertion of a particular product component package, such as 116A, into a component matrix, such as 108, may be checked or otherwise verified by scanning the machine-readable code on the corresponding package, such as 116A, and scanning the machine-readable code located on the component matrix, such as 108, at the insertion point (shown as 118A). In this regard, an associated processor or controller, such as 106, may check or verify that a product component package, such as 116A, is properly located within a component matrix, such as 108.

In another embodiment, a cup such as 136 or other container may include identifying information such as an RFID or other machine readable tag such as 138 mounted to the cup shown in FIG. 1. In certain embodiments, the identifying information may be associated with the consumer by way of, for example, an RFID or other machine readable tag like 138, embedded in or otherwise attached to an icon or other object. A reader, such as an RFID or other machine readable code reader, such as 140, associated with the product dispenser, such as 102A, may receive or otherwise obtain identification information from an RFID or other machine readable tag, such as 138. As shown in fig. 1, a processor or controller such as 106 associated with a product dispenser such as 102A may be in communication with an RFID or other machine readable code reader such as 140, and some or all of the identification information obtained from the RFID or other machine readable tag such as 138 may be stored or otherwise processed by the processor or controller such as 106. In this embodiment, the identification information may be embedded in machine-readable codes, bar codes, RFID, radio frequency, infrared or other form of wireless communication method or device, or other types and kinds of encoding and/or storage techniques as may be needed and desired in a particular embodiment. An RFID reader or machine-readable code reader such as 140 may be a corresponding device to read or receive identification information from an RFID or other machine-readable tag such as 138, and may include an RFID read/write device, an infrared device, a magnetic card reader, a bar code reader, or other suitable reader or receiver technology as may be needed and/or desired in a particular embodiment.

In another embodiment, a server or transaction processing resource such as 142 may facilitate payment or payment processing when a consumer selects and attempts to purchase a product such as a beverage at a product dispenser such as 102A. An associated processor or controller such as 106 may receive payment or related information, data transmission or other input from the consumer, for example, by way of a display device such as 112, before, during or after selection of a particular product or beverage. In any case, the processor or controller, such as 106, may transmit payment or related information to a server or transaction processing resource, such as 142, via a network, such as 104. The server or transaction processing resource, such as 142, may access at least one database, such as 128A-128C, or may be in communication with at least one data processing resource, such as 126, to approve or otherwise confirm payment or related information prior to accepting payment by the consumer or prior to otherwise dispensing the selected product or beverage to the consumer.

Referring to FIG. 2, an example of a consumer update environment or system 200 is shown. In one embodiment, one or more networked product dispensers, such as 210, may be mounted at a plurality of respective locations, such as location 202, and may be capable of communicating with one or more servers or data processing resources, such as 206, and one or more data storage devices, such as databases, such as 208, via a network 204, such as the internet or a global network. For example, the product dispenser 210 may be similar to the product dispenser or dispenser device 102A described in fig. 1. In one example, a product dispenser such as 210 may include some or all of the following components described with respect to FIG. 1: a component matrix such as 108 having locations operable to receive one or more product component packages such as 116A-116Q, a controller such as 106, one or more package insertion detection devices or RFID readers/writers such as 118A-118Q, a pump such as 120, a valve such as 122, and a nozzle such as 124. For example, the server or data processing resource 206 may be similar to the server or data processing resource 126 described in fig. 1.

In one embodiment, one or more consumers, such as 212, may access a network, such as 104, or a consumer update network, such as 204. Through network 204, consumers such as 212 may register to configure consumer preferences, accessAsking the corresponding account, receiving promotional offers, managing legitimate accounts, and/or registering for other types and kinds of opportunities and services that may be needed or desired in a particular embodiment. In another embodiment, a consumer such as 212 may choose to access the network 104 or update the network system such as 200, and one or more networked product dispensers such as 210, by way of any number of client-type devices, including but not limited to: personal Computers (PCs) such as 214A, data processing devices such as 214B, wireless communication devices such as 214C, and/or by way of other types and kinds of data processing, processor or client type devices. Examples of wireless communication devices may include, but are not limited to: wireless data processing device, wireless telephone, mobile telephone, IPHONE^TM、IPOD^TMPersonal data assistant and/or POCKET PC^TM。

Referring to FIG. 3, one example of an enhanced view graphical user interface 300 is shown. In one embodiment shown, a product dispenser, such as 210 in FIG. 2, may include at least one user interface, such as an enhanced view graphical user interface, such as 300, or a consumer interface. The user interface such as 300 may be used, for example, by a consumer such as 212 to select any number of different product or beverage types, categories, and recipes. In use, a product dispenser such as 210 having an enhanced view graphical user interface such as 300 may provide a consumer with a series of dynamically generated menus of selectable product or beverage options, wherein the consumer may locate and select a particular brand, category, type and/or scheme of the respective product or beverage desired. Once a particular product or beverage option is selected, the consumer may cause the corresponding product or beverage to be formulated and dispensed by the product dispenser.

Referring to FIG. 4, an example of another user interface is shown. In one embodiment, a product dispenser, such as 210 in FIG. 2, may include a classic-view graphical user interface, such as 400. A user interface, such as 400, may be used by a consumer, such as 212, to select from a limited number of different product or beverage types, categories, and/or options. In use, a consumer such as 212 may more easily select a product or beverage from a limited number of product or beverage choices. Once a particular product or beverage option is selected, the consumer may cause the corresponding product or beverage to be formulated and dispensed by the product dispenser. In some embodiments, a classic type of graphical user interface may also be referred to as a traditional view because it is generally similar to a traditional sprinkler dispensing valve design. Thus, a classic type graphical user interface may be referred to as a traditional view graphical user interface.

In one embodiment, the consumer may desire fewer product or beverage selections than are displayed by a product dispenser that allows, for example, selection of a plurality of different types of products or beverages. In this case, a classic-view graphical user interface may be displayed with relatively fewer, more traditional product or beverage selections and including one or more traditional types of product or beverage selections to facilitate the consumer to interact with the product dispenser more quickly at certain times.

In another embodiment, the consumer may choose to create one or more consumer preferences that may modify the type and/or variety of brands and/or product or beverage options displayed in a user interface, such as a classic view graphical user interface, in effect creating a consumer customized classic view graphical user interface. In this particular embodiment, the consumer may create a classic view graphical user interface that is customized by the consumer. For example, when a consumer identifies himself or herself to a product dispenser such as 210, one or more consumer preferences may be retrieved by the dispenser 210. Based at least in part on one or more consumer preferences, product dispenser 210 may display a default user interface to the consumer, which may be an enhanced view graphical user interface, a classic view graphical user interface, or a classic view graphical user interface customized by the consumer.

Fig. 5-12 are examples of flow diagrams of various methods according to embodiments of the invention. Some or all of the illustrated methods may be implemented by a system, network, product dispenser, or any combination associated with those illustrated in fig. 1-4.

Referring to FIG. 5, one example of a method 500 of building a database of product composition data records is shown. The method 500 begins in block 502. In block 502, input is received from a consumer to dispense a product. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may allow the consumer to select and dispense a selected product. For example, a consumer may enter or select a product via a user interface associated with the product dispenser, such as user interface 112. A processor or controller such as 106 associated with the product dispenser such as 102A may allow the consumer to dispense a selected product.

Block 502 is followed by block 504 in which a product composition data record is established. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may create or otherwise generate a product composition data record or other file for storing and subsequently retrieving product information. The controller, such as 106, may store the product composition data records or other files in an associated memory or data storage device, such as 110. Product composition data records or files may include, but are not limited to: the type and/or type of product selected, the volume or amount of each ingredient dispensed when the product is formed, the date and time the product was dispensed, any associated consumer data, any associated dispenser data, and/or other types and/or types of data. In one embodiment, a local and/or remote server or data processing resource, such as 126, may create or otherwise generate and store product composition data records or other files in an associated memory or data storage device, such as 110 or 128A-128C. In any case, a product composition data record is established.

In one embodiment, the product dispenser builds a product composition data record based at least in part on the type and/or type of product selected, the volume or amount of each component dispensed when the product is formed, the date and time the product was dispensed, any relevant consumer data, any relevant dispenser data, and/or other types and/or types of data, as may be needed and/or desired in a particular embodiment.

Block 504 is followed by block 506, wherein the product composition data records may optionally be combined with other types and/or kinds of data records. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may optionally combine other types of data and information with the product composition data record or other file for storage and subsequent retrieval of product information. The controller, such as 106, may store other types of data and information and product composition data records or other files in an associated memory or data storage device, such as 110. The controller, such as 106, may communicate the file to a local and/or remote server or data processing resource, such as 126, for storage and retrieval. In one embodiment, local and/or remote servers or data processing resources such as 126 may store other types of data and information in product component data records or other files in associated memory or data storage devices such as 110 or 128A-128C. In any case, the product composition data records may optionally be combined with other types and/or kinds of data records.

Block 506 is followed by block 508, wherein the product composition data record is data transmitted locally and/or remotely to a data processing resource. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may transmit the file to a local and/or remote server or data processing resource, such as 126, for storage and retrieval.

Block 508 is followed by block 510, wherein the product composition data records are stored in a database at the data processing resource. In this embodiment, the local and/or remote servers or data processing resources such as 126 may store other types of data and information in product composition data records or other files in associated memory or data storage devices such as 110 or 128A-128C for subsequent retrieval.

The method 500 ends after block 510.

In one embodiment, the product makeup data record is generated each time a consumer selects and/or dispenses a product from the product dispenser. This product composition data record may include, but is not limited to: the type and/or type of product selected, the volume or amount of each ingredient dispensed in forming the product, the date and time the product was dispensed, any associated consumer data, any associated dispenser data, and/or other types and types of data as may be needed and/or desired. These product composition data records are data communicated between the product dispenser and local and/or remote data processing resources. The product makeup data records may be stored in a database and used for analysis of product dispenser operation, for restocking, other supply chain applications, and/or for other aspects, as may be needed and/or desired in particular embodiments.

Referring to fig. 6, one example of a method 600 for using a virtual component matrix to track component provisioning and order restock components when the virtual component is below a threshold is shown. The method 600 begins in block 602. In block 602, one or more product composition data records are queried from a database. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with a product dispenser, such as 102A, may query one or more product makeup data records or other files from a memory, database, or data storage device, such as 110 or 128A-128C. The controller, such as 106, may retrieve some or all of the product make-up data records or other files from a memory, database, or data storage device, such as 110 or 128A-128C. In one embodiment, a local and/or remote server or data processing resource such as 126 may query one or more product composition data records or other files from a memory, database, or data storage device such as 110 or 128A-128C. In any case, one or more product composition data records may be queried from the database.

Block 602 is followed by block 604, wherein the product composition data records are used to deplete volumes or amounts from similar virtual components. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with a product dispenser, such as 102A, may deplete or otherwise reduce the volume and/or quantity from similar or identical virtual components based at least in part on some or all of the product makeup data records. The controller, such as 106, may construct a data record using some or all of the products and adjust volumes and/or quantities from similar or identical virtual components and track changes in volumes and/or quantities of similar or identical virtual components. For example, if one or more queried product makeup data records indicate that one ounce of cherry flavor is dispensed, then one ounce of cherry flavor may be subtracted from the volume of cherry flavor currently associated with the virtual cherry flavor component. In this regard, the product composition data record may be used to adjust some or all of the virtual ingredient matrix ingredient levels such that by processing the product composition data record, the virtual ingredient volume and quantity levels match the actual ingredient volume and quantity levels. The "virtual component matrix level", "virtual components", and virtual type data may represent data associated with an actual component matrix in a product dispenser, such as component matrix 108. This data may be stored in a memory, database, or data storage device, such as 110 or 128A-128C, and may also be stored in a processor or controller, such as 106, or a local and/or remote server or data processing resource, such as 126. In one embodiment, local and/or remote servers or data processing resources such as 126 may be depleted or otherwise reduced in volume and/or quantity from similar or identical virtual components that make up a data record based at least in part on some or all of the products. In any case, the product composition data record may be used to deplete volumes or quantities from similar virtual ingredients.

Block 604 is followed by block 606 in which a determination is made as to the remaining volume or number of each virtual component in the virtual component matrix. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may determine the remaining volume or amount of each virtual component in the virtual component matrix. A controller such as 106 may construct a data record using some or all of the products and determine the remaining volume or amount of each virtual component in the virtual component matrix. In one embodiment, a local and/or remote server or data processing resource such as 126 may determine the remaining volume or amount of each virtual component in a matrix of virtual components that make up the data record based at least in part on some or all of the products. In any case, a determination may be made as to the remaining volume or number of each virtual component in the virtual component matrix.

Block 606 is followed by block 608 in which a determination is made as to whether any virtual components need to be restored. If the determination is positive, i.e., the score needs to be restored, the method continues to block 610. If the determination is negative, i.e., the score does not need to be stored again, the method 600 ends. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may determine whether any virtual ingredients need to be restored. A controller such as 106 may use some or all of the product composition data records to determine if any virtual components need to be restored. For example, if the determination indicates that the composition is below a predetermined level, the composition needs to be re-stored. In one embodiment, a local and/or remote server or data processing resource such as 126 may determine whether any virtual components need to be restored based at least in part on some or all of the product composition data records. In any case, a determination may be made as to whether any virtual components need to be restored.

In block 610, an order is placed for components that have been depleted below a predetermined level. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with a product dispenser, such as 102A, may place an order for ingredients that have been depleted below a predetermined level. A controller such as 106 may generate and transmit or otherwise assist in placing an order, for example, with a third party, to obtain one or more components that have been depleted below a predetermined level. For example, the order may enable the actual restocked components to be shipped to the product dispenser location such that the restocked components will be available nearby to restock the product dispenser when the components are empty. In one embodiment, a local and/or remote server or data processing resource such as 126 may generate and transmit or otherwise assist in placing an order, for example, with a third party, to obtain one or more components that have depleted below a predetermined level. In any case, an order may be placed for ingredients that have been depleted below a predetermined level.

The method 600 ends after block 610.

In one embodiment, the virtual component matrix may be saved at the data processing resource. The virtual component matrix may represent an actual component matrix in the product dispenser. In operation, the virtual component matrix may track the types and/or kinds of components in the actual component matrix. In addition, the virtual component matrix may track the volume and/or number of each component in the actual component matrix. In operation, the supply of ingredients may be depleted from the virtual ingredient matrix when the data processing resource receives a product makeup data record indicating the type and/or kind of product and the volume and/or quantity of each ingredient that is dispensed. In this regard, when the volume and/or quantity of the virtual ingredient is depleted to a predetermined level, a restock order is triggered such that the restock ingredient is actually sent to the product dispenser location before the ingredient is depleted. Thus, when it is time to restock depleted ingredients in the ingredient matrix, the product dispenser will have an immediate restock supply of ingredients.

Referring to FIG. 7, one example of a method of inventory management is shown.

The method 700 begins in block 702. In block 702, one or more product composition data records are queried from a database. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with a product dispenser, such as 102A, may query one or more product makeup data records or other files from a memory, database, or data storage device, such as 110 or 128A-128C. The controller, such as 106, may retrieve some or all of the product make-up data records or other files from a memory, database, or data storage device, such as 110 or 128A-128C. In one embodiment, a local and/or remote server or data processing resource, such as 126, may query one or more product composition data records or other files from a memory, database, or data storage device, such as 110 or 128A-128C. In any case, one or more product composition records may be queried from the database.

Block 702 is followed by block 704, wherein a depletion rate for each component in the component matrix is determined. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may determine the consumption rate of some or all of the ingredients in the ingredient matrix. A controller, such as 106, may use some or all of the product composition data records to determine the depletion rate of some or all of the ingredients in the ingredient matrix. For example, the rate of depletion of an ingredient is related to how quickly the ingredient is depleted. When used in one or more calculations with available ingredient supplies, an expected date on which the ingredient will be estimated to be depleted may be determined, which may also be referred to as an ingredient supply end date. In one embodiment, a local and/or remote server or data processing resource such as 126 may determine the depletion rate of some or all of the ingredients in the ingredient matrix based at least in part on some or all of the product makeup data records. In any case, the depletion rate of each constituent in the constituent matrix may be determined.

Block 704 is followed by block 706, wherein the computation of the end of supply of the constituent is based in part on the estimated volume or quantity currently available nearby and the determined depletion rate of the constituent. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may determine the end of the supply of the ingredient based at least in part on the estimated volume or quantity currently available nearby and the determined depletion rate of the ingredient. The controller, such as 106, may use some or all of the product composition data records to determine the end of ingredient supply. In one embodiment, a local and/or remote server or data processing resource such as 126 may determine the end of ingredient supply based at least in part on some or all of a product slate data record that includes an estimated volume or quantity currently available nearby and a determined depletion rate for the ingredient. In any case, the end of the ingredient supply is calculated based in part on the estimated volume or quantity currently available nearby and the determined depletion rate for the ingredient.

Block 706 is followed by block 708 in which it is determined which virtual components need to be restored. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may determine whether some or all of the virtual ingredients need to be restored. The controller, such as 106, may use some or all of the product composition data records to determine whether some or all of the virtual components need to be restored. For example, the predetermined level or threshold may be used as a guide to determine how long to supply, how many ingredients should be available nearby, and/or may be used to assist in determining which ingredients need to be restocked. In one embodiment, the local and/or remote server or data processing resource, such as 126, may determine whether some or all of the virtual components need to be restocked based at least in part on some or all of the product makeup data records that include predetermined levels or thresholds, which may be used to determine how long they can be served, how many components should be available in the near future, and/or other factors that may be used to assist in determining which components need to be restocked. In any case, it may be determined whether some or all of the virtual components need to be restored.

Block 708 is followed by block 710 in which it is determined whether any components need to be restored. If the determination is positive, i.e., certain components need to be restored, the method continues to block 712. If the determination is negative, i.e., the score does not need to be stored again, the method ends. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may determine whether some or all of the ingredients need to be restocked. The controller, such as 106, may use some or all of the product composition data records to determine whether some or all of the ingredients need to be restocked. In one embodiment, a local and/or remote server or data processing resource such as 126 may determine whether some or all of the ingredients need to be restocked based at least in part on some or all of the product makeup data records that include predetermined levels or thresholds, which may be used to determine how long it can be served, how many ingredients should be available in the near future, and/or other factors that may be used to assist in determining which ingredients need to be restocked. In any case, it may be determined whether some or all of the components need to be restored.

In block 712, an order is placed to restock components associated with the depleted virtual component. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with a product dispenser, such as 102A, may place an order to restock components associated with depleted virtual components or components associated with components that have otherwise been identified as needing to be restocked. A controller, such as 106, may generate and transmit or otherwise facilitate placing an order, for example, with a third party, to obtain one or more components that have been depleted below a predetermined level. For example, the order may enable actual restocking components to be shipped to the product dispenser location such that the restocking components may be available nearby to restock the product dispenser when the components are empty. In one embodiment, a local and/or remote server or data processing resource such as 126 may generate and transmit or otherwise facilitate placing an order, for example, with a third party, to restore components associated with depleted virtual components or components associated with components that have otherwise been identified as needing to be restored. In any case, an order may be placed to restock components associated with the depleted virtual component.

The method 700 ends after block 712.

In one embodiment, the product composition data record is used to calculate the depletion rate for each ingredient in the ingredient matrix. The depletion rate can then be used in conjunction with a virtual component matrix that tracks the volume or amount of each remaining component to predict when the component will be empty and need to be restocked. This information can then be used to trigger an ingredient restock order when certain conditions are met, so that the restocked ingredient is shipped to the product dispenser to be available near the time the ingredient is empty.

Referring to FIG. 8, one example of a method 800 of synchronizing virtual component matrix component volume or quantity levels to match re-stored actual component matrix component volume or quantity levels is illustrated. The method begins in block 802. In block 802, one or more component packages are received within a component matrix located within a product dispenser. In the illustrated embodiment, one or more ingredient packages, such as 116A-116Q in FIG. 1, may be inserted by a person into an ingredient matrix, such as 108, associated with the product dispenser. A processor or controller, such as 106 in fig. 1, associated with the product dispenser, such as 102A, may detect the insertion of one or more component packages, such as 116A-116Q, as they are inserted.

Block 802 is followed by block 804 in which a component data record is established. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with a product dispenser, such as 102A, may create or otherwise generate a composition data record or other file for storage and retrieval of subsequent product information. The controller, such as 106, may store product composition data records or other files in an associated memory or data storage device, such as 110. The component data records or files may include, but are not limited to: the component package inserts data, component type and/or class, volume or quantity remaining in the package, and/or other types and/or classes of data. In one embodiment, local and/or remote servers or data processing resources such as 126 may create or otherwise generate and store component data records or other files in associated memory or data storage devices such as 110 or 128A-128C. In any case, a component data record may be established.

Block 804 is followed by block 806, wherein the component data records may optionally be combined with other types and/or categories of data records. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may optionally combine other types of data and information with the ingredient data records or other files for storage and subsequent retrieval of product information. The controller, such as 106, may store other types of data and information with the component data records or other files in an associated memory or data storage device, such as 110. The controller, such as 106, may transmit the file to a local and/or remote server or data processing resource, such as 126, for storage and retrieval. In one embodiment, the local and/or remote servers or data processing resources such as 126 may store other types of data and information in associated memory or data storage devices such as 110 or 128A-128C, or in combination with component data records or other files in associated memory or data storage devices such as 110 or 128A-128C. In any case, the component data records may optionally be combined with other types and/or kinds of data records.

Block 806 is followed by block 808, wherein the component data records may be transmitted to a data processing resource. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may transmit the file to a local and/or remote server or data processing resource, such as 126, for storage and retrieval.

Block 808 is followed by block 810 in which the virtual component matrix is updated to indicate that components are inserted into the actual component matrix, and the virtual component matrix volume or quantity level is adjusted to match the actual component volume or quantity level. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may update the virtual ingredient matrix to indicate that a particular ingredient is inserted into the actual ingredient matrix, and if desired, also adjust the virtual ingredient matrix volume or quantity level to match the actual ingredient volume or quantity level. Controllers such as 106 may utilize some or all of the constituent data records to facilitate updating and adjustment. For example, the actual component level may be synchronized with the virtual component level. In one embodiment, a local and/or remote server or data processing resource such as 126 may update the virtual component matrix to indicate that a particular component is inserted into the actual component matrix, and if desired, also adjust the virtual component matrix volume or quantity level to match the actual component volume or quantity level based at least in part on some or all of the component data records. In any case, the virtual component matrix may be updated to indicate that components are inserted into the actual component matrix, and the virtual component matrix volume or quantity level may be adjusted to match the actual component volume or quantity level.

The method 800 ends after block 810.

In one embodiment, when the composition matrix associated with the product dispenser changes as the composition is restored, the composition data record may be transmitted to the data processing resource to synchronize some or all of the actual composition volumes or amounts with some or all of the virtual composition volumes or amounts resident in the data processing resource. To achieve this synchronization, ingredient data records may be generated at the product dispenser. As may be needed and/or desired in particular embodiments, the component data records may include, but are not limited to: the component package inserts data, component type and/or class, volume or quantity remaining in the package, and/or other types and/or classes of data.

Referring to FIG. 9, one example of a method 900 for determining an optimized component matrix utilizing, in part, the component velocities of depletion calculations is shown. The method 900 begins in block 902. In block 902, the query product constitutes a data record. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with a product dispenser, such as 102A, may query one or more product makeup data records or other files from a memory, database, or data storage device, such as 110 or 128A-128C. The controller, such as 106, may retrieve some or all of the product make-up data records or other files from a memory, database, or data storage device, such as 110 or 128A-128C. In one embodiment, a local and/or remote server or data processing resource, such as 126, may query one or more product composition data records or other files from a memory, database, or data storage device, such as 110 or 128A-128C. In any case, one or more product composition data records may be queried from the database.

Block 902 is followed by block 904, wherein an optimized component matrix is determined by analyzing the rate at which each component is consumed. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may determine an optimized ingredient matrix by analyzing the rate at which each ingredient is consumed. A controller such as 106 may use some or all of the product composition data records to determine an optimized composition matrix by analyzing the rate at which each composition is consumed. For example, the rate at which each constituent is consumed may be referred to as the depletion rate of the constituent. The higher the depletion rate of a particular ingredient, the faster the ingredient is consumed, and the more often the ingredient may need to be restocked. Thus, optimizing the composition matrix may include determining which of some or all of the compositions in the composition matrix should have more than one slot based at least in part on the rate of depletion, which may effectively increase the supply volume or quantity of a particular composition. In one embodiment, a local and/or remote server or data processing resource such as 126 may determine an optimized component matrix based at least in part on some or all of the product makeup data records, including analyzing the rate at which each component is consumed. In any case, the optimized composition matrix may be determined by analyzing the rate at which each product is consumed.

Block 906 is followed by block 908 in which the component assignments in the current virtual component matrix are compared to the optimized component matrix that has been previously determined. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may compare the constituent assignments in the current virtual constituent matrix to any previously determined optimized constituent matrix. The controller, such as 106, may utilize some or all of the product composition data records to compare the ingredient assignments in the current virtual ingredient matrix to any previously determined optimized ingredient matrix. For example, based at least in part on one or more product composition data records, a rate of ingredient depletion can be determined, and in turn an optimized ingredient matrix can be determined. The optimized component matrix may include, but is not limited to: what each component in the list of components and the actual matrix of components should be. Comparison of the determined optimized component matrix with the current actual component matrix may yield a difference, which may facilitate further optimization. In one embodiment, a local and/or remote server or data processing resource such as 126 may compare the component allocations in the current virtual component matrix to any previously determined optimized component matrices. In any case, the component assignments in the current virtual component matrix may be compared to any previously determined optimized component matrix.

Block 908 is followed by decision block 910 in which a determination is made as to whether there is any difference between the determined optimized component matrix and the current actual component matrix. If the determination is positive, i.e., there is a difference, the method 900 continues to block 912. If the determination is negative, i.e., there is no difference, the method 900 ends. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may determine whether there is any difference between the determined optimized component matrix and the current actual component matrix. The controller, such as 106, may utilize some or all of the product composition data records to determine if there is any difference between the determined optimized composition matrix and the current actual composition matrix. For example, a comparison may be made between the determined optimized component matrix and the components in the current actual component matrix. In one embodiment, a local and/or remote server or data processing resource, such as 126, may determine whether there is any difference between the determined optimized component matrix and the current actual component matrix based at least in part on some or all of the pre-product data records. In any case, it may be determined whether there is any difference between the determined optimized component matrix and the current actual component matrix.

In block 912, the servicer may be prompted that the composition matrix is not optimized. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may communicate an indication or communication to a service person, such as a service technician or other person, that the compositional matrix is not optimized. For example, a processor or controller, such as 106, may communicate information or communications via a user interface, such as 112. Alternatively, a processor or controller such as 106 may communicate with a local and/or remote server or data processing resource such as 126 and transmit or otherwise communicate information to a service person such as a service technician or other personnel via a network such as 104 to one or more wireless communication devices associated with the service person, service technician or other personnel. In any case, a service person, such as a service technician, may be prompted that the component matrix is not optimized.

Block 912 is followed by decision block 914, wherein a determination is made as to whether the service person wishes to optimize the current actual composition matrix. If the determination is positive, i.e., the maintenance personnel wish to optimize the actual composition matrix, the method 900 continues to block 916. If the determination is negative, i.e., the maintenance personnel do not wish to optimize the actual composition matrix, the method 900 ends. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may receive an indication or other input from a service person, service technician, or other person whether the service person, service technician, or other person wishes to optimize the current actual composition matrix. For example, a processor or controller such as 106 may receive input, selections, information or communications from a service person, service technician or other personnel via a user interface such as 112. Alternatively, the processor or controller, such as 106, may receive input, selection, information or communications from a service person, service technician or other person via a local and/or remote server or data processing resource, such as 126, that is transmitted or otherwise communicated by the service technician or other person via a network, such as 104, from one or more wireless communication devices associated with the service person, service technician or other person. In any event, a determination may be made as to whether the service technician wishes to optimize the current actual composition matrix.

In block 916, the optimized component matrix is output. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may output or otherwise display the optimized compositional matrix. For example, the controller such as 106 may output or otherwise display the optimized component matrix via a user interface associated with the product dispenser, such as user interface 112.

Block 916 is followed by block 918, wherein input is received from a service person to move/add/subtract components to or from the actual component matrix to optimize product dispenser operation. In the illustrated embodiment, a processor or controller, such as 106 in fig. 1, associated with the product dispenser, such as 102A, may receive an indication or other input from a service person, service technician, or other person regarding any constituent change, such as moving a constituent to and/or from an actual constituent matrix, adding a constituent, or subtracting a constituent, to optimize product dispenser operation. In any case, the actual component matrix may be synchronized with the determined virtual component matrix. For example, a processor or controller such as 106 may receive input, selections, information, or communications from a service person, service technician, or other personnel via a user interface such as 112.

Block 918 is followed by block 920 where the component data records are transmitted to a data processing resource to inform about the changes in the actual component matrix component assignments that have been generated. In the illustrated embodiment, a processor or controller, such as 106 in fig. 1, associated with the product dispenser, such as 102A, may transmit component data records, including any changes in the physical component matrix component assignments, to a local and/or remote server or data processing resource, such as 126, for storage and retrieval. Additionally, changes may include acknowledgements and updates.

Block 920 is followed by block 922, where any missing components are ordered. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may place an order for any missing ingredients. As may be needed and/or desired in particular embodiments, the controller, such as 106, may generate and transmit or otherwise facilitate placing an order, for example, with a third party, to obtain one or more ingredients determined to be missing, and may order any ingredients that are not immediately available to a service person, such as a service technician, for delivery to the product dispenser location. For example, the order may enable the actual component to be shipped to the product dispenser location such that when the component is empty, the replacement component may be available nearby to stock the product dispenser. In one embodiment, a local and/or remote server or data processing resource such as 126 may generate and transmit or otherwise facilitate placing an order, for example, with a third party to obtain any missing components or components that have otherwise been identified as missing. In any case, any missing components may be ordered.

The method 900 ends after block 922.

In one embodiment, one or more product slate data records can be used to determine the rate of ingredient depletion. For example, the rate at which the constituent is depleted may be characteristic of the rate at which the constituent is consumed. Some or all of this information may be used to optimize the composition matrix. For example, if the depletion rate of cherry flavor is sufficiently high, the optimized ingredient matrix may indicate that two matrix slots in place of one matrix slot should be dedicated to cherry flavor to avoid or otherwise minimize ingredient supply interruptions or to minimize the frequency with which cherry flavor needs to be restocked.

Referring to fig. 10, one example of a method 1000 of determining a total amount of components and/or quantities consumed and/or a remaining amount in a component package is shown. The method 1000 begins in block 1002, and in block 1002, input is received from a consumer to dispense a product. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may allow the consumer to select and dispense a selected product. For example, a consumer may enter or select a product via a user interface associated with the product dispenser, such as user interface 112 in FIG. 1. A processor or controller such as 106 associated with the product dispenser such as 102A may allow the consumer to dispense a selected product.

Block 1002 is followed by block 1004, wherein a product composition data record may be created. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with a product dispenser, such as 102A, may create or otherwise generate a product composition data record or other file for storage and subsequent retrieval of product information. The controller, such as 106, may store product composition data records or other files in an associated memory or data storage device, such as 110. Product composition data records or other files may include, but are not limited to: the type and/or kind of product selected or ingredient dispensed, the volume or quantity of each ingredient dispensed when the product is formed, the date and time the product was dispensed, any associated consumer data, any associated dispenser data, and/or other types and/or kinds of data. In one embodiment, a local and/or remote server or data processing resource, such as 126, may create or otherwise generate and store product composition data records or other files in an associated memory or data storage device, such as 110 or 128A-128C. In any case, a product composition data record may be established.

Block 1004 is followed by block 1006 wherein the virtual ingredient matrix ingredient supply is depleted by volume and/or quantity as reflected in the product makeup data record. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with a product dispenser, such as 102A, may deplete or otherwise reduce volume and/or quantity from similar or identical virtual ingredients based at least in part on some or all of the product composition data records. The controller, such as 106, may utilize some or all of the product composition data records and adjust volumes and/or quantities from similar or identical virtual components and track changes in volumes and/or quantities of similar or identical virtual components. For example, if one or more queried product composition data records indicate that one ounce of cherry flavor is dispensed, the one ounce of cherry flavor may be subtracted from the volume of cherry flavor currently associated with the virtual cherry flavor component. In this regard, the product composition data record may be used to adjust some or all of the virtual component matrix component levels such that the virtual component volume and quantity levels match the actual component volume and quantity levels by processing the product composition data record. Such data may be stored in a memory, database, or data storage device, such as 110 or 128A-128C, and may also be stored in a processor or controller, such as 106, or a local and/or remote server or data processing resource, such as 126. In one embodiment, a local and/or remote server or data processing resource such as 126 may be depleted or otherwise reduced in volume and/or quantity from similar or identical virtual components based at least in part on some or all of the product makeup data records. In any case, the virtual ingredient matrix ingredient supply may be depleted by volume and/or quantity as reflected in the product composition data record.

Block 1006 is followed by block 1008 in which the percentage of the volume and/or quantity of components consumed and/or remaining is determined. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may determine the percentage of the volume and/or quantity of ingredients consumed and/or remaining. The controller, such as 106, may utilize some or all of the product makeup data records to determine the percentage of the volume and/or quantity of ingredients consumed and/or remaining. For example, the determination may be based at least in part on a previous virtual ingredient volume or amount that is less than the total amount of ingredients dispensed, as indicated by the product composition data record. The determination may be extended to some or all of the components in the virtual component matrix such that the volume and amount consumed or remaining is known to some or all of the virtual component matrix. Since the virtual component matrix can be synchronized with the actual component matrix, the volume and number of virtual components are about the same as the volume and number of actual components. In one embodiment, a local and/or remote server or data processing resource, such as 126, may determine the percentage of the component volume and/or amount consumed and/or remaining based at least in part on some or all of the product makeup data records. In any case, the percentage of the volume and/or amount of ingredients consumed and/or remaining may be determined.

Block 1008 is followed by block 1010, wherein the product dispenser data is optionally communicated locally and/or remotely with a data processing resource. In the illustrated embodiment, a processor or controller, such as 106 in fig. 1, associated with the product dispenser, such as 102A, may transmit the component data records, including any changes in the actual component matrix component assignments, to a local and/or remote server or data processing resource, such as 126, for storage and retrieval. For example, the data communication may include transmitting data of the percentage of the components consumed and/or remaining in the component matrix, and/or other types and/or kinds of data, as may be needed and/or desired in a particular implementation.

Block 1010 is followed by block 1012, wherein the result is optionally written to a data processing device associated with the component wrapper. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with a product dispenser, such as 102A, may selectively write results to data processing equipment associated with product component packages or component packages shown as 116A-116Q. For example, data processing devices may include, but are not limited to: RFID tags, and/or other types and/or kinds of data processing devices, as may be needed and/or desired in particular embodiments.

In one embodiment, writing to the data processing device associated with the ingredient package may be advantageous in that data relating to consumed and/or remaining ingredient volumes and/or quantities may be transferred along with data in the data processing device as the ingredient package is moved to other product dispensers.

The method 1000 ends after block 1012.

In one embodiment, a product consumption data record may be generated when a consumer dispenses a product. The product composition data record indicates the type and/or kind of ingredients dispensed and the volume and/or quantity of those ingredients dispensed, etc. Thus, the product composition data record may be used to deplete the virtual ingredient supply such that the volume and/or amount of virtual ingredient reflects the volume and/or amount of actual ingredient remaining in the product dispenser. The results may be data transferred to a data processing resource and/or written to a data processing device associated with the component wrapper. The data processing device may be, for example, an RFID tag, and/or other types and/or kinds of data processing devices, as may be needed and/or desired in particular embodiments.

Referring to fig. 11, one example of a method 1100 for determining a total amount of consumed and/or remaining component volumes and/or quantities in a component package is shown. The method 1100 begins in block 1102. In block 1102, the volume and/or quantity is read from the data processing device associated with the component packet. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with a product dispenser, such as 102A, may read or otherwise obtain data from one or more data processing devices associated with respective product component packages or component packages, shown as 116A-116Q. For example, one or more machine readable code readers 118A-118Q may read or obtain data from one or more data processing devices, such as RFID tags, associated with respective product component packages, shown as 116A-116Q, to obtain the volume and/or quantity of components contained within the package.

Block 1102 is followed by block 1104 in which input is received from the consumer to dispense the product. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may allow the consumer to select and dispense a selected product. For example, a consumer may enter or select a product via a user interface associated with the product dispenser, such as user interface 112 in FIG. 1. A processor or controller such as 106 associated with the product dispenser such as 102A may allow the consumer to dispense a selected product.

Block 1104 is followed by block 1106 in which a product composition data record is established. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with a product dispenser, such as 102A, may create or otherwise generate a product composition data record or other file for storage and subsequent retrieval of product information. The controller, such as 106, may store product composition data records or other files in an associated memory or data storage device, such as 110. Product composition data records or files may include, but are not limited to: the type and/or kind of product selected or ingredient dispensed, the volume or quantity of each ingredient dispensed when the product is formed, the date and time the product was dispensed, any associated consumer data, any associated dispenser data, and/or other types and/or kinds of data. In one embodiment, a local and/or remote server or data processing resource, such as 126, may create or otherwise create and store product composition data records or other files in an associated memory or data storage device, such as 110 or 128A-128C. In any case, a product composition data record may be established.

Block 1106 is followed by block 1108, in which the virtual ingredient matrix ingredient supply is depleted by volume and/or quantity as reflected in the product makeup data record. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with a product dispenser, such as 102A, may deplete or otherwise reduce the volume and/or quantity from similar or identical virtual ingredients based at least in part on some or all of the product composition data records. The controller, such as 106, may utilize some or all of the product composition data records and adjust the volume and/or number of similar or identical virtual components, as well as track changes in the volume and/or number of similar or identical virtual components. For example, if one or more queried product composition data records indicate that one ounce of cherry flavor is dispensed, then one ounce of cherry flavor is subtracted from the volume of cherry flavor currently associated with the virtual cherry flavor component. In this regard, the product composition data record may be used to adjust some or all of the virtual component matrix component levels such that the virtual component volume and quantity levels match the actual component volume and quantity levels by processing the product composition data record. Such data may be stored in a memory, database, or data storage device, such as 110 or 128A-128C, and may also be stored in a processor or controller, such as 106, or a local and/or remote server or data processing resource, such as 126. In one embodiment, a local and/or remote server or data processing resource such as 126 may be depleted or otherwise reduced in volume and/or quantity from similar or identical virtual components based at least in part on some or all of the product makeup data records. In any case, the virtual ingredient matrix ingredient supply may be depleted by volume and/or quantity as reflected in the product composition data record.

Block 1108 is followed by block 1110 in which product dispenser data is optionally communicated locally and/or remotely to a data processing resource. In the illustrated embodiment, a processor or controller, such as 106 in fig. 1, associated with the product dispenser, such as 102A, may transmit the component data records, including any changes in the actual component matrix component assignments, to a local and/or remote server or data processing resource, such as 126, for storage and retrieval. For example, the data communication may include transmitting data of the percentage of the components consumed and/or remaining in the component matrix, and/or other types and/or kinds of data, as may be needed and/or desired in a particular implementation.

Block 1110 is followed by block 1112 in which the results are optionally written to a data processing apparatus associated with the component wrapper. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with a product dispenser, such as 102A, may selectively write results to data processing equipment associated with product component packages or component packages shown as 116A-116Q. For example, data processing devices may include, but are not limited to: RFID tags, and/or other types and/or kinds of data processing devices, as may be needed and/or desired in particular embodiments. In one embodiment, writing to the data processing device associated with the ingredient package may be advantageous in that data relating to consumed and/or remaining ingredient volumes and/or quantities may be transferred along with data in the data processing device as the ingredient package is moved to other product dispensers.

The method 1100 ends after block 1112.

In one embodiment, the consumed or remaining ingredient volume or amount may be written onto a data processing device associated with the ingredient packaging. In operation, the data processing device may be read, adjusted by processing the beverage consumption data record, and written back to the data processing device. In this connection, the data processing device always contains the most recent information about the volume or amount of consumed and remaining components.

Referring to fig. 12, one example of a method 1200 of updating a recipe/prescription database in a product dispenser is shown. The method 1200 begins in block 1202. In block 1202, a product dispenser communicates with a data processing resource locally and/or remotely. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may communicate with local and/or remote servers or data processing resources, such as 126, via a network, such as 104. For example, data communications may include, but are not limited to: a check is made to see if a more recent version of the recipe/prescription database is available for download from the data processing resource to the product dispenser.

Block 1202 is followed by block 1204, wherein a determination is made as to whether a recipe/prescription database update is available. If the determination is positive, i.e., an update is available, the method 1200 continues to block 1206. If the determination is negative, i.e., no updates are available, the method 1200 ends. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may compare the current version to a version of a recipe/prescription database that may be downloaded from a data processing resource, such as 126. In one embodiment, a local and/or remote server or data processing resource such as 126 may compare the current version to the version of the downloadable recipe/prescription database. In any case, a determination may be made as to whether a recipe/prescription database upgrade is available.

In block 1206, a more recent version of the recipe/recipe is transmitted from the data processing resource to the product dispenser. In the illustrated embodiment, a data processing resource, such as 126 in FIG. 1, may communicate a more recent version of the recipe/prescription to a product dispenser, such as 102A, via a network, such as 104. A processor or controller such as 106 associated with the product dispenser such as 102A may receive an updated version of the recipe/prescription database.

Block 1206 is followed by block 1208, wherein the product dispenser recipe/prescription database is updated. In the illustrated embodiment, a processor or controller, such as 106 in FIG. 1, associated with the product dispenser, such as 102A, may store or otherwise install an updated version of the recipe/recipe received from a data processing resource, such as 126, in an associated memory or data storage device, such as 110.

The method 1200 ends after block 1208.

In one embodiment, the recipe/prescription database may be maintained at the data processing resource. Periodically, the recipe/prescription database may be compared to the version of the database in the product dispenser. The recipe/prescription database may be transmitted from the data processing resource to the product dispenser if the version of the database in the product dispenser needs to be updated.

The capabilities of various embodiments of the present invention can be implemented in software, firmware, hardware or some combination thereof.

As one example, one or more aspects of the present invention can be included in an article of manufacture (such as one or more computer program products) having, for instance, computer usable media. The media has embodied therein, for instance, computer readable program code means for providing and facilitating the capabilities of embodiments of the present invention. The article of manufacture can be included as a part of a computer system or sold separately. An example of a suitable article of manufacture is a consumer interaction engine or module such as 114 depicted in FIG. 1.

Additionally, at least one program storage device readable by a machine, tangibly embodying at least one program or set of instructions executable by the machine to perform the capabilities of embodiments of the present invention can be provided. One example of a suitable program storage device readable by a machine is a memory or data storage device such as 110 depicted in FIG. 1.

The flow diagrams depicted herein are just examples. There may be many variations to these diagrams or the elements (or operations) described therein without departing from the scope of the invention as claimed. For example, elements may be performed in a differing order, or elements may be added, deleted or modified. All of these variations are intended to be part of the claimed invention.

While embodiments of the invention have been described, it will be understood that those skilled in the art, both now and in the future, may make various improvements and enhancements which fall within the scope of the claims which follow. These claims should be construed to maintain the proper protection for the invention first described.

Claims (21)

1. A product dispenser (102) comprising:

an ingredient matrix (108) operable to hold a plurality of product ingredients, wherein the ingredient matrix is operable to hold a plurality of product ingredient packages, wherein at least a portion of the plurality of product ingredient packages contain ingredients at defined locations within the ingredient matrix; and

a controller (106) in communication with the composition matrix (108) and operable to implement a set of instructions to:

receiving product data associated with the plurality of product ingredients;

tracking usage of the plurality of product ingredients in a product composition data record when at least one product is dispensed;

updating the product data during dispensing of a product or installation of one or more product ingredients in the ingredient matrix (108), or after dispensing of a product or installation of one or more product ingredients in the ingredient matrix (108), wherein the product composition data record is depleted of one or more product ingredient volumes or quantities using the plurality of product ingredients; and

updating one or more product component volumes or quantities of the product composition data record based at least in part on detecting insertion of a new product component package into the component matrix.

2. The dispenser (102) of claim 1, wherein the product data comprises at least one of: product composition data, ingredient type, product type, volume of product ingredient, quantity of product ingredient, rate of depletion of product ingredient, volume of product ingredient remaining, or quantity of product ingredient remaining.

3. The dispenser (102) of claim 1, wherein the controller is further operable to implement a set of instructions to:

generating a virtual ingredient matrix based at least in part on the plurality of product ingredients within the ingredient matrix (106).

4. The dispenser (102) of claim 3, wherein the controller (106) is further operable to implement a set of instructions to:

updating the virtual ingredient matrix during or after dispensing at least one product based at least in part on the product data.

5. The dispenser (102) of claim 1, wherein the controller (106) is further operable to implement a set of instructions to:

determining whether to order one or more of the product components based at least in part on the product data.

6. The dispenser (102) of claim 1, wherein the controller (106) is further operable to implement a set of instructions to:

estimating when the product ingredient will be depleted based at least in part on the product data.

7. The dispenser (102) of claim 1, wherein the controller (106) is further operable to implement a set of instructions to:

determining an optimized composition matrix based at least in part on the product data.

8. The dispenser (102) of claim 1, further comprising:

a reader (1106A) configured to read machine-readable information associated with an ingredient package containing at least one product ingredient.

9. A method for operating a beverage dispenser (102), comprising:

receiving product data associated with a plurality of product ingredients operable to be contained within an ingredient matrix, wherein at least a portion of the plurality of product ingredients contain ingredients at defined locations within the ingredient matrix;

tracking usage of the plurality of product ingredients in a product composition data record when at least one product is dispensed; and

updating the product data in a product composition data record during dispensing of a product or installation of one or more product ingredients in the ingredient matrix (108), or after dispensing of a product or installation of one or more product ingredients in the ingredient matrix (108), wherein one or more product ingredient volumes or amounts in the product composition data record are depleted via use of the plurality of product ingredients, or wherein one or more product ingredient volumes or amounts are increased via installation of one or more newly added product ingredients.

10. The method of claim 9, wherein tracking usage of the plurality of product ingredients as at least one product is dispensed comprises: monitoring at least one of: volume of ingredients used, number of ingredients used, or rate of use of ingredients.

11. The method of claim 9, further comprising:

estimating when at least one of the plurality of product ingredients will be depleted based at least in part on the product data.

12. The method of claim 9, further comprising:

determining when to order one or more product ingredients of the plurality of product ingredients based at least in part on the product data.

13. The method of claim 9, further comprising:

an optimized composition matrix is determined based at least in part on the product data.

14. The method of claim 13, wherein determining an optimized composition matrix based at least in part on product data comprises: estimating when at least one product ingredient of the plurality of product ingredients will be depleted based at least in part on the product data.

15. A method for managing a product dispenser (102), the method comprising:

receiving product data associated with a plurality of product ingredients installed within an ingredient matrix (108);

tracking usage of the plurality of product ingredients in a product composition data record when at least one product is dispensed, wherein one or more product ingredient volumes or amounts in the product composition data record are depleted via usage of the plurality of product ingredients;

estimating when at least one product ingredient of the plurality of product ingredients will be depleted; and

an order for any depleted product component is transmitted via the network (104).

16. The method of claim 9 or 15, wherein receiving product data associated with a plurality of product ingredients installed within an ingredient matrix (108) comprises: machine-readable information associated with a package of ingredients (116A-116Q) containing at least one product ingredient is read.

17. The method of claim 9 or 15, wherein tracking usage of the plurality of product ingredients as at least one product is dispensed comprises:

generating a virtual ingredient matrix based at least in part on the plurality of product ingredients within the ingredient matrix (108); and

updating the virtual ingredient matrix during or after dispensing at least one product based at least in part on the product data.

18. The method of claim 15, wherein estimating when at least one of the plurality of product ingredients will be depleted comprises: determining an estimate based at least in part on one of: the usage volume of the component, the usage amount of the component, the usage speed of the component, the usage volume of the virtual component, the usage amount of the virtual component, or the usage speed of the virtual component.

19. The method of claim 15, wherein the step of communicating the order for any depleted product ingredients via the network (104) comprises at least one of: the order is sent before the product component or virtual component is depleted or at a predetermined time before an estimated time of depletion of the product component or virtual component.

20. A system (100) for managing product ingredients, the system (100) comprising:

an ingredient matrix operable to hold a plurality of product ingredients, wherein at least a portion of the plurality of product ingredients comprise ingredients at defined locations within the ingredient matrix; and

a controller (106) in communication with the composition matrix (108) and operable to implement a set of instructions operable to:

receiving product data associated with a plurality of product ingredients installed within an ingredient matrix (108);

tracking usage of the plurality of product ingredients in a product composition data record when at least one product is dispensed, wherein one or more product ingredient volumes or amounts in the product composition data record are depleted via usage of the plurality of product ingredients;

estimating when at least one product ingredient of the plurality of product ingredients will be depleted; and

an order for any depleted product component is transmitted via the network (104).

21. The system of claim 20, wherein the controller (106) is further operable to implement a set of instructions operable to:

generating a virtual ingredient matrix based at least in part on the plurality of product ingredients within the ingredient matrix (108); and

updating the virtual ingredient matrix during or after dispensing at least one product based at least in part on the product data.