A development system and method for rapidly forming special equipment management capability

Abstract

The application discloses a development system and method for quickly forming special equipment management capability, comprising a technical middle station framework and a business middle station framework, wherein the technical middle station framework comprises a starting management module, a database module, a cache module, an authentication module, a security module and a log module; and the business middle station framework comprises a special equipment management module. The application belongs to the technical field of special equipment management, and aims to solve the problems in the prior art that the design mode is relied on, the workload of developers needs to be increased, the codes among products lack commonality and reusability, and thus the development efficiency is reduced. The technical effects are that the core function is modularized, the user can flexibly combine and expand according to the requirements, the development and deployment efficiency is improved, efficient classification mapping and function integration are realized, the code reuse rate is improved, the code structure is standardized, and the development efficiency and system stability are improved.

Description

Technical Field

[0001] This application belongs to the field of special equipment management technology, specifically relating to a development system and method for rapidly developing special equipment management capabilities. Background Technology

[0002] Specialized equipment is an indispensable component of industrial production and daily life. Major manufacturers in this field are now launching specialized equipment products, and their safe operation and management are of paramount importance. With the acceleration of industrial modernization and the improvement of safety regulations, the safety supervision of specialized equipment has become a key area of ​​national and societal concern.

[0003] However, several pressing issues exist in current project development in this area, negatively impacting overall development efficiency and delivery speed. Specifically, existing methodologies rely on design patterns, increasing developer workload and leading to low efficiency in project setup and deployment. When customer needs change rapidly or the technology stack is broad, the division of responsibilities often struggles to adapt quickly, compromising delivery speed. As the business scope of user units or inspection and monitoring agencies expands, business logic becomes more complex. In such cases, a lack of code commonality and reusability across products results in significant duplication of effort, reducing development efficiency and increasing costs. Summary of the Invention

[0004] This application provides a development system and method for rapidly developing special equipment management capabilities. It aims to solve the problems of existing technologies relying on design patterns, which require developers to increase their workload, resulting in low efficiency in project setup and development deployment, and difficulty in guaranteeing delivery speed. At the same time, the lack of code universality and reusability between products leads to a large amount of repetitive work, thereby reducing development efficiency.

[0005] Firstly, a development system for rapidly forming special equipment management capabilities includes a technology middleware framework and a business middleware framework. The technology middleware framework includes a startup management module, a database module, a caching module, an authentication module, a security module, and a log module.

[0006] The business middleware framework includes a special equipment management module, a sensor integration module, a process module, and an inspection and testing record and report management module;

[0007] The startup management module is responsible for the system's startup, shutdown, and configuration management;

[0008] The database module provides data storage, management, and access services, and includes an entity designer and an attribute designer.

[0009] The cache module is used to accelerate data access and reduce database load through a cache strategy;

[0010] The authentication module is responsible for user identity verification and permission management, supports the creation of a role-permission-resource granular fine-grained permission allocation model, and dynamically adjusts permissions through an API interface.

[0011] The security module provides a protection mechanism for the system, including a firewall, encryption, and security access control, to ensure data and network security.

[0012] The log module is used to record system operation status and operation logs.

[0013] The special equipment management module is used to comprehensively and systematically manage special equipment.

[0014] The sensor integration module contains Internet of Things sensor binding, which integrates device basic information and operation monitoring information.

[0015] The process module provides a template-style configuration tool for different types of business processing, and users can customize the workflow according to their business needs.

[0016] The inspection and detection record report management module can dynamically generate inspection records and inspection report templates based on the table editor.

[0017] Further, the technology platform framework further includes an interface document module, a code generator module, a dynamic table editor module, and a front-end module.

[0018] The interface document module is used to generate and manage API interface documents online.

[0019] The code generator module can automatically generate specific types of code, reducing the workload of developers.

[0020] The dynamic table editor module is used to create, edit, and manage dynamic tables, supporting table creation, data addition, deletion, modification, and query, and formula calculation.

[0021] The front-end module is used to provide a front-end development framework and components, supporting modular front-end page construction.

[0022] Further, the cache module uses a Redis-based cache mechanism, and the cache module includes high-performance data access, flexible data cache strategies, support for multiple cache types, and distributed cache support.

[0023] Further, the code generator module includes a configuration setting module, a table name and path setting module, a data parsing module, a front-end component construction module, and a code generation and management module.

[0024] Further, the configuration setting module provides a plurality of configuration options for developers, who can flexibly adjust various parameters of the generated code according to business requirements;

[0025] The table name and path setting module can customize the database table name of the generated code according to business requirements, and set the dynamic module and path, so that the generated file can meet the requirements of a specific directory structure;

[0026] The data analysis module is responsible for in-depth analysis of different types of data fields;

[0027] The front-end component building module integrates a variety of commonly used front-end UI components, and developers can quickly build front-end interfaces that meet business logic by simply configuring and combining different components according to actual needs;

[0028] The code generation and management module provides a "one-click generation" function, which can generate complete front-end and back-end code at one time according to the previously configured parameters.

[0029] Further, the special equipment management module includes equipment account management, equipment point patrol management, equipment maintenance management, equipment use management, equipment scrap management, and equipment query and statistical management.

[0030] Further, the inspection and detection record report management module works as follows:

[0031] S1: In the "dynamic template configuration center", the developer needs to select the equipment type and inspection item type according to the actual business scenario, and configure the applicable record and report template;

[0032] S2: After the template configuration is completed, the user selects the template through the "record / report compilation process" and enters the relevant inspection data;

[0033] S3: After completing the data reporting, the system will automatically enter the "multi-level approval process engine", and the developer configures the approval rules of each link through the process designer;

[0034] S4: After the process approval is completed, the system automatically enters the "report output and archiving management" stage, and the developer configures the report output format.

[0035] Further, the database module works as follows:

[0036] S1: Through the multi-data source switching module, the target data source is directly selected in the visual interface to establish a connection pool;

[0037] S2: According to the actual configuration, automatically reconnect the corresponding database;

[0038] S3: When performing data update, the user calls the master-slave heterogeneous processing module, and the master-slave heterogeneous processing module automatically identifies the type of the currently operated database;

[0039] S4: The dynamic permission management module automatically identifies the role of the user after login, and generates an adapted permission statement based on the role;

[0040] S5: In the scenario where the enterprise needs to comprehensively record data change operations, the data change recording module can automatically record the insertion, update and deletion operations of the data in real time.

[0041] Further, the working steps of the cache module are as follows:

[0042] S1: The administrator sets the business data type that needs to be cached in the background through the cache strategy setting module;

[0043] S2: Set the first-level cache as the memory cache for quickly responding to hot data requests, and then further start the second-level cache for storing relatively cold data;

[0044] S3: For frequently updated content and large access volume, the administrator selects the "listen to database event to refresh cache" mode in the cache update strategy management module, in some report statistical data that do not have high real-time requirements, the user selects the "timed task to refresh cache" function, and in the scenario where the business is frequently changed in a short time but does not want to frequently refresh the cache, the user configures the "delayed cache update" function.

[0045] Secondly, a development method for quickly forming a special equipment management capability, the method steps are as follows:

[0046] S1: First, set the system startup parameters through a graphical interface or a configuration file;

[0047] S2: After the system reads the configuration, the management module is started, that is, the initialization operation is performed according to the configuration content;

[0048] S3: Load the core module, and the remaining functional modules are dynamically loaded by the module loading module when actually called;

[0049] S4: After the system is successfully started and stably runs, if the user wants to shut down the system, issue a system stop instruction through the control panel or operation and maintenance instruction;

[0050] S5: After the system stop management module receives the instruction, it will first terminate the unfinished business tasks, and then write the data in the cache into the database and close the connection pool resources.

[0051] Compared with the prior art, the present application has at least the following beneficial effects:

[0052] Based on further analysis and research on the problems of the prior art, the application improves the project construction and deployment efficiency by adopting functional modular design, modularizes the core function, and enables users to flexibly combine and expand according to the requirements. This design simplifies the system building process and improves the development and deployment efficiency. With the support of Spring Boot, the system realizes efficient classification mapping and function integration, improves the code reuse rate, standardizes the code structure, reduces the communication and maintenance cost, and can dynamically configure components to meet the changes in enterprise requirements, improve software production efficiency and quality. It solves some common difficulties and repetitive work in the software development process of special equipment industry, and improves the development efficiency and system stability. BRIEF DESCRIPTION OF DRAWINGS

[0053] Figure 1 An architecture diagram of a development system and method for quickly forming special equipment management capability is provided for some embodiments of the application;

[0054] Figure 2 An architecture diagram of a startup management module of a development system and method for quickly forming special equipment management capability is provided for some embodiments of the application;

[0055] Figure 3 An architecture diagram of a database module of a development system and method for quickly forming special equipment management capability is provided for some embodiments of the application;

[0056] Figure 4 An architecture diagram of a cache module of a development system and method for quickly forming special equipment management capability is provided for some embodiments of the application;

[0057] Figure 5 An architecture diagram of an authentication module of a development system and method for quickly forming special equipment management capability is provided for some embodiments of the application;

[0058] Figure 6 An architecture diagram of a security module of a development system and method for quickly forming special equipment management capability is provided for some embodiments of the application;

[0059] Figure 7 An architecture diagram of a log module of a development system and method for quickly forming special equipment management capability is provided for some embodiments of the application;

[0060] Figure 8 An architecture diagram of an interface document module of a development system and method for quickly forming special equipment management capability is provided for some embodiments of the application;

[0061] Figure 9An architecture diagram of a code generator module of a development system and method for quickly forming a special equipment management capability for some embodiments of the present application;

[0062] Figure 10 An architecture diagram of a front-end module of a development system and method for quickly forming a special equipment management capability for some embodiments of the present application;

[0063] Figure 11 An architecture diagram of a special equipment management module of a development system and method for quickly forming a special equipment management capability for some embodiments of the present application;

[0064] Figure 12 An architecture diagram of a sensor integration module of a development system and method for quickly forming a special equipment management capability for some embodiments of the present application;

[0065] Figure 13 An architecture diagram of a flow module of a development system and method for quickly forming a special equipment management capability for some embodiments of the present application;

[0066] Figure 14 An architecture diagram of a test and detection record report management module of a development system and method for quickly forming a special equipment management capability for some embodiments of the present application. DETAILED DESCRIPTION

[0067] In order to make the purposes, technical solutions and advantages of the present application more clear, the present application is further described in detail below in combination with the drawings and embodiments.

[0068] Embodiment One

[0069] As shown in Figure 1 , a development system for quickly forming a special equipment management capability is provided, including a technical middle platform framework and a business middle platform framework, the technical middle platform framework including a startup management module, a database module, a cache module, an authentication module, a security module, a log module, an interface document module, a code generator module, a dynamic table editor module and a front-end module;

[0070] The startup management module is responsible for the startup, stop and configuration management of the system, and ensures the smooth operation of the system; the startup management module is configured to include automatic startup and stop management, flexible configuration management, support for multi-environment deployment, scalability and customizability, and integrated operation interface.

[0071] The database module provides data storage, management and access services, including an entity designer and an attribute designer, and users can freely define field attributes, in addition to conventional data types, and can also customize data types, supporting efficient data processing and query operations;

[0072] The database module includes multi-data source switching, data storage and efficient query, data consistency and transaction management, data security and permission control, flexible data model support, monitoring and optimization tools;

[0073] The cache module is used to accelerate data access through cache strategy, reduce database load, and improve system performance. The cache module adopts a Redis-based cache mechanism. The cache module includes high-performance data access, flexible data cache strategy, support for multiple cache types, distributed cache support, automatic expiration and invalidation mechanism, data consistency guarantee, high availability and fault tolerance mechanism, cache penetration and breakthrough protection, integrated cache warm-up mechanism.

[0074] The authentication module is responsible for user identity verification and permission management, supports the creation of role-permission-resource granular fine-grained permission allocation model, and dynamically adjusts permissions through API interface to ensure system security and user legitimacy. The authentication module includes support for multiple authentication methods, single sign-on (SSO), role-based access control (RBAC), multi-factor authentication (MFA), fine-grained permission control, dynamic and short-term tokens, token verification and encryption, flexible permission policy, integration with third-party authentication systems, and abnormal behavior monitoring and alarm.

[0075] The security module provides a protection mechanism for the system, including firewall, encryption and security access control, to protect data and network security. At the same time, the security module has a built-in security authentication mechanism and security-related functions that are triggered when an interface is accessed, including API permission code authentication, data encryption and decryption, and security access control. The security module includes data encryption and privacy protection, identity authentication and access control, malware and virus protection, access audit and risk assessment.

[0076] The log module is used to record system running status and operation logs for later monitoring and problem troubleshooting. The log module includes comprehensive log recording, efficient log storage and management, real-time log monitoring and analysis, multi-level log level management, log security and compliance, and multi-terminal support for logs.

[0077] The interface document module is used to generate and manage API interface documents online, facilitating collaboration and interface use for developers and teams. The interface document module includes clear interface description, standardized parameter explanation, detailed error code explanation, automatic and real-time update, interface permission and security description, interactive document and test function, easy browsing and searching, document support for multiple formats, and integration and collaboration.

[0078] The code generator module can automatically generate a specific type of code, reduce the workload of the developer, and improve the development efficiency; the code generator module includes template-driven code generation, automatic generation of CRUD operations, API generation, front-end code generation, configuration file generation, custom code generation function, code template and plug-in support, code quality and style check.

[0079] The dynamic table editor module is used for creating, editing and managing dynamic tables, supporting table creation, data addition, deletion, modification and query, and formula calculation, improving data processing efficiency, and at the same time being able to preview the editing effect in real time, optimizing the user operation experience, and supporting multi-terminal adaptation.

[0080] The front-end module is used for providing front-end development framework and components, supporting modular front-end page construction, including modularity and reusability, responsiveness and adaptability, user interaction and experience (UX / UI), data binding and dynamic rendering, testability, module dependency and package management, security, maintainability and code specification, integration with backend interface, continuous integration and deployment.

[0081] The business middle platform framework includes a special equipment management module, a sensor integration module, a process module and an inspection and detection record report management module.

[0082] The special equipment management module is used for comprehensively and systematically managing special equipment, including equipment account management, equipment point inspection management, equipment maintenance management, equipment use management, equipment scrap management, equipment query and statistical management.

[0083] The sensor integration module includes Internet of Things sensor binding, which integrates device basic information and operation monitoring information.

[0084] The process module provides a template type configuration tool for different types of business processing, and users can customize the workflow according to their business needs; the process module provides a template type configuration tool, visual workflow design, flexible rule engine and process automation to help enterprises quickly build, adjust and optimize business processes. Compared with traditional manual operation or fixed process design method, it has higher efficiency, flexibility and scalability, can effectively reduce development cost, improve business processing speed and enhance the adaptability of the system.

[0085] The inspection and detection record report management module can dynamically generate inspection records and inspection report preparation templates according to the table editor, and can also select report template according to equipment type and inspection type to prepare, check, review, approve and print and archive.

[0086] The test detection record report management module ensures efficient, standardized and safe record and report management in the test work through functions such as dynamic template generation, built-in approval process and permission control, electronic signature and historical version tracking. Compared with the traditional way, it provides higher flexibility, automation and compliance, greatly improves work efficiency, reduces human errors, has stronger adaptability and expandability, and can meet different business needs.

[0087] Embodiment two

[0088] As Figure 2 shown, a development method for quickly forming special equipment management capability is provided. Taking the development system in the method applied to Figure 1 as an example, the method includes the following steps:

[0089] S1: First, set the system startup parameters through a graphical interface or a configuration file, such as whether to enable on-demand loading mode, the startup order of each function module, the dependency relationship between modules, etc.

[0090] S2: After the system reads the configuration, the management module is started, that is, initialization operations are performed according to the configuration content. In the early stage of system startup, the management module will automatically complete system-level initialization, such as log component warm-up, basic connection pool construction, cache directory preparation, etc., while judging whether the current configuration enables the on-demand loading mode.

[0091] For example, when the system needs to respond quickly to online, and some modules are user operation triggered functions, the on-demand loading strategy can be enabled.

[0092] S3: Load the core modules, such as the authentication module, the configuration module, the basic service module, etc., and the remaining function modules are dynamically loaded by the module loading module when they are actually called. The core module will detect module call requests in real time and perform lazy loading operations to ensure on-demand allocation of system resources and reduce startup time.

[0093] For example, in some scenarios, the system needs to load all business function modules at a time when starting. At this time, the system automatically and sequentially loads all modules according to the preset module dependency chain to ensure that each module can provide services as soon as it is started. For example, the authentication module depends on the configuration module, so the configuration module will be loaded first. The log module, the cache module, the interface document module, etc. are initialized and activated in turn according to the dependency chain.

[0094] S4: After the system is successfully started and stably runs, if the user wants to shut down the system, issue a system stop instruction through the control panel or operation and maintenance instruction. For example, in some production environments, to ensure data consistency and the integrity of resource release, the system can be set to enable the "graceful shutdown" strategy.

[0095] S5: After receiving the instruction, the system stop management module will terminate the unfinished business task in advance, then write the data in the cache to the database, close the connection pool resource, release the thread resource, etc. For example, during use, the system runs multiple modules, including a log processing module, a core business module, and an interface module. After receiving the stop instruction, the system stop management module will send a stop signal to each module one by one to ensure that each module completes the cleaning and recycling process before the system is completely closed.

[0096] To prevent system resource residue or leakage, the resource recycling module will be started during system shutdown, performing operations such as memory release, temporary file cleaning, thread pool destruction, etc. For example, in a high-concurrency scenario, a system starts multiple threads to handle tasks. When the system is shut down, the resource recycling module will uniformly destroy the thread pool to avoid system abnormalities caused by leftover threads.

[0097] As shown in Figure 3 The database module includes a multi-data source switching module, a master-slave heterogeneous processing module, a dynamic permission management module, and a data change record. The specific work of the database module includes the following steps:

[0098] S1: Through the multi-data source switching module, the target data source is directly selected in the visual interface, and the connection pool is established, which facilitates the user to access the database under different systems (such as A system, B system) during operation and maintenance;

[0099] S2: According to the actual configuration, automatically reconnect the corresponding database, which greatly improves the convenience and efficiency of environment switching.

[0100] S3: When performing data updates, the user calls the master-slave heterogeneous processing module, which automatically identifies the type of the currently operated database (such as MySQL, Dream, God Thunder, etc.), and adjusts the execution logic according to the built-in strategy, so that developers do not need to understand the syntax differences of each database to complete common data operation tasks, thereby significantly reducing the technical threshold.

[0101] S4: The dynamic permission management module automatically identifies the role of the user after login, and generates an adaptive permission statement based on the role.

[0102] For example, ordinary users can only query their own data, while administrators can perform global operations. For permission control with business logic requirements, developers can also customize permission expressions by configuring rules to achieve flexible permission isolation. At the same time, for tables containing sensitive fields such as user identity and approval records, the module also encrypts and displays or restricts access to them through field-level control logic to ensure data security from the source. In some systems that do not require permission control but have high requirements for data integrity, the illegal statement interception module can be used to prevent users from submitting SQL statements with abnormal structure or that may cause data damage. For example, when detecting that the execution statement contains prohibited keywords, missing conditional statements, or data tables beyond the permission range, the system will automatically intercept the execution process of the SQL and return detailed prompt information, thereby effectively ensuring system stability.

[0103] S5: In scenarios where enterprises need to record data changes comprehensively, the data change recording module can automatically record data insertion, update, and deletion operations in real time, and save information such as execution user, timestamp, data content before and after changes. These records can be used for auditing, responsibility tracking, and data recovery scenarios, effectively improving data management capabilities.

[0104] As shown in Figure 4 , the cache module includes a cache strategy setting module, a cache level design module, and a cache update strategy management module. The cache strategy setting module is used to reduce the performance loss caused by frequent database access,

[0105] The cache level design module is used to configure a multi-level cache solution. Through a simplified configuration process, this module achieves rapid deployment of complex cache structures.

[0106] The specific work of the cache module includes the following steps:

[0107] S1: The administrator configures the business data types that need to be cached, such as user information, configuration items, or interface response content, in the background through the cache strategy setting module. Only the data category to be cached, the cache duration of the data item, and the memory occupation limit need to be set. The system will automatically apply these strategies without the need for manual coding of any cache processing code, making it suitable for daily maintenance operations by technical personnel.

[0108] S2: Set the first-level cache as an in-memory cache to quickly respond to hot data requests. Then, further enable the second-level cache (such as Redis) to store relatively cold data, and set up a master-slave data synchronization mechanism to ensure the consistency of cached data.

[0109] S3: For frequently updated content and large access volume, the administrator selects the "refresh cache by listening to database events" mode in the cache update strategy management module; in some report statistical data that do not require real-time performance, the user selects the "refresh cache by timing task" function, and in the scenario where the business is frequently changed in a short time but does not want to frequently refresh the cache, the user configures the "delayed cache update" function, sets the delay to 3 minutes after the data is changed to execute cache update, and effectively balances the relationship between performance and accuracy;

[0110] The "refresh cache by listening to database events" mode listens to operation events such as insertion, update, and deletion through database triggers or middleware, and automatically refreshes the cache content once data changes are detected, thereby ensuring real-time updating of the data displayed on the front end without manual intervention.

[0111] For example, the "refresh cache by timing task" function can be set to automatically refresh the cache every 10 minutes, which reduces the pressure on the database while ensuring relatively real-time data.

[0112] The cache module system uses the above-mentioned implementation mode to combine the use of cache strategy setting, hierarchical cache design, and flexible update mechanism, which is not only suitable for various high-concurrency and high-access systems, but also reduces the use threshold of the cache mechanism.

[0113] As shown in Figure 5 To facilitate understanding of the application mode of the authentication module for enhancing system security, the following describes the use effect and advantages of the present application in different business scenarios through multiple actual use examples.

[0114] In actual operation, the administrator selects the module through dynamic Client authentication, and quickly configures the authentication mode used for user login in the background interface. If it is configured as general login, the administrator can select account / password / sms verification as the basic authentication mode; and for sensitive management, MFA (multi-factor authentication) verification can be enabled to further improve the system security level. In an online service supporting multi-terminal access, the system can automatically identify the type of device currently used by the user through the multi-terminal device differentiation module. The system can automatically apply differentiated security policies according to the identification result,

[0115] For example, the expiration time is extended on mobile devices, while a more convenient SSO (Single Sign-On) method is allowed on enterprise intranet desktop devices, thus providing a better user experience while ensuring security. For example, in a large SaaS platform, in order to facilitate administrators to flexibly manage the permissions of subordinate employees, a permission management module can be used to enable role-based access control (RBAC). Administrators can bind roles such as "management role", "audit role" or "normal role" with respective required function modules on the platform interface, avoiding repeated configuration and improving management efficiency.

[0116] If there are more detailed permission requirements, attribute-based access control (ABAC) can be enabled, and the system will automatically determine whether to allow the request according to attributes such as user access time, IP range or department. The authentication module system has three functions of flexible selection of authentication methods, device differentiation identification and fine-grained permission configuration, which improves the security and adaptability of the system.

[0117] As shown in Figure 6 , the security module includes an authentication module, an API permission code authentication module, a flow limiting module, a desensitization module, a data encryption and decryption module, a monitoring module and a log module.

[0118] In a platform that provides interface services to the outside, developers can select appropriate authentication methods through the authentication module in the background management interface. For example, ordinary user login can use account / password verification; while administrator accounts enable MFA (Multi-Factor Authentication) or SSO (Single Sign-On) to enhance account security. The entire configuration process does not require code writing, and can be completed by enabling the corresponding options in the configuration panel. The system exposes multiple API interfaces to the outside, and developers set access permission codes for these interfaces through the API permission code authentication module. For example, a certain internal query interface is only authorized for a specific service to access, and the administrator can assign an independent permission code to the service. Requests without the correct permission code will be automatically rejected by the system, thus effectively preventing unauthorized access.

[0119] In terms of traffic management, the flow limiting module is widely used in high-concurrency scenarios. Administrators configure the upper limit of access frequency for each interface, for example, limiting an API interface to be accessed at most 50 times per second, and the excess part of the request will be automatically discarded or delayed in response, thus effectively preventing system crashes caused by malicious requests or traffic surges.

[0120] When handling user sensitive data, data protection is achieved through the desensitization module. For example, when exporting a user information table, the module will automatically desensitize fields such as ID card number, mobile phone number, email address, etc., and only part of the information will be retained for display, thus protecting user privacy.

[0121] In terms of data security transmission, the data encryption and decryption module provides both symmetric encryption and asymmetric encryption. Users can choose the appropriate encryption method according to the business type, encrypt sensitive data before transmission, and decrypt it at the receiving end through the key to ensure the confidentiality and security of data during transmission and storage.

[0122] During system operation, the log module serves as the recording hub of the entire security system, storing all key operation and event logs. For example, it records user login, interface invocation, configuration changes, and other operation traces, facilitating post-event traceability analysis and supporting audit requirements.

[0123] As shown in Figure 7 , the log module includes a log management initialization module, a log output target configuration module, and a message listening processing module.

[0124] In actual environment operation, administrators can set up logs through the log management initialization module. Developers only need to select the required log level (such as error, warning, information, etc.) in a simple interface and specify the log location. This operation does not require understanding of complex log management systems. Users can complete log record initialization by selecting the appropriate configuration, reducing the technical threshold.

[0125] In terms of log output target configuration module, the system provides flexible options. For example, administrators can output logs to log files and avoid performance problems caused by large log files by setting log rotation strategies. This module also supports multi-level configuration of log files, allowing different levels of log information to be stored separately, thus achieving precise log management.

[0126] For scenarios where logs are stored in databases, users can further set dynamic table names and table splitting strategies to optimize log data storage efficiency. In addition, users can set operation types, business identifiers, and other information according to actual needs to facilitate subsequent efficient query and analysis.

[0127] The message listening processing module is used to monitor key events in the system. Administrators set up message listeners to capture and record events. For example, when the system encounters errors or critical operations, the listener will capture and record the event in the log system in a timely manner. This not only helps administrators discover potential problems in real time, but also provides valuable reference data for subsequent troubleshooting and analysis.

[0128] As shown in Figure 8As shown, the API documentation module, through the collaborative work of multiple modules, enables developers to automatically generate and maintain API documentation. For example, while coding, developers can use the code comment parsing module to add standardized comments to each function and method. These comments not only describe the function's functionality and parameters but also extract information such as the function name, parameter names and their types, and return value through a predefined format. In this way, developers do not need to manually write documentation but can directly generate API documentation from comments, ensuring the accuracy and consistency of the documentation.

[0129] In terms of in-depth analysis of input and output parameters, the API documentation module automatically generates detailed parameter descriptions and return result descriptions by analyzing the function's input parameters and output results. For example, the system can identify the data structure, format, and meaning of parameters through static analysis or actual calls, thereby generating comprehensive API documentation to help developers better understand how to use the API.

[0130] The API documentation generation module automatically combines the outputs from the code comment parsing module and the input / output parameter deep analysis module to generate standard-formatted API documentation according to preset templates and specifications. These documents can be output in various formats, such as Markdown, HTML, or PDF, to facilitate use in different development environments. The documentation standardization module ensures that the generated API documentation adheres to a unified format standard, thereby improving communication efficiency among team members and enabling external developers to quickly understand and use the API. This allows different developers to follow the same documentation format, improving the readability and standardization of the documentation.

[0131] For example, developers can choose to use authentication methods such as OAuth or JWT to ensure the security and compliance of API documentation. The online debugging module allows developers to debug the API directly in their browser without installing additional software.

[0132] Developers can use this module to quickly send requests, view responses, and adjust request parameters in real time as needed, effectively improving development efficiency. Finally, the automatic deployment and synchronization module ensures the automated deployment and updating of API documentation. Each time code is changed, the documentation is automatically updated to ensure consistency between the documentation content and the actual code.

[0133] like Figure 9 As shown, the code generator module includes a configuration setting module, a table name and path setting module, a data parsing module, a front-end component building module, and a code generation and management module.

[0134] Code generation provides an efficient and flexible code generation and management solution through the cooperation of multiple modules, helping developers quickly generate code that meets their needs in different business scenarios. The following is an application example of each module to illustrate the actual use of the invention.

[0135] The configuration setting module provides developers with multiple configuration options, allowing them to flexibly adjust various parameters of the generated code according to business needs. By configuring the data source (DataSourceConfig), developers can specify the connection information to the database, ensuring that the generated code can correctly connect to the specified data source. Global configuration (GlobalConfig) allows developers to set global parameters of the project, such as project name, version information, etc. Package configuration (PackageConfig) enables developers to specify the package path after code generation, while template configuration (TemplateConfig) allows developers to select or customize the code generation template according to specific needs. Injection configuration (InjectionConfig) and Vue configuration (VueConfig) provide flexible settings for injecting components and front-end Vue configuration in the generated code, ensuring that the generated code can meet the needs of front-end and back-end development.

[0136] In the table name and path setting module, developers can customize the database table name to be generated according to business needs, and set dynamic modules and paths to ensure that the generated files meet the requirements of specific directory structures. Developers select which database tables need to participate in the code generation function, and flexibly define the storage path of the generated code, ensuring that the file directory structure is clear and orderly.

[0137] The data parsing module is responsible for in-depth analysis of different types of data fields, such as primary keys, dictionary types, date types, and numerical types. This module analyzes the structure of the input data and ensures that the generated code accurately reflects the characteristics of the original data structure. Through comprehensive analysis of data fields, the generated code can handle various complex data types, ensuring the efficiency and maintainability of the code.

[0138] The front-end component construction module integrates a variety of commonly used front-end UI components, including lists, text boxes, date selectors, drop-down menus, and tree controls. Developers can combine different components according to actual needs through simple configuration to quickly build front-end interfaces that meet business logic. For example, developers can generate a form page containing a list and a drop-down menu through this module, directly displaying and interacting with data on the front end.

[0139] The code generation and management module provides a "one-click generation" function, which can generate complete front-end and back-end code based on the previously configured parameters. At the same time, it supports previewing the generated code, and developers can view the code content before downloading to ensure that the generated code meets the requirements. The generated code can be packaged as a compressed package for easy downloading and further development by developers.

[0140] As shown in Figure 10 , the front-end module aims to help developers quickly implement cross-platform front-end application development by integrating multi-terminal support and compatibility support modules. Through a graphical operation interface, developers can reduce technical requirements and achieve rapid component and module development. For example, the multi-terminal support module provides a intuitive platform for users to achieve mobile and web application development through simple drag-and-drop and configuration operations. Developers do not need to write complex code, but only need to select the required support terminal in the graphical interface and configure it according to actual needs to achieve application display on different terminals. Whether developing mobile applications or web applications, users can easily achieve cross-platform adaptation and development through this module.

[0141] The compatibility support module is designed to adapt to different mobile devices and web browsers. Developers can select target devices or browsers through a graphical interface, and the system will automatically generate corresponding compatibility adjustment schemes. For example, developers can choose to optimize for browsers or adapt to different sizes of mobile phone screens. This module ensures that applications can run stably in various device and browser environments and provides targeted optimization solutions.

[0142] The component construction module integrates a variety of commonly used front-end components, including but not limited to list components, form components, menu components, tree components, date components, modal components, state components, and layout components 1, etc. Developers can choose the required components from the preset component library through an intuitive graphical interface and complete component property settings through simple configuration. For example, developers can select a form component and configure field types, validation rules, and other properties in the graphical interface. This module also allows users to customize component styles and functions to meet specific needs, ensuring the individuality and efficiency of the front-end interface.

[0143] The module construction module provides more complex functions, such as the drawing module, the desensitization module, and the dynamic permission module. Developers can directly operate these modules in the graphical interface to quickly build complex business logic. For example, users can use the drawing module to draw flowcharts or architecture diagrams.

[0144] As shown in Figure 11 , the special equipment management module designs and implements six functional modules covering the entire process from equipment accounting to scrapping.

[0145] In the implementation process, first, a unified equipment information registration template is established through equipment account management, supporting two-dimensional code binding, batch import, and state tracking, to realize the standardization and traceability of basic data.

[0146] Equipment point patrol management ensures the coverage of daily operation inspection by configuring inspection plans, task assignment, and code scanning check-in mechanisms, and automatically triggers maintenance processes when abnormalities are found.

[0147] Equipment maintenance management supports the closed-loop processing of planned and temporary maintenance tasks, including task assignment, process recording, completion archiving, and other functions, and synchronizes maintenance history to the equipment archives.

[0148] For equipment usage management, the system provides functions such as application review, usage record archiving, and conflict checking, effectively controlling the flow of equipment.

[0149] For the end of the equipment life cycle, equipment scrap management supports user application submission and multi-level approval processes, and automatically updates the equipment status and archives related materials after disposal is completed.

[0150] To support daily management and efficient decision-making, the system also provides equipment query and statistical management, allowing equipment information to be retrieved based on multiple conditions, supporting the export of custom reports, and visually displaying key indicators such as maintenance frequency and fault distribution through charts, helping managers to monitor equipment status and operational risks in real time.

[0151] As shown in Figure 12 The sensor integration module supports the connection of multiple types of sensors (such as temperature, pressure, liquid level, vibration, etc.) during implementation, and realizes rapid integration through standardized interfaces. Implementers can select appropriate sensors based on equipment type, and after deployment, the system will automatically perform real-time data collection and processing. Collected data will be analyzed by cloud analysis models, and users can view real-time graphs, equipment operating status, and abnormal data fluctuations in the system.

[0152] When parameter limits or trend abnormalities are detected, the system will automatically trigger an early warning mechanism, pushing alarm information to the terminals of management personnel (such as mobile phones, computers, and boards), avoiding possible omissions or delays in manual inspection. At the same time, the system also supports remote monitoring and control, allowing users to remotely view equipment status, adjust parameters, or start and stop operations through the platform, improving emergency response efficiency. All collected data will be automatically archived by equipment, and users can view historical records and generate data reports through the query function, achieving problem tracing and trend analysis.

[0153] As shown in Figure 13As shown, the process module provides complete low-code process building capabilities, including template library management, process designer, rule engine configuration, data model binding, permission and role configuration, and testing and simulator, supporting the rapid construction of business processes and logical rules.

[0154] Developers can select existing templates from the workflow template library or create new workflows, and use the WYSIWYG workflow designer to arrange nodes, including common actions such as form filling, approval workflow, conditional judgment, and automatic notification. Each workflow node can be flexibly configured with trigger conditions, processing logic, and associated actions.

[0155] At the rule level, the system provides a visual rule engine configuration interface, supporting the setting of rules for field validation, calculation logic, branch judgment, and other functions. Rules can be defined independently and bound to specific process nodes through the interface, or they can be dynamically loaded and used by developers via API.

[0156] In terms of data model binding, the process supports mapping with existing business models (such as devices, users, work orders, etc.). Developers only need to configure field mapping relationships during design to achieve real-time interaction and linkage between process data and system master data.

[0157] At the access control layer, the system integrates role and permission configuration functions, supporting the setting of process access permissions, node processing permissions and field visibility range for users with different roles, ensuring data security and clear responsibilities.

[0158] Once built, developers can use the built-in simulator tool to test the process, covering multiple dimensions such as input, rule matching, and abnormal paths, to ensure that the process logic is correct before going live.

[0159] like Figure 14 As shown, when the inspection and testing record report management module is working, developers can complete the entire process from template configuration to report archiving according to the functional divisions and workflow paths provided by the system, ensuring that the system has efficient, compliant, and scalable report management capabilities. The specific work steps are as follows:

[0160] S1: In the "Dynamic Template Configuration Center," developers need to select the equipment type and inspection item type based on the actual business scenario and configure the applicable record and report templates. This module supports field-level customization, logical rule validation, and style layout design, and has template version management capabilities to ensure the traceability of historical templates and meet the differentiated needs of different scenarios. For typical business processes, the system also supports automatically generating templates through case management rules, further reducing manual intervention.

[0161] S2: After the template configuration is completed, the user selects the template through the "record / report preparation process" and enters the relevant inspection data. The system supports batch data import, automatic export of basic information, field linkage, and other functions, and performs automatic verification logic in the save link to avoid missing or incorrect filling, ensuring data accuracy. In actual application, this process has functions such as draft saving, data recovery, and field permission control, facilitating data isolation and security protection between different operating roles in the enterprise.

[0162] S3: After completing the data reporting, the system will automatically enter the "multi-level approval process engine". The developer configures the approval rules of each link through the process designer, supports multi-node configuration such as editing, auditing, approval, and signing, and can set condition jumping, node backtracking, comment explanation, and electronic signature operations. Each node can be bound to a specific role permission to ensure that only authorized personnel can handle related approval tasks, ensuring process compliance and security.

[0163] S4: After the process approval is completed, the system automatically enters the "report output and archiving management" stage. The developer configures the report output format (such as PDF, Word), realizes one-key generation and printing, and supports connection with the archiving system to uniformly archive and store information such as report content, version, signature information, and associated data, supporting historical record query, version comparison, and audit traceability. The entire archiving process is automatically completed without human intervention, ensuring that the report materials are complete, legal, and traceable.

[0164] In the above-mentioned development system and method for quickly forming a special equipment management capability, a functional modular design is adopted to improve project construction and deployment efficiency, modularize core functions, and allow users to flexibly combine and expand according to needs. This design simplifies the system building process and improves development and deployment efficiency. With the support of Spring Boot, the system realizes efficient classification mapping and function integration, improves code reuse rate, standardizes code structure, reduces communication and maintenance costs, and can dynamically configure components to meet changes in enterprise needs, improving software production efficiency and quality. It solves some common difficulties and repetitive work in the development process of special equipment industry software, improves development efficiency and system stability. Each module has clear function division and mutual cooperation to ensure efficient, stable, and safe operation of the system. Each module is supported by automated, standardized, and efficient tools to reduce repetitive work in development, improve development efficiency, reduce error rate, and ensure system stability and security. At the same time, modular design greatly optimizes the software development life cycle, improves team collaboration, and enables enterprises to quickly respond to market demand and maintain competitiveness.

[0165] Any technical features in the above embodiments can be combined, and for the sake of brevity, not all possible combinations are described, however, any combination of the technical features is considered to be within the scope of the present specification.

Claims

1. A development system for rapidly developing special equipment management capabilities, characterized by, The technical middle platform framework includes a start management module, a database module, a cache module, an authentication module, a security module, and a log module. The business middle platform framework includes a special equipment management module, a sensor integration module, a process module, and an inspection and detection record report management module. The start management module is responsible for the start, stop, and configuration management of the system. The database module provides data storage, management, and access services, including an entity designer and an attribute designer. The working steps of the database module are as follows: S1: Through the multi-data source switching module, the target data source is selected directly in the visual interface, and the connection pool is established. S2: According to the actual configuration, the corresponding database is automatically reconnected. S3: When performing data updates, the user calls the master-slave heterogeneous processing module, which automatically identifies the type of the currently operated database. S4: The dynamic permission management module automatically identifies the role of the user after login and generates an adapted permission statement based on the role. S5: In scenarios where the enterprise needs to record data changes comprehensively, the data change record module can automatically record the insertion, update, and deletion operations of data in real time. The cache module is used to accelerate data access and reduce database load through caching strategies. The authentication module is responsible for user identity verification and permission management, supports the creation of a role-permission-resource granular and fine-grained permission allocation model, and dynamically adjusts permissions through API interfaces. The security module provides a protection mechanism for the system, including a firewall, encryption, and security access control, to ensure data and network security. The log module is used to record system operation status and operation logs. The special equipment management module is used to comprehensively and systematically manage special equipment. The sensor integration module includes Internet of Things sensor binding, which integrates device basic information and operation monitoring information. The process module provides a template-style configuration tool for different types of business processing, and users can customize the workflow according to their business needs. The inspection and detection record report management module can dynamically generate inspection records and report preparation templates based on the table editor. The working steps of the inspection and detection record report management module are as follows: 1): In the "dynamic template configuration center", the developer needs to select the device type and inspection item type according to the actual business scenario, and configure the applicable record and report template. 2): After the template configuration is completed, the user selects the template through the "record / report preparation process" and enters the relevant inspection data. 3): After completing the data reporting, the system will automatically enter the "multi-level approval process engine", and the developer configures the approval rules of each link through the process designer. 4): After the process approval is completed, the system automatically enters the "report output and archiving management" stage, and the developer configures the report output format. The technical middle platform framework also includes an interface document module, a code generator module, a dynamic table editor module, and a front-end module. The interface document module is used to generate and manage API interface documents online. The code generator module can automatically generate a specific type of code, reducing the workload of the developer; The dynamic table editor module is used for creating, editing and managing dynamic tables, supporting table creation, data addition, deletion, modification and query, and formula calculation; The front-end module is used for providing a front-end development framework and components, supporting modular front-end page construction.

2. The development system for quickly forming a special device management capability according to claim 1, wherein The cache module adopts a Redis-based cache mechanism, and includes high-performance data access, flexible data cache strategy, support for multiple cache types, and distributed cache support.

3. The development system for quickly forming a special device management capability according to claim 1, wherein The code generator module includes a configuration setting module, a table name and path setting module, a data parsing module, a front-end component construction module, and a code generation and management module.

4. The development system for quickly forming a special device management capability according to claim 3, wherein The configuration setting module provides multiple configuration options for developers, who can flexibly adjust various parameters of the generated code according to business requirements; The table name and path setting module can customize the database table name for which the code is to be generated according to business requirements, and set dynamic modules and paths, so that the generated files can meet the requirements of a specific directory structure; The data parsing module is responsible for deep parsing of different types of data fields; The front-end component construction module integrates a variety of commonly used front-end UI components, and developers can quickly build front-end interfaces that meet business logic by simply configuring and combining different components according to actual needs; The code generation and management module provides a "one-click generation" function, which can generate complete front-end and back-end code at one time according to the parameters configured in the front.

5. The development system for quickly forming a special device management capability according to claim 1, wherein The special equipment management module includes equipment account management, equipment point patrol management, equipment maintenance management, equipment use management, equipment scrap management, and equipment query and statistical management.

6. The development system for quickly forming a special device management capability according to claim 1, wherein The working steps of the cache module are as follows: S1: The administrator sets the business data type that needs to be cached in the background through the cache strategy setting module; S2: Set the first-level cache as a memory cache for quick response to hot data requests, then further enable the second-level cache for storing relatively cold data; S3: For frequently updated and high-traffic content, the administrator selects the "listen to database event to refresh cache" method in the cache update strategy management module, for some report statistical data that do not require real-time, the user selects the "timed task to refresh cache" function, and in the case where the business frequently changes in a short time but does not want to frequently refresh the cache, the user configures the "delayed cache update" function.

7. A method for developing a system for rapidly forming a special device management capability based on any one of claims 1 to 6, characterized by, The method steps are as follows: S1: First, set the system startup parameters through a graphical interface or a configuration file; S2: After the system reads the configuration, the management module is started, that is, the initialization operation is performed according to the configuration content; S3: Load the core module, and the remaining functional modules are dynamically loaded by the module loading module when they are actually called; S4: After the system is successfully started and runs stably, if the user wants to shut down the system, issue a system stop instruction through the control panel or operation and maintenance instruction; S5: After the system stop management module receives the instruction, it will first terminate the unfinished business tasks, then write the data in the cache to the database, and close the connection pool resources.

Images