WEBVTT 00:00:09.720 --> 00:00:12.740 Welcome to the Tech Arena, featuring authentic 00:00:12.740 --> 00:00:15.339 discussions between tech's leading innovators 00:00:15.339 --> 00:00:20.179 and our host, Alison Klein. Now let's step into 00:00:20.179 --> 00:00:25.269 the arena. Welcome in the arena. My name is Alison 00:00:25.269 --> 00:00:29.030 Klein. And today, we are very excited to be joined 00:00:29.030 --> 00:00:32.090 by two business leaders that are making waves 00:00:32.090 --> 00:00:35.689 in the tech sector. Andrea Cesarini, Accenture 00:00:35.689 --> 00:00:38.609 Oracle Business Group EMEA lead, and Andrew De 00:00:38.609 --> 00:00:41.469 La Torre, Group Vice President of Technology. 00:00:41.789 --> 00:00:43.850 Welcome to the program, Andrea and Andrew. How 00:00:43.850 --> 00:00:47.409 are you doing? Very well. Thanks for having us 00:00:47.409 --> 00:00:50.070 today with you. Yep. Same here, Alison. It's 00:00:50.070 --> 00:00:52.270 great to be here. Thank you. So why don't we 00:00:52.270 --> 00:00:55.250 just start with introductions about your roles 00:00:55.250 --> 00:01:00.149 and how you fit into the broader purview of each 00:01:00.149 --> 00:01:02.210 of your respective companies. Andrea, why don't 00:01:02.210 --> 00:01:05.250 we start with you? Always a pleasure to start. 00:01:05.609 --> 00:01:08.510 So Andres Isarini, I'm actually joining Accenture 00:01:08.510 --> 00:01:12.629 27 years now. And I think that I started from 00:01:12.629 --> 00:01:15.790 understand consulting and the majority of my 00:01:15.790 --> 00:01:18.370 career has been in the telco industry, been in 00:01:18.370 --> 00:01:22.420 the telco industry around 23 years, working always 00:01:22.420 --> 00:01:25.079 abroad, which is an interesting, because I've 00:01:25.079 --> 00:01:27.799 been almost everywhere and always in a transformation 00:01:27.799 --> 00:01:30.620 where Oracle has had an important role. Four 00:01:30.620 --> 00:01:33.920 years ago, I took the role of the Oracle lead 00:01:33.920 --> 00:01:38.599 for EMEA and I'm also the Oracle Global CTO looking 00:01:38.599 --> 00:01:42.159 after the strategy and the roadmap and the way 00:01:42.159 --> 00:01:45.260 we invest jointly together with Oracle in order 00:01:45.260 --> 00:01:48.920 to address the client needs. And Andrew? My name 00:01:48.920 --> 00:01:51.640 is Andrew Doherty. I'm also on the wrong side 00:01:51.640 --> 00:01:55.040 of 25 years in this industry, so I've been around 00:01:55.040 --> 00:01:57.980 quite a while. I've done a variety of roles in 00:01:57.980 --> 00:02:00.680 the communications sector from strategy roles 00:02:00.680 --> 00:02:03.700 into chief technology officer roles. Here at 00:02:03.700 --> 00:02:06.640 Oracle now, I'm a group vice president of technology. 00:02:06.780 --> 00:02:09.919 I'm responsible for the product strategy of the 00:02:09.919 --> 00:02:12.849 communications business. Oracle Communications 00:02:12.849 --> 00:02:15.949 is a part of Oracle, which is one of our industry 00:02:15.949 --> 00:02:19.069 -specific business units, and we're focused on 00:02:19.069 --> 00:02:22.129 the communications sector. I was really excited 00:02:22.129 --> 00:02:24.990 for this industry because both of your companies 00:02:24.990 --> 00:02:27.629 have such an incredible impact on the industry, 00:02:27.629 --> 00:02:29.189 and I really wanted to hear what you were doing 00:02:29.189 --> 00:02:33.289 in the telco arena. And Andrea, we have witnessed 00:02:33.289 --> 00:02:36.110 a complete transformation of telco in the last 00:02:36.110 --> 00:02:39.789 decade, and this transformation is based on an 00:02:39.789 --> 00:02:44.199 ongoing pursuit as telco operators leverage compute 00:02:44.199 --> 00:02:47.539 to deliver cloud -like control and agility to 00:02:47.539 --> 00:02:50.840 their networks and open up new monetization streams 00:02:50.840 --> 00:02:54.080 and efficiency for themselves. Where are we on 00:02:54.080 --> 00:02:57.900 this journey in your estimation? I think, Alison, 00:02:58.300 --> 00:03:01.379 the telco industry, it has been an incredible 00:03:01.379 --> 00:03:04.159 industry, always been at the forefront of innovation 00:03:04.159 --> 00:03:06.860 and technology. But I think I like let's say, 00:03:06.960 --> 00:03:09.599 to shape the answer according to three different 00:03:09.599 --> 00:03:12.860 phases, what was pre -pandemic, during the pandemic 00:03:12.860 --> 00:03:15.419 and post -pandemic, just to highlight the key 00:03:15.419 --> 00:03:18.580 role of telco in this place. I think there was 00:03:18.580 --> 00:03:20.580 an important transformation already started. 00:03:20.699 --> 00:03:23.539 During the pandemic, I think the telco demonstrated 00:03:23.539 --> 00:03:26.240 to be the backbone of every other industry. And 00:03:26.240 --> 00:03:29.000 now I think that the disruption is happening 00:03:29.000 --> 00:03:31.300 even more because, of course, it's clear how 00:03:31.300 --> 00:03:34.020 much is important the connectivity and how the 00:03:34.020 --> 00:03:37.300 telco can become. more important in enabling 00:03:37.300 --> 00:03:40.580 also the adhesion industry. If you look at what 00:03:40.580 --> 00:03:43.490 happened... In Europe, but actually in EMEA, 00:03:43.550 --> 00:03:46.169 if you like, what I see is that there has been 00:03:46.169 --> 00:03:49.870 multiple trends that were involving about monetizing 00:03:49.870 --> 00:03:52.289 the network, because I think one of the most 00:03:52.289 --> 00:03:55.629 important subjects after having invested massively 00:03:55.629 --> 00:03:59.310 in 5G was to try to separate the network for 00:03:59.310 --> 00:04:02.449 the SelfCo, so the service company. I think that 00:04:02.449 --> 00:04:05.810 there is still a cost optimization, because I 00:04:05.810 --> 00:04:08.250 think this is an industry that has been caught 00:04:08.250 --> 00:04:11.689 in a commoditization conundrum with... growth. 00:04:12.189 --> 00:04:14.830 Nonetheless, I think that again remain the most 00:04:14.830 --> 00:04:17.329 important industry because it's where you can 00:04:17.329 --> 00:04:20.449 exploit the new technology. I think that we will 00:04:20.449 --> 00:04:23.449 discuss, I believe later about the importance 00:04:23.449 --> 00:04:26.889 of generative AI and also about the importance 00:04:26.889 --> 00:04:29.790 of cloud. So I think that there is a lot of potential 00:04:29.790 --> 00:04:33.610 to express. I think it's important that we continue 00:04:33.610 --> 00:04:37.069 to invest further the network and also to explore 00:04:37.480 --> 00:04:41.339 what is behind the connectivity, like becoming, 00:04:41.360 --> 00:04:44.000 I think this was a subject discussed while it 00:04:44.000 --> 00:04:46.939 was about the telco at the forefront to become 00:04:46.939 --> 00:04:51.319 a modern orchestrator of B2B services providing 00:04:51.319 --> 00:04:55.279 the 5G connectivity, but also helping all the 00:04:55.279 --> 00:04:58.420 other enterprises to digitize and adopt data 00:04:58.420 --> 00:05:03.569 and AI. Andrew, Oracle made a surprising announcement 00:05:03.569 --> 00:05:06.329 recently with a major product innovation for 00:05:06.329 --> 00:05:09.269 BSS automation that really caught my attention. 00:05:09.470 --> 00:05:12.509 I always think of Oracle about enterprise, and 00:05:12.509 --> 00:05:15.889 this introduced me as a first -time observer 00:05:15.889 --> 00:05:18.970 into the telco arena. Can you tell me what you've 00:05:18.970 --> 00:05:21.949 delivered? I'm glad we've managed to surprise 00:05:21.949 --> 00:05:25.009 you, Alison. That's always a prime ambition. 00:05:25.689 --> 00:05:28.790 What we've recently announced is a new digital 00:05:28.790 --> 00:05:32.069 business experience solution. Now this is basically 00:05:32.069 --> 00:05:35.370 an all -in -one digital BSS solution for service 00:05:35.370 --> 00:05:38.149 providers. It's really designed to allow them 00:05:38.149 --> 00:05:40.810 to manage their experiences and their revenue 00:05:40.810 --> 00:05:42.970 across the entire customer journey, so all the 00:05:42.970 --> 00:05:45.990 way from concept to cash to care. Now with this 00:05:45.990 --> 00:05:48.670 solution, the idea is really that we can actually 00:05:48.670 --> 00:05:52.209 allow service providers to capitalize on the 00:05:52.209 --> 00:05:54.709 kind of new emerging enterprise opportunities, 00:05:55.189 --> 00:05:57.329 because it will allow them to really easily sort 00:05:57.329 --> 00:06:00.110 of design these differentiated offers and be 00:06:00.110 --> 00:06:02.949 able to do really rapid order capture and fulfillment. 00:06:03.350 --> 00:06:05.290 And obviously have very comprehensive revenue 00:06:05.290 --> 00:06:07.990 management capabilities. But importantly, this 00:06:07.990 --> 00:06:10.689 particular solution also allows them to continue 00:06:10.689 --> 00:06:13.769 to service a very complex and demanding consumer 00:06:13.769 --> 00:06:15.829 base that they have in their business today. 00:06:16.089 --> 00:06:18.709 So this is really a kind of multi -channel. future 00:06:18.709 --> 00:06:21.689 proof solution for them. When we spoke to a lot 00:06:21.689 --> 00:06:23.930 of our service provider customers, they really 00:06:23.930 --> 00:06:26.649 told us that they needed a very sophisticated 00:06:26.649 --> 00:06:29.310 set of solutions to be able to give them the 00:06:29.310 --> 00:06:31.689 necessary control and flexibility that they want 00:06:31.689 --> 00:06:34.209 over all the aspects of their business in this 00:06:34.209 --> 00:06:37.790 space. What we really tried to do with this experience 00:06:37.790 --> 00:06:40.449 was to give them something that allows them to 00:06:40.449 --> 00:06:43.629 meet the needs of the emerging industry opportunities 00:06:43.629 --> 00:06:46.589 but also their existing markets and so the focus 00:06:46.589 --> 00:06:49.009 was very much on something that was a full featured 00:06:49.009 --> 00:06:52.329 solution giving all the benefits around the pre 00:06:52.329 --> 00:06:56.009 integrated solution stack and giving them access 00:06:56.009 --> 00:06:59.050 to product ties to configurable. capabilities 00:06:59.050 --> 00:07:01.769 already within there. And I think importantly, 00:07:01.970 --> 00:07:04.449 and Andrea touched on this point, it unlocks 00:07:04.449 --> 00:07:07.029 that ability to take that journey into the cloud 00:07:07.029 --> 00:07:09.449 as well. So this is a fully cloud native solution. 00:07:09.850 --> 00:07:12.449 It can be deployed anywhere. It can be on premise. 00:07:12.509 --> 00:07:14.829 It can be in public cloud, but it's really giving 00:07:14.829 --> 00:07:17.730 them the scalability and the operational efficiencies 00:07:17.730 --> 00:07:20.329 of the cloud. But more importantly, as Andrea 00:07:20.329 --> 00:07:22.629 mentioned, giving them access to those really 00:07:22.629 --> 00:07:24.670 significant technical innovations that we're 00:07:24.670 --> 00:07:28.100 now seeing in the cloud, such as AI. If I may 00:07:28.100 --> 00:07:31.300 add something, just because I'm so interested 00:07:31.300 --> 00:07:34.459 in this subject and with Andrew, sorry if I interrupt 00:07:34.459 --> 00:07:37.199 a bit of the flow, but back to the original story. 00:07:37.540 --> 00:07:40.199 I think if you look at the evolution of the telco 00:07:40.199 --> 00:07:43.300 from business and how this has been matched by 00:07:43.300 --> 00:07:46.139 an architecture, I think that you can acknowledge 00:07:46.139 --> 00:07:49.600 a bit of three, four phases. And this is just 00:07:49.600 --> 00:07:52.819 why I like the importance of VB now. So if you 00:07:52.819 --> 00:07:57.000 go back prior to 2000, was everything was about 00:07:57.000 --> 00:07:59.800 billing. And billing was the only channel that 00:07:59.800 --> 00:08:02.399 the telco user to communicate with customer, 00:08:02.800 --> 00:08:05.500 providing a single invoice was actually the best 00:08:05.500 --> 00:08:07.860 way to interact. I think then there has been 00:08:07.860 --> 00:08:11.420 around 10 years where it was all about CRM and 00:08:11.420 --> 00:08:15.339 CRM to enable the assisted channel. I think that 00:08:15.339 --> 00:08:18.240 in the last seven, eight years, I think the full 00:08:18.240 --> 00:08:22.220 attention was deserved to the only channel capability. 00:08:22.680 --> 00:08:25.740 and this has been further accelerated during 00:08:25.740 --> 00:08:28.300 the pandemic with the need to digitize. I think 00:08:28.300 --> 00:08:32.019 now DBE is addressing a specific point which 00:08:32.019 --> 00:08:34.720 is for me critically important is the digital 00:08:34.720 --> 00:08:38.759 core. And the digital core is what we were using 00:08:38.759 --> 00:08:41.700 in the past to call system of record and core 00:08:41.700 --> 00:08:46.039 transactional system. What DBE is great at is 00:08:46.039 --> 00:08:49.940 a modern core system. and for modern being cloud 00:08:49.940 --> 00:08:53.679 -native, which is providing a central set of 00:08:53.679 --> 00:08:56.899 data with the secure access to the artificial 00:08:56.899 --> 00:09:00.759 intelligence. And the idea is to provide this 00:09:00.759 --> 00:09:03.480 suite from CNRAM to the billing to the order 00:09:03.480 --> 00:09:06.299 management in order to provide the client with 00:09:06.299 --> 00:09:09.399 adaptability, being cloud -native, designed to 00:09:09.399 --> 00:09:12.570 run on cloud, speed and resiliency. I think that 00:09:12.570 --> 00:09:16.330 what is important for Tavco to rethink back about 00:09:16.330 --> 00:09:18.669 combining all these elements that historically 00:09:18.669 --> 00:09:22.250 were considered as important, so RAM, billing, 00:09:22.529 --> 00:09:24.629 and now for the management from an influence 00:09:24.629 --> 00:09:27.490 standpoint, so that they could become the primary 00:09:27.490 --> 00:09:31.610 source of competitive advantage. Thanks for that. 00:09:31.830 --> 00:09:34.269 One question that I have about that, Andrew, 00:09:34.509 --> 00:09:38.009 is how does that fit into Oracle's broader cloud 00:09:38.009 --> 00:09:42.370 first business strategy and your engagement across 00:09:42.370 --> 00:09:45.769 different businesses. To double click on the 00:09:45.769 --> 00:09:47.929 topic of cloud, the first thing I would probably 00:09:47.929 --> 00:09:51.169 highlight is the journey for the service providers 00:09:51.169 --> 00:09:53.990 into the cloud is way more than just a technology 00:09:53.990 --> 00:09:57.610 adoption challenge. It is fundamental to their 00:09:57.610 --> 00:09:59.350 operating model and to the way that they run 00:09:59.350 --> 00:10:02.809 their businesses. It is an extremely challenging 00:10:02.809 --> 00:10:05.649 journey to take to be able to move into cloud 00:10:05.649 --> 00:10:08.690 adoption across all of the different technical 00:10:08.690 --> 00:10:11.730 components of the stack that they run. Now with 00:10:11.730 --> 00:10:13.950 digital business experience, what we wanted to 00:10:13.950 --> 00:10:16.429 do was provide as much flexibility as possible 00:10:16.429 --> 00:10:19.690 so that a given service provider can almost tailor 00:10:19.690 --> 00:10:22.629 that journey that they go on in line with their 00:10:22.629 --> 00:10:24.970 business strategy in the broader sense, but also 00:10:25.320 --> 00:10:27.539 their ability to transform their organization 00:10:27.539 --> 00:10:30.799 and to make those operating changes. So when 00:10:30.799 --> 00:10:33.059 you look at what we've done with digital business 00:10:33.059 --> 00:10:35.899 experience, I mentioned already that it's extremely 00:10:35.899 --> 00:10:39.059 flexible in terms of the deployment configurations 00:10:39.059 --> 00:10:41.100 that you can have. You can run it in on -prem 00:10:41.100 --> 00:10:43.559 environments. You can run it in public clouds. 00:10:43.740 --> 00:10:46.320 But more importantly, what we've done is we've 00:10:46.320 --> 00:10:49.000 connected it to Oracle's core strategy around 00:10:49.000 --> 00:10:51.519 really embracing and allowing hybrid or multi 00:10:51.519 --> 00:10:54.360 -cloud environments as well. So the ability to 00:10:54.360 --> 00:10:57.440 be able to efficiently interconnect into other 00:10:57.440 --> 00:10:59.980 third -party infrastructure. And so if you look 00:10:59.980 --> 00:11:02.139 at some of the strategic partnerships that Oracle's 00:11:02.139 --> 00:11:04.559 already announced with Azure, with Google, more 00:11:04.559 --> 00:11:07.200 recently with AWS, these kind of highly secure 00:11:07.200 --> 00:11:09.340 connections between the cloud, they're really 00:11:09.340 --> 00:11:11.759 unlocking the ability for the service providers 00:11:11.759 --> 00:11:14.480 to be able to move data around those different 00:11:14.480 --> 00:11:17.480 cloud environments in line with however they've 00:11:17.480 --> 00:11:20.259 chosen to deploy their various solutions. So 00:11:20.259 --> 00:11:22.100 their front office, their back office, whatever. 00:11:22.330 --> 00:11:24.789 And the point here is that it's this data alignment 00:11:24.789 --> 00:11:28.389 that's really key to unlocking how you can then 00:11:28.389 --> 00:11:30.669 access the latest generation of insights that 00:11:30.669 --> 00:11:33.549 you can get from the AI capabilities in the cloud. 00:11:33.590 --> 00:11:36.529 So the ability to bring this data together and 00:11:36.529 --> 00:11:39.340 to get. really good information and insights 00:11:39.340 --> 00:11:42.679 from it is what drives the opportunities. So 00:11:42.679 --> 00:11:44.940 for many of our customers, the CX has always 00:11:44.940 --> 00:11:48.019 really been a priority and it's viewed very often 00:11:48.019 --> 00:11:50.740 as this low -hanging fruit in terms of AI adoption. 00:11:51.220 --> 00:11:54.720 Looking at use cases like summarization or sentiment 00:11:54.720 --> 00:11:56.879 analysis or real -time transcript, I mean, all 00:11:56.879 --> 00:12:00.059 of these kind of capabilities you can get by 00:12:00.059 --> 00:12:03.399 having access to your data in a uniform way. 00:12:03.600 --> 00:12:06.899 And then being able to use these large language 00:12:06.899 --> 00:12:10.519 models to use these AI engines to be able to 00:12:10.519 --> 00:12:13.500 deliver those insights. So again, to kind of 00:12:13.500 --> 00:12:15.679 wrap it up, the point here is that we've tried 00:12:15.679 --> 00:12:17.940 to provide as much flexibility as possible for 00:12:17.940 --> 00:12:20.679 the customers because the cloud journey is not 00:12:20.679 --> 00:12:23.340 a simple one. It is one where we know that they're 00:12:23.340 --> 00:12:25.559 going to have to have different solutions from 00:12:25.559 --> 00:12:27.740 different providers. But what we've tried to 00:12:27.740 --> 00:12:29.720 do is make sure that they have a vehicle to be 00:12:29.720 --> 00:12:31.840 able to re -bring the data together, which is 00:12:31.840 --> 00:12:35.059 where all the magic starts. Now Andrea, it's 00:12:35.059 --> 00:12:37.899 really obvious that these two teams are collaborating 00:12:37.899 --> 00:12:40.980 deeply. Can you provide some context for the 00:12:40.980 --> 00:12:43.730 collaboration between the two companies? Let 00:12:43.730 --> 00:12:46.610 me say that, honestly, I've been involved in 00:12:46.610 --> 00:12:49.350 this project even before it started. Also, I 00:12:49.350 --> 00:12:51.970 think the collaboration with Oracle in communication, 00:12:52.149 --> 00:12:55.029 especially about me, is a historical collaboration. 00:12:55.250 --> 00:12:57.110 I think the two companies have been collaborating 00:12:57.110 --> 00:13:00.190 for 30 years. I believe I started working on 00:13:00.190 --> 00:13:02.990 the same subject together with Oracle along the 00:13:02.990 --> 00:13:05.450 pendulum that was set before that. I started 00:13:05.450 --> 00:13:08.950 from billing, and when Oracle acquired PortAdditionNet 00:13:08.950 --> 00:13:12.070 and moved to Siebel, then it became the standard 00:13:12.070 --> 00:13:16.029 de facto. for the CRM in all the possible countries, 00:13:16.269 --> 00:13:18.750 the opportunity and the luckiness to work with. 00:13:19.190 --> 00:13:21.370 And then in the past, I think we had also another 00:13:21.370 --> 00:13:23.870 collaboration of Rodod that we can consider a 00:13:23.870 --> 00:13:26.950 bit of the father of what DB is today. I think 00:13:26.950 --> 00:13:29.309 that the collaboration is quite high. I think 00:13:29.309 --> 00:13:31.889 two points that to me are very relevant. I think 00:13:31.889 --> 00:13:35.210 one, building on what Andrew said, the fact that 00:13:35.210 --> 00:13:38.350 cloud is becoming the admission ticket for a 00:13:38.350 --> 00:13:41.210 modern enterprise and that Elko is no different 00:13:41.210 --> 00:13:43.789 from the others. So I think that the evolutionary 00:13:43.789 --> 00:13:47.809 path taken by DB to become cloud native and enable 00:13:47.809 --> 00:13:51.370 a SaaS -like operation is a critical point for 00:13:51.370 --> 00:13:53.870 all the telco. The second point, I think this 00:13:53.870 --> 00:13:56.750 is strongly supported by the Oracle strategy 00:13:56.750 --> 00:13:59.629 of multi -cloud. If you remind a couple of Oracle 00:13:59.629 --> 00:14:02.429 cloud work ago, Larry Ellison introduced the 00:14:02.429 --> 00:14:06.190 concept of the internet of cloud and he was introducing 00:14:06.190 --> 00:14:09.309 his pitch saying, no wallet gardener are tumbling 00:14:09.309 --> 00:14:12.679 down. and from that I think many things happen 00:14:12.679 --> 00:14:15.860 and honestly I think the strategy is so strong 00:14:15.860 --> 00:14:18.399 acknowledging that there is no workload equal 00:14:18.399 --> 00:14:21.879 to the other and every workload requires a specific 00:14:21.879 --> 00:14:25.120 cloud and the specificity of Oracle is that Oracle 00:14:25.120 --> 00:14:28.639 is the best cloud supporting high transactional 00:14:28.639 --> 00:14:31.980 capability and back to the Telco and back to 00:14:31.980 --> 00:14:34.700 the BSS and OSS is the place where you have the 00:14:34.700 --> 00:14:37.509 customer that you have the order data, you have 00:14:37.509 --> 00:14:39.750 the product data, the billing data. So I think 00:14:39.750 --> 00:14:42.830 having a solution that is cloud native, designed 00:14:42.830 --> 00:14:45.409 to run on cloud, is a big value for the customer. 00:14:45.529 --> 00:14:47.590 So in terms of partnership, we will continue 00:14:47.590 --> 00:14:50.909 in the major client where we are developing this 00:14:50.909 --> 00:14:54.389 opportunity. And of course, in designing the 00:14:54.389 --> 00:14:57.169 roadmap together of the client in alignment with 00:14:57.169 --> 00:15:00.350 the benefit from that. Another, to me, critical 00:15:00.350 --> 00:15:03.529 point is how the client will transform. We say 00:15:03.529 --> 00:15:05.750 that this is an industry always at the forefront 00:15:05.750 --> 00:15:09.289 of the innovation, but is also an industry that 00:15:09.289 --> 00:15:11.850 supports all the other industries, but is also 00:15:11.850 --> 00:15:14.169 an industry that has been disrupted massively. 00:15:14.350 --> 00:15:16.669 with a lot of investment because it's a capital 00:15:16.669 --> 00:15:19.230 intensive if you consider the amount of money 00:15:19.230 --> 00:15:23.029 that Tesco plays on 4G, then 5G and then very 00:15:23.029 --> 00:15:25.549 soon with the 6G and some of them already started. 00:15:26.090 --> 00:15:28.830 So I think that what I think is important when 00:15:28.830 --> 00:15:31.649 we speak about DBE that we can help the client 00:15:31.649 --> 00:15:34.649 to transform themselves but with an evolutionary 00:15:34.649 --> 00:15:37.649 path as opposite of a revolutionary path. So 00:15:37.649 --> 00:15:41.330 you are using all the great technology, but building 00:15:41.330 --> 00:15:44.629 on what the client has or they can take, or having 00:15:44.629 --> 00:15:48.970 any historical data like SIDBEL, like BRM, like 00:15:48.970 --> 00:15:51.610 OSM and COM. So I think that this will help a 00:15:51.610 --> 00:15:54.129 lot because in a disrupted industry and in a 00:15:54.129 --> 00:15:57.570 disrupted world, I think having the possibility 00:15:57.570 --> 00:16:01.129 to design your evolutionary path, to transform 00:16:01.129 --> 00:16:03.970 yourself, to reinvent yourself with the assurance 00:16:03.970 --> 00:16:06.429 that you are basing this... to transformation 00:16:06.429 --> 00:16:10.049 that is evolutionary is a kind of assurance that 00:16:10.049 --> 00:16:12.850 the client should adopt. And honestly, with this 00:16:12.850 --> 00:16:15.470 level of partnership knowledge, I think we are 00:16:15.470 --> 00:16:17.850 best suited to partner together and to get the 00:16:17.850 --> 00:16:20.110 client to where they want to be in the future. 00:16:20.970 --> 00:16:24.090 Now, why was this the right moment to target 00:16:24.090 --> 00:16:27.870 BSS? And what does this open up for monetization 00:16:27.870 --> 00:16:31.149 of services like what we discussed before? If 00:16:31.149 --> 00:16:34.190 I may, I believe that as I say, there is a pendulum 00:16:34.190 --> 00:16:37.289 and also like Andrew, we are a long time in the 00:16:37.289 --> 00:16:41.129 industry. And I think that the recent happening, 00:16:41.590 --> 00:16:44.149 fortunate or unfortunate, I think that pushed 00:16:44.149 --> 00:16:47.850 some priority to the tech. So I think that during 00:16:47.850 --> 00:16:49.990 the pandemic, a lot of customer experience, a 00:16:49.990 --> 00:16:52.889 lot of infrastructure job in order to save money, 00:16:53.149 --> 00:16:55.750 reinvest the capital in the area that were more 00:16:55.750 --> 00:16:58.879 urgent to save. I think that today there is another 00:16:58.879 --> 00:17:01.360 big event from the industry, from the market, 00:17:01.659 --> 00:17:05.480 which is the availability of generative AI, artificial 00:17:05.480 --> 00:17:07.720 intelligence in general, that for the people 00:17:07.720 --> 00:17:10.240 that did engineer like me, something that I did 00:17:10.240 --> 00:17:13.160 30 years ago at the university, but there were 00:17:13.160 --> 00:17:16.119 at the time no computational power, no storage, 00:17:16.599 --> 00:17:19.920 and both of them were incredible price and cost. 00:17:20.220 --> 00:17:23.619 Today is a technology that is available for everyone, 00:17:24.079 --> 00:17:27.160 so I think that refocusing on where the critical 00:17:27.160 --> 00:17:30.000 data of the 10 core aside is really strategic. 00:17:30.299 --> 00:17:32.359 And that's why I think we speak about the digital 00:17:32.359 --> 00:17:35.059 core. For me, the D is a digital core for the 00:17:35.059 --> 00:17:38.059 10 core, and we are... helping the client to 00:17:38.059 --> 00:17:40.359 refocus on where the critical data is because 00:17:40.359 --> 00:17:43.420 then you can leverage of the new technology coming 00:17:43.420 --> 00:17:45.759 from artificial intelligence and generative AI 00:17:45.759 --> 00:17:48.039 to improve the customer experience or to improve 00:17:48.039 --> 00:17:50.819 the sentiment that he can do, mention a few of 00:17:50.819 --> 00:17:54.740 them, summarization, but also improve the efficiency 00:17:54.740 --> 00:17:57.940 and effectiveness of the billing, tracking the 00:17:57.940 --> 00:18:00.700 order, the service request, the level of services. 00:18:00.740 --> 00:18:03.019 So it's really the right moment. It's just an 00:18:03.019 --> 00:18:06.759 alignment of planets in the view. Now, Andrew, 00:18:07.119 --> 00:18:09.700 what has the customer response been to this announcement 00:18:09.700 --> 00:18:13.400 since you delivered it earlier this year? I'd 00:18:13.400 --> 00:18:16.279 start probably by saying that this business experience 00:18:16.279 --> 00:18:19.079 was actually born from listening to our customers 00:18:19.079 --> 00:18:22.140 and actually working with our strategic partners 00:18:22.140 --> 00:18:24.420 like Accenture and actually paying attention 00:18:24.420 --> 00:18:28.119 to what the needs of the market were. And somewhat 00:18:28.119 --> 00:18:30.200 unsurprisingly, the response has obviously been 00:18:30.200 --> 00:18:32.500 very overwhelmingly positive because what we're 00:18:32.500 --> 00:18:34.420 trying to do here is really to give the market 00:18:34.420 --> 00:18:37.079 what it's telling us it needs. I would probably 00:18:37.079 --> 00:18:39.980 bucket those four needs into maybe four core 00:18:39.980 --> 00:18:42.579 categories. And so the first one and the first 00:18:42.579 --> 00:18:44.759 message that came across loud and clear is we 00:18:44.759 --> 00:18:47.240 need a solution that's going to help us to accelerate 00:18:47.240 --> 00:18:50.500 and move to the cloud and ultimately to get access 00:18:50.500 --> 00:18:53.119 to that latest generation of cloud services that 00:18:53.119 --> 00:18:55.960 then unlocks and Andrea there was talking about. 00:18:56.059 --> 00:18:58.079 once again, all those different ways in which 00:18:58.079 --> 00:19:01.880 you can use AI to be able to augment and support 00:19:01.880 --> 00:19:04.920 what you do with customer experiences as an example. 00:19:05.640 --> 00:19:07.619 The second sort of message that came loud and 00:19:07.619 --> 00:19:10.200 clear was that they really wanted a fully digital 00:19:10.200 --> 00:19:13.099 solution. And so again, Andrea is referring to 00:19:13.099 --> 00:19:15.700 this digital core and the criticality of that 00:19:15.700 --> 00:19:19.259 as a vehicle to be able to unlock. new market 00:19:19.259 --> 00:19:21.519 opportunities that are coming from the enterprise 00:19:21.519 --> 00:19:24.359 vertical service space and so that was a very 00:19:24.359 --> 00:19:27.140 clear requirement as well. The third one was 00:19:27.140 --> 00:19:30.920 really around trying to ease the adoption and 00:19:30.920 --> 00:19:33.440 the implementation and so the message there was 00:19:33.440 --> 00:19:35.819 really around bring us a pre -integrated offering 00:19:35.819 --> 00:19:38.740 bring us something that has a rich set of. Out 00:19:38.740 --> 00:19:41.359 of the box product models and predefined journeys 00:19:41.359 --> 00:19:44.500 and can allow us to things just one click publishing 00:19:44.500 --> 00:19:46.759 to all the downstream applications and this is 00:19:46.759 --> 00:19:49.400 really around how we reduce time to market how 00:19:49.400 --> 00:19:52.400 do i get a solution that allows me to be fast 00:19:52.400 --> 00:19:55.799 and agile in the market but i'm trying to chase. 00:19:56.019 --> 00:19:58.900 I'm in fourth and i think probably most critically 00:19:58.900 --> 00:20:02.079 there was a really strong message around. make 00:20:02.079 --> 00:20:04.920 sure that this thing is super feature rich, right? 00:20:05.079 --> 00:20:08.259 There was no willingness to compromise on the 00:20:08.259 --> 00:20:11.740 need to be able to continue to service the existing 00:20:11.740 --> 00:20:14.759 business that they have. And so moving into new 00:20:14.759 --> 00:20:16.819 business spaces is really critical for the future 00:20:16.819 --> 00:20:19.319 of the industry, but you can't walk away from 00:20:19.319 --> 00:20:22.420 what you have today. And communications has an 00:20:22.420 --> 00:20:25.960 incredibly complex and rich set of products and 00:20:25.960 --> 00:20:28.279 journeys and experiences that are locked into 00:20:28.279 --> 00:20:31.170 the customer base. And so the message really 00:20:31.170 --> 00:20:33.670 there was loud and clear, which is we make no 00:20:33.670 --> 00:20:35.650 compromise on the capabilities of the platform. 00:20:35.869 --> 00:20:37.910 It has to be future proofed, but it has to do 00:20:37.910 --> 00:20:40.430 everything that we need it to do today. And so, 00:20:40.450 --> 00:20:42.029 you know, what we've done with digital business 00:20:42.029 --> 00:20:43.849 experience is really creates and I can quite 00:20:43.849 --> 00:20:47.450 unique because It manages to combine all of these 00:20:47.450 --> 00:20:49.869 kind of four requirements, these four attributes 00:20:49.869 --> 00:20:52.650 in a way that's genuinely best in class. And 00:20:52.650 --> 00:20:54.849 to come to the core of the question, the response 00:20:54.849 --> 00:20:57.029 really from the industry as a whole, from customers, 00:20:57.230 --> 00:20:59.309 from analysts, from our strategic partners like 00:20:59.309 --> 00:21:02.309 Accenture, it really has been super positive 00:21:02.309 --> 00:21:05.690 because they can see the ambition of trying to 00:21:05.690 --> 00:21:07.569 really create something that can really help 00:21:07.569 --> 00:21:11.230 the customers win in the market. Now, Andrea, 00:21:11.569 --> 00:21:14.829 can you just take that? perspective that Andrew 00:21:14.829 --> 00:21:17.549 just laid out and talk to us about how customers 00:21:17.549 --> 00:21:20.529 actually implement the solution from the decision 00:21:20.529 --> 00:21:24.750 to deploy to full throttle activation. I think 00:21:24.750 --> 00:21:28.109 there are just two ways. Now, one is Greenfield 00:21:28.109 --> 00:21:30.329 and the other one is Brownfield. Those are the 00:21:30.329 --> 00:21:32.950 two approaches that I see. Brownfield is the 00:21:32.950 --> 00:21:36.210 one that is taking the majority of the value 00:21:36.210 --> 00:21:38.809 of an evolutionary path. And this is actually 00:21:38.809 --> 00:21:41.710 cool because you can just update your solution, 00:21:42.029 --> 00:21:44.390 adding some component if you like, you'll get 00:21:44.390 --> 00:21:47.609 it to the end. Greenfield is when you want to 00:21:47.609 --> 00:21:50.269 be a bit, let's say, a revolutionary in this 00:21:50.269 --> 00:21:53.109 evolutionary path, creating a new instance and 00:21:53.109 --> 00:21:55.410 then migrate what you have in the house into 00:21:55.410 --> 00:21:58.309 the new patch. The other point of the decision 00:21:58.309 --> 00:22:01.049 is when you want to get the value from the cloud, 00:22:01.210 --> 00:22:03.690 if you want to get from the beginning or migrating 00:22:03.690 --> 00:22:06.029 later, but the solution is already designed for 00:22:06.029 --> 00:22:09.150 that. And in case you migrate with some of our 00:22:09.150 --> 00:22:11.450 joint clients, with Andrew, that client that 00:22:11.450 --> 00:22:14.069 decided to embrace the dedicated region Cloud 00:22:14.069 --> 00:22:18.029 .Customer, I think that we also observed an incredible 00:22:18.029 --> 00:22:20.750 improvement of the performance of the processes 00:22:20.750 --> 00:22:23.490 from the end to end standpoint. So I think that 00:22:23.490 --> 00:22:25.390 the fact that we are speaking about the solution 00:22:25.390 --> 00:22:28.400 that is full cloud native that give you the possibility 00:22:28.400 --> 00:22:31.140 to decide whether you want to embrace the private 00:22:31.140 --> 00:22:33.680 cloud or the public cloud in the moment that 00:22:33.680 --> 00:22:36.559 you like, in the right moment in time. And this 00:22:36.559 --> 00:22:39.000 is the strategy to meet the client where they 00:22:39.000 --> 00:22:42.180 are and to accompany them in their evolutionary 00:22:42.180 --> 00:22:45.140 journey next to them to get to where they want 00:22:45.140 --> 00:22:49.619 to be. And, Andrew, when you look at this deployment, 00:22:49.819 --> 00:22:52.480 what do you see as the benefit to your telco 00:22:52.480 --> 00:22:55.720 customers? This is really about investing in 00:22:55.720 --> 00:22:57.839 their future. It's really about investing in 00:22:57.839 --> 00:23:00.839 the next wave of market opportunity that is open 00:23:00.839 --> 00:23:04.380 to them. By deploying digital business experience, 00:23:04.539 --> 00:23:06.839 what the customers are actually really achieving 00:23:06.839 --> 00:23:09.980 is they're putting the foundations in to be able 00:23:09.980 --> 00:23:13.440 to monetize APIs, to be able to present themselves 00:23:13.440 --> 00:23:16.539 into the market as that kind of telco as a platform 00:23:16.539 --> 00:23:20.849 concept. And so this digital core is really the 00:23:20.849 --> 00:23:24.410 start of that journey into the world beyond consumer 00:23:24.410 --> 00:23:27.490 the world beyond the current enterprise and being 00:23:27.490 --> 00:23:30.910 able to carve out a path to revenue growth so 00:23:30.910 --> 00:23:34.210 that really is the whole raison d 'etre of why 00:23:34.210 --> 00:23:36.329 they go down this path and why they're investing 00:23:36.329 --> 00:23:39.269 it's about allowing them to have something that 00:23:39.269 --> 00:23:41.930 keeps them. highly competitive still in their 00:23:41.930 --> 00:23:44.170 existing markets so that they can continue to 00:23:44.170 --> 00:23:46.329 generate the revenues that are fueling their 00:23:46.329 --> 00:23:49.309 businesses today, but have this digital platform 00:23:49.309 --> 00:23:52.130 that's going to unlock entirely new revenue streams 00:23:52.130 --> 00:23:54.609 as they move forward in the future. That's really 00:23:54.609 --> 00:23:57.309 important effectively to set the path forward 00:23:57.309 --> 00:23:59.769 as it were for them to grow and to be successful. 00:24:01.289 --> 00:24:03.490 And Andrea, when you think about what you've 00:24:03.490 --> 00:24:06.750 accomplished here with Oracle, what's next on 00:24:06.750 --> 00:24:09.170 the roadmap for the two companies working together? 00:24:10.190 --> 00:24:14.109 I think that we should continue to design together 00:24:14.109 --> 00:24:16.890 the roadmap and I think the way we can help is 00:24:16.890 --> 00:24:20.289 that Oracle is an incredible company when it's 00:24:20.289 --> 00:24:23.700 about data engineering solutions. Accent should 00:24:23.700 --> 00:24:26.619 complement Oracle with the industry knowledge 00:24:26.619 --> 00:24:29.339 and the function expertise. So I think that the 00:24:29.339 --> 00:24:32.099 idea is really to make sure that the roadmap 00:24:32.099 --> 00:24:36.779 continues to be sound and innovative, addressing 00:24:36.779 --> 00:24:40.220 the industry concern and the functional concern. 00:24:40.820 --> 00:24:43.859 with the capability and I think Andrew and I 00:24:43.859 --> 00:24:47.240 were always talking about enabling at scale, 00:24:47.420 --> 00:24:51.019 low code, no code, generative AI addressing one 00:24:51.019 --> 00:24:53.440 of the two, three cases that are more important 00:24:53.440 --> 00:24:56.019 for the client in addition to always working 00:24:56.019 --> 00:24:58.380 together with our client because this is actually 00:24:58.380 --> 00:25:01.559 what is giving us the insight and the direction 00:25:01.559 --> 00:25:04.299 where we want to go because we really want to 00:25:04.299 --> 00:25:07.559 help the client to succeed and to transform themselves. 00:25:08.079 --> 00:25:10.759 If I could add to that, Alison, because I really 00:25:10.759 --> 00:25:13.559 would like to reinforce why I think the relationship 00:25:13.559 --> 00:25:16.119 between Oracle and Accenture is so powerful. 00:25:16.559 --> 00:25:18.440 Through digital experience, we're bringing an 00:25:18.440 --> 00:25:20.859 incredibly powerful toolkit to the customers. 00:25:21.500 --> 00:25:23.619 But then there's still the question of learning 00:25:23.619 --> 00:25:25.619 to use that in the most effective way. And the 00:25:25.619 --> 00:25:28.119 beauty of Accenture is that they have such an 00:25:28.119 --> 00:25:30.440 intimate and close knowledge of the customer's 00:25:30.440 --> 00:25:32.119 businesses, the challenges they have, and what 00:25:32.119 --> 00:25:34.579 they're trying to achieve, that they're really 00:25:34.579 --> 00:25:37.200 well positioned to be able to take. something 00:25:37.200 --> 00:25:39.440 like digital business experience and realize 00:25:39.440 --> 00:25:42.900 the full potential with those customers. So I 00:25:42.900 --> 00:25:45.599 think such a symbiotic relationship really between 00:25:45.599 --> 00:25:49.380 the two businesses here. Fantastic. And one final 00:25:49.380 --> 00:25:52.400 question for you, Andrew. Where can folks find 00:25:52.400 --> 00:25:54.619 out more about the solutions discussed today? 00:25:55.190 --> 00:25:58.589 The go -to place is always oracle .com, so go 00:25:58.589 --> 00:26:01.089 to our website, click on industries, click on 00:26:01.089 --> 00:26:03.250 communications and you'll find our microsite 00:26:03.250 --> 00:26:05.269 there and you'll be able to see our latest press 00:26:05.269 --> 00:26:07.609 release. There's a really great data sheet as 00:26:07.609 --> 00:26:09.349 well on digital business experience where you 00:26:09.349 --> 00:26:11.630 can learn all the fundamentals. So take a look 00:26:11.630 --> 00:26:13.730 at the website and please reach out to us if 00:26:13.730 --> 00:26:16.440 you need more. Guys, it's been a pleasure. Really 00:26:16.440 --> 00:26:19.319 impressive collaboration and really impressive 00:26:19.319 --> 00:26:21.980 in how you're delivering value to your customers. 00:26:22.240 --> 00:26:24.619 I can't wait to hear more. Thank you so much 00:26:24.619 --> 00:26:27.039 for being on the show today. Hey, Phallusen. 00:26:27.119 --> 00:26:31.859 Good evening, guys. Always a pleasure. Thanks 00:26:31.859 --> 00:26:35.119 for joining the Tech Arena. Subscribe and engage 00:26:35.119 --> 00:26:38.779 at our website, thetecharena .net. All content 00:26:38.779 --> 00:26:40.500 is copyrighted by the Tech Arena.