Method for developing a stockyard management platform and stockyard management platform

Abstract

The present application relates to a kind of method for developing reservoir area management platform and the reservoir area management platform developed based on the method, corresponding data transmission object is generated by the code generator mapping database table structure reflection, and the code including basic management code of structure data, structure data integrity verification code, the code of the strong and weak type reference conversion of data and the code of the extension of accompanying basic business function, code generator is based on Vue+Element front-end framework and SpringBoot+Security back-end framework;The front end of the reservoir area management platform developed based on the method and its back end are based on JSON format data interaction.It can provide standardized operation and management support for reservoir operation and management unit, improve reservoir early warning and forecasting and scheduling capability, greatly improve the safety operation and management level and efficiency of reservoir, and give full play to the social and economic benefits of reservoir.

Description

Technical Field

[0001] This invention belongs to the field of reservoir automation management technology, specifically relating to a method for developing a reservoir management platform and the reservoir management platform itself. Background Technology

[0002] Currently, reservoir area management and industry management still rely heavily on traditional manual processes for handling a large amount of data and information. This approach fails to effectively manage and maintain various types of data and information, and also hinders information sharing. This not only affects the improvement of reservoir area management but also makes it difficult for water conservancy authorities at all levels to timely, accurately, and comprehensively understand the status and trends of reservoir area and industry development. Reservoir area management requires assigning different permissions to different roles involved in management, and the data displayed on the front end needs frequent updates and iterations. However, existing database management methods using front-end / back-end separation frameworks, such as CN105824619A, can only generate persistent database tables (DTOs) to facilitate the transformation from a database-oriented model to an object-oriented model. Summary of the Invention

[0003] To address the above technical problems, this invention proposes a method for developing a warehouse management platform, which uses a code generator to map the database table structure and reflectively generate corresponding data transmission objects and code with basic business functions.

[0004] The code generator generates the front-end code of the development library management platform based on the Vue + Element front-end framework, and generates the back-end code of the development library management platform based on the Spring Boot + Security back-end framework.

[0005] The code with basic business functions includes basic management code for structured data, code for verifying the integrity of structured data, and code for converting and extending strong and weak type references of data; the front-end and back-end of the development library management platform interact with each other based on JSON format; the data based on JSON format includes a main body containing both token and EntityData.

[0006] This invention can provide standardized operation and management support for reservoir operation and management units, improve reservoir early warning and dispatch capabilities, significantly enhance the safety operation and management level and efficiency of reservoirs, and fully realize the social and economic benefits of reservoirs. Attached Figure Description

[0007] Figure 1 Development process for one implementation method;

[0008] Figure 2 : A schematic diagram of a development method for one implementation. Detailed Implementation

[0009] It should be noted first that the following terms appearing in this application shall be understood as:

[0010] CSRF (Cross-site request forgery): cross-site request forgery; Token: a string generated by the server as a token for the client to make requests; EntityData: a binary named tag (NBT) for editing entities, entitydata <entity> <NBT tag> specifies the entity whose data is to be edited.

[0011] The following embodiments further illustrate the content of the present invention, but shall not be construed as limiting the present invention.

[0012] In some implementations, the steps of developing the reservoir area management platform include the steps in the process as Figure 1 : a data preparation step, a front-end construction step, a back-end construction step, and a dynamic assembly step;

[0013] The front-end construction step includes: an interface configuration step, a variable configuration step, a basic information configuration step, and an interface invocation step;

[0014] The front-end takes the Config configuration file as the core, and respectively configures the GIS terminal and the API RESTFUL data gateway according to the configuration variables;

[0015] The back-end takes the DataSource.properties configuration file as the core, and configures the reception of API resource request verification and auditing, configurable database types and database connection information according to the configuration variables;

[0016] The dynamic assembly step specifically includes: a double verification step, a double filtering step, and on-demand allocation of an invocation module and a loading module.

[0017] It should be noted that the term "dynamic assembly" includes two actions of "loading" and "configuring". The "loading" step includes that the back-end divides function areas and operation permissions according to the user's regional administrative permission, department and level, packs the available operation modules and sends the package to the front-end. The "configuring" step includes that the front-end re-verifies whether the user still matches the received module package, and then distributes the module package to each system module loading processing center for loading and display.

