A method and system for cross-professional collaborative management of factory object location number design data

By building a factory object tag data warehouse and using metadata configuration files and data publishing adapters, the problem of data sharing between engineering disciplines was solved, cross-disciplinary data merging and consistency management were achieved, and the standardization and delivery quality of design data were improved.

CN116383404BActive Publication Date: 2026-06-16BAOSTEEL ENG & TECH GRP

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
BAOSTEEL ENG & TECH GRP
Filing Date
2023-03-18
Publication Date
2026-06-16

AI Technical Summary

Technical Problem

The uneven development of integration and collaboration among various engineering disciplines, coupled with a lack of data sharing methods and management approaches, results in low-quality design data, particularly hindering data sharing and synchronized changes during design modifications.

Method used

Build a factory object tag data warehouse, set up professional data domains, use metadata configuration files and data publishing adapters for data sharing, build a data sharing structure, and perform data merging, consistency analysis and change tracking through entity recognition models and professional design knowledge graphs.

🎯Benefits of technology

It enables cross-disciplinary data merging and consistency management, improves the standardization level and delivery quality of design data, supports multi-disciplinary collaborative changes, and breaks down information barriers between disciplines.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116383404B_ABST
    Figure CN116383404B_ABST
Patent Text Reader

Abstract

The application belongs to the technical field of data management, and discloses a kind of factory object position number design data cross-professional collaborative management method and system.The method comprises the following steps: constructing factory object position number data warehouse, and setting corresponding several professional data domains;Constructing metadata configuration file and data publishing adapter;Build data sharing structure;Release metadata configuration file and data publishing adapter;Each engineering design professional publishes factory object position number design data to the corresponding professional data domain;The factory object position number design data in each professional data domain is collaboratively managed.The system comprises a factory object position number design data collaborative management unit and a factory object design data publishing unit.The application solves the problems of data collaboration difficulty among various engineering design professionals, lack of data sharing means and management methods, and low delivery data quality in the prior art.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention belongs to the field of data management technology, specifically relating to a cross-disciplinary collaborative management method and system for factory object tag design data. Background Technology

[0002] With the development of digital design technology, the application of information technologies such as 3D design and collaborative design has promoted the rapid improvement of the technical level of the engineering industry. However, the integration and collaborative work among various engineering disciplines is unevenly developed. Design work carried out in different professional fields, especially digital design work, relies on specific professional design tools, which restricts the further improvement of engineering design efficiency and quality. The application software of each engineering discipline is relatively independent and loosely connected. Each application software relies on independent databases, which lack sharing and have a large amount of data redundancy, resulting in limited data consistency and reliability. Due to the lack of data sharing means and management methods, the disciplines are independent and lack communication capabilities. It is difficult to ensure the consistency of design data quality, especially when design changes occur. Related disciplines cannot achieve data sharing and synchronous changes, which often leads to low design delivery quality. Summary of the Invention

[0003] To address the problems of uneven development in integration and collaboration among various engineering disciplines, lack of data sharing methods and management approaches, and low design delivery quality in existing technologies, this invention aims to provide a cross-disciplinary collaborative management method and system for factory object tag design data.

[0004] The technical solution adopted in this invention is as follows:

[0005] A cross-disciplinary collaborative management method for factory object tag design data includes the following steps:

[0006] Construct a factory object tag data warehouse, and set up corresponding professional data fields in the factory object tag data warehouse according to several engineering design specialties;

[0007] Based on the characteristics of the professional software data of each engineering design discipline, corresponding metadata configuration files and data publishing adapters are constructed respectively.

[0008] In the factory object tag data warehouse, a data sharing structure is constructed based on several professional data domains, several metadata configuration files and data publishing adapters, and several engineering design specialties;

[0009] Based on the data sharing structure, the metadata configuration file and data publishing adapter are published to the corresponding engineering design disciplines;

[0010] In each engineering design discipline, based on the metadata configuration file and data publishing adapter, the corresponding factory object tag design data is generated and published to the corresponding professional data domain;

[0011] In the factory object tag data warehouse, collaborative management is carried out on the factory object tag design data of various engineering design specialties in various professional data domains.

[0012] Furthermore, the engineering design profession includes specialties such as process, equipment, instrumentation, electrical, piping, and architecture;

[0013] The professional data domains corresponding to the engineering design major include data domains such as process, equipment, instrumentation, electrical, piping, and architecture;

[0014] The metadata configuration files corresponding to the engineering design major include metadata configuration files for process, equipment, instrumentation, electrical, piping, and architecture;

[0015] Data publishing adapters for engineering design include those for process, equipment, instrumentation, electrical, piping, and architecture.

[0016] Furthermore, in the factory object tag data warehouse, a data sharing structure is constructed based on several professional data domains, several metadata configuration files and data publishing adapters, and several engineering design specialties, including the following steps:

[0017] In the factory object tag data warehouse, based on several professional data fields, the same number of shared nodes are constructed, and the link relationship between each shared node and the corresponding professional data field is constructed.

[0018] Establish the link relationship between each engineering design specialty and its corresponding shared nodes;

[0019] Establish the link relationship between each shared node and its corresponding metadata configuration file and data publishing adapter;

[0020] A data sharing structure is constructed based on several professional data domains, several metadata configuration files and data publishing adapters, several engineering design specialties, the link relationships between each shared node and its corresponding professional data domain, the link relationships between each engineering design specialty and its corresponding shared node, and the link relationships between each shared node and its corresponding metadata configuration file and data publishing adapter.

[0021] Furthermore, in each engineering design discipline, based on the metadata configuration file and data publishing adapter, corresponding factory object tag design data is generated, and the factory object tag design data is published to the corresponding professional data domain, including the following steps:

[0022] In various engineering design disciplines, the received data publishing adapter is used to parse the received metadata configuration file and extract the corresponding factory object tag design metadata.

[0023] Generate the corresponding factory object design data based on the factory object design metadata;

[0024] The factory object tag design data is published to the corresponding professional data domain through the data publishing adapter corresponding to the current engineering design profession.

[0025] Furthermore, collaborative management includes data merging, consistency analysis, and change tracking of factory object reference design data;

[0026] In the factory object tag data warehouse, collaborative management of factory object tag design data for each engineering design specialty within each professional data domain includes the following steps:

[0027] Build an entity recognition model in the factory object tag data warehouse;

[0028] Using an entity recognition model, extract historical design data entities from several historical design data of various engineering design disciplines;

[0029] Based on several historical design data entities, several professional design knowledge corresponding to each engineering design discipline is obtained;

[0030] By integrating several professional design knowledge from various engineering design disciplines, a professional design knowledge graph is constructed.

[0031] Using entity recognition models, design data entities are extracted from the factory object tag design data of each engineering design specialty in each professional data domain.

[0032] Based on the professional design knowledge graph, the design data entities with common characteristics of the design data of the object tag design data of each factory are merged to obtain the merged factory object tag design data.

[0033] A consistency analysis is performed on the design data entities based on the horizontal relationships between the design data of each factory object tag number, and a consistency report is obtained.

[0034] Change tracking is performed on the design data entities of the object tag design data of each factory, recording the changed design data entities and their respective factory object tag design data, and a change tracking report is obtained.

[0035] A cross-disciplinary collaborative management system for factory object tag design data, based on a cross-disciplinary collaborative management method for factory object tag design data, includes a factory object tag design data collaborative management unit and a factory object design data publishing unit. The factory object tag design data collaborative management unit is connected to the factory object design data publishing unit. The factory object design data publishing unit is set up in each engineering design discipline, and the factory object design data publishing unit is connected to the design data server of each engineering design discipline.

[0036] The Factory Object Design Data Collaborative Management Unit is used to construct a Factory Object Design Data Warehouse. Based on several engineering design specialties, it sets up several corresponding professional data fields in the Factory Object Design Data Warehouse. Based on the professional software data characteristics of each engineering design specialty, it constructs corresponding metadata configuration files and data publishing adapters. In the Factory Object Design Data Warehouse, based on several professional data fields, several metadata configuration files and data publishing adapters, and several engineering design specialties, it constructs a data sharing structure. Based on the data sharing structure, it publishes the metadata configuration files and data publishing adapters to the Factory Object Design Data Publishing Unit. In the Factory Object Design Data Warehouse, it performs collaborative management of the Factory Object Design Data of each engineering design specialty in each professional data field.

[0037] The Factory Object Design Data Publishing Unit is used to generate corresponding factory object tag design data for each engineering design discipline based on metadata configuration files and data publishing adapters, and to publish the factory object tag design data to the professional data domain corresponding to the Factory Object Tag Design Data Collaborative Management Unit.

[0038] Furthermore, the factory object reference design data collaborative management unit includes a factory object reference data warehouse module, a configuration file and adapter construction module, a data sharing structure construction module, a configuration file and adapter publishing module, and a factory object reference design data collaborative management module. The factory object reference data warehouse module is connected to the configuration file and adapter construction module, the data sharing structure construction module, the configuration file and adapter publishing module, the factory object reference design data collaborative management module, and the factory object design data publishing unit, respectively.

[0039] The Factory Object Tag Data Warehouse module is used to build and store the Factory Object Tag Data Warehouse, and to set up several professional data fields in the Factory Object Tag Data Warehouse according to several engineering design specialties.

[0040] The configuration file and adapter building module constructs corresponding metadata configuration files and data publishing adapters based on the characteristics of professional software data for each engineering design discipline, and sends the metadata configuration files and data publishing adapters to the factory object tag data warehouse module.

[0041] The data sharing structure building module is used to build a data sharing structure in the factory object tag data warehouse based on several professional data domains, several metadata configuration files and data publishing adapters, and several engineering design disciplines.

[0042] The configuration file and adapter publishing module is used to publish metadata configuration files and data publishing adapters to data publishing units designed through factory objects, based on the data sharing structure.

[0043] The Factory Object Design Data Collaborative Management Module is used to collaboratively manage the factory object design data of various engineering design disciplines in various professional data domains within the factory object design data warehouse. It also includes an entity recognition model and a professional design knowledge graph.

[0044] Furthermore, the data sharing structure construction module includes a shared node construction submodule, a link relationship construction submodule, and a data sharing structure construction submodule. The shared node construction submodule, the link relationship construction submodule, and the data sharing structure construction submodule are connected in sequence, and both the shared node construction submodule and the data sharing structure construction submodule are connected to the factory object tag data warehouse module.

[0045] The shared node construction submodule is used to construct the same number of shared nodes in the factory object tag data warehouse according to several professional data fields;

[0046] The link relationship building submodule is used to build the link relationship between each shared node and the corresponding professional data domain, the link relationship between each engineering design profession and the corresponding shared node, and the link relationship between each shared node and the corresponding metadata configuration file and data publishing adapter.

[0047] The data sharing structure construction submodule is used to construct the data sharing structure based on several professional data domains, several metadata configuration files and data publishing adapters, several engineering design specialties, the link relationships between each shared node and its corresponding professional data domain, the link relationships between each engineering design specialty and its corresponding shared node, and the link relationships between each shared node and its corresponding metadata configuration file and data publishing adapter.

[0048] Furthermore, the factory object tag design data collaborative management module includes an entity recognition model submodule, a professional design knowledge graph submodule, a collaborative management submodule, a data merging submodule, a consistency analysis submodule, and a change tracking submodule. The entity recognition model submodule, the professional design knowledge graph submodule, the data merging submodule, the consistency analysis submodule, and the change tracking submodule are all connected to the collaborative management submodule. The entity recognition model submodule is connected to the professional design knowledge graph submodule, and the collaborative management submodule is connected to the factory object tag data warehouse module.

[0049] The text entity recognition sub-model module is used to build an entity recognition model. Using the entity recognition model, it extracts historical design data entities from several historical design data of various engineering design disciplines and sends the obtained historical design data entities to the professional design knowledge graph sub-module. Using the entity recognition model, it extracts design data entities from the factory object tag design data of various engineering design disciplines in the professional data domains of the factory object tag design data warehouse module and sends the design data entities of several factory object tag design data to the collaborative management sub-module.

[0050] The Professional Design Knowledge Graph submodule is used to obtain several professional design knowledge corresponding to each engineering design profession based on several historical design data entities, integrate the several professional design knowledge of each engineering design profession, construct a professional design knowledge graph, and send the professional design knowledge graph to the Collaborative Management submodule.

[0051] The Collaborative Management submodule is used to receive design data entities of several factory object tag design data sent by the Text Entity Recognition Submodel Module and professional design knowledge graph sent by the Professional Design Knowledge Graph Submodule. According to the collaborative management requirements, it calls the corresponding Data Merging Submodule, Consistency Analysis Submodule and Change Tracking Submodule, and receives the merged factory object tag design data sent by the Data Merging Submodule, the consistency report sent by the Consistency Analysis Submodule and the change tracking report sent by the Change Tracking Submodule.

[0052] The data merging submodule is used to extract the design data entities and professional design knowledge graphs of several factory object tag design data stored in the collaborative management submodule. It merges the design data entities with common characteristics of each factory object tag design data in the factory object tag data warehouse module to obtain the merged factory object tag design data, and sends the merged factory object tag design data to the collaborative management submodule.

[0053] The consistency analysis submodule is used to extract the design data entities of several factory object tag design data stored in the collaborative management submodule, perform consistency analysis on the design data entities with horizontal relationships between the design data of each factory object tag design data, obtain a consistency report, and send the consistency report to the collaborative management submodule;

[0054] The change tracking submodule is used to extract the design data entities of several factory object tag design data stored in the collaborative management submodule, track changes to the design data entities of each factory object tag design data, record the changed design data entities and their respective factory object tag design data, obtain a change tracking report, and send the change tracking report to the collaborative management submodule.

[0055] Furthermore, the factory object design data publishing unit includes several factory object design data publishing sub-units with the same structure. Each factory object design data publishing sub-unit is connected to the factory object tag design data collaborative management unit and the design data server of the corresponding engineering design discipline.

[0056] The Factory Object Design Data Publishing Subunit is used to generate the corresponding factory object reference design data according to the metadata configuration file and data publishing adapter in the corresponding engineering design discipline, and publish the factory object reference design data to the corresponding professional data domain in the Factory Object Reference Design Data Collaborative Management Unit.

[0057] The factory object design data publishing subunit includes a metadata parsing module, a factory object tag design data generation module, and a factory object tag design data publishing module. These modules are connected sequentially, and both the metadata parsing module and the factory object tag design data publishing module are connected to the factory object tag design data collaborative management unit. The factory object tag design data generation module is connected to the design data server of the corresponding engineering design discipline.

[0058] The metadata parsing module is used in the corresponding engineering design discipline to parse the received metadata configuration file using the received data publishing adapter, extract the corresponding factory object reference design metadata, and send the factory object reference design metadata to the factory object reference design data generation module.

[0059] The factory object reference design data generation module is used to match and collect the corresponding design data in the design data server of the corresponding engineering design profession based on the factory object reference design metadata, generate the corresponding factory object reference design data, and send the factory object reference design data to the factory object reference design data publishing module.

[0060] The Factory Object Design Data Publishing Module is used to publish the factory object design data to the corresponding professional data field in the Factory Object Design Data Collaborative Management Unit through the data publishing adapter corresponding to the current engineering design profession.

[0061] The beneficial effects of this invention are as follows:

[0062] This invention provides a cross-disciplinary collaborative management method and system for factory object tag design data. Through metadata configuration files and data publishing adapters, it achieves unified metadata definition, eliminating the imbalance between integration and collaborative work development. Professional data domains effectively isolate factory object tag design data from different disciplines, ensuring data independence and facilitating change management and tracking. A shared factory object data warehouse enables targeted merging of similar items across disciplines, allowing for horizontal data comparison between different disciplines and breaking down information barriers. Data-level professional change management based on factory object tag numbers allows for the assessment of the impact of inter-discipline design changes, facilitating multi-discipline collaborative changes. Project-level factory object tag design data consistency analysis helps different design disciplines find common ground while respecting differences, strengthening the construction of common data standards, and improving design standardization and delivery quality.

[0063] Other beneficial effects of the present invention will be further explained in the specific embodiments. Attached Figure Description

[0064] Figure 1 This is a flowchart of the cross-disciplinary collaborative management method for factory object tag design data in this invention.

[0065] Figure 2 This is a structural block diagram of the cross-disciplinary collaborative management system for factory object tag design data in this invention. Implementation

[0066] The present invention will be further explained below with reference to the accompanying drawings and specific embodiments. Example

[0067] like Figure 1 As shown, this embodiment provides a cross-disciplinary collaborative management method for factory object tag design data, including the following steps:

[0068] Construct a factory object tag data warehouse, and set up several corresponding professional data fields in the factory object tag data warehouse according to several engineering design specialties; engineering design specialties include process, equipment, instrumentation, electrical, piping and construction specialties; the professional data fields corresponding to the engineering design specialties include process, equipment, instrumentation, electrical, piping and construction data fields;

[0069] Based on the characteristics of the professional software data for each engineering design specialty, corresponding metadata configuration files and data publishing adapters are constructed. The metadata configuration files for engineering design include metadata configuration files for process, equipment, instrumentation, electrical, piping, and architecture. The data publishing adapters for engineering design include data publishing adapters for process, equipment, instrumentation, electrical, piping, and architecture.

