1
00:00:09,840 --> 00:00:13,240
Welcome to our podcast Inside 
SAP Svahana. 

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

3
00:00:17,440 --> 00:00:21,000
project success. 
In this episode we will talk 

4
00:00:21,000 --> 00:00:26,900
about Kwc's journey to Clouderp.
My name is Marcus Erteld and I'm

5
00:00:26,900 --> 00:00:30,740
happy to have two guests and 
experts on this podcast that 

6
00:00:30,740 --> 00:00:35,020
will share the experience today.
The first one is Manuel Flitstra

7
00:00:35,540 --> 00:00:38,700
from KWC. 
Hi Manu, How is it going today? 

8
00:00:39,540 --> 00:00:41,260
Hi, good morning all. 
Well here. 

9
00:00:41,300 --> 00:00:42,500
Thank you. 
Perfect. 

10
00:00:42,540 --> 00:00:43,900
Good to hear. 
Good morning to you. 

11
00:00:44,460 --> 00:00:48,740
And from SAP we have Giad Yan 
Dembour and Giad Yan. 

12
00:00:48,740 --> 00:00:51,060
How are you? 
I looked very well today. 

13
00:00:51,300 --> 00:00:55,460
I'm in the office and. 
It's Friday, so all good. 

14
00:00:56,100 --> 00:00:58,660
You can cover it. 
Friday and office sounds good 

15
00:00:58,660 --> 00:01:00,940
and we have a lovely SAP office 
in Zurich. 

16
00:01:02,180 --> 00:01:05,980
Let's go to you may know you 
bring a lot of experience from 

17
00:01:05,980 --> 00:01:08,580
the life science and consumer 
industries. 

18
00:01:08,580 --> 00:01:11,580
You are the head of group IT at 
KWC Group AG. 

19
00:01:11,580 --> 00:01:16,380
Maybe tell me a little bit about
yourself and who are you and 

20
00:01:16,460 --> 00:01:19,140
what makes you run? 
What makes me tick 

21
00:01:19,180 --> 00:01:21,610
professionally? 
Normally business 

22
00:01:21,610 --> 00:01:24,650
transformations, I have a 
background in business process 

23
00:01:24,650 --> 00:01:29,210
redesign in various companies 
like Rush, Biogen. 

24
00:01:29,570 --> 00:01:33,090
I started my career in the 
Netherlands with Philips and 

25
00:01:33,370 --> 00:01:38,850
Vopec for the last decades, 
involved in bigger technology 

26
00:01:38,850 --> 00:01:42,570
transformations and trying to 
make business processes more 

27
00:01:42,570 --> 00:01:47,230
efficient, more global, more 
harmonized and run better yet. 

28
00:01:47,230 --> 00:01:51,110
Jan, you are the SAP Business 
Architect for KWC in 

29
00:01:51,110 --> 00:01:54,590
Switzerland. 
I know personally that you like 

30
00:01:54,590 --> 00:01:58,150
camping and windsurfing and also
in the past you were heavily 

31
00:01:58,150 --> 00:02:01,230
involved in the asset and 
service intensive industries. 

32
00:02:02,070 --> 00:02:04,670
What else would you like to tell
our audience about yourself 

33
00:02:04,670 --> 00:02:05,910
today? 
Hi there. 

34
00:02:06,350 --> 00:02:08,110
I come like Manor from the 
Netherlands. 

35
00:02:08,630 --> 00:02:11,950
I live since more than 30 years 
in Switzerland and I'll be 

36
00:02:11,950 --> 00:02:14,950
working most of the time in the 
manufacturing industry. 

37
00:02:15,870 --> 00:02:18,950
So I have a business background.
I've been working in different 

38
00:02:18,950 --> 00:02:23,710
roles in business and IT sides 
in companies like ABB and Allsto

39
00:02:24,390 --> 00:02:29,630
and since five years I work as a
business architect in SB and I'm

40
00:02:29,630 --> 00:02:34,590
advising large enterprise. 
I have a business background in 

41
00:02:34,870 --> 00:02:39,830
different companies like ABB and
Allsto and I also work there in 

42
00:02:39,830 --> 00:02:41,190
different IT. 
Roles. 

43
00:02:41,830 --> 00:02:46,150
And since five years, I work as 
a business architect in SAP and 

44
00:02:46,150 --> 00:02:50,790
I advise large manufacturing 
companies like KWC with their 

45
00:02:50,790 --> 00:02:54,390
digital transformation. 
So we support with sharing 

46
00:02:54,390 --> 00:02:59,470
industry best practices, we help
to drive adoption of innovative 

47
00:02:59,470 --> 00:03:04,110
solutions moving into the cloud 
and we support with architect 

48
00:03:04,110 --> 00:03:07,870
topics in general. 
So it's a great fields to work 

49
00:03:07,870 --> 00:03:10,390
in. 
When we look at KWC, it has a 

50
00:03:10,390 --> 00:03:13,470
tradition. 
I mean this is amazing of 150 

51
00:03:13,470 --> 00:03:15,470
years when I went on the 
website. 

52
00:03:15,470 --> 00:03:17,870
I really like the value 
statement or the mission 

53
00:03:17,870 --> 00:03:21,870
statement values, hygiene, 
safety, sustainability and 

54
00:03:21,950 --> 00:03:24,270
enthusiasm. 
I have never seen that before, 

55
00:03:24,270 --> 00:03:26,910
but I really like that somehow I
found this really cool 

56
00:03:26,910 --> 00:03:30,540
enthusiasm. 
We have 3 divisions focusing on 

