Development system and method for quickly forming special equipment management capability

Abstract

The invention discloses a development system and method for rapidly forming special equipment management capability, and the system comprises a technical platform framework and a business platform framework, the technical platform framework comprises a starting management module, a database module, a cache module, an authentication module, a security module, and a log module; and the service platform framework comprises a special equipment management module. The invention belongs to the technical field of special equipment management, and aims to solve the problems that in the prior art, a design mode is depended, the workload of developers needs to be increased, and codes between products are lack of universality and reusability, so that the development efficiency is reduced. The method has the technical effects that core functions are modularized, so that a user can flexibly combine and expand according to 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 the system stability are improved.

Description

Technical Field

[0001] The present application belongs to the technical field of special equipment management, and specifically relates to a development system and method for rapidly forming special equipment management capabilities. Background Art

[0002] Special equipment is an essential 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 crucial. With the acceleration of industrial modernization and the improvement of the safety production regulatory system, the safety supervision of special equipment has become a key area of concern for both the government and society.

[0003] However, in the current project development process in this field, there are some urgent problems that need to be solved, which have an adverse impact on the overall development efficiency and delivery speed. Specifically, the existing method architecture relies on design patterns, which requires developers to increase their workload, resulting in too low efficiency in building projects and development deployment. When customer needs change rapidly or the technology stack spans a large area, the functional division of labor model is often difficult to change quickly, making it difficult to ensure the delivery speed. With the increase in the business areas of user units or inspection and monitoring agencies, business logic has become more complex. In this case, if the codes between products lack commonality and reusability, it will lead to a lot of duplication of work, thereby reducing development efficiency and increasing costs. Summary of the Invention

[0004] This application provides a development system and method for quickly forming special equipment management capabilities, aiming to solve the problem that existing technologies rely on design patterns, require developers to increase their workload, resulting in low efficiency in project construction and development deployment, and difficulty in ensuring delivery speed. At the same time, the lack of commonality and reusability of codes between products will lead to a large amount of duplication of work, thereby reducing development efficiency.

[0005] First, a development system for rapidly developing special equipment management capabilities includes a technical mid-stage framework and a business mid-stage framework. The technical mid-stage framework includes a startup management module, a database module, a cache module, an authentication module, a security module, and a log module.

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

[0007] The startup management module is responsible for the startup, stop and configuration management of the system;

[0008] The database module provides data storage, management and access services, and contains entity designers and attribute designers;

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

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

[0011] The security module provides system protection mechanisms, including firewalls, encryption and secure access control, to ensure data and network security;

[0012] The log module is used to record the system operation status and operation log;

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

[0014] The sensor integration module contains IoT sensor binding, which integrates basic device information and operation monitoring information;

[0015] The process module provides template-based configuration tools for different types of business processes, allowing users to customize workflows based on their business needs;

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

[0017] Furthermore, 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;

[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 to reduce the workload of developers;

[0020] The dynamic table editor module is used to create, edit and manage dynamic tables, and supports 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, and supports modular front-end page construction.

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

[0023] Furthermore, 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] Furthermore, 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;

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

[0026] The data parsing 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. Developers can combine different components through simple configuration according to actual needs to quickly build a front-end interface that conforms to business logic;

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

[0029] Furthermore, the special equipment management module includes equipment inventory management, equipment inspection management, equipment maintenance management, equipment use management, equipment scrapping management, and equipment query and statistics management.

[0030] Furthermore, the working steps of the inspection and testing record report management module are as follows:

[0031] 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;

[0032] S2: After the template is configured, the user selects the template through the "Record / Report Preparation Process" and enters the relevant inspection data;

[0033] S3: After completing the data entry, the system will automatically enter the "multi-level approval process engine" and the developer will configure the approval rules for 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] Furthermore, the working steps of the database module are as follows:

[0036] S1: Use the multi-data source switching module to directly select the target data source in the visual interface and establish a connection pool;

[0037] S2: Automatically reconnect to the corresponding database according to the actual configuration;

[0038] S3: When executing 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 user's role after logging in and generates an adaptive permission statement based on the role;

[0040] S5: In scenarios where enterprises need to comprehensively record data change operations, the data change recording module can automatically record data insertion, update, and deletion operations in real time.

[0041] Furthermore, the cache module operates as follows:

[0042] S1: The administrator uses the cache policy setting module to quickly configure the business data types that need to be cached in the background;

[0043] S2: Set the first-level cache as a memory cache to quickly respond to hot data requests. Then, the user further enables the second-level cache to store relatively cold data.

