Electronic form digital management system based on waste incineration power generation management application

Abstract

The invention relates to the technical field of waste incineration, in particular to an electronic form digital management system based on waste incineration power generation management application. The system comprises a system architecture and an electronic form system, the system architecture comprises a server, a database and clients, MVVM architectures are embedded in the clients, the database is deployed on the server, the server establishes a server data interaction link with the multiple clients through the database, and client data interaction links are established among the multiple clients; the electronic form system comprises a server layer, a data layer, a service layer, an interaction layer, a business layer, a user interaction interface and an interface. The independent electronic form system is developed and used for being connected with related form services, service digitization and electronization are achieved, and the whole-process execution efficiency of forms commonly used in the work ticket, operation ticket and other garbage power generation incineration management processes is improved.

Description

Technical Field

[0001] This invention relates to the field of waste incineration technology, and in particular to an electronic form digital management system based on waste incineration power generation management applications. Background Technology

[0002] The electronic work order system commonly used in the waste-to-energy incineration industry is limited in functionality and efficiency, and does not support expansion or user-defined functions. Complete ERP systems are expensive and difficult to deploy, and currently, most similar technologies rely on web servers to achieve similar functions, leading to the following technical shortcomings: all data processing depends on the web server, resulting in poor interactivity; the native system does not support cross-platform operation; business integration is low, and business expansion is not supported; and it does not support interaction with large language models. Summary of the Invention

[0003] This invention provides an electronic form digital management system based on waste incineration power generation management applications, aiming to solve the technical problems existing in the current electronic work ticket system.

[0004] This invention provides an electronic form digital management system based on waste incineration power generation management application, including a system architecture and an electronic form system. The system architecture includes a server, a database, and a client. The client has an embedded MVVM architecture. The database is deployed on the server. The server establishes server data interaction links with multiple clients through the database, and multiple clients establish client data interaction links with each other. The electronic form system includes: The server layer includes local servers and remote servers; The data layer is used for data retrieval between different layers, as well as for data filtering, encoding optimization, verification, and storage. The service layer is used to integrate business rules and operational processes related to electronic forms into callable services. The interaction layer includes workflow management: used to integrate relevant data from the service layer and data layer, and output structured and graphical data based on user-defined conditions; form business assistance: an auxiliary module for creating form business, providing functions such as component node management, data statistics, and data export by calling server and local resources; and a global window manager: a function to integrate form data with the same ID in multi-window applications and update the data within a single window. The business layer is an abstraction layer used to manage electronic form transactions. User interaction interface, transforming electronic form business into an operable interface; An interface for accessing large language models.

[0005] As a further improvement of the present invention, the business layer includes an electronic form defect registration management module, the workflow of which is as follows: A defect report form is created and reviewed by the shift leader and specialist in turn. If the review fails, the form process ends. If the review passes, the maintenance team receives and processes the form. During the review stage, the equipment specialty or maintenance specialty on the form can be changed as needed. Finally, the processing result and acceptance result are submitted, and the form process ends. When there are related defect orders, create a related defect order for the unresolved defect order and execute the above defect form process. After the process is completed, update the unresolved defect order.

[0006] As a further improvement of the present invention, the business layer includes a work order management module, the workflow of which is as follows: Create work order forms, including creating new ones directly, or / and creating them through favorites, or / and creating them by applying historical work orders, or / and creating them by reusing invalid work order numbers, or / and creating them through a standard work order library; The Operations Department reviews the application; if approved, it is sent to the Equipment Department; if not approved, it returns to the process of creating a work order. The Equipment Department reviews the application; if approved, the server assigns a work order number; if not approved, it returns to the process of creating a work order. After assigning the work order number, the work order is printed and tracked, thus ending the work order form process.

[0007] As a further improvement of the present invention, the business layer includes an operation ticket management module, the workflow of which is as follows: Create an operation ticket form, store, print, and execute the operation ticket form. After execution, update the operation ticket content, create a snapshot, and store it. Repeat the process until the entire operation ticket form has been executed.

[0008] As a further improvement of the present invention, the business layer includes a periodic work management module, the workflow of which is as follows: Get the current time and shift, create a task list and execute it, and then end the operation for that shift after reporting the execution result; switch to the next shift and repeat the above operation.

[0009] As a further improvement of the present invention, the data layer includes: Data access interface: Provides a data access interface for data access between different levels; Data verification: Rapid verification of massive amounts of data is achieved through an established independent data verification mechanism; Data filtering: Using a localized data filtering mechanism, data from the server is obtained for the entire range selected by the user. The data filter is applied after the data is obtained, and works with the "data seamless refresh" framework to achieve background data updates. Data encoding and optimization: Long data is encoded using algorithms such as Base64, MD5, SHA128, and SHA256, read locally, dynamically parsed according to business needs, and form data is cached; Data storage: Used for local data caching.

[0010] As a further improvement of the present invention, the service layer includes: Log service: Collects log data from distributed systems and applications through various log collection methods to provide developers with a basis for bug fixing; Automatic software updates: By pulling the software version configuration file from the server, an independent component is used to achieve online automatic software updates, keeping the software always up-to-date; UDP communication service: Local area network communication via the UDP protocol, including UDP broadcasting within the local area network; responsible for queued parsing and processing of received messages; Authentication: Performs current operation permission determination and performs form operability status generic matching; Automatic tagging service: Automatically colors-codes the features matched by each piece of data on the form management page; IDE Fast Input Engine: By simulating the IDE's fast input engine, it allows users to quickly find matching data or fields by continuously or intermittently inputting Pinyin, Chinese characters, or the first letter of Pinyin. Hash algorithm assistance: Used for one-way SHA512 encryption of user data, and at the same time, it encodes multi-form workflow data using MD5 and other methods for fast comparison and database hash verification; Real-time preview engine: By introducing an HTML-based rich text editing display mode, the form is rendered and previewed in real time based on the form information constructed by the user on the user interface; Workflow model: used to build workflows for each form; Database connection management service: used to implement automatic configuration of database connection pool; Notification service: Used to convert messages from various threads and notify operators via pop-up windows; Global hotkey service: used to adapt to global keyboard shortcuts and monitor barcode scanner scan data; ReactiveUI Message Bus Service: Used for communication between multiple Models and ViewModels components within the client; System Status Response Service: Used to detect system status, automatically release software resources based on the operating system's idle state, and automatically refresh data when the system status recovers; Snowflake ID generation and parsing service: The Snowflake algorithm incorporates unique form identifiers and unique computer identifiers; during parsing, it distinguishes the form type by extracting the unique form identifier and automatically executes the next execution plan.

[0011] As a further improvement of the present invention, the user interface includes: WinformUI: Building user interfaces for Windows; HTML: Primarily used for real-time preview engine rendering of form pages; AvaloniaUI: Build user interfaces for platforms such as Windows, Linux, Android, and macOS.

[0012] As a further improvement of the present invention, when multiple clients interact, the client acting as the sender performs the following process: When a user sends a message on the client, the client extracts and parses the ID, updates and queries the data in the server's database, and verifies the data to be updated. If the data is new, the cache is updated directly and a notification is sent. If the data is already existing, the data is merged, new data is created, and a notification is sent.

[0013] As a further improvement of the present invention, when multiple clients interact, the client acting as the receiver performs the following process: The client receives a message and adds it to a thread queue. The UI thread processes the message and validates the message data. If the validation passes, the thread terminates; otherwise, the data is retrieved again. Simultaneously, after processing the message, the client extracts and parses the ID, updates and queries the data in the server's database, and checks the message data. If the data is new, the cache is updated directly, the data is synchronized, and the UI is modified. If the data already exists, the data is merged, new data is created, synchronized, and the UI is modified.

