61 min video  /  58 minute read


Travis Cox

Chief Technology Evangelist

Inductive Automation

Kevin McClusky

Chief Technology Architect & VP of Sales

Inductive Automation

Kent Melville

Director of Sales Engineering

Inductive Automation

The 2021 Build-a-Thon was the first ever to feature members of the Ignition community battling it out head-to-head. This year, we invited all of Inductive Automation’s Premier Integrators to apply for a chance to wear the Build-a-Thon blazer, and after three rounds of challenges, the final two integrators, DMC and Roeslein & Associates, will face off at the conference.


Announcer: Welcome to the Build-a-Thon. Please give a round of applause to Inductive Automation’s CTE, Travis Cox, and CTA, Kevin McClusky.

Kent Melville: Okay. Welcome, everybody, to ICC X, and of course, of course, the Build-a-Thon, the best session of the conference by far. Not that I'm biased at all, but truly today, we have a great show prepared for you, so be excited. We're gonna keep you on the edge of your seat the whole time. But at this conference, we've had a lot of exciting things happen. Right? We've met new company leadership, got to check out the Ignition Cloud Edition, hear about that. Learned a little bit about 8.3, and we've seen some old friends, we've been able to meet some new friends, and now you're all here so that we can take those friendships and tear them apart as we put people head-to-head and make you, the Ignition community, vote to see who will end up being the inevitable victor. But nobody really embodies that spirit of competition and that pursuit of excellence quite like the original competitors of the Build-a-Thon, Travis Cox and Kevin McClusky. Guys, come on out here.

Kent Melville: So yeah, how are you guys doing?

Travis Cox: We're doing great, man.

Kevin McClusky: Fantastic.

Travis Cox: Glad to be here.

Kent Melville: You excited for this competition?

Travis Cox: Oh, 100%.

Kevin McClusky: Oh yeah.

Kent Melville: Awesome. Well, sounds good. Well, you guys can go ahead here and take a seat. And despite the Build-a-Thon always being a thinly veiled vanity trip for me, so I can just come and sing and dance and perform on stage, we have actually announced some pretty exciting things at each Build-a-Thon for the past several years. And so, Travis and Kevin, can you guys tell us a little bit about these past IC... Or these past Build-a-Thons and what people have seen?

Kevin McClusky: Sure, yeah. So starting out with the first one, if we go all the way back to the Stone Age, we started out... There was a song by Kent in the middle of it, which was amazing. Two of you were here for it. And we started out just doing building head-to-head, we had the Perspective Module in beta, and we sat down, and we built something, and Travis, you took home the crown. It was really amazing what you did.

Travis Cox: I just can't believe we actually went on stage and developed on a beta program. Oh my gosh.

Kent Melville: It turned out great.

Travis Cox: But of course, then the second year, Kevin won his revenge. I didn't really want him to have his revenge. It was all about I was gonna get the title twice there. But that year, we released the Ignition Exchange, and that was a lot of fun. We got to show the Exchange in action, and Kevin kicked my butt because he pulled out that amazing tag history playback, and then he had to put that music video on his application, and that did it for me right there.

Kevin McClusky: It was a freeze-frame with Kent's head up in the big screen right here.

Travis Cox: It was great.

Kevin McClusky: And then, so if we take a look at the third year, we stepped it up a notch, and it really became the premier event in competitive SCADA. We had two teams that came in... I'm not joking. This is real. It's a thing. And both of those teams, Flexware and...

Travis Cox: You can't forget Vertech. Oh my gosh...

Kevin McClusky: Yeah, Vertech. Man. Flexware...

Travis Cox: Let's be fair, that was Team Kevin, Team Travis, still. I was the coach of Vertech. And what happened? I think we won that year. Oh, that's right.

Kevin McClusky: Flexware was Team Kevin, so I kind of ignored the other side of it, so I apologize. Flexware actually, they took home the crown... Or, Vertech took home the crown.

Travis Cox: They took home the crown.

Kevin McClusky: Flexware took home the crown for 45% of the vote.

Travis Cox: But we had a lot of fun that year, but today we get to unveil a new champion. I'm super excited about that. Keep this competition alive.

Kevin McClusky: Yeah.

Kent Melville: Absolutely. And a lot of people were like, "This is great for Flexware, great for Vertech," but there were so many people after that that said, "We want to participate in the Build-a-Thon. We want to compete." And so we were left with the difficult decision of how do we narrow down the playing field. How do we find our next two competitors? And so what we did is we went, and we created a series of challenges broken into the three rounds, and we asked Premier Integrators to submit applications. And we chose our top 20 submissions, and we had them compete in these rounds, and each round we eliminate people, and if you're curious what these challenges included, what they were, it had all kinds of stuff. So it had fixing a SQL script, it had going through and interacting with web APIs, and then it also had some more fun trivial things like it had Wordle built into it, it had Minesweeper, it had an image scrambler, all kinds of stuff. So, it was a lot of fun. If you wanna see if you have what it takes, we took that whole project, and we've made it publicly available. It's at, and so you and your teams can go and play through it at your leisure.

Kent Melville: There is a public leaderboard, so you can see who gets through the fastest. But we're down to two now. We had two teams that were able to finish the fastest through all three of those online round challenges, and we're gonna bring them out now, so everybody help me welcome. DMC and Roeslein & Associates.

Kent Melville: Alright. So to introduce you to these guys. First off, David Berno, thanks for being here. We got Nicoli Liedtke, and we've got Casimir Smith. They represent the DMC team. Over here, we've got Mitchell Leefers, Phillip Bourner, and Scott Cushman representing Roeslein & Associates. And Travis and Kevin, what do you guys think of our competitors this year?

Travis Cox: Man, I think we've got some two great teams over here. If you look at DMC. David, he can jumpstart a car in under 60 seconds. So we know he could build a project in two days easily.

Kent Melville: That is true. But yeah. Kevin, any thoughts about these guys?

Kevin McClusky: Well, our producers gave us a couple of fun facts here about some of the others, and actually, I've got one... If you take a look at Mitchell, and many of you in the audience may be able to relate to this, he has twin sons, so he can handle a lot of chaos.

Kent Melville: That's true. I can't even imagine. I've got two kids. Luckily they came three years apart. So, guys, what were your experiences going through these online challenges, all of the pressure of earning your spot here today?

Phillip Bourner: Just the variety of questions was super fun. Seeing everybody in our department being able to provide a different helping hand and getting us here. It's really more than just the three of us that got us up here it's the entire group.

Kent Melville: It takes a village.

Phillip Bourner: It does.

Kent Melville: Yeah. How about you guys? It was just you three, right? Nobody else got involved?