[0044] S3: For content that is frequently updated and has a large number of visits, the administrator selects the "Listen to database events to refresh the cache" method in the cache update policy management module. For some report statistics that do not require high real-time performance, the user selects the "Scheduled task to refresh the cache" function. In scenarios where the business frequently changes in a short period of time but frequent cache refreshes are not desired, the user configures the "Delayed cache update" function.

[0045] Second, a method for rapidly developing special equipment management capabilities is provided, comprising the following steps:

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

[0047] S2: After the system reads the configuration, it starts the management module and performs initialization operations 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 they are actually called;

[0049] S4: After the system is successfully started and running stably, if the user wants to shut down the system, he / she can issue a system stop command through the control panel or operation and maintenance instructions;

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

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

[0052] This application is based on further analysis and research of existing technical problems. It improves the efficiency of project construction and deployment by adopting functional modular design, modularizes the core functions, and allows users to flexibly combine and expand according to their needs. This design simplifies the system construction process and improves development and deployment efficiency. With the support of Spring Boot, the system achieves efficient classification mapping and functional integration, while improving code reuse, standardizing code structure, reducing communication and maintenance costs, and can dynamically configure components to meet changes in enterprise needs and improve software production efficiency and quality. It solves some common difficulties and repetitive work in the software development process of the special equipment industry, and improves development efficiency and system stability. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] Figure 1 An architectural diagram of a development system and method for rapidly developing special equipment management capabilities, provided in some embodiments of the present application;

[0054] Figure 2 An architectural diagram of a startup management module for a development system and method for rapidly developing special equipment management capabilities, as provided in some embodiments of the present application;

[0055] Figure 3 An architectural diagram of a database module for a development system and method for rapidly developing special equipment management capabilities, as provided in some embodiments of the present application;

[0056] Figure 4 An architectural diagram of a cache module for a development system and method for rapidly developing special equipment management capabilities, as provided in some embodiments of the present application;

[0057] Figure 5 An architectural diagram of an authentication module for a development system and method for rapidly developing special equipment management capabilities, as provided in some embodiments of the present application;

[0058] Figure 6 An architectural diagram of a security module for a development system and method for rapidly developing special equipment management capabilities, as provided in some embodiments of the present application;

[0059] Figure 7 An architectural diagram of a log module for a development system and method for rapidly developing special equipment management capabilities, as provided in some embodiments of the present application;

[0060] Figure 8 An architectural diagram of an interface document module for a development system and method for rapidly developing special equipment management capabilities, as provided in some embodiments of the present application;

[0061] Figure 9An architectural diagram of a code generator module for a development system and method for rapidly developing special equipment management capabilities, as provided in some embodiments of the present application;

[0062] Figure 10 An architectural diagram of a front-end module of a development system and method for rapidly developing special equipment management capabilities, as provided in some embodiments of the present application;

[0063] Figure 11 An architectural diagram of a special equipment management module for a development system and method for rapidly developing special equipment management capabilities, as provided in some embodiments of the present application;

[0064] Figure 12 An architectural diagram of a sensor integration module for a development system and method for rapidly developing special equipment management capabilities, as provided in some embodiments of the present application;

[0065] Figure 13 An architectural diagram of a process module for a development system and method for rapidly developing special equipment management capabilities, as provided in some embodiments of the present application;

[0066] Figure 14 An architectural diagram of the inspection and testing record and report management module of a development system and method for rapidly developing special equipment management capabilities provided in some embodiments of the present application. DETAILED DESCRIPTION

[0067] In order to make the purpose, technical solutions and advantages of this application more clear, this application is further described in detail below with reference to the accompanying drawings and embodiments.

[0068] Example 1

[0069] like Figure 1 As shown, a development system for quickly forming special equipment management capabilities is provided, including a technical middle platform framework and a business middle platform framework. The technical middle platform framework includes 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 to ensure the smooth operation of the system; the startup management module is configured to include automated startup and stop management, flexible configuration management, support for multi-environment deployment, scalability and customizability, and an integrated operation interface.

[0071] The database module provides data storage, management and access services, including entity designers and attribute designers. Users can freely define field attributes. In addition to conventional data types, they can also customize data types to support 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, reduce database load, and improve system performance through cache strategies. The cache module adopts a Redis-based cache mechanism; the cache module includes high-performance data access, flexible data cache strategies, support for multiple cache types, distributed cache support, automatic expiration and invalidation mechanisms, data consistency assurance, high availability and fault tolerance mechanisms, cache penetration and breakdown protection, and an integrated cache preheating mechanism;

[0074] The authentication module is responsible for user identity authentication and permission management, supports the creation of a granular and fine-grained permission allocation model based on roles, permissions, and resources, and dynamically adjusts permissions through the 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 tokens and short-term tokens, token verification and encryption, flexible permission strategies, integration with third-party authentication systems, and abnormal behavior monitoring and alarms.

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

[0076] The logging module is used to record system operating status and operation logs, facilitating subsequent monitoring and troubleshooting. It includes comprehensive logging, efficient log storage and management, real-time log monitoring and analysis, multi-level log level management, log security and compliance, and multi-terminal support.

[0077] The interface documentation module is used to generate and manage API interface documents online, facilitating collaboration and interface usage between developers and teams. The interface documentation module includes clear interface descriptions, standardized parameter descriptions, detailed error code descriptions, automation and real-time updates, interface permissions and security descriptions, interactive documentation and testing functions, easy browsing and search, document support for multiple formats, and integration and collaboration.

[0078] The code generator module can automatically generate specific types of code, reducing the workload of developers and improving 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 functions, code templates and plug-in support, and code quality and style checking.

[0079] The dynamic table editor module is used to create, edit and manage dynamic tables. It supports table creation, data addition, deletion, modification and query, and formula calculation, improving data processing efficiency. At the same time, it can preview the editing effect in real time, optimize the user operation experience, and support multi-terminal adaptation.

[0080] The front-end module is used to provide a 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 standards, integration with back-end interfaces, and 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 testing record report management module.

[0082] The special equipment management module is used to comprehensively and systematically manage special equipment, including equipment ledger management, equipment inspection management, equipment maintenance management, equipment use management, equipment scrapping management, equipment query and statistical management.

[0083] The sensor integration module contains IoT sensor binding, which integrates basic device information and operation monitoring information;

[0084] The process module provides template-based configuration tools for different types of business processes, allowing users to customize workflows based on their business needs. By offering templated configuration tools, visual workflow design, a flexible rules engine, and process automation, the process module helps companies quickly build, adjust, and optimize business processes. Compared to traditional manual operations or fixed process design methods, it offers greater efficiency, flexibility, and scalability, effectively reducing development costs, increasing business processing speed, and enhancing system adaptability.

[0085] The inspection and testing record report management module can dynamically generate inspection record and inspection report compilation templates based on the table editor, and can also select report templates for compilation, verification, review, approval, and printing and archiving according to equipment type and inspection type.

[0086] The Inspection and Testing Record and Report Management module ensures efficient, standardized, and secure record and report management during inspection work through dynamic template generation, built-in approval processes and permission control, electronic signatures, and historical version traceability. Compared to traditional methods, it offers greater flexibility, automation, and compliance, significantly improving work efficiency and reducing human error. It also offers greater adaptability and scalability to meet diverse business needs.

[0087] Example 2

[0088] like Figure 2 As shown in the figure, a development method for quickly forming special equipment management capabilities is provided, which can be applied to Figure 1 The development system in the example is used to illustrate the following steps:

[0089] S1: First, set the system startup parameters through the graphical interface or configuration file, such as whether to enable the on-demand loading mode, the startup order of each functional module, and the dependencies between modules;

[0090] S2: After the system reads the configuration, the startup management module performs initialization operations based on the configuration. During the initial system startup, the startup management module automatically completes system-level initialization, such as preheating the log component, building the basic connection pool, and preparing the cache directory. It also determines whether the current configuration enables on-demand loading mode.

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

[0092] S3: Load core modules, such as authentication module, configuration module, basic service module, etc. The remaining functional 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 once during startup. In this case, the system automatically loads all modules in order according to the pre-set module dependency chain, ensuring that each module is ready to provide services immediately upon startup. For example, if the authentication module depends on the configuration module, the configuration module will be loaded first. The logging module, cache module, and interface documentation module are also initialized and activated sequentially according to the dependency chain.

[0094] S4: After the system is successfully started and running stably, if the user wishes to shut down the system, they can issue a system shutdown command through the control panel or operation and maintenance instructions. For example, in a production environment, to ensure data consistency and complete resource release, the system can be set to enable a "graceful shutdown" policy.

