Energy storage laboratory management system and test method thereof
By designing the energy storage laboratory management system, the information island problem caused by traditional energy storage testing management methods is solved, and cross-departmental collaborative work is optimized and system maintainability is improved.
Patent Information
- Application Number
- CN202411947128.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-27
- Publication Date
- 2025-04-25
AI Technical Summary
Traditional energy storage testing management methods lead to information silos between different management tools, hindering collaborative work across departments and groups.
An energy storage laboratory management system is designed, including a database, business logic layer and display layer. Through a modular structure, the full process coverage of project establishment to test tasks is achieved, and information circulation and collaboration efficiency are optimized.
Through a full-process management system, the information circulation and collaboration efficiency between departments and groups is optimized, and the system maintainability and scalability is improved.
Smart Images
Figure CN119883910A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of energy storage testing, and in particular to an energy storage laboratory management system and a testing method thereof. Background Art
[0002] Energy storage is a comprehensive industry, in which energy storage testing includes not only hardware and circuit-related testing, but also software testing.
[0003] Traditionally, hardware and circuit-related test data management and maintenance are performed in Excel spreadsheets, while software testing uses the ZenTao platform to manage and maintain exceptions; this separate management method leads to information islands between different management tools, hindering cross-departmental and group collaboration. Summary of the invention
[0004] To solve the above problems, the present application discloses a safe power supply circuit and its control method, which optimizes the information flow and collaboration efficiency between departments and groups by achieving full process coverage from project establishment to test task completion, and improves the maintainability and scalability of the system.
[0005] The first technical solution adopted in this application is: to provide an energy storage laboratory management system, including:
[0006] A database storing user information, project information, entrustment information, use case information, exception information and task information;
[0007] Business logic layer, which includes user management module, project management module, entrustment management module, use case management module, exception management module and task management module; the business logic layer receives information from the database and calls corresponding modules to work;
[0008] The presentation layer receives the test results of the business logic layer and presents them.
[0009] It also includes an ORM framework, based on which the business logic layer and the database complete data interaction.
[0010] It also includes a unified interface layer, based on which data interaction between the presentation layer and the business logic layer is realized.
[0011] The business logic layer further includes a product management module and a file management module, based on which product information is added and / or product information is managed; based on the file management module, a test report is obtained and saved in a file form.
[0012] Among them, the task management module includes a task board unit, based on which the progress of the test task is obtained and fed back to the display layer in real time; based on the task board unit, the test exception information in the test task process is obtained, and the task board unit sends the test exception information to the exception management module.
[0013] The second technical solution adopted in the present application is to provide a testing method, which is applied to the energy storage laboratory management system as described in any of the above items, and comprises the following steps:
[0014] Step S11: Create a project based on the project management module and add product information using the product management module; the entrustment management module initiates the test entrustment task, and the use case management module uploads the test case;
[0015] Step S12: designate test representatives and assign tasks; the task management module executes the test tasks, and records and manages any abnormal situations that occur during the process;
[0016] Step S13: The exception management module performs exception processing based on the exception information, and saves the final test results and related documents based on the file management module.
[0017] Among them, creating a new project based on the project management module, adding product information based on the product management module, initiating a test delegation task based on the delegation management module, and uploading a test case based on the use case management module will determine whether the project already exists, whether the product already exists, whether the delegation has been opened, and whether the use case already exists; based on the judgment results, the new project, new product, new delegation, and new use case are output to the task management module.
[0018] The third technical solution adopted in the present application is: an electronic device is provided, the electronic device comprising: a memory and a processor coupled to each other, the processor being used to execute program instructions stored in the memory to implement the test method as described in any one of the above items.
[0019] The fourth technical solution adopted in the present application is: providing a computer-readable storage medium, wherein the computer-readable storage medium stores program data, and the program data can be executed by a processor to implement any of the methods described above.
[0020] Beneficial effects of the present application: Different from the prior art, the present application discloses an energy storage laboratory management system and a testing method thereof; the energy storage laboratory management system includes a database, a business logic layer and a display layer; the database stores user information, project information, delegation information, use case management, exception information and task information; the business logic layer includes a user management module, a project management module, a delegation management module, a use case management module, an exception management module and a task management module; the business logic layer receives information from the database and calls the corresponding modules to work; the display layer receives the test results of the business logic layer and displays them; by achieving full process coverage from project establishment to test task completion, the information flow and collaboration efficiency between departments and groups are optimized, and the maintainability and scalability of the system are improved. BRIEF DESCRIPTION OF THE DRAWINGS
[0021] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.
[0022] in:
[0023] Figure 1 A schematic diagram of the structure of an embodiment of an energy storage laboratory management system provided by this application;
[0024] Figure 2 A structural schematic diagram of another embodiment of the energy storage laboratory management system provided by the present application;
[0025] Figure 3 A schematic diagram of the structure of another embodiment of the energy storage laboratory management system provided by the present application;
[0026] Figure 4 A schematic diagram of a flow chart of an embodiment of a testing method provided in this application;
[0027] Figure 5 A flowchart of an embodiment of an exception management module provided in the present application performing exception handling based on exception information;
[0028] Figure 6 This is a schematic diagram of the structure of an embodiment of a computer device of the present application;
[0029] Figure 7 This is a schematic diagram of the structure of an embodiment of a computer-readable storage medium of the present application. DETAILED DESCRIPTION
[0030] The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. It will be appreciated that the specific embodiments described herein are only used to explain the present application, rather than to limit the present application. It should also be noted that, for ease of description, only some but not all structures related to the present application are shown in the drawings. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the art without making creative work are within the scope of protection of the present application.
[0031] The terms "first", "second", etc. in this application are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices.
[0032] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.
[0033] This application provides an energy storage laboratory management system, which optimizes the information flow and collaboration efficiency between departments and groups by achieving full process coverage from project establishment to test task completion, and improves the maintainability and scalability of the system. Figure 1 As shown, Figure 1 A schematic diagram of the structure of an embodiment of an energy storage laboratory management system provided in this application, including a database, a business logic layer and a display layer.
[0034] The database stores user information, project information, delegation information, use case information, exception information, and task information. The following describes in detail the role of the information recorded in the database:
[0035] User information is used to record detailed information of all system users, including but not limited to name, contact information, permission level, etc.
[0036] Project information is used to store the background, goals, schedule, associated product information, etc. of each project.
[0037] The commission information is used to record the task details of the test commission, such as the commissioning party, the commissioned party, the test requirements, the estimated completion time, etc.
[0038] Use case information is used to store specific test cases for different product types and test categories, including test steps, expected results, etc.
[0039] Exception information refers to all abnormal situations that occur during the test, including exception description, occurrence time, processing status, etc.
[0040] Task information includes the status of each test task, such as task assignment, execution progress, completion status, etc.
[0041] The establishment of the database not only realizes the effective management and maintenance of the above-mentioned types of information, but also promotes collaboration and communication between departments, improves work efficiency, reduces the probability of errors, and ensures the security and integrity of data.
[0042] The business logic layer includes user management module, project management module, delegation management module, use case management module, exception management module and task management module; the business logic layer receives information from the database and calls the corresponding modules to work; the business logic layer separates the different functional modules of the system, and each module focuses on processing specific business rules and operations, making the system structure clearer, easier to understand and maintain.
[0043] Each module is designed independently, and new functions can be easily added or existing functions can be modified according to changing requirements. For example, if new test types or management processes need to be introduced in the future, only relevant modules need to be added or adjusted without large-scale reconstruction of the entire system. This flexibility enables the system to quickly adapt to changes in the market and technology.
[0044] As an intermediate layer, the business logic layer provides a unified interface for the presentation layer and other external systems to call; it simplifies the interaction between the front and back ends and ensures the consistency and stability of data transmission. For example, through the RESTful API format, the front-end web page can easily obtain and submit data, while supporting integration with other systems.
[0045] The presentation layer receives and displays the test results of the business logic layer. The presentation layer can update and display the latest test results and status changes in real time. It converts complex test results and statistical data into charts, tables, etc. to help users better understand and analyze information. It enhances the readability and interpretability of data, allowing users to quickly identify key trends and issues. For example, a line chart can be used to display task progress, or a bar chart can be used to compare the test results of different products.
[0046] In summary, the energy storage laboratory management system of this embodiment includes a database, a business logic layer and a display layer; the database stores user information, project information, delegation information, use case management, exception information and task information; the business logic layer includes a user management module, a project management module, a delegation management module, a use case management module, an exception management module and a task management module; the business logic layer receives information from the database and calls the corresponding modules to work; the display layer receives the test results of the business logic layer and displays them; by achieving full process coverage from project establishment to test task completion, the information flow and collaboration efficiency between departments and groups are optimized, and the maintainability and scalability of the system are improved.
[0047] Alternatively, if Figure 2 As shown, Figure 2 This is a structural diagram of another embodiment of the energy storage laboratory management system provided in the present application. The energy storage laboratory management system also includes an ORM framework.
[0048] Based on the ORM (Object-Relational Mapping) framework, the business logic layer and the database complete data interaction; in one embodiment, according to the system development language and technology stack, Entity Framework is selected as the ORM framework. Entity Framework is an open source ORM library provided by Microsoft and is widely used in C# development environment.
[0049] The ORM framework maps database tables to object-oriented entity classes, allowing developers to operate on the database by operating objects without having to write complex SQL statements; through automatically generated code and intuitive APIs, the workload of manually writing data access layer code is reduced, speeding up development. Code written using the ORM framework is more concise, easy to read, and easy to understand and maintain. Developers can focus on business logic rather than underlying SQL syntax and connection management.
[0050] Since the ORM framework automatically generates a lot of data access codes and provides a type-safe API, it reduces the possibility of human errors, especially the risk of security vulnerabilities such as SQL injection. Modern ORM frameworks are optimized to generate efficient SQL queries and provide a caching mechanism to reduce the number of database accesses and improve system performance.
[0051] Alternatively, if Figure 3 As shown, Figure 3 This is a structural diagram of another embodiment of the energy storage laboratory management system provided in the present application. The energy storage laboratory management system also includes a unified interface layer.
[0052] The unified interface layer is used to implement data interaction between the presentation layer and the business logic layer. As the middleware between the presentation layer and the business logic layer, the unified interface layer is responsible for processing data transmission and communication between the two. Its main functions include:
[0053] The complex operations of the business logic layer are abstracted into simple API interfaces, so that the presentation layer does not need to worry about the underlying data structure and operation details.
[0054] Convert the data format returned by the business logic layer (such as C# objects, entity classes, etc.) into a format that the presentation layer can understand (such as JSON, XML, etc.) to ensure seamless data transfer between different layers.
[0055] Receive requests from the presentation layer and distribute them to the corresponding business logic module for processing according to the request type. For example, a "get project list" request initiated by the presentation layer will be distributed to the project management module.
[0056] Assemble the results processed by the business logic layer to form response data that meets the expectations of the presentation layer. For example, merge the query results of multiple modules into a complete JSON object and return it to the front end.
[0057] Capture exceptions thrown by the business logic layer and convert them into friendly error messages or status codes so that the presentation layer can provide appropriate user prompts or log records.
[0058] During the data interaction process, the unified interface layer can integrate the permission verification mechanism to ensure that only authorized users can access specific API interfaces and data resources.
[0059] The unified interface layer can easily adjust the design and implementation of the API according to changing requirements without modifying the code of the presentation layer or business logic layer; it supports rapid iteration and functional expansion. For example, when a new presentation method or business process needs to be introduced, only the interface layer needs to be updated without large-scale reconstruction of the entire system.
[0060] Optionally, the business logic layer further includes a product management module (not shown) and a file management module (not shown), and adds product information and / or manages product information based on the product management module; obtains the test report based on the file management module and saves it in the form of a file;
[0061] Product information includes PCS, BMS or battery cells, etc., without any restrictions. The product management module provides a comprehensive view of product information to help management better understand the characteristics and requirements of products and make more informed decisions. For example, future test plans can be optimized based on historical test results of products.
[0062] Different departments (such as R&D, testing, and production) can share the same set of product data through the product management module, which enhances cross-departmental collaboration and communication. For example, R&D personnel can view the latest product specifications, and testers can obtain detailed testing requirements.
[0063] The file management module can automatically archive the documents generated after the test is completed, reducing manual intervention and improving work efficiency. For example, when a test task is completed, the system will automatically archive the relevant test reports and log files.
[0064] The file management module supports multi-person collaborative editing and commenting, making it easier for team members to discuss and improve document content. For example, testers and developers can jointly edit test reports on the same platform and exchange opinions in real time.
[0065] Optionally, the task management module includes a task board unit, which obtains the progress of the test task based on the task board unit and feeds it back to the display layer in real time; obtains the test exception information in the test task process based on the task board unit, and sends the test exception information to the exception management module; the task board unit monitors the status of each test task in real time, including the start time, expected completion time, current progress, etc. of the task. The latest task progress information is pushed to the display layer in real time to ensure that users can keep abreast of the latest progress of the task; the management can adjust the project plan and resource allocation according to the real-time progress to ensure that the project is completed on time. For example, if a task is behind schedule, more resources can be deployed in time to support it.
[0066] The task dashboard unit captures any abnormal situations that occur in real time during the test process, and records the specific description of the abnormality, the time of occurrence, the test cases involved, and other information; the captured abnormal information is automatically sent to the abnormality management module, which is further processed and tracked; the abnormal information can be discovered and passed to relevant personnel at the first time, shortening the time for problem handling and avoiding the accumulation and expansion of problems. All abnormal information is centralized in the abnormality management module for unified processing, which is convenient for subsequent analysis and improvement; for example, common problems can be found through abnormal statistical analysis to optimize the test process.
[0067] The present application also provides a testing method that can be applied to the energy storage laboratory management system of any of the above embodiments. Figure 4 As shown, Figure 4 The flowchart of an embodiment of the test method provided in this application includes the following steps:
[0068] Step S11: Create a project based on the project management module and add product information using the product management module; the entrustment management module initiates the test entrustment task, and the use case management module uploads the test case;
[0069] Step S12: designate test representatives and assign tasks; the task management module executes the test tasks, and records and manages any abnormal situations that occur during the process;
[0070] Step S13: The exception management module performs exception processing based on the exception information, and saves the final test results and related documents based on the file management module.
[0071] Optionally, creating a new project based on the project management module, adding product information based on the product management module, initiating a test delegation task based on the delegation management module, and uploading a test case based on the use case management module will determine whether the project already exists, whether the product already exists, whether the delegation has been opened, and whether the use case already exists; based on the judgment results, the new project, new product, new delegation, and new use case are output to the task management module; when the user tries to create a new project, add a new product, initiate a delegation, or upload a use case, the system will provide intelligent prompts and guidance based on the judgment results to help the user complete the operation smoothly; for existing entries, the system can automatically associate them to the corresponding task management module, reducing the user's operation steps.
[0072] By introducing a comprehensive judgment mechanism into the project management, product management, commission management and use case management modules, and outputting new projects, new products, new commissions and new use cases to the task management module based on the judgment results, the energy storage laboratory management system not only avoids duplicate creation and optimizes resource allocation, but also enhances data integrity and accuracy, simplifies user operations, promotes cross-departmental collaboration, and supports automated processes.
[0073] Alternatively, if Figure 5 As shown, Figure 5 This is a flow chart of an embodiment of an exception management module provided in the present application performing exception handling based on exception information. The exception management module performing exception handling based on exception information includes the following steps:
[0074] Step S131: adding an exception based on the exception information and selecting an exception handling strategy;
[0075] Step S132: performing exception handling based on the exception handling strategy, obtaining the exception handling progress if the exception information is handled; and reselecting the exception handling strategy if the exception information is not handled;
[0076] Step S133: determine whether the task progress has been completed, and end if completed; if the exception handling strategy is executed but the task progress is not completed, re-execute step S131.
[0077] For the above embodiment, the present application provides a computer device, see Figure 6 , Figure 6The schematic diagram of the structure of an embodiment of a computer device of the present application includes a memory and a processor, wherein the memory and the processor are coupled to each other, the memory stores program data, and the processor is used to execute the program data to implement the steps of any embodiment of the above-mentioned test method.
[0078] In this embodiment, the processor may also be referred to as a CPU (Central Processing Unit). The processor may be an integrated circuit chip having signal processing capabilities. The processor may also be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.
[0079] The method of the above embodiment can be implemented in the form of a computer program, so the present application proposes a computer readable storage medium, see Figure 7 , Figure 7 This is a schematic diagram of the structure of an embodiment of a computer-readable storage medium of the present application. The computer-readable storage medium stores program data that can be run by a processor, and the program data can be executed by the processor to implement the steps of any embodiment of the above-mentioned test method.
[0080] The computer-readable storage medium in this embodiment may be a medium that can store program data, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, or may also be a server storing the program data, which may send the stored program data to other devices for execution, or may also execute the stored program data itself.
[0081] In the several embodiments provided in this application, it should be understood that the disclosed methods and devices can be implemented in other ways. For example, the device implementation described above is only illustrative, for example, the division of the modules or units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed.
[0082] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.
[0083] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.
[0084] The above description is only an implementation method of the present application, and does not limit the patent scope of the present application. Any equivalent structure or equivalent process transformation made using the contents of the present application specification and drawings, or directly or indirectly used in other related technical fields, are also included in the patent protection scope of the present application.
Claims
1. An energy storage laboratory management system, characterized in that: include: A database storing user information, project information, entrustment information, use case information, exception information and task information; Business logic layer, which includes user management module, project management module, entrustment management module, use case management module, exception management module and task management module; the business logic layer receives information from the database and calls corresponding modules to work; The presentation layer receives the test results of the business logic layer and presents them.
2. The energy storage laboratory management system according to claim 1, characterized in that: It also includes an ORM framework, based on which the business logic layer and the database complete data interaction.
3. The energy storage laboratory management system according to claim 2, characterized in that: It also includes a unified interface layer, based on which data interaction between the presentation layer and the business logic layer is realized.
4. The energy storage laboratory management system according to claim 3, characterized in that: The business logic layer also includes a product management module and a file management module, based on which product information is added and / or product information is managed; based on the file management module, a test report is obtained and saved in a file form.
5. The energy storage laboratory management system according to claim 4, characterized in that: The task management module includes a task dashboard unit, based on which the progress of the test task is obtained and fed back to the display layer in real time; based on the task dashboard unit, the test exception information in the test task process is obtained, and the task dashboard unit sends the test exception information to the exception management module.
6. A testing method, which can be applied to the energy storage laboratory management system according to any one of claims 1 to 5, characterized in that: The steps include: Step S11: Create a project based on the project management module and add product information using the product management module; the entrustment management module initiates the test entrustment task, and the use case management module uploads the test case; Step S12: Appoint test representatives and assign tasks; The task management module executes the test tasks and records and manages any abnormal situations that occur during the test. Step S13: The exception management module performs exception processing based on the exception information, and saves the final test results and related documents based on the file management module.
7. The testing method according to claim 6, characterized in that: Creating new projects based on the project management module, adding product information based on the product management module, initiating test delegation tasks based on the delegation management module, and uploading test cases to the use case management module will determine whether the project already exists, whether the product already exists, whether the delegation has been opened, and whether the use case already exists; based on the judgment results, output new projects, new products, new delegations, and new use cases to the task management module.
8. The testing method according to claim 7, characterized in that: The exception management module performs exception handling based on exception information, including the following steps: Step S131: adding an exception based on the exception information and selecting an exception handling strategy; Step S132: performing exception handling based on the exception handling strategy, obtaining the exception handling progress if the exception information is handled; and reselecting the exception handling strategy if the exception information is not handled; Step S133: determine whether the task progress has been completed, and end if completed; if the exception handling strategy is executed but the task progress is not completed, re-execute step S131.
9. An electronic device, characterized in that: The electronic device comprises: a memory and a processor coupled to each other, wherein the processor is used to execute program instructions stored in the memory to implement the testing method according to any one of claims 6 to 8.
10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores program data, and the program data can be executed by a processor to implement the method according to any one of claims 6 to 8.