From SPE Standards to Hands-On Automation with McKenzie from CLN of SF and Ed from HARTING (Automate 2024)

WEBVTT

00:00:00.100 --> 00:00:00.781
I'm McKenzie Reed.

00:00:00.781 --> 00:00:15.163
I've worked for Harding for the last eight years and my primary function now is single-pair Ethernet standards development, mostly through ODBA, a little bit through IEEE and TIA other standards organizations.

00:00:15.163 --> 00:00:37.374
And then last May my wife and I acquired an industrial machinery company in South Florida doing three-axis CNC router tables and a proprietary machine that bends industrial outdoor signage, so like the profile for like a sign that will go on the outside of your building or like a plaza or something like that.

00:00:37.374 --> 00:00:40.281
So industrial automation in that respect.

00:00:41.624 --> 00:00:46.671
Yeah right on, I guess I'll introduce myself again.

00:00:46.671 --> 00:00:53.628
We've met before Ed Garskowitz, edgy, long time Harding employee, 26 years.

00:00:53.628 --> 00:01:11.875
I am currently, and most recently, in the role of senior industrial segment manager for automation and robotics A role, by the way, with some big footsteps, because that's one of the roles that mckinsey actually the role you joined the company yeah, yeah yeah, so yep, first automation, ism.

00:01:12.534 --> 00:01:20.646
Uh, that was when it was split from machinery and automation to just automation, because the market had gotten big enough to like justify bringing on ahead.

00:01:20.646 --> 00:01:29.105
And and I worked together in the same pod you were energy man I was broadcasting which was a lot of fun.

00:01:29.287 --> 00:01:34.805
Yep, yeah you said pod like podcast.

00:01:34.805 --> 00:01:37.188
Oh, what's up?

00:01:37.510 --> 00:01:42.602
uh like our seating pod oh, right, yeah cool like kind of this four person thing.

00:01:42.662 --> 00:01:42.802
What?

00:01:42.802 --> 00:01:43.864
Why is it called a pod?

00:01:44.566 --> 00:01:48.334
It was just like a big square and we had like a meeting table in the middle of it.

00:01:48.334 --> 00:01:51.368
Actually, that was like my favorite setup that we had in the office.

00:01:51.608 --> 00:01:52.311
I love the pod.

00:01:52.311 --> 00:01:56.590
It enables collaboration right, yes, exactly it does.

00:01:56.739 --> 00:01:59.808
Little communities within your whole floor space.

00:01:59.808 --> 00:02:00.771
Yep it does.

00:02:00.771 --> 00:02:02.359
Pod.

00:02:02.359 --> 00:02:01.709
It sounds like.

00:02:01.399 --> 00:02:01.459
Orcus or something.

00:02:01.150 --> 00:02:02.552
Yes, it does Pod.

00:02:02.552 --> 00:02:03.795
It sounds like Orcus or something.

00:02:05.141 --> 00:02:07.903
Yes, or the pod people in sci-fi, you know.

00:02:08.864 --> 00:02:10.626
I just imagine this like in-shape thing.

00:02:11.306 --> 00:02:12.687
So, Allie you should introduce yourself.

00:02:13.608 --> 00:02:16.170
Oh, I'm Allie Gilpin.

00:02:16.170 --> 00:02:27.580
I started a systems integration firm after being a controls engineer for 10 years, and where I first actually found Harding connectors was at an OEM.

00:02:27.580 --> 00:02:36.826
I came from process side, so I came from process automation and transferred into like factory machine automation Cool and so that was a change for me.

00:02:36.826 --> 00:02:39.788
But now you do it.

00:02:41.901 --> 00:02:42.926
I'm Nikki Gonzalez.

00:02:42.926 --> 00:02:47.659
Although some in the industry may remember me from my maiden name days.

00:02:47.659 --> 00:02:51.620
I actually met an old Keyence colleague earlier this morning.

00:02:51.620 --> 00:02:57.754
I used to go by Halgrim's daughter a lot harder to figure out how to spell, but you kind of don't forget it.

00:02:58.056 --> 00:03:01.460
And yeah, I've kind of come full circle in a lot of ways.

00:03:01.460 --> 00:03:47.927
I used to be a field sales engineer for machine vision, barcode readers and laser markers back when those were small enough product lines to be lumped together Sure, which they're really not today, right, yeah, and I've kind of worked my way around different things because I'm perpetually curious and I get really bored once I learn something really well and I find myself, I guess, the happiest at a bottom of a steep learning curve, with a little bit of anxiety at the bottom of my pit of my stomach and there's just constantly something new to learn in this industry completely and never ended, and so when, when I heard somebody on LinkedIn to ask about connectors the other day and this is a couple months ago but kind of how we ended up connecting with Harding and why we're here having these conversations, it's just something that I never really thought about.

00:03:48.240 --> 00:03:50.669
It didn't touch what I did enough.

00:03:50.669 --> 00:03:59.871
But, like a factory floor, a manufacturing facility has so many facets and I think a lot of us are kind of used to our little space in the industry.

00:03:59.871 --> 00:04:01.782
We look at things through a certain lens.

00:04:01.782 --> 00:04:21.055
And me, coming in as a sales engineer with vision systems, of course I was always looking for a problem to solve with vision and then I ended up wanting to learn more about the handling systems, more about the control systems, and I guess I just kind of can't get enough of trying to learn.

00:04:21.055 --> 00:04:32.672
The next thing Didn't think about connectors before, but I am actually really fascinated by meeting you and your journey because I actually now have a goal I would love to own a manufacturing business so that at some point I can kind of practice what I preach.

00:04:33.581 --> 00:04:36.220
You know like test your own stuff on your own business.

00:04:36.560 --> 00:04:49.408
We're about a year in, almost exactly coming up in June, and and it's a lot of what you just said of like the anxiety at the bottom level of like, oh my God, I feel like I don't know anything.

00:04:50.899 --> 00:04:55.882
I've been in automation for 12 years and I'm just like, yep, no, all right.

00:04:55.882 --> 00:04:56.745
What is this problem?

00:04:56.745 --> 00:04:58.206
Every day is a new problem.

00:04:58.206 --> 00:05:12.391
Every day is like we have to try and find a solution in real time, whether it's like a machine that's been out in the field for 15 years which we don't even make anymore and we're three iterations of machine past that one, but we have to support it, yeah.

00:05:12.391 --> 00:05:28.928
Or or just improving the design of what we are doing now, which is, you know, including connectors like we're taking hard looks at Harding products and then things that are outside of the Harding portfolio to connectorize more of the machinery.

00:05:28.928 --> 00:05:36.569
So it's like I was just actually talking about that this morning with one of our suppliers of like practicing what I preach.

00:05:36.569 --> 00:05:39.269
It's like I've been talking about automation for a long time.

00:05:39.480 --> 00:05:45.009
I did automation for four and a half years at Rockwell Automation as a field engineer.

00:05:45.009 --> 00:05:47.750
Like I didn't just jump into like a machinery business.

00:05:47.750 --> 00:05:51.225
It was like they shipped me all over the country starting up industrial machinery.

00:05:51.225 --> 00:06:00.290
So it's like a little bit of that experience, but different animal now of like being in the driver's seat, yeah, real yeah, yeah, it's fun though.

00:06:01.372 --> 00:06:20.872
Uh, we just went to our like biggest trade show of the year, uh, last month for the industrial sign industry and, um, my wife comes from that world of doing like trade show exhibits and whole like user experiences, so that was that was a lot of fun to like kind of reintroduce the whole company there I mean that's a huge resource that you have.

00:06:20.951 --> 00:06:29.750
I mean most new companies or people starting out like I've built many a booth from scratch, not knowing what I'm doing whatsoever, with no professionals.

00:06:30.351 --> 00:06:32.706
That's a, that's a pretty nice built-in advantage that you have right there.

00:06:32.725 --> 00:06:39.942
Um, but something that I'm seeing you know more and more in the industry as well is that we're, as we get a chance to talk about it more with the outside world.

00:06:39.942 --> 00:06:44.730
We can have more collaborations with people, whether they know our industry or not.

00:06:44.730 --> 00:06:59.829
Like there's more people kind of coming in, becoming aware of machinery, automation, manufacturing, what we do, and a lot of people think it's really cool and, even if they have no background in it, like they want to come in and it's been traditionally kind of a closed industry.

00:06:59.829 --> 00:07:07.009
Like you have to have connections to be able to learn about this stuff, and I love this direction of like Harding being part of this.

00:07:07.009 --> 00:07:22.834
Hey, we want to just get the information out to the people, however they want it Right, be a supportive resource, be somebody that people can call on when they need to know about this very niche area of the industry which I mean there's just like so much to so much to know.

00:07:22.834 --> 00:07:26.603
Our good friend Josh Vargis made a really good point the other day.

00:07:26.642 --> 00:07:47.043
He said oh, if you want to be impressive, just get really good at like a really niche thing that most people don't care about, and then you'll always sound super smart yeah and that's easy to do in this yeah, there, yeah, you could, niches in the niche, pull on whatever thread you want to pull on and you know talking about being a subject matter expert or trying to just get the word out there.

00:07:47.043 --> 00:08:00.088
Uh, we're sitting with the person that's probably been in more harding marketing videos than anyone, which is ed uh and touched basically every product line in your uh, in your what 26 years you said yeah, that's right.

00:08:00.910 --> 00:08:20.894
um, I think we do a pretty good job of that of like, whether it's industrial ethernet Week, which happened a couple months ago, which was single pair Ethernet focused as well as other parts of emerging Ethernet, or, like our Han product line, we're pretty much always kind of doing customer outreach learning sessions.

00:08:20.894 --> 00:08:24.012
Have you guys seen our digital experience center?

00:08:24.012 --> 00:08:24.675
No.

00:08:24.956 --> 00:08:25.540
In the headquarters.

00:08:25.540 --> 00:08:28.185
It's very cool, uh, state of the art.

00:08:28.185 --> 00:08:34.110
Instead of traveling during the covid year, we built that facility with like a big led wall for presentations.

00:08:34.110 --> 00:08:42.644
So if you've seen anything that's kind of recent within the last few years at harding, it's out of that studio right, that's where gora and I had our conversation the last time.

00:08:42.683 --> 00:08:54.888
Yeah, yeah so so you guys were definitely, if not our only, guests that had a recording studio on the other end of our meeting, nice Versus just showing up with headphones or whatever.

00:08:54.888 --> 00:09:05.001
So it's very impressive and I think we're very much looking forward to an opportunity to visit Not that- I'm sure we have an open invitation, but we do a whole lot of travel already.

00:09:05.179 --> 00:09:08.948
Sure, Trying to really like.

00:09:08.948 --> 00:09:33.558
If you gave me carte blanche, like what I wanted to do all year and it had nothing to do with like family responsibilities or other work that I have to get done, I would be visiting all of these places and talking to all the eds in all of the different niches, because they are also the people like as the workforce is transitioning, and especially younger people, they stick around one discipline you know less often than I think, often than I think used to be the case.

00:09:33.558 --> 00:09:44.432
But once you find people that are passionate enough and have been in a niche long enough, the more we can proliferate what they know and make sure that they're a known connection in all of our different communities.

00:09:44.432 --> 00:09:48.414
I know for us we work with a lot of smaller systems integrators that are growing.

00:09:48.414 --> 00:09:56.778
They're not going to be experts at everything, but in order to be effective and grow their company they really have to know who to call on for those different areas.

00:09:57.485 --> 00:09:59.490
Yeah, I'd say we talk about that a lot.

00:09:59.490 --> 00:10:26.094
When it comes to the standards body, what we talk about within ODBA meetings a lot is that we have to define these standards down to granular levels that we haven't done before, which includes connectors, actually, you know, calling out one specific connector to use for IP20 applications or IP65, ip67 applications, and it's because I fully agree that I think that people are going to be more generalist than specific.

00:10:26.094 --> 00:10:27.216
Moving forward.

00:10:27.216 --> 00:10:37.038
It's like within basically any company that you look at, people are wearing multiple hats and don't really have the bandwidth anymore to just be that specialist.

00:10:37.038 --> 00:10:44.719
You're expected to be the subject matter expert and extremely niche, specific and also do another, probably two roles on top of that.

00:10:44.719 --> 00:10:45.184
Yeah.

00:10:45.385 --> 00:10:52.073
So, from the standards point of view, we're trying to go down to an additional layer that we didn't go to before.

00:10:52.073 --> 00:11:03.136
To be extremely explicit, of like you don't have to go figure this out, Like we will figure it out for you and just give you the roadmap, and then you just implement, um, and you keep going about.

00:11:03.136 --> 00:11:11.111
You know your design process, like here's the five that you use, here's the cable, here's the chip set, here's the connector for this application.

00:11:11.111 --> 00:11:20.355
And being more specific about what applications certain technologies go into and which ones they don't go into, I think is kind of the main difference.

00:11:22.706 --> 00:11:28.138
Right, I would say McKinsey is the Michael Jordan of SPE.

00:11:28.505 --> 00:11:30.472
I kind of feel really honored sitting next to him.

