• Domestic sources

    From Don Y@21:1/5 to All on Thu Nov 7 17:09:02 2024
    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?)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From john larkin@21:1/5 to All on Thu Nov 7 16:46:11 2024
    On Thu, 7 Nov 2024 17:09:02 -0700, Don Y <blockedofcourse@foo.invalid>
    wrote:

    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?)

    There are companies that do such an analysis as a service, including
    second sources and part end-of-life estimates. I can't recall a name
    just now.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Klaus Vestergaard Kragelund@21:1/5 to john larkin on Sat Nov 9 00:18:23 2024
    On 08-11-2024 01:46, john larkin wrote:
    On Thu, 7 Nov 2024 17:09:02 -0700, Don Y <blockedofcourse@foo.invalid>
    wrote:

    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?)

    There are companies that do such an analysis as a service, including
    second sources and part end-of-life estimates. I can't recall a name
    just now.


    Silicon Expert seems to be more or less industry standard.

    https://www.siliconexpert.com/

    It integrates with major tools. You pay for the number of unique lines
    in the BoM, so it can "pay" to remove the typicals, that you are sure
    never will be a problem (surface mount resistors, caps etc)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)