[0014] The beneficial effects of this invention are: It develops an independent electronic form system for connecting with relevant form-related business processes, realizing the digitization and electronicization of business operations, and improving the overall efficiency of the execution of work orders, operation tickets, and other forms commonly used in the management of waste-to-energy incineration; the form business module uses an independent open framework, which can be extended to other types of online form management businesses according to business management needs, solving the problem of business functionality not being expandable; and it builds a native cross-platform application, achieving cross-platform operation without relying on any third-party components or middleware. Attached Figure Description

[0015] Figure 1 This is a system architecture diagram of the electronic form digital management system of the present invention; Figure 2 This is a flowchart illustrating the functionality of the client as the sender in this invention. Figure 3 This is a flowchart illustrating the function of the client as the receiver in this invention. Figure 4 This is a diagram of the MVVM structure in this invention; Figure 5 This is a distributed architecture diagram under the MVVM architecture in this invention; Figure 6 This is a layered diagram of the software architecture of the electronic form system in this invention; Figure 7 This is a flowchart of the defect registration and management module in this invention; Figure 8 This is a flowchart illustrating the workflow of the defect registration management module in this invention under form association conditions; Figure 9 This is a flowchart of the work order management module in this invention; Figure 10 This is a flowchart of the operation ticket management module in this invention; Figure 11 This is a flowchart of the periodic work management module in this invention. Detailed Implementation

[0016] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments.

[0017] like Figure 1 and Figure 5 As shown, the present invention provides an electronic form digital management system based on waste incineration power generation management applications, including a system architecture and an electronic form system. The system architecture includes a server, a database, and a client. The client has an embedded MVVM architecture, and the database is deployed on the server. The server establishes server data interaction links with multiple clients through the database, and multiple clients establish client data interaction links with each other.

[0018] The development framework of this system uses WinForm UI and Avalonia UI to build the user interface. Avalonia UI adopts the MVVM architecture, namely M (Model)-V (View)-VM (View Model), and improves overall performance by introducing the Reactive UI framework and implementing reactive programming. The backend uses the .NET Core framework to achieve cross-platform capabilities.

[0019] Among them, .NET Core (.NET 8.0): .NET Core is a free, open-source, hosted computer software framework for Windows, Linux, and macOS. It is the first official version developed by Microsoft and is an application development framework with cross-platform capabilities.

[0020] WinForm: Based on the .NET WinForm desktop application development environment, it is a tool built using the C# language to improve software development efficiency. By providing predefined modules and components, it reduces repetitive coding work, thereby accelerating project development. The WinForm software development framework typically adopts a three-tier business logic architecture as its basic development platform. The three tiers are: Form, BLL, and DAL.

[0021] AvaloniaUI: Create cross-platform applications using .NET. It uses a rendering engine to draw UI controls, ensuring consistent look and behavior across different platforms such as Windows, macOS, Linux, Android, iOS, and WebAssembly.

[0022] This system adopts a combined C / S + distributed architecture. While supporting local or cloud deployment, it fully leverages the advantages of the C / S architecture to enable independent data processing on each node, thereby improving overall system performance. The EFS system architecture is designed based on the core principle of solving complex problems with the simplest architecture. Detailed functionalities are further refined by introducing other secondary architectures.

[0023] The servers include: web server, FTP server, and database, which can be deployed locally or remotely.

[0024] Database: PostgreSQL relational database (supports deployment on Linux, Windows and other platforms), supports deployment on local or remote servers.

[0025] Client program: The client program has the ability to communicate with each other and has the ability to communicate directly with the server.

[0026] C / S architecture: Client program: The client program has the ability to communicate with each other and has the ability to communicate directly with the server.

[0027] C / S distributed architecture: C / S architecture refers to the server C (Client) and the client S (Server).

[0028] Distributed architecture: Distributed architecture refers to a network where each client node has independent data processing capabilities, capable of performing local application operations or global application operations via the network.