00:11:31.615 --> 00:11:35.649
If you have any questions about that in particular, I would fire away right now.

00:11:37.875 --> 00:11:40.519
I guess my question is SPE specifically.

00:11:40.519 --> 00:11:44.014
How do you see that potential to transform your manufacturing business?

00:11:44.014 --> 00:11:53.678
Like what do you have strategic imperatives to or plans to utilize that technology specifically as any kind of catalyst within your business?

00:11:56.865 --> 00:12:01.730
I think that it's going to enable IOT really for the first time.

00:12:01.730 --> 00:12:14.946
We've all been in different sectors of this industry for varying amounts of time and I think that we haven't seen IOT grow the way that we've seen IoT grow, you know.

00:12:14.946 --> 00:12:23.870
So, like on the consumer side, with consumer appliances or whatever you choose to look at smart TVs, whatever Everything is integrated, everything talks to each other.

00:12:23.870 --> 00:12:26.715
Everything in your home talks to each other, if you want it to be that way.

00:12:26.715 --> 00:12:31.356
We haven't seen that happen in industrial automation or process automation yet.

00:12:31.356 --> 00:12:35.168
Haven't seen that happen in industrial automation or process automation yet.

00:12:35.168 --> 00:12:41.408
I think that SPE will help with actually bringing that to the forefront, because you're going to cost effectively put things on Ethernet for the first time.

00:12:41.408 --> 00:12:46.426
It's going to be easier to implement at varying speeds and distances.

00:12:46.426 --> 00:12:58.498
I know that you spoke with Gota and Ed about this previously, but like starting at 10 megabit per second and going up to multi-gigabit speed, all on one network, one common protocol, one common connector.

00:12:58.498 --> 00:13:11.650
You know if it's for industrial automation or process automation, there are a few different flavors, but I really just see it facilitating that for the most part, and within my own business, where we are already planning to implement.

00:13:11.692 --> 00:13:17.532
It is the edge cases, so the sensors that we already have on the machine.

00:13:17.611 --> 00:13:21.178
Some of them can be retrofitted for SPU, which is what we're working on right now.

00:13:21.178 --> 00:13:33.184
Other ones where you know, there are adapter kits where Harding has partnered with companies like SparkFun and other partners to put a whole adapter kit together and other partners to put a whole adapter kit together.

00:13:33.184 --> 00:13:55.134
That's another one that I'm looking at implementing to just add more sensing to, specifically, the CNC 3-axis router tables where we want to start measuring temperature and vibration on the spindle, which will run 10 hours a day at 24,000 RPM, just back-to-back cutting for wholesale manufacturers.

00:13:55.134 --> 00:14:11.432
So we want to be able to have our customers monitor what's going on with their machine and then the bonus being that we're also able to monitor where we get an alert and are able to actually contact our customer before they contact us for technical support.

00:14:11.432 --> 00:14:12.596
That's huge.

00:14:12.596 --> 00:14:15.815
That's going to be a big enabler for us moving forward.

00:14:15.815 --> 00:14:18.393
And then it's just more analytics.

00:14:18.393 --> 00:14:26.076
I want to know more about what's going on with the machine before things break or need maintenance.

00:14:27.184 --> 00:14:37.996
Yeah, so a big part of it is obviously operational efficiency, cost savings, quality, but then really it's also enabling you to potentially provide a much better customer experience right than your competitor.

00:14:37.996 --> 00:14:38.284
Sure.

00:14:38.284 --> 00:14:40.870
Yeah, it's pretty exciting.

00:14:41.230 --> 00:14:41.511
Yeah, it's.

00:14:41.511 --> 00:14:49.434
You know, on the one side of the business, we have a specialized machine that has a patent and all this fancy technology.

00:14:49.434 --> 00:14:57.293
On the other side, with the 3-axis CNC router tables if you're familiar with them, a router table is a router table is a router table.

00:14:57.293 --> 00:14:59.871
It's the same general technology.

00:14:59.871 --> 00:15:07.793
So you have to set yourself apart in other ways, and the way that we do it is through our service and technical support, and so this is just the next iteration of that.

00:15:07.793 --> 00:15:29.409
We're remotely, if you give us access, we're remotely monitoring your machine and can tell you when it's time for maintenance, when you're having premature wear on any one of the specific components, and one of the most expensive and sensitive things on the machine is actually the 11 horsepower spindle, so you want to protect that at all costs.

00:15:29.409 --> 00:15:29.971
Yeah.

00:15:30.110 --> 00:15:38.321
But some of our customers are more output driven and they're like we will just replace the spindle.

00:15:38.321 --> 00:15:40.231
We are just all about output.

00:15:40.231 --> 00:15:44.856
And other ones are like no, I want this spindle to last for 15 years.

00:15:44.856 --> 00:15:47.474
So anything that we can do to protect it, we want to protect it.

00:15:47.474 --> 00:15:49.226
So you know.

00:15:49.226 --> 00:15:54.177
Again, going back to connectivity and networks, that's really where we're looking to improve.

00:15:54.177 --> 00:15:59.114
By the end of this year we aim to have a single pair Ethernet solution on the machine.

00:15:59.956 --> 00:16:00.638
It's pretty exciting.

00:16:00.638 --> 00:16:06.794
But yeah, like you said, different customers have different goals and so they're not all focused on the same metric necessarily.

00:16:06.794 --> 00:16:16.618
I've talked to people that are like, oh, we have a machine down and you know, this is a huge deal, and some people it costs them tens of thousands of dollars an hour or more.

00:16:16.618 --> 00:16:25.291
And then others are like, yeah, it's totally fine, this is down for a week, so you can't make the assumptions.

00:16:25.291 --> 00:16:35.394
But I think connectorization, modularization, flexibility right, and having, let's say, something like Ethernet, you can choose to use all of that power or not, but you have it built in if you need it.

00:16:35.835 --> 00:16:53.284
Yeah, right, I'm seeing a lot of that in terms of like design projects that we've been working on is designing for future capabilities as well, because we all know that, like you, have a process today, but if you're a forward-thinking company, you're going to potentially change it or add on to it or do something right.

00:16:53.525 --> 00:16:55.131
How do you do that without starting from scratch?

00:16:55.131 --> 00:17:02.575
Do you have a piece of hardware that you have to completely replace the system, or can you, you know, make those changes as business evolves?

00:17:02.575 --> 00:17:12.479
Right, and I think we're seeing that with a lot of the soft platforms that are coming out, less, you know, reliance on one specific piece of hardware.

00:17:12.479 --> 00:17:21.733
And you know, with, I think, the standardization of connectors, right, you get more flexibility by it being standardized, because then you can use them in more places.

00:17:21.733 --> 00:17:25.255
You can, you know, stock replacements and spares and things like that.

00:17:25.255 --> 00:17:48.435
And I don't know if it's like commercial reasons or industry norms or whatever, but we've kind of been very siloed in the past and like, just like, I mean, I guess the same thing could be said for things like the consumer ecosystem, sure, but wanting to keep people in your kind of grip, right, use this specialty and then you can't replace it except for with anything but mine.

00:17:48.435 --> 00:17:53.567
And I think our generation in particular, and younger people, they don't appreciate that attitude anymore, they're like you know what?

00:17:53.627 --> 00:18:03.015
I want you to actually earn it and I want to be able to switch over and not just use you because the cost of changing is too high or because I'm now caught in some sort of barrier.

00:18:03.015 --> 00:18:06.432
Competitively, obviously, companies want to build a moat.

00:18:08.046 --> 00:18:27.397
I think, a really good example of that and I'm not the expert on this, I don't operate within this standards project, but it's the Open Compute Project for data centers, which we've been involved in, I think, since back in 2016 or 2018.

00:18:27.397 --> 00:18:29.880
Center space and said we want you to standardize on.

00:18:29.880 --> 00:18:43.153
You can have your own proprietary technology, but we have to standardize on where the mounting holes are, where of all the individual components that go inside of these blades for data centers.

00:18:43.173 --> 00:18:50.605
We have to standardize on what these look like and where they go and how they get mounted and what their power requirements are and what their outputs are.

00:18:50.605 --> 00:18:59.067
Everything like that they moved in the direction of you can be competitive in your offering, but we have to standardize on the hardware.

00:18:59.067 --> 00:19:26.753
So I completely agree with you that the users are going to be looking for more options where you may want to use vendor A for an HMI, vendor B for a PLC and vendor C for a drive, and the expectation moving forward is going to be that all those things work together and aren't, you know, safeguarded behind a proprietary, you know like annual cost, or that they just flat out won't work with each other.

00:19:27.684 --> 00:19:37.250
Yeah, and I think COVID kind of exposed a lot of the flaws of this model where we don't work together, because if you can't get something, you have to do something, you have to change over right.

00:19:37.250 --> 00:19:38.784
It was really painful for a lot of people.

00:19:39.306 --> 00:19:52.567
That was before my time at CLN, but that exact thing happened where the manufacturer of the variable frequency drives that we were using they were just nowhere in the world All of a sudden you could get them drives that we were using.

00:19:52.567 --> 00:19:53.288
They're just nowhere in the world.

00:19:53.288 --> 00:20:10.256
All of a sudden you could get them, and so they had to get really creative of finding an alternate that would be as close to a drop-in replacement as you could get, and it wasn't a seamless fit but it worked and I have about 50 of them still sitting in the inventory because we don't use them.

00:20:10.256 --> 00:20:13.971
It was just kind of to get through that push, yeah, and now I have to.

00:20:13.971 --> 00:20:18.603
You know, like figure out was just kind of to get through that push and now I have to, you know, like figure out what I'm going to do with that.

00:20:18.623 --> 00:20:24.574
But you know that's a pain point that I'm living right now is that before my time they had a problem.

00:20:24.574 --> 00:20:29.914
They just had to solve it for the moment, and then now we're kind of figuring out what we're going to do with it now that things have gotten back to normal.

00:20:29.914 --> 00:20:33.085
But I'm even seeing that you know with it, now that things have gotten back to normal.

00:20:33.085 --> 00:20:39.904
But I'm even seeing that, you know, for whatever reason there's not a root cause that I've identified yet but that lead times are getting pushed out pretty drastically.

00:20:39.904 --> 00:20:49.214
In Q1 of this year we went on one part from six weeks to 22 within, you know, like one reorder, and couldn't really get an explanation as to why.

00:20:49.214 --> 00:20:55.478
So, like we're looking for those options of like vendor A, b and C as a swap-out replacement when we need it.

00:20:57.365 --> 00:21:11.534
Yeah, because I mean just yeah, relying on one vendor or one, everything is great, it's fine, but when you're forced to make these tradeoffs because you can't get what you, you know, originally signed up for, you have to have some options.

00:21:11.534 --> 00:21:14.876
Sure, and I think you know a lot of people kind of changed.

00:21:14.876 --> 00:21:16.259
You know what this is actually necessary.

00:21:16.259 --> 00:21:18.760
We have to be able to make these crosses.

00:21:18.760 --> 00:21:26.856
You know we have to be able to collaborate as an industry Because ultimately, if our customers can't automate, then our entire industry loses.

00:21:26.856 --> 00:21:35.700
Yep, right, and I think you know, with robotic deployments, for instance, like why the heck has it taken so long in the US for us to really start deploying lots of robotics?

00:21:35.700 --> 00:21:41.037
And not to say that robots are the answer to every automation challenge or that we should be automating everything with robots.

00:21:42.105 --> 00:21:50.355
Personally, having worked with, like, gantry systems, there's tons of other options which are often better, but I have seen, you know, robot deployments that failed.

00:21:50.355 --> 00:22:11.015
It was really like a lack of training, maintenance, knowledge, and I think if we standardize more, then those sorts of things can be more general, people can be generally more aware of like hey, this is generally how we need to maintain and operate robots Versus it kind of used to be like every vendor had their own class that was very specific.

00:22:11.015 --> 00:22:15.192
It's a very closed system and so it just doesn't become like general knowledge.

00:22:15.192 --> 00:22:21.416
It's kind of gatekept, like you have to be able to afford to go to the class and become a specialist in this and learn this particular operating system.

00:22:21.416 --> 00:22:26.773
And this is maybe just you know my view.

00:22:26.834 --> 00:22:47.358
Looking back, like I feel like we would have gotten more deployment faster if we were kind of more open about it this way Shared more information, made more hardware, more interfaces, interoperable Because then, yeah, it's risky to like go down a path, invest a lot of money in something that you can't change.

00:22:47.358 --> 00:22:51.529
Sure, and you know manufacturing businesses, a lot of them.

00:22:51.529 --> 00:23:01.384
I mean, maybe you can speak to this, but like your goal every day is to run your machines and run your business, and then you have some time to hopefully work on the business, make investments, like all of those things.

00:23:01.384 --> 00:23:03.192
But you have to be conservative.

00:23:03.192 --> 00:23:07.415
You can't just like jump on every new trend and start implementing it on the floor.

00:23:07.715 --> 00:23:23.785
Sure, does it de-risk it to feel like you have options and more ways that you can make money on your investment if things change.

00:23:27.025 --> 00:23:37.012
Right now, we're in the mode of making improvements to both of the flagship product lines and we're doing it slowly and, I think, with purpose, to make sure that we don't break anything that came before.

00:23:37.012 --> 00:23:47.361
Yeah, because, as I said before, we have to support what's out there and, specifically on our channel letter machine, we'll release a new version of it.

00:23:47.361 --> 00:23:49.323
You know when it's ready and eventually.

00:23:49.323 --> 00:24:09.651
But I want to make sure that everything that we change on that machine is reverse compatible where we can put it into a kit and ship it to a customer, because I want to make sure the customers that bought a machine in 2023 or 2022 are still going to get the latest and greatest in terms of, like the software and the firmware side, which we're working on, as well as any hardware improvements.

00:24:09.651 --> 00:24:19.992
So it's taking longer than I would like it to, but we're doing it in a way where it's like, okay, we're going to make sure that these are drop-in, replacement improvements to the machines that are out in the field.

00:24:20.486 --> 00:24:45.635
And that's kind of how we're de-risking the situation of getting away from products and suppliers that are maybe like long in the tooth, where we have concerns that we're not going to be able to get those components in a few years, and just making sure that even machines that we haven't made product lines that we haven't made in a few years are still supported with the latest and greatest in controls and electronics.

00:24:45.635 --> 00:24:48.751
Ed, I think you were going to say something.

00:24:51.246 --> 00:25:03.080
One of the things that I wanted to say on the standardization topic is that what I like about it, the beauty of it also, is it forces the supplier to innovate.

00:25:03.080 --> 00:25:07.455
So let's say, the interface itself is standard, right, it has to fit.

00:25:07.455 --> 00:25:11.109
It has to fit in that box, that profile, whatever.

00:25:11.109 --> 00:25:17.619
So how does a supplier differentiate their product from any other person's product besides price?

00:25:17.619 --> 00:25:23.116
And so what you do is you add bells, whistles where you can.

00:25:23.116 --> 00:25:30.999
Maybe you make your product easier to use, maybe feel installable, whatever you can do to then differentiate your product.

00:25:30.999 --> 00:25:37.233
So I think standardization also supports innovation, kind of in a backdoor way.

00:25:38.707 --> 00:25:47.194
I have a question about single-pair Ethernet because I'm thinking about implementation and this is after, because we have IO-Link right now and that's kind of how we do it.

00:25:47.194 --> 00:25:48.057
We do it in clusters.

00:25:48.057 --> 00:25:54.208
Single-pair Ethernet is going to let us do every single device has an IP address and we're just going to talk to that directly.

00:25:54.208 --> 00:26:10.715
But that's going to blow up our networks and so do you guys have a partner in networks to help your customers when they do finally get all of their devices in their plants with their own IP address?

00:26:10.816 --> 00:26:12.086
Yeah, which is.

00:26:12.247 --> 00:26:13.632
I think I'm excited for that.

00:26:13.912 --> 00:26:20.738
It's a challenge and it may finally push us into IPv6 versus v4.

00:26:21.839 --> 00:26:22.124
Oh, definitely.

00:26:22.526 --> 00:26:29.739
Which has been an option on a lot of control devices for the last 15 years at least.

00:26:29.739 --> 00:26:30.645
You know.

00:26:30.645 --> 00:26:36.276
For me, when I was commissioning machinery, it was like a checkbox of whether I wanted to use IPv4 or v6.

00:26:36.276 --> 00:26:42.753
For any listener that's not familiar with what we're talking about, it's just adding more strings to the IP address.

00:26:43.105 --> 00:26:44.993
Yeah, we literally ran out of IP addresses.

00:26:45.244 --> 00:26:49.826
Yeah, which would just exponentially open it up In terms of, like, the bandwidth and the traffic on there.

00:26:49.826 --> 00:26:56.770
That's kind of where I think that the network will continue to have to evolve.

00:26:56.770 --> 00:26:58.932
We have to get really good at that.

00:26:59.672 --> 00:27:22.736
ODBA did a good job with this back in the DeviceNet days where you would have a DeviceNet network of 40 nodes and maybe all of those were variable frequency drives and then it had a converter to Ethernet and then from your PLC you would only really see that connection point and then you could drill down into all those drives.

00:27:22.736 --> 00:27:31.097
But now what we're talking about is each one of those drives has an IP address, and not only that, but all the sensors that are out on the conveyor belts or your process automation application, they also have it.

00:27:31.097 --> 00:27:40.134
So I think that it won't be gateways in the way that we understand gateways today, but there'll be access points to where you know.

00:27:40.134 --> 00:27:49.287
You kind of just like open up the tree and here's a whole plethora of IP addresses and then you close that one, you navigate to the next tree and then you have a whole bunch of them.

00:27:49.287 --> 00:27:51.530
But it is a challenge.

00:27:52.112 --> 00:28:02.775
The network companies, like the ones that do the networking technology and switches and routers they're all taking very serious looks at how we deploy this.

00:28:02.775 --> 00:28:04.878
I'm excited.

00:28:04.878 --> 00:28:17.693
Benefit of it will be that there aren't going to be a lot of customers that do a full deployment of SBE and we're changing over our entire plant.

00:28:17.693 --> 00:28:22.611
Maybe there will be a greenfield customer that does that, where we want the latest and greatest of everything.

00:28:22.611 --> 00:28:31.038
But I think that SBE will be rolled out into the market and already is being rolled out into the market as like pocket applications.

00:28:31.038 --> 00:28:31.440
Sure yeah.

00:28:32.701 --> 00:28:34.448
And we can kind of like deal with it as we go.

00:28:36.380 --> 00:28:45.371
I'm hearing from our friends in networking that the startup-y customers are the ones that are wanting basically everything like with a single just IP address, up to the cloud.

00:28:45.371 --> 00:28:45.592
Yeah.

00:28:46.160 --> 00:28:47.102
Virtual PLCs.

00:28:47.102 --> 00:29:17.769
They're really trying to get ahead of this using the older hardware and I think also their talent pool is more modern software engineers and so they have a hard time getting traditional controls folks because just the way that their companies are operating, the way they're recruiting, they have this kind of different talent pool that they're looking at and I think they're looking for they're the ones that would be doing a Greenfield project, Like let's just connect everything this way, Right?

00:29:17.769 --> 00:29:21.807
I think that's a very small percentage of what's going on.

00:29:22.067 --> 00:29:27.646
Yeah, and we really try to stay away from those types of buzzwords because we feel like they've been talked about for so long.

00:29:27.646 --> 00:29:29.851
Oh yes, Are they being realized on the floor?

00:29:29.851 --> 00:29:39.046
In most cases not, and we see great presentations with all this promise and then it's like but you kind of glossed over a part there that's actually really big and really complicated.

00:29:39.548 --> 00:29:49.670
Yeah, the implementation and how do you go line down to test this thing, which has been simulated, but you're maybe the first one to actually deploy it.

00:29:49.670 --> 00:30:13.452
That's the other part of the standardization process where the market is really pushing us at the moment to publish standards for single-payer Ethernet guidance, because some of the biggest movers in the industry are ready to move and that will drag the rest of the market, but they're not going to do it until they have specific guidelines to do what they want to do.

00:30:15.102 --> 00:30:23.115
And a lot of people have the hesitation because they want to see the big movers move before they start making changes on their plant floor.

00:30:24.040 --> 00:30:28.008
Is there anything you can recommend to us to stay on top of news in this area?

00:30:28.008 --> 00:30:31.173
Standards body is like what's going to be coming out what people?

00:30:31.173 --> 00:30:35.300
Can where you recommend they can like, if they want to be involved or just follow along.

00:30:35.300 --> 00:30:36.202
Sure kind of ask.

00:30:36.202 --> 00:30:37.384
This is evolving uh.

00:30:37.444 --> 00:30:46.570
So within odba they do a pretty good job of um like public uh news releases of what we're working on and what they're allowed to talk about.

00:30:46.570 --> 00:30:57.644
Uh, one of the most exciting things which ed and Gota touched on was that last year we did a marketing study of the market readiness for single-payer Ethernet and ODVA published that last October.

00:30:57.644 --> 00:31:19.490
It was very surprising the amount of people that are ready to adopt and deploy now and so, kind of leading the project that I lead within ODVA, I was like, okay, we need to move forward towards publication because the market is more ready to adopt in a faster timeframe than I was expecting, honestly.

00:31:19.490 --> 00:31:21.807
So ODVA is a good resource.

00:31:21.807 --> 00:31:25.988
Ieee is always a good resource with the publications that they put out.

00:31:27.901 --> 00:31:32.282
I'd say that Harding does a good job with our industrial Ethernet weeks of like this is what's coming.

00:31:32.282 --> 00:31:34.329
This is what we're working on within standardization.

00:31:34.329 --> 00:32:04.125
Just in the last few weeks there's been calls for interest within ODVA, profinet organization and advanced physical layer for more collaboration across the global standards groups to make sure that the one standard is being put out and is not directly in conflict with another standard that's being put out in Europe or you know just that we're not breaking anything along the way as we're publishing what we're doing.

00:32:04.606 --> 00:32:10.680
So it's a challenge because these are all volunteer-led organizations where you're doing that on top of your normal day-to-day job.

00:32:10.680 --> 00:32:12.546
And and now there's a challenge because these are all volunteer-led organizations where you're doing that on top of your normal day-to-day job.

00:32:12.546 --> 00:32:18.607
And now there's a lot of groups having the same conversations.

00:32:18.607 --> 00:32:22.733
But we have to do that to make sure that we're not.

00:32:23.234 --> 00:32:23.796
Check each other.

00:32:24.922 --> 00:32:35.638
Yeah, that we're not missing something, that we're not missing an entire subsegment of the market, like you said that you would come from, process automation, and that's a whole different application use case than industrial.

00:32:35.901 --> 00:32:41.230
Yeah, we do flow meters that have Ethernet, so I'm just thinking process stuff that everything could have.

00:32:41.230 --> 00:32:43.866
There's already two wires going to it.

00:32:44.440 --> 00:32:45.785
Explosion-proof applications.

00:32:45.785 --> 00:32:47.651
That was the APL project.

00:32:48.119 --> 00:33:17.301
They were the first to deploy single-pair Ethernet and it uses a completely different connector solution than what is general-purpose single-pair Ethernet, which is kind of like the working term of the projects that we're working on now, because it is going inside an explosion-proof cabinet, so they're just landing on a terminal block or they picked a m12a code for their application, but what we're working on within our working groups is completely different from that.

00:33:17.301 --> 00:33:20.190
But we have to make sure.

00:33:20.190 --> 00:33:21.674
Okay, is this going?

00:33:21.674 --> 00:33:35.374
Is this all going to connect up in the same switch, and on one side of the switch is general purpose spe and on the other side of the switch is apl, explosion proof applications or these two different networks that have to talk to each other?

00:33:35.374 --> 00:33:49.568
Like those are all the things where we're checking each other and cross collaborating.

00:33:49.568 --> 00:33:50.410
You know this is.

00:33:50.410 --> 00:33:52.611
You know we work with direct competitors.

00:33:52.611 --> 00:34:03.678
Automation companies that are historically direct competitors and never were really in the same room are directly working on this technology together, which I think is really promising.

00:34:06.381 --> 00:34:06.961
Yeah, that's been.

00:34:06.961 --> 00:34:16.610
We're part of an association for high-tech distribution, so distributors, and there are tons of competitors in that group.

00:34:16.610 --> 00:34:16.951
Sure.

00:34:18.262 --> 00:34:18.804
But it's growing.

00:34:18.804 --> 00:34:22.048
It's growing a lot and more and more people come to these conferences every year.

00:34:22.048 --> 00:34:29.338
So I think people are seeing kind of the benefit of yeah, you know what these are my competitors, but we all have certain things that we can actually work together on.

00:34:29.338 --> 00:34:32.262
You know what these are my competitors, but we all have certain things that we can actually work together on Sharing knowledge.

00:34:32.262 --> 00:34:33.768
You know best practices.

00:34:33.768 --> 00:34:39.766
Obviously, standards are something that just the industry in general has to happen, but the more we can collaborate on them, the better.

00:34:39.766 --> 00:35:00.422
And yeah, I'll just keep like my big soapbox is always like the pie is getting bigger for all of us and it's really the customer that needs to see the success of this and us inviting and or keeping things to ourselves and things like that.

00:35:00.442 --> 00:35:02.485
If it doesn't, it won't help the customer.

00:35:02.485 --> 00:35:03.367
It makes all of us look bad.

00:35:03.367 --> 00:35:09.262
Have you found that working in standards organizations has had a positive impact on your career?

00:35:09.262 --> 00:35:11.987
Does that feel like you've made personal connections or?

00:35:12.027 --> 00:35:16.875
it's added to your I don't know the enrichment of you actually doing your job, Because it's challenging, right?

00:35:16.875 --> 00:35:23.088
Like you said, it's a volunteer gig that you do on top of your normal job and now you run a business, right?

00:35:23.088 --> 00:35:32.050
Same thing with the podcasting we find it to be extremely rewarding, but it can get exhausting, sure, but for us, like, the pros heavily outweighed the cons.

00:35:32.050 --> 00:35:35.994
Would you say that participating in these types of standards organizations has been positive?

00:35:36.719 --> 00:35:48.735
Yeah, and I would say one of the largest reasons why is because I have professional working relationships with our direct competition now.

00:35:49.096 --> 00:35:49.416
That's cool.

00:35:50.583 --> 00:35:51.748
We're on first name basis.

00:35:51.748 --> 00:35:58.385
We have conversations about this technology inside the standards groups A lot of the times.

00:35:58.425 --> 00:36:40.045
we don't agree on everything, but we have built a bridge which I've never seen in my professional career of working with our direct competition, having personal and professional relationships with them where, like we know each other, we meet in person a few times a year, we meet virtually every week, um, and and that would have never happened before you know they we ask about like, oh, what did you do on this vacation that you recently went on, or some people were traveling to see the recent eclipse, and you kind of chop it up and have those conversations before the meeting gets started, and I've never seen that before.

00:36:40.045 --> 00:36:41.485
So it's pretty cool to see.

00:36:42.480 --> 00:36:47.007
It makes a huge difference to get to know people a little bit on a personal level, because at the end of the day, we're all people.

00:36:47.007 --> 00:36:59.166
We have to spend time with all these other people at work, and it's much better if you can get a little bit of joy out of it and feel like you're actually there, you know, for a common purpose or to help each other.

00:37:00.780 --> 00:37:18.514
Well, when you need to push and when you need to pull it makes it easier because you have a relationship with this person where they're not just going to completely shut the door every time because you're a competitor, like we work collaboratively and maybe not always in our own best interest but in the best interest of the industry and the technology.

00:37:18.514 --> 00:37:27.173
And because you have that relationship with them, you know they're able to like work with you more than I think that they otherwise would be.

00:37:28.141 --> 00:38:04.586
And I'm not a specifying engineer, but I am a buyer in some capacity now with my role and all other things being equal, somebody may have a great technology, but I personally want to know that there's some goodness behind the company or that their people are community-minded, or that you know and I see and hear that from a lot of my peers is they actually want to know a little bit about what your motivations and how you act in the world as an organization and like your people, in addition to just the technology, because there's so many choices now for type you can, you know, find anything.

00:38:04.586 --> 00:38:05.027
Sure.

00:38:05.380 --> 00:38:06.262
From a lot of places.

00:38:07.827 --> 00:38:08.789
That's sorry.

00:38:08.789 --> 00:38:11.047
No, go ahead the differentiators.

00:38:11.047 --> 00:38:14.378
I mean you want to like who you're working with or who you're buying from.

00:38:14.579 --> 00:38:14.699
Yeah.

00:38:14.840 --> 00:38:25.346
That could be the difference between buying from vendor A, who's a little cheaper, and vendor B, who actually seems to be a quality person, or about the world, or sustainability, whatever.

00:38:25.800 --> 00:38:32.184
That's just sales 101, right, you're going to go to the people that didn't make you mad or the people that give you the better feel?

00:38:32.204 --> 00:38:37.300
yep yeah, we talk a lot about uh, or we don't talk about it a lot.

00:38:37.300 --> 00:38:40.291
But you know like, oh, it's engineering, it's not about feelings.

00:38:40.291 --> 00:38:46.315
Uh, you may think that all you want in the front of your brain, but your feelings are still at play, no matter how.

00:38:46.315 --> 00:38:49.688
You know technical, you're, you're going with it.

00:38:49.688 --> 00:38:50.751
Yeah, absolutely.

00:38:52.704 --> 00:38:55.351
When I get a tech support call about one of our machinery.

00:38:55.351 --> 00:39:03.311
These days we've hired a full-time tech support person to handle those, but for a while in the early days I was handling myself and it is emotional.

00:39:04.039 --> 00:39:05.286
Absolutely, oh my God.

00:39:06.001 --> 00:39:18.139
They've had a machine for eight years and have never done scheduled maintenance on it, but then it goes down and they like literally call and are screaming at you and it's tough not to get emotional in that situation.

00:39:18.139 --> 00:39:20.365
But it's like, okay, let's just work the problem.

00:39:20.847 --> 00:39:21.769
This is your fault.

00:39:21.769 --> 00:39:22.190
Yeah, yeah.

00:39:22.190 --> 00:39:25.489
Let's just okay what is going on?

00:39:26.360 --> 00:39:28.065
What are your team viewer credentials?

00:39:28.126 --> 00:39:31.228
Let's start there, let me just remote in see what's going on.

00:39:32.719 --> 00:39:38.670
Yeah, I mean, we may not emote it, but it's always emotional.

00:39:39.873 --> 00:39:43.028
Absolutely, but that's how you produce a happy customer, I'm sure yeah.

00:39:44.760 --> 00:39:47.630
Yeah, so thank you so much for coming here and having this conversation with us.

00:39:47.630 --> 00:39:52.112
I mean, we love this actually just getting to know people on the podcast.

00:39:52.112 --> 00:39:58.809
You know we can have a whole hour to prepare ahead of time, but we just get to know each other and this is, I think, hopefully the first of many conversations.

00:40:01.420 --> 00:40:13.594
You know, we out of all the thousands and thousands of people here, the people that have this mindset, that they want to collaborate, that they want to, you know, share, uh, share knowledge and move our industry forward together.

00:40:13.594 --> 00:40:17.884
Um, those are the people that we end up like coming back to again and again.

00:40:17.884 --> 00:40:28.744
And so I, as this single pair, ethernet, rolls out more as the standards come out, I really look forward to you know, following it and seeing, now that I know some people that I can talk to about it.

00:40:28.744 --> 00:40:38.643
It's not just like, oh, view a webinar, yeah, like there's so many of those topics, and I'm like, yeah, there's so many innovations, and then I'm just going to forget them all because I don't care, I don't have a personal connection.

00:40:38.905 --> 00:40:39.909
Especially during COVID.

00:40:39.909 --> 00:40:45.702
It was like every week, everybody was scrambling to you know produce.

00:40:45.802 --> 00:40:47.224
Yeah, including us.

00:40:47.224 --> 00:41:00.951
This was even before our studio and we were just doing it in like one of our office spaces, but it very quickly, kind of washed over me of did come down to well, this is a person that I know so like I trust their opinion.

00:41:00.951 --> 00:41:19.929
I know that they're a subject matter expert, that they're going to, you know, do a deep dive and this isn't going to be like just a general session.

00:41:19.929 --> 00:41:24.291
So that's just challenge for all of us in like doing content.

00:41:24.291 --> 00:41:30.788
I'm sure you both probably know that better than myself, but yeah, it's all fun.

00:41:31.289 --> 00:41:35.550
We try to be transparent and one of the reasons why we do so many different formats of our content.

00:41:35.550 --> 00:41:38.369
Sometimes people are like what are you exactly?

00:41:38.369 --> 00:41:45.548
We're like, well, we're a podcast, but some of the conversations we want to have need show and tell, so we can't just do an audio recording like this.

00:41:45.548 --> 00:41:47.927
So we came up with this idea demo days.

00:41:47.927 --> 00:41:57.681
Sometimes I just want to see a new cool product and I'm not qualified to buy it right now and so like but can you just come give me a demo?

00:41:57.681 --> 00:42:00.208
Like can you do it on camera so that my friends can also see it?

00:42:00.208 --> 00:42:00.929
Or if.

00:42:01.070 --> 00:42:04.467
I want to like I thought it was super cool and I thought of someone that should have seen it.

00:42:04.467 --> 00:42:11.150
I can just send them the recording instead of now having to send them to you and you qualify them to spend another hour to show them the same thing that you just showed to me.

00:42:11.150 --> 00:42:16.184
But yeah, we call it demo so that people know if they're going to come watch it.

00:42:16.184 --> 00:42:17.947
It's a sales demo.

00:42:18.309 --> 00:42:25.210
It's not a podcast or a sales demo disguised as a podcast, or a sales pitch disguised as a webinar.

00:42:25.210 --> 00:42:27.034
Like, let's just be real.

00:42:27.034 --> 00:42:28.503
Sometimes people want the sales pitch.

00:42:28.503 --> 00:42:31.692
Let them know that it's a sales pitch and let them know that that's what they're in for.

00:42:32.221 --> 00:42:37.713
Or if you're going to have a deep dive discussion with the subject matter expert about applications, then let people know that ahead of time.

00:42:37.713 --> 00:42:51.293
You know we have so many imitations to so many things and I'm really tired of like the next big thing in Industry 4.0, come watch our webinar and I'm like how is it going to be different from the webinar I've been on for the past 10 years?

00:42:51.373 --> 00:42:51.795
Definitely.

00:42:52.880 --> 00:43:22.422
And on the CLN side, which is still all very much like a raw and learning experience for me, we've had the best performance by not doing anything that's like sales related, but to reaching out to either an existing or a potential customer and just saying send us a file and we will run it and we'll record it and we'll send you the result of like number one, how fast our machine is and number two, the quality of what it outputs, and that is miles ahead of anything else that we're doing.

00:43:22.461 --> 00:43:29.485
It's just like no, send us, like send us your worst file that you have a problem with, and like let us run it and provide the results to you.

00:43:29.485 --> 00:43:35.606
And I mean, you know, sometimes out of the gate it doesn't come out well and it takes like massaging on our side.

00:43:35.606 --> 00:43:48.672
And then it's a learning experience of like okay, we found out that we had to edit your file in like X, y, z ways and now it runs well, and so like here's a immediate solution for you, and then keep us in mind in the future.

00:43:48.672 --> 00:43:51.706
And you know that's just what's worked for us.

00:43:51.706 --> 00:43:51.969
So far.

00:43:51.989 --> 00:43:54.800
I think we've all been a little jaded by all kinds of advertising over.

00:43:54.800 --> 00:44:04.268
You know so long of things that are shiny, that are really great, but the devil's in the details, sure, and then we try it and then we fail or whatever.

00:44:04.268 --> 00:44:12.992
It doesn't live up to its hype, like I would rather see you like tell me your flaws ahead of time, show me the demo, and I know something's going to go wrong.

00:44:12.992 --> 00:44:19.320
But at least I know you're doing it live and not giving me something pre-canned that's so perfect that I would never be able to actually replicate that.

00:44:19.320 --> 00:44:30.811
Because we all know real life always comes with challenges, right as somebody that's been in the field, like actually starting up machines, the seamless is that a?

00:44:30.811 --> 00:44:31.932
Favorite of yours.

00:44:32.072 --> 00:44:33.514
Oh man, Seamless integration.

00:44:34.940 --> 00:44:36.025
Anybody that actually does it.

00:44:36.025 --> 00:44:38.909
You kind of feel slapped in the face with that.

00:44:38.909 --> 00:44:45.708
So, for us, embrace the fact that things are imperfect and you can earn your stripes and respect actually.

00:44:45.708 --> 00:44:46.009
Sure.

00:44:46.219 --> 00:44:47.967
Because people that really have been around the block.

00:44:47.967 --> 00:45:00.628
They don't want your shiny sales pitch, they want how is this actually going to work for me, and the braver you are in trying to give that a legit try and give them personalized answers.

00:45:00.628 --> 00:45:07.074
I think, yeah, we earn respect that way, oftentimes through our failures, in fact.

00:45:07.074 --> 00:45:15.125
And how do we deal with challenges versus just having the coolest thing and it's easy to market but it's hard to follow up and practice?

00:45:15.125 --> 00:45:21.949
Yeah, absolutely Well, like I said, I think I tried to wrap this up once before, but I would probably keep talking about this for another hour.

00:45:22.521 --> 00:45:24.166
Ed, anything that you want to add before we?

00:45:24.646 --> 00:45:25.068
sign off.

00:45:25.068 --> 00:45:25.771
No, I'm good, let's go.

00:45:26.199 --> 00:45:26.481
Cool.

00:45:26.481 --> 00:45:28.125
Well, yeah, thanks everybody.

00:45:28.125 --> 00:45:30.811
We'll be up for doing a few more recordings today.

00:45:30.811 --> 00:45:36.293
I know this is not going to come out live because A this show is crazy and we can't even stream stuff.

00:45:36.293 --> 00:45:37.485
The internet here is so bad.

00:45:37.485 --> 00:45:45.634
Yeah, but if you're catching this and you didn't come to Automate this year, we will be back at every Automate, I'm sure, for years to come.

00:45:45.634 --> 00:45:53.246
And then there will also be Ethernet Week what was it?

00:45:53.266 --> 00:45:54.329
Industrial Ethernet Week.

00:45:54.329 --> 00:45:54.791
That Harding does.

00:45:54.791 --> 00:45:55.494
That's a virtual event, correct?

00:45:55.494 --> 00:45:59.106
Yeah, it was a few months ago and we do a few different flavors of that across the year.

00:45:59.106 --> 00:46:06.621
It won't be called Industrial Ethernet Week, but single-pair Ethernet and all of our Ethernet solutions are included in multiple events throughout the year.

00:46:06.942 --> 00:46:09.827
Okay, well, we'll be continuing these conversations and thank you very much.

00:46:10.148 --> 00:46:10.929
Thank you, thank you.