[0070] In the factory object tag data warehouse, a data sharing structure is constructed based on several professional data domains, several metadata configuration files and data publishing adapters, and several engineering design disciplines, including the following steps:

[0071] In the factory object tag data warehouse, based on several professional data fields, the same number of shared nodes are constructed, and the link relationship between each shared node and the corresponding professional data field is constructed.

[0072] Establish the link relationship between each engineering design specialty and its corresponding shared nodes;

[0073] Establish the link relationship between each shared node and its corresponding metadata configuration file and data publishing adapter;

[0074] A data sharing structure is constructed based on several professional data domains, several metadata configuration files and data publishing adapters, several engineering design specialties, the link relationships between each shared node and its corresponding professional data domain, the link relationships between each engineering design specialty and its corresponding shared node, and the link relationships between each shared node and its corresponding metadata configuration file and data publishing adapter.

[0075] Based on the data sharing structure, the metadata configuration file and data publishing adapter are published to the corresponding engineering design disciplines;

[0076] In each engineering design discipline, based on the metadata configuration file and data publishing adapter, the corresponding factory object tag design data is generated, and the factory object tag design data is published to the corresponding professional data domain, including the following steps:

[0077] In various engineering design disciplines, the received data publishing adapter is used to parse the received metadata configuration file and extract the corresponding factory object tag design metadata.

[0078] The plant object tag design metadata includes the plant object tag basic attributes, the plant object tag design basic attribute group, the plant object tag design process attribute group, the plant object tag design selection attribute group, the plant object tag design associated plant object tag classification group, and the plant object tag design feature attribute group. The plant object tag basic attributes include the plant object tag name, UID, and naming rules. The plant object tag design basic attribute group includes several basic attribute information describing the plant object tag's specialty, status, and design requirements. The plant object tag design process attribute group includes several process attribute information describing the plant object tag's process logic.

[0079] Generate the corresponding factory object design data based on the factory object design metadata;

[0080] Publish the factory object tag design data to the corresponding professional data domain through the data publishing adapter corresponding to the current engineering design profession;

[0081] In the factory object tag data warehouse, collaborative management is implemented for factory object tag design data from various engineering design disciplines across different professional data domains. Collaborative management includes data merging, consistency analysis, and change tracking of factory object tag design data, encompassing the following steps:

[0082] Build an entity recognition model in the factory object tag data warehouse;

[0083] An entity recognition model is built based on recurrent neural networks and graph neural networks. The model includes an input layer, a semantic feature extraction module, a graph feature extraction module, a feature interaction and collaboration module, a Conditional Random Field (CRF) module, and an output layer. The input layer is connected to both the semantic and graph feature extraction modules, which are in turn connected to the feature interaction and collaboration module. The semantic feature extraction module is based on a pre-trained language sub-model using Bidirectional Encoder Representation from Transformers (BERT) and a Bidirectional Long-term and Short-term Memory (BILSTM) network. The graph feature extraction module is connected to the semantic feature extraction module and is based on a pre-trained language sub-model using BERT and a graph attention network. The AttentionNetwork (GAT) is established, and the feature interaction collaboration module is connected to the CRF module. The feature interaction collaboration module is based on the interaction attention mechanism, and the CRF module is connected to the output layer. The semantic feature extraction module includes a word vector representation layer and a BILSTM layer with a BERT pre-trained language sub-model. The graph feature extraction module includes a word vector representation layer, a word-word relationship text construction layer, and a GAT layer with a BERT pre-trained language sub-model. The feature interaction collaboration module includes a Positionalembedding sub-module, a Multi-head Attention Mechanism sub-module, two Add & Norm sub-modules, and two FeedForward sub-modules. The input layer receives historical design data or factory object location design data from various engineering design disciplines. The semantic feature extraction module extracts the semantic features of the factory object location design data, and the graph feature extraction module extracts the graph features from the factory object location design data. The feature interaction collaboration module performs feature interaction collaboration between the semantic features and the graph features to obtain the interaction collaboration feature sequence. The CRF module performs dependency processing based on the interaction collaboration feature sequence to obtain the design data entity.

[0084] Using an entity recognition model, extract historical design data entities from several historical design data of various engineering design disciplines;

[0085] Based on several historical design data entities, several professional design knowledge corresponding to each engineering design discipline is obtained;

[0086] By integrating several professional design knowledge from various engineering design disciplines, a professional design knowledge graph is constructed.

[0087] Using entity recognition models, design data entities are extracted from the factory object tag design data of each engineering design specialty in each professional data domain.

[0088] Based on the professional design knowledge graph, the design data entities with common characteristics of the design data of the object tag design data of each factory are merged to obtain the merged factory object tag design data.

[0089] For example, when designing a control valve, the process design focuses on process parameters, including the medium name, operating temperature, and operating pressure. However, in the instrumentation design, the focus shifts to attributes such as valve body type, valve body material, and actuator action. Data merging supports selecting multiple professional design data for a plant object tag number, merging all common data into a single plant object tag number independent of the design. This data is then used to provide the merged plant object tag number design data service to external systems via Web services, RESTful APIs, or microservices.

[0090] A consistency analysis is performed on the design data entities based on the horizontal relationships between the design data of each factory object tag number, and a consistency report is obtained.

[0091] During the execution of engineering projects, information asynchrony can easily occur in multidisciplinary designs. Consistency analysis supports cross-disciplinary horizontal data comparison of plant object tag design data, identifies inconsistent design data entities between disciplines, generates consistency reports, and guides synchronous design across disciplines. For example, the process design of a control valve specifies an inlet pressure of 0.3 MPa, but the instrumentation design selects an inlet pressure of 0.5 MPa. Through consistency analysis, the process and instrumentation disciplines can quickly understand the data differences, thereby taking timely adjustment measures and improving collaboration capabilities.

[0092] Change tracking is performed on the design data entities of the object tag design data of each factory, recording the changed design data entities and their respective factory object tag design data, and a change tracking report is obtained;