57
00:03:30,540 --> 00:03:33,700
home solutions. 
So here I was told you focus on 

58
00:03:33,700 --> 00:03:36,900
high quality bathrooms, showers,
kitchen fittings. 

59
00:03:36,940 --> 00:03:40,540
Then the second one is 
professional solutions, meaning 

60
00:03:40,620 --> 00:03:43,700
solutions for public and 
commercial sanitary rooms. 

61
00:03:44,260 --> 00:03:48,140
And the third one is I think 
also a promising 1 the medical 

62
00:03:48,140 --> 00:03:51,140
solutions. 
So premium products for the 

63
00:03:51,140 --> 00:03:54,220
healthcare sector where you 
probably face a strict 

64
00:03:54,220 --> 00:03:58,080
disinfection and hygiene 
regulations, man, or maybe you 

65
00:03:58,080 --> 00:04:02,280
can tell me a little bit more in
the year, I think it was 2021, 

66
00:04:02,320 --> 00:04:06,600
the KWC group became independent
after a divesture, is that 

67
00:04:06,600 --> 00:04:07,320
correct? 
Yeah. 

68
00:04:07,320 --> 00:04:13,280
Basically KWC was a division in 
Itvanka assists manufacturing 

69
00:04:13,880 --> 00:04:18,640
company the water business. 
KWC business was a business of 

70
00:04:18,640 --> 00:04:24,000
around 200, two 150 million with
around 1100 people globally. 

71
00:04:24,280 --> 00:04:26,840
That business was sold in May 
2021. 

72
00:04:27,470 --> 00:04:31,070
And decided at that moment in 
time to fully separated company.

73
00:04:31,070 --> 00:04:36,510
By the end of 2021 all decisions
regarding IT had been taken. 

74
00:04:36,790 --> 00:04:39,590
That was also the moment that I 
joined. 

75
00:04:39,870 --> 00:04:43,510
So it was decided to do the 
carve out as you called it, the 

76
00:04:43,510 --> 00:04:48,070
separation of KWC from the 
mother company which completely 

77
00:04:48,070 --> 00:04:50,710
new business applications all in
clouds. 

78
00:04:50,710 --> 00:04:54,470
So that means. 
The European clouds CREM in 

79
00:04:54,470 --> 00:04:59,030
clouds, PDM in clouds, marketing
systems in clouds and of course 

80
00:04:59,030 --> 00:05:01,990
as always with the carve out of 
course on an infrastructure 

81
00:05:02,190 --> 00:05:05,710
which happened to be also 
completely cloud based with 

82
00:05:05,710 --> 00:05:10,430
Microsoft 365 in the cloud and 
Azure servers either on premise 

83
00:05:10,430 --> 00:05:14,910
or in cloud. 
And we basically we had to do 

84
00:05:14,910 --> 00:05:22,230
that carve out up until November
last year. 2022, so basically, 

85
00:05:22,230 --> 00:05:26,710
we developed those applications,
we integrated those applications

86
00:05:27,070 --> 00:05:31,590
and we switched it all in clouds
in approximately 9 months. 

87
00:05:32,030 --> 00:05:35,390
If you take into account that we
have manufacturing in China, 

88
00:05:35,390 --> 00:05:40,030
Middle East, Germany, 
Switzerland, UK and Finland, 

89
00:05:40,030 --> 00:05:45,470
that was quite a job and not 
only from an ERP, so as a P ERP 

90
00:05:45,590 --> 00:05:48,610
cloud perspective. 
But also from the perspective 

91
00:05:48,610 --> 00:05:53,650
that we had to integrate it with
new PDM, CRM and HR, 

92
00:05:53,650 --> 00:05:58,050
SuccessFactors and Marketing 
Applications, we succeeded in in

93
00:05:58,050 --> 00:06:00,290
doing that. 
So everything was done by 

94
00:06:00,290 --> 00:06:04,970
November 2022. 
So roughly a year from start, 

95
00:06:04,970 --> 00:06:10,130
which was in Q 4/20/21, 
everything was separated and all

96
00:06:10,130 --> 00:06:13,530
the transaction service 
agreements between KWC and 

97
00:06:13,530 --> 00:06:15,970
Franca on the IT sides were 
finished. 

98
00:06:16,540 --> 00:06:19,620
We had established an old 
support organization, heavily 

99
00:06:19,620 --> 00:06:24,180
outsourced of course fully live 
and kicking for the new business

100
00:06:24,660 --> 00:06:26,460
of course the last couple of 
months. 

101
00:06:26,740 --> 00:06:29,740
So we're now talking summer 
2023. 

102
00:06:30,220 --> 00:06:33,500
We spent another six months on 
further maturing our 

103
00:06:33,500 --> 00:06:39,820
organization, our processes and 
putting the dots on the eye and 

104
00:06:39,820 --> 00:06:43,100
crossing the T's and that's 
where we are right now. 

105
00:06:44,180 --> 00:06:47,680
Impressive menu when I go to 
Kiatian quickly. 

106
00:06:47,720 --> 00:06:50,400
When did you get involved in? 
What was your role when you 

107
00:06:50,400 --> 00:06:54,160
started to advise KWC? 
During the beginning times after

108
00:06:54,160 --> 00:06:58,000
the car filed or divisor. 
So I joined advising. 

109
00:06:58,000 --> 00:07:04,920
KWC early 2022 after the Aswana 
project started and we have been

110
00:07:04,920 --> 00:07:07,000
working since with Mano and his 
team. 

111
00:07:07,680 --> 00:07:11,560
So what we do is we support with
growing business requirements 

112
00:07:11,880 --> 00:07:14,680
and for those additional 
requirements which cannot be 

113
00:07:14,680 --> 00:07:17,970
solved. 
Within the ERP core, we help 

114
00:07:17,970 --> 00:07:21,570
with additional solutions. 
For example, if we help to 

115
00:07:21,570 --> 00:07:26,290
implement signature for business
process management to analyze 

116
00:07:26,290 --> 00:07:31,970
and to document the processes 
and also like sub analytics 

117
00:07:32,250 --> 00:07:37,810
cloud, we help to get insights 
into the data of Kdboc and 

118
00:07:37,810 --> 00:07:40,970
improve also the reporting 
capabilities. 

119
00:07:42,170 --> 00:07:47,050
We to To achieve this we have 
weekly meetings where we discuss

120
00:07:47,250 --> 00:07:50,890
strategic topics but also 
sometimes operational topics 

121
00:07:51,370 --> 00:07:54,250
like with S for HANA the Co 
lives. 

122
00:07:55,210 --> 00:07:58,770
We also have a regular quarterly
business reviews. 

123
00:07:59,010 --> 00:08:02,810
We had one yesterday where we 
were on site in the. 

124
00:08:02,850 --> 00:08:06,970
Unto com in. 
The office of KWC and the 

125
00:08:06,970 --> 00:08:10,850
highlight for me was we did the 
factory visit where I could see 

126
00:08:10,850 --> 00:08:15,410
end to end. 
From a roll bar of metal until 

127
00:08:15,450 --> 00:08:19,450
the finished good full KWC 
leaving the factory. 

128
00:08:19,610 --> 00:08:23,130
So this was a was a great 
experience to see the end to end

129
00:08:23,290 --> 00:08:28,570
process in real time and so it's
cool Factory Visitors is always 

130
00:08:28,690 --> 00:08:33,010
good menu. 
You finished the big as a PS1 

131
00:08:33,010 --> 00:08:35,049
and cloud public edition 
implementation. 

132
00:08:35,049 --> 00:08:38,610
You told us already a little bit
about your key processes, your 

133
00:08:38,610 --> 00:08:42,120
localizations. 
Not so much about the project 

134
00:08:42,120 --> 00:08:46,120
setup yet, but maybe you can 
share more insights about your 

135
00:08:46,120 --> 00:08:49,840
learnings and what you learned. 
Or if I would be the CIO and I 

136
00:08:49,840 --> 00:08:52,000
would have been in your role, 
how did you do it? 

137
00:08:52,000 --> 00:08:54,520
What else did you learn? 
How did you set it up? 

138
00:08:54,920 --> 00:08:59,160
I must say our project was 
simply time boxed, so failure 

139
00:08:59,160 --> 00:09:02,360
was not an option. 
The date of the 1st of November 

140
00:09:02,360 --> 00:09:05,830
was firm. 
So that is one topic. 

141
00:09:05,830 --> 00:09:10,110
So also for businesses, it was 
clear that we had to harmonize 

142
00:09:10,110 --> 00:09:13,430
our business and that we had to 
go to the change management and 

143
00:09:13,430 --> 00:09:17,350
that we had to implement those 
systems by November 1st. 

144
00:09:18,590 --> 00:09:23,390
What we did is we started with a
process harmonization effort by 

145
00:09:23,390 --> 00:09:27,310
the end of 2021. 
Formerly I was not on boarded 

146
00:09:27,510 --> 00:09:31,590
yet at that moment in time. 
So that's basically defined the 

147
00:09:31,590 --> 00:09:36,170
standard business processes. 
And harmonize matters across 

148
00:09:36,330 --> 00:09:39,530
ERP, product development, 
customer relationship 

149
00:09:39,530 --> 00:09:43,130
management. 
In 2022 when we started the 

150
00:09:43,130 --> 00:09:45,730
implementation, we sticked to 
that standard. 

151
00:09:45,730 --> 00:09:49,730
That was one thing, but we also 
implemented a project according 

152
00:09:49,730 --> 00:09:55,970
to a Pathfinder methodology. 
So basically two or 231 big 

153
00:09:55,970 --> 00:09:59,050
sites and two smaller sites 
where the Pathfinder for the 

154
00:09:59,050 --> 00:10:02,750
implementation. 
So we focused all implementation

155
00:10:02,750 --> 00:10:06,950
efforts initially on those 3 
Pathfinder sites. 

156
00:10:06,950 --> 00:10:09,910
Those were Germany, Austria and 
Middle East. 

157
00:10:10,270 --> 00:10:14,790
And we focused all resources on 
the implementations for these 

158
00:10:14,790 --> 00:10:17,790
sites. 
And we also enhanced the system.

159
00:10:18,310 --> 00:10:21,590
When that was done, we did the 
lessons learned and we 

160
00:10:21,590 --> 00:10:25,470
implemented the system more 
quickly and in a more standard 

161
00:10:25,470 --> 00:10:32,140
way in Scandinavia in the UK. 
And in other parts of Germany, 

162
00:10:32,540 --> 00:10:35,860
that was also the moment that we
decided to postpone the 

163
00:10:35,860 --> 00:10:38,540
implementation of Switzerland. 
We could. 

164
00:10:39,100 --> 00:10:42,140
So in all honesty we did that 
actually at the beginning of 

165
00:10:42,140 --> 00:10:45,380
this year, but also from a carve
out perspective that was 

166
00:10:45,380 --> 00:10:48,700
possible. 
Another topic which was really 

167
00:10:48,700 --> 00:10:51,460
important for us is the whole 
data migration. 

168
00:10:51,980 --> 00:10:55,060
We started with the data 
migration from the beginning of 

169
00:10:55,060 --> 00:10:59,020
the project, but I think we did 
not give it enough focus. 

170
00:10:59,530 --> 00:11:02,890
So during the Pathfinder 
project, it was all hands on 

171
00:11:02,890 --> 00:11:06,210
deck, especially from a data 
migration perspective. 

172
00:11:07,050 --> 00:11:12,490
And we fine-tuned the data 
transition conversion approaches

173
00:11:12,570 --> 00:11:16,930
after Pathfinder and I think 
it's only at the end of the 

174
00:11:16,930 --> 00:11:20,050
program that we really got it 
right in terms of data 

175
00:11:20,050 --> 00:11:22,170
migration. 
So one of the lessons learned 

176
00:11:22,570 --> 00:11:25,050
from me on this implementation 
is. 

177
00:11:25,450 --> 00:11:28,410
Harmonization and 
standardization possible, user 

178
00:11:28,410 --> 00:11:33,330
adoption, training possible, 
research, time frame integration

179
00:11:33,370 --> 00:11:37,250
possible, but data migration, 
data conversion, data 

180
00:11:37,250 --> 00:11:40,530
transition, we should have 
addressed that much earlier. 

181
00:11:41,330 --> 00:11:45,450
Of course, it is the case that I
said already that over the last 

182
00:11:45,450 --> 00:11:50,530
half year we have been further 
maturing our systems management 

183
00:11:51,010 --> 00:11:54,650
still user adoption into company
processes. 

184
00:11:55,050 --> 00:11:59,970
So it is not the case that in 
November 2021 everything was 

185
00:12:00,010 --> 00:12:03,010
completely finalized. 
There was still a lot of work to

186
00:12:03,010 --> 00:12:07,090
be done also afterwards. 
Very understood and good message

187
00:12:07,130 --> 00:12:10,570
from you. 
Before this podcast I when I 

188
00:12:10,570 --> 00:12:13,330
looked at the three divisions I 
saw the Medical Solutions 

189
00:12:13,330 --> 00:12:18,570
division that you have to handle
regulations from governmental 

190
00:12:18,570 --> 00:12:22,450
agencies or customers of yours 
with SPS on a cloud public 

191
00:12:22,450 --> 00:12:23,890
edition. 
Yeah. 

192
00:12:24,010 --> 00:12:28,250
After the Pathfinder project to 
which was excluding Medical, we 

193
00:12:28,250 --> 00:12:31,610
focused after that on the 
implementation also for Medical 

194
00:12:31,610 --> 00:12:34,290
And there yeah, the compliance 
requirements are somewhat 

195
00:12:34,290 --> 00:12:37,450
stricter. 
That was taken into account and 

196
00:12:37,450 --> 00:12:42,050
I must say you asked earlier to 
as a P where did you contribute 

197
00:12:42,250 --> 00:12:45,290
to this customer. 
I think the contribution there 

198
00:12:45,290 --> 00:12:49,530
also specifically for Medical is
that as a P assisted. 

199
00:12:50,080 --> 00:12:54,240
In finding the adequate 
functionality in ERP cloud also 

200
00:12:54,240 --> 00:12:56,960
for medical but also for our 
manufacturing business, of 

201
00:12:56,960 --> 00:12:59,280
course we go to a lot of help 
there. 

202
00:12:59,880 --> 00:13:04,640
FT John was explaining about 
factory visits actually already 

203
00:13:04,920 --> 00:13:07,560
much earlier. 
The as a P team for Waldorf 

204
00:13:07,560 --> 00:13:12,200
visited outside and looked at 
some of the specifics which were

205
00:13:12,200 --> 00:13:16,320
needed for our manufacturing 
implementation and I must say we

206
00:13:16,320 --> 00:13:20,440
got quite some support. 
From the SAP team, how we could 

207
00:13:20,440 --> 00:13:24,200
make best use of some of the 
functionalities which were 

208
00:13:24,200 --> 00:13:27,320
sometimes not there or not 
completely there, but there were

209
00:13:27,320 --> 00:13:30,720
alternatives. 
In your question was around 

210
00:13:30,720 --> 00:13:34,920
medical, also in the business 
technology platform and the 

211
00:13:34,920 --> 00:13:38,800
integration and reporting to 
authorities, but also the 

212
00:13:38,800 --> 00:13:41,280
integration in the product data 
management. 

213
00:13:41,720 --> 00:13:45,240
Also there on the BTP side, 
we're getting good support of 

214
00:13:45,240 --> 00:13:48,650
SAP. 
Also for the more complex 

215
00:13:48,650 --> 00:13:53,650
resolutions needed for medical, 
also in the medical domain of 

216
00:13:53,650 --> 00:13:57,490
course the EFP clouds as such is
not enough. 

217
00:13:57,610 --> 00:14:02,250
You need a good integration with
employee data, you need a good 

218
00:14:02,250 --> 00:14:07,250
integration with service 
management specifically and also

219
00:14:07,250 --> 00:14:10,170
that integration. 
We got quite some support from 

220
00:14:10,170 --> 00:14:14,450
SAP in setting up that 
integration and that integrated 

221
00:14:14,650 --> 00:14:17,930
set of systems that. 
Covered all the medical 

222
00:14:17,930 --> 00:14:25,210
requirements we had to comply to
in the September October 2022 

223
00:14:25,210 --> 00:14:27,890
time frame. 
Let's move a little bit to a 

224
00:14:27,890 --> 00:14:32,290
different topic, maybe the 
aspect of extensibility Did you 

225
00:14:32,290 --> 00:14:36,050
handle or how did you handle it?
Did you even need to extend the 

226
00:14:36,050 --> 00:14:38,970
solution? 
Yeah, I must say there's of 

227
00:14:38,970 --> 00:14:43,850
course the SAP strategy and SAP 
strategy is extensibility in a 

228
00:14:43,850 --> 00:14:48,200
three tier landscape. 
Unfortunately we are in a 2 tier

229
00:14:48,200 --> 00:14:52,680
landscape and we cannot yet 
migrate to the three tier 

230
00:14:52,680 --> 00:14:56,440
landscape in which you have more
possibilities to make changes. 

231
00:14:56,920 --> 00:15:01,440
I must say if you look at our 
implementation in terms of 

232
00:15:01,440 --> 00:15:06,360
integration and interfaces, we 
have about 25 systems we 

233
00:15:06,360 --> 00:15:09,940
interface and integrate with. 
And it goes from automated 

234
00:15:09,940 --> 00:15:14,940
warehouses to Threepl solutions 
to payroll solutions to the 

235
00:15:14,940 --> 00:15:20,340
integration of SAP itself with 
SuccessFactors and C for C So in

236
00:15:20,340 --> 00:15:25,660
terms of often extensibility and
integration are under 1 header. 

237
00:15:26,100 --> 00:15:30,460
In terms of the integration over
the BTP platform, that is 

238
00:15:30,460 --> 00:15:35,690
definitely working. 
We made some modifications to 

239
00:15:35,690 --> 00:15:39,010
the EP cloud system, so we 
apparently we were able to do 

240
00:15:39,010 --> 00:15:41,970
so. 
There's also requirements to 

241
00:15:41,970 --> 00:15:47,010
extend more and to make more 
dedicated solutions for KWCI 

242
00:15:47,010 --> 00:15:51,650
must say that is not possible 
yet and we're definitely waiting

243
00:15:51,730 --> 00:15:55,930
to step in that era of three 
tier where I in my view the 

244
00:15:55,930 --> 00:15:59,290
extensibility and the 
possibility for changes are 

245
00:15:59,290 --> 00:16:02,530
bigger. 
On the other hand, I have to say

246
00:16:02,530 --> 00:16:06,370
given the fact that our time 
frames where we implemented for 

247
00:16:06,610 --> 00:16:11,010
this 1100 employee company a 
mini global manufacturer I call 

248
00:16:11,010 --> 00:16:13,930
ourselves, we had to do that in 
a year. 

249
00:16:14,170 --> 00:16:17,850
And the fact that we have had to
stick to standard processes 

250
00:16:18,010 --> 00:16:21,650
helped us also a lot in 
convincing business, hey, you 

251
00:16:21,650 --> 00:16:24,890
have to harmonize and stick to 
this best business practices. 

252
00:16:25,340 --> 00:16:29,180
There's only a couple of domains
where I would say coming from an

253
00:16:29,180 --> 00:16:33,060
ECC background over the last 
decades, I would say yeah, there

254
00:16:33,060 --> 00:16:35,300
this functionality. 
That's a pity that we don't have

255
00:16:35,300 --> 00:16:37,700
it. 
Maybe this would be a different 

256
00:16:37,700 --> 00:16:41,420
podcast or maybe we can go out 
and have a beer and you can talk

257
00:16:41,420 --> 00:16:45,980
me about it and then can see if 
we can bring those requirements 

258
00:16:45,980 --> 00:16:49,940
also in the cloud. 
You touched on the integration 

259
00:16:49,940 --> 00:16:52,660
part. 
I know from Get Young there were

260
00:16:53,170 --> 00:16:55,290
big question mark about the 
third party logistics 

261
00:16:55,290 --> 00:16:58,890
integration before this project,
the implementation started. 

262
00:16:59,250 --> 00:17:01,530
I don't know who wants to take 
it but Get Young or Meno. 

263
00:17:01,850 --> 00:17:05,290
How did it go in the end? 
That was basically innovation 

264
00:17:05,290 --> 00:17:09,770
based on EOP clouds. 
So we in November last year, as 

265
00:17:09,770 --> 00:17:13,970
I told we had implemented this 
EOP cloud solution in all these 

266
00:17:13,970 --> 00:17:18,210
countries and then the request 
came as still up is. 

267
00:17:18,569 --> 00:17:22,050
We would like to outsource our 
logistics processes to a third 

268
00:17:22,050 --> 00:17:26,530
party logistics provider as we 
started the project in November 

269
00:17:26,810 --> 00:17:32,050
to specify the division of Labor
between this new threepl in this

270
00:17:32,050 --> 00:17:35,810
case and ourselves. 
And actually that division of 

271
00:17:35,810 --> 00:17:39,890
Labor is standard EP, standard 
threepl integration between a 

272
00:17:39,890 --> 00:17:44,730
manufacturer and a threepl we 
implemented or we specified. 

273
00:17:45,190 --> 00:17:49,190
Those processes we agreed with 
the 3PL on the separation of 

274
00:17:49,190 --> 00:17:53,590
activities and duties on the 
separation of systems and 

275
00:17:53,590 --> 00:17:58,230
implemented this functionality 
with yet another implementation 

276
00:17:58,230 --> 00:18:01,510
partner and that was quite a 
success. 

277
00:18:02,190 --> 00:18:05,670
This project starts to November.
The three PL. outsourcing. 

278
00:18:05,670 --> 00:18:09,070
We're talking about multiple 
locations in Germany, 

279
00:18:09,070 --> 00:18:14,070
Switzerland, Austria. 
Also goods coming in from the 

280
00:18:14,070 --> 00:18:16,730
Middle East. 
And that project took from 

281
00:18:16,730 --> 00:18:21,570
November up until March when we 
also moved the warehouses in the

282
00:18:21,570 --> 00:18:24,530
month of February. 
So all the warehouse, all the 

283
00:18:24,530 --> 00:18:27,890
inventory was moved. 
The warehouse in Southern 

284
00:18:27,890 --> 00:18:32,650
Germany was switched on. 
Also the whole integration via 

285
00:18:32,650 --> 00:18:36,810
BTP was set up. 
And this project went really, 

286
00:18:36,810 --> 00:18:39,690
really smooth. 
Yeah, you basically see that 

287
00:18:39,690 --> 00:18:41,930
this whole application 
infrastructure that you can 

288
00:18:41,930 --> 00:18:45,520
build on it and innovate. 
Without too many issues. 

289
00:18:45,720 --> 00:18:48,680
We also did it with the 2nd 
implementation partner. 

290
00:18:49,000 --> 00:18:52,280
So that is also good that we now
have that multi vendor approach 

291
00:18:52,280 --> 00:18:55,360
implemented. 
We get a lot of compliments from

292
00:18:55,360 --> 00:18:57,320
business that it went so 
smoothly. 

293
00:18:58,280 --> 00:19:02,880
And also if I look now at the 
number of tickets incidents and 

294
00:19:02,880 --> 00:19:07,200
problems with this innovation 3P
L, it's very limited. 

295
00:19:07,200 --> 00:19:13,080
I think we have below 5 priority
three issues every two weeks, 

296
00:19:13,080 --> 00:19:16,230
but that's it. 
I'm happy it went well at the 

297
00:19:16,230 --> 00:19:18,630
end. 
We talked a lot about today 

298
00:19:18,670 --> 00:19:22,190
implementation, extensibility, 
data migration already was 

299
00:19:22,190 --> 00:19:24,270
touched. 
But I know Manu, you're also a 

300
00:19:24,270 --> 00:19:27,950
business guy. 
How does your business rate the 

301
00:19:27,950 --> 00:19:30,150
user experience? 
With SAPS file and cloud public 

302
00:19:30,150 --> 00:19:32,190
edition? 
How happy is your business? 

303
00:19:33,030 --> 00:19:36,150
We came from a situation with 9 
ERP systems. 

304
00:19:36,870 --> 00:19:39,830
Some of them were SAP, some of 
them were non SAP. 

305
00:19:40,670 --> 00:19:45,590
The former SAP ERP users 
recognize the processes and SAP 

306
00:19:45,590 --> 00:19:50,390
support in the ERP cloud system.
You still see the old ECC 

307
00:19:50,390 --> 00:19:54,030
functionalities and where they 
are available and where not. 

308
00:19:54,430 --> 00:19:59,390
So that went in that from a 
process perspective, well after 

309
00:19:59,390 --> 00:20:03,710
implementation there also for 
the SAP people were used to SAP,

310
00:20:03,750 --> 00:20:07,590
there was a lot of training 
necessary and a lot of user 

311
00:20:07,590 --> 00:20:11,600
adoption had to take place. 
I would say on average it's took

312
00:20:11,600 --> 00:20:16,480
the organizations about six 
months to really give a thumbs 

313
00:20:16,480 --> 00:20:18,800
up. 
Yeah, everything is working 

314
00:20:18,800 --> 00:20:21,680
fine, perfect, and we're happy 
with the system. 

315
00:20:22,080 --> 00:20:26,840
But the Pathfinder project, 
which was implemented around the

316
00:20:26,840 --> 00:20:32,200
1st of September, gives all 
middle management gave a kind of

317
00:20:32,240 --> 00:20:34,400
thumbs up, let's say six months 
later. 

318
00:20:35,120 --> 00:20:38,640
So that was early this year. 
There were also differences in 

319
00:20:38,640 --> 00:20:41,840
China. 
It was very smooth and a good 

320
00:20:41,840 --> 00:20:46,480
usage of the system in the 
Middle East, verbally a lot of 

321
00:20:46,480 --> 00:20:51,040
approval, but still people had 
difficulty doing intercompany 

322
00:20:51,280 --> 00:20:54,800
processes etcetera. 
In Germany, there were quite 

323
00:20:54,800 --> 00:20:57,920
some discussions and we started 
after implementation with a 

324
00:20:57,920 --> 00:21:01,960
little bit of business backlog, 
but that was covered within, I 

325
00:21:01,960 --> 00:21:06,330
would say within four weeks. 
Now I go to the non SAP 

326
00:21:06,570 --> 00:21:10,610
experience to user organization 
for them it was really 

327
00:21:10,610 --> 00:21:12,370
difficult. 
That organization was in 

328
00:21:12,370 --> 00:21:15,250
Switzerland. 
I don't know if it's also 

329
00:21:15,250 --> 00:21:20,490
culturally related, but our 
Swiss organization and that is 

330
00:21:20,490 --> 00:21:24,330
one of our main manufacturing 
sites is in my view really 

331
00:21:24,330 --> 00:21:27,650
struggling with the system and 
user adoption. 

332
00:21:27,650 --> 00:21:31,410
The system is working perfectly,
but has it been designed 

333
00:21:31,410 --> 00:21:34,770
adequately, have those 
discussions being done 

