CN112347565B - Rail transit vehicle product module configuration rule construction method - Google Patents
Rail transit vehicle product module configuration rule construction method Download PDFInfo
- Publication number
- CN112347565B CN112347565B CN202011312038.4A CN202011312038A CN112347565B CN 112347565 B CN112347565 B CN 112347565B CN 202011312038 A CN202011312038 A CN 202011312038A CN 112347565 B CN112347565 B CN 112347565B
- Authority
- CN
- China
- Prior art keywords
- module
- constraint
- type
- platform
- modules
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000010276 construction Methods 0.000 title abstract description 11
- 238000000034 method Methods 0.000 claims abstract description 16
- 230000002194 synthesizing effect Effects 0.000 claims 1
- 230000008878 coupling Effects 0.000 description 8
- 238000010168 coupling process Methods 0.000 description 8
- 238000005859 coupling reaction Methods 0.000 description 8
- 239000000725 suspension Substances 0.000 description 5
- 238000004519 manufacturing process Methods 0.000 description 4
- 230000008569 process Effects 0.000 description 3
- 239000000463 material Substances 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000015572 biosynthetic process Effects 0.000 description 1
- 238000010224 classification analysis Methods 0.000 description 1
- 230000002860 competitive effect Effects 0.000 description 1
- 238000001816 cooling Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000003786 synthesis reaction Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F30/00—Computer-aided design [CAD]
- G06F30/10—Geometric CAD
- G06F30/15—Vehicle, aircraft or watercraft design
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
- G06Q30/0621—Item configuration or customization
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
- G06Q50/04—Manufacturing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2111/00—Details relating to CAD techniques
- G06F2111/04—Constraint-based CAD
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Geometry (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Economics (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- General Health & Medical Sciences (AREA)
- Computational Mathematics (AREA)
- Manufacturing & Machinery (AREA)
- Human Resources & Organizations (AREA)
- Primary Health Care (AREA)
- Tourism & Hospitality (AREA)
- Automation & Control Theory (AREA)
- Aviation & Aerospace Engineering (AREA)
- Development Economics (AREA)
- Health & Medical Sciences (AREA)
- Mathematical Analysis (AREA)
- Mathematical Optimization (AREA)
- Pure & Applied Mathematics (AREA)
- Computer Hardware Design (AREA)
- Evolutionary Computation (AREA)
- General Engineering & Computer Science (AREA)
- Stored Programmes (AREA)
- Body Structure For Vehicles (AREA)
Abstract
Aiming at the construction requirements of the current rail transit vehicle product platform and aiming at ensuring the reasonability of module combination in module configuration, the invention provides a method for constructing the module configuration rule of the rail transit vehicle product, which finally forms the module configuration rule table of each product main structure by analyzing and constructing the constraint relation between different modules in the product main structure, thereby quickly and conveniently completing the module configuration of the rail transit vehicle product platform.
Description
Technical Field
The invention relates to a method for constructing product module configuration rules, in particular to a method for constructing product module configuration rules of rail transit vehicles.
Background
With the declaration and opening of more and more subway lines in China, the subway market evolves from the traditional relatively stable type to the dynamic multi-variant type, the current subway vehicle manufacturing industry is changed from a mass production mode to a large-scale customizing mode, how to quickly respond to diversified customer demands and how to develop high-quality products with lower cost and shorter design period become a major war subject of competitive development of subway vehicle manufacturing enterprises. The product platform is a set of subsystems and interfaces thereof forming a common architecture, and a product set with similar functions and different performances, namely a product family, can be continuously derived on the basis of the architecture. In recent years, major host plants of medium-sized vehicles, such as the four-party, the long passenger, the down-sized vehicles, the town of pu, and the like, have attracted attention to the construction of product platforms and product families of rail transit vehicles.
However, there are numerous modules in the product platform build process. The construction of the product platform is directly influenced by whether the configuration relationship between the modules is proper or not. Therefore, a module configuration rule construction method of a product platform is urgently needed.
Disclosure of Invention
The invention aims to: aiming at the construction requirements of the current rail transit vehicle product platform, in order to ensure the reasonability of module combination during module configuration, a module configuration rule table of each product main structure is finally formed by analyzing and constructing constraint relations among different modules in the product main structure, so that the module configuration of the rail transit vehicle product platform is completed.
In order to achieve the above object, the present invention provides a method for constructing a rule of configuration of a rail transit vehicle product module, which is characterized by comprising the following steps:
step 1, analyzing configuration rules; according to the modules defined in the main structure of the product, analyzing the configuration rules between any two modules, and determining the constraint relationship between the modules;
and 2, constructing a module configuration rule table according to the configuration analyzed in the step 1, and completing the module configuration of the product platform of the rail transit vehicle.
In step 1, classifying a constraint relationship between any two modules into:
1) mandatory-constraint relationship between non-platform modules; 2) mandatory-non-platform module and optional-platform module constraint relationship; 3) mandatory-non-platform module and optional-non-platform module constraint relationship; 4) optional-constraint relationships between platform modules; 5) a constrained relationship between the optional-platform module and the optional-non-platform module; 6) optional-constraint relationships between non-platform modules;
wherein, the constraint relation between the mandatory-non-platform modules comprises: a "module A type-module B type" constraint; a "module A type-module B parameter" constraint; "Module A parameters-Module B parameters" constraint; the constrained relationship between the mandatory-non-platform module and the optional-platform module includes: "Module A type-Module B has or has not" constraint; "Module A parameters-Module B has or not" constraints; the constraint relationship between the mandatory-non-platform module and the optional-non-platform module includes: "Module A type-Module B has or has not" constraint; a "module A type-module B type" constraint; a "module A type-module B parameter" constraint; "Module A parameters-Module B has or not" constraints; a "module A parameter-module B parameter" constraint; constraint relationships between alternative-platform modules include: "whether or not module A exists" or not module B exists "constraint; the constraint relationship between the selectable-platform module and the selectable-non-platform module includes: "whether or not module A exists" or not module B exists "constraint; "whether or not module A has a-module B type" constraint; "whether or not module A has a-module B parameter" constraint; constraint relationships between optional-non-platform modules include: "whether or not module A exists" or not module B exists "constraint; "whether or not module A is present-module B type" constraint; "whether or not module A has a-module B parameter" constraint; a "module A type-module B type" constraint; a "module A type-module B parameter" constraint; "Module A parameters-Module B parameters" constraints.
According to the established constraint relation, a configuration rule function for reasoning and a configuration rule function for constraint checking are established; the configuration rule function for reasoning is expressed by (if ()), then ()) or the functional relationship y ═ f (x); the configuration rule function playing a role in constraint checking is expressed by using a feasible combination pair or a function relation f (x, y) which is more than or equal to 0.
Most of the existing configuration rule construction methods construct configuration rules from aspects such as logic constraints (such as dependency constraints and repulsion constraints) of module instance combinations or function constraints (equality or inequality relations) among module attribute parameters, and a configuration rule analysis framework comprehensively considering the diversity of configurable elements of rail transit products is lacked, so that the comprehensiveness and systematicness of configuration rule construction cannot be ensured. The invention provides a method for constructing a module configuration rule aiming at the requirement of constructing a platform of a rail transit vehicle product and aiming at ensuring the reasonability of module combination during module configuration, and compared with the traditional method, the method has the following beneficial effects that:
1) the method is characterized in that the characteristics of different modules are comprehensively considered for several types of modules existing in the main structure of the rail transit vehicle product, and the possible constraint relation between any two types of modules is analyzed from the three aspects of the existence of the modules, the type configurability and the parameter configurability, so that all possible conditions of configuration rules in the main structure of the product are comprehensively reflected.
2) According to the classification analysis of the configuration rules, a configuration rule classification framework is constructed, and the engineering meanings of different types of configuration rules are explained. The framework can be used for supporting module configuration rule analysis and construction in different product main structures.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below. It is to be understood that the embodiments described are only a few embodiments of the present invention, and not all embodiments.
Thus, the following detailed description of the embodiments of the invention is not intended to limit the scope of the invention as claimed, but is merely representative of some embodiments of the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that the embodiments of the present invention and the features and technical solutions thereof may be combined with each other without conflict.
The product platform is a set of subsystems and interfaces thereof forming a common architecture, and product sets with similar functions and different performances, namely product families, can be derived continuously on the basis of the architecture. In recent years, the construction of rail transit vehicle product platforms and product families is concerned by various domestic main engine plants. In the process of building a rail transit vehicle product platform, firstly, a modular structure tree of a rail transit vehicle is built based on a BOM multi-level module division method, and then the module type is identified according to the built modular structure tree, namely, leaf nodes (irrevocable nodes) on the structure tree are identified as product platform modules (including basic modules, general modules and special modules) and non-platform modules. Wherein the basic module is a module which is adopted by all products in a product family and has the same shape and characteristics in the products; the universal module is a module which is adopted by a plurality of products in a product family, and the shapes and the characteristics of the universal module are completely the same in the products; the dedicated module is a module adopted by a few products in a product family, and the shapes and the characteristics of the modules are completely the same in the products; non-flat modules refer to modules whose shape and characteristics are not exactly the same in a product family. The main structure of the product is formed by integrating the modular structure tree, the module type recognition result and the module entity design result. Specifically, the category of each module object is identified according to the result of module type recognition based on the modular meta-structure tree of each vehicle type. The module categories that need to be identified have two dimensions: a general degree dimension and a selection requirement dimension. The general degree reflects the universality of the module instance used in all products in a product family, namely, the identified platform module and the non-platform module specifically include four types: basic module, general module, special module, non-platform module. The selection requirement reflects the characteristic of whether the module exists in all products in the product family, and can be specifically divided into the following steps: a basic module (which is the same as the basic module in the platform module) means that the module must exist and the module instance is unique; the optional module means that the module is in all products in a product family, and the module instance is not unique; the optional module refers to that the module can be added or deleted according to the requirement of a client, and the module can be in products in a product family. It should be noted that the optional module is not necessarily a non-platform module, and the optional module may be a general-purpose module, a special-purpose module in the platform module, or a non-platform module (i.e., optional and non-unique). And identifying the category of the leaf node modules in the structure tree according to the category dimensions of the two modules. Associating the entity design result of each module with the module object on the modular structure tree as a configurable space of the module object, and expressing the product main structure according to the following table:
for a plurality of modules in a product platform, in order to ensure the reasonability of module combination during module configuration, the constraint relationship among different modules in a product main structure needs to be analyzed and constructed. In view of the above, the invention finally forms the module configuration rule table of the main structure of each product through the configuration rule of the structure modeling module.
In the process of constructing the configuration rule of the rail transit vehicle product module, the configuration rule needs to be analyzed first. The module configuration knowledge describes the constraint relationship between different modules, and for the convenience of analysis, the two module types need to be synthesized to clarify the characteristics of different modules. The module types according to two dimensions defined in the aforementioned product main structure comprise: according to the general degree, the system is divided into a basic module, a general module, a special module and a non-platform module; according to the type selection requirement, the method is divided into a basic module, a necessary selection module and an optional module, and the module types of two dimensions are integrated, so that the following results can be obtained:
4 types of modules are obtained by the classification and synthesis, namely a basic module, a mandatory-non-platform module, an optional-platform module and an optional-non-platform module, so that the configuration rules between any two modules can be analyzed. Module nodes of the basic module exist certainly and the examples are unique, the examples of the basic module can be directly selected only after project order products are positioned to a specific product platform, configuration is not needed, and therefore configuration rules corresponding to the modules do not exist. The constraint relationships between the remaining three types of modules need to be analyzed, and the following table shows the constraint relationships between the modules of different types:
| optional-non-platform module | Selectable platform module | Optional-non-platform module | |
| Optional-non-platform module | 1 | ||
| Selectable platform module | 2 | 4 | |
| Option-non-platform module | 3 | 5 | 6 |
1. Mandatory-non-platform Module constraint relationship
Optional-non-platform module means that module nodes exist certainly but module instances are not unique, and a module with configuration design or modified design can be carried out. Two aspects need to be considered: configurable examples of the modules may belong to different categories (namely different realization principles or different topological structures), for example, axles can be divided into solid axles and hollow axles according to the topological structures, and basic braking devices can be divided into disc-type braking devices, tread braking devices and the like; secondly, according to requirements or constraint relations of other modules, attribute parameters (size, performance, materials, interfaces and the like) of the modules can be configured with different values, for example, the power of the traction motor can be 250kW and 350 kW. Thus, instantiation of this type of module requires configuration from two levels, namely module type configuration and module instance parameter configuration.
The constraint relationship between modules limits the feasibility of different module configuration combinations, which exists at the two configuration levels described above for any two mandatory-non-platform modules. There are three types of possible configuration constraint relationships between mandatory-non-platform modules, and the constraint relationships between different types of modules are shown in the following table (where the "module a type-module B parameter" constraint and the "module a parameter-module B type" constraint belong to the same class).
Wherein:
the "module A type-module B type" constraint refers to: such constraints express a constraint relationship between the two modules in type selection. For example, a traction motor module and a coupling module in a platform of a motor vehicle product, a traction motor may be selected from a suspension type and a body suspension type, a coupling may be selected from a flexible floating dog coupling and a cardan shaft, and a constraint relationship between the two may be expressed as if (traction motor is suspension type motor), then (coupling is flexible floating dog coupling) and if (traction motor is body suspension type motor), and then (coupling is cardan shaft).
The "module A type-module B parameters" constraint means: such constraints express a constraint relationship between the type of a module and the parameters of a module. For example if (traction motor power) kW, then (traction motor cooling fan).
The "module a parameters-module B parameters" constraint means: such constraints express a constraint relationship between parameters of the two modules, including dimensions, performance, materials, interface parameters, and the like. For example, the nominal diameter of the coupling shaft hole is equal to the nominal diameter of the output shaft of the traction motor, and the allowable coupling rotation speed is larger than the maximum output rotation speed of the traction motor.
2. Constraint relationship between mandatory-non-platform module and optional-platform module
As analyzed in the mandatory-non-platform module, there may be two levels of configuration of the mandatory-non-platform module: module type configuration and module instance parameter configuration. Whereas an alternative-platform module is a module in which a module node may or may not exist and has a unique module instance. Therefore, the configuration of the optional-platform module only has the existence of configuration, and the configuration of the module category and the module instance parameter does not exist. Thus, there are two types of possible configuration constraint relationships between the mandatory-non-platform module and the optional-platform module, and the following table shows the constraint relationships between the mandatory-non-platform module.
Wherein:
the "module a type-module B presence or absence" constraint means: such constraints express a constraint relationship between the selection of the type of one module and the presence or absence of another module. For example, in a platform of a subway product, if (S-web wheel) and then (disc brake).
The constraint of "module a parameters-module B presence or absence" means: such constraints express the constraint relationship of the setting of one module parameter value to the presence or absence of another module.
3. Constrained relationship between mandatory-non-platform modules and optional-non-platform modules
As analyzed between mandatory-non-platform modules, there may be two levels of configuration of mandatory-non-platform modules: module type configuration and module instance parameter configuration. An optional-non-platform module is a module that may or may not exist in a module node, and has multiple module instances, and may be configured or designed in variations. Referring to the mandatory-non-platform module and optional-platform module, optional-non-platform modules may exist in configurations: configuration of existence, module type configuration, and module instance parameter configuration. There are five types of possible configuration constraint relationships between mandatory-non-platform modules and optional-non-platform modules ("module a type-module B parameter" constraint and "module a parameter-module B type" constraint are the same). The various constraints are as follows, the meaning of which has been set forth above and will not be described further herein. The following table shows the constraint relationship between the mandatory-non-platform module and the optional-non-platform module.
4. Constraint relationships between selectable-platform modules
As analyzed in the alternate-platform module, the configuration of the alternate-platform module only exists with or without configuration, and the configuration of the module class and the module instance parameters does not exist. Optional-there is only one type of possible configuration constraint relationship between platform modules: "whether or not module A exists" or not module B exists "constraint. The following table shows the binding relationships between the alternative-platform modules.
The constraint of "presence or absence of module a-presence or absence of module B" means: the constraint relationship of the presence or absence of one module to the presence or absence of another module may be embodied as a dependency constraint (which must be present at the same time) or a repulsion constraint (which cannot be present at the same time).
5. Constrained relationship between selectable-platform modules and selectable-non-platform modules
As analyzed in the option-platform module, the configuration of the option-platform module only exists with or without configuration. As analyzed in the optional-non-platform module, the optional-non-platform module may have a configuration of: configuration of existence, module type configuration and module instance parameter configuration. There are three types of possible configuration constraint relationships between the optional-platform module and the optional-non-platform module. The following are various types of constraints, and the meaning of each type of constraint is explained as shown above, and is not described herein again. The following table shows the constraint relationship between the optional-platform module and the optional-non-platform module.
6. Constraint relationships between optional-non-platform modules
As with the optional-non-platform module analysis, optional-non-platform modules may exist in configurations: configuration of existence, module type configuration, and module instance parameter configuration. The possible configuration constraint relationships between the selectable non-platform modules are of six types (the existence of the module A and the type of the module B as well as the existence of the constraint of the module A and the type of the module B, the existence of the module A and the parameter of the module B as well as the existence of the constraint of the module A and the parameter of the module B, and the constraint of the module A and the parameter of the module B as well as the constraint of the module A and the parameter of the module B belong to the same type). The various constraints are as follows, the meaning of which has been explained above and will not be described further here. The following table shows the constraint relationship between the mandatory-non-platform module and the optional-non-platform module. The following table shows the constraint relationship between the optional-platform module and the optional-non-platform module.
By combining the analysis of the constraint relationship among the modules, the constraint relationship possibly existing among various modules in the main structure of the product of the project is summarized in the following table. The constraint relationships listed in the table take into account all the types of constraint relationships that may exist between the 3 types of modules, and the actual constraint relationships in the main structure of a certain product are a subset of the table. If there are not multiple optional types (type is unique, there is no configuration of module type) for a certain optional-non-platform module in the product main structure, then there is no constraint relation related to the optional-non-platform module type. For another example, if the existence of an optional-platform module is determined by requirements, there is no class constraint relationship associated with the optional-platform module. The following table functions: a framework is provided for analysis of module constraint relations in main structures of different products, and various constraint relations can be comprehensively analyzed according to the framework.
As can be seen from the following table, the above constraint relationships can be generalized to six classes when the association with the module object is ignored: the constraint of 'whether the module A exists or not-the module B exists or not', whether the module A exists or not-the module B type 'constraint,' whether the module A exists or not-the module B parameter 'constraint,' the module A type-the module B type 'constraint,' the module A type-the module B parameter 'constraint,' and the module A parameter-the module B parameter 'constraint'. These six types of constraints are abbreviated as: "presence/absence", "presence/absence-type", "presence/absence-parameter", "type-type", "type-parameter", "parameter-parameter" may be used to describe the category of the module configuration rule.
From the role of configuration rules, module configuration rules can be divided into two types: configuration rules that function as inferences and configuration rules that function as constraint checks. The configuration rule for inference can be expressed by a production formula rule (if ()), then (), a functional relationship y ═ f (x), or the like, and when parameters/conditions are input, an output is calculated by rule inference or a function. The configuration rule for constraint checking is generally expressed by a feasible combination pair (referring to a CSP (such as a (body suspension motor, cardan shaft)) as a feasible combination), a functional relationship f (x, y) of not less than 0, and the like, and after the values of the types or parameters of the two modules are configured, whether the set types or parameter values meet the constraints is judged through the feasible combination pair or the functional relationship. Thus, the specific representation of each type of module configuration rule in the table above may have four forms: if (), then (), y ═ f (x), feasible combination pairs, f (x, y) ≧ 0.
After the analysis of the configuration rules among the modules is completed, a module configuration rule table can be constructed, which is specifically shown in the following table:
illustratively, the invention analyzes the constraint relationship among modules in a certain type A subway product platform, and constructs the module configuration rule in the product platform, as shown in the following table:
the above embodiments are only used for illustrating the invention and not for limiting the technical solutions described in the invention, and although the present invention has been described in detail in the present specification with reference to the above embodiments, the present invention is not limited to the above embodiments, and therefore, any modification or equivalent replacement of the present invention is made; all such modifications and variations are intended to be included herein within the scope of this disclosure and the appended claims.
Claims (1)
1. A method for constructing configuration rules of a rail transit vehicle product module is characterized by comprising the following steps:
step 1, analyzing configuration rules; according to the modules defined in the main structure of the product, analyzing the configuration rules between any two modules to determine the constraint relationship between the modules; the module is divided into a basic module, a general module, a special module and a non-platform module according to the general degree; dividing the module into a basic module, a mandatory module and an optional module according to the type selection requirement, and comprehensively obtaining the basic module, the mandatory-non-platform module, the optional-platform module and the optional-non-platform module by the module types of two dimensions;
step 2, building a module configuration rule table according to the constraint relation between the modules determined in the step 1, and completing module configuration of the rail transit vehicle product platform;
wherein the constraint relationship between any two modules in the step 1 is classified as:
1) mandatory-constraint relationships between non-platform modules; 2) mandatory-constraint relationship between non-platform modules and optional-platform modules; 3) mandatory-non-platform module and optional-non-platform module constraint relationship; 4) alternative-constraint relationships between platform modules; 5) a constraint relationship between the selectable-platform module and the selectable-non-platform module; 6) optional-constraint relationships between non-platform modules;
the constraint relation between the mandatory non-platform modules is as follows:
a "module A type-module B type" constraint; the constraint expresses the constraint relation of the two modules in type selection;
a "module A type-module B parameter" constraint or a "module A parameter-module B type" constraint; the constraint expresses a constraint relationship between the type of one module and the parameters of another module;
a "module A parameter-module B parameter" constraint; this constraint expresses a constraint relationship between the parameters of the two modules;
the constraint relation between the mandatory-non-platform module and the optional-platform module is as follows:
"Module A type-Module B has or has not" constraint; this constraint expresses the constraint relationship between the selection of the type of one module and the presence or absence of another module;
"Module A parameters-Module B has or not" constraints; this constraint expresses the constraint relationship of the setting of one module parameter value to the presence or absence of another module;
the constraint relationship between the mandatory-non-platform module and the optional-non-platform module is as follows:
"Module A type-Module B has or has not" constraint; this constraint expresses the constraint relationship between the selection of the type of one module and the presence or absence of another module;
a "module A type-module B type" constraint; the constraint expresses the constraint relation of the two modules in type selection;
a "module A type-module B parameter" constraint or a "module A parameter-module B type" constraint; the constraint expresses a constraint relationship between the type of one module and the parameters of another module;
"Module A parameters-Module B has or not" constraints; this constraint expresses the constraint relationship between the selection of parameters of one module and the presence or absence of another module;
a "module A parameter-module B parameter" constraint; this constraint expresses a constraint relationship between the parameters of the two modules;
the constraint relationship between the selectable-platform modules is as follows:
"whether or not module A exists" or not module B exists "constraint; this constraint expresses the constraint relationship of the presence or absence of one module with the presence or absence of another module;
the constraint relation between the selectable-platform module and the selectable-non-platform module is as follows:
"whether or not module A exists" or not module B exists "constraint; this constraint expresses the relationship of the presence or absence of one module to the presence or absence of another module;
"module A has or not-module B type" constraint; this constraint expresses the constraint relationship between the presence or absence of one module and another module type;
"whether or not module A has a-module B parameter" constraint; this constraint expresses the constraint relationship between the presence or absence of one module and the parameters of another module;
the constraint relation between the selectable-non-platform modules is as follows:
whether the module A exists or not and whether the module B exists or not are restricted; this constraint expresses the constraint relationship of the presence or absence of one module with the presence or absence of another module;
whether the module A exists or not, the module B type or the module A type, and whether the module B has or not are restricted; this constraint expresses the constraint relationship between the presence or absence of one module and another module type;
whether the module A exists or not, the module B parameter or the module A parameter, and whether the module B exists or not are restrained; this constraint expresses the constraint relationship between the presence or absence of one module and the parameters of another module;
"Module A type, Module B type" constraint; the constraint expresses the constraint relation of the two modules in type selection;
a "module A type, module B parameter" or a "module A parameter, module B type" constraint; the constraint expresses a constraint relationship between the type of one module and the parameters of another module;
a "module A parameter-module B parameter" constraint; this constraint expresses a constraint relationship between the parameters of the two modules;
according to the established constraint relation between the modules, a configuration rule function for reasoning and a configuration rule function for constraint checking are established; wherein, the configuration rule function for reasoning is expressed by (if ()), then ()) or the functional relation y ═ f (x); the configuration rule function playing a role in constraint checking is expressed by using a feasible combination pair or a function relation f (x, y) is more than or equal to 0; constructing a module configuration rule table according to the established configuration rule function, and completing the module configuration of the rail transit vehicle product platform; wherein, the module configuration rule table comprises: module A-module A type, module A configuration element, module B-module B type, module B configuration element, constraint relationship, constraint action, constraint category;
when the module configuration rule is constructed, the method further comprises the following steps:
building a modular structure tree of the rail transit vehicle based on a BOM multi-level module division method, then identifying the module type according to the built modular structure tree, and identifying the irrevocable nodes on the structure tree into a basic module, a general module, a special module and a non-platform module; and synthesizing the modular structure tree, the module type recognition result and the module entity design result to form a product main structure.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011312038.4A CN112347565B (en) | 2020-11-20 | 2020-11-20 | Rail transit vehicle product module configuration rule construction method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011312038.4A CN112347565B (en) | 2020-11-20 | 2020-11-20 | Rail transit vehicle product module configuration rule construction method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112347565A CN112347565A (en) | 2021-02-09 |
| CN112347565B true CN112347565B (en) | 2022-08-16 |
Family
ID=74365376
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011312038.4A Active CN112347565B (en) | 2020-11-20 | 2020-11-20 | Rail transit vehicle product module configuration rule construction method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112347565B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115730430A (en) * | 2022-11-03 | 2023-03-03 | 聪脉（上海）信息技术有限公司 | DFMEA system analysis method and system |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105005633A (en) * | 2014-04-18 | 2015-10-28 | 中国科学院深圳先进技术研究院 | Configuration platform and configuration method of high speed train product |
| CN107403272A (en) * | 2017-07-27 | 2017-11-28 | 山东大学 | Support the product configuration method and system of multi-stage platform |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105488291A (en) * | 2015-12-11 | 2016-04-13 | 南车青岛四方机车车辆股份有限公司 | Configuration rule processing method and apparatus for quick design of high-speed train |
| CN107657100B (en) * | 2017-09-18 | 2020-12-15 | 中车工业研究院有限公司 | Generation method and device of rail transit train product |
| US11729782B2 (en) * | 2018-06-11 | 2023-08-15 | Apple Inc. | Enhanced uplink beam management |
| CN109344501A (en) * | 2018-09-30 | 2019-02-15 | 西安电子工程研究所 | A kind of modular product configuration and design method |
-
2020
- 2020-11-20 CN CN202011312038.4A patent/CN112347565B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105005633A (en) * | 2014-04-18 | 2015-10-28 | 中国科学院深圳先进技术研究院 | Configuration platform and configuration method of high speed train product |
| CN107403272A (en) * | 2017-07-27 | 2017-11-28 | 山东大学 | Support the product configuration method and system of multi-stage platform |
Non-Patent Citations (5)
| Title |
|---|
| 《Constraint-based Vehicle Configuration: A Case Study》;Jean-Marc Astesana等;《2010 22nd IEEE International Conference on Tools with Artificial Intelligence》;20101027;第68-75页 * |
| 《产品平台设计参数的回归划分方法研究》;林承九等;《机械设计与制造》;20180731(第7期);第73-75+79页 * |
| 《动车组转向架模块化产品平台设计》;陈刚桦等;《机械设计与制造》;20200229(第2期);第183-186+190页 * |
| 《基于约束网络的高速列车车体关联设计技术研究》;邱红铭等;《机械设计与制造》;20171031(第10期);第96-99页 * |
| 《按单设计型复杂产品的配置设计技术综述》;王建等;《计算机集成制造系统》;20200630;第26卷(第02期);第410-425页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112347565A (en) | 2021-02-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Deb et al. | Innovization: Innovating design principles through optimization | |
| CN110659866B (en) | Method for releasing BOM from PDM system to ERP system | |
| CN112347565B (en) | Rail transit vehicle product module configuration rule construction method | |
| CN107403272B (en) | Product configuration method and system supporting multi-stage platform | |
| Huang et al. | Disassembly sequence generation using a neural network approach | |
| Deng et al. | Process flexibility design in unbalanced networks | |
| Michelena et al. | Optimal model-based decomposition of powertrain system design | |
| CN102801552A (en) | System and methods for fault-isolation and fault-mitigation based on network modeling | |
| CN102081706B (en) | Process planning method based on similarity theory | |
| CN113239492B (en) | Tower crane body steel structure damage positioning and monitoring method | |
| KR102063796B1 (en) | Used car grade diagnostic method | |
| Sivashanmugam et al. | Aero-structural optimization of an axial turbine stage in three-dimensional flow | |
| CN112330416B (en) | Design method of rail transit vehicle product | |
| CN105224712A (en) | A kind of disposal route of bullet train product meta-model and device | |
| Sugimura et al. | Kriging-model-based multi-objective robust optimization and trade-off-rule mining using association rule with aspiration vector | |
| CN107862073B (en) | Web community division method based on node importance and separation | |
| Sugimura et al. | Kriging-model-based multi-objective robust optimization and trade-off rule mining of a centrifugal fan with dimensional uncertainty | |
| Le-Khac et al. | A new approach for distributed density based clustering on grid platform | |
| CN115796527A (en) | Production scheduling management method and equipment based on knowledge graph | |
| Huang et al. | Simulation study using system dynamics for a CONWIP-controlled lamp supply chain | |
| CN112633994B (en) | Rail transit vehicle product platform planning method | |
| CN107133727A (en) | Dimensionality optimization method is assessed based on the failure effect for differentiating force coefficient | |
| CN113450194B (en) | Rail transit vehicle product platform construction method | |
| CN112364437B (en) | Simple system design method for rail transit vehicle product platform module | |
| Muller et al. | Applications of fuzzy hierarchies and fuzzy MADM methods to innovative system design |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |