GoKawiilHarish: 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 we have put down because we don't want to keep moving data from one place to the other. That's not good business practice in the IT world. Most of our integration architectures are API-driven and event-based. That is our focus.
Coming back to your new technologies perspective, we want to reuse as much as possible and standardize versus going out and buying these one-off tools that solve for point-in-case use cases. We really don't want to go down that path. For major processes, we do adopt a best-of-breed approach, but for, let's say, site-based use cases where a specific site has a particular need for a tool, we try and standardize that and reuse what exists in a different site, for example. There may be some need for a business process change, minor process changes, but that is our direction to make those process changes and reuse what is there already in a different location or a different region. So, that's one.
Lastly, we are heavily aligned with SAP's clean-core approach when it comes to customization. That has been the challenge for us over the last 25 years where we have been using SAP is our systems are heavily customized because we cater to different customers across the globe. Most of our demands are customer-driven, so we have to put in play these heavy customizations.
But now we are taking a pause, and we are saying, "You know what? We have customized so much so far, but now we are moving our systems into RISE, which would enable a clean-core journey in the future." Now we have to put really good governance criteria and review processes that do not allow heavy customization of our system. We want to move away from that model as much as possible. Again, it's not easy to do that at this point in time, but there is always a start.
Megan: I mean, it sounds like you took a very incremental, intentional approach to this. I mean, as you scaled globally then, what did modernization really look like at the company, and why start with integration?