Control device and control method

Abstract

We will respond to disaster recovery (DR) requests by making more reliable use of resources from the time of agreement to execution. [Solution] A management device for managing multiple resources, which acquires information on the status of the multiple resources, determines whether it can meet the power conditions of the DR at a first timing after the DR agreement and before the execution of the DR, determines whether it can meet the power conditions of the DR at a second timing after the first timing and before the execution of the DR, determines whether it can meet the power conditions of the DR during the execution of the DR, if it is determined that it cannot meet the power conditions of the DR, performs a process to supplement with an external resource different from the multiple resources, if it is determined that it cannot meet the power conditions of the DR, re-secures a resource among the multiple resources that is scheduled to be used, and if it is determined that it cannot meet the power conditions of the DR, changes the power usage amount of the multiple resources that are currently in operation.

Description

Technical Field

[0001] The present invention relates to a technology for managing resources used in demand response.

Background Art

[0002] In recent years, research and development related to resource utilization that contributes to energy efficiency has been carried out to ensure that more people can access affordable, reliable, sustainable and advanced energy. Patent Document 1 proposes a technology for managing resources utilized for demand response (DR), and discloses a system that uses a storage battery provided in a base station. In the system of Patent Document 1, after selecting a storage battery (base station) corresponding to DR, if it is detected that the response cannot be made, compensation by another base station or compensation by the selected base station is selectively controlled.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Resources such as mobility equipped with secondary batteries tend to have highly variable usage opportunities, and resources that were scheduled to be used in DR may not be available. It is required to manage resources more reliably from the agreement of DR to the execution of DR.

[0005] An object of the present invention is to provide a technology for responding to demand response by utilizing resources more reliably from the agreement of DR to the execution of DR.

Means for Solving the Problems

[0006] According to the present invention, A management device for managing multiple resources that respond to demand response, An acquisition means for acquiring information regarding the status of the aforementioned multiple resources, After the agreement on the demand response, and at a first timing before the execution of the demand response, a first determination means determines, based on the information, whether or not it is possible to respond to the power conditions of the demand response, After the first timing and before the execution, a second determination means determines, based on the information, whether or not it can respond to the power conditions of the demand response. During the execution of the demand response, a third determination means determines, based on the information, whether or not it is possible to respond to the power conditions of the demand response, If the first determination means determines that it is not possible to meet the power conditions of the demand response, the first processing means performs a process of supplementing with an external resource different from the multiple resources, If the second determination means determines that it is not possible to meet the power conditions of the demand response, the second processing means re-secures the resource scheduled for operation from among the multiple resources, The system includes a third processing means that, if the third determination means determines that it is not possible to meet the power conditions of the demand response, changes the power usage amount of multiple resources currently in operation. A management device characterized by the above is provided. [Effects of the Invention]

[0007] According to the present invention, it is possible to provide a technology that can respond to disaster recovery (DR) by more reliably utilizing resources from the agreement on DR to the execution of DR. [Brief explanation of the drawing]

[0008] [Figure 1] A schematic diagram of a management system using a management device according to one embodiment of the present invention. [Figure 2] Diagram illustrating the power transmission system in the management system shown in Figure 1. [Figure 3]A diagram illustrating an example of the structure of information registered in a database. [Figure 4] Block diagram of an in-vehicle terminal. [Figure 5] Block diagram of a mobile device. [Figure 6] (A) and (B) are flowcharts illustrating examples of database update processes. [Figure 7] A diagram illustrating the general process from contract execution to execution of a Dispute Resolution (DR) transaction. [Figure 8] A flowchart illustrating an example of the process performed by the management device. [Figure 9] A flowchart illustrating an example of the process performed by the management device. [Figure 10] (A) to (D) are flowcharts showing examples of processes performed by the management device. [Modes for carrying out the invention]

[0009] The embodiments will be described in detail below with reference to the attached drawings. Note that the following embodiments do not limit the invention as defined in the claims, and not all combinations of features described in the embodiments are essential to the invention. Two or more features from the multiple features described in the embodiments may be combined arbitrarily. Furthermore, identical or similar configurations will be given the same reference numeral, and redundant descriptions will be omitted.

[0010] <System Overview> Figure 1 is a schematic diagram of a management system 1 using a management device 2 according to one embodiment of the present invention. The management system 1 manages resources 3, which are distributed energy resources, using the management device 2, and utilizes them for demand response (DR) to maintain the balance of power supply and demand. The management device 2 is a server that functions as an aggregator that utilizes resources 3 via a communication network such as the internet.

[0011] In the present embodiment, the resource 3 corresponding to DR is a battery-equipped vehicle represented by an electric vehicle, a hybrid vehicle, or an electric motorcycle, and includes an in-vehicle terminal 30. The user 5 of the resource 3 is a registered user who has previously permitted the operator of the management device 2 to operate the resource 3 for DR, and the resource 3 is a registered resource. The registered resource group 11 is a group of a plurality of resources 3 for which power operation has been permitted in advance in this manner. The management device 2 is capable of wireless communication with the in-vehicle terminal 30 of the resource 3 and the mobile terminal 4 via a communication network.

[0012] The management device 2 basically utilizes the resources 3 included in the registered resource group 11 to participate in DR. However, in a predetermined case, the resources 6 and 7 belonging to the external resource group 12 may also be utilized. The external resource group 12 is a resource whose operation has not been permitted in advance to the operator of the management device 2. As an example, the resource 6 is a battery-equipped vehicle represented by a hybrid vehicle or an electric motorcycle, and the resource 7 is a residence provided with a solar panel. When utilizing such an external resource group 12, the management device 2 obtains permission individually, or requests power supply and demand from another aggregator via a server 8 operated by the aggregator to respond to DR.

[0013] The management device 2 is a server computer including a processing unit 21, a storage unit 22, and a communication unit 23. The processing unit 21 is a processor represented by a CPU, and executes a program stored in the storage unit 22. The storage unit 22 is a storage device such as a RAM, a ROM, or a hard disk, and stores programs executed by the processing unit 21 and various types of data. In the storage unit 22, a resource database 221 in which information on registered resources is accumulated, and a DR database 222 in which information on DR is accumulated are constructed. The communication unit 23 includes a communication interface that communicates with an external communication terminal via a communication network.

[0014] Figure 2 is an explanatory diagram of a power transmission system in the management system 1. The electric utility 100 is, for example, a grid power utility having a large-scale power plant, and can perform power sales to consumers and surplus power purchase. The illustrated electric utility 100 is also used as a concept referring to facilities such as distribution facilities, power transmission facilities, and substation facilities that constitute a power system together with the power network 100a.

[0015] Each resource 3 belonging to the registered resource group 11 is, as an example, connected to the power network 100a via the power facility 102 in the residence 101 of its user 5. The resource 3 is connected to the power facility 102 via a detachable power cable (charging cable) 103 that can be attached to and detached from the resource 3. The power facility 102 includes, for example, a distribution board, a relay, and a controller, and relays charging and discharging between the resource 3 connected to the power cable 103 and the power network 100a. When the resource 3 is connected to the power cable 103, the in-vehicle terminal 30 can perform control such as charging the battery included in the resource 3 with power supplied from the power network 100a and discharging power from the battery to the power network 100a. Accordingly, the management device 2 instructs the in-vehicle terminal 30 to perform charging and discharging via communication, so that the resource 3 can be utilized for DR via the power network 100a.

[0016] Each resource 6 belonging to the external resource group 12 is also, as an example, connected to the power network 100a via the power facility 112 in the residence 111 of its user. The resource 6 is connected to the power facility 112 via a detachable cable 113 that can be attached to and detached from the resource 6. The resource 7 is also connected to the power network 100a via the power facility 7a in the residence.

[0017] <Database> Examples of information stored in the resource database 221 and the DR database 222 of the management device 2 are described. Figure 3 shows a configuration example of a record 221a stored in the resource database 221 and a configuration example of a record 222a stored in the DR database 222.

[0018] Record 221a is generated for each user 5 and includes "User ID," "User Communication Information," "Planned Usage Information," "Resource ID," "Resource Communication Information," and "Status Information." "User ID" is an identifier that identifies user 5. "User Communication Information" is information necessary for user 5's mobile terminal 4 and the management device 2 to communicate via the communication network, for example, the communication identification number of the mobile terminal 4. "Planned Usage Information" is the date and time information for the period during which user 5 will use resource 3 (date and time information for the period when resource 3 cannot be used for DR) or the date and time information for the period during which resource 3 is permitted to be used for DR.

[0019] The "Resource ID" is an identifier that identifies Resource 3. The "Resource Communication Information" is information necessary for Resource 3 of User 5, identified by the "User ID," and the management device 2 to communicate via the communication network, such as the communication identification number of the in-vehicle terminal 30. The "Status Information" is information regarding the energy storage status and readiness for use of Resource 3, such as the State of Charge (SOC) of Resource 3 and the connection status of the power cable 103 to Resource 3 (it cannot be used if not connected).

[0020] Record 222a is generated for each agreed-upon DR and includes "DRID," "Schedule," "Request Details," "Resource Information," and "Failure Information." "DRID" is an identifier that identifies the DR. "Schedule" is date and time information related to the DR execution period. "Request Details" is information about the power requested in the DR, including whether it is a power supply or demand situation and information such as the maximum power amount. "Resource Information" is information that identifies the group of resources that are planned to be used or are currently being used in the DR. "Failure Information" is information about failures that occurred during the execution of the DR.

[0021] <Device Configuration> Figure 4 is a block diagram of the configuration of the in-vehicle terminal 30 and its surroundings. In this embodiment, the in-vehicle terminal 30 is an ECU that controls the charging and discharging of the battery 35 mounted on resource 3. The in-vehicle terminal 30 is a computer that includes a processing unit 31, a storage unit 32, an input / output interface (I / F) unit 33, and a communication unit 34. The processing unit 31 is a processor, such as a CPU, and executes programs stored in the storage unit 32. The storage unit 32 is a storage device such as RAM, ROM, or hard disk, and stores programs executed by the processing unit 31 and various types of data. The input / output I / F unit 33 relays signals between the in-vehicle terminal 30 and the processing unit 31. The communication unit 34 includes a communication interface that communicates with the management device 2 via a communication network and a communication interface that communicates with the mobile terminal 4.

[0022] The battery 35 is a secondary battery such as a lithium-ion battery, and is a battery that supplies power to the driving source (e.g., a motor) of resource 3. The charge / discharge circuit 36 ​​includes an AC / DC converter, a DC / AC converter, and a control circuit that controls current and voltage. It charges the battery 35 by converting AC power supplied from the power equipment 102 (power grid 100a) of the residence 101 to DC power via a power cable 103 connected to the connector 37, and discharges the DC power stored in the battery 35 back to the power equipment 102 (power grid 100a) by converting it to AC power. The sensor 38 is a sensor that measures the DC current and voltage between the charge / discharge circuit 36 ​​and the battery 35, and can estimate the charge and discharge amounts from its detection results. In other words, the in-vehicle terminal 30 can estimate the state of charge (SOC) of the battery 35 from the detection results of the sensor 38. The estimated SOC can be stored in the memory unit 32.

[0023] The connector 37 includes a connection terminal for power lines connected to the charge / discharge circuit 36 ​​and a connection terminal for communication lines connected to the in-vehicle terminal 30, and the power cable 103 includes power lines and communication lines. The in-vehicle terminal 30 can communicate with the power equipment 102 via the communication lines, and if communication is established, the in-vehicle terminal 30 can determine that the power cable 103 is connected to resource 3. The determination result can be stored in the storage unit 32.

[0024] Figure 5 is a block diagram of the mobile terminal 4. The mobile terminal 4 is a communication terminal that includes a processing unit 41, a storage unit 42, a display unit 43, an input unit 44, and a communication unit 45, and is, for example, a smartphone. The processing unit 41 is a processor, such as a CPU, and executes the program stored in the storage unit 42.

[0025] The memory unit 42 is a memory device such as RAM or ROM. The memory unit 42 also stores application programs (called DR apps) that are convenient for user 5 to participate in the management system 1. The display unit 43 is a device that serves both to display images and to accept input operations from user 5, such as a touch panel. The input unit 44 is a device that accepts touch operations from the user. The communication unit 45 includes a communication interface that communicates with the management device 2 via a communication network, and a communication interface that communicates with the in-vehicle terminal 30.

[0026] <Database Update> By updating the resource database 221, the accumulated information can be kept up-to-date. Figure 6(A) shows an example of processing that the processing unit 21 of the management device 2 periodically executes, and in particular, an example of acquiring vehicle status information from resource 3 and updating the resource database 221. Vehicle status information is the information accumulated in the "status information" of record 221a in Figure 3.

[0027] In step S1, an information provision request is transmitted to the in-vehicle terminal 30. The in-vehicle terminal 30 that has received the provision request transmits various types of information stored in the storage unit 32 back to the management device 2 together with the resource ID. In step S2, the information received from the in-vehicle terminal 30 is acquired as vehicle state information, and in step S3, the "state information" of the corresponding resource 3 is updated. In this way, the "state information" is maintained as the latest information.

[0028] Figure 6(B) shows a processing example of the processing unit 21 of the management device 2 related to the update of the "usage schedule information" of the record 221a in Figure 3. In the case of the present embodiment, the update of the "usage schedule information" is triggered by an update notification from the user 5. The user 5 launches the DR application on the mobile terminal 4 and establishes communication with the management device 2. After that, the user 5 performs an operation of transmitting the usage schedule of the resource 3 or the DR participation permission period input on the DR application to the management device 2. The information input by the user 5 is transmitted to the management device 2 together with the user ID.

[0029] In step S11, the information received from the mobile terminal 4 is acquired as usage schedule information, and in step S12, the "usage schedule information" of the corresponding user 5 is updated. In this way, the "usage schedule information" is maintained as the latest information.

[0030] Note that in the present embodiment, the usage schedule information is transmitted from the mobile terminal 4 to the management device 2, but it may be transmitted from the mobile terminal 4 to the in-vehicle terminal 30 via wireless communication to be stored, and then transmitted from the in-vehicle terminal 30 to the management device 2 in the process of Figure 6(A). In this case, the process of Figure 6(B) is not required.

[0031] <Resource management for DR> An example of the management procedure for resource 3 in response to DR performed by management device 2 will be explained with reference to Figure 7. Figure 7 is a diagram illustrating the overview of the processing content of management device 2 from the agreement to the execution of DR. In the example of Figure 7, the series of responses related to DR are divided chronologically and virtually into a procurement phase, an operational preparation phase, and an operational phase. The procurement phase is the bidding stage for DR products. Once the bid is successful and an agreement is reached, it becomes the operational preparation phase. When an execution command for the agreed-upon DR is issued, it becomes the operational phase.

[0032] When a DR product is contracted, the resources 3 to be used during operation and the amount of electricity used (supply and demand) for each resource 3 are provisionally determined. At the time of contract, the resource 3 to be used is selected from the resources 3 included in the registered resource group 11, and the selection is stored as "resource information" in the DR database. This selection is made based on, for example, the "planned usage information" and "status information" of the resource database 221a, predicting the amount of resources that can be provided and whether or not it is possible to respond to the request for the DR product. In Figure 7, the resources 3 to be used at the time of contract are shown as the provisionally selected resource group 11a from the registered resource group 11.

[0033] The SOC and usage status of Resource 3 will fluctuate. During the operational preparation phase, the resource group 11a will be checked multiple times to determine whether it can handle the contracted DR product, and countermeasures will be taken accordingly.

[0034] First, compensation is determined at timing TM1. Timing TM1 is, for example, the day before the scheduled execution date and time. More specifically, timing TM1 is, for example, the time period from the time of execution to 6 hours before the scheduled execution date and time of the refund.

[0035] The compensation decision determines whether the provisionally selected resource group 11a can meet the DR power conditions (supply and demand power amount and supply and demand time period). This decision is made by predicting the amount of resources that can be provided by the provisionally selected resource group 11a based on the "planned usage information" and "status information" of the resource database 221a, and using this as a criterion to determine whether it can meet the DR power conditions. If the predicted amount of resources that can be supplied is smaller than the amount of resources that have been agreed upon, it is determined that the DR power conditions cannot be met. If it is determined that it cannot be met, resources belonging to the external resource group 12 are utilized, given that there is a relatively long time until the scheduled date and time of execution of the DR and from the standpoint of ensuring the fulfillment of the agreed-upon DR. In the example in Figure 7, it is assumed that resource 6 is used instead because it was found that resource 3a, which was planned to be used, cannot be used. The utilization of the external resource group 12 is done by requesting power usage managed by the server 8's aggregator from the server 8, or by making requests to individual resources.

[0036] Next, a re-allocation check is performed at timing TM2. Timing TM2 is, for example, the timing on the day of the scheduled execution. More specifically, timing TM2 is, for example, the time period from 6 hours before the scheduled execution date to the scheduled execution date.

