Maintenance progress network diagram visual interaction method and system

Abstract

The invention discloses a visual interaction method and system for a maintenance progress network diagram, relates to the technical field of computer application, and aims to solve the problems of static dependency relationship, lack of dynamic data fusion, single visualization dimension and insufficient permission adaptation in a traditional system. The method supports double-click expansion of different hierarchies by constructing a three-level progressive tree hierarchical structure; realizing node visibility control based on a role permission model; the dependency intensity is calculated in combination with static logic dependency and dynamic data mining, and is visually presented through a connecting line style; multi-mode interaction operation is supported, conflicts are detected in real time, and a mediation scheme is generated; and the mobile terminal adopts block rendering optimization display. The system comprises a node hierarchy management module, a role authority management module, a dependency intensity calculation module, a dependency visual mapping module, an interactive operation processing module, a conflict processing module and a mobile terminal rendering optimization module, and can realize dynamic visual interactive management of the maintenance progress.

Description

Technical Field

[0001] This invention relates to the field of computer application technology, specifically to a visualization system in industrial production management, and particularly to a method and system for visualizing and interacting with the dynamic dependencies of equipment maintenance progress, which is a network diagram visualization of maintenance progress. Background Technology

[0002] In fields such as industrial equipment maintenance and manufacturing process management, traditional visualization systems generally suffer from the following technical problems: Staticization of Dependencies: Existing systems often represent logical dependencies between nodes using fixed connections, such as process sequence and resource allocation. However, they cannot reflect dynamic changes in dependencies, such as the impact of task delays caused by equipment failures on upstream and downstream processes. For example, a delay in a certain equipment maintenance task may lead to a compression of the time window for multiple related tasks. However, existing technologies can only show whether there is a dependency, but cannot quantify the difference in the strength of the dependency. For instance, if the maintenance task of "replacing generator parts" is delayed, it will reduce the available time for subsequent tasks such as "parts testing" and "unit acceptance." However, existing systems can only draw a line to indicate that they are related, and cannot let administrators see that the impact of "replacing parts" on "unit acceptance" is actually more important than on "parts testing." In other words, they cannot show the difference in the strength of the dependency.

[0003] Lack of dynamic data fusion: Static dependency models cannot integrate historical execution data, such as actual task time and resource usage frequency, resulting in a lack of data support for dependency assessment. For example, a resource node may be frequently called in historical execution, but in the static model it may only be marked as a basic support unit, failing to reflect its actual importance. For instance, in the existing system, a support resource like a "maintenance wrench" is only marked as a "basic tool," but it is frequently used in actual application. However, the existing system does not include the historical usage of this tool, making it impossible for higher-privilege roles like administrators to know its importance and change its dependency on the importance of maintenance. In other words, without combining historical data, the dependency relationship cannot be determined.

[0004] The visualization dimension is limited: the visualization of dependency relationships usually only distinguishes whether they are related by the color or type of the line, and lacks a multi-dimensional mapping of the dependency strength; for example, the dependency strength of a task on an upstream node is 3 times that of another task, but the existing system cannot intuitively present this difference through visual differences.

[0005] Insufficient permission adaptation: Different roles, such as maintenance workers, dispatchers, and management, have different focuses on dependencies, but existing systems mostly adopt a "one-size-fits-all" display method, resulting in key information being buried by redundant data; for example, management needs a global overview of dependencies, while workers only need to focus on the local dependencies of their own tasks, and existing technology cannot dynamically adjust the visualization content according to permission levels.

[0006] To address the above issues, this invention proposes a method and system for visualizing and interacting with maintenance progress network diagrams. Summary of the Invention

[0007] The main objective of this invention is to provide a method and system for visualizing and interacting with maintenance progress network diagrams, thereby solving the problems mentioned in the background art.

[0008] To solve the above-mentioned technical problems, the technical solution adopted by the present invention is: a method for visualizing and interacting with a maintenance progress network diagram, comprising the following steps: S1. Construct a three-level progressively expanding tree-like hierarchical structure. Each node can trigger the expansion of the first-level thumbnail layer, the second-level task flow layer, and the third-level resource details layer in sequence by double-clicking. S2. Based on the preset role permission model, visibility control is performed on nodes at each level, and the access permissions of different roles to nodes are matched through the association mapping between roles and nodes. S3. Combine static logical dependencies with dynamic data mining results to calculate the dependency strength between nodes, and visualize the dependency strength through differences in connection styles; S4. Receive interactive operation commands triggered by the user through gesture operation, voice command and on-site positioning signal, and adjust the node time, select associated nodes and mark node status according to the command; S5. Real-time detection of resource allocation conflicts and time planning conflicts during node interaction operations, and generation of corresponding mediation schemes based on conflict parameters; S6. The network graph displayed on mobile devices is loaded using a segmented rendering method, and the rendering parameters are dynamically adjusted according to the device performance to optimize the display effect.

[0009] Furthermore, step S1 further includes the following steps: S101: Based on the management dimensions and data relationships of maintenance tasks, the technical attributes of the three-level nodes are defined as follows: The first-level node is the project management unit, which is associated with the phase boundary data of the maintenance project; the second-level node is the task execution unit, which is associated with the decomposed task data of the first-level node; the third-level node is the resource support unit, which is associated with the resource configuration data of the second-level node; each level of node is uniquely bound through preset hierarchical attribute tags, and each node's attribute tag contains a hierarchical identifier and a parent node association code. S102: A structured data model is used to store the relationships between three levels of nodes. Each node is configured with three technical parameters: a unique identifier code, a parent node code, and a hierarchy identifier. The parent node code points to the directly related parent node. The hierarchy identifier is used to distinguish between first-level, second-level, and third-level nodes. The parent node code of a first-level node is set to null. The parent node code of a second-level node matches the unique identifier code of its parent first-level node. The parent node code of a third-level node matches the unique identifier code of its parent second-level node. A chain relationship from first-level to second-level and then to third-level is established through an encoding mapping algorithm. S103: Configure a node interaction response mechanism based on node relationships. This mechanism receives user operation signals in real time and parses the operation type. When a trigger signal for a target node is detected, the hierarchical attribute of the node is read through a hierarchical identifier matching algorithm, and the corresponding child node expansion procedure is called. If it is a first-level node, the program retrieves the associated second-level node data based on its unique identifier code, switches the second-level node from the cached state to the display state, and positions the child node according to the radial layout algorithm. If it is a second-level node, the program retrieves the associated third-level node data and positions and displays it according to the linear extension layout algorithm. The expansion procedure is not executed when a third-level node is triggered. During the expansion process, the connection lines between the parent node and the child node are displayed through the connection rendering function, and the line attributes match the hierarchical association strength parameter.

