A method and system for automatically generating a maintenance cross diagram of a hydropower plant

Abstract

This invention discloses an automatic generation method and system for Gantt charts of hydropower plant maintenance, relating to the field of hydropower plant maintenance technology. The method includes constructing a maintenance data model; setting relative start and end times and Gantt chart identifiers; identifying maintenance procedures with Gantt chart identifiers and extracting the corresponding procedure content and relative start and end times; converting the relative start and end times into specific natural dates based on the actual start and end times of the maintenance items; performing consistency and density calculations on the converted maintenance procedure time data and determining thresholds for each; and generating and outputting the maintenance Gantt chart if the thresholds are passed. This invention achieves automatic generation of maintenance Gantt charts by structurally modeling maintenance project data and introducing relative time conversion and consistency / density threshold determination mechanisms, avoiding errors from manual drawing and improving the accuracy, rationality, and management efficiency of maintenance plans.

Description

Technical Field

[0001] This invention relates to the field of hydropower plant maintenance technology, and in particular to a method and system for automatically generating Gantt charts for hydropower plant maintenance. Background Technology

[0002] In the maintenance management of hydropower plants, it is usually necessary to prepare maintenance Gantt charts to show the time arrangement of each maintenance procedure within the maintenance cycle, so that managers can grasp the maintenance progress, identify peak work periods, and coordinate resources. In the current technology, maintenance Gantt charts are mostly generated manually. Usually, staff members check the start and end times of each maintenance procedure according to the contents of the maintenance document package, and then organize and draw them using drawing software or spreadsheet tools.

[0003] However, during maintenance, the maintenance projects involve many types of equipment and a large number of procedures. The time information of the procedures is scattered in different maintenance documents, making the manual sorting process cumbersome and prone to omissions or duplications. Moreover, the time configuration of maintenance procedures is often filled in directly with natural dates. When the maintenance project cycle is adjusted, all procedure times need to be manually recalculated and corrected, which is labor-intensive and prone to errors. Furthermore, the existing Gantt chart generation process lacks quantitative verification of the rationality of maintenance procedure times and cannot identify problems such as incomplete or overly concentrated procedure time distribution before generation. This can easily lead to the generation of plans that do not match the actual maintenance capacity. At the same time, the generated Gantt chart results are mostly at the display level and lack data-based generation constraints, making it difficult to provide effective support for the scientific nature of maintenance plans. Therefore, we propose an automatic generation method and system for hydropower plant maintenance Gantt charts. Summary of the Invention

[0004] The purpose of this invention is to provide an automatic generation method and system for maintenance Gantt charts in hydropower plants, in order to solve the problems mentioned in the background art.

[0005] To achieve the above objectives, the present invention provides the following technical solution: a method for automatically generating a Gantt chart for hydropower plant maintenance, comprising the following steps:

[0006] Step 1: Configure the hydropower plant maintenance project data in a structured manner to build a maintenance data model that includes maintenance projects, maintenance document packages, and maintenance procedures;

[0007] Step 2: Set the relative start and end times for each maintenance process in the maintenance document package, and set the Gantt chart labels for the maintenance processes that need to participate in the generation of the Gantt chart;

[0008] Step 3: Identify the maintenance procedures marked with Gantt chart symbols, and extract the corresponding procedure content and relative start and end times;

[0009] Step 4: Based on the actual start and end times of the maintenance project, convert the relative start and end times into specific calendar dates;

[0010] Step 5: Perform consistency calculation and density calculation on the converted maintenance process time data, and determine the threshold for each.

[0011] Step 6: If the threshold determination is passed, generate and output the maintenance Gantt chart.

[0012] Preferably, step 1 includes:

[0013] Construct a basic information structure for maintenance projects to describe the overall scope of a hydropower plant's maintenance tasks. The basic information for maintenance projects includes at least the project name, project number, maintenance type, and the planned start and end dates of the project.

[0014] Multiple maintenance document package data units are established under each maintenance item to classify and manage the maintenance content of different equipment, systems or maintenance areas.

[0015] Establish a corresponding maintenance process data structure in each maintenance file package. The maintenance process data structure shall include at least the process name, process sequence number, process description information, and time-related attribute fields.

[0016] By using standardized data fields, maintenance projects, maintenance document packages, and maintenance procedures are linked and bound together to form a maintenance data model with clear hierarchy and well-defined relationships.

[0017] Preferably, step 2 includes:

[0018] Using the overall cycle of the maintenance project as a time reference benchmark, a corresponding relative start and end time interval is set for each maintenance procedure.

[0019] The relative start and end times are configured with the maintenance project start date as day 1, using the format "day N to day M" to describe the time position of the maintenance process within the project cycle.

[0020] During the configuration of maintenance procedures, Gantt chart labels are set for maintenance procedures that need to be displayed in the Gantt chart to distinguish between procedures that participate in the generation of the Gantt chart and those that do not.

[0021] The relative start and end times and Gantt chart identifiers are stored as attribute information of the maintenance process in the maintenance data model.

[0022] Preferably, step 3 includes:

[0023] Perform a comprehensive scan of all maintenance procedures in the maintenance document package;

[0024] Based on the preset Gantt chart identification rules, the maintenance procedures with Gantt chart identification are selected from all maintenance procedures.

[0025] Extract the process content information and relative start and end time information corresponding to the maintenance processes marked with Gantt charts;

[0026] The extracted process details are associated and encapsulated with relative start and end times to form a process time dataset for generating Gantt charts.

[0027] Preferably, step 4 includes:

[0028] Obtain the planned start date and planned end date of the maintenance project, and set the planned start date of the maintenance project as the time conversion base;

[0029] Calculate the corresponding natural date offset based on the relative start and end times of the maintenance procedures;

[0030] The natural date offset is converted to the planned start date of the maintenance project to generate the actual natural start and end dates corresponding to the maintenance process;

[0031] The generated start and end dates are verified against the planned end date of the maintenance project to ensure that the converted process time is within the maintenance project cycle.

[0032] Preferably, the calculation of the natural date offset includes:

[0033] The planned start date of the maintenance project is used as the time base for Day 1;

[0034] Calculate the natural date offset based on the day value corresponding to the relative start and end times of the maintenance process;

[0035] When the calculated start and end dates of the maintenance procedures exceed the planned end date of the maintenance project, the excess portion is either truncated or an anomaly marker is generated.

[0036] The natural start and end dates of the processed maintenance procedures will be used as input data for subsequent consistency and density calculations.

[0037] Preferably, step 5 includes:

[0038] Based on the natural start and end dates of the maintenance procedures, the execution time consistency of the maintenance procedures involved in the generation of the Gantt chart is calculated to assess the time coverage of the maintenance procedures.

[0039] Based on the number of maintenance procedures and the length of the maintenance project cycle, the time density of maintenance procedures is calculated to assess the degree of concentration of maintenance procedures within the project cycle.

[0040] The consistency calculation results are compared with the preset consistency threshold, and the density calculation results are compared with the preset density threshold.

[0041] The decision information is generated based on the threshold comparison results to indicate whether the process of generating the Gantt chart is allowed.

[0042] Preferably, the formula for calculating the consistency between the time distribution of maintenance procedures and the cycle of maintenance projects is as follows:

[0043] ;

[0044] Among them, D i start D represents the actual start date of the i-th maintenance procedure. i end Let D be the actual end date of the i-th maintenance procedure, n be the number of maintenance procedures involved in generating the Gantt chart, and D be the number of maintenance procedures involved in generating the Gantt chart. proj C represents the total cycle days of the maintenance project, and C is the consistency index of maintenance process time.

[0045] When C < Tc, the time distribution of the maintenance process is determined to be incomplete, and the generation of the Gantt chart is prevented.

[0046] When C≥Tc, proceed to the next processing step;

[0047] The value of Tc ranges from 0.7 to 0.9.

[0048] The density calculation formula used to assess the concentration of maintenance procedures during the maintenance cycle is as follows:

[0049] ;

[0050] Where n is the number of maintenance procedures involved in generating the Gantt chart, and D proj K represents the total cycle days of the maintenance project, and K is the time density index of the maintenance process.

[0051] When K > Tk, the maintenance process is determined to be concentrated, and a high load warning is generated.

[0052] When K≤Tk, it is permissible to generate a Gantt chart based on the original data;

[0053] The value of Tk ranges from 0.3 to 0.6.

[0054] Preferably, step 6 includes:

[0055] When both the consistency calculation result and the density calculation result meet the corresponding threshold conditions, the Gantt chart generation process is triggered.

[0056] The maintenance procedures are arranged horizontally by time according to their natural start and end dates.

[0057] Fill the maintenance procedures and corresponding time intervals into the Gantt chart structure to form a complete maintenance Gantt chart.

[0058] The generated maintenance Gantt chart is output for system display, file download, or maintenance data archiving.

[0059] An automatic generation system for maintenance Gantt charts of hydropower plants, implementing the automatic generation method for maintenance Gantt charts of hydropower plants described in any of the above-mentioned embodiments, includes:

[0060] The maintenance data structuring module is used to construct data models of maintenance projects, maintenance document packages, and maintenance procedures.

[0061] The process time configuration module is used to configure the relative start and end times of the maintenance process and the Gantt chart identifiers.

[0062] The process identification and extraction module is used to identify and extract maintenance processes marked with Gantt chart symbols.

[0063] A date conversion module, which is used to convert relative start and end times into specific natural dates;

[0064] A consistency and density analysis module, which performs consistency calculations and density calculations and determines thresholds;

[0065] A Gantt chart generation module is used to generate a maintenance Gantt chart after the threshold determination is passed.

[0066] The technical effects and advantages of this invention are as follows:

[0067] This invention achieves automatic generation of maintenance Gantt charts by structuring and modeling hydropower plant maintenance project data and introducing a threshold judgment mechanism that combines relative time configuration, automatic conversion of natural dates, and consistency and density calculations. By structuring maintenance projects, maintenance document packages, and maintenance procedures, the time information of maintenance procedures has a unified and standardized expression at the data level, reducing the workload and error risk of manual data processing. Maintenance procedures are described using relative start and end times and automatically converted to natural dates during the generation stage, enabling overall linkage updates of procedure times when maintenance project cycles are adjusted, improving the flexibility of maintenance plan maintenance. Consistency and density calculations are introduced before Gantt chart generation, and threshold judgments are used to quantitatively analyze the completeness and concentration of maintenance procedure times, effectively avoiding the direct generation of Gantt charts when maintenance plans are clearly unreasonable, thereby improving the executability and reliability of maintenance plans. Finally, after the threshold judgment is passed, the maintenance Gantt chart is automatically generated and output, realizing the transformation of maintenance Gantt charts from manual drawing to automatic generation, improving the efficiency and standardization of maintenance management. Attached Figure Description

[0068] The accompanying drawings are provided to further illustrate the invention and form part of the specification. They are used together with the embodiments of the invention to explain the invention, but do not constitute a limitation thereof. In the drawings:

[0069] Figure 1 This is a schematic diagram of the method flow of the present invention;

[0070] Figure 2 This is a schematic diagram of the consistency calculation process of the present invention;

[0071] Figure 3 This is a schematic diagram of the density calculation process of the present invention. Detailed Implementation

[0072] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0073] This invention provides, for example Figures 1-3 The method for automatically generating a Gantt chart for hydropower plant maintenance, as shown, includes the following steps:

[0074] Step 1: Configure the hydropower plant maintenance project data in a structured manner to build a maintenance data model that includes maintenance projects, maintenance document packages, and maintenance procedures;

[0075] Step 1 includes:

[0076] Construct a basic information structure for maintenance projects to describe the overall scope of maintenance tasks at a hydropower plant. The basic information for maintenance projects should include at least the project name, project number, maintenance type, and the planned start and end dates of the project.

[0077] Multiple maintenance document package data units are established under each maintenance item to classify and manage the maintenance content of different equipment, systems or maintenance areas.

[0078] Establish a corresponding maintenance process data structure in each maintenance file package. The maintenance process data structure shall include at least the process name, process sequence number, process description information, and time-related attribute fields.

[0079] By using unified data field specifications, maintenance projects, maintenance document packages, and maintenance procedures are associated and bound together to form a maintenance data model with clear hierarchy and well-defined relationships.

[0080] In a specific embodiment of the present invention, step 1 is used to perform a unified structured configuration of the relevant data of the hydropower plant maintenance project, so as to provide a standardized and reliable data foundation for the automatic generation of the subsequent maintenance Gantt chart.

[0081] In practice, the first step is to construct the basic information structure of the maintenance project. By centrally configuring key information such as project name, project number, maintenance type, and planned start and end dates, the overall scope and time boundaries of a maintenance task are clarified, ensuring that all subsequent maintenance data can be managed and calculated within a unified project cycle.

[0082] Based on this, multiple maintenance document package data units are established under each maintenance project. Different maintenance document packages correspond to different equipment, systems or maintenance areas to achieve classified management of complex maintenance content. Through the hierarchical setting of maintenance document packages, various maintenance contents have a clear belonging relationship at the data level, avoiding data mixing between different maintenance objects.

[0083] Furthermore, a corresponding maintenance procedure data structure is established in each maintenance file package to provide a detailed description of the specific maintenance operation. The maintenance procedure data structure includes at least the procedure name, procedure sequence number, procedure description information, and time-related attribute fields, so that each maintenance procedure has a clear data expression in terms of logical sequence, content description, and time arrangement.

[0084] Finally, by using a unified data field specification, maintenance projects, maintenance document packages and maintenance procedures are associated and bound together to form a top-down, hierarchical and logically consistent maintenance data model, which provides stable data support for subsequent process time conversion, threshold calculation and Gantt chart generation.

[0085] Through the implementation of step 1 above, this invention achieves systematic and structured management of hydropower plant maintenance project data, forming a clear data hierarchy and correlation between maintenance projects, maintenance document packages, and maintenance procedures. This avoids the omissions, duplications, or logical confusion that easily occur when manually compiling maintenance data in the traditional way. At the same time, since the time attributes of maintenance procedures are pre-standardized and configured in the data model, there is no need to manually sort out the original maintenance data during the subsequent Gantt chart generation process. This significantly reduces the complexity of Gantt chart generation, improves the accuracy and consistency of data processing, and provides a reliable foundation for the visualization of maintenance plans and management decisions.

[0086] Step 2: Set the relative start and end times for each maintenance process in the maintenance document package, and set the Gantt chart labels for the maintenance processes that need to participate in the generation of the Gantt chart;

[0087] Step 2 includes:

[0088] Using the overall cycle of the maintenance project as a time reference benchmark, a corresponding relative start and end time interval is set for each maintenance procedure.

[0089] The relative start and end times are configured with the start date of the maintenance project as day 1, using the format "day N to day M" to describe the time position of the maintenance procedure within the project cycle.

[0090] During the configuration of maintenance procedures, Gantt chart labels are set for maintenance procedures that need to be displayed in the Gantt chart to distinguish between procedures that participate in the generation of the Gantt chart and those that do not.

[0091] The relative start and end times and Gantt chart identifiers are stored as attribute information of the maintenance process in the maintenance data model;

[0092] In a specific embodiment of the present invention, step 2 is used to configure the time attribute and display attribute of the maintenance procedures in the maintenance document package, so as to realize the unified expression and selective display of the maintenance procedures within the maintenance cycle.

[0093] In practice, the overall cycle of the maintenance project is used as a unified time reference benchmark. The planned start date of the maintenance project is set as day 1 to avoid time calculation deviations caused by different start dates for different maintenance procedures.

[0094] Based on this, a corresponding relative start and end time interval is set for each maintenance procedure. The relative start and end time is configured in the form of "day N to day M" to describe the time position of the maintenance procedure within the entire maintenance project cycle. By configuring the relative time, the time expression of the maintenance procedure does not depend on the specific natural date, which facilitates overall linkage update when the maintenance project time is adjusted.

[0095] During the configuration of maintenance procedures, Gantt chart labels are set for maintenance procedures that need to be displayed in the Gantt chart. This is used to distinguish between key maintenance procedures that participate in the generation of the Gantt chart and auxiliary procedures that are only used for record management and do not need to be displayed. By setting the Gantt chart labels, the system can quickly identify the target procedures in the subsequent processing and avoid irrelevant procedures from interfering with the display effect of the Gantt chart.

[0096] Finally, the relative start and end times and the Gantt chart identifiers are stored as attribute information of the maintenance process in the maintenance data model, thereby ensuring that the time information and display control information of the maintenance process are consistent and traceable at the data level.

