Cross-system data object association and consistency maintenance method and system

Abstract

The invention discloses a cross-system data object association and consistency maintenance method and system, and the method comprises the steps: recognizing a downstream federated data object associated with an engineering drawing when the change of the engineering drawing is detected, and setting a cross-system dependency mapping model, calculating a final propagation influence score of a process node corresponding to the engineering drawing on each federal data object after multi-hop propagation; according to the final propagation influence score, the corresponding federal data object is controlled, and the control operation comprises the steps of locking the federal data object, giving an alarm and switching to manual examination and approval or sending notification information; and when the control operation is to lock the federal data object or give an alarm and transfer to manual examination and approval, synchronously modifying the locked federal data object or unlocking after the locked federal data object passes the examination and approval.

Description

Technical Field

[0001] This invention belongs to the field of consistency maintenance technology for engineering drawing changes, and more specifically, relates to a method and system for cross-system data object association and consistency maintenance. Background Technology

[0002] In existing technologies, engineering drawings and related business data are typically linked and synchronized between different information systems (such as PDM / PLM, ERP, MES, procurement systems, BOM, process cards, supplier platforms, etc.) in a point-to-point or limited integration manner. Although these systems each undertake key functions such as R&D design, production execution, resource management, and procurement supply, in actual operation, the lack of a unified cross-system dependency modeling and impact propagation mechanism often leads to problems such as delayed, incomplete, or error-proliferated information transmission when drawings are changed or versions are iterated. Existing solutions mostly rely on static rule configurations (such as BOM reference relationships and process route bindings), which can only reflect the surface-level direct dependencies. The existing methods are prone to errors, making it difficult to identify indirect dependencies across domains and systems, and even more difficult to measure the strength of dependencies and the scope of their impact. Therefore, when drawings are modified, the purchase orders in the ERP system, the work orders in the MES system, or the supplier data may not be accurately and timely detected, which can easily lead to the risk of the execution layer using outdated data. In addition, existing methods often simply bind the freezing and notification mechanisms to the BOM level, lacking comprehensive consideration based on multiple dimensions such as semantic similarity, historical covariance frequency, and time sensitivity. This can lead to problems of "over-freezing" or "missed locking," which on the one hand seriously reduces the operational efficiency of enterprises, and on the other hand may allow key objects to be modified uncontrollably, ultimately causing the spread of change risks, production plan delays, and inefficient supply chain collaboration.

[0003] Therefore, there is an urgent need for a technical solution that can solve the above technical problems. Summary of the Invention

[0004] To address the above technical problems, this invention proposes a method for cross-system data object association and consistency maintenance, comprising: When a change in the engineering drawing is detected, the downstream federated data objects associated with the engineering drawing are identified, and a cross-system dependency mapping model is set up to calculate the final propagation impact score of each federated data object after the process node corresponding to the engineering drawing has undergone multi-hop propagation. Based on the final propagation impact score, control operations are performed on the corresponding federated data objects, including: locking the federated data object, issuing an alarm and transferring it to manual approval or sending a notification message; When the control operation is to lock the federal data object or issue an alarm and transfer it to manual approval, the locked federal data object is modified or approved simultaneously, and then the lock is released.

[0005] Furthermore, identifying downstream federated data objects associated with the engineering drawings includes generating a dependency graph using the engineering drawings and federated data objects as process nodes and references / dependencies as directed edges.

[0006] Furthermore, before identifying the downstream federated data objects associated with the engineering drawings, the process includes locking the engineering drawings when a change is detected in the approval system to prevent modifications to the engineering drawings before approval is completed.

[0007] Furthermore, the cross-system dependency mapping model includes: , in, Process nodes corresponding to engineering drawings After multi-hop propagation, the federal data object The final propagation affects the score. The total number of hops in the propagation path. For the propagation path The attenuation factor of the jump, To start from process nodes To Federal Data Objects The transmission path, For a certain edge on the propagation path The strength, Process nodes corresponding to engineering drawings Transmission path The impact score of the first federal data object.

[0008] Furthermore, the corresponding process nodes in the engineering drawings. Transmission path Impact score of the first federal data object include: , in, The weights of directly connected flag values, process node and transmission path The first directly linked flag value of the federated data object, if the process node If directly linked to the first federated data object, then =1, otherwise =0, Weights for semantic similarity process node Metadata and propagation path The semantic similarity of the metadata of the first federal data object, The weights for historical covariance frequencies. process node and transmission path The historical covariance frequency of the first federal data object, As a weight for time sensitivity, process node and transmission path The time sensitivity of the first federal data object This is the sigmoid function.

[0009] Furthermore, a certain side of the transmission path intensity include: , in, Historically, due to a certain border One end of the federal data object Changes that cause a certain edge The other end of the federal data object The number of times the changes are synchronized. for Upstream, For a certain border in history One end of the federal data object Total number of changes.

[0010] Furthermore, based on the final propagation impact score, the control operations on the corresponding federated data objects include: locking the federated data object when the final propagation impact score is greater than or equal to a preset first threshold; issuing an alarm and transferring the application to manual approval when the final propagation impact score is less than the preset first threshold but greater than or equal to a preset second threshold; and sending a notification message when the final propagation impact score is less than the preset second threshold.

[0011] This invention also proposes a cross-system data object association and consistency maintenance system, comprising: The impact score calculation module is used to identify downstream federated data objects associated with the engineering drawings when a change is detected, and to set up a cross-system dependency mapping model to calculate the final propagation impact score of each federated data object after the process node corresponding to the engineering drawings has undergone multi-hop propagation. The control module is used to perform control operations on the corresponding federated data objects based on the final propagation impact score. The control operations include: locking the federated data object, issuing an alarm and transferring it to manual approval or sending a notification message. The consistency maintenance module is used to simultaneously modify the locked federated data object or release the lock after approval when the control operation is to lock the federated data object or trigger an alarm and transfer it to manual approval.

[0012] Furthermore, identifying downstream federated data objects associated with the engineering drawings includes generating a dependency graph using the engineering drawings and federated data objects as process nodes and references / dependencies as directed edges.

[0013] Furthermore, before identifying the downstream federated data objects associated with the engineering drawings, the process includes locking the engineering drawings when a change is detected in the approval system to prevent modifications to the engineering drawings before approval is completed.

[0014] In summary, the technical solutions conceived by this invention have the following beneficial effects compared with the prior art: When a drawing is changed, the system not only locks the drawing itself, but also automatically identifies and locks all downstream associated federated data objects (such as purchase orders in ERP and work-in-process orders in MES). After the change process is completed, the data is automatically and synchronously unlocked and updated in all associated systems. Attached Figure Description

[0015] Figure 1 This is a flowchart of the method in Embodiment 1 of the present invention; Figure 2 This is a system structure diagram of Embodiment 2 of the present invention. Detailed Implementation

[0016] To better understand the above technical solutions, the following will provide a detailed explanation of the technical solutions in conjunction with the accompanying drawings and specific implementation methods.

[0017] The method provided by this invention can be implemented in a terminal environment that may include one or more of the following components: a processor, a storage medium, and a display screen. The storage medium stores at least one instruction, which is loaded and executed by the processor to implement the method described in the following embodiments.

[0018] A processor may include one or more processing cores. The processor uses various interfaces and lines to connect various parts of the terminal, and performs various functions and processes data by running or executing instructions, programs, code sets or instruction sets stored in the storage medium, and by calling data stored in the storage medium.

[0019] Storage media can include random access memory (RAM) or read-only memory (ROM). Storage media can be used to store instructions, programs, code, code sets, or instructions.

[0020] The display screen is used to show the user interface of each application.

[0021] In addition, those skilled in the art will understand that the above-described structure of the terminal does not constitute a limitation on the terminal. The terminal may include more or fewer components, or combine certain components, or have different component arrangements. For example, the terminal may also include radio frequency circuits, input units, sensors, audio circuits, power supplies, and other components, which will not be described in detail here.