[0018] "Dynamic assembly" does not only exist in a simple front-end or back-end, but is a front-end plus back-end mode that performs double verification, filtering, and on-demand allocation of the invocation module and the loading module.

[0019] Specifically, for example Figure 2As shown, the code generator maps the database table structure to reflectively generate the corresponding Data Transfer Object (DTO) and the code with accompanying basic business functions. The code with accompanying basic business functions (as shown in the part below) includes basic management code for structured data, code for verifying the integrity of structured data, code for converting strong and weak type references to data, and extended code; a part of the code with accompanying basic business functions:

[0020] public String getFID(){

[0021] return FID;

[0022] public void setFID(String fID){

[0023] EID = fID;

[0024] }

[0025] @Override

[0026] public int hashCode(){

[0027] final int prime-31:int result=1;

[0028] result=prime*reault+((ADDRESS==null)?O:ADDRESS,hashCode();longtempi

[0029] temp=Double.doubleToLongBits(ELECTRIC);

[0030] result=prime*result+(int)(temp*(temp>>>>32));

[0031] result=prime*result+((ELECTRIC ID==nu11)?0:ELECTRIC ID.hashCode());

[0032] result=prime*result+(((FID=null)?0;

[0033] FID, hashCode());

[0034] result=prime*result+(((ID==null)?O:ID.hashCode());

[0035] result=prime*result+((MONITOR_TIME--null)?O:MONITOR_TIME,hashCode());

[0036] result=prime*result+((OPERATE_TIME==null)?O:OPERATE_TIME,hashCode());

[0037] result=prime*result+((REGION_ID==null)?0:REGION_ID.hashCode());

[0038] result=prime*result+((UNIQUE_ID=m nu11)?O:UMIQUE_ID.hashCode());

[0039] result=prime*result+((USER_ID==null)?0:USER_ID.hashCode());

[0040] return result;

[0041] }

[0042] @override

[0043] public boolean equals(Object obj)[

[0044] if(this==obj)

[0045] return troe;if(obj==null)

[0046] return false;

[0047] if(getClass()I-obj.getClass())

[0048] return false;

[0049] ……

[0050] The code generator generates the front-end code for the development repository management platform based on the Vue+Element front-end framework, and generates the back-end code for the development repository management platform based on the SpringBoot+Security back-end framework. The front-end and back-end of the development repository management platform interact based on JSON format data, which includes a main body containing both token and EntityData.

[0051] In the process of calling the API, the order of API calls is as follows: front-end sends request, gateway, back-end, database API.

[0052] In some specific implementation methods, the data preparation steps include the following:

[0053] Data from the reservoir area is collected using intelligent data acquisition devices, including intelligent water level gauges and intelligent rain gauges.

[0054] Data from the storage area is processed using multi-source heterogeneous data integration technology;

[0055] The data in the storage area is stored in any relational database, including Oracle, SQL Server, and MySQL.

[0056] Some more specific implementations of the backend setup steps include configuration steps and CSRF protection steps, wherein the configuration steps include: cross-domain, authentication, encryption, access control configuration, and dynamic gateway configuration;

[0057] The specific dynamic gateway supports hot configuration, hot update, hot start, low latency, high efficiency distribution, centralized configuration and request processing, multi-threaded task distribution, hot database switching, multi-node switching, and unauthorized request interception.

[0058] The backend is also configured to load any one or more models, including engineering technology models, management technology models, and information technology integration models. Specifically, this includes: generating engineering technology models through model drawing or real-scene photography; generating management technology models based on on-site operation management and scheduling modes; and finally generating information technology integration models by customizing the models according to the specific content of engineering infrastructure and monitoring.

[0059] Some more specific implementation methods for multi-source heterogeneous data integration technology include the following steps:

[0060] The collected data from the storage area is standardized according to the standardized data receiving database table structure;

[0061] The receiving server deploys a receiving service to uniformly receive standardized reported data.

[0062] In some specific implementations, the front-end is configured to support a visual interface for automatically generating code, through which operations including CRUD operations, sorting, exporting, and access control are generated. The back-end setup steps specifically include configuration steps and CSRF protection steps, wherein the configuration steps include cross-domain, authentication, encryption, and access control configurations; the back-end is also configured to load any one or more models, including engineering technology models, management technology models, and information technology integration models.

[0063] In order to improve the overall service efficiency of the reservoir area by combining the business needs of reservoir area safety management, operation management and maintenance management, a code generation rapid development framework with front-end and back-end separation mode is adopted. Compared with the traditional three-layer full-stack architecture mode, this implementation method is easy to develop, has low requirements for technical personnel, and has weak coupling between front-end and back-end programs.

[0064] Some implementations of the reservoir management platform developed based on any of the above implementations can realize functions including scheduling procedures, meteorological monitoring, water and rainfall monitoring, flood forecasting, flood control scheduling, beneficial scheduling, gate valve operation, and water supply management. The front end of the platform supports a visual interface for automatically generating code, through which operations including adding, deleting, modifying, querying, sorting, exporting, and access control are generated.

[0065] In some implementation methods, the developed reservoir management platform can realize functions including scheduling procedures, meteorological monitoring, water and rainfall monitoring, flood forecasting, flood control scheduling, beneficial scheduling, gate valve operation, and water supply management.

[0066] This platform also enables the management of engineering equipment and facilities, as well as their maintenance and upkeep, and facilitates flood control and beneficial resource allocation. Flood control allocation includes: reservoir user terminals submitting request forms, control centers issuing instruction forms, reservoir user terminals issuing early warning instruction forms, reservoir user terminals sending early warning feedback, and reservoir user terminals issuing operation instructions. Beneficial resource allocation includes: dispatch personnel developing allocation plans, control centers approving and issuing allocation plans at different levels, operation departments receiving beneficial resource allocation orders, operation departments providing feedback on actual operations, operation personnel providing feedback on operations to reservoir user terminals, and operation personnel providing feedback on operations to the control center.

[0067] Some implementation methods, using a warehouse management platform developed through any of the above implementation methods, manage engineering equipment and facilities and their maintenance status, specifically including the following steps: maintenance objects, routine maintenance, specialized repairs, and property-style management, specifically including:

[0068] 1) Project Inspection: Inspection personnel conduct outdoor inspections via mobile devices and report inspection records and routes. The main inspection items include management buildings, water-retaining structures, and drainage structures. If problems are found during the inspection, the hazard handling procedure is initiated.

[0069] 2) The reservoir patrol module primarily records and displays the results of patrols and inspections of the reservoir surface. By binding patrol equipment to patrol vessels, it automatically records the patrol trajectory and can record any anomalies or enforcement actions discovered during the patrol process.

[0070] 3) Engineering safety monitoring: The changes in monitoring data are displayed in the form of line graphs.

[0071] It acquires and analyzes monitoring data from dams, corridors, and reservoir perimeters. Data can be filtered and displayed by time, monitoring type, keywords, etc.

[0072] 4) Record and statistically analyze the project safety assessment. Display the number of assessments, the latest assessment results, and the completion time. Users can add and modify safety assessment-related information, upload relevant documents, and view detailed assessment reports online in PDF format.

[0073] 5) Displays and records information on reservoir reinforcement and safety improvements, including the time of reinforcement and improvements, before and after photos, and other data. Users can edit reinforcement and safety improvement information and upload relevant images. Data can be searched using keywords such as year and name.

[0074] 6) Hazard Source Management: Store and record all hazard sources in the reservoir. Enter all potentially hazardous substances and capabilities in the reservoir, as well as equipment, facilities, or locations that may cause harm to people, property, or the environment, into the hazard source management module. Regularly push hazard source information to all users to enhance their awareness and understanding of existing hazard sources, raise their vigilance, and enable users to guard against hazard sources in the reservoir at all times.

[0075] 7) Hazard Management: Conduct standardized procedures for identifying and repairing hazards encountered by patrol personnel during patrols.

[0076] Some implementation methods, achieved through a reservoir management platform developed using any of the above methods, manage reservoir scheduling and operation, including scheduling procedures, meteorological monitoring, hydrological and rainfall monitoring, flood forecasting, flood control scheduling, beneficial water use scheduling, gate and valve operation, and water supply management. Specific operations are as follows:

[0077] 1) Dispatch Procedures: The Dispatch Procedures module stores and displays the written reservoir dispatch procedures. You can modify and update the uploaded PDF files of the dispatch procedures, and you can filter and search for files by filename.

[0078] 2) Flood Control Scheduling: The system implements the flood control scheduling process, ensuring traceability of scheduling and timely and accurate transmission of scheduling information. The flood control scheduling process has been designed and can be customized through the platform. The specific process is as follows:

[0079] The reservoir submits a request form, the flood control office issues an instruction form, the reservoir issues an early warning instruction form to carry out various preparatory work before opening the gate, sends early warning feedback, the reservoir issues an operation order, and the reservoir performs flood control scheduling operations.

[0080] 3) Beneficial Water Use Scheduling: The system implements the scheduling processes for beneficial uses (water supply and irrigation, sediment control, power generation, and ecological water use), ensuring traceability and timely and accurate information transmission. The scheduling process is designed to be customizable through the platform. The specific process is as follows:

[0081] Dispatchers formulate dispatch plans according to the prescribed frequency, approve and issue the dispatch plans according to the hierarchical process, the operation department receives the Xingli dispatch order, the operation department reports the actual operation status, the operators report the operation status to the reservoir, and the operators report the operation status to the superior competent department.

[0082] 4) Gate Valve Operation: The gate operation module records a series of information related to the opening and closing of the gate. This includes completing and storing dispatch order information, recording early warning information, and recording the gate's opening, adjustment, and closing height and time. This allows users with advanced privileges to have a complete understanding of the gate's operational information. By monitoring and recording the gate's operational data, quarterly or annual dispatch ledgers are generated for operation and management personnel to review and analyze.

[0083] 5) Water Supply Management: The water supply management module manages the reservoir's water use plan, water supply process, and related records, and schedules water use according to the plan. By analyzing historical data recorded during scheduling, optimal scheduling can be achieved, maximizing water supply revenue. Water supply management also provides unified management of water fee collection, including water prices, user data, and other relevant information.

[0084] Some implementation methods utilize a warehouse management platform developed through any of the above implementation methods to manage engineering equipment and facilities and their maintenance, ensuring the integrity of the engineering equipment and facilities. This includes functions such as maintenance targets, routine maintenance, specialized repairs, and property management. Specifically, it includes:

[0085] 1) Maintenance Objects: This category includes all equipment and objects requiring maintenance and upkeep, such as hydraulic structures, management buildings, flood control vehicles and vessels, gate hoists, and backup power supplies. Facilities can be added, and information such as facility name, management requirements, responsible person, remarks, and images can be added. The system allows for quick filtering of corresponding maintenance objects using keywords such as name.

[0086] 2) Routine Maintenance: Stores and displays maintenance records for all objects under maintenance. Specifically, the responsible person fills out a project application, which must include reservoir information, the amount requested, the applicant, and upload the maintenance application documents before submitting it to the superior user for approval. During the approval process, the responsible person can check the application progress and modify the application content at any time. It also records routine maintenance activities, including the time, personnel involved, and the condition before and after the maintenance.

[0087] 3) Specialized Maintenance: A management module is established for approved maintenance projects. Users can add and modify information such as project name, project type, project source, planned start time, planned end time, funding, and project details. The maintenance process is recorded, and before-and-after comparisons can be viewed.

[0088] Some implementation methods have developed warehouse management platforms that support a variety of terminal devices, including computers, tablets, and mobile phones.

[0089] The embodiments of the subject matter described in this specification can be implemented as one or more computer programs, that is, one or more modules of computer program instructions encoded on one or more tangible non-transitory program carriers, for execution by a data processing device or for controlling the operation of a data processing device.

[0090] The processing and logic flow described in this specification can be executed by one or more programmable computers that execute one or more computer programs by processing input data and generating output to run functions.

[0091] The term "data processing device" encompasses all kinds of devices, apparatuses, and machines for processing data, including, for example, programmable processors, computers, or multiprocessor systems or multiple computers. In addition to hardware, a device may include code that creates the execution environment for the associated computer program, such as code constituting processor firmware, protocol stacks, database management systems, operating systems, or combinations thereof. Computer programs can be written in any form of programming language, including compiled or interpreted languages, declarative or procedural languages, and can be deployed in any form, including as standalone programs or as modules, components, subroutines, or other units suitable for use in a computing environment. Computer programs can be deployed to execute on one or more computers located in one place or distributed across multiple locations and interconnected via a communication network.

[0092] The embodiments of the subject matter described in this specification can be implemented in a computing system that includes back-end components such as a data server, or middleware components such as an application server, or front-end components such as a client computer having a graphical user interface or a web browser through which a user can interact with the embodiments of the subject matter described in this specification, or the computer system includes any combination of one or more such back-end components, middleware components, or front-end components. Components in the system can be interconnected via digital data communication through any form or medium, such as a communication network. The computing system may include clients and servers. Clients and servers are typically geographically separated and typically interact via a communication network. The relationship between clients and servers is established using computer programs running on their respective computers and having client-server relationships with each other.

[0093] Although the present invention has been described in detail above with general descriptions, specific embodiments, and experiments, modifications or improvements can be made to it, which will be obvious to those skilled in the art. Therefore, all such modifications or improvements made without departing from the spirit of the present invention fall within the scope of protection claimed by the present invention.

Claims

1. A method for developing a warehouse area management platform, characterized in that, The method uses a code generator to map the database table structure and reflectively generate corresponding data transmission objects and code with basic business functions. The code generator generates the front-end code of the library management platform based on the Vue+Element front-end framework, and the code generator generates the back-end code of the library management platform based on the SpringBoot+Security back-end framework. The code with basic business functions includes basic management code for structured data, code for verifying the integrity of structured data, and code for converting and extending strong and weak type references of data; the front-end and back-end of the warehouse management platform interact with each other based on JSON format; the data based on JSON format includes a main body containing both token and EntityData; The method further includes a dynamic assembly step, which includes an assembly step and a fitting step. The packing step includes: the backend divides functional areas and operation permissions according to the administrative authority, department and level of the user's region, packs and boxes the modules that can be operated and sends them to the frontend; The allocation step includes: after the front end verifies whether the user and the package match again based on the received module package, it allocates the package to each system module loading and processing center for loading and display; The front-end and back-end perform dual verification and dual filtering on the user and the module package, and allocate the calling module and loading module as needed; The method further includes: a data preparation step, a front-end setup step, and a back-end setup step; the front-end setup step includes: an interface configuration step, a variable configuration step, a basic information configuration step, and an interface call step. The front end is based on the Config configuration file, and the GIS terminal and APIRESTFUL data gateway are configured according to the configuration variables. The backend is based on the DataSource.properties configuration file, and it can configure the API resource request verification and approval, database type and database connection information according to the configuration variables. The order of calling the interfaces in the interface calling steps is as follows: front-end sends request, gateway, back-end, database interface; The backend setup steps specifically include configuration steps and CSRF protection steps, wherein the configuration steps include: cross-domain, authentication, encryption, access control configuration, and dynamic gateway configuration; The dynamic gateway supports hot configuration, hot update, hot start, low latency, high efficiency distribution, centralized configuration and request processing, multi-threaded task distribution, hot database switching, multi-node switching, and unauthorized request interception. The backend is also configured to load any one or more models, including engineering technology models, management technology models, and information technology integration models. Specifically, this includes: generating engineering technology models through model drawing or real-scene photography; drawing and generating management technology models based on on-site operation management and scheduling modes; and finally generating information technology integration models by customizing the models according to the specific content of engineering infrastructure and monitoring.

2. The method as described in claim 1, characterized in that, The data preparation step specifically includes the following steps: Data from the warehouse area is collected using intelligent data acquisition equipment; The data in the storage area is processed using a multi-source heterogeneous data integration technology; The data in the storage area can be stored in any relational database, including Oracle, SQL Server, and MySQL.

3. The method as described in claim 2, characterized in that, The data preparation step specifically includes the following steps: The collected data from the storage area is standardized according to the standardized data receiving database table structure; The receiving server deploys a receiving service to uniformly receive standardized reported data.

4. The method as described in claim 3, characterized in that, The front end is configured to support a visual interface for automatically generating code, through which operations including CRUD operations, sorting, exporting, and access control are generated.

5. A warehouse area management platform, characterized in that, The warehouse management platform is developed based on any one of the methods described in claims 1 to 4, and the warehouse management platform includes a front-end and a back-end.

Images