WEBVTT
1
00:00:00.919 --> 00:00:04.419
(bright electronic music)
2
00:00:08.580 --> 00:00:10.710 line:15%
Hi, everybody, my name is Steve Mulder.
3
00:00:10.710 --> 00:00:12.960 line:15%
I'm the North American OEM director here
4
00:00:12.960 --> 00:00:14.550 line:15%
with Rockwell Automation.
5
00:00:14.550 --> 00:00:17.130 line:15%
And really excited today to be speaking with Horia.
6
00:00:17.130 --> 00:00:18.480
And Horia, maybe we'll start
7
00:00:18.480 --> 00:00:20.280
with having you introduce yourself.
8
00:00:20.280 --> 00:00:22.290 line:15%
Sure, thank you for having me.
9
00:00:22.290 --> 00:00:23.520 line:15%
My name is Horia Saulean.
10
00:00:23.520 --> 00:00:25.380 line:15%
I'm the Director of Robotic Solutions here
11
00:00:25.380 --> 00:00:27.120 line:15%
at DCC Automation.
12
00:00:27.120 --> 00:00:29.400
So Horia, first question I'd like to ask is:
13
00:00:29.400 --> 00:00:31.440
What, from your opinion, could be achieved
14
00:00:31.440 --> 00:00:34.320
with machines and equipment that are DataReady?
15
00:00:34.320 --> 00:00:36.540
Sure, thanks for the question.
16
00:00:36.540 --> 00:00:39.450
You know, there are a lot of capabilities that we can bring.
17
00:00:39.450 --> 00:00:42.813
There's a lotta stuff that our end users could benefit from.
18
00:00:43.800 --> 00:00:45.450
The collaborative approach, right?
19
00:00:45.450 --> 00:00:47.250
I think that we're seeing a trend towards
20
00:00:47.250 --> 00:00:48.963
a lot more collaboration, so.
21
00:00:50.280 --> 00:00:55.143
Reducing waste by being more efficient, right, higher OEE,
22
00:00:56.070 --> 00:01:00.510
reducing power usage, and really proving
23
00:01:00.510 --> 00:01:02.883
that we actually are a lot more efficient.
24
00:01:04.530 --> 00:01:07.980
And really, empowering the workforce, right,
25
00:01:07.980 --> 00:01:10.740
the remaining of the workforce
26
00:01:10.740 --> 00:01:14.220
that's still in place at our end users.
27
00:01:14.220 --> 00:01:16.950
I think that it has a lotta benefits.
28
00:01:16.950 --> 00:01:18.720
Yeah, so I'm kinda curious.
29
00:01:18.720 --> 00:01:21.240
Maybe I'll ask you, with all that potential value
30
00:01:21.240 --> 00:01:23.040
and all the things that having equipment
31
00:01:23.040 --> 00:01:26.340
that's ready to organize and contextualize
32
00:01:26.340 --> 00:01:29.460
and deliver data, why haven't things moved forward
33
00:01:29.460 --> 00:01:30.540
more than they have?
34
00:01:30.540 --> 00:01:31.440
It's a good question.
35
00:01:31.440 --> 00:01:33.630
I think a lot of it has to do with the fact
36
00:01:33.630 --> 00:01:36.180
that some end users don't know really
37
00:01:36.180 --> 00:01:37.683
what kinda data they want.
38
00:01:38.790 --> 00:01:40.563
Others know what they want,
39
00:01:41.880 --> 00:01:45.600
but are a little bit hesitant to pull the trigger
40
00:01:45.600 --> 00:01:48.270
due to the cost, right?
41
00:01:48.270 --> 00:01:52.050
There's a little bit of a upfront cost associated
42
00:01:52.050 --> 00:01:54.483
with integrating all these solutions.
43
00:01:55.710 --> 00:01:59.670
But generally, people talk about data,
44
00:01:59.670 --> 00:02:01.950
but it's hard for them to justify
45
00:02:01.950 --> 00:02:05.250
or really articulate what kinda data is essential
46
00:02:05.250 --> 00:02:10.250
or even relevant to what the OEMs have to provide.
47
00:02:10.620 --> 00:02:13.327
So it sounds like one of those big stumbling blocks is,
48
00:02:13.327 --> 00:02:16.020
"Because I don't know exactly what data I want
49
00:02:16.020 --> 00:02:18.450
and how I want it, I don't do anything,
50
00:02:18.450 --> 00:02:21.210
including even building in the foundational capability."
51
00:02:21.210 --> 00:02:24.150
Correct, and I think it's really, for us as OEMs,
52
00:02:24.150 --> 00:02:25.020
you know, we're looking
53
00:02:25.020 --> 00:02:27.390
to always transfer the knowledge, right?
54
00:02:27.390 --> 00:02:30.600
So because we know what data we can provide,
55
00:02:30.600 --> 00:02:34.620
we always try to share as much as we can
56
00:02:34.620 --> 00:02:37.773
as far as the need, right, versus the want.
57
00:02:39.000 --> 00:02:40.140
You know, as you know,
58
00:02:40.140 --> 00:02:42.030
some things are easier done than others.
59
00:02:42.030 --> 00:02:45.570
So there's some data that we can provide right away, right?
60
00:02:45.570 --> 00:02:48.270
I think DataReady, the first thing in DataReady
61
00:02:48.270 --> 00:02:49.533
is basically OEE.
62
00:02:50.760 --> 00:02:54.363
A lot of customers talk about OEE.
63
00:02:55.290 --> 00:02:57.270
Unfortunately, I think every customer that I have
64
00:02:57.270 --> 00:02:59.193
has a different definition of OEE.
65
00:03:00.120 --> 00:03:03.600
So by us educating them and really showing them
66
00:03:03.600 --> 00:03:06.277
the true value and how to calculate true OEE,
67
00:03:07.560 --> 00:03:11.330
it makes it easier for us to integrate
68
00:03:11.330 --> 00:03:14.670
in future machinery.
Okay, great.
69
00:03:14.670 --> 00:03:15.503
Well, let's talk a little bit:
70
00:03:15.503 --> 00:03:18.060
How have you worked with Rockwell
71
00:03:18.060 --> 00:03:20.550
to kinda move past some of these execution challenges
72
00:03:20.550 --> 00:03:22.203
and these barriers to progress?
73
00:03:23.940 --> 00:03:24.810
You know, for us,
74
00:03:24.810 --> 00:03:27.870
I think we have a history of collaboration.
75
00:03:27.870 --> 00:03:31.410
I think our journey really started back
76
00:03:31.410 --> 00:03:34.113
when we were collaborating on other platforms.
77
00:03:35.664 --> 00:03:40.290
The integrated robotics was really the first step
78
00:03:40.290 --> 00:03:41.943
of our collaboration process.
79
00:03:43.170 --> 00:03:46.770
And from there, we're looking at all of these new platforms,
80
00:03:46.770 --> 00:03:51.330
right, to be, first of all, to embrace them, right,
81
00:03:51.330 --> 00:03:53.685
and also to give feedback, whatever feedback is relevant
82
00:03:53.685 --> 00:03:57.330
to make sure that, from the collaboration,
83
00:03:57.330 --> 00:03:59.980
we develop something that's meaningful for the space.
84
00:04:00.960 --> 00:04:02.610
And also secondly, really to be the ones
85
00:04:02.610 --> 00:04:03.780
that are on the ground floor, right?
86
00:04:03.780 --> 00:04:06.360
So there's a lot of advantage to both,
87
00:04:06.360 --> 00:04:09.870
but DataReady specifically has a lotta potential
88
00:04:09.870 --> 00:04:12.360
to empower really all the other platforms
89
00:04:12.360 --> 00:04:15.480
that we're involved in, collaboration-wise.
90
00:04:15.480 --> 00:04:18.933
So you know, the robots, some of the other,
91
00:04:20.010 --> 00:04:21.630
you know, vision, the AI stuff.
92
00:04:21.630 --> 00:04:24.063
So it kind of all ties together.
93
00:04:25.380 --> 00:04:28.830
But I think, you know, really harnessing the data
94
00:04:28.830 --> 00:04:32.160
from everything and aggregating it and presenting it
95
00:04:32.160 --> 00:04:34.260
is a huge milestone.
96
00:04:34.260 --> 00:04:36.990
So we kinda talked about what could be achieved
97
00:04:36.990 --> 00:04:39.870
if we didn't have these kind of barriers
98
00:04:39.870 --> 00:04:42.480
and stumbling blocks that we've traditionally had.
99
00:04:42.480 --> 00:04:44.220
Maybe you can talk a little bit now,
100
00:04:44.220 --> 00:04:45.810
you've done some things with DataReady,
101
00:04:45.810 --> 00:04:48.210
you've started to move down this path.
102
00:04:48.210 --> 00:04:51.090
What is it enabling you to bring to your customers?
103
00:04:51.090 --> 00:04:54.060
Well, you know, I think a lot of our customers
104
00:04:54.060 --> 00:04:59.060
are really feeling the pain of the shortages in labor,
105
00:04:59.670 --> 00:05:03.090
and it's really labor, I guess, we'll use it broadly,
106
00:05:03.090 --> 00:05:04.990
because it's through the organization.
107
00:05:06.420 --> 00:05:09.000
So just a couple of things, right, that we've noticed
108
00:05:09.000 --> 00:05:11.883
is through DataReady, we're able to provide,
109
00:05:12.930 --> 00:05:14.490
you know, predictive maintenance.
110
00:05:14.490 --> 00:05:16.173
Power usage is another big one.
111
00:05:17.010 --> 00:05:18.610
You know, a lot of our customers
112
00:05:19.680 --> 00:05:21.120
are resource-conscious, right?
113
00:05:21.120 --> 00:05:24.300
So you know, having the ability
114
00:05:24.300 --> 00:05:27.360
to quantify really power usage, right,
115
00:05:27.360 --> 00:05:31.380
via these smart objects really gives them the ability
116
00:05:31.380 --> 00:05:34.560
to make, first of all, informed decisions, right,
117
00:05:34.560 --> 00:05:35.880
but also to make sure that,
118
00:05:35.880 --> 00:05:39.210
with the decisions that they take,
119
00:05:39.210 --> 00:05:41.940
they'll be able to achieve the highest OEE possible, so.
120
00:05:41.940 --> 00:05:42.960
Perfect.
121
00:05:42.960 --> 00:05:44.760
Those are great things that you're doing now
122
00:05:44.760 --> 00:05:45.960
kinda right outta the gates
123
00:05:45.960 --> 00:05:48.960
and things that are challenges today.
124
00:05:48.960 --> 00:05:52.080
What do you see coming in terms of future opportunities
125
00:05:52.080 --> 00:05:56.250
related to this data and information being made available,
126
00:05:56.250 --> 00:05:59.340
you know, from the OT level, from machines and equipment?
127
00:05:59.340 --> 00:06:01.860
Where could it go or where do you see it going
128
00:06:01.860 --> 00:06:05.670
built on top of this foundational ability that is DataReady?
129
00:06:05.670 --> 00:06:08.340
You know, I think it's a good question,
130
00:06:08.340 --> 00:06:12.690
and really, there isn't one silver lining, right,
131
00:06:12.690 --> 00:06:15.300
or silver bullet for the future.
132
00:06:15.300 --> 00:06:17.460
But I think overall efficiency, right,
133
00:06:17.460 --> 00:06:19.083
proving overall efficiency,
134
00:06:20.340 --> 00:06:23.340
overall OEE, right, overall uptime,
135
00:06:23.340 --> 00:06:26.220
and having the ability to differentiate
136
00:06:26.220 --> 00:06:30.240
between individual machinery versus complete line OEE,
137
00:06:30.240 --> 00:06:32.703
right, overall efficiency of the line.
138
00:06:34.140 --> 00:06:39.140
It's tremendous because it gives also the ability
139
00:06:39.240 --> 00:06:41.460
to track potential problem, right,
140
00:06:41.460 --> 00:06:43.770
and not just our specific machinery,
141
00:06:43.770 --> 00:06:45.770
whatever's upstream or downstream of us.
142
00:06:47.460 --> 00:06:51.840
And also, it sort of forces us to be better.
143
00:06:51.840 --> 00:06:54.150
And it kinda forces everyone else to be honest
144
00:06:54.150 --> 00:06:57.030
about, you know, what they can and cannot do.
145
00:06:57.030 --> 00:06:59.550
So I don't think that, in the future,
146
00:06:59.550 --> 00:07:04.050
when we build these lines or these, you know,
147
00:07:04.050 --> 00:07:05.853
higher efficiency machines,
148
00:07:06.780 --> 00:07:08.040
we're not gonna have a situation
149
00:07:08.040 --> 00:07:10.620
where we overpromise and underdeliver.
150
00:07:10.620 --> 00:07:14.280
So I think data is really the key
151
00:07:14.280 --> 00:07:16.080
to proving a lotta those things.
152
00:07:16.080 --> 00:07:19.387
Really being able to objectively say,
153
00:07:19.387 --> 00:07:21.330
"Hey, this is what we said we were gonna do.
154
00:07:21.330 --> 00:07:22.560
This is what we are doing."
155
00:07:22.560 --> 00:07:24.630
And have everybody feel comfortable
156
00:07:24.630 --> 00:07:26.730
that that's really the situation, huh?
157
00:07:26.730 --> 00:07:28.080
Correct, and I think, you know,
158
00:07:28.080 --> 00:07:30.630
just a couple of comments on, you know, proving our value
159
00:07:30.630 --> 00:07:32.640
and this value proposition, right?
160
00:07:32.640 --> 00:07:35.110
There's no better way to prove the value
161
00:07:36.120 --> 00:07:38.430
than having the hard data to provide
162
00:07:38.430 --> 00:07:40.290
after the machine is installed,
163
00:07:40.290 --> 00:07:43.353
after it's run for a couple months or an X amount of years,
164
00:07:44.280 --> 00:07:47.107
you know, having the data there to back up and say,
165
00:07:47.107 --> 00:07:48.900
"Hey, this is what we promised.
166
00:07:48.900 --> 00:07:50.760
This is what we delivered.
167
00:07:50.760 --> 00:07:54.450
And this is really how the customer benefited from this."
168
00:07:54.450 --> 00:07:55.800
I think it's tremendous.
169
00:07:55.800 --> 00:07:57.420
I think the last question I would have for you is
170
00:07:57.420 --> 00:07:59.310
maybe a summarization.
171
00:07:59.310 --> 00:08:02.160
So we've talked about, hey, it's valuable
172
00:08:02.160 --> 00:08:05.400
to be able to organize, contextualize,
173
00:08:05.400 --> 00:08:08.403
make data and information available from equipment.
174
00:08:09.420 --> 00:08:13.860
And it's a way of moving past this stalemate, maybe,
175
00:08:13.860 --> 00:08:16.980
that we've had is being agnostic or being able
176
00:08:16.980 --> 00:08:20.490
to move that data in industry standard formats,
177
00:08:20.490 --> 00:08:22.470
even if you don't know exactly where it's gonna go
178
00:08:22.470 --> 00:08:24.780
or how it's gonna be used outta the gates.
179
00:08:24.780 --> 00:08:27.180
I guess my last question for you would be:
180
00:08:27.180 --> 00:08:29.220
What's unique about the approach
181
00:08:29.220 --> 00:08:30.870
that Rockwell has taken and the things
182
00:08:30.870 --> 00:08:32.010
that we've done together?
183
00:08:32.010 --> 00:08:36.060
Why do it the way Rockwell does with DataReady built
184
00:08:36.060 --> 00:08:39.090
in Logix and built with Optix?
185
00:08:39.090 --> 00:08:41.400
What would you say is unique or makes sense
186
00:08:41.400 --> 00:08:43.650
in doing it this way versus other ways
187
00:08:43.650 --> 00:08:45.030
that might be available?
188
00:08:45.030 --> 00:08:46.650
I mean, there are a lotta benefits, right?
189
00:08:46.650 --> 00:08:49.110
Some that are really obvious is, you know,
190
00:08:49.110 --> 00:08:51.270
the modular approach.
191
00:08:51.270 --> 00:08:54.210
I think that having, you know, these modular smart objects,
192
00:08:54.210 --> 00:08:57.270
right, where we can drop an OEE object,
193
00:08:57.270 --> 00:08:58.950
we could drop a power object,
194
00:08:58.950 --> 00:09:01.830
or we could drop something in the future, right,
195
00:09:01.830 --> 00:09:03.360
that's developed for the platform
196
00:09:03.360 --> 00:09:06.153
really makes it easy to integrate, easy to roll out.
197
00:09:07.800 --> 00:09:12.180
And it sort of kind of plays within the same environment
198
00:09:12.180 --> 00:09:15.423
as the visualization portion of it, right, which is Optix.
199
00:09:16.560 --> 00:09:18.630
So all of them play together,
200
00:09:18.630 --> 00:09:21.150
but they're very modular, they're very easy.
201
00:09:21.150 --> 00:09:26.150
So hopefully, in the future when we have more smart objects,
202
00:09:28.500 --> 00:09:30.667
right, I think that we'll be better prepared to say,
203
00:09:30.667 --> 00:09:33.387
"Okay, well, we offer all these things."
204
00:09:34.560 --> 00:09:36.720
But for the time being,
205
00:09:36.720 --> 00:09:38.620
I think just having the platform
206
00:09:39.990 --> 00:09:42.333
being there, right, which is Optix, right,
207
00:09:43.380 --> 00:09:46.980
I think it's important just for the OEE perspective,
208
00:09:46.980 --> 00:09:50.460
the power usage, right, and whatever other smart objects
209
00:09:50.460 --> 00:09:51.753
that we have available.
210
00:09:53.340 --> 00:09:56.490
And also having the ability to do VPN.
211
00:09:56.490 --> 00:09:57.960
I mean, there are a lotta different features
212
00:09:57.960 --> 00:09:59.790
that are sort of baked into this.
213
00:09:59.790 --> 00:10:01.770
But yeah, the platform is very easy,
214
00:10:01.770 --> 00:10:03.840
very, very easy to navigate.
215
00:10:03.840 --> 00:10:06.630
Well hey, I think I wanna thank you for your feedback
216
00:10:06.630 --> 00:10:08.943
and your input and your perspective.
217
00:10:09.870 --> 00:10:11.610
Obviously, we at Rockwell think it's great,
218
00:10:11.610 --> 00:10:13.680
but it's super to hear from a customer like you
219
00:10:13.680 --> 00:10:16.830
that's out trying to serve your customers better every day,
220
00:10:16.830 --> 00:10:19.350
giving us your perspective on how to use this
221
00:10:19.350 --> 00:10:21.630
and how it can change the game.
222
00:10:21.630 --> 00:10:23.015
Sure, thank you for having me,
223
00:10:23.015 --> 00:10:25.980
and again, I think it's the collaborative processes
224
00:10:25.980 --> 00:10:27.483
has been a success so far.
225
00:10:28.320 --> 00:10:30.480
And we're really excited about, you know,
226
00:10:30.480 --> 00:10:32.070
the potentials of DataReady.
227
00:10:32.070 --> 00:10:33.570
Perfect, thanks. Horia.
228
00:10:33.570 --> 00:10:34.403
Thank you.
229
00:10:34.403 --> 00:10:37.852
(bright electronic music)