[0093] Changes in engineering design are inevitable. Change tracking and notification functions can help professionals stay informed about changes in the design data of published factory object reference numbers, facilitating rapid response and adjustments by collaborating professionals and improving the quality of design deliverables. Example

[0094] like Figure 2As shown, this embodiment provides a cross-disciplinary collaborative management system for factory object tag design data. Based on the cross-disciplinary collaborative management method for factory object tag design data, it includes a factory object tag design data collaborative management unit and a factory object design data publishing unit. The factory object tag design data collaborative management unit is connected to the factory object design data publishing unit. The factory object design data publishing unit is set in each engineering design discipline, and the factory object design data publishing unit is connected to the design data server of each engineering design discipline.

[0095] The Factory Object Design Data Collaboration Management Unit is used to build a factory object design data warehouse. Based on several engineering design disciplines, it sets up corresponding professional data fields within the factory object design data warehouse. According to the characteristics of the professional software data of each engineering design discipline, it constructs corresponding metadata configuration files and data publishing adapters. In the factory object design data warehouse, based on the several professional data fields, metadata configuration files and data publishing adapters, and several engineering design disciplines, it constructs a data sharing structure and publishes the metadata configuration files and data publishing adapters to the factory object design data publishing unit according to the data sharing structure. It also performs collaborative management of the factory object design data of each engineering design discipline in each professional data field within the factory object design data warehouse. The factory object design data collaboration management module provides project-level cross-disciplinary data collaboration functions, maintaining the independence of each professional data and avoiding the overwriting of duplicate data between disciplines.

[0096] The Plant Object Design Data Publishing Unit is used to generate corresponding plant object tag design data for each engineering design discipline based on metadata configuration files and data publishing adapters, and to publish the plant object tag design data to the corresponding professional data domain of the Plant Object Tag Design Data Collaborative Management Unit. For example, if the pipeline design uses OpenPlant 3D design software, when it is necessary to publish pipeline design data related to a project, the professional selects the pipeline plant object tag to be published in the OpenPlant software. The data publishing adapter parses the pipeline discipline's metadata configuration file, extracts the pipeline plant object tag design data from the OpenPlant software according to the data format defined in the configuration file, and publishes it to the plant object data warehouse in XML file format. The plant object data warehouse executes a data processing program in the background, parses the published XML data file, and obtains the structured pipeline plant object tag design data in the corresponding professional data domain.

[0097] Preferably, the factory object reference design data collaborative management unit includes a factory object reference data warehouse module, a configuration file and adapter construction module, a data sharing structure construction module, a configuration file and adapter publishing module, and a factory object reference design data collaborative management module. The factory object reference data warehouse module is connected to the configuration file and adapter construction module, the data sharing structure construction module, the configuration file and adapter publishing module, the factory object reference design data collaborative management module, and the factory object design data publishing unit, respectively.

[0098] The Factory Object Tag Data Warehouse module is used to build and store the Factory Object Tag Data Warehouse, and to set up several professional data fields in the Factory Object Tag Data Warehouse according to several engineering design specialties.

[0099] The configuration file and adapter building module constructs corresponding metadata configuration files and data publishing adapters based on the characteristics of professional software data for each engineering design discipline, and sends the metadata configuration files and data publishing adapters to the factory object tag data warehouse module.

[0100] The data sharing structure building module is used to build a data sharing structure in the factory object tag data warehouse based on several professional data domains, several metadata configuration files and data publishing adapters, and several engineering design disciplines.

[0101] The configuration file and adapter publishing module is used to publish metadata configuration files and data publishing adapters to data publishing units designed through factory objects, based on the data sharing structure.

[0102] The Factory Object Design Data Collaborative Management Module manages the factory object design data of various engineering design disciplines in the Factory Object Design Data Warehouse, and includes entity recognition models and professional design knowledge graphs.

[0103] Preferably, the data sharing structure construction module includes a shared node construction submodule, a link relationship construction submodule, and a data sharing structure construction submodule, which are connected sequentially. Both the shared node construction submodule and the data sharing structure construction submodule are connected to the factory object tag data warehouse module.

[0104] The shared node construction submodule is used to construct the same number of shared nodes in the factory object tag data warehouse according to several professional data fields;

[0105] The link relationship building submodule is used to build the link relationship between each shared node and the corresponding professional data domain, the link relationship between each engineering design profession and the corresponding shared node, and the link relationship between each shared node and the corresponding metadata configuration file and data publishing adapter.

[0106] The data sharing structure construction submodule is used to construct the data sharing structure based on several professional data domains, several metadata configuration files and data publishing adapters, several engineering design specialties, the link relationships between each shared node and its corresponding professional data domain, the link relationships between each engineering design specialty and its corresponding shared node, and the link relationships between each shared node and its corresponding metadata configuration file and data publishing adapter.

[0107] As a preferred embodiment, the factory object tag design data collaborative management module includes an entity recognition model submodule, a professional design knowledge graph submodule, a collaborative management submodule, a data merging submodule, a consistency analysis submodule, and a change tracking submodule. The entity recognition model submodule, the professional design knowledge graph submodule, the data merging submodule, the consistency analysis submodule, and the change tracking submodule are all connected to the collaborative management submodule. Furthermore, the entity recognition model submodule is connected to the professional design knowledge graph submodule, and the collaborative management submodule is connected to the factory object tag data warehouse module.

[0108] The text entity recognition sub-model module is used to build an entity recognition model. Using the entity recognition model, it extracts historical design data entities from several historical design data of various engineering design disciplines and sends the obtained historical design data entities to the professional design knowledge graph sub-module. Using the entity recognition model, it extracts design data entities from the factory object tag design data of various engineering design disciplines in the professional data domains of the factory object tag design data warehouse module and sends the design data entities of several factory object tag design data to the collaborative management sub-module.

