1
00:00:10,000 --> 00:00:13,900
Hi, everyone across the world 
and Welcome to our podcast 

2
00:00:13,900 --> 00:00:18,500
inside as a PS4, Hannah about 
software as a service and 

3
00:00:18,500 --> 00:00:24,000
Manufacturing myth or reality. 
There is no customer success 

4
00:00:24,100 --> 00:00:28,900
without product success and 
project success, a common belief

5
00:00:28,900 --> 00:00:31,800
exists in the market. 
That cloud applications are best

6
00:00:31,800 --> 00:00:34,500
suited for front office 
applications and Professional 

7
00:00:34,500 --> 00:00:38,400
Services companies and that 
handling manufacturing or supply

8
00:00:38,400 --> 00:00:41,900
chain. 
Processes are too complex today.

9
00:00:41,900 --> 00:00:46,100
I would like to discuss this 
question with Louis de Alexander

10
00:00:46,100 --> 00:00:49,600
qz. 
Head of manufacturing from sap 

11
00:00:49,600 --> 00:00:52,300
partner share. 
Welcome Larissa. 

12
00:00:52,300 --> 00:00:55,700
And how are you? 
I'm Marcos, I'm super excited to

13
00:00:55,708 --> 00:00:57,700
be here with you. 
Thanks for having me. 

14
00:00:58,200 --> 00:01:00,000
Oh, you're very welcome. 
Thanks. 

15
00:01:00,200 --> 00:01:03,100
For being here. 
And if you would have to 

16
00:01:03,100 --> 00:01:06,900
describe yourself in three 
sentences to the world, who is 

17
00:01:06,900 --> 00:01:14,100
Larisa, who is La Casa? 
O, que la, casa is an amateur 

18
00:01:14,100 --> 00:01:20,000
Gardener a cycling cyclist lover
and a super positive and 

19
00:01:20,000 --> 00:01:23,600
pathetic leader. 
I can see that I can see that 

20
00:01:23,600 --> 00:01:27,500
Larissa. 
Thanks for this description and 

21
00:01:27,500 --> 00:01:29,200
additionally to your regular 
work. 

22
00:01:29,200 --> 00:01:32,400
As head of manufacturing, you 
are leading a charity project 

23
00:01:32,400 --> 00:01:34,800
for the Children's Hospital 
Zurich in Switzerland. 

24
00:01:35,300 --> 00:01:38,300
What is this project about? 
And how did you get involved? 

25
00:01:39,500 --> 00:01:42,800
This was my first 
entrepreneurial project after 

26
00:01:42,800 --> 00:01:47,900
University during my career. 
As a professional athlete, I was

27
00:01:47,900 --> 00:01:52,100
inspired by Marcel who quizzes 
with wheelchair racing athlete. 

28
00:01:52,500 --> 00:01:57,700
I learned a lot from him about 
mental, strength, strength, and 

29
00:01:57,700 --> 00:02:02,300
also what it means when people 
are born with an open, back 

30
00:02:02,600 --> 00:02:06,700
spinabifida be da, it's called 
and medical terms. 

31
00:02:07,100 --> 00:02:11,500
When I realized that, it's that 
it's possible to perform 

32
00:02:11,500 --> 00:02:16,800
operations on unborn children. 
Why there are still in the womb 

33
00:02:16,800 --> 00:02:18,600
of the mother? 
And in order to minimize 

34
00:02:18,600 --> 00:02:23,800
disabilities and increase 
quality of life, and that in 

35
00:02:23,800 --> 00:02:27,700
Switzerland, the cost for such 
operations are not covered by 

36
00:02:27,700 --> 00:02:30,900
the health insurance companies. 
This is why I organized this 

37
00:02:30,900 --> 00:02:35,300
charity project to support 
parents to be in the financing 

38
00:02:35,300 --> 00:02:41,500
with such Very inspiring story. 
Very cool. 

39
00:02:41,600 --> 00:02:46,800
Thanks for sharing and Teresa. 
You're the head of manufacturing

40
00:02:46,900 --> 00:02:49,600
of sap partner, share in 
Switzerland. 

41
00:02:50,100 --> 00:02:53,200
So what kind of services does 
share actually offer to its 

42
00:02:53,200 --> 00:02:56,800
client? 
Cher is known for its industry, 

43
00:02:56,800 --> 00:03:01,600
specific process expertise. 
We are a partner for customers 

44
00:03:01,700 --> 00:03:06,300
on their way to the meaningful 
and efficient use of sap. 

45
00:03:06,300 --> 00:03:11,800
And as a PS4, Hannah worldwide, 
show group has more than 30 

46
00:03:11,800 --> 00:03:15,600
offices and branches and Germany
the Netherlands Austria, 

47
00:03:15,700 --> 00:03:20,700
Switzerland, turkey Croatia, 
just to mention a few and share,

48
00:03:20,700 --> 00:03:23,200
Netherlands. 
Actually has celebrated its 

49
00:03:23,200 --> 00:03:29,300
anniversary as Sap Cloud ear. 
P partner for ten years in April

50
00:03:29,300 --> 00:03:33,200
2020. 
This year after they started as 

