Power supply and demand management system, power supply and demand management method, and autonomous distributed recovery device

Abstract

To achieve appropriate power supply and demand management.SOLUTION: Each base management device includes an autonomous distributed recovery unit 800. The autonomous distributed recovery unit 800 includes: a network reconfiguration unit 820 that reconfigures a base group including a plurality of base systems capable of communicating with each other as elements when it becomes impossible for an overall management system to manage power supply and demand between multiple base systems due to an occurrence of a failure in the overall management system or a first communication network; an overall management startup destination selection unit 840 that selects one of the base management devices in the multiple base systems belonging to the base group as the startup destination for a new overall management unit; and an overall management unit startup unit 860 that starts the overall management unit in the selected base management device.SELECTED DRAWING: Figure 6

Description

[Technical Field]

[0001] The present invention relates to an electric power supply and demand management system, an electric power supply and demand management method, and an autonomous decentralized restoration device. [Background technology]

[0002] In recent years, with the goal of improving economic efficiency through decarbonization and energy efficiency, there has been an increasing need to share electricity generated from renewable energy sources among multiple scattered electricity supply and demand bases.To achieve this, a multi-tiered electricity management system may be used, in which a system that manages the overall electricity supply and demand is linked to multiple systems that manage the electricity supply and demand at each supply and demand base.

[0003] For example, the abstract of Patent Document 1 below states that "in a business entity consisting of a power receiving business and a power generating business, a self-dispatch plan is formulated by taking into consideration the uncertainty of multiple production schedules at manufacturing plants, and furthermore, by adjusting the production schedule, the power demand is changed to maintain the planned simultaneous equal amount. An energy management device in a business entity with a power generating business and a power receiving business connected to a power grid, in which an EMS is installed in the power generating business and the power receiving business, and an AEMS is installed in the business entity, and the EMS of the power receiving business predicts the power transition for each of its own production lines on the scheduled date, and automatically manages the power demand on the scheduled date." It is characterized by classifying the operation schedules of its own production lines into confirmed schedules, unconfirmed schedules, and adjustable schedules, and the AEMS determines the confirmed demand on the scheduled day and the maximum demand taking into account the unconfirmed schedule from the classified operation schedules and power trends on the scheduled day reported by the EMS of the power receiving facility, and determines the self-dispatch planned output to the power receiving facility within the range of the minimum self-dispatch amount calculated as the difference between the maximum demand and the contracted power of the power receiving facility and the confirmed demand, and the EMS of the power generating facility generates power in accordance with the self-dispatch planned output determined by the AEMS."

[0004] Furthermore, the abstract of Patent Document 2 below states, "In a power management system in which a load device connected to a power system 10, a storage battery 23 connected to the power system 10, and battery-equipped equipment 20 equipped with a charge / discharge control device 26 that controls the charging and discharging of the storage battery 23 in accordance with a predetermined charge / discharge algorithm are connected to an EMS controller 31 via a network, the EMS controller 31 transmits the charge / discharge algorithm of the battery-equipped equipment 20 to the charge / discharge control device 20 via the network. The charge / discharge control device 20 retains the transmitted charge / discharge algorithm and performs charging and discharging operations of the storage battery 23 in accordance with the algorithm."

[0005] Furthermore, the abstract of Patent Document 3 below states that "a controlled device 16 is capable of executing predetermined operations and instruction operations based on messages from a control device 12 that performs power control, and is characterized by having a communication unit 121 that can acquire messages from the control device 12, and a control unit 124 that executes the predetermined operation when a predetermined time has elapsed since the message was acquired." [Prior art documents] [Patent documents]

[0006] [Patent Document 1] International Publication No. 2018 / 229895 [Patent Document 2] Japanese Patent Application Publication No. 2019-9997 [Patent Document 3] Japanese Patent Application Publication No. 2017-195774 Summary of the Invention [Problem to be solved by the invention]

[0007] However, in the above-mentioned technology, there is a demand for realizing more appropriate power supply and demand management. The present invention has been made in view of the above-mentioned circumstances, and an object of the present invention is to provide a power supply and demand management system, a power supply and demand management method, and an autonomous decentralized recovery device that can realize appropriate power supply and demand management. [Means for solving the problem]

[0008] In order to solve the above problem, the power supply and demand management system of the present invention comprises a plurality of base systems, each having a plurality of power supply and demand facilities and a base management device that manages the supply or demand of power via the power network of the power supply and demand facilities; and an overall management system having an overall management unit that generates power supply and demand plan data that defines a power supply and demand plan between the plurality of base systems via a first communication network, wherein each of the base management devices has an autonomous decentralized recovery unit, and the autonomous decentralized recovery unit has: a network reconfiguration unit that reconfigures a base group made up of a plurality of the base systems that can communicate with each other when a failure occurs in the overall management system or the first communication network and the overall management system becomes unable to manage the power supply and demand between the plurality of base systems; an overall management startup destination selection unit that selects one of the base management devices in the plurality of base systems that belong to the base group as a new startup destination for the overall management unit; and an overall management unit startup unit that starts the overall management unit in the selected base management device. [Effects of the Invention]

[0009] According to the present invention, appropriate power supply and demand management can be realized. [Brief explanation of the drawings]

[0010] [Figure 1] 1 is a block diagram of an electricity supply and demand management system according to a first embodiment. [Figure 2] FIG. 2 is a block diagram of the power supply and demand management system in the case where a failure occurs in the first embodiment. [Figure 3] FIG. 2 is a block diagram showing the hardware configuration of a total management device in the first embodiment. [Figure 4] FIG. 2 is a block diagram showing the functional configuration of an overall management unit in the first embodiment. [Figure 5] FIG. 2 is a block diagram showing the functional configuration of a base management unit in the first embodiment. [Figure 6] FIG. 2 is a block diagram showing the functional configuration of an autonomous decentralized restoration unit in the first embodiment. [Figure 7] 10 is a flowchart of an autonomous decentralized recovery processing routine. [Figure 8] 10 is a flowchart of an autonomous decentralized recovery subroutine. [Figure 9] 10 is a flowchart of a start-up destination selection subroutine. [Figure 10] FIG. 10 is a block diagram showing an example of an electric power supply and demand management system in which a new overall management unit is activated. [Figure 11] FIG. 10 is a block diagram of an overall management unit in the second embodiment. [Figure 12] 10 is a flowchart showing an example of a base failure response routine in the second embodiment. [Figure 13] FIG. 11 is a block diagram of an overall management unit 600 in the third embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0011] [Outline of the embodiment] By applying the contents of Patent Document 1 described above, it is believed that it is possible to realize power interchange between multiple base systems (supply and demand businesses) using a multi-layer structure. However, a failure may occur in the system that manages the overall power supply and demand. Also, a failure may occur in communication between the system that manages the overall power supply and demand and the system that manages the power supply and demand of each supply and demand business. In such cases, it becomes difficult to continue the overall power supply and demand management, and there is a possibility that the utilization rate and economic efficiency of power from renewable energy sources will decrease. Therefore, in the embodiment described below, an attempt is made to maintain the utilization rate and economic efficiency of power as much as possible by continuing power supply and demand management between base systems that can communicate with each other.

[0012] [First embodiment] <Configuration of the first embodiment> FIG. 1 is a block diagram of an electricity supply and demand management system 100 according to the first embodiment. The electricity supply and demand management system 100 includes an overall management system 60, multiple base systems 10-1 to 10-5, communication networks 110-J and 110-K (first communication networks), communication networks 120-E, 120-F, 120-G, and 120-H (second communication networks), and an electricity network 130. In the following description, multiple components, information, etc. having the same or similar functions or significance may be referred to by the same reference numeral with a "-" and alphanumeric characters added, such as "base systems 10-1 and 10-2." However, when it is not necessary to distinguish between these multiple components, etc., they may be referred to by omitting the "-" and alphanumeric characters, such as "base system 10."

[0013] Each base system 10 is a system installed at a base such as a power plant, factory, or power storage facility, and transmits and receives power via a power network 130. A unique base ID is assigned to each base system 10. This allows the base systems 10 to share power with each other and ensure efficient power supply and demand. The overall management system 60 plans and manages the overall power supply and consumption of the base systems 10-1 to 10-5, and supplies the results to each base system 10 as power supply and demand plan data DPLN-1 to DPLN-5 (not shown) corresponding to each base system 10-1 to 10-5. For example, the power supply and demand plan data DPLN includes a command such as "transfer the power generated by base system 10-1 to base system 10-5." This allows base system 10-5 to consume the power received from base system 10-1.

[0014] The power supply and demand plan data DPLN includes, for example, the date of power supply and demand, the time slot during which power supply and demand will occur, the power type indicating the type of power, the power source type, the base ID of the power supply, the base ID of the power demand, and the amount of power to be received. Here, "power type" indicates, for example, the type of power generated by renewable energy, the type of power generated by combined heat and power generation, etc.

[0015] The overall management system 60 and each base system 10 are connected to each other via communication networks 110-J and 110-K so that they can communicate with each other. Furthermore, the base systems 10 may be connected to each other via a communication network 120 so that they can communicate with each other. In the example of FIG. 1 , the base system 10-1 is connected to the base system 10-4 via communication network 120-E and to the base system 10-2 via communication network 120-F. Furthermore, the base system 10-5 is connected to the base system 10-4 via communication network 120-G and to the base system 10-3 via communication network 120-H. Furthermore, the base systems 10 that are not directly connected to each other can be reached via (hopping between) other base systems 10. For example, the base systems 10-1 and 10-3 can communicate with each other via the base systems 10-4 and 10-5.

[0016] Each base system 10-k (where 1≦k≦5) includes a base management device 11-k, a power supply and demand facility 12-k, and an equipment control device 13-k. The base management device 11-k manages the power supply and demand within the base. In FIG. 1, each base system 10-k includes one power supply and demand facility 12-k, but the number of power supply and demand facilities 12-k is not limited to one and may be multiple. The power supply and demand facility 12-k may be, for example, a power generation device that generates power from renewable energy such as solar power, or a load device that consumes power such as a machine tool. The equipment control device 13-k controls the power supply and demand facilities 12-k.

[0017] The base management device 11-k and the equipment control device 13-k are connected to each other so that they can communicate with each other via a communication network 140. Furthermore, the equipment control device 13-k and the power supply and demand facility 12-k within the same base are connected to each other so that they can communicate with each other via a communication network 150. The base management device 11-k and the equipment control device 13-k may be installed within the same base where power supply and demand is performed, or only the base management device 11-k may be installed in a remote location. The base management device 11-k includes a base management unit 700-k.

[0018] The base management unit 700-k calculates, for example, a supply forecast value DSPLY-k (not shown), which is a time-series forecast value of power generated by renewable energy, and a demand forecast value DEDM-k (not shown), which is a time-series forecast value of power consumed within the base.The base management unit 700-k then calculates power interchange availability information DICT-k (not shown) or power interchange request information DDMD-k (not shown) from these time-series forecast values, and notifies the overall management system 60 of the results via the communication network 110.

[0019] The power interchange availability information DICT-k and the power interchange request information DDMD-k include, for example, the information listed below. - The date on which power is to be supplied or requested to be supplied; Time slots for transferring or requesting power; - Power type indicating the type of electricity; Power source type, - The ID of the location that will provide or request power supply, The amount of electricity to be supplied or requested to be supplied. The base management unit 700-k may notify the overall management system 60 of a supply forecast value DSPLY-k and a demand forecast value DEDM-k in addition to the above-mentioned data.

[0020] Furthermore, the local management device 11-k accesses the overall management system 60 via the communication network 110 and notifies it of power supply and demand record data DACV-k (not shown) that indicates the record values ​​of power generation and consumption. The power supply and demand record data DACV-k includes, for example, the information listed below. - The date on which the electricity was supplied and demanded; - Time slot during which power supply and demand occurred, - Power type indicating the type of electricity; Power source type, Actual supply and demand values ​​where supply and demand were performed.

[0021] The equipment control device 13-k controls the power supply and demand facility 12-k based on the supply and demand plan notified by the base management device 11-k. The equipment control device 13-k also monitors the operating status of the power supply and demand facility 12-k and transmits the information to the base management device 11-k. The power supply and demand facilities 12 are connected to each other via a power network 130, and each power supply and demand facility 12 can transmit power to other power supply and demand facilities 12, and the received power can be consumed by the power supply and demand facilities 12.

[0022] The overall management system 60 includes an overall management device 61. The overall management device 61 uses an overall management unit 600-A to create power supply and demand plan data DPLN for each base system 10 based on the power interchange availability information DICT and power interchange request information DDMD received from each base system 10.

[0023] FIG. 2 is a block diagram of the power supply and demand management system 100 in the first embodiment when a failure occurs. 2, failures occur in the communication networks 110-J, 110-K, and 120-G, and the overall management system 60 is unable to transmit the power supply and demand plan data DPLN to the base system 10. This causes problems with power interchange between multiple bases. Furthermore, a communication failure also occurs in the communication network 120-G, and the base systems 10-4 and 10-5 are also unable to communicate with each other. As a result, the base systems 10-1, 10-2, and 10-4 are unable to reach the base systems 10-3 and 10-5 via communication.

[0024] In this embodiment, when a failure occurs in the overall management system 60 having the overall management unit 600-A, or when a communication failure occurs between the overall management system 60 and the base system 10, the base management devices 11 communicate with each other in an autonomous and distributed manner. Then, one of the multiple base management devices 11 that can communicate with each other starts the overall management unit 600. Then, the base system 10 having the overall management unit 600 cooperates with one or more other base systems 10 to restore and continue power supply and demand management.

[0025] FIG. 3 is a block diagram showing the hardware configuration of the overall management device 61 in the first embodiment. As shown in FIG. 3, the overall management device 61 has a processor 62, a communication I / F (interface) 63, a main memory device 64, an auxiliary memory device 65, an input / output I / F 66, and a bus 67 that communicatively connects the above-mentioned modules. The auxiliary memory device 65 stores various programs 68 and various data 69. The site management device 11 has the same hardware configuration as the overall management device 61. The overall management device 61 and the site management device 11 may be a single computer such as a server, or multiple computers such as servers may work together to provide various functions. The site management device 11 may be located at a site where power is supplied and demanded, or may be located in a remote location as a server.

[0026] The processor 62 is a central processing unit that controls the operation of each part of the overall management device 61. The processor 62 is, for example, a central processing unit (CPU), a digital signal processor (DSP), or an application specific integrated circuit (ASIC). The processor 62 deploys a program 68 stored in the auxiliary storage device 65 in an executable manner in a working area of ​​the main storage device 64. The main storage device 64 stores the program executed by the processor 62, data processed by the processor, etc. The main storage device 64 is, for example, a flash memory, a random access memory (RAM), etc. The auxiliary storage device 65 stores, for example, an operating system (OS), various programs, various tables, etc. The auxiliary storage device 65 is, for example, a silicon disk including a non-volatile semiconductor memory (flash memory, erasable programmable ROM (EPROM)), a solid state drive device, a hard disk drive (HDD), etc. The program 68 and the data 69 may be downloaded from a predetermined location using an external communication network and set up in the auxiliary storage device 65, or the program 68 or the data 69 may be read from a predetermined storage medium storing the program 68 or the data 69 and set up in the auxiliary storage device 65. The program 68 includes all programs used in this embodiment, such as the power interchange plan formulation program and the autonomous decentralized recovery program. The data 69 includes all data used in this embodiment, such as the power interchange plan and the power supply and demand record data DACV-k.

[0027] The communication I / F 63 is an interface for communicatively connecting each system with the overall management system 60 via the communication network 110. The input / output I / F 66 accepts operation instructions and the like from an administrator who operates an input device connected to the input / output I / F 66. Examples of the input device include a keyboard, a touch panel, a mouse, and a microphone. In addition, the input / output I / F 66 can be connected to display devices such as an LCD (Liquid Crystal Display), an EL (Electroluminescence) panel, and an organic EL panel, as well as output devices such as a printer and a speaker. The input / output I / F 66 outputs data and information processed by the processor 62 and data and information stored in the main memory device 64 and the auxiliary memory device 65 to the output device.

[0028] FIG. 4 is a block diagram showing the functional configuration of the overall management unit 600-A in the first embodiment. As shown in FIG. 4, the overall management unit 600-A includes an overall supply and demand planning unit 610, a market trading unit 620, a health monitoring unit 630, and an external communication unit 640. The overall supply and demand planning unit 610 creates power supply and demand plan data DPLN for the base system 10 based on the power interchange availability information DICT and power interchange request information DDMD received from the base system 10 .

[0029] Here, the sum of the power interchange availability information DICT-1 to DICT-5 is called total power interchange availability information ΣDICT (not shown), and the sum of the power interchange request information DDMD-1 to DDMD-5 is called total power interchange request information ΣDDMD (not shown). The overall supply and demand planning unit 610 matches, for example, the base system 10 that notified the maximum power interchange availability information DICT with the base system 10 that notified the maximum power interchange request information DDMD, and formulates a power supply and demand plan between the two systems.

[0030] Next, the matched amount of power interchangeable information DICT is subtracted from the total power interchangeable information ΣDICT, and the matched amount of power interchange request information DDMD is subtracted from the total power interchange request information ΣDDMD. Then, from the remaining power interchangeable information DICT and power interchange request information DDMD, the maximum power interchangeable information DICT is matched with the maximum power interchange request information DDMD.

[0031] The overall supply and demand planning unit 610 creates the power supply and demand plan data DPLN by repeating the above-described operation until either the total power interchange request information ΣDDMD or the total power interchange request information ΣDDMD becomes "0." The power supply and demand plan data DPLN may be created by applying an optimization method or the like that maximizes the utilization rate and economic efficiency of electricity from renewable energy sources. Priorities may be assigned to the base systems 10 that interchange power and the base systems 10 that receive the power, and the power supply and demand plan data DPLN may be created so that the systems with higher priorities are prioritized. Furthermore, the power supply and demand plan data DPLN may include transactions with power trading markets or the like external to the power supply and demand management system 100. In other words, power trading may be performed rather than power interchange between bases, prioritizing environmental friendliness and economic efficiency.

[0032] The overall supply and demand planning unit 610 transmits the power supply and demand plan data DPLN that it has created for each base to the external communication unit 640. Furthermore, if the power supply and demand plan data DPLN includes a trading plan with an external power trading market, the overall supply and demand planning unit 610 transmits the created trading plan to the market trading unit 620. Furthermore, the overall supply and demand planning unit 610 receives the results of power trading agreements from the market trading unit 620, and if the power supply and demand plan data DPLN needs to be updated, it updates the power supply and demand plan data DPLN of the base system 10 and transmits the updated power supply and demand plan data DPLN to the external communication unit 640.

[0033] The market trading unit 620 makes bids on the power trading market and manages the contract status based on the trading plan received from the overall supply and demand planning unit 610. The contract results are sent to the overall supply and demand planning unit 610. The alive / dead monitoring unit 630 manages the alive / dead status of the base systems 10. For example, it transmits an alive / dead monitoring message DLDM to the base systems 10 at regular time intervals via the external communication unit 640. The alive / dead monitoring unit 630 monitors the alive / dead status of each base system 10 based on responses from the base systems 10 received from the external communication unit 640.

[0034] The external communication unit 640 communicates with the base systems 10 via the communication network 110. When the external communication unit 640 receives power interchange availability information DICT-k and power interchange request information DDMD-k from a base system 10-k (1≦k≦5), it transmits the power interchange availability information DICT-k and the power interchange request information DDMD-k to the overall supply and demand planning unit 610. When the external communication unit 640 receives power supply and demand plan data DPLN for each base system 10 from the overall supply and demand planning unit 610, it transmits the power supply and demand plan data DPLN to the base system 10. When the external communication unit 640 receives an alive / dead monitoring message DLDM for each base system 10 from the alive / dead monitoring unit 630, it transmits the alive / dead monitoring message DLDM to the base system 10. When the external communication unit 640 receives a response to the alive / dead monitoring message DLDM from the base system 10, it transmits the response to the alive / dead monitoring unit 630.

[0035] Fig. 5 is a block diagram showing the functional configuration of the base management unit 700 in the first embodiment. As shown in Fig. 5, the base management unit 700 includes a supply and demand prediction unit 710, a plan execution unit 720, an external communication unit 730, and an autonomous decentralized recovery unit 800 (autonomous decentralized recovery device).

[0036] The supply and demand prediction unit 710 calculates a supply prediction value DSPLY of the power to be generated in the base system 10 and a demand prediction value DEDM of the power to be consumed within the base, and calculates power interchange availability information DICT or power interchange request information DDMD from these prediction values. The supply and demand prediction unit 710 calculates the supply prediction value DSPLY and the demand prediction value DEDM based on, for example, the operating status of the power supply and demand equipment 12 received from the equipment control device 13, meteorological information and weather forecasts for the base system 10, past supply and demand history stored in an auxiliary storage device, etc.

[0037] For example, if the difference between the predicted supply value DSPLY of power to be generated and the predicted demand value DEDM of power to be consumed is positive, this may be treated as power interchange availability information DICT, and if negative, as power interchange request information DDMD. The supply and demand prediction unit 710 transmits the calculated power interchange availability information DICT or power interchange request information DDMD to the external communication unit 730. It is also possible to transmit the calculated power supply prediction value DSPLY and the calculated demand prediction value DEDM of power to be consumed within the base directly to the overall management system 60 without calculating the power interchange availability information DICT or the power interchange request information DDMD.

[0038] The plan execution unit 720 manages and executes the base power supply and demand plan data DPLN received from the overall management system 60 via the external communication unit 730. For example, when executing the received base power supply and demand plan data DPLN, the plan execution unit 720 transmits the power supply and demand plan data DPLN to the equipment control device 13 via the external communication unit 730 and causes the equipment control device 13 to execute the contents of the power supply and demand plan data DPLN.

[0039] When the autonomous distributed recovery unit 800 receives a health / death monitoring message DLDM from the overall management system 60 via the external communication unit 730, it transmits an alive response message to the overall management system 60 via the external communication unit 730. Then, if the autonomous distributed recovery unit 800 does not receive a health / death monitoring message DLDM from the overall management system 60 for a certain period of time, it performs autonomous distributed recovery operation. If the health / death monitoring message DLDM is not received, this occurs when a failure occurs in the overall management system 60 or when a failure occurs in communication between the base system 10 and the overall management system 60.

[0040] The external communication unit 730 communicates with the overall management system 60 via the communication network 110. When the external communication unit 730 receives power supply and demand plan data DPLN from the overall management system 60, it transmits the power supply and demand plan data DPLN to the plan execution unit 720. Furthermore, as described above, when the external communication unit 730 receives a life / death monitoring message DLDM from the overall management system 60, it transmits the life / death monitoring message DLDM to the autonomous decentralized recovery unit 800. Furthermore, when the external communication unit 730 receives power interchange availability information DICT, power interchange request information DDMD, supply forecast value DSPLY, or demand forecast value DEDM from the supply and demand prediction unit 710, it transmits these data to the overall management system 60. Furthermore, when the autonomous decentralized recovery unit 800 detects a failure in the overall management system 60, the external communication unit 730 communicates with other base systems 10 via the communication network 120 regarding autonomous decentralized recovery and communication after recovery.

[0041] FIG. 6 is a block diagram showing the functional configuration of the autonomous decentralized restoration unit 800 in the first embodiment. As shown in Figure 6, the autonomous distributed recovery unit 800 includes an alive monitoring response unit 810, a network reconfiguration unit 820 (network reconfiguration process), a score calculation unit 830, an overall management startup destination selection unit 840 (overall management startup destination selection process), a startup function determination unit 850, an overall management unit startup unit 860 (overall management unit startup process), and a communication unit 870.

[0042] The alive / dead monitoring response unit 810 responds to the alive / dead monitoring message DLDM received from the overall management system 60 and manages the reception status. If the alive / dead monitoring response unit 810 does not receive the alive / dead monitoring message DLDM for a certain period of time, it determines that a failure has occurred in the overall management system 60 and starts autonomous distributed recovery. For example, the alive / dead monitoring response unit 810 stores the time when the alive / dead monitoring message DLDM was received in an auxiliary storage device in the local management device 11. Then, if a new alive / dead monitoring message DLDM is not received after a predetermined period of time has elapsed since the time when the alive / dead monitoring message DLDM was received, the alive / dead monitoring response unit 810 determines that a failure has occurred in the overall management system 60. When the alive / dead monitoring response unit 810 detects a failure in the overall management system 60, it sends an autonomous distributed recovery start command to the network reconfiguration unit 820 and the communication unit 870 and starts autonomous distributed recovery.

[0043] Furthermore, the alive / dead monitoring response unit 810 notifies the base system 10 that is adjacent in communication to the detection of a failure in the overall management system 60 via the communication network 120, and initiates autonomous distributed recovery of the entire system. The alive / dead monitoring response unit 810 may also receive a failure detection of the overall management system 60 from another base system 10 that is adjacent in communication via the communication unit 870. In this case, the alive / dead monitoring response unit 810 that has received the failure detection sends an autonomous distributed recovery start command to the communication unit 870, and initiates autonomous distributed recovery, just as when the alive / dead monitoring response unit 810 itself detects a failure in the overall management system 60. Furthermore, the alive / dead monitoring response unit 810 that has received the failure detection notifies the other base system 10 that is adjacent in communication to the detection of a failure in the overall management system 60 via the communication network 120.

[0044] The network reconfiguration unit 820 exchanges information on the communication connection status with other adjacent base systems 10, and reconfigures the connection relationships with other base systems 10 based on the current failure status. In this way, a group (hereinafter referred to as a base group) is constructed that includes a plurality of base systems 10 that are configured to be able to communicate with each other.

[0045] As will be described in detail later, the overall management unit activation unit 860 of one of the base management devices 11 among the base systems 10 belonging to the base group activates a new overall management unit 600 in the base management device 11. The score calculation unit 830 then calculates a score for determining the base management device 11 that will activate the overall management unit 600. For example, the score calculation unit 830 may calculate the score based on the remaining computing resources of the base management device 11, the type of power supply and demand equipment 12 in the base system 10, the number of power supply and demand equipment 12, etc. Here, the "type of power supply and demand equipment 12" refers to, for example, power generation equipment such as solar power generators, storage batteries, and power demand equipment such as factories. Note that the score may be calculated based on the number of hops based on communication connection relationships, the connection relationship of the physical communication network 120, or the congestion state. Furthermore, the score may be calculated based on the geographical location of the base systems 10 to take into account the geographical relevance of failures caused by disasters and the like.

[0046] The overall management startup destination selection unit 840 selects the local management device 11 with the highest score within the local group as the startup destination of the overall management unit 600. The overall management startup destination selection unit 840 exchanges the scores calculated by the score calculation unit 830 with adjacent local systems 10 by communicating with each other. This calculates which local management device 11 has the highest score within the local group. Furthermore, if the local management device 11 to which the overall management startup destination selection unit 840 belongs has the highest score, the overall management startup destination selection unit 840 transmits a startup command to the startup function determination unit 850 to instruct the startup of the overall management unit 600.

[0047] The activation function determination unit 850 determines the functions to be provided in the overall management unit 600 to be activated, for example, depending on the number of base systems 10 in the base group reconfigured by the network reconfiguration unit 820. For example, in electricity market trading, there may be restrictions such as a single bidding authority, which states that "one business operator can only bid once per time slot." In such a case, activating the market trading unit 620 (see FIG. 4) in each of the divided base groups would cause inconvenience. Therefore, the activation function determination unit 850 determines to activate the overall management unit 600 including the market trading unit 620 when the number of base systems 10 belonging to the base group is a majority of the total number of bases ("5" in the example of FIG. 1).

[0048] On the other hand, if the number of base systems 10 belonging to the base group is half or less, the activation function determination unit 850 determines to activate the overall management unit 600 that does not have a market trading unit 620. The activation function determination unit 850 sends a startup command along with this determination result to the overall management unit startup unit 860. Note that the functions to be equipped in the overall management unit 600 to be activated may be determined based on the characteristics of the power equipment, such as the power generation capacity, power receiving capacity, and power storage capacity, of the entire reconfigured base group. Furthermore, if multiple business entities are cooperating to share power between multiple base systems 10, the functions to be equipped in the overall management unit 600 may be determined depending on the business entities.

[0049] The overall management unit startup unit 860 starts up the overall management unit 600 based on the received startup command. As a result, the started overall management unit 600 notifies the base systems 10 in the base group of its startup. Then, the newly started overall management unit 600 takes over the functions that were previously handled by the overall management unit 600-A of the overall management system 60. This completes the restoration of power supply and demand management through cooperation between the overall management unit 600 and the multiple base systems 10.

[0050] The communication unit 870 has a function of receiving the alive monitoring message DLDM and the failure detection of the overall management system 60 from the external communication unit 730, and transmitting them to the alive monitoring response unit 810. The communication unit 870 also has a function of receiving information indicating the connection relationship of the base system 10 from the external communication unit 730, and transmitting it to the network reconfiguration unit 820. The communication unit 870 also has a function of receiving a score used for selecting a startup destination by the overall management unit 600 from the external communication unit 730, and transmitting it to the overall management startup destination selection unit 840.

[0051] 7 is a flowchart of an autonomous decentralized restoration processing routine, which illustrates the contents of an autonomous decentralized restoration procedure in the autonomous decentralized restoration unit 800 (see FIG. 5) and the like. 7, when the process proceeds to step S2, the base management device 11 including the overall management unit 600 executes alive monitoring of each base system 10. That is, the processor in the base management device 11 loads an alive monitoring program stored in the auxiliary storage device into the main storage device and executes alive monitoring of each base system 10.

[0052] Furthermore, the base management device 11 loads the autonomous distributed recovery program stored in the auxiliary storage device into the main storage device and starts the autonomous distributed recovery operation. When the alive / dead monitoring response unit 810 receives the alive / dead monitoring message DLDM from the alive / dead monitoring unit 630 of the overall management unit 600, it stores the time when the alive / dead monitoring message DLDM was received. It also transmits a response to the alive / dead monitoring message DLDM.

[0053] Next, when the process proceeds to step S4, the alive-or-dead monitoring response unit 810 compares the current time with the time when the last alive-or-dead monitoring message DLDM was received, and determines whether a predetermined time has elapsed since the last alive-or-dead monitoring message DLDM was received. If the determination here is "No," the process returns to step S901, and the above-mentioned processes such as alive-or-dead monitoring are repeated.

[0054] On the other hand, if the determination in step S4 is "Yes," the process proceeds to step S6. Step S6 is executed when a failure occurs in a system having the overall management unit 600 (for example, the overall management system 60), or when a failure occurs in the communication network 110 or 120. In step S6, the autonomous distributed recovery subroutine shown in FIG. 8 is called, and the autonomous distributed recovery unit 800 starts the autonomous distributed recovery operation. Details of this process will be described later, but an overview of step S6 will be given below.

[0055] In step S6, first, the alive check response unit 810 sends an autonomous distributed recovery start command to the network reconfiguration unit 820. The alive check response unit 810 also notifies the communicatively adjacent base systems 10 via the communication network 120 of the detection of a fault in the system having the overall management unit 600, and starts the autonomous distributed recovery of the entire system.

[0056] Furthermore, in the above-mentioned step S2, there may be a case where a failure detection of the overall management system 60 is received from another adjacent base system 10. In this case as well, in step S6, the alive monitoring response unit 810 sends an autonomous distributed recovery start command to the network reconfiguration unit 820 to start the autonomous distributed recovery operation. In this way, by the operations of steps S2 to S6, the base system 10 that detected the failure of the system having the overall management unit 600 and all base systems 10 that are communicatively reachable from each other start the autonomous distributed recovery operation. Then, the network reconfiguration unit 820 exchanges information on the communication connection status with the communicatively adjacent base systems 10, and reconfigures the current failure status and the connection relationship of the base systems 10 (i.e., the base group).

[0057] Next, when the process proceeds to step S8, the score calculation unit 830 and the overall management startup destination selection unit 840 select a local management device 11 that will be the startup destination of the new overall management unit 600. More specifically, in step S8, the startup destination selection subroutine shown in FIG. 9 is called. Details of this process will be described later, but an overview of step S8 will be given below. That is, first, the score calculation unit 830 calculates the above-mentioned score for each local management device 11 that belongs to the base group reconfigured in step S6, and transmits the score to the overall management startup destination selection unit 840.

[0058] The overall management startup destination selection unit 840 communicates and propagates the received score to other base systems 10 belonging to the same base group using the same procedure as in step S6. As a result, in each base system 10 belonging to the base group, the overall management startup destination selection unit 840 calculates which base management device 11 has the highest score, and selects the base management device 11 with the highest score as the startup destination of the new overall management unit 600. Note that in the above example, the start of the autonomous distributed recovery operation (step S6) and the selection process of the startup destination of the overall management unit (step S8) are executed sequentially, but they may be executed in parallel for the purpose of reducing the time for the recovery process, etc.

[0059] Next, when the process proceeds to step S10, the overall management startup destination selection unit 840 determines whether or not its own base was selected as the startup destination of the new overall management unit 600 in the above-mentioned step S8. If the determination here is "No," the process of this routine ends. That is, a new overall management unit 600 is not started in the base management device 11 to which the autonomous decentralized recovery unit 800 belongs. On the other hand, if the determination in step S10 is "Yes," the process proceeds to step S12.

[0060] Here, the number of base systems 10 originally belonging to the electricity supply and demand management system 100 is referred to as the "total number of bases." In the example shown in FIG. 1, the total number of bases is "5." In step S12, the activation function determination unit 850 determines whether the number of base systems 10 belonging to the base group is a majority of the total number of bases.

[0061] If the determination in step S12 is "Yes," the process proceeds to step S14. In this case, the base group is the base group having the largest number of base systems 10 in the electricity supply and demand management system 100. Therefore, the activation function determination unit 850 transmits an activation command to the overall management unit activation unit 860 to activate the overall management unit 600 having a single function, such as the market trading unit 620. As a result, the overall management unit activation unit 860 activates the overall management unit 600 having a single function, such as the market trading unit 620, based on the received activation command.

[0062] On the other hand, if the determination in step S12 is "No," the process proceeds to step S16. Here, activation function determination unit 850 transmits an activation command to overall management unit activation unit 860 to activate overall management unit 600 that does not have a unitary function, such as market trading unit 620. As a result, overall management unit activation unit 860 activates overall management unit 600 that does not have a unitary function, such as market trading unit 620, based on the received activation command.

[0063] In the above example, the function to be activated is determined based on the number of base systems 10 belonging to the base group, but the function to be activated may be determined by calculating the total amount of power that the base systems 10 can supply, and determining whether this value exceeds a predetermined threshold. In the above example, the market trading unit 620 is exemplified as a function that requires unity, but if the overall management unit 600 has a function other than those exemplified in this embodiment, the determination may be made for that function.

[0064] When the processing of either step S14 or S16 is completed, the processing proceeds to step S18. Here, the activated overall management unit 600 notifies the base systems 10 belonging to the base group that the overall management unit 600 has been activated. With the above steps, the processing of this routine is completed.

[0065] After the series of processes according to this routine is completed, the new overall management unit 600 monitors the alive status of the base system 10, just like the overall management unit 600 that was operating before the failure was detected. In addition, the autonomous distributed recovery unit 800 restarts the autonomous distributed recovery processing routine (FIG. 7). By repeating the above operations, even if a failure occurs in the base system 10 having the overall management unit 600 after recovery, or if a failure occurs again in communication between the base system 10 and another base system 10, recovery can be achieved using the same procedure.

[0066] 8 is a flowchart of the autonomous decentralized recovery subroutine, which is called in step S6 of the autonomous decentralized recovery processing routine (FIG. 7) described above. 8, when the process proceeds to step S602, the autonomous distributed recovery unit 800 performs initialization processing. That is, the network reconfiguration unit 820 communicates with the adjacent base system 10 and establishes the connection state at the start of the network reconfiguration. Then, the network reconfiguration unit 820 initializes the established connection state as connection state data of its own base. The connection state data is, for example, a set of edges that represent the connections between the base systems 10. Here, an "edge" represents a line connecting the base systems 10 that can communicate with each other.

[0067] Next, when the process proceeds to step S604, the network reconfiguration unit 820 transmits the connection status data of its own base to the adjacent base system 10. Next, when the process proceeds to step S606, the network reconfiguration unit 820 determines whether or not other connection status data has been received from the adjacent base system 10 within a predetermined time period.

[0068] If the determination in step S606 is "Yes," the process proceeds to step S608. Here, the network reconfiguration unit 820 compares the received connection status data with the connection status data of its own base and determines whether or not an unknown connection status is included. If the determination in step S608 is "No," the process returns to step S606.

[0069] On the other hand, if the determination in step S608 is "Yes," the process proceeds to step S610. Here, the network reconfiguration unit 820 updates the connection status data of the local base using the received connection status data. For example, if the connection status data of the local base and the received connection status data are a set of edges representing connections between base systems 10, the network reconfiguration unit 820 calculates the union of the connection status data of the local base and the received connection status data, and updates the result as new connection status data of the local base. When the process of step S610 is completed, the process returns to step S604, and the processes of steps S604 to S610 are continued until new connection status data is no longer received from the adjacent base system 10.

[0070] If no new connection status data is received from the adjacent base system 10 even after the predetermined time has elapsed, the result in step S606 is "No," and the process proceeds to step S612. Here, the network reconfiguration unit 820 determines that the reconfiguration of the connection status has been completed, and configures a base group to which the base belongs based on the connection status data of the base. For example, if the reconfigured connection status data includes connection relationships with base systems 10-1, 10-2, and 10-4, the network reconfiguration unit 820 configures a base group whose elements are base systems 10-1, 10-2, and 10-4. When the above process is completed, the process returns to the autonomous distributed recovery process routine (FIG. 7) that called this routine, and the process from step S8 onwards in FIG. 7 is continued.

[0071] 9 is a flowchart of the startup destination selection subroutine, which is called in step S8 of the autonomous decentralized recovery processing routine (FIG. 7) described above. 9, when the process proceeds to step S802, the overall management startup destination selection unit 840 calculates the score of the base management device 11 at the own base and sets this as the initial value of the maximum score. The score of the base management device 11 at the own base can be calculated based on the computational resources of the base management device 11, the type and number of power supply and demand facilities 12 at the own base, etc.

[0072] For example, the computational resources of the base management device 11 are calculated as values, and a weight is set for each type of power supply and demand facility 12. Then, from the computational resource values, a value is calculated for each type of power supply and demand facility 12 by multiplying the number of power supply and demand facilities 12 by the weight, and the result is used as a score. Note that in the above example, the score is calculated based on the computational resources of the base management device 11, the type and number of power supply and demand facilities 12, etc., but the score may also be calculated based on the number of communication hops to other base management devices 11, the number of adjacent connections, the connection relationship of the physical communication network, or the congestion state.

[0073] Next, when the process proceeds to step S804, the overall management startup destination selection unit 840 transmits the current maximum score to another adjacent base system 10 (connected directly without hopping). Next, when the process proceeds to step S806, the overall management startup destination selection unit 840 determines whether or not another score has been received from an adjacent base system 10 within a predetermined time. Here, the received score is the current maximum score of the base system 10 that transmitted it.

[0074] If the determination in step S805 is "Yes," the process proceeds to step S808, where the overall management startup destination selection unit 840 determines whether the received score is greater than the maximum score. If the determination here is "No," the process returns to S806. On the other hand, if the determination in step S808 is "Yes," the process proceeds to step S810, where the overall management startup destination selection unit 840 updates the maximum score to the received score. Note that if the received score and the maximum score are equal, it is preferable to use the site with the smaller base ID as the maximum score. When the process in step S810 is completed, the process returns to step S804, and the processes in steps S804 to S810 are continued until no new scores are received from adjacent site systems 10.

[0075] If no new score is received from the adjacent base system 10 after the predetermined time has elapsed, the result of step S806 is determined to be "No," and the process proceeds to step S812. Here, the overall management startup destination selection unit 840 determines that calculation of the maximum score has been completed, and determines whether the maximum score matches the score of the base.

[0076] If the determination in step S812 is "Yes," the process proceeds to step S814, where the overall management startup destination selection unit 840 selects its own base as the startup destination of the overall management unit 600. On the other hand, if the determination in step S812 is "No," the process in step S814 is skipped. When the above process is completed, the process returns to the autonomous decentralized recovery process routine (FIG. 7) that called this routine, and the process from step S10 onwards in FIG. 7 is continued.

[0077] In the above example, the overall management startup destination selection unit 840 selected the local management device 11 with the highest score as the startup destination. However, the process of determining whether the score is large or small may be reversed depending on the score calculation criteria. That is, the more suitable the local management device 11 is as a device that will start the overall management unit 600, the smaller its score may be. In this case, the overall management startup destination selection unit 840 may select the local management device 11 with the smallest score as the device that will start the overall management unit 600. Furthermore, the local management devices 11 that are permitted to start the overall management unit 600 may be limited from all the local management devices 11. In this case, the overall management startup destination selection unit 840 selects the local management device 11 that will start the overall management unit 600 from among the devices that are permitted to start the overall management unit 600.

[0078] Fig. 10 is a block diagram showing an example of the power supply and demand management system 100 in which a new overall management unit 600 has been activated. That is, Fig. 10 is a block diagram showing the result of performing an autonomous distributed recovery operation for the failure state shown in Fig. 2. That is, in the example of Fig. 10, new overall management units 600-B and 600-C have been activated in the base systems 10-1 and 10-5, respectively. Then, in the divided base groups GB and GC, power interchange between the multiple bases has been resumed.

[0079] 2 occurs, the alive monitoring response unit 810 detects the failure in the power supply and demand management system 100 in at least some of the base management devices 11. That is, when the autonomous decentralized recovery processing routine (FIG. 7) is executed in the base management device 11, the result in step S4 is "Yes." As a result, the base group GB having the base systems 10-1, 10-2, and 10-4 and the base group GC having the base systems 10-3 and 10-5 are reconfigured (step S6).

[0080] In addition, in each of the base groups GB and GC, the overall management unit 600 selects the base management device 11-1 of the base system 10-1 and the base management device 11-5 of the base system 10-5 as the startup destinations (step S8). Then, in each of the base groups GB and GC, the power supply and demand management is restored and resumed through cooperation between the overall management units 600-B and 600-C and the multiple base systems 10.

[0081] Here, the number of base systems 10 in the base group GB is "3," which is more than half of the total number of bases, "5." Therefore, the overall management unit 600-B activated in the base management device 11-1 has a market trading unit 620 (see FIG. 4). On the other hand, the number of base systems 10 in the base group GC is "2," which is less than half of the total number of bases, "5." Therefore, the overall management unit 600-C activated in the base management device 11-5 does not have a market trading unit 620.

[0082] In this way, the appropriate overall management units 600-B, 600-C are activated depending on the number of base systems 10 belonging to the reconfigured base group. This makes it possible to plan and execute appropriate power supply and demand control in response to changes that occur after a failure occurs in the power supply and demand management system 100 having the original overall management unit 600-A.

[0083] Furthermore, as described above, it is not necessary for all base management devices 11 to have the function of starting the overall management unit 600, and it is possible to limit the base management devices 11 that are permitted to start the overall management unit 600. For example, it is conceivable that the base management devices 11 of base systems 10-1, 10-2, 10-3, and 10-5 are permitted to start the overall management unit 600, while the base management device 11-4 of base system 10-4 is prohibited from starting the overall management unit 600. In this case, the score calculation unit 830 of base system 10-4 can subtract a sufficiently large value from the score used to select the system to be started, thereby enabling recovery using the method described above.

[0084] On the other hand, if only multiple base management devices 11 in which the activation of the overall management unit 600 is prohibited can communicate with each other, and communication is not possible with base management devices 11 in which the activation of the overall management unit 600 is permitted, it will be impossible to restore power supply and demand management in a base group consisting of these base systems 10.

[0085] In the above example, a method for dynamically determining the activation destination of the overall management unit 600 based on the score among the base management devices 11 that can communicate with each other has been exemplified. However, at least one base management device 11 may be selected in advance as the activation destination of the overall management unit 600. In this case, the network reconfiguration operation (step S6), the activation destination selection operation (step S8), the unity function determination operation (step S12), etc. may be omitted, and the overall management unit 600 may be activated in the base management device 11 selected in advance. For example, the pre-selection of the activation destination may be performed using the computational resources of the base management device 11, the number and type of power supply and demand facilities 12, the state of the communication network and the power network, etc., as in the case of dynamic selection.

[0086] Furthermore, the functions of the overall management unit 600 at the predetermined startup destination may be restricted. Also, it may be determined in advance which base system 10 the predetermined startup destination will manage. For example, the base management devices 11-1 and 11-3 of the base systems 10-1 and 10-3 may be determined in advance as the startup destinations of the overall management unit 600, and the base management device 11-1 may be able to start the overall management unit 600 with a single-purpose function, while the base management device 11-3 may be able to start the overall management unit 600 without a single-purpose function.

[0087] Furthermore, for example, in the event of a failure in the overall management unit 600-A, it may be determined in advance that the base management device 11-1 of the base system 10-1 will manage the base systems 10-2 and 10-4, and the base management device 11-3 of the base system 10-3 will manage the base system 10-5. In the above example, if a failure occurs in the overall management unit 600-A, the base management devices 11-1 and 11-3 can immediately start up the overall management unit 600 and perform recovery, omitting the network reconfiguration operation (step S6), the startup destination selection operation (step S8), and the unity function determination operation (step S12). On the other hand, if the startup destination is selected in advance, recovery from a disconnection between any of the base systems 10 becomes difficult, making the system vulnerable to a second failure.

[0088] [Second embodiment] Next, a power supply and demand management system according to a second embodiment will be described. The configuration of the power supply and demand management system according to the second embodiment is the same as the power supply and demand management system 100 (FIGS. 1 to 10) according to the first embodiment, except for the points described below. In the description of each embodiment, parts corresponding to those in the first embodiment are given the same reference numerals, and their description may be omitted. In this embodiment, when a failure occurs in a base system 10 or the power supply and demand facility 12 at that base, the base system 10 having an overall management unit 600 corrects the power supply and demand plan data DPLN of normal base systems 10 other than the failed base, thereby reducing the difference with the power supply and demand plan data DPLN of the entire group that interchanges power. Hereinafter, with reference to Figures 11 and 12, a compensation operation for a failure in the base system 10 and the power supply and demand facility 12 at that base according to the second embodiment will be described.

[0089] First, in this embodiment, the base management unit 700 (see FIG. 5) in each base system 10 will be described. The configuration of the base management unit 700 is the same as that in the first embodiment. As described above, the supply and demand prediction unit 710 in the base management unit 700 calculates a supply prediction value DSPLY-k of power to be generated and a demand prediction value DEDM-k of power to be consumed within the base in the base system 10-k, and calculates power interchange availability information DICT-k or power interchange request information DDMD-k from these prediction values.

[0090] In addition to these, the supply and demand prediction unit 710 in the second embodiment calculates a possible power supply fluctuation amount DSPC (not shown) and a possible power demand fluctuation amount DDMC (not shown), and transmits them to the external communication unit 730. The possible power supply fluctuation amount DSPC and the possible power demand fluctuation amount DDMC are information including, for example, the date on which the power supply and demand can be fluctuated, the time slot on which the power supply and demand can be fluctuated, the power type indicating the type of fluctuating power, the power source type, the base ID for fluctuating the power supply and demand, the amount of power supply and demand that can be adjusted as an upward DR (Demand Response) or downward DR, and the amount of power supply and demand that can be adjusted by fluctuations in the supply prediction value DSPLY and the demand prediction value DEDM.

[0091] Furthermore, in this embodiment, when the external communication unit 730 receives the possible power supply fluctuation amount DSPC and the possible power demand fluctuation amount DDMC from the supply and demand prediction unit 710, it transmits these data to the overall management system 60. The function of the autonomous decentralized recovery unit 800 (see FIG. 6) is the same as that of the first embodiment. Also, the recovery processing procedure in the event of a failure in the system having the overall management unit 600 and in communication between the system and the base system 10 is the same as that of the first embodiment (see FIGS. 7 to 9).

[0092] FIG. 11 is a block diagram of the overall management unit 600-A in the second embodiment. The overall management unit 600-A of the second embodiment, like that of the first embodiment (see FIG. 4), includes an overall supply and demand planning unit 610, a market trading unit 620, an alive monitoring unit 630, and an external communication unit 640. Furthermore, the overall management unit 600-A of the present embodiment includes a base failure response unit 650.

[0093] The overall supply and demand planning unit 610 has the same functions as those in the first embodiment. Furthermore, when the overall supply and demand planning unit 610 in this embodiment receives a supplementary supply and demand plan for a failure in the base system 10 from the base failure response unit 650, it corrects the power supply and demand plan data DPLN managed in a device having a power supply and demand management function, and transmits the corrected power supply and demand plan data DCPLN to the external communication unit 640.

[0094] The market trading unit 620 also has the same functions as those in the first embodiment. Furthermore, when the market trading unit 620 in this embodiment receives a market trading plan related to the corrected power supply and demand plan data DCPLN, it makes a bid and a contract in the market, and transmits the results to the overall supply and demand planning unit 610.

