1
00:00:10,680 --> 00:00:14,160
Welcome to the podcast Inside 
SAPS for HANA Cloud. 

2
00:00:14,240 --> 00:00:17,440
There is no customer success 
without product success and 

3
00:00:17,440 --> 00:00:21,640
project success. 
A transition to a new software 

4
00:00:21,640 --> 00:00:25,240
has so many facets. 
It touches on the IT landscape, 

5
00:00:25,360 --> 00:00:29,040
business processes and most 
importantly the users of the 

6
00:00:29,040 --> 00:00:32,360
system. 
In episode 103 recently, we 

7
00:00:32,360 --> 00:00:36,640
discussed the initial stages of 
our customers Felinas transition

8
00:00:36,920 --> 00:00:41,880
from SAP Business by Design to 
SAP Eswana Cloud Public Edition.

9
00:00:42,360 --> 00:00:45,400
If you missed that episode, I 
invite you to listen to it. 

10
00:00:46,000 --> 00:00:48,680
Today, around four months post 
go live. 

11
00:00:48,800 --> 00:00:51,840
We are reconnecting with the 
same customer, Felina and their 

12
00:00:51,840 --> 00:00:55,800
partners Snap to delve deeper 
into the current experiences and

13
00:00:55,800 --> 00:00:59,080
inside gains from that 
significant change. 

14
00:00:59,680 --> 00:01:03,160
Let's explore today how the 
transition has unfolded and what

15
00:01:03,160 --> 00:01:07,000
lessons have been learned along 
the way by both the customer 

16
00:01:07,000 --> 00:01:11,440
Felina and the partners Snap. 
So welcome or welcome back, Deck

17
00:01:11,440 --> 00:01:15,760
DeVos from Felina and Rafael 
Pink, the partner Snap. 

18
00:01:16,120 --> 00:01:19,680
Good to have you back. 
Hello Yannick, good to be back. 

19
00:01:20,880 --> 00:01:23,440
Hi, Yannick. 
Thanks for being with us today. 

20
00:01:23,440 --> 00:01:27,080
And let's start with looking 
back over the implementation. 

21
00:01:27,080 --> 00:01:30,400
I know it took actually more 
time than planned. 

22
00:01:30,480 --> 00:01:34,200
Is this something you would have
done differently to keep the 

23
00:01:34,200 --> 00:01:37,360
project timelines? 
Maybe you want to start with 

24
00:01:37,360 --> 00:01:39,240
that one that Rafael you can 
comment? 

25
00:01:40,360 --> 00:01:44,920
So if we talk specifically about
the the timing, the planning and

26
00:01:44,920 --> 00:01:50,160
the timeline, yes, if we would 
have known upfront exactly, then

27
00:01:50,160 --> 00:01:53,400
we would have allowed ourselves 
a little bit more time. 

28
00:01:54,520 --> 00:01:56,960
At the same time, when you 
enter, when you embark on a 

29
00:01:56,960 --> 00:02:01,080
project like this, you have to 
keep some room for flexibility. 

30
00:02:01,280 --> 00:02:06,360
I think it's impossible to 
really detail out everything in 

31
00:02:06,360 --> 00:02:11,039
the plan from A-Z with the 
correct timeline to some degree 

32
00:02:11,039 --> 00:02:14,080
of flexibility. 
Some degree of relaxation during

33
00:02:14,080 --> 00:02:18,280
such a project is needed. 
I call it flexible focus. 

34
00:02:18,720 --> 00:02:21,040
Yeah, you keep your eye on the 
ball, you keep your eye on the 

35
00:02:21,040 --> 00:02:25,880
end target and you have to allow
yourself to be flexible in 

36
00:02:25,880 --> 00:02:29,480
certain areas to be able to come
to a good end result. 

37
00:02:30,680 --> 00:02:32,040
Yeah. 
And I think we shouldn't forget 

38
00:02:32,040 --> 00:02:36,320
the context of the Fena project 
where they went to a first 

39
00:02:36,320 --> 00:02:39,440
implementation of by design and 
just after the goal arrives, 

40
00:02:39,440 --> 00:02:41,360
they realized they need another 
solution. 

41
00:02:41,640 --> 00:02:44,440
They had to change partner to re
engage the key user. 

42
00:02:44,880 --> 00:02:48,360
That means we knew from the 
beginning that yes, we had a 

43
00:02:48,720 --> 00:02:53,120
very good project plan, but we 
knew we will have to accommodate

44
00:02:53,120 --> 00:02:56,040
that. 
Not so much to be ready from a 

45
00:02:56,040 --> 00:02:59,200
technical point of view, but to 
make sure that the key users are

46
00:02:59,200 --> 00:03:01,960
ready. 
Because second goal live 18 

47
00:03:01,960 --> 00:03:05,080
months after the first one is a 
lot of workload and stress for 

48
00:03:05,080 --> 00:03:07,880
the key user. 
Maybe in addition, what I would 

49
00:03:07,880 --> 00:03:12,560
say is at some point, I think it
was in January, we needed to 

50
00:03:12,560 --> 00:03:15,320
decide whether we were going to 
go live or not. 

51
00:03:15,600 --> 00:03:18,960
We had to take that go no go 
decision and we decided not to 

52
00:03:18,960 --> 00:03:22,080
go live at that moment, but to 
allow ourselves a little bit 

53
00:03:22,080 --> 00:03:25,160
more time to have a more 
successful launch. 

54
00:03:25,840 --> 00:03:29,640
I do not regret for one second 
making that decision. 

55
00:03:30,200 --> 00:03:33,560
I think if we would have really 
stuck to the original planning 

56
00:03:33,560 --> 00:03:37,480
and seen that as a fetish to go 
live at the moment that we said 

57
00:03:37,480 --> 00:03:41,160
we were going to go live, we 
would have had a much more 

58
00:03:41,160 --> 00:03:45,240
difficult launch and a much more
difficult integration of the 

59
00:03:45,240 --> 00:03:46,840
project and the rest of the 
business. 

60
00:03:47,400 --> 00:03:51,920
So I'm absolutely very positive 
and still in favour of making 

61
00:03:51,920 --> 00:03:54,520
that decision to allow ourselves
a little bit more time. 

62
00:03:55,280 --> 00:03:57,960
I like to love this idea and the
wording you've chosen, the 

63
00:03:57,960 --> 00:03:59,840
flexible focus. 
I think you're the first time 

64
00:03:59,840 --> 00:04:03,920
bringing that on the podcast 
today, a couple of weeks, a 

65
00:04:03,920 --> 00:04:07,280
month after, Go live. 
How is life for you, the 

66
00:04:07,280 --> 00:04:09,440
customer and from the partner 
perspective? 

67
00:04:10,880 --> 00:04:14,960
I think the Go live were 
extremely smooth, much smoother 

68
00:04:14,960 --> 00:04:17,920
than we would even have expected
from the partner side. 

69
00:04:18,399 --> 00:04:20,959
The integration work well from 
day one. 

70
00:04:20,959 --> 00:04:26,080
We ramp up the activation of the
2000 EDI customer in few days or

71
00:04:26,080 --> 00:04:27,920
weeks, which was a complete 
opposite. 

72
00:04:27,920 --> 00:04:31,120
That was the customer experience
and the oath of Go lives that 

73
00:04:31,120 --> 00:04:36,160
took place few months before. 
Of course we had an hyper care 

74
00:04:36,160 --> 00:04:38,280
situation for a couple of 
months. 

75
00:04:38,680 --> 00:04:41,960
We watch very closely the 1st 
monthly closures. 

76
00:04:42,280 --> 00:04:47,440
No, we are on five months after 
Goliath and the customer is 

77
00:04:47,720 --> 00:04:51,480
contacting us on very rare 
occasion for additional support.

78
00:04:53,680 --> 00:04:55,400
I would agree with Rafael on 
this one. 

79
00:04:55,600 --> 00:04:59,960
The go live and the hyper care, 
which was not a couple of months

80
00:04:59,960 --> 00:05:03,680
but a couple of weeks, six weeks
to be exact, went very smooth. 

81
00:05:04,160 --> 00:05:07,000
I think everybody was very well 
prepared. 

82
00:05:07,080 --> 00:05:10,800
It went better than anybody 
expected to the point where 

83
00:05:10,800 --> 00:05:13,760
there was some disbelief in the 
project team and we were kind of

84
00:05:13,760 --> 00:05:16,720
bracing for something that was 
going to come and that we hadn't

85
00:05:16,720 --> 00:05:18,320
noticed yet. 
But it didn't come. 

86
00:05:18,920 --> 00:05:22,520
So it went very well and I think
everybody involved in the 

87
00:05:22,520 --> 00:05:25,120
project is extremely happy with 
how it went. 

88
00:05:25,680 --> 00:05:30,600
There is one area where we now 
see that there could have been 

89
00:05:30,600 --> 00:05:33,880
better preparation and in our 
case that is in the finance 

90
00:05:33,880 --> 00:05:36,800
area. 
Oddly enough, the finance area 

91
00:05:36,800 --> 00:05:40,800
was the first to say that they 
were ready well before the go 

92
00:05:40,800 --> 00:05:43,600
live. 
But in fact, once we had the go 

93
00:05:43,600 --> 00:05:46,800
live, they were struggling and 
the first month closure took an 

94
00:05:46,800 --> 00:05:49,480
extra month for them to be able 
to finish it. 

95
00:05:50,040 --> 00:05:54,120
We have not really done the 
postpartum or post launch 

96
00:05:54,160 --> 00:05:57,840
analysis specifically on the 
finance area to understand why 

97
00:05:57,840 --> 00:06:00,720
that happened. 
But it seems that a little bit 

98
00:06:00,720 --> 00:06:05,200
of overconfidence has creeped in
there and it kind of relaxed a 

99
00:06:05,200 --> 00:06:06,920
bit after they thought that they
were ready. 

100
00:06:07,640 --> 00:06:10,440
But overall, I would say it was 
a very successful launch. 

101
00:06:10,960 --> 00:06:12,640
OK, thanks. 
Glad to hear that. 

102
00:06:12,640 --> 00:06:14,480
Obviously. 
And you did all that with the 

103
00:06:14,480 --> 00:06:16,560
team because you have a business
to run, you have a business 

104
00:06:16,560 --> 00:06:19,600
transformation for which you 
need new platform. 

105
00:06:20,040 --> 00:06:23,120
So I'd like to understand from 
you what were some of the 

106
00:06:23,120 --> 00:06:26,360
immediate business impact you 
notice post transition, you 

107
00:06:26,360 --> 00:06:29,120
know, on the day-to-day 
operations, especially looking 

108
00:06:29,120 --> 00:06:31,400
at business performance. 
Have you observed measurable 

109
00:06:31,400 --> 00:06:36,280
improvements or benefits can be 
really directly attributed to 

110
00:06:36,280 --> 00:06:40,040
the new platform to the fact 
that you are now running on SAPS

111
00:06:40,040 --> 00:06:45,440
400 cloud Public edition? 
Yes, the area where the problem 

112
00:06:45,440 --> 00:06:47,920
was the biggest, where the pain 
was the biggest with the old 

113
00:06:47,920 --> 00:06:52,240
system that was inadequate with 
our customer service department 

114
00:06:52,800 --> 00:06:54,800
because that is where everything
comes together. 

115
00:06:54,800 --> 00:06:58,840
You need to be able to give a 
quick and correct answer to any 

116
00:06:58,960 --> 00:07:02,480
customer requirement or request 
coming in, whether it's new 

117
00:07:02,480 --> 00:07:05,800
orders, whether it's order 
situation, whether it's 

118
00:07:06,000 --> 00:07:09,040
questions from customers on when
their delivery will arrive, 

119
00:07:09,040 --> 00:07:12,080
etcetera, etcetera. 
Do you really need to be able to

120
00:07:12,080 --> 00:07:15,640
look up the correct information 
in any area of the business? 

121
00:07:16,160 --> 00:07:20,720
And the stress in the customer 
service department prior to the 

122
00:07:20,720 --> 00:07:24,680
launch, even prior to starting 
the project was extremely high. 

123
00:07:25,160 --> 00:07:28,560
Workload was extremely high. 
And then of course they went 

124
00:07:28,560 --> 00:07:32,240
through a very hard time during 
the project because on top of 

125
00:07:32,240 --> 00:07:36,200
that workload, they also had to 
run the S4 project. 

126
00:07:36,760 --> 00:07:41,360
But now after the go live, we 
have seen an immediate 

127
00:07:41,480 --> 00:07:45,560
relaxation within that team. 
The workload has come down 

128
00:07:45,640 --> 00:07:49,480
significantly to the point where
we now have one person of the 

129
00:07:49,480 --> 00:07:53,480
team who is on parental leave 
for a year who did not have the 

130
00:07:53,480 --> 00:07:57,000
need to replace that person. 
The rest of the team can now 

131
00:07:57,240 --> 00:08:00,400
relatively easily, and I have to
be careful with my words because

132
00:08:00,400 --> 00:08:03,480
they might listen relatively 
easily. 

133
00:08:03,480 --> 00:08:05,480
They can handle the workload 
that is there. 

134
00:08:05,480 --> 00:08:08,560
Now they really have the feeling
that the information is at their

135
00:08:08,560 --> 00:08:11,240
fingertips. 
That is really remarkable 

136
00:08:11,240 --> 00:08:14,880
improvement that we are noticing
and that is only possible 

137
00:08:14,880 --> 00:08:19,120
because all the other 
departments are now capable of 

138
00:08:19,240 --> 00:08:22,320
providing the correct 
information via the system, 

139
00:08:22,360 --> 00:08:25,200
which was also hard to do 
before. 

140
00:08:25,680 --> 00:08:29,280
Logging the correct information,
adjusting it where needed, 

141
00:08:29,320 --> 00:08:32,440
updating it where needed was a 
real burden before. 

142
00:08:32,679 --> 00:08:36,440
And now it's just a part of the 
day-to-day work and it happens 

143
00:08:36,440 --> 00:08:39,720
very smoothly, including the 
exchange of information with our

144
00:08:39,720 --> 00:08:42,640
factory in Hungary and also the 
exchange of information with our

145
00:08:42,640 --> 00:08:46,360
external partners like our 
logistical partners and with our

146
00:08:46,360 --> 00:08:49,560
customers through electronic 
data exchange, EDI. 

147
00:08:50,120 --> 00:08:53,040
All of that is working much 
smoother than before. 

148
00:08:53,640 --> 00:08:55,920
OK, that's interesting. 
And did you really get feedback 

149
00:08:55,920 --> 00:08:58,560
from the users in the customer 
service department? 

150
00:08:58,560 --> 00:09:00,880
You talk about this relaxation, 
so can you quote a few 

151
00:09:00,880 --> 00:09:02,240
colleagues? 
What did they say to you? 

152
00:09:02,920 --> 00:09:05,680
Yes, definitely. 
I think the most remarkable 

153
00:09:05,680 --> 00:09:08,800
quotes we got was from one of 
our colleagues who's been 

154
00:09:08,920 --> 00:09:11,600
critical throughout the entire 
process. 

155
00:09:11,840 --> 00:09:16,000
She adeared extremely to the old
platform that we had in in which

156
00:09:16,000 --> 00:09:17,720
she had been working for 13 
years. 

157
00:09:18,040 --> 00:09:20,960
And the biggest compliment that 
I heard was I've been really 

158
00:09:20,960 --> 00:09:23,280
trying to find something wrong, 
but I couldn't find any. 

159
00:09:23,600 --> 00:09:25,440
That's a beautiful quote. 
Yeah. 

160
00:09:25,840 --> 00:09:28,760
OK, good. 
But let's look at the other side

161
00:09:28,760 --> 00:09:30,800
of the cone. 
There are always some challenges

162
00:09:30,840 --> 00:09:34,120
and migration from ERPA to ERPB,
It's a change. 

163
00:09:34,120 --> 00:09:36,360
Management should bring a lot of
people with you. 

164
00:09:36,480 --> 00:09:39,520
Most people, including me, don't
like to go from a new software 

165
00:09:39,520 --> 00:09:41,200
because it was so nice in the 
past. 

166
00:09:41,280 --> 00:09:44,480
We all know that, right? 
So what were the challenges that

167
00:09:44,480 --> 00:09:48,600
you faced at Helena? 
Unexpected hurdles that arise 

168
00:09:48,600 --> 00:09:51,120
and throw the goal out. 
And how did you address them? 

169
00:09:52,040 --> 00:09:55,880
It's exactly what you said. 
The difficulty is all the things

170
00:09:55,880 --> 00:09:58,400
that we know from traditional 
change management. 

171
00:09:58,720 --> 00:10:02,200
If people need to change their 
habits, it's a hard thing to do,

172
00:10:02,200 --> 00:10:05,160
and people tend to focus on what
they lose and not on what they 

173
00:10:05,160 --> 00:10:08,040
gain. 
It helped, of course, that the 

174
00:10:08,040 --> 00:10:11,080
pain in the old system was 
really high. 

175
00:10:11,080 --> 00:10:16,080
The pain level was high and it 
was relatively easy once we 

176
00:10:16,080 --> 00:10:19,560
launched S4. 
The difference with what they 

177
00:10:19,560 --> 00:10:24,880
had experienced before that was 
very important, not to say 

178
00:10:24,880 --> 00:10:29,680
immense. 
So that helped tremendously in 

179
00:10:29,800 --> 00:10:35,200
the adoption of S4 by the users.
But that was of course after the

180
00:10:35,200 --> 00:10:37,800
go live. 
While we needed to prepare 

181
00:10:37,800 --> 00:10:42,280
before the Go live, all we could
do was remind people of all the 

182
00:10:42,280 --> 00:10:44,760
difficulties that they were 
going through with the old 

183
00:10:44,760 --> 00:10:47,920
system, how this would be solved
in the new system. 

184
00:10:47,920 --> 00:10:49,480
And that took a bit of a leap of
faith. 

185
00:10:49,840 --> 00:10:52,920
It wasn't always there. 
The faith was not always there. 

186
00:10:53,320 --> 00:10:56,840
But the best remedy or what you 
need to do in those 

187
00:10:56,840 --> 00:11:03,080
circumstances is communication. 
We had very regular, all staff 

188
00:11:03,080 --> 00:11:07,880
meetings where we discussed the 
progress, where we celebrated 

189
00:11:07,880 --> 00:11:11,160
little milestones when we could 
say, OK, now we've tested this 

190
00:11:11,160 --> 00:11:13,920
and it was successful. 
And these are the benefits that 

191
00:11:13,920 --> 00:11:16,080
you will live through once we go
live. 

192
00:11:16,400 --> 00:11:20,920
So layer by layer, we've been 
building up the confidence in 

193
00:11:20,920 --> 00:11:24,600
the new system by demonstrating 
in the test system how things 

194
00:11:24,600 --> 00:11:26,920
were going to work. 
And of course, you cannot 

195
00:11:26,920 --> 00:11:30,400
demonstrate everything in the 
test system, even only because 

196
00:11:30,400 --> 00:11:33,480
the test system is not loaded 
with all the information and all

197
00:11:33,480 --> 00:11:36,000
the data that we're going to use
in the actual production 

198
00:11:36,000 --> 00:11:39,000
environment. 
But for me, the keyword is 

199
00:11:39,000 --> 00:11:43,160
communication. 
One of the lessons learned is 

200
00:11:43,160 --> 00:11:47,160
that having one person 
responsible who is not 

