A full-process intelligent management method and system for concrete pouring

Abstract

A kind of whole-process intelligent management method and system of concrete pouring order belong to building engineering information management technical field. Including: task creation and initiation, multi-level intelligent approval flow, task execution and state locking, file automatic filing and generation. The present application realizes the online, standardization, closed-loop management of pouring order, guarantees the approval efficiency through the automatic passing mechanism of timeout, ensures the data authenticity and traceability through the state locking mechanism, effectively improves the construction management efficiency and engineering quality control level.

Description

Technical Field

[0001] This invention relates to the field of information management technology for construction projects, specifically to an intelligent management method and system for the entire process of concrete pouring, which is particularly suitable for smart construction site construction of large-scale infrastructure, building construction, and water conservancy and hydropower projects. Background Technology

[0002] In building construction, concrete pouring is a critical process that determines structural safety and quality. To ensure standardized construction and traceability, the industry generally adopts a "pouring order" system, which requires the construction unit to submit an application before pouring, which can only be implemented after review and confirmation by multiple parties, including technical, testing, supervision, and mixing plant personnel.

[0003] Currently, traditional pouring order management mainly relies on paper forms or scattered electronic spreadsheets. Although the existing technology CN112907200A, a pouring order monitoring system and method, proposes an online approval and image monitoring approach for pouring orders, it still has the following shortcomings. This application proposes an improvement scheme to address these shortcomings: (1) The lack of an automatic approval mechanism for timeouts means that approval efficiency is greatly affected by human factors; A current pouring order monitoring system and method only specifies the approval time but lacks an automatic approval mechanism for overdue orders. If an approver fails to process the order in a timely manner, the entire process will be blocked, failing to meet the high timeliness requirements of construction sites. This application establishes an automatic approval mechanism for overdue orders. The system automatically updates the status of unapproved nodes to "approved" and moves the process to the next node, avoiding process interruptions caused by personnel response delays.

[0004] (2) There is a lack of data locking mechanism after task execution, data can be tampered with, and traceability is poor; While a current pouring order monitoring system and method has implemented approval record archiving, it does not lock the data for tasks already executed. In engineering practice, task parameters can still be modified after pouring is completed, posing a risk of data falsification or post-construction modifications, affecting the authenticity of quality traceability. This application automatically locks all data fields after the task status is updated to "pouring completed," prohibiting any modification or deletion operations, ensuring the authenticity, integrity, and immutability of construction data.

[0005] (3) Historical data memory and input recommendation are not implemented, resulting in low efficiency for repeated input; A current pouring order monitoring system and method does not mention the recording and utilization of user historical input data. Construction workers must repeatedly fill in a large number of the same or similar parameters each time they create a task order, resulting in low efficiency. This application uses a history memory unit to automatically record data such as pouring location, slump, and strength grade entered by the user each time, and provides input recommendations for the next creation, significantly improving operational efficiency.

[0006] (4) The approval process is rigid and lacks a flexible personnel configuration interface; The approval process for a pouring order monitoring system and method is relatively complex and includes a reverse secondary confirmation process, but it does not provide a flexible multi-level approval personnel configuration function, making it difficult to adapt to the customized needs of different projects for approval nodes. This application provides a personnel configuration interface, supporting users to flexibly configure multi-level approval personnel such as supervisors, testers, and mixing plant auditors. Each node can be configured with one or more people, making it highly adaptable.

[0007] (5) Batch generation of standard format pouring order files is not supported; The existing pouring order monitoring system and method only mentions archiving functionality and does not address the batch generation of pouring order files in industry-standard format from multiple task orders. This application supports users in batch selecting task orders, automatically generating a standard PDF file containing three copies of the documents from the engineering department, laboratory, and mixing plant. It also supports embedded signature images, dynamic layout, and packaged download, meeting the needs of project archiving and printing.

[0008] (6) The generation of statistical charts based on filtering criteria has not been implemented; A current pouring order monitoring system and method does not provide visualization and statistical functions for pouring task data. This application supports filtering by conditions such as contract section, time range, and mixing plant, and automatically generates pie charts / bar charts showing the planned volume ratio of strength grades to assist management decision-making. Summary of the Invention

[0009] To achieve the above objectives, the present invention provides a method and system for intelligent management of the entire process of concrete pouring orders, the specific technical solution of which is as follows: A fully intelligent management method for concrete pouring orders includes the following steps: Step S1: Task creation and initiation; In response to user input on the client interface, the system receives the core parameters of the concrete pouring task. These core parameters include, but are not limited to: planned pouring time, contract section, associated mixing plant, pouring location, concrete strength grade, planned volume, design slump, transportation method, transportation distance, and remarks.

[0010] During user input, the system performs real-time data integrity checks, marking all required fields with an asterisk (*) and prompting the user before submission if any required fields are missing. Simultaneously, the system records historical user input data, building a user operation memory. When the user creates a task again, the system automatically retrieves historical input data from the memory and provides input recommendations, including historical input options for fields such as pouring location, slump, and strength grade.

[0011] The system provides an approval personnel configuration interface, supporting users to flexibly configure multi-level approval personnel, including the supervising leader, testers, and mixing plant auditors. Each approval node supports configuring one or more approval personnel. After the user completes all the information and clicks the confirmation button, the system generates a pouring task order with a unique number. This unique number is generated based on the current timestamp to ensure global uniqueness.

[0012] Step S2: Multi-level intelligent approval workflow; The system will push the pouring task order to each approval node in sequence according to the preset multi-level approval process. The preset multi-level approval process is as follows: the leader in charge reviews the node → the tester reviews the node → the mixing plant reviews the node.

[0013] The system monitors the approval status of each approval node in real time and implements an automatic timeout approval mechanism, specifically including: The system periodically scans the approval record table via scheduled tasks; For approval records with a status of "pending review" and an update time exceeding the preset timeout period, the system will automatically update the approval status of that node to "approved". The system automatically sets the approver of the current approval node as the first-priority approver preset for that node and records "automatic review after timeout" in the approval comments field; The system automatically forwards the task order to the next approval node.

[0014] When the approval status changes at each approval node, the system automatically sends an SMS notification to the relevant responsible person, specifically including: Once the task order is submitted, the system sends a text message to all responsible persons configured by the supervising leader node, containing the task order identification information. Once the supervisor in charge approves the application, the system sends a text message to all responsible persons configured in the tester node. Once the tester approves the application, the system sends a text message to all responsible persons configured in the batching plant's reviewer node. Once the mixing plant approves the application, the system sends a text message to the person who initiated the task order, informing them that the approval is complete.

[0015] Step S3: Task execution and state locking; The system monitors the approval status of each approval node in real time. When the approval status of all approval nodes is "approved", the system updates the status of the pouring task order to the executable status and displays the "execute" button on the client interface.

[0016] In response to the user's confirmation action triggered by the confirmation interface on the client, the system displays a secondary confirmation dialog box. After the user confirms again, the system performs the following operations: Add a new record of type "Execution" to the audit record table, recording the executor's information and the execution time; Update the status of the pouring task sheet to "Pouring Completed"; Lock all data fields of the pouring task sheet, including planned pouring time, section, mixing plant, pouring location, strength grade, planned volume, slump, transportation method, transportation distance, and remarks, and prohibit any modification or deletion of these fields.

[0017] The system also provides a withdrawal function, allowing the task initiator to withdraw a task when it is in the pending approval or review process but has not yet been executed. When the withdrawal operation is performed, the system resets the status of each approval node to the "not started" state and deletes the existing review records, allowing the user to edit and resubmit.

[0018] Step S4: Automatic file archiving and generation; In response to a download request triggered by the user on the client, and based on at least one pouring task selected by the user, the system performs the following operations: Iterate through the list of pouring task IDs selected by the user; For each pouring task order, the file generation module is invoked to dynamically fill the preset three-part form template based on the task order data; The three-part form template includes a first copy for the engineering department, a second copy for the laboratory, and a third copy for the mixing plant. Each copy fully presents the project name, pouring location, strength grade, planned volume, slump, transportation method, transportation distance, and remarks, and indicates the planned pouring time and signature field. The signature field includes the signatures of the construction worker, the supervisor in charge, the tester, and the mixing plant. The system reads the corresponding signature image URLs from the user information table and embeds them into the PDF file. The system uses the iText library to generate PDF files and dynamically adjusts the font size according to the text length. For extremely long texts, the font size is automatically reduced to ensure that the content is displayed completely. The system packages all generated PDF files into a ZIP archive and returns it to the client for users to download.

[0019] Step S5: Data visualization and statistics; In response to a user's query request, the system generates a statistical chart of the pouring task based on the filtering criteria selected by the user. The filtering criteria include the section, time range, and mixing plant.

[0020] Specifically, the system supports generating actual usage ratio charts, and the generation process includes: Based on the filtering criteria, retrieve the pouring task orders that meet the criteria from the data storage module; Extract the intensity level and planned quantity of each task; Group by intensity level and calculate the total planned volume for each intensity level; Calculate the total planned volume of all task orders; Calculate the percentage of planned volume for each intensity level; Generate pie charts or bar charts to show the proportion of concrete usage for each strength grade; At the same time, the system records the user's query conditions and saves them to the user's operation memory database for easy access next time.

[0021] A fully intelligent management system for concrete pouring operations includes: The task management module receives and manages user-created pouring task orders, supporting operations such as adding, deleting, modifying, and querying these orders, as well as status monitoring. This module includes a history memory unit to record data entered by the user each time a task order is created, providing historical input recommendations when the user creates a new task. The module also includes a time verification unit to determine if the pouring time is more than 5 minutes earlier than the current time; if so, it is automatically marked as a "supplementary" task.

[0022] The process engine module, connected to the task management module, is used to solidify multi-level approval processes and control the flow of pouring task orders between approval nodes. This module includes a timeout monitoring unit, configured to periodically scan the approval record table for records whose status is "Pending Review" and whose update time exceeds a preset timeout period, automatically update their status to "Approved," and move the task order to the next node. The module also includes a status determination unit, used to comprehensively determine the current process stage of the task order based on the review status of each node. These process stages include: pending submission, pending leadership review, pending tester review, pending mixing plant review, approved, and pouring completed.

[0023] The notification and reminder module, connected to the workflow engine module, automatically pushes notification messages to relevant responsible parties when the task status changes. This module integrates an SMS gateway interface, supporting batch SMS sending. The SMS content includes task identification information and to-do reminders. The module also includes a user information query unit to retrieve user mobile phone numbers based on user ID or username.

[0024] Access Control Module: Implemented based on the Shiro framework, this module verifies user identity and operation permissions, including at least permission checks for task creation, editing, deletion, approval, and execution. The module is configured as follows: when the status of a pouring task order is "Pouring Completed," all operations except for querying are prohibited, including editing, deletion, and withdrawal; when the current user is not the approver of the current approval node of the task order, their approval operation is prohibited; when the current user is not the creator of the task order, their deletion operation is prohibited.

[0025] The document generation module, connected to the task management module, dynamically fills a preset template with concrete pouring order data to generate a standard-format concrete pouring order document. This module integrates the iText and PDFBox libraries, supporting the creation, editing, and image embedding of PDF files. It includes a font management unit for loading Chinese fonts and supporting the normal display of Chinese content; a signature processing unit for loading signature images from a specified URL and encoding URLs containing Chinese characters; and a dynamic layout unit for dynamically adjusting cell font sizes based on text length to ensure complete content display.

[0026] Data storage module: Connected to the modules mentioned above, this module stores task order information, approval records, user information, and system configuration data. It is implemented using a MySQL database and includes the following tables: Task order information table, storing core parameters of the pouring task; Approval record table, storing review records for each approval node; Operation memory table, storing historical user input data and query conditions; and User information table, storing basic user information, mobile phone number, and signature image path.

[0027] Compared with the prior art, the present invention has the following beneficial effects: 1. Improve the quality and safety of the project: By establishing a mandatory pre-approval mechanism, key indicators such as mix proportion, strength grade, and raw material testing are ensured to be approved before pouring, thus preventing potential quality problems from the source and effectively reducing project rework and safety risks.

[0028] 2. Improve management and collaboration efficiency: Enable full-process online management with "online initiation, real-time push, one-click approval, and automatic archiving". Combined with the automatic approval mechanism for timeouts, it effectively avoids process blockages caused by personnel response delays, significantly reduces communication costs, and improves cross-departmental and cross-position collaboration efficiency.

[0029] 3. Enhanced process control capabilities: A status locking mechanism (unmodifiable after execution) ensures the authenticity, integrity, and immutability of construction data, providing a solid data foundation for accountability and quality acceptance. The design of the withdrawal function balances process rigor with flexibility in handling business changes.

[0030] 4. Promoting Digital Construction: The structured data generated by the system can be seamlessly integrated with BIM platforms, ERP systems, or government regulatory platforms, providing fundamental support for subsequent big data analysis, resource optimization and scheduling, and green construction assessment. The history memory function further enhances user experience and input efficiency.

[0031] 5. Excellent scalability and versatility: The system adopts a modular design with decoupling between modules, facilitating functional expansion and customization. Its strong versatility, flexible deployment, and ease of operation make it suitable for various engineering scenarios such as building construction, bridges, tunnels, and water conservancy, and it possesses significant value for replication and promotion. Attached Figure Description

[0032] Figure 1 This is a flowchart illustrating the overall process of intelligent management of the entire concrete pouring order in this embodiment of the invention. Figure 2 This is a detailed flowchart of the multi-level approval process in an embodiment of the present invention;

[0033] Figure 3 This is a state diagram of task order state transitions in an embodiment of the present invention;

[0034] Figure 4 This is a block diagram of the system module structure in an embodiment of the present invention. Detailed Implementation

[0035] The technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. This embodiment is illustrated using the concrete pouring management of a large-scale highway project as an application scenario.

[0036] Example 1

[0037] like Figure 1 As shown, a fully intelligent management method for concrete pouring orders includes the following steps: Step S1: Task creation and initiation; In response to user input on the client interface, the system receives the core parameters of the concrete pouring task. These core parameters include, but are not limited to: planned pouring time, contract section, associated mixing plant, pouring location, concrete strength grade, planned volume, design slump, transportation method, transportation distance, and remarks.

[0038] During user input, the system performs real-time data integrity checks, marking all required fields with an asterisk (*) and prompting the user before submission if any required fields are missing. Simultaneously, the system records historical user input data, building a user operation memory. When the user creates a task again, the system automatically retrieves historical input data from the memory and provides input recommendations, including historical input options for fields such as pouring location, slump, and strength grade.

[0039] The system provides an approval personnel configuration interface, supporting users to flexibly configure multi-level approval personnel, including the supervising leader, testers, and mixing plant auditors. Each approval node supports configuring one or more approval personnel. After the user completes all the information and clicks the confirmation button, the system generates a pouring task order with a unique number. This unique number is generated based on the current timestamp to ensure global uniqueness.

[0040] Step S2: Multi-level intelligent approval workflow; The system will push the pouring task order to each approval node in sequence according to the preset multi-level approval process. The preset multi-level approval process is as follows: the leader in charge reviews the node → the tester reviews the node → the mixing plant reviews the node.

[0041] The system monitors the approval status of each approval node in real time and implements an automatic timeout approval mechanism, specifically including: The system periodically scans the approval record table via scheduled tasks; For approval records with a status of "pending review" and an update time exceeding the preset timeout period, the system will automatically update the approval status of that node to "approved". The system automatically sets the approver of the current approval node as the first-priority approver preset for that node and records "automatic review after timeout" in the approval comments field; The system automatically forwards the task order to the next approval node.

[0042] When the approval status changes at each approval node, the system automatically sends an SMS notification to the relevant responsible person, specifically including: Once the task order is submitted, the system sends a text message to all responsible persons configured by the supervising leader node, containing the task order identification information. Once the supervisor in charge approves the application, the system sends a text message to all responsible persons configured in the tester node. Once the tester approves the application, the system sends a text message to all responsible persons configured in the batching plant's reviewer node. Once the mixing plant approves the application, the system sends a text message to the person who initiated the task order, informing them that the approval is complete.

[0043] Step S3: Task execution and state locking; The system monitors the approval status of each approval node in real time. When the approval status of all approval nodes is "approved", the system updates the status of the pouring task order to the executable status and displays the "execute" button on the client interface.

[0044] In response to the user's confirmation action triggered by the confirmation interface on the client, the system displays a secondary confirmation dialog box. After the user confirms again, the system performs the following operations: Add a new record of type "Execution" to the audit record table, recording the executor's information and the execution time; Update the status of the pouring task sheet to "Pouring Completed"; Lock all data fields of the pouring task sheet, including planned pouring time, section, mixing plant, pouring location, strength grade, planned volume, slump, transportation method, transportation distance, and remarks, and prohibit any modification or deletion of these fields.

[0045] The system also provides a withdrawal function, allowing the task initiator to withdraw a task when it is in the pending approval or review process but has not yet been executed. When the withdrawal operation is performed, the system resets the status of each approval node to the "not started" state and deletes the existing review records, allowing the user to edit and resubmit.

[0046] Step S4: Automatic file archiving and generation; In response to a download request triggered by the user on the client, and based on at least one pouring task selected by the user, the system performs the following operations: Iterate through the list of pouring task IDs selected by the user; For each pouring task order, the file generation module is invoked to dynamically fill the preset three-part form template based on the task order data; The three-part form template includes a first copy for the engineering department, a second copy for the laboratory, and a third copy for the mixing plant. Each copy fully presents the project name, pouring location, strength grade, planned volume, slump, transportation method, transportation distance, and remarks, and indicates the planned pouring time and signature field. The signature field includes the signatures of the construction worker, the supervisor in charge, the tester, and the mixing plant. The system reads the corresponding signature image URLs from the user information table and embeds them into the PDF file. The system uses the iText library to generate PDF files and dynamically adjusts the font size according to the text length. For extremely long texts, the font size is automatically reduced to ensure that the content is displayed completely. The system packages all generated PDF files into a ZIP archive and returns it to the client for users to download.

[0047] Step S5: Data visualization and statistics; In response to a user's query request, the system generates a statistical chart of the pouring task based on the filtering criteria selected by the user. The filtering criteria include the section, time range, and mixing plant.

[0048] Specifically, the system supports generating actual usage ratio charts, and the generation process includes: Based on the filtering criteria, retrieve the pouring task orders that meet the criteria from the data storage module; Extract the intensity level and planned quantity of each task; Group by intensity level and calculate the total planned volume for each intensity level; Calculate the total planned volume of all task orders; Calculate the percentage of planned volume for each intensity level; Generate pie charts or bar charts to show the proportion of concrete usage for each strength grade; At the same time, the system records the user's query conditions and saves them to the user's operation memory database for easy access next time.

[0049] Example 2

[0050] like Figure 4 As shown, a fully intelligent management system for concrete pouring includes: The task management module receives and manages user-created pouring task orders, supporting operations such as adding, deleting, modifying, and querying these orders, as well as status monitoring. This module includes a history memory unit to record data entered by the user each time a task order is created, providing historical input recommendations when the user creates a new task. The module also includes a time verification unit to determine if the pouring time is more than 5 minutes earlier than the current time; if so, it is automatically marked as a "supplementary" task.

[0051] The process engine module incorporates a three-tiered approval logic: "Supervisor → Tester → Mixing Plant," and integrates an automatic timeout approval algorithm. Connected to the task management module, it solidifies the multi-level approval process and controls the flow of pouring task orders between approval nodes. This module includes a timeout monitoring unit configured to periodically scan the approval record table for records with a status of "Pending Review" and an update time exceeding a preset timeout period, automatically updating their status to "Approved" and transferring the task order to the next node. The module also includes a status determination unit, used to comprehensively determine the current process stage of the task order based on the review status of each node. These process stages include: Pending Submission, Pending Supervisor Review, Pending Tester Review, Pending Mixing Plant Review, Approved, and Pouring Completed.

[0052] The notification and reminder module, connected to the workflow engine module, automatically pushes notification messages to relevant responsible parties when the task status changes. This module integrates an SMS gateway interface, supporting batch SMS sending. The SMS content includes task identification information and to-do reminders. The module also includes a user information query unit to retrieve user mobile phone numbers based on user ID or username.

[0053] Access Control Module: Implemented based on the Shiro framework, this module verifies user identity and operation permissions, including at least permission checks for task creation, editing, deletion, approval, and execution. The module is configured as follows: when the status of a pouring task order is "Pouring Completed," all operations except for querying are prohibited, including editing, deletion, and withdrawal; when the current user is not the approver of the current approval node of the task order, their approval operation is prohibited; when the current user is not the creator of the task order, their deletion operation is prohibited.

[0054] The document generation module, connected to the task management module, dynamically fills a preset template with concrete pouring order data to generate a standard-format concrete pouring order document. This module integrates the iText and PDFBox libraries, supporting the creation, editing, and image embedding of PDF files. It includes a font management unit for loading Chinese fonts and supporting the normal display of Chinese content; a signature processing unit for loading signature images from a specified URL and encoding URLs containing Chinese characters; and a dynamic layout unit for dynamically adjusting cell font sizes based on text length to ensure complete content display.

[0055] Data storage module: Connected to the modules mentioned above, this module stores task order information, approval records, user information, and system configuration data. It is implemented using a MySQL database and includes the following tables: Task order information table, storing core parameters of the pouring task; Approval record table, storing review records for each approval node; Operation memory table, storing historical user input data and query conditions; and User information table, storing basic user information, mobile phone number, and signature image path.

[0056] Example 3

[0057] This embodiment uses a specific project to introduce a full-process intelligent management method for concrete pouring orders, as described in Embodiment 1.

[0058] First, the construction worker accesses the task creation interface on the client (PC web application or mobile app). The system calls the task management module, displaying the WBS project structure tree for the user to select information such as the contract section and mixing plant. After filling in core parameters such as pouring location, strength grade, and planned volume, the user configures the supervising supervisor, tester, and mixing plant reviewer using the personnel selection controls. The system marks all required fields with asterisks (*) on the front end to ensure data integrity. After the user clicks "Confirm" to submit, the system calls the backend interface to generate a uniquely numbered task order, with the default status being "Pending Submission." At this point, the system automatically records the user's historical information for future recommendations.

[0059] like Figure 2As shown, after a user submits a task, the system calls the process engine module to change the task status to "Pending Leader Approval" and sends a text message to the supervisor through the notification reminder module: "You have a new task order that needs to be approved: Pouring Order - XX Section - XX Mixing Plant - XX Location".

[0060] After logging into the system, the supervising leader views the task details in the "Pending Review" list and clicks "Approve". The system records their review comments and moves the task to the "Pending Tester Review" node, while simultaneously sending an SMS notification to the tester.

[0061] If the supervising supervisor or researcher does not perform any action within 3 minutes, the system triggers the `taskAutomaticReview` method via the XXL-Job scheduled task. This method scans the database for records whose status is "Pending Review" and whose update time exceeds 3 minutes, automatically updates their status to "Approved," sets the approver as the first-priority approver for that node, adds the note "Automatic Review Overdue," and then forces the process to the next node. This mechanism effectively solves the problem of process blockage caused by personnel response delays.

[0062] When the task order reaches the "Pending Mixing Plant Review" node, after the mixing plant operator approves it, the system determines that all prerequisites have been met, and the task order status is updated to "Approved".

[0063] After the construction worker finds a record with a status of "Approved" on the task order homepage, they click the "Execute" button. The system displays a secondary confirmation dialog box. After the user confirms, the system calls the execute interface, adds an "exe" type record to the approval record table, and marks the task order status as "Pouring Completed." Figure 3 As shown, once a task order enters the "pouring complete" state, the system locks all fields through the permission control module, preventing users from editing or deleting the task order.

[0064] Finally, when archiving or printing is required, the data clerk can select multiple records in the task list and click "Batch Download". The system calls the file generation module, iterates through the selected task IDs, and calls the `generatePdf` method for each task. This method uses the iText library to dynamically populate the task data (project name, pouring location, strength grade, etc.) into the three-part form template, generates a PDF file, and packages it into a ZIP archive for users to download.

[0065] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for intelligent management of the entire process of concrete pouring orders, characterized in that, Includes the following steps: Step S1, Task Creation and Initiation: Responding to the user's input on the client interface, receive the core parameters of the concrete pouring task, and generate a pouring task order with a unique identifier based on the user-configured approver information. Step S2, Multi-level intelligent approval process: The pouring task order is pushed to each approval node in sequence according to the preset multi-level approval process, the approval status of each approval node is monitored in real time, and an automatic timeout approval mechanism is executed: if the current approval node does not complete the approval operation within the preset timeout period, the system automatically updates the approval status of the node to approved and transfers the task order to the next approval node. Step S3, Task Execution and Status Locking: When the approval status of all approval nodes is "passed", the status of the pouring task order is updated to "executable". In response to the confirmation operation triggered by the user on the execution confirmation interface, the status of the pouring task order is updated to "pouring completed", and all data fields of the pouring task order are locked to prevent modification or deletion. Step S4: Automatic File Archiving and Generation: In response to a download request triggered by the user on the client, based on at least one pouring task sheet selected by the user, automatically generate a standard format concrete pouring order file and return it to the client or archive it for storage.

2. The intelligent management method for the entire process of concrete pouring orders according to claim 1, characterized in that, Step S1 specifically includes: Step S11: In response to the user's input operation on the client interface, receive the core parameters of the concrete pouring task. The core parameters include: planned pouring time, contract section, associated mixing plant, pouring location, concrete strength grade, planned volume, design slump, transportation method, transportation distance, and remarks. Step S12: During user input, the system performs real-time data integrity verification, marks all required fields with asterisks, and prompts the user before submission if any required information is not filled in. At the same time, the system records the historical data of each user input and builds a user operation memory bank. When the user creates a task order again, the system automatically retrieves historical input data from the memory bank and provides input recommendations to the user. The input recommendations include historical input options for fields such as pouring location, slump, and strength grade. Step S13: The system provides an approval personnel configuration interface, which supports users to flexibly configure multi-level approval personnel. The multi-level approval personnel include the supervisor, the tester, and the mixing plant auditor. Each approval node supports the configuration of one or more approval personnel. After the user completes all the information, clicks the confirmation button, and the system generates a pouring task sheet with a unique number. The unique number is generated based on the current timestamp to ensure global uniqueness.

3. The intelligent management method for the entire process of concrete pouring orders according to claim 1, characterized in that, Step S2 specifically includes: Step S21: The system pushes the pouring task order to each approval node in sequence according to the preset multi-level approval process. The preset multi-level approval process is: the leader in charge approves the node → the tester approves the node → the mixing plant approves the node. Step S22: The system monitors the approval status of each approval node in real time and executes an automatic timeout approval mechanism, specifically including: The system periodically scans the approval record table via scheduled tasks; For approval records whose status is pending review and whose update time exceeds the preset timeout period, the system will automatically update the approval status of that node to approved; The system automatically sets the approver of the current approval node as the first-priority approver preset for that node, and records the automatic review timeout in the approval comments field; The system automatically forwards the task order to the next approval node; Step S23: When the approval status changes at each approval node, the system automatically sends an SMS notification to the relevant responsible person, specifically including: Once the task order is submitted, the system sends a text message to all responsible persons configured by the supervising leader node, containing the task order identification information. Once the supervisor in charge approves the application, the system sends a text message to all responsible persons configured in the tester node. Once the tester approves the application, the system sends a text message to all responsible persons configured in the batching plant's reviewer node. Once the mixing plant approves the application, the system sends a text message to the person who initiated the task order, informing them that the approval is complete.

