A method and system for verifying the release of an energy storage EMS system version

Abstract

This application relates to the technical field of EMS system management, and particularly to a method and system for verifying the release of an energy storage EMS system version, which includes: docking with distributed on-site energy storage stations and waiting for registration, and completing device synchronization after registration; performing data polling to obtain the energy storage data corresponding to each on-site energy storage station; selecting an energy storage verification strategy to capture the energy storage data for a preset duration at the corresponding characteristic positions and integrating them to generate a verification instance; pushing the energy storage data to the local verification energy storage system to start the verification instance; generating an actual operation report based on the energy storage data of the on-site energy storage station over a preset duration, and generating a verification report based on the verification data uploaded by the verification energy storage system; comparing the contents of the actual operation report and the verification report, and generating a version verification result based on the comparison result. This application has the effect of achieving full-coverage simulation of version verification for multi-microgrid scenarios and multi-device differences.

Description

Technical Field

[0001] This application relates to the technical field of EMS system management, and in particular, to a method and system for verifying the release of an energy storage EMS system version. Background Art

[0002] The energy management system (EMS) of an energy storage power station operation control system is a key technology and equipment of the energy storage power station system. At present, there is no tool or means in the industry to conduct experiments and verifications on the operation control system EMS of large-scale energy storage power stations. Facing the monitoring and control of massive real-time data and control objects, how to ensure the effectiveness and feasibility of the design scheme? How to ensure that the energy storage power station operation control system EMS can meet the design requirements of stable and efficient operation of the system? These are necessary conditions for project investment and the system to achieve the target effect.

[0003] Currently, when releasing the version of the energy storage EMS system, different energy management strategy verification methods need to be adopted according to different managed microgrid subsystems, but there are the following problems:

[0004] There are multiple types of microgrid subsystems in the energy storage EMS system, such as the municipal power subsystem, the energy storage subsystem, the load subsystem, the photovoltaic subsystem, the charging pile subsystem, and the diesel generator subsystem. In actual scenarios, an energy storage EMS system often consists of the above-mentioned energy storage subsystem + a combination of one or more other subsystems. This leads to many combined scenarios that need to be verified. In actual verification, the tested energy storage system often cannot ensure that it can include different subsystem combinations of different scenarios;

[0005] There are many types of equipment and manufacturers in the energy storage EMS system, and the corresponding equipment protocols are also different. This leads to the need to separately verify the data points for collecting these devices, match the corresponding equipment protocols, etc. for result verification, and often the test environment cannot cover so many device models and equipment protocols.

[0006] How to cover all microgrid scenarios and equipment differences during system version release verification to simulate the operation of a real site and ensure the stability and accuracy of each version release is an urgent problem to be solved. Summary of the Invention

[0007] In order to achieve full-coverage simulation of version verification for multiple microgrid scenarios and multiple equipment differences, this application provides a method and system for verifying the release of an energy storage EMS system version.

[0008] In the first aspect, this application provides a method for verifying the release of an energy storage EMS system version, adopting the following technical solution:

[0009] A method for verifying the release of an energy storage EMS system version includes the following steps:

[0010] Dock with on-site energy storage sites in each distribution and wait for registration. After registration, complete device synchronization;

[0011] Conduct data polling to obtain energy storage data corresponding to each of the on-site energy storage sites. The energy storage data includes scenario data, device data, and operation data;

[0012] Select an energy storage verification strategy to capture the energy storage data for a preset duration at corresponding characteristic positions and integrate and generate a verification instance. The characteristic positions include characteristic time positions and characteristic node positions;

[0013] Push the energy storage data to the local verification energy storage system to start the verification instance;

[0014] Generate an actual operation report based on the energy storage data of the on-site energy storage site for a preset duration, and generate a verification report based on the verification data uploaded by the verification energy storage system;

[0015] Compare the contents of the actual operation report and the verification report, and generate a version verification result based on the comparison result.

[0016] In some of the embodiments, conducting data polling to obtain energy storage data corresponding to each of the on-site energy storage sites includes the following steps:

[0017] Obtain the first composition information of each subsystem in the on-site energy storage site, and construct a corresponding microgrid scenario based on the subsystem type, subsystem quantity, and subsystem combination in the first composition information to generate scenario data;

[0018] Obtain the second composition information of the devices in each subsystem, and generate device data based on the device type, device manufacturer, and device protocol in the second composition information;

[0019] Obtain the interaction instruction actions, interaction timestamps, and interaction response results of each device to obtain an interaction log, and use the interaction log as the operation data.

[0020] In some of the embodiments, conducting data polling to obtain energy storage data corresponding to each of the on-site energy storage sites includes the following steps:

[0021] Obtain the first composition information of each subsystem in the on-site energy storage site, and construct a corresponding microgrid scenario based on the subsystem type, subsystem quantity, and subsystem combination in the first composition information to generate scenario data;

[0022] Obtain the second composition information of the devices in each subsystem, and generate device data based on the device type, device manufacturer, and device protocol in the second composition information;

[0023] Obtain the interaction instruction actions, interaction timestamps, and interaction response results of each of the devices to obtain an interaction log, and use the interaction log as the operation data.

[0024] In some embodiments, select an energy storage verification strategy to capture the energy storage data at a corresponding characteristic position for a preset duration and integrate it to generate a verification instance, including the following steps:

[0025] Select the corresponding on-site energy storage site as the object to be verified, and based on the selected energy storage verification strategy, find the position where the object to be verified matches the characteristic time point or trigger node to obtain the energy storage data for a preset duration;

[0026] Configure a verification scenario, verification equipment, and verification operation task based on the energy storage data for the preset duration to integrate into the verification instance.

[0027] In some embodiments, selecting an energy storage verification strategy to capture the energy storage data at a corresponding characteristic position for a preset duration and integrating it to generate a verification instance further includes the following steps:

[0028] Compare the scenario data of each of the on-site energy storage sites to determine whether there are duplicate scenarios;

[0029] If there are, define the on-site energy storage sites corresponding to several of the duplicate scenarios as sites to be processed;

[0030] Obtain the number of selected energy storage verification strategies and determine whether it is greater than 1;

[0031] If it is not greater than, select any one of the sites to be processed in the duplicate scenarios as the object to be verified;

[0032] If it is greater than, obtain the verification requirements defined by the user;

[0033] If the verification requirement is urgent processing, select any one of the sites to be processed in the duplicate scenarios as the object to be verified;

[0034] If the verification requirement is slow processing and the number of sites to be processed is not less than the number of energy storage verification strategies, select the same number of sites to be processed as the number of energy storage verification strategies in the duplicate scenarios as the object to be verified;

[0035] If the verification requirement is slow processing and the number of sites to be processed is less than the number of energy storage verification strategies, use all the sites to be processed as the object to be verified.

[0036] In some embodiments, pushing the energy storage data to a local verification energy storage system to start a verification instance includes the following steps:

[0037] Build a corresponding test microgrid scenario in the verification energy storage system based on the scenario data, where the test microgrid scenario includes an actual subsystem and a simulation subsystem;

[0038] Configure corresponding test equipment in the verification energy storage system based on the equipment data, where the test equipment includes actual equipment and simulation equipment;

[0039] Send the interaction logs in the operation data to the corresponding test equipment to realize the simulation operation of the verification energy storage system;

[0040] Among them, the number of the verification energy storage systems is equal to the number of the verification instances.

[0041] In some embodiments, sending the interaction logs in the operation data to the corresponding test equipment to realize the simulation operation of the verification energy storage system further includes the following steps:

[0042] Judge whether the actual equipment includes the action equipment corresponding to each interaction instruction action in the interaction logs;

[0043] If it includes, control the actual equipment to perform the interaction instruction action at the corresponding interaction timestamp and reach the interaction response result to realize real - machine verification;

[0044] If it does not include, send the interaction instruction action and the corresponding interaction response result as simulation configuration parameters to the simulation equipment based on the interaction timestamp for simulation verification.

[0045] In some embodiments, comparing the content of the actual operation report and the verification report, and generating a version verification result based on the comparison result includes the following steps:

[0046] The content comparison includes the comparison of the revenue results at the final time point, as well as the comparison of the operation periods and equipment powers at the real - time time points;

[0047] If there is a confidence match in the comparison result, it is characterized as verification passed;

[0048] If there is a confidence anomaly in the comparison result, it is characterized as verification failed.

[0049] In some embodiments, it further includes:

[0050] Store each verification instance to build a dynamic knowledge base;

[0051] When there is a version verification requirement, the corresponding verification instance is preferentially matched in the dynamic knowledge base based on the energy storage data and pushed to the verification energy storage system for startup;

[0052] If the corresponding verification instance cannot be matched in the dynamic knowledge base, the corresponding on-site energy storage site is selected based on the version verification requirement to obtain the energy storage data, and a new verification instance is generated in combination with the energy storage verification strategy.

[0053] In a second aspect, the present application provides an energy storage EMS system version release verification system, adopting the following technical solution:

[0054] An energy storage EMS system version release verification system includes an on-site distributed energy storage EMS system, a locally set verification energy storage system, and an energy storage simulation management system. Among them, the energy storage EMS system contains several on-site energy storage sites, and the energy storage simulation management system includes:

[0055] An energy storage site registration center for docking with each distributed on-site energy storage site and registering to complete device synchronization;

[0056] A microgrid scenario center for data polling to obtain energy storage data including scenario data corresponding to each on-site energy storage site;

[0057] A microgrid device center for data polling to obtain energy storage data including device data corresponding to each on-site energy storage site;

[0058] A device instruction response configuration center for data polling to obtain energy storage data including operation data corresponding to each on-site energy storage site;

[0059] The energy storage simulation management system is also used to select an energy storage verification strategy to capture the energy storage data for a preset duration at corresponding characteristic positions and integrate and generate a verification instance. The characteristic positions include characteristic time positions and characteristic node positions, and the energy storage data is pushed to the local verification energy storage system to start the verification instance;

[0060] The energy storage simulation management system also includes an EMS operation report center for obtaining the energy storage data of the on-site energy storage site for a preset duration to generate an actual operation report, and the verification data uploaded by the verification energy storage system to generate a verification report;

[0061] Compare the contents of the actual operation report and the verification report, and generate a version verification result based on the comparison result.

[0062] The technical solutions provided in the embodiments of the present application have the following technical effects:

[0063] Based on data acquisition in a real - running energy storage site, various scenarios and equipment differences in the energy storage microgrid can be comprehensively covered during strategy verification; the simulation system obtains devices, data, and instruction responses from the on - site energy storage site, maintaining consistency with the on - site site. The energy storage EMS system running instance simulates the above - mentioned actual scenarios. After completing the operation of a specific scenario, the generated EMS operation report can be directly compared with the history of the on - site operation site to directly obtain the verification result, simulating the operation of various real sites to ensure the stability and accuracy during each version release. Brief Description of the Drawings

[0064] Figure 1 It is a schematic diagram of the steps of a method for verifying the release of an energy storage EMS system version provided in this embodiment.

[0065] Figure 2 It is a schematic diagram of the modules of an energy storage EMS system version release verification system provided in an embodiment of the present application. Detailed Embodiments

[0066] To more clearly understand the purpose, technical solutions, and advantages of the present application, the present application will be described and explained below in conjunction with the drawings and embodiments. However, those of ordinary skill in the art should understand that the present application can be implemented without these details. In some cases, to avoid unnecessary descriptions from making aspects of the present application obscure, well - known methods, processes, systems, components, and / or circuits that have been described at a higher level will not be elaborated too much. For those of ordinary skill in the art, it is obvious that various changes can be made to the disclosed embodiments of the present application, and without departing from the principles and scope of the present application, the general principles defined in the present application can be applied to other embodiments and application scenarios. Therefore, the present application is not limited to the shown embodiments, but conforms to the broadest scope consistent with the scope claimed in the present application.

[0067] It should be noted here that the descriptions of these embodiments are used to help understand the present invention, but do not constitute a limitation to the present invention. In addition, the technical features involved in the various embodiments of the present invention described below can be combined with each other as long as they do not conflict with each other.

[0068] In the description of the present application, the meaning of several is one or more, the meaning of multiple is two or more, greater than, less than, exceeding, etc. are understood as not including the number itself, and above, below, within, etc. are understood as including the number itself. If there is a description of first and second, it is only used to distinguish technical features and cannot be understood as indicating or implying relative importance or implicitly indicating the quantity of the indicated technical features or implicitly indicating the sequence relationship of the indicated technical features.

[0069] In the description of the present application, the description referring to terms such as "one embodiment", "some embodiments", "schematic embodiments", "examples", "specific examples", or "some examples" means that the specific features, structures, materials, or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic expressions of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described can be combined in any one or more embodiments or examples in a combined manner.

[0070] As Figure 1 shown, an embodiment of the present application discloses a method for verifying the release of an energy storage EMS system version, including the following steps:

[0071] S100, dock with each distributed on-site energy storage site and wait for registration. After registration, device synchronization is completed.

[0072] This step is carried out by the energy storage site registration center in the system. It first obtains the basic information of several energy storage sites distributed in reality and registers with each energy storage site. After registration, the system obtains the identity information, location information, customer information, etc. of each energy storage site. At the same time, after the registration is completed, the energy storage EMS system version release verification system can perform device synchronization with the energy storage site to obtain various types of data uploaded by the energy storage site in real time. These data include the operating parameters during operation, the information of the devices in the energy storage site, and the information of the various subsystems constructed in the energy storage site.

[0073] S200, conduct data polling to obtain the energy storage data corresponding to each on-site energy storage site. The energy storage data includes scenario data, device data, and operation data.

[0074] After the system completes the connection registration and synchronization with the on-site energy storage site, before verification, it first obtains the corresponding verification data from the target on-site energy storage site through data polling. The verification data specifically includes the scenario data representing the energy storage scenarios of each energy storage site, the device data existing in the on-site energy storage site, and the real-time data during the operation of each device.

[0075] After the above data is polled and integrated, the energy storage simulation management system will send it to the local energy storage system for verification based on certain strategies and verification requirements.

[0076] S300, select an energy storage verification strategy to capture the energy storage data for a preset duration at the corresponding characteristic positions and integrate it to generate a verification instance. The characteristic positions include characteristic time positions and characteristic node positions.

[0077] Energy storage strategies are characterized by different energy storage strategies corresponding to the environment where the energy storage power station is located, the application field, and the special power consumption plan, such as peak shaving and valley filling, dynamic virtual quantity, maximum virtual quantity, etc. Each different energy storage verification strategy corresponds to a different verification method. The main difference lies in the different positions of the characteristic nodes to be verified in different strategies. This position can be the node position of the trigger quantity or the node position in time.

[0078] After selecting the energy storage verification strategy, select the energy storage data for a preset duration based on the specific content of the strategy and integrate it in the energy storage simulation management system. After integration, it is used as a verification instance to be sent to the subsequent local system for simulation and verification.

[0079] S400, Push the energy storage data to the local verified energy storage system to start the verification instance.

[0080] The energy storage simulation management system sends and pushes the integrated energy storage data to the local verified energy storage system, and controls the verified energy storage system to perform simulation based on the obtained verification instance.

[0081] S500, Generate an actual operation report based on the energy storage data of the on-site energy storage site for a preset duration, and generate a verification report based on the verification data uploaded by the verified energy storage system.

[0082] Since the energy storage simulation management system obtains real-time data from the on-site energy storage site in actual operation, based on the data it obtains, the EMS operation report center in the system can generate an actual operation report based on the actual operation data. This report is characterized by the corresponding result data and process data during the system operation in a historical period of time.

[0083] At the same time, the EMS operation report center simultaneously obtains the real-time parameters corresponding to the verified energy storage system during the simulation based on the real energy storage data in real time, and generates a corresponding verification report based on the result data and process data in the same period of time.

[0084] S600, Compare the contents of the actual operation report and the verification report, and generate a version verification result based on the comparison result.

[0085] In this way, after the EMS operation report center obtains a real operation report and a simulation verification report with the same time, the same scenario, the same equipment, and the same operation data, it can compare the contents between the two reports and judge the version verification result according to the comparison result.

[0086] Among them, the contents of the comparison mainly include benefits, operation periods, equipment power, etc.

[0087] Through the above method, based on data acquisition in a real - operating energy storage site, various scenarios and device differences in the energy storage microgrid can be comprehensively covered during strategy verification; the simulation system obtains devices, data, and instruction responses from the on - site energy storage site, maintaining consistency with the on - site site. The energy storage EMS system operation instance simulates the above - mentioned actual scenarios. After completing the operation of a specific scenario, the generated EMS operation report can be directly compared with the history of the on - site operation site to directly obtain the verification result, simulating the operation of various real sites to ensure the stability and accuracy during each version release.

[0088] In some other embodiments, data acquisition is performed to obtain the energy storage data corresponding to each on - site energy storage site, including the following steps:

[0089] S210, obtain the first composition information of each subsystem in the on - site energy storage site, and based on the subsystem type, subsystem quantity, and subsystem combination in the first composition information, construct the corresponding microgrid scenario to generate scenario data.

[0090] After the energy storage site completes the registration synchronization with the energy storage site registration center, first obtain the reported subsystem composition information. If the subsystems included in different energy storage sites are different, they are characterized as being under different microgrid scenarios. For example, in the microgrid scenario of a charging station, the subsystems included are an energy storage subsystem, a municipal power subsystem, a load subsystem, and a charging pile subsystem; the community microgrid scenario includes an energy storage subsystem, a municipal power subsystem, a load subsystem, a photovoltaic subsystem, etc.

[0091] Then, according to the first composition information of several subsystems obtained from the on - site energy storage site, that is, which subsystems are included, the corresponding quantity of each subsystem, etc., a specific microgrid scenario can be constructed, and scenario data can be generated based on the specific microgrid scenario.

[0092] The scenario data is used as reference data for scenario construction during subsequent simulation verification of the local system. Under different scenarios, the operating data and the corresponding verification strategies are different.

[0093] S220, obtain the second composition information of the devices in each subsystem, and generate device data based on the device type, device manufacturer, and device protocol in the second composition information.

[0094] After the microgrid scenario is set up, the microgrid device center then obtains the type information of each device included in each subsystem (PCS, BMS, photovoltaic inverter, electric meter, DIDO, air conditioner, fire protection, etc.), the manufacturer of each device, and the device protocol used by each device.

[0095] After collecting this data, it is integrated into device data, which is used as reference data for setting up the device environment when the subsequent local system conducts simulation verification.

[0096] S230, obtain the interaction instruction actions, interaction timestamps, and interaction response results of each device to obtain an interaction log, and use the interaction log as operation data.

[0097] Meanwhile, the device instruction response configuration center obtains the interaction action data uploaded by each device in real time, such as specific interaction actions like power on, power off, reset, etc., as well as the time when the interaction action is issued and the final result (success or failure) of the interaction action, and uniformly integrates the continuous data in the time dimension into an interaction log.

[0098] This interaction log characterizes the operating status of each device in the scenario. Using the interaction log as operation data, it is used as simulated or real interaction data when the subsequent local system conducts simulation verification.

[0099] In some other embodiments, select an energy storage verification strategy, including the following steps:

[0100] S310, upload the energy storage verification strategy and classify it to obtain time verification classes and node verification classes.

[0101] The energy storage verification strategy is uploaded by the user. When uploading, according to the differences in the energy storage verification strategy, it is mainly divided into time verification classes and node verification classes.

[0102] The time verification class characterizes reacting to the nodes that appear at characteristic times for key verification. For example, under the strategy of peak shaving and valley filling, it is necessary to focus on the changes in the operating data of each device in the energy storage power station at the valley price time around 12 o'clock at night and the peak price time around 12 o'clock at noon for comparison and simulation verification.

[0103] The node verification class characterizes reacting to the nodes that appear at characteristic numerical points for key verification. For example, under the strategy of maximum virtual quantity, it is necessary to pay attention to whether the power value exceeds a preset maximum value at a certain moment. Then, when a time point where the power exceeds the preset maximum value is obtained based on the real-time acquired device power data, the time when this numerical point appears and a period of time after that are used as the key attention objects, and comparison and simulation verification are carried out according to their changes.

[0104] S311, obtain characteristic time points based on the time verification class, and configure a corresponding minimum time period starting from the characteristic time points to generate verification time.

[0105] When the energy storage verification strategy is a time verification type, first select a characteristic time point based on the specific content of the strategy, then configure a minimum time period based on the characteristic time point in combination with the verification requirements. The minimum time period represents the duration that must be verified under different verification requirements or verification precisions. Finally, generate the corresponding verification time in combination with the minimum time period.

[0106] For example, under the strategy of peak shaving and valley filling, if 11 pm is the characteristic time point and the valley point time is generally 8 am the next day, then in order to effectively verify the version under this strategy, the minimum time period needs to be set to 9 hours. So the final verification time is the nine hours from 11 pm to 8 am the next day.

[0107] Another example is that if the precision requirement for version release verification is low or the version release time is urgent, the verification time can be set to 1 hour, 2 hours, etc. When a higher precision and lower hidden danger verification is required for version release verification, the verification time can be set to 1 day.

[0108] S312, Obtain the trigger node based on the node verification type, and continuously detect the electrical energy data in real time until the trigger node is reached, and then configure the corresponding verification time based on the current time point as the starting point. The electrical energy data includes power, voltage, current, and frequency.

[0109] If the strategy type is the node verification type, then set the trigger node based on its specific content. The trigger node is the action trigger value corresponding to an electrical energy data type, such as reaching a power of how many kW, a voltage of how many v, and so on.

[0110] After setting, determine whether each electrical energy data during operation reaches the action trigger value based on the data uploaded by the actually and real-time operating energy storage site. If it reaches, use the time point of the moment of triggering as the starting point, and also configure the verification time based on the verification precision requirement.

[0111] Among them, the preset duration is not less than the verification time. Because the verification time represents the minimum time that must be fully verified under the energy storage verification strategy, in order to ensure the accuracy of the verification result before version release and meet the verification requirements, when capturing the energy storage data for a certain period of time, it is necessary to ensure that the captured data time period completely covers the verification time. Only in this way can the generated verification instance be verified in the local verification energy storage system, and the local verification energy storage system can perform full-coverage verification on the time period to be verified.

[0112] In some other embodiments, the selection of the verification strategy is also dynamically and intelligently replaced. It can select verification strategy a at y o'clock every day from x1 to x2 according to the actual verification requirements of version release, and select verification strategy b throughout the day from x3 to x4.

[0113] In some other embodiments, an energy storage verification strategy is selected to capture the energy storage data at a corresponding characteristic position for a preset duration and integrate and generate a verification instance, including the following steps:

[0114] S320. Select a corresponding on-site energy storage site as the object to be verified, and based on the selected energy storage verification strategy, find the position of the matching characteristic time point or trigger node of the object to be verified to obtain the energy storage data for a preset duration.

[0115] S321. Configure a verification scenario, verification equipment, and verification operation tasks based on the energy storage data for a preset duration to integrate them into a verification instance.

[0116] When verification before version release is required, first select the corresponding on-site energy storage site as the object to be verified, find the position of the corresponding time point or node through the energy storage verification strategy, obtain the energy storage data for a preset duration for integration, configure the verification scenario based on the scenario data, configure the verification equipment based on the equipment data after integration, and finally configure the verification operation tasks based on the operation data and integrate them as a complete verification instance.

[0117] After pushing the verification instance to the local verification energy storage system, start the instance so that the local verification energy storage system performs operation simulation based on the same scenario, the same equipment, and the same operation interaction actions as the real system.

[0118] In some other embodiments, an energy storage verification strategy is selected to capture the energy storage data at a corresponding characteristic position for a preset duration and integrate and generate a verification instance, further including the following steps:

[0119] S330. Compare the scenario data of each on-site energy storage site to determine whether there are duplicate scenarios.

[0120] Duplicate scenarios are characterized by the scenario data corresponding to two or more on-site energy storage sites being exactly the same.

[0121] S331. If so, define the on-site energy storage sites corresponding to several duplicate scenarios as the sites to be processed.

[0122] Because when generating a verification instance later, in order to reduce the system load and the workload of the verification system, the optimal situation is that one energy storage scenario corresponds to one verification instance and one instance startup link.

[0123] Then if there are duplicate scenarios, define the energy storage sites corresponding to multiple duplicate scenarios as the sites to be processed, and determine whether to retain one or several through subsequent steps.

[0124] S332. Obtain the number of selected energy storage verification strategies and determine whether it is greater than 1.

[0125] S333: If it is not greater than, select any one of the sites to be processed in the repeated scenario as the object to be verified.

[0126] S334: If it is greater than, obtain the verification requirements defined by the user.

[0127] S335: If the verification requirement is urgent processing, select any one of the sites to be processed in the repeated scenario as the object to be verified.

[0128] S336: If the verification requirement is slow processing and the number of sites to be processed is not less than the number of energy storage verification strategies, select the same number of sites to be processed as the number of energy storage verification strategies in the repeated scenario as the objects to be verified.

[0129] S337: If the verification requirement is slow processing and the number of sites to be processed is less than the number of energy storage verification strategies, take all the sites to be processed as the objects to be verified.

[0130] First, judge the number of energy storage verification strategies. Because if the number of different energy storage verification strategies is greater than 1, then due to different characteristic times to be verified for different energy storage verification strategies, the energy storage sites in the repeated scenario combined with different energy storage verification strategies can still correspond to two different verification instances.

[0131] Furthermore, judge the urgency of the current system version verification link. If it is necessary to complete the verification as soon as possible, then it is necessary to quickly obtain the energy storage data in the on-site energy storage sites and quickly integrate it into several verification instances. Then, if multiple sites to be processed are reserved for separate data call measurement, it will cause the energy storage simulation management system to obtain multiple groups of the same data in parallel and select the required data based on the characteristic time respectively, and the processing speed of the energy storage simulation relationship system will slow down.

[0132] Therefore, in the case of urgent processing, it is necessary to select any one of the sites to be processed as the object to be verified, and respectively select the time period data corresponding to each energy storage verification strategy from the continuous data of this one on-site energy storage site. In this way, one object to be verified can correspond to multiple verification instances.

[0133] If the system version verification is not urgent, then a longer verification can be allowed. Then, multiple sites to be processed with repeated scenarios can be selected as the objects to be verified. Each object to be verified corresponds to one energy storage verification strategy and one verification instance respectively.

[0134] Secondly, it is also necessary to pre-judge whether the number of sites to be processed in the case of slow processing is greater than or equal to the number of energy storage verification strategies. If it is greater than or equal to, it means that there are enough sites to be processed to allocate all the energy storage verification strategies. At this time, only need to select the same number of sites to be processed as the number of energy storage verification strategies as the objects to be verified.

[0135] If it is less than the number of energy storage verification strategies, it means that the sites to be processed in the current repeated scenario cannot allocate all the energy storage verification strategies. In this case, all the sites to be processed can be selected as the objects to be verified. After evenly allocating the energy storage verification strategies, the remaining unallocated energy storage verification strategies are randomly distributed to the corresponding number of sites to be processed. At this time, some on-site energy storage sites in the repeated scenario correspond to one energy storage verification strategy, while some on-site energy storage sites correspond to multiple energy storage verification strategies.

[0136] If the number of energy storage verification strategies is not greater than 1, it means that there is only one energy storage verification strategy. In this case, only any one of the sites to be processed needs to be retained as the object to be verified, and other on-site energy storage sites do not need to upload the corresponding energy storage data to the energy storage simulation management system based on the call measurement.

[0137] In some other embodiments, pushing the energy storage data to the local verification energy storage system to start the verification instance includes the following steps:

[0138] S410, building a corresponding test microgrid scenario in the verification energy storage system based on the scenario data. The test microgrid scenario includes an actual subsystem and a simulation subsystem.

[0139] After the verification energy storage system obtains the scenario data, it configures and builds a test microgrid scenario identical to the scenario data.

