Construction method and device of ontology model of knowledge graph and storage medium

Abstract

The embodiment of the invention discloses a construction method and device of an ontology model of a knowledge graph and a storage medium. The method comprises the following steps: determining first ontology classes of stages included in a product life cycle and a first association relationship between the first ontology classes; determining second ontology classes of business activities of the enterprise and a second association relationship between the second ontology classes; determining a third association relationship between the second ontology class and the first ontology class; determining third ontology classes of related information of the second ontology class and a fourth incidence relation between the third ontology classes; determining a fifth association relationship between the second ontology class and the third ontology class; determining a fourth ontology class of the object related to the third ontology class and a fifth ontology class of a key attribute category of the object; determining a sixth association relationship between the fourth ontology class and the fifth ontology class and a seventh association relationship between the third ontology class and the fourth ontology class; and constructing an ontology model. The business intention is taken as the center, and guidance is provided for knowledge graph and data integration.

Description

Method, device and storage medium for constructing ontology model of knowledge graph Technical Field

[0001] The present invention relates to the field of enterprise modeling technology, and in particular to a method, device, and storage medium for constructing an ontology model of a knowledge graph. Background Art

[0002] Knowledge graphs connect knowledge from different domains, data sources, and heterogeneous data formats without changing its original form. They enable industrial enterprises to unleash the potential of integrated knowledge. Currently, there are no ready-made cases to follow for designing enterprise knowledge graphs that can efficiently and effectively collect and organize all the information needed to effectively support enterprise management and operations. Enterprise modeling is the process of describing the enterprise accurately through generalization and abstraction, using relatively independent and general forms to facilitate reading, comprehension, analysis, and communication. Currently, many modeling methods have been proposed internationally, and a variety of enterprise models have been established. Among the more well-known are the IDEF method, the CIM-OSA method, the ARIS method, the GRAI / GIM method, the BAAN / DEM method, the PERA method, the DEM dynamic enterprise model construction method, the workflow modeling method, the object-oriented modeling method, and so on.

[0003] In the manufacturing domain, a typical manufacturing system can be described based on three topics: (1) products; (2) processes; and (3) resources. Published ontology models typically focus on these three topics. However, these three topics are far from sufficient to describe an enterprise.

[0004] Summary of the Invention

[0005] The embodiments of the present invention propose a method, device and storage medium for constructing an ontology model of a knowledge graph.

[0006] A method for constructing an ontology model of a knowledge graph, comprising:

[0007] Determining first ontology classes of stages included in a product life cycle and first association relationships between the first ontology classes;

[0008] Determining a second ontology class of business activities of the enterprise and a second association relationship between the second ontology classes;

[0009] Determining a third association relationship between the second ontology class and the first ontology class based on the stage of the product life cycle to which the business activity belongs;

[0010] Determining a third ontology class of related information of the second ontology class, and a fourth association relationship between the third ontology classes;

[0011] Determining a fifth association relationship between the second ontology class and the third ontology class based on an input-output relationship between the business activity and the relevant information;

[0012] Determining a fourth ontology class of objects related to the third ontology class, and a fifth ontology class of key attribute categories of the objects;

[0013] Determine a sixth association relationship between the fourth ontology class and the fifth ontology class and a seventh association relationship between the third ontology class and the fourth ontology class;

[0014] The ontology model is constructed based on the first ontology class, the second ontology class, the third ontology class, the fourth ontology class, the fifth ontology class, the first association relationship, the second association relationship, the third association relationship, the fourth association relationship, the fifth association relationship, the sixth association relationship and the seventh association relationship.

[0015] It can be seen that the embodiment of the present invention constructs an enterprise ontology model centered on business intent, which is no longer limited to modeling based on products, processes, and resources. Therefore, the model is more accurate.

[0016] In an exemplary embodiment, the business activities of the enterprise are derived from at least one of the following:

[0017] Domain knowledge related to product life cycle and value chain;

[0018] Domain knowledge related to the business activities between the enterprise and its business partners;

[0019] Domain knowledge related to the operational execution processes of the enterprise, from management to production and manufacturing.

[0020] Therefore, business activities are diverse, which improves the accuracy of the model.

[0021] In an exemplary embodiment, the business activities between the enterprise and its business partners include purchasing activities, sales activities, or transportation activities.

[0022] In an exemplary embodiment, determining the first ontology classes of the stages included in the product life cycle of an enterprise and the first association relationships between the first ontology classes include:

[0023] Determine the types of stages included in the product life cycle, the numerical attributes of the stage types, and the order of stages;

[0024] Creating the first ontology class based on the type of the stage, and creating the numerical attributes of the first ontology class based on the numerical attributes of the type of the stage;

[0025] Based on the sequence relationship between the stages, a first association relationship between the first ontology classes is created.

[0026] It can be seen that a novel ontology class is created based on the product life cycle, which facilitates the subsequent establishment of an enterprise ontology model.

[0027] In an exemplary embodiment, determining the second ontology class of the enterprise's business activity and the second association relationship between the second ontology class, and determining the third association relationship between the second ontology class and the first ontology class based on the stage of the product life cycle to which the business activity belongs, includes:

[0028] Determine the types of business activities, the numerical attributes of the types of business activities, the hierarchical relationships between the types of business activities, and the stage of the product life cycle to which the business activities belong;

[0029] Creating the second ontology class based on the type of the business activity, and creating the numerical attributes of the second ontology class based on the numerical attributes of the type of the business activity;

[0030] Creating a second association relationship between the second ontology classes based on the hierarchical relationship between the types of business activities;

[0031] Based on the stage of the product life cycle to which the business activity belongs, a third association relationship between the second ontology class and the first ontology class is determined.

[0032] Therefore, the association between the stages of the product life cycle and business activities is achieved, and the model accuracy is improved.

[0033] In an exemplary embodiment, the relevant information of the second ontology class includes input information and output information of the second ontology class;

[0034] The third ontology class for determining the relevant information of the second ontology class and the fourth association relationship between the third ontology classes include:

[0035] For each second ontology class, determine the types of input information and output information required by it, the numerical attributes of the types of input information and output information, and the hierarchical relationship between the input information and the output information;

[0036] Creating a third ontology class based on the types of the input information and the output information, and creating a numerical attribute of the third ontology class based on the numerical attribute of the types of the input information and the output information;

[0037] Based on the hierarchical relationship between the input information and the output information, a fourth association relationship is created between the third ontology classes.

[0038] It can be seen that a novel ontology class of information related to business activities is created, which improves the accuracy of the model.

[0039] In an exemplary embodiment, determining a fourth ontology class of an object related to the third ontology class and a fifth ontology class of a key attribute category of the object includes:

[0040] Determine the type of objects related to the third ontology class, the numerical attributes of the object type, and the key attribute categories of the object type;

[0041] Establishing a fourth ontology class based on the type of the object, and creating a numerical attribute of the fourth ontology class based on the numerical attribute of the type of the object;

[0042] The fifth ontology class is established based on the key attribute categories of the object type.

[0043] It can be seen that novel ontology classes of objects and key category types are created, which improves the accuracy of the model.

[0044] In an exemplary embodiment, the key attribute categories include:

[0045] Functional attributes of an object; capability type of an object; quality attributes of an object; specification attributes of an object.

[0046] A device for constructing an ontology model of a knowledge graph, comprising:

[0047] A first determining module is configured to determine first ontology classes of stages included in a product life cycle, and first association relationships between the first ontology classes;

[0048] a second determining module configured to determine a second ontology class of a business activity of an enterprise and a second association relationship between the second ontology classes;

[0049] a third determining module configured to determine a third association relationship between the second ontology class and the first ontology class based on the stage of the product life cycle to which the business activity belongs;

[0050] a fourth determining module configured to determine a third ontology class of related information of the second ontology class, and a fourth association relationship between the third ontology classes;

[0051] a fifth determining module configured to determine a fifth association relationship between the second ontology class and the third ontology class based on an input-output relationship between the business activity and the relevant information;

[0052] a sixth determining module configured to determine a fourth ontology class of objects related to the third ontology class, and a fifth ontology class of a key attribute category of the objects;

[0053] a seventh determining module, configured to determine a sixth association relationship between the fourth ontology class and the fifth ontology class and a seventh association relationship between the third ontology class and the fourth ontology class;

[0054] A construction module is configured to construct the ontology model based on the first ontology class, the second ontology class, the third ontology class, the fourth ontology class, the fifth ontology class, the first association relationship, the second association relationship, the third association relationship, the fourth association relationship, the fifth association relationship, the sixth association relationship and the seventh association relationship.

[0055] It can be seen that the embodiment of the present invention constructs an enterprise ontology model centered on business intent, which is no longer limited to modeling based on products, processes, and resources. Therefore, the model is more accurate.

[0056] In an exemplary embodiment, the business activities of the enterprise are derived from at least one of the following:

[0057] Domain knowledge related to product life cycle and value chain;

[0058] Domain knowledge related to the business activities between the enterprise and its business partners;

[0059] Domain knowledge related to the operational execution processes of the enterprise, from management to production and manufacturing.

[0060] Therefore, business activities are diverse, which improves the accuracy of the model.

[0061] In an exemplary embodiment, the business activities between the enterprise and its business partners include purchasing activities, sales activities, or transportation activities.

[0062] In an exemplary embodiment, the first determination module is configured to: determine the types of stages included in the product life cycle, the numerical attributes of the stage types, and the chronological relationship between the stages; create the first ontology class based on the types of the stages, and create the numerical attributes of the first ontology class based on the numerical attributes of the stage types; and create a first association relationship between the first ontology classes based on the chronological relationship between the stages.

[0063] It can be seen that a novel ontology class is created based on the product life cycle, which facilitates the subsequent establishment of an enterprise ontology model.

[0064] In an exemplary embodiment, the second determination module is configured to determine the type of business activity, the hierarchical relationship between the numerical attributes of the business activity type, and the stage of the product lifecycle to which the business activity belongs; create the second ontology class based on the type of business activity, and create the numerical attributes of the second ontology class based on the numerical attributes of the business activity type; create a second association relationship between the second ontology classes based on the hierarchical relationship between the business activity types; and determine a third association relationship between the second ontology class and the first ontology class based on the stage of the product lifecycle to which the business activity belongs. Thus, the product lifecycle stage and business activity are associated, improving model accuracy.

[0065] In an exemplary embodiment, the relevant information of the second ontology class includes input information and output information of the second ontology class;

[0066] The fourth determination module is configured to include: determining, for each second ontology class, the types of input information and output information required, the numerical attributes of the types of the input information and output information, and the hierarchical relationship between the input information and the output information; creating a third ontology class based on the types of the input information and the output information, and creating numerical attributes of the third ontology class based on the numerical attributes of the types of the input information and the output information; and creating a fourth association relationship between the third ontology classes based on the hierarchical relationship between the input information and the output information.

[0067] It can be seen that a novel ontology class of information related to business activities is created, which improves the accuracy of the model.

[0068] In an exemplary embodiment, the sixth determination module is configured to: determine the type of object related to the third ontology class, the numerical attributes of the object type, and the key attribute category of the object type; establish a fourth ontology class based on the type of the object, and create the numerical attributes of the fourth ontology class based on the numerical attributes of the object type; and establish the fifth ontology class based on the key attribute category of the object type.

[0069] It can be seen that novel ontology classes related to objects and key category types are created, which improves the model accuracy.

[0070] In an exemplary embodiment, the key attribute categories include:

[0071] Functional attributes of an object; capability type of an object; quality attributes of an object; specification attributes of an object.

[0072] A device for constructing an ontology model of a knowledge graph, comprising:

[0073] processor;

[0074] a memory for storing executable instructions of the processor;

[0075] The processor is used to read the executable instructions from the memory and execute the executable instructions to implement the method for constructing the ontology model of the knowledge graph as described in any one of the above items.

[0076] A computer-readable storage medium having computer instructions stored thereon, wherein the computer instructions, when executed by a processor, implement the method for constructing an ontology model of a knowledge graph as described in any of the above items.

[0077] A computer program product comprises a computer program, wherein when the computer program is executed by a processor, the method for constructing an ontology model of a knowledge graph as described in any one of the above items is implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0078] The preferred embodiments of the present invention will be described in detail below with reference to the accompanying drawings, so that those skilled in the art will understand the above and other features and advantages of the present invention more clearly. In the accompanying drawings:

[0079] FIG1 is an overall architecture diagram of an ontology model of an enterprise according to an embodiment of the present invention.

[0080] FIG2 is a flowchart of a method for constructing an ontology model of a knowledge graph according to an embodiment of the present invention.

[0081] FIG3 is a diagram showing an ontology model of a manufacturing enterprise according to an embodiment of the present invention.

[0082] FIG4 is an ontology architecture diagram of the PLM stage according to an embodiment of the present invention.

[0083] FIG5 is a diagram showing a hierarchical structure of business activities according to an embodiment of the present invention.

[0084] FIG6 is an ontology architecture diagram of a business activity according to an embodiment of the present invention.

[0085] FIG7 is a diagram showing an ontology model of business activities related to a business according to an embodiment of the present invention.

[0086] FIG8 is a diagram showing an ontology model of manufacturing operation management activities according to an embodiment of the present invention.

[0087] FIG9 is a diagram of an information ontology architecture according to an embodiment of the present invention.

[0088] FIG10 is a diagram showing an ontology model of business-related information according to an embodiment of the present invention.

[0089] FIG11 is a diagram showing an ontology model of manufacturing operation information according to an embodiment of the present invention.

[0090] FIG12 is a schematic diagram of information interaction between detailed production scheduling center activities according to an embodiment of the present invention.

[0091] FIG13 is a diagram showing an ontology model of a public object according to an embodiment of the present invention.

[0092] FIG. 14 is a schematic diagram of common objects and information interconnected via key attribute categories according to an embodiment of the present invention.

[0093] FIG15 is a diagram showing an ontology model of detailed resources according to an embodiment of the present invention.

[0094] FIG. 16 is a diagram showing an ontology model of a business partner according to an embodiment of the present invention.

[0095] FIG17 is a diagram showing an ontology model of key attribute categories according to an embodiment of the present invention.

[0096] FIG18 is a schematic diagram of a device for constructing an ontology model of a knowledge graph having a memory-processor architecture according to an embodiment of the present invention.

[0097] FIG19 is a schematic diagram of a device for constructing an ontology model of a knowledge graph according to an embodiment of the present invention.

[0098] The accompanying drawings are numerals as follows:

[0099]

[0100]

[0101]

[0102]

[0103]

[0104] DETAILED DESCRIPTION

[0105] In order to make the purpose, technical solutions and advantages of the present invention more clear, the present invention is further described in detail with reference to the following examples.

[0106] For the sake of brevity and intuitiveness in description, the solution of the present invention is explained below by describing several representative implementations. A large number of details in the implementations are only used to help understand the solution of the present invention. However, it is obvious that the technical solution of the present invention may not be limited to these details when implemented. In order to avoid unnecessarily obscuring the solution of the present invention, some implementations are not described in detail, but only a framework is given. Hereinafter, "including" means "including but not limited to", and "according to..." means "at least according to..., but not limited to only according to...". Due to the language habits of Chinese, when the number of a component is not specifically specified below, it means that the component can be one or more, or can be understood as at least one.

[0107] The applicant has discovered that there are currently no existing examples for designing an enterprise knowledge graph that can efficiently and effectively collect and organize all the information required to effectively support enterprise management and operations. In view of this, the embodiments of the present invention propose a method for constructing an enterprise ontology model centered on business intent, which can serve as a skeleton metamodel for the enterprise knowledge graph. The modeling method of the embodiments of the present invention can be implemented in various types of enterprises, such as manufacturing enterprises.

[0108] In the intelligent manufacturing standardization reference model, the enterprise is described in three dimensions: (1) layers, life cycle and value stream, and hierarchy levels. The layer axis consists of the asset layer, integration layer, communication layer, information layer, function layer, and business layer. The asset layer represents physical facilities, equipment, or products. The life cycle and value stream axis mainly includes the type and instance stages. The hierarchy axis includes products, field equipment, workstations, work centers, enterprises, and the connected world.

[0109] In this embodiment of the present invention, a method and architecture for constructing an enterprise ontology model are proposed, based on standardized reference models for intelligent manufacturing (e.g., RAMI 4.0). The core principles of the enterprise ontology model in this embodiment include: within an enterprise, business activities are the core content, and various information and resources serve to achieve business intent. Business or manufacturing activities are included in upper-level concept nodes, which organize all required information and objects and interrelate them.

[0110] To embody this core principle, the enterprise can be described as four interacting models: the product lifecycle model, the object model, the key category model, and the information model. In product lifecycle management, various activities exist. These activities require the exchange of various information to achieve business intent. Objects (e.g., resources) participate in these activities by providing and receiving information.

[0111] FIG1 is an overall architecture diagram of an ontology model of an enterprise according to an embodiment of the present invention.

[0112] In Figure 1, the product life cycle 10 includes five stages, namely product design 11, production planning 12, production engineering 13, production execution 14 and operation service 15.

[0113] Business activities 20 include business planning and logistics-related activities and manufacturing operations management activities 25. Business planning and logistics-related activities include: planning 21, resources 22, delivery 23 and returns 24.

[0114] Information 30 includes business planning and logistics information 311 and manufacturing operations management information 312. Planning and logistics information 311 includes procurement information 31, order processing information 32, and marketing and sales information 37, among others. Manufacturing operations management information 312 includes definition information 33, capability information 34, scheduling information 35, and performance information 36, among others.

[0115] Object 40 includes key attribute categories (aspects) 41, common objects 42, supplier levels 43, and customer levels 44. Key attribute categories (aspects) 41 include object capabilities 411, object specifications 412, object functions 413, and object quality 414. Common objects 42 include personnel 421, equipment 422, physical assets 423, materials 424, and process segments 425.

[0116] Activity 20 can occur at any stage of PLM10, so the relationship between activity 20 and PLM10 is: happens during; information 30 is exchanged between business activities 20, so the relationship between information 30 and business activities 20 is: exchanges among; object 40 provides or receives information 30, so the relationship between object 40 and information 3 is: offers or receives; the relationship between public object 42 and key attribute category 41 is: association.

[0117] FIG2 is a flowchart of a method for constructing an ontology model of a knowledge graph according to an embodiment of the present invention.

[0118] As shown in FIG2 , the method 100 for constructing an ontology model of a knowledge graph includes:

[0119] Step 101: Determine first ontology classes of stages included in a product life cycle and first association relationships between the first ontology classes.

[0120] Step 102: Determine the second ontology classes of the enterprise's business activities and the second association relationships between the second ontology classes.

[0121] Step 103: Based on the stage of the product life cycle to which the business activity belongs, determine the third association relationship between the second ontology class and the first ontology class.

[0122] Step 104: Determine the third ontology class of the relevant information of the second ontology class, and the fourth association relationship between the third ontology class.

[0123] Step 105: Based on the input-output relationship between the business activity and the relevant information, determine the fifth association relationship between the second ontology class and the third ontology class.

[0124] Step 106: Determine a fourth ontology class of objects related to the third ontology class, and a fifth ontology class of key attribute categories of the objects.

[0125] Step 107: Determine the sixth association relationship between the fourth ontology class and the fifth ontology class and the seventh association relationship between the third ontology class and the fourth ontology class.

[0126] Step 108: Construct an ontology model of the enterprise based on the first ontology class, the second ontology class, the third ontology class, the fourth ontology class, the fifth ontology class, the first association relationship, the second association relationship, the third association relationship, the fourth association relationship, the fifth association relationship, the sixth association relationship and the seventh association relationship.

[0127] The present invention can be implemented using ontology modeling tools (such as Protg). In an exemplary embodiment, the enterprise's ontology model can be used as a skeleton metamodel of the knowledge graph to create the enterprise's knowledge graph, especially the knowledge graph of a manufacturing enterprise with complex relationships.

[0128] In an exemplary embodiment, an enterprise's business activities are derived from at least one of the following: domain knowledge related to the product lifecycle and value chain; domain knowledge related to business activities between the enterprise and its business partners; and domain knowledge related to the enterprise's operational execution processes, from management to production and manufacturing. Preferably, the business activities between the enterprise and its business partners include procurement, sales, or transportation.

[0129] In an exemplary embodiment, determining the first ontology class of the stages included in the product life cycle of an enterprise and the first association relationship between the first ontology classes includes: determining the types of the stages included in the product life cycle, the numerical attributes of the stage types, and the precedence relationship between the stages; creating the first ontology class based on the type of the stage, creating the numerical attributes of the first ontology class based on the numerical attributes of the type of the stage; and creating the first association relationship between the first ontology classes based on the precedence relationship between the stages.

[0130] In an exemplary embodiment, determining a second ontology class of an enterprise's business activities and a second association relationship between the second ontology classes, and determining a third association relationship between the second ontology class and the first ontology class based on the stage of the product life cycle to which the business activities belong includes: determining the type of business activity, the numerical attributes of the type of business activity, the hierarchical relationship between the types of business activities, and the stage of the product life cycle to which the business activities belong; creating a second ontology class based on the type of business activity, creating the numerical attributes of the second ontology class based on the numerical attributes of the type of business activity; creating a second association relationship between the second ontology classes based on the hierarchical relationship between the types of business activities; and determining the third association relationship between the second ontology class and the first ontology class based on the stage of the product life cycle to which the business activities belong.

[0131] In an exemplary embodiment, the relevant information of the second ontology class includes the input information and output information of the second ontology class; determining the third ontology class of the relevant information of the second ontology class, and the fourth association relationship between the third ontology classes includes: for each second ontology class, determining the type of input information and output information required, the numerical attributes of the type of input information and output information, and the hierarchical relationship between the input information and the output information; creating a third ontology class based on the type of input information and output information, and creating the numerical attributes of the third ontology class based on the numerical attributes of the type of input information and output information; creating the fourth association relationship between the third ontology classes based on the hierarchical relationship between the input information and the output information.

[0132] In an exemplary embodiment, determining a fourth ontology class of objects related to the third ontology class and a fifth ontology class of key attribute categories of the objects includes: determining the type of objects related to the third ontology class, the numerical attributes of the object's type, and the key attribute categories of the object's type; establishing a fourth ontology class based on the type of the object, and creating numerical attributes of the fourth ontology class based on the numerical attributes of the object's type; and establishing a fifth ontology class based on the key attribute categories of the object's type.

[0133] In an exemplary embodiment, the key attribute categories include: object function; object capability; object quality; object specification; and object qualification.

[0134] Figure 3 is a diagram showing the ontology model of a manufacturing enterprise according to an embodiment of the present invention. A manufacturing enterprise is used as an example for illustration. As can be seen, the ontology model includes a product lifecycle (PLM) class, a business activity class (activity), a key attribute category class (aspect), an information class (Information) and an object class (Object). The PLM class further includes five subclasses, namely product design, production planning, production engineering, production execution and operation services. The business activity class includes two subclasses, namely: business planning and logistics activities (BusinessPlanningAndLogisticsActivity) and manufacturing operations management activities (ManufacturingOperationManagementActivity). The information class includes two subclasses, namely: manufacturing operations information (ManufacturingOperationInformation) and business planning and logistics information (BusinessPlanningAndLogisticsInformation). The object class includes two subclasses, namely: business partner (BusinessPartner) and common object (CommonObject). The key attribute category class includes five subclasses, namely Common Object Capability, Common Object Specification, Common Object Requirement, Common Object Response and Common Object Qualification, etc.

[0135] The above exemplary descriptions are typical examples of the ontology model of a manufacturing enterprise. Those skilled in the art will appreciate that such descriptions are merely exemplary and are not intended to limit the scope of protection of the embodiments of the present invention.

[0136] Figure 4 is a diagram of the PLM phase ontology architecture according to an embodiment of the present invention. As can be seen, under the Owl:thing class 70, there is a PLM phase (PLM_phase) class 71. PLM phase class 71 includes five subclasses: Product Design phase (ProductDesign_phase) class 72, Production Planning (ProductionPlanning_phase) phase class 73, Production Engineering (ProductionEngineering_phase) phase class 74, Production Execution (ProductionExecution_phase) phase class 75, and Operation AndService (OperationAndService_phase) phase class 76. Furthermore, based on the order of the product lifecycles to which these five subclasses correspond, these five subclasses are further associated with each other. For example: the subsequent stage of product design stage class 72 is production planning stage class 73; the previous stage of production planning stage class 73 is product design stage class 72; the subsequent stage of production planning stage class 73 is production engineering stage class 74; the previous stage of production engineering stage class 74 is production planning stage class 73; the subsequent stage of production engineering stage class 74 is production execution stage class 75, and the previous stage of production execution stage class 75 is production engineering stage class 74; the subsequent stage of production execution stage class 75 is operation service stage class 76; the previous stage of operation service stage class 76 is production execution stage class 75.

[0137] Figure 5 is a hierarchical architecture diagram of business activities according to an embodiment of the present invention. In Figure 5, business activities are layered according to standard IEC 622264-1. Block 60 represents Level 0, block 61 represents Level 1, block 62 represents Level 2, block 63 represents Level 3, and block 64 represents Level 4. Level 0 represents the actual production process. Level 1 is used to sense and operate the manufacturing process. Level 2 is used to monitor, direct, control, and automate the production process. Level 3 includes workflows for generating desired end products, maintaining records and optimizing the production process, dispatching production, and detailed production scheduling. Level 4 is used to establish basic production plans, material usage, transportation, shipping, determine inventory levels, and manage operations. Blocks 61 and 62 include batch control 53, continuous control 54, and discrete control 55. Block 63 includes manufacturing operations management 52. Block 64 includes business planning and logistics 51.

[0138] FIG6 is an ontology architecture diagram of business activities according to an embodiment of the present invention. It can be seen that the business activity (Activity) class 80 includes two subclasses, namely the business planning and logistics activity (Business PlanningAnd Logistics Activity) class 81 and the manufacturing operation management activity (Manufacturing Operation Management Activity) class 82. FIG7 is a display diagram of the ontology model of business activities related to business according to an embodiment of the present invention. In FIG7, the subclasses of business planning and logistics activities are exemplarily described. FIG8 is a display diagram of the ontology model of manufacturing operation management activities according to an embodiment of the present invention. In FIG8, the subclasses of manufacturing operation management activities are exemplarily described.

[0139] FIG9 is an ontology architecture diagram of information according to an embodiment of the present invention. It can be seen that the information class 90 includes two subclasses, namely the manufacturing operation information class 91 and the business planning and logistics information class 92. Manufacturing operation information is clearly defined in the standard IEC649 / 13 and will not be described in detail here. FIG10 is an ontology model display diagram of business-related information according to an embodiment of the present invention. FIG11 is an ontology model display diagram of manufacturing operation information according to an embodiment of the present invention. In FIG10 and FIG11, typical examples of the subclasses of manufacturing operation information and business planning and logistics information are respectively described as examples.

[0140] The following example illustrates how to define the information to be exchanged and how to organize specific activities within a business scope through information flows.

[0141] Figure 12 is a schematic diagram of the information exchange between activities in the detailed production schedule center according to an embodiment of the present invention. The ontology model illustrates the information exchange between detailed production scheduling 704, product definition management 706, and production resource management 708. Furthermore, production scheduling 703, work instructions 707, work capacity 710, and resource relationship network 709 are inputs to the detailed production scheduling activity 704, while work order scheduling 711 is output from the detailed production scheduling activity 704. A subclass of business planning and logistics activity 701 is production planning and scheduling 702. The relationship between production planning and scheduling 702 and production scheduling 703 is "generate information." Detailed production scheduling 704, work instructions 707, and production resource management 708 are subclasses of production operations management 705. The output of production resource management 708 includes resource relationship network 709 and work capacity 710. The output of product definition management 706 includes work instructions 707.

[0142] IEC 62264-2 defines five common object types: personnel; equipment; physical assets; materials; and process segments. The corresponding ontology class creation is shown in Figure 13. Figure 13 illustrates the ontology model for common objects according to an embodiment of the present invention. These object classes are connected to information classes through key attribute categories (Aspects). Objects participate in activities through information. For example, the operational capability information specified in the IEC 62264 standard is a collection of personnel capabilities, equipment capabilities, and so on. This capability information is associated with elements in the object model (personnel model, equipment model, etc.). Accordingly, this association relationship is created in the ontology model, as shown in Figure 14. Figure 14 is a schematic diagram of common objects and information interconnected through key attribute categories according to an embodiment of the present invention. The key attribute category concept is derived from the Aspect class defined in ISO 15926-14, which is used to describe the properties and characteristics of an object. Here, categories are used to link common objects and information. The ISO 15926-14 ontology has 33 OWL classes, of which three are the most basic: activity class, attribute category class (Aspect), and object class. The activity class represents the process in which the object participates; the category class includes the characteristics and attributes of the object; and the object class description includes the main and independent entities. Figure 17 is a diagram showing the ontology model of the key attribute category according to an embodiment of the present invention.

[0143] In Figure 14 , subcategories of key attribute category 500 include object capability 501. Subcategories of object capability 501 include personnel capability 502, equipment capability 503, physical asset capability 504, material capability 505, and process segment capability 506. Subcategories of object 514 include common objects 513. Subcategories of common objects 513 include resources 511 and process segments 512. Subcategories of resources 511 include personnel 507, equipment 508, physical assets 509, and materials 510. Subcategories of operational capability information 515 include personnel 507, equipment 508, physical assets 509, and materials 510. Furthermore, personnel 507 is associated with personnel capability 502; specifically, personnel 507 possesses the capabilities of personnel capability 502. Similarly, equipment 508 is associated with equipment capability 503, specifically, equipment 508 possesses the capability of equipment capability 503; physical asset 509 is associated with physical asset capability 504, specifically, physical asset 509 possesses the capability of physical asset capability 504; material 510 is associated with material capability 505, specifically, material 510 possesses the capability of material capability 505; and process section 512 is associated with process section capability 506, specifically, process section 512 possesses the capability of process section capability 506. Furthermore, operational capability information 515 is aggregated with personnel capability 502, equipment capability 503, physical asset capability 504, material capability 505, and process section capability 506.

[0144] Figure 15 illustrates a detailed resource ontology model according to an embodiment of the present invention. As shown in Figure 15 , for each public object class, a new ontology model can be created to extend and define its subclasses and related attributes. For example, for the resource class, a separate independent resource ontology model can be defined as follows: This describes the resource class in greater detail than the upper-level ontology model. To horizontally describe the interactions between a manufacturer and its business partners, the concept of a business partner is defined as follows: They will interact with the manufacturer through business-related information and activities.

[0145] FIG. 16 is a diagram showing an ontology model of a business partner according to an embodiment of the present invention.

[0146] Specifically, in the embodiment of the present invention, the following steps are performed to implement modeling:

[0147] (1) Determine the types of stages included in the product life cycle dimension, their numerical attributes, and the order of the stages. Create an ontology class for the product life cycle stage based on the type of the product life cycle stage, and create the numerical attributes of the ontology class based on the numerical attributes of the type. Based on the order of the stages in the product life cycle, create associations between the ontology classes of the product life cycle stage.

[0148] (2) Determine the type of business activity to be modeled, its numerical attributes, and the hierarchical relationships between the types of business activities. Determine the stage of the product life cycle in which the business activity is located. Create an ontology class for the business activity based on the type of business activity. Create numerical attributes for the ontology class of the business activity based on the numerical attributes of the business activity. Create relationships between the ontology classes of the business activity based on the hierarchy of the business activities. Create an association relationship between the ontology class of the business activity and the ontology class of the product life cycle stage based on the stage of the life cycle in which the business activity is located.

[0149] (3) For each business activity type, determine the required input / output information type, the numerical attributes of the information, and the hierarchical relationship between the information. Create an ontology class based on the information type, and create the numerical attributes of the information ontology class based on the numerical attributes of the information. Create relationships between the information ontology classes based on the hierarchical relationship between the information. Create an association relationship between the business activity ontology class and the information ontology class based on the input / output relationship between the business activity and the information.

[0150] (4) Determine the basic object types, basic attributes of the objects, and key attribute categories of each type of object involved in the information ontology class to be built. Establish the object ontology class based on the basic object type, and create the numerical attributes of the object ontology class based on the basic attributes of the object. Establish the key attribute ontology class based on the key attribute category, and create the association relationship between the object ontology class and the key attribute ontology class. Establish the association relationship between the information ontology class and the object ontology class involved in it.

[0151] The embodiments of the present invention use business activities as the core to organize the information flows and objects required, and construct an ontology model of the enterprise knowledge graph. This service-oriented modeling concept can improve the interoperability of cross-enterprise applications. In particular, the embodiments of the present invention build a business activity layer model from three dimensions based on the Industry 4.0 reference architecture system model, providing a reference template for data and information integration for enterprises to achieve comprehensive knowledge management and digital and intelligent application development with Industry 4.0 as the goal. These three dimensions include: (1) product life cycle and value chain; (2) horizontal business activities with business partners (procurement, sales, transportation, etc.); (3) vertical operations and execution from enterprise management to production and manufacturing.

[0152] The present invention also provides a device for constructing an ontology model of a knowledge graph with a processor-memory architecture. Figure 18 is a schematic diagram of a device for constructing an ontology model of a knowledge graph with a memory-processor architecture according to an embodiment of the present invention.

[0153] As shown in Figure 18, the construction device 800 includes a processor 801, a memory 802, and a computer program stored in the memory 802 and executable on the processor 801. When the computer program is executed by the processor 801, a method for constructing an ontology model of a knowledge graph as described above is implemented. Among them, the memory 802 can be specifically implemented as a variety of storage media such as an electrically erasable programmable read-only memory (EEPROM), a flash memory (Flash memory), and a programmable read-only memory (PROM). The processor 801 can be implemented as including one or more central processing units or one or more field programmable gate arrays, wherein the field programmable gate array integrates one or more central processing unit cores. Specifically, the central processing unit or the central processing unit core can be implemented as a CPU or an MCU or a DSP, and so on.

[0154] In summary, the embodiment of the present invention designs a framework for creating an enterprise ontology model. This framework is similar to a tree structure and contains main branches that describe the enterprise. When implemented in a specific enterprise, the tree needs to be customized, but only more branches and leaves need to be added to the tree. When building an enterprise knowledge graph, the embodiment of the present invention provides a clear logical guide for organizing enterprise data from various systems and departments. The architectural principles of the embodiment of the present invention include: within the enterprise, business activities are the core content, and various information and resources serve the realization of business intent. Specifically, it includes: (1) in terms of product life cycle management, there are various activities; (2) various information needs to be exchanged between these activities to realize business intent; (3) objects (various resources) participate in activities by providing and receiving information. The embodiment of the present invention provides the main branches that describe the enterprise. The embodiment of the present invention is also suitable for standardized design and is widely applicable to all walks of life.

[0155] Furthermore, embodiments of the present invention provide efficient data organization and management for intelligent manufacturing, embodied in business-intent-centric data organization. Well-organized domain models and their connections support both horizontal (supply chain, interactions with other business partners) and vertical (from the enterprise level, manufacturing operations level, to the field object level) connectivity, a prerequisite for intelligent manufacturing. Interconnected data provides the foundation for upper-level intelligent applications centered around business analytics, ensuring targeted data collection without the need to gather data from a variety of sources, and improving the efficiency and effectiveness of business activities.

[0156] FIG19 is a schematic diagram of a device for constructing an ontology model of a knowledge graph according to an embodiment of the present invention. As shown in FIG19 , the device 200 for constructing an ontology model of a knowledge graph includes:

[0157] The first determining module 201 is configured to determine first ontology classes of stages included in a product life cycle, and first association relationships between the first ontology classes;

[0158] The second determining module 202 is configured to determine a second ontology class of the business activities of the enterprise and a second association relationship between the second ontology classes;

[0159] A third determining module 203 is configured to determine a third association relationship between the second ontology class and the first ontology class based on the stage of the product life cycle to which the business activity belongs;

[0160] The fourth determining module 204 is configured to determine the third ontology class of the relevant information of the second ontology class, and a fourth association relationship between the third ontology classes;

[0161] A fifth determining module 205 is configured to determine a fifth association relationship between the second ontology class and the third ontology class based on the input-output relationship between the business activity and the relevant information;

[0162] a sixth determining module 206 configured to determine a fourth ontology class of objects related to the third ontology class, and a fifth ontology class of a key attribute category of the objects;

[0163] The seventh determining module 207 is configured to determine a sixth association relationship between the fourth ontology class and the fifth ontology class and a seventh association relationship between the third ontology class and the fourth ontology class;

[0164] The construction module 208 is configured to construct an ontology model of the enterprise based on the first ontology class, the second ontology class, the third ontology class, the fourth ontology class, the fifth ontology class, the first association relationship, the second association relationship, the third association relationship, the fourth association relationship, the fifth association relationship, the sixth association relationship and the seventh association relationship.

