Distributed photovoltaic development, construction, operation and maintenance management system and management method

Abstract

The invention discloses a distributed photovoltaic development, construction, operation and maintenance management system and management method, and the system comprises a tenant unit which is created for each tenant; the tenant unit comprises one or more module configuration units, and the module configuration units are created for module information needing to be displayed on a page; the module configuration unit comprises one or more parameter configuration units, and the parameter configuration units are created for business elements needing to be displayed on a page; the management method is realized according to the management system. The method and the device can be applied to a system which has multi-tenant project requirements and the project requirement of each tenant has personalized characteristics, can meet the business scene of the multi-tenant project, can also realize the customization requirement of each tenant project, can realize the isolation of business data among the projects, and can also realize the customization requirement of each tenant project. And the whole platform satisfies the data overview of managers, and supports the expansion of infinite tenant projects.

Description

Technical Field

[0001] This application relates to the field of software development technology, and in particular to a distributed photovoltaic development, construction, operation and maintenance management system and management method. Background Technology

[0002] The distributed photovoltaic construction management system adopts a front-end and back-end separation architecture. The back-end mainly uses Spring Boot, Spring Cloud, and Mybatis, while the front-end mainly uses mainstream technologies such as Vue, uni-app, and Ant Design. To manage distributed photovoltaic construction operations and handle flexible and customized business scenarios across different projects, existing technologies employ the following methods: directly writing front-end code and styles on the front-end pages; if a project has personalized requirements, all business fields, including page styles, are directly written on the front-end page; when personalized requirements arise from multiple projects, it is necessary to analyze whether there are common fields or module information in each project. If there are common fields, they need to be checked on the existing front-end page; if new business fields are introduced, it is also necessary to add the new business fields on the existing project pages, and the styles of different pages also need to be rewritten based on these checks.

[0003] The above method has poor scalability, requiring continuous writing of conditional statements to add branches on a front-end page, resulting in increasingly long codebases. When there are many styles and fields, the code becomes chaotic and prone to errors. Modifying a new business function often affects other business functions that are currently in use. Moreover, the development efficiency is slow, and the testing process and workload are also large. Summary of the Invention

[0004] The purpose of the embodiments in this specification is to provide a distributed photovoltaic development, construction, operation and maintenance management system and management method to solve the problems of poor scalability and easy error correction in existing general photovoltaic construction management systems.

[0005] To achieve the above objectives, the embodiments in this specification adopt the following technical solutions: Firstly, a distributed photovoltaic development, construction, operation, and maintenance management system is provided, including: Tenant units, which are created for each tenant; A module configuration unit, wherein the tenant unit includes one or more module configuration units, which are created for the module information that the page needs to display; The parameter configuration unit includes one or more parameter configuration units, which are created for the business elements that need to be displayed on the page.

[0006] Optionally, the tenant information of the tenant unit includes the tenant name and tenant number; and / or, The module information of the module configuration unit includes module name, module number, module serial number; and / or, The business elements of the parameter configuration unit include parameter name, parameter number, and parameter sequence number.

[0007] Optionally, the module number and the parameter number are assigned according to the order of the display positions, and the order of the display positions is from left to right and from top to bottom.

[0008] Optionally, the distributed photovoltaic development, construction, operation and maintenance management system includes an online creation unit, which includes a creation template. The creation template is used to create tenant units, module configuration units, and parameter configuration units.

[0009] Secondly, a method for the development, construction, operation, and maintenance management of distributed photovoltaic power is provided, including the following steps: Multi-tenancy technology is used to create a tenant unit for each tenant, and the tenant unit includes tenant information; Create a module configuration unit in the tenant unit, the module configuration unit including the module information that the page needs to display; Create a parameter configuration unit in the module configuration unit, the parameter configuration unit including the business elements that the page needs to display; The front-end interface allows users to input tenant information, module information, or business elements, and then call the server back-end query interface to obtain the information that needs to be displayed on the page.

[0010] Optionally, the tenant information of the tenant unit includes the tenant name and tenant number; and / or, The module information of the module configuration unit includes module name, module number, module serial number; and / or, The business elements of the parameter configuration unit include parameter name, parameter number, and parameter sequence number.

[0011] Optionally, the module information is obtained from the tenant's stored data by using keyword retrieval.

[0012] Optionally, when a module configuration unit and / or parameter configuration unit needs to be moved up, down, or added, the module number corresponding to the module configuration unit and / or the parameter number corresponding to the parameter configuration unit is changed to the last digit of the module number or parameter number of the adjacent preceding position; and / or, When a module configuration unit and / or parameter configuration unit need to be deleted, the module configuration unit and / or parameter configuration unit shall be deleted.

[0013] Optionally, when the number of module configuration units and / or parameter configuration units that need to be moved up, down, added, or deleted reaches a certain number, the module serial number corresponding to the module configuration unit and / or the parameter serial number corresponding to the parameter configuration unit are reordered.

[0014] Optionally, data can be isolated based on the tenant number of the tenant unit; and / or, Each tenant unit has its own independent database storage, or multiple tenant units share the same database; and / or, Each tenant unit's data set is configured with a key.

[0015] The above-described technical solutions adopted in the embodiments of this application can achieve the following beneficial effects: This manual provides a distributed photovoltaic development, construction, operation and maintenance management system and management method, which can be applied to systems that have both multi-tenant project requirements and personalized requirements for each tenant project. It can meet the business scenarios of multi-tenant projects, realize the customization requirements of each tenant project, isolate business data between projects, and provide the entire platform with a complete data overview for the administrator, and support the expansion of unlimited tenant projects. Attached Figure Description

[0016] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments of this application and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings: Figure 1 This is a flowchart illustrating a distributed photovoltaic development, construction, operation, and maintenance management method as one embodiment of this specification. Detailed Implementation

[0017] To make the purpose, technical solutions, and advantages of this application more clear, the technical solutions of this application will be clearly and completely described below in conjunction with the specific embodiments of this application and the corresponding drawings. Obviously, the embodiments described are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0018] According to one embodiment of this application, a distributed photovoltaic development, construction, operation and maintenance management system is provided, including: Tenant units, which are created for each tenant; A module configuration unit, wherein the tenant unit includes one or more module configuration units, which are created for the module information that the page needs to display; The parameter configuration unit includes one or more parameter configuration units, which are created for the business elements that need to be displayed on the page.

[0019] On the other hand, according to one embodiment of this application, a method for the development, construction, operation and maintenance management of distributed photovoltaic power is provided, including the following steps: (1) In the distributed photovoltaic development, construction and operation management system, multi-tenant technology is used to create a tenant unit for each tenant project. The tenant information of the tenant unit includes the tenant name, tenant number, and may also include other tenant information that needs to be reflected, such as the tenant contact person and the tenant contact number. The tenant number is a unique number in the whole system and cannot be repeated.

[0020] (2) A module configuration unit function has been established on each tenant unit. A module configuration unit is established in the tenant unit. The module configuration unit is created by creating the module information that needs to be displayed on the page according to business requirements. The module information of the module configuration unit includes module name, module number, and module sequence number. The module number is a unique number in the entire system and cannot be repeated. The module sequence number is used for sorting.

[0021] Front-end developers call APIs to query module information from module configuration units and display it on the page in a loop. The back-end API returns data to the front-end. Each tenant stores all data related to that tenant. The module information to be displayed needs to be extracted from this data. This extraction process can use keyword extraction to collect keywords from the module information, then extract statements or paragraphs matching those keywords and return them to the front-end. Here, the front-end refers to the user interface, responsible for displaying content and handling interactions, while the back-end refers to the interface running on the server, responsible for handling business logic, managing data, and communicating with the front-end.

[0022] (3) Establish parameter configuration units in the module configuration units. The parameter configuration units are created by creating the business elements that each module configuration unit on the page needs to display as parameter configuration units according to business requirements. The business elements of the parameter configuration units include parameter name, parameter number, and parameter sequence number. The parameter number is a unique number in the entire system and cannot be repeated. The parameter sequence number is used for sorting. The business elements are different with the personalization of the business scenario, and the business processing flow is also different.

[0023] (4) Once the module configuration unit and parameter configuration unit are created, the front-end development of a certain tenant project only needs to call the back-end API query interface and pass in the tenant number of the corresponding tenant unit to obtain the business modules and elements to be displayed on the page (that is, the created module configuration unit and parameter configuration unit). Then, the front-end page only needs to use a for loop to display all the information on the page and complete the front-end page development. The back-end can isolate the data between each tenant according to the tenant unit number.

[0024] In the embodiments of this specification, in the distributed photovoltaic development, construction, operation and maintenance management system, the naming of tenant names, module names, parameter names, etc., is based on business requirements. For example, if a business requirement includes user information, the tenant name, module name, or parameter name will be called "user information." Each named business requirement must be distinct from the others, and the naming must reflect the content of the business, clearly indicating the content of the tenant unit, module configuration unit, or parameter configuration unit to which it belongs. Tenant numbers, module numbers, parameter numbers, etc., are assigned to each module. This numbering is like a data dictionary; for example, number 1 corresponds to the user information module. The numbering rules are defined by the developers, and the numbers are not displayed on the business interface. Regarding module serial numbers and parameter serial numbers, they are assigned according to the order of their display positions. The display position order rule is from left to right and from top to bottom, and the sorting is based on the parameter serial number. For example, if parameter A's serial number is 1 and parameter B's serial number is 2, they will be arranged according to their serial numbers, with serial number 1 displayed above and serial number 2 displayed below. If serial numbers 1 and 2 are in the same row, serial number 1 is on the left and serial number 2 is on the right. If the order is adjusted, the parameter sequence number will also change, and the display position on the page will also change. The parameter number is bound to its module number, and the module number is bound to its tenant number. A tenant unit can have multiple module configuration units, and a module can have multiple parameter configuration units. This is like a parent-child relationship: the tenant unit is the parent, the module configuration unit is the child, and the parameter configuration unit is the child of the module configuration unit. Each child records its parent's number, recursively searching for it. The naming convention can be tenant number-module number-parameter number, using a dash to represent this parent-child relationship, or other methods can be used.

[0025] The types of module configuration units and parameter configuration units within a tenant unit are determined by business requirements; only the information needed is created according to those requirements. This system enables online creation of tenant units, module configuration units, and parameter configuration units, allowing for the rapid creation of a complete template. When personalized requirements arise for adding new tenant units, a complete tenant unit structure can be quickly built. Based on the keyword information returned to the front end, the system matches the created tenant units, module configuration units, and parameter configuration units with their corresponding functions. If no matching keyword is found during creation, the system creates the appropriate module configuration unit and then the corresponding parameter configuration unit for the tenant unit, ensuring that the information returned to the front end has the necessary data location.

