Perkins Generator Logo

What a 36-Hour Allen-Bradley PLC Emergency Taught Me About Training Kits and Transfer Switches

· Pavel Novak

March 14, 2024, 16:47. My phone buzzed. It was a facility manager at a mid-sized bottling plant—one of our longer-standing accounts—and he was not in a good mood.

Their main filler line was down. Not running slow—stopped. The culprit: a 2005 Allen-Bradley PLC motherboard that had finally cooked itself after 19 years of near-continuous service.

They'd already called two other suppliers. Nobody had the exact replacement in stock, and the OEM quoted a 2–3 week lead time on the closest equivalent.

I looked at the clock. Thursday afternoon. Their contract had a productivity penalty clause kicking in Monday at 6:00 a.m.: $18,000 if the line wasn't back up.

When I first started managing emergency PLC orders, I assumed the job was about getting the right hardware to the customer as fast as possible. Seven years later, I've realized that's only half the battle. The other half—the part that actually determines whether an order becomes a rescue or a warning—is whether the team on-site is ready to use what we ship.

The order that almost wasn't a win

I started working the phones. After 90 minutes of calls, I found a freight-forwarded small Allen-Bradley PLC—a Micro850 with enough I/O points for their immediate needs—sitting in a distributor warehouse in Columbus, Ohio. Rush freight would put it on-site by Friday morning.

Normally, that would be the win. But I've learned to ask one question before I seal any rush order: Who's going to program it?

That question saved us.

The client had two maintenance techs on staff. One had some RSLogix experience. The other had spent most of his career on relay logic. Neither had touched the newer Connected Components Workbench environment. They could swap hardware, but they couldn't get the line running again without help.

So I added an Allen-Bradley PLC training kit to the order—the same-day version with the controller, power supply, and pre-wired I/O modules that let you run through logic exercises before you touch live equipment. I paid $1,200 extra in rush fees for it. (Pricing based on distributor quotes from March 2024; verify current rates before budgeting.)

But the training kit wasn't even the real headache. That came next.

The manual transfer switch question I should have asked first

While the hardware was in transit, the client's senior tech called me. "We're splicing the old logic over. Should be straightforward—we're keeping the manual transfer switch, right?"

I paused. "Let me check what your transfer switch actually is."

I assumed—wrongly—that it was just a simple rotary switch. When I pulled up the spec sheet he emailed over, I realized it was a mechanically interlocked manual transfer switch designed to feed power between two supply sources. The old PLC had been directly driving the contactor coils from its relay outputs.

Here's where my day got interesting. I asked the senior tech what he thought about the new PLC's relay output driving the same contactor coils. He paused for a second and said, "Well, that depends on whether you're switching a relay or a contactor."

And I realized I didn't actually know the answer cold.

That's the kind of thing you'd think an automation distributor rep would have memorized. I had to work it out in my head: the difference between a relay and a contactor isn't just about size or load rating. A relay handles logic-level currents and control signals. A contactor handles the actual load—motor currents, high-voltage switching, inductive loads. The old design was mixing both functions by using the PLC's relay outputs to directly pull in contactor coils.

On paper, that works. In practice, it's a recipe for contact welding after a few thousand cycles, especially with the inductive kick from a contactor coil.

We added two interposing relays to the shipment—$180 in rush fees, but it saved us a future failure. The senior tech caught the gap before I did, which humbled me a bit. Not ideal, but workable.

Friday night, two techs, and a sticker I didn't expect to matter

The Allen-Bradley PLC training kit arrived Friday morning alongside the PLC. That's when I hit my next snag. The kit's documentation was incomplete—one of the quick-start cards was missing.

We found a workaround. Each module in the kit had a small PLC logo sticker that clearly marked which module was the controller versus the I/O extension. It sounds trivial, but when two techs are sorting through modules at 11 p.m., visual identification pays for itself.

We used that logo to rebuild the training sequence, then watched the junior tech walk through a ladder logic exercise using the kit's pre-mapped I/O. He was building his first working program by midnight.

We tested the interposing relay wiring Saturday afternoon. The manual transfer switch behaved exactly as it should—no welded contacts, no phantom signals. The junior tech ran the startup sequence twice without an error. Worth doing, but tedious.

Monday, 5:35 a.m.

The line was back up at 5:35 a.m. Monday, five minutes before the deadline and 15 minutes before the penalty clause activated.

Total incremental spend on rush freight, the training kit, and the interposing relays: about $2,400. The penalty we avoided: $18,000. The actual production value recovered: somewhere north of $50,000 based on the client's own estimate.

Not a bad weekend. But that's not the lesson I'm still thinking about nearly a year later.

What I wish I'd packed from day one

I don't have hard data on how many emergency PLC orders fail because of preparation gaps rather than supply problems. But anecdotally, across the 400+ rush orders I've handled, the ones that cause trouble almost always involve a gap between the hardware and the team's readiness to use it. My sense is it's a significant chunk—maybe a third.

Even after I chose the training kit option, I kept second-guessing. What if the techs didn't have time to go through the material? What if the transfer switch wiring was more complex than the spec sheet suggested? I didn't fully relax until the Monday morning startup. The moment the line ran product without an alarm, I exhaled for the first time all weekend.

So what changed?

I now package a few extras with every emergency Allen-Bradley PLC order:

  • A training kit—even the basic version. It doesn't cost much, and it changes the conversation from "when will the box arrive" to "can your team run this?"
  • A printed relay-vs-contactor reference card. One page. It sounds absurdly simple, but when a tech is wiring at midnight, a reference card on the panel door saves 20 minutes of googling.
  • A pre-determined contact at the distributor who can confirm relay output specs before the order ships.

None of this is glamorous. But the shift from "buy the part fast" to "buy the part fast and make sure the team can use it" has cut our emergency callbacks by more than half.

That old tech's question—"relay or contactor?"—turned out to be the most valuable sentence of the whole weekend. Not because it was obscure, but because I should have asked it first.


Ask about this topic

Share your application conditions and the project stage so the discussion can focus on relevant ratings, interfaces, and documentation.