Name
Customer Case Study: Why ERP Wasn’t the Starting Point for Rheem’s SAP Transformation
Description

Most SAP transformations start with ERP. Rheem didn’t — and that decision reshaped how the business approached transformation.

After modernising sales, service, planning, and analytics, Rheem accelerated innovation across the business — but also introduced new complexity across systems, processes, and regions. With multiple transformation initiatives moving in parallel, the challenge became clear: how do you bring it all together without slowing momentum or disrupting operations?

In this session, Rheem’s Head of Digital Transformation shares why ERP came last, and what it took to unify a highly integrated, multi-country landscape into a single digital core with SAP S/4HANA and RISE. From reducing decades of custom code to managing over 100 integrations and aligning teams across Australia, New Zealand, and Vietnam, this is a candid look at the trade-offs, risks, and decisions behind sequencing transformation differently.

Rheem was recognised as a Best Tech Awards 2025 Intelligent ERP finalist for this program.

Key Takeaways:

  • Why Rheem chose not to start with ERP — and when that approach makes sense

  • How to manage competing transformation initiatives without creating fragmentation

  • What it takes to unify a complex SAP landscape into a single digital core

Mian Ahmad
Session Tag
Data and Analytics, Technology, Cloud & Security
Session Type
Customer Case Study