Industry Challenges

Australian manufacturing organisations face rising input costs, supply chain fragility, increasing regulatory requirements, and the digital transformation of operations from the shop floor to the boardroom. Enterprise systems designed for a different operational environment are increasingly inadequate. Disconnected systems create information gaps that prevent operational decisions from being made with confidence.

Our Solutions for Manufacturing

• ✓
  SAP S/4HANA for Manufacturing: S/4HANA implementations and migrations covering MRP, production planning, quality management, plant maintenance, and procurement.
• ✓
  OT/IT Integration: Architectures connecting operational technology (SCADA, MES, IoT sensors) with enterprise systems for real-time production data.
• ✓
  Supply Chain Data Platform: Consolidated supply chain data enabling demand forecasting, supplier performance analytics, and inventory optimisation.
• ✓
  Asset Management: SAP PM implementations connecting maintenance planning with operational performance data for predictive maintenance.

Frequently Asked Questions

How do you approach OT/IT integration for manufacturing?

OT/IT integration in manufacturing requires attention to security, latency, and the operating patterns of operational technology systems. We design integration architectures providing enterprise visibility into operational data without compromising OT system performance or security, typically using an edge processing layer that aggregates OT data before passing it to the enterprise integration platform.

Can COUPS handle multi-site SAP implementations across Australian manufacturing groups?

Yes. We have led SAP implementations across multi-entity manufacturing groups with operations across multiple Australian states and APAC markets. Our template-and-localisation approach ensures global consistency while accommodating site-specific requirements.

Industry Challenges

Australia's mining and resources sector operates some of the world's largest and most complex operational environments. Remote assets, complex supply chains, stringent safety and environmental compliance, and the need to connect operational technology with enterprise systems create a unique set of technology challenges. SAP and ERP systems in mining often fail to deliver their potential because they are not adequately connected to the operational environment.

Our Solutions for Mining

• ✓
  Asset and Maintenance Management: SAP PM implementations connecting planned, breakdown, and preventive maintenance with equipment performance data from operational systems.
• ✓
  Project Management Integration: SAP PS solutions for capital project management connecting cost, schedule, and resource data into unified project reporting.
• ✓
  Operational Data Platform: Data platforms consolidating OT data with enterprise data, enabling operational intelligence that improves production performance and reduces cost.
• ✓
  Procurement and Inventory: SAP procurement and inventory management for remote and complex site environments including strategic sourcing and inventory optimisation.

Frequently Asked Questions

How do you approach OT/IT integration in a mining environment?

OT/IT integration in mining requires careful attention to security, latency, and the different operating patterns of operational technology. We design integration architectures providing enterprise visibility into operational data without compromising OT system performance or security. This typically involves an edge processing layer aggregating and transforming OT data before passing it to the enterprise integration platform.

Industry Challenges

Australian healthcare organisations are managing growing patient volumes, increasing care complexity, and the pressure to do more with constrained resources. Enterprise systems have a direct impact on operational efficiency and increasingly on patient outcomes through the data they hold and the insights they enable. Healthcare organisations face specific ERP and data challenges: compliance with Australian privacy legislation, interoperability requirements with clinical systems, complex workforce management, and the need to connect administrative and clinical data for population health purposes.

Our Solutions for Healthcare

• ✓
  ERP Modernisation for Health Organisations: Replacing outdated ERP platforms with modern, cloud-based environments reducing administrative burden and improving financial visibility.
• ✓
  Healthcare Data Platform: Data platforms consolidating administrative, clinical, and operational data for population health analytics and research access.
• ✓
  Finance and Procurement Transformation: SAP Finance and Procurement implementations for multi-entity health structures including grant management and healthcare-specific procurement.

Frequently Asked Questions

How do you manage data residency and privacy compliance in healthcare data platforms?

All healthcare data platform implementations are designed with Australian Privacy Act and HIPAA compliance requirements built in from the architecture phase. We ensure data residency controls keep health data in Australian cloud regions, implement role-based access controls aligned to clinical role structures, and conduct Privacy Impact Assessments for all data flows.

Industry Challenges

Australian retail is in transition. The integration of physical and digital channels has moved from a competitive differentiator to a baseline requirement. Supply chains have become more complex and more fragile. Consumer expectations for personalisation and convenience are rising. And the data required to meet these expectations is scattered across disconnected systems. SAP and ERP systems designed for a store-centric retail model are often inadequate for omnichannel operations without significant integration and modernisation investment.

Our Solutions for Retail

• ✓
  SAP Retail Consulting: S/4HANA Retail implementations covering merchandise management, inventory management, pricing, promotions, and wholesale management.
• ✓
  Omnichannel Integration Architecture: Integration architectures connecting e-commerce, POS, warehouse management, and SAP in real time for unified inventory visibility and order management.
• ✓
  Retail Data Platform: Unified transactional, customer, and operational data for demand forecasting, promotional analytics, and customer analytics.

Frequently Asked Questions

How do you handle real-time inventory synchronisation across channels?

Real-time inventory synchronisation requires an event-driven integration architecture where inventory changes in any channel publish events consumed by all other channels within seconds. We design this architecture using SAP Integration Suite with Event Mesh, connecting SAP inventory management to e-commerce, POS, and WMS platforms. The architecture is designed for the transaction volumes of major Australian retail operations.

Industry Challenges

Australian government agencies face ERP modernisation challenges that differ from the private sector. Procurement governance requirements add complexity to vendor selection. Legacy systems are often older and more deeply embedded than in comparable private-sector organisations. Political and public accountability requirements create risk aversion. And the consequences of system failure are visible in ways that private-sector failures are not. These constraints are real but do not prevent successful ERP modernisation; they require programme approaches specifically designed for the public-sector environment.

Our Solutions for Government

• ✓
  ERP Strategy and Business Case: Business cases designed to survive gateway review and minister approval processes: rigorous, transparent, and evidence-based.
• ✓
  SAP Public Cloud Implementation: S/4HANA Public Cloud implementations for government agencies, designed to maximise standard functionality and minimise customisation.
• ✓
  Programme Assurance: Independent programme assurance reducing the risk of cost overrun and delivery failure for large government ERP programmes.

Frequently Asked Questions

How do you approach government procurement requirements for SAP advisory?

We have experience operating under panel arrangements, open tender processes, and direct engagement under applicable procurement thresholds. We understand the documentation and compliance requirements of government procurement and can support agencies through vendor selection as well as delivery.

What is your experience with Australian government ERP programmes?

We have advised on and led ERP programmes for federal and state government agencies across Australia. Government programmes require specific expertise in probity management, public-sector programme governance, and communication with ministerial and parliamentary stakeholders.

Industry Challenges

Australian utilities are navigating a transformation of their operating environment. The energy transition is reshaping the asset base, operating model, and regulatory requirements of electricity network operators, generators, and retailers. In this context, enterprise systems are critical infrastructure. SAP IS-U, SAP PM, and SAP Finance support the billing, asset management, and financial management processes that utilities depend on. And the data these systems hold is increasingly important for regulatory compliance, capital planning, and operational performance management.

Our Solutions for Utilities

• ✓
  SAP IS-U and Utilities Consulting: Specialist consulting for SAP IS-U implementations, migrations, and modernisation programmes in energy and water utilities.
• ✓
  Asset Management and Plant Maintenance: SAP PM implementations connecting planned and reactive maintenance with asset performance data.
• ✓
  Regulatory Reporting and Analytics: Reporting solutions for AEMO, AER, and state-level regulatory compliance requirements.

Frequently Asked Questions

How do you handle AEMO and AER reporting requirements in SAP?

We design SAP reporting architectures specifically for the Australian regulatory reporting requirements, including automated data extraction, validation, and submission workflows aligned to AEMO and AER submission formats. Our utilities practice has experience building these architectures for network operators and retailers across multiple Australian jurisdictions.

Industry Challenges

Australian financial services organisations operate under APRA prudential standards, ASIC regulatory requirements, and increasingly complex data privacy and cybersecurity obligations. Enterprise systems must support operational efficiency while providing the controls, auditability, and reporting capabilities that regulated environments demand. ERP and data platform decisions have compliance implications requiring specialist knowledge; SAP implementations must be designed with the right access controls, segregation of duties, and audit trail capabilities.

Our Solutions for Banking and Finance

• ✓
  SAP Financial Services Consulting: SAP implementations for financial services with deep understanding of APRA and ASIC compliance requirements and the controls needed for regulated environments.
• ✓
  Finance Transformation: Finance function modernisation leveraging S/4HANA Finance to improve close cycle times, reporting accuracy, and management accounting.
• ✓
  Regulatory Data and Reporting: Data platform designs for APRA reporting, AUSTRAC requirements, and ASIC data submissions.

Frequently Asked Questions

How do you approach segregation of duties in SAP for financial services?

Segregation of duties in SAP for financial services requires a role design methodology that maps regulatory requirements to SAP authorisation objects, implements compensating controls for conflicts that cannot be structurally avoided, and integrates with GRC tooling for ongoing monitoring. We design and implement SoD frameworks that satisfy APRA auditor requirements.

Challenge

The group designs and manufactures medical devices, healthcare products and in vitro diagnostic (IVD) systems, with manufacturing, distribution and commercial operations around the world. Growth and acquisitions had left it with a fragmented ERP landscape: different systems and process variants by region, inconsistent master data, and limited end-to-end visibility from supplier to finished product. As a regulated manufacturer, the group also had requirements that a new platform could not compromise: batch and serial traceability, Unique Device Identification (UDI), validated systems under GxP, and electronic records controls aligned with FDA 21 CFR Part 11 and the EU MDR and IVDR. Products supplied to hospitals and laboratories meant supply could not be interrupted at any cutover.

Solution Approach

COUPS worked with the group across the six-year programme, from global template design through successive regional rollouts. The global template covered finance, procurement, manufacturing, quality management, supply chain and order-to-cash, with regulated processes such as batch management, serialisation and quality inspection designed into the standard rather than added site by site. Computer system validation was built into the delivery method from the start, with documented requirements, risk-based testing and a requirements traceability matrix maintained for every release.

Implementation

The programme was delivered in waves by region and business. Each wave reused the global template and added only the localisation needed for country legal, tax and regulatory requirements, which kept the core consistent and made later waves faster to deploy. Master data for materials, customers and suppliers was cleansed and harmonised before migration, and data loads were validated through repeated dress rehearsals. Cutovers were planned around manufacturing schedules and inventory build-ups so that product supply continued throughout.

Results

• ✓
  One global SAP S/4HANA template in use across regions and businesses
• ✓
  Legacy regional ERP systems retired
• ✓
  End-to-end batch and serial traceability supporting UDI and recall readiness
• ✓
  Validated, audit-ready system landscape for a regulated manufacturing environment
• ✓
  Harmonised global master data for materials, customers and suppliers
• ✓
  Real-time global visibility of inventory, production and financial performance

Challenge

The group manufactures and sells building products through plants, distribution centres and sales companies in several regions, with its headquarters in Japan. Each region had grown its own reporting on top of local ERP, manufacturing and sales systems, so data definitions differed from country to country and group-level reporting depended on spreadsheets assembled by hand. Headquarters could not see sales, inventory, production and margin across the group on a consistent basis or at the speed management needed. The existing data warehouse was slow, costly to run and could not scale to new data sources or advanced analytics.

Solution and Results

COUPS designed and delivered a modern data platform that pairs SAP and Google Cloud. SAP BW/HANA on the SAP HANA database models and serves the group's SAP data, while Google BigQuery holds non-SAP and high-volume data at cloud scale. SAP Analytics Cloud, Tableau and Google Looker give headquarters and regional teams planning, dashboards and self-service analysis on the same governed data. A group-wide data model set common definitions for products, customers, plants and financial measures, and a data governance framework assigned clear ownership for each data domain across headquarters and the regions. Over 24 months the platform was rolled out region by region, and legacy reporting was moved across and retired. Results: one trusted source of group-wide data for headquarters and regional management; consistent sales, inventory, production and margin reporting across all regions; manual spreadsheet consolidation replaced with automated, governed reporting; the legacy data warehouse modernised on SAP HANA and Google BigQuery; and a platform ready for forecasting and other AI use cases.

Challenge

A wholesale distribution company was running its finance, procurement, inventory and order management on a system in place for over 20 years, out of vendor support and hosted on infrastructure requiring urgent replacement. Disconnected processes between purchasing, warehousing and sales made stock visibility slow and month-end close labour-intensive. Two previous replacement attempts had been terminated before go-live due to scope and cost overruns.

Solution and Results

COUPS conducted a six-week programme recovery assessment identifying three root causes of previous failures: poorly defined scope, over-optimistic benefit assumptions, and governance too slow to make required decisions. We recommended SAP S/4HANA Public Cloud, supported by a fit/gap analysis showing 94% of functional requirements met by standard functionality across procure-to-pay, order-to-cash, inventory management and finance. A fixed-scope programme with a locked business case and a decision-velocity governance model followed. Results: delivered 3 days ahead of the go-live date and within approved budget; 20-year legacy system retired; month-end close reduced from 10 days to 4 days; procurement approval times reduced by 60% through automated workflow.

What Is Clean Core?

Clean core is SAP's architecture principle that the core S/4HANA system should be kept as close to standard as possible, with customisations and extensions built outside the core using SAP-standard APIs and BTP tools. In ECC, core modifications were common and often the easiest way to implement business requirements. They accumulated as technical debt that made upgrades expensive and change slow. In S/4HANA, SAP has invested in making standard functionality rich enough that most requirements can be met without core modification, and in providing BTP as the platform for clean extensions.

Why Clean Core Matters for Australian Enterprises

Australian enterprises approaching S/4HANA migration typically have two to five hundred customisations in their ECC landscape accumulated over a decade or more. Rebuilding them as S/4HANA customisations preserves technical debt. Retiring them forces process redesign. Building them as BTP extensions requires architecture discipline but produces a sustainable result. Organisations that adopt clean core during migration find subsequent upgrades take weeks rather than months, and features that SAP releases quarterly become available quickly rather than being blocked by upgrade risk assessment.

Building a Clean Core Strategy

A practical clean core strategy starts with a customisation inventory and assessment. Every customisation should be documented, classified by business criticality and technical complexity, and evaluated against three options: retire (the business need no longer exists or can be met by standard functionality); adopt (replace with standard SAP functionality or process redesign); or extend (rebuild as a clean BTP extension). For a typical Australian enterprise with 300 to 500 ECC customisations, realistic outcomes are: 30-40% retired, 30-40% replaced by standard functionality with some process change, and 20-30% requiring clean BTP extensions.

Frequently Asked Questions

How long does a customisation inventory and assessment take?

For a mid-size enterprise with 200 to 400 ECC customisations, typically four to six weeks. For larger landscapes, eight to twelve weeks. This assessment is a prerequisite for the S/4HANA migration business case.

Is SAP BTP included in RISE with SAP?

Yes, but the scope of the BTP entitlement varies by contract and does not always cover all services needed for a comprehensive extension architecture. Review the specific BTP services included in your RISE contract against your architecture requirements before signing.

Does clean core mean no customisation at all?

No. Clean core means customisations are built in the right place (outside the core) using the right tools (BTP and standard APIs). Organisations can and should build extensions meeting their specific business requirements. The principle is about where and how, not whether.

Failure Mode 1: Scope That Cannot Be Controlled

The most common cause of ERP programme cost and schedule overrun is scope that grows during delivery without corresponding budget or timeline adjustment. The prevention: a thorough scope definition process, a change control process requiring financial impact quantification and executive approval for every addition, and a business case reviewed against actual scope at each major milestone.

Failure Mode 2: Data Quality Addressed Too Late

Data quality issues discovered in the final quarter are the most common cause of go-live delay. The prevention: data quality assessment from the first programme phase, data cleansing as a funded workstream throughout delivery, and migration dress rehearsals validating completeness and accuracy against defined acceptance criteria.

Failure Mode 3: Integration Surprises

Legacy integration landscapes are consistently underestimated. Some interfaces may not be documented. Some may connect to retired systems whose data flows are still relied upon. The prevention: comprehensive integration inventory in the strategy phase, integration migration as a dedicated programme workstream, and end-to-end integration testing validating business process flows rather than individual interface connectivity.

Failure Mode 4: Change Management Underfunded

ERP transformation changes how people do their jobs. If people whose jobs change are not adequately prepared, go-live adoption is poor, workarounds proliferate, and business benefits fail to materialise. The prevention: change management budgeted at 15-25% of total programme cost, a change impact assessment identifying every affected role, and a sustained communication programme from programme start to post-go-live stabilisation.

Failure Mode 5: Governance Too Slow for the Programme

Governance that cannot make decisions quickly enough is as damaging as no governance at all. The prevention: a steering committee meeting at least fortnightly during active delivery, clear decision rights defining which decisions the programme makes independently, and escalation paths allowing urgent decisions to reach the executive sponsor within 48 hours.

What Is a Data Lakehouse?

A data lakehouse combines the low-cost storage and schema flexibility of a data lake with the governance, performance, and query capabilities of a data warehouse. The core idea is a single storage layer supporting both structured analytical queries and raw, unstructured data, with governance and access controls applied across the entire estate. Implementations typically use cloud object storage (Azure Data Lake Storage, AWS S3, Google Cloud Storage) with a governance and query layer (Delta Lake, Apache Iceberg) and a processing and serving layer (Azure Synapse, Databricks, Amazon Redshift, Google BigQuery). The data lakehouse pattern is centralised by design — a central data team manages the platform, pipelines, and data quality standards.

What Is a Data Mesh?

Data mesh is a decentralised architecture pattern treating data as a product owned by the business domain that generates it. Each domain is responsible for publishing its data as a product meeting defined standards of quality, accessibility, and documentation. Data mesh is an organisational and architectural pattern, not a specific technology. The critical components are: domain ownership, data as a product, self-serve infrastructure, and federated governance.

When to Choose Each

The lakehouse works well for organisations with centralised data teams, clear source system data ownership, and a manageable number of domains. The data mesh works well for large organisations with strong domain ownership culture, a history of centralised warehouse bottlenecks, and engineering maturity in domain teams to build and maintain data products. Most Australian enterprises in 2025 are adopting a pragmatic hybrid: lakehouse infrastructure with data mesh principles applied to data ownership and governance.

Frequently Asked Questions

How does SAP Business Data Cloud fit into a data mesh architecture?

SAP BDC, built on SAP Datasphere, supports data mesh principles through its data product and data space capabilities. SAP-originated data domains can be published as data products and consumed by other domain teams without requiring centralised pipeline management. This makes BDC a natural fit for organisations applying data mesh principles to their SAP data estate.