[0029] The distributed architecture functionality includes: distributed architecture functionality to enable data interaction between clients; data sending and receiving functionality based on ReactiveUI.MessageBus (message bus service) and UDP communication protocol; millisecond-level response for data reading in conjunction with database caching mechanism; implementation of sender role functionality; and implementation of receiver role functionality.

[0030] like Figure 2 As shown, when multiple clients interact, the sending client performs the following process: the user performs a sending operation on the client, the client extracts and parses the ID, updates and queries the data through the server's database, and checks the data to be updated. If the data is new, the cache is updated directly and a notification is sent. If the data is already existing, the data is merged, new data is created, and a notification is sent.

[0031] like Figure 3 As shown, when multiple clients interact, the receiving client executes the following process: The client receives a message, adds the received message to a thread queue, the UI thread processes the information, and validates the message data. If the validation passes, the thread terminates; if the validation fails, the data is retrieved again. Simultaneously, after the UI thread processes the information, the client extracts the ID and parses it, updates and queries the data through the server's database, and checks the message data. If the validation indicates new message data, the cache is directly updated, the data is synchronized, and the changes are made to the UI. If the validation indicates existing data, the data is merged, new data is created, and the data is synchronized and changed to the UI.

[0032] like Figure 4 As shown, the client-side embedded MVVM architecture of this invention combines the advantages of MVC (Model-View-ViewModel) and MVP (Model-View-Presenter), separating interface logic from business logic and achieving automatic synchronization of the view and model through data binding and event-driven methods. Figure 5 As shown, each client embedded in the MVVM architecture establishes a data interaction link with the server's database and other clients through the view model.

[0033] like Figure 6 As shown, the electronic form system includes: The server layer includes local servers and remote servers; The data layer is used for data retrieval between different layers, as well as for data filtering, encoding optimization, verification, and storage. The service layer is used to integrate business rules and operational processes related to electronic forms into callable services. The interaction layer includes workflow management: used to integrate relevant data from the service layer and data layer, and output structured and graphical data based on user-defined conditions; form business assistance: an auxiliary module for creating form business, providing functions such as component node management, data statistics, and data export by calling server and local resources; and a global window manager: a function to integrate form data with the same ID in multi-window applications and update the data within a single window. The business layer is an abstraction layer used to manage electronic form transactions. User interaction interface, transforming electronic form business into an operable interface; An interface for accessing large language models.

[0034] The data layer includes: (1) Data access interface: Provides software data access interface for data calling between components.

[0035] (2) Data verification: By establishing an independent data verification mechanism, we can achieve rapid verification of massive amounts of data with minimal server resources.

[0036] (3) Data Filtering: The software uses a localized data filtering mechanism, which retrieves all user-selected data from the server. The data filter is applied after the data is retrieved, and works with the "seamless data refresh" framework to update the data in the background, significantly reducing server resource consumption. At the same time, considering that users frequently operate the filter, the localized data filtering mechanism can control the data filtering response time to within 50ms.

[0037] (4) Data encoding and optimization: Data is encoded using algorithms such as Base64, MD5, SHA128, and SHA256, read locally, and dynamically parsed according to business needs. Caching millions of form data only requires minimal memory resources.

[0038] (5) Data storage: used for local data caching.

[0039] The service layer includes: (1) Log service: The log service collects log data from distributed systems and applications through various log collections to provide developers with a basis for bug fixing.

[0040] (2) Automatic software update: By pulling the software version configuration file from the server, an independent component is used to realize the online automatic update of the software, keeping the software always the latest version.

[0041] (3) UDP communication service: Local area network communication via the UDP protocol, performing UDP broadcasts on the local area network. It is responsible for the queued parsing and processing of received messages.

[0042] (4) Permission authentication: Perform current operation permission determination and perform form operability status generic matching.

[0043] (5) Automatic tagging service: Automatically color-codes the features matched by each piece of data on the form management page.

[0044] (6) IDE Fast Input Engine: By simulating the fast input engine of the IDE (inheriting the development environment), it enables the quick search of matching data or fields by continuous input of Pinyin, Chinese characters or the first letter of Pinyin, or by interval input.

[0045] (7) Hash Algorithm Assistance: Used to implement SHA512 one-way encryption of user data, and to encode multi-form workflow data through MD5 and other methods to achieve fast comparison and database hash verification.

[0046] (8) Real-time preview engine: By introducing an HTML-based rich text editing display mode, the form is rendered and previewed in real time based on the form information constructed by the user on the user interface.

[0047] (9) Workflow model: used to build workflows for each form.

[0048] (10) Database connection management service: used to implement automatic configuration of database connection pool.

[0049] (11) Notification service: used to convert messages from each thread and remind the operator via pop-up window.

[0050] (12) Global hotkey service: used to adapt global keyboard shortcuts and monitor scanning data of barcode scanners (non-COM port).

[0051] (13) ReactiveUI Message Bus Service: Used to enable communication between multiple Models and ViewModels components within the client, ensuring data exchange between modules under the condition of MVVM decoupling.

[0052] (14) System Status Response Service: Used to detect system status, automatically release software resources according to the idle state of the operating system, and automatically refresh data when the system status is restored.

[0053] (15) Snowflake ID Generation and Parsing Service: A new Snowflake algorithm is obtained by improving the existing Snowflake algorithm. The algorithm incorporates information such as unique form identifiers and unique computer identifiers, and simplifies the timestamp information according to the business volume. During parsing, the form type can be distinguished by extracting the unique form identifier, and the program will automatically execute the next execution plan.

[0054] The interaction layer includes: (1) Workflow management: Used in service layer and data layer methods to integrate relevant data and output structured and graphical data according to user-defined conditions.

[0055] (2) Form Business Assistance: An auxiliary module for creating form business, which provides related functions such as component node management (KKS-like), data statistics, and data export by calling server and local resources.

[0056] (3) Global Window Manager: In multi-window applications, it solves the problem of repeatedly opening the same form, integrates form data with the same ID, and realizes the function of updating the data when accessing it again in a single window.

[0057] The business layer is an abstraction layer used to manage form-related business logic integrated with the EFS system, including: (1) such as Figure 7 As shown, the defect registration management module's workflow is as follows: A defect order form is created, which is then reviewed sequentially by the shift leader and specialist. If the review fails, the form process ends; if it passes, the maintenance team receives and processes it. During the review stage, the equipment specialty or maintenance specialty on the form can be changed as needed. Finally, the processing result and acceptance result are submitted, and the form process ends. Figure 8 As shown, when there are related defect orders, a related defect order is created for the unresolved defect order, and the above defect form process is executed. After the process is completed, the unresolved defect order is updated.

[0058] (2) such as Figure 9 As shown, the work order management module's workflow is as follows: Create a work order form, including creating a new form directly, or / and creating it through favorites, or / and creating it by applying historical work orders, or / and creating it by reusing expired work order numbers, or / and creating it through the standard work order library; The Operations Department reviews the form; if approved, it is sent to the Equipment Department; if not approved, it returns to the work order creation process; The Equipment Department reviews the form; if approved, the server assigns a work order number; if not approved, it returns to the work order creation process; After assigning the work order number, it is printed, and the work order is tracked, ending the work order form process.

[0059] (3) such as Figure 10As shown, the operation ticket management module has the following workflow: create an operation ticket form, store, print and execute the operation ticket form, update the operation ticket content after execution, create a snapshot and store it, and repeat the process until the entire operation ticket form is executed.

[0060] (4) such as Figure 11 As shown, the workflow of the regular work management module is as follows: obtain the current time and shift, create a task list and execute it, and end the operation of the shift after receiving feedback on the execution result; switch to the next shift and repeat the above operation.

[0061] The user interface includes: (1) WinformUI: Build a Windows-based user interface.

[0062] (2) HTML: mainly used for real-time preview engine rendering of form pages.

[0063] (3) AvaloniaUI: Build user interfaces for platforms such as Windows, Linux, Android, and MacOS.

[0064] The interface is used for DeepSeek and ChatGPT large language model access: the server supports the deployment of local large language models, and the EFS client access provides advanced functions such as intelligent data analysis and intelligent data completion.

[0065] This system consists of a server, server-side application, database, client, and client-side application. The application software is called Electronic Form System (EFS). Its application scope is the digitization of forms in waste-to-energy incineration plants. Its business scope includes defect reports, work orders, operation tickets, scheduled work, handover notices, and records. The development framework is .NET Core 8.0, WinForm UI, Avalonia UI, and Reactive UI.

[0066] The general functions of this system include user and permission allocation system, data import and export, notification and tagging, quick management of PostgreSQL database, form data template management, defect ticket management, work ticket management, operation ticket management, regular work management, and form business expansion, etc.

[0067] Defect order management includes: querying, creating, modifying, reviewing and managing, automatic numbering, one-click re-creation (for defects not eliminated last month), querying all defects of a device within a certain time range, filtering and quick search functions, intelligent status and progress marking, data statistics, form addition reminders, online confirmation and review, form progress update reminders, comments, notes and messages, form association and automatic inheritance.

[0068] Work order management includes: querying, creating, modifying, reviewing and managing work orders; automatic numbering; creating new work orders by applying historical work orders; creating new work orders by applying standardized work order templates; automatic completion of security measures; completion of intelligent security measure identifiers; addition of intelligent security measures; near-expiration reminders; overdue reminders; form association and automatic inheritance; work order favorites; creation of standard work orders; standard work order favorites; and management of historical security measures.

[0069] Operation ticket management includes: operation ticket creation, operation ticket historical version snapshots, operation ticket favorites, and operation ticket templates.

[0070] Regular task management includes: regular task execution records, historical regular task queries, advanced queries, execution reminders, task lists, and custom task lists.

[0071] The system of the present invention addresses the following disadvantages of the prior art: (1) Currently, similar technologies widely use Web technology and rely on operating system browsers to run. Although Web technology has achieved a universal cross-platform solution, its performance in multi-window processing and large data volume display is poor. In addition, relying on HTTPS to send requests to remote servers will result in high latency, and all data processing depends on the server.

[0072] (2) Web-dependent technologies cannot achieve real-time data updates. High-frequency queries implemented through AJAX frameworks or polling consume excessive server resources.

[0073] (3) It is not closely integrated with actual business operations.

[0074] (4) There is no historical database of security measures for work ticket business.

[0075] The technical effects achieved by the system of the present invention include: (1) Deeply integrated with business and usage scenarios.

[0076] (2) Data collection and training of large language models, and API integration with mainstream large language models (DeepSeek, ChatGPT).

[0077] (3) Fully customizable form templates.

[0078] (4) Optimize and update accordingly as needed based on changes in actual production operations.

[0079] (5) It has significant advantages over similar systems that currently rely heavily on Web and traditional JavaScript frameworks, which suffer from inefficiency due to the need for dynamic or paginated loading when loading large amounts of data. It has faster data processing capabilities when loading massive amounts of data, and it is fast and smooth when displaying large amounts of data, achieving fast data loading by calling local computer cache resources.

[0080] (6) Cross-platform operation is achieved by rewriting the UI part using Avalonia UI.

[0081] (7) Use the most powerful free and open-source relational database system on the market: PostgreSQL. Its indexing performance is superior to MySQL.

