Equipment digital main line construction method based on product breakdown structure

Abstract

The application belongs to the technical field of equipment digital modeling, and particularly relates to an equipment digital main line construction method based on product decomposition structure. The method comprises the following steps: constructing an aircraft forward research and development global data architecture based on an aircraft product decomposition structure, decomposing the aircraft product into a multi-layer structure, each layer comprising a requirement transmission data chain, a product research and development data chain and a requirement verification data chain; determining the requirement transmission relationship of each layer for the requirement transmission process, and penetrating the requirement transmission data chain of each layer from top to bottom; determining the interaction relationship between the task domain, scheme domain, product domain, manufacturing domain and support domain of each layer for the product research and development process, and establishing a product research and development data chain penetrating the whole process; and establishing a requirement verification data chain connecting the requirement verification method, requirement verification task, requirement verification scene and requirement verification result for the requirement verification process. The application can realize global correlation analysis of the aircraft research and development whole-process model data.

Description

TECHNICAL FIELD

[0001] The application belongs to the technical field of equipment digital modeling, and particularly relates to an equipment digital main line construction method based on product decomposition structure. BACKGROUND

[0002] At present, digital technology is widely used in various links of research and development of complex equipment such as aircraft to assist research and development, and a large amount of digital models and data are generated. However, the model data of different stages and different business processes of aircraft research and development lack a unified data management framework, and the data across stages and business domains lack correlation, which leads to difficulty in continuous transmission of research and development data and models, difficulty in consistency control and traceability analysis of data of different business processes, and influence on research and development design iteration efficiency and consistency of technical state. SUMMARY

[0003] In order to solve the above problems, the application provides an equipment digital main line construction method based on product decomposition structure, which aims to establish a research and development digital main line through task domain, scheme domain, product domain, manufacturing domain and support domain, so as to solve the organization and management, correlation analysis and traceability of model data of different business domains in the whole research and development process, and improve the research and development design iteration efficiency and data correlation analysis capability.

[0004] The equipment digital main line construction method based on product decomposition structure of the application mainly includes:

[0005] Step S1, constructing an aircraft forward research and development global data architecture based on an aircraft product decomposition structure, wherein the aircraft forward research and development global data architecture is decomposed into a multi-layer structure according to an aircraft product, each layer includes a requirement transmission data chain, a product research and development data chain and a requirement verification data chain;

[0006] Step S2, for the requirement transmission process, determining the requirement transmission relationship of each layer from the problem domain to the solution scheme domain, and penetrating the requirement transmission data chain of each layer from top to bottom;

[0007] Step S3, for the product research and development process, determining the interaction relationship between the task domain, the scheme domain, the product domain, the manufacturing domain and the support domain of each layer, and establishing a product research and development data chain penetrating the whole process;

[0008] Step S4, for the requirement verification process, carrying out requirement closed-loop control data chain design, and establishing a requirement verification data chain connecting the requirement verification method, the requirement verification task, the requirement verification scene and the requirement verification result.

[0009] Preferably, step S1 further includes:

[0010] Step S11: Divide the aircraft equipment system into equipment system level, equipment level, system level, subsystem level and equipment level from top to bottom, and establish the aircraft product decomposition structure;

[0011] Step S12: For each level of the aircraft product decomposition structure, further add a requirement transmission data chain, a product development data chain, and a requirement verification data chain;

[0012] Step S13: For each level of the aircraft product decomposition structure, determine the meta-model of the relationship between the requirement transmission data chain, the product development data chain, and the requirement verification data chain, thereby establishing the global data architecture for the forward development of the aircraft.

[0013] Preferably, step S13 further includes:

[0014] For the demand transmission data chain and the product development data chain, with demand as the center, the relationship between the demand in the demand transmission data chain and the functional units, logical units, product units, support processes and support resources in the product development data chain is established according to the evolution process of the demand.

[0015] For the requirement delivery data chain and the requirement verification data chain, with the requirement as the center, according to the verification relationship of the requirement, the association relationship between the requirement in the requirement delivery data chain and the verification method and verification task in the requirement verification data chain is established respectively.

