Access Official Technical PDF

Share Summary:LinkedInEmail

Industrial software is not a single market: it spans manufacturing analytics, engineering tools, test automation, infrastructure and security. A Q2 2020 software-market snapshot offers a useful historical look at how buyers evaluated these capabilities during a period of exceptional disruption. For decision-makers assessing industrial software M&A, the transactions show the strategic importance of connecting software capabilities with manufacturing, supply-chain and product-development workflows.

Industrial software M&A during a disrupted market

COVID-19 restrictions slowed software dealmaking in the second quarter of 2020, but activity did not stop. The update reported that small- and mid-cap transaction volume was about 20% below the pace of the previous two years, while large-cap deal activity came to a halt for the quarter. Strategic buyers remained active as private equity buyers temporarily pulled back amid tighter debt markets.

The market figures also illustrate why deal volume and valuation should be read together. Median software deal multiples in 2020 year to date were below the 10-year historical average. Yet disclosed private-equity deals that closed in the first half of 2020 had a median value of 4.9 times revenue, higher than the 4.2 and 4.0 times recorded in 2018 and 2019. The report attributed the higher result in part to a higher quality threshold for the deals that proceeded, despite lower volumes.

These figures describe a specific period, not current market conditions or a forecast. They show how disruption can affect financing and transaction activity unevenly: fewer deals may close, while assets that do attract buyers can still command strong interest.

Manufacturing analytics becomes a strategic capability

One notable transaction involved OptimalPlus, whose software applied machine learning to real-time analysis of supply-chain management and manufacturing processes in the semiconductor, automotive and electronics sectors. National Instruments acquired the company to expand its enterprise software capabilities and provide customers with product analytics across product development and supply-chain activities.

The strategic logic is relevant to industrial organizations: buyers may seek to connect operational data with broader product and enterprise workflows. In this case, the stated rationale emphasized complementary end markets and products that were often used together. For integrators and plant leaders, that makes compatibility and workflow fit important considerations when evaluating software ecosystems—not just the capabilities of an individual tool.

Automation and infrastructure deals address different layers

Other Q2 transactions highlighted software needs adjacent to industrial automation. Keysight acquired Eggplant, a software test automation provider whose platform used AI and analytics to automate test creation and execution. The reported rationale centered on bringing together capabilities spanning physical and protocol layers through to application layers, with potential to leverage measurement technologies across the combined businesses.

For engineering teams, the example underlines the breadth of “automation” in software: test automation can complement the systems used to design, measure and validate products. It is distinct from factory control, but can support the wider engineering lifecycle.

NetApp’s acquisition of Spot focused on public-cloud infrastructure management and automation. Spot’s software managed application performance using predictive algorithms, data migration and application-scaling automation. The announced combination aimed to join compute and storage capabilities for ongoing optimization across cloud-native and legacy workloads. This transaction illustrates another layer of industrial software strategy: managing the infrastructure that supports enterprise applications, rather than directly controlling production equipment.

Security and fit matter alongside functionality

The update also identified a transaction in industrial control system network security management among its notable software deals by vertical. It did not provide enough detail to assess that deal’s product capabilities or outcome, but its inclusion reflects the place of security within the broader software landscape.

Across the highlighted acquisitions, the strategic rationale was specific to each combination: complementary products, shared customers or markets, and the opportunity to bring capabilities together. For buyers and technology decision-makers, a practical review should therefore ask:

  • How does the software fit existing production, engineering, supply-chain or cloud workflows?
  • Which data, platforms and systems must it work with?
  • Does the proposed combination address a defined operational need, or mainly expand a product portfolio?
  • How will security and integration requirements be assessed?

These questions help distinguish a useful operational fit from a deal rationale that may be compelling only at a corporate level.

What historical software valuations can—and cannot—show

Public software companies were valued differently across market segments in the June 2020 data. The report placed the median enterprise-value-to-calendar-2020-revenue multiple for its tracked software universe at 7.8 times, while SaaS companies traded at a premium to the broader universe. These are historical market observations, not direct benchmarks for an industrial automation vendor or a specific acquisition.

Valuation comparisons require attention to business model, growth expectations, profitability and sector. The source’s figures covered multiple software categories, including engineering, ERP and supply-chain management, infrastructure and vertical software. A broad sector median cannot, on its own, establish the value of a particular industrial platform.

Practical implications for industrial decision-makers

The Q2 2020 snapshot suggests that even amid a sharp slowdown, strategic buyers continued to pursue software that could extend analytics, testing, infrastructure management and security capabilities. For plant managers, operations leaders and system integrators, the enduring lesson is to evaluate acquisitions and vendor changes through operational fit: how well the software connects with existing systems, supports real workflows and complements the technology already in use.

Market activity and multiples provide context, but they are not substitutes for technical and commercial due diligence. Clear requirements around integration, data, security and intended outcomes can help organizations make better-informed decisions as industrial software markets and ownership change.

Access Official Technical PDF

About The Author