Who this checklist is for

If you're installing or accepting an Allen-Bradley PLC system—whether it's a new CompactLogix line, a legacy SLC 500 retrofit, or a trainer kit for your team—this is the exact sequence I run through before I sign off. I'm a quality and brand compliance manager. I review every deliverable before it reaches our customers, roughly 200 unique items a year. I've rejected about 15% of first deliveries in 2024, mostly for spec mismatches nobody caught during unpacking.

There are 7 steps. They're in order. Skip one and you'll probably find out at the worst possible time—line down, customer waiting, everyone looking at you.

Step 1: Confirm the exact PLC model against the purchase order

This sounds insulting. Do it anyway. I've seen a CompactLogix 5380 show up when the PO said 5480 (the spec sheet looks nearly identical until you get to the memory and motion capability).

For the Allen-Bradley SLC 500 PLC specifically—still common in retrofits—check the catalog number character by character. A 1747-L542 is not the same as a 1747-L543. The suffix difference can mean different memory or communication ports. Vendors quote from memory. Your acceptance should not.

In Q1 2024 we received a batch of 40 PLC modules where the firmware revision was two versions behind the spec. The vendor claimed it was "within industry standard." It wasn't. We rejected the batch, and they reflashed at their cost. That episode cost us a $22,000 redo and pushed our launch back three weeks. Now every contract includes a firmware revision clause.

Step 2: Open the trainer kit and inventory everything

If you ordered an Allen-Bradley PLC trainer kit, don't let it sit in the box until training day. Open it the day it arrives.

Here's what I check:

  • Power supply matches the local voltage (this gets missed constantly on international orders)
  • All I/O modules are seated and the keyswitch is functional
  • Communication cables are present and the correct type (Ethernet vs. serial—people mix these up)
  • The software license is registered to your company, not the reseller

I ran a blind spot check with our training coordinator last year: we set up two trainer kits, one factory-sealed and one pre-inspected. She found the sealed kit had a missing Ethernet cable. Nobody would have known until the first training session. That's a $400 cable delaying a $3,000 training day.

Step 3: Verify the 12V DC-DC battery charger for backup and field power

This is the step most people skip. If your PLC system has any field-mounted components or backup power, you need to verify the DC-to-DC battery charger 12V setup before you energize anything.

What I check:

  • Input voltage range matches your source (12V nominal doesn't mean it accepts 9-18V—read the datasheet)
  • Charging profile is compatible with the battery chemistry you're using (AGM vs. gel vs. lithium—they're not interchangeable)
  • Output ripple is within the PLC power supply's tolerance. I've seen cheap chargers inject enough noise to cause intermittent I/O faults. That's a nightmare to diagnose because it looks like a programming bug.

I have mixed feelings about off-brand chargers here. On one hand, a name-brand unit costs 2-3x more. On the other, I've watched a $30 charger take down a $15,000 I/O rack because nobody checked the ripple spec. We now standardize on units with published ripple figures under 50mV.

Step 4: Set up the industrial PC and open the NVIDIA Control Panel

If your programming workstation or HMI runs on a PC with an NVIDIA GPU (common on visualization stations), verify display settings before you connect to the PLC. This sounds tangential. It isn't.

Here's how to open the NVIDIA Control Panel: right-click on the desktop and select it from the context menu. If it's missing, the driver install may have skipped the control panel component—reinstall with the "custom" option and check the box.

Why this matters for PLC work: if the display is scaling at 125% or 150% (common on 4K monitors), HMI screen layouts and tag tables in Studio 5000 can render with clipped columns. You'll spend an hour thinking your project file is corrupted when it's just display scaling. I've done this. Twice.

Step 5: Check field power—including any Amped Outdoors battery charger if used on-site

For field commissioning or remote sites, portable power matters. If your team uses an Amped Outdoors battery charger or similar portable unit for test equipment, verify it's charged and outputting the correct voltage before you leave for the site.

Portable chargers are great for laptops and test meters. They are not PLC power supplies. Do not connect one to a PLC rack. I've seen someone try. The result was a blown fuse and a very quiet truck ride back to the shop.

Take this with a grain of salt, but our field team's rule is: portable charger for test gear only, hardwired supply for anything that runs a process.

Step 6: Verify I/O wiring and grounding

Basic, yes. Skipped, constantly. Before energizing:

  • Check that analog shields are grounded at one end only (both ends creates a ground loop that shows up as random noise)
  • Confirm 24V field power is within tolerance at the farthest device, not just at the supply
  • Verify the PLC ground is bonded to the panel ground—separate grounds cause communication faults that look like software issues

The "separate grounds" thing was true 15 years ago when PLC networks were more forgiving of ground potential differences. Today's Ethernet-based systems are less tolerant, and a floating ground can cause intermittent communication drops that are genuinely hard to trace.

Step 7: Document everything before handoff

Photograph the installed rack. Record firmware versions. Note any deviations from the approved drawing—even the "temporary" ones your installer says they'll fix later.

I went back and forth between paper sign-off and a digital checklist for about six months. Paper was faster on-site; digital was searchable later. Ultimately chose digital because when a question came up eight months post-install, I could find the answer in 30 seconds instead of digging through a filing cabinet. The trade-off was worth it.

Even after we switched to digital, I kept second-guessing. What if the field team didn't fill it out properly? The first month was stressful. Then we caught a wiring error during a quarterly audit that the digital record pinpointed to a specific install date. I relaxed after that.

Common mistakes I see repeatedly

  • Accepting delivery without opening boxes. You have less leverage every day that passes.
  • Assuming "it powered on" means "it's configured." Power-on is not a quality check.
  • Letting the installer be the only person who sees the final wiring. Get a second set of eyes before the panel goes dark.
  • Skipping the firmware verification because the label says the right version. Labels get printed wrong. Check the software.
  • Using portable power equipment (including that Amped Outdoors battery charger) for anything beyond test gear. It's not built for it.

Here's what you need to know: none of this is complicated. It's just tedious. And tedious things get skipped when everyone's under deadline pressure. That's exactly when you pay for it.

Ingrid Bauer

Ingrid Bauer

Ingrid Bauer is an industrial automation and electromechanical systems analyst specializing in variable-frequency drives, motors, pumps, and complete power-drive systems. She applies IEC 61800-9-2 drive-efficiency methods, IEC 60034-30-1 motor efficiency classes, and ISO 9906 pump tests while examining torque-speed duty, harmonics, head, flow, and operating-point efficiency. She helps engineers size drive and pump combinations for real load profiles, cable lengths, ambient conditions, process control, energy use, and maintenance access.