[0016] For the product development data chain and the requirement verification data chain, taking the design objects of each stage of product development as the center, establish the association between the verification tasks in the requirement verification data chain and the functional units, logical units, product units and assurance processes in the product development data chain.

[0017] Preferably, step S2 further includes:

[0018] Step S21: For each level, refine and decompose the requirements assigned to this level by the level above it to establish the top-level requirements for this level.

[0019] Step S22: Assign the top-level requirements to the next level of this level, and add the derivative requirements generated by the introduction of the specified solution. Establish the bottom-level requirements of this level based on the derivative requirements.

[0020] Step S23: Establish the relationship between top-level requirements and bottom-level requirements at the same level.

[0021] Preferably, step S2 further includes:

[0022] Step S24, the quantification index identification and importance level division of each level requirement are carried out in turn from top to bottom, and a key characteristic index transmission chain from the top-level capability index to the bottom-level equipment-level technology index is established.

[0023] Preferably, step S3 further comprises:

[0024] Step S31, in the task domain, a task architecture of the aircraft equipment system is established, an equipment system capability tree of the aircraft is established according to the requirement of the equipment capability for the task, and the dependency relationship between the equipment system capabilities and the support relationship between the equipment system capability and the task are determined;

[0025] Step S32, in the scheme domain, the function architecture, the logic architecture and the physical architecture are respectively established according to the requirements of each level, the function composition and the interaction relationship, the logic composition and the interaction relationship, and the physical composition and the interaction relationship of the level are determined, and the association relationship between the function architecture and the equipment system capability tree is established;

[0026] Step S33, in the product domain, a product structure tree is established according to the actual product composition relationship, the composition and the interaction relationship of each level of the product are determined, and the association relationship between the product structure tree and the physical architecture is established;

[0027] Step S34, in the manufacturing domain, a process structure tree and a real installation structure tree are established in turn according to the product manufacturing process scheme and the actual manufacturing process, the manufacturing division and the actual installation state of each level of the product are determined, the association relationship between the process structure tree and the product structure tree is established, and the association relationship between the real installation structure tree and the process structure tree is established;

[0028] Step S35, in the support domain, a support structure tree is established according to the physical architecture and the product structure tree composition, the fault mode, the support task and the required support resource of each level of the product are determined, and the association relationship between the support structure tree and the function architecture, the physical architecture and the product structure tree is respectively established.

[0029] Preferably, in step S35, the establishment of the support structure tree further comprises:

[0030] Taking the fault closed-loop control process as the core, the association relationship between the fault closed-loop control process and the function architecture and the physical architecture is established, the data source of fault identification, analysis and test is determined, the association relationship between the fault closed-loop control process and the support task is established, the support task for fault prevention and disposal is determined, the association relationship between the fault closed-loop control process and the support resource is established, and various types of equipment, technical publications and station equipment resources required for analysis of the support process are determined.

[0031] Preferably, step S4 further comprises:

[0032] Step S41, determining an initial verification task for the top-level requirement of the product hierarchy;

[0033] Step S42, establishing a requirement verification tree containing product hierarchy verification tasks according to the initial verification task;

[0034] Step S43, for each hierarchy verification task in the requirement verification tree, establishing three types of data tags of verification object, verification scenario and verification result;

[0035] Step S44, under the data tag of verification object, establishing the association relationship between functions, logics, physics or products in the product R&D data chain.

[0036] For the whole process of digital R&D of complex equipment such as aircraft, the application establishes a unified aircraft R&D data architecture based on product decomposition structure, first proposes a method of establishing R&D digital main line from three dimensions of requirement transfer, product R&D and requirement verification, realizes unified organization, through management and correlation analysis of data models from task domain, scheme domain, product domain, manufacturing domain and support domain, improves the efficiency of continuous data transfer and data consistency of R&D whole life cycle model, and can realize global correlation analysis of model data in the whole process of aircraft R&D. BRIEF DESCRIPTION OF DRAWINGS

