1
00:00:09,920 --> 00:00:13,520
Welcome to our podcast. 
There is no Customer success 

2
00:00:13,520 --> 00:00:16,239
without Product Success and 
Project Success. 

3
00:00:16,920 --> 00:00:20,040
I'm Yanik Pederschmidt from 
Cloud ERP Product Success 

4
00:00:20,040 --> 00:00:23,200
Enablement and I'm happy to 
announce that we're now the 

5
00:00:23,200 --> 00:00:28,000
podcast inside SAPS Fohana 
Cloud. 

6
00:00:28,680 --> 00:00:32,320
It's a small but important 
change on our name and branding 

7
00:00:32,759 --> 00:00:36,040
to keep the same focus on the 
same strategy, sharing projects,

8
00:00:36,040 --> 00:00:39,520
best practices, lessons learned 
and certainly successful goal 

9
00:00:39,520 --> 00:00:43,480
out with a CMP Esfahana Cloud. 
We continue to share. 

10
00:00:43,480 --> 00:00:46,440
Perspective from customers, 
partners and of course, 

11
00:00:46,440 --> 00:00:50,000
colleagues too in today's. 
Episode we will put the. 

12
00:00:50,000 --> 00:00:54,480
Spotlight on a very special 
topic that is relevant for many,

13
00:00:54,480 --> 00:01:00,840
many ACP customers, which is the
transition of the ERP system SAP

14
00:01:00,840 --> 00:01:04,680
by design to SAPS Farhana Cloud 
public. 

15
00:01:04,680 --> 00:01:07,400
Edition. 
Joining me today are Russell de 

16
00:01:07,400 --> 00:01:11,560
Lamp, Executive VP at Navigator 
Business Solution, a customer 

17
00:01:11,560 --> 00:01:15,880
and partner from the United 
States, Dirk DeVos, the MD of 

18
00:01:15,880 --> 00:01:20,760
Felina, our German based 
customer and Rafael Fink, the 

19
00:01:20,760 --> 00:01:25,120
CEO of SNAP, SAP Implementation 
Partner of Felina. 

20
00:01:25,760 --> 00:01:28,400
To kick things off, I'd ask I 
guess to introduce themselves. 

21
00:01:29,040 --> 00:01:32,000
We start with you, Russell 
joining us remotely from the US.

22
00:01:32,520 --> 00:01:35,880
Yeah, rest of the lap I I run 
our services and support team 

23
00:01:35,880 --> 00:01:40,600
here and Navigator we've been 
SAP partner for 15 years. 

24
00:01:40,600 --> 00:01:44,080
We started with B1 and primarily
have been working with by design

25
00:01:44,240 --> 00:01:48,000
for the last decade or so. 
And then recently, the last two 

26
00:01:48,000 --> 00:01:52,880
years we started our S4 practice
and that journey has been a lot 

27
00:01:52,880 --> 00:01:54,920
of fun. 
It's the fastest growing segment

28
00:01:54,920 --> 00:01:57,200
of our organization and like I 
said, happy to be here. 

29
00:01:57,600 --> 00:01:59,840
Thanks for being with us. 
Let's move into the second 

30
00:01:59,840 --> 00:02:02,320
customer, Dirk, from our 
customer, Felina. 

31
00:02:02,640 --> 00:02:04,600
Can you go and say a few words 
about the customer, about 

32
00:02:04,600 --> 00:02:08,320
yourself, of course. 
Well, so thanks for having me. 

33
00:02:08,320 --> 00:02:09,639
Let's talk a little bit about 
Felina. 

34
00:02:09,639 --> 00:02:13,560
Felina is a German company. 
Actually next year we will be 

35
00:02:13,560 --> 00:02:16,400
celebrating our 140th 
anniversary. 

36
00:02:16,400 --> 00:02:21,640
So we've been around since 1885.
We are a manufacturer and 

37
00:02:21,640 --> 00:02:26,000
distributor of premium lingerie,
premium of women's, women's 

38
00:02:26,000 --> 00:02:29,440
lingerie. 
We are based not too far from 

39
00:02:29,440 --> 00:02:32,920
here in, in Mannheim and we've 
been that throughout our entire 

40
00:02:32,920 --> 00:02:36,880
history. 
And a couple of years ago, we 

41
00:02:36,880 --> 00:02:40,240
came to the conclusion that our 
ERP system was no longer serving

42
00:02:40,240 --> 00:02:44,400
its purposes. 
And that is when we did a survey

43
00:02:44,400 --> 00:02:47,840
of the market and decided to go 
with SAP. 

44
00:02:48,880 --> 00:02:49,960
Great. 
Thanks for being with us. 

45
00:02:50,160 --> 00:02:53,040
And every good project and 
successful customers has a great

46
00:02:53,040 --> 00:02:55,360
partner. 
So we have Rafael Fink with us, 

47
00:02:55,400 --> 00:02:57,360
the CEO of Snap. 
Thanks for being with us. 

48
00:02:57,880 --> 00:03:00,360
Welcome. 
So yes, before creating Snap 

49
00:03:00,400 --> 00:03:03,400
eight years ago, I was myself on
the customer side, implementing 

50
00:03:03,400 --> 00:03:08,000
SAP product for almost 20 years.
In fact, we created Snap with my

51
00:03:08,000 --> 00:03:10,080
wife here in Slovakia. 
It's a family business. 

52
00:03:10,440 --> 00:03:13,440
We started the very small 
focusing on by design, 

53
00:03:13,440 --> 00:03:17,960
exclusively and only SAP public 
cloud solution and two years ago

54
00:03:17,960 --> 00:03:21,840
we started the transaction 
transition to S4 public, of 

55
00:03:21,840 --> 00:03:23,760
course with our first customer 
similar. 

56
00:03:24,120 --> 00:03:25,200
OK, thanks. 
Good. 

57
00:03:25,600 --> 00:03:27,120
Let's not dig into the topic of 
the day. 

58
00:03:27,200 --> 00:03:31,200
I'm very excited about your your
answers and I'm first looking at

59
00:03:31,200 --> 00:03:34,720
you dear representing Felina. 
I think our audience is very 

60
00:03:34,720 --> 00:03:37,600
curious to understand you know 
what really motivated you to 

61
00:03:37,600 --> 00:03:42,240
move from one you know well 
running ERP system, cloud ERP 

62
00:03:42,320 --> 00:03:45,320
system to SAPS 4 HANA Cloud 
public edition. 

63
00:03:45,320 --> 00:03:47,920
Can you give a bit? 
You know the the why and what 

64
00:03:47,920 --> 00:03:52,040
behind all that? 
So like I said, we at some 

65
00:03:52,040 --> 00:03:56,080
points we made a choice to go 
with SAP and at the time we 

66
00:03:56,080 --> 00:03:59,320
chose to start with the BYD 
version of the cloud version of 

67
00:03:59,560 --> 00:04:04,560
your ERP system. 
And even though Felina is AI 

68
00:04:04,560 --> 00:04:06,800
would say an SME, it's a small 
medium enterprise. 

69
00:04:06,880 --> 00:04:13,920
We are about 50 people, but it's
a relatively complex business 

70
00:04:14,280 --> 00:04:18,040
even for even for the size. 
You have to know that we run 

71
00:04:18,040 --> 00:04:23,120
about 14,000 SKU, so 14,000 
different products that we 

72
00:04:23,120 --> 00:04:26,920
distribute globally to about 
4000 customers. 

73
00:04:27,560 --> 00:04:32,400
And also our product offering 
because we are essentially a 

74
00:04:32,400 --> 00:04:35,440
fashion business, you know it's 
with the summer and the winter 

75
00:04:35,440 --> 00:04:40,840
season, our offer to our 
customers changes every six 

76
00:04:40,840 --> 00:04:44,280
months to about 30%. 
And so there's a there's a lot 

77
00:04:44,280 --> 00:04:48,160
of innovation, there's a lot of 
change in in in our business and

78
00:04:48,160 --> 00:04:52,760
relatively big complexity even 
if the numbers as such are not 

79
00:04:52,840 --> 00:04:56,600
are not that that big you know 
or not that that that important.

80
00:04:57,400 --> 00:05:02,360
So even the for a small business
we need a powerful ERP system. 

81
00:05:03,200 --> 00:05:07,760
The step from our old ERP system
into BY you know helped us a lot

82
00:05:07,760 --> 00:05:10,440
in even understanding our own 
business because we hadn't done 

83
00:05:10,440 --> 00:05:14,600
the real in depth analysis of 
our business and our processes 

84
00:05:14,600 --> 00:05:18,120
because you know things had been
running quite well for for 15 

85
00:05:18,120 --> 00:05:22,760
years until they didn't anymore.
So moving into BYD gave us an 

86
00:05:22,760 --> 00:05:25,600
opportunity to really analyse 
our business and to much better 

87
00:05:25,600 --> 00:05:28,240
understand you know where the 
difficulties are. 

88
00:05:29,040 --> 00:05:32,880
But it also had a as a 
consequence that relatively soon

89
00:05:32,880 --> 00:05:36,400
we found out that BYD was 
actually not powerful enough. 

90
00:05:36,480 --> 00:05:40,200
And you know, we wanted to make 
that step up into S4. 

91
00:05:40,720 --> 00:05:45,160
The fact that we didn't use BYD 
for that long was a bit of 

92
00:05:45,160 --> 00:05:47,760
inhibiting factor I would say to
adopt A new system. 

93
00:05:47,760 --> 00:05:50,120
But thanks to the Lighthouse 
project that was, you know, 

94
00:05:50,120 --> 00:05:53,400
offered to us by SAP that 
enabled us to make that step 

95
00:05:53,400 --> 00:05:59,000
from BYD into you know S4 clouds
or SA PS4 cloud a lot faster. 

96
00:05:59,000 --> 00:06:01,120
So that really, really helped 
us. 

97
00:06:01,680 --> 00:06:05,720
And then the other thing is for 
that second transition from BY 

98
00:06:05,840 --> 00:06:10,120
into S4, our partner Snap came 
on board. 

99
00:06:10,120 --> 00:06:13,560
We had some experience with them
from work that we had done 

100
00:06:13,560 --> 00:06:15,720
before in our production units 
in Hungary. 

101
00:06:16,320 --> 00:06:20,400
And I can't underline enough how
important a good partner is in 

102
00:06:20,400 --> 00:06:24,240
implementing, you know, a new 
ERP system like this, because 

103
00:06:24,520 --> 00:06:28,120
we've had both experiences, you 
know where it was a a more 

104
00:06:28,120 --> 00:06:30,440
difficult trajectory I would 
say. 

105
00:06:30,440 --> 00:06:33,880
And then we learned with with 
Snap that it can also be very 

106
00:06:33,880 --> 00:06:36,080
smooth and swift. 
This is great to hear. 

107
00:06:36,240 --> 00:06:38,320
So a few things you mentioned 
that are very interesting. 

108
00:06:38,320 --> 00:06:40,400
I think first of all is about 
the business process 

109
00:06:40,400 --> 00:06:43,720
transformation and build the 
business processes on the cloud,

110
00:06:43,760 --> 00:06:45,800
ERP. 
The second thing you mentioned 

111
00:06:45,800 --> 00:06:50,160
is you've reached the technical 
limit of a system that kind of 

112
00:06:50,160 --> 00:06:54,120
forces you out to the next one, 
which is thankfully the next 

113
00:06:54,120 --> 00:06:57,120
Gen. cloud ERP from ASAP. 
And you mentioned then the 

114
00:06:57,120 --> 00:07:00,480
Lighthouse program and I think 
the two projects that you guys 

115
00:07:00,480 --> 00:07:03,800
represent today were under the 
so-called Lighthouse program. 

116
00:07:04,080 --> 00:07:05,800
Could you please shed some light
a little bit? 

117
00:07:06,400 --> 00:07:09,040
When we moved into BYD that that
was not under Lighthouse, but 

118
00:07:09,280 --> 00:07:13,120
then but then the transition 
from BYD to S4 went under the 

119
00:07:13,520 --> 00:07:17,280
the the Lighthouse program. 
And for us, I think also for 

120
00:07:17,280 --> 00:07:21,720
SNAP having access to all the 
the expertise and the 

121
00:07:21,720 --> 00:07:27,200
consultants of SAP itself and 
you know the the S4 cloud 

122
00:07:27,760 --> 00:07:31,880
package still being relatively 
young and we encountered some 

123
00:07:31,880 --> 00:07:35,920
issues and some problems that 
were First off and that probably

124
00:07:35,920 --> 00:07:39,560
would have taken us a very long 
time to develop or or find 

125
00:07:39,560 --> 00:07:43,520
solutions on our own and having 
access to the, you know, 

126
00:07:43,520 --> 00:07:47,600
directly to the SAP people. 
That helped us tremendously. 

127
00:07:48,240 --> 00:07:52,040
We have a weekly steering 
committee where somebody from 

128
00:07:52,120 --> 00:07:55,320
SAP participates, you know, 
together with our partners and 

129
00:07:55,320 --> 00:07:58,760
our internal project management,
and that made all the 

130
00:07:58,760 --> 00:08:00,960
difference. 
Let's not talk about the 

131
00:08:00,960 --> 00:08:04,760
solution, but you both are using
both customer and I'd like to 

132
00:08:04,760 --> 00:08:08,920
maybe ask you or Rafael first as
as Felina's partner, you were 

133
00:08:08,920 --> 00:08:11,680
certainly involved in the 
decision you know to move from 

134
00:08:11,680 --> 00:08:15,520
cloud ERPA to cloud ERPB, lots 
of functionality from the one 

135
00:08:15,520 --> 00:08:18,280
inside, lot of functionalities 
on the other hand side more 

136
00:08:18,280 --> 00:08:21,640
powerful capabilities. 
But how did you at the end make 

137
00:08:21,640 --> 00:08:25,880
the decision that this is the 
right cloud ERP for your 

138
00:08:25,880 --> 00:08:28,040
customer, but the? 
First thing which was 

139
00:08:28,040 --> 00:08:30,800
challenging is to go through the
journey with a customer about 

140
00:08:30,800 --> 00:08:33,360
how to identify that by design 
was not anymore the right 

141
00:08:33,360 --> 00:08:37,200
solution because it was already 
a big investment made in in this

142
00:08:37,200 --> 00:08:39,120
tool. 
In fact, we did something that 

143
00:08:39,120 --> 00:08:42,080
was forgotten in the previous 
implementation is to make the 

144
00:08:42,080 --> 00:08:44,640
sizing exercise and that's what 
helped you. 

145
00:08:45,200 --> 00:08:47,800
You mentioned and very quickly 
realised that this tool was not 

146
00:08:47,800 --> 00:08:51,520
able to support your growth and 
also the volume of data that was

147
00:08:51,520 --> 00:08:53,800
needed to be in the transaction 
on a daily basis. 

148
00:08:54,040 --> 00:08:57,920
Then we went with SAP and Fenina
and DIA was involved was a 

149
00:08:57,920 --> 00:09:00,800
digital discovery analyse we we 
wanted. 

150
00:09:00,840 --> 00:09:03,800
I wanted to convince the Fenina 
to stay in the Recip family. 

151
00:09:04,200 --> 00:09:07,320
It was not so difficult because 
Fenina wanted to stay in the 

152
00:09:07,320 --> 00:09:10,240
Recip family. 
We said look, that didn't work, 

153
00:09:10,680 --> 00:09:13,800
what is the best tool for us? 
And we came to the conclusion 

154
00:09:13,800 --> 00:09:16,720
list for public cloud. 
So Digital Discovery Analyse is 

155
00:09:16,720 --> 00:09:20,120
really a tool that didn't exist 
before and that's really helped 

156
00:09:20,120 --> 00:09:23,200
a lot to convince the customer 
to give them, to help them to 

157
00:09:23,200 --> 00:09:26,120
scope the project and to 
understand what they will get 

158
00:09:26,120 --> 00:09:28,520
and what they will not get. 
Rafael said that we absolutely 

159
00:09:28,520 --> 00:09:30,520
wanted to stay within the SAP 
family. 

160
00:09:30,520 --> 00:09:33,400
That is not entirely true in the
sense we had really an open 

161
00:09:33,400 --> 00:09:37,640
approach to the market that we 
also considered other suppliers 

162
00:09:37,640 --> 00:09:40,560
if you want. 
But in the end, after the DDA, 

163
00:09:41,000 --> 00:09:44,480
we came to the conclusion that 
probably the best fit for our 

164
00:09:44,480 --> 00:09:47,000
needs and coming out of BOID 
would have been SAP. 

165
00:09:47,160 --> 00:09:48,000
OK, OK. 
That's. 

166
00:09:48,000 --> 00:09:51,520
It's not like we blindly just 
went again into SAP. 

167
00:09:51,520 --> 00:09:54,880
We we really did our homework 
and came to the conclusion that 

168
00:09:54,920 --> 00:09:56,800
SAP would be the best solution. 
For us. 

169
00:09:56,840 --> 00:09:58,840
OK. 
So there it was not just the not

170
00:09:58,840 --> 00:10:01,800
the natural extension, but there
was a real assessment where you 

171
00:10:01,800 --> 00:10:04,120
could as a good. 
As a good housekeeper, we did 

172
00:10:04,120 --> 00:10:05,920
our homework. 
I think that's the that's the 

173
00:10:06,120 --> 00:10:08,720
job that has to be done. 
It seems not too hard for us, 

174
00:10:08,760 --> 00:10:10,640
was not necessarily not for the 
customer. 

175
00:10:11,240 --> 00:10:13,560
OK, good. 
Russell, now I'm looking at you 

176
00:10:13,560 --> 00:10:16,360
and and you have a special role 
here because you both customers 

177
00:10:16,360 --> 00:10:20,080
and partners which makes that 
even more interesting that's 

178
00:10:20,080 --> 00:10:22,320
safe because you have the the 
the two perspective in the in 

179
00:10:22,320 --> 00:10:24,720
the same house. 
First of all the the same 

180
00:10:24,720 --> 00:10:29,600
questions that we just asked 
here is how did you came to the 

181
00:10:29,600 --> 00:10:33,200
conclusion that Acps for HANA 
Public Cloud is the right 

182
00:10:33,200 --> 00:10:36,560
solution for yourself for NBS as
a company? 

183
00:10:37,600 --> 00:10:39,120
Yeah. 
It's an interesting question 

184
00:10:39,120 --> 00:10:42,000
because we've been running by 
design for over 10 years. 

185
00:10:42,520 --> 00:10:46,280
So it was just kind of time for 
an optimization and we wanted to

186
00:10:46,760 --> 00:10:50,160
explore our options and and look
at either optimizing by design 

187
00:10:50,160 --> 00:10:53,040
for the future of what we're 
looking for or transition over 

188
00:10:53,040 --> 00:10:55,280
to something like S4 Public 
Edition. 

189
00:10:55,720 --> 00:10:58,240
And then we ended up moving over
to to S4 for a variety of 

190
00:10:58,240 --> 00:11:00,720
reasons. 
Number one, it's the fastest 

191
00:11:00,920 --> 00:11:02,640
growing business segment at 
Navigator. 

192
00:11:02,640 --> 00:11:06,520
So we wanted more expertise in 
house and there's a lot more 

193
00:11:06,520 --> 00:11:12,200
depth and the financial services
area for S4 than in by design. 

194
00:11:12,320 --> 00:11:15,120
And ultimately it's just more 
resilient with additions of 

195
00:11:15,120 --> 00:11:19,640
things like the BTP which allow 
us to innovate within the BTP 

196
00:11:19,640 --> 00:11:22,440
and actually take that 
innovation and deploy it to our 

197
00:11:22,440 --> 00:11:25,160
customers as well as other 
partners through the SAP store. 

198
00:11:25,280 --> 00:11:27,920
And other things like you know 
obviously working with SAP in 

199
00:11:27,920 --> 00:11:31,160
the Lighthouse program was was a
really neat opportunity for us 

200
00:11:31,160 --> 00:11:33,720
to both kind of be that partner 
and customer. 

201
00:11:33,720 --> 00:11:35,800
So we're we're really getting a 
lot of benefit both from our 

202
00:11:35,800 --> 00:11:38,760
internal operations working with
SAP, but as well as our 

203
00:11:38,760 --> 00:11:41,760
implementation team being able 
to refine their tools and our 

204
00:11:41,760 --> 00:11:44,840
methodology and then how we 
actually go to market with S4. 

205
00:11:45,000 --> 00:11:48,000
The last big factor that ended 
up because it is an investment 

206
00:11:48,000 --> 00:11:51,360
to do that transition versus 
optimization is a lot of the 

207
00:11:51,360 --> 00:11:53,640
predictive elements within that 
are shipped kind of 

208
00:11:53,640 --> 00:11:55,640
out-of-the-box. 
So a lot more innovation around 

209
00:11:55,640 --> 00:11:58,720
machine learning, artificial 
intelligence and again being 

210
00:11:58,720 --> 00:12:00,480
able to leverage that with the 
BTPS. 

211
00:12:00,560 --> 00:12:04,520
OK, thanks for this answer. 
Now I want to dig a bit more 

212
00:12:04,920 --> 00:12:08,280
into the details of the, So 
let's call that the migration 

213
00:12:08,280 --> 00:12:11,600
strategy because I mean you you 
said it already a lot of data, 

214
00:12:11,600 --> 00:12:17,640
too many data, too many too much
information and and and and I 

215
00:12:17,640 --> 00:12:20,920
think you need to be very brave 
if you have from the ambition to

216
00:12:20,920 --> 00:12:24,960
move from one well running ERP 
system to the other because of 

217
00:12:24,960 --> 00:12:27,200
the data. 
It's not only about the software

218
00:12:27,200 --> 00:12:30,440
itself, but it's about the data 
and making sure that you keep 

219
00:12:30,760 --> 00:12:34,600
the data that you need for the 
future, for future decision for 

220
00:12:34,600 --> 00:12:37,360
example. 
So how did you, how did you 

221
00:12:37,360 --> 00:12:40,320
approach that and maybe Russell,
you want to enhance on that one?

222
00:12:42,280 --> 00:12:44,320
Yeah. 
Again, it's, it's kind of a 

223
00:12:44,320 --> 00:12:47,280
funny story because Navigator, 
we're actually innovating in 

224
00:12:47,280 --> 00:12:50,160
this cycle as well. 
That was one of our areas that 

225
00:12:50,160 --> 00:12:53,120
we're investing in is this 
transition from by design to S4.

226
00:12:53,600 --> 00:12:56,200
But then when I started talking 
with some of the folks at SAP 

227
00:12:56,320 --> 00:12:59,040
and begun our journey, actually 
implement implementing that. 

228
00:12:59,360 --> 00:13:03,000
SAP has provided what we call 
integration flows or I flows in 

229
00:13:03,000 --> 00:13:06,680
the ETP where you can basically 
just extract data from by 

230
00:13:06,680 --> 00:13:09,600
design, put it through this I 
flow and it kicks out a 

231
00:13:10,080 --> 00:13:14,320
translated file for S4. 
So migrating most of our master 

232
00:13:14,320 --> 00:13:17,160
data objects where it was very 
easy, the only things that we 

233
00:13:17,160 --> 00:13:19,640
had to look at were basically 
the custom fields. 

234
00:13:19,640 --> 00:13:23,760
So that dramatically increased 
our implementation time when you

235
00:13:23,760 --> 00:13:26,400
have that automatic transition 
translation of data. 

236
00:13:26,720 --> 00:13:28,480
So it's it's literally just 
three steps. 

237
00:13:28,480 --> 00:13:32,280
You download the data, you 
import it into the BTP and then 

238
00:13:32,280 --> 00:13:35,000
that kicks out a file that you 
then upload into the migration 

239
00:13:35,000 --> 00:13:37,640
workbench for S4. 
So pretty pretty streamline 

240
00:13:37,640 --> 00:13:40,720
process and then you just refine
kind of the the, the custom 

241
00:13:40,720 --> 00:13:43,040
data, the custom fields that you
might have had in one same 

242
00:13:43,040 --> 00:13:46,120
system versus the other? 
Rafael, would you like to add 

243
00:13:46,120 --> 00:13:48,520
something on this point? 
So, needs you. 

244
00:13:48,520 --> 00:13:51,160
You mentioned the Excel Lighters
program, how important it was 

245
00:13:51,160 --> 00:13:53,240
for you. 
But it was equally important for

246
00:13:53,240 --> 00:13:55,840
us because as you heard it from 
the ARC, it was not an easy 

247
00:13:55,960 --> 00:13:57,640
project. 
It was not just, of course. 

248
00:13:57,640 --> 00:13:59,800
It was a migration from by 
design to S4. 

249
00:14:00,280 --> 00:14:02,800
And in this sense with the high 
flow that Russell just 

250
00:14:02,840 --> 00:14:06,200
mentioned, we were able to take 
the migration part away from 

251
00:14:06,200 --> 00:14:09,160
Fenina key user workload. 
And that was mainly a work from 

252
00:14:09,160 --> 00:14:12,040
consultant and technician and 
developer to migrate this date. 

253
00:14:12,040 --> 00:14:15,760
And then we could focus with the
customer on the best practice 

254
00:14:15,760 --> 00:14:18,240
from SAP. 
And of course then it was 

255
00:14:18,240 --> 00:14:19,840
another component that was 
important. 

256
00:14:19,840 --> 00:14:22,640
It was one key functionality 
which is a pure retail 

257
00:14:22,640 --> 00:14:26,480
functionality that was not 
available within S4 public that 

258
00:14:26,480 --> 00:14:29,000
we were able to develop 
specifically for for the 

259
00:14:29,000 --> 00:14:31,200
customer and that also made a 
difference. 

260
00:14:32,040 --> 00:14:34,600
But with all the writers 
programs that means for the help

261
00:14:34,600 --> 00:14:37,160
of the migration help us to 
understand the business process 

262
00:14:37,320 --> 00:14:40,160
because we were both early 
adopter in this journey. 

263
00:14:40,520 --> 00:14:43,760
Without the also the Technical 
Support we got for the specific 

264
00:14:43,760 --> 00:14:46,680
development we made or the one 
specific add on we needed, we 

265
00:14:46,680 --> 00:14:48,400
wouldn't be able to to achieve 
that. 

266
00:14:48,520 --> 00:14:50,720
OK, OK. 
Good to know that you want to 

267
00:14:50,760 --> 00:14:53,680
add something on this. 
This is one example of one of 

268
00:14:53,680 --> 00:14:57,840
our concerns in moving into S4. 
Another one was also the size of

269
00:14:57,840 --> 00:15:00,560
our orders. 
The number of order lines that 

270
00:15:00,560 --> 00:15:04,840
we have on a typical order is 
simply too much for BYD. 

271
00:15:04,960 --> 00:15:08,480
So that was one of the things 
that we wanted to be sure of 

272
00:15:08,480 --> 00:15:12,680
that S4 would be able to cope 
with that because there was some

273
00:15:12,680 --> 00:15:16,680
scepticism with the users. 
We needed to develop a number of

274
00:15:16,680 --> 00:15:19,920
workarounds in BYD to be able to
handle the size of the orders 

275
00:15:19,920 --> 00:15:22,960
that was coming in from our 
customers and that put a lot of 

276
00:15:22,960 --> 00:15:27,440
stress on customer service. 
So at the one time that created 

277
00:15:27,440 --> 00:15:29,800
the scepticism from some of the 
users. 

278
00:15:30,360 --> 00:15:33,680
On the other hand that was also 
like the carrots that we could 

279
00:15:33,680 --> 00:15:36,760
hold in front of them because 
nobody was jumping up and down 

280
00:15:36,760 --> 00:15:39,840
to so quickly after a first 
implementation, we were going 

281
00:15:39,840 --> 00:15:42,680
through a second one. 
But the carrot was that, you 

282
00:15:42,680 --> 00:15:47,520
know, S4 would be able to solve 
a lot of the user interface and 

283
00:15:47,520 --> 00:15:50,400
user issues that had arisen in 
BYD. 

284
00:15:50,640 --> 00:15:55,160
So we took advantage of that to 
motivate people to go for it 

285
00:15:55,160 --> 00:15:56,760
again. 
That's a good thing. 

286
00:15:56,760 --> 00:15:58,920
We actually to my next question,
we'd like to listen a bit about 

287
00:15:58,920 --> 00:16:01,480
or learn more from the 
challenges that you guys have 

288
00:16:01,480 --> 00:16:04,120
encountered, you know during the
project, be it you know, 

289
00:16:04,120 --> 00:16:06,960
functional challenges, technical
challenges, extensibility 

290
00:16:06,960 --> 00:16:09,120
challenges. 
Russell, do you want to to start

291
00:16:09,120 --> 00:16:12,160
with this one? 
Some of the challenges with that

292
00:16:12,160 --> 00:16:15,280
migration is you know really 
just cloud is in our DNA 

293
00:16:15,280 --> 00:16:17,000
Navigator. 
So we're we're very used to the 

294
00:16:17,000 --> 00:16:18,920
cloud deployment method. 
We're very used to the Fit to 

295
00:16:18,920 --> 00:16:21,520
standard workshop. 
But there is differences between

296
00:16:21,520 --> 00:16:25,200
by design and S4 fundamentally 
how they're designed. 

297
00:16:25,600 --> 00:16:28,240
Whereas by design is more that 
suite in a box. 

298
00:16:28,240 --> 00:16:31,560
So you get like a a mile wide in
an inch deep type of 

299
00:16:31,560 --> 00:16:36,120
functionality whereas S4 is much
deeper in certain areas but not 

300
00:16:36,120 --> 00:16:39,400
necessarily as wide. 
And so certain challenges with 

301
00:16:39,400 --> 00:16:41,960
the functionality that my team 
wanted weren't there. 

302
00:16:42,000 --> 00:16:44,400
And so how we, how we really 
address that is we just took 

303
00:16:44,760 --> 00:16:47,440
those fit to standard workshops,
identified the gaps and really 

304
00:16:47,440 --> 00:16:51,480
broke down those deviations to 
the best practices, escalated 