Casimir Smith: We'd like to think that our entire Zoom call full of people dotted around the country may have helped a little bit. Got to definitely learn some new skills, see some new interesting techniques there. I really liked seeing that in the Exchange resources.

Kent Melville: Awesome, yeah. And anybody have a challenge that they remember that was particularly fun or maybe just notable in some way?

Phillip Bourner: The Regex like little puzzle solve there.

Kent Melville: We did. We had a Regex crossword puzzle. As if Regex wasn't hard enough already. But yeah, thanks, Brad. You're new sales engineer probably, so be excited. He built that one for us. But yeah, and then one more question for you guys. You're here now as a team, you've been working together, but are you guys all from the same office, or are you guys... Have you worked together before? How about you guys, Roeslein?

Phillip Bourner: Yeah, we're all from the same office.

Kent Melville: Same office. So you guys came, you knew how to work together, you guys were ready. How about you guys?

Nicoli Liedtke: We're from three different offices. So we have San Diego, Houston, and Cincinnati represented. But also included in the initial challenges, we probably had 10-plus offices, kind of like helping us out on that Zoom call, too.

Kent Melville: Very nice. And remote work is now the norm, right? So, location doesn't matter. But some of you out there are pretty sharp, and you may have noticed there's three... Three people from each team. In past Build-a-Thons, we've had a single champion from different companies. And the changes to the Build-a-Thon don't stop there. The Build-a-Thon today is quite a bit different. And so... What was this year? What is the Build-a-Thon? It actually didn't start just now, it's been going on all week, and we wanna tell you about it. So what's worth noting is the Build-a-Thon started Monday morning. And so these two teams, they showed up at our offices, and they came, and up to this point how much did you guys know about what you were gonna be doing?

Mitchell Leefers: On Monday?

Kent Melville: On Monday.

Mitchell Leefers: Nothing.

Phillip Bourner: We knew when to be at the office.

Mitchell Leefers: Yeah.

Kent Melville: They knew nothing. They knew when to get there, yeah. That's it. And so they come, they just show up, and at that point they were given a project to complete over two days. And so they had build time on Monday, they had build time on Tuesday. Tuesday night, they were done. They had to stop touching the keywords. And then, today, during this event, they're gonna show off the projects they built, and they have to do a live demo showing some functionality. So, hopefully, the projects they built work and still work today, and you guys will be able to see that and judge which team you think was better. But that begs the question, what did they build? What was the challenge? And so, as we were thinking about the Build-a-Thon, in past years, the Build-a-Thon has been very focused on-screen design and the back end of that has always been simulated tags. And so while it's cool that we've shown you incredible screens, custom functionality, reusable Exchange resources, to truly be an Ignition maker you need to be able to do more than just design a screen. And so, with that, you need to be able to integrate it with a real industrial process.

Kent Melville: And so this year, we decided we needed a portable industrial process that we could give them to automate and that we could bring here and have them automate live before you guys. And in order to help us do that, we partnered with Opto 22. Opto 22 has been helping us for a long time with providing hardware for the Build-a-Thon since the very beginning. And so, with no further ado, I'd like Travis and Kevin, if you guys could come and show us what that automated process is all about and what Opto 22 has done for us.

Travis Cox: Absolutely. We're really excited about this one because this year, we actually show the full process of how we can build back-end and front-end with the real process. And so, to show you the process today that both teams got to work with the last couple of days, Kevin, let's give them a sneak peek here.

Travis Cox: So first and foremost, I'm gonna go through the panel and kinda describe what's there. But I would wanna give a really big shout-out to Opto 22 for helping us. They are the official sponsor of the Build-a-Thon now. And just real quick, I wanna bring out the people behind Opto 22 that made this happen. I wanna bring out Benson and Garrick, so everybody can... Give them a round of applause for all the work they've put in.

Travis Cox: Thank you.

Benson Hougland: Thank you.

Travis Cox: These guys spent a massive amount of time putting this panel together. I literally drew up a diagram and I said, “You gotta make this happen.” And they did.

Benson Hougland: We figured out a way.

Travis Cox:Alright, so we're gonna go through it here. Basically, we provided an EPIC controller. There are three ingredient vessels here on the top, they have temperature probes, and they have level indicators, and there are valves below each of those ingredient vessels that are gravity-fed into a mixing tank. And in that mixing tank, we've got temperature and level as well. Then from there, we can actually heat up that liquid. There's a three-way valve that can re-circulate that back into the mixing tank, get that heated, and then the final step would be to bring that over to that holding tank. What we did was say, “Look, we're gonna provide you the raw IO. We're not gonna automate this process. You gotta use Ignition to do all of that. And all we're gonna do is put protection to the PLC so that the pump doesn't run dry and that the tanks don't overflow, we don't want, of course, our carpets to get wet.” But that was the process. Really exciting to see what these teams are gonna be doing with it.

Kevin McClusky: These teams are starting completely from scratch, which is a little bit different than years past. So when Travis and I ended up doing everything that we did to compete against each other, and when the teams competed last year, they had a few months beforehand to build up Exchange resources to get ready for the competition. This is very different, it is completely sight-unseen until Monday morning.

Travis Cox: I wanna truly emphasize the fact that they had no prior knowledge whatsoever. Came in, we threw a challenge and rules and requirements, and they literally built an entire project in two days. Testament not only to their skill but to the ease of the Ignition platform.

Kent Melville: Absolutely.

Kent Melville: Before I let you guys sit back down. Wonder if you can tell us a little bit about... So you guys know, they came in Monday morning, we did a big reveal like this, and we gave them a long document with a list of requirements. And those are the requirements that they're gonna be judged on here. Can you tell us a little bit about what those requirements were that they were given, as far as what you were supposed to do when they're automating this panel?

Travis Cox: Yeah, absolutely, that's a good question. So, basically, as I said, we got raw IO. So we wanna automate the process. There's three distinct steps we want them to do. The first step is to empty the ingredients into that mixing tank, and they can't start the next phase until all of those are emptied. Only one can be empty at a time. And then from there, after all the amounts that we wanna bring down, based on a recipe... Of course, we have a recipe that determines how much of each of those liquid. Once it's in that tank, we want to then heat that liquid up to a desired amount. Again, based on what's in that recipe. That's the second step. And then from there, we're gonna then bring it over to that dump tank as the final. So, they had to build a system that not only creates recipe management, that does the back-end logic that handles all of that, they have to show all that live on a screen in HMI, they have to log all that process data, create alarms, 'cause there is an E-stop, that we may or may not press today, we'll see. And they have to then show the history of all the executions. And, literally, this is an entire project, guys, that they had to do.

Kevin McClusky: There were a couple of other things in there, like validation of recipes, make sure it doesn't go outside of different set points. And so we actually ended up with either three or four pages of rules, but that's a very nice summary right there.

Kent Melville: Perfect. Thanks, guys. So we presented that to the teams, and we let them go, we let them start building. And since you're not able to see that live today, of course we had a film crew that was filming them to capture their creative process, to see what they were thinking. I would like to show you that footage today. And so enjoy this video.

Mitchell Leefers: Yeah, initial impressions of the challenge. So it's gonna be a tough challenge to get everything completed in two days, but I think we're able to dissect it and kind of work on it in sections and focus on different parts.

Nicoli Liedtke: Overall, the challenge is, especially within the time crunch we're in, going to be quite a challenge. We're definitely having to prioritize what's most important. We're kind of building a system that actually accomplishes something that you might see out in the real world, but we're trying to do it in just two days.

Mitchell Leefers: So we're kind of focusing logic first, and then working into the screens, and then making sure that there's a good user interface for it.

Nicoli Liedtke: One of our focuses right now is any of the large challenges that we think aren't a must-have but maybe would really set us apart from Roeslein.

Mitchel Leefers: Really, the first step was getting a good structure down, and so making sure that we have a structure that we're able to manage and that works well for the project, for analytics, and for expandability as well, for adding recipes and adding other parameters. So yeah, I think the challenge with the database is making sure that we have the right structure. Because if you don't start out with a good structure, it's gonna get messy later on.

Nicoli Liedtke: What we're working through right now to make sure we accomplish everything we want to is that we've decided on the most core functionality that the project kind of necessitates. We're trying to finish the base core functionality as quickly as possible and leave as much time to make as many of the super cool things that we're looking to do happen.

Mitchel Leefers: The easy part of the challenge, I think, for us will be making it fun for the user because I think we're creative and, I think, that we understand how users like to interact with applications.

Nicoli Liedtke: DMC is gonna bring to the table some really unique elements that don't get showcased pretty often in sort of some PLC HMIs and maybe exist more so in the design world within web development, and that's some of the more flashy elements that we're hoping to showcase.

Kent Melville: Alright, well, Travis and Kevin, I'm here over here with these guys... What are your thoughts of their planning? You think, they're... We’re on a good starting point?

Kevin McClusky: Yeah, yeah, I definitely do. They ended up going through we saw the whiteboards, we saw the different planning steps that were there. I actually have a couple of questions for these guys though because we saw it over the whole evolution, so maybe starting with Roeslein, looking back at your younger naive selves from three days ago, is there anything that you see now that didn't end up really going according to plan, or did it end up working out about how you were hoping?

Mitchell Leefers: I think we made a good choice in the beginning of dividing and conquering, so we had someone to work on the logic, someone to work on the database, and someone to work on the screens, so I feel like we made a good choice from the get-go, maybe we could have spent less time on the logic if we had more than one person working on it, so maybe we could have had a little more help on the control side, but it all worked out.

Kevin McClusky: Okay.

Kent Melville: Confident. Happy with their decisions.

Kevin McClusky: And a question for DMC. Did you all agree on the initial strategy, or coming from different geographical locations, did you find that you had a little bit of maybe conflict, maybe not conflict, but things to work out in the initial stages of where you wanted to go and where you wanted to basically, take this thing, the features that you wanted to implement, the approach that you wanted to take?

David Berno: Definitely, yeah, I think that coming from different offices and different backgrounds and working within different industries, we brought a different set of experiences, especially in how we're working within the Ignition platform. So the biggest one for us was how we were going to handle the sequencing for our team. So that we had some initial back and forth on before settling on our solution.

Kevin McClusky: Great, great.

Kent Melville: Awesome. You feel good now though. You made peace, amongst each other.

DMC and Roeslein Members: Yeah.

Kent Melville: Yeah, good. But we had taken that footage pretty early on in day one, but we didn't just send the film crews home at that point. They kept building, and of course, we kept filming through that whole process, especially day two, we came and checked in to see how the teams were doing, making sure that they were on track, and we wanna show you that footage as well, so enjoy this next video.

Kent Melville: Well, guys, day two is underway. How are we feeling?

Casimir Smith: We got a lot of fun ideas, a lot of work left to do.

Kent Melville: Yeah. Percentage-wise, where do you think you're at? Functionality-wise.

Casimir Smith: Core functionality, I think we're sitting up at 80%, but all of our extra bits and pieces. I think we got a little bit more to go on there.

Kent Melville: Sure, sure. I don't know. It's the 80-20 rule, so that the first 80% is the easy part, right? The rest 20%... Yeah, no, it should be interesting, but yeah, your screens are really looking cool. I like that you guys got to highlight DMC loud and proud right on top, right?

David Berno: Exactly.

Kent Melville: Yesterday, you guys were talking about adding some bells and whistles, maybe even bringing some web design-type stuff. Have you guys been able to circle around to that yet?

Casimir Smith: So some of the interesting features, I'd say they don't look great right now 'cause their styles are still kind of on our back burner, but one kinda thoughts that we had was leveraging this idea of being able to drag different objects to make your own... Make your own dashboard using this new Split Container Component, which we're really excited about, and also leveraging the power of the view canvas, which I think is really cool. I haven't gotten to play with it too much, so the idea being that the user can then bring in their own screens or select from a pre-set that might make kind of a dashboard suited for a specific purpose. So give them the power to put whatever they want wherever they want, but then have that built-in functionality as well.

Kent Melville: I think you got something there.

Casimir Smith: It's something that we thought would really kind of pop and get people excited.

Kent Melville: Well, looks like you guys are well on your way, so I won't keep you waiting any more, but...

David Berno: Sure.

Kent Melville: Yeah, best of luck. And it's gonna be an exciting day.

Kent Melville: Hey guys, day two is under way. How are we feeling?

Roeslein Members: Good.

Kent Melville: Yeah, give me a percentage here of just the core functionality. How far along do you think you guys are?

Phillip Bourner: It's working.

Kent Melville: It's working?

Mitchell Leefers: Yeah.

Phillip Bourner: Now we gotta make it pretty.

Kent Melville: Now you gotta make it pretty. Okay, and so what does that mean by working? So you guys can run recipes of all words from HMI?

Phillip Bourner: We're just trying to tweak in some of the logic behind the scenes for some of our reporting tools right now.

Kent Melville: Gotcha. So out of curiosity. What did you guys end up doing for your logic engine for the sequencing? How are you handling that?

Phillip Bourner: So it's all in the Tag Browser with some tag scripts based on values of tags and stuff like that.

Kent Melville: Nice.

Kent Melville: So just the tags are maintaining the state and then you're right to the next tag...

Phillip Bourner: Tracking how much we've used...

Kent Melville: And you guys are confident. It all run smoothly, and you have fun working with the Opto 22 panel here, testing it out, and then seeing the research and everything.

Phillip Bourner: It's been great. It's been fun.

Mitchell Leefers: It's been lot of fun to work with it.

Kent Melville: Did you guys make any modifications to your plans or your project or anything, or everything kinda right on track still?

Mitchell Leefers: It definitely made us think more about visual components for sure and how things are gonna look on that giant screen, so it's definitely playing a part into the visual aspect of it, for sure.

Kent Melville: Nice. I see a dark background here. Are you thinking of going with kind of a dark theme here?

Mitchell Leefers: Yeah, we're thinking dark mode is the way to go.

Phillip Bourner: Get the dark going on, purples and greens and golds and stuff like that.

Kent Melville: Getting into the season huh, with Halloween right around the corner.

Roeslein Members: Yeah.

Kent Melville: Very nice.

Mitchell Leefers: I think the biggest challenge is making sure that it will translate on the stage and on to the presentation because that's gonna play such a big part in who actually wins this presentation and how the audience sees the project, so just trying to make sure that it all looks great.

Kent Melville: Yeah. It sounds exciting.

Mitchel Leefers: Definitely.

Kent Melville: Alright.

Phillip Bourner: We're excited.

Kent Melville: Alright, well, good luck guys.

Phillip Bourner: Thank you.

Roeslein Members: Yeah, thanks.

Kent Melville: And you'll have noticed you may have been frustrated. They talk about cool features or things, and then we didn't zoom in on their screens. We showed you partial corners or seen it from distance. That's all on purpose. We don't wanna steal the big reveal, but there are some really cool things that the teams have built, but Travis and Kevin, once again, I'm interested in your thoughts based on what we saw there. How'd the building go?

Travis Cox: Well, I gotta say, I definitely coming on the second day, we saw a lot of really great progress, some really cool features that are in those, but I also saw a lot of very sweaty foreheads. They were a little bit nervous there on that second day, getting towards the end, but I wanna know have you guys felt. Did you feel like the whole two days went by super slow, super fast? How is the experience overall? 'Cause I can tell you what it looked like from our side.

Mitchel Leefers: Yeah, so first day went by pretty slow. Second day, it feels like it didn't even happen. I mean, it went by so fast, so yeah, that second day went by quick, and when it got down to the last couple of hours, it was... It was go-time.

Travis Cox: And we came in at 4:45, almost at the end there, and so it's only a little bit left. How are things going? Like, “Get the hell out of the room!”

Kevin McClusky: They were still putting the spice in the gumbo.

Travis Cox: That's right. That's... So DMC, I got a question for you guys. How did you feel the? Having the Opto 22 panel. How did you guys feel that the hardware... How did it add? Did it add anything to the overall experience? Did you enjoy working with it?

Casimir Smith: I thought it was really great to be able to work with a physical skid here. It's nice that you might not be able to see it out here, but it's all water, just LEDs, so it's something we can reset easily, which made it really easy to work with while still giving us, these actual process values that I think added to the appeal of our solution quite a bit. Yeah.

Kent Melville: Awesome. Who is excited to see their actual full projects?

Kent Melville: Well, hurry up and wait. Because we're still talking about me, people. It would not be a Build-a-Thon...

Travis Cox: I might have forgot to say, do we see how amazing Kent looks here on stage?

Travis Cox: However, he does have a green jacket, not orange winner’s jacket.

Kent Melville: You know, I may be overcompensating 'cause to get an orange jacket, you have to win a Build-a-Thon, and I haven't competed yet, so who's interested in seeing Kent compete in the future here?

Travis Cox: Yeah.

Kent Melville: There we go. Kentertainment for the win. But yeah, no, I may be overcompensating. So I just thought fancy, plus Travis and Kevin, in their new roles, vacated their directorship. So as the new Director of Sales Engineering, I had to bring some class to the position that may have been missing in the past. Just saying. Really, the Build-a-Thon, we just have a lot of fun up here, as you know, and in the first year, I randomly sang on stage, and since then, music has been part of this for no reason at all, really, but we enjoy it, and we have another music video for you today. And so enjoy.

Arnell Ignacio’s children: Dad, what does Ignition do?

Arnell Ignacio: Well, kids, that's a really good question. Well, we do have a song for that.

[Song plays]

Kent Melville: That's my job. That's what I do. But yeah, hopefully, you enjoyed that from the IA Department of Funk, and we had a great time with you guys last night, so thanks for indulging us in our musical career fantasies, but now who's actually ready to see these projects? Yeah.

Kent Melville: Well, forget about it 'cause I have one more thing to talk about. We actually have another competition that we like to talk about here in the Build-a-Thon, and it is the Ignition Exchange Challenge. And so, as was talked about earlier, we introduced the Ignition Exchange at the second Build-a-Thon. For those who don't know, the Ignition Exchange is a free online repository that is community driven, meaning anybody can go and they can create exciting resources built on the Ignition platform and they can upload them for anyone to download and to use within their projects, and we just love that our community has stepped up and they have built cool things to put there. We were worried that Inductive Automation would have to really drive this, that we would have to be constantly building more and more resources to feed into this for people to see it being useful, and we do, to some extent, still create resources and put them up there for people to use, but we've been so impressed with our incredible community. We can't talk about it enough at this Ignition Community Conference here, but you guys have really submitted some incredible resources and your spirit of giving and sharing to make these public for free, for anybody's uses, is truly astounding. And we like to reward these people by highlighting them here at ICC, so every Exchange resource that goes up, it gets submitted to be part of an Exchange Challenge.

Kent Melville: And then we go, and we review the submissions, and we pick out our top three favorite that we think are really something special. And so we are... As I was waiting for slides to change here, they gave me the clicker. It's my job. Kent, stop waiting on yourself, but we're gonna announce that now, we're gonna announce these winners, and so first off, honorable mention. We have this Defect Pareto Chart by Justin with RoviSys, and this is an incredible resource, definitely worth mentioning. You guys should go check it out, but this is in Perspective, and it allows a defect to be selected and input and then allows for a date range selection and shows all recorded defects over that time range, both in a tabular manner as well as via Pareto charts. So really cool resource. The second one was uploaded by Jerry Huck, PCC Structurals, and this is an SCPI Instrument Interface API, and you can easily create an interface to talk to your SCPI standard commands for programmable instruments, enabled instruments here, but it provides sample working scripts with the UDT to send and receive SPCI language commands. So really cool here, you're gonna start to see a theme for the next few, so thank you, Jerry, for this one.

Kent Melville: Our next one is an Omron S8VK Power Supply Modbus Interface, also submitted by Jerry Huck from PCC Structurals, and these S8VK power supplies have a Modbus interface, and so he created a UDT that maps to that, uses our Modbus driver, has a Modbus driver settings, and a sample template screen. And also, this series of Omron power supplies are useful for powering and monitoring a control cabinet, control power from a central operations center, and the S8VK series comes with, once again, that Modbus TCP/IP interface and that UDT allows you to leverage all the different possible features in Ignition with regard to that. Those are the honorable mentions. On to this year's winners: in third place, we have Jerry Huck with PCC Structurals. Yeah, go, Jerry.

Kent Melville: This resource is an APC UPS Modbus Interface. APC manufactures hundreds of these different UPS models, most of which can be monitored real time using their Modbus interface that provide UDTs with this resource, bring out all those different features in Ignition, making it all available. 'Cause it's all tags now, and there's pre-built screens and everything to get in and use this, and you can see some of those sample screens there. And really, this third place represents more than just this one resource. We just really appreciate Jerry has equipment that he needs to talk to. It's Modbus, so you can't just auto-discover all the tags, right? So he goes, he figures out that structure, he builds out a UDT, builds out some screens, and instead of just saving that knowledge for himself, he goes and he puts it up on the Exchange, so that anybody else who has one of these devices can just go download this, immediately connect, have the UDTs there and already have some screens to view the status. And so that was one of our original dreams for the Exchange, was for people to go and create their own templates, their own UDTs, all these things for all different types of devices out there, 'cause we can't cover every edge case at Inductive Automation. But you guys are out there dealing with all kinds of stuff that you can share that knowledge on the Exchange. Makes everybody's lives better, so thank you, Jerry. Yeah.

Kent Melville: Second place, this is another cool story of sharing and stuff, but this is a Weather App that uses the Open Weather Maps (Direct Access API). And the name that goes along with this one is Arnaud from Ceratec. But it's not just Arnaud's name that we want to mention here. Another name you need to know is Greg Radcliff. So Greg had gone, and Greg created this weather app, but it was using Node-RED behind the scenes to collect weather information, and there was kind of a lot that went into it, and so to use it, you had to go set up Node-RED, and that worked really well for his environment. He shared that incredible mobile-responsive app and Arnaud goes on and he sees the great work that Greg did, and he says, "I wanna use that, but I want to swap out the backend. Instead of using Node-RED to go and collect the weather information, I want to tie that into the Open Weather Maps API." And so he did that. He swapped it out, and he took that Exchange resource, and he uploaded his version of it. And because all of Exchange resources go up under an open license, they're all shareable, they're... People can do that. They can go, they can download, they can improve upon resources, and they can re-submit them.

Kent Melville: And we think that that is an incredible thing to do. And if you now go on to the Exchange and you go to either Arnaud's version or Greg's version, they each individually updated their descriptions to point to each other's resources. And so nobody's trying to steal credit from anybody else, but they just are embodying the Exchange, and they are collaborating, and we just think that's incredible, so thank you, Arnaud, thank you, Greg.

Kent Melville: First place, congratulations to Ashwin from Axcend Automation. He made something called Track Now, which is a ticketing management system which is a flexible organizational tool. It allows you to consolidate various issues and requests coming from different sources into a centralized dashboard, and the system organizes, processes, and keeps track of customer issues from submission to resolution. And it allows you the ability to raise an updated ticket with relevant context, gives you a ticketing dashboard. That includes status-based categories, view details and a timeline of each ticket's life cycle, and more. And so this resource we wanted to highlight as first place here because we thought that this was a really complete solution. It's beautiful to look at, this design is great, it's feature-rich. And so please help me congratulate Ashwin for the incredible resource.

Kent Melville: Now, these people are all the winners, and they are receiving their rewards. Also, anybody who uploads something to the Exchange gets a t-shirt. And we try to invite them all into this Ignition Maker community. And so I'd like to bring out a couple of people from our team to show you these t-shirts, and so I don't know where they... Here they are. Thank you, guys. This is Brad. He's the Regex guy, so thanks, Brad. But Brad and Madiha, thank you for being here. And so let's share some T-shirts with the group. Go ahead... Well... Yeah, throw 'em out there. Who wants a T-shirt?

Kent Melville: Oh, up top. Oh, fall short. Stick to Regex. Alright. Well, thank you, Brad and Madiha. Alright, now, who is actually ready to see these projects in action?

Kent Melville: Alright. I was expecting, you know, boy who cried wolf thing, they'd be like no cheers, like, "I don't believe you. It's too late. You've lost our trust." But no, it really is time. And so for this, our teams are gonna be coming up here. They've got their projects on these computers, and they are going to go ahead and run an actual recipe now that is gonna be provided by one of our judges, and so you'll be able to see their project in action, you're gonna be able to see if they were able to complete all those requirements. Since there were like four pages of requirements, you don't know all of them, so Travis and Kevin are gonna be watching closely to make sure things are all met, and they'll clue you in if they see any gaps. So with that, first off, I'm not even on the right page here, we're gonna be starting with DMC, and so come on down. David is gonna be doing the demo today, and Travis, as their judge, take this away.

Travis Cox: Alright. Alright, let's do it.

Travis Cox: All right, now I get the fun part. I get to see if this works.

David Berno: Exactly.

Travis Cox: It's exciting. Alright, so here's what we want you to do. As we mentioned, we have the recipe management system that we want them to build and to have to execute this system. So what we want them to do now is add a new recipe in the system, so can we get their... DMC's application in the camera? So we did blow us up for guys, so you could see it working in action as it goes. Alright, so here's what we want you to do, we want you to put a recipe in, and with the first thing, we're gonna... I don't know if you labeled the red, green, and blue in terms of different things, but let's put a recipe in with the red being 110% and the green being 45%, and the blue being 30%.

David Berno: Alright, say that one more time. So red, which is cherry... So we're making candy today with our system, so.

Travis Cox: Alright.

David Berno: DMC stands for Dynamic Motion Control, but today we're the Dynamic Makers of Candy, so we're gonna start off with the cherry. So here...

Travis Cox: I like that. All right, I like that.

David Berno: This one's cherry. So what's our cherry?

Travis Cox: So our cherry is gonna be 110%.

David Berno: 110%. Oh man, that's over 100 though, so we won't let that go into our recipe.

Travis Cox: Oh look, he passed that first test.

David Berno: Yeah.

Travis Cox: Alright, so then let's actually do a real one. Let's do that one being at 45%.

David Berno: 45%. That's a good one.

Travis Cox: Let's make your green, which is your apple. Let's make that 30%.

David Berno: 30%. Alright.

Travis Cox: And let's put your blue at 15%.

David Berno: 15%. Alright, so we've got 45% of the cherry, 15% of the blue raspberry, and 30% of apple, and that is going to come out with a chocolate-covered colored syrup. It looks like we're here. So, this is the recipe, so I guess we'll call this one chocolate for our recipe name.

Travis Cox: And we'll heat it up, the one degree that you already have on there.

David Berno: Perfect.

Travis Cox: So we'll heat that liquid one degree.

David Berno: Sounds good.

Travis Cox: So we're gonna see three distinct processes happen.

David Berno: All right. So we're gonna go ahead and create this recipe. So as you can see on the left-hand side, so we're using a Split-View Container here. This is a new container that's come out in 8.1.18, so we're really excited to use that one for this. We're gonna go ahead and create this recipe, and we'll see it show up here at the top of our recipe list, a couple of other ones that we were testing with yesterday. So are we ready to see some chocolate get made?

Travis Cox: Let's run this thing.

David Berno: All right. So I'm gonna load this recipe here. Press the load button. We're gonna get a little preview of our recipe, what color liquid we're gonna end up with based on the percentages of red, green, and blue that are going to this recipe, and we are going to run it. So I'm gonna press run here. You'll see across the top here we've got... This is actually a single SVG image across the top here, showing the progress as we go throughout the process. From here, we've got our different tank levels, so we're filling up with cherry first. I'll dra-and-drop from the cherry side over to the right-hand side here. We're gonna get a little bit more of an in-depth view of what's happening with that cherry tank. So you'll see here we've got our live tank level, we're coming down to our setpoint here, we're getting closer. We've got our live trend here, so we have both the level and the temperature, so I can see, as the operator, we've got the level decreasing in this tank. Now we're gonna switch over to the green tank. So the green tank with our green apple, let's take a close look at that one over here, so we'll drag and drop again to get a little bit more...

Travis Cox: I see there's a red button over here. I wonder what this red button does.

David Berno: Oh, that's a good question. What does that one do? Oh, no, we've got an E-stop. We've got an E-stop active. That pauses the whole process. And at this point, we need to recover. So at this point, our chocolate is more of an orange color, so we're gonna continue that process from this point. So if you wanna release that E-stop. I will go ahead and resume our process here, so let's pick back up right where we left off there in the middle of the green apple flavor coming into our chocolate. So after that, we've moved on to our blue, and we've seen our levels decreasing again. We've got our mixed tank over here as well. We'll see this one. This is going the opposite direction. We've got our level coming up here, and our color is changing, so we're close to that chocolate color now at this point. So the next thing that we're gonna do here, now we're gonna start heating up our liquid up to our set point, so we've got our live temperature here. It's rising one degree, so we've got a few more seconds here for it to get up to temperature. While we're doing that, let's jump back and talk a little bit more about our SVG up here. So like I mentioned, this is one single image that we're using scripting in order to change the image itself.

David Berno: So for those of you that saw the Technical Keynote, today we're really excited to use that new drawing editor that's coming out soon. This would have made that a lot easier for us here. The other thing that we're using is our Split Container with the drag-and-drop, so this is using a view canvas along the bottom, dragging and dropping our different views over here. You'll see an animated image of the valve changing over here, and we'll go into our dump tank looking at that filling up over here as well. As our run finishes, let's take a look at our run history. So these are all the different runs that we've done. So this is our run from today, so this is all built on a PostgreSQL backend. Here, this is showing our chocolate recipe that we just ran, when it was started, and who executed it. This can be filtered based on the user, so the recipes that the different ones of us ran, so right now, just DMC has been running these different recipes. We'll see here as it completes another event come in, so we've got our start coming in here, and we'll get a complete event as well showing the runtime once the pump has completed.

David Berno: We can also filter this by mints or by chocolate, and as the process completes, we'll also see all of our historized values, so now that we've started and completed, we've got our custom-built trends over here looking at tag historical data for things, so right now we'll look at the tank levels. This matches up with what we just saw. We saw the red tank go first. That's our cherry color. We've got our green tank next dropping down. We'll see that pause in the middle where the E-stop was pressed, and the level was constant. The blue comes up next with the blue raspberry.

David Berno: If we wanted to take a look at tank temperatures, we could check out that as well. They all stayed relatively constant throughout this process, and the commands over different valves as well back here. So we can also take a look at the alarm history here from the bottom, so we'll see that we had an emergency stop alarm pop-up throughout the process as well. So, going back to our recipes really briefly here, we can not only create a new recipe like what we did previously, but we can also edit recipes that are existing, so for example, if I wanted to edit the existing mints recipe, I could come in here, I could change different percentages, and if I wanted to maybe make an invalid recipe with nothing in it, I could do that and save the edits, and we could get a pop-up here, this is using an Exchange resource for pop-ups, giving us a save error, that it doesn't have any color amounts in it. So we can set this back, or we could even delete this recipe. If I don't wanna make any mints anymore, we could go ahead and delete mints, and we'll see that mints is no longer in our recipe here.

David Berno: So a couple of things that are going to hit the Exchange. After this presentation, we're gonna be sharing an example of how we did our custom SVG image creation at the top here with the scripting to change the colors as we went along. The backend of this is using the... The actual sequencing of this is using a Gateway timer script running Python code scripting for saving the states, or whole state machine is built within Ignition scripting and saving the state in the set of memory tags. We'll share an example of that, as well as an example of our drag-and-drop functionality, so dragging and dropping from our bottom navigation into here and showcasing the use of a split canvas home. That's what we were able to put together over the course of two days, so...

Travis Cox: Boy, let's give him a round applause for that one.

Kent Melville: Alright, David. Well, thank you. And so we're gonna go ahead and reset our panel here to get ready for the next demo here by Roeslein, but Travis and Kevin, what do you think of that project?

Kevin McClusky: Well, I think they really did put some spice in the gumbo.

Travis Cox: You keep on saying that. They did put the spice in the gumbo there, Kevin.It was a pretty impressive project there, I gotta say. I mean, guys, they did that in two days.

Kent Melville: 16 hours.

Travis Cox: And they had no recollection whatsoever about even what we're gonna ask them to build, and they got the whole thing done. It's pretty impressive.

Kevin McClusky: Yeah, they didn't do it like Travis and I did, where we stayed up all night. We actually kicked 'em out of the offices where they were, so they couldn't pull all nighters and put all this together, and 16 hours for each of the engineers there, and that's what they were able to come up.