[0010] Furthermore, step S2 further includes the following steps: S201: Preset role technical attribute parameters, including role unique identifier ID, permission level code, and operation permission set; among them, the permission level code is divided into three levels, corresponding to 01 basic view, 02 edit operation, and 03 global configuration permission; the operation permission set is identified by binary bits, and the operation permissions are further divided into view only, view plus edit, and full permission; S202: Based on the technical attributes of nodes and roles, a two-dimensional association matrix is ​​used to store the permission mapping relationship between roles and nodes, with matrix elements representing permission level codes. Simultaneously, a hash mapping algorithm is introduced to establish an index of role ID-node code-permission level. The algorithm logic is as follows: using the role ID plus the node code as the input to the hash function, and the permission level code as the output of the hash function, we have: Hash(role ID + node code) = permission level code. When a new role or node is added, the system automatically updates the association matrix and hash index. S203: Configure the permission verification mechanism. This mechanism receives the user role ID in real time and traverses the set of nodes in the current network graph. For each node, it queries the permission level code of the current role through the hash index. If the permission level code is 01, call the node status control interface to set the node to view-only; If the permission level code is 02, the node is set to view and edit, but editing of first-level nodes is restricted; If the permission level code is Null, then set the node to a hidden state; During the control process, recent query results are stored through a permission caching mechanism.

[0011] Furthermore, step S3 further includes the following steps: S301: Based on the hierarchical attributes of the nodes in S101, dependency types are distinguished: project-level nodes are phase dependencies, task-level nodes are process dependencies, and resource-level nodes and task-level nodes are support dependencies; then, basic weight coefficients are assigned to each, with the weight coefficient for phase dependencies being... The weighting coefficient for process dependence is The weighting coefficients supporting the dependency are ; Introducing process complexity coefficient correction factor This coefficient is dynamically set based on the stage boundary data, decomposed task data, and resource allocation data that define the association in S1. The formula for calculating the static dependency strength is as follows: Stage dependencies: (1); Process dependence: (2); Supporting dependencies: (3); in, , , These are the quantified values ​​of the static dependency strength between nodes at different levels; S302: Extract nodes from historical data based on the chained node sequence in S102. With nodes The execution sequence relationship is used to calculate dependency support, using the following formula: (4); in, For nodes and Dependency support reflects historical After completion The probability of starting; To contain simultaneously Complete and The number of startup history records; For historical maintenance data, including nodes Total number of all valid data entries; The total number of valid data entries refers to all historical maintenance data that meet the system's preset validity criteria and include nodes. The total number of completion records, regardless of whether nodes are included. Impact of startup status; Then, a time decay factor is introduced to correct the timeliness of the data, as shown in the following formula: (5); in, This is the time decay factor, with a value range of [0,1]. The time decay coefficient is dynamically configured according to the technical attributes of the three-level nodes described in S101, corresponding to the project level. Task level correspondence Resource level correspondence Each is adapted to the execution cycle of different node levels; Record the interval between the current time and the historical data. Finally, the dynamic strength is obtained by fusing the dependency support and the time decay factor. The calculation formula is as follows: (6); in, Represents a node and The dynamic dependency strength, with a value range of [0,1].

[0012] Furthermore, step S3 also includes: Step S303: Based on static dependency strength , , With dynamic dependency strength By using a weighted algorithm to fuse data and combining it with the role and permission settings of S2 to adapt and adjust the fusion parameters, the overall strength between nodes is obtained. The calculation formula is as follows: (7); in, This is a static weighting coefficient, with a value range of [0,1]. It is dynamically configured based on the role permission level defined in S201. Roles with permission level 03 can be manually set. The value, permission level 02, uses the system default. The value cannot be modified for characters with permission level 01. value; To determine the static dependency strength based on node hierarchy attributes, the phase dependencies between project-level nodes are... Process dependencies between task-level nodes Support dependencies between resource-level and task-level nodes ; During fusion, the values ​​of the weight coefficients are limited according to the type of the nodes: The first-level project control unit node corresponds to the preset first static weight coefficient range, which is bound to the process stability requirements of the stage boundary data through system preset; The nodes of the secondary task execution unit and the tertiary resource support unit correspond to the preset second static weight coefficient range, which is bound to the dynamic execution requirements of the decomposed task data and resource configuration data through system preset; Among them, the first static weight coefficient interval and the second static weight coefficient interval are non-overlapping intervals predefined by the system, and unique matching is achieved through node level identifiers; Fusion results The S203 permission verification mechanism is required; only roles with permission level 03 can view it. The calculation details show that characters with permission level 01 only receive... The final quantized value; S304: By using the system's preset mapping rules, the overall dependency strength will be determined. Convert to line width, style, and color parameters: line width and The numerical ranges form a direct proportional correspondence. The higher the value, the wider the parameter increases according to a preset gradient; the connection style is based on... Preset threshold switching, A solid line is drawn when the first threshold is reached, and a dashed line is drawn when the line falls within the second threshold range; the line color is based on... The numerical gradient is presented in the order of the international color sequence standard. The value change corresponds to a linear adjustment of the color channel value; The above mapping rules allow the connection style to directly reflect the dependency strength between nodes; simultaneously, combined with the S203 permission verification mechanism, roles with permission level 03 can view the style parameters and... The mapping logic and threshold settings allow roles with permission level 01 to only obtain visual style differences and not display parameter details.

