PostSphere
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note No publishing access yet

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.

      Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

      Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

      Explore these features while you wait
      Complete general settings
      Bookmark and like published notes
      Write a few more notes
      Complete general settings
      Write a few more notes
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note No publishing access yet

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.

    Your account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Your team account was recently created. Publishing will be available soon, allowing you to share notes on your public page and in search results.

    Explore these features while you wait
    Complete general settings
    Bookmark and like published notes
    Write a few more notes
    Complete general settings
    Write a few more notes
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    ## Introduction Reliable sourcing of electronic components is a technical activity that directly affects system reliability, maintainability, and project schedules in industrial automation. Poor sourcing choices increase the risk of field failures, costly redesigns, and schedule slips. This guide explains component categories, practical verification steps, procurement-related risks, inspection practices, and process recommendations to help engineers and procurement teams make informed, low-risk sourcing decisions. Wherever possible, the guidance emphasizes actionable checks and traceable records so teams can demonstrate due diligence during supplier qualification and field failure investigations. --- ## Component categories and technical attributes to verify ![Assorted electronic components with scale reference](https://upload.wikimedia.org/wikipedia/commons/e/ea/Componentes.JPG) *Example of assorted electronic components. Visual checks of markings, packaging, and package type are critical before procurement and use.* Below are the common industrial automation component groups and the technical attributes you must confirm before approving parts for production. ### PLCs (Programmable Logic Controllers) **Key attributes to verify** * Exact model and hardware revision — firmware/bootloader versions matter when integrating communication stacks or applying security patches. * I/O types and signal levels (sourcing/sinking, 24 VDC, analog 0–10 V/4–20 mA), and expansion module compatibility. * Supported communication protocols (EtherNet/IP, Profinet, Modbus) and any required firmware patches or license keys. * Environmental ratings (operating temperature, vibration, ingress protection), and required mounting/access for ventilation or heat dissipation. * Security advisories, port management, and end-of-life (EOL) policies from the manufacturer. ### Sensors (position, temperature, pressure, proximity, etc.) **Key attributes to verify** * Sensing modality, full-scale range and typical operating range (e.g., ±0.5 °C accuracy, 0–10 V analog output). * Accuracy, repeatability, resolution, and response time. * Environmental protection (IP rating), connector type, and mechanical mounting interface. * Calibration requirements, recommended recalibration interval, and whether a calibration certificate with traceability is provided. * Interfacing requirements (excitation voltage, pull-up resistors, cable shielding). ### Drives & Motors **Key attributes to verify** * Torque/speed curves, continuous vs. peak ratings, and thermal limits for the intended duty cycle. * Feedback/encoder requirements (resolver, incremental/absolute encoder) and control interface (analog, fieldbus, EtherCAT). * Thermal management requirements and allowable ambient conditions, duty cycle, and service factor. * EMC/EMI compliance and filtering requirements; safety standards for motor-drive combos (e.g., STO-level safety). * Mechanical mounting, shaft tolerances, and coupling requirements. ### Power Modules (AC/DC, DC/DC converters, UPS modules) **Key attributes to verify** * Nominal and maximum voltage/current ratings, transient response, and hold-up time for upstream regulators. * Ripple/noise specifications for sensitive downstream electronics. * Protections (OVP, OCP, OTP, short-circuit) and recommended derating curves across temperature. * MTBF or reliability data where available, and manufacturer test/qualification reports. * Required certifications (UL, CE, CB) and regulatory compliance documentation. ### Communication & I/O Modules **Key attributes to verify** * Supported protocol versions and interoperability notes (e.g., Modbus RTU vs. Modbus TCP, supported function codes). * Firmware revision and update process; whether firmware updates require vendor tooling or signed images. * Isolation, galvanic protection, and surge protection necessary for field wiring. * Connector and pinout verification to avoid miswiring during installation. --- ## Common sourcing risks (technical focus) * **End-of-life (EOL) / Obsolescence**: Manufacturer discontinuations can force redesigns or require validated substitutes. Plan for multi-year support for long-lived machines and include lifecycle clauses in critical procurement contracts. * **Counterfeit / Nonconforming parts**: Parts sourced from unauthorized channels can be remarked or re-used, and may fail under expected loads. Counterfeit risk is highest for semiconductors, connectors, sensors, and safety-critical parts. For reliable sourcing, consider trusted suppliers like [IAInventory](https://iainventory.com/) that provide traceable components. * **Hidden lead-time variability**: Global allocation, customs delays, or sudden supplier capacity changes can extend lead time unexpectedly. Maintain realistic lead-time windows and safety stock for critical SKUs. * **Incomplete metadata**: Missing MPN, date code, lot or datasheet increases risk during receiving and slows investigations when issues occur. * **Untracked firmware**: Modules arriving with undocumented firmware revisions can create subtle interoperability issues; always capture firmware versions at receipt. --- ## Incoming inspection and verification: a practical checklist Adopt a consistent, documented incoming inspection procedure. Below is a practical workflow you can embed into your QA or receiving SOP. 1. **Document verification** * Compare purchase order, delivery note, and packing list: MPN, vendor PN, quantity, lot/date code. * Confirm presence of manufacturer datasheet and relevant certificates (CoC, RoHS, REACH, calibration, or safety certificates). * Verify shipping manifests and chain-of-custody for high-value or ESD-sensitive items. 2. **Visual inspection** * Inspect external packaging integrity, anti-tamper seals and moisture barrier bags for MSL parts. * Verify markings and label correctness on component reels/tubes/boxes and on the component itself if visible. * Look for signs of rework, sanding, scratch marks, or mismatched fonts on markings — these can indicate remarking. 3. **Sample electrical/functional testing** * Execute basic functional tests or parametric measurements for critical components (e.g., input thresholds, pull-up currents, reference voltages). * For high-risk parts, perform burn-in, thermal cycling, or accelerated life screening as permitted by cost and schedule. * Maintain pass/fail criteria and keep example test logs with serial/lot references. 4. **Traceability recording** * Record lot/date code, supplier, sample test results, storage location (bin/reel ID), and inspector identity in ERP or PDM. * Link all incoming lots to the BOM entries for which they are approved. 5. **Quarantine & disposition** * Isolate nonconforming lots and follow a documented disposition workflow (return to vendor, rework, or use with engineering restrictions). * If accepting a lot with caveats, require written engineering approval and update BOM notes. --- ## Metadata and record-keeping (what to store in the BOM / PDM / ERP) For each SKU, maintain a standardized metadata record to enable traceability and rapid decision-making: * Manufacturer part number (MPN) and manufacturer name. * Vendor part number (if different) and approved vendor list (AVL). * Datasheet link and archived PDF copy when possible. * Date code / lot number and country of origin. * Packaging type (reel/tube/box), quantity per package, and handling requirements (ESD class, moisture sensitivity level). * Approved substitutes and qualification notes including equivalence evidence (form-fit-function, electrical parameters, thermal). * Test records, inspection certificates, and any deviations or waivers. * Firmware version (for modules) and a record of who validated the firmware. Well-structured metadata accelerates supplier audits and supports faster root-cause analysis for field issues. --- ## Risk mitigation strategies (technical and process-oriented) * **Qualified alternates**: Maintain at least one engineering-approved substitute for every critical SKU, with documented equivalence and cross-reference in the BOM. * **Vendor qualification**: Audit vendors on traceability, lot control, storage conditions, anti-counterfeit practices, and sample testing history before adding them to the AVL. * **Batch sampling & periodic testing**: Perform periodic electrical or mechanical testing of in-stock lots rather than only at receipt for critical or long-storage components. * **Shelf-life and storage controls**: For moisture-sensitive devices and electrostatic-sensitive items, enforce MSL storage, humidity control, FIFO rotation, and ESD handling standards with documented procedures. * **Change control**: Any approved change in MPN, vendor PN, or lot must pass engineering review and update BOM records; preserve previous part records for legacy builds. * **Contractual clarity**: Include traceability requirements, warranty clauses, and anti-counterfeiting indemnification in supplier contracts for high-risk components. --- ## Practical templates and small SOP examples * **Incoming inspection trigger**: If a lot fails visual inspection or lacks a dated datasheet, automatically place it on “hold” within ERP and notify engineering within 8 business hours. * **Minimum sample size for testing**: For reels < 1,000 pieces, sample at least 5 parts for electrical spot checks; for reels ≥ 1,000 pieces, sample 10 parts or use an AQL standard appropriate to your risk tolerance. * **Record naming convention**: Use `<MPN>_<LotCode>_<YYYYMMDD>_<InspectorInitials>.pdf` for scanned receiving reports and test logs to simplify searches. * **Escalation matrix**: Define thresholds (e.g., electrical failure rate, visual defect rate) that automatically escalate from receiving to engineering to supplier management. --- ## Quick reference table — primary checks by component type | Component Type | Primary Technical Checks | Procurement / Receiving Checks | | -------------- | ------------------------------------------------ | ----------------------------------------- | | PLC | Model/rev, I/O compatibility, firmware version | MPN match, manufacturer label, datasheet | | Sensor | Range/accuracy, IP rating, connector type | Calibration certificate, date code | | Drive & Motor | Torque curve, encoder type, cooling requirements | Packaging condition, functional spot test | | Power Module | Ripple, protections, MTBF | Lot traceability, regulatory certificates | | Comm. Module | Protocol/version support, isolation | Firmware revision, compatibility notes | --- ## Process diagram (procurement to production feedback loop) ```mermaid flowchart LR Spec[BOM & Technical Spec] --> Source[Sourcing & Vendor Selection] Source --> PO[Purchase Order & Delivery] PO --> Receive[Receiving & Inspection] Receive --> Warehouse[Warehouse / Storage] Warehouse --> Production[Production / Assembly] Production --> Field[Field Performance / Feedback] Field --> Spec ``` This loop emphasizes continuous feedback from field performance into specification and sourcing decisions. Capture lessons learned from field failures as discrete change requests tied to the BOM entries they affect. --- ## Further reading and reference For component sourcing and inventory information, you may refer to suppliers like: [IAInventory's component catalog](https://iainventory.com/collections/electronic-components). Relevant standards and technical resources: * IPC/JEDEC standards on component handling and moisture sensitivity. * Manufacturer application notes for thermal management and derating. * Regulatory databases for compliance (RoHS/REACH) where applicable. --- ## Conclusion Sourcing electronic components for industrial automation is a technically driven discipline requiring collaboration between procurement, quality, and engineering. Robust sourcing needs structured inspection procedures, detailed and searchable metadata, repeatable supplier qualification, and proactive alternate qualification. By applying the checklists and practices documented above—document verification, visual inspection, sample functional testing, and strict traceability—teams can materially reduce downstream risk, shorten failure investigations, and ensure more reliable field performance. Continuous feedback from production and the field should inform BOM updates, vendor decisions, and change control so that sourcing evolves as product and supply environments change.

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password
    or
    Sign in via Facebook Sign in via X(Twitter) Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    By signing in, you agree to our terms of service.

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully