Instead, modern BOM solutions connect these engineering domains within an integrated product definition. This maximizes efficiency by making it easier to manage change and configuration. It also provides a “single source of truth” product definition for downstream manufacturing and service disciplines.
Aligning all relevant data to a comprehensive engineering bill of materials sounds great on the surface, but what about the experience of the user?
View the BOM in Domain Context
How do your users, who are now bombarded with information, get their jobs done effectively and efficiently?
For every product, you have to manage massive amounts of data.
Typically, only a fraction of that data is relevant for a particular task. Consider the example of a rocket launch vehicle for sending a satellite into space. Critical to the success of this product is keeping mechanical and electrical components in synch – working together correctly.
However, your mechanical engineers have no need to see all the intricacies of the electronic and software components. Having them wade through information that is not pertinent to their task wastes precious time.
The ideal product lifecycle management (PLM) system would allow every user to work in context with their own BOM view. At a basic level, the system should seamlessly enable the integrated product definition to be leveraged by all stakeholders. This allows groups to organize and capture information that is relevant to their domain without affecting the other. The solution should not involve duplication of data to support different teams.
Duplication requires a lot of synchronization and leads to costly mistakes due to out-of-date information. Your PLM backbone needs to keep all pieces of the integrated product definition in synch as parallel evolution of the product takes place.
The solution can’t stop with only domain specific work in context. For many products, even that would still result in massive amounts of data. Consider again the rocket launch vehicle for sending a satellite into space.
An engineer doesn’t really need a model of the entire rocket and payload. They are most likely focusing on one particular component or subsystem, say, an infrared camera. Ad hoc views can help define the data needed on the fly to accomplish the task at hand.
Ad hoc views allow quick search and filtering across massive amounts of data. This way, you only gather the requirements needed to fulfill a particular task. With this context, the data is more easily understandable and more useful.
Your PLM solution must provide the ability to create and manage data focused on specific tasks, but always in the context of the entire product.
This approach allows individuals and teams to create and work more efficiently on their specific assignments. Also, it greatly facilitates their management of in-context and relevant technical knowledge.
This approach enables multiple teams in all departments and operations to work in parallel to reduce cycle times while maintaining strict compliance to all regulations.