Real-time Construction Method and Application System of Dynamic Data Standards and Data Models

Abstract

The present invention discloses a method for real-time construction of a dynamic data standard and a data model. The method for constructing a dynamic data standard and a data model includes the following steps: S1, based on business activities, identify the work process, data flow, and business nodes, and construct a business node directory tree; S2, based on the business nodes, identify engineering objects, construct a hierarchical decomposition structure according to the characteristics of engineering facilities, and construct an engineering object directory tree; S3, construct the relationship between business nodes and engineering objects; S4, create an engineering object entity table; S5, according to the characteristics of business nodes; S6, define the attribute authority node; S7, construct a software mapping relationship, identify the homologous end / terminal of the engineering object attributes, and design the mapping relationship of the software table data. An application system for a dynamic data standard and a data model is also disclosed. The method for constructing a dynamic data standard and a data model and the application system provided by the present invention ensure the effective flow of data between various business nodes, and achieve the purpose of defining data at one point and sharing globally.

Description

Technical Field

[0001] The present invention belongs to the technical field of engineering design and manufacturing in the oil and gas industry, and particularly relates to a method for real-time construction of dynamic data standards and data models and an application system. Background Art

[0002] In the process of enterprise digital transformation, the data model is a virtual reproduction of business activities, and the in-depth participation of business personnel is one of the necessary conditions to ensure the accuracy of the data model. Traditional data modeling work is mainly led by the information technology department, generally starting from a technical perspective. Without relevant background knowledge, it is difficult for business personnel to effectively convert business activities into data models; while IT personnel, due to their unfamiliarity with business activities, are also unable to independently complete the data model construction work. At the same time, in the process of engineering design in the oil and gas industry, various CAD (Computer Aided Design) and CAE (Computer Aided Engineering) software are usually used to complete the design of engineering products. These software are relatively independent, resulting in scattered data distributed in different databases, causing information islands and bringing great inconvenience to the distribution of data and tasks.

[0003] Therefore, there is an urgent need to design a method for real-time construction of dynamic data standards and data models and an application system to solve the problems in the above-mentioned existing technologies, where the software is relatively independent, resulting in scattered data distributed in different databases, causing information islands and bringing great inconvenience to the distribution of data and tasks. Summary of the Invention

[0004] To solve the technical problems in the background art, where the software in the existing technology is relatively independent, resulting in scattered data distributed in different databases, causing information islands and bringing great inconvenience to the distribution of data and tasks, a method for real-time construction of dynamic data standards and data models and an application system are provided to solve the above problems.

[0005] To achieve the above object, the specific technical solutions of the method for real-time construction of dynamic data standards and data models and the application system of the present invention are as follows:

[0006] A method for constructing dynamic data standards and data models includes the following steps:

[0007] S1. Based on business activities, identify the work process, data flow, and business nodes, and construct a business node directory tree;

[0008] S2. Based on business nodes, identify engineering objects, construct a hierarchical decomposition structure according to the characteristics of engineering facilities, and construct an engineering object directory tree;

[0009] S3. Based on the data carried by the business activity bearer of the business node, construct the relationship between the business node and the engineering object;

[0010] S4. Create an engineering object entity table;

[0011] S5. According to the characteristics of the business node, define the boundary relationship between the engineering object and the business node, form the input / output data standard of the engineering object in the business node, and constitute the data gateway for data flow between business nodes;

[0012] S6. Define the attribute authority node, input the source inspection of attributes, and at the same time select the business nodes of the attribute authority source;

[0013] S7. Construct the software mapping relationship and identify the mapping relationship between the data of the homologous / terminal design software tables of the engineering object attributes.

[0014] Furthermore, based on the business activities, construct a business node directory tree, accurately understand and create node directories and business nodes step by step according to the business domain, business node type, and business node object. The business nodes of the directory tree correspond to one or a class of specific business activities.

[0015] Furthermore, construct an engineering object directory tree. The engineering object identification methods include:

[0016] According to the engineering facility breakdown structure, take all physical objects with unique identification codes and instantiability in the facility as engineering objects;

[0017] Through the design information carried by the business node, refine and summarize the engineering objects carried by the business node. When multiple business nodes jointly describe the same engineering object, avoid duplicate creation of the engineering object to eliminate differences in understanding of the same engineering object between different business nodes;

[0018] During the process of analyzing the data information of the business node, some data is not carried by the engineering object, and this part of the data needs to create a carrier to carry it, which is usually summarized as a "virtual object" for creation.

[0019] Furthermore, construct the association relationship between the business node and the engineering object, and associate the engineering object by analyzing the data information carried by the business node; or from the perspective of the engineering object, screen the relevant business nodes for association.

[0020] Further, in S4, by traversing the business nodes associated with the engineering object, object attributes are identified to form an engineering object entity table. The attributes are created as object private attributes at the object level or as common attributes at the directory level created in S2. All objects under this directory level can reference the common attributes. Then, in S5, the relationships between the business nodes and the associated engineering object attributes are constructed, including input attributes and output attributes, to form the binding of the business flow and the data flow, realizing the transfer of data driven by the business flow between business nodes.

[0021] Further, in S6, by checking the source of the input attributes of the business nodes, the effective connection of data transfer between business nodes is ensured, and at the same time, semantic disambiguation of attributes across business nodes is also carried out. At the same time, by defining the authoritative source of attributes, the situation of data not being able to be confirmed due to multiple data sources is avoided, ensuring the uniqueness of the data source of the instantiated object.

[0022] Further, when the attributes in the entity table need to be sent to the professional design software or are generated by the professional design software, then in S7, the mapping relationship between the engineering object attribute homologous / terminal design software table data is identified, and the function of the business flow driving the data flow is extended to the relevant professional design software in the form of an interface.

[0023] An application system for a dynamic data standard and a data model includes the following steps:

[0024] S8, creating an instantiated project based on the enterprise-level data model database, and defining general engineering objects such as engineering facilities and monomers;

[0025] S9, creating instantiated business nodes as needed in the instantiated project;

[0026] S10, selecting standard business nodes for the instantiated business nodes, that is, selecting standard business nodes from the business node directory tree constructed in S1 and applying them to the instantiated business nodes;

[0027] S11, starting the instantiated business nodes, obtaining input data based on the standard nodes, and the platform obtaining relevant engineering objects and data generated by upstream professionals according to the input data standard formed in S5, and continuing to carry out business node activities on this basis;

[0028] S12, ending the instantiated business nodes, generating output data based on the standard nodes, submitting the business activity results after completing the business activities, and at the same time generating data of the engineering objects associated with this node according to the output data standard formed in S5;

[0029] S13, data rationality verification. When the data generated by the business node activities is transmitted to the system, the system will verify the data rationality, including mapping relationship check, data integrity, value range, etc.;

[0030] S14. The data is stored in the database. Through the interface development between the collaborative design platform and the lightweight 3D model, the data generated by business activities is displayed through the model, realizing a more intuitive visualization of data assets.

[0031] Furthermore, continue to carry out business node activities including:

[0032] S11.1. When the business activity is completed in an external professional design software, the design software side can obtain the upstream data at one key based on the mapping relationship defined in S7 and write it into the design software database.

[0033] S11.2. When the business activity is completed on the collaborative design platform, directly obtain the upstream data for designers to continue the design work.

[0034] Furthermore, the output data standard generates the data of the engineering objects associated with this node, including:

[0035] S12.1. When the business activity is completed based on an external design software, the data transfer from the design software to the collaborative design platform can be automatically realized based on the mapping relationship defined in S7 above.

[0036] S12.2. When the business activity is completed on the collaborative design platform, the collaborative design platform directly obtains the data generated during the design process and stores it.

[0037] S12.3. When the business activity is independently completed without the help of software or platform, it is necessary to enter or import it into the collaborative design platform according to the output data standard.

[0038] The real-time construction method and application system of the dynamic data standard and data model of the present invention

[0039] Compared with the prior art, the present invention breaks the conventional practice of using business activity nodes or business objects as entities, but constructs a data model based on the engineering objects at all levels refined from the engineering facility breakdown structure; further deepens the responsibility of data sources from the business object level or entity level to the attribute level, avoiding data redundancy caused by repeated definition of the same attribute by multiple business nodes, and at the same time constructing the input / output dimension models of data based on business node activities respectively, ensuring the effective flow of data between various business nodes and realizing the purpose of "defining at one point and sharing globally" of data. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Figure 1 It is a flowchart of the real-time construction method of the dynamic data standard and data model of the present invention;

[0041] Figure 2 It is a flowchart of the application system of the dynamic data standard and data model of the present invention;

[0042] Figure 3 It is a schematic diagram of the implementation method of steps S3 to S5 of the present invention;

[0043] Figure 4 It is an application architecture diagram of the business data model of the present invention;

[0044] Figure 5 It is a schematic diagram of the implementation method of steps S11 to S12 of the present invention;

[0045] Figure 6 It is a flowchart of the implementation of steps S11.1 and S12.2 of the present invention. Detailed implementation manners

[0046] To make the objectives, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Apparently, the described embodiments are some but not all of the embodiments of the present invention. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0047] Those skilled in the art can understand that although some of the embodiments herein include certain features included in other embodiments rather than other features, the combination of the features of different embodiments means that it is within the scope of the present invention and forms different embodiments. For example, in the claims, any one of the claimed embodiments can be used in any combination.

[0048] Next, refer to the attached Figure 1 to the attached Figure 6 Describe the real-time construction method and application system of the dynamic data standard and data model of the present invention.

[0049] The present invention includes two parts: a real-time construction method and an application system of a dynamic data standard and a data model. Among them, the real-time construction method of the dynamic data standard and the data model, as Figure 1 shown, includes the following steps:

[0050] S1. Based on business activities, construct a business node directory tree, accurately understand and create a node directory and business nodes step by step according to the business domain, business node type, and business node object. The business nodes of the directory tree correspond to one or a class of specific business activities; for the engineering design field, typical business nodes are design tasks, including specifications, drawings, data sheets, reports, etc. Creating business nodes also includes the following steps:

[0051] S1.1. Define design task types, such as specifications, drawings, data sheets, etc.;

[0052] S1.2, Design software related to specified business node activities;

[0053] S1.3, Define the design phases used by the business node, such as basic design, detailed design, etc.

[0054] S2, Identify engineering objects based on business nodes, construct a hierarchical decomposition structure according to the characteristics of engineering facilities, and construct an engineering object directory tree. The identification of engineering objects includes three methods, which are respectively:

[0055] S2.1, According to the engineering facility decomposition structure, all physical objects within the facility that have unique identification codes and can be instantiated are used as engineering objects;

[0056] S2.2, Through the design information carried by the business node, extract and summarize the engineering objects carried by the business node. When multiple business nodes jointly describe the same engineering object, duplicate creation of the engineering object should be avoided to eliminate differences in understanding of the same engineering object between different business nodes;

[0057] S2.3, During the process of analyzing business node data information, some data is not carried by engineering objects. This part of the data needs to create a carrier to carry it, and it is usually summarized as a "virtual object" for creation. It can carry necessary descriptive attributes such as systems and logistics, and can also ensure that the data flows normally between business nodes through the connection of virtual objects.

[0058] S3, Establish the association relationship between business nodes and engineering objects. From the perspective of business nodes, associate engineering objects by analyzing the data information carried by business nodes; or from the perspective of engineering objects, screen relevant business nodes for association.

[0059] S4, Define the corresponding entity table for the engineering object, that is, the process of creating attributes around the engineering object. Attributes can be created as object private attributes at the object level, or as common attributes in the directory tree created in S2. All objects located under this directory tree can reference the common attributes.

[0060] S5, Based on the engineering object, define the boundary relationship in the business node. Take the object attributes that the engineering object needs to obtain before the business node activity as the input data standard, and the attributes that need to be assigned when the business node activity ends as the output data standard; each business node can still define input and output standards with different depths according to the stage (such as the version number of the design document, the modeling stage, etc.).

