WEBVTT
Language: en-US

1
00:00:08.050 --> 00:00:10.770
<v Speaker 1>Welcome to the battery podcast from
Siemens Digital-Industries.

2
00:00:10.890 --> 00:00:14.970
<v Speaker 1>We're picking up our conversation with
Punit Sinha, Hari Gopal Krishna, and Tal

3
00:00:14.970 --> 00:00:18.190
<v Speaker 1>Schlapper on making battery manufacturing
a data-driven endeavor.

4
00:00:18.489 --> 00:00:22.209
<v Speaker 1>In the last episode, we covered the trends
and benefits, making this a worthwhile

5
00:00:22.209 --> 00:00:26.610
<v Speaker 1>evolution, but for this one, we're diving
into how businesses can integrate a

6
00:00:26.610 --> 00:00:28.629
<v Speaker 1>data-driven approach into their
operations.

7
00:00:28.920 --> 00:00:29.530
<v Speaker 1>Take it away, Pune.

8
00:00:30.520 --> 00:00:30.920
<v Speaker 2>Perfect.

9
00:00:31.000 --> 00:00:36.840
<v Speaker 2>So let, let me peel the next layer of
onion, and then we talk about, as you said, we

10
00:00:36.840 --> 00:00:42.430
<v Speaker 2>have 3 pillars to our data-driven
manufacturing practice.

11
00:00:42.959 --> 00:00:46.299
<v Speaker 2>We'll talk about 2 ITOT convergence and
digital twin.

12
00:00:46.680 --> 00:00:49.689
<v Speaker 2>As I said earlier, digital twin is.

13
00:00:50.830 --> 00:00:55.430
<v Speaker 2>It, it, it is there to, to help you do a
lot of things in the digital world.

14
00:00:55.470 --> 00:01:01.069
<v Speaker 2>You can look at the, not only just the
self product performance, but also how the

15
00:01:01.069 --> 00:01:05.349
<v Speaker 2>machines are, uh, developed, how they need
to, all of these machines needs to

16
00:01:05.349 --> 00:01:08.870
<v Speaker 2>connect, how all of these different
machines needs to operate.

17
00:01:09.750 --> 00:01:13.589
<v Speaker 2>And of course, ITOD convergence is coming
at the factory floor of how you're

18
00:01:13.589 --> 00:01:18.750
<v Speaker 2>bringing MES and how you're connecting,
uh, with, with the, the right machines and

19
00:01:18.750 --> 00:01:19.650
<v Speaker 2>factories together.

20
00:01:21.550 --> 00:01:26.110
<v Speaker 2>Um, there is one example I want to bring,
which is one of my favorite, is many times

21
00:01:26.110 --> 00:01:30.330
<v Speaker 2>people think of digital twin that happens
before you get in a factory, you're in the

22
00:01:30.330 --> 00:01:35.269
<v Speaker 2>engineering side, you're sitting in front
of a computer and do that, and you somehow

23
00:01:35.269 --> 00:01:39.449
<v Speaker 2>throw that across the wall and things come
in the, in the, in the factory.

24
00:01:39.989 --> 00:01:42.809
<v Speaker 2>And when the things get real, things start
breaking down.

25
00:01:43.150 --> 00:01:48.870
<v Speaker 2>So I want to bring an example to elaborate
that these things are not siloed, and

26
00:01:48.870 --> 00:01:50.110
<v Speaker 2>that example is.

27
00:01:51.080 --> 00:01:53.930
<v Speaker 2>And, um, I'll talk about a specific
problem.

28
00:01:54.040 --> 00:01:55.360
<v Speaker 2>So if you look at the winding.

29
00:01:56.500 --> 00:02:01.400
<v Speaker 2>This, this operation happens at a at a
very high speed, and, and the tension needs

30
00:02:01.400 --> 00:02:07.209
<v Speaker 2>to be correct for the during the winding
too loose, you are going to have a bad

31
00:02:07.209 --> 00:02:10.860
<v Speaker 2>winding, too tight of tension, foil can
break.

32
00:02:11.050 --> 00:02:14.429
<v Speaker 2>And if foil breaks, of course, you have to
stop the production.

33
00:02:15.160 --> 00:02:17.250
<v Speaker 2>There are time and costs associated with
it.

34
00:02:18.110 --> 00:02:22.229
<v Speaker 2>This is a great example where we are
bringing digital twin, which typically people

35
00:02:22.229 --> 00:02:25.809
<v Speaker 2>think of something that you do when you're
sitting in a in a cubicle.

36
00:02:26.229 --> 00:02:31.059
<v Speaker 2>We take that digital twin off that machine
of that winding operation, creating an

37
00:02:31.059 --> 00:02:36.789
<v Speaker 2>executable version that is running on
industrial edge in a factory.

38
00:02:37.800 --> 00:02:42.059
<v Speaker 2>And the power that is as the operation is
running on the left hand side.

39
00:02:42.839 --> 00:02:47.210
<v Speaker 2>The digital representation of the same
operation is running on the right-hand side.

40
00:02:47.630 --> 00:02:52.059
<v Speaker 2>And that is allowing you to see, hey, is
the tension, stress or strain getting too

41
00:02:52.059 --> 00:02:56.410
<v Speaker 2>much at any point in time in that foil,
something you can't measure.

42
00:02:57.880 --> 00:03:03.440
<v Speaker 2>And as that digital twin explores that, it
is working as a virtual sensor in a

43
00:03:03.440 --> 00:03:04.130
<v Speaker 2>certain way.

44
00:03:04.360 --> 00:03:11.080
<v Speaker 2>And then through ITOT integration, we can
feed through PLCs how the motor torque

45
00:03:11.080 --> 00:03:15.520
<v Speaker 2>speed needs to be changed, if it is
getting it, you know, if the tension is too

46
00:03:15.520 --> 00:03:16.619
<v Speaker 2>high, how to bring it down.

47
00:03:16.949 --> 00:03:19.779
<v Speaker 2>If the tension is getting too low, how to
speed, how to bring it up.

48
00:03:20.080 --> 00:03:25.839
<v Speaker 2>This, this is an example of how the
digital twins and ITOT integration, all of that

49
00:03:25.839 --> 00:03:26.580
<v Speaker 2>come together.

50
00:03:26.869 --> 00:03:28.389
<v Speaker 2>And it allows you to.

51
00:03:29.339 --> 00:03:31.320
<v Speaker 2>Avoid the problem before it happens.

52
00:03:31.500 --> 00:03:34.490
<v Speaker 2>Once the problem has happened, then you
have to find a solution.

53
00:03:34.529 --> 00:03:35.300
<v Speaker 2>It takes time.

54
00:03:35.589 --> 00:03:41.529
<v Speaker 2>So this is one of my favorite examples of
showing the power of digital and ITOD

55
00:03:41.529 --> 00:03:46.179
<v Speaker 2>convergence, and they don't need to happen
one in cubicle, one on a factory floor.

56
00:03:46.559 --> 00:03:50.360
<v Speaker 2>So Hari, I'll come to you and help us
understand how.

57
00:03:51.190 --> 00:03:55.399
<v Speaker 2>AWS is making this happen because there's
a lot of data and a lot of architecture

58
00:03:55.399 --> 00:03:55.669
<v Speaker 2>there.

59
00:03:56.710 --> 00:03:58.130
<v Hari Gopalakrishna>Um, yeah, so.

60
00:03:59.589 --> 00:04:04.179
<v Hari Gopalakrishna>So what you're seeing right now on the
screen is an industrial, a purpose-built

61
00:04:04.179 --> 00:04:05.899
<v Hari Gopalakrishna>industrial architecture.

62
00:04:07.110 --> 00:04:11.710
<v Hari Gopalakrishna>So, here, you know, what you're seeing
also is a hybrid architecture.

63
00:04:12.070 --> 00:04:15.779
<v Hari Gopalakrishna>You have the cloud, you have the edge, and
you have in between, right?

64
00:04:16.109 --> 00:04:19.500
<v Hari Gopalakrishna>There are some things that are better done
in the cloud, and there are some things

65
00:04:19.500 --> 00:04:21.109
<v Hari Gopalakrishna>that are better done at the edge.

66
00:04:21.899 --> 00:04:27.140
<v Hari Gopalakrishna>Things that are latency sensitive, that
are going to be needed with short-term, like

67
00:04:27.140 --> 00:04:30.320
<v Hari Gopalakrishna>really quick inference needs that are
going to happen at the edge.

68
00:04:30.579 --> 00:04:32.980
<v Hari Gopalakrishna>So what you're seeing here it's a great
example, by the way.

69
00:04:34.000 --> 00:04:40.929
<v Hari Gopalakrishna>You have an AWS IOT client running on
Siemens Industrial Edge, which is

70
00:04:40.929 --> 00:04:42.690
<v Hari Gopalakrishna>connected to the equipment.

71
00:04:44.049 --> 00:04:47.369
<v Hari Gopalakrishna>Which it has the ability to connect to
diverse set of equipment and process

72
00:04:47.369 --> 00:04:48.019
<v Hari Gopalakrishna>variables.

73
00:04:48.200 --> 00:04:49.630
<v Hari Gopalakrishna>You can collect all kinds of data.

74
00:04:50.209 --> 00:04:55.149
<v Hari Gopalakrishna>Once this data is collected, it's
contextualized and it's sent to the cloud where

75
00:04:55.450 --> 00:05:01.519
<v Hari Gopalakrishna>that data could be combined with other
types of data from MES, CRP, CMMS systems,