[0082] (8) A security measure consists of: device name (node ​​data), security measure description, and security measure identifier, with the security measure being the main component of the work order. Due to differences in individual processing habits, the descriptions of security measures may vary slightly. Using an auto-completion function for security measures in this context would lead to a continuous increase in similar data in the database, making identification difficult and significantly increasing the workload of data maintenance. This software partitions the historical security measure database using fields such as work order type and device specialty, and creates an MD5 hash for each record for rapid verification. By leveraging the mechanism of binding security measures to associated devices, database maintenance overhead is significantly reduced, enabling millisecond-level querying and rapid insertion of security measures.

[0083] (9) Do not maintain the connection, access on demand, close the connection immediately after the data request is completed, and release server resources.

[0084] (10) Highly customizable manual and automatic maintenance functions.

[0085] (11) In the era of big language models, other intelligent functions can be realized by connecting with big language models through form systems.

[0086] The above description, in conjunction with specific preferred embodiments, provides a further detailed explanation of the present invention. It should not be construed that the specific implementation of the present invention is limited to these descriptions. For those skilled in the art, various simple deductions or substitutions can be made without departing from the concept of the present invention, and all such modifications and substitutions should be considered within the scope of protection of the present invention.

Claims

1. An electronic form digital management system based on waste incineration power generation management applications, characterized in that, The system includes a system architecture and an electronic form system. The system architecture includes a server, a database, and a client. The client has an embedded MVVM architecture. The database is deployed on the server. The server establishes server data interaction links with multiple clients through the database. The multiple clients establish client data interaction links with each other. The electronic form system includes: The server layer includes local servers and remote servers; The data layer is used for data retrieval between different layers, as well as for data filtering, encoding optimization, verification, and storage. The service layer is used to integrate business rules and operational processes related to electronic forms into callable services. The interaction layer includes workflow management: used to integrate relevant data from the service layer and data layer, and output structured and graphical data based on user-defined conditions; form business assistance: an auxiliary module for creating form business, providing functions such as component node management, data statistics, and data export by calling server and local resources; and a global window manager: a function to integrate form data with the same ID in multi-window applications and update the data within a single window. The business layer is an abstraction layer used to manage electronic form transactions. User interaction interface, transforming electronic form business into an operable interface; An interface for accessing large language models.

2. The electronic form digital management system based on waste incineration power generation management application as described in claim 1, characterized in that, The business layer includes an electronic form defect registration management module, and the workflow of the defect registration management module is as follows: Create a defect report form, which is reviewed by the shift leader and specialist in turn. If the review fails, the form process ends. If the review passes, the maintenance team receives and processes the form, and changes the equipment specialty or maintenance specialty as needed. Finally, the processing result and acceptance result are submitted, and the form process ends. When there are related defect orders, create a related defect order for the unresolved defect order and execute the above defect form process. After the process is completed, update the unresolved defect order.

3. The electronic form digital management system based on waste incineration power generation management application as described in claim 1, characterized in that, The business layer includes a work order management module, and the workflow of the work order management module is as follows: Create work order forms, including creating new ones directly, or / and creating them through favorites, or / and creating them by applying historical work orders, or / and creating them by reusing invalid work order numbers, or / and creating them through a standard work order library; The Operations Department reviews the application; if approved, it is sent to the Equipment Department; if not approved, it returns to the process of creating a work order. The Equipment Department reviews the application; if approved, the server assigns a work order number; if not approved, it returns to the process of creating a work order. After assigning the work order number, the work order is printed and tracked, thus ending the work order form process.

4. The electronic form digital management system based on waste incineration power generation management application as described in claim 1, characterized in that, The business layer includes an operation ticket management module, and the workflow of the operation ticket management module is as follows: Create an operation ticket form, store, print, and execute the operation ticket form. After execution, update the operation ticket content, create a snapshot, and store it. Repeat the process until the entire operation ticket form has been executed.

5. The electronic form digital management system based on waste incineration power generation management application as described in claim 1, characterized in that, The business layer includes a periodic work management module, and the workflow of the periodic work management module is as follows: Get the current time and shift, create a task list and execute it, and then end the operation for that shift after reporting the execution result; switch to the next shift and repeat the above operation.