201
00:11:47,160 --> 00:11:50,880
necessarily active in the 
project, but who is responsible 

202
00:11:50,880 --> 00:11:54,640
for the constant communication 
between the project and the rest

203
00:11:54,640 --> 00:11:59,360
of the organization is crucial. 
Back in the days when we were in

204
00:11:59,360 --> 00:12:03,000
the BYD adoption, we did not 
have that role. 

205
00:12:03,480 --> 00:12:06,600
Now in the S4 adoption, we 
installed that role. 

206
00:12:06,600 --> 00:12:09,520
We had one person from the 
marketing department who got the

207
00:12:09,520 --> 00:12:12,080
responsibility of keeping the 
communication between the 

208
00:12:12,080 --> 00:12:14,880
project and the rest of the 
organization flowing, and that 

209
00:12:14,880 --> 00:12:18,280
was a real asset. 
And that went through a monthly 

210
00:12:18,280 --> 00:12:23,120
newsletter, through ad hoc 
communications to announce small

211
00:12:23,120 --> 00:12:27,000
successes or difficulties. 
And like I said, once a month we

212
00:12:27,000 --> 00:12:30,280
had what we call the town hall 
meeting with all the staff where

213
00:12:30,280 --> 00:12:34,240
we gave an update not only on 
the S4 project but also on the 

214
00:12:34,400 --> 00:12:36,080
S4 project. 
OK. 

215
00:12:36,120 --> 00:12:37,920
That's interesting. 
With the person responsible, I'd

216
00:12:37,920 --> 00:12:39,720
like to dig just quickly into 
that. 

217
00:12:39,720 --> 00:12:42,920
Is it someone coming more from 
the IT or from the business 

218
00:12:42,920 --> 00:12:45,080
side? 
From the business side, OK, 

219
00:12:45,480 --> 00:12:47,320
actually from the organization 
side. 

220
00:12:47,360 --> 00:12:51,120
So in our case, we asked 
somebody from marketing who is 

221
00:12:51,120 --> 00:12:53,160
also responsible for external 
PR. 

222
00:12:53,440 --> 00:12:57,800
So somebody who is used to 
setting up good communication, 

223
00:12:57,880 --> 00:13:01,160
who is used to making positive 
stories, so to speak. 

224
00:13:01,160 --> 00:13:03,440
We had our own PR manager for 
the project. 

225
00:13:04,400 --> 00:13:07,680
OK, which seems to be a critical
key success factor in the 

226
00:13:07,680 --> 00:13:09,440
project. 
Yes. 

227
00:13:09,840 --> 00:13:12,600
Good. 
Let's have a look now at some 

228
00:13:12,600 --> 00:13:16,160
pathet of the IT landscape. 
Of course, these SAPS for an A 

229
00:13:16,160 --> 00:13:19,800
Cloud public edition system is 
part of a larger landscape where

230
00:13:20,000 --> 00:13:24,720
end to end process has to run. 
Can you discuss how well the 

231
00:13:24,720 --> 00:13:28,400
integration was achieved? 
What were the challenges and 

232
00:13:28,400 --> 00:13:31,560
recommendations to your peers 
when it comes to the larger 

233
00:13:31,560 --> 00:13:34,320
infrastructure and the systems 
that are connected and have to 

234
00:13:34,320 --> 00:13:38,440
work daily with SAPS for an A 
cloud public edition might be 

235
00:13:38,440 --> 00:13:39,320
interesting in your point of 
view. 

236
00:13:39,320 --> 00:13:41,720
Rafael as well, of course, the 
system integrator. 

237
00:13:42,680 --> 00:13:46,320
One big difference is that we 
included in the project BTP and 

238
00:13:46,480 --> 00:13:50,320
subcloud platform integration in
the landscape and that's allowed

239
00:13:50,360 --> 00:13:53,240
us to manage all the interface 
and not with point to point 

240
00:13:53,240 --> 00:13:55,480
interface like it was 
implemented in. 

241
00:13:55,480 --> 00:13:59,960
By design, it had even such a 
good effect that suddenly the 

242
00:13:59,960 --> 00:14:04,160
customer realized that they can 
also ask ATP check more easily 

243
00:14:04,160 --> 00:14:07,240
than the past to the points. 
And during one month, we had 

244
00:14:07,240 --> 00:14:12,440
more than 13 million call during
a single month, OK, which is 

245
00:14:12,440 --> 00:14:16,280
more or less five call per 
second just to request an ATP 

246
00:14:16,280 --> 00:14:19,120
check, which was a big surprise 
for us and of course had some 

247
00:14:19,120 --> 00:14:22,000
impact. 
But the positive things here is 

248
00:14:22,000 --> 00:14:26,560
that the system is even able to 
under such big workload and we 

249
00:14:26,560 --> 00:14:29,600
were able to monitor where all 
these calls are coming in the 

250
00:14:29,600 --> 00:14:32,760
system and so on and after to 
optimize a little bit the 

