Machine room operation and maintenance collaborative management system based on operation and maintenance task linkage

Abstract

The application discloses a machine room operation and maintenance collaborative management system based on operation and maintenance task linkage and relates to the technical field of machine room operation and maintenance, which is used for solving the problems of quantitative perception and dynamic triggering scheduling of multi-work-type collaborative task progress deviation, leading to uncontrolled collaborative task time sequence advancement and cross-work-type response lag. Through collection of work-type task node completion rate and node operation time length deviation, progress deviation comprehensive quantity is generated and progress deviation state is classified. Trigger urgency is calculated by fusing time sequence dependence strength between work types. A correction trigger threshold is generated based on historical trigger error mean value to determine whether to enter a ready trigger state. Trigger execution quantity is generated by fusing downstream work type personnel arrival situation and tool verification result. Corresponding level ready notifications are issued to downstream work types according to the trigger execution quantity. Downstream work type response arrival time length is detected to evaluate response sufficiency. Trigger execution quantity is executed with multiplicative attenuation for reverse correction, realizing collaborative task trigger precision and cross-work-type response closed-loop management.

Description

Technical Field

[0001] This invention relates to the field of data center operation and maintenance technology, and more specifically, to a data center operation and maintenance collaborative management system based on the linkage of operation and maintenance tasks. Background Technology

[0002] As data centers continue to expand in scale, the complexity of data center operation and maintenance tasks is increasing. In typical operation and maintenance tasks such as rack relocation, power distribution maintenance, and structured cabling, there are strict time-series dependencies between different trades. These tasks need to be carried out sequentially according to a preset task template. Existing data center operation and maintenance management platforms are usually based on a work order system, which records the execution status of task nodes for each trade. The scheduler then uses experience to determine whether to issue a readiness notification to downstream trades in order to drive the sequential progress of the overall collaborative tasks.

[0003] The existing technology has the following shortcomings: Currently, existing technologies rely on human experience to judge the degree of progress deviation in multi-task collaborative task management. They lack quantitative integration methods for the completion rate of task nodes and the deviation of node operation time. They cannot adaptively collect the on-site status of downstream personnel and tool verification results to form hierarchical ready notifications. They also cannot perform reverse correction and closed-loop feedback on the triggered execution volume based on the actual response time of downstream personnel. As a result, there are problems such as uncontrolled task timing and insufficient collaborative efficiency. Therefore, a data center operation and maintenance collaborative management system based on operation and maintenance task linkage is proposed.

[0004] The information disclosed in the background section is only intended to enhance the understanding of the background of this disclosure, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0005] To overcome the aforementioned deficiencies of the prior art, embodiments of the present invention provide a data center operation and maintenance collaborative management system based on operation and maintenance task linkage. This system utilizes a collaborative linkage mechanism that employs quantitative perception of progress deviation, dynamic correction of trigger thresholds, tiered readiness notification issuance, and closed-loop feedback of response sufficiency to address the problems mentioned in the background art.

[0006] To achieve the above objectives, this invention provides the following technical solution: a data center operation and maintenance collaborative management system based on operation and maintenance task linkage, comprising a deviation perception module, a threshold correction module, a linkage triggering module, and a response closed-loop module, the functions of each module being as follows: The deviation perception module is used to collect the completion rate of task nodes for each type of work, detect the deviation of the node operation time of each task node, generate a comprehensive progress deviation quantity by combining the completion rate of task nodes and the node operation time deviation quantity, identify the progress deviation status of the current collaborative task based on the comprehensive progress deviation quantity, classify the progress deviation status, and pass the comprehensive progress deviation quantity and progress deviation status to the threshold correction module. The threshold correction module is used to receive the overall progress deviation and progress deviation status, retrieve the time dependency strength between job types preset in the task template, calculate the trigger urgency based on the overall progress deviation and time dependency strength, retrieve the average trigger error of similar historical tasks in the historical work order database, generate a corrected trigger threshold based on the average trigger error, determine whether to enter the ready trigger state, and pass the trigger urgency and ready trigger state to the linkage trigger module. The linkage triggering module is used to receive the trigger urgency and ready trigger status. When the ready trigger status is in the ready trigger status, it collects the current ready status of the downstream work, merges the current ready status of the downstream work with the trigger urgency to generate the trigger execution quantity, and sends the corresponding level of ready notification to the downstream work according to the trigger execution quantity, driving the collaborative task sequence to advance, and passing the trigger execution quantity to the response closed loop module. The response closed-loop module is used to receive the trigger execution quantity, detect the time from the issuance of the ready notification to the downstream work's confirmation and receipt of the response, evaluate the sufficiency of the response based on the response sufficiency, determine whether to perform reverse correction on the trigger execution quantity based on the response sufficiency, and generate the corrected trigger execution quantity.

[0007] In a preferred embodiment, in the deviation perception module, the task node completion rate is the ratio of the number of task nodes actually completed by each task type in the current collaborative task to the number of task nodes planned to be completed. The deviation of node operation time is the difference between the actual operation time and the planned operation time for each task node; Max-Min standardization is performed on the deviation of node operation time to obtain the standardized result of the deviation of node operation time. The overall schedule deviation is calculated by standardizing the deviation between the completion rate of the task nodes and the operation time of the nodes using the Euclidean composite method.

[0008] In a preferred embodiment, the deviation perception module performs a three-stage comparison between the overall progress deviation and the minor deviation threshold and the major deviation threshold: When the total deviation from the schedule is greater than or equal to the severe deviation threshold, the schedule deviation status is classified as severe deviation. When the total deviation from the schedule is greater than or equal to the minor deviation threshold but less than the major deviation threshold, the schedule deviation status is classified as minor deviation. When the total deviation from the schedule is less than the minor deviation threshold, the schedule deviation status is classified as normal progress.

[0009] In a preferred embodiment, the threshold correction module uses a geometric mean to integrate the overall progress deviation and the temporal dependence strength between different job types to obtain the trigger urgency. The mean trigger error is the average difference between the actual ready time and the trigger time in similar historical collaborative tasks. The mean trigger error is standardized using Max-Min standardization to obtain the standardized mean trigger error. The standardized result of the trigger error is used to generate a corrected trigger threshold through a bias compensation method: ,in, To correct the trigger threshold, The preset baseline trigger threshold, This is the result after standardizing the mean of the trigger error.

[0010] In a preferred embodiment, the threshold correction module uses the progress deviation state as a gating condition and the trigger urgency as a numerical condition, and performs a joint judgment with the correction trigger threshold: When the progress deviation status is a minor deviation or a major deviation, and the trigger urgency is greater than or equal to the correction trigger threshold, the ready trigger status is set to trigger ready. When the progress deviation status is normal progress, or the trigger urgency is less than the correction trigger threshold, the ready trigger status will be set to maintain monitoring.

[0011] In a preferred embodiment, in the linkage triggering module, under the condition that the ready triggering state is trigger ready, the current ready state of the downstream work type is collected. Personnel availability is the ratio of the actual number of workers in downstream jobs to the number of workers who should be in place. The tool verification result is the ratio of the number of tools that passed the verification for downstream jobs to the number of tools that should be provided. The current readiness status of downstream jobs is obtained by integrating personnel availability and tool verification results using a geometric mean method. The trigger execution quantity is obtained by combining the trigger urgency with the current readiness status of downstream tasks using a harmonic averaging method.

[0012] In a preferred embodiment, the linkage triggering module performs a three-stage comparison with the high-level classification threshold and the intermediate-level classification threshold, and issues the corresponding level of ready notification to downstream tasks according to the classification result: When the number of executions triggered is greater than or equal to the advanced tier threshold, a Level 1 Readiness Notification is sent to downstream tasks. When the number of triggered executions is greater than or equal to the intermediate tier threshold and less than the advanced tier threshold, a level 2 ready notification is sent to the downstream work types. When the number of triggered executions is less than the intermediate tier threshold, a level 3 ready notification is sent to downstream tasks.

[0013] In a preferred embodiment, in the response closed-loop module, the response arrival time is the difference between the time when the downstream work unit confirms receipt and the time when the ready notification is issued. The response time is standardized using a benchmark ratio method to obtain the response adequacy.

