A high-speed train product whole life cycle configuration management method

Abstract

The present application relates to a kind of high-speed train product whole life cycle configuration management method.First by building function-physical model and correlation design structure matrix, using condensation hierarchical clustering algorithm is divided into module, the division result is evaluated using module degree, then according to the module division result gradually decomposes and builds modular product decomposition structure;On this basis, build the design, manufacturing, operation and maintenance each stage configuration view can evolve, with consistent whole life cycle integrated configuration;By analyzing configuration change content, combined with configuration baseline management, build whole life cycle configuration change management model.The present application solves the problem that configuration data consistency is difficult to maintain in the whole life cycle of high-speed train product, configuration information is difficult to trace and configuration change control is insufficient, so as to realize product whole life cycle data through and configuration change control, improve data management capability.

Description

Technical Field

[0001] This invention relates to a product lifecycle configuration management method, specifically, a high-speed train product lifecycle configuration management method. Background Technology

[0002] High-speed trains are complex equipment with tens of thousands of components. Throughout their entire lifecycle, they generate massive amounts of data, often exhibiting inconsistencies and difficulties in information traceability. To ensure consistency between product functional and physical characteristics and product requirements and technical status information, and to maintain clear and traceable configuration information at all times, configuration management is an effective solution. It is a management technology that addresses the entire product lifecycle, using product structure as a carrier and modular configuration as a foundation, to ensure consistency between product functional and physical characteristics and product requirements and technical status information. In the rail transit industry, most studies focus on the configuration at different stages of the product lifecycle separately, rarely incorporating configuration changes throughout the product lifecycle into a unified configuration management system. This often leads to inconsistent configuration data and difficulties in traceability.

[0003] Current configuration management mainly uses components as configuration management units, resulting in high complexity and poor consistency of configurations at different stages. Treating configurations at different stages as independent objects makes it difficult to meet the requirements of keeping product functional and physical characteristics consistent with product requirements and technical status information, and ensuring that configuration information is always clear and traceable. Summary of the Invention

[0004] The purpose of this invention is to address the problems in current high-speed train full lifecycle configuration management, such as difficulty in accurately determining the granularity of configuration management, poor consistency of configuration at different stages, difficulty in tracing configuration information, and insufficient change control. This invention provides a high-speed train product full lifecycle configuration management method to achieve consistency, traceability, and change control of full lifecycle configuration data.

[0005] To achieve the above-mentioned objectives, the present invention provides the following technical solution: A method for full lifecycle configuration management of high-speed train products includes step S1: modular product decomposition structure construction; step S2: full lifecycle configuration change management. Step S1 includes the following steps: S11: Constructing a functional-physical model; S12: Component correlation analysis; S13: Module clustering and evaluation; S14: Establishing a modular product decomposition structure; S15: Configuration construction and evolution at each stage; Step S2 includes the following steps: S21: Analyze the configuration change content of the product; S22: Build a full life cycle configuration change management model.

[0006] Preferably, step S11 includes steps S111-S113: S111: Establish a corresponding functional black box model based on the top-level functions; the inputs and outputs of the black box model include energy flow, information flow, and material flow; the top-level functions include traction function, braking function, steering function, load-bearing function, and buffering function; S112: Establish a functional chain for each black box model. By analyzing the movement and transformation of energy flow, information flow, and material flow, decompose the top-level function into the product's sub-functions and clarify the physical carriers for realizing the sub-functions; preferably, the functions and carriers are not a one-to-one mapping. S113: Merge each functional chain and add spatial geometric constraints of physical carrier components to construct a complete functional-physical model.

[0007] Preferably, in step S12, the component correlation includes functional correlation, physical correlation, assembly geometry correlation, assembly stability correlation, assembly process correlation, and maintenance frequency similarity; the specific analysis steps are as follows: S121: Analyze the correlation between various components and define the strength of each correlation; S122: Construct each correlation matrix separately; S123: Use the analytic hierarchy process (AHP) to determine the weights of each correlation; S124: Constructing a comprehensive correlation matrix ; (1); (2); In the formula: w 1 represents the functional relevance weighting coefficient; w 2 represents the physical correlation weighting coefficient; w 3 indicates the assembly geometry relevance weighting coefficient; w 4 represents the assembly stability correlation weighting coefficient; w 5 represents the assembly process relevance weighting coefficient; w 6 represents the weighting coefficient for similarity in maintenance frequency; Represents the functional correlation matrix; Represents the physical correlation matrix; Represents the assembly geometry correlation matrix; Represents the assembly stability correlation matrix; Represents the assembly process correlation matrix; This represents the similarity matrix of maintenance frequency; the higher the correlation strength value, the higher the correlation and the closer the connection between the parts.

[0008] Preferably, in step S13, agglomerative hierarchical clustering is used for clustering, and modularity is used to evaluate the results of modular partitioning. Agglomerative hierarchical clustering calculates the distance between each data point and all data points, aggregates the two data points with the highest correlation as new data points, and then performs the next aggregation, repeating this process to finally obtain a hierarchical nested clustering tree; modularity Q Definition: (3); In the formula, e ii Indicates community i The proportion of interior edges to the total number of edges. This indicates that in a random network, the community i The expected proportion of internal edges; based on the clustering results, calculate the modularity of each module partitioning scheme. Q The higher the modularity, the higher the internal tightness of the module, and the better the quality of the module partitioning; specifically, it involves the following steps: S131: Based on the comprehensive correlation matrix, clustering is performed using the agglomerative hierarchical clustering algorithm to obtain the partitioning results of different modules; S132: Calculate the modularity of each modular partitioning result; S133: Select the module partitioning scheme with the highest modularity as the system layer.

[0009] Preferably, in step S14, the module division result is used as the system layer. Based on the hierarchical structure of the clustering tree, it is decomposed step by step to construct a modular product decomposition structure, and the nodes above the module layer are determined as configuration items, i.e. configuration management units. The modular product decomposition structure is divided into product layer, system layer, module layer, solution layer and component layer from top to bottom. Based on the configuration layer, products that meet customer needs are configured, and the product configuration is expressed using the modular product decomposition structure.

[0010] Preferably, in step S15, configuration nodes for each stage are defined based on requirements and product characteristics. Manufacturing and operation configurations are constructed through node adjustments, attribute adjustments, and configuration file adjustments, forming an integrated comprehensive configuration. The configurations for each stage are then re-evolved through this integrated configuration. The specific steps are as follows: S151: Based on the modular product decomposition structure, a design configuration is constructed. The design configuration includes product structure, basic attributes, version attributes, and configuration files. The design configuration reflects the product design structure and the relationship between various physical carriers. It is an instance configuration obtained through customer selection based on the modular product decomposition structure, and consists of product layer, system layer, module layer, and component layer. Nodes above the module layer are set as configuration items and associated with attributes and configuration files. The component layer is not managed separately as a configuration item. S152: Construct a manufacturing configuration based on the design configuration; the manufacturing configuration reflects the product manufacturing structure. Based on the manufacturing configuration elements, the manufacturing configuration is constructed through configuration adjustments. The manufacturing configuration includes product structure, basic attributes, version attributes, assembly attributes, and configuration files; configuration adjustments can be made in the following ways: node adjustments; attribute adjustments; and configuration file adjustments. S153: An operation and maintenance configuration is constructed based on the manufacturing configuration; the operation and maintenance configuration reflects the product operation and maintenance structure, including product structure, basic attributes, version attributes, operation and maintenance attributes, and configuration files; the operation and maintenance configuration is adjusted according to the location of repair points or disassembly points, and the configuration adjustment methods include: node adjustment; attribute adjustment; configuration file adjustment, thereby reflecting the characteristics of the operation and maintenance phase; the operation and maintenance configuration is constructed on the basis of the manufacturing configuration, thus forming an integrated comprehensive configuration; S154: The configurations at each stage are re-evolved through an integrated configuration.

[0011] Preferably, step S21 includes the following steps: Step S211: Design Phase Change Analysis; Changes in the design phase include three categories: product structure changes, design parameter changes, and functional changes; Step S212: Manufacturing stage changes; Manufacturing stage changes include changes to suppliers and models, as well as changes to installation locations; Step S213: Changes during the operation and maintenance phase; Changes during the operation and maintenance phase mainly include three categories: changes to maintenance parts, changes to spare parts, and upgrades and modifications.

[0012] Preferably, in step S22, a three-dimensional model for configuration change management is formed using three dimensions: time, hierarchy, and node identifier. The hierarchy axis represents the configuration structure hierarchy, and the node identifier axis represents the position identifier of the configuration item node in the three-dimensional model. The configuration evolves along the time axis. Along the time axis, the changed parts are recorded. Using a search algorithm, the current configuration of the product and the technical status of individual configuration items are clear at any given time, ensuring the traceability of configuration data throughout the product's entire lifecycle. Step S22 specifically includes the following steps: S221: Construct a three-dimensional model for configuration change management that includes three dimensions: time, hierarchy, and node identifiers; S222: Record the nodes and their attributes in the model, as well as the changes in the configuration file; S223: The configuration baseline is changed synchronously after approval; S224: Use a search algorithm to search for configuration items or configuration trees at a certain time to trace configuration information. The search algorithm is a process of recursively traversing the product structure tree, and based on the time condition, by calling GetCI(ID,t) and GetCTree(IDs,t), obtaining the configuration items of each node and its child nodes level by level, and outputting the matching results. It is divided into search algorithm 1 for configuration item tracing and search algorithm 2 for configuration tree tracing.

[0013] Preferably, in step S223, once the configuration baseline is published, any changes must be made according to the following procedure: S2231: Request for amendment; the request for amendment shall include the reasons for the amendment and an analysis of its impact, and recommendations for the amendment; S2232: Impact Analysis; Analyze the impact of changes, specifically including the impact on attributes, nodes, and configuration files associated with nodes; S2233: Change Review; Review changes and record signature information; There are two types of review conclusions: if the review fails, the change application must be revised and returned to the change application submission step; if the review passes, the approval process begins. S2234: Change Approval; Conduct the change approval process and record the approval signature information; S2235: Change execution; modify node-related information and release a new baseline version; complete the configuration baseline change through the control flow, release the new configuration baseline, and then update the configuration baseline attributes.