51
00:03:33,200 --> 00:03:39,000
a so-called early adopter, 10 
years ago, brilliant brilliant 

52
00:03:39,600 --> 00:03:42,600
and what are the typical 
discussions you have with 

53
00:03:42,600 --> 00:03:45,200
manufacturing customers about 
using SPSS. 

54
00:03:45,200 --> 00:03:49,800
Hana Cloud, are they actually 
scared when you when you visit 

55
00:03:49,800 --> 00:03:51,700
them? 
Or when they hear the word 

56
00:03:51,700 --> 00:03:54,400
software as a service or do they
are actively? 

57
00:03:54,600 --> 00:04:00,900
Really want to know more from 
you, basically our sap as for 

58
00:04:00,900 --> 00:04:03,700
Hana Cloud. 
Implementations include to path 

59
00:04:03,900 --> 00:04:07,600
on a customer side as well as 
internally at Shell group 

60
00:04:07,600 --> 00:04:11,000
itself. 
Typical discussions with clients

61
00:04:11,000 --> 00:04:14,000
include three main points. 
Actually, what cloud 

62
00:04:14,000 --> 00:04:18,000
manufacturing is, why cloudier P
manufacturing is at the top of 

63
00:04:18,000 --> 00:04:23,000
many companies to do lists right
now and what is in it for 

64
00:04:23,000 --> 00:04:27,200
manufacturers. 
Km and maybe we can briefly 

65
00:04:27,200 --> 00:04:31,100
address those or these three 
points and what is actually 

66
00:04:31,100 --> 00:04:35,700
Cloud by the factoring? 
Sure, Marcus Cloud manufacturing

67
00:04:35,700 --> 00:04:40,200
makes operational resources 
available on demand across the 

68
00:04:40,200 --> 00:04:46,300
business using Technologies, 
such as artificial intelligence 

69
00:04:46,300 --> 00:04:51,400
or Cloud connectivity, 
industrial iot through the use 

70
00:04:51,400 --> 00:04:55,500
of a centralized system, then 
such as Cloud ear, R p, software

71
00:04:55,700 --> 00:04:57,700
Cloud. 
Manufacturing operations can be 

72
00:04:57,700 --> 00:05:01,900
optimized and managed across the
entire lifecycle of a product 

73
00:05:02,100 --> 00:05:06,600
from R&D to maintenance. 
And even to the end of life and 

74
00:05:06,600 --> 00:05:12,100
recycling things for explaining,
those three points and why is 

75
00:05:12,100 --> 00:05:15,000
transforming the public Cloud 
for manufacturers, a more 

76
00:05:15,000 --> 00:05:20,800
important topic than ever. 
From my point of view, the 

77
00:05:21,200 --> 00:05:24,100
enormous change that 
manufacturing and supply chain 

78
00:05:24,100 --> 00:05:26,700
operations. 
Have undergone in the past four 

79
00:05:26,700 --> 00:05:30,600
years has left. 
Even some of the really best run

80
00:05:30,600 --> 00:05:34,800
companies feeling around. 
For example, growing customer 

81
00:05:34,800 --> 00:05:37,600
demands for Speed and 
customizations where are 

82
00:05:37,600 --> 00:05:41,700
poaching. 
Legacy Erp systems to the limits

83
00:05:42,700 --> 00:05:47,700
in order to thrive and not only 
to cope with this manufacturers 

84
00:05:47,700 --> 00:05:51,200
are looking for solutions that 
coordinate, their operations 

85
00:05:51,200 --> 00:05:55,500
holistically on one shared. 
Single platform. 

86
00:05:56,900 --> 00:06:02,000
I agree with you and when we 
talk about migrating to SPS for 

87
00:06:02,008 --> 00:06:06,700
Hannah cloud or public Cloud, so
that represents represents a 

88
00:06:06,700 --> 00:06:10,800
redesign technically and from a 
process engineering perspective.

89
00:06:11,500 --> 00:06:14,700
So taking up, much time, 
resources and capital. 

90
00:06:14,700 --> 00:06:19,100
What is in it for manufacturers?
Then using the S4 Hana Cloud, 

91
00:06:19,100 --> 00:06:22,300
manufacturing solution, includes
higher Innovation, ability 

92
00:06:22,400 --> 00:06:26,800
versus on-premise Solutions 
because the the upgrades from 

93
00:06:26,800 --> 00:06:31,100
sap will keep your public Cloud 
environment up to date with the 

94
00:06:31,100 --> 00:06:36,800
most Innovative Technologies. 
This way sap has found a way to 

95
00:06:36,900 --> 00:06:41,500
keep software receptive to 
Industry changes while really 

96
00:06:41,500 --> 00:06:45,900
keeping in mind, the Namek 
regulatory requirements beside 

97
00:06:46,200 --> 00:06:49,100
this Innovation. 
Topic, does our solution offers 

98
00:06:49,500 --> 00:06:52,500
the lowest TCO total cost of 
ownership. 

99
00:06:52,500 --> 00:06:57,000
Meaning the total cost of the 
public cloud is Comprehensively 

100
00:06:57,000 --> 00:07:00,100
less than its substitutes 
including implementation 