[0014] In a preferred embodiment, in the response closed-loop module, the response sufficiency is compared with the sufficiency threshold, and the result of the comparison determines whether to perform a reverse correction on the triggered execution amount. When the sufficiency of the response is greater than or equal to the sufficiency threshold, the reverse correction is not performed, and the corrected trigger execution amount is set to be equal to the trigger execution amount. When the sufficiency of the response is less than the sufficiency threshold, a reverse correction in the form of multiplicative decay is performed on the trigger execution amount, and the product of the sufficiency of the response and the trigger execution amount is used as the corrected trigger execution amount.

[0015] The technical effects and advantages of this invention are as follows: This invention achieves a significant improvement in the accuracy of collaborative task triggering by using Euclidean composite quantification to measure the deviation between task completion rate and node operation time. It also achieves adaptive correction of trigger threshold by integrating the temporal dependence strength between tasks and the average of historical trigger errors. After harmonizing and averaging the trigger urgency and downstream readiness status, ready notifications are issued according to level. Based on the response arrival time, a multiplicative attenuation inverse correction is performed on the trigger execution amount. This significantly improves the accuracy of collaborative task triggering, effectively reduces the cross-task response delay rate, and ensures the stability and closed-loop controllability of the time sequence advancement of multi-task collaborative tasks. Attached Figure Description

[0016] Figure 1 This is a flowchart illustrating the implementation of the data center operation and maintenance collaborative management system based on operation and maintenance task linkage, as described in this invention.

[0017] Figure 2 This is a schematic diagram of the modules of the data center operation and maintenance collaborative management system based on operation and maintenance task linkage of the present invention. Detailed Implementation

[0018] 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.

[0019] This invention constructs a collaborative architecture consisting of four modules: deviation perception, threshold correction, linkage triggering, and response closed loop. It integrates the quantitative calculation of progress deviation of multi-task collaborative tasks, dynamic correction of trigger thresholds, and downstream response closed loop feedback into a unified whole, thereby achieving precise triggering and adaptive closed-loop management of the time sequence advancement of data center operation and maintenance collaborative tasks.

[0020] Example 1, please refer to Figures 1 to 2 The data center operation and maintenance collaborative management system based on operation and maintenance task linkage includes a deviation perception module, a threshold correction module, a linkage triggering module, and a response closed-loop module, with electrical signal connections between the modules; The functions of each module are as follows: The deviation perception module is used to collect the completion rate of task nodes for each type of work, detect the deviation of the node operation time of each task node, generate a comprehensive progress deviation quantity by combining the completion rate of task nodes and the node operation time deviation quantity, identify the progress deviation status of the current collaborative task based on the comprehensive progress deviation quantity, classify the progress deviation status, and pass the comprehensive progress deviation quantity and progress deviation status to the threshold correction module. The threshold correction module is used to receive the overall progress deviation and progress deviation status, retrieve the time dependency strength between job types preset in the task template, calculate the trigger urgency based on the overall progress deviation and time dependency strength, retrieve the average trigger error of similar historical tasks in the historical work order database, generate a corrected trigger threshold based on the average trigger error, determine whether to enter the ready trigger state, and pass the trigger urgency and ready trigger state to the linkage trigger module. The linkage triggering module is used to receive the trigger urgency and ready trigger status. When the ready trigger status is in the ready trigger status, it collects the current ready status of the downstream work, merges the current ready status of the downstream work with the trigger urgency to generate the trigger execution quantity, and sends the corresponding level of ready notification to the downstream work according to the trigger execution quantity, driving the collaborative task sequence to advance, and passing the trigger execution quantity to the response closed loop module. The response closed-loop module is used to receive the trigger execution quantity, detect the time from the issuance of the ready notification to the downstream work's confirmation and receipt of the response, evaluate the sufficiency of the response based on the response sufficiency, determine whether to perform reverse correction on the trigger execution quantity based on the response sufficiency, and generate the corrected trigger execution quantity.

[0021] It should be noted that a job task node is the smallest execution unit in a data center operation and maintenance collaborative task, divided by job type. Each task node corresponds to a specific operation undertaken by a job type in the collaborative task sequence. A collaborative task refers to a data center operation and maintenance task that is completed jointly by multiple job types in a pre-set sequence, such as cabinet relocation, power distribution maintenance, and structured cabling, which require multi-job collaboration. A task template is a set of data that is pre-established before the collaborative task starts and is used to describe the collaborative task structure and the dependencies between job types. The historical work order database is a set of data used to store previous data center operation and maintenance collaborative task work order records. Its content includes information such as the job type composition of each work order, the completion status of task nodes, the trigger time, the ready time, and the final completion time.

[0022] In the deviation perception module, the task node completion rate of each type of work is collected from the on-site construction record system. The task node completion rate is the ratio of the number of task nodes actually completed by each type of work in the current collaborative task to the number of task nodes planned to be completed. The value range is [0,1], which reflects the progress of the corresponding type of work in the collaborative task. The larger the value, the better the current completion status of the type of work.

[0023] The deviation of node operation time for each task node is collected from the work order system. The deviation of node operation time is the difference between the actual operation time and the planned operation time for each task node, in minutes. It reflects the degree of delay in the execution time of the corresponding task node. The larger the value, the more serious the time delay of the task node.

[0024] Max-Min standardization is applied to the deviation of node operation duration, mapping it to the [0,1] interval: ,in, This is the standardized result of the node operation time deviation. This represents the deviation in node operation time. It represents the minimum value among the distributions of operation time deviations across all task nodes in the current collaborative task. This represents the maximum value among all task nodes in the current collaborative task in terms of their operation time deviation distribution.

[0025] The larger the deviation in node operation time, the closer the standardized result of the node operation time deviation is to 1, reflecting that the time delay of the corresponding task node is relatively more serious among all task nodes in the current collaborative task.

[0026] Based on the fact that the standardized results of the task completion rate and the deviation of the operation time are both within the [0,1] interval, the Euclidean composite method is used to generate the comprehensive progress deviation: ,in, For the schedule to deviate from the overall quantity, For the completion rate of job tasks, This is the result after standardizing the deviation of node operation time.

[0027] The lower the completion rate of a task's milestones, the larger the schedule gap and the greater the overall schedule deviation; the larger the standardized result of the deviation in node operation time, the greater the overall schedule deviation. An increase in deviation in either dimension will cause a simultaneous increase in the overall schedule deviation, reflecting the severity of the overall deviation of the collaborative task.

[0028] The overall deviation from the schedule is compared in three stages with the minor deviation threshold and the major deviation threshold: When the total deviation from the schedule is greater than or equal to the severe deviation threshold, the overall deviation of the collaborative task is determined to be serious, and the schedule deviation status is classified as severe deviation. When the total deviation from the schedule is greater than or equal to the minor deviation threshold but less than the major deviation threshold, the collaborative task is determined to have a controllable deviation, and the schedule deviation status is classified as a minor deviation. When the overall deviation from the schedule is less than the minor deviation threshold, the collaborative task is determined to proceed according to the established sequence, and the schedule deviation status is classified as normal progress.

[0029] The thresholds for minor and major deviations are set as follows: Access the historical work order database to extract samples of the overall progress deviation of similar collaborative tasks under three categories of results: normal completion, minor delay, and major delay. Statistically analyze the distribution range of the three types of samples, and take the upper limit of the distribution of normally completed samples as the minor deviation threshold, and take the upper limit of the distribution of minor delayed samples as the major deviation threshold, so as to ensure that collaborative tasks that proceed in the established sequence are not misjudged as deviations.

[0030] By collecting the deviations in task completion rate and operation time of each task, the severity of the progress deviation of the collaborative task is quantified into a comprehensive progress deviation. The comprehensive progress deviation is further classified into progress deviation status and fed into the threshold correction module, providing a quantifiable progress basis for subsequent trigger urgency calculation and trigger determination.