[0026] Tenant units and tenant numbers are in a one-to-one correspondence and are predefined, much like a data dictionary. The relationship between tenant number and tenant unit is fixed; for example, 1 corresponds to tenant A, and this remains unchanged. Developers can directly call the API with tenant number 1 to query tenant A's data. Furthermore, the distributed photovoltaic development, construction, operation, and maintenance management system allows for custom sorting of parameter configuration units. Each parameter configuration unit has its own parameter number, and we can move, move, or delete elements on the page to change their position without modifying the code. When the display changes, the system can make corresponding adjustments using methods such as moving, moving, deleting, and adding elements. For parameter configuration units that are moved up or down, the parameter number of the moving parameter configuration unit is incremented by the last digit. For example, if a parameter is numbered 3 and needs to be moved down to between parameter configuration units with parameter numbers 4 and 5, its parameter number can be changed to 4.1, thus clearly defining the order and position of this parameter configuration unit. If it needs to be moved up to between parameter configuration units with parameter numbers 1 and 2, its parameter number can be changed to 1.1. If too many parameter configuration units are moved, they can be changed sequentially from 4.2 to 4.10, and so on. Alternatively, after a certain number of moves, the parameter numbers of all parameter configuration units under a given module configuration unit can be reordered. The module number of module configuration units that are moved up or down is adjusted in the same way as the parameter number. For parameter configuration units or module configuration units that are deleted, they can be deleted directly. After a certain number of deletions, the parameter numbers of all parameter configuration units under a given module configuration unit can be reordered. For newly added parameter configuration units or module configuration units, they are added to the corresponding sequence number position based on their display location. If the added parameter is between parameter configuration units numbered 4 and 5, its sequence number becomes 4.1. After a certain number of additions, the parameter sequences of all parameter configuration units under a given module configuration unit are reordered. Alternatively, the number of moves up, down, deletions, and additions can be accumulated, and after a certain number of operations are performed within a given module configuration unit, the parameter sequences of all parameter configuration units are reordered.

[0027] The parameter settings also allow you to customize the parameter type (e.g., whether the parameter is an input box, an image, or a drop-down option), and then customize the parameter input attributes (e.g., whether it is required or optional). After the front end obtains the parameter information, it only needs to control the relevant business logic according to the parameter settings. The above is the implementation of the distributed photovoltaic development, construction, operation and maintenance management system and management methods.

[0028] When multiple tenant projects require customized development, front-end and back-end developers only need to use the distributed photovoltaic development, construction, operation, and maintenance management system and its methods. First, create new tenant units. Then, within each tenant unit, create module configuration units according to requirements, and within each module configuration unit, create parameter configuration units. The front-end only needs to obtain the unit number of each tenant unit and use it to call the back-end API query interface to quickly complete the development of each tenant project's customized requirements. The back-end isolates data based on the tenant unit's tenant number. This improves development efficiency, avoids repeated modifications within the same code module, greatly reduces the impact on other projects, and supports unlimited expansion of tenant projects. Each tenant's data can be stored in an independent database, or, to save storage costs and facilitate management, all tenants can share the same database, distinguished by tenant number. Each tenant's data set is assigned a key, which front-end developers need to use to query the API. The tenant number can be used directly as the key, or a key can be generated after inputting the tenant number, ensuring good data security for each tenant in the shared database.

[0029] After developing the functionalities of tenant A's project based on business needs, tenant B's project suddenly came along, but both of them had the same requirements for the platform system. The existing technology involves adding branches and customized business logic to the front-end and back-end code modules of project A. This requires modifying a large amount of code in tenant A's project, and the front-end page development workload is also large. It can also easily cause bugs to appear in the originally normal business logic of tenant A's project.

[0030] This invention employs multi-tenant technology, a distributed photovoltaic (PV) development, construction, operation, and maintenance (PCO) management system and method. The distributed PCO management system and method refers to a research and development technique used when multiple tenants exist within the same business system, each tenant being an independent project with its own business processes and customized business requirements. This approach aims to centralize each project on a single platform system while enabling rapid development of customized business functions for each tenant project. This invention satisfies both data isolation between different projects and achieves unified browsing of the data platform.

[0031] This invention, powered by multi-tenant technology, proposes a module configuration unit and parameter configuration unit technical solution for the customized functions of each tenant. Tenants bind modules, and then the modules bind parameters, completing the development of the front-end business page through a single query interface. The parameter modular configuration technical solution allows for parameter movement (moving up, down, and deleting), enabling rapid adjustment of the position of business information on the page as needed, and direct deletion of unnecessary business information without rewriting code. After modular parameter configuration, parameter attributes are also set, such as parameter type (text input box, image selector, dropdown selection box), and input attributes (required, optional). Front-end developers can obtain parameter attributes along with parameter information through the API query interface, enabling direct business control. The resulting distributed photovoltaic development, construction, operation, and maintenance management system can be applied to distributed photovoltaic development, construction, operation, and maintenance management systems, replacing the traditional approach of constantly writing conditional statements and adding branches within a single code block on both the front-end and back-end.

[0032] The technical solutions provided by the various embodiments of this application are described in detail below with reference to the accompanying drawings.

[0033] Example 1: Please see Figure 1 This paper provides a method for the development, construction, operation, and maintenance management of distributed photovoltaic power, including the following steps: (1) Platform initialization: Start the low-code platform, load basic configuration and templates; multi-tenant management module, including tenant database, tenant configuration, etc.

[0034] (2) Tenant creation: The distributed photovoltaic development, construction, operation and maintenance management system completes the establishment of tenant projects through multi-tenant technology. The platform administrator or super user creates new tenants through the interface or API provided by the platform; assigns a unique tenant ID and initialization data (such as template, basic configuration, etc.) to the new tenant; and creates an independent database instance or data isolation area for the new tenant in the multi-tenant database.

[0035] After using the distributed photovoltaic development, construction, operation and maintenance management system, you can first create a tenant project (Project A) and assign it a unique number (this number is unique throughout the system). Then, on the tenant project, divide the business data that needs to be displayed on the page into modules and define a name and number for each module (the module is the type name of each category of business information on the page). Each business data name that needs to be displayed within a module is defined as a parameter (the parameter is actually a field on the page), and the parameter is assigned a unique number (this number is unique throughout the system). Front-end and back-end personnel only need to obtain the name of the module and the name of the parameter based on the predefined tenant project number, module number, and parameter number during development, and then display them on the page of the tenant project. When the B tenant project needs to start, a new tenant for the B tenant project is created directly in the tenant unit, and a number is assigned to it. Similarly, through parameter modular configuration technology, in the parameter management of the B tenant project's tenant unit, a name and number are defined for each module configuration unit of the business information according to the business requirements of the B tenant project (this number cannot be repeated throughout the system). The business field data that needs to be displayed on the page is defined as the parameter configuration unit within the module (the parameters are the fields on the page), and the parameters are assigned a number (this number is unique throughout the system). Front-end and back-end developers only need to obtain the module name and parameter name based on the predefined tenant B tenant project number, module number, and parameter number during development to quickly complete the page development of the B project.

[0036] (3) Tenant configuration: Tenant administrators log in to the platform to configure tenants in detail, such as setting tenant name, domain name, logo, permission settings, etc.; according to tenant requirements, customize or adjust the low-code components, forms, processes, etc. provided by the platform.

[0037] (4) Application development: Tenant developers use the low-code tools provided by the platform to develop applications, such as drag-and-drop interface design and logic configuration; the platform automatically converts the developers’ designs into executable code or application instances.

[0038] (5) Application deployment: After the developers complete the application development, they deploy the application to the tenant's environment through the deployment tools or functions provided by the platform; the platform ensures that each tenant's application instance runs in its independent environment, realizing data isolation between tenants.

[0039] (6) Tenant use: Tenant users log in to the platform through a tenant-specific portal and use applications customized for them; the platform ensures that users can only access the data and functions of their respective tenants based on the tenant's configuration and permission settings.

[0040] (7) Platform maintenance: The platform administrator regularly maintains the platform, including updating system patches, optimizing performance, and monitoring security; the platform automatically handles data backup, recovery and migration between multiple tenants to ensure data security and availability.

[0041] (8) Tenant Management: Platform administrators or super users manage tenants, such as modifying tenant configurations, upgrading tenant versions, closing or deleting tenants, etc. The platform provides statistics and reporting functions on tenant usage to help administrators understand tenant usage and needs.

