
Siemens merges four automation units on 1 October: what changes on your quotation
On 1 October 2026, Siemens collapses four automation business units into one. Customer Services, Factory Automation, Motion Control and Process Automation become a single organisation called Automation, under Rainer Brehm, reporting to Cedrik Neike. If you buy PLCs, drives, HMIs or service contracts, that is one supplier consolidating four price lists, four quotation processes and four support desks into one — three weeks from now.
Reorganisations usually do not belong on a buyer's calendar. This one does, because of who was appointed.
Read the appointment, not the announcement
Siemens' press release of 12 August 2026 gives the reason as the ONE Tech Company strategy and helping customers build "more flexible, productive and resilient production systems". Standard language. The specific fact underneath it is Brehm's current brief: Digital Industries COO for automation and CTO, and in that role, per the release, he has been "driving the strategic development of the company's automation portfolio, including technologies such as software-defined automation and Industrial AI." Before that he was CEO of Factory Automation.
So the executive whose portfolio was software-defined automation now runs the hardware businesses too. Neike's stated reason names the direction outright: "The future of industry lies at the intersection of automation, software and AI."
For procurement that translates into one question. Over the next capital cycle, does a controller stay a part number you buy once and depreciate over ten years, or does it become a licence you renew?
What consolidation does to the number you actually pay
A merged unit changes the commercial surface a buyer negotiates against, and it does not change it in the buyer's favour by default. Four business units meant four sets of targets and, in practice, four places where a deal could be found. One unit means one set.
Here is the mapping, unit by unit, of what moves.
| Business unit folded in | What a buyer typically sources from it | What the merge changes |
|---|---|---|
| Factory Automation | PLCs, I/O, HMIs, industrial PCs | Core hardware; the platform the licence question attaches to |
| Motion Control | Servo drives, motors, CNC | Was quoted separately from the PLC; now the same P&L |
| Process Automation | Process control systems, instrumentation | Different sales motion, now under one president |
| Customer Services | Spares, repairs, support contracts, training | The one that matters most — service leverage now sits inside the same unit that sells you the hardware |
Customer Services being inside the merged unit is the line to underline. When service is a separate business, its revenue depends on being wanted, and a buyer has room to argue that a support contract should be priced on its own merits. When it sits in the same organisation as the hardware, bundling gets easier to propose and harder to unpick.
Nothing in the release says Siemens intends that. The release does not discuss pricing, contracts, headcount or revenue at all. It is an appointment announcement, and it should be read as one. But the structure is now in place, and structure tends to arrive before the commercial policy that uses it.
The figure not to quote
Siemens publishes no revenue or headcount for the new Automation unit. What is published is the group: revenue of €78.9 billion, net income of €10.4 billion, and around 318,000 employees as of 30 September 2025, in a fiscal year that covers Siemens AG entirely — industry, infrastructure, mobility and healthcare, including its majority stake in Siemens Healthineers.
Those are group numbers. Attaching them to the Automation business would be wrong by an order of magnitude and it is the mistake to watch for in the coverage over the next month. Until Siemens reports segment figures on the new structure, the honest statement is that the size of the merged automation business is not public.
What a buyer should do before 1 October
Three weeks is enough time to do the boring work, and the boring work is where the money is.
Pull every open Siemens quotation and note which business unit issued it. Quotations written under the old structure carry the old unit's discount authority, and quotations have validity dates. If something is close to signature and priced acceptably, the argument for closing it before the structure changes is simply that you know what you are getting.
Then look at the service contracts. Find their renewal dates and check whether any of them renew automatically in the fourth quarter. A support agreement that rolls over on 31 December will roll over under a management line that did not exist when it was negotiated.
Third, and this is the one that outlives the reorganisation: ask, in writing, what the licensing model is for any controller you are specifying now. Perpetual, subscription, or perpetual with a subscription for the engineering software. Get the answer on paper and get it into the purchase order, because a controller specified in 2026 will be running in 2036, and a licensing model that changes underneath it is a cost you did not price.
The part worth having a view on
Software-defined automation is usually sold on flexibility — run the control logic on standard servers, decouple it from the hardware, redeploy it where you need it. That is a real engineering benefit and it is not the reason it is happening.
Hardware is a one-time sale into a ten-year replacement cycle. Software is a recurring line. Every automation vendor moving toward software-defined control is moving toward a revenue model with better characteristics for the vendor, and the flexibility argument is true and also convenient. Both things can hold at once.
The buyer's response is not to resist the technology. It is to insist that the flexibility being sold is actually delivered: if control logic is portable, the contract should let you run it on hardware you chose, and if the answer is that it only runs on the vendor's own platform, then what was bought was a subscription with a flexibility story attached. Ask that question in the negotiation, not after the commissioning.
Sources
- Siemens AG, Rainer Brehm Named President of Siemens' Automation Business, press release, Munich, 12 August 2026 — the source of the 1 October 2026 effective date, the four units being merged, the reporting line to Cedrik Neike, both quotations, Brehm's current role, and the FY2025 group figures.
- Drives & Controls, Siemens merges four automation businesses and appoints Brehm as president — trade coverage of the same announcement.
- Siemens at #SPS2025 — 'Software Defined Automation' with Jan Bajorat by Kevin O'Donovan — cited as evidence of how long Siemens has been presenting software-defined automation publicly. Its published summary was read; the interview is not quoted.
- Ep. 232 — Future of Automation with Siemens: Industrial AI, Virtual PLCs, and Digital Twin Factories by Manufacturing Hub — cited for the same reason, from its published description of the Automate booth discussion.
Vesprr Software builds and integrates the systems that sit above the controller — MES, ERP integration, production reporting. If you are specifying automation this quarter and want the licensing terms read before you sign, talk to us.