1
00:00:10,000 --> 00:00:12,900
Welcome to a podcast inside a 
CPS for Hannah. 

2
00:00:13,000 --> 00:00:15,900
There's no customer success 
without product success and 

3
00:00:15,900 --> 00:00:19,400
project success. 
His unique, the head of a CPS 

4
00:00:19,400 --> 00:00:21,700
for an enablement at sap 
engineering. 

5
00:00:22,600 --> 00:00:26,300
No matter where you are in your,
It modernization Journey and 

6
00:00:26,300 --> 00:00:29,600
automation strategy at scale, 
will always improve employee 

7
00:00:29,600 --> 00:00:32,700
satisfaction. 
Shin accelerate Innovation and 

8
00:00:32,700 --> 00:00:35,300
reduce the costs for ACP 
customers. 

9
00:00:35,300 --> 00:00:39,100
This is even more relevant as 
they move to a CPS for Hannah 

10
00:00:39,100 --> 00:00:41,900
Cloud. 
Moving to the public cloud, and 

11
00:00:41,900 --> 00:00:44,400
moving on a platform, like 
Microsoft Azure, making 

12
00:00:44,400 --> 00:00:48,600
Automation, and essential asset 
to realize the benefits of 

13
00:00:48,800 --> 00:00:52,500
public Cloud today. 
I'm excited to have two guests 

14
00:00:52,500 --> 00:00:55,800
who will discuss the joint acps 
for Hannah on Asia automation 

15
00:00:55,800 --> 00:00:59,900
proposition, which completely 
automates ACP deployment and 

16
00:00:59,900 --> 00:01:02,000
operation. 
Operation, Asia using red Hat's,

17
00:01:02,000 --> 00:01:04,300
market-leading and Sybil 
automation platform. 

18
00:01:04,700 --> 00:01:08,800
Welcome with me, prakash, but 
Diane principal product manager 

19
00:01:09,000 --> 00:01:12,900
ACP on Asia engineering at 
Microsoft and Ricardo Garcia 

20
00:01:12,900 --> 00:01:14,700
cavero. 
Principal portfolio. 

21
00:01:14,700 --> 00:01:18,400
Architect at Red Hat, happy to 
have you both on the podcast. 

22
00:01:18,400 --> 00:01:22,000
Thanks for being with us guys. 
To get to know our guests a 

23
00:01:22,000 --> 00:01:25,100
little better. 
I'd like to start with a little 

24
00:01:25,100 --> 00:01:27,300
Icebreaker, maybe I'll start 
with your Ricardo. 

25
00:01:27,300 --> 00:01:29,000
Can you tell us something 
special about you? 

26
00:01:29,000 --> 00:01:31,800
Something we should remember. 
That beside your role at Red 

27
00:01:31,800 --> 00:01:34,000
Hat. 
You're unique. 

28
00:01:34,100 --> 00:01:36,200
Well, first of all, thank you 
for having me here. 

29
00:01:36,600 --> 00:01:40,200
It's a pleasure to be here with 
you in this podcast and 

30
00:01:40,200 --> 00:01:43,700
something apart from. 
Yeah, what I do my day-to-day 

31
00:01:43,700 --> 00:01:47,400
life. 
So my blog post and the 

32
00:01:47,400 --> 00:01:49,700
solutions are work for a at red 
hat. 

33
00:01:50,200 --> 00:01:53,400
So for example, something easy 
to remember I think because he's

34
00:01:53,400 --> 00:01:57,900
not too common for a Spanish 
person is that I really like 

35
00:01:58,200 --> 00:02:01,300
sitar music in the music and I 
play sitar myself. 

36
00:02:01,300 --> 00:02:03,900
So I would say that crazy. 
To Remember Me. 

37
00:02:03,900 --> 00:02:06,800
Be thanks for sharing your card.
Oh what, a bleep rat cash. 

38
00:02:06,800 --> 00:02:08,000
Thanks for being with us as 
well. 

39
00:02:08,000 --> 00:02:11,200
Can you share something that 
people will remember decide Your

40
00:02:11,200 --> 00:02:13,900
Role at Microsoft? 
Yeah, thanks for having us 

41
00:02:13,900 --> 00:02:18,400
Yannick happy to be here. 
I'm based out of Dallas in Texas

42
00:02:18,400 --> 00:02:24,800
in the u.s., so prior to that, I
was in Colorado for about 8 to 

43
00:02:24,800 --> 00:02:30,900
10 Years, love the outdoors love
Colorado in summer. 

44
00:02:30,900 --> 00:02:34,200
So that's something. 
I hope it's interesting. 

45
00:02:34,500 --> 00:02:38,500
Okay, thanks for sharing both. 
I will stay with you now. 

46
00:02:38,500 --> 00:02:42,800
Prakash and ask maybe the 
question of, you know, maybe go 

47
00:02:42,800 --> 00:02:47,300
a bit deeper into your role. 
And how is it real close to our 

48
00:02:47,300 --> 00:02:50,300
AC PS? 
400 public, Cloud install base 

49
00:02:50,300 --> 00:02:55,100
of customers. 
Yes, so, I'm part of the sap on 

50
00:02:55,100 --> 00:02:57,700
Azure core Engineering Group at 
Microsoft. 

51
00:02:57,800 --> 00:03:03,000
So this team is responsible for 
creating the infrastructure. 

52
00:03:03,100 --> 00:03:08,400
Original the other computer 
requirements to run sap and also

53
00:03:08,400 --> 00:03:10,500
all in the first party 
offerings. 

54
00:03:10,500 --> 00:03:14,600
Anything that we have to develop
for sap to run as the first 

55
00:03:14,600 --> 00:03:19,300
party product on Microsoft 
definition of the sap reference 

56
00:03:19,300 --> 00:03:24,900
architectures as well is done by
this Engineering Group strong 

57
00:03:24,900 --> 00:03:28,400
collaboration. 
So we have folks, go located on 