101
00:07:00,100 --> 00:07:04,000
licensing. 
And also overall support from 

102
00:07:04,000 --> 00:07:08,400
our experience at shared total 
cost of ownership production can

103
00:07:08,400 --> 00:07:13,700
be up to 20 25 percent reduction
in development time and 

104
00:07:13,700 --> 00:07:18,300
therefore fudge the time to 
Market can be as much as 50 to 

105
00:07:18,300 --> 00:07:24,200
75 percent from projects 
experience but every company has

106
00:07:24,200 --> 00:07:28,600
a different maturity And it's 
really important to determine 

107
00:07:28,600 --> 00:07:32,000
your own specific value. 
Proposition for your business, 

108
00:07:32,200 --> 00:07:36,400
with a partner. 
Thanks for explaining your point

109
00:07:36,400 --> 00:07:38,900
of view about what's in it for 
manufacturers. 

110
00:07:38,900 --> 00:07:42,900
And do you see a difference 
between sap established 

111
00:07:42,900 --> 00:07:46,700
installed base customers or net 
new name, customers in the 

112
00:07:46,707 --> 00:07:49,600
manufacturing Industries? 
And the demand about using a 

113
00:07:49,600 --> 00:07:54,700
software-as-a-service Erp? 
Yeah, install base, customers 

114
00:07:54,700 --> 00:08:00,700
actually have been using ECC for
several years but times have 

115
00:08:00,700 --> 00:08:03,800
changed like with electric cars.
It's easy. 

116
00:08:03,900 --> 00:08:08,500
Whilst the best technology then 
and is now being replaced. 

117
00:08:08,500 --> 00:08:13,900
So what does this mean for 
customers and installed base? 

118
00:08:13,900 --> 00:08:17,100
Customer has developed a set 
tables or P function. 

119
00:08:17,100 --> 00:08:21,500
And with regards to the cloud, 
they have to stick to best 

120
00:08:21,500 --> 00:08:25,000
practices after fit a standard 
workshops. 

121
00:08:25,000 --> 00:08:29,800
This idea is not easy for the 
business because it can mean a 

122
00:08:29,800 --> 00:08:33,900
huge change in the way of 
working right on the other. 

123
00:08:33,900 --> 00:08:37,799
Other hand, new name, customers 
or less tempted to see 

124
00:08:37,799 --> 00:08:40,700
implementing a digital core just
as an infrastructure 

125
00:08:40,700 --> 00:08:46,100
optimization or being tempted to
copy outdated Landscapes and 

126
00:08:46,100 --> 00:08:49,400
technological limitations from 
the past into the future. 

127
00:08:50,000 --> 00:08:54,500
But rather see the opportunity 
to optimize their entire 

128
00:08:54,500 --> 00:08:58,700
business model. 
As a consequence and yeah to sum

129
00:08:58,700 --> 00:09:03,700
it up, the natural reaction and 
concern of a customer that is 

130
00:09:03,700 --> 00:09:09,100
used to any CC system. 
Is that a transformation from 

131
00:09:09,100 --> 00:09:11,300
on-premise to the public 
calcloud? 

132
00:09:11,300 --> 00:09:14,700
Can't adopt current working 
routines identically and that 

133
00:09:14,700 --> 00:09:17,300
the cloud environment is 
therefore not the right 

134
00:09:17,300 --> 00:09:21,700
environment at first glance. 
I mean this may sound logical 

135
00:09:21,700 --> 00:09:25,600
because who likes to change 
long-standing working routines, 

136
00:09:25,700 --> 00:09:29,000
right? 
But a chair at the same time. 

137
00:09:29,100 --> 00:09:33,500
We may experience in discussions
with manufacturers that 

138
00:09:33,800 --> 00:09:37,900
downsizing of processes and lean
management within their 

139
00:09:37,900 --> 00:09:43,000
production is a Hot Topic and 
according to usage analysis, and

140
00:09:43,000 --> 00:09:48,500
average sap customer actively 
uses less than 40% of the custom

141
00:09:48,500 --> 00:09:52,400
code in their sap system. 
In order words also from the 

142
00:09:52,400 --> 00:09:57,600
market, these are clear signals 
that the focus is Likely moving 

143
00:09:57,600 --> 00:10:01,400
from Individual process and 
individual business requirements

144
00:10:01,400 --> 00:10:06,600
and the customizations to best 
practices and standardization 

145
00:10:07,300 --> 00:10:10,200
which is actually the 
possibility that the cloud 

146
00:10:10,200 --> 00:10:13,400
cloud. 
Public Cloud offers, thank you 

147
00:10:13,400 --> 00:10:16,300
very much for this. 
Very good and detailed 

148
00:10:16,700 --> 00:10:21,000
explanation and if we look at 
different manufacturing 

149
00:10:21,000 --> 00:10:25,600
Industries do you think there's 
a niche or that as a PS4 Hana 

150
00:10:26,100 --> 00:10:28,000
cloud? 
As a software-as-a-service model

151
00:10:28,000 --> 00:10:32,500
works well from experience. 
The simple rule applies. 

152
00:10:33,100 --> 00:10:37,200
The more complex the product and
the smaller, the batch size, the

153
00:10:37,200 --> 00:10:40,100
more likely it is that 
additional Solutions will be 

154
00:10:40,100 --> 00:10:42,500
needed. 
Like epd Enterprise product 

155
00:10:42,500 --> 00:10:48,200
development, which enables all 
users to collaborate seamlessly 

156
00:10:48,200 --> 00:10:53,300
unstructured or even on 
unstructured product data and 

157
00:10:53,600 --> 00:10:56,400
realization of a holistic 
development and production. 

158
00:10:56,800 --> 00:11:00,200
Protects with regard to the 
manufacturing Industries. 

159
00:11:00,200 --> 00:11:04,600
You asked for markers, from 
project experience as a PS4, 

160
00:11:04,600 --> 00:11:07,600
Hannah, Public, Cloud 
Indiscreet, Industries works, 

161
00:11:07,600 --> 00:11:11,200
best for make, to stork 
assembled order, and configure 

162
00:11:11,200 --> 00:11:14,600
to order, whereas individual 
production. 

163
00:11:14,600 --> 00:11:18,800
With its PLM, Focus has some 
limitation because it's not 

164
00:11:18,800 --> 00:11:22,300
standard therefore, epd 
integration to secure 

165
00:11:22,300 --> 00:11:24,600
collaborative, product 
development is needed. 

166
00:11:25,400 --> 00:11:29,800
Besides our A cloud 
implementation experience with 

167
00:11:29,800 --> 00:11:33,900
make to stalker sample to order.
Share has also one customer 

168
00:11:34,000 --> 00:11:37,700
Manta racing. 
That is already running its 

169
00:11:37,700 --> 00:11:42,100
businesses on cloud. 
Not only for cereal, but also, 

170
00:11:42,100 --> 00:11:46,300
for individual production, for a
custom, Porsche, for example, 

171
00:11:47,300 --> 00:11:51,300
man, type, or she has won the GT
class at the 24 hours of your 

172
00:11:51,300 --> 00:11:55,000
mat regarding engineer to order 
scenarios. 

173
00:11:55,500 --> 00:11:59,700
Currently, we are Facing the 
situation of how to integrate an

174
00:11:59,700 --> 00:12:04,000
external non sap PLM system into
the cloud with the P2P. 

175
00:12:04,900 --> 00:12:07,700
Thank you Loretta. 
Am you mentioned Monday racing, 

176
00:12:07,700 --> 00:12:10,100
have you driven a Porsche at 
their place? 

177
00:12:10,500 --> 00:12:14,300
Another Monday, for sure yet. 
What about you Marcus? 

178
00:12:15,000 --> 00:12:18,500
No, not yet, but maybe in the 
future of the collaboration with

179
00:12:18,500 --> 00:12:23,300
them, it's going as well as it 
is, you mentioned. 

180
00:12:24,500 --> 00:12:29,100
Okay, perfect, cool. 
Then you mentioned already 

181
00:12:29,100 --> 00:12:34,900
customers and I know you're 
implementing also at for a 

182
00:12:34,908 --> 00:12:38,000
different company as well and 
you touched a little bit on the 

183
00:12:38,000 --> 00:12:41,700
experience so far. 
And is it, is there more to add 

184
00:12:41,700 --> 00:12:44,500
or what other experiences are 
there so far? 

185
00:12:45,300 --> 00:12:48,900
Mmm, chairman through more than 
seven cloud implementations with

186
00:12:48,900 --> 00:12:53,000
customers today. 
So, one reference I also allowed

187
00:12:53,000 --> 00:12:56,000
to talk about is niaga spelled 
backwards. 

188
00:12:56,000 --> 00:13:01,500
It's Again it is a DSM startup 
offering innovative solutions 

189
00:13:01,500 --> 00:13:03,800
for recycling, in the 
manufacture of carpets and 

190
00:13:03,800 --> 00:13:06,700
mattresses with its own 
manufacturing facility in the 

191
00:13:06,700 --> 00:13:10,300
Netherlands to manage its 
operations. 

192
00:13:10,300 --> 00:13:15,300
Niaga needed a full scope 
manufacturing Erp solution but 

193
00:13:15,500 --> 00:13:21,200
adding Yaga business entities to
one of the existing GSM s Apec 

194
00:13:21,200 --> 00:13:25,500
systems was not the preferred 
solution and the as for Hana 

195
00:13:25,500 --> 00:13:30,600
Cloud was It to support all of 
naggers end-to-end processes 

196
00:13:30,600 --> 00:13:34,900
from Sales Direct, procurement 
production quality management, 

197
00:13:35,100 --> 00:13:38,700
warehousing Logistics and 
finance within sap Fury user 

198
00:13:38,700 --> 00:13:42,200
interface. 
Another client example together 

199
00:13:43,200 --> 00:13:47,000
with another client. 
We are also implementing the sap

200
00:13:47,000 --> 00:13:50,400
as for Hana cloud with full 
manufacturing and supply chain 

201
00:13:50,800 --> 00:13:56,400
and warehouse management already
in a later stage or together. 

202
00:13:56,500 --> 00:13:59,900
This client we are currently 
Gathering experiences how to 

203
00:13:59,900 --> 00:14:04,500
integrate a mes system, which 
requires read a lot of 

204
00:14:04,500 --> 00:14:08,300
integration in order to give 
manufacturing staff. 

205
00:14:08,300 --> 00:14:14,600
A clear overview of production, 
operations, and analytics for 

206
00:14:14,600 --> 00:14:20,800
the management team as mes or a 
shop floor system is the system 

207
00:14:20,800 --> 00:14:22,900
of record for a work in progress
data. 

208
00:14:23,800 --> 00:14:28,700
The central Lessons Learned From
This this project is basically 

209
00:14:28,700 --> 00:14:35,200
interfacing interfaces are 
working very well and almost 

210
00:14:35,200 --> 00:14:39,300
everything is possible in btp as
long as you have an API 

211
00:14:39,300 --> 00:14:43,700
available, Thank you. 
This is a very important point. 

212
00:14:43,700 --> 00:14:48,600
I think you made here, and if we
go more into the subject of 

213
00:14:48,600 --> 00:14:52,400
extensibility and 
configurability around sap as 

214
00:14:52,400 --> 00:14:55,300
Hana Cloud. 
What is your or your customers 

215
00:14:55,300 --> 00:14:59,900
perception there. 
Mmm from experience. 

216
00:14:59,900 --> 00:15:04,400
Crucial for success is to follow
the path of standard industry. 

217
00:15:04,400 --> 00:15:08,600
Best practices, really keep 
complexity out of the door and 

218
00:15:08,600 --> 00:15:12,000
run your business with. 
Words that does mean that 

219
00:15:12,000 --> 00:15:15,700
extensibility or configuration 
needs will never come up. 

220
00:15:15,700 --> 00:15:19,700
Of course, there are extension 
possibilities within an app 

221
00:15:19,700 --> 00:15:22,700
extension or set. 
PTP offers a standard way for 

222
00:15:22,700 --> 00:15:28,400
extending the as for Hana Cloud.
But the ultimate goal is not to 

223
00:15:28,400 --> 00:15:32,700
extend for many good reasons. 
However, if extensibility 

224
00:15:32,700 --> 00:15:37,100
requirements arise, before we 
immediately look for extensions,

225
00:15:38,700 --> 00:15:42,100
we look at the process. 
First, because maybe it's too 

226
00:15:42,100 --> 00:15:46,000
complicated. 
We then analyze the process with

227
00:15:46,000 --> 00:15:49,700
the client to look for 
simplifications and how we can 

228
00:15:49,700 --> 00:15:53,700
implement it within a standard 
as a process expert. 

229
00:15:53,700 --> 00:15:57,200
Chair is a preferred partner to 
support customers in Cloud 

230
00:15:57,200 --> 00:16:02,400
implementation, which follow the
path for or the path of best 

231
00:16:02,400 --> 00:16:07,100
practice and requirement 
requires process knowledge to do

232
00:16:07,100 --> 00:16:10,000
so. 
One example, I would like to 

233
00:16:10,000 --> 00:16:13,400
share with you is a, is a 
special achievement when it 

234
00:16:13,400 --> 00:16:16,900
comes to extensibility in 
process. 

235
00:16:16,900 --> 00:16:20,400
Manufacturing, for One customer 
share, created some business 

236
00:16:20,400 --> 00:16:26,200
rules reading the process order 
from the S4 Hana Cloud doing. 

237
00:16:26,200 --> 00:16:29,700
Then I conversion from 
components. 

238
00:16:30,000 --> 00:16:34,700
And after up the after the 
optimization the process, go 

239
00:16:34,700 --> 00:16:37,100
order goes back to this for 
cloud. 

240
00:16:37,300 --> 00:16:40,900
So that the client gets It's all
kind of components and different

241
00:16:40,900 --> 00:16:44,700
packaging sizes, which is the 
most optimal packaging size. 

242
00:16:45,000 --> 00:16:48,100
For example, if the process 
ordered and requires only 25 

243
00:16:48,100 --> 00:16:52,200
kilos, they do not need the 100 
kilo packaging size and this is 

244
00:16:52,200 --> 00:16:55,300
a special development be made 
with btp in the Netherlands, 

245
00:16:55,600 --> 00:16:59,000
which works quite well. 
Very nice. 

246
00:16:59,000 --> 00:17:01,700
Very nice. 
Thanks for sharing this concrete

247
00:17:01,700 --> 00:17:04,500
example. 
And if we go into the direction 

248
00:17:04,500 --> 00:17:08,900
of end-to-end, business, 
scenarios or content, here we 

249
00:17:08,900 --> 00:17:12,200
had sap have been focusing on 
many end-to-end business, 

250
00:17:12,200 --> 00:17:15,000
scenarios around manufacturing 
and supply chain. 

251
00:17:15,700 --> 00:17:19,000
And also, including, of course 
sales, procurement finance. 

252
00:17:19,599 --> 00:17:22,900
And to end, of course, and 
especially in the areas of make 

253
00:17:22,900 --> 00:17:27,300
to stalk, or made-to-order with,
or without variant configuration