[0109] The Professional Design Knowledge Graph submodule is used to obtain several professional design knowledge corresponding to each engineering design profession based on several historical design data entities, integrate the several professional design knowledge of each engineering design profession, construct a professional design knowledge graph, and send the professional design knowledge graph to the Collaborative Management submodule.

[0110] The Collaborative Management submodule is used to receive design data entities of several factory object tag design data sent by the Text Entity Recognition Submodel Module and professional design knowledge graph sent by the Professional Design Knowledge Graph Submodule. According to the collaborative management requirements, it calls the corresponding Data Merging Submodule, Consistency Analysis Submodule and Change Tracking Submodule, and receives the merged factory object tag design data sent by the Data Merging Submodule, the consistency report sent by the Consistency Analysis Submodule and the change tracking report sent by the Change Tracking Submodule.

[0111] The data merging submodule is used to extract the design data entities and professional design knowledge graphs of several factory object tag design data stored in the collaborative management submodule. It merges the design data entities with common characteristics of each factory object tag design data in the factory object tag data warehouse module to obtain the merged factory object tag design data, and sends the merged factory object tag design data to the collaborative management submodule.

[0112] The consistency analysis submodule is used to extract the design data entities of several factory object tag design data stored in the collaborative management submodule, perform consistency analysis on the design data entities with horizontal relationships between the design data of each factory object tag design data, obtain a consistency report, and send the consistency report to the collaborative management submodule;

[0113] The change tracking submodule is used to extract the design data entities of several factory object tag design data stored in the collaborative management submodule, track changes to the design data entities of each factory object tag design data, record the changed design data entities and their respective factory object tag design data, obtain a change tracking report, and send the change tracking report to the collaborative management submodule.

[0114] As a preferred embodiment, the factory object design data publishing unit includes several factory object design data publishing sub-units with the same structure. Each factory object design data publishing sub-unit is connected to the factory object tag design data collaborative management unit and the design data server of the corresponding engineering design profession.

[0115] The Factory Object Design Data Publishing Subunit is used to generate the corresponding factory object reference design data according to the metadata configuration file and data publishing adapter in the corresponding engineering design discipline, and publish the factory object reference design data to the corresponding professional data domain in the Factory Object Reference Design Data Collaborative Management Unit.

[0116] The factory object design data publishing subunit includes a metadata parsing module, a factory object tag design data generation module, and a factory object tag design data publishing module. These modules are connected sequentially, and both the metadata parsing module and the factory object tag design data publishing module are connected to the factory object tag design data collaborative management unit. The factory object tag design data generation module is connected to the design data server of the corresponding engineering design discipline.

[0117] The metadata parsing module is used in the corresponding engineering design discipline to parse the received metadata configuration file using the received data publishing adapter, extract the corresponding factory object reference design metadata, and send the factory object reference design metadata to the factory object reference design data generation module.

[0118] The factory object reference design data generation module is used to match and collect the corresponding design data in the design data server of the corresponding engineering design profession based on the factory object reference design metadata, generate the corresponding factory object reference design data, and send the factory object reference design data to the factory object reference design data publishing module.

[0119] The Factory Object Design Data Publishing Module is used to publish the factory object design data to the corresponding professional data field in the Factory Object Design Data Collaborative Management Unit through the data publishing adapter corresponding to the current engineering design profession.

[0120] This invention provides a cross-disciplinary collaborative management method and system for factory object tag design data. Through metadata configuration files and data publishing adapters, it achieves unified metadata definition, eliminating the imbalance between integration and collaborative work development. Professional data domains effectively isolate factory object tag design data from different disciplines, ensuring data independence and facilitating change management and tracking. A shared factory object data warehouse enables targeted merging of similar items across disciplines, allowing for horizontal data comparison between different disciplines and breaking down information barriers. Data-level professional change management based on factory object tag numbers allows for the assessment of the impact of inter-discipline design changes, facilitating multi-discipline collaborative changes. Project-level factory object tag design data consistency analysis helps different design disciplines find common ground while respecting differences, strengthening the construction of common data standards, and improving design standardization and delivery quality.

[0121] This invention is not limited to the optional embodiments described above, and anyone can derive other various forms of products based on the inspiration of this invention. The specific embodiments described above should not be construed as limiting the scope of protection of this invention; the scope of protection of this invention should be determined by the claims, and the specification can be used to interpret the claims.

Claims

1. A cross-disciplinary collaborative management method for factory object tag design data, characterized in that: Includes the following steps: Construct a factory object tag data warehouse, and set up corresponding professional data fields in the factory object tag data warehouse according to several engineering design specialties; Based on the characteristics of the professional software data of each engineering design discipline, corresponding metadata configuration files and data publishing adapters are constructed respectively. In the factory object tag data warehouse, a data sharing structure is constructed based on several professional data domains, several metadata configuration files and data publishing adapters, and several engineering design specialties, including the following steps: In the factory object tag data warehouse, based on several professional data fields, the same number of shared nodes are constructed, and the link relationship between each shared node and the corresponding professional data field is constructed. Establish the link relationship between each engineering design specialty and its corresponding shared nodes; Establish the link relationship between each shared node and its corresponding metadata configuration file and data publishing adapter; A data sharing structure is constructed based on several professional data domains, several metadata configuration files and data publishing adapters, several engineering design specialties, the link relationships between each shared node and its corresponding professional data domain, the link relationships between each engineering design specialty and its corresponding shared node, and the link relationships between each shared node and its corresponding metadata configuration file and data publishing adapter. Based on the data sharing structure, the metadata configuration file and data publishing adapter are published to the corresponding engineering design disciplines; In each engineering design discipline, based on the metadata configuration file and data publishing adapter, the corresponding factory object tag design data is generated, and the factory object tag design data is published to the corresponding professional data domain, including the following steps: In various engineering design disciplines, the received data publishing adapter is used to parse the received metadata configuration file and extract the corresponding factory object tag design metadata. Generate the corresponding factory object design data based on the factory object design metadata; Publish the factory object tag design data to the corresponding professional data domain through the data publishing adapter corresponding to the current engineering design profession; In the factory object tag data warehouse, collaborative management is carried out on the factory object tag design data of each engineering design specialty in each professional data domain; The collaborative management includes data merging, consistency analysis, and change tracking of factory object tag design data.