[0097] By implementing step 2, the present invention achieves the standardized expression of maintenance process time information, enabling each maintenance process to have a unified time reference system within the same maintenance project cycle, thus avoiding the problems of misalignment and repeated verification that easily occur when manually filling in process time using natural dates.

[0098] Meanwhile, by using Gantt charts to filter and control maintenance procedures, the Gantt charts only present procedures that are of practical significance to maintenance plan management, thereby improving the readability and practicality of the Gantt charts and providing clear and reliable data input conditions for the subsequent automatic generation of Gantt charts.

[0099] Step 3: Identify the maintenance procedures marked with Gantt chart symbols, and extract the corresponding procedure content and relative start and end times;

[0100] Step 3 includes:

[0101] Perform a comprehensive scan of all maintenance procedures in the maintenance document package;

[0102] Based on the preset Gantt chart identification rules, the maintenance procedures with Gantt chart identification are selected from all maintenance procedures.

[0103] Extract the process content information and relative start and end time information corresponding to the maintenance processes marked with Gantt charts;

[0104] The extracted process content is associated and encapsulated with relative start and end times to form a process time dataset for generating Gantt charts;

[0105] In a specific embodiment of the present invention, step 3 is used to automatically identify the maintenance procedures that need to participate in the generation of the Gantt chart from the maintenance document package, and extract the corresponding procedure content and timing information to form standardized data input;

[0106] In practice, the system first scans all maintenance procedures contained in the maintenance document package to ensure that all configured maintenance procedures are included in the identification range, thereby avoiding omissions caused by manual screening.

[0107] Based on the traversal scan, the system filters all maintenance procedures according to the pre-set Gantt chart identification rules, and only identifies maintenance procedures with Gantt chart identification as target procedures. By determining the Gantt chart identification, the system can accurately distinguish between key maintenance procedures used for Gantt chart display and non-display procedures used only for process recording or management.

[0108] Subsequently, for the identified maintenance procedures marked with Gantt charts, their corresponding procedure content information and relative start and end time information are extracted. The procedure content information is used to describe the specific maintenance operation items, and the relative start and end time information is used to characterize the time position of the procedure within the maintenance project cycle.

[0109] Finally, the extracted process content is associated with and encapsulated with the relative start and end times to form a process time dataset with a unified structure, which is used for subsequent process time conversion, threshold calculation and Gantt chart generation and other processing steps.

[0110] By implementing step 3, the present invention achieves automatic identification and accurate extraction of maintenance procedures, avoiding the problems of large workload and high error rate caused by relying on manual search and screening of maintenance procedures in the traditional method.

[0111] Meanwhile, by uniformly screening maintenance procedures through Gantt chart labeling rules, the data entering the Gantt chart generation process has clear business significance, ensuring the accuracy and consistency of Gantt chart data sources and providing a reliable data foundation for the subsequent automatic generation and standardized display of Gantt charts.

[0112] Step 4: Based on the actual start and end times of the maintenance project, convert the relative start and end times into specific calendar dates;

[0113] Step 4 includes:

[0114] Obtain the planned start date and planned end date of the maintenance project, and set the planned start date of the maintenance project as the time conversion base;

[0115] Calculate the corresponding natural date offset based on the relative start and end times of the maintenance procedures;

[0116] Convert the natural date offset to the planned start date of the maintenance project to generate the actual natural start and end dates corresponding to the maintenance procedures;

[0117] The generated start and end dates are verified against the planned end date of the maintenance project to ensure that the converted process time is within the maintenance project cycle.

[0118] The calculation of the natural date offset includes:

[0119] The planned start date of the maintenance project is used as the time base for Day 1;

[0120] Calculate the natural date offset based on the day value corresponding to the relative start and end times of the maintenance process;

[0121] When the calculated start and end dates of the maintenance procedures exceed the planned end date of the maintenance project, the excess portion is either truncated or an anomaly marker is generated.

[0122] The natural start and end dates of the processed maintenance procedures will be used as input data for subsequent consistency and density calculations.

[0123] In a specific embodiment of the present invention, step 4 is used to convert the relative start and end times configured in the maintenance process into specific natural dates, so as to achieve accurate positioning of the maintenance process on the actual timeline.

[0124] In practice, the system first obtains the planned start date and planned end date of the maintenance project, and sets the planned start date of the maintenance project as the unified benchmark for time conversion, thereby providing a consistent time reference for all maintenance procedures.

[0125] Based on this, for each maintenance procedure, the system calculates the corresponding natural date offset according to the time expression of "day N to day M". The planned start date of the maintenance project is used as the first day time base. By parsing the corresponding day values ​​in the relative start and end times, the time offset relationship of each maintenance procedure relative to the project start point is determined.

[0126] Subsequently, the system converts the natural date offset with the planned start date of the maintenance project to generate the actual natural start and end dates corresponding to the maintenance process, so that the maintenance process, which was originally described based on relative time, can be mapped to a specific calendar date range.

[0127] After completing the natural date conversion, the system further verifies the natural start and end dates of the generated maintenance procedures with the planned end date of the maintenance project to determine whether the procedure time exceeds the overall cycle range of the maintenance project.

[0128] When the system detects that the natural start and end dates of a certain maintenance procedure exceed the planned end date of the maintenance project, it will truncate the excess part or generate an abnormal mark for the maintenance procedure to indicate that the time configuration of the procedure is unreasonable. The natural start and end dates of the maintenance procedure after truncation or marking are uniformly used as input data for subsequent consistency calculation and density calculation, thereby ensuring that the subsequent calculation process is based on legal and standardized time data.

[0129] By implementing step 4, the present invention realizes the automatic and unified conversion of maintenance process time from relative description to natural date, avoiding the calculation errors and inconsistencies that are easy to occur when manually converting process time to natural date one by one in the traditional way.

[0130] Meanwhile, by verifying the periodic range of the conversion results and performing truncation or marking when anomalies are found, it is ensured that the data entering subsequent consistency calculations and density calculations are all within the effective time range of the maintenance project, thereby improving the reliability and controllability of time data.

[0131] The above processing method not only ensures the accuracy of the maintenance Gantt chart in the time dimension, but also provides a stable data foundation for subsequent analysis and judgment based on time data, thereby improving the overall accuracy and engineering practicality of the automatic generation process of the Gantt chart.

[0132] Step 5: Perform consistency calculation and density calculation on the converted maintenance process time data, and determine the threshold for each.

[0133] Step 5 includes:

[0134] Based on the natural start and end dates of the maintenance procedures, the execution time consistency of the maintenance procedures involved in the generation of the Gantt chart is calculated to assess the time coverage of the maintenance procedures.

[0135] Based on the number of maintenance procedures and the length of the maintenance project cycle, the time density of maintenance procedures is calculated to assess the degree of concentration of maintenance procedures within the project cycle.

[0136] The consistency calculation results are compared with the preset consistency threshold, and the density calculation results are compared with the preset density threshold.

[0137] The decision information is generated based on the threshold comparison results to indicate whether the process of generating the Gantt chart is allowed.

[0138] The formula for calculating the consistency between the time distribution of maintenance procedures and the cycle of maintenance projects is as follows:

[0139] ;

[0140] Among them, D istart D represents the actual start date of the i-th maintenance procedure. i end Let D be the actual end date of the i-th maintenance procedure, n be the number of maintenance procedures involved in generating the Gantt chart, and D be the number of maintenance procedures involved in generating the Gantt chart. proj C represents the total cycle days of the maintenance project, and C is the consistency index of maintenance process time.

[0141] When C < Tc, the time distribution of the maintenance process is determined to be incomplete, and the generation of the Gantt chart is prevented.

[0142] When C≥Tc, proceed to the next processing step;

[0143] The value of Tc ranges from 0.7 to 0.9. The consistency index C essentially measures the degree to which the maintenance process time covers the project cycle. The maintenance summary of hydropower plants does not involve work every day. Preparation period, acceptance period and buffer period are allowed. Therefore, C is not required to be 1. Instead, a certain proportion of non-operation time is allowed. Common non-operation time includes: equipment cooling or heating waiting, safety isolation and reset, material allocation and personnel handover. In engineering statistics, this type of time usually accounts for 10%-30%, which corresponds to the lower limit of Tc of 0.7. When the maintenance is a planned major overhaul or centralized maintenance, the process coverage requirement is high, and Tc tends to be 0.8-0.9. When the maintenance is a partial maintenance or technical renovation maintenance, Tc tends to be 0.7-0.9.

[0144] The density calculation formula used to assess the concentration of maintenance procedures during the maintenance cycle is as follows:

[0145] ;

[0146] Where n is the number of maintenance procedures involved in generating the Gantt chart, and D proj K represents the total cycle days of the maintenance project, and K is the time density index of the maintenance process.

[0147] When K > Tk, the maintenance process is determined to be concentrated, and a high load warning is generated.

[0148] When K≤Tk, it is permissible to generate a Gantt chart based on the original data;

[0149] The value of Tk ranges from 0.3 to 0.6, and the density index K represents the average number of processes handled per day. In hydropower plant maintenance, excessive density indicates personnel conflicts, conflicts with hoisting and power outage windows, and overlapping safety risks. In engineering projects, 0.3-0.6 processes per day is within a coordinateable and executable range. Exceeding this range indicates a high degree of overlap in processes and a significant increase in actual execution difficulty. When the maintenance design involves many equipment and processes, and personnel, hoisting, and power outage windows are highly concentrated, and the degree of parallelism of operations is high but the risk of resource conflicts is significant, it is necessary to strictly control the process density to avoid excessive process overlap leading to execution difficulties. For control, Tk is biased towards 0.3-0.4. When maintenance involves multiple equipment, has a moderate number of procedures, and involves both parallel and sequential operations, such as annual routine maintenance, multi-system collaborative maintenance without a complete shutdown, and combined maintenance with partial maintenance and technical upgrades, it is necessary to moderately limit the concentration of procedures, but not as strictly as major overhauls. Tk is biased towards 0.4-0.5. When maintenance involves a limited range of equipment, a small number of procedures, and a low probability of conflict between parallel operations, it is permissible to complete multiple procedures in the short to medium term, with a high tolerance for procedure density. In this case, Tk is biased towards 0.5-0.6.

[0150] In a specific embodiment of the present invention, step 5 is used to perform a rationality analysis on the maintenance process time data that has been converted to natural dates before the maintenance Gantt chart is generated, so as to avoid directly generating the Gantt chart when there are obvious defects in the maintenance plan.

[0151] In practice, the system first performs time consistency calculations on all maintenance procedures involved in generating the Gantt chart based on the actual natural start and end dates of the maintenance procedures. This is used to measure the coverage of the maintenance procedures on the overall cycle of the maintenance project in terms of time.

[0152] The consistency calculation is performed by summarizing the actual duration of each maintenance procedure and comparing it with the total maintenance project cycle to obtain a consistency index for the maintenance procedure time. This consistency index reflects whether the currently configured maintenance procedures form a complete and continuous time distribution within the overall time range. When the consistency index is less than the preset consistency threshold, it indicates that there are obvious gaps or incomplete configurations in the time distribution of the maintenance procedures. Based on this, the system determines that the current maintenance plan does not meet the conditions for generating a Gantt chart and prevents it from entering the Gantt chart generation process. When the consistency index is greater than or equal to the consistency threshold, it is considered that the time distribution of the maintenance procedures meets the basic integrity requirements and allows it to enter the subsequent processing steps.

[0153] After completing the time consistency calculation, the system further performs a time density calculation of maintenance procedures based on the number of maintenance procedures involved in the generation of the Gantt chart and the length of the maintenance project cycle. This is used to assess the degree of concentration of maintenance procedures within the maintenance cycle. Through this density calculation, it can be identified whether maintenance procedures are excessively concentrated within a limited time, which may lead to excessive load on maintenance resources or unreasonable construction arrangements.

[0154] The system compares the calculated maintenance process time density index with the preset density threshold. When the density index exceeds the density threshold, it determines that there is a concentrated risk in the time distribution of the maintenance process and generates a high load warning message. When the density index is less than or equal to the density threshold, it considers the time distribution of the maintenance process to be relatively reasonable and allows the generation of a maintenance Gantt chart based on the original data.

[0155] Finally, the system generates comprehensive judgment information based on the consistency threshold judgment result and the density threshold judgment result, which is used to indicate whether to allow entry into the automatic generation process of the maintenance Gantt chart;

[0156] By implementing step 5, this invention introduces a quantitative analysis and threshold determination mechanism based on time data before the maintenance Gantt chart is generated, so that the generation of the Gantt chart no longer depends solely on the static configuration of the maintenance procedures, but is dynamically judged based on the completeness and rationality of the maintenance plan in the time dimension.

[0157] Consistency calculation effectively avoids generating misleading Gantt charts when maintenance procedures are incomplete or time distribution is severely lacking; density calculation can identify potential high load risks caused by excessive concentration of maintenance procedures in advance, providing a basis for adjusting maintenance plans.

[0158] The aforementioned dual calculation and threshold determination mechanism enhances the reliability and engineering feasibility of the generated maintenance Gantt chart in terms of time coverage and load distribution, thereby improving the scientific nature and practical value of maintenance plan management.

[0159] In one embodiment of this application, the system first performs a consistency calculation, and then performs a density calculation when the consistency meets the threshold condition. This is because the consistency calculation is used to determine whether the maintenance process time data "has the basic legality to generate a Gantt chart", while the density calculation is used to assess the "time distribution risk" under the premise of legality. Only when the consistency meets the threshold condition does the density calculation have engineering significance.

[0160] Consistency calculation addresses the question of "whether the data is complete." The essence of consistency calculation is to determine whether the maintenance process time covers the main time interval of the maintenance project and whether there are a large number of time gaps, missing data, or configuration errors. If the consistency index C is less than Tc, it means that the maintenance process time itself is incomplete, and the Gantt chart has been distorted in the time dimension. At this time, generating a Gantt chart has no engineering value.

[0161] Density calculation addresses whether the distribution is reasonable. It focuses on whether the number of processes is too concentrated within a given time frame and whether there is a risk of excessive resource load. However, this judgment requires a prerequisite: the time distribution itself must be complete and legal. If consistency is not met, the density results will have two problems: they will be artificially amplified or reduced by "time gaps" and the resulting values ​​will not be meaningful for decision-making.

[0162] In the logical relationship, although the formulas for consistency calculation and density calculation are independent, they have a logical prerequisite relationship. Consistency judgment determines whether it is worthwhile to enter the analysis stage, while density judgment determines whether there is risk under the premise of analyzability. Simply put, consistency is an analyzability judgment, and density is a risk assessment judgment.

[0163] Step 6: If the threshold determination is passed, generate and output the maintenance Gantt chart.

[0164] Step 6 includes:

[0165] When both the consistency calculation result and the density calculation result meet the corresponding threshold conditions, the Gantt chart generation process is triggered.

[0166] The maintenance procedures are arranged horizontally by time according to their natural start and end dates.

[0167] Fill the maintenance procedures and corresponding time intervals into the Gantt chart structure to form a complete maintenance Gantt chart.

[0168] The generated maintenance Gantt chart is output for system display, file download, or maintenance data archiving.

[0169] In a specific embodiment of the present invention, step 6 is used to automatically generate a maintenance Gantt chart and output the results after the reasonableness of the maintenance process time is determined;

[0170] In practice, the system first makes a comprehensive judgment on the consistency calculation results and density calculation results obtained in step 5. Only when both meet the corresponding threshold conditions will the maintenance Gantt chart generation process be triggered, thereby ensuring that the maintenance data entering the generation stage meets the preset requirements in terms of time integrity and distribution rationality.

[0171] After the Gantt chart generation process is triggered, the system arranges the maintenance procedures involved in the Gantt chart generation in a horizontal time arrangement based on the actual natural start and end dates of the maintenance procedures, so that the sequential relationship and duration of each maintenance procedure on the time axis can be intuitively reflected.

[0172] Subsequently, the system fills the maintenance process content and corresponding time interval into the Gantt chart structure. Through a unified time scale and process display format, a complete maintenance Gantt chart is formed, thereby realizing the visualization of the maintenance plan in the time dimension.

[0173] After generating the maintenance Gantt chart, the system outputs the generated Gantt chart. The output methods include at least displaying it on the system interface, generating a downloadable file, and archiving and storing it as maintenance data to meet the application needs of the maintenance Gantt chart in different usage scenarios.

