Power management system
The power management system addresses high communication costs by allowing the controller to manage power consumption locally and selectively transmit data, reducing unnecessary communication and optimizing resource usage.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- TOYOTA JIDOSHA KK
- Filing Date
- 2024-11-08
- Publication Date
- 2026-05-20
AI Technical Summary
The high communication volume between the controller and the server in power management systems increases the resource cost due to the implementation of control logic in a cloud-based server, which lacks control logic in consumer facilities.
A power management system with a controller that acquires and selectively transmits information to a server, reducing unnecessary communication by determining transmission based on predefined conditions such as non-peak consumption times and demand response periods, and controlling devices locally.
Reduces the amount of communication between the controller and the server, thereby lowering resource costs and optimizing power management efficiency.
Smart Images
Figure 2026083843000001_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to a power management system, and more particularly, to a power management system that manages the power consumption of a consumer facility.
Background Art
[0002] Conventionally, power management systems for managing the power consumption of consumer facilities have been developed. For example, Japanese Unexamined Patent Application Publication No. 2015-056996 (Patent Document 1) discloses a peak cut device including a controller that drives and controls a bidirectional inverter so that an average power value over a certain period does not exceed a predetermined power value based on the power measured by a pulse detector.
Prior Art Documents
Patent Documents
[0003] <*
Patent Document 1
Patent Document 2
Patent Document 3
Summary of the Invention
Problems to be Solved by the Invention
[0004] In recent years, from the viewpoints of function upgrade and implementation of demand response, the control logic of the controller included in the peak cut device is generally implemented in a server installed in the cloud. That is, the controller installed in the consumer facility does not have control logic and operates as a gateway for transmitting information between the server and each device installed in the consumer facility. In this case, the controller transmits the information acquired from each device to the server and receives a control command indicating the control content of each device from the server. Therefore, the communication volume between the controller and the server increases. As a result, the cost of the resources constituting the server becomes high.
[0005] This disclosure was made to solve the above-mentioned problems, and its purpose is to provide a power management system that can reduce the amount of communication between the controller and the server. [Means for solving the problem]
[0006] A power management system relating to a certain aspect of this disclosure manages the power consumption of a customer facility. The power management system includes a controller that acquires information from each of several devices installed at the customer facility and controls one or more of the multiple devices according to control commands, and a server that generates control commands based on the information. The controller switches whether or not to transmit information to the server. [Effects of the Invention]
[0007] According to the power management system described herein, the amount of communication between the controller and the server is reduced. [Brief explanation of the drawing]
[0008] [Figure 1] This figure shows the overall configuration of the power management system according to the embodiment. [Figure 2] This diagram shows a flowchart illustrating the processing flow in an energy management system. [Figure 3] Figure 2 is a flowchart showing the flow of the first pre-preparation process in step S2. [Figure 4] Figure 2 is a flowchart showing the flow of the second pre-preparation process in step S2. [Figure 5] Figure 2 shows an example of a condition table that may be used in step S2. [Figure 6] Figure 2 is a flowchart showing the processing flow of the subroutine in step S2. [Modes for carrying out the invention]
[0009] Embodiments of this disclosure will be described in detail below with reference to the drawings. In the drawings, the same or corresponding parts are denoted by the same reference numerals and their descriptions will not be repeated.
[0010] Figure 1 shows the overall configuration of a power management system according to an embodiment. The power management system 1 shown in Figure 1 manages the power consumption of a customer facility 2. The customer facility 2 includes single-family homes, apartment buildings, shops, factories, commercial facilities, medical facilities, educational facilities, public facilities, buildings, etc.
[0011] As shown in Figure 1, the power management system 1 comprises an energy management system controller (hereinafter referred to as "EMS controller 10"), a plurality of devices 20 installed at the customer facility 2, and an energy management server 30. The EMS controller 10 is connected to the energy management server 30 via a communication network. The communication network typically includes the internet.
[0012] The multiple devices 20 include devices for measuring power consumption and electrical equipment that consumes power. For example, the multiple devices 20 include a smart meter 21, a charge / discharge device 22, an air conditioner 23, one or more electrical devices 24, and one or more power measuring instruments 25.
[0013] The smart meter 21 has the function of measuring the amount of electricity consumed at the customer's facility and the function of communicating the measurement results to the power company, etc.
[0014] The charging / discharging device 22 charges the electric vehicle 5 and discharges the electricity stored in the electric vehicle 5 to the customer facility 2. The charging / discharging device 22 is also called V2H (Vehicle to Home).
[0015] One or more electrical devices 24 include various electrical devices other than the air conditioner 23. Each of the one or more power meters 25 measures the power consumed by the corresponding electrical device 24.
[0016] The EMS controller 10 is installed in the customer facility 2. The EMS controller 10 acquires information 3 from each of a plurality of devices 20 installed in the customer facility 2. The EMS controller 10 transmits the information 3 to the energy management server 30. Further, the EMS controller 10 receives a control command 4 from the energy management server 30. The EMS controller 10 controls one or more controlled devices among the plurality of devices 20 according to the control command 4.
[0017] The information 3 indicates the amount of power measured by the corresponding device or the state of the corresponding device. The information 3 includes information 3a, 3b, 3c, 3d, and 3e acquired from the smart meter 21, the charge / discharge device 22, the air conditioner 23, the electrical equipment 24, and the power meter 25, respectively.
[0018] The information 3a indicates the amount of power purchased and sold for each time period (e.g., 30 minutes) in the customer facility 2. The information 3b indicates the state of the charge / discharge device 22 (including the presence or absence of connection of the electric vehicle ⑤, the amount of charge / discharge, etc.). The information 3b is an example of the "first information" of the present disclosure. The information 3c indicates the state of the air conditioner 23 (including the operation mode, set temperature, etc.). The information 3c is an example of the "second information" of the present disclosure. The information 3d indicates the state of the electrical equipment 24. The information 3e indicates the amount of power consumption measured by the power meter 25.
[0019] The control command 4 indicates the control content for the controlled device. For example, the control content for the charge / discharge device 22 includes start of discharge, stop of discharge, change in the amount of discharge per unit time, start of charge, stop of charge, change in the amount of charge per unit time, etc. The control content for the air conditioner 23 includes switching of the operation mode and change in the set temperature.
[0020] The EMS controller 10 is realized by general-purpose computing resources. That is, the EMS controller 10 includes a processor 11, a memory 12, a storage 13, and a communication interface 14.
[0021] The processor 11 includes a CPU (Central Processing Unit) or an MPU (Micro Processing Unit). The processor 11 reads the program stored in the storage 13 and loads it into the memory 12. The processor 11 executes the loaded program. The memory 12 includes, for example, a volatile storage device such as DRAM (Dynamic Random Access Memory) or SRAM (Static Random Access Memory). The storage 13 includes, for example, a non-volatile storage device such as an HDD (Hard Disk Drive), SSD (Solid State Drive), or flash memory. The storage 13 stores the program executed by the processor 11. The communication interface 14 communicates with the energy management server 30 via a communication network.
[0022] The energy management server 30 is installed, for example, in the cloud. The energy management server 30 receives information 3 from the EMS controller 10 and generates a control command 4 based on the information 3. Specifically, the energy management server 30 performs calculations using the information 3 according to a predetermined control logic. The control logic may employ a known method. Based on the calculation results, the energy management server 30 determines whether or not it is necessary to generate a control command. If the energy management server 30 determines that it is necessary to generate a control command, it generates a control command 4 based on the information 3. For example, the energy management server 30 generates a control command 4 to bring the state of the controlled device indicated by the information 3 closer to a standard state. The standard state is a state in which power consumption can be suppressed and is predetermined.
[0023] For example, the energy management server 30 determines that it is necessary to generate a control command 4 to reduce the amount of electricity purchased at the customer facility 2 when the amount of electricity purchased exceeds a preset threshold value. The threshold value is set based on the contract between the customer and the power company. Specifically, the threshold value is the contracted power value or the contracted power value multiplied by a predetermined coefficient (e.g., 0.9 or 0.8).
[0024] Alternatively, the energy management server 30 may determine that it is necessary to generate a control command 4 to reduce the amount of electricity purchased in response to the activation of a demand response request.
[0025] The control command 4 for reducing the amount of electricity purchased includes, for example, a command to stop the air conditioner 23, a command to raise the set temperature of the air conditioner 23 during cooling operation, a command to lower the set temperature of the air conditioner 23 during heating operation, or a command to stop charging by the charge / discharge device 22. Furthermore, the control command 4 for reducing the amount of electricity purchased may also include a command to start discharging by the charge / discharge device 22. For example, if the information 3c of the air conditioner 23 indicates a cooling operation mode and the set temperature indicated by the information 3c is lower than the standard temperature, the energy management server 30 generates a control command 4 to raise the set temperature of the air conditioner 23 to the standard temperature. Alternatively, if the amount of charge per unit time indicated by the information 3b of the charge / discharge device 22 is higher than the standard amount, the energy management server 30 generates a control command 4 to lower the amount of charge per unit time in the charge / discharge device 22, or a control command 4 to stop charging by the charge / discharge device 22.
[0026] The energy management server 30 is implemented using general-purpose computing resources. Specifically, the energy management server 30 includes a processor 31, memory 32, storage 33, and a communication interface 34.
[0027] The processor 31 includes a CPU or MPU, etc. The processor 31 reads the program stored in the storage 33 and loads it into the memory 32. The processor 31 executes the loaded program. The memory 32 includes a volatile storage device such as DRAM or SRAM. The storage 33 includes a non-volatile storage device such as an HDD, SSD or flash memory, etc. The storage 33 stores the program executed by the processor 31. The communication interface 34 communicates with the EMS controller 10 via a communication network.
[0028] In this embodiment, the EMS controller 10 switches whether or not to transmit information 3 to the energy management server 30. This reduces the amount of communication between the EMS controller 10 and the energy management server 30.
[0029] Figure 2 is a flowchart illustrating the processing flow in an energy management system. The flow shown in Figure 2 is performed periodically (for example, every 30 minutes).
[0030] In step S1, the EMS controller 10 acquires information 3 from each of the multiple devices 20 installed at the customer facility 2.
[0031] In the next step S2, the EMS controller 10 determines whether or not it is possible to transmit information 3 to the energy management server 30. The determination of whether or not to transmit information 3 may be made for each piece of equipment 20.
[0032] If the transmission of information 3 is feasible (YES in step S2), in step S3, the EMS controller 10 transmits information 3 to the energy management server 30. However, if it is determined that the transmission of information 3 is feasible for only some of the multiple devices 20, the EMS controller 10 transmits only the information 3 obtained from those some devices to the energy management server 30.
[0033] In step S4, following step S3, the energy management server 30 performs calculations using information 3 according to predetermined control logic. In the next step S5, the energy management server 30 determines whether or not it is necessary to generate control command 4 based on the calculation results.
[0034] If it is necessary to generate a control command (YES in step S5), in step S6, the energy management server 30 generates a control command 4 based on the information 3 and outputs the control command 4 to the EMS controller 10.
[0035] In step S7, following step S6, the EMS controller 10 controls one or more controlled devices in accordance with the control command 4 received from the energy management server 30.
[0036] After step S7, the process ends. The process also ends if the transmission of information 3 is not possible (NO in step S2), or if the generation of control commands is unnecessary (NO in step S5).
[0037] Refer to Figures 3 to 6 to explain the details of step S2. Figure 3 is a flowchart showing the flow of the first preparatory process in step S2 shown in Figure 2. The flow shown in Figure 3 is performed, for example, by the energy management server 30.
[0038] In step S11, the energy management server 30 acquires actual power consumption data from the customer facility 2. The actual power consumption data shows the history of power consumption (typically purchased electricity) every 30 minutes as measured by the smart meter 21. The actual power consumption data is stored in the EMS controller 10 or the energy management server 30.
[0039] In the next step S12, the energy management server 30 determines, based on actual power consumption data, the time period during which no peak power consumption is expected to occur as the first non-transmittable time period. For example, based on actual data from the past year, the energy management server 30 identifies the peak power consumption and calculates a baseline value by multiplying the peak power consumption by a predetermined ratio (e.g., 70%, 50%, or 30%). Based on the actual data, the energy management server 30 determines, as the first non-transmittable time period, the time period during which power consumption is below the baseline value within each 30-minute time period each day. Typically, nighttime hours are determined as the first non-transmittable time period. The determined first non-transmittable time period is communicated to the EMS controller 10 and held by the EMS controller 10. After step S12, the first pre-preparation process is completed.
[0040] Note that the flow shown in Figure 3 may also be performed by the EMS controller 10. In this case, the EMS controller 10 retains the determined first transmission unavailable time period.
[0041] Figure 4 is a flowchart showing the flow of the second pre-preparation process in step S2 shown in Figure 2. The flow shown in Figure 4 is performed, for example, by the energy management server 30.
[0042] In step S21, the energy management server 30 acquires actual demand response request data. The actual demand response request data indicates the date and time when the demand response was requested. Demand responses include upward DR (demand response) which encourages an increase in electricity demand, and downward DR which encourages a decrease in electricity demand. In this embodiment, downward DR is the main focus. The actual demand response request data is created based on the history of demand response requests from the power company and is stored in the energy management server 30.
[0043] In the next step S22, the energy management server 30 determines, based on actual demand response request data, a period during which no demand response requests are expected to occur as a non-transmission period. For example, based on actual data from the past year, the energy management server 30 determines all or part of a target period during which no demand response requests have occurred for a predetermined number of consecutive days as a non-transmission period. For example, the non-transmission period is the period during which the first predetermined number of days from the start date and the second predetermined number of days from the end date are excluded from the target period. The first and second predetermined number of days are predetermined, for example, 1 day, 5 days, 10 days, etc. Typically, the spring or autumn period is determined as the non-transmission period. The determined non-transmission period is communicated to the EMS controller 10 and retained by the EMS controller 10.
[0044] In the next step S23, the energy management server 30 determines a second uncommunicated time period based on actual demand response request data, during which no demand response requests are expected to occur. For example, based on actual data from the past year, the energy management server 30 determines a second uncommunicated time period during which no demand response requests have ever occurred. Typically, nighttime hours are determined as the second uncommunicated time period. The second uncommunicated time period may overlap with the first uncommunicated time period. The determined second uncommunicated time period is communicated to the EMS controller 10 and held by the EMS controller 10. After step S23, the second pre-preparation process is completed.
[0045] Note that the flow shown in Figure 4 may also be performed by the EMS controller 10. In this case, the EMS controller 10 retains the determined transmission unavailable period and the second transmission unavailable period.
[0046] Both the first preparatory process shown in Figure 3 and the second preparatory process shown in Figure 4 may be performed, or only one of them may be performed.
[0047] Figure 5 shows an example of a condition table that may be used in step S2 shown in Figure 2. The condition table 50 shown in Figure 5 is created in advance and stored in the EMS controller 10.
[0048] As shown in Figure 5, the condition table 50 associates specific equipment among the multiple pieces of equipment 20 installed in the customer facility 2 with transmission failure conditions. For example, the condition table 50 shows the transmission failure condition "No electric vehicle is connected" corresponding to the charge / discharge device 22. The condition table 50 also shows the transmission failure condition "No change in operating status" corresponding to the air conditioner 23.
[0049] Figure 6 is a flowchart showing the processing flow of the subroutine in step S2 shown in Figure 2. The flow shown in Figure 6 is performed for each of the multiple devices 20 installed at the customer facility 2. Hereinafter, the device selected as the target of the flow shown in Figure 6 from among the multiple devices 20 will be referred to as the "device of interest".
[0050] In step S31, the EMS controller 10 determines whether the current timing falls within the transmission unavailable period, the first transmission unavailable time period, or the second transmission unavailable time period.
[0051] If the current timing falls within the transmission unavailable period, the first transmission unavailable time period, or the second transmission unavailable time period (YES in step S31), in step S32, the EMS controller 10 decides not to transmit the information 3 acquired from the device of interest to the energy management server 30.
[0052] If the current timing is not included in the transmission unavailable period, the first transmission unavailable time period, or the second transmission unavailable time period (NO in step S31), the process proceeds to step S33. In step S33, the EMS controller 10 determines whether the device of interest is registered in the condition table 50.
[0053] If the device of interest is registered in the condition table 50 (YES in step S33), the process proceeds to step S34. In step S34, the EMS controller 10 determines whether the state of the device of interest satisfies the transmission failure condition corresponding to the device of interest. The state of the device of interest is identified based on the information 3 obtained from the device of interest. The transmission failure condition corresponding to the device of interest is identified from the condition table 50 shown in Figure 5.
[0054] If the status of the device of interest satisfies the conditions for non-transmission (YES in step S34), the process proceeds to step S32. As a result, the EMS controller 10 decides not to transmit the information 3 obtained from the device of interest to the energy management server 30.
[0055] If the device of interest is not registered in the condition table 50 (NO in step S33), or if the status of the device of interest does not satisfy the conditions for non-transmission (NO in step S34), the process proceeds to step S35. In step S35, the EMS controller 10 decides to transmit the information 3 obtained from the device of interest to the energy management server 30.
[0056] After step S32 or step S35, the flow shown in Figure 6 is performed for the next device of interest. Once the flow shown in Figure 6 has been performed for all devices of interest, step S2 is completed.
[0057] As described above, the first non-transmission period is a period during which it is not expected that a peak in power consumption will occur. If a peak in power consumption does not occur, the energy management server 30 is unlikely to generate a control command 4. Therefore, during the first non-transmission period, it is unnecessary to transmit information 3 for generating the control command 4. According to the flow shown in Figure 6, the EMS controller 10 does not transmit information 3 to the energy management server 30, depending on whether the current timing falls within the first non-transmission period. This avoids the transmission of unnecessary information 3 and reduces the amount of communication between the EMS controller 10 and the energy management server 30.
[0058] The communication blackout period is a period during which no demand response requests are expected to occur. The second communication blackout time period is also a period during which no demand response requests are expected to occur. If no demand response requests occur, the energy management server 30 is unlikely to generate control command 4. Therefore, during the communication blackout period or the second communication blackout time period, it is unnecessary to transmit information 3 for generating control command 4. According to the flow shown in Figure 6, the EMS controller 10 does not transmit information 3 to the energy management server 30 depending on whether the current timing falls within the communication blackout period or the second communication blackout time period. This avoids the transmission of unnecessary information 3 and reduces the amount of communication between the EMS controller 10 and the energy management server 30.
[0059] If the electric vehicle 5 is not connected to the charge / discharge device 22, the charge / discharge device 22 cannot charge the electric vehicle 5 or discharge the electric vehicle. Therefore, the information 3b obtained from the charge / discharge device 22 is not used to generate the control command 4 for the charge / discharge device 22. According to the condition table 50 shown in Figure 5 and the flow shown in Figure 6, the EMS controller 10 does not transmit the information 3b to the energy management server 30 in response to the fact that the electric vehicle 5 is not connected to the charge / discharge device 22. This avoids the transmission of unnecessary information 3 and reduces the amount of communication between the EMS controller 10 and the energy management server 30.
[0060] If there is no change in the operating state of the air conditioner 23, the information 3c obtained from the air conditioner 23 also remains unchanged. In this case, the energy management server 30 can use the previously received information 3c. Therefore, it does not need to resend the information 3c. According to the condition table 50 shown in Figure 5 and the flow shown in Figure 6, the EMS controller 10 does not transmit information 3c to the energy management server 30 in response to the fact that there is no change in the operating state of the air conditioner 23. This avoids the transmission of unnecessary information 3, and reduces the amount of communication between the EMS controller 10 and the energy management server 30. The EMS controller 10 can determine that there is no change in the operating state of the air conditioner 23 if the state indicated by the previously obtained information 3c from the air conditioner 23 matches the state indicated by the currently obtained information 3c.
[0061] Step S31 shown in Figure 6 may also be performed by the energy management server 30. The energy management server 30 notifies the EMS controller 10 of a flag indicating whether periodic transmission is necessary, according to the determination result of step S31. Specifically, if the current timing falls within the transmission unavailable period, the first transmission unavailable time period, or the second transmission unavailable time period, the energy management server 30 notifies the EMS controller 10 of a flag indicating that periodic transmission is not necessary. If the current timing does not fall within the transmission unavailable period, the first transmission unavailable time period, or the second transmission unavailable time period, the energy management server 30 notifies the EMS controller 10 of a flag indicating that periodic transmission is necessary.
[0062] If the flag indicates that periodic transmission is not required, the EMS controller 10 proceeds to step S32. If the flag indicates that periodic transmission is required, the EMS controller 10 proceeds to step S32. In this case as well, the EMS controller 10 does not transmit information 3 to the energy management server 30, depending on whether the current timing falls within the transmission unavailable period, the first transmission unavailable time period, or the second transmission unavailable time period.
[0063] The embodiments disclosed herein should be considered in all respects to be illustrative and not restrictive. The scope of this disclosure is indicated by the claims rather than by the description of the embodiments above, and all modifications within the meaning and scope equivalent to the claims are intended to be included. [Explanation of Symbols]
[0064] 1 Power management system, 2 Consumer facilities, 3,3a~3e Information, 4 Control command, 5 Electric vehicles, 10 Controller, 11,31 Processor, 12,32 Memory, 13,33 Storage, 14,34 Communication interface, 20 Equipment, 21 Smart meter, 22 Charge / discharge device, 23 Air conditioner, 24 Electrical equipment, 25 Power meter, 30 Energy management server, 50 Condition table.
Claims
1. A power management system for managing the power consumption of customer facilities, A controller that acquires information from each of the multiple devices installed at the customer facility and controls one or more of the multiple devices according to a control command, The system includes a server that generates the control command based on the aforementioned information, The controller is a power management system that switches whether or not to perform the transmission of the information to the server.
2. The controller or server determines, based on the actual power consumption at the customer facility, the time period during which it is not expected that the peak power consumption will occur. The power management system according to claim 1, wherein the controller does not transmit the information to the server depending on whether the current timing falls within the time period.
3. The controller or server determines, based on the history of demand response requests, a period or time period during which it is expected that no demand response requests will occur. The power management system according to claim 1, wherein the controller does not transmit the information to the server depending on whether the current timing falls within the period or time zone.
4. The aforementioned plurality of devices include a charge / discharge device for charging and discharging electric vehicles, The aforementioned information includes first information obtained from the charging and discharging device, The power management system according to any one of claims 1 to 3, wherein the controller does not transmit the first information to the server in response that the electric vehicle is not connected to the charge / discharge device.
5. The aforementioned multiple devices include an air conditioner, The aforementioned information includes second information obtained from the air conditioner, The power management system according to any one of claims 1 to 3, wherein the controller does not transmit the second information to the server in response to no change in the operating state of the air conditioner.