2. The method for cross-disciplinary collaborative management of factory object tag design data according to claim 1, characterized in that: The engineering design disciplines mentioned include process, equipment, instrumentation, electrical, piping, and architecture; The professional data domains corresponding to the engineering design major include data domains for process, equipment, instrumentation, electrical, piping, and architecture. The metadata configuration files corresponding to the engineering design specialty include metadata configuration files for process, equipment, instrumentation, electrical, piping, and building: The data publishing adapters corresponding to the engineering design major include data publishing adapters for process, equipment, instrumentation, electrical, piping, and architecture.

3. The method for cross-disciplinary collaborative management of factory object tag design data according to claim 1, characterized in that: In the factory object tag data warehouse, a data sharing structure is constructed based on several professional data domains, several metadata configuration files and data publishing adapters, and several engineering design disciplines, including the following steps: In the factory object tag data warehouse, based on several professional data domains, the same number of shared nodes are constructed, and the link relationship between each shared node and the corresponding professional data domain is constructed. Establish the link relationship between each engineering design specialty and its corresponding shared nodes; Establish the link relationship between each shared node and its corresponding metadata configuration file and data publishing adapter; A data sharing structure is constructed based on several professional data domains, several metadata configuration files and data publishing adapters, several engineering design specialties, the link relationships between each shared node and its corresponding professional data domain, the link relationships between each engineering design specialty and its corresponding shared node, and the link relationships between each shared node and its corresponding metadata configuration file and data publishing adapter.

4. The method for cross-disciplinary collaborative management of factory object tag design data according to claim 1, characterized in that: Each engineering design discipline generates the corresponding factory object tag design data based on the metadata configuration file and data publishing adapter, and publishes the factory object tag design data to the corresponding professional data domain, including the following steps: Each engineering design discipline uses the received data publishing adapter to parse the received metadata configuration file and extract the corresponding factory object tag design metadata; Generate the corresponding factory object design data based on the factory object design metadata; The factory object tag design data is published to the corresponding professional data domain through the data publishing adapter corresponding to the current engineering design profession.

5. The method for cross-disciplinary collaborative management of factory object tag design data according to claim 1, characterized in that: The collaborative management includes data merging, consistency analysis, and change tracking of factory object reference design data; In the factory object tag data warehouse, collaborative management of factory object tag design data for each engineering design specialty in each professional data domain is carried out, including the following steps: Constructing an entity recognition model in the factory object tag data warehouse; Using an entity recognition model, extract historical design data entities from several historical design data of various engineering design disciplines; Based on several historical design data entities, several professional design knowledge corresponding to each engineering design discipline is obtained; By integrating several professional design knowledge from various engineering design disciplines, a professional design knowledge graph is constructed. Using entity recognition models, design data entities are extracted from the factory object tag design data of each engineering design specialty in each professional data domain. Based on the professional design knowledge graph, the design data entities with common characteristics of the design data of the object tag design data of each factory are merged to obtain the merged factory object tag design data. A consistency analysis is performed on the design data entities based on the horizontal relationships between the design data of each factory object tag number, and a consistency report is obtained. Change tracking is performed on the design data entities of the object tag design data of each factory, recording the changed design data entities and their respective factory object tag design data, and a change tracking report is obtained.

6. A cross-disciplinary collaborative management system for factory object tag design data, based on the cross-disciplinary collaborative management method for factory object tag design data as described in any one of claims 1-5, characterized in that: It includes a factory object tag design data collaborative management unit and a factory object design data publishing unit. The factory object tag design data collaborative management unit is connected to the factory object design data publishing unit. The factory object design data publishing unit is set up in each engineering design discipline, and the factory object design data publishing unit is connected to the design data server of each engineering design discipline. The Factory Object Design Data Collaborative Management Unit is used to construct a Factory Object Design Data Warehouse. Based on several engineering design specialties, it sets up several corresponding professional data fields in the Factory Object Design Data Warehouse. Based on the professional software data characteristics of each engineering design specialty, it constructs corresponding metadata configuration files and data publishing adapters. In the Factory Object Design Data Warehouse, based on several professional data fields, several metadata configuration files and data publishing adapters, and several engineering design specialties, it constructs a data sharing structure. Based on the data sharing structure, it publishes the metadata configuration files and data publishing adapters to the Factory Object Design Data Publishing Unit. In the Factory Object Design Data Warehouse, it performs collaborative management of the Factory Object Design Data of each engineering design specialty in each professional data field. The Factory Object Design Data Publishing Unit is used to generate corresponding factory object tag design data for each engineering design discipline based on metadata configuration files and data publishing adapters, and to publish the factory object tag design data to the professional data domain corresponding to the Factory Object Tag Design Data Collaborative Management Unit.

7. The cross-disciplinary collaborative management system for factory object tag design data according to claim 6, characterized in that: The factory object tag design data collaborative management unit includes a factory object tag data warehouse module, a configuration file and adapter construction module, a data sharing structure construction module, a configuration file and adapter publishing module, and a factory object tag design data collaborative management module. The factory object tag data warehouse module is connected to the configuration file and adapter construction module, the data sharing structure construction module, the configuration file and adapter publishing module, the factory object tag design data collaborative management module, and the factory object design data publishing unit, respectively. The Factory Object Tag Data Warehouse module is used to build and store the Factory Object Tag Data Warehouse, and to set up several professional data fields in the Factory Object Tag Data Warehouse according to several engineering design specialties. The configuration file and adapter building module constructs corresponding metadata configuration files and data publishing adapters based on the characteristics of professional software data for each engineering design discipline, and sends the metadata configuration files and data publishing adapters to the factory object tag data warehouse module. The data sharing structure building module is used to build a data sharing structure in the factory object tag data warehouse based on several professional data domains, several metadata configuration files and data publishing adapters, and several engineering design disciplines. The configuration file and adapter publishing module is used to publish metadata configuration files and data publishing adapters to data publishing units designed through factory objects, based on the data sharing structure. The Factory Object Design Data Collaborative Management Module is used to collaboratively manage the factory object design data of various engineering design disciplines in various professional data domains within the factory object design data warehouse. It also includes an entity recognition model and a professional design knowledge graph.