[0165] In an exemplary embodiment, the business activities of an enterprise are derived from at least one of the following: domain knowledge related to the product life cycle and value chain; domain knowledge related to business activities between the enterprise and its business partners; and domain knowledge related to the enterprise's operational execution process from management to production and manufacturing.

[0166] In an exemplary embodiment, the business activities between the enterprise and its business partners include purchasing activities, sales activities, or transportation activities.

[0167] In an exemplary embodiment, the first determination module 201 is configured to: determine the types of stages included in the product life cycle, the numerical attributes of the stage types, and the chronological relationship between the stages; create a first ontology class based on the types of the stages, and create numerical attributes of the first ontology class based on the numerical attributes of the stage types; and create a first association relationship between the first ontology classes based on the chronological relationship between the stages.

[0168] In an exemplary embodiment, the second determination module 202 is configured to determine the type of business activity, the hierarchical relationship between the numerical attributes of the type of business activity, and the stage of the product life cycle to which the business activity belongs; create a second ontology class based on the type of business activity, and create the numerical attributes of the second ontology class based on the numerical attributes of the type of business activity; create a second association relationship between the second ontology classes based on the hierarchical relationship between the types of business activities; and determine a third association relationship between the second ontology class and the first ontology class based on the stage of the product life cycle to which the business activity belongs.

[0169] In an exemplary embodiment, the relevant information of the second ontology class includes input information and output information of the second ontology class;

[0170] The fourth determination module 204 is configured to include: determining, for each second ontology class, the types of input information and output information required, the numerical attributes of the types of the input information and output information, and the hierarchical relationship between the input information and the output information; creating a third ontology class based on the types of the input information and the output information, and creating numerical attributes of the third ontology class based on the numerical attributes of the types of the input information and the output information; and creating a fourth association relationship between the third ontology classes based on the hierarchical relationship between the input information and the output information.

[0171] In an exemplary embodiment, the sixth determination module 206 is configured to: determine the type of object related to the third ontology class, the numerical attributes of the object type, and the key attribute category of the object type; establish a fourth ontology class based on the type of the object, and create the numerical attributes of the fourth ontology class based on the numerical attributes of the object type; establish a fifth ontology class based on the key attribute category of the object type.

[0172] In an exemplary embodiment, the key attribute categories include: object function; object capability; object quality; object specification; and object qualification.

[0173] It should be noted that not all steps and modules in the above processes and structure diagrams are required, and certain steps or modules can be omitted based on actual needs. The execution order of the steps is not fixed and can be adjusted as needed. The division of the modules is merely for the convenience of describing the functional division adopted. In actual implementation, a module can be implemented by multiple modules, and the functions of multiple modules can be implemented by the same module. These modules can be located in the same device or in different devices.

[0174] The hardware modules in each embodiment can be implemented mechanically or electronically. For example, a hardware module may include a specially designed permanent circuit or logic device (such as a dedicated processor, such as an FPGA or ASIC) for performing a specific operation. The hardware module may also include a programmable logic device or circuit (such as a general-purpose processor or other programmable processor) temporarily configured by software to perform a specific operation. As for whether to implement the hardware module mechanically, or using a dedicated permanent circuit, or using a temporarily configured circuit (such as configured by software), it can be decided based on cost and time considerations.

[0175] The above description is only a preferred embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included in the scope of protection of the present invention.

Claims

1. A method (100) for constructing an ontology model of a knowledge graph, characterized in that: include: Determining first ontology classes of stages included in a product life cycle and first association relationships between the first ontology classes (101); Determining a second ontology class of the enterprise's business activities and a second association relationship between the second ontology classes (102); Determining a third association relationship between the second ontology class and the first ontology class based on the stage of the product life cycle to which the business activity belongs (103); Determining a third ontology class related to the second ontology class, and a fourth association relationship between the third ontology classes (104); Determining a fifth association relationship between the second ontology class and the third ontology class based on an input-output relationship between the business activity and the relevant information (105); Determining a fourth ontology class of objects related to the third ontology class, and a fifth ontology class (106) of key attribute categories of the objects; Determine a sixth association relationship between the fourth ontology class and the fifth ontology class and a seventh association relationship between the third ontology class and the fourth ontology class (107); The ontology model (108) is constructed based on the first ontology class, the second ontology class, the third ontology class, the fourth ontology class, the fifth ontology class, the first association relationship, the second association relationship, the third association relationship, the fourth association relationship, the fifth association relationship, the sixth association relationship and the seventh association relationship.

2. The method (100) for constructing an ontology model of a knowledge graph according to claim 1, characterized in that: The business activities of the enterprise are derived from at least one of the following: Domain knowledge related to product life cycle and value chain; Domain knowledge related to the business activities between the enterprise and its business partners; Domain knowledge related to the operational execution processes of the enterprise, from management to production and manufacturing.

3. The method (100) for constructing an ontology model of a knowledge graph according to claim 2, characterized in that: Business activities between the enterprise and its business partners include purchasing activities, sales activities or transportation activities.

4. The method (100) for constructing an ontology model of a knowledge graph according to claim 1, characterized in that: The first ontology class for determining the stages included in the product life cycle of an enterprise and the first association relationship (101) between the first ontology classes include: Determine the types of stages included in the product life cycle, the numerical attributes of the stage types, and the order of stages; Creating the first ontology class based on the type of the stage, and creating the numerical attributes of the first ontology class based on the numerical attributes of the type of the stage; Based on the sequence relationship between the stages, a first association relationship between the first ontology classes is created.

5. The method (100) for constructing an ontology model of a knowledge graph according to claim 1, characterized in that: The determining of the second ontology class of the enterprise's business activities and the second association relationship between the second ontology class, and determining the third association relationship between the second ontology class and the first ontology class based on the stage of the product life cycle to which the business activities belong, includes: Determine the types of business activities, the numerical attributes of the types of business activities, the hierarchical relationships between the types of business activities, and the stage of the product life cycle to which the business activities belong; Creating the second ontology class based on the type of the business activity, and creating the numerical attributes of the second ontology class based on the numerical attributes of the type of the business activity; Creating a second association relationship between the second ontology classes based on the hierarchical relationship between the types of business activities; Based on the stage of the product life cycle to which the business activity belongs, a third association relationship between the second ontology class and the first ontology class is determined.