305
00:16:51,480 --> 00:16:54,120
those to our steering committee 
and were able to make a decision

306
00:16:54,120 --> 00:16:58,560
on how to accomplish and resolve
those issues. 

307
00:16:58,560 --> 00:17:01,600
And again we ended up leveraging
the the BTP for some 

308
00:17:01,600 --> 00:17:04,640
integrations in a third party 
for for some more depth in the 

309
00:17:04,640 --> 00:17:08,240
CRM area was one one example 
that we we needed to extend into

310
00:17:08,240 --> 00:17:09,359
do. 
You want to add something? 

311
00:17:09,839 --> 00:17:13,280
Yeah, in term of challenge, the 
first thing which is great with 

312
00:17:13,280 --> 00:17:16,920
S for public is the way the tool
is documented and to activate 

313
00:17:16,920 --> 00:17:19,640
methodology and all the tools 
that we are available for the 

314
00:17:19,640 --> 00:17:21,599
project. 
On the other side, there is so 

315
00:17:21,599 --> 00:17:24,880
many tool that it was difficult 
at the beginning to digest all 

316
00:17:24,880 --> 00:17:29,240
of that, but that's great. 
The other challenge is thing 

317
00:17:29,240 --> 00:17:32,080
that project is complex because 
you have third party logistic, 

318
00:17:33,320 --> 00:17:36,240
we have shops that means we are 
using also SAP customer checkout

319
00:17:36,600 --> 00:17:39,440
and we have an EDI partner and 
we have 2000 customers that are 

320
00:17:39,480 --> 00:17:41,520
sending EDI message on a daily 
basis. 

321
00:17:42,000 --> 00:17:44,960
And we needed in the middle to 
put in the middle of sub cloud 

322
00:17:44,960 --> 00:17:48,080
platform integration to 
orchestrate all of that and that

323
00:17:48,080 --> 00:17:51,880
was a a big challenge and to 
manage all the exception of all 

324
00:17:51,880 --> 00:17:54,680
the customer of Fenina. 
And from the customer point of 

325
00:17:54,680 --> 00:17:57,520
view, the the main challenges 
that you now remember after the 

326
00:17:57,520 --> 00:18:00,240
process? 
The first thing is that that the

327
00:18:00,440 --> 00:18:04,800
SAPERP environment is a bit of a
closed environment. 

328
00:18:05,000 --> 00:18:07,840
You know, SAP uses their own 
vocabulary. 

329
00:18:07,840 --> 00:18:11,680
There's there's a lot of very 
specific terminology a lot of 

330
00:18:11,680 --> 00:18:15,880
very specific processes that are
going on and we are not in the 

331
00:18:15,880 --> 00:18:17,720
ERP business. 
You know I'm I'm in the laundry 

332
00:18:17,720 --> 00:18:20,520
business and so are my 
colleagues that's for us this is

333
00:18:20,520 --> 00:18:24,320
something else that comes on top
of you know what is really our 

334
00:18:24,320 --> 00:18:26,320
business and then what we are 
concerned about. 

335
00:18:26,720 --> 00:18:30,520
So that took quite a bit of you 
know, getting used to and and if

336
00:18:30,520 --> 00:18:34,120
we go back to the early stages 
like the scoping exercise and 

337
00:18:34,120 --> 00:18:38,160
then afterwards the the fit to 
standard, you really have to 

338
00:18:38,240 --> 00:18:41,480
even before you know how the 
whole system works. 

339
00:18:41,960 --> 00:18:45,040
You need to kind of get into it 
mentally and and understand the 

340
00:18:45,040 --> 00:18:50,640
vocabulary and actually also 
find out three, four, sometimes 

341
00:18:50,680 --> 00:18:54,760
you know six months later that 
something that was meant in the 

342
00:18:54,840 --> 00:18:58,800
fit to standards is not exactly 
how you understood it and now it

343
00:18:58,800 --> 00:19:02,400
comes back and you need to you 
know review that or or or make 

344
00:19:02,400 --> 00:19:06,000
some some adaptations. 
So that was a big challenge. 

345
00:19:06,760 --> 00:19:09,640
Like I said, the other challenge
was, you know, to motivate the 

346
00:19:09,640 --> 00:19:11,400
key users. 
Like I said, we're a small team.

347
00:19:11,400 --> 00:19:14,360
We're 50 people. 
There's only a handful of people

348
00:19:14,360 --> 00:19:19,120
that are capable of playing that
role of key user. 

349
00:19:19,760 --> 00:19:22,680
So they've been doing that now 
for three years in a row on top 

350
00:19:22,680 --> 00:19:25,240
of their normal jobs. 
So that was a big challenge. 

351
00:19:25,240 --> 00:19:29,000
And how do you manage that? 
How do you manage the change 

352
00:19:29,000 --> 00:19:30,800
management? 
What kind of decision do you 

353
00:19:30,800 --> 00:19:33,080
take there? 
What initiatives do you take to 

354
00:19:33,080 --> 00:19:35,560
keep people motivated? 
Also to make sure that the rest 

355
00:19:35,560 --> 00:19:40,160
of the organization that is not 
so deeply involved stays aware 

356
00:19:40,160 --> 00:19:43,880
of what is happening and doesn't
see it as somebody else's 

357
00:19:43,880 --> 00:19:46,240
problem. 
Now they need to understand that

358
00:19:46,240 --> 00:19:50,160
sooner or later they will also 
be working in this environment. 

359
00:19:50,160 --> 00:19:53,800
So you need to constantly keep 
them abreast and keep them 

360
00:19:53,800 --> 00:19:56,040
informed of of what is 
happening. 

361
00:19:56,360 --> 00:19:59,920
So those are some of the 
challenges that we had on top of

362
00:20:00,720 --> 00:20:03,200
managing the costs, managing the
timing. 

363
00:20:03,640 --> 00:20:06,680
Making sure that the quality of 
the output was what we needed 

364
00:20:06,680 --> 00:20:09,240
and and what we expected. 
Thank you for that. 

365
00:20:09,240 --> 00:20:12,000
Rafael, you mentioned the 
quality of documentation. 

366
00:20:12,000 --> 00:20:14,200
I think you mentioned as well 
ACP Activate, which is the 

367
00:20:14,200 --> 00:20:17,920
implementation methodology that 
you use for SAP as far on a 

368
00:20:17,920 --> 00:20:20,400
public cloud. 
I'd like to understand from both

369
00:20:20,400 --> 00:20:24,440
projects how was this method, 
ACP Activate able to bring the 

370
00:20:24,440 --> 00:20:28,280
right structure, the right 
people, and ultimately make the 

371
00:20:28,280 --> 00:20:31,200
entire project successful. 
Russell, would you like to start

372
00:20:31,200 --> 00:20:33,000
with this one? 
Yeah, I'd love to. 

373
00:20:33,120 --> 00:20:36,040
So the Activate methodology is a
really great tool. 

374
00:20:36,040 --> 00:20:38,400
Like I said, kind of cloud is in
our DNA already. 

375
00:20:38,400 --> 00:20:41,240
That's all we've been doing is 
cloud deployments in the public 

376
00:20:41,240 --> 00:20:43,920
environment. 
And so the Activate methodology 

377
00:20:43,920 --> 00:20:45,480
is very similar to what we 
already do. 

378
00:20:45,600 --> 00:20:48,520
However, it did give us a few 
more tools to use. 

379
00:20:48,680 --> 00:20:53,320
I do agree the best practice 
explorers that come with S4 are 

380
00:20:53,320 --> 00:20:56,760
a lot more robust and detailed 
and they're they're great to 

381
00:20:56,760 --> 00:20:59,320
kind of lay that best practice 
out and give you that foundation

382
00:20:59,320 --> 00:21:02,960
to work within. 
So one of the things that we use

383
00:21:02,960 --> 00:21:05,640
with the activate methodology is
like I kind of mentioned before 

384
00:21:05,640 --> 00:21:09,080
in the challenges was to do more
of that documentation in that 

385
00:21:09,080 --> 00:21:12,400
fit to standard workshop and 
that gave us our 80% fit. 

386
00:21:12,720 --> 00:21:15,280
And then in the next phase 
before we moved on to larger 

387
00:21:15,280 --> 00:21:18,840
testing, we just were able to 
focus on that 20% process 

388
00:21:18,840 --> 00:21:21,160
engineering that we had due to 
fine tune the system. 

389
00:21:21,680 --> 00:21:24,840
And then once we had that, we 
had that documentation that was 

390
00:21:24,840 --> 00:21:28,520
provided for the baseline and 
we're able to create those SOP S

391
00:21:28,520 --> 00:21:32,640
again in a very fast way. 
Another thing to point out is in

392
00:21:32,640 --> 00:21:35,000
SA PS Eyes Navigator is a small 
company. 

393
00:21:35,000 --> 00:21:37,520
We're on the lower end of that 
mid market spectrum. 

394
00:21:37,640 --> 00:21:41,760
And so we were able to scale the
methodology down to a project 

395
00:21:41,760 --> 00:21:45,200
team that was smaller than it 
was nationally intended to. 

396
00:21:45,240 --> 00:21:48,400
So it adds to the foundation 
that it really is a good 

397
00:21:48,400 --> 00:21:52,240
foundation and framework to work
within for companies kind of all

398
00:21:52,240 --> 00:21:55,440
sizes for implementations on S4.
What is your point of view here?

399
00:21:55,640 --> 00:21:57,720
Very similar. 
What is also great, which is 

400
00:21:57,720 --> 00:22:00,120
coming on the top of the 
activate minology is SAP, 

401
00:22:00,120 --> 00:22:04,000
Claude, ALM and tools like the 
business configuration 

402
00:22:04,000 --> 00:22:05,640
questionnaire. 
And that's come back to what you

403
00:22:05,640 --> 00:22:09,400
said here about the vocabulary 
might appear very complex, but 

404
00:22:09,400 --> 00:22:11,920
at least we have a checklist to 
go through to make sure we don't

405
00:22:11,920 --> 00:22:14,800
forget something important, even
if we don't necessarily go 

406
00:22:14,800 --> 00:22:16,080
through everything with the 
customer. 

407
00:22:16,280 --> 00:22:20,000
That's also the job of the 
consultant to simplify the 

408
00:22:20,200 --> 00:22:23,920
absorption of the information. 
Of course we say night they were

409
00:22:23,920 --> 00:22:27,400
the first one, the next customer
might not go through everything 

410
00:22:27,400 --> 00:22:30,320
we we did with Fenya. 
We we will like also mentioned 

411
00:22:30,680 --> 00:22:34,480
simplify it from the for SME. 
Let's go to one of the biggest 

412
00:22:34,480 --> 00:22:37,400
moments of of an European 
implementation, which is the go 

413
00:22:37,400 --> 00:22:40,360
live. 
I don't know if you as a from a 

414
00:22:40,360 --> 00:22:44,400
partner perspective you if this 
is day zero or this is already 

415
00:22:44,400 --> 00:22:47,840
the day 360 because a year has 
been spent or or a couple of 

416
00:22:47,840 --> 00:22:50,520
months has been spent there. 
But it's definitely the day 

417
00:22:50,520 --> 00:22:54,120
where the entire operation of 
the company works on this new 

418
00:22:54,120 --> 00:22:56,920
piece of software. 
And I'd like to understand 

419
00:22:56,920 --> 00:23:00,280
especially from our partners 
here the experience of the go 

420
00:23:00,280 --> 00:23:04,800
live, the support that you've 
gotten from SAP as your of your 

421
00:23:04,800 --> 00:23:06,800
software vendor. 
We can start with you. 

422
00:23:07,720 --> 00:23:11,280
Then we are going to go live in 
few weeks with Felina, but I can

423
00:23:11,280 --> 00:23:13,240
comment on the on the support 
from SAP. 

424
00:23:13,960 --> 00:23:16,920
That was the reason why the 
lighters was important for SNAP 

425
00:23:17,080 --> 00:23:20,240
as well As for FENA. 
Because we needed access to the 

426
00:23:20,280 --> 00:23:24,080
SAP consultant and we had access
to a full team of functional 

427
00:23:24,080 --> 00:23:27,520
specialist based in India and 
they delivered some very good 

428
00:23:27,520 --> 00:23:29,320
answer on some specific 
questions. 

429
00:23:29,360 --> 00:23:33,280
We also had access to workforce 
for specific development and of 

430
00:23:33,280 --> 00:23:38,320
course BTP is a main place where
we develop things, but we also 

431
00:23:38,320 --> 00:23:42,520
wanted to develop things inside 
S4 directly in steam punk and 

432
00:23:42,520 --> 00:23:45,440
for this we needed guidance. 
With all the support of SAP, we 

433
00:23:45,440 --> 00:23:48,600
will just still try to look 
where to build things. 

434
00:23:48,760 --> 00:23:51,600
What we know is that the go live
is an important milestone, but 

435
00:23:51,600 --> 00:23:53,800
it's not an end. 
Once we have the go live, we 

436
00:23:53,800 --> 00:23:57,480
need to support the customer at 
least until the 1st monthly 

437
00:23:57,480 --> 00:24:01,000
closure and after there is all 
the phase two implementation 

438
00:24:01,000 --> 00:24:02,960
that is. 
That's something that Felina 

439
00:24:02,960 --> 00:24:05,920
understood very early, although 
eat an elephant one piece at a 

440
00:24:05,920 --> 00:24:09,040
time and of course we have a 
full scope for the phase one and

441
00:24:09,040 --> 00:24:11,560
we have a scope coming for the 
phase two when when the team 

442
00:24:11,560 --> 00:24:12,840
will have the digest as a go 
live. 

443
00:24:13,000 --> 00:24:14,560
Typical cloud implementation, 
right? 

444
00:24:14,640 --> 00:24:17,360
Yeah, but I think it's also 
important to point out here that

445
00:24:17,560 --> 00:24:20,480
technically we probably could 
have gone live on January 1st. 

446
00:24:21,000 --> 00:24:23,480
We chose not to. 
And you know, people should just

447
00:24:23,480 --> 00:24:25,840
know that our go live with BYD 
was pretty rough. 

448
00:24:26,360 --> 00:24:29,640
So we learned some lessons there
and even if we could have gone 

449
00:24:29,640 --> 00:24:33,400
live on on let's say January 
2nd, from a technical point of 

450
00:24:33,400 --> 00:24:38,840
view, we prefer to add on 
another 90 days or three months 

451
00:24:38,960 --> 00:24:43,640
of you know, additional testing,
some further fine tuning and 

452
00:24:43,640 --> 00:24:48,240
especially give a key users and 
all the users the opportunity to

453
00:24:48,240 --> 00:24:50,200
get much more acquainted with 
the system. 

454
00:24:50,200 --> 00:24:53,640
So that by the time that we 
really go live on which will be 

455
00:24:53,640 --> 00:24:57,080
on April 2nd, people are 
actually familiar with the 

456
00:24:57,080 --> 00:25:00,840
environment, familiar with the 
technicity, have done a lot of 

457
00:25:00,960 --> 00:25:05,200
your dry runs and specifically 
for their area off the business.

458
00:25:05,200 --> 00:25:10,200
And then hopefully we'll have a 
seamless go live, at least a lot

459
00:25:10,200 --> 00:25:12,520
better than the last one. 
Let me maybe you should say a 

460
00:25:12,520 --> 00:25:14,800
little bit more about that 
because yes, you mentioned your 

461
00:25:14,800 --> 00:25:16,600
key user three years on a 
project. 

462
00:25:16,920 --> 00:25:20,000
The first part was with a by 
design project and you mentioned

463
00:25:20,280 --> 00:25:24,280
just after we went to another 
point and all difficult it was 

464
00:25:24,280 --> 00:25:28,560
that means six weeks you were 
without being able to ship we. 

465
00:25:28,600 --> 00:25:31,480
Had four weeks without any 
shipping at all and then we 

466
00:25:31,480 --> 00:25:34,120
could gradually start to start 
to build it up. 

467
00:25:34,320 --> 00:25:36,040
So that was not a good year for 
us. 

468
00:25:36,240 --> 00:25:37,880
OK. 
I can imagine. 

469
00:25:38,360 --> 00:25:42,040
Russell, back to the go live 
this big moment, How was that 

470
00:25:42,040 --> 00:25:44,560
for your company, for the end 
users? 

471
00:25:44,720 --> 00:25:46,040
How did that all go for you 
guys? 

472
00:25:46,720 --> 00:25:49,880
So I think it all comes in order
to have a good go live like you 

473
00:25:49,880 --> 00:25:53,040
just heard from the other teams 
is testing is so important. 

474
00:25:53,040 --> 00:25:56,240
And so that's what we always 
really focus on and we have 

475
00:25:56,360 --> 00:26:00,200
different quality gates and you 
know peer review and certain 

476
00:26:00,200 --> 00:26:02,840
benchmarks that we assigned to 
the users and we use the 

477
00:26:02,840 --> 00:26:06,280
activate methodology for that 
feedback and not just making 

478
00:26:06,280 --> 00:26:08,240
sure you can get through the 
process but also looking at the 

479
00:26:08,240 --> 00:26:09,880
results that come from that 
process. 

480
00:26:10,360 --> 00:26:14,120
And so our our mantra here is 
you know go live is just another

481
00:26:14,120 --> 00:26:16,600
day because you've done so much 
testing, you have the 

482
00:26:16,600 --> 00:26:19,160
repetition, you can do your job 
in the new system. 

483
00:26:19,440 --> 00:26:22,240
We have change management 
embedded into the methodology 

484
00:26:22,600 --> 00:26:26,040
and so our goal is always to 
have go live just another day. 

485
00:26:26,320 --> 00:26:28,040
So it's not this big stressful 
event. 

486
00:26:28,720 --> 00:26:31,160
And the second thing is then and
you kind of mentioned it 

487
00:26:31,160 --> 00:26:34,880
earlier, do you consider that 
day one or day 365, we actually 

488
00:26:34,880 --> 00:26:37,760
don't a navigator, we don't 
consider our customer and same 

489
00:26:37,760 --> 00:26:39,840
with our as being a customer as 
well. 

490
00:26:40,200 --> 00:26:42,280
We didn't consider ourselves 
live until the first month and 

491
00:26:42,280 --> 00:26:44,120
close. 
And so after you've been using 

492
00:26:44,120 --> 00:26:46,880
the system for a month and then 
you can actually look at the 

493
00:26:46,880 --> 00:26:49,840
results, close your books, 
submit your statutory reports, 

494
00:26:50,200 --> 00:26:52,880
that's the day that we really 
say, OK, now this phase and this

495
00:26:52,880 --> 00:26:56,040
implementation is now complete 
and we move into that kind of 

496
00:26:56,040 --> 00:26:59,400
hyper care and support phase or 
different phase twos that have 

497
00:26:59,400 --> 00:27:00,960
been identified throughout the 
project. 

498
00:27:01,280 --> 00:27:04,400
And so for us we did have two 
phases and so the first phase 

499
00:27:04,680 --> 00:27:06,440
went pretty smooth. 
The biggest challenge that we 

500
00:27:06,440 --> 00:27:09,480
had is this user bandwidth, 
they're very consumed on the 

501
00:27:09,480 --> 00:27:12,520
finance side with closing out 
you know last month at the same 

502
00:27:12,520 --> 00:27:14,160
time using the new system for 
this month. 

503
00:27:14,160 --> 00:27:16,600
But other than that, from a a 
functional system perspective, 

504
00:27:16,600 --> 00:27:19,880
the team was was very ready to 
cut over and and start using the

505
00:27:19,880 --> 00:27:21,600
system. 
Yeah, you've already started a 

506
00:27:21,600 --> 00:27:24,320
bit to talk about, you know 
comparison as you can. 

507
00:27:24,600 --> 00:27:27,400
It's sometimes doesn't help much
to compare especially if it's 

508
00:27:27,400 --> 00:27:28,960
apples and oranges. 
But we're talking about two 

509
00:27:28,960 --> 00:27:32,640
cloud ear pieces and and I'd 
like you refer to dig a little 

510
00:27:32,640 --> 00:27:36,240
bit in, you know the before 
after them comparisons, what is 

511
00:27:36,240 --> 00:27:40,160
now working much better, what 
things you're eventually 

512
00:27:40,160 --> 00:27:42,600
missing, you know from the 
previous software which would be

513
00:27:42,600 --> 00:27:45,000
an eventual road map element for
AC PS road map. 

514
00:27:45,360 --> 00:27:46,640
Would you like to do the best 
one? 

515
00:27:46,960 --> 00:27:48,400
Sure. 
And we're actually we're 

516
00:27:48,400 --> 00:27:50,840
actually working with some of 
the innovation teams at SAP 

517
00:27:50,840 --> 00:27:53,840
right now based on our feedback.
So that's what's pretty excited 

518
00:27:53,840 --> 00:27:55,720
about being both a partner and 
as a customer. 

519
00:27:56,160 --> 00:27:58,920
So time entry is always just a 
challenge in in any professional

520
00:27:58,920 --> 00:28:01,960
service organization and while 
it's it's very functional and 

521
00:28:01,960 --> 00:28:04,160
that's we're out-of-the-box. 
We're looking at leveraging 

522
00:28:04,160 --> 00:28:08,240
things like AI to use natural 
language time entry and convert 

523
00:28:08,240 --> 00:28:10,120
that into actually booking the 
time. 

524
00:28:10,120 --> 00:28:15,600
So you can basically just use 
natural language and book my 

525
00:28:15,600 --> 00:28:19,120
time the same as last week and 
then the the ChatGPT will 

526
00:28:19,120 --> 00:28:21,720
actually use that and enter your
time for you on that behalf. 

527
00:28:21,720 --> 00:28:24,960
So just some optimizations on 
really that time entry part is 

528
00:28:24,960 --> 00:28:27,960
our big goal and that's not 
necessarily a gap, but just 

529
00:28:27,960 --> 00:28:31,520
looking to to add value to my 
team as well as take off some of

530
00:28:31,520 --> 00:28:34,160
the administration functions. 
That's not value adding to our 

531
00:28:34,160 --> 00:28:36,480
organization, right. 
That gives them more time to be 

532
00:28:36,480 --> 00:28:39,120
in front of our customers and 
obviously delivering value to. 

533
00:28:39,680 --> 00:28:42,680
Them Diek and Rafael, would you 
like to add some words on this 

534
00:28:42,680 --> 00:28:45,240
before, after? 
Well, obviously there's a big 

535
00:28:45,240 --> 00:28:48,520
change for the users after 
having worked in for over 15 

536
00:28:48,520 --> 00:28:52,040
years in one system and then, 
you know, switching to SIPBYD, 

