Developing manufacturing BOMs with BOMControl

8 June 2012: We all know that the engineering (design) BOM is not usable for manufacturing. It’s not robust enough for manufacturing. It contains much of what manufacturing needs, but not enough. Here are some things needed for manufacturing to have a usable BOM:

  • Non-design elements such as paint, labels,
  • Manufacturing instruction
  • Manufacturing assemblies
  • Test and quality procedures
  • Detailed information on purchased parts
  • Variants for different zones of manufacturing
  • And so on . . .

If this is the case, then one might ask how does one use a design BOM to build an MBOM? Several alternatives come to mind. Rather than giving a dissertation on the subject, I spoke with Steve Chalgren, VP of Product Management & Strategy of Arena Solutions. The company, one of the earliest cloud based providers, provides only a cloud based solution. In fact, the company was at one time called BOM.com.

Founded in the late 90’s, the company has grown to about 100 employees, with 500+ customers, and 15K to 20K users in 40+ countries. More than half of their customers are in the high tech electronics business.

I had a chance to meet with the former founder soon after they were founded, but have not kept up with the company since then. A recent press release revealing that their net new subscriptions grew by over 25% in the first quarter piqued my interest. The company stated that the “increase in new business can be attributed to Arena’s 2011 investments in new products, like PDXViewer and PartsList, and integrations to cloud enterprise resource planning (ERP) solutions like SAP Business ByDesign and Netsuite, and component aggregators like Octopart.” My interest centers on possible use in the mechanical realm.

Their products include the following three cloud based products:

  • BOMControl: A collaborative and centralized way to manage BOMs and changes
  • PDXViewer: Share build and quote packages up and down your supply chain
  • PartsList: A lightweight app that helps capture, document, and share designs

BOMControl seems to offer much of the capability that mechanical design users need, including BOM management, import from CAD systems for creating the MBOM, and change management of the created BOM’s. Typical users might include the engineering team, document control managers, operations and manufacturing planning, supply chain management, and suppliers. The software makes it easy to add and track items needed for manufacturing. The fact that it is isolated from engineering CAD systems and from internal PDM or PLM system seems to allow secure access into just those areas that suppliers need without concerns about intellectual property (IP). Allowing suppliers direct access to internal PLM systems always makes me nervous.

The software seems to make sense for those companies that do not yet have or will not soon have a fully integrated PLM system for BOM management. And few do today. My guess is that many companies today use spreadsheets (like Excel) to manage their BOM’s, since most CAD PDM systems have little or no capability for multiple BOM views of the product, instead, focusing entirely on the engineering BOM, the EBOM. While spreadsheets will work for this application, they do not have the capabilities to easily collaborate, track changes, or smoothly interact with EBOMs to automate data exchange.

In the case of electronics manufacturing, an electronic search engine called Octopart automatically searches for the data associated with specified purchased parts and adds it to the MBOM. Capabilities exist for also adding these hooks manually and to include virtually any type of part descriptive files. Thus the Arean Solutions MBOM can become the residence not only of part data, but many other types of data associated with manufacturing. Consider test descriptions, supplier acceptance requirements, engineering test specifications and calculations as just a bit of what is possible.

Shown below are two screen shots of BOMControl managing these exact processes.

Showing the ability to track changes

Allowing various views into the BOM

Plans and pricing

Arena Solutions offers a BOMControl basic plan for $49 per month for up to 3 seats. They also have a 30-day free trial. For more information see their website at http://www.arenasolutions.com/products/bomcontrol/plans/. This trial pricing program is competitive with Autodesk 360 PLM and considerably cheaper than PLM vendors.

Recommendation

Arena Solutions’ products are aimed at taking the design EBOM and allowing a secure system for developing, maintaining, and collaborating MBOMs. All of which are needed to build and even service the eventual delivered product. All user companies without a current or short-term plan should definitely consider BOMControl.

One might think that BOMControl is used only by smaller companies, yet this is not the case. A large proportion of Arena Solutions clients are large companies.

I received no compensation for this review.

For more information

http://www.arenasolutions.com

http://octopart.com/

—-

My Twitter feed at PlanetPTC Live 2012 expanded with additional comments

7 Jun 2012

Introduction

I attended PlanetPTC Live 2012 as a media and analyst guest of PTC earlier this week. I was free to mingle with any user in attendance, and attend the general sessions, as were the other 75 or so media representatives. PTC also organized special sessions for the media. These sessions generally were more concise and allowed more direct interaction with PTC executives, other management and selected presenters. [Disclosure: PTC paid for my airfare and hotel accommodations.]

I tweeted during the events I attended, not prolifically as do some other tweeters, instead choosing to focus on what I found to be interesting and the highlights of some sessions. I have taken most these tweets and expanded on them below for my blog readers. In a blog to be posted soon, I might add additional comments.

In general, the conference was upbeat and well organized. With Creo and Windchill almost evenly divided in terms of revenue, the two lines of business account for some 80% of PTC revenue. The other three (ALM, SCM, and SLM) make up the balance, but represent substantial future growth areas for PTC. All three are collaborative businesses based on Windchill. SLM being the newest. With the PTC business now focused on lines of business, each with its own P&L, customers are better represented.

Tweets expanded (tweets are identified by the • symbol, followed by an expanded explanation)

  • In the exec wrap up on Tuesday, Brian Shepherd confirmed plans for an entry level Windchill. Pre-configured for smaller users.

More: While I had not heard of such an activity, some media were and asked the status of the project. As best I can recollect, this may come out in 2013. Probably one reason why Windchill ProductPoint was decommissioned last year. Remember this product, which relied on Microsoft SharePoint?

  • PTC realigns organization structure by lines of business, each with P&L responsibility. CAD, PLM, ALM, SCM, and SLM.
  • SLM is service lifecycle management. According to EVP Barry Cohen, an underserved market.
  • Mike Campbell now heading up MCAD segment. Brian Shepherd and Bill Berutti head up other 4. Development reports to EVP Rob Gremley.

More: Here are the relevant descriptions from the latest PTC company info flyer:

Rob Gremley EVP, Product Development & Corporate Marketing
Brian Shepherd EVP, PLM & SCM Segments
Bill Berutti EVP, ALM & SLM Segments
Mike Campbell Division General Manager, MCAD Segment

  • Problems reconciling EBOMs and MBOMs? Now there’s another – SBOMs. Service BOMs add parts kitting.

More: Users have struggled with developing and managing manufacturing BOMs for decades. Add a new one for managing the services practices – the Service BOM, which describes the product from a service point of view. These often contain groups of parts that may be replaced as one unit in the field.

It looks like Windchill MPMLink today manages this process for MBOMs and EBOMs in those companies that use Windchill and Creo. With PTC constructing a Service Lifecycle Management business unit, I am not sure where or how the SBOM relates to the other BOMs and how it is managed. I am sure PTC has thought this out and can provide an answer.

  • Campbell highlights Creo Layout and Freestyle as providing impetus for move to Creo.

More: These two Creo apps are new for Creo 2. Both are targeted towards giving users more easy to use modeling methods, fully integrated with Creo Parametrics. In the case of these two apps, both also play in the concept design space. PTC stressed the connection into Creo, rather that having a stand-alone concept design system, a dig I am sure meant to rattle the cage of companies using Alias (from Autodesk), today’s most widely application for industrial and concept design.

  •  PTC positions Creo 2 as opening the floodgates for Wildfire transitions. No cost to users. UI and functions better.

More: Brian Shepherd said this on the first day in the main tent session. For those of you not aware of what the term main tent is, it relates back to my days at IBM, where they called the main tent was where all the attendees were gathered together, as opposed to the breakout sessions. I guess back in the early days IBM held these sessions under tents – companies were smaller then.

  •  With release of Creo 2, PTC encouraging third parties to develop [apps]. None available from third parties yet. Opportunity to fully integrate.

More: In a follow up conversation with Brian Thompson, VP of Product Management for Creo, he stated that the requisite API’s are not fully available yet. They will be by Creo 3 and Creo 4. Creo 4, I asked! Yes, he said by Creo 4, or two years from now. Third party developers might want to clarify this directly with PTC.

  • Option modeling another approach to developing ETO configurations. Another approach to developing requirements based models?
  •  Option modeling marries Creo 2 and Windchill 10.1. Can add PLM config options based on geometric positioning.

More: Option modeling allows a concise description of a product with many variants. In some systems users plug all the variants into a parametric model containing all of the variant options. This often results in a very large model with an obscure definition of when each variant is used. Creo 2 and Windchill aim to solve this by combining the geometric properties of Creo with the data management properties of Windchill. For example, in a bicycle, all wheels are attached to hubs. Thus one need only keep track of the different wheels, along with any geometric modifications to the geometric model for the various wheels. Filters and equations are used for the definitions. I think, because I only saw a five minute video example.

  • Attending Cummins case study of integrating mfg and product intros. Closing the loop between the two.

More: Dr. Michael Grieves, author of several books on PLM, along with Apriso, revealed a startling efficiency claim for Cummins, which integrated its PLM, ERP, and MES systems. See if you can get a copy of his slides for an explanation.

  • Main tent sessions focused on Creo 2.0 and hints of what’s to come. Main business line highlighted. Campbell: great job on CAD.

More: On the first day PTC revealed what’s new with upcoming products and it vision for the future, near term.

  • Chief customer officer – Mark Hodges. Never heard of that title.

More: From Wikipedia I found out that a chief customer officer (CCO) is defined as “an executive who provides the comprehensive and authoritative view of the customer and creates corporate and customer strategy at the highest levels of the company to maximize customer acquisition, retention, and profitability.” The CCO typically reports to the chief executive officer, and is potentially a member of the board of directors.

  • High of 97 degs expected today at PlanetPTC in Orlando. Hot AND humid. Good to be inside with A/C all day.

More: Guess someone got a good discount for holding it here this time of the year.

—————–