[0037] Figure 1 is a flowchart of a preferred embodiment of the equipment digital main line construction method based on product decomposition structure of the application.

[0038] Figure 2 is a schematic diagram of the framework of aircraft R&D digital main line based on product decomposition structure.

[0039] Figure 3 is a schematic diagram of the core data model of the requirement transfer data chain.

[0040] Figure 4 is a schematic diagram of the core data model of the product R&D data chain.

[0041] Figure 5 is a schematic diagram of the core data model of the requirement verification data chain. DETAILED DESCRIPTION

[0042] For the purposes of making the objectives, technical solutions and advantages of the present application clearer, the technical solutions in the embodiments of the present application will be described in more detail below with reference to the drawings in the embodiments of the present application. Identical or similar reference numerals in the drawings represent identical or similar elements or elements with identical or similar functions throughout. The described embodiments are part of the embodiments of the present application, rather than all the embodiments of the present application. The embodiments described below with reference to the drawings are exemplary and are intended to serve to explain the present application, and cannot be understood as a limitation on the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work are within the scope of protection of the present application. The embodiments of the present application will be described in detail below with reference to the drawings.

[0043] The present application provides a method for constructing a digital main line of equipment based on a product breakdown structure, as shown in the figure, mainly comprising: Figure 1

[0044] Step S1, constructing an aircraft forward R&D global data architecture based on an aircraft product breakdown structure, the aircraft forward R&D global data architecture being broken down into a multi-layer structure according to the aircraft product, each layer including a requirement transfer data chain, a product R&D data chain and a requirement verification data chain;

[0045] Step S2, for the requirement transfer process, determining the requirement transfer relationship of each layer from the problem domain to the solution domain, and penetrating the requirement transfer data chain of each layer from top to bottom;

[0046] Step S3, for the product R&D process, determining the interaction relationship between the task domain, the scheme domain, the product domain, the manufacturing domain and the support domain of each layer, and establishing a product R&D data chain penetrating the whole process;

[0047] Step S4, for the requirement verification process, carrying out requirement closed-loop control data chain design, and establishing a requirement verification data chain connecting the requirement verification method, the requirement verification task, the requirement verification scene and the requirement verification result.

[0048] The present application first increases the requirement transfer data chain, the product R&D data chain and the requirement verification data chain on the basis of the aircraft product structure tree in step S1, constructs the aircraft forward R&D global data architecture, and then in steps S2-S4, respectively for the three data chains, associates each node between the same layer or different layers, forms a R&D digital main line including three dimensions of requirement transfer, product R&D and requirement verification, and realizes global association analysis of the aircraft R&D whole-process model data, which will be described in detail below.

[0049] Step S1 is used for the aircraft forward R&D global data architecture, and in some optional embodiments, step S1 further comprises: ​

[0050] Step S11, top-down division of the aircraft equipment system into equipment system level, equipment level, system level, subsystem level and device level, establishment of the aircraft product breakdown structure;

[0051] Step S12, for each level of the aircraft product breakdown structure, further increase the requirement transmission data chain, product development data chain and requirement verification data chain;

[0052] Step S13, for each level of the aircraft product breakdown structure, determine the association relationship meta-model between the requirement transmission data chain, the product development data chain and the requirement verification data chain, thereby establishing the aircraft forward development global data architecture.

[0053] In this embodiment, as shown in Figure 2 the first step S11, according to the aircraft equipment system integration relationship, top-down division of the aircraft equipment system into equipment system level, equipment level, system level, subsystem level and device level, establishment of the aircraft product breakdown structure. Among them, when defining the product breakdown structure according to the aircraft equipment system integration relationship, the nodes in the product breakdown structure are divided into two types: entity nodes and organization nodes. If the development process needs to carry out demand analysis, product design and demand verification and other specific business activities at this node, it is divided into an entity node, and the node needs to include the business data of the demand, design and verification activities of this level; If the development process does not need to carry out demand analysis, product design and demand verification and other specific business activities at this node, it is only used as a product unit organization management, it is divided into an organization node, and the node does not include specific business data, and directly transmits data to the lower level product structure unit in the digital main line construction process.

