Are you an experienced controls engineer working in manufacturing or integration with an in depth knowledge of Allen-Bradley and have recently been introduced to Siemens?

Image by Chris Wright

For eleven years I've predominately with Allen-Bradley Programmable Controllers, which is not very surprising as they are the most common brand used in North America.

But recently I started working with a manufacturing company who’s equipment is all Siemens, and for the past year I've been exclusively working with the Siemens line.

So in today's article I want to share with you a comparison of these two product lines, including both the programmable controller hardware, as well as programming software.


Let’s start by looking at the Controllers or CPUs of each manufacturer.

From an Allen-Bradley programmer's perspective, at first glance a Siemens S7-1200 might look like a MicroLogix, with its small form factor and on-board I/O.

Siemens S7-1200 (click for source)

But the S7-1200 is actually more comparable to the CompactLogix in terms of processing power and memory.

That said, the S7-1200 is more limited in add-on modules. It supports a max of 1 signal expansion board (aka plug-in), 8 signal modules, and 3 communications modules, while the latest CompactLogix line, the 5380 series, can support up to 31 I/O modules (with the largest Controllers – Ed.)

Image by Shawn Tierney

On the larger scale Siemens offers the S7-1500, which is comparable to the ControlLogix family of controllers.

The main difference between these two is the S7-1500 does not require a backplane, as it is a din rail mount system.

Siemens S7-1500 Family (click for source)

The S7-1500 also comes standard with two PROFINET ports, which allows the user to separate networks and makes connecting to other devices simpler.

The S7-1500 also comes with a small graphical display which allows for troubleshooting right from the front of the PLC.

Image by Shawn Tierney

One area that I feel Siemens has Allen-Bradley beat in is the remote I/O field.

Siemens offers the ET200 line of remote I/O which can be used as remote I/O or a standalone PLC system as the ET200 can be purchased with a CPU and can be programmed just like the S7-1500; a failsafe CPU can also be purchased.

I use this option quite a bit in smaller machine applications as it is cost-effective.


Now let's take a look at the Siemens TIA Portal software; v16 of TIA Portal was just recently launched.

The first thing Siemens has going for it is the HMI and PLC can be programmed from the same software package; yes, I know Connected Components Workbench allows for the same but it is not even close to TIA Portal. (TIA Portal comes with WinCC Basic to program Siemens Basic Panels, and can be upgraded to support higher end HMIs. Rockwell's Studio 5000 Logix Designer comes with View Designer for the PanelView 5000 HMIs – Ed.)

TIA Portal software allows the user to connect to PLC where the IP address is unknown, allowing you to connect to the PLC through the accessible devices option simplifying configuring of a new PLC, and eliminating the need to use a utility like BOOTP.

Image by Chris Wright

Siemens also does not require other software such as RSLinx and FactoryTalk View Studio in order to program and setup the PLC and HMI.

One issue I do have with this is if I make an HMI change, someone cannot come behind and upload the HMI changes I made. I would instead have to give them a copy of my PLC program.

Programming Environment

Now to everyone’s favorite topic: What is the difference between Siemens and Allen-Bradley in the programming environment?

Short answer: a lot, but to cover that in detail would be another article. Here we will look at a few of the most noticeable differences.

One of the positives for Siemens is that it allows the user to add an “Unspecified CPU,” and then add the I/O modules to it.

This allows the programmer to start writing code right away even before the exact CPU has been chosen.

In the project tree of an TIA Portal project we see several folders and icons, and most of these serve the same purpose as the project tree functions in RSLogix 5000.

Devices and networks can be compared to RSLinx, but in my opinion better.

This shows the devices that are connected to your PLC network; HMIs, robot, torque boxes, etc.

Program blocks is where you can add Functions, Function Blocks, and Data Blocks, or in Allen-Bradley terms, Routines.

PLC Tags is comparable to Controller Tags in RSLogix/Studio 5000, and is where your I/O will be located with and other tags you might want to add.

PLC Data Types is (as you probably guessed) for User Defined Data Types.


Siemens has come a long way since the days of STEP 7 Classic and it shows.

While in North America Allen-Bradley is the more popular PLC brand, Siemens is starting to make some headway.

Allen-Bradley PLCs allow the user to expand the system more, but this comes at a higher price point compared to Siemens.

And Siemens all-in-one programming software cuts down on software packages and licensing costs; you still have to buy a license for Siemens programming software.

I also feel Siemens makes it easier to setup new devices, and I really like not having to use RSLinx or BOOTP.

However, coming from 11 years of AB programming, I still feel it's easier to program A-B from scratch vs. Siemens from scratch.

Written by Chris Wright
Process/Controls Engineer and Freelance Writer

Have a question or comment on this article? Join our community to take part in the discussion! You'll also find all of our courses at




  1. Motion control with an AB system has for more high end capability than siemens. Coordinate systems, multi-axis control/failure mode, and integrated safety options in particular feels more seamless and powerful with AB. Siemens has better auto tuning features however.

    AB has gigabit DLR support in their modern remote IO systems. Their drives don’t unfortunately.

    Siemens typically performs better for small/medium systems (shorter cycle time). AB came a long way with the 5380 series, but is still lagging. Larger systems are a wash between AB/Siemens.

    AB controlflashplus makes it really easy to upgrade firmware across all devices in a system. This is a big win for AB, as firmware upgrades are tedious. A lot of people don’t update firmware as a result.

    License sharing among multiple engineers is another area where AB wins out. You can share and borrow licenses, the grace period resets and gives you 7 days. Siemens licensing is much more painful to share. Hence you need more licenses for the same quantity of engineers.

    Siemens WinCC doesn’t have the template features that Studio View 5000 has. When you do repeat work, AB wins out.

    I find siemens as a preferred platform for blow/injection molding applications. I find AB preferred for systems with advanced motion control. Both are about the same for robotic systems.

    When I use siemens, I tend to use more localized PLCs on a multi-cell system. With AB, I tend to be more comfortable using a single PLC and remote IO panels. This is partially cost, but also tends to be a result of IO speed/program organization/encapsulation/failure modes.

    If a system is IO heavy, siemens has a cost advantage and is faster to set up IO and see things move. If a system has complex logic, then I find AB reduces my logic development time.

    • I agree with your observations; I am still fairly new with Siemens. I can’t remember how AB is, but if PLC tags were changed on a safety PLC can’t upload the changes because it won’t allow F-blocks to be uploaded unless that option was checked in the safety settings. I am running into this issue as we got some equipment that changes were made and it will not let upload.

      As far as WINCC isn’t there a screen template folder were you can import commonly used screens? I know there is the library folder, I have used this for FBs.

    • Thanks for sharing your thoughts and insights @VoteCoffee!

      BTW – I love the name

      @Chris, I’d love to hear more about Turck – never used them myself

      • TurckIO has been my go-to for a long time. They make configurable IO blocks that are robust and cheap (TBEN and FXEN for digital, BLCEN for analog). They also have some really neat din-rail blocks (Turck FEN20) that are phenomenal for adding dry contacts to an external system. I’ve also found that for multiple RFID readers, their gateways and blocks are more cost effective than many alternatives (TBEN-L-RFID/TBEN-S-RFID even have codesys capabilities for advanced filtering).

      • IOLink is winning out in the distributed IO world right now. Balluff has the best IOLink blocks for IO in my opinion. But IFM’s IOLink platform is more capable for IoT implementations than competitors. IFM’s blocks more readily integrate with high level systems for status and lifecycle monitoring, whereas most other block manufacturers have been developing it as a field wiring solution. IFM has been working on getting their costs down to match, but their blocks are not mixed IO (you need separate input/output blocks), which makes it clumsy to deploy unfortunately.

        • I have not heard from Turck, but talked to IFM and I’m hoping to get some of their IO Link products next month!


  2. I found the hardest challenge was there is no auto save feature in Siemens so you have to always remember to save your work. It can make it worse that screen and PLC development are in the same project because you can lose work in both instead of just either PLC or HMI. AB has good recovery

    • I definitely agree with you. I wish Siemens would correlate automatically if there are changes in the CPU.

  3. Hi Chris!
    In your fine comparison you write about changes to HMI in SIEMENS and how to download the changes, have you seen the feature in the TIA16 Online – HMI Device maintenance – Pack & Go?

    kind regards
    Jens Chr. Pedersen

Comments are closed.