Industrial Automation and Industrial Software: History, Value Chain, Markets, and Challenges

Tue, 06 Oct 2026 00:00:00 +0000

Sources current to 5 October 2026

Global scope, with emphasis on China, Europe and the United States. Market measures retain their exact regions, periods, currencies and definitions. Supporting Evidence appears in a separate appendix after Parts 1–4.

Part 1: Industry Story

On 5 October 2026, Schneider Electric and PTC announced that they had signed a definitive acquisition agreement. The proposed cash price was US$205 per share, valuing PTC's equity at approximately US$22.6 billion. A supplier with automation and operations software was seeking to acquire a company whose products manage engineering and product information. The announcement offers a concrete way into a larger industry question: what changes when the information used to design a product is connected to the systems used to make it? The agreement was an announced transaction at this report's cutoff; completion is not assumed. [E025, E003, E008, E009]

The products make the connection concrete. PTC describes Windchill as a system for product data, lifecycle collaboration and controlled changes, including information from multiple CAD tools. AVEVA, whose remaining shares Schneider acquired in 2023, offers operations software for visualizing equipment, collecting process records and supporting operational decisions. One helps establish and manage what a product is supposed to be. The other helps people understand how an operating process is behaving. Linking those responsibilities is a manufacturing problem with a software and automation business built around it. [E009, E003, E008]

Consider an engineering change as an analytical example. A revised product definition may require a different production instruction, inspection requirement or machine configuration. The useful outcome is a controlled path through those changes: the relevant people see the approved information, the right system executes it, and the factory can trace what happened. A single corporate owner could make some coordination easier, but ownership alone supplies none of those operating results. Models, interfaces, permissions, testing and responsibility still have to align. This example explains the workflow; it does not describe an undisclosed Schneider or PTC customer project. [E007, E009, E013, E016]

The industry's central question follows: who can carry engineering information into reliable production, and maintain that connection as products, equipment and security requirements change? The answer involves a long history of translating information into machine actions, a value chain spanning chips to factory operations, and commercial models that reward different kinds of delivery and support. This report follows that sequence. Its global comparison concentrates on China, Europe and the United States, while keeping narrower statistical regions and product categories explicit.

Part 2: Industry History

Putting motion into instructions

A useful starting point is the moment when a machine's movements could be described as information. In a 1959 MIT programme, researcher J. Francis Reintjes traced the demonstration of numerical-control feasibility to 1952. Encoded numbers on punched tape directed electronic equipment and servomechanisms that moved a machine tool. Douglas Ross then explained APT, which translated descriptions of part geometry and tool movements into machine instructions. The important connection was already visible: engineering information could become a sequence of physical operations. [H001]

We can see the beginnings of a recurring division of labour here. The machine, its motion equipment, the programming system and the person translating manufacturing requirements into instructions each contributed something different. Better hardware alone could not remove the work of describing the part and preparing its operations. This helps explain why industrial software developed alongside machinery: the useful product was a working route from design requirements to repeatable execution, with expertise needed at the boundaries. [H001]

Computer drawing developed a complementary route. Ivan Edward Sutherland's January 1963 dissertation described Sketchpad, in which a light pen let a user draw and modify objects on a display. The system stored relationships, reused symbols and applied geometric conditions such as parallel lines. This research example matters because engineering information could carry relationships that changed with a drawing. It was an early technical demonstration, rather than evidence that a commercial CAD market was already established. [H010]

Making factory control reconfigurable

Programmable control extended this principle to the logic governing factory equipment. Schneider Electric's 2019 retrospective dates Modicon's conception to 1968 and describes General Motors' demand for a more flexible alternative to relay wiring. Dick Morley's team developed the Modicon 084, allowing functions to be changed through programming without rebuilding the relay connections. The historical significance lies in moving part of the change process into software. It created a continuing role for controller programming, commissioning and maintenance around the physical equipment. [H002]

Process plants developed another important control architecture. Yokogawa's anniversary account records the announcement of CENTUM in June 1975 and describes its early use of microprocessors and a CRT interface. We can read this DCS milestone as an expansion of the commercial task: suppliers needed to support monitoring and control across a plant, bringing equipment, operator interfaces and engineering together. These capabilities still occupy distinct positions in the industry. Making control programmable also increased the importance of preserving the knowledge embedded in a configured system when a plant later changed or expanded. [H002, H003]

