Energy storage EMS system version release verification method and system

Abstract

The invention relates to the technical field of EMS system management, in particular to an energy storage EMS system version release verification method and system, and the method comprises the steps: carrying out the butt joint of all distributed on-site energy storage sites, waiting for registration, and completing the equipment synchronization after registration; data interrogation is carried out to acquire energy storage data corresponding to each field energy storage station; selecting an energy storage verification strategy to capture energy storage data of a preset duration at the corresponding feature position, and integrating the energy storage data to generate a verification instance; 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 field energy storage site in the preset duration, and generating a verification report based on verification data uploaded by the verification energy storage system; and performing content comparison on the actual operation report and the verification report, and generating a version verification result based on a comparison result. The method and the device have the effect of realizing full-coverage simulation of version verification of multi-microgrid scenes and multi-device differences.

Description

Technical Field

[0001] The present 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 EMS operation control system of energy storage power stations is the key technology and equipment of energy storage power station systems. At present, the industry does not have the tools and means to conduct EMS experiments and verification of large-scale energy storage power station operation control systems. Faced with massive real-time data and monitoring and control of control objects, how to ensure that the design plan is effective and feasible? How to ensure that the EMS operation control system of energy storage power stations can meet the design requirements of stable and efficient operation of the system? It is a necessary condition for project investment and system to achieve the target effect.

[0003] Currently, when the energy storage EMS system version is released, different energy management strategy verification methods need to be adopted according to the different microgrid subsystems managed, but there are the following problems: There are many microgrid subsystems in the energy storage EMS system, such as the city electronic system, energy storage subsystem, load subsystem, photovoltaic subsystem, charging pile subsystem and diesel subsystem. In actual scenarios, an energy storage EMS system is often a combination of the above energy storage subsystem + one or more other subsystems. This leads to many combination scenarios that need to be verified. In actual verification, the energy storage system used for testing often cannot ensure that it can contain different subsystem combinations in different scenarios. There are many types of equipment and equipment manufacturers in the energy storage EMS system, and the corresponding equipment protocols are also different. This means that during verification, it is necessary to verify the data points collected from these devices separately, match the corresponding equipment protocols, and verify the results. Often, the test environment cannot cover so many equipment models and equipment protocols.

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

[0005] In order to achieve full coverage simulation of version verification for multi-microgrid scenarios and multi-device differences, the present application provides a method and system for energy storage EMS system version release verification.

[0006] In the first aspect, the present application provides a method for verifying the release of an energy storage EMS system version, which adopts the following technical solution: A method for verifying the release of an energy storage EMS system version includes the following steps: Connect to each distributed on-site energy storage site and wait for registration. After registration, complete device synchronization; Performing 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; 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.

[0007] In some embodiments, performing data call testing to obtain energy storage data corresponding to each of the on-site energy storage sites includes the following steps: 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; The interaction instruction action, interaction timestamp and interaction response result of each of the devices are obtained to obtain an interaction log, and the interaction log is used as the operation data.

[0008] In some embodiments, performing data call testing to obtain energy storage data corresponding to each of the on-site energy storage sites includes the following steps: 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; The interaction instruction action, interaction timestamp and interaction response result of each of the devices are obtained to obtain an interaction log, and the interaction log is used as the operation data.

[0009] In some embodiments, 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.

[0010] In some of the embodiments, 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 further 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, then obtain 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.

[0011] In some embodiments, 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.

[0012] In some of the embodiments, sending the interaction log in the operation data to the corresponding test device to implement the simulation operation of the energy storage system verification further 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.

[0013] In some embodiments, the actual operation report and the verification report are compared in content, and a version verification result is generated based on the comparison result, including 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.

[0014] In some of the embodiments, it 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.

[0015] In the second aspect, the present application provides an energy storage EMS system version release verification system, which adopts the following technical solution: An energy storage EMS system version release verification system includes an energy storage EMS system distributed on-site, a locally set verification energy storage system, and an energy storage simulation management system, wherein the energy storage EMS system includes a plurality of 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; A 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; 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; The equipment 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; 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.

[0016] The technical solution provided by the embodiment of the present application has the following technical effects: Based on data call testing in real operating energy storage sites, various scenarios and various equipment differences in the energy storage microgrid can be fully covered when verifying strategies; the simulation system obtains equipment, data and command responses from the on-site energy storage site, and maintains consistency with the on-site site. 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 results, simulate the operation of various real sites, and ensure the stability and accuracy of each version release. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] 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.

[0018] Figure 2 It is a module diagram of the energy storage EMS system version release verification system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0019] To more clearly understand the purpose, technical solutions and advantages of the present application, the present application is described and illustrated below in conjunction with the accompanying drawings and embodiments. However, it should be understood by those of ordinary skill in the art that the present application can be implemented without these details. In some cases, in order to avoid unnecessary descriptions that make various 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 described in detail. For those of ordinary skill in the art, it is obvious that various changes can be made to the embodiments disclosed in 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 embodiments shown, but conforms to the broadest scope consistent with the scope claimed for protection of the present application.

[0020] It should be noted that the description of these embodiments is used to help understand the present invention, but does not constitute a limitation of the present invention. In addition, the technical features involved in each embodiment of the present invention described below can be combined with each other as long as there is no conflict between them.

[0021] In the description of this application, "several" means one or more, "more" means more than two, "greater than", "less than", "exceed", etc. are understood to exclude the number itself, and "above", "below", "within", etc. are understood to include the number itself. If there is a description of "first" or "second", it is only used to distinguish the technical features, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features or implicitly indicating the order of the indicated technical features.

[0022] In the description of the present application, the description with reference to the terms "one embodiment", "some embodiments", "illustrative embodiments", "examples", "specific examples", or "some examples" means that the specific features, structures, materials, or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials, or characteristics described may be combined in any one or more embodiments or examples.

[0023] like Figure 1 As shown, the embodiment of the present application discloses a method for verifying the release of an energy storage EMS system version, comprising the following steps: S100, connecting to each distributed on-site energy storage site and waiting for registration, and completing device synchronization after registration.

[0024] This step is performed 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 registration is completed, the energy storage EMS system version release verification system can synchronize devices with the energy storage site to obtain various types of data uploaded by the energy storage site in real time. These data include operating parameters at runtime, information about the equipment in the energy storage site, and information about the construction of each subsystem in the energy storage site.

[0025] S200, performing data call testing to obtain energy storage data corresponding to each on-site energy storage site, where the energy storage data includes scene data, equipment data, and operation data.

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

[0027] After calling and integrating the above data, the energy storage simulation management system will send it to the local energy storage system for verification based on certain strategies and verification requirements.

[0028] S300, selecting an energy storage verification strategy to capture energy storage data of a preset duration 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.

[0029] Energy storage strategies are characterized by different energy storage strategies corresponding to the different environments, application fields, and special electricity consumption plans of energy storage power stations, 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 locations of the feature nodes that need to be verified in different strategies. The location can be the node location of the trigger quantity or the node location in time.

[0030] After selecting the energy storage verification strategy, energy storage data of a preset duration is selected based on the specific content of the strategy and integrated in the energy storage simulation management system. After integration, it is used as a verification instance for distribution to subsequent local systems for simulation and verification.

[0031] S400: Push the energy storage data to the local verification energy storage system to start the verification instance.

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

[0033] S500, 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.

[0034] Since the energy storage simulation management system obtains real-time data from actual on-site energy storage sites, the EMS operation reporting center in the system can generate an actual operation report based on the actual operation data based on the data it obtains. The report is represented by the corresponding result data and process data of the system operation over a period of history.

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

[0036] S600: Compare the actual operation report and the verification report, and generate a version verification result based on the comparison result.

[0037] 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 scene, the same equipment, and the same operation data, it can compare the contents of the two reports and determine the version verification result based on the comparison results.

[0038] Among them, the comparison contents mainly include revenue, operating hours, equipment power, etc.

[0039] Through the above method, based on the data call test in the real operating energy storage site, various scenarios and various equipment differences in the energy storage microgrid can be fully covered when verifying the strategy; the simulation system obtains equipment, data and command responses from the on-site energy storage site, and maintains consistency with the on-site site. The energy storage EMS system operation instance simulates the above actual scenario, 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, simulate the operation of various real sites, and ensure the stability and accuracy of each version release.

[0040] In some other embodiments, performing data call testing to obtain energy storage data corresponding to each on-site energy storage site includes the following steps: S210, obtaining first configuration information of each subsystem in the on-site energy storage site, and constructing a corresponding microgrid scenario based on the subsystem type, subsystem quantity, and subsystem combination in the first configuration information to generate scenario data.

[0041] When the energy storage site completes the registration synchronization with the energy storage site registration center, the reported subsystem composition information is first obtained. If the subsystems contained in different energy storage sites are different, they are represented in different microgrid scenarios. For example, in the microgrid scenario of the charging station, the subsystems included include the energy storage subsystem, the municipal electronic system, the load subsystem, and the charging pile subsystem; the community microgrid scenario includes the energy storage subsystem, the municipal electronic system, the load subsystem, and the photovoltaic subsystem.

[0042] Then, based on the first composition information of several subsystems obtained at 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.

[0043] The scenario data is used as the reference data for scenario construction when the local system is simulated and verified later. In different scenarios, the running data and corresponding verification strategies are different.

[0044] S220, obtaining second configuration information of devices in each subsystem, and generating device data based on the device type, device manufacturer, and device protocol in the second configuration information.

[0045] After the microgrid scene is built, the microgrid device center obtains the type information of each device contained in each subsystem (PCS, BMS, photovoltaic inverter, electric meter, DIDO, air conditioning, fire protection, etc.), the manufacturer of each device, and the device protocol used by each device.

[0046] After these data are collected, they are integrated into device data, which is used as reference data for setting up the device environment during subsequent local system simulation verification.

[0047] S230, acquiring the interaction instruction action, interaction timestamp and interaction response result of each device to obtain an interaction log, and using the interaction log as operation data.

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

[0049] The interaction log represents the operating status of each device in the scene. The interaction log is used as operating data, which is used as simulated or real interaction data for subsequent local system simulation verification.

[0050] In other embodiments, selecting an energy storage verification strategy includes the following steps: S310, uploading the energy storage verification strategy and classifying it to obtain a time verification class and a node verification class.

[0051] The energy storage verification strategy is uploaded by the user. When uploading, it is mainly divided into time verification type and node verification type according to different energy storage verification strategies.

[0052] The time verification category is characterized by reacting to the nodes that appear at the characteristic time for key verification. For example, under the peak shaving and valley filling strategy, it is necessary to focus on the changes in the operating data of each device in the energy storage power station during the valley price time around 12 o'clock in the evening and the peak price time around 12 o'clock in the afternoon for comparative simulation verification.

[0053] The node verification category is characterized by reacting to the nodes where characteristic numerical points appear for key verification. For example, under the maximum virtual quantity strategy, it is necessary to pay attention to whether the power value exceeds the preset maximum value at a certain moment. Then, when the power exceeds the preset maximum value at a certain point in time based on the real-time device power data, the time when the numerical point appears and the period of time thereafter are the focus of attention, and compared simulation verification is performed based on its changes.

[0054] S311, obtaining a characteristic time point based on the time verification class, and configuring a corresponding minimum time period with the characteristic time point as the starting point to generate a verification time.

[0055] When the energy storage verification strategy is a time verification type, first select the characteristic time point based on the specific content of the strategy, then configure a minimum time period based on the characteristic time point combined with the verification requirements. The minimum time period represents the length of time that must be verified under different verification requirements or verification accuracies. Finally, the corresponding verification time is generated after combining the minimum time period.

[0056] For example, under the peak-shaving and valley-filling strategy, if 11 p.m. is the characteristic time point, because the valley time is generally 8 a.m. 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 p.m. to 8 a.m. the next day.

[0057] For example, if the accuracy 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., and if higher accuracy and lower risk verification is required for version release verification, the verification time can be set to 1 day.

[0058] S312, obtaining a trigger node based on the node verification class, and detecting the electric energy data in real time until the trigger node is reached, and configuring a corresponding verification time based on the current time point as the starting point. The electric energy data includes power, voltage, current, and frequency.

[0059] If the strategy type is a node verification class, a trigger node is set based on its specific content. The trigger node is an action trigger value corresponding to an electric energy data type, such as a certain kW of power, a certain V of voltage, and so on.

[0060] After setting up, the data uploaded by the real-time energy storage site is used to determine whether the various power data during operation have reached the action trigger value. If reached, the triggering moment is taken as the starting point, and the verification time is also configured based on the verification accuracy requirements.

[0061] The preset duration is not less than the verification time. Because the verification time is the minimum time that must be fully verified under the energy storage verification strategy, in order to ensure the accuracy of the verification results before the version is released and meet the verification requirements, when capturing energy storage data for a certain period of time, it is necessary to ensure that the time period of the captured data is completely covered by the verification time. In this way, when the generated verification instance is verified in the local verification energy storage system, the local verification energy storage system can fully cover the time period that needs to be verified.

[0062] In other embodiments, the selection of verification strategies is also changed dynamically and intelligently, and according to the verification requirements of the actual version release, verification strategy a can be selected at y o'clock every day from x1 to x2, and verification strategy b can be selected all day from x3 to x4.

[0063] In other embodiments, selecting an energy storage verification strategy to capture energy storage data of a preset time length at a corresponding feature position and integrating and generating a verification instance includes the following steps: S320, selecting a corresponding on-site energy storage site as an object to be verified, and finding a location of a matching characteristic time point or trigger node of the object to be verified based on the selected energy storage verification strategy to obtain energy storage data over a preset time period.

[0064] S321, configuring verification scenarios, verification equipment and verification operation tasks based on energy storage data over a preset time period to integrate them into a verification instance.

[0065] When verification is required before version release, first select the corresponding on-site energy storage site as the object to be verified, and use the energy storage verification strategy to find the location of the corresponding time point or node and obtain the energy storage data of the preset duration for integration. After integration, configure the verification scenario based on the scenario data, configure the verification equipment based on the equipment data, and finally configure the verification operation task based on the operation data, and integrate the whole into a complete verification instance.

[0066] After pushing the verification instance to the local verification energy storage system, the instance is started so that the local verification energy storage system can perform operation simulation based on the same scenario, the same equipment, and the same operation interaction actions as the real system.

[0067] In other embodiments, selecting an energy storage verification strategy to capture energy storage data of a preset time length at a corresponding feature position and integrating and generating a verification instance further includes the following steps: S330, comparing the scene data of each on-site energy storage site to determine whether there is a repeated scene.

[0068] A repeated scenario is characterized by the scenario data corresponding to two or more on-site energy storage sites being exactly the same.

[0069] S331: If so, define the on-site energy storage sites corresponding to the multiple repeated scenarios as sites to be processed.

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

[0071] If there are repeated scenarios, the energy storage sites corresponding to the multiple repeated scenarios are defined as sites to be processed, and subsequent steps are used to determine whether to retain one or more.

[0072] S332, obtaining the number of selected energy storage verification strategies, and determining whether the number is greater than 1.

[0073] S333: If it is not greater than, select any site to be processed in the repeated scene as the object to be verified.

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

[0075] S335: If the verification requirement is urgent processing, any site to be processed in the repeated scene is selected as the object to be verified.

[0076] 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, then in the repeated scenario, the number of sites to be processed that is the same as the number of energy storage verification strategies is selected as objects to be verified.

[0077] 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, all sites to be processed are taken as objects to be verified.

[0078] First, determine the number of energy storage verification strategies. If the number of different energy storage verification strategies is greater than 1, then different energy storage verification strategies have different characteristic times to be verified. Therefore, energy storage sites in repeated scenarios combined with different energy storage verification strategies can still correspond to two different verification instances.

[0079] Furthermore, the urgency of the current system version verification link is determined. If the verification needs to be completed as soon as possible, the energy storage data in the on-site energy storage sites needs to be quickly acquired and quickly integrated into several verification instances. If multiple sites to be processed are retained for data call testing, the energy storage simulation management system will acquire multiple sets of the same data in parallel and select the required data based on the characteristic time, which will slow down the processing speed of the energy storage simulation relationship system.

[0080] When dealing with emergencies, it is necessary to select any site to be processed as the object to be verified, and select the time period data corresponding to each energy storage verification strategy from the continuous data of this on-site energy storage site, so that one object to be verified can correspond to multiple verification instances.

[0081] If the system version verification is not urgent, a longer verification period can be allowed. In this case, multiple sites with repeated scenarios can be selected as the objects to be verified. Each object to be verified corresponds to a storage verification strategy and a verification instance.

[0082] Secondly, it is also necessary to determine in advance whether the number of sites to be processed during buffering 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 energy storage verification strategies. At this time, you only need to select the same number of sites to be processed as the energy storage verification strategies as the objects to be verified.

[0083] If it is less than the number of energy storage verification strategies, it means that the pending sites of the current repeated scene cannot be assigned to all energy storage verification strategies. At this time, all pending sites can be selected as pending verification objects, and after evenly assigning energy storage verification strategies, the remaining unassigned energy storage verification strategies are randomly sent to the corresponding number of pending sites. At this time, some on-site energy storage sites of repeated scenes correspond to one energy storage verification strategy, while some on-site energy storage sites correspond to multiple energy storage verification strategies.

[0084] If the number of energy storage verification strategies is not greater than 1, it means that there is only one energy storage verification strategy. At this time, you only need to retain any one site to be processed 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 test.

[0085] In some other embodiments, pushing the energy storage data to a local verification energy storage system to start a verification instance includes the following steps: S410, 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.

[0086] After obtaining the scenario data, the verification energy storage system configures and builds a test microgrid scenario that is identical to the scenario data.

[0087] That is, a one-to-one energy storage scenario is built in the local verification energy storage system based on the subsystem configuration, type, and quantity in the scenario data. At the same time, if the corresponding subsystem exists in the local verification system, the corresponding actual subsystem is configured. If the corresponding subsystem does not exist, the non-existent subsystem is configured accordingly through the simulation software model.

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

[0089] After obtaining the device data, the energy storage system is verified to configure the test equipment that is the same as the device data.

[0090] That is, a one-to-one test device is built in the local verification energy storage system based on the device type, device manufacturer, device protocol, etc. in the device data. At the same time, if the corresponding identical device exists in the local verification system, the corresponding actual device is configured. If the corresponding identical device does not exist, the type, model, and protocol information of the non-existent device are entered into the simulation program to configure the simulation device.

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

[0092] After obtaining the operation data, the verification energy storage device extracts the interaction actions, interaction results and other information in the interaction log, and sends it to the corresponding test equipment so that each test equipment can perform simulation operation based on the corresponding operation action.

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

[0094] One verification energy storage system verifies one instance, so that the result of a verification energy storage system can correspond to the verification result of a field energy storage device in a scenario corresponding to a verification strategy for comparison, avoiding comparison deviation and ensuring a one-to-one synchronous comparison effect.

[0095] In other embodiments, sending the interaction log in the operation data to the corresponding test equipment to verify the simulation operation of the energy storage system also includes the following steps: S431, determining whether the actual device includes the action device corresponding to each interaction instruction action in the interaction log.

[0096] S432: If included, then control the actual device to perform the interactive instruction action at the corresponding interactive timestamp and achieve the interactive response result to realize the real machine verification.

[0097] S433: 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.

[0098] When the local verification energy storage system contains the action device corresponding to the interaction instruction in the interaction log, the specific interaction action can be performed directly in the physical device. For example, if there is a start of the motor at time t1 in the interaction log, and the start result is successful, then the verification energy storage system controls the corresponding motor to start when the time reaches t1, and defines that the start action must be a successful result, so as to realize real machine verification.

[0099] When the local verification energy storage system does not contain the action devices corresponding to some interactive instruction actions in the interaction log, the specific interactive actions cannot be performed on the actual equipment. For example, if there is no PCS in the local verification energy storage system, the startup and shutdown actions of the PCS cannot be performed on the actual equipment.

[0100] Then, when there is no equipment that can actually perform actions, in order to verify that the actions and operating status of the energy storage system are completely consistent with the on-site energy storage site, the interaction actions and corresponding results are directly sent to the simulation device through simulation instructions for simulation, on the premise that the interaction actions and interaction results are clearly known through the interaction log. In this way, the local verification system does not need to have all types, manufacturers, and protocols of equipment. As long as the actions and results are based on real operation and real historical data, the actions and results can be directly simulated one-to-one in the simulation model. Dynamic simulation, to ensure that the operation between the real energy storage power station and the local energy storage system remains completely consistent.