[0140] That is, building a one-to-one energy storage scenario in the local verification energy storage system based on the subsystem configuration, type, and quantity in the scenario data. At the same time, if there is a corresponding subsystem in the local verification system, the corresponding actual subsystem is configured; if there is no corresponding subsystem, the non-existent subsystem is configured through the simulation software model.

[0141] S420, configuring corresponding test equipment in the verification energy storage system based on the equipment data. The test equipment includes actual equipment and simulation equipment.

[0142] After the verification energy storage system obtains the equipment data, it configures test equipment identical to the equipment data.

[0143] That is, building a one-to-one test equipment in the local verification energy storage system based on the equipment type, equipment manufacturer, equipment protocol, etc. in the equipment data. At the same time, if there is a corresponding identical equipment in the local verification system, the corresponding actual equipment is configured; if there is no corresponding identical equipment, the type, model, and protocol information of the non-existent equipment are input into the simulation program to configure the simulation equipment.

[0144] S430, sending the interaction log in the operation data to the corresponding test equipment to realize the simulation operation of the verification energy storage system.

[0145] Verify that after the energy storage device obtains the operation data, it extracts information such as interaction actions and interaction results in the interaction log and sends them to the corresponding test devices so that each test device can perform simulation operations based on the corresponding operation actions.

[0146] Among them, the number of verified energy storage systems is equal to the number of verification instances.

[0147] One verified energy storage system verifies one instance, which can ensure that the result of one verified energy storage system can correspond to the verification result of one on-site energy storage device under the scenario corresponding to one verification strategy for comparison, avoiding comparison deviations, and at the same time ensuring a one-to-one synchronous comparison effect.

[0148] In some other embodiments, sending the interaction log in the operation data to the corresponding test device to implement the simulation operation of the verified energy storage system further includes the following steps:

[0149] S431, determine whether the actual device contains the action devices corresponding to the interaction instruction actions in the interaction log.

[0150] S432, if it contains, control the actual device to perform the interaction instruction action at the corresponding interaction timestamp and reach the interaction response result to implement real machine verification.

[0151] S433, if it does not contain, send the interaction instruction action and the corresponding interaction response result as simulation configuration parameters to the simulation device for simulation verification based on the interaction timestamp.

[0152] When the local verified energy storage system contains the action devices corresponding to the interaction instructions in the interaction log, then the specific interaction actions can be directly performed on the physical device. For example, if there is a start of a motor at time t1 in the interaction log and the start result is successful, then the verified energy storage system controls the corresponding motor to start when the time reaches t1, and at the same time defines that this start action must be a successful result to implement real machine verification.

[0153] When the local verified energy storage system does not contain the action devices corresponding to some interaction instruction actions in the interaction log, then the specific interaction actions cannot be performed on the actual device. For example, if there is no PCS in the local verified energy storage system, then the power-on and power-off actions of the PCS cannot be performed on the actual device.

[0154] Then, when there is no device that can actually perform actions, in order to keep the actions and operating status of the verification energy storage system exactly the same as those of the on-site energy storage site, on the premise of clearly knowing the interaction actions and interaction results through the interaction log, the interaction actions and the corresponding results are directly sent to the simulation device through simulation instructions for simulation. In this way, the local verification system does not need to have all types, manufacturers, and protocol devices comprehensively. As long as it is based on the historical data obtained from real operation, the actions and results can be directly simulated one-to-one in the simulation model, ensuring that the operation between the real energy storage power station and the local energy storage system remains exactly the same.

[0155] In some other embodiments, the content of the actual operation report and the verification report is compared, and a version verification result is generated based on the comparison result, including the following steps:

[0156] S610, the content comparison includes the comparison of the revenue results at the final time point, as well as the comparison of the operation periods and device powers at the real-time time points.

[0157] After obtaining the actual operation report and the verification report, it is necessary to compare and analyze the specific content in the two reports. The comparison includes the comparison of the revenue results. For example, the electricity price corresponding to the on-site energy storage site operating in real time in a period is compared with the electricity price calculated by the verification energy storage system simulated one-to-one in this period; it also includes the comparison of the operation periods at the real-time time points. For example, if the photovoltaic in the on-site energy storage site is turned on in the time period from t1 to t2 and turned off in the time period from t3 to t4, then it is compared whether the photovoltaic in the verification energy storage system is also turned on and off in the corresponding time periods after simulation; on the one hand, the device power is characterized by whether the monitoring curves of the energy storage data device powers between the on-site energy storage site and the verification energy storage system coincide, and whether the time positions of the characteristic powers such as the maximum power and the minimum power are the same, etc.

[0158] S620, if there is a confidence match in the comparison result, it is characterized that the verification is passed.

[0159] If the comparison results of each data item in the two operation reports all match, and the matching results have a high confidence level, it is considered that this verification is passed.

[0160] S630, if there is a confidence anomaly in the comparison result, it is characterized that the verification is not passed.

[0161] If there are mismatches in the comparison results of each data item in the two operation reports, the confidence level is analyzed based on the differences between the mismatched data and the number of mismatched data. If it is a high confidence, it is characterized that the current verification is not passed.

[0162] In some other embodiments, it further includes:

[0163] S700 stores each verification instance to build a dynamic knowledge base.

[0164] When a verification instance appears and is started and passed the verification, the completed verification instances are sorted out to build a dynamic knowledge base.

[0165] At the same time, whenever a new verification instance appears, it is necessary to verify whether the scenario, device, operation data, and corresponding verification strategy corresponding to the verification instance are exactly the same as the verification instances already in the dynamic knowledge base before adding it to the dynamic knowledge base; if they are exactly the same, it is considered that the verification instance has been stored in the dynamic knowledge base, and then the duplicate verification instances will not be added to the dynamic knowledge base.

[0166] S710, when there is a version verification requirement, first match the corresponding verification instance in the dynamic knowledge base based on the energy storage data and push it to the verification energy storage system for startup.

[0167] Whenever a version release verification task needs to be performed, first judge whether the instance requirements composed of the required scenario, device, operation information, and required verification strategy can match exactly the same verification instance in the dynamic knowledge base. If so, directly obtain the corresponding verification instance in the dynamic knowledge base and send it to the verification energy storage system for startup, so that there is no need to spend time and computing power to call the data of on-site energy storage devices.

[0168] S720, if the corresponding verification instance cannot be matched in the dynamic knowledge base, select the corresponding on-site energy storage site based on the version verification requirement to obtain the energy storage data, and combine the energy storage verification strategy to generate a new verification instance.

[0169] If there is no exactly matching verification instance in the dynamic knowledge base, select one or more on-site energy storage sites according to the requirements corresponding to the version verification and configure the energy storage verification strategy to obtain the energy storage data for the corresponding duration and integrate it into a new verification instance. Similarly, when the verification instance passes the verification, it will also be added to the dynamic knowledge base to expand the number of instances in the library.

[0170] Through the above steps, because the number of different energy storage scenarios is dynamic and constantly updated, the test instances corresponding to each scenario will be saved in the overall verification process, which makes the number of instances stored in the knowledge base increase continuously. Subsequently, which scenario to verify can directly retrieve the instances in the knowledge base. The energy storage simulation management system can automatically build a scenario knowledge base, automatically start multi-instance verification, fully automate the verification process, and generate EMS operation report results.

[0171] Such as Figure 2As shown in the figure, the present application also discloses a verification system for the release of an energy storage EMS system version, including an energy storage EMS system distributed on-site, a verification energy storage system set locally, and an energy storage simulation management system. Among them, several on-site energy storage sites are included in the energy storage EMS system, and the energy storage simulation management system includes:

[0172] An energy storage site registration center, which is used to connect to each distributed on-site energy storage site and register to complete device synchronization;

[0173] A microgrid scenario center, which is used to perform data polling to obtain energy storage data including scenario data corresponding to each on-site energy storage site;

[0174] A microgrid device center, which is used to perform data polling to obtain energy storage data including device data corresponding to each on-site energy storage site;

[0175] A device instruction response configuration center, which is used to perform data polling to obtain energy storage data including operation data corresponding to each on-site energy storage site;

[0176] The energy storage simulation management system is also used to select an energy storage verification strategy to capture energy storage data for a preset duration at corresponding characteristic positions, where the characteristic positions include characteristic time positions and characteristic node positions, and integrate the energy storage data to generate a verification instance, and push the energy storage data to the local verification energy storage system to start the verification instance;

[0177] The energy storage simulation management system also includes an EMS operation report center, which is used to obtain energy storage data of the on-site energy storage site for a preset duration to generate an actual operation report, and verification data uploaded by the verification energy storage system to generate a verification report;

[0178] Compare the contents of the actual operation report and the verification report, and generate a version verification result based on the comparison result.

[0179] The implementation principle is:

[0180] Based on data polling in actual operating energy storage sites, various scenarios and device differences in the energy storage microgrid can be comprehensively covered during strategy verification; the simulation system obtains devices, data, and instruction responses from on-site energy storage sites, and maintains consistency with on-site sites. The energy storage EMS system operation instance simulates the above actual scenarios, and after completing the operation of a specific scenario, the generated EMS operation report can be directly compared with the history of the on-site operation site to directly obtain the verification result, simulating the operation of various real sites to ensure the stability and accuracy of each version release.

[0181] It should be understood that although the steps in the flowchart of the accompanying drawings are shown sequentially according to the indication of the arrows, these steps are not necessarily executed sequentially in the order indicated by the arrows. Unless there is a clear indication in this text, there is no strict order restriction for the execution of these steps, and they can be executed in other orders.

[0182] The above are all preferred embodiments of the present application, and the protection scope of the present application is not limited thereby. Therefore, all equivalent changes made according to the structure, shape, and principle of the present application shall be covered within the protection scope of the present application.

Claims

1. A method for verifying the release of an energy storage EMS system version, characterized in that: The following steps are involved: Connect to each distributed on-site energy storage site and wait for registration. After registration, complete device synchronization; Perform data call testing to obtain energy storage data corresponding to each of the on-site energy storage sites, wherein the energy storage data includes scene data, equipment data, and operation data. Specifically, Acquire first composition information of each subsystem in the on-site energy storage site, and construct a corresponding microgrid scenario based on the subsystem type, subsystem quantity, and subsystem combination in the first composition information to generate scenario data; Acquire the second configuration information of the devices in each of the subsystems, and generate device data based on the device type, device manufacturer, and device protocol in the second configuration information; Obtaining the interaction instruction action, interaction timestamp and interaction response result of each of the devices to obtain an interaction log, and using the interaction log as the operation data; Selecting an energy storage verification strategy to capture the energy storage data of a preset time length at a corresponding characteristic position and integrate and generate a verification instance, wherein the characteristic position includes a characteristic time position and a characteristic node position; Pushing the energy storage data to a local verification energy storage system to start a verification instance; Generating an actual operation report based on the energy storage data of the on-site energy storage site over a preset period of time, and generating a verification report based on the verification data uploaded by the verification energy storage system; The actual operation report and the verification report are compared in content, and a version verification result is generated based on the comparison result.

2. The energy storage EMS system version release verification method according to claim 1 is characterized in that: Selecting an energy storage verification strategy includes the following steps: Upload the energy storage verification strategy and classify it into time verification class and node verification class; Acquire a characteristic time point based on the time verification class, and configure a corresponding minimum time period with the characteristic time point as the starting point to generate a verification time; Acquire a trigger node based on the node verification class, and detect the electric energy data in real time until the trigger node is reached, and configure a corresponding verification time based on the current time point as the starting point, wherein the electric energy data includes power, voltage, current, and frequency; Wherein, the preset duration is not less than the verification time.

3. The energy storage EMS system version release verification method according to claim 2 is characterized in that: Selecting an energy storage verification strategy to capture the energy storage data of a preset time length at a corresponding feature position and integrating and generating a verification instance includes the following steps: Select the corresponding on-site energy storage site as the object to be verified, and find the location of the object to be verified that matches the characteristic time point or trigger node based on the selected energy storage verification strategy to obtain the energy storage data over a preset time period; Based on the energy storage data over the preset time period, verification scenarios, verification equipment and verification operation tasks are configured to be integrated into the verification instance.

4. The energy storage EMS system version release verification method according to claim 3 is characterized in that: Selecting an energy storage verification strategy to capture the energy storage data of a preset time length at a corresponding feature position and integrating and generating a verification instance also includes the following steps: Comparing the scene data of each of the on-site energy storage sites to determine whether there are repeated scenes; If so, defining the on-site energy storage sites corresponding to the repeated scenarios as sites to be processed; Obtain the number of the selected energy storage verification strategies, and determine whether it is greater than 1; If not, selecting any one of the sites to be processed in the repeated scene as the object to be verified; If it is greater, get the user-defined validation requirements; If the verification requirement is urgent processing, any one of the to-be-processed sites in the repeated scenario is selected as the to-be-verified object; If the verification requirement is slow processing and the number of the to-be-processed sites is not less than the number of the energy storage verification strategies, then selecting the to-be-processed sites with the same number as the energy storage verification strategies as the objects to be verified in the repeated scenario; If the verification requirement is slow processing and the number of sites to be processed is less than the number of energy storage verification strategies, all the sites to be processed are taken as the objects to be verified.

5. The energy storage EMS system version release verification method according to claim 1 is characterized in that: Pushing the energy storage data to a local verification energy storage system to start a verification instance includes the following steps: Building a corresponding test microgrid scenario in the verification energy storage system based on the scenario data, wherein the test microgrid scenario includes an actual subsystem and a simulation subsystem; Based on the device data, configure corresponding test equipment in the verification energy storage system, wherein the test equipment includes actual equipment and simulation equipment; Sending the interaction log in the operation data to the corresponding test equipment to realize the simulation operation of the verification energy storage system; The number of the verified energy storage systems is equal to the number of the verified instances.

6. The energy storage EMS system version release verification method according to claim 5 is characterized in that: Sending the interaction log in the operation data to the corresponding test equipment to realize the simulation operation of the verification energy storage system also includes the following steps: Determine whether the actual device includes an action device corresponding to each of the interaction instruction actions in the interaction log; If included, then controlling the actual device to perform the interaction instruction action and achieve the interaction response result at the corresponding interaction timestamp to realize real machine verification; If not included, the interaction instruction action and the corresponding interaction response result are sent to the simulation device as simulation configuration parameters based on the interaction timestamp for simulation verification.

7. The energy storage EMS system version release verification method according to claim 1 is characterized in that: Comparing the actual operation report with the verification report, and generating a version verification result based on the comparison result, includes the following steps: Content comparison includes comparison of revenue results at the final time point, as well as comparison of operating time periods and equipment power at real-time time points; If a confident match appears in the comparison result, it is characterized as verification passed; If a confidence anomaly appears in the comparison result, it is characterized as a failure of verification.

8. The energy storage EMS system version release verification method according to claim 1 is characterized in that: Also includes: Storing each of the verification instances to build a dynamic knowledge base; When there is a version verification requirement, the corresponding verification instance is matched in the dynamic knowledge base based on the energy storage data and pushed to the verification energy storage system for startup; If the corresponding verification instance cannot be matched in the dynamic knowledge base, the corresponding on-site energy storage site is selected based on the version verification requirement to obtain the energy storage data, and the energy storage verification strategy is combined to generate a new verification instance.

9. An energy storage EMS system version release verification system, characterized in that: It includes an on-site distributed energy storage EMS system, a locally set verification energy storage system, and an energy storage simulation management system, wherein the energy storage EMS system includes several on-site energy storage sites, and the energy storage simulation management system includes: The energy storage site registration center is used to connect to various distributed on-site energy storage sites and register them to complete device synchronization; The microgrid scene center is used to perform data call testing to obtain energy storage data including scene data corresponding to each of the on-site energy storage sites. Specifically, Acquire first composition information of each subsystem in the on-site energy storage site, and construct a corresponding microgrid scenario based on the subsystem type, subsystem quantity, and subsystem combination in the first composition information to generate scenario data; The microgrid equipment center is used to perform data call testing to obtain energy storage data including equipment data corresponding to each on-site energy storage site. Specifically, Acquire the second configuration information of the devices in each of the subsystems, and generate device data based on the device type, device manufacturer, and device protocol in the second configuration information; The device command response configuration center is used to perform data call testing to obtain energy storage data including operation data corresponding to each on-site energy storage site. Specifically, Obtaining the interaction instruction action, interaction timestamp and interaction response result of each of the devices to obtain an interaction log, and using the interaction log as the operation data; The energy storage simulation management system is also used to select an energy storage verification strategy to capture the energy storage data of a preset time length at a corresponding characteristic position and integrate and generate a verification instance, wherein the characteristic position includes a characteristic time position and a characteristic node position, and push the energy storage data to a local verification energy storage system to start the verification instance; The energy storage simulation management system also includes an EMS operation report center, which is used to obtain the energy storage data of the on-site energy storage site over a preset time to generate an actual operation report, and the verification data uploaded by the verification energy storage system to generate a verification report; The actual operation report and the verification report are compared in content, and a version verification result is generated based on the comparison result.

Images