A Ferranti Argus 500 computer system in Edinburgh, photographed in 1980.
Photo: Leocapaldi · Wikimedia Commons · Public domain (author's release). Original linked above; web copies resized and converted to WebP, without cropping.

Building product and production models

The engineering side was changing too. PTC's product history records the launch of Pro/ENGINEER in 1988. Parameters, constraints and associative updates allowed design intent to be carried within a three-dimensional model, so a change could propagate through related elements. This was one company's milestone in a much longer CAD history. Its relevance today is the growing value of the model itself: engineering software became a place to maintain relationships and decisions, which could become as consequential to a manufacturer as the drawing or final physical component. [H004]

PTC introduced Windchill in 1998, using a shared web architecture for lifecycle collaboration. The scope widened from creating a design to coordinating product information across teams. Manufacturing operations needed another kind of shared model. ISA's committee history dates the first publication of ISA-95 to 2000: Parts 1 and 2 defined enterprise–control exchanges and their framework, while later parts formalised manufacturing operations management at level 3. These were logical integration boundaries, giving different systems a clearer way to describe their responsibilities and information. [H004, H006]

This history helps explain today's separate CAD, PLM and manufacturing-operations markets. They grew around different decisions, users and information structures. Connecting them requires agreement on what a product, resource or production operation means, as well as a technical interface. We therefore see migration and integration as work on accumulated models and practices. Moving files or buying a new application addresses only part of that work; the business value depends on preserving useful relationships across the workflow. [H004, H006]

Connecting systems and renewing software

Interoperability became an explicit collective project. The OPC Foundation traces its standards activity to 1996. Its joint group with PLCopen began in 2008, and a controller client specification followed in 2014, supporting exchanges between controllers and with systems such as MES and ERP. The significance was a common route across suppliers and system levels. That route still required implementation and integration. Standardised communication and information models still needed to be matched to the meaning, quality and use of data in a particular plant. [H005]

Germany's Industrie 4.0 initiative, launched in early 2011, gave this integration ambition a broader policy framework. The April 2013 working-group report called for horizontal integration through value networks, engineering integration across the value chain, and vertical integration of networked manufacturing. Those were recommendations requiring further research and implementation. We can see why platform strategies later became attractive: the proposed value depended on connecting previously separate activities. It also made standards, system complexity and the installed factory important to the commercial proposition. [H007]

Licensing changed alongside this wider scope. PTC announced in January 2018 a broader subscription-only policy for new core-software and ThingWorx licences from January 2019, following a January 2018 transition in the Americas and Western Europe. China and several other markets remained exceptions; existing perpetual licences stayed usable, and Kepware retained both forms. Subscription created a continuing renewal relationship, changing how access, upgrades and spending could be organised. It did not by itself determine where software ran. This distinction remains central when comparing recurring revenue with cloud deployment. [H008]

Bringing AI into industrial engineering

On 31 October 2023, Siemens and Microsoft introduced Siemens Industrial Copilot, a jointly developed generative-AI assistant for manufacturing. The announcement described generating, optimising and debugging automation code by combining industrial information with Azure OpenAI Service. The engineering workflow became a meeting point for control expertise and cloud AI capabilities. We can interpret this as another extension of the industry's long-running effort to translate intentions into usable instructions, with a new method for interacting with the information and software already involved. [H009]

The resulting industry carries several generations of capability at once. Motion and control equipment remain necessary; product and operations models organise decisions; interoperability connects them; licences and services shape the ongoing commercial relationship. AI adds another engineering capability within this accumulated structure. Our reading of the history is that competitive value depends on making these layers work together through actual manufacturing changes. That explains the continuing importance of component suppliers, software specialists, platform companies and integrators, each serving a different part of the same practical task. [H001, H002, H003, H004, H005, H006, H007, H008, H009]

Part 3: Market Landscape

The value chain begins with a physical measurement

Industrial automation turns measurements into actions: a sensor detects a condition, a controller evaluates it, and a drive or actuator changes the physical process. Industrial software also defines the product, tests its design, schedules and records production, and manages changes across its life. The useful industry boundary therefore follows the manufacturing workflow. It includes components, control systems, engineering and operations software, robotic equipment, machine integration and factory use. This is the working scope of this report; individual market statistics below retain their publishers' definitions. [E004, E006, E007, E020]

Upstream suppliers make the ingredients of an automation system. Texas Instruments lists analog and embedded devices for sensing, communication, motor control and power conversion. SICK's 2022 business description covers sensors, cameras and encoders; Inovance's product directory includes AC drives, servo drives and motors. Their immediate customers can be equipment and system manufacturers rather than the final factory alone. These examples establish product roles, without establishing a procurement relationship between any two named companies. [E004, E005, E021, E023]

The value of this layer is application fitness. A sensor must capture the relevant physical signal, a processor must handle the required computation, and a drive must work with the selected motor and machine. In our analysis, a lower component price creates value only if qualification, replacement availability and engineering work remain acceptable over the equipment's service life. NIST's discussion of long-lived operational technology explains why support and compatibility belong in the purchasing decision. The available product descriptions do not measure global component shortages or any country's import dependence. [E004, E005, E013, E021]

Control, operations and engineering solve different tasks

In the middle of the chain, PLCs execute machine logic and motion tasks; distributed control systems coordinate process operations. Siemens' 2024 SIMATIC S7-1200 G2 announcement describes TIA Portal engineering and motion functions. SUPCON describes the ECS-700 DCS within an architecture of instruments, I/O, operator and engineering stations, process records and related systems. Inovance's H5U PLC provides another disclosed machine-control example. A comparison between these products must start with the process and required control functions, rather than treating every controller as a substitute for every other controller. [E006, E019, E024]

A WAGO controller in a pharmaceutical monitoring setup, photographed in 2016.
Photo: Pierre75000 · Wikimedia Commons · CC BY-SA 4.0 International. Original linked above; web copies resized and converted to WebP, without cropping.

Above the immediate control task, HMI and SCADA present operating conditions, while historians preserve process data. AVEVA Operations Control packages visualization, historian, reporting and communication tools with subscription entitlements. MES addresses production execution: recipes, work in progress, quality, material tracking and product genealogy. Rockwell places this software between enterprise systems and shop-floor controls and identifies FactoryTalk ProductionCentre and Plex as examples. For the factory, the commercial question is whether the software can make production information usable at the point of a decision, and whether its interfaces and support fit existing operations. [E007, E008]

Engineering software acts earlier in the workflow. CAD models product geometry; simulation tests engineering behaviour; PLM governs product information, revisions and change processes. Dassault Systèmes assigns these roles to CATIA, SIMULIA and ENOVIA, and describes DELMIA across manufacturing planning and execution. PTC's Windchill manages lifecycle data and collaboration, including multi-CAD information and change traceability. The economic asset here is the accumulated product definition and the work built around it. We infer that migration must preserve usable relationships and revision history, in addition to transferring files; this is a consequence of the disclosed functions, not a measured switching-cost estimate. [E009, E020]

Robotic equipment occupies another middle-chain role: it carries out physical manufacturing tasks under a configured control system. Inovance's portfolio includes industrial robots as well as drives and controllers, showing how a supplier can span several branches. A machine builder or factory engineering team must turn the equipment into an application. Our commercial analysis separates the robot delivery from tooling, programming, cell integration and ongoing support; the agreed contract determines which party provides each. The map below separates functions so that a broad company portfolio is not mistaken for a single product market. It also includes named examples of a machine builder and a factory user, rather than assuming that a robot sale completes an entire production system. [E021, E023, E012]

Stäubli industrial robots on a manufacturing line, photographed in January 2023.
Photo: Clemenspool · Wikimedia Commons · CC0 1.0. Original linked above; web copies resized and converted to WebP, without cropping.

INDUSTRY MAP

Industrial automation and industrial software: the value chain

Global representative products and users. Expand a branch to explore the four levels: industry, stage, function, and company or product.

Read the full text outline

Industrial Automation and Industrial Software
- Upstream
  - Semiconductors
    - Texas Instruments analog and embedded chips [E004]
  - Sensing and machine vision
    - SICK sensors, cameras and encoders [E005]
  - Drives and motors
    - Inovance AC drives, servo drives and motors [E021]
- Midstream
  - PLC and distributed control systems
    - Siemens SIMATIC; SUPCON ECS-700 DCS [E019, E006]
    - Inovance H5U PLC [E024]
  - HMI, SCADA and process data
    - AVEVA Operations Control [E008]
  - Manufacturing execution systems
    - Rockwell FactoryTalk ProductionCentre and Plex [E007]
  - CAD and engineering simulation
    - Dassault Systèmes CATIA and SIMULIA [E020]
  - Product lifecycle management
    - PTC Windchill; Dassault Systèmes ENOVIA [E009, E020]
  - Manufacturing planning and operations
    - Dassault Systèmes DELMIA [E020]
  - Industrial robotic equipment
    - Inovance industrial robot portfolio [E021]
- Downstream
  - Machine building and integration
    - thyssenkrupp Automation Engineering [E012]
  - Factory operations
    - Siemens Electronics Factory Erlangen [E012]

Connections classify product roles; they do not establish procurement contracts. Companies may appear in several roles. Evidence cutoff: 5 October 2026.

Sources: E004 · E005 · E021 · E019 · E006 · E024 · E008 · E007 · E020 · E009 · E012. Reviewed 2026-10-06.

Figure 1. Industry value chain: global representative products and users. The hierarchy is industry → upstream, midstream and downstream → functional segment → company or product. Source references appear at the leaves; branches classify roles. A company can supply equipment and software while also operating its own factory. [E004, E005, E006, E007, E008, E009, E012, E019, E020, E021, E024]

Download printable map (SVG) · Download map nodes (CSV)

The downstream customer buys a working production process

Machine builders and integrators connect mechanical equipment, control programs and information flows for an application. Factory operators then run, maintain and modify the resulting assets. Siemens' November 2024 release identifies thyssenkrupp Automation Engineering as a special-machine and plant builder using its engineering copilot in a battery quality-inspection machine. The same release describes an operations-copilot application on soldering machines at Siemens' Electronics Factory Erlangen. These are distinct positions in the chain, even though a common supplier supports both. The disclosure verifies the applications; it supplies no independently audited payback period. [E012]

Business models consequently follow different deliverables. A component supplier provides devices; a controls supplier combines equipment with engineering tools and support; an engineering-software vendor licenses software supporting a workflow; and a service organization provides agreed implementation, maintenance or continuing support. AVEVA explicitly offers subscription software across on-premises, cloud and hybrid deployments. PTC's licensing transition also left existing perpetual rights intact. Subscription describes a payment and entitlement relationship; deployment describes where the software runs. Keeping these dimensions separate is essential when comparing commercial offers. [E008, H008, E104]

For the buyer, our suggested comparison is the cost of the complete operating workflow: equipment and licences, integration and validation, training, support, future changes and a feasible exit. For the supplier, the corresponding questions are what is delivered once, what must be maintained over time, and which party bears the cost of an implementation problem. This framework explains why recurring revenue can coexist with substantial engineering work. It also explains why a vendor's software label cannot, on its own, establish either its profit margin or the customer's total cost. The segment disclosures later in this section provide concrete accounting evidence. [E008, E013, E104]

Market size depends on what is being counted

The available evidence describes several substantial markets. Three figures are useful because each points to a different source of demand: engineering software used to develop products, industrial-software product revenue reported in China, and control systems sold into Chinese process industries. Their boundaries need to remain visible when discussing market size. [E207, E208, E201]

Scope and source	Statistical year; amount	Published growth
Global broad PLM economy — CIMdata estimate	2025; USD 88.3bn	+9.9%
China industrial-software products — MIIT	2025; RMB 333.0bn	+9.7%
China DCS — MIR estimate	2024; approximately RMB 11.76bn	−3.6%

These are separately defined revenue/value measures, in their original currencies. They are not components of a combined total. Sources: [E207, E208, E201].

CIMdata’s PLM definition stretches well beyond a product-data-management application. It includes engineering tools such as mechanical CAD, CAM, simulation and analysis, electronic-design automation and architecture/engineering/construction software, alongside innovation platforms and digital manufacturing. Its release identifies notable growth in EDA and AEC. This helps explain why a broad engineering-software economy can grow for reasons extending beyond manufacturers’ spending on shop-floor systems. China’s MIIT product-revenue category covers a different geography and statistical boundary; DCS includes hardware, software, services and engineering. Adding the three amounts would therefore mix different years, overlap software categories and combine unlike businesses. [E207, E208, E201]

MIIT reports RMB 333.0bn of industrial-software product revenue for 2025 and growth of 9.7%. Its earlier 2024 release reported RMB 294.0bn. Dividing those two published amounts produces approximately 13.3%: (333.0/294.0 − 1) × 100. The basis for reconciling those amounts with the official growth rate has not been established here, so 9.7% remains the cited growth rate and the two releases are not turned into a continuous growth chart. [E208, E209]

MIR’s public DCS estimate offers a different competitive signal: a market can contract while an established domestic supplier retains a substantial position. The excerpt places SUPCON at 40.4% of China’s 2024 DCS market, whose delivered offering includes services and engineering. This attributed estimate identifies a specific process-control position; it does not establish supplier profitability or individual system prices. [E201, E202]

Different regions, different installation cycles

Industrial-robot installations provide a cleaner physical comparison across regions. IFR reports that global additions exceeded 600,000 in 2025, up 11%. China expanded faster than that global pace, the United States also grew, and EU27 installations fell. These figures describe new industrial robots installed during the same calendar year, making the direction of demand comparable even though the regions differ greatly in population and manufacturing scale. [E204, E205, E206]

Market	2025 new installations (units)	Year-on-year change
China	354,000	+20%
United States	38,400	+12%
EU27	60,500	−11%

IFR public releases. US value follows the country-specific release; the global summary says almost 38,500. EU27 is not all Europe. Counts retain published precision. Sources: [E204, E205, E206].

China represented 59% of global deployments according to IFR. Chinese suppliers installed 195,000 units in their home market, up 15%, but their category share fell from 57% to 55% as total Chinese installations grew faster. The point is economically useful: increasing domestic suppliers’ volume can coexist with a lower share of a faster-growing market. The evidence does not identify a single cause, such as price, quality or policy, for that change. [E204]

INDUSTRIAL ROBOT SUBMARKET · Calendar 2025

Annual new industrial-robot installations, grouped by supplier origin. IFR reports approximately 354,000 installations in China in 2025.

China · Share of annual new installations (%)

View the data table

China industrial-robot installations by supplier origin · Calendar 2025 · Share of annual new installations (%)
Supplier origin	Share
Chinese suppliers	55%
All other suppliers	45%

Download data (CSV)

IFR directly reports Chinese suppliers at 55%; all other suppliers = 100% − 55% = 45%. Percentages retain the published integer precision. These are shares of installations in a named submarket, not global automation or software revenue, or individual vendor shares. [E204]

Source: International Federation of Robotics (IFR) — Five Million Robots now Operate in Factories Globally (2026-09-24). Reviewed 2026-10-06.

Figure 2. China industrial-robot installations by supplier origin, 2025: Chinese suppliers 55%; all other supplier origins 45%. The second category is calculated as 100% − 55%. Denominator: annual new installations in China; source: IFR [E204].

The chart is a supplier-origin split, not a ranking of individual robot manufacturers. It also counts installations rather than sales revenue: a unit installed in one application need not have the same selling price or integration cost as a unit in another. Its value is to show how much of China’s annual deployment is supplied by the domestic category, without pretending to measure the whole value captured by automation suppliers. A common vendor-share denominator covering this report's combined global scope was not established in the reviewed public evidence. ARC/Control's automation definition, for example, excludes robotics and several other categories. The chart consequently uses the explicitly defined robot submarket and installation measure. [E204, E212]

The United States illustrates the distinction between robot manufacturing and deployment capability. IFR describes many domestic system integrators, while saying that most robots are still imported from Japan and Europe. Automotive remained its largest customer sector, with 13,500 installations, down 1%, even as total installations rose 12%; food and beverage grew 30% to 2,900. Those figures support a reading of demand spreading beyond the largest established customer sector, rather than an automotive-led explanation for all growth. [E205]

EU27 presents a large installed base with weaker new investment. Its operating stock reached 712,000 units at year-end 2025, while new installations fell 11%. Automotive additions declined 25% to 14,900 and metal-industry additions 13% to 13,000; food and beverage increased 4% to 5,300. This sector pattern helps explain the aggregate decline without claiming that it exhausts the causes. Germany accounted for 41% of EU27 installations, making the largest national market particularly important to regional equipment demand. A declining annual flow does not erase the existing base that may need maintenance, integration and upgrades; that last implication is an analytical inference, not a measured service-market estimate. [E206]

Reading company results through their business models

Recent company disclosures show where growth and profit appeared within large suppliers. Siemens and Rockwell report fiscal third quarters ending 30 June 2026; Schneider’s comparison below uses the six months ending on that date. Each operates globally, so these are company operating results rather than indicators of demand in its home country. [E101, E102, E105]

Business; reporting period	Revenue and growth	Profit and recurring-business measures
Siemens Digital Industries; Q3 FY2026	EUR 4.9bn; +10% comparable. Software subset EUR 1.8bn; +15%.	Segment profit EUR 923m; margin 18.7%. ARR EUR 5.7bn; +11% organic.
Rockwell Software & Control; Q3 FY2026	USD 751m; +19% reported/+18% organic.	Segment operating earnings USD 261m; margin 34.8%. Group organic ARR +6%.
Schneider Industrial Automation; H1 calendar 2026	EUR 3.585bn; +7.7% organic.	Adjusted EBITA EUR 501m; margin 14.0%. AVEVA ARR +11% at 30 June.

Currencies and reporting periods remain separate. Schneider’s Q2 Industrial Automation growth was 11% organic [E103]; the table uses H1 amounts from E105. Profit measures are company-defined; group ARR and AVEVA ARR are labelled separately. Sources: [E101, E102, E103, E105].

Siemens provides a direct link between the software contribution and segment profitability: Digital Industries’ profit rose 44%, and the company identified software as the largest contributor to the improvement. The segment margin rose from 14.5% to 18.7%. Orders were EUR 4.9bn, up 9% comparably, alongside revenue of the same rounded amount, up 10%. Orders indicate incoming business; revenue records what was recognized in the quarter. ARR supplies a separate view of recurring business. Their different growth rates describe different commercial stages, rather than three versions of the same sale. [E101]

Rockwell permits a useful comparison within one company and quarter. Segment operating margins were 34.8% in Software & Control, 20.0% in Intelligent Devices and 15.1% in Lifecycle Services. Its filing describes predominantly point-in-time product revenue in Intelligent Devices, a product/software combination in Software & Control, and predominantly over-time solutions/services revenue in Lifecycle Services. Large systems and services are mainly sold directly; products also rely on distributors. Our interpretation is that product reuse, engineering delivery and the timing of contract performance create different operating demands, so an automation supplier needs more than one earnings model. [E102, E104]

Higher volume was Rockwell’s stated main driver of Software & Control margin improvement. Strong project execution and the Sensia dissolution benefited Lifecycle Services’ margin despite lower sales. Schneider similarly reported support-function cost leverage while Industrial Automation’s gross margin slipped slightly because productivity and pricing did not fully offset raw-material inflation and tariffs. Its adjusted EBITA margin nevertheless improved from 13.7% to 14.0%. These disclosures show why revenue growth and margin movement need separate explanations; they do not isolate software subscriptions as the sole cause of profitability. [E102, E105]

Contract indicators add another dimension. Rockwell disclosed about USD 1.375bn of remaining performance obligations, of which about USD 820m was expected to become revenue within 12 months. The measure excludes specified short contracts, invoice-based services and unexercised renewals. Its ARR instead represents the annual contract value of active recurring contracts and is expressly separate from revenue, contract liabilities and backlog. A growing ARR can help track a recurring relationship; RPO can help assess committed work still to be recognized. Neither alone supplies a complete forecast of future sales or cash. [E102, E104]

Schneider’s Industrial Automation business also grew unevenly by geography: H1 organic growth was 5% in North America, 7% in Europe and 12% in China and East Asia. The company associated Chinese growth with discrete automation, packaging/material handling and improving OEM activity, while AVEVA contributed across regions. These are segment-specific explanations for 2026 sales, alongside the different 2025 robot-installation cycle. Read together, the evidence points to a market whose direction depends on application, geography and how the supplier earns and recognizes revenue. [E105, E204, E205, E206]

Competition moves across the workflow

The competitive landscape has three overlapping forms. Controls companies can add engineering and operations software to their installed equipment base. Software specialists can deepen the product model or manufacturing workflow. Integrators can combine products from different suppliers for a particular process. These positions are visible in the portfolios and applications above. In our analysis, the practical dividing line is where a supplier takes responsibility: an interface, a software task, a configured machine or a continuing production outcome. Portfolio breadth and implementation responsibility should therefore be assessed separately. [E006, E007, E008, E009, E012, E020]

Completed acquisitions show established suppliers extending that scope. Schneider Electric completed the purchase of the AVEVA shares it did not already own on 18 January 2023. Emerson completed its purchase of the remaining AspenTech shares on 12 March 2025, making it a wholly owned subsidiary within Control Systems & Software. Siemens completed its Altair acquisition on 26 March 2025 for an enterprise value of approximately US$10 billion, adding simulation, high-performance computing, data science and AI capabilities. These transactions have different histories; in particular, buying remaining shares is a change from an existing ownership position. [E003, E002, E001]

The strategic attraction is a broader route from engineering decisions to operating information. Our interpretation is that a connected portfolio can reduce handoffs if models, permissions and change processes actually align. It can also concentrate dependency in one supplier and create a larger migration task when a customer changes platforms. Acquisition announcements establish ownership and stated intentions; the buyer still needs evidence of compatible versions, usable interfaces, support terms and application-level results. The disclosed transactions do not supply a common measure of global industry concentration. [E001, E002, E003, E009, E016]

For a supplier, this makes the renewal and expansion of a working customer process a useful test of competitiveness. For a customer, it makes continuity through the next product change, equipment upgrade or security update a useful test of value. These are our proposed evaluation criteria, rather than a ranking of companies. They connect the regional demand and segment economics above to the central industry question: which supplier can carry engineering information into dependable production while keeping the system supportable over time? [E009, E012, E013, E104]

Part 4: Industry Challenges

Existing factories make verification part of the product

A factory upgrade must fit a process that already works. NIST's OT security guidance describes requirements for predictable response, safety and continuity, alongside legacy systems that may run unsupported operating systems. Routine rebooting can be unsuitable, and software changes require testing and staged implementation. The resulting challenge extends beyond installing a newer application: a change in communications, controller software or equipment behaviour can affect production and safety together. In our assessment, the scarce resource in a brownfield project is often a controlled opportunity to verify the whole workflow, including its response when a component fails. [E013]

A practical approach is to document dependencies, test changes away from the live process where feasible, agree an acceptance window, and prepare recovery steps before deployment. Buyers also need a support plan covering controller firmware, operating systems, application versions and available engineering expertise. These are analytical recommendations derived from the operating constraints, rather than a universal installation recipe. A test environment may omit physical conditions present in production; a successful trial therefore reduces uncertainty without removing the need for site acceptance. Support commitments also have to survive future version changes and changes of supplier. [E013]

Interoperability needs meaning, permission and responsibility

The OPC Foundation describes OPC UA as a framework combining communications, information models and access mechanisms, with authentication, encryption and auditing. IDTA's 10 June 2025 AAS announcement adds fine-grained access control for properties, submodels and registry or repository services. These mechanisms offer a useful route through a basic integration problem: two systems may exchange a value yet interpret its identity, units, revision or permitted use differently. Their availability in a standard establishes a design path; implementation in a particular product and agreement between particular systems still require verification. [E016, E017]

Our proposed starting point is a bounded workflow, such as carrying an approved engineering change into production records. PTC describes Windchill's multi-CAD management, controlled product changes and traceability, giving that workflow an identifiable information-management role. Implementation then needs agreed identifiers, version rules, authorized users and responsibility for exceptions. Technical permissions can restrict access to selected fields, while contracts must establish who may retain, reuse or transfer the data. Neither layer resolves every semantic disagreement. Buyers should therefore assess export and migration arrangements alongside the interface demonstration, with validation costs included in the commercial decision. [E009, E016, E017]

AI assistance shifts work towards review and verification

Siemens and Microsoft introduced Industrial Copilot on 31 October 2023 with functions for generating, optimizing and debugging automation code. Siemens' November 2024 release described a thyssenkrupp Automation Engineering battery-inspection machine using the engineering assistant, and an operations assistant used on soldering machines at Siemens' Erlangen factory. These vendor-disclosed applications show where assistance enters engineering and maintenance. The difficult transition is from a plausible answer to an approved machine change: code must fit the controller, process sequence and failure conditions, while maintenance advice must match the installed equipment and current documentation. [H009, E012, E013]

We would evaluate an assistant through a reviewed workflow: identify its information sources and versions, restrict access, test proposed code, and retain human approval for deployment. Evaluation should count review time, integration, computing and ongoing support alongside time saved in drafting. Rockwell's filing distinguishes product, software and services delivery, a reminder that the commercial package extends beyond an assistant's licence. The cited AI announcements provide no independently measured return on investment. A useful pilot should consequently measure accepted work and its total cost at the customer site, including corrections, rather than treating the volume of generated code as the outcome. [H009, E012, E013, E104]

Security duties continue after installation

Europe's Cyber Resilience Act gives lifecycle security a concrete timetable. Reporting obligations began on 11 September 2026: the Commission describes an early warning within 24 hours of awareness and full notification within 72 hours for relevant actively exploited vulnerabilities and severe security incidents. These are reporting deadlines. The main product obligations apply from 11 December 2027. Application depends on the product and statutory scope, so a manufacturer needs to establish its actual role before assigning responsibilities. The operational consequence is already clear for covered reporting: someone must recognize an incident, gather information and escalate it in time. [E014, E022]

NIST's recommended segmentation, authorized communications and OT-specific training provide practical engineering paths. Our analysis is that these measures work best when linked to maintenance ownership and recovery procedures: a restricted network still needs necessary production traffic, and trained staff still need access to current equipment information. China's AI + Manufacturing policy, published on 7 January 2026, similarly emphasizes industrial reliability, safety, data governance and evaluation, with objectives for 2027. Those objectives indicate policy direction. Project results must be assessed separately through operating evidence, with responsibilities and validation suited to the process in each jurisdiction. [E013, E015]

Supply choices and delivery economics meet at acceptance

Industrial software depends on physical equipment. Texas Instruments describes sensing, communications, motor-control and power-conversion components; Inovance lists drives, motors, controllers and interfaces. These product roles help locate dependencies, while establishing neither a particular supplier relationship nor a current shortage. Our supply-chain analysis therefore starts with qualification: replacing a component or drive may require checking electrical behaviour, interfaces, software compatibility and support arrangements. Alternative suppliers can create options, but each qualified configuration takes engineering work. Procurement should weigh that work against price and availability instead of assuming that products in the same category are interchangeable. [E004, E021, E013]

Delivery economics differ across the chain. Rockwell's quarterly filing for the period ended 30 June 2026 describes product revenue recognized predominantly at a point in time for Intelligent Devices, a product-and-software mix in Software & Control, and mainly over-time solutions and services in Lifecycle Services. In our assessment, reusable software and standard configurations can spread development work across customers, while site integration, acceptance and continuing support consume resources with each deployment. Revenue-recognition categories alone establish neither cash timing nor software-only profitability. A sound decision therefore asks what will be accepted, who will maintain it, how a change will be verified, and what the full supported workflow will cost. [E104, E013]

Appendix: Supporting Evidence

Each record identifies the claim, source, dates, statistical scope and limits. Company disclosures establish what the company reports; third-party estimates retain their original definitions. The evidence cutoff is 5 October 2026; verification includes reading on 6 October. Original research materials are linked to their publishers.

Download the complete English report (TXT) · Download source records (JSON)

[E025] Schneider Electric to acquire PTC, creating the next level of Energy and Industrial Intelligence

Supported claim: On 5 October 2026, Schneider Electric and PTC announced that they had signed a definitive acquisition agreement. The proposed cash price is US$205 per share, valuing PTC equity at approximately US$22.6 billion.

Schneider Electric and PTC; financial release hosted by Schneider Electric · Primary joint acquisition-agreement announcement, original PDF first page visually read

Industrial Software on DEX Research

Industrial Automation and Industrial Software: History, Value Chain, Markets, and Challenges

Part 1: Industry Story

Part 2: Industry History

Putting motion into instructions

Making factory control reconfigurable

Building product and production models

Connecting systems and renewing software

Bringing AI into industrial engineering

Part 3: Market Landscape

The value chain begins with a physical measurement

Control, operations and engineering solve different tasks

The downstream customer buys a working production process

Market size depends on what is being counted

Different regions, different installation cycles

Reading company results through their business models

Competition moves across the workflow

Part 4: Industry Challenges

Existing factories make verification part of the product

Interoperability needs meaning, permission and responsibility

AI assistance shifts work towards review and verification

Security duties continue after installation

Supply choices and delivery economics meet at acceptance

Appendix: Supporting Evidence

[E025] Schneider Electric to acquire PTC, creating the next level of Energy and Industrial Intelligence

[E003] Schneider Electric announces completion of transaction to acquire entire share capital of AVEVA

[E008] AVEVA Operations Control Software

[E009] Windchill PLM Software | Enterprise PLM System

[E007] What is Manufactuing Execution System?

[E013] Guide to Operational Technology (OT) Security

[E016] Unified Architecture – Landingpage

[H001] MIT Science Reporter—Automatically Programmed Tools (1959)

[H010] Sketchpad A man-machine graphical communication system

[H002] Schneider Electric celebrates 50 years of Modicon, the programmable controller that maximizes operational profitability (translated title)

[H003] Yokogawa Celebrates the 50th Anniversary of the CENTUM Distributed Control Systems: A Pioneering Achievement

[H004] A Quick History of Creo at PTC: From Parametric to the Cloud and AI

[H006] The ISA-95 Enterprise-Control System Integration standards

[H005] OPC Foundation and PLCopen release version 1.02 of the OPC UA for IEC61131-3 specification

[H007] Recommendations for implementing the strategic initiative INDUSTRIE 4.0: Final report of the Industrie 4.0 Working Group

[H008] PTC Continues to Accelerate Subscription Business Model Globally

[H009] Siemens and Microsoft partner to drive cross-industry AI adoption

[E004] Industrial automation

[E006] Distributed Control Systems for Critical Process Operations

[E020] Dassault Systèmes’ Software Portfolio: Unified by the 3DEXPERIENCE Platform

[E005] Updated Environmental Statement 2022

[E021] A complete industrial automation portfolio

[E023] About Inovance

[E019] Debut at Hannover Messe 2024: Siemens announces a new generation of controller with Simatic S7-1200 G2, part of Siemens Xcelerator

[E024] H5U PLC

[E012] Siemens Industrial Copilot expanded, adopted by thyssenkrupp

[E104] Rockwell Automation Form 10-Q for quarter ended 30 June 2026

[E207] CIMdata Publishes Executive PLM Market Report

[E208] Software Industry Performance in 2025 (translated title)

[E201] Fourteen consecutive wins! SUPCON’s 2024 DCS market share rises to 40.4%, setting another industry record (translated title)

[E209] China’s Software Industry Performed Well in 2024 (translated title)

[E202] Automation Product Data Updates: Content and Timing (translated title)

[E204] Five Million Robots now Operate in Factories Globally

[E205] U.S. now Second-Largest Robotics Market, Following China

[E206] European Union’s Industrial Robot Stock Hits Record 700,000 Units

[E212] Control’s Top 50 Automation Companies

[E101] Record third quarter – Outlook raised

[E102] Rockwell Automation Reports Third Quarter 2026 Results

[E105] Schneider Electric Half-Year Financial Report 2026 — issuer text distributed unchanged

[E103] Financial results

[E002] Emerson Completes Acquisition of Remaining Outstanding Shares of AspenTech

[E001] Siemens acquires Altair to create most complete AI-powered portfolio of industrial software

[E017] Milestone for industrial digitalisation: Asset Administration Shell standard receives security specification

[E014] Cyber Resilience Act - Reporting obligations

[E022] Cyber Resilience Act

[E015] Implementation Opinions on the 'Artificial Intelligence + Manufacturing' Special Action (translated title)

Image Credits