One lesser-known consequence of outsourcing has been called the “outsourcing-induced job vacuum”—(based on the idea that no product is an island.) A fascinating New York Times animated video summarizes the concept like this—as assembly jobs move overseas, technical jobs such as design and engineering do too.

The infographic below shows how the top employers in the U.S. economy have shifted toward a service-based model. Take Apple for instance. While the company is worth more than some of the biggest oil, energy and manufacturing companies, it only employs 43,000 Americans. (In contrast with General Motors, which employed over 400,000 American workers half a century ago.)

Resources for businesses interested in onshoring

For many businesses, outsourcing overseas is still a necessary reality. However, if you are considering moving your manufacturing back to the U.S., here are a few resources that can help get you started.

SelectUSA is a website that maintains a database of current federal programs and incentives available for U.S. businesses, as well as testimonials from companies who have successfully kept operations at home. The website even breaks down resources by specific industry so businesses can get tailored information.

The Manufacturing Extension Partnership specializes in helping small and mid-sized U.S. manufacturers create and retain jobs, increase profits and become more efficient. The program, which is a branch of the U.S. Chamber of Commerce, has over 1,300 technical advisers in every state that help solve manufacturers’ challenges and identify areas for growth.

And if you are outsourcing overseas in 2012, here are some resources to help you manage potential obstacles:   

Three outsourcing challenges you may be facing

Tips and resources for managing your outsourcing relationships

2011 Manufacturing Outsourcing Survey by Arena

The Octopart Team: (from left) Jacob Ribnik, Andres Morey, Bryan Newbold, Sam Wurzel, Christopher Calvi, Harish Agarwal

Andres Morey and Samuel Wurzel are changing the way you shop for electronic parts.

Andres and Sam, who studied physics together at Brown, then pursued PhDs in astroparticle physics and plasma physics respectively, are the founders of Octopart—a Google-esq search engine for electronic parts.

Octopart makes it easy to compare the prices and availability of electronic components across a wide variety of distributors, all in one place. You can use Octopart to search for parts by name and number, or navigate through a taxonomy of structured items. For every part on the site, Octopart provides a variety of distributors for every part, as well as prices and links to buy. The site has been live since 2007, and gets over 700,000 unique visitors per month.

We recently partnered with Octopart to create the Autofill functionality for Arena PartsList—a new application that automates electronic component evaluation and documentation—so I took some time to talk with Andres and Sam about the past, present and future of Octopart, and what it takes to grow a successful company.

Alex: How did you come up with the idea for Octopart?

(Andres) We developed the concept for Octopart when we were both in grad school working on some hardware projects. Sam was working on a fusion reactor—

(Sam) Let me jump in here, it was an experiment related to nuclear fusion energy, I wasn’t building an actual reactor.

(Andres) Right.

(Sam) And while I was doing that, Andres was working on some really wild experiment where they were building a particle detector at the South Pole.

(Andres) So at that time, we were both working on hardware projects with very demanding tolerances. As we were going through the process, we discovered it was really hard to get the components we needed.

While I spent weeks looking for capacitors that could be embedded in the ice of the South Pole, Sam was tearing his hair out trying to find amplifiers with really high frequency requirements.

 (Sam) We found ourselves really struggling to find the parts we were looking for, and ended up spending a lot of our time pouring over catalogs. We were getting really frustrated, but then we realized that all of our coworkers were doing the same thing.

As it became clear that component shopping was a universal problem, we thought, “Maybe there is an opportunity to do something for all the people that have this problem.”

(Andres) From there, we started brainstorming all the different things we could do. We both loved coding, so the idea of a website made a lot of sense.

As soon as we had something ready we threw it up on the web and sent out an email to our friends for feedback. We applied for Y Combinator funding a few months later and launched formally a few months after that in March 2007.

Alex: How did two physics majors create a successful software startup? What’s your secret?

 (Sam) In some ways, startups are remarkably simple. It comes down to what Y Combinator says over and over—“Make something people want.”

(Andres) That’s right, there really is no secret to starting up a company. Step one—Make something people want, and Step two—Don’t run out of money before you achieve Step one.

(Sam)  If you do those two things, you’re going to be successful. It’s a simple formula, but for something so simple, it can be really hard to do. We’ve been working on Octopart seven days a week for over five years now, and there’s always more to do.

(Andres) We also had a lot of help from some really amazing people. A friend of mine from grad school, Harish, joined us the day we launched and there’s no way we could have grown the company without him. Most recently we convinced a couple of really smart people to join us. Bryan and Chris have already made a tremendous impact and I can’t imagine the company without them.

Alex: When launching a company off the ground, how important is experience?

(Sam)  I don’t think business experience is as important as you might think. We had physics backgrounds but we didn’t have any business or industry experience. We were able to pick up the business side of things as we went along. But without a physics background, picking up the technical aspects would have been much more difficult.

(Andres) I would even say that in some ways, our naivety helped us, because we were so optimistic. We had no idea how many challenges there would be, so we went into the whole thing very optimistically and with a lot of energy. I think this was helpful when we ran into those coding and business challenges, because we just worked through them.

Alex: What are some of the challenges you faced while trying to get Octopart off the ground?

(Sam) Jumping into an industry where we had no contacts and no experience was a challenge. Building relationships and learning the ins and outs of the electronic component industry took a long time.

(Andres) Things take longer than you anticipate. Like many people who love their idea, we thought that if we could get the data and site together, we would have the world at our doorstep right away. In reality, it took quite a lot of time to build relationships in the industry and develop our user base.

We faced a whole other set of challenges when it was time to scale—both on the software side and on the organizational side. On the product side, when you have a part database of 15 million, you’re constantly working to make sure it’s accessible and scalable. And on the organizational side, anytime you grow, there are more people and personalities that you have to bring together around the common goal, which can be tough.

(Sam) Over the last year or so, we’ve played around with a lot of ways to organize and manage responsibilities. Whether you’re talking about scaling a product or scaling a company, experimentation is a big part of it. You circle around to find out what’s not working, and keep iterating.

Alex: How do you see Octopart evolving? Where would you like to take the site from here?

(Sam) A year from now, we want to be a couple of different things. First off, we really want to improve the quality of the data on the site—a lot of that is dependent on developing business relationships to gather that information.

We also are really focused on increasing our industry penetration, and syncing Octopart up with as many manufacturers as possible. When it comes to securing all different kinds of part information, we really see partnerships as a great place to grow the business.

 (Andres) I would definitely say the future is growth. We’ve doubled the size of the company in the last 6 months, and are increasing our efforts to improve and increase the site’s information.

On one hand, that means working with our current partners to index their component info on the site, and add updated data sheets, etc, but like Sam said, we also want to increase the amount of manufacturers and distributors we work with to get critical part information.

Currently, we’re looking for really good developers, and people who are passionate about electronics. We need people to talk to and work with the manufacturers of electronic parts so we can increase the amount of content on the site.

Alex: What’s it like to work at Octopart?

(Sam) I think it’s great. We work really hard, but also have a great sense of camaraderie and teamwork, and we all really believe in the project.

(Andres) In general, I would say Octopart is a great place to work because we’re always trying to improve our product, and are extremely open to innovation.

All of us are really passionate about electronics and coding, and most of us were hardware hackers before working at Octopart. Lately we’ve been trying to make room for side projects to keep in touch with our hardware roots.

Octopart discusses the future of component shopping

In addition to learning more about Octopart’s mission to improve part shopping, I also picked Sam and Andres’ brains about the future of component shopping, PartsList, and the likelihood of a one-stop component shopping experience. Check back next week to learn why one-stop component shopping may just be a pipe dream.

For more information:

Octopart homepage

Cloud PLM gets personal

- Stephen Colbert

Over 40,000 people visit the emergency room each year for table saw related injuries, and almost 4,000 of those people end up losing at least one finger. That’s a table saw accident every 9 minutes. 10 table saw amputations every day.

Steve Gass, is looking to change this with his patented SawStop technology. The SawStop table saw automatically detects when a person’s finger has made contact with the blade, and can stop the spinning blade almost instantaneously. Sounds like a great idea, but table saw manufacturers believe the technology will drive up the price of table saws, making them too expensive for hobbyists and small businesses to purchase.

We’ve covered the SawStop controversy in previous articles, but now comedian and TV host Stephen Colbert has taken notice of the SawStop technology, as well as its mission to eliminate “our God-given right to cut off our fingers.”

Check out the SawStop segment here. (If you’re a regular viewer of The Colbert Report, you might not be surprised to learn that a bit of the video is NSFW.)

Despite how much of a “buzz-kill” these regulations to mandate SawStop technology might be (Colbert’s words, not mine), more and more builders today are growing attached to their SawStop table saws. Pete, an avid woodworker, puts it best: “I’ll give up my saw when you take it from my cold, 9 ½ fingers.” (He had 10 before the accident…)

So what do you think? Should the Consumer Product Safety Commission require table saw manufacturers to adopt a technology like SawStop?

For more information:

SawStop founder requests a mandate for tougher table saw safety regulations—how does this affect manufacturers?

The SawStop: Product design with a purpose [cool video!]

NPR: Advocates urge lawmakers to make table saws safer

Maybe this is the world you already live in.

A journey through the dark days of file sharing

In a world without PDX, document controllers dread the task of preparing a build package for delivery.  They waste entire days gathering data to include in a package—from the detailed BOM itself to other files, prints, specs, travelers and routers. Because the information can be complicated, and in various formats, most packages must include a guide explaining what has been sent.

In this world, when there’s a need to share BOM data (which most likely lives in a business system that isn’t designed to print well) it must be exported to Excel, so it never looks quite as good as it did in the original system interface. This means engineers and doc controllers must also take screen shots or use PDF printing to maintain the integrity of the BOM format, which takes additional time.

After the BOM has been moved to a sharable format, it’s time to locate the relevant file attachments and dump them into a central location. Someone will then need to sort through the pile of tens—maybe hundreds—of files in order to organize them in a way the supplier will understand. This gets more difficult when the supplier wants the files broken down by BOM indentation or sorted by part category or family, especially when each supplier or CM has their own format preferences.

In a world without PDX, OEMs spend a great deal of time in front of their printer, fax machine or email—where it takes just as long to set up the build package as it does to revise it and rework any corrections. And even after the package is complete, the fear that there is a mistake, just waiting to throw everything off, can linger for days.

But this doesn’t have to be reality.

How PDX can save the day

For people who are overwhelmed and hesitant to add another system to their life, PDX is a lifesaver.

Product data exchange (PDX) provides a way to share a clean, build package by allowing manufacturers to create a snapshot output of item, change, AML, AVL, attachment files and relational data from a business system. Several business systems are already configured with a PDX output option, so using PDX files to communicate product data saves precious time. No more manual removal and re-formatting of product information in a business system.

For engineers working tirelessly to create and perfect a product BOM, PDX files can help preserve the original context—saving a great deal of time, effort and confusion.

And for doc controllers putting together a build package, PDX reduces the chance for data error that happens when someone manually compiles information. After all, any time you automate a process, reducing the number of times you touch the data, you reduce chance for error.

Arena PDXViewer takes product data exchange to the next level

If you think a world without PDX sounds like a total nightmare, you’re not alone. This is why we’ve made a big effort to support and encourage the PDX file standard with the launch of Arena PDXViewer, which displays PDX build packages in an easy-to-read format.

Although simple to use, PDXViewer is robust. Besides viewing PDX files, you can break up build packages into smaller subsets of data to share with subcontractors, vendors or manufacturing partners. You can even export change orders with redlined PDX files. PDXViewer displays exactly what has been changed with its special Redlines view.

PDXViewer is part of our new focus on personal cloud PLM, which is all about expanding PLM to a larger audience, and giving engineers, manufacturers, designers and serial inventors the tools they need earlier in the process.

More articles you might enjoy:

Why my PDX Viewer in better than yours

Why you should be using the PDX file standard

Cloud PLM gets personal

Part one: setting up your internal organization for scaling success

Success often strikes when you least expect it, and when it does, will you be ready?

This blog series will help you determine whether your business is ready to handle the challenges of an increase in production volume—and help you be prepared to scale when the market demands.

Part I will focus on preparing your internal processes for scaling, and part II will address how to prepare your supply chain for growth.

Do you have a scalable master parts list and product BOM?

When you need to scale, time is of the essence. Because of this, using a centralized, revision-controlled system like Arena to manage your product records will give all relevant departments a common reference point for part information—and save you time and money. And when you’re in control of your BOM, you can push changes easier and increase production with fewer notifications and chances for miscommunications.

How risky are your product components?

Do you know which parts in your product BOM are most likely to be in short supply? And are you taking steps to reduce the risk of single source or rare components?

While it may not be realistic to find secondary sources and substitutions for every part in your product, you can be aware of which parts pose the greatest risk to scaling and proactively seek out solutions. If you’re working with parts that are expensive, have long lead times and/or single sources, you should monitor those parts carefully all the way from ordering through use. And if you find yourself in a pinch, keep in mind that you may be able to rework scrap to recover those tricky-to-find parts.

How much do you know about how your products are made?

If you haven’t run into production problems yet, it is for one of two reasons. Either your manufacturing processes are correctly set up and in place, or you’ve been lucky. A quick look at your assembly process, the documentation around it and your results off the line will indicate which is the case for your business.

If you know how you build today, you can better prepare for scaling tomorrow. The first thing to look at is whether your manufacturing and quality processes—and those of your suppliers—are well documented (more on scaling with a CM in Part II). Secondly, take a look at how you build, particularly, how well you build. Do you have a large scrap pile that could be repurposed, or eliminated altogether? This can save your business significant dollars.

Can you answer the ‘what if’ scenarios of scaling?

The last important question to consider as your prepare for scaling is whether your company can handle the impact. The best way to do this is to run through some ’what if’ scenarios.

What would you change if you had to triple production on your largest volume product? Would you increase the number of days a month that you build? Or add another shift or line? Or even take resources from another product? Or leave the entire decision up to your CM?

Be ready for your golden opportunity

Most likely, your business is more prepared to scale in some areas than in others. But no matter where you’re at right now, you can always bolster your current competitive edge by preparing for unexpected market opportunities.

While BOM and change management tools enable you track changes and share your product data (and are essential for companies who want to scale their business) for those who are just starting out, Arena offers two exciting new tools to make the process all the easier.

Arena PartsList is our new cloud application that helps you prototype faster by making it easy to document, organize and share BOMs. And Arena PDXViewer lets you quickly share PDX build packages with anyone who needs them.

Here’s the bottom line—using the right tools for the job, no matter where you are in your organization and product lifecycle, will help you scale successfully.

For more information:

5 steps to scaling your business when your competition stumbles

Manufacturing outsourcing: 7 common pitfalls to avoid

Lessons from Mobius Photonics: Three ways small businesses can get ahead

Your feedback on intelligent vs. non-intelligent part numbering schemes

One reader, who was part of a merger between two companies with different part numbering schemes, decided that an intelligent part numbering scheme helped to ease the transition.

I want to relate an instance where a company with a non-intelligent scheme acquired a company with an intelligent scheme. Luckily, the database system was capable of utilizing both [schemes], but training became the key to being able to adapt workers, buyers, accounting, sales, etc…

As people in the organization were trained and worked with both systems in their respective areas, they began to see more advantages of the intelligent system. The ability to search, identify, expand, and build upon the foundation of the intelligent system allowed it to be more efficient.

The truth is, you never know what may happen in business, so choosing a nimble part numbering scheme is always a good idea. Here is one reader’s take on why it is important to think long-term when choosing a scheme.

Over many years, part numbers can be duplicated for other parts thus corrupting long term databases (and confusing long term customers) so master product naming systems must be aware of older but still live parts and their naming.  Sounds simple. Mix in the M&A activity, and part lists that are out-of-context with supplier or industry, and things get very messy.

Your thoughts on the intelligent part numbering rabbit hole

Despite the benefits of an intelligent part numbering scheme, several readers shared their frustrations with the downsides of intelligent schemes.

I have run into numbering intelligence that ended up being wrong for the part, but it had already been shared. Correcting the number would have [unwanted] rippling effects.

One reader believes that intelligent schemes are obsolete in today’s automated world.

Most part numbering methods grew from the need to interject more information in a small area or field, giving the user the ability to file and locate parts quickly in a non-computer based world. Not so much of a problem today.

And another reader is convinced that intelligent schemes are doomed to fail.

We have too much experience with intelligent numbering systems to think they are a good approach to part numbering. Don’t put intelligence in the number; use other fields to capture parameters to reflect the information you deem necessary regarding the item. Otherwise you WILL go down that rabbit hole.

Are hybrid numbering schemes the best way to go?

Because no one scheme can address all the issues that arise when managing part numbers, hybrid schemes have emerged in attempt to offer the best of both worlds.

One reader shared how he would set up a hybrid scheme.

I think the answer lies in semi-intelligent numbering. Have high-level categories to indicate commodity, and some basic technical tenets. The rest should be included in the description. It is still good look at a part number starting with 53- and know it’s a cable.

And another reader points out that the right solution depends on the company in question.

It all comes down to the enterprise itself—it’s size, market, suppliers, work process, accounting, and all others who touch this important and sometimes neglected part of business.

There’s no clear winner in this numbering scheme debate

The part numbering debate is so complex because both schemes offer valid merits and shortcomings.

One reader who describes his himself as “the bridge between the architectural cloud thinkers and the hardened manufacturing techs in the trenches” looks at the intelligent vs. non-intelligent numbering scheme standstill like this:

I know what this [debate] looks like from both perspectives. They are both right. That’s what makes it such an interesting problem.

I think the key is providing an absolute minimalist structure – just enough to make the part identifiable and unique among all other parts you might encounter. The life story of the part is unnecessary, but you need some fundamental understanding of whatever it is you are holding in your hand…literally at a glance.

Ultimately, as one reader points out, you have to take a look at your organization and determine the best solution for you and your team.

In our complex world of global design, manufacturing, and business coupled with the sometimes constant change in business acquisitions and mergers, no one system will be the final answer.  It’s a question of optimizing the system for what is known, some of the unknowns, but mostly for the situation at hand.

Thank you to everyone who contributed to our conversation on part numbering schemes. And it’s not too late to weigh in—what experiences have you had with part numbering?

For more information:

Intelligent vs. non-intelligent part numbering—who’s winning the debate?

A trip down the intelligent part numbering rabbit hole

Three considerations when choosing the part numbering scheme that’s right for you

Significant part numbering tips

If you’re part of an organization that’s scaling to production, we’ve got you covered with our scalable cloud PLM solution.

But what if you’re just starting out? You need to capture and document parts, but without changes and a supply chain to manage, you may not be ready to implement a full-service solution. You may just need something that helps you design and document a prototype, or turn your parts into BOMs.

For people like you, we created PartsList.

Why PartsList?

In the last year, we noticed a lack of engineer-focused systems that individuals and small teams could use to document and share their designs. We hope to change all that with PartsList—a new cloud application that makes it easy to document, organize and share BOMs.

PartsList is a low cost tool for engineers who just need to find parts, document a BOM and get it to doc control (or a partner, vendor or friend). Since we launched in January, we’ve been getting an enthusiastic response, and a lot of early traction, which has been really exciting to see.

As the product manager of PartsList, I’d like to give you a tour of PartsList, so you can see how it can help you get your prototype built. At this point in time, we’re letting new users try PartsList for free, so if you think you might be interested, set up your account today.

What are some cool things you can do with PartsList?

When we created PartsList we had design engineers in mind.

The use case for PartsList begins with an engineer who needs to get his/her full circuit design from EDA or ECAD documented. (Or an engineer who needs to document a napkin drawing, reference BOM or a parts list in a spreadsheet.) From there, PartsList can be used to:

Complete the documentation process for an existing bill of materials

Export a BOM from ECAD, import it into PartsList and use Autofill to collect datasheets and vendor site information for your entire BOM in one click. For any given part, all you need is the manufacturer and manufacturer number to capture the rest of the information—including datasheets and links to purchase—with the click of a button.

When you’re done, export the BOM to CSV or PDX to share it with whoever needs it. (And if you’re unfamiliar with PDX, here is more information on how you can use PDX to share build packages.)

Consider multiple critical component contenders

PartsList comes with PartSaver—a bookmarklet that you can use to capture and save critical part information with one click. If you’re browsing parts online, you can use the PartSaver browser button to capture critical component information—including datasheets and vendor information, and make comparative evaluation easy.

Create a new Bill of Materials

If you want to start a BOM from scratch, you can find the parts individually online, and use PartSaver to capture all the data into a unique list.

It’s also easy to build out a napkin-drawing or sketched BOM with PartsList. Just load the basic information—part number and manufacturer—into PartsList, select Autofill and PartsList will pull the rest of the information you need to complete your BOM.

If you have a BOM in EDA or ECAD, or a reference design from a partner or manufacturer, you can import the old design to PartsList, remove the components that you want to replace, and use PartSaver to clip replacement parts.

Create a new part request form

PartsList gives you a full list with supplier item information, which can be passed to document control for creation of internal part numbers and inclusion of parts into another system—if you have access to PLM, or an ECAD library.

It’s never too early to be organized

If you’re an engineer at an early-stage startup, two guys in a garage building a prototype or even a serial inventor with a ton of ideas to document, a comprehensive cloud PLM solution might feel like a bit much. But if you want to be prepared when it’s time to scale, it’s never too early to adopt a simple, effective way to collect part data, as well as build and share simple BOMs. So I hope you give PartsList a try.

For more information:

Try Arena PartsList for free today

Your right-sized BOM management toolkit in the cloud

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

While a lot of the big picture questions (like, how much do we expect to make from this product, why are we launching something new in the first place, etc.) are VP or C-level questions, a successful new product introduction (NPI) is something everyone in the organization must help with.

Here are some things engineering, operations, sales and marketing should consider during the NPI process.

Has operations considered . . .

• How to kick off/manage the various production phases (prototype, pilot, production)
• The supply chain strategy—are you consigned, turnkey, hybrid or ”appliance” manufacturing?
• CM selection—will your CMs operate locally or offshore, and should you go with an ODM?
• Production strategy—will you build to order or build to forecast?
• Time that needs to be added for the quality assurance process
• Your production capacity requirements, plans for expansion
• The Finished Goods (FGI) warehouse/distribution plan
• Repair center process and costs
• Cost reduction

Have engineers taken some time to discuss . . .

• The NPI process (gates, deliverables, approvals)
• Product data management and engineering changes
• Part numbers—custom vs. standard, commonality, intelligent vs. non-intelligent
• Design Verification Testing (DVT)/QA
• Product Reliability testing (HALT)
• Test specs
• Available diagnostics
• Special test equipment
• Feedback loops

Have sales and marketing thought about . . .

• Sales channels—will you use a direct model, or work with distributors  or partners?
• Sales regions—there are different considerations if you’re selling domestically than there are if you’d like to expand your customer base to Europe, China, India or Brazil)
• Standard order ARO requirements
• Terms and conditions
• Stock Keeping Units (SKU’s)—how many do you need to have available?
• Sales forecast process
• Customer warranty—how will you manage returns and spares?
• Compliance (UL, FCC, RoHS, WEEE, FDA)
• Software delivery scheme (CD, web-site access)

And for every department, it’s important to make sure the right business systems are in place.

In particular, the following systems make it much easier to manage the new product introduction process:

• Product Lifecycle Management (PLM)—for design and manufacturing documents, BOM and change management and compliance
• Enterprise Resource Planning (ERP)—for purchasing, inventory, order administration and finance
• Customer Relationship Management (CRM)—for sales forecasting and customer orders, pipeline management, RMAs, return rates, customer case history and warranty entitlement

To learn more about new product introduction (NPI)

If you’re interested in learning more about new product introduction best practices, our partner Product Realization Group is hosting a seminar next week that you might enjoy. The event, “Launching Success,” is available as an in-person networking and lunch for $10 (early bird pricing) and as a free webinar. Sign up today!

Some other links you might enjoy

First-to-market innovation challenges: An Arena customer spotlight

Big picture questions to ask when launching a new product

Avoiding NPI pitfalls: Plan for the total customer experience

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