Patent Publication Number: US-9852484-B1

Title: Providing demand response participation

Description:
CROSS-REFERENCE TO RELATED APPLICATION 
     This application claims priority to and the benefit of U.S. Provisional Patent Application No. 61/937,249, filed on Feb. 7, 2014, the disclosure of which is incorporated by reference herein in its entirety. 
    
    
     BACKGROUND 
     Field 
     The present disclosure relates generally to energy conservation and more specifically to increasing utility customer participation in demand response (DR) events. 
     Description of the Related Art 
     During certain peak use events, energy systems may not be able to meet energy demand or energy prices may spike. For example, during a heat wave or when a power plant needs to be taken offline for maintenance, blackouts, brownouts, or energy price spikes may occur due to shortages in energy. Accordingly, during a peak use event, a utility company may initiate a DR event. A DR event refers to actions that are taken to reduce energy demand during these peak use events. 
     For example, a DR event may involve remotely controlling utility customers&#39; thermostats to reduce energy consumption of heating/cooling systems during a peak use event, either by cycling heating/cooling systems off for a period of time or by adjusting a thermostat set point. However, because utility customers are generally worried about being uncomfortable during DR events and because DR events are generally optional, utility customers often opt out of DR events. 
     In the related art, utility companies may offer financial incentives to utility customers who participate in DR events during peak use events. However, these incentives may be expensive for the utility companies to provide and utility customers may still opt out of these DR events. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       A general architecture that implements the various features of the disclosure will now be described with reference to the drawings. The drawings and the associated descriptions are provided to illustrate embodiments of the disclosure and not to limit the scope of the disclosure. Throughout the drawings, reference numbers are reused to indicate correspondence between referenced elements. 
         FIG. 1  is a flow diagram illustrating a process for providing DR event feedback information to at least one utility customer, according to an embodiment. 
         FIG. 2  is a flow diagram illustrating a process for determining a percentage of utility customers participating in a DR event, according to an embodiment. 
         FIG. 3  is a flow diagram illustrating a process for determining a percentage of utility customers participating in a DR event and providing the determined percentage to at least one utility customer, according to an embodiment. 
         FIG. 4  is a block diagram illustrating a DR event participation system, according to an embodiment. 
         FIG. 5  is a block diagram illustrating a client device, according to an embodiment. 
         FIGS. 6A, 6B, 6C, 6D, 7A, 7B, 7C, 8A, 8B, 9A, 9B, 9C, 9D, 9E, 10A, and 10B  illustrate a user interface (UI) of a client device, according to an embodiment. 
     
    
    
     DETAILED DESCRIPTION 
     Embodiments may address at least some of the above problems and/or disadvantages and other disadvantages not described above. Also, embodiments are not required to overcome the disadvantages described above, and an embodiment may not overcome any of the problems described above. 
     An embodiment employs behavioral science techniques to encourage utility customers to participate in DR events (e.g., to not opt out of DR events). In particular, utility customers are segmented into groups according to different metrics to encourage group participation. For example, utility customers may be segmented by a zip code or neighborhood associated with each utility customer (e.g., where each utility customer resides), demographic information, socioeconomic data, particular utility programs that utility customers are enrolled in, utility substations that utility customers use, or other targeting algorithms. Thereafter, DR event feedback information is generated based on utility customer participation in DR programs and may be provided to the utility customers in the group. 
     For instance, when a utility customer is asked to enroll in a DR event or attempts to opt out of a DR event, DR event feedback information such as “98 percent of your neighbors are participating” may be provided to the utility customer. Because utility customers are provided with information corresponding to how they compare with their peers (e.g., utility customers in the same neighborhood, or utility customers in the same utility program), they may be encouraged to conform to, or exceed, normative behavior. For example, if a utility customer sees that 98% of his or her neighbors are participating in a DR event, the utility customer may be much less likely to opt out of the DR event. 
     The term “peak use event” as used herein may refer to an event that occurs or a situation in which an energy system (e.g., an energy grid) may become compromised or when energy price spikes occur due to energy shortages or predicted shortages in the energy system. For example, as set forth above, a peak use event may occur during a heat wave when utility customers are using (or are expected to be using) their air conditioning systems to stay cool, and as a result, energy use in the energy system may exceed (or be expected to exceed) a certain threshold level. 
     Accordingly, in order to avoid blackouts, brownouts, and/or energy price spikes, which are implemented to discourage energy use during certain times or occur as a consequence of high levels of energy use, utility companies have begun utilizing DR programs. The term “DR program” as used herein may refer to a program in which utility customers agree to lower their power consumption by participating in DR events during peak use event. The term “DR event” as used herein may refer to an implementation of a DR program during which participating utility customers&#39; thermostats are remotely controlled by a utility company so as to reduce energy consumption of heating/cooling systems during a peak use event. For example, during a heat wave, energy consumption can be reduced by cycling off an air conditioning unit for periods of time or adjusting a thermostat set point. In other implementations of DR programs, utility customers may control their thermostats or other energy consuming devices themselves in order to reduce energy consumption during a peak event. The DR event may also include an enrollment or opt out period before or during a peak use event for which the DR event is initiated. 
     According to an embodiment, the DR feedback event information may be provided to utility customers in real-time, prior to, during, or after a DR event. For example, the DR feedback event information may be transmitted to a client device, such as a utility customer&#39;s smartphone, mobile device, computer, or thermostat mounted in a utility customer&#39;s home, and displayed on the client device. Alternatively, the DR feedback event information may be transmitted to and displayed on a website accessible to a utility customer (e.g., the utility customer&#39;s utility account). 
     Because information about participation in DR events may be provided to utility customers in real-time, utility customers are made aware of what other utility customers are doing during the DR event, and, as a whole, will learn what perceived normal behavior is and will be more likely to conform with that learned behavior. According to an embodiment, using behavioral comparisons is effective for driving outliers (i.e., utility customers who opt out of DR events) to normative behavior (i.e., not opting out of DR events) because, in general, individuals do not want to be perceived as doing something incorrectly or outside of what is considered to be normal. Instead, individuals, especially within a group of their peers, want to conform to or exceed the behavior practiced by their peers. For example, if a large number of utility customers participate in DR events, outliers may be encouraged to participate in the DR events and/or not opt out. Further, if there is a particularly hot day in which DR event is necessary to avoid blackouts or brownouts, utility customers, who may have otherwise opted out, may not opt out in order to avoid deviating from what is perceived as being normal behavior. 
       FIG. 1  is a flow diagram illustrating a process for providing DR event feedback information to at least one utility customer. DR event feedback information may correspond to at least one of a percentage, a ratio, or a number of utility customers participating in a DR event. According to one embodiment, when a utility customer is participating in a DR event, the thermostat of the utility customer can be controlled by the utility company to reduce energy consumption. For example, on a hot day when a utility customer is using his or her air conditioning system, the utility provider may reduce usage of the air conditioning system (e.g., by setting a thermostat set point that uses less electricity) or cycle off for periods of time the air conditioning system of a utility customer who is participating in a DR event, during the DR event. In order to encourage the utility customer to enroll in or to not opt out of a DR event, the DR event feedback information may be displayed in a user interface (UI) such as a UI in which the thermostat set point is adjusted. 
     Referring to  FIG. 1 , information regarding participation in a DR event by a plurality of utility customers is received in block  100 . The information may be received directly from a client device such as a thermostat, mobile device, or other device, from the utility company (e.g., from a server or database maintained by the utility), from a thermostat manufacturer, from a third-party database, or any other source, and will be described in greater detail below with reference to  FIG. 4 . According to an embodiment, the information may include whether a utility customer is enrolled or registered in a DR program, whether the utility customer is currently participating in a future or current DR event, or whether the utility customer is requesting to opt out of the DR program or DR event. This will be described in greater detail below with reference to  FIG. 4 . 
     Next, in block  110 , DR event feedback information is determined using the received participation information. In an embodiment, utility customers may be segmented into one or more groups and metrics may be generated based on participating information for utility customers in the one or more groups. The utility customers may be segmented in such a way as to maximize participation in DR events. For example, a utility customer may be more likely to respond to feedback indicating high participation among utility customers that are similar to them (e.g., neighbors). Additionally, a utility customer may be more likely to respond to feedback indicating high participation among utility customers that they aspire to be like (e.g., energy efficient neighbors). 
     Therefore, according to an embodiment, utility customers may be segmented into one or more groups of similar utility customers. Similar utility customers may be identified based on various factors/characteristics and signals including, for example, location (e.g., residential addresses, work addresses, etc.), socioeconomic data, demographic data, building data, weather data, etc. Location information may include a zip code, a city, a neighborhood, global positioning system (GPS) coordinates, an area around a location (e.g., a four block radius around a utility customer&#39;s home), weather patterns, characteristics, or other weather data near a location, or any other location information. Other information used to identify similar users may include household income, property values, a number of occupants of a residence, a number of children in a family, a number of bedrooms and/or bathrooms in a building, a size (e.g., square footage) of a building, a number of floors in a building, a building type, or any other information that may be obtained about a utility customer or calculated for a utility customer. In some embodiments, the information may be retrieved from the customer and stored on a server of the system or obtained from a 3 rd  party system. However, the embodiments are not limited thereto. 
     For instance, a group that includes all of the utility customers in a certain neighborhood may be selected, as a utility customer may be more likely to enroll or continue participating in DR events when provided with feedback on the participation of neighbors because the utility customer may be motivated to conform his or her behavior with that of his or her neighbors. Alternatively or additionally, a subset of the group of neighbors that includes utility customers in the neighborhood that are energy efficient may be selected. A utility customer may be more likely to enroll or continue participating in DR events when provided with feedback on the participation of high performing neighbors because the utility customer may be motivated to join or beat his or her high performing neighbors. An energy efficient neighbor may be a utility customer that uses an amount of energy below a certain threshold level or a utility customer that is associated with an energy efficiency score that exceeds (or does not exceed) a certain threshold value. The number or percentage of participating utility customers among the utility customers in the selected group may be calculated and continuously updated during a DR event. 
     According to an embodiment, individualized DR event information may be provided to each participating utility customer. For example, a utility customer associated with at least one of the above-discussed characteristics (e.g., location information) may be identified. Thereafter, a group may be selected based on the at least one characteristic and individualized DR event feedback information may be generated and provided to the identified utility customer. Therefore, participation in DR events can be further improved. 
     Next, in block  120 , the determined DR event feedback information is provided to at least one utility customer among the plurality of utility customers. As set forth above, the DR event feedback information may be transmitted to and displayed on a client device of the utility customer. This will be discussed in greater detail below with reference to  FIGS. 5, 6A, 6B, 6C, 6D, 7A, 7B, 7C, 8A, 8B, 9A, 9B, 9C, 9D, 9E, 10A, and 10B . 
       FIG. 2  is a flow diagram illustrating a process for determining a percentage of utility customers participating in a DR event, according to an embodiment. The determined percentage of utility customers participating in the DR event may be used in determining the utility DR event feedback information as described above with reference to block  110  of  FIG. 1 . 
     Referring to  FIG. 2 , a total number of utility customers in a group is determined in block  200 . For instance, as set forth above, a number of utility customers may be grouped together according to a certain algorithm or method. The group may include only those utility customers who have opted in or been selected to participate in a DR program. Alternatively, the group may include all utility customers targeted for DR events. In some embodiments, the group may include utility customers selected based on various factors or characteristics (e.g., similar customers, neighbors, energy efficient neighbors, etc.). Accordingly, the total number of utility customers in a group may be determined. 
     Next, in block  210 , it is determined if a utility customer has opted out of the DR event. A utility customer may be able to opt out of the DR event prior to the DR event and/or during the DR event. 
     Next, in block  220 , the percentage of utility customers remaining in the DR event is determined based on the total number of utility customers in the group and the number of utility customers that have opted out or that are still participating. In an embodiment, a utility customer participating in a DR program may be able to opt out of the DR event before it begins. Accordingly, the percentage of utility customers remaining in the DR event may be calculated before the DR event begins and updated until the DR event ends. Utility customers may be provided with participation information leading up to the DR event and throughout the DR event. 
     Next, in block  230 , if the DR event has not ended, the process returns to block  210  to determine if any other utility customers have opted out of the DR event. Otherwise, if the DR event has ended, the process is terminated. Although the embodiment discussed with respect to  FIG. 2  determines the percentage of utility customers in a DR event based on whether utility customers have opted out of the DR event, in other embodiments, the percentage of utility customers in a DR event may be determined based on whether utility customers have enrolled in a DR event or indicated that they will participate in a DR event. 
       FIG. 3  is a flow diagram illustrating a process for determining a percentage of utility customers participating in a DR event and providing the determined percentage to at least one utility customer, according to an embodiment. 
     Referring to  FIG. 3 , a total number of utility customers in a group is determined in block  300 . This has been described in detail above with reference to  FIG. 2  and will not be described again in detail. 
     Next, in block  310 , if the DR event has not started, the process returns to block  300 . Otherwise, if the DR event has started, the process proceeds to block  320  and the percentage of utility customers participating in the DR event, among the total number of utility customers in the group, is determined. The embodiment is not limited thereto and the system may be configured to add utility customers during a DR event. In this case, the total number of utility customers may be updated during the DR event. 
     Next, in block  330 , the determined percentage or number of participating utility customers and/or other feedback information is provided to at least one utility customer. The percentage or number of participating utility customers and/or other feedback information may be provided to participating utility customers to encourage the utility customers currently participating in the DR event to remain in the DR event and not opt out. According to another embodiment, the percentage or number and/or other feedback information may also be provided to utility customers who have opted out of the DR event and/or utility customers not participating in the DR program to encourage the non-participating utility customers to participate in future DR events. 
     Next, in block  340 , if no utility customers are requesting to opt out of the DR event, the process determines if the DR event has ended, in block  380 . Otherwise, if a utility customer is requesting to opt out of the DR event, the process may provide, to the utility customer requesting to opt out of the DR event, the percentage of participating utility customers, along with a prompt requiring that the utility customer confirm the request to opt out of the DR event, in block  350 . This will be described in greater detail below with reference to  FIG. 8A . 
     Next, in block  360 , if the utility customer confirmed the request to opt out of the DR event, the percentage of utility customers participating in the DR event is updated, in block  370 . Otherwise, if the utility customer did not confirm his or her request to opt out of the DR event (i.e., the utility customer decided to remain in the DR event) the process returns to block  340  and a determination is made as to whether or not any other utility customers are requesting to opt out of the DR event. 
     After the percentage of utility customers participating in the DR event is updated, in block  370 , it is determined if the DR event has ended, in block  380 . If the DR event has ended, the process is terminated. Otherwise, if the DR event has not ended, the process returns to block  340 . 
     According to another embodiment, DR event feedback information may be additionally provided to utility customers in the form of e-mails, text messages, or other forms. According to yet another embodiment, a utility customer&#39;s participation in DR event programs, along with the participation of the other utility customers in the group of the utility customer, may be provided on the utility customer&#39;s utility bill. 
       FIG. 4  is a block diagram that illustrates an embodiment of a network  400  including servers  430 ,  440  upon which the DR event participation system may be implemented and client devices  450 - 1 ,  450 - 2 ,  450 - 3  that communicate with the servers  430 ,  440 . The client devices  450 - 1 ,  450 - 2 ,  450 - 3  will be described in greater detail below with reference to  FIG. 5 . Server  1   440  includes a transmitter  441 , a receiver  443 , a feedback generator  445 , a controller  447 , and a memory  449 . The feedback generator  445  and the controller  447  may include at least one of a processor, a hardware module, or a circuit for performing their respective functions. Although not illustrated, server  2   430  may be similarly embodied. The client devices  450 - 1 ,  450 - 2 ,  450 - 3  communicate across the Internet or another wide area network (WAN) or local area network (LAN)  410  with server  1   440  and server  2   430 . Server  1   440  and server  2   430  may also communicate with database  420  across the Internet or another wide area network (WAN) or local area network (LAN)  410 . 
     The feedback generator  445 , controller  447 , and memory  449  operate to execute instructions, as known to one of skill in the art. The term “computer-readable storage medium” as used herein refers to any tangible medium, such as a disk or semiconductor memory, that participates in providing instructions to the feedback generator  445  or controller  447  for execution. 
     According to an embodiment, one or both of server  1   440  and server  2   430  may implement the DR event participation system. For example, server  1   440  and/or server  2   430  may be located at a utility company, a third-party site, or any other location and may be configured to receive information from the client devices  450 - 1 ,  450 - 2 ,  450 - 3 , database  420 , or another source (e.g., the utility company, a thermostat manufacturer, a third-party database, or any other source) regarding participation information in DR events or programs. Server  1   440  and/or server  2   430  may segment the utility customers into groups, determine DR event feedback information based on the received information, and communicate the determined DR event feedback information to the client devices  450 - 1 ,  450 - 2 ,  450 - 3  and/or to the database  420 , the utility company, the thermostat manufacturer, a third-party database, or any other source. However, this is merely exemplary and the system may be implemented on a single server or on more than two servers. Further, the database  420  may be optionally omitted. 
       FIG. 5  is a block diagram that illustrates an embodiment of a client device  500  upon which an embodiment may be implemented. The client device  500  includes a transmitter  501 , a receiver  503 , a display  505 , a controller  507 , and a memory  509 . The transmitter  501  may be configured to transmit participation information to server  1   440 , server  2   430 , and/or database  420 . The receiver  503  may be configured to receive, from server  1   440 , server  2   430 , and/or database  420 , information including the DR event feedback information and additional information. The additional information will be described in greater detail with reference to  FIGS. 6A, 6B, 6C, 6D, 7A, 7B, 7C, 8A, 8B, 9A, 9B, 9C, 9D, 9E, 10A, and 10B . 
     The controller  507  and the memory  509  operate to execute instructions, as known to one of skill in the art. The controller  507  may include at least one of a processor, a hardware module, or a circuit for performing its respective functions. The display  505  may be configured to display the received information. Further, the display  505  may be a touchscreen display and may act as an input device for interacting with a utility customer or other user. The client device  500  may connect to the network  410  using wireless protocols, such as 802.11 standards, Bluetooth®, or cellular protocols, or via physical transmission media, such as cables or fiber optics. 
     The client device  500  may be embodied in many different forms such as a smartphone, a mobile device, a thermostat, a computer, a device having a graphical UI (GUI) from which a thermostat set point can be selected or adjusted, etc. The GUI may be accessed through an application installed on a utility customer&#39;s smartphone or through a browser displaying the utility customer&#39;s utility account. Therefore, a utility customer may be able to remotely control his or her thermostat and participate in DR events. 
       FIGS. 6A, 6B, 6C, 6D, 7A, 7B, 7C, 8A, 8B, 9A, 9B, 9C, 9D, 9E, 10A, and 10B  illustrate a UI of a client device, according to an embodiment. For convenience, an embodiment illustrating a UI of a smartphone, on which an application implementing an embodiment is installed, is illustrated. However, the embodiment is not limited thereto, and any device having a display, e.g., a computer (not illustrated), a thermostat (not illustrated), etc., may constitute the client device  500 . In the following figures, redundant explanation of the same elements as those of previous figures is omitted. 
     Referring to  FIG. 6A , a screen  600 - 1  illustrating a GUI in which a thermostat set point can be selected is displayed. Screen  600 - 1  may be displayed when a utility customer opens an application installed on a smartphone. As shown in screen  600 - 1 , a current temperature set point (i.e., “72”)  616  of, e.g., the utility customer&#39;s home, may be displayed. The utility customer can adjust the current temperature set point using buttons  612 ,  614  to control the heating or cooling systems in the utility customer&#39;s home. A current schedule  618  of the utility customer may be displayed. For example, in order to save energy, the thermostat may be programmed to keep the house at an optimal temperature only when the utility customer is scheduled to be home (e.g., before 10:00 p.m.). One or more icons  620  may also be displayed to indicate the current schedule period and other schedule periods (e.g., “home,” “away,” “sleep,” etc.). 
     Because there are a number of different screens that may be displayed on the smartphone, a page identifier (i.e., “Thermostat”)  606  may be displayed to indicate to the utility customer that the currently displayed page corresponds to the utility customer&#39;s thermostat. Icon  608  may be displayed to identify a current program or mode. For example, a flame icon may be displayed to indicate a heating program, and a snowflake icon (not illustrated) may be displayed to indicate a cooling program. Finally, a thermostat message  602  which may provide relevant information about scheduled, active, and/or completed DR events may be displayed. 
     If the utility customer selects the menu button  604 , a screen  600 - 2  may be displayed, as shown in  FIG. 6B . Also, as shown in  FIG. 6B , a portion of the screen  600 - 1  may also be displayed. The utility customer may navigate back to the screen  600 - 1  by swiping the screen toward the left side of the smartphone or by tapping on the screen  600 - 1 . The screen  600 - 2  may display a navigation menu including menu items “Thermostat”  622 , “Program”  624 , “Comparison”  626 , and “Peak Use Events”  628 . “Peak Use Events”  628  may be displayed for utility programs that have a DR component. The utility customer may select “Thermostat”  622  to return to screen  600 - 1 . The utility customer may select “Program”  624  to navigate to a screen displaying currently programmed heating/cooling schedule along with an interface for modifying the currently programmed schedule (not illustrated). The utility customer may select “Comparison”  626  to navigate to a screen displaying, for example, the utility customer&#39;s energy usage and participation in DR events as compared to the other utility customers in the group to which the utility customer belongs (not illustrated). The utility customer may select “Peak Use Events”  628  to learn about the DR events and to get real-time information about scheduled, active, and completed DR events. Further, “App Settings”  630  may be displayed. The utility customer may select “App Settings”  630  to navigate to a screen where the utility customer can make changes to the settings of the installed application. 
     If the utility customer selects “Peak Use Events”  628 , screen  600 - 3  is displayed, as shown in  FIG. 6C . In screen  600 - 3 , the page identifier  606  may be updated to display “Peak Use Events.” Further, screen  600 - 3  may display a message band  634 , an additional information box  636 , a link or button to select for additional information about peak use events  638 , a thank you message  640 , and an opt out link or button  642 . 
     The message band  634  may display information about scheduled, active, and completed DR events. For example, the message band may display participation information (e.g., DR event feedback information) and information to encourage participation during DR events. The additional information box  636  may provide utility customers with a set of tips designed to help them stay conformable during a DR event along with other information to motivate them to remain in the DR event (i.e., not opt out). The additional information box will be described in greater detail below with reference to  FIGS. 9A, 9B, 9C, 9D, and 9E . The link or button for additional information about peak use events  638  is a selectable link or button for navigating to a screen displaying information about peak use events and what to expect during a DR event. This will be described in greater detail with reference to  FIG. 6D  below. The opt out link or button  642  may be provided to enable the utility customer to opt out of a DR event, if for instance, they require cooling during the DR event. The opt out link  642  may display a reminder that if a utility customer opts out of a DR event, they cannot later opt back in to the DR event. 
     If the utility customer selects “Learn about peak use events”  638 , screen  600 - 4  is displayed, as shown in  FIG. 6D . Screen  600 - 4  may provide utility customers with useful information and answers to frequently asked questions about what a peak use event is (i.e., “What is a peak use event?”)  646 , how their heating, ventilation, and air conditioning (HVAC) equipment operation will be modified (i.e., “How does it work?”)  648 , and what to expect during a DR event (i.e., “What should I expect?”)  650 . 
       FIGS. 7A, 7B, and 7C  illustrate different “Peak Use Event” screens which may be displayed during a DR event corresponding to a peak use event. 
     Referring to  FIG. 7A , during a DR event corresponding to a peak use event, the message band  634  may display DR event feedback information. For example, if the group of utility customers is determined to be all of the utility customers within a neighborhood, the percentage of utility customers participating in the DR event may be calculated and displayed. As shown in  FIG. 7A , if 98% of the utility customers in the neighborhood are currently participating in the DR event, the message band  634  may display “98% of your neighbors are currently participating.” Furthermore, the time completed/remaining in the DR event may be displayed in the message band  702 . 
     Referring to  FIG. 7B , when the DR event is two-thirds completed, screen  700 - 2  may be displayed. In screen  700 - 2 , the time completed/remaining in the DR event may be updated so that “⅔ into the event,” may be displayed in the message band  702 . Further, the message band  634  may be updated to display words of encouragement to encourage the utility customer to complete the DR event. For example, the message band  634  may be updated to display “Doing great! You&#39;re more than half way done!” 
     Referring to  FIG. 7C , when the DR event is approaching its conclusion (e.g., has 20 minutes remaining), screen  700 - 3  may be displayed. In screen  700 - 3 , the time completed/remaining in the current DR may be updated so that a message such as “Last 20 minutes of event” is displayed in the message band  702 . Further, the message band  634  may be updated to display different words of encouragement to encourage the utility customer to complete the DR event. For example, the message band  634  may be updated to display “Don&#39;t change a thing, you&#39;re so close to completing this event!” 
     Referring to  FIG. 8A , when a utility customer is participating a DR event and requests to opt out (e.g., step  340  in  FIG. 3 ), DR event feedback information such as “95% of your neighbors are still participating”  804 , may be provided to the utility customer, along with a prompt, “Are you sure you want to leave this event? This cannot be undone”  806  (e.g., step  350  of  FIG. 3 ). As set forth above, the utility customer may request to opt out of the DR event by selecting the link or button  642 , as shown in  FIG. 6C . If the utility customer initiates a request to opt out of the DR event, the utility customer is prompted to confirm or cancel the request to opt out using the selectable buttons  808 ,  810  (e.g., step  360  of  FIG. 3 ). If the utility customer confirms the request to opt out, the percentage of utility customers participating in the DR event is updated (e.g., step  370  in  FIG. 3 ) and screen  800 - 2  is displayed, as shown in  FIG. 8B . 
     Referring to  FIG. 8B , in screen  800 - 2 , the message band  634  may be updated to display “You left the event—98% of your neighbors are still participating.” 
       FIGS. 9A, 9B, 9C, 9D, and 9E  illustrate different additional information that may be displayed in additional information box  636 , which is displayed on various screens. For instance,  FIG. 9A  illustrates a tip instructing the utility customer to “Turn your fan on” so that the utility customer may be more comfortable during a DR event and therefore less likely to leave the DR event.  FIG. 9B  illustrates a tip with a recipe for strawberry lemonade.  FIG. 9C  illustrates a tip to “Pre-cool your home.”  FIG. 9D  illustrates a tip to “Close your interior shades.” Finally,  FIG. 9E  illustrates information on “What causes a blackout?” This additional information is exemplary and is not limited thereto. Accordingly, any tips or information to improve a utility customer&#39;s comfort during a DR event and therefore increase the likelihood of the utility customer completing the DR event may be displayed. 
     Referring to  FIG. 10A , screen  1000 - 1  may be shown when the DR event ends. In  FIG. 10A , the message band  634  may be updated to “Event complete!” Screen  1000 - 2  may display a message encouraging the utility customer. For example, the message band  634  may be updated to display “You helped prevent energy shortages today!” 
     The foregoing detailed description has set forth various embodiments via the use of block diagrams, schematics, and examples. Insofar as such block diagrams, schematics, and examples contain one or more functions and/or operations, each function and/or operation within such block diagrams, flowcharts, or examples can be implemented, individually and/or collectively, by a wide range of hardware, software, or virtually any combination thereof, including software running on a general purpose computer or in the form of a specialized hardware. 
     While certain embodiments have been described, these embodiments have been presented by way of example only, and are not intended to limit the scope of the protection. Indeed, the novel methods and apparatuses described herein may be embodied in a variety of other forms. Furthermore, various omissions, substitutions and changes in the form of the methods and systems described herein may be made without departing from the spirit of the protection. The accompanying claims and their equivalents are intended to cover such forms or modifications as would fall within the scope and spirit of the protection.