Working for a major SDO, part of my job is helping others to make a query for parts in a design as efficient as possible. That is, I often hear "I'd like to be able to query against a lot of part attributes and get a table of part numbers that satisfy my constraints." Then the request I get is to do additional queries to further narrow the list. I've heard this from a handful of design engineers, and I'm curious as to how representative this is. Is this truly an issue when creating a design? Is a lot of time wasted looking for parts specs? From what I understand, the desire to look for parts listed in a spec is due to the belief that a part associated with a spec will cost less than one created without one.
Red Flag Submitted
Thank you for helping keep Eng-Tips Forums free from inappropriate posts. The Eng-Tips staff will check this out and take appropriate action.
Reply To This Thread
Posting in the Eng-Tips forums is a member-only feature.
In the components business price can often be the determining factor as to what product the manufacturer uses. For a great many mass-market products and applications, the low-cost off-the-shelf, one-piece stamped receptacle fits the bill. The price is right, the performance is adequate. Download Now
In today’s cost-sensitive world, designers are often driven to specify the lowest cost solution for every aspect of their designs to ensure that their solution is competitively priced and their company remains profitable. However, specifying a low-cost, low-quality connector solution can result in premature failure, considerable re-work costs and damage to reputations.
Increasingly, product and services companies are seeking more information and control in the
operational lifecycle of their products, including service and use. Better information about the operational lifecycle, and the ability to use that information, requires more than just unstructured data flowing back from products in the field.