Get AI summaries of any video or article — Sign up free
Supply Chain Control Towers in Action | APQC Webinar thumbnail

Supply Chain Control Towers in Action | APQC Webinar

APQC·
6 min read

Based on APQC's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

A control tower’s value comes from orchestrating data, people, and processes so exceptions are prioritized and owned—not from dashboards alone.

Briefing

Supply chain control towers are emerging as the practical way to turn fragmented, multi-company supply networks into coordinated decision-making—by unifying data, standardizing processes, and assigning clear ownership for exceptions. Across three very different organizations, the common thread is that “visibility” alone doesn’t fix supply problems. The real payoff comes when alerts and events are prioritized by business impact, planners can collaborate across functions and regions, and governance makes decisions repeatable rather than reactive.

Exxon Mobil’s lubricants business built an end-to-end control tower to address pain points created by disconnected regional systems and manual, firefighting-style planning. With ERP and planning tools running separately in Asia Pacific, the Americas, and Europe Middle East and Africa, the company chose a global rollout early to ensure one set of procedures and a single operating model. More than 250 pain points were collected through workshops, then consolidated into themes: limited cross-region visibility, coordination challenges, heavy manual/reactive processes, data governance gaps, and pressure to improve service levels while lowering costs. The resulting objective was a cloud-based “single source of truth” that orchestrates data, people, and processes across the lubricants value chain—from raw material suppliers through production, packaging, distribution, and delivery to customers.

The project was structured as a five-year program executed with agile methods, releasing capabilities as they became ready. Change management was treated as a core requirement, including robust adoption planning (using Prosci change management). Early deliverables focused on data visibility and supplier connectivity (via API connections into data lakes), along with exception management that groups alerts into events, assigns ownership, and supports root-cause collaboration. Later capabilities added scenario planning—built into the same control tower environment—so planners could run “what-if” simulations quickly (for example, modeling demand increases and impacts on raw materials and production capacity). Exxon Mobil framed the effort as a marathon: a staged build that kept funding alive by demonstrating measurable inventory and service improvements.

The reproductive health supply chain network (van), hosted by the Reproductive Health Supplies Coalition, approached control tower value from a public-health resilience angle. The network’s visibility platform enabled real-world redistribution during disruptions such as Cyclone Idai, where delays in Mozambique threatened stockouts across thousands of kilometers. The van’s scale—nearly 100 member organizations, including 35 governments—supports tracking thousands of shipments and orders across hundreds of products and countries. Its impact was quantified through decisions that expedited shipments and transfers, mobilized additional funding after geopolitical shocks, and helped prevent stockouts during the pandemic.

Lessons learned from van emphasized that a control tower is a multi-enterprise network requiring governance, data harmonization, and decision-making capacity—not just dashboards. Stu Strummel highlighted the need for “drum beat” alignment (harmonizing the cadence of data readiness with planning cycles) and warned that data must be actionable when it arrives. Abbott’s story reinforced a more pragmatic approach: starting from a manual “war room” during performance issues, then digitizing and standardizing KPI reporting using Power BI and Microsoft tools, linking control tower outputs to S&OP rhythms, escalation processes, and risk monitoring. Across all three, success depended on people-first operating models, ongoing master data management, and process integration that makes exceptions manageable and decisions faster.

Cornell Notes

Control towers turn supply chain visibility into coordinated action by uniting data, processes, and decision rights across multiple organizations. Exxon Mobil built a global, cloud-based end-to-end tower for lubricants, addressing disconnected regional systems and manual exception handling through agile delivery, supplier connectivity, and event-based alert management. The van (hosted by the Reproductive Health Supplies Coalition) demonstrated how a multi-enterprise visibility network supports resilience during disruptions, enabling shipment and transfer decisions that avert stockouts and even mobilize new funding. Across both cases, “visibility isn’t enough”: governance, data harmonization (including master data management), and harmonized planning cadences (“drum beat”) are what make alerts usable and decisions repeatable. Abbott’s approach showed that even with simpler tooling, linking dashboards to S&OP cycles and escalation processes can operationalize a control tower.

What makes a supply chain control tower more than a dashboard?

Across the cases, the differentiator is decision-making capability tied to governance and process. Exxon Mobil moved from reactive, manual exception management to event-based prioritization: alerts are grouped into events, ownership and root causes are assigned, and planners collaborate across functions and regions. The van similarly frames the tower as a multi-enterprise decision platform—visibility is used to coordinate actions like transfers and schedule rebalancing. Abbott’s control tower also emphasizes operational rhythms: KPI dashboards feed daily/weekly/monthly meetings, escalation processes, and S&OP cycles, turning monitoring into managed response.

Why did Exxon Mobil choose a global rollout instead of starting region-by-region?

Exxon Mobil’s ERP and planning tools were deployed separately across Asia Pacific, the Americas, and Europe Middle East and Africa, with no direct connection between instances. That fragmentation created process and alignment issues. To avoid building a tower that worked only in one region, the company decided early to plan and execute globally so the control tower would be “fit for purpose” across all regions with one set of procedures and a consistent operating model.

How does the “drum beat” concept affect control tower effectiveness?

Stu Strummel described “drum beat” as aligning the cadence of expectations and data readiness across the network with the planning process. If data arrives faster but isn’t cleaned, harmonized, and locked at the right moments, planners end up using stale or unusable information—creating chaos rather than faster decisions. Julia White added a metaphor: data should be prepared like canal locks—there are moments when data is cleaned and made actionable, so planners can make decisions confidently.

What role does master data management play in multi-enterprise control towers?

Master data management is treated as a critical path item because control towers aggregate information from many parties with potentially competing definitions. Stu emphasized that data must be continuously kept clean; otherwise, “day two” becomes a mess again. The van also highlighted master data harmonization as foundational, including building a Master catalog to manage differing data definitions across organizations. Abbott similarly stressed data cleanup before automation so KPIs and reporting could be standardized.

How did the van demonstrate measurable value during disruptions?

The van used visibility to support concrete actions during geopolitical and pandemic shocks. After a 2021 UK government aid cut created funding shortfalls, the network used data to identify gaps and advocate for additional procurements and donations, helping avert unintended pregnancies. During COVID-era logistics constraints, the van supported transfers between countries and schedule rebalancing. A specific example involved diverting a shipment destined for Nigeria to Zambia when Nigerian ports closed, avoiding expiration risk and port fees. Aggregated results in 2021 included expedited shipments and transfers valued over $10 million and stockout prevention in 19 countries.

How did Abbott operationalize its control tower using existing tools?

Abbott started with a crisis-driven, manual “war room” that collected KPIs on paper. The control tower digitized and standardized that process by centralizing global supply chain reporting and linking it to the executive S&OP process. Abbott used Power BI dashboards and Microsoft packages to avoid investing in entirely new software, then broadcast KPIs through a Power BI app. The tower also supported risk and resilience monitoring and defined escalation processes for disruptions, with reporting structured into daily, weekly, and monthly cycles.

Review Questions

  1. What governance and process elements are necessary to convert supply chain alerts into decisions, and why does visibility alone fall short?
  2. Compare how Exxon Mobil, the van, and Abbott each integrated control tower outputs into their operating rhythms (planning cycles, governance meetings, or S&OP).
  3. Why is data harmonization (including master data management) especially difficult in multi-enterprise networks, and what operational failures can result if it’s neglected?

Key Points

  1. 1

    A control tower’s value comes from orchestrating data, people, and processes so exceptions are prioritized and owned—not from dashboards alone.

  2. 2

    Exxon Mobil’s global rollout addressed disconnected regional ERP/planning instances by building one end-to-end operating model across regions.

  3. 3

    Agile, staged delivery helped Exxon Mobil release capabilities early (single source of truth, supplier connectivity, event management) while keeping funding through measurable benefits.

  4. 4

    The van demonstrated resilience value by enabling multi-country decisions such as transfers and schedule rebalancing during disruptions, supported by a trusted neutral convening partner.

  5. 5

    “Drum beat” alignment matters: the cadence of data readiness must match planning cycles so information is actionable when decisions are made.

  6. 6

    Master data management is foundational and ongoing; competing definitions across organizations can break aggregation and analysis.

  7. 7

    Abbott’s approach shows that even with simpler tooling, linking KPI reporting to S&OP rhythms, escalation processes, and risk monitoring can operationalize a control tower.

Highlights

Exxon Mobil shifted from manual firefighting to event-based exception management where alerts are grouped, ownership is assigned, and root causes are addressed.
The van used visibility to redirect and redistribute health products during disruptions—turning data into actions like expedited shipments and cross-country transfers.
Stu Strummel’s “drum beat” warning: real-time data only helps if it’s cleaned, harmonized, and locked into the planning cadence planners can use.
Abbott’s “war room to Power BI” path shows a practical route to control tower adoption by standardizing KPIs and embedding them into S&OP cycles.

Topics

  • Supply Chain Control Towers
  • Multi-Enterprise Governance
  • Exception Management
  • Scenario Planning
  • Master Data Management

Mentioned

  • Marisa Brown
  • Carolyn Zurakowski
  • Julia White
  • Stu Strummel
  • Andreas Galler
  • ERP
  • S&OP
  • van
  • API
  • ROI
  • KPI
  • SLA
  • AI
  • ML