58
00:03:28,400 --> 00:03:32,600
either side. 
So some of sap folks working 

59
00:03:32,600 --> 00:03:36,700
with this at Redmond and some of
Microsoft employees working with

60
00:03:36,700 --> 00:03:40,400
sap as well, very strong 
relationships as we bring 

61
00:03:40,400 --> 00:03:43,100
Innovations to Market. 
So extra cash. 

62
00:03:43,100 --> 00:03:44,800
What about you recover? 
Can you please bring it a bit 

63
00:03:44,800 --> 00:03:49,300
more context about your job and 
how is that adding value to a 

64
00:03:49,300 --> 00:03:52,400
CPS 400 customers? 
Sure. 

65
00:03:52,800 --> 00:03:57,300
So when I started with rehab, is
going to be three years ago, I 

66
00:03:57,300 --> 00:04:00,800
was doing consultancy. 
So, actually working on the 

67
00:04:00,800 --> 00:04:04,800
field and before that I came 
from ASAP basis administrator 

68
00:04:04,800 --> 00:04:07,000
world. 
So I have been doing that for 

69
00:04:07,000 --> 00:04:09,900
maybe 15 years. 
When it came to Red Hat, I 

70
00:04:09,900 --> 00:04:15,600
started working on solutions 
that can help customers say make

71
00:04:15,600 --> 00:04:19,200
their their transition to the 
cloud into as for Hannah easier.

72
00:04:19,200 --> 00:04:22,300
So, namely, I focus a lot on 
automation on ansible. 

73
00:04:22,700 --> 00:04:27,700
So also engaging in a lot of 
customer projects doing doing 

74
00:04:27,700 --> 00:04:29,800
those things. 
Not only here only automation, 

75
00:04:29,800 --> 00:04:33,700
but also another, some other 
areas and Then I move to 

76
00:04:33,700 --> 00:04:36,500
portfolio architectures. 
Who would we try to reduce all 

77
00:04:36,500 --> 00:04:39,200
these solutions that we 
implemented with customers? 

78
00:04:39,600 --> 00:04:43,400
We try to extract them and give 
you like more like a reference 

79
00:04:43,400 --> 00:04:46,600
architecture and show customers 
how they can benefit from 

80
00:04:46,600 --> 00:04:49,700
Technologies, like Automation, 
in this journey to as a PS4 

81
00:04:49,700 --> 00:04:52,500
hunting, the club. 
Finding Africa do as I told you 

82
00:04:52,500 --> 00:04:54,300
offline. 
One of my first training when I 

83
00:04:54,300 --> 00:04:58,000
joined ACP in France, was on 
radar Technologies and I was 

84
00:04:58,000 --> 00:05:01,300
always impressed by the amazing 
technology that you guys provide

85
00:05:01,300 --> 00:05:05,400
to ACP customers at that time, 
it Java applets to call some HR 

86
00:05:05,400 --> 00:05:07,300
pay Sleep time. 
Sheets, Etc. 

87
00:05:07,900 --> 00:05:11,700
Now you've been with ACP for a 
couple decades and of course, 

88
00:05:11,700 --> 00:05:16,900
supported change going to cloud 
and going to public Cloud. 

89
00:05:17,200 --> 00:05:19,800
So can you allude a bit about 
the impact and eventually the 

90
00:05:19,800 --> 00:05:22,200
transformation on the Reddit 
site for that one? 

91
00:05:22,900 --> 00:05:27,000
So, that's the really the moving
of customers to the cloud is 

92
00:05:27,000 --> 00:05:31,700
when something really important 
a redhead, and how we construct 

93
00:05:31,700 --> 00:05:32,900
with this solution for 
customers. 

94
00:05:33,000 --> 00:05:37,100
Thomas actually is the one of 
the main drivers in what we do 

95
00:05:37,100 --> 00:05:39,800
at red hat for sap. 
Customers is the move. 

96
00:05:39,800 --> 00:05:42,100
We have this customers to the 
cloud because we're shaping the 

97
00:05:42,108 --> 00:05:45,100
method. 
So you can they all solutions 

98
00:05:46,600 --> 00:05:49,400
right to to focus on these 
customers move to the cloud 

99
00:05:49,500 --> 00:05:53,300
because one of the main premises
of red hat in general, not only 

100
00:05:53,300 --> 00:05:56,800
participate, customers is that 
anyone should be able to use our

101
00:05:56,800 --> 00:05:58,900
Technologies on the hybrid 
Cloud. 

102
00:05:59,000 --> 00:06:02,300
So private hybrid, a public 
whatever. 

103
00:06:02,600 --> 00:06:07,900
So We think that the best way to
to help customers is to help in 

104
00:06:07,900 --> 00:06:11,200
first when migrating to 
recipients for hand, I named it 

105
00:06:11,200 --> 00:06:12,500
to the club. 
Okay. 

106
00:06:12,500 --> 00:06:14,700
Can you legally business that? 
Because as you know, when you 

107
00:06:14,700 --> 00:06:17,600
move to the cloud, when you have
to public Cloud, there's a very 

108
00:06:17,600 --> 00:06:20,900
strict ACP activate methodology.
So at which phase of the 

109
00:06:20,900 --> 00:06:25,200
mythology is Red Hat jumping in 
and added value to the overall 

110
00:06:25,200 --> 00:06:30,000
project. 
So when we jump in is when the 

111
00:06:30,000 --> 00:06:34,000
migration plan has been 
established and customers know 

112
00:06:34,600 --> 00:06:37,600
which data structures with 
tables and which modules have 

113
00:06:37,600 --> 00:06:40,200
they're going to activate and 
they say PS4 Hannah's win, the 

114
00:06:40,200 --> 00:06:43,400
plan has been kind of laid out 
that when we jump in and we 

115
00:06:43,400 --> 00:06:46,300
provide for example, the 
automation assets for that. 

116
00:06:46,400 --> 00:06:47,900
So there's a clear plan for 
that. 

117
00:06:48,000 --> 00:06:52,800
Normally, we team up with 
systems integrators and partner 

118
00:06:52,800 --> 00:06:57,500
with them, and when they do the 
technique of With a technical. 

119
00:06:57,800 --> 00:07:02,600
They the actual defined 
definition and design of the 

120
00:07:02,600 --> 00:07:04,500
migration and how they want to 
do it. 

121
00:07:04,800 --> 00:07:07,800
Then we put in place our 
Technologies and then the 

122
00:07:07,800 --> 00:07:11,600
automation to to the detect the 
technical migration itself. 

123
00:07:12,600 --> 00:07:15,300
For example, if we was going to 
say if we're if we're talking 

124
00:07:15,300 --> 00:07:18,300
about moving to a public cloud 
like a sure look something we 

125
00:07:19,900 --> 00:07:22,100
give the are provide the assets 
to do. 

126
00:07:22,500 --> 00:07:25,500
All the technical migration 
end-to-end automatically, so 

127
00:07:25,600 --> 00:07:28,400
building, the Girl creating the 
virtual machines are not sure 

128
00:07:28,700 --> 00:07:34,000
installing the operating system 
image and then applying all the 

129
00:07:34,000 --> 00:07:39,000
sap notes that need to that are 
needed for to build the sap Hana

130
00:07:39,000 --> 00:07:42,700
on the, in the CPS, for Hannah 
targets and then until the 

131
00:07:42,700 --> 00:07:45,900
system has been my greatest for 
all the technical migration can 

132
00:07:45,900 --> 00:07:49,000
be done. 
But if we are talking about 

133
00:07:49,000 --> 00:07:53,200
extracting data in all that we 
are not in that part for you, 

134
00:07:53,207 --> 00:07:56,400
having been on projects before 
public Cloud came to Erp. 

135
00:07:56,600 --> 00:07:59,700
Or Erp came to public Cloud. 
Better said, what are the key 

136
00:07:59,700 --> 00:08:01,400
change? 
You've noticed? 

137
00:08:01,400 --> 00:08:04,100
I would say both on the business
side of the customer, on the it 

138
00:08:04,100 --> 00:08:07,300
side, and all challenges, 
bottlenecks Etc, that you need 

139
00:08:07,300 --> 00:08:12,100
to clearly inform before you 
really start the project hands 

140
00:08:12,100 --> 00:08:17,600
on. 
Well, is before I used to be a 

141
00:08:17,600 --> 00:08:21,600
much more problem of having the 
right hardware and premises. 

142
00:08:21,600 --> 00:08:27,000
Now, that's much more flexible. 
So it has changed completely the

143
00:08:27,000 --> 00:08:29,500
the view of the customers and 
how they approach, and migration

144
00:08:29,500 --> 00:08:32,200
a move to the club. 
So I see that now, customers are

145
00:08:32,200 --> 00:08:35,400
much more open to Big migration 
because of that, because they 

146
00:08:35,400 --> 00:08:38,500
know the flexibility. 
And when we show them the value 

147
00:08:38,500 --> 00:08:42,600
of automation, they, they are 
much more reassured and they can

148
00:08:42,600 --> 00:08:45,700
see that. 
To reduce the time of Mike of 

149
00:08:45,700 --> 00:08:49,500
the migration of a system from 
several days to just some our. 

150
00:08:49,500 --> 00:08:52,600
So I think that's changing a 
lot. 

151
00:08:52,600 --> 00:08:55,400
The mindset of the of the 
business because they're more 

152
00:08:55,400 --> 00:08:58,900
open to changes in total 
Automation, and just kill the 

153
00:08:58,900 --> 00:09:03,300
use of automation, not only to 
the migration but then to the to

154
00:09:03,300 --> 00:09:04,900
the day to day or day, two 
operations. 

155
00:09:04,900 --> 00:09:10,800
So when it comes to keeping the 
lights on and their sap basis, 

156
00:09:10,800 --> 00:09:15,600
administrators doing the job, 
they are more in to accept to 

157
00:09:15,600 --> 00:09:19,100
use automation there as well. 
And I assume precaution you are 

158
00:09:19,100 --> 00:09:21,500
on the same project. 
Are you on the same project, 

159
00:09:21,500 --> 00:09:23,600
right now? 
Yeah. 

160
00:09:23,600 --> 00:09:31,600
So our goal is to make a sure 
the best platform to run sap, 

161
00:09:31,800 --> 00:09:34,500
right? 
So, several common goal, well 

162
00:09:34,500 --> 00:09:36,500
aligned with red hat, as well as
sap. 

163
00:09:37,100 --> 00:09:39,100
Yes. 
And interesting about your 

164
00:09:39,100 --> 00:09:41,800
learnings prakash, obviously, 
because Microsoft and disappears

165
00:09:41,800 --> 00:09:45,700
been partners for forever. 
What was the change on your 

166
00:09:45,700 --> 00:09:49,300
business unit? 
You know, with SB going to Cloud

167
00:09:49,300 --> 00:09:54,300
ear P having this hyper scale of
strategy with Microsoft Azure. 

168
00:09:54,400 --> 00:09:56,200
Obviously, one of the major 
partner there. 

169
00:09:56,700 --> 00:09:59,800
What changes did you notice on 
the customer side? 

170
00:10:00,300 --> 00:10:06,700
Yes, a couple of observations so
there is a huge shift in the 

171
00:10:06,800 --> 00:10:10,600
operating mindset rape. 
So there's a heavy capex 

172
00:10:10,600 --> 00:10:13,700
investment typically involved in
traditional implementation. 

173
00:10:13,800 --> 00:10:18,500
Mentation days, lot of cycle, 
time taken, even to provision. 

174
00:10:18,500 --> 00:10:22,100
The first virtual machine are 
first system to have a Sandbox, 

