System and method for interactive demand response for controlling and routing power to one or more irrigation systems

The present application claims priority to U.S. Provisional Application No. 62/505,215 filed May 12, 2017.

1. Field of the Present Invention

The present invention relates generally to a system and method for providing interactive demand response in energy generation and routing and more particularly, to a system and method for providing an interactive demand response system for controlling and routing power to one or more irrigation systems.

2. Background of the Invention

Demand response is a forced reduction in the power consumption of an electric utility customer to better match the demand for power with the supply. Demand response is used by power companies to reduce the load on their systems. This is generally accomplished by remote management of a control box and a local load control switch that is wired into electrical systems of equipment to enable shutting down equipment during periods of peak demand. Most load control switches consist of a communication module and a relay switch. Such switches generally operate similarly to a pager, receiving signals or an electrical frequency shift to turn off or reduce power to an appliance during tunes of peak electrical demand.

Within conventional demand response systems, a customer's options are limited to either adjusting power demand by postponing some tasks that require large amounts of electric power, or paying a higher price for their electricity. If properly equipped, some customers may also switch part of their consumption to alternate sources, such as on-site diesel generators.

Regardless of how they are setup, current demand response systems do not allow customers to dynamically tailor their power consumption based on rapid fluctuations in temperature or other factors. This limitation is particularly important to farm operations which consume large amounts of electricity within very concentrated windows of time. It is even more important to irrigation systems since the timing of irrigation events carry direct economic consequences for any changes to prescribed schedules.

To address the shortcomings presented in the prior art, the present invention provides an interactive demand response system for controlling and routing power to one or more systems including irrigation systems. According to a preferred embodiment of the present invention, a system is provided which includes a power station load control CPU and a terminal interface module to allow growers to sign up for and selectively override load control events via any web-connected computer, tablet, or smartphone. Further, the present invention preferably generates automated text and email alerts for upcoming load control events including the start and end times for each event. Further, the present invention may provide for displays of current system demand within groups of load control devices before, during, and after load control events. Further the system of the present invention preferably includes the creation and transmission of messages and reports which provide a recap for the power company and/or the growers and which detail the level of participation, power usage, timing of load control events, and the selection of overrides.

The accompanying drawings, which are incorporated in and constitute part of the specification, illustrate various embodiments of the present invention and together with the description, serve to explain the principles of the present invention.

FIG. 1 shows a block diagram in accordance with an embodiment of the present invention.

FIG. 2 illustrates a method for use with one or more embodiments of the present invention.

For the purposes of promoting an understanding of the principles of the present invention, reference will now be made to the embodiments illustrated in the drawings and specific language will be used to describe the same. It will nevertheless be understood that no limitation of the scope of the present invention is hereby intended and such alterations and further modifications in the illustrated devices are contemplated as would normally occur to one skilled in the art.

Various inventive features are described below which can be used independently of one another or in combination with other features. However, any single inventive feature may not address any of the problems discussed above or only address one of the problems discussed above. Further, one or more of the problems discussed above may not be fully addressed by any of the features described below.

The terms “program,” “computer program,” “software application,” “module” and the like as used herein, are defined as a sequence of instructions designed for execution on a computer system. A program, computer program, module or software application may include a subroutine, a function, a procedure, an object implementation, an executable application, an applet, a servlet, a source code, an object code, a shared library, a dynamic load library and/or other sequence of instructions designed for execution on a computer system. A data storage means, as defined herein, includes many different types of computer readable media that allow a computer to read data therefrom and that maintain the data stored for the computer to be able to read the data again. Such data storage means can include, for example, non-volatile memory, such as ROM, Flash memory, battery backed-up RAM, Disk drive memory, CD-ROM, DVD, and other permanent storage media. However, even volatile storage such a RAM, buffers, cache memory, and network circuits are contemplated to serve as such data storage means according to different embodiments of the present invention.

At least portions of the functionalities or processes described herein can be implemented in suitable computer-executable instructions. The computer-executable instructions may be stored as software code components or modules on one or more computer readable media (such as non-volatile memories, volatile memories, DASD arrays, magnetic tapes, floppy diskettes, hard drives, optical storage devices, etc. or any other appropriate computer-readable medium or storage device). In one embodiment, the computer-executable instructions may include lines of complied C++, Java, HTML, or any other programming or scripting code such as R, Python and/or Excel. Further, the present invention teaches the use of processors to perform the functionalities and processes described herein.

Additionally, the functions of the disclosed embodiments may be implemented on one computer or shared/distributed among two or more computers in or across a network. Communications between computers implementing embodiments can be accomplished using any electronic, optical, radio frequency signals, or other suitable methods and tools of communication in compliance with known network protocols.

The terms “computer,” “engine,” “module,” “processor” and the like should be understood to be synonymous for the purposes of this disclosure. Additionally, any examples or illustrations given herein are not to be regarded in any way as restrictions on, limits to, or express definitions of, any term or terms with which they are utilized. Instead, these examples or illustrations are to be regarded as illustrative only. Those of ordinary skill in the art will appreciate that any term or terms with which these examples or illustrations are utilized will encompass other embodiments which may or may not be given therewith or elsewhere in the specification and all such embodiments are intended to be included within the scope of that term or terms.

The terms “power company,” “power provider” and the like should be understood to be synonymous for the purposes of this disclosure. These terms should be understood to generically refer to any system or mechanism for providing power to an end user.

Reference is now made in detail to the exemplary embodiments of the invention, examples of which are illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts. It should be understood that throughout this disclosure, unless logically required to be otherwise, where a process or method is shown or described, the steps of the method may be performed in any order or simultaneously. As used throughout this application, the word “may” is used in a permissive sense (i.e., meaning “having the potential to”), rather than the mandatory sense (i.e. meaning “must”).

With reference now to FIG. 1 , a block diagram in accordance with an embodiment of the present invention will now be discussed. As shown in FIG. 1 , the present invention provides a power transmission control system 100 which includes an electrical transmission network 110 which provides power to a plurality of irrigation systems 102 , 104 , As further shown, a central control CPU 116 is preferably provided which monitors the electrical transmission network 110 and controls the on/off status of the plurality of irrigation systems 102 , 104 through the use of load control switches 103 , 105 respectively. Although irrigation systems are discussed in this example, it should be understood that the present invention may be used for load control for any appliance, machine or other electricity consuming entity.

As shown, CPU 116 preferably includes a control-decision module which preferably includes software code running on a processor within or connected to the CPU 116 . In operation, the load control CPU 116 is preferably in communication with a load forecast/database module 114 which stores and updates the predicted loads for upcoming time periods. Preferably, the load forecast module 114 is further in communication with a remote updating service or the like so that the best and most accurate data may be available to the load control CPU 116 .

With the data from the load forecast module 114 , the load control CPU 116 preferably may determine one or more periods of peak load. Depending on the data available, the load control CPU 116 may simply receive a peak pre-identified period of peak load or may independently calculate the peak load periods based on one or more data sets. In some cases, utility personnel may simply consider the forecasted temperature and prior system behavior to determine system load. Further, the load control CPU 116 may receive and/or calculate the precise peak load time period for either an entire network system or for only a portion of the system. In this way, the system may treat discrete portions of a network system separately for the purpose of calculating peak load periods.

In addition to the load forecast module 114 , the load control CPU 116 may preferably further interface with a terminal interface module 118 . According to a preferred embodiment, the terminal interface module 118 preferably may be an operator accessible web or portal interface which allows communication with clients and operators. For example, the terminal interface module 118 preferably may allow operators to log on and determine load control schedules for a given set of systems. Further, the terminal interface module 118 preferably may allow operators to set up and access selections regarding their participation in the load control program and to access power saving calculations.

As further shown in FIG. 1 , an exemplary operator control system 106 is shown which preferably allows an operator to control and monitor the operations of one or more irrigation systems 102 , 104 . According to a still further preferred embodiment, the system of the present invention may preferably further include a grower control terminal 108 which allows for remote operation and monitoring of the operator control system 106 . According to a further preferred embodiment, the grower control terminal 108 may preferably include a computer, tablet and/or a smartphone type of device which allows for communications with the operator control system 106 as well as the terminal interface module 118 . According to a further preferred embodiment, the terminal interface module 118 may communication and receive information directly from either the operator control system 106 and/or the grower control terminal 108 .