[0022] Example 1 like Figure 1 As shown, this embodiment proposes a method for cross-system data object association and consistency maintenance, including: Step 101: When a change in the engineering drawing is detected, identify the downstream federated data objects associated with the engineering drawing, set up a cross-system dependency mapping model, and calculate the final propagation impact score of each federated data object after the process node corresponding to the engineering drawing has undergone multi-hop propagation. Preferably, for example, the federated data object can be an ERP purchase order, MES work order, etc. If the engineering drawings are changed, the ERP purchase order, MES work order, etc. may also need to be changed.

[0023] Specifically, identifying the downstream federated data objects associated with the engineering drawings includes generating a dependency graph using the engineering drawings and federated data objects as process nodes and references / dependencies as directed edges.

[0024] Specifically, before identifying the downstream federated data objects associated with the engineering drawings, the process also includes locking the engineering drawings when a change is detected in the approval system to prevent modifications to the engineering drawings before approval is completed.

[0025] Step 102: Based on the final propagation impact score, perform control operations on the corresponding federated data objects, wherein the control operations include: locking the federated data object, issuing an alarm and transferring it to manual approval or sending a notification message; Specifically, the cross-system dependency mapping model includes: , in, Process nodes corresponding to engineering drawings After multi-hop propagation, the federal data object The final propagation affects the score. This represents the total number of hops in the propagation path (generally limited to 3-5). For the propagation path The attenuation factor of the jump (with a value ranging from 0.5 to 0.8) indicates that the further the jump, the weaker the effect. To start from process nodes To Federal Data Objects The transmission path, For a certain edge on the propagation path The strength, Process nodes corresponding to engineering drawings Transmission path The impact score of the first federal data object.

[0026] Preferred, regarding For example, such as →u1→u2→ Specifically, the current process node corresponding to the engineering drawings. Transmission path Impact score of the first federal data object include: , in, The weights of directly connected flag values, process node and transmission path The first directly linked flag value of the federated data object, if the process node If it is directly linked to the first federated data object (e.g., whether an ERP purchase order depends on this engineering drawing), then =1, otherwise =0, Weights for semantic similarity process node Metadata and propagation path The semantic similarity of the metadata of the first federal data object, The weights for historical covariance frequencies. process node and transmission path The historical covariance frequency of the first federal data object (the frequency with which the two were changed together or caused problems in the past N changes). As a weight for time sensitivity, process node and transmission path The time sensitivity of the first federal data object This is the sigmoid function.

[0027] Preferred process nodes Metadata and propagation path Semantic similarity of metadata of the first federal data object include: , in, process node Metadata (referring to the metadata of engineering drawings, such as part codes, process specifications, etc.). For the propagation path The metadata of the first federal data object (such as the metadata of an MES work order corresponding to an engineering drawing).

[0028] Preferred process nodes and transmission path Time sensitivity of the first federal data object include: , in, For example, the attenuation coefficient (e.g.) =0.1), The most recent process node and transmission path The time difference between the first interaction / synchronization of the federated data object.

[0029] Preferably, , All are normalized to [0,1], and , , , The sum equals 1.

[0030] Specifically, a certain edge on the propagation path intensity include: , in, Historically, due to a certain border One end of the federal data object Changes that cause a certain edge The other end of the federal data object The number of times the changes are synchronized. for Upstream, For a certain border in history One end of the federal data object Total number of changes.

[0031] Step 103: When the control operation is to lock the federal data object or issue an alarm and transfer to manual approval, the locked federal data object is modified or approved simultaneously, and then the lock is released.

[0032] Specifically, based on the final propagation impact score, the control operations on the corresponding federated data objects include: locking the federated data object when the final propagation impact score is greater than or equal to a preset first threshold; issuing an alarm and transferring the case to manual approval when the final propagation impact score is less than the preset first threshold but greater than or equal to a preset second threshold; and sending a notification message when the final propagation impact score is less than the preset second threshold.