[0013] Furthermore, S4 further includes the following steps: S401: Based on the configured multimodal interaction interface, receive the interaction quality triggered by the user through gesture operation, voice command and on-site positioning signal. The gesture operation corresponds to node selection and dragging, the voice command corresponds to node time adjustment and status marking, and the on-site positioning signal is used to match the physical workstation node corresponding to the current operation. All of the above operations require permission verification and can only be executed by roles with permission level 02 and above. S402: Based on the verified interaction command, adjust the node state update module: if it is a time adjustment command, synchronously trigger the comprehensive dependency strength of S303. Recalculate; if it is an associated node instruction, filter the target node based on the chained association relationship in S102; if it is a status marking instruction, update the status field in the node attribute label.

[0014] Furthermore, S5 further includes the following steps: S501. During interactive operations, conflict behaviors in system operation are detected in real time. Based on the comprehensive dependency strength S and node association relationships, two types of conflicts are detected: Resource allocation conflict: The same resource-level node is simultaneously associated with multiple task-level nodes, and the dependency strength exceeds the preset threshold; Time planning conflict: The time adjustment of task-level nodes causes the timing relationship between them and related nodes to violate the static dependency logic of S301; S502. For detected conflicts, based on the hierarchical attributes and dependency strength of the conflicting nodes... The numerical range generates a mediation scheme: In the event of a resource conflict, resources are preferentially allocated to tasks marked with the permission level 03 role based on permission level, and so on according to role level; in the event of a time conflict, the dynamic intensity is used as the basis for the mediation scheme. We recommend the time adjustment scheme with the lowest probability of conflict in the historical execution records, and update the time nodes synchronously.

[0015] Furthermore, S6 further includes the following steps: S601: The network graph displayed on mobile devices adopts a segmented rendering mechanism. The segmentation rules are based on the three-level node hierarchy attributes: the first-level project management unit is the top-level block, the second-level task execution unit is the secondary block, and the third-level resource support unit is the basic block; the node association relationship within the block is consistent with the chain association relationship. S602: Based on the separation rules, configure a dynamic adjustment mechanism for rendering parameters. This mechanism automatically adjusts the priority of block addition according to the performance indicators of the mobile device and the maximum power limit of the mobile processor. It prioritizes loading node blocks and rendering precision within the current role's permission range, while caching already rendered blocks to reduce redundant calculations.

[0016] The present invention also provides a maintenance progress network diagram visualization and interactive system to implement the steps in the above method, including a node hierarchy management module, a role and permission management module, a dependency strength calculation module, a dependency visualization mapping module, an interactive operation processing module, a conflict handling module, and a mobile terminal rendering optimization module.

[0017] Furthermore, the node hierarchy management module defines the technical attributes of first-level project control units, second-level task execution units, and third-level resource support units based on the management dimensions and data association relationships of maintenance tasks. It establishes chain associations through coding mapping algorithms and configures node interaction response mechanisms to ensure that double-clicking can trigger the expansion of the corresponding level, providing a data carrier for subsequent dependent calculations and access control. The role and permission management module presets the unique identifier ID, permission level code and operation permission set of the role, stores the permission mapping relationship through a two-dimensional association matrix and hash mapping algorithm, verifies the user role in real time and controls the node visibility, so as to realize the differentiated access of different roles to the node; The dependency strength calculation module distinguishes stage dependency, process dependency, and support dependency based on node hierarchy attributes, and quantifies static dependency strength by combining process complexity correction coefficient; it mines historical data based on chain node sequence, and calculates dynamic dependency strength through dependency support and time decay factor; finally, it integrates static and dynamic strengths through weighted fusion algorithm to quantify and integrate dependency relationships. The dependency visualization mapping module, based on preset mapping rules, transforms the comprehensive dependency strength S into the width, style, and color of the lines, and combines role-based permission control with visualization details to transform the abstract dependency strength into an intuitive visual signal. The interactive operation processing module receives instructions triggered by gestures, voice, and on-site positioning signals through a multimodal interaction interface. After authorization verification, it performs node time adjustment, associated node selection, and status marking operations, and simultaneously triggers dependency strength recalculation to achieve real-time interaction between the user and the network graph. The conflict resolution module, during interactive operations, is based on the comprehensive dependency strength. It associates nodes, detects resource allocation conflicts and time planning conflicts, and determines the relationship based on the hierarchical attributes of the conflicting nodes. Value generation mediation scheme; The mobile rendering optimization module adopts a block rendering mechanism based on three-level node hierarchy attributes, dynamically adjusts rendering priority and precision according to device performance, and caches rendered content to optimize the mobile display effect.

[0018] Beneficial effects: 1. By using a weighted fusion algorithm of static logical dependencies and dynamic data mining results, the strength of dependencies between nodes can be accurately quantified; 2. By calculating dependency support and time decay factor, historical execution data is incorporated into dynamic dependency strength; 3. By combining role-based access control with visual control, different roles see different information, which ensures that managers have a comprehensive view while avoiding frontline staff being disturbed by redundant data. This solves the problem of key information being buried due to the "one-size-fits-all" display of traditional systems. 4. The comprehensive dependency strength S is transformed into multi-dimensional visual signals such as the width, style, and color of the lines, which solves the problem that traditional systems cannot reflect dependency differences by relying on a single color or line type. Attached Figure Description

[0019] Figure 1 This is a flowchart illustrating a method for visualizing and interacting with a maintenance progress network diagram according to the present invention. Figure 2 This is a timing diagram of a maintenance progress network diagram visualization and interactive system according to the present invention. Detailed Implementation

