Domestic sources

Liste des GroupesRevenir à se design 
Sujet : Domestic sources
De : blockedofcourse (at) *nospam* foo.invalid (Don Y)
Groupes : sci.electronics.design
Date : 08. Nov 2024, 01:09:02
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vgjkr6$2sarr$2@dont-email.me>
User-Agent : Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2
An old client dropped me a line (I have no idea how he managed
to find valid contact information!  I will have to look into that...)
He was concerned over the possibility of "import duties" levied
on the components in one of the devices Id designed for him.
To be honest, I've never looked at WHERE a component was sourced
as part of the selection process.  <frown>
My advice to him was essentially that of how one would handle
an obsolete component:
- redesign the hardware with necessary substitutions
- port the software to accommodate any necessary changes
- update production documents
Porting the software is, by far, the easiest and shortest effort (as
it was designed and written with this as a goal).
Updating production documents/procedures should be a no-brainer.
And, the hardware redesign should be easy -- EXCEPT for the
added task of identifying component sources (country of origin).
I figure 3 man months for the whole exercise -- assuming domestic
sources are available for all components.  So, it should be
relatively easy to put a price tag on that effort -- even if
taken in anticipation of a future problem.
Are folks undertaking such analysis?  Or, waiting to see what
ACTUALLY happens?  (Politicians are renowned for making all sorts
of claims and not following through -- has anyone seen that check
from Mexico for the wall?)

Date Sujet#  Auteur
8 Nov 24 * Domestic sources3Don Y
8 Nov 24 `* Re: Domestic sources2john larkin
9 Nov 24  `- Re: Domestic sources1Klaus Vestergaard Kragelund

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal