A management system for product bill of materials for virtualized prototypes

Abstract

The application discloses a kind of for the management system of product bill of materials of virtual prototype, comprising: recursive index module, for using recursive algorithm to describe the hierarchical and grouping relationship between product modules, form recursive system index data model for product;Recursive system index data model contains a series of pointers to product system engineering process data;Integrated interface module is used to describe the interface and interoperation relationship between adjacent product modules, and based on object model, software interface for interoperation between prototype products under virtualization environment is provided.The application makes the data generated in system engineering process form an organic whole, decomposes the system according to engineering habits, indexes all kinds of process data and controls its state, improves the interoperation of subsystem product data, test data and other data, fully utilizes all kinds of process data and result data, and guarantees the direct consistency of final product and system engineering process data.

Description

TECHNICAL FIELD

[0001] The application belongs to the technical field of system engineering, and particularly relates to a management system for product bill of materials of a virtual prototype. BACKGROUND

[0002] A product is the target of system engineering, and a bill of materials (BOM) is a technical document for defining the product, also known as a product structure table or product structure tree, and is used to assist a computer in managing the product. A traditional BOM is constructed around a CAD, CAE and other underlying application process, and utilizes CAD parts, combinations and other definitions for system decomposition, which often does not conform to the actual deployment mode of system engineering, resulting in difficulty in decoupling subsystems and complex and chaotic status of component attribution. Meanwhile, the traditional BOM takes CAD files as the core and is difficult to comprehensively manage product-related information such as CAE, software and test data. SUMMARY

[0003] The technical problem of the application is to overcome the deficiencies of the prior art, provide a management system for product bill of materials of a virtual prototype, form an organic whole of data generated in a system engineering process, decompose a system according to engineering habits, comprehensively index various process data and control the state thereof, improve the interoperability of subsystem product data, test data and other data, fully utilize various process data and result data, and guarantee the direct consistency of the final product and the system engineering process data.

[0004] To solve the above technical problem, the application discloses a management system for product bill of materials of a virtual prototype, comprising:

[0005] A recursive indexing module is configured to describe the hierarchical and grouping relationship between product modules by using a recursive algorithm, and form a recursive system indexing data model for the product; wherein the recursive system indexing data model contains a series of pointers to product system engineering process data;

[0006] An integrated interface module is configured to describe the interface and interoperability relationship between adjacent product modules, and provide a software interface for the interoperability between prototype products in a virtual environment based on an object model.

[0007] In the above management system for product bill of materials of a virtual prototype, in a process of carrying out product prototype virtualization test or verification based on the product bill of materials, the hierarchical and grouping relationship between product prototype modules is obtained from the recursive indexing module, the recursive indexing module points the interaction between product modules to the object model managed by the integrated interface module; the product prototype modules in the same group and at the same level have interaction interfaces; wherein the interaction includes mechanical information, thermal information and electromagnetic information.

[0008] In the above product bill of materials management system for virtualizing a prototype, the data structure of the recursive system index data model is a tree structure recursively described, comprising:

[0009] Root node S(0): representing the 0th level system division of the current product S;

[0010] Node S(N): the Nth level system division of the current product, i.e. subdividing the composition of the current product to the Nth level;

[0011] Node Si(N): the ith subsystem in the Nth level system division, belonging to the Nth level of the tree structure;

[0012] Node Sij(N+1): the jth submodule of the ith subsystem in the Nth level system division, belonging to the N+1th level of the tree structure.

[0013] In the above product bill of materials management system for virtualizing a prototype, the division of the subsystem or submodule follows engineering habits, and the subsystem or submodule can produce certain utility relatively independently in the system, which cooperates with the utility of other subsystems or submodules of the same level to make the system produce certain functional utility.

[0014] In the above product bill of materials management system for virtualizing a prototype, if the object set S(N) contains m different elements, and there is interaction between any two different elements Sa(N+1) and Sb(N+1) in the object set S(N), i.e. the utility produced by Sa(N+1) will cause an influence on Sb(N+1) that must be considered in engineering; then the object set S(N) is determined as an N-level system; wherein m>1 and m is an integer; a is less than m, b is less than m, and a and b are not equal.

[0015] In the above product bill of materials management system for virtualizing a prototype, the node Si(N) is a series of addresses pointing to the storage locations of different system engineering process data and object models.

[0016] In the above product bill of materials management system for virtualizing a prototype, the system engineering process data comprises product design results, product simulation analysis models and data, and test data.

[0017] In the above product bill of materials management system for virtualizing a prototype, the object model is a software interface description of Si(N) interacting with the outside, comprising a state interface and a method interface; wherein the state interface is a series of definitions of state variables, and the method interface is a function of the change rule of the state variables.

[0018] In the above product bill of materials management system for virtualizing a prototype,

[0019] State interface, used to define the physical or information variable that changes when Si(N) interacts with other N-level subsystems;

[0020] Method interface, used to define the algorithm of the state model variable change rule of Si(N) interacting with other N-level subsystems, the input of the algorithm is the state model variable value of the N-level subsystem related to the interaction at the virtualization starting time, and the output is the value of the related variable at the virtualization ending time.

[0021] In the above management system of product bill of materials for virtualization prototype, the object model is written in a model modeling language based on the TENA middleware definition, the model modeling language has the ability to describe states and interactions, and can define and construct a distributed interactive simulation running system according to the description.

[0022] The present application has the following advantages:

[0023] The present application discloses a management system of product bill of materials for virtualization prototype, which adds an object model system for system integration virtualization on the basis of the traditional BOM, and has the following significant advantages:

[0024] (1) The division and connection mode of fractal recursive system and subsystem breaks through the traditional BOM form defined based on the product itself, and has the ability of infinite decomposition and free aggregation.

[0025] (2) The combination of the object model interoperation system and the fractal recursive system architecture forms a system BOM that can be freely combined and integrated and used for virtualization verification.

[0026] (3) Based on the state model and the interaction method system, the time evolution integration of the matrix mechanics operation mode can be realized. BRIEF DESCRIPTION OF DRAWINGS

[0027] Figure 1 is a schematic diagram of a data structure of a recursive system index data model in an embodiment of the present application. DETAILED DESCRIPTION

[0028] In order to make the purpose, technical scheme and advantages of the present application clearer, the embodiments disclosed by the present application will be further described in detail below with reference to the drawings.

[0029] In the embodiment, the management system of product bill of materials for virtualization prototype comprises:

[0030] The recursive index module is used to describe the hierarchical and grouping relationship between product modules by using a recursive algorithm, and form a recursive system index data model for the product; wherein the recursive system index data model contains a series of pointers to product system engineering process data.

[0031] An integrated interface module is used to describe the interface and interoperation relationship between adjacent product modules, and provides a software interface for the interoperation between prototype products in a virtualization environment based on an object model.

[0032] In the process of carrying out product prototype virtualization test or verification based on product bill of materials, the hierarchical and grouping relationship between product prototype modules is obtained from a recursive index module, which points the interaction between product modules to the object model managed by the integrated interface module; the product prototype modules in the same group and at the same level have interaction interfaces; wherein the interaction includes mechanical information, thermal information and electromagnetic information.

[0033] In the embodiment, as Figure 1 , the data structure of the recursive system index data model is a tree structure recursively described, including:

[0034] Root node S(0): represents the 0th level system division of the current product S.

[0035] Node S(N): the Nth level system division of the current product, that is, the composition of the current product is subdivided to the Nth level.

[0036] Node Si(N): the i-th subsystem in the Nth level system division, belonging to the Nth level of the tree structure.

[0037] Node Sij(N+1): the j-th submodule of the i-th subsystem in the Nth level system division, belonging to the N+1th level of the tree structure.

[0038] In the embodiment, the division of subsystems or submodules follows engineering habits, and the subsystems or submodules can produce certain utility relatively independently in the system, which cooperates with the utility of other subsystems or submodules at the same level to make the system produce certain functional utility. Generally, product modules with partial complete functions in the system are divided into subsystems.

[0039] In the embodiment, if the object set S(N) contains m different elements, and there is interaction between any two different elements Sa(N+1) and Sb(N+1) in the object set S(N), that is, the utility produced by Sa(N+1) will cause an influence (such as control, thrust, etc.) that must be considered in engineering on Sb(N+1); then the object set S(N) is determined as an N-level system. Wherein, m>1 and m is an integer; a is less than m, b is less than m, and a and b are not equal.

[0040] In the embodiment, the node Si(N) is a series of addresses pointing to the storage locations of different system engineering process data and object models. Wherein, the system engineering process data includes: product design results, product simulation analysis models and data, test data.

[0041] Preferably, the object model is a software interface description of Si(N) and external interaction, including: state interface and method interface. The state interface is a series of definitions of state variables, and the method interface is a function of the change rule of the state variables. The state interface is used to define the physical or information parameters that change when Si(N) interacts with other N-level subsystems; the method interface is used to define the algorithm of the change rule of the state model parameters of Si(N) and other N-level subsystems in the interaction state model. The input of the algorithm is the state model parameter value of the N-level subsystem related to the interaction at the start time of virtualization, and the output is the value of the related parameter at the end time of virtualization.

[0042] Preferably, the object model is written in a modeling language based on the TENA middleware definition, which has the ability to describe states and interactions, and can define and build a distributed interactive simulation running system accordingly.

[0043] Based on the above embodiment, a specific example is described below.

[0044] A product BOM based on a prototype is established taking solid rocket A as an example.

[0045] The data model defines the relationship between the system and the subsystem based on the idea of fractal recursion, and the data structure is a tree structure. The root node of the tree represents the current solid rocket A, i.e., S(0). All 1-level nodes represent 1-level subsystems Si(1), including structural subsystem S1(1), power subsystem S2(1), control subsystem S3(1), attitude control subsystem S4(1), and ground subsystem S5(1).

[0046] The structural subsystem S1(1) includes:

[0047] • fairing S11(2);

[0048] • cabin section structure S12(2);

[0049] • control surface S13(2).

[0050] The power subsystem S2(1) includes:

[0051] • engine S21(2)

[0052] The control subsystem S3(1) includes:

[0053] • missile-borne machine S31(2)

[0054] • inertial unit S32(2)

[0055] • sensor S33(2)

[0056] • missile-borne software S34(2)

[0057] • Power distribution module S35(2)

[0058] • Data link S36(2)

[0059] • Servos S37(2)

[0060] • Cable network S38(2)

[0061] The attitude control subsystem S4(1) includes:

[0062] • Attitude control engine S41(2)

[0063] • Nozzle S42(2)

[0064] The ground subsystem S5(1) includes:

[0065] • Launch pad S51(2)

[0066] • Launch control system S52(2)

[0067] The BOM node Si(N) is a series of addresses pointing to different system engineering process data and object model storage locations. The system engineering process data includes product CAD files, product simulation analysis models and data, and test data. The object model is the object model of the subsystem Si(N) corresponding to the node.

[0068] The structure subsystem S1(1) object model is defined as follows:

[0069] ■ State model

[0070] ■ Mass distribution

[0071] Variables include: point number, point mass, point inertia, D-body coordinate system point coordinates.

[0072] ■ Aerodynamic shape

[0073] Linear description based on DATACOM.

[0074] ■ Rigid body dynamics state

[0075] Variables include: position, velocity, acceleration, attitude, angular velocity, angular acceleration.

[0076] ■ Mechanical environment characteristics

[0077] Characterize the load value of the key structure connection point.

[0078] • Interaction method

[0079] ■ Load environment

[0080] According to the flight state, calculate whether the mechanical environment characteristics exceed the design threshold.

[0081] Power subsystem S2(1) object model definition is as follows:

[0082] ● State model:

[0083] ■ Mass distribution

[0084] According to the nozzle, shell, grain decomposition.

[0085] ■ Thrust vector

[0086] Describe the direction of engine thrust.

[0087] Thrust vector point, thrust vector.

[0088] ■ Rigid body dynamics state

[0089] Position, velocity, acceleration, attitude, angular velocity, angular acceleration.

[0090] ■ Mechanical environment characteristics

[0091] Characterize the key structure, connection point load characteristic value.

[0092] ■ Exit gas state

[0093] Average pressure, average temperature, gas constant, isentropic index, constant pressure specific heat, constant volume specific heat, average molecular weight, average density, average velocity, average Mach number, condensed phase percentage, viscosity coefficient, Prandtl number, gas blackness.

[0094] ● Interaction method

[0095] ■ Engine time evolution model

[0096] Contains internal D channel detailed model, input and output are all engine states. Encapsulate test data model or engine working mechanism model as evolution algorithm.

[0097] Control subsystem object model S3(1) object model definition is as follows:

[0098] ● State model:

[0099] ■ Sensor parameter state

[0100] Information level sensor measurement parameters.

[0101] ■ Control instruction state

[0102] Information level control instruction message.

[0103] ■ Electrical state

[0104] Sensor level value, power supply key point electrical parameters.

[0105] ■ Software state

[0106] The subject's on-board software is deployed on a virtual on-board computer, whose state, timer time, etc. are indexed through the object model.

[0107] Quality distribution

[0108] Control unit, cable network, servo mechanism.

[0109] Interaction method

[0110] Sensor bias model

[0111] The input state is the full-vehicle flight state, the simulation with bias measurement results, and the output is the sensor parameter state.

[0112] Instruction delivery model

[0113] The input state is the control instruction of a certain sending port, and the output is the control quality of a certain receiving port. Random errors are added according to the design state.

[0114] Electrical state time evolution model

[0115] Encapsulated electrical system Modelica principle model, with the input and output states required for system integration.

[0116] The object model S4(1) of the attitude control subsystem object model is defined as follows:

[0117] State model

[0118] Attitude control system state

[0119] Working state of the attitude control system Modelica model.

[0120] Quality distribution

[0121] Nozzle, valve, fuel tank, control device, etc., other definitions are the same as 4.2.1

[0122] Attitude control thrust vector

[0123] Describe the direction of the attitude control engine thrust.

[0124] Thrust vector point, thrust vector.

[0125] Attitude control instruction buffer

[0126] Information level attitude control instruction message.

[0127] Interaction method

[0128] Attitude control thrust time evolution model

[0129] Modelica model of a packaged attitude control system.

[0130] The ground subsystem object model S5(1) object model is defined as follows:

[0131] • State model (VIO):

[0132] ■ Launch pad state

[0133] References the rigid body dynamics state of the launch pad model.

[0134] ■ Measurement and control command state

[0135] Information level measurement and control command message, provides a general transmission message object.

[0136] Although the present application has been disclosed with reference to the preferred embodiments as set forth above, it should be understood that those skilled in the art will be able to devise their own changes and modifications to the technical solutions of the present application without departing from the spirit and scope of the present application, and therefore, any simple modification, equivalent change and modification made to the above embodiments according to the technical essence of the present application, which does not deviate from the technical solutions of the present application, shall fall within the protection scope of the technical solutions of the present application.

[0137] The contents not described in detail in the specification of the present application are known to those skilled in the art.

Claims

1. A management system for product bill of materials for virtualized prototypes, characterized in that, Comprise: Recursive index module, for using recursive algorithm to describe the hierarchical and grouping relationship between product modules, forming a recursive system index data model for the product; wherein the recursive system index data model contains a series of pointers to product system engineering process data; Integration interface module, for describing the interface and interoperability relationship between adjacent product modules, providing software interface for the interoperability between product prototypes in virtualization environment based on object model; In the process of carrying out product prototype virtualization test or verification based on product bill of materials, the hierarchical and grouping relationship between product modules is obtained from the recursive index module, and the recursive index module points the interaction between product modules to the object model managed by the integration interface module; the product modules in the same group and at the same level have interaction interface; wherein the interaction includes mechanical information, thermal information and electromagnetic information; The data structure of the recursive system index data model is a tree structure described recursively, comprising: Root node S(0): representing the 0th level system division of the current product S; Node S(N): representing the Nth level system division of the current product S, i.e. subdividing the composition of the current product to the Nth level; Node Si(N): representing the i th subsystem in the Nth level system division, belonging to the Nth level of the tree structure; Node Sij(N+1): representing the j th submodule of the i th subsystem in the Nth level system division, belonging to the N+1th level of the tree structure; Node Si(N) is a series of addresses pointing to the storage locations of different system engineering process data and object models; the object model is a software interface description of Si(N) and external interaction, including: state interface and method interface; wherein the state interface is a series of state variable definitions, and the method interface is a function of state variable change rule; the state interface is used to define the physical or information parameters that change when Si(N) interacts with other N-level subsystems; the method interface is used to define the algorithm of the change rule of the state model parameters of Si(N) and other N-level subsystems, and the input of the algorithm is the state model parameter value of the N-level subsystem related to the interaction at the start time of virtualization, and the output is the value of the related parameter at the end time of virtualization.

2. The management system for product bill of materials of a virtual prototype according to claim 1, wherein, The division of subsystems or submodules follows engineering habits, and the subsystems or submodules can produce certain utility relatively independently in the system, which will cooperate with the utility of other subsystems or submodules at the same level to make the system produce certain functional utility.

3. The management system for virtualizing a product bill of materials of a prototype according to claim 1, wherein, If S(N) contains m different elements, and there is interaction between any two different elements Sa(N+1) and Sb(N+1) in S(N), i.e. the utility produced by Sa(N+1) will have an influence on Sb(N+1) that must be considered in engineering; then S(N) is determined as an N-level system; wherein m>1 and m is an integer; a is less than m, b is less than m, and a and b are not equal.

4. The management system for virtualizing a product bill of materials of a prototype according to claim 1, wherein, System engineering process data, including: product design results, product simulation analysis model and data, test data.

5. The management system for virtualizing a product bill of materials of a prototype according to claim 1, wherein, The object model is written in a class-based modeling language defined for the TENA middleware, which has the ability to describe states and interactions and to define a distributed interactive simulation runtime system accordingly.

Images