In my ideal world this is the sort of thing the purchasing guys would notice.
"Hey Mr. Engineer -- is there something special about this cap that makes it
worth 10x this seemingly superior one over here?"
With lead times going out into forever, we're just lucky they've not had any
purchasing disasters this year. OTOH, we have inventory of some components
that go out three years, or more.
Although in my ideal world the engineers at some point went over the BOM to do
a little sanity checking on prices as well, and would also notice it. Before
hiring you, I mean, since I imagine it's a product that existed before you
were hired.![]()
Actually it did. ;-) It's used in the football version of the unit you
played with and came out a year before. The good news is that there is only
one per board, the build numbers are in the low tens per year, and the product
has *reallY* fat margins (5-10x that of what you saw).
The real problem is that engineering never saw prices after the original
look-see in DigiKey during design. I asked our admin to dump the purchasing
database by part number and I'm going through the BOM manually (actually, I
placing the cost info into the schematic properties pages). I'm trying to get
the IT folks to feed back the purchasing database into our engineering
database at least monthly, but so far no one is very interested.
If one's not going to use 'K', 'RLY' is a lot better than RL or REL.
I suspect the kids have never used them so make things up as they go. No
reason to use any such abortions. Relays get 'K', period. ...might just as
well use that commie 49R9 and 3K9 crap. ;-)
Abbreviations are kinda strange, though. We occasionally refer to spectrum
analyzers as "SpecAns" for short, but I have a radio that refers to them as
"SpeAnas." Weird...
That's the problem with such abbreviations. Everyone does it differently.
As far as the "SpecAns" goes, how about "FreqDomScope", or better, "that gizmo
over there"?