[0033] Example 2 like Figure 2 As shown, this embodiment proposes a cross-system data object association and consistency maintenance system, including: The impact score calculation module is used to identify downstream federated data objects associated with the engineering drawings when a change is detected, and to set up a cross-system dependency mapping model to calculate the final propagation impact score of each federated data object after the process node corresponding to the engineering drawings has undergone multi-hop propagation. Preferably, for example, the federated data object can be an ERP purchase order, MES work order, etc. If the engineering drawings are changed, the ERP purchase order, MES work order, etc. may also need to be changed.

[0034] Specifically, identifying the downstream federated data objects associated with the engineering drawings includes generating a dependency graph using the engineering drawings and federated data objects as process nodes and references / dependencies as directed edges.

[0035] Specifically, before identifying the downstream federated data objects associated with the engineering drawings, the process also includes locking the engineering drawings when a change is detected in the approval system to prevent modifications to the engineering drawings before approval is completed.

[0036] The control module is used to perform control operations on the corresponding federated data objects based on the final propagation impact score. The control operations include: locking the federated data object, issuing an alarm and transferring it to manual approval or sending a notification message. Specifically, the cross-system dependency mapping model includes: , in, Process nodes corresponding to engineering drawings After multi-hop propagation, the federal data object The final propagation affects the score. This represents the total number of hops in the propagation path (generally limited to 3-5). For the propagation path The attenuation factor of the jump (with a value ranging from 0.5 to 0.8) indicates that the further the jump, the weaker the effect. To start from process nodes To Federal Data Objects The transmission path, For a certain edge on the propagation path The strength, Process nodes corresponding to engineering drawings Transmission path The impact score of the first federal data object.

[0037] Preferred, regarding For example, such as →u1→u2→ Specifically, the current process node corresponding to the engineering drawings. Transmission path Impact score of the first federal data object include: , in, The weights of directly connected flag values, process node and transmission path The first directly linked flag value of the federated data object, if the process node If it is directly linked to the first federated data object (e.g., whether an ERP purchase order depends on this engineering drawing), then =1, otherwise =0, Weights for semantic similarity process node Metadata and propagation path The semantic similarity of the metadata of the first federal data object, The weights for historical covariance frequencies. process node and transmission path The historical covariance frequency of the first federal data object (the frequency with which the two were changed together or caused problems in the past N changes). As a weight for time sensitivity, process node and transmission path The time sensitivity of the first federal data object This is the sigmoid function.

[0038] Preferred process nodes Metadata and propagation path Semantic similarity of metadata of the first federal data object include: , in, process node Metadata (referring to the metadata of engineering drawings, such as part codes, process specifications, etc.). For the propagation path The metadata of the first federal data object (such as the metadata of an MES work order corresponding to an engineering drawing).

[0039] Preferred process nodes and transmission path Time sensitivity of the first federal data object include: , in, For example, the attenuation coefficient (e.g.) =0.1), The most recent process node and transmission path The time difference between the first interaction / synchronization of the federated data object.

[0040] Preferably, , All are normalized to [0,1], and , , , The sum equals 1.

[0041] Specifically, a certain edge on the propagation path intensity include: , in, Historically, due to a certain border One end of the federal data object Changes that cause a certain edge The other end of the federal data object The number of times the changes are synchronized. for Upstream, For a certain border in history One end of the federal data object Total number of changes.

[0042] The consistency maintenance module is used to simultaneously modify the locked federated data object or release the lock after approval when the control operation is to lock the federated data object or trigger an alarm and transfer it to manual approval.

[0043] Specifically, based on the final propagation impact score, the control operations on the corresponding federated data objects include: locking the federated data object when the final propagation impact score is greater than or equal to a preset first threshold; issuing an alarm and transferring the case to manual approval when the final propagation impact score is less than the preset first threshold but greater than or equal to a preset second threshold; and sending a notification message when the final propagation impact score is less than the preset second threshold.

[0044] Example 3 This invention also proposes a storage medium storing multiple instructions for implementing the cross-system data object association and consistency maintenance method.

[0045] Optionally, in this embodiment, the storage medium may be located in any computer terminal in a group of computer terminals in a computer network, or in any mobile terminal in a group of mobile terminals.

[0046] Optionally, in this embodiment, the storage medium is configured to store program code for performing the following method steps: Step 101, when a change in the engineering drawing is detected, identify the downstream federated data objects associated with the engineering drawing, set up a cross-system dependency mapping model, and calculate the final propagation impact score of the process node corresponding to the engineering drawing on each federated data object after multi-hop propagation; Specifically, identifying the downstream federated data objects associated with the engineering drawings includes generating a dependency graph using the engineering drawings and federated data objects as process nodes and references / dependencies as directed edges.

[0047] Specifically, before identifying the downstream federated data objects associated with the engineering drawings, the process also includes locking the engineering drawings when a change is detected in the approval system to prevent modifications to the engineering drawings before approval is completed.

[0048] Step 102: Based on the final propagation impact score, perform control operations on the corresponding federated data objects, wherein the control operations include: locking the federated data object, issuing an alarm and transferring it to manual approval or sending a notification message; Specifically, the cross-system dependency mapping model includes: , in, Process nodes corresponding to engineering drawings After multi-hop propagation, the federal data object The final propagation affects the score. The total number of hops in the propagation path. For the propagation path The attenuation factor of the jump, To start from process nodes To Federal Data Objects The transmission path, For a certain edge on the propagation path The strength, Process nodes corresponding to engineering drawings Transmission path The impact score of the first federal data object.

[0049] Specifically, the current process node corresponding to the engineering drawings. Transmission path Impact score of the first federal data object include: , in, The weights of directly connected flag values, process node and transmission path The first directly linked flag value of the federated data object, if the process node If directly linked to the first federated data object, then =1, otherwise =0, Weights for semantic similarity process node Metadata and propagation path The semantic similarity of the metadata of the first federal data object, The weights for historical covariance frequencies. process node and transmission path The historical covariance frequency of the first federal data object, As a weight for time sensitivity, process node and transmission path The time sensitivity of the first federal data object This is the sigmoid function.

[0050] Specifically, a certain edge on the propagation path intensity include: , in, Historically, due to a certain border One end of the federal data object Changes that cause a certain edge The other end of the federal data object The number of times the changes are synchronized. for Upstream, For a certain border in history One end of the federal data object Total number of changes.

[0051] Step 103: When the control operation is to lock the federal data object or issue an alarm and transfer to manual approval, the locked federal data object is modified or approved simultaneously, and then the lock is released.

[0052] Specifically, based on the final propagation impact score, the control operations on the corresponding federated data objects include: locking the federated data object when the final propagation impact score is greater than or equal to a preset first threshold; issuing an alarm and transferring the case to manual approval when the final propagation impact score is less than the preset first threshold but greater than or equal to a preset second threshold; and sending a notification message when the final propagation impact score is less than the preset second threshold.

[0053] Example 4 This invention also proposes an electronic device, including a processor and a storage medium connected to the processor. The storage medium stores multiple instructions, which can be loaded and executed by the processor to enable the processor to execute the cross-system data object association and consistency maintenance method.

[0054] Specifically, the electronic device in this embodiment can be a computer terminal, which may include one or more processors and a storage medium.

[0055] The storage medium can be used to store software programs and modules, such as the cross-system data object association and consistency maintenance method in this embodiment of the invention. The corresponding program instructions / modules allow the processor to execute various functional applications and data processing by running the software programs and modules stored in the storage medium, thus realizing the aforementioned cross-system data object association and consistency maintenance method. The storage medium may include high-speed random access storage media, and may also include non-volatile storage media, such as one or more magnetic storage systems, flash memory, or other non-volatile solid-state storage media. In some instances, the storage medium may further include storage media remotely configured relative to the processor, which can be connected to the terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0056] The processor can call the information and application stored in the storage medium through the transmission system to execute the following method steps: Step 101, when a change in the engineering drawing is detected, identify the downstream federated data objects associated with the engineering drawing, set up a cross-system dependency mapping model, and calculate the final propagation impact score of each federated data object after the process node corresponding to the engineering drawing has undergone multi-hop propagation. Specifically, identifying the downstream federated data objects associated with the engineering drawings includes generating a dependency graph using the engineering drawings and federated data objects as process nodes and references / dependencies as directed edges.

[0057] Specifically, before identifying the downstream federated data objects associated with the engineering drawings, the process also includes locking the engineering drawings when a change is detected in the approval system to prevent modifications to the engineering drawings before approval is completed.

[0058] Step 102: Based on the final propagation impact score, perform control operations on the corresponding federated data objects, wherein the control operations include: locking the federated data object, issuing an alarm and transferring it to manual approval or sending a notification message; Specifically, the cross-system dependency mapping model includes: , in, Process nodes corresponding to engineering drawings After multi-hop propagation, the federal data object The final propagation affects the score. The total number of hops in the propagation path. For the propagation path The attenuation factor of the jump, To start from process nodes To Federal Data Objects The transmission path, For a certain edge on the propagation path The strength, Process nodes corresponding to engineering drawings Transmission path The impact score of the first federal data object.

[0059] Specifically, the current process node corresponding to the engineering drawings. Transmission path Impact score of the first federal data object include: , in, The weights of directly connected flag values, process node and transmission path The first directly linked flag value of the federated data object, if the process node If directly linked to the first federated data object, then =1, otherwise =0, Weights for semantic similarity process node Metadata and propagation path The semantic similarity of the metadata of the first federal data object, The weights for historical covariance frequencies. process node and transmission path The historical covariance frequency of the first federal data object, As a weight for time sensitivity, process node and transmission path The time sensitivity of the first federal data object This is the sigmoid function.

[0060] Specifically, a certain edge on the propagation path intensity include: , in, Historically, due to a certain border One end of the federal data object Changes that cause a certain edge The other end of the federal data object The number of times the changes are synchronized. for Upstream, For a certain border in history One end of the federal data object Total number of changes.

[0061] Step 103: When the control operation is to lock the federal data object or issue an alarm and transfer to manual approval, the locked federal data object is modified or approved simultaneously, and then the lock is released.

[0062] Specifically, based on the final propagation impact score, the control operations on the corresponding federated data objects include: locking the federated data object when the final propagation impact score is greater than or equal to a preset first threshold; issuing an alarm and transferring the case to manual approval when the final propagation impact score is less than the preset first threshold but greater than or equal to a preset second threshold; and sending a notification message when the final propagation impact score is less than the preset second threshold.

[0063] In the above embodiments of the present invention, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0064] In the several embodiments provided by this invention, it should be understood that the disclosed technical content can be implemented in other ways. The system embodiments described above are merely illustrative; for example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, indirect coupling or communication connection between units or modules, and may be electrical or other forms.

[0065] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0066] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0067] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes: USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, optical disks, and other media capable of storing program code.

[0068] Obviously, the above embodiments are merely illustrative examples for clear explanation and are not intended to limit the implementation. Those skilled in the art will recognize that other variations or modifications can be made based on the above description. It is neither necessary nor possible to exhaustively list all possible implementations here. However, obvious variations or modifications derived therefrom are still within the scope of protection of this invention.

Claims

1. A method for cross-system data object association and consistency maintenance, characterized in that, include: When a change in the engineering drawing is detected, the downstream federated data objects associated with the engineering drawing are identified, and a cross-system dependency mapping model is set up to calculate the final propagation impact score of each federated data object after the process node corresponding to the engineering drawing has undergone multi-hop propagation. Based on the final propagation impact score, control operations are performed on the corresponding federated data objects, including: locking the federated data object, issuing an alarm and transferring it to manual approval or sending a notification message; When the control operation is to lock the federal data object or issue an alarm and transfer it to manual approval, the locked federal data object is modified or approved simultaneously, and then the lock is released.

2. The method for cross-system data object association and consistency maintenance as described in claim 1, characterized in that, Identifying downstream federated data objects associated with the engineering drawings includes generating a dependency graph using the engineering drawings and federated data objects as process nodes and references / dependencies as directed edges.

3. The method for cross-system data object association and consistency maintenance as described in claim 1, characterized in that, Before identifying the downstream federated data objects associated with the engineering drawings, the process also includes locking the engineering drawings when a change is detected in the approval system to prevent modifications to the engineering drawings before approval is completed.

4. The method for cross-system data object association and consistency maintenance as described in claim 2, characterized in that, The cross-system dependency mapping model includes: ， in, Process nodes corresponding to engineering drawings After multi-hop propagation, the federal data object The final propagation affects the score. The total number of hops in the propagation path. For the propagation path The attenuation factor of the jump, To start from process nodes To Federal Data Objects The transmission path, For a certain edge on the propagation path The strength, Process nodes corresponding to engineering drawings Transmission path The impact score of the first federal data object.

5. The method for cross-system data object association and consistency maintenance as described in claim 4, characterized in that, The current process node corresponding to the engineering drawings Transmission path Impact score of the first federal data object include: ， in, The weights of directly connected flag values, process node and transmission path The first directly linked flag value of the federated data object, if the process node If directly linked to the first federated data object, then =1, otherwise =0, Weights for semantic similarity process node Metadata and propagation path The semantic similarity of the metadata of the first federal data object, The weights for historical covariance frequencies. process node and transmission path The historical covariance frequency of the first federal data object, As a weight for time sensitivity, process node and transmission path The time sensitivity of the first federal data object This is the sigmoid function.

6. The method for cross-system data object association and consistency maintenance as described in claim 4, characterized in that, One side of the propagation path intensity include: ， in, Historically, due to a certain border One end of the federal data object Changes that cause a certain edge The other end of the federal data object The number of times the changes are synchronized. for Upstream, For a certain border in history One end of the federal data object Total number of changes.

7. The method for cross-system data object association and consistency maintenance as described in claim 1, characterized in that, Based on the final propagation impact score, the control operations on the corresponding federated data objects include: locking the federated data object when the final propagation impact score is greater than or equal to a preset first threshold; issuing an alarm and transferring the case to manual approval when the final propagation impact score is less than the preset first threshold but greater than or equal to a preset second threshold; and sending a notification message when the final propagation impact score is less than the preset second threshold.

8. A cross-system data object association and consistency maintenance system, characterized in that, include: The impact score calculation module is used to identify downstream federated data objects associated with the engineering drawings when a change is detected, and to set up a cross-system dependency mapping model to calculate the final propagation impact score of each federated data object after the process node corresponding to the engineering drawings has undergone multi-hop propagation. The control module is used to perform control operations on the corresponding federated data objects based on the final propagation impact score. The control operations include: locking the federated data object, issuing an alarm and transferring it to manual approval or sending a notification message. The consistency maintenance module is used to simultaneously modify the locked federated data object or release the lock after approval when the control operation is to lock the federated data object or trigger an alarm and transfer it to manual approval.

9. A cross-system data object association and consistency maintenance system as described in claim 8, characterized in that, Identifying downstream federated data objects associated with the engineering drawings includes generating a dependency graph using the engineering drawings and federated data objects as process nodes and references / dependencies as directed edges.

10. A cross-system data object association and consistency maintenance system as described in claim 8, characterized in that, Before identifying the downstream federated data objects associated with the engineering drawings, the process also includes locking the engineering drawings when a change is detected in the approval system to prevent modifications to the engineering drawings before approval is completed.

Images