[0095] S5: Upon receiving the command, the system stop management module will first terminate unfinished business tasks, then write cached data to the database, close connection pool resources, and release thread resources. For example, during use, the system runs multiple modules, including the log processing module, core business module, and interface module. Upon receiving the stop command, the system stop management module will send a stop signal to each module one by one, ensuring that each module completes the cleanup and recovery process before completely shutting down the system.

[0096] To prevent residual or leaked system resources, the resource recovery module is activated during system shutdown to perform operations such as memory release, temporary file cleanup, and thread pool destruction. For example, if a system starts multiple threads processing tasks in a high-concurrency scenario, the resource recovery module will destroy the thread pools uniformly during system shutdown to prevent system anomalies caused by residual threads.

[0097] like Figure 3 As shown, the database module includes a multi-data source switching module, a master-slave heterogeneous processing module, a dynamic rights 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 can be directly selected in the visual interface to establish a connection pool, which is convenient for users to access databases in different systems (such as system A and system B) during operation and maintenance.

[0099] S2: Automatically reconnects to the corresponding database based on the actual configuration, greatly improving the convenience and efficiency of environment switching.

[0100] S3: When executing data updates, users call the master-slave heterogeneous processing module. The master-slave heterogeneous processing module automatically identifies the type of database currently being operated (such as MySQL, DAMO, Shentong, etc.) and adjusts the execution logic according to the built-in strategy, so that developers can complete common data operation tasks without having to understand the syntax differences of each database, thereby significantly reducing the technical threshold.

[0101] S4: The dynamic permission management module automatically identifies the user's role after logging in 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 the display 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 structures or that may cause data damage. For example, when it is detected that the execution statement contains prohibited keywords, missing conditional statements, or a data table that exceeds 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: For scenarios where enterprises need to comprehensively record data changes, the Data Change Recording module automatically records data insert, update, and delete operations in real time, saving information such as the executing user, timestamp, and data content before and after the change. These records can be used for auditing, accountability tracking, and data recovery, effectively improving data management capabilities.

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

[0105] The cache hierarchy design module is used to configure multi-level cache solutions. This module enables rapid deployment of complex cache structures through a simplified configuration process.

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

[0107] S1: Administrators use the cache policy setting module to quickly configure the types of business data that need to be cached, such as user information, configuration items, or interface response content. Simply select the cached data category and set the cache duration and memory usage limit for the data item. The system automatically applies these policies, eliminating the need to manually write any cache processing code. This makes it suitable for technical personnel's daily operations and maintenance.

[0108] S2: Set up a first-level cache as a memory cache to quickly respond to hot data requests; then, the user further enables a second-level cache (such as Redis) to store relatively cold data, and sets up a master-slave data synchronization mechanism to ensure the continuous consistency of the cached data.

[0109] S3: For content that is frequently updated and has high traffic, administrators can select "Listen for database events to refresh the cache" in the cache update policy management module. For report statistics that don't require high real-time performance, users can select "Scheduled task to refresh the cache." In scenarios where business frequently changes within a short period of time but frequent cache refreshes are undesirable, users can configure "Delayed cache update" to delay cache updates for three minutes after data changes, effectively balancing performance and accuracy.

[0110] The "listen for database events to refresh the cache" method uses database triggers or middleware to listen for insert, update, delete, and other operation events. Once a data change is detected, the cache content is automatically refreshed, ensuring that the data displayed on the front end is updated in real time without manual intervention.

[0111] For example, the "scheduled task refresh cache" function can be set to automatically refresh the cache every 10 minutes, allowing the system to reduce the pressure on the database while ensuring that the data is relatively real-time.

[0112] Through the above implementation method, the cache module system combines 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 lowers the threshold for using the cache mechanism.

[0113] like Figure 5 As shown, in order to facilitate understanding of the application of the authentication module for enhancing system security described in the present invention, the following describes the use effects and advantages of the present invention in different business scenarios through multiple actual usage examples.

[0114] In actual operation, the administrator selects the module through the dynamic Client authentication method and quickly configures the authentication method used for user login in the background interface. If configured as a universal login, the administrator can select account / password / SMS verification as the basic authentication method; and for sensitive management, MFA (multi-factor authentication) verification can be enabled to further improve the system security level. In an online service that supports 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 based on the identification results.

[0115] For example, extending the expiration time on mobile devices and enabling a more convenient SSO (single sign-on) method on corporate intranet desktop devices ensures security while providing a better user experience. Another example is that on a large SaaS platform, to facilitate administrators to flexibly manage the permissions of subordinate employees, a permissions management module can be used to enable role-based access control (RBAC). Administrators can bind roles such as "management role," "audit role," or "general role" to their required functional modules on the platform interface, avoiding duplication of configuration and improving management efficiency.

