Method and device for supporting communication between complex equipment system design and simulation

Through the generation of simulation configuration files based on the meta-model library and form based on the KARMA language, the conversion problem of multiple simulation platforms and modeling languages ​​in the existing technology is solved, and the flexibility and efficiency improvement of the design and simulation of complex equipment system are achieved.

CN119047196APending Publication Date: 2024-11-29BEIJING INST OF TECH
View PDF 0 Cites 3 Cited by

Patent Information

Application Number
CN202411236753.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-09-04
Publication Date
2024-11-29

AI Technical Summary

Technical Problem

The existing system design and simulation methods are difficult to support the integration of multiple system simulation platforms and model conversion under the description of multiple modeling languages, resulting in poor flexibility and adaptability of the conversion, making it difficult to meet the design of multi-field heterogeneous modeling languages. Simulation requirements.

Method used

The complex equipment system is constructed using the meta-model library based on the KARMA language. The architecture and functional state transition are described through the graphic element model, object element model and relational element model, combined with the mission and task analysis form and equipment parameter form, and generated simulation configuration file code, supporting Transformation of multiple modeling languages ​​and simulation platforms.

Benefits of technology

It realizes seamless integration of system design and multiple simulation platforms and model conversion of multiple modeling languages, improves the flexibility and adaptability of model conversion, enhances data traceability and efficiency of design simulation, and supports a wide range of Compatibility and applicability.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119047196A_ABST
    Figure CN119047196A_ABST
Patent Text Reader

Abstract

The invention provides a method and device for supporting communication between complex equipment system design and simulation. The method comprises the following steps: constructing a meta-model library of a complex equipment system based on a KARMA language, and designing a form; based on mission task information, system equipment composition information, function state conversion information of each equipment in the system and system simulation process information in the complex equipment system, constructing various source models of the complex equipment system by utilizing a meta-model library and a form; a user formulates a code generation rule by writing a code generation script, extracts information from the source model according to the code generation rule and fills the information into a configuration file template, and a configuration file code required by simulation deduction is generated; the simulation configuration file code is imported into the simulation deduction platform, and deduction evaluation is carried out on the designed simulation scene. By means of the method, communication between system design and various system simulation platforms and conversion from a system design model described by various modeling languages to a simulation model can be supported.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of complex equipment system engineering, and in particular to a method and device for supporting complex equipment system design and simulation. Background Art

[0002] With the continuous advancement of the digitalization process of complex systems, many industrial sectors have begun to carry out digital practices of system or system design. To support these digital practices, most companies choose to use model-based system engineering methods. Model-based system engineering is a method that formally applies modeling in the conceptual design stage. Its purpose is to support full life cycle design activities such as demand analysis, conceptual design, detailed development, production and manufacturing, operation and maintenance, and decommissioning. Among them, in the digital transformation process of system design, the connection between system design and system simulation is an important link. Through the connection between system design and system simulation, efficient and seamless transmission from the design end to the simulation end can be achieved, thereby improving the iteration efficiency and accuracy of system design and shortening the system development cycle.

[0003] Patent publication number CN112989610A discloses a model-driven simulation verification method. The specific implementation steps of the method are as follows:

[0004] Step S1: construct a system design model including multiple perspective views, and obtain a metadata description specification of the system design model.

[0005] Step S2: defining a first transformation rule from the system function metamodel of the system design model to the simulation metamodel, and a second transformation rule from the state transition metamodel to the simulation rule metamodel.

[0006] Step S3: Process the first conversion rule and the second conversion rule based on a preset model to generate a first conversion rule template from a system function metamodel to a simulation metamodel, and a second conversion rule template from a state transition metamodel to a simulation rule metamodel.

[0007] Step S4: converting the input and output models based on the first conversion rule template and the second conversion rule template to generate a dynamic simulation model library.

[0008] Existing technologies build system design models from multiple perspectives, define the rules for mapping system design models to system simulation models, and perform model conversion to convert system design models into system simulation models. However, the current method of connecting system design and system simulation is:

[0009] (1) It is difficult to support the integration of system design and multiple system simulation platforms

[0010] The existing design-simulation integration methods only support the integration of system design models to specified system simulation platforms. For other system simulation platforms, new system design-system simulation model converters need to be customized and developed, and the flexibility and adaptability of the conversion are relatively poor.

[0011] (2) It is difficult to support the conversion of system design models to simulation models described in multiple modeling languages

[0012] The existing design-simulation integration methods only support system design models built based on the UML modeling language, and are difficult to support system design models based on other general modeling languages ​​such as UPDM, SysML or specific domain modeling languages. The universality of design-simulation integration is relatively poor, and it is difficult to support design-simulation integration described in multi-domain heterogeneous modeling languages. Summary of the invention

[0013] In view of this, the present invention provides a method for supporting the integration of complex equipment system design and simulation, which can support the integration of system design and multiple system simulation platforms, and the conversion of system design models to simulation models described in multiple modeling languages.

[0014] In order to solve the above technical problems, the present invention is implemented as follows.

[0015] A method for supporting the design and simulation of complex equipment systems, including:

[0016] Step S1: Construct a metamodel library of a complex equipment system based on the KARMA language; KARMA language is a text-based system modeling language that can support the description of the MBSE modeling language by constructing a metamodel library, thereby supporting the construction of a full life cycle model of system requirements, design, analysis, verification and validation. In this metamodel library, the graphic metamodels include: system equipment composition graphic metamodel, functional state transition graphic metamodel, simulation process diagram metamodel; the object metamodels include: system object metamodel, equipment object metamodel, functional state object metamodel, behavior action object metamodel;

[0017] And design two forms: mission analysis form and equipment parameter form;

[0018] Step S2: Based on the mission information, system equipment composition information, function state conversion information of each equipment in the system, and system simulation process information in the complex equipment system, the meta-model library is used to construct a system equipment composition model, an equipment function state conversion model, and a simulation process model of the complex equipment system; and two forms are used to construct a mission analysis model and an equipment parameter model of the complex equipment system;

[0019] Step S3: The user formulates code generation rules by writing a code generation script. According to the code generation rules, the model generated in step S2 is used as the source model, information is extracted from it and filled into the corresponding placeholders in the predetermined configuration file template, and the configuration file code required for the simulation deduction is generated, including a simulation evaluation target configuration file, a simulation behavior configuration file, a simulation environment configuration file, and an equipment parameter configuration file;

[0020] Step S4: The simulation configuration file code is directly or after parsing and conversion imported into the simulation deduction platform to perform deduction and evaluation on the designed simulation scenario.

[0021] Preferably, in the metamodel library of the complex equipment system based on the KARMA language constructed in step S1:

[0022] (1) The graphic element model includes: system equipment composition graphic element model, equipment function state conversion graphic element model, and simulation process graphic element model;

[0023] The system equipment composition graph metamodel is used to construct the system equipment composition module, which is used to describe the equipment set contained in the system; the configuration object metamodel includes the system object metamodel and the equipment object metamodel; the configuration relationship metamodel includes the inclusion relationship metamodel;

[0024] The function state transition graph metamodel is used to construct the equipment function state transition model, describing the function state and transition relationship of each equipment; the configuration object metamodel includes the function state object metamodel, the start object metamodel, and the end object metamodel; the configuration relationship metamodel includes the transition metamodel;

[0025] The simulation process graph metamodel is used to build the simulation process model and describe the system simulation behavior; the configuration relation metamodel includes the sequence flow metamodel;

[0026] (2) Object metamodels include: system object metamodel, equipment object metamodel, function state object metamodel, start object metamodel, end object metamodel, and behavior action object metamodel;

[0027] (3) The relational metamodel includes: relational metamodel, transformation relational metamodel, and sequence flow relational metamodel; the relational metamodel describes the component relationship between the system and the equipment, the transformation relational metamodel is used to describe the sequential relationship between the functional states of the equipment, and the sequence flow relational metamodel is used to describe the sequential relationship between behavioral actions.

[0028] Preferably, the header of the mission task analysis form includes: mission task name, simulation scenario task name, simulation scenario task effectiveness measurement value;

[0029] The header of the equipment parameter form includes: equipment name, equipment type, equipment attributes, and equipment quantity.

[0030] Preferably, in step S2, the construction of the system equipment composition model includes:

[0031] Construct system objects according to mission tasks;

[0032] According to the equipment information involved in the system design process, the equipment object metamodel is used to describe the equipment objects contained in the system;

[0033] According to the composition relationship between the system and equipment, the relational metamodel is used to describe the inclusion relationship between the two.

[0034] Preferably, in step S2, the equipment function state transition model is constructed as follows:

[0035] For each equipment, the start object is constructed based on the start object metamodel; the end object is constructed based on the end object metamodel; the equipment's various stage states are constructed based on the state transition object metamodel; the conversion relationship between the equipment's functional states is constructed based on the conversion relationship metamodel, and the start object, each state object and the end object are connected in sequence.

[0036] Preferably, in step S2, the simulation process model is constructed as follows: based on the start object metamodel, a start object is constructed; based on the end object metamodel, an end object is constructed; based on the behavior action object metamodel, each behavior action object in the simulation process is constructed; based on the sequence flow relationship metamodel, a sequence flow relationship is constructed, and the start object, each behavior action object and the end object are connected in sequence.

[0037] Preferably, in step S2, the mission task analysis model is constructed by: inputting relevant information of the mission task under each header in the mission task analysis form.

[0038] Preferably, in step S2, the equipment parameter model is constructed by: constructing the equipment parameter model based on the equipment parameter table, and filling in the information of each equipment in turn according to each table header.

[0039] Preferably, in step S3, the code generation rules include conversion source, conversion template, and character holder information;

[0040] The conversion source declares the code generation source model and the metamodel information of the object to be extracted;

[0041] The conversion template is a configuration file template, which declares the format of the output configuration file code and the placeholders therein;

[0042] The placeholder information declares the information source of the placeholder filled in the conversion template, and the information source is the column information of the form or the local name or attribute information of the object.

[0043] The present invention also provides a device for supporting the design and simulation connection of a complex equipment system, including a metamodel construction module, a model construction module, a code generation module, and a connection module;

[0044] The metamodel building module is used to build a metamodel library of a complex equipment system based on the KARMA language, and to design two forms; in the metamodel library, the graphic metamodel includes: a system equipment composition graphic metamodel, a functional state transition graphic metamodel, and a simulation flow chart metamodel; the object metamodel includes: a system object metamodel, an equipment object metamodel, a functional state object metamodel, and a behavior action object metamodel; the two forms include: a mission task analysis form and an equipment parameter form;

[0045] The model building module is used to build a system equipment composition model, equipment function state transition model, and simulation process model of a complex equipment system based on the mission information, system equipment composition information, function state transition information of each equipment in the system, and system simulation process information in a complex equipment system; and to build a mission task analysis model and an equipment parameter model of a complex equipment system using the metamodel library;

[0046] The code generation module is used to receive the user's input, determine the code generation rules according to the generated script code written by the user, and according to the code generation rules, take the model generated by the model construction module as the source model, extract information from it and fill it into the corresponding placeholder in the predetermined configuration file template to generate the configuration file code required for the simulation deduction, including the simulation evaluation target configuration file, the simulation behavior configuration file, the simulation environment configuration file, and the equipment parameter configuration file;

[0047] The through module is used to import the simulation configuration file code generated by the code generation module into the simulation deduction platform directly or after parsing and conversion, and to perform deduction and evaluation on the designed simulation scenario.

[0048] Beneficial effects:

[0049] (1) The system design and system simulation integration method of the present invention adopts code generation technology, which supports the conversion of system models described in multiple modeling languages ​​such as UML, UPDM, and SysML or in specific domain modeling languages ​​of complex equipment systems into target codes. Therefore, the flexibility and adaptability of model conversion are relatively strong.

[0050] (2) The data traceability of the system design and system simulation connection method of the present invention is relatively strong. The code generation technology can realize the automatic or semi-automatic conversion of the system model to other heterogeneous data files. When the engineer modifies or adjusts the system model, he only needs to re-execute the code generation rules to generate a new simulation configuration file, which reduces the time for reconfiguring the design simulation connection rules and greatly improves the efficiency of the design simulation connection.

[0051] (3) The system design and system simulation integration method of the present invention can realize the integration of system models and multiple system simulation platforms. Engineers standardize the code generation process by formulating text-based code generation rules. The templates in these rules can be customized according to the different target simulation platforms to meet different needs. Since the simulation configuration files of various system simulation platforms have different formats, the code generation technology of the present invention can meet the needs of different system design platforms by flexibly formulating templates, thereby supporting the generation of simulation configuration files required by various system simulation platforms and achieving wider compatibility and applicability. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] Figure 1 A method flow chart of a method and apparatus for supporting the integration of complex equipment system design and simulation.

[0053] Figure 2 A schematic diagram of the method framework for methods and devices to support the integration of complex equipment system design and simulation.

[0054] Figure 3 Schematic diagram of code generation rules for target profiles for simulation evaluation.

[0055] Figure 4 Schematic diagram of the target profile code for simulation evaluation.

[0056] Figure 5 Schematic diagram of code generation rules for simulation behavior profiles.

[0057] Figure 6 Schematic diagram of the configuration file code for simulation behavior.

[0058] Figure 7 Schematic diagram of code generation rules for configuring files for the simulation environment.

[0059] Figure 8 Schematic diagram of the simulation environment configuration file code.

[0060] Fig. 9 Schematic diagram of code generation rules for equipment parameter configuration files.

[0061] Fig.10 This is a code diagram of the equipment parameter configuration file. DETAILED DESCRIPTION

[0062] The present invention is described in detail below with reference to the accompanying drawings and embodiments.

[0063] like Figure 1-Figure 2 As shown, the present invention proposes a method for supporting the design and simulation of complex equipment systems, comprising the following steps:

[0064] Step S1: Use the multi-architecture modeling platform to build a metamodel library of the complex equipment system based on the KARMA language. The metamodel library contains six types of metamodels: graph metamodel, object metamodel, relationship metamodel, point metamodel, attribute metamodel and role metamodel.

[0065] (1) The graphic element model includes: system equipment composition graphic element model, function state transition graphic element model, and simulation process graphic element model;

[0066] ① System equipment composition graph metamodel: ID is "TX_Construct", used to build the system equipment composition model, describe the equipment set included in this system, configuration object metamodel includes: system object metamodel, equipment object metamodel, configuration relationship metamodel includes inclusion relationship metamodel, configuration attribute metamodel includes: none, configuration inclusion relationship start end can be connected to system object metamodel, configuration inclusion relationship end end can be connected to equipment object metamodel;

[0067] ② Functional state conversion primitive model: Its ID is “TX_FunctionExchange”, which is used to construct the equipment functional state conversion model and describe the functional states and conversion relationships of each equipment.

[0068] The configuration object metamodel includes: function state object metamodel, start object metamodel, end object metamodel;

[0069] The configuration relational metamodel includes a transformation metamodel;

[0070] Configuration property metamodels include: None;

[0071] The configuration conversion relationship start end can connect the function state object metamodel and the start object metamodel;

[0072] The configuration transition relationship terminal can connect the functional state object metamodel and the end object metamodel.

[0073] ③Simulation process diagram meta-model: Its ID is “TX_ActivityDiagram”, which is used to build the simulation process model and describe the system simulation behavior.

[0074] The configuration object metamodel includes: behavior action object metamodel, start object metamodel, and end object metamodel;

[0075] The configuration relational metamodel includes the sequence flow metamodel;

[0076] Configuration property metamodels include: None;

[0077] The beginning of the sequence flow relationship can be configured to connect the behavior action object metamodel and the start object metamodel;

[0078] Configuring sequence flow relationship terminals can connect behavior action object metamodel and end object metamodel.

[0079] (2) Object metamodels include: system object metamodel, equipment object metamodel, function state object metamodel, start object metamodel, end object metamodel, behavior action object metamodel

[0080] ① System object metamodel: ID is "TIXI", which is used to describe the system in the system equipment composition and its related characteristics;

[0081] The configuration style is "Rounded Rectangle";

[0082] The configuration attribute metamodel includes: name attribute metamodel;

[0083] Set the color to "Default".

[0084] ② Equipment object metamodel: ID is "ZB", used to describe the equipment in the system equipment composition and its related characteristics;

[0085] The configuration style is "Rounded Rectangle";

[0086] The configuration attribute metamodel includes: name attribute metamodel;

[0087] Set the color to "Default".

[0088] ③ Functional state object metamodel: Its ID is "ZT", which is used to describe the functional state and its related characteristics in the equipment functional state transition model;

[0089] The configuration style is "Rounded Rectangle";

[0090] The configuration attribute metamodel includes: name attribute metamodel;

[0091] Set the color to "Default".

[0092] ④ Start object metamodel: ID is "start", used for the start state and its related characteristics in the equipment function state transition model;

[0093] The configuration style is "circular";

[0094] Configuration property metamodels include: None;

[0095] Set the color to "Default".

[0096] ⑤ End object metamodel: ID is "end", used for the end state and its related characteristics in the equipment function state transition model;

[0097] The configuration style is "circular";

[0098] Configuration property metamodels include: None;

[0099] Set the color to "Default".

[0100] ⑥Behavior action object metamodel: ID is "XWDZ", which is used to simulate the behavior actions and related characteristics in the behavior model;

[0101] The configuration style is "Rounded Rectangle";

[0102] The configuration attribute metamodel includes: name attribute metamodel and executor attribute metamodel;

[0103] Set the color to "Default".

[0104] (3) Relational metamodels include: inclusion relational metamodel, transformation relational metamodel, and sequence flow relational metamodel.

[0105] ① Inclusion relationship metamodel: used to describe the composition relationship between systems and equipment;

[0106] The beginning of the containment relationship is bound to the system object, and the end of the containment relationship is bound to the device object;

[0107] Configuration property metamodels include: None;

[0108] Configure the start-end role to include the start-end role metamodel;

[0109] Configure the terminal to contain the terminal role metamodel;

[0110] The configuration style is "bold straight line".

[0111] ② Transformation relationship metamodel: used to describe the sequential relationship between functional states;

[0112] The beginning of the conversion relationship is bound to the previous functional state object, and the end of the conversion relationship is bound to the next functional state object;

[0113] Configuration property metamodels include: None;

[0114] Configure the start-end role as the transformation start-end role metamodel;

[0115] Configure the terminal to transform the terminal role metamodel;

[0116] The configuration style is "bold straight line".

[0117] ③ Sequential flow relational metamodel: used to describe the sequential relationship between behavioral actions;

[0118] The beginning of the conversion relationship is bound to the previous action object, and the end of the conversion relationship is bound to the next action object;

[0119] Configuration property metamodels include: None;

[0120] Configure the start role as the sequence flow start role metamodel;

[0121] Configure the terminal as the sequence flow terminal role metamodel;

[0122] The configuration style is "bold straight line".

[0123] (4) Attribute metamodel includes: name attribute metamodel, executor attribute metamodel

[0124] ① Name attribute metamodel: used to describe the names of the system object metamodel, equipment object metamodel, state transition object metamodel, and behavior action object metamodel. The attribute value type is configured as String type, and the unit is configured as "None";

[0125] ②Actuator attribute metamodel: used to describe the executor of the action. The attribute value type is configured as String type and the unit is configured as "None".

[0126] (5) The point meta-model is none.

[0127] (6) The role metamodel includes: inclusion start role metamodel, inclusion end role metamodel, conversion start role metamodel, conversion end role metamodel, sequence flow start role metamodel, sequence flow end role metamodel;

[0128] ① Included start role metamodel: used to bind the included start;

[0129] The direction of the configuration containing the start role metamodel is "start" and the style is "arrow";

[0130] ② and the included terminal role metamodel: used to bind the included terminals;

[0131] The configuration includes the terminal role metamodel with the direction of "terminal" and the style of "diamond";

[0132] ③ Transformation start role metamodel: used to bind the start of the transformation;

[0133] Configure the direction of the transformation start role metamodel to "start" and the style to "arrow";

[0134] ④Conversion terminal role metamodel: used to bind the terminal for conversion, and configure the direction of the conversion terminal role metamodel to "terminal" and the style to "diamond";

[0135] ⑤ Sequence flow start role metamodel: used to bind the start of the sequence flow, and configure the direction of the sequence flow start role metamodel to be "start" and the style to be "arrow";

[0136] ⑥ Sequence flow terminal role metamodel: used to bind the terminal of the sequence flow. The direction of the sequence flow terminal role metamodel is configured as "terminal" and the style is "diamond" style.

[0137] This step also designs two forms: mission analysis form and equipment parameter form.

[0138] The header of the mission task analysis form includes: mission task name, simulation scenario task name, and simulation scenario task effectiveness measurement value.

[0139] The header of the equipment parameter form includes: equipment name, equipment type, equipment attributes, and equipment quantity.

[0140] Step S2: Based on the mission information, system equipment composition information, functional state transition information of each equipment in the system, and system simulation process information in the complex equipment system, the metamodel in the metamodel library and the two designed forms are dragged in the multi-architecture modeling platform to respectively construct the mission analysis model, system equipment composition model, equipment functional state transition model, simulation process model, and equipment parameter model of the complex equipment system.

[0141] The following is the construction process of each part of the model:

[0142] (1) The process of building the mission task analysis model is as follows: the ID is set to "TableForTask";

[0143] In the "Mission Name" column of the mission task analysis form, enter "Quickly implement urban emergency rescue" and the simulation scenario task name is: "Quick rescue in large-scale chemical leakage accident scenarios"; the simulation scenario task effectiveness measurement value is "rescue range greater than or equal to 10km, rescue time less than or equal to 30min".

[0144] (2) The process of building the system equipment composition model is as follows: ID is set to “ZBContain”;

[0145] ● Based on the system object metamodel in the metamodel library, construct the system object (name attribute value is the urban multi-mode rescue transportation system) according to the mission task;

[0146] ●Based on the equipment object metamodel in the metamodel library, according to the equipment information involved in the system design process, the equipment object metamodel is used to describe the equipment objects contained in the system to realize equipment object construction, including: Type A rescue aircraft (the name attribute value is Type A rescue aircraft), Type B rescue aircraft (the name attribute value is Type B rescue aircraft), Type C rescue aircraft (the name attribute value is Type C rescue aircraft), Type A rescue car (the name attribute value is Type A rescue car), Type B rescue car (the name attribute value is Type B rescue car), Type C rescue car (the name attribute value is Type C rescue car), scheduling decision-making equipment (the name attribute value is scheduling decision-making equipment), and rescue headquarters (the name attribute value is rescue headquarters).

[0147] ●Based on the inclusion relationship metamodel in the metamodel library, according to the composition relationship between the system and the equipment, the relationship metamodel is used to describe the inclusion relationship between the two, and the inclusion relationship construction is realized: this example constructs seven inclusion relationships. The first inclusion relationship starts with the connection: the urban multimodal rescue transportation system object, and the terminal connects the type A rescue aircraft object. The second inclusion relationship starts with the connection: the urban multimodal rescue transportation system object, and the terminal connects the type B rescue aircraft object. The third inclusion relationship starts with the connection: the urban multimodal rescue transportation system object, and the terminal connects the type C rescue aircraft object. The fourth inclusion relationship starts with the connection: the urban multimodal rescue transportation system object, and the terminal connects the type A rescue car object. The fifth inclusion relationship starts with the connection: the urban multimodal rescue transportation system object, and the terminal connects the type B rescue car object. The sixth inclusion relationship starts with the connection: the urban multimodal rescue transportation system object, and the terminal connects the type C rescue car object. The sixth inclusion relationship starts with the connection: the urban multimodal rescue transportation system object, and the terminal connects the dispatch decision-making equipment object. The seventh inclusion relationship starts with the connection: the urban multimodal rescue transportation system object, and the terminal connects the rescue command center object.

[0148] (3) The process of constructing the equipment function state conversion model is to perform the following operations for each piece of equipment:

[0149] The ID is set to "ModelForZB1". The functional state transition model of type A rescue aircraft builds the start object based on the start object metamodel; builds the end object based on the end object metamodel; builds the standby state (the name attribute is set to the standby state) and flight state (the name attribute is set to the flight state) based on the state transition object metamodel; builds the transition relationship between the functional states based on the transition relationship metamodel, and connects the start, standby state, flight state, and end in sequence.

[0150] The ID is set to "ModelForZB2". The functional state transition model of type B rescue aircraft builds the start object based on the start object metamodel; builds the end object based on the end object metamodel; builds the standby state (the name attribute is set to the standby state), flight state (the name attribute is set to the standby state), and air monitoring state (the name attribute is set to the air monitoring state) based on the state transition object metamodel; builds the transition relationship between the functional states based on the transition relationship metamodel, and connects the start, standby state, flight state, air monitoring state, and end in sequence.

[0151] The ID is set to "ModelForZB3". The functional state transition model of the C-type rescue aircraft builds the start object based on the start object metamodel; builds the end object based on the end object metamodel; builds the standby state (the name attribute is set to the standby state), flight state (the name attribute is set to the standby state), and broadcast notification state (the name attribute is set to the air monitoring state) based on the state transition object metamodel; builds the transition relationship between the functional states based on the transition relationship metamodel, and connects the start, standby state, flight state, broadcast notification state, and end in sequence.

[0152] The ID is set to "ModelForZB4". The functional state transition model of Type A rescue vehicle builds the start object based on the start object metamodel; builds the end object based on the end object metamodel; builds the standby state (the name attribute is set to the standby state), running state (the name attribute is set to the standby state), and working state (the name attribute is set to the working state) based on the state transition object metamodel; builds the transition relationship between the functional states based on the transition relationship metamodel, and connects the start, standby state, flight state, working state, and end in sequence.

[0153] The ID is set to "ModelForZB5". The functional state transition model of type B rescue vehicle constructs the start object based on the start object metamodel; constructs the end object based on the end object metamodel; constructs the standby state (the name attribute is set to the standby state), the running state (the name attribute is set to the standby state), and the monitoring state (the name attribute is set to the operating state) based on the state transition object metamodel; constructs the transition relationship between the functional states based on the transition relationship metamodel, and connects the start, standby state, flight state, monitoring state, and end in sequence.

[0154] The ID is set to "ModelForZB6". The functional state transition model of the C-type rescue vehicle constructs the start object based on the start object metamodel; constructs the end object based on the end object metamodel; constructs the standby state (the name attribute is set to the standby state), the running state (the name attribute is set to the standby state), and the evacuation guidance state (the name attribute is set to the operating state) based on the state transition object metamodel; constructs the transition relationship between the functional states based on the transition relationship metamodel, and connects the start, standby state, flight state, evacuation guidance state, and end in sequence.

[0155] (4) The simulation process model construction process is: ID is set to "ModelForXW";

[0156] ●Build the start object based on the start object metamodel in the metamodel library;

[0157] ●Build the end object based on the end object metamodel in the metamodel library;

[0158] ● Based on the behavior state object metamodel in the metamodel library, construct various behavior action objects in the simulation process, including: receiving emergency calls (the name attribute value is receiving emergency calls, and the executor attribute value is scheduling decision-making equipment), decision-making and evaluation (the name attribute value is decision-making and evaluation, and the executor attribute value is scheduling decision-making equipment), resource scheduling and allocation (the name attribute value is resource scheduling and allocation, and the executor attribute value is scheduling decision-making equipment), transporting advanced chemical handling experts and equipment to the scene (the name attribute value is transporting advanced chemical handling experts and equipment to the scene, and the executor attribute value is type A rescue aircraft), air monitoring and evaluation of leakage (the name attribute value is air monitoring and evaluation of leakage, and the executor attribute value is type B rescue aircraft), and quickly transferring seriously injured and seriously poisoned people to the city's medical center ( The name attribute value is quickly transferring seriously injured and severely poisoned people to the city’s medical center, and the executor attribute value is Type B rescue aircraft), large-scale evacuation of affected residents (the name attribute value is large-scale evacuation of affected residents, and the executor attribute value is Type C rescue aircraft), ground rescue and preliminary chemical treatment (the name attribute value is ground rescue and preliminary chemical treatment, and the executor attribute value is Type A rescue car), ground monitoring and rescue (the name attribute value is ground monitoring and rescue, and the executor attribute value is Type B rescue car), transporting lightly injured and poisoned people to nearby hospitals (the name attribute value is transporting lightly injured and poisoned people to nearby hospitals, and the executor attribute value is Type B rescue car), and evacuating affected residents to safe areas (the name attribute value is evacuating affected residents to safe areas, and the executor attribute value is Type C rescue car).

[0159] ●Based on the sequential flow relation metamodel, construct a sequential flow relation, and connect the start object, each behavior action object and the end object in sequence, that is, connect the start, receiving emergency calls, decision-making and evaluation, resource scheduling and allocation, transportation of senior chemical handling experts and equipment to the scene, aerial monitoring and assessment of leakage, rapid transfer of seriously injured and seriously poisoned people to the city’s medical center, large-scale evacuation of affected residents, ground rescue and preliminary chemical treatment, ground monitoring and rescue, transportation of lightly injured and poisoned people to nearby hospitals, evacuation of affected residents to safe areas, and end in sequence.

[0160] (5) The equipment parameter model construction process is: ID is set to "TableForZBSX";

[0161] Based on the equipment parameter table, construct an equipment parameter model and fill in the following information in the table header: equipment name, equipment type, equipment attribute, and equipment quantity: {Type A rescue aircraft; aircraft; maximum speed: 800km / h, load capacity: 5 tons, range: 1500km; 1}, {Type B rescue aircraft; aircraft; maximum speed: 750km / h, load capacity: 10 tons, range: 1200km; 1}, {Type C rescue aircraft; aircraft; maximum speed: 700km / h, load capacity: 15 tons, range: 1000km; 1}, {Type A rescue vehicle; vehicle; maximum speed: 120km / h, load capacity: 2 tons, equipment: basic first aid equipment; 1}, {Type B rescue vehicle ... B rescue vehicle; aircraft; maximum speed: 750km / h, load capacity: 10 tons, range: 1200km; 1}, {Type C rescue aircraft

[0162] ; Car; Maximum speed: 110km / h, Loading capacity: 3 tons, Equipment: Advanced first aid equipment; 1}, {Type C rescue car; Car; Maximum speed: 100km / h, Loading capacity: 4 tons, Equipment: Comprehensive first aid and monitoring system; 1}.

[0163] Step S3: Based on the code automatic generation method and the script templates corresponding to the various meta-model instances used for the simulation deduction, the configuration file code required for the simulation deduction is generated, including four types of simulation configuration files: simulation evaluation target configuration file (in XML format), simulation behavior configuration file (in SCN format), simulation environment configuration file (in OPD format), and equipment parameter configuration file (XML). Among them, the user formulates the code generation rules by writing a code generation script, and takes the model generated in step S2 as the source model. The code generation method is to extract the information of the specified position from the source model according to the code generation rules and fill it into the corresponding placeholder in the predetermined template, generate the configuration file code required for the simulation deduction, and then output it.

[0164] The code generation rules include three parts: conversion source, conversion template, and placeholder information. The conversion source declares the code generation source model and the metamodel information of the object to be extracted in the source model, the conversion template declares the format of the output configuration file code and the placeholders therein, and the placeholder information declares the information source of the placeholders filled in the conversion template.

[0165] In this case, if Figure 3 The following is a simulation evaluation target configuration file code generation script, where "fromObject[Object_Table]obj2; in Model[TableForTask]model1;" is the conversion source part, which declares that the source model is the model with ID "TableForTask" and the object source is the "Object_Table" object. "TemplategeneJulia2(ann,bnn)=<% <scene> <name> <ann>< / ann> < / name> <target> <bnn>< / bnn> < / target> < / scene> %>" is the conversion template part, which declares the template as " <scene> <name> <ann>< / ann> < / name> <target> <bnn>< / bnn> < / target> < / scene> ”, which contains <ann> , <bnn>Placeholder. "e<-geneJulia2(obj2.Property["Simulation scenario task"],obj2.Property["Simulation scenario task effectiveness measurement value"]);" is the placeholder information part, which declares the information source of the placeholder in the template. In this example, <ann>The source of information is the "Simulation Scenario Task" attribute of each entry in the form. <bnn>The source of information is the "Simulation Scenario Task Effectiveness Metric" attribute of each entry in the form. Execute the simulation and obtain the following Figure 4 The simulation evaluation target configuration file shown.

[0166] In this case, if Figure 5 The following is a simulation behavior configuration file code generation script, where "from Object[XWDZ]obj2; in Model[ModelForXW]model1;" is the conversion source part, which declares that the source model is the model with ID "ModelForXW" and the object source is the "XWDZ" object. "Template geneJulia2(ann,bnn)=<% <action> <name> <ann>< / ann> < / name> <executor> <bnn>< / bnn> < / executor> <team> 0< / team> <Ra darPower>1< / action> %>" is the conversion template part, which declares the template as " <action> <name> <ann>< / ann> < / name> <executor> <bnn>< / bnn> < / executor> <team> 0< / team> <radarpower> 1< / radarpower> < / action> ”, which contains <ann> , <bnn>Placeholder. "e<-geneJulia2(obj2.Property["name"],obj2.Property["executor"]);" is the placeholder information part, which declares the source of the placeholder information in the template. In this example, <ann>The source of information is the "name" attribute of the object whose object metamodel is "XWDZ" in the model. <bnn>The source of information is the "executor" attribute of the object with the object metamodel "XWDZ". Execute the simulation and get the following Figure 6 The simulation evaluation target configuration file shown.

[0167] In this case, if Figure 7 The following is a simulation environment configuration file code generation script, which contains seven rules. The second to sixth rules have similar formats and methods, so only the first and second rules are introduced. The first rule: The rule name is "generateJulia1", where "from Object[ZB]obj2; in Model[ZBContain]model1;" is the conversion source part, which declares that the source model is the model with ID "ZBContain" and the object source is the "ZB" object. "TemplategeneJulia1(ann)=<% <equirementtypes> <equirementtype> <ann>< / ann> < / equirementtype> < / equirementTy pes> %>" is the conversion template part, which declares the template as " <equirementtypes> <equirementtype> <ann>< / ann> < / equirementtype> < / equirementType s> ”, which contains <ann>Placeholder. "e<-geneJulia2(obj2.Property["name"]);" is the placeholder information part, which declares the source of the placeholder information in the template. In this example, <ann>The source of information is the "name" attribute of the object whose object metamodel is "ZB" in the model. Execute the simulation and get the following Figure 8 The simulation evaluation target configuration file is shown. The second rule: The rule name is "generateJulia2" where "from Object[ZT]obj2; in Model[ModelForZB1]model1;" is the conversion source part, which declares that the source model is the model with ID "ModelForXW" and the object source is the "ZT" object. "TemplategeneJulia2(ann)=<% <equipment> <name> Type A rescue aircraft< / name> <statuses> <status> <ann>< / ann> < / status> < / statuses> < / equipment> %>" is the conversion template part, which declares the template as " <equipment> <name> Type A rescue aircraft< / name> <statuses> <status> <ann>< / ann> < / status> < / statuses> < / equipment> ”, which contains <ann>Placeholder. "e<-geneJulia2(obj2.Property["name"]);" is the placeholder information part, which declares the source of the placeholder information in the template. In this example, <ann>The source of information is the "name" attribute of the object whose object metamodel is "ZT" in the model. Execute the simulation and get the following Figure 8 The simulation evaluation target configuration file shown.

[0168] In this case, if Fig. 9 The following is a code generation script for the equipment parameter configuration file, where "from Object[ZBSX]obj2;in Model[TableForZBSX]model1;" is the conversion source part, which declares that the source model is the model with ID "TableForTask" and the object source is the "ZBSX" object. "Template geneJulia2(ann,bnn,cnn,dnn)=<% <equirement> <name> <ann>< / ann> < / name> <type> <bnn>< / bnn> < / type> <property> <cnn>< / cnn> < / property> <number> <dnn>< / dnn> < / number> < / equirement> %>" is the conversion template part, which declares the template as " <equirement> <name> <ann>< / ann> < / name> <type> <bnn>< / bnn> < / type> <property> <cnn>< / pro perty> <number> <dnn>< / dnn> < / number> < / cnn> < / property> < / equirement> ”, which contains <ann> , <bnn> , <cnn> , <dnn>Placeholder. "e<-geneJulia2(obj2.Property["Equipment Name"],obj2.Property["Equipment Type"],obj2.Property["Equipment Attribute"],obj2.Property["Equipment Quantity"]);" is the placeholder information part, which declares the information source of the placeholder in the template. In this example, <ann>The source of information is the "Equipment Name" attribute of each entry in the form. <bnn>The source of information is the "equipment type" attribute of each entry in the form. <cnn>The source of information is the "Equipment Attributes" attribute of each item in the form. <dnn>The source of information is the "equipment quantity" attribute of each item in the table. Execute the simulation and get the following Fig.10 The simulation evaluation target configuration file shown.

[0169] Step S4: Based on the generated simulation configuration file code, the simulation evaluation target configuration file and the equipment configuration file need to be parsed and converted by the simulation deduction platform engineer before use, and the simulation behavior configuration file and the simulation environment configuration file can be directly input into the platform to support simulation execution. The simulation configuration file is imported into the relevant simulation deduction platform to perform deduction and evaluation on the designed simulation scenario.

[0170] This is the end of the process.

[0171] Based on the above method, the present invention also provides a device that supports the design and simulation of complex equipment systems, such as Figure 2 As shown, it includes a metamodel building module, a model building module, a code generation module, and a through module;

[0172] The metamodel construction module is used to construct a metamodel library of a complex equipment system based on the KARMA language and design two forms; in the metamodel library, the graphic metamodel includes: system equipment composition graphic metamodel, function state conversion graphic metamodel, simulation flow chart metamodel; the object metamodel includes: system object metamodel, equipment object metamodel, function state object metamodel, behavior action object metamodel; the two forms include: mission task analysis form and equipment parameter form. The specific metamodel library and form content refer to the above step S1.

[0173] The model building module is used to build the system equipment composition model, equipment function state transition model, and simulation process model of the complex equipment system based on the mission information, system equipment composition information, function state transition information of each equipment in the system, and system simulation process information of the complex equipment system; and to build the mission task analysis model and equipment parameter model of the complex equipment system using the two forms. For the specific model building method, see step S2 above.

[0174] The code generation module is used to receive the user's input, determine the code generation rules according to the generated script code written by the user, and according to the code generation rules, take the model generated by the model building module as the source model, extract information from it and fill it into the corresponding placeholder in the predetermined configuration file template to generate the configuration file code required for the simulation deduction, including the simulation evaluation target configuration file, the simulation behavior configuration file, the simulation environment configuration file, and the equipment parameter configuration file. Figure 2 The code generation module includes a script editing module for users to input and generate script codes; the matching module matches the required source models and objects in the model generated by the model construction module according to the code generation rules; the conversion module is responsible for filling the matching information into the corresponding placeholders in the predetermined configuration file template (i.e., the conversion template), generating the configuration file code required for the simulation deduction, and completing the conversion.

[0175] The through module is used to import the simulation configuration file code generated by the code generation module directly or through parsing and conversion into the simulation deduction platform to perform deduction and evaluation on the designed simulation scenario.

[0176] The above specific embodiments only describe the design principle of the present invention. The shapes and names of the components in the description may be different and are not limited. Therefore, those skilled in the art in the field of the present invention may modify or replace the technical solutions recorded in the above embodiments; and these modifications and replacements do not deviate from the creative purpose and technical solutions of the present invention and should all fall within the protection scope of the present invention.< / dnn> < / cnn> < / bnn> < / ann> < / dnn> < / cnn> < / bnn> < / ann> < / ann> < / ann> < / ann> < / ann> < / equirementtypes> < / equirementtypes> < / bnn> < / ann> < / bnn> < / ann> < / bnn> < / ann> < / bnn> < / ann>

Claims

1. A method for supporting the design and simulation of complex equipment systems, characterized in that: include: Step S1: construct a meta-model library of complex equipment system based on KARMA language; In this metamodel library, the graph metamodels include: system equipment composition graph metamodel, function state transition graph metamodel, simulation flow graph metamodel; the object metamodels include: system object metamodel, equipment object metamodel, function state object metamodel, behavior action object metamodel; And design two forms: mission analysis form and equipment parameter form; Step S2: Based on the mission information, system equipment composition information, function state conversion information of each equipment in the system, and system simulation process information in the complex equipment system, the meta-model library is used to construct a system equipment composition model, an equipment function state conversion model, and a simulation process model of the complex equipment system; and two forms are used to construct a mission analysis model and an equipment parameter model of the complex equipment system; Step S3: The user formulates code generation rules by writing a code generation script. According to the code generation rules, the model generated in step S2 is used as the source model, information is extracted from it and filled into the corresponding placeholders in the predetermined configuration file template, and the configuration file code required for the simulation deduction is generated, including a simulation evaluation target configuration file, a simulation behavior configuration file, a simulation environment configuration file, and an equipment parameter configuration file; Step S4: The simulation configuration file code is directly or after parsing and conversion imported into the simulation deduction platform to perform deduction and evaluation on the designed simulation scenario.

2. The method according to claim 1, characterized in that In the meta-model library of the complex equipment system based on the KARMA language constructed in step S1: (1) The graphic element model includes: system equipment composition graphic element model, equipment function state conversion graphic element model, and simulation process graphic element model; The system equipment composition graph metamodel is used to construct the system equipment composition module, which is used to describe the equipment set contained in the system; the configuration object metamodel includes the system object metamodel and the equipment object metamodel; the configuration relationship metamodel includes the inclusion relationship metamodel; The function state transition graph metamodel is used to construct the equipment function state transition model, describing the function state and transition relationship of each equipment; the configuration object metamodel includes the function state object metamodel, the start object metamodel, and the end object metamodel; the configuration relationship metamodel includes the transition metamodel; The simulation process graph metamodel is used to build the simulation process model and describe the system simulation behavior; the configuration relation metamodel includes the sequence flow metamodel; (2) Object metamodels include: system object metamodel, equipment object metamodel, function state object metamodel, start object metamodel, end object metamodel, and behavior action object metamodel; (3) The relational metamodel includes: relational metamodel, transformation relational metamodel, and sequence flow relational metamodel; the relational metamodel describes the component relationship between the system and the equipment, the transformation relational metamodel is used to describe the sequential relationship between the functional states of the equipment, and the sequence flow relational metamodel is used to describe the sequential relationship between behavioral actions.

3. The method according to claim 1, characterized in that The header of the mission task analysis form includes: mission task name, simulation scenario task name, simulation scenario task effectiveness measurement value; The header of the equipment parameter form includes: equipment name, equipment type, equipment attributes, and equipment quantity.

4. The method according to claim 2, characterized in that In step S2, the construction of the system equipment composition model includes: Construct system objects according to mission tasks; According to the equipment information involved in the system design process, the equipment object metamodel is used to describe the equipment objects contained in the system; According to the composition relationship between the system and equipment, the relational metamodel is used to describe the inclusion relationship between the two.

5. The method according to claim 2, characterized in that In step S2, the equipment function state transition model is constructed as follows: For each equipment, a start object is constructed based on the start object metamodel; an end object is constructed based on the end object metamodel; Based on the state transition object metamodel, construct the states of each stage of the equipment; Based on the transformation relationship metamodel, the transformation relationship between the functional states of the equipment is constructed, and the start object, each state object and the end object are connected in sequence.

6. The method according to claim 2, characterized in that In step S2, the construction of the simulation process model is as follows: based on the start object metamodel, a start object is constructed; based on the end object metamodel, an end object is constructed; Based on the behavior action object metamodel, construct each behavior action object in the simulation process; based on the sequence flow relationship metamodel, construct the sequence flow relationship, and connect the start object, each behavior action object and the end object in sequence.

7. The method according to claim 3, characterized in that In step S2, the mission task analysis model is constructed by inputting the mission task related information under each table header in the mission task analysis form.

8. The method according to claim 3, characterized in that In step S2, the equipment parameter model is constructed by: constructing the equipment parameter model based on the equipment parameter table, and filling in the information of each equipment in turn according to each table header.

9. The method according to claim 3, characterized in that In step S3, the code generation rules include conversion source, conversion template, and character holder information; The conversion source declares the code generation source model and the metamodel information of the object to be extracted; The conversion template is a configuration file template, which declares the format of the output configuration file code and the placeholders therein; The placeholder information declares the information source of the placeholder filled in the conversion template, and the information source is the column information of the form or the local name or attribute information of the object.

10. A device supporting complex equipment system design and simulation, characterized in that: It includes meta-model building module, model building module, code generation module and connection module; The metamodel building module is used to build a metamodel library of a complex equipment system based on the KARMA language and design two forms; In the metamodel library, the graph metamodels include: system equipment composition graph metamodel, function state conversion graph metamodel, simulation process graph metamodel; the object metamodel includes: system object metamodel, equipment object metamodel, function state object metamodel, behavior action object metamodel; the two forms include: mission task analysis form and equipment parameter form; The model building module is used to build a system equipment composition model, equipment function state transition model, and simulation process model of a complex equipment system based on the mission information, system equipment composition information, function state transition information of each equipment in the system, and system simulation process information in a complex equipment system; and to build a mission task analysis model and an equipment parameter model of a complex equipment system using the metamodel library; The code generation module is used to receive the user's input, determine the code generation rules according to the generated script code written by the user, and according to the code generation rules, take the model generated by the model construction module as the source model, extract information from it and fill it into the corresponding placeholder in the predetermined configuration file template to generate the configuration file code required for the simulation deduction, including the simulation evaluation target configuration file, the simulation behavior configuration file, the simulation environment configuration file, and the equipment parameter configuration file; The through module is used to import the simulation configuration file code generated by the code generation module into the simulation deduction platform directly or after parsing and conversion, and to perform deduction and evaluation on the designed simulation scenario.

Citation Information

Cited By

  • Method for converting aircraft models constructed by different modeling methods

    CN119849218A

  • Ontology-based heterogeneous modeling language unified description method, device and equipment

    CN119990145A

  • Method and system for supporting aircraft undercarriage system modeling and closed loop verification

    CN120430021A