6. The method (100) for constructing an ontology model of a knowledge graph according to claim 1, characterized in that: The relevant information of the second ontology class includes input information and output information of the second ontology class; The third ontology class for determining the relevant information of the second ontology class and the fourth association relationship (104) between the third ontology classes include: For each second ontology class, determine the types of input information and output information required by it, the numerical attributes of the types of input information and output information, and the hierarchical relationship between the input information and the output information; Creating a third ontology class based on the types of the input information and the output information, and creating a numerical attribute of the third ontology class based on the numerical attribute of the types of the input information and the output information; Based on the hierarchical relationship between the input information and the output information, a fourth association relationship is created between the third ontology classes.

7. The method (100) for constructing an ontology model of a knowledge graph according to claim 1, characterized in that: The fourth ontology class of the object related to the third ontology class and the fifth ontology class (106) of the key attribute category of the object include: Determine the type of objects related to the third ontology class, the numerical attributes of the object type, and the key attribute categories of the object type; Establishing a fourth ontology class based on the type of the object, and creating a numerical attribute of the fourth ontology class based on the numerical attribute of the type of the object; The fifth ontology class is established based on the key attribute categories of the object type.

8. The method (100) for constructing an ontology model of a knowledge graph according to claim 1, characterized in that: The key attribute categories include: The function of an object; the capability of an object; the quality of an object; the specification of an object; the qualification of an object.

9. A device (200) for constructing an ontology model of a knowledge graph, characterized in that: include: A first determining module (201) is configured to determine first ontology classes of stages included in a product life cycle, and first association relationships between the first ontology classes; A second determining module (202) is configured to determine a second ontology class of a business activity of an enterprise and a second association relationship between the second ontology classes; A third determining module (203) is configured to determine a third association relationship between the second ontology class and the first ontology class based on the stage of the product life cycle to which the business activity belongs; a fourth determining module (204), configured to determine a third ontology class of relevant information of the second ontology class, and a fourth association relationship between the third ontology classes; A fifth determining module (205) is configured to determine a fifth association relationship between the second ontology class and the third ontology class based on an input-output relationship between the business activity and the relevant information; a sixth determining module (206), configured to determine a fourth ontology class of an object related to the third ontology class, and a fifth ontology class of a key attribute category of the object; a seventh determining module (207), configured to determine a sixth association relationship between the fourth ontology class and the fifth ontology class and a seventh association relationship between the third ontology class and the fourth ontology class; A construction module (208) is configured to construct the ontology model based on the first ontology class, the second ontology class, the third ontology class, the fourth ontology class, the fifth ontology class, the first association relationship, the second association relationship, the third association relationship, the fourth association relationship, the fifth association relationship, the sixth association relationship and the seventh association relationship.

10. The device (200) for constructing an ontology model of a knowledge graph according to claim 9, characterized in that: The business activities of the enterprise are derived from at least one of the following: Domain knowledge related to product life cycle and value chain; Domain knowledge related to the business activities between the enterprise and its business partners; Domain knowledge related to the operational execution processes of the enterprise, from management to production and manufacturing.

11. The device (200) for constructing an ontology model of a knowledge graph according to claim 10, characterized in that: Business activities between the enterprise and its business partners include purchasing activities, sales activities or transportation activities.

12. The device (200) for constructing an ontology model of a knowledge graph according to claim 9, characterized in that: The first determination module (201) is configured to: determine the types of stages included in the product life cycle, the numerical attributes of the stage types, and the order relationship between the stages; create the first ontology class based on the types of the stages, and create the numerical attributes of the first ontology class based on the numerical attributes of the stage types; Based on the sequence relationship between the stages, a first association relationship between the first ontology classes is created.

13. The device (200) for constructing an ontology model of a knowledge graph according to claim 9, characterized in that: The second determination module (202) is configured to determine the type of business activity, the hierarchical relationship between the numerical attributes of the type of business activity, and the stage of the product life cycle to which the business activity belongs; create the second ontology class based on the type of business activity, create the numerical attributes of the second ontology class based on the numerical attributes of the type of business activity; create a second association relationship between the second ontology classes based on the hierarchical relationship between the types of business activities; and determine a third association relationship between the second ontology class and the first ontology class based on the stage of the product life cycle to which the business activity belongs.

14. The device (200) for constructing an ontology model of a knowledge graph according to claim 9, characterized in that: The relevant information of the second ontology class includes input information and output information of the second ontology class; The fourth determination module (204) is configured to include: determining, for each second ontology class, the types of input information and output information required by the class, the numerical attributes of the types of the input information and output information, and the hierarchical relationship between the input information and the output information; creating a third ontology class based on the types of the input information and the output information, and creating numerical attributes of the third ontology class based on the numerical attributes of the types of the input information and the output information; and creating a fourth association relationship between the third ontology classes based on the hierarchical relationship between the input information and the output information.

15. The device (200) for constructing an ontology model of a knowledge graph according to claim 9, characterized in that: The sixth determination module (206) is configured to: determine the type of object related to the third ontology class, the numerical attributes of the object type and the key attribute category of the object type; establish a fourth ontology class based on the type of the object, and create the numerical attributes of the fourth ontology class based on the numerical attributes of the object type; and establish the fifth ontology class based on the key attribute category of the object type.

16. The device (200) for constructing an ontology model of a knowledge graph according to claim 9, characterized in that: The key attribute categories include: The function of an object; the capability of an object; the quality of an object; the specification of an object; the qualification of an object.

17. A device (800) for constructing an ontology model of a knowledge graph, characterized in that: include: Processor (801); a memory (802) for storing executable instructions of the processor (801); The processor (801) is used to read the executable instructions from the memory (802) and execute the executable instructions to implement the method (100) for constructing an ontology model of a knowledge graph according to any one of claims 1 to 8.

18. A computer-readable storage medium having computer instructions stored thereon, characterized in that: When the computer instructions are executed by a processor, the method (100) for constructing an ontology model of a knowledge graph according to any one of claims 1 to 8 is implemented.

19. A computer program product, characterized in that It includes a computer program, which, when executed by a processor, implements the method (100) for constructing an ontology model of a knowledge graph according to any one of claims 1 to 8.

Images