JP2016009438A - Demand adjustment system, demand adjustment device, demand adjustment method, and demand adjustment program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a demand adjustment system capable of easily responding to the correction/addition of a use case for demand adjustment.SOLUTION: A use case template engine 11 generates use case definition information constituted of information on a message to be transmitted/received and the information of state transition from information input on a use case input screen, and stores the use case definition information in a use case definition database 111, and a use case flow engine 12 generates and starts an instance which operates in accordance with the use case definition information, and a protocol frame work 13 processes a demand response protocol under control from the use case flow engine 12. Thus, it is possible to perform demand adjustment by a demand response protocol only by inputting information to the use case input screen of the use case template engine 11.

Description

  The present invention relates to a technique for adjusting power supply and demand.

  With the diversification of power generation methods, power supply has become unbalanced between supply and demand, causing power outages due to insufficient power generation and system instability due to excessive generation of renewable energy. The power supply company predicts the amount of power supplied from the weather forecast and makes a power generation plan, but reserves power to prepare for unforeseen circumstances such as sudden changes in temperature, fluctuations in the production plan of the customer, and troubles in power generation facilities. It is necessary to have.

  The conventional method of equalizing the supply-demand balance was only supply-side adjustment by the power supplier that adjusts the amount of power generated according to the amount of power demand. It has been verified that the excess can be adjusted more efficiently.

  For this reason, there is a supply and demand adjustment business in Europe and the United States in which when the supply amount is insufficient, the customer side cooperates in peak cuts and peak shifts to reduce power consumption, and pays the amount corresponding to the cooperation as an incentive. In the supply and demand adjustment, a business operator (hereinafter referred to as an aggregator) who performs a certain amount of power adjustment by gathering customers plays a role of adjusting the consumer in response to the demand of the supply business.

  Conventionally, an aggregator adjusts supply and demand with telephones and e-mails with individual customers. However, since the aggregator lacks responsiveness and accuracy of adjustment amount, automation by systematization is required. Therefore, standardization of the procedure for systematizing these supply and demand adjustments (OASIS OpenADR2.0, ZigBee Alliance SEP2.0, etc., hereinafter referred to as demand response protocol) has been proposed.

  When demand adjustment is systematized and communication is performed using a demand response protocol, there are the following problems.

  First, there are various use cases that determine how to adjust supply and demand, and it is necessary to make adjustments in advance on the supply side and on the consumer side (for organizations that define generic use cases, the Energy Information Standards (EIS) Alliance, North American Energy Standards Board (NAESB), IEC TC57 WG21, JSCA DR-TF, etc.). For example, as a method for requesting supply and demand adjustment, there is a method of requesting notification of a target reduction amount, a request of notification of an incentive price for the reduction amount, a request for control notification of a specific customer theory. In addition, there are various combinations such as the date and time of notification in advance, the number of notifications, whether or not to respond to whether adjustment is available, and adjustment of the schedule that can be handled.

  In addition, it is necessary to cope with changes in use cases and new use cases, such as the case where the supply and demand adjustment time period is morning, noon, evening, and the adjustment time changes according to the season. Since these use cases depend on the customer, it must be defined for each customer.

  In addition, there is a problem that a new demand response protocol has to be implemented in a conventional customer-side system (such as xEMS). When automatically controlling devices, it is often necessary to convert between demand response protocols and conventional protocols (BACnet, EchonetLite, Multispeak, etc.).

  In order to realize a supply and demand adjustment system using the demand response protocol with the conventional method of implementing an application for each use case, first define the use case of the supply and demand adjustment method with a general expression method such as a business flow. The range that can be implemented by the demand response protocol is extracted based on the general definition, the message flow is designed to realize this use case, and the requirements are defined such as cancellation and acceptance. Replace with EiEvent, EiOpt, etc.) and determine the value of the payload of each message (such as SignalName, SignalType in OpenADR). Based on these designs, the demand response protocol itself is implemented in both the aggregator-side system and the customer-side system, and an application for operating this use case is designed and implemented, and the initial use case is verified. It is realized through the process.

“OpenADR Standardization Trend”, NTT Technical Journal, Nippon Telegraph and Telephone Corporation, October 2013, Vol. 25, No. 10, pp.38-41

  Systematization of the supply and demand adjustment system using the demand response protocol can be expected to improve interoperability, while at the same time, the systemization corresponding to various characteristics of the supply and demand adjustment method (use case) can be realized and the supply and demand can be reduced. The balance can be improved with high accuracy. However, a deep understanding of the demand response protocol is indispensable, and if diversity is required, systemization becomes complicated, and there is a problem that it is impossible to cope with changes and additions. Since the use cases differ from customer to customer, and in order to maximize and maintain the effect, readjustment after implementation of the use case at the pre-planning stage is indispensable. Has a problem. In addition to the use cases between aggregators and consumers, supply and demand that communicates information using demand response protocols between various operators (hereinafter referred to as actors) such as suppliers, transmission and distribution system operators, and market market operators. Coordinating use cases are required, adding to the complexity.

  The present invention has been made in view of the above, and an object of the present invention is to provide a supply and demand adjustment system that can easily cope with correction / addition of use cases for supply and demand adjustment.

  A supply and demand adjustment system according to a first aspect of the present invention is a supply and demand adjustment system that executes a power supply and demand adjustment use case using a demand response protocol, and includes a plurality of supply and demand adjustment devices assigned to each business operator. The supply and demand adjustment device accepts parameters and message information necessary for supply and demand adjustment, generates use case definition information including information on messages to be transmitted and received and state transition information, and stores the use case definition information in a use case definition storage unit. Reads the use case definition information from the case definition generation means and the use case definition storage means, operates according to the use case definition information, and generates a demand response protocol message corresponding to the message when transmitting the message. Use case execution means to In the supply and demand adjustment device assigned to each, the use cases defined by the supply and demand adjustment use cases are respectively input, and there are use cases for receiving requests for supply and demand adjustment and use cases for requesting supply and demand adjustments. The inputted supply and demand adjustment device operates by linking the use cases.

  The supply and demand adjustment apparatus according to the second aspect of the present invention is a supply and demand adjustment apparatus that adjusts the supply and demand of power using a demand response protocol, and receives information about parameters and messages necessary for supply and demand adjustment, and information about messages to be transmitted and received Use case definition generating means for generating use case definition information including state transition information and storing the use case definition information in the use case definition storing means, and reading the use case definition information from the use case definition storing means, And a use case executing means for generating a message of a demand response protocol corresponding to the message when transmitting the message.

  In the supply and demand adjustment device, the supply and demand adjustment device receives a request for supply and demand adjustment from a higher-order supply and demand adjustment device, and requests a lower-order supply and demand adjustment device for supply and demand adjustment. The first use case definition information that receives a request for supply and demand adjustment and the second use case definition information that requests a supply and demand adjustment are stored in association with each other, and the use case execution means receives the request for supply and demand adjustment. It operates according to the first use case definition information, and operates according to the second use case definition information in cooperation with the first use case definition information.

  The supply and demand adjustment apparatus includes an interface providing unit that provides an interface for acquiring an instruction to the use case executing unit and a state of an instance activated by the use case executing unit.

  ADVANTAGE OF THE INVENTION According to this invention, the supply-and-demand adjustment system which can respond easily to correction and addition of the use case for supply-and-demand adjustment can be provided.

