Full-process progress management and control method for communication engineering construction project and storage medium
By combining JSON templates and the Flowable engine with the MinIO storage system, the problems of information silos and insufficient critical path monitoring in communication engineering construction projects have been solved, enabling real-time updates and efficient collaboration of the entire process schedule, and improving the agility and intelligence of construction management.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- FUJIAN POST&TELECOM PLANNING & DESIGNING INST CO LTD
- Filing Date
- 2026-01-16
- Publication Date
- 2026-05-01
AI Technical Summary
Traditional communication engineering construction projects suffer from problems such as a disconnect between planning and actual progress, information silos, and insufficient monitoring of critical paths, making it difficult to share construction progress in real time and achieve efficient collaboration, which in turn affects project schedule control.
The system uses JSON templates to define process template information and establishes monitoring processes through the Flowable process engine. It combines the MinIO high-performance distributed object storage system to achieve centralized management of project documents and real-time updates of progress data. It configures progress control thresholds for dynamic comparison and hierarchical alarms, and supports visual interface display and data analysis.
It enables full-process progress control of communication engineering construction projects, avoids manual coordination and data aggregation, realizes real-time information sharing and efficient collaboration, improves progress response capability and risk warning efficiency, and supports data-driven continuous optimization.
Smart Images
Figure CN121961185A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of IT and software development technology, specifically to a method for full-process progress control and storage medium for communication engineering construction projects. Background Technology
[0002] With the widespread adoption of high-speed internet, 5G communication, and the Internet of Things (IoT), the complexity of communication engineering construction projects has significantly increased. Traditional construction processes still rely heavily on plan-driven approaches, phased linear progress, manual coordination of schedules, and manual data aggregation and hierarchical reporting. These traditional methods are no longer sufficient to meet the refined management and timeliness requirements of modern communication engineering construction projects, primarily in the following three aspects:
[0003] 1. The plan is out of sync with reality, and dynamic adjustments are lagging behind.
[0004] The initial project schedule is often based on idealized assumptions and fails to adequately consider the complexities of the on-site environment (such as municipal coordination, weather impacts, and route changes), leading to frequent unplanned delays during construction. Furthermore, the schedule monitoring and adjustment mechanisms are not agile enough to respond promptly to changes, resulting in the overall project schedule spiraling out of control.
[0005] 2. Severe information silos and low collaboration efficiency.
[0006] The various participants (construction unit, design institute, construction unit, supervision unit, etc.) use different tools or systems, resulting in scattered progress data and delayed updates, making it difficult to achieve real-time information sharing and efficient collaboration.
[0007] 3. Insufficient monitoring of the critical path and delayed risk warning.
[0008] The lack of a refined tracking and intelligent early warning mechanism for key processes (such as fiber optic cable laying and base station commissioning) often means that problems are only discovered when they accumulate to the point of seriously affecting the project schedule, thus missing the best opportunity for intervention. Summary of the Invention
[0009] In view of the above problems, this application provides a method and storage medium for full-process progress control of communication engineering construction projects. The existing construction process of communication engineering construction projects relies on the mechanism of manual coordination of progress, manual summarization and hierarchical reporting, which has the problems of scattered progress data, delayed updates and difficulty in achieving real-time information sharing and efficient collaboration.
[0010] To achieve the above objectives, the inventors provide a method for full-process progress control of communication engineering construction projects, including:
[0011] The process template information for communication engineering construction projects is obtained through JSON template definition. The process template information includes project type, project name, project version, process node set and process review record. The process node set includes node information of process nodes, including node number, node name, start time, end time, node progress percentage, node document set and node review record.
[0012] Based on the process template information, a monitoring process is established using the Flowable process engine.
[0013] Obtain the progress data of the current process node and update the monitoring progress bar based on the progress data. The progress data includes the node start time, node completion time, document submission status, and approval time.
[0014] In some embodiments, the following steps are also included:
[0015] The project documents for each process node are obtained through the interface of the MinIO high-performance distributed object storage system, and corresponding attributes are bound to the project documents obtained for each process node. The attributes include the project to which the document belongs, the process node, the person in charge, and the timestamp.
[0016] In some embodiments, the following steps are also included:
[0017] When project documents are uploaded, if corresponding custom tags are received, the project documents will be automatically tagged with the corresponding tags.
[0018] In some embodiments, the following steps are also included:
[0019] Based on the business system's permission framework, assign corresponding project document operation permissions to different roles.
[0020] In some embodiments, the following steps are also included:
[0021] When the current process node receives an edit to the project document, it retains the modified project document as well as historical versions of the project document.
[0022] In some embodiments, the following steps are also included:
[0023] The acquired progress data is compared with a preset threshold, and a reminder message is issued when a deviation occurs.
[0024] In some embodiments, issuing a reminder message when a deviation occurs specifically includes the following steps:
[0025] Based on the deviation procedure, a reminder message is sent to the corresponding personnel.
[0026] In some embodiments, the following steps are also included:
[0027] The monitoring process is displayed on a visual interface, and the completion progress of each process node is marked with different colors.
[0028] In some embodiments, the following steps are also included:
[0029] Obtain full-process data for historical and current projects;
[0030] Analysis reports are generated based on the acquired data from the entire process and displayed on a visual interface.
[0031] Another technical solution is also provided: a storage medium storing a computer program, which, when run by a processor, executes the steps in the above-described method for full-process progress control of communication engineering construction projects.
[0032] Unlike existing technologies, the above technical solution obtains the process template information of the current communication construction project through JSON template definition. The process template information includes project type, project name, project version, process node set, and process review records, forming the overall structure of the process template. The process node set includes node number, node name, start time, end time, node progress percentage, node document set, and node review records, forming the overall structure of the process nodes. The obtained process template information is converted into a monitoring process through the Flowable process engine to achieve full-process progress control of the current communication construction project. During the control process, the progress data of the current process node is obtained, and the monitoring process is updated based on the obtained progress data. By combining JSON template definition and Flowable process engine driving, monitoring of each node of the communication construction project can be achieved without manual progress coordination, manual summarization, and hierarchical reporting. Timely updates to process progress are possible, enabling real-time information sharing and efficient collaboration.
[0033] The above description of the invention is merely an overview of the technical solution of this application. In order to enable those skilled in the art to better understand the technical solution of this application and to implement it based on the description and drawings, and to make the above-mentioned objectives and other objectives, features and advantages of this application easier to understand, the following description is provided in conjunction with the specific embodiments and drawings of this application. Attached Figure Description
[0034] The accompanying drawings are only used to illustrate the principles, implementation methods, applications, features, and effects of specific embodiments of this application and other related content, and should not be considered as limitations on this application.
[0035] In the accompanying drawings of the instruction manual:
[0036] Figure 1 A flowchart illustrating the full-process progress control method for communication engineering construction projects described in this embodiment;
[0037] Figure 2 This is another flowchart illustrating the full-process progress control method for communication engineering construction projects described in the specific implementation method.
[0038] Figure 3 This is an example of the overall structure of the process template described in the specific implementation method;
[0039] Figure 4 This is an example of the detailed structure of the process node described in a specific implementation method;
[0040] Figure 5 This is a structural diagram illustrating the entire process nodes of a construction project containing hidden works, as described in a specific implementation method;
[0041] Figure 6 This is a schematic diagram of the structure of the storage medium described in a specific embodiment.
[0042] The reference numerals used in the above figures are explained as follows:
[0043] 610. Storage medium,
[0044] 620. Processor. Detailed Implementation
[0045] To illustrate the possible application scenarios, technical principles, implementable specific solutions, and achievable objectives and effects of this application in detail, the following description, in conjunction with the listed specific embodiments and accompanying drawings, provides a detailed explanation. The embodiments described herein are merely illustrative of the technical solutions of this application and are therefore intended to limit the scope of protection of this application.
[0046] In this document, the term "embodiment" means that a specific feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The term "embodiment" appearing in various places throughout the specification does not necessarily refer to the same embodiment, nor does it specifically limit its independence or connection with other embodiments. In principle, in this application, as long as there are no technical contradictions or conflicts, the technical features mentioned in each embodiment can be combined in any way to form corresponding implementable technical solutions.
[0047] Unless otherwise defined, the technical terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains; the use of related terms herein is merely for the purpose of describing particular embodiments and is not intended to limit this application.
[0048] In the description of this application, the term "and / or" is used to describe the logical relationship between objects, indicating that three relationships can exist. For example, A and / or B means: A exists, B exists, and A and B exist simultaneously. Additionally, the character " / " in this document generally indicates that the preceding and following objects have an "or" logical relationship.
[0049] In this application, terms such as “first” and “second” are used only to distinguish one entity or operation from another, and do not necessarily require or imply any actual quantity, hierarchy or order relationship between these entities or operations.
[0050] Unless otherwise specified, the use of terms such as “comprising,” “including,” “having,” or other similar expressions in this application is intended to cover non-exclusive inclusion, which does not exclude the presence of additional elements in a process, method, or product that includes the stated elements, such that a process, method, or product that includes a list of elements may include not only those defined elements but also other elements not expressly listed, or elements inherent to such a process, method, or product.
[0051] As understood in the Examination Guidelines, in this application, expressions such as "greater than," "less than," and "exceeding" are understood to exclude the stated number; expressions such as "above," "below," and "within" are understood to include the stated number. Furthermore, in the description of the embodiments in this application, "multiple" means two or more (including two), and similar expressions related to "multiple" are also understood in this way, such as "multiple groups" and "multiple times," unless otherwise explicitly specified.
[0052] In the description of the embodiments of this application, the space-related expressions used, such as "center," "longitudinal," "lateral," "length," "width," "thickness," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "vertical," "top," "bottom," "inner," "outer," "clockwise," "counterclockwise," "axial," "radial," and "circumferential," indicate the orientation or positional relationship based on the orientation or positional relationship shown in the specific embodiments or drawings. They are only for the purpose of describing the specific embodiments of this application or for the reader's understanding, and do not indicate or imply that the device or component referred to must have a specific position, a specific orientation, or be constructed or operated in a specific orientation. Therefore, they should not be construed as limitations on the embodiments of this application.
[0053] Unless otherwise expressly specified or limited, the terms "installation," "connection," "linking," "fixing," and "setting," as used in the description of the embodiments of this application, should be interpreted broadly. For example, "connection" can be a fixed connection, a detachable connection, or an integral setting; it can be a mechanical connection, an electrical connection, or a communication connection; it can be a direct connection or an indirect connection through an intermediate medium; it can be the internal connection of two components or the interaction between two components. For those skilled in the art to which this application pertains, the specific meaning of the above terms in the embodiments of this application can be understood according to the specific circumstances.
[0054] Please see Figure 1 This embodiment provides a method for full-process progress control of communication engineering construction projects, including:
[0055] Step S110: Obtain the process template information for communication engineering construction projects through JSON template definition. The process template information includes project type, project name, project version, process node set and process review record. The process node set includes node information of process nodes. The node information includes node number, node name, start time, end time, node progress percentage, node document set and node review record.
[0056] Step S120: Based on the process template information, establish a monitoring process using the Flowable process engine;
[0057] Step S130: Obtain the progress data of the current process node and update the monitoring progress bar according to the progress data. The progress data includes the node start time, node completion time, document submission status, and approval time.
[0058] The process template information for the current communication construction project is obtained through JSON template definition. This template information includes project type, project name, project version, process node set, and process review records, forming the overall structure of the process template. The process node set includes node number, node name, start time, end time, node progress percentage, node document set, and node review records, forming the overall structure of the process nodes. The obtained process template information is then converted into a monitoring process using the Flowable process engine to achieve full-process progress control for the current communication construction project. During the control process, progress data for the current process node is acquired, and the monitoring process is updated based on this data. By combining JSON template definition and the Flowable process engine, monitoring of each node in the communication construction project is achieved without the need for manual progress coordination, manual summarization, and hierarchical reporting. Timely updates to process progress are possible, enabling real-time information sharing and efficient collaboration.
[0059] In some embodiments, the following steps are also included:
[0060] The project documents for each process node are obtained through the interface of the MinIO high-performance distributed object storage system, and corresponding attributes are bound to the project documents obtained for each process node. The attributes include the project to which the document belongs, the process node, the person in charge, and the timestamp.
[0061] A centralized document repository is built based on the MinIO high-performance distributed object storage system. All project documents generated at each process node (such as commencement reports, hidden works records, and completion documents) are automatically uploaded through the system interface, preventing files from being scattered. At the same time, each project document is automatically bound to its project, process node, responsible person, and timestamp when uploaded, ensuring that "the document is where the process goes" and achieving full traceability.
[0062] In some embodiments, the following steps are also included:
[0063] When project documents are uploaded, if corresponding custom tags are received, the project documents will be automatically tagged with the corresponding tags.
[0064] It supports adding custom tags to project documents (such as "Safety", "Six Essentials", "ISO", "Insurance Materials", etc.), facilitating quick searching and filtering by type, stage, responsible party, and other criteria. Among them, "Six Essentials" refers to the six essential measures for safety management at construction sites.
[0065] In some embodiments, the following steps are also included:
[0066] Based on the business system's permission framework, assign corresponding project document operation permissions to different roles.
[0067] By integrating with the business system's permission framework, control the viewing, downloading, or editing permissions of different roles for documents.
[0068] In some embodiments, the following steps are also included:
[0069] When the current process node receives an edit to the project document, it retains the modified project document as well as historical versions of the project document.
[0070] When the current process node receives an edit to the uploaded project document, the original historical version of the project document is retained to prevent accidental deletion or overwriting, thus meeting audit and compliance requirements.
[0071] In some embodiments, the following steps are also included:
[0072] The acquired progress data is compared with a preset threshold, and a reminder message is issued when a deviation occurs.
[0073] Configure progress control parameters, i.e., preset thresholds, for each node in the process template, such as planned start and end times, maximum allowable delay days, and key node completion rate, as monitoring benchmarks. Automatically collect actual progress data (such as node start / completion time, document submission status, and approval time) and dynamically compare it with the preset thresholds to identify deviations. When progress data deviates from the preset thresholds, an alert message is sent.
[0074] In some embodiments, issuing a reminder message when a deviation occurs specifically includes the following steps:
[0075] Based on the deviation procedure, a reminder message is sent to the corresponding personnel.
[0076] Different levels of alerts are triggered based on the severity of the deviation. Minor delays are notified to the project manager via in-site message or email; serious delays are automatically escalated to the production department head, engineering supervision department, or even higher-level managers.
[0077] In some embodiments, the following steps are also included:
[0078] The monitoring process is displayed on a visual interface, and the completion progress of each process node is marked with different colors.
[0079] By monitoring the process and displaying it on a visual interface, and using color to indicate the status of nodes in the flowchart interface (gray = not started, blue = in progress, green = completed, red = overdue), progress risks are made "clear at a glance," improving management response efficiency.
[0080] In some embodiments, the following steps are also included:
[0081] Obtain full-process data for historical and current projects;
[0082] Analysis reports are generated based on the acquired data from the entire process and displayed on a visual interface.
[0083] It automatically integrates historical and current project workflow data, including node time, approval rounds, document completeness rate, alarm count, and reasons for delays, and associates them with project attributes (type, region, scale, etc.). Then, it integrates the workflow data of historical and current projects to generate various analytical reports, such as "average node processing time trend," "critical path delay hotspot distribution," "ranking of document submission timeliness rates for each production department," and "top 10 high-frequency alarm nodes."
[0084] Please see Figure 2In some embodiments, a method for full-process progress control of communication engineering construction projects is provided. First, a process template is defined, and then process instances of the project are established based on the process template. During the flow of process instances, process documents are collected and progress is tracked and alarms are issued. After the process instance is completed, the data can be analyzed and statistically analyzed.
[0085] The process template definition is the foundation of this method. This method uses JSON to define the process template. The overall structure of the process template and the detailed structure of the process nodes are described in detail below.
[0086] The overall structure of the workflow template describes the template type (templateType), name (templateName), version (version), workflow node set (procNodes), workflow review records (procCheckRecords), and other information. The workflow review records document the workflow's review information (arranged in reverse chronological order), including the applicant reviewer ID (applyUserId), application review time (applyTime), reviewer ID (checkUserId), review result (checkRslt), review time (checkTime), and review description (checkDesc). Figure 3 This is an example of the overall structure of the process template.
[0087] Detailed Structure of a Process Node: The detailed structure of a process node is the process node set (procNodes) described above. Its information includes serial number, node name, start time, end time, node progress percentage (procPct), node document set (files), and node review records (nodeCheckRecords). The node document set (files) details the project documents (fileName) that need to be collected for this node. These documents are stored in the MinIO object storage engine (minioRef), and their attributes can be marked using tags. The node review records (nodeCheckRecords) record the review information for this node, and its structure is similar to the process review records (procCheckRecords) described above. Figure 4 This is a detailed structural example of a process node.
[0088] The flow and interaction of the process involves transforming the process template defined in the previous section into a monitoring process, which is achieved through the Flowable process engine technology.
[0089] For example, taking the full-process progress monitoring of a construction project including hidden works as an example, its full-process nodes are as follows: Figure 5 As shown.
[0090] Node 1: Pre-construction Preparation. This node requires the project manager to submit the following materials: Project Manager Authorization Letter, Team Member List (including operation certificates), Construction Organization Design Plan, Three-Level Training Materials, Personnel Insurance, Safety Production Responsibility Agreement, Confidentiality Agreement, Construction Personnel Entry Training Materials, Safety Technical Disclosure Record Form, Construction Project Safety Production Measures Fee Ledger, Labor Protection Supplies Requisition Materials, and Responsibility Agreement. This is a critical node requiring review by both the production department and the project supervision department. Upon approval, this node will turn green.
[0091] Node 2: Commencement of Work. This node requires the project manager to submit materials such as the "Commencement Report / Notification (including subcontractors)" and the "Equipment (Materials) Arrival Inspection Form." This is a critical node and requires review by both the production department and the engineering supervision department. If it is an ongoing node, it will be marked in blue.
[0092] Node 3: Concealed Works. This node requires the project manager to submit the following materials: "Concealed Works Acceptance Record," "Pre-shift, During-shift, and Post-shift Safety Inspection Checklist," "Weekly Safety Inspection Checklist," "Safety Production Meeting Records (Monthly Meetings)," "Personnel Insurance Review (Monthly Checklist)," and "On-site Construction Safety Inspection Penalty Checklist." This is a standard node and only requires review by the production department. If there is no starting node, it will be grayed out.
[0093] Node 4: Equipment / Materials Arrival and Acceptance. For this node, the project manager needs to submit the following materials: Logistics Documents, Arrival Confirmation Form, Unpacking and Acceptance Form, Pre-shift, During-shift, and Post-shift Safety Inspection Checklist, Weekly Safety Inspection Checklist, Safety Production Meeting Records (Monthly Meetings), Personnel Insurance Review (Monthly Checklist), and On-site Construction Safety Inspection and Penalty Form. This is a standard node and only requires review by the production department.
[0094] Node 5: Equipment Installation and Commissioning / Other Construction. This node requires the project manager to submit the following materials: Equipment Installation and Commissioning Report, Engineering Liaison Form, Engineering Change Request Form, Meeting Minutes, Construction Log, Weekly Work Report, Engineering Stoppage and Resumption Report, Rectification / Penalty Notice, Rectification Completion Verification Report, Communication Records, Project Delivery Certificate (Out-of-Town), Site Photos, Pre-Shift, During-Shift, and Post-Shift Safety Inspection Checklists, Weekly Safety Inspection Checklist, Safety Production Meeting Records (Monthly Meetings), Personnel Insurance Verification (Monthly Checklist), and On-Site Construction Safety Inspection Penalty Form. This is a standard node and only requires review by the production department.
[0095] Node 6: Completion. At this node, the project manager needs to submit materials such as the "Project Self-Inspection Report," "Completion Report," and "As-Built Documents." This is a critical node and requires review by both the production department and the engineering supervision department.
[0096] Node 7: Preliminary Acceptance. This node requires the project manager to submit materials such as the "Preliminary Acceptance Application Report," "Preliminary Acceptance Rectification Report," and "Preliminary Acceptance Report." This is a critical node and requires review by both the production department and the engineering supervision department.
[0097] Node 8: Submission for Review. At this node, the project manager needs to submit materials such as the "Project Settlement Report," "Settlement Application Form," "Reviewed Subcontract Settlement Documents," and "Submission Acceptance Form." This is a standard node and only requires review by the production department.
[0098] Node 9: Review and Approval. This node requires the project manager to submit a "Review and Approval Report." This is a standard node and only requires review by the production department.
[0099] Node 10: Trial Operation. This node requires the project manager to submit the "System Trial Operation Record Form (Trial Operation Report)". This is a standard node and only requires review by the production department.
[0100] Node 11: Final Acceptance. This node requires the project manager to submit the "Final Acceptance Application Form," "Final Acceptance Report," and "Equipment and Material Acceptance and Handover Form," among other materials. This is a critical node and requires review by both the production department and the engineering supervision department.
[0101] Node 12: Project Settlement. At this node, the project manager needs to submit materials such as "Engineering Financial Records and Vouchers," "Engineering Settlement Statement," and "Audit Report." This is a standard node and only requires review by the production department.
[0102] Node 13: Maintenance. This node requires the project manager to submit materials such as the "Warranty Expiration Quality Confirmation Form," "Customer Complaints and Handling Records," and "Warranty Records." This is a standard node and only requires review by the production department.
[0103] Node 14: Post-Project Evaluation. This node requires the project manager to submit the "Post-Project Evaluation Report". This is a standard node and only requires review by the production department.
[0104] Project document aggregation aims to solve problems such as scattered documents, version chaos, and difficulty in traceability in communication engineering construction projects. By integrating the MinIO distributed object storage system, it achieves centralized, structured, and tagged management of documents throughout the entire process. All node documents are automatically associated with project and process status, supporting access control, version retention, and efficient retrieval, ensuring the integrity, compliance, and auditability of the data.
[0105] Unified storage architecture: A centralized document repository is built based on the MinIO high-performance distributed object storage system. All files generated by process nodes (such as commencement reports, hidden works records, completion documents, etc.) are automatically uploaded through the system interface to avoid file scattering.
[0106] Structured association management: Each document is automatically bound to its project, process node, responsible person, and timestamp when uploaded, ensuring that "the document belongs to wherever the process goes" and achieving full traceability.
[0107] Multi-dimensional tag classification: Supports adding custom tags to documents (such as "Safety", "Six Essentials", "ISO", "Insurance Materials", etc.), facilitating quick searching and filtering by type, stage, responsible party, and other criteria. (Note: "Six Essentials" refers to the six essential measures for safety management at construction sites.)
[0108] Access Control and Version Control: In conjunction with the business system's access control framework, control the viewing, downloading, or editing permissions of different roles for documents; at the same time, retain historical versions to prevent accidental deletion or overwriting, and meet audit and compliance requirements.
[0109] Progress tracking and alerting are designed to enable dynamic monitoring of project progress and early warning of risks. By pre-setting alert thresholds in process templates and combining them with real-time data comparison, a tiered alert mechanism is automatically triggered. Leveraging visual status indicators and multi-channel notification strategies, it significantly improves the speed of anomaly response and the timeliness of control.
[0110] Threshold preset mechanism: Configure progress control parameters for each node in the process template, such as planned start and end time, maximum allowable delay days, and key node completion rate, as a monitoring benchmark.
[0111] Real-time progress comparison: The system automatically collects actual progress data (such as node start / completion time, document submission status, approval time) and dynamically compares it with preset thresholds to identify deviations.
[0112] Tiered alert strategy: Different levels of alerts are triggered based on the severity of the deviation. Minor delays are notified to the project manager via in-site message or email; serious delays are automatically escalated to notify the production department head, engineering supervision department, or even higher-level managers.
[0113] Visual status display: The flowchart interface uses colors to indicate the status of nodes (gray = not started, blue = in progress, green = completed, red = overdue), making progress risks "clear at a glance" and improving management response efficiency.
[0114] Data analysis and statistics focus on extracting and summarizing from historical project data, supporting process optimization and scientific decision-making through multi-dimensional aggregation analysis and visualization. The system automatically aggregates structured data from the entire process, forming intuitive and easy-to-understand statistical analysis charts, driving enterprise project management from "experience-driven" to "data-driven," and providing quantitative data to support leadership decision-making.
[0115] Multi-dimensional data aggregation: Automatically integrates historical and current project process data, including node time, approval rounds, document completeness rate, alarm count, reasons for delays, etc., and associates them with project attributes (type, region, scale, etc.).
[0116] Intelligent statistical reports: Supports the generation of various analytical reports, such as "average node processing time trend", "critical path delay hotspot distribution", "ranking of document submission timeliness rate of each production department", "top 10 high-frequency alarm nodes", etc.
[0117] Visualized dashboard presentation: The overall progress, health status, and bottlenecks are intuitively displayed on the management dashboard through charts, heat maps, dashboards, and other forms, assisting senior management in decision-making.
[0118] This solution is based on a configurable workflow template mechanism using JSON: It defines workflow templates that include node order, document requirements, approval rules, and alarm thresholds using structured JSON, supporting flexible customization based on project type (such as concealed works), enabling rapid workflow reuse and unified management. It also integrates the Flowable engine and MinIO's closed-loop management architecture: Flowable drives the flow of workflow instances and embeds multi-level approval logic, while automatically aggregating documents from each node to MinIO and tagging them; combined with real-time progress comparison and tiered alarms, it forms an integrated digital management closed loop of "template definition → instance creation → document aggregation → dynamic alarms → data analysis".
[0119] Compared to traditional methods of controlling construction progress in telecommunications engineering that rely on manual coordination, static planning, and decentralized management, this solution significantly improves the agility, collaboration, and intelligence of project management through IT system integration and process standardization. Specific advantages and effects are reflected in the following aspects:
[0120] 1. Achieve full-process digital closed-loop management: Through JSON template definition, Flowable process engine driving and MinIO document collection, connect the entire chain of planning, execution, documentation, early warning and analysis, and avoid information gaps caused by traditional manual coordination.
[0121] 2. Enhance progress response and risk control capabilities: Preset alarm thresholds in the process template, automatically trigger graded early warnings by combining real-time progress comparison, and quickly identify lagging nodes with visual status indicators, significantly enhancing dynamic adjustment capabilities.
[0122] 3. Supports data-driven continuous optimization: Statistical analysis and large-screen display based on multi-dimensional data of historical projects (such as node time consumption, alarm frequency, and document completeness rate) to accurately locate weak links in management and provide quantitative basis for process iteration and decision-making.
[0123] Please see Figure 6 A storage medium 610 stores a computer program, which, when executed by a processor 620, performs the following steps:
[0124] The process template information for communication engineering construction projects is obtained through JSON template definition. The process template information includes project type, project name, project version, process node set and process review record. The process node set includes node information of process nodes, including node number, node name, start time, end time, node progress percentage, node document set and node review record.
[0125] Based on the process template information, a monitoring process is established using the Flowable process engine.
[0126] Obtain the progress data of the current process node and update the monitoring progress bar based on the progress data. The progress data includes the node start time, node completion time, document submission status, and approval time.
[0127] The process template information for the current communication construction project is obtained through JSON template definition. This template information includes project type, project name, project version, process node set, and process review records, forming the overall structure of the process template. The process node set includes node number, node name, start time, end time, node progress percentage, node document set, and node review records, forming the overall structure of the process nodes. The obtained process template information is then converted into a monitoring process using the Flowable process engine to achieve full-process progress control for the current communication construction project. During the control process, progress data for the current process node is acquired, and the monitoring process is updated based on this data. By combining JSON template definition and the Flowable process engine, monitoring of each node in the communication construction project is achieved without the need for manual progress coordination, manual summarization, and hierarchical reporting. Timely updates to process progress are possible, enabling real-time information sharing and efficient collaboration.
[0128] In some embodiments, the following steps are also included:
[0129] The project documents for each process node are obtained through the interface of the MinIO high-performance distributed object storage system, and corresponding attributes are bound to the project documents obtained for each process node. The attributes include the project to which the document belongs, the process node, the person in charge, and the timestamp.
[0130] A centralized document repository is built based on the MinIO high-performance distributed object storage system. All project documents generated at each process node (such as commencement reports, hidden works records, and completion documents) are automatically uploaded through the system interface, preventing files from being scattered. At the same time, each project document is automatically bound to its project, process node, responsible person, and timestamp when uploaded, ensuring that "the document is where the process goes" and achieving full traceability.
[0131] In some embodiments, the following steps are also included:
[0132] When project documents are uploaded, if corresponding custom tags are received, the project documents will be automatically tagged with the corresponding tags.
[0133] It supports adding custom tags to project documents (such as "Safety", "Six Essentials", "ISO", "Insurance Materials", etc.), facilitating quick searching and filtering by type, stage, responsible party, and other criteria. Among them, "Six Essentials" refers to the six essential measures for safety management at construction sites.
[0134] In some embodiments, the following steps are also included:
[0135] Based on the business system's permission framework, assign corresponding project document operation permissions to different roles.
[0136] By integrating with the business system's permission framework, control the viewing, downloading, or editing permissions of different roles for documents.
[0137] In some embodiments, the following steps are also included:
[0138] When the current process node receives an edit to the project document, it retains the modified project document as well as historical versions of the project document.
[0139] When the current process node receives an edit to the uploaded project document, the original historical version of the project document is retained to prevent accidental deletion or overwriting, thus meeting audit and compliance requirements.
[0140] In some embodiments, the following steps are also included:
[0141] The acquired progress data is compared with a preset threshold, and a reminder message is issued when a deviation occurs.
[0142] Configure progress control parameters, i.e., preset thresholds, for each node in the process template, such as planned start and end times, maximum allowable delay days, and key node completion rate, as monitoring benchmarks. Automatically collect actual progress data (such as node start / completion time, document submission status, and approval time) and dynamically compare it with the preset thresholds to identify deviations. When progress data deviates from the preset thresholds, an alert message is sent.
[0143] In some embodiments, issuing a reminder message when a deviation occurs specifically includes the following steps:
[0144] Based on the deviation procedure, a reminder message is sent to the corresponding personnel.
[0145] Different levels of alerts are triggered based on the severity of the deviation. Minor delays are notified to the project manager via in-site message or email; serious delays are automatically escalated to the production department head, engineering supervision department, or even higher-level managers.
[0146] In some embodiments, the following steps are also included:
[0147] The monitoring process is displayed on a visual interface, and the completion progress of each process node is marked with different colors.
[0148] By monitoring the process and displaying it on a visual interface, and using color to indicate the status of nodes in the flowchart interface (gray = not started, blue = in progress, green = completed, red = overdue), progress risks are made "clear at a glance," improving management response efficiency.
[0149] In some embodiments, the following steps are also included:
[0150] Obtain full-process data for historical and current projects;
[0151] Analysis reports are generated based on the acquired data from the entire process and displayed on a visual interface.
[0152] It automatically integrates historical and current project workflow data, including node time, approval rounds, document completeness rate, alarm count, and reasons for delays, and associates them with project attributes (type, region, scale, etc.). Then, it integrates the workflow data of historical and current projects to generate various analytical reports, such as "average node processing time trend," "critical path delay hotspot distribution," "ranking of document submission timeliness rates for each production department," and "top 10 high-frequency alarm nodes."
[0153] Finally, it should be noted that although the above embodiments have been described in the text and drawings of this application, this should not limit the scope of patent protection of this application. Any technical solutions that are based on the essential concept of this application and utilize the content described in the text and drawings of this application, resulting in equivalent structural or procedural substitutions or modifications, as well as the direct or indirect application of the technical solutions of the above embodiments to other related technical fields, are all included within the scope of patent protection of this application.
Claims
1. A method for full-process progress control of communication engineering construction projects, characterized in that, include: The process template information for communication engineering construction projects is obtained through JSON template definition. The process template information includes project type, project name, project version, process node set and process review record. The process node set includes node information of process nodes, including node number, node name, start time, end time, node progress percentage, node document set and node review record. Based on the process template information, a monitoring process is established using the Flowable process engine. Obtain the progress data of the current process node and update the monitoring progress bar based on the progress data. The progress data includes the node start time, node completion time, document submission status, and approval time.
2. The method for full-process progress control of communication engineering construction projects according to claim 1, characterized in that, It also includes the following steps: The project documents for each process node are obtained through the interface of the MinIO high-performance distributed object storage system, and corresponding attributes are bound to the project documents obtained for each process node. The attributes include the project to which the document belongs, the process node, the person in charge, and the timestamp.
3. The method for full-process progress control of communication engineering construction projects according to claim 2, characterized in that, It also includes the following steps: When project documents are uploaded, if corresponding custom tags are received, the project documents will be automatically tagged with the corresponding tags.
4. The method for full-process progress control of communication engineering construction projects according to claim 1, characterized in that, It also includes the following steps: Based on the business system's permission framework, assign corresponding project document operation permissions to different roles.
5. The method for full-process progress control of communication engineering construction projects according to claim 1, characterized in that, It also includes the following steps: When the current process node receives an edit to the project document, it retains the modified project document as well as historical versions of the project document.
6. The method for full-process progress control of communication engineering construction projects according to claim 1, characterized in that, It also includes the following steps: The system compares the actual progress data with a preset threshold, and issues a reminder when a deviation occurs.
7. The method for full-process progress control of communication engineering construction projects according to claim 6, characterized in that, The step of issuing a reminder message when a deviation occurs includes the following steps: Based on the deviation procedure, a reminder message is sent to the corresponding personnel.
8. The method for full-process progress control of communication engineering construction projects according to claim 1, characterized in that, It also includes the following steps: The monitoring process is displayed on a visual interface, and the completion progress of each process node is marked with different colors.
9. The method for full-process progress control of communication engineering construction projects according to claim 1, characterized in that, It also includes the following steps: Obtain full-process data for historical and current projects; Analysis reports are generated based on the acquired data from the entire process and displayed on a visual interface.
10. A storage medium storing a computer program, characterized in that, When the computer program is run by the processor, it executes the steps in the full-process progress control method for communication engineering construction projects as described in any one of claims 1-9.