Drawing heterogeneous data standardization method and system, electronic equipment and storage medium

Abstract

The invention provides a drawing heterogeneous data standardization method and system, electronic equipment and a storage medium. The method comprises the following steps: based on an OEM model, extracting unstructured drawing heterogeneous data; adapters in one-to-one correspondence with the extracted unstructured drawing heterogeneous data are established, an adapter library of data files is formed, semi-structured data based on an OEM model is formed, and a directed graph based on the OEM model is obtained; the XML-based data middle layer effectively organizes and manages semi-structured data of the directed graph based on the OEM model to form structured integrated data, and external interfaces and use are unified. The internal organization structure of the data is flexible and changeable, good expansibility is achieved, the drawing is subjected to standardization processing, information in the drawing is extracted and effectively organized, and high-quality basic data can be provided for data analysis.

Description

Technical Field

[0001] The present invention belongs to the technical field of drawing data processing, and in particular relates to a drawing heterogeneous data normalization method, system, electronic equipment and storage medium. Background Art

[0002] At present, the ship design process generates a large amount of data and files, such as layout drawings, process piping diagrams, system schematics, equipment installation drawings, equipment technical requirements, system manuals and other unstructured files. The total amount of these data is extremely large and the span is long. Data types include WORD files, CAD files, pictures, videos, etc.

[0003] The process piping drawings of ship power systems are mainly used for system design and to guide the construction of ship power systems. The internal information of the process piping drawings of ship power systems includes systems, equipment, pipelines, pipeline accessories, connection relationships between equipment, interfaces, technical requirements, etc. These drawings are very rich in internal information, but after the ship is built, due to the use of CAD and other formats as carriers, the internal information is often not effectively used. The query and use of information can generally only use the file name, keywords, author, publication time and other information of the data. The information in the file often requires manual browsing by personnel to view. The existence of unstructured data has seriously affected the establishment of ship knowledge bases and data analysis applications. When other designers use them, they need to repeatedly view and search multiple drawing files, which affects information reuse.

[0004] These files are generally called unstructured data, and these unstructured data are difficult to use.

[0005] Therefore, how to provide a method, system, electronic device and storage medium for normalizing heterogeneous drawing data has become a technical problem that urgently needs to be solved in this field. Summary of the invention

[0006] The purpose of the present invention is to provide a method, system, electronic device and storage medium for normalizing heterogeneous drawing data.

[0007] According to a first aspect of the present invention, a method for normalizing heterogeneous drawing data is provided, comprising:

[0008] Step S1: extracting unstructured heterogeneous drawing data based on the OEM model;

[0009] Step S2, establishing adapters corresponding one-to-one to the extracted unstructured drawing heterogeneous data, forming an adapter library of data files, forming semi-structured data based on the OEM model, and obtaining a directed graph based on the OEM model;

[0010] Step S3: The XML-based data middle layer effectively organizes and manages the semi-structured data of the directed graph based on the OEM model, forms structured integrated data, and unifies the external interface and usage.

[0011] Preferably, in the step S1, the OEM model is a model in an extensible format.

[0012] Preferably, in step S1, extracting unstructured heterogeneous drawing data includes one or more of the following:

[0013] 1) Name of the drawing;

[0014] 2) Drawing code;

[0015] 3) Drawing scale;

[0016] 4) Weight;

[0017] 5) Owner information;

[0018] 6) Parts list information;

[0019] 7) Tile information;

[0020] 8) Drawing address.

[0021] Preferably, in the step S1, the extracting of unstructured heterogeneous drawing data further comprises: proprietary extraction content;

[0022] The proprietary extraction content includes one or more of the following:

[0023] Marking information, key parameters, technical descriptions or technical requirements.

[0024] Preferably, in step S2, the directed graph is a hierarchical sub-graph based on a drawing.

[0025] Preferably, in step S2, the first level of the directed graph is the drawing name; the second level is one or more of the drawing name, drawing code, drawing scale, weight, owner information, parts list information, block information or drawing address; and the third level is the specific information content corresponding to the second level name.

[0026] Preferably, the drawings are divided into drawings of the conceptual design, technical design or construction design stage, and are classified in the OEM model.

[0027] The second aspect of the present invention discloses a drawing heterogeneous data normalization system; the system comprises:

[0028] A first processing module is configured to extract unstructured drawing heterogeneous data based on the OEM model;

[0029] The second processing module is configured to establish adapters corresponding to the extracted unstructured heterogeneous drawing data one by one, form an adapter library of data files, form semi-structured data based on the OEM model, and obtain a directed graph based on the OEM model;

[0030] The third processing module is configured to effectively organize and manage the semi-structured data of the directed graph based on the OEM model based on the XML data middle layer, form structured integrated data, and unify the external interface and use.

[0031] According to the system of the second aspect of the present invention, the first processing module is specifically configured such that the OEM model is a model in an extensible format.

[0032] According to the system of the second aspect of the present invention, the first processing module is specifically configured to extract unstructured heterogeneous drawing data including one or more of the following:

[0033] 1) Name of the drawing;

[0034] 2) Drawing code;

[0035] 3) Drawing scale;

[0036] 4) Weight;

[0037] 5) Owner information;

[0038] 6) Parts list information;

[0039] 7) Tile information;

[0040] 8) Drawing address.

[0041] According to the system of the second aspect of the present invention, extracting unstructured heterogeneous drawing data includes: proprietary extraction content; the proprietary extraction content includes one or more of the following: annotation information, key parameters, technical descriptions or technical requirements.

[0042] According to the system of the second aspect of the present invention, the second processing module is specifically configured so that the directed graph is a hierarchical sub-graph based on a drawing.

[0043] According to the system of the second aspect of the present invention, the second processing module is specifically configured as follows: the first level of the directed graph is the drawing name; the second level is one or more of the drawing name, drawing code, drawing scale, weight, owner information, parts list information, block information or drawing address; and the third level is the specific information content corresponding to the name of the second level.

[0044] According to the system of the second aspect of the present invention, the second processing module is specifically configured to classify the drawings into drawings of the conceptual design, technical design or construction design stage, and classify them in the OEM model.

[0045] The third aspect of the present invention discloses an electronic device, which includes a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the steps in any one of the drawing heterogeneous data normalization methods in the first aspect of the present disclosure are implemented.

[0046] The fourth aspect of the present invention discloses a computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps in any one of the drawing heterogeneous data normalization methods in the first aspect of the present disclosure are implemented.

[0047] The beneficial effects brought by the present invention are as follows:

[0048] The dynamic normalization method is adopted, and the internal organizational structure of the data is flexible and has good scalability, which effectively meets the requirements of data normalization of the process piping diagram of the ship power system. Normalizing the process piping diagram of the ship power system, extracting the information and organizing it effectively can provide high-quality basic data for data analysis and lay the foundation for intelligent knowledge management and knowledge scenario application of ships. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] Figure 1 A flowchart of a method for normalizing heterogeneous drawing data provided according to an embodiment;

[0050] Figure 2 A directed graph of a method for normalizing heterogeneous drawing data provided according to an embodiment;

[0051] Figure 3 A schematic diagram of drawing names and codes in a drawing in a method for normalizing heterogeneous drawing data provided according to an embodiment;

[0052] Figure 4 A schematic diagram of owner information in a drawing in a method for normalizing heterogeneous drawing data provided according to an embodiment;

[0053] Figure 5 A schematic diagram of comprehensive parts list information in a drawing in a method for normalizing heterogeneous drawing data provided according to an embodiment;

[0054] Figure 6 A schematic diagram of block information in a drawing in a method for normalizing heterogeneous drawing data provided according to an embodiment;

[0055] Figure 7A schematic diagram of proprietary extracted content in a drawing in a method for normalizing heterogeneous drawing data provided according to an embodiment;

[0056] Figure 8 A schematic diagram of annotation information in a drawing in a method for normalizing heterogeneous drawing data provided according to an embodiment;

[0057] Fig. 9 A schematic diagram of an interface comparison in a drawing in a method for normalizing heterogeneous drawing data provided according to an embodiment;

[0058] Fig.10 A structural diagram of a drawing heterogeneous data normalization system according to an embodiment of the present invention;

