Aerospace component revision management using product lifecycle management system

Abstract

A method is provided for generating a dynamic Engineering Bill of Materials (EBOM) in a Project Lifecycle Management (PLM) system. The method includes obtaining product data associated with a product having one or more parts, the product data including at least one of part name data, part identifier (ID) data, and part quantity data. The method also includes generating a lifecycle status for each of the one or more parts of the product. The method further includes generating a dynamic EBOM based on the product data and lifecycle status using a Bill of Materials (BOM) generation module. The dynamic EBOM includes a table with at least one row item representing each of the one or more parts in the product. Each row item in the at least one row item includes a lifecycle status and at least one of part name data, part ID data, and part quantity data.

Description

Technical Field

[0001] This disclosure relates to revision management of aerospace components using a product lifecycle management (PLM) system. Background Technology

[0002] Product Lifecycle Management (PLM) systems have been developed as resources to provide a global environment for developing, describing, managing, and communicating digital product knowledge and related information. Some PLM systems enable companies to virtually design and present products, thus eliminating the need for prototyping. Such systems can save money, parts, and other resources, and improve product and workplace safety and ergonomics.

[0003] PLM systems can generate and manage an Engineering Bill of Materials (EBOM) for a product, which is a list of all parts in the product. Traditionally, revising a product in a PLM system results in the existing EBOM being saved as history, and a completely new EBOM reflecting the product revision being generated. This leads to large-scale data duplication and prevents historical data from being viewed on the new EBOM.

[0004] Therefore, improved methods for the generation and revision management of EBOMs in PLM systems are desirable and will be welcomed in the field. Attached Figure Description

[0005] The complete and feasible disclosure of this disclosure, including its best mode, is set forth in the specification with reference to the accompanying drawings, for those skilled in the art, wherein:

[0006] Figure 1 This is a block diagram of a computing system according to an embodiment of the present disclosure;

[0007] Figure 2 This is a schematic diagram of a PLM system according to an embodiment of the present disclosure;

[0008] Figure 3 A schematic diagram of a PLM system according to an embodiment of the present disclosure is shown;

[0009] Figure 4 It may be included in various aspects of this disclosure. Figure 2 The block diagram of the EBOM system in the PLM system is shown below.

[0010] Figure 5A , Figure 5B , Figure 5C The following are illustrated dynamic (live) EBOMs at different stages (e.g., in their original form, after the first modification, and after the second modification) according to embodiments of this disclosure;

[0011] Figure 6A and Figure 6B The dynamic EBOM before and after organization based on one or more lifecycle states is shown according to various aspects of this disclosure;

[0012] Figure 7A and Figure 7B The dynamic EBOM before and after organization based on one or more lifecycle states is shown according to various aspects of this disclosure;

[0013] Figure 8A and Figure 8B The dynamic EBOM before and after organization based on one or more lifecycle states is shown according to various aspects of this disclosure;

[0014] Figure 9A and Figure 9B The present disclosure illustrates dynamic EBOMs before and after organization based on one or more lifecycle states, according to various aspects of this disclosure; and

[0015] Figure 10 This is a flowchart of a method for generating an EBOM in a PLM system according to embodiments of the present disclosure. Detailed Implementation

[0016] Reference will now be made in detail to the present embodiments of this disclosure, one or more examples of which are illustrated in the accompanying drawings. The detailed description uses numerals and letter reference numerals to denote features in the drawings. Similar or analogous reference numerals in the drawings and description have been used to denote similar or analogous portions of this disclosure.

[0017] The term "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any implementation described herein as "exemplary" is not necessarily to be construed as superior or better than other implementations. Furthermore, unless explicitly stated otherwise, all embodiments described herein should be considered exemplary.

[0018] Unless the context clearly indicates otherwise, the singular forms “a,” “a,” and “the” include plural references.

[0019] In a context such as “at least one of A, B and C”, the term “at least one” means only A, only B, only C, or any combination of A, B and C.

[0020] Traditionally, PLM systems use a "revision-based" approach when engineering changes affect the EBOM (Extended Embedded Items). Each change creates a completely new EBOM, and the old EBOM is saved as history. The new EBOM typically differs from the old one only in the row items affected by the change that led to the revision. This is not an efficient approach because it results in massive data duplication. For example, traditionally, both the old and new EBOMs are stored in the PLM system, and each EBOM includes all entries, the only difference being the row items affected by the change.

[0021] This disclosure generally relates to the generation and revision management of dynamic EBOMs using a PLM system. A dynamic EBOM can be a single, continuous bill of materials that includes all historical and current data for a product within the PLM system. For example, when one or more parts in a product are revised (or changed) using the PLM system, the dynamic EBOM can be updated to include the changes while retaining historical data. This advantageously prevents the creation of a new EBOM for each revision, significantly reducing data production and thus lowering data storage costs. Furthermore, a dynamic EBOM allows all changes to a product to be viewed on a single EBOM.

[0022] Referring now to the accompanying drawings, where the same number indicates the same element throughout the drawings, Figure 1 A block diagram of a computing system 100 including one or more processors 24 and memory 26 is shown. Memory 26 may store embodiments of a product lifecycle management (PLM) system 10 according to this disclosure, including specific software modules within the PLM system and user interface features for accessing the PLM system.

[0023] Specifically, Figure 1 An embodiment of a PLM system 10 suitable for providing various processes, including PLM processes 12, 14, 16, 18, 20, and 22, is illustrated. In the depicted embodiment, the PLM system 10 may include support for the execution of a conceptualization process 12. For example, the conceptualization process 12 may produce a set of specifications, such as requirement specifications that document a set of requirements to be met by a design, part, product, or combination thereof. The conceptualization process 12 may also produce a concept or prototype of a part or product (e.g., a machine). A series of design processes 14 may then use the specifications and / or prototypes to produce one or more three-dimensional (3D) design models of, for example, parts or products, which may include utilizing a computer-aided design (CAD) system. The 3D design models may include solid / surface modeling, parametric models, wireframe models, vector models, non-uniform rational basis spline (NURBS) models, geometric models, 2D manufacturing part and assembly drawings, etc.

[0024] The design model can then be further refined and content added by executing development / engineering process 16. For example, the development / engineering process can create and apply models such as thermodynamic models, low-cycle fatigue (LCF) models, life prediction models, multibody dynamics (MBD) and kinematic models, computational fluid dynamics (CFD) models, finite element analysis (FEA) models, and / or 3D-to-2D FEA mapping models, which can be used to predict the behavior of parts or products during their operation. For example, turbine blades can be modeled to predict fluid flow, pressure, clearances, etc., during the operation of a gas turbine engine. Development / engineering process 16 can also result in tolerances, material specifications (e.g., material type, material hardness), clearance specifications, etc. For example, one or more of the models described above can be used to model aerospace components (such as turbine or compressor blades) during the development / engineering process. FEA models can be used to analyze the thermal stress, mechanical loads, and / or vibrations experienced by aerospace components during operation. CFD models can be used to simulate the fluid flow, heat transfer, and / or aerodynamics associated with aerospace components. LCF models can be used to predict the fatigue life of aerospace components that may be subjected to cyclic loads during the operation of aerospace engines.

[0025] PLM system 10 may additionally provide manufacturing process 18, which may include support for manufacturing automation. For example, additive manufacturing models, such as 3D printing models for material jetting, binder jetting, vatphotopolymerization, powder bed fusion, sheet lamination, directional energy deposition, material extrusion, etc., can be exported to create parts or products. Other manufacturing models, such as computer numerical control (CNC) models with G-code, can be exported for machining or otherwise removing material to produce parts or products (e.g., via milling, turning, plasma cutting, wire cutting, etc.). Purchase requisitions, purchase orders, etc., may also be provided as part of manufacturing process 18 (or other PLM processes).

[0026] The PLM system 10 may additionally provide a verification and / or validation process 20, which may include automated inspection of parts or products and automated comparison of specifications, requirements, etc.

[0027] A set of service and tracking processes 22 can also be provided via PLM system 10. Service and tracking processes 22 can record maintenance activities, part replacements, part lifespan (e.g., in operating hours), etc. As shown, PLM system 10 can include feedback between processes 12, 14, 16, 18, 20, and 22. For example, data from service and tracking processes 22 can be used to redesign parts or products via design process 14. In fact, data from any of processes 12, 14, 16, 18, 20, and 22 can be used by any other process in those processes to improve parts or products or to create new parts or products. In this way, PLM system 10 can combine data from downstream processes and use that data to improve parts or create new parts.