8. The cross-disciplinary collaborative management system for factory object tag design data according to claim 7, characterized in that: The data sharing structure construction module includes a shared node construction submodule, a link relationship construction submodule, and a data sharing structure construction submodule. The shared node construction submodule, the link relationship construction submodule, and the data sharing structure construction submodule are connected in sequence, and both the shared node construction submodule and the data sharing structure construction submodule are connected to the factory object tag data warehouse module. The shared node construction submodule is used to construct the same number of shared nodes in the factory object tag data warehouse according to several professional data fields; The link relationship building submodule is used to build the link relationship between each shared node and the corresponding professional data domain, the link relationship between each engineering design profession and the corresponding shared node, and the link relationship between each shared node and the corresponding metadata configuration file and data publishing adapter. The data sharing structure construction submodule is used to construct the data sharing structure based on several professional data domains, several metadata configuration files and data publishing adapters, several engineering design specialties, the link relationship between each shared node and its corresponding professional data domain, the link relationship between each engineering design specialty and its corresponding shared node, and the link relationship between each shared node and its corresponding metadata configuration file and data publishing adapter. The factory object tag design data collaborative management module includes an entity recognition model submodule, a professional design knowledge graph submodule, a collaborative management submodule, a data merging submodule, a consistency analysis submodule, and a change tracking submodule. The entity recognition model submodule, the professional design knowledge graph submodule, the data merging submodule, the consistency analysis submodule, and the change tracking submodule are all connected to the collaborative management submodule, and the entity recognition model submodule is connected to the professional design knowledge graph submodule. The collaborative management submodule is connected to the factory object tag data warehouse module. The text entity recognition sub-model module is used to build an entity recognition model. Using the entity recognition model, it extracts historical design data entities from several historical design data of various engineering design disciplines and sends the obtained historical design data entities to the professional design knowledge graph sub-module. Using the entity recognition model, it extracts design data entities from the factory object tag design data of various engineering design disciplines in the professional data domains of the factory object tag design data warehouse module and sends the design data entities of several factory object tag design data to the collaborative management sub-module. The Professional Design Knowledge Graph submodule is used to obtain several professional design knowledge corresponding to each engineering design profession based on several historical design data entities, integrate the several professional design knowledge of each engineering design profession, construct a professional design knowledge graph, and send the professional design knowledge graph to the Collaborative Management submodule. The Collaborative Management submodule is used to receive design data entities of several factory object tag design data sent by the Text Entity Recognition Submodel Module and professional design knowledge graph sent by the Professional Design Knowledge Graph Submodule. According to the collaborative management requirements, it calls the corresponding Data Merging Submodule, Consistency Analysis Submodule and Change Tracking Submodule, and receives the merged factory object tag design data sent by the Data Merging Submodule, the consistency report sent by the Consistency Analysis Submodule and the change tracking report sent by the Change Tracking Submodule. The data merging submodule is used to extract the design data entities and professional design knowledge graphs of several factory object tag design data stored in the collaborative management submodule. It merges the design data entities with common characteristics of each factory object tag design data in the factory object tag data warehouse module to obtain the merged factory object tag design data, and sends the merged factory object tag design data to the collaborative management submodule. The consistency analysis submodule is used to extract the design data entities of several factory object tag design data stored in the collaborative management submodule, perform consistency analysis on the design data entities with horizontal relationships between the design data of each factory object tag design data, obtain a consistency report, and send the consistency report to the collaborative management submodule; The change tracking submodule is used to extract the design data entities of several factory object tag design data stored in the collaborative management submodule, track the changes of the design data entities of each factory object tag design data, record the changed design data entities and their respective factory object tag design data, obtain a change tracking report, and send the change tracking report to the collaborative management submodule. The factory object design data publishing unit includes several factory object design data publishing sub-units with the same structure. Each of the factory object design data publishing sub-units is connected to the factory object tag design data collaborative management unit and the design data server of the corresponding engineering design profession. The Factory Object Design Data Publishing Subunit is used to generate the corresponding factory object reference design data according to the metadata configuration file and data publishing adapter in the corresponding engineering design discipline, and publish the factory object reference design data to the corresponding professional data domain in the Factory Object Reference Design Data Collaborative Management Unit. The factory object design data publishing subunit includes a metadata parsing module, a factory object tag design data generation module, and a factory object tag design data publishing module. The metadata parsing module, the factory object tag design data generation module, and the factory object tag design data publishing module are connected in sequence. The metadata parsing module and the factory object tag design data publishing module are both connected to the factory object tag design data collaborative management unit. The factory object tag design data generation module is connected to the design data server of the corresponding engineering design discipline. The metadata parsing module is used in the corresponding engineering design discipline to parse the received metadata configuration file using the received data publishing adapter, extract the corresponding factory object reference design metadata, and send the factory object reference design metadata to the factory object reference design data generation module. The factory object reference design data generation module is used to match and collect the corresponding design data in the design data server of the corresponding engineering design profession based on the factory object reference design metadata, generate the corresponding factory object reference design data, and send the factory object reference design data to the factory object reference design data publishing module. The Factory Object Design Data Publishing Module is used to publish the factory object design data to the corresponding professional data field in the Factory Object Design Data Collaborative Management Unit through the data publishing adapter corresponding to the current engineering design profession.