175
00:10:22,100 --> 00:10:23,800
right? 
It used to take months to get 

176
00:10:23,800 --> 00:10:27,200
that, right, as opposed to few 
minutes of clicking some buttons

177
00:10:27,200 --> 00:10:29,500
and then you have a system up 
and running in no time. 

178
00:10:29,500 --> 00:10:31,700
So you can do pocs, really 
quickly. 

179
00:10:32,000 --> 00:10:35,000
Faster, time to Market and all 
of the complexities that you 

180
00:10:35,000 --> 00:10:37,900
have in managing a data center 
at all layers, right? 

181
00:10:37,900 --> 00:10:41,900
From the infra layer managing 
the hardware and all the, you 

182
00:10:41,900 --> 00:10:45,000
know, the vendor support that 
You two have managing a Data 

183
00:10:45,000 --> 00:10:48,000
Center and all the applications 
for that you need to have on top

184
00:10:48,000 --> 00:10:51,200
of it, right? 
So sap has done a phenomenal job

185
00:10:51,800 --> 00:10:55,300
of coming up with various 
different deployment models, and

186
00:10:55,300 --> 00:10:58,800
options that will suit a variety
of customers with various needs 

187
00:10:58,800 --> 00:11:01,200
across the Spectrum. 
Bright star, getting very large 

188
00:11:01,200 --> 00:11:04,900
Enterprises all the way down to 
small and medium segment. 

189
00:11:04,900 --> 00:11:09,200
Customers so quickly. 
We could put together some of 

190
00:11:09,200 --> 00:11:14,000
the sap scenarios out of the box
and test it and take It to 

191
00:11:14,000 --> 00:11:17,600
Market very quick. 
So a lot of our sap customers 

192
00:11:17,600 --> 00:11:22,300
are embracing some of it and the
other aspect to that is also the

193
00:11:22,300 --> 00:11:24,000
Innovation that comes along 
with, right? 

194
00:11:24,000 --> 00:11:27,000
It's no longer low-cost 
discussion. 

195
00:11:27,200 --> 00:11:30,400
So what else can you do? 
One Cloud Beyond just running 

196
00:11:30,400 --> 00:11:34,400
sap workloads on cloud, right? 
You could unleash Innovation, 

197
00:11:34,400 --> 00:11:39,400
you can use sap s analytics and 
AI Services. 

198
00:11:39,600 --> 00:11:43,400
Bill Mission machine learning 
models and derive. 

199
00:11:44,000 --> 00:11:46,400
That you never had before for 
your Enterprise, right? 

200
00:11:46,400 --> 00:11:49,500
And it's out of the possibility 
that Leah combined with 

201
00:11:49,500 --> 00:11:52,200
Microsoft Technologies. 
When it comes to collaboration 

202
00:11:52,200 --> 00:11:55,000
on the Microsoft team space and 
things like that, it makes it 

203
00:11:55,000 --> 00:12:01,700
even, you know, more exciting 
for our customers, because you 

204
00:12:01,700 --> 00:12:05,700
lead to efficiency, right? 
And privations here improve 

205
00:12:05,700 --> 00:12:09,800
productivity as well. 
That's a very good say where I 

206
00:12:09,800 --> 00:12:12,700
wanted to go a bit closer to end
users and you just mentioned 

207
00:12:12,700 --> 00:12:16,100
practice, the integration with 
Microsoft teams that ACA PS4 

208
00:12:16,800 --> 00:12:20,600
Hana Cloud offers as an early 
adopter program with the latest 

209
00:12:20,600 --> 00:12:24,500
product updates, 0 to 20, 2008, 
version of ogres very simple 

210
00:12:24,500 --> 00:12:25,800
question. 
Prakash, what did you hear about

211
00:12:25,800 --> 00:12:29,700
that one? 
Yeah, so great collaboration in 

212
00:12:29,700 --> 00:12:33,800
general rate leads to increased 
productivity and improve 

213
00:12:33,800 --> 00:12:38,100
employee efficiency. 
In general, it can also affect 

214
00:12:38,100 --> 00:12:41,600
the quality. 
Of service, our customers and 

215
00:12:41,600 --> 00:12:45,500
customer receives in general. 
And right, if you just look at 

216
00:12:45,500 --> 00:12:49,000
our Microsoft teams, adoption, 
he throws. 

217
00:12:49,000 --> 00:12:52,500
Several folds during the covid 
time, right? 

218
00:12:52,500 --> 00:12:55,500
And also its continuing to grow 
post covid as well. 

219
00:12:55,500 --> 00:13:00,700
And I think we are over 250 
million monthly active users at 

220
00:13:00,700 --> 00:13:05,100
this point. 
So the S4 Hana Cloud, 7:40 

221
00:13:05,100 --> 00:13:08,200
update is a very exciting 
release press. 

222
00:13:08,800 --> 00:13:12,700
Specifically, the integration 
with Microsoft teams that are 

223
00:13:12,700 --> 00:13:16,500
users can take advantage of 
Rights through the early adopter

224
00:13:16,500 --> 00:13:19,200
CARE program. 
So with the new feature that 

225
00:13:19,200 --> 00:13:24,200
we've launched the users can now
take advantage of the share to 

226
00:13:24,200 --> 00:13:28,000
Microsoft teams. 
Option that would allow the 

227
00:13:28,000 --> 00:13:33,200
users to share the data from any
sap fiori elements app to their 

228
00:13:33,200 --> 00:13:36,600
co-workers and tag a message. 
Say okay, so look at all of 

229
00:13:36,600 --> 00:13:40,000
these or fix the issues here. 
Can you take it for processing 

230
00:13:40,000 --> 00:13:42,100
and things like that and 
collaborate with their 

231
00:13:42,100 --> 00:13:44,500
co-workers, using Microsoft 
teams? 

232
00:13:44,800 --> 00:13:47,900
So the recipients can just 
simply click the link and then 

233
00:13:47,900 --> 00:13:50,800
it will take them right into the
data item that was shared with 

234
00:13:50,800 --> 00:13:54,200
them, so they can collaborate 
efficiently and ultimately 

235
00:13:54,200 --> 00:13:57,000
reading to employ efficiency and
productivity. 

236
00:13:57,900 --> 00:14:00,700
And this is just one of the 
features that was released in 

237
00:14:00,700 --> 00:14:03,300
7:40, right? 
So users, God allow the 

238
00:14:03,300 --> 00:14:06,700
horizontal theme that comes with
accessibility features. 

239
00:14:07,000 --> 00:14:08,500
The in-house Banking, and 
finance. 

240
00:14:08,600 --> 00:14:11,900
As business process scheduling 
in supply chain, developer 

241
00:14:11,900 --> 00:14:16,000
extensibility, manufacturing and
service updates and RPA and so 

242
00:14:16,000 --> 00:14:18,900
on and on and on. 
So the Innovation is not going 

243
00:14:18,900 --> 00:14:22,100
to stop and we will continue to 
innovate with sap together as 

244
00:14:22,100 --> 00:14:24,400
well. 
So, I think it's a great time 

245
00:14:24,400 --> 00:14:28,700
for our customers to consider 
and plan the adoption Journey 

246
00:14:28,700 --> 00:14:31,600
for us for her. 
A picture could not agree, more 

247
00:14:31,600 --> 00:14:34,400
practice, we tested at ourself 
obviously, as we are going to be

248
00:14:34,400 --> 00:14:37,800
end user to at sap and a 
thrilled to see how smooth it 

249
00:14:37,800 --> 00:14:40,000
was. 
And The value is obvious, right?

250
00:14:40,500 --> 00:14:44,200
And user productivity it's is 
the name of the game Ricardo. 

251
00:14:44,200 --> 00:14:47,300
So we've talked about value for 
the end users and I know that 

252
00:14:47,300 --> 00:14:52,000
right at is a lot in these 
intelligent Erp, adding 

253
00:14:52,000 --> 00:14:56,100
intelligence to business 
processes with machine learning 

254
00:14:56,300 --> 00:15:01,800
with eventually, a, I can you 
give some examples of processes 

255
00:15:01,800 --> 00:15:05,600
where you've been able to add 
value to end users with 

256
00:15:05,600 --> 00:15:08,500
intelligent processes or making,
that's a standard process. 

257
00:15:08,600 --> 00:15:10,500
This is even more intelligent. 
Yeah. 

258
00:15:11,000 --> 00:15:16,000
So for this first comes into my 
money says a red hat insights 

259
00:15:16,200 --> 00:15:19,800
because his that's part of the 
platform that we offer to sap 

260
00:15:19,800 --> 00:15:22,300
customers. 
So real insights is software as 

261
00:15:22,300 --> 00:15:25,200
a service and it's using 
artificial intelligence and 

262
00:15:25,208 --> 00:15:29,700
machine learning and what it 
tries to do or what it does is 

263
00:15:30,100 --> 00:15:35,100
kind of proactive monitoring and
it kind of complements solution 

264
00:15:35,100 --> 00:15:37,500
manager. 
So what solution manager does, 

265
00:15:37,500 --> 00:15:41,300
add more applications People or 
the early whatever report do are

266
00:15:41,300 --> 00:15:46,200
more a application-level 
insights dusted more as 

267
00:15:47,000 --> 00:15:48,800
operating system level and host 
levels. 

268
00:15:48,800 --> 00:15:53,800
So it makes sure that any time 
all the sap servers are 

269
00:15:53,800 --> 00:15:57,200
complying with all the sap notes
that are needed to run the work 

270
00:15:57,200 --> 00:16:00,300
load speed, as if Hannah or 
build your application, perform 

271
00:16:00,300 --> 00:16:04,200
a lie. 
So before ever occurs, if it 

272
00:16:04,200 --> 00:16:07,400
sees that there are some 
characteristics that has led to 

273
00:16:07,400 --> 00:16:11,700
a number in the past. 
It will say okay this is say you

274
00:16:11,700 --> 00:16:15,900
need to apply this package to 
this to this server or whatever.

275
00:16:16,100 --> 00:16:20,500
Any combination with ansible it 
can do the reputation before it 

276
00:16:20,500 --> 00:16:22,600
occurs. 
So this is good for. 

277
00:16:23,100 --> 00:16:27,300
Well, if you consider any users,
the ACP basis, administrators. 

278
00:16:27,300 --> 00:16:30,200
Because at the end of the day, 
that's making their life easier.

279
00:16:30,500 --> 00:16:33,600
But also in other processes with
artificial intelligence and 

280
00:16:33,600 --> 00:16:38,200
machine learning, we have also 
been doing a lot of work with 

281
00:16:38,300 --> 00:16:40,400
us. 
The data intelligence so 

282
00:16:40,600 --> 00:16:44,800
complementing, they are they 
artificial intelligence 

283
00:16:44,800 --> 00:16:47,300
capabilities that it has in 
providing a platform for you 

284
00:16:47,300 --> 00:16:51,200
because, you know, the array had
provides all been shipped which 

285
00:16:51,200 --> 00:16:54,400
is a kubernetes platform on 
which data intelligence can run.

286
00:16:55,000 --> 00:16:58,000
So we are doing a lot of work. 
We will together with sap on 

287
00:16:58,000 --> 00:17:01,700
that and also with other 
partners, like Intel because 

288
00:17:01,700 --> 00:17:04,700
they are also using their 
artificial intelligence and 

289
00:17:04,700 --> 00:17:07,700
machine learning libraries to 
incorporate them into use cases 

290
00:17:07,800 --> 00:17:11,300
like Supply. 
Chained to the for date 

291
00:17:11,300 --> 00:17:15,700
intelligence. 
Also we jump some pocs in which 

292
00:17:15,700 --> 00:17:19,599
say we can come up with 
recommendations for customers 

293
00:17:19,599 --> 00:17:23,400
that are going to have shop for 
example and depending on where 

294
00:17:23,400 --> 00:17:28,099
there's spending more time, they
can we can send them a take 

295
00:17:28,099 --> 00:17:31,100
intelligence can send them 
recommendations on where to go 

296
00:17:31,100 --> 00:17:33,500
next. 
So, yeah, I think that's a 

297
00:17:33,500 --> 00:17:38,400
compliment a bit any user. 
And also sap basis a minute 

298
00:17:38,700 --> 00:17:41,400
Years if you consider them as 
and users of the product. 

299
00:17:41,600 --> 00:17:46,400
And that's how we are trying to 
help with artificial 

300
00:17:46,400 --> 00:17:47,600
intelligence and machine 
learning. 

301
00:17:48,400 --> 00:17:51,100
What are some of the other 
latest offering from red hat 

302
00:17:51,200 --> 00:17:53,300
from which sap customer can 
benefit? 

303
00:17:53,400 --> 00:17:57,800
You want to explain a bit more? 
Yeah, we can talk in terms of 

304
00:17:57,800 --> 00:18:01,000
latest of freezer because I read
how do you suppose always doing 

305
00:18:01,000 --> 00:18:03,200
and running certifications for 
sap Hana. 

306
00:18:03,200 --> 00:18:06,500
So every minor version of the 
operating system needs to be 

307
00:18:06,500 --> 00:18:11,200
certified as so, Just about two 
weeks ago, Rel 8.6 got 

308
00:18:11,200 --> 00:18:14,400
certified. 
So now uses that her wish to to 

309
00:18:14,400 --> 00:18:17,100
go to that version week they can
go for it. 

310
00:18:17,400 --> 00:18:21,400
That version for example is is 
available on a sure? 

311
00:18:21,400 --> 00:18:23,900
For sure. 
And it can be used as the 

312
00:18:23,900 --> 00:18:27,400
operating system for the sap 
data for the sap, Hana data 

313
00:18:27,400 --> 00:18:29,700
base. 
That's underlined, the sap is 

314
00:18:29,700 --> 00:18:33,700
for Hannah club without 
something in about the 

315
00:18:33,700 --> 00:18:35,700
certifications or very 
consistent certifications. 

316
00:18:35,700 --> 00:18:41,500
But also recently in the 
highwomen Ability to main, we 

317
00:18:41,500 --> 00:18:45,000
added some new scenarios for 
that are supported with high 

318
00:18:45,000 --> 00:18:46,600
availability. 
So one of them is the coast 

319
00:18:46,600 --> 00:18:50,500
optimized installations of sap 
Hana. 

320
00:18:50,500 --> 00:18:53,700
So that means, for example, 
customers who want to save a bit

321
00:18:53,700 --> 00:18:57,900
on resources, they might be able
to install an sap Hana 

322
00:18:57,900 --> 00:19:01,900
production DB the same server as
an test DB for example. 

323
00:19:02,200 --> 00:19:05,600
So now they can create a page 
mode, cluster pacemaker, cluster

324
00:19:05,600 --> 00:19:09,800
sorry without any supported by 
Rel Also, another interesting 

325
00:19:09,800 --> 00:19:13,100
scenario for the high 
availability is the multi to 

326
00:19:13,100 --> 00:19:14,800
replication, whoops, or remove 
the charger. 

327
00:19:14,800 --> 00:19:17,200
Multi-tier has been supported 
for a long time now. 

328
00:19:17,400 --> 00:19:19,600
So multi-tier application. 
When we're talking about 

329
00:19:19,600 --> 00:19:24,100
clusters is a, you have an sap 
Hana data base, and it's 

330
00:19:24,100 --> 00:19:26,700
replicating at the same time to 
several targets. 

331
00:19:27,000 --> 00:19:30,500
So then this way, they achieve 
more data consistency on my data

332
00:19:30,500 --> 00:19:35,200
redundancy so that kind of of 
scenery supported now we're by 

333
00:19:35,200 --> 00:19:41,600
the reliability add-on and So if
we talk her, we go back to 

334
00:19:41,600 --> 00:19:44,400
automation. 
Red had actively Works in 

335
00:19:44,400 --> 00:19:47,000
collaboration affair, with 
community of practices for 

336
00:19:48,000 --> 00:19:50,400
developing new assets. 
New uncivil to make sure that's 

337
00:19:50,400 --> 00:19:54,100
it's for sap. 
So what we try to do with 

338
00:19:54,100 --> 00:19:58,100
everyone who's interested in 
automating processes that sap, 

339
00:19:58,300 --> 00:20:04,000
we try to create playbooks and 
rolls until production rose that

340
00:20:04,000 --> 00:20:08,400
automate day-to-day operations 
for sap surface. 

341
00:20:08,500 --> 00:20:13,000
A system refreshes changing 
parameters upgraded - the 

342
00:20:13,000 --> 00:20:16,200
colonel. 
No, no system copies. 

343
00:20:16,200 --> 00:20:19,600
So I said you're changing 
parameters in the database 

344
00:20:19,600 --> 00:20:21,300
database operations 
backup/restore. 

345
00:20:21,500 --> 00:20:24,000
So not only I said at the 
beginning not only is about 

346
00:20:24,000 --> 00:20:27,500
using automation to migrate your
workloads to the cloud but it's 

347
00:20:27,500 --> 00:20:31,700
also about using it day to day 
and make your life easier and 

348
00:20:32,300 --> 00:20:35,700
saving up time of the basis 
administrators. 

349
00:20:36,500 --> 00:20:39,700
Thanks Ricardo prakash. 
How is Microsoft and right at 

350
00:20:39,700 --> 00:20:42,800
partnering to bring out this 
strong offering for the SP 

351
00:20:42,800 --> 00:20:45,300
customers. 
Yeah, great question. 

352
00:20:45,300 --> 00:20:48,500
Thanks Yannick. 
So red hat and Microsoft have 

353
00:20:48,500 --> 00:20:53,100
been a very strong in general at
Great Ally and straight to Red 

354
00:20:53,100 --> 00:20:55,600
Hat. 
Enterprise Linux, the world's 

355
00:20:55,600 --> 00:20:58,900
leading Enterprise Linux 
platform and there are several 

356
00:20:58,900 --> 00:21:01,700
customers that use red hat. 
Enterprise Linux distribution to

357
00:21:01,700 --> 00:21:04,300
run a business workloads on 
Microsoft cloud today. 

358
00:21:05,500 --> 00:21:08,600
So we also partner with red hat 
on openshift, which is now now 

359
00:21:08,600 --> 00:21:12,700
available on HR, which we call 
as Aro, Red Hat, ansible 

360
00:21:12,700 --> 00:21:16,600
automation platform, which has 
now become the de facto standard

361
00:21:16,600 --> 00:21:19,600
for configuration as code is 
also available on Microsoft 

362
00:21:19,600 --> 00:21:22,900
cloud. 
We also have red hat, JBoss 

363
00:21:22,900 --> 00:21:26,500
Enterprise application platform,
which is optimized for cloud in 

364
00:21:26,500 --> 00:21:29,100
containers available on 
Microsoft cloud as well. 

365
00:21:29,100 --> 00:21:33,500
So, this is all up Alliance rain
but specifically, for sap as 

366
00:21:33,500 --> 00:21:37,200
well, the two companies are 
strong partners and work very 

367
00:21:37,200 --> 00:21:39,900
closely together and we are 
Engineering programs. 

368
00:21:40,400 --> 00:21:43,900
For example, Red Hat was a great
collaborator and co-development 

369
00:21:43,900 --> 00:21:48,400
partner for Monitoring Solutions
to bring out the Telemetry that 

370
00:21:48,400 --> 00:21:51,700
we have on the infrastructure 
layer. 

371
00:21:52,200 --> 00:21:57,200
We also work with red hat on 
defining and enhancing the 

372
00:21:57,200 --> 00:21:59,700
reference. 
Architectures published ASAP to 

373
00:21:59,700 --> 00:22:03,300
work better on Azure with the 
red hat. 

374
00:22:03,300 --> 00:22:05,200
Enterprise Linux operating 
system. 

375
00:22:06,100 --> 00:22:10,100
We also work together on putting
together some open source 

376
00:22:10,400 --> 00:22:13,600
deployment automation framework 
that up our customers and 

377
00:22:13,600 --> 00:22:17,200
partners can take advantage of 
if the customers choose to go 

378
00:22:17,200 --> 00:22:19,300
that route, right? 
And which is available for free 

379
00:22:19,300 --> 00:22:23,900
in GitHub to summarize, strong 
Partnerships at all levels 

380
00:22:23,900 --> 00:22:27,100
Beyond sap. 
And there are specific programs 

381
00:22:27,100 --> 00:22:31,400
appear working together to also 
bring Innovation to customers 

382
00:22:31,400 --> 00:22:35,200
and partners, do you want to 
invention a few of the latest 

383
00:22:35,200 --> 00:22:39,300
offerings from Microsoft. 
So for join customer can Looking

384
00:22:39,300 --> 00:22:41,100
for. 
Yeah, great question again, 

385
00:22:41,100 --> 00:22:44,400
Yannick. 
So I'll touch on briefly on sap 

386
00:22:44,400 --> 00:22:48,400
and Microsoft's partnership. 
Again, we have been partners for

387
00:22:48,400 --> 00:22:53,200
about 30 years now, serving 
Enterprise customers and we work

388
00:22:53,200 --> 00:22:58,400
together obviously to bring our 
customers value throughout their

389
00:22:58,400 --> 00:23:01,100
migration Journey as they 
migrate each Mission critical 

390
00:23:01,100 --> 00:23:06,000
applications for sap to cloud 
and Microsoft ourselves. 

391
00:23:06,000 --> 00:23:10,200
I believe is the only hyper 
scalar During our own Finance 

392
00:23:10,200 --> 00:23:14,700
supply chain and HR business 
processes on sap for the last 25

393
00:23:14,700 --> 00:23:18,000
years and we are running that in
our own cloud for over three 

394
00:23:18,000 --> 00:23:22,000
years. 
In terms of what we do together,

395
00:23:22,000 --> 00:23:23,600
right? 
They're always looking for ways 

396
00:23:23,600 --> 00:23:27,200
to enhance the user experience 
for sap running on a show. 

397
00:23:27,200 --> 00:23:34,000
Right example, we just released 
Jin GA sap private link which 

398
00:23:34,000 --> 00:23:36,900
reduces the complexity of 
connections when you want to 

399
00:23:36,900 --> 00:23:40,600
connect sa PBT. 
P on Microsoft cloud. 

400
00:23:40,600 --> 00:23:43,800
If you have some of the services
that you want to take advantage 

401
00:23:43,800 --> 00:23:46,900
of either, you know, deployment 
options here. 

402
00:23:47,800 --> 00:23:51,100
And also, the other thing I 
would mention is an Azure Center

403
00:23:51,100 --> 00:23:55,400
for sap Solutions. 
Also call this a CSS, is another

404
00:23:55,600 --> 00:23:58,700
first party offering that 
they've released on Azure which 

405
00:23:58,700 --> 00:24:01,700
will help you kind of like 
deploy SAP systems and also 

406
00:24:01,700 --> 00:24:04,000
operate some of it. 
Some of the aspects of 

407
00:24:04,000 --> 00:24:08,500
operations is covered as well as
your single pane of glass for An

408
00:24:08,508 --> 00:24:12,800
sap system record and Azure. 
We also revamped our monitoring 

409
00:24:12,800 --> 00:24:15,800
solution, which is called, as 
your monitor for sap, which is a

410
00:24:15,808 --> 00:24:19,200
public preview. 
And ACS is the one I mentioned 

411
00:24:19,200 --> 00:24:20,900
before is in public preview, as 
well. 

412
00:24:21,800 --> 00:24:24,500
So the earlier version of the 
monitoring solution required, a 

413
00:24:24,500 --> 00:24:27,800
deployment, VM to be created and
that you have to manage yourself

414
00:24:27,800 --> 00:24:29,700
and things like that. 
But now the new version is built

415
00:24:29,700 --> 00:24:32,300
using Azure functions so you 
don't have the management 

416
00:24:32,300 --> 00:24:34,300
overhead as well. 
So these are some of the 

417
00:24:34,300 --> 00:24:38,000
exciting things, a lot more 
coming up in the near future. 

418
00:24:38,800 --> 00:24:41,600
Thank you, prakash before we 
close the podcast like to end up

419
00:24:41,600 --> 00:24:44,800
with the same question with the 
two of you Cloud obviously is 

420
00:24:44,800 --> 00:24:46,500
about speed of innovation, 
right? 

421
00:24:46,500 --> 00:24:48,400
We are very short, Innovation 
Cycles. 

422
00:24:48,400 --> 00:24:50,500
We have the ability to she 
practically overnight 

423
00:24:50,500 --> 00:24:53,300
Innovations to our customers. 
So looking at the Joint 

424
00:24:53,300 --> 00:24:57,100
partnership and maybe starting 
with you Ricardo, what would be 

425
00:24:57,100 --> 00:24:59,100
your, you know, being with 
customers? 

426
00:24:59,100 --> 00:25:01,800
What are you hearing the key 
things that ACP should kind of 

427
00:25:01,800 --> 00:25:06,400
hit overnight to make the 
partnership even stronger? 

428
00:25:07,000 --> 00:25:10,000
Yes, oh yes. 
Practice has mentioned before 

429
00:25:10,200 --> 00:25:13,900
they are asking the Lord about 
monitoring proactive, Monitoring

430
00:25:13,900 --> 00:25:17,600
Solutions. 
So that Tails back to to the 

431
00:25:17,600 --> 00:25:21,200
insights and a lot of customers 
are asking about that and 

432
00:25:21,200 --> 00:25:24,900
nothing, they're very interested
but also as we mentioned before 

433
00:25:24,900 --> 00:25:27,500
as well about the day-to-day 
operation so they said okay now 

434
00:25:27,500 --> 00:25:32,200
my sap workloads in my ears or 
Honda cloudy, Sinatra's migrated

435
00:25:32,200 --> 00:25:37,100
or perfect but now we want to be
able to manage here in a better 

436
00:25:37,100 --> 00:25:40,200
way with automation. 
They're asking a lot of with for

437
00:25:40,200 --> 00:25:43,200
a specific use cases and is good
because they're feeding us back.

438
00:25:43,800 --> 00:25:47,200
And we know where to work and 
which use cases to prioritize in

439
00:25:47,200 --> 00:25:49,700
terms of automation? 
Thank you for sharing. 

440
00:25:49,700 --> 00:25:51,900
What about you prakash? 
What is your point of view here?

441
00:25:52,300 --> 00:25:56,300
Yeah, I agree with Ricardo. 
I think the big ask we see from 

442
00:25:56,300 --> 00:25:59,300
customers and partners this 
Automation in general rain. 

443
00:26:00,300 --> 00:26:04,200
So in various aspects, obviously
sap is a mission critical 

444
00:26:04,200 --> 00:26:07,300
application running business 
workloads. 

445
00:26:07,900 --> 00:26:13,700
But the Migration Journey could 
be something that the customer 

446
00:26:13,700 --> 00:26:18,600
needs to put a lot of focus on 
so the Automation and during the

447
00:26:18,600 --> 00:26:22,300
deployment of SAP systems 
Automation in the operations of 

448
00:26:22,300 --> 00:26:26,300
deployment of the SAP systems 
and also the Automation in the 

449
00:26:26,308 --> 00:26:31,500
space of extensions, right? 
So bring in data and analytics 

450
00:26:31,500 --> 00:26:35,500
and insights together and make 
it as easy for adoption as 

451
00:26:35,500 --> 00:26:39,200
possible, through automation 
built and Allowed to enter 

452
00:26:39,200 --> 00:26:42,600
customer migration Journey 
starting from Discovery 

453
00:26:42,600 --> 00:26:46,400
preparation, migration 
operations and even you know 

454
00:26:46,400 --> 00:26:48,400
extensions and Innovation. 
Right. 

455
00:26:49,100 --> 00:26:52,100
So our mission is to keep I 
think thank you. 

456
00:26:52,100 --> 00:26:53,700
Thank you prakash. 
I think these are great. 

457
00:26:53,700 --> 00:26:56,800
Closing words, you mentioned the
migration Journey cloud is 

458
00:26:56,800 --> 00:27:00,600
definitely a journey punctuated 
with Innovations transformation.

459
00:27:01,900 --> 00:27:04,700
Thanks a lot Ricardo. 
Thanks a lot prakash for being 

460
00:27:04,700 --> 00:27:08,200
with us today. 
Thanks to our audience. 

461
00:27:08,300 --> 00:27:11,200
For following us, providing us 
with feedback. 

462
00:27:11,400 --> 00:27:14,300
I have learned a lot today and 
I'm sure our audience will enjoy

463
00:27:14,300 --> 00:27:19,200
this one to feel free to drop us
an email via inside S4 at AC 

464
00:27:19,200 --> 00:27:24,000
p.com and let us know which 
topics are of your interest. 

465
00:27:24,900 --> 00:27:29,500
Thanks again to Ricardo prakash 
tuning all next time and be 

466
00:27:29,500 --> 00:27:31,200
inside a CPS for Hannah.