4. The intelligent management method for the entire process of concrete pouring orders according to claim 1, characterized in that, Step S3 specifically includes: Step S31: The system monitors the approval status of each approval node in real time. When the approval status of all approval nodes is approved, the system updates the status of the pouring task order to the executable status and displays the execute button on the client interface. Step S32: In response to the user's confirmation operation triggered by the confirmation interface on the client, the system pops up a secondary confirmation dialog box. After the user confirms again, the system performs the following operations: Add a new record for the execution type in the audit record table, recording the executor information and execution time; Update the status of the pouring task sheet to "pouring completed"; Lock all data fields of the pouring task sheet, including planned pouring time, section, mixing plant, pouring location, strength grade, planned volume, slump, transportation method, transportation distance and remarks, and prohibit modification or deletion of these fields. Step S33: The system also provides a withdrawal function. When a task is in the pending approval state or in the review process but has not yet been executed, the task initiator can withdraw the task. When the withdrawal operation is executed, the system will reset the status of each approval node to the non-started state and delete the existing review records, allowing the user to edit and resubmit.

5. The intelligent management method for the entire process of concrete pouring orders according to claim 1, characterized in that, Step S4 specifically includes: In response to a download request triggered by the user on the client, and based on at least one pouring task selected by the user, the system performs the following operations: Iterate through the list of pouring task IDs selected by the user; For each pouring task order, the file generation module is invoked to dynamically fill the preset three-part form template based on the task order data; The three-part form template includes a first copy for the engineering department, a second copy for the laboratory, and a third copy for the mixing plant. Each copy fully presents the project name, pouring location, strength grade, planned volume, slump, transportation method, transportation distance, and remarks, and indicates the planned pouring time and signature field. The signature field includes the signatures of the construction worker, the supervisor in charge, the tester, and the mixing plant. The system reads the corresponding signature image URLs from the user information table and embeds them into the PDF file. The system uses the iText library to generate PDF files and dynamically adjusts the font size according to the text length. For extremely long texts, the font size is automatically reduced to ensure that the content is displayed completely. The system packages all generated PDF files into a ZIP archive and returns it to the client for users to download.

6. A method for intelligent management of the entire process of concrete pouring orders according to any one of claims 1 to 5, characterized in that, It also includes step S5: in response to the user's query request, a statistical chart of the pouring task is generated based on the filtering conditions selected by the user. The filtering conditions include the section, time range, and mixing plant.

7. A fully intelligent management system for the concrete pouring process used in the method of claim 1, characterized in that, include: The task management module is used to receive and manage the pouring task orders created by users, and supports adding, deleting, modifying and querying pouring task orders as well as status monitoring. The process engine module, connected to the task management module, is used to solidify multi-level approval processes, control the flow of pouring task orders between approval nodes, and implement an automatic timeout approval mechanism. The notification and reminder module, connected to the process engine module, is used to automatically push notification messages to relevant responsible persons when the status of a task order changes; The access control module is used to verify user identity and operation permissions, including at least permission verification for task creation, editing, deletion, approval and execution operations; The file generation module is connected to the task management module and is used to dynamically fill the preset template according to the data of the pouring task order to generate a standard format concrete pouring order file. The data storage module, connected to the above modules, is used to store task order information, approval records, user information, and system configuration data.

8. The intelligent management system for the entire process of concrete pouring orders according to claim 7, characterized in that, The process engine module includes a timeout monitoring unit, which is configured to periodically scan the approval record table for approval records whose status is pending review and whose update time exceeds a preset timeout period, automatically update their status to approved, and transfer the task to the next node.

9. The intelligent management system for the entire process of concrete pouring orders according to claim 7, characterized in that, The access control module is configured such that when the status of the pouring task order is "pouring completed", any operation other than querying is prohibited, including editing, deletion and revocation.

10. The intelligent management system for the entire process of concrete pouring orders according to claim 7, characterized in that, The task management module is also equipped with a history memory unit, which records the data entered by the user each time a task is created, and provides historical input recommendations when the user creates a task again.

Images