Installation system for demand response resources

Abstract

An installation system for demand response resources. The system may invoke a use of an installer portal to increase an efficiency of installing resources for demand response systems. Installation of such resources may incorporate registering a client with a particular customer, configuring the client with parameters, installing the client, confirming that the client is communicating properly with a demand response management system, connecting the client to various components at a resource facility, and confirming that the client sends usage or other data correctly to the demand response management system.

Description

BACKGROUND

The present disclosure pertains to utility resources and particularly to assessment and distribution of the resources. More particularly, the disclosure pertains to beneficial management of resources and their loads.

SUMMARY

The disclosure reveals a use of an installer portal to increase an efficiency of installing resources for demand response systems. Installation of such resources may incorporate registering a client with a particular customer, configuring the client with parameters, installing the client, confirming that the client is communicating properly with a demand response management system, connecting the client to various components at a resource facility, and confirming that the client sends usage or other data correctly to the demand response management system.

BRIEF DESCRIPTION OF THE DRAWING

FIG. 1 is a diagram of an example demand response system;

FIG. 2 is a diagram of a system utilizing an automated demand response program;

FIG. 3 is a diagram of a screen print showing an example of a login at a demand response automation server for obtaining an installer portal;

FIG. 4 is a diagram of a screen print showing an example page in the portal for creating a client;

FIG. 5 is a diagram of a screen print showing an example page of the portal for entering parameters for a client;

FIG. 6 is a diagram of a screen print an example status page of a portal that may indicate such things as whether a client is on or off line;

FIG. 7 is a diagram of a screen print showing an example of a test event being sent to a client from a demand response management system;

FIG. 8 is a diagram of a screen print showing an example layout for events selected on a bar in the portal;

FIG. 9 is a diagram of a screen print showing a graph of usage data sent by a client to a demand response management system; and

FIG. 10 is a diagram of an approach for installing a component in a demand response system.

DESCRIPTION

An effective resource is especially critical when communities are confronted with a scarcity of a resource in question. It may be noted that “resource” is a term which may have several senses or meanings. “Resource” may refer to energy, commodity, product, load, and so on. In another sense or meaning, “resource” such as a demand response (DR) resource may refer to a customer, user, participant, facility, and so on. In the first mentioned sense, it may refer to electricity, water, gas and natural resources such as oil. A definition of resource may be extended to include such things such as water quality and air quality. In this regard, adequate water quality and air quality appear necessary to support a self-sustaining environment.

Resource management, in several senses, may be necessary so that systems can optimize the use of a limited resource. Currently, there are various systems for managing resources in various environments such as buildings, apartments, industrial facilities, and computing systems.

One mechanism that might be used to encourage customers to reduce demand and thereby reduce the peak demand for electricity may be referred to as demand response. Demand response may refer to management of the demand by customers in response to supply conditions. For example, electricity customers may reduce their consumption at critical times and/or costs in response to market prices. These customers may be regarded as DR resources.

DR programs may require that a utility and/or independent service operator (ISO) deliver DR signals to customers or participants via a communications channel. The programs may relate to a distribution of resources such as, but not limited to, electricity, water and natural gas.

DR signals may incorporate business level information, such as prices, reliability and shed levels. At some point, from the utility/ISO to loads in a facility, the business level information sent by the utility/ISO should be processed and used to execute a DR strategy and program for the facility.

DR programs may take many forms. They may differ from normal rates and tariffs in that the DR programs are designed to allow the utility/ISO take specific actions to influence the load profiles of facilities that participate in the DR programs at peak consumption times or periods on a grid. The peak consumption periods may cause critical grid reliability issues which should be addressed, but they may also trigger economic factors where the price of electricity or other power commodity reaches a critical level which may be ameliorated by reducing the overall consumption on the grid during those periods. The critical periods, in which the utility/ISO needs to influence a load profile of a facility, may be referred to as DR events.

A manner in which a utility/ISO may influence a load profile of a facility is to send out a DR signal which is specific to the DR event. DR signals may contain information related to businesses, controlling loads, and so on. There may be an automated DR where the DR signals that are sent out by the utility/ISO are responded to in an automated fashion. Loads within a facility may ultimately be affected by DR events via DR signals to which the facility acts upon or responds. The term “facility” may refer to virtually any location in which there are loads influenced by DR events. A place where there are such loads may be regarded as a “DR resource”. The term “utility” may be used in a general sense to refer to a utility, independent system operator, service provider, and the like.

To provide a context for an aggregation approach, the present disclosure reveals an implementation of DR signals in a demand response arrangement 20 on a diagram of FIG. 1. System 20 and associated software may be effected and operated with one or more computers/controllers (controllers) 22, 23 and respective connections. The arrangement may be a system that is used by utilities/ISO's to manage the operation of DR programs. A focus of the arrangement may be on the operational aspects of managing the selection, signaling and monitoring of the DR resources that are participating in DR programs. The arrangement may be specifically designed to manage operations of automated DR programs.

There may be various types of interactions that might occur between the utility/ISO and a DR resource as part of a DR program. FIG. 1 is a diagram of an example interaction between a utility/ISO 22 and a DR resource (customer) 23. There may be DR signals 39 going from utility/ISO 22 to DR resource 23. There may be DR resource information 46, such as load measurements, going from DR resource 23 to utility/ISO 22.

Terms such as customer, client, user, participant, DR resource, and like terms, may be used, interchangeably or distinct from one another, depending on a context of a pertinent portion of a description or a claim.

A description of DR signals 39 may be noted. At a high level, there may often be some sort of grid condition, be it economic or grid reliability in nature, which triggers a so-called DR event that requires some sort of interaction between the utility/ISO 22 and its customer 23. This interaction may eventually trigger some sort of load control taking place at a customer's facility. The interaction between the utility/ISO 22 and the customer 23 may be mediated by DR signals 39 and DR resource signals 46, i.e., information such as measurements. Signals 39 and 46 may represent communications between utility/ISO 22, and the DR resource or customer 23. Information contained within DR signals 39 may dictate where much of the decision-making takes place relative to, for example, in how the initial grid condition, which triggered the DR event, results in the eventual load control.

A computer or controller may incorporate one or more inputs, a processor, a user interface incorporating a keyboard, a display and a touch screen, a memory, external connections such as an internet, one or more outputs, and so forth. The computer or controller may be utilized with virtually all items in and pertinent to FIGS. 1-9.

Automated demand response (ADR) programs may be used in a number of different customer market segments ranging from large commercial and industrial to small commercial and residential areas. The number of small commercial facilities may typically outnumber the larger commercial and industrial facilities by an order of magnitude. In addition, the large commercial and industrial facilities may typically have a dedicated staff and a larger budget for installing the equipment necessary to participate in ADR programs. What may be needed is an approach and system to simplify the installation process and make it more affordable and easier to use the system and participate in an ADR program.

FIG. 2 is a diagram of an ADR 11. ADR 11 may entail major components such as a demand response management system (DRMS) 12, an energy services interface (ESI) 13, automation equipment 14 and metering equipment 21.

The demand response management system 12 may be used by the electricity service provider 15 (i.e., a utility, independent service operator, or aggregator) to interact with a customer's automation equipment 14 of a customer facility 16 and send the automation equipment so-called “DR signals” 17. An example of a demand response management system may be described in patent application Ser. No. 13/019,943, filed Feb. 2, 2011, which is hereby incorporated by reference.

The energy services interface 13 at the customer's facility 16 may interact with the DRMS 12 in order to receive demand response signals 17 so that automation equipment can intelligibly receive them and send back electrical usage data (e.g., meter data) which are put in a form so that DRMS 12 can intelligibly receive them.

Automation equipment 14 may control customer's loads 19 in response to receiving DR signals 17, via ESI 13, from the DRMS 12. Metering equipment 21 may be used for measuring the usage data. The usage data from meter 21 may be put in a form of meter or usage data 18, via ESI 13, so that DRMS 12 can intelligibly receive them.

An installer referred to herein may be the person responsible for installing the ESI 13 in a customer's facility 16 and connecting ESI 13 to the automation equipment 14 within facility 16 so that the facility can respond to DR signals 17 and send usage data 18 back to the DRMS 12 of provider 15. In general, the functions of receiving the DR signals 17 and returning the usage data 18 in the ESI 13 may be decoupled operations and be implemented in separate devices. The separate devices may be considered to be part of ESI 13.

The present disclosure may be primarily concerned with simplifying the tasks associated with installing the ESI 13. In general, the tasks may need to be performed in order to install an ESI 13 and insure that everything is operating properly. The tasks may incorporate the following items: 1) Register ESI 13 with a particular customer within DRMS 12; 2) Configure ESI 13 with appropriate communication parameters such as security credentials so that ESI 13 can communicate with DRMS 12; 3) Install ESI 13 within the customer's facility 16 and confirm that ESI is communicating properly with DRMS 12; 4) Connect ESI 13 to the customer's automation equipment 14; 5) Connect ESI 13 to the customer's meter 21; 6) Send test DR signals 17 from DRMS 12 to ESI 13; and 7) Confirm that usage or meter data 18 is being sent correctly from ESI 13 to DRMS 12.

In many deployments of ADR tasks, item 1), register ESI 13 with a particular customer within DRMS 12, and item 6), send test DR signals 17 from DRMS 12 to ESI 13, may be performed by an operator of DRMS 12 and need to be scheduled and coordinated with the installer, or vice versa. As the number of customer facilities grows, like that of facility 16, this approach may become burdensome and ideally all the above tasks might be done without the need to coordinate time between various parties.

An approach or solution described herein may simplify the installation process by providing a web-based installer portal with screen print presentations 40-44 in which virtually all of the tasks listed above may be performed by the installer alone without a need to coordinate with other individuals.

Task 1), registering ESI 13 with a particular customer within DRMS 12, and task 2), configuring ESI 13 with appropriate communication parameters, may be performed during a manufacturing of the ESI 13 before it is delivered and installed at the customer site 16; however, for the sake of completeness, the ESI 13 may be supported in the installer's portal presentations 40-44 shown in FIGS. 4-8 to provide flexibility in the installation process.

One may note that certain items of tasks 1-7 listed above may be portrayed in the screen shots 27-33 shown in FIGS. 3-9, respectively, and may be performed in conjunction with the DRMS 12 interfacing with the ESI 13. One may note that in the screen shots 27-33 of FIGS. 3-9, respectively, ESI 13 may be regarded as a “client”.

FIG. 3 is a diagram of a screen print 27 showing an example installer log-in at a demand response automation server (DRAS) page for getting to a DRAS installer portal. In this example, the installer may log into the participant's account so that by default virtually all subsequent actions are done with respect to the participant whose account which the installer has logged into.

The ESI 13 used by the installer to perform the tasks described herein may be implemented as a web-based portal that is integrated with DRMS 12. The installer may need a user name 24 and password 25 entered in the appropriate places as shown by screen print 27, which would allow the installer to securely log into a demand response automation server website by then clicking on a login button 26. The website may be used to perform the tasks listed above.

FIG. 4 is a diagram of a screen print 28 showing an example page (e.g., a DRAS installer portal) for creating ESI 13 entities (clients) which by default may be linked to the participant of whose account which has been logged into by the installer.

Once the installer is logged in, a DRAS installer portal (40) may be revealed in screen print 28, having a bar where “DRAS Participant” has been selected with a click on (button) selection 45. A button 35, entitled clients, of row or bar 56, may be selected. The DRAS installer portal (presentation 40) with a table 34 may appear as shown in screen print 28. Table 34 may have headings of name 121, events 122, programs 123, pending 124, mode 125, last connect 126 and comm. status 127. A selection of buttons 36, 37 and 38, entitled “Complete Installation”, “New Client” and “Delete Clients” may appear on portal (presentation 40). Other items may also appear on the portal.

FIG. 5 is a diagram of a screen print 29 showing an example of entering parameters for ESI 13, specifically the “authentication” parameters necessary for the ESI 13 to communicate with DRMS 12. Here, ESI 13 (client) may be configured.

“New Client” 37 back in portal 40 of FIG. 4, may be clicked on to result in a portal 41 in screen print 29 of FIG. 5 for creating a client. The name of the client may be entered in box 47 of portal 41 in FIG. 5. A password may be entered in box 48 and confirmed in box 49. Button 51 may then be clicked to create the client, or the creating may be canceled by clicking button 52.

FIG. 6 is a diagram of a screen print 30 showing an example of a status page of a portal 42 that may indicate, among other things, whether the ESI 13 is on or off line. This may also indicate whether the ESI 13 is communicating properly with the DRMS 12. Screen print 30 is where ESI 13 (client) communications may be tested.

In portal presentation 42, a bar or row 53 may reveal the client 101, “test.c2”, type 102, “AUTO”, pending status 103, “NONE (OFF)”, mode 104, “NORMAL”, last contact 105, no entry, and communication status 106, “OFFLINE”. Bar or row 54 may reveal client events 107. Event information indicated may incorporate name 111, program 112, start 113, end 114, status 115 and actions 116. Relevant information may be below or alongside a respective heading.

A function of the present approach may be a providing a single login to install clients. In an installer mode, some functionalities may be filtered out, such as aggregation, contacts sub tab and subsuer tab, to ease an installation.

FIG. 7 is a diagram of a screen print 31 showing an example of how a test event may be sent to the ESI 13 from the DRMS 12. Here is where the installer may send test events.

A portal presentation 43 is revealed in screen print 31. A test event 60 of a bar 56 may be clicked on to reveal a creating an event of a test program in portal 43. A notification time of 15:55 on Mar. 25 with a notice of 5 min. is shown for the event, along with a start time of 16:00 on Mar. 25 having a duration of 5 min. for an end time of 16:05 indicated in area 57.

A table 58 in portal 43 shows column headings 61-66 of action and date/time 61, absolute offset from notification (mins) 62, event status 63, mode load_level 64, bid load_amount 65 and price price_absolute 66.

The first row under the headings 61-66 may respectively show 3/25 15:55, 0, Far(Notification), and three spaces with no entries. The second row may show 03/25 15:56, 1, Near, and three spaces with no entries. The third row may show 03/25 16:00, 5, Active(Start), NORMAL, 0.0 and 0.0. The fourth row may show 03/25 16:05, 10, None(end), and three spaces with no entries.

Below area 57 and table 58 may be a block 59 for a list of select clients by name. A client test.c2 appears to be listed. Other clients may be listed. One of the buttons 67, 68 and 69, entitled select all (clients), select none and issue event, respectively, may be clicked on.

A portal presentation 44 in screen print 32 of FIG. 8 may reveal a layout for events 35 selected on bar 56. One event revealed for the client list in block 59 of FIG. 7 may be shown in a table 70 under labels 71-77 incorporating name and program 71, clients 72, remaining time 73, start 74, end 75, status 76 and actions 77. The row under the headings 71-77 may show information respectively such as Test Program_—0325-154831 and Test Program, test.c2, 0 Days, 0 Hours, 14 Minutes, 03/25 16:00, 3/25 16:05, RECEIVED and Opt-out. Test DR signals may be sent.

FIG. 9 is a diagram of a screen print 33 showing a graph which may be used to confirm that the usage or meter data 18 are being sent correctly from the ESI 13 to the DRMS 12. Here is where there may be the testing of usage information conveyance.

Screen print 33 may reveal a DRAS customer interface 80 of 03/25 at 16:15 for the noted client of the preceding installer portal presentations of the previous Figures. A usage button 81 of a bar 56 may be clicked. Headings of base 83, actual 84 and shed 85 of an information box 86 may reveal usage data of the client. Box 86 may incorporate two rows, one for the entire day and a second for during an event, as indicated under the heading of base 83. In each of the rows there may also be indicated Avg (KW) and total (KWH) under each of the headings of base 83, actual 84 and shed 85. In the first row, data may be indicated as 0 (zero) for base 83, 37.663 KW and 2,711.752 KWH for actual 84, and −37.663 KW and −2,711.752 KWH for shed 85. In the second row, for base 83, actual 84 and shed 85, the data entries appear as 0 (zero).

Also in the DRAS customer interface 80 is a graph 90 showing power usage in KW versus a time of the power usage. Legend 91 indicates a graph selection of projected normal usage and current usage. As noted, current usage is selected for graph 90. A calendar 92 indicates a date of the usage. Screen print 33 may merely be one illustrative example of usage by a client (or customer).

To recap, a demand response system may incorporate a facility of a participant and a utility service provider. The facility may incorporate an energy services interface, an energy usage measuring instrument connected to the energy services interface, automation equipment connected to the energy services interface, and one or more energy usage loads connected to the automation equipment. The utility service provider may incorporate a demand response management system connected to the energy services interface. An installer of the energy services interface may log in with a computer into a demand response automation server website to pull up a demand response automation server installer portal on a display screen. The installer may be logged into an account of the participant.

The energy services interface may be selected and created in the portal. The energy services interface may be registered with the demand response management system for the participant. The energy services interface may be configured by entering parameters in the portal to configure the energy services interface necessary for the energy services interface to communicate with the demand response management system. The portal may indicate whether the energy services interface is communicating satisfactorily with the demand response management system. The portal may provide information about the energy services interface and/or events. The portal may enable the installer to have a test event to be sent from the demand response management system to the energy services interface. The portal may enable the installer to confirm data of the meter being sent correctly from the energy services interface to the demand response management system. The portal may reveal energy usage data from the energy services interface.

Virtually all actions by the installer via the demand response automation server installer portal may be performed on behalf of the participant if the installer is logged into the account of the participant.

The energy services interface may be registered with the demand response management system during a manufacturing of the energy services interface. During the manufacturing of the energy services interface, the energy services interface may be configured with one or more parameters for communication with the demand response management system.

FIG. 10 is a diagram of an approach 130 for installing a component in a demand response system. The approach may incorporate more or less steps or symbols, and the order may be different, as approach 130 is just an illustrative example. The approach may incorporate logging in with a computer into a demand response automation server website to obtain a demand response automation server installer portal on a screen in symbol 131, selecting a client on the portal in symbol 132, and registering the client in the portal with a demand response management system in an account of a participant in symbol 133.

The client may be an interface for a demand response resource facility of the participant. One or more tasks for installation of the client may be performed via the portal on behalf of the participant.

Approach 130 may further incorporate configuring the client with one or more parameters in the portal for communication with the demand response management system in symbol 134. The approach may also incorporate determining from the portal whether the client is communicating satisfactorily with the demand response management system in symbol 135.

Approach 130 may further yet incorporate obtaining information about the client and client events from the portal in symbol 136, and sending a test event from the demand response management system to the client with the portal in symbol 137. The approach may further incorporate confirming that energy usage data from the client is sent to the demand response management system with the portal in symbol 138.

An approach for installing an energy services interface in a demand response system, may incorporate providing a web-based installer portal via a computer, creating an energy services interface at the portal, registering the energy services interface with a particular customer within a demand resource management system, during a manufacturing of the energy services interface, and configuring the energy services interface with appropriate communication parameters during the manufacturing of the energy services interface.

An installer may log in at a demand response automation server page to get to the installer portal. The installer may log into an account of a participant so that virtually all actions are performed on behalf of the participant.

The web-based installer portal may be integrated with the demand response management system. The portal may be used to perform tasks for installing the energy services interface.

The energy services interface may be configured via the portal for communication with the demand response management system. The energy services interface may be tested via the portal for communicating properly with the demand response management system. A test event may be sent to the energy services interface from the demand response management system via the portal.

Usage data may be confirmed as being with the portal conveyed correctly from the energy services to the demand response management system. The usage data may be displayed graphically.

In the present specification, some of the matter may be of a hypothetical or prophetic nature although stated in another manner or tense.

Although the present system and/or approach has been described with respect to at least one illustrative example, many variations and modifications will become apparent to those skilled in the art upon reading the specification. It is therefore the intention that the appended claims be interpreted as broadly as possible in view of the related art to include all such variations and modifications.

Claims

1. A demand response system comprising: a facility of a participant; anda utility service provider; andwherein:the facility comprises: an energy services interface;an energy usage measuring instrument connected to the energy services interface;automation equipment connected to the energy services interface; andone or more energy usage loads connected to the automation equipment;the utility service provider comprises a demand response management system connected to the energy services interface;an installer of the energy services interface logs in with a computer into a demand response automation server website to pull up a demand response automation server installer portal on a display screen;the installer is logged into an account of the participant;determining from the portal whether the participant is communicating satisfactorily with the demand response management system; andconfirming that energy usage data from the participant is sent to the demand response management system with the portal; andwherein:a client is an interface for a demand response resource facility of the participant; andone or more tasks for installation of the client are performed via the portal on behalf of the participant.

2. The system of claim 1, wherein: the energy services interface is selected and created in the portal;the energy services interface is registered with the demand response management system for the participant;the energy services interface is configured by entering parameters in the portal to configure the energy services interface necessary for the energy services interface to communicate with the demand response management system;the portal indicates whether the energy services interface is communicating satisfactorily with the demand response management system;the portal provides information about the energy services interface and/or events;the portal enables the installer to have a test event to be sent from the demand response management system to the energy services interface;the portal enables the installer to confirm data of the meter being sent correctly from the energy services interface to the demand response management system; and/orthe portal reveals energy usage data from the energy services interface.

3. The system of claim 1, virtually all actions by the installer via the demand response automation server installer portal are performed on behalf of the participant since the installer is logged into the account of the participant.

4. The system of claim 1, wherein: the energy services interface is registered with the demand response management system during a manufacturing of the energy services interface; andduring the manufacturing of the energy services interface, the energy services interface is configured with one or more parameters for communication with the demand response management system.

5. A method for installing a component in a demand response system, comprising: logging in with a computer into a demand response automation server website to obtain a demand response automation server installer portal on a screen;selecting a client on the portal;registering the client in the portal with a demand response management system in an account of a participant;configuring the client with one or more parameters in the portal for communication with the demand response management system;determining from the portal whether the client is communicating satisfactorily with the demand response management system; andconfirming that energy usage data from the client is sent to the demand response management system with the portal; andwherein:the client is an interface for a demand response resource facility of the participant; andone or more tasks for installation of the client are performed via the portal on behalf of the participant; andwherein:the client is an interface for a demand response resource facility of the participant; andone or more tasks for installation of the client are performed via the portal on behalf of the participant.

6. The method of claim 5, further comprising obtaining information about the client and client events from the portal.

7. The method of claim 6, further comprising sending a test event from the demand response management system to the client with the portal.