Manufacturing system model conversion method and apparatus, device, and storage medium

Abstract

Disclosed in the embodiments of the present invention are a manufacturing system model conversion method and apparatus, a device, and a storage medium. The method comprises: establishing a manufacturing system demand model on the basis of a target task and a system modeling language, and in the process of establishing the manufacturing system demand model, using a top-down hierarchical structure decomposition rule to decompose a manufacturing system demand to obtain a demand decomposition result; on the basis of the demand decomposition result, performing modeling on a manufacturing system from three dimensions: structure, behavior and parameter, so as to obtain a manufacturing system design model; and on the basis of a mapping relationship between a system modeling language model element and a discrete event simulation model element, converting the manufacturing system design model into a manufacturing system simulation model that is based on system discrete event simulation, wherein the manufacturing system simulation model is used for executing the target task. The present invention can automatically implement conversion of a system modeling language-based model and a discrete event simulation-based simulation model.

Description

Manufacturing system model conversion method, device, equipment and storage medium Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a manufacturing system model conversion method, device, equipment and storage medium. Background Art

[0002] Traditionally, requirements descriptions involve customers filling out forms, recording information in text, or a combination of the two. These methods collect a fixed range of data and require further processing into computer data. With the introduction of the Systems Modeling Language (SysML) model, customers can express their requirements freely, following the conversational style of text recording. Instead of recording information in text form, they can directly record their requirements in a SysML model. This makes it easier to convert unstructured or semi-structured data into structured data.

[0003] SysML-based models play an important role in addressing manufacturing system requirements description and design modeling. Through graphical and semantic model elements, they provide a clear system perspective for various stakeholders. Discrete Event Simulation (DES) software has been widely used for manufacturing system modeling and simulation. However, the conversion between SysML-based models and DES-based simulation models is difficult. Therefore, how to convert SysML-based models into DES-based simulation models is an urgent technical challenge.

[0004] Summary of the Invention

[0005] The embodiments of the present invention provide a manufacturing system model conversion method, apparatus, device and storage medium, which can automatically realize the conversion between a model based on a system modeling language and a simulation model based on discrete event simulation.

[0006] A manufacturing system model conversion method, comprising:

[0007] Establishing a manufacturing system requirement model based on a system modeling language according to target tasks, and decomposing the manufacturing system requirements using a top-down hierarchical structure decomposition rule in the process of establishing the manufacturing system requirement model to obtain a requirement decomposition result;

[0008] Based on the demand decomposition results, the manufacturing system is modeled from three dimensions: structure, behavior, and parameters to obtain a manufacturing system design model;

[0009] Based on the mapping relationship between system modeling language model elements and discrete event simulation model elements, the manufacturing system design model is converted into a manufacturing system simulation model based on system discrete event simulation, wherein the manufacturing system simulation model is used to execute the target task.

[0010] In one embodiment,

[0011] The types of requirements for manufacturing system requirements include: stakeholder requirements, system requirements, functional requirements, and physical requirements;

[0012] The top-down hierarchical structure decomposition rules include:

[0013] Any manufacturing system construction task has stakeholder demand information and physical demand information; wherein the manufacturing system construction task is generated according to the manufacturing system demand;

[0014] Any of the above requirement types can be obtained by decomposing the stakeholder demand information;

[0015] Any of the aforementioned demand types can be decomposed to obtain physical demand information;

[0016] Any stakeholder requirement can be decomposed into system requirement information, or functional requirement information, or system requirement information and functional requirement information.

[0017] In one embodiment,

[0018] Based on the demand decomposition result, the manufacturing system is modeled from three dimensions: structure, behavior, and parameters to obtain a manufacturing system design model, including:

[0019] Extract manufacturing system domain knowledge, build a metamodel of the manufacturing system, and define the model attributes of the metamodel;

[0020] Matching the attribute information of the meta-model with data corresponding to the demand decomposition result;

[0021] Fusing the matched model attributes of the meta-model with the data corresponding to the demand decomposition result, and instantiating them to generate a corresponding manufacturing system resource module;

[0022] A bottom-up combination method is adopted to combine the manufacturing resource modules from three dimensions: structure, behavior and parameters to obtain a manufacturing system design model.

[0023] In one embodiment,

[0024] The fusing the matched model attributes of the meta-model with the data corresponding to the demand decomposition result includes:

[0025] Directly embedding the structural data in the requirement decomposition result into the metamodel attributes of the matching metamodel;

[0026] For the unstructured data or semi-structured data in the decomposition results, the manufacturing system domain knowledge is extracted according to the graphic element architecture defined in the metamodel attributes, converted into requirement modules, and then embedded into the metamodel attributes of the matching metamodel.

[0027] In one embodiment,

[0028] The method of converting the manufacturing system design model into a manufacturing system simulation model based on system discrete event simulation based on a mapping relationship between system modeling language model elements and discrete event simulation model elements includes:

[0029] Acquire a general model corresponding to the meta-model based on the mapping relationship;

[0030] Acquire a data model corresponding to a resource module based on the mapping relationship; the resource module is a module for constructing a manufacturing system design model; the resource module is a module obtained by instantiating the metamodel;

[0031] A manufacturing system simulation model based on system discrete event simulation is generated based on the data model and the general model.

[0032] In one embodiment,

[0033] The mapping relationship between the system modeling language model elements and the discrete event simulation model elements is established based on the matching relationship between the object concept in the meta-model for establishing the manufacturing system design model and the simulation object concept in the discrete event simulation software.

[0034] In one embodiment,

[0035] The method further comprises:

[0036] Associating the manufacturing system requirement model, the manufacturing system design model and the manufacturing system simulation model constructed from a system perspective based on four dimensions: requirement, structure, behavior and parameter;

[0037] Verifying requirements through the manufacturing system simulation model;

[0038] In response to the manufacturing system simulation model failing to meet the manufacturing system requirements or the manufacturing system requirements changing, a manufacturing system design model and a manufacturing system simulation model are rebuilt based on an updated manufacturing system requirement model.

[0039] A manufacturing system model conversion device, comprising:

[0040] a decomposition module configured to establish a manufacturing system requirement model based on a system modeling language according to a target task, and decompose the manufacturing system requirements using a top-down hierarchical structure decomposition rule during the manufacturing system requirement model establishment process to obtain a requirement decomposition result;

[0041] A construction module is configured to execute modeling of the manufacturing system from three dimensions of structure, behavior and parameters based on the demand decomposition result to obtain a manufacturing system design model;

[0042] The conversion module is configured to execute a mapping relationship between system modeling language model elements and discrete event simulation model elements, and convert the manufacturing system design model into a manufacturing system simulation model based on system discrete event simulation, wherein the manufacturing system simulation model is used to perform the target task.

[0043] In one embodiment,

[0044] The construction module is configured to perform manufacturing system domain knowledge extraction, construct a metamodel of the manufacturing system, and define the model attributes of the metamodel; match the attribute information of the metamodel with the data corresponding to the demand decomposition result; fuse the matched model attributes of the metamodel with the data corresponding to the demand decomposition result, and instantiate them to generate a corresponding manufacturing system resource module; adopt a bottom-up combination method to combine the manufacturing resource modules from three dimensions of structure, behavior and parameters to obtain a manufacturing system design model.

[0045] In one embodiment,

[0046] The conversion module is configured to execute the acquisition of a general model corresponding to the metamodel based on the mapping relationship; the acquisition of a data model corresponding to the resource module based on the mapping relationship; the resource module is a module for constructing a manufacturing system design model; the resource module is a module obtained after instantiating the metamodel; and the generation of a manufacturing system simulation model based on system discrete event simulation based on the data model and the general model.

[0047] An electronic device, comprising:

[0048] processor;

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

[0050] The processor is configured to read the executable instructions from the memory and execute the executable instructions to implement any one of the manufacturing system model conversion methods described above.

[0051] A computer-readable storage medium stores computer instructions, wherein the computer instructions, when executed by a processor, implement the manufacturing system model conversion method as described in any one of the above items.

[0052] A computer program product comprises a computer program, wherein when the computer program is executed by a processor, the manufacturing system model conversion method as described in any one of the above items is implemented.

[0053] As can be seen from the above technical solution, the above embodiment builds a system requirement model based on SysML and decomposes the manufacturing system requirements during the model construction process. Based on the requirement decomposition results and the extraction of manufacturing system domain knowledge, a manufacturing system design model is constructed from the three dimensions of structure, behavior, and parameters. Finally, based on the conversion of SysML model data to DES simulation data and the mapping relationship, the conversion between the manufacturing system design model and the manufacturing system simulation model is achieved. This disclosed example can automatically realize the conversion between the model based on the system modeling language and the simulation model based on discrete event simulation, thereby improving the efficiency of model generation and reducing the cost of model generation. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] 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:

[0055] FIG1 is a flow chart of a manufacturing system model conversion method according to an embodiment of the present invention.

[0056] FIG2 is a schematic diagram of a manufacturing system requirement decomposition architecture in an embodiment disclosed in the present invention.

[0057] FIG3 is a schematic diagram of a manufacturing system design model architecture generated in an embodiment disclosed in the present invention.

[0058] FIG4 is a schematic diagram of a module architecture for generating resource of a manufacturing system in an embodiment disclosed in the present invention.

[0059] FIG5 is a schematic diagram of an architecture for converting a manufacturing system design model into a manufacturing system simulation model in an embodiment disclosed in the present invention.

[0060] FIG6 is a schematic diagram of a modeling architecture of a manufacturing system requirement-design-simulation model from a system perspective in an embodiment disclosed in the present invention.

[0061] FIG7 is a structural diagram of a manufacturing system model conversion device disclosed in an embodiment of the present invention.

[0062] FIG8 is a structural diagram of an electronic device disclosed in an embodiment of the present invention.

[0063] The accompanying drawings are numerals as follows: DETAILED DESCRIPTION

[0064] 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.

[0065] 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.

[0066] Currently, the integration of manufacturing system requirements, design, and simulation is gaining increasing attention. This can greatly improve the design efficiency of manufacturing systems and better meet customer needs. However, this inevitably requires considering data interaction throughout the process to facilitate the transformation from requirements models to design models and simulation models.

[0067] Standardized data collection methods based on tables in related technologies cannot fully meet customer needs. While non-standard data collection methods can document customer requirements in greater detail, subsequent data processing remains challenging. SysML models effectively adapt to this situation by converting unstructured or semi-structured data into structured data. However, how to automatically convert SysML-based models into DES-based simulation models remains a pressing technical challenge.

[0068] The embodiment of the present invention proposes a novel manufacturing system model conversion method, which can automatically convert a SysML-based model into a DES-based simulation model.

[0069] When a target task needs to be executed, a manufacturing system simulation model for executing the target task needs to be established. How to establish a manufacturing system simulation model based on the target task is the technical problem to be solved below. The target task here can be controlling equipment production, system fault detection, etc., which is not limited in the embodiments of the present application.

[0070] Figure 1 is a flow chart of a manufacturing system model conversion method according to an embodiment of the present invention. The method can be executed by one or more devices.

[0071] As shown in FIG1 , the method includes:

[0072] Step 101: Establish a manufacturing system requirement model based on a system modeling language according to a target task, and decompose the manufacturing system requirements using a top-down hierarchical structure decomposition rule during the manufacturing system requirement model establishment process to obtain a requirement decomposition result.

[0073] Step 102 : Based on the demand decomposition result, the manufacturing system is modeled from three dimensions: structure, behavior, and parameters, to obtain a manufacturing system design model.

[0074] Step 103 : Based on the mapping relationship between the system modeling language model elements and the discrete event simulation model elements, the manufacturing system design model is converted into a manufacturing system simulation model based on system discrete event simulation, wherein the manufacturing system simulation model is used to execute the target task.

[0075] In step 101, when establishing a manufacturing system requirement model based on the system modeling language according to the target task, the technical process of the international standard ISO / IEC 15288:2002 (2008) is followed. The technical process defines requirement categories and related concepts and approves the consistency of these concepts with existing model elements in SysML. It also implements the establishment of requirement model elements and attributes based on the extensibility of SysML.

[0076] The demand types of manufacturing system requirements include stakeholder requirements (SN), system requirements (SR), functional requirements (FR), and physical requirements (PR). The demand information corresponding to each demand type is stakeholder demand information, system demand information, functional demand information, and physical demand information.

[0077] The hierarchical structure decomposition rules used can be specifically:

[0078] Any manufacturing system construction task has stakeholder demand information and physical demand information. The manufacturing system construction task is generated according to the manufacturing system demand, which can be expressed as follows:

[0079] Among them, TASK construction Represents the manufacturing system construction task; it can also be seen here that the two types of requirements, SN and PR, are the minimum conditions for describing the construction task.

[0080] Any type of requirement can be obtained by decomposing the stakeholder demand information; it can be expressed as follows:

[0081] Any requirement type can be decomposed to obtain physical requirement information; this can be expressed as follows:

[0082] Any stakeholder requirement can be decomposed into system requirement information, or functional requirement information, or system requirement information and functional requirement information; it can be expressed by the following formula:

[0083] in, Indicates any, arbitrary, It means existence, ∨ means conjunction (and) operation of proposition, ∧ means disjunction (or) operation of proposition, and Decomposition means decomposition.

[0084] Figure 2 is a schematic diagram of the manufacturing system requirements decomposition architecture in accordance with an embodiment of the present invention. Figure 2 illustrates how stakeholder requirements information 11 can be decomposed into system requirements information 12 and / or functional requirements information 13; system requirements information 12 and functional requirements information 13 can then be decomposed into physical requirements information 14. Figure 2 illustrates a typical requirements decomposition process; in practical applications, stakeholder requirements information 11 can also be directly decomposed into physical requirements information 14, a process not specifically limited in the present invention.

[0085] In step 102, based on the result of the demand decomposition, the manufacturing system is modeled from three dimensions: structure, behavior, and parameters to obtain a manufacturing system design model. See FIG3, which is a schematic diagram of the architecture of the manufacturing system design model generated in the embodiment disclosed in the present invention.

[0086] Specifically include:

[0087] First, the manufacturing system domain knowledge is extracted from the domain knowledge base 21, a metamodel of the manufacturing system is constructed, and the model attributes of the metamodel are defined;

[0088] Secondly, the attribute information of the meta-model is matched with the result of the demand decomposition; wherein the result of the demand decomposition is stored in the database 22 and converted into the knowledge of the ontology model when stored in the database 22 .

[0089] Taking the subsystem MPO as an example, according to the physical objects in the physical requirement information in the requirement decomposition result, the corresponding metamodel is called from the metamodel package to match the resources defined by the physical entity.

[0090] In the process of building the metamodel of the manufacturing system, if there is no such metamodel, the metamodel can be newly created and supplemented according to the metamodel construction method.

[0091] Thirdly, the model attributes of the matched meta-model and the data corresponding to the demand decomposition result are fused and instantiated 20 to generate a manufacturing system resource module;

[0092] In this step, the model attributes of the matched meta-model are integrated with the data corresponding to the requirements decomposition results, specifically including:

[0093] The structural data in the requirements decomposition results are directly embedded into the metamodel attributes of the matching metamodel;

[0094] For the unstructured data or semi-structured data in the decomposition results, the manufacturing system domain knowledge is extracted according to the graphic element architecture defined in the metamodel attributes, converted into requirement modules, and then embedded into the metamodel attributes of the matching metamodel.

[0095] In specific implementation, the meta-model is instantiated into a manufacturing resource module based on different equipment data, fault data, etc. in the demand decomposition results.

[0096] Finally, a bottom-up combination method is adopted to combine manufacturing resource modules from three dimensions: structure, behavior, and parameters to obtain a manufacturing system design model.

[0097] When the three dimensions of structure, behavior and parameters are combined, the structure is divided into system structure 31 and subsystem structure 311; the behavior is divided into system behavior 32 and subsystem behavior 321; and the parameters are divided into system parameters 33 and subsystem parameters 331.

[0098] The following is a specific example to give the process of generating the manufacturing system design model.

[0099] Figure 4 is a schematic diagram of the architecture for generating a manufacturing system resource module in an embodiment of the present invention. The multidimensional data 40 in the demand decomposition results shown in Figure 4 are: product data 41, production data 42, structure data 43, quality data 44, equipment data 45, personnel data 46, and statistical data 47. This is just one example of an embodiment of the present invention; in specific implementations, data of corresponding dimensions may be increased or decreased based on the actual application scenario.

[0100] Domain knowledge is extracted from the domain knowledge base 21 to establish a workstation meta-model 48 and define attribute information of the workstation meta-model. The multidimensional data 40 is fused with the attribute information of the workstation meta-model 48 to obtain a fusion result 49.

[0101] Based on the fusion result, the workstation meta-model is instantiated to obtain the manufacturing system resource module 410 of the processing station “drilling and reaming #1”.

[0102] In practical applications, metamodel attributes do not necessarily need to be fully embedded in the data before they can be instantiated. Instead, the selection of attribute filling depends on the actual application. For example, the attribute filling of the machining station "Drilling and Reaming #1" in Figure 4 is not fully integrated with the data compared to the station metamodel. The integration of metamodel attributes and data is also a process of reorganizing the data.

[0103] The manufacturing industry generates a vast amount of multidimensional, heterogeneous data throughout its design, implementation, and operation processes. While some structured data can be directly used after analysis, unstructured and semi-structured data is more difficult to use directly and requires conversion. A metamodel, a specific data extraction framework, processes this data and transforms it into structured data.

[0104] As shown in Figure 4, the instantiated resource module: processing station "Drilling and Reaming #1", corresponding attributes: Drilling and Reaming #1 attributes, flow: white disk, parameters: Drilling and Reaming #1 production data, Drilling and Reaming #1 fault data, Drilling and Reaming #1 quality data, Drilling and Reaming #1 statistics, corresponding requirements: Drilling and Reaming #1 requirements, corresponding structure: Drilling and Reaming #1 structure;

[0105] These contents correspond to data modules respectively, namely: drilling and reaming hole #1 attribute data module 411, white disc data module 412, drilling and reaming hole #1 production data data module 413, drilling and reaming hole #1 fault data data module 414, drilling and reaming hole #1 quality data data module 415, drilling and reaming hole #1 statistical data data module 416, drilling and reaming hole #1 demand module 417, and drilling and reaming hole #1 structure module 418.

[0106] The eight data modules described above are the fusion of multidimensional data and metamodel attributes, organized into a data structure that is directly application-oriented. Furthermore, the metamodel instantiation forms a manufacturing system resource module, which is organized according to the modeling methodology to form a manufacturing system design model. Subsequently, a corresponding manufacturing system simulation model will need to be established. The instantiation of the module with data integration provides more diverse and specific descriptive information, and only such information can support the subsequent construction of the simulation model. If only simulation applications are considered, the metamodel attributes can be embedded to select the data requirements for simulation modeling. Once the integration is complete, the corresponding data interface can be used to generate an information model in the simulation space.

[0107] The resource modules for implementing each functional requirement have been identified, but these are only individual resource modules; the relationships between these modules are not. The construction of a manufacturing system design model involves organizing these manufacturing resource modules according to the modeling approach to construct the corresponding application domain model and system integration model.

[0108] The model is organized from the bottom up, following the resource module-subsystem-system hierarchy, and is described from three dimensions: structure, behavior, and parameters. The structure uses SysML's Block Definition Diagram (BDD) and Internal Block Diagram (IBD) to express the subsystem's external structure and internal relationships. The behavior is expressed using SysML's Activity Diagram (ACT). The Block Definition Diagram (BDD) and Parameter Diagram (PAR) integrate the data parameters of each module and subsequently convert them into corresponding data information models.

[0109] The following examples illustrate the subsystem structure, subsystem behavior, subsystem parameters, and system parameters:

[0110] Subsystem structure:

[0111] Take the structural information expression of the multifunctional processing station MPO with a kiln as an example:

[0112] Clearly express the components of the MPO subsystem, such as the kiln, two-axis rail robot with vacuum grippers, conveyor belt, milling machine, and PLC;

[0113] Express the relationship between the components within the subsystem MPO structure, as well as the relationship between the components of the subsystem, workpiece flow and other information;

[0114] Embedded activity modules integrate the subsystem's main activities into the internal module diagram, enhancing stakeholders' understanding of the model and improving its readability. Activity diagrams typically only represent the behavior but fail to describe the actors who perform it. Embedded activity modules not only enrich the subsystem's internal structure but also couple components with activities, allowing for a clearer description of the relationships between them.

[0115] Subsystem behavior:

[0116] Take the behavior information representation of the multifunctional processing station MPO with a kiln as an example:

[0117] Use activity diagrams (ACTs) to describe the functions, behaviors, and operations within the MPO. The model information in the activity diagram is delivered based on flows, focusing on each behavior, operation, and corresponding state determination, without involving objects related to the activity.

[0118] In the multifunctional processing station MPO with kiln, the workpiece flow automatically passes through several workstations, simulating different process steps. The workpieces are combined into a workpiece flow and finally output as sintered and milled workpieces.

[0119] The "Input Workpiece" action sends a signal to check whether the workpiece has arrived at the kiln. A subsequent event action determines the workpiece's position. If the workpiece is in place, it proceeds to the next action, "Sintering." Simultaneously, a signal flow is sent to execute the "Status Update" and "PLC Control" actions. If the workpiece is not in place, the workpiece's position is continuously determined until the required position is met. Subsequent actions, such as "Transfer," "Milling," and "Ejection," follow the same logic. Finally, the processed workpiece is output, and the "Milling Machine Zeroing" action is executed.

[0120] Subsystem parameters and system parameters:

[0121] In order to make the equipment data more suitable for building the information model in the simulation model, the resource modules in Figure 4 are reorganized according to the corresponding parameters of the workstation model.

[0122] At this point, the construction of the manufacturing system design model is completed.

[0123] In step 103, the mapping relationship between system modeling language model elements and discrete event simulation model elements is established based on the matching relationship between the object concepts in the metamodel used to establish the manufacturing system design model and the simulation object concepts in the discrete event simulation software. An example of a specific mapping relationship is provided below in conjunction with Table 1, but the mapping relationship is not limited to the mapping relationship shown in Table 1. The specific mapping relationship is determined based on the target task.

[0124] Table 1

[0125] Table 1 shows the mapping relationship between metamodel elements and simulation elements, and gives the simulation element type to indicate whether the simulation element is an original software object or a custom object.

[0126] The mapping relationships in Table 1 can be set up simultaneously with the metamodel construction. The concepts extracted from the metamodel construction have clear definitions and functional descriptions, while the corresponding simulation objects need to consider the internal definitions of the specific simulation software. This allows for simultaneous implementation, saving time and improving efficiency in model conversion.

[0127] In step 103, based on the mapping relationship between system modeling language model elements and discrete event simulation model elements, the manufacturing system design model is converted into a manufacturing system simulation model based on system discrete event simulation. For a specific implementation, see FIG5 , which is a schematic diagram of the architecture for converting a manufacturing system design model into a manufacturing system simulation model in accordance with an embodiment of the present invention. FIG5 illustrates the integration of a manufacturing system design model 501 within a SysML environment 50, the generation of a manufacturing system simulation model 511 within a discrete event simulation environment 51, and the conversion between the integrated manufacturing system design model 501 and the manufacturing system simulation model 511 based on a mapping relationship 52. Specifically,

[0128] Obtaining a general model 512 corresponding to the metamodel 502 based on the mapping relationship 52;

[0129] The data model 513 corresponding to the resource module 503 is obtained based on the mapping relationship; the resource module 503 is a module for constructing the manufacturing system design model; the resource module 503 is obtained after the metamodel 502 is instantiated;

[0130] A manufacturing system simulation model 511 is generated based on the data model 513 and the general model 512 .

[0131] A manufacturing system design model 501 may be generated based on the resource module 503 .

[0132] Therefore, in the conversion process between the design model and the simulation model, the design model objects are mapped to the simulation model objects; the system parameters in the design model are converted into the data structure in the simulation environment.

[0133] The purpose of mapping from metamodel 502 to general model 512 is to find a general model in the simulation space that can present the same concepts and functions as the metamodel. The physical objects represented by the metamodel may have simple semantics. Basic objects in the simulation space are sufficient to virtually present physical objects. Some are more complex and require combining multiple basic objects to form new modules to meet usage requirements. Both the general model and the metamodel can be regarded as classes, and an instantiation process is introduced to convert the classes into actual usable modeling objects.

[0134] Mapping resource modules 503 to data models 513 involves mapping resource modules to information models within the simulation space. The correlation between metamodel attributes and data can be viewed as a data reorganization process. Specifically, the resource module obtained through instantiation is a data structure block with domain characteristics. A data model with object identifiers and attribute data can be obtained from the resource module's source file.

[0135] In the embodiment of the present application, the mapping between the manufacturing system design model elements and the manufacturing system simulation model elements is performed based on the defined rule table, and the mapping is implemented based on the Xpath data interface. As shown in Figure 5, the mapping process is divided into two parts:

[0136] The first part of the mapping process involves mapping the metamodel to a general model in the simulation space. This process primarily involves identifying corresponding objects in the simulation space for the entities represented by the metamodel. Some physical objects represented by metamodels have simple semantics, and their functionality can be satisfied using the basic objects in the simulation modeling software. Others are more complex, requiring the combination of multiple basic objects in the simulation space to form new modules to meet specific needs. Both the general model and the metamodel can be considered classes, and the data-driven process of instantiating the general model and metamodel is the process of materializing the classes into actual, usable objects.

[0137] The second part of the mapping process involves mapping the manufacturing system resource module to a data model in the simulation space. During the manufacturing system design modeling process, the integration of metamodel attributes and data is itself a data reorganization process. The resulting instantiated manufacturing system resource module is a data structure with actual feature attributes. Using the corresponding interface, data is extracted from the source file of the manufacturing resource module, and the output is a data model with object identifiers and attribute data.

[0138] The manufacturing system requirement model and the manufacturing system design model are both built based on SysML, and the manufacturing system simulation model is built based on DSE.

[0139] At this point, the conversion between the SysML-based model and the manufacturing system simulation model is completed, and the establishment of the manufacturing system DES model is also realized.

[0140] In the disclosed embodiment of the present invention, manufacturing system requirements are decomposed during the construction of a system simulation requirements model based on SysML. Based on the decomposition results and the extraction of manufacturing system domain knowledge, a manufacturing system design model is constructed from three dimensions: structure, behavior, and parameters. Finally, based on mapping relationships, the manufacturing system design model is converted into a manufacturing system simulation model, and the SysML model data is converted into DES simulation data. This disclosed example can automatically convert SysML-based models into DES-based models, thereby improving model generation efficiency and reducing model generation costs.

[0141] On this basis, the disclosed example also proposes a closed-loop implementation to model the manufacturing system based on four dimensions: demand, structure, behavior, and parameters, and to update the model. The specific implementation is as follows:

[0142] Based on the four dimensions of demand, structure, behavior and parameters, the manufacturing system demand model, manufacturing system design model and manufacturing system simulation model from the system perspective are linked;

[0143] Verify requirements through manufacturing system simulation models;

[0144] In response to the manufacturing system simulation model failing to meet the manufacturing system requirements or the manufacturing system requirements changing, the manufacturing system design model and the manufacturing system simulation model are rebuilt based on the updated manufacturing system requirement model.

[0145] Figure 6 is a schematic diagram of the modeling architecture of the manufacturing system requirement-design-simulation model from a system perspective in the disclosed embodiment of the present invention. In Figure 6, the domain dimension of the model domain is mainly based on the model domain, which is specifically divided into the manufacturing system simulation model, the manufacturing system design model, and the resource module. It is used to replace the problem domain, the solution domain, and the implementation domain in the MagicGrid methodology. The information description of the requirement domain will be directly completed by the requirements in the subsequent key information dimension. The key information dimension completely follows the four aspects of requirements, behavior, structure, and parameters in the MagicGrid methodology to fully describe the model content in the model domain.

[0146] The entire closed-loop process begins with requirements decomposition in the requirements domain. The system simulation model corresponds to stakeholder requirements, and the entire closed-loop is verified by the virtual simulation model in the DES software. Stakeholder requirements are then decomposed into corresponding system requirements and functional requirements, which are qualitatively verified by the system model and subsystem models in the system design model. Functional requirements are decomposed into physical requirements, which determine the metamodel required for modeling. Through the metamodel-data association mechanism, the metamodel is instantiated into the corresponding manufacturing resource module. The behavior, structure, and parameter columns primarily describe the model assembly process. Manufacturing resource modules are assembled into the system design model, which is then converted into the system simulation model based on a mapping mechanism. If the system simulation model fails to meet stakeholder requirements or if stakeholder requirements change, the requirements decomposition and model integration process is repeated to generate a new manufacturing system design model and manufacturing system simulation model until the new manufacturing system simulation model meets stakeholder requirements.

[0147] This system perspective also provides a standardized process for manufacturing system requirements-design-simulation modeling. Modelers can perform requirements decomposition, data conversion, and model construction according to Figure 6.

[0148] Figure 6 shows that information dimension 60 includes requirements 61, structure 62, behavior 63, and parameters 64. Model domain 600 includes system simulation model layer 601, system design model layer 602, and resource module model layer 603. Requirements verification is performed on manufacturing system simulation model 611. If the manufacturing system simulation model fails to meet manufacturing system requirements or if manufacturing system requirements 61 change, stakeholder information 11 is updated and decomposed to obtain system requirements information 12 and / or functional requirements information 13. This system requirements information 12 and / or functional requirements information 13 are then decomposed to obtain physical requirements information 14.

[0149] Next, the manufacturing system resource module is generated based on the domain knowledge base 21 and the decomposed physical requirement information 14:

[0150] First, the manufacturing system domain knowledge is extracted from the domain knowledge base 21, a metamodel of the manufacturing system is constructed, and the model attributes of the metamodel are defined;

[0151] Secondly, the attribute information of the meta-model is matched with the result of the demand decomposition; wherein the result of the demand decomposition is stored in the database 22 and converted into the knowledge of the ontology model when stored in the database 22 .

[0152] Thirdly, the model attributes of the matched meta-model and the data corresponding to the demand decomposition result are fused and instantiated 20 to generate a manufacturing system resource module;

[0153] Finally, a bottom-up combination method is adopted to combine manufacturing resource modules from three dimensions: structure, behavior, and parameters to obtain a manufacturing system design model.

[0154] When the three dimensions of structure, behavior and parameters are combined, the structure is divided into system structure 31 and subsystem structure 311; the behavior is divided into system behavior 32 and subsystem behavior 321; and the parameters are divided into system parameters 33 and subsystem parameters 331.

[0155] Based on the mapping relationship 52 , a model mapped from the manufacturing system design model is obtained as a manufacturing system simulation model.

[0156] At this point, the system model update is completed.

[0157] FIG7 is a structural diagram of a manufacturing system model conversion device disclosed in an embodiment of the present invention. As shown in FIG7 , the manufacturing system model conversion device 700 includes:

[0158] The decomposition module 701 is configured to establish a manufacturing system requirement model based on a system modeling language according to a target task, and decompose the manufacturing system requirements using a top-down hierarchical structure decomposition rule during the manufacturing system requirement model establishment process to obtain a requirement decomposition result;

[0159] A construction module 702 is configured to execute modeling of the manufacturing system from three dimensions of structure, behavior and parameters based on the demand decomposition result to obtain a manufacturing system design model;

[0160] The conversion module 703 is configured to execute a mapping relationship between system modeling language model elements and discrete event simulation model elements, and convert the manufacturing system design model into a manufacturing system simulation model based on system discrete event simulation, wherein the manufacturing system simulation model is used to perform the target task.

[0161] In one embodiment,

[0162] The construction module 702 is configured to perform manufacturing system domain knowledge extraction, construct a metamodel of the manufacturing system, and define the model attributes of the metamodel; match the attribute information of the metamodel with the data corresponding to the requirement decomposition result; fuse the matched model attributes of the metamodel with the data corresponding to the requirement decomposition result; use the data corresponding to the fused requirement decomposition result to instantiate the corresponding metamodel to generate a corresponding manufacturing system resource module; adopt a bottom-up combination method to combine the manufacturing resource modules from three dimensions of structure, behavior and parameters to obtain a manufacturing system design model.

[0163] In one embodiment,

[0164] The conversion module 703 is configured to execute the steps of obtaining a general model corresponding to the meta-model based on the mapping relationship; obtaining a data model corresponding to the resource module based on the mapping relationship; the resource module is a module for constructing a manufacturing system design model; the resource module is a module obtained by instantiating the meta-model; and generating a manufacturing system simulation model based on system discrete event simulation based on the data model and the general model.

[0165] The embodiment of the present invention also proposes an electronic device with a processor-memory architecture. Figure 8 is a structural diagram of an electronic device disclosed in the embodiment of the present invention. As shown in Figure 8, the electronic device 800 includes a processor 801, a memory 802, and a computer program stored on the memory 802 and executable on the processor 801. When the computer program is executed by the processor 801, any of the above manufacturing system model conversion methods 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 to include 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, an MCU, or a DSP, and so on.

[0166] 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.

[0167] 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.

[0168] The above are only preferred embodiments of the present invention and are 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 should be included in the scope of protection of the present invention.

[0169] Nouns and pronouns referring to persons in this patent application are not limited to a specific gender.

Claims

1. A manufacturing system model conversion method, characterized in that: include: Establishing a manufacturing system requirement model based on a system modeling language according to the target task, and decomposing the manufacturing system requirements using a top-down hierarchical structure decomposition rule in the process of establishing the manufacturing system requirement model to obtain a requirement decomposition result (101); Based on the demand decomposition result, the manufacturing system is modeled from three dimensions of structure, behavior and parameters to obtain a manufacturing system design model (102); Based on the mapping relationship between system modeling language model elements and discrete event simulation model elements, the manufacturing system design model is converted into a manufacturing system simulation model based on system discrete event simulation, wherein the manufacturing system simulation model is used to execute the target task (103).

2. The method according to claim 1, characterized in that The types of requirements for the manufacturing system requirements described include: stakeholder requirements, system requirements, functional requirements, and physical requirements; The top-down hierarchical structure decomposition rules include: Any manufacturing system construction task has stakeholder demand information and physical demand information; wherein the manufacturing system construction task is generated according to the manufacturing system demand; Any of the above requirement types can be obtained by decomposing the stakeholder demand information; Any of the requirements types described can be decomposed to obtain physical requirements information; Any stakeholder requirement can be decomposed into system requirement information, or functional requirement information, or system requirement information and functional requirement information.

3. The method according to claim 1, characterized in that Based on the requirement decomposition result, the manufacturing system is modeled from three dimensions of structure, behavior and parameters to obtain a manufacturing system design model, including: Extract knowledge from the manufacturing system domain, build a metamodel of the manufacturing system, and define the model attributes of the metamodel; Matching the attribute information of the meta-model with the data corresponding to the requirement decomposition result; The model attributes of the matched meta-model are integrated with the data corresponding to the demand decomposition result, and instantiated to generate a corresponding manufacturing system resource module; A bottom-up combination method is adopted to combine the manufacturing resource modules from three dimensions of structure, behavior and parameters to obtain a manufacturing system design model.

4. The method according to claim 3, characterized in that The step of fusing the matched model attributes of the meta-model with the data corresponding to the requirement decomposition result includes: Directly embedding the structural data in the requirement decomposition result into the metamodel attributes of the matching metamodel; For the unstructured data or semi-structured data in the decomposition result, the manufacturing system domain knowledge is extracted according to the primitive element architecture defined in the metamodel attributes, converted into requirement modules, and then embedded into the metamodel attributes of the matching metamodel.

5. The method according to claim 1, characterized in that The method of converting the manufacturing system design model into a manufacturing system simulation model based on system discrete event simulation based on a mapping relationship between system modeling language model elements and discrete event simulation model elements comprises: Acquire a common model corresponding to the meta-model based on the mapping relationship; Based on the mapping relationship, a data model corresponding to a resource module is obtained; the resource module is a module for constructing a manufacturing system design model; the resource module is a module obtained by instantiating the metamodel; A manufacturing system simulation model based on system discrete event simulation is generated based on the data model and the general model.

6. The method according to claim 1, characterized in that The mapping relationship between the system modeling language model elements and the discrete event simulation model elements is established based on the matching relationship between the object concept in the meta-model for establishing the manufacturing system design model and the simulation object concept in the discrete event simulation software.

7. The method according to any one of claims 1 to 6, characterized in that: The method further comprises: Associating the manufacturing system requirement model, the manufacturing system design model and the manufacturing system simulation model constructed from a system perspective based on four dimensions: requirement, structure, behavior and parameter; Verifying requirements through the manufacturing system simulation model; In response to the manufacturing system simulation model failing to meet the manufacturing system requirements, or the manufacturing system requirements changing, a manufacturing system design model and a manufacturing system simulation model are rebuilt based on an updated manufacturing system requirement model.

8. A manufacturing system model conversion device (700), characterized in that: include: A decomposition module (701) is configured to establish a manufacturing system requirement model based on a system modeling language according to a target task, and decompose the manufacturing system requirements using a top-down hierarchical structure decomposition rule in the process of establishing the manufacturing system requirement model to obtain a requirement decomposition result; A construction module (702) is configured to perform modeling of the manufacturing system from three dimensions of structure, behavior and parameters based on the demand decomposition result to obtain a manufacturing system design model; The conversion module (703) is configured to execute a mapping relationship between system modeling language model elements and discrete event simulation model elements, and convert the manufacturing system design model into a manufacturing system simulation model based on system discrete event simulation, wherein the manufacturing system simulation model is used to execute the target task.

9. The device (700) according to claim 8, characterized in that The construction module (702) is configured to perform manufacturing system domain knowledge extraction, construct a metamodel of the manufacturing system, and define the model attributes of the metamodel; match the attribute information of the metamodel with the data corresponding to the requirement decomposition result; fuse the matched model attributes of the metamodel with the data corresponding to the requirement decomposition result, and instantiate them to generate a corresponding manufacturing system resource module; adopt a bottom-up combination method to combine the manufacturing resource modules from three dimensions of structure, behavior and parameters to obtain a manufacturing system design model.

10. The device (700) according to claim 8, characterized in that The conversion module (703) is configured to execute the steps of acquiring a general model corresponding to the metamodel based on the mapping relationship; acquiring a data model corresponding to a resource module based on the mapping relationship; the resource module is a module for constructing a manufacturing system design model; and the resource module is a module obtained by instantiating the metamodel. A manufacturing system simulation model based on system discrete event simulation is generated based on the data model and the general model.

11. An electronic device (800), characterized in that: include: Processor (801); A memory (802), configured to store 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 manufacturing system model conversion method according to any one of claims 1 to 7.

12. A computer-readable storage medium having computer instructions stored thereon, characterized in that: When the computer instructions are executed by a processor, the manufacturing system model conversion method according to any one of claims 1 to 7 is implemented.

13. A computer program product, characterized in that The invention comprises a computer program, which, when executed by a processor, implements the manufacturing system model conversion method according to any one of claims 1 to 7.

Images