[0028] As a non-limiting example, aerospace products can be generated and / or managed by PLM system 10. During the conception process 12, PLM system 10 can provide or generate one or more requirements or objectives (such as weight, thrust, durability objectives) for the aerospace product. For example, requirements or objectives may include structural strength (e.g., parts must withstand certain loads), aerodynamics (e.g., drag coefficient must not exceed a certain threshold), weight, materials, or other requirements. Additionally, during the conception process 12, materials that meet one or more requirements or objectives can be identified, and initial computational simulations can be performed. During the design process 14 and engineering process 16, the computer-aided design (CAD) tools of PLM system 10 can be used to model and test the aerospace product. For example, CAD models of the aerospace product can be generated using PLM system 10, and simulations (such as FEA simulations, CFD simulations, or other simulations) can be performed using the CAD models to confirm that the aerospace product meets design requirements. For example, if the aerospace product is a turbine blade, an FEA or CFD simulation can determine whether the turbine blade can operate as expected and withstand operational stresses. Additionally, during the engineering process 16, the PLM system 10 can generate an EBOM for the aerospace product, which may include a structured list or table of all components and materials associated with the aerospace product. The PLM system 10 can generate the EBOM by extracting data (such as part names, part numbers, part materials, the structure of the aerospace product, material data, or other data) from the CAD model associated with the aerospace product. For example, in an embodiment where the aerospace product is a turbine blade assembly, the EBOM may include a structured list or table for each component, including materials, part names, part numbers, etc. Specifically, in such an embodiment, the list or table may include: airfoil (ceramic material, part number 001, etc.), root (titanium material, part number 002, etc.), shield (steel, part number 003, etc.).

[0029] During manufacturing process 18, additive manufacturing models, CNC models, or other models associated with the production of parts / assemblies of the aerospace product are generated based on the CAD model of the aerospace product. Additionally, PLM system 10 can be used to generate work instructions (e.g., for machinists and / or assemblers) associated with the aerospace product. Work instructions may include a list of steps outlining or describing how to assemble the aerospace product. The EBOM and work instructions can be used to generate a Manufacturing Bill of Materials (MBOM). The MBOM may include work instructions describing how the aerospace product will be assembled, machined, and constructed. Work instructions may include the assembly or machining sequence (e.g., machining part A, additive manufacturing part B, connecting part A to part B to form assembly C, etc.). For example, in an embodiment where the aerospace product is a turbine blade assembly, the MBOM may include: machining the airfoil, additive manufacturing the root, welding the root to the airfoil, etc.

[0030] It should be understood that when changes are made to aerospace products during the design or engineering processes 14, 16, this affects the EBOM, and then the MBOM. For example, if changes are made to the geometry, materials, or design of a CAD model (e.g., an airfoil of a turbine blade assembly) associated with an aerospace product in PLM system 10, this may affect how the aerospace product (e.g., a turbine blade assembly) is represented on the EBOM (e.g., in the form of material updates, structural updates, part name updates, part number updates, or others). Subsequently, the work instructions on the MBOM may be updated based on the changes on the EBOM. For example, additive manufacturing or machining instructions may be updated on the MBOM based on design / material changes to the CAD model, or assembly instructions may be developed based on structural updates to the CAD model.

[0031] Additionally, during manufacturing process 18, PLM system 10 can utilize MBOM to generate a Bill of Process (BOP), which defines the manufacturing workflow required to transform raw materials into the final product. The BOP can link the MBOM to the tools, machines, or other physical workstations needed to manufacture the aerospace product. For example, in an embodiment where the aerospace product is a turbine blade assembly, the BOP could include, for instance, fabricating the airfoil from titanium using CNC machining, generating the root from ceramic powder using an additive manufacturing system, and welding the airfoil to the root at a welding station, etc.

[0032] The computing system 100 may include one or more processors 24 capable of executing software programs to perform the disclosed techniques, and a memory 26 (which may store the PLM system 10). Furthermore, the processor 24 may include multiple microprocessors, one or more "general-purpose" microprocessors, one or more application-specific microprocessors, and / or one or more application-specific integrated circuits (ASICs), or some combination thereof. For example, the processor 24 may include one or more Reduced Instruction Set Computing (RISC) processors. The PLM system 10 is a software-based system having a set of computer-readable and executable instructions stored on a tangible computer-readable medium, such as that represented by the memory 26. The memory 26 may include software instructions configured to implement the program features and steps of the PLM system 10 and / or product data and other information accessed by the software instructions. The memory 26 may be provided as a single or multiple portions of one or more tangible, non-transitory, computer-readable media, such as, but not limited to, any combination of volatile memory (e.g., random access memory (RAM, such as DRAM, SRAM, etc.) and non-volatile memory (e.g., ROM, flash memory, hard disk drive, magnetic tape, CD-ROM, DVD-ROM, etc.), or any other memory device (including floppy disks, drives, other magnetic-based storage media, optical storage media, solid-state storage media, etc.).

[0033] The memory 26 may include one or more non-transitory computer-readable media that jointly store instructions that, when executed by one or more processors 24, cause the computing system 100 to operate, such as the operation described below with reference to FIG9.

[0034] PLM system 10 can be stored in various computer-accessible media locations, such as on one or more dedicated servers or a combination of networked computers or networked storage devices. In some embodiments, the storage location of PLM system 10 is accessible from other computing systems via network 310. In some embodiments, other computing systems (not shown) connected to network 310 store a copy of PLM system 10 locally, but selected data accessed by such applications is stored in a central or distributed network-accessible location.

[0035] When remote access to the software features of PLM system 10 is obtained, such remote connection can be established directly or indirectly via one or more wired or wireless connections to the storage / media device 26 hosting PLM system 10. The remote computer can be connected via network 310, which can correspond to any type of network, including but not limited to dial-in networks, utility networks, public switched telephone networks (PSTN), local area networks (LANs), wide area networks (WANs), metropolitan area networks (MANs), personal area networks (PANs), virtual private networks (VPNs), campus area networks (CANs), storage area networks (SANs), the Internet, intranets, or Ethernet networks, combinations of two or more of these types of networks, or other networks, implemented using any kind of network topology with a combination of one or more wired and / or wireless communication links.

[0036] The computing device accessing the PLM system 10 or its selected features may include one or more communication interfaces, one or more memory / media devices, and one or more processing devices, such as microprocessors. Therefore, by executing software instructions presented as part of the PLM system 10, such a computing / processing device can be adapted to operate as a dedicated machine. The software instructions stored in the memory / media device 26 can also define multiple different interfaces for accessing the PLM system 10, thereby connecting the PLM system 10 to interfaces of different corporate entities associated with product management. For example, Figure 1 Exemplary software interfaces in the form of a New Product Introduction (NPI) interface 312, an Application Application interface 314, an Authorization Implementation interface 316, and an Operational Feedback interface 318 are shown. In this way, different types of access to the PLM system 10 can be customized for different corporate entities based on different needs throughout the product lifecycle (e.g., product creation, application, implementation, and operation).

[0037] System users can return Figure 1 One or more user I / O control devices 320 shown access the PLM system 10 and / or its selected software functions. Exemplary input devices may include, but are not limited to, a keyboard, a touchscreen monitor, an eye tracker, a microphone, a mouse, etc. Exemplary output devices may include, but are not limited to, a monitor, a printer, or other devices for visually depicting output data created according to the disclosed techniques. Other I / O devices correspond to intermediate computer components, such as memory or a processor, that access the PLM system 10. As used herein, the term “user” refers to a human operator, another computer, or a combination of human and machine operators. Therefore, it should be understood that the term “user” is not limited to a human operator.

[0038] The specific types of products that can be managed according to the disclosed technology can correspond to various different types of products, components, processes, or even computer software. In some specific examples, the disclosed technology can be used with a PLM system to manage aircraft or aerospace components, such as, but not limited to, gas turbine engines, fans, blades (rotors or stationary), fuselage components, or other parts.

[0039] Now for reference Figure 2 A block diagram of PLM system 10, which includes a number of PLM-based systems or modules (e.g., software systems). More specifically, embodiments of PLM system 10 illustrate a computer-aided requirements capture (CAR) system 30, a computer-aided design (CAD) system 32, a computer-aided engineering (CAE) system 34, a computer-aided manufacturing / computer-integrated manufacturing (CAM / CIM) system 36, a coordinate measuring machine (CMM) system 38, a product data management (PDM) system 40, and an engineering bill of materials (EBOM) system 42. Each of systems 30, 32, 34, 36, 38, 40, and 42 can be stored in a memory system (such as memory 26). Figure 1 In, and can be via processor (such as via processor 24 ( Figure 1 ))implement.

[0040] In the depicted embodiments, CAR system 30 can provide entries of requirements and / or specifications, such as the dimensions of a part or product, the operating conditions the part or product is expected to encounter (e.g., temperature, pressure), certifications to be complied with, quality control requirements, performance requirements, etc. For example, in an embodiment where the product managed by the PLM system is an aerospace product (such as a turbine blade assembly), requirements and / or specifications may include structural strength (e.g., the turbine blade assembly must withstand loads up to a certain threshold), aerodynamic requirements (e.g., the airfoil of the turbine blade assembly must have a drag coefficient within a certain range), weight limitations, or other requirements. CAD system 32 can provide a graphical user interface suitable for creating and manipulating graphical representations of 2D and / or 3D models as described above with respect to design process 14. For example, 3D design models may include solid / surface modeling, parametric models, wireframe models, vector models, non-uniform rational basis spline (NURBS) models, geometric models, etc. CAD system 32 can provide the creation and updating of 2D and / or 3D models and related information (e.g., views, drawings, annotations, notes, PMI objects, etc.). In fact, CAD system 32 can combine graphic representations of parts or products with other relevant information.

[0041] CAE system 34 can create various engineering models (such as those described above regarding development / engineering process 16). For example, CAE system 34 can apply engineering principles to create models such as thermodynamic models, low-cycle fatigue (LCF) life prediction models, multibody dynamics (MBD) and kinematic models, computational fluid dynamics (CFD) models, finite element analysis (FEA) models, and / or 3D-to-2D FEA mapping models. CAE system 34 can then apply these models to analyze certain part or product characteristics (e.g., physical properties, thermodynamic properties, fluid flow characteristics, etc.), for example, to better match the requirements and specifications of the part or product. CAE system 34 can extract information (e.g., material information, structural information, etc.) from EBOM or CAD models for simulation, such as FEA simulation, CFD simulation, thermal simulation, etc. CAE system 34 can detect whether the CAD model meets the requirements and can notify the CAD model whether adjustments are needed, which then affects EBOM, MBOM, and BOP. For example, in an implementation where the product managed by the PLM system is an aerospace product (such as a turbine blade assembly), the CAE system 34 can utilize the CAD model of the turbine blade assembly to apply FEA simulations, CFD simulations, or other virtual tests to verify whether the turbine blade assembly meets design requirements (e.g., the CAE system 34 can use FEA simulations to determine whether the airfoil of the turbine blade assembly can withstand certain loads). If not, the CAD model of the turbine blade assembly can be updated (e.g., the material of the airfoil can be changed or modified).

[0042] The CAM / CIM system 36 can provide certain automation and manufacturing efficiencies, for example, by exporting certain programs or code (e.g., G-code) and then executing those programs or code to manufacture parts or products. The CAM / CIM system 36 can support certain automated manufacturing techniques, such as additive (or subtractive) manufacturing techniques, including material jetting, binder jetting, photopolymerization, powder bed melting, sheet lamination, directional energy deposition, material extrusion, milling, turning, plasma cutting, wire cutting, or combinations thereof. For example, for aerospace products (such as turbine blade assemblies), the CAM / CIM system 36 can, at least in part, derive the toolpaths required for machining the complex shapes of airfoils using subtractive manufacturing techniques (such as milling, turning, grinding, etc.), based on a CAD model of the aerospace product. Additionally or alternatively, the CAM / CIM system 36 can, at least in part, generate layer-by-layer deposition paths followed by additive manufacturing systems to fabricate aerospace products, based on a CAD model of the aerospace product. The CMM system 38 may include machinery for automated inspection. For example, probe-based, camera-based, and / or sensor-based machinery can automatically inspect parts or products to ensure they conform to certain geometries, tolerances, shapes, etc.

[0043] PDM system 40 can manage and publish data from systems 30, 32, 34, 36, 38, and / or 42. For example, systems 30, 32, 34, 36, 38, and / or 42 can communicate with data repositories 56, 58, and 60 via data sharing layer 62. PDM system 40 can then manage collaboration between systems 30, 32, 34, 36, 38, and / or 42 by providing data translation services, version control support, file management, update notifications, etc. PDM system 40 can also provide business support, such as interfacing with supplier / retailer systems and / or logistics systems for procurement, invoicing, order tracking, etc. PDM system 40 can also interface with service / record systems (e.g., service center data management systems) to help track the maintenance and lifecycle of parts or products as they undergo operation. Teams 64 and 66 can collaborate with team members via collaboration layer 68. The collaboration layer may include web interfaces suitable for sharing information and various data, messaging systems, drag-and-drop / pick-up systems, etc. In an implementation where the products managed by PLM system 10 are aerospace products (such as turbine blade assemblies), collaboration layer 68 can allow engineering teams to collaborate with manufacturing teams to verify data on various bills of materials (BOMs). For example, once an EBOM is generated for an aerospace product, the manufacturing team can collaborate with the engineering team to generate or verify details on the MBOM. Additionally, collaboration layer 68 can allow individual teams to collaborate on collaborative tasks. For example, engineering teams can collaborate with each other to ensure that machining tolerances are met for airfoils of turbine blade assemblies. Collaboration layer 68 can also include, or communicate with, a cloud-based system 70, which can provide decentralized computing services and file storage. For example, some (or all) of systems 30, 32, 34, 36, 38, and 42 can be stored in and / or accessible via cloud 70.

[0044] EBOM system 42 can generate, manage, and maintain EBOMs associated with components and / or parts generated within PLM system 10. It should be understood that an EBOM is a comprehensive list or table detailing all parts (or components), components, and sub-components required to produce a product. An EBOM may include specification data, part identification (ID) data, part description data, part quantity data, unit of measurement data, and hierarchical data. Other systems within PLM system 10 (such as CAR system 30, CAD system 32, CAE system 34, CAM / CIM system 36, and / or CMM system 38) can provide EBOM system 42 with data about components, sub-components, parts, and / or parts produced or managed within PLM system 10 for generating and / or managing the EBOM for those components, sub-components, parts, and / or parts.

[0045] By, for example, via systems 30, 32, 34, 36, 38, 40, and 42, enabling processes 12, 14, 16, 18, 20, and 22 ( Figure 1 The techniques described herein can provide more effective cradle-to-grave product lifecycle management. For example, processes 12, 14, 16, 18, 20, and 22, as described in more detail below... Figure 1 Systems 30, 32, 34, 36, 38, 40, and 42 can use PLM system 10 to facilitate the generation and revision management of dynamic EBOMs. A dynamic EBOM can be a single, continuous bill of materials (BOM) that includes all historical and current data for a product from the PLM system. For example, when one or more parts in a product are revised (or changed) using the PLM system, the dynamic EBOM can be updated to include the changes while retaining historical data. This advantageously prevents the creation of a new EBOM each time a revision is made, significantly reducing data production and thus lowering data storage costs. Additionally, a dynamic EBOM allows all changes to a product to be viewed on a single EBOM. The dynamic EBOM can then be used to generate MBOMs and / or BOPs.

[0046] Now for reference Figure 3 A schematic diagram of a PLM system 10 according to an embodiment of the present disclosure is shown. Specifically, Figure 3 The logical relationships between various processes are illustrated by showing how the processes in PLM system 10 overlap with each other (e.g., in a Venn diagram). As shown, PLM system 10 is suitable for providing various processes, including those referenced above. Figure 1 The PLM system 10 details the conceptualization process 12, design process 14, engineering process 16, manufacturing process 18, and verification / validation process 20. Additionally, the PLM system 10 may be equipped with a CAD system 32, which can be used to implement PLM processes 12, 14, 16, 18, and 20. The CAD system 32 can provide a graphical user interface suitable for creating and manipulating graphical representations of 2D and / or 3D models as described above with respect to conceptualization process 12 and design process 14. For example, the CAD system 32 can provide detailed part modeling by utilizing 3D design models, which may include solid / surface modeling, parametric models, wireframe models, vector models, non-uniform rational basis spline (NURBS) models, geometric models, etc. The CAD system 32 can provide the creation and updating of 2D and / or 3D models and related information (e.g., views, drawings, annotations, notes, PMI objects, etc.). In fact, the CAD system 32 can combine graphical representations of parts or products with other relevant information.

[0047] Additionally, CAD system 32 can be used to generate assembly models (such as EBOMs) during design and / or engineering processes 14, 16. Furthermore, CAD system 32 can be used to generate tooling designs and / or engineering drawings during engineering and / or manufacturing processes 16, 18. Moreover, CAD system 32 can be used to analyze the product during engineering and / or validation processes 16, 20.

[0048] Now for reference Figure 4 The embodiments of the present disclosure can be seen above with reference to the above. Figure 1 and Figure 2 The diagram describes a block diagram of an EBOM system 42 implemented in a PLM system 10. As shown, the EBOM system 42 may include an EBOM generation module 104. The EBOM generation module 104 can generate, manage, and maintain a dynamic EBOM 106. The dynamic EBOM 106 may be a table 108 or list that includes components 110, sub-components 112, and parts 114 in a product (such as a product generated using the PLM system 10). For example, in an implementation where the product managed by the PLM system 10 is an aerospace product (such as a turbine blade assembly), the dynamic EBOM 106 may include part names associated with aerospace components (e.g., airfoil, root, shield, etc.), part numbers associated with each component (e.g., 1, 2, 3, etc.), part quantities, part materials (e.g., ceramic, titanium, steel, etc.), and other data.

[0049] The EBOM generation module 104 can, for example, receive or obtain product data 116 from the PLM system 10, which can be used to generate a dynamic EBOM 106. For example, the EBOM generation module 104 can refer to the above-mentioned reference... Figure 2 The PLM system 10 receives product data 116 from one of systems 30, 32, 34, 36, and / or 38. Specifically, in an exemplary embodiment, product data 116 may be derived from the above-referenced... Figure 2 The CAD system 32, CAE system 34 and / or CAM / CIM system 36 described are provided.

[0050] Product data 116 may include part name data 118, part identification (ID) data 120, part quantity data 122, part material data 124, and / or hierarchical structure data 126. Part name data 118 may include the name or description of each component, sub-component, and / or part in the product. Part name data 118 may also include a description or descriptor of the material forming the component, sub-component, and / or part. Examples of part name data 118 may include “bent handle,” “wheel,” “aluminum pedal,” etc. Part ID data 120 may be a unique string of characters and / or numbers for each component, sub-component, and part in the product, facilitating component tracking and management. Part quantity data 122 may include the quantity of each component, sub-component, and / or part required to assemble or produce the product. Part material data 124 may describe the material used for parts in the product (e.g., steel, aluminum, plastic, etc.). Hierarchical structure data 126 may indicate the structured relationships between components of the product, describing which parts are included in a component or sub-component and / or which sub-component is included in a component. For example, in… Figure 4 In the dynamic EBOM 106 shown, part 114 is included in subassembly 112, and the subassembly is included in assembly 110, as shown in the structured relationships between parts (e.g., top-to-bottom and indented arrangement). For example, if the product is an aerospace product (such as a turbine segment), assembly 110 may be a rotor assembly that may include one or more turbine blade subassemblies, which may include airfoils, roots, shrouds, etc. That is, indented arrangement can indicate that the turbine segment includes a rotor assembly with turbine blade subassemblies, which include several parts (such as airfoils, roots, shrouds, etc.).

[0051] In an exemplary embodiment, the EBOM generation module 104 may include a revision management module 128. The revision management module 128 can monitor products within the PLM system 10, and when a product is modified, the revision management module 128 can update the dynamic EBOM 106. For example, if changes are made to the geometry, material, or design of a CAD model (e.g., an airfoil of a turbine blade assembly) associated with a product in the PLM system 10, this may affect how the aerospace product (e.g., a turbine blade assembly) is represented on the EBOM (e.g., in the form of material updates, structural updates, part name updates, part number updates, or others). The revision management module 128 can identify that changes have been made to the CAD model and update the dynamic EBOM 106 accordingly. Specifically, if the material of one or more components of an aerospace product (such as an airfoil) is changed in the CAD model (e.g., from titanium to steel), the revision management module 128 can detect or identify the change and update the dynamic EBOM to reflect it.

[0052] In many implementations, the revision management module 128 can generate a lifecycle state 130 for each component, subcomponent, and / or part in the dynamic EBOM 106. Based on product data and lifecycle states, the dynamic EBOM 106 can be generated (or updated) using the EBOM generation module 104. In other words, the dynamic EBOM 106 can include a lifecycle state 130 for each component 110, subcomponent 112, and part 114. The lifecycle state 130 can describe whether the product's component 110, subcomponent 112, and / or part 114 are in their original form, and whether the product's component 100, subcomponent 122, and / or part 114 are in an active or historical state in the current EBOM. For example, lifecycle status 130 could describe whether product component 110, sub-component 112, and / or part 114 are in their original form, whether product component 100, sub-component 122, and / or part 114 have been modified during one or more revisions (e.g., from version 1 to version 2), or whether product component 120, sub-component 122, and / or part 114 are currently being revised. For example, if the product is a turbine rotor blade, lifecycle status 130 could indicate whether the turbine rotor blade (e.g., a CAD model representing the turbine rotor blade) is in its original design form, whether the turbine rotor blade has been modified during one or more revisions (whether the design, materials, quantity, name, or other data associated with the turbine rotor blade have been modified by an engineering team or other users using a CAD system), or whether the turbine rotor blade is currently being revised (e.g., whether the engineering team of PLM system 10 or another user is currently revising the design of the turbine rotor blade using a CAD system). Specifically, in a non-limiting example, if the engineering team or other users modify the material of the turbine rotor blades by updating the CAD model representing the turbine rotor blades, the dynamic EBOM108 can update the lifecycle status 130 to indicate that a change has been made.

[0053] The dynamic EBOM 106 can be a single, continuous bill of materials (BOM) that includes all historical and current data about the product from the PLM system 10. For example, when one or more parts in a product are revised (or changed) using the PLM system 10, the dynamic EBOM 106 can be updated to include the changes while retaining historical data. This advantageously prevents the creation of a new EBOM each time a revision is made, significantly reducing data production and thus lowering data storage costs. Additionally, the dynamic EBOM 106 allows all changes to the product to be viewed on a single EBOM. Furthermore, the dynamic EBOM 106 can advantageously reduce the complexity of generating MBOMs and BOPs. For example, as discussed above, MBOMs and BOPs can include specific instructions for building or manufacturing the product. The dynamic EBOM 106 prevents users or machines from having to process several EBOMs to generate an MBOM or BOP. Moreover, the dynamic EBOM 106 can be provided to the CAM / CIM system 36 ( Figure 2 The CAM / CIM system 36 can derive machine paths based on the dynamic EBOM 106, which can be provided to a manufacturing apparatus for producing various parts of a product. For example, the CAM / CIM system 36 can derive, at least in part, paths for complex shapes of one or more parts of a product machined using subtractive manufacturing techniques such as milling, turning, grinding, etc., based on the CAD model and / or the dynamic EBOM 106, which can be provided to a subtractive manufacturing machine. Additionally or alternatively, the CAM / CIM system 36 can generate layer-by-layer deposition paths based on the CAD model and / or the dynamic EBOM 106, which can be provided to an additive manufacturing system for producing the product.

[0054] Now for reference Figure 5A , Figure 5B and Figure 5C This illustrates a dynamic EBOM 200 according to an embodiment of the present disclosure. Specifically, Figure 5A The dynamic EBOM 200 representing the product in its original version is shown. Figure 5B This illustrates the dynamic EBOM200 following the first change (or revision in a legacy system) to one or more parts of the product, resulting in the first version of the product. Figure 5C This illustrates the dynamic EBOM 200 following a second change (or revision in a legacy system) to one or more parts of the product, resulting in a second version of the product.

[0055] like Figures 5A-5C As shown, the dynamic EBOM 200 includes a table 202 with at least one row item 204 (e.g., row) for each part in the product. For example, the dynamic EBOM 200 can list all parts of the product, and the dynamic EBOM 200 can be referenced above. Figure 1 and Figure 2 The described PLM system 10 generates and manages [the product]. Table 202 may include at least one row item 204 representing each part (or component) of the product, such that each part is listed at least once in Table 202. In the illustrated embodiment, the dynamic EBOM 200 may include at least one row and at least one column. For example, the data in the dynamic EBOM 200 may be arranged such that each row represents a unique entry associated with a part of the product, and each column categorizes specific data attributes or data types associated with that part of the product according to the engineering bill of materials. For example, as shown, each row (or row item) corresponds to a different part of the product, and each column represents a different data type associated with that part, such as part ID data, part name data, and / or lifecycle status 208. Although not shown, the dynamic EBOM 200 may include [other data types, such as those referenced above] Figure 4 Additional columns for the part quantity data, part material data, and / or hierarchical structure data. It should be understood that in other embodiments (not shown), the arrangement of the dynamic EBOM 200 can be flipped so that columns represent parts of the product and rows represent data attributes or data types.

[0056] As shown in the figure, the lifecycle state 208 of each part identifies whether the line item of that part is historical, current, or in progress (e.g., with a label such as "Historical," "Current," or "In Progress"). Additionally, the lifecycle state 208 of each part identifies at least one of the following: part version (e.g., original version, first version, second version) and version transition. Version transition can indicate or describe from which version the part was modified and to which version the part was modified. For example, if a part is modified from the original version to the first version via Chg1, the lifecycle state 208 can identify this as "Orig-Chg1," indicating that the line item becomes historical based on Chg1, or using another similar identifier. In other words, the lifecycle state 208 can describe at least one of the following: whether the line item (e.g., line) of the part is historical, current, or in progress; the part version (e.g., the original version); and whether the part has been modified between versions during revisions.

[0057] For example, such as Figure 5AAs shown, this is the dynamic EBOM 200 before any modifications are made to the parts in the product. The lifecycle status 208 of each part indicates that the part is: (1) current (i.e., the latest version of the part); and (2) original (i.e., this is the first or initial version of the part). In this way, the lifecycle status 208 can indicate or describe whether (1) the row (e.g., the part described by the row) includes current or historical data; and (2) whether the row is original or has been modified. For example, in the illustrated embodiment, the dynamic EBOM 200 in Figure 5(A) has a lifecycle status 208 of "current (Orig)" for each part.

[0058] Figure 5B The diagram illustrates a dynamic EBOM 200 following the first change (or revision in a conventional system) to one or more parts of a product. For example, PLM system 10 may modify one or more parts of the product during a new revision period (e.g., a new revision time period). That is, one or more parts of the product may be modified during the new revision period via the reference above. Figure 2 Modify at least one of the described CAR system 30, CAD system 32, CAE system 34, CAM / CIM system 36 and / or CMM system 38.

[0059] PLM system 10 can modify part quantity, part name, part material, part specifications (e.g., size and / or shape), part hierarchy, or other part attributes to create modified part data 210. In response, the system can, for example, use the above reference... Figure 4 The described EBOM generation module 104 and / or revision management module 128 generate the current lifecycle status 209 and historical lifecycle status 207 of modified (or being modified) parts in one or more parts.

[0060] Subsequently or simultaneously, the dynamic EBOM 200 can be updated to reflect the change while retaining all historical data. That is, for each modified part, the EBOM generation module 42 can generate or add a new line item 205 (or row) for the modified part. The new line item 205 includes the modified data 210, the current lifecycle status 209, and any data that has not changed (e.g., part ID). In other words, after (or during) a product modification using the PLM system 10, the dynamic EBOM 200 can be updated by adding a new line item 205 corresponding to the modified (or being modified) part in table 202 to create historical line items 203 and current line items 205. The current line item 205 includes the current lifecycle status 209, the modified data 210, and at least one of the part name data, part ID data, part quantity data, and material data for one or more parts in the product. The historical line item 207 includes the historical lifecycle status 207, and at least one of the part name data, part ID data, part quantity data, and part material data for one or more parts in the product. Historical line item 203 does not include modified data. This allows every part throughout the entire product engineering lifecycle (e.g., from the original version to the final version, including all intermediate versions) to be viewed on a single, continuous, dynamic EBOM 200.

[0061] For example, when one or more changes, updates, or revisions are made to parts of a product using, for example, PLM system 10, EBOM system 42 can identify which data has been changed for each part in the product. For example, the system can identify whether part name data 118, part quantity data 122, part material data 124, and / or part hierarchy data 126 have been changed for each part in the product to generate modified data 210. Subsequently, for each part that has been modified during the revision, new line items (or rows) can be added to table 202 while retaining historical part data. The new line items 205 can include the modified data 210 and any data that has not been changed.

[0062] As a non-restrictive example, such as comparison Figure 5A and Figure 5B As shown, in generating Figure 5A Following the dynamic EBOM 200 shown, the part name of the first part in the list can be changed from "Steel Frame" to "Aluminum Frame". Subsequently, as... Figure 5BAs shown, the dynamic EBOM 200 can be updated in response to a modification of the part to reflect the change. That is, the dynamic EBOM 200 can be modified by adding a row item 204 (e.g., a row) corresponding to the modified (or being modified) part in the table to create a historical row item 203 and a current row item 205. The current row item 205 includes a new lifecycle state (e.g., “Current (chg1)”) and at least one of the part name data, part ID data, part material data, and part quantity data for one or more parts in the product. For example, the current row item 205 includes modified data 210 (e.g., a new part name (aluminum frame)) and any unchanged data related to the part, such as part ID data, part quantity data, etc. The new lifecycle state can describe that: (1) the current row 205 includes current data; and (2) the current row 205 is generated due to a change made during the first revision period (during the first change of the product). For example, as shown, the new lifecycle state in the current row 205 could be “Current (chg1)”.

[0063] Additionally, the lifecycle status 208 of historical line item 203 can be updated (e.g., updated to historical lifecycle status 207) to reflect that the line item now contains historical data. Historical lifecycle status 207 can describe: (1) historical line 203 contains historical data; (2) from which version of the product the change or revision was made; and (3) which version of the product the change or revision resulted in. For example, as shown in the figure, historical lifecycle status 207 in historical line item 203 is "Historical (Orig-Chg1)", indicating that the line contains historical data and that the change was made from the original version to the first version during the first revision period (e.g., during the first change to the product).

[0064] Figure 5C The diagram illustrates a dynamic EBOM 200 following a second change or revision to one or more parts of a product. For example, PLM system 10 may modify one or more parts of the product during a second new revision period (e.g., a new revision time period). That is, one or more parts of the product may be modified during the second new revision period via the reference above. Figure 2 Modify at least one of the described CAR system 30, CAD system 32, CAE system 34, CAM / CIM system 36 and / or CMM system 38.

[0065] For example, through comparison Figure 5B and Figure 5C As shown, in generating Figure 5BFollowing the dynamic EBOM 200 shown, the part name of part 001 in the list can be changed a second time from "Aluminum Frame" to "Alloy Frame". Additionally, part 002 in the list can be changed from "Straight Handle" to "Bent Handle". Subsequently, as... Figure 5C As shown, the dynamic EBOM 200 can be updated to reflect a part change in response to a modification of the part's specifications (size and / or shape). That is, the dynamic EBOM 200 can be modified by adding two additional row items 204 (e.g., rows) to the table corresponding to the modified (or being modified) part to create a historical row item 203 and a current row item 205. The current row item 205 includes a new lifecycle state (e.g., "Current (chg2)"), and at least one of the part's part name data, part ID data, part quantity data, and material data for one or more parts in the product. For example, the current row item 205 includes modified data 210 (e.g., part name (alloy frame) and / or new specification data (e.g., bent handle)), and any unchanged data related to the part, such as part ID data, part quantity data, etc. The new lifecycle state can be described as: (1) the current row item 205 includes current data; and (2) the current row item 205 was generated due to a change made during a second revision period. For example, as shown in the figure, the new lifecycle state in the current row 205 could be "current (chg2)".

[0066] The dynamic EBOM 200 described above can be a single, continuous bill of materials that includes all historical and current data for the product from the PLM system. For example, when one or more parts in a product are revised (or changed) using the PLM system 10, the dynamic EBOM 200 can be updated to include the changes while retaining historical data. This advantageously prevents the creation of a new EBOM each time a revision is made, significantly reducing data production and thus lowering data storage and maintenance costs. Furthermore, the dynamic EBOM allows all changes to the product to be viewed on a single EBOM.

[0067] Additionally, the dynamic EBOM 200 can be used to generate the MBOM and / or BOP. For example, as discussed above, the MBOM and BOP can include specific instructions for building or manufacturing the product. The dynamic EBOM 200 prevents users or machines from having to process several EBOMs to generate the MBOM or BOP. In this way, the MBOM and / or BOP can be generated based on a single dynamic EBOM 200 instead of several versions of the EBOM. Furthermore, the dynamic EBOM 106 can be provided to the CAM / CIM system 36 ( Figure 2The CAM / CIM system 36 can derive machine paths based on the dynamic EBOM 106, which can be provided to a manufacturing apparatus for producing various parts of a product. For example, the CAM / CIM system 36 can derive, at least in part, paths based on the CAD model and / or the dynamic EBOM 106, for machining one or more parts of a product using subtractive manufacturing techniques such as milling, turning, grinding, etc., which can be provided to a subtractive manufacturing machine. Additionally or alternatively, the CAM / CIM system 36 can generate layer-by-layer deposition paths based on the CAD model and / or the dynamic EBOM 106, which can be provided to an additive manufacturing system for producing the product.

[0068] Now for reference Figure 6A , Figure 7A , Figure 8A and Figure 9A The diagram illustrates a dynamic EBOM 200 according to an embodiment of the present disclosure. The dynamic EBOM 200 includes a table 202 having at least one row item 204 (e.g., a row) representing each of one or more parts in a product. For example, the dynamic EBOM 200 can list all parts of a product; the dynamic EBOM 200 can be referenced above. Figure 1 and Figure 2 The described PLM system 10 generates and manages products. Each row (or row item 204) corresponds to a different part of the product, and each column represents a different data type associated with that part, such as part ID data, part name data, and / or lifecycle status 208.

[0069] like Figure 6A , Figure 7A , Figure 8A and Figure 9AAs shown, lifecycle status 208 can be historical lifecycle status 207, current lifecycle status 209, and / or in-process lifecycle status 212. Additionally, the lifecycle status 208 for each part identifies at least one of the following: part version (e.g., original version, first version, second version) and version transition. Version transition can indicate or describe from which version the part was modified and to which version the part was modified. For example, referring to part 001, lifecycle status 208 indicates that the part started as a "steel frame" in the original version. Lifecycle status 208 also indicates that part 001 was changed to an "aluminum frame" during the first revision, thus transitioning from the original version to the first version. Subsequently, part 001 was further changed to an "alloy frame" during the second revision, thus transitioning from the first version to the second version. Finally, in-process lifecycle status 212 indicates that part 001 of the product is being further modified to a "carbon frame" during the third revision, thus becoming the third version. Similarly, the lifecycle status 208 of part 002 indicates that the part started as a “straight handle,” was modified to a “bent handle,” and is currently being further modified to a “hybrid handle.” This allows every part throughout the entire engineering BOM lifecycle of the product (e.g., from the original version to the final version, including all intermediate versions) to be viewed on a single, continuously dynamic EBOM 200.

[0070] Now for reference Figure 6B , Figure 7B , Figure 8B and Figure 9B The dynamic EBOM 200 can be organized based on the lifecycle states of interest. Specifically, lifecycle state 208 describes both: (a) whether a part's line item is current, historical, or in progress; and (b) which version of the product the part's line item belongs to, such as Orig, Chg1, Chg2, Chg3, Chg4, or any other version. Therefore, the dynamic EBOM 200 can be organized based on either (a) or (b). That is, the dynamic EBOM 200 can be organized by history or version.

[0071] For example, such as Figure 6BAs shown, the dynamic EBOM 200 can be organized by the first version of the product. The first version of the product is generated during the first revision period (e.g., a time period). Therefore, the dynamic EBOM 200 can be organized to reflect the product that exists after the first revision period. In this way, the resulting dynamic EBOM 200 can include any parts modified during the first revision period (e.g., part 001) and any parts not modified during the first revision period (e.g., parts 001, 002, and 003). Organizing table 202 based on the lifecycle status 208 of each part can include selecting one or more lifecycle statuses of interest (e.g., any lifecycle status corresponding to the first version of the product), such as any line item 204 generated by the first revision period (e.g., "Orig-Chg1") and any line item 204 not modified during the first revision period (e.g., "Orig"). Subsequently, any line item 204 that does not include the lifecycle status of interest can be removed from table 202, and any line item 204 that includes the lifecycle status of interest can be retained. This results in Figure 6B Table 202 shown here illustrates the products that existed after the first revision period.

[0072] The dynamic EBOM 200 can be used to generate the MBOM and / or BOP. For example, as discussed above, the dynamic EBOM can define the product by design, the MBOM can be adapted from the dynamic EBOM 200 for manufacturing (e.g., by including fabrication / assembly instructions), and the BOP can also be adapted from the MBOM to include specific process steps for building the product. By utilizing the dynamic EBOM 200, the PLM system 10 does not need to process several EBOMs to generate the MBOM or BOP. In this way, the MBOM and / or BOP can be generated based on a single dynamic EBOM 200 instead of several versions of the EBOM. Furthermore, the dynamic EBOM 106 can be provided to the CAM / CIM system 36 (…). Figure 2 The CAM / CIM system 36 can derive machine paths based on the dynamic EBOM 106, which can be provided to a manufacturing apparatus for producing various parts of a product. For example, the CAM / CIM system 36 can derive, at least in part, paths for complex shapes of one or more parts of a product machined using subtractive manufacturing techniques such as milling, turning, grinding, etc., based on the CAD model and / or the dynamic EBOM 106, which can be provided to a subtractive manufacturing machine. Additionally or alternatively, the CAM / CIM system 36 can generate layer-by-layer deposition paths based on the CAD model and / or the dynamic EBOM 106, which can be provided to an additive manufacturing system for producing the product.

[0073] like Figure 7BAs shown, the dynamic EBOM 200 can be organized using the product's third revision (Chg3). The third revision of a product is generated by following the first revision from the original version to the first version, then the second revision from the first version to the second version, and finally the third revision from the second version to the third version. Not every part in the product is updated or modified during each revision period. For example, as... Figure 7A As shown, only part 001 was modified from the original version (“Orig”) to the first version (“Chg1”) during the first revision period, while both parts 001 and 002 were modified to the second version (“Chg2”) during the second revision period.

[0074] Therefore, as Figure 7B As shown, a dynamic EBOM 200 can be organized to reflect products existing after (or during) the third revision period. In this way, the resulting dynamic EBOM 200 can include any parts modified during the third revision period (e.g., part 001), any parts modified before the first revision period (e.g., part 002), and any parts not modified from the original version (e.g., parts 003 and 004). Organizing table 202 based on the lifecycle status 208 for each part can include selecting one or more lifecycle statuses of interest (e.g., any lifecycle status corresponding to the third version of the product). This includes any line items 204 modified during the third revision period, any line items 204 modified before the third revision period, and any line items 204 not modified from the original version. Subsequently, any line items 204 that do not include the lifecycle status of interest can be removed from table 202, and any line items 204 that include the lifecycle status of interest can be retained. This results in… Figure 7B Table 202 shown here illustrates the products that existed during the third revision period.

[0075] In many embodiments, such as Figure 6A , Figure 7A , Figure 8A and Figure 9A As shown, a product can be modified by multiple different users simultaneously, which can be advantageously displayed concurrently via a dynamic EBOM 200. For example, as illustrated, a first user can modify the first part of the product during the third revision period to generate the third version (Chg3) of the product, and a second user can simultaneously modify the second part of the product during the fourth revision period to generate the fourth version (Chg4) of the product. The dynamic EBOM 200 can display two modifications at the same time, which advantageously allows users to identify all modifications to the product by viewing a single dynamic EBOM 200 instead of several EBOMs.

[0076] like Figure 8BAs shown, the dynamic EBOM 200 can be organized using the product's third version (Chg3) and fourth version (Chg4). The dynamic EBOM 200 can be organized to reflect the product existing after (or during) the third and fourth revision periods. In this way, the resulting dynamic EBOM 200 can include any parts modified during the third revision period (e.g., part 001), any parts modified during the fourth revision period (e.g., part 002), and any parts not modified from the original version (e.g., parts 003 and 004). Organizing table 202 based on the lifecycle status 208 for each part can include selecting one or more lifecycle statuses of interest (e.g., any lifecycle status corresponding to the product's third and fourth versions). This includes any line items 204 modified during the third or fourth revision period, any line items 204 modified before the third and fourth revision periods, and any line items 204 not modified from the original version. Subsequently, any line items 204 that do not include the lifecycle status of interest can be removed from table 202, and any line items 204 that include the lifecycle status of interest can be retained. This results in... Figure 8B Table 202, shown below, illustrates the products that existed during the third and fourth revision periods.

[0077] Version-based organization of Dynamic EBOM 200 allows for traceability throughout the product lifecycle. For example, each version can capture certain design updates and / or material changes to the product. In other words, lifecycle status enables Dynamic EBOM 200 to be organized on a version-based basis, allowing users of PLM system 10 to access the EBOM representing the latest design of the product, while retaining the ability to access previous versions for comparison without needing to store each version of the EBOM separately. Dynamic EBOM 200 also prevents outdated EBOMs (e.g., previous versions) from being incorrectly used to generate MBOMs or BOPs.

[0078] like Figure 9AAs shown, the dynamic EBOM 200 can be organized based on whether the lifecycle state is current, historical, or in progress. Specifically, the dynamic EBOM 200 can be organized to reflect the current state of the product (e.g., any revisions that have been completed and are not in progress). In this way, the resulting dynamic EBOM 200 can include line items 204, each including an indication that the entry is in the current lifecycle state. Organizing table 202 based on the lifecycle state 208 for each part can include selecting one or more lifecycle states of interest (e.g., any lifecycle state indicating that line item 204 is current). Subsequently, any line items 204 that do not include the lifecycle states of interest can be removed from table 202, and any line items 204 that include the lifecycle states of interest can be retained. This results in… Figure 9B Table 202, shown below, illustrates the current status of the product.

[0079] Now for reference Figure 10 A flowchart of a method 900 for generating a dynamic EBOM in a PLM system according to an embodiment of this subject is shown. For example, one or more steps of this method may be performed by a computing system 100 as discussed herein. Generally, this document will refer to the above references. Figure 1 Method 900 is described using the computing system 100, PLM system 10, EBOM system 42, and EBOM 200 described in section -9. However, those skilled in the art will understand that the disclosed method 900 can generally be used with any other suitable system construction. Additionally, although... Figure 10 For illustrative and discussion purposes, steps are depicted in a specific order, but unless otherwise specified in the claims, the methods discussed herein are not limited to any particular order or arrangement. Using the disclosure provided herein, those skilled in the art will understand that the steps of the methods disclosed herein may be omitted, rearranged, combined, and / or modified in various ways without departing from the scope of this disclosure. Dashed boxes indicate optional steps of method 900.

[0080] For example, method 900 may include obtaining product data associated with a product having one or more parts at (902). The product data includes at least one of part name data, part identification (ID) data, part quantity data, and material data. The product data may be received by a product data management system of a PLM system. Part name data may include the name or description of each component, sub-component, and / or part in the product. Part ID data may be a unique string of characters and / or numbers for each component, sub-component, and part in the product, facilitating component tracking and management. Part quantity data may include the quantity of each component, sub-component, and / or part required to assemble or produce the product. Part material data may describe the material used for the parts in the product (e.g., steel, aluminum, plastic, etc.). Hierarchical data may indicate the structured relationships between components of the product, describing which parts are included in a component or sub-component, and / or which sub-component is contained within a component.

[0081] Method 900 may further include generating a lifecycle state at (904) for each of one or more parts of the product. The lifecycle state 208 for each part identifies whether a line item representing the part is historical, current, or in progress (e.g., having a label such as "historical," "current," or "in progress"). Additionally, the lifecycle state 208 for each part identifies at least one of the following: part version (e.g., original version, first version, second version) and version transition. Version transition can indicate or describe from which version the part was modified and to which version the part was modified.

[0082] Method 900 may also include, at (906), using a Bill of Materials (BOM) generation module to generate a dynamic EBOM based on product data and lifecycle status. The dynamic EBOM may be a table having at least one row item (or row) representing each of one or more parts in a product. Each row item in the at least one row item includes a lifecycle status and at least one of part name data, part ID data, part quantity data, and material data.

[0083] In some embodiments, method 900 may further include, at (908), modifying one or more parts of the product via a PLM system during a new revision period. As a result, at least a portion of the product data is modified due to the part modification to create modified part data. That is, one or more parts of the product can be modified during a new revision period via the above reference. Figure 2The PLM system 10 can be modified by at least one of the described CAR system 30, CAD system 32, CAE system 34, CAM / CIM system 36, and / or CMM system 38. The PLM system 10 can modify the part quantity, part name, part material, part specifications (e.g., size and / or shape), part hierarchy, or other attributes of the part to create modified part data.

[0084] In various embodiments, method 900 may include at (910) generating a new lifecycle state and a historical lifecycle state for a part among one or more parts that have been modified or are being modified, during or after a new revision period. Subsequently, method 900 may include at (912) updating the dynamic EBOM in response to the modified part. Updating the EBOM at (912) may also include at (914) adding row items to the table corresponding to the modified or being modified part to create historical row items and current row items. The current row item includes the new lifecycle state, the modified data, and at least one of part name data, part ID data, part quantity data, and material data for the part among one or more parts in the product. The historical row item includes the historical lifecycle state, and at least one of part name data, part ID data, part quantity data, and part material data for the part among one or more parts in the product.

[0085] In some embodiments, the modification at (908) may include changing a part of one or more parts of a product from a first version to a second version via a PLM system during a new revision period. In such embodiments, the historical lifecycle status describes the change of a part from the first version to the second version. In other embodiments, the modification at (908) may include at least one of the following: modifying part name data to generate modified part name data for the part in the product and modifying part quantity data to generate modified part quantity data for the part in the product. In such embodiments, the current line item includes at least one of the modified part name data and the modified part quantity data, and the historical line item includes the (unchanged) part name data and the (unchanged) part quantity data.

[0086] In many embodiments, during a new revision period, the method may include generating a new lifecycle state for the part being modified among one or more parts to describe that the part is in the process of being modified. For example, when one or more parts are being modified, the lifecycle state may be reflected in the dynamic EBOM, for example, with the label "in progress" or other similar labels. In contrast, after a new revision period, the method may include generating a new lifecycle state for the modified part among one or more parts to describe that the part was modified during the new revision period.

[0087] In many embodiments, the method may further include organizing a table based on the lifecycle state of each part. Organizing the table may include selecting one or more lifecycle states of interest. Based on the selected lifecycle states of interest, the method may include removing row items from the table that do not include one or more lifecycle states of interest. Subsequently or simultaneously, the method may include retaining row items in the table that include the lifecycle states of interest. This will result in a table showing only the row items with the lifecycle states of interest.

[0088] In many implementations, the method may include generating a Manufacturing Bill of Materials (MBOM) based at least in part on a dynamic EBOM. The MBOM may be adapted to manufacture the product, and the MBOM may be organized for the product's assembly, machining, and production. For example, in addition to the product's design details (including all components, sub-components, materials, part names, and part numbers) derived from the dynamic EBOM, the MBOM may also include manufacturing steps, tools, work instructions, and / or supplier details.

[0089] Furthermore, the method may include providing a dynamic EBOM to a PLM system's computer-aided manufacturing / computer-integrated manufacturing (CAM / CIM) system to derive one or more machine manufacturing models, at least in part, based on the dynamic EBOM. In this implementation, the method may also include providing the machine manufacturing models to a manufacturing machine to produce one or more parts of a product. In other words, the method may include providing the PLM system (… Figure 2 The CAM / CIM system provides a dynamic EBOM, from which the CAM / CIM system can derive machine paths that can be provided to manufacturing equipment for producing various parts of a product. For example, the CAM / CIM system can derive, at least in part, paths based on a CAD model and / or a dynamic EBOM for machining one or more parts of a product using subtractive manufacturing techniques such as milling, turning, grinding, etc., which can be provided to a subtractive manufacturing machine to produce one or more parts of the product. Additionally or alternatively, the CAM / CIM system can generate layer-by-layer deposition paths based on a CAD model and / or a dynamic EBOM 106, which can be provided to an additive manufacturing system to produce one or more parts of the product.

[0090] In various implementations, the method may include, for example, displaying a dynamic EBOM using one or more display devices (such as monitors, tablets, etc.), which may be related to the above-referenced... Figure 1 The user I / O control device 320 is associated with this. Alternatively or additionally, the method may include storing the dynamic EBOM in, for example, a memory device (such as the one mentioned above). Figure 1 In the aforementioned memory 26).

[0091] Traditionally, PLM systems employ a "revision-based" approach when engineering changes affect the EBOM (Established Bill of Materials). Each change creates a completely new EBOM, and the old EBOM is saved as history. The new EBOM typically differs from the old one only in the line items affected by the change that led to the revision. This is not an efficient approach because it results in massive data duplication. For example, traditionally, both the old and new EBOMs are stored in the PLM system, and each EBOM includes all entries, the only difference being the line items affected by the change. The dynamic EBOM described above can advantageously be a single, continuous bill of materials that includes all historical and current data for the product from the PLM system. For example, when one or more parts in a product are revised (or changed) using the PLM system, the dynamic EBOM can be updated to include the changes while retaining historical data. This advantageously prevents the creation of a new EBOM with each revision, significantly reducing data production and thus lowering data storage and maintenance costs. Furthermore, a dynamic EBOM allows all changes to the product to be viewed on a single EBOM.

[0092] Further details are provided by the following topics:

[0093] A method for generating a dynamic Engineering Bill of Materials (EBOM) in a Project Lifecycle Management (PLM) system, the method comprising: obtaining product data associated with a product having one or more parts, the product data including at least one of part name data, part identifier (ID) data, and part quantity data; generating a lifecycle status for each of the one or more parts of the product; and generating the dynamic EBOM based on the product data and the lifecycle status using a Bill of Materials (BOM) generation module, the dynamic EBOM comprising: a table having at least one row item representing each of the one or more parts of the product, wherein each row item in the at least one row item includes the lifecycle status and at least one of the part name data, the part ID data, and the part quantity data.

[0094] The method according to any of the foregoing clauses further includes: providing the dynamic EBOM to a computer-aided manufacturing / computer-integrated manufacturing (CAM / CIM) system of the PLM system to derive one or more machine manufacturing models based at least in part on the dynamic EBOM; and providing the machine manufacturing models to a manufacturing machine to produce one or more parts of the product.

[0095] According to the method described in any of the foregoing clauses, the lifecycle status identifier of each part indicates whether the line item of the part is historical, current, or in progress.

[0096] According to the method described in any of the foregoing clauses, the lifecycle state of each part identifies at least one of the following: part version; and version transition.

[0097] The method according to any of the foregoing clauses further includes: modifying a part among the one or more parts of the product via the PLM system during a new revision period, whereby at least a portion of the product data is modified due to the modification of the part to create modified part data; generating a new lifecycle state and a historical lifecycle state for the modified or being modified part among the one or more parts during or after the new revision period; and updating the dynamic EBOM in response to the modification of the part of the product by adding row items corresponding to the modified or being modified part to the table to create historical row items and current row items, the current row item including the new lifecycle state, the modified data, and at least one of the part name data, the part ID data, and the part quantity data of the one or more parts of the product, the historical row item including the historical lifecycle state, and at least one of the part name data, the part ID data, and the part quantity data of the one or more parts of the product.

[0098] According to any of the foregoing clauses, modifying the part includes: modifying the part of one or more parts of the product from a first version to a second version via the PLM system during the new revision period, and wherein the historical lifecycle status describes the part being modified from the first version to the second version.

[0099] According to any of the foregoing clauses, modifying one or more parts in the product includes at least one of: modifying the part name data to generate modified part name data for the part in the product, and modifying the part quantity data to generate modified part quantity data for the part in the product, and wherein the current line item includes at least one of the modified part name data and the modified part quantity data.

[0100] The method according to any of the foregoing clauses, wherein during the new revision period, the method includes: generating the new lifecycle state for the part being modified among the one or more parts, to describe that the part is in the process of being modified.

[0101] The method according to any of the foregoing clauses, wherein, after the new revision period, the method includes: generating the new lifecycle state for the modified part among the one or more parts to describe that the part was modified during the new revision period.

[0102] The method according to any of the foregoing clauses further includes: organizing the table based on the lifecycle status of each part.

[0103] The method according to any of the foregoing clauses, wherein organizing the table comprises: selecting one or more lifecycle states of interest; removing row items from the table that do not include the one or more lifecycle states of interest; and retaining row items in the table that include the lifecycle states of interest.

[0104] A computational system for generating a dynamic Engineering Bill of Materials (EBOM) in a Project Lifecycle Management (PLM) system, the computational system comprising: one or more processors; and one or more non-transitory computer-readable media, the one or more non-transitory computer-readable media jointly storing instructions, the instructions, when executed by the one or more processors, causing the computational system to operate, the operation comprising: obtaining product data associated with a product having one or more parts, the product data including at least one of part name data, part identifier (ID) data, and part quantity data; generating a lifecycle state for each of the one or more parts of the product; and generating the dynamic EBOM based on the product data and the lifecycle state using a Bill of Materials (BOM) generation module, the dynamic EBOM comprising: a table having at least one row item representing each of the one or more parts of the product, wherein each row item in the at least one row item includes the lifecycle state and at least one of the part name data, the part ID data, and the part quantity data.

[0105] According to any of the foregoing clauses, the lifecycle status identifier of each part indicates whether the line item of the part is historical, current, or in progress.

[0106] According to any of the foregoing clauses, the lifecycle state of each part identifies at least one of the following: part version; and version transition.

[0107] According to any of the foregoing clauses, the operation further includes: modifying a part among the one or more parts of the product through the PLM system during a new revision period, whereby at least a portion of the product data is modified due to the modification of the part to create modified part data; generating a new lifecycle state and a historical lifecycle state for the modified or being modified part among the one or more parts during or after the new revision period; and updating the dynamic EBOM in response to the modification of the part of the product by adding row items corresponding to the modified or being modified part to the table to create historical row items and current row items, the current row item including the new lifecycle state, the modified data, and at least one of the part name data, the part ID data, and the part quantity data of the one or more parts of the product, the historical row item including the historical lifecycle state, and at least one of the part name data, the part ID data, and the part quantity data of the one or more parts of the product.

[0108] According to any of the foregoing clauses, modifying the part includes: changing one or more parts of the product from a first version to a second version via the PLM system during the new revision period, and wherein the historical lifecycle status describes the part as being changed from the first version to the second version.

[0109] According to any of the foregoing clauses, modifying a part in one or more parts of the product includes at least one of: modifying the part name data to generate modified part name data for the part in the product, and modifying the part quantity data to generate modified part quantity data for the part in the product, wherein the current line item includes at least one of the modified part name data and the modified part quantity data.

[0110] According to any of the foregoing clauses, the operation further includes, during the new revision period, generating the new lifecycle state for the part being modified among the one or more parts, to describe that the part is in the process of being modified.

[0111] According to any of the foregoing clauses, the operation further includes, after the new revision period, generating the new lifecycle state for the modified part among the one or more parts, to describe the part being modified during the new revision period.

[0112] According to any of the foregoing clauses of the system, the operation further includes: organizing the table based on the lifecycle status of each part.

[0113] According to any of the foregoing clauses, organizing the table includes: selecting one or more lifecycle states of interest; removing row items from the table that do not include the one or more lifecycle states of interest; and retaining row items in the table that include the lifecycle states of interest.

[0114] This written description uses examples to disclose this disclosure, including best practices, and also enables any person skilled in the art to practice this disclosure, including making and using any device or system and methods of making any combination. The patentable scope of this disclosure is defined by the claims, but may include other examples that would occur to a person skilled in the art. Such other examples are intended to fall within the scope of the claims if they include structural elements that are not indistinguishable from the literal language of the claims, or if they include equivalent structural elements that are not substantially different from the literal language of the claims.

Claims

1. A method for generating a dynamic Engineering Bill of Materials (EBOM) in a Project Lifecycle Management (PLM) system, characterized in that, The method includes: Obtain product data associated with a product having one or more parts, the product data including at least one of part name data, part identification (ID) data, and part quantity data; Generate a lifecycle state for each of the one or more parts of the product; and The dynamic EBOM is generated using the Bill of Materials (BOM) generation module based on the product data and the lifecycle status. The dynamic EBOM includes: A table having at least one row item representing each of the one or more parts in the product, wherein each row item in the at least one row item includes the lifecycle status and at least one of the part name data, the part ID data and the part quantity data.

2. The method according to claim 1, characterized in that, Further includes: The dynamic EBOM is provided to the computer-aided manufacturing / computer-integrated manufacturing (CAM / CIM) system of the PLM system to derive one or more machine manufacturing models, at least in part, based on the dynamic EBOM; as well as The machine manufacturing model is provided to the manufacturing machine to produce one or more parts of the product.

3. The method according to claim 1, characterized in that, in, The lifecycle status identifier for each part indicates whether the line item of the part is historical, current, or in progress.

4. The method according to claim 1, characterized in that, in, The lifecycle status of each part identifies at least one of the following: part version; and version transition.

5. The method according to claim 1, characterized in that, Further includes: During the new revision period, a part of one or more parts of the product is modified through the PLM system, and at least a portion of the product data is modified as a result of the modification of the part to create modified part data; During or after the new revision period, a new lifecycle state and a historical lifecycle state are generated for the modified or being modified parts among the one or more parts; as well as In response to a modification to the part of the product, the dynamic EBOM is updated in the following manner: Add row items corresponding to the modified or being modified parts to the table to create historical row items and current row items. The current row item includes the new lifecycle status, the modified data, and at least one of the part name data, part ID data, and part quantity data of the one or more parts in the product. The historical row item includes the historical lifecycle status, and at least one of the part name data, part ID data, and part quantity data of the one or more parts in the product.

6. The method according to claim 5, characterized in that, in, Modifications to the part include: During the new revision period, the PLM system modifies one or more parts of the product from a first version to a second version, wherein the historical lifecycle status describes the part being modified from the first version to the second version.

7. The method according to claim 5, characterized in that, in, Modifying one or more parts in the product includes at least one of the following: modifying the part name data to generate modified part name data for the part in the product, and modifying the part quantity data to generate modified part quantity data for the part in the product, wherein the current line item includes at least one of the modified part name data and the modified part quantity data.

8. The method according to claim 5, characterized in that, in, During the new revision period, the method includes: A new lifecycle state is generated for the part that is being modified, one or more of the parts, to describe that the part is in the process of being modified.

9. The method according to claim 5, characterized in that, in, After the new revision period, the method includes: A new lifecycle state is generated for the modified part among the one or more parts to describe the modification of the part during the new revision period.

10. The method according to claim 1, characterized in that, Further includes: The table is organized based on the lifecycle status of each part.

Images