334
00:21:34,810 --> 00:21:39,090
adequately, question mark, can 
all people now work with the 

335
00:21:39,090 --> 00:21:41,770
processes? 
It's also still difficult. 

336
00:21:42,130 --> 00:21:46,370
So the last implementation for 
Switzerland was done in April, 

337
00:21:46,930 --> 00:21:49,970
but also three months later, 
we're still having small 

338
00:21:49,970 --> 00:21:55,130
business backlog and we are 
still evaluating are the 

339
00:21:55,130 --> 00:21:59,450
processes now designed optimally
and what else can we do in order

340
00:21:59,450 --> 00:22:04,160
to help the end users there. 
We are still struggling. 

341
00:22:04,480 --> 00:22:08,600
Our forecast is that we get the 
business backlog sorted in the 

342
00:22:08,600 --> 00:22:14,120
next month and after that is 
done that we then evaluate let's

343
00:22:14,120 --> 00:22:17,200
say warehousing strategies, 
picking strategies. 

344
00:22:17,840 --> 00:22:21,720
So there will be a lessons 
learned session on the design 

345
00:22:21,720 --> 00:22:23,520
and the efficiencies of the 
system. 

346
00:22:24,950 --> 00:22:28,750
Yes, Young US trusted advisor 
saw the change management 

347
00:22:28,750 --> 00:22:32,630
process at KWC doing and before 
the implementation. 

348
00:22:33,350 --> 00:22:35,990
What did you see? 
And can you also advise other 

349
00:22:35,990 --> 00:22:38,270
customers wanting to convert to 
Srps? 

350
00:22:38,270 --> 00:22:41,350
One or cloud public edition? 
It's also an interesting. 

351
00:22:41,390 --> 00:22:43,910
Theory like whether explained 
there were some challenges with 

352
00:22:43,910 --> 00:22:46,910
change management and with 
adoption, but I think that's 

353
00:22:46,910 --> 00:22:51,520
normal for any bigger company. 
In a nutshell, as far as cloud 

354
00:22:51,520 --> 00:22:56,080
publication is really a greater 
flexible solution which you can 

355
00:22:56,720 --> 00:23:00,640
integrate easily with, 
especially with SAP solutions. 

356
00:23:01,320 --> 00:23:06,440
And this is a great jump start 
for any company the size of KWC.

357
00:23:07,400 --> 00:23:09,320
But it's supported to do the 
right things. 

358
00:23:09,320 --> 00:23:12,320
So you have to clean up your 
processes, you have to 

359
00:23:12,480 --> 00:23:16,560
streamline and you have to adopt
the best practices of SAP. 

360
00:23:17,470 --> 00:23:20,830
So in each and every location 
where you go live, you have the 

361
00:23:20,830 --> 00:23:24,390
typical challenge that people 
say why should I work a bit 

362
00:23:24,390 --> 00:23:28,390
different than I did before in 
my previous SAP system or not 

363
00:23:28,470 --> 00:23:32,870
SAP system. 
And this is just a process which

364
00:23:32,910 --> 00:23:37,670
cannot be shortcut too much like
you can train the people, you 

365
00:23:37,670 --> 00:23:39,990
can build up a key user 
organization. 

366
00:23:40,310 --> 00:23:43,910
But in the end each and every 
end user must be trained and 

367
00:23:43,910 --> 00:23:47,710
explained how we. 
Has to use the new system. 

368
00:23:49,070 --> 00:23:53,030
What is nice is that the 
standard functionalities and 

369
00:23:53,030 --> 00:23:57,550
standard integration make it 
easier to adopt new areas. 

370
00:23:57,590 --> 00:24:00,830
Like at the moment we are 
discussing how can we support 

371
00:24:00,830 --> 00:24:03,390
KWC in the area of 
sustainability. 

372
00:24:03,950 --> 00:24:08,950
So there's several areas like 
the ESC reporting or the plastic

373
00:24:08,950 --> 00:24:13,950
taxes or the bottle up CO2 
calculations. 

374
00:24:14,540 --> 00:24:18,620
And these are areas where we 
have solutions which can be 

375
00:24:18,620 --> 00:24:22,180
integrated with as follow out of
the books. 

376
00:24:22,540 --> 00:24:26,260
So these are areas which we are 
discussing at the moment and in 

377
00:24:26,260 --> 00:24:30,620
the next few months. 
Good Young, you already touched 

378
00:24:30,620 --> 00:24:33,660
a little bit on it. 
Maybe it's also interesting for 

379
00:24:33,660 --> 00:24:37,150
our listeners. 
US Architect How do you identify

380
00:24:37,150 --> 00:24:39,830
solutions of value for your 
customers? 

381
00:24:39,910 --> 00:24:42,990
How do you go about it and how 
do you know it's the right 

382
00:24:42,990 --> 00:24:44,830
solution? 
It's like I mentioned in the 

383
00:24:44,830 --> 00:24:49,830
beginning, I joined K Do we see 
one out here ago and we have 

384
00:24:50,430 --> 00:24:54,150
weekly operational meetings 
about S for HALA and then I'll 

385
00:24:54,150 --> 00:24:55,350
listen in. 
What's going on? 

386
00:24:55,350 --> 00:24:57,710
What's the discussions? 
Where are the pain points? 

387
00:24:58,400 --> 00:25:03,880
And we also have set up biweekly
strategic goals with Mano and 

388
00:25:03,880 --> 00:25:07,240
his direct team. 
And here we discussed strategic 

389
00:25:07,240 --> 00:25:10,000
topics. 
So we say OK, what's the law to 

390
00:25:10,000 --> 00:25:12,920
review of cater. 
We'll see what's the kind of 

391
00:25:13,080 --> 00:25:18,440
areas you want to evolve in like
eco strategy or like what do you

392
00:25:18,440 --> 00:25:22,320
want to do in the area of 
procurement or how do you want 

393
00:25:22,320 --> 00:25:25,600
to continue with track your 
automation for example. 

394
00:25:26,470 --> 00:25:29,030
And then if you see that there 
is, it's the right timing and 

395
00:25:29,030 --> 00:25:33,230
there's an interest, then I talk
to the experts in SFP and we set

396
00:25:33,230 --> 00:25:38,270
up an initial call, So we reset 
certain solutions say this is 

397
00:25:38,270 --> 00:25:42,790
the benefits that is how we 
could start using it in KWC and 

398
00:25:42,790 --> 00:25:48,190
then step by step we extend the 
IT landscape of WC with 

399
00:25:48,190 --> 00:25:52,790
additional solutions. 
So that's with how we approach 

400
00:25:52,790 --> 00:25:54,870
it. 
And for example, yesterday we. 

401
00:25:55,260 --> 00:25:58,420
We had this quarterly business 
review with a wider team of 

402
00:25:58,420 --> 00:26:03,340
people and then we also agreed 
that we want to have a deep dive

403
00:26:03,380 --> 00:26:05,900
on the BDP with a wider 
community. 

404
00:26:06,540 --> 00:26:10,500
It is already in use at the KWC,
but there's a lot of potential 

405
00:26:10,500 --> 00:26:13,860
to smoothen the existing 
processes with additional 

406
00:26:13,860 --> 00:26:17,420
capabilities. 
Maybe we're almost at the end of

407
00:26:17,500 --> 00:26:21,260
our podcast. 
What is on your agenda for Kwc's

408
00:26:21,260 --> 00:26:23,140
future? 
What's next to come? 

409
00:26:24,550 --> 00:26:27,910
It's on the one hand, the total 
landscape still needs to be 

410
00:26:27,910 --> 00:26:30,790
extended with certain 
functionalities had John 

411
00:26:30,790 --> 00:26:34,150
mentioned it. 
But it's analytics simply 

412
00:26:34,150 --> 00:26:37,630
because we now have to use the 
insights we have and the data we

413
00:26:37,630 --> 00:26:40,790
have. 
It's on environmental safety and

414
00:26:40,790 --> 00:26:44,630
health where we simply have to 
comply with regulation basically

415
00:26:44,630 --> 00:26:48,250
on interval supply chain 
reporting and whether it's CO2 

416
00:26:48,250 --> 00:26:51,370
or plastic or other topics that 
is a must. 

417
00:26:51,450 --> 00:26:54,890
We're working hard on employee 
self-service just because of 

418
00:26:54,930 --> 00:26:58,370
efficiency. 
And another must is on 

419
00:26:58,370 --> 00:27:02,770
integration with our customers 
around projects, the design of 

420
00:27:02,850 --> 00:27:08,730
the bathroom, the design of the 
public wash areas, so that we 

421
00:27:08,730 --> 00:27:12,290
work hand in hand on projects 
with our customers and in that 

422
00:27:12,290 --> 00:27:16,020
way Dr. our order intake. 
So there's one thing. 

423
00:27:16,020 --> 00:27:20,460
So that's general Specifically 
we are more and more focusing on

424
00:27:20,460 --> 00:27:23,660
the different business lines and
the differences between the 

425
00:27:23,660 --> 00:27:26,100
business lines. 
So really supporting our 

426
00:27:26,100 --> 00:27:29,500
professional business, which is 
work where we're working for 

427
00:27:29,500 --> 00:27:34,420
bigger customers with a tighter 
customer integration in home 

428
00:27:34,420 --> 00:27:38,500
where we do the e-commerce and 
have the processes to the 

429
00:27:38,500 --> 00:27:43,440
wholesalers, but maybe also with
companies like Reuters, the A, 

430
00:27:43,640 --> 00:27:47,240
selling over the Internet. 
And then specific support for 

431
00:27:47,640 --> 00:27:51,520
our health domain, which is 
basically driven out of Nordics,

432
00:27:51,800 --> 00:27:57,680
Scandinavia and our business in 
China, which is basically an OEM

433
00:27:57,680 --> 00:28:00,560
business also with their 
specific needs. 

434
00:28:00,800 --> 00:28:04,160
So what I see is that the 
differences between these 

435
00:28:04,280 --> 00:28:07,960
business lines are coming up 
with more dedicated support, 

436
00:28:08,530 --> 00:28:11,970
also dedicated requirements from
the integration platform. 

437
00:28:12,170 --> 00:28:14,810
That is what we start to focus 
on right now. 

438
00:28:15,530 --> 00:28:17,730
Very good. 
As I already mentioned, we at 

439
00:28:17,730 --> 00:28:20,850
the end of this episode, I 
really enjoyed this. 

440
00:28:20,850 --> 00:28:23,970
I would have so many more 
questions for you, Meno and get 

441
00:28:23,970 --> 00:28:26,450
Yan. 
Thank you so much for being here

442
00:28:26,450 --> 00:28:28,930
today and also thank you for 
joining. 

443
00:28:29,940 --> 00:28:35,700
As always, feel free to drop us 
an e-mail via inside S4 SAP COM 

444
00:28:35,700 --> 00:28:39,300
and let us know which topics are
of your interest. 

445
00:28:39,300 --> 00:28:42,780
TuneIn next time and be inside 
SAP S for HANA.