76
00:05:01.730 --> 00:05:03.890
<v Hari Gopalakrishna>all these different skater systems.

77
00:05:04.350 --> 00:05:09.869
<v Hari Gopalakrishna>And so that's where you would build your
models, build your digital twins, and once

78
00:05:09.869 --> 00:05:15.209
<v Hari Gopalakrishna>you have that, you would then deploy that
at the edge and it will run at the edge

79
00:05:15.510 --> 00:05:20.549
<v Hari Gopalakrishna>because they are, you know, context
sensitive, they are latency sensitive, and so

80
00:05:20.549 --> 00:05:25.910
<v Hari Gopalakrishna>this is the kind of fundamental
architecture that we operate within the industrial

81
00:05:25.910 --> 00:05:29.160
<v Hari Gopalakrishna>facilities at scale now as an example.

82
00:05:29.899 --> 00:05:36.660
<v Hari Gopalakrishna>As you scale from a lab to a gig
gigafactory, the, the volume of

83
00:05:36.660 --> 00:05:41.380
<v Hari Gopalakrishna>data is also very high, uh, for one of our
customers, it's almost 1 petabyte of data

84
00:05:41.380 --> 00:05:42.190
<v Hari Gopalakrishna>per day.

85
00:05:42.700 --> 00:05:48.149
<v Hari Gopalakrishna>So in order for you to make sense of this
data and to be able to truly drive

86
00:05:48.149 --> 00:05:53.089
<v Hari Gopalakrishna>insights, you have to know how to handle
that data, how to really contextualize,

87
00:05:53.579 --> 00:05:58.059
<v Hari Gopalakrishna>process it at the right places, and also,
you know, really connect with other types

88
00:05:58.059 --> 00:05:58.579
<v Hari Gopalakrishna>of data.

89
00:05:58.920 --> 00:06:03.399
<v Hari Gopalakrishna>So you know you have the overall view of
what problems are you solving, because it's

90
00:06:03.399 --> 00:06:05.269
<v Hari Gopalakrishna>ultimately outcome centric, right?

91
00:06:05.529 --> 00:06:06.730
<v Hari Gopalakrishna>You're driving an outcome.

92
00:06:07.410 --> 00:06:07.869
<v Hari Gopalakrishna>So

93
00:06:08.510 --> 00:06:09.040
<v Speaker 2>Absolutely.

94
00:06:09.079 --> 00:06:14.239
<v Speaker 2>And, and as you said, it's a data
processing at the right places very critical

95
00:06:14.239 --> 00:06:15.380
<v Speaker 2>because you cannot.

96
00:06:16.279 --> 00:06:20.160
<v Speaker 2>Download the data from one computer and in
in your USB drive and take to the other.

97
00:06:20.239 --> 00:06:22.730
<v Speaker 2>So that is a real um practical problem.

98
00:06:23.160 --> 00:06:23.880
<v Speaker 2>So I'm, I'm gonna.

99
00:06:25.049 --> 00:06:28.980
<v Speaker 2>I shift the gear and come to scrap rate
and quality issue.

100
00:06:29.220 --> 00:06:34.019
<v Speaker 2>Earlier I mentioned that as we are
deploying this, our data-driven manufacturing

101
00:06:34.019 --> 00:06:40.299
<v Speaker 2>practices with our collective solutions, I
mentioned that at a customer there is a

102
00:06:40.299 --> 00:06:44.500
<v Speaker 2>10% reduction in scrap rate we were able
to achieve from their baseline.

103
00:06:45.309 --> 00:06:51.429
<v Speaker 2>So, Tal, I would love for you to explain
that, elaborate on, on that, that customer

104
00:06:51.429 --> 00:06:52.260
<v Speaker 2>challenges.

105
00:06:52.470 --> 00:06:53.630
<v Speaker 2>How did we solve that?

106
00:06:54.510 --> 00:06:57.049
<v Speaker 2>And what, what are the borders that we are
able to solve together?

107
00:06:58.299 --> 00:07:02.209
<v Tal Sholklapper>Yeah, of course, so it's a handful of
these scenarios we've seen across customers,

108
00:07:02.269 --> 00:07:06.029
<v Tal Sholklapper>you know, the, there's that initial ramp
up as you're getting up to, you know,

109
00:07:06.190 --> 00:07:10.989
<v Tal Sholklapper>increasing production volumes, you're, you
know, decreasing those scrap rates, and a

110
00:07:10.989 --> 00:07:15.029
<v Tal Sholklapper>lot of customers we've seen this like
stubborn, you know, we can get up to 60, 70,

111
00:07:15.130 --> 00:07:20.420
<v Tal Sholklapper>80%, and, uh, taking that next step and
further decreasing scrap rates, uh, from

112
00:07:20.420 --> 00:07:22.890
<v Tal Sholklapper>whatever that baseline is, is, is very
challenging.

113
00:07:23.269 --> 00:07:27.910
<v Tal Sholklapper>And even once you get into production,
there's still continuous uh challenges that

114
00:07:27.910 --> 00:07:32.350
<v Tal Sholklapper>will pop up and deviations and uh
excursions that will occur in the production

115
00:07:32.350 --> 00:07:32.890
<v Tal Sholklapper>process, so.

116
00:07:33.989 --> 00:07:39.750
<v Tal Sholklapper>Uh, this customer, uh, in particular, uh,
they started initially to see some early

117
00:07:39.750 --> 00:07:45.190
<v Tal Sholklapper>issues with, uh, very early warranty
returns from their customer, um, their end

118
00:07:45.190 --> 00:07:50.350
<v Tal Sholklapper>customer, which was putting it into
devices, and what they, you know, realized that

119
00:07:50.350 --> 00:07:54.510
<v Tal Sholklapper>they were able to catch some of these with
a little tighter, uh, tolerances, uh, for

120
00:07:54.510 --> 00:07:59.820
<v Tal Sholklapper>their OCVs and voltage drops, uh, for
self-discharge from the cells at the end of

121
00:07:59.820 --> 00:08:01.049
<v Tal Sholklapper>the production process.

122
00:08:01.739 --> 00:08:05.649
<v Tal Sholklapper>Uh, the first thing we did with them was
actually start looking, uh, a little deeper

123
00:08:05.649 --> 00:08:11.500
<v Tal Sholklapper>into their existing formation data, and
we're able to identify, uh, the ability to

124
00:08:11.500 --> 00:08:17.019
<v Tal Sholklapper>actually catch many of these defects
within the first, uh, couple of hours of

125
00:08:17.019 --> 00:08:22.649
<v Tal Sholklapper>formation, those initial charge-ups, and
be able to identify, uh, a number of those,

126
00:08:22.660 --> 00:08:25.640
<v Tal Sholklapper>uh, deviant cells, uh, very early in the
process.

127
00:08:26.829 --> 00:08:29.220
<v Tal Sholklapper>The next thing we did was, it was very
rudimentary.

128
00:08:29.269 --> 00:08:33.789
<v Tal Sholklapper>They did not have the full, you know,
genealogy of their upstream process steps, uh,

129
00:08:33.869 --> 00:08:37.369
<v Tal Sholklapper>but we were able to actually take in at
least the granular data, what.

130
00:08:38.150 --> 00:08:40.090
<v Tal Sholklapper>You know, piece of equipment that this
come through.

131
00:08:40.750 --> 00:08:46.309
<v Tal Sholklapper>What a lot of, you know, slurry was mixed,
what was the batches of material, and

132
00:08:46.309 --> 00:08:52.229
<v Tal Sholklapper>we're actually able to go through and tie
this to the storage rooms and the humidity

133
00:08:52.229 --> 00:08:54.789
<v Tal Sholklapper>of their materials that were coming into
the facility.

134
00:08:54.830 --> 00:08:59.710
<v Tal Sholklapper>And so when they didn't have proper
materials handling and keep the material in the

135
00:08:59.710 --> 00:09:05.229
<v Tal Sholklapper>right environment, uh, we had these
excursions that were leading to moisture

136
00:09:05.229 --> 00:09:06.530
<v Tal Sholklapper>depositing in the material.

137
00:09:06.969 --> 00:09:11.630
<v Tal Sholklapper>And, you know, It was great that we're
able to, you know, shift left, catch those

138
00:09:11.630 --> 00:09:14.820
<v Tal Sholklapper>issues, you know, in formation early on,
just looking at things like the

139
00:09:14.820 --> 00:09:19.109
<v Tal Sholklapper>differential capacity for the cells, but
really the key, you know, thing that I was

140
00:09:19.109 --> 00:09:23.390
<v Tal Sholklapper>able to save them on the scrap race was,
uh, you know, identifying the root cause

141
00:09:23.390 --> 00:09:26.909
<v Tal Sholklapper>which was actually in the materials
handling and the moisture of the materials in

142
00:09:26.909 --> 00:09:28.349
<v Tal Sholklapper>this case, uh, but.

143
00:09:28.405 --> 00:09:32.244
<v Tal Sholklapper>Tremendous value all from things and data
that already exists at the customer and

144
00:09:32.244 --> 00:09:36.284
<v Tal Sholklapper>just really putting that together in a way
so that you could, you know, shift left

145
00:09:36.284 --> 00:09:40.815
<v Tal Sholklapper>the identification of issues, start
remedying those, uh, looking to remediate those

146
00:09:40.815 --> 00:09:45.405
<v Tal Sholklapper>as quickly as possible and then having a
way to drill down and really understand

147
00:09:45.405 --> 00:09:49.864
<v Tal Sholklapper>where that is coming from rather than
having to go with thumb drives or disparate