It is a whole lineblock diagram of the supply-and-demand adjustment system in this embodiment. It is a sequence diagram which shows the supply-demand adjustment use case performed with the supply-demand adjustment system in this Embodiment. It is a functional block diagram which shows the structure of a supply-and-demand adjustment gateway. It is a figure which shows the example of the screen which inputs the information for registering the use case of an event. It is a sequence diagram which shows the sequence of a certain use case. It is a sequence diagram which shows the sequence of another use case. It is a figure which shows the example of the screen which inputs the information for registering the use case of a report. FIG. 6 is a sequence diagram illustrating an example in which a supply and demand adjustment gateway executes the use case of FIG. 5. It is a figure which shows the example of API which a supply-and-demand adjustment gateway provides. It is a figure which shows the example of the use case which the supply-and-demand adjustment gateway of an aggregator performs.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  FIG. 1 is an overall configuration diagram of a supply and demand adjustment system according to the present embodiment configured with a plurality of supply and demand adjustment gateways (demand and supply adjustment devices).

  In the example shown in FIG. 1, there are one supplier, multiple aggregators, and multiple customers as actors, and each actor has a supply and demand adjustment gateway 1. The supply and demand adjustment gateway 1 of each actor is arranged on the cloud. The supply and demand adjustment gateway 1 can be composed of a multi-stage configuration and a plurality of adjacent supply and demand adjustment gateways 1. The supply and demand adjustment gateway 1 communicates using a demand response protocol. A system (xEMS or the like) unique to each actor that does not implement the demand response protocol and the supply and demand adjustment gateway 1 cooperate with each other via an API (Application Programming Interface) of the supply and demand adjustment gateway 1.

  Using the supply and demand adjustment system shown in FIG. 1, a supply and demand adjustment use case involving a plurality of actors as shown in FIG. 2, for example, is executed. The use case of each actor defined in the supply and demand adjustment use case is input to each supply and demand adjustment gateway 1 assigned to each actor. For example, in the example of FIG. 2, as a use case related to a DR (Demand Response) event, a use case in which sending / receiving and checking of an advance notice / request is confirmed between a supplier and an aggregator, and an activation request is issued between an aggregator and a customer. Includes use cases for sending and receiving. In addition, the use cases related to reports include a use case for transmitting and receiving an amount suppressed by DR execution between a customer and an aggregator, and a use case for reporting results between an aggregator and a supplier. Here, the use case of overall supply and demand adjustment is referred to as a supply and demand adjustment use case, and each use case of an actor is simply referred to as a use case.

  The aggregator in FIG. 2 receives a request for supply and demand adjustment from a supplier and requests a consumer for supply and demand adjustment. The aggregator supply and demand adjustment gateway 1 receives a use case for requesting supply and demand adjustment and a use case for requesting supply and demand adjustment. These use cases input to the supply and demand adjustment gateway 1 of the aggregator are associated with each other and operate in cooperation with each other. Specifically, when the supply / demand adjustment gateway 1 of the aggregator receives the advance notice / request from the supplier, the aggregator returns a confirmation of the advance notice / request according to the use case between the supplier and the aggregator, and between the aggregator and the customer. Send the activation request according to the use case.

  Next, the supply and demand adjustment gateway will be described. FIG. 3 is a functional block diagram showing the configuration of the supply and demand adjustment gateway.

  The supply and demand adjustment gateway 1 illustrated in FIG. 3 includes a use case template engine 11, a use case flow engine 12, a protocol framework 13, and an API processing unit 14. Each unit included in the supply and demand adjustment gateway 1 may be configured by a computer including an arithmetic processing device, a storage device, and the like, and the processing of each unit may be executed by a program. This program is stored in a storage device included in the supply and demand adjustment gateway 1, and can be recorded on a recording medium such as a magnetic disk, an optical disk, or a semiconductor memory, or provided through a network.

  The use case template engine 11 presents a use case input screen, inputs parameters necessary for supply and demand adjustment, information on messages, and the like, and uses case definition including information on messages to be transmitted and received and information on state transitions. Information is generated and stored in the use case definition database 111. Use case input and generated use case definition information will be described later.

  The use case flow engine 12 reads use case definition information from the use case definition database 111, creates an instance of the execution object, starts it, and manages the state in the use case execution database 121. The use case flow engine 12 operates based on the use case definition information, requests the protocol framework 13 to perform a demand response protocol process, and starts a data flow with another supply and demand adjustment gateway 1. For example, if the use case definition information includes sending an advance notice message, generate a demand response protocol message corresponding to the advance notice message and obtain the necessary information from the use case definition information. It is put on the generated message and passed to the protocol framework 13. Further, the use case flow engine 12 makes a state transition in response to a request from the API processing unit 14 and returns state information and the like to the API processing unit 14.

  The protocol framework 13 includes an event processing unit 131 and a report processing unit 132, and performs a demand response protocol process with the opposing supply and demand adjustment gateway 1. The event processing unit 131 performs processing related to an event such as a demand / supply adjustment request, and the report processing unit 132 performs processing related to a report such as weighing.

  The API processing unit 14 provides an API for controlling the use case flow engine 12 to an external application (such as xEMS), and controls the use case flow engine 12 according to the API. In this embodiment, the API is provided as a Web API, and the supply and demand adjustment gateway 1 is arranged on the cloud, so that the external application is released from the implementation of the application process depending on the use case and the implementation of the demand response protocol.

  Next, use case input and generated use case definition information will be described.

  The types of use cases input to the use case template engine 11 are roughly classified into two types: events relating to the triggering of supply and demand adjustment and reports relating to reporting of energy usage and restraint.

  FIG. 4 shows an example of a screen for inputting information for registering an event use case. On the screen shown in FIG. 6, it is possible to input information such as start / end date / time, request destination, type (event in FIG. 4), and information related to a message for requesting supply and demand adjustment. The requested group is a group of a plurality of actors, and is designated when requesting supply and demand adjustment to the plurality of actors collectively.

  As information related to a message for requesting supply and demand adjustment, an event type (a type of a method for requesting supply and demand adjustment such as a suppression amount and a price), necessary information according to the event type, and presence / absence of an acceptance response request can be input. The presence / absence of an acceptance response request indicates whether a response message is returned.

  In addition, information related to a prior notice message transmitted prior to a message for requesting supply and demand adjustment can be input here.

  Messages for requesting supply and demand adjustment and advance notice messages can be increased or decreased using the add and delete buttons on the right side of the screen. For example, if the aggregator and the customer have a contract to send advance notice twice or more before requesting supply and demand adjustment, operate the add button of the advance notice message and send the advance notice. Increase your message. Alternatively, when the contract is not necessary for the advance notice, the advance notice message deletion button is operated to delete the advance notice message.

  By inputting necessary information in FIG. 4 and operating the registration button at the bottom of the screen, the use case template engine 11 generates use case definition information and stores it in the use case definition database 111. The use case flow engine 12 reads out this use case definition information, creates an instance of the execution object, and activates it, thereby requesting supply and demand adjustment using the demand response protocol.

  A specific example of a use case input using the screen of FIG. 4 will be described.

  For example, for a message requesting supply and demand adjustment, if an acceptance response request is “Yes”, a prior notice message is required on the previous day, and an acceptance response request is also “Yes” for the advance notice message, as shown in FIG. In addition, the advance notice message and the response message are sent and received the day before the supply and demand adjustment is activated, and the use case definition information that changes the state according to the sequence in which the message and the response message are sent and received on the day of the supply and demand adjustment is generated. And stored in the use case definition database 111. The use case definition information includes parameters described in each message. Note that the message here is not a message defined by the demand response protocol, but a message generally expressed by a prior notice message, a demand / supply adjustment request message, or the like.

  As another example, regarding a message for requesting supply and demand adjustment, when an acceptance response request is “none” and a prior notice message is not required, a message for requesting supply and demand adjustment on the day of supply and demand adjustment is activated as shown in FIG. The use case definition information that only transmits is generated and stored in the use case definition database 111.

  Report use cases are registered by entering information in the same way as event use cases. FIG. 7 shows an example of a screen for inputting information for registering a use case of a report. On the screen shown in FIG. 6, it is possible to input information such as start / end date / time, request destination, type (report in FIG. 7), collection cycle, and information on a message for transmitting the report. As information about a message for transmitting a report, a report type for designating a format for transmitting the report (for example, suppressed power consumption, power consumption, etc.) can be input. You can increase or decrease the number of messages to be sent with the add button and delete button.

  The use case template engine 11 generates use case definition information and stores it in the use case definition database 111 by inputting necessary information in FIG. 7 and operating the registration button at the bottom of the screen. The use case flow engine 12 reads out this use case definition information, creates an instance of the execution object, and starts it up, thereby transmitting a report using a demand response protocol.

  Next, the operation of the supply and demand adjustment gateway 1 will be described.

  FIG. 8 is a sequence diagram showing an example in which the supply and demand adjustment gateway 1 executes the use case shown in FIG.

  First, the aggregator / customer xEMS instructs the supply / demand adjustment gateways 1A, 1B to execute a use case by API (steps S101, S301). The API communication provided by the supply and demand adjustment gateways 1A and 1B is performed between the aggregator and the customer's xEMS and the supply and demand adjustment gateways 1A and 1B. FIG. 9 shows an example of the API. APIs are roughly divided into a side (TN) that instructs supply and demand adjustment and a side (EN) that receives an instruction. The API parameters include parameters for specifying use cases. API parameters do not depend on the definition of use cases.

  When the use case flow engine 12 of the supply and demand adjustment gateways 1A and 1B creates and starts an instance of the execution object of the use case definition information, the demand and supply adjustment gateway 1B of the consumer sends a registration request to the supply and demand adjustment gateway 1A of the aggregator Then, a registration request acceptance response is received (S201). Thereafter, communication according to the demand response protocol is performed between the supply and demand adjustment gateways 1A and 1B.

  On the day before the request for the supply and demand adjustment, the supply and demand adjustment gateway 1A transmits an advance notice to the consumer's supply and demand adjustment gateway 1B using the demand response protocol based on the use case definition information (step S202). In step S202 of FIG. 8, the supply and demand adjustment gateway 1B transmits an oadrPoll message to the supply and demand adjustment gateway 1A, and receives an oadrDitributEvent message including the contents of the advance notice from the supply and demand adjustment gateway 1A. The contents and conditions of messages transmitted and received between the supply and demand adjustment gateways 1A and 1B are defined in the use case definition information. For example, in the example of FIG. 8, it is defined in the use case definition information that the supply and demand adjustment gateway 1 </ b> B periodically inquires the supply and demand adjustment gateway 1 </ b> A by an oadrPoll message. The use case flow engine 12 creates a demand response protocol message based on the use case definition information, and requests the protocol framework 13 to process the demand response protocol. The use case flow engine 12 changes the state according to message transmission / reception, a timer, and the like.

  The customer's xEMS acquires an advance notice from its own supply / demand adjustment gateway 1B using the API (step S302), and notifies the supply / demand adjustment gateway 1B using the API of a response indicating that the supply / demand adjustment is accepted (step S303).

  The supply / demand adjustment gateway 1B transmits a response to the advance notice to the supply / demand adjustment gateway 1A to the supply / demand adjustment gateway 1A (step S203). The aggregator xEMS acquires a response to the advance notice from the supply and demand adjustment gateway 1A using the API (step S102).

  On the day of the activation date, the supply and demand adjustment gateway 1A transmits an activation request to the supply and demand adjustment gateway 1B (step S204).

  The customer's xEMS acquires an activation request from the supply and demand adjustment gateway 1B and returns a response (steps S304 and S305). The supply and demand adjustment gateway 1B transmits a response to the activation request to the supply and demand adjustment gateway 1A (step S205). The aggregator xEMS acquires a response to the activation request from the supply and demand adjustment gateway 1A (step S103).

  With the above processing, supply and demand adjustment is started.

  After the supply / demand adjustment is started, the aggregator and the customer's xEMS acquire the supply / demand adjustment state using the state acquisition API (steps S104 and S306), and when the supply / demand adjustment is completed, the message history API is used to acquire the message history. (Steps S105 and S307).

  In FIG. 8, the xEMS of the aggregator and the customer performed the supply and demand adjustment using the API of the supply and demand adjustment gateways 1A and 1B. However, a use case in which the operator accesses the supply and demand adjustment gateway 1A and requests the supply and demand adjustment. The operator may start up, check the request content by accessing the supply and demand adjustment gateway 1B, and instruct xEMS to supply and demand adjustment according to the request content.

  Next, a use case of an aggregator supply and demand adjustment gateway will be described.

  The supply / demand adjustment gateway 1 of the aggregator performs processing for receiving a request for supply / demand adjustment from the higher-order supply / demand adjustment gateway 1 and processing for requesting supply / demand adjustment to the lower-order supply / demand adjustment gateway 1. In the supply / demand adjustment gateway 1 of the aggregator, use case definition information that is activated to transmit / receive a message to / from the lower supply / demand adjustment gateway 1 when a message is received from the higher supply / demand adjustment gateway 1 is specified.

  In the example shown in FIG. 10, the use case 200 is designated as the use case 100 in the supply and demand adjustment gateway 1 of the aggregator. When the supply / demand adjustment gateway 1 of the aggregator receives the message of the use case 100, the use case 200 is executed. The supply / demand adjustment gateway 1 of the aggregator operates the use case 100 and the use case 200 in cooperation with each other, and forwards the message received from the supply / demand adjustment gateway 1 of the upper supplier to the supply / demand adjustment gateway 1 of the lower customer. Then, the message received from the supply / demand adjustment gateway 1 of the lower-order customer is transferred to the supply / demand adjustment gateway 1 of the higher-order supplier.

  As described above, according to the present embodiment, the supply and demand adjustment gateway 1 includes the use case template engine 11, the use case flow engine 12, and the protocol framework 13, and the use case template engine 11 is displayed on the use case input screen. From the input information, use case definition information composed of information about messages to be transmitted and received and state transition information is generated and stored in the use case definition database 111. The use case flow engine 12 is used by the use case definition database. The use case definition information is read from 111, an instance that operates according to the use case definition information is generated and started, and the protocol framework 13 is controlled by the use case flow engine 12 under the demand response process. By processing col, simply inputting information on the use case input screen of the use case template engine 11, the demand and supply can be adjusted by the demand response protocol, and the existing actor that has the API provided by the supply and demand adjustment gateway 1 By using the xEMS, it is possible to incorporate a supply and demand adjustment function. To modify or add a use case, it is only necessary to input information on the use case input screen of the use case template engine 11. Therefore, the modification of the system to the modification and addition of the use case can be minimized, and the dependency of the demand response protocol can be reduced. Can be minimized.

  In addition, since the standard specification of the demand response protocol is secured by the supply and demand adjustment gateway 1, the examination / implementation of non-functional requirements can be minimized.

