• 专利附录
  • 专利说明
  • 权利要求
  • 类似技术
  • 同族专利
  • 引用文献
  • 法律状态
  • 优先权
    • 专利摘要:
    Electrical power demand management device, to effectively establish a demand adjustment. A dr server includes: a communication unit that communicates with client terminals that manage devices through a communication network; a program unit that creates an electrical power demand adjustment program that shows the amount of demand adjustment assigned to at least a first client terminal, based on predetermined limiting conditions and client information received from client terminals; a program execution unit that transmits the generated electrical power demand setting, and commands the first client terminal to execute the power demand adjustment; and a provision unit that provides information that includes the cause of the failure, when the electric power demand adjustment can not be created. (Machine-translation by Google Translate, not legally binding)
    公开号:ES2609516A2
    申请号:ES201630290
    申请日:2016-03-14
    公开日:2017-04-20
    发明作者:Nobuyuki Ohama；Masao Tsuyuzaki；Itsuya NISHIKAWA；Masato Utsumi；Syuuichi Yoshida；Yasuhiro Kawai；Jyunpei OGAWA；Shingo IZUMI
    申请人:Hitachi Ltd；
    IPC主号:
    专利说明:

    5 Background of the invention
    1. Field of the invention
    The present invention relates to an electrical power demand adjustment program management apparatus and an electrical power demand adjustment program management method.
    10 2. Description of the related technique
    The demand for electric power fluctuates daily. When the demand for electric power has a peak in a given block of time, electric companies need to be able to operate sufficiently and be equipped with sufficient facilities to meet the corresponding peak demand. A big difference between the
    The supply and demand of electrical power causes a problem in the stability of the electricity grid and in the quality of the electrical power.
    Therefore, it is considered a response to the demand (referred to hereinafter as "DR", as appropriate), in which a power supplier side requests an electric power client side to reduce or increase the amount from
    20 electric power consumption.
    The DR to manipulate the amount of electric power consumption has been implemented with a manual communication unit such as a telephone. Around 2013, standard OpenADR 2.0b specifications were established ("OpenADR Alliance Releases 2.0b Profile Specification for Full Featured Demand Response Programs", published by
    25 OpenADR Alliance, July 2013, URL = http://www.openadr.org/index.php option=com_content&view=article&id=84:openadralliance-releases-2-0b-profile-specification&catid=21: press-releases & ltemid = 121) for automatic DR, and since then automatic DRs have been increasingly used. These standard specifications define how communications are made, and do not define how
    30 the DR program is established.
    Based on EiEvent and EiReport which are main functions in OpenADR 2.0b, they have
    provided communication specifications ("Demand and response interface specification version 1.0 (Draft)", published by JSCA, May 2013, URL = http://www.meILgo.jp/press/2013/05/20130515004/20130515004-7 .pdf) for DR in Japan as a subset of OpenADR 2.0b.
    The DR program is established to determine how far and in what time block a customer's device should fit (Japanese patent application open for public consultation 2013-9565). In Japanese Patent Application No. 2013-9565, a DR program is described. It is considered sufficient if the DR is made as uniform as possible if the objectives for it are not achieved.
    Summary of the invention
    When a DR program that achieves a goal cannot be established, a DR program planner attempts to reset the program by performing any of the following operations so that the DR program can be established.
    As a first operation, the DR program planner asks a customer who participates in the DR program to reduce a desired customer value. For example, the DR program planner asks the customer to reduce the desired value of the least acceptable assigned amount of adjustment.
    As a second operation, the DR program planner again requests a client, who was asked to participate in the DR program and responded by refusing to participate in the DR program, to participate in the DR program.
    The DR program planner reviews the conditions associated with a request such as a restriction and an incentive to provide an advantage to a client.
    Therefore, these operations to establish the DR program that achieves the objective were carried out manually, and therefore inefficiently, based on the experience of the DR program planner.
    In view of the foregoing, an object of the present invention is to provide an electrical power demand adjustment program management apparatus and an electrical power demand adjustment program management method with which an energy efficiency program can be effectively established. Electric power demand adjustment.
    To achieve the objective, a management apparatus of the demanded electrical power adjustment program is proposed that adjusts a demand for electrical power, including the electrical power demand adjustment program management apparatus: a communication unit that performs two-way communications with a plurality of client terminals that manage devices on a client side through a communication network; a program unit that creates an electric power demand adjustment program that shows the amount of demand adjustment assigned to at least a first customer terminal, selected from the plurality of customer terminals, in each predetermined time segment, based on a condition such as predetermined limitation set in advance and predetermined customer information acquired from the plurality of client terminals through the communication unit; a program execution instruction unit which, when the program unit has successfully created the electric power demand adjustment program, transmits the electric power demand adjustment program created by the program unit to the first client terminal and instructs the first client terminal to execute the electric power demand adjustment program; and a provisioning unit that, when the program unit fails to create the electric power demand adjustment program, provides information on the result of the investigation of the cause of the failure.
    With the present invention, when a demanded electric power adjustment program fails to be created, it can provide information that includes the result of investigating the cause of the program creation failure. Therefore, using the information obtained as a result of the investigation, the electric power demand adjustment program can be effectively re-created.
    Brief description of the drawings
    Figure 1 is a diagram illustrating a complete overview of an embodiment of the present invention.
    Figure 2 is a block diagram illustrating an electrical power demand management system employing a DR server.
    Figure 3 is a diagram illustrating a system configuration of the DR server and a client terminal.
    Figure 4 is a diagram illustrating tables stored in a device of
    DR server storage.Figure 5 illustrates a customer table in an initial state.Figure 6 is a diagram illustrating a sequence in which the DR server notifies the
    client terminal a DR event, and a configuration of an event table.
    5 Figure 7 is a diagram illustrating a sequence in which the client terminal notifiesto the DR server a DR response and a configuration of the DR response notification.Figure 8 is a diagram illustrating a sequence in which the client terminal notifies
    to the DR server a DR report. Figure 9 is a diagram illustrating the DR program in detail. 10 Figure 10 is a diagram that schematically illustrates the relationship between customers that
    they participate in a main program and clients that participate in a complementary program. Figure 11 illustrates a customer table obtained by registering a capacity to participate
    in the DR program.
    15 Figure 12 illustrates an example of the first report information. Figure 13 illustrates an example of second report information. Figure 14 illustrates a customer table as a result of additionally registering the
    First report information.Figure 15 illustrates a table in which types of adjustable quantity are defined.
    20 Figure 16 illustrates an example of a customer table as a result of predicting the adjustable quantity. Figure 17 illustrates another example of the customer table as a result of predicting the quantity
    adjustable. Figure 18 is a diagram illustrating an output result in a case in which the DR program has been successfully established. Figure 19 is a diagram illustrating an output result in a case in which you have not

    The DR program was established.
    Figure 20 illustrates a table in which limitation conditions are managed.
    Figure 21 illustrates a process flow diagram of DR program establishment.
    5 Figure 22 is a table in which conditions for attenuated objectives are managedaccording to a second embodiment.
    Figure 23 is a diagram illustrating an output result of the DR program.
    Figure 24 illustrates a process flow diagram of DR program establishment.
    10 Figure 25 illustrates a process flow diagram of DR program establishment according to a third embodiment.
    Figure 26 illustrates a flow chart of program setting processing
    from DR.
    Figure 27 illustrates a flow chart of newly issued processing of a request 15 to a client terminal with an increased incentive according to a fourth embodiment.
    Description of the preferred embodiment
    An embodiment of the present invention is described below with reference to the drawings. A request to reduce a demand for electric power and a request to increase a demand for electric power only differ from one another in how it
    20 changes (reduces or increases) the consumption of electrical power. Therefore, the case in which the request to reduce the demand for electric power is issued is mainly described, and the case in which the request to increase the demand for electric power is issued is omitted. It is clear that the present invention can be applied to the case in which the request to increase the demand for electric power is issued.
    In the present embodiment, an electric power demand adjustment program management system will be described, in which an electric power supplier or a DR server 1 on one side of an electric power aggregator that received a request from the Electric power provider requests a customer terminal 21 to adjust a demand for electric power.
    In the present embodiment, communications for DR are implemented between the DR server 1 and the client terminal 21 with an efficient method. For example, DR server 1 has a function of notifying a client, who can participate in the event, an event ID to identify a DR event and event date and time indicating the date and time of the event. An example of such a function includes an EiEvent function defined in OpenADR 2.Gb. For example, DR server 1 also has a function of transmitting a resource amount and a really measured value related to DR between a DR requestor and a DR executor, periodically, or when requested. An example of such a function includes an EiReport function defined in OpenADR 2.Gb. These functions defined in OpenADR 2.0b can be properly used in the present embodiment. However, the present embodiment is not limited to these functions defined in OpenADR 2.0b.
    For example, DR server 1 includes an event notification function, a DR response reception function, a report reception function, a viable amount adjustment prediction function, a DR program function and a function. of provision.
    For example, as defined in the EiEvent function, the event notification function is a function of notifying the client terminal 21 of an event (also called the DR event) of requesting adjustment of the amount of demand for electrical power. For example, the event notification function corresponds to a DR program execution instruction unit F13 illustrated in Figure 1, and an event notification unit F13 illustrated in Figure 3. The program execution instruction unit of DR illustrated in Figure 1 and the event notification unit illustrated in Figure 3 perform the same function (event notification function), and are therefore represented with the same reference number.
    For example, as defined in EiEvent, the response reception function DR is a reception function of the client terminal 21, a response indicating whether the client terminal 21 participates in the event. The DR response reception function corresponds to a DR response reception unit F14 illustrated in Figure 3.
    For example, as defined in EiReport, the report reception function is a reception function from the client terminal 21, notified values indicating a possibly adjustable amount of the client terminal 21. For example, the reported values include: a maximum adjustable amount; an acceptable minor adjustment amount indicating the acceptable minor adjustment amount; a maximum duration that indicates a maximum period during which the adjustment can be executed continuously; a minimum duration that indicates a minimum desired period during which the client as the objective of the assignment in the DR executes the adjustment; and a minimum downtime that indicates the minimum downtime required for the client as the objective of the assignment in the DR. Some of these reported values are values desired by the client terminal 21 (values desired by a client 2 with the client terminal 21). Each of the remaining notified values is either a really measured value or a value defined in the specifications. The report reception function corresponds to a report transmission and reception unit F15 illustrated in Figure 3. In Figure 1, the response response unit F14 DR and the report transmission and reception unit F15 are illustrated incorporated in a communication unit 113 for reasons of description.
    The viable amount adjustment prediction function is a prediction function of the adjustable amount of the client terminal 21 based on information that serves as the basis of the prediction. The viable adjustment amount prediction function compares the predicted adjustment amount and the value reported from the client terminal 21, and uses the smallest value as the value to be used to create the DR program. The amount of adjustment used to create the DR program is called final adjustable amount or predicted value of final adjustable amount in the present embodiment. For example, the information as the basis of the prediction includes: a history of adjustment amount; past weather information
    or forecasted; calendar information that indicates whether a day in the past or in the future is a weekday or a non-working day, and the like. The function of prediction of viable amount of adjustment corresponds to a unit F12 of prediction of viable amount of adjustment illustrated in Figures 1 and 3.
    DR server 1 stores various management tables including a client table T11, an event table T10, and the like, as illustrated in Figure 3. The client table T11 is briefly described, which is one of the tables described in detail below. For example, the customer table T11 records address information for communicating with each client terminal 21 and information indicating the ability to participate in the event, as well as the notified values, the predicted adjustable amount and the final adjustable amount predicted value which were described above.
    The DR program function is a DR program creation function based on information that serves as the basis for the creation of the program. The DR program function corresponds to a DR program unit F11 illustrated in Figures 1 and 3.
    More specifically, the DR program function creates the DR program to determine the amount of adjustment to be assigned to a client terminal 21 for each predetermined time segment, based on a predetermined predetermined limitation condition and information Default client side acquired from each client terminal 21. The DR program function can create a complementary program, supporting the DR program, when this DR program is created.
    In the present embodiment, the DR program includes a main program and a complementary program that are set separately as described below. The main program is a program that serves as the core of the DR program, and the complementary program is a program to mediate the adverse effect of the sudden withdrawal (disconnection) of the client terminal 21. The client terminal 21 participating in the main program is called the "first client terminal", and the client terminal 21 participating in the complementary program is called the "second client terminal". The term "the program is set" can also be written as "the program is created" or "the program is generated" in the description below.
    For example, the predetermined limitation condition includes a condition that must be satisfied to achieve the target adjustment amount of the DR program. For example, the limitation conditions include a satisfied condition when the sum of the predicted values of the final adjustable amount of the client terminals 21 is equal to or greater than the target adjustment amount. For example, the default client side information is the notified values acquired from the client terminal 21.
    The DR program function uses the target adjustment amount, the predicted value of the final adjustable amount, the notified values except for the maximum adjustable value, and the complementary adjustment amount, as information on which the creation of the program is based. The amount of complementary adjustment represents a ratio of the amount of objective adjustment in the complementary program to the amount of objective adjustment in the main program (the amount of complementary adjustment = the amount of objective adjustment in the complementary program I the amount of objective adjustment in the main program).
    The DR program function receives the information that serves as the basis for the creation of the program, and determines for each predetermined time segment whether each of the limiting conditions for the target adjustment amount is satisfied, the predicted value of adjustable amount final and notified values except for the maximum adjustable value. Therefore, the DR program function establishes the DR program with which the adjustment amount is determined and the client terminal 21 to which the adjustment amount is assigned for each time segment. The predetermined time segment is also called the period or block of time below in this document.
    The DR server 1 of the present embodiment further includes a function to recreate a new program when the DR program function fails to create it as described below. For example, this function can be roughly divided into a function to investigate and provide the cause of the failure, and a function to recreate the DR program automatically or semi-automatically.
    For example, the function of re-creating the DR program may include at least one of: a function of facilitating the planning of a new program by attenuating the limitation condition; and a function to facilitate the planning of a new program by introducing a virtual client terminal. The function of re-creating the DR program may also include a function of automatically negotiating with the client terminal 21 to implement the newly planned program.
    The function of investigating the cause of the failure in the creation of the DR program and providing the investigation result provides a DR program planner and similar investigation result information, which includes the cause of the failure. The investigation result information includes: information to identify a period without solution that satisfies the conditions of limitation; information to identify the limitation condition corresponding to the cause of the failure; and information to identify the client terminal corresponding to the cause of the failure. When the predetermined client side information, acquired from a client terminal, includes an inappropriate value, the investigation result information may also include information to identify the inappropriate value and alert the planner. For example, the function of providing the investigation result determines that the desired lowest acceptable amount of adjustment of the client terminal 21 that exceeds the predicted value of final adjustable amount to be achieved by the client terminal 21 is the inappropriate value. The function of providing the investigation result can detect the client terminal and the period related to the inappropriate value, and notify the planner.
    Figures 1 and 3 are related to each other in such a way that the function of investigating the cause of the phallus and providing the investigation result corresponds to a unit F117 of creation of detail illustrated in Figures 1 and 3. Unit F117 of creation of Detail works in conjunction with the report transmission and reception unit F15 and a user interface unit 115 illustrated in Figure 3 to notify a user of detailed result information described below with reference to Figure 19.
    The function of recreating the DR program automatically or semi-automatically corresponds to a limitation condition attenuation unit F116 illustrated in Figures 1 and 3.
    The F116 function of re-creating the DR program may include an F118 function of introducing the virtual client terminal to facilitate the planning of the new program. A function of automatically negotiating with the client terminal 21 to implement the newly planned program corresponds to a negotiating unit F119.
    The F117 function of investigating the cause of the failure in the creation of the DR program and providing the investigation result provides the DR program planner with the result of the investigation, which includes the cause of the failure. The investigation result information includes: information to identify a period without solution that satisfies the conditions of limitation; information to identify the limitation condition corresponding to the cause of the failure; and information to identify the client terminal corresponding to the cause of the failure. When the default customer information, acquired from a customer terminal, includes an inappropriate value, the result of the investigation may also include information to identify the inappropriate value and alert the planner. For example, the function of providing the investigation result determines that the acceptable minor adjustment amount desired by the client terminal 21, which exceeds the predicted value of the final adjustable amount to be achieved by the client terminal 21 is the inappropriate value . The function F117 of providing the investigation result can detect the client terminal and the period related to the inappropriate value, and notify the planner.
    For example, the client terminal 21 includes an event reception function, a DR response transmission function, a report transmission function and a device control function. As defined in the EiEvent function for example, the event reception function receives an event to request the adjustment of the amount of demand for electrical power, from the DR server 1. The event reception function corresponds to an event reception unit F21 illustrated in Figure 3.
    As defined in the EiEvent function for example. The DR response transmission function transmits a response, which indicates whether the client terminal participates in the event, to the DR server 1. The DR response transmission function corresponds to a DR response transmission unit F22 illustrated in Figure 3.
    As defined in the EiReport function, for example, the report transmission function transmits to the DR server 1 the reported value indicating the possibly adjustable amount and a measured value of the amount of electric power consumption. The report transmission function corresponds to a report transmission and reception unit F23 illustrated in Figure 3. The report transmission and reception unit F23 can receive information and the like transmitted from the negotiating unit F119 and the like, and present visually the information in a user interface unit 215.
    The device control function controls the operation of a control target device 22 illustrated in Figure 2. The device control function corresponds to a device control unit F24 illustrated in Figure 3.
    In the present embodiment, the DR program can be created efficiently, in a shorter period of time and with a smaller amount of work, and therefore greater ease of use can be achieved. In addition, the DR program can be established even if there is not much time between creation and execution. In addition, in the present embodiment, the DR program can achieve opportunities in the electric power transaction.
    The description in this description is given below with the following terms.
    - Period: a minimum unit time when the DR program is established, and is 30 minutes for example.
    - Connect: an action of a client terminal that participates in a DR event.
    - Disconnect: an action from the client terminal that is removed from (no longer participates in) the DR event
    - Main program: a program for assigning the adjustment amount to each client terminal to achieve the objective adjustment amount, and is a term used as a comparison with the complementary program.
    - Complementary program: a program established to prepare for a situation in which the amount of objective adjustment can no longer be achieved by the main program due to the sudden disconnection of the client terminal.
    An example of a method of creating a DR program according to the present embodiment is now described. The following stages 1 and 2 are executed in the method of setting the DR program. Thus, in the present embodiment, a program (main program) is established that determines both the amount of adjustment and the block of time (period) allocated to each client terminal to achieve the amount of objective adjustment. Through a similar procedure, a complementary program is established that achieves an objective complementary adjustment value.
    (Procedure 1) The following conditions of limitation are satisfied in each period.
    (to) The sum of adjustment amounts of the client terminals is equal to or greater than a target value.
    (b) The adjustment amount of each client terminal is equal to or greater than the least acceptable adjustment amount.
    (C) The duration of implementation in relation to each client terminal is equal to or shorter than the maximum duration.
    (d) The duration of implementation in relation to each client terminal is equal to or longer than the minimum duration.
    (and) Each customer tenninal has the minimum downtime.
    (Procedure 2) A condition with the highest priority is selected as the solution.
    For example, a higher priority is set at a lower sum and a unit price in all periods.
    The program can be created taking into account the conditions of limitation in procedure 1 that may include "the capacity to increase or decrease in ramp".
    [First realization]
    A first embodiment is described with reference to Figures 1 to 15. Figure 1 is a diagram illustrating a complete overview of the present embodiment. Figure 1 illustrates a configuration of an embodiment in enough detail to understand and implement the present invention. Therefore, the scope of the present invention is not limited to the example illustrated in Figure 1. In other words, a functional configuration described below is merely an example, and other functional configurations may be employed.
    For example, the DR server 1 includes the DR program unit F11, the feasible adjustment amount prediction unit F12, the DR program execution instruction unit F13, the DR response response unit F14 and the DR F15 unit for transmitting and receiving reports (see Figure 3), as well as user interface unit 115 and communication unit 113.
    For example, the DR program unit F11, which serves as a "program unit", includes a creation target program selection unit F111, a program plan creation unit F112, a determination unit F113, a unit F114 termination, an output unit F115, the limitation condition attenuation unit F116, the detail creation unit F117, the virtual client terminal addition unit F118 and the negotiation unit F119.
    The F111 unit of creation program selection selects one of the main program and the complementary program as the creation objective. In the present embodiment, a customer terminal (second customer terminal) that participates in the complementary program is selected first, and then a customer terminal (first customer terminal) that participates in the main program is selected, such as It is described later. However, this should not be construed in a limiting sense, and the client terminal participating in the main program can first be selected, and then the client terminal participating in the complementary program can be selected.
    The F112 program plan creation unit calculates a program plan plan of the creation target program (OR program). The F12 unit for predicting a viable amount of adjustment estimates the amount of demand adjustable for each client terminal 21. The F112 program plan creation unit calculates the program plan based on the predicted adjustable amount (final adjustable amount), the target adjustment amount, and the like.
    The determination unit F113 determines whether the program plan created by the program plan creation unit F112 satisfies all the limiting conditions. The program plan that satisfies all the limiting conditions is also called "solution" in the present embodiment.
    The termination unit F114 obtains the program plan that satisfies all the limitation conditions as the final version by calculating the amount of adjustment assigned to each client terminal 21 in each period, and determining a priority of each client based on the product of a price unit with incentive and amount of adjustment.
    The output unit F115 stores the program thus completed in a storage area, and transmits the program to the F13 instruction unit for executing the DR program. In addition, the output unit F115 provides the completed program and detailed information to be described later to the scheduler (a user operating the DR server 1) through the user interface unit 115.
    The DR program execution instruction unit F13 is described as the event notification unit F13 in the description with reference to Figure 3. The DR program execution instruction unit F13 transmits an event to order the execution of the DR program from the communication unit 113 to each client terminal 21 participating in the program, through a communication network CN 1.
    When the determination unit F11 3 determines that no program plan is found that satisfies all the conditions of limitation, that is, none of all the program plans created manages to satisfy at least one of the conditions of limitation, the planner (also called user below in this document) can be referred to the program result detail information created by the F117 detail creation unit.
    Regardless of whether the detail creation unit F117 is successful or in the creation of the program, the information indicating the details of the program can be created. The detail information of the program result in a case where the program has not been created is an example of the "research result information".
    When the program plan that satisfies all the limitation conditions cannot be created, the limitation condition attenuation unit F116 attenuates a predetermined limitation condition in all limitation conditions, and requests the program plan creation unit F112 Re-create the program plan. For example, the limitation condition attenuation unit F116 attenuates the limitation condition by decreasing the acceptable minor adjustment amount desired by the client terminal 21 or by shortening the minimum duration desired by the client terminal 21. The limitation condition attenuation unit F116 gradually attenuates the limitation condition by gradually attenuating a predetermined condition, such as the least acceptable amount of adjustment and the minimum duration, according to predetermined values. This is to create a program that can achieve an amount as close to the original goal as possible with the minimum condition attenuation.
    When the program plan that satisfies all the limiting conditions cannot be created only by attenuating the predetermined condition to the maximum level, the virtual client terminal addition unit F118 adds a virtual client terminal 21 participating in the DR program to obtain theoretically the solution. For example, the virtual client terminal is an entity introduced to obtain the solution with the limitation condition satisfied. The virtual client terminal is defined as an entity with which the limitation condition that could not be satisfied only with the client terminals 21 can be satisfied. Therefore, the plan can be created by merely defining the client terminal 21 that can serve exactly the same role as the virtual client terminal. If the virtual client terminal is not entered in the calculations, it is necessary to redo the calculations for all the client terminals 21, and therefore requires a long time.
    The negotiation unit F119 negotiates with the client terminal 21 the limitation condition attenuated by the attenuation unit F116 of the limitation condition, or the expected client terminal 21 serves the same as the virtual client terminal. More specifically, the negotiating unit F119 notifies the client terminal 21 of which permission is required and the client terminal 21 that has been requested to replace the virtual client terminal, and receives a response.
    Figure 2 is a block diagram illustrating the electrical power demand management system. The DR server 1 is connected to and can perform two-way communications with the client terminal 21, provided to the client 2, through a first communication network CN1. The number of each of the client 2 and the client terminal 21, which is one in Figure 2, is more than one in a real situation. Each client terminal 21 is connected to DR server 1.
    For example, the client 2 includes the client terminal 21, at least one target control device 22, and an electricity meter 23. Each control target device 22 is connected to and can perform two-way communications with the client terminal 21, through a second communication network CN2. The client terminal 21 is also connected to the meter 23 through the second communication network CN2.
    For example, the target control device 22 is an electric power consumption device such as a refrigerator, a freezer, an air conditioner, a lighting device, an electric motor, an elevator and a processing machine. The control target device 22 operates by consuming the electrical power supplied from an electrical network 3. The target control device may be, for example, a solar power generating device or a storage battery.
    The meter 23 measures the amount of electrical power acquired from an electrical network 3 by the client 2, and notifies the DR server 1 of the amount. Alternatively, the power consumption of the customer 2 can be acquired from a computer system of an energy distribution company.
    The first communication network CN1, used primarily for the transmission and reception of data, may be a general communication network provided by a telecommunications operator, or it may be a single dedicated communication network. The second communication network CN2, used primarily for the control of the device, may be the general communication network or the single dedicated communication network. Each of the CN1 and CN2 communication networks can be a wired or wireless network that uses any communication scheme.
    DR server 1 is connected to and can perform two-way communications with an information server 4. The DR server 1 and the information server 4 can be connected to each other through the first communication network CN1 or through another communication network not illustrated. For example, information server 4 includes: a weather information server that distributes a weather forecast and past weather data; a traffic information server that distributes information about traffic jams and the like; a server that distributes information about show events such as a concert; a news server that distributes news; and the like The DR server 1 estimates the viable amount of adjustment of each client terminal 21 using the information acquired from the information server 4.
    Figure 3 is a diagram illustrating system configurations of DR server 1 and client terminal 21. In the present embodiment, a case is described as an example in which the DR server 1 establishing the DR program communicates directly with the client terminal 21. It should be noted that a sub-regulator that collectively manages the clients 2 can be provided between the electric power provider operating the DR server 1 (or an aggregator that is requested to perform the operation by the electric power provider) and the customers 2. The present invention can be applied to a case in which the sub-regulator retransmits communications between the client terminal 21 of each client 2 and the DR server 1. The information server 4 is omitted in Figure 3.
    The DR server 1 that establishes the DR program is connected to and can perform bi-directional communications with the client terminal 21 of the client 2 through the first communication network CN1. Figure 3 illustrates only one of the plurality of client terminals 21 that are connected to the DR server 1 in normal situations as described above.
    For example, the DR server 1 includes a control unit 110, a central processing unit (CPU) 111, a memory 112, a communication port 113, a storage device 114 and a user interface unit 115. The control unit 110 includes the CPU 111 and the memory 112. The control unit 110, the storage device 114 and the user interface unit 115 are connected and can conduct bi-directional communications with each other via an internal bus. The storage device 114 and the user interface unit 115 may be connected to the communication port 113 through the control unit 110. The communication port 113 and the communication unit 113 illustrated in Figure 1 correspond to each other and are therefore represented by the same reference numbers.
    The user interface unit 115 includes an information output device that provides information to the user and an information input device that receives an instruction and information from the user. For example, the information output device includes a screen, a printer, a voice synthesizer device, an email transmission function, and the like. For example, the information input device includes a keyboard, a touch panel, a voice input device, an electronic data reader device, and the like.
    The storage device 114 stores a predetermined computer program to implement various functions and a predetermined table described below. For example, the predetermined computer program includes the DR program unit F11, the feasible adjustment amount prediction unit F12, the event notification unit F13, the DR response response unit F14 and the transmission unit F15 and report reception The default table includes the event table T10 and the customer table T11 as well as the tables T12 to T18 described below with reference to Figure 4.
    The DR program unit F11 creates the DR program based on the default limitation condition and the default client side information as described below. As described below, the viable adjustment amount prediction unit F12 estimates the adjustable amount of each customer terminal 21 and selects the most viable of the adjustable amount reported from the customer terminal 21 and the predicted adjustable amount.
    The event notification unit F13 notifies the client terminal 21 of an event to request the execution of the DR program. The response response unit F14 receives a response (response DR) indicating whether the client terminal 21 will participate or not participate in the event. The report transmitting and receiving unit F15 receives information indicating the electrical power consumption of the client 2 from the client terminal 21. The report transmitting and receiving unit F15 transmits to the client terminal 21 or visually displays in the user interface unit 115, the information (program result table and the program result detail table) indicating the detail of the Program planning result. The report transmission and reception unit F15 can transmit an email of a report indicating the result of program planning and the like to the user.
    The event table T10 stores the event information as described below with reference to Figure 6. The customer table T11 stores the customer information according to the progress of the creation of the DR program, as described below. with reference to figures 5, 11, 14, 16 and 17.
    An example of a configuration of the client terminal 21 is described. The client terminal 21 is installed to various clients 2 such as a company and a home, and controls the consumption of electrical power in the corresponding client 2.
    For example, the client terminal 21 includes a control unit 210, a CPU 211, a memory 212, a communication port 213, a storage device 214 and the user integer unit 215. For example, control unit 210 includes CPU 211 and memory 212.
    For example, the storage device 214 stores computer programs to implement each of the event reception unit F21, the DR response response unit F22, the report transmission and reception unit F23 and the device control unit F24 .
    The event reception unit F21 is a function for communicating with the event notification unit F13 of the DR server 1. The response response transmission unit F22 is a function for issuing a response, indicating whether the client terminal 21 participates in the event, to the response response receiving unit F14 of the DR server 1. The report transmission and reception unit F23 is a function for transmitting a really measured value of electric power consumption and the like to DR server 1. The report transmitting and receiving unit F23 can visually display the information received from the DR server 1 through the user interface unit 215. The device control unit F24 has a control function of an operation of the control target device 22 managed by the client terminal 21. For example, the device control unit F24 can control the start and stop of the control target device 22, and change a setting value of the control target device 22.
    Figure 4 schematically illustrates the other tables T12 to T18 stored in the storage device 114 of the DR server 1.
    For example, the DR program unit F11 contains a table T10 for the program result, a table T13 for the program result detail, a table T14 for the condition attenuation rule and a table T15 for the limitation condition. . Table T10 stores a DR program creation result. Table T13 stores a detail of the DR program creation result. Table T14 stores a rule to mitigate a limiting condition to recreate the DR program. Table T15 stores the limitation conditions that need to be met by the DR program. It is not necessary that all tables T10 to T18 be used in all embodiments. For example, table T15 for limitation condition and table T14 for condition attenuation rule are not used in the first embodiment, but are used in the second and third embodiments.
    For example, the F12 unit for predicting a viable amount of adjustment contains a table T16 of history of amount of adjustment, a table T17 of weather information and a table T18 of calendar information.
    The T16 adjustment quantity history table manages the history of the adjustment quantities, achieved by each client terminal 21, associated with date and time or a weather condition. Table T17 of meteorological information stores past, present and future acquired meteorological information. The T18 calendar information table is used to identify whether the day the DR program was run was a weekday or weekend. The F12 unit for predicting a viable amount of adjustment can use a table to manage information related to various events (events other than the DR event) such as an international concert and conference, in addition to tables T16 to T18.
    Figure 5 illustrates an initial state of the customer table T11. For example, this customer table T11 (1) manages a client terminal C110 ID and a client terminal C111 address. The following describes as an example a case in which three client terminals 21 are managed. However, this should not be construed in a limiting sense, and the OR server 1 can manage one, two, or four or more client terminals 21.
    The client terminal ID C110 is information to uniquely identify each client terminal 21 in the electrical power demand adjustment program management system. In Figure 5, the three client terminals 21 are each provided with the IDs "CSTMR1", "CSTMR2" and "CSTMR3". The client terminal address C111 is a network address used to communicate with each client terminal 21.
    Figure 6 is a sequence diagram illustrating the OR event notification processing. The DR event is sometimes abbreviated as an event in the following description. The event notification unit F13 of the DR server 1 notifies the event receiving unit F21 of the client terminal 21 the event (S11).
    After receiving the event from the OR server 1, the event reception unit F21 of the client terminal 21 notifies the event notification unit F13 of the successful reception (S12).
    The event table T10, which illustrates an example of the event information reported from the OR server 1 to the client terminal 21, is illustrated at the bottom of Figure 6.
    For example, the event table T10 manages an event ID C100, an event date C101, an event time block C102 and a detail C103 that are associated with each other.
    The C100 event ID is information to uniquely identify an event. The C101 event date is information that indicates the date of the event. The event time block C102 is information indicating a time block in which the event is executed on the date of the event. Detail C103 is information that indicates the detail of the event.
    Figure 6 illustrates an example in which the event ID C100 is "Event 1", the event date C101 is "12/31/2015" and the event time block C102 is "from 09:00 to 10:30 ". In detail C103 an address is described (uniform resource locator (URL) of a page in which a method of calculating an incentive price and the like is written.
    Figure 7 is a diagram illustrating a sequence for the DR response. When participating in the event, the DR response transmission unit F22 of the client terminal 21 notifies the DR response reception unit F14 of the DR server 1 the DR response (S21). After receiving the DR response from the client terminal 21, the DR response reception unit F14 of the DR server 1 notifies the DR response response unit F22 of the client terminal 21 of the successful reception (S22).
    An example of information T21 reported through the DR response is illustrated in the lower part of Figure 7. For example, the information T21 notified through the DR response includes a client terminal C210 ID, an event C211 ID and a C212 response.
    A value that is the same as that used for the client terminal ID in the client table T11 is used for the client terminal ID C210. A value that is the same as that used for the event ID in the event table T10 is used for the event ID C211. Response C212 stores information indicating whether the client terminal 21 participates in the event. In the example illustrated in Figure 7, "CSTMR1 " Event 1 "and" participates "are stored respectively as the client terminal ID, event ID and response.
    Fig. 8 is a diagram illustrating a sequence of the report information notification processing. In this case, a case is described in which the client terminal 21 notifies the DR server 1 of the report information. Alternatively, the DR server 1 can notify the client terminal 21 of the report information.
    The report transmitting and receiving unit F23 of the client terminal 21 notifies the report transmitting and receiving unit F15 of the DR server 1 of the report information (S31). After receiving the report information, the report transmission and reception unit F15 of the DR server 1 notifies the report transmission and reception unit F23 of the client terminal 21 of the satisfactory reception (532).
    The report transmitting and receiving unit F23 of the client terminal 21 waits for a predetermined period of time to periodically transmit the report information to the DR server 1 (833). When the predetermined period of time elapses, the report transmission and reception unit F23 returns to step 831 and repeats the processing in steps S31 to S33 described above. The report information T21 and the report information T22, transmitted from the client terminal 21 to the DR server 1, are described below with reference to Figures 12 and 13.
    An example of the DR program is described with reference to Figure 9. In the DR program, the target adjustment amount is set for each period as the predetermined time segment, that is, for each predetermined time block. The amount of objective adjustment in each period is achieved by at least one client terminal 21 (a plurality of client terminals 21 in a normal situation).
    The amount of objective adjustment in each period is illustrated in the upper part of Figure 9. The quantity of objective adjustment in a period from 9:00 is 30 Wh. The target adjustment amount in a period from 9:30 is 40 Wh. The amount of objective adjustment in a period from 10:00 is 40 Wh. The numerical values and the specific units of the amount of adjustment are merely an example for a better understanding. The scope of the present invention is not limited to any specific numerical value and unit including other examples described below.
    A graph illustrating the allocation of the target adjustment amount to the client terminals 21 in each period is illustrated in the lower part of Figure 9. Three client terminals 21 (CSTMR1, CSTMR2, and CDTMR3) participate in the DR program. The program result table T12 and the program result detail table T13, described below with reference to Figure 18, are created based on the example illustrated in Figure 9.
    The dashed bold line in Figure 9 represents the target adjustment amount of the main program. The mixed bold line in Figure 9 represents the amount of objective adjustment of the complementary program. The objective adjustment amount of the complementary program is set to be less than the objective adjustment amount of the main program as illustrated in Figure 9. Although it does not appear elaborately in the figure, the complementary program is implemented by the others. client terminals 21 that do not participate in the main program. The complementary program is created as a smaller-scale version of the main program, based on the ratio between the objective adjustment amount of the complementary program and the objective adjustment amount of the main program.
    In the period from 9:00 with the target adjustment amount of 30 Wh, the client terminal 21 (CSTMR2) is assigned 20 Wh, the client terminal 21 (CSTMR1) is assigned 10 Wh and the terminal 21 of Customer (CSTMR3) is not assigned any adjustment amount.
    In the period from 9:30 with the target adjustment amount of 40 Wh, the client terminal 21 (CSTMR1) is assigned 10 Wh, the client terminal 21 (CSTMR2) is assigned 20 Wh and the terminal 21 of Client (CSTMR3) is assigned 10 Wh.
    In the period from 10:00 with the target adjustment amount of 40 Wh, the client terminal 21 (CSTMR3) is assigned 20 Wh, the client terminal 21 (CSTMR2) is assigned 10 Wh and the terminal 21 of Client (CSTMR1) is assigned 10 Wh.
    Figure 10 is a diagram illustrating the relationship between the client terminals 21 participating in the main program and the client terminals 21 participating in the complementary program. First, a group of client terminals (# 1 to # 6) participating in the complementary program is selected from a group of client terminals managed by the DR server 1. Then, a group of client terminals (# 1 to # 18) participating in the main program is selected from the remaining groups of the client terminal group.
    As described above, the client terminals that participate in the complementary program are selected first, and then the client terminals that participate in the main program are selected. The objective adjustment amount of the supplementary program is set to be less than the objective adjustment amount of the main program (from a small amount to less than 20% for example). Therefore, the number of client terminals required in the complementary program is less than the number of client terminals required in the main program. The complementary program is created in preparation for a case in which the client terminal that is expected to participate in the main program is suddenly removed from the program (disconnection). Therefore, a reliable client terminal must participate in the complementary program. This can be achieved using different types of prioritization for the main program and for the complementary program. For example, the prioritization for the main program is set to achieve a lower overall cost, and the prioritization for the complementary program is set to include more customers with a disconnection record. Clients participating in the complementary program are distinguished from clients participating in the main program so that each client is dedicated to the participating program, whereby the DR can be executed with greater reliability.
    This can be achieved by selecting the client that participates in the main program of the clients that do not participate in the complementary program.
    Therefore, in the present embodiment, the group of client terminals participating in the complementary program of the managed client terminal group is selected first, and then the group of client terminals participating in the main program of the remaining of the managed client terminals. Therefore, a highly reliable complementary program can be prepared so that it is ready for a sudden change in the main program. As in the embodiment described below, the new creation of the main program can be facilitated by gradually reducing the number of client terminals that are expected to participate in the complementary program. The dashed line in Figure 10 illustrates how the client terminal 21 (# 2) of the complementary program is transferred to the main program.
    Figure 11 illustrates an example of a customer table T11 (2) obtained by recording the ability to participate in the event. The customer table T11 (2) is obtained by adding information C112, which indicates the ability to participate in the event identified by the event ID, to the customer table T11 (1) in the initial state illustrated in Figure 5. After receiving a T21 DR response from the client terminal 21 that wishes to participate in the event through the processing described with reference to Figure 7, the DR server 1 registers the ability of the client terminal 21 to participate in the event in the table Customer T11
    Figure 12 illustrates an example of first report information T21. The first report information T21 is transmitted from the report transmission and reception unit F23 of the client terminal 21 the report transmission and reception unit F15 of the DR server 1 through the processing described with reference to Figure 8.
    The first report information T21 contains information required for the DR server 1 to establish the DR program. For example, the first report information T21 includes the client terminal ID C210, the event ID C211, a maximum duration C212, a minimum duration C213, a minimum idle time C214, the lower acceptable C215A to C215C values of respective periods, and the maximum adjustable C216A to C21 bC values of respective periods.
    The C210 client terminal ID and the C211 event ID are the same as those described above, and therefore their description will be omitted.
    The maximum duration C212 is a value notified from each client terminal 21 and represents a maximum period of time during which the client terminal 21 can continuously execute the demand adjustment. The maximum duration is a value that depends on the capacity of the client. Time and period of time are represented by the number of periods.
    The minimum duration C213 is a value notified from each client terminal 21 and represents the shortest acceptable time for the client terminal 21 that wants to participate in the program. Therefore, the value also represents a condition of the client in which the client does not participate in the DR program if the client cannot participate in the execution of the demand adjustment for at least the minimum C213 duration. This is because the customer who executes the demand adjustment for a shorter period of time is usually given a lower incentive.
    The minimum idle time C214 is a reported value from each client terminal 21, and represents a required downtime before the demand adjustment that depends on the customer's capacity is executed. For example, when the demand is adjusted by stopping the air conditioner during the day in summer, it is necessary to reduce the temperature that has risen during that time. How long it is necessary to operate the air conditioner depends on the capacity of the air conditioner and the thermal insulation performance of the corresponding building.
    Values C215A to C215C for minor acceptable adjustment of respective periods are values notified from each customer terminal 21. Each client terminal 21 can notify different values, such as the lower acceptable setting values, for respective periods to the DR server 1. The lowest acceptable adjustment value represents the smallest amount of acceptable demand adjustment for the client terminal 21. The customer who achieves a lower amount of demand adjustment is usually given a lower incentive.
    The maximum adjustable C216A to C21bC values of respective periods are values notified from each client terminal 21. Each client terminal 21 can notify different values, such as the maximum adjustable value, for respective periods to the DR server 1. The maximum adjustable value is a value that can be achieved maximum of the amount of demand adjustment of the client terminal 21 and depends on the capacity of the client.
    Figure 13 illustrates an example of second report information T22. The second report information T22 is periodically transmitted from the client terminal 21 to the DR server 1 through the processing described with reference to Figure 8.
    For example, the second report information T22 contains a client terminal ID C220, a date C221, a block C22 of time and a quantity C223 of consumption.
    The date C221 indicates the date created from the second report information T22. The time block C22 indicates a time block during which the amount of electric power consumption has been measured. The amount C223 of consumption indicates the sum of the amounts of electrical power consumed by the control target devices 22 managed by the client terminal 21.
    Figure 13 illustrates the second report information T22 that has been transmitted from the client terminal (CSTMR1) to the DR server 1 on ~ 1/1/2015/01: 00 "and indicates that the amount of electrical power consumed in the block of time (00: 30-01: 00) is
    100Wh
    The amount obtained by subtracting the reference amount from the amount of electric power consumption (amount of electricity consumption) is a value actually measured from an amount of adjustment to be recorded in table T16 of adjustment quantity history. The reference amount is a value that serves as the basis for calculating the actual value of the demand adjustment, and is set to be "amount of electric power consumption in the last three months" for example. The T16 adjustment amount history table, which is not illustrated in the figure, is a table that stores the actual value of the adjustment amount for each customer terminal ID and for each time block.
    Each client terminal 21 may transmit the second report information T22 to the DR server 1 at any appropriate time. For example, the client terminal 21 may transmit the second report information T22 to the DR server 1 once at each predetermined time, or after being ordered to transmit information by the client.
    Figure 14 illustrates an example of a customer table T11 (3) obtained by recording the ability to participate in the event and the content of the first report information T21. The customer table T11 (3) illustrated in Figure 14 is obtained by adding content C113 to C117 of the first report information T21 to the customer table T11 (2) illustrated in Figure 11.
    More specifically, the customer table T11 (3) includes a maximum duration C113, a minimum duration C114, a minimum C115 downtime, C116A to C116C values of lower acceptable settings, and maximum adjustable C117 A to C117C values as additionally recorded items . Elements C113 to C117 are as described above. Abbreviated terms such as Dumax, Dumin, Dtmin, Awmin and Awmax may be used respectively for the maximum duration, the minimum duration, the minimum downtime, the lowest acceptable setting value and the maximum adjustable value, as appropriate to simplify the illustration. .
    Figure 15 is a table T19 illustrating an example of the adjustable amount processed by the F12 unit for predicting a viable amount of adjustment. This table T19 for defining the adjustable quantity illustrated in Figure 15 is a table used to describe the types of the adjustable quantity. It is not necessary that the unit F12 of prediction of viable quantity of adjustment actually contains the table T19 of definition of the adjustable quantity.
    Adjustable quantity types include the maximum adjustable value (Awmax), a predicted adjustable quantity (Awp) and a final predicted adjustable quantity (Awfp) as illustrated in the figure as elements C190 to C192.
    The F12 unit for predicting a viable amount of adjustment predicts the predicted adjustable amount as the viable amount of adjustment for each customer, referring to the T16 table of adjustment quantity history. the T17 weather information table and the T18 calendar information table, based on the date of the event, the time block of the event and the client terminal ID, for example.
    The F12 unit for predicting a viable amount of adjustment uses the lowest of the maximum adjustable value reported from each client terminal 21 and the predicted adjustable amount. This is because the maximum adjustable value is a value notified from the client terminal 21 and therefore is not necessarily a reliable value.
    Therefore, the unit F12 of prediction of viable amount of adjustment employs the smallest of the maximum adjustable value, which is a notified value, and the predicted adjustable amount, which is a predicted value, as the final final predictable adjustable amount of terminal 21 of client, to achieve greater accuracy of the DR program and a low risk of the DR program ending in a fault.
    Figure 16 illustrates an example of a customer table T11 (4) obtained by recording the ability to participate in the event, the content of the first report information T21, and the prediction result of the F12 unit of prediction of viable amount of adjustment. The customer table T11 (4) illustrated in Figure 16 is obtained by adding elements C118A to C118C and elements C119A to C119C to the customer table T11 (3) illustrated in Figure 14. The elements C118A to C118C each represent the quantity Adjustable predicted (Awp) in a corresponding period. Elements C119A through C119C each represent the final predicted adjustable amount (Awfp) in a corresponding period.
    As illustrated in the right part of the customer table T11 (4), the lowest acceptable adjustment value (Awmin) of the client terminal 21 (CSTMR3) in the period beginning at
    9:30 is set to "310" which is a relatively higher value than the other values. This indicates that the client terminal 21 (CSTMR3) wishes to adjust the demand by at least 310 Wh in the period from 9:30. However, at this point it is still unknown if the requested adjustment (Awmin of 310 Wh from 9:30) is acceptable.
    The final predicted adjustable amount (Awfp) of the client terminal 21 (CSTMR3) in the period from 9:00 is set to "0.01" which is less than the other values. This indicates that the lowest of the maximum adjustable value (Awmax) reported by the customer terminal 21 (CSTMR3) and the predicted adjustable amount (Awp) predicted by the F12 unit for predicting a viable amount of adjustment is "0.01".
    Figure 17 illustrates an example of a customer table T11 (5) obtained by recording the ability to participate in the event, the content of the first report information T21, and the prediction result of the F12 unit for predicting viable amount of adjustment. The customer table T11 (5) illustrated in Figure 17 is obtained by partially changing the values of elements C11 O to C119 in the customer table T11 (4) illustrated in Figure 16.
    More specifically, as illustrated in the right part of the customer table T11 (5), the lowest acceptable adjustment value (Awmin) of the client terminal 21 (CSTMR3) in the period since 9:30 has been changed from " 310 "in Figure 16 to" 10 ".
    As described in an embodiment described below, the DR server 1 can generate the DR program that satisfies all the limiting conditions by gradually attenuating the value based on a request from the client terminal at the values notified from the terminal 21 of client.
    DR server 1 requires acquiring the following information to create the DR program. For example, the information required to create the program includes: the amount of objective adjustment; the minimum duration; the maximum duration; the minimum downtime; the lowest acceptable adjustment value; the final predicted adjustable amount; and the complementary adjustment ratio. These elements, except for the target adjustment amount and the complementary adjustment ratio, must be set for each client terminal 21. More specifically, the minimum duration, maximum duration, minimum downtime, the lowest acceptable adjustment value and the final predicted adjustable amount are set for each client terminal 21. A value requested by the aggregator and the electric power supplier is used as the target adjustment amount. A value requested by the user is used as the complementary adjustment ratio. The user can set a supplemented amount under the complementary program so that it is large in a required case so that greater viability of the main program can be achieved.
    Figure 18 illustrates an example of the program result table T12 and the program result detail table T13 in a case in which the DR program was successfully created. After successfully creating the DR program (including the main program and the complementary program) that satisfies all the limiting conditions, the DR program unit F11 of the DR server 1 issues the tables T12 and T13 illustrated in Figure 18. The DR server 1 can provide tables T12 and T13 to the user through the user interface unit 115. DR server 1 may transmit part or all of tables T11 and T12 to the client terminal 21 participating in the DR program depending on the content of a contract and the like.
    For example, the T12 program result table in the case where the DR program was created successfully includes a registration C120 number, a request C121 ID and a C122 success / failure indicator.
    Registration number C120 is identification information uniquely provided to each record. The request ID C121 is a value uniquely provided to each DR program. The C 122 success / failure indicator is information that indicates whether the DR program identified by the request ID was created successfully, and is set to "1" when the program is created successfully, and is set to "O" when the creation of the DR program is not achieved as described below with reference to the figure
    19.
    The T13 program result detail table illustrates a detail of the DR program that was created successfully. For example, the T13 program result detail table includes a request ID C130, an adjustment target period C131, an adjustment amount C132 assigned to each client terminal in each period, and a main program indicator C133. The T13 program result detail table illustrated in Figure 18 has been created based on the DR program illustrated in Figure 9.
    The period C131 adjustment target indicates a time block in which the demand for electrical power is adjusted. The adjustment amount C132 of each client terminal indicates the IDs of the client terminals 21 that participate in the demand adjustment and an adjustment amount assigned to each of the client terminals 21 in each objective adjustment period. The C133 main program indicator indicates whether the program is the main program or the complementary program, and is set to ~ True "for the main program and" False "for the complementary program.
    In this case, the main program indicator C133 is all set to "True" so that the adjustment rate with the complementary program is 0%, for reasons of description. The complementary program thus omitted in this document can be created in a manner similar to that of the main program. Therefore, one skilled in the art can easily understand a method of creating the complementary program based on the description of how the main program is created, and therefore can implement the present invention.
    If the complementary adjustment ratio is set to a positive value, and therefore the customer terminal 21 is assigned the adjustment amount according to the complementary program, a record is also recorded with the main program indicator set to "Fatso" in T13 tab of program result detail.
    Figure 19 illustrates an example of the program result table T12 and the program result detail table T13 in a case where the creation of the DR program has ended in a failure. When the DR program unit F11 fails to satisfy any of the limiting conditions, the creation of the DR program (including the main program and the complementary program) ends in a failure. After failing to create the DR program, the OR program unit F11 issues the tables T12 and T13 illustrated in Figure 19. The DR server 1 can provide the tables T12 and T13 to the user through the interface unit 115 of user.
    The T12 program result table in the case where the creation of the DR program has ended in a fault also includes a failed period C123 number, a fault limiting condition C124 and a failed client C125 terminal, in addition to registration number C120, request ID C121 and the C122 success / failure indicator. Therefore, the program result table T12 in Figure 19 illustrates an overview of the cause of the failure to create the OR program.
    The C123 period number with failure is information to identify a period in which it has been determined that the creation of the DR program has ended in a failure. Failure limitation condition C124 is information to identify the limitation condition that has not been satisfied when it has been determined that the creation of the OR program has ended in a failure. The failed client terminal C125 is information to identify the client terminal 21 related to the limitation condition that has not been satisfied when it has been determined that the creation of the OR program has ended in a failure. The failed client terminal is a client terminal for which the limitation condition has not been satisfied, and can also be called the target client terminal with fault limitation.
    The example illustrated in Figure 19 indicates that the failure has occurred for the third customer with respect to the fifth limitation condition that will be described later with reference to Figure 20 in the second period.
    The value of the failed client terminal C125 indicates the order in which the information of the client terminals 21 is entered when the OR program is created. For example, when the terminal IDs CSTMR1, CSTMR2 and CSTMR3 are entered in this order, the client terminal C125 with a fault set to "3" indicates that the fault related to the terminal 21 of the one that has the third ID has occurred. of input terminal (CSTMR3).
    The failed client terminal C125 is set only when "True" is stored as a C152 client-based limitation indicator in a table T15 of the limiting condition described below with reference to Figure 20.
    In the present embodiment, the period number C123 with failure, condition C124 of fault limitation, and the client terminal C125 with failure in the program result table T12 are provided to the user through the user interface unit 115 user to facilitate the new creation of the program by the user.
    Table T1 3 of the program result detail in Figure 19 illustrates the cause of the failure to create the OR program in detail. Table T1 3 of the program result detail includes a request ID C130, an adjustment target period C131, a C132A evaluation of each client terminal and a main program indicator C133.
    The program result detail table T13 illustrated in Figure 19 is obtained by replacing the adjustment amount C132 of each client terminal in the program result detail table T1 3 illustrated in Figure 18 with the evaluation C132A of each terminal Customer
    The C132 evaluation is information to clearly notify the user of data (inappropriate data) with a negative value. When it has been determined that the creation of the DR program (REQ3) has ended in a fault as indicated by the request ID C130, the OR program unit F11 identifies the client terminal 21 that has notified the data (data inappropriate) not appropriate to create the program, with the C132A evaluation.
    Evaluation C132A is set to "-2", indicating "NG", when any one of the inappropriate conditions 1 and 2 described below is satisfied, and is set to "-1", indicating "OK", when not satisfied none of the inappropriate conditions 1 and 2.
    (Inappropriate condition 1): The lowest acceptable adjustment value exceeds the final predicted adjustable amount.
    (Inappropriate condition 2): The final predicted adjustable amount is less than a predetermined amount (for example, 1 Wh).
    The program result detail table T13 illustrated in Figure 19 illustrates an example in which the contents of the customer table T11 (4), illustrated in Figure 16, are entered into the OR server 1. The client terminal ID (CSTMR3) in Figure 16 corresponds to "310" as the lowest acceptable adjustment value (Awmin) in the period from 9:30, and "20" as the final predicted adjustable amount (Awfp) in the same period. Therefore, inappropriate condition 1 is satisfied, whereby the evaluation of the client terminal ID (CSTMR3) in the period from 9:30 is set to "-2".
    Similarly, the client terminal ID (CSTMR3) in Figure 16 corresponds to "0.01 H as the final predicted adjustable amount (Awfp) in the period from 9:00, which is less than the predetermined amount" 1 Wh ". Therefore, inappropriate condition 2 is satisfied, whereby the evaluation of the client terminal ID (CSTMR3) in the period from 9:00 is set to" -2 ".
    The evaluation of the client terminal ID (CSTMR3) in the period from 10:00 is set to the evaluation "-1" because none of the inappropriate conditions are satisfied. The evaluation of the customer IDs (CSTMR1) and (CSTMR2) is set to the evaluation "-1 H for all periods, because none of the inappropriate conditions are satisfied.
    Figure 20 illustrates an example of table T15 of limiting condition for managing the limiting condition. For example, the T15 limitation condition table includes a C150 condition number, a detail C151 and the limitation indicator for each client C152.
    The C150 condition number is information to uniquely identify the condition
    of limitation Detail C151 indicates the detail of the limitation condition. The limitation indicator for each client C152 is an indicator indicating whether the limitation condition is set for each client terminal 21 (True), or only a limitation condition is set for all client terminals 21 (False).
    The present invention uses the following five limiting conditions by way of example.
    (Limitation condition 1) The sum of the upper limit values of the amount of adjustment of the client terminals is equal to or greater than a target value.
    (Limitation condition 2) The duration of each client terminal is equal to or shorter than the maximum duration.
    (Limitation condition 3) The duration of each client terminal is equal to or longer than the minimum duration.
    (Limitation condition 4) The minimum downtime of each client terminal
    It can be guaranteed.
    (Limitation condition 5) An adjustment amount that is equal to or greater than the lowest acceptable adjustment value is assigned to each customer terminal.
    Figure 21 is a flow chart illustrating the creation processing of the DR program. In this case, the processing, which is mainly executed by the DR program unit F11, is described with the DR server 1 as the object of the operations.
    First, DR server 1 executes repeated processing for each period (S101). DR server 1 generates a state transition that satisfies the limiting conditions (S102).
    More specifically, the DR server 1 extracts all combinations between the client terminals 21 that execute and do not execute the demand adjustment, and generates the combination that satisfies all the limiting conditions illustrated in Figure 20 (S102). In Figure 21, such a combination is called state transition.
    DR server 1 determines if all combinations (state transition) that satisfy the limiting conditions include the solution (S103). When the solution exists (S103: Yes), the DR server 1 assigns adjustment amounts to the intended client terminals participating in the DR program (S1 04).
    DR server 1 assigns the adjustment amounts in such a way that to each of theExpected customer terminals participating in the DR program are assigned theminor adjustment amount acceptable or more, and such that the adjustment amountobjective is achieved by adding the adjustment amounts assigned to the terminals5 client planned to participate in the DR program. DR server 1 can setpriorities to client terminals 21 and assign adjustment amounts while havingConsider the priorities. For example, adjustment amounts can be assigned in thereliability order calculated for each client terminal based on a record ofParticipation in the DR program. Alternatively, the adjustment amounts may
    10 be assigned in the order of reliability given the highest priority set in the client terminal 21 that has accepted an adverse condition in a DR program that has been performed before, to compensate for the loss in that time.
    DR server 1 stores the result of assigning the adjustment amount in step 8104 as an internal variable that can be a value for each period, and performs an update 15 with the values corresponding to the period number currently processed. In the initial processing, the values are not updated, but are generated again.
    When the repeated processing for each period is terminated (8106), the DR server 1 prioritizes the state transitions, and determines the state transition with the highest priority as the final solution (8107). For example, DR server 1 prioritizes the
    20 state transitions in such a way that a state transition corresponding to a product less than the amount of adjustment assigned and a unit price of electric power acquisition has a higher priority, and selects the one with the highest priority as a solution.
    DR server 1 determines whether both the main program and the program
    25 complementary have been created (8108). When both the main program and the complementary program have been created (8108: 8í), the processing is terminated. When any one of the main program and the complementary program has not been created (8108: NO), the DR server 1 changes the program to be created (8109), and returns to step 8101. When the complementary program has been created first, the program that
    30 to be created is changed to the main program, and when the main program has been created first, the program to be created is changed to the complementary program.
    The complementary program is created using the objective adjustment amount of the complementary program calculated from the objective adjustment amount of the main program and
    the complementary adjustment ratio.
    After determining that there is no solution in step 8103 (8103: NO), the DR server 1 identifies the number of the period in which no solution was found (8110). In addition, DR server 1 identifies the limitation condition information including the condition
    5 of limitation and the client terminal that has been determined to have no solution (8111). More specifically, information is identified that includes the fault limitation condition and the client terminal with failure. As described above, only when the limiting condition is set at each client terminal, is the customer terminal identified for which the limiting condition cannot be satisfied.
    10 DR server 1 investigates whether there is insufficient data inappropriate for the creation of the DR program based on the information identified in step 8111 (8112). The DR server 1 provides the investigation result obtained in step 8112 to the user in the form of the investigation result table T12 and the investigation result detail table T13 described with reference to Figure 19. The result of investigating
    The cause of the failure can be provided to the user in a different way from the form of the tables illustrated in Figure 19.
    In the present embodiment, when the creation of the DR program ends in a failure, the DR server 1 investigates the cause of the failure, and provides the investigation result to the user in the form of tables T12 and T13. Therefore, the user can recreate a
    20 new DR program while recognizing the cause of the failure by referring to tables T12 and T13. As a result, the DR program can be created in a shorter period of time, whereby greater operating efficiency can be achieved.
    In the present embodiment, when the creation of the DR program ends in a failure, the DR server 1 investigates whether there is inadequate data to create the program.
    DR 25 in the first place, and provides the verification result to the user. Therefore, the user can quickly recognize the specific cause of the failure.
    In the present embodiment, the lower of the maximum adjustable value, reported from the client terminal 21, and the predicted adjustable amount, predicted by the F12 prediction unit of viable amount of adjustment based on the previous record and the like are employed. By
    Therefore, a realistic DR program can be created that is likely to be viable, whereby DR server 1 can be achieved with greater reliability.

    (Second embodiment)
    A second embodiment is described with reference to Figures 22 to 24. The embodiments described below including the present embodiment are modifications of the first embodiment, and are therefore described by focusing on the difference with respect to the first embodiment. In the present embodiment, when the creation of the DR program ends in a failure, an attempt is made to re-create a DR program by gradually attenuating a predetermined limitation condition set in advance.
    As described above, to create the DR program, the DR server 1 requires acquiring the minimum duration, the maximum duration, the minimum downtime, the lowest acceptable adjustment value, the final predicted adjustable amount, the ratio of complementary adjustment, and the like in addition to the amount of objective adjustment.
    The minimum duration, the lowest acceptable adjustment value and the complementary adjustment ratio in these information elements are fixed values according to a request from the client or the user (requested value). The maximum duration, the minimum downtime and the final predicted adjustable amount are values that depend on the capacity on the client side (capacity value). Generally, the performance value is more difficult to change than the request value, and therefore the request value is easier to change than the capacity value.
    Figure 22 illustrates an example of a condition attenuation rule table T14 used to re-create the DR program. The new creation of the DR program can be referred to below in this document as new planning.
    For example, the condition attenuation rule table T14 includes a condition C140 number, an attenuation condition name C141, an attenuation order C142 and an attenuation value C143.
    The C140 condition number is information to identify the attenuated condition. The name C141 of the attenuation condition is information indicating the content of the attenuated condition. The order C142 of attenuation is information that defines the order of the conditions to be attenuated when there is a plurality of attenuated conditions. The C143 attenuation value is an amount in which the attenuated condition is attenuated each time.
    The condition attenuation rule table T14 can be set by a DR server 1 provider or by the DR server 1 user when the DR server 1 is sent or installed. For example, the user records the condition related to the request value in the T14 condition attenuation rule table. This is because the condition related to the requested value can be eased more easily than the condition related to the capacity value, and is therefore suitable for the processing of new planning. The user can set the attenuated order and the attenuation value to desired values.
    In an example illustrated in Figure 22, the predetermined conditions that can be attenuated include the lowest acceptable adjustment value, the minimum duration and the complementary adjustment ratio to which the highest, second major and minor priorities are respectively provided. Priorities are set in this way because the lowest acceptable adjustment value and the minimum duration are values that do not depend on the capacity of the client side and is a value requested by the client that can be easily changed by permission from the client (permission by the client terminal 21).
    The complementary adjustment ratio is also a user request value that can be easily changed. On the other hand, the complementary adjustment ratio defines a capacity of the complementary program to support the main program, and therefore the lower order is provided to maintain the high reliability of the DR program. Alternatively, the user can individually determine and set the conditions to be attenuated and the order of the attenuated conditions. As described above, the user can freely set the condition attenuation rule table T14, and therefore can enjoy greater ease of use.
    Figure 23 illustrates an example of the T12A program result table. The program result table T12A of this embodiment includes the registration number C120, the request ID C121, the exithalalium indicator C122, the period period C123 with failure, the condition C124 limiting with failure and the client terminal C125 with failure as in the case of the program result table T12 illustrated in Figure 19, and also includes an attenuated condition indicator C126.
    The C126 attenuated condition indicator is information that indicates a truly attenuated condition of the predetermined conditions (the lowest acceptable adjustment value, the minimum duration and the complementary adjustment ratio), and is set to "r for the really attenuated condition, and is set to "O" for the condition that has not been attenuated.
    The C126 attenuated condition indicator, which may be in any appropriate form, is illustrated in the form of a matrix in this embodiment. In the matrix, the client terminals are arranged in the direction of the rows, and the predetermined conditions to be attenuated are arranged in the direction of the columns.
    Figure 23 illustrates a table with the registration of the request ID "RE02" corresponding to that of the customer table T11 (5) illustrated in Figure 17, the target adjustment amount corresponding to an example illustrated with reference to Figure 9 , and the registration of the request ID "RE03" corresponding to that of the customer table T11 (4) illustrated in Figure 16. The creation of the DR program based on the customer table T11 (4) illustrated in Figure 16 it fails because "310" as the lowest acceptable setting value (Awmin) corresponding to the client terminal ID (CSTMR3) in the period from 9:30 is too large.
    Therefore, the DR server 1 reduces the "lowest acceptable setting value" with the highest order attenuated by "300 Wh" according to the T14 condition attenuation table illustrated in Figure 22. Therefore, the setting value Acceptable minor (Awmin) is reduced from "310" to "10". As a result, the DR server 1 can obtain the client table T11 (5) illustrated in Figure 17 by attenuating a condition, and thus can successfully create the DR program
    The "RE04" record corresponds to an example in which the amount of objective adjustment in the period from 9:00 is greater than the amount of objective adjustment illustrated in Figure 9 in 10 Wh, in the case of the table Customer T11 (4) illustrated in Figure 16. More specifically, the amount of target adjustment in the period from 9:00, which is set to "30 Wh" in Figure 9, is set to "40 Wh" in the example illustrated in figure 23. As illustrated on the lower side of table T11 (4) in figure 16, the final predictable adjustable quantities (Awfp) in the period from 9:00 on the client terminal (CSTMR1 ), the client terminal (CSTMR2) and the client terminal (CSTMR3) are "10 Wh". "20 Wh" and "0.01 Wh", respectively. Therefore, the sum of the adjustable quantities of all the client terminals (CSTMR1 to 3) that participate in the DR program in the period from 9:00 is "30.01 Wh" and therefore the target adjustment amount of "40 Wh".
    Therefore, the DR program corresponding to "RE04" cannot achieve the target adjustment amount, even when all the attenuated conditions illustrated in Figure 22 are attenuated as much as possible. and therefore it is determined as a failure. All the values in the matrix of the attenuated condition indicator for the DR program of the "REQ4" are set to 1 indicating that the new planning has been done attenuating all the attenuated conditions as much as possible. In this case, for reasons of a simpler explanation, the complementary adjustment ratio in the present embodiment is set at 0%.
    Fig. 24 is a flow chart illustrating the program creation processing according to the present embodiment. The processing includes all steps 8101 to 5112 described in Figure 21. In addition, in the processing, after determining that the results obtained in step 5102 do not include the solution (5103: NO), the OR server 1 determines whether the condition of limitation can be attenuated (8120). As described above, the OR server 1 attenuates at least one of the conditions that can be attenuated set in advance to attenuate the limiting condition corresponding to the attenuated condition.
    After determining that the limitation condition can be attenuated (5120: yes), the OR server 1 attenuates the predetermined condition to attenuate the limitation condition (8121), and then returns to step 5101. On the other hand, for example, after determining that the limitation condition can no longer be mitigated because all the conditions that can be attenuated have been attenuated as much as possible (5120: NO), the OR server 1 creates the detailed T13 table program result in steps S110 to S112, and provides the table to the user.
    The present embodiment with the configuration described above can provide the same advantageous effects as the first embodiment. Furthermore, in the present embodiment, the attempt may be made to re-create the OR program by attenuating the limitation condition, gradually attenuating the predetermined condition to mitigate the limitation condition. Therefore, the user can implement the automatic or semi-automatic creation of a new program, whereby the OR program can be created in a shorter period of time compared to the case of the first embodiment, whereby a greater efficiency.
    [Third embodiment]
    5e describes a third embodiment with reference to Figures 25 and 26. In the present embodiment, by eliminating a state in which there is no solution when the OR program is re-created, the creation process of the OR program can be stopped .
    Figure 25 illustrates an example of a program result table T128 and a program result detail table T138 of the present embodiment. The program result table T128 illustrated in Figure 25 includes the registration number C120, the request ID C121 and the success / failure indicator C122 as in the case of the program result table T12 illustrated in Figure 18, and also includes an attenuated condition indicator C126 and a client terminal addition indicator C127. The C127 client terminal add indicator indicates whether (Virtual) is added (True) or not added (False) when the DR program is created.
    The T138 program result detail table of this embodiment is obtained by adding an element for a virtual client terminal (VIRTUAL) to the adjustment amount C132 for each client terminal in the T13 program result detail table illustrated in the figure 18.
    The DR program corresponding to "REQS" represents an example in which the amount of objective adjustment in the period from 9:00 is greater than the amount of objective adjustment illustrated in Figure 9 in "10 Wh", in the case from the customer table T11 (4) illustrated in Figure 16. In this example it is assumed that in the period from 9:00, the client terminal (CSTMR3) is in idle time and therefore the assignment is implemented No amount of adjustment.
    As described above, the amount of objective adjustment in the period from
    9:00 is "40 Wh". The adjustable amount of the client terminat (CSTMR1) that is expected to participate in the DR program is "10 Wh", and the adjustable amount of another client terminal (CSTMR2) is "20 Wh". The third client terminal (CSTMR3) with the adjustable amount of "0.01 Wh" is not assigned any adjustment amount in the period from 9:00.
    Therefore, the adjustment amount of "10 Wh" does not require an additional allocation in the period from 9:00. In this case, the DR program can only be successfully created by entering a virtual client terminal, defined as a client terminal that can eliminate the cause of the program creation failure, in the DR program.
    Even so, a truly executable DR program cannot be created with the virtual client terminal that is nothing more than a virtual entity. Therefore, the user searches for a real client terminal that can replace the virtual client terminal. More specifically, it is only necessary to find a single real client terminal that participates in the DR program instead of the virtual client terminal. Therefore, a new planning can be performed in a shorter period of time compared to a case in which the new planning involves all managed client terminals 21.
    Fig. 26 is a flow chart illustrating the program creation processing of this embodiment. This processing includes steps S101 to S108 and steps S120 and 8121 in the processing described with reference to Figure 24, but does not include steps 8110 to 8112 in Figure 24 because theoretically the creation of the DR program never fails in processing. .
    The processing further includes steps 8130, 8131 and 8132. After determining that the limitation condition cannot be attenuated (S120: NO), the DR server 1 determines whether the virtual client terminal has been added to the DR program (8130) .
    When the virtual client terminal has not been added to the DR program (8130: NO), the DR server 1 adds a virtual (VIRTUAL) client terminal to the DR program as illustrated in Figure 25 (8131).
    Then, the DR server 1 sets data required for the virtual client terminal (8132), and returns to step 8101. The data required for the virtual client terminal is data to solve the cause of the program creation failure. For example, when there is a period in which the final predicted adjustable amount is insufficient, the deficiency is supplemented by the virtual client terminal.
    Then, the user finds a client terminal 21 that can replace the virtual client terminal of the group of client terminals managed by the DR server 1. For example, the user can find the client terminal that can replace the virtual client terminal by offering a high special incentive.
    The present embodiment with the configuration described above may provide the same advantageous effect as the first and second embodiments. Furthermore, in the present embodiment, the virtual client terminal that can theoretically establish the DR program is introduced after attenuated attenuated conditions as much as possible (8120: NO) when it is determined that there is no solution (8 103: NO). Therefore, the DR program can be created in a shorter period of time than the new creation of the DR program that involves all client terminals because the user only needs to find a single client terminal that can replace the virtual client terminal .
    The virtual client terminal number is not limited to one. For example, when there is a plurality of periods lacking in the amount of adjustment, the virtual client terminal can be entered in each of the periods or a single virtual client terminal that can theoretically replace the lack in the amount of adjustment in the plurality of periods.
    [Fourth realization]
    8e describes a fourth embodiment with reference to Figure 27. In the present embodiment, a permission request is automatically transmitted to the client terminal so that the condition is attenuated in the second embodiment and the client terminal that can replace the client terminal virtual in the third embodiment, and an answer is obtained. The request can be issued with communications based on OpenAOR. The client terminal for which the condition is attenuated and the client terminal that can replace the virtual client terminal are referred to below in this document requesting client terminal.
    An example is described in which the limitation condition is attenuated. A request notification T31 is transmitted from the event notification unit F13 of the OR server 1 to the request target client terminal 21 (8141). The client terminal 21 that has received the request responds to the request (8142).
    After receiving the response from the request target client terminal 21, the DR server 1 compares the content of the response with the content of the request (S143). When the content of the response matches the content of the request, that is, when the request target client terminal 21 has accepted the request from the OR server 1 as is, the OR program is used with the limitation condition attenuated (S144). On the other hand, when the OR server 1 receives a response that saturates the content of the request from the request target client terminal 21, the OR server 1 again modifies the OR program based on the content of the response ( 8144).
    When no response is received from the request target client terminal 21 within a predetermined period of time, or when the content of the response cannot satisfy the content of the request (when the request is denied), the notification of The request can be transmitted to another client terminal, or it can be collectively transmitted to a plurality of the client terminals 21 and the client terminal that has accepted the request in the first place can be selected.
    For example, the request notification T31 includes an event ID C310, an event date C311, an event time block C312, a request content C313 and a C314 incentive.
    The C313 request content indicates the requested content. For example, the request content clearly indicates a desired changed value for an item such as the lowest acceptable adjustment value that has been notified in advance. More specifically, it may be requested that the value that has been reported as 400 Wh in advance be decreased to 100 Wh. In the example illustrated in Figure 23 described above, the CSTMR3 customer corresponding to REQ3 is requested to decrease the lower acceptable setting value by 300 Wh. The C314 incentive indicates an incentive obtained after accepting the request.
    A method that is similar to that described with reference to Figure 27 can be applied to a case in which the request is issued to the client terminal that can replace the virtual client terminal as described in the third embodiment.
    The present embodiment may provide the advantageous effects that are the same as those provided by the first to third embodiments. Furthermore, in the present embodiment, the DR server 1 automatically issues a request to the client terminal for which the limitation condition is attenuated or to the client terminal replacing the virtual client terminal to obtain the response. Therefore, the DR program can be created in a shorter period of time and through a less cumbersome procedure, and therefore a greater ease of use can be achieved.
    The transmission and reception that take place between the event notification unit and the event reception unit in the attached figure 27 can take place between two transmit and receive report units. The present invention is not limited to the embodiments described above. One skilled in the art can make various additions, modifications, and the like without departing from the scope of the present invention. The exemplary configuration described in the embodiments with reference to the attached figures should not be construed in a limiting sense. The configurations and processing methods in the embodiments can be modified appropriately without departing from the object of the present invention.
    Each component in the report transmission and reception unit may be selected and omitted as appropriate and the present invention includes the invention with a configuration as a result of selection and omission. The configurations described in the scope of claims can be combined in a manner that is not clearly described in the scope of claims.
    权利要求:
    Claims (16)
    [1]
    1. Electric power demand adjustment system comprising:
    a plurality of customer terminals that measure the consumption of electrical power;
    an electrical power demand adjustment program management apparatus that manages a program with which an electrical power demand is adjusted, characterized in that the apparatus comprises:
    a communication unit that performs bidirectional communications with a plurality of client terminals that measure the consumption of electrical power and manage devices connected to the electrical network on a client side through a communication network;
    a program unit that creates an electric power demand adjustment program that shows the amount of demand adjustment assigned to at least a first customer terminal, selected from the plurality of customer terminals, in
    each predetermined time segment, based on a predetermined limitation condition set in advance and predetermined customer information acquired from the plurality of client terminals through the communication unit;
    a program execution instruction unit which, when the program unit has successfully created the electric power demand adjustment program, transmits the electric power demand adjustment program created by the program unit to the first client terminal and instructs the first customer terminal to execute the electric power demand adjustment program, where the electric power demand adjustment comprises instructions for changing the electric power demand of a customer device connected to the power grid; Y
    a provisioning unit that, when the program unit fails to create the electric power demand adjustment program, provides investigation result information that includes a result of investigating the cause of the fault.
    [2]
    2. Electric power demand adjustment system according to claim 1, wherein, after successfully creating a plurality of electric power demand adjustment programs, the program unit selects the best program
    of demand adjustment of electrical power from the plurality of programs of adjustment of demand for electrical power, based on a priority set according to an index prepared in advance.
    [3]
    3. Electric power demand adjustment system according to claim 2, wherein the program unit creates a complementary program that mitigates a change that occurs when at least a first customer terminal of the first customer terminals is removed from the program electric power demand adjustment, based on a priority that is different from the priority for the electric power demand adjustment program.
    [4]
    Four. Electric power demand adjustment system according to claim 3, wherein
    the program unit includes a limitation condition attenuation unit that attenuates at least one predetermined condition related to the predetermined limitation condition, and
    After determining that the electrical power demand adjustment program cannot be created by the program unit, the limitation condition attenuation unit attenuates the predetermined condition and requests the program unit to re-create the demand adjustment program of electrical power
    [5]
    5. Electric power demand adjustment system according to claim 3, wherein
    The program unit also includes a prediction unit of viable amount of adjustment that predicts the amount of viable demand adjustment of the client terminal,
    the unit of prediction of viable amount of adjustment predicts a quantity of viable demand adjustment of the client terminal, based on a reported value indicating the amount of viable demand adjustment of the client terminal notified by the client terminal, a history of the amount of demand adjustment, weather information and calendar information that are in the default customer side information.
    [6]
    6. Electric power demand adjustment system according to claim 3, wherein the provisioning unit adds information, which identifies a segment of
    time related to the cause of the failure to create the electric power demand adjustment program by the program unit, to the investigation result information.
    [7]
    7. Electric power demand adjustment system according to claim 6, wherein the provisioning unit adds predetermined information related to the cause of the failure in the creation of the electric power demand adjustment program by the program unit, of the information included in the default client side information, to the investigation result information.
    [8]
    8. Electric power demand adjustment system according to claim 4, wherein
    the predetermined condition includes a condition of reducing the number of second client terminals, the second client terminals being those that participate in the complementary program in the plurality of client terminals, and
    The limitation condition attenuation unit reduces the number of the second client terminals according to predetermined attenuation values.
    [9]
    9. Electric power demand adjustment system according to claim 8, wherein first the first customer terminals of the plurality of customer terminals are selected, and then the second customer terminals of the remaining ones of the plurality of customer terminals
    [10]
    10. Electric power demand adjustment system according to claim 4, wherein
    The program unit further includes a virtual client terminal addition unit that adds a first virtual client terminal to satisfy the predetermined limitation condition, and
    When the limitation condition attenuation unit can no longer attenuate the default condition, the virtual client terminal addition unit adds the first virtual client terminal to the first client terminals and requests the program unit to recreate the electric power demand adjustment program.
    [11]
    11. Electric power demand adjustment system according to claim 10,
    in which the provisioning unit also adds information that identifies a customer terminal related to the cause of the failure in the creation of the electric power demand adjustment program by the program unit and information on limiting conditions, to the information of research result.
    [12]
    12. Electric power demand adjustment system according to claim 4, wherein the limitation condition attenuation unit sets a priority and an attenuation value to each of the predetermined conditions in advance, and gradually attenuates the predetermined conditions by implementing attenuation gradual only on attenuation values according to priority.
    [13]
    13. Electric power demand adjustment system according to claim 4, wherein the limitation condition attenuation unit automatically transmits to a customer terminal related to the attenuation of the predetermined condition in the plurality of customer terminals, information related to attenuation of the default condition and automatically acquires a response from the client terminal.
    [14]
    14. Electric power demand adjustment system according to claim 10, wherein the virtual client terminal addition unit requests a client terminal that can replace the first virtual client participating in the electric power demand adjustment program offering a participation condition, and receives a response from the client terminal that has been requested to participate in the electric power demand adjustment program.
    [15]
    fifteen. Method implemented by a system according to any one of claims 1 to 14, characterized in that
    The method comprises:
    acquire predetermined customer information from each of a plurality of customer terminals that measure the consumption of electrical power and;
    create an electrical power demand adjustment program indicating the amount of demand adjustment assigned to at least a first customer terminal, selected from the plurality of customer terminals, in each predetermined time segment based on a predetermined limitation condition set in advance and the default client side information;
    transmit, when the electric power demand adjustment program has been successfully created, the electric power demand adjustment program to the first customer terminal and order the first customer terminal to execute the electric power demand adjustment program, where demand adjustment
    5 electric power comprises instructions to change the power demandelectrical of a client device; Y
    provide, when the demand adjustment program has not been created
    of electrical power, research result information that includes a
    result of investigating the cause of the failure.
    Method according to claim 15, wherein the creation of the electric power demand adjustment program also creates a complementary program that mitigates a change that occurs when at least one of the first customer terminals is removed from the electric power demand adjustment program.
    [17]
    17. Method according to claim 15, wherein the creation of the adjustment program
    Power demand 15 includes attenuating at least one predetermined condition related to the predetermined limitation condition, and
    in the attenuation of the predetermined condition, the limiting condition
    default is attenuated by attenuating the default condition and is requested to
    Electric power demand adjustment program that is recreated.
    类似技术:
    公开号 | 公开日 | 专利标题
    ES2609516A2|2017-04-20|Electrical power demand adjustment program management apparatus and electric power demand adjustment adjustment management method |
    US9497139B2|2016-11-15|Client-allocatable bandwidth pools
    US8667499B2|2014-03-04|Managing allocation of computing capacity
    US9154589B1|2015-10-06|Bandwidth-optimized cloud resource placement service
    US9953351B1|2018-04-24|Managing resource requests that exceed reserved resource capacity
    EP2923479B1|2017-06-28|Method and apparatus for controlling utilization in a horizontally scaled software application
    CN105159775A|2015-12-16|Load balancer based management system and management method for cloud computing data center
    CN103210382B|2016-02-24|Bus transaction based on bus unit health and fitness information and related power management in mediates communications bus
    US20140269256A1|2014-09-18|Network capacity planning
    US11175943B2|2021-11-16|Tenant-controlled cloud updates
    Wang et al.2014|Optimal online multi-instance acquisition in IaaS clouds
    CN107291546B|2020-07-14|Resource scheduling method and device
    US20140101316A1|2014-04-10|Apparatus and method for provisioning
    WO2017075967A1|2017-05-11|Bandwidth allocation method and system for on-line media service
    WO2016173280A1|2016-11-03|Monitoring management method and apparatus
    CN105263163B|2019-01-15|A kind of sending method of notification message, device and system
    JP5945810B2|2016-07-05|Energy management system
    US9665109B2|2017-05-30|Soliciting user input for thermostat control
    US20190068405A1|2019-02-28|Allocating internal vlan ids to user-configured vlans
    CN109284275A|2019-01-29|A kind of cloud platform virtual machine file system monitoring method and apparatus
    JP2014230187A|2014-12-08|Traffic regulation system, traffic regulation control apparatus, preferential control method and program therefor
    JP6094931B2|2017-03-15|Energy management method and energy management program
    TW202121274A|2021-06-01|Cloud resource management method and apparatus, and electronic device and computer readable storage medium
    WO2016206472A1|2016-12-29|Mac traffic scheduling method and apparatus, base station, and computer-readable storage medium
    WO2015117309A1|2015-08-13|Method and apparatus for generating warning
    同族专利:
    公开号 | 公开日
    US10642236B2|2020-05-05|
    JP6653153B2|2020-02-26|
    GB2542868A|2017-04-05|
    US20170097622A1|2017-04-06|
    GB2542868B|2020-04-01|
    ES2609516R1|2017-06-07|
    ES2609516B1|2018-02-09|
    JP2017070131A|2017-04-06|
    GB201604669D0|2016-05-04|
    引用文献:
    公开号 | 申请日 | 公开日 | 申请人 | 专利标题
    US4324987A|1978-05-26|1982-04-13|Cyborex Laboratories, Inc.|System and method for optimizing shed/restore operations for electrical loads|
    JP3671680B2|1998-07-13|2005-07-13|株式会社日立製作所|Power system with load control device adapted to the situation of power equipment|
    US6671586B2|2001-08-15|2003-12-30|Statsignal Systems, Inc.|System and method for controlling power demand over an integrated wireless network|
    US8676953B2|2009-07-17|2014-03-18|Honeywell International Inc.|Use of aggregated groups for managing demand response resources|
    US8782190B2|2009-07-17|2014-07-15|Honeywell International, Inc.|Demand response management system|
    US8738190B2|2010-01-08|2014-05-27|Rockwell Automation Technologies, Inc.|Industrial control energy object|
    US20110258018A1|2010-04-19|2011-10-20|General Electric Company|System and method for scheduling demand response events in a network|
    US8676394B2|2010-06-30|2014-03-18|Siemens Aktiengesellschaft|Integrated demand response for energy utilization|
    KR101732628B1|2010-11-05|2017-05-04|엘지전자 주식회사|Power management apparatus for controlling consumption power and method of operating the same|
    KR101731361B1|2010-11-05|2017-05-11|엘지전자 주식회사|Electronic device for controlling consumption power and method of operating the same|
    US8825215B2|2010-11-17|2014-09-02|General Electric Company|Power consumption compliance monitoring system and method|
    US9310786B2|2011-06-17|2016-04-12|Siemens Industry, Inc.|Automated demand response scheduling to reduce electrical loads|
    JP5779014B2|2011-06-27|2015-09-16|株式会社東芝|Power supply / demand control device, power management device, and power supply / demand control method|
    US9153964B2|2011-09-09|2015-10-06|General Electric Company|Systems and methods to aggregate loads for demand response events|
    JP5603318B2|2011-12-22|2014-10-08|株式会社日立製作所|Power demand adjustment system, apparatus, and method|
    US9257840B2|2012-02-22|2016-02-09|General Electric Company|Synchronized PWM randomization for coordinated load management|
    GB2505929A|2012-09-14|2014-03-19|Pod Point Holiding Ltd|Method and system for predictive load shedding on a power grid|
    US20140095410A1|2012-09-28|2014-04-03|General Electric Company|Method and system for demand response management|
    WO2014089466A1|2012-12-07|2014-06-12|Battelle Memorial Institute|Using demand side resources to provide frequency regulation|
    US20140324240A1|2012-12-14|2014-10-30|Alcatel-Lucent Usa Inc.|Method And System For Disaggregating Thermostatically Controlled Appliance Energy Usage From Other Energy Usage|
    EP2963610A4|2013-02-27|2016-11-09|Hitachi Ltd|Power creation control system and method|
    WO2014167741A1|2013-04-11|2014-10-16|株式会社日立システムズ|Broad area management system, broad area management apparatus, building management apparatus, and broad area management method|
    EP2984609A4|2013-04-12|2016-05-04|Neurio Technology Inc|System and method for performing demand response optimizations|
    US9691076B2|2013-07-11|2017-06-27|Honeywell International Inc.|Demand response system having a participation predictor|
    US20150019037A1|2013-07-11|2015-01-15|Honeywell International Inc.|System having customer defined demand response signals|
    JP5858080B2|2013-08-23|2016-02-10|横河電機株式会社|Operation planning method and operation planning system|
    JP6234264B2|2014-02-14|2017-11-22|株式会社日立製作所|Electric power demand adjustment system, electric power demand adjustment method, and electric power demand adjustment device|
    US20180059701A1|2016-09-01|2018-03-01|Honeywell International Inc.|Providing demand response|
    US10554046B2|2017-12-18|2020-02-04|International Business Machines Corporation|Virtualization of large-scale energy storage|CN107748946A|2017-09-06|2018-03-02|国家电网公司|Electric power optical transmission device state-detection evaluation system|
    KR101986020B1|2017-10-12|2019-06-04|전자부품연구원|System and Method for Processing DR|
    JP6823581B2|2017-12-19|2021-02-03|大阪瓦斯株式会社|Demand response system|
    WO2020101056A1|2018-11-14|2020-05-22|전자부품연구원|Demand response processing system and method|
    WO2021187673A1|2020-03-16|2021-09-23|주식회사 아이온커뮤니케이션즈|Apparatus for managing power supply and demand, and method therefor|
    法律状态:
    2018-02-09| FG2A| Definitive protection|Ref document number: 2609516 Country of ref document: ES Kind code of ref document: B1 Effective date: 20180209 |
    优先权:
    申请号 | 申请日 | 专利标题
    JP2015195532A|JP6653153B2|2015-10-01|2015-10-01|Power demand adjustment plan management device|
    JP2015-195532|2015-10-01|
    [返回顶部]