251
00:14:32,760 --> 00:14:36,880
solution to reduce the volume. 
But going with CPI was a key 

252
00:14:36,880 --> 00:14:40,240
factor we were able to 
integrate, but first to make the

253
00:14:40,240 --> 00:14:44,640
data migration using I flows and
using CPI we were able to 

254
00:14:44,640 --> 00:14:47,760
connect more efficiently the 
manufacturing facility which is 

255
00:14:47,760 --> 00:14:50,800
still running by design. 
And there is some information we

256
00:14:50,800 --> 00:14:54,920
couldn't get through standard 
interface from by design to by 

257
00:14:54,920 --> 00:14:57,040
design. 
Putting CPI in the middle 

258
00:14:57,040 --> 00:15:00,960
simplifies that and we connected
the B to B platform where 

259
00:15:00,960 --> 00:15:05,520
customer can put order directly 
in the system and I think 

260
00:15:05,520 --> 00:15:08,880
putting the middle way in place 
was a game changer for failing 

261
00:15:08,920 --> 00:15:09,720
out. 
OK. 

262
00:15:09,840 --> 00:15:11,560
Thanks, Rafael. 
Dick, do you want to comment 

263
00:15:11,600 --> 00:15:13,280
into out here? 
Yes. 

264
00:15:13,440 --> 00:15:16,080
Although I'm not a technical 
person so I can't give much of A

265
00:15:16,080 --> 00:15:21,200
technical explanation, but I 
know enough now of these SCPIS. 

266
00:15:21,200 --> 00:15:26,000
And that was an advice that Snap
gave us and really insisted on 

267
00:15:26,000 --> 00:15:28,920
putting those in place. 
And that has really been a game 

268
00:15:28,920 --> 00:15:32,760
changer for us because now all 
of a sudden the communication 

269
00:15:32,760 --> 00:15:36,280
between us and our external 
parties went smooth, whereas 

270
00:15:36,280 --> 00:15:42,160
before it had been a constant 
burden and a constant cause for 

271
00:15:42,200 --> 00:15:46,200
technical difficulties. 
Which also underlines that one 

272
00:15:46,200 --> 00:15:49,880
of the key SuccessFactors of a 
project like this is your 

273
00:15:49,880 --> 00:15:53,480
partner choice, the integrating 
partner that you want to work 

274
00:15:53,480 --> 00:15:56,040
with. 
It is extremely important to 

275
00:15:56,040 --> 00:15:59,040
make a good choice there and to 
make sure that you have somebody

276
00:15:59,040 --> 00:16:01,680
that not only understands the 
technical side, but also 

277
00:16:01,680 --> 00:16:04,320
understands your business and 
your setup and the goals that 

278
00:16:04,320 --> 00:16:07,160
you want to achieve. 
Because I've used the word 

279
00:16:07,160 --> 00:16:10,760
flexible focus for Felina 
before, but that is also 

280
00:16:10,760 --> 00:16:14,720
required from your partner. 
They may come in with a certain 

281
00:16:14,720 --> 00:16:17,960
vision, but then as they learn 
more about your business, as 

282
00:16:17,960 --> 00:16:22,080
they learn how you operate, they
also have to have some degree of

283
00:16:22,080 --> 00:16:24,800
flexibility to make sure that 
they can provide the solution 

284
00:16:24,800 --> 00:16:28,120
that is actually going to work 
in your day-to-day life and 

285
00:16:28,120 --> 00:16:30,120
every day-to-day requirements of
the business. 

286
00:16:30,640 --> 00:16:31,960
Good. 
Thank you, Derek for that. 

287
00:16:32,160 --> 00:16:35,320
We're approaching the end of the
podcast already, but I'd like 

288
00:16:35,640 --> 00:16:39,000
for both of you have a little 
reflection on the advices you 

289
00:16:39,000 --> 00:16:42,160
would like to give other 
companies who considering a 

290
00:16:42,160 --> 00:16:45,680
similar transition from SP by 
Design to SCPS SWANA Cloud 

291
00:16:45,680 --> 00:16:48,520
Public Edition, because this is 
a very particular context. 

292
00:16:48,960 --> 00:16:53,080
Maybe you want to stop Dick. 
Yes, I think there are four 

293
00:16:53,080 --> 00:16:55,640
points that I would like to 
touch on. 

294
00:16:56,200 --> 00:17:00,080
One, the pre work, the 
preparation before you actually 

295
00:17:00,080 --> 00:17:03,440
enter the project phase is 
extremely important. 

296
00:17:04,000 --> 00:17:07,599
So really understanding what are
the problems that you are facing

297
00:17:07,599 --> 00:17:11,079
today with DYD, which are the 
points that you would like to 

298
00:17:11,079 --> 00:17:16,400
see improved and making sure 
that S4 will actually solve 

299
00:17:16,400 --> 00:17:19,920
those issues. 
As I said in a previous podcast,

300
00:17:20,119 --> 00:17:23,760
we did our homework. 
We did not assume from day one 

301
00:17:23,760 --> 00:17:26,839
that we would transition from 
BYD to S4. 

302
00:17:27,040 --> 00:17:29,040
We really started with a blank 
slate. 

303
00:17:29,280 --> 00:17:32,920
But based on our needs and based
on the issues that we faced with

304
00:17:32,920 --> 00:17:37,040
BYD, it was clear for us that S4
would be the best solution and 

305
00:17:37,040 --> 00:17:40,200
that's why we decided to go with
S42. 

306
00:17:40,200 --> 00:17:43,840
What I just touched on the 
selection, the choice of your 

307
00:17:43,840 --> 00:17:47,680
partner is a key success factor 
to your project. 

308
00:17:48,080 --> 00:17:50,520
I've been through both sides of 
that coin. 

309
00:17:50,720 --> 00:17:53,440
I've worked with a partner that 
was not adequate for our 

310
00:17:53,440 --> 00:17:57,280
business and I've worked with 
one who was very adequate and we

311
00:17:57,280 --> 00:18:00,160
were extremely happy with the 
work and still are extremely 

312
00:18:00,160 --> 00:18:04,800
happy with the work that Snap 
has been doing for us. 3, making

313
00:18:04,800 --> 00:18:08,680
sure that you give enough 
resources to your projects 

314
00:18:08,680 --> 00:18:12,120
internally. 
It's very tempting to go with 

315
00:18:12,120 --> 00:18:16,280
the minimum set up because of 
course there's also the rest of 

316
00:18:16,280 --> 00:18:19,400
the business that needs to 
continue and you want to have as

317
00:18:19,400 --> 00:18:22,920
little disruption of the 
business as possible during the 

318
00:18:22,920 --> 00:18:25,920
project. 
It is a painful time when people

319
00:18:25,920 --> 00:18:29,280
have to wear 2 caps when they 
have to work in the business and

320
00:18:29,280 --> 00:18:33,080
also do the project work. 
It demands a lot of the people. 

321
00:18:33,320 --> 00:18:37,360
But this is one of the areas 
where you can be Pennywise and #

322
00:18:37,360 --> 00:18:39,800
foolish. 
Trying to save resources on the 

323
00:18:39,800 --> 00:18:43,800
project ultimately will bite you
back at the end of the project. 

324
00:18:44,280 --> 00:18:47,640
Either the solution will not be 
satisfying or you will not be 

325
00:18:47,640 --> 00:18:51,480
able to reach the deadlines, 
resulting both in a longer, more

326
00:18:51,480 --> 00:18:54,720
painful and more costly go life 
operation. 

327
00:18:55,240 --> 00:18:57,560
And last. 
I've used the word twice now 

328
00:18:57,560 --> 00:19:00,000
already. 
But the flexible focus is really

329
00:19:00,000 --> 00:19:02,640
important. 
Also, there is a plan when you 

330
00:19:02,640 --> 00:19:04,880
start. 
But like Norman Schwarzkopf used

331
00:19:04,880 --> 00:19:08,400
to say, the plan is nothing. 
Planning is everything. 

332
00:19:08,400 --> 00:19:11,400
So you have to be prepared 
during the project to review 

333
00:19:11,400 --> 00:19:14,840
your plan, maybe even review 
some of the requirements or some

334
00:19:14,840 --> 00:19:18,400
of the outcome if it's clear 
that not changing or not 

335
00:19:18,400 --> 00:19:22,960
adapting will give you a sub 
optimal solution in the end. 

336
00:19:23,480 --> 00:19:28,160
Sometimes that is hard, either 
for the organization or for the 

337
00:19:28,160 --> 00:19:30,640
partner. 
Nobody likes it when things 

338
00:19:30,640 --> 00:19:34,240
change when you are in flight, 
but both parties have to keep 

339
00:19:34,240 --> 00:19:37,160
that flexibility and accept that
this may happen during a 

340
00:19:37,160 --> 00:19:39,240
project. 
So those would be my four 

341
00:19:39,240 --> 00:19:43,160
critical SuccessFactors. 
Thank you, Dyac. 

342
00:19:43,280 --> 00:19:45,640
Rafael, what are your key 
SuccessFactors? 

343
00:19:45,640 --> 00:19:47,320
What would like to reflect on 
the journey? 

344
00:19:48,160 --> 00:19:51,520
Yuck mentioned most of them, but
I think what was very critical 

345
00:19:51,720 --> 00:19:54,640
is that we took the time to 
understand the female business 

346
00:19:54,640 --> 00:19:58,320
challenge and technical 
challenge and to find a solution

347
00:19:58,320 --> 00:20:01,000
together as a partner. 
And from the beginning we were 

348
00:20:01,000 --> 00:20:03,280
partner. 
We didn't guide anything. 

349
00:20:03,280 --> 00:20:05,960
When we had a challenge, we put 
them on the table. 

350
00:20:05,960 --> 00:20:08,080
And that was a very good 
environment. 

351
00:20:08,400 --> 00:20:11,240
And maybe what I can also say, 
and I know it's not necessarily 

352
00:20:11,240 --> 00:20:13,960
typical in the public cloud 
business, but we already had a 

353
00:20:13,960 --> 00:20:17,360
team dedicated for the lengths 
of the project to failing out. 

354
00:20:17,360 --> 00:20:18,960
They didn't focus on anything 
else. 

355
00:20:19,240 --> 00:20:21,720
And that allowed us to 
understand correctly the 

356
00:20:21,720 --> 00:20:24,520
business and the previous 
challenges the customer face in 

357
00:20:24,520 --> 00:20:26,120
order to provide the right 
solution. 

358
00:20:26,480 --> 00:20:27,600
OK. 
Thank you. 

359
00:20:27,720 --> 00:20:30,040
That was a great compliment 
though finally. 

360
00:20:30,040 --> 00:20:33,200
So looking ahead, what are the 
next step for the Felina 

361
00:20:33,200 --> 00:20:37,520
organization and leveraging the 
full potential of SCPS 1A cloud 

362
00:20:37,520 --> 00:20:40,440
public edition? 
So you're using a big bunch of 

363
00:20:40,440 --> 00:20:42,560
the scope, but not to the 
entirety. 

364
00:20:42,560 --> 00:20:48,120
So can you dear comment a bit on
the next step where the business

365
00:20:48,120 --> 00:20:52,640
will make more or run even more 
on the SAP application? 

366
00:20:53,560 --> 00:20:58,600
Looking forward, I think there's
two things that are still in the

367
00:20:58,600 --> 00:21:02,320
pipeline. 
They're not defined precisely in

368
00:21:02,320 --> 00:21:04,840
terms of the timing of when we 
are going to do this. 

369
00:21:05,240 --> 00:21:09,000
But one thing is that there are 
certain processes where we will 

370
00:21:09,040 --> 00:21:12,680
look to further automate because
some of the processes still 

371
00:21:12,680 --> 00:21:16,440
require quite a bit of human 
intervention and we believe 

372
00:21:16,440 --> 00:21:20,960
there are possibilities to 
relying more on the system than 

373
00:21:20,960 --> 00:21:25,360
we have done before. 
There has been traditionally a 

374
00:21:25,600 --> 00:21:30,240
tendency to control the system 
and keeping the possibility of 

375
00:21:30,240 --> 00:21:34,800
intervening in the processes. 
Now that the trust in the system

376
00:21:34,800 --> 00:21:38,920
has grown, we will take another 
step and let the system do more 

377
00:21:38,920 --> 00:21:40,840
than what we have done 
traditionally. 

378
00:21:40,960 --> 00:21:45,280
So that's one area. 
The second area is the 

379
00:21:45,280 --> 00:21:47,920
reporting. 
There is a lot of standard 

380
00:21:47,920 --> 00:21:51,840
reporting available in S4 and we
are still learning a lot in that

381
00:21:51,840 --> 00:21:55,120
area. 
But there are some specific 

382
00:21:55,120 --> 00:21:59,640
tailor made reports that we want
to build and that is something 

383
00:21:59,640 --> 00:22:04,480
that probably early next year, 
so early 2025 we will be 

384
00:22:04,480 --> 00:22:07,880
focusing on to develop more 
specific reporting. 

385
00:22:08,440 --> 00:22:13,160
And then in the far future we 
will probably do more in the 

386
00:22:13,200 --> 00:22:15,920
area of customer relationship 
management. 

387
00:22:15,920 --> 00:22:19,560
So the CRM is something that we 
will also be looking at to 

388
00:22:19,560 --> 00:22:21,840
develop that further. 
Thanks a lot. 

389
00:22:21,840 --> 00:22:24,960
I think these are very good 
closing words alike, especially 

390
00:22:24,960 --> 00:22:28,120
the trustee of the system and 
rely more on the system versus 

391
00:22:28,120 --> 00:22:31,920
try to control the system. 
Thanks a lot, dear, for spending

392
00:22:31,920 --> 00:22:34,560
this couple of minutes with us. 
Thanks to you as well, Rafael. 

393
00:22:34,600 --> 00:22:38,760
It's been a pleasure for me to 
reconnect with both of you and 

394
00:22:38,760 --> 00:22:41,840
thanks to you audience for 
joining this episode. 

395
00:22:41,960 --> 00:22:45,880
If you like it as much as I did,
even have ideas about the next 

396
00:22:45,880 --> 00:22:49,760
relevant topic for this podcast,
please just drop us a note at 

397
00:22:49,840 --> 00:22:55,480
insides4@sap.com. 
TuneIn next time and always be 

398
00:22:55,480 --> 00:22:57,720
inside SAP S4. 
Anna Cloud. 

399
00:22:58,160 --> 00:23:01,000
Thanks again, Derek and Raphael 
and hope to hear from you soon. 

400
00:23:01,000 --> 00:23:02,320
Bye. 
Bye. 

401
00:23:02,720 --> 00:23:03,200
Thanks guys.