[0101] In other embodiments, the actual operation report and the verification report are compared in content, and a version verification result is generated based on the comparison result, including the following steps: S610, content comparison includes comparison of revenue results at the final time point, and comparison of operating time periods and equipment power at the real time point.

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

[0103] S620: If a confident match appears in the comparison result, it is characterized as verification passed.

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

[0105] S630: If a confidence anomaly appears in the comparison result, it indicates that the verification has failed.

[0106] If there is a mismatch in the comparison results of each data item in the two running reports, the confidence level is analyzed based on the difference between the mismatched data, the number of mismatched data, etc. If the confidence level is high, it indicates that the current verification has failed.

[0107] In some other embodiments, it also includes: S700, storing each verification instance to build a dynamic knowledge base.

[0108] When a verification instance appears and is started and passes verification, the completed verification instances are organized to build a dynamic knowledge base.

[0109] At the same time, whenever a new verification instance appears, it is necessary to verify whether the scenario, equipment, operation data and corresponding verification strategy corresponding to the verification instance are completely consistent with the verification instance already in the dynamic knowledge base before adding it to the dynamic knowledge base; if they are completely consistent, the verification instance is considered to be stored in the dynamic knowledge base, and the duplicate verification instance will not be added to the dynamic knowledge base.

[0110] S710, 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.

[0111] Whenever a version release verification task is required, first determine whether the instance requirements consisting of the required scenarios, equipment, operating information, and required verification strategies can be matched to a completely consistent 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 to start. This eliminates the need to spend time and computing power to call for data from on-site energy storage equipment.

[0112] S720: 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 energy storage data, and a new verification instance is generated in combination with the energy storage verification strategy.

[0113] If there is no fully matched verification instance in the dynamic knowledge base, one or more on-site energy storage sites are selected according to the requirements of the version verification and the energy storage verification strategy is configured to obtain energy storage data of 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.

[0114] 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 instances stored in the knowledge base continue to increase. If you want to verify any scenario later, you can directly call the instance in the knowledge base. The energy storage simulation management system can automatically build the scenario knowledge base, automatically start multi-instance verification, fully automate the verification process, and generate EMS operation report results.

[0115] like Figure 2 As shown, the present application also discloses an energy storage EMS system version release verification system, including an energy storage EMS system distributed on-site, 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 conduct data call testing to obtain energy storage data including scene data corresponding to each on-site energy storage site; 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; The equipment 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; The energy storage simulation management system is also used to select an energy storage verification strategy to capture energy storage data of a preset duration at a corresponding characteristic position and integrate and generate a verification instance. 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 energy storage data of on-site energy storage sites over a preset period of time to generate actual operation reports, and to verify the verification data uploaded by the energy storage system to generate verification reports; Compare the actual operation report and the verification report, and generate version verification results based on the comparison results.

[0116] The implementation principle is: Based on data call testing in real operating energy storage sites, various scenarios and various equipment differences in the energy storage microgrid can be fully covered when verifying strategies; the simulation system obtains equipment, data and command responses from the on-site energy storage site, and maintains consistency with the on-site site. 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 results, simulate the operation of various real sites, and ensure the stability and accuracy of each version release.

[0117] It should be understood that although the steps in the flowchart of the accompanying drawings are shown in sequence according to the instructions of the arrows, these steps are not necessarily performed in the order indicated by the arrows. Unless otherwise clearly stated in this document, the execution of these steps is not strictly limited in order and can be performed in other orders.

[0118] The above are all preferred embodiments of the present application, and the protection scope of the present application is not limited thereto. Therefore, any equivalent changes made according to the structure, shape, and principle of the present application should be included in 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; Performing 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; 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: Performing data call testing to obtain energy storage data corresponding to each of the on-site energy storage sites includes the following steps: 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; The interaction instruction action, interaction timestamp and interaction response result of each of the devices are obtained to obtain an interaction log, and the interaction log is used as the operation data.

3. 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.

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 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.

5. The energy storage EMS system version release verification method according to claim 4 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, then obtain 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.

6. 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.

7. The energy storage EMS system version release verification method according to claim 6 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.

8. 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.

9. 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.

10. 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; A 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; 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; The equipment 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; 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