1
00:00:09,960 --> 00:00:13,960
Welcome to the podcast inside 
SAP Sahana Cloud. 

2
00:00:14,120 --> 00:00:17,760
There's no customer success 
without product success and 

3
00:00:17,760 --> 00:00:21,080
project success. 
I'm your host, Mark Surtlet and 

4
00:00:21,080 --> 00:00:24,960
today we will talk about how 
Rush manages their quality batch

5
00:00:24,960 --> 00:00:27,120
release process with the help of
SAP. 

6
00:00:27,280 --> 00:00:30,600
As for HANA and SAP Batch 
Release Hub, which was Co 

7
00:00:30,600 --> 00:00:34,080
innovative with Rush. 
But First things first, let's 

8
00:00:34,080 --> 00:00:38,080
introduce our guests. 
Melanie Fabian, welcome to this 

9
00:00:38,080 --> 00:00:40,360
podcast. 
You've studied in Kiel and 

10
00:00:40,360 --> 00:00:45,080
received your probation as a 
pharmacist since I think 1996. 

11
00:00:45,080 --> 00:00:48,520
You held various positions in 
pharma manufacturing and quality

12
00:00:48,520 --> 00:00:51,960
management. 
And if I'm right, in 2007, you 

13
00:00:51,960 --> 00:00:53,840
joined Rush. 
What else would you like to 

14
00:00:53,840 --> 00:00:56,560
share about yourself? 
Thank you for the introduction. 

15
00:00:56,560 --> 00:00:59,480
Yeah, that's correct. 
So I'm by training a pharmacist.

16
00:00:59,480 --> 00:01:02,200
I have worked in the 
Pharmaceutical industry in the 

17
00:01:02,200 --> 00:01:05,680
area of the IMP. 
So that's the introduction of 

18
00:01:05,680 --> 00:01:09,640
new medicines, new molecules. 
But then I have also gained 

19
00:01:09,640 --> 00:01:11,400
experience in the commercial 
area. 

20
00:01:11,400 --> 00:01:15,920
And that's also the reason why I
joined the Rush project to 

21
00:01:15,920 --> 00:01:20,720
introduce the new S 400 system 
and also to have a strong 

22
00:01:20,720 --> 00:01:25,240
position to make the new tools 
available for commercial, the 

23
00:01:25,240 --> 00:01:28,080
drug, substance, drug product 
and finish good release, but 

24
00:01:28,080 --> 00:01:30,120
also for the development 
products. 

25
00:01:30,560 --> 00:01:33,440
Thank you so much, Melanie, for 
this great introduction of 

26
00:01:33,440 --> 00:01:37,520
yourself, and I'm also welcoming
Dr. Marco Strohmeyer. 

27
00:01:37,600 --> 00:01:39,720
Marco, also welcome to this 
podcast. 

28
00:01:39,760 --> 00:01:44,560
I know you studied in Stuttgart 
and received your PhD in Biology

29
00:01:44,560 --> 00:01:48,040
at the University of Heidelberg.
You joined Rush also, I think in

30
00:01:48,040 --> 00:01:53,440
2007 in biotech manufacturing 
and then joined Quality in 2015.

31
00:01:53,520 --> 00:01:55,080
What else would you like to tell
our audience? 

32
00:01:55,720 --> 00:01:57,120
Hello, Marcus. 
Thank you for this nice 

33
00:01:57,120 --> 00:01:58,960
introduction. 
It's also a pleasure for me to 

34
00:01:58,960 --> 00:02:01,840
be here and talk about a little 
bit of topics you mentioned 

35
00:02:01,840 --> 00:02:05,440
before with the start in at Hosh
in the manufacturing area, I was

36
00:02:05,440 --> 00:02:08,479
already deeply involved in a lot
of challenging topics from the 

37
00:02:08,479 --> 00:02:11,280
manufacturing processes. 
And then when I went over to 

38
00:02:11,280 --> 00:02:15,080
quality, it was clear that 
process validation and set up is

39
00:02:15,080 --> 00:02:17,640
basically my passion. 
And then based with this 

40
00:02:17,640 --> 00:02:22,040
knowledge, I also made an an 
education as Lindsey Sigma Green

41
00:02:22,040 --> 00:02:26,080
and then later as Black Belt and
with the strong focus on batch 

42
00:02:26,080 --> 00:02:28,800
process management and process 
optimization. 

43
00:02:28,800 --> 00:02:31,320
And then also joined S 
Millennium at the same time the 

44
00:02:31,560 --> 00:02:33,720
project for the S4 
implementation. 

45
00:02:33,720 --> 00:02:37,760
And then of course it was a very
good thing to join SAP in the Co

46
00:02:37,760 --> 00:02:41,080
innovation, to go forward with 
the BIH and to contribute with 

47
00:02:41,080 --> 00:02:42,560
the knowledge I have collected 
during the. 

48
00:02:42,560 --> 00:02:44,000
Past years. 
Great. 

49
00:02:44,000 --> 00:02:46,640
Thank you, Marco. 
I'm excited to hear more about 

50
00:02:46,640 --> 00:02:49,880
your passion. 
Also, we welcome Aladdin. 

51
00:02:49,880 --> 00:02:52,680
Aladdin, we know you from our 
first quality management 

52
00:02:52,680 --> 00:02:55,720
podcast. 
I think it was episode 79, but 

53
00:02:55,720 --> 00:02:58,120
it would be nice if you 
introduce yourself quickly as 

54
00:02:58,120 --> 00:02:59,920
well. 
Great to be here again. 

55
00:03:00,000 --> 00:03:03,000
I am currently the Director of 
Product Marketing in the Life 

56
00:03:03,000 --> 00:03:06,560
Sciences industry and Healthcare
Business unit at SAB where my 

57
00:03:06,560 --> 00:03:10,680
rule focuses heavily on solution
evangelizing in the industry to 

58
00:03:10,680 --> 00:03:14,440
explain the real business value 
behind them and unlock 

59
00:03:14,440 --> 00:03:16,680
improvement potential for SAB 
customers. 

60
00:03:16,880 --> 00:03:20,920
My career in the life industry 
spends over a decade where I 

61
00:03:20,920 --> 00:03:24,520
have had the privilege of 
working in leadership positions 

62
00:03:24,520 --> 00:03:28,440
at some fantastic companies like
Johnson and Johnson, McCabe, 

63
00:03:28,440 --> 00:03:30,400
Carter Pulmonary and Drager 
Medical. 

64
00:03:30,440 --> 00:03:33,560
During these years, I focused on
quality and regulatory 

65
00:03:33,560 --> 00:03:37,240
compliance, continuous 
improvement, Lean 6 Sigma and 

66
00:03:37,280 --> 00:03:39,440
enterprise project portfolio 
management. 

67
00:03:40,120 --> 00:03:42,840
Thank you very much, Aladdin. 
Also welcome again to our 

68
00:03:42,840 --> 00:03:46,560
listeners that might not be so 
familiar with the Pharmaceutical

69
00:03:46,560 --> 00:03:49,360
industry. 
You need to be able to trace 

70
00:03:49,360 --> 00:03:52,480
products and batches throughout 
the supply chain. 

71
00:03:52,680 --> 00:03:55,640
You even have compliance 
standards that regulate batch 

72
00:03:55,640 --> 00:03:58,520
management. 
And data management is very 

73
00:03:58,520 --> 00:04:02,120
important as a vast amount of 
data is created during the batch

74
00:04:02,120 --> 00:04:05,080
management process. 
So from production, quality 

75
00:04:05,080 --> 00:04:07,640
control data and also testing 
data. 

76
00:04:07,640 --> 00:04:11,320
So analysing this data is not 
always easy and very important. 

77
00:04:11,320 --> 00:04:15,000
Efficiency and batch management 
is also the key to maintain 

78
00:04:15,000 --> 00:04:17,440
profitability and meeting 
customer demand. 

79
00:04:17,519 --> 00:04:20,200
Melania and Marco Rush is 
handling their quality 

80
00:04:20,200 --> 00:04:23,880
management processes, especially
batches in a world class way. 

81
00:04:23,960 --> 00:04:28,200
Tell us about your role, please.
My role in this project is to 

82
00:04:28,240 --> 00:04:33,040
contribute to the release 
process that we have to set up 

83
00:04:33,080 --> 00:04:37,200
in this global tool in S4. 
And we have, of course, the 

84
00:04:37,400 --> 00:04:40,640
knowledge what is relevant for 
the release process. 

85
00:04:40,720 --> 00:04:44,000
And with that knowledge, we can 
then come up with the right 

86
00:04:44,000 --> 00:04:48,120
technical solutions that are 
required to help the future 

87
00:04:48,120 --> 00:04:52,240
users to have the right system, 
but also the right checks in 

88
00:04:52,240 --> 00:04:55,680
place that are relevant and what
are expected from our 

89
00:04:55,720 --> 00:04:58,000
regulations. 
Brilliant, Melanie. 

90
00:04:58,000 --> 00:05:00,000
Thanks. 
And Marco, would you like to add

91
00:05:00,000 --> 00:05:02,680
something? 
So as many, I'm also a business 

92
00:05:02,680 --> 00:05:05,880
process expert and starting with
the project to implement. 

93
00:05:05,920 --> 00:05:09,840
As for Hannah at Rush, our main 
goal was to start really on 

94
00:05:09,840 --> 00:05:13,480
Greenfield to define the right 
system landscape using as far as

95
00:05:13,480 --> 00:05:17,880
the digital backbone and where 
we then basically enable a lean 

96
00:05:17,920 --> 00:05:21,200
and fully supply chain 
integrated quality management. 

97
00:05:21,280 --> 00:05:25,440
And so with that topics like 
aviation management, Kappa and 

98
00:05:25,440 --> 00:05:28,120
change management, risk 
management or also the 

99
00:05:28,120 --> 00:05:31,440
integration of QC testing into 
the system, we are of focus. 

100
00:05:31,440 --> 00:05:34,400
And then basically all of that 
information are relevant then 

101
00:05:34,400 --> 00:05:36,880
for the batch release. 
And as Melanie has explained, 

102
00:05:36,880 --> 00:05:40,400
which is this is then the final 
tool we wanted to provide within

103
00:05:40,400 --> 00:05:44,080
the project that the batch 
release is enabled in a fast and

104
00:05:44,080 --> 00:05:46,600
lean way. 
And therefore basically the Co 

105
00:05:46,600 --> 00:05:49,920
innovation was just coming in 
the right time so that we then 

106
00:05:49,920 --> 00:05:53,760
could join and benefit from this
full integration of the final 

107
00:05:53,760 --> 00:05:57,640
tool into the S4 system to make 
our vision come true that we 

108
00:05:57,640 --> 00:06:00,920
have this lean fully integrated 
release concept available. 

109
00:06:01,200 --> 00:06:04,120
We are not only the quality 
processes are integrated, but 

110
00:06:04,120 --> 00:06:07,880
also the production process, the
assets management and so on, so 

111
00:06:07,880 --> 00:06:10,640
that we have the full overview 
and finally in the release on 

112
00:06:10,640 --> 00:06:13,040
the batch datos on the 
compliance requirements that 

113
00:06:13,040 --> 00:06:16,160
need to be fulfilled. 
Thank you, Melanie and Marco. 

114
00:06:16,240 --> 00:06:19,440
Marco, you already mentioned 
Asfahana is the heart of your IT

115
00:06:19,600 --> 00:06:22,680
system landscape. 
When we look at the global batch

116
00:06:22,680 --> 00:06:25,840
release solution that you Co 
developed with us, how did the 

117
00:06:25,840 --> 00:06:29,280
Co innovation start or when did 
you know? 

118
00:06:29,320 --> 00:06:32,640
Yeah, you needed something 
outside Asfahana as a core. 

119
00:06:33,200 --> 00:06:35,840
The point is that S for Hannah 
in the direction of batch 

120
00:06:35,840 --> 00:06:39,480
release with the standard 
functionality was very early 

121
00:06:39,480 --> 00:06:43,040
identified as not suitable for 
actually the replacement of our 

122
00:06:43,040 --> 00:06:46,880
legacy tool we have which was a 
quite advanced and custom built 

123
00:06:47,080 --> 00:06:49,160
tool. 
Standard functionalities with 

124
00:06:49,160 --> 00:06:52,280
the transactions and so on were 
of course not sufficient to 

125
00:06:52,280 --> 00:06:55,920
support this activities in a 
full compliant and easy to use 

126
00:06:55,920 --> 00:06:57,840
way. 
So this was the reason why we 

127
00:06:57,840 --> 00:07:00,560
have identified that we need to 
replace this standard 

128
00:07:00,560 --> 00:07:02,720
functionality with the add on 
for BRH. 

129
00:07:03,200 --> 00:07:07,720
May I add to that, we have also 
a lot of systems which are not 

130
00:07:07,720 --> 00:07:11,960
in the SAP system but are also 
relevant for the final release 

131
00:07:11,960 --> 00:07:14,320
of a bitch. 
So we have other systems that 

132
00:07:14,320 --> 00:07:18,120
deliver data for the release 
process like a limb system that 

133
00:07:18,120 --> 00:07:21,880
is containing quality control 
data of the testing. 

134
00:07:21,880 --> 00:07:25,360
We have also a deviation 
management system which is a 

135
00:07:25,360 --> 00:07:28,440
different system that is 
delivering data for the release 

136
00:07:28,440 --> 00:07:30,840
process. 
And so we have other systems 

137
00:07:30,840 --> 00:07:35,440
like a bitch trace system, 
serialization system, a system 

138
00:07:35,440 --> 00:07:39,440
which is doing our regulation, 
supporting our filings and the 

139
00:07:39,440 --> 00:07:42,240
release to the markets in the 
various countries. 

140
00:07:42,320 --> 00:07:46,040
Those systems are all containing
data which are relevant for our 

141
00:07:46,040 --> 00:07:49,680
release and we have to bring 
these data into a centralized 

142
00:07:49,680 --> 00:07:54,440
place And the standard SAP 
system does not really offer 

143
00:07:54,440 --> 00:07:56,920
this place. 
And we have now is a batch 

144
00:07:56,920 --> 00:08:00,120
release up found a way to bring 
in data which we can then 

145
00:08:00,120 --> 00:08:03,080
consume during the release 
process and also have them 

146
00:08:03,200 --> 00:08:04,920
automatically checked in certain
areas. 

147
00:08:04,920 --> 00:08:07,960
So that's the benefit of this 
stand alone tool that we have 

148
00:08:07,960 --> 00:08:10,240
now developed. 
So it's connected with S4. 

149
00:08:10,360 --> 00:08:12,760
That was very important for us. 
Great to hear. 

150
00:08:12,880 --> 00:08:14,320
Thanks for sharing your 
insights. 

151
00:08:14,440 --> 00:08:17,800
Let's move maybe more to the 
internal project set up. 

152
00:08:17,880 --> 00:08:21,160
When you started this project, 
how did you set it up? 

153
00:08:21,160 --> 00:08:24,080
What did it look like and how 
was the working model with 

154
00:08:24,080 --> 00:08:25,920
SAPOS? 
How did that work? 

155
00:08:26,440 --> 00:08:28,760
Yeah, Marcus. 
So the internal setup was that 

156
00:08:28,760 --> 00:08:32,039
we have been actually a quite 
small team with two business 

157
00:08:32,039 --> 00:08:36,640
experts mainly and one IT expert
supporting us in this area. 

158
00:08:36,720 --> 00:08:39,799
And then we expanded, I would 
say right through to two 

159
00:08:39,799 --> 00:08:43,200
additional people, more from the
business point of view that are 

160
00:08:43,200 --> 00:08:46,920
bringing more business expertise
with them for also checking for 

161
00:08:46,920 --> 00:08:50,760
compliance topics and so on. 
So with the small team of up to 

162
00:08:50,760 --> 00:08:55,800
5-6 people, we coordinated them 
with SAP on this BIH topic. 

163
00:08:55,920 --> 00:08:59,680
And in that Co innovation, which
was really well driven by SAP, 

164
00:08:59,680 --> 00:09:03,080
we were basically more like 
consulted for the different 

165
00:09:03,080 --> 00:09:05,480
requirements. 
We also had the topics to 

166
00:09:05,560 --> 00:09:08,840
explain actually SAP how batch 
release is working and what are 

167
00:09:08,840 --> 00:09:10,480
the compliance requirements, 
right. 

168
00:09:10,800 --> 00:09:14,480
So this developed and over the 
time and internally we of course

169
00:09:14,480 --> 00:09:17,560
had also our steering committees
also thank you to the sponsors 

170
00:09:17,560 --> 00:09:21,120
of this project that were 
supporting us also was giving 

171
00:09:21,120 --> 00:09:24,760
guidance and aligning these 
activities of the BIH Co 

172
00:09:24,760 --> 00:09:27,560
innovation with the big S4 
implementation project 

173
00:09:27,560 --> 00:09:29,960
activities so that we could stay
connected. 

174
00:09:29,960 --> 00:09:33,360
Of course, we had benefited from
the fact that we have this big 

175
00:09:33,360 --> 00:09:36,880
S4 implementation project so 
that the BIH Co innovation was a

176
00:09:36,880 --> 00:09:39,720
small sub project of that. 
So we could use the whole 

177
00:09:39,720 --> 00:09:42,440
infrastructure of the big 
project as well. 

178
00:09:42,800 --> 00:09:45,720
But nevertheless, it was 
basically a small team which 

179
00:09:45,720 --> 00:09:48,920
made us also very quick in 
decision making and responding 

180
00:09:48,920 --> 00:09:50,480
to the needs of the Co 
innovation. 

181
00:09:50,800 --> 00:09:53,960
That's good to hear. 
And let's move back to you, 

182
00:09:53,960 --> 00:09:56,680
Aladdin. 
When SAP started to Co innovate 

183
00:09:56,680 --> 00:10:00,360
with Rush, what was your role 
and how did our internal setup 

184
00:10:00,360 --> 00:10:02,760
look like? 
Marcus Our journey with Roche 

185
00:10:02,760 --> 00:10:06,440
began with the shared division 
for creating an innovative 

186
00:10:06,440 --> 00:10:10,400
solution that meets the needs of
the life sciences industry at 

187
00:10:10,400 --> 00:10:12,680
all. 
At ECB, we have a well 

188
00:10:12,680 --> 00:10:16,360
established process and best 
practices for Co innovation and 

189
00:10:16,360 --> 00:10:19,360
we assembled a professional 
cross functional team that 

190
00:10:19,360 --> 00:10:22,960
included experts from product 
engineering, product management 

191
00:10:22,960 --> 00:10:25,960
and product marketing. 
This team worked closely with 

192
00:10:25,960 --> 00:10:29,360
Roche, adopting a project 
management approach with clear 

193
00:10:29,360 --> 00:10:32,560
milestones and deliverables to 
ensure seamless execution. 

194
00:10:32,680 --> 00:10:36,480
From the beginning, we imprised 
a collaborative spirit at each 

195
00:10:36,480 --> 00:10:38,800
milestone. 
We held show and tell sessions 

196
00:10:38,800 --> 00:10:42,720
with Roche, where we showcased 
what had been developed and 

197
00:10:42,720 --> 00:10:46,160
gathered their feedback. 
These sessions were crucial in 

198
00:10:46,160 --> 00:10:50,040
streamlining communication and 
ensuring mutual agreement at 

199
00:10:50,040 --> 00:10:51,920
every stage. 
Of course, these regular 

200
00:10:51,920 --> 00:10:55,080
meetings with Roche allowed us 
to deep dive into their 

201
00:10:55,080 --> 00:10:58,640
requirement, which we then 
validated against broader 

202
00:10:58,640 --> 00:11:01,600
industry standards. 
This collaborative approach not 

203
00:11:01,600 --> 00:11:04,680
only made the project run 
smoothly, but also built a 

204
00:11:04,680 --> 00:11:08,400
strong partnership with Roche 
showing how Co innovation can 

205
00:11:08,400 --> 00:11:11,920
create a solution that is really
solve a business challenge. 

206
00:11:12,000 --> 00:11:16,160
Now when come to my rule in that
project, my main rule has been 

207
00:11:16,160 --> 00:11:20,240
in sharing industry requirements
during the engineering process 

208
00:11:20,240 --> 00:11:23,200
to make sure that the batch 
release hub is a standard 

209
00:11:23,200 --> 00:11:27,520
industry solution that meets not
only the need of Roche but the 

210
00:11:27,520 --> 00:11:30,400
entire industry. 
My focus after the successful 

211
00:11:30,400 --> 00:11:34,120
launch of the has been on 
evangelizing this solution 

212
00:11:34,120 --> 00:11:37,680
within the industry and to key 
industry leaders with the goal 

213
00:11:37,680 --> 00:11:42,360
of highlighting the immense 
value it brings not only in 

214
00:11:42,360 --> 00:11:46,000
streamlining batch release 
management process, but also in 

215
00:11:46,000 --> 00:11:48,800
boosting overall supply chain 
performance. 

216
00:11:48,800 --> 00:11:52,840
It's really incredible rewarding
to see how our innovations 

217
00:11:52,840 --> 00:11:56,640
together with Roche can truly be
game changers addressing real 

218
00:11:56,640 --> 00:11:59,920
business challenges. 
We have seen interest not only 

219
00:11:59,920 --> 00:12:02,840
from the life sciences industry 
about batteries hub but also 

220
00:12:02,840 --> 00:12:05,440
from other industries like 
consumers for example. 

221
00:12:05,960 --> 00:12:08,320
Take care, Aladeen, this is very
interesting. 

222
00:12:08,360 --> 00:12:11,840
Also mentioning other industries
here that contacted you after 

223
00:12:11,840 --> 00:12:14,280
this Co innovation has been 
finished. 

224
00:12:14,400 --> 00:12:17,680
Melanie, one more question to 
you, Marco already mentioned 

225
00:12:17,680 --> 00:12:19,840
that we had SAP. 
We learned a lot about batch 

226
00:12:19,840 --> 00:12:22,920
management or batch release 
management from you from Rush. 

227
00:12:22,960 --> 00:12:25,720
But what were some other 
challenges within the Co 

228
00:12:25,720 --> 00:12:30,320
innovation with SAP? 
So what I found especially 

229
00:12:30,400 --> 00:12:35,280
important is to always push into
the direction of automation. 

230
00:12:35,320 --> 00:12:38,920
The release process has to 
consider so many different 

231
00:12:38,920 --> 00:12:42,480
things, values from different 
systems, which is very time 

232
00:12:42,480 --> 00:12:46,360
consuming for the user. 
And the idea was always to have 

233
00:12:46,400 --> 00:12:49,840
a system which would help the 
user to automate certain steps. 

234
00:12:49,840 --> 00:12:53,000
That the user does not need to 
do all checks manually, but has 

235
00:12:53,000 --> 00:12:56,480
a system in place that would 
come up with certain rules and 

236
00:12:56,480 --> 00:12:58,720
checks, certain data sets. 
It's automatically. 

237
00:12:58,720 --> 00:13:02,000
And this is how we came to the 
business rules that are now 

238
00:13:02,000 --> 00:13:05,560
implemented in BRH, which are 
really helpful to do certain 

239
00:13:05,560 --> 00:13:08,840
checks, especially in an area 
where you have a lot of data 

240
00:13:08,880 --> 00:13:12,120
like in the regulatory release. 
So there you have to check a lot

241
00:13:12,120 --> 00:13:15,320
of things if certain approvals 
are given for changes that you 

242
00:13:15,320 --> 00:13:17,080
have made to your products, for 
example. 

243
00:13:17,080 --> 00:13:19,280
This is a very cumbersome 
process at Hosch. 

244
00:13:19,360 --> 00:13:22,400
And with a batch release up, we 
have now a tool in place which 

245
00:13:22,520 --> 00:13:25,760
really eases this check. 
But we also have in other areas 

246
00:13:25,760 --> 00:13:29,040
this automation achieved. 
So we have also done certain 

247
00:13:29,040 --> 00:13:32,080
checks in the deviation 
management area which also can 

248
00:13:32,080 --> 00:13:34,760
be time intense to execute these
kind of checks. 

249
00:13:35,280 --> 00:13:37,280
Very good, Melanie. 
Thank you very much. 

250
00:13:37,320 --> 00:13:40,520
Marco, would you like to add 
here something on the challenge 

251
00:13:40,520 --> 00:13:41,880
and maybe how will you solve 
them? 

252
00:13:42,320 --> 00:13:44,960
For me, one of the big lessons 
we learned during the Co 

253
00:13:44,960 --> 00:13:48,000
innovation together with SAP was
the importance of thinking 

254
00:13:48,000 --> 00:13:51,280
greedy with integrated systems 
and how to implement integrated 

255
00:13:51,280 --> 00:13:53,600
systems, right. 
So at the beginning what we 

256
00:13:53,600 --> 00:13:55,840
understood and what we learned 
is that the understanding was 

257
00:13:55,840 --> 00:13:58,760
more like that we have a stand 
alone tool to be developed than 

258
00:13:58,760 --> 00:14:01,800
during the sessions. 
We were then basically pushing 

259
00:14:01,800 --> 00:14:05,360
more in the direction of fully 
integrated system into the S4 

260
00:14:05,360 --> 00:14:07,520
landscape. 
And as I explained at the very 

261
00:14:07,520 --> 00:14:10,400
beginning that especially when 
you look at the various quality 

262
00:14:10,400 --> 00:14:14,080
processes that are relevant as 
input to the release and also to

263
00:14:14,080 --> 00:14:18,000
the different manufacturing 
management process or the assets

264
00:14:18,000 --> 00:14:20,720
management planning processes 
and so on. 

265
00:14:20,760 --> 00:14:24,040
It's really obvious that the 
full integration of such an 

266
00:14:24,040 --> 00:14:28,000
police system into your supply 
chain tool which is our S4 

267
00:14:28,000 --> 00:14:30,560
system in the future is, is very
crucial. 

268
00:14:30,560 --> 00:14:34,080
And with that we developed this 
fully integrated concept of 

269
00:14:34,080 --> 00:14:38,240
having BIH connected to S4. 
So that BIH is basically for us 

270
00:14:38,240 --> 00:14:40,800
not a stand alone tool, but it's
highly integrated. 

271
00:14:41,000 --> 00:14:44,800
And there we benefit as Melanie 
said from the clear data stream 

272
00:14:44,840 --> 00:14:48,760
into the BIH being a cockpit 
that displays the data in a user

273
00:14:48,760 --> 00:14:51,240
understandable way. 
So that the release decision, 

274
00:14:51,240 --> 00:14:55,040
which was in the past a very 
cumbersome process to collect 

275
00:14:55,040 --> 00:14:58,600
the data, to understand the data
and to draw the conclusion that 

276
00:14:58,600 --> 00:15:00,440
everything was basically 
compliant. 

277
00:15:00,880 --> 00:15:04,320
And to to transform this process
with the system into a thing 

278
00:15:04,320 --> 00:15:07,440
where you easily see with 
traffic lights and created by 

279
00:15:07,440 --> 00:15:10,320
this business rules. 
And that the process was 

280
00:15:10,320 --> 00:15:13,680
properly executed, compliant and
that the batch can be released 

281
00:15:13,680 --> 00:15:16,040
to the next production step or 
even to the market. 

282
00:15:16,040 --> 00:15:18,520
And. 
Now the Co innovation of the SAP

283
00:15:18,520 --> 00:15:21,720
Batch Release Hub is done. 
Who wants to describe the 

284
00:15:21,720 --> 00:15:24,960
outcome or the capabilities of 
the product that was developed 

285
00:15:24,960 --> 00:15:29,240
together with you, Rush and SAP?
What I can tell is that I'm 

286
00:15:29,240 --> 00:15:31,840
really happy that we have such a
flexible tool. 

287
00:15:31,840 --> 00:15:33,480
I think we have not mentioned 
this yet. 

288
00:15:33,480 --> 00:15:37,520
So from our perspective, we are 
not doing the release only for 

289
00:15:37,560 --> 00:15:40,320
our drug, substance or drug 
products, but we are also 

290
00:15:40,320 --> 00:15:43,360
releasing our components that we
use for our production 

291
00:15:43,360 --> 00:15:46,760
processes. 
And for each type of material we

292
00:15:46,760 --> 00:15:49,160
have to perform different 
release steps. 

293
00:15:49,160 --> 00:15:52,440
So we have not one schema that 
we can follow, but sometimes we 

294
00:15:52,440 --> 00:15:54,600
have to do testing, sometimes we
don't. 

295
00:15:54,600 --> 00:15:58,000
Sometimes we have to consider 
certain transport or checks, 

296
00:15:58,000 --> 00:16:01,640
sometimes we don't. 
And the tool allows us really to

297
00:16:01,720 --> 00:16:05,680
put together the release 
activities really tailored per 

298
00:16:05,680 --> 00:16:08,080
the material type that we want 
to release. 

299
00:16:08,080 --> 00:16:11,600
So that's really something great
that this tool is offering us 

300
00:16:11,600 --> 00:16:16,000
because it's so flexible for us 
and really supports us in every 

301
00:16:16,000 --> 00:16:18,120
situation when we have to do a 
release. 

302
00:16:19,040 --> 00:16:22,000
Fully agree with Melanie. 
And I just want to add that also

303
00:16:22,000 --> 00:16:25,320
the tool is in a way flexible 
that you can also adapt to 

304
00:16:25,320 --> 00:16:28,840
different business needs, right.
So even designed from our point 

305
00:16:28,840 --> 00:16:32,680
of view to be very lean with the
data flow and also Mr. release 

306
00:16:32,680 --> 00:16:36,560
process, it can basically be 
automated or instantaneously you

307
00:16:36,560 --> 00:16:39,200
can release a batch if the data 
are properly available. 

308
00:16:39,360 --> 00:16:42,800
But on the other hand, there are
certain business requirements 

309
00:16:42,800 --> 00:16:46,680
also country specific and the 
BRH is flexible to also adapt to

310
00:16:46,680 --> 00:16:49,880
those requirements or also 
different business behaviors 

311
00:16:49,880 --> 00:16:52,840
throughout the network. 
So that also then allows us to 

312
00:16:52,840 --> 00:16:55,760
address the different 
stakeholder requirements when 

313
00:16:55,760 --> 00:16:59,240
deploying the tool. 
So this is also a great benefit,

314
00:16:59,240 --> 00:17:03,000
not only that we can cover the 
different release types, we call

315
00:17:03,000 --> 00:17:05,920
it we have in our network, but 
also the different needs from 

316
00:17:05,920 --> 00:17:10,000
the customers that are for 
example, the QP situation in the

317
00:17:10,160 --> 00:17:13,560
e-mail region or the release 
responsible situation for the 

318
00:17:13,560 --> 00:17:16,240
Swiss area and so on. 
And so far, we always have 

319
00:17:16,240 --> 00:17:18,800
different regulations that need 
to be addressed as well. 

320
00:17:19,440 --> 00:17:22,200
Aladdin, would you like to add 
something and what are your key 

321
00:17:22,200 --> 00:17:25,240
findings here after the Co 
animation of the SAP release 

322
00:17:25,240 --> 00:17:28,160
hub? 
I want to mention here that I am

323
00:17:28,160 --> 00:17:31,640
very happy I had a pleasure to 
work with Melania and Marco into

324
00:17:31,640 --> 00:17:33,160
the Co innovation of Batcheries 
Hub. 

325
00:17:33,240 --> 00:17:37,320
Actually they are the people who
had the vision and The Pioneers 

326
00:17:37,320 --> 00:17:40,400
who bring the life sciences 
industry to the next level with 

327
00:17:40,400 --> 00:17:43,160
their visions bringing 
Batchelor's Hub to the market. 

328
00:17:43,320 --> 00:17:47,160
And I have never seen so much 
excitement in a room or at any 

329
00:17:47,160 --> 00:17:50,400
even as I have seen when talking
about Bachelor lease hub. 

330
00:17:50,400 --> 00:17:53,960
Because the real business value 
of this solution that it 

331
00:17:53,960 --> 00:17:58,440
centralizes all the information 
needed by qualified persons and 

332
00:17:58,440 --> 00:18:01,920
quality assurance team at one 
single place so that they can 

333
00:18:01,920 --> 00:18:05,000
make faster decision making 
about the batch compliance. 

334
00:18:05,160 --> 00:18:09,000
Knowing also that bachelor lease
decisions exist at multiple 

335
00:18:09,000 --> 00:18:12,000
points in the supply chain. 
And this acceleration in the 

336
00:18:12,000 --> 00:18:15,280
decision making significantly 
improves the supply chain 

337
00:18:15,280 --> 00:18:17,560
performance. 
It enhances inventory 

338
00:18:17,560 --> 00:18:20,880
management, reduces order 
fulfillment, lead time and of 

339
00:18:20,880 --> 00:18:23,840
course improve employee 
productivity and quality 

340
00:18:23,840 --> 00:18:26,240
management. 
We have also seen that companies

341
00:18:26,240 --> 00:18:29,760
who adopting this technology 
will have more resilient and 

342
00:18:29,760 --> 00:18:33,480
agile supply chains that can 
meet the needs of new business 

343
00:18:33,480 --> 00:18:36,520
models that emerges now in the 
life sciences industry like 

344
00:18:36,520 --> 00:18:39,360
individualized and cell and gene
therapy medicines. 

345
00:18:40,440 --> 00:18:44,440
We have time for one more topic 
and I would like to move into a 

346
00:18:44,560 --> 00:18:47,280
hot topic at the moment, 
artificial intelligence. 

347
00:18:47,360 --> 00:18:50,600
Are there use cases that came 
out of the coronation between 

348
00:18:50,600 --> 00:18:54,760
Russian SAP, maybe Melanie and 
Marco, you saw some use cases 

349
00:18:54,760 --> 00:18:57,480
that would make sense. 
So during the Co innovation, we 

350
00:18:57,480 --> 00:19:00,440
have not touched this topic of 
artificial intelligence. 

351
00:19:00,680 --> 00:19:03,640
Of course, there are use cases 
for artificial intelligence. 

352
00:19:03,640 --> 00:19:06,800
I could imagine that in the 
deviation area, we could use 

353
00:19:06,800 --> 00:19:11,320
this way of working to identify,
track and trend or to identify 

354
00:19:11,320 --> 00:19:14,800
trends in this area. 
I could also think of the supply

355
00:19:14,800 --> 00:19:18,880
chain that we have to overview 
and would identify certain needs

356
00:19:18,880 --> 00:19:22,040
that we can't deliver to certain
countries. 

357
00:19:22,200 --> 00:19:23,440
Yeah. 
Just to catch up on what you 

358
00:19:23,440 --> 00:19:25,400
said, Melanie, correct. 
At the moment we are in a 

359
00:19:25,400 --> 00:19:28,040
situation that we want to 
implement this new fantastic 

360
00:19:28,040 --> 00:19:30,040
tool that we have collaborated 
with SAP. 

361
00:19:30,280 --> 00:19:34,480
And our main tasks are really to
bring the data in a clean and 

362
00:19:34,480 --> 00:19:37,160
clear way into the tool. 
And maybe artificial 

363
00:19:37,160 --> 00:19:39,800
intelligence, as Melanie said, 
could help us here to, to 

364
00:19:39,800 --> 00:19:43,160
understand the data better, to 
interpret various free text 

365
00:19:43,160 --> 00:19:45,800
data, so to say, which are not 
really structured data. 

366
00:19:45,960 --> 00:19:48,960
But on the other hand, we are at
the moment really focused on 

367
00:19:48,960 --> 00:19:51,600
getting the data structured and 
properly set up so that the 

368
00:19:51,600 --> 00:19:53,920
release is automated and able to
convene. 

369
00:19:54,200 --> 00:19:57,400
And there is also a lot of new 
functionalities coming with the 

370
00:19:57,400 --> 00:19:59,120
BIH, as we know from the road 
map. 

371
00:19:59,280 --> 00:20:02,240
We are really looking forward to
get those implemented. 

372
00:20:02,240 --> 00:20:05,640
And they are also tightly 
connected with clear structured 

373
00:20:05,640 --> 00:20:08,720
data, master data that need to 
be set up and defined properly, 

374
00:20:08,840 --> 00:20:09,600
right? 
And this is. 

375
00:20:09,800 --> 00:20:14,000
Main focus, I would say I'm very
excited to see what capabilities

376
00:20:14,000 --> 00:20:17,280
will then come later on with the
artificial intelligence to be 

377
00:20:17,280 --> 00:20:20,200
implemented or other 
technologies like blockchain and

378
00:20:20,200 --> 00:20:22,520
so on that might be used for 
this tool. 

379
00:20:23,040 --> 00:20:25,600
Melanie and Marco, thank you 
very much for your insights in 

380
00:20:25,600 --> 00:20:28,720
the artificial world and vision 
of yourself. 

381
00:20:28,960 --> 00:20:32,680
Looking at the time of my watch,
I see that we are already at the

382
00:20:32,680 --> 00:20:35,000
end of this episode. 
Time flies when you're having 

383
00:20:35,000 --> 00:20:37,160
fun. 
I really enjoyed this talk with 

384
00:20:37,160 --> 00:20:39,960
you guys and let's hear your 
final words. 

385
00:20:40,320 --> 00:20:42,080
Thank you Marcos for this great 
session. 

386
00:20:42,080 --> 00:20:45,480
It was really a pleasure talking
to you as also the Co innovation

387
00:20:45,480 --> 00:20:48,480
was a real big fun we had with 
SAP, right. 

388
00:20:48,480 --> 00:20:51,400
We still remember the great time
and we were sitting together 

389
00:20:51,400 --> 00:20:55,360
discussing really into the 
details how the tool might work 

390
00:20:55,360 --> 00:20:58,640
in the future then and then also
to see how the tool came to 

391
00:20:58,640 --> 00:21:00,920
life. 
We are actually very excited 

392
00:21:00,920 --> 00:21:04,800
that we are still leading here 
with implementation of the BIH 

393
00:21:04,800 --> 00:21:07,000
connected to S4 fully 
integrated. 

394
00:21:07,040 --> 00:21:10,080
And we are looking forward with 
a future great collaboration 

395
00:21:10,080 --> 00:21:12,240
with SAP. 
And thank you for the podcast. 

396
00:21:12,240 --> 00:21:15,240
Also from my side, Aladdin, also
thank you for your support 

397
00:21:15,280 --> 00:21:17,440
making all of this happen with 
the team at SAP. 

398
00:21:18,240 --> 00:21:20,040
Also from my end, I want to 
thank you. 

399
00:21:20,240 --> 00:21:22,640
I think it was a great 
experience to do this 

400
00:21:22,640 --> 00:21:24,760
connivation. 
Typically you don't do this so 

401
00:21:24,760 --> 00:21:27,720
often in your life. 
So this was definitely a very 

402
00:21:27,720 --> 00:21:30,600
good experience. 
We had a very good team, good 

403
00:21:30,600 --> 00:21:33,360
collaboration. 
We enjoyed it a lot and also the

404
00:21:33,360 --> 00:21:36,600
outcome is a very good tool that
we have now in place. 

405
00:21:36,840 --> 00:21:40,680
Thank you so much. 
Thanks again, Melanie, Marco and

406
00:21:40,680 --> 00:21:44,160
also Aladdin and all the best to
you, to our audience. 

407
00:21:44,160 --> 00:21:47,880
If you like this episode and 
have ideas about the next 

408
00:21:47,880 --> 00:21:51,360
relevant topics for this 
podcast, send us an e-mail to 

409
00:21:51,440 --> 00:21:56,960
insideas4@sap.com. 
TuneIn next time and be inside 

410
00:21:56,960 --> 00:21:58,560
SAP. 
As for Hannah Cloud?