[0031] In the threshold correction module, the progress deviation total and progress deviation status are received from the deviation perception module. The task template retrieves the temporal dependency strength between upstream and downstream tasks in the current collaborative task. The temporal dependency strength between tasks is a pre-defined quantitative indicator that represents the degree of connection between upstream and downstream tasks. The value range is [0,1]. The larger the value, the closer the connection between upstream and downstream tasks and the greater the impact of the completion time of the upstream task on the start time of the downstream task.

[0032] The trigger urgency is obtained by fusing the two factors using a geometric mean, and the calculation formula is as follows: ,in, To trigger urgency, For the schedule to deviate from the overall quantity, This represents the intensity of temporal dependency between different job types.

[0033] The greater the deviation from the overall schedule or the stronger the time dependence between different tasks, the greater the urgency of triggering the schedule; if any factor is low, the urgency of triggering the schedule will be lowered accordingly.

[0034] The average trigger error of similar historical tasks is retrieved from the historical work order database. The average trigger error is the average difference between the actual ready time and the trigger time in similar historical collaborative tasks, in minutes. It reflects the systematic deviation between the historical trigger sequence and the actual ready sequence. A positive value indicates that the historical trigger is generally earlier than the actual ready time, that is, the downstream tasks need to wait a long time after the trigger before they are truly ready.

[0035] The mean trigger error is standardized using Max-Min standardization to obtain the standardized mean trigger error. The larger the mean trigger error, the closer the result of the normalized mean trigger error is to 1, reflecting the more serious the degree of premature triggering in history.

[0036] Based on the trigger urgency, a modified trigger threshold is generated using a deviation compensation method: ,in, To correct the trigger threshold, The preset baseline trigger threshold, This is the result after standardizing the mean of the trigger error; The larger the normalized mean of the trigger error, the higher the trigger threshold will be, thus delaying the trigger determination in order to compensate for the systematic bias of earlier triggers in the past.

[0037] The preset baseline trigger threshold is set by accessing the historical work order database to extract the trigger urgency samples corresponding to successful linkage cases in similar collaborative tasks, statistically analyzing the sample distribution, and taking the lower quartile value as the preset baseline trigger threshold. This ensures that, under standard conditions unaffected by historical deviations, trigger urgency reaching this value is considered to meet the triggering conditions.

[0038] The process involves using the progress deviation status as a gating condition, the trigger urgency as a numerical condition, and a combined judgment with a modified trigger threshold. When the progress deviation is minor or severe, and the trigger urgency is greater than or equal to the correction trigger threshold, it is determined that the collaborative task has met the conditions for linkage triggering, and the ready triggering state is set to trigger ready. When the progress deviation status is normal progress, or the trigger urgency is less than the correction trigger threshold, it is determined that the collaborative task does not need to be triggered in time, and the ready trigger status is set to maintain monitoring.

[0039] By combining the geometric mean of the overall progress deviation and the time dependence strength between different tasks, and by compensating for the deviation of the trigger threshold based on the result of standardization of the trigger error mean, the trigger urgency and the corrected trigger threshold are jointly output to the linkage trigger module as the basis for subsequent trigger execution quantity calculation and the determination of the graded issuance of ready notification.

[0040] In the linkage triggering module, the trigger urgency and ready trigger status are received from the threshold correction module. When the ready trigger status is "trigger ready", the current ready status of downstream tasks is collected; when the ready trigger status is "maintain monitoring", the current ready status of downstream tasks is not collected, nor is a trigger execution quantity generated.

[0041] The current readiness status of downstream jobs is reflected by two dimensions: personnel availability and tool verification results.

[0042] The attendance data of downstream workers is collected by on-site attendance devices. The attendance data is the ratio of the actual number of workers in downstream jobs to the number of workers who should be in attendance. The value range is [0,1], which reflects the adequacy of the attendance of downstream workers.

[0043] The tool verification device collects the tool verification results of downstream jobs. The tool verification result is the ratio of the number of tools that have passed the verification to the number of tools that should be provided by the downstream jobs. The value range is [0,1], which reflects the availability and usability of the tools required by the downstream jobs.

[0044] Based on the premise that both personnel availability and tool verification results are within the [0,1] interval, the current readiness status of downstream jobs is obtained by merging the two using a geometric mean: ,in, The current readiness status of downstream processes. Regarding the availability of personnel, This is the result of the tool verification.