[0116] If more granular permission requirements exist, attribute-based access control (ABAC) can be enabled. The system automatically determines whether to grant access based on user attributes such as access time, IP range, or department. The authentication module system enhances system security and adaptability through flexible authentication method selection, device identification, and granular permission configuration.

[0117] like Figure 6 As shown, the security module includes an authentication module, an API permission code authentication module, a current limiting module, a desensitizing 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 world, developers can select the appropriate authentication method through the authentication module in the background management interface. For example, ordinary users can use account / password verification to log in; while administrator accounts enable MFA (multi-factor authentication) or SSO (single sign-on) to enhance account security. The entire configuration process does not require writing code, and can be completed by simply enabling the corresponding options in the configuration panel. The system opens multiple API interfaces to the outside world, and developers set access permission codes for these interfaces through the API permission code authentication module. For example, an internal query interface only authorizes access to specific services. The administrator can assign an independent permission code to the service. Requests that do not provide the correct permission code will be automatically rejected by the system, thereby effectively preventing unauthorized access.

[0119] In terms of traffic management, the current limiting module is widely used in high-concurrency scenarios. Administrators configure the access frequency limit for each interface, for example, limiting an API interface to a maximum of 50 accesses per second. Requests exceeding this limit will be automatically discarded or delayed by the system, effectively preventing system crashes caused by malicious requests or traffic surges.

[0120] When processing sensitive user data, the desensitization module implements data protection. For example, when exporting a user information table, the module automatically desensitizes fields such as ID number, mobile phone number, and email address, retaining only a portion of the information for display, thereby protecting user privacy.

[0121] For secure data transmission, the data encryption and decryption module provides both symmetric and asymmetric encryption. Users can select the appropriate encryption method based on their business type. Sensitive data is encrypted before transmission, and the receiving end decrypts it using a key, ensuring the confidentiality and security of the data during transmission and storage.

[0122] During system operation, the logging module serves as the central recording hub for the entire security system, storing all key operations and event logs. For example, these logs include user logins, interface calls, configuration changes, and other operational traces. This facilitates subsequent analysis of security incidents and supports audit requirements.

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

[0124] In real-world environments, administrators can configure log settings through the Log Management Initialization module. Developers simply select the desired log level (e.g., error, warning, information) and specify the log location within a simple interface. This eliminates the need to understand complex log management systems. Users can initialize logging simply by selecting the configuration that suits their needs, lowering the technical barrier to entry.

[0125] The system offers flexible options for configuring log output destinations. For example, administrators can output logs to log files and set log rotation policies to avoid performance issues caused by oversized log files. The module also supports multi-level configuration of log files, allowing different levels of log information to be stored separately, enabling precise log management.

[0126] For scenarios where logs are stored in a database, users can further configure dynamic table names and table partitioning strategies to optimize log data storage efficiency. Furthermore, users can also set information such as operation type and business identifier based on actual needs to facilitate efficient subsequent query and analysis.

[0127] The message monitoring module monitors critical system events. Administrators can set up message listeners to capture and log these events. For example, when a system error or critical operation occurs, the listener captures the event and logs it to the log system. This not only helps administrators identify potential issues in real time but also provides valuable reference data for subsequent troubleshooting and analysis.

[0128] like Figure 8As shown, the interface documentation module enables developers to automatically generate and maintain interface documentation through the collaborative work of multiple modules. For example, while coding, developers can use the code comment parsing module to add standard 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 using a predefined format. This eliminates the need for developers to manually write documentation; instead, interface documentation is generated directly from comments, ensuring accuracy and consistency.

[0129] For in-depth analysis of input and output parameters, the interface 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 parameter's data structure, format, and meaning through static analysis or actual calls, thereby generating detailed interface documentation to help developers better understand how to use the interface.

[0130] The API interface document generation module automatically combines the output of the code comment parsing module and the input and output parameter depth parsing module to generate interface documents in a standard format according to preset templates and specifications. These documents can be output in multiple formats such as Markdown, HTML, or PDF according to user needs, making them convenient for use in different development environments. The document standardization module ensures that the generated interface documents follow a unified format standard, thereby improving communication efficiency between team members and enabling external developers to quickly understand and use the API. This allows different developers to follow the same document format, improving the readability and standardization of the document.

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

