One environment holds the PLC code, the HMI and SCADA, the drives and the network configuration, which removes the data handoffs between separate tools that cause most integration defects on a Siemens site.
S7-1500 and S7-1200 are the current controllers, with S7-300 and S7-400 on a defined support clock. The right call depends on installed base, the OEM machines arriving on site and the skills the plant already has.
Safety Integrated runs protective functions in a rated fail-safe controller over PROFIsafe, while WinCC provides the operator visibility and the historised record around that safety system.
Siemens SIMATIC is one of the most widely installed automation platforms on Australian process plants, and the engineering for it now runs almost entirely through TIA Portal. This guide is written from the perspective of an integrator who programs and commissions Siemens controllers on local food, beverage and dairy sites. Metromotion Controls is a control systems integrator based in Mount Waverley that delivers Siemens automation projects for manufacturers across Melbourne, Victoria and Australia. That gives us a practical view of where Siemens is the right platform and where the real decisions sit on a brownfield site.
This post supports our PLC, SCADA and HMI programming service, where Siemens STEP 7 and WinCC delivery, PROFINET and PROFIsafe design, and migration of legacy S7 and S5 plant all sit.
The first thing to get straight on a Siemens project is which controller family the work targets, because the platform is broad and includes ranges still in service but out of production.
The current performance controller for plant-scale process control, larger I/O counts, motion and demanding scan times. It is the usual base for a new food or beverage process line with sequencing, batching and safety, and the platform the Siemens engineering model is built around.
The current compact controller for smaller machines, standalone skids and modest I/O. It shares the TIA Portal engineering model with the S7-1500, so code structure and skills carry across between the two.
The previous generation, still running on many Australian sites. S7-300 and ET 200M production has been reported as ended in late 2023, with spares support nominally available for around a decade afterwards, putting these lines on a defined support clock. Confirm current lifecycle dates against the Siemens documentation.
The SIMATIC distributed I/O family that puts I/O in the field, the MCC or at the machine, connected back over PROFINET or PROFIBUS. ET 200SP and ET 200MP are the current ranges and are how most S7-1500 systems reach their field signals.
The practical point is to confirm what is actually on site and what the OEM machines arriving are built on. A plant can easily run a current S7-1500 process controller alongside legacy S7-300 line equipment and packaged machines on S7-1200, all under one engineering environment. Naming the current and legacy parts of the estate accurately is the start of any sensible upgrade or integration plan.
Siemens engineering has consolidated around TIA Portal because it puts the whole automation stack in one project rather than across several disconnected tools. The Totally Integrated Automation Portal holds the controller programming, the visualisation, the drives and the network configuration together, so the parts that have to agree with each other share the same data.
The main tools inside the environment are:
What this buys a team is fewer handoffs. Where the PLC, HMI and drives are configured in separate applications, every tag, alarm and parameter has to be exported and imported across tool boundaries, and each boundary is a place for the systems to drift out of step. In TIA Portal a controller tag referenced on an HMI screen is the same object, an alarm defined once is available to the visualisation, and a drive parameter is visible to the program that uses it. That shared project is where the integration time is saved, the same drawing-aligned discipline behind our PLC programming in Melbourne.
Siemens implements IEC 61131-3, the international standard that defines the programming languages for programmable controllers, so the concepts carry across from any other compliant platform. The skill is choosing the right representation for each task.
The vendor-independent body PLCopen publishes guidance on writing portable, maintainable code against the standard at plcopen.org, worth knowing whichever platform you build on.
The structure of a Siemens program decides whether a site can maintain it. Build it around function blocks with instance data blocks, so a pump, a valve group, a tank or a heat exchanger becomes a reusable block that owns its own logic, state and interlocks and exposes a clean interface. Keep the sequence logic separate from the device blocks, so the recipe can change without rewriting how a valve behaves. Tie tag naming to the P&ID and instrument loop numbers, so a tag on the drawing maps to a tag in the controller. This is the same discipline that turns a P&ID into control logic on any platform, and on the S7-1500 and S7-1200 it fits the optimised data block model, where symbolic access is the default and a block can be extended without shifting every downstream address.
Proving a program against a simulator before site moves the bulk of the debugging off the critical path. PLCSIM runs a simulated S7 CPU on the engineering PC, so the logic and the WinCC HMI can be exercised without controller hardware. PLCSIM Advanced extends this to a virtual controller that an external process simulation model can drive, supporting virtual commissioning against a model of the plant behaviour. Sequences, interlocks, alarms, mode changes and fault handling are driven through the simulator so defects surface where they are cheap to fix, rather than on a live line under startup pressure. Confirm current PLCSIM compatibility with your TIA Portal release in the Siemens documentation.
The WinCC family inside TIA Portal spans operator panel through to plant SCADA, and choosing the right tier early avoids a rebuild later. WinCC is configured in the same project as the controller, so the tags and alarms defined once are shared with it.
The right tier follows the number of clients, the architecture and whether browser-based access matters. A single packaged machine usually needs a Comfort or Advanced panel; a plant-wide supervisory system points toward Professional or Unified. The trade-offs mirror the wider question in our SCADA platform comparison. Confirm the current WinCC positioning and licensing against the Siemens documentation, because the family has evolved.
A Siemens system is built on its network as much as its controller, and on most current designs that network is PROFINET, the Ethernet-based industrial network connecting the controller to distributed I/O, drives and field devices. Older installations often run PROFIBUS, the earlier fieldbus, and a brownfield design frequently has to bridge both during a staged upgrade.
Safety runs on the same physical network through PROFIsafe, the safety communication profile that carries safety-related signals over a standard PROFINET or PROFIBUS network without compromising the safety function. This is what Siemens calls Safety Integrated: a fail-safe controller, an F-CPU, executes the safety program and communicates with fail-safe I/O over PROFIsafe, alongside standard control traffic on the same wires.
Safety functions belong in the F-CPU, kept separate from the standard control program, while WinCC supervises around them. A function that brings the process to a safe state, such as an emergency stop, a guard interlock or a safe-state trip, runs in the F-CPU with its own assessed integrity level and does not depend on the standard control logic or the SCADA layer. WinCC provides the operator visibility, alarm annunciation and historised record that the function performed as designed, but it does not execute the protective action. Whether a fail-safe controller is required, and to what integrity level, is an output of the machine risk assessment rather than a default, and keeping the protective action in the F-CPU preserves the independence the safety system is assessed on.
The following is a deliberately simple, illustrative example, not a real Metromotion Controls project. Consider an HTST pasteuriser skid controlled by an S7-1500: a transfer pump (P-101), a plate heat exchanger, a product-outlet temperature loop (TIC-201) holding the pasteurisation temperature, a hold tube with a flow transmitter (FT-301), and a flow diversion valve (FDV-401). The safety-related function is the divert: if product leaving the hold tube is below the legal pasteurisation temperature, the valve must move it to divert rather than send it forward.
The control program is built in TIA Portal as follows.
The point is the separation. The GRAPH sequence commands the device blocks and reads their feedback, the device blocks know how to run a pump or valve safely, and the safety divert lives in the F-CPU where its integrity is assessed independently. That structure lets the FAT against PLCSIM test the sequence and devices on their own, and lets a technician trace why the skid is holding without the original programmer on the phone.
Most Australian sites are already committed to a platform on at least part of the plant, and the right answer is usually lifecycle fit rather than abstract preference. The broader trade-offs are covered in our PLC platform comparison.
Rockwell is often the better fit where the site is already FactoryTalk and Logix throughout, the maintenance team and integrator network are Rockwell-skilled, and the existing code library and spares sit on that platform. Neither vendor is better in the abstract for an Australian food, beverage or dairy plant; the right call follows what is installed, what the machine fleet runs, and what the site can support. Confirm current Australian Siemens distribution and support arrangements at the time of the project.
The usual trigger for a Siemens migration is supportability rather than performance. The S5 family is long discontinued, and S7-300 with ET 200M is on a published discontinuation path, so a line running it today is on a defined clock, with spares cost and lead time climbing before formal end of support. The right time to plan is when one card failure would turn into a sourcing problem, the same trigger we set out for any legacy PLC migration.
The work is more than swapping hardware. The program moves into the current TIA Portal model, re-expressing older addressing and pointer constructs, including ANY pointer parameters that become VARIANT, and moving toward the optimised block model. The HMI is rebuilt in the current WinCC tier, and the network usually moves from PROFIBUS toward PROFINET, often bridging both during a staged cutover. A converter handles structure and the engineer handles correctness, proven through factory and then site acceptance testing. Our automation upgrades work covers staged migration that keeps a live plant running, line by line where it cannot stop at once.
Siemens is a common platform on local process plants, and the engineering for a dairy or food and beverage site is the same as anywhere, with local standards and hygienic-processing requirements shaping how the work is documented and made safe. The control program has to respect cleaning modes and CIP interaction as part of the logic, and the divert and trip functions that protect product safety are treated as safety functions assessed separately from basic process control. Getting the structure right in TIA Portal, with modular device blocks, GRAPH sequences, safety in the F-CPU and the right WinCC tier proven against PLCSIM before site, decides how the line starts and how easily it is supported.
The descriptions of the SIMATIC platform, TIA Portal, the WinCC tiers, the network and safety profiles, and the IEC 61131-3 languages in this article are general industry and vendor references, cited so the technical claims can be checked against the originals. They are not Metromotion Controls measurements. Confirm current product positioning, version compatibility, lifecycle dates and Australian distribution and support against the Siemens documentation at the time of a project, because these change.
Tommy Kim writes for Metromotion Controls, a Melbourne control systems integrator delivering PLC, SCADA, controls integration and commissioning for food, beverage, dairy and FMCG manufacturers across Australia.
TIA Portal, the Totally Integrated Automation Portal, is the single Siemens engineering framework that holds the tools for the whole SIMATIC automation stack. STEP 7 programs the S7 controllers, WinCC configures the HMI panels and SCADA, Startdrive commissions the SINAMICS drives, and the safety and network configuration sit in the same project. The benefit is that a controller tag, an HMI button and a drive parameter all reference the same project data rather than being maintained in separate disconnected tools. Confirm the exact tool versions and licensing against current Siemens documentation, because the package layout changes between releases.
S7-1200 is the compact controller for smaller machines, standalone skids and modest I/O counts, while S7-1500 is the performance platform for plant-scale process control, larger I/O, motion and demanding scan times. For a new food or beverage process line with several sequences, batching and safety, S7-1500 is usually the right base. For a single packaged machine or a small standalone skid, S7-1200 is often enough. The two share the TIA Portal engineering model, so code structure and skills carry across, which makes a mixed estate manageable.
Both implement IEC 61131-3, so the underlying concepts carry across, but the conventions differ. Siemens organises code around function blocks with instance data blocks and global data blocks for structured storage, programmed in STEP 7 inside TIA Portal, and adds SCL for textual logic and GRAPH for step sequencers. Rockwell uses a tag-based memory model in Studio 5000 with Add-On Instructions for reusable logic. The practical decision for an Australian site is usually to match the installed base, the OEM machine fleet and the in-house maintenance skills rather than to prefer one model in the abstract.
PROFIsafe is the safety communication profile that carries safety-related signals over a standard PROFINET or PROFIBUS network, so safety I/O and a fail-safe controller share the same physical network as the standard control traffic without compromising the safety function. You need a fail-safe controller, an F-CPU, where the risk assessment calls for a safety function with an assessed integrity level, such as an emergency stop, a guard interlock or a safe-state trip. The safety logic runs in the F-CPU and is kept separate from the standard control program. Whether a fail-safe controller is required is an output of the machine risk assessment, not a default.
Yes, as a defined project. Siemens has placed S7-300 and ET 200M on a discontinuation path, with production reported as ended in late 2023 and spares support nominally available for around a decade afterwards, while the older S5 family is long discontinued, so both are migration candidates driven by supportability. Confirm the current lifecycle dates against the Siemens documentation. Migration means moving the program into the current TIA Portal model, re-expressing older addressing and pointer constructs, rebuilding the HMI in WinCC, and proving the result through factory and site acceptance testing. The converter handles structure and the engineer handles correctness, the same as any platform migration.
S7-1500 and S7-1200 support optimised data blocks, where the controller manages the internal memory layout of a block rather than the engineer assigning fixed byte offsets. This makes symbolic access the normal way to work, lets blocks be extended without shifting every downstream address, and generally runs faster on the newer CPUs. Standard, non-optimised blocks still exist for cases that need a fixed absolute layout, such as certain legacy interfaces or absolute addressing into a block. For new work, optimised blocks with symbolic access are the maintainable default.
Yes. PLCSIM simulates an S7 CPU on the engineering PC so logic and HMI can be tested without hardware, and PLCSIM Advanced extends this to a virtual controller with a programming interface that can be driven by a process simulation model, which supports virtual commissioning. Proving sequences, interlocks and fault handling against a simulator before site moves the bulk of the debugging off the critical path. Confirm the current PLCSIM and PLCSIM Advanced version compatibility with your TIA Portal release in the Siemens documentation.
The WinCC family in TIA Portal spans panel HMI through to plant SCADA. WinCC Comfort and WinCC Advanced target operator panels and single-station HMI. WinCC Professional is the SCADA-class option inside TIA Portal for larger supervisory systems. WinCC Unified is the newer web-based visualisation system built on open web technologies for both machine-level and plant-level applications. The right tier follows the number of clients, the architecture and whether browser-based access matters, so confirm the current product positioning and licensing against the Siemens documentation when you scope the system.
PLC logic, SCADA architecture, HMI standards, alarming and historian integration for manufacturing sites.
Modernise legacy PLC, SCADA, HMI and control infrastructure with staged cutover planning.
Controls for dairy processing, milk receival, pasteurisation, CIP and production reporting.
Automation, traceability, CIP, SCADA and production data for Australian food and beverage plants.
Rockwell, Siemens, Schneider, Beckhoff and Omron compared on programming, motion, installed base and support for Australian manufacturers.
The IEC 61131-3 languages and when each fits, maintainable code and sequence design, platform differences, commissioning and version control.
Planning an upgrade without losing production on a live Australian manufacturing site.
Rockwell, Siemens, Schneider, Beckhoff and Omron PLCs compared for Australian manufacturers: programming, motion, installed base, spares and best fit.
Key point
The installed estate usually decides the platform
Published 3 June 2026
A practical ISA-88 batch control guide for Australian food and beverage manufacturers, covering when you need it, the physical, procedural and recipe models, phase states, FSANZ traceability, platform choice and brownfield migration.
Key point
ISA-88 gives batch control a consistent structure
Published 9 May 2026
How a controls engineer reads a P&ID and its ISA-5.1 symbology, then derives equipment modules, sequences, interlocks and control loops from the drawing plus a short conversation about how the plant runs.
Key point
A P&ID carries most of the control design already
Published 3 June 2026
Map out scope, delivery approach and what to have ready before the first conversation. Answer a few questions and Metromotion Controls returns a tailored scoping brief on screen.