In industrial plants, a Siemens PLC rarely operates as a ‘stand-alone programme’. It functions as part of a system: it has configured hardware, a network, I/O modules, and communication with drives and HMI panels, and is also expected to provide diagnostics, predictable response times and stable operation for years to come. That is why the basics of Siemens PLCs do not end with whether someone knows ladder logic. It starts with understanding how the CPU works, how TIA Portal brings the configuration together, and how a project is built so that someone can maintain it after commissioning.
Many beginners quickly fall into the trap of a ‘nice-looking programme’ that works on a desktop but starts to fall apart when deployed on-site. More often than not, the problem lies not in the logic itself, but in the details: the CPU cycle, real-time signal processing, addressing, PROFINET communication, data structures, I/O configuration errors, or a lack of diagnostics. If you want to enter the world of automation professionally, you must treat the basics as a set of commissioning skills, rather than simply knowledge of a single programming language.
What does ‘Siemens PLC’ actually mean in a factory setting?
Siemens PLC usually refers to the SIMATIC ecosystem and the TIA Portal environment. The S7-1200 and S7-1500 families dominate new installations, as they offer a consistent operating model and a straightforward scaling path from small machines to larger production lines. TIA Portal acts as the project hub: you configure the CPU, expansion modules, PROFINET network, tags, programme blocks and, often, the HMI all in one place. From a maintenance and integration perspective, this is a huge advantage, but it also requires an understanding that the ‘program’ is just one layer.
In a factory setting, you will most often encounter a system where the PLC is responsible for sequence logic, safety and interlocks, communication with drives, and collecting status data for visualisation. Even a simple machine today has an inverter, sensors, a valve island, an operator panel and some form of communication with a master system. That is why the basics must cover not only programming, but also what happens ‘around the programme’.
How does a PLC execute a programme, and why does this affect everything?
A PLC operates in a cyclical manner. It reads inputs, executes logic, updates outputs, and handles communication and diagnostics. This operating model influences the system’s response to signals, the implementation of filters and delays, and how edge detection works. Once you understand the cycle, you stop making common mistakes, such as repeatedly ‘capturing’ an event within a single cycle, miscalculating time, or unstable control resulting from a lack of a clear point in the programme where you make a decision.
At Siemens, there is also the matter of organisational blocks, or OBs. These form the framework for programme execution. OB1 usually handles the main cycle, but the system also has other OBs that are event-driven. This is important in practical operation, as certain tasks are better carried out in the appropriate blocks rather than ‘everywhere at once’. If you add diagnostics, interrupts and timed tasks to this, you start to build a programme that behaves predictably, rather than just ‘somehow’.
Project structure at Siemens: OB, FB, FC and DB as the foundation of maintenance
At Siemens, a well-designed project is based on blocks and data from the outset. An OB serves as the programme’s entry point and organises its execution. An FC is a function that does not retain state, so it works well for calculations, data transformations and simple operations. An FB is a function block that has state memory and operates on a DB instance, allowing you to build modules that represent devices and their behaviour.
A database is data. You can store parameters, states, counters, recipes and everything else that needs to survive the programme cycle within it. In practice, a well-designed database and a consistent block structure deliver two benefits. Firstly, the project becomes easier to read, as the device logic is contained within dedicated modules rather than scattered throughout a single main block. Secondly, the project becomes safer to maintain, as a change in a single FB is less likely to cause side effects throughout the entire application.
If you start with a ‘big OB1’, you’ll quickly lose track of the interdependencies. It might work at launch, but the moment there’s a failure, an upgrade or a new feature is added, chaos ensues. From a fundamental perspective, the ability to break an application down into functional blocks (FB) for devices and functions is more important than whether someone writes a beautiful contact layout in LAD.
Programming languages: LAD, FBD and SCL
You will still very often come across LAD in discrete logic. Maintenance engineers prefer LAD because it makes it easy to read interlocks, locks and start conditions. This makes sense, particularly in machinery where logical diagnostics need to be quick. FBD can be useful for simple functional and signal circuits.
SCL, or Structured Text in Siemens, offers an advantage when dealing with data, arrays, recipes, calculations and scaling. In industrial practice, SCL is extremely useful because it allows you to write code that is clear and repeatable, whilst also facilitating the creation of libraries. If you’re thinking about a career in automation, it’s not worth limiting yourself to a single language. A basic understanding of Siemens PLCs means knowing when LAD makes maintenance easier and when SCL shortens the design process and reduces the number of errors.
PROFINET and I/O: you can’t get started without them
In new installations, PROFINET is the standard. The CPU usually acts as the I/O controller, whilst field devices act as I/O devices. Inputs and outputs are often located on I/O islands in the cabinet or in distributed modules. Drives, valve islands, readers, scales and other devices communicate via PROFINET. This means that ‘PLC programming’ without an understanding of the network ends with the project being implemented in the laboratory.
The basics in this area include the ability to configure devices in TIA Portal, assign PROFINET names, set up addressing, and load device descriptions. In a real-world commissioning scenario, common issues include incorrect device names, address conflicts, modules that do not match the configuration, or topology problems. Without online diagnostics, it is easy to spend hours searching for a fault that stems from a single parameter.
It’s also worth remembering that I/O isn’t just about ‘assigning bits’. What matters are filtering times, contact bounce, signal speeds, and—in analogue systems—scaling, filtering and fault detection. Fundamentally, you need to be able to configure the signal so that it doesn’t generate false events or disrupt sequences.
Diagnostics and commissioning: this is where most of the work takes place
In a sprint, it’s not usually the person who writes code the fastest who wins. The winner is the one who can diagnose and understand what the system is doing at any given moment the quickest. That’s why the basics must include online tools: tag monitoring, watchlists, module state checks, cycle time analysis, and the judicious use of forcing. Forcing is a powerful and dangerous tool, so it requires discipline. It is used to recreate conditions and check the programme’s response, not just to ‘make it work’.
Good practice is for the programme to indicate what is happening. If the device fails to start, the operator and maintenance engineer should be able to see whether it is blocked by a fault, a lack of acknowledgement, the drive not being ready, a lack of pressure or some other condition. This means that, right from the ground up, you need to plan status bits, diagnostic signals and simple ‘why it isn’t working’ mechanisms. Without this, every start-up becomes a hunt for a single bit amongst several hundred tags.
The minimum standard for a first application that makes sense in a factory
If you want to build your first application in Siemens so that it resembles real-world operation, design it as a small part of a machine. Create a structure using FB for the function, add a DB for parameters and statuses, and organise the logic in a way that can be diagnosed. A practical example is drive control with a start and stop sequence, interlocks, confirmations, timers and fault handling.
In this application, you’ll learn the entire process: from I/O configuration, through logic, to online diagnostics. You’ll also learn how to work with states, as the sequence requires you to keep track of the stage and reset it correctly. This is exactly the kind of skill that’s useful from day one at a control room or an integrator.
How can you study without getting stuck on the basics?
The most common pitfall is learning individual instructions without understanding the operational context. In a factory, nobody cares whether you know fifty function blocks. What people care about is whether you can start up the machine, identify the cause of a stoppage, correct the sequence, and ensure that process safety isn’t compromised.
That is why a sensible learning path should follow a series of tasks: discrete control, analogue control, communication and simple visualisation. In each task, you should practise troubleshooting and ensuring your code is easy to read. If you get into the habit of creating modules, status indicators and clear blocking conditions right from the start, you will find it easier to tackle larger projects later on.
Summary – Siemens PLC basics
The basics of Siemens PLCs are a set of skills that ensure reliable commissioning and maintenance, rather than just ‘working code’. You need to understand the CPU cycle, the structure of OB/FB/FC/DB blocks, data handling and online diagnostics. You also need to understand PROFINET and I/O configuration, as these form the backbone of most installations.
Once you’ve mastered these basics, the programming language becomes a tool rather than an end in itself. That’s when LAD, FBD and SCL start working for you, rather than against you. And then your first application won’t be a ‘training project’, but something that actually resembles what happens in a real-world setting.
