In today’s complex digital landscape, the evolution of a product involves orchestrated maturity of many individual disciplines: design, engineering, manufacturing, planning, service. Each domain has a way to view and organize a product and specific properties and behaviors to assign to a product’s parts and assemblies.
Efficiently managing, controlling, and eliciting change on such an orchestrated set of product data begins with accurately aligning the evolving product design, aka CAD BOM, and the product engineering BOM.
Our customers have been talking with us for a long time about their needs for having a different product design and product EBOM. While the product’s design and EBOM views are complimentary, they have other data structures and support various functions. Also, the way the design and EBOM evolve is quite different, with different business processes and different roles in the company taking part in them.
For example, designers, research & development, and the different engineering disciplines use various design tools to author, innovate, and create a rich set of designs to be inserted into a design definition. On the other hand, product engineers, purchasing, regulatory, and service must define and manage cost, logistics, opportunities, operations, regional availability, and rules in what constitutes the product EBOM.
For another example, in some companies, design tends to take the lead. Design systems and components evolve first, and much of the EBOM tends to resemble the design structure, with some additions in the EBOM from product engineers. However, in other companies, the EBOM takes the lead. The product engineer defines the assemblies and parts to be designed, and the design structure tends to resemble the EBOM.