Power deviation reason processing method, energy management equipment and system
By using visual charts to handle power deviations in power trading scenarios, the problem of low efficiency in manual recording is solved, and efficient and accurate recording and reporting of deviation causes are achieved.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-12-12
- Publication Date
- 2026-03-24
AI Technical Summary
In the context of electricity trading, existing technologies require manual recording of time, power deviations, and causes using Excel spreadsheets, which is inefficient and involves a large amount of data, making it time-consuming and labor-intensive.
By acquiring the power deviation at each time granularity of the target site and displaying and editing the reasons for the deviation in a visual chart, users can batch replace and respond to reports, reducing manual data entry time.
It significantly improves the efficiency of recording and reporting deviation causes, reduces the probability of errors, adapts to the processing needs of a large number of records, ensures timeliness and accuracy, and provides efficient data support for compliant settlement of power transactions and analysis of power grid operation.
Smart Images
Figure CN121724261A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of power trading data processing technology, and in particular to a method for handling power deviation causes, an energy management device and system. Background Technology
[0002] In power trading scenarios, deviations often occur between actual power generation / consumption and the power agreed upon in the trading contract due to various factors such as equipment operating status and grid dispatch adjustments. According to relevant power trading rules, the specific reasons for these deviations must be recorded and reported, and the time granularity of the deviation records must reach 15 minutes, covering the entire 24 hours, resulting in a large number of deviation records that need to be reported daily.
[0003] Currently, it is necessary to manually record time, power deviation, and reasons for deviation using Excel spreadsheets, which is time-consuming, labor-intensive, and inefficient. Summary of the Invention
[0004] In view of the above problems, this application provides a method for handling power deviation causes, an energy management device, and a system to significantly improve the efficiency of recording and reporting deviation causes. The specific solution is as follows:
[0005] The first aspect of this application provides a method for handling power deviation, including:
[0006] Obtain the power deviation of the target site at each time granularity within the target date. The power deviation is the deviation between the actual power generation and the agreed power generation or the deviation between the actual power consumption and the agreed power consumption.
[0007] The power deviation of the target site at each time granularity within the target date and the original cause of the deviation are displayed in the form of a visual chart;
[0008] Based on the target time period input by the user, the power deviation of the target site at each time granularity within the target time period on the target date and the original cause of the deviation are displayed in the form of a visual chart.
[0009] Based on the user-inputted cause of deviation and at least one target time granularity within the target time period selected by the user, the original cause of deviation at the at least one target time granularity is replaced with the target cause of deviation.
[0010] In response to the user's input reporting command, the power deviation of the target site at each time granularity within the target date and the reason for the deviation are reported.
[0011] In one possible implementation, displaying the power deviation of the target site at each time granularity within the target date and the original cause of the deviation in the form of a visual chart includes:
[0012] If the target site has not edited the deviation reason on the target date, the pre-configured default deviation reason will be determined as the original deviation reason for the target site at each time granularity within the target date, and displayed in the form of a visual chart.
[0013] In one possible implementation, replacing the original cause of deviation at the at least one target time granularity with the target deviation cause based on the user-inputted cause of deviation and the user-selected cause of deviation within the target time period includes:
[0014] When the cause of the target deviation is a non-custom type, the original deviation cause of the at least one target time granularity is replaced with the target deviation cause. The non-custom type deviation cause includes at least one of the following: equipment failure deviation, deviation caused by power grid dispatch, equipment debugging deviation, algorithm debugging deviation, and normal equipment loss deviation.
[0015] If the cause of the target deviation is custom, the user is prompted to enter a custom deviation cause, and the original deviation cause of the at least one target time granularity is replaced with the custom deviation cause entered by the user.
[0016] In one possible implementation, after replacing the original cause of deviation at the at least one target time granularity with the target cause of deviation, the method further includes:
[0017] In response to the rollback operation for the target deviation cause, all deviation causes within the target time period corresponding to the time granularity of the target deviation cause are uniformly replaced with the default deviation cause.
[0018] In one possible implementation, after displaying the power deviation of the target site at each time granularity within the target time period on the target date, and the reasons for the deviation, in the form of a visual chart, the method further includes:
[0019] In response to the rollback operation for the deviation reasons of the target time period, the deviation reasons for each time granularity within the target time period are uniformly replaced with the default deviation reasons.
[0020] In one possible implementation, the method further includes:
[0021] When a time granularity is selected, the power deviation and the reason for the deviation corresponding to that time granularity are displayed in a floating manner.
[0022] In one possible implementation, the method further includes:
[0023] In response to the user's click operation on the time viewer, a calendar interface within a preset date range of the target date is displayed, and the dates on the calendar interface where the reason for the deviation has been edited are marked.
[0024] In one possible implementation, the time granularity corresponding to different causes of deviation is displayed differently in the visualization chart.
[0025] A second aspect of this application provides an energy management device, comprising: at least one processor and a memory connected to the processor, wherein:
[0026] The memory is used to store computer programs;
[0027] The processor is used to execute the computer program so that the energy management device can implement the power deviation cause handling method of the first aspect or any implementation thereof.
[0028] A third aspect of this application provides an energy management system, comprising:
[0029] Energy management equipment;
[0030] A power conversion device at at least one site that is communicatively connected to the energy management device;
[0031] The DC side of the power conversion device is connected to a DC power supply, and the AC side of the power conversion device is connected to the power grid. The energy management device is communicatively connected to the power conversion device and is configured to obtain the actual power generation or actual power consumption of the power conversion device and store it in time granularity by station.
[0032] The DC power supply includes at least one of battery power and photovoltaic power;
[0033] The energy management device is also configured to implement the power deviation cause handling method of the first aspect or any implementation of the first aspect.
[0034] By employing the aforementioned technical solution, this application provides a method for handling power deviation causes. This method first acquires the power deviation at each time granularity of the target site within a target date, then visually presents the power deviation and original causes for the entire period within the target date in a graphical form. It supports users inputting a specific target time period, facilitating the selection of target deviation causes and at least one target time granularity. This allows for batch replacement of deviation causes at target time granularities, ultimately responding to reporting commands to complete data reporting. This effectively solves the tedious problem of manually recording deviation information line by line in Excel spreadsheets in existing technologies, significantly reducing the manual cost and time consumption of data entry, and significantly improving the efficiency of deviation cause recording and reporting. Simultaneously, the graphical display format not only allows users to quickly view and verify the correlation between power deviations and deviation causes at different time granularities, but also provides an intuitive understanding of the daily power deviation trend, reducing the probability of errors in deviation cause recording. Furthermore, the batch replacement function adapts to the processing needs of a large number of daily deviation records, further ensuring the timeliness and accuracy of deviation cause reporting, and providing efficient and reliable data support for compliant power trading settlement and grid operation analysis. Attached Figure Description
[0035] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale.
[0036] Figure 1 A flowchart illustrating a method for handling power deviation issues provided in an embodiment of this application;
[0037] Figure 2 This application provides a schematic diagram of a deviation cause graph interface.
[0038] Figure 3 This is a schematic diagram of a deviation cause reporting interface provided in an embodiment of this application;
[0039] Figure 4 This is a schematic diagram of another deviation cause reporting interface provided in an embodiment of this application;
[0040] Figure 5 This is a schematic diagram of another deviation cause reporting interface provided in an embodiment of this application;
[0041] Figure 6 This is a schematic diagram of another deviation cause reporting interface provided in an embodiment of this application;
[0042] Figure 7 This is a schematic diagram of another deviation cause reporting interface provided in an embodiment of this application;
[0043] Figure 8 This is a schematic diagram of another deviation cause reporting interface provided in an embodiment of this application;
[0044] Figure 9 This is a schematic diagram of another deviation cause reporting interface provided in an embodiment of this application;
[0045] Figure 10 This is a schematic diagram of another deviation cause reporting interface provided in an embodiment of this application;
[0046] Figure 11 This is a schematic diagram of another deviation cause reporting interface provided in an embodiment of this application;
[0047] Figure 12 This is a schematic diagram of another deviation cause reporting interface provided in an embodiment of this application;
[0048] Figure 13 This is another schematic diagram of the deviation cause quantity graph interface provided in the embodiments of this application;
[0049] Figure 14 This is a schematic diagram of the structure of an energy management device provided in an embodiment of this application. Detailed Implementation
[0050] The embodiments of this application are described below with reference to the accompanying drawings. The terminology used in the implementation section of this application is for explaining specific embodiments only and is not intended to limit the scope of this application.
[0051] The embodiments of this application will now be described with reference to the accompanying drawings. Those skilled in the art will recognize that, with technological advancements and the emergence of new scenarios, the technical solutions provided in the embodiments of this application are equally applicable to similar technical problems.
[0052] The terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such terms are interchangeable where appropriate; this is merely a way of distinguishing objects with the same attributes in the embodiments of this application. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion, so that a process, method, system, product, or apparatus that comprises a series of elements is not necessarily limited to those elements, but may include other elements not explicitly listed or inherent to those processes, methods, products, or apparatuses.
[0053] Reference Figure 1 , Figure 1 This is a flowchart illustrating a method for handling power deviation issues provided in an embodiment of this application, as shown below. Figure 1As shown in the embodiment of this application, a method for handling power deviation can include steps 101 to 105, which are described in detail below.
[0054] 101: Obtain the power deviation of the target site at each time granularity within the target date.
[0055] The target site can be a photovoltaic power station (i.e., a power generation site), a charging station (i.e., a power consumption site), or a site that includes both photovoltaic power generation equipment and power consumption equipment.
[0056] Power deviation is the deviation between actual power generation and agreed power generation, or the deviation between actual power consumption and agreed power consumption. Here, agreed power generation and agreed power consumption are the power agreed in the transaction contract in the power transaction of the target site.
[0057] The time granularity is the time granularity agreed upon in the power trading contract, such as 15 minutes.
[0058] The target date can be either the date on which no power deviation has been reported or the date on which a power deviation has been reported.
[0059] In one possible implementation, to prevent the cause of power deviation on a reported power deviation date from being tampered with, the cause of power deviation on a date when no power deviation has been reported can be set to have edit permissions, while the cause of power deviation on a reported power deviation date can only have view permissions and not edit permissions.
[0060] The power deviation of the target site at each time granularity within the target date can be stored in a database. The database can also store the power deviation of at least one site at each time granularity within different dates. In one possible implementation, after the user selects the target site and the target date, the power deviation of the target site at each time granularity within the target date is obtained by reading the database.
[0061] 102: Display the power deviation of the target site at each time granularity within the target date and the original cause of the deviation in the form of a visual chart.
[0062] Visual charts can be bar charts, line charts, dot distribution charts, etc., and this embodiment does not impose specific limitations.
[0063] The original reason for the deviation indicates the reason for the deviation before this edit.
[0064] If the cause of deviation for the target site on the target date has been edited, the cause of deviation is obtained while reading the database to retrieve the power deviation of the target site at each time granularity within the target date.
[0065] If the deviation reasons for the target site on the target date have not been edited, one possible implementation is to store the default deviation reasons for the target site at each time granularity within the target date in the database (the default deviation reasons are pre-configurable). When reading the database to obtain the power deviation of the target site at each time granularity within the target date, the default deviation reasons are obtained and used as the original deviation reasons. In another possible implementation, the deviation reasons for the target site at each time granularity within the target date are empty in the database. When displaying the power deviation and original deviation reasons for the target site at each time granularity within the target date in the form of a visual chart, the pre-configured default deviation reasons are displayed as the original deviation reasons.
[0066] For an example of a visual chart using a bar chart, please refer to [link / reference]. Figure 2 The diagram showing the causes of deviation is shown. Figure 2 The chart consists of three visualization areas from top to bottom. The top visualization area is the cause-colored area, which displays the power deviation of a certain site at each time granularity as of June 1, 2024, in the form of a bar chart. The height of the bar represents the power deviation at that time granularity. The middle visualization area includes a line chart showing the power deviation trend within that date and a deviation cause icon. According to the deviation cause icon, the original deviation cause at each time granularity is the normal wear and tear deviation of the equipment. The bottom visualization area is the time area.
[0067] Since the time granularity is relatively small, taking a time granularity of 15 minutes as an example, there are 96 time granularities in a day. In order to avoid displaying and editing the power deviation and deviation reasons of all granularities in the reason color area, which would cause the bar chart to be crowded and prone to misoperation, this embodiment displays all time granularities in a strip form through the time area, so that users can easily select the target time period to be edited.
[0068] 103: Based on the target time period input by the user, display the power deviation of the target site at each time granularity within the target date and target time period, as well as the original reasons for the deviation, in the form of a visual chart.
[0069] The target time period is less than or equal to one day.
[0070] After the user selects the target time period in the time zone, the power deviation and the original cause of the deviation will be displayed in the cause color area. Since the target time period contains fewer time granularities than a whole day, the power deviation and the original cause of the deviation can be displayed more clearly through the visualization chart, making it easier for users to view and edit the deviation cause.
[0071] 104: Based on the user-inputted cause of deviation and at least one target time granularity within the target time period selected by the user, replace the original cause of deviation for at least one target time granularity with the target cause of deviation.
[0072] Users can first select the target deviation cause, and then select at least one corresponding target time granularity to batch replace the original deviation cause of at least one target time granularity with the target deviation cause. Alternatively, users can first select at least one target time granularity, and then select the corresponding target deviation cause to batch replace the original deviation cause of at least one target time granularity with the target deviation cause. This embodiment does not impose any specific limitations.
[0073] return Figure 2 Taking the deviation cause graph shown as an example, the user clicks... Figure 2 The pen-shaped editing button in the upper right corner jumps to... Figure 3 The deviation cause reporting interface shown is relative to... Figure 2 , Figure 3 An icon has been added to display the various reasons for deviations, and a prompt has been added that you can first select the reason for the deviation, and then click on the corresponding time period (i.e., time granularity).
[0074] In one possible implementation, after the user is first redirected to the deviation reason reporting interface of the target site on the target date, the save button is disabled. This forces the user to follow the standard process of "select reason → select time period → save", avoiding invalid data generation and operational errors, ensuring that the deviation reason reporting complies with the power trading rules, and adapting to the core function of batch entry.
[0075] After the user selects equipment malfunction as the cause of the target deviation, such as Figure 4 The deviation reporting interface shown in the image displays a paint bucket cursor, the color of which matches the icon for equipment fault deviations. Clicking the bar corresponding to 06:30 replaces the deviation reason for that bar with a normal equipment wear deviation, and simultaneously displays a floating list of the power deviation and its reason for that time granularity. Similarly, users can click on bars corresponding to other time granularities to perform batch replacements of equipment fault deviations.
[0076] 105: In response to the user's input reporting command, report the power deviation of the current target site at each time granularity within the target date and the reason for the deviation.
[0077] After the user finishes editing the reasons for the deviation, in one possible implementation, clicking the save button will save the power deviation and the reasons for the deviation at each time granularity of the current target site within the target date, and then redirect back to the previous page. Figure 5The deviation cause graph interface shown can be edited to include not only the default deviation causes for each time granularity within the target date at the target site, but also other causes such as... Figure 5 The device fault deviation and the deviation caused by power grid dispatch are shown. Then, you can click the report button to report the power deviation of the target site at each time granularity within the target date and the reason for the deviation with one click. In another possible implementation, save and report are the same button, which can save and report the power deviation of the target site at each time granularity within the target date and the reason for the deviation with one click.
[0078] This embodiment provides a method for handling power deviation causes. It first obtains the power deviation of the target site at each time granularity within the target date, and then presents the power deviation and original deviation cause for the entire time period within the target date in a visual chart. It supports users to input the target time period, making it convenient for users to select the target deviation cause and at least one target time granularity, and realize the batch replacement of the deviation cause at the target time granularity. Finally, it responds to the reporting command to complete the data reporting, which effectively solves the tedious problem of manually recording deviation information line by line through Excel spreadsheets in the prior art, greatly reduces the manual cost and time consumption of data entry, and significantly improves the efficiency of recording and reporting deviation causes.
[0079] Meanwhile, the visual charts not only make it easy for users to quickly view and verify the correlation between power deviations and their causes at different time granularities, but also allow them to intuitively grasp the trend of power deviation changes throughout the day, reducing the probability of errors in recording deviation causes. Furthermore, the batch replacement function is adapted to the processing needs of a large number of deviation records every day, further ensuring the timeliness and accuracy of deviation cause reporting, and providing efficient and reliable data support for compliant settlement of power transactions and grid operation analysis.
[0080] In practical applications, the cause of power deviation is generally the deviation of normal equipment loss. In order to avoid users having to edit the deviation cause for each time granularity, this embodiment pre-configures the default deviation cause.
[0081] In one possible implementation, if the target site has not edited the deviation reason at the target date, the pre-configured default deviation reason is determined as the original deviation reason for the target site at each time granularity within the target date, and displayed in the form of a visual chart. For an example, please refer to... Figure 2 If the deviation reason has not been edited as of June 1, 2024, the power deviation and the default deviation reason - normal equipment loss deviation - will be displayed in the form of a bar chart. If the deviation reason is correct, the user does not need to edit it again, but only needs to modify some deviation reasons in individual cases, which effectively improves the efficiency of editing deviation reasons.
[0082] Considering that the pre-configured deviation reasons may not cover all deviation reasons in actual applications, the power variation reason handling method provided in this embodiment offers non-customized deviation reasons for users to select, and also offers customized deviation reasons for users to input according to actual application scenarios.
[0083] Please see Figure 3 The deviation reason reporting interface shown includes at least one of the following non-custom deviation reasons: equipment failure deviation, deviation caused by power grid dispatch, equipment debugging deviation, algorithm debugging deviation, and normal equipment wear deviation. Users can directly select the appropriate reason when editing the deviation reason. Users can also choose to customize the reason, which will take them to a page like... Figure 6 The deviation reason reporting interface shown in the image changes the cursor to a paint bucket, and the color of the paint bucket is the same as the custom icon color. When the user clicks on the column corresponding to 06:30, the deviation reason corresponding to that column is replaced by the normal equipment loss deviation and then a custom error is displayed. At the same time, the power deviation and deviation reason input box corresponding to that time granularity will be displayed in a floating window, prompting the user to enter a custom deviation reason. The user can enter a specific reason or leave it blank. If no reason is entered, the custom error will be displayed.
[0084] If the reason for deviation at a certain time granularity is edited incorrectly, the user can re-edit the reason for deviation at that time granularity by selecting the correct reason. Figure 7 As shown in the deviation reason reporting interface, if the deviation reason corresponding to time granularity 06:30 - equipment failure deviation is edited incorrectly, the user can reselect the correct deviation reason - normal equipment wear deviation, and thus re-edit the deviation reason corresponding to time granularity 06:30 to obtain the correct result. Figure 8 The interface for reporting deviation reasons is shown.
[0085] If the time granularity corresponding to a certain deviation cause is edited incorrectly, in order to improve rollback efficiency and avoid users re-editing the deviation cause granularly time by time, this embodiment provides a rollback function for the entire deviation cause. In response to a rollback operation targeting a specific deviation cause, all deviation causes within the target time period corresponding to the target deviation cause's time granularity are uniformly replaced with the default deviation cause. For example, as shown... Figure 9 The deviation cause reporting interface shown has a trash can-shaped back button next to each deviation cause icon. If the user clicks the back button next to the device malfunction deviation icon, they will be redirected to... Figure 10 The deviation reason reporting interface shown below. Figure 9 All deviation reasons corresponding to the time granularity of equipment fault deviation are uniformly replaced with the default deviation reason - normal equipment wear deviation.
[0086] In one possible implementation, this embodiment also provides a rollback function for the causes of deviation within a target time period. In response to a user's rollback operation for the causes of deviation within a target time period, the causes of deviation at each time granularity within the target time period are uniformly replaced with the default causes of deviation. For example, as shown... Figure 9 The deviation reporting interface shown has a clear button in the upper right corner. Clicking the clear button will execute the correct procedure for the deviation. Figure 9 The rollback operation for the deviation reasons in the target time period will pop up as follows: Figure 11 The pop-up window shown prompts the user to clear all reported reasons. Confirmation will revert to the default reason: normal equipment wear and tear deviation. After clicking the confirmation button, the user will be redirected to... Figure 3 The deviation reason reporting interface shown in the image displays the default deviation reason for all time granularities within the target time period: normal equipment wear and tear deviation. This allows for a complete rollback of the deviation reason for a specific time period.
[0087] In the above embodiments, when a user edits the cause of deviation at a certain time granularity, i.e., when the cursor changes to a paint bucket shape, the power deviation and the cause of deviation corresponding to that time granularity are displayed in a floating manner. Furthermore, to enable users to intuitively view the power deviation and the cause of deviation corresponding to each time granularity in various scenarios, the power variation cause processing method provided in this embodiment displays the power deviation and the cause of deviation next to the selected time granularity in a floating manner. Figure 12 The deviation reason reporting interface shown above, if the deviation reason has not been edited and the user is redirected to the deviation reason reporting interface on June 1, 2024, when the user selects the time granularity 06:30, the power deviation corresponding to that time granularity will be displayed in a floating manner, with the deviation reason being "no reason". If the user clicks the save button at this time and then selects the same time granularity again, the power deviation corresponding to that time granularity will be displayed in a floating manner, with the deviation reason being the default deviation reason: normal equipment loss deviation.
[0088] In addition, both the deviation cause reporting interface and the deviation cause graph interface in the above embodiments display a time frame, which serves as a time viewer. For example, if a user clicks the time viewer in the deviation cause graph main interface, the following will be displayed: Figure 13 The target date shown falls within the preset date range ( Figure 13 (Using a month as an example) The calendar interface allows users to easily see which date was last edited for the reason for deviation by marking the dates on the calendar. Furthermore, clicking on a specific date in the calendar will take the user to the corresponding deviation reason graph interface.
[0089] Furthermore, in the above embodiments, in order to facilitate users to distinguish the time granularity corresponding to different deviation causes in the visualization chart, different time granularities corresponding to different deviation causes are displayed in different forms. Taking the visualization chart as a bar chart as an example, the bars corresponding to different deviation causes can be different colors.
[0090] This application also provides an energy management device, including at least one processor and a memory connected to the processor, wherein:
[0091] Memory is used to store computer programs;
[0092] The processor is used to execute computer programs to enable the energy management device to implement the power deviation cause processing method provided in any embodiment of this application.
[0093] refer to Figure 14 As shown, it illustrates a structural schematic diagram suitable for implementing the energy management device in the embodiments of this application. Figure 14 The energy management device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.
[0094] like Figure 14 As shown, the energy management device may include a processing unit (e.g., a central processing unit, a graphics processing unit, etc.) 141, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 142 or a program loaded from a storage device 148 into a random access memory (RAM) 143. When the energy management device is powered on, the RAM 143 also stores various programs and data required for the operation of the energy management device. The processing unit 141, ROM 142, and RAM 143 are interconnected via a bus 144. An input / output (I / O) interface 145 is also connected to the bus 144.
[0095] Typically, the following devices can be connected to I / O interface 145: input devices 146 including, for example, a touchscreen, touchpad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 147 including, for example, a liquid crystal display (LCD), speaker, vibrator, etc.; storage devices 148 including, for example, memory card, hard disk, etc.; and communication devices 149. Communication device 149 allows the energy management device to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 14 An energy management device with various devices is shown; however, it should be understood that implementation or possession of all the devices shown is not required. More or fewer devices may be implemented alternatively.
[0096] This application also provides a computer program product including computer-readable instructions, which, when executed on an energy management device, cause the energy management device to implement any of the power deviation cause handling methods provided in this application.
[0097] This application also provides a computer-readable storage medium carrying one or more computer programs. When the one or more computer programs are executed by an energy management device, the energy management device can implement any of the power deviation cause processing methods provided in this application.
[0098] This application also provides an energy management system, including:
[0099] Energy management equipment;
[0100] A power conversion device at at least one site that is communicatively connected to an energy management device; the power conversion device may be an inverter, an energy storage converter, etc.
[0101] The DC side of the power conversion device is connected to a DC power supply, and the AC side of the power conversion device is connected to the power grid. The energy management device is connected to the power conversion device through communication and is configured to obtain the actual power generation or actual power consumption of the power conversion device through a communication protocol and store it in time granularity on a site-by-site basis.
[0102] DC power sources include at least one of battery power sources and photovoltaic power sources;
[0103] The energy management device is also configured to implement the power deviation cause handling method provided in any embodiment of this application.
[0104] It should also be noted that the device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. In addition, in the device embodiment drawings provided in this application, the connection relationship between modules indicates that they have a communication connection, which can be implemented as one or more communication buses or signal lines.
[0105] Through the above description of the embodiments, those skilled in the art can clearly understand that this application can be implemented by means of software plus necessary general-purpose hardware, or it can be implemented by special-purpose hardware including application-specific integrated circuits, special-purpose CPUs, special-purpose memory, special-purpose components, etc. Generally, any function performed by a computer program can be easily implemented by corresponding hardware, and the specific hardware structure used to implement the same function can also be diverse, such as analog circuits, digital circuits, or special-purpose circuits. However, for this application, software program implementation is more often the preferred implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a readable storage medium, such as a computer floppy disk, USB flash drive, mobile hard disk, ROM, RAM, magnetic disk, or optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, training equipment, or network device, etc.) to execute the methods described in the various embodiments of this application.
[0106] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product.
[0107] The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, training device, or data center to another website, computer, training device, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can store or a data storage device such as a training device or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).
Claims
1. A method for handling power deviation causes, characterized in that, include: Obtain the power deviation of the target site at each time granularity within the target date. The power deviation is the deviation between the actual power generation and the agreed power generation or the deviation between the actual power consumption and the agreed power consumption. The power deviation of the target site at each time granularity within the target date and the original cause of the deviation are displayed in the form of a visual chart; Based on the target time period input by the user, the power deviation of the target site at each time granularity within the target time period on the target date and the original cause of the deviation are displayed in the form of a visual chart. Based on the user-inputted cause of deviation and at least one target time granularity within the target time period selected by the user, the original cause of deviation at the at least one target time granularity is replaced with the target cause of deviation. In response to the user's input reporting command, the power deviation of the target site at each time granularity within the target date and the reason for the deviation are reported.
2. The power deviation cause handling method according to claim 1, characterized in that, The method of displaying the power deviation of the target site at each time granularity within the target date and the reasons for the deviation in the form of a visual chart includes: If the target site has not edited the deviation reason on the target date, the pre-configured default deviation reason will be determined as the original deviation reason for the target site at each time granularity within the target date, and displayed in the form of a visual chart.
3. The power deviation cause handling method according to claim 1, characterized in that, The step of replacing the original deviation cause of the at least one target time granularity with the target deviation cause based on the user-inputted target deviation cause and the user-selected target time period includes: When the cause of the target deviation is a non-custom type, the original deviation cause of the at least one target time granularity is replaced with the target deviation cause. The non-custom type deviation cause includes at least one of the following: equipment failure deviation, deviation caused by power grid dispatch, equipment debugging deviation, algorithm debugging deviation, and normal equipment loss deviation. If the cause of the target deviation is custom, the user is prompted to enter a custom deviation cause, and the original deviation cause of the at least one target time granularity is replaced with the custom deviation cause entered by the user.
4. The method for handling power deviation as described in claim 2, characterized in that, After replacing the original cause of deviation for the at least one target time granularity with the target cause of deviation, the method further includes: In response to the rollback operation for the target deviation cause, all deviation causes within the target time period corresponding to the time granularity of the target deviation cause are uniformly replaced with the default deviation cause.
5. The power deviation cause handling method according to claim 2, characterized in that, After displaying the power deviation of the target site at each time granularity within the target time period on the target date, and the reasons for the deviation, in the form of a visual chart, the method further includes: In response to the rollback operation for the deviation reasons of the target time period, the deviation reasons for each time granularity within the target time period are uniformly replaced with the default deviation reasons.
6. The method for handling power deviation causes according to any one of claims 1-5, characterized in that, The method further includes: When a time granularity is selected, the power deviation and the reason for the deviation corresponding to that time granularity are displayed in a floating manner.
7. The method for handling power deviation causes according to any one of claims 1-5, characterized in that, The method further includes: In response to the user's click operation on the time viewer, a calendar interface within a preset date range of the target date is displayed, and the dates on the calendar interface where the reason for the deviation has been edited are marked.
8. The method for handling power deviation causes according to any one of claims 1-5, characterized in that, In visualization charts, the time granularity corresponding to different causes of deviation is displayed in different ways.
9. An energy management device, characterized in that, It includes at least one processor and a memory connected to the processor, wherein: The memory is used to store computer programs; The processor is used to execute the computer program to enable the energy management device to implement the power deviation cause handling method as described in any one of claims 1 to 8.
10. An energy management system, characterized in that, include: Energy management equipment; A power conversion device at at least one site that is communicatively connected to the energy management device; The DC side of the power conversion device is connected to a DC power supply, and the AC side of the power conversion device is connected to the power grid. The energy management device is communicatively connected to the power conversion device and is configured to obtain the actual power generation or actual power consumption of the power conversion device and store it in time granularity by station. The DC power supply includes at least one of battery power and photovoltaic power; The energy management device is also configured to implement the power deviation cause handling method as described in any one of claims 1 to 8.