254
00:17:27,300 --> 00:17:30,700
or serial Management. 
And what is your, and your 

255
00:17:30,700 --> 00:17:34,000
customers user experience? 
Or yeah. 

256
00:17:34,100 --> 00:17:35,700
What do you think are your 
customers? 

257
00:17:35,700 --> 00:17:38,100
Think about this into any 
business scenarios? 

258
00:17:38,100 --> 00:17:41,500
Where you develop now? 
Mmm, well end-to-end. 

259
00:17:41,500 --> 00:17:44,700
Prospective, as you said, Marcus
is imperative. 

260
00:17:45,700 --> 00:17:50,800
We are not looking at single 
business units, like, CRM sales,

261
00:17:50,800 --> 00:17:53,400
finance and so on, but rather, 
we walk through the end-to-end 

262
00:17:53,400 --> 00:17:57,300
processes, defining little Cash 
Source to pay designed to 

263
00:17:57,300 --> 00:17:59,500
operate. 
And so, Go on in workshops with 

264
00:17:59,500 --> 00:18:03,100
all the business units. 
An example that nicely 

265
00:18:03,100 --> 00:18:06,600
demonstrates, the end-to-end 
perspective, with end-to-end 

266
00:18:06,600 --> 00:18:09,200
Master data comes from anti 
racing again. 

267
00:18:09,600 --> 00:18:13,300
They did the cloud 
implementation itself with 

268
00:18:13,300 --> 00:18:18,400
another partner first. 
But in retrospective, not enough

269
00:18:18,400 --> 00:18:22,800
time was spent exploring best 
practice processes in the 

270
00:18:22,800 --> 00:18:26,800
so-called Discovery phase. 
They realized then that they 

271
00:18:27,800 --> 00:18:30,100
did. 
Have enough process knowledge on

272
00:18:30,100 --> 00:18:34,700
how to implement stock of 
material provided to vendor and 

273
00:18:34,700 --> 00:18:36,800
the processor and outside the 
system. 

274
00:18:36,800 --> 00:18:42,200
First at this point share with 
its process expertise came in 

275
00:18:42,400 --> 00:18:45,600
and implemented the standard 
process for this scenario in the

276
00:18:45,600 --> 00:18:48,200
public Cloud for month. 
I that starts. 

277
00:18:48,500 --> 00:18:52,800
As you said, way up front and 
master data management in a 

278
00:18:52,800 --> 00:18:56,200
nutshell, the essential lessons 
learned from this project is 

279
00:18:56,900 --> 00:19:02,600
really to And enough time, 
exploring the best practices at 

280
00:19:02,600 --> 00:19:07,500
the beginning of the project, 
with a partner with strong 

281
00:19:07,500 --> 00:19:11,500
process expertise. 
Otherwise you will find it very 

282
00:19:11,500 --> 00:19:14,900
difficult and to implement the 
customers business processes 

283
00:19:14,900 --> 00:19:18,600
within the standard and within 
the essay, PS4 Hana Cloud. 

284
00:19:18,700 --> 00:19:21,300
Definitely. 
Thanks Larisa. 

285
00:19:21,500 --> 00:19:25,700
Also for this clarification and 
having, if I would be a 

286
00:19:25,708 --> 00:19:29,700
manufacturing company and I 
would go to Larisa and call you 

287
00:19:29,700 --> 00:19:35,100
up and ask about SPS. 
Hana Cloud at what point would 

288
00:19:35,100 --> 00:19:38,100
you get careful and maybe advise
a private Cloud for me? 

289
00:19:38,600 --> 00:19:45,000
Yeah, so first of all, it's 
necessary that customers choose 

290
00:19:45,000 --> 00:19:47,200
the deployment option. 
That best Suites their business 

291
00:19:47,200 --> 00:19:52,000
needs budget and resources. 
But nevertheless if you will 

292
00:19:52,000 --> 00:19:55,500
call me Marcus a secondly, we 
are in the middle of a huge 

293
00:19:55,500 --> 00:19:58,900
change. 
And Cloud will be the solution 

294
00:19:58,900 --> 00:20:03,400
in the long term. 
A lot of this a lot as possible 

295
00:20:03,400 --> 00:20:07,900
with PTP and Sir provides you, 
the latest technology on a 

296
00:20:07,900 --> 00:20:13,500
regular basis while with private
Cloud, you have to secure this 

297
00:20:13,500 --> 00:20:17,400
on your own Rhythm. 
And from experience, we know 

298
00:20:17,400 --> 00:20:21,700
that customers tend to postpone 
this Due to the immense testing 

299
00:20:21,700 --> 00:20:26,900
effort, which is not required 
with wireless wireless that our 

300
00:20:26,900 --> 00:20:29,200
pace, for example, in the Cloud 
public Cloud. 

301
00:20:30,100 --> 00:20:35,500
However, if you would call me 
Marcos regulated Industries or 

302
00:20:35,500 --> 00:20:41,700
an example, I would get careful 
and think, twice, or if a cloud 

303
00:20:41,700 --> 00:20:44,000
mindset, just can't get 
involved. 

304
00:20:44,800 --> 00:20:47,500
Okay, fair enough. 
Yeah, two good points. 