[0132] This module allows developers to quickly send requests, view responses, and adjust request parameters in real time as needed, effectively improving development efficiency. Finally, the automatic publishing and synchronization module ensures automated deployment and updates of interface documentation. With each code change, the documentation is automatically updated to ensure consistency between the document 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 construction module and a code generation and management module.

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

[0135] The configuration setting module provides developers with multiple configuration options, allowing developers to flexibly adjust the 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 to ensure that the generated code can correctly connect to the specified data source. The global configuration (GlobalConfig) allows developers to set global parameters for the project, such as project name, version information, etc. The package configuration (PackageConfig) enables developers to specify the package path after code generation, while the template configuration (TemplateConfig) allows developers to select or customize the template for generated code according to specific needs. The injection configuration (InjectionConfig) and Vue configuration (VueConfig) provide flexible settings for the injected components and front-end Vue configuration in the generated code to ensure that the generated code can meet the front-end and back-end development needs.

[0136] In the Table Name and Path Settings module, developers can customize the database table names for code generation based on business needs and set dynamic modules and paths to ensure that the generated files meet specific directory structure requirements. Developers can select which database tables to include in the code generation function and flexibly define the storage path for the generated code, ensuring a clear and orderly file directory structure.

[0137] The data parsing module is responsible for deeply analyzing different types of data fields, such as primary keys, dictionary types, date types, and numeric 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. This comprehensive analysis of data fields enables the generated code to handle a variety of complex data types, ensuring efficient and maintainable code.

[0138] The front-end component building module integrates a variety of commonly used front-end UI components, including lists, text boxes, date pickers, drop-down menus, and tree controls. Developers can quickly build a front-end interface that conforms to business logic by combining different components through simple configuration based on actual needs. For example, developers can use this module to generate a form page with a list and drop-down menu, allowing data display and interactive operations directly on the front-end.

[0139] The code generation and management module provides a "one-click generation" feature that generates complete front-end and back-end code in one go based on previously configured parameters. It also supports previewing the generated code, allowing developers to review the code content before downloading and ensure that the generated code meets their requirements. The generated code can be packaged into a compressed package, making it easy for developers to download and further develop locally.

[0140] like Figure 10 As shown, the front-end module is designed to help developers quickly implement cross-platform front-end application development by integrating multi-terminal support and compatibility support modules. Through the graphical operation interface, developers can reduce technical requirements and achieve rapid component and module development. For example, the multi-terminal support module provides developers with an intuitive platform, allowing users to implement mobile and web application development through simple drag and drop and configuration operations. Developers do not need to write complex code, just select the required support terminal in the graphical interface and configure it according to actual needs to realize the display of the application 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 adapts apps to different mobile devices and web browsers. Developers select target devices or browsers through a graphical interface, and the system automatically generates corresponding compatibility adjustments. For example, developers can choose to optimize for a specific browser or adapt to different mobile screen sizes. This module ensures that apps run stably across a variety of devices and browser environments, and provides targeted optimization solutions.

[0142] The component building 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. Developers can use an intuitive graphical interface to select the desired components from a pre-set component library and set component properties through simple configuration. For example, developers can select a form component and configure properties such as the field type and validation rules for the form items within the graphical interface. The module also allows users to customize component styles and functionality to meet specific needs, ensuring a personalized and efficient front-end interface.

[0143] The module building 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 a graphical interface to quickly build complex business logic. For example, users can use the drawing module to create flowcharts or architecture diagrams.

[0144] like Figure 11 As shown, the special equipment management module has designed and implemented six functional modules, covering the entire process from equipment accounting to scrapping.

[0145] During the implementation process, we first establish a unified equipment information registration template through equipment ledger management, support QR code binding, batch import and status tracking, and realize the standardization and traceability of basic data.

[0146] Equipment inspection management ensures the inspection coverage of daily equipment operations by configuring inspection plans, task dispatching, and QR code sign-in mechanisms, and automatically triggers maintenance processes when abnormalities are found.

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

[0148] In terms of equipment usage management, the system provides functions such as application approval, usage record archiving, and conflict verification to effectively control the equipment circulation process.

[0149] At the end of the equipment's life cycle, equipment scrapping management supports users to submit applications and go through a multi-level approval process. After disposal is completed, the equipment status is automatically updated and related materials are archived.

[0150] To support daily management and efficient decision-making, the system also provides equipment query and statistical management. It can retrieve equipment information according to multi-dimensional conditions, support the export of customized reports, and intuitively display key indicators such as maintenance frequency and fault distribution in the form of charts, helping managers to understand equipment status and operational risks in real time.

[0151] like Figure 12 As shown in the figure, the sensor integration module supports the integration of various sensor types (such as temperature, pressure, liquid level, and vibration) and enables rapid integration through standardized interfaces. Implementers can select the appropriate sensor based on the device type. Once deployed, the system automatically collects and processes real-time data. The collected data is analyzed using cloud-based analytical models, and users can view real-time graphs, device operating status, and abnormal data fluctuations within the system.

[0152] When a parameter exceeds a limit or an abnormal trend is detected, the system automatically triggers an early warning mechanism and sends an alert to the manager's terminal (such as a mobile phone, computer, or dashboard), preventing possible omissions or delays during manual inspections. The system also supports remote monitoring and control, allowing users to remotely view device status, adjust parameters, and start and stop devices, improving emergency response efficiency. All collected data is automatically archived by device, and users can use the query function to view historical records and generate data reports, enabling problem tracing and trend analysis.

[0153] like 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 process template library or create new processes. Using the WYSIWYG process designer, they can orchestrate nodes, including common actions such as form filling, approval flow, conditional judgment, and automatic notifications. Each process 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 that supports setting rules such as field validation, calculation logic, and branch judgment. Rules can be independently defined and then bound to specific process nodes through the interface, or developers can dynamically load and use them through the API.

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

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

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

[0159] like Figure 14 As shown, when the inspection and testing record report management module is working, developers can complete the whole process construction from template configuration to report archiving according to the functional division and process path 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 select the equipment type and inspection item type based on the specific business scenario and configure applicable record and report templates. This module supports field-level customization, logic rule validation, and style layout design. It also features template version management, ensuring traceability of historical templates and meeting the differentiated needs of different scenarios. For typical business processes, the system also supports automatic template generation based on case management rules, further reducing manual intervention.

[0161] S2: After the template is configured, users select the template through the "Record / Report Preparation Process" and enter relevant inspection data. The system supports batch data import, automatic import of basic information, field linkage, and other functions. Automatic verification logic is also implemented during the save process to prevent missing or incorrect entries and ensure data accuracy. In practice, this process includes features such as draft saving, data recovery, and field permission control, facilitating data isolation and security protection between different operational roles.

[0162] S3: After completing the data entry, the system automatically enters the "Multi-Level Approval Process Engine." Developers use the process designer to configure approval rules for each stage. This supports multiple node configurations, including editing, review, approval, and signing. Conditional jumps, node rollbacks, annotations, and electronic signatures can also be set. Each node can be bound to specific role permissions, ensuring only authorized personnel can handle relevant approval tasks, ensuring process compliance and security.

[0163] S4: Once the process is approved, the system automatically enters the "Report Output and Archiving Management" phase. Developers configure the report output format (e.g., PDF, Word), enabling one-click generation and printing. The system also connects to the archiving system, centrally archiving and storing report content, version, signature information, and associated data. This allows for historical record query, version comparison, and audit traceability. The entire archiving process is automated, requiring no human intervention, ensuring that report data is complete, legal, and traceable.

[0164] The aforementioned development system and method for rapidly developing special equipment management capabilities utilizes a functional modular design to improve project construction and deployment efficiency. Core functions are modularized, allowing users to flexibly combine and expand them based on their needs. This design simplifies the system setup process and enhances development and deployment efficiency. Leveraging Spring Boot, the system achieves efficient classification mapping and functional integration, while also increasing code reuse, standardizing code structure, and reducing communication and maintenance costs. It also enables dynamic component configuration to meet changing enterprise needs, improving software production efficiency and quality. This addresses common difficulties and repetitive work in software development for the special equipment industry, enhancing development efficiency and system stability. Each module has a clear functional division and collaborates with each other to ensure efficient, stable, and secure system operation. Through automation, standardization, and efficient tool support, each module reduces duplication during development, improves development efficiency, reduces error rates, and ensures system stability and security. Furthermore, the modular design significantly optimizes the software development lifecycle and enhances team collaboration, enabling enterprises to quickly respond to market demands and maintain competitiveness.

[0165] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

Claims

1. A development system for rapidly developing special equipment management capabilities, characterized by: It includes a technical middle platform framework and a business middle platform framework. The technical middle platform framework includes a startup 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 testing record report management module; The startup management module is responsible for the startup, stop and configuration management of the system; The database module provides data storage, management and access services, and contains entity designers and attribute designers; The cache module is used to accelerate data access and reduce database load through cache strategies; The authentication module is responsible for user identity authentication and permission management, supports the creation of a granular and fine-grained permission allocation model of role-permission-resource, and dynamically adjusts permissions through the API interface; The security module provides system protection mechanisms, including firewalls, encryption and secure access control, to ensure data and network security; The log module is used to record the system operation status and operation log; The special equipment management module is used to manage special equipment comprehensively and systematically; The sensor integration module contains IoT sensor binding, which integrates basic device information and operation monitoring information; The process module provides template-based configuration tools for different types of business processes, allowing users to customize workflows based on their business needs; The inspection and testing record and report management module can dynamically generate inspection records and inspection report compilation templates based on the table editor.

2. A development system for rapidly forming special equipment management capabilities according to claim 1, characterized in that: 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 specific types of code to reduce the workload of developers; The dynamic table editor module is used to create, edit and manage dynamic tables, and supports table creation, data addition, deletion, modification and query, and formula calculation; The front-end module is used to provide a front-end development framework and components, and supports modular front-end page construction.

3. A development system for rapidly developing special equipment management capabilities according to claim 1, characterized in that: The cache module adopts a Redis-based cache mechanism, which includes high-performance data access, flexible data caching strategies, support for multiple cache types, and distributed cache support.

4. A development system for rapidly forming special equipment management capabilities according to claim 2, characterized in that: 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.

5. A development system for rapidly forming special equipment management capabilities according to claim 4, characterized in that: 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; The table name and path setting module can customize the database table name to be generated according to business needs, and set the dynamic module and path so that the generated file can meet the requirements of a specific directory structure; The data parsing module is responsible for in-depth analysis of different types of data fields; The front-end component building module integrates a variety of commonly used front-end UI components. Developers can combine different components through simple configuration according to actual needs to quickly build a front-end interface that conforms to business logic; The code generation and management module provides a "one-click generation" function, which can generate complete front-end and back-end codes at one time based on the previously configured parameters.

6. A development system for rapidly developing special equipment management capabilities according to claim 1, characterized in that: The special equipment management module includes equipment ledger management, equipment inspection management, equipment maintenance management, equipment use management, equipment scrapping management, and equipment query and statistics management.

7. A development system for rapidly developing special equipment management capabilities according to claim 1, characterized in that: The working steps of the inspection and testing record report management module are as follows: S1: In the Dynamic Template Configuration Center, developers need to select the device type and inspection item type based on the actual business scenario, and configure the applicable record and report templates. S2: After the template is configured, the user selects the template through the "Record / Report Preparation Process" and enters the relevant inspection data; S3: After completing the data entry, the system will automatically enter the "Multi-level Approval Process Engine" and the developer can configure the approval rules for each link through the process designer; 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.

8. A development system for rapidly developing special equipment management capabilities according to claim 1, characterized in that: The working steps of the database module are as follows: S1: Use the multi-data source switching module to directly select the target data source in the visual interface and establish a connection pool; S2: Automatically reconnect to the corresponding database according to the actual configuration; S3: When executing 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; S4: The dynamic permission management module automatically identifies the user's role after logging in and generates an adaptive permission statement based on the role; S5: In scenarios where enterprises need to comprehensively record data change operations, the data change recording module can automatically record data insertion, update, and deletion operations in real time.

9. A development system for rapidly developing special equipment management capabilities according to claim 1, characterized in that: The working steps of the cache module are as follows: S1: The administrator uses the cache policy setting module to quickly configure the business data types that need to be cached in the background; S2: Set the first-level cache as a memory cache to quickly respond to hot data requests. Then, the user further enables the second-level cache to store relatively cold data. S3: For content that is frequently updated and has a high traffic volume, the administrator can select the "Listen to database events to refresh cache" method in the cache update policy management module. For report statistics that do not require high real-time performance, the user can select the "Scheduled task to refresh cache" function. In scenarios where business changes frequently within a short period of time but frequent cache refreshes are undesirable, the user can configure the "Delayed cache update" function.

10. A method for rapidly developing special equipment management capabilities based on any one of claims 1 to 9, characterized in that: The method steps are as follows: S1: First, set the system startup parameters through the graphical interface or configuration file; S2: After the system reads the configuration, it starts the management module and performs initialization operations 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 running stably, if the user wants to shut down the system, he / she can issue a system stop command through the control panel or operation and maintenance instructions; S5: After receiving the instruction, the system stop management module will first terminate the unfinished business tasks, then write the data in the cache to the database and close the connection pool resources.

Images