Product full life cycle model construction method and system
By establishing a four-layer MDA architecture and model mapping relationship, the problem of poor communication in the full life cycle management of complex products is solved, cross-stage collaboration is realized, design efficiency and quality are improved, and system-level multi-scale definition is supported.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- 山东山大华天软件股份有限公司
- Filing Date
- 2022-05-17
- Publication Date
- 2026-04-28
AI Technical Summary
In existing technologies, the management of models at each stage of the entire life cycle of complex products suffers from problems such as poor interoperability, cumbersome interoperability, and difficulty in collaboration. The lack of cross-unit, cross-stage, and cross-level collaboration mechanisms makes it difficult to improve product design efficiency and quality.
It adopts a combination of meta-meta-models and meta-models, realizes the model mapping relationship through SysML and TGG methods, establishes a four-layer MDA architecture, defines meta-meta-models and meta-models, supports multi-view expression and rapid traceability, and realizes cross-stage collaborative management by using databases, knowledge bases and case libraries.
It enables visualization and traceability of the entire product lifecycle, improves design efficiency and quality, shortens the development cycle, supports system-level multi-scale definition of complex products, and meets the needs of efficient cross-unit, cross-stage, and cross-level collaboration mechanisms.
Smart Images
Figure CN121934816A_ABST
Abstract
Description
Technical Field
[0001] This invention belongs to the field of digital design technology, and in particular relates to a method and system for constructing a product lifecycle model. Background Technology
[0002] The statements in this section are merely background information related to the present invention and do not necessarily constitute prior art.
[0003] Currently, for complex products, the management model of static models and the independent management models and methods for each stage of the entire product lifecycle are generally adopted.
[0004] Currently, the product lifecycle management system uses a static model approach, relying on independent system platforms for each stage of the lifecycle. As the modeling level increases throughout the product lifecycle, complex relationships arise, including poor interoperability, cumbersome interoperability, and difficulties in collaboration. This hinders rapid improvement in product design efficiency and quality. Furthermore, the early system design phase lacks fundamental theoretical and platform support, resulting in the following problems: Currently, the expression of requirements, functions, and architecture in the early stages of product design is almost entirely based on document-level interaction.
[0005] There is a lack of unified expression for the models of each stage of the product lifecycle. Furthermore, there is a lack of efficient, model-based collaborative mechanisms across units, stages, and levels. Summary of the Invention
[0006] To overcome the shortcomings of the prior art, this invention provides a product lifecycle model construction method that ensures the semantic consistency of the entire product lifecycle, meets the requirements of efficient cross-unit, cross-stage, and cross-level collaborative mechanisms, supports system-level multi-scale definition of complex products, realizes visualization and traceability of the entire design process, and improves product quality.
[0007] To achieve the above objectives, one or more embodiments of the present invention provide the following technical solutions: Firstly, a method for constructing a product lifecycle model is disclosed, including: S1. Retrieve the meta-model from the database; extract the name, ID, description, model, quality, specifications, database ID parameters and their values to form the initial meta-model definition. S2. Based on SysML and the consistent input / output interface of the meta-meta-model, the meta-meta-model is assembled to form the meta-model definition. The meta-meta-model definition uses the item nodes in the meta-model to realize multi-view expression and rapid traceability of design information, data, knowledge and cases; the meta-model definition is associated with relevant knowledge. S3. Create a structured product requirement model based on meta-model combination; S4. Based on the attributes and relationship features of the meta-model and meta-meta-model, search for relevant instances in the design requirement instance library for the product structured requirement model; S5. Calculated through domain matching degree, i.e. in It is defined by customer requirements, Δd name , Δd id , Δd description , Δd type , Δd quality , Δd specification Δdata id These are the deviation values between the meta-model definition in MDA and the customer requirement definition, used to determine whether they match the requirement model; the model in MDA forms reference relationships with products, processes, organizations, and resources, and in defining specific product, process, organization, and resource instances, it can realize the establishment and mapping of MDA instances, enabling consistent modeling and collaborative management of the entire product lifecycle model; S6. If yes, add the instance to the set of requirement instances to be pushed; output the set of requirement instances and the requirement list; S7. If not, construct new product design requirement instances until they match the requirement model; specifically including: S71. Organize and conduct design requirements instance reviews; S72. Review passed, return to matching degree calculation, and execute steps S6 and S61; S73. If the review fails, return to step S7 and rebuild the design requirement instance.
[0008] Preferably, the meta-meta-model is used to describe component attributes and is the smallest granularity in the MDA composition; the meta-meta-model is associated with attribute features. The meta-meta-model is a meta-object in SysML, whose attributes include: name, ID, description, model, quality, specifications, database ID parameter and its value. At the same time, the input and output interfaces are defined in the meta-object to facilitate the assembly of the meta-meta-model.
[0009] Preferably, the meta-model includes components and their physical, behavioral, rule definitions and interrelationships; The metamodel definition is based on the unified modeling language and includes components, relationships, constraints, and modeling rules between them. The metamodel is defined based on the SysML modeling language, and the mapping relationship between other modeling languages and the metamodel is realized using the TGG method.
[0010] Preferably, the model is constructed based on the components and relationships in the meta-model and organized according to the business requirement template, supporting single-step or full-process, single-item or integrated model configuration and release.
[0011] Preferably, the database ID is associated with the meta-model, the knowledge base ID is associated with the meta-model, and the case library ID is associated with the model.
[0012] Secondly, a product lifecycle model building system is disclosed, which is based on a server-side application and configured to execute: Retrieve the meta-model from the database; A meta-model is created based on the combination of meta-meta-models to create a demand-oriented model; Create a structured product requirement model based on meta-model combination; Based on the attributes and relationship features of the meta-model and meta-meta-model, relevant instances are searched in the design requirement instance library for the product's structured requirement model; The domain matching degree is calculated to determine whether it matches the requirement model. If it does, the instance is included in the set of requirement instances to be pushed; the set of requirement instances and the requirement list are output. If not, construct new product design requirement instances until they match the requirement model.
[0013] Thirdly, a computer device is disclosed, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps of the above-described method.
[0014] Fourthly, a computer-readable storage medium is disclosed, on which a computer program is stored, which, when executed by a processor, performs the steps of the above-described method. The above one or more technical solutions have the following beneficial effects: In addition to the parametric model data in the detailed design process, this invention also includes six types of models: requirement model, functional model, product model, engineering model, manufacturing model, and implementation model. It uses digital means to achieve full product lifecycle management, including requirement definition, functional decomposition, engineering analysis, and manufacturing process analysis.
[0015] The model defined in this invention provides an open interface that can be integrated with other models. After the interface is defined, it can be further combined to form a larger model according to requirements.
[0016] The method of this invention establishes a database / knowledge base / case library to store a large amount of data resources, process knowledge and design cases. It realizes multi-view expression through models, which greatly improves the efficiency of complex product design and ensures the orderly accumulation and rapid retrieval of knowledge and cases.
[0017] This invention enables visualization and traceability of the entire product lifecycle management process, which improves design efficiency, ensures design quality, shortens the development cycle, and provides conditions for enterprise knowledge accumulation.
[0018] Advantages of additional aspects of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. Attached Figure Description
[0019] The accompanying drawings, which form part of this invention, are used to provide a further understanding of the invention. The illustrative embodiments of the invention and their descriptions are used to explain the invention and do not constitute an improper limitation of the invention.
[0020] Figure 1 This is a schematic diagram of the four-layer MDA model architecture according to an embodiment of the present invention; Figure 2 This is an example diagram defining a four-layer model according to an embodiment of the present invention; Figure 3 This invention provides six types of model diagrams supporting the entire product lifecycle in its embodiments. Figure 4 This is a schematic diagram illustrating the supporting role of each model in the embodiments of the present invention throughout the product lifecycle; Figure 5 This is a schematic diagram illustrating the relationship between the model in the four-layer MDA of this invention and the product lifecycle model. Detailed Implementation
[0021] It should be noted that the following detailed descriptions are exemplary and intended to provide further illustration of the invention. Unless otherwise specified, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains.
[0022] It should be noted that the terminology used herein is for the purpose of describing particular implementations only and is not intended to limit the exemplary implementations of the present invention.
[0023] Where there is no conflict, the embodiments and features in the embodiments of the present invention can be combined with each other.
[0024] The product lifecycle model construction method disclosed herein is applicable to the model construction of complex products. Complex products are those that use high technology, employ complex processes, have a large number of parts, have multiple product structure layers, have many changing relationships between parts and products, and have high value, such as modeling products like airplanes and vehicles.
[0025] In the development of complex products throughout their entire lifecycle, the unified quantitative description and modeling theories and technologies for each stage need improvement, the system integration is not high, and cross-disciplinary, cross-domain, and cross-stage collaboration is difficult. Therefore, it is necessary to solve key technical problems such as the basic theories and collaborative methods for the unified interconnection specifications of complex product lifecycle models.
[0026] The following section explains the basic concepts and construction process involved in model building.
[0027] Example 1 This embodiment discloses a method for constructing a product lifecycle model, including: Establishing an MDA: This architecture comprises four model layers, such as Figure 1 As shown, the instance layer (M0) consists of specific data of a concrete object; an instance is an instantiation of the model. The model layer (M1) is a template abstracted to describe specific business logic. The metamodel layer (M2) is an "abstract language" defined to describe the model layer, representing a further abstraction of the model layer; the model is an inheritance of the metamodel. The meta-metamodel layer (M3) is an "abstract language" defined to describe the metamodel; the metamodel is an inheritance of the meta-metamodel. An example of a four-layer model is given here, such as... Figure 2 As shown.
[0028] Model Definition: Defines model types and systems to meet different needs; provides all model definitions required for digital design modeling throughout the product lifecycle. The model is represented in BOM form and linked to relevant data instances throughout the product lifecycle.
[0029] Different lifecycle stages require models of different forms, granularities, and representations. Throughout the entire lifecycle of complex product development, six types of models—requirement models, functional models, product models, engineering models, manufacturing models, and implementation models—drive the development process. Figure 3 As shown. This involves establishing a data link throughout the entire product development process, enabling modeling of product design, integration verification, and product realization, and gradually building a systems engineering development model based on digitalization, networking, and intelligence. It addresses data tracking and management throughout the entire lifecycle, including requirements, design, simulation, manufacturing, assembly, testing, and operation. It supports the definition of the entire system, subsystems, and individual machines, and meets the storage requirements for all elements: standards, data, processes, algorithms, etc., enabling multi-dimensional business views such as spatial, temporal, and production / safety element dimensions. The supporting role of each model in the entire product lifecycle is as follows: Figure 4 As shown, this enables comprehensive technical status management throughout the product lifecycle and closed-loop verification across the system design, product design, and product implementation stages.
[0030] Defining the Metamodel: The metamodel includes the definitions of components and their physical properties, behaviors, rules, and interrelationships. From a modeling perspective, the metamodel defines components based on a unified modeling language, as well as the relationships, constraints, and modeling rules between them. The metamodel is defined using the SysML modeling language, and the TGG (Triple Graph Grammar) method is used to implement the mapping relationship between other modeling languages and the metamodel. Related knowledge is associated with the definition of the metamodel. The six major models mentioned above are formed by connecting multiple metamodels through the definition of relationships between them.
[0031] Define the meta-meta-model: The meta-meta-model describes component attributes and is the smallest granularity in the MDA composition. The meta-meta-model associates attribute characteristics, including name, material, weight, load, department, etc.
[0032] By organizing the data, knowledge, and instances throughout the entire product lifecycle through a four-layer model, the system can effectively organize them and meet the requirements of fine-grained collaboration.
[0033] The relationship between the model in the four-layer MDA and the product lifecycle model is defined as follows: Figure 5 As shown, the MDA establishes reference relationships between the model and products, processes, organizations, and resources. After defining specific product, process, organization, and resource instances, the establishment and mapping of MDA instances are realized based on the data association relationship between the MDA instances and the IDs (identifiers) of the product, process, organization, and resource instances. This enables consistent modeling and collaborative management of the product lifecycle model.
[0034] The Product Lifecycle Model (MBD) includes six types of models: requirements model, functional model, product model, engineering model, manufacturing model, and implementation model. These can be summarized into four parts: product, organization, resources, and process. Each part is represented by an MBD model, such as... Figure 5 As shown, the model is organized based on references to multiple metamodel IDs in the MDA.
[0035] In a specific embodiment, the collaborative complex product lifecycle model management method can meet the requirements for design instance matching and design solution push for demand models, including the following steps: Step S1: Retrieve the meta-model from the database and extract the name (d name ID(d) id ), description (d description ), model (d) type ), quality (d) quality Specifications (d) specification ), database ID (data id ) and their values form the initial meta-model definition (schema) i ), that is; schemai ={d name ,d id ,d description ,d type ,d quality ,d specification ,data id}; Step S2: Create a metamodel S for the requirement-oriented model based on the combination of meta-meta-models. j ={schema1,schema2,…,schema i}; Step S3: Create a structured product requirement model based on meta-model combination; R = {S1, S2, ..., S} j} Step S4: Based on the attributes and relationship features of the meta-model and meta-meta-model, search for relevant instances in the design requirement instance library for the product structured requirement model; Step S5: Calculate the domain matching degree (mea), i.e. in It is defined by customer requirements, Δd name , Δd id , Δd description , Δd type , Δd quality , Δd specification Δdata id The deviation values between the meta-model definition in MDA and the customer requirement definition are used to determine whether they match the requirement model. Step S6: If yes, add the instance to the set of demand instances to be pushed; Step S61: Output the set of requirement instances and the requirement list; Step S7: If not, construct a new product design requirement instance using expert knowledge; Step S71: Organize a design requirements instance review; Step S72: Review passed, return to matching degree calculation, and execute steps S6 and S61; Step S73: If the review fails, return to step S7 and rebuild the design requirement instance.
[0036] It has promoted the structural, digital, and consistent definition of the entire product lifecycle, starting from the concept stage, and improved the product's digitalization rate and design efficiency.
[0037] This disclosed technical solution can define a product lifecycle requirement model. Based on the meta-model, meta-model and ID reference relationship between models in MDA, it can realize the traceability of model data. It supports the definition of multiple types and fine-grained models. By adding or trimming ID reference relationships, it can achieve fast and efficient multi-view configuration, ensure the consistency of semantics throughout the product lifecycle, meet the needs of efficient cross-unit, cross-stage and cross-level collaboration mechanism, support system-level multi-scale definition of complex products, realize the visualization and traceability of the entire design process, and improve product quality.
[0038] This disclosed technical solution analyzes modeling languages for complex product system design from a model-driven perspective, and uses model expression and construction technologies to develop software components and enabling toolsets that support unified model management, model data feature association and matching, and intelligent retrieval and query functions; a knowledge base / database / case library for each stage of the complex product lifecycle; and a prototype system for complex product lifecycle model management that supports all aspects of design, analysis, manufacturing planning, and maintenance services.
[0039] Example 2 The purpose of this embodiment is to provide a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps of the above-described method.
[0040] Example 3 The purpose of this embodiment is to provide a computer-readable storage medium.
[0041] A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the steps of the above method.
[0042] Example 4 The purpose of this embodiment is to provide a second aspect of the present invention: a complex product lifecycle model management system that supports collaboration, implemented on a server, including: Model definition module: For the requirements of complex product lifecycle management, based on the components and relationships in the meta-model, it organizes and builds six types of models according to business requirement templates: requirement model, functional model, product model, engineering model, manufacturing model, and implementation model. It supports the configuration and release of models for single step or full process, single item or integrated, to meet the modeling requirements of product design, integration verification, and product implementation process. Database, Knowledge Base, and Case Library Modules: These modules comprise the system platform for product management, containing all component libraries, standard documents, components, databases, knowledge bases, case libraries, and programs linking to other platform modules. Database: Contains four types of development data: complex product design data, simulation data, manufacturing data, and test data, linked to the meta-model via database IDs. Knowledge Base: Contains six types of model knowledge: requirements models, functional models, product models, engineering models, manufacturing models, and implementation models for the entire lifecycle of complex products, linked to the meta-model via knowledge base IDs. Case Library: Contains four types of cases: design defect cases, product quality cases, process defect cases, and assembly quality cases, linked to the model via case library IDs.
[0043] Metamodel Definition Module: Based on the consistent input / output interface of SysML and meta-metamodel, the meta-metamodel is assembled to form the metamodel definition. The definition of the meta-metamodel utilizes the item nodes in the metamodel to achieve multi-view representation and rapid traceability of design information, data, knowledge, and cases; relevant knowledge is associated during the metamodel definition.
[0044] Meta-metamodel definition module: A meta-metamodel is a meta-object in SysML, whose attributes include parameters and values such as name, ID, description, model, quality, specifications, and database ID. Input and output interfaces are defined within the meta-object to facilitate the assembly of meta-metamodels. The association between the database and the meta-metamodel is established based on the database ID.
[0045] Based on the above modules, MDA is implemented to achieve visualization of the six major models that meet the needs of the entire product lifecycle, enabling multi-view expression and rapid traceability of design information, data, knowledge, and cases.
[0046] This embodiment illustrates the application of the method and system to a server. It is understood that the method can also be applied to terminals, and can be applied to systems including terminals, servers, and other components, and implemented through interaction between the terminal and the server. The server can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network servers, cloud communication, middleware services, domain name services, CDN security services, and big data and artificial intelligence platforms. The terminal can be a smartphone, tablet, laptop, desktop computer, etc., but is not limited to these. The terminal and server can be directly or indirectly connected via wired or wireless communication, which is not limited herein.
[0047] The steps and methods involved in the apparatuses of Embodiments 2, 3, and 4 above correspond to those in Embodiment 1. For specific implementation details, please refer to the relevant description section of Embodiment 1. The term "computer-readable storage medium" should be understood as a single medium or multiple media including one or more instruction sets; it should also be understood as including any medium capable of storing, encoding, or carrying an instruction set for execution by a processor and enabling the processor to perform any of the methods in this invention.
[0048] Those skilled in the art will understand that the modules or steps of the present invention described above can be implemented using general-purpose computer devices. Optionally, they can be implemented using computer-executable program code, thereby allowing them to be stored in a storage device for execution by a computer device, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. The present invention is not limited to any particular combination of hardware and software.
[0049] While the specific embodiments of the present invention have been described above in conjunction with the accompanying drawings, this is not intended to limit the scope of protection of the present invention. Those skilled in the art should understand that various modifications or variations that can be made by those skilled in the art without creative effort based on the technical solutions of the present invention are still within the scope of protection of the present invention.
Claims
1. A method for constructing a product lifecycle model, characterized in that, include: S1. Retrieve the meta-model from the database; extract the name, ID, description, model, quality, specifications, database ID parameters and their values to form the initial meta-model definition. S2. Based on the consistent input / output interface of SysML and meta-meta-model, the meta-meta-model is assembled to form the meta-model definition. The meta-meta-model definition realizes multi-view expression and rapid traceability of design information, data, knowledge and cases based on the item nodes in the meta-model; relevant knowledge is associated when defining the meta-model. S3. Create a structured product requirement model based on meta-model combination; S4. Based on the attributes and relationship features of the meta-model and meta-meta-model, search for relevant instances in the design requirement instance library for the product structured requirement model; S5. Calculate the domain matching degree, i.e. in It is defined by customer requirements, Δd name , Δd id , Δd description , Δd type , Δd quality , Δd specification Δdata id These are the deviation values between the meta-model definition in MDA and the customer requirement definition, used to determine whether they match the requirement model; the model in MDA forms a reference relationship with products, processes, organizations, and resources, and in defining specific product, process, organization, and resource instances, it can realize the establishment and mapping of MDA instances, and realize consistent modeling and collaborative management of the entire product lifecycle model; S6. If so, add the instance to the set of demand instances to be pushed; Output a collection of requirement instances and a list of requirements; S7. If not, construct new product design requirement instances until they match the requirement model; specifically including: S71. Organize and conduct design requirements instance reviews; S72. Review passed, return to matching degree calculation, and execute steps S6 and S61; S73. If the review fails, return to step S7 and rebuild the design requirement instance.
2. The product lifecycle model construction method as described in claim 1, characterized in that, The meta-meta-model is used to describe component attributes and is the smallest granularity in the composition of MDA. The meta-meta-model is associated with attribute features. The meta-meta-model is a meta-object in SysML, whose attributes include: name, ID, description, model, quality, specifications, database ID parameter and its value. At the same time, the input and output interfaces are defined in the meta-object to facilitate the assembly of the meta-meta-model.
3. The product lifecycle model construction method as described in claim 1, characterized in that, The metamodel includes components and their physical, behavioral, rule definitions and interrelationships; The metamodel definition is based on the unified modeling language and includes components, relationships, constraints, and modeling rules between them. The metamodel is defined based on the SysML modeling language, and the mapping relationship between other modeling languages and the metamodel is realized using the TGG method.
4. The product lifecycle model construction method as described in claim 1, characterized in that, Based on the components and relationships in the meta-model, the model is organized and constructed according to the business requirement template, supporting the configuration and release of models in single-step or full-process, single-item or integrated manner.
5. The product lifecycle model construction method as described in claim 1, characterized in that, The database ID is used to associate with the meta-model, the knowledge base ID is used to associate with the meta-model, and the case library ID is used to associate with the model.
6. A product lifecycle model construction system, implemented on a server, characterized in that, Configured to execute: Retrieve the meta-model from the database; A meta-model is created based on the combination of meta-meta-models to create a demand-oriented model; Create a structured product requirement model based on meta-model combination; Based on the attributes and relationship features of the meta-model and meta-meta-model, relevant instances are searched in the design requirement instance library for the product's structured requirement model; The domain matching degree is calculated to determine whether it matches the requirement model. If it does, the instance is included in the set of requirement instances to be pushed; the set of requirement instances and the requirement list are output. If not, construct new product design requirement instances until they match the requirement model.
7. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the steps of the method described in any one of claims 1-5.
8. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it performs the steps of the method described in any one of claims 1-5 above.