Siemens and Rolls-Royce show how industrial software partnerships deepen

Siemens and Rolls-Royce Submarines’ October 2025 agreement formalises an industrial technology relationship that the companies say spans twenty-five years. Its scope reaches across software, hardware, skills and working practices, making it a useful case for businesses selling into complex engineering organisations.

The announcement is a memorandum of understanding. It does not disclose a new software order value or licence count. Its significance lies in the direction of cooperation and the customer environment around it: Rolls-Royce has long-term delivery obligations and is organising several kinds of industrial capability to support them.

The agreement spans the industrial lifecycle

Siemens’ 10 October announcement identifies Xcelerator technologies as part of the collaboration. It describes work across engineering, manufacturing, research, training and continuing support, with the aim of improving efficiency and reducing the time needed to bring new technology into production.

Rolls-Royce published its own account of the same agreement. These are statements from the two participants in one relationship, rather than separate evidence that every intended improvement has been achieved.

The breadth of the scope matters commercially. Engineering, manufacturing and support teams do not necessarily use information in the same way. A change that helps one group may require another to adjust its process. The value of an industrial software project often depends on making that handover more dependable.

For a smaller software supplier, this creates a more precise market question than whether Rolls-Royce is “doing digital transformation”. The useful question is which handover or decision its product improves, and which team can adopt that change.

A long-term customer contract provides context

The MOD’s January 2025 Unity announcement describes an approximately £9 billion, eight-year contract with Rolls-Royce Submarines for design, manufacture and support services. It consolidates earlier commercial arrangements and is intended to improve delivery and investment certainty.

That contract is distinct from the Siemens memorandum. The £9 billion figure is not a software budget and cannot be allocated to Siemens from the public announcements. It provides context for the scale and duration of the customer obligations within which industrial technology decisions are made.

The commercial implication is that a software investment may be evaluated against a continuing delivery programme. The customer needs to consider how a tool will be supported, how knowledge will be retained and whether information remains usable as the product and organisation evolve.

A vendor promising a quick implementation should therefore explain the continuing arrangement as well as the initial project. A successful introduction can create value over many years, but only if the customer can maintain the process and understand the dependencies it has accepted.

Other partnerships reveal different supplier roles

A later December 2025 announcement from Assystem names Assystem, AtkinsRéalis and Frazer-Nash in Rolls-Royce’s Capability Assured Strategic Partnership. Assystem describes an expanded role across engineering, project management and digital services.

That is a separate relationship from the Siemens agreement. It shows that the customer’s industrial capability is assembled through several kinds of partner, rather than one undifferentiated technology provider. The announcements do not disclose a complete workshare map or identify open subcontracts for additional companies.

For competitor research, those distinctions are useful. A platform vendor, an engineering services provider and a specialist application company may all address the same customer while performing different work. Treating them as direct substitutes can produce a misleading market map.

For a new entrant, the potential relationship depends on the contribution it can make. A specialised tool might fit through an existing service provider. An integration business might address a specific process. A company pursuing a larger direct role would need broader evidence of its ability to deliver within the customer’s environment.

Installed systems affect the cost of a new product

A twenty-five-year relationship implies a substantial history of working together, but the announcement does not quantify the installed software estate. A prospective supplier should avoid assuming either that every function is closed to competition or that it can enter without understanding existing systems.

The cost of change is wider than a licence fee. Users may need new training, information may need conversion, and responsibility for support may move between teams. Those effects belong in the commercial case because the customer has to absorb them.

A proposal can become more persuasive by making those effects explicit. A company that explains where its product fits, what information it requires and which process remains with the customer gives the buyer a clearer decision. A broad claim to replace the entire digital environment creates a much larger organisational commitment.

This is one reason complementary products can have a credible position. They can address a defined weakness while fitting within an accepted platform and support arrangement. The value still has to be demonstrated; compatibility alone is not a customer problem.

Skills are part of the proposed improvement

The Siemens announcement includes sharing practices and developing skills alongside technology. That is a meaningful part of the scope because people need to understand how to use and maintain a changed workflow.

For a product company, training can be more than an implementation accessory. It can determine whether the customer is able to use the product repeatedly and interpret its outputs consistently. Support material also helps the organisation preserve knowledge when staff change.

A hypothetical application for reviewing engineering records illustrates the point. The software might make information easier to compare, but users still need to understand the review process and what the output means. The customer also needs a way to update that process when its requirements change.

The vendor’s case should therefore include how the application becomes part of ordinary work. That might involve clear documentation, a defined review responsibility and a supported update process. These are commercial implications of adoption, not claims about the private terms of the Siemens agreement.

The support team is another audience for that material. If it cannot reproduce a problem or determine which version generated an output, a small issue can consume considerable time across several organisations. Clear ownership of the information and a shared description of the supported configuration can make the supplier relationship more dependable. That kind of operational clarity is a tangible part of the product, even when it is less visible than a new interface.

Productivity needs a defined measure

The companies describe ambitions to improve efficiency and shorten time to production. Those aims do not establish a measured programme-wide result. A future case study would be more informative if it identified the particular task, the previous process and the change accepted by the customer.

For example, reducing the time to find an approved record could be valuable even if it does not immediately alter the overall manufacturing schedule. The customer may gain a more dependable review process or reduce duplicated work. The metric should reflect the actual benefit rather than borrow the scale of the wider programme.

The US Navy’s Ship OS investment provides a separate example of industrial software being connected to specific workflow improvements. Patria’s software sustainment integration offers a comparison at the support stage.

The Siemens–Rolls-Royce agreement is most useful as evidence of how industrial technology relationships deepen. A long-term customer obligation creates reasons to invest in dependable information, skills and integration. For another supplier, the opportunity begins with a well-defined contribution to that work and a credible explanation of how it can be sustained.