1
00:00:12,400 --> 00:00:15,400
Welcome again to a podcast 
inside sap. 

2
00:00:15,400 --> 00:00:18,600
As for Hannah, there's no 
customer success without product

3
00:00:18,600 --> 00:00:22,300
success and project success. 
My name is Jani, Peter Schmidt. 

4
00:00:22,300 --> 00:00:25,200
And I'm leading the product 
success and ableman team based 

5
00:00:25,200 --> 00:00:29,300
out of Waldorf. 
In today's episode, I'm joined 

6
00:00:29,300 --> 00:00:32,400
by Mark. 
Altitude from sap and Lena 

7
00:00:32,400 --> 00:00:36,000
Michelle from our customer 
comics and is the project leader

8
00:00:36,000 --> 00:00:37,700
for the implementation of a 
safe. 

9
00:00:37,700 --> 00:00:40,700
PS4 on a cloud. 
At the manufacturing plant in 

10
00:00:40,700 --> 00:00:45,500
caffeine do as well as their 
digital business manager Lena, 

11
00:00:45,700 --> 00:00:49,200
welcome or better said welcome 
back after our joint podcast 

12
00:00:49,200 --> 00:00:53,600
episode number 42, Hi everyone. 
Nice to be here again. 

13
00:00:55,100 --> 00:00:57,500
And of course, my dear 
colleague, Mark was Earl told 

14
00:00:57,500 --> 00:01:00,200
her product expert for 
manufacturing supply chain. 

15
00:01:00,600 --> 00:01:02,800
Discrete Industries, who 
supporting me to there's a 

16
00:01:02,808 --> 00:01:07,300
co-host with this expect. 
He's hello Marcus ionic. 

17
00:01:07,300 --> 00:01:11,000
Thanks for having me. 
So for today's episode, we want 

18
00:01:11,000 --> 00:01:13,800
to continue a series and talk 
about the implementation that 

19
00:01:13,800 --> 00:01:16,800
Comics, how it's going? 
Because this is where we stopped

20
00:01:16,800 --> 00:01:19,000
last time. 
But of course before we start as

21
00:01:19,000 --> 00:01:22,100
we exactly two weeks before 
Christmas here in Germany Lena, 

22
00:01:22,100 --> 00:01:25,100
are you planning some days off? 
What are your wishes? 

23
00:01:26,700 --> 00:01:30,400
Well, the first wish will be 
that we are going smooth through

24
00:01:30,400 --> 00:01:34,200
our cut over right now. 
Therefore the team and I, we are

25
00:01:34,200 --> 00:01:36,200
going to have three or four days
of. 

26
00:01:36,200 --> 00:01:40,200
But but in between Christmas and
New Year's Eve, we are going to 

27
00:01:40,600 --> 00:01:43,200
continue with our cutover so 
more or less. 

28
00:01:43,200 --> 00:01:47,500
They are only three days off but
I will try to enjoy them and 

29
00:01:47,500 --> 00:01:49,900
stay at home. 
Have a nice time with my family 

30
00:01:49,900 --> 00:01:54,400
and I hope everyone is doing 
well because of the pandemic 

31
00:01:54,400 --> 00:01:57,100
right now. 
Thank you for sharing and 

32
00:01:57,200 --> 00:01:58,300
Marcus. 
What about you? 

33
00:01:59,500 --> 00:02:05,000
Of course, also working on the 
new release 2022 or two, but my 

34
00:02:05,000 --> 00:02:08,699
family and I we wanted to go to 
Berlin for Christmas to see my 

35
00:02:08,699 --> 00:02:11,300
mom. 
It's probably not possible 

36
00:02:11,300 --> 00:02:16,000
anymore because in Switzerland, 
we are in the high risk and but 

37
00:02:16,000 --> 00:02:18,300
it's important, everybody's 
healthy. 

38
00:02:18,300 --> 00:02:20,200
So it doesn't really matter. 
It's not today. 

39
00:02:20,300 --> 00:02:22,700
So maybe tomorrow, I can go 
sledding with my son. 

40
00:02:22,700 --> 00:02:28,300
So everything is good and so 
yeah, Christmas can come. 

41
00:02:29,500 --> 00:02:31,700
Great Christmas, and come back 
before that. 

42
00:02:31,800 --> 00:02:35,300
Let's get started with our 
podcasts for little recap later.

43
00:02:35,300 --> 00:02:38,200
Can you please tell us what 
comic does? 

44
00:02:38,200 --> 00:02:41,300
What is the purpose and the 
ambition of your company and 

45
00:02:41,300 --> 00:02:44,500
what is the plant in caffeine? 
Are you working is producing? 

46
00:02:44,500 --> 00:02:49,900
Exactly. 
Of course, right now, Comics is 

47
00:02:49,900 --> 00:02:53,600
a market leader within the field
of automated automated way of 

48
00:02:53,600 --> 00:02:56,600
processing. 
And it's a Swiss company based 

49
00:02:56,600 --> 00:03:00,500
in Lucerne with production 
facilities around The globin 

50
00:03:00,600 --> 00:03:04,400
round about 2,000 employees and 
Comics is right now, 

51
00:03:04,400 --> 00:03:08,100
concentrating on for market, 
segments Automotive Aerospace 

52
00:03:08,100 --> 00:03:12,700
Telecom and Industrial and 
especially in graph. 

53
00:03:12,700 --> 00:03:16,400
Now, in the middle of the 
Bavarian Forest at the comic 

54
00:03:16,400 --> 00:03:20,400
Sicily, we are focused on the 
production of customers specific

55
00:03:20,400 --> 00:03:25,100
Solutions with around 250 
employees and in addition to 

56
00:03:25,100 --> 00:03:30,700
that as well quality tools and 
micrograph labs Thanks a lot 

57
00:03:30,800 --> 00:03:32,900
later for the introduction to 
comics. 

58
00:03:33,500 --> 00:03:37,400
And the last episode, we talked 
a lot about the discovery phase.

59
00:03:37,900 --> 00:03:41,400
Now you moved on in the project 
and you went into the explore 

60
00:03:41,400 --> 00:03:45,800
phase, how did you structure the
explore phase and what's going 

61
00:03:45,800 --> 00:03:49,700
on there? 
So, basically, at the beginning,

62
00:03:49,700 --> 00:03:53,100
we had a lot of use cases and 
the output of our Discovery 

63
00:03:53,100 --> 00:03:56,700
assessment which took place in 
October, 20, 20. 

64
00:03:56,700 --> 00:04:01,400
And after that, after going into
the project, We started with the

65
00:04:01,400 --> 00:04:06,500
explore phase and we defined our
fittest and of workshops based 

66
00:04:06,500 --> 00:04:10,800
on our use case we try to make 
like Workshop packages based on 

67
00:04:10,800 --> 00:04:15,600
different scope items together 
and we try to structure those 

68
00:04:15,600 --> 00:04:19,700
packages along our use cases 
here and along our end-to-end 

69
00:04:19,700 --> 00:04:24,900
process and we really try to 
discuss the packages and as well

70
00:04:24,900 --> 00:04:29,000
as go buy items with our project
team that they really ensure or 

71
00:04:29,000 --> 00:04:31,100
that win. 
Assure the understanding of the 

72
00:04:31,100 --> 00:04:34,500
topics covered in the different 
workshops for us. 

73
00:04:34,500 --> 00:04:37,600
It was pretty challenging 
because due to the pandemic we 

74
00:04:38,000 --> 00:04:41,900
had to do all the workshops 
remotely and was a hard time for

75
00:04:42,000 --> 00:04:44,700
for the entire project team 
because sitting in front of a 

76
00:04:45,100 --> 00:04:48,900
monitor for video calling six to
eight hours. 

77
00:04:48,900 --> 00:04:54,500
A day was sometimes pretty hard 
for them but it was a we went 

78
00:04:54,500 --> 00:04:56,800
through it. 
Pretty good with the workshops. 

79
00:04:58,600 --> 00:05:00,900
You're not the explore phase is,
of course, fundamental in the 

80
00:05:00,900 --> 00:05:06,500
entire methodology. 
What is according to use the, 

81
00:05:07,600 --> 00:05:09,600
what are the most important 
things? 

82
00:05:09,800 --> 00:05:14,900
Most important step to know, 
based on your experience and 

83
00:05:14,900 --> 00:05:17,400
especially from an business user
perspective? 

84
00:05:17,500 --> 00:05:21,700
What would you share with us? 
So for us it was pretty crucial 

85
00:05:21,700 --> 00:05:26,000
that our business is really 
understanding the main processes

86
00:05:26,000 --> 00:05:29,200
behind the scope items. 
So that they are able to like do

87
00:05:29,200 --> 00:05:34,000
the mapping between the scope 
item and our use case or our 

88
00:05:34,000 --> 00:05:38,000
Comics use case, and that they 
are as well able to let or to 

89
00:05:38,000 --> 00:05:41,200
map them on a high level 
business perspective that they 

90
00:05:41,200 --> 00:05:45,100
know which scope item to use in 
which end-to-end process. 

91
00:05:45,100 --> 00:05:49,000
Since we are having a huge 
variety of different use cases, 

92
00:05:49,000 --> 00:05:52,700
as well for us. 
It was well, crucial to identify

93
00:05:52,700 --> 00:05:56,800
critical topics and to structure
them around the workshops as 

94
00:05:56,800 --> 00:05:59,100
well. 
I'm to point out some 

95
00:05:59,100 --> 00:06:02,500
integrative topic. 
So for example, the entire bomb 

96
00:06:02,500 --> 00:06:06,200
handling for the entire 
end-to-end process and we really

97
00:06:06,200 --> 00:06:11,400
try to focus on those critical 
topics as well, that they are 

98
00:06:11,400 --> 00:06:15,800
not going to be a showstopper 
during the entire project and 

99
00:06:15,800 --> 00:06:20,700
really to structure them into or
to put them between different 

100
00:06:20,700 --> 00:06:23,500
workshops. 
And on the other hand, it was 

101
00:06:23,600 --> 00:06:27,200
very useful for us to block our 
users. 

102
00:06:27,400 --> 00:06:31,400
Early enough for the workshop. 
So we really tried for weeks 

103
00:06:31,400 --> 00:06:34,600
before the workshops took place 
to really block them that they 

104
00:06:34,600 --> 00:06:38,900
really could concentrate on a 
workshop and then get out of 

105
00:06:38,900 --> 00:06:42,500
their daily business and really 
go into the project, be able to 

106
00:06:42,700 --> 00:06:46,500
perform their tasks and really 
to understand what the workshop 

107
00:06:46,500 --> 00:06:50,900
is about and really to be in the
workshop and in the topic and it

108
00:06:50,900 --> 00:06:52,500
not somewhere in the Daily 
Business. 

109
00:06:52,500 --> 00:06:56,300
Right now. 
Interestingly enough and in 

110
00:06:56,300 --> 00:06:58,800
general, what are your 
experiences with configurations 

111
00:06:58,800 --> 00:07:04,700
in s as a PS4 on a cloud. 
So for us, DSS cui, approaches 

112
00:07:04,900 --> 00:07:09,500
giving a very good guidance for 
our business and as well you 

113
00:07:09,500 --> 00:07:13,800
have limited configuration 
options and if you have a 

114
00:07:13,800 --> 00:07:18,000
business which really wants to 
like customize the system, the 

115
00:07:18,000 --> 00:07:22,600
S4 is definitely the wrong 
system, but on our side we were 

116
00:07:22,600 --> 00:07:27,000
able to Nearly bring every 
requirement into the system and 

117
00:07:27,200 --> 00:07:31,500
I think the configuration is 
very good and it's a good 

118
00:07:31,500 --> 00:07:33,700
explanation. 
The Consultants have a really 

119
00:07:33,700 --> 00:07:37,400
good guidance with the SSU eyes 
and I think it's a it's a good 

120
00:07:37,500 --> 00:07:41,600
good overview for us and some 
cases we had the feeling that 

121
00:07:41,600 --> 00:07:46,400
there are a few limitations. 
But yeah, as I said before 

122
00:07:46,500 --> 00:07:49,400
that's if you are going to the 
standardized system, the 

123
00:07:50,000 --> 00:07:53,000
consequences are taking their 
but I think it's more the 

124
00:07:53,000 --> 00:07:56,200
feeling. 
On the business side that we may

125
00:07:56,500 --> 00:08:00,500
have needed or may need more 
configuration as a see you guys 

126
00:08:00,500 --> 00:08:04,000
as well. 
More will come Lena more, we 

127
00:08:04,000 --> 00:08:09,300
come and Lena. 
How did you handle the global 

128
00:08:09,300 --> 00:08:11,700
settings? 
Or maybe explain a little bit, 

129
00:08:11,700 --> 00:08:14,000
the global configuration 
settings? 

130
00:08:15,300 --> 00:08:20,100
So, from our side, there were a 
lot of global settings already 

131
00:08:20,800 --> 00:08:22,400
defined from the previous row 
lot. 

132
00:08:22,400 --> 00:08:25,600
So, for example, the Global 
Currency right now. 

133
00:08:25,600 --> 00:08:31,000
And we tried to really enforce 
or try to get the Consultants 

134
00:08:31,000 --> 00:08:33,700
into our Comics defined global 
settings. 

135
00:08:33,700 --> 00:08:38,200
They did a self enablement on 
the comics configuration, what 

136
00:08:38,200 --> 00:08:41,799
is already in the system and 
then they explained it to our 

137
00:08:41,799 --> 00:08:44,800
team and then our team discuss 
the global settings and try to 

138
00:08:44,800 --> 00:08:48,400
understand them and already 
tested them in the system. 

139
00:08:48,400 --> 00:08:52,600
Then then we had a few not 
defined global settings. 

140
00:08:52,600 --> 00:08:56,500
So for example, Within 
manufacturing, we had a few of 

141
00:08:56,500 --> 00:09:01,100
them because right now, we are 
one of the main engineered water

142
00:09:01,100 --> 00:09:05,400
locations right now and 
therefore, we had to set 

143
00:09:05,400 --> 00:09:09,000
different other global settings 
and we just discuss them 

144
00:09:09,000 --> 00:09:12,900
together with the global team 
from Switzerland. 

145
00:09:12,900 --> 00:09:16,300
And then, decided together, what
would be the perfect fit for the

146
00:09:16,300 --> 00:09:18,500
entire Comics group for the 
global setting. 

147
00:09:18,500 --> 00:09:22,800
And after going through the 
explore phase, all settings are 

148
00:09:22,800 --> 00:09:24,800
not only global settings as 
well. 

149
00:09:24,900 --> 00:09:29,600
The plant based settings where 
approved from and reviewed from 

150
00:09:29,600 --> 00:09:32,500
the global team that we have a 
broad understanding in the 

151
00:09:32,500 --> 00:09:35,300
entire company about the 
configuration graph. 

152
00:09:35,300 --> 00:09:39,200
And I'll let you talk about 
global settings. 

153
00:09:40,100 --> 00:09:42,900
Most people would know, global 
settings in finance, like, 

154
00:09:43,000 --> 00:09:45,200
fiscal year, fiscal year Ryan's 
Etc. 

155
00:09:45,900 --> 00:09:48,700
But you are already on your as 
well as the production side 

156
00:09:48,700 --> 00:09:51,500
running MRP. 
Advanced ATP can do a little bit

157
00:09:51,500 --> 00:09:53,400
about the global settings on 
your end. 

158
00:09:54,700 --> 00:09:57,500
So, basically, what you 
mentioned before, the finance 

159
00:09:57,700 --> 00:10:01,400
line of business is very strong 
and full of global settings. 

160
00:10:01,400 --> 00:10:04,300
Like I mentioned before the 
global currency, for example, 

161
00:10:05,200 --> 00:10:09,100
within the manufacturing area, 
there are a lot of global 

162
00:10:09,100 --> 00:10:12,300
settings. 
For example, the catalog for the

163
00:10:12,300 --> 00:10:15,100
lot size procedure, which is 
defined globally. 

164
00:10:15,600 --> 00:10:19,500
Then, on the other hand, the ATP
check where we only have three 

165
00:10:19,500 --> 00:10:23,600
available ATP groups, which need
to be transferred into it. 

166
00:10:23,800 --> 00:10:26,800
Every company and therefore you 
need for example, to harmonize 

167
00:10:26,800 --> 00:10:30,000
the ATP check on a few points 
there. 

168
00:10:30,000 --> 00:10:33,600
And there are a lot of global 
settings, where you're coming 

169
00:10:33,600 --> 00:10:39,100
over during the project, thanks 
Lena for exploration and going 

170
00:10:39,100 --> 00:10:40,900
more into detail for the global 
settings. 

171
00:10:40,900 --> 00:10:44,800
When we come to also in a very 
important topic, migration of 

172
00:10:44,800 --> 00:10:49,300
data did you already migrated 
Master data and your test system

173
00:10:49,400 --> 00:10:51,200
and what are your experiences 
there? 

174
00:10:51,200 --> 00:10:53,600
Did you use a specific tool from
sap? 

175
00:10:53,800 --> 00:10:57,400
How did you do it? 
So basically we did the first 

176
00:10:57,400 --> 00:11:01,300
migration already in the so 
called sandbox system and 

177
00:11:01,300 --> 00:11:05,400
afterwards. 
We made different rounds of 

178
00:11:05,400 --> 00:11:10,000
migrating our data into the 
queue system and then we used 

179
00:11:10,000 --> 00:11:14,000
our migrated data for the 
testing that we ensure that all 

180
00:11:14,000 --> 00:11:18,000
migrated data has the 
appropriate data quality, to be 

181
00:11:18,000 --> 00:11:20,700
honest, it was a pretty hard 
time for the team because they 

182
00:11:20,900 --> 00:11:24,800
needed to get used to all the 
sap language as Sap attributes. 

183
00:11:25,300 --> 00:11:29,800
And for them, it was a pretty 
good learning time for the 

184
00:11:29,800 --> 00:11:32,700
migration of the of the queue 
system data. 

185
00:11:34,400 --> 00:11:37,200
What we basically did, we 
created our own software to 

186
00:11:37,200 --> 00:11:40,500
extract the data from our Legacy
system and to do the mapping, 

187
00:11:40,500 --> 00:11:44,700
within the software, one of my 
colleagues did a pretty good job

188
00:11:44,700 --> 00:11:47,200
here. 
And then he is doing all the, or

189
00:11:47,200 --> 00:11:52,700
his running order, logic logical
checks within his tool and then 

190
00:11:52,700 --> 00:11:57,200
the tool is Directly bringing 
the data into the sap, migration

191
00:11:57,200 --> 00:12:00,400
files and afterwards. 
We are uploading the migration 

192
00:12:00,400 --> 00:12:05,100
files and the migration tool 
from sap and then they directly 

193
00:12:05,200 --> 00:12:10,000
go into the system. 
Hopefully, in another topic I'd 

194
00:12:10,000 --> 00:12:12,700
like to address. 
This is authorizations, most of 

195
00:12:12,700 --> 00:12:16,700
us or many of us, would remember
the authorization in on-premise 

196
00:12:16,700 --> 00:12:20,200
with the PFC G roles in the back
ends and the front end, but of 

197
00:12:20,200 --> 00:12:21,700
course in the cloud. 
It's different. 

198
00:12:21,800 --> 00:12:23,600
Alright. 
Same, look and feel Theory. 

199
00:12:23,700 --> 00:12:28,200
Re-access. 
But how is that working for you?

200
00:12:28,500 --> 00:12:30,500
Did you work with the standard 
business roles that are 

201
00:12:30,508 --> 00:12:33,500
pre-configured? 
Because cloud is based on the 

202
00:12:33,600 --> 00:12:40,700
standard pre-configuration, or 
what did you do to adjust to the

203
00:12:40,700 --> 00:12:45,100
needs of comics? 
So basically, within the testing

204
00:12:45,100 --> 00:12:49,200
within the sandbox will use the 
pre-configured standard roads as

205
00:12:49,200 --> 00:12:53,300
well in the queue system. 
And what we then did, we ask our

206
00:12:53,300 --> 00:12:56,900
business There are any deltas 
and then we slightly adjusted 

207
00:12:56,900 --> 00:13:02,000
the roles, but all in all we try
to go along the standard Rose 

208
00:13:02,000 --> 00:13:04,600
from sap but we had slight 
adjustments. 

209
00:13:04,600 --> 00:13:08,700
If our organizations, for 
example, structured little bit 

210
00:13:08,700 --> 00:13:11,700
different to the provided a 
secure roads. 

211
00:13:12,800 --> 00:13:16,700
When you plan to move into the 
test phase or are maybe already 

212
00:13:16,700 --> 00:13:19,000
in the test phase, we haven't 
talked to her in a while. 

213
00:13:20,100 --> 00:13:22,700
Yes. 
So we are already finished with 

214
00:13:22,700 --> 00:13:24,800
the test phase. 
So, last week, we've started 

215
00:13:24,800 --> 00:13:29,000
with our cat over. 
We moved it to the test. 

216
00:13:29,000 --> 00:13:32,400
Phase around about at the end of
August after our Q gate. 

217
00:13:33,100 --> 00:13:36,400
And right now, the users are 
pretty familiar with the system 

218
00:13:36,400 --> 00:13:40,800
and what we did or what was 
really an enabler for the entire

219
00:13:40,800 --> 00:13:45,800
project are the integrative test
sessions and we really block the

220
00:13:45,800 --> 00:13:47,600
entire Team, every line of 
business. 

221
00:13:47,600 --> 00:13:51,200
Every Tuesday, and Thursday 
morning, we did put them 

222
00:13:51,200 --> 00:13:54,200
together on site and to one room
and then they had Going to use 

223
00:13:54,200 --> 00:13:57,900
cases to test and it really 
helped the team to understand 

224
00:13:58,000 --> 00:14:01,700
the entire end-to-end process 
and to understand what is 

225
00:14:01,700 --> 00:14:03,400
happening. 
If I am clicking on, for 

226
00:14:03,400 --> 00:14:06,200
example, one button and what is 
happening, for example, in the 

227
00:14:06,200 --> 00:14:09,700
group controlling Department 
there, and it was really one 

228
00:14:09,800 --> 00:14:14,200
huge enabler for our business to
really understand the system. 

229
00:14:14,800 --> 00:14:18,000
And then at the end of October, 
we completed our solution 

230
00:14:18,000 --> 00:14:22,500
walkthrough where the team 
really showed us a complete 

231
00:14:22,500 --> 00:14:25,700
end-to-end process. 
For a made-to-order scenario. 

232
00:14:26,000 --> 00:14:30,400
And as well different use cases,
which could occur during the 

233
00:14:31,500 --> 00:14:35,000
entire processor. 
For example, adding some 

234
00:14:35,000 --> 00:14:39,300
material or changing something 
within the production orders, 

235
00:14:39,300 --> 00:14:46,800
and they try to test a lot of 
different like use cases, Okay, 

236
00:14:46,800 --> 00:14:48,000
cool. 
Yeah, thank you. 

237
00:14:49,900 --> 00:14:54,200
So being in the test phase and 
moving on, I assume maybe in 

238
00:14:54,200 --> 00:14:58,000
January or something, you go for
going live or maybe also then 

239
00:14:58,000 --> 00:14:59,600
going into hyper care 
afterwards. 

240
00:15:00,400 --> 00:15:03,000
One more question for my site. 
The do you still sleep? 

241
00:15:03,000 --> 00:15:07,200
Well as a project manager. 
Well basically since we are in a

242
00:15:07,200 --> 00:15:10,400
cad over and really in the last 
three to four weeks before I go 

243
00:15:10,400 --> 00:15:14,300
life, it's kind of hard to get 
the end, her sleep tearing eye 

244
00:15:14,308 --> 00:15:16,200
because there are a lot of Of 
open points. 

245
00:15:16,200 --> 00:15:18,000
You need to think through and be
aware of. 

246
00:15:18,000 --> 00:15:21,300
And since the time is getting 
closer for the go life, it's 

247
00:15:21,600 --> 00:15:24,400
it's pretty hard right now. 
But we are having a great team 

248
00:15:24,400 --> 00:15:27,800
here and they are supporting. 
Every step, we are taking in the

249
00:15:27,800 --> 00:15:31,000
project. 
So I think we are good to go 

250
00:15:31,000 --> 00:15:34,100
life right now good. 
This is super tagline. 

251
00:15:34,100 --> 00:15:36,800
Lena sleep well with a CPS for 
on a cloud. 

252
00:15:37,700 --> 00:15:43,000
Yeah, as we approach Christmas. 
What do you wish from a CPR, 

253
00:15:43,000 --> 00:15:45,200
concretely? 
Where do you see? 

254
00:15:45,400 --> 00:15:48,800
Especially in the ACP, as for 
Hannah Cloud activate 

255
00:15:48,800 --> 00:15:55,400
methodology from my perspective,
we needed a lot of help for the 

256
00:15:55,400 --> 00:16:00,200
mapping between our use case. 
And the sap use case to really 

257
00:16:00,200 --> 00:16:05,400
understand what is, or in other 
words, really, to understand 

258
00:16:05,400 --> 00:16:08,900
what sap wanted to do with the 
best practice process. 

259
00:16:09,200 --> 00:16:12,000
So, for example, if you have a 
best practice process, which 

260
00:16:12,000 --> 00:16:15,700
differs pretty much from our 
current process, To really 

261
00:16:15,700 --> 00:16:18,000
understand why does it differ so
much? 

262
00:16:18,000 --> 00:16:21,200
And what do we need to change to
really fit into the best 

263
00:16:21,200 --> 00:16:27,300
practice process and therefore 
helping to really map our use 

264
00:16:27,300 --> 00:16:31,200
cases to the scope. 
Items was really helpful. 

265
00:16:31,200 --> 00:16:34,300
So a lot of Consultants. 
They try to during the 

266
00:16:34,300 --> 00:16:36,000
workshops. 
And I think we did a good job 

267
00:16:36,000 --> 00:16:40,100
here but therefore we had to 
take a few action items here. 

268
00:16:40,600 --> 00:16:43,800
And on the other hand, the scope
items, they are pretty much 

269
00:16:43,800 --> 00:16:47,400
focused on to one LOB. 
And I think we're going to 

270
00:16:47,400 --> 00:16:50,600
activate methodology. 
There would be or there need to 

271
00:16:50,600 --> 00:16:55,300
be more integrative scenarios, 
more integrated integrative 

272
00:16:55,300 --> 00:16:58,300
testings at the beginning 
already that you, for example, 

273
00:16:58,300 --> 00:17:01,900
structured the fittest and of 
workshops on different topics 

274
00:17:01,900 --> 00:17:04,099
integrative way, you know, you 
need, for example. 

275
00:17:04,099 --> 00:17:07,599
Controlling manufacturing 
logistic together. 

276
00:17:09,099 --> 00:17:11,400
Yeah. 
And what we did together with 

277
00:17:11,400 --> 00:17:16,900
sap, was the cue Gates and I 
know there, Are basically the 

278
00:17:16,900 --> 00:17:22,200
queue gates from sap and we like
developed our own Co max-q gate 

279
00:17:22,800 --> 00:17:25,400
and it was pretty good to get 
our Kovacs management. 

280
00:17:25,400 --> 00:17:29,300
Together, get sap management 
together, get the sap team and 

281
00:17:29,300 --> 00:17:33,800
my team together and it was a 
pretty good approach because we 

282
00:17:33,900 --> 00:17:38,200
were very focused on those Q 
Gates and we're able to deliver 

283
00:17:38,400 --> 00:17:41,300
the work. 
We had to deliver that time. 

284
00:17:42,800 --> 00:17:46,200
All right. 
Lena noted that That were a few 

285
00:17:46,200 --> 00:17:48,600
good hints actually. 
Not only to sleep well with, as 

286
00:17:48,600 --> 00:17:51,900
for Hannah, but to prepare even 
better, the project Lena. 

287
00:17:52,000 --> 00:17:55,600
Thanks very much for joining us 
today and sharing your Insight 

288
00:17:55,600 --> 00:17:58,800
in a second episode. 
Thank you very much for having 

289
00:17:58,800 --> 00:18:00,900
me today. 
And, of course, Marcus, thanks 

290
00:18:00,900 --> 00:18:03,400
to you again for hosting this 
episode. 

291
00:18:03,900 --> 00:18:08,500
Always a pleasure, you are 
welcome unique and had lots of 

292
00:18:08,500 --> 00:18:11,000
fun today. 
Let me remind our listeners. 

293
00:18:11,000 --> 00:18:14,100
This will be a series of several
episodes where we will follow 

294
00:18:14,100 --> 00:18:17,300
Comics Journey. 
To a CPS for on a cloud on this 

295
00:18:17,300 --> 00:18:21,000
spot class very closely if 
you'll enjoy today's discussion 

296
00:18:21,000 --> 00:18:23,000
as much as I did and would like 
to learn more. 

297
00:18:23,100 --> 00:18:26,700
Stay tuned for the next one. 
And as always feel free to drop 

298
00:18:26,700 --> 00:18:31,800
us an email via inside. 
As for at sap.com/learnbi, let 

299
00:18:31,800 --> 00:18:36,700
us know which topics are of your
interest tune in next time and 

300
00:18:36,700 --> 00:18:40,000
be inside sap as for Hannah. 
Goodbye.