Kent Melville: It's pretty incredible. And yeah, I think, I just wanna highlight this research here. This is also... The Opto 22 guys are... They built a system to go and to rebalance the water for all these... So that these guys could run their recipes over and over the last few days. So once again, just extremely grateful for the Opto 22 team for really making a first-class solution here. But were there any features in that project that really stood out to you guys?

Kevin McClusky: Well, I thought the drag-and-drop is a really nice feature. The fact that they're publishing this bout to the Exchange afterward to share with the community is really great. And the split pane was another thing that I saw there too, that not a lot of folks have used because it's brand new.

Travis Cox: Well, it's brand new, right? Yeah.

Kevin McClusky: Yeah.

Kent Melville: Absolutely. So that project's gonna be tough to beat, but if there's anybody that could do it, it'd be Roeslein. So, Mitchell, come on down. And yeah, shout out for them.

Kent Melville: And Kevin, see if you can kick this thing off as their judge.

Kevin McClusky: All right. So you were able to see what the other team just did. Yeah, do you wanna bring up your project right here? And I'm going to be doing the same thing as Travis, make sure that you didn't violate any rules and end up in the “Travis Cox penalty zone” that's over there next to the stage. I know you didn't know about that. They just added it to the end of the... The producers, they put it on there. It's the “Kevin McClusky winner circle” and the “Travis Cox penalty zone” over there.

Travis Cox: Got you, got you. All right.

Kevin McClusky: So what you're gonna be doing is go ahead, and for the red tank... So I see you've got your ingredients up here, go ahead and put in, you're gonna be really surprised about this, 110.

Mitchell Leefers: 110. It just won't let you do it.

Kevin McClusky: All right. And it comes up with a little red overlay there.

Mitchell Leefers: Yes, it does. Yeah, it can do that.

Kevin McClusky: All right, revert it back. Alright. And then let's see. Surprise numbers here as well, 45 for red. A little drag-and-drop there.

Mitchell Leefers: Or you can enter, right?

Kevin McClusky: Oh and typing? Okay, both of them?

Mitchell Leefers: Yeah, yeah.

56:11 Kevin McClusky: Green, we're gonna do 30. And then for the last one, for the blue, 15.

Mitchell Leefers: 15. Perfect. Do we have a temperature change on here?

Kevin McClusky: Temperature change is going to be one degree.

Mitchell Leefers One. Perfect. And did you wanna name... We're making potions here, by the way, so did you wanna name your potion or any of the ingredients in there?

Kevin McClusky: Oh name my potion.

Mitchell Leefers: We also do have a...

Kevin McClusky: Let's do the love potion, number nine.

Mitchell Leefers: Perfect.

Kevin McClusky: Love potion, I'll take it. Yeah.

Mitchell Leefers: So we'll put some love.

Kevin McClusky: Yeah.

Mitchell Leefers: Hearts, and we'll put a little bit of Kevin in there.

Kevin McClusky: They have my vote. Alright, go ahead and kick it off.

Mitchell Leefers: Alright, awesome. Now that we have all the parameters entered in here, we can add it to our list of available potions, so puts it there at the bottom for us.

Kevin McClusky: Fantastic.

Mitchell Leefers: And if we want to go over and run this potion, now we can head over to brewing. Oh, I have to turn on OPC connections.

Kevin McClusky: Oh alright.

Travis Cox: Don't worry. This was not a part... We had both of them up here connected to the same controller. We did tell one of them has gotta be disconnected while the other's running, so we don't affect each other. So let them get that fixed here.

Kevin McClusky: Yeah, so this is not anything to dock them any points as you're voting, this is just part of switching over between the systems here.

Mitchell Leefers: Alright, now we're good to go.

Kevin McClusky: Alright.

Mitchell Leefers: Everything is in here. We've got our new love potion number nine here. We can select it, gives us all of our ingredients, and we can run it. So while that potion is running, we have some nice visuals here using the Piping Components, and it shows you which container is emptying into the mixing vessel right now, and I think it's important to note on this mixing vessel, we're not just throwing RGB values into that mixing vessel. We're actually calculating the correct RGB value proportionate to how much of that color of liquid is in the mixing vessel, so as we move from red to green, when the green starts moving into the mixing vessel, it starts to turn a little bit orange and then yellow, and then same with the blue, as it adds the blue, it will finally turn into the actual color of the potion. That was a fun feature that we wanted to put in here. Are you going to pause this, Kevin?

Kevin McClusky: Anxiously waiting.

Mitchell Leefers: We do have an E-stop button that, if it's pressed, it'll...

Kevin McClusky: It could be pressed at any time.

Mitchell Leefers: It could be pressed at any time, and it will stop the process.

Mitchell Leefers: The E-stop has been pressed. So we can see E-stop is active. We can see that anywhere in the project 'cause we have it here on the side menu too, so that you do know the E-stop is active, and if you try to resume the procedure while it's active, it won't let you. And if we de-press the E-stop button, our alarms will go away. The process won't resume until somebody comes over here and physically resumes the process. So now we have that process running again, we can dive into some analytics and check out what's going on with the data from this process. So our analytics screen starts off with a nice fresh start here, and these are all of the batches that have ran, most recent one down here at the bottom that's running right now. You can click on it and it brings up all of the different parameters that are in there in the system here, and so you can track any of those if you wanna look at this crazy chart with all of these lines on it.

Mitchell Leefers: That's wonderful, but we also put some focus levels in there, so you can focus on tank levels, focus on just the valves, or you can enable everything, or if you want to disable everything and add one tag at a time, and you can do that as well. To make it a little more customizable, so you can really drill down into your process and see what's going on, and you can also filter these batches by user or by the type of recipe, so if we do both of those so that one hasn't been ran by W Adams yet, so we can then click any of these and we can do the same thing with all the history here. We like to make these menus expandable on the analytics screen because a lot of the times people want a big chart to look at, so by having these expandable menus on the side, it really, it allows someone to make a big chart and really see what's going on rather than try and look at a small screen. And back to the journal, I wanna just point out, we wanted to make this fun name changer that just kind of algorithmically puts together some fun words so that you can create your potion names, and then you can also create all your ingredient names to match your name that it gives you. So just a little bit of a user interaction that we wanna keep... That we wanna put in the project so that people want to use the project. And now you can see we're dumping, and with that, that's the application that we put together, so thank you guys for listening and watching. Oh, what else?

Kevin McClusky: Alright, and yeah, can we... We actually had a chance to see with the previous team the one degree increase there. Could you bring up the charts there?

Mitchell Leefers: Oh sure. Certainly. Yeah.

Kevin McClusky: Just to verify, make sure that everything is solid. Nice analytics there, so should be able to just bring that up and see that degree go from one to the next.

Mitchell Leefers: So we want the mixing vessel temperature. So, you can see the one degree here from...

Travis Cox: That's from 0.2...

Travis Cox: From 0.2 to 1.2.

Kevin McClusky: Alright. 0.2 to 1.2, which is a one-degree increase over that period of time. Excellent. Alright, I think we've got everything. So thank you so much for your presentation.

Kent Melville: So next time you're working on a project, just know that this is what you can do in two days, so you can use that as your benchmark, all future projects. Now, with these two teams really brought it. It's incredible. We're gonna be doing voting in a second. We're gonna be voting using the ICC app, and so if you can pull out your phone, start pulling up that app, that would be useful. While you're pulling that out, Travis and Kevin, another great project, what were the highlights in your minds?

Travis Cox: Well, I definitely saw a few things that were pretty cool in that project. I like that dark theme. Really nice. You look at that HMI, showed the color changing there with the liquid on screen and in the direction of that liquid. I also thought it was just a nice touch with that tank where you can actually use a slider instead of just putting the value in there, you just need to turn off that reject updates during edit while it's in focus, but it was very, very impressive all the way around, and the docks were pretty cool, I thought too.

Kevin McClusky: Yeah, yeah, I really like the ability to expand that out. I know when I'm working with the process, having something big in front and center and being able to see the full chart on the screen, that was a nice touch to me.

Travis Cox: Yeah.

Kent Melville: Awesome, well, Travis and Kevin can give you their opinions from the peanut gallery, but the decision is up to you who you want to be the winner, and so what you're gonna be doing is you're gonna be going into the ICC app. You're gonna be going to schedule... You're gonna scroll... You're gonna make sure you're on today, Wednesday, it should go there by default, I believe, but you're gonna scroll all the way to the bottom, and you're gonna find the Build-a-Thon session, the one you're in right now. You're gonna scroll to the bottom of that session, and you're gonna see a poll. And that poll is gonna be allowing you to vote for either DMC or Roeslein & Associates, and so take a few minutes here to vote, but while you guys are in their voting, Travis and Kevin, any additional thoughts or questions for these competitors, as we kinda wrap things up here?

Kevin McClusky: I was really happy that both of them stayed out of the “Travis Cox penalty zone.”

Travis Cox: Yeah, both of those projects were really, really great, it was fun to watch them through the journey and to basically see the final product that was built, and you can't get two better projects than these two you saw here. Pretty amazing.

Kevin McClusky: When you're starting out from scratch, you're building something over the course of that time. You don't have a chance to build your own Exchange resources beforehand that you can pull in live. These were almost 100% from scratch for everything that we saw here, so it's a testament to these engineers' skills and ability.

Kent Melville: It really is. And how are you guys feeling right now?

Phillip Bourner: That's good. Glad to be over.

Mitchell Leefers: Yeah.

Kent Melville: Glad to be over. Yeah. As you kinda saw each other here, does this bring you guys together, or is this just ramping up the competition between the companies?

Phillip Bourner: It brings us... It's good to know other companies are using the software and getting a good name for Ignition as a whole, not just the individual integrators or stuff like that. So we build off each other as a community.

Kent Melville: Absolutely. Well, we're glad to hear that. But that's the answer. That is the official answer. Yeah, we want the camaraderie, we want the spirit of the sharing, but as you guys saw each other's projects, any kind of last comments about why yours was so superior?

Phillip Bourner: Dark mode.

Kent Melville: Dark mode. The dark mode. We got.

Casimir Smith: Have you ever walked into a candy store with the lights off?

Kent Melville: That's a fair point. Fair point.

Travis Cox: Good point.

Kent Melville: I do like the Domino's tracker at the top. I order a lot of pizza, to know my candy is being made the same way, it was great, but when I was a kid, I did... My first on-stage music scene was karaoke of Love Potion Number Nine. So maybe we'll have to work that in in a future Build-a-Thon. Stay tuned. Put that on the ideas portal.

Kevin McClusky: Do you think it's fair to say that they both put the spice in the gumbo?

Kent Melville: Yes, Kevin. I think they did. I think they did both put the spice in the gumbo.

Kevin McClusky: Thank you.

Kent Melville: Everybody had a chance to vote? Yeah? Who is excited to see who is gonna be crowned the next champion? Yeah?

Kent Melville: Alright. Well, if you can help me count down... We're gonna count down from 10, and then we're gonna display the results up here. So are you ready? Ten, nine, eight, seven, six, five, four, three, two, one.

Kent Melville: Oh. Roeslein by three. By three votes. Come on down guys. Wow.

Kent Melville: By three votes.

Kent Melville: Incredible.

Kevin McClusky: Whoever said a single vote doesn't count? Right? A single vote counts.

Travis Cox: Thank you guys. Wow, man.

Kevin McClusky: Congratulations guys.

Travis Cox: Oh my gosh.

Kent Melville: Alright.

Travis Cox: Wow.

Kent Melville: It is now time for these gentlemen to receive their winner’s jackets, and so for that, we'd like to invite out our current reigning champions Vertech, so come out, Ryan... I thought they were right there. Ryan Crownover and Chris McLaughlin. There we go.

Kent Melville: So, go ahead. Guys are gonna be receiving your jackets here. You'll notice these jackets are slightly different than theirs, these are gonna be their placeholder jackets, but they are going to be getting custom embroidered jackets that have their names and the date that they won. Can you show off? You can see here. They've got their own names in their jackets, pretty fancy. I'm not bitter at all. But... Yeah, someday, someday. Alright.

Travis Cox: Well, let's give Kent a round of applause real quick. He's amazing.

Kent Melville: Alright. Guys, come up and get your jackets one at a time here.

Kent Melville: Well, everybody, thank you so much for coming to ICC this year. It's been super fun, and thank you for sticking around to the end for the Build-a-Thon. We like letting our hair down a little bit, we like playing, but also we like to highlight the incredible community we have. We like to highlight the incredible skills out there of our integrators, and DMC and Roeslein obviously represent that excellence and pursuit for really elevating the world of SCADA, IIoT MES, DataOps, all these things that we highlighted, these guys are really where the rubber meets the road, making all these things happen as are all of you, so thank you so much for your time and with that that's gonna conclude the conference. We hope you travel home safely. Hope you come again next year. But give it up one last time for Roeslein & Associates.

Announcer: That concludes the 2022 Ignition Community Conference and we'll see you next year.

Posted on October 18, 2022