[0020] Example 1 like Figures 1-2 As shown in the figure, this embodiment provides a method for visualizing and interacting with a maintenance progress network diagram, including the following steps: S1. Construct a three-level progressively expanding tree-like hierarchical structure. Each node, through a double-click operation, sequentially triggers the expansion of the first-level thumbnail layer, the second-level task flow layer, and the third-level resource details layer. The specific process is as follows: S101. Based on the management dimensions and data relationships of maintenance tasks, define the technical attributes of the three-level nodes. The technical attributes of the three-level nodes are as follows: The first-level node is the project management unit, which is associated with the phase boundary data of the maintenance project; the second-level node is the task execution unit, which is associated with the decomposed task data of the first-level node; the third-level node is the resource support unit, which is associated with the resource configuration data of the second-level node; each level of node is uniquely bound through preset hierarchical attribute tags, and each node's attribute tag contains a hierarchical identifier and a parent node association code. S102. A structured data model is used to store the association relationship of three-level nodes. Each node is configured with three technical parameters: unique identifier code, parent node code, and hierarchy identifier. Among them, the parent node code points to the directly associated parent node; the hierarchy identifier is used to distinguish between first-level, second-level, and third-level nodes; the parent node code of the first-level node is set to null, the parent node code of the second-level node matches the unique identifier code of its parent first-level node, and the parent node code of the third-level node matches the unique identifier code of its parent second-level node; and a chain association from first-level to second-level and then to third-level is established through an encoding mapping algorithm. S103. Based on the node association relationship, configure a node interaction response mechanism. This mechanism receives user operation signals in real time and parses the operation type. When a trigger signal for a target node is detected, the hierarchical attribute of the node is read through a hierarchical identifier matching algorithm, and the corresponding child node expansion program is called. If it is a first-level node, the program retrieves the associated second-level node data according to its unique identifier code, switches the second-level node from the cached state to the display state, and positions the child node according to the radial layout algorithm. If it is a second-level node, the program retrieves the associated third-level node data and positions and displays it according to the linear extension layout algorithm. The expansion program is not executed when a third-level node is triggered. During the expansion process, the connection lines between the parent node and the child node are displayed through the connection rendering function, and the line attributes match the hierarchical association strength parameter.

[0021] S2. Based on a preset role-based access control model, visibility control is implemented for nodes at each level. Access permissions for different roles to nodes are matched through the association mapping between roles and nodes. The specific process is as follows: S201. Preset role technical attribute parameters, including role unique identifier ID, permission level code, and operation permission set; among which, the permission level code is divided into three levels, corresponding to 01 basic view, 02 edit operation, and 03 global configuration permission respectively; the operation permission set is identified by binary bits, and the operation permissions are further divided into view only, view + edit, and full permissions; S202. Based on the node's technical attributes and the role's technical attributes, a two-dimensional association matrix is ​​used to store the permission mapping relationship between roles and nodes, with the matrix elements being permission level codes. At the same time, a hash mapping algorithm is introduced to establish an index of role ID-node code-permission level, with the algorithm logic being: Hash(role ID + node code) = permission level code. When a new role or node is added, the system automatically updates the association matrix and hash index. S203. Configure the permission verification mechanism. This mechanism receives the user role ID in real time and traverses the set of nodes in the current network graph. For each node, it queries the permission level code of the current role through the hash index. If the permission level code is 01, call the node status control interface to set the node to view-only; If the permission level code is 02, set the node to view + edit, but restrict editing of first-level nodes; If the permission level code is Null, then set the node to a hidden state; During the control process, recent query results are stored through a permission caching mechanism.

[0022] S3. Calculate the dependency strength between nodes by combining static logical dependencies and dynamic data mining results, and visualize the dependency strength through differences in connection styles. The specific process is as follows: S301. Based on the hierarchical attributes of the nodes in S101, determine the dependency types: project-level nodes are phase dependencies, task-level nodes are process dependencies, and resource-level nodes and task-level nodes are support dependencies; then assign basic weight coefficients to each, with the weight coefficient for phase dependencies being... The weighting coefficient for process dependence is The weighting coefficients supporting the dependency are ; Introducing process complexity coefficient correction factor This coefficient is dynamically set based on the stage boundary data, decomposed task data, and resource allocation data that define the association in S1. The formula for calculating the static dependency strength is as follows: Stage dependencies: (1); Process dependence: (2); Supporting dependencies: (3); in, , , These are the quantified values ​​of the static dependency strength between nodes at different levels; S302. Based on the chained node sequence in S102, extract nodes from the historical data. With nodes The execution sequence relationship is used to calculate dependency support, using the following formula: (4); in, For nodes and Dependency support reflects historical After completion The probability of starting; To contain simultaneously Complete and The number of startup history records; For historical maintenance data, including nodes Total number of all valid data entries; The total number of valid data entries refers to all historical maintenance data that meet the system's preset validity criteria and include nodes. The total number of completion records, regardless of whether nodes are included. Impact of startup status; Then, a time decay factor is introduced to correct the timeliness of the data, as shown in the following formula: (5); in, This is the time decay factor, with a value range of [0,1]. The time decay coefficient is dynamically configured according to the technical attributes of the three-level nodes described in S101, corresponding to the project level. Task level correspondence Resource level correspondence Each is adapted to the execution cycle of different node levels; Record the interval between the current time and the historical data. Finally, the dynamic strength is obtained by fusing the dependency support and the time decay factor. The calculation formula is as follows: (6); in, Represents a node and The dynamic dependency strength, with a value range of [0,1]; Step S303, based on static dependency strength , , With dynamic dependency strength By using a weighted algorithm to fuse data and combining it with the role and permission settings of S2 to adapt and adjust the fusion parameters, the overall strength between nodes is obtained. The calculation formula is as follows: (7); in, This is a static weighting coefficient, with a value range of [0,1]. It is dynamically configured based on the role permission level defined in S201. Roles with permission level 03 can be manually set. The value, permission level 02, uses the system default. The value cannot be modified for characters with permission level 01. value; To determine the static dependency strength based on node hierarchy attributes, the phase dependencies between project-level nodes are... Process dependencies between task-level nodes Support dependencies between resource-level and task-level nodes ; During fusion, the values ​​of the weight coefficients are limited according to the type of the nodes: The first-level project control unit node corresponds to the preset first static weight coefficient range, which is bound to the process stability requirements of the stage boundary data through system preset; The nodes of the secondary task execution unit and the tertiary resource support unit correspond to the preset second static weight coefficient range, which is bound to the dynamic execution requirements of the decomposed task data and resource configuration data through system preset; Among them, the first static weight coefficient interval and the second static weight coefficient interval are non-overlapping intervals predefined by the system, and unique matching is achieved through node level identifiers; Fusion results The S203 permission verification mechanism is required; only roles with permission level 03 can view it. The calculation details show that characters with permission level 01 only receive... The final quantized value; S304. By using the system's preset mapping rules, the overall dependency strength is determined. Convert to line width, style, and color parameters: line width and The numerical ranges form a direct proportional correspondence. The higher the value, the wider the parameter increases according to a preset gradient; the connection style is based on... Preset threshold switching, A solid line represents the area reaching the first threshold, while a dashed line represents the area within the second threshold range. The first and second thresholds are adaptively set by users with permission level 03 based on different projects. The line color is based on... The numerical gradient is presented in the order of the international color sequence standard. The value change corresponds to a linear adjustment of the color channel value.

