메뉴
BL
MIT Tech Review • 23일 전

단순함으로 대규모 AI 통합 실현하기

IMP
4/10
핵심 요약

MIT 테크놀로지 리뷰가 SAP와 공동 제작한 팟캐스트에서, 글로벌 제조기업 재빌(Jabil)의 SAP IT 디렉터 하리시 마노하르는 '먼저 단순화하고 그다음 혁신한다'는 전략으로 30개국 100개 이상 사업장의 시스템을 통합하는 여정을 소개한다. 검증된 데이터 기반과 통합 시스템 위에서 예측형 공급망 인사이트, 지능형 예외 처리, AI 기반 계획·예측 등 AI 활용을 확장할 수 있으며, 이러한 대규모 단순화가 곧 경쟁 우위라고 강조한다.

번역된 본문

후원 콘텐츠 (SAP와 공동 제작)

기업이 성장함에 따라 운영을 지원하는 기술은 자산이 되는 만큼 빠르게 부담이 될 수도 있습니다. 단절된 시스템, 사업장별 도구, 스프레드시트, 수작업 우회 처리 등은 데이터 사일로를 만들어 문제를 조기에 발견하고, 대응을 조율하고, 확신을 갖고 의사결정을 하기 어렵게 만듭니다.

30개국 이상에 100개 이상의 사업장을 둔 글로벌 제조기업 재빌(Jabil)의 해답은 통합과 단순화를 우선순위로 삼는 것이었습니다. 재빌의 SAP IT 디렉터인 하리시 마노하르는 회사가 '먼저 단순화하고, 그다음 혁신한다(simplify-first, then-innovate)'는 사고방식을 채택했다고 말합니다. 복잡성을 먼저 줄이지 않은 채 새 기술을 추가하면 오히려 리스크가 커질 수 있다는 인식에서입니다. 목표는 프로세스를 표준화하고, 가능한 곳은 통합하며, 조직 전반에 걸쳐 더 일관된 데이터 기반을 구축하는 것입니다.

"단순화 없는 혁신은 복잡성만 더할 뿐"이라고 마노하르는 말합니다. 이 철학은 재빌이 현대화(modernization)에 접근하는 방식도 바꿔놓았습니다. "어떤 현대화나 전환이든 측정 가능한 비즈니스 가치를 더해야 한다"며, 회사는 공급망 전반에서 프로세스를 엔드투엔드로 연결하고 지역 간에 일관되게 확장 가능한 기반을 만드는 데 집중하고 있습니다.

통합이 우선인 이유는, 마노하르의 표현대로 "현대 조직의 근간은 데이터"이기 때문입니다. 조직이 최적화, 자동화, AI를 적용하기 전에 데이터가 시스템 간에 원활하게 흘러야 합니다. 하지만 글로벌 조직에서 이를 실행하는 것은 결코 간단하지 않습니다. 재빌의 100개 이상 사업장은 각기 다른 수준의 프로세스 성숙도, 레거시 시스템, 현지화된 업무 흐름으로 운영되며, 규제 대상 사업부문은 추가적인 컴플라이언스 요건을 가져옵니다. 따라서 서로 다른 지역과 비즈니스 환경에서 표준화한다는 것은 기존 운영을 방해하지 않으면서 프로세스와 거버넌스를 변경한다는 의미입니다.

이러한 작업의 가치는 기술을 넘어 그것을 사용하는 사람에게까지 확장됩니다. 통합된 업무 흐름은 직원들에게 데이터에 대한 공유 가시성을 제공하고, 수작업 데이터 대사(reconciliation)를 줄이며, 정보를 쫓아다니는 것에서 인사이트에 기반해 행동하는 것으로 전환하도록 돕습니다. 재빌의 목표는 공급망 이벤트에 대한 실시간 가시성을 높여 중단 상황에 더 빠르게 대응하고 운영 리스크를 줄이는 것이기도 합니다.

미래를 보면, 이러한 기반은 AI와 자동화를 더욱 유용하고 확장 가능하게 만들 수 있습니다. 신뢰할 수 있는 데이터와 통합된 시스템을 갖춘 재빌은 예측형 공급망 인사이트, 지능형 예외 처리, AI 기반 계획 및 예측을 탐구하고 있습니다. 마노하르에게 교훈은 분명합니다. "대규모 단순함(simplicity at scale)은 매우 강력한 경쟁 우위"이며, 기술 투자는 궁극적으로 비즈니스 가치와 운영 탄력성으로 연결되어야 한다는 것입니다.

본 에피소드는 SAP와 공동 제작되었습니다.

전체 스크립트:

메건 테이텀(Megan Tatum): MIT 테크놀로지 리뷰의 메건 테이텀입니다. Business Lab은 연구실에서 나와 시장으로 들어오는 새로운 기술을 비즈니스 리더가 이해하도록 돕는 쇼입니다. 오늘 주제는 기업 기술 통합, 그리고 공급망 전반에서 도구와 시스템을 통합할 때 얻는 이점이 조직이 대규모로 더 안정적으로 운영되도록 돕는 방식입니다. 기업이 도구 난립(tool sprawl)을 줄이고 시스템을 더 효과적으로 연결하면 생산 라인 전반에서 더 이른 가시성, 더 빠른 대응, 더 큰 탄력성을 얻게 됩니다.

오늘의 게스트는 재빌의 SAP IT 디렉터 하리시 마노하르입니다. 재빌은 SAP 통합 스위트(Integration Suite)를 기반으로 시스템을 연결하고 분산된 도구를 폐기하며 전 세계적으로 더 일관된 운영을 가능하게 하며 기술 환경을 단순화하는 여정을 걸어왔습니다. 본 팟캐스트는 SAP와 공동 제작되었습니다. 하리시, 환영합니다.

하리시 마노하르(Harish Manohar): 안녕하세요, 메건. 좋은 아침입니다.

메건: 와주셔서 감사합니다, 하리시. 먼저 배경을 좀 깔기 위해, 재빌이라는 기업과 전반적인 전환 여정에 대해 간략히 소개해 주시겠어요?

원문 보기
원문 보기 (영어)
Sponsored In partnership with SAP As companies scale, the technology supporting operations can become a liability just as quickly as it becomes an asset. Disconnected systems, site-specific tools, spreadsheets, and manual workarounds can create data silos that make it harder to spot problems early, coordinate responses, and make decisions with confidence. For Jabil, a global manufacturing company with more than 100 sites across more than 30 countries, the answer has been to make integration and simplification a priority. The company adopted a “simplify-first, then-innovate mindset,” says Harish Manohar, SAP IT director at Jabil, recognizing that adding new technologies without first reducing complexity risks creating more risk. The goal is to standardize processes, consolidate where possible, and establish a more consistent data backbone across the organization. “Any innovation without simplification is going to add more complexity,” Manohar says. That philosophy also changes how Jabil approaches modernization. “Any modernization or transformation should add measurable business value,” Manohar says. The company is focused on connecting processes end-to-end across its supply chain and creating a foundation that can scale consistently across regions. Integration comes first because, as Manohar puts it, “the backbone of any contemporary or modern organization is data.” Before organizations can optimize, automate, or apply AI, data needs to flow seamlessly across systems. But doing that across a global organization is hardly straightforward. Jabil’s more than 100 sites operate with different levels of process maturity, legacy systems, and localized workflows, while regulated businesses bring additional compliance requirements. As such, standardizing across different regions and business environments means changing processes and governance without disrupting the operations already in place. The value of that work extends beyond the technology to the people using it. Integrated workflows can offer employees shared visibility into data, reduce manual data reconciliation, and help them move from chasing information to acting on insights. For Jabil, the aim is also to improve real-time visibility into supply chain events, which can enable faster responses to disruptions and reduce operational risk. Looking to the future, that foundation could make AI and automation all the more useful and scalable. With trusted data and integrated systems in place, Jabil is exploring predictive supply chain insights, intelligent exception handling, and AI-driven planning and forecasting. To Manohar, the takeaway is clear: "Simplicity at scale is a very competitive advantage,” and technology investments must ultimately connect 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 the benefits of consolidating tools and systems across the supply chain help 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 on a journey to simplify its technology landscape by 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 so much for being here, Harish. Just to start, if we could set some context, can you give us a quick overview of Jabil, the business and its overall transformation journey? Harish: All right. So, about Jabil. Jabil is 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. We have a global footprint of about over 100 different sites across 30-plus countries, 140,000-plus employees. We are a trusted partner for more than 400 of the world's top brands. That's a little bit about Jabil. Megan: Fantastic. And a lot of scale there, as you're referring to some of the stats there. As things have got more complex, where did disconnected tools and systems start to slow you down, and what ultimately drove you to make integration a really strategic priority? Harish: I talked about our global footprint across 100-plus sites. With a global footprint always comes complexity about site-specific tools. All of our sites have been in business for a long time, and over the period of years, they had their own tools for their own processes. It's a little bit disconnected. When we are looking to scale, the first thing we wanted to start looking at is what is this mix of site-specific tools, manual workarounds, spreadsheet-based processes, legacy applications, whatnot? That's a big technical debt that we have had over the last 25 years. That's where we started, and that is what led Jabil to make integration a strategic priority because we had limited ability to see issues early across plants, across regions, which would help us to coordinate responses consistently, and also to be able to scale those responses consistently. This complexity created data silos, and in a way delayed robust decision-making. As the complexity increased globally, integration became extremely critical to a few things. It was critical to establishing a single trusted data backbone, which would directly enable faster coordinated responses across the network. We at Jabil, as part of our transformation journey, believe that having the right data at the right time fundamentally changes how we respond to disruptions, which is all about a manufacturing business. How we respond to disruptions. This is where we started our strategic priority towards having a integrated system that drove data consistency across our landscape. Megan: Fantastic. As you have outlined there, there was obviously a real commercial need for this, but how did you think about bringing in those new technologies without adding even more complexity to the mix? Harish: Great question. Whenever we talk about transformation, we talk about all these bleeding-edge technologies that are out there today when it comes to AI and data, cloud, et cetera. But it was very important for us to put a stake in the ground and say and adopt a simplify-first, then-innovate mindset. Because any innovation without simplification is going to add more complexity, just like you mentioned. For us, SAP is our core digital platform. We want to focus on bringing more processes into SAP as much as possible. That is easier said than done because we have been in business for a while, global company, so not all processes exist within SAP at this point in time. We are slowly trying to standardize those processes, and having them under one single source of data would help us scale faster in terms of having data silos. We don't want data silos across different systems. This is where we started to introduce newer capabilities around SAP. From a cloud standpoint, we have been using SAP's BTP and Integration Suite, which is proving to be the center stage of all integrations across Jabil. Well, it's not there yet, but that is the direction that we want to pursue is we don't want to have a slew of different integration platforms, rather try and see where Integration Suite fits best and where other smaller integration platforms would add more value. Similarly, we have adopted an API-driven, event-based integration approach. That is our best practice that w