537
00:28:52,520 --> 00:28:55,000
that was a big change in every 
aspect. 

538
00:28:55,400 --> 00:28:58,120
The look and feel, the, the 
navigation, the, the user 

539
00:28:58,120 --> 00:29:00,320
interface. 
I mean everything, the whole 

540
00:29:00,320 --> 00:29:02,600
logic behind the system was 
different. 

541
00:29:03,200 --> 00:29:07,680
And you know you have as many 
different opinions on that as 

542
00:29:07,680 --> 00:29:10,000
you have people, you know, 
because some people are really 

543
00:29:10,000 --> 00:29:14,280
open for the change and we have 
other people that after two 

544
00:29:14,280 --> 00:29:18,720
years are still, you know have 
some melancholy for the previous

545
00:29:18,720 --> 00:29:20,800
system. 
So that is very diverse. 

546
00:29:21,280 --> 00:29:23,680
Now what we're really looking 
forward to with the transition 

547
00:29:23,680 --> 00:29:27,520
to S4 is that you know we are 
confident, we know from the 

548
00:29:27,520 --> 00:29:29,920
testing now that means starts to
show really in the in the 

549
00:29:29,920 --> 00:29:33,600
testing that S4 is going to be 
much more performant than BYD 

550
00:29:33,600 --> 00:29:35,520
was. 
And that will have a major 

551
00:29:35,520 --> 00:29:40,960
impact on our organization 
because currently the users are 

552
00:29:40,960 --> 00:29:43,440
much quicker than what the 
system can handle. 

553
00:29:44,040 --> 00:29:47,080
Which means that we're actually 
putting some overtime and just 

554
00:29:47,080 --> 00:29:50,480
getting through the work in BYD.
And that will be a massive 

555
00:29:50,480 --> 00:29:52,640
improvement once we make the 
step into S4. 

556
00:29:53,240 --> 00:29:56,720
Which means not only that we 
will work more efficient but it 

557
00:29:56,720 --> 00:30:01,520
will also free up additional 
time that will allow us to 

558
00:30:01,520 --> 00:30:04,640
actually engage with our 
customers more that we currently

559
00:30:04,640 --> 00:30:07,240
can do. 
We need to be we're working the 

560
00:30:07,240 --> 00:30:10,360
system now. 
What really our focus should be 

561
00:30:10,360 --> 00:30:13,320
is working our customers and 
that is something that we are 

562
00:30:13,320 --> 00:30:17,320
really looking forward to for 
April 3rd, the day after. 

563
00:30:17,720 --> 00:30:20,840
For that, Rafael, would you like
to add something on this 

564
00:30:20,840 --> 00:30:24,440
perspective? 
I can talk about the project. 

565
00:30:24,440 --> 00:30:27,400
Obviously we didn't make the by 
design project and we know that 

566
00:30:27,880 --> 00:30:30,120
it's very easy at the end of the
project to come to have a 

567
00:30:30,120 --> 00:30:32,800
different opinion and to finger 
point the mistakes. 

568
00:30:33,280 --> 00:30:36,200
We definitely made some more so 
during that implementation, but 

569
00:30:36,200 --> 00:30:38,480
we tried at least not to 
replicate the same mistakes on 

570
00:30:38,480 --> 00:30:42,000
the previous implementation. 
Of course we we have a team 

571
00:30:42,000 --> 00:30:44,640
based in Slovakia and in Hungary
and we are serving a project in 

572
00:30:44,640 --> 00:30:48,600
Germany, which is already 
something different, but we try 

573
00:30:48,600 --> 00:30:52,400
to be as much present on site as
possible and that the project 

574
00:30:52,400 --> 00:30:54,960
methodology we hope is making 
the difference today. 

575
00:30:56,440 --> 00:30:58,640
Yeah and that may be something 
that can be stressed enough. 

576
00:30:59,320 --> 00:31:01,920
You know where we did the choice
of the partner for the for the 

577
00:31:01,920 --> 00:31:05,760
implementation is paramount. 
You know with SAP that you have 

578
00:31:05,760 --> 00:31:08,440
a a thoroughly tested and built 
system. 

579
00:31:08,440 --> 00:31:12,480
You know you, you can't second 
guess the quality of the product

580
00:31:12,480 --> 00:31:16,040
that you're buying, but how you 
implement it and what what it 

581
00:31:16,040 --> 00:31:19,080
actually will do for your 
organization there, There is a 

582
00:31:19,080 --> 00:31:22,680
big, a big difference there. 
And like I said as a small 

583
00:31:22,680 --> 00:31:25,160
organization, we cannot focus on
the system. 

584
00:31:25,160 --> 00:31:27,920
We have to focus on our business
and on our customers. 

585
00:31:28,240 --> 00:31:31,760
So what we need is an 
implementation partner that has 

586
00:31:31,760 --> 00:31:35,920
all the SAP knowledge in their 
back pocket and then is prepared

587
00:31:36,280 --> 00:31:39,080
to invest the time to understand
our business. 

588
00:31:39,440 --> 00:31:40,960
Yeah. 
And really become that in 

589
00:31:40,960 --> 00:31:45,120
between person, between the 
system and SAP and our business 

590
00:31:45,120 --> 00:31:50,760
and be the translator of us who 
are really focusing on what we 

591
00:31:50,760 --> 00:31:54,320
need to get done. 
And then translated that into 

592
00:31:54,320 --> 00:31:58,160
the setup of the system, in this
case of SAPS 4. 

593
00:31:58,640 --> 00:32:01,720
And in selecting your partner, I
think that is really, really 

594
00:32:01,720 --> 00:32:04,600
important to make sure that you 
have somebody that is prepared 

595
00:32:04,960 --> 00:32:08,320
and has the capability of 
digging into your business and 

596
00:32:08,320 --> 00:32:11,360
really becoming a partner in 
that sense as well. 

597
00:32:11,840 --> 00:32:13,240
OK. 
I think it's a great call to 

598
00:32:13,280 --> 00:32:16,000
actions for all the partners 
eventually watching this 

599
00:32:16,000 --> 00:32:17,760
recording. 
Be prepared and the cloud 

600
00:32:17,760 --> 00:32:20,520
mindsets, but it's possible. 
Yeah, it is. 

601
00:32:21,480 --> 00:32:24,520
Big thanks to you, Russell, to 
you, Dirk, and to you, Rafael. 

602
00:32:24,520 --> 00:32:27,280
I think this was a very 
interesting, very unique thing, 

603
00:32:27,280 --> 00:32:31,720
and I think it would be super 
valuable for our audience. 1 

604
00:32:31,720 --> 00:32:34,280
main thing that I've learned 
personally is that it's not 

605
00:32:34,280 --> 00:32:36,880
possible to outgrow the SAP 
portfolio. 

606
00:32:37,320 --> 00:32:41,800
All the SAP by Design customers 
have the opportunity, if the 

607
00:32:41,800 --> 00:32:45,800
business needs it, to go to that
next level and to start the 

608
00:32:45,800 --> 00:32:49,520
journey with ACPS 4 HANA Cloud 
Public Edition. 

609
00:32:49,880 --> 00:32:53,400
It was a very. 
Exciting episode again to our. 

610
00:32:53,400 --> 00:32:57,000
Audience if you like it. 
And have ideas about the next 

611
00:32:57,000 --> 00:33:00,040
relevant topic for this podcast?
Please just send us an. 

612
00:33:00,040 --> 00:33:02,960
E-mail to inside S. 
Four at SAP dot. 

613
00:33:02,960 --> 00:33:09,320
Com TuneIn next time and always 
be inside SAPS for Hana Cloud.

