Ontology model construction method and system oriented to manufacturing industry industrial software resource sharing
By building an ontological model of industrial software resources for manufacturing, the problem of inconsistent sharing standards in industrial software resource sharing is solved, unified description and efficient sharing of resources are realized, and digital construction of small and medium-sized enterprises and the development of industrial clusters is promoted.
Patent Information
- Application Number
- CN202411138203.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-19
- Publication Date
- 2024-11-29
AI Technical Summary
The lack of a unified knowledge organization system for industrial software resource sharing in manufacturing has led to low efficiency of resource sharing and inconsistent sharing standards, which hinders the digitalization and high-quality development of regional industrial clusters.
Build a manufacturing industry ontology model, establish a unified industrial software resource ontology model by determining the field and scope, dividing structural levels, describing data attributes, and defining data content and transmission direction.
It has realized a unified description model of industrial software resources, broken the problem of inconsistent sharing standards and difficulty in sharing, promoted the sharing of industrial software resources, and promoted the digital construction of small and medium-sized enterprises and the digital and high-quality development of industrial clusters.
Smart Images

Figure CN119048006A_ABST
Abstract
Description
Technical Field
[0001] The present invention belongs to the technical field of ontology model design and construction, and relates to an ontology model construction method and system for sharing industrial software resources in manufacturing industry. Background Art
[0002] As a pillar industry of the national economy, manufacturing is an important force in promoting the development of social productivity and scientific and technological progress. As the "brain" of modern manufacturing, industrial software is the result of the softwareization of industrial technology, the core content of intelligent manufacturing and industrial Internet, an important support for the deep integration of industrialization and informatization, and an important means to promote my country's industrialization process. It deeply integrates advanced information technology, giving birth to new production methods such as cloud manufacturing, network collaboration, and service-oriented manufacturing, and effectively promotes the implementation of intelligent manufacturing strategies and industrial upgrading, becoming a key factor in building future smart factories and shaping the core competitiveness of the manufacturing industry. However, the lack of industrial software resource sharing and the lack of unified sharing standards in the digital construction of small and medium-sized enterprises have hindered the digitalization and high-quality development of regional industrial clusters. The reason is that the field of industrial software lacks a unified knowledge organization system, and it is impossible to systematically describe and associate software information.
[0003] The concept of ontology originates from the field of philosophy. In philosophy, it is defined as "a systematic description of objective things in the world, that is, ontology", which is a philosophical problem that studies the essence of existence. Since the 1990s, the concept of ontology has been introduced into fields such as artificial intelligence by foreign scholars and has gradually become a research focus. In recent years, it has also been realized and applied in fields such as biology, architecture, agriculture, and medicine. Wang Yiru combined architectural characteristics to define the concept class and attributes of architectural knowledge ontology in the field of intangible cultural heritage; Zhang Dandan et al. constructed a trait regulation gene ontology model framework to solve the problems of low efficiency in cross-species disciplinary knowledge acquisition and difficulty in discovering excellent multi-effect genes in crop breeding knowledge services; Li Xiaoying et al. used the protégé tool to preliminarily construct a respiratory tumor ontology. Although ontology has been widely used in multiple disciplines and deeply penetrated into the core of various fields, there is no specially constructed ontology model in the field of industrial software resources, resulting in the lack of a unified and detailed description framework in this field, which hinders the improvement of industrial software resource sharing efficiency. Summary of the invention
[0004] The purpose of the present invention is to solve the existing problems in the prior art, such as lack of industrial software resource sharing and inconsistent sharing specifications, which hinder the digitalization and high-quality development of regional industrial clusters, and to provide an ontology model construction method and system for industrial software resource sharing in the manufacturing industry.
[0005] In order to achieve the above object, the present invention adopts the following technical solutions:
[0006] A method for constructing an ontology model for industrial software resource sharing in manufacturing industry comprises the following steps:
[0007] Determine the fields and scopes involved in the industrial software resource ontology;
[0008] Based on the determined domain and scope, the structural level of industrial software resource ontology is divided;
[0009] Describe the data attributes of the industrial software resource ontology;
[0010] Define the data content and direction transferred between industrial software resource ontology classes;
[0011] An industrial software resource ontology model is constructed based on structural hierarchy, data attributes, data content and transmission direction.
[0012] A further improvement of the present invention is:
[0013] The fields and scopes involved in the industrial software resource ontology include:
[0014] Industrial software for business management, R&D design, manufacturing, operation and maintenance services, and AI empowerment.
[0015] The division of the structural hierarchy of the industrial software resource ontology comprises the following steps:
[0016] The industrial software ontology hierarchy is divided into five first-level subcategories:
[0017] Business management, R&D and design, manufacturing, operation and maintenance services, and AI empowerment;
[0018] The second-level sub-categories are divided based on the first-level sub-categories:
[0019] The secondary subcategories of the business management category include: enterprise resource management, financial management, human resource management, asset management, marketing management, supply chain management, office collaboration, quality inspection and traceability, instrument equipment management, supplier management, equipment visualization and predictive maintenance, and knowledge management;
[0020] The secondary subcategories of the R&D and design category include: computer-aided design, computer-aided manufacturing, computer-aided engineering, computer-aided process planning, electronic design automation, process simulation software, product life cycle management, 3D virtual simulation system, molecular design software, first principle calculation software, economic evaluation software and product digital design;
[0021] The secondary subcategories of the manufacturing category include: advanced planning systems, manufacturing execution systems, manufacturing operations management, warehouse management systems, scheduling optimization systems, energy efficiency management systems, real-time optimization systems, operator training simulation systems, advanced control systems, distributed control systems, programmable control systems, safety instrument systems, safety and risk management, data acquisition and monitoring systems, real-time database systems, product data management, quality management systems, decision support systems, and carbon emission monitoring and optimization;
[0022] The secondary subcategories of the operation and maintenance service category include: asset performance management, maintenance and repair operation management, and fault prediction and health management
[0023] The secondary subcategories of the AI empowerment category include:
[0024] Industrial intelligence generation, industrial large model platform, intelligent big data analysis, industrial robot control, materials
[0025] The data attributes describing the industrial software resource ontology include:
[0026] Basic attributes, functional attributes, state attributes and transaction attributes.
[0027] The basic properties include:
[0028] Software name, version information, release date, hardware requirements, software requirements, official website, software description and vendor information.
[0029] The functional attributes include:
[0030] Business segment, compatibility, software type (third-party applications, AI applications, web applications, mobile applications), access rights, scalability, integration capabilities, interface type (graphical user interface, web interface, physical controller interface, command line interface), degree of customization;
[0031] The state attributes include:
[0032] Not online, online, or offline;
[0033] The transaction attributes include:
[0034] Service fees, payment methods, transaction records, transaction types, delivery methods and user agreements;
[0035] The data content transmitted between the industrial software resource ontology classes includes:
[0036] Basic process, actual process data, approval process, cost, customer data, design model, design quality, equipment status parameters, inventory, working time data, material consumption, material data, material distribution plan, material requirement plan, bill of materials, organizational data, outbound requisition, material list, personnel data, process model, output, production plan, production quality, supplier quality, business document data, process route and work order.
[0037] The transmission direction includes:
[0038] The transfer direction of the basic process is: from the PLM system to the MES system;
[0039] The actual process data is transmitted from the MES system to the PLM system.
[0040] The transmission direction of the approval process is: from the OA system to the ERP system;
[0041] The cost transfer direction is: from the ERP system to the PLM system;
[0042] The direction of transmission of the customer data is: from the CRM system to the SCM system;
[0043] The transmission direction of the design model is: from the CAPP system to the PLM system;
[0044] The transmission direction of the design quality is: from the PLM system to the QMS system;
[0045] The transmission direction of the equipment status parameters is: from the SCADA system to the MES system;
[0046] The transfer direction of the inventory is: from the WMS system to the MES system or ERP system;
[0047] The transmission direction of the working time data is: from the MES system to the HRM system;
[0048] The transmission direction of the material consumption is: from the MES system to the ERP system;
[0049] The material data transmission direction is: from the ERP system to the MES system or WMS system;
[0050] The material distribution plan is transmitted from the MES system to the WMS system.
[0051] The transmission direction of the material requirement plan is: from the ERP system to the SCM system;
[0052] The transfer direction of the bill of materials is: from the PLM system to the MES system;
[0053] The transmission direction of the organizational data is: from the HRM system to the ERP system;
[0054] The delivery direction of the delivery application form is: from the MES system to the WMS system;
[0055] The material list is transferred from the PLM system to the ERP system.
[0056] The transfer direction of the personnel data is: from the HRM system to the ERP system;
[0057] The transmission direction of the process model is: from the PLM system to the CAPP system;
[0058] The transmission direction of the output is: from the MES system to the ERP system;
[0059] The transmission direction of the production plan is: from the ERP system to the MES system;
[0060] The transmission direction of the production quality is: from the MES system to the QMS system;
[0061] The transfer direction of supplier quality is: from SCM system to QMS system;
[0062] The transmission direction of the business document data is: from the ERP system to the OA system;
[0063] The transmission direction of the process route is: from the PLM system to the ERP system;
[0064] The transmission direction of the work order is: from the MES system to the SCADA system.
[0065] An ontology model construction system for industrial software resource sharing in manufacturing industry, including:
[0066] The scope determination module is used to determine the fields and scopes involved in the industrial software resource ontology;
[0067] The hierarchical division module is used to divide the structural hierarchy of the industrial software resource ontology based on the determined domain and scope;
[0068] The attribute determination module is used to describe the data attributes of the industrial software resource ontology;
[0069] The data content and transmission direction determination module is used to define the data content and transmission direction transmitted between industrial software resource ontology classes;
[0070] The model building module is used to build an industrial software resource ontology model based on structural hierarchy, data attributes, data content and transmission direction.
[0071] A terminal device comprises a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of any method described in the present invention when executing the computer program.
[0072] A computer-readable storage medium stores a computer program, wherein the computer program, when executed by a processor, implements the steps of any method described in the present invention.
[0073] Compared with the prior art, the present invention has the following beneficial effects:
[0074] The present invention discloses a method for constructing an ontology model for sharing industrial software resources in the manufacturing industry, including the division of the industrial software resource hierarchy, the determination of the software attribute description dimension and the data transmission direction, and then constructing the ontology model on this basis, unifying the industrial software resource information description models of software providers, platform operators and software users in the sharing process, breaking the difficult problems of inconsistent industrial software resource sharing standards and difficult sharing, and being able to promote the sharing of industrial software resources and the digital construction of small and medium-sized enterprises with the support of the industrial software sharing platform, and making up for the lack of an industrial software resource ontology model, providing a unified description model of industrial software resource information for software providers, users and platform operators involved in the industrial software resource sharing process. BRIEF DESCRIPTION OF THE DRAWINGS
[0075] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for use in the embodiments are briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present invention and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without creative work.
[0076] Figure 1 is a flow chart of the method of the present invention;
[0077] Figure 2 The hierarchical division diagram of the industrial software resource ontology structure of the present invention;
[0078] Figure 3 It is the hierarchical structure information and description diagram of the industrial software resource ontology class of the present invention;
[0079] Figure 4 It is the data attribute information and description diagram of the industrial software resource ontology of the present invention;
[0080] Figure 5 It is a schematic diagram describing the data content and transmission direction of the industrial software resource ontology of the present invention. DETAILED DESCRIPTION
[0081] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Generally, the components of the embodiments of the present invention described and shown in the drawings here can be arranged and designed in various different configurations.
[0082] Therefore, the following detailed description of the embodiments of the present invention provided in the accompanying drawings is not intended to limit the scope of the invention claimed for protection, but merely represents selected embodiments of the present invention. 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.
[0083] It should be noted that similar reference numerals and letters denote similar items in the following drawings, and therefore, once an item is defined in one drawing, further definition and explanation thereof is not required in subsequent drawings.
[0084] In the description of the embodiments of the present invention, it should be noted that if the terms "upper", "lower", "horizontal", "inner", etc. indicate an orientation or positional relationship based on the orientation or positional relationship shown in the drawings, or the orientation or positional relationship in which the product of the invention is usually placed when in use, it is only for the convenience of describing the present invention and simplifying the description, and does not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation on the present invention. In addition, the terms "first", "second", etc. are only used to distinguish the description, and cannot be understood as indicating or implying relative importance.
[0085] In addition, if the term "horizontal" appears, it does not mean that the component must be absolutely horizontal, but can be slightly tilted. For example, "horizontal" only means that its direction is more horizontal than "vertical", which does not mean that the structure must be completely horizontal, but can be slightly tilted.
[0086] In the description of the embodiments of the present invention, it is also necessary to explain that, unless otherwise clearly specified and limited, the terms "set", "install", "connect", and "connect" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be indirectly connected through an intermediate medium, or it can be the internal connection of two components. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.
[0087] The present invention is further described in detail below in conjunction with the accompanying drawings:
[0088] See also Figure 1 The embodiment of the present invention discloses a method for constructing an ontology model for industrial software resource sharing in manufacturing industry, comprising the following steps:
[0089] Step 1: Determine the fields and scope of the industrial software resource ontology.
[0090] Specifically, the fields and scopes involved in the industrial software resource ontology are determined as follows:
[0091] Industrial software covering business management, R&D design, production and manufacturing, operation and maintenance services, and AI empowerment for the entire life cycle of manufacturing products.
[0092] Among them, the application groups of the industrial software resource ontology are the software providers, software users and sharing platform operators involved in the software sharing process. The purpose of building the industrial software resource ontology is to provide a unified industrial software description framework for software providers, software users and sharing platform operators to promote the implementation of software sharing.
[0093] It should be noted that the above-mentioned R&D design, production and manufacturing, operation and maintenance services, AI-enabled industrial software, and their corresponding subcategories are all defined based on scientific and technological literature, reports, knowledge bases and other resources related to the field of industrial software.
[0094] Step 2: Based on the determined domain and scope, clarify the structural hierarchy of the industrial software resource ontology.
[0095] like Figure 2 As shown, the industrial software resource ontology level is divided into five first-level subcategories, including business management, R&D and design, production and manufacturing, operation and maintenance services, and AI empowerment;
[0096] Furthermore, based on the first-level sub-categories, the second-level sub-categories are further divided:
[0097] Specifically, the secondary subcategories of business management include:
[0098] Enterprise resource management (ERP), financial management (FM), human resource management (HRM), asset management (EAM), marketing management (CRM), supply chain management (SCM), office collaboration (OA), quality inspection and traceability (QMT), instrument equipment management (AMS), supplier management (SRM), equipment visualization and predictive maintenance (EVPM), knowledge management (KM);
[0099] The secondary subcategories of R&D and design include:
[0100] Computer-aided design (CAD), computer-aided manufacturing (CAM), computer-aided engineering (CAE), computer-aided process planning (CAPP), electronic design automation (EDA), process simulation software (PSS), product lifecycle management (PLM), 3D virtual simulation system (VSS), molecular design software (MDS), first principle calculation software (FPC), economic evaluation software (EES), product digital design (PDD);
[0101] Secondary subcategories of the manufacturing category include:
[0102] Advanced Planning System (APS), Manufacturing Execution System (MES), Manufacturing Operation Management (MOM), Warehouse Management System (WMS), Scheduling Optimization System (SOS), Energy Efficiency Management System (EMS), Real-Time Optimization System (RTO), Operator Training Simulation System (OTS), Advanced Control System (APC), Distributed Control System (DCS), Programmable Control System (PLC), Safety Instrument System (SIS), Safety and Risk Management (SARM), Supervisory Control and Data Acquisition System (SCADA), Real-Time Database System (RTDB), Product Data Management (PDM), Quality Management System (QMS), Decision Support System (DMS), Carbon Emission Monitoring and Optimization (CMO);
[0103] The second-level subcategories of operation and maintenance services include:
[0104] Asset performance management (APM), maintenance and repair operations (MRO), and failure prediction and health management (PHM);
[0105] Secondary subcategories of AI empowerment include:
[0106] Industrial Intelligence Generation (IAIC), Industrial Big Model Platform (IBM), Intelligent Big Data Analysis (IBA), Industrial Robot Control (IRC), Material Genome Design (MGD), Knowledge Representation and Reasoning (KRI).
[0107] Step 3: Describe the data attributes of the industrial software resource ontology.
[0108] The data attributes of the industrial software resource ontology refer to the data characteristics or parameters possessed by the ontology. Data attributes include basic attributes, functional attributes, state attributes, and transaction attributes. The specific attribute information and its meaning are shown in the following table.
[0109]
[0110]
[0111] Step 4: Define the data content and direction transmitted between industrial software resource ontology classes.
[0112] The data content and its transfer direction describe the relationship between one class and another class. The specific data content and data transfer direction are shown in the following table:
[0113]
[0114]
[0115] Step 5: Construct an industrial software resource ontology model based on the determined structural hierarchy, data attributes, data content and its transmission direction.
[0116] For example, protégé can be used to construct an industrial software resource ontology model. The specific process is as follows:
[0117] Step 5.1: Create the ontology class.
[0118] Create the first-level subclasses and their corresponding second-level subclasses in the hierarchical structure of the industrial software ontology. Classes at the same structural level are in a parallel relationship, and each class and its corresponding subclass are in a containment relationship, such as Figure 3 shown.
[0119] Step 5.2: Create data attributes of the industrial software ontology, such as Figure 4 shown.
[0120] Step 5.3: Create the data content and transmission direction of the industrial software ontology, such as Figure 5 As shown, Domains represents the data output system and Ranges represents the data input system.
[0121] Step 5.4: Combine the class hierarchy, data attributes, data content and its transmission direction to complete the establishment of the industrial software resource ontology model.
[0122] The established industrial software ontology model will be stored in the Neo4j graph database. In the Neo4j graph database, each class and attribute can be used as a node, and it supports the addition, deletion, query and modification of data, which is convenient for subsequent modification and expansion.
[0123] This method determines the hierarchical structure, attribute description dimensions, and software data transmission direction of software resources in the process of industrial software resource sharing, clarifies the basic architecture in the process of software resource sharing, and can effectively solve the problem of inconsistent sharing specifications in the process of industrial software resource sharing, break the bottleneck of difficulties in industrial software resource sharing and unclear supply and demand matching, effectively promote the digital construction of small and medium-sized enterprises, promote the digitalization and high-quality development of industrial clusters, and provide support for multi-mode collaborative innovation of regional small and medium-sized enterprise clusters under the industrial Internet environment.
[0124] This embodiment also discloses an ontology model construction system for industrial software resource sharing in the manufacturing industry, which is characterized by comprising:
[0125] The scope determination module is used to determine the fields and scopes involved in the industrial software resource ontology;
[0126] The hierarchical division module is used to divide the structural hierarchy of the industrial software resource ontology based on the determined domain and scope;
[0127] The attribute determination module is used to describe the data attributes of the industrial software resource ontology;
[0128] The data content and transmission direction determination module is used to define the data content and transmission direction transmitted between industrial software resource ontology classes;
[0129] The model building module is used to build an industrial software resource ontology model based on structural hierarchy, data attributes, data content and transmission direction.
[0130] A schematic diagram of a terminal device provided in an embodiment of the present invention. The terminal device of this embodiment includes: a processor, a memory, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the steps in the above-mentioned method embodiments are implemented. Alternatively, when the processor executes the computer program, the functions of the modules / units in the above-mentioned device embodiments are implemented.
[0131] The computer program may be divided into one or more modules / units, and the one or more modules / units are stored in the memory and executed by the processor to accomplish the present invention.
[0132] The terminal device may be a computing device such as a desktop computer, a notebook, a PDA, a cloud server, etc. The terminal device may include, but is not limited to, a processor and a memory.
[0133] The processor can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
[0134] The memory may be used to store the computer programs and / or modules, and the processor implements various functions of the terminal device by running or executing the computer programs and / or modules stored in the memory and calling the data stored in the memory.
[0135] If the module / unit integrated in the terminal device is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present invention implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, U disk, mobile hard disk, disk, optical disk, computer memory, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), electric carrier signal, telecommunication signal and software distribution medium. It should be noted that the content contained in the computer-readable medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electric carrier signals and telecommunication signals.
[0136] The above are only preferred embodiments of the present invention and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. 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.
Claims
1. A method for constructing an ontology model for industrial software resource sharing in manufacturing industry, characterized in that: The following steps are involved: Determine the fields and scopes involved in the industrial software resource ontology; Based on the determined domain and scope, the structural level of industrial software resource ontology is divided; Describe the data attributes of the industrial software resource ontology; Define the data content and direction transferred between industrial software resource ontology classes; An industrial software resource ontology model is constructed based on structural hierarchy, data attributes, data content and transmission direction.
2. The ontology model construction method for industrial software resource sharing in manufacturing industry according to claim 1 is characterized in that: The fields and scopes involved in the industrial software resource ontology include: Industrial software for business management, R&D design, manufacturing, operation and maintenance services, and AI empowerment.
3. The ontology model construction method for sharing industrial software resources in manufacturing industry according to claim 1 is characterized in that: The division of the structural hierarchy of the industrial software resource ontology comprises the following steps: The industrial software ontology hierarchy is divided into five first-level subcategories: Business management, R&D and design, manufacturing, operation and maintenance services, and AI empowerment; The second-level sub-categories are divided based on the first-level sub-categories: The secondary subcategories of the business management category include: enterprise resource management, financial management, human resource management, asset management, marketing management, supply chain management, office collaboration, quality inspection and traceability, instrument equipment management, supplier management, equipment visualization and predictive maintenance, and knowledge management; The secondary subcategories of the R&D and design category include: computer-aided design, computer-aided manufacturing, computer-aided engineering, computer-aided process planning, electronic design automation, process simulation software, product life cycle management, 3D virtual simulation system, molecular design software, first principle calculation software, economic evaluation software and product digital design; The secondary subcategories of the manufacturing category include: advanced planning systems, manufacturing execution systems, manufacturing operations management, warehouse management systems, scheduling optimization systems, energy efficiency management systems, real-time optimization systems, operator training simulation systems, advanced control systems, distributed control systems, programmable control systems, safety instrument systems, safety and risk management, data acquisition and monitoring systems, real-time database systems, product data management, quality management systems, decision support systems, and carbon emission monitoring and optimization; The secondary subcategories of the operation and maintenance service category include: asset performance management, maintenance and repair operation management, and fault prediction and health management The secondary subcategories of the AI empowerment category include: Industrial intelligence generation, industrial large model platform, intelligent big data analysis, industrial robot control, material genome design and knowledge representation and reasoning.
4. The ontology model construction method for industrial software resource sharing in manufacturing industry according to claim 1 is characterized in that: The data attributes describing the industrial software resource ontology include: Basic attributes, functional attributes, state attributes and transaction attributes.
5. The method for constructing an ontology model for sharing industrial software resources in manufacturing industry according to claim 4, characterized in that: The basic properties include: Software name, version information, release date, hardware requirements, software requirements, official website, software description and vendor information; The functional attributes include: Business segment, compatibility, software type (third-party applications, AI applications, web applications, mobile applications), access rights, scalability, integration capabilities, interface type (graphical user interface, web interface, physical controller interface, command line interface), degree of customization; The state attributes include: Not online, online, or offline; The transaction attributes include: Service fees, payment methods, transaction records, transaction types, delivery methods and user agreements.
6. The method for constructing an ontology model for industrial software resource sharing in manufacturing industry according to claim 1, characterized in that: The data content transmitted between the industrial software resource ontology classes includes: Basic process, actual process data, approval process, cost, customer data, design model, design quality, equipment status parameters, inventory, working time data, material consumption, material data, material distribution plan, material requirement plan, bill of materials, organizational data, outbound requisition, material list, personnel data, process model, output, production plan, production quality, supplier quality, business document data, process route and work order.
7. The method for constructing an ontology model for sharing industrial software resources in manufacturing industry according to claim 6, characterized in that: The transmission direction includes: The transmission direction of the basic process is: from the PLM system to the MES system; The actual process data is transmitted from the MES system to the PLM system. The transmission direction of the approval process is: from the OA system to the ERP system; The cost transfer direction is: from the ERP system to the PLM system; The direction of transmission of the customer data is: from the CRM system to the SCM system; The transmission direction of the design model is: from the CAPP system to the PLM system; The transmission direction of the design quality is: from the PLM system to the QMS system; The transmission direction of the equipment status parameters is: from the SCADA system to the MES system; The transfer direction of the inventory is: from the WMS system to the MES system or ERP system; The transmission direction of the working time data is: from the MES system to the HRM system; The transmission direction of the material consumption is: from the MES system to the ERP system; The material data transmission direction is: from the ERP system to the MES system or WMS system; The material distribution plan is transmitted from the MES system to the WMS system. The transmission direction of the material requirement plan is: from the ERP system to the SCM system; The transfer direction of the bill of materials is: from the PLM system to the MES system; The transmission direction of the organizational data is: from the HRM system to the ERP system; The delivery direction of the delivery application form is: from the MES system to the WMS system; The material list is transferred from the PLM system to the ERP system. The transfer direction of the personnel data is: from the HRM system to the ERP system; The transmission direction of the process model is: from the PLM system to the CAPP system; The transmission direction of the output is: from the MES system to the ERP system; The transmission direction of the production plan is: from the ERP system to the MES system; The transmission direction of the production quality is: from the MES system to the QMS system; The transfer direction of supplier quality is: from SCM system to QMS system; The transmission direction of the business document data is: from the ERP system to the OA system; The transmission direction of the process route is: from the PLM system to the ERP system; The transmission direction of the work order is: from the MES system to the SCADA system.
8. An ontology model building system for industrial software resource sharing in manufacturing industry, characterized in that: include: The scope determination module is used to determine the fields and scopes involved in the industrial software resource ontology; The hierarchical division module is used to divide the structural hierarchy of the industrial software resource ontology based on the determined domain and scope; The attribute determination module is used to describe the data attributes of the industrial software resource ontology; The data content and transmission direction determination module is used to define the data content and transmission direction transmitted between industrial software resource ontology classes; The model building module is used to build an industrial software resource ontology model based on structural hierarchy, data attributes, data content and transmission direction.
9. A terminal device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.
10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.
Citation Information
Cited By
Production whole-process management method and system based on AI industrial ontology
CN122736054A