[0045] The trigger execution quantity is obtained by combining the trigger urgency with the current readiness status of downstream tasks using a harmonic averaging method. ,in, To trigger the execution volume, To trigger urgency, This indicates the current readiness status of downstream processes.

[0046] The trigger execution volume is larger only when both the trigger urgency and the current readiness status of the downstream tasks are high; when either one is low, the trigger execution volume is significantly biased towards a smaller value.

[0047] The trigger execution volume will be compared with the high-level classification threshold and the medium-level classification threshold in three stages, and the corresponding level of readiness notification will be issued to downstream tasks according to the classification results: When the number of executions triggered is greater than or equal to the advanced tier threshold, it is determined that this linkage should be promoted with the highest priority, and a level one ready notification is issued to the downstream tasks. When the number of triggered executions is greater than or equal to the intermediate tier threshold and less than the advanced tier threshold, the linkage is determined to proceed with the normal priority, and a level 2 ready notification is issued to the downstream work. When the number of triggered executions is less than the intermediate tier threshold, the linkage is determined to proceed with a prompting priority, and a level 3 ready notification is issued to downstream tasks.

[0048] The advanced and intermediate grading thresholds are set as follows: Access the historical work order database to extract the trigger execution volume samples corresponding to successful progress cases in similar collaborative tasks, statistically analyze the sample distribution, take the upper quartile value as the advanced grading threshold, and take the lower quartile value as the intermediate grading threshold to ensure that the grading of ready notifications is consistent with the intensity distribution of historical successful cases.

[0049] By integrating the geometric mean of personnel availability and tool verification results, and the harmonic mean of trigger urgency and current readiness status of downstream tasks, the trigger execution volume is converted into corresponding level readiness notifications and sent to downstream tasks, driving the sequential advancement of collaborative tasks. The trigger execution volume is then passed to the response closed-loop module for subsequent response adequacy assessment.

[0050] In the closed-loop response module, the trigger execution amount is received from the linkage trigger module; the response arrival time is collected from the ready notification receipt log. The response arrival time is the difference between the downstream work unit's confirmation and receipt time and the ready notification issuance time, in minutes, reflecting the timeliness of the downstream work unit's response to the ready notification.

[0051] The response time is mapped to the [0,1] interval using a baseline ratio method: ,in, The result is the standardized response time. In order to respond to the time required, This is the preset response baseline duration.

[0052] When the response time does not exceed the preset response baseline time, the standardized result of the response time is always 1, reflecting that the response is completed within the baseline time and is considered timely; when the response time exceeds the preset response baseline time, the standardized result of the response time is less than 1, and the larger the multiple of the response time exceeding the baseline time, the smaller the standardized result of the response time.

[0053] The standardized response time is directly used as the response adequacy. The shorter the response time, the closer the standardized response time is to 1, the higher the response adequacy, and the more adequate the response of downstream tasks to the readiness notification.

[0054] The response sufficiency is compared with the sufficiency threshold, and the result of the comparison determines whether to perform a reverse correction on the triggered execution amount: When the sufficiency of the response is greater than or equal to the sufficiency threshold, it is determined that the response of the downstream work type to the current level readiness notification has met the standard, and no reverse correction is performed. Instead, the corrected trigger execution amount is set to be equal to the trigger execution amount. When the sufficiency of the response is less than the sufficiency threshold, it is determined that the response of the downstream work type to the current level of readiness notification is not up to standard. A multiplicative decay-based reverse correction is applied to the triggered execution quantity, calculated as follows: ,in, To trigger the execution amount after correction, To trigger the execution volume, For adequacy of response.

[0055] The lower the sufficiency of the response, the deeper the multiplicative decay, and the smaller the amount of execution triggered after correction.