305
00:20:47,700 --> 00:20:52,500
I thank you for your advice. 
I will write those down and what

306
00:20:52,500 --> 00:20:56,300
kind of questions about security
for example in a software as a 

307
00:20:56,300 --> 00:20:58,200
service Cloud setting? 
Do you get from your 

308
00:20:58,200 --> 00:21:00,800
manufacturing customers? 
Yeah. 

309
00:21:01,200 --> 00:21:04,100
The question, can anyone access 
my data? 

310
00:21:04,600 --> 00:21:10,400
Frankly it's a common question. 
Yes, first we have more than 70 

311
00:21:10,400 --> 00:21:13,000
location for data centers 
available. 

312
00:21:13,000 --> 00:21:16,100
Every customer has the freedom. 
Choice of which location its 

313
00:21:16,100 --> 00:21:22,100
preferred and backup processes, 
physical security of data and 

314
00:21:22,100 --> 00:21:27,200
much more avoidable tool. 
Apart from that, I would often 

315
00:21:27,200 --> 00:21:30,200
ask how the data is currently 
secured. 

316
00:21:30,500 --> 00:21:34,600
And I have already experienced 
that the team could access the 

317
00:21:34,600 --> 00:21:38,900
Erp environment without any VPN 
or that customers had no 

318
00:21:38,900 --> 00:21:43,400
firewalls. 
So, my key message is Data, 

319
00:21:43,400 --> 00:21:47,000
Centers offered. 
The security with the strictest 

320
00:21:47,000 --> 00:21:51,100
industry standards which is 
mostly more than each customer 

321
00:21:51,100 --> 00:21:55,400
could do on its own. 
If you have a hosted environment

322
00:21:55,400 --> 00:21:59,200
with another provider than sap, 
you ask yourself exactly the 

323
00:21:59,200 --> 00:22:04,000
same questions spitting the the 
ideal will further and what kind

324
00:22:04,000 --> 00:22:07,900
of mindset do manufacturing 
customers need when they decide 

325
00:22:07,900 --> 00:22:12,500
to implement as a PS4 on a 
cloud, the transition to the 

326
00:22:12,500 --> 00:22:16,600
cloud is not just Bridging, the 
functional solution Gap. 

327
00:22:16,900 --> 00:22:21,200
It's a different mindset 
definitely such as the protest a

328
00:22:21,200 --> 00:22:24,800
project approach, the 
implementation engagement, 

329
00:22:24,800 --> 00:22:28,800
customer interaction. 
For example, instead of fitting 

330
00:22:29,400 --> 00:22:32,600
the solution to the business, 
the focus is really on fitting 

331
00:22:32,600 --> 00:22:36,000
the business to the standard. 
Best practice solution while 

332
00:22:36,000 --> 00:22:40,300
still allowing configuration. 
Of course, from our experience, 

333
00:22:40,300 --> 00:22:47,500
a cloud meant mindset implies 
Embracing change deploying, best

334
00:22:47,500 --> 00:22:51,900
practice Solutions, and 
promoting self-control not 

335
00:22:51,900 --> 00:22:54,300
building any more but 
configuring. 

336
00:22:55,600 --> 00:23:00,700
Very well said Larisa and 
promoting self control, I'll 

337
00:23:00,700 --> 00:23:04,400
remember that. 
And when we think about the 

338
00:23:04,400 --> 00:23:09,600
cloud mindset little bit further
and is not only important for 

339
00:23:09,600 --> 00:23:14,100
customers but also differs it 
from the traditional as a PS4 

340
00:23:14,100 --> 00:23:16,400
Hannah on premise approach or 
where's the difference? 

341
00:23:16,400 --> 00:23:20,600
They're totally agree with you. 
Marcus as a partner for 

342
00:23:20,600 --> 00:23:24,300
customers on their way to sap as
for Hana Cloud. 

343
00:23:24,300 --> 00:23:29,400
It is Our responsibility in to 
introduce not only the customer 

344
00:23:29,400 --> 00:23:33,500
but also our consultants and 
sales people today 

345
00:23:33,500 --> 00:23:37,800
implementation shift between the
more traditional on-premise and 

346
00:23:37,800 --> 00:23:41,100
Cloud which is much more 
transformative. 

347
00:23:42,700 --> 00:23:46,600
Okay, thank you and you already 
mentioned it. 

348
00:23:46,700 --> 00:23:50,100
You are an sap partner with 
strong, focus on sap as funnel 

349
00:23:50,100 --> 00:23:54,500
cloud, and I heard you actually 
read as well. 

350
00:23:55,000 --> 00:23:58,500
You building up a team Larisa 
and expertise in Switzerland? 

351
00:23:59,000 --> 00:24:02,300
Meaning, you invest a lot as a 
company, very, you see the 

352
00:24:02,300 --> 00:24:06,000
benefit for a new business model
with this approach, especially 

353
00:24:06,000 --> 00:24:10,800
in the manufacturing and supply 
chain world since the first 

354
00:24:10,800 --> 00:24:13,400
release of sap. 
Yes, for Hannah Public Cloud 

355
00:24:14,300 --> 00:24:18,200
regularly update us updates, 
with significant additional 

356
00:24:18,200 --> 00:24:22,400
functions, have followed a few 
years ago to be honest. 

357
00:24:22,400 --> 00:24:26,000
At this time the cloud was 
hardly an issue for 

358
00:24:26,000 --> 00:24:29,000
manufacturers because 
manufacturing processes are not 

359
00:24:29,000 --> 00:24:33,900
Commodities but multi-tenant 
Cloud systems are predetermined 

360
00:24:33,900 --> 00:24:38,100
for commodity processes. 
This is, this is actually the 

361
00:24:38,100 --> 00:24:42,400
reason why Professional Services
or HR or Finance Science 

362
00:24:42,400 --> 00:24:46,000
developed better straight from 
the beginning in the cloud. 

363
00:24:46,800 --> 00:24:51,200
After a couple of years. 
Now, PTP solves that problem and

364
00:24:51,200 --> 00:24:54,300
cloudier P. 
Manufacturing is at the top of 

365
00:24:54,300 --> 00:24:56,500
many companies to do lists right
now. 

366
00:24:57,200 --> 00:25:02,100
Why do I say manufacturing? 
I mean, because especially the 

367
00:25:02,100 --> 00:25:06,200
manufacturing industry is so 
trained to for Best Practices 

368
00:25:06,500 --> 00:25:10,400
manufacturers have lean 
production management Six Sigma 

369
00:25:10,400 --> 00:25:15,500
principles since Here's which is
exactly what the public Cloud 

370
00:25:15,500 --> 00:25:19,100
stands for. 
Really keep complexity out of 

371
00:25:19,100 --> 00:25:21,900
the door and run your business 
with standards. 

372
00:25:22,600 --> 00:25:27,200
And yeah, with that said, I see 
the benefit for a new business 

373
00:25:27,200 --> 00:25:30,900
model with this approach. 
Especially in the manufacturing,

374
00:25:30,900 --> 00:25:34,100
the supply chain World. 
Thanks for your insights 

375
00:25:34,100 --> 00:25:37,000
Larissa. 
And if we had one wish from SRP,

376
00:25:37,100 --> 00:25:41,700
what would that be one? 
Wish honestly. 

377
00:25:41,700 --> 00:25:46,500
I I have the same expectations 
as for ourselves internally at 

378
00:25:46,500 --> 00:25:50,200
share and for all other partners
and the world as well. 

379
00:25:50,800 --> 00:25:55,500
We all have to upskill 
ourselves, our consultants, and 

380
00:25:55,500 --> 00:26:00,500
salespersons and make them 
future-ready and familiar with 

381
00:26:00,500 --> 00:26:03,800
the cloud mindset and the 
different implementation 

382
00:26:03,800 --> 00:26:09,600
approach as well. 
We are all coming from this ECC 

383
00:26:09,600 --> 00:26:12,700
world. 
We have to Really take the 

384
00:26:12,700 --> 00:26:17,000
responsibility for shaping the 
future together with clients and

385
00:26:17,000 --> 00:26:22,500
not only to copy an outdated ECC
world, and its processes into a 

386
00:26:22,500 --> 00:26:25,400
cloud environment. 
Even if this would be the path 

387
00:26:25,400 --> 00:26:29,800
of last at least resistance, 
businesses are tackling other 

388
00:26:29,800 --> 00:26:33,900
challenges in the 21st century 
which is why new business models

389
00:26:33,900 --> 00:26:36,700
are needed. 
Very good. 

390
00:26:36,800 --> 00:26:39,500
Awesome. 
I remember that Larissa. 

391
00:26:39,500 --> 00:26:43,600
And to enter the initial 
question, is it still a myth or 

392
00:26:43,600 --> 00:26:46,500
already a reality that 
manufacturing companies can work

393
00:26:46,500 --> 00:26:50,000
with as a PS4 Hana Cloud? 
Manufacturing world is going 

394
00:26:50,000 --> 00:26:53,800
Cloud. 
The manufacturing world is going

395
00:26:53,800 --> 00:26:57,900
Cloud. 
I really like that Larissa and 

396
00:26:58,000 --> 00:27:01,400
yeah, that's actually a good. 
Very good note to end this 

397
00:27:01,400 --> 00:27:05,600
episode on Marissa head of 
manufacturing at sap partner. 

398
00:27:05,800 --> 00:27:09,800
Share, thank you very much for 
joining and answering the 

399
00:27:09,800 --> 00:27:13,100
questions software as a service 
and Manufacturing myth or 

400
00:27:13,100 --> 00:27:16,800
reality, and sharing your 
insights about sop as Hana 

401
00:27:16,800 --> 00:27:20,900
Cloud. 
If you all enjoyed today's 

402
00:27:20,900 --> 00:27:24,300
discussion and would like to 
learn more, stay tuned for the 

403
00:27:24,300 --> 00:27:29,500
next one, as always feel free to
drop us an email via inside as 

404
00:27:29,500 --> 00:27:35,200
for ad sap.com/learnbi, which 
topics are of your interest. 

405
00:27:35,800 --> 00:27:39,600
Tune in next time and be inside.
Sap is for Hannah.

