If you're specifying an Allen-Bradley PLC for the first time, you're probably feeling the pressure. Not just from the project deadline, but from the sheer number of options. I've been there. In my first year handling automation orders (2017), I made the classic mistake: I picked a controller based on price and availability, without thinking about the ecosystem. It worked on paper. On the factory floor, it was a disaster. A $3,200 order of CompactLogix controllers that didn't scale with our I/O needs. The $400 rewire and 1-week delay to swap them out taught me a lesson I'll never forget.
This checklist is built from that mistake and about a dozen others. If you're an engineer or a procurement manager getting into Allen-Bradley for the first time, these five steps will save you from repeating my errors. I don't have hard data on how many first-time buyers get this wrong, but based on our 5 years of orders, my sense is at least 20% of initial PLC specs need a revision. Let's make sure yours isn't one of them.
When to Use This Checklist
This isn't for seasoned Rockwell Automation users. It's for you if:
- You're moving from a different platform (Siemens, Mitsubishi, etc.) to Allen-Bradley.
- You're an OEM building your first machine around an Allen-Bradley controller.
- You're under a tight deadline and can't afford to second-guess your hardware choices.
People assume choosing a PLC is just about specs. The reality is it's about the ecosystem—training, support, spare parts, and future scalability. I've seen engineers pick a Micro800 for a 20-I/O project that later needed 50 I/O. That's not a spec issue; it's a forethought issue. Below is a step-by-step checklist. I'll walk you through each one.
Step 1: Map Your I/O and Future-Proof It
This sounds obvious. It isn't. Most people count the current I/O points and add 10%. That's not enough. In September 2022, I approved a spec for a Micro850 PLC that had exactly the right number of digital inputs for the current project. Three months later, the client added a sensor array. We had to add an expansion module, which wasn't in stock. Two-week delay.
The rule I learned the hard way: Count your current I/O. Then double it. If that feels like overkill, add 50%. The cost of an unused expansion slot is minimal compared to the cost of a retrofit.
Checklist for this step:
- Count all digital and analog I/O points.
- Add 50-100% of that as a future growth buffer.
- Check if any I/O needs specialty modules (high-speed counter, temperature, etc.).
- Verify the PLC's max I/O capacity with expansion modules. (CompactLogix 5380, for example, handles up to 256 local I/O points, but can expand further.)
Step 2: Choose Your Programming Environment (Software)
From the outside, it looks like the software is a minor detail. The reality is the software determines your development time, debugging ability, and long-term maintenance. The Micro800 series uses CCW (Connected Components Workbench). The CompactLogix and ControlLogix use Studio 5000. They are not interchangeable.
Honestly, this is where I see the biggest rookie mistake. A colleague once ordered 10 Micro820 PLCs because they were cheap, but the team only knew Studio 5000. We spent a week learning CCW from scratch. The project was delayed, and the 'savings' from the cheaper PLC were eaten by overtime.
Rule of thumb:
- If your team knows Rockwell software, use what they know.
- If this is a new team, start with Studio 5000 if the budget allows. It's the industry standard and most training resources are built around it. CCW is fine for simple standalone machines, but it has limits.
- Don't buy a Micro800 unless you're certain the project will never grow beyond its CCW limitations. (I should add that CCW is free, which is a nice perk for budget projects.)
Step 3: Verify Power and Networking Requirements
This is the step people skip because it's 'boring.' It's not boring until your panel doesn't power up. Allen-Bradley PLCs have specific power supply requirements. For example, the 1769-series CompactLogix controllers need a 24V DC power supply with enough current to handle the CPU and all I/O modules.
Here's the hidden catch: The power supply calculation isn't just about the total current; it's about inrush current when the system powers up. In March 2024, I saw a spec fail because the power supply was rated for 2A continuous but the system needed 3.5A for startup for a split second. The controller kept resetting.
Checklist for this step:
- Look up the exact power consumption of your chosen CPU and each I/O module.
- Calculate total continuous current.
- Add a 20-30% safety margin.
- Check the inrush/startup current from the datasheet.
- For networking, decide on Ethernet/IP, ControlNet, or DeviceNet ahead of time. (Ethernet/IP is standard for most modern applications.)
Worse than expected: I once ordered a ControlLogix system with the wrong power supply module. The 1756-PA72 vs 1756-PB72? Different voltage ranges. Cost us $200 in restocking fees.
Step 4: Procure with a Contingency Plan
This is where the time certainty premium comes in. In an ideal world, you order a PLC and it shows up next week. In reality, lead times for Allen-Bradley products can be 2-6 weeks depending on availability. If you're on a tight deadline, the cost of rush delivery or guaranteed stock is worth it.
In March 2024, we paid $400 extra for a rush delivery on a CompactLogix 5380. The alternative was missing a $15,000 event. Easy decision. After getting burned twice by 'probably on time' promises from standard suppliers, we now budget for guaranteed delivery on critical projects.
Action Steps:
- Check stock levels with three suppliers before committing.
- Ask for lead time guarantees in writing.
- If the deadline is hard, pay for expedited shipping or premium supplier tiers.
- Order spare modules if the project timeline can't tolerate a single failure. A spare 1769-L30ER costs about $600. A day of downtime costs more.
Step 5: Plan for Training and Setup
People assume the PLC will work perfectly out of the box. That's true for the hardware maybe 95% of the time. The software is another story. If your team hasn't used Studio 5000 before, budget for at least 3 days of initial training. I know, I know, training costs money. But untrained engineers cost more in rework.
Here's a practical setup checklist:
- Assign one person as the 'controller lead' who will own the spec and programming.
- Enroll them in a Rockwell Automation training course (online or in-person) before the hardware arrives.
- Have the programming software installed and licensed before the controller arrives.
- Do a bench test before panel installation. Power it up, flash the firmware, test a simple program.
Dodged a bullet when I insisted on a bench test for a recent ControlLogix order. We found a firmware mismatch that would have caused a 3-day panic during commissioning. Cost us 30 minutes to fix on a bench. We were one click away from installing a mismatched controller in the panel.
3 Common Mistakes (And How to Avoid Them)
I'll leave you with the three errors I see most often:
- Buying the wrong series. The Micro800 is not a 'smaller CompactLogix.' They're architecturally different. Don't treat them as substitutes.
- Ignoring spare parts. You don't need a stockpile, but a spare CPU or power supply for critical equipment is baseline. Learn from my $890 redo.
- Skipping the training budget. A $2,000 training course pays for itself if it prevents one $4,000 programming error.
The surprise for me was how much of a difference the 'expensive' option—Studio 5000, proper training, rush delivery—made in overall project cost. The cheapest quote is rarely the cheapest project. That's a lesson I keep learning, every time I skip my own checklist.
