How to Evaluate Controller Manufacturers: ABB PLC and Beyond — A Scenario-Based Practical Guide

Why "Which Controller Brand Is Best?" Is the Wrong Question

If you've ever asked "which PLC manufacturer is the best?" — you're asking the wrong question. I know because I've spent nine years handling PLC, drive, and electrical component orders for an industrial distribution business that operates across three regions. I've made (and documented) four significant mistakes in that time, totaling roughly $14,000 in wasted budget. Every single one of those mistakes came from the same root cause: I was optimizing for the wrong scenario.

Here's what nobody tells you: evaluating controller manufacturers isn't one decision. It's at least four different decisions that depend on what you're actually doing. Mixing them up is the fastest way to end up with too much of the wrong thing — or too little of the right one.

The Four Procurement Scenarios (And Why They Need Different Criteria)

From what I've seen, controller manufacturer evaluation comes down to four scenarios, each with a different set of priorities:

• Scenario A: Bulk distribution and private-label procurement — where delivery certainty, documentation, and landed cost dominate.
• Scenario B: OEM and custom application integration — where software ecosystems, programming support, and integration cost dominate.
• Scenario C: Safety-critical and regulated environments — where certifications, functional safety ratings, and traceability dominate.
• Scenario D: Lifecycle procurement and spare parts support — where long-term availability years down the road dominates.

Most teams fall into at least two of these scenarios without realizing each one demands different evaluation criteria. I've made that mistake myself — we once specified a distribution-grade component for a safety-rated application because a purchasing manager on our team equated "cheaper" with "better" on a mixed-use order. That's a pain I don't wish to repeat.

Scenario A: Bulk Distribution and Private-Label Procurement

This is the scenario where I got burned early on a large order — around 4,000 contactors and relays that should have been straightforward. The low quote looked great until we added customs, repackaging costs, and three weeks of demurrage. That "cheap" vendor ended up costing roughly $2,100 more than the mid-range quote I'd been sitting on.

I learned the hard way that in bulk procurement, the unit price on a catalog sheet is almost never the real cost. Same logic applies to bulk drive orders — you're not comparing drive unit prices, you're comparing landed cost per unit.

What Actually Matters in This Scenario

1. Landed cost, not unit price — Ask for FOB pricing with freight, duty assumptions, packaging requirements, and minimum order quantities factored in. Different vendors present this differently. I've found the ones who break down every fee upfront are usually the ones who won't surprise you later. (Should mention: I've seen "cheap" quotes with 15% of the cost buried in packaging requirements that were never stated.)
2. Documentation completeness for core products — Compliance certificates, RoHS/REACH declarations, and traceability for batch lots should be available at quote stage, not after something goes wrong. If a supplier can't produce these on request, they're not ready for bulk procurement regardless of price.
3. Lead time consistency for replenishment — This is the one I underweight most often — current lead times on a quote versus lead times six months from now are two different things. Manufacturers with global distribution (ABB's scale here is a genuine advantage, though frankly, that depends on your specific region) tend to maintain replenishment cycles. But ask anyway.
4. Batch consistency — If you're private-labeling, your spec is only as good as the variance between manufacturing runs. Get that commitment in writing.

For a global manufacturer like ABB's contactor and relay range, the distribution network built around those products is a real asset — but only if you're in their core market coverage. I've seen teams pay a premium on logistics for outlying regions because they didn't ask the right questions upfront.

Scenario B: OEM and Custom Application Integration

Here's the counterintuitive bit that trips people up: in OEM settings, chasing the lowest bill of materials cost often ignores engineering time cost. This is the "cheap PLC doesn't cost extra to program" misconception — and it comes from an era when all PLCs programmed roughly the same and software tools were basic.

The "cheap PLC programs the same" thinking comes from the early 2000s when programming environments were more similar and engineers were less locked into one ecosystem. That's changed. Today, the gap between a top-tier PLC software suite and a budget alternative can mean hundreds of engineering hours across a project.

Most modern platforms follow IEC 61131-3 programming standards, but vendor extensions and library ecosystems vary significantly. You get access to certified function blocks, simulation environments, and community resources — or you don't.

This is why ABB PLC software for the AC500 series, for instance, can result in a lower total cost of ownership for a mid-size OEM than a cheaper PLC brand. Not because the hardware is cheaper — it isn't — but because the engineering time is shorter. I've watched one team save roughly 40 hours of commissioning time on a single project because the software handled the integration work more cleanly. At engineering rates, that's a real number.

What Actually Matters in This Scenario

1. Programming software licensing model — Free? Subscription? Per-seat? Perpetual? ABB PLC software (Automation Builder) offers a free version, which makes a real difference in evaluation-stage costing. Don't assume you'll need the paid tier — check the feature matrix.
2. Function block libraries and certified code — How many times will you reimplement the same logic? Certified function blocks reduce integration engineering substantially.
3. Communication protocol support — Native support for the fieldbuses you actually use, or converters? Converters introduce latency, add failure points, and typically add 20-30% to commissioning time.
4. Training and support pathways — Is there manufacturer-supported training, or are you relying on community forums? ABB's training infrastructure is one of their advantages, but I'll admit the quality of training varies by region.

Scenario C: Safety-Critical and Regulated Environments

This is the scenario where the wrong evaluation creates actual liability. I've watched this go sideways: a safety PLC selection where the certification marks looked right, but the SIL rating didn't match the application. We caught it during a client audit — a few weeks before the installation date. The retrofit cost was painful. The credibility cost was worse.

Now, when evaluating a safety PLC catalog, I check compliance against requirements item by item. No assumptions.

What Actually Matters in This Scenario

1. Specific SIL rating and match to your application — SIL 2 and SIL 3 are different products with different cost structures. Over-specify and you pay for capability you won't use. Under-specify and you're exposed. Get this wrong and it's not a money problem — it's a safety problem.
2. Third-party certification — and which body — TÜV, UL, IEC 61508 are the standards, but the specific report and certificate matter. Ask for certificate numbers. Verify them.
3. Safety catalog depth, not just individual products — Can you build a complete safety system from a single vendor's safety-rated catalog? Mixing safety components across vendors makes certification more complicated, not less. (Should mention: some integrators do this successfully, but the documentation burden increases with every vendor you add.)
4. Safety programming environment — Is your safety logic handled in a separate, certified software environment? Is it clearly documented as validated? If not, that's a flag.

ABB's safety PLC catalog covers this space — but that catalog is only useful after you've confirmed it matches your specific application ratings. I'll be honest: this is the one area where I trust nothing but documented evidence.

Scenario D: Lifecycle Procurement and Spare Parts Support

This is the scenario nobody thinks about until a production line goes down because a discontinued module isn't in stock. I don't have a specific disaster story to share here — but I've seen enough close calls to include it. One system-level issue we had taught me that the manufacturer's lifecycle communication policy matters as much as their current inventory levels.

I still kick myself for not asking about the discontinuation roadmap earlier on an older system. If I had, we'd have planned the migration six months ahead instead of scrambling. That one cost us roughly $1,500 in expedited replacements — plus the awkward customer call.

What Actually Matters in This Scenario

1. Product discontinuation notice policy — 12 months ahead versus 6 months is a large difference. Ask for their standard policy in writing.
2. Spare parts availability duration after discontinuation — 5 years is one number. 10 years is another. Get it in the contract.
3. Migration path clarity — When a replacement is announced, is it drop-in compatible? Pin-compatible? Requires rewiring? Get real answers, not "it should work" from a salesperson.
4. Backward compatibility with newer products from the same manufacturer — If you upgrade in the future, will your existing code migrate cleanly? Or will it require a rewrite?

How to Figure Out Which Scenario You're Actually In

You're probably in two or three of these simultaneously. Here's a quick diagnostic to find your primary placement:

1. Do you order more than ~500 units of any controller or drive per year? If yes, Scenario A is primary. Documentation completeness and landed cost will determine your real spend, regardless of unit price.
2. Are you integrating controllers into your own OEM product? If yes, Scenario B dominates. Software ecosystem cost and engineering hours matter far more than BOM price.
3. Does the application involve human safety or regulatory compliance? If yes, Scenario C is your first gate. Certifications are hard requirements — compare cost only among suppliers who meet them.
4. Are you maintaining any systems that are 5+ years old? If yes, Scenario D is a real constraint. A supplier who's excellent on reliability is still the wrong choice if they can't support you years down the line.

If you check multiple boxes — and most of my clients do — evaluate each scenario separately and assign different weights. Don't try to apply one set of criteria to cover all cases. That's how you end up with a safety-rated solution for a distribution-grade application, or a budget PLC for a system that needs 10-year availability.

If I could distill nine years of mistakes into one takeaway: ABB PLC, Schneider's Modicon, or Rockwell's ControlLogix are only as good as the fit for what you're actually doing with them. They can each be the wrong choice in the wrong scenario. The evaluation isn't about finding the best brand — it's about matching the manufacturer's strengths to your specific priorities.

And one more thing: get it in writing. Whatever you decide, whatever the supplier promises — document it. I'm still kicking myself over decisions that were based on verbal assurances. That lesson cost more than any single order on this list.