[0061] S6. Selection of the source check of the input attributes of the service node and the authoritative source service node of the project object attributes. The former ensures the effective connection of data flow among service nodes and also performs semantic disambiguation on attributes across service nodes; the latter avoids the situation where data cannot be confirmed due to multiple data sources and ensures the uniqueness of the data source of the instantiated object data.

[0062] S7. Build the software mapping relationship and identify the mapping relationship between the data of the homologous / terminal design software tables of the project object attributes. If in the above S1 - S5, the design software related to the service node is specified, when submitting a task through the design software, the data of the design software table can be captured according to the output standard at the same time to realize the upload of project object data; conversely, when starting the service node activity, the software can obtain and write the data of the design software table according to the input standard to realize the download of project object data.

[0063] Furthermore, as Figure 3 shown, it is a schematic diagram of the implementation method of steps S3 - S5 of the present invention.

[0064] Build the association relationship between the service node and the project object. From the perspective of the service node, the project object can be associated by analyzing the data information carried by the service node; from the perspective of the project object, the relevant service nodes can be screened for association. Define the corresponding entity table for the project object, which is the process of creating attributes around the project object. Attributes can be created as private attributes of the object at the object level or as common attributes in the directory tree created in S2, and all objects under this directory tree can reference the common attributes. Define the boundary relationship of the project object in the service node. Take the object attributes that the project object needs to obtain before the service node activity as the input data standard, and the attributes that need to be assigned when the service node activity ends as the output data standard; each service node can still define input and output standards with different depths according to stages (such as the version number of the design document, the modeling stage, etc.).

[0065] The present invention includes two parts: a real-time construction method of dynamic data standards and data models and an application system. Among them, the architecture diagram of the application system of dynamic data standards and data models is as Figure 4As shown in the figure, it includes a data source layer, a data sharing layer, and a data application layer. The data source layer includes engineering design software such as intelligent PID, 3D design software, instrument design software, electrical design software, and Excel form data. The data within the software is stored in the system data sharing layer through a standardized interface. The data sharing layer includes master data management, master data management, metadata management, data standards, data permissions, data applications, result files, structured data, material coding, data dictionaries, lineage analysis, etc. It is responsible for merging multi-source heterogeneous data based on the engineering object entity table and providing various data services to the data application layer. The data application layer includes functions such as enterprise portals, project gates, process management, historical projects, operation analysis, data spaces, data views, data retrieval, data analysis, and data services. On the one hand, this application layer carries the workflow, and on the other hand, it realizes the driving of the data flow through data interaction with the sharing layer.

[0066] The application of the dynamic data standard and data model in the present invention refers to the process of creating an instantiated project based on the enterprise-level data model database, and realizing the data collection, transmission, and storage of each business node by calling the standardized nodes in the data standard through the instantiated nodes in the project. As Figure 2 shown, it specifically includes the following steps:

[0067] S8. Create an instantiated project based on the enterprise-level data model database. In this step, it is necessary to define general engineering objects such as engineering facilities and single entities.

[0068] S9. Create instantiated business nodes in the instantiated project according to the project needs. For engineering design activities, a typical business node is a design task. Creating business nodes is actually a process of compiling the task lists of each design specialty.

[0069] S10. Select standard business nodes for the instantiated business nodes, that is, select standard business nodes from the business node directory tree constructed in S1 and apply them to the instantiated business nodes.

[0070] S11. Start the business node activity. The platform will obtain the relevant engineering objects and the data generated by the upstream business nodes according to the input data standard formed in S5 above. Designers will continue to carry out business node activities on this basis, specifically including:

[0071] S11.1. When the business activity is completed in an external professional design software, the design software side can obtain the upstream data with one key based on the mapping relationship defined in S7 and write it into the design software database;

[0072] S11.2. When the business activity is completed on the collaborative design platform, directly obtain the upstream data for designers to continue the design work.

[0073] S12. Finalize the instantiation of the business node, generate output data based on the standard node, and after completing the business activity, while submitting the results of the business activity, generate data for the engineering objects associated with this node according to the output data standard formed in S5 above. The specific methods include:

[0074] S12.1. When the business activity is completed based on an external design software, the data transfer from the design software to the collaborative design platform can be automatically realized based on the mapping relationship defined in S7 above;

[0075] S12.2. When the business activity is completed on the collaborative design platform, the collaborative design platform directly obtains the data generated during the design process and stores it;

[0076] S12.3. When the business activity is independently completed without the help of software or platform, it is necessary to enter or import it into the collaborative design platform according to the output data standard.

[0077] S13. Data rationality verification. When the data generated by the business node activities is transferred to the system, the system will verify the data rationality, including mapping relationship check, data integrity and value range, etc.

[0078] S14. Store the data in the database. Through the interface development between the collaborative design platform and the lightweight 3D model, the data generated by the business activities, including the structured data of engineering objects, various design result files, manufacturer information, etc., can be displayed through the model, realizing a more intuitive visualization of the data assets.

[0079] Further, as Figure 5 shown, it is a schematic diagram of the implementation method of steps S11 - S12 of the present invention. The instance object of the engineering object entity table (pressure gauge) is created when drawn by PID, and attributes such as tag number, temperature and pressure parameters are generated. These attributes will be used as the input for the design of the pressure gauge data table to automatically obtain the corresponding data at the start of the design. After further supplementing the selection parameters during the data table design process, the assignment of other attributes of the pressure gauge entity table is completed. When all relevant business nodes end, the assignment of all attributes of the entity table is completed.

[0080] Further, as Figure 6 shown, it is a flowchart of the implementation of steps S11.1 and S12.2 of the present invention. First, start the work task in the system. The software side obtains the task and the input data corresponding to the task through the interface plug-in. After completing the design task, while submitting the work task, the system will obtain the corresponding data from the software based on the output standard of the task, and after verification, store it in the engineering object entity table.

[0081] Compared with the prior art, the present invention breaks the conventional practice of using business activity nodes or business objects as entities. Instead, it constructs a data model based on engineering objects at all levels refined from the engineering facility breakdown structure. The responsibilities of data sources are further deepened from the business object level or entity level to the attribute level, avoiding data redundancy caused by repeated definition of the same attribute by multiple business nodes. At the same time, input / output dimension models of data are respectively constructed based on business node activities to ensure the effective flow of data between various business nodes, achieving the purpose of "defining at one point and sharing globally".

[0082] Obviously, the above embodiments of the present invention are merely examples for clearly illustrating the present invention, rather than limiting the implementation manners of the present invention. For those of ordinary skill in the art, other different forms of changes or alterations can be made based on the above description. It is not necessary and impossible to enumerate all implementation manners here. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the claims of the present invention.

Claims

1. A real-time construction method for a dynamic data standard and a data model, characterized in that, Including the following steps; S1. Based on business activities, identify the workflow, data flow, and business nodes, and construct a business node directory tree; S2. Based on business nodes, identify engineering objects, construct a hierarchical decomposition structure according to the characteristics of engineering facilities, and construct an engineering object directory tree; S3. Based on the data carried by the business activity carriers of business nodes, construct the relationship between business nodes and engineering objects; S4. Create an engineering object entity table; S5. According to the characteristics of business nodes, define the boundary relationship between engineering objects and business nodes, form the input / output data standard of engineering objects in business nodes, and constitute a data gateway for data flow between business nodes; S6. Define the authoritative attribute nodes, perform source inspection of input attributes, and select the business nodes of the authoritative attribute sources at the same time; S7. Construct a software mapping relationship, and identify the mapping relationship between the homologous / terminal design software table data of engineering object attributes; Construct a business node directory tree based on business activities, accurately understand and create node directories and business nodes step by step according to the business domain, business node type, and business node object. Each business node in the directory tree corresponds to one or a class of specific business activities.

2. The real-time construction method of the dynamic data standard and data model according to claim 1, wherein, Construct an engineering object directory tree. The engineering object identification methods include: According to the engineering facility decomposition structure, all physical objects with unique identification codes and instantiability in the facility are regarded as engineering objects; Through the design information carried by business nodes, refine and summarize the engineering objects carried by these business nodes. When multiple business nodes jointly describe the same engineering object, avoid duplicate creation of engineering objects to eliminate differences in the understanding of the same engineering object between different business nodes; In the process of analyzing business node data information, some data is not carried by engineering objects. This part of the data needs to create a carrier to carry it, and is usually summarized as a "virtual object" for creation.

3. The real-time construction method of the dynamic data standard and data model according to claim 1, characterized in that Construct the association relationship between business nodes and engineering objects, and associate engineering objects by analyzing the data information carried by business nodes; or from the perspective of engineering objects, screen the relevant business nodes for association.

4. The real-time construction method of the dynamic data standard and data model according to claim 1, characterized in that, In S4, identify object attributes by traversing the business nodes associated with engineering objects to form an engineering object entity table. Attributes are created as object private attributes at the object level, or as common attributes at the directory level created in S2. All objects under this directory level can reference the common attributes; then construct the relationship between business nodes and the attributes of associated engineering objects in S5, including input attributes and output attributes, to form the binding of business flow and data flow, and realize the flow of data driven by business flow between business nodes.

5. The real-time construction method of the dynamic data standard and data model according to claim 1, characterized in that, In S6, ensure the effective connection of data flow between business nodes through source inspection of business node input attributes, and perform semantic disambiguation on attributes across business nodes; at the same time, avoid the situation of data non-rights confirmation caused by multi-source data by defining the authoritative attribute source, and ensure the uniqueness of the data source of instantiated objects.

6. The real-time construction method of the dynamic data standard and data model according to claim 1, characterized in that When the attributes in the entity table need to be sent to the professional design software or are generated by the professional design software, the mapping relationship of the homologous end / end design software table data of the engineering object attributes recognized by S7 is used to extend the function of the business flow driving the data flow to the relevant professional design software in the form of an interface.

7. An application system of a dynamic data standard and a data model, applied to the method as described in claim 1, characterized in that Create an instantiated project based on the enterprise-level data model database, and define engineering facilities and monomer general engineering objects; Create instantiated business nodes according to project requirements in the instantiated project; Select standard business nodes for the instantiated business nodes, that is, select standard business nodes from the business node directory tree constructed in S1 and apply them to the instantiated business nodes; Start the instantiated business node, obtain input data based on the standard node, and the platform obtains relevant engineering objects and data generated by the upstream specialty according to the input data standard formed in S5, and continues to carry out business node activities on this basis; End the instantiated business node, generate output data based on the standard node, submit the business activity results after completing the business activity, and at the same time generate data of the engineering objects associated with this node according to the output data standard formed in S5; Data rationality verification: When the data generated by the business node activities is transmitted to the system, the system will verify the data rationality, including mapping relationship check, data integrity and value range; Store the data in the database. Through the interface development between the collaborative design platform and the lightweight 3D model, the data generated by the business activities is displayed through the model to achieve more intuitive visualization of the data assets.

8. The application system of the dynamic data standard and data model according to claim 7, characterized in that, Continuing to carry out business node activities includes: When the business activity is completed in the external professional design software, the design software side can obtain the upstream data with one key based on the mapping relationship defined in S7 and write it into the design software database; When the business activity is completed on the collaborative design platform, directly obtain the upstream data for the designers to continue the design work.

9. The application system of the dynamic data standard and data model according to claim 7, characterized in that Generating data of the engineering objects associated with this node by the output data standard includes: When the business activity is completed based on the external design software, the data transfer from the design software to the collaborative design platform is automatically realized based on the mapping relationship defined in S7 above; When the business activity is completed on the collaborative design platform, the collaborative design platform directly obtains the data generated during the design process and stores it; When the business activity is independently completed without the help of software or platform, it is necessary to enter or import it into the collaborative design platform according to the output data standard on the collaborative platform.

Images