When you’re dealing with engineers you’re talking CAD and design; when you’re working with purchasing and production you’re talking ERP and SCM. And if you have to share product data between these groups, the only way to make sure each system accepts the information is to send everything via email and spreadsheets.

While email and spreadsheets are fine for some things, they are not the best way to share a build package or a change order.  This is why we developed Arena PDXViewer—a free cloud application that displays PDX build packages in an easy-to-read, navigable format. (To learn more about the PDX file standard, check out my previous post.)

We built PDXViewer for ultimate usability, enabling it to work on any computer with any operating system and without any required set up. Our viewer has been the cleanest, simplest viewer on the market for some time, but we’ve recently introduced a new feature that brings PDXViewer to the next level—the ability to filter a build package.

Introducing Filter—the easiest way to break your BOM up into supplier-specific build packages

With Filter, you have the flexibility to decide what to include and exclude in your PDX build package. This new feature means that PDXViewer now gives you complete control over the exact set of parts and drawings you share with a subcontractor, vendor or manufacturing partner.

How to use Filter to control your product data

Filter addresses an issue that affects everyone in the manufacturing process—control over what data is shared.

• Engineers can use Filter to remove unwanted or private files, items, manufacturers and contacts from a build package before sharing with downstream partners, or requesting a quote.
• Procurement can use Filter to break build packages up into vendor-specific data sets for clear, unambiguous communication with vendors.
• Operations can use Filter to attach a customized build package to a work order so manufacturing partners have all the information they need to do their jobs.
• Contract manufacturers can use Filter to create a unique build package for each vendor when outsourcing aspects of production, such as cables, PCB, enclosures, or the shipping and packaging.

Give PDXViewer a try—it’s free!

When sharing a build package, there is always the concern that including too much information will lead to unwanted exposure of private or erroneous data, or confusion on the part of the recipient. With the addition of Filter to PDXViewer, you can rest easy, knowing you are in complete control of what data travels down the supply chain.

Try PDXViewer today for free—create and share build packages with more control and fewer errors.

Let me explain.

We’ve come a long way since our early days as BOM.com, and today Arena is used by thousands of manufacturers around the world. And while we’ve solved the problem of capturing, communicating and controlling product data for small to midsize organizations with our cloud PLM software, we know that data management is still a challenge for the lone hobbyist, the garage startup or the small business that is still deciding on vendors and processes, or building out their supply chain.

Managing product data should be a no brainer—even if you’re just two guys in a garage

To solve this problem, we’ve launched two new products that can help manufacturers and engineers get their designs documented and shared earlier in the process—Arena PartsList, and Arena PDXViewer.

Together, PartsList and PDXViewer create a lightweight solution that requires no organizational initiative and no set up. Using PartsList and PDXViewer together, engineers can import designs from ECAD, automatically pull in critical component information and create a fully documented BOM (which can be shared as read-only build package for fast quoting or building.)

How PartsList and PDXViewer help you document and share your designs from Day One

Arena PartsList—create and share clean, fully documented BOMs

Arena PartsList is the ultimate lightweight tool for design engineers. With one click, PartsList turns any list of parts into a purchasable BOM you can share with doc control, purchasing or potential vendors.

If you import designs from your ECAD tool and select Autofill, PartsList will automatically pull the datasheets and key component attributes for all the parts in your list. If you’re browsing parts online, you can use the PartSaver bookmarklet to capture critical component information in one click.

You can use PartsList to create any number of parts lists, organize them however you like them share your lists with anyone who needs them by exporting to CSV or PDX.

PDXViewer—display PDX build packages in an easy-to-read, navigable format

PDXViewer is a free tool for sharing easy-to-read, organized BOM data with anyone who needs it. PDXViewer opens any PDX file (including ones you create with PartsList) and can be used on any operating system or machine. PDXViewer takes the hassle out of handing off the BOM, and is a great tool to use with vendors and suppliers.

Although easy to use, PDXViewer is extremely robust. In addition to viewing PDX files, you can use PDXViewer to break a build package up into smaller subsets of data to share with subcontractors, vendors or manufacturing partners. With the ability to preview your files, or share exported change orders as redlined PDX packages, you can be sure you are always sending the right data downstream.

Right-sized PLM solutions for every manufacturer, at every stage of development

Although we are extending the benefits of cloud PLM to a larger audience, don’t think we’ve forgotten about our current customers. At its core Arena is about cloud collaboration—whether through our new lightweight apps, or our scalable BOM and change management tool.

We decided to extend the benefits of cloud PLM to a wider audience because we believe that all manufacturers—at all stages of development—deserve an easy-to-start, easy-to-learn, easy-to-use solution for centralizing product data and sharing BOMs with suppliers.

With PartsList and PDXViewer, we now fully support product design at every stage of the market. We have tools for the individual, for the partnership, for the startup, for the small and midsize companies, and for the large organization. At any size, and any price point, you can rely on Arena to help you capture and easily share your designs.

PDXViewer is a free tool from Arena. You can try PartsList for free for 90 days. Sign up now—and help influence development going forward by sending me your feedback or posting to the comments. Thanks!

For more information

Arena PartsList—create and share clean, fully documented BOMs

PDXViewer—display PDX build packages in an easy-to-read, navigable format

Don't let Excel keep your BOM on lockdown.

Imagine where you want your business to be in five years. Can you get to that place if you’re still managing your BOM revisions and changes in Excel?

For most manufacturers, the answer is no. Excel is a shortsighted business tool—not well equipped to manage change and collaboration with internal teams, let alone a global supply chain.

When you’re ready to move out of Excel, here are 10 simple tips for getting your data into a more long-term BOM management tool—all while protecting the integrity of your existing data.

Start by getting your existing product record in order.

1. Establish a consistent naming convention across all cells.

Your computer does not know that “AVX Corp.” in your master supplier list is the same part source as “AVX.” So avoid confusion down the road and clear it up now.

2. Simplify the look of your spreadsheet.

Colored text and cells may look nice but they make your spreadsheet more complicated than it needs to be, increasing the odds that you will lose data in the migration process. Rather than fancy formatting, use a separate column to draw attention to important information.

Validation Lists, set up under Data in the Menu bar, help protect your data from typos.

3. Protect your data from accidental corruption with data validation lists.

You can limit the choices for entry in a given cell by setting up validations lists, which let you dictate a pre-determined set of entries that are acceptable for a given cell. You can then restrict the cell to only accept entries offered in that list.

4. Double check your number formats.

You can indicate what type of data belongs in each cell (dates, currency values, percentages, etc.) Choosing the right format protects your data from problems like the loss of leading zeros.

5. Get rid of any placeholder values.

If you don’t know a particular part number, leave it blank. A mock entry can accidentally be interpreted as a valid value.

Once you’ve cleaned house, you’re ready to start your data migration.

6. Determine which data you want to move.

We recommend you only prepare live data for the move. You can keep archived data in Excel or move it over at a later date.

7. Start small and work your way up.

Prepare your smallest dataset for migration first—this makes it easier for you to uncover and repair kinks in your current data entry processes.

8. Double and triple check your data is clean and stable.

Are you using a consistent method for part naming and descriptions? Are your numbers in their correct formats? Checking that the data is clean will help you avoid problems with bad data in your new system.

9. Squash any lingering typos.

Because of the nature of data entry in Excel, there is no simple way to catch typos. But here’s one trick that may help: identify any values that occur several times throughout your spreadsheet and run a simple ‘find’ search using a portion of the entry that is the least likely to have been mistyped (such as the first few values). For each finding, manually check to make sure the rest of the value in the cell is correct.   

Besides mistyped values, beware of forgetting commas between reference designators.

10. Think like a computer.

Make sure all your values are entered consistently and labeled clearly. Avoid relying on subjective or visual cues like tabs, fancy formatting or indents.

I hope these simple tips for a smooth data migration will help you prevent miscommunications and inefficiencies down the road. And better management of the product record means you’re one step closer to actualizing your ultimate business vision.

For more information:

Ten tips to get by when you’re relying on Excel

The hidden costs of using Excel for BOM management

Three essential tips for BOM control

BOM Management in Arena

If you're using Excel to manage your BOMs, it's only a matter of time before the strategy blows up in your face.

As product life-cycles continue to shrink, price pressures increase and the supply chain becomes more globally dispersed than ever before, it’s surprising how few manufacturers are prepared to manage the chaos.

For example, if you’re still using Excel to manage your product data, you’ve probably noticed that managing change and collaboration with a global supply chain is an organizational nightmare.

If Excel is causing more trouble than it’s worth in your organization, it may be time for a new system of product data management. But if you’re not quite sick of Excel yet—just wait. Here are five reasons why your days of Excel spreadsheets are numbered.

Five reasons why Excel spreadsheets are a temporary solution

1. Over time, your BOMs become larger and more complex. And as your product goes through multiple revisions, a spreadsheet simply cannot keep track of the change history to the product record. Such one-dimensional record keeping makes real collaboration nearly impossible.
2. BOMs are highly relational, which makes managing your product record on several static spreadsheets extremely challenging. As a growing number of internal teams and global suppliers need access to data and files, the problem is escalated. Eventually, it becomes nearly impossible to keep data accurate.
3. Because Excel can’t easily track product compliance requirements, this important piece of the product is often managed manually and separately from the BOM spreadsheet. Not surprisingly, this can lead to oversight of critical compliance requirements. Compliance status cannot be effectively managed when divorced from the original record, but if you’re using Excel, it may be your only option.
4. Multiple internal and external teams need access to the BOM to edit the product record throughout the product life-cycle. In many cases, multiple versions are created as “save as” docs. As BOM data is changed by multiple parties, and multiple people believe they have the most updated version, eventually the truth is lost among the spreadsheets. At that point avoiding scrap, rework and wasted time is nearly impossible.
5. Spreadsheets cannot communicate with other business systems such as ERP, so the product record has to be manually entered into the system—along with every new update to the product. For obvious reasons, this is not sustainable.

The BOM of the future—collaborative and centralized

The shortcomings of Excel BOMs boil down to this. You can not effectively collaborate with supply chain partners or guarantee that there is one version of the truth when you’re using Excel spreadsheets. So if you’re looking for a new way to manage your product data, consider tools that can do what Excel can’t—facilitate collaboration and centralization. Even if you’re just getting off the ground, you still need something lightweight that can keep everyone on the same page as you grow.

Your manufacturing process will only work as smoothly as the tools that manage it—so if you’re experiencing issues with Excel now, don’t wait around for them to get worse before adopting a solution that works.

For more information:

Beyond BOM 101: Next generation of bill of materials management

The hidden costs of using excel for bill of materials management

The best BOM resources from Arena

Don't fall into the trap of using the wrong tool for the job!

Why would I want to take the time to learn and implement a new tool when I have one that is doing the job . . . kind of . . . at least for now?

Sound like you?

We all have cut corners at some point in our lives— from using a half-broken umbrella to duct-taping a leaky pipe. Shortcuts are called that for a reason—they allow us to get a job done quickly and with less effort. But when it comes to your manufacturing process, cutting corners will ultimately cost you more.

Are you using the wrong tools for the job?

It’s understandable that getting products to market as efficiently as possible is a top objective. But don’t get so caught up in your rush to market that you don’t take the time to implement the right tools for the job.

One of the most common examples we see of this mistake is managing product records and business financials with the same system (usually ERP.)

ERP and PLM systems are not interchangeable

ERP and PLM both enable manufacturing companies to manage their design and production processes, but these tools are designed to work together, and aren’t an either/or solution. While PLM systems focus on the product record—the BOM, AML and revision history, ERP systems focus on the financial roadmap.

PLM—the system of record for your product

Includes:

• Bill of materials (BOM) management
• Item management
• Change management (ECR, ECO, ECN)
• Document management
• Compliance management

ERP—the system of record for your financials

Includes:

• Purchasing
• Accounting
• Inventory management
• Order management
• Sales forecasting

Knowing which business systems to use for which purpose, and getting your systems in place early is the best way to ensure your product makes it to market with minimal setbacks.

When should I use a PLM system?

A PLM system helps companies maintain an accurate product record throughout the entire manufacturing process by managing parts lists, BOMs, revision history and vendor lists. Any company who designs and produces complex or engineered-to-order products, manufacturers in-house, uses outside resources like CMs and suppliers or has multiple product lines will benefit from using PLM to manage their product record.

When does an ERP system come into play?

ERP systems help companies manage business financials and assist in sales forecasting, manufacturing planning and execution, customer care and support and shipping logistics. Companies that manufacture in-house or produce complex engineered-to-order products typically use ERP to share information between their finance, sales and manufacturing departments.

How do ERP and PLM systems fit together?

ERP and PLM systems provide the highest level of efficiency when integrated together.

Because PLM is intended to manage the development of your product and ERP is intended to manage the resource planning of your finalized design, it makes sense to start with a PLM system. After all, it’s a waste to plan out the resources for a product design that is still undergoing revisions.

Below, you can see how everything flows through PLM and then into ERP.

Learn more about ERP and PLM:

ERP and PLM: How these systems work together for manufacturing success

Set your PLM implementation up for success in three easy steps

A three-step approach for controlling your product data

At Arena, we have built a robust way to invite trusted suppliers into your decision making process, but there are still occasions in which you need a quick, easy way to send product data to one-time, transactional partners. That’s why I am so excited about Arena PDXViewer—it makes assembling and sending build packages, quote requests and BOMs easy.

If you’re already using a PDX viewer, I encourage you to try Arena PDXViewer—it’s web-based, easy to use and works on any computer. If you’re unfamiliar with PDX—read on to learn how this XML-based standard can revolutionize the way you connect with your suppliers.

Life before PDX

If you’re not using PDX files to share comprehensive product data (including AMLs, BOMs, change orders, etc.) you can probably relate to how difficult it is to make your BOM accessible to external teams.

Without PDX files, preparing a build package for delivery is a mixture of black magic, blood, sweat and data from a business system. In some companies, one person is hired or trained to access the system for the sole purpose of sending data to suppliers once or twice a year. At other companies, data is pulled manually out of the PLM system by the design engineers, who put the data into an Excel spreadsheet and send it to suppliers in binders or zip files.

There are several problems with the manual methods of data sharing. For one thing, it’s nearly impossible to maintain the original BOM indentation when you export to Excel or try to print, and you may end up making PDFs of screen shots to try and maintain the original format. If you need to get rid of confidential data before sending your data, the process takes even longer. You quickly end up using tools like Paint or Acrobat, or find yourself at the printer with scissors, Wite-Out and a glue stick.

It’s amazing how many time-consuming, error-prone methods there are for getting product data out of a PLM system, when all you really need is a simple, standardized format for sharing PLM data.

A case for PDX

If you’re sick of all the workarounds, you may be ready for PDX—an open IPC XML-based standard with a solid and devoted following.

PDX is a great way to maximize your PLM usage because it incorporates suppliers—and anyone else who can’t access your PLM system—into your process in a clean, secure way.

PDX acknowledges that not everyone will be a PLM power user, and takes the burden off of engineers and doc control to get data from business systems for colleagues and vendors.  For power PLM users who have to work with a wide variety of people, PDX means easy data consolidation and sharing. Suppliers can even use PDX to run exports with BOM attachments as needed, or take the information and upload it into a variety of systems.

The PDX standard is fast, but more importantly, it minimizes errors. Because PDX is a read-only snapshot, you don’t have to worry that your data will get tampered with or that errors will be introduced to your BOM. PDX really is a fool-proof way to get structured product data out of your business system, and get it to the people who need it.

PDXViewer—a PDX viewer from Arena

As we announced earlier this year, Arena offers a free PDX viewer that is more convenient, and easier to use than any other PDX viewer on the market. (Check it out at arenasolutions.com/pdxviewer.)

Based on customer feedback, we recently updated the Arena PDXViewer interface and added the ability to highlight BOM substitutes. We believe these updates really increase the value of PDXViewer, and extend its functionality even further.

We have already seen how useful PDX can be, and we are committed to improving the process for Arena customers and other users. If you have never used PDX, I would urge you to give Arena PDXViewer a try. It works with SAP, Agile, Arena, Teamcenter and WebSphere systems, go to arenasolutions.com/pdxviewer, and check it out.

For more information

Announcing Arena PDXViewer: A free web app for sharing product data

Today I wanted to do a bit of a round-up, and share some of our most popular “BOM” blog posts and downloads from the Arena website.

Enjoy! And if you have any additional questions about BOM management you’d like us to answer on this blog, post to the comments and I will be sure to get back to you.

Engineering BOM: the ins and outs

The EBOM is the starting point for any product. Learn how the EBOM differs from the MBOM, and download the Arena BOM Master Kit—one of our most popular downloads.

The manufacturing BOM: critical for successfully building a product

Unlike the EBOM, which is organized according to the design of a product, the MBOM is structured to support how a product is assembled. Here are tips for better MBOMs and a link to the Arena BOM Master Kit.

Beyond BOM 101

This free download discusses:

• Current BOM management processes and their associated challenges
• Current BOM management tools
• New automated tools to manage BOMs
• Benefits of selecting the right PLM tool

Sample BOMs

Need a visual? Here’s how a GPS navigation product BOM would look in both Excel and a dedicated BOM management system like Arena.

Three tips for building better BOMs

The best BOM management system in the world won’t help you if you don’t create correct and complete BOMs from the start. Here are three tips I originally shared on the Arena Blog about building better BOMs.

10 tips for better Excel BOMs

If you are managing your BOMs in Excel, here are 10 tips to help you keep your data organized.

When is the right time to embrace a BOM management tool?

A successful startup shares how early adoption of product management tools fostered innovation.

What should you look for in a BOM management tool?

Not all BOM management tools are created equal. We highlight three key features that are must-haves in any BOM tool.

Should you manage your BOMs with ERP?

ERP systems are NOT optimal for managing product data during the design stage—find out why.

Why is it so hard to move a BOM from Engineering to Manufacturing?

An in depth explanation of common disconnects between engineering and production—particularly when it comes to managing the bill of materials.

 3 tips for taking control of your bill of materials

This cautionary tale tells the story of how the lack of a centralized BOM delayed one company’s launch for months. It also comes with a bonus—three key tips for keeping BOMs in sync and under control.

Sharing BOMs with your supply chain?

Use the PDX File standard to share your BOMs in a clear, structured format.

This raw information (BOMs, drawings, specifications, purchasing and sourcing information) is of critical importance to your suppliers, yet many OEMs lack visibility into how ambiguous their data can be when it’s received on the other end.

The idea of throwing product data over the wall is a major source of frustration for OEMs. While it can be a struggle to get the right information to the right person at the right time, its important that the people building your product receive the information they need.

Your CM: An ally in the fight against product record ambiguity

Fortunately, your contract manufacturer wants to minimize ambiguity too.

It shouldn’t come as a surprise that your CM partners dislike fighting over quality problems, excess and obsolete inventory, or the costs of a product recall or field service problem. And if the source of confusion is often due to incomplete, messy or outdated product data, this is something you can easily fix.

If you think you may be sharing less-than-perfect data with your suppliers, here is a list of four things you can do to ensure you are giving your supplier team the information they need to be successful.

Four things you must do to eliminate product record confusion!

1. Define:

• what makes each part/revision acceptable
• which parts should be used (and when)
• assembly instructions for how parts go together physically

2. Control:

• who can edit your BOMs (and how)
• how related BOM updates are grouped
• who reviews & approves BOM changes
• how & when BOM changes become effective

3. Communicate:

• sufficient information to build the product
• only the necessary information
• each and every update to the BOM

4. Collaborate:

• sign-off for BOM changes (in advance)
• requests for improvements
• up-to-date status

And a bonus tip (that a lot of companies struggle with): Keep a historical BOM accurate and unambiguous. To do this, it’s helpful to adopt a system that allows you to manage change over time (like Arena.)

Helping your suppliers is a win—win situation

Ambiguity can sometimes seem like an unavoidable part of the outsourcing relationship—especially when it comes to sharing your product record. But with the right processes in place, you can communicate with your CM partners with focus and purpose.

For more information:

Tips and resources for managing your outsourcing relationships

Three tips for effective product revision control and communication

To be successful, you need highly productive independent teams, as well as consistent and clear communication across departments and partner organizations. This means you need a single record of truth for your product that can be accessed at any time—even by key contributors in different time zones.

Your BOM =  the single record of truth that describes your product

For companies who build a product, a bill of materials (BOM) is the best place to maintain the single record of truth for that product. A BOM contains part details, drawings, change information and any other details that describe or show what you’re trying to build, and is an essential part of making sure all teams have a clear picture of what the product is, how it will be built and what it will cost.

Building out a complete BOM for every product, and developing an effective way to make and communicate changes to the BOM, is the best way to avoid mistakes as you move to production and beyond. If your BOM reflects last week’s truth, is missing product data or is updated in multiple places, it can mean disaster for your product.

Three tips for better BOMs

When managed effectively, the BOM can create interdepartmental awareness of the impact individual work has on other internal and external departments, and provides a solid foundation for making and communicating changes to your product.