[0037] The re-allocation decision determines whether the provisionally selected resource group 11a (or the resource group after compensation if compensation is made in the compensation decision) can meet the DR power requirements. This decision is made by predicting the amount of resources that can be provided by the provisionally selected resource group 11a based on the "planned usage information" and "status information" of the resource database 221a, and using this as the criterion for whether or not it can meet the DR power requirements. If the amount of resources actually secured is less than the amount of resources that were agreed upon, it is determined that the DR power requirements cannot be met. If it is determined that the requirements cannot be met, another resource 3 belonging to the registered resource group 11 is re-allocated because the scheduled date and time of the DR is approaching. In the example in Figure 7, it is assumed that resource 3b is used instead because it was found that resource 3a, which was planned to be used, cannot be used. The selection of resource 3b is made based on the "planned usage information" and "status information" of the resource database 221a.

[0038] During the operational phase, allocation decisions and fault detections are performed. The allocation decision determines whether the operational resource group can meet the power requirements. This decision is made by predicting the amount of resources that can be provided by the operational resource group, for example, based on the "planned usage information" and "status information" of the resource database 221a, and determining whether it is still possible to meet the DR power requirements. If it is determined that it is not possible, the power usage amount (supply and demand amount) of each resource in the operational resource group is changed to address the issue. The same procedure applies when using resources other than the registered resource group 11.

[0039] The fault detection process determines whether an operational issue (failure) has occurred in any of the resources currently in operation. This determination is made, for example, based on the results of communication with the individual resource 3. For example, if communication with the vehicle terminal 30 of resource 3 is impossible, if the vehicle terminal 30 of resource 3 notifies that the connection between the power cable 103 and resource 3 has been disconnected, if the vehicle terminal 30 of resource 3 notifies that the charge / discharge amount of the battery 35 based on the detection results of the sensor 38 cannot be confirmed, or if the vehicle terminal 30 of resource 3 notifies that the charge / discharge amount of the battery 35 based on the detection results of the sensor 38 has not reached the instruction given by the management device 2, then that resource is deemed operational and is determined to be faulty. The same applies when using resources other than those in the registered resource group 11. The processing when a failure is determined will be described later.

[0040] <Example of processing> Figures 8 and 9 are flowcharts showing examples of processing performed by the processing unit 21 of the management device 2, and in particular, the flowchart in Figure 7 shows an example of processing after the agreement is made.

[0041] In step S21, it is determined whether or not it is timing TM1 for compensation determination, based on the current date and time and the "schedule" information in the DR database 222. If it is timing TM1, the process proceeds to step S22.

[0042] In step S22, a compensation determination is made. Here, as explained with reference to Figure 7, it is determined whether the provisionally selected resource group 11a can meet the power conditions of the DR. In step S23, it is determined whether the determination result in step S22 was that the DR could be met. If it is met, the process proceeds to step S25; if it is not met, the process proceeds to step S24.

[0043] In step S24, compensation processing is performed. As explained with reference to Figure 7, processing is performed such as requesting power usage managed by the aggregator of server 8 via communication to secure resources other than the registered resource group 11. After that, the process proceeds to step S25.

[0044] In step S25, it is determined whether or not it is timing TM2 for re-allocation determination, based on the current date and time and the "schedule" information in the DR database 222. If it is timing TM2, the process proceeds to step S26.

[0045] Step S26 is a re-allocation determination. Here, as explained with reference to Figure 7, it is determined whether the provisionally selected resource group 11a (or the resource group after compensation if compensation is made in the compensation determination) can meet the DR power conditions. In step S27, it is determined whether the determination result in step S26 was able to meet the DR. If it is possible, the process proceeds to step S29; otherwise, the process proceeds to step S28.

[0046] In step S28, a re-allocation process is performed. Here, as explained with reference to Figure 7, the resource 3 scheduled for operation is changed, and another resource 3 belonging to the registered resource group 11 is selected as the resource scheduled for operation.

[0047] In step S29, it is determined whether or not the DR execution has started. For example, if the scheduled start date and time arrive, or if an execution instruction is sent to the management device 2 via the communication network from the server requesting the DR, it is determined that the DR execution has started.

[0048] In step S30, in response to the DR, the operation of the finally selected group of resources is started. For example, the management device 2 instructs the in-vehicle terminal 3 on the amount of power supply and demand for the battery 35 and on its execution. During operation, if there is a command on the amount of power supply and demand from the server that requested the DR via the communication network to the management device 2, it is responded to in real time.

[0049] In step S31, an allocation determination is made. Here, as explained with reference to Figure 7, it is determined whether the operational resource group can meet the power conditions. In step S32, it is determined whether the determination result from step S31 is suitable for DR. If it is suitable, the process proceeds to step S34; otherwise, the process proceeds to step S34.

[0050] In step S33, the allocation process is performed. Here, as explained with reference to Figure 7, the power usage amount (power supply and demand amount) of each resource in the group of resources currently in operation is changed. Then, for example, the management device 2 instructs the in-vehicle terminal 3 of resource 3, which is currently in operation, to change the power usage amount of the battery 35 and to execute it. After that, the process proceeds to step S34.

[0051] In step S34, a fault check is performed. Here, as explained with reference to Figure 7, it is determined whether or not a fault has occurred in any of the resources currently in operation. In step S35, it is determined whether or not the result of the check in step S34 was a fault. If there are no faults in any of the resources, the process proceeds to step S37. If there is a fault in any one of the resources, the process proceeds to step S36.

[0052] In step S37, it is determined whether the DR execution has finished. For example, it is determined that the DR execution has finished when the scheduled end date and time arrives, or when a termination instruction is sent to the management device 2 via the communication network from the server that requested the DR. If it is determined that the DR execution has finished, the process ends; if it is determined that the DR execution has not finished, the process returns to step S31 and repeats the same process.

[0053] In step S36, fault handling is performed. Figure 10(A) is a flowchart of fault handling A as an example.

[0054] In step S41, the resource determined to be faulty is identified, and the details of the failure are recorded. The failure details are stored, for example, in the "Failure Information" section of the DR database 222. This allows for retrospective verification of the cause of the failure, which can be used for future DR operations.

[0055] In step S42, the DR execution continues, and operations continue using resources that are not faulty. The process proceeds to step S37. As a result, it may not be possible to perform some of the subsequent DR, but this is unavoidable.

[0056] Another example of fault handling in step S36 will be described. Figure 10(B) is a flowchart of fault handling B, which is another example of fault handling in step S36.

[0057] Step S51 records the details of the failure. This is the same process as in step S41. In step S52, the execution of DR is stopped, and the operation of all resources is stopped. For example, the management device 2 instructs the in-vehicle terminal 3 of resource 3, which is in operation, to stop charging and discharging the battery 35. This prevents the entire management system 1 from failing due to a failure in some resources.

[0058] Figure 10(C) is a flowchart of fault handling C, which is yet another example of fault handling in step S36.

[0059] Step S61 records the details of the failure. This is the same process as in step S41. Step S62 stops the execution of DR and stops the operation of all resources. Further execution of DR is abandoned. This is the same process as in step S52. Step S63 instructs the in-vehicle terminals 3 of all resources 3 that were in operation to start charging a certain amount of battery 35. This avoids a situation where resource 3, which is a vehicle, becomes immobile due to lack of power, and ensures the convenience of user 5.

[0060] Figure 10(D) is a flowchart showing another example of fault handling in step S36, specifically fault handling D.

[0061] Step S71 records the details of the failure. This is the same process as in step S41. In step S72, only for resource 3 which has been determined to be faulty, the in-vehicle terminal 3 is instructed to start charging a certain amount of battery 35. This prevents resource 3 which has been determined to be faulty from becoming immobile due to lack of power. This ensures the convenience of user 5. In step S73, the DR execution continues, and operation continues with the resources that are not faulty. The process proceeds to step S37. As a result, it may not be possible to perform some of the subsequent DR, but this is unavoidable.

[0062] Furthermore, one of the fault processing steps A to D may be selectively executed as the fault processing step S36, depending on the situation. The selectable fault processing steps may be four types, A to D, or three types from A to D. In the case of three types, the selectable fault processing steps may be A to C. The selection criteria may be, for example, the number of failed resources or the type of failure. A priority may be set for the selection; for example, fault processing A may have the lowest priority, and fault processing A < fault processing B < fault processing C or fault processing D.

[0063] As described above, in this embodiment, by checking and taking measures to ensure that DR can be handled in stages at each phase from DR agreement to execution, resources can be utilized more reliably to respond to DR from the agreement to the execution of DR.

[0064] <Summary of Embodiments> The above embodiment discloses a management device and management method for at least the following items.

[0065] Item 1. A management device for managing multiple resources that respond to demand response, An acquisition means for acquiring information regarding the status of the aforementioned multiple resources, After the agreement on the demand response, and at a first timing before the execution of the demand response, a first determination means determines, based on the information, whether or not it is possible to respond to the power conditions of the demand response, After the first timing and before the execution, a second determination means determines, based on the information, whether or not it can respond to the power conditions of the demand response. During the execution of the demand response, a third determination means determines, based on the information, whether or not it is possible to respond to the power conditions of the demand response, If the first determination means determines that it is not possible to meet the power conditions of the demand response, the first processing means performs a process of supplementing with an external resource different from the multiple resources, If the second determination means determines that it is not possible to meet the power conditions of the demand response, the second processing means re-secures the resource scheduled for operation from among the multiple resources, The system includes a third processing means that, if the third determination means determines that it is not possible to meet the power conditions of the demand response, changes the power usage amount of multiple resources currently in operation. A management device characterized by the following features. According to this embodiment, resources can be utilized more reliably to respond to disaster recovery (DR) from the agreement to the execution of DR.

[0066] Item 2. The control device described in item 1, Each of the aforementioned resources is a vehicle equipped with a battery. The system includes a fourth determination means for determining whether or not there are any unusable resources among the multiple resources in operation during the execution of the aforementioned demand response. A management device characterized by the following features. According to this embodiment, operational failures can be identified and corrected.

[0067] Item 3. The control device described in item 2, If the fourth determination means determines that there is a resource among the multiple resources currently in operation that is unavailable for the demand response, information identifying the unavailable resource is recorded, and the operation of the demand response is continued. A management device characterized by the following features. According to this embodiment, in the event of an operational failure, it is possible to respond to a disaster recovery (DR) while enabling post-event verification.

[0068] Item 4. The control device described in item 2, If the fourth determination means determines that there is an unusable resource among the multiple resources currently in operation, the system includes a fourth processing means that performs a process to stop the operation of the demand response. A management device characterized by the following features. According to this embodiment, if an operational failure occurs, it is possible to perform post-incident verification while avoiding further system failures.

[0069] Item 5. The control device described in item 2, If the fourth determination means determines that there is an unusable resource among the multiple resources currently in operation, the system is further equipped with a fourth processing means that initiates a certain amount of charging to all of the resources currently in operation. A management device characterized by the following features. According to this embodiment, in the event of an operational failure, the movement of the vehicle, which is a resource, can be secured, thereby ensuring user convenience.

[0070] Item 6. The control device described in item 2, If the fourth determination means determines that there is an unusable resource among the multiple resources currently in operation, the system includes a fourth processing means that identifies the unusable resource and initiates a certain amount of charging only to the identified resource. A management device characterized by the following features. According to this embodiment, in the event of an operational failure, the movement of the faulty vehicle, which is a resource, can be secured, thereby ensuring user convenience.

[0071] Item 7. The control device described in item 1, Each of the aforementioned resources is a vehicle equipped with a battery. The aforementioned information is, The State of Charge (SOC) of the battery, and vehicle status information including the connection status between the vehicle and the power cable, This includes scheduled information indicating the planned use of the aforementioned vehicle, A management device characterized by the following features. According to this embodiment, the determination at each stage can be made more accurately.

[0072] Item 8. The control device described in item 7, The vehicle is equipped with a communication means capable of wireless communication with the vehicle, At least a portion of the aforementioned information is obtained from the vehicle via the communication means. A management device characterized by the following features. According to this embodiment, it becomes easier to obtain the latest information.

[0073] Item 9. The control device described in item 7, The vehicle is equipped with a communication means capable of wireless communication with the user's communication terminal, At least a portion of the aforementioned information is obtained from the communication terminal via the communication means. A management device characterized by the following features. According to this embodiment, it becomes easier to obtain the latest information.

[0074] Item 10. A management method for managing multiple resources that respond to demand responses using a server, The server performs an acquisition step of acquiring information regarding the status of the multiple resources, The server performs a first determination step, after the demand response has been agreed upon and before the demand response has been executed, to determine, based on the information, whether or not it can meet the power conditions of the demand response. The server, after the first timing and before execution, performs a second determination step in which it determines, based on the information, whether or not it can respond to the power conditions of the demand response. The server, while executing the demand response, performs a third determination step of determining whether it can respond to the power conditions of the demand response based on the information, If the server is determined by the first determination step to be unable to meet the power requirements of the demand response, the first processing step includes performing a process to supplement the multiple resources with external resources different from the multiple resources, If the server is determined by the second determination step to be unable to meet the power requirements for the demand response, a second processing step is performed to reallocate the resources scheduled for operation from among the multiple resources, The system includes a third processing step that modifies the power usage amount of multiple resources in operation if the server is determined by the third determination step to be unable to meet the power conditions of the demand response. A management method characterized by the following features. According to this embodiment, resources can be utilized more reliably to respond to disaster recovery (DR) from the agreement to the execution of DR.

[0075] Although embodiments of the invention have been described above, the invention is not limited to the above embodiments, and various modifications and changes are possible within the scope of the gist of the invention. [Explanation of Symbols]

[0076] 1. Management system, 2. Management device, 3. Resources

Claims

1. A management device for managing multiple resources that respond to demand response, An acquisition means for acquiring information regarding the status of the aforementioned multiple resources, After the agreement on the demand response, and at a first timing before the execution of the demand response, a first determination means determines, based on the information, whether or not it is possible to respond to the power conditions of the demand response, After the first timing and before the execution, a second determination means determines, based on the information, whether or not it can respond to the power conditions of the demand response. During the execution of the demand response, a third determination means determines, based on the information, whether or not it is possible to respond to the power conditions of the demand response, If the first determination means determines that it is not possible to meet the power conditions of the demand response, the first processing means performs a process of supplementing with an external resource different from the multiple resources, If the second determination means determines that it is not possible to meet the power conditions of the demand response, the second processing means re-secures the resource scheduled for operation from among the multiple resources, The system includes a third processing means that, if the third determination means determines that it is not possible to meet the power conditions of the demand response, changes the power usage amount of multiple resources currently in operation. A management device characterized by the following features.

2. A control device according to claim 1, Each of the aforementioned resources is a vehicle equipped with a battery. The system includes a fourth determination means for determining whether or not there are any resources among the multiple resources currently in operation that are unavailable for the demand response during the execution of the demand response. A management device characterized by the following features.

3. A control device according to claim 2, If the fourth determination means determines that there is a resource among the multiple resources currently in operation that is unavailable for the demand response, information identifying the unavailable resource is recorded, and the operation of the demand response is continued. A management device characterized by the following features.

4. A control device according to claim 2, If the fourth determination means determines that there is an unusable resource among the multiple resources currently in operation, the system includes a fourth processing means that performs a process to stop the operation of the demand response. A management device characterized by the following features.

5. A control device according to claim 2, If the fourth determination means determines that there is an unusable resource among the multiple resources currently in operation, the system is further equipped with a fourth processing means that initiates a certain amount of charging to all of the resources currently in operation. A management device characterized by the following features.

6. A control device according to claim 2, If the fourth determination means determines that there is an unusable resource among the multiple resources currently in operation, the system includes a fourth processing means that identifies the unusable resource and initiates a certain amount of charging only to the identified resource. A management device characterized by the following features.

7. A control device according to claim 1, Each of the aforementioned resources is a vehicle equipped with a battery. The aforementioned information is, The state of charge (SOC) of the battery and vehicle status information including the connection status between the vehicle and the power cable, This includes scheduled information indicating the planned use of the aforementioned vehicle, A management device characterized by the following features.

8. A control device according to claim 7, The vehicle is equipped with a communication means capable of wireless communication with the vehicle, At least a portion of the aforementioned information is obtained from the vehicle via the communication means. A management device characterized by the following features.

9. A control device according to claim 7, The vehicle is equipped with a communication means capable of wireless communication with the user's communication terminal, At least a portion of the aforementioned information is obtained from the communication terminal via the communication means. A management device characterized by the following features.

10. A management method for managing multiple resources that respond to demand responses using a server, The server performs an acquisition step of acquiring information regarding the status of the multiple resources, The server performs a first determination step, after the demand response has been agreed upon and before the demand response has been executed, to determine whether it can meet the power conditions of the demand response based on the information, The server, after the first timing and before execution, performs a second determination step in which it determines, based on the information, whether or not it can respond to the power conditions of the demand response. The server, while executing the demand response, performs a third determination step of determining whether it can respond to the power conditions of the demand response based on the information, If the server is determined by the first determination step to be unable to meet the power requirements of the demand response, the first processing step includes performing a process to supplement the multiple resources with external resources different from the multiple resources, If the server is determined by the second determination step to be unable to meet the power requirements for the demand response, a second processing step is performed to reallocate the resources scheduled for operation from among the multiple resources, The system includes a third processing step that modifies the power usage amount of multiple resources in operation if the server is determined by the third determination step to be unable to meet the power conditions of the demand response. A management method characterized by the following features.

Images