How do the world’s largest companies approach supply chain monitoring? (March 2024)

The world’s largest companies rely on Enterprise Resource Planning (ERP) systems to run their supply chains. So, which ERP is most utilized at enterprises with the largest supply chains in the world?

The world’s largest companies rely on Enterprise Resource Planning (ERP) systems to run their supply chains. So, which ERP is most utilized at enterprises with the largest supply chains in the world?

  • Walmart: SAP S/4HANA

  • Microsoft: SAP S/4HANA

  • Ikea: SAP S/4HANA

  • Toyota: SAP S/4HANA

  • Audi AG: SAP S/4HANA

  • Tesla: Warp, an in-house platform (Musk decided not to upgrade SAP...)

Beyond serving as the backbone of supply chains and operations, ERP systems facilitate collaboration among a company’s departments by offering a centralized database.

ERPs serve to incorporate operations across various business functions such as accounting, eCommerce, human resources, project management, procurement, and customer relationship management (CRM).

What can companies of all sizes learn from the "Walmarts of the world" about supply chain monitoring?

Put simply, the largest enterprises in North America generally run SAP S/4HANA.

As of February 2024, SAP reported that 85 of the world’s 100 largest companies were SAP S/4HANA customers. The largest companies also happen to have the largest supply chains.

SAP is the leading ERP run by Fortune 2000 companies in dozens of industries – most of which are built upon large, multinational, supply chains. Forbes Global 2000 companies are hardly different; 92% trust SAP to manage their supply chain operations.

However, since SAP is used extensively by a wide variety of professionals across 20+ industries, it shouldn’t come as a surprise that supply chain professionals have varied opinions on SAP:

"SAP has been a game-changer for our visibility and control over our supply chain. We can now track inventory in real-time, identify bottlenecks before they become problems, and react quickly to disruptions." - Supply Chain Manager, Fortune 500 manufacturer

"The integration of SAP with our other systems has streamlined our logistics and procurement processes. We've seen significant cost savings and improved customer satisfaction as a result." - Director of Supply Chain, mid-sized logistics company

"SAP's commitment to innovation gives me confidence that our supply chain will stay ahead of the curve. Their latest AI and machine learning tools are helping us optimize inventory levels and predict demand with greater accuracy." - Head of Supply Chain Operations, large retail chain

A diagram of several benefits reported by S/4HANA users

Even though the benefits of implementing S/4HANA (both on-prem and Cloud) are widely known, not all sentiments are... positive on SAP S/4HANA implementations:

"Implementing SAP was a monumental undertaking, and it took much longer and cost more than we initially anticipated. The learning curve for our team was steep." - Supply Chain Manager, food production enterprise

"We sometimes feel like we're just scratching the surface of what SAP can do. There's so much functionality, but it can be challenging to customize it to meet our specific needs." - Logistics Manager, mid-sized pharmaceutical company

"SAP can be rigid and unforgiving. It doesn't always adapt well to changes in our business or the market. We sometimes have to work around the system, which can be frustrating." - Director of Procurement, consumer goods company

Steep learning curves and customization difficulties are a couple of potential drawbacks associated with SAP's versatility, which can lead to implementation challenges. Predictably, implementation complexity, lack of integration with third-party applications, and budget are common concerns.

Common S/4HANA implementation pain points ranked by ASUG & DSAG

Beyond pain points: CIOs & Digital Transformation Leaders may be tasked with two difficult questions before implementation:

  • Will the implementation project positively impact supply chain uptime?

  • Can this wait? How much revenue was lost last year to SAP downtime?

Tackling SAP implementation is like taming a wild beast, but amidst the chaos, it's easy to forget to give a little love to continuous system monitoring. Determining an average cost of downtime across enterprise supply chains is difficult; discrepancies in company size, industry and supply chain complexity further complicate this.

The severity of downtime can vary – a software glitch causing a very short delay is entirely different from a natural disaster shutting down a production facility. A single minute of downtime may be monetarily insignificant for smaller companies, while for larger enterprises, the same duration can trigger cascading effects with significant cost implications.

Decades of research suggests revenue lost to supply chain downtime can range from tens of thousands to millions of dollars per hour. Some estimates place the average cost of enterprise server downtime at $300,000 per hour, which likely underestimates losses for complex supply chain disruptions that occurred this decade.

Other studies like, ITIC's Global Server Hardware and Server OS Reliability Survey report in 2022, indicated that 91% of respondents experience hourly downtime costs exceeding $301,000, with 44% of them indicating downtime losses greater than $1 million per hour.

To cite one industry example, a semiconductor production line disruption could cost millions per hour due to uncounted orders and potential chip shortages impacting other businesses. Meanwhile, a delayed container ship arrival at a major port might result in losses of only tens of thousands per hour due to storage fees and disruption of downstream logistical activities.

Causes of downtime and hours of downtime ranked across enterprise organizations from IDC

Of course, there are other factors that could influence the cost of downtime:

  • Company size and industry: a commercial retailer with a single distribution center will face different costs compared to a global energy enterprise.

  • Supply chain complexity: a more basic chain with limited dependencies may see lower downtime costs than a complex, global chain with numerous suppliers and transportation legs.

  • Indirect costs: beyond lost revenue, downtime can cause damage to brand reputation, leading to legal fees, lost customer orders, and employee overtime costs.

To embark on the perilous quest of uncovering the true financial dragon that is supply chain downtime, taking one or both of these paths may be of value:

  • Focusing on a specific average can be misleading; conducting a cost-of-downtime analysis tailored to a business’s unique supply chain should help to identify vulnerable points.

  • Thoroughly reviewing the current effectiveness of risk mitigation strategies across supply chain networks.

Put simply, developing rapid response protocols can begin to reduce the impact and duration of downtime to ultimately minimize losses (who knew)?

To avoid supply chain downtime, how much budget should be allocated to monitoring SAP?

Thousands of organizations are tasked with answering this question each year – and finding an answer that fits their unique SAP-run supply chain landscape is easier said than done.

A quick Google search will likely reveal that supply chain monitoring expenditures can range from just a few thousand dollars for small businesses to millions of dollars annually for large enterprises. Specific solutions, for example, like GPS tracking for transportation fleets, may cost only $10 per vehicle per month, while advanced data platforms made for tracking multiple components of supply networks can amount to hundreds of thousands of dollars annually.

An invaluable supply chain monitoring solution can effectively mitigate and potentially predict disruptions; however, the average losses during disruptions must be considered – an organization with a multinational supply network that bleeds $100,000+ per minute of disruption likely has much to gain from making a sizeable investment in "next-generation" supply chain monitoring.


Ranking common disruption mitigation approaches, KPIs, and priorities of supply chain professionals

Beyond preventing outages, the return on investment (ROI) for proactive SAP monitoring can be significant. Going from reactive to proactive monitoring can mean supporting multiple monitoring KPIs associated with improved labor efficiency, reduced downtime risk, and improved customer experience – all associated with higher revenue.

Buckle up: consider the heavyweights in supply chain monitoring

  • Technology and tools: off-the-shelf software solutions will be priced "differently" than customizable platforms that integrate cutting-edge AI solutions and on-demand services to assist with deployment.

  • Flexing labor costs and monitoring scope: the cost of basic tracking (manually gathering data on what has been picked, what has been shipped, what is on the truck, etc.) may differ from real-time analysis and predictive models that can identify bottlenecks in near real-time, requiring less labor.

  • Company size and complexity: multi-billion dollar enterprises with global supply chains will naturally incur higher monitoring costs than smaller, single region distribution networks.

For basic tracking services, budgets may start around $5,000 – 10,000 per month for smaller, commercial businesses. On the other hand, advanced, real-time solutions with access to predictive and historic analytics may cost upwards of 10,000 per month for large enterprises with dozens of SAP systems to be monitored.

An additional budgetary challenge for supply chain professionals may be reviewing data platforms to ingest and monitor IoT data, which could hold the negative connotation of high upfront costs.

How do supply chain leaders (like Walmart, FedEx, or Home Depot) approach SAP monitoring budgets?

It might seem impossible to reach a realistic estimate of the annual budget that massive enterprises such as Home Depot spend on monitoring their SAP-run supply chains, due to two prominent factors:

  • Integrated nature of costs: SAP monitoring is deeply embedded within broader supply chain processes and technologies (no surprise), making it difficult to isolate and quantify the specific ROI of SAP monitoring solutions on maintaining overall supply chain uptime.

  • Evolving and dynamic systems: it may also come as no surprise that Home Depot, for example, has continually invested in and scaled their supply chain, making any snapshot of monitoring-related spending outdated in less than a year.

With Home Depot's complex landscape encompassing a global network of suppliers, thousands of stores, fulfillment centers, delivery fleets, and diverse product lines, effective monitoring necessitates significant resources – where robust monitoring is likely a critical success factor.

A diagram showing parts of one enterprise's business network

Industry averages suggest that large enterprises (like Home Depot, Walmart, or Fedex) spend 0.5% to 2% of their total supply chain expenditures on visibility and traceability technologies. Considering that costs wrapped around Home Depot's supply chain likely reach $100 billion, the annual monitoring budget at similarly sized enterprises could amount to hundreds of millions of dollars.

Costs aside: how much time do enterprise organizations spend monitoring their SAP-run supply chains?

Determining the amount of time spent on manually monitoring supply chains is even more intricate than pinpointing the associated costs, due to wide variations in company size, industry, and complexity of supply networks.

While there's no clear industry "average” for time spent on SAP monitoring labor, recent studies suggest that dedicated supply chain professionals spend anywhere from 25% to 75% of their time on monitoring activities. This might translates to roughly 40 to 120 hours per month (480 to 1440 hours per year) for each full-time employee (FTE) tasked with monitoring a single region's operations.

To mitigate the labor-intensive nature of manual monitoring, some organizations now distribute supply chain monitoring responsibilities across multiple teams, while others leverage automated solutions to reduce the shared workload and time commitments.