[0095] The alive monitoring unit 630 also has the same functions as in the first embodiment. Furthermore, when the alive monitoring unit 630 in this embodiment detects a failure in any of the base systems 10, it transmits base failure detection information indicating the details of the failure to the base failure response unit 650. The external communication unit 640 also has the same functions as in the first embodiment. Furthermore, when the external communication unit 640 in this embodiment receives corrected power supply and demand plan data DCPLN from the overall supply and demand plan unit 610, it transmits the corrected power supply and demand plan data DCPLN to the base system 10. Furthermore, when the external communication unit 640 receives the possible power supply fluctuation amount DSPC and the possible power demand fluctuation amount DDMC from the base system 10, it transmits these to the base failure response unit 650.

[0096] The base failure response unit 650 modifies the power supply and demand plan data DPLN based on the base failure detection information from the alive monitoring unit 630. For example, when base failure detection information related to a failure in a certain base system 10 is received, the unit modifies the power supply and demand plan data DPLN of the other base systems 10 so as to compensate for the planned supply and demand of that base system 10. Here, the base system 10 whose power supply and demand plan data DPLN is modified belongs to the same group (balancing group) as the failed base system 10, for which the difference in the power supply and demand plan data DPLN is calculated. Furthermore, when the unit receives the possible power supply fluctuation amount DSPC or the possible power demand fluctuation amount DDMC of each base system 10 from the external communication unit 640, the unit stores and holds the contents in an auxiliary storage device.

[0097] FIG. 12 is a flowchart showing an example of a base failure handling routine in the second embodiment. This routine is executed in the overall management device 61 having the overall management section 600 and the local management device 11. 12, when the processing proceeds to step S32, the alive / dead monitoring unit 630 transmits an alive / dead monitoring message DLDM to all base systems 10 belonging to the base group that it manages in order to monitor the alive / dead status of the base systems 10 in the base group that it manages. Next, when the processing proceeds to step S34, the alive / dead monitoring unit 630 determines whether or not a response to the alive / dead monitoring message DLDM has been received within a predetermined time from all base systems 10 that belong to the base group that it manages. If the determination in step S34 is "Yes," the processing returns to step S32, and the alive / dead monitoring unit 630 continues monitoring the alive / dead status of the base systems 10.

[0098] On the other hand, if no response is received within the predetermined time from at least one base system 10 belonging to the base group, the result in step S34 is "No," and the process proceeds to step S36. In this case, a failure has occurred in the base system 10 that did not respond. Hereinafter, the base system 10 in which the failure has occurred will be referred to as the failed base system 10-f (not shown). Furthermore, the amount of power that a base system 10-k (1≦k≦5) planned to supply to other base systems 10 will be referred to as the power supply plan amount DSPN-k (not shown), and the amount of power that it planned to receive from other base systems 10 will be referred to as the power demand plan amount DDMN-k (not shown). The power supply plan amount DSPN and the power demand plan amount DDMN are data included in the above-mentioned power supply and demand plan data DPLN.

[0099] In step S36, the alive monitoring unit 630 initializes the compensation plan to start compensation processing for the power supply plan amount DSPN-f and the power demand plan amount DDMN-f of the failed base system 10-f. The alive monitoring unit 630 also notifies the base failure response unit 650 of the failed base system 10-f. Next, the overall management unit 600 executes the processing of steps S38 to S42 and the processing of steps S44 to S48 in parallel.

[0100] First, in step S38, the base failure response unit 650 determines whether the power supply plan amount DSPN-f in the failed base system 10-f is sufficient. That is, it determines whether the required power can be accommodated by the power supply plan amount DSPN of the base systems 10 other than the failed base system 10-f. If the determination in step S38 is "No," the processing proceeds to step S40, and the base failure response unit 650 determines whether the remaining amount of the power supply fluctuation allowable amount DSPC of the base system 10 that can be used for compensation is "0."

[0101] If there is a possible power supply variation amount DSPC available for compensation, the determination in step S40 is "No," and the process proceeds to step S42. Here, the base failure response unit 650 uses the possible power supply variation amount DSPC to compensate for the power supply of the failed base system 10-f. That is, the base failure response unit 650 updates the power supply plan amount DSPN of each base system 10 so that all or part of the power supply plan amount DSPN assigned to the failed base system 10-f is compensated for by another base system 10. The amount of power used for compensation is excluded from the possible power supply variation amount DSPC and is made unavailable for use in additional compensation plans. Then, the process returns to step S38.

[0102] If the power supply plan amount DSPN of the failed base system 10-f is satisfied, the determination in step S38 is "Yes," and the base failure response unit 650 completes the creation of the compensation plan for the power supply plan. If there is no power supply fluctuation amount DSPC available for compensation, the determination in step S40 is "Yes," and in this case too, the base failure response unit 650 completes the creation of the compensation plan for the power supply plan.

[0103] Furthermore, after the processing of step S36 ends, when the processing proceeds to step S44, the base failure response unit 650 determines whether the planned power demand amount DDMN-f in the failed base system 10-f is satisfied. In other words, it determines whether the necessary power can be demanded based on the planned power demand amount DDMN of the base systems 10 other than the failed base system 10-f. If the determination in step S44 is "No," the processing proceeds to step S46, and the base failure response unit 650 determines whether the remaining amount of the possible power demand fluctuation amount DDMC of the base system 10 that can be used for power demand is "0."

[0104] If there is a possible power demand fluctuation amount DDMC available for demand, the determination in step S46 is "No," and the process proceeds to step S48. Here, the base failure response unit 650 uses the possible power demand fluctuation amount DDMC to compensate for the power demand of the failed base system 10-f. That is, the base failure response unit 650 updates the planned power demand amount DDMN of each base system 10 so that all or part of the planned power demand amount DDMN allocated to the failed base system 10-f is compensated for by another base system 10. The amount of power used for compensation is excluded from the planned power demand amount DDMN, and is made unavailable for use in additional compensation plans. Then, the process returns to step S44.

[0105] If the planned power demand amount DDMN of the failed base system 10-f is satisfied, the determination in step S44 is "Yes," and the base failure response unit 650 completes the creation of a compensation plan for the power demand plan. If there is no available power demand fluctuation amount DDMC that can be used for demand, the determination in step S46 is "Yes," and in this case too, the base failure response unit 650 completes the creation of a compensation plan for the power demand plan.

[0106] When the processing of both steps S38 to S42 and steps S44 to S48 is completed, the process proceeds to step S50, where the base failure response unit 650 transmits compensation plans for both the power supply plan and the power demand plan to the overall supply and demand planning unit 610. Having received the compensation plans, the overall supply and demand planning unit 610 updates the power supply and demand plan data DPLN of each base system 10 and transmits the updated power supply and demand plan data DPLN to each base system 10 via the external communication unit 640. Furthermore, the overall supply and demand planning unit 610 also transmits any compensation plans that require market trading to the market trading unit 620. This completes the processing of this routine.

[0107] In the example shown in FIG. 12, the compensation process (steps S36 to S50) for the power supply and demand plan data DPLN is immediately initiated based on the failure to receive a response to the health monitoring message DLDM. However, the compensation process may be delayed until a further condition is satisfied. This is because, even if the communication function of the faulty base system 10-f is impaired, the subordinate equipment control device 13 and power supply and demand facility 12 may function normally, and compensation process may not be necessary. For example, the administrator of the faulty base system 10-f may be contacted by telephone or the like to confirm the fault status of the faulty base system 10-f. Here, confirmation of the fault status of the faulty base system 10-f may be automated by providing a device that can replace the above-mentioned telephone contact. Then, when a fault actually occurs in the equipment control device 13-f and the power supply and demand facility 12-f in the faulty base system 10-f and the power supply and demand plan data DPLN-f cannot be executed, the overall management unit 600 may determine to execute compensation process.

[0108] 12, the power supply and demand plan data DPLN can be modified to compensate for the power supply and demand plan data DPLN-f in the failed base system 10-f by utilizing the possible power supply fluctuations DSPC and possible power demand fluctuations DDMC from each base system 10 as much as possible. In other words, when a base system 10 or control device fails, the difference between the difference in the power supply and demand plan data DPLN and the actual supply and demand can be reduced. The overall management unit 600 uses the possible power supply fluctuations DSPC and possible power demand fluctuations DDMC of the non-failed base systems 10 to modify the power supply and demand plan data DPLN to compensate for the power supply and demand plan data DPLN in the failed base system 10-f. This reduces the difference between the overall power supply and demand plan data DPLN and the actual supply and demand.

[0109] [Third embodiment] Next, a power supply and demand management system according to a third embodiment will be described. The configuration of the power supply and demand management system according to the third embodiment is the same as the power supply and demand management system 100 according to the first embodiment (FIGS. 1 to 10), except for the points described below. In the description of each embodiment, parts corresponding to parts in the other embodiments described above are given the same reference numerals, and their description may be omitted.

[0110] In this embodiment as well, if a failure occurs in the system having the overall management unit 600 or if a communication failure occurs between the overall management system 600 and the base system 10, the base management device 11 activates the overall management unit 600. At that time, in order to reduce the calculation processing load of the overall management unit 600 and achieve efficient power supply and demand, in this embodiment, the operation of the overall supply and demand planning unit 610 of the overall management unit 600 is replaced by an approximation model.

[0111] For example, if the computational resources of the base management device 11 are smaller than those of the overall management system 60, it may be difficult to create the overall power supply and demand plan data DPLN even if the base management device 11 starts up the overall management unit 600 using the recovery method in the first embodiment. Therefore, in this embodiment, the overall management unit 600 started up by the base management device 11 is one to which an approximation model is applied.

[0112] The configuration of the power supply and demand management system 100 in this embodiment is the same as that in the first embodiment (see FIG. 1). The hardware configurations of the overall management device 61 and the base management device 11 are also the same as those in the first embodiment (see FIG. 3). The functional configuration of the base management unit 700 is also the same as that in the first embodiment (see FIG. 5). However, the external communication unit 730 in this embodiment receives approximate model data DMDL (not shown) indicating an approximate model of the overall supply and demand planning operation of the overall management unit 600 from the overall management system 60. Then, the external communication unit 730 transmits the received approximate model data to the autonomous decentralized recovery unit 800.