DESCRIPTION OF SYMBOLS 1 ... Supply-demand adjustment gateway 11 ... Use case template engine 111 ... Use case definition database 12 ... Use case flow engine 121 ... Use case execution database 13 ... Protocol framework 131 ... Event processing part 132 ... Report processing part 14 ... API processing part 100 , 200 ... Use cases

Claims (7)

A supply and demand adjustment system that executes a power supply and demand adjustment use case using a demand response protocol,
It has multiple supply and demand adjustment devices assigned to each company,
The supply and demand adjustment device is
A use case definition generating means for receiving parameters and message information necessary for supply and demand adjustment, generating use case definition information including information on messages to be transmitted and received and state transition information, and storing the use case definition storage means;
Read the use case definition information from the use case definition storage means, operate according to the use case definition information, and when sending a message, use case executing means for generating a message of a demand response protocol corresponding to the message; Have
In the supply and demand adjustment device allocated to each business operator, the use cases of each business operator defined in the supply and demand adjustment use case are respectively input, and the use case that receives a request for supply and demand adjustment and the use that requests the supply and demand adjustment. The supply and demand adjustment system, wherein a case is input, operates in cooperation with the use cases. A supply and demand adjustment device that adjusts the supply and demand of power using a demand response protocol,
A use case definition generating means for receiving parameters and message information necessary for supply and demand adjustment, generating use case definition information including information on messages to be transmitted and received and state transition information, and storing the use case definition storage means;
Read the use case definition information from the use case definition storage means, operate according to the use case definition information, and when sending a message, use case executing means for generating a message of a demand response protocol corresponding to the message; ,
A supply and demand adjustment device comprising: The supply and demand adjustment device receives a request for supply and demand adjustment from an upper supply and demand adjustment device, and requests a supply and demand adjustment to a lower order supply and demand adjustment device,
The use case definition accumulating means stores first use case definition information that receives a request for supply and demand adjustment in association with second use case definition information that requests a supply and demand adjustment;
The use case execution means operates in accordance with the first use case definition information when receiving a request for supply and demand adjustment, and in accordance with the second use case definition information in cooperation with the first use case definition information. The supply and demand adjustment apparatus according to claim 2, wherein the supply and demand adjustment apparatus operates.   4. The supply and demand adjustment apparatus according to claim 2, further comprising an interface providing unit that provides an interface for acquiring an instruction to the use case executing unit and a state of the use case executing unit. A supply and demand adjustment method executed by a supply and demand adjustment device that adjusts supply and demand of power using a demand response protocol,
Receiving parameters necessary for supply and demand adjustment and message information, generating use case definition information including information on messages to be transmitted and received and state transition information, and storing the use case definition storage means in a use case definition storage unit;
Reading the use case definition information from the use case definition storage means, and operating according to the use case definition information;
Generating a demand response protocol message corresponding to the message when sending the message;
A method for adjusting supply and demand, comprising: The supply and demand adjustment device receives a request for supply and demand adjustment from an upper supply and demand adjustment device, and requests a supply and demand adjustment to a lower order supply and demand adjustment device,
The use case definition accumulating means stores first use case definition information that receives a request for supply and demand adjustment in association with second use case definition information that requests a supply and demand adjustment;
A step of operating according to the first use case definition information when receiving a request for supply and demand adjustment;
6. The supply and demand adjustment method according to claim 5, further comprising a step of operating in accordance with the second use case definition information in cooperation with the first use case definition information. A supply and demand adjustment program that adjusts the supply and demand of power using a demand response protocol,
Processing for receiving parameters and message information necessary for supply and demand adjustment, generating use case definition information including information on messages to be transmitted and received and state transition information, and storing them in the use case definition storage means;
A process of reading the use case definition information from the use case definition storage means and operating according to the use case definition information;
When sending a message, processing to generate a demand response protocol message corresponding to the message,
Supply and demand adjustment program characterized by causing computer to execute.

Images