1
00:00:10,040 --> 00:00:13,560
Welcome to our podcast Inside 
Saps for HANA. 

2
00:00:14,160 --> 00:00:17,680
There's no Customer success 
without Product Success and 

3
00:00:17,720 --> 00:00:21,680
Project Success. 
Today we talk about how SAP 

4
00:00:21,680 --> 00:00:25,160
Partner Syntax accelerates 
companies around high 

5
00:00:25,160 --> 00:00:29,240
performance batteries and 
mobility business with SAP Asana

6
00:00:29,240 --> 00:00:33,400
Cloud Public Edition. 
My name is Mark Sertel and I'm 

7
00:00:33,400 --> 00:00:37,720
honored to have Roman Freider, 
Global Center of Excellence, 

8
00:00:37,760 --> 00:00:41,600
Leader Manufacturing Industry 
and Director of Presales from 

9
00:00:41,600 --> 00:00:43,800
SAP Partners Index on the show 
today. 

10
00:00:44,680 --> 00:00:46,760
Welcome to Roman and how are you
feeling today? 

11
00:00:47,840 --> 00:00:50,800
Thank you, Marcus. 
Great to be on your show today 

12
00:00:51,120 --> 00:00:54,640
and it's pretty warm outside. 
We have 31 degrees already, 9 

13
00:00:54,640 --> 00:00:57,340
degrees Fahrenheit. 
How is the weather at home? 

14
00:00:57,420 --> 00:01:00,340
Where you live, it's also very 
hot. 

15
00:01:00,460 --> 00:01:03,020
We have about the same 
temperature today. 

16
00:01:03,620 --> 00:01:06,460
It rained a little bit this 
morning, but the temperature is 

17
00:01:06,460 --> 00:01:10,300
climbing. 
Again, Roman, I know you're an 

18
00:01:10,300 --> 00:01:14,940
expert in driving digital 
transformations in cloud EP and 

19
00:01:14,940 --> 00:01:18,860
digital manufacturing projects. 
And before joining, actually 

20
00:01:18,860 --> 00:01:24,100
consulting at the syntax, you 
worked for an SAP customer and I

21
00:01:24,100 --> 00:01:27,470
know you like NASCAR and what 
else would you like to share in 

22
00:01:27,470 --> 00:01:29,750
our beginning? 
Yeah, my background basically 

23
00:01:29,750 --> 00:01:33,270
starts in manufacturing. 
So I worked several years for 

24
00:01:33,270 --> 00:01:36,310
SAP customers, global SAP 
customers in the automotive 

25
00:01:36,310 --> 00:01:38,950
sector. 
I'm a motorsport enthusiast, 

26
00:01:39,270 --> 00:01:41,230
like watch Formula One 
yesterday. 

27
00:01:41,230 --> 00:01:44,350
And then of course NASCAR is 
also a passion from my side. 

28
00:01:44,710 --> 00:01:47,870
And a little secret what I could
tell you is this is my first 

29
00:01:47,870 --> 00:01:51,230
podcast ever and it's a new 
experience. 

30
00:01:51,230 --> 00:01:54,110
But I'm also a little bit 
nervous to be honest. 

31
00:01:54,750 --> 00:01:57,590
Thanks for sharing someone. 
I did not notice that you 

32
00:01:57,710 --> 00:02:00,470
actually were nervous. 
Maybe before we start to go 

33
00:02:00,470 --> 00:02:04,630
further into the topic, you can 
say what syntax stands for and 

34
00:02:04,630 --> 00:02:06,910
what actually your company does.
Thanks. 

35
00:02:07,110 --> 00:02:10,470
Today's syntax is a leading 
managed cloud provider from 

36
00:02:10,470 --> 00:02:13,630
mission critical applications. 
With our approach, we would like

37
00:02:13,630 --> 00:02:17,830
to act as a partique at scale 
with offices worldwide and over 

38
00:02:17,830 --> 00:02:20,350
1000 customers across all 
business segments. 

39
00:02:20,660 --> 00:02:23,820
Syntax has deep and diversified 
customer based with long 

40
00:02:23,820 --> 00:02:26,980
standing relationships 
developing companies and 

41
00:02:26,980 --> 00:02:29,500
manufacturers. 
We can also call them 

42
00:02:29,540 --> 00:02:31,900
Gigafactories or high 
performance. 

43
00:02:31,900 --> 00:02:35,140
Battery cells and applications 
in the vehicle and mobility 

44
00:02:35,140 --> 00:02:38,460
segment are becoming more and 
more strategically important. 

45
00:02:38,460 --> 00:02:41,260
In today's world. 
We can see improvements and 

46
00:02:41,260 --> 00:02:44,340
charging capabilities for 
example or high temperature 

47
00:02:44,340 --> 00:02:48,710
stability and safety also maybe 
a lot of Oem's. 

48
00:02:48,710 --> 00:02:51,470
So the original equipment 
manufacturers have a big 

49
00:02:51,510 --> 00:02:55,950
interest in becoming CO2 neutral
at least by 20-30 with local 

50
00:02:55,950 --> 00:02:58,910
production and supply of 
material with a low CO2 

51
00:02:58,910 --> 00:03:01,310
footprint. 
Can you maybe share your 

52
00:03:01,310 --> 00:03:05,430
experience with us how you see 
the market shifting not only 

53
00:03:05,430 --> 00:03:08,910
from the classical engine to 
battery cells, but maybe from 

54
00:03:08,910 --> 00:03:12,550
the overall market perspective? 
So the global demand for 

55
00:03:12,550 --> 00:03:14,670
batteries are increasing 
dramatically. 

56
00:03:15,150 --> 00:03:19,350
If we see the forecast for 
20-30, it's just rapidly how 

57
00:03:19,350 --> 00:03:22,990
quick those Gigafactories has to
let's say build up from the 

58
00:03:22,990 --> 00:03:26,310
Greenfield and with the 
Greenfield, I mean building a 

59
00:03:26,310 --> 00:03:30,910
new factory, founding a joint 
venture etcetera where currently

60
00:03:30,910 --> 00:03:34,990
no manufacturing is ever. 
If we just see how quickly 

61
00:03:35,070 --> 00:03:38,550
battery sell manufacturer was 
established the last one or two 

62
00:03:38,550 --> 00:03:41,950
years, this journey was just the
beginning what what we saw. 

63
00:03:42,650 --> 00:03:45,970
Also what we see where we often 
is that especially with EV 

64
00:03:46,050 --> 00:03:49,770
better resells and module, the 
time to market is very crucial. 

65
00:03:50,050 --> 00:03:54,610
What does it mean? 
So in the past if we talk about 

66
00:03:54,610 --> 00:03:59,490
our classical big OEMs, they got
long journey production 

67
00:03:59,490 --> 00:04:03,970
implementations like creating a 
new car takes years of 

68
00:04:03,970 --> 00:04:06,210
development until serious 
production. 

69
00:04:06,740 --> 00:04:10,820
With the EV space, we talk about
days and weeks and months. 

70
00:04:10,900 --> 00:04:12,500
We don't talk about years 
anymore. 

71
00:04:12,940 --> 00:04:17,339
How is this so different. 
So big OEMs, what we all know 

72
00:04:17,339 --> 00:04:20,620
from the whole world, they 
founding joint ventures in order

73
00:04:20,620 --> 00:04:24,740
to start Greenfield factories or
they change their business 

74
00:04:24,740 --> 00:04:27,580
dramatically. 
One of the best example is one 

75
00:04:27,580 --> 00:04:30,780
of our battery sell projects 
we've implemented last year. 

76
00:04:31,540 --> 00:04:34,370
So comparison. 
To the classical project 

77
00:04:34,370 --> 00:04:38,410
implementation, we could say in 
error it was maybe six months of

78
00:04:38,410 --> 00:04:41,770
sales cycle and then maybe 9 to 
12 months of a project 

79
00:04:41,770 --> 00:04:45,250
implementation. 
Nowadays we talk about one to 

80
00:04:45,250 --> 00:04:49,010
two months in sales and just 90 
days of the whole project 

81
00:04:49,010 --> 00:04:52,170
implementation. 
This was just possible because 

82
00:04:52,170 --> 00:04:56,090
of a clear a child approach and 
focusing on standardization. 

83
00:04:56,610 --> 00:04:59,930
And why is that very important 
if we compare for example 

84
00:05:00,450 --> 00:05:04,120
typical OVM? 
And how many variations or how 

85
00:05:04,120 --> 00:05:07,760
many configurations you have? 
In a German premium brand 

86
00:05:07,840 --> 00:05:12,920
configuration you can define 6 
rims, 10,000 seat options, etc. 

87
00:05:13,280 --> 00:05:16,720
If you go to the new EV 
companies, let's say the car 

88
00:05:16,720 --> 00:05:18,840
companies, you maybe have ten 
options. 

89
00:05:19,200 --> 00:05:21,560
So that means also from that 
complexity from the 

90
00:05:21,560 --> 00:05:26,120
manufacturing process and from 
those options they also go back 

91
00:05:26,120 --> 00:05:30,960
to less complex manufacturing 
process in order to drive. 

92
00:05:31,400 --> 00:05:34,960
Cheap manufacturing and to be 
more effective for us as a 

93
00:05:34,960 --> 00:05:39,160
client. 
Maybe you can also give us more 

94
00:05:39,160 --> 00:05:43,040
insights and the important 
factor within the organizations 

95
00:05:43,080 --> 00:05:45,200
we heard at speed, maybe the 
size of the company. 

96
00:05:45,600 --> 00:05:48,320
The important factor starts 
within the organization. 

97
00:05:48,480 --> 00:05:52,640
If you think about a classical 
OEM with X factories around the 

98
00:05:52,640 --> 00:05:57,440
globe and very complex processes
and integration, the speed is 

99
00:05:57,440 --> 00:06:00,870
just not within the innovation. 
Even if the company forgets all 

100
00:06:00,870 --> 00:06:03,910
the internal topic, it would 
still not be fast enough. 

101
00:06:04,710 --> 00:06:07,670
Also, the approach within the 
battery cell companies is 

102
00:06:07,670 --> 00:06:09,950
different. 
One example is that they will 

103
00:06:09,950 --> 00:06:14,350
focus on their key businesses 
manufacturing battery cells 

104
00:06:14,350 --> 00:06:17,870
modules and not running an IT 
department with 50 or more 

105
00:06:17,870 --> 00:06:22,230
employees. 
Currently we have labor shortage

106
00:06:22,310 --> 00:06:25,790
and for the future it would not 
just be right to build up that 

107
00:06:25,790 --> 00:06:28,670
big IT department just to manage
IT systems. 

108
00:06:29,100 --> 00:06:32,420
Therefore, it's very important 
to go with software as a service

109
00:06:32,420 --> 00:06:36,740
solution in order to be future 
proved and out-of-the-box ready 

110
00:06:36,940 --> 00:06:39,540
for new requirements. 
What will come from our 

111
00:06:39,540 --> 00:06:45,420
customers, Customers Syntax has 
great success implementing as a 

112
00:06:45,420 --> 00:06:49,420
PSO on a cloud public edition in
the high performance batteries 

113
00:06:49,420 --> 00:06:51,860
market. 
Now I'm asking myself and 

114
00:06:51,860 --> 00:06:53,820
probably a lot of listeners, how
do you do it? 

115
00:06:53,980 --> 00:06:56,340
What is your secret that you're 
successful? 

116
00:06:57,500 --> 00:07:01,060
I think the secret sauce is our 
employees and the mindset of our

117
00:07:01,060 --> 00:07:03,620
employees. 
But I would like to give you our

118
00:07:03,620 --> 00:07:07,940
5 golden rules in order to drive
the journey of S for HANA Public

119
00:07:07,940 --> 00:07:10,980
cloud implementation. 
One is of course the speed of 

120
00:07:10,980 --> 00:07:14,980
the implementation by using 
standard processes for example 

121
00:07:15,180 --> 00:07:17,780
known as best practice or sub 
model company. 

122
00:07:18,380 --> 00:07:22,420
This is very important because 
SAP has over 800 standard best 

123
00:07:22,420 --> 00:07:25,140
practice scenarios what you 
could use out-of-the-box. 

124
00:07:25,580 --> 00:07:28,620
So why do you need to define a 
special process when there is a 

125
00:07:28,620 --> 00:07:30,220
standard defined already for 
you? 

126
00:07:31,260 --> 00:07:35,580
Second golden rule is you don't 
have any effort in the upgrades.

127
00:07:36,220 --> 00:07:39,900
You don't need to do a five 
month project in your annual or 

128
00:07:40,180 --> 00:07:43,860
BI yearly updates you will get 
in the past every quarter. 

129
00:07:43,860 --> 00:07:47,860
Nowadays you get it every half 
year, some updates and just for 

130
00:07:47,860 --> 00:07:51,020
example within the February 
release is a peak game. 

131
00:07:51,550 --> 00:07:55,550
Customers, over 600 new 
features, API, new best 

132
00:07:55,550 --> 00:07:58,910
practices where you as a company
can use out-of-the-box. 

133
00:07:58,910 --> 00:08:02,510
So that means on Saturday there 
will be the update performed by 

134
00:08:02,510 --> 00:08:06,750
SAP and on Monday morning, 8:00 
AM you start work and 12:00 AM 

135
00:08:07,070 --> 00:08:09,590
and lunchtime you have the new 
process maybe already in your 

136
00:08:09,590 --> 00:08:12,350
production system. 
I mean this is now a little bit 

137
00:08:12,550 --> 00:08:15,430
very easy speaking, the reality 
looks maybe a little bit 

138
00:08:15,430 --> 00:08:18,590
different, but that's how 
cricket could be achieved. 

139
00:08:20,030 --> 00:08:23,060
The third topic is. 
That the business value driven 

140
00:08:23,060 --> 00:08:25,980
implementation of integration 
and extensions. 

141
00:08:26,260 --> 00:08:30,180
So that means we don't need 
every time an IT colleague for 

142
00:08:30,180 --> 00:08:34,659
making a specification, for 
making that addition add on etc.

143
00:08:34,980 --> 00:08:38,740
Because there are a lot of no 
code, no code add-ons available 

144
00:08:38,940 --> 00:08:41,580
where you can build your own 
report, where you can create 

145
00:08:41,580 --> 00:08:44,940
your own dashboard, where you 
don't need to make whatever A5 

146
00:08:44,940 --> 00:08:48,140
day specification and you 
basically have to jump down in 

147
00:08:48,180 --> 00:08:52,390
four hours by yourself. 
The fourth option is of course 

148
00:08:52,550 --> 00:08:57,750
we could reduce our partner or 
SAP implementation efforts by 

149
00:08:57,790 --> 00:09:02,510
reusing the capabilities, the 
best practice scenarios because 

150
00:09:02,750 --> 00:09:05,870
everything what we learn from a 
customer can be in the kind like

151
00:09:05,870 --> 00:09:08,310
reused. 
Of course not the specific for 

152
00:09:08,310 --> 00:09:12,630
this company, but the overall 
achievement of As for HANA 

153
00:09:12,630 --> 00:09:16,990
public cloud implementation is 
basically on the next project 

154
00:09:17,070 --> 00:09:20,190
just accelerating because we 
already know how we've done it. 

155
00:09:20,510 --> 00:09:24,590
We could reuse the standard 
documents and can basically 

156
00:09:24,590 --> 00:09:28,270
accelerate even more. 
At the last point, we have 

157
00:09:28,270 --> 00:09:31,750
multiple customer projects 
already lives in less than 90 

158
00:09:31,750 --> 00:09:33,910
working days. 
And this is very important 

159
00:09:33,910 --> 00:09:37,750
because we have defined within 
our HR approach that we have a 

160
00:09:37,750 --> 00:09:41,670
step by step approach in order 
to hand over the existing 

161
00:09:41,670 --> 00:09:45,270
features, what the customer, AIA
for example, need. 

162
00:09:46,040 --> 00:09:49,000
To the business and then 
continue adding more and more 

163
00:09:49,120 --> 00:09:52,120
features and functions in 
regards to the standard best 

164
00:09:52,120 --> 00:09:55,880
practice scope items. 
Those 5 golden rules help us to 

165
00:09:55,880 --> 00:09:59,160
accelerate, to work with 
customer, to onboard the 

166
00:09:59,160 --> 00:10:03,200
customer and basically be rapid,
fast, perfect. 

167
00:10:03,200 --> 00:10:06,280
Holman, thanks for sharing those
5 golden rules. 

168
00:10:06,360 --> 00:10:10,590
Very impressive. 
If we look at the most technical

169
00:10:10,590 --> 00:10:14,550
challenges in your projects, how
did you solve them together with

170
00:10:14,550 --> 00:10:17,430
your customers in the high 
performance batteries market? 

171
00:10:17,430 --> 00:10:20,150
What do you think? 
SAP can still improve SAP Aswana

172
00:10:20,150 --> 00:10:22,190
Cloud Public Edition in that 
market segment? 

173
00:10:23,030 --> 00:10:27,510
Looking back five years since 
Svana Public Cloud was available

174
00:10:27,830 --> 00:10:31,430
in the old days, called 
Essential now Public as the 

175
00:10:31,430 --> 00:10:36,270
product name, I think SAP made 
significant effort and 

176
00:10:36,270 --> 00:10:38,030
investment to make the product 
better. 

177
00:10:38,760 --> 00:10:43,600
If we look back how we start 
with customers 19 and 20, we 

178
00:10:43,600 --> 00:10:47,960
have probably no idea how we 
solved some of those critical 

179
00:10:47,960 --> 00:10:51,400
things where there was no 
technical solution there back in

180
00:10:51,400 --> 00:10:55,680
the days. 
Nowaday we just can smile and 

181
00:10:55,680 --> 00:10:58,000
think about how do we solve it 
back in the days. 

182
00:10:58,000 --> 00:11:02,320
And there is an hour standard 
solution since we started this 

183
00:11:02,320 --> 00:11:04,640
journey with S for HANA Public 
Cloud. 

184
00:11:05,070 --> 00:11:09,150
SAP delivered thousands of new 
features, APIs, best practices, 

185
00:11:09,830 --> 00:11:12,750
helps us within all of our 
customer implementation because 

186
00:11:12,990 --> 00:11:16,950
every customer who runs on the 
public option gets this new 

187
00:11:16,950 --> 00:11:20,750
feature and functions. 
So that means some application 

188
00:11:20,750 --> 00:11:23,430
or workaround we have 
implemented back in the days 

189
00:11:23,630 --> 00:11:27,030
where we have not a technical 
solution and maybe now 

190
00:11:27,150 --> 00:11:30,990
implemented in the standard of 
the SAP portfolio and we could 

191
00:11:31,150 --> 00:11:33,870
right now just basically remove 
the workaround. 

192
00:11:34,340 --> 00:11:38,020
And use it within the standard. 
One example is back in the days 

193
00:11:38,020 --> 00:11:41,780
when we start with our customer 
smart press shop that were not 

194
00:11:41,860 --> 00:11:44,220
Prts available for the 
production order. 

195
00:11:44,700 --> 00:11:48,740
So that means we got a quick 
workaround and once 21 this 

196
00:11:48,740 --> 00:11:51,620
feature was available generally 
for everyone in February. 

197
00:11:51,860 --> 00:11:55,340
Then we basically just removed 
the workaround and we used the 

198
00:11:55,340 --> 00:11:57,340
standard feature in less than 
two days. 

199
00:11:58,780 --> 00:12:02,020
Also something where I think 
that SAP can improve. 

200
00:12:02,580 --> 00:12:06,300
Is especially if we're talking 
about manufacturing companies 

201
00:12:06,780 --> 00:12:11,260
and we have in Germany love 
creative manufacturing from ETO 

202
00:12:11,260 --> 00:12:15,980
engineering to order to make to 
order to configure to order all 

203
00:12:15,980 --> 00:12:19,260
kind of processes out there. 
And especially if we're talking 

204
00:12:19,260 --> 00:12:22,260
about high performance 
batteries, maybe in the 

205
00:12:22,260 --> 00:12:26,140
beginning there is only one 
phone factor and one battery to 

206
00:12:26,140 --> 00:12:29,140
prove that you can assemble and 
manufacture the battery and the 

207
00:12:29,140 --> 00:12:33,110
quality, but. 
In a very short term you will 

208
00:12:33,110 --> 00:12:37,310
get more and more complexity and
new form factors where you need 

209
00:12:37,830 --> 00:12:41,310
an PLM system in order to map 
the design and of course the 

210
00:12:41,310 --> 00:12:43,910
manufacturing. 
And therefore I would like to 

211
00:12:43,910 --> 00:12:46,870
point out two things. 
One is of course the full 

212
00:12:46,870 --> 00:12:50,710
engineering to order support 
where we have order complex and 

213
00:12:50,710 --> 00:12:54,350
VIP changes etc. 
And of course one of my favorite

214
00:12:54,350 --> 00:12:56,870
features is the external PLM 
integration. 

215
00:12:56,870 --> 00:13:00,150
Looking forward to get my hands 
on the test system. 

216
00:13:00,810 --> 00:13:03,370
To see what will be shipped out 
with the new release. 

217
00:13:03,770 --> 00:13:06,650
But this is let's say one 
feature where currently the 

218
00:13:06,650 --> 00:13:11,210
customer landscape maybe got an 
SAP PLM, maybe an external. 

219
00:13:11,530 --> 00:13:15,410
But now with this feature of 
connecting external Plms, you 

220
00:13:15,410 --> 00:13:19,130
have the full flexibility and 
process integration from design 

221
00:13:19,290 --> 00:13:23,130
to manufacturing and later on of
call to shipping like supporting

222
00:13:23,130 --> 00:13:26,260
the complete process designed to
operate Google. 

223
00:13:26,260 --> 00:13:30,060
And I also learned that at a 
later phase you implemented SAP 

224
00:13:30,100 --> 00:13:32,980
digital manufacturing. 
What are the main processes or 

225
00:13:32,980 --> 00:13:36,340
capabilities that are used with 
our product and what is the best

226
00:13:36,340 --> 00:13:40,260
approach for fast and successful
implementation there for the 

227
00:13:40,420 --> 00:13:42,180
high performance battery 
industry? 

228
00:13:43,220 --> 00:13:45,500
Thanks that you mentioned the 
sub DM product. 

229
00:13:45,740 --> 00:13:48,820
One of our sweet spot is of 
course the combination of S for 

230
00:13:48,820 --> 00:13:53,500
HANA Public Cloud in combination
with SUB, DM and other apps like

231
00:13:53,580 --> 00:13:57,650
SAP SAC. 
Or QER because we define 

232
00:13:57,650 --> 00:14:01,730
ourselves as a boutique at scale
where we can help our customers 

233
00:14:01,730 --> 00:14:04,650
with our deep knowledge, 
especially of integration. 

234
00:14:04,650 --> 00:14:09,570
Top floor to shop floor and very
important since we made the 

235
00:14:09,570 --> 00:14:14,610
journey from the on Prem to the 
cloud world, the UI looks more 

236
00:14:14,610 --> 00:14:17,690
or less the same. 
We have Fiori overall within all

237
00:14:17,690 --> 00:14:22,130
the apps, so that means unique 
user experience for shop floor 

238
00:14:22,130 --> 00:14:24,610
worker is very important 
because. 

239
00:14:25,500 --> 00:14:29,540
Why do I need to log into five 
different system if I have one 

240
00:14:29,540 --> 00:14:32,300
job? 
We can't explain this to the 

241
00:14:32,300 --> 00:14:35,820
colleagues, so therefore it's 
important that maybe an app is 

242
00:14:35,940 --> 00:14:40,180
in As for to be executed another
app, for example is it the DM 

243
00:14:40,180 --> 00:14:44,460
sector executed and talking 
about especially for battery 

244
00:14:44,460 --> 00:14:46,820
cells. 
In the future, every battery 

245
00:14:46,820 --> 00:14:50,500
cell company in the world has to
follow the Battery Passport 

246
00:14:50,500 --> 00:14:53,860
which is a kind like ID from the
mine. 

247
00:14:54,590 --> 00:14:56,750
To the OEM and back to 
recycling. 

248
00:14:56,750 --> 00:14:59,750
So that means it's like your 
Facebook of the batteries, your 

249
00:14:59,750 --> 00:15:03,790
diary, everything, what will be 
assembled, raw material etc has 

250
00:15:03,790 --> 00:15:07,350
to go in and therefore it's very
important because the machine 

251
00:15:07,590 --> 00:15:12,150
who builds that products with 
the chemicals with the raw 

252
00:15:12,150 --> 00:15:15,270
materials, this will be a high 
speed production process. 

253
00:15:15,270 --> 00:15:18,110
So that means there will be no 
human being interacting, 

254
00:15:18,510 --> 00:15:21,630
everything will be serialized 
and all of those data will be 

255
00:15:21,630 --> 00:15:23,990
collected via the sub DM 
application. 

256
00:15:24,400 --> 00:15:28,600
Will be then forwarded of course
to the Asforhana cloud in order 

257
00:15:28,600 --> 00:15:33,240
to have the data for shipping 
etc start and maybe all the data

258
00:15:33,280 --> 00:15:36,680
goes to the Catina X or other 
battery apps. 

259
00:15:36,680 --> 00:15:40,160
What will be developed nowadays?
And therefore it's very 

260
00:15:40,160 --> 00:15:43,520
important to have the 
combination to support your 

261
00:15:43,520 --> 00:15:47,080
enterprise with the Asforhana 
public and of course to support 

262
00:15:47,080 --> 00:15:50,790
your shop floor. 
With the sub DN we set it nicely

263
00:15:50,790 --> 00:15:54,990
from top floor to shop floor and
let's move from there. 

264
00:15:54,990 --> 00:15:58,990
More on the subject of 
extensibility and how do you 

265
00:15:58,990 --> 00:16:01,190
handle extensibility in your 
projects? 

266
00:16:01,430 --> 00:16:05,230
Maybe not even only in your high
performance batteries projects, 

267
00:16:05,230 --> 00:16:07,950
but also in other Saps or high 
cloud public edition 

268
00:16:07,950 --> 00:16:11,870
implementations. 
Something what was a myth in the

269
00:16:11,870 --> 00:16:16,070
past and probably still in a lot
of brains, basically like 

270
00:16:16,070 --> 00:16:18,350
engraved. 
The myth is that. 

271
00:16:18,710 --> 00:16:21,830
As for HANA, Public Cloud only 
works for small companies. 

272
00:16:22,630 --> 00:16:24,750
It's not flexible enough for my 
needs. 

273
00:16:25,390 --> 00:16:28,830
We can't modify this. 
It's not that flexible and 

274
00:16:28,830 --> 00:16:33,470
modifiable as a classical As for
implementation or also known as 

275
00:16:33,510 --> 00:16:36,110
As for HANA Cloud Private 
Edition. 

276
00:16:36,910 --> 00:16:42,110
If we talk about this, I think 
my clear is absolutely different

277
00:16:42,310 --> 00:16:46,590
because since last year, 
especially when SAP released a 

278
00:16:46,590 --> 00:16:49,460
lot of new. 
And on our extension 

279
00:16:49,460 --> 00:16:52,620
possibilities, my view is clear.
If you wanna have a 

280
00:16:52,620 --> 00:16:56,820
state-of-the-art cloud European,
there is no way, why not put S 

281
00:16:56,820 --> 00:16:59,460
for HANA cloud for your future 
European system. 

282
00:17:00,380 --> 00:17:03,340
If we're looking to the 
innovations and the cycles what 

283
00:17:03,340 --> 00:17:07,500
SAP put in, I think this would 
be my horse where I put my money

284
00:17:07,500 --> 00:17:11,180
on. 
If we compare it to NFL. 

285
00:17:11,260 --> 00:17:15,380
We talked about sports earlier. 
Marcus, if we talk about S4, 

286
00:17:15,940 --> 00:17:19,010
this is Tom Brady. 
A very good quarterback, you 

287
00:17:19,010 --> 00:17:22,490
will probably win everything. 
But As for Hana Cloud is maybe 

288
00:17:22,490 --> 00:17:26,210
pet Mahomes. 
So that means yes, he won the 

289
00:17:26,210 --> 00:17:29,090
Super Bowl, maybe you throw some
interceptions. 

290
00:17:29,090 --> 00:17:32,450
What means not everything is 
perfect at the beginning, but 

291
00:17:32,450 --> 00:17:36,730
every year when we grow, the 
product will be better and 

292
00:17:36,730 --> 00:17:41,370
therefore you need sometimes 
some creativity to use some 

293
00:17:41,370 --> 00:17:42,770
fields. 
What are existing? 

294
00:17:43,210 --> 00:17:46,890
One example is for example if we
talk about logistics. 

295
00:17:47,220 --> 00:17:50,540
And we have a fixed handling 
unit because we have engraved 

296
00:17:50,540 --> 00:17:54,460
number on our handling units. 
Problem in the standard is you 

297
00:17:54,460 --> 00:17:57,180
create a handling unit and the 
system will automatically create

298
00:17:57,300 --> 00:18:00,260
a dynamic handling unit number 
for us all for the client. 

299
00:18:00,780 --> 00:18:03,340
How did we help? 
We basically created a handling 

300
00:18:03,340 --> 00:18:07,500
unit with the random number what
was created and we created a 

301
00:18:08,220 --> 00:18:10,260
plant maintenance equipment 
number. 

302
00:18:10,460 --> 00:18:12,820
And this plant maintenance 
equipment number will be fixed 

303
00:18:12,820 --> 00:18:16,510
every time and then we map the. 
The handling unit and the 

304
00:18:16,510 --> 00:18:19,790
equipment number together that 
we have the fixed number, what 

305
00:18:19,790 --> 00:18:23,070
is engraved at the handling unit
physically and we have the 

306
00:18:23,070 --> 00:18:26,630
variable number, what was 
generated by the system so we 

307
00:18:26,630 --> 00:18:29,910
could use all the standard apps.
We have a lookup table for the 

308
00:18:29,910 --> 00:18:32,910
real engraved number and 
everyone was happy. 

309
00:18:33,470 --> 00:18:36,310
So that means customer was 
happy, we were happy at this 

310
00:18:36,310 --> 00:18:39,710
workaround, cost us a couple 
days of work and let's say brain

311
00:18:39,710 --> 00:18:43,590
knowledge and basically it 
solved exactly customer needs. 

312
00:18:44,480 --> 00:18:47,840
Nevertheless, we also find out 
that some of those apps are 

313
00:18:47,840 --> 00:18:52,080
maybe not just specific for one 
customer, where we put in some 

314
00:18:52,080 --> 00:18:56,280
syntax IP in order to help 
customers to be better, faster, 

315
00:18:56,280 --> 00:18:58,760
etc. 
And I would like to point out 

316
00:18:58,760 --> 00:19:02,880
three apps, what we have created
in the past and what will be 

317
00:19:03,120 --> 00:19:07,320
enhanced every quarter basically
with new features and functions.

318
00:19:07,560 --> 00:19:10,000
The first one we call it 
internally Logismal. 

319
00:19:10,240 --> 00:19:14,040
This is a BTP app what makes 
every logistics workers. 

320
00:19:14,310 --> 00:19:17,710
State tasks easier. 
We have created a very intuitive

321
00:19:17,710 --> 00:19:21,150
mobile screen optimized for 
mobile barcode scanners. 

322
00:19:21,590 --> 00:19:25,310
We use the Fiori but our big 
buttons are basically triple 

323
00:19:25,310 --> 00:19:28,310
size of the normal Fiori buttons
you know from the Uis. 

324
00:19:28,830 --> 00:19:33,910
This also helps support by using
those device basically driving 

325
00:19:33,910 --> 00:19:37,190
on a forklift and of course 
wearing a glove where you maybe 

326
00:19:37,190 --> 00:19:40,790
need bigger buttons because you 
don't hit the detail button. 

327
00:19:40,870 --> 00:19:43,560
Perfect. 
The second app is that we have 

328
00:19:43,560 --> 00:19:47,040
also some customers. 
They basically after the end of 

329
00:19:47,040 --> 00:19:51,440
the manufacturing run they need 
to confirm the yield and scrap 

330
00:19:51,720 --> 00:19:55,120
within the sub DM application. 
They also need to do the 

331
00:19:55,120 --> 00:19:58,600
logistics booking and probably 
also have a quality inspection 

332
00:19:58,600 --> 00:20:01,680
by end of the day. 
So that means the reality would 

333
00:20:01,680 --> 00:20:06,800
be that you have 4 apps, DM S 
for HANA, EWM and maybe a 

334
00:20:06,800 --> 00:20:09,610
quality app. 
What we have done with this 

335
00:20:09,610 --> 00:20:12,210
small app is that we create a 
small app. 

336
00:20:12,370 --> 00:20:16,050
You scan this physical handy 
unit with a bar code in our case

337
00:20:16,050 --> 00:20:18,810
for scanning. 
Then you have a single button of

338
00:20:18,810 --> 00:20:22,050
confirming the good parts. 
If you want to confirm basically

339
00:20:22,050 --> 00:20:26,130
a quality, you need to basically
check the radio button from 

340
00:20:26,250 --> 00:20:29,250
value one to value 2 and also 
press this button. 

341
00:20:29,490 --> 00:20:32,010
So that means it's very 
intuitive also for high speed 

342
00:20:32,010 --> 00:20:36,270
manufacturing in order to do all
the material bookings within the

343
00:20:36,270 --> 00:20:38,710
system with basically one scan 
and one click. 

344
00:20:39,070 --> 00:20:42,270
The last point is basically 
integration As for on a public 

345
00:20:42,310 --> 00:20:44,310
cloud within the Microsoft 
ecosystem. 

346
00:20:44,790 --> 00:20:47,830
With this I want to talk about 
for example integration of 

347
00:20:47,830 --> 00:20:51,750
workflows, approval of 
transports, approval of budget 

348
00:20:51,750 --> 00:20:56,030
etc, whatever you have as a 
workflow defined, even we can do

349
00:20:56,030 --> 00:20:58,830
the side by side. 
So that means you can create a 

350
00:20:58,830 --> 00:21:04,160
record in System A and can 
confirm or approve or deny this 

351
00:21:04,160 --> 00:21:06,440
in the software B and then vice 
versa. 

352
00:21:06,960 --> 00:21:11,120
And with those, let's say 
acceleration package, we combine

353
00:21:11,120 --> 00:21:16,480
basically SAP products like sub 
DM like S for HANA Public Cloud 

354
00:21:16,600 --> 00:21:20,240
with Teams, Outlook or other 
products of the Microsoft Suite.

355
00:21:21,840 --> 00:21:25,840
Very good, very impressive. 
You as SAP partner if you had a 

356
00:21:25,840 --> 00:21:28,960
wish from SAP or in your 
opinion, where should SAP invest

357
00:21:28,960 --> 00:21:31,880
a lot of its money in SAP S for 
HANA Cloud Public Edition? 

358
00:21:32,170 --> 00:21:35,650
What is your point of view? 
I have two wishes, 1 wishes for 

359
00:21:35,650 --> 00:21:38,810
all of our customer who listen 
to podcast and one wish of 

360
00:21:38,810 --> 00:21:41,730
course for SAP. 
So my wish for all the customers

361
00:21:41,730 --> 00:21:45,610
is take that risk to move your 
existing European, whatever it 

362
00:21:45,610 --> 00:21:51,170
is an SAP European or non SAP 
European and take the risk to 

363
00:21:51,170 --> 00:21:54,890
move to S 400 public cloud. 
As I said, this is for me 

364
00:21:54,890 --> 00:21:58,600
absolutely strategic cause where
I would put my money on and then

365
00:21:58,600 --> 00:22:02,720
work very closely with SAP and 
syntax together to close those 

366
00:22:02,720 --> 00:22:06,680
gaps or identify those gaps. 
So we have a lot of projects. 

367
00:22:06,680 --> 00:22:09,840
We have a very close 
relationship where we work with 

368
00:22:09,840 --> 00:22:14,320
the sub development together to 
understand what are the gaps. 

369
00:22:14,320 --> 00:22:18,480
Are those gaps on the roadmap, 
Can we wait one or two releases 

370
00:22:18,560 --> 00:22:22,040
or can we bring this release 
onto the sub roadmap. 

371
00:22:22,680 --> 00:22:25,400
This is very important because 
our lessons learned was 

372
00:22:25,440 --> 00:22:30,090
absolutely that SAP is open to 
discuss very creatively with the

373
00:22:30,090 --> 00:22:34,610
customer to find also solutions 
for those gaps and then also 

374
00:22:34,610 --> 00:22:36,410
solve it within the project 
lifetime. 

375
00:22:37,570 --> 00:22:41,690
My second wish for SAP where I 
hope that SAP invests a lot of 

376
00:22:41,690 --> 00:22:45,210
money. 
As you asked before Marcus, I 

377
00:22:45,210 --> 00:22:47,610
would like to have complexity 
reduction. 

378
00:22:48,130 --> 00:22:50,970
I don't want to talk about 
products or integration 

379
00:22:50,970 --> 00:22:54,060
scenarios. 
Basically if we talk about 

380
00:22:54,220 --> 00:22:58,780
scheduling, just scheduling of 
orders, of parts of Labor of 

381
00:22:58,780 --> 00:23:02,700
whatever, There are currently a 
lot of products in the market, 

382
00:23:03,180 --> 00:23:07,300
sub or non sub and currently 
some of those products have also

383
00:23:07,300 --> 00:23:10,660
overlap or also a feature 
restriction. 

384
00:23:11,420 --> 00:23:16,580
My wish for the future is that 
we simplify or SAP simplify this

385
00:23:16,900 --> 00:23:20,020
to make it easier for the 
customer to jump on and of 

386
00:23:20,020 --> 00:23:22,940
course for SAP to save 
development resources. 

387
00:23:24,100 --> 00:23:26,660
Thanks for your feedback. 
Most of the high performance 

388
00:23:26,660 --> 00:23:30,940
batteries companies are new to 
SAP as their startups. 

389
00:23:31,020 --> 00:23:34,580
And how is your feedback from 
your customers on user 

390
00:23:34,580 --> 00:23:36,780
experience? 
Do they like to work in SAPS? 

391
00:23:36,780 --> 00:23:37,980
Partner. 
Cloud public edition. 

392
00:23:38,460 --> 00:23:42,820
If we talk about let's say new 
customers, I mean the persons 

393
00:23:42,820 --> 00:23:47,460
are not new, even if it's a 
startup, they not just hiring 

394
00:23:47,940 --> 00:23:50,700
young colleagues from the 
university with no experience, 

395
00:23:51,420 --> 00:23:53,900
the people have also some 
experience from their previous 

396
00:23:53,900 --> 00:23:57,140
job, maybe with or without SAP 
as an ERP system. 

397
00:23:58,260 --> 00:24:02,860
I think the way of getting 
trained into the S 400 public 

398
00:24:02,860 --> 00:24:06,660
cloud, especially since last 
August when SAP released the 

399
00:24:06,660 --> 00:24:12,380
Horizon theme, the way of how to
work within the apps and the 

400
00:24:12,380 --> 00:24:16,130
information comes to you is 
absolutely different than if you

401
00:24:16,130 --> 00:24:19,730
worked in the past with the ECC 
and you know every T code 

402
00:24:19,730 --> 00:24:21,970
basically out-of-the-box and you
typed it in. 

403
00:24:22,570 --> 00:24:28,290
So therefore the people demand 
this new UI and from my point of

404
00:24:28,290 --> 00:24:34,330
view SAP especially with the UI 
have to be as easy as an Apple 

405
00:24:34,330 --> 00:24:37,090
iPhone. 
That means there should not be a

406
00:24:37,090 --> 00:24:40,650
manual available because 
everyone knows intuitive how to 

407
00:24:40,650 --> 00:24:43,450
work with it. 
By the way, Marcus, have you 

408
00:24:43,450 --> 00:24:46,690
ever found out if Apple has a 
manual for their phones? 

409
00:24:49,250 --> 00:24:51,810
It's a good question. 
I've never used one because it's

410
00:24:51,810 --> 00:24:56,090
that easy and that's also 
important for moving forward. 

411
00:24:56,410 --> 00:25:00,010
It has to be easy. 
No manuals, No 10 clicks that 

412
00:25:00,010 --> 00:25:01,970
everyone can use it. 
Very good. 

413
00:25:02,770 --> 00:25:05,850
Let's keep this in mind before 
we come to the end. 

414
00:25:05,930 --> 00:25:08,690
One last question. 
If you had one wish, what would 

415
00:25:08,690 --> 00:25:10,330
it be? 
Thank you, Marcus. 

416
00:25:10,650 --> 00:25:14,690
From my side, no open questions.
I basically throw it out a 

417
00:25:14,690 --> 00:25:19,080
second ago with my manual idea. 
I think all the investments what

418
00:25:19,080 --> 00:25:24,040
we saw at the Sapphire also with
the new AI integration, I think 

419
00:25:24,160 --> 00:25:27,400
my last wish would be that if we
can combine this new AI 

420
00:25:27,400 --> 00:25:34,640
technology and the SSAP 
technology to do like ASAP, Can 

421
00:25:34,640 --> 00:25:37,560
you show me where I lose money? 
What is the highest demanding 

422
00:25:37,560 --> 00:25:42,160
cost center as one idea and the 
system shows you exactly, well, 

423
00:25:42,580 --> 00:25:45,060
Romans Presale cost Center is 
the highest cost center in the 

424
00:25:45,060 --> 00:25:47,380
company. 
You need to look at labor, Just 

425
00:25:47,380 --> 00:25:50,140
one example. 
Another idea is can you please 

426
00:25:50,140 --> 00:25:54,180
create a report for me with the 
sales figures of the last 

427
00:25:54,180 --> 00:25:57,980
quarter and I would like to 
point out the top 10 customers 

428
00:25:58,660 --> 00:26:01,660
and the system automatically 
builds through that report and 

429
00:26:01,660 --> 00:26:05,300
you just have to say safe. 
Sounds very good. 

430
00:26:05,620 --> 00:26:07,620
I like your creativity. 
I like your ideas. 

431
00:26:09,100 --> 00:26:11,460
I really enjoyed this podcast 
with you. 

432
00:26:12,750 --> 00:26:15,910
Thank you so much Roman again 
for your great insights today. 

433
00:26:16,430 --> 00:26:18,150
Marcus, thanks also from my 
side. 

434
00:26:18,430 --> 00:26:22,550
It was great to talk to you 
about battery S for HANA. 

435
00:26:22,630 --> 00:26:25,310
So text and SAP. 
Thanks Roman, and as always, 

436
00:26:25,550 --> 00:26:30,870
feel free to drop us an e-mail 
via inside S4 at sap.com and let

437
00:26:30,870 --> 00:26:33,590
us know which topics are of your
interest. 

438
00:26:33,590 --> 00:26:36,630
In next time and be inside SAP S
for Han.

