New Part Number Request forms

[HybridGuy]

I am looking to implement some structure here as to how requests for new part numbers (internal p/ns) are handled. I am looking at a form or forms to gather parametric and application information (i.e. voltage,Pd,Rdson,etc.)from the Design Engineers to better help them find the right part for the design and/or verify that one does not already exist in the system. I am just wondering if anyone has such forms that they would be willing to share. I hate to re-invent the wheel if I don't have too.

 

[schlebda]

Start by gathering data on your existing parts, include costs; then prepare a database of parts. Better engineers tend to look through existing parts provided it is not cumbersome to do so, lazy engineers don't bother to look.

 

[designchain]

Depending on what your current situation is (including things like component system of record - e.g. Agile and the like, number of existing parts, supplier preferences, internal or outsourced mfg, organizational structure) a new part request / new part number assignment process can get pretty complex. Just collecting and entering parametrics accurately is tough enough (especially if you expect your design engineer to enter them...and to do so accurately and diligently) and requires a pretty well thought out classification scheme if you want to collect the right parameters.

If you have thousands of existing parts you may want to have an outside service provider cleanse (validate that the manufacturer's part number is correct) and "enrich" (add related information like parametrics and a current datasheet) your parts rather than doing it yourself. That typically costs between $0.50 and $15 per part, depending on where it's done and how much research is required to find the part and extract information on it.

We've devised quite a few NPR processes for a variety of companies; they can be extremely simple based just on collecting some specific information like manufacturer, part number, project name, etc. in an email and firing it off to a component engineer, to amazingly complex and based on sophisticated business process management software, depending on the needs of the company. Most companies don't need "amazingly complex" but "an email" is generally insufficient to ensure control.

Mike

--
Mike Kirschner
Design Chain Associates, LLC

http://www.designchainassociates.com

 

[HybridGuy]

We already have a pretty good part numbering system that breaks things down by part types, packaging, qualification etc. We currently have around 7000 part numbers, not huge as my last company had 70,000. But as schlebda noted, Design Engineers don't often bother to look at the existing parts. We have an electronic part request but it doesn't give the CE the information required. I want to create a better part request form and that is what I was looking for. I can start from scratch but I just thought someone might have someting thy would like to share.

designchain -
As we move to a new ERP system, a database scrub is definitely in order and I have considered using an outside service.

 

[designchain]

So is the problem with your design engineers or your component engineers? How is making the DEs enter parametric data going to help improve reuse of existing parts? This sounds on the surface like a "set the bar higher" approach...make getting a new part more painful so maybe they'll look at existing parts in the hope that they won't have to suffer through the new part request process...not the best approach. Why should the onus be on DEs to enter that data anyway? Usually CEs do that - and prefer to - since they're more detail-oriented when it comes to part information because they own it and have to maintain it. What information do the CEs need that they can't get from the DEs and why can't they get it?

The part numbering system isn't going to drive reuse unless you use extremely intelligent numbers that embed _all_ key parametrics (and there are a bunch of risks and problems with that discussed in another forum and other places), and a new form that does nothing but collect more data from the DE won't drive reuse either. This is more of a business process issue than a simple data collection exercise or technical problem. Providing the right tools with the right level of searchability (via consistent descriptions or, preferably, parametrics and an engine that allows searching on numerical values and not just text values) and business processes with the right incentives will drive reuse.

Mike

--
Mike Kirschner
Design Chain Associates, LLC

http://www.designchainassociates.com

 

[ComponentEngineer]

Hi, if i understand it correct. You are asking the design engineer to pass the parametric info to CE and inturn he will search the part. Whereas, generally DE has the upper hand to chose whatever component he feels suitable for his applciation and then goes to CE for approval.
coming to your query - New part request can be performed in many ways. One is simple Email notification/approval system, in which you will have list of questions to be filled by respective group and the same goes to multiple people. Otherwise, implement a smart webtool to do the same.
Whatever the tool it be, attaching datasheet or specifying the complete Mfg Part number should be there..

To have a better NPR, you should first have a component database of existing components arranged in proper fashion (based on component types etc)and its DE duty to verify the repective component type, before he requests a new part.