148
00:09:49.864 --> 00:09:53.244
<v Tal Sholklapper>data systems internally, uh, and all in a
simple, simple system.

149
00:09:54.460 --> 00:09:55.140
<v Speaker 2>Perfect.

150
00:09:55.570 --> 00:09:57.919
<v Speaker 2>So, I have an obvious question.

151
00:09:58.020 --> 00:10:03.299
<v Speaker 2>So we, we talked a lot about data,
collecting data and, and processing data.

152
00:10:03.880 --> 00:10:09.840
<v Speaker 2>So we get this question a lot and I, I
would love for us to answer that is, if it is

153
00:10:09.840 --> 00:10:16.640
<v Speaker 2>all about data processing and extracting
intelligence out, out of data, we are in

154
00:10:16.640 --> 00:10:17.880
<v Speaker 2>the AI age.

155
00:10:17.989 --> 00:10:23.929
<v Speaker 2>So why can't AI teams or data analytics
teams in, in companies handle this?

156
00:10:25.799 --> 00:10:29.840
<v Tal Sholklapper>Yeah, it's something we get asked very
often today, you know, someone can go in with

157
00:10:29.840 --> 00:10:33.159
<v Tal Sholklapper>some, uh, AI tools and very quickly build
a dashboard.

158
00:10:33.200 --> 00:10:35.659
<v Tal Sholklapper>It's, it's, uh, if anything, it's easier
than ever, which is great.

159
00:10:35.809 --> 00:10:40.869
<v Tal Sholklapper>Our teams take advantage of it as well,
um, but the real challenge here is in order

160
00:10:40.869 --> 00:10:47.440
<v Tal Sholklapper>to really understand this domain specific,
uh, you know, problem, you need to have a

161
00:10:47.440 --> 00:10:48.119
<v Tal Sholklapper>couple of things.

162
00:10:48.200 --> 00:10:53.479
<v Tal Sholklapper>You have to have the data well structured
in a way that you can actually, you know,

163
00:10:53.640 --> 00:10:55.400
<v Tal Sholklapper>learn from large amounts of it.

164
00:10:55.859 --> 00:10:59.700
<v Tal Sholklapper>You need a lot of data, you need to be
cleaned, and you don't just need the raw data

165
00:10:59.700 --> 00:11:03.599
<v Tal Sholklapper>most of the times, you actually need the
features and metrics extracted from it that

166
00:11:04.020 --> 00:11:07.080
<v Tal Sholklapper>provide you insight onto what's going on
in those devices.

167
00:11:07.380 --> 00:11:08.320
<v Tal Sholklapper>Um, and so.

168
00:11:09.340 --> 00:11:13.140
<v Tal Sholklapper>You know, really what we have been focused
on is trying to create the infrastructure

169
00:11:13.140 --> 00:11:18.299
<v Tal Sholklapper>and platforms to, you know, do that to,
you know, if you look across the battery

170
00:11:18.299 --> 00:11:21.659
<v Tal Sholklapper>industry, there's a whole range of AI
solutions you'll see out there.

171
00:11:22.059 --> 00:11:24.340
<v Tal Sholklapper>They're trained off like 3 to 50 data
points.

172
00:11:24.419 --> 00:11:28.020
<v Tal Sholklapper>It's, you know, that's not AI, that's, you
know, you could do regression, you could

173
00:11:28.020 --> 00:11:29.960
<v Tal Sholklapper>do better most of the time just in Excel.

174
00:11:30.340 --> 00:11:35.190
<v Tal Sholklapper>Um, and so really the key here is, you
know, you want to implement these tools.

175
00:11:35.270 --> 00:11:39.309
<v Tal Sholklapper>These tools are great, we're super excited
about them, but really getting the data

176
00:11:39.309 --> 00:11:44.289
<v Tal Sholklapper>pipelines and infrastructure in place to
bring this data at scale into, uh,

177
00:11:44.390 --> 00:11:47.630
<v Tal Sholklapper>solutions where you can leverage these
advanced techniques is really the key in the

178
00:11:47.630 --> 00:11:52.429
<v Tal Sholklapper>battery industry and getting that
infrastructure and then also consultatively

179
00:11:52.429 --> 00:11:56.909
<v Tal Sholklapper>helping customers figure out what data to
bring in, you know, there's, there's a lot

180
00:11:56.909 --> 00:11:59.299
<v Tal Sholklapper>of potential data you can collect and.

181
00:11:59.799 --> 00:12:03.280
<v Tal Sholklapper>What data do you bring in and what
resolution and how do you actually extract that

182
00:12:03.280 --> 00:12:06.900
<v Tal Sholklapper>meaningful insight so that you can layer
in these advanced tools is really key.

183
00:12:08.489 --> 00:12:09.250
<v Speaker 2>What about you, Audie?

184
00:12:09.260 --> 00:12:10.179
<v Speaker 2>You have something to add?

185
00:12:10.539 --> 00:12:12.500
<v Hari Gopalakrishna>No, I think that he's covered it really
well.

186
00:12:12.820 --> 00:12:18.090
<v Hari Gopalakrishna>One thing that I would add is, you know,
Voltig as an example is a a solution that's

187
00:12:18.090 --> 00:12:19.059
<v Hari Gopalakrishna>built on AWS.

188
00:12:19.580 --> 00:12:24.239
<v Hari Gopalakrishna>We have a number of services that are
targeted at security, data governance, and,

189
00:12:24.469 --> 00:12:29.700
<v Hari Gopalakrishna>um, a key management services, identity
identity management, um, encryption services

190
00:12:29.700 --> 00:12:30.260
<v Hari Gopalakrishna>and things like that.

191
00:12:30.330 --> 00:12:35.260
<v Hari Gopalakrishna>And so, you know, if there are fear about
he going to do this in the cloud because I

192
00:12:35.260 --> 00:12:39.700
<v Hari Gopalakrishna>have, you know, concerns about IP and, you
know, IP and data protection and that

193
00:12:39.700 --> 00:12:44.700
<v Hari Gopalakrishna>sort of thing, uh, this is, you know, we
have a suite of services to assist with

194
00:12:44.700 --> 00:12:44.940
<v Hari Gopalakrishna>that.

195
00:12:45.270 --> 00:12:51.799
<v Hari Gopalakrishna>And generally when these solutions are
built on AWS we make sure that it's built

196
00:12:51.799 --> 00:12:56.260
<v Hari Gopalakrishna>correctly and so we have our own
foundational technical review process to ensure

197
00:12:56.559 --> 00:13:01.559
<v Hari Gopalakrishna>let's say a full solution like Voltaic is
leveraging the right type of security data

198
00:13:01.559 --> 00:13:05.119
<v Hari Gopalakrishna>management practices and it's built for
scale so you know.

199
00:13:05.530 --> 00:13:10.849
<v Hari Gopalakrishna>There shouldn't be any concerns around
that, you know, using cloud and that sort of

200
00:13:10.849 --> 00:13:11.179
<v Hari Gopalakrishna>stuff, yeah,

201
00:13:11.590 --> 00:13:15.989
<v Tal Sholklapper>yeah, and one of the fun things we've seen
is that, you know, a lot of these early,

202
00:13:16.049 --> 00:13:19.729
<v Tal Sholklapper>you know, exec driven or internally
driven, like, hey, we want to implement AI, we

203
00:13:19.729 --> 00:13:23.210
<v Tal Sholklapper>want to get something going, and, uh, at
the end of the day, you know, these people,

204
00:13:23.289 --> 00:13:26.770
<v Tal Sholklapper>you'll spend 9 months doing essentially a
POC and then they try to roll it out.

205
00:13:26.809 --> 00:13:29.869
<v Tal Sholklapper>It doesn't work because you haven't
trained on enough data, you don't have the right

206
00:13:29.869 --> 00:13:31.510
<v Tal Sholklapper>infrastructure to enable these and.

207
00:13:31.900 --> 00:13:35.630
<v Tal Sholklapper>It's really the, the coming together of
solutions like ours that they try to sort of

208
00:13:35.630 --> 00:13:38.429
<v Tal Sholklapper>hack together for those projects, um.

209
00:13:39.229 --> 00:13:42.390
<v Tal Sholklapper>You know, they, they, they end up really
trying to pull us in and we become those

210
00:13:42.390 --> 00:13:45.070
<v Tal Sholklapper>key partners helping them enable these
advanced tools.

211
00:13:46.369 --> 00:13:47.289
<v Speaker 2>Absolutely.

212
00:13:47.650 --> 00:13:52.210
<v Speaker 2>You know, guys, what, what I say is the
difference between dashboarding and data

213
00:13:52.210 --> 00:13:52.960
<v Speaker 2>intelligence.

214
00:13:53.289 --> 00:13:57.969
<v Speaker 2>Dashboarding is knowing that tomato is a
fruit, and, and data intelligence is

215
00:13:57.969 --> 00:14:00.429
<v Speaker 2>knowing that you don't put tomato in your
fruit salad.

216
00:14:01.049 --> 00:14:04.750
<v Speaker 2>Um, so, I know we, our time is coming to
an end.

217
00:14:05.739 --> 00:14:10.500
<v Speaker 2>Uh, but before we end, I would love to
hear what, what, how will you communicate to

218
00:14:10.500 --> 00:14:11.059
<v Speaker 2>our audience?

219
00:14:11.140 --> 00:14:13.140
<v Speaker 2>What is our joint value propositions?

220
00:14:13.539 --> 00:14:18.299
<v Speaker 2>How, um, our audience, if they want to
work with us, how they can approach us and

221
00:14:18.299 --> 00:14:19.380
<v Speaker 2>initiate this journey.

222
00:14:20.619 --> 00:14:21.409
<v Speaker 2>Howdy, do you want to start?

223
00:14:21.809 --> 00:14:22.250
<v Speaker 2>Sure,

224
00:14:22.609 --> 00:14:29.010
<v Hari Gopalakrishna>so battery manufacturing is complex on
many fronts from materials, R&amp;D to

225
00:14:29.010 --> 00:14:29.729
<v Hari Gopalakrishna>manufacturing.

226
00:14:30.750 --> 00:14:34.869
<v Hari Gopalakrishna>And there's different domains of expertise
in that, right?

227
00:14:35.520 --> 00:14:42.469
<v Hari Gopalakrishna>And what we are bringing, you know, from
AWS is that data expertise, uh,

228
00:14:42.510 --> 00:14:43.909
<v Hari Gopalakrishna>AI machine learning.

229
00:14:44.929 --> 00:14:50.349
<v Hari Gopalakrishna>Large language models, generative AI, that
sort of things, advanced analytics, and

230
00:14:50.530 --> 00:14:57.010
<v Hari Gopalakrishna>the right type of industrial data
architecture to handle the data and the volume

231
00:14:57.250 --> 00:14:59.609
<v Hari Gopalakrishna>from the plan to the cloud, right?

232
00:15:00.469 --> 00:15:02.210
<v Hari Gopalakrishna>But that's only one domain.

233
00:15:02.630 --> 00:15:08.809
<v Hari Gopalakrishna>We need other domains like yourself,
Siemens bring the expertise around industrial

234
00:15:09.270 --> 00:15:10.469
<v Hari Gopalakrishna>er connectivity.

235
00:15:11.140 --> 00:15:17.669
<v Hari Gopalakrishna>Uh, automation, software, PLM, MES, and
decades and, you know, over 100 years of

236
00:15:17.669 --> 00:15:18.150
<v Hari Gopalakrishna>experience.

237
00:15:18.960 --> 00:15:24.440
<v Hari Gopalakrishna>So, same thing with Voltaic, the level of
battery knowledge and expertise that they

238
00:15:24.440 --> 00:15:28.440
<v Hari Gopalakrishna>bring to the table and really making sense
and, you know, driving insights out of

239
00:15:28.440 --> 00:15:29.099
<v Hari Gopalakrishna>all of this.

240
00:15:29.979 --> 00:15:32.919
<v Hari Gopalakrishna>That's why, you know, bringing all three
of us together.

241
00:15:33.570 --> 00:15:39.940
<v Hari Gopalakrishna>And bringing an integrated set of tools
and platform really helps accelerate uh our,

242
00:15:39.950 --> 00:15:41.250
<v Hari Gopalakrishna>our customers' business, right?

243
00:15:41.530 --> 00:15:43.409
<v Hari Gopalakrishna>The innovation and, and in time to market

244
00:15:44.479 --> 00:15:44.760
<v Speaker 2>absolutely tell.

245
00:15:45.940 --> 00:15:49.179
<v Tal Sholklapper>Yeah, it comes down to, you know, the time
frames, you know.

246
00:15:50.130 --> 00:15:53.650
<v Tal Sholklapper>Whether you've got an existing factory or
you're putting up new ones, the cost

247
00:15:53.650 --> 00:15:57.010
<v Tal Sholklapper>pressures are here, the time pressures,
you need to get these factories up and

248
00:15:57.010 --> 00:16:01.090
<v Tal Sholklapper>running, uh, you need to, you know, ensure
the quality of the cells coming out of

249
00:16:01.090 --> 00:16:01.950
<v Tal Sholklapper>there because.

250
00:16:02.479 --> 00:16:07.880
<v Tal Sholklapper>You know, the investments, uh, you know,
periods of free, low, you know, low

251
00:16:07.880 --> 00:16:08.960
<v Tal Sholklapper>interest rate money is gone.

252
00:16:09.599 --> 00:16:12.000
<v Tal Sholklapper>You're gonna have to do this with, you
know, smaller staffs.

253
00:16:12.119 --> 00:16:15.469
<v Tal Sholklapper>You're not gonna have the leeway of years
to try to get these factories up and

254
00:16:15.469 --> 00:16:20.760
<v Tal Sholklapper>running, uh, the high scrap rates, you
know, the, with the cost models and contracts

255
00:16:20.760 --> 00:16:25.159
<v Tal Sholklapper>now for sales and prices, you know, you
gotta work those quality issues out of the

256
00:16:25.159 --> 00:16:27.299
<v Tal Sholklapper>production process as quickly as you can,
and so.

257
00:16:28.380 --> 00:16:31.809
<v Tal Sholklapper>Really what we're focused on is, you know,
trying to deliver a complete solution

258
00:16:31.809 --> 00:16:36.609
<v Tal Sholklapper>here to customers and, you know, from the
PLCs to the controls to the, you know,

259
00:16:36.690 --> 00:16:42.169
<v Tal Sholklapper>analytics to the infrastructure to store
and host all this data, um, try to deliver

260
00:16:42.169 --> 00:16:45.690
<v Tal Sholklapper>that in a complete solution as quickly as
possible so that you can hit the ground

261
00:16:45.690 --> 00:16:49.650
<v Tal Sholklapper>running and your team could be more
efficient, uh, you know, you're not getting back

262
00:16:49.650 --> 00:16:53.409
<v Tal Sholklapper>that extra headcount and, you know, allow
us to come in and partner with you to help

263
00:16:53.409 --> 00:16:57.250
<v Tal Sholklapper>you, you know, achieve those goals faster
with the, you know, limitations we have

264
00:16:57.250 --> 00:16:57.690
<v Tal Sholklapper>right now.

265
00:16:58.349 --> 00:16:58.960
<v Speaker 2>Thank you, guys.

266
00:16:59.080 --> 00:17:04.199
<v Speaker 2>And um I just want to leave you guys with
this image again, that data-driven

267
00:17:04.199 --> 00:17:06.319
<v Speaker 2>manufacturing is achievable.

268
00:17:06.800 --> 00:17:13.280
<v Speaker 2>We are doing it together by bringing
digital twin, ITOT convergence, and data

269
00:17:13.280 --> 00:17:14.319
<v Speaker 2>intelligence together.

270
00:17:15.069 --> 00:17:19.579
<v Speaker 2>And one last point, if I can leave you
with this, you don't have to wait till your

271
00:17:19.579 --> 00:17:22.810
<v Speaker 2>production becomes at a high, large scale.

272
00:17:23.219 --> 00:17:25.890
<v Speaker 2>This is something you can implement.

273
00:17:26.779 --> 00:17:27.479
<v Speaker 2>Early.

274
00:17:28.019 --> 00:17:33.298
<v Speaker 2>If you are getting up at the R&amp;D
scale, even at a pilot scale, this is a great place

275
00:17:33.298 --> 00:17:37.218
<v Speaker 2>to start because the longer you wait, the
bigger the problem it becomes.

276
00:17:37.418 --> 00:17:42.088
<v Speaker 2>It's a lot easier to, to optimize your
operation, extract the knowledge from the

277
00:17:42.088 --> 00:17:44.088
<v Speaker 2>systems early in the cycle.

278
00:17:44.389 --> 00:17:48.938
<v Speaker 2>So if there is one action I can leave you
with is start early, scale fast, come to

279
00:17:48.938 --> 00:17:49.328
<v Speaker 2>us.

280
00:17:49.609 --> 00:17:50.818
<v Speaker 2>We are there to help you.

281
00:17:52.560 --> 00:17:54.239
<v Speaker 1>Thank you for listening to the battery
podcast.

282
00:17:54.319 --> 00:17:58.040
<v Speaker 1>We're putting a lid on our first season of
the show, but we'll be back soon with

283
00:17:58.040 --> 00:17:59.939
<v Speaker 1>season two as we enter a new year.

284
00:18:00.359 --> 00:18:03.680
<v Speaker 1>There will be more guests from around the
world, new conversations from industry

285
00:18:03.680 --> 00:18:06.900
<v Speaker 1>showcases and insights on the different
battery markets around the world.

286
00:18:07.160 --> 00:18:10.640
<v Speaker 1>Make sure to subscribe so you don't miss
the next season's premiere or any new

287
00:18:10.640 --> 00:18:12.339
<v Speaker 1>episodes if you're listening in the
future.

288
00:18:12.800 --> 00:18:16.920
<v Speaker 1>We'll be back soon, but you can always
check out our website, Siemens.com/battery

289
00:18:16.920 --> 00:18:17.880
<v Speaker 1>for more information.

290
00:18:27.349 --> 00:18:30.630
<v Speaker 1>This podcast contains the personal views
and opinions of the speakers.

291
00:18:30.979 --> 00:18:34.300
<v Speaker 1>It is important to note that these
opinions are solely those of the speakers and do

292
00:18:34.300 --> 00:18:38.229
<v Speaker 1>not reflect the views or positions of
Siemens, its management, its employees, or any

293
00:18:38.229 --> 00:18:40.579
<v Speaker 1>entities the speakers may be affiliated
with.

294
00:18:40.949 --> 00:18:44.609
<v Speaker 1>Siemens as a company does not endorse any
of these statements made in the podcast.

295
00:18:45.219 --> 00:18:48.790
<v Speaker 1>Siemens bears no responsibility for
ensuring the content's accuracy or verifying the

296
00:18:48.790 --> 00:18:50.050
<v Speaker 1>statements made in this podcast.