[0056] The corrected trigger execution amount is used as the trigger baseline update value for the current collaborative task, and fed back as a reference for triggering the next round of collaborative tasks. The sufficiency threshold and the preset response baseline duration are set as follows: the sufficiency threshold is obtained by statistical analysis of the response sufficiency samples corresponding to successful response cases in the historical work order database, and the lower quartile of the sample distribution is taken as the sufficiency threshold; the preset response baseline duration is determined by the median value of the normal response time of downstream tasks in the task template, so as to ensure that the baseline duration covers the upper limit of the normal response time, and does not include occasional extreme response delays within the normal range.

[0057] By eliminating the dimensions of the benchmark ratio method for response arrival time and by making a reverse correction based on the multiplicative attenuation of the trigger execution quantity based on response sufficiency, a closed-loop feedback from trigger issuance to response receipt is achieved. This reverses the actual response capability of downstream tasks to the trigger benchmark, enabling the trigger determination of subsequent collaborative tasks to dynamically match the actual response level of downstream tasks.

[0058] Finally, it should be noted that in this paper, relational terms such as first and second are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations.

[0059] Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0060] In this document, the singular forms “a,” “an,” and “the” may also include the plural forms unless the context clearly indicates otherwise. It should also be understood that terms such as “comprising / including” or “having” specify the presence of the stated features, integrals, steps, operations, components, parts, or combinations thereof, but do not preclude the possibility of the presence or addition of one or more other features, integrals, steps, operations, components, parts, or combinations thereof. Meanwhile, the term “and / or” as used in this specification includes any and all combinations of the associated listed items.

[0061] The various embodiments in this specification are described in a progressive manner. Each embodiment focuses on the differences from other embodiments. The various embodiments can be combined as needed, and the same or similar parts can be referred to each other.

[0062] The above description of the disclosed embodiments will enable those skilled in the art to make or use various modifications to these embodiments. It will be readily apparent to those skilled in the art that the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A data center operation and maintenance collaborative management system based on operation and maintenance task linkage, characterized in that: This includes a data center operation and maintenance collaborative management system based on operation and maintenance task linkage, comprising a deviation detection module, a threshold correction module, a linkage triggering module, and a response closed-loop module. The functions of each module are as follows: The deviation perception module is used to collect the completion rate of task nodes for each type of work, detect the deviation of the node operation time of each task node, generate a comprehensive progress deviation quantity by combining the completion rate of task nodes and the node operation time deviation quantity, identify the progress deviation status of the current collaborative task based on the comprehensive progress deviation quantity, classify the progress deviation status, and pass the comprehensive progress deviation quantity and progress deviation status to the threshold correction module. The threshold correction module is used to receive the overall progress deviation and progress deviation status, retrieve the time dependency strength between job types preset in the task template, calculate the trigger urgency based on the overall progress deviation and time dependency strength, retrieve the average trigger error of similar historical tasks in the historical work order database, generate a corrected trigger threshold based on the average trigger error, determine whether to enter the ready trigger state, and pass the trigger urgency and ready trigger state to the linkage trigger module. The linkage triggering module is used to receive the trigger urgency and ready trigger status. When the ready trigger status is in the ready trigger status, it collects the current ready status of the downstream work, merges the current ready status of the downstream work with the trigger urgency to generate the trigger execution quantity, and sends the corresponding level of ready notification to the downstream work according to the trigger execution quantity, driving the collaborative task sequence to advance, and passing the trigger execution quantity to the response closed loop module. The response closed-loop module is used to receive the trigger execution quantity, detect the time from the issuance of the ready notification to the downstream work's confirmation and receipt of the response, evaluate the sufficiency of the response based on the response sufficiency, determine whether to perform reverse correction on the trigger execution quantity based on the response sufficiency, and generate the corrected trigger execution quantity.

2. The data center operation and maintenance collaborative management system based on operation and maintenance task linkage according to claim 1, characterized in that: In the deviation perception module, the task node completion rate is the ratio of the number of task nodes actually completed by each job in the current collaborative task to the number of task nodes planned to be completed. The deviation of node operation time is the difference between the actual operation time and the planned operation time for each task node; Max-Min standardization is performed on the deviation of node operation time to obtain the standardized result of the deviation of node operation time. The overall schedule deviation is calculated by standardizing the deviation between the completion rate of the task nodes and the operation time of the nodes using the Euclidean composite method.

3. The data center operation and maintenance collaborative management system based on operation and maintenance task linkage according to claim 1, characterized in that: In the deviation perception module, the overall progress deviation is compared with the minor deviation threshold and the major deviation threshold in three stages: When the total deviation from the schedule is greater than or equal to the severe deviation threshold, the schedule deviation status is classified as severe deviation. When the total deviation from the schedule is greater than or equal to the minor deviation threshold but less than the major deviation threshold, the schedule deviation status is classified as minor deviation. When the total deviation from the schedule is less than the minor deviation threshold, the schedule deviation status is classified as normal progress.

4. The data center operation and maintenance collaborative management system based on operation and maintenance task linkage according to claim 3, characterized in that: In the threshold correction module, the trigger urgency is obtained by integrating the overall progress deviation and the temporal dependence between different job types using a geometric average method. The mean trigger error is the average difference between the actual ready time and the trigger time in similar historical collaborative tasks. The mean trigger error is standardized using Max-Min standardization to obtain the standardized mean trigger error. The standardized result of the trigger error is used to generate a corrected trigger threshold through a bias compensation method: ,in, To correct the trigger threshold, The preset baseline trigger threshold, This is the result after standardizing the mean of the trigger error.

5. The data center operation and maintenance collaborative management system based on operation and maintenance task linkage according to claim 3, characterized in that: In the threshold correction module, the progress deviation status is used as the gating condition, the trigger urgency is used as the numerical condition, and the correction trigger threshold is used for joint judgment: When the progress deviation status is a minor deviation or a major deviation, and the trigger urgency is greater than or equal to the correction trigger threshold, the ready trigger status is set to trigger ready. When the progress deviation status is normal progress, or the trigger urgency is less than the correction trigger threshold, the ready trigger status will be set to maintain monitoring.

6. The data center operation and maintenance collaborative management system based on operation and maintenance task linkage according to claim 5, characterized in that: In the linkage triggering module, under the condition that the ready triggering state is trigger ready, the current ready state of the downstream work type is collected; Personnel availability is the ratio of the actual number of workers in downstream jobs to the number of workers who should be in place. The tool verification result is the ratio of the number of tools that passed the verification for downstream jobs to the number of tools that should be provided. The current readiness status of downstream jobs is obtained by integrating personnel availability and tool verification results using a geometric mean method. The trigger execution quantity is obtained by combining the trigger urgency with the current readiness status of downstream tasks using a harmonic averaging method.

7. The data center operation and maintenance collaborative management system based on operation and maintenance task linkage according to claim 1, characterized in that: In the linkage triggering module, the trigger execution volume is compared with the high-level classification threshold and the medium-level classification threshold in three stages, and the corresponding level of ready notification is issued to the downstream tasks according to the classification result: When the number of executions triggered is greater than or equal to the advanced tier threshold, a Level 1 Readiness Notification is sent to downstream tasks. When the number of triggered executions is greater than or equal to the intermediate tier threshold and less than the advanced tier threshold, a level 2 ready notification is sent to the downstream work types. When the number of triggered executions is less than the intermediate tier threshold, a level 3 ready notification is sent to downstream tasks.

8. The data center operation and maintenance collaborative management system based on operation and maintenance task linkage according to claim 1, characterized in that: In the closed-loop response module, the response time is the difference between the time when the downstream work unit confirms receipt and the time when the ready notification is issued. The response time is standardized using a benchmark ratio method to obtain the response adequacy.

9. The data center operation and maintenance collaborative management system based on operation and maintenance task linkage according to claim 1, characterized in that: In the response closed-loop module, the response sufficiency is compared with the sufficiency threshold, and the result of the comparison determines whether to perform a reverse correction on the triggered execution amount. When the sufficiency of the response is greater than or equal to the sufficiency threshold, the reverse correction is not performed, and the corrected trigger execution amount is set to be equal to the trigger execution amount. When the sufficiency of the response is less than the sufficiency threshold, a reverse correction in the form of multiplicative decay is performed on the trigger execution amount, and the product of the sufficiency of the response and the trigger execution amount is used as the corrected trigger execution amount.

Images