JP7740177B2 - Power Management System - Google Patents

Description

This disclosure relates to a power management system.

In recent years, attention has been focused on virtual power plants (VPPs), which integrate and control multiple distributed energy resources (DERs) as if they were a single power plant in order to maintain a balance between supply and demand for electricity supplied from the power grid. Japanese Patent Application Laid-Open Publication No. 2020-156149 (Patent Document 1) discloses that, to meet the needs of electric utilities, an aggregator's server communicates with a consumer's energy management system (e.g., a Home Energy Management System (HEMS)) via an EMS (Energy Management System) network, and charges and discharges the battery installed in an electric vehicle, thereby utilizing the vehicle's battery as a DER.

Japanese Patent Application Laid-Open No. 2020-156149

In the VPP system described in Patent Document 1, the aggregator acquires data on the specifications and usage status of the battery installed in the electric vehicle, and uses this data to formulate an operation plan for the battery and control the charging and discharging of the battery.

For example, if an operation plan for a battery is formulated using data from the battery, the amount of charge and discharge may be insufficient, and the aggregator may not be able to secure enough charge and discharge power to meet the demands of the electric utility, which could result in transactions not being concluded in the electricity market.

This disclosure aims to increase the likelihood of transactions being concluded in the electricity market even when it is not possible to secure enough charging and discharging power to meet the demand.

The power management method disclosed herein controls multiple power regulation resources that can be electrically connected to a power grid. The power management method aggregates the chargeable and dischargeable power of the power regulation resources based on a request plan requested by the power grid, and when the aggregated chargeable and dischargeable power does not meet the request plan, creates an alternative plan and inquires whether the power regulation resources can be controlled based on the alternative plan.

According to this method, the chargeable and dischargeable power of power regulation resources is aggregated based on the demand plan requested by the power grid. If the aggregated chargeable and dischargeable power does not meet the demand plan, an alternative plan is created and control of the power regulation resources based on the alternative plan is proposed. If the proposed alternative plan is accepted, a transaction in the electricity market is concluded, thereby increasing the likelihood of a transaction in the electricity market being concluded compared to when an alternative plan is not proposed.

Preferably, the request plan may be requested by an aggregation coordinator, and the aggregation of the chargeable and dischargeable power of the power adjustment resources may be performed by the resource aggregator. When the aggregated chargeable and dischargeable power does not meet the request plan, it may be determined whether the chargeable and dischargeable power meets the request plan when a power storage device owned by the resource aggregator is used as a power adjustment resource. If the chargeable and dischargeable power does not meet the request plan even when a power storage device is used as a power adjustment resource, an alternative plan may be created and control of the power adjustment resources based on the alternative plan may be proposed.

A resource aggregator is a business that directly concludes a VPP service contract with consumers who own the power regulation resources and controls the power regulation resources. An aggregation coordinator is a business that aggregates the power controlled by the resource aggregator and trades power directly with electric power companies (power generation companies, transmission and distribution companies, etc.) that manage the power grid.

According to this method, when the aggregated chargeable/dischargeable power does not meet the request plan requested by the aggregation coordinator, a determination is made as to whether the chargeable/dischargeable power will meet the request plan when a power storage device owned by the resource aggregator is used as a power adjustment resource. If the chargeable/dischargeable power meets the request plan when a power storage device owned by the resource aggregator is used as a power adjustment resource, the aggregation coordinator's request can be met, thereby increasing the likelihood of a transaction being concluded in the electricity market. Furthermore, even when a power storage device is used as a power adjustment resource, if the chargeable/dischargeable power does not meet the request plan, control of the power adjustment resource based on an alternative plan is proposed. If the proposed alternative plan is accepted, a transaction is concluded in the electricity market. This increases the likelihood of a transaction being concluded in the electricity market compared to when an alternative plan is not proposed.

Preferably, when aggregating the chargeable/dischargeable power of a power adjustment resource based on a request plan requested by the power grid, if the power adjustment resource is an on-board power storage device mounted on a vehicle, the chargeable/dischargeable power is aggregated taking into account the limitations of the on-board power storage device, and if the aggregated chargeable/dischargeable power does not meet the request plan, the limitations of the on-board power storage device are relaxed and the chargeable/dischargeable power is re-aggregated, and if the re-aggregated chargeable/dischargeable power does not meet the request plan, an alternative plan is created and control of the power adjustment resource based on the alternative plan is proposed.

Onboard energy storage devices used as a vehicle's power source are subject to limitations on charging and discharging, such as the amount of storage required by the vehicle's driving plan (travel schedule) and the frequency (number of times the relay is activated) of relays to protect the system main relay. According to this method, when aggregating the chargeable and dischargeable power of a power regulation resource based on a request plan requested from the power grid, if the power regulation resource is an onboard energy storage device mounted on a vehicle, the chargeable and dischargeable power is aggregated taking into account the limitations of the onboard energy storage device. If the aggregated chargeable and dischargeable power does not meet the request plan, the limitations of the onboard energy storage device are relaxed and the chargeable and dischargeable power is re-aggregated. If the re-aggregated chargeable and dischargeable power meets the request plan, the request can be met, increasing the likelihood of a transaction being concluded in the electricity market. Furthermore, if the re-aggregated chargeable and dischargeable power does not meet the request plan, control of the power regulation resource based on an alternative plan is proposed. If the proposed alternative plan is accepted, a transaction is concluded in the electricity market. This increases the likelihood of a transaction being concluded in the electricity market compared to when an alternative plan is not proposed.

The power management system disclosed herein controls multiple power adjustment resources that can be electrically connected to a power grid, and includes a first server that formulates a request plan based on the adjustment amount requested by the power grid, and a second server that acquires the request plan formulated by the first server and issues charging and discharging commands to the power adjustment resources. The second server aggregates the chargeable and dischargeable power of the power adjustment resources based on the request plan, and when the aggregated chargeable and dischargeable power does not meet the request plan, creates an alternative plan and proposes control of the power adjustment resources based on the alternative plan to the first server.

With this configuration, the second server aggregates the chargeable and dischargeable power of the power adjustment resources based on the request plan formulated by the first server. When the aggregated chargeable and dischargeable power does not meet the request plan, the second server creates an alternative plan and proposes control of the power adjustment resources based on the alternative plan to the first server. If the proposed alternative plan is accepted, a transaction in the electricity market is concluded, thereby increasing the likelihood of a transaction in the electricity market being concluded compared to when an alternative plan is not proposed.

Preferably, the second server is a server managed by the resource aggregator, and the power management system further includes a power storage device owned by the resource aggregator. When the aggregated chargeable/dischargeable power does not meet the required plan, the second server determines whether the chargeable/dischargeable power meets the required plan when the power storage device is used as a power adjustment resource, and when the chargeable/dischargeable power does not meet the required plan even when the power storage device is used as a power adjustment resource, creates an alternative plan and proposes to the first server control of the power adjustment resource based on the alternative plan.

With this configuration, when a power storage device owned by a resource aggregator is used as a power adjustment resource, if the chargeable/dischargeable power meets the required plan, the request of the power grid can be met, increasing the likelihood of a transaction being concluded in the power market. Furthermore, even when a power storage device is used as a power adjustment resource, if the chargeable/dischargeable power does not meet the required plan, a proposal is made to control the power adjustment resource based on an alternative plan. Therefore, if the proposed alternative plan is accepted, a transaction is concluded in the power market. This increases the likelihood of a transaction being concluded in the power market compared to when an alternative plan is not proposed.

Preferably, when aggregating the chargeable and dischargeable power of the power adjustment resource based on the request plan, if the power adjustment resource is an on-board power storage device mounted on a vehicle, the second server aggregates the chargeable and dischargeable power taking into account the limitations of the on-board power storage device, and if the aggregated chargeable and dischargeable power does not meet the request plan, relaxes the limitations of the on-board power storage device and re-aggregates the chargeable and dischargeable power, and if the re-aggregated chargeable and dischargeable power does not meet the request plan, creates an alternative plan and proposes to the first server control of the power adjustment resource based on the alternative plan.

With this configuration, if the re-aggregated chargeable/dischargeable power meets the request plan, the request can be met, increasing the likelihood of a transaction being concluded in the electricity market. Furthermore, if the re-aggregated chargeable/dischargeable power does not meet the request plan, a proposal is made to control power adjustment resources based on an alternative plan. If the proposed alternative plan is accepted, a transaction is concluded in the electricity market. This increases the likelihood of a transaction being concluded in the electricity market compared to when an alternative plan is not proposed.

This disclosure increases the likelihood of a transaction being concluded in the electricity market, even if it is not possible to secure enough charging and discharging power to meet the demand.

1 is a schematic overall configuration diagram of a power management system according to an embodiment of the present invention; FIG. 2 is a diagram illustrating an example of the configuration of a server and an electric vehicle managed by a lower-level aggregator. 10 is a flowchart showing an example of processing of a power management method according to the present embodiment. 10 is a flowchart showing an example of processing of a power management method according to the present embodiment.

Embodiments of the present disclosure will now be described in detail with reference to the drawings. Note that identical or corresponding parts in the drawings will be designated by the same reference numerals, and their description will not be repeated.

Figure 1 is a schematic diagram of the overall configuration of a power management system 1 according to this embodiment. The power management system 1 of this embodiment is a VPP system. A VPP system uses advanced energy management technology that utilizes IoT (Internet of Things) to bundle a large number of DERs together and remotely and centrally control these DERs to make them function as if they were a single power plant. The power management system 1 of this embodiment uses vehicles equipped with power storage devices as DERs. The power storage devices installed in the vehicles are DERs and are an example of the "power adjustment resources" of this disclosure.

The power management system 1 includes multiple electric vehicles and multiple power supply devices (EVSE: Electric Vehicle Service Equipment). The number of electric vehicles and EVSE included in the power management system 1 is each independently arbitrary, and may be 10 or more, or 100 or more. The power management system 1 may include at least one of non-public EVSE (for example, a home EVSE) that can only be used by specific users, and public EVSE that can be used by an unspecified number of users.

The power management system 1 includes a power company E1, a higher-level aggregator E2, and a lower-level aggregator E3. The power company E1 serves as a power generation company, a power transmission and distribution company, an electricity retailer, etc. The power company E1 is the administrator of the power grid PG. The lower-level aggregator E3 is a resource aggregator that directly concludes VPP service contracts with consumers who own power adjustment resources and controls resources (DERs). The higher-level aggregator E2 is, for example, an aggregation coordinator that aggregates the power controlled by the resource aggregator (lower-level aggregator) E3 and trades power directly with the power company E1. The higher-level aggregator E2 receives a DR (Demand Response) request from the power company E1, formulates a DR request plan, and transmits the DR request plan to the lower-level aggregator E3.

Figure 2 is a diagram showing an example of the configuration of a server 30 and an electric vehicle 50 managed by a lower-level aggregator (resource aggregator) E3. Figure 2 shows the relationship between the power grid PG, smart meter 13, server 30, EVSE 40, electric vehicle 50, EMS network 60, and HEMS 70. Server 30 corresponds to an example of a "second server" in this disclosure.

The electric vehicle 50 is configured to be able to run using electric power stored in a power storage device (battery) 100. The electric vehicle 50 according to this embodiment is an electric vehicle (BEV: Battery Electric Vehicle) that does not have an engine (internal combustion engine), but may also be a plug-in hybrid electric vehicle (PHEV: Plug-in Hybrid Electric Vehicle). The battery 100 is composed of a secondary battery such as a lithium-ion battery or a nickel-metal hydride battery. The battery 100 is an example of an "on-vehicle power storage device" as defined in this disclosure.

The electric vehicle 50 includes an ECU (Electronic Control Unit) 110. The ECU 110 is configured to control the charging and discharging of the battery 100. The electric vehicle 50 also includes a monitoring module (not shown) that monitors the state of the battery 100. The monitoring module includes various sensors that detect the state of the battery 100 (e.g., voltage, current, and temperature) and outputs the detection results to the ECU 110. Note that the monitoring module may be a BMS (Battery Management System) that, in addition to the above sensor functions, also has an SOC (State Of Charge) estimation function, an SOH (State of Health) estimation function, a cell voltage equalization function, a diagnostic function, and a communication function.

The electric vehicle 50 is equipped with an inlet 120 and a charge/discharge circuit 130 for charging and discharging the battery 100. The inlet 120 is configured to exchange power with the outside of the electric vehicle 50. The inlet 120 is configured to allow connection of a connector 45 of a charge/discharge cable 44. When the connector 45 of the charge/discharge cable 44 connected to the main body of the EVSE 40 is connected (plugged in) to the inlet 120 of the electric vehicle 50, the electric vehicle 50 enters a state in which it can be charged and discharged (i.e., a state in which it can exchange power with the EVSE 40).