[0113] The functional configuration of the autonomous decentralized recovery unit 800 is the same as that of the first embodiment (see FIG. 6), but the communication unit 870 can also send and receive data to and from the overall management unit startup unit 860. As a result, the communication unit 870 sends the approximate model data DMDL received from the external communication unit 640 to the overall management unit startup unit 860. The overall management unit startup unit 860 stores and holds the approximate model data DMDL in an auxiliary storage device. If approximate model data DMDL has already been held, it is updated to the newly received approximate model data DMDL.

[0114] When the overall management unit startup unit 860 receives a startup command from the startup function determination unit 850, it starts up a lightweight overall management unit 600 in which the planning operation of the overall supply and demand plan unit 610 for creating the power supply and demand plan data DPLN is replaced by an approximation model. The recovery process procedure for the approximation model when a failure occurs in the system having the overall management unit 600 and in communication between the system and the base system 10 is the same as the processes shown in Figures 7 to 9.

[0115] FIG. 13 is a block diagram of the overall management unit 600-A in the third embodiment. Similar to that of the first embodiment (see FIG. 4), the overall management unit 600-A of the third embodiment includes an overall supply and demand planning unit 610, a market trading unit 620, a health monitoring unit 630, and an external communication unit 640, as well as an approximate model management unit 660. The functions of the overall supply and demand planning unit 610, the market trading unit 620, and the health monitoring unit 630 are similar to those of the first embodiment.

[0116] The approximation model management unit 660 constructs and manages an approximation model of the operation of the overall supply and demand planning unit 610 to formulate the power supply and demand plan data DPLN, and distributes the constructed approximation model as approximation model data DMDL to the base system 10. The approximation model management unit 660 constructs an approximation model for calculating the power supply and demand plan data DPLN using the past power supply and demand plan data DPLN, the past power interchange availability information DICT, the past power interchange request information DDMD, and the past power supply and demand record data DACV at predetermined intervals, for example, every other day.

[0117] For example, it is constructed so that the power interchange availability information DICT, power interchange request information DDMD, and power supply and demand record data DACV are input, and the power supply and demand plan data DPLN at that time is output. By applying, for example, a decision tree, linear regression, or neural network as an approximation model, it is possible to model the relationship between the power interchange availability information DICT, power interchange request information DDMD, and power supply and demand plan data DPLN.

[0118] The data used to construct the model may include all of the stored data, or the data to be used may be limited according to predetermined conditions. The approximate model data DMDL may be constructed so as to include data that can be obtained by the administrator of the power supply and demand management system 100, such as past weather information, past weather forecasts, weather forecasts at the time the power supply and demand plan data DPLN is formulated, power generation locations, years of power generation, and power generation sources. Having constructed the approximate model data DMDL, the approximate model management unit 660 records the approximate model in the auxiliary storage device 65 (see FIG. 3). Furthermore, the approximate model management unit 660 transmits the approximate model data DMDL to the external communication unit 640 via the communication network 110 for distribution to the base systems 10 under its control.

[0119] The external communication unit 640 has the same functions as those in the first embodiment (see FIG. 4). Furthermore, when the external communication unit 640 receives approximate model data DMDL from the approximate model management unit 660, it transmits the approximate model data DMDL to all of the base systems 10 under its control. When a failure occurs in the system having the overall management unit 600 or in communication between that system and the base system 10, the base management device 11 of the base system 10 that receives and stores the approximate model performs the recovery operation in the first embodiment and starts up a lightweight overall management unit 600 substituted with the approximate model data DMDL.

[0120] As a result, the base management device 11 can create the power supply and demand plan data DPLN using few resources without performing complex optimization calculations by inputting the power interchange availability information DICT and power interchange request information DDMD received from the base systems 10 under its jurisdiction into the approximation model. In this way, when a failure occurs in the system having the overall management unit 600 or a communication failure occurs between the overall management unit 60 and the base systems 10 and the overall management unit 600 is started in the base management device 11, the calculation processing of the overall management unit 600 can be reduced and efficient power supply and demand can be achieved.

[0121] That is, the overall management system 60 can construct approximate model data DMDL that approximates the operation of formulating the power supply and demand plan data DPLN and distribute it to the base system 10. Then, the base management device 11 of the base system 10 starts up a lightweight overall management unit 600 that includes an approximate model based on the distributed approximate model data DMDL. This makes it possible to formulate the power supply and demand plan data DPLN that is computationally lightweight and efficient. In particular, when the calculation resources of the base management device 11 are scarce compared to the calculation resources of the overall management device 61, it becomes possible for the base management device 11 to also formulate the power supply and demand plan data DPLN.

[0122] [Variations] The present invention is not limited to the above-described embodiments and various modifications are possible. The above-described embodiments are provided as examples to facilitate understanding of the present invention and are not necessarily limited to those including all of the described configurations. Furthermore, it is possible to replace part of the configuration of one embodiment with the configuration of another embodiment, or to add the configuration of another embodiment to the configuration of one embodiment. It is also possible to delete part of the configuration of each embodiment, or to add or replace other configurations. Furthermore, the control lines and information lines shown in the figures are those considered necessary for explanation, and do not necessarily represent all control lines and information lines necessary for the product. In reality, it is acceptable to consider that almost all components are interconnected. Possible modifications of the above-described embodiments include, for example, the following:

[0123] (1) Since the hardware of the overall management device 61, the base management device 11, etc. in the above embodiment can be realized by a general computer, the processes corresponding to the above-mentioned block diagrams and flowcharts, and programs for executing the various processes described above may be stored in a storage medium (a computer-readable storage medium on which a program is recorded) or distributed via a transmission path.

[0124] (2) In the above embodiment, the processes corresponding to the block diagrams and flowcharts, as well as the various other processes described above, are described as software processes using programs. However, some or all of these processes may be replaced with hardware processes using an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array), etc.

[0125] (3) The various processes executed in the above embodiment may be executed by a server computer via a network (not shown), and the various data stored in the above embodiment may also be stored in the server computer.

[0126] [Effects of the embodiment] According to each of the above-described embodiments, each base management device 11 is equipped with an autonomous distributed recovery unit 800, and the autonomous distributed recovery unit 800 is equipped with a network reconfiguration unit 820 that reconfigures base groups GB, GC consisting of multiple base systems 10 that can communicate with each other when a failure occurs in the overall management system 60 or the first communication network (110) and the overall management system 60 becomes unable to manage the power supply and demand between the multiple base systems 10, an overall management startup destination selection unit 840 that selects one of the base management devices 11 in the multiple base systems 10 belonging to the base groups GB, GC as the startup destination for the new overall management unit 600, and an overall management unit startup unit 860 that starts the overall management unit 600 in the selected base management device 11.

[0127] As a result, if a failure occurs in the overall management system 60 having the overall management unit 600-A, or if a communication failure occurs between the overall management system 60 and the base systems 10, appropriate power supply and demand management can be achieved through cooperation between the overall management unit 600 and the multiple base systems 10. That is, the base management devices 11 that detect the failure in the overall management unit 600-A communicate with each other in an autonomous and decentralized manner to reconfigure the communication connection relationships, and start up a new overall management unit 600 in one of the base management devices 11 in the reconfigured group, thereby restoring power supply and demand management through cooperation between the newly started overall management unit 600 and the other base systems 10.

[0128] Furthermore, by restoring the overall management unit 600, it becomes possible to appropriately control the entire system in response to changes in the state of the power supply and demand equipment 12, etc., after a failure occurs in the overall management system 60. Furthermore, by recursively executing the recovery procedures shown in each embodiment again in the restored overall management unit 600 and the multiple base systems 10, recovery can be achieved even if a failure occurs again.

[0129] Furthermore, it is more preferable that the autonomous decentralized recovery unit 800 further includes a score calculation unit 830 that calculates a score indicating the priority of starting up the overall management unit 600 for the base system 10 to which the corresponding base management device 11 belongs, and the overall management startup selection unit 840 selects, based on the score, one of the base management devices 11 belonging to the base groups GB and GC that will start up the overall management unit 600. This makes it possible to start up the overall management unit 600 in the most appropriate one of the multiple base management devices 11 based on the score.

[0130] Furthermore, it is more preferable that the score calculation unit 830 calculates the score based on the computational resources of the base management device 11, the type of power supply and demand equipment 12 in the base system 10, or the quantity of power supply and demand equipment 12 in the base system 10. This makes it possible to select the base management device 11 that will activate the overall management unit 600 depending on the configuration of the power supply and demand equipment 12.

[0131] Furthermore, it is more preferable that the plurality of site management devices 11 communicate with each other via the second communication network (120), and the score calculation unit 830 calculates the score based on the congestion state in the second communication network (120). This allows the site management device 11 with the least congestion state to be selected as the startup destination of the overall management unit 600.

[0132] Furthermore, it is more preferable that the plurality of site management devices 11 communicate with each other via the second communication network (120), and the score calculation unit 830 calculates the score based on the connection relationship of the plurality of site management devices 11 to the second communication network (120). This allows, for example, a site management device 11 that can maintain a good communication state to be selected as the startup destination of the overall management unit 600.

[0133] Furthermore, it is more preferable that the autonomous decentralized recovery unit 800 further includes an activation function determination unit 850 that determines the functions that should be provided to the overall management unit 600 to be activated, depending on the number of base systems 10 belonging to the base groups GB and GC. This allows the appropriate functions to be provided to the overall management unit 600 to be activated, depending on the number of base systems 10 in the base groups GB and GC.

[0134] Furthermore, the autonomous distributed recovery unit 800 in each base management device 11 further includes a score calculation unit 830 that calculates a score indicating the priority of starting up the overall management unit 600 for the base system 10 to which the corresponding base management device 11 belongs, and an activation function determination unit 850 that determines the functions that the activated overall management unit 600 should have, depending on the number of base systems 10 that belong to the base groups GB and GC, and it is more preferable that the overall management activation destination selection unit 840 selects, based on the score, one of the base management devices 11 that belong to the base groups GB and GC that will start up the overall management unit 600. This makes it possible to start up the overall management unit 600 in the most appropriate one of the multiple base management devices 11 based on the score, and further to provide appropriate functions to the activated overall management unit 600.

[0135] Furthermore, it is more preferable that the base management device 11 that has started up the overall management unit 600 creates power supply and demand plan data DPLN that indicates the planned contents of power supply and demand in the base groups GB, GC to which the base management device 11 belongs, using the started overall management unit 600. This allows power supply and demand to be realized in the base groups GB, GC based on the power supply and demand plan data DPLN.

[0136] Furthermore, as in the third embodiment, it is more preferable that the overall management unit (600-A) in the overall management system 60 further includes an approximation model management unit 660 that generates approximate model data DMDL representing a model for constructing the power supply and demand plan data DPLN based on the power supply and demand relationships in the multiple base systems 10, and the overall management unit 600 started up in the base management device 11 constructs the power supply and demand plan data DPLN for the corresponding base groups GB, GC based on the approximate model data DMDL. This allows the overall management unit 600 to be started up in the base management device 11 even when the base management device 11 has few calculation resources.

[0137] Furthermore, it is more preferable that the approximation model management unit 660 constructs the approximation model data DMDL based on past results of the power interchangeable information DICT that indicates the amount of power that each base system 10 can interchange with other base systems 10, past results of the power interchange request information DDMD that indicates the amount of power that each base system 10 has requested to be interchanged with other base systems 10, past weather information, past results of the power supply and demand result data DACV that indicates the actual values ​​of the power generated and consumed by each base system 10, and past results of the power supply and demand plan data DPLN that indicates the planned values ​​of the power generated and consumed by each base system 10. In this way, the approximation model data DMDL can be constructed based on various results.

[0138] In addition, in each of the above-described embodiments, a plurality of base systems 10 each including a plurality of power supply and demand facilities 12 and a base management device 11 that manages the supply or demand of power via a power network 130 of the power supply and demand facilities 12; an overall management system (60) including an overall management unit (600) that manages the supply and demand of electricity between a plurality of base systems (10) via a first communication network (110); A pre-designated one of the multiple base management devices 11 can be modified to include an autonomous distributed recovery unit 800 that activates a new overall management unit 600 when a failure occurs in the overall management system 60 or the first communication network (110) and the overall management system 60 becomes unable to manage the power supply and demand between the multiple base systems 10. This allows the new overall management unit 600 to be started up quickly.

[0139] Furthermore, according to another aspect, the second embodiment described above is a plurality of base systems 10 each including a plurality of power supply and demand facilities 12 and a base management device 11 that manages the supply or demand of power via a power network 130 of the power supply and demand facilities 12; an overall management system (60) including an overall management unit (600) that generates power supply and demand plan data (DPLN) that defines a power supply and demand plan between a plurality of base systems (10) via a first communication network (110); The overall management system 60 is equipped with a base failure response unit 650 that, in the event of a failure base system 10-f, which is a base system 10 that has experienced a disruption in power supply and demand, modifies the power supply and demand plan data DPLN so that the power supply and demand in the failed base system 10-f is compensated for by other base systems 10 that are not experiencing a failure. This makes it possible to suppress the impact on the power supply and demand even when a failure occurs in the base system 10-f.

[0140] Furthermore, it is more preferable that the overall management unit 600 has a function of receiving, from each base system 10, the variable power supply amount DSPC, which is the variable amount of power supplied, or the variable power demand amount DDMC, which is the variable amount of power demanded, and that the base fault response unit 650 corrects the power supply and demand plan data DPLN based on the variable power supply amount DSPC or the variable power demand amount DDMC. This allows the power supply and demand plan data DPLN to be corrected within the ranges allowed by the power supply fluctuation potential DSPC and the power demand fluctuation potential DDMC.

[0141] Furthermore, it is more preferable that the base failure response unit 650 starts correcting the power supply and demand plan data DPLN based on the notification from the failed base system 10-f. This makes it possible to prevent the power supply and demand plan data DPLN from being revised when such revision is unnecessary. [Explanation of symbols]

[0142] 10 base systems 10-f Disaster Management System 11 Base management device 12 Electricity supply and demand facilities 60 Overall Management System 100 Electricity supply and demand management system 110 Communication Network (First Communication Network) 120 Communication Network (Second Communication Network) 130 Power Network 600 General management department 650 Base Failure Response Department 660 Approximation Model Management Unit 800 Autonomous Distributed Recovery Unit (Autonomous Distributed Recovery Device) 820 Network reconfiguration unit (network reconfiguration process) 830 Score Calculation Unit 840 Overall management startup destination selection section (Overall management startup destination selection process) 850 Startup function determination section 860 Overall management department startup part (Overall management department startup process) GB,GC base group DACV Electricity Supply and Demand Performance Data DDMC Power demand fluctuation potential DDMD power interchange request information DICT power flexibility information DMDL Approximation Model Data DPLN Power Supply and Demand Planning Data DSPC Power supply fluctuation potential

Claims

1. a plurality of base systems each including a plurality of power supply and demand facilities and a base management device that manages the supply or demand of power via a power network of the power supply and demand facilities; an overall management system including an overall management unit that generates, via a first communication network, power supply and demand plan data that defines a power supply and demand plan between the plurality of base systems; Each of the base management devices includes an autonomous decentralized recovery unit, The autonomous decentralized recovery unit a network reconfiguration unit that reconfigures a base group including a plurality of base systems that can communicate with each other when the overall management system or the first communication network has failed and the overall management system is unable to manage the power supply and demand between the plurality of base systems; an overall management startup destination selection unit that selects one of the base management devices in the plurality of base systems that belong to the base group as a new startup destination of the overall management unit; an overall management unit starting unit that starts the overall management unit in the selected site management device; An electric power supply and demand management system characterized by the above.

2. The autonomous decentralized recovery unit a score calculation unit that calculates a score indicating a priority of starting up the overall management unit for the base system to which the corresponding base management device belongs; The overall management startup destination selection unit selects, from the base management devices belonging to the base group, one that will start the overall management unit based on the score. The power supply and demand management system according to claim 1 .

3. The score calculation unit calculates the score based on the computational resources of the base management device, the type of the power supply and demand equipment in the base system, or the quantity of the power supply and demand equipment in the base system. The power supply and demand management system according to claim 2 .

4. the plurality of site management devices communicate with each other via a second communication network, The score calculation unit calculates the score based on a congestion state in the second communication network. The power supply and demand management system according to claim 2 .

5. the plurality of site management devices communicate with each other via a second communication network, The score calculation unit calculates the score based on a connection relationship between the plurality of site management devices and the second communication network. The power supply and demand management system according to claim 2 .

6. The autonomous decentralized recovery unit The system further includes an activation function determination unit that determines functions that should be included in the overall management unit to be activated depending on the number of the base systems that belong to the base group.

2. The power supply and demand management system according to claim 1.

7. The autonomous decentralized recovery unit in each of the base management devices a score calculation unit that calculates a score indicating a priority of starting up the overall management unit for the base system to which the corresponding base management device belongs; a start function determination unit that determines functions that should be included in the overall management unit to be started according to the number of the base systems that belong to the base group; The overall management startup destination selection unit selects, from the base management devices belonging to the base group, one that will start the overall management unit based on the score.

2. The power supply and demand management system according to claim 1.

8. The base management device that has started up the overall management unit uses the started overall management unit to create the power supply and demand plan data that indicates the planned content of power supply and demand in the base group to which the base management device belongs.

2. The power supply and demand management system according to claim 1.

9. the overall management unit in the overall management system further includes an approximation model management unit that generates approximation model data representing a model for constructing the power supply and demand plan data based on power supply and demand relationships in the plurality of base systems; The overall management unit activated in the base management device constructs the power supply and demand plan data for the corresponding base group based on the approximate model data. The power supply and demand management system according to claim 1 .

10. The approximation model management unit constructs the approximation model data based on past results of power interchangeable information indicating the amount of power that each of the base systems can interchange with other base systems, past results of power interchange request information indicating the amount of power that each of the base systems has requested to be interchanged with other base systems, past weather information, past results of power supply and demand result data indicating actual values ​​of power generated and consumed by each of the base systems, and past results of power supply and demand plan data indicating planned values ​​of power generated and consumed by each of the base systems. The power supply and demand management system according to claim 9 .

11. a plurality of base systems each including a plurality of power supply and demand facilities and a base management device that manages the supply or demand of power via a power network of the power supply and demand facilities; an overall management system including an overall management unit that generates, via a first communication network, power supply and demand plan data that defines a power supply and demand plan between the plurality of base systems; Each of the base management devices is an electric power supply and demand management method executed in an electric power supply and demand management system including an autonomous decentralized recovery unit, The autonomous decentralized recovery unit a network reconfiguration process for reconfiguring a base group having a plurality of base systems that can communicate with each other when the overall management system or the first communication network has failed and the overall management system is unable to manage the power supply and demand between the plurality of base systems; an overall management startup destination selection step of selecting one of the base management devices in the plurality of base systems belonging to the base group as a new startup destination of the overall management unit; and executing an overall management unit starting step of starting the overall management unit in the selected local management device. A power supply and demand management method comprising:

12. an autonomous decentralized recovery device provided in each of the base management devices of a power supply and demand management system, the autonomous decentralized recovery device comprising: a plurality of base systems each including a plurality of power supply and demand facilities and a base management device that manages power supply or demand via a power network of the power supply and demand facilities; and an overall management system including an overall management unit that generates power supply and demand plan data that defines a power supply and demand plan between the plurality of base systems via a first communication network, a network reconfiguration unit that reconfigures a base group including a plurality of base systems that can communicate with each other when the overall management system or the first communication network has failed and the overall management system is unable to manage the power supply and demand between the plurality of base systems; an overall management startup destination selection unit that selects one of the base management devices in the plurality of base systems that belong to the base group as a new startup destination of the overall management unit; an overall management unit starting unit that starts the overall management unit in the selected site management device; An autonomous distributed recovery device characterized by:

Images