Sourcing Components for Industrial Automation Products That Must Last

A remote-I/O module or a machine controller is expected to sit in a panel beside contactors and drives, run around the clock and still be repairable a decade or two later. That expectation changes how its parts should be bought. A part that is fine in a consumer gadget can cause intermittent resets near a VFD, a communication stack can lose vendor support halfway through the product's life, and a cheap relay can wear out before the warranty does. What you are really sourcing is a combination of hardware, firmware, protocol behaviour and long-term support.

Put the plant conditions into numbers

"Industrial grade" on a quotation means whatever the seller wants it to mean. Replace it with measurable conditions before the RFQ goes out:

• supply voltage, tolerance, transients, reverse polarity and brown-out behaviour;
• ambient and in-panel temperature, humidity and condensation;
• vibration, shock, dust, oil mist and chemicals;
• analogue accuracy, sample rate and loop timing;
• field-wiring length, earthing scheme and where the isolation boundaries sit;
• the networks, device profiles and controller families it must work with;
• the safe state after loss of power, a sensor, an actuator or the network;
• how many years you will build it, and how many years you will support it after that.

The scope of IEC 61131-2, the equipment standard for programmable controllers, shows how wide this gets. The 2017 edition covers functional and EMC requirements and their verification tests for PLCs, PACs and their peripherals. That edition removed the safety requirements and points instead to IEC 61010-2-201, so a supplier quoting "IEC 61131-2 compliant" is no longer making a safety claim. Ask which standards the safety evidence actually rests on.

Tier the BOM by the cost of a change

Not every line deserves the same scrutiny. Grade each one by what happens if it has to change.

For critical and high lines, record the exact manufacturer part number, lifecycle status, approved channel, the engineering reason it was chosen, qualification evidence, and who receives change notices. A tier is product-specific: a resistor that is "low" in an LED circuit can be "high" in a 4 to 20 mA input.

Buy the boundaries carefully

Most field failures in automation products start at the edges: the power input, the field I/O and the network port. Power inputs see surges, bursts and wiring mistakes. Inputs see ground-potential differences and common-mode transients. Relay contacts and terminals collect dust and get over-tightened.

Look at the whole protection chain as one design: fuse or eFuse, reverse-polarity element, surge suppressor, filter, isolation barrier, DC/DC converter and regulator. Check derating at the hottest point inside the enclosure, not at 25 °C. For isolators, compare working voltage, transient rating, creepage and clearance and insulation lifetime; a single high test-voltage figure says little on its own.

Analogue channels deserve an error budget: sensor tolerance, protection leakage, resistor ratio, reference drift, converter error, noise and temperature. A 24-bit ADC cannot recover accuracy lost in a 1% resistor.

IEC 61000-6-2:2016 is the generic immunity standard for industrial environments. Your product family standard may set different levels, but asking a supplier for immunity results against it, on the board or module you are buying, is a reasonable first filter.

Network conformance is a purchasing document

"Supports industrial Ethernet" is not a specification. Write down the protocol, the device role, conformance class, device profile, cycle time, redundancy behaviour and the engineering-file version, then ask for evidence that matches the hardware revision and firmware you will receive.

The protocol organisations make this checkable. ODVA says each product incorporating its technology must pass vendor-independent conformance testing, after which it issues a Declaration of Conformity that is posted on its website. PROFIBUS & PROFINET International states that certification testing is mandatory for PROFINET and PROFIsafe products and is carried out by PI Test Laboratories. A certificate for a communication module is still not proof that your finished device interoperates with a customer's PLC, switches and configuration tools under load, so run that test as well.

Ask suppliers how they handle stack updates, security fixes, engineering-file changes and the retesting that follows. A module that stops being configurable when a vendor's tool or licence lapses is a lifecycle risk you are buying.

Functional safety stays with the system

If the product takes part in an emergency stop, guard monitoring or safe motion, the functional-safety engineers should approve the architecture before parts are frozen. A component's safety manual and failure-rate data help the analysis but do not certify the safety function. Purchasing's role is to keep the exact part and revision the analysis assumed, to hold the safety manuals and diagnostic data on file, and to block uncontrolled alternates in diagnostic paths, clocks, memory, output drivers and power supervision.

Security support is a supplier capability

NIST SP 800-82 Rev. 3, the Guide to Operational Technology (OT) Security published in September 2023, frames OT security around the performance, reliability and safety needs of control systems. In sourcing terms: security cannot be bolted on after the processor and modem are chosen.

For processors, modules and gateways, check secure boot, signed updates, protected key storage, role-based access, the ability to disable unused interfaces, event logging, a vulnerability reporting channel and recovery from a failed update. IEC 62443-4-2 groups component requirements under seven foundational requirements: identification and authentication control, use control, system integrity, data confidentiality, restricted data flow, timely response to events and resource availability. IEC 62443-4-1 covers the supplier's development process, from security requirements and secure design through verification, defect and patch management to product end-of-life. Asking a supplier where they stand against both is a quick way to separate those with a process from those with a brochure.

Plan for a twenty-year field life

IEC 62443-2-1:2024 notes that the lifespan of an industrial automation and control system can exceed twenty years and that many legacy systems contain hardware and software that are no longer supported. Component longevity is only part of the answer. Check how long you can get the compiler, protocol stack, configuration software, calibration utility and programming fixture, and whether licences are perpetual. Decide last-time-buy rules, service-stock quantities and redesign triggers in advance, and route end-of-life notices to named people rather than a shared purchasing inbox. The guide on last-time buys for end-of-life parts covers the arithmetic.

Market access: CE, India and the rest

For the EU, the EMC Directive 2014/30/EU requires that equipment neither causes nor suffers from electromagnetic disturbance; compliance with harmonised standards gives a presumption of conformity, and the European Commission notes that CE marking can only be affixed after the product has been tested and the conformity assessment completed. Other directives may apply as well, depending on the product.

In India, BIS certification is voluntary for most products, with compulsory certification applied product by product through Quality Control Orders and the registration scheme. Check the finished product against the current BIS lists rather than assuming that a registered internal component covers it (checked October 2026). North American customers will usually name the UL or CSA standard they expect; get that in writing before you choose an enclosure or power supply.

The evidence pack to request

• Manufacturer and authorised-channel proof for the exact part number
• Lot and date-code traceability and storage history
• Datasheet, errata, change notices and lifecycle status
• EMC, environmental, reliability and safety reports relevant to your use
• Protocol conformance certificate matched to hardware and firmware revision
• Firmware origin, licence terms and update method
• Quality-system scope and change-control procedure
• Counterfeit-avoidance and nonconforming-material controls
• Samples and pilot lots built on the production route
• Lead-time, allocation and end-of-life notification rules
• Failure-analysis capability and response times

Qualify in stages

A sensible sequence is: document review, engineering samples, bench characterisation, environmental and EMC pre-compliance, network interoperability, a pilot build, stress testing where justified, then a monitored field trial. Freeze hardware, firmware, programming files and test limits together. Incoming inspection should check identity, packaging, moisture protection, date codes and traceability; production tests should exercise boundaries, communications, calibration and fault recovery, not just power-up. Feed field returns back into supplier scores.

Several of these controls carry over to other regulated or long-life products; see the guides on EV charger component sourcing and medical electronics sourcing. To find candidate makers, browse automation and process control suppliers or embedded systems suppliers, then post a QUICK RFQ on the RFQ page with the part numbers, conditions and evidence you need.