The EVSE 40 of this embodiment is a power supply device compatible with V2G (Vehicle to Grid) (or V2H (Vehicle to Home)), and converts AC power supplied from the power grid PG into DC power to charge the battery 100. The EVSE 40 is also capable of converting DC power discharged from the battery 100 into AC power and supplying it to the power grid PG (reverse power flow). The EVSE 40 includes a control unit 41, a communication unit 42, a power supply circuit 43, and a charge/discharge cable 44. The control unit 41, the communication unit 42, and the power supply circuit 43 are provided in the main body of the EVSE 40. The charge/discharge cable 44 is connected to the main body of the EVSE 40. The charge/discharge cable 44 may be permanently connected to the main body of the EVSE 40, or may be detachable from the main body of the EVSE 40. The charge/discharge cable 44 has a connector 45 at its tip and includes a power line inside. The control unit 41 controls the communication unit 42 and the power supply circuit 43.

The power grid PG is a power network provided by the power company E1. The power grid PG is electrically connected to multiple EVSEs (including EVSE 40) and supplies AC power to each EVSE. The smart meter 13 is configured to measure the amount of power every predetermined time (for example, every 30 minutes), store the measured amount of power, and transmit it to the server 10 (see Figure 1) managed by the power company E1. The smart meter 13 also transmits the measured amount of power to the server 30 managed by the lower-level aggregator E3.

The server 30 managed by the lower aggregator E3 communicates with the electric vehicle 50 and the HEMS 70 via the EMS network 60. The EMS network 60 may be a dedicated line or an internet line such as a VPN (Virtual Private Network). The communication device 140 installed in the electric vehicle 50 communicates with the server 30 via the EMS network 60. The communication device 140 is configured to communicate with the communication unit 42 of the EVSE 40 via the charge/discharge cable 44. The communication method between the EVSE 40 and the electric vehicle 50 is arbitrary, and may be, for example, a Controller Area Network (CAN) or a Control Pilot Line (CPLT) communication using Power Line Communication (PLC). The communication between the electric vehicle 50 and the EVSE 40 may be wireless communication using Bluetooth (registered trademark) or the like. The communication unit 42 and communication device 140, which communicate between the EVSE 40 and the electric vehicle 50, correspond to an example of a "second communication device" in this disclosure.

The server 30 is configured to include a control device 31, a storage device 32, and a communication device 33. The control device 31 includes a processor and memory, and is configured to perform predetermined information processing and control the communication device 33. The storage device 32 is configured to be able to store various types of information. The communication device 33 includes various communication I/Fs, and is configured to communicate with the outside world via the EMS network 60.

HEMS 70 is a controller that controls home appliances in the home. In this embodiment, it controls EVSE 40 based on a DR command (charge/discharge command) from server 30, and controls the charging and discharging of battery 100. In this embodiment, HEMS 70 is used because EVSE 40 is a non-public EVSE (e.g., a home EVSE) that can only be used by specific users. If EVSE 40 is a public EVSE that can be used by an unspecified number of users, a Factory Energy Management System (FEMS) or Building Energy Management System (BEMS) installed in a business establishment (e.g., a factory or commercial facility) may be used instead of HEMS 70.

The HEMS 70 is configured to include a control device 71, a storage device 72, and a communication device 73. The control device 71 includes a processor and memory, and is configured to perform predetermined information processing and control the communication device 73. The storage device 72 is configured to be able to store various types of information. The communication device 73 includes various communication I/Fs and is configured to communicate with the outside world via the EMS network 60. The communication device 73 is also connected to the communication unit 42 of the EVSE 40 via a LAN, and the HEMS 70 also functions as a gateway device that relays between the EMS network 60 and the LAN (relaying between the server 30 and the EVSE 40). The LAN may be a wired LAN or a wireless LAN using Wi-Fi.

Referring to FIG. 1, electric power company E1 constructs a power grid (power system PG shown in FIG. 1) using a power plant 11 and power transmission and distribution equipment 12, and maintains and manages the power system PG using a server 10. The power plant 11 includes a power generation device and is configured to supply the power generated by the power generation device to the power transmission and distribution equipment 12. The power generation method of the power plant 11 is arbitrary. The power generation method of the power plant 11 may be any of thermal power generation, hydroelectric power generation, wind power generation, nuclear power generation, and solar power generation. The power transmission and distribution equipment 12 includes transmission lines, substations, and distribution lines, and is configured to transmit and distribute the power supplied from the power plant 11.

By working with the aggregator, electric power company E1 can adjust power consumption in the electric power grid PG. Upper aggregator (aggregation coordinator) E2 operates and manages server 20. Lower aggregator (resource aggregator) E3 operates and manages servers (e.g., servers 30, 30A, 30B) for each business operator. Server 20 managed by upper aggregator (aggregation coordinator) E2 corresponds to an example of the "first server" in this disclosure. Note that the configuration of server 20 is almost identical to that of server 30, and therefore a description thereof will be omitted.

In FIG. 1, electric vehicle 50A and EVSE 40A have substantially the same configuration as electric vehicle 50 and EVSE 40. EVSE 40A is connected to the power grid PG via smart meter 13A. EVSE 40A is not connected to server 30 via a HEMS or the like, and battery charge/discharge control is performed by (the ECU of) electric vehicle 50A based on DR commands (charge/discharge commands) from server 30. Furthermore, a solar power generation device 90 is electrically connectable to the power grid PG, and the solar power generation device 90 is capable of communicating with server 30. The solar power generation device 90 is one type of DER and may be an example of a "power adjustment resource" of the present disclosure. The solar power generation device 90 may also include a power storage device. Electric vehicle 50 (EVSE 40, HEMS 70), electric vehicle 50A (EVSE 40A), and solar power generation device 90 are owned by each consumer, and each consumer has concluded a VPP service contract with lower-level aggregator E3, which operates (manages) server 30. Power storage device 80 is a DER owned by lower-level aggregator E3, which operates (manages) server 30, and is electrically connectable to power grid PG.

In this embodiment, the server 10 of the electric power company E1 issues a DR request to the server 20 of the upper aggregator E2 based on the power demand forecast of the power grid PG, specifying the time period (date and time) for DR execution and the charge/discharge power. If power demand is tight, a downward DR request is issued, and if there is a power surplus, an upward DR request is issued. The server 20 of the upper aggregator E2 formulates a DR request plan based on the DR request from the server 10. The server 20 then transmits the DR request plan to the servers 30, 30A, and 30B of the lower aggregator E3. The DR request plans transmitted to the servers 30, 30A, and 30B may be the same. Furthermore, a DR request plan may be created according to the business scale of the lower aggregator (resource aggregator) E3, and the DR request plan according to the business scale may be transmitted to the servers 30, 30A, and 30B. The DR request plan may include the time period (date and time) when DR will be performed and the charging and discharging power.

The servers 30, 30A, and 30B of the lower aggregator E3 transmit DR request values to contracted consumers, taking into account the characteristics and capabilities (scale) of each consumer's DER. The DR request value is, for example, the time period for DR execution and the charge/discharge power. Because the processes executed by the servers 30, 30A, and 30B are similar, the following describes the example of server 30. Referring to FIG. 2 , upon receiving DR request value information via the EMS network 60, the HEMS 70 determines whether the electric vehicle 50 can respond to the DR request. For example, the EVSE 40 communicates with the electric vehicle 50 to acquire vehicle information such as the electric vehicle 50's planned activities (departure date and time, etc.) and the SOC of the battery 100. The EVSE 40 transmits the acquired vehicle information to the HEMS 40. The HEMS 40 determines whether it can respond to the DR request transmitted from the server 30 based on the received vehicle information. If the HEMS 40 is able to respond to the DR request, it transmits participation possibility information and chargeable/dischargeable power to the server 30. If it is difficult to respond to the DR request, it transmits participation possibility information to the server 30. Note that the electric vehicle 50 (ECU 110) may determine whether to respond to the DR request through communication between the electric vehicle 50 and the server 30, and transmit information such as participation possibility to the server 30. Alternatively, the consumer may check the DR request information displayed on a display device (not shown) of the HEMS 70 or a display device (not shown) of the electric vehicle 50, and transmit whether or not to participate in DR at the consumer's discretion.

When the server 30 of the lower aggregator E3 receives information from all contracted consumers regarding whether they can participate in DR, it aggregates the chargeable and dischargeable power. For example, it calculates the available power by adding up the chargeable and dischargeable power of each DER that can participate in DR. The available power corresponds to an example of the "aggregated chargeable and dischargeable power" of this disclosure. If the chargeable and dischargeable power (available power) aggregated by the server 30 does not meet the chargeable and dischargeable power (request value) in the DR request plan, the lower aggregator E3 will be unable to secure the chargeable and dischargeable power that meets the request of the upper aggregator E2, making it difficult for the lower aggregator E3 to conclude a transaction with the upper aggregator E2.

In this embodiment, if the lower aggregator E3's available power (chargeable and dischargeable power aggregated by server 30) does not meet the DR request plan, it creates an alternative plan and proposes the created alternative plan to the upper aggregator E2 (server 20). If the alternative plan is acceptable to the upper aggregator E2, the lower aggregator E3 can conclude a transaction with the upper aggregator E2, increasing the likelihood of a transaction being concluded in the electricity market.

Figures 3 and 4 are flowcharts showing an example of a power management method in this embodiment. The processing according to this flowchart is performed in cooperation with the server 20 of the upper aggregator E2, the server 30 of the lower aggregator E3, and the control unit (e.g., HEMS 70, ECU of electric vehicle 50A) of a DER owned by a consumer that has concluded a VPP service contract with the lower aggregator E3 that operates server 30. Note that in Figures 3 and 4, the decision-making steps in the control unit of the DER owned by the consumer are omitted.

When the server 20 of the upper aggregator E2 receives a DR request from the server 10 of the electric power company E1, in step (hereinafter, step is abbreviated as "S") 1, it creates a DR request plan and transmits the created DR request plan to the server 30 of the lower aggregator E3. The DR request plan may include the time period (date and time) for DR execution and the requested charge and discharge power. For example, the charge and discharge power for each 30-minute period is the charge and discharge power for each period. In the case of an upward DR request, the charge and discharge power is the charge power (power consumption) of each consumer. In this embodiment, in the case of a downward DR request, reverse power flow aggregation (positive watt aggregation) is requested, and the requested charge and discharge power is the discharge power (power generation power) of each consumer's DER.

When server 30 of lower aggregator E3 receives the DR request plan sent from server 20, a positive judgment is made in S20, and a DR request value is calculated in S21. The DR request value is calculated for each DER, taking into account the characteristics and capacity (scale) of the DER of the contracted consumer. Next, in S22, the calculated DR request value is sent to the control unit of each consumer's DER. Upon receiving the DR request value, the control unit of each consumer's DER calculates the chargeable and dischargeable power. If the DER is a battery (on-board storage battery) installed in an electric vehicle, various restrictions are taken into account when calculating the chargeable and dischargeable power to calculate whether or not to participate in DR and the chargeable and dischargeable power. For example, when the HEMS 70 receives the DR request value and calculates the chargeable/dischargeable power of the battery 100, it calculates whether or not to participate in DR and the chargeable/dischargeable power taking into account restrictions such as the planned activities of the electric vehicle 50 (departure date and time, SOC required at departure, etc.), the current SOC, the system main relay operation frequency (number of times operated), and the input/output power upper limit (input/output current upper limit). Subsequently, in S51, the HEMS 70 transmits whether or not to participate and the calculated chargeable/dischargeable power to the server 30.

The server 30 receives from the control unit of each consumer's DER whether or not they can participate in DR and the chargeable and dischargeable power. When the server 30 receives the participation and dischargeable power from all consumers, a positive determination is made in S23, and the available power is calculated in S24. The available power is the sum of the chargeable and dischargeable power of each DER that can participate in DR, and corresponds to an example of the "aggregated available chargeable and dischargeable power" of this disclosure. In S25, the server 30 determines whether the available power satisfies the DR request plan received in S20. If the available power satisfies the DR request plan, a positive determination is made and the process proceeds to S36. If the available power is less than the charge and discharge power requested in the DR request plan and the available power does not satisfy the DR request plan, a negative determination is made and the process proceeds to S26.

In S26, the available power when participating in DR using the power storage device 80 owned by the lower aggregator E3 that operates (manages) the server 30 is calculated. The available power when using the power storage device 80 is calculated by adding the available power calculated in S24 to the chargeable power of the power storage device 80.

In the following S27, the server 30 determines whether the available power calculated in S26 satisfies the DR request plan received in S20. If the available power calculated in S26 satisfies the DR request plan, a positive determination is made and the process proceeds to S36. If the available power calculated in S26 does not satisfy the DR request plan, a negative determination is made and the process proceeds to S28.

In S28, the server 30 transmits a request to recalculate the chargeable/dischargeable power to the control unit of the DER, which is an on-board power storage device and has transmitted its acceptance for DR participation. For example, the server 30 transmits a request to recalculate the chargeable/dischargeable power to the HEMS 70. Upon receiving the request to recalculate the chargeable power, the HEMS 70 relaxes the restrictions and calculates the chargeable/dischargeable power in S52. Relaxation of the restrictions is performed, for example, by removing or relaxing restrictions previously set by the consumer (user of the electric vehicle 50). For example, a user who can tolerate a certain degree of deterioration of the system main relay may set the system main relay to remove restrictions on its operation frequency (number of times it operates). If the user can tolerate an increase in the temperature of the battery 100, the user may set a large input/output power upper limit (input/output current upper limit) and relax the restrictions. After relaxing the restrictions and calculating the chargeable/dischargeable power, the calculated chargeable/dischargeable power is transmitted to the server 30 in S53.

When server 30 receives the chargeable/dischargeable power calculated by relaxing the restrictions from all consumers who have requested a recalculation of the available power, a positive judgment is made in S29, and server 30 recalculates the available power in S30. The recalculation of the available power is performed by replacing the chargeable/dischargeable power received in S23 from the consumers who have requested a recalculation of the available power, which is included in the available power calculated in S26, with the chargeable/dischargeable power calculated by relaxing the restrictions received in S29. The available power recalculated in S30 corresponds to an example of the "re-aggregated chargeable/dischargeable power" of the present disclosure.

In S31, server 30 determines whether the available power recalculated in S30 satisfies the DR request plan received in S20. If the available power recalculated in S30 satisfies the DR request plan, a positive determination is made and the process proceeds to S36. If the available power recalculated in S30 does not satisfy the DR request plan, a negative determination is made and the process proceeds to S32.

In S32, server 30 creates an alternative plan. The alternative plan is created based on the charge/discharge power that the lower-level aggregator E3 can handle. The charge/discharge power that can be handled may be, for example, the handleable power calculated in S24, the handleable power calculated in S26, or the handleable power recalculated in S30. The alternative plan is a plan for controlling the charge/discharge of DERs owned by consumers who have contracts with lower-level aggregator E3, which operates (manages) server 30. In S33, the alternative plan created in S32 is sent to server 20, where it is proposed to upper-level aggregator E2.

In S36, server 30 transmits to server 20 that it can accommodate the DR request plan. When server 20 of upper aggregator E2 receives that it can accommodate, it makes a positive judgment in S2 and proceeds to S7. When server 20 receives the alternative plan from server 30, it makes a positive judgment in S3 and proceeds to S4. In S4, it determines whether the alternative plan received in S3 is acceptable, and if the alternative plan is acceptable, it makes a positive judgment and proceeds to S7. If the alternative plan cannot be accepted, it makes a negative judgment in S4 and proceeds to S5.

In S5, server 20 reviews the DR request plan sent to server 30 in S1, creates a DR re-request plan, and then proceeds to S6, where it sends the DR re-request plan to server 30. The DR re-request plan may request charging/discharging power that is lower than the charging/discharging power of the alternative plan received in S3, and may be created taking into account the charging/discharging power that can be handled by another lower-level aggregator E3 (lower-level aggregator E3 that operates servers 30A and 30B).

When the DR re-request plan is sent from server 20, server 30 that receives the DR re-request plan executes the processing from S20 onwards for the DR re-request plan in the same way as for the DR request plan.

In S7, server 20 transmits to server 30 a notification that a transaction has been concluded between upper aggregator E2 and lower aggregator E3, which operates server 30, and that a contract has been concluded. When server 30 receives a notification from server 20 that a contract has been concluded, it makes a positive determination in S34 and proceeds to S35. In S35, it transmits a notification that a transaction has been concluded and that a contract has been concluded to the control unit of the DER that transmitted the DR participation acceptance. In S54, the control unit of the DER detects that a transaction has been concluded and that a contract has been concluded, and waits to control the DER (power adjustment resource) based on the DR information scheduled thereafter.

According to this embodiment, the lower aggregator E3 (its server 30) aggregates the chargeable and dischargeable power of the DER (power regulation resource) based on the request plan requested by the power system PG (power company E1, upper aggregator E2) (S23, S24). Then, when the aggregated chargeable and dischargeable power (capable power) does not meet the request plan (negative judgment in S25), an alternative plan is created (S32) and DER control based on the alternative plan is proposed (S33). If the proposed alternative plan is accepted, a transaction is concluded between the lower aggregator E3 and the upper aggregator E2, thereby increasing the possibility of a transaction being concluded in the electricity market compared to when an alternative plan is not proposed.

In this embodiment, when the aggregated chargeable/dischargeable power (available power) does not meet the requested plan, it is determined whether the available power meets the requested plan when the storage device 80 owned by the lower aggregator E3 that operates (manages) the server 30 is used as a DER (power adjustment resource) (S26, 27). If the available power meets the requested plan when the storage device 80 is used as a power adjustment resource, the request of the upper aggregator E2 can be met, thereby increasing the likelihood of a transaction being concluded between the lower aggregator E3 and the upper aggregator E2.

In this embodiment, when aggregating chargeable/dischargeable power, if the DER (power regulation resource) is a battery 100 mounted on an electric vehicle, the chargeable/dischargeable power is calculated taking into account the limitations of the battery 100 (S50). If the aggregated chargeable/dischargeable power (capable power) does not meet the requested plan, the limitations of the battery 100 are relaxed and the chargeable/dischargeable power is re-aggregated (S52, S53, S30). If the re-aggregated chargeable/dischargeable power meets the requested plan (positive determination in S31), the request can be met, increasing the likelihood of a transaction being concluded between the lower-level aggregator E3 and the upper-level aggregator E2.

In the above embodiment, the processes of S5 and S6 may be omitted, and if the alternative plan is not accepted by the server 20, the transaction between the lower-level aggregator E3 and the upper-level aggregator E2 may not be concluded.

In the above embodiment, the processes of S26 and S27 may be omitted, and the processes of S28 to S31, S52, and S53 may be omitted. Also, in the above embodiment, the processes of S26 to S31, S52, and S53 may be omitted. Furthermore, the processes of S28 to S31 may be executed following S25, and S26 and S27 may be executed after S31.

The embodiments disclosed herein should be considered in all respects to be illustrative and not restrictive. The scope of the present invention is indicated by the claims, not by the description of the above embodiments, and is intended to include all modifications within the meaning and scope of the claims.

1 Power management system, 10 Server, 11 Power plant, 12 Power transmission and distribution equipment, 13 Smart meter, 20 Server, 30 Server, 31 Control device, 32 Storage device, 33 Communication device, 40 EVSE, 41 Control unit, 42 Communication unit, 43 Power supply circuit, 44 Charging and discharging cable, 45 Connector, 50 Vehicle, 60 EMS network, 70 HEMS, 71 Control device, 72 Storage device, 73 Communication device, 80 Power storage device, 90 Solar power generation device, 100 Battery, 110 ECU, 120 Inlet, 130 Charging and discharging circuit, 140 Communication equipment, E1 Power company, E2 Upper aggregator, E3 Lower aggregator, PG Power system.

Claims (3)

A power management system that controls a plurality of power regulation resources that can be electrically connected to a power grid,
a first server that formulates a request plan based on an adjustment amount requested from the power grid;
a second server that acquires the request plan formulated by the first server and issues a charge/discharge command to the power adjustment resource owned by a contracted consumer ;
The second server
aggregating chargeable and dischargeable power of the power adjustment resource based on the request plan;
When the aggregated chargeable/dischargeable power does not meet the requested plan, an alternative plan is created, and control of the power adjustment resource based on the alternative plan is proposed to the first server. the second server is a server managed by a resource aggregator,
the resource aggregator has a power storage device;
The second server
When the aggregated chargeable/dischargeable power does not satisfy the required plan, determining whether the chargeable/dischargeable power satisfies the required plan when the power storage device is used as the power adjustment resource;
2. The power management system according to claim 1, wherein, even when the storage device is used as the power adjustment resource, when the chargeable/dischargeable power does not satisfy the required plan, an alternative plan is created and control of the power adjustment resource based on the alternative plan is proposed to the first server. The second server
When aggregating the chargeable and dischargeable power of the power adjustment resource based on the request plan, if the power adjustment resource is an on-board power storage device mounted on a vehicle, aggregating the chargeable and dischargeable power taking into account limitations of the on-board power storage device;
When the aggregated chargeable/dischargeable power does not satisfy the required plan, the restrictions on the vehicle-mounted power storage device are relaxed and the chargeable/dischargeable power is aggregated again;
2. The power management system according to claim 1 , wherein when the re-aggregated chargeable/dischargeable power does not meet the required plan, the alternative plan is created and control of the power adjustment resource based on the alternative plan is proposed to the first server.