While many companies (like Arena) provide services that can help you manage your BOMs once you’ve created them, the best BOM management system in the world won’t help you if you don’t create correct and complete BOMs from the start.

Here are some tips I’d like to share for building better BOMs—are there any others you think should be added to the list?

1. If you want it in the product, put it in the BOM!

This seems like a no-brainer when it comes to the core mechanical and electrical parts, but what about the random and non-modeled parts like glue, software, cables, and patch cords? If you have these types of elements in your product, make sure they’re in the BOM!

In addition, it’s important that the documentation, warranty cards, offers from business partners, and packaging are accounted for, because these pieces, while they may not directly be part of the product, affect the working of your product as well as your customer’s experience.

Your BOM should be a living, breathing record of your product, down to the last wire—and if something doesn’t make it into your BOM, or the wrong part makes it into the BOM, your product won’t be made correctly.

2. Be proactive about making BOM changes

When it comes to change, don’t assume that someone else has communicated your changes across the departments, or that the head nods in last week’s meeting meant everyone was listening to your idea. The best way to maintain the integrity of your BOM is to take responsibility for the changes you make, and ensure the right people see, understand and approve your changes to the product.

 3. Communicate, communicate, communicate!

Once you get to a place where you are confident that your BOM reflects the truth, the whole truth, and nothing but the truth, communication is key. (And this is where systems come in handy.) A system with built-in intelligence to warn managers when specifications in the design, engineering, manufacturing and marketing BOMs disagree is ideal, but at the very least you should define a process for communicating changes to the affected work groups.

Putting energy in to ensure your BOMs are correct, and defining a system for BOM amd change management upfront, ensures you never risk your business on assumptions again.

For more information on better BOMs

Everything goes BOOM: A product disaster story

Arena BOM Master Kit

The PDX file standard—an easier way to share BOMs with your supply chain

To learn more about Arena

Try BOM and change management software for free

Watch a demo of Arena BOM and change management software

Engineers are told to design something, manufacturers are told to make something.

Engineering opens the design funnel, manufacturing closes it.

Engineers wrestle multiple theoretical possibilities into a realistic design, manufacturers make that design a physical reality.

When you really think about it, manufacturing and engineering are asked to work in parallel while being completely at odds philosophically. Their differing educations, day-to-day tasks and departmental goals ultimately cause them to form very different beliefs about how things should get done. So is it any surprise that there are often disconnects between engineering and production—particularly when it comes to managing the bill of materials (BOM)?

During the design phase, the cost of change is low

When engineers begin to design a BOM in their CAD tool, the possibilities can seem endless. As they move through iterations to find the perfect solution, dealing with a restrictive change process can be extremely frustrating.

During this part of the design process the cost of change is very low, and so for engineers, the ability to iterate quickly and keep the creativity flowing is key. Changes to the design—however major—have nowhere near the impact they will have several hops later in the process when the entire supply chain is involved and real products are being molded and extruded.

For manufacturers, software changes have real consequences

On the other hand, once a BOM crosses over to the manufacturing side, actions taken in the software program actually map to actions in the physical world. When you change order quantities, or mess around with the components in the BOM, this can potentially cost your organization large sums of money. A plan to build 100k of Product A using xyz materials actually translates into those materials becoming a product—with connected inventory usage and labor costs. This focus on the present and the tangible is really what drives manufacturers to care so much about keeping things on track, and making sure changes are managed methodically and thoroughly.

Walking the line between engineering and manufacturing

With the differences in philosophy between engineering and manufacturing, there is a natural tension between these two groups—from the way each group manages product data, to the way each group prefers to handoff the BOM. But is this tension irreconcilable? While engineers often are frustrated by document control, manufacturers can be frustrated with an engineer’s desire to work and rework a product, pushing up dangerously close to production timelines.

Given  our application’s position in the engineering and manufacturing process, we see both sides of the story in every single customer who joins the Arena community. Because of our connection to both production and design, I am interested in hearing how each group has managed the engineering/manufacturing relationship.

I’d like to know—how have you come to consensus on how change revisions and the BOM itself should be managed?

If you have a particularly interesting story, send me an email—I would love to interview you for future articles.

For more information

Excel BOM Template—for organizations just getting started with BOM and change management

Engineering BOM—the ins and outs

Share clean snapshots of your BOM with PDXViewer

Turning great designs into great products: the changing world of mechanical design