Why is it important to manage your product Bill of Materials (BoM) in a PLM (Product Lifecycle Management)? This is a tough question to answer across the board for every company, but this article breaks down what you need to know.
The level of BoM management in PLM can be dependent on your companies’ products, downstream systems, and product development processes.
With that in mind, here are some general benefits and reasons to manage the creation of your product BoM in PLM.
The benefit of bill of materials management in PLM
PLM in nature is meant to be a tool to help engineering manage their production date while allowing dynamic collaboration and change control throughout the product development cycle.
The data managed in a product lifecycle management system includes CAD and BoM information, as well as additional supporting product information and documentation.
PLM functionality typically allows an organization to store any and all product information in a structured manner. The structured manner is what properly represents the product within all stages of the product’s development.
This includes everything from initial design requirements, to manufacturing requirements and process plans, to quality assurance documents- all linked to a single product structure.
This gives you the ability to graphically see a truly complete representation of any and all products managed within the PLM system.
In addition, many of the top PLM systems (such as PTC Windchill) give you the ability to manage different views of a single bill of material.
For instance, you could see the design or engineering view of the structure and all design information needed for that BoM product structure.
You would also have the ability to look at a manufacturing view that has the structure defined in a way to support the best possible manufacturing process, while it also links to any supporting information and work instructions.
Additionally, you could see a service BoM that represents exactly what is on-site or on the hands of a customer, with linked product information specifically related to service or support (such as a service repair or product manual).
These systems focus on tracking and managing all cost and profit throughout the process.
Because of this, changes are tightly controlled and require significant steps to ensure proper applications across the system.
There are also few systems that allow for full product representation inside of ERP or MES as outlined above. Nor do they fully support many different views of the same BoM.
ERP tends to only manage what is required to properly manufacture or sell a product, which does not always represent the full product design or its full breadth of supporting information and documentation.
There many impacts on these fundamental differences.
When to use PLM for BoM Management
Here are some general concepts as to when to use PLM for BoM management.
When your product development is in the dynamic phases that require many changes and updates at each phase gate, your bill of materials should be primarily managed in PLM.
If your product requires specific requirements management, detailed manufacturing, quality work instructions, or an intensive manufacturing process, it’s in your best interest to use product lifecycle management for your BoM.
At the very least, all of your product information should also be managed, or linked to your product lifecycle management system to ensure full accountability to all information updates required in the instance of change.
Integrating ERP and PLM
At a minimum, if you have an ERP system it’s important to integrate your system together with PLM.
It’s essential to establish key integration points between your enterprise systems that send needed information back and forth to your enterprise resource planning solution. This will help you properly execute new product releases and changes.
By integrating your systems, your ERP processes will ensure all proper tasks and functions are executed in your ERP or MES systems.
From there, your ERP to PLM system integration would send information back to your PLM system to close the loop.
These are our best practices to help you get ahead and to take product data further. We would love to hear about your thoughts about this topic and answer any additional questions you might have. Feel free to drop a comment below or leave an inquiry under let’s talk.
Looking for an easy way to quickly assess your bill of materials and ensure projects stay on-time and on-track?
Part II – (You can read part 1 here) Evolving your BoM strategy, tools, and abilities. “EBoM vs. MBoM” transforms into “EBoM integrates with MBoM.” This integration includes associativity to one another, time saving tools, elimination of error prone manual steps & more.
Imagine eliminating the common disjointed processes, additional time, and error prone manual steps involved in the creation of downstream BoMs from Engineering into Manufacturing, Production and Service management.
Concepts & examples such as Manufacturing Bill of Materials (MBoM) are shown below, all under one system, integrated & associated, and created with a single click. Then they’re easily edited to meet downstream BoM needs.
BoM creation can be streamlined & improved by associatively creating downstream BoMs (S or M or other) and eventually, connecting them to your ERP system. For now, we’ll focus on the first step of this business transformation concept; the creation of the second, or downstream M or SBoM, starting with a simple EBoM example, created in minutes, and easily viewed & tracked.
Who should be involved in this topic at your company? Ideally, your Configuration Manager role should be leading or heavily involved in this process.
The starting point & tool is PTCs Windchill and your willingness to change & improve.
Once your CAD data is ready to check into Windchill, there is an option (check box) to auto-associate the EBoM to a downstream BoM such as an MBoM. It is a 1:1 relationship for starters. Options can branch out from here into many CM (Configuration Management) directions. Such as multi-level BoM management, uses, visualization and more.
Once created, you can manipulate & edit the default 1:1 downstream BoM to your needs; adding bulk items, manufacturing specific sub assemblies, (build throughs) even new service end items. You can also flatten out an EBoM to meet assembly or production needs. BoM items such as adhesive, lubricant, paint or coatings, packaging items, all things that typically are not on an EBoM, can and do belong on the M or SBoM.
If this fits your company’s needs? consider using Windchill’s auto-associate feature.
This article covers a couple examples. If this is not deep enough…here are even more tools to consider. Topics such as creating associated manufacturing instructions, work instructions, work plans and more. Change Management is shown as reference only, it is an optional element of Windchill for another blog.
There are many options to this topic, these are common examples that fit a lot of needs and is considered a starting point.
1stexample shows all BoM & change components all connected in one system vs. manually done in silo fashion, which is industry’s most common method today. These examples are shown in PTCs Windchill reference viewer tool, which ties all related objects into view for easy visibility with just a few clicks.
- 1. EBoM structure (highlighted in green)
- 2. Change requests, notices and tasks (highlighted in red)
- 3. MBoM structure (highlighted in blue) with their own, or connected Change Management Requests, Notices & Tasks
2ndexample shows an EBoM, SBoM (Service Kit in this example), with a saleable end item service kit, as well as components for service or manufacturing BoMs. It also shows Changes, these can also be created, edited, routed, approved or rejected, and even include the SBoM if need be.
Please connect with EAC to learn more, to discover your company’s transformation opportunities with an assessment, maybe see a demo, or attend a webinar. The goal is to help your company transform how you design, manufacture, connect to and service your products.
Communicating product data across an organization has become more complex than ever. Here are 9 reasons it’s time to connect your enterprise systems.
With different departments gathering product data form a variety of systems including Product Lifecycle Management (PLM) Systems, Enterprise Resource Planning (ERP) Systems, Manufacturing Execution Systems (MES), and Quality Management Systems (QMS) and more, how do we know our organizations are making the most out of all the information we’re collecting?
Just think about it for a second. Our systems and departments speak different languages, while a company likely aims for a single goal. This is why it can pay to connect your systems and provide company-wide access to business and product knowledge
With an estimated 90% of the world’s data created in the last two years alone (Conner, n.d.), it’s no wonder that companies have trouble utilizing it all. The IDC estimates that just 0.5% of the data we companies produce is ever used. It’s time to change that.
1. Increased Usability
Data experts believe that if Fortune 1,000 companies increased the amount of data they used by just 10%, they could realize over $65 million in additional net income (Marr, 2015). These numbers are huge. Hopefully, they help you understand why I’m writing this blog and pleading my case.
The truth is – our systems are currently too complex for many roles within our organizations to navigate, find, and transfer the right information. This leaves our separate departments accountable for communicating different product data.
So how do we make our product data more usable? By democratizing our product data from all existing sources into one single system.
2. Better Access to Data
The most important reason your product data shouldn’t (internally) be kept a secret is because product data is your company’s most valuable asset. Not everyone who needs access to specific product information hosted in your PLM system is from your engineering department, so why force them through the same vigorous Product Lifecycle system training?
In order to effectively use data, departments must have ready access to it.
After all, the solution to this problem must make rich product information easy to accessible for a broad set of roles. By creating an organized system that connects all of your product data, your organization’s information is easily assessable to users beyond those who have created it. Just think of the possibilities if you connected your data from multiple systems and delivered it to all departments through individualized, role-based views.
3. Complete Data
Imagine an entire enterprise with access to real data, at the right time, when it’s needed. By connecting your product lifecycle management systems with your other enterprise systems, every stakeholder within your organization can leverage product data from multiple systems. They can make accurate decisions based on the latest, most accurate information from EBoM, MBoM, SBoM, ERP, MRP, and QMS data.
4. Better Insights
Better data + better visibility = better insights. Your teams are demanding more at lightning speeds from your PLM processes and solutions. This is another reason why your organization might consider integration technologies and custom front-end solutions.
An enterprise with insights into how current products and processes can be optimized can drastically improve overall productivity. Providing your team with access to up-to-date, accurate product data will allow your organization to have better insight into areas for continuous improvement.
5. Better Decisions
Ready access to information is especially important to any company involved with product development.
Users without access to information often make assumptions and resort to workarounds. This opens the door to poor decisions and errors, quality problems, and waste. Decisions made from out-of-date, inaccurate data threaten product quality and delay time to market.
By providing everyone in your organization with broad visibility into your organization will drive better, more accurate decisions. This will improve your quality, reduce waste, scrap, rework, and meeting your time-to-market goals. The analytics resulting from connected systems help users across your organization make accurate decisions throughout your entire development process.
6. Better Products
Who doesn’t want to create better products faster? Providing your organization with universal access to data will allow your company to drastically accelerate product development. How so? By connecting disparate systems, you will have access to real-time data allowing you to achieve better product decisions. Because your decisions and actions are now driven by up-to-date information, you will achieve a higher product quality.
7. Increased Productivity
Why waste time manually reading, entering and analyzing data, when it could be automatically collected, filtered, and combined? By linking enterprise systems into one simple interface, any user within your organization can access contextual, up-to-date, real-time product information anytime they need. I guarantee your productivity will grow when your organization is able to plan earlier with manufacturing, order materials sooner with purchasing all while your engineering team is spending less time pulling reports.
8. Increased Collaboration
Using a system that provides role-based access for stakeholders provides every role with the ability to quickly understand the status of a part number, inventory, and the part or assembly’s role in the “big picture.” This will not only help mobilize and inform the work of teams throughout the organization, but it will also help maximize the success of your product development. Giving your team the ability to extend and connect your PLM data into the rest of your enterprise will rapidly increase your overall organization collaboration.
9. Real Results
The ultimate benefit your organization will achieve by connecting your systems comes from your ability to get to real results faster. It makes the “to” in “Quote-to-Cash” just a little bit faster. What does that mean? Data gives your organization confidence to quickly deliver value. Good decisions, accurate manufacturing, knowledgeable service groups, self-sufficient marketing and sales teams. This all adds up to faster time to market, faster time to revenue — real results.
So.. what now? It’s time to connect your enterprise systems.
I know what you’re probably thinking, ‘this sounds great, but it’s not that easy to connect and provide role-based access to enterprise systems.’
And you’re right. It would take a tool that connects all of your enterprise systems, right? I’m glad you’ve stuck it out for the long haul — because this is what I’ve been waiting to tell you. There IS a solution. It’s called ThingWorx Navigate. What is it? It is a single role-based app that you can easily access from your smartphone, tablet, or computer where you can literally see all of your product data in one place — no matter what department you’re from. Mind blown? We knew we needed to get our hands on it the moment we found out this solution that everyone has been looking for — which is why PTC has trusted us to be a valued Solutions Provider for their product ThingWorx Navigate.
Watch our video on how easy it is to use ThingWorx Navigate and how it may change the way your company does business.
It’s no surprise that product data is your organization’s most valuable asset. Product data gives the employees within your organization the key to their own day-to-day success. Most enterprise software tools are inaccessible to a broad range of users due to costly licensing, extensive training, and the time it takes to personalize the data for various roles throughout an organization.
Imagine how powerful your company can become with one centralized hub everyone within the organization can access without over complicating the product design process.
EAC Product Development Solutions is a Solutions Provider for PTC – which means we give companies access to the latest technologies that the Industry has to offer for product development.
What is ThingWorx Navigate?
PTC’s latest genius product has us all jumping up and down with joy as it is something that will ultimately make your lives easier. PTC ThingWorx Navigate (formerly known as PTC Navigate) is a role-based app that gives your team a platform where every department can access product information through one centralized hub. Instead of having to manually access your Enterprise Resource Planning (ERP) or your Product Lifecycle Management (PLM) system to find the information you need to share with other departments, each individual will have access right from their smartphone, tablet, or desktop computer.
The image below shows just some of the out-of-the-box apps available to PTC Navigate users. ThingWorx Navigate gives you the ability to customize the apps according to your company’s own organization and data needs.
ThingWorx Navigate offers a modern user experience that is as easy to use as a smartphone app. It’s time you started unlocking the potential of your product data.
How We Can Customize ThingWorx Navigate to Fit Your Organization
Our team of developers can customize and configure ThingWorx Navigate apps for your organization. Our developers created EAC Productivity Apps, custom- built “apps” for PTC Windchill and other enterprise data – called PLMReports and QuickAccess.
The screenshot you see below is a configuration of PLMReports, displaying a search filter for a part number.
EAC’s Implementation Consultant, David Sichi, says that “PLMReports is an app that acts as a centralized location to run Windchill reports from within ThingWorx. From here, a number of different reports that would appear in different locations in Windchill can be run from the same page. Each report can be accessed by double clicking it’s row, bringing up a small input search filter screen. After populating the specified criteria, the report results can be displayed either in the same window or brought up in a new tab to retain the current page.”
The screenshot you see below is a configuration of ThingWorx Navigate created by our engineers called QuickAccess.
QuickAccess provides simplified access to PDM (product data management) and ERP data and visualizations. Greg Montgomery, EAC’s Senior Implementation Consultant says, “QuickAccess provides simplified access for downstream and upstream manufacturing roles to select PLM data sets. The simplified interface results in an improved end user experience and ultimately greater user adoption of PLM.” EAC Productivity Apps and ThingWorx Navigate capabilities make it easier for people to see and submit change, variant, and deviation requests throughout their product development processes.
Check out more information on managing product data and your design process with PTC ThingWorx Navigate with our free eBook here.
In last week’s post I walked through a manufacturing use case without Product Lifecycle Management (PLM). I hope you noticed the possible issues and costs related to restricting Manufacturing direct access to PLM and engineering data.
If you missed last weeks post, you can read it here:
Product Lifecycle Management in Manufacturing: Part 1
This week I will use the same use case story. The only difference will be manufacturing has access to PLM. I have also included manufacturing specific modules, which are run through PLM as well. Manufacturing has access to these modules and uses them for all Manufacturing planning.
As before, Engineering completes a new product design and starts a release process of the product in PLM. One major difference now, is Manufacturing personnel are included at appropriate points in the new release process. There is a full integration between PLM and Enterprise Resource Planning (ERP) systems as well. This integration allows for automatic transfer of the Manufacturing Bill of Materials (BoM) to Enterprise Resource Planning (ERP) when appropriate based on processes managed in PLM.
One thing to note on the outline below; each system task, since it is in PLM, has links to all the required information engineering released as well as any supporting information. This is including manufacturing information, customer specification, and supplier specifications on purchased parts.
Part 1: Release Process
The lead Manufacturing Engineer receives a PLM task asking him to begin manufacturing planning for this associated new products design.
Part 2: Manufacturing Planning
The manufacturing engineer begins the layout of manufacturing processes in the PLM Manufacturing Planning System. This includes planning at each work cell. Each cell is linked to required resources, parts, CAD data, and manufacturing documents required to complete that cell action. With the correct system, this will have included all metrics required to properly and completely plan a manufacturing process.
If required, a Manufacturing BoM is based off of, and linked to, the Design BoM. This allows the Manufacturing Engineer to restructure the BoM as needed to allow for the most efficient manufacturing processes without losing ties to the design BoM and parts the manufacturing BoM was created from.
Once complete, work instructions can be created in web form or be printed to paper from this plan. The work instructions would include links to the correct Engineering data and required manufacturing documentation.
Part 3: Release Process Continues
Once the Manufacturing Engineer completes their planning tasks, all required parts and Manufacturing BoMs, are automatically added and/or updated into the ERP system via an integration to PLM.
During this same process, PLM system tasks are sent to purchasing to start the procurement process.
Tasks are also sent to the tooling designers to start tooling generation.
As mentioned, these tasks are automatically linked to all the required engineering and manufacturing information to appropriately complete each task.
Part 4: Tooling and Controls Tasks
Tooling designers access PLM to generate their tooling data and controlling programs directly from engineering 3D data.
The resulting CAD and other tooling data are also saved to the PLM system. This data is linked to Engineering data, Manufacturing data, and the Manufacturing process plan.
Machining paths and other controlling programs generated are also created and saved to PLM with the same functionality mentioned above.
Having these links from manufacturing to engineering data allows for full impact analyses of any potential changes being planned for the product by the company. As well as insures all downstream data is updated appropriately when an engineering change does occur.
Part 5: In-Process Change by Engineering
While ramp up is happening, Engineering makes a last-minute change. Once the change is complete in Engineering, they start a change process that includes all downstream departments. Each department receives a PLM system task with the all required information related to the change linked to the task. This includes purchasing, manufacturing, tooling, etc. Each department acts upon the change, completing all internal department actions required.
Once all of the departments have completed their tasks in PLM, the change has been completed. Manufacturing ramp up continues leading into the initial manufacturing process.
Part 6: Issue Tracking and Correction During Manufacturing
During the initial manufacturing process, a manufacturing team member notices there is a clearance issue with the design. The team member verbally notifies their cell leader of this issue. The cell leader creates a change request in the PLM System. During that process, he creates a digital markup that is saved with the change request. The change request is created referencing the engineering data the issue is related to.
The engineer responsible receives a PLM system task notifying of this problem. The engineer takes the needed corrective actions and updates the CAD data. This CAD data is then revised released and included in the problem report.
The cell leader receives the notification the problem report was approved and corrected. The updated CAD data is included, the cell leader and the manufacturing floor team member can now reference the new data directly from PLM and make the needed correction.
This happens many times during the initial manufacturing process. The necessary PLM processes are initiated based on the issues found during the initial manufacturing run.
Manufacturing uses PLM to gain access to engineering data because it always references the latest released information. This insures nothing is made from outdated information.
Part 7: Final Product Release
The final product is released to the customer.
All as-built information has been saved in PLM, meaning most of the related engineering data has been changed via the PLM process capturing changes. Anything that hasn’t been corrected yet is also saved via electronic markups to be processed later.
Part 8: Another Manufacturing Run
One year later, the company needs to do a manufacturing run on this same product. However, they have a large turnover with their manufacturing employees. Only a few people are there that worked on the first production run of this product. Without the use of PLM, this could be a disaster. However, all as-built changes where captured in PLM for the first production run of this product and manufacturing is still using PLM to access all build information. This allows manufacturing the ability to properly prepare for the next run. This resulted in very few, if any, issues during the next production run.
Hopefully it is easy to see the benefits of giving manufacturing direct access to PLM, even based on this limited use case example.
There are many benefits to utilizing PLM in manufacturing. Much more than is appropriate to list in a blog. If you’d like to take a deeper dive, please contact one of our experts here at EAC. We would love to talk you through all the benefits PLM utilized in manufacturing could offer you.
In the meantime, reading our eBook, “Designing an Effective Change Control Process” may be helpful. We walk you through how to design a change control process to improve productivity and reduce quality issues.
Many still think that a Product Lifecycle Management (PLM) system is only for the Engineering department. At one point that may have been true. However, I am starting to see a shift in that mind set. More companies every day are starting to see the benefit, and even the necessity, in giving manufacturing direct access to the appropriate engineering data through a robust PLM system.
In this two part series I am going to outline a fictional use case both with and without PLM. My intent is for this to highlight the benefit of PLM in manufacturing. Please realize the use cases are not all inclusive. There are many possible actions that need to be taken to start manufacturing of a new product. I am simplifying for purpose of maintaining a storyline that is easier to follow along.
In the first use case, engineering is working in a PLM system and Manufacturing is not. Engineering uses PLM for data management, process management, and controls their release process utilizing this system. However, only engineering has access to this PLM system.
When a new product is released to manufacturing, only the drawings associated to this product are printed on paper and put in a folder and then physically handed to manufacturing. Once manufacturing has this folder, they begin the required tasks to begin production of this product. I will outline below what a possible workflow might look like in manufacturing without a PLM system.
Part 1: Initial Manufacturing Product Release Tasks
The required parts are manually entered into the Enterprise Resource Planning (ERP) system. In many cases, the parts are entered into a manufacturing Excel file instead. Requests made to purchasing to procure parts and raw materials required, utilizing copies of the 2D prints to send to the suppliers. After that, a Bill of Materials (BoM) structure for the parts is manually created to support the required manufacturing processes.
Part 2: Process Planning
Manufacturing will then begin the layout of processes required to manufacture the product. In many cases, the layouts are also created in Excel.
Part 3: Tooling and Controls Design
The tooling designers recreate the required 3D models from the 2D prints. The designs are typically saved in an uncontrolled manner such as on a local drive on a user desktop. The machining paths and other controlling programs are generated from these uncontrolled tooling files as well.
Part 4: In Process Engineering Change
While the ramp up is happening, engineering has the ability to make last-minute changes. If a change is made, a new 2D print must be created and supplied to manufacturing. Manufacturing must attempt to replace all copies of the printed design with a new copy. When this happens, there is great risk associated with having two of these copies floating around. Designers are manually notified to make the required changes, as are the supplies to make the required changes to the new prints. Manufacturing planning must adjust processes based on these changes as well.
Part 5: Finish Ramp Up
Manufacturing ramp up continues leading into the initial manufacturing process.
Part 6: Begin Initial Manufacturing Run
During the initial manufacturing process, a manufacturing team member notices there is a clearance issue with the design. The manufacturing team member verbally notifies their cell leader of this issue. The cell leader will then make a phone call to the engineer whose name is on the print and explains the problem. The engineer tells him to grind down the part to allow the needed clearance. The cell lead marks by hand on the print how much the part must be grinded down. If the engineer remembers, he will also update the 3D design to match this. It’s unlikely they would request a formal change to be release. One thing to note here is that there is no history of this interaction anywhere but on the market up print on the manufacturing floor.
This happens many times during the initial manufacturing process. Typically, only major issues are formally documented which will drive a full change process in Engineering.
Part 7: Out-of-date Information on Manufacturing Floor
One sub-assembly was made using out-of-date information due to outdated prints being used. Rebuild of this sub-assembly was required.
Part 8: Product Release
The final product is released to the customer.
Most of the as-built documentation is saved on paper in a folder in the manufacturing offices.
One year later, they need to do a manufacturing run on this same product. However, they have a large turnover with their manufacturing employees. Only a few people are there that worked on the first production run of this product. They were not aware of the as-built mark-ups manufacturing had in their folders. So, many of the same issues were found and had to be corrected in this manufacturing run again.
I listed a few possible issues that could come from uncontrolled information used in manufacturing. I am sure you can imagine, or even experienced other possible issues.
Keep your eyes peeled for next weeks post where I review the same manufacturing process, but this time with manufacturing having direct access to Product Lifecycle Management (PLM). If you would like to learn more about the benefits of PLM in manufacturing you can download our eBook, “Designing an Effective Change Control Process” here. This eBook discusses how following a change control process would likely improve productivity and reduce quality issues. The benefits of having a controlled process in place substantially outweigh the initial time and resources to get started.