With reference now to FIGS. 1 and 2 , an exemplary method in accordance with a further preferred embodiment of the present invention shall now be discussed. As shown in FIG. 2 , an exemplary first step 202 of the present invention preferably includes storing irrigation system information for a given grower. This information preferably includes a listing for each irrigation system used by grower/operators and the power draw/load information for each piece of equipment under load control. Preferably, this information may be variously stored for access by the load control CPU 116 and the operator control system 106 . With the load information stored, the load control CPU 116 in the next step 204 may preferably then calculate and maintain a load control schedule determination. Preferably, this load control schedule will include a calculation of the desired run periods for each irrigation system 102 , 104 . At step 206 , the load control CPU 116 preferably initiates a load control event message to the grower/operator which provides the dates and times of upcoming load control events. Preferably, the messages may be initiated at any scheduled time and they may further be initiated to occur at any given time interval prior to a load control event occurring (i.e. 30 minutes prior to the load control event). At step 208 , the time and duration of the load control is preferably received by the grower via the grower control terminal 108 and/or the operator control system 106 . According to a preferred aspect of the present invention, the operator control system 106 may preferably perform a calculation comparing the increased electricity cost of overriding the scheduled load control event with one or more factors affecting the crop growth. These may include: growth stage of crop; heat; humidity; soil composition; weather forecasts and the like. Preferably, the operator control system 106 may then preferably provide a comparison of the cost and benefits of overriding the load control event and provide the analysis to the grower control terminal 108 for the grower's review and analysis. Based on the grower's decision, in step 210 the grower may preferably opt to override the load control event and instead allow a given irrigation system to operate. Further, the grower may choose to allow the load control event to occur so that the irrigation systems 102 and 104 may be shut off or without power.

According to a further preferred embodiment, the grower may also elect to override a load control event for first system 102 based on growth data while allowing a second system to be subject to the load control event. For any response, the grower preferably may communicate through the grower control terminal 108 to the load control CPU 116 via the terminal interface module 118 . According to a further preferred embodiment, growers may preferably remotely override a load control event from anywhere using an internet or cellular data connection and a computer, tablet or smartphone as a grower control terminal 108 .

At step 212 , the load control CPU 116 preferably receives the load control responses for each system in the electrical transmission network 110 and uses the responses to update its load calculations for the load control event. According to a preferred embodiment, if the load calculation changes the price and/or the duration of the load control event, the load control CPU 116 may reset the schedule again (step 204 ) and/or retransmit an updated load control event message (step 206 ) with the updated calculations. For example, the load control CPU 116 may transmit any increase/decrease in the cost or duration of a load control event. Thereafter, the grower's system may proceed to update its calculations (step 208 ) and the grower may transmit a new or updated response (step 210 ). For example, based on a high number of growers opting out of a load control event, the cost of opting out may necessarily need to be increased. According to a further preferred embodiment, further incentives may also be provided to growers for not opting out of a given load control event, with the incentives increasing depending on factors such as: increased power demand, low grower participation in load control; and/or a high percent of growers opting out of a particular load control event.

At step 214 , with all of the grower choices determined, the load control CPU 116 will then preferably execute the load control event. In according with further aspects of the present invention, the load control CPU 116 preferably allows power producers to group enrolled units and observe in near real-time the number of units that are running and the amount of actual load that can be dropped from their system. According to further aspects of the present event, when a load control event is initiated, the users may preferably be notified within a very short time period (i.e., 5 to 30 seconds). Further, the system may preferably provide notices for events that are scheduled in the future, as well as the start and end of initiated load control events.

As discussed above, according to a preferred embodiment of the present invention, a power provider may use the power station load control CPU 116 and terminal interface module 118 of the present invention to allow growers to sign up for and selectively override load control events via any web-connected computer, tablet, or smartphone. Further, the present invention may preferably generate automated text and email alerts for upcoming load control events including the start and end times for each event. Further, the present invention may provide for displays of current system demand within groups of load control devices before, during, and after load control events. Further the system of the present invention preferably includes the creation and transmission of messages and reports which provide a recap for the power company including for example: levels of participation, power usage, timing of load control events, and selection of overrides.

While the above descriptions regarding the present invention contain much specificity, these should not be construed as limitations on the scope, but rather as examples. Many other variations are possible. For example, the present system may be used with other power consuming systems unrelated to irrigation such as those in mining, manufacturing, construction and the like without limitation. Further, the present invention may be used with groups of systems as well as individual systems. Accordingly, the scope should be determined not by the embodiments illustrated, but by the appended claims and their legal equivalents.