Relay Notes

Allen-Bradley PLC Types and Logic: A 7-Step Emergency Spec Checklist

2026-10-29 · Marta Kowalska

Who This Checklist Is For

I'm an emergency-order coordinator at an industrial automation supplier. My shift starts when a line is down and somebody needs a controller specified, sourced, and talking before the next crew clocks in. What follows comes from roughly 200 rush jobs over six years — mostly packaging cells, material handling, and a handful of water-treatment panels. If you're building a greenfield plant on a two-year schedule, some of these steps will feel overcautious. Keep the ones that fit.

Seven steps. With an I/O list and a set of drawings in front of you, it takes about 45 minutes. Without them, it takes an afternoon and a phone call to the electrician who actually wired the machine.

Step 1: Pick the Allen-Bradley PLC Type From the Job, Not the Datasheet

Allen-Bradley PLC types break down roughly four ways in practice — or rather, four families you'll actually see on a quote:

  • Micro800 family (Micro850 and up) — standalone machines, small I/O counts, built-in Ethernet on the 850.
  • CompactLogix (5380 series) — cell-level control, the workhorse for most mid-size lines.
  • ControlLogix (5580 series) — plant-wide, redundancy, the big I/O racks.
  • SLC 500 and PLC-5 — legacy. Only spec these when you're replacing in kind and the customer has a shelf of spares.

Before you pick, check the site standard. If the plant is already running CompactLogix everywhere, don't be the person who saves $900 by introducing a Micro850 into a maintenance department that only stocks CompactLogix spares. That's a false economy with a six-month fuse on it.

Step 2: Decide the Logic Language Before You Buy Hardware

Allen-Bradley PLC logic isn't one thing. IEC 61131-3 defines five languages, and Studio 5000 supports ladder, function block, structured text, sequential function chart, and instruction list.

My default for a line that will be maintained by plant techs: ladder. It's what most maintenance people can read at 2 a.m. without opening a manual. Use structured text for the math-heavy blocks (PID tuning, scaling, recipe math) and function block for process control where the drawing looks like the P&ID. Don't use structured text for the whole machine just because you find it faster to type. You won't be the one debugging it in three years.

Step 3: Count I/O and Power, Then Add a Buffer

Take the I/O list and add 20% spare on both digital and analog. Not 10%. The spare points get used on almost every project, usually during commissioning, and the cost of a spare card later is roughly three times the cost of ordering it with the rack.

Analog modules need their own supply check. A 24 VDC supply sized off the digital count alone will brown out the first time three transmitters pull current at once. I've watched that happen. Add up the worst-case current draw, not the typical.

Step 4: Lock the Firmware and Software Revision (the Step People Skip)

This is the one that burns emergency buyers. The controller you order arrives with a firmware revision. Your Studio 5000 install has a version. If they don't match — and if you don't have the right software version — the controller is a very expensive paperweight until something gets downloaded.

I've seen this go wrong in exactly the way you'd expect. In February last year, a customer took delivery of a CompactLogix on a Thursday with the line due to restart Friday morning. Firmware far newer than their Studio 5000 install. No one on site had the matching version. We spent six hours on support lines and an overnight download to fix a problem a five-minute check at the quote stage would have avoided. Since then it's step four on our internal checklist, not a footnote (note to self: this is the check I used to skip when the customer was in a hurry).

Step 5: Confirm the Network Before the Hardware Ships

EtherNet/IP is the default on modern Allen-Bradley PLCs, and most of the time it just works. The failures I see are almost never the controller. They're the switch that turned out to be unmanaged, the IP plan that collided with an existing subnet, or a gateway that was supposed to bridge Modbus and nobody confirmed the settings.

Get an IP range in writing before the order goes out. If there's a Modbus device in the mix, decide now whether you're using a gateway or a dedicated module. Deciding it on commissioning day costs a day.

Step 6: Build a Spares Line Into the Order

At minimum: one spare power supply and, on any line that runs three shifts, a spare CPU. I know what that does to the quote. I also know what a $1,800 CPU saves when the alternative is a $12,000 downtime invoice.

We learned that the expensive way. In 2022 we quoted a rush panel without a spare CPU to keep the total under a budget number the customer had in their head. The CPU failed on a Saturday night six weeks later. Emergency air freight, weekend support, and a very uncomfortable Monday call added up to more than the spare would have cost three times over. The customer still buys from us. I don't think that's because they forgot.

Step 7: Hand Over Documentation, Not Just Hardware

As-built drawings, an IP address table, and commented logic. Uncommented ladder is a form of job security that nobody actually wants. If you're handing a line to a maintenance team that didn't build it, spend the extra hour on comments. It's the cheapest thing on the whole project and the one most often cut.

Where This Checklist Stops — and Where to Look Instead

I want to be honest about the boundary. This checklist covers Allen-Bradley PLC selection and commissioning under deadline pressure. It does not cover everything that lands in our inbox.

We get calls every week from people who found us searching solar inverter near me, or looking for an oil filter for a GMC Sierra 1500, or asking how to test a car battery with a multimeter. We don't do any of those. Different supply chain, different expertise, different phone call. We point people toward someone who does that work well, and we go back to what we're actually built to do.

That's not a humblebrag. It's just how a specialist stays a specialist. The vendor who tells you 'this isn't our strength — here's who does it better' is usually telling the truth about everything else too.

The Three Mistakes That Cost the Most

Assuming firmware compatibility. Already covered, still the number one cause of a dead-on-arrival controller.

Cutting spares to hit a budget number. The budget number is real. So is the downtime invoice. Only one of them shows up on your boss's radar.

Skipping the site standard check. A technically correct platform choice that the maintenance team can't support is a wrong choice.

My sample is roughly 200 rush jobs, mostly mid-size lines. If you're working on a plant-wide ControlLogix rollout with a dedicated controls team and a two-year runway, some of this will be too conservative for you. Take what fits and leave the rest.

Marta Kowalska

Marta Kowalska

Marta Kowalska is an electrical equipment procurement and quality analyst covering distribution gear, automation, generators, pumps, test instruments, and engineered assemblies. She reviews IEC 61439 routine-verification records for assembly current and temperature rise, IEC 60034-1 rating and test data for rotating machines, and ISO/IEC 17025 laboratory scopes for reported calibration uncertainty. She helps buyers compare inspection status, document traceability, total installed cost, lead time, service access, spare-parts support, warranty boundaries, and failure consequences across equipment categories.