METHOD OF OPTIMIZING MARKET SUPPLY AND DEMAND DYNAMICS FOR ENERGY DISTRIBUTION AND CONSUMPTION

Abstract

The invention is related to the field of regulating energy consumption of a group of energy consumers serviced by utility companies, especially during peak demand periods. The invention teaches a novel way to incentivize consumers to manage electric loads during peak hours and use those loads during off-peak hours, thereby saving both consumers and utility companies money, while also conserving valuable energy producing resources. The invention utilizes hardware that may be used remotely to both monitor and turn on or off energy on or to a premises or load.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application relies on the disclosures of and claims priority to and the benefit of the filing date of U.S. Provisional Application No. 62/447,847, filed Jan. 18, 2017. The disclosures of that application are hereby incorporated by reference herein in their entireties.

BACKGROUND

Field of the Invention

The invention is related to the field of regulating energy consumption of a group of energy consumers serviced by utility companies, especially during peak demand periods. The invention herein teaches a novel way to incentivize consumers to participate in grid balancing activities such as, in one instance, demand response, thereby saving both consumers and utility companies money, while also conserving valuable energy producing resources.

Description of the Related Art

The following is generally reproduced from M. H. Albadi and E. F. El-Saadany, “A summary of demand response in electricity markets,” Electric Power Systems Research, vol. 78, pp. 1989-1996 (2008), which is incorporated herein in its entirety by reference.

There are three general actions by which a customer response can be achieved. Each of these actions involves cost and measures taken by the customer. First, customers can reduce their electricity usage during critical peak periods when prices are high without changing their consumption pattern during other periods. This option involves a temporary loss of comfort. This response is achieved, for instance, when thermostat settings of heaters or air conditioners are temporarily changed. Secondly, customers may respond to high electricity prices by shifting some of their peak demand operations to off-peak periods; for example, they shift some household activities (e.g., dishwashers, pool pumps) to off-peak periods. The residential customer in this case will bear no loss and will incur no cost. The third type of customer response is by using onsite generation—customer owned distributed generation. Customers who generate their own power may experience no or very little change in their electricity usage pattern. However, from a utility perspective, electricity use patterns will change significantly, and demand will appear to be smaller.

Different Demand Response (DR) programs can be classified into two main categories: Incentive-Based Programs (IBP) and Price-Based Programs (PBP). Some literature named these categories as system- and market-led, emergency and economic-based, or stability- and economic-based DR programs.

IBP are further divided into classical programs and market-based programs. Classical IBP include Direct Load Control programs and Interruptible/Curtailable Load programs. Market based IBP includes Emergency DR Programs, Demand Bidding, Capacity Market, and the Ancillary services market. In classical IBP, participating customers receive participation payments, usually as a bill credit or discount rate, for their participation in the programs. In market-based programs, participants are rewarded with money for their performance, depending on the amount of load reduction during critical conditions.

In Direct Load Control programs, utilities have the ability to remotely shut down participant equipment on a short notice. Typical remotely controlled equipment includes air conditioners and water heaters. This kind of program is of interest mainly to residential customers and small commercial customers. As with Direct Load Control programs, customers participating in Interruptible/Curtailable Programs receive upfront incentive payments or rate discounts. Participants are asked to reduce their load to predefined values. Participants who do not respond can face penalties, depending on the program terms and conditions.

Demand Bidding (also called Buyback) programs are programs in which consumers bid on specific load reductions in the electricity wholesale market. A bid is accepted if it is less than the market price. When a bid is accepted, the customer must curtail his load by the amount specified in the bid or face penalties. On the other hand, in Emergency DR Programs, participating customers are paid incentives for measured load reductions during emergency conditions. Furthermore, Capacity Market Programs are offered to customers who can commit to providing pre-specified load reductions when system contingencies arise. Participants usually receive a day-ahead notice of events and are penalized if they do not respond to calls for load reduction.

Ancillary services market programs allow customers to bid on load curtailment in the spot market as operating reserve. When bids are accepted, participants are paid the spot market price for committing to be on standby and are paid spot market energy price if load curtailment is required.

Currently, market based IBP are designed for large energy consumers such as industrial and large commercial facilities due to metering complexity and high investment requirements into advanced metering to enable the ability to send a signal, measure response and validated participation.

PBP programs are based on dynamic pricing rates in which electricity tariffs are not flat; the rates fluctuate following the real time cost of electricity. The ultimate objective of these programs is to flatten the demand curve by offering a high price during peak periods and lower prices during off-peak periods. These rates include the Time of Use (TOU) rate, Critical Peak Pricing (CPP), Extreme Day Pricing (EDP), Extreme Day CPP (ED-CPP), and Real Time Pricing (RTP).

The basic type of PBP is the TOU rates, which are the rates of electricity price per unit consumption that differ in different blocks of time. The rate during peak periods is higher than the rate during off-peak periods. The simplest TOU rate has two time blocks; the peak and the off-peak. The rate design attempts to reflect the average cost of electricity during different periods.

CPP rates include a pre-specified higher electricity usage price superimposed on TOU rates or normal flat rates. CPP prices are used during contingencies or high wholesale electricity prices for a limited number of days or hours per year. On the other hand, EDP is similar to CPP in having a higher price for electricity and differs from CPP in the fact that the price is in effect for the whole 24 hours of the extreme day, which is unknown until a day-ahead. Furthermore, in ED-CPP rates, CPP rates for peak and off-peak periods are called during extreme days. However, a flat rate is used for the other days.

RTP are programs in which customers are charged hourly fluctuating prices reflecting the real cost of electricity in the wholesale market. RTP customers are informed about the prices on a day-ahead or hour-ahead basis.

SUMMARY OF THE INVENTION

The invention herein teaches a method for managing the amount and/or timing of group energy consumption, including providing one or more device, capable of remote control, which allows for changing, adjusting, and/or turning on or off one or more circuit, device, load, appliance, and/or outlet on a premises, including but not limited to, a residential dwelling, house, apartment, duplex, condominium, farm, hotel, motel, business location, office, commercial building, government building, industrial complex, warehouse, open space, parking lot, parking deck, or any other physical location or structure. According to the invention, one or more time period is determined when to conserve and/or expend energy consumption based on the price and/or availability of energy during that one or more time period. Using the device to turn off energy to one or more circuit, device, load, appliance, and/or outlet on a premises, energy may be conserved during certain time periods, for example during peak demand time periods. Conversely, the device may be used to turn on energy to one or more circuit, device, load, appliance, and/or outlet on a premises to expend energy consumption during off-peak time periods. A consumer of the energy provided by, for example, a utility company, is incentivized to turn off or have turned off one or more circuit, device, load, appliance, and/or outlet on a premises during peak demand time periods. Accordingly, the cost of energy goes down for utility companies and their customers, and less energy is wasted. This paradigm can also be used to optimize use of renewable energy sources.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings illustrate certain aspects of some of the embodiments of the present invention, and should not be used to limit or define the invention. Together with the written description the drawings serve to explain certain principles of the invention.

FIG. 1 is flowchart depicting a possible embodiment of the invention taught herein.

FIG. 2 is flowchart depicting a possible embodiment of the invention taught herein.

DETAILED DESCRIPTION OF VARIOUS EMBODIMENTS OF THE INVENTION

The present invention has been described with reference to particular embodiments having various features. It will be apparent to those skilled in the art that various modifications and variations can be made in the practice of the present invention without departing from the scope or spirit of the invention. One skilled in the art will recognize that these features may be used singularly or in any combination based on the requirements and specifications of a given application or design. Embodiments comprising various features may also consist of or consist essentially of those various features. Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention. The description of the invention provided is merely exemplary in nature and, thus, variations that do not depart from the essence of the invention are intended to be within the scope of the invention. All references cited in this specification are hereby incorporated by reference in their entireties.

1. Summary of Peak Demand and Demand Response (DR)

Reliable operation of the electricity system generally requires a balance between supply and demand in close to or in real time. This balance has proven difficult to achieve in practice given that both supply and demand levels can change rapidly and unexpectedly due to many reasons, such as generation unit forced outages, transmission and distribution line outages, and sudden load changes. The electricity system infrastructure is capital intensive and, typically, is designed to meet expected certain levels of demand.

At certain time periods during certain days aggregated load in the electricity system may reach its maximums, representing a period of simultaneous, strong consumer demand.

“Peak demand”, “peak load,” and/or “on-peak” are terms used in energy demand management describing a period in which electrical power is expected to be provided for a sustained period at a significantly higher than average supply level. Peak demand fluctuations may occur on daily, monthly, seasonal and yearly cycles. For an electric utility company, the actual point of peak demand is a single half-hour or hourly period which represents the highest point of customer consumption of electricity.

DR can be described as the changes in electricity usage by end-use customers from their normal consumption patterns in response to changes in the price of electricity over time. Further, DR can be also described as the incentive payments designed to induce lower electricity use at times of high wholesale market prices or when system reliability is jeopardized. DR includes all intentional electricity consumption pattern modifications by end-use customers that are intended to alter the timing, level of instantaneous demand, or total electricity consumption.

2. Description of Current Marketplace Invention

The current invention is a marketplace platform that enables retail energy consumers, power utility companies and other parties to trade commitments to reduce or increase energy consumption during certain periods. Components of the platform presented by hardware, software, or a combination of these elements, may be deployed on a customer's premises, utility company facilities, or other places such as online servers.

One of the goals of the invention is to assist in the reduction of peak consumption through an enhanced demand response (DR) method. Such a method will unlock the potential of DR participation for consumers with electric loads that previously did not have the ability to be involved in peak reduction management.

In one aspect, the platform enables utility companies to offer retail consumers the ability to reduce or increase energy consumption by specific devices, appliances, outlets, and circuits or groups of devices, appliances, outlets, and circuits in exchange for incremental or wholesale monetary or other benefits. Such offers may be placed in real time or in near real time, on a subscription basis, in advance, or under other terms.

In another aspect, the platform may provide an ability for retail energy consumers to accept or decline utility company calls (offers, bids) for DR. Alternatively, retail customers may subscribe to participate in DR calls issued within certain time periods, for specific loads, or calls with certain monetary value(s).

3. Platform Components

The marketplace platform comprises multiple components operating separately or as a whole system. These components ensure proper pricing, execution, and/or delivery of transactions held on the platform. Platform components may include:

a. Hardware

A hardware component of the platform comprises one or more of the following elements:

An energy management device installed at a customer's premises. Such a device may incorporate physical hardware and software necessary for execution of its functions, which are incorporated in their entirety herein by reference, or as practiced in the industry. In one aspect, such a device may incorporate an ability to obtain measurements of energy consumption on a circuit or groups of circuits in a circuit breaker panel, individual device, appliance, outlet or groups of devices, appliances, and/or outlets at a customer's premises. In another aspect, such a device may incorporate the ability to turn on and off energy on specific circuits or groups of circuits as well as individual devices, appliances, outlets or groups of devices, appliances, and/or outlets at a customer's premises.

Any additional energy management devices capable of two way communication and energy consumption control. Such devices may include, but are not limited to, individual devices and appliances with built-in energy management capabilities such as thermostats, water heaters, and other devices. In addition, such energy management devices may include specific devices designed to control energy consumption of an individual or multiple circuits, loads, outlets or appliances.

A device (such as a phone, tablet, computer or any other computing or communication means) used by a customer to respond to utility company DR calls, update specific settings, and/or perform other operations.

A computer server running software that enables the platform operations. Such a server may be set up as a separate physical machine or group of machines connected by means of a wireless network, wireless connection, or wired connection, through Internet or some other wireless or wired communication(s). Alternatively, such a server may be set up as a virtual machine or group of machines operating in the “cloud” or a combination of physical and virtual machines.

A computer server, computer, laptop or any other computing means installed at the utility company's facility. Such a server may be set up to input and send information on proposed DR calls, perform specific calculations on required parameters of DR calls such as necessary load reduction, optimal pricing, and other parameters.

b. Software

A software component of the platform comprises one or more of the following elements:

• • A software code operating on the energy management device installed at a customer's premises;
  • A software code operating on a user's device such as a phone, tablet, computer or any other device used for monitoring and/or control purposes (e.g., an app and/or webpage);
  • A software code operating on a remote server or “cloud” (e.g., software on the “cloud”); and/or
  • A software code operating on servers and/or computers belonging to the utility company.

Embodiments of the invention also include a computer readable medium comprising one or more computer files comprising a set of computer-executable instructions for performing one or more of the calculations, steps, processes and operations described and/or depicted herein. In exemplary embodiments, the files may be stored contiguously or non-contiguously on the computer-readable medium. Embodiments may include a computer program product comprising the computer files, either in the form of the computer-readable medium comprising the computer files and, optionally, made available to a consumer through packaging, or alternatively made available to a consumer through electronic distribution. As used in the context of this specification, a “computer-readable medium” is a non-transitory computer-readable medium and includes any kind of computer memory such as floppy disks, conventional hard disks, CD-ROM, Flash ROM, non-volatile ROM, electrically erasable programmable read-only memory (EEPROM), and RAM. In exemplary embodiments, the computer readable medium has a set of instructions stored thereon which, when executed by a processor, cause the processor to perform tasks, based on data stored in the electronic database or memory described herein. The processor may implement this process through any of the procedures discussed in this disclosure or through any equivalent procedure.

In embodiments of the invention, files comprising the set of computer-executable instructions may be stored in computer-readable memory on a single computer or distributed across multiple computers. A skilled artisan will further appreciate, in light of this disclosure, how the invention can be implemented, in addition to software, using hardware or firmware. As such, as used herein, the operations of the invention can be implemented in a system comprising a combination of software, hardware, or firmware.

Embodiments of this disclosure include one or more computers or devices loaded with a set of the computer-executable instructions described herein. The computers or devices may be a general purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a particular machine, such that the one or more computers or devices are instructed and configured to carry out the calculations, processes, steps, operations, algorithms, statistical methods, formulas, or computational routines of this disclosure. The computer or device performing the specified calculations, processes, steps, operations, algorithms, statistical methods, formulas, or computational routines of this disclosure may comprise at least one processing element such as a central processing unit (i.e. processor) and a form of computer-readable memory which may include random-access memory (RAM) or read-only memory (ROM). The computer-executable instructions can be embedded in computer hardware or stored in the computer-readable memory such that the computer or device may be directed to perform one or more of the calculations, steps, processes and operations depicted and/or described herein.

Additional embodiments of this disclosure comprise a computer system for carrying out the computer-implemented method of this disclosure. The computer system may comprise a processor for executing the computer-executable instructions, one or more electronic databases containing the data or information described herein, an input/output interface or user interface, and a set of instructions (e.g. software) for carrying out the method. The computer system can include a stand-alone computer, such as a desktop computer, a portable computer, such as a tablet, laptop, PDA, or smartphone, or a set of computers connected through a network including a client-server configuration and one or more database servers. The network may use any suitable network protocol, including IP, UDP, or ICMP, and may be any suitable wired or wireless network including any local area network, wide area network, Internet network, telecommunications network, Wi-Fi enabled network, or Bluetooth enabled network. In one embodiment, the computer system comprises a central computer connected to the internet that has the computer-executable instructions stored in memory that is operably connected to an internal electronic database. The central computer may perform the computer-implemented method based on input and commands received from remote computers through the internet. The central computer may effectively serve as a server and the remote computers may serve as client computers such that the server-client relationship is established, and the client computers issue queries or receive output from the server over a network.

The input/output interfaces may include a graphical user interface (GUI) which may be used in conjunction with the computer-executable code and electronic databases. The graphical user interface may allow a user to perform these tasks through the use of text fields, check boxes, pull-downs, command buttons, and the like. A skilled artisan will appreciate how such graphical features may be implemented for performing the tasks of this disclosure. The user interface may optionally be accessible through a computer connected to the internet. In one embodiment, the user interface is accessible by typing in an internet address through an industry standard web browser and logging into a web page. The user interface may then be operated through a remote computer (client computer) accessing the web page and transmitting queries or receiving output from a server through a network connection.

Such graphical controls and components are reusable class files that are delivered with a programming language. For example, pull-down menus may be implemented in an object-oriented programming language wherein the menu and its options can be defined with program code. Further, some programming languages integrated development environments (IDEs) provide for a menu designer, a graphical tool that allows programmers to develop their own menus and menu options. The menu designers provide a series of statements behind the scenes that a programmer could have created on their own. The menu options may then be associated with an event handler code that ties the option to specific functions. Text fields, check boxes, and command buttons may be implemented similarly through the use of code or graphical tools. A skilled artisan can appreciate that the design of such graphical controls and components is routine in the art.

4. Utility Company or Other Party Involved in Utility Grid Management Enrollment

A utility company or other party involved in utility grid management may become a marketplace participant by either establishing its own marketplace program or connecting to an existing program.

The platform may provide functionality for utility companies, municipalities or other parties to manage specific sections of the marketplace segregated by geography, connection to a specific grid segment, or other characteristic(s). In cases where the platform is involved in management of energy commitments in deregulated markets, the management rights may be transferred to an independent third-party or may remain with the platform operator such as a platform development company.

A utility company or other party involved in utility grid management may need to comply with local regulations and meet specific criteria set up in a specific location for an organization to be involved in grid operations. Such criteria may include specific licenses, certifications, capital requirements, or other criteria.

5. Customer Enrollment and Asset Identification (e.g., What the Customer Has to Offer)

To become a participant of the marketplace, an energy consumer may need to perform certain steps including but not limited to:

Install or caused to be installed in or on the premises the hardware device. Such installation may be initiated by the customer or other party such as a landlord, facility management company or other party that has the right to initiate such installation. Alternatively, a utility company may install or cause to be installed the hardware, such as by providing a DR program involving said device(s).

Alternatively, an energy customer may install or cause to be installed any other energy management system including energy consumption measurement and control on full premises, one or more circuits, one or more outlets, and/or one or more energy consuming loads.

Connecting the installed hardware to the Internet by means of wireless network, wired connection or other means.

Sign up for participation in a DR program. The sign up process may be initiated by the customer or other party such as a landlord, facility management company or other party that has the right to initiate the sign up procedure. A utility company may also sign up a customer. A sign up process may involve a number of steps, such as:

• • Providing personal data such as:
    • Name;
    • Address;
    • Age, gender, household income level and other personal and household data; and/or
    • Utility company account number and other information associated with a utility contract.
  • Providing Information about premises such as:
    • Size;
    • Age;
    • Number of floors;
    • Number of rooms;
    • Information about circuit breaker box and/or electricity consumption; and/or
    • Other data.
  • Providing Information about other occupants including:
    • Names;
    • Age;
    • Gender; and/or
    • Other data.
  • Providing permission for access to data associated with the user's account and stored on the device(s), online server, or other locations. Such data may include:
    • Number and names of device(s), circuit breaker panel(s), circuits, appliances, outlets and/or plugs, etc. on premises;
    • Historical consumption data for circuits, devices, loads, appliances, outlets, etc. on premises; and/or
    • Other consumption characteristics such as specific time periods, days, consumption peaks and other data.
  • Providing additional information as may be required such as:
    • Specific characteristics of circuits, devices, loads, appliances, or outlets on premises;
    • Preferred participation time periods; and/or
    • Other personal preferences including desired frequency of participation.
  • Other steps.

Install software such as an app or other software on a device or number of devices (such as a phone, tablet, computer or any other computing means) used by a customer to respond to utility company DR calls and/or other communication.

Registration (pairing) of said user devices (such as a phone, tablet, computer or any other computing means) with the marketplace platform and/or software by means of assigning of unique identification number(s) or other identification information to each device or other means. Customer and other information may be encrypted or otherwise made to be confidential.

Other steps as may be needed.

As a part of the customer registration process, the software may create a unique record or set of records in a database or number of databases reflecting a customer profile. The software may assign certain specific characteristics to such record that will enable classification for customer eligibility for DR calls/contacts. Such characteristics may include:

• • Geographical location of the customer's premises;
  • Identification of a specific utility company servicing the customer;
  • Connection to a specific utility grid branch and/or circuit;
  • Electricity consumption profile/history;
  • Likelihood of success in response to utility demand reduction calls; and/or
  • Other characteristics.

Some or all characteristics may be updated from time to time.

In one aspect, the software may assign probabilities for a customer to actively participate in DR calls/contacts. Such probabilities may be based on customer unique characteristics such as electricity consumption profile/history, size of premises, average number of loads in similar sized premises, use of premises, age, gender, income or other characteristics. Alternatively, such probabilities may be assigned based on probabilities calculated for other customers with matching profiles that are already enrolled into the marketplace. In either case, such probabilities may be adjusted based on observed customer behavioral patterns.

Once a customer is registered, the software may proceed to identify and record a list of circuits, devices, appliances, loads, and/or outlets existing in a customer's premises. Such circuits, devices, loads, appliances, and/or outlets may be considered by the software as potential targets for DR calls/contacts. The software may analyze previous consumption history and assign each identified load (such as a circuit, device, appliance, or outlet) with a number of characteristics that may be used to determine potential for a load's participation in a DR call/contact. Such characteristics may include:

• • Energy consumption parameters such as watts, volts, and amps;
  • Patterns describing load usage and energy consumption;
  • Frequency of load usage;
  • Typical time periods of consumption;
  • Typical days of consumption;
  • Seasonal effect on consumption; and/or
  • Other parameters.

In another aspect, the software may assign each identified load with specific marks to assign periods of activity and inactivity.

6. Customer Automatic Participation and Subscription

A customer may enroll one or more circuits, devices, loads appliances, and/or outlets to automatically participate in DR utility calls/contacts. A customer may create a set of rules for such subscription by accessing respective menu(s) and setting up appropriate rules in a user interface of the software on the online server or in the app installed on user's device (phone, tablet, computer, etc.).

A customer may create various sets of rules and parameters for subscription to DR participation for circuits, devices, loads, appliances, and/or outlets including:

• • Name of circuit(s), device(s), load(s), appliance(s), or outlet(s);
  • Time when such circuits, devices, appliances, loads, or outlets may automatically enroll in DR calls/contacts (e.g., from 9:00 am to 4:00 pm);
  • Days when such circuits, devices, loads, appliances, or outlets may automatically enroll in DR calls/contacts (e.g., Monday through Friday);
  • Maximum duration of each enrollment cycle (e.g., no longer than 2 hours per cycle or per day);
  • Minimum threshold on monetary or other benefits received; and/or
  • Other parameters.

In one aspect, each rule and/or parameter may be modified and/or cancelled by a customer at any point in time by accessing a respective menu(s) in the user interface of the software on the online server or in the app installed on the user's device (phone, tablet, computer, etc.). Alternatively, a user may have an option to cancel all subscriptions by addressing specific menu item(s) in a form of a link, button, or other graphical images. In one aspect, the user interface may be performed in-person, over the phone, or by document sent to, for example, the utility company.

Each circuit, device, load, appliance, or outlet enrolled into automatic DR may be triggered by a utility company DR call/contact without further consent from a user subject to compliance to the subscription rules and parameters set by such user as described above. All monetary or other benefits, in this case, will be transferred to the user by the utility company based on the participation of such enrolled circuits, devices, loads, appliances, or outlets.

In another aspect, a user may use the same procedure to subscribe to participate in utility calls/contacts for shifting consumption by selected circuits, devices, loads, appliances, or outlets from peak periods to nonpeak periods. In this case, each circuit, device, load, appliance, or outlet subscribed to the DR program may be triggered by a utility company DR bid to shut off power supply during peak periods and, respectively, return it back for specific nonpeak periods. The method for shifting consumption from peak to nonpeak periods is described further below.

In addition, a customer may use the same procedure to subscribe for renewable energy consumption by selected circuits, devices, loads, appliances, or outlets when available. Alternatively, such subscription may involve reduction of consumption on specific circuits, devices, loads, appliances, or outlets when there is a shortage of renewable energy. The method for managing of renewable energy consumption is described further below.

7. Utility Call Determination for an Individual User

When a utility company experiences or expects a peak load, such utility company may input an aggregated bid calling for a specific load reduction. Such bid may contain specific values such as:

• • overall amount of load reduction sought;
  • aggregated load level expected;
  • determination of specific geography where the load reduction is required;
  • specific parts, regions, sections or branches of utility grid where load reduction is required;
  • specific time periods when load reduction is required;
  • aggregated price range for the bid determining how much bidding utility company is willing to pay for the overall DR load reduction; and/or
  • other parameters.

In a preferred embodiment, once such a bid is placed in the system, it is transferred to an online server (e.g., cloud) by means of wireless network, wireless connection, or wired connection, through Internet or some other form of communication for further processing. In this aspect, the software on the cloud performs initial classification of the bid by matching the parameters of the bid with retail consumers that may be eligible to respond to the call. Such classification may involve filtering a consumer database to identify those consumers that match required parameters such as geography and connection to a specific grid branch.

Once the software identifies the eligible subset of consumers matching these parameters, it proceeds to review, search for, and/or analysis of available loads that may participate in the DR call/contact by executing several steps, those steps comprising one or more of the following:

The software reviews loads that were subscribed for automatic DR participation by consumers within required bid parameters such as time periods, price range and others. Such loads are then enrolled into the DR call/contact automatically.

The software calculates the amount of load reduction achieved by triggering the subscribed loads. The software determines the remaining amount of load reduction as a difference between the aggregated load reduction bid and the amount of load reduction achieved by triggering subscribed loads. In situations when such amount is less than the amount of aggregated load reduction bid, the software proceeds to the next step. In situations when the amount of load reduction achieved by triggering the subscribed loads is higher than the amount of aggregated load reduction bid, the software proceeds to the step determining the combination of the subscribed loads triggered by the bid.

The software determines what circuits; devices, loads, appliances, outlets or groups of circuits, devices, loads, appliances, outlets for an individual customer may represent the loads that customers are likely to agree to turn on or off in case they receive a bid notification. Such classification may be based on one or more of:

• • load size;
  • user consumption patterns;
  • pre-created database of loads that are most likely to react based on load name, location, size or other parameters;
  • past history of bids that user agreed to accept (likelihood of bid success);
  • aggregated patterns for consumption and bid participation by other users; and/or
  • other parameters.

The software creates a combination of loads across multiple eligible users in a way such that the sum of triggered loads equals or exceeds the difference between the aggregated load reduction bid and the amount of load reduction achieved by triggering subscribed loads. Such calculation may incorporate allowances for probabilities of user response success. The combination of loads is created in a way that it targets to prioritize loads under certain parameters such as:

• • Loads with larger size over loads with smaller size;
  • Loads that consumers are more likely to agree to turn on or off in case they receive a bid notification;
  • Past history of loads that consumers agreed to turn on or off; and/or
  • Other parameters.

When the combination of individual loads satisfying the parameters of a utility's aggregated bid is created, the software may send users individual bids. Each user may receive a single bid, multiple bids, or a combined bid grouping several circuits, devices, loads, appliances, or outlets. Such bids may include specific instructions and suggestions for users to commit to a specific consumption behavior on identified circuits, devices, loads, appliances, or outlets. The bid may contain a proposal for a monetary or other benefit that a user may receive in case the user agrees to accept the bid. A bid may be sent to a user in one or several forms including a text message, a phone call, an email, a bid through an app installed on a user's phone, tablet, or computer, a bid on a user's online portal, or other form of a bid. Such bid may contain the tools to execute the action in the form of links, buttons, or other graphical images or text. By clicking, pressing, pushing or otherwise interacting with these tools, a user may send specific commands to the software and indicate acceptance or denial of the bid. The bid and/or user interface may also be used for advertisement purposes. For example, more energy efficient appliances or light bulbs may be suggested. Other offers by the utility company may be suggested. Other third party services or products may be offered.

In one aspect, identifying loads of energy consumers capable of enrolling in the load reduction process takes into account the probability that the consumer is likely to agree to turn off or decrease power supply to a load(s).

In another aspect, selecting of loads or additional loads for participation in the load reduction process involves prioritizing by one or more of: the loads with larger size over the loads with smaller size; the loads that the consumers are more likely to agree to turn off if notified; and/or past history of loads that consumers agreed to turn off.

In one aspect, a user may receive a bid from a utility company containing specific consumption parameters comprising:

• • specific circuit, device, load, appliance, or outlet name (e.g., “Would you agree to turn off your washing machine . . . ”);
  • specific peak period when the user is committing to reduce or stop usage of the circuit, device, load, appliance, or outlet (e.g., “ . . . between 6 pm and 8 pm today . . . ”);
  • specific monetary or other benefit that the user may receive in case of accepting the bid (e.g., “You will receive $1 payment for agreeing to the terms.”); and/or
  • Tools to accept/deny the bid in the form of a question (e.g., “Would you like to accept the terms?”) and two push buttons (e.g., “Yes” and “No”).

When a user agrees to accept the bid, the software may cause power supply shut off to the respective circuit, device, load, appliance, or outlet for the time period indicated in the bid by executing certain commands on the installed hardware components of the marketplace. This operation may be required to ensure proper execution of the transaction and increase reliability of grid operations. Once the period elapses, the software returns power supply to the indicated circuit, device, load, appliance, or outlet.

8. Participation Through Adjusting Individual Device Settings

As described above, a user may participate in DR bids at the marketplace by committing to increase or decrease energy consumption. Such changes may be caused by complete shut off of energy supply to specific circuits, devices, loads, appliances, outlets or groups of circuits, devices, loads, appliances, or outlets. Alternatively, a user may participate in DR bids by committing to change specific settings of individual devices on a temporary basis.

In one aspect, a user may commit to adjust specific settings of an individual device leading to an increase or decrease of energy consumption. An example of such commitment may be a change in temperature settings by several degrees on a thermostat on a hot summer day when power grid experiences a peak load.

The software may determine specific devices at a user's premises that have an ability to be managed remotely by means of a wireless network, wireless connection, or wired connection, through Internet or some other wireless or wired form of communication. Such devices may have the ability to connect to Smart Home platforms and may be managed or operated in some other form by the hardware and/or software described or incorporated by reference in this application. Alternatively, a user may enroll into marketplace participation specific devices with such abilities to be managed over a wireless network, wireless connection, or wired connection, through Internet or some other wireless or wired form of communication.

In one aspect, the software may perform one or multiple test measurements to verify specific impact(s) on energy consumption that may be achieved by adjusting device settings.

In another aspect, the software may use pre-determined formulas, coefficients, algorithms or other methods to calculate potential impact(s) of a setting's adjustment on energy consumption.

The software may create and update a database or multiple databases with records of such devices with various records indicating, for example:

• • device names;
  • specific circuit in premise's circuit breaker panel where devices are installed;
  • unique identification numbers;
  • device location in the premises;
  • device functionality;
  • ability to turn on/off in response to a signal sent through the smart home hub;
  • manufacturer's characteristics such as targeted energy consumption;
  • potential impact on energy consumption determined as described above; and/or
  • other parameters.

The software may factor such devices into the method of determining a combination of individual loads to satisfy an aggregated DR bid. In this aspect, when the combination of individual loads satisfying the parameters of a utility's aggregated bid is created including load reductions from settings' adjustment(s), the software may send users individual bids. Each user may receive a single bid, multiple bids, or a combined bid grouping several circuits, devices, loads, appliances, or outlets. Such combinations may involve suggestions to adjust certain device settings.

Such bids may include specific instructions and suggestions for users to commit to a specific consumption behavior. The bid may contain a proposal for a monetary or other benefit that a user may receive in case the user agrees to accept the bid. A bid may be sent to a user in one of several forms including a text message, a phone call, an email, a bid through the app installed on a user's phone, tablet, or computer, a bid on user's online portal, or other form of bid. Such bid may contain the tools to execute the action in the form of links, buttons or other graphical images or text. By clicking, pressing, pushing or otherwise interacting with these tools, a user may send specific commands to the software and indicate acceptance or denial of the bid.

For example, a user may receive a bid from a utility company containing specific device adjustment parameters comprising:

• • Specific device name and action suggested (e.g., “Would you agree to decrease the temperature on your thermostat by 4 degrees . . . ”);
  • Specific peak period when the user is committing to change device settings (e.g., “ . . . between 2 pm and 4 pm today . . . ”);
  • Specific monetary or other benefit that the user may receive in case of accepting the bid (e.g., “You will receive $1 payment for agreeing to the terms.”); and/or
  • Tools to accept/deny the bid in the form of a question (e.g, “Would you like to accept the terms?”) and two push buttons (e.g., “Yes” and “No”).

When a user agrees to accept the bid, the software may cause the selected device to change its settings for the period indicated in the bid. Once the period elapses, the software returns device settings to the initial value.

9. Individual Bid Price

The software may determine the monetary amount of an individual bid in a way that a sum of all monetary amounts of all individual bids would be equal to or less than the monetary amount set by a utility company or other party involved in utility grid management as the maximum payment to achieve sought demand reduction. When an aggregated bid is received, the software may follow a set of rules to identify prices assigned to individual bids.

Users that have subscribed specific circuits, devices, loads, appliances, outlets or groups of circuits, devices, loads, appliances, or outlets for automatic participation in DR bids may receive individual bids with, for example:

• • Prices representing the maximum price of the price range for each bid determined by a utility company or other party involved in utility grid management. Such method may be used to incentivize users to enroll and subscribe circuits, devices, loads, appliances, or outlets to DR participation;
  • Prices representing the minimum price of the price range for each bid by a utility company or other party involved in utility grid management. Such method may be used to engage a larger retail customer base to enroll in the marketplace and actively participate in DR bids on a regular basis;
  • Prices representing the average or median price of the price range for each bid by a utility company or other party involved in utility grid management. Such method may be used to provide average distribution of the DR participation value to all users beyond the subscribed group; and/or
  • Prices determined otherwise within the price range for each bid by a utility company or other party involved in utility grid management.

Users that have not subscribed specific circuits, devices, loads, appliances, outlets or groups of circuits, devices, loads, appliances, or outlets for automatic participation in DR bids may receive individual bids with, for example:

Prices representing the maximum price of the price range for each bid determined by a utility company or other party involved in utility grid management. Such method may be used to engage larger retail customer base to enroll in the marketplace and actively participate in DR bids on a regular basis;

• • Prices representing the minimum price of the price range for each bid by a utility company or other party involved in utility grid management. Such method may be used to incentivize users to enroll and subscribe circuits, devices, loads, appliances, or outlets to automatic DR participation;
  • Prices representing the average or median price of the price range for each bid by a utility company or other party involved in utility grid management. Such method may be used to provide average distribution of the DR participation value to all users participating in the DR bid; and/or
  • Prices determined otherwise within the price range for each bid by a utility company or other party involved in utility grid management.

10. Utility Automatic Participation Without Manual Actions

A utility company or other party involved in utility grid management may actively participate in the marketplace by issuing specific bids either manually or automatically. In cases when a utility company or other party involved in utility grid management decides to set up automatic participation, it may create a set of rules that may trigger a new aggregated bid.

In one aspect, such set of rules may include:

• • Specific load levels on the grid that a utility company or other marketplace participant seeks to maintain;
  • Geography and grid circuits or branches involved in the marketplace;
  • Retail customer profiles that a utility company or other marketplace participant seeks to target;
  • Targeted price ranges for bids; and/or
  • Other characteristics.

In another aspect, a utility company or other party involved in utility grid management may connect its grid and load monitoring systems with the marketplace platform. Such connection may be provided by means of a wireless network, wireless connection, or wired connection, through Internet or some other form of communication.

When the software observes a set of conditions on the grid that meet preset rules, it may trigger an automatic bid placement on behalf of the marketplace participant.

For example, when the software observes a rise in overall load level on the grid in a specific time frame, or anticipates such a rise in overall load level, it may issue a DR bid. The software may use a predetermined price range for such bid. Alternatively, the software may receive price data from other sources such as energy wholesale marketplaces, third-party websites and other sources to identify proper price range for a bid.

In another aspect, the software may monitor wholesale energy market prices in real time and issue DR bids when specific price levels are achieved or expected.

A utility company or other party involved in utility grid management may set specific limits for costs that it plans either for wholesale energy procurement or generation and transmission costs. The software may monitor whether actual wholesale energy market prices allow for the set spending limits. When the software may forecast that such spending limit may be exceeded, the software may trigger a DR bid to reduce energy purchases.

11. Peak Smoothing by Shifting Consumption

The marketplace may provide additional functionality for utility companies to incentivize retail customers to shift energy consumption by specific electric loads from peak periods to nonpeak periods. Retail customers may receive specific suggestions that may be coupled with monetary or other benefits to use certain circuits, devices, loads, appliances, or outlets during periods that are identified by a utility company as nonpeak.

In one aspect, the software may create or use a pre-created database of circuits, devices, loads, appliances, or outlets that may be used during nonpeak periods instead of being used in peak periods. For example, such a database may contain specific records indicating appliances or circuits where appliances such as washers, dryers, dishwashers may be located.

The software analyzes user consumption history to identify usage patterns of circuits, devices, loads, appliances, or outlets identified in said database. In cases when the software identifies that a user is likely to use such circuits, devices, loads, appliances, or outlets during peak periods, it may create or update a list of suggested alterations. In addition, the software may calculate a potential effect of such alterations resulting from customers' shift in consumption. The potential effect may be calculated as a sum of consumption characteristics such as watts, volts, and/or amps across specific subset(s) of circuits, devices, loads, appliances, or outlets. Such sum may be calculated for a single user or a group of users characterized by a specific geography, utility grid circuit or branch, device type or other characteristic.

The software may present a report on the calculated potential effect to a utility company. The report may include calculation of economic benefits achieved by shifting consumption during peak periods to nonpeak periods. Such benefits may be based on the difference of peak period utility energy purchase costs or generation and distribution costs and similar costs during nonpeak periods.

When a utility company anticipates a peak consumption period, it may direct software to issue an aggregated bid to the users in the identified list. Such bid may contain specific values such as:

• • overall amount of load reduction sought;
  • aggregated load level expected;
  • determination of specific geography where the load reduction is required;
  • specific parts, regions, sections or branches of utility grid where load reduction is required;
  • specific time periods when load reduction is required;
  • aggregated price range for the bid determining how much a utility company is willing to pay for the overall load reduction; and/or
  • other parameters.

In one aspect, once such a bid is placed in the system, it is transferred to the online server (e.g., cloud) by means of wireless network, wireless connection, or wired connection, through the Internet or some other form of communication for further processing. The software in the cloud performs initial classification of the bid by matching the parameters of the bid with retail consumers in the identified list that may be eligible to respond to the call/contact. Such classification may involve filtering a consumer database to identify those consumers that match required parameters such as geography and connection to a specific grid branch or circuit.

Once the software identifies the subset of consumers matching these parameters, it proceeds to a review of available loads that may participate in the consumption shift bid call by executing several steps comprising one or more of the following:

The software reviews loads that were subscribed for automatic consumption shift participation by consumers within required periods. Such loads are then enrolled into the consumption shift call automatically. The software calculates the amount of load reduction achieved by triggering the subscribed loads. In cases when such amount is less than the amount of aggregated load reduction bid, the software proceeds to the next step.

The software determines the remaining amount of load reduction as a difference between the aggregated load reduction bid and the amount of load reduction achieved by triggering subscribed loads.

The software determines what circuits, devices, loads, appliances, outlets or groups of circuits, devices, loads, appliances, outlets for an individual customer or group of individual customers may represent the loads that customers are likely to agree to change consumption patterns for, in case they receive a bid notification. Such classification may be based on:

• • load size;
  • user consumption patterns;
  • pre-created database of loads that are most likely to react based on load name, location, size or other parameters;
  • past history of bids that a user agreed to accept or reject (likelihood of bid success);
  • aggregated patterns for consumption and bid participation by other users; and/or
  • other parameters.

The software creates a combination of loads across multiple eligible users in a way that the sum of triggered loads equals or exceeds the difference between the aggregated load reduction bid and the amount of load reduction achieved by triggering subscribed loads. Such calculation may incorporate allowances for probabilities of user response success. The combination of loads is created in a way that it targets to prioritize loads under certain parameters such as:

• • Loads with larger size over loads with smaller size;
  • Loads that consumers are more likely to agree to turn on or off in case they receive a bid notification;
  • Past history of loads that consumers agreed to turn on or off; and/or
  • Other parameters.

When the combination of individual loads satisfying the parameters of a utility's aggregated bid is created, the software may send users individual bids. Each user may receive a single bid, multiple bids, or a combined bid grouping several circuits, devices, loads, appliances, or outlets.

Such bids may include specific instructions and suggestions for users to commit to a specific consumption behavior on identified circuits, devices, loads, appliances, or outlets. The bid may contain a proposal for a monetary or other benefit that a user may receive in case the user agrees to accept the bid. A bid may be sent to a user in one or several forms including a text message, a phone call, an email, a bid through the app installed on a user's phone, tablet, or computer, a bid on user's online portal, or other form of bid. Such bid may contain the tools to execute the action in the form of links, buttons or other graphical images or text. By clicking, pressing, pushing or otherwise interacting with these tools, a user may send specific commands to the software and indicate acceptance or denial of the bid.

For example, a user may receive a bid from a utility company containing specific consumption parameters:

• • Specific circuit, device, load, appliance, or outlet name (e.g., “Would you agree to run your washing machine . . . ”);
  • Specific non-peak period when the user may use the circuit, device, load, appliance, or outlet (e.g, “ . . . after 9 pm today . . . ”);
  • Specific peak period when the user typically uses the circuit, device, load, appliance, or outlet (e.g., “ . . . as opposed to running it between 6 pm and 8 pm.”);
  • Specific monetary or other benefit that the user may receive in case of accepting the bid (e.g., “You will receive $1 payment for agreeing to the terms.”); and/or
  • Tools to accept/deny the bid in the form of a question (e.g., “Would you like to accept the terms?”) and two push buttons (e.g., “Yes” and “No”).

When a user agrees to accept the bid, the software may cause the power supply to shut off to the respective circuit, device, load, appliance, or outlet for the time period indicated in the bid. This operation may be required to ensure proper execution of the transaction and increase reliability of grid operations. Once the time period elapses, the software may return power supply to the indicated circuit, device, load, appliance, or outlet. Although it is recognized that automatic turning on and/or off of the power supply to the target circuit, device, load, appliance or outlet is most desirable from an efficiency standpoint, the turning on and/or off can alternatively be performed manually, such as by the customer.

12. Early Bid Participation Cancellation and Penalties for Consumers

Retail customers participating in the marketplace may trade their commitments and enter into specific agreements with utility companies or other parties to reduce or increase energy consumption on certain circuits, devices, loads, appliances, or outlets. In cases when a customer voluntarily or involuntarily breaches a term of a bid that the customer has accepted, such customer may be charged with a penalty.

After a customer accepts terms of a bid placed through the marketplace, such customer subscribes to certain consumption characteristics within a defined timeframe. However, such customer may have an ability to cancel her participation in the accepted bid.

In one aspect, where the software may cause power supply shut off to the respective circuit, device, load, appliance, or outlet for the period indicated in the bid, a customer may have an ability to restore such power supply. To do so, a customer may access a respective menu in a user interface of the software on the online server or in the app installed on user's device (phone, tablet, computer, etc.). Alternatively, a user may have an option to cancel one or plural ongoing accepted bids by addressing specific menu item(s) in the form of a link, button or other graphical images. The customer may also have a manual override switch to restore power.

When a customer performs certain actions that lead to cessation of participation in a particular bid or multiple bids, such customer may lose monetary or other benefits associated with such bid or multiple bids.

In another aspect, a utility company or other party acting as a counterpart on a bid or multiple bids, may place certain penalties on a customer who ceased her participation in a DR bid. Such penalties may have monetary or other nature.

13. Renewable Energy

The marketplace platform may be utilized to manage renewable energy generation sources and related energy consumption. A utility company or other party involved in utility grid management may issue specific DR bids associated with generation of renewable energy. Retail customers may receive specific suggestions that may be coupled with monetary or other benefits to use certain circuits, devices, loads, appliances, or outlets during specific periods when certain renewable energy generation sources are producing or not producing power.

In one aspect, the software may create or use a pre-created database of users that identify themselves as willing to use as much renewable energy as possible. Such database may include indication of circuits, devices, loads, appliances, or outlets that may be used during periods when renewable energy is most accessible; for example, using solar power during sunshine periods, such as during the summer.

Information about users' intention to maximize or minimize renewable energy consumption may be obtained by the software through multiple ways including:

• • Sending a specific request to the user;
  • Receiving such information from a utility company or other third party; and/or
  • Obtaining data from a third-party source such as an online database or other places.

In another aspect, a utility company or other party involved in utility grid management may decide to incentivize users with or without renewable energy consumption preferences to enter into specific DR bids during certain periods when there is an abundance of renewable power generated or, conversely, when there is a lack of renewable energy generation.

Incentivizing Retail Customers to Use More Renewable Energy

The software may analyze user consumption history to identify usage patterns of circuits, devices, loads, appliances, or outlets with or without renewable energy preferences. In cases when the software identifies that a user has preferences to use renewable energy, it may create a list of suggestions for circuits, devices, loads, appliances, or outlets usage based on the time of renewable energy availability. Alternatively, a user may proactively subscribe for the marketplace to use more renewable energy. In some instances, a user may subscribe some circuits, devices, loads, appliances, or outlets for automatic participation in renewable energy bids issued through the marketplace.

The software may present a report on the potential increase or decrease in renewable energy usage to a utility company. The report may include calculation of economic benefits achieved by shifting consumption to the periods with high renewable energy availability. Such benefits may be based on the difference of renewable energy generation costs and similar costs during periods when renewable energy is not available.

A utility company or other party involved in utility grid management may anticipate specific periods when renewable energy may be abundant such as sunny summer days. Alternatively, the software may create specific predictions for renewable energy availability based on weather forecasts, geographic location, seasonal shifts, and/or other factors.

When a utility company or other party involved in utility grid management anticipates these periods, it may direct software to issue an aggregated bid to the users in the identified list. Such bid may contain specific values such as:

• • overall amount of additional renewable energy to be sold;
  • aggregated load level expected;
  • determination of specific geography where the renewable energy may be delivered;
  • specific parts, regions, sections or branches of a utility grid where the renewable energy may be delivered;
  • specific time periods when the renewable energy may be delivered;
  • aggregated price range for the bid determining how much a utility company is willing to charge for the deliverable renewable energy; and/or
  • other parameters.

In one aspect, once such a bid is placed in the system, it is transferred to an online server (e.g., the cloud) by means of wireless network, wireless connection, or wired connection, through Internet or some other form of communication for further processing. The software in the cloud performs initial classification of the bid by matching the parameters of the bid with retail consumers in the identified list that may be eligible to respond to the call/contact. Such classification may involve filtering a consumer database(s) to identify those consumers that match required parameters such as geography and connection to a specific grid branch or circuit.

Once the software identifies the subset of consumers matching these parameters, it proceeds to a review of available loads that may participate in the consumption shift bid call by executing one or more of several steps:

The software reviews loads that were subscribed for participation in renewable energy bids by consumers within required periods. Such loads are then enrolled into the renewable energy consumption call automatically. The software calculates the amount of additional load achieved by triggering the subscribed loads. In cases when such amount is less than the amount of aggregated renewable energy bid, the software proceeds to the next step.

The software determines the remaining amount of renewable energy to be delivered as a difference between the aggregated bid and the amount of renewable energy to be delivered achieved by triggering subscribed loads.

The software determines what circuits, devices, loads, appliances, outlets or groups of circuits, devices, loads, appliances, outlets for an individual customer or group of individual customers may represent the loads that customers are likely to agree to change consumption patterns for, in case they receive a renewable energy bid notification. Such classification may be based on:

• • load size;
  • user consumption patterns;
  • pre-created database of loads that are most likely to react based on load name, location, size or other parameters;
  • past history of bids that user agreed to accept or reject (likelihood of bid success);
  • aggregated patterns for consumption and bid participation by other users; and/or
  • other parameters.

The software creates a combination of loads across multiple eligible users in a way that the sum of triggered loads equals or is less than the difference between the aggregated bid and the amount of renewable energy to be delivered achieved by triggering subscribed loads.

Such calculation may incorporate allowances for probabilities of user response success. The combination of loads is created in a way that it targets to prioritize loads under certain parameters such as:

• • Loads with larger size over loads with smaller size;
  • Loads that consumers are more likely to agree to turn on or off in case they receive a bid notification;
  • Past history of loads that consumers agreed to turn on or off; and/or
  • Other parameters.

When the combination of individual loads satisfying the parameters of a utility's aggregated bid is created, the software may send users individual bids. Each user may receive a single bid, multiple bids, or a combined bid grouping several circuits, devices, loads, appliances, or outlets.

Such bids may include specific instructions and suggestions for users to commit to a specific consumption behavior on identified circuits, devices, loads appliances, or outlets. The bid may contain a proposal for a monetary or other benefit that a user may receive in case the user agrees to accept the bid. A bid may be sent to a user in one or several forms including a text message, a phone call, an email, a bid through the app installed on a user's phone, tablet, or computer, a bid on user's online portal, or other form of bid. Such bid may contain the tools to execute the action in the form of links, buttons or other graphical images or text. By clicking, pressing, pushing or otherwise interacting with these tools, a user may send specific commands to the software and indicate acceptance or denial of the bid.

For example, a user may receive a bid from a utility company containing specific consumption parameters:

• • Specific circuit, device, load, appliance, or outlet name (e.g., “Would you agree to run your washing machine . . . ”);
  • Specific period when the user may use the circuit, device, load, appliance, or outlet (e.g., “ . . . between 2 pm and 4 pm today . . . ”);
  • Specific monetary or other benefit that the user may receive in case of accepting the bid (e.g., “ . . . and receive a special 10% discount for the consumed energy . . . ”);
  • Reason indicating renewable energy availability (e.g., “ . . . because your washing machine can be powered entirely by solar energy during this period.”); and/or
  • Tools to accept/deny the bid in the form of a question (e.g., “Would you like to accept the terms?”) and two push buttons (e.g., “Yes” and “No”).

In cases when a user agrees to accept the bid, the software may cause power supply shut on or off to the respective circuit, device, load, appliance, or outlet for the time period indicated in the bid. This operation may be required to ensure proper execution of the transaction and increase reliability of grid operations.

Incentivizing Retail Customers to Reduce Energy Consumption when Renewable energy generation is low or absent

During the periods when renewable energy generation is low or absent, the platform may provide a utility company or other party involved in utility grid management with tools to reduce energy consumption to meet specific predetermined load level achieved by base load generation capacities.

A utility company or other party involved in utility grid management may anticipate specific periods when renewable energy may be in deficit and energy demand must be satisfied with base load capacities. Alternatively, the software may create specific predictions for renewable energy availability based on weather forecasts, geographic location, seasonal shifts, and other factors.

When a utility company or other party involved in utility grid management anticipates these periods, it may direct software to issue an aggregated bid based on shortage of renewable energy to the users. Such bid may contain specific values such as:

• • overall amount of load reduction sought;
  • aggregated load level expected to achieve;
  • determination of specific geography where the load reduction is required;
  • specific parts, regions, sections or branches of utility grid where load reduction is required;
  • specific time periods when load reduction is required;
  • aggregated price range for the bid determining how much utility company is willing to pay for the overall load reduction; and/or
  • other parameters.

In one aspect, once such bid is placed in the system, it is transferred to a remote server (e.g., the cloud) by means of wireless network, wireless connection, or wired connection, through Internet or some other form of communication for further processing. The software on the server performs initial classification of the bid by matching the parameters of the bid with retail consumers in the identified list that may be eligible to respond to the call. Such classification may involve filtering a consumer database to identify those consumers that match required parameters such as geography and connection to a specific grid branch or circuit.

Once the software identifies the subset of consumers matching these parameters, it proceeds to review of available loads that may participate in the renewable energy DR call by executing one or more of several steps:

The software reviews loads that were subscribed for automatic renewable energy DR participation by consumers within required time periods. Such loads are then enrolled into the DR call automatically.

The software determines the remaining amount of load reduction as a difference between the aggregated renewable energy load reduction bid and the amount of load reduction achieved by triggering subscribed loads. In cases when the amount of load reduction achieved by subscribed loads is less than the amount of aggregated load reduction bid, the software proceeds to the next step. In cases when the amount of load reduction achieved by triggering the subscribed loads is higher than the amount of aggregated load reduction bid the software proceeds to determining the combination of the subscribed loads triggered by the bid.

The software determines what circuits, devices, loads, appliances, outlets or groups of circuits, devices, loads, appliances, outlets for an individual customer or group of individual customers may represent the loads that customers are likely to agree to turn on or off in case they receive a bid notification. Such classification may be based on one or more of:

• • load size;
  • user consumption patterns;
  • pre-created database of loads that are most likely to react based on load name, location, size or other parameters;
  • past history of bids that user agreed to accept or reject (likelihood of bid success);
  • aggregated patterns for consumption and bid participation by other users; and/or
  • other parameters.

The software creates a combination of loads across multiple eligible users in a way such that the sum of triggered loads equals or exceeds the difference between the aggregated load reduction bid and the amount of load reduction achieved by triggering subscribed loads. Such calculation may incorporate allowances for probabilities of user response success. The combination of loads is created in a way that it targets to prioritize loads under certain parameters such as:

• • Loads with larger size over loads with smaller size;
  • Loads that consumers are more likely to agree to turn on or off in case they receive a bid notification;
  • Past history of loads that consumers agreed to turn on or off; and/or
  • Other parameters.

When the combination of individual loads satisfying the parameters of a utility's aggregated bid is created, the software may send users individual bids. Each user may receive a single bid, multiple bids, or a combined bid grouping several circuits, devices, loads, appliances, or outlets. Such bids may include specific instructions and suggestions for users to commit to a specific consumption behavior on identified circuits, devices, loads, appliances, or outlets. The bid may contain a proposal for a monetary or other benefit that a user may receive in case the user agrees to accept the bid. A bid may be sent to a user in one or several forms including a text message, a phone call, an email, a bid through the app installed on a user's phone, tablet, or computer, a bid on user's online portal, or other form of bid. Such bid may contain the tools to execute the action in the form of links, buttons or other graphical images or text. By clicking, pressing, pushing or otherwise interacting with these tools, a user may send specific commands to the software and indicate acceptance or denial of the bid.

For example, a user may receive a bid from a utility company containing specific consumption parameters:

• • Specific circuit, device, load, appliance, or outlet name (e.g., “Would you agree to turn off your washing machine . . . ”);
  • Specific peak period when the user is committing to reduce or stop usage of the circuit, device, load, appliance, or outlet (e.g., “ . . . between 6 pm and 8 pm today . . . ”);
  • Reason indicating renewable energy availability (e.g., “ . . . because our grid will experience a deficit of renewable energy during this period.”);
  • Specific monetary or other benefit that the user may receive in case of accepting the bid (e.g., “You will receive $1 payment for agreeing to the terms.”); and/or
  • Tools to accept/deny the bid in the form of a question (e.g., “Would you like to accept the terms?”) and two push buttons (e.g., “Yes” and “No”).

In cases when a user agrees to accept the bid, the software may cause power supply shut off to the respective circuit, device, load, appliance, or outlet for the time period indicated in the bid. This operation may be required to ensure proper execution of the transaction and increase reliability of grid operations. Once the period lapses, the software returns power supply to the indicated circuit, device, load, appliance, or outlet. Alternatively, the power can be shut off and/or turned back on manually, such as by the customer.

14. Ad Hoc DR Participation by Retail Customers

A customer may proactively participate in ongoing DR bids, consumption shift bids, renewable energy bids, or other bids placed on the marketplace platform. In specific cases, such bids may be created on the platform as open for participation until a targeted load level is met.

In one aspect, the software may record specific bids or portions of aggregated bids that have not been fully or partially fulfilled by either users, circuits, devices, loads, appliances, or outlets subscribed for automatic bid participation or by users, circuits, devices, loads, appliances, or outlets that received specific bids and decided to reject such bids or remained unresponsive. In another aspect, the software may record specific bids or portions of aggregated bids that are being filled on an ongoing basis.

Such records may contain specific bid parameters comprising one or more of:

• • overall amount of load reduction sought;
  • aggregated load level expected to achieve;
  • determination of specific geography where load reduction is required;
  • specific parts, regions, sections or branches of utility grid where load reduction is required;
  • specific time periods when load reduction is required;
  • aggregated price range for the bid determining how much utility company is willing to pay for the overall load reduction;
  • specific price that a utility company is willing to pay for a unit of load reduction such as watt, kilowatt, volt, kilovolt, or other unit; and/or
  • other parameters.

Such bids may be recorded in a specific area of the platform where a user may review any or all outstanding bids and enroll specific circuits, devices, loads, appliances, or outlets or groups of circuits, devices, loads, appliances, or outlets into such bids. The software may pre-filter outstanding bids and demonstrate to the user only such bids where such user is eligible to participate. Such classification may involve filtering a consumer database to identify those consumers that match required parameters such as geography and connection to a specific grid branch or circuit.

To initiate such participation, a user may access a respective menu in a user interface of the software on the online server or in the app installed on user's device (phone, tablet, computer, etc.). Alternatively, a user may have an option to review ongoing bids on the marketplace by addressing specific menu item(s) in the form of a link, button or other graphical images.

Such bids may include specific instructions and suggestions for users to commit to a specific consumption behavior on identified circuits, devices, loads, appliances, or outlets. The bid may contain a proposal for a monetary or other benefit that a user may receive in case the user agrees to accept the bid. A bid may be viewed or received by a user in one or several forms including a text message, a phone call, an email, a bid through the app installed on a user's phone, tablet, or computer, a bid on user's online portal, or other form of bid. Such bid may contain the tools to execute the action in the form of links, buttons or other graphical images or text. By clicking, pressing, pushing or otherwise interacting with these tools, a user may send specific commands to the software and indicate acceptance or denial of the bid.

A user may enroll in one or multiple outstanding bids with any number of circuits, devices, loads, appliances, or outlets.

The invention may also use software to implement various aspects of the system for managing energy consumption described herein.

1. Software Architecture

The software running on or along with the invention explained herein comprises a complex of several components or each component individually. These components work together to enable proper work of algorithms, functions, features, controls and other options as described below.

The software comprises one or more of the following components:

• • Software code operating on the processor or connected to an energy management or other device (software at user's location);
  • Software code operating on a remote server or “cloud” (software in the “cloud”);
  • Software code operating on user's device used for monitoring and control such as a phone, tablet, computer or any other device used for monitoring and/or control purposes (an app and webpage); and
  • Software code operating on servers and/or computers belonging to utility company.

2. Installation—Set Up

In one aspect, once the system is activated, a processor then runs the initial start-up script and launches the software responsible for ongoing operations. In one aspect, a wireless communication chip on a device as part of the invention herein creates a temporary wireless network for user to connect and perform initial set-up operations.

As a part of the start-up process, the processor sends test signals wirelessly or along communication lines embedded in the device. The signals, among other things, enable the processor to identify the number and grade (amperage) related to the device or system.

A user connects an input device (such as a phone, tablet, laptop, computer, computer processing unit, or any other computing means) to the device using either a temporary wireless network, wireless connection, or wired connection.

In one aspect, a user may launch a web browser or some other communication/control means and input specifically designated IP address, or open special software (an app, for example) that has been pre-installed on an input device through, for example, any type of online marketplace such as Apple AppStore, Google Play, Microsoft Store or others, or downloaded from other online resources such as a manufacturer's website or provided on a physical storage means such as a flash card, a CD disk or others. The information may be installed by other means, such as storage device connected to input device.

On the web page, or otherwise using the application, the user encounters a series of set up screens where the user performs certain actions and/or provides certain information comprising one or more of the following:

• • Creates a personal account by creating a login and password that can be used for online access in the future;
  • Provides an e-mail address and any other contact information as may be needed for contact between the device and the user in the future;
  • Provides local wireless network (or other communication or network) credentials so that the device may connect to the Internet via said wireless network (or connected by other means);
  • Inputs a specific name for a device or aspect of the device;
  • Provides information about the electrical utility company providing electrical service to the building (if applicable);
  • Provides information about any smart home or other apps used in or on the premises; and/or
  • Provides information about available renewable energy sources (for example, solar panels) and power storage equipment installed in the building.

In one aspect, in case a local wireless network is not available, a user may establish a connection between a device and a wireless adapter installed anywhere in the building. Such connection involves data transfer through a powerline. The powerline wireless adapter then connects to a local wireless network. In this case, the device sends/receives data through its power line into the electrical grid of the building. The data is then sent/received by the powerline adapter and transmitted to local wireless network connected to the Internet.

In one aspect, once a user finishes the initial setup including connection, such as to the Internet, the user performs certain additional actions and/or provides certain information including (but not limited to):

• • Confirms geographical location determined by the software;
  • Provides information about the building such as number of floors, square footage, age of the building, etc.; and/or
  • Provides information about building occupants such as their number, age, etc.

Some information requested during the setup process may be omitted by the user.

The user then is offered to pair his/her input device(s) (for example, phone, tablet, or computer) with the device. In this case, user's input device unique ID is registered in the software.

3. Data Monitoring, Transfer, and Storage

Once the initial set up process is complete, the device starts monitoring energy consumption by, for example only, measuring electrical current or energy expended, or estimating energy consumption. In addition, in one possible aspect, the software may measure electrical voltage (or some other unit/parameter) with a voltage sensor or sensors in the device. The information may then be saved in the memory of the device and/or transmitted to the online server through the Internet connection, or otherwise communicated wirelessly or with a wire connection to a user or some other device (e.g., a phone, tablet, computer, or storage apparatus).

The data received from devices installed on energy consumer's premises is classified based on the information and analyzed by an algorithm determining consumption (see, e.g., below “Learning by devices”).

Data may then be stored on a hard drive memory for future analyzes of consumption trends over certain periods of time, or stored elsewhere, such as on the cloud-based servers. In one aspect, data is also aggregated to provide a combined view over total power consumption of the building/premises as well as consumption of certain circuit(s) or circuit groups, consumption of certain device types, consumption of certain loads, consumption of certain outlets, consumption of certain appliances, consumption of certain rooms, etc.

Data stored on the devices or elsewhere may then be copied, stored, and/or shared at the online server through connection to the Internet, or otherwise copied, stored, and/or shared by some other means (e.g., a wired connection or other type of wireless connectivity).

4. Learning and Identification of Devices

Once devices start receiving or generating data on energy consumption, the software, in some embodiments, classifies and analyzes the incoming data to identify specific electric loads.

The software monitors energy consumption. When consumption changes from a steady level detected by the device (can be a change from zero consumption to some higher number, for example), the software creates a record, sometimes referred to herein as an “event”. Such event may be, for example, the one-time or incremental change in consumption.

Each event is analyzed to determine one or more electric load(s) causing such event. As a part of the analysis, the software defines several parameters of the data such as, by way of example: square of the area under the consumption curve line, height of curve peaks, local maximums and minimums on the curve, intervals between local maximums and minimums, frequency characteristics, and/or other parameters.

The software creates a unique record in a database for the loads causing an event. Such record or records, for example, of an event caused by a load, appliance, outlet, etc., is assigned with a unique ID and the values of all determined parameters. Once the record is created, the software proceeds to identification of the load, appliance, outlet, etc.

The identification can be done in several ways including, but not limited to:

Through Interaction with User

A user may be asked for several descriptive characteristics of a new device including but not limited to:

Mobility of the load, appliance, outlet, etc., i.e. whether the load, appliance, outlet, etc., can be relocated by user to a different circuit/area in the premises in the future.

Through Analysis of Past Data

Upon creation of a record, the software uploads the record onto, for example, the online server through Internet connection. In one aspect, at the server, the software compares the newly uploaded record with other records collected from the same or different users.

The software specifically compares one or more parameters, including but not limited to:

• • square of the area under the consumption curve line;
  • height of curve peaks;
  • local maximums and minimums on the curve;
  • intervals between local maximums and minimums;
  • frequency characteristics; and/or
  • household parameters such as number of occupants, age and size of the house.
    Once the software identifies previous records with parameters that match the new record's parameters, the software assigns the new record with the name of a load, appliance, outlet, etc. or group of loads, appliances, outlets, etc. that were used in previous records.

The record originally stored is updated with the name of a load, appliance, outlet, etc. or group of loads, appliances, outlets, etc. through Internet or other connection(s).

Backward Device Recognition/Analysis

Once a new record is created, the software applies the parameters of the new record to analyze previous consumption records (events) that have not been assigned with a specific load, appliance, outlet, etc. or group of loads, appliances, outlets, etc.

In one aspect, the software analyzes past consumption on the load where the newly created record was created. Upon completion of such analysis, the software may check other loads in the premises.

Once the analysis is completed, the software matches the new record with historical events in the consumption database that a.) have not been assigned to any other record in device database and b.) match consumption characteristics of the new record.

5. Monitoring and Reporting of Regular Consumption

The software records data on energy consumption per load, appliance, outlet, etc. or group of loads, appliances, outlets, etc.

A user has access to the data through, by way of example only:

• • a web portal where, in one aspect, such user inputs unique credentials to access consumption data;
  • an app installed on user's mobile phone, tablet, and/or computer; and/or
  • any other device capable of presenting data in graphical, numerical format, and/or other format (e.g., a screen on a load or installed/located in or near the premises).

Energy consumption can be represented, for example, by using one or multiple methods (including combination of such methods):

• • Using different metrics

Energy consumption can be presented in various metrics that provide a user with most valuable insights. Such metrics may include, but are not limited to, kilowatt-hours (kWh), kilowatts (kW) and other metrics including but not limited to monetary values (see “Calculation of monetary amounts and ongoing power bill” below).

• • Per load, appliance, outlet, etc. or group of loads, appliances, outlets, etc.

Energy consumption data may be shown per specific energy consuming load, appliance, outlet, etc. (for example, thermostat, “Refrigerator”, “TV Main room,” etc.) or group of loads, appliances, outlets, etc. paired either by certain characteristics such as load, appliance, outlet type (for example, “All TVs”), location (“All devices on the 1st floor”), circuit connection (“Devices plugged into sockets in Main room”) or other characteristics. Some of mentioned grouping options may be preprogrammed in the software while others may be created by a user individually.

To create a group specified by a certain characteristic, a user may use an interface that lists all load, appliance, outlet, etc. or group of loads, appliances, outlets, etc. that have been previously identified in the premises. The interface enables user to mark specific load, appliance, outlet, etc. or group of loads, appliances, outlets, etc. and group them into a new group with custom name.

Within a Specified Time Period

Energy consumption data may be presented as accumulated statistics over certain period(s) of time such as hour, day, week, month, etc. In addition, energy consumption data may be presented as a real-time number(s) reflecting current energy consumption or as a statistical number that is being updated in real-time.

A user may change the settings and representations of the data by switching demonstrated time periods. In addition, a user may specify and compare certain data sets such as monthly consumption (for example, energy consumption in July vs. February). This data may also be represented and analyzed as other numerical data, such as a financial figure(s) (e.g., the cost of consumption).

6. Calculation of Monetary Amounts, Ongoing Power Bill, and Forecasted Bill

Using the energy consumption data stored, for example, in the device's memory and at the online server, the software may perform calculations to convert such data into monetary values reflecting the costs of energy incurred by a user.

In one aspect, to perform such calculations, the software utilizes the identification of a local power utility provided by a user during the initial set-up process. If a user does not specify a particular utility provider, the software may assign a utility company based on geographical location of the premises or use standard or average terms defined for specific geographic locations where multiple utility providers are available.

The software addresses a pre-created database that lists specific rules and values (rates) used by each listed power utility company. Applying these rules, the software performs calculations to convert consumption metrics such as kilowatt-hours (kWh), kilowatts (kW), and other metrics, into monetary values.

The software applies said rules and rates specified for a particular power utility to consumption metrics measured for whole premises, specific circuit or group of circuits, and/or specific load, appliance, outlet, etc. or group of loads, appliances, outlets, etc. Thus, the software calculates and converts consumption metrics for a whole premises, specific circuit or group of circuits, and/or load, appliance, outlet, etc. or group of loads, appliances, outlets, etc. into monetary values.

A user may be asked to provide additional information such as billing cycle start date. In addition, a user may be asked to provide online credentials for a utility company account (see “Access to utility company online account”).

Assuming certain dates as billing cycle starting points and certain number of days as cycle period, the software calculates monthly bills that resemble actual bills received by a user from a power utility company. At the same time, the software provides an ability to further review and analyze such bills by granular data composition reflecting each circuit or group of circuits, or each load, appliance, outlet, etc. or group of loads, appliances, outlets, etc.

Alternatively, a user may specify certain periods in time for which the software will perform a calculation(s) of monetary values. Such periods may include year, quarter, month, week, day or any other custom period defined by a user. The result of such calculation(s) will be a report similar to a power bill that would reflect the total consumption and monetary amounts for the specified period(s) as well as a detailed analysis by each circuit in a premises or group of circuits, or each load, appliance, outlet, etc. or group of loads, appliances, outlets, etc.

In Real-Time

The software will perform calculations for real-time consumption to provide users with real-time monetary values. The real-time monetary values will reflect the amount of money currently spent for energy. These values may come in formats of dollars per hour/minute/second and may be provided for a whole premises, specific circuit or group of circuits, and/or specific load, appliance, outlet, etc. or group of loads, appliances, outlets, etc.

In one aspect, to calculate said values, the software takes current consumption in kilowatts and extrapolates it for a defined period(s) (hour, minute, or second) as if such consumption remains at a steady level for such a period(s). The software applies a local utility company's rules and rates to calculate the monetary value of current consumption as defined above. This monetary value is presented to a user in an aggregated manner and in a detailed breakdown. For example, such a user may receive information on the total monetary amount representing a full house current power consumption as well as monetary amounts for each load, appliance, outlet, etc. or group of loads, appliances, outlets, etc. that consume power at the moment.

Forecast

The software may also forecast the monetary value of energy consumed over future periods. Forecasted periods may include, for example, the current billing cycle, year, quarter, month, week, day, and/or any other period.

To perform the forecast, the software executes an ongoing analysis of past energy consumption trends by load, appliance, outlet, etc. and circuit(s) level. The analysis may include additional factors such as seasonality, weather forecasts, and others. In addition, such an analysis may use anonymized consumption data patterns revealed across the user database.

Once such an analysis reveals statistically sound trends including average consumption, minimums, maximums, correlations and other parameters, the software forecasts future consumption by extrapolating existing consumption history through the application of revealed trends.

7. Connection with Smart Home Platforms

During the initial set-up process, a user may be asked whether the premise has any smart home hubs or platforms installed. A smart home hub is a device that connects some or all devices in the premises with connectivity features and, in some cases, may allow for communication across such devices. Some of the smart home hubs include Samsung SmartThings, Amazon Echo, Apple HomeKit, Philips HueBridge, and others.

The software taught herein may connect to a smart home hub installed in a premises. Such connection may be performed through Wi-Fi network or any other means of communication. The software then obtains a list of all other devices connected to the smart home hub including multiple characteristics, such as:

• • names of connected devices;
  • unique identification numbers;
  • their location in the premises;
  • their functionality;
  • ability to turn on/off in response to a signal sent through the smart home hub;
  • manufacturer's characteristics such as targeted energy consumption; and/or
  • other parameters.

In some cases, the software may address a database located on the online server or other third-party servers to obtain additional characteristics of connected devices.

Once connection to a Smart Home platform is established, the software starts exchanging data and commands about specific devices including:

• • current status (on/off);
  • current activity including type of performed action, length of such performance, etc.;
  • any existing schedules (repeating and one-time) for operations of a connected device;
  • commands for turning on/off a connected device;
  • commands to adjust specific schedules, intensity or type of certain activities of a connected device; and/or
  • other data and commands as may be required.

The software may create a separate database of all devices within a house connected to a Smart Home platform. Alternatively, the software may add specific records about Smart Home connectivity to existing database of all devices identified within a house.

8. Remote Control

The software allows for a user to have control over energy consumption on specific circuits and loads, appliances, outlets, etc.

A user may choose to turn on/off or adjust the energy supply to each circuit(s) within the circuit breaker panel or to certain loads, appliances, outlets, etc. and groups of loads, appliances, outlets, etc. that are connected with a Smart Home platform.

To execute a remote control function, a user may access a screen on, for example, a phone, tablet, or computer.

Scheduled Control

The software allows for a user to create a schedule for circuit(s) and loads, appliances, outlets, etc. to turn on/off or adjust at specifically or automated scheduled times. For example, a hot water heater or the circuit to such a heater may turn off during the day while a user is out of the home. These times may be specifically scheduled by a user, or they may be suggested or implemented by the software based on typical usage by electricity consumers. For example, during winter months, the software may suggest to a user to turn off or turn down a premise's heat during evening hours when a consumer is sleeping or during the day when consumers are away from the premises.

Control from Messages

The software may be enabled to send messages to a user via a phone, tablet, computer or other device to turn on/off circuit(s) or particular loads, appliances, outlets, etc. The user, based on such “pings,” may have the option to accept such notifications by turning on/off or otherwise adjusting circuit(s) or loads, appliances, outlets, etc. depending on applicability of a user. For example, a user may receive a notification on a cell phone from the device and software taught herein informing the user that because it is during the day when the user is typically not on the premises (based on, for example, input from the user or the software noticing patterns of very little electricity typically being used generally at this time (e.g., all the lights in the home are usually off)) the user will save electricity by turning off or adjusting the heat. The software may inform the user of how much the user will save in electricity costs if the user turns off or turns down the heat for a set period of time. The software may ask the user when the user plans to return to the premises so the software can turn back on or turn back up the heat.

The device and software may similarly notify a user that a certain load, appliance, outlet, etc. is left on when, for example, it is typically off at a certain time. If the user forgot to turn off a light for example, the notification will give the user the option to turn off the circuit or the light.

Control Based on User's Location

The software may be enabled to get access in real time to user location data and calendar records stored on user's mobile phone, tablet, computer or other device. Based on the information, the software may turn on specific circuits, loads, appliances, outlets etc. that have been turned off previously. For example, a user may manually turn off water heater when she leaves premises in the morning and the software may turn the water heater back on when it receives a signal that the user is coming back.

9. Access to Utility Company Online Account

During the initial set-up process, a user may be asked to provide online credentials for an account with a local utility company. The software uses the credentials to obtain some or more of the following data about the user's energy consumption:

• • Utility company name and location;
  • User location;
  • User rate schedule;
  • User consumption and demand history in kilowatt-hours, kilowatts, and money;
  • Lengths of past billing cycles and current billing cycle; and/or
  • Other data as may be required.

Obtained data may be used in multiple ways including but not limited to:

• • Improvement of ongoing bill calculations performed by the software through adjusting rate schedule calculation rules;
  • Calculation of certain energy efficiency measures (actual or proposed) as compared with past consumption;
  • Ensuring that the user's bill is calculated correctly and the user is charged correctly by the utility company; and/or
  • Other needs as may be required.

10. Reporting of Abnormalities (e.g., a Light on the Premises is On)

The software analyzes stored consumption data in order to find repeatable consumption patterns. The scope of such analysis includes sampling on specific loads, appliances, outlets, circuits, time periods, week days, months, etc.

To perform more accurate analyses, the software may utilize anonymized data on energy consumption for other users, loads, appliances, outlets, circuits, time periods, week, days, months, etc. stored at, for example, an online server. To do so, the software may search for similarities in consumption patterns linkable under various parameters such as:

• • geographical location;
  • weather data;
  • multiple house characteristics such as size, age, etc.;
  • multiple household characteristics such as number of people, age, gender etc.;
  • load, appliance, outlet, etc. characteristics and features;
  • circuit characteristics including names, amperage, etc.;
  • time of the day consumption patterns;
  • patterns repeating across certain days including comparison of business days vs. weekends; and/or
  • seasonality factors including summer/winter patterns and others.

Once the software identifies repeatable patterns in a user's energy consumption, it compares any new consumption data to such established patterns. Such comparison is performed over analysis of multiple parameters of current consumption such as:

• • day and time of consumption;
  • circuit where consumption is recorded;
  • specific load, appliance, outlet, etc.;
  • length of consumption;
  • watts/amps drawn over the consumption period as well as specific peaks; and/or
  • other parameters.

In cases when certain parameters of current consumption deviate from the established pattern(s), the software may record an event reporting consumption abnormality. Such events are analyzed by the software in an attempt to identify the cause of the consumption abnormality. Some examples of such causes may include:

• • a user forgot to turn on/off specific equipment such as lights or stove;
  • equipment malfunctioning;
  • equipment wear;
  • unusual weather conditions; and/or
  • unusual user behavior.

Depending on the identified cause, the software may send a user a notification in one or several forms including a text message, a phone call, an email, a notification through the app installed on a user's phone, tablet, or computer, a notification on user's online portal, or other form of notification.

Such notification may include information about an identified event, such as its cause. The notification may include information on the load, appliance, outlet, etc. and circuit on which abnormal consumption was noticed, as well as description of the abnormality such as time and length. The notification may also include a projected calculation of additional costs that a user may incur over the course of the abnormal event, if for example a light is accidentally left on. Such calculation may be based on consumption characteristics such as watts and volts, time and length of the event, local utility company tariffs, potential equipment replacement costs, and/or other factors.

In addition, the notification may include a specific proposal for action as well as provide a user with certain tools to execute such action. Such proposal may take the form of a specific suggestion to perform certain steps to remedy the abnormality. Such steps may include turning on/off or adjusting specific loads, appliances, outlets, etc. and/or circuits.

In one aspect, the tools to execute the remedial action may take the form of links, buttons or other graphical images embedded into the notification. By clicking, pressing, pushing or otherwise interacting with these tools, a user may send specific commands to the software and initiate certain remedy actions (e.g., a notification would pop up on a mobile phone with a button allowing a user to turn off a light or turn down the heat).

An example of such notification would be a pop-up message on smartphone screen with one or more of the following, for example:

• • brief description of an abnormal event (“You forgot to turn off the lights in your bedroom”);
  • projected costs calculation (“If you leave them on for the day, you will spend an additional $2 in energy costs”); and/or
  • tools to remedy the event in the form of a question (“Would you like to turn them off?”) and two push buttons (“Yes” and “No”).

11. Power Outage (Utility Company Reporting+Lighting)

The software monitors voltage level through, for example, voltage sensor(s) installed or included in the device taught herein. If the software records significant voltage fluctuations or complete loss of voltage, the software may initiate a power outage procedure.

Under this procedure, the software may send a report to a local utility company using, by way of example, an installed wireless chip capable of sending and receiving a signal through cellular towers, through the Internet, or by some other means. Such report may contain data about loss of power including:

• • day and time of the event;
  • geographical location including address;
  • contact information of the household; and/or
  • other information.

In order to avoid unnecessary reporting on power outages in cases when such an outage may be caused by certain events or actions specific to the premises (e.g., tripped breaker, electrical works on site, etc.), the software may perform a check-up procedure prior to sending the report to a local utility company.

To perform the check-up procedure, the software may send outage data to an online server where such data is analyzed and compared with data received from other devices installed in geographical proximity. When certain geographical and time patterns are observed by the software running on the online server, it may send a power outage report to a local utility company.

When a power outage is observed in a premises, the software may send a user a notification in one or several forms including a text message, a phone call, an email, a notification through the app installed on user's phone, tablet, or computer, a notification on user's online portal, or other form of notification.

Such notification may contain a proposal for the user to indicate whether the outage is caused by certain events or actions specific to premises (e.g., tripped breaker, electrical works on site, etc.).

In addition, a user may have an option to log into the associated account through an online portal, app, or other means, and set a status indicating that the user's premises may be subject to a power outage caused by certain events or actions specific to the premises (e.g., tripped breaker, electrical works on site, etc.). Alternatively, such status may be set by an electrician performing specific electrical works or a utility company.

In a case when the software receives such a notification from a user, the software gives such outage event a status that does not trigger the report to the utility company.

12. Energy Consumption Trends Analysis (Energy Audit)

The software may perform analysis of a user's consumption trends and patterns and create certain recommendations and suggestions based on such an analysis. The frequency of the analysis may be predetermined with regular intervals such as day, week, month, quarter, year or any other interval. Alternatively, the frequency may be determined by a user on a custom basis including an ability to launch such analysis upon request.

Analysis of consumption trends is designed to identify certain repeatable actions and events in a household's energy consumption, locate specific equipment units responsible for certain portions of energy consumption, and create detailed recommendations and proposals on energy savings specific to each individual household. An analysis may be based on certain data such as:

• • geographical location;
  • weather data;
  • multiple house characteristics such as size, age, etc.;
  • multiple household characteristics such as number of people, age, gender, etc.;
  • specific device characteristics and features;
  • circuit characteristics including names, amperage, etc.;
  • time of the day consumption patterns;
  • patterns repeating across certain days including comparison of business days vs. weekends;
  • seasonality factors including summer/winter patterns and others;
  • day and time of consumption;
  • length and frequency of consumption;
  • watts/amps drawn over the consumption period as well as specific peaks;
  • specific settings on certain devices including thermostat settings;
  • anonymized similar data received from other users; and/or
  • other parameters.

The outcomes of the analysis may include specific insights and personalized action recommendations for a user to decrease power consumption and save money on an energy bill. These action recommendations may address specific user behavior patterns that may include recommendations on usage of specific energy consuming equipment in specific areas of the house during specific time periods. An example of such recommendation may be an indication that a user typically keeps lights on in a bedroom during daytime and a suggestion to turn these lights off. Such recommendation may be accompanied with a calculation of how much electricity the addressed equipment consumes over the course of a month, a year, or any other time period as well as calculation of the costs that a user incurs due to the analyzed behavior pattern.

In addition to the behavioral recommendation, the software may include a suggestion to automate certain actions leading to improvements in energy consumption. Such automation may involve setting up certain schedules for turning on and off specific circuits and/or turning on/off or adjusting devices. The suggestion may describe a specific consumption pattern identified by the software and a description of a solution suggested to a user. For example, the software may suggest that it will automatically turn off the circuit feeding the lights in the bedroom from 10 am to 4 pm during workdays; it may turn off one or more particular lights; or it may change or adjust thermostat settings.

13. Suggestion of Utility Plans

Within certain markets where a user may choose a specific utility provider and a specific utility plan, the software may provide certain recommendations on choosing a utility plan and perform necessary actions required to switch to a chosen utility plan.

The software may use certain information provided by a user as well as other information including:

• • geographical location;
  • address;
  • utility company name and location;
  • user location;
  • user rate schedule;
  • user consumption and demand history in kilowatt-hours, kilowatts, and/or money;
  • lengths of past billing cycles and current billing cycle; and/or
  • other data as may be required/informative.

The software may use various sources to receive information on specific terms of utility plans in different utility territories including:

• • a pre-created database stored in device memory, online server, or other location;
  • various online sources such as utility company websites, online repositories, and other online libraries;
  • user's online account with utility company; and/or
  • third-party websites.

A user may request the software to perform a utility plan analysis by accessing a respective menu and choosing appropriate action in a user interface of the software on the online server or in the app installed on user's device (phone, tablet, computer, etc.) or by some other interface means. Alternatively, the software may initiate the analysis, from time to time, on a preset schedule. A user may change the schedule of the analysis or otherwise program timing of the analysis.

The analysis may include calculation of a user's energy bill based on the past consumption history. Such consumption data may be applied to multiple terms of various utility plans. An array of modeled energy bills may be created to identify the lowest energy bill and a utility plan that results in lowest costs to the user. Such an analysis may be based on the energy bills of other energy consumers in proximity to a user.

After completion of the analysis, the software may generate a report describing findings of the analysis. The report may include details of analyzed utility plans as well as recommendations on plan switching based on the performed analysis. Such recommendations may include specific indication of projected savings that a user may experience in case of switching a current utility plan to the plan identified by the software as the most beneficial under a user's specific consumption patterns.

The report may also contain an action section including a button, link or other form of user interaction form, which a user may initiate to transition to the recommended utility plan. In cases when a user decides to initiate such transition, a user may be asked to provide certain personal data as well as authorization to perform such transition. In a preferred embodiment, after receipt of such data and authorization, the software will proceed with the switch process by contacting the chosen utility provider, communicating user's data and chosen plan, and performing other actions necessary for the transition.

14. Recommendations on Appliance Maintenance and Replacement

The software may perform analysis of consumption trends and patterns of individual devices and create certain recommendations and suggestions for potential issues and replacements based on such analysis. The frequency of the analysis may be predetermined with regular intervals such as day, week, month, quarter, year or any other interval. Alternatively, the frequency may be determined by a user on a custom basis including an ability to launch such analysis upon request.

The software analyzes stored consumption data per individual device in order to find repeatable consumption patterns. The scope of such analysis includes sampling on specific loads, appliances, outlets, time periods, weeks, days, months, etc.

To perform more accurate analyses, the software may utilize anonymized data on energy consumption patterns received from other users on specific loads, appliances, outlets, time periods, weeks, days, months, etc. stored at, for example, an online server. Another means of analyzing, in one aspect, is to use information from a database storing energy consumption patterns for various devices (e.g., appliances) received from, for example, device manufacturers. To do so, the software may search for similarities in consumption patterns linkable under various parameters such as:

• • geographical location;
  • weather data;
  • multiple house characteristics such as size, age, etc.;
  • multiple household characteristics such as number of people, age, gender, etc.;
  • load, appliance, outlet, etc. characteristics and features;
  • time of the day consumption patterns;
  • patterns repeating across certain days including comparison of business days vs. weekends; and/or
  • seasonality factors including summer/winter patterns and others.

Once the software identifies repeatable patterns in an individual device energy consumption, it compares any new consumption data to such established patterns. Such comparison is performed over analysis of multiple parameters of current consumption such as:

• • day and time of consumption;
  • specific load, appliance, outlet, etc.;
  • length of consumption;
  • watts/amps drawn over the consumption period as well as specific peaks; and/or
  • other parameters.

Analysis of consumption by individual device is designed to identify multiple parameters:

• • Proper working state of an individual device

In cases when certain parameters of current consumption deviate from the established pattern(s), the software may record an event reporting consumption abnormality. Such events are analyzed by the software in an attempt to identify the cause of the consumption abnormality. Some examples of such causes may include device improper functioning due to normal wear, breakage of specific device parts (sensors, motors, etc.) and others.

Depending on the identified cause, the software may send a user a notification in one or several forms including a text message, a phone call, an email, a notification through the app installed on a user's phone, tablet, or computer, a notification on user's online portal, or other form of notification.

Such notification may include information about an identified event, including its cause. The notification may include information on the load, appliance, outlet, etc. on which abnormal consumption was noticed, as well as a description of the abnormality such as time and length. The notification may also include a projected calculation of additional costs that a user may incur over the course of the abnormal event, if for example an air conditioner keeps running due to a bad temperature sensor. Such calculation may be based on consumption characteristics such as watts and volts, time and length of the event, local utility company tariffs, potential equipment replacement costs, and/or other factors.

In addition, the notification may include a specific proposal for action as well as provide a user with certain tools to execute such action. Such proposal may take the form of a specific suggestion to perform certain steps to remedy the abnormality. Such steps may include turning on/off or adjusting/changing specific loads, appliances, outlets, etc. and/or circuits.

In one aspect, the tools to execute the remedial action may take the form of suggestions to replace or service a device that has been identified with abnormal consumption. Such suggestion may include specific indications in the form of links, buttons or other graphical images or text proposing a purchase of a new device or appliance or order maintenance service for the device.

In another aspect, the tools to execute the remedial action may take the form of links, buttons or other graphical images embedded into the notification. By clicking, pressing, pushing or otherwise interacting with these tools, a user may send specific commands to the software and initiate certain remedial actions (e.g., a notification would pop up on a mobile phone with a button allowing a user to turn off a specific device).

An example of such notification would be a pop-up message on a smartphone screen with one or more of the following, for example:

• • brief description of an abnormal event (“Your refrigerator has been consuming more power over the past two weeks”);
  • identified potential cause (“It looks like the motor needs service”);
  • projected costs calculation (“Over the next month, you will spend an additional $5 in energy costs due to the bad motor”); and/or
  • tools to remedy the event in the form of a question (“Would you like to schedule a technician's visit?”) and two push buttons (“Yes” and “No”).

Potential Replacement of Devices and Appliances with Energy Efficient Analogs

The software may seek for potential replacements for individual devices. The search may be targeted towards achieving additional energy savings by locating more energy efficient options that may replace existing devices and appliances in a user's household.

The search may be structured to compare existing consumption parameters and patterns of devices and appliances installed in a user's household and consumption parameters and patterns of devices and appliances available on the market. The software may use various sources to receive information on specific consumption parameters of various appliances and devices available on the market including:

• • a pre-created database stored in device memory, online server, website, or other location;
  • various online sources such as device manufacturing company websites, online repositories, and other online libraries; and/or third-party websites.

The software may ask a user to provide additional parameters and characteristics of existing devices that cannot be identified through energy consumption analysis. For example, the software may ask for a size of a TV in living room or specific light bulb form. Alternatively, for devices that have connectivity features, the software may obtain such parameters and characteristics via connection to Smart Home platforms.

The software may use certain parameters and characteristics of existing devices to search for available analogs. These parameters and characteristics may include:

• • device name;
  • energy consumption in watts, volts and/or amps;
  • device size;
  • device function;
  • additional features built into device;
  • frequency of usage;
  • length of usage;
  • multiple house characteristics such as size, age, etc.;
  • multiple household characteristics such as number of people, age, gender, etc.;
  • time of the day consumption patterns; and/or
  • other parameters and characteristics.

Once the software obtains the data on energy consumption parameters and patterns as well as other characteristics of existing appliances, it may search for potential replacements matching set parameters and characteristics. Upon identification of potential replacements, the software may create various models of energy consumption for such replacements. These models may include existing user energy consumption patterns. The software may calculate the amount of energy that may be potentially consumed by the identified replacements in case existing devices and appliances are replaced with the new devices and appliances.

Then the software may calculate monetary values for the calculated energy consumption of the new devices and appliances. To perform the calculation, the software may use existing utility plan data or other energy tariff information.

Once such calculation(s) is performed, the software may compare energy consumption by existing devices and appliances with forecasted energy consumption of devices and appliances identified as potential replacements. Such comparison(s) may include:

• • energy units (watts or volts consumed);
  • monetary values (potential savings achieved by replacement);
  • sustainability metrics (savings in CO2 emissions and other environmental impact metrics);
  • non-monetary benefits (improvement of house energy efficiency status, qualification for sustainability awards and certificates, etc.); and/or
  • other parameters.

Depending on the results of the analysis, the software may send a user a notification in one or several forms including a text message, a phone call, an email, a notification through the app installed on a user's phone, tablet, or computer, a notification on user's online portal, or other form of notification.

Such notification may include information about potential monetary savings and other outcomes that user may achieve by switching to the new devices and appliances. The notification may include information on the potential replacements such as device name, specific characteristics, energy consumption parameters, and other information. The notification may also include a projected calculation of additional costs that a user may incur over the course of life of existing devices and appliances. Such calculation may be based on consumption characteristics such as watts and volts, time and length of consumption, local utility company tariffs, potential equipment replacement costs, and/or other factors.

In addition, the notification may include a specific proposal for action as well as provide a user with certain tools to execute such action. Such proposal may take the form of a specific suggestion to perform certain steps to purchase or replace existing devices and appliances.

In one aspect, the tools to execute the action may take the form of specific indications in the form of links, buttons or other graphical images or text proposing a purchase of a new device or appliance or request additional information on the device.

In another aspect, the tools to execute the action may take the form of links, buttons or other graphical images embedded into the notification. By clicking, pressing, pushing or otherwise interacting with these tools, a user may send specific commands to the software and initiate certain actions such as purchase of a new device.

An example of such notification would be a pop-up message on smartphone screen with one or more of the following, for example:

• • brief description of an analyzed device (“Your refrigerator has been consistently consuming more energy than existing analogs”);
  • projected savings calculation (“In case you decide to purchase a new energy efficient refrigerator, you may save $70 every year in energy costs”); and/or
  • tools to execute the action in the form of a question (“Would you like to learn more about energy efficient refrigerator options?”) and two push buttons (“Yes” and “No”).

15. Vacation Package

The software may provide a user with an option to use a set of rules targeted at energy management during long periods of absence. This set of rules may be called a “vacation package,” for example.

Such set of rules may be developed and updated manually by a user or created and updated with pre-programmed algorithms. Alternatively, a mix of the two approaches (manual and pre-programmed) may be used.

Vacation package is aimed at optimizing energy consumption during the periods when a user stays away from home for extended period(s) of time that is longer than typically observed absences.

Vacation package consists of a number of rules for turning on/off and/or adjusting specific devices, loads, and/or circuits or groups of devices, loads, and/or circuits. In one aspect, such rule may include specific indication of:

• • Individual device or circuit or group of devices or circuits that fall under the respective rule;
  • Specific timing for turning on and off or adjusting said devices and/or circuits;
  • Identification of specific days or other periods when the rule is activated (for example, daily, hourly, or twice per hour in the period from 6 pm to 9 pm on weekends etc.); and/or
  • other parameters.

A set of rules may consist of one or more rules activated simultaneously or during different time periods.

In one aspect, a user may create a set of rules by accessing a respective menu and setting up appropriate rules in a user interface of the software on the online server or in the app installed on user's device (phone, tablet, computer, etc.).

Alternatively, the software may design or have a set of pre-programmed rules. In one aspect, setting such pre-programmed rules may include analysis of specific devices or circuits and/or groups of devices or circuits. The software may look for specific parameters identifying devices and/or circuits that may be turned on and off or adjusted during a user's long absence.

For example, the software may be looking for a device and/or circuit with a name “Water heater” or “Boiler”. Once such device and/or circuit is identified, the software may create a rule that assumes turning off said device/circuit while user is absent. In another example, the software may be looking for a device and/or circuit with a name “thermostat” or Nest®. Once such device and/or circuit is identified, the software may create a rule that turns down said device while user is absent.

In another aspect, the software may utilize anonymized data on energy consumption for other users and/or energy consumers, loads, appliances, outlets, circuits, time periods, weeks, days, months, etc. stored at, for example, an online server. The software may search for similarities in consumption patterns linkable under various parameters such as:

• • geographical location;
  • weather data;
  • multiple house characteristics such as size, age, etc.;
  • multiple household characteristics such as number of people, age, gender, etc.;
  • load, appliance, outlet, etc. characteristics and features;
  • time of the day consumption patterns;
  • patterns repeating across certain days including comparison of business days vs. weekends; and/or
  • seasonality factors including summer/winter patterns and others.

Once the software identifies that it is common among other users or consumers to include a circuit with a name “Bedroom” into their vacation package rules, then the software may create a rule that directs a circuit with the same name to be turned off in a user's house when vacation package is activated.

In one aspect, a user may access a respective menu user interface of the software on the online server or in the app installed on a user's device (phone, tablet, computer, etc.) to modify the rules pre-created by the software.

An example of the vacation package may look like the following set of rules:

Rule	Circuit	Device				Action
name	name	name	Action	Start action	End action	created by
Rule 1	Water	N/A	Turn off	At	If user set	Software
	heater			activation	ending time of
				of the	vacation
				vacation	package then
				package	turn the circuit
					on 3 hours
					prior to the set
					time.
					If user did not
					set ending
					time then turn
					the circuit on
					when the user
					ends the
					package time
					manually
Rule 2	Living	N/A	Cycle:	At	When the user	User
	room	1.	turn off	activation	ends the
	lights	2.	turn on at 6	of the	package active
			pm daily	vacation	status
		3.	turn off at	package
			10 pm daily
		4.	repeat cycle
			from item 2
Rule 3	N/A	Smart	Reduce room	At	If user set	Software
		thermostat	temperature to	activation	ending time of	(based on
		(via Smart	65 F.	of the	vacation	average
		Home		vacation	package then	temperature
		platform		package	turn on the	set by other
		connection)			circuit 3 hours	users for
					prior to the set	“away”
					time.	mode for
					If user did not	user's
					set ending	geography -
					time then turn	70 F.) and
					on the circuit	then
					when the user	adjusted by
					ends the	user to 68 F.
					package active
					status

Turing to the Figures, FIG. 1 is a flow chart diagram of the marketplace algorithm processing demand response (DR) bids from utility companies and/or other market participants involved in grid management. When a utility company observes or predicts peak load on the grid (Step 1001), it may submit an aggregated DR bid to the marketplace platform (Step 1002). Upon receipt of such a bid, marketplace software identifies potential energy consumers that are eligible for the DR bid (Step 1003). Such an identification process may involve filtering a consumer database or multiple databases to identify those consumers that match required parameters of the DR bid, such as geography, connection to a specific grid branch or circuit, and other parameters. Upon completion of consumer eligibility analysis, marketplace software makes a decision on further progress (Step 1004). In cases when eligibility analysis reveals that there are no customers eligible for the DR bid, marketplace software closes the bid (Step 1018). In cases when eligibility analysis identifies consumers eligible for the DR bid, marketplace software proceeds to search for and review loads that were enrolled or subscribed by eligible consumers for automatic participation in DR bids (Step 1005). The software compares subscription terms such as time of the day, bid price, and other parameters with parameters of the DR bid. Upon completion of a review of subscribed loads, the software makes a decision on further progress (Step 1006). In cases when there are no subscribed loads matching DR bid parameters, marketplace software proceeds to a review of availability of additional loads that are likely to participate in the DR bid (Step 1012). In cases when analysis reveals matching subscribed loads, marketplace software proceeds to the estimation of the load reduction that will be achieved by triggering all subscribed loads (Step 1007). If the aggregated load reduction achieved by triggering all subscribed loads is calculated as less than the aggregated load reduction sought by the DR bid, the software enrolls all subscribed loads into the DR bid (Step 1011). If the aggregated load reduction achieved by triggering all subscribed loads is calculated as more than the aggregated load reduction sought by the DR bid, the software calculates such combination of subscribed loads that will equal or exceed by a predetermined fluctuation rate the DR bid size (Step 1008). During this process, the software may prioritize certain subscribed loads over other subscribed loads based on a range of preset parameters such as load size, consumption patterns, and other parameters. Once a combination of subscribed loads matching the DR bid is created, the software enrolls such loads into the DR bid (Step 1009). Marketplace software then informs the utility company or other party that placed the DR bid about bid fulfillment (Step 1010) and then closes the DR bid. (Step 1018).

When the software enrolls all subscribed loads in the DR bid (Step 1011) upon determination that the aggregated load reduction achieved by triggering all subscribed loads is calculated as less than the aggregated load reduction sought by the DR bid during execution of Step 1007, the software proceeds to identification of additional loads that are likely to participate in the DR bid among eligible customers (Step 1012). During this analysis, the software may assess various parameters such as load size, consumption patterns, likelihood of response of an individual consumer and load to the DR bid, and other parameters. Procedures performed during Step 1012 may also be triggered in cases when the software does not identify any subscribed loads matching the DR bid parameters while executing Step 1006.

Upon completion of a determination of additional loads that are likely to participate in the DR bid, marketplace software calculates such combination of the identified additional loads that will equal or exceed by a predetermined fluctuation rate the DR bid size (Step 1013). Once the combination of loads is identified, the software sends out individual bids to energy consumers to propose specific terms for enrollment of the predetermined loads in the DR bid (Step 1014).

As marketplace software receives responses to individual bids from energy consumers, the software evaluates whether the parameters of the aggregated DR bid such as overall load reduction, aggregated price range, and other parameters are met (Step 1015). Once the parameters of the aggregated DR bid are satisfied, the software informs the utility or other party that placed the DR bid about bid fulfillment (Step 1010) and then closes the DR bid. (Step 1018).

In cases when the software does not receive enough responses over a period of time predetermined by the aggregated DR bid or otherwise, the software informs the utility company or other party that placed the DR bid about the incomplete DR bid (Step 1016). The software may enroll all loads that have responded to the bid by this stage even though the aggregated load reduction goal is not met. In addition, the software may generate a list of suggestions on changes to DR bid parameters that may cause a higher rate of response from energy consumers (Step 1017). These changes may include price range, timing of load reduction, and other parameters. In cases when the utility company or other party that placed the DR bid does not want to implement any changes, the software closes the DR bid (Step 1018). In cases when the utility company or other party that placed the DR bid implements changes to the DR bid, the new bid is placed into the marketplace platform (Step 1002) and the process described in this flow chart (FIG. 1) repeats.

FIG. 2 is a flow chart diagram of the marketplace algorithm processing consumption incentive bids (IB) from utility companies and/or other market participants involved in grid management. When a utility company observes or predicts excessive energy generation on the grid (Step 2001), it may submit an aggregated incentive bid to the marketplace platform (Step 2002). Upon receipt of such bid, marketplace software identifies potential energy consumers that are eligible for the consumption incentive bid (Step 2003). Such identification process may involve filtering a consumer database or multiple databases to identify those consumers that match required parameters of the IB such as geography, connection to a specific grid branch or circuit, and other parameters. Upon completion of the consumer eligibility analysis, marketplace software makes a decision on further progress (Step 2004). In cases when eligibility analysis reveals that there are no customers eligible for the consumption incentive bid, marketplace software closes the bid (Step 2018). In cases when eligibility analysis identifies consumers eligible for the IB, marketplace software proceeds to search for and review loads that were enrolled or subscribed by eligible consumers for automatic participation in consumption incentive bids (Step 2005). The software compares subscription terms such as time of the day, bid price, and other parameters with parameters of the IB. Upon completion of the review of subscribed loads, the software makes a decision on further progress (Step 2006). In cases when there are no subscribed loads matching IB parameters, marketplace software proceeds to a review of availability of additional loads that are likely to participate in the incentive bid (Step 2012). In cases when analysis reveals matching subscribed loads, marketplace software proceeds to the estimation of the consumption and load increase that will be achieved by triggering all subscribed loads (Step 2007). If the aggregated consumption and load increase achieved by triggering of all subscribed loads is calculated as less than the aggregated consumption and load increase sought by the IB, the software enrolls all subscribed loads in the consumption incentive bid (Step 2011). If the aggregated consumption and load increase achieved by triggering of all subscribed loads is calculated as more than the aggregated consumption and load increase sought by the IB, the software calculates such combination of subscribed loads that will be equal or lower by a predetermined fluctuation rate than the incentive bid size (Step 2008). During this process, the software may prioritize certain subscribed loads over other subscribed loads based on a range of preset parameters such as load size, consumption patterns, and other parameters. Once a combination of subscribed loads matching the consumption incentive bid is created, the software enrolls such loads in the IB (Step 2009). Marketplace software then informs the utility company about fulfillment of the placed consumption incentive bid (Step 2010) and then closes the incentive bid (Step 2018).

When the software enrolls all subscribed loads in the IB (Step 2011) upon determination during execution of Step 2007 that the aggregated consumption and load increase achieved by triggering all subscribed loads is calculated as less than the aggregated consumption and load increase sought by the incentive bid, the software proceeds to identification of additional loads that are likely to participate in the consumption incentive bid among eligible customers (Step 2012). During this analysis, the software may assess various parameters such as load size, consumption patterns, likelihood of response of an individual consumer and load to the incentive bid, and other parameters. Procedures performed during Step 2012 may also be triggered in cases when the software does not identify any subscribed loads matching the IB parameters while executing Step 2006.

Upon completion of determining additional loads that are likely to participate in the consumption incentive bid, marketplace software calculates such combination of the identified additional loads that will be equal or lower by a predetermined fluctuation rate than the incentive bid size (Step 2013). Once the combination of loads is identified, the software sends out individual bids to energy consumers to propose specific terms for enrollment of the predetermined loads in the incentive bid (Step 2014).

As marketplace software receives responses to individual bids from energy consumers, the software evaluates whether the parameters of the aggregated incentive bid such as overall consumption and load increase, aggregated price range, and other parameters are met (Step 2015). Once the parameters of the aggregated IB are satisfied, the software informs the utility company or other party that placed the IB about bid fulfillment (Step 2010) and then closes the incentive bid. (Step 2018).

In cases when the software does not receive enough responses over a period of time predetermined by the aggregated incentive bid or otherwise, the software informs the utility company or other party that placed the IB about the incomplete consumption incentive bid (Step 2016). The software may enroll all loads that have responded to the bid by this stage even though the aggregated consumption and load increase goal is not met. In addition, the software may generate a list of suggestions for changes to incentive bid parameters that may cause a higher rate of response from energy consumers (Step 2017). These changes may include price range, timing of consumption and load increase, and other parameters. In cases when the utility company or other party that placed the incentive bid does not want to implement any changes, the software closes the incentive bid (Step 2018). In cases when the utility company or other party that placed the IB implements changes to the bid, the new bid is placed into the marketplace platform (Step 2002) and the process described in this flow chart (FIG. 2) repeats.

One skilled in the art will recognize that the disclosed features may be used singularly, in any combination, or omitted based on the requirements and specifications of a given application or design. When an embodiment refers to “comprising” certain features, it is to be understood that the embodiments can alternatively “consist of” or “consist essentially of” any one or more of the features. Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention.

It is noted in particular that where a range of values is provided in this specification, each value between the upper and lower limits of that range is also specifically disclosed. The upper and lower limits of these smaller ranges may independently be included or excluded in the range as well. The singular forms “a,” “an,” and “the” include plural referents unless the context clearly dictates otherwise. It is intended that the specification and examples be considered as exemplary in nature and that variations that do not depart from the essence of the invention fall within the scope of the invention. Further, all of the references cited in this disclosure are each individually incorporated by reference herein in their entireties and as such are intended to provide an efficient way of supplementing the enabling disclosure of this invention as well as provide background detailing the level of ordinary skill in the art.

Claims

1. A method for managing energy consumption comprising:

providing a remote monitoring and/or control device, apparatus, system, and/or component, which allows an energy provider, energy consumer, and/or group of energy consumers to monitor and/or control energy consumed on one or more load, device, apparatus, circuit, appliance, outlet, and/or premises;

determining when an energy consumer or group of energy consumers is consuming energy or is likely to consume energy on one or more load, device, apparatus, circuit, appliance, outlet, and/or premises;

having the energy provider incentivize the energy consumer or group of energy consumers with an incentive in exchange for changing the amount of energy provided to or consumed by the one or more load, device, apparatus, circuit, appliance, outlet, and/or premises; and

allowing the energy provider, energy consumer, and/or group of energy consumers to change the amount of energy provided to or consumed by the one or more load, device, apparatus, circuit, appliance, outlet, and/or premises if the energy consumer or group of energy consumers agrees to the incentive.

2. The method of claim 1, further comprising sending the energy consumer or group of energy consumers a communication giving them an option to change the amount of energy provided to or consumed by the one or more load, device, apparatus, circuit, appliance, outlet, and/or premises, and giving the energy consumer or group of energy consumers an incentive(s) to change the amount of energy provided to or consumed by the one or more load, device, apparatus, circuit, appliance, outlet, and/or premises.

3. The method of claim 2, wherein, if the energy consumer or group of energy consumers chooses the option to change the amount of energy provided to or consumed by the one or more load, device, apparatus, circuit, appliance, outlet, and/or premises, the energy provided to or consumed by the one or more load, device, apparatus, circuit, appliance, outlet, and/or premises is changed, adjusted, and/or turned on or off.

4. The method of claim 2, wherein the energy to the one or more load, device, apparatus, circuit, appliance, outlet, and/or premises is changed at the time, or around the time, when the energy consumer or group of energy consumers chooses the option to change the amount of energy provided to or consumed by the one or more load, device, apparatus, circuit, appliance, outlet, and/or premises.

5. The method of claim 4, wherein the energy provided to or consumed by the one or more load, device, apparatus, circuit, appliance, outlet, and/or premises is changed within one hour of the energy consumer or group of energy consumers choosing the option to change the amount of energy provided to or consumed by the one or more load, device, apparatus, circuit, appliance, outlet, and/or premises.

6. The method of claim 1, wherein the energy consumer or group of energy consumers is given a choice to change the amount of energy provided to or consumed by the one or more load, device, apparatus, circuit, appliance, outlet, and/or premises or not change the amount of energy provided to or consumed by the one or more load, device, apparatus, circuit, appliance, outlet, and/or premises, and the energy consumer or group of energy consumers is given financial incentive(s) to change the amount of energy provided to or consumed by the one or more load, device, apparatus, circuit, appliance, outlet, and/or premises.

7. The method of claim 1, wherein determining when an energy consumer or group of energy consumers is consuming energy or is likely to consume energy on the one or more load, device, apparatus, circuit, appliance, outlet, and/or premises is based on energy consumption and/or energy consumption patterns by the energy consumer or group of energy consumers according to information and/or data provided by the remote monitoring and/or control device, apparatus, system, and/or component.

8. The method of claim 1, wherein a change in an amount of energy provided to or consumed by the one or more load, device, apparatus, circuit, appliance, outlet, and/or premises during one or more time period is preapproved, scheduled, and/or initiated by the energy consumer or group of energy consumers.

9. A method for managing energy consumption comprising:

determining an amount of energy for an energy provider to save during a time period(s), wherein the amount of energy to save is determined by calculated energy consumption patterns of an energy consumer or group of energy consumers;

determining an energy consumer or group of energy consumers that are available to change the amount of energy provided to or consumed by one or more load, device, apparatus, circuit, appliance, outlet, and/or premises during the time period(s);

giving the available energy consumer or group of energy consumers the option of or an incentive for changing the amount of energy provided to or consumed by the one or more load, device, apparatus, circuit, appliance, outlet, and/or premises during the time period(s); and

changing the amount of energy provided to or consumed by the one or more load, device, apparatus, circuit, appliance, outlet, and/or premises of the available energy consumer or group of energy consumers who agree to the option and/or the incentive at the time or thereafter when the available energy consumer or group of energy consumers agrees to change the amount of energy provided to or consumed by the one or more load, device, apparatus, circuit, appliance, outlet, and/or premises during the time period(s).

10. A method for managing an amount and/or timing of group energy consumption comprising:

providing one or more device, capable of monitoring and remote control, to an energy consumer or a group of energy consumers which allows for changing the amount of energy provided to or consumed by one or more circuit, device, load, appliance, and/or outlet on a premises of the energy consumer or group of energy consumers;

determining one or more time period when to conserve and/or expend energy consumption based on price and/or availability of energy during the one or more time period;

contacting the energy consumer or group of energy consumers, before or during the one or more time period, and giving the energy consumer or group of energy consumers the option to change the amount of energy provided to or consumed by the one or more circuit, device, load, appliance, and/or outlet on a premises during the one or more time period; and

upon the energy consumer or group of energy consumers choosing to change the amount of energy provided to or consumed by the one or more circuit, device, load, appliance, and/or outlet on a premises during the one or more time period, remotely changing the amount of energy provided to or consumed by the one or more circuit, device, load, appliance, and/or outlet on a premises during the one or more time period.

11. The method of claim 10, wherein determining the one or more time period when to conserve and/or expend energy consumption based on the price and/or availability of energy during the one or more time period is further based on energy consumption patterns by the energy consumer or group of energy consumers during the time period or multiple time periods in the past.

12. The method of claim 10, further comprising sending a notification to the energy consumer or group of energy consumers that the one or more device, capable of monitoring and remote control, will change the amount of energy provided to or consumed by the one or more circuit, device, load, appliance, and/or outlet on a premises to conserve energy consumption during the one or more time period, and/or sending a notification to the energy consumer or group of energy consumers that the one or more device, capable of monitoring and remote control, will change the amount of energy provided to or consumed by to the one or more circuit, device, load, appliance, and/or outlet on a premises to expend energy consumption during the one or more time period.

13. The method of claim 10, further comprising providing to the energy consumer or group of energy consumers an option to choose whether to change the amount of energy provided to or consumed by the one or more circuit, device, load, appliance, and/or outlet on the premises to conserve energy consumption during the one or more time period, and/or providing to the energy consumer or group of energy consumers an option to change the amount of energy provided to or consumed by the one or more circuit, device, load, appliance, and/or outlet on the premises to expend energy consumption during the one or more time period.

14. The method of claim 10, wherein an energy utility company or energy grid manager decides whether to change the amount of energy provided to or consumed by the one or more circuit, device, load, appliance, and/or outlet on a premises to conserve energy consumption during the one or more time period, or an energy utility company or energy grid manager decides whether to change the amount of energy provided to or consumed by the one or more circuit, device, load, appliance, and/or outlet on a premises to expend energy consumption during the one or more time period.

15. The method of claim 10, further comprising establishing and providing an incentive(s) for the energy consumer or group of energy consumers to allow the one or more device, capable of monitoring and remote control, to change the amount of energy provided to or consumed by the one or more circuit, device, load, appliance, and/or outlet on the premises to conserve or expend energy consumption during the one or more time period.

16. The method of claim 10, wherein determining one or more time period when to conserve and/or expend energy consumption based on the price and/or availability of energy during that one or more time period is based on past, current, and/or forecasted energy prices.

17. The method of claim 10, wherein determining one or more time period when to conserve and/or expend energy consumption based on the price and/or availability of energy during that one or more time period is based on past, current, and/or forecasted energy availability.

18. The method of claim 10, wherein determining one or more time period when to conserve and/or expend energy consumption based on the price and/or availability of energy during that one or more time period is based on past, current, and/or forecasted energy supply.

19. The method of claim 10, wherein determining one or more time period when to conserve and/or expend energy consumption based on the price and/or availability of energy during that one or more time period is past, current, and/or forecasted energy demand.

20. The method of claim 10, wherein the energy is renewable energy chosen from one or more of solar energy, wind energy, hydroelectric energy, bio energy, geothermal energy, hydrogen energy, and/or ocean/water energy.

21. The method of claim 10, wherein the one or more device, capable of monitoring and remote control, is remotely controlled using a computer, laptop computer, tablet computer, phone, cell phone, server, cloud-based computing software, algorithm, and/or software application.

22. The method of claim 10, wherein the one or more device, capable of monitoring and remote control, is remotely controlled by a user of energy on a premises having the one or more device, an owner of a premises having the one or more device, and/or a renter on a premises having the one or more device.

23. The method of claim 1, further comprising identifying one or more premises, circuit on a premises, device on a premises, load on a premises, appliance on a premises, and/or outlet on a premises, which may be locally or remotely changed, adjusted, and/or turned on or off.

24. The method of claim 1, further comprising calculating how many one or more circuit, device, load, appliance, and/or outlet on a premises, or group(s) of one or more circuit, device, load, appliance, and/or outlet on a premises, must be changed, adjusted, and/or turned on or off to conserve or expend a desired amount and/or cost of energy consumption.

25. The method of claim 1, further comprising calculating how many one or more circuit, device, load, appliance, and/or outlet on a premises, or group(s) of one or more circuit, device, load, appliance, and/or outlet on a premises, must be changed, adjusted, and/or turned on or off to offset an amount and/or cost of energy consumption.

26. A method of managing energy consumption comprising:

identifying an amount of load reduction needed to reduce a peak load to a desired level;

identifying consumers with one or more loads contributing to the peak load;

identifying loads of consumers flagged for participation in a load reduction process;

shutting off, decreasing, and/or otherwise managing power supply to the loads flagged for participation for a period of time;

determining the remaining amount of load reduction needed from the difference between the amount of load reduction needed to reduce the peak load to the desired level and the amount of the loads flagged for participation in the load reduction process;

if additional load reduction is needed, identifying one or more additional loads of the consumers capable of enrolling in the load reduction process;

selecting one or more of the additional loads for participation in the load reduction process by aggregating the one or more additional loads in a manner to equal or exceed the difference between the amount of load reduction needed to reduce the peak load to the desired level and the amount of the loads flagged for participation in the load reduction process;

notifying consumers with the one or more additional loads selected for participation in the load reduction process; and

shutting off, decreasing, and/or otherwise managing power supply to the one or more additional loads for a period of time to meet or exceed the amount of load reduction needed to reduce the peak load to the desired level, upon acceptance by the consumer to participate in the load reduction process.

27. The method of claim 26, wherein the identifying of the one or more additional loads of the consumers capable of enrolling in the load reduction process takes into account one or more of:

load size;

user consumption patterns;

probabilities of loads to participate in load reduction process based on load name, location, and/or size;

past history of participation by the consumer in prior load reduction processes; and/or

consumption patterns and/or participation in prior load reduction processes by others.

28. The method of claim 26, wherein the notifying of the consumers with the one or more additional loads selected for participation in the load reduction process involves one or more of:

instructions for the consumers to commit to a specific consumption behavior;

a proposal for a benefit that the consumer may receive for participating; and/or

actionable tools to execute the proposal.

29. The method of claim 26, wherein once the period of time has elapsed for shutting off power supply to the loads flagged for participation and to the one or more additional loads, the power supply is returned to a former unchanged level.

30. The method of claim 1, wherein changing the amount of energy provided to or consumed by the one or more load, device, apparatus, circuit, appliance, outlet, and/or premises is performed by turning on, turning off, or adjusting or changing settings or levels on the one or more load, device, apparatus, circuit, appliance, outlet, and/or premises.