6. The electronic form digital management system based on waste incineration power generation management application as described in claim 1, characterized in that, The data layer includes: Data access interface: Provides a data access interface for data access between different levels; Data verification: Rapid verification of massive amounts of data is achieved through an established independent data verification mechanism; Data filtering: Using a localized data filtering mechanism, data of all user-selected ranges is obtained from the server. The data filter is applied after the data is obtained, and works with the "data seamless refresh" framework to achieve background data updates. Data encoding and optimization: Data is encoded using algorithms such as Base64, MD5, SHA128, and SHA256, read locally, dynamically parsed according to business needs, and form data is cached; Data storage: Used for local data caching.

7. The electronic form digital management system based on waste incineration power generation management application as described in claim 1, characterized in that, The service layer includes: Log service: Collects log data from distributed systems and applications through various log collection methods to provide developers with a basis for bug fixing; Automatic software updates: By pulling the software version configuration file from the server, an independent component is used to achieve online automatic software updates, keeping the software always up-to-date; UDP communication service: Local area network communication via the UDP protocol, including UDP broadcasting within the local area network; responsible for queued parsing and processing of received messages; Authentication: Performs current operation permission determination and performs form operability status generic matching; Automatic tagging service: Automatically colors-codes the features matched by each piece of data on the form management page; IDE Fast Input Engine: By simulating the IDE's fast input engine, it allows users to quickly find matching data or fields by continuously or intermittently inputting Pinyin, Chinese characters, or the first letter of Pinyin. Hash algorithm assistance: Used for one-way SHA512 encryption of user data, and at the same time, it encodes multi-form workflow data using MD5 and other methods for fast comparison and database hash verification; Real-time preview engine: By introducing an HTML-based rich text editing display mode, the form is rendered and previewed in real time based on the form information constructed by the user on the user interface; Workflow model: used to build workflows for each form; Database connection management service: used to implement automatic configuration of database connection pool; Notification service: Used to convert messages from various threads and notify operators via pop-up windows; Global hotkey service: used to adapt to global keyboard shortcuts and monitor barcode scanner scan data; ReactiveUI Message Bus Service: Used for communication between multiple Models and ViewModels components within the client; System Status Response Service: Used to detect system status, automatically release software resources based on the operating system's idle state, and automatically refresh data when the system status recovers; Snowflake ID generation and parsing service: The Snowflake algorithm incorporates unique form identifiers and unique computer identifiers; during parsing, it distinguishes the form type by extracting the unique form identifier and automatically executes the next execution plan.

8. The electronic form digital management system based on waste incineration power generation management application according to claim 1, characterized in that, The user interface includes: WinformUI: Building user interfaces for Windows; HTML: Primarily used for real-time preview engine rendering of form pages; AvaloniaUI: Build user interfaces for platforms such as Windows, Linux, Android, and macOS.

9. The electronic form digital management system based on waste incineration power generation management application as described in claim 1, characterized in that, When multiple clients interact, the client acting as the sender performs the following procedure: When a user sends a message on the client, the client extracts and parses the ID, updates and queries the data in the server's database, and verifies the data to be updated. If the data is new, the cache is updated directly and a notification is sent. If the data is already existing, the data is merged, new data is created, and a notification is sent.

10. The electronic form digital management system based on waste incineration power generation management application according to claim 1, characterized in that, When multiple clients interact, the client acting as the receiver performs the following procedure: The client receives a message and adds it to a thread queue. The UI thread processes the message and validates the message data. If the validation passes, the thread terminates; otherwise, the data is retrieved again. Simultaneously, after processing the message, the client extracts and parses the ID, updates and queries the data in the server's database, and checks the message data. If the data is new, the cache is updated directly, the data is synchronized, and the UI is modified. If the data already exists, the data is merged, new data is created, synchronized, and the UI is modified.

Images