How to Evaluate PLC Suppliers and Drive Manufacturers: A Quality Reviewer's Checklist

If you are about to add a new PLC supplier, approve a drive manufacturer, or re-qualify an existing automation vendor, this checklist is for you.

I work as a quality compliance manager for a control panel and custom machinery company. I do not place the largest orders in our industry, but every component I approve has to survive production, a panel build, and a customer acceptance test. In 2024, I logged more than 200 supplier submissions and still rejected about 11% of first deliveries. Most of those disapprovals were not dramatic. Wrong firmware version. Missing Declaration of Conformity. A software library that did not match the part number. That is the level of detail that decides whether a supplier belongs on your approved list.

This checklist is a practical pass. Use it when you are choosing between two PLC suppliers, or when you need to decide whether a drive manufacturer should become your second source. It will not tell you which brand is perfect, because no brand is.

The Six Evaluation Checks

I have broken the process into six checks. The first three happen at your desk. The next three require samples, software, and a little patience.

1. Compare specifications with the real operating envelope

The first thing I do is read the datasheet for the exact model number. Not the product family page. Not the marketing table with typical performance. The specific model datasheet.

I want to know what the product can do when the conditions are not perfect. A PLC might be rated for 0 to 60 C, but what is the ambient temperature inside your panel when the drive next to it is running at full load? If you use DC output cards, do the total current and the inrush current of your valves stay inside the output ratings?

With drive manufacturers, pay attention to the output current at your required switching frequency. A VFD can be rated for 8 A at 4 kHz, but at 12 kHz the available continuous current can drop. Check the derating table instead of assuming the nominal motor rating is enough for continuous duty.

Make a list of required signals before you compare quotes. If your PLC has sourcing outputs and the drive inputs expect dry contacts, that is not a deal-breaker, but it should appear in the design review. The datasheet is where those compatibility questions become visible.

2. Verify certifications on the exact product variant

Certification is not a logo next to a brand name. It has to apply to the exact product variant and, in many cases, the firmware version. I do not accept a certificate unless the product name, series, and options are visible.

In Q1 2024, a vendor sent a certificate for a previous safety PLC version. The printed label on the sample matched the new version, but the documentation did not. The product did not need to be re-certified in the end, but the mismatch cost us four days of verification work. On a project with a deadline, four days is real money.

For drive manufacturers, the same logic applies. If the catalog says STO or safe torque off, find the standard behind that claim. IEC 61800-5-2 is the standard for safety-related power drive systems. I expect the manufacturer to state the safety integrity level, installation conditions, response time, and relevant parameters. If that information is missing from the manual, then the safety claim is not ready for your machine.

3. Treat lead-time certainty as a quality criterion

I learned this lesson in a way that cost me a stressful week. In March 2024, we had a $15,000 machine shipment waiting on one drive. One vendor offered a slightly cheaper drive and a delivery estimate that sounded like probably six weeks. Another vendor offered a locked delivery date and charged about $400 more. We paid the extra $400.

That $400 was not buying speed. It was buying certainty. In emergency situations, an uncertain cheap option is more expensive than a clear premium because the cost of missing the deadline lands on your project, your customer relationship, and your team's overtime.

A flexible delivery promise is not a specification.

Ask suppliers how on-time delivery is measured. Ask whether the delivery date starts when the purchase order is placed or after engineering review. Ask whether the commitment can be included in writing. When I evaluate drive manufacturers today, lead-time certainty carries as much weight as the price.

4. Run an integration test with the actual PLC and drive

A showroom demo tells you that each product works by itself. It does not tell you how a drive behaves when a PLC writes a speed reference over Modbus TCP, or whether the fault codes in the manual match the fault codes in the register map.

Set up a sample in your own lab with the same programming environment your engineers will use. Try reading drive status, writing a speed setpoint, changing a parameter, and resetting a fault through the network. You are looking for mismatches between the manual and the real device.

I once saw a PLC read drive current as a 16-bit value while the drive was publishing a 32-bit scaled value. The network connection worked. The data did not mean what we expected. The fix was simple, but finding it took a day of engineering time. A simple integration test before supplier approval would have exposed it.

Vendors that refuse to send a sample or make you work through a sales engineer for every technical question are not saving you time. They are transferring risk to your team.

5. Evaluate the software ecosystem and the supplier knowledge base

Hardware specifications matter, but the software ecosystem decides how much engineering time you will spend. Compare the programming environment, license model, firmware update process, and training material as carefully as you compare the PLC price.

If the supplier charges separately for basic function blocks, that cost should appear in your total comparison. If the programming software only works with an operating system version your company has stopped supporting, that is a future compatibility risk. If a drive manufacturer expects you to use a configuration tool that changes with every firmware release, that is a maintenance cost.

Documentation quality is another clue. This is where the Schneider PLC knowledge base has become my reference benchmark. The Modicon M221, M340, and M580 families are documented in a structured way: specifications, programming software, certificates, FAQs, firmware updates, and troubleshooting guides are available without sending an email to a salesperson. That does not make Schneider the only good supplier, but it shows what a mature technical knowledge base looks like.

When I review a new PLC supplier, I ask: can I find the current manual and the latest firmware without talking to a human? If the answer is no, your future support desk is going to be your own engineering team.

6. Read the safety PLC catalog, even if safety is not on the drawing

A standard PLC and a safety PLC are not the same product. If your machine has a guard door, an emergency stop, or a light curtain, the architecture needs certified safety functions. But even when the current project is not safety-rated, reading the safety PLC catalog tells you how seriously the supplier treats functional safety.

Look for a catalog section that clearly separates standard PLCs from safety PLCs. Check which safety functions are certified and which conditions must be met. If a supplier says it has a safety PLC but the catalog does not list SIL/PLe values, response times, or certified configurations, that is a red flag.

For drive manufacturers, the question is simpler: does the drive have a safe torque off option? If the drive does not support STO, a future safety upgrade may require an external safety contactor. That is not the end of the world, but it affects panel space, wiring, and cost. Evaluating that possibility before you approve the vendor is much cheaper than redesigning the panel later.

What I've Learned to Treat With Caution

One old belief that I still hear is that a local warehouse is always faster. Local can be fast, but can be is not a specification. I have waited longer for a nearby supplier that forgot to enter an order than for a well-organized remote supplier that shipped the next day. The real question is not distance. It is process.

I am also cautious about demonstration sessions where the supplier's own engineer runs the equipment. A demo shows what the supplier wants you to see. An integration test with your PLC, your software version, and your application shows what your Monday morning will look like.

And I no longer ignore documentation quality. If the PDF manual is outdated, if the knowledge base is mostly marketing content, or if the examples do not match the current version of the product, the supplier has made a choice. They are spending money somewhere else. Some of that cost will eventually land on you.

Final Note

Choosing between an established supplier and a challenger is not automatically about brand reputation. It is about where the risks hide and who pays for them later.

I evaluate drive manufacturers and PLC suppliers with this checklist when the component is critical to a project. Some suppliers answer every question clearly. Some do not. The ones with clear documentation, verified certifications, honest delivery commitments, and a useful knowledge base are easier to choose. The rest are not necessarily bad, but they should be accepted only when you understand the risk you are taking.