AI Integration Made Simple at Scale

Share

As companies grow, the very technology that powers their operations can shift from an asset to a bottleneck. Disconnected systems, site-specific tools, spreadsheets, and manual workarounds create data silos that obscure early warning signs, slow down coordinated responses, and undermine confident decision-making. Jabil, a global manufacturer operating more than 100 sites across 30-plus countries, has responded by putting integration and simplification at the center of its strategy.

The company operates with a “simplify-first, then-innovate” mindset, explains Harish Manohar, SAP IT Director at Jabil. The logic is straightforward: layering new technology onto an already complex environment multiplies risk. The focus is on standardizing processes, consolidating systems, and building a consistent data backbone. As Manohar puts it, “Any innovation without simplification is going to add more complexity.”

This principle also shapes Jabil’s approach to modernization. “Any modernization or transformation should add measurable business value,” Manohar says. The company is working to connect processes end-to-end across the supply chain and build a foundation that can scale region by region. Integration leads the way because, as Manohar notes, “the backbone of any contemporary or modern organization is data.” Before optimization, automation, or AI can take hold, data must move seamlessly between systems.

Executing that across a global enterprise is rarely straightforward. Jabil’s 100-plus sites operate with varying levels of process maturity, a mix of legacy systems, and localized workflows. Regulated businesses add another layer of compliance complexity. Standardizing across regions means changing processes and governance without disrupting operations that are already running.

The payoff reaches beyond the IT stack to the people using it. Integrated workflows give employees shared visibility into data, cut down on manual reconciliation, and help teams move from hunting for information to acting on it. For Jabil, that translates into better real-time visibility into supply chain events, faster responses to disruptions, and lower operational risk.

Looking ahead, that foundation is what makes AI and automation practical at scale. With trusted data and connected systems in place, Jabil is exploring predictive supply chain insights, intelligent exception handling, and AI-driven planning and forecasting. Manohar’s takeaway is straightforward: “Simplicity at scale is a very competitive advantage,” and technology investments must tie back to business value and operational resilience.

This episode of Business Lab is produced in partnership with SAP.

Full Transcript:

Megan Tatum: From MIT Technology Review, I’m Megan Tatum, and this is Business Lab, the show that helps business leaders make sense of new technologies coming out of the lab and into the marketplace.

Our topic today is enterprise technology integration, and how consolidating tools and systems across the supply chain helps organizations operate more reliably at scale. When companies reduce tool sprawl and connect their systems more effectively, they gain earlier visibility, faster response, and greater resilience across production lines.

My guest today is Harish Manohar, SAP IT Director at Jabil. Jabil has been simplifying its technology landscape, using SAP Integration Suite as the foundation to connect systems, retire fragmented tools, and enable more consistent operations globally.

This podcast is produced in partnership with SAP.

Welcome, Harish.

Harish Manohar: Hello, Megan. Good morning.

Megan: Thank you for being here, Harish. To start, could you give us a quick overview of Jabil, the business, and its overall transformation journey?

Harish: About Jabil: we are a global manufacturing company headquartered in St. Petersburg, Florida, USA. We have about 60 years of experience offering comprehensive engineering, supply chain, and manufacturing solutions across different industries. Our global footprint spans over 100 sites across 30-plus countries, with more than 140,000 employees.

We are a trusted partner for more than 400 of the world’s top brands. That’s a little about Jabil.

Megan: Fantastic, and clearly a lot of scale there. As things got more complex, where did disconnected tools and systems start to slow you down, and what ultimately drove you to make integration a strategic priority?

Harish: With a global footprint of 100-plus sites comes complexity from site-specific tools. Many of our sites have been operating for a long time, and over the years they built their own tools for their own processes. It’s a bit disconnected.

When we looked at scaling, the first thing we examined was that mix of site-specific tools, manual workarounds, spreadsheet-based processes, and legacy applications. That is significant technical debt accumulated over the last 25 years. That’s where we started, and it’s what made integration a strategic priority. We had limited ability to spot issues early across plants and regions, which prevented us from coordinating responses consistently. This complexity created data silos and, in a way, delayed robust decision-making.

As complexity increased globally, integration became critical to establishing a single trusted data backbone — one that enables faster, coordinated responses across the network. At Jabil, we believe having the right data at the right time fundamentally changes how we respond to disruptions, which is the core of a manufacturing business. That’s where our strategic priority toward an integrated system that drives data consistency across our landscape began.

Megan: There was clearly a commercial need for this. How did you think about bringing in new technologies without adding even more complexity?

Harish: Whenever we talk about transformation, we hear about bleeding-edge technologies — AI, data, cloud, and so on. But it was important for us to put a stake in the ground and adopt a simplify-first, then-innovate mindset. Any innovation without simplification is going to add more complexity.

For us, SAP is our core digital platform. We want to bring more processes into SAP wherever possible. That’s easier said than done — we’ve been in business a long time, and not all processes live in SAP today. We are working to standardize those processes, and having them under one source of data helps us scale faster and avoid data silos across different systems.

This is where we started introducing newer SAP capabilities. From a cloud standpoint, we’ve been using SAP BTP and Integration Suite, which is becoming the center stage for integrations across Jabil. It’s not fully there yet, but the direction is clear: we don’t want a slew of different integration platforms. We want to see where Integration Suite fits best and where smaller platforms add more value.

Similarly, we’ve adopted an API-driven, event-based integration approach as our best practice. We don’t want to keep moving data from one place to another — that’s not good business practice in IT. Most of our integration architectures are API-driven and event-based.

On the new technologies front, we want to reuse and standardize as much as possible, rather than buying one-off tools that solve point-in-time use cases. For major processes, we adopt a best-of-breed approach. But for site-based use cases where a specific location has a particular need, we try to standardize and reuse what already exists at another site. There may be minor business process changes required, but our direction is to make those changes and reuse what’s already in place elsewhere.

Lastly, we are heavily aligned with SAP’s clean-core approach regarding customization. That has been our challenge over the last 25 years — our systems are heavily customized because we serve different customers globally. Most demands are customer-driven, so we’ve had to implement heavy customizations.

Now we’re pausing and saying, “We’ve customized so much so far, but we’re moving our systems into RISE, which enables a clean-core journey.” We need strong governance and review processes that prevent heavy customization of our system. We want to move away from that model as much as possible. It’s not easy to do overnight, but there’s always a start.

Megan: It sounds like you took a very incremental, intentional approach. As you scaled globally, what did modernization look like in practice, and why start with integration?

Harish: We’ve always looked at transformation and modernization objectively. For us, it’s not just about upgrading a system — that’s not the point. Any modernization or transformation should add measurable business value; that’s our charter. We don’t look at modernization in terms of upgrades alone, but in terms of what it delivers to the business.

Most of our modernization approaches focus on connecting processes end-to-end across the supply chain, which is key to business value. We also have a concerted effort to standardize how our plants operate globally. With 100-plus plants, different processes, regulations, and countries, it’s hard to create one global template. But we’re trying to standardize as much as possible. That’s where we’re leveraging SAP Signavio, our business process management tool, to help standardize these global processes.

Why did integration come first? Because data is the backbone of any modern organization. To get the right data at the right time, integration is the key enabler. Data needs to flow seamlessly before we can optimize, automate, or apply AI use cases.

We wanted to create a single system of record across operations. When I say “single system of record,” it’s not just SAP — it’s the ability to create data pipelines across systems of record in supply chain, planning, inventory, and the broader operational space.

The result we’re aiming for is a foundation that helps us scale consistently across regions. How do we set up a foundation that supports growth as we expand across industries? Simplicity and consolidation become strategic assets at scale.

Megan: You’ve touched on some complexities of operating at Jabil’s scale. What were the biggest challenges in rolling this out across regions, and how did the standardized approach help?

Harish: Let me reiterate the key challenges. One hundred-plus sites, each with different maturity levels in how they approach processes. They have a multitude of legacy systems, localized processes, workarounds, and spreadsheets. Change management differs at each site. We also have a footprint of highly regulated businesses, which brings its own challenges around qualification and CSV processes.

Standardization helps us provide consistent workflows, data flows, and governance across sites. We’re not at 100%, but we’re working toward it. And it enables faster rollouts of new technologies. Traditionally, deploying tools like SAP BTP or Signavio required heavy customization for each site. Standardization removes that burden, which accelerates deployment.

Ultimately, we want to scale across all our plants. Initially, the target is about 40-plus plants with shared processes consistent across regions. We want to shift from a site-by-site operations model to an enterprise-capability approach.

Megan: You’ve mentioned the people side of this. How did the shift to a more simplified landscape change the day-to-day experience for employees compared to juggling multiple tools?

Harish: I’ve heard direct feedback from our business community on how these initiatives have changed their daily work significantly. Before this transformation, any persona — a buyer, inventory planner, or finance analyst — had to deal with multiple tools, manual coordination, and data reconciliation, especially in finance. Inconsistent processes across regions meant time spent reconciling data delayed robust decision-making. That was the “before.”

Now, with standardization and integration, we’re achieving single integrated workflows across systems to a certain extent. We’ve built key processes for this. Users across roles have clear visibility and shared data within their teams. Previously, they dealt with different versions of data, local workbooks, and spreadsheets, spending time reconciling what the right data was and where the single source of truth lived. We’re peeling that layer away so employees don’t have to deal with that complexity.

This reduces manual effort and enables faster issue resolution during disruptions. Employees shift from chasing information to acting on insights — which is where AI comes into play. Technology becomes an enabler of decision-making, not an overhead.

Megan: With an initiative this scale, ROI is always front and center. What benefits stood out most, and how important was better visibility across systems?

Harish: For Jabil, modernization means measurable business value, which is directly connected to ROI. We don’t undertake transformation initiatives just for the sake of IT. Any investment must have a deliverable business case approved and signed off by the business. True transformation only happens when IT and business partner together.

The biggest benefit we’ve seen is real-time visibility across supply chain events. That’s the most significant outcome. It enables faster response to disruptions and exceptions, and we’re working to reduce operational risk significantly under this model.

One example is the unified workflows I mentioned. They enabled earlier identification of missing materials and faster resolution across sites. For a global manufacturing company, materials are the backbone of the supply chain. A unified workflow that identifies missing materials early was a game changer for our operations community.

Real-time analytics allow instant supply chain adjustments without delays. We’re focused on building a global analytics footprint that enables that. This is where AI will play a major role, both now and in the near future.

On visibility: it’s not just about reporting what’s in the system. Visibility should enable scenario modeling for users to make strategic adjustments. It should support proactive decision-making and foster business continuity. That’s how we define visibility at Jabil.

Megan: Now that Jabil has a solid integration foundation, what does it unlock next, and how are you thinking about AI and automation?

Harish: We strongly believe a strong integration foundation enables event-driven, real-time processes, robust decision-making, and scalable automation — all of which accelerate AI adoption. We’re moving toward an AI-enabled enterprise, and having these foundations in place truly fast-tracks our AI use cases.

Our key focus areas for AI and automation in the immediate future are predictive supply chain insights and intelligent exception handling, which is critical for site operations. On the supply chain side, predictive insights are absolutely important. All of this enables AI-driven planning and forecasting.

For us, AI should augment genuine decision-making and deliver measurable value — not just serve as an experiment. We want to move beyond piloting AI in business processes to implementing AI that truly enhances decision-making and delivers business value.

How does this connect to integration? Integration ensures AI has access to trusted data and can act across multiple systems in a global company like Jabil.

Megan: To finish, what advice would you offer other leaders dealing with tool sprawl, based on what you’ve learned about prioritizing integration from the start?

Harish: Tool sprawl can appear in many areas — application development, integration, data. But let’s focus on integration, the core topic here.

My recommendation to those in transformation roles: start with integration as a foundation, not an afterthought. Prioritize simplification over adding more tools to address different capabilities. Simplify as much as possible before starting an upgrade or transformation journey. Standardize over locally optimizing tools. Help your business community and key SMEs understand how standardization enables faster value delivery.

Second, build a single source of truth for data wherever possible. I’m not saying an organization at Jabil’s scale can run entirely on SAP — there will always be different systems. But work toward a model with a single source of truth, not locally siloed data sources.

Next, focus on building a scalable integration architecture. Don’t limit yourself to the current state and build something that only serves you for the next six months. Anything you build should be scalable and serve the organization for the next three to five years. When I’m designing a new architecture pattern or event-driven insight, I ask, “Where will Jabil be in two or three years? Will this support that scale?”

Finally, focus on outcomes, not just technology. Think speed, visibility, and resilience — not just deployment. At the end of the day, IT and business should partner on business value, not technology upgrades alone.

Going back to the core principle: simplicity at scale is a competitive advantage, and technology investments must tie directly to business value and operational resilience. That’s how we approach tool sprawl and integration at Jabil, and that’s what I’d suggest to other leaders.

Megan: Brilliant and very comprehensive advice. Thank you, Harish. That was Harish Manohar, SAP IT Director at Jabil, whom I spoke with from Brighton in England.

That’s it for this episode of Business Lab. I’m your host, Megan Tatum, a contributing editor at Insights, the custom publishing division of MIT Technology Review. We were founded in 1899 at the Massachusetts Institute of Technology, and you can find us in print, on the web, and at events each year around the world. For more information about us and the show, visit our website at technologyreview.com.

This show is available wherever you get your podcasts. If you enjoyed this episode, please take a moment to rate and review us. Business Lab is a production of MIT Technology Review, and this episode was produced by Giro Studios. Thanks for listening. Goodbye.

This content was produced by Insights, MIT Technology Review’s custom content arm, not its editorial staff. It was researched and written by humans, with any AI tools that may have been used limited to production processes under human oversight.

Read more