[0014] Preferably, the input to GetCI(ID,t) is the node ID and the time point t; the output is the configuration item of the node at time t (if it exists), otherwise it returns null. The input of GetCTree(IDs,t) is the IDs of the child nodes and the time point t; the output is the complete structure tree with the node as the top level; the internal implementation is: get the IDs of the node and all its direct child nodes, and for each child node, recursively call GetCTree(IDs,t) to obtain the substructure tree; The steps of search algorithm 1 are as follows: (1) Initialization; set the current search time... t Set as start time t s (2) Judgment and status query; Determine the current time t Is it less than the end time? t e ,like t < t e , call GetCI ( ID , t Get unique identifier ID and current time t Simultaneously matching configuration terms; if t ≥ t e If a matching record exists, the traversal ends; (3) Judgment and output; If a matching record exists, output the record, which contains the configuration item in t The attributes, version, and associated file information of the time; if no matching record is found, it is determined that the configuration item is int If the time does not exist or has not changed, then the time will be... t Add a minimum time unit, then return to step (2) of search algorithm 1 and continue querying the state at the next time point; (4) end; summarize and output all historical state records obtained in step (3) of search algorithm 1, thus fully presenting the configuration item in t s to t e The trajectory of change over a period of time; The steps of search algorithm 2 are as follows: (1) Obtain the root node; call GetCI ( ID , t Get the specified ID The configuration term in time t The state; (2) Recursive traversal; Taking the root node configuration item with the specified ID as the root node, find all its child nodes; For each found child node, call GetCTree ( IDs , t Get child nodes IDs and the child node and its next-level nodes in time t The configuration item state is obtained, and the process ends after obtaining the configuration item states of all child nodes; (3) Output; All nodes, attributes and their relationships obtained in steps (1) and (2) of search algorithm 2 are arranged into a complete configuration tree state according to their original hierarchical structure, and the configuration tree is output to reflect the configuration item of the root node in time. t The complete technical status.

[0015] Compared with the prior art, the beneficial effects of the present invention are as follows: (1) In practice, the inventors found that it is difficult for technicians to accurately determine the granularity of configuration management of high-speed train products in the prior art. The present invention takes into account the influencing factors of the whole life cycle and divides the modules to determine the granularity of configuration management, thereby effectively reducing the configuration reconstruction work in the subsequent stages and helping to reduce the complexity of product configuration management.

[0016] (2) In practice, the inventors found that in the prior art, it is difficult for technicians to achieve hierarchical modular division of products, and they can only divide them into fixed modules. This invention uses agglomerative hierarchical clustering algorithm to perform clustering and obtain hierarchical module division results, which is conducive to the construction of modular product decomposition structure and the construction of subsequent stage configurations, and provides a hierarchical carrier for configuration management.

[0017] (3) In practice, the inventors found that in the existing technologies for constructing the configuration of high-speed train products at each stage, it is difficult to maintain consistency in the configuration structure, node-related attributes, and mapping of configuration files at each stage, and it is difficult to express them explicitly. In response, this invention proposes to use methods such as node adjustment (keeping nodes, adding nodes, decomposing nodes, etc.); attribute adjustment (keeping attributes, adding attributes, assigning attribute values); and configuration file adjustment (keeping and adding configuration files) to construct manufacturing and operation configurations, forming an integrated comprehensive configuration, and completing the explicit expression and consistency maintenance of the product configuration.

[0018] (4) In practice, the inventors found that the existing methods of treating different stage configurations as independent objects are difficult to meet the requirement of keeping configuration information clear and traceable at all times. Therefore, this invention adopts a three-dimensional configuration change management model that incorporates the entire product lifecycle into a unified configuration management process, ensuring the consistency of configuration data and realizing the connection, traceability, and change control of configuration data throughout the entire lifecycle. This simplifies enterprise management, improves design efficiency, and saves manufacturing and maintenance costs. Attached Figure Description

[0019] Figure 1 A schematic diagram of the physical model of some functions of a high-speed train; Figure 2 A schematic diagram of a product lifecycle configuration change management model; Figure 3 This is a schematic diagram of the search algorithm. Detailed Implementation

[0020] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments.

[0021] A method for managing the entire lifecycle configuration of high-speed train products, comprising steps S1-S2: Step S1: Modular product breakdown structure construction; Step S2: Full lifecycle configuration change management.

[0022] Preferably, step S1 includes the following steps: S11: Construct the functional-physical model; S12: Component Correlation Analysis; S13: Module Clustering and Evaluation; S14: Establish a modular product breakdown structure; S15: Configuration construction and evolution at each stage.

[0023] Preferably, step S11 includes steps S111-S113: S111: Establish a corresponding functional black box model based on the top-level functions. The inputs and outputs of the black box model include energy flow (such as electrical energy, mechanical energy, etc.), information flow (such as start signals, braking signals, etc.), and material flow (such as air). The top-level functions include traction, braking, steering, load-bearing, and buffering functions. The traction function converts electrical energy into traction force through traction signal commands, transmitting the traction force generated at the wheel-rail contact point to the car body and coupler, propelling the vehicle forward and providing feedback acceleration signals. The braking function converts high-pressure air energy into braking force through braking signal commands, causing the vehicle to decelerate or stop as required, and providing feedback deceleration signals; air is released when braking is canceled. The load-bearing function bears the mass of all parts above the bogie (including: car body mass, passenger mass, water, and dynamic loads, etc.) and ensures even axle load distribution. The steering function converts the lateral disturbance force on the wheel-rail or car body into a centering restoring force, ensuring the vehicle smoothly passes through curves. The buffering function converts the energy of vibrations in all directions into heat dissipation, ensuring good vehicle stability.

[0024] S112: Establish a functional chain for each black box model. By analyzing the movement and transformation of energy flow, information flow, and material flow, decompose the top-level function into sub-functions of the product and clarify the physical carriers for realizing the sub-functions. Preferably, the function and the carrier are not a one-to-one mapping.

[0025] S113: Merge each functional chain and add spatial geometric constraints of physical carrier components to construct a complete functional-physical model.

[0026] Preferably, in step S12, the component correlation includes functional correlation, physical correlation, assembly geometry correlation, assembly stability correlation, assembly process correlation, and maintenance frequency similarity. The specific analysis steps are as follows: S121: Analyze the correlation between various components and define the strength of each correlation; S122: Construct each correlation matrix separately; S123: Use the analytic hierarchy process (AHP) to determine the weights of each correlation; S124: Constructing a comprehensive correlation matrix ; (1); (2); In the formula: w 1 represents the functional relevance weighting coefficient; w 2 represents the physical correlation weighting coefficient; w 3 indicates the assembly geometry relevance weighting coefficient; w4 represents the assembly stability correlation weighting coefficient; w 5 represents the assembly process relevance weighting coefficient; w 6 represents the weighting coefficient for similarity in maintenance frequency; Represents the functional correlation matrix; Represents the physical correlation matrix; Represents the assembly geometry correlation matrix; Represents the assembly stability correlation matrix; Represents the assembly process correlation matrix; This represents a similarity matrix of maintenance frequencies. A higher correlation strength value indicates a stronger correlation and closer connection between components. Obtained by the Analytic Hierarchy Process (AHP).

[0027] The factors affecting the entire life cycle include functional relevance, physical relevance, assembly geometry relevance, assembly stability relevance, assembly process relevance, and maintenance frequency similarity. This invention considers the factors affecting the entire life cycle to divide the product into modules, reducing the work of reconfiguring the product at each stage, thereby helping to reduce the complexity of product configuration management.

[0028] Preferably, in step S13, agglomerative hierarchical clustering is used for clustering, and modularity is used to evaluate the modular partitioning results. Agglomerative hierarchical clustering calculates the distance between each data point and all other data points, aggregating the two closest (i.e., most correlated) data points as new data points, and then repeating this process to obtain a hierarchical nested clustering tree. Modularity Q Definition: (3); In the formula, e ii Indicates community i The proportion of interior edges to the total number of edges. This indicates that in a random network, the community i The expected proportion of internal edges. Based on the clustering results, calculate the modularity of each module partitioning scheme. Q The higher the modularity value, the higher the internal tightness of the modules, and the better the quality of module partitioning. Preferably, this value is between 0.3 and 0.7. The process consists of the following steps: S131: Based on the comprehensive correlation matrix, clustering is performed using the agglomerative hierarchical clustering algorithm to obtain the partitioning results of different modules; S132: Calculate the modularity of each modular partitioning result; S133: Select the module partitioning scheme with the highest modularity as the system layer.

[0029] Preferably, in step S14, the module division result is used as the system layer. Based on the hierarchical structure of the clustering tree, it is progressively decomposed downwards to construct a modular product decomposition structure, and the nodes above the module layer are identified as configuration items, i.e., configuration management units. The modular product decomposition structure is divided into product layer, system layer, module layer (configuration layer), solution layer, and component layer from top to bottom. Based on the configuration layer, products that meet customer needs are configured, and this modular product decomposition structure is used to express the product configuration.

[0030] This invention uses nodes above the module level as configuration items to determine the granularity of configuration management for high-speed train products. It uses agglomerative hierarchical clustering algorithm to perform clustering and obtain hierarchical module division results, which is beneficial for the construction of modular product decomposition structure and the construction of configurations in subsequent stages, providing a hierarchical carrier for configuration management.

[0031] Preferably, in step S15, configuration nodes for each stage are defined according to requirements and product characteristics (associated with attributes and configuration files). Manufacturing and operation configurations are constructed through node adjustments (keeping nodes, adding nodes, decomposing nodes, etc.), attribute adjustments (keeping attributes, adding attributes, assigning attribute values), and configuration file adjustments (keeping and adding configuration files), forming an integrated comprehensive configuration. The configurations for each stage are then re-evolved through this integrated configuration. The specific steps are as follows: S151: Based on the modular product decomposition structure, a design configuration is constructed. The design configuration includes product structure (nodes and relationships between them), basic attributes (code, name, model, quantity, location), version attributes (version number, version validity period), and configuration files (2D drawings, 3D models, design technical documents, etc.). The design configuration reflects the product design structure and the relationships between various physical carriers. It is an example configuration obtained through customer selection based on the modular product decomposition structure, and consists of a product layer, system layer, module layer (configuration layer), and component layer. Nodes above the module layer are set as configuration items and associated with attributes and configuration files; the component layer is not managed separately as configuration items.

[0032] Preferably, the change management of the component layer is set according to the actual situation. Changes to important components are reflected in the changes of the previous version, while changes to non-important components are not recorded, thereby optimizing the configuration granularity.

[0033] S152: Constructing a manufacturing configuration based on the design configuration. The manufacturing configuration reflects the product's manufacturing structure. Based on the manufacturing configuration elements, the manufacturing configuration is constructed through configuration adjustments. The manufacturing configuration includes the product structure (nodes and the relationships between nodes), basic attributes (code, name, model, quantity, location, supplier, batch number), version attributes (version number), assembly attributes (assembly status), and configuration files (2D drawings, 3D models, design technical documents, process planning documents, etc.). Configuration adjustments include: node adjustments (keeping nodes, adding nodes, decomposing nodes, etc.); attribute adjustments (keeping attributes, adding attributes, assigning attribute values); and configuration file adjustments (keeping and adding configuration files).

[0034] S153: An operation and maintenance (O&M) configuration is constructed based on the manufacturing configuration. The O&M configuration reflects the product's operation and maintenance structure, including product structure (nodes and relationships between nodes), basic attributes (code, name, model, quantity, location, supplier, batch number), version attributes (version number), O&M attributes (failure status, repair time, next maintenance time, remaining service life, mileage, runtime), and configuration files (2D drawings, 3D models, design technical documents, process planning documents, history sheets, spare parts inventory lists, etc.). The O&M configuration can be adjusted based on the location of repair or disassembly points. Configuration adjustments include: node adjustment (keeping nodes, adding nodes, decomposing nodes, etc.); attribute adjustment (keeping attributes, adding attributes, assigning attribute values); and configuration file adjustment (keeping and adding configuration files), thus reflecting the characteristics of the O&M phase. The O&M configuration is constructed based on the manufacturing configuration, forming an integrated comprehensive configuration.

[0035] S154: The configurations at each stage are re-evolved through an integrated configuration.

[0036] This invention proposes to construct manufacturing and operation configurations by using node adjustment (keeping nodes, adding nodes, decomposing nodes, etc.), attribute adjustment (keeping attributes, adding attributes, assigning attribute values), and configuration file adjustment (keeping and adding configuration files) to form an integrated comprehensive configuration, thereby achieving explicit expression and consistency maintenance of product configuration.

[0037] Preferably, step S2 includes the following steps: S21: Analyze the changes in the product's configuration; S22: Build a full lifecycle configuration change management model.

[0038] Throughout the product lifecycle, configuration changes occur due to design alterations, supplier shortages, cost factors, maintenance operations, and operator-initiated upgrades. These changes impact configuration nodes, node attributes, and configuration files. Since configuration changes occurring at different stages of the product lifecycle have varying impacts, step S21 is necessary.

[0039] Preferably, step S21 includes the following steps: Step S211: Design Phase Change Analysis. Changes during the design phase include three categories: product structure changes, design parameter changes, and functional changes. When the product structure changes, it affects configuration documents such as 2D drawings, 3D models, and technical specifications, as well as attributes and configuration nodes. When design parameters (such as shape and material) change, it affects configuration documents such as 2D drawings, 3D models, and technical specifications, and changes to attributes. When product functionality changes, it affects configuration documents such as 2D drawings, 3D models, and technical specifications, and affects attributes and configuration nodes.

[0040] Step S212: Manufacturing Stage Changes. Manufacturing stage changes include supplier and model changes, as well as installation location changes. When a supplier or model change occurs but does not involve structural or functional alterations, it has no impact on the configuration files, only affecting configuration node attributes. When a supplier or model change involves structural or functional alterations, it will affect configuration files such as 2D drawings, 3D models, technical specifications, and process planning documents, affecting not only attributes and configuration nodes but also the design baseline. When the installation location changes, it will affect configuration files and attributes such as 2D drawings, 3D models, technical specifications, and process planning documents.

[0041] Step S213: Changes during the Operation and Maintenance Phase. Changes during the operation and maintenance phase mainly include three categories: changes to maintenance parts, changes to spare parts, and upgrades / modifications. When maintenance parts are repaired due to operational duration and service life, or when the same model of parts is replaced, the impact on the configuration is reflected in changes to attributes and configuration documents. When spare parts are changed, only the spare parts inventory list is affected, with no direct impact on the configuration. When upgrades / modifications are performed and involve changes to structure or function, configuration documents such as 2D drawings, 3D models, technical specifications, and upgrade / modification records will be affected, impacting attributes and configuration nodes, and further affecting the operation and maintenance baseline. Based on the change impact analysis, the specific content of the configuration change is identified.

[0042] Preferably, in step S22, a three-dimensional model for configuration change management is formed using three dimensions: time, hierarchy, and node identifier. The hierarchy axis represents the configuration structure hierarchy, and the node identifier axis represents the position identifier of the configuration item node in the three-dimensional model. The configuration evolves along the time axis. Along the time axis, the changed parts are recorded. Using a search algorithm, the current configuration of the product and the technical status of individual configuration items can be clearly understood at any given time, ensuring the traceability of configuration data throughout the product's entire lifecycle. Step S22 specifically includes the following steps: S221: Construct a three-dimensional model for configuration change management that includes three dimensions: time, hierarchy, and node identifiers.

[0043] S222: Record the nodes and their attributes in the model, as well as the changes in the configuration file.

[0044] S223: The configuration baseline must be changed synchronously after approval. Once the configuration baseline is published, any changes must be made according to the following procedure: S2231: Change request submitted. The change request includes the reasons for the change and an analysis of its impact, as well as recommendations for the change.

[0045] S2232: Impact Analysis. Analyze the impact of the changes, specifically the impact on attributes, nodes, and configuration files associated with nodes. These impacts may involve one or more nodes.

[0046] S2233: Change Review. Review the changes and record the signature information. There are two possible review conclusions: if the review fails, the change request must be revised and the process returned to the change request submission step; if the review passes, the process proceeds to approval.

[0047] S2234: Change Approval. Conduct the change approval process and record the approval signature information.

[0048] S2235: Change Execution. Modify node-related information and release a new baseline version. Through the control flow, complete the configuration baseline change, release the new configuration baseline, and then update the configuration baseline attributes.

[0049] The three-dimensional configuration change management model adopted in this invention incorporates the entire product lifecycle into a unified configuration management process, ensuring the consistency of configuration data.

[0050] S224: Use a search algorithm to search for configuration items or configuration trees at a certain time to trace configuration information. The search algorithm is a process of recursively traversing the product structure tree, and based on the time condition, by calling GetCI(ID,t) and GetCTree(IDs,t), obtaining the configuration items of each node and its child nodes level by level, and outputting the matching results. It is divided into search algorithm 1 for configuration item tracing and search algorithm 2 for configuration tree tracing.

[0051] Preferably, the input of GetCI(ID,t) is the node ID and the time point t; the output is the configuration item of the node at time t (if it exists), otherwise it returns empty.

[0052] Preferably, the input of GetCTree(IDs,t) is the IDs of the child nodes and the time point t; the output is the complete configuration tree with the node as the top level (including the configuration items of the node and all its child nodes at time t); the internal implementation (recursive) is as follows: get the IDs of the node and all its direct child nodes, and for each child node, recursively call GetCTree(IDs,t) to obtain the subconfiguration tree.

[0053] Preferably, the search algorithm 1 is implemented as follows: (1) Initialization. Set the current search time... t Set as start time t s (2) Judgment and Status Inquiry. Determine the current time. t Is it less than the end time? t e ,like t < t e , call GetCI ( ID , t Get unique identifier ID and current time t Simultaneously matching configuration terms. If t ≥ t e If a matching record exists, the traversal ends. (3) Judgment and output. If a matching record exists, output the record, which contains the configuration item in t The attributes, version, and associated file information of the time. If no matching record is found, the configuration item is determined to be in [location missing]. t If the time does not exist or has not changed, then the time will be... t Add a minimum time unit, then return to step (2) and continue querying the status at the next time point. (4) End. Summarize and output all historical status records obtained in step (3) to fully present the configuration item in t s to t e The trajectory of change over a period of time.

[0054] The steps of search algorithm 2 are as follows: (1) Obtain the root node. Call GetCI ( ID , t Get the specified ID The configuration term in time t The state. (2) Recursive traversal. Using the root node configuration item with the specified ID as the root node, find all its child nodes. For each found child node, call GetCTree ( IDs , t Get child nodes IDs and the child node and its next-level nodes in time t The configuration item state is obtained, and the process ends after obtaining the configuration item states of all child nodes. (3) Output. All nodes, attributes and their relationships obtained in steps (1) and (2) are arranged into a complete configuration tree state according to their original hierarchical structure. The configuration tree is output to reflect the configuration item of the root node in time. t The complete technical status.

[0055] This invention utilizes a configuration change management model and search algorithm to achieve seamless, traceable, and change-controlled configuration data throughout the entire lifecycle, thereby simplifying enterprise management, improving design efficiency, and saving manufacturing and maintenance costs.

[0056] The above embodiments are only used to illustrate the present invention and are not intended to limit the technical solutions described herein. Although the present invention has been described in detail with reference to the above embodiments, the present invention is not limited to the specific embodiments described above. Therefore, any modifications or equivalent substitutions to the present invention, as well as all technical solutions and improvements that do not depart from the spirit and scope of the invention, are covered within the scope of the claims of the present invention.

Claims

1. A method for full lifecycle configuration management of high-speed train products, characterized in that: Step S1: Modular product breakdown structure construction; Step S2: Full lifecycle configuration change management; In step S1, The process includes the following steps: S11: Constructing a functional-physical model; S12: Component correlation analysis; S13: Module clustering and evaluation; S14: Establishing a modular product decomposition structure; S15: Configuration construction and evolution at each stage; In step S2, The process includes the following steps: S21: Analyze the configuration changes of the product; S22: Build a full lifecycle configuration change management model.

2. The high-speed train product full life cycle configuration management method as described in claim 1, characterized in that: Step S11 includes steps S111-S113: S111: Establish a corresponding functional black box model based on the top-level functions; the input and output of the black box model include energy flow, information flow, and material flow; the top-level functions include traction function, braking function, steering function, load-bearing function, and buffering function; the traction function converts electrical energy into traction force through traction signal commands, transmits the traction force generated at the wheel-rail contact point to the car body and coupler, pulls the vehicle forward, and provides feedback acceleration signals; the braking function converts high-pressure air energy into braking force through braking signal commands, causing the vehicle to decelerate or stop as required, and provides feedback deceleration signals, releasing air when braking is canceled; the load-bearing function bears the mass of all parts above the bogie and ensures even distribution of axle load; the steering function converts the lateral disturbance force on the wheel-rail or car body into a centering restoring force, ensuring the vehicle smoothly passes through curves; the buffering function converts the vibration energy received from all directions into heat energy dissipation, ensuring good vehicle stability; S112: Establish a functional chain for each black box model. By analyzing the movement and transformation of energy flow, information flow, and material flow, decompose the top-level function into the product's sub-functions and clarify the physical carriers for realizing the sub-functions; preferably, the functions and carriers are not a one-to-one mapping. S113: Merge each functional chain and add spatial geometric constraints of physical carrier components to construct a complete functional-physical model.

3. The high-speed train product full life cycle configuration management method as described in claim 2, characterized in that: In step S12, component correlation includes functional correlation, physical correlation, assembly geometry correlation, assembly stability correlation, assembly process correlation, and maintenance frequency similarity; the specific analysis steps are as follows: S121: Analyze the correlation between various components and define the strength of each correlation; S122: Construct each correlation matrix separately; S123: Use the analytic hierarchy process (AHP) to determine the weights of each correlation; S124: Constructing a comprehensive correlation matrix ; （1）； （2）； In the formula: w 1 represents the functional relevance weighting coefficient; w 2 represents the physical correlation weighting coefficient; w 3 indicates the assembly geometry relevance weighting coefficient; w 4 represents the assembly stability correlation weighting coefficient; w 5 represents the assembly process relevance weighting coefficient; w 6 represents the weighting coefficient for similarity in maintenance frequency; Represents the functional correlation matrix; Represents the physical correlation matrix; Represents the assembly geometry correlation matrix; Represents the assembly stability correlation matrix; Represents the assembly process correlation matrix; This represents the similarity matrix of maintenance frequency; the higher the correlation strength value, the higher the correlation and the closer the connection between the parts.

4. The high-speed train product full life cycle configuration management method as described in claim 3, characterized in that: In step S13, agglomerative hierarchical clustering is used for clustering, and modularity is used to evaluate the results of modular partitioning. Agglomerative hierarchical clustering calculates the distance between each data point and all other data points, aggregating the two most correlated data points as new data points, and then repeating this process to obtain a hierarchical nested clustering tree. Modularity... Q Definition: （3）； In the formula, e ii Indicates community i The proportion of interior edges to the total number of edges. This indicates that in a random network, the community i The expected proportion of internal edges; based on the clustering results, calculate the modularity of each module partitioning scheme. Q The higher the modularity, the higher the internal tightness of the module, and the better the quality of the module partitioning; specifically, it involves the following steps: S131: Based on the comprehensive correlation matrix, clustering is performed using the agglomerative hierarchical clustering algorithm to obtain the partitioning results of different modules; S132: Calculate the modularity of each modular partitioning result; S133: Select the module partitioning scheme with the highest modularity as the system layer.

5. The high-speed train product full life cycle configuration management method as described in claim 4, characterized in that: In step S14, the module division result is used as the system layer. Based on the clustering tree hierarchy, it is decomposed step by step to construct the modular product decomposition structure, and the nodes above the module layer are determined as configuration items, i.e. configuration management units. The modular product decomposition structure is divided into product layer, system layer, module layer, solution layer, and component layer from top to bottom; based on the configuration layer, products that meet customer needs are configured, and the modular product decomposition structure is used to express the product configuration.

6. The high-speed train product full life cycle configuration management method as described in claim 5, characterized in that: In step S15, configuration nodes for each stage are defined based on requirements and product characteristics. Manufacturing and operation configurations are constructed through node adjustments, attribute adjustments, and configuration file adjustments, forming an integrated comprehensive configuration. The configurations for each stage are then re-evolved from this integrated configuration. The specific steps are as follows: S151: Based on the modular product decomposition structure, a design configuration is constructed. The design configuration includes product structure, basic attributes, version attributes, and configuration files. The design configuration reflects the product design structure and the relationship between various physical carriers. It is an instance configuration obtained through customer selection based on the modular product decomposition structure, and consists of product layer, system layer, module layer, and component layer. Nodes above the module layer are set as configuration items and associated with attributes and configuration files. The component layer is not managed separately as a configuration item. S152: Constructing a manufacturing configuration based on a design configuration; Manufacturing configuration reflects the product's manufacturing structure. Based on the manufacturing configuration elements, the manufacturing configuration is constructed through configuration adjustments. The manufacturing configuration includes product structure, basic attributes, version attributes, assembly attributes, and configuration files. Configuration adjustments can be made through: node adjustments; attribute adjustments; and configuration file adjustments. S153: An operation and maintenance configuration is constructed based on the manufacturing configuration; the operation and maintenance configuration reflects the product operation and maintenance structure, including product structure, basic attributes, version attributes, operation and maintenance attributes, and configuration files; the operation and maintenance configuration is adjusted according to the location of repair points or disassembly points, and the configuration adjustment methods include: node adjustment; attribute adjustment; configuration file adjustment, thereby reflecting the characteristics of the operation and maintenance phase; the operation and maintenance configuration is constructed on the basis of the manufacturing configuration, thus forming an integrated comprehensive configuration; S154: The configurations at each stage are re-evolved through an integrated configuration.

7. The high-speed train product full life cycle configuration management method as described in claim 6, characterized in that: Step S21 includes the following steps: Step S211: Design Phase Change Analysis; Changes in the design phase include three categories: product structure changes, design parameter changes, and functional changes; Step S212: Manufacturing stage changes; Manufacturing stage changes include changes to suppliers and models, as well as changes to installation locations; Step S213: Changes during the operation and maintenance phase; Changes during the operation and maintenance phase mainly include three categories: changes to maintenance parts, changes to spare parts, and upgrades and modifications.

8. The high-speed train product full life cycle configuration management method as described in claim 7, characterized in that: In step S22, a three-dimensional model for configuration change management is formed using three dimensions: time, hierarchy, and node identifier. The hierarchy axis represents the configuration structure hierarchy, and the node identifier axis represents the position identifier of the configuration item node in the three-dimensional model. The configuration evolves along the time axis. Along the time axis, the changed parts are recorded. Using a search algorithm, the current configuration of the product and the technical status of individual configuration items are clear at any given time, ensuring the traceability of configuration data throughout the product's entire lifecycle. Step S22 specifically includes the following steps: S221: Construct a three-dimensional model for configuration change management that includes three dimensions: time, hierarchy, and node identifiers; S222: Record the nodes and their attributes in the model, as well as the changes in the configuration file; S223: The configuration baseline is changed synchronously after approval; S224: Use a search algorithm to search for configuration items or configuration trees at a certain time to trace configuration information. The search algorithm is a process of recursively traversing the product structure tree, and based on the time condition, by calling GetCI(ID,t) and GetCTree(IDs,t), obtaining the configuration items of each node and its child nodes level by level, and outputting the matching results. It is divided into search algorithm 1 for configuration item tracing and search algorithm 2 for configuration tree tracing.

9. The high-speed train product full life cycle configuration management method as described in claim 8, characterized in that: In step S223, once the configuration baseline is published, any changes must be made according to the following procedure: S2231: Request for amendment; the request for amendment shall include the reasons for the amendment and an analysis of its impact, and recommendations for the amendment; S2232: Impact Analysis; Analyze the impact of changes, specifically including the impact on attributes, nodes, and configuration files associated with nodes; S2233: Change Review; Review changes and record signature information; There are two types of review conclusions: if the review fails, the change application must be revised and returned to the change application submission step; if the review passes, the approval process begins. S2234: Change Approval; Conduct the change approval process and record the approval signature information; S2235: Change Implementation; Modify node-related information and release a new baseline version; complete the configuration baseline change through the control flow, release the new configuration baseline, and then update the configuration baseline attributes.

10. The high-speed train product full life cycle configuration management method as described in claim 9, characterized in that: The input to GetCI(ID,t) is the node ID and the time point t; the output is the configuration item of the node at time t (if it exists), otherwise it returns null. The input of GetCTree(IDs,t) is the IDs of the child nodes and the time point t; the output is the complete structure tree with the node as the top level; the internal implementation is: get the IDs of the node and all its direct child nodes, and for each child node, recursively call GetCTree(IDs,t) to obtain the substructure tree; The steps of search algorithm 1 are as follows: (1) Initialization; set the current search time... t Set as start time t s (2) Judgment and status query; Determine the current time t Is it less than the end time? t e ,like t < t e , call GetCI ( ID , t Get unique identifier ID and current time t Simultaneously matching configuration terms; if t ≥ t e If a matching record exists, the traversal ends; (3) Judgment and output; If a matching record exists, output the record, which contains the configuration item in t The time-to-date information, including attributes, version, and associated files; If no matching record is found, then the configuration item is determined to be in t If the time does not exist or has not changed, then the time will be... t Add a minimum time unit, then return to step (2) of search algorithm 1 and continue querying the state at the next time point; (4) end; summarize and output all historical state records obtained in step (3) of search algorithm 1, thus fully presenting the configuration item in t s to t e The trajectory of change over a period of time; The steps of search algorithm 2 are as follows: (1) Obtain the root node; call GetCI ( ID , t Get the specified ID The configuration term in time t The state; (2) Recursive traversal; Taking the root node configuration item with the specified ID as the root node, find all its child nodes; For each found child node, call GetCTree ( IDs , t Get child nodes IDs and the child node and its next-level nodes in time t The configuration item state is obtained, and the process ends after obtaining the configuration item states of all child nodes; (3) Output; All nodes, attributes and their relationships obtained in steps (1) and (2) of search algorithm 2 are arranged into a complete configuration tree state according to their original hierarchical structure, and the configuration tree is output to reflect the configuration item of the root node in time. t The complete technical status.

Images