[0054] After that, in step S12, at each level of the aircraft product breakdown structure or the entity node given in the above embodiment, three data chains of requirement transmission, product development and requirement verification are added. Finally in S13, the association relationship meta-model between the requirement transmission data chain, the product development data chain and the requirement verification data chain is determined.

[0055] In some optional embodiments, step S13 further comprises:

[0056] For the requirement transmission data chain and the product development data chain, the association relationship between the requirements in the requirement transmission data chain and the functional units, logical units, product units, guarantee processes and guarantee resources in the product development data chain is established according to the evolution process of the requirements.

[0057] According to the demand transmission data chain and the demand verification data chain, a correlation between the demand in the demand transmission data chain and the verification method and the verification task in the demand verification data chain is established according to the verification relationship of the demand.

[0058] According to the product research and development data chain and the demand verification data chain, a correlation between the verification task in the demand verification data chain and the functional unit, the logic unit, the product unit and the guarantee process in the product research and development data chain is established.

[0059] In this embodiment, the correlation relationship meta-model between the demand transmission data chain and the product research and development data chain is taken as the center, the correlation relationship is defined according to the demand, the correlation relationship between the demand and the functional unit, the demand and the logic unit, the demand and the product unit, the demand and the guarantee process, the demand and the guarantee resource and other business data is established according to the evolution process of the demand, which is used for traceability analysis and rapid iteration of the demand design implementation process; the correlation relationship meta-model between the demand transmission data chain and the demand verification data chain is taken as the center, the correlation relationship meta-model is defined according to the demand, the correlation relationship between the demand and the verification method and the verification task is established according to the verification relationship of the demand, which is used for traceability analysis and rapid iteration of the demand verification process; similarly, the correlation relationship meta-model between the product research and development data chain and the demand verification data chain is taken as the center, the correlation relationship meta-model is defined according to the design object of each stage of the product research and development, the correlation relationship between the verification task and the functional unit, the logic unit, the product unit and the guarantee process is established, which is used for traceability analysis and rapid iteration of the design, simulation and test.

[0060] After the top framework is constructed, step S2 begins to design the demand transmission data chain in detail.

[0061] In some optional embodiments, step S2 further includes:

[0062] Step S21, for each level, the last level of the level is assigned to the demand of the level to refine and decompose, and the top-level demand of the level is established;

[0063] Step S22, the top-level demand is assigned to the next level of the level, and the derived demand generated due to the introduction of the specified solution is increased, and the bottom-level demand of the level is established according to the derived demand;

[0064] Step S23, the correlation relationship between the top-level demand and the bottom-level demand of the same level is established.

[0065] In this embodiment, as Figure 3As shown, first, the refinement decomposition of requirements is performed through step S21, for each product decomposition structure level, the requirements of the level are refined and decomposed according to the requirements allocated to the level from the upper level, combined with the operation scene analysis and knowledge experience of the level, the top-level requirements of the level are established, and the specific design scheme of the product level is not considered in the process. Then in step S22, according to the top-level requirements of the level, the top-level requirements are allocated to the product units of the next level of the product decomposition structure according to the design scheme of the level, and the derived requirements due to the introduction of specific solutions are added, the bottom-level requirements of the level are established, for example, the top-level requirement allocated to a structural member is "load bearing capacity", the structural member can adopt two schemes of metal structure and composite material structure, if the composite material scheme is selected, the derived requirement of "preventing the cracking of the matrix and the ply of the composite material" is added, if the metal scheme is selected, the derived requirement does not exist, the derived requirements related to such solution schemes are included in the bottom-level requirements. Finally, in step S23, the association relationship between the top-level requirements and the bottom-level requirements of the product units of the level is established, and the association relationship type is identified in the association relationship attribute, including the composition relationship, the allocation relationship or the derived relationship, etc., so as to establish the requirement transmission data chain of the product level from the problem domain to the solution domain. According to the above method, the association relationship between the requirements of each level is defined in turn, and the requirement transmission data chain of the entire aircraft equipment system is established.

[0066] In some optional embodiments, step S2 further includes:

[0067] Step S24, the quantitative index identification and importance level division in each level requirement are carried out in turn from top to bottom, and the critical characteristic index transmission chain from the top-level capability index to the bottom-level equipment-level technical index is established.

[0068] In this embodiment, the critical characteristic index transmission chain is further added on the basis of the requirement transmission data chain. The critical characteristic index transmission chain refers to the control process of decomposing the key characteristics and important characteristics from the system level to each unit node in the product design, manufacturing and testing process. Its core is to clarify the key links affecting the product quality through transmission coefficient analysis and characteristic classification, and to ensure the effectiveness of quality control.

[0069] First, at the equipment system level, the quantitative indexes in the equipment system capability requirements are identified, and the capability indexes are divided into three levels of key, important and general according to the influence degree on the success of the equipment mission task, for example, the quantitative indexes in the aircraft equipment system capability requirements are flight performance, detection distance, radar cross section, and transfer scale, etc., if the aircraft mainly performs a certain set task, "radar cross section" and "detection distance" are most important to the set task, then the two indexes are classified as key indexes.

[0070] At the next level of the equipment system, i.e., the equipment level, the quantitative indicators in the top-level requirement of the equipment are identified, the correlation with the capability indicators at the equipment system level is established, the importance level of the indicators at the equipment level is determined in combination with the importance level of the capability indicators at the equipment system level and the influence on the safety of the equipment, and the importance level also includes three levels of key, important and general. According to the above method, the identification of the quantitative indicators in the requirement of each product decomposition structure level and the division of the importance level are sequentially carried out, and the parameter chain from the top-level capability indicator to the bottom-level equipment-level technical indicator is established, which is used for the quantitative analysis and hierarchical control of the requirement.

[0071] The requirement quantitative analysis and control based on the importance level mainly refers to determining the priority of the related requirement item and the influence range of the engineering change according to the importance level of the indicator. For example, the indicator of "radar reflection cross section" belongs to the key indicator, and therefore the priority of the low radar reflection cross section capability requirement is defined as "high". If the requirement is changed during the research and development process, it needs to be submitted to the highest management institution for approval.

[0072] Then, the detailed design of the product research and development data chain is carried out in step S3. In some optional embodiments, step S3 further includes:

[0073] Step S31, in the task domain, a task architecture of the aircraft equipment system is established, an equipment system capability tree of the aircraft is established according to the requirement of the task on the equipment capability, and the dependency relationship between the equipment system capabilities and the support relationship between the equipment system capability and the task are determined;

[0074] Step S32, in the scheme domain, the functional architecture, the logical architecture and the physical architecture are respectively established according to the requirements at each level, the functional composition and the interaction relationship, the logical composition and the interaction relationship, and the physical composition and the interaction relationship of the level are determined, and the correlation between the functional architecture and the equipment system capability tree is established;

[0075] Step S33, in the product domain, a product structure tree is established according to the actual product composition relationship, the composition and the interaction relationship of each level of the product are clarified, and the correlation between the product structure tree and the physical architecture is established;

[0076] Step S34, in the manufacturing domain, a process structure tree and a real installation structure tree are sequentially established according to the product manufacturing process scheme and the actual manufacturing process, the manufacturing division and the actual installation state of each level of the product are determined, the correlation between the process structure tree and the product structure tree is established, and the correlation between the real installation structure tree and the process structure tree is established;

[0077] Step S35: In the protection domain, based on the physical architecture and product structure tree, establish a protection structure tree, determine the failure modes, protection tasks and required protection resources of each level of the product, and establish the association between the protection structure tree and the functional architecture, physical architecture and product structure tree respectively.

[0078] In this embodiment, reference Figure 4 In the mission domain, the mission architecture of the aircraft equipment system is established around the mission of the aircraft, the mission of the equipment is clarified and the interaction relationship between the equipment is defined. According to the mission requirements for the equipment capabilities, the capability tree of the aircraft equipment system is established, the dependency relationship between the capabilities of each equipment system and the support relationship between the capability and the mission are defined. For example, the long-range airborne mission architecture includes capabilities such as "long-range flight", "cargo loading" and "personnel airborne", among which the realization of the "personnel airborne" capability must depend on the "long-range flight" capability.

[0079] In the solution domain, functional architecture, logical architecture, and physical architecture were established, and the interaction relationships between them were clarified. For example, the "long-range flight" capability was further decomposed into functional units such as "providing aircraft control", "providing ground control", "providing energy", and "providing safety protection" in the aircraft functional architecture. The "providing aircraft control" functional unit was further decomposed and allocated to physical systems such as "flight control system" and "landing gear control" in the aircraft physical architecture, until it was allocated to the smallest off-the-shelf products such as "flight control computer" and "brake device". At the same time, the inter-linkage relationship between physical devices such as "flight control computer" and "brake device" was established.

[0080] In the product domain, a product structure tree (EBOM, i.e., Engineering Bill of Materials) is established to clarify the equipment / software / module composition and interaction relationships at the product level, and to establish the relationship between the product structure tree and the physical architecture. For example, the "braking device" in the physical architecture is refined into specific installation elements such as "brake operation unit", "brake sensor unit", and "brake control unit" during the product design process.

[0081] In the manufacturing domain, a process structure tree (MBOM, Production Bill of Materials) and an installation structure tree (BBOM, Equipment Bill of Materials) were established, and the relationships between the structure trees were established. For example, process units such as equipment delivery, installation, and ground testing for "brake device" were established in the MBOM, and the installation elements of "brake device" in the product structure tree were assigned to the corresponding units in the process structure tree to establish a mapping relationship.

[0082] Within the support domain, a support structure tree has been established, clearly defining the failure modes, support tasks, and required support resources such as support equipment and technical publications for that product level.

[0083] In some alternative implementations, step S35, establishing the protection structure tree, further includes:

[0084] The fault closed-loop control process is the core of the support structure tree. The fault closed-loop control process is associated with the functional architecture and the physical architecture outside the support structure tree, forms the support objects inside the support structure tree, and is also associated with the support tasks and the support resources inside the support structure tree. When the association relationship between the support structure tree and the functional architecture and the physical architecture outside the support structure tree is constructed, the data sources for fault identification, analysis, and testing can be determined. For example, the fault of "ground control failure" needs to be associated with the function of "providing ground control function" in the functional architecture of the aircraft and needs to be associated with the physical device of "brake device" in the physical architecture of the aircraft to identify the specific object to which the failure mode is directed. When the association relationship between the support tasks and the faults inside the support structure tree is constructed, the support tasks for fault prevention and disposal can be determined. For example, the fault of "ground control failure" is associated with the task of "pre-takeoff ground check" to determine that the task needs to detect the possible faults and their causes of "ground control failure". When the association relationship between the support resources inside the support structure tree is constructed, various types of equipment, technical publications, and station equipment resources required for the analysis of the support process can be determined. For example, the task of "pre-takeoff ground check" needs the support of ground support equipment and ground personnel during the execution process, and therefore the association relationship with the corresponding ground support equipment or ground personnel needs to be established.

[0085] In this embodiment, the core of the support structure tree is the fault closed-loop control process. The control process is associated with the functional architecture and the physical architecture outside the support structure tree, forms the support objects inside the support structure tree, and is also associated with the support tasks and the support resources inside the support structure tree. When the association relationship between the support structure tree and the functional architecture and the physical architecture outside the support structure tree is constructed, the data sources for fault identification, analysis, and testing can be determined. For example, the fault of "ground control failure" needs to be associated with the function of "providing ground control function" in the functional architecture of the aircraft and needs to be associated with the physical device of "brake device" in the physical architecture of the aircraft to identify the specific object to which the failure mode is directed. When the association relationship between the support tasks and the faults inside the support structure tree is constructed, the support tasks for fault prevention and disposal can be determined. For example, the fault of "ground control failure" is associated with the task of "pre-takeoff ground check" to determine that the task needs to detect the possible faults and their causes of "ground control failure". When the association relationship between the support resources inside the support structure tree is constructed, various types of equipment, technical publications, and station equipment resources required for the analysis of the support process can be determined. For example, the task of "pre-takeoff ground check" needs the support of ground support equipment and ground personnel during the execution process, and therefore the association relationship with the corresponding ground support equipment or ground personnel needs to be established.

[0086] Finally, in step S4, a detailed design of the requirement verification data chain is performed. In some optional embodiments, step S4 further includes:

[0087] Step S41, determining an initial verification task for the top-level requirement of the product hierarchy;

[0088] Step S42, establishing a requirement verification tree containing product hierarchy verification tasks according to the initial verification task;

[0089] Step S43, establishing three types of data tags of verification objects, verification scenarios, and verification results for each hierarchy verification task in the requirement verification tree;

[0090] Step S44, establishing the association relationship between the functions, logics, physicals, or products in the product research and development data chain under the data tag of verification objects.

[0091] ReferenceFigure 5 In this embodiment, firstly, the requirement compliance verification method definition is carried out for the top-level requirements of the product hierarchy, and the initial verification tasks are determined according to the compliance verification method, i.e. Figure 5 the "verification tasks" under the "requirements" node. Then, the verification tasks of all top-level requirements are effectively organized, the requirement verification tree of the product hierarchy is established, and the association between the primary verification tasks and the requirement verification tree is determined, that is, the relationship between the "verification tasks" under the "requirements" node and the "verification tasks" under the "requirement verification tree" node is determined, for example, the initial verification task formed for the "ground control" functional requirement in the requirement tree, two-level verification tasks of "landing gear brake simulation verification" and "landing gear turning simulation verification" are planned in the verification task tree, and the relationship between the initial verification task corresponding to the requirement and the two-level verification tasks is established.

[0092] Then, based on the requirement verification tree, the requirement verification data is organized and managed, the requirement verification confirmation and evidence chain are established, the verification tasks are divided into simulation and test two categories, for the simulation task, three types of data tags of simulation object, simulation scene and simulation result are established, which are respectively used to organize the design data to which the verification is directed, the environmental condition data contained in the simulation and the result data of the simulation; for the test task, three types of data tags of test object, test scene and test result are established, which are respectively used to organize the design data to which the test is directed, the environmental condition data contained in the test and the result data of the test. Finally, under the simulation object and test object data tags, the functional object, logic object, physical object or product object in the product development data chain is referenced, and the association between the simulation task, test and design object is established.

[0093] The above is only a specific embodiment of the present application, but the protection scope of the present application is not limited thereto, any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered in the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A method for constructing a digital masterline based on a product breakdown structure, characterized in that, Comprise: Step S1, constructing an aircraft forward research and development global data architecture based on an aircraft product decomposition structure, the aircraft forward research and development global data architecture being decomposed into a multi-layer structure according to the aircraft product, each level comprising a requirement passing data chain, a product research and development data chain and a requirement verification data chain; Step S2, for the requirement passing process, determining the requirement passing relationship of each level from the problem domain to the solution domain, and passing through the requirement passing data chain of each level from top to bottom; Step S3, for the product research and development process, determining the interaction relationship between the task domain, the scheme domain, the product domain, the manufacturing domain and the guarantee domain of each level, and establishing a product research and development data chain passing through the whole process; Step S4, for the requirement verification process, carrying out requirement closed-loop control data chain design, and establishing a requirement verification data chain connecting the requirement verification method, the requirement verification task, the requirement verification scene and the requirement verification result; Wherein, step S1 further comprises: Step S11, dividing the aircraft equipment system into equipment system level, equipment level, system level, subsystem level and device level from top to bottom, and establishing an aircraft product decomposition structure; Step S12, for each level of the aircraft product decomposition structure, further adding a requirement passing data chain, a product research and development data chain and a requirement verification data chain; Step S13, for each level of the aircraft product decomposition structure, determining the association relationship meta-model between the requirement passing data chain, the product research and development data chain and the requirement verification data chain, thereby establishing the aircraft forward research and development global data architecture; Step S13 further comprises: For the requirement passing data chain and the product research and development data chain, taking the requirement as the center, and respectively establishing the association relationship between the requirement in the requirement passing data chain and the functional unit, the logic unit, the product unit, the guarantee process and the guarantee resource in the product research and development data chain according to the evolution process of the requirement; For the requirement passing data chain and the requirement verification data chain, taking the requirement as the center, and respectively establishing the association relationship between the requirement in the requirement passing data chain and the verification method and the verification task in the requirement verification data chain according to the verification relationship of the requirement; For the product research and development data chain and the requirement verification data chain, taking the design object of each stage of product research and development as the center, and establishing the association relationship between the verification task in the requirement verification data chain and the functional unit, the logic unit, the product unit and the guarantee process in the product research and development data chain.

2. The equipment digital masterline construction method based on product breakdown structure according to claim 1, wherein, Step S2 further comprises: Step S21, for each level, assigning the last level of the level to the requirement of the level for refined decomposition, and establishing the top-level requirement of the level; Step S22, assigning the top-level requirement to the next level of the level, and increasing the derived requirement generated due to the introduction of the specified solution, and establishing the bottom-level requirement of the level according to the derived requirement; Step S23, establishing the association relationship between the top-level requirement and the bottom-level requirement of the same level.

3. The equipment digital masterline construction method based on product breakdown structure according to claim 2, wherein, Step S2 further comprises: Step S24, sequentially carrying out the identification of quantitative indicators and the classification of importance levels in the requirements of each level from top to bottom, and establishing a critical characteristic indicator passing chain from the top-level capability indicator to the bottom-level device-level technical indicator.

4. The equipment digital masterline construction method based on product breakdown structure according to claim 1, wherein, Step S3 further comprises: Step S31, in the task domain, establishing a task architecture of the aircraft equipment system, establishing an equipment system capability tree of the aircraft according to the requirement of the task on the equipment capability, determining the dependency relationship between each equipment system capability and the support relationship between the equipment system capability and the task; Step S32, in the scheme domain, respectively establishing a function architecture, a logic architecture and a physical architecture according to the requirement of each level, determining the function composition and interaction relationship, the logic composition and interaction relationship, the physical composition and interaction relationship of the level, and establishing the association relationship between the function architecture and the equipment system capability tree; Step S33, in the product domain, establishing a product structure tree according to the actual product composition relationship, determining the composition and interaction relationship of each level of the product, and establishing the association relationship between the product structure tree and the physical architecture; Step S34, in the manufacturing domain, according to the product manufacturing process scheme and the actual manufacturing process, successively establishing a process structure tree and an installation structure tree, determining the manufacturing division and the actual installation state of each level of the product, establishing the association relationship between the process structure tree and the product structure tree, and establishing the association relationship between the installation structure tree and the process structure tree; Step S35, in the support domain, according to the physical architecture and the product structure tree composition, establishing a support structure tree, determining the fault mode, the support task and the required support resource of each level of the product, and respectively establishing the association relationship between the support structure tree and the function architecture, the physical architecture and the product structure tree.

5. The equipment digital masterline construction method based on product breakdown structure according to claim 4, wherein, In step S35, the establishment of the support structure tree further comprises: Taking the fault closed-loop control process as the core, establishing the association relationship with the function architecture and the physical architecture, determining the data source of fault identification, analysis and test; establishing the association relationship with the support task, determining the support task for fault prevention and disposal; and establishing the association relationship with the support resource, determining various types of equipment, technical publications and station equipment resources required for analyzing the support process.

6. The equipment digital masterline construction method based on product breakdown structure according to claim 1, wherein, Step S4 further comprises: Step S41, determining an initial verification task for the top-level requirement of the product level; Step S42, establishing a requirement verification tree containing the product level verification task according to the initial verification task; Step S43, for each level verification task in the requirement verification tree, establishing three types of data tags of verification object, verification scene and verification result; Step S44, under the data tag of verification object, establishing the association relationship between the function, logic, physics or product in the product research and development data chain.

Images