A system for storing, dispensing, and brewing coffee

Abstract

A scale hub for guiding a user in storing, dispensing and brewing coffee, the scale hub comprising: a weight sensor; a processor; a tag reader; a memory storing a program for performing a method of: receiving tag identifiers from tags attached to a coffee receptacle placed upon the weight sensor; receiving a roast date and a storage temperature profile for coffee beans in the coffee receptacle; determining a flavour intensity of the coffee beans depending upon the roast date and the storage temperature profile; determining a brewing recipe; displaying instructions to place a brewing module on the scale bed; displaying instructions to grind an amount of coffee from the tagged coffee receptacle and transfer the ground coffee to the brewing module; and displaying instructions to process the ground coffee with water to produce a flavoured cup of coffee.

Description

A SYSTEM FOR STORING, DISPENSING, AND BREWING COFFEEField

[0001] The present invention relates generally to coffee making, and in particular to a compact system and a method for guiding a user in storing, dispensing and brewing coffee. The present invention also relates to a computer program product including a computer readable medium having recorded thereon a computer program for, in the noted system, performing a method of storing, dispensing and brewing coffee.Background

[0002] Coffee is a beloved beverage enjoyed by millions around the world. While the simplest method of making coffee involves brewing ground, roasted coffee beans with hot water to extract their flavour and aroma, this basic approach does not always yield a consistently greattasting cup. Achieving a superior coffee experience, with rich flavours and aromas, requires attention to several key elements.

[0003] In order to consistently produce better-tasting coffee, a number of factors need to be taken into account. Using freshly roasted coffee beans at their peak freshness is crucial. The beans should match the user’s preferred flavour profile, whether it be a light, medium, or dark roast. Different roasts, namely light, medium, and dark, have distinct peak freshness time windows and need to be consumed at different times from their roasting date. Good quality coffee is both costly and delicate, making it essential to employ proper storage practices to slow down the oxidation process and preserve its freshness. The coffee beans must be ground to the appropriate size for the chosen brewing method to ensure optimal flavour extraction. Additionally, coffee should be brewed within a minute of grinding to preserve its freshness and flavour. Maintaining the right balance between coffee and water is essential, adjusted to the user’s preferred strength for a more personalized experience. The water temperature must be carefully controlled to avoid over-extraction or under-extraction, which can negatively impact the flavour. The brewing time must be precisely managed according to the method used, ensuring the best possible flavour extraction.

[0004] Achieving consistently great-tasting coffee requires the use of numerous items of specialty brewing equipment. Precise monitoring of factors such as coffee weight, brewing time, temperature, and grind size is crucial to replicate ideal brewing conditions consistently. However, setting up and operating this equipment can be complex and time-consuming.Summary

[0005] It is an object of the present invention to ameliorate one or more of the above disadvantages or at least provide a useful alternative to the above.

[0006] Disclosed are arrangements, referred to as Data Driven Coffee Preparation (DDCP) arrangements, which seek to address the above problems by providing a coffee storage and process management system that is compact and stores important information about the roasted coffee beans at the time when they are stored in one or more coffee storage receptacles. This information is then used by the DDCP systems to determine a freshness parameter for the roasted coffee beans in question. This information guides and directs the user to use the roasted coffee beans in a time frame which is appropriate for making coffee with the best flavour and aroma. The DDCP arrangements can also provide the user with an estimate of when the coffee storagemodules will become empty and need to be refilled. Some DDCP arrangements can also guide and direct the user in making coffee with the best flavour and aroma having regard to a variety of brewing styles, brewing modules and desired coffee strengths.

[0007] According to an aspect of the present disclosure, there is provided a scale hub configured to guide a user in storing, dispensing and brewing coffee, the scale hub comprising: a weight sensor operatively coupled to a scale bed of the scale hub; a processor; a tag reader operatively coupled to the processor; a memory storing a processor executable program for directing the processor to perform a method comprising the steps of receiving from the tag reader one or more tag identifiers from electronically readable tags attached to a tagged coffee receptacle placed upon the scale bed; receiving from the user a roast date and a storage temperature profile for roasted coffee beans in the tagged coffee receptacle; determining a flavour intensity of the roasted coffee beans depending upon the roast date and the storage temperature profile; determining a brewing recipe; displaying instructions from the brewing recipe for the user to place a brewing module associated with the brewing recipe on the scale bed; displaying instructions for the user to grind an amount of coffee from the tagged coffee receptacle and transfer the ground coffee to the brewing module; and displaying instructions for the user to process the ground coffee with water to produce a flavoured cup of coffee.

[0008] According to an aspect of the present disclosure, there is provided a scale hub according to paragraph

[0007] , wherein the tagged coffee receptacle is a coffee storage module comprising a container component and a complimentary lid component each having attached a respective electronically readable tag; and the electronically readable tags are associated with the coffee storage module in stored system information stored in the memory.

[0009] According to an aspect of the present disclosure, there is provided a scale hub according to paragraph

[0007] , wherein the tagged coffee receptacle is a coffee storage bag having attached an electronically readable tag; and the electronically readable tag is associated with the coffee storage bag in stored system information stored in the memory.

[0010] According to an aspect of the present disclosure, there is provided a scale hub according to paragraph

[0007] , wherein the coffee storage receptacle is permanently stored in a specified storage temperature environment; and the storage temperature profile is a fixed temperature reflecting the storage temperature environment in which the coffee storage receptacle is permanently stored.

[0011] According to an aspect of the present disclosure, there is provided a scale hub according to paragraph

[0010] , wherein the coffee storage receptacle is permanently stored in one of three storage temperature environments namely (i) at ambient temperature or (ii) in a refrigerator, or (iii) in a freezer; and the storage temperature profile is a fixed temperature reflecting the storage temperature environment in which the coffee storage receptacle is permanently stored.

[0012] According to an aspect of the present disclosure, there is provided a scale hub according to paragraph

[0007] , wherein the flavour intensity has a mathematical representation of an exponential decay function depending upon the elapsed time after degassing time and a roast type dependent decay constant.

[0013] According to an aspect of the present disclosure, there is provided a scale hub according to paragraph

[0012] , wherein the flavour intensity has a mathematical representation of an exponential decay function further depending upon the storage temperature profile.

[0014] According to an aspect of the present disclosure, there is provided a scale hub according to paragraph

[0007] , wherein the step of determining a brewing recipe comprises the steps of: receiving from the user a selection of a brewing style from a displayed list of available brewing styles; and determining the brewing recipe from the selected brewing style and stored system information stored in the memory.

[0015] According to an aspect of the present disclosure, there is provided a scale hub according to paragraph

[0007] , wherein the step of determining a brewing recipe comprises the steps of: receiving from the tag reader one or more tag identifiers of tags attached to a tagged brewing module placed upon the scale bed; determining a brewing style dependent upon the tag identifiers of the tagged brewing module and stored system information stored in the memory; and determining the brewing recipe from the brewing style and stored system information stored in the memory.

[0016] According to an aspect of the present disclosure, there is provided a scale hub according to paragraph

[0007] , wherein prior to the step of displaying instructions for the user to grind an amount of coffee the method comprises the further step of communicating a control signal depending upon the flavour intensity to the electronically controllable coffee grinder to thereby direct the coffee grinder to grind roasted coffee beans to a desired particle size.

[0017] According to an aspect of the present disclosure, there is provided a scale hub according to paragraph

[0016] , wherein the control signal directs the coffee grinder to grind roasted coffee beans to a desired particle size depending upon the flavour intensity and a roast type.

[0018] According to an aspect of the present disclosure, there is provided a scale hub according to paragraph

[0007] , wherein the specific tagged coffee receptacle placed upon the scale bed is one of a plurality of tagged coffee receptacles each having attached a corresponding set of associated tags and tag identifiers; and the method comprises the further steps of: determining a weight of the specific filled coffee storage receptacle during successive multi-module storage mode processing cycles during each of which a weight of coffee is removed from the specific coffee storage receptacle; estimating a number of days remaining until the specific coffee storage receptacle is empty; and issuing an alert, depending upon the estimated number of days remaining and the flavour intensity, indicating that re-ordering of coffee should be performed.

[0019] According to an aspect of the present disclosure, there is provided a scale hub according to paragraph

[0014] or paragraph

[0015] , wherein the method comprises the further steps of: receiving from the user a selection of a desired number of cups from a display indicating the available number of cups; receiving from the user selection of a desired strength from a display indicating the available range of strength; and determining the recipe dependent upon the selected number of cups and the selected strength.

[0020] According to an aspect of the present disclosure, there is provided a tangible computer readable data storage medium having a computer program recorded therein, the program being executable by a computer apparatus to make the computer perform a method comprising the steps of: receiving from a tag reader operatively coupled to the computer apparatus one or more tag identifiers from electronically readable tags attached to a tagged coffee receptacle placed upon a weight sensor in communication with the computer apparatus; receiving from a user a roast date and a storage temperature profile for roasted coffee beans in the tagged coffee receptacle; determining a flavour intensity of the roasted coffee beans depending upon the roast date and the storage temperature profile; determining a brewing recipe; displaying instructions from the brewing recipe for the user to place a brewing module associated with the brewingrecipe on the weight sensor; displaying instructions for the user to grind an amount of coffee from the tagged coffee receptacle and transfer the ground coffee to the brewing module; and displaying instructions for the user to process the ground coffee with water to produce a flavoured cup of coffee.

[0021] According to an aspect of the present disclosure, there is provided a scale hub configured to guide a user in dispensing coffee, the scale hub comprising: a weight sensor operatively coupled to a scale bed of the scale hub; a processor; a memory storing a processor executable program for directing the processor to perform a method comprising the steps of: receiving from a user a roast date and a storage temperature profile for roasted coffee beans in a coffee receptacle placed upon the scale bed; and determining and displaying a flavour intensity of the roasted coffee beans depending upon the roast date and the storage temperature profile.

[0022] According to an aspect of the present disclosure, there is provided a scale hub according to paragraph

[0021] , comprising the further steps of: determining a weight of the coffee receptacle during successive single-module storage mode processing cycles during each of which a weight of coffee is removed from the coffee receptacle; and estimating a number of days remaining until the coffee receptacle is empty; and issuing an alert, depending upon the estimated number of days remaining and the flavour intensity, indicating that re-ordering of coffee should be performed.

[0023] According to an aspect of the present disclosure, there is provided a scale hub according to paragraph

[0007] , wherein the brewing module associated with the brewing recipe is a multicomponent brewing module comprising a plurality of complimentary brewing module components, each of which is individually tagged with a corresponding electronically readable tag.

[0024] According to an aspect of the present disclosure, there is provided a scale hub according to paragraph

[0023] , wherein the complimentary brewing module components are a pour over carafe and a pour over dripper each of which is individually tagged with a corresponding electronically readable tag.

[0025] According to an aspect of the present disclosure, there is provided a scale hub according to paragraph

[0023] , wherein the multi-component brewing module is a cold brew carafe assembly comprising three complimentary brewing module components, each of which is individually tagged with a corresponding electronically readable tag.

[0026] Other aspects are also disclosed.Brief Description of the Drawing

[0027] Preferred embodiments of the present invention will now be described by way of example, with reference to the accompanying drawings and APPENDICES (also see the GLOSSARY in the “Detailed Description” for the meaning of some terms), wherein:Fig. l is a schematic depiction of a multi-module DDCP system;Fig. 2 is a schematic depiction of a scale hub that can be used in the DDCP systems of Figs. 1 and 8;Figs. 3A and 3B collectively form a schematic block diagram representation of an embedded electronic computing device upon which described DDCP systems can be practiced;Fig- 4 is an example of a process flow diagram for performing an initial setup process for modules used in a multi-module DDCP system;Fig- 5 is an example of a process flow diagram for a storage mode process used in both singlemodule and multi-module DDCP systems;Fig- 6 is an example of a process flow diagram for a user-selection based (also referred to as user-guided) dispense mode process used in a multi-module DDCP system;Fig. 7 is an example of a process flow diagram for a brewing mode process used in a multimodule DDCP system;Fig. 8 is a schematic depiction of a single-module DDCP system;Fig. 9 is an example of a process flow diagram for performing an initial setup process for coffee stored in a coffee bag without using a storage module;Fig. 10 is an example of a process flow diagram for performing single and multi-module DDCP system processes;Fig. 11 is an example of a process flow diagram fragment for DDCP system processes for coffee in a coffee bag without using storage modules;Fig. 12 is an example of a process flow diagram for an equipment-selection based (also referred to as accessory-guided) dispense mode process used in a multi-module DDCP system;Fig. 13 illustrates in graphical format flavour intensity over time for different roasts at 20°C (Room Temperature) showing Freshness curves at 20 °C (computed from Table 8B);Fig. 14 illustrates in graphical format flavour intensity over time for different roasts at 4°C (Fridge) showing Freshness curves at 4 °C (computed from Table 10B); andFig. 15 illustrates in graphical format flavour intensity over time for different roasts at -18°C (Freezer) showing Freshness curves at -18 °C (computed from Table 1 IB).APPENDIX I sets out data that is input or output from various process steps in the flow charts depicted in Figs. 4, 5, 6, 7, 9, 10, 11 and 12; andAPPENDIX II describes examples of brewing recipe parameter values for brewing recipes that the DDCP system makes available to the user.Detailed Description

[0028] Where reference is made in any one or more of the accompanying drawings to steps and / or features, which have the same reference numerals, those steps and / or features have for the purposes of this description the same function(s) or operation(s), unless the contrary intention appears.

[0029] It is to be noted that the discussions contained in the "Background" section and the section above relating to prior art arrangements relate to discussions of documents or devices which may form public knowledge through their respective publication and / or use. Such discussions should not be interpreted as a representation by the inventor or the patent applicantthat such documents or devices in any way form part of the common general knowledge in the art.

[0030] The following table contains a GLOSSARY of terms used in this description and their associated meanings, unless otherwise explicitly stated.

[0031] Fig. 8 is a schematic depiction of a single-module DDCP system 800. The system 800 comprises a coffee storage module 809 made up from a coffee storage module container component 802 and a coffee storage module lid component 801. The container and lid components 802, 801 are referred to as complimentary coffee storage module components.

[0032] The coffee storage module 809 can be placed upon, or alternately is detachably attached to, the scale bed 137 of the scale hub 112. The scale hub 112 has an embedded computing device 301 (described hereinafter in more detail with reference to Figs. 3A and 3B), user interface peripherals comprising control buttons 388, a display 318 (which may be a touch screen that can receive user input by the user touching the display 318), and a lip 805 which can hold a smart phone 122 (see Fig. 1) in place as described hereinafter in more detail with reference to Fig. 1.

[0033] In use a user 120 purchases the bag 107 of unroasted coffee beans. The user 120 roasts the unroasted coffee beans in the coffee roaster 123 producing the coffee storage bag 124 of roasted coffee beans. The user 120 can then transfer the roasted coffee beans in the bag 124 to the empty coffee storage module 809 which has been placed on, or is detachably attached to, the scale hub 112, according to DDCP processes described hereinafter in more detail with reference to Figs. 5 and 10. The coffee storage module 809 is then stored at a moderate temperature of (10°C to 21°C) in a pantry away from direct sunlight if possible until it is desired to make coffee. Alternately, the user can use the DDCP system with the coffee storage bag 124 of roasted coffee beans without transferring the roasted coffee beans from the bag 124 of roasted coffee beans to a coffee storage module, described hereinafter in more detail with reference to Fig. 10.

[0034] The single-module DDCP system 800 ensures that once the roasted coffee beans are transferred from their packaging 124 to the coffee storage module 809 according to the DDCP processes depicted in Figs. 5 and 10, important information about the beans such as their roast date is securely stored in the DDCP system.

[0035] When the user 120 wishes to make a cup of coffee he places the coffee storage module 809 on the scale hub 112 (unless it is already detachably attached thereto) and removes an amount of roasted coffee beans from the container (as described hereinafter in more detail with reference to the DDCP processes depicted in Figs. 5 and 10). The DDCP processes depicted in Figs. 5 and 10 provide the user 120 with a freshness parameter value (described hereinafter in more detail with reference to a step 521 in Fig. 5) for the roasted coffee beans in the coffee storage module 809 and can also provide the user with an estimate of when the roasted coffee beans in the coffee storage module 809 will be used up at the present rate of consumption (described hereinafter in more detail with reference to a step 521 in Fig. 5).

[0036] The user grinds the removed weight of roasted coffee beans in a coffee grinder 109. The coffee grinder 109 can be an electronically controllable grinder having an electronic signal input port (such as a digital communication interface) so that the coffee grinder can be directed to grind roasted coffee beans to a desired particle size.

[0037] The user 120 then pours water at the appropriate temperature from a kettle 119 directly into a cup (not shown) into which the ground coffee has been placed. Alternately, the user 120 pours the water from the kettle 119 over a brewing module (described hereinafter in more detail with reference to Fig. 1) into which the ground coffee has been placed and thence into the cup, producing the desired cup of coffee with optimal flavour and aroma. If brewing espresso the cup and Scale hub 112 is placed on the espresso machine tray and the extraction goes straight into the cup. If brewing with a Pour-Over Coffee-Maker the coffee maker sits on top of a carafe, and the brewed coffee is poured into a cup.

[0038] Peak flavour potential for the bag 124 of roasted coffee beans typically occurs when the beans are used an optimum number of days after roasting (see Table 5). This optimum number of days can vary depending on the type of bean and the roasting type (e.g. light, medium or dark roast), and the style of the coffee storage module 809 (e.g. vacuum sealed, somewhat air-tight etc.).

[0039] Fig. 1 is a schematic depiction of a multi-module DDCP system 100. The system 100 includes a plurality 101 of coffee storage modules 102, ..., 103. The system also includes a plurality 111 of brewing modules 113, . . ., 117. The system 100 further includes the scale hub 112 (described hereinafter in more detail with reference to Figs. 2, 3A and 3B) having the scale bed 137 upon which a selected coffee storage module such as 102 can be placed or detachably attached.

[0040] The scale hub 112 has the embedded computing device 301 (described hereinafter in more detail with reference to Figs. 3A and 3B). The scale hub 112 can communicate, as depicted by dashed lines 130 and 128, via a local area network 129 with a smartphone 122 having a display 138. The local area network 129 can be implemented using Wi Fi, Bluetooth or other suitable local networking protocol. The smartphone 122 can communicate, as depicted by dashed lines 121 and 105, over a wide area communication network 106 with a remote server 104. The scale hub 112 can also communicate, as depicted by dashed lines 130, 110 and 105, over the wide area network 106 with the remote server 104. The smartphone 122 runs a DDCP software application (not shown) that connects the scale hub 112 to an online subscription service (not shown), running on the remote server 104. The DDCP system can automatically pause a scheduled order or advance reordering more coffee ahead of the scheduled order depending upon the dynamically estimated days remaining 523.

[0041] In use the user 120 purchases the bag 107 of unroasted coffee beans. The user 120 roasts the unroasted coffee beans in the coffee roaster 123 producing the bag 124 of roasted coffeebeans. The user 120 can then transfer the roasted coffee beans in the bag 124 to one of the plurality 101 of empty coffee storage module 102, . . 103 which has been placed on, or is detachably attached to, the scale hub 112, according to DDCP processes described hereinafter in more detail with reference to Figs. 4 - 7 and 10. The coffee storage module is then stored at a moderate temperature of (10°C to 21 °C) in a pantry away from direct sunlight if possible until it is desired to make coffee.

[0042] The multi-module DDCP system 100 ensures that once roasted coffee beans are transferred from their packaging 124 to the coffee storage module according to the DDCP processes depicted in Figs. 4-7 and 10, important information about the beans such as their roast date is securely stored in the DDCP system.

[0043] When the user 120 wishes to make a cup of coffee he can place the coffee storage module on the scale hub 112 or detachably attach it thereto, and the scale hub 112 will direct the user 120 to make the desired cup of coffee according to the processes depicted in Figs. 4-7 and 10.

[0044] Fig. 2 is a schematic depiction of the scale hub 112 that can be used in the DDCP systems of Figs. 1 and 8. The scale hub 112 has the scale bed 137 upon which a coffee storage module such as 809 (see Fig. 8) can be placed or can be detachably attached. The scale hub 112 has the tag reader 387 (which is an RFID tag reader in the example shown) which can read the tags (such as 134 and 135 in Fig. 1) attached to the complimentary container and lid components (respectively 802 and 801 in Fig. 8) of the coffee storage module 809. The scale hub 112 has an embedded computing device 301 and user interface peripherals 318, 388 (described hereinafter in more detail with reference to Figs. 3A and 3B). The scale hub 112 has a lip 204 to hold the smart phone 122 (see Fig. 1) in place if the smart phone 122 is placed on the display 318 in which case the smartphone display 138 takes on the user interface function otherwise provided by the scale hub display 318.

[0045] Figs. 3A and 3B collectively form a schematic block diagram representation of an electronic device upon which described DDCP arrangements can be practised.

[0046] Figs. 3A and 3B collectively form a functional block diagram of the electronic computing device 301, upon which the DDCP methods previously described can be practiced. Fig. 3A depicts the computing device 301 and its environment, and Fig. 3B depicts the embedded controller 302 in the electronic computing device 301.

[0047] As seen in Fig. 3A, the electronic device 301 comprises an embedded controller 302. Therefore, the electronic device 301 may be referred to as an “embedded device.” In the depicted example, the embedded controller 302 has a processing unit (or processor) 305 which communicates in a bi-directional manner with an internal data storage block 309 (described hereinafter in more detail in regard to Fig. 3B). The data storage block 309 can be implemented with non-volatile semiconductor read only memory (ROM) 360 and semiconductor random access memory (RAM) 370 (see Fig. 3B). The RAM 370 may be volatile, non-volatile or a combination of volatile and non-volatile memory modules.

[0048] The electronic device 301 includes a display controller 307 that communicates with a display 318, which may be a liquid crystal display (LCD) panel or the like. The display controller 307 can display text and / or graphical images on the display 318 as directed by instructions received from the embedded controller 302, with which the display controller 307 communicates.

[0049] The electronic device 301 also includes a user interface I / O module 313 which communicates with user input devices such as the tag reader 387, the weight sensor 385 and the manual control buttons 388. In some implementations, the user interface I / O module 313 may include a touch sensitive panel physically associated with the display 318 to collectively form a graphical user interface (GUI) touch-screen for receiving inputs and providing outputs to the user. Alternately, a prompt or menu driven GUI can be used with keypad-display combinations. Other forms of user input devices may also be used, such as a microphone (not illustrated) for voice commands or a joystick / thumb wheel (not illustrated) for ease of navigation about menus.

[0050] As seen in the example in Fig. 3A, the electronic device 301 has a memory interface module 306, which communicates with the processor 305 as depicted by an arrow 319. The memory interface 306 can communicate with a compatible portable memory device 325 which can act as a source or destination of data or to supplement the internal data storage device 309. The interface 306 can communicate, for example, with portable memory devices such as Universal Serial Bus (USB) memory devices, Secure Digital (SD) cards, Personal Computer Memory Card International Association (PCMIA) cards, optical disks and magnetic disks.

[0051] The electronic device 301 has a communications interface 308 and a wireless modem 380 to permit the device 301 to communicate with “remote” system components such as the remote server 104 or to a computer or communications network (not shown) as depicted by an arrow 383.

[0052] The electronic device 301 is configured to monitor and control the scale hub 112. The embedded controller 302, in conjunction with further special function components such as the tag reader 387 and the weight sensor 385, is provided to perform that DDCP function.

[0053] The methods described above may be implemented using the embedded controller 302, where the processes of Figs. 4-7 and 10 may be implemented as one or more interoperable software application programs 333 that can be executed by the embedded controller 302. The electronic device 301 of Fig. 3A implements the described DDCP methods. With reference to Fig. 3B it is clearly understood that the steps of the described DDCP methods are carried out by instructions (such as 362 in Fig. 3B) in the software applications 333 that are performed by the embedded controller 302. The software instructions (such as 362) may be formed as one or more software code routines, each routine performing one or more specified tasks. The one or more interoperable software applications 333 may also be partitioned into two separate functional parts, in which a first part and the corresponding code modules perform the described DDCP methods, and a second part and the corresponding code modules manage a user interface between the first part and the user.

[0054] The software 333 of the embedded controller 302 is typically stored in the non-volatile ROM 360 of the internal data storage block 309. The software application 333 that is stored in the ROM 360 can be updated when required from a computer readable medium such as the portable data storage medium 325. The software application 333 can be loaded into and executed by the processor 305. In some instances, the processor 305 may execute software instructions that are located in the RAM 370. Software instructions may be loaded into the RAM 370 by the processor 305 creating a copy of one or more code modules from the ROM 360 for copying into the RAM 370. Alternatively, the software instructions of one or more code modules may be pre-installed in a non-volatile region of the RAM 370 by a manufacturer. After one or more code modules have been discovered in the RAM 370, the processor 305 may execute software instructions of the one or more code modules.

[0055] In one DDCP arrangement, the software application program 333 is pre-installed and stored in the ROM 360 by a manufacturer, prior to distribution of the scale hub 112. However, in other instances, the software application programs 333 may be supplied to the user encoded on one or more computer readable data storage media (such as 325) and read via the memory interface 306 of Fig. 3A prior to data storage in the internal data storage block 309 or alternately in the portable memory 325.

[0056] The term “computer readable data storage media” refers to any non-transitory tangible data storage medium that participates in providing instructions and / or data to the embedded controller 302 for execution and / or processing. Examples of such computer readable data storage media include magnetic tape, CD-ROM devices, a hard disk drive, a ROM or integrated circuit, a USB memory device, a magneto-optical disk, a flash memory device, or a computer readable card such as a PCMCIA card and the like, whether or not such devices are internal or external of the device 301. A computer readable medium having such software or computer program recorded on it is referred to as a computer program product.

[0057] The second part of the software application programs 333 and the corresponding code modules mentioned above may be executed to implement one or more graphical user interfaces (GUIs) to be rendered or otherwise represented upon the display 318 of Fig. 3A. Through manipulation of the user input devices such as the control buttons 388 which communicates with the user interface module 313, a user of the device 301 and the application programs 333 may manipulate the interface in a functionally adaptable manner to provide controlling commands and / or input to the applications associated with the GUI(s). Other forms of functionally adaptable user interfaces may also be implemented, such as an audio interface utilizing speech prompts output via loudspeakers (not illustrated) and user voice commands input via a microphone (not illustrated).

[0058] Fig. 3B depicts an example functional block diagram of the embedded controller 302 including the processor 305 for executing the DDCP software application programs 333 and the internal data storage block 309. The internal data storage 309 block includes a read only memory (ROM) module 360 and a random-access memory (RAM) module 370. The processor 305 can execute the software application programs 333 which are stored in one or both of the interconnected memories 360 and 370. When the electronic device 301 is initially powered up, a system program (not shown) that is permanently stored in the ROM 360 is executed. The system program that is permanently stored in the ROM 360 is sometimes referred to as “firmware”. Execution of the firmware by the processor 305 may fulfil various functions, including processor management, memory management, device management, data storage management and user interface.

[0059] The processor 305 typically includes a number of functional modules including a control unit (CU) 351, an arithmetic logic unit (ALU) 352, a digital signal processor (DSP) 353 and a local or internal memory comprising a set of registers 354, 356, 357, as well as internal buffer or cache memory 355. One or more internal buses 359 enable communication between these functional modules. The processor 305 typically also has one or more interfaces 358 for communicating with external devices via a system bus 381, as depicted by a line 361.

[0060] The DDCP software application program 333 includes a sequence of instructions 362 through 363 that typically include conditional branch and loop instructions. The software program 333 can also include data, which is used in execution of the software program 333. This data may be stored as part of the instructions (362, . . ., 363) or in a separate location 364 within the ROM module 360 or the RAM module 370.

[0061] The processor 305 is typically provided with the set of instructions (362, . . . , 363), for execution. This set of instructions may be organised into routines, each of which may perform a specific task or handle specific events that occur in the electronic device 301. Typically, the software application program 333 waits for events and upon their occurrence executes the block of code (routine) associated with that event. Events may be triggered in response to input from a user, via the user input devices 388 / 318 of Fig. 3A, as detected by the processor 305. Events may also be triggered in response to other sensors and interfaces in the electronic device 301.

[0062] The execution of a software application comprising a set of the instructions typically requires variables to be read and modified in the course of the execution. Such variables are typically stored in the RAM module 370. The disclosed DDCP method uses input variables 371 that are stored in memory locations 372, 373 in the RAM module 370. The input variables 371 are processed to produce output variables 377 that are stored in memory locations 378, 379 in the memory RAM module 370. The aforementioned processing may produce intermediate variables 374 which may be stored in additional memory locations in locations 375, 376 of the memory RAM module 370. Alternatively, some intermediate variables may only exist in the registers 354, 356, 357 of the processor 305.

[0063] The execution of a software program comprising a sequence of instructions is achieved by the processor 305 carrying out a repeated application of a fetch-execute cycle. The control unit 351 of the processor 305 maintains a register called the program counter, which contains the address in the ROM module 360 or the RAM module 370 of the next instruction to be executed. At the start of the fetch execute cycle, the contents of the memory address indexed by the program counter is loaded into the control unit 351. The instruction thus loaded controls the subsequent operation of the processor 305, causing for example, data to be loaded from the ROM memory module 360 into the processor registers 354, the contents of a register to be arithmetically combined with the contents of another register, the contents of a register to be written to the location stored in another register and so on. At the end of the fetch execute cycle the program counter is updated to point to the next instruction in the system program code. Depending on the instruction just executed this may involve incrementing the address contained in the program counter or loading the program counter with a new address in order to achieve a branch operation.

[0064] Each step or sub-process in the processes of the methods described below is associated with one or more segments of the application program 333 and is performed by repeated execution of a fetch-execute cycle in the processor 305 or similar programmatic operation of other independent processor blocks in the electronic device 301.

[0065] Fig. 10 is an example 1000 of a process flow diagram for performing single and multimodule DDCP system processes. Process steps having solid outlines, such as a decision step 1001, are performed by the processor 305 of the DDCP system executing the DDCP software application 333. Process steps having dashed outlines, such as a step 1034, are performed manually by the user 120. Dashed parallelograms, such as 1028, represent information that is input or output from a process step.

[0066] The process 1000 commences with the decision step 1001 performed by the processor 305 executing the software application 333. If the decision step 1001 receives an “Activate” command from the user 120, either via one of the control buttons 388 or the touch screen 318, then the process 1000 follows a “Y” arrow 1003 from the decision step 1001 to a decision step 1004. If on the other hand the decision step 1001 does not receive an “Activate” command from the user 120, then the process 1000 follows a “N” arrow 1002, in a looping manner, from the decision step 1001 back to the decision step 1001.

[0067] If the step 1004, performed by the processor 305 executing the software application 333, receives a “Single module” command from the user 120 either via one of the control buttons 388 or the touch screen 318, indicating that the user wishes to operate the system in a “Single module” mode previously described in regard to Fig. 8, then the step 1004 confirms the user command by providing a suitable display on the display screen 318 instructing the user 120 to position the coffee storage module 809 on the scale bed 137 and the process 1000 follows a “SINGLE” arrow 1014 from the decision step 1004 to a manual step 1034 in which the user 120 places the coffee storage module 809 on the scale bed 137. The manual step 1034 is labelled “MON” indicating that the user places the module on the scale bed 137. The process 1000 then follows an arrow 1035 from the step 1034 to a decision step 1015.

[0068] If the step 1015, performed by the processor 305 executing the software application 333, receives a “Fill Container” command from the user 120 either via one of the control buttons 388 or the touch screen 318, indicating that the user wishes to fill the coffee storage module 809 just placed on the scale bed 137 with roasted coffee beans, then the step 1015 confirms the user command by a providing a suitable display on the display screen 318 and the process follows a “Y” arrow 1016 from the decision step 1015 to the manual step 1017.

[0069] While the user is manually filling the coffee storage module 809 during the step 1017, the DDCP process follows an arrow 1018 to a step 1020. The step 1020, performed by the processor 305 executing the software application 333, monitors the (increasing) weight of the coffee storage module 809 on the scale bed 137 until the weight remains constant for a period of time greater than a pre-determined threshold indicating that the user 120 has completed the filling operation of the coffee storage module 809 with roasted coffee beans. The weight of the empty coffee storage module, including both the coffee storage module container component 802 and the coffee storage module lid component 801 have previously been measured and recorded at a step 425 during an initial setup process 400 (described hereinafter in more detail with reference to Fig. 4). Accordingly, the step 1020 determines the weight of the added roasted coffee beans and records this weight in a coffee storage module data structure 1028 associated with the coffee storage module in question.

[0070] The following example (Table 1) of the data structure 1028 shows the weight of coffee being 20gm at 8:00am, 20gm is removed from the container at 8:01am triggering an alert 529 (see Fig. 5), and 500gm of coffee is put into the container at 8:02am (see 1011 in Fig. 10).Table 1 - Container becomes empty from removal of beans over time

[0071] The following example (Table 2) of the data structure 1028 shows the weight of coffee being 200 gm at 8:00am, 200gm is removed from the container at 8:01am due to an alert 529 (see Fig. 5) signalling that the coffee is stale, and 500gm of coffee is put into the container at 8:02am (see 1011 in Fig. 10).Table 2 - Freshness Alert: Expired Discard Beans. The user discards the contents of the container

[0072] The data structure 1028 is part of stored system information 406. The process 1000 then follows an arrow 1021 from the step 1020 to a decision step 1022.

[0073] Returning to the step 1015 if the step receives a “Do not Fill Container” command from the user 120, either via one of the control buttons 388 or the touch screen 318, indicating that the user does not wish to fill the coffee storage module 809 with roasted coffee beans but rather to check the status of the stored coffee beans in the coffee storage module 809 or to make a cup of coffee, then the step 1015 confirms the user command by providing a suitable display on the display screen 318 and the process follows a “N” arrow 1019 from the decision step 1015 to the step 1020. The step 1020, performed by the processor 305 executing the software application 333, weighs the coffee storage module 809 and records this weight in the coffee storage module data structure 1028. This weight will reflect the amount of coffee removed from the coffee storage module 809 since the previous time the coffee storage module 809 was placed on the scale bed 137. The process 1000 then follows an arrow 1021 from the step 1020 to the decision step 1022.

[0074] In an alternate DDCP arrangement, if the decision step 1015 determines that the coffee storage module placed on the scale bed 137 in the manual step 1034 is full (ie the weight of the coffee storage module exceeds a predefined threshold) then the process 1000 follows the N arrow 1019 from the step 1015 to the step 1020 without requiring the user to provide an input indicating that the user does not wish to fill the coffee storage module 809 with roasted coffee beans.

[0075] If the decision step 1022, performed by the processor 305 executing the software application 333, receives an “Check Status” command from the user 120, either via one of the control buttons 388 or the touch screen 318, indicating that the user 120 wants to check the status of the roasted coffee beans in the coffee storage module 809, then the process 1000 follows a “Check Status” arrow 1042 from the decision step 1022 to a step 513 in Fig. 5. If on the other hand the decision step 1022 receives a “Make Coffee” command from the user 120, either via one of the control buttons 388 or the touch screen 318, then the process 1000 follows a “Make Coffee” arrow 1023 from the decision step 1022 to a manual step 1024 in which the user 120 removes a desired weight of roasted coffee beans from the coffee storage module 809. This “desired weight of roasted coffee beans” is determined by the user 120 without further information from the DDCP system. While the user is manually removing the desired weight of roasted coffee beans from the coffee storage module 809 in the step 1024, the process 1000 follows an arrow 1038 from the step 1024 to the step 1039. The step 1039, performed by the processor 305 executing the software application 333, monitors the (decreasing) weight of the coffee storage module 809 on the scale bed 137 until the weight remains constant for a period of time greater than a pre-determined threshold indicating that the user 120 has removed the desired amount of roast coffee beans from the coffee storage module 809. The step 1039 then records this weight in the coffee storage module data structure 1028 associated with the coffee storage module in question. The process 1000 then follows the arrows 1025 and 1042 to the step 513 in Fig. 5

[0076] As the user 120 uses the single module DDCP system of Fig. 8 as described in relation to Fig. 10 a successive number of times, data is recorded by the step 1039 into the data structure 1028 which thereby accumulates data which can be represented, for example, in following table (Table 3)Table 3

[0077] The “Weight (gm)” column shows the weight of the container module 809 on successive occasions that the container is placed on the scale bed 137 in the manual step 1034. This information enables the amount of coffee removed by the user 120 in the step 1024 to be determined. This information also enables the DDCP system to estimate the amount of coffee stored in the coffee storage container as any specific time of interest, the average daily consumption of coffee from the coffee storage container, and the days remaining until the coffee storage container will be empty (ie the days remaining until depletion - see Equation (2)) and will require refilling.

[0078] The step 513 (described hereinafter in more detail with reference to Fig. 5), performed by the processor 305 executing the software application 333, prompts the user 120 to input additional information.

[0079] Returning to the step 1004 in Fig. 10 if the step, performed by the processor 305 executing the software application 333, receives a “Multi-module” command from the user 120 either via one of the control buttons 388 or the touch screen 318, indicating that the user wishes to operate the system in a “Multi-module” mode previously described in regard to Fig. 1, then the step 1004 confirms the user command by providing a suitable display on the display screen 318 and the process follows a “MULTI” arrow 1005 from the decision step 1004 to a decision step 1006.

[0080] If the decision step 1006, performed by the processor 305 executing the software application 333, receives an “Initial setup not complete” command from the user 120 either via one of the control buttons 388 or the touch screen 318, indicating that the user wishes to incorporate one or more additional untagged coffee storage modules 101 and / or one or more additional untagged brewing modules into the DDCP system 100 previously described in regard to Fig. 1, then the step 1006 confirms the user command by providing a suitable display on the display screen 318 and the process follows a “N” arrow 1007 from the decision step 1006 to a step 401 in Fig. 4. Importantly, if the user 120 wishes to operate the DDCP system 100 using the plurality 101 of coffee storage modules 102, ..., 103 and / or the plurality 111 of brewing modules 113, ... 117 then the user needs to ensure that all the desired coffee storage modules and all the desired brewing modules are processed using the initial setup mode process 400 (see Fig. 4).

[0081] If the decision step 1006, performed by the processor 305 executing the software application 333, receives an “Initial setup complete” command from the user 120 either via one of the control buttons 388 or the touch screen 318, indicating that the user does not wish to incorporate one or more additional untagged coffee storage modules 101 and / or one or more additional untagged brewing modules into the DDCP system 100 previously described in regardto Fig. 1, then the step 1006 confirms the user command by providing a suitable display on the display screen 318 and the process follows a “Y” arrow 1008 from the decision step 1006 to a decision step 1009.

[0082] If the decision step 1009, performed by the processor 305 executing the software application 333, receives a “Fill specific container” command from the user 120 either via one of the control buttons 388 or the touch screen 318, indicating that the user wishes to fill a specific one of the plurality of tagged coffee storage modules 101 previously described in regard to Fig. 1, then the step 1009 confirms the user command by providing a suitable display on the display screen 318 and the process follows a “Y” arrow 1010 from the decision step 1009 to a manual step 1032 in which the user 120 places the desired tagged coffee storage module on the scale bed 137. The process 1000 then follows an arrow 1033 from the manual step 1032 to a manual step 1011.

[0083] While the user is manually filling the desired tagged coffee storage module during the step 1011, the DDCP process follows an arrow 1029 from the step 1011 to a step 1030. The step 1030, performed by the processor 305 executing the software application 333, monitors the (increasing) weight of the specific coffee storage module until the weight remains constant for a period of time greater than a pre-determined threshold indicating that the user 120 has filled the coffee storage module with roasted coffee beans. The weight of the empty coffee storage module, including both the coffee storage module container component and the coffee storage module lid component have previously been measured and recorded (described hereinafter in more detail with reference to Fig. 4). Accordingly, the step 1030 determines the weight of the added roasted coffee beans and records this weight in the coffee storage module data structure 1028 associated with the specific coffee storage module in question. The process 1000 then follows arrows 1012 and 1037 from the step 1030 to a step 501 in Fig. 5.

[0084] Returning to the decision step 1009, if the step, performed by the processor 305 executing the software application 333, receives a “Do not fill specific container” command from the user 120 either via one of the control buttons 388 or the touch screen 318, indicating that the user does not wish to fill a specific one of the plurality of coffee storage modules 101 previously described in regard to Fig. 1, then the step 1009 confirms the user command by a suitable display on the display screen 318 and the process follows a “N” arrow 1013 from the decision step 1009 to a manual step 1036 in which the user places the desired coffee storage module on the scale bed 137. The process 1000 then follows an arrow 1037 from the step 1036 to the step 501 in Fig. 5.

[0085] Returning to the decision step 1004, if the step 1004, performed by the processor 305 executing the software application 333, receives a “coffee bag” command from the user 120 either via one of the control buttons 388 or the touch screen 318, indicating that the user wishes to operate the system using coffee in the coffee bag without using container modules, then the step 1004 confirms the user command by providing a suitable display on the display screen 318 and the process 1000 follows a “COFFEE BAG” arrow 1041 from the decision step 1004 to a decision step 1101 in Fig. 11.

[0086] Fig. 4 is an example 400 of a process flow diagram for performing initial setup of modules used in a multi-module DDCP system.

[0087] The process 400 commences with a start step 401, performed by the processor 305 executing the software application 333. The process 400 then follows an arrow 402 from the start step 401 to a step 403. The step 403, performed by the processor 305 executing the software application 333, receives previously stored system information 406.

[0088] The stored system information can include instructions for the initial setup mode process 400 such as the following. “If initialising a storage container module component, make sure the storage container module component is empty. Container and lid components are to be processed separately. If initialising a brewing equipment module component proceed. Select a blank RFID tag. Place the blank tag on the scale bed RFID reader. Wait for confirmation that the tag has been read. Attach the tag to the module component. If initialising brewing equipment enter the equipment type. Optionally add equipment nickname. If initialising a container component add nickname”.

[0089] The step 403 then displays, as depicted by a dashed arrow 404, on the display screen 318, initial instructions 405 for the user 120. If the module to be processed is a coffee storage module 101 the instructions are to process the corresponding container and lid components separately, and to ensure that the container is empty. If the module to be processed is a brewing module 111 the instructions are to process brewing module components separately.

[0090] The process 400 then follows an arrow 408 from the step 403 to a manual step 409 at which the user 120 places a blank tag (which may be an RFID tag, an optical tag, or another electronically readable tag) on the scale bed 137 so that the tag information 442 can be read by the tag reader 387. While the user 120 is manually placing the tag on the scale bed during the step 409, the process 400 follows an arrow 410 to a step 411. The step 411, performed by the processor 305 executing the software application 333, monitors the tag reader 387 until the tag identifier is successfully read. The step 411 then displays, as depicted by a dashed arrow 412, the tag identifier 413 and optionally instructions for the following manual step 415. The step 411 also adds the tag identifier 413, as depicted by a dashed arrow 437, to the stored system information 406. The process 400 then follows an arrow 414 from the step 411 to a manual step 415.

[0091] In the manual step 415 the user 120 provides, as depicted by a dashed arrow 416, the additional information 417 specified in the displayed information 413 relating to the module being processed such as the module type (eg coffee storage module storage component, or portafilter) and optionally a label (eg Peter’s container). While the user 120 is manually providing the additional information 417 during the manual step 415, the process 400 follows an arrow 418 to a step 419. The step 419, performed by the processor 305 executing the software application 333, monitors manual data entry being performed in the step 415 until the specified additional information has been successfully entered. The step 419 then associates the additional information with the tag identifier 413 of the tag being presently processed and adds, as depicted by a dashed arrow 436, the additional information to the stored system information 406, associating the additional information 417 with the tag identifier 413. The process 400 then follows an arrow 420 from the step 419 to a manual step 421.

[0092] In the manual step 421 the user 120 attaches the tag being processed to the module being processed (eg the coffee storage module storage component). Once the tag has been attached to the module being processed (eg the coffee storage module storage component), the process 400 follows an arrow 422 from the step 421 to a manual step 423. In the manual step 423 the user 120 places the tagged module on the scale bed 137 and the scale hub 112 receives, as depicted by a dashed arrow 445, the tagged module ID 444 which can be one tag ID or a plurality of complimentary tag IDs if module comprises a plurality of complimentary module components. If the module comprises a plurality of complimentary module components the plurality of complimentary tag IDs are associated with the module in the stored system information 406. While the user 120 is manually placing the tagged module on the scale bed 137, the process 400 follows an arrow 424 to a step 425. The step 425, performed by the processor 305 executing the software application 333, monitors the weight registered by the weight sensor 385 which isoperatively coupled to the scale bed 137 until the weight reading stabilises, indicating that the tagged module is properly located on the scale bed 137. The step 425 then measures the weight of the tagged module. The process 400 then follows an arrow 426 from the step 425 to a step 427.

[0093] The step 427, performed by the processor 305 executing the software application 333, displays, as depicted by a dashed arrow 428, the tag identifier, the weight of the module, the type of the module (eg coffee storage module storage component), and the module label 429 (eg Peter’s container) on the display screen 318. The step 427 also stores, as depicted by a dashed arrow 438, the aforementioned information 429 in the stored system information 406. The process 400 then follows an arrow 430 from the step 427 to a decision step 431. The step 431 displays, as depicted by a dashed arrow 432, instructions 433 to the user on how to process a single component module and multicomponent modules comprising complimentary components.

[0094] If the decision step 431, performed by the processor 305 executing the software application 333, receives a “another module component” command from the user 120 either via one of the control buttons 388 or the touch screen 318, indicating that the user wishes to apply the initialisation process to another module, then the process 400 follows a dashed “Y” arrow 435 from the decision step 431 to a manual step 440 in which the user removes the module presently on the scale bed 137. The manual step 440 has a “MOFF” label, indicating that the user removes the module in question from the scale bed in this step. The process 400 then follows an arrow 441 from the manual step 440 to the manual step 409.

[0095] If, however, the decision step 431 does not receive a “another module component” command from the user 120 either via one of the control buttons 388 or the touch screen 318, indicating that the user does not wish to apply the initialisation process to another module, then the process 400 follows a “N” arrow 434 from the decision step 431 to a manual step 439. In the manual step 439 the user 120 removes the module presently on the scale bed 137. The process 400 then follows an arrow 1043 from the manual step 439 to the step 1009 in Fig. 10.

[0096] Considering the step 431 if only one of two complimentary storage module components have been processed, then the process 400 follows the Y arrow 435 to process the complimentary storage module component, ie the storage lid / storage container if the present storage module component is storage container / storage lid. If both complimentary storage module components have been processed, or if the module being processed is a single component brewing equipment module, then the process 400 follows the N arrow 434 as no further information is needed from user. If the brewing equipment module has more than 1 module and only one has been processed, then the process 400 follows the Y arrow 435 to process the complimentary brewing module component.

[0097] Fig. 5 is an example 500 of a process flow diagram for a coffee storage mode process used in both single-module and multi-module DDCP systems. The process 500 commences with a start step 501 which may be entered from a step 927 via an arrow 930 in Fig. 9, from a step 1036 via an arrow 1037 in Fig. 10, or from a step 1101 via an arrow 1102 in Fig. 11.

[0098] The process 500 commences with a start step 501, performed by the processor 305 executing the software application 333. The process 500 then follows an arrow 502 from the start step 501 to a step 503. The step 503, performed by the processor 305 executing the software application 333, reads, if the module in question has a plurality of complimentary module components, the plurality of tag identifiers associated with the complimentary components of the coffee storage module placed on the scale bed 137 in one of the manual steps 1032, 1034, 1036 in Fig. 10 It is noted that the module in question may have a single component in which case themodule is associated with a single tag. Alternately, the module in question may have a plurality of complimentary module components in which case the module is associated with a corresponding plurality (ie “set”) of tags. The process 500 then follows an arrow 504 from the step 503 to a step 505. The step 505, performed by the processor 305 executing the software application 333, retrieves as depicted by a dashed arrow 506, based upon the one or more tag identifiers read by the step 503, information 507 from the stored system information 406. The information 507 typically includes the weights of the empty coffee storage module complimentary components and the weight record for the coffee storage module as depicted above in Table 3.

[0099] The process 500 then follows an arrow 508 from the step 505 to a step 509. The step 509, performed by the processor 305 executing the software application 333, determines and displays, as depicted by an arrow 510, on the display screen 318 data 511 for the coffee storage model as shown, for example, in the following table (Table 4).Table 4

[0100] In one DDCP arrangement the data 511 includes Tag IDs of storage module complimentary components, empty storage module weight, current storage module weight (including weight of contents) and removed weight from previous reading.

[0101] The process 500 then follows an arrow 512 from the step 509 to a step 513. The step 513 may also be also entered from a step 1022 in Fig. 10 via an arrow 1042. The step 513, performed by the processor 305 executing the software application 333, prompts the user 120 to provide additional information for the roasted coffee beans in the coffee storage module provided that (A) the coffee storage module has been filled according to the step 1017 in Fig. 10 and (B) no coffee has been removed from the coffee storage module (ie the step 1022 in Fig. 10 has received from the user, either via one of the control buttons 388 or the touch screen 318, a “Check Status” command). The step 513 prompts the user by displaying on the display screen 318 suitable directions for the user 120.

[0102] The process 500 then follows an arrow 514 from the step 513 to a manual step 515. If the conditions (A) and (B) noted above are TRUE, and the prompt displayed by the step 513 on the display screen 318 directs the user 120 to provide additional information, the user will provide information 517, as depicted by a dashed arrow 516, which typically includes the Brand, the type of roast and flavour profile, the roast date, a label for the roasted coffee beans in the coffee storage module (eg Pete’s coffee), the type of container used in the coffee storage module placed by the user on the scale bed 137 in one of the steps 1032, 1036 in Fig. 10 (as the type of the coffee storage module container component and the type of coffee storage module lid component will impact the freshness profile (depicted in Figs, 13, 14 and 15) and the freshness parameter 523 output by the step 521 in Fig. 5).

[0103] In another DDCP arrangement the step 513 may also prompt the user to specify (A) whether the coffee storage module (or the coffee storage bag) is to be permanently stored inone of three storage temperature profile environments namely (i) at ambient temperature (eg on a shelf in a pantry or kitchen) or (ii) in a refrigerator, or (iii) in a freezer, or (B) whether the coffee storage module is to be movably stored among (i) ambient temperature (eg on a shelf in a pantry or kitchen) or (ii) in a refrigerator, or (iii) in a freezer. It is noted that other DDCP arrangements may use a greater number of storage temperature profile environments.

[0104] The process 500 then follows an arrow 518 from the step 515 to a step 519. The step 519, performed by the processor 305 executing the software application 333, receives the additional information 517 provided by the user 120 in the step 515 and stores the information, as depicted by a dashed arrow 537, in the data structure 1028. The process 500 then follows an arrow 520 from the step 519 to a step 521. The step 521, performed by the processor 305 executing the software application 333, reads the necessary information from the stored system information 406, and determines and displays, as depicted by a dashed arrow 522, information 523 relating to the freshness parameter of the roasted coffee beans in the coffee storage module, and the days remaining until the roasted coffee beans in the coffee storage module are used up given the historic usage pattern. The step 521 also determines if any alerts are triggered by the information for the roasted coffee beans in the coffee storage module.

[0105] The step 521 determines the information 523 relating to the freshness parameter of the roasted coffee beans in the coffee storage module as set out below.

[0106] In one DDCP arrangement, a control signal (not shown) based upon the value of the freshness parameter 523 (ie based upon the flavour intensity) determined by the step 521 can be communicated to the coffee grinder 109 if that coffee grinder 109 has an electronic signal input port (such as a digital communication interface) in order to control the grinder setting of the coffee grinder responsive to the value of the freshness parameter.

[0107] Thus, for example, the coffee grinder 109 can be directed to grind the roasted coffee beans that are removed from the container at the step 632 in Fig. 6 and input into the coffee grinder to a smaller particle size as the freshness parameter value decreases (ie as the freshness of the coffee beans decreases). This is depicted according to one example in the following Table 6Table 6

[0108] The above Table 6 links the Freshness Quality Ratings for Roasted Coffee Beans (Original-Ambient-v2) to suggested grind size adjustments for espresso.

[0109] Baseline Peak freshness is anchored at 250-270 pm ground coffee particle size (D50) for medium roast.

[0110] D50 refers to the median particle size, meaning 50% of ground coffee particles are smaller and 50% are larger.

[0111] Adjustments are expressed as target D50 values to maintain consistent extraction quality. Values shown here correspond to light, medium, and dark roasts stored at ambient 20 °C.

[0112] For the case where the coffee is to be permanently stored at ambient temperature a comprehensive model has been developed to represent the degassing and staling process of light, medium, and dark roasted Arabica coffee beans over time stored in optimum conditions of an airtight, light-proof coffee storage module at 20°C. The same approach can be used to modify the model to account for other types of coffee beans, other types of coffee storage modules, ie coffee storage modules which are not light-proof or air-tight. By categorizing the quality of the coffee into five ratings — Degassing, Peak, Good, Fair, and Stale - this model provides a quantitative method for determining and displaying the information 523 relating to the freshness parameter of the roasted coffee beans in the coffee storage module.Table 5: Freshness Conditions by Roast Level

[0113] This model employs exponential decay functions identified by the inventor to simulate the degradation of flavour intensity, with decay constants tailored to light, medium, and dark roast types.

[0114] Accordingly, the value of the freshness parameter (also referred to as the flavour intensity) reduces with time elapsed after the degassing time as depicted in equation (1), where the degassing time commences after the roast date.

[0115] Information has been identified relating to day ranges for degassing and each freshness category. Table 5 reflects this data, showing that while the freshness periods for light, medium, and dark roasts vary. A clear trend is observable, as depicted in Figs, 13, 14 and 15 for freshness vs time for various roasts at various storage profile temperatures.

[0116] A line of best fit is applied to the identified data to closely match the identified data. An exponential function has been found to provide the closest fit with the highest R2values, as shown in Figs, 13, 14 and 15. The corresponding exponential coefficients for the trend lines are displayed on the plot. These coefficients are used to calculate and determine coffee freshness by accounting for the number of days since roasting and degassing.Exponential Decay Functions:

[0117] The general form of the exponential decay function used is shown in equation (1) as follows:Flavour Intensity=5 x e-kt( 1 )• t is the elapsed time in days after the degassing time.• k is the decay constant, which varies for different roast level (ie roast type).Decay constants derived from the identified data are as follows:1. Light Roast: o Decay Constant (k): 0.0232. Medium Roast: o Decay Constant (k): 0.0273. Dark Roast: o Decay Constant (k): 0.03Examples of the freshness profiles are depicted in graphical form in Figs, 13, 14 and 15 for freshness vs time for various roasts at various storage profile temperatures.

[0118] If a specific roast type is not provided at the step 515 in Fig. 5 then the decay constant k assumes a default value which is typically the mean value of the decay constants for the light, medium and dark roasts ie k = 0.0267. The default value for the decay constant k can assume other values as well.

[0119] The step 521 determines the information 523 relating to the days remaining until the roasted coffee beans in the coffee storage module are used up given the historic usage pattern as set out below. The same approach can be used to modify the model to account for other types of coffee beans, other types of coffee storage modules, ie coffee storage modules which are not light-proof or air-tight and other temperatures.

[0120] The DDCP system monitors and memorizes coffee weight over time (for example see the steps 1020, 1039, 1030 in Fig. 10, and the steps 634 and 1234 in Figs. 6 and 12 respectively), allowing it to display the number of Days Remaining Before the coffee is Depleted (referred to as Days Remaining Until Depletion) and may automatically order more coffee before it runs out based upon the amount of coffee remaining in the container and / or the value of the freshness parameter.

[0121] In one DDCP arrangement the relevant equation for determining Days Remaining Until Depletion is as follows:D=W / C (2) where:• W: Stored Coffee Weight - Represents the amount of coffee currently stored.• C: Average Daily Consumption - Represents the average amount of coffee consumed daily.• D: Days Remaining Until Depletion - Represents the number of days left before the coffee supply is exhausted.

[0122] In one DDCP arrangement re-ordering can be performed according to a time re-order threshold according to the following equation (3):Re-order when D <= TROT (3)

[0123] In another DDCP arrangement re-ordering can be performed according to a freshness reorder threshold according to the following equation (4):Re-order when FP <= FROT (4)

[0124] In another DDCP arrangement re-ordering can be performed according to a time-or- freshness re-order threshold according to the following equation (5):Re-order when earliest of following occurs D <= TROT or FP <= FROT (5)

[0125] For the case where the coffee is to be permanently stored in one of three temperature environments namely (i) at ambient temperature (eg on a shelf in a pantry or kitchen) or (ii) in a refrigerator, or (iii) in a freezer, or (B) where the coffee storage module is to be movably stored among (i) ambient temperature (eg on a shelf in a pantry or kitchen) or (ii) in a refrigerator, or (iii) in a freezer another comprehensive model has been developed as follows (curves of coffee freshness vs time for various storage profile temperatures and roasts are shown in Figs, 13, 14 and 15).Freshness Quality Ratings for Roasted Arabica Coffee Beans by Storage Temperature: 20 °C, 4 °C, -18 °C

[0126] The following framework can be used for modelling coffee freshness over time across three storage temperatures: 20 °C (Room Temperature), 4 °C (Fridge), and -18 °C (Freezer). Freshness is expressed on a 0-5 scale (5=Peak, 4=Good, 3=Fair, 2=Stale) and modelled as an exponential decay F(t) = 5 eA(-k t). The data indicates ~1.5x slower degradation at 4 °C and ~3.3* slower at -18 °C versus ambient. Now described are the resulting freshness bands and the calibrated decay constants (k) for light, medium and dark roasts.

[0127] Definitions & Assumptions• Freshness categories: Peak=5, Good=4, Fair=3, Stale=2 and below.• Roast levels: Light, Medium, Dark.• Storage conditions: airtight, light-proof container; temperatures assessed at 20 °C, 4 °C, and -18 °C.

[0128] Method (Model & Fitting)

[0129] Model: F(t) = 5 eA(-k t), where F(t) is freshness on a 0-5 scale and t is days elapsed. Band boundaries correspond approximately to scores 5^4^3^2. For k, the ‘degassing- eliminated’ approach is used: set t=0 at the first day of Peak and compute k from the start of Stale using k = ln(5 / 2) / t_stale.

[0130] Example (Medium, 20 °C): t stale = 41 - 8 = 33 k = ln(5 / 2) / 33 = 0.0278 day1.

[0131] Formula & Notation (Short)Model: F(t) = 5 eA(-k t) — F(t) freshness (0-5), t days since start of Peak, k in day '.Calibrating k: at Stale start (F=2): k = ln(5 / 2) / t_stale.Degassing shift: t = (days after roast) - start-of-Peak; start-of-Peak: Light=12, Medium=8, Dark=6.Units: time=days; temperature=°C; k=day '; use eA{-k t} with a minus sign.Band mapping: Peak=5, Good=4, Fair=3, Stale=2 and below.

[0132] Curve-fitting setup (degassing eliminated): For decay-curve calculations using y = 5 eA(-k t), we standardise time by setting t = 0 at the start of Peak for each roast (Light: day 12; Medium: day 8; Dark: day 6). This shifts all boundaries by subtracting 12 / 8 / 6 days respectively. We then compute k from y(0) = 5 and y = 2 at t = t_stale via k = ln(5 / 2) / t_stale. All graphs in this document were produced using this method.

[0133] Results: 20 °C (Room Temperature)Table 9 — Decay Constants (k) at 20 °C

[0134] Results: 4 °C (Fridge)Table 10A — Freshness Conditions by Roast Level at 4 °C (with Degassing)Table 10B — Model Inputs at 4 °C (degassing eliminated; single time per band)Table 11 — Decay Constants (k) at 4 °C

[0135] Results: -18 °C (Freezer)Table 12A — Freshness Conditions by Roast Level at -18 °C (with Degassing)Table 12B — Model Inputs at -18 °C (degassing eliminated; single time per band)Table 13 — Decay Constants (k) at -18 °C

[0136] The process 500 then follows an arrow 524 from the step 521 to a decision step 525. If the decision step 525, performed by the processor 305 executing the software application 333, receives an “ALERT” signal from the step 521, indicating that an alert should be provided to the user 120, then the process 500 follows a “Y” arrow 526 from the decision step 525 to a step 527. The step 527, performed by the processor 305 executing the software application 333, displays, as depicted by a dashed arrow 528, an alert 529 on the display screen 318. The process 500 then follows an arrow 530 from the step 527 to a decision step 532. Returning to the decision step 525, if the step does not receive an “ALERT” signal from the step 521, then the process 500 follows a “N” arrow 531 to the decision step 532.

[0137] If the decision step 532, performed by the processor 305 executing the software application 333, receives a “SINGLE CONTAINER” signal from the decision step 1004 in Fig. 10, indicating that the user has elected the single container operating mode, then the process 500follows a “Y” arrow 533 from the decision step 532 to a stop step 536. Returning to the decision step 532, if the step receives a “MULTI-CONTAINER” signal from the decision step 1004 in Fig- 10, then the process 500 follows a “N” arrow 601 from the decision step 532 to a decision step 538. The decision 538, performed by the processor 305 executing the software application 333, displays, as depicted by a dashed arrow 541, a message 542 on the display screen 318 asking the user to select a “USER-SELECTION-BASED” dispense mode process or an “EQUIPMENT-SELECTION BASED” dispense mode process. If the decision step 538, performed by the processor 305 executing the software application 333, receives a “USERSELECTION-BASED” signal from the user, then the process 500 follows a “U” arrow 539 from the decision step 538 to a step 602 in Fig. 6. If on the other hand the decision step 538, performed by the processor 305 executing the software application 333, receives a “EQUIPMENT-SELECTION-BASED” signal from the user, then the process 500 follows a “E” arrow 540 from the decision step 538 to a step 1202 in Fig. 12.

[0138] Fig. 6 is an example 600 of a process flow diagram for a user-selection based (also referred to as user-guided) dispense mode process used in a multi-module DDCP system. In this arrangement the user manually selects a desired brewing style from a displayed list of available brewing styles, and this selection triggers identification of the appropriate brewing modules and recipes by the DDCP system. The DDCP system then prompts the user with relevant actions, adjusts the user interface, brewing recipe and workflow accordingly and logs the interaction.

[0139] As described with reference to Fig. 3A the process 600 may be implemented as one or more interoperable software application programs 333 that can be executed by the embedded controller 302. The steps of the process 600 are carried out by instructions (such as 362 in Fig. 3B) in the software applications 333 that are performed by the embedded controller 302. In one arrangement, implementation of the process steps 602, 608, 610, 616, 618, 624, 626, 628, 634, 640, 646 and 651, and the information in the dashed parallelograms 603, 656, 658, 612, 620, 661, 630, 636, 642, 649, 662 and 653, which represent information that is input or output from corresponding process step, are logged by storing the relevant information in the stored system information 406 for later use.

[0140] The process 600 is entered via an arrow 539 from the step 538 in Fig. 5 to a step 602, performed by the processor 305 executing the software application 333. The step 602 displays, as depicted by a dashed arrow 665 on the display screen 318, a list of the various brewing styles available 603 namely Espresso, Pour-over, French Press / Plunger, Drip, Percolator Aero Press, Cold Brew and so on.

[0141] Some of the brewing styles are described in the following paragraphs.Pour Over

[0142] Pour over coffee involves manually processing the ground coffee with water by pouring hot water over ground coffee in a filter, which is typically placed in a dripper over a carafe or mug. The water passes through the coffee grounds and filter, extracting flavors and oils before dripping into the container below. This method allows for precise control over the water temperature, flow rate, and extraction time, resulting in a flavoured clean, balanced cup of coffee with distinct flavor clarity. Specific types / brands of common pour over devices include the Hario V60, Chemex, and Kalita Wave.Aeropress

[0143] The Aeropress is a versatile and innovative coffee maker that processing the ground coffee with water by using air pressure to push hot water through coffee grounds, producing a flavoured clean and strong cup of coffee. The process involves adding medium-fine groundcoffee and hot water to the Aeropress chamber, stirring, and then pressing the mixture through a filter into a cup. The steeping time is short, typically around one minute, making it a quick brewing method.French Press / Plunger

[0144] The French Press, also known as a plunger pot, is a simple and effective brewing method that involves processing the ground coffee with water by steeping coarsely ground coffee in hot water for about four minutes before pressing a metal or plastic plunger through the coffee grounds to separate them from the brewed coffee. This immersion method allows for a full extraction of the coffee's oils and flavors, resulting in a flavoured rich, full-bodied cup of coffee. The French Press is favored for its straightforward process and the robust, flavorful coffee it produces.Cold Brew

[0145] Cold brew coffee is made by processing the ground coffee with water by steeping coarsely ground coffee beans in cold or room temperature water for an extended period, usually between 12 to 24 hours. This slow extraction process produces a coffee concentrate that is low in acidity and has a smooth, rich flavor profile. After steeping, the coffee grounds are filtered out, leaving behind a flavoured concentrate that can be diluted with water, milk, or used as a base for various coffee drinks.

[0146] Returning to the process 600, the process 600 then follows an arrow 605 from the step 602 to a manual step 606. In the manual step 606 the user 120 selects, via one or more of the user interface peripherals comprising control buttons 388 and the display318, the selected brewing style. The process 600 then follows an arrow 607 from the manual step 606 to a step 608. In the step 608, performed by the processor 305 executing the software application 333, the DDCP system 100 receives, as depicted by a dashed arrow 657, information 656 specifying the brewing style selected by the user 120 in the manual step 606 and stores this information 65 in the data structure 1028 which forms part of the stored system information 406. The process 600 then follows an arrow 609 from the step 608 to a step 610.

[0147] The step 610 displays, as depicted by a dashed arrow 611 on the display screen 318, the number of cups 612 which the user 120 may elect namely 1-15 cups for example. The process 600 then follows an arrow 613 from the step 610 to a manual step 614. In the manual step 614 the user 120 selects, via one or more of the user interface peripherals comprising the control buttons 388 and the display318, the desired number of cups. The process 600 then follows an arrow 615 from the manual step 614 to a step 616. In the step 616, performed by the processor 305 executing the software application 333, the DDCP system 100 receives, as depicted by a dashed arrow 659, the information 658 specifying the number of cups selected by the user 120 in the manual step 614 and stores this information 658 in the data structure 1028 which forms part of the stored system information 406. The process 600 then follows an arow 617 from the step 616 to a step 618.

[0148] The step 618 displays, as depicted by a dashed arrow 619 on the display screen 318, the strength options 620 which the user 120 may elect namely 1 :2 - 1 :20 meaning 1 part coffee to 10 parts water (weaker) to 1 part coffee to 10 parts coffee (stronger) for example. The process 600 then follows an arrow 621 from the step 618 to a manual step 622. In the manual step 622 the user 120 selects, via one or more of the user interface peripherals comprising the control buttons 388 and the display318, the desired strength. The process 600 then follows an arrow 623 from the manual step 622 to a step 624. In the step 624, performed by the processor 305 executing the software application 333, the DDCP system 100 receives, as depicted by a dashed arow 660, the information 661 specifying the strength selected by the user 120 in the manual step 622 andstores this information 661 in the data structure 1028 which forms part of the stored system information 406. The process 600 then follows an arow 625 from the step 624 to a step 626.

[0149] In the step 626, performed by the processor 305 executing the software application 333, the DDCP system 100 determines a specific brewing recipe depending upon the brewing style, the number of cups, and the strength parameters selected by the user in the steps 606, 614 and 622 respectively.

[0150] An example of a specific brewing recipe determined by the step 626 (see 630 which is displayed by a following step 628) is as follows (see APPENDIX II for other examples):Brewing RecipeRecipe Time: 3:00 minCoffee: 14.7gTotal Water: 250g at Temp - 97°CBloom Size: 44.1g of water over 17.64 secondsFlowrate Target (Bloom): 2.5 grams per secBloom Time: 1 minRemaining Time: 2 minRemaining Pour: 205.9g of water over 41.18 secFlowrate Target (Post-Bloom): 5 grams per second

[0151] Table 6 and Table 7 depict typical ranges for brewing recipe parameters for pour over brewing style.

[0152] APPENDIX II provides a number of examples of brewing recipes and brewing instructions.

[0153] The DDCP arrangement provides a generalised method for generating a brewing recipe for the user-based and accessory-based dispense mode processes depicted in Fig. 6 and Fig. 12 respectively. This is based upon the brewing style (selected by the user in the user-guided process depicted in Fig. 6 and based upon the selected brewing equipment placed on the scale bed in the accessory-guided process depicted in Fig. 12), the number of cups, and the strength parameters selected by the user in the steps 614 and 622 respectively in the user-guided process of Fig. 6, and the number of cups, and the strength parameters selected by the user in the steps 1214 and 1222 respectively in the accessory-guided process of Fig. 12, as follows:

[0154] Recipe Generation with User InputsCup Definition: 1 cup = 250 mL (~ 250 g) water.

[0155] User Inputs• Brewing Method (Not required when “Accessory Guided”)• Number of cups (1-8 cups, scalable beyond)• Strength (brew ratio 1 : 10 to 1 :20)

[0156] Computation (From Inputs to Full Recipe)Given inputs cups (c) and ratio (r), compute:1) Total water W = 250 c (g)2) Coffee dose D = W / r (g)3) Bloom pour water B = min(3 D, W) (g)4) Bloom pour duration t_b_pour = B / 2.5 (s); Bloom time total t_b = 60 s; Bloom wait = t_b - t_b_pour5) Main pour water R = W - B (g)6) Main pour duration t_m_pour = R / 5 (s); Main phase total t_m = 120 s; Main wait = t_m - t_m_pour7) Total recipe time T = t_b + t_m (s)Note: All water values are expressed in grams, equivalent to millilitres for water.

[0157] Default Settings (Values are Different for Each Brewing Method)

[0158] Default Settings - Pour Over• Water temperature: 97 °C• Bloom pour water: 3. Ox coffee dose• Bloom flowrate: 2.5 g / s; Bloom time (total): 60 s• Main pour flowrate: 5.0 g / s; Main phase time (total): 120 s• Total brew time: 3:00 min

[0159] Default Settings - AeroPress• Water temperature: 95 °C• Bloom pour water: 3. Ox coffee dose• Bloom flowrate: 2.5 g / s; Bloom time (total): 45 s• Main pour flowrate: 5.0 g / s; Main phase time (total): 75 s• Total brew time: 2:00 min

[0160] Default Settings - French Press• Water temperature: 93 °C• Bloom pour water: 3. Ox coffee dose• Bloom flowrate: 3.0 g / s; Bloom time (total): 45 s• Main pour flowrate: 3.0 g / s; Main phase time (total): 195 s• Total brew time: 4:00 min

[0161] Default Settings - Cold Brew• Water temperature: Room temperature• Bloom pour water: 3. Ox coffee dose• Bloom flowrate: 3.0 g / s; Bloom pour duration: 1 :23 min• Main pour flowrate: 3.0 g / s; Main phase time (steep): 11-23 hours• Total brew time: 12-24 hours

[0162] Example RecipesExample Recipe - Pour Over 1 Cup 1 : 17 RegularRecipe Time: 3:00 minCoffee: 14.7gTotal Water: 250g at 97 °CBloom pour water: 44.1g over 17.64 sFlowrate Target (Bloom): 2.5 g / sBloom Time: 1 minMain pour water: 205.9g over 41.18 sFlowrate Target (Main Pour): 5 g / sTotal Brew Time: 3:00 minBrewing Instructions (Fig.7 Steps) - Pour OverBLOOM POUR• Pour 44.1g bloom pour water.• Start timer: count to 1 :00 min.• Display elapsed bloom time and flow rate.• Alerts: 1 :00 min reached, 44.1g poured.MAIN POUR• Pour 205.9g main pour water at 5 g / s.• Display elapsed main pour time.• Alerts: 205.9g poured, 3:00 min reached.• Stop pour.

[0163] Returning to Fig. 6 the process 600 then follows an arrow 627 from the step 626 to a step 628.

[0164] The step 628 displays, as depicted by a dashed arrow 629 on the display screen 318, the specific brewing recipe 630 determined by the step 626.

[0165] In one simple pour over example, if the user selects a single cup at the step 614 and a “normal” strength at the step 622, then the brewing recipe will contain the “normal / recommended” parameter values from Table 6 and Table 7 as appropriate.

[0166] More generally, the DDCP system will select at the step 626 a specific brewing recipe 630 based on (i) the brewing style 656 selected by the user in the step 606, the brewing module associated with the selected brewing style 656 (the association between brewing styles, brewing recipes and brewing equipment is pre-loaded into the stored system information 406 when the DDCP system is manufactured or when the DDCP system software 333 is updated), the number of cups 658 selected by the user in the step 614, the strength 661 selected by the user in the step 622, and the brewing recipe parameter values shown in Tables 6 and 7. However, the user can adjust the brewing recipe parameter values depicted on the display screen 318 as depicted by a dashed looping arrow 664.

[0167] After the user is satisfied with the brewing recipe parameter values, the process 600 then follows an arrow 631 from the step 628 to a manual step 632. In the manual step 632 the user 120 removes the weight of coffee specified by the brewing recipe 630 displayed by the step 628 on the display screen 318 from the coffee storage module that was placed on the scale bed 137 by the user 120 in one of the manual steps 1032, 1036 in Fig. 10. The process 600 then follows an arow 633 from the manual step 632 to a step 634.

[0168] The step 634 determines and displays, as depicted by a dashed arrow 635 on the display screen 318, the weight of roasted coffee beans 636 removed in the manual step 632. The process 600 then follows an arrow 637 from the step 634 to a manual step 638. In the manual step 638 the user 120 removes the coffee storage module that was placed on the scale bed 137 by the user 120 in one of the manual steps 1032, 1036 in Fig. 10. The process 600 then follows an arow 639 from the manual step 638 to a step 640.

[0169] The step 640 determines and displays, as depicted by a dashed arrow 641 on the display screen 318, a specification 642 of the brewing module associated with the brewing recipe 630 displayed in the step 628 and instructions to the user to place the brewing module on the scale bed 137. The association between brewing styles and brewing equipment (ie the brewing module) is pre-loaded into the stored system information 406 when the DDCP system is manufactured or when the DDCP system software 333 is updated. The process 600 then follows an arow 643 from the step 640 to a manual step 644.

[0170] In the manual step 644 the user 120 places the brewing module specified by the information 642 displayed by the step 640 on the scale bed 137. The process 600 then follows an arow 645 from the manual step 644 to a step 646.

[0171] The step 646 detects (as depicted by a dashed arrow 663) and displays, as depicted by a dashed arrow 648 on the display screen 318, the tag identifier(s) 649 of the brewing module components of the brewing module placed by the user 120 on the scale bed 137 in the manual step 644. The process 600 then follows an arow 650 from the step 646 to a step 651.

[0172] The step 651 displays, as depicted by a dashed arrow 652 on the display screen 318, the weight of coffee 653 specified in the brewing recipe 630 by the step 628 and removed by the user 120 from the coffee storage module in the step 638. The process 600 then follows an arow 654 from the step 651 to a manual step 655.

[0173] In the manual step 655 the user 120 grinds the roasted coffee beans removed from the coffee storage module in the step 632 and adds the specified weight of the ground roasted coffee beans 653 to the brewing module 642 placed on the scale bed 137 by the user 120 in the step 644.

[0174] The process 600 then follows an arow 701 from the manual step 655 to a step 702 in Fig. 7.

[0175] Fig. 12 is an example 1200 of a process flow diagram for an equipment-selection based (also referred to as accessory-guided) dispense mode process used in a multi-module DDCP system. In this arrangement the user selects a desired brewing module from a set of available brewing modules and places the selected module on the scale bed 137. This triggers identification of the appropriate brewing styles and recipes by the DDCP system. The DDCP system then prompts the user with relevant actions, adjusts the user interface, brewing recipe and workflow accordingly and logs the interaction.

[0176] As described with reference to Fig. 3A the process 1200 may be implemented as one or more interoperable software application programs 333 that can be executed by the embedded controller 302. The steps of the process 1200 are carried out by instructions (such as 362 in Fig. 3B) in the software applications 333 that are performed by the embedded controller 302. In one arrangement, implementation of the process steps 1206, 1208, 1210, 1216, 1218, 1224, 1226, 1228, 1234, 1246 and 1251, and the information in the dashed parallelograms 1203, 1256, 1258, 1212, 1220, 1261, 1230, 1236, 1249, 1262 and 1253, which represent information that is input or output from corresponding process step, are logged by storing the relevant information in the stored system information 406 for later use.

[0177] The process 1200 is entered via an arrow 540 from the step 538 in Fig. 5 and proceeds to a manual step 1202. In the manual step 1202 the user 120 selects the desired brewing module and places the brewing module on the scale bed 137. The process 1200 then follows an arrow 1205 from the manual step 1202 to a step 1206. The step 1206 detects and displays, as depictedby a dashed arrow 1265 on the display screen 318, the Tag IDs 1203 of the selected brewing module. The process 1200 then follows an arrow 1207 from the step 1206 to a step 1208.

[0178] The step 1208, performed by the processor 305 executing the software application 333, determines the brewing style that is associated with the brewing module that was placed on the scale bed 137 in the manual step 1202 by the user, using information 1256 that is input to the step 1208 as depicted by a dashed arrow 1257. The information 1256 specifies the association between brewing modules and appropriate brewing styles, recipe parameter ranges and brewing instructions and is part of the stored system information 406.

[0179] The process 1200 then follows an arrow 1209 from the step 1208 to a step 1210. The step 1210 displays, as depicted by a dashed arrow 1211 on the display screen 318, the number of cups 1212 which the user 120 may elect namely 1-15 cups for example. The process 1200 then follows an arrow 1213 from the step 1210 to a manual step 1214. In the manual step 1214 the user 120 selects, via one or more of the user interface peripherals comprising the control buttons 388 and the display318, the desired number of cups.

[0180] The process 1200 then follows an arrow 1215 from the manual step 1214 to a step 1216. In the step 1216, performed by the processor 305 executing the software application 333, the DDCP system 100 receives, as depicted by a dashed arrow 1259, the information 1258 specifying the number of cups selected by the user 120 in the manual step 1214 and stores this information 1258 in the data structure 1028 which forms part of the stored system information 406. The process 1200 then follows an arow 1217 from the step 1216 to a step 1218.

[0181] The step 1218 displays, as depicted by a dashed arrow 1219 on the display screen 318, the strength options 1220 which the user 120 may elect namely 1 :2 - 1 :20 meaning 1 part coffee to 10 parts water (weaker) to 1 part coffee to 10 parts coffee (stronger) for example. The process 1200 then follows an arrow 1221 from the step 1218 to a manual step 1222. In the manual step 1222 the user 120 selects, via one or more of the user interface peripherals comprising the control buttons 388 and the display318, the desired strength. The process 1200 then follows an arrow 1223 from the manual step 1222 to a step 1224. In the step 1224, performed by the processor 305 executing the software application 333, the DDCP system 100 receives, as depicted by a dashed arow 1260, the information 1261 specifying the strength selected by the user 120 in the manual step 1222 and stores this information 1261 in the data structure 1028 which forms part of the stored system information 406. The process 1200 then follows an arow 1225 from the step 1224 to a step 1226.

[0182] In the step 1226, performed by the processor 305 executing the software application 333, the DDCP system 100 determines a specific brewing recipe depending upon the brewing style (associated with the brewing module that was placed on the scale bed 137 in the manual step 1202 by the user), the number of cups, and the strength parameters selected by the user in the steps 1206, 1214 and 1222 respectively.

[0183] In one simple pour over example, if the user selects a single cup at the step 1214 and a “normal” strength at the step 1222, then the brewing recipe will contain the “normal / recommended” parameter values from Table 6 and Table 7 as appropriate.

[0184] More generally, the DDCP system will select at the step 1226 a specific brewing recipe 1230 based on the brewing module that was placed on the scale bed 137 in the manual step 1202 by the user, the number of cups 658 selected by the user in the step 614, the strength 661 selected by the user in the step 622, and the brewing recipe parameter values shown in Tables 6 and 7.However, the user can adjust the brewing recipe parameter values depicted on the display screen 318 as depicted by a dashed looping arrow 664.

[0185] The process 1200 then follows an arrow 1227 from the step 1226 to a step 1228.

[0186] The step 1228 displays, as depicted by a dashed arrow 1229 on the display screen 318, the specific brewing recipe 1230 determined by the step 1226. Brewing recipe parameter values are typically set using predetermined default values by the DDCP system, however the user can adjust the brewing recipe parameter values depicted on the display screen 318 as depicted by a dashed looping arrow 1264.

[0187] After the user is satisfied with the brewing recipe parameter values, the process 1200 then follows an arrow 1231 from the step 1228 to a manual step 1232. In the manual step 1232 the user places the coffee storage module on the scale bed 137 and removes the weight of coffee specified by the brewing recipe 1230 displayed by the step 1228 on the display screen 318 from the coffee storage module. The process 1200 then follows an arow 1233 from the manual step 1232 to a step 1234.

[0188] The step 1234 determines and displays, as depicted by a dashed arrow 1235 on the display screen 318, the weight of roasted coffee beans 1236 removed in the manual step 1232. The process 1200 then follows an arrow 1237 from the step 1234 to a manual step 1238. In the manual step 1238 the user 120 removes the coffee storage module that was placed on the scale bed 137 by the user 120 in the manual step 1232. The process 1200 then follows an arow 1239 from the manual step 1238 to a manual step 1244.

[0189] In the step 1244 the user 120 places the brewing module on the scale bed 137. The process 1200 then follows an arow 1245 from the manual step 1244 to a step 1246.

[0190] The step 1246 detects (as depicted by a dashed arrow 1263) the tag identifier(s) 1262 of the brewing module components of the brewing module placed by the user 120 on the scale bed 137 in the manual step 1244 and displays, as depicted by a dashed arrow 1248 on the display screen 318, the tag identifier(s) 1249 of the brewing module components of the brewing module placed by the user 120 on the scale bed 137 in the manual step 1244. The process 1200 then follows an arow 1250 from the step 1246 to a step 1251.

[0191] The step 1251 displays, as depicted by a dashed arrow 1252 on the display screen 318, the weight of coffee 1253 specified in the brewing recipe 1230 by the step 1228 and removed by the user 120 from the coffee storage module in the step 1238. The process 1200 then follows an arow 1254 from the step 1251 to a manual step 1255.

[0192] In the manual step 1255 the user 120 grinds the roasted coffee beans removed from the coffee storage module in the step 1232 and adds the specified weight of the ground roasted coffee beans 1253 to the brewing module 1242 placed on the scale bed 137 by the user 120 in the step 1244.

[0193] The process 1200 then follows an arow 701 from the manual step 1255 to a step 702 inFig. 7.

[0194] Fig. 7 is an example of a process flow diagram for a brewing mode process used in a multi-module DDCP system. The following description is general, and variations thereof apply to specific brewing styles as described after the general description.

[0195] The process 700 is entered via an arrow 701 from the step 655 in Fig. 6 to a step 702. The step 702, performed by the processor 305 executing the software application 333, determines, from the selected brewing recipe 630 determined by the step 626 (see Fig. 6) brewing instructions 706.

[0196] The process 700 then follows an arrow 703 from the step 702 to a step 704. The step 704, performed by the processor 305 executing the software application 333, displays, as depicted by a dashed arrow 705, on the display screen 318, the brewing instructions 706 as depicted in APPENDIX II. The process 700 then follows an arrow 707 from the step 704 to a manual step 708.

[0197] In the manual step 708 the user 120 starts pouring water from the kettle 119 (see Fig. 1) over the ground roasted coffee in the brewing module that has been placed on the scale bed 137 by the user in the manual step 644 (see Fig. 6). The process 700 then follows an arrow 709 from the manual step 708 to a step 710. In the step 710, performed by the processor 305 executing the software application 333, the DDCP system 100 starts a brewing timer.

[0198] Considering a “Bloom Pour” 713, following activation of the timer by the step 710 the process 700 commences a “bloom pour” and follows an arrow 712 from the step 710 to a step 714. The step 714, performed by the processor 305 executing the software application 333, determines, and displays, as depicted by a dashed arrow 715, on the display screen 318, an elapsed time value 716. The process 700 then follows an arrow 717 from the step 714 to a decision step 718. If the decision step 718, performed by the processor 305 executing the software application 333, determines that the elapsed time determined by the step 714 has exceeded a pre-determined bloom time parameter, then the process 700 follows a “Y” arrow 720 from the decision step 718 to a step 721. If on the other hand the decision step 718 determines that the elapsed time determined by the step 714 has not exceeded the pre-determined bloom time parameter, then the process 700 follows a “N” arrow 719, in a looping manner, from the decision step 718 back to the decision step 718.

[0199] The step 721, performed by the processor 305 executing the software application 333, issues, as depicted by a dashed arrow 722, an alert by displaying an alert message 723 on the display screen 318. This advises the user 120 that the bloom pour time has elapsed and the postbloom pour is about to commence. The process 700 then follows an arrow 724 from the step 721 to a step 739.

[0200] Considering the “Bloom Pour” 713, Following activation of the timer by the step 710 the process 700 also follows an arrow 711 from the step 710 to a step 725. The step 725, performed by the processor 305 executing the software application 333, determines, and displays, as depicted by a dashed arrow 726, on the display screen 318, a flow rate parameter value 727. The process 700 then follows an arrow 728 from the step 725 to a step 729. The step 729, performed by the processor 305 executing the software application 333, determines, and displays, as depicted by a dashed arrow 763, on the display screen 318, a parameter value 762 indicating the accumulated amount of water poured thus far. The process 700 then follows an arrow 730 from the step 729 to a decision step 731.

[0201] If the decision step 731, performed by the processor 305 executing the software application 333, determines that the cumulative amount of water poured thus far equals or exceeds a pre-determined water amount, then the process 700 follows a “Y” arrow 733 from the decision step 731 to a step 734. If on the other hand the decision step 731 determines that the cumulative amount of water poured thus far does not equal or exceed the pre-determined water amount parameter, then the process 700 follows a “N” arrow 732, in a looping manner, from thedecision step 731 back to the decision step 731. The step 734, performed by the processor 305 executing the software application 333, issues, as depicted by a dashed arrow 735, an alert by displaying an alert message 736 on the display screen 318. This advises the user 120 that the bloom pour water amount has been poured and the post-bloom pour is about to commence. The process 700 then follows an arrow 737 from the step 734 to a step 748.

[0202] Considering the “Bloom Pour” 713, the user 120 aims to control the speed of the pour in the manual step 708 so that the bloom time alert 723 and the specified water alert 736 occur as close together in time as possible.

[0203] Following completion of the bloom pour the process 700 commences a “post bloom pour” 738. The step 739, performed by the processor 305 executing the software application 333, determines, and displays, as depicted by a dashed arrow 733, on the display screen 318, an elapsed post-bloom time value 732. The process 700 then follows an arrow 740 from the step 739 to a decision step 741. If the decision step 741, performed by the processor 305 executing the software application 333, determines that the elapsed post-bloom time determined by the step 739 has exceeded a pre-determined post-bloom time parameter then the process 700 follows a “Y” arrow 743 from the decision step 741 to a step 744. If on the other hand the decision step 741 determines that the elapsed post-bloom time determined by the step 739 has not exceeded the pre-determined post-bloom time parameter, then the process 700 follows a “N” arrow 742, in a looping manner, from the decision step 741 back to the decision step 741.

[0204] The step 744, performed by the processor 305 executing the software application 333, issues, as depicted by a dashed arrow 745, an alert by displaying an alert message 746 on the display screen 318. This advises the user 120 that the post-bloom pour has been completed. The process 700 then follows an arrow 747 from the step 744 to a stop step 761.

[0205] Considering the “Post Bloom Pour” 738, as noted above following completion of the bloom pour the process 700 commences the “post bloom pour”. The step 748, performed by the processor 305 executing the software application 333, determines, and displays, as depicted by a dashed arrow 749, on the display screen 318, a flow rate parameter value 750. The process 700 then follows an arrow 751 from the step 748 to a step 752. The step 752, performed by the processor 305 executing the software application 333, determines, and displays, as depicted by a dashed arrow 765, on the display screen 318, a parameter value 764 indicating the accumulated amount of water poured thus far. The process 700 then follows an arrow 753 from the step 752 to a decision step 754.

[0206] If the decision step 754, performed by the processor 305 executing the software application 333, determines that the cumulative amount of water poured thus far equals or exceeds a pre-determined post bloom time water amount then the process 700 follows a “Y” arrow 756 from the decision step 754 to a step 757. If on the other hand the decision step 754 determines that the cumulative amount of water poured thus far does not equal or exceed the predetermined post bloom water amount parameter, then the process 700 follows a “N” arrow 755, in a looping manner, from the decision step 754 back to the decision step 754. The step 757, performed by the processor 305 executing the software application 333, issues, as depicted by a dashed arrow 758, an alert by displaying an alert message 759 on the display screen 318. This advises the user 120 that the post bloom pour water amount has been poured. The process 700 then follows an arrow 760 from the step 757 to the stop step 761.

[0207] In use the user 120 aims to control the speed of the pour in the manual step 708 so that the post-bloom time alert 746 and the specified post-bloom water alert 759 occur as close together in time as possible.

[0208] An example of specific brewing instructions determined by the step 702 (see 706 which is displayed by the following step 704) is as follows (see APPENDIX II for other examples):Pour Over 1 Cup 1:17 RegularBrewing RecipeRecipe Time: 3:00 minCoffee: 14.7gTotal Water: 250g at Temp - 97°CBloom Size: 44.1g of water over 17.64 secondsFlowrate Target (Bloom): 2.5 grams per secBloom Time: 1 minRemaining Time: 2 minRemaining Pour: 205.9g of water over 41.18 secFlowrate Target (Post-Bloom): 5 grams per secondBrewing InstructionsBLOOM POUR• Pour water onto brewing module: Start pouring 44.1g of water.• Start timer: Counting up to 1 :00 min.• Determine / display elapsed bloom time: X of 1 min has elapsed.• Determine and display flow rate: 2.5 grams per sec.• Issue alert: 1 min has elapsed.• Issue alert: 44.1g of water has been poured.POST-BLOOM POUR• Determine / display elapsed post-bloom time: 2:00 min remaining.• Determine and display flow rate: 5 grams per second.• Pour water onto brewing module: Start pouring 205.9g of water.• Issue alert: 2 min has elapsed.• Issue alert: 205.9g of water has been poured.• Stop pour.

[0209] Variations of the brewing mode process 700 for particular brewing styles are described below.

[0210] When the process 700 is applied to the espresso cup 114 and the portafilter 136 / 113 the cup 114 is placed on the scale bed 137 and the scale hub 112 is placed in the espresso machine (not shown) in the step 644 (see Fig. 6), the ground coffee produced in the step 655 is placed in the portafilter 136 / 113 in the step 655 and the portafilter 136 / 113 is inserted into the espresso machine (not shown), the water is poured by the espresso machine through the portafilter into the cup in the step 708, and the remainder of the process 700 proceeds as described above.

[0211] When the process 700 is applied to the pour over carafe 115 a paper filter is placed in a V60 funnel (also referred to as a pour over dripper) which is placed into the pour over carafe 115 and the aforementioned assembly (which is a multi-component brewing module made up of two complimentary brewing module components, both of which are individually tagged with a corresponding electronically readable tag) is placed on the scale bed 137 in the step 644, and ground coffee is placed into the paper filter in the step 655, and water is poured into the paperfilter in the step 708 and the brewed coffee is poured into the cup 114 in the step 761, and the remainder of the process 700 proceeds as described above.

[0212] When the process 700 is applied to the chemex 116 a paper filter is placed into the chemex 116 and the assembly is placed on the scale bed in the step 644 and ground coffee is placed into the paper filter in the step 655, and water is poured into the paper filter in the step 708 and the brewed coffee is poured into the cup 114 in the step 761, and the remainder of the process 700 proceeds as described above.

[0213] When the process 700 is applied to the cold brew carafe assembly 131 / 132 / 133 (which is a multi-component brewing module made up of three complimentary brewing module components, each of which is individually tagged with a corresponding electronically readable tag) the assembly is placed on the scale bed in the step 644 and ground coffee is placed into the assembly in the step 655 and water is poured into the assembly in the step 708 and the brewed coffee is poured into the cup 114 in the step 761, and the remainder of the process 700 proceeds as described above.

[0214] Fig. 9 is an example of a process flow diagram for performing an initial setup process for coffee stored in a coffee bag without using a storage module.

[0215] The process 900 commences with a start step 901, performed by the processor 305 executing the software application 333. The process 900 then follows an arrow 902 from the start step 901 to a step 903. The step 903, performed by the processor 305 executing the software application 333, receives previously stored system information 406.

[0216] The stored system information 406 can include instructions for the initial setup mode process 900 such as the following. “If initialising a full coffee bag containing coffee please proceed. Select a blank RFID tag. Place the blank tag on the scale bed RFID reader. Wait for confirmation that the tag has been read. Attach the tag to the coffee bag. Optionally add coffee bag nickname.”.

[0217] The step 903 then displays, as depicted by a dashed arrow 904, on the display screen 318, initial instructions 905 for the user 120. If the module to be processed is a full coffee bag containing coffee the instructions are to proceed.

[0218] The process 900 then follows an arrow 908 from the step 903 to a manual step 909 at which the user 120 places a blank tag (which may be an RFID tag, an optical tag, or another electronically readable tag) on the scale bed 137 so that the tag information 942 can be read by the tag reader 387. While the user 120 is manually placing the tag on the scale bed during the step 909, the process 900 follows an arrow 910 to a step 911. The step 911, performed by the processor 305 executing the software application 333, monitors the tag reader 387 until the tag identifier is successfully read. The step 911 then displays, as depicted by a dashed arrow 912, the tag identifier 913 and optionally instructions for the following manual step 915. The step 911 also adds the tag identifier 913, as depicted by a dashed arrow 937, to the stored system information 406. The process 900 then follows an arrow 914 from the step 911 to a manual step 915.

[0219] In the manual step 915 the user 120 provides, as depicted by a dashed arrow 916, the additional information 917 specified in the displayed information 913 relating to the coffee bag being processed such as the module type (eg coffee bag) and optionally a label (eg Peter’s bag). While the user 120 is manually providing the additional information 917 during the manual step 915, the process 900 follows an arrow 918 to a step 919. The step 919, performed by theprocessor 305 executing the software application 333, monitors manual data entry being performed in the step 915 until the specified additional information has been successfully entered. The step 919 then associates the additional information with the tag identifier 913 of the tag being presently processed and adds, as depicted by a dashed arrow 936, the additional information to the stored system information 406, associating the additional information 917 with the tag identifier 913. The process 900 then follows an arrow 920 from the step 919 to a manual step 921.

[0220] In the manual step 921 the user 120 attaches the tag being processed to the coffee bag being processed. Once the tag has been attached to the bag being processed, the process 900 follows an arrow 922 from the step 921 to a manual step 923. In the manual step 923 the user 120 places the tagged bag on the scale bed 137 and the scale hub 112 receives, as depicted by a dashed arrow 945, the tagged bag ID 944. While the user 120 is manually placing the tagged bag on the scale bed 137, the process 900 follows an arrow 924 to a step 925. The step 925, performed by the processor 305 executing the software application 333, monitors the weight registered by the weight sensor 385 which is operatively coupled to the scale bed 137 until the weight reading stabilises, indicating that the tagged bag is properly located on the scale bed 137. The step 925 then measures the weight of the tagged bag. The process 900 then follows an arrow926 from the step 925 to a step 927.

[0221] The step 927, performed by the processor 305 executing the software application 333, displays, as depicted by a dashed arrow 928, the tag identifier, the weight of the bag, the type of the bag (ie coffee bag), and the bag label 429 (eg Peter’s bag) on the display screen 318. The step927 also stores, as depicted by a dashed arrow 928, the aforementioned information 929 in the stored system information 406. The process 900 then follows an arrow 930 from the step 927 to step 501 in Fig. 5.

[0222] Table 6 and Table 7 are examples of brewing recipe parameter ranges for the pour over brewing style supported by a particular DDCP system. The brewing recipe parameters are depicted for three examples, namely light roast brew coffee beans for a pour-over brewing style, medium roast brew coffee beans for a pour-over brewing style, and dark roast brew coffee beans for a pour-over brewing style. Clearly a typical DDCP system can support brewing recipe parameter ranges for other roast types, and other brewing styles.

[0223] Each of the aforementioned examples has associated parameters which are “Strength” (which includes a strength range from 1 : 10 to 1 :20), “Water Temperature” (which includes a temperature range from 95degC to lOOdegC), “Bloom Size” (which includes a bloom size range from 2x to 4x), “Bloom Length” (which includes a bloom length range from 30 sec to 2 min), and “Remaining Pour Flow Rate” (which includes a rate range from 5gm / sec to lOgm / sec).

[0224] Table 6 - Brewing Recipe Parameter Value Ranges for pour over brewing style

[0225] Table 7 Brewing Recipe Parameter Value Ranges for pour over brewing style

[0226] Fig. 11 is an example of a process flow diagram fragment for DDCP system processes for coffee in a coffee bag without using storage modules. If the decision step 1101, performed by the processor 305 executing the software application 333, receives an “Initial setup not complete” command from the user 120 either via one of the control buttons 388 or the touch screen 318, indicating that the user wishes to incorporate a coffee bag into the DDCP system, then the step 1101 confirms the user command by providing a suitable display on the display screen 318 and the process follows a “N” arrow 1103 from the decision step 1101 to a step 901 in Fig. 9.

[0227] If on the other hand the decision step 1101, performed by the processor 305 executing the software application 333, receives an “Initial setup complete” command from the user 120 either via one of the control buttons 388 or the touch screen 318, indicating that the user does not wish to incorporate a coffee bag into the DDCP system, then the step 1101 confirms the usercommand by providing a suitable display on the display screen 318 and the process follows a “Y” arrow 1102 from the decision step 1101 to a step 501 in Fig. 5.Industrial Applicability

[0228] The arrangements described are applicable to domestic food and drink preparation and the hospitality industry.

[0229] The foregoing describes only some embodiments of the present invention, and modifications and / or changes can be made thereto without departing from the scope and spirit of the invention, the embodiments being illustrative and not restrictive.APPENDIX IINPUT AND OUTPUT DATA REFERENCED IN THE FIGURESAPPENDIX IIExamples of brewing recipe parameters and brewing recipe parameter values

[0230] Brewing Recipes: Key ParametersCrafting the perfect cup of coffee involves understanding and manipulating several key parameters. These parameters determine the flavour, strength, and overall quality of the brew. Below are the essential brewing recipe parameters:

[0231] Brewing Method: o Definition: The equipment and process used to brew coffee, such as drip, French press, espresso, AeroPress, etc. o Impact: Each method has unique characteristics that influence the strength, body, and clarity of the coffee.

[0232] Water Temperature: o Definition: The temperature of the water used to brew coffee. o Impact: Ideal temperature ranges from 195°F to 205°F (90°C to 96°C). Too hot can cause over-extraction; too cold can cause under-extraction.

[0233] Bloom Size: o Definition: The initial amount of water used to wet the coffee grounds, causing them to release CO2. o Impact: Helps achieve a more even extraction and typically uses a small portion of the total water.

[0234] Bloom Time-Length: o Definition: The duration of the bloom phase, where the coffee grounds are allowed to de-gas before the main pour. o Impact: Usually lasts about 30-45 seconds and ensures a more uniform extraction.

[0235] Remaining Pour / Flow Rate: o Definition: The rate at which the remaining water is poured over the coffee grounds after the bloom phase. o Impact: Affects the extraction rate and flavour profile. Consistent, controlled pouring leads to better extraction and balanced flavours.

[0236] The following parameter is mentioned for completeness however the DDCP system does not consider this parameter in detail.

[0237] Grind Size: o Definition: The coarseness or fineness of the coffee grounds.o Impact: Grind size directly affects the flow rate of water through coffee grounds, which in turn influences the extraction process. Coarser grinds allow water to pass through quickly, suitable for methods requiring longer contact times. Finer grinds slow down the flow rate, which is ideal for methods with shorter brew times and higher pressures. Adjusting the grind size is essential for achieving the desired balance of flavour and strength in your coffee.A number of specific brewing recipe examples are set out below.[02381 Pour Over 1 Cup 1 : 17 RegularBrewing RecipeRecipe Time: 3:00 minCoffee: 14.7gTotal Water: 250g at Temp - 97°CBloom Size: 44.1g of water over 17.64 secondsFlowrate Target (Bloom): 2.5 grams per secBloom Time: 1 minRemaining Time: 2 minRemaining Pour: 205.9g of water over 41.18 secFlowrate Target (Post-Bloom): 5 grams per secondBrewing InstructionsBLOOM POUR• Pour water onto brewing module: Start pouring 44.1g of water.• Start timer: Counting up to 1 :00 min.• Determine / display elapsed bloom time: X of 1 min has elapsed.• Determine and display flow rate: 2.5 grams per sec.• Issue alert: 1 min has elapsed.• Issue alert: 44.1g of water has been poured.POST-BLOOM POUR• Determine / display elapsed post-bloom time: 2:00 min remaining.• Determine and display flow rate: 5 grams per second.• Pour water onto brewing module: Start pouring 205.9g of water.• Issue alert: 2 min has elapsed.• Issue alert: 205.9g of water has been poured.• Stop pour.

[0239] Aeropress 1 Cup 1 : 13 RegularBrewing RecipeRecipe Time: 2:00 minCoffee: 15gTotal Water: 200g at Temp - 95°CBloom Size: 45g of waterFlowrate Target (Bloom): 2.5 grams per secBloom Time: 45 secRemaining Time: 1 min 15 secRemaining Pour: 155g of water over 31 secFlowrate Target (Post-Bloom): 5 grams per secondBrewing InstructionsBLOOM POUR• Pour water onto brewing module: Start pouring 45g of water.• Start timer: Counting up to 45 sec.• Determine / display elapsed bloom time: X of 45 seconds has elapsed.• Determine and display flow rate: 2.5 grams per second.• Issue alert: 45 sec has elapsed.• Issue alert: 45g of water has been poured.POST-BLOOM POUR• Determine / display elapsed post-bloom time: 1 min 15 sec remaining.• Determine and display flow rate: 5 grams per second.• Pour water onto brewing module: Start pouring 155g of water.• Issue alert: 1 min 15 sec has elapsed.• Issue alert: 155g of water has been poured.• Stop pour.

[0240] French Press 1 Cup 1 : 15 RegularBrewins RecipeRecipe Time: 4:00 minCoffee: 15gTotal Water: 225g at Temp - 93°CBloom Size: 45g of waterFlowrate Target (Bloom): 3 grams per secBloom Time: 45 secRemaining Time: 3 min 15 secRemaining Pour: 180g of water over 1 minFlowrate Target (Post-Bloom): 3 grams per secondBrewing InstructionsBLOOM POUR• Pour water onto brewing module: Start pouring 45g of water.• Start timer: Counting up to 45 sec.• Determine / display elapsed bloom time: X of 45 seconds has elapsed.• Determine and display flow rate: 3 grams per second.• Issue alert: 45 sec has elapsed.• Issue alert: 45g of water has been poured.POST-BLOOM POUR• Determine / display elapsed post-bloom time: 3 min 15 sec remaining.• Determine and display flow rate: 3 grams per second.• Pour water onto brewing module: Start pouring 180g of water.• Issue alert: 1 min has elapsed.• Issue alert: 180g of water has been poured.• Stop pour.

[0241] Cold Brew 1 Litre 1 :8 StrongBrewing RecipeRecipe Time: 12-24 hoursCoffee: 125gTotal Water: 1000g at Temp - Room TemperatureBloom Size: 250g of waterFlowrate Target (Bloom): 3 grams per secBloom Time: 1 min 23 secRemaining Time: 11-23 hoursRemaining Pour: 750g of water over 4 min 10 secFlowrate Target (Post-Bloom): 3 grams per secondBrewing InstructionsBLOOM POUR• Pour water onto brewing module: Start pouring 250g of water.• Start timer: Counting up to 1 min 23 sec.• Determine / display elapsed bloom time: X of 1 min 23 sec has elapsed.• Determine and display flow rate: 3 grams per second.• Issue alert: 1 min 23 sec has elapsed.• Issue alert: 250g of water has been poured.POST-BLOOM POUR• Determine / display elapsed post-bloom time: 11-23 hours remaining.• Determine and display flow rate: 3 grams per second.• Pour water onto brewing module: Start pouring 750g of water.• Issue alert: 4 min 10 sec has elapsed.• Issue alert: 750g of water has been poured.• Stop pour.

[0242] Espresso 1 Shot 1 :2 Ratio - Points of difference in italicsBrewing RecipeRecipe Time: 25-30 secondsCoffee: 18gTotal Water: 36g at Temp - 93°CPre-Infusion Size: 10g of waterFlowrate Target (Pre-Infusion): 2 grams per secPre-Infusion Time'. 5 secRemaining Time: 20-25 secondsRemaining Pour: 26g of water over 13 secondsFlowrate Target (Extraction): 2 grams per secondBrewing InstructionsPRE-INFUSION - Replaces BLOOM POUR• Pour water onto coffee grounds (the espresso machine automatically does this) . Start pouring 10g of water.• Start timer: Counting up to 5 sec.• Determine / display elapsed pre-infusion time: X of 5 seconds has elapsed.• Determine and display flow rate: 2 grams per second.• Issue alert: 5 sec has elapsed.• Issue alert: 10g of water has been poured.EXTRACTION - Replaces POST-BLOOM POUR• Determine / display elapsed extraction time: 20-25 sec remaining.• Determine and display flow rate: 2 grams per second.• Pour water onto brewing module (the espresso machine automatically does this) '. Start pouring 26g of water.• Issue alert: 20-25 sec has elapsed.• Issue alert: 26g of water has been poured.• Stop pour.

Claims

Claims:

1. A scale hub configured to guide a user in storing, dispensing and brewing coffee, the scale hub comprising: a weight sensor operatively coupled to a scale bed of the scale hub; a processor; a tag reader operatively coupled to the processor; a memory storing a processor executable program for directing the processor to perform a method comprising the steps of: receiving from the tag reader one or more tag identifiers from electronically readable tags attached to a tagged coffee receptacle placed upon the scale bed; receiving from the user a roast date and a storage temperature profile for roasted coffee beans in the tagged coffee receptacle; determining a flavour intensity of the roasted coffee beans depending upon the roast date and the storage temperature profile; determining a brewing recipe; displaying instructions from the brewing recipe for the user to place a brewing module associated with the brewing recipe on the scale bed; displaying instructions for the user to grind an amount of coffee from the tagged coffee receptacle and transfer the ground coffee to the brewing module; and displaying instructions for the user to process the ground coffee with water to produce a flavoured cup of coffee.

2. A scale hub according to claim 1, wherein the tagged coffee receptacle is a coffee storage module comprising a container component and a complimentary lid component each having attached a respective electronically readable tag; and the electronically readable tags are associated with the coffee storage module in stored system information stored in the memory.

3. A scale hub according to claim 1, wherein the tagged coffee receptacle is a coffee storage bag having attached an electronically readable tag; and the electronically readable tag is associated with the coffee storage bag in stored system information stored in the memory.

4. A scale hub according to claim 1, wherein the coffee storage receptacle is permanently stored in a specified storage temperature environment; and the storage temperature profile is a fixed temperature reflecting the storage temperature environment in which the coffee storage receptacle is permanently stored.

5. A scale hub according to claim 4, wherein the coffee storage receptacle is permanently stored in one of three storage temperature environments namely (i) at ambient temperature or (ii) in a refrigerator, or (iii) in a freezer; and the storage temperature profile is a fixed temperature reflecting the storage temperature environment in which the coffee storage receptacle is permanently stored.

6. A scale hub according to claim 1, wherein the flavour intensity has a mathematical representation of an exponential decay function depending upon the elapsed time after degassing time and a roast type dependent decay constant.

7. A scale hub according to claim 6, wherein the flavour intensity has a mathematical representation of an exponential decay function further depending upon the storage temperature profile.

8. A scale hub according to claim 1, wherein the step of determining a brewing recipe comprises the steps of: receiving from the user a selection of a brewing style from a displayed list of available brewing styles; and determining the brewing recipe from the selected brewing style and stored system information stored in the memory.

9. A scale hub according to claim 1, wherein the step of determining a brewing recipe comprises the steps of: receiving from the tag reader one or more tag identifiers of tags attached to a tagged brewing module placed upon the scale bed; determining a brewing style dependent upon the tag identifiers of the tagged brewing module and stored system information stored in the memory; and determining the brewing recipe from the brewing style and stored system information stored in the memory.

10. A scale hub according to claim 1, wherein prior to the step of displaying instructions for the user to grind an amount of coffee the method comprises the further step of communicating a control signal depending upon the flavour intensity to the electronically controllable coffee grinder to thereby direct the coffee grinder to grind roasted coffee beans to a desired particle size.

11. A scale hub according to claim 10, wherein the control signal directs the coffee grinder to grind roasted coffee beans to a desired particle size depending upon the flavour intensity and a roast type.

12. A scale hub according to claim 1, wherein the specific tagged coffee receptacle placed upon the scale bed is one of a plurality of tagged coffee receptacles each having attached a corresponding set of associated tags and tag identifiers; and the method comprises the further steps of: determining a weight of the specific filled coffee storage receptacle during successive multi-module storage mode processing cycles during each of which a weight of coffee is removed from the specific coffee storage receptacle; estimating a number of days remaining until the specific coffee storage receptacle is empty; and issuing an alert, depending upon the estimated number of days remaining and the flavour intensity, indicating that re-ordering of coffee should be performed.

13. A scale hub according to claim 8 or claim 9, wherein the method comprises the further steps of: receiving from the user a selection of a desired number of cups from a display indicating the available number of cups; receiving from the user selection of a desired strength from a display indicating the available range of strength; and determining the recipe dependent upon the selected number of cups and the selected strength.

14. A tangible computer readable data storage medium having a computer program recorded therein, the program being executable by a computer apparatus to make the computer perform a method comprising the steps of: receiving from a tag reader operatively coupled to the computer apparatus one or more tag identifiers from electronically readable tags attached to a tagged coffee receptacle placed upon a weight sensor in communication with the computer apparatus; receiving from a user a roast date and a storage temperature profile for roasted coffee beans in the tagged coffee receptacle; determining a flavour intensity of the roasted coffee beans depending upon the roast date and the storage temperature profile; determining a brewing recipe; displaying instructions from the brewing recipe for the user to place a brewing module associated with the brewing recipe on the weight sensor; displaying instructions for the user to grind an amount of coffee from the tagged coffee receptacle and transfer the ground coffee to the brewing module; and displaying instructions for the user to process the ground coffee with water to produce a flavoured cup of coffee.

15. A scale hub configured to guide a user in dispensing coffee, the scale hub comprising: a weight sensor operatively coupled to a scale bed of the scale hub; a processor; a memory storing a processor executable program for directing the processor to perform a method comprising the steps of: receiving from a user a roast date and a storage temperature profile for roasted coffee beans in a coffee receptacle placed upon the scale bed; and determining and displaying a flavour intensity of the roasted coffee beans depending upon the roast date and the storage temperature profile.

16. A scale hub according to claim 15, comprising the further steps of: determining a weight of the coffee receptacle during successive single-module storage mode processing cycles during each of which a weight of coffee is removed from the coffee receptacle; and estimating a number of days remaining until the coffee receptacle is empty; and issuing an alert, depending upon the estimated number of days remaining and the flavour intensity, indicating that re-ordering of coffee should be performed.

17. A scale hub according to claim 1, wherein the brewing module associated with the brewing recipe is a multi-component brewing module comprising a plurality of complimentary brewing module components, each of which is individually tagged with a corresponding electronically readable tag.

18. A scale hub according to claim 17, wherein the complimentary brewing module components are a pour over carafe and a pour over dripper each of which is individually tagged with a corresponding electronically readable tag.

19. A scale hub according to claim 17, wherein the multi-component brewing module is a cold brew carafe assembly comprising three complimentary brewing module components, each of which is individually tagged with a corresponding electronically readable tag.

Images