[0174] By implementing step 6, the present invention achieves automatic generation of maintenance Gantt charts under the premise that the maintenance process time configuration meets the requirements of rationality, thus avoiding the risk of misleading the generation of Gantt charts when there are obvious defects in the maintenance plan.

[0175] Meanwhile, by arranging the maintenance procedures and time intervals in chronological order according to natural dates, the generated maintenance Gantt chart can intuitively reflect the time distribution and continuity of maintenance procedures, thereby improving the practical value of the Gantt chart in maintenance planning management, resource coordination and progress control.

[0176] In addition, the generated Gantt chart can be directly used for display, download and archiving, reducing the workload of manually drawing and repeatedly organizing Gantt charts, thereby improving the overall efficiency and standardization of the hydropower plant maintenance management process.

[0177] An automatic generation system for Gantt charts of hydropower plant maintenance, implementing any of the above-mentioned methods for automatic generation of Gantt charts of hydropower plant maintenance, adopts a modular structure design, and the functional modules work collaboratively through a data model, including:

[0178] The maintenance data structuring module is used to build data models for maintenance projects, maintenance document packages, and maintenance procedures, thereby enabling structured management of maintenance business data and providing a unified data foundation for subsequent data processing in various modules.

[0179] The process time configuration module is used to configure the relative start and end times of maintenance processes and the Gantt chart labels, so that the maintenance processes have clear data definitions in terms of time attributes and display attributes.

[0180] The process identification and extraction module is used to identify and extract maintenance processes with Gantt chart labels. Based on the Gantt chart labels, the maintenance processes in the maintenance file package are identified and screened, and the corresponding process content and relative start and end time information are extracted to form process time data for subsequent processing.

[0181] The date conversion module is used to convert relative start and end times into specific natural dates, so that maintenance procedures can be accurately mapped to the actual timeline.

[0182] The consistency and density analysis module is used to perform consistency and density calculations and threshold determination to determine whether the time distribution of maintenance procedures meets the conditions for generating a Gantt chart.

[0183] The Gantt chart generation module is used to generate a maintenance Gantt chart after the threshold judgment is passed, so as to realize the visualization output of the maintenance plan.

[0184] By implementing the above system structure, this invention breaks down the maintenance Gantt chart generation process into multiple clearly defined and collaborative modules. This enables maintenance data to form a complete data processing chain, from structured modeling, time configuration, identification and extraction, date conversion, calculation and judgment to Gantt chart generation. The system can automatically prevent Gantt chart generation when there are unreasonable time configurations or load risks in the maintenance process, thereby avoiding the generation of misleading maintenance plan charts and improving the reliability of maintenance management. At the same time, through modular design, the system has good scalability and maintainability, reducing the workload of manually drawing Gantt charts and repeatedly checking time data, and significantly improving the automation level and engineering practical value of hydropower plant maintenance Gantt chart generation.

[0185] This invention constructs a structured model of hydropower plant maintenance project data and introduces a mechanism for relative time configuration of maintenance procedures, automatic conversion of natural dates, and dual calculation and threshold determination of consistency and density. This makes the generation of maintenance Gantt charts no longer dependent on manual processing and experience-based judgment, but based on quantifiable and verifiable time data analysis.

[0186] Consistency calculations quantitatively assess the time coverage of maintenance procedures within the maintenance project cycle, effectively preventing the generation of Gantt charts when maintenance procedures are incomplete or time distributions are severely lacking. Density calculations determine the concentration of maintenance procedures within a finite period, enabling early identification of potential high-load risks and thus improving the rationality and feasibility of maintenance plans.

[0187] The Gantt chart generation process is triggered only after the dual threshold judgment is passed, ensuring that the generated maintenance Gantt chart meets the preset requirements in terms of time integrity and distribution rationality, so that the Gantt chart not only has an intuitive display function, but also can truly reflect the feasibility status of the maintenance plan in the time dimension.

[0188] Therefore, this invention realizes the technical transformation of maintenance Gantt charts from "manual drawing and post-correction" to "automatic generation and pre-verification", which significantly improves the accuracy, reliability and engineering practical value of maintenance plan preparation, and has obvious technical progress effect.

[0189] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and alterations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A method for automatically generating maintenance Gantt charts for hydropower plants, characterized in that, Includes the following steps: Step 1: Configure the hydropower plant maintenance project data in a structured manner to build a maintenance data model that includes maintenance projects, maintenance document packages, and maintenance procedures; Step 2: Set the relative start and end times for each maintenance process in the maintenance document package, and set the Gantt chart labels for the maintenance processes that need to participate in the generation of the Gantt chart; Step 3: Identify the maintenance procedures marked with Gantt chart symbols, and extract the corresponding procedure content and relative start and end times; Step 4: Based on the actual start and end times of the maintenance project, convert the relative start and end times into specific calendar dates; Step 5: Perform consistency calculation and density calculation on the converted maintenance process time data, and determine the threshold for each. Step 6: If the threshold determination is passed, generate and output the maintenance Gantt chart.

2. The method for automatically generating a Gantt chart for hydropower plant maintenance according to claim 1, characterized in that, Step 1 includes: Construct a basic information structure for maintenance projects to describe the overall scope of a hydropower plant's maintenance tasks. The basic information for maintenance projects includes at least the project name, project number, maintenance type, and the planned start and end dates of the project. Multiple maintenance document package data units are established under each maintenance item to classify and manage the maintenance content of different equipment, systems or maintenance areas. Establish a corresponding maintenance process data structure in each maintenance file package. The maintenance process data structure shall include at least the process name, process sequence number, process description information, and time-related attribute fields. By using standardized data fields, maintenance projects, maintenance document packages, and maintenance procedures are linked and bound together to form a maintenance data model with clear hierarchy and well-defined relationships.

3. The method for automatically generating a Gantt chart for hydropower plant maintenance according to claim 1, characterized in that, Step 2 includes: Using the overall cycle of the maintenance project as a time reference benchmark, a corresponding relative start and end time interval is set for each maintenance procedure. The relative start and end times are configured with the maintenance project start date as day 1, using the format "day N to day M" to describe the time position of the maintenance process within the project cycle. During the configuration of maintenance procedures, Gantt chart labels are set for maintenance procedures that need to be displayed in the Gantt chart to distinguish between procedures that participate in the generation of the Gantt chart and those that do not. The relative start and end times and Gantt chart identifiers are stored as attribute information of the maintenance process in the maintenance data model.

4. The method for automatically generating a Gantt chart for hydropower plant maintenance according to claim 1, characterized in that, Step 3 includes: Perform a comprehensive scan of all maintenance procedures in the maintenance document package; Based on the preset Gantt chart identification rules, the maintenance procedures with Gantt chart identification are selected from all maintenance procedures. Extract the process content information and relative start and end time information corresponding to the maintenance processes marked with Gantt charts; The extracted process details are associated and encapsulated with relative start and end times to form a process time dataset for generating Gantt charts.

5. The method for automatically generating a Gantt chart for hydropower plant maintenance according to claim 1, characterized in that, Step 4 includes: Obtain the planned start date and planned end date of the maintenance project, and set the planned start date of the maintenance project as the time conversion base; Calculate the corresponding natural date offset based on the relative start and end times of the maintenance procedures; The natural date offset is converted to the planned start date of the maintenance project to generate the actual natural start and end dates corresponding to the maintenance process; The generated start and end dates are verified against the planned end date of the maintenance project to ensure that the converted process time is within the maintenance project cycle.

6. The method for automatically generating a Gantt chart for hydropower plant maintenance according to claim 5, characterized in that, The calculation of the natural date offset includes: The planned start date of the maintenance project is used as the time base for Day 1; Calculate the natural date offset based on the day value corresponding to the relative start and end times of the maintenance process; When the calculated start and end dates of the maintenance procedures exceed the planned end date of the maintenance project, the excess portion is either truncated or an anomaly marker is generated. The natural start and end dates of the processed maintenance procedures will be used as input data for subsequent consistency and density calculations.

7. The method for automatically generating a Gantt chart for hydropower plant maintenance according to claim 1, characterized in that, Step 5 includes: Based on the natural start and end dates of the maintenance procedures, the execution time consistency of the maintenance procedures involved in the generation of the Gantt chart is calculated to assess the time coverage of the maintenance procedures. Based on the number of maintenance procedures and the length of the maintenance project cycle, the time density of maintenance procedures is calculated to assess the degree of concentration of maintenance procedures within the project cycle. The consistency calculation results are compared with the preset consistency threshold, and the density calculation results are compared with the preset density threshold. The decision information is generated based on the threshold comparison results to indicate whether the process of generating the Gantt chart is allowed.

8. The method for automatically generating a Gantt chart for hydropower plant maintenance according to claim 1, characterized in that, The formula for calculating the consistency between the time distribution of maintenance procedures and the cycle of maintenance projects is as follows: ； Among them, D i start D represents the actual start date of the i-th maintenance procedure. i end Let D be the actual end date of the i-th maintenance procedure, n be the number of maintenance procedures involved in generating the Gantt chart, and D be the number of maintenance procedures involved in generating the Gantt chart. proj C represents the total cycle days of the maintenance project, and C is the consistency index of maintenance process time. When C < Tc, the time distribution of the maintenance process is determined to be incomplete, and the generation of the Gantt chart is prevented. When C≥Tc, proceed to the next processing step; The value of Tc ranges from 0.7 to 0.

9. The density calculation formula used to assess the concentration of maintenance procedures during the maintenance cycle is as follows: ； Where n is the number of maintenance procedures involved in generating the Gantt chart, and D proj K represents the total cycle days of the maintenance project, and K is the time density index of the maintenance process. When K > Tk, the maintenance process is determined to be concentrated, and a high load warning is generated. When K≤Tk, it is permissible to generate a Gantt chart based on the original data; The value of Tk ranges from 0.3 to 0.

6.

9. The method for automatically generating a Gantt chart for hydropower plant maintenance according to claim 1, characterized in that, Step 6 includes: When both the consistency calculation result and the density calculation result meet the corresponding threshold conditions, the Gantt chart generation process is triggered. The maintenance procedures are arranged horizontally by time according to their natural start and end dates. Fill the maintenance procedures and corresponding time intervals into the Gantt chart structure to form a complete maintenance Gantt chart. The generated maintenance Gantt chart is output for system display, file download, or maintenance data archiving.

10. An automatic generation system for maintenance Gantt charts of hydropower plants, implementing the automatic generation method for maintenance Gantt charts of hydropower plants as described in any one of claims 1-9, characterized in that, include: The maintenance data structuring module is used to construct data models of maintenance projects, maintenance document packages, and maintenance procedures. The process time configuration module is used to configure the relative start and end times of the maintenance process and the Gantt chart identifiers. The process identification and extraction module is used to identify and extract maintenance processes marked with Gantt chart symbols. A date conversion module, which is used to convert relative start and end times into specific natural dates; A consistency and density analysis module, which performs consistency calculations and density calculations and determines thresholds; A Gantt chart generation module is used to generate a maintenance Gantt chart after the threshold determination is passed.

Images