Additional time commitments of monitoring SAP may include:

  • Manual labor spent on monitoring components that are constantly fluctuating due to specific events or disruptions within the supply network.

  • Proactive planning and manual analysis – not just reactive firefighting – both of which require hefty time investments.

  • Time allocated to implementing advanced monitoring that could improve efficiency and cut labor costs – automating certain reporting tasks and configuring real-time notifications and alerts.

Which SAP monitoring tools are most utilized by enterprise organizations with large supply chains?

SAP Solution Manager (SolMan) 7.2

The preferred SAP monitoring tools at enterprise organizations vary greatly, but a few typical choices are:

  • SAP Solution Manager: an integrated platform for monitoring performance, analyzing trends, and identifying issues across various SAP applications, including those related to supply chain management.

  • SAP HANA Cloud Platform: provides real-time data analytics and reporting capabilities, enabling businesses to monitor supply chain KPIs and make informed decisions based on SAP data.

  • SAP Leonardo IoT Foundation: allows for integration of sensor data from connected devices within the supply chain, offering deeper visibility into material movement, equipment performance, and environmental conditions.

While SAP’s beloved Solution Manager (SolMan) offers valuable functionalities that can support supply chain monitoring, like whispering sweet nothings into the ears of SAP systems to ensure everything runs smoothly, it's crucial to consider limitations before forgoing other monitoring solutions and relying on Solution Manager alone.

Believe it or not (some might not...), there can be significant costs associated with solely using Solution Manager for comprehensive supply chain monitoring:

  • Initial staff and implementation investments and ongoing maintenance costs can be significant, especially for enterprises with multinational supply networks.

  • Implementing and customizing Solution Manager to keep up with and scale to growing manufacturing or distribution networks requires a large amount of SAP expertise, and months (if not years) of highly-skilled labor.

  • Continuously fluctuating supply networks with additional components and KPIs to monitor and report on, amounting to higher resource demands.

Other drawbacks to SolMan may include limited visibility and flexibility, as:

  • Solution Manager focuses on SAP applications and data, potentially neglecting external sources and broader supply chain ecosystems.

  • In-house customizations can fall short when compared to dedicated data analytics platforms that offer greater visualization capabilities with out-of-the-box SAP data extractors and dashboards.

  • Scalability may be limited for gargantuan supply chains with vast data volumes and diverse integrations across SAP landscapes.

  • Performance bottlenecks may occur under heavy data loads, or after extensive customization.

  • Integration with non-SAP systems can be challenging and require additional time and expertise.

  • Staying updated with the latest features and functionalities requires ongoing resource allocation.

Are there any drawbacks to third-party SAP monitoring solutions?

Third-party visibility solutions may offer broader ecosystem coverage but could involve additional costs and integration complexities that interfere with existing SAP investments. Internal development of custom monitoring solutions can be expensive and time-consuming, requiring expert technical resources to be consistently available.

SAP professionals may choose to evaluate specific needs and limitations before relying solely on Solution Manager to support broad monitoring efforts.

A hybrid approach to monitoring that combines SolMan with other SAP-certified tools may allow for broader visibility and deeper analytics. Some organizations have begun with weighing the pros and cons of third-party solutions to complement Solution Manager, based on technical expertise available, as well as desired level of customization.

Next-generation SAP monitoring: what is it?

Some of the Fortune 500 have entrusted the health of their supply chains with SAP-certified monitoring solutions that provide more robust "next-generation" monitoring than Solution Manager does alone, with features such as:

  • Pre-built, out-of-the-box connectors and data extractors: seamless integration with SAP systems and various supply chain data sources.

  • Real-time visibility and actionable insights: immediate visibility into supply chain health for proactive decision-making with automated alerts and notifications.

  • User-friendly interface and on-demand support: tailored for ease of use by business users without requiring deep technical knowledge; providing experts available on-call to support the implementation process.

Even though each enterprise’s supply chain landscape is different, organizations of all sizes thoroughly evaluate their SAP landscapes before implementing any monitoring solution that claims to provides "comprehensive monitoring" or "SAP observability,” or "O11y," even if the solution is SAP-certified.

Ultimately, most enterprises simply want a solution that offers:

  • Capability to integrate easily with existing IT infrastructure and SAP systems.

  • Ability to reduce labor and increase the current capacity of SAP teams.

  • Ability to scale, supporting landscapes growing in complexity.

  • A degree of operational SAP visibility – ability to provide a service-oriented view of landscapes, and correlate SAP & infrastructure.

Tiered maturity model for SAP Observability "O11y" from RHONDOS

By utilizing a tiered approach to determine a "current state” of SAP monitoring and observability, SAP-run enterprises may get one step closer to finishing their monitoring list of "must haves" necessary to support years of scalable growth.

Further reading:

Safeguarding login security across SAP systems

A different approach to S/4HANA migration

Getting the most value out of IT Service Intelligence for SAP

When does everything at a Fortune 500 company grind to a halt?

RHONDOS On Demand now available for RISE with SAP

Previous
Previous

SAP Performance Tuning: The RHONDOS PowerConnect Way (May 2024)

Next
Next

RHONDOS On Demand Now Available for RISE With SAP (September 2023)