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.
1st example 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 need to tell you. There IS a solution. It’s called Windchill 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. This is why PTC has trusted us to be a valued solutions provider for their product Windchill Navigate. Learn more about it in our video “Windchill Navigate: Unlocking Product Data for Everyone.”
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 Windchill 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 Windchill 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. Windchill Navigate gives you the ability to customize the apps according to your company’s own organization and data needs.
Windchill 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 Windchill Navigate to Fit Your Organization
Our team of developers can customize and configure Windchill Navigate apps for your organization. Check out more information on managing product data and your design process with PTC Windchill Navigate.
This is part one of a three part series regarding PTC Arbortext, deciding whether to customize or not. In this series, we will discuss the benefits of customization, the costs of customization, and deciding whether to customize or not.
You’ll often hear of DITA in the technical documentation world. DITA stands for ‘Darwin Information Typing Architecture’ -it’s an XML-based open standard for structuring, developing, managing, and publishing content. Quite the mouthful huh? What you need to know about DITA is that it leverages XML to be used as a way of writing and storing your data so you can manage it like an asset. What does it have to do with PTC’s Arbortext? PTC was the first company to ever deliver a complete DITA solution – one where organizations can finally start to maximize their investment in service lifecycle management.
One of the most fundamental questions you have to face when considering an Arbortext implementation is whether to use the technical documentation software out of the box or develop customizations to adapt the software to your specific use cases and work processes.
In practice, this is not so much of an either/or decision, as a how-much decision. In other words, nearly every implementation has some amount of customization, even if it’s just tweaking a composition stylesheet to add your own appearance specifications to the composed output. For some applications, where one of the standard doctypes such as DITA or DocBook is adequate, that’s all you need. For other applications, you may want to add custom features, user interface elements such as toolbars and custom dialogs, a tailored doctype or schema to support specific data requirements, connections to other enterprise systems such as ERP systems, and so on.
Adapting Arbortext software to your specific business environment can provide a number of advantages. Here are some examples where customization can add value to your implementation:
Author Efficiency
Custom features and user interface controls allow the author to work more efficiently.
Example: if authors frequently need to change one type of element into another similar element, then adding a toolbar button and/or keyboard shortcut to trigger the operation can let authors do it with a single click or key press, as opposed to using the Change Markup dialog.
Workflow Integration
Custom integration with software can streamline processes in the workflow.
Example: Suppose you have part data stored in an ERP system, and you are writing support documents associated with the part data. In a stock Arbortext installation, you might need to export the part data as an Excel spreadsheet, and then copy portions of the exported data in Excel to paste into the XML document in Arbortext. In contrast, a customization could allow authors to click a toolbar button, make a few quick selections in a dialog box, and automatically extract, format, and insert the part data in the correct location in the document.
New Capabilities
Customizations allow you to add new features to Arbortext Editor.
Example: Suppose you have a metric that you want to track on your documents that depends on the number of specific elements in each document, such as graphic elements. You can easily add a feature that would count instances of a specific element and report that for a document. You could also generate a report for a set of documents found in a directory tree or a folder in a content management system (CMS). This would let authors get this information directly within Arbortext Editor, without having to switch to an external tool to do the analysis/reporting.
This publishing engine software can be customized in a number of ways, and frequently we see users customizing their stylesheets to make them look better or compliant with their publishing standards. Arbortext stylesheets are used to publish documents that have consistent styling and formatting, no matter who authored the document. Sometimes these stylesheet customizations can be significant and complex, but often we see a need to make simple modifications to the fonts, logos, and page margins. EAC QuickPubs provides users an easy way to make those simple style modifications and create great looking documents.
Stay tuned for the next post where we discuss the cost of customization.
If you’re looking for ways to adapt your environment to fit your organizations needs, EAC QuickPubs may be for you. It’s an add-on designed to style documents that fit your organizations brand at a lower cost than a customization to PTC Arbortext. You can create aesthetically pleasing part manuals, owner’s guides, service manuals and more with ease. Publish fast, cheaper, and better today!
Transform the way you design and publish product information through QuickPubs, an EAC product for PTC Arbortext. For more information about QuickPubs contact us. Publish faster, cheaper, and better today!
