Collaborative Innovation, AI, & Cultural Dynamics w/ Dylan DuFresne

WEBVTT

00:00:00.020 --> 00:00:00.381
Cool.

00:00:00.381 --> 00:00:05.331
Okay, it is the day before Thanksgiving, wednesday, november 27th.

00:00:05.331 --> 00:00:22.585
This is a pre-recorded episode and I actually, dylan, I'm not sure if it's going to go out in this season or if we're going to have to wait to publish it next season, but I'm really glad we caught you before a barrage of end of year on-site projects and stuff.

00:00:22.585 --> 00:00:29.931
I know that your schedule was pretty full for the rest of the year, yeah, so I guess I should back up and say welcome to another episode of Automation.

00:00:29.931 --> 00:00:31.585
Ladies Folks, thank you for listening.

00:00:32.380 --> 00:00:50.185
And we have, myself and Allie, today with our guest, dylan Dufresne, which we have tried a couple of times to get on and we ended up having to reschedule because Allie couldn't make it last time and Dylan and I ended up talking for the whole hour anyway without recording anything.

00:00:50.185 --> 00:01:08.989
So to officially get this conversation out in front of our audience and to get them to let you know, get to know you a little bit better, dylan, I guess I'll go ahead and ask our first question, and that is can you tell us a little bit about yourself and how you got to be doing what you're doing right now in the automation space?

00:01:09.400 --> 00:01:13.266
Yeah, I guess I could talk for hours on that part, so we'll keep it short on that.

00:01:13.266 --> 00:01:27.614
But a lot of it happened just kind of by accident and where I ended up Started off in a tech school, relatively local, kind of an easy option and good place.

00:01:28.421 --> 00:01:30.424
I was I was stalking you.

00:01:30.424 --> 00:01:34.731
How did you find a mechatronics program?

00:01:34.731 --> 00:01:39.328
And then I know now that you're just like really like software heavy.

00:01:39.328 --> 00:01:43.540
How did you like were you maybe a computer guy before that?

00:01:43.540 --> 00:01:48.513
Like, how did you get so deep into the software when you started in a mechatronics program?

00:01:48.513 --> 00:01:53.427
And how did you find the mechatronics program, Start with that and then go to the other one?

00:01:53.849 --> 00:02:18.713
Yeah, so the funny thing with the robotics program is the school that I went to is a pretty well-known regional one, not like a big name in the country, but well-known with a lot of the local companies, and I fell into it because my grandparents lived in town and I didn't have to pay rent for the first year they had a robot program and robots sounded cool.

00:02:19.580 --> 00:02:25.324
I was on the robotics team in high school, did a little bit of CAD and stuff like that, but nothing like real industry type stuff.

00:02:25.324 --> 00:02:27.629
And one thing led to another.

00:02:27.629 --> 00:02:30.502
We went through the program and when is this?

00:02:30.502 --> 00:02:30.842
This is in.

00:02:30.862 --> 00:02:31.346
Minnesota.

00:02:31.860 --> 00:02:32.862
Yeah, this is in Minnesota.

00:02:32.862 --> 00:02:42.862
Yeah, yeah, One thing led to another got the first job there working as a service tech, started out with an internship and got a job there for a OEM making packaging machines.

00:02:42.862 --> 00:02:46.491
While I was there we did a lot of everything.

00:02:46.491 --> 00:02:55.407
They kind of bounced me around department to department so I worked with the mechanical assembly guys, the electrical assembly panel shop.

00:02:55.407 --> 00:03:06.405
I worked with the controls engineers, the electrical designers, startups and troubleshooting calls, things like that for about a year, Ended up getting laid off from that job.

00:03:06.405 --> 00:03:16.171
That's always fun, oh yeah, especially right out of school, and I did the dumb thing and just bought my first real car and it was a fun time.

00:03:16.171 --> 00:03:20.568
It didn't last long, Turns out it was an in-demand skill set.

00:03:20.568 --> 00:03:26.000
So about a month after I got laid off I think I had like six or seven job offers.

00:03:26.000 --> 00:03:29.146
In that time it wasn't like uh that's a sell.

00:03:29.227 --> 00:03:40.655
That's a sell for us, yeah and ended up getting a job as an electrical drafter with a electrical contractor so still not really software.

00:03:40.655 --> 00:03:52.812
Um, ended up going and started to do, just because that came up, started doing some controls projects with them, got into one really, really big one way in over my head, sweet um.

00:03:52.812 --> 00:04:06.674
It was probably 50 or 60 different pieces of equipment we were controlling I think it was 15 and a whole grain elevator into feed mill situation pl PLC, scada project and that was a good start for your project.

00:04:06.693 --> 00:04:07.534
A bunch of cabinets.

00:04:08.040 --> 00:04:09.860
All MCC, yep, nice.

00:04:09.860 --> 00:04:14.331
So we had one panel and a bunch of MCC sections, a bunch of VFDs and feeder screws.

00:04:14.331 --> 00:04:23.387
We had a 400-horse VFD control and hammer mill so that we could ramp it up and take care of the inrush current a little bit and then rotate the direction every time you started it up.

00:04:23.387 --> 00:04:30.394
It was a lot for the first project.

00:04:30.394 --> 00:04:35.317
We'll put it that way To this point I had only troubleshot ladder logic, I had never done anything real in a PLC.

00:04:35.317 --> 00:04:35.980
Yet, baller, that's how you learn.

00:04:36.701 --> 00:04:37.322
By fire.

00:04:38.307 --> 00:04:44.060
Oh yeah, that project also, ironically, was the first time I had heard of Ignition.

00:04:44.060 --> 00:04:52.574
It was a Rockwell PLC at Ignition and that was my introduction to the industry, early days of Ignition.

00:04:52.574 --> 00:05:00.093
And then from there the controls team that did exist all ended up quitting or getting fired.

00:05:00.093 --> 00:05:08.975
So then for a while there it was just me and I was taking care of all the service calls and everything across the pretty much across the Midwest.

00:05:08.975 --> 00:05:23.209
So one day I'd be in pretty much South Dakota and the next day I'd be on the other side of Wisconsin and the next day after that I'd be somewhere in Iowa doing a service call, or Nebraska and just bouncing around driving all over the Midwest.

00:05:23.740 --> 00:05:25.627
Would you notice that when we would like?

00:05:25.627 --> 00:05:36.663
When you go out to dinner, right, you see, like other people that are completely by themselves and you're just like I don't know, you like nod at them because you're like, you're here in business and you don't know anyone, do you?

00:05:36.663 --> 00:05:43.747
It's really easy to spot those people because you are them oh, yeah, definitely and yeah.

00:05:43.766 --> 00:05:53.889
So through that troubleshooting I definitely learned a lot, but that was again still mostly PLCs, HMIs, some SCADA stuff and a lot of instrumentation and working very closely with electricians.

00:05:53.889 --> 00:05:58.860
So a lot of focus on the install side as well, but learning everything I mean.

00:05:58.860 --> 00:05:59.925
There was one project we did.

00:05:59.925 --> 00:06:07.312
It was a pretty small project, adding a bin to a grain site, and the owner said, hey, we got this job, Go do it, Figure it out.

00:06:07.312 --> 00:06:10.206
And my first question was all right, what's Profibus?

00:06:10.206 --> 00:06:17.086
And his response was you'll figure it out, Gave me the keys to the truck and sent me on my way.

00:06:17.086 --> 00:06:17.949
Fantastic.

00:06:19.721 --> 00:06:20.603
And you did, didn't you?

00:06:20.603 --> 00:06:21.848
Oh yeah, I did.

00:06:26.007 --> 00:06:27.879
I don't know how I did it at the time, but I always figured it out one way or another.

00:06:28.360 --> 00:06:31.144
That's what I love about this job and then, yeah, that company.

00:06:31.185 --> 00:06:43.560
It grew from that where I think I could be wrong on my numbers, but when I started there there was less than 30 employees for sure, and then when I left that company about eight years later, there was almost 300.

00:06:43.560 --> 00:06:44.992
So then I got through the entire phase of that integrator.

00:06:44.992 --> 00:06:46.276
About eight years later there was almost 300.

00:06:46.276 --> 00:06:47.437
So then I got through the entire phase of that integrator.

00:06:47.437 --> 00:06:47.617
That was.

00:06:47.617 --> 00:06:51.706
Their primary business was electrical services, power services, things like that, some solar work and all that.

00:06:51.706 --> 00:06:59.492
And then we had the integrator within that and, yeah, so I learned a lot watching that company grow from the inside, seeing how things worked.

00:06:59.492 --> 00:07:14.033
I mean, I went from the drafter who got thrown on a PLC project to, by the time I was done, I was the manager of the entire engineering team and saw that along the way, made my own mistakes along the way and learned a lot on that side.

00:07:14.033 --> 00:07:19.379
And over the time there, the different projects we were on, we got more and more into SCADA.

00:07:19.581 --> 00:07:22.670
I accidentally fell into MES just because that was customer request.

00:07:22.670 --> 00:07:29.492
I didn't know the word for it until we were already done with the project, but they just asked, hey, can we track this.

00:07:29.492 --> 00:07:30.300
Can we log that?

00:07:30.300 --> 00:07:35.382
Let's put a database in for this and we need to be able to track this stuff and schedule work orders and all that.

00:07:35.382 --> 00:07:42.408
And then, a few months after that project, I learned what MES was and I'm like, oh, I've already done this, that's hilarious.

00:07:42.509 --> 00:07:48.122
All at MES in their industry Yep, um, that's hilarious.

00:07:48.122 --> 00:07:49.285
All at mes in their industry yep, um.

00:07:49.285 --> 00:08:05.305
And yeah, so through all that, I mean I pretty much got everything from hands in panels installing sensors and troubleshooting the installation all the way through all the starting to get into the software and the mes side of things and pretty much every layer of the stack through there, integrating with the erp systems and as the company grew.

00:08:05.305 --> 00:08:06.269
Those are the jobs we got.

00:08:06.269 --> 00:08:16.947
So I just kind of went where the work did and learned what I needed to to keep up and then managing the team and all that was a whole different story, a whole other skill set to learn.

00:08:16.947 --> 00:08:25.875
And yeah, but along the way, the big one for me was where I really enjoyed it was the software side.

00:08:25.875 --> 00:08:34.150
That's where I was interacting more with people and not just sitting by myself in a control room, and for me personally that was kind of what I enjoyed more than anything.

00:08:38.780 --> 00:08:39.403
The police.

00:08:41.047 --> 00:08:43.272
They'll pass, you'll be able to hear me again, yeah.

00:08:43.272 --> 00:08:54.806
So through all those different types of projects I kind of learned what I enjoyed, more I got I'm still probably I'm still really good with and I just can't seem to get away from the plc side of stuff.

00:08:54.806 --> 00:09:08.587
But I really enjoy the software and the people aspect of it really more so than any of that, and being on the software side and almost even to a point of more like consulting work and things like that.

00:09:08.587 --> 00:09:11.333
That's where I really kind of found my enjoyment.

00:09:11.333 --> 00:09:17.629
So the last couple of years has been spent really trying to find that niche and figure out what I want to do going forward.

00:09:20.855 --> 00:09:25.530
Very cool very cool.

00:09:25.551 --> 00:09:36.363
So, yeah, I mean I could go round and round at a lot of this, but I don't know if you've got more questions or ali, I'm gonna give you the opportunity to ask follow-up questions, otherwise I'll dive in.

00:09:36.884 --> 00:09:45.841
But I I like tried to take a screenshot just now and I did something funny with my computer, where everything is dark relatively dark I can still see it, except for your face.

00:09:45.841 --> 00:09:52.020
Dylan is nice and bright, but, like when I change my screens, that that little rectangle stays.

00:09:52.020 --> 00:10:05.591
So I'm in this stage of my life right now where I'm seem to be in between being good at anything, including this, um, but aside from from those distractions, uh, I'm I'm curious.

00:10:05.591 --> 00:10:07.554
Well, ali, what do you?

00:10:07.554 --> 00:10:08.964
Do you have any follow-ups to that, or do you want me?

00:10:08.984 --> 00:10:11.350
to um, yeah, like how how did covid go?

00:10:13.844 --> 00:10:15.626
for us it was probably our busiest season.

00:10:15.626 --> 00:10:21.043
Interesting, um, it might have been the phase of growth in the company.

00:10:21.043 --> 00:10:24.461
It might have been more work coming in because things were kind of shut down otherwise.

00:10:24.461 --> 00:10:29.365
But I mean again, our primary business was electrical contractors were you traveling during that time?

00:10:29.365 --> 00:10:44.929
Oh yeah, I spent pretty much the entire winter of I believe it was 2020 in arizona, back and forth, and I think I flew more during covid than I have before or since interesting like reverse oh yeah, are you tired of traveling?

00:10:46.091 --> 00:10:47.575
uh, sometimes it comes in waves.

00:10:47.575 --> 00:10:51.428
If I don't travel too long, I want to travel again.

00:10:51.428 --> 00:10:52.952
If I travel too long, I want to be home.

00:10:53.360 --> 00:11:03.807
It's hard to find that balance, but do you think it has something to do with the nature of the work, the fact that a lot of us, I think that are drawn to it like need that variety somehow?

00:11:04.469 --> 00:11:10.543
I think so the people, people, um.

00:11:10.764 --> 00:11:14.931
So so when did you first like get into anything with erp?

00:11:14.931 --> 00:11:17.455
So it looks like mes.

00:11:17.495 --> 00:11:34.447
It's like you went from skater into mes on accident and then yeah so erp was kind of part of that accidental mes piece where we were interfacing with, like recipe systems and reporting actual run reports and things like that back into the ERP system.

00:11:34.447 --> 00:11:55.193
So we would have a couple of different side ones, some big, real ERP systems, and at the time most of it was a file transfer, some legacy system where we didn't really have good access to stuff, but some of it was like custom homebrewed Microsoft access systems that they called their ERP functions and various types of them.

00:11:55.193 --> 00:12:00.490
But it was always kind of feature requests where we want to do this and we'd figure out how to do it.

00:12:03.014 --> 00:12:09.100
Yeah, how to do it.

00:12:09.100 --> 00:12:11.067
Um, yeah, it's really cool that you, that you like started your career kind of with the electricians.

00:12:11.067 --> 00:12:17.610
Um, because I was going to ask you, like on the people side, like, have you seen, you know, implementations of you?

00:12:17.610 --> 00:12:33.341
Know, I guess industry 4.0 or digital transformation go wrong because nobody cares about you, the people that they're pushing it onto, that have to make it successful to go like to move on or to like, yeah, after the implementation.

00:12:35.125 --> 00:12:35.787
Yeah, definitely.

00:12:35.787 --> 00:12:39.721
I mean it's all, at the end of the day, it's there to make things easier for people.

00:12:39.721 --> 00:12:50.163
I mean easier for everybody, and if they're not thinking about everybody it doesn't really work very well Most of the time.

00:12:50.163 --> 00:12:56.279
What I've worked on has begun pretty well, but that's also because I've been embedded on the plant floor from day one.

00:12:56.279 --> 00:13:08.360
I mean there's projects where I'll be quoting it with the owner of a local company and then I'll be doing the project on the floor with the maintenance team owner of a local company and then I'll be doing the project on the floor with the maintenance team.

00:13:08.360 --> 00:13:10.461
So it's kind of it's.

00:13:10.461 --> 00:13:11.245
It's it's kind of skewed.

00:13:11.245 --> 00:13:23.164
My perspective there Cause that's kind of what I've seen more than not, is the smaller companies and the more integrated approach where the people who are running the business still day-to-day interact with the people, and there's those smaller businesses that really have that luxury afforded to them.

00:13:24.506 --> 00:13:29.174
Yeah, because the ones that are really kicking butt are like the Amazons of the world and Teslas.

00:13:29.174 --> 00:13:33.903
But you say you've worked with smaller companies Like can you talk to?

00:13:33.903 --> 00:13:45.489
Like how do you, can you encourage, I guess, small companies to like get into this, get into this connecting all of your systems, and then what are?

00:13:45.489 --> 00:14:01.090
You know, what are steps you can take so you don't have to like take it all at once, because I think that's what these companies are afraid of and they're just happy to, you know, be at the size that they're at, but you know it will come down to competition eventually.

00:14:01.871 --> 00:14:04.171
Right, and I think the big one there is.

00:14:04.171 --> 00:14:08.868
The small companies are actually at a luxury there because it's a lot easier to start small when you're already small.

00:14:08.868 --> 00:14:12.683
Oh, and it's didn't think about that.

00:14:12.683 --> 00:14:15.735
Everything's dependent on existing systems too.

00:14:15.735 --> 00:14:26.659
But it's also a lot easier if you have one brownfield site versus 100 or 200 or a thousand, and so there's always the difference between brownfield and greenfield.

00:14:26.659 --> 00:14:32.284
Most of the stuff's going to be brownfield and you don't want to rip and replace things that are already working more often than not.

00:14:32.284 --> 00:14:43.567
But if we're talking more theoretical, we're just going to get started and some of the more greenfield type stuff it's easy enough just to throw in a single ignition gateway or something and just get started with that.

00:14:44.370 --> 00:15:11.035
Um, one of the some of the projects we do I mean it's very much you hear a little bit about that land and expand model and one of the projects we're doing recently is we came in to quote a process system mostly just pumps and valves transferring between tanks and fill lines and things like that, and we came in as just the PLC and the HMI of this project.

00:15:12.081 --> 00:15:25.548
We were able to work with the customer and to get the HMI ended up being ignition in this scenario, which opened the door for a lot of other stuff, and then throwing in a little bit of data logging features and event logs and things like that.

00:15:25.548 --> 00:15:33.951
So they had a very data-centric HMI that was logging events and data that otherwise really wouldn't have been possible with some of the more traditional HMI platforms.

00:15:33.951 --> 00:15:40.582
Then, through that, I mean at the beginning of the project, they said you can use Ignition but you can't call it a SCADA system.

00:15:40.582 --> 00:15:41.485
We're not ready for that.

00:15:41.485 --> 00:15:53.645
And then, by by now closer to the end of the project, they're looking for ms systems, they're looking for some data collection and enterprise wide kpis and things like that.

00:15:53.645 --> 00:16:01.826
So a lot of it is just showing them what's possible early on, and it doesn't have to be big very cool.

00:16:05.890 --> 00:16:17.849
I like that a lot because, like you said, you know existing companies, like especially the small ones, right, they always like don't have budget right and maybe not always, like some companies in certain niches are, you know, very profitable.

00:16:17.869 --> 00:16:29.014
But I'd say they the average manufacturing operation, right, they don't have, you know, slushy budgets and they have a lot of things to consider ongoing maintenance, just keeping their operation going right.

00:16:29.033 --> 00:16:36.094
So it can be hard to A fit in the time, b find the right partner and then C, like actually overhaul anything.

00:16:36.094 --> 00:16:50.402
So I think, just from you know my perspective and the things that I've built in the past, it makes a lot of sense to try to or to be able to like start small, like that, right.

00:16:50.402 --> 00:16:54.152
And so you mentioned that, yeah, you came in and you called it the HMI, but you guys threw in some some data logging and stuff.

00:16:54.152 --> 00:17:07.972
Was that just on your prerogative, wanting to be like, hey, we want to show this customer that there's more here, and so you kind of add that to the project, or do you try to get them to agree up front that, hey, we should add this, we should like and I know the way that I would do.

00:17:07.972 --> 00:17:12.585
It would just be like slightly put it in there and be like look, how cool this is, here's something that you can do.

00:17:12.585 --> 00:17:14.406
But like, how do you approach that conversation?

00:17:14.960 --> 00:17:21.770
Well, part of it is just our base standards, and a lot of that comes down to yes, we want to show them what's possible.

00:17:21.770 --> 00:17:25.604
Yes, we want to show them what's possible, and that is part of it.

00:17:25.604 --> 00:17:26.164
That's probably half of it.

00:17:26.164 --> 00:17:28.369
But you also a project like this, you also can't lose.

00:17:28.369 --> 00:17:36.680
I mean, as an integrator, you've still got to make your own money too, You've got to keep your doors open and your employees paid, so you can't give away everything for free, especially as a small integrator.

00:17:36.680 --> 00:17:43.929
Some of the bigger ones they might be able to afford to just do the whole $100,000 project to start with and prove it and then get paid later.

00:17:43.929 --> 00:17:46.211
The smaller ones, like us, we really can't afford that.

00:17:46.211 --> 00:18:00.221
So we got to find ways of getting the little bits we can in and then working with the people and the culture to really kind of prove what's possible and shift that and the other piece the other half of that puzzle really is too, though it makes our job that much easier.

00:18:00.923 --> 00:18:01.222
Yeah.

00:18:01.483 --> 00:18:17.351
I mean, one thing I learned very early on in my career is if I start logging who's pressing buttons and if I have trend logs and things like that, I get the call that says, hey, something happened at 2 am, we don't know what, and then we can figure out what.

00:18:17.391 --> 00:18:22.311
We're not sitting there waiting to do it, we're not, and so a lot of it just comes into various practices.

00:18:22.311 --> 00:18:30.105
We have that keep make troubleshooting easier, make commissioning easier, validation easier, and so, yeah, 50%.

00:18:30.105 --> 00:18:31.810
We definitely want to show them what's possible.

00:18:31.810 --> 00:18:48.219
But the project actually gets exponentially more expensive when we don't have these tools, because they also help our efficiencies as an integrator, which definitely helps that balance of how can we afford to give these things away, to show the art of the possible, and all that without having that budget.

00:18:48.219 --> 00:18:59.141
Because we're a small integrator, we use those same tools to increase our own efficiencies and that makes the projects on our side that much more effective as well, which kind of hits both sides and everybody's happy.

00:18:59.141 --> 00:19:06.153
And if they don't want it, we can delete the database when we're done commissioning it, but we're still going to use it as our own tool, just like we want a meter or anything else.

00:19:11.267 --> 00:19:13.055
Right, right, yeah, okay, that's really smart.

00:19:16.701 --> 00:19:20.606
Let's talk about the magic of Ignition, because I thought Ignition for the longest time.

00:19:20.606 --> 00:19:26.135
I just thought it was like a really cool um skater platform.

00:19:26.135 --> 00:19:36.252
And it is not a skater platform, it is a iiot like mega giant um and it can do so much more than I ever thought.

00:19:36.252 --> 00:19:58.924
But, um, kind of, maybe, since you like saw it like back when it was, you know, growing, can you talk about, like, how much more it is than a skater system and what, and like uh, how easy it is, and like what, what the other, because I've heard of other platforms, like perspective, and like I'm not even sure you know the difference, uh, but I know there's like a lot more computer programming on that side.

00:19:58.924 --> 00:20:03.902
But yeah, like, yeah, can you talk on that point of, like the magic disney world of ignition?

00:20:04.782 --> 00:20:05.723
Yeah.

00:20:05.723 --> 00:20:10.388
So at the risk of sounding like a salesperson here, but it is from my experience I do believe it.

00:20:10.388 --> 00:20:35.886
So the big thing for ignition for me is if you strip away all the other features, if you strip away every module and function, what you get in that first core module for it's like 1100 bucks or something I have to look at their website again for sure but even headless just that core module and nothing else, gives you the ability to connect to a plc of almost any type and brand.

00:20:35.886 --> 00:20:41.803
Amazing, uh, use the udts and scripting to do a lot with that.

00:20:41.803 --> 00:20:43.444
I mean even headless.

00:20:43.444 --> 00:20:53.007
At that base price you can connect a SQL database, a Rockwell PLC, and start logging data in ways that are kind of hard.

00:20:53.007 --> 00:20:53.429
Otherwise.

00:20:53.429 --> 00:20:59.767
You can accomplish a lot of that at that small level with stuff like Node-RED and that too, but then that doesn't scale very well.

00:20:59.767 --> 00:21:03.540
So then you're ripping out the work you already did rather than building upon it.

00:21:03.540 --> 00:21:12.111
So when we can start with even just that base headless ignition, it gives us that platform to start collecting that data and then you can add on, like the web dev module.

00:21:12.111 --> 00:21:15.055
Now we've got an API, we can use something else to visualize it.

00:21:15.055 --> 00:21:16.236
Still for relatively cheap.

00:21:16.236 --> 00:21:18.482
You can start adding MQTT.

00:21:18.482 --> 00:21:33.587
We can publish that to a broker and now we've got these data models published to a broker with the API and we don't have any visualization in Ignition yet.

00:21:33.587 --> 00:21:35.733
But we're doing all the back end, all the data modeling and connecting to the edge devices.

00:21:35.733 --> 00:21:38.339
And the big one is there too we can contextualize edge devices.

00:21:38.339 --> 00:21:57.865
Maybe we've got a bunch of sensors that are all Modbus, tcp that aren't really part of control but they're part of how we're monitoring the environment and we've got a Rockwell PLC in one corner and maybe a Siemens PLC in the next and we can connect all three of those seamlessly, build up UDTs and structure that data and then from there we can share that data with the rest of the world.

00:21:57.865 --> 00:22:02.464
And we haven't even gotten to anything that's remotely HMI or SCADA yet.

00:22:02.885 --> 00:22:12.000
I mean, once you start adding, in the past you in the early days it was just the vision module, which was a more traditional SCADA.

00:22:12.000 --> 00:22:15.633
It was all a Java based drag and drop screens.

00:22:15.633 --> 00:22:17.961
You bind properties and it's very traditional SCADA.

00:22:17.961 --> 00:22:29.813
It's just a lot easier to work with than most of them and I have worked with most of them here to work with than most of them and I have worked with most of them, um, and so from there, it was just the easiest gator to work with.

00:22:29.813 --> 00:22:32.221
It was both the cheapest, the easiest and allowed us to deliver the best results.

00:22:32.221 --> 00:22:44.749
And this was back in 2015, 2016 probably as mature as it is um and then over the years they added more functions, more, more features, things like that.

00:22:44.749 --> 00:22:46.232
Yeah, there were some bugs to work out.

00:22:46.232 --> 00:22:53.606
As they grew, their support kind of came and went, sometimes as their company too, and I'm sure they were growing pains on that side.

00:22:53.606 --> 00:22:55.287
And that's all resolved now, which is awesome.

00:22:56.320 --> 00:22:58.789
And over the years, now we've got the Perspective module.

00:22:58.789 --> 00:23:00.586
The MQTT stuff's gotten even bigger.

00:23:00.586 --> 00:23:09.207
The industry is really looking for more of this and Perspective is much more of your web development type side of things.

00:23:09.207 --> 00:23:15.147
So it's kind of a you could use it for SCADA and I think they would tell you to.

00:23:15.147 --> 00:23:36.885
But my personal preference to this day is, if I'm doing an HMI and maybe a SCADA system I'm Envision If it's a SCADA system that's more on the MES or IOT side, then I might use Perspective and a lot of your big applications use both for different purposes, maybe even on different gateways, as we keep scaling up and up, and Perspective is more of a web-based interface.

00:23:36.885 --> 00:23:43.750
It's kind of a drag and drop way to make web pages with those same tags that we built in that first version when we first got started.

00:23:45.916 --> 00:23:55.663
That's not to mention the so more for mes and erp for my personal experience, I would say yes, but that's also changing as that platform is getting more mature as well.

00:23:55.663 --> 00:24:05.900
So watching this a year or two from now, this could all be different yeah, how do you see um ai helping the systems integrators?

00:24:07.865 --> 00:24:16.074
I think because it's being used for everything, but like yeah, let's start with like, where different pieces it can be used yeah, there's a lot of things we can do with ai.

00:24:16.675 --> 00:24:20.505
I think there's a lot of steps before we should really get to that conversation.

00:24:20.505 --> 00:24:31.286
As most integrators, um, if you don't have the support and the culture and the attitude and the technology and the data already in place, it's not going to do that much for you.

00:24:31.286 --> 00:24:55.726
I mean, even before AI was on this train, I went down the AI rabbit hole a little bit and pulled back, but I'm much more a proponent of let's get some better practices and standards, let's make more reusable code, let's write more code generation without AI, let's get things repeatable and reusable, and then we can start talking about how AI is going to help and stuff too.

00:24:55.726 --> 00:25:01.467
I mean, I really do like it, for I mean, it's really nice to help comment code things like that.

00:25:01.467 --> 00:25:11.486
I use it almost every day, but I also as much as I think it's a really, really great benefit to the industry, I also think it's pretty overhyped as well.

00:25:15.315 --> 00:25:15.635
Yeah.

00:25:15.635 --> 00:25:39.053
I will say, my recent experience with Copilot has left me very underwhelmed, has left me very, uh, underwhelmed back where I was about a year ago thinking like, yeah, this sounds kind of cool, but honestly, these like the real value add for me, for me is very low.

00:25:39.053 --> 00:26:00.519
Um, and unfortunately, I was thinking that a ai tool built into a tool suite would be more effective than something like a generic, like a chat gpt maybe it will be one day, because it's inside the application and should be then tailored to be useful to the use cases of that application.

00:26:01.340 --> 00:26:16.046
Um, but I've kind of found it to be the exact opposite, like it's less capable than a generic tool and the fact that it's tied to the application for a suite that has multiple different tools and they don't talk to each other and there's no like recognition between them.

00:26:16.046 --> 00:26:33.463
Um, so I can only imagine, like not having touched any of the co-pilots inside any kind of engineering tools, that they would be equally limited at this point to like very, very small use cases, like you say, maybe the note annotating, or for us it's like meeting notes.

00:26:33.463 --> 00:26:40.640
But even then I can't even tell Copilot in what format I normally like my meeting notes, like in ChatGPT.

00:26:40.640 --> 00:26:51.038
It can remember, I can say, hey, I like my meeting notes formatted this way, and it will remember that Copilot was like oh, I have no memory there is a.

00:26:51.340 --> 00:26:52.223
We want to do it all.

00:26:52.223 --> 00:26:54.659
Do you want me to summarize this email for you?

00:26:54.659 --> 00:26:57.385
I'm like no, the email is already two, two sentences long.

00:26:57.426 --> 00:27:06.801
Like I don't need a summary of this email there is an important distinction too between general ai, just as a conversation and topic, and llms, which is what we're talking about with like copilot and chat gpt.

00:27:06.801 --> 00:27:08.186
Yeah yeah, there's a whole lot of different specific implementations.

00:27:08.186 --> 00:27:10.575
Well then, just as a conversation and a topic, and LLMs, which is what we're talking about with like Copilot and ChatGP.

00:27:11.217 --> 00:27:14.005
Yeah, there's a whole lot of different specific implementations.

00:27:14.175 --> 00:27:17.241
Well then, what's machine learning All over this AI umbrella.

00:27:17.875 --> 00:27:25.922
Yeah, and there's I'm not going to repeat one here because I'll probably be wrong because I've seen 20 different versions of definitions of the difference between AI and ML.

00:27:25.922 --> 00:27:31.067
But there is the AI side and the machine learning side.

00:27:31.067 --> 00:27:38.701
I mean it doesn't have to be these big chat, gpt, llm type models, it doesn't have to be these big diffusions and things like that.

00:27:38.701 --> 00:27:39.284
It's just.

00:27:39.284 --> 00:27:42.800
I mean a simple forecast algorithm can do a lot of good for somebody.

00:27:42.800 --> 00:27:47.440
A simple search algorithm on a data set can do a lot.

00:27:47.440 --> 00:27:51.144
I mean you could do before we start talking about all the LLMs and stuff.

00:27:51.144 --> 00:27:57.247
I see there a lot of benefit with what the software world would consider traditional and old school.

00:27:57.247 --> 00:28:04.781
But what can we do with graphs and search algorithms and stuff before we even really talk about LLMs and all that?

00:28:06.365 --> 00:28:30.467
And there's a lot of them what's been traditionally called like operations research, that they use a lot of machine learning, um, in, yeah, statistical modeling and things like that, right, uh, and distributions like I think this is my uneducated or or out of date opinion of when I used to like play more in that space.

00:28:31.111 --> 00:28:51.897
But most people that want AI, they really want the functionality that can be accomplished by standard machine learning, statistical modeling using the right data, because that's also going to be a lot more likely to like, because it's working with a specific data set and it's trained on that and it's a computational type model.

00:28:52.219 --> 00:29:13.964
I'm probably saying this all wrong, but like it's actually uh, trying to just give you the right answer, versus, or to be trained to produce a better answer, um, or better prediction, right, whereas, like the loms are kind of they're still a bit of a black box and they all they do is predict, and they predict based on large, based on language, like how it sounds, right.

00:29:14.025 --> 00:29:28.945
So I think that's a big source of confusion for a lot of people is that they're never, they've never been designed to give you anything close to accuracy or you know anything of use other than sounding good, which is why those like use cases.

00:29:28.945 --> 00:29:36.019
Okay, you can summarize an email right like that's a pretty decent use case and you know that it can be, you know, fairly predictable and do fairly well with that.

00:29:36.019 --> 00:29:45.467
But you really have to architect a whole host of models if you really want it to do anything that gives you any kind of like output that you can rely on.

00:29:45.467 --> 00:29:55.584
Right, and then an lln may be the input mechanism for reaching that model if you want to be able to talk to it, yeah, and right now.

00:29:55.624 --> 00:30:02.230
Well, again, I'll say it's overhyped, and even the llm side of things, I mean technology is moving at an incredibly fast pace.

00:30:02.230 --> 00:30:05.801
So if you're not thinking about it right now, you are probably going to fall behind at some point.

00:30:05.801 --> 00:30:12.023
But I do caution against just throwing it at everything and considering it's at the best option without looking at others.

00:30:13.086 --> 00:30:20.377
I think right now, everybody should be playing around with it a little bit, even if just to be like me, to be like you know what, yeah, you're, you're absolutely like.

00:30:20.377 --> 00:30:45.675
My instinct was correct this hype and this marketing does not live up to what I actually expect, but it takes me actually going and trying it out, to be like, yes, I feel comfortable that I know that current capabilities of this technology don't do what I want or it's not the right fit, right, I think if you're not touching it at all, then you're just susceptible to listening to the hype and thinking it's going to solve your problems and then it really won't.

00:30:45.675 --> 00:30:47.958
I think in most cases it won't at all.

00:30:47.958 --> 00:30:58.411
Or, yeah, yeah, like me, like I've been kind of following from the sidelines, knowing a lot about the previous models and implementations of AI.

00:30:58.411 --> 00:31:05.028
Before LLMs came on the scene, I was skeptical but optimistic.

00:31:05.048 --> 00:31:19.157
Right, I'm excited for the potential of this but at the same time, like I know how overhyped the previous, you know version of things was, even back then, um, working on like proof of concepts where people wanted ai to do all these things.

00:31:19.198 --> 00:31:35.516
And then eventually it's like, yeah, we actually, you know, presented and solved the problem with a, you know, random forest, uh model, architected with a couple of other things that really would be considered more like basic machine learning, right, right, um, but what matters is the output, like people want the output that they want.

00:31:35.516 --> 00:32:04.238
How we get there doesn't really matter, but I think if you're not on that side of the equation, it's way too easy right now to think that current, like hyped technology will just all of a sudden fix all these things that we couldn't do before, or on the other side, you can just be like completely pessimistic and not look into it at all, and then I think you are like things are moving so quickly that you're kind of going to miss the boat because you'll have no clue what's going on when things actually are getting to a point where they are really useful yeah, I mean I remember back.

00:32:04.357 --> 00:32:05.599
Was it two or three years ago?

00:32:05.599 --> 00:32:07.362
I'd have to look at the exact timeline again.

00:32:07.362 --> 00:32:08.844
It might be close to three by now.

00:32:08.844 --> 00:32:21.159
But when Dolly Mini really first came out and I mean it was just we'd around the office we would print out pictures as memes and throw them on each, on people's cubes and on the walls and by the printer, and it was just fun.

00:32:21.721 --> 00:32:21.921
Yeah.

00:32:22.102 --> 00:32:22.442
But it was.

00:32:22.442 --> 00:32:25.818
We weren't getting anything out of it, it was just office jokes.

00:32:25.818 --> 00:32:30.977
And then all of a sudden, chat, gpt came out of nowhere and it was kind of cool, but it wasn't.

00:32:30.977 --> 00:32:32.742
We weren't doing too much crazy stuff with it.

00:32:32.742 --> 00:32:35.819
And then you started learning oh, we can help you with the code and things like that.

00:32:35.819 --> 00:32:52.851
And in my experience it's a lot better on the software side of things like if you want to program something in python or something like that than it is on the plc side, just because there's a larger knowledge base out there for it to learn from yeah um, but then it went from that to all what we know now, all overnight.

00:32:53.115 --> 00:33:09.029
I mean watching the different image generators come and go and watching the technology change and I mean, if I remember, back to just those pictures where it couldn't even do a face without making it look like a swirl, that we were laughing and joking about in the office, to what we're doing now, where it is ubiquitous and a lot of people's lives.

00:33:09.772 --> 00:33:13.821
it's crazy how fast it's moving yeah, so I think we will have.

00:33:13.821 --> 00:33:21.144
Potentially I guess we'll still determining this and, ali, you can speak to this better than I can we're thinking about having an ai section.

00:33:21.144 --> 00:33:46.199
Uh, at ot skater con right, and that that's prompted by a couple of people in our network that attended last year that are actually working on something in the systems integration realm using ai, and that is like building specific applications to to solve a customer problem that they have, or a um, a process that they see as being a repeatable part of their business that they can offer to their customers.

00:33:46.199 --> 00:33:49.105
That has some value for.

00:33:49.184 --> 00:33:49.224
AI.

00:33:49.224 --> 00:33:50.768
Like Wireshark with AI.

00:33:50.768 --> 00:33:53.579
Huh, like Wireshark with AI.

00:33:55.324 --> 00:34:00.821
Yeah, yeah, okay, I don't know about that one, but that would be something that we'd be interested in.

00:34:00.821 --> 00:34:07.865
You know, kind of like exploring in the community, but with, like, what are we actually doing?

00:34:07.865 --> 00:34:09.079
Don't give me the sales pitch.

00:34:09.079 --> 00:34:24.123
Like, having been to some of the press conferences for the you know, release of these co-pilot things, like I just don't see a whole lot of value in like hearing that it's like, okay, brass tacks, so like, can this actually do my thing?

00:34:24.123 --> 00:34:26.963
Or, if it can't do my thing, what can it do?

00:34:26.963 --> 00:34:28.340
What is it actually doing?

00:34:30.335 --> 00:34:34.065
I think it can just do anything that we can do, but way faster than us.

00:34:34.065 --> 00:34:45.407
I think the idea is that it's not going to build anything magical, but we are the magic and if we fed it to these systems, we can do our magic faster.

00:34:45.407 --> 00:34:51.686
So really it's just about bringing our magic to market faster.

00:34:51.686 --> 00:34:56.161
I mean, I think that's really all we're trying to do with the ai right now.

00:34:56.161 --> 00:35:11.074
Um is speed, um, because I I mean, I don't think, yeah, ai isn't magical enough to just make shit up, but, like we have so many things that we can, just that we do so slow and yeah, it's great job security.

00:35:11.074 --> 00:35:20.940
But, like, if we want to actually compete with, like large firms bigger than us, cause we're little right, like if we want to compete and all these other small firms, like, how do you leverage?

00:35:20.940 --> 00:35:31.318
And especially because we are small, we can and we're like startups and we're new, we can bring all this stuff in and force all our people to not force, but you know what I mean?

00:35:31.318 --> 00:35:42.746
Like bring it, make it part of the culture, whereas these giants can't do that, and so it really can be a means of, uh, competition between the little firms and the giants.

00:35:42.746 --> 00:35:48.643
Um, so we can take a real market share if we can use this magic.

00:35:48.643 --> 00:35:57.367
But we have to direct the magic because it absolutely is garbage in, garbage out, um, and so we we have to find the, the magical people to to feed.

00:35:57.668 --> 00:36:02.414
I think I mean nikki was talking about doing this, where it was like people needed to make their own gpts.

00:36:02.414 --> 00:36:20.842
So it was like courtney could make a courtney gpt and that gpt could like help you size a robot and like I could make you, you could make an alley GPT and that will help you, like I don't know, size a pump or whatever, do some piping, um, just like, take all our individual skills and like make these, you know GPTs.

00:36:20.842 --> 00:36:32.389
And then I guess, if we could, I I really want to use it to like quote systems, because I hate making custom, you know, custom control panel quotes.

00:36:32.389 --> 00:37:05.963
It's like there's only so many drawings, there's only so many control narratives and like oem manuals, there's only so many like deliverables, right, like on the integration side, and then the installation side has all of its own and you know, we partner with like electricians and then we just build something that just like makes this so much faster because, like we do, we spend a lot of overhead, uh, creating these freaking proposals, and I think some I mean other people do it better than I do it or we do it, but like, yeah, that's where I'm like I feel like we could really use it.

00:37:06.804 --> 00:37:19.608
Um is, yeah, just sizing, sizing like all the crap that we already know how to size, and yeah, kind of just if we taught it from the you know best people in our organizations.

00:37:19.608 --> 00:37:22.170
But then how do you implement that?

00:37:22.170 --> 00:37:50.123
Because that just seems like really hard, like, unless you can take, unless the person's mind is of the type that can like, like regurgitate everything they know into a list or a flow chart, which I feel I can, but, like, I feel like most people can't, um, and they just don't know how to like dump whatever it is they want to happen into a sequence, or into a flow chart or into a whatever lot sequence of logic gates, yeah, um, and so like, maybe, um, are we thinking?

00:37:50.123 --> 00:37:56.130
Or into a whatever sequence of logic gates, and so, like, maybe are we thinking of, like, maybe we need to start a new business?

00:37:57.014 --> 00:37:58.398
No, I'm just kidding.

00:37:58.398 --> 00:38:02.605
The inverse of that also is like that is all possible without AI.

00:38:03.126 --> 00:38:23.385
It's just it takes building and I think maybe what the barrier that may be being removed here is somebody that's not technical enough to build this into a standard, like in a standard software type environment, or a plugin like build it drop tool Could do this now potentially right by just dumping all that information into a GPT and like trying to train it.

00:38:23.385 --> 00:38:27.365
But, dylan, is that something that you guys like that you're already familiar with, kind of building these things?

00:38:27.434 --> 00:38:35.088
I see you nodding like a little bit technology I'm more nodding because this pivots back to an earlier piece.

00:38:35.088 --> 00:38:38.282
Here there's two points off of that to bring up.

00:38:38.282 --> 00:38:52.117
Is one just like anything else, whether or not we use ai, what, what tool it is, whether it's ml or just a human process, it goes back to the conversation of what are we trying to accomplish?

00:38:52.117 --> 00:38:53.360
Then let's find a tool to do it.

00:38:53.360 --> 00:38:57.119
Ai may or may not be that tool, and it could be a lot of times.

00:38:57.119 --> 00:39:01.858
But if we start with a conversation with, well, I need AI, you're not going to get the right tool.

00:39:02.760 --> 00:39:04.021
Okay, touche.

00:39:04.824 --> 00:39:11.503
So the big one for me is starting with the problem, starting with the need, and then finding the tools and the technologies that can support that.

00:39:12.605 --> 00:39:23.202
And then, if we follow that logic back to kind of what Ali was saying, I was really nodding along with the point of well, that takes the right type of person, who can document that, who can think that way, who can.

00:39:24.143 --> 00:39:32.567
And even if you take A out of the equation, you need that, that somebody in the organization with that skill to get that knowledge transfer to happen.

00:39:32.567 --> 00:39:40.599
Because a lot of the engineers are really good at documenting in very technical ways, or some of them are really good at figuring stuff out, but they can't document anything for their life.

00:39:40.599 --> 00:39:53.844
Some people are really good at documenting but they don't have any of the technical experience and so they're really good at pulling that out of people and then documenting it for them, and those are all good ways of doing it for different people.

00:39:53.844 --> 00:39:58.784
And that comes back to even before you start talking about the needs and the problems.

00:39:58.784 --> 00:40:13.166
That's much larger cultural things to think about and that's part of where the further I got in with the technology, starting even with the electricians and wires and terminations in the field, all the way through almost the entire automation stack.

00:40:13.166 --> 00:40:15.449
The conclusion I came to is none.

00:40:15.449 --> 00:40:16.650
And AI is included.

00:40:19.375 --> 00:40:24.467
None of these technologies are going to solve your problems until you've identified the problems and identify the need to do something about it.

00:40:24.467 --> 00:40:48.208
That's where a lot of my current time and thought is spent on the people side and the culture, much more than it is on any specific technology or implementation, because they're always different, but the people are the same, the attitudes are the same, the culture is the same, and it always goes back to that question of whether I want to put a wiki together and put it in a Teams channel as a knowledge base.

00:40:48.208 --> 00:40:50.360
Well, I got to get my employees to do that.

00:40:50.360 --> 00:40:51.865
They're not all good writers.

00:40:51.865 --> 00:41:00.284
Some of them are really good and some of them are good at other things, and we were in that same problem that we just came to when we were talking about documenting GPTs as well.

00:41:00.284 --> 00:41:05.505
So you have a lot of this overlap, and it all happens way before we start talking about technology.

00:41:08.938 --> 00:41:09.733
People are everything.

00:41:10.135 --> 00:41:10.456
Mm-hmm technology.

00:41:10.456 --> 00:41:14.262
People are everything.

00:41:14.262 --> 00:41:20.762
So, just like, if I mean the question comes down to do I need an MQTT broker in my IOT stack?

00:41:20.762 --> 00:41:22.907
Maybe let's talk about it.

00:41:22.907 --> 00:41:23.916
What are you trying to accomplish?

00:41:23.916 --> 00:41:26.282
Do I need AI in my corporate initiative?

00:41:26.282 --> 00:41:27.907
Maybe let's figure out why.

00:41:29.335 --> 00:41:36.186
But if you start saying I need an MES system or I need a SCADA system or I need AI, it's going to be a problem.

00:41:36.186 --> 00:41:40.126
And then your digital transformation, your little project, whatever the scope, is going to fail.

00:41:40.126 --> 00:41:46.036
The one might be successful, the second one or the third one you're eventually going to find yourself in a bottleneck.

00:41:46.036 --> 00:41:47.501
You're going to have some technical debt.

00:41:47.501 --> 00:41:49.947
Things are going to fall apart somewhere along the line.

00:41:50.608 --> 00:42:00.219
So if you really want long-term sustainable solutions rather than just a one-off project, that's where these questions come in, where it's not about I need an ERP system.

00:42:00.219 --> 00:42:01.240
It's not a part.

00:42:01.240 --> 00:42:02.163
I need MES.

00:42:02.163 --> 00:42:08.163
It's I want a way to schedule my work orders better, because the people on the floor are losing the papers.

00:42:08.163 --> 00:42:11.655
And now we start talking about how can we do that?

00:42:11.655 --> 00:42:22.079
And oh, by the way, now we have an MES system, or maybe we're going to add some more features than eventually we do, or I need to know the state of this machine that's running so that I can calculate this KPI over here.

00:42:22.079 --> 00:42:35.025
All right, let's throw in some IO link sensors and maybe that master talks MQTT, so we throw a broker in there and then that broker goes to whatever's calculating that kpi and all right, yeah, cool, now we've got some iot going.

00:42:35.025 --> 00:42:36.237
But that was never the intention.

00:42:36.818 --> 00:42:44.782
The intention should always be to solve a problem yeah, I think we get a lot of on the vendor side of our industry.

00:42:44.782 --> 00:42:50.092
We get lost in our own buzzwords and marketing and we think that everybody needs our solution.

00:42:50.193 --> 00:43:01.494
Right, they should well, somebody brought up to me recently the difference between engineering, like selling engineering, and selling solutions, and I was like, oh, that was like an epiphany for me.

00:43:01.494 --> 00:43:08.791
I was like, oh crap, like, because engineering doesn't, you know, is repeatable.

00:43:08.791 --> 00:43:16.748
Everybody can, a lot of people can do engineering, but like providing a solution, I mean it's like when did when did engineering not become solutions based?

00:43:16.748 --> 00:43:26.717
Like, I don't know what happened, but it definitely happened Because, you know, I always thought engineering was, you know, we're engineering because we're trying to solve something, but that's not necessarily what's going on.

00:43:26.717 --> 00:43:28.061
And so you should.

00:43:28.061 --> 00:43:33.485
I mean, at least in terms of like, when people are looking for solutions, they're not looking for engineering.

00:43:34.074 --> 00:43:35.398
Right, and that's where I'm in.

00:43:35.398 --> 00:43:38.838
Going back to the project I was talking about, where we start with ignition.

00:43:38.838 --> 00:43:56.280
As an HMI, I mean projects like that and I get myself in trouble sometimes because it's not always great for the companies I work for usually ends up good in the end, but some, depending on how you're thinking about it, right yeah Is I'll be sitting down with the customer and clients and I will be sitting in this meeting.

00:43:56.280 --> 00:44:08.827
We'll be talking about the scope and what we need to do and I'll start putting a quote together and I'll see, well, we hard specced a panel view and I'll go back and said, well, you said you want to do all this, but you told me you want to use that.

00:44:08.827 --> 00:44:10.871
That's not going to work.

00:44:10.871 --> 00:44:20.259
And so then we start to kind of the conversation and sometimes I have to just quote the panel view and it is what it is and we'll do the job.

00:44:20.259 --> 00:44:22.465
And most of the time it doesn't work.

00:44:22.545 --> 00:44:28.137
If that was what they were talking about, if it's a standalone little panel on the side, a little skid system or something, there's no problem.

00:44:28.137 --> 00:44:39.724
But if you're trying to then connect to that later, then the PLC becomes a bottleneck because now you've got the HMI and some other device and your IoT system all pulling tags out of the thing, and now you just run out of memory.

00:44:39.724 --> 00:45:23.317
The CPU can't keep up, so then okay, well, if we know we're going to do this data initiative no-transcript, the plc like let it go, like, oh yeah and I mean at the same time they're, they're, they're, they're going to argue.

00:45:23.356 --> 00:45:32.217
Well, our people all know how to use, like they know how to do mer files, or they know how to use panel view, and that's why we don't want to do your solution.

00:45:32.217 --> 00:45:33.822
We want to do what our people know.

00:45:33.822 --> 00:45:36.527
Um, I mean, how do you really combat that?

00:45:36.527 --> 00:45:48.762
Or do you just put that gateway in and you're just like fine, we'll use your stuff, but we're going to make it all talk through this and then we all win, even though you're still you're spending more money but you are making your maintenance people happy right and there's a compromise.

00:45:48.782 --> 00:45:55.259
I mean, sometimes there is a very good reason for this is what the people know and we can't spare parts agreements.

00:45:55.981 --> 00:46:05.007
I mean, that's used as a very bad argument a lot of times, but there are times where it's valid and it's identifying those and being able to put together the team.

00:46:05.007 --> 00:46:17.791
And again that's where I keep falling back to the culture piece much more in the technology, because you can't actually affect any change for what I'm trying to look for and where I'm passionate in with just putting in the panel view.

00:46:17.791 --> 00:46:21.085
So then it's well, and sometimes the panel view is great.

00:46:21.085 --> 00:46:38.315
I'm not saying that's always the bad solution, but in the case where you want this big data architecture, you want this other stuff and you're going to put in the panel view, but you won't even at least put in an OPC server or something on the side, then you start having problems with scalability and maintainability.

00:46:38.226 --> 00:46:41.847
Things really don't scale the way that, through the conversation with them, have already identified that they're looking for.

00:46:41.847 --> 00:46:49.867
And so then you guys start talking about the bigger picture stuff and you start talking about strategies and roadmaps and how are we going to get there?

00:46:49.867 --> 00:46:53.355
And well, this is part of a bigger thing and you lose a lot of people there.

00:46:53.355 --> 00:47:02.043
So then you got to start figuring out how to feed the information at the right times and make sure things are successful, and it just becomes a whole dance of how to.

00:47:02.043 --> 00:47:13.347
I mean, it's all about the culture, more so than anything, and that's a whole different game than the technology it's.

00:47:13.487 --> 00:47:22.527
That's so true, because you can take the same technology stack and implement it in two different companies that have two different cultures, and you'll have very, very, very different outcomes.

00:47:22.708 --> 00:47:36.876
Yep, and I'll recommend a fully different technology stack to those two different cultures yeah I mean you might have a brownfield site that already has plant packs installed on everything and there's no reason to rip it out for data stuff, but you're not getting much of your data out of it.

00:47:36.876 --> 00:47:40.143
So then maybe we don't even look too much at ignition right away.

00:47:40.143 --> 00:47:44.664
Maybe we just start with like flow software or high byte or something to pull data out of fact talk historian.

00:47:44.664 --> 00:47:57.539
Or if we're doing a site where they don't already have this entrenched stuff, or maybe it is a rip and replace type thing where the old system's not working well or it's a legacy thing that needed to go anyway, then we can start with something big like Ignition and build the whole thing from there.

00:47:57.539 --> 00:48:06.291
But there's always different people involved and as long as there's different people, you're going to have different solutions and different needs and different wants and different perspectives.

00:48:06.291 --> 00:48:11.094
Everybody's different, every team is unique and what they need to be successful is unique.

00:48:13.505 --> 00:48:24.280
Well, I think the one non-unique thing is that everybody needs to like focus on data, and if you're blind to data, you're kind of like well what, I don't know what's gonna happen to you.

00:48:24.280 --> 00:48:47.230
I worked with a machine shop that I will not name whose control engineer used panel views often and never, never, used the like alarm historian and like alarm alarming, like you know the table yep um, and so there would just be, you know, like if there was an alarm state, you could see it, but there was no history of it, right.

00:48:47.269 --> 00:48:55.125
so it was like we didn't have time stamped alarms and I was like what in the hell is going on, um, and so it was just like welcome to you know the 21st century.

00:48:55.585 --> 00:49:02.416
No, but, um, uh, that's incredibly important and people don't know they need that.

00:49:02.416 --> 00:49:13.507
They don't even know what they're missing if they've never seen it, and some of that stuff is just like built into even things like a panel view and yeah.

00:49:13.507 --> 00:50:02.150
So there's like those standards, you know, if they don't know about it, uh, data, data standards, um, and and like how you get like what is the general information that you need to show to like the operator of a machine, like there's minimums and you can go really deep, um, and you can create all these you know, like compounded kind of situations, um, but at the minimum, you know every sensor you need to know like is, is it in a faulted state, like um, and or you could just not look into that at all and not show those numbers, and and then you don't know what you don't know, I guess, yeah um, and that goes back not just to the customer side too, but also as we're doing commissioning and things like that, or as we get service calls.

00:50:02.813 --> 00:50:08.960
So going back to do we put these things in, at whose cost and how much are we giving away for free?

00:50:08.960 --> 00:50:19.228
This is part of the efficiencies that we're gaining on our side, too is now we get the service call for this machine that we've warrantied for a year or whatever, and with Ignition as the HMI.

00:50:19.228 --> 00:50:41.875
One of the things that I do with very minimal effort, now that I've done it enough times is we've got the data log to tell you which operator was logged into which HMI when they pressed the button to put the machine into hand mode and manually jog this thing, at which alarm showed up at that time nice, the general equipment state and all the other stuff.

00:50:41.875 --> 00:50:44.188
That and the other machines that might also have that right.

00:50:44.188 --> 00:50:51.168
And once you're on that level of stuff, I mean that's when the doors really start to open.

00:50:51.168 --> 00:50:53.655
People know what they, people don't know what they don't know.

00:50:53.655 --> 00:50:53.996
They don't know.

00:50:53.996 --> 00:50:55.969
This is even possible, let alone that it's easy.

00:50:55.969 --> 00:50:58.673
And so the big one there is.

00:50:58.673 --> 00:51:07.016
I mean my favorite story on that is I was at a customer site where they had three shifts and the manager came in.

00:51:07.217 --> 00:51:10.637
Manager and I both came in the morning we were still commissioning it, but they were already running it.

00:51:10.637 --> 00:51:14.072
It was pretty much that last week where you're kind of babysitting and training right.

00:51:14.072 --> 00:51:25.307
And we came in in the morning and there had been a big problem, a big pile up of spilt raw materials on the floor on third shift and nobody knew why.

00:51:25.307 --> 00:51:30.233
Manager just got upset and started yelling at the operator this is what's going on, and all that.

00:51:30.233 --> 00:51:33.186
And I pulled him back and said, hey, before you start yelling, let's actually figure out what happened.

00:51:33.186 --> 00:51:37.197
And so I pulled him in toward we were looking at that.

00:51:37.344 --> 00:51:39.858
This is a larger SCADA system, not so much just an HMI.

00:51:39.858 --> 00:51:49.976
So we pulled them in front of the computer and pulled up the keyboard and threw together some of the ad hoc trending tools we had and let him drag and drop tags and history into a chart and some trends and all that.

00:51:49.976 --> 00:51:57.998
And we were able to identify that the operator actually did exactly what they were trained to do in that scenario and he realized they probably shouldn't be trained to do that.

00:51:57.998 --> 00:52:00.590
So I actually don't do that anymore.

00:52:00.590 --> 00:52:01.092
That's on me.

00:52:01.092 --> 00:52:10.514
And now nobody was screaming at anybody, nobody was angry, and everybody got better for it, and that's not an, that's more that's.

00:52:11.425 --> 00:52:16.750
That's a life jab at me because I always spiral and really I just need to not do that.

00:52:17.070 --> 00:52:31.606
It's like calm down let's just let's just figure it out, yeah but even I mean I guess I don't know that about you or not, but specifically like if you had the option to come in, you saw something was wrong and you knew the data was there.

00:52:31.606 --> 00:52:39.856
Now that gives you the chance to go yeah absolutely, even if you were right now you've got that cool down period where you're no longer hotheaded, just jumping into the situation.

00:52:39.856 --> 00:52:44.826
You've had 20 minutes removed trying to solve it and identify it, but also now you know what happened.

00:52:45.407 --> 00:52:46.690
whether it was what you thought.

00:52:46.690 --> 00:52:48.655
Absolutely, I've never not regretted it.

00:52:48.655 --> 00:52:50.525
It's just something that's hard to control.

00:52:50.525 --> 00:52:53.608
But yeah, no, the data.

00:52:53.608 --> 00:52:58.871
The data speaks way louder than anything else and that's why you need to have the data.

00:52:58.951 --> 00:53:06.094
And yeah, I've, you know, through my career, have, you know, let others pressure me.

00:53:06.155 --> 00:53:14.079
You know, like project managers and like other people in the project that have a, you know they want to save money on a project.

00:53:14.139 --> 00:53:32.418
So it's like they make decisions and or they push decisions onto the designers that aren't the best decisions, and I've watched, you know, the repercussions of that, and so it's just, you know, nice to see that like, oh crap, Like I've seen we're not going to put limit switches in on our valves.

00:53:33.744 --> 00:53:55.449
So so when we go to, like you know, and we had like temperature control valves and we're like, well, it's sending out, like full open for the cooling valve, and like you go there and you just hear yep, and I'm like, no, it's because air is like not being delivered, like, yes, the solenoids open, uh, but there is, yeah, the air was not connected.

00:53:55.449 --> 00:53:56.592
Somebody disconnected air.

00:53:56.592 --> 00:54:11.731
And so, if you don't know that, by having all of the proper feedback, feedback costs more money because it, because it's usually another set of wires or another wire, um, and so that's where people are like, well, let's use you know as much as we can.

00:54:11.731 --> 00:54:17.532
You know communication or remote ios, so we can do you know less, less wiring or whatever.

00:54:17.532 --> 00:54:20.398
But yeah, I don't know where I was going with that.

00:54:22.226 --> 00:54:25.315
I'll make an assumption where you're going with that and correct me if I'm wrong.

00:54:25.315 --> 00:54:32.186
But I mean that data just isn't for the big MES data type, erp, digital transformation things.

00:54:32.186 --> 00:54:34.552
We need more data for the control systems too.

00:54:34.552 --> 00:54:43.268
I mean I've been there where you've got the projects, like you just said, where you don't have positions on the valves and the operator's saying, well, the valve's open, why isn't it open?

00:54:43.268 --> 00:54:44.291
Screen says it is.

00:54:44.291 --> 00:54:46.507
You're clearly wrong and I'm like, no, did you turn on the air?

00:54:46.507 --> 00:54:50.943
And yeah, whole thing's avoidable by just putting the switches on.

00:54:50.963 --> 00:54:58.559
Yeah, the screen is it got an orange or a green valve because the signal is on, but that doesn't mean that it's actually turned on.

00:54:58.559 --> 00:55:00.713
It just means you're trying to turn it on.

00:55:00.713 --> 00:55:01.909
The command is on.

00:55:02.331 --> 00:55:03.146
Right, Green doesn't.

00:55:03.146 --> 00:55:07.536
If it's green or white or whatever your color scheme, that doesn't mean that it's on.

00:55:07.536 --> 00:55:08.931
It means that we're assuming it's on.

00:55:09.545 --> 00:55:11.291
Yeah, it means that we're trying to turn it on.

00:55:12.525 --> 00:55:13.786
And then I mean it goes to the same thing.

00:55:13.786 --> 00:55:17.492
Do you have auxiliary contacts coming into inputs off your e-stops?

00:55:17.492 --> 00:55:19.594
Do you have disconnects?

00:55:19.594 --> 00:55:23.139
Do you know which disconnect is tripped, or is the motor just going to not run?

00:55:23.139 --> 00:55:24.860
So now we're telling it to run and it's not running.

00:55:24.860 --> 00:55:31.197
Well, do we assume it's a bad motor because or, as we're troubleshooting, we find the disconnect?

00:55:31.217 --> 00:55:32.922
was off, and how much time was wasted there.

00:55:37.144 --> 00:55:38.672
And even outputs on cards can go out, or inputs, which is crazy.

00:55:38.672 --> 00:55:38.954
And so it's.

00:55:38.954 --> 00:55:41.364
The data isn't just for the big picture IoT world and the digital transformation.

00:55:41.364 --> 00:55:47.351
We need more data to make better control systems too, before we even talk about logging in and doing stuff with it outside of controls.

00:55:47.351 --> 00:56:06.931
And again that goes back to the culture piece, because if the bottom line says, well, we can save money by pulling, not pulling these two wires, and then a year later they realized how much more time they're spending in maintenance and troubleshooting because they didn't have those wires, and I don't think anybody in the controls world has ever not had this thought of, well, we weren't consulted early enough in the project.

00:56:06.931 --> 00:56:13.755
But it's true, yeah, because nobody thought about the ramifications of taking out those wires because they didn't know it's not well.

00:56:13.775 --> 00:56:46.797
That's why I think it's so unique and so valuable to have someone like you, with your background, or Allie in the sense of like, where the time that she spent, like with the electricians and in these different types of like, different areas of the business, right, because you start to realize that you should think of things that other people that just haven't had that experience with it, right, and I know we don't have much time left so people that just haven't had that experience with it right, and, uh, I know we don't have much time left, so, um, I'll mention a tangent path that we won't go down but otherwise would be a whole.

00:56:46.817 --> 00:57:06.856
Another episode um, I noticed some chatter in our ot skater con uh group about, uh, I guess vlad from manufacturing hub shared an article or a podcast, I think, think, and this was um, and I know Alicia Lomas uh chimed in but about kind of software engineering and how that's really kind of taken over in a lot of the greenfield and like the startup space in particular.

00:57:07.278 --> 00:57:24.849
And I'm quoting something I haven't listened to, but the discussion seemed to be that, you know, they're kind of finding that, yes, people want to do this with more traditional software approaches and get away from, like the old school, plc stuff, right, so you can have more software engineers instead of, like, lateral logic controls people.

00:57:24.849 --> 00:57:28.476
But they seem to be missing the boat on this success.

00:57:28.476 --> 00:57:49.472
I think in large part and this is again just my you know, throwing my opinion at the wall without knowing much that you have software engineers that can program processes all day long, but they don't know whether there should be a limit switch on something or whether there's missing data input from the way that the processes actually work or what cavitation is, or anything.

00:57:50.304 --> 00:57:51.489
Yeah, and this is, I think.

00:57:51.650 --> 00:58:13.175
Ali and correct me if I'm wrong, but one of the reasons why you put together OT Skatecon was exactly for this reason to try to get all of those people together in the same room and to like not so much that everyone has to know all the things, but you should know what you don't know to a degree and like who you need to be thinking of and maybe who to call if you do need that perspective.

00:58:14.286 --> 00:58:24.907
Knowing what you don't know is incredibly powerful today yeah and except that many people like dylan around that, like you know, you started an electrical installation and now you do.

00:58:24.907 --> 00:58:29.677
You know software programming for these big systems like that.

00:58:29.677 --> 00:58:35.623
I don't think that, like I don't know any old electricians and then now works in mes.

00:58:35.664 --> 00:58:39.074
Like that's crazy, which is really cool I mean, naomi does too.

00:58:39.074 --> 00:58:45.097
But like, yeah, like it's very, very, very rare to be able to to speak both of those languages.

00:58:45.097 --> 00:58:47.851
Like because electricians do speak their own language.

00:58:47.851 --> 00:58:51.927
And if you do not know how to design motor control circuits, good luck.

00:58:51.927 --> 00:59:06.512
Uh, actually like arguing with them in a commissioning job, I find that right now, like with my own engineers, I'm like they are going to, they're going to say a lot of things and the only way to prove it isn't us is to prove that it is them.

00:59:06.512 --> 00:59:11.494
So you have to be able to like, see, like look at their circuits and be like, well, what about this?

00:59:11.494 --> 00:59:15.773
And once they know that you speak their language, like they do, they stop with the crap.

00:59:17.164 --> 00:59:17.445
And and.

00:59:17.445 --> 00:59:19.608
Once they know that you speak their language like they do, they stop with the crap.

00:59:19.608 --> 00:59:25.260
And to touch on a few of the points we just hit there real quick before we run out of time is the first one going backwards in order here as I remember them.

00:59:25.260 --> 00:59:29.797
But the funny thing for me too is I didn't just start with and know a lot of electricians.

00:59:29.797 --> 00:59:32.632
I was taught electrical engineering by electricians.

00:59:33.353 --> 00:59:34.197
That's baller.

00:59:34.726 --> 00:59:38.967
And that comes from a whole different perspective than a traditional education would.

00:59:38.967 --> 00:59:46.931
Yeah, then the other one is too with the software piece, and we could have a whole, another hour or two long conversation on the nuances there.

00:59:46.931 --> 00:59:51.835
But just to say it a little bit is again, it comes down to the people and the needs.

00:59:51.835 --> 01:00:00.938
I mean, I know plenty of controls engineers who don't have the process knowledge either, and so it's not a unique thing with the software engineers, it's just a thing with the industry.

01:00:00.938 --> 01:00:05.382
You need to have both the process and some of the programming knowledge, or at least a team that has all of that.

01:00:05.961 --> 01:00:06.181
Yeah.

01:00:06.545 --> 01:00:16.409
And going back with different needs, different tools, different technologies for different people and cultures and things like that is you get into, it's always going to be you need both.

01:00:16.409 --> 01:00:22.036
Nowadays, there's never an argument, I'll say, where you don't need software or you don't need control as a traditional engineering.

01:00:22.036 --> 01:00:25.596
But how much of each is going to depend on the team.

01:00:25.596 --> 01:00:35.110
And there are applications where a fully software-defined PLC will do the job better than a regular one, and there's times where you need the reliability and the safety of a more traditional one.

01:00:35.110 --> 01:00:39.641
And as more technology comes out, I'm sure that line is going to get more and more gray as it goes.

01:00:39.641 --> 01:00:46.425
But it always comes down to, just with any other technology, it's we can use this and that, not this, or yeah.

01:00:48.748 --> 01:00:59.336
So, yeah, my, my life motto seems to apply here, just like it does to everything else, which is why it's still my motto, which is the answer to everything, is it depends.

01:00:59.336 --> 01:01:13.389
Yep, you're like that's a cop-out, but it's not in the sense well, yeah, no, I mean, it just feels like one, yeah, well, yeah, and.

01:01:13.389 --> 01:01:27.476
And the lack of a cop-out is clear if you say, well, it depends, and now let's dig into what those things are, versus just using the word it depends as a way to avoid getting any kind of answer I've been accused of that myself.

01:01:27.557 --> 01:01:45.474
I say it depends a little bit too much, especially with technical stuff and especially on forums and stuff where you can't really have the whole story up front yeah it's always it's why it's so hard to have these discussions, and I don't want to venture into other topics like politics or whatever, but it's like when people don't appreciate nuance, then what the heck?

01:01:45.474 --> 01:01:46.637
Why are you even talking?

01:01:46.637 --> 01:01:46.818
Now?

01:01:46.818 --> 01:01:48.530
You're just like you're.

01:01:49.213 --> 01:02:04.838
You're saying one thing and it clearly can't be like correct and you just have childhood trauma at that point like, and that's not our problem, but I think that's one of the things that we struggle with, too, as content creators, if you want to call it that.

01:02:04.838 --> 01:02:14.594
Right, like we were having these discussions, and in public, and the reason we did was we were, we thought there was value in the discussions we were having in small groups online, and we were like you know what?

01:02:14.594 --> 01:02:18.755
There's probably people that would love to be part of this small group if they knew that we existed, and vice versa.

01:02:18.755 --> 01:02:42.523
So let's put this out there and let those people find these discussions or whatever we're talking about, right, but we're so not like focused on the headlines or the clickbaits, or even when people, when they want to have an episode with us and I love the way you put it was like here, an episode with us, um, and I love the way you put it was like here's a bunch of things I can talk about and or anything.

01:02:42.472 --> 01:02:46.538
Um, because that's also how we are because when people want to like, oh, we want to talk about this specific thing and the headline is going to be this, I just feel like it loses meaning for me.

01:02:46.538 --> 01:03:07.735
Like, if you're trying to predetermine in a can what you're saying, then really what you're doing is messaging you're not discussing anything if all you want to do is, like you know, talk like throw out your buzzwords and not get into the meat of actually how and why, and those things are always messy and complicated and they don't got into some buzzwords when they were playing meeting.

01:03:09.827 --> 01:03:12.271
Um, it just yeah, it's, it's.

01:03:12.592 --> 01:03:41.751
It's tricky to then be like you have confidence in what you know, um, but standing next to someone that has like unlimited confidence in the thing they don't know, they can come off as more than you because you actually care to like really give the the better answer or the more correct answer or the more feasible answer, versus just the thing that I've been taught and like I've been guilty.

01:03:42.353 --> 01:03:57.771
My first job out of college was for a, you know, manufacturer of sensors like kians, and they're very they sell only their own stuff and they they're you know, japanese kind of version of doing things is when they, when they come out with a new version, they want to make sure that they're the best at something right.

01:03:57.771 --> 01:04:07.898
So every catalog that comes out of key is that I know from at least back in my day was like it's the fastest, the world's smallest, the whatever.

01:04:07.898 --> 01:04:20.293
Like a very definitive, very flashy statement which has some truth to it, because at the time it was released it probably was the smallest in its class, based on the design considerations and like the application that they're tackling.

01:04:20.293 --> 01:04:36.717
But you know, when I come out with that brochure two years later and I go to my customer and I'm like it's the smallest in the world and it's like, well, with a lot of asterisks, right, like you start to realize, the more you learn how stupid it is to say something like that.

01:04:37.264 --> 01:04:38.349
Most of the smallest in the world.

01:04:38.349 --> 01:04:47.313
But if you've got a bunch of empty space now because you didn't need the smallest, it comes back down to yeah, and also it probably won't be the smallest for very long, right?

01:04:47.333 --> 01:04:50.713
So your talking point is immediately outdated as soon as somebody else makes a smaller one.

01:04:50.713 --> 01:04:58.552
And, yeah, I think you know from a systems integrator point of view too, like, how do you communicate the value of the fact that you know what?

01:04:58.552 --> 01:05:05.681
We're not going to try to sell you a solution and a can solution that won't actually be the best for your problem.

01:05:05.681 --> 01:05:34.655
We have, you know, being able to say, like that, something that's like super and I guess this is why I'm not in copywriting or marketing, really but like you have to be able to translate that into something that sounds as flashy as as the people that are super confident in their, in their like major feature that's just going to like be the silver bullet for everything.

01:05:34.675 --> 01:05:35.237
Yeah, and that's as you said.

01:05:35.237 --> 01:05:48.159
Nuance and intent matters, and one of the scary parts of public conversations like this is intent matters, and somebody listening to this later or with a different background may or may not pick up on that intent.

01:05:48.159 --> 01:06:03.713
And then you said something that was right for this scenario, but that doesn't mean it's right for every scenario, and you can only say so much in a one-hour conversation, so you can't cover your bases of well, in this scenario, it's this and I like that over there, and maybe this one instead, and there's a lot of nuance that it's hard to convey.

01:06:04.815 --> 01:06:17.697
Absolutely Well, I think, and for those of you that are listening unless you're, like a first time listener to Automation Ladies, hopefully you know our intent and the fact that we appreciate this nuance, and we hope that you do too.

01:06:17.697 --> 01:06:19.472
Uh, but we would, I guess.

01:06:19.472 --> 01:06:21.219
Yeah, let's, let's wrap this up, ali.

01:06:21.219 --> 01:06:26.695
Do you have any last questions, since I kind of hijacked the last few minutes here before I go into my standard closing question?

01:06:26.695 --> 01:06:30.452
No, I'm good, this was awesome, thank you.

01:06:30.452 --> 01:06:34.099
Thank you, yeah, so I guess we'll just end with dylan.

01:06:34.099 --> 01:06:51.010
Can you tell our listeners, um, where, if, if you know you're open to connecting, where people should find you, what they should do, if they like what you have to say today, either from a, you know they want to work with you or they just want to, you know, be in your professional circles.

01:06:51.010 --> 01:06:55.536
Where do they find you and is there anything that we should be looking forward to seeing from you in the near future?

01:06:56.505 --> 01:06:59.594
So the first one is easiest place to find me is going to be LinkedIn.

01:06:59.594 --> 01:07:03.753
Other links should be available through there just as easy as anywhere else.

01:07:03.753 --> 01:07:10.456
Yep, the if you need to get in touch and want to work with us, things like that.

01:07:10.456 --> 01:07:17.273
Fishbone Technical is a systems integrator, so we're doing a lot of the stuff I talked about here.

01:07:17.273 --> 01:07:28.913
That's what we're doing and we do everything from machine and process control to data-centric IoT stuff and process implementations and consulting and things like that.

01:07:28.913 --> 01:07:35.851
And as far as what's coming next, I don't have too many announcements, but 2025 will be a fun year.

01:07:38.385 --> 01:07:38.505
Okay.

01:07:38.505 --> 01:07:40.489
So I think everybody, everybody, let's follow dylan.

01:07:40.489 --> 01:07:48.291
Um, we are going to be seeing you at ot skate icon and I think, ali, we are working on, I think we got you to agree, we just now.

01:07:48.291 --> 01:07:53.898
Now we need to go implement, but to to help us with some sort of discord, uh chat for those that are coming.

01:07:53.898 --> 01:07:59.447
Um, and, yeah, I think we should make one of the rules for that is that you must appreciate nuance and discussion.

01:07:59.447 --> 01:08:06.927
If you want to be here, yeah, it might as well be said.

01:08:06.927 --> 01:08:28.166
You know, to be clear that, and I tried to put this caveat like you know, we're not just going to cancel you if you say something wrong, but you kind of have to be open to the feedback as well, like if you're going to come in and like in any public form or semi you know public thing, because even we all know, like private groups are still not private.

01:08:28.185 --> 01:08:37.475
Somebody can always share what you say or whatever, but it's really important to be able to appreciate people's intent and the nuance in the discussion.

01:08:37.475 --> 01:08:45.186
And I think in most cases where people end up fighting and you know mudslinging and stuff, like you really don't need to do that.

01:08:45.186 --> 01:09:16.354
You probably were trying to say the same thing in the beginning but you just, you know, didn't take the time to try to get there, to realize where, where you're at compared to another person, and so many of these like interpersonal and career and like things that we think about there are so reflected on the same side of the technology, because we're always integrating, right, we're integrating different processes with different companies and you know you've got the end user and the systems integrator and all the associated contractors and like it kind of goes hand in hand.

01:09:16.354 --> 01:09:31.975
Like you, really you just got to understand who you're working with, like try to understand, like where to anchor the conversation, what people know, what they don't know, and then like just proceed with kindness and the intent to get something done of value together.

01:09:33.085 --> 01:09:39.127
Integration is a much, much larger category than just automation, and it's easy to forget that in our field.

01:09:39.148 --> 01:09:52.356
That's true, um, and I guess it's been hard for us to capture the in, in the name of the event, at exactly what it is, because some people just look at skater and they're like, well, I don't do skater, this isn't for me, um, or you know that sort of stuff.

01:09:52.396 --> 01:10:11.442
So we we could change that, we could put a motto and it's just like the yeah, like a little tagline or something that solutions community, that we're a lot more inclusive than just the, the ot and the skater uh terminology.

01:10:11.442 --> 01:10:15.586
But anyway, we're very happy to have you as part of our community, dylan.

01:10:15.586 --> 01:10:16.726
Thank you so much for the time.

01:10:16.726 --> 01:10:23.671
I think our listeners are going to either already know you or be very interested in getting to know you and following you.

01:10:23.671 --> 01:10:25.771
And yeah, I think that's all.

01:10:25.771 --> 01:10:26.731
And happy Thanksgiving.

01:10:26.731 --> 01:10:47.904
I know whoever's listening to this it will not be Thanksgiving, but we are recording this, everybody that listens and supports our community, and from us you should probably expect some more video content as we try to shift a little bit just from the audio side of things to video going into 2025.

01:10:47.904 --> 01:10:52.336
But this one will come out on the audio podcast either way.

01:10:52.336 --> 01:10:56.555
So with that I'm going to stop rambling and say goodbye everybody.

01:10:56.555 --> 01:11:00.144
Thank you, thank you, thank you.