[0059] Fig.11 The figure is a structural diagram of an electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0060] In order to make the purpose, technical solution and advantages of the present invention clearer, the technical solution in the embodiment of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiment of the present invention. Obviously, the described embodiment is a part of the embodiment of the present invention, not all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0061] In order to effectively utilize the internal information of unstructured data, the OEM (object exchange model) method was used to extract data information from unstructured data, as follows:

[0062] 1) Standardized description based on OEM model

[0063] Based on the OEM model, information extraction and planned description of heterogeneous files such as technical documents and technical drawings can be performed, so that various types of data can be described conveniently, flexibly and accurately, which is suitable for process piping drawings generated in the ship power process.

[0064] 2) XML-based data middle layer for data summarization and integration

[0065] The OEM models generated at different stages of ship design are integrated through the unified XML format to adapt to data transmission and processing. It has the advantages of good scalability, good consistency, separation of content and form, and good self-description.

[0066] 3) Specification integration of ship power system process piping drawings

[0067] Through the heterogeneous data integration method, the heterogeneous data of the ship power system process piping drawings are integrated to form a unified external access interface. This patent adopts a dynamic normalization method, and its internal organizational structure of data is flexible and has good scalability, which effectively meets the requirements of ship power system process piping diagram data normalization.

[0068] The ship power design process generates a large amount of heterogeneous data such as process piping diagrams, mainly in CAD format, which often cannot be effectively reused. Through this solution, the heterogeneous data of the ship power system process piping can be standardized, and the information can be extracted and effectively organized, which can provide high-quality basic data for subsequent data analysis and lay the foundation for intelligent knowledge management and knowledge scenario application.

[0069] Embodiment 1:

[0070] According to a first aspect of the present invention, the present invention discloses a method for normalizing heterogeneous drawing data. Figure 1 FIG. 1 is a flow chart of a method for normalizing heterogeneous drawing data according to an embodiment of the present invention. Figure 1 As shown, the method includes:

[0071] Step S1: extracting unstructured heterogeneous drawing data based on the OEM model;

[0072] In the step S1, the OEM model is a model in an extensible format.

[0073] In step S1, extracting unstructured heterogeneous drawing data includes one or more of the following:

[0074] 1) Name of the drawing;

[0075] 2) Drawing code;

[0076] 3) Drawing scale;

[0077] 4) Weight;

[0078] 5) Owner information;

[0079] 6) Parts list information;

[0080] 7) Tile information;

[0081] 8) Drawing address.

[0082] In the step S1, the extracting of unstructured heterogeneous drawing data further includes: proprietary extraction content;

[0083] The proprietary extraction content includes one or more of the following:

[0084] Marking information, key parameters, technical descriptions or technical requirements.

[0085] Step S2, establishing adapters corresponding one-to-one to the extracted unstructured drawing heterogeneous data, forming an adapter library of data files, forming semi-structured data based on the OEM model, and obtaining a directed graph based on the OEM model;

[0086] In the step S2, the directed graph is a hierarchical sub-graph based on a drawing.

[0087] In step S2, the first level of the directed graph is the drawing name; the second level is one or more of the drawing name, drawing code, drawing scale, weight, owner information, parts list information, block information or drawing address; the third level is the specific information content corresponding to the second level name.

[0088] Step S3: The XML-based data middle layer effectively organizes and manages the semi-structured data of the directed graph based on the OEM model, forms structured integrated data, and unifies the external interface and usage.

[0089] The drawings are divided into drawings of the schematic design, technical design or construction design phase and are classified in the OEM model.

[0090] In summary, the main process of the heterogeneous data normalization proposed in the present invention is based on the heterogeneous data of a large number of process drawings generated by the ship power system, and the semi-structured data of the OEM directed graph is formed by extracting the heterogeneous data, and then the OEM model is effectively organized and managed based on the XML format to form structured integrated data for use by the business layer. Specifically, based on the OEM model, information extraction and planning description of heterogeneous files such as technical documents and technical drawings can be performed, so that various types of data can be described conveniently, flexibly and accurately, which is suitable for the process piping drawings generated in the ship power process; the OEM models generated at different stages of ship design are integrated through the unified format of XML to adapt to data transmission and processing. It has the advantages of good scalability, good consistency, separation of content and form, and good self-descriptiveness. Through the heterogeneous data integration method, the heterogeneous data of the process piping drawings of the ship power system are integrated and integrated to form a unified external access interface. This application adopts a dynamic normalization method, and its internal organizational structure of data is flexible and changeable, with good scalability, which effectively meets the requirements of data normalization of the process piping diagram of the ship power system. Standardizing the process piping diagrams of ship power systems, extracting information and organizing it effectively can provide high-quality basic data for data analysis and lay the foundation for intelligent knowledge management and knowledge scenario-based applications of ships.

[0091] Embodiment 2:

[0092] Based on the method for normalizing heterogeneous drawing data disclosed in Example 1, Figure 2 As shown, Example 2 normalizes heterogeneous data based on drawings of lubricating oil network test system schematics. The method is particularly suitable for drawings of process piping diagrams of ship power systems. The method includes:

[0093] Step S1, based on the OEM model, extract unstructured heterogeneous drawing data; based on the OEM model, extract information and plan description of heterogeneous files such as technical documents and technical drawings, so that various types of data can be described conveniently, flexibly and accurately, which is suitable for process piping drawings generated in the ship power process.

[0094] The OEM model is a model in an extensible format, and the extraction of unstructured heterogeneous drawing data includes one or more of the following:

[0095] The streams, characters and values ​​stored in the ship power system process piping diagram files cannot be directly used for data sharing and utilization. It is necessary to extract the data informatization of various types of data, turn these unstructured original records into information with content, and make them logical. The following technical design of the lubricating oil network test system schematic diagram is taken as an example to describe the heterogeneous data extraction and normalization processing method.

[0096] The general extraction content includes the following parts:

[0097] 1) For the content extraction of technical drawings, the drawing name should be extracted first

[0098] 2) Then extract its drawing code, such as Figure 3 As shown,

[0099] 3) Drawing scale

[0100] 4) Weight

[0101] 5) Owner information, such as design, proofreading, review, standard inspection, approval, etc. Figure 4 As shown;

[0102] 6) Comprehensive parts list information, taking "XXX-024-001 lubricating oil pipe network test system schematic diagram" as an example, the comprehensive parts list marks the accessories information involved in the system diagram: one electric control valve DN200 PN10, six electric control valves DN100 PN10, one lubricating oil relief valve DN150 PN10, two stop check valves A10200, two stop check valves A10125, four stop valves A10250, two stop valves A10200, two stop valves A10150, two stop valves A10125, one stop valve A10100, one stop valve A10040, four control valves A10040; such as Figure 5 shown.

[0103] 7) Block information, taking "XXX-024-001 Lubricating oil pipe network test system schematic diagram" as an example, the blocks include: temperature measuring points, pressure measuring points, flow measuring points, electric control valves, stop valves, regulating valves, stop check valves, electric lubricating oil pumps, lubricating oil filters, simulation devices, circulating lubricating oil cabinets, lubricating oil coolers, etc. Figure 6 shown.

[0104] 8) Technical drawing address

[0105] The physical storage address of the extraction technology pattern in the distributed system.

[0106] 9) Proprietary Extraction Content

[0107] (1) In technical drawings, more information is marked, such as dimension, shape and position tolerances, etc. Figure 7 However, not all of this information needs to be recorded, and not all drawings need to extract this information, so it is considered proprietary extraction content.

[0108] (2) In technical drawings, there is often some information that needs special explanation. Generally, text information such as notes, technical instructions or technical requirements will be written. This information is very important and needs to be extracted, but not all drawings have it. Therefore, it is necessary to locate the proprietary extraction content, such as Figure 8 shown.

[0109] (3) Some technical drawings, such as interface diagrams and system diagrams, will contain interface information. Some equipment general drawings will contain key parameters, which are often presented in the form of tables. Each technical drawing is different, and each designer has different habits. Therefore, it is positioned as proprietary extraction content and is defined at any time according to the specific technical drawings, such as Fig. 9 shown.

[0110] Step S2, establishing adapters corresponding one-to-one to the extracted unstructured drawing heterogeneous data, forming an adapter library of data files, forming semi-structured data based on the OEM model, and obtaining a directed graph based on the OEM model;

[0111] First, an extensible format is defined based on the OEM model to semi-structure the unstructured files, which contain common information but can also be extended with other information. The file-level adaptation of data mainly solves this problem. The main idea is to analyze the formats of a large number of original data files, establish adapters that correspond to these files one by one, and form an adapter library for data files.