[0042] Data permissions can be isolated based on the project numbers of tenant A and tenant B. With this modular parameter configuration technology, it is no longer necessary to familiarize oneself with and modify the code of tenant A project each time. Each project's business module is self-contained based on its number, and it will not affect the business of other projects. Similarly, when more tenant projects have customized needs to be developed, the same method can be used to quickly complete the development of customized business functions of tenant projects using modular parameter configuration technology. This not only improves development efficiency, but also greatly reduces the probability of mutual interference and problems during the coding process. No matter what kind of customized business scenario, modular parameter configuration can be performed according to requirements, realizing the infinite expansion of the platform.

[0043] It should be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0044] The above descriptions are merely embodiments of this application and are not intended to limit this application. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of the present invention; at the same time, for those skilled in the art, there will be changes in specific implementation methods and application scope based on the ideas of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application. In summary, the content of this specification should not be construed as a limitation of the present invention, and any modifications, equivalent substitutions, and improvements made within the principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A distributed photovoltaic development, construction, operation and maintenance management system, characterized in that, include: Tenant units, which are created for each tenant; A module configuration unit, wherein the tenant unit includes one or more module configuration units, which are created for the module information that the page needs to display; The parameter configuration unit includes one or more parameter configuration units, which are created for the business elements that need to be displayed on the page.

2. The distributed photovoltaic development, construction, operation and maintenance management system according to claim 1, characterized in that, The tenant information of the tenant unit includes the tenant name, tenant number; and / or, The module information of the module configuration unit includes module name, module number, module serial number; and / or, The business elements of the parameter configuration unit include parameter name, parameter number, and parameter sequence number.

3. The distributed photovoltaic development, construction, operation and maintenance management system according to claim 2, characterized in that, The module number and the parameter number are assigned according to the order of their display positions, which are from left to right and from top to bottom.

4. The distributed photovoltaic development, construction, operation and maintenance management system according to claim 1, characterized in that, The distributed photovoltaic development, construction, operation and maintenance management system also includes an online creation unit, which includes a creation template. The creation template is used to create tenant units, module configuration units, and parameter configuration units.

5. A method for the development, construction, operation, and maintenance management of distributed photovoltaic power, characterized in that, Includes the following steps: Multi-tenancy technology is used to create a tenant unit for each tenant, and the tenant unit includes tenant information; Create a module configuration unit in the tenant unit, the module configuration unit including the module information that the page needs to display; Create a parameter configuration unit in the module configuration unit, the parameter configuration unit including the business elements that the page needs to display; The front-end interface allows users to input tenant information, module information, or business elements, and then call the server back-end query interface to obtain the information that needs to be displayed on the page.

6. The distributed photovoltaic development, construction, operation, and maintenance management method according to claim 5, characterized in that, The tenant information of the tenant unit includes the tenant name, tenant number; and / or, The module information of the module configuration unit includes module name, module number, module serial number; and / or, The business elements of the parameter configuration unit include parameter name, parameter number, and parameter sequence number.

7. The distributed photovoltaic development, construction, operation and maintenance management method according to claim 5, characterized in that, The module information is obtained from the tenant's stored data using keyword retrieval.

8. The distributed photovoltaic development, construction, operation and maintenance management method according to claim 6, characterized in that, When a module configuration unit and / or parameter configuration unit needs to be moved up, down, or added, the module number corresponding to the module configuration unit and / or the parameter number corresponding to the parameter configuration unit is changed to the last digit of the module number or parameter number of the adjacent preceding position; and / or, When a module configuration unit and / or parameter configuration unit need to be deleted, the module configuration unit and / or parameter configuration unit shall be deleted.

9. The distributed photovoltaic development, construction, operation and maintenance management method according to claim 6, characterized in that, When the number of module configuration units and / or parameter configuration units that need to be moved up, down, added, or deleted reaches a certain number, the module serial number corresponding to the module configuration unit and / or the parameter serial number corresponding to the parameter configuration unit are reordered.

10. The distributed photovoltaic development, construction, operation and maintenance management method according to claim 6, characterized in that, Data is isolated based on the tenant number of the tenant unit; and / or, Each tenant unit has its own independent database storage, or multiple tenant units share the same database; and / or, Each tenant unit's data set is configured with a key.

Images