[0023] The above mapping rules enable the connection style to directly reflect the dependency strength between nodes; at the same time, combined with the permission verification mechanism of S203, the role with permission level 03 can view the mapping logic between the style parameters and S and the threshold setting, while the role with permission level 01 can only obtain the visual differences of the style and does not display parameter details.

[0024] S4. Receive interactive operation commands triggered by the user through gestures, voice commands, and on-site positioning signals. Based on the commands, adjust the node time, select associated nodes, and mark node status. The specific process is as follows: S401: Based on the configured multimodal interaction interface, receive the interaction quality triggered by the user through gesture operation, voice command and on-site positioning signal. The gesture operation corresponds to node selection and dragging, the voice command corresponds to node time adjustment and status marking, and the on-site positioning signal is used to match the physical workstation node corresponding to the current operation. All of the above operations require permission verification and can only be executed by roles with permission level 02 and above. S402: Based on the verified interaction command, adjust the node state update module: if it is a time adjustment command, synchronously trigger the comprehensive dependency strength of S303. Recalculate; if it is an associated node instruction, filter the target node based on the chained association relationship in S102; if it is a status marking instruction, update the status field in the node attribute label.

[0025] S5. During node interaction operations, resource allocation conflicts and time planning conflicts are detected in real time, and corresponding mediation schemes are generated based on the conflict parameters. The detailed steps are as follows: S501. During interactive operations, conflict behaviors in system operation are detected in real time. Based on the comprehensive dependency strength S and node association relationships, two types of conflicts are detected: Resource allocation conflict: The same resource-level node is simultaneously associated with multiple task-level nodes, and the dependency strength exceeds the preset threshold; Time planning conflict: The time adjustment of task-level nodes causes the timing relationship between them and related nodes to violate the static dependency logic of S301; S502. For detected conflicts, based on the hierarchical attributes and dependency strength of the conflicting nodes... The numerical range generates a mediation scheme: In the event of a resource conflict, resources are preferentially allocated to tasks marked with the permission level 03 role based on permission level, and so on according to role level; in the event of a time conflict, the dynamic intensity is used as the basis for the mediation scheme. We recommend the time adjustment scheme with the lowest probability of conflict in the historical execution records, and update the time nodes synchronously. S6. The network graph displayed on mobile devices is loaded using a chunked rendering method, and the rendering parameters are dynamically adjusted according to device performance to optimize the display effect. The detailed steps are as follows: S601. The network graph displayed on the mobile terminal adopts a block rendering mechanism. The block division rule is based on the three-level node hierarchy attributes: the first-level project management unit is the top-level block, the second-level task execution unit is the secondary block, and the third-level resource support unit is the basic block; the node association relationship within the block is consistent with the chain association relationship. S602. According to the separation rules, configure a dynamic adjustment mechanism for rendering parameters. This mechanism automatically adjusts the priority of block addition based on the performance indicators of the mobile device and the maximum power limit of the mobile processor. Prioritizes loading node blocks and rendering precision within the current role's permission range, while caching already rendered blocks to reduce redundant calculations.

[0026] This embodiment also provides a maintenance progress network diagram visualization and interactive system, including a node hierarchy management module, a role and permission management module, a dependency strength calculation module, a dependency visualization mapping module, an interactive operation processing module, a conflict handling module, and a mobile rendering optimization module.

[0027] The node-level management module defines the technical attributes of nodes at the first-level project control unit, the second-level task execution unit, and the third-level resource support unit based on the management dimensions and data relationships of maintenance tasks. It establishes chain-like associations through coding mapping algorithms and configures node interaction response mechanisms to ensure that double-clicking can trigger the expansion of the corresponding level, providing a data carrier for subsequent dependent calculations and access control. The role and permission management module presets the unique identifier ID, permission level code and operation permission set of each role. It stores the permission mapping relationship through a two-dimensional association matrix and hash mapping algorithm, verifies user roles in real time and controls node visibility, and realizes differentiated access to nodes for different roles. The dependency strength calculation module distinguishes stage dependency, process dependency, and support dependency based on node hierarchy attributes, and quantifies static dependency strength by combining process complexity correction coefficient; it mines historical data based on chain node sequence and calculates dynamic dependency strength through dependency support and time decay factor; finally, it integrates static and dynamic strengths through weighted fusion algorithm to quantify and integrate dependency relationships. The dependency visualization mapping module, based on preset mapping rules, transforms the overall dependency strength S into the width, style, and color of the lines, and combines role-based access control with visualization details to transform the abstract dependency strength into an intuitive visual signal. The interactive operation processing module receives commands triggered by gestures, voice, and on-site positioning signals through a multimodal interaction interface. After authorization verification, it performs node time adjustment, associated node selection, and status marking operations, and simultaneously triggers dependency strength recalculation to achieve real-time interaction between the user and the network graph. In interactive operations, the conflict resolution module detects resource allocation conflicts and time planning conflicts based on the comprehensive dependency strength S and the node association relationship, and generates a mediation scheme according to the conflict node hierarchy attributes and S value. The mobile rendering optimization module adopts a block rendering mechanism based on three-level node hierarchy attributes. It dynamically adjusts the rendering priority and precision according to device performance and caches rendered content to optimize the display effect on mobile devices.

[0028] Example 2 This embodiment provides a specific implementation process for a method and system for visualizing and interacting with maintenance progress network diagrams. First, a three-level progressively unfolding tree-like hierarchical structure is constructed. The first-level node is the "Generator Set Maintenance Project," serving as the project management unit. It is associated with the boundary data of the six stages: maintenance preparation, disassembly, testing, repair, assembly, and trial operation. Its unique identifier is XM001, the parent node is set to null, and the hierarchical identifier is L1. The second-level nodes, decomposed from the first-level nodes, include task execution units such as "Disassembly Operation" and "Parts Inspection." Taking "Disassembly Operation" as an example, its unique identifier is RW001, the parent node matches XM001, and the hierarchical identifier is L2, associating with disassembly steps, required man-hours, and other decomposed task data. The third-level nodes are resource support units, such as maintenance tools like "Hydraulic Wrench" and "Ultrasonic Detector." The unique identifier for "Hydraulic Wrench" is ZY001, the parent node matches RW001, and the hierarchical identifier is L3, associating with equipment model, usage period, and other resource configuration data.

[0029] Each level of node is uniquely bound by an attribute label containing a level identifier and a parent node association code, and then a chain association is established through an encoding mapping algorithm. When a user double-clicks a first-level node XM001, the system retrieves the associated second-level nodes based on its unique identifier code, switches these second-level nodes from the cached state to the displayed state according to the radial layout algorithm, and maintains the association with the first-level node through line rendering, with the line attributes matching the level association strength parameter; double-clicking a second-level node RW001 expands the third-level node according to the linear extension layout algorithm, but the expansion procedure is not executed when the third-level node is triggered.

[0030] Next, node visibility control is implemented based on a preset role-based permission model. The system presets roles including dispatcher (permission level 03), maintenance worker (permission level 02), and intern (permission level 01). Each role has a unique ID, and the set of operation permissions is identified by binary bits. Dispatchers have full access, maintenance workers have view and edit permissions, and interns have only view permissions. A two-dimensional association matrix is ​​used to store the permission mapping relationship between roles and nodes, and a hash mapping algorithm is introduced, such as Hash(Dispatcher ID + XM001) = 03. When a dispatcher logs into the system, the permission verification mechanism traverses the current network graph nodes, and through the hash index, finds that their permission level code is 03 or 02. Therefore, the dispatcher can view and edit all nodes except for first-level nodes, and can see all nodes. After logging in, maintenance workers can only view first-level nodes and can edit second- and third-level nodes. After logging in, some nodes are hidden because their permission level code is null, and interns can only view specific nodes. The system also uses a permission caching mechanism to store recent query results, improving permission verification efficiency.

[0031] Then calculate the dynamic dependency strength and extract the "decomposition operation" from the historical data, i.e., the node. i， With "part inspection", i.e., node j The execution sequence relationship, which also includes i Complete and j Startup history count N ij 180, including i Total number of all valid data entries N total If the value is 200, then it depends on the support. S ij =180 / 200=0.9. Historical data was recorded 6 months ago; this is the task-level time decay factor. k 2 is 0.1, the time decay factor. λ =e^(-0.1×6)=0.5488, dynamic intensity W d=0.9×0.5488≈0.4939. The dispatcher sets the static weight coefficient α to 0.7, and the overall strength S = 0.7×0.72 + (1-0.7)×0.4939≈0.652. According to the mapping rule, S The value is 0.652. Within the range of 0.6 to 0.8, the corresponding line width is medium. Lines exceeding the first threshold of 0.5 are displayed as solid lines, and the color is orange. The scheduler can view this mapping logic and threshold settings, while interns can only see the visual difference of the orange solid line.

[0032] In terms of user interaction, the system receives instructions through a multimodal interface. Maintenance workers can select the "Part Inspection" node via gesture dragging, and after authorization, can execute the operation. By giving the voice command "Postpone the part inspection task for 2 days," the system adjusts the node status update module and simultaneously triggers the comprehensive dependency strength adjustment. S Recalculate; the on-site positioning signal is matched to the physical work station node corresponding to the "hydraulic wrench", making it convenient for maintenance workers to operate.

[0033] During the interaction, the system detects conflicts in real time and generates mediation solutions. When the "hydraulic wrench" is simultaneously associated with two task-level nodes, "disassembly operation" and "parts cleaning," and both dependencies exceed the preset threshold of 0.6, a resource allocation conflict occurs. The system prioritizes allocating it to the "disassembly operation" task marked by the scheduler based on permission levels. If the time adjustment of the "parts inspection" task causes a violation of static dependency logic in its timing relationship with "maintenance operation," resulting in a time planning conflict, the system determines the conflict based on dynamic strength. W d We recommend the time adjustment scheme with the lowest probability of conflict in the historical execution records, which will postpone the "maintenance work" by 1 day and update the time node accordingly.

[0034] For mobile display, the system employs a chunked rendering mechanism. The first-level node "Generator Set Maintenance Project" is the top-level block, second-level nodes such as "Disassembly Operation" are secondary blocks, and third-level nodes such as "Hydraulic Wrench" are basic blocks. When a maintenance worker logs into the system using a mobile phone, the system automatically adjusts the chunk loading priority based on the phone's processor's maximum power limit. It prioritizes loading the "Disassembly Operation" secondary block and its associated third-level basic block, which are within the maintenance worker's authorized scope. This ensures rendering accuracy is adapted to the phone's performance, while caching already rendered blocks reduces redundant calculations and optimizes the display effect.

[0035] Through the application of this system, the annual maintenance project of the generator units of the Yangtze Power hydropower station has achieved visualized management of the maintenance progress. Different roles can obtain information as needed, the dependencies are clearly presented, the interactive operation is convenient and efficient, conflicts can be mediated in a timely manner, and the mobile terminal display is smooth, which significantly improves the efficiency of maintenance management.

[0036] The above embodiments are merely preferred technical solutions of the present invention and should not be considered as limitations on the present invention. The scope of protection of the present invention should be limited to the technical solutions described in the claims, including equivalent substitutions of the technical features described in the claims. That is, equivalent substitutions and improvements within this scope are also within the scope of protection of the present invention.

Claims

1. A method for visualizing and interacting with a maintenance progress network diagram, characterized in that: Includes the following steps: S1. Construct a three-level progressively expanding tree-like hierarchical structure. Each node can trigger the expansion of the first-level thumbnail layer, the second-level task flow layer, and the third-level resource details layer in sequence by double-clicking. S2. Based on the preset role permission model, visibility control is performed on nodes at each level, and the access permissions of different roles to nodes are matched through the association mapping between roles and nodes. S3. Combine static logical dependencies with dynamic data mining results to calculate the dependency strength between nodes, and visualize the dependency strength through differences in connection styles; S4. Receive interactive operation commands triggered by the user through gesture operation, voice command and on-site positioning signal, and adjust the node time, select associated nodes and mark node status according to the command; S5. Real-time detection of resource allocation conflicts and time planning conflicts during node interaction operations, and generation of corresponding mediation schemes based on conflict parameters; S6. The network graph displayed on mobile devices is loaded using a segmented rendering method, and the rendering parameters are dynamically adjusted according to the device performance to optimize the display effect.

2. The method for visualizing and interacting with a maintenance progress network diagram according to claim 1, characterized in that: Step S1 further includes the following steps: S101. Based on the management dimensions and data relationships of maintenance tasks, the technical attributes of the three-level nodes are defined as follows: The first-level node is the project management unit, which is associated with the phase boundary data of the maintenance project; the second-level node is the task execution unit, which is associated with the decomposed task data of the first-level node; the third-level node is the resource support unit, which is associated with the resource configuration data of the second-level node; each level of node is uniquely bound through preset hierarchical attribute tags, and each node's attribute tag contains a hierarchical identifier and a parent node association code. S102. A structured data model is used to store the association relationship of three-level nodes. Each node is configured with three technical parameters: unique identifier code, parent node code, and hierarchy identifier. Among them, the parent node code points to the directly associated parent node; the hierarchy identifier is used to distinguish between first-level, second-level, and third-level nodes; the parent node code of the first-level node is set to null, the parent node code of the second-level node matches the unique identifier code of its parent first-level node, and the parent node code of the third-level node matches the unique identifier code of its parent second-level node; and a chain association from first-level to second-level and then to third-level is established through an encoding mapping algorithm. S103. Based on the node association relationship, configure a node interaction response mechanism. This mechanism receives user operation signals in real time and parses the operation type. When a trigger signal for a target node is detected, the hierarchical attribute of the node is read through a hierarchical identifier matching algorithm, and the corresponding child node expansion program is called. If it is a first-level node, the program retrieves the associated second-level node data according to its unique identifier code, switches the second-level node from the cached state to the display state, and positions the child node according to the radial layout algorithm. If it is a second-level node, the program retrieves the associated third-level node data and positions and displays it according to the linear extension layout algorithm. The expansion program is not executed when a third-level node is triggered. During the expansion process, the connection lines between the parent node and the child node are displayed through the connection rendering function, and the line attributes match the hierarchical association strength parameter.

3. The method for visualizing and interacting with a maintenance progress network diagram according to claim 1, characterized in that: Step S2 further includes the following steps: S201. Preset role technical attribute parameters, including role unique identifier ID, permission level code, and operation permission set; among which, the permission level code is divided into three levels, corresponding to 01 basic view, 02 edit operation, and 03 global configuration permission respectively; the operation permission set is identified by binary bits, and the operation permissions are further divided into view only, view plus edit, and full permission; S202. Based on the node's technical attributes and the role's technical attributes, a two-dimensional association matrix is ​​used to store the permission mapping relationship between roles and nodes, with the matrix elements being permission level codes. Simultaneously, a hash mapping algorithm is introduced to establish an index of role ID-node code-permission level. The algorithm logic is as follows: the role ID plus the node code is used as the input to the hash function, and the permission level code is used as the output of the hash function. When a new role or node is added, the system automatically updates the association matrix and the hash index. S203. Configure the permission verification mechanism. This mechanism receives the user role ID in real time and traverses the set of nodes in the current network graph. For each node, it queries the permission level code of the current role through the hash index. If the permission level code is 01, call the node status control interface to set the node to view-only; If the permission level code is 02, the node is set to view and edit, but editing of first-level nodes is restricted; If the permission level code is Null, then set the node to a hidden state; During the control process, recent query results are stored through a permission caching mechanism.

4. The interactive visualization method for maintenance progress network diagrams according to claim 2 or 3, characterized in that: Step S3 further includes the following steps: S301. Based on the hierarchical attributes of the nodes in S101, determine the dependency types: project-level nodes are phase dependencies, task-level nodes are process dependencies, and resource-level nodes and task-level nodes are support dependencies; then assign basic weight coefficients to each, with the weight coefficient for phase dependencies being... The weighting coefficient for process dependence is The weighting coefficients supporting the dependency are ; Introducing process complexity coefficient correction coefficient This coefficient is dynamically set based on the stage boundary data, decomposed task data, and resource allocation data that define the association in S1. The formula for calculating the static dependency strength is as follows: Stage dependencies: （1）； Process dependence: （2）； Supporting dependencies: （3）； in, , , These are the quantified values ​​of the static dependency strength between nodes at different levels; S302. Based on the chained node sequence in S102, extract nodes from the historical data. With nodes The execution sequence relationship is used to calculate dependency support, using the following formula: （4）； in, For nodes and Dependency support reflects historical After completion The probability of starting; To contain simultaneously Complete and The number of startup history records; For historical maintenance data, including nodes Total number of all valid data entries; The total number of valid data entries refers to all historical maintenance data that meet the system's preset validity criteria and include nodes. The total number of completion records, regardless of whether nodes are included. Impact of startup status; Then, a time decay factor is introduced to correct the timeliness of the data, as shown in the following formula: （5）； in, This is the time decay factor, with a value range of [0,1]. The time decay coefficient is dynamically configured according to the technical attributes of the three-level nodes described in S101, corresponding to the project level. Task level correspondence Resource level correspondence Each is adapted to the execution cycle of different node levels; Record the interval between the current time and the historical data. Finally, the dynamic strength is obtained by fusing the dependency support and the time decay factor. The calculation formula is as follows: （6）； in, Represents a node and The dynamic dependency strength, with a value range of [0,1].

5. The interactive visualization method for maintenance progress network diagrams according to claim 4, characterized in that: Step S3 also includes: Step S303, based on static dependency strength , , With dynamic dependency strength By using a weighted algorithm to fuse data and combining it with the role and permission settings of S2 to adapt and adjust the fusion parameters, the overall strength between nodes is obtained. The calculation formula is as follows: （7）； in, This is a static weighting coefficient, with a value range of [0,1]. It is dynamically configured based on the role permission level defined in S201. Roles with permission level 03 can be manually set. The value, permission level 02, uses the system default. The value cannot be modified for characters with permission level 01. value; To determine the static dependency strength based on node hierarchy attributes, the phase dependencies between project-level nodes are... Process dependencies between task-level nodes Support dependencies between resource-level and task-level nodes ; During fusion, the values ​​of the weight coefficients are limited according to the type of the nodes: The first-level project control unit node corresponds to the preset first static weight coefficient range, which is bound to the process stability requirements of the stage boundary data through system preset; The nodes of the secondary task execution unit and the tertiary resource support unit correspond to the preset second static weight coefficient range, which is bound to the dynamic execution requirements of the decomposed task data and resource configuration data through system preset; Among them, the first static weight coefficient interval and the second static weight coefficient interval are non-overlapping intervals predefined by the system, and unique matching is achieved through node level identifiers; Fusion results The S203 permission verification mechanism is required; only roles with permission level 03 can view it. The calculation details show that characters with permission level 01 only receive... The final quantized value; S304. By using the system's preset mapping rules, the overall dependency strength is determined. Convert to line width, style, and color parameters: line width and The numerical ranges form a direct proportional correspondence. The higher the value, the wider the parameter increases according to a preset gradient; the connection style is based on... Preset threshold switching, A solid line represents the area reaching the first threshold, while a dashed line represents the area within the second threshold range. The first and second thresholds are adaptively set by users with permission level 03 based on different projects. The line color is based on... The numerical gradient is presented in the order of the international color sequence standard. The value change corresponds to a linear adjustment of the color channel value.

6. The method for visualizing and interacting with a maintenance progress network diagram according to claim 5, characterized in that: S4 further includes the following steps: S401. Based on the configured multimodal interaction interface, receive the interaction quality triggered by the user through gesture operation, voice command and on-site positioning signal. The gesture operation corresponds to node selection and dragging, the voice command corresponds to node time adjustment and status marking, and the on-site positioning signal is used to match the physical workstation node corresponding to the current operation. All of the above operations require permission verification and can only be executed by roles with permission level 02 and above. S402. Based on the verified interaction command, adjust the node state update module: if it is a time adjustment command, synchronously trigger the comprehensive dependency strength of S303. Recalculate; if it is an associated node instruction, filter the target node based on the chained association relationship in S102; if it is a status marking instruction, update the status field in the node attribute label.

7. The method for visualizing and interacting with a maintenance progress network diagram according to claim 4, characterized in that: S5 further includes the following steps: S501. During interactive operations, conflict behaviors in system operation are detected in real time. Based on the comprehensive dependency strength S and node association relationships, two types of conflicts are detected: Resource allocation conflict: The same resource-level node is simultaneously associated with multiple task-level nodes, and the dependency strength exceeds the preset threshold; Time planning conflict: The time adjustment of task-level nodes causes the timing relationship between them and related nodes to violate the static dependency logic of S301; S502. For detected conflicts, based on the hierarchical attributes and dependency strength of the conflicting nodes... The numerical range generates a mediation scheme: In the event of a resource conflict, resources are preferentially allocated to tasks marked with the permission level 03 role based on permission level, and so on according to role level; in the event of a time conflict, the dynamic intensity is used as the basis for the mediation scheme. We recommend the time adjustment scheme with the lowest probability of conflict in the historical execution records, and update the time nodes synchronously.

8. The method for visualizing and interacting with a maintenance progress network diagram according to claim 1, characterized in that: S6 further includes the following steps: S601. The network graph displayed on the mobile terminal adopts a block rendering mechanism. The block division rule is based on the three-level node hierarchy attributes: the first-level project management unit is the top-level block, the second-level task execution unit is the secondary block, and the third-level resource support unit is the basic block; the node association relationship within the block is consistent with the chain association relationship. S602. According to the separation rules, configure a dynamic adjustment mechanism for rendering parameters. This mechanism automatically adjusts the priority of block addition based on the performance indicators of the mobile device and the maximum power limit of the mobile processor. Prioritizes loading node blocks and rendering precision within the current role's permission range, while caching already rendered blocks to reduce redundant calculations.

9. A maintenance progress network diagram visualization and interactive system for implementing the steps in the method according to any one of claims 1 to 8, characterized in that: It includes a node hierarchy management module, a role and permission management module, a dependency strength calculation module, a dependency visualization mapping module, an interactive operation processing module, a conflict handling module, and a mobile rendering optimization module.

10. The maintenance progress network diagram visualization and interactive system according to claim 9, characterized in that: The node hierarchy management module defines the technical attributes of first-level project control units, second-level task execution units, and third-level resource support units based on the management dimensions and data associations of maintenance tasks. It establishes chain associations through coding mapping algorithms and configures node interaction response mechanisms to ensure that double-clicking can trigger the expansion of the corresponding level, providing a data carrier for subsequent dependent calculations and access control. The role and permission management module presets the unique identifier ID, permission level code and operation permission set of the role, stores the permission mapping relationship through a two-dimensional association matrix and hash mapping algorithm, verifies the user role in real time and controls the node visibility, so as to realize the differentiated access of different roles to the node; The dependency strength calculation module distinguishes stage dependency, process dependency, and support dependency based on node hierarchy attributes, and quantifies static dependency strength by combining process complexity correction coefficient. Historical data is mined based on chain node sequences, and dynamic dependency strength is calculated by dependency support and time decay factor. Finally, a weighted fusion algorithm is used to integrate static and dynamic strengths to quantify and integrate dependencies. The dependency visualization mapping module, based on preset mapping rules, transforms the comprehensive dependency strength S into the width, style, and color of the lines, and combines role-based permission control with visualization details to transform the abstract dependency strength into an intuitive visual signal. The interactive operation processing module receives instructions triggered by gestures, voice, and on-site positioning signals through a multimodal interaction interface. After authorization verification, it performs node time adjustment, associated node selection, and status marking operations, and simultaneously triggers dependency strength recalculation to achieve real-time interaction between the user and the network graph. The conflict resolution module, during interactive operations, is based on the comprehensive dependency strength. It associates nodes, detects resource allocation conflicts and time planning conflicts, and determines the relationship based on the hierarchical attributes of the conflicting nodes. Value generation mediation scheme; The mobile rendering optimization module adopts a block rendering mechanism based on three-level node hierarchy attributes, dynamically adjusts rendering priority and precision according to device performance, and caches rendered content to optimize the mobile display effect.

Images