[0112] Taking the "Schematic Diagram of Lubricating Oil Pipeline Network Test System" as an example, it reflects the directed graph based on the OEM model. As shown in Figure 2, it expresses a sample definition of the OEM model for this technical drawing. The formed OEM model is a directed graph that extracts and stores the key information in the technical document in the form of a directed graph. At the same time, through the OEM model, the technical drawing is associated with existing knowledge or other data (such as relevant standards, other technical drawings, etc.).

[0113] In step S2, the directed graph is a hierarchical sub-graph based on the drawing; as Figure 2 shown, the first level of the directed graph is the drawing name; the second level is one or more of the drawing name, drawing code, drawing scale, weight, owner information, parts list information, block information, or drawing address; the third level is the specific information content corresponding to the second-level name. Of course, there can also be a fourth level, a fifth level...; it depends on the specific situation of the drawing.

[0114] Step S3: Through XML format, effectively organize and manage the semi-structured data of the directed graph based on the OEM model to form structured integrated data, and unify the external interface and usage.

[0115] The drawings are divided into drawings in the scheme design, technical design, or construction design stages and are classified in the OEM model.

[0116] The advantages of XML in representing data have led to the emergence of a large number of integrated information relying on XML documents. And within a certain range, it is necessary to integrate XML documents containing different types of data.

[0117] And the design process of the entire project is divided into multiple stages such as scheme design, technical design, and construction design. Therefore, to effectively manage heterogeneous data information in the data middle layer, it is necessary to first establish an overall description of the XML documents in each stage of the project.

[0118] As shown, taking the achievements formed in each stage of the shipbuilding industry as an example, the XML document for constructing the overall project description according to the stage is as follows:[[]]

[0119] 1) The overall XML format is as follows:[[]]

[0120] <?xml version="1.0" encoding="GB2312"?>[[]]

[0121] <XX Ship>[[]]

[0122] <Phase tag="Scheme Design">[[]]

[0123] <Start Time>20150816< / Start Time>[[]]

[0124] <Person in Charge>Zhang San< / Person in Charge>

[0125] <Document List>...< / Document List>

[0126] <Phase Transition Time>20160816< / Phase Transition Time>

[0127] < / Phase>

[0128] <Phase tag="Technical Design">

[0129] <Start Time>20160816< / Start Time>

[0130] <Person in Charge>Zhang San< / Person in Charge>

[0131] <Document List>...< / Document List>

[0132] <Phase Transition Time>20170816< / Phase Transition Time>

[0133] < / Phase>

[0134] <Phase tag="Construction Design">

[0135] <Start Time>20170816< / Start Time>

[0136] <Person in Charge>Li Si< / Person in Charge>

[0137] <Document List>...< / Document List>

[0138] <Phase Transition Time>20180816< / Phase Transition Time>

[0139] < / Phase>

[0140] < / XX Ship>

[0141] 2) The XML format of the Scheme Design Phase is as follows:

[0142] <Phase tag="Scheme Design Phase">

[0143] <Start Time>20150816< / Start Time>

[0144] <Person in Charge>Zhang San< / Person in Charge>

[0145] <Document List>

[0146] <Document tag="Lubricating Oil System" oem_address="xxx.xxx.xxx / Lubricating Oil System Schematic Diagram.oem">Schematic Diagram< / Document>

[0147] <Document tag="Steam System" oem_address="xxx.xxx.xxx / Schematic Diagram of Steam System.oem">Schematic Diagram< / Document>

[0148] <Document tag="Working Water System" oem_address="xxx.xxx.xxx / Schematic Diagram of Working Water System.oem">Schematic Diagram< / Document>

[0149] < / Document List>

[0150] <Phase Transition Time>20160816< / Phase Transition Time>

[0151] < / Phase>

[0152] 3) The XML format of the technical design phase is as follows:

[0153] <Phase tag="Technical Design">

[0154] <Start Time>20160816< / Start Time>

[0155] <Responsible Person>Zhang San< / Responsible Person>

[0156] <Document List>

[0157] <Document tag="Lubricating Oil System" oem_address="xxx.xxx.xxx / Schematic Diagram of Lubricating Oil System.oem">Schematic Diagram< / Document>

[0158] <Document tag="Steam System" oem_address="xxx.xxx.xxx / Schematic Diagram of Steam System.oem">Schematic Diagram< / Document>

[0159] <Document tag="Working Water System" oem_address="xxx.xxx.xxx / Schematic Diagram of Working Water System.oem">Schematic Diagram< / Document>

[0160] < / Document List>

[0161] <Phase Transition Time>20170816< / Phase Transition Time>

[0162] < / Phase>.

[0163] 4) The XML format of the construction design phase is as follows:

[0164] <Phase tag="Construction Design">

[0165] <Start Time>20170816< / Start Time>

[0166] <Responsible Person>Zhang San< / Responsible Person>

[0167] <List of Documents>

[0168] <Document tag="Lubricating Oil System" oem_address="xxx.xxx.xxx / Lubricating Oil System Pipeline Diagram.oem">Schematic Diagram< / Document>

[0169] <Document tag="Steam System" oem_address="xxx.xxx.xxx / Steam System Pipeline Diagram.oem">Schematic Diagram< / Document>

[0170] <Document tag="Working Water System" oem_address="xxx.xxx.xxx / Working Water System Pipeline Diagram.oem">Schematic Diagram< / Document>

[0171] < / List of Documents>

[0172] <Phase Transition Time>20180816< / Phase Transition Time>

[0173] < / Phase>.

[0174] Among them, for the heterogeneous data normalization of the distributed data management process, the OEM model is adopted to extract and normalize the heterogeneous data information, and the file-level OEM model adaptation of the technical drawings of the ship power system is elaborated in detail. Taking the schematic diagram of a certain system as an example, the OEM model foundation is initially constructed, and at the same time, how to construct the OEM model for other data types and how to expand the OEM model are elaborated.

[0175] For the heterogeneous data normalization of the data middle layer, the research on the heterogeneous data normalization of the data middle layer based on XML technology is adopted. For each stage of the overall project: the scheme design stage, the technical design stage, and the construction design stage, in addition to the basic XML format description, an association with the OEM model is established in the XML format description.

[0176] At the same time, the XML format can also be expanded. For example, first use the XML file to define the power system, then define different specialties (hull, outfitting, electrical) in each stage, and finally establish an association with the OEM model.

[0177] In summary, the above is only the preferred embodiment of the present invention and is not used to limit the protection scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

[0178] Embodiment 3:

[0179] The present invention discloses a drawing heterogeneous data normalization system. Fig.10is a structural diagram of a drawing heterogeneous data normalization system according to an embodiment of the present invention; Fig.10 As shown, the system 100 includes:

[0180] The first processing module 101 is configured to extract unstructured heterogeneous drawing data based on the OEM model;

[0181] The second processing module 102 is configured to establish adapters corresponding to the extracted unstructured heterogeneous drawing data one by one, form an adapter library of data files, form semi-structured data based on the OEM model, and obtain a directed graph based on the OEM model;

[0182] The third processing module 103 is configured to effectively organize and manage the semi-structured data of the directed graph based on the OEM model based on the XML data middle layer, form structured integrated data, and unify the external interface and use.

[0183] According to the system of the second aspect of the present invention, the first processing module 101 is specifically configured such that the OEM model is a model in an extensible format.

[0184] According to the system of the second aspect of the present invention, the first processing module 101 is specifically configured to extract unstructured heterogeneous drawing data including one or more of the following:

[0185] 1) Name of the drawing;

[0186] 2) Drawing code;

[0187] 3) Drawing scale;

[0188] 4) Weight;

[0189] 5) Owner information;

[0190] 6) Parts list information;

[0191] 7) Tile information;

[0192] 8) Drawing address.

[0193] According to the system of the second aspect of the present invention, extracting unstructured heterogeneous drawing data includes: proprietary extraction content; the proprietary extraction content includes one or more of the following: annotation information, key parameters, technical descriptions or technical requirements.

[0194] According to the system of the second aspect of the present invention, the second processing module 102 is specifically configured such that the directed graph is a hierarchical sub-graph based on a drawing.

[0195] According to the system of the second aspect of the present invention, the second processing module 102 is specifically configured as follows: the first level of the directed graph is the drawing name; the second level is one or more of the drawing name, drawing code, drawing scale, weight, owner information, parts list information, block information or drawing address; and the third level is the specific information content corresponding to the name of the second level.

[0196] According to the system of the second aspect of the present invention, the second processing module 102 is specifically configured to classify the drawings into drawings of the schematic design, technical design or construction design stage, and classify them in the OEM model.

[0197] Embodiment 4:

[0198] The present application discloses an electronic device, which includes a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the steps in a method for normalizing heterogeneous drawing data in any one of the embodiments 1 disclosed in the present invention are implemented.

[0199] Fig.11 is a structural diagram of an electronic device according to an embodiment of the present invention, such as Fig.11 As shown, the electronic device includes a processor, a memory, a communication interface, a display screen and an input device connected via a system bus. Among them, the processor of the electronic device is used to provide computing and control capabilities. The memory of the electronic device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The communication interface of the electronic device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be achieved through WIFI, an operator network, near field communication (NFC) or other technologies. The display screen of the electronic device can be a liquid crystal display screen or an electronic ink display screen, and the input device of the electronic device can be a touch layer covered on the display screen, or a button, a trackball or a touch pad set on the housing of the electronic device, or an external keyboard, touch pad or mouse, etc.

[0200] Those skilled in the art will understand that Fig.11 The structure shown in the figure is only a structural diagram of the part related to the technical solution of the present disclosure, and does not constitute a limitation on the electronic device to which the technical solution of the present application is applied. The specific electronic device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0201] Embodiment 5:

[0202] The present invention discloses a computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps in a method for normalizing heterogeneous drawing data in any one of the embodiments of the present invention are implemented.

[0203] Please note that the technical features of the above embodiments can be combined arbitrarily. In order to make the description concise, all possible combinations of the technical features in the above embodiments are not described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification. The above embodiments only express several implementation methods of the present application, and their descriptions are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that for ordinary technicians in this field, without departing from the concept of the present application, several variations and improvements can be made, which all belong to the scope of protection of the present application. Therefore, the scope of protection of the patent in this application shall be based on the attached claims.

[0204] The embodiments of the subject matter and functional operations described in this specification may be implemented in the following: digital electronic circuits, tangibly embodied computer software or firmware, computer hardware including the structures disclosed in this specification and their structural equivalents, or a combination of one or more of them. The embodiments of the subject matter described in this specification may be implemented as one or more computer programs, i.e., one or more modules in computer program instructions encoded on a tangible non-temporary program carrier to be executed by a data processing device or to control the operation of the data processing device. Alternatively or additionally, the program instructions may be encoded on an artificially generated propagation signal, such as a machine-generated electrical, optical or electromagnetic signal, which is generated to encode information and transmit it to a suitable receiver device for execution by a data processing device. The computer storage medium may be a machine-readable storage device, a machine-readable storage substrate, a random or serial access memory device, or a combination of one or more of them.

[0205] The processes and logic flows described in this specification can be performed by one or more programmable computers executing one or more computer programs to perform corresponding functions by operating on input data and generating output. The processes and logic flows can also be performed by special purpose logic circuits, such as FPGAs (field programmable gate arrays) or ASICs (application-specific integrated circuits), and the apparatus can also be implemented as special purpose logic circuits.

[0206] Computers suitable for executing computer programs include, for example, general and / or special microprocessors, or any other type of central processing unit. Typically, the central processing unit will receive instructions and data from a read-only memory and / or a random access memory. The basic components of a computer include a central processing unit for implementing or executing instructions and one or more memory devices for storing instructions and data. Typically, the computer will also include one or more large-capacity storage devices for storing data, such as magnetic disks, magneto-optical disks, or optical disks, or the computer will be operably coupled to this large-capacity storage device to receive data from it or to transmit data to it, or both. However, the computer does not necessarily have such a device. In addition, the computer can be embedded in another device, such as a mobile phone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a global positioning system (GPS) receiver, or a portable storage device such as a universal serial bus (USB) flash drive, to name a few.

[0207] Computer readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including, for example, semiconductor memory devices (e.g., EPROM, EEPROM and flash memory devices), magnetic disks (e.g., internal hard disks or removable disks), magneto-optical disks, and CD ROM and DVD-ROM disks. The processor and memory may be supplemented by, or incorporated in, special purpose logic circuitry.

[0208] Although this specification includes many specific implementation details, these should not be interpreted as limiting the scope of any invention or the scope of protection claimed, but are mainly used to describe the features of the specific embodiments of specific inventions. Certain features described in multiple embodiments in this specification may also be implemented in combination in a single embodiment. On the other hand, the various features described in a single embodiment may also be implemented separately in multiple embodiments or in any suitable sub-combination. In addition, although features may work in certain combinations as described above and even initially claim protection, one or more features from the claimed combination may be removed from the combination in some cases, and the claimed combination may point to a sub-combination or a variation of a sub-combination.

[0209] Similarly, although operations are depicted in a particular order in the accompanying drawings, this should not be understood as requiring that these operations be performed in the particular order shown or performed sequentially, or requiring that all illustrated operations be performed to achieve the desired results. In some cases, multitasking and parallel processing may be advantageous. In addition, the separation of various system modules and components in the above-described embodiments should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product, or packaged into multiple software products.

[0210] Thus, specific embodiments of the subject matter have been described. Other embodiments are within the scope of the appended claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the particular order or sequential order shown to achieve the desired results. In some implementations, multitasking and parallel processing may be advantageous.

[0211] The above are preferred embodiments of the present invention. It should be pointed out that, for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as within the scope of protection of the present invention.

Claims

1. A method for normalizing heterogeneous drawing data, characterized in that: include: Step S1: extracting unstructured heterogeneous drawing data based on the OEM model; Step S2, establishing adapters corresponding one-to-one to the extracted unstructured drawing heterogeneous data, forming an adapter library of data files, forming semi-structured data based on the OEM model, and obtaining a directed graph based on the OEM model; Step S3: The XML-based data middle layer effectively organizes and manages the semi-structured data of the directed graph based on the OEM model, forms structured integrated data, and unifies the external interface and usage.

2. The method for normalizing heterogeneous drawing data according to claim 1, characterized in that: In the step S1, the OEM model is a model in an extensible format.

3. The method for normalizing heterogeneous drawing data according to claim 2, characterized in that: In step S1, extracting unstructured heterogeneous drawing data includes one or more of the following: 1) Name of the drawing; 2) Drawing code; 3) Drawing scale; 4) Weight; 5) Owner information; 6) Parts list information; 7) Tile information; 8) Drawing address.

4. The method for normalizing heterogeneous drawing data according to claim 3, characterized in that: In the step S1, the extracting of unstructured heterogeneous drawing data further includes: proprietary extraction content; The proprietary extraction content includes one or more of the following: Marking information, key parameters, technical descriptions or technical requirements.

5. The method for normalizing heterogeneous drawing data according to claim 4, characterized in that: In the step S2, the directed graph is a hierarchical sub-graph based on a drawing.

6. The method for normalizing heterogeneous drawing data according to claim 5, characterized in that: In step S2, the first level of the directed graph is the drawing name; the second level is one or more of the drawing name, drawing code, drawing scale, weight, owner information, parts list information, block information or drawing address; the third level is the specific information content corresponding to the second level name.

7. The method for normalizing heterogeneous drawing data according to claim 6, characterized in that: The drawings are divided into Drawings from the conceptual design, technical design or construction design phase and are classified in the OEM model.

8. A drawing heterogeneous data normalization system, characterized in that: The system comprises: A first processing module is configured to extract unstructured drawing heterogeneous data based on the OEM model; The second processing module is configured to establish adapters corresponding to the extracted unstructured heterogeneous drawing data one by one, form an adapter library of data files, form semi-structured data based on the OEM model, and obtain a directed graph based on the OEM model; The third processing module is configured to effectively organize and manage the semi-structured data of the directed graph based on the OEM model based on the XML data middle layer, form structured integrated data, and unify the external interface and use.

9. An electronic device, characterized in that: The electronic device includes a memory and a processor, the memory stores a computer program, and when the processor executes the computer program, the steps in the method for normalizing heterogeneous drawing data described in any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps in the method for normalizing heterogeneous drawing data described in any one of claims 1 to 7 are implemented.

Images