Data Liberation Front: Liberate Industrial Data and Scale Digital Value

00:06
Speaker 1
Good morning, and welcome to the Element8 quarterly Data Liberation Front webinar. Thank you. For those online, I see there’s a good number of people online for a Friday morning. Your time is valuable. Thank you for joining us. We have some exciting new updates for you today. We’ve got a customer showcase from our friends at Systeco Automation. We’ll celebrate our top SI partners, at least then, for the final quarter of last year. And there are some really nice technology updates to look forward to. More than usual is there are a couple of big releases on the way. What is the Data Liberation Front? If you’re not familiar with what the Data Liberation Front is, we are element 8. But the Data Liberation Front is really a movement. It’s a community of like-minded men and women with a common purpose and passion for growing our industry.

01:00
Speaker 1
If you’re not familiar with element 8 at all, where I look at the names, I think everybody should know us. But maybe for the recording and for those that will look after, watch this afterwards. Element 8 is the proud distributor of Ignition universal industrial application platform, Sepasoft, MES and the Canary Data Historian. We exist to help ensure a flourishing future for Industry. Our guiding principles to achieve this is to humbly serve our community and the industry. To learn from others and share what we’ve learned and to provide intuitive and scalable technologies that break down the barriers of cost and complexity. That’s us, that’s eliminated. And with you today on this side, in this room here, my name is Jaco. I look after the team at Element8. We have Laura online. Laura, I assume you’re still with us. You can hear us?

01:51
Speaker 2
Hi, yes, I can’t see my video, unfortunately.

01:56
Speaker 1
Okay, that’s. That’s unfortunate. I’d rather just.

01:59
Speaker 2
If you can fix it on your end. I would definitely say hi to everyone.

02:06
Speaker 1
That would be cool. We’ll check that out.

02:08
Speaker 2
Thank you.

02:10
Speaker 1
Laura is from Cape Town, and our customer success lead, right across from me is Gary Lowenstein.

02:15
Speaker 3
Hi, good morning everybody.

02:16
Speaker 1
He is our Sales Engineer and then really our guest presenter today. Our guest upon that last but not least is Clarice van Rooyen, the assistant manager at Systeco Automation who’s going to take us through their success story which is a really impressive body of work and application that they did for a customer in Australia. Therese. Good morning.

02:41
Speaker 4
Good morning. How are you?

02:43
Speaker 1
Thank you for joining us, Clarice. Well unfortunately, you the star of the show and you’re up last so you’ll have to listen to us Waffle for a Couple of minutes first.

02:53
Speaker 4
It’s okay, no problem.

02:55
Speaker 1
Cool. All right. Somebody else in the room with us today is Luan. Luan Tata, who’s our marketing lead started with us. When was it? 1st of 3rd of January, 6th of January. You even got a couple of extra days in January. We’ve got some new team members that joined us at the beginning of this year. Luan looks after all of our marketing, branding, design, and event kind of initiatives. Then we have Katlego Gagoopane. I’m just going to say Scada Cat. I like Scada Cat and it stuck. As well as Jaco Sadler. Jaco is not the OG Jaco. There’s only one OG Jaco, but there’s another Jaco Sadler, and both he and Kat joined Laura’s team as customer success engineers. And we’re really grateful to be bringing in new people into the business, especially young people.

03:52
Speaker 1
So welcome to these, these three gentlemen that have joined us at the beginning of January. The circle is growing. All right, so what do we have in store for you today? We’ve got, as always, we’ve got some community news. We will look at the Cirrus link MQTT Unified Namespace Update. That’s a very big mouthful. We’ll explain a little bit more about that when we get to it. We will introduce you very briefly to a new offering called Sepa IQ by Sepasoft that we’re really excited about. We’re going to take a quick peek at the new Ignition industry packs. There’s two of them. Really, really nice, comprehensive resource that’s available free. We’re going to look at Ignition and Canary updates, the typical product updates that we have and we will jump straight into the customer showcase with Clarice and Systeco Automation.

04:48
Speaker 1
So that’s the agenda for today. Anything I’m missing, Gary?

04:51
Speaker 3
No, I don’t think so.

04:52
Speaker 1
No. All right, as always, we’ll kick off with who’s new. Welcome to new friends and new customers who joined us over the last three months. I could probably quickly mention all of them. Agri Technovation, Courier IT, Danone, FCT Water Board Abuja Nigeria, Kellanova, Lundin Gold, Makana Brick, mpact, Nutrisek, Pioneer Fishing Process Rack centre also in Nigeria. It’s nice to have a growing base and community in Nigeria. Shoprite, Sibanye Stillwater, Siza Water, Take 5, Thaba Joint Venture, and a couple of local municipalities. I’m hoping that’s pronounced correctly. Turnkey, Modular and Unilever. Welcome to some new Faces in our community. New customers over the last three months, new partner certifications. We have Ignition certified. We’ve got a couple of new customers or new partners.

05:54
Speaker 1
We’ve got automatic for the people down in the Western Cape, Energy Auditing Services, Gass at Site, all in the Western Cape in control from Seychelles, Protomation Works and Ryan Mechatronics all became Ignition certified over the last three months. Four months essentially Gold certified. Green Row Solutions, well done to the guys there. Qualico Solutions, Zip Automations in Nigeria, all Gold certified. I think I hope we haven’t missed any new certifications over the last three months. And then, of course, from Qualico Solutions, also Canary certified. If we have missed a certification, I do apologize. Our last DLF was, geez, I think it was around July, August last year. So there may have been a couple of certifications that we’ve missed.

06:47
Speaker 1
If you want to learn more about the certification program, how to become certified, the training, the enablement, the journey to do that and how to reach the level of certification, please reach out to Clarice Rautenbach, our channel partner lead. Clarice will be happy to take you through those steps and guide you through the process. You can also scan the QR code. All these QR codes have been tested. It’s not the same one. So you’re welcome to point your phone at the screen and follow the QR code as well to the partner page. We’re incredibly proud to Highlight our top 10 selling system integrators. So each integrator’s ranking on this leaderboard is based on their total sales for the quarter, which would have been our final quarter of last year. October to December.

07:35
Speaker 1
We’re already halfway through this quarter, but for now, we can at least do a tally and a recognition of the final quarter of last year. These are the real heroes in our community, the people that do the hard work. We’ve got the easy jobs; these people have the difficult tasks and challenges, Francis and the real brains trust. But let’s look at the top team closing out 2024. We’ll start with the bottom half. Number 10 Integ, Iritron, Devcotech, Darner Engineering and Control Software Solutions. And then, our top five, we have VisiPraxis number five, Vennic are fourth, Afrilek third, Advansys number two. And our top-selling system integrator for the final quarter of last year was Concera. So congratulations to Rolf and the team and everybody.

08:26
Speaker 1
I don’t think the objective is always to be in the top 10, but the objective is certainly to serve your customers as best as you can. we’ve got some regulars that reach in the top 10. Well done to everybody. Really proud of you guys. Really happy to have you in our community, and we look forward to see what the first quarter of this year is going to look like as far as the top system ratings go. Upcoming training is obviously a very big part of enablement and making sure that you are enabled and trained to make sure the software serves you. We’ve got Canary training the first week of March. I believe there are eight or nine or 10 people. We can accommodate 10 on that one. Ignition perspective down Durban. I know, Laura, that perspective is really in demand at the moment.

09:16
Speaker 1
We have spoken about adding a second perspective date before May. We will hopefully confirm that over the next couple of days next week.

09:27
Speaker 2
It will be virtual, so anyone can join.

09:29
Speaker 1
That one will be virtual. Yeah, we’ve got Ignition Advanced right at the end of March, which is, of course, database scripting. And then we have another Ignition call early in May, and naturally, there are a couple of others, but we’ll leave it there until the middle of May. For now, scan the QR code again to follow the link for the training page and we will confirm that second perspective date fairly soon. All right, let’s kick off with the updates. There was enough of the waffle. Let’s get straight into what is new and what has been released over the last couple of months. We celebrated Christmas since the last time we spoke. A lot has happened not only with business but also in South Africa. But let’s focus on the technology and understand what is new and what’s been added since then.

10:22
Speaker 1
So, Ignition MQTT modules, if you’re not familiar with MQTT, we’re not going to cover that now. That’s a topic for another day. But we do want to focus on what functionality has been added to these MQTT modules that enables, and builds and essentially transmits the UNS natively inside of these MQTT modules. So what is the Unified Namespace? Very briefly, just for context, the Unified Namespace is the architectural foundation of successful digital transformation initiatives because it enables you to make data accessible from your entire enterprise to a single database. Typically, I’ve been speaking about a broker-centric architecture, but more specifically, UNS is a standardized way to organize and name data, and it contains an enterprise structure and events in one communication interface.

11:20
Speaker 1
So I think the important bit to read out of those two very long sentences is that the UNS is essentially a real-time single source of truths for data in your operations and environment that is semantic. Semantic. And it aligns with the physical plant environment. It’s open and accessible to other people, other systems, and other software, both bidirectionally. The unified namespace. We’ve spoken a lot about it over the last couple of really two years. It was coined by Walker Reynolds, of course, from Industry 4.0 Solutions. There is a very helpful guide that you can download from Inductive Automation that talks through the UNs with some key concepts. But it is certainly very much an approach and a philosophy that is worth understanding. But why is this relevant to the new MQTT functionality?

12:19
Speaker 1
We do speak about ISA 95 part 2, specifically hierarchy, as it pertains to your physical plant environment. Meaning that we want your data that lives inside of your unified namespace to represent the same physical environment, to be a true reflection of where the data is not only originating from, but where the data is being essentially gathered from. Yeah. Do we leave it at that? ISA95 part 2 hierarchy?

12:51
Speaker 3
I think that’s, that’s enough for that.

12:53
Speaker 1
Okay, cool. All right, so what has been added to the new MQTT engine? Specifically, the MQTT engine and MQTT transmission modules. I think it’s the latest, this version 4026, if I’m not mistaken. Maybe. Gary, do you want to take us through what’s been added? Yeah.

13:10
Speaker 3
So when you’re building out a unified namespace for UNS, and you have multiple devices or nodes out of the edge, from a central perspective, your MQTT engine connects to your MQTT broker, and it listens for remote spark load clients that are publishing into Ignition. So, in this example here, I’ve got Edge Node One, Edge Node Two, and Edge Node One is Artifactory One, and it’s got Station One and Station Two. But what you’ll notice is station two is serviced by two different edge nodes. When I publish all of that into Spark Plug, I get the Spark Plug view of it and we have the print drip, the edge, the device, and all of the folder structure within that device. Now, when we pass data from OT to IT, we actually want to get it into a structure or into a fashion that matches the enterprise.

14:10
Speaker 3
In other words, we’d like to get it back into something like the ISA95 structure that’s really new, or the new MQTT engine that’s available from Cirrus-Link or Part and Parcel of Ignition comes into play.

14:27
Speaker 1
Are you able to show us some of that? I think that’s probably the best part.

14:30
Speaker 3
I can do some of that. Let me see if I’m going to share my screen.

14:37
Speaker 1
This is a live demo. Always dangerous.

14:39
Speaker 3
Yeah, Always dangerous. Always very dangerous. So am I sharing? No.

14:47
Speaker 1
Yeah.

14:50
Speaker 2
Yeah, you’re sharing. We can see the gateway currently.

14:54
Speaker 1
Yeah.

14:55
Speaker 3
So now I’m looking at my central gateway here. I’ve got an ignition MQTT engine configured here. And in the MQTT engine, all that I’m going to change is I’m going to go down to my Spark Plug message and I’ve got things that are hidden behind. There we go. I’m going to go down to my Spark Track B, and in the Spark Track B configuration, I have this new checkbox which says UNS enable MQTT engine tags in a specific folder. And I’ve just said I want to enable that into MQTT. One of the questions that you may ask that’s going to come, I’m sure, is that by doing this, am I not going to double up the amount of tags that I’m publishing into my engine? The answer is yes, but I can always just disable the default tags inside of that before I save those changes.

15:56
Speaker 3
I just want to go and show you what I’ve actually got configured here. I’ve got my central gateway, I’ve got Edge Node one and Edge Node two, and as I said earlier, I’ve got Edge Node one, which has got Station one and Station two and only part of Station two. And in Edge Node Two, I’ve got Station Two at Station Three. If I look and see what it publishes for me, I can see that it publishes our Edge Node one with all the device structures and then the folders underneath it. And exactly the same for edge node 2. Now, this is really not what we want. We want all of that stitched into a single view. So the first thing I’m going to do is I’m just going to go and enable these UNS tags on my MQTT engine.

16:50
Speaker 3
I’ve specified my folder prefix of UNS and we’ll see where that comes in a second. Then I save those changes. Now I’m going to go across to my MQTT transmission module on my Edge Node one. If I go and look at this, there’s no special configuration that I’ve done here. I’ve given it a name, I’m going to enable this transmitter, I’ve given it a tag provider. I can give it a tag path or not if I want to. I’m not converting the UDTs to tags. I’m leaving them as is; I want to publish them. One very important thing is if I’m using UDTs, all of these UDTs on my edge nodes must be the same. They must be the same UDTs. I haven’t got history enabled for this one. I’ve then got my standard Spark Plug settings.

17:45
Speaker 3
I’ve got a view of Enterprise, my Edge Node ID and my Device ID, and I’m going to save those changes. And straight away in my engine settings I can see that I now have a new folder called edge node1 with what I’ve enabled from node1, I’m now going to go to get this out of the way, my edge Node two and I’m going to do exactly the same on Edge Node two. I’m going to go down to my MQTT transmission module, I’m going to go to my transmitter, I’m going to enable it slightly different, well, exactly the same settings. I’ve just given it a unique name. My data provider is different. All of the other settings are the same. As I said, it is very important that the UDTs must be the same.

18:41
Speaker 3
Save my changes and what’s going to happen is immediately you see that Station 3 has popped in and it stitched it all together. Everything that I had under station 2 for each node 2 is now stitched into that section that I had. Now, what else is very nice is I can go and say, well, I’ve got some functionality that would typically not live in the edge, so I want to go and create some aggregates or some totals or things like that. So I’ve gone and done some little scripting in the background and I’ve got some tags that I’ve created for each station here, total usage. I want to stitch those tags back into the same units. Well, it’s exactly the same principle. I’ve got the same kind of structure defined, or I’ve got the same structure defined as I have in my edge nodes.

19:35
Speaker 3
Same principle. I go to my central gateway, I go to my MQTT transmission; I’m going to go and enable that transmitter and save those changes. And if I go back to my MQTT engine to UNS, you’ll see now that it’s stitched those statistics tags or those usage tags that I’ve created back into that structure. And I think this is such a nice feature to have for anybody that’s using MQTT, you already have this. It’s part and parcel of the latest releases of the engine and transmission modules.

20:26
Speaker 1
Fantastic. Really, really.

20:28
Speaker 3
I think it’s very conscious. It’s an absolute game-changer. It makes life so much easier. If I had to do this in the past, I could have done it with reference tags, but it absolutely would have taken a lot of work, and every time something changed, I would have to go and change it manually. This really makes my life so much easier.

20:44
Speaker 1
It would have been a significant engineering lift. That’s true. Very, very nice. So that is A version 4026, I think is the latest of the MQTT margins that. Thanks, Gavin. That was very brave to do a live demo as well.

21:03
Speaker 3
Oh, be brave.

21:09
Speaker 1
All right. I think my screen is back up. Should be.

21:13
Speaker 2
Yes, fantastic.

21:16
Speaker 1
Right, so that is all about the new MQTT UNS functionality. We’re just going to call it that, the UNS functionality Sepa IQ. So we’re really excited about. Oh, by the way, if you have any questions, please ask in the chat. We do monitor the Q and A. We usually have a couple of good questions. If anybody do have any questions, please type away, and we’ll answer them live as we go along, if we can. If we have the capability to answer them. There’s no need for formalities to keep it to the end. Please let us know if you have any questions. So, SEPA IQ. We’re really excited about SEPA IQ. It is, as we mentioned, Sepasoft’s latest offering. We’d like to be the first to announce it, but it was announced at the Ignition Community Conference last year in Folsom in September.

22:09
Speaker 1
Based on the discussions that we’ve had with many of you, it does seem like you know about Sepa IQ, which is good. And there’s also a good understanding that it is a complete manufacturing analysis or analytics solution. We often hear about AI and machine learning and all of these other two and three-letter digitization acronyms. But before we can realize the value of those things, we need to understand why data-driven is a key concept, and that’s really why we’re excited about Sepa IQ. So maybe just very briefly, why data-driven manufacturing, let’s look at, for example, optimizing operations. So by analysing data you can identify the inefficiencies in your process, reduce downtime, improve productivity, optimize resource allocation. All of those things lead to cost savings and higher profitability. Then we’ve got predictive maintenance, quality control, inventory management, and supply chain optimization.

23:10
Speaker 1
All are very reliant on cleansed, contextualized data. All of those things obviously eventually mean competitive advantage, being able to innovate more effectively and respond faster to market changes. So that’s a little bit about why Data Driven I think we can all agree about the importance of contextualizing cleanse data as a foundation for solving problems. But what is needed to leverage AI and machine learning tools? Gaining insights from these tools and these available offerings that are typically very expensive is only as good as the data that is fed into its learning algorithms and into its learning. So the cleaner the data better. So that’s the old saying about garbage in, garbage out. We are right at the point where AI knows what to do with all of this data.

24:06
Speaker 1
Creating the models still requires guidance or guidance by someone with domain knowledge, expertise, industry experience, and, in most cases, data science knowledge as well. When it comes to MES data contextualization is vital. So the general rule of thumb is that These tasks take 85% of the effort to implement and maintain an AI solution. Why hasn’t anybody assumed that the data is cleansed, contextualized, and available? Why hasn’t everybody felt that AI is manufactured yet? And there’s a. There’s a couple of really good research pieces about this, but we are still very much in the hype curve of this new technology. Up until now, I think the general consensus with a lot of people has been let’s collect all of our data and we’ll figure out what to do with it later.

25:00
Speaker 1
You know, let’s just gather any and all and figure out what to do with it later. And too often today the existing solutions that we see in this space are typically very overpriced for manufacturing, specifically for our industry. And then the change of data. Data needs to change both input and output. It needs to be bidirectional with the context. Simply collecting it and storing it somewhere centrally, whether that be a data lake or a cloud, is not enough. It does need to be actionable and bidirectional. How do you incorporate your new manufacturing director’s favourite KPIs as an example? Have you invested in a tool that can do that? It is an expensive technology, so Sepa IQ is not our announcement, but maybe just to understand a little bit of the fundamentals of what it is.

25:56
Speaker 1
It is a complete manufacturing analytics solution that unifies and contextualizes production data, which allows you to strengthen the effectiveness of your AI and ML business intelligence tools. It specifically breaks down two barriers. One of the biggest barriers we’ve seen with most of these solutions is performance. It has to be lightning-fast to keep up with the data demands of our modern systems and structures. It’s got to be scalable. Its Sepa IQ is cloud or on-premise. There is load balancing through server clusters, and SEPA IQ is very important and complements the existing Sepasoft MES offering but does not replace the production control features of the modules that you use today. Whether that’s OEE or batch and track and trace, it complements it does not replace it. So Sepa IQ connectivity is really the heart of Sepa IQ.

26:55
Speaker 1
It’s designed to stream data from diverse sources such as your SCADA, MES, unmanaged or unmanned databases. Supporting protocols. There are a few MQTT, Kafka, Restful, API, Ignition 8.3 and many more to follow. Some of the Data challenges: yes, Sepa IQ does allow you to cleanse, transform and contextualize production data without reducing the need to do data governance and data preparation or massaging manually. Some of the analysis features include built-in OEE and SPC calculations or calculators. You can obviously create your custom calculations of JavaScript Real-time predictions based on your own production data sentiment. You can also do sentiment tracking real time analytics. That’s all part of the very powerful analysis capability of Sepa IQ. And then finally sharing the communication flexibility that you typically have with SEPA IQ for receiving data is equally available for transmitting the data.

28:10
Speaker 1
Equally as important to connect to those data syncs your higher level BI and naturally your other AI systems that you have available. Sepa IQ does support connectivity for a variety of data sources and syncs. So that’s the in, the analytics and the out essentially. So, the takeaway is that this is just a teaser. The demo requests were live this week. I think right now you can schedule a demo with the Sepasoft team. Sepa IQ is a complete manufacturing analytics solution that we’re quite excited about. We’re also learning about a little bit more ourselves. SEPA IQ Premium is available right now. The demo request is available, and again, you do not require the Sepasoft MES modules right now with SEPA IQ Premium, but the later version that will Follow with Edition 8.3 will require those modules.

29:08
Speaker 1
But check it out, go to the website sepasoft.com or scan the QR code, and let us know what you think. We’d be happy to chat about it further. We’re quite excited about it, and we hope to be able to see a demo, at least show you a demo, in the very near future. Right, so that was Sepa IQ. Let’s start off with Ignition 8.3. What is the latest update on Ignition 8.3?

29:32
Speaker 2
Laura yeah, very exciting. Before I jump into that just. By the way, guys, we are aware that the chat was disabled but if you just refresh. I see we’ve already gotten a question in from Quintin, so maybe just check. Yeah, if. If there’s still a bit of an issue, guys. Yeah, I apologize. Maybe just play around with the chats and see if you can submit those. Those questions in for us. Right.

30:03
Speaker 1
Maybe we should ask for a question to see who’s. Who can test the chat?

30:06
Speaker 3
Quintin has put a question.

30:09
Speaker 1
Oh, yes. Quintin.

30:10
Speaker 3
What are the primary use cases and industries where Sepa IQ has shown the most impact?

30:15
Speaker 1
SEPA IQ is brand new. It was developed from the ground up. It is currently running successfully at a food and beverage enterprise customer in North America. The initial feedback. Yeah, Quinton, it’s very promising. It really takes a lot of time and cost-benefit. But that is literally their first customer. It is brand new technology. So it will be made public. The results will be made public. And that case study or that showcase, we will be able to share it. But SEPA IQ is not a regurgitation of another technology or a product that has existed. It was built from the ground up. Which is good in terms of references. Less exciting, Quinta, but a good question.

31:08
Speaker 2
There you go. Okay, so I see the questions are coming through the Q A section, not the chat section. So two different types.

31:14
Speaker 1
Yes, the chat is just for us.

31:18
Speaker 2
Okay. Internal. All right. Okay. But let me start off with Ignition 8.3. So, guys, inductive Automation has decided to update their schedule to target an early quarter two release. But that would be for the ignition 8.3 beta version. Now, the new timeline that they’ve given through to us is going to allow them to gather the highest quality of feedback during the beta phase, which will set the stage for Ignition 8.3 to provide. The idea is just a great user experience. And that would be for its final release, which will be later this year. So we understand that everyone is very eager to get their hands on it to test out new features. I mean, we are as well. So we do appreciate everyone’s patience. But they are working very hard to deliver the most powerful version of Ignition yet. So together with.

32:15
Speaker 1
I think we’d appreciate that, Laura. I think it is wise to do that. And then. Or making the private beta a little bit longer, I think will probably serve us well to do that. So, you know, in a couple of. In a year or two years’ time, we won’t remember that it was, you know, a few months late, but I think the User experience, quality or assurance is what they’re looking at by delay. So that’s okay.

32:40
Speaker 2
Yeah. Yes, exactly. I mean, I know they’ve gotten so much feedback during the initial beta version testing that they’ve decided to make that complete alpha. And so the beta is coming out again because they said they wanted to make the source code as close as possible to the final release as they possibly can let it run through a whole new cycle of testing. But some of the new features, I know a lot of you guys have heard of a few of the things that are coming out and a lot of the features have been like, you know, mentioned over and over again. But if you go and delve a little bit deeper into the feature notes, there’s some cool stuff that I think we should be highlighting as well.

33:25
Speaker 2
So there are about two things that might look familiar, but the rest are all little tidbits that I think need a bit more attention. So the first one is, of course, the redesigned Gateway web user interface. It’s got a lot of new capabilities. They’ve got like a whole video on it. But what excites me the most is it includes a fully functional built-in RESTful web API, which is open API compliant and fully documented. It’s amazing. So, yeah, that is, of course, one of the cool new capabilities of the Gateway. All of the current file systems that are used for configuration have been moved from using an internal database to a complete file system. So this will follow a logical hierarchy, meaning that it’s humanly readable. And so provides us with the capability to integrate with version control software like Git.

34:22
Speaker 2
And I know that’s been a big request as well. Then I think together with that’s something that is been highly anticipated is something called deployment modes that they’ve added. So this allows you to seamlessly move between development, staging and production modes all in one environment. So you can have one gateway set it up to have, for example, development, staging and production configuration. So, completely different configurations for different modes in one gateway and switch between the modes as needed, which is fantastic. Then of course, everyone knows about the native SVG drawing editor that’s been added to Perspective just as a reminder of that. It allows you to create and edit your own SVGs in projects and yeah, then offline mode. Offline mode is interesting. I got a question about it the other day, so I thought I might just clarify it for everyone.

35:20
Speaker 2
So through your Ignition Perspective app, users can make the projects available not only while just being disconnected from the gateway, because everyone assumes that’s the only option, but also being completely disconnected from the Internet, so you don’t even need a cellular connection or data connectivity at all. So what happens is the project or the application resources get downloaded onto the device. You can then interact with it, use it, make changes, and whenever that device reconnects with the gateway over any type of connection, it pushes all those changes automatically. And then, obviously, it pulls all of the changes that were made on the gateway through to the device. So it’s like an automatic merging.

36:05
Speaker 2
So if you’ve used version control software before, see it as those two little windows next to each other that says these are the changes that’s been made on the gateway, this has been made on the project, but it automatically syncs all of that changes that we’ve made. So that is very cool. And then lastly, they’ve expanded the alarm notification capabilities with WhatsApp integration. So we’re very excited to see what that entails as well.

36:31
Speaker 1
Finally.

36:32
Speaker 2
Yeah, finally. Right, so let’s check out some standard bug fixes in addition to the latest Ignition 8.1 version. And of course, just what you expect on the new upcoming version. So, in version 45, I introduced a new system property to the designer. I’m mentioning this because I’ve actually had a few support issues. No issues or support tickets regarding the specific thing, but they added a property called Ignition Perspective Designer Save Timeout. And this can control the designer’s wait time for embedded browser frame responses. This is awesome because it significantly improves asynchronous handling. And then of course, just some error messaging during save operations. Because we know if you start embedding browser frames into a project, those browsers might take a while to respond and that usually causes a bit of issue inside of the design. So that’s been added. Very excited.

37:31
Speaker 2
And to improve the infrastructure, they also upgraded the Java runtime environment to the newest version, which is 17013. And they also enhanced the Powercharts tag browser to display the correct Start pass when this tag browser Start Pass property has been bound. Since those are just like some standout features, there haven’t been a lot of major fixes or changes because that was done just in December, so everyone kind of went on holiday. But now coming in version 814 6, there’s a few new big stuff. So for example, Ignition Cloud Edition will now be available as a container image. So yay for the guys working with Docker. And that’s to facilitate deployment in containerized environments. They are also introducing a new usage-based license strategy for Ignition Cloud Edition. So that’s just to offer people more flexible licensing options.

38:29
Speaker 2
I know it’s still gaining traction here in South Africa, but I know it was a big thing regarding how licensing worked inside of Ninja or an AWS space there in America.

38:41
Speaker 1
So it’s pretty rigid.

38:45
Speaker 2
They’re making some changes to that, which is great. Also, one thing that I’m very happy that they addressed is that they fixed a problem that was causing bound custom session properties to disappear from the designer when merging changes from the gateway. It’s something very small, but it caused a lot of headaches. So it’s being fixed in 146.

39:12
Speaker 1
So, essentially, two development streams are still very much focusing on 8.1, which is our current major version, and adding not only boat fixes but continuing to add enhancements today. Then, naturally, the 8.3 build is happening in parallel. So, the I8 teams have been busy for sure.

39:36
Speaker 3
For you before we carry on designations three, that’s from ignition.

39:42
Speaker 2
Yes. So ignition 8.3 will support Python 3. Currently, ignition 8.1 does not support Python 3 because that means it needs. They need to rebuild the whole Python structure in the back end. So that is in conjunction, that’s been done for ignition 8.3. Fantastic. Okay, so what you guys see on the screen now, this is the fun and new thing that Jaco mentioned at the start is something called industry packs. So Inductive Automation has released two new Ignition industry packs and this is a new type of resource that they are providing to the Ignition community through the Ignition Exchange. So what are these industry packs? They are just resource bundles. They contain pre-built, ready-to-use solutions for a specific industry. Now, you can expect these things to include perspective use equipment-specific UDTs, some custom SVG components and so on.

40:45
Speaker 2
And the whole idea of these industry packs is to provide integrators and end users with again these pre-built industry-specific solutions that you can download for free on Ignition Exchange while they are keeping the Ignition platform industry agnostic. So the idea is to empower the Ignition community, you know, all of us and like together with just, you know, empowering us with these pre-built resources is you can actually use these as sales tools for prospective customers that are looking for resources in this demo.

41:23
Speaker 1
Tools, you can use it for bold tools. It’s free and I think these are the same resources that’s being used in the online demos.

41:31
Speaker 2
Exactly.

41:32
Speaker 1
Yeah.

41:32
Speaker 3
This is about speed. As a result, it gives you a fantastic starting point.

41:37
Speaker 1
Yeah, you’d be silly not to use it. At least check it out and see what’s available, especially if there’s some engineering work that will be removed from your project time.

41:47
Speaker 2
Great. So they’ve released two packs, right? Namely the Water Industry Pack and the Data Centre Industry Pack, which are, as I understand it, the first of many to come. So I’m going to show you really quickly just where to find them and how easy it is to, you know, to access these resources and use them.

42:08
Speaker 1
So should we maybe kind of point people to the.

42:14
Speaker 2
We can skip this. Yeah, exactly. I was just going to show them where to find them. But if you go to Ignition Exchange, guys, you can just log in with your inductive automation account details, and you’ll see under Resources, there’s just a brand new section that’s added called Industry Packs. If you download it, you can download it for free. It gives you readme files and a step-by-step instruction guide showing you how to import the projects, how to import UDTs, how to import tags, what you can use the widgets for, and how the widgets work. It’s amazing. I’ve literally set it up in like 10 minutes, both of these projects and it’s so cool.

42:52
Speaker 2
And that is actually what they use, like Jaco said, to build out the Water demo as well as the data centre demo that you can find on the Ignition demo, the online demo.

43:02
Speaker 1
In other words, a lot of things we are saying today, we kind of assume that people would know. I know there are a lot of familiar folks on the call, but there’s also somebody that I’ve never heard of Ignition Exchange. So it’s worthwhile checking out. It is a resource repository where you can download all different types of resources that have been made available free by the community. So it’s definitely worthwhile not only checking out these industry packs but seeing what else is available on the Exchange.

43:33
Speaker 2
Correct, Correct. Right. So these Canary updates, as you guys have heard, we’ve been speaking quite a lot about Canary version 24 nowadays. So that is the next big release of Canary. But since the initial release of 24, which was at the end of last year, there’s been five additional releases, each implementing a handful of new features. So the latest version, which is version 24.2, has gotten a major improvement in a few things. And yeah, the first one is the audit log. So it now supports the option to write events to Microsoft SQL Server instead of SQLite. And that makes it easier to see the differences in things like identity configuration changes, you know, it logs the users when you use the store and Forward API. Let’s say you can see who purged sessions, pause sessions, unpause sessions, and so on. The store went forward.

44:31
Speaker 2
Performance has been improved, especially now when you’re working with like thousands worth of sessions. So that’s very nice as well. The calculations. This is, this is cool. They now support plugins for third party custom functions. And so you can. Yeah, so you can use your own custom functions or they’ve also added a function package called Steam Functions. So that’s a plugin that’s available and that implements the IPWS IF97 standard. Excellent.

45:04
Speaker 1
Yes, very familiar with that standard.

45:08
Speaker 2
Okay, right. And the views now allow reading events from remote calculation services. So that’s very cool as well. Also, the Installer for version 24.2 has been improved with fault tolerance when you’re migrating Historian settings. Okay, so there’s quite a lot of features. I just mentioned a few of them. But for those of you wondering, we still have this. Oh, on the next slide, but just to let you guys know, they are moving. They are busy using or creating Linux Support for the Canary 24 services which is added to the Linux support as well. So some features you are here to highlight that were added in previous minor versions, which is obviously included in 24.2 as well, is the newly added snapshot utility to gather the diagnostic information about the HDB files and the computer systems inside of the Historian.

46:06
Speaker 2
This is such a great tool, especially when you’re troubleshooting data in the data set.

46:13
Speaker 4
Right.

46:13
Speaker 2
They added data set prefix validation to the SQL OPC and MQTT collector. So a nice validation tool that added the concept of asset trends to train graph control for enhanced asset functionality. They added a state drawing method to trend graph control. They added an authentication option in Excel to use an API token. They added the ability to import multiple files per import in the CSV collector and they also added the ability to copy and paste between screens applications in Axiom.

46:45
Speaker 1
These are very important considering that it’s a web browser—a browser-based application. Yep.

46:55
Speaker 2
Yeah, these are just standout features in those five releases. But guys, the release notes for the features are insane. There are a lot. So do yourself a favour and check them out on the Canary community website under the Canary System release notes.

47:13
Speaker 1
It’s a 24.2 list, and I wasn’t sure what you could put in the summary of five points on this slide, so. Well, done!

47:21
Speaker 3
I think so, yeah.

47:23
Speaker 1
2024 was a. Was a significant release for Canary, and I think, you know, it was in. In many ways it was. It. It was a new code. So 24.2, Gary, as far as. As versions go, should be a safe time to upgrade.

47:40
Speaker 3
A lot of work on 24.2.

47:42
Speaker 1
Yeah.

47:42
Speaker 3
And it’s a. It’s a very stable version. And if anybody wants to upgrade to 24, please let the support team know before you go down this road. You need to. If you’re on version 23, you’re on support; you need to get a new license, and you need to be on specific versions. They have specific requirements. So please let Laura and her team know that you plan to upgrade it. Plan. Don’t do it the day before. Give us a couple of days’ notice so that we can get things organized for you. One of our team members will be on the call and we will more than likely even arrange for somebody from Canary to be available as well.

48:25
Speaker 1
Cool. Laura, thank you. So, one last thing. On Canary, they will be hosting their. The Canary team is hosting their first-ever user conference. Can you believe it? In 30 years of business, they haven’t had one. So they decided, we’ve been doing this, well, 40 years. Let’s have our first user conference. So it will be this year in August in Pennsylvania. It is a month prior. A month or so prior to the Ignition Community conference in Folsom. So those are two really good excuses for a valuable trip to the US to spend time with those communities, both the Canary and the Ignition communities, this August. We will definitely be there. Not quite sure who, but if you’re thinking of joining, please let us know.

49:10
Speaker 1
We’d love to arrange that with whoever in the local community would like to attend that conference. All right. That was it. That was a lot of waffle—much longer than it should have been. It was my fault. Sorry, Laura. Thank you. Clarice, I hope you’re still with us and you haven’t run away.

49:30
Speaker 3
I’m still here.

49:31
Speaker 4
Yeah. Don’t worry.

49:32
Speaker 1
Hospital sessions on the cloud are as steep as all their coffers. Therese, if you. If you’re able to. To turn on your video and you. You are in an environment where you can do that; you’re welcome to. Oh, there we go. Fantastic. You would think so many webinars in. We’ve got to figure out. But we. We finally found the button. But I actually found the button. It was my fault for enabling it. So nice. Nice to see you and thank you again for joining us, Clarice.

49:57
Speaker 4
Yeah, thank you. For having me.

49:59
Speaker 1
I am nuts about this application by the way. And no, it is a. It is. The title reads automating a large-scale Macadamia nut processing facility with ignition SCADA. What we didn’t know initially, Clarice, is that this is an Australian-based project. We didn’t, we didn’t get a sense of the scale initially when we spoke with your team based on what we’ve seen and what you’ve shared. It is a phenomenal application. So well done for that. And maybe we can jump straight into that with you giving us an idea of who you are a little bit about Systeco, if that’s okay. Just to give us some context about your business, the industries and the customers that you serve.

50:47
Speaker 4
Yes.

50:47
Speaker 2
Okay.

50:47
Speaker 4
So Systeco Automation is basically a division of Systeco Proof that specializes in in involves designing tailored automation solutions to meet diverse industry needs. Our Expertise includes the flag, PLC programming, SCADA designs, and IoT integration, also enabling us to enhance product efficiency by minimizing human error. So basically, we bought us a Phoenix and Ignition certified integrator, which maintains close partnerships with them, allowing us to test and implement their pilot products. So this ensures innovative and reliable solutions for our clients. Also, this collaboration extends to the integration, sorry, integration for seamless data acquisitions, real-time monitoring, as well as advanced automation controlling for scalable high-performance and industrial solutions.

51:47
Speaker 1
Okay, so you’re fully, you’re quite a comprehensive from fabrication all the way to advanced process control business. I haven’t been to your Nelspruit office. Gary has been. We’d love to visit one day but I believe it’s beautiful.

52:05
Speaker 3
Yeah, really, really nice facility.

52:08
Speaker 1
Also a nice part of the world at the moment.

52:13
Speaker 2
Can I come as well?

52:20
Speaker 1
Yeah, for sure we need to do that. So tell us a little bit more about your client in Australia. I’ve got it on the screen. I’ve got a little bit of the overview of what you’ve done. The project is still, I believe, ongoing. It’s not complete yet. We’ve put some of the functional requirements on the screen and some of the solutions. But maybe tell us about it. Yeah. The customer and their needs and how you found it.

52:45
Speaker 4
Yeah, so our customer is wide-based sorting. obviously, it’s an Australian-owned and grown processing company. The company was founded by a group of leading academia growers who recognize the need for the market. The need for the market, the process, and to deliver premium academics to the world. So yeah, they guarantee the quality by controlling Supply chains basically from the hand, from the farmer straight to the consumer. This basically uses the combined years of expertise and the commitment to farming excellence. So yeah, but considering that White Bay is one of two companies currently in Australia that is associated with another, they’re both basically based in Central Queensland, so currently, there are an additional four to three to four other companies that we’re working within Australia and getting startups on. So it’s super exciting.

53:45
Speaker 4
Definitely a lot to handle, a lot on our plates, but we’re coping. But yeah, our team is excellent, enthusiastic about all of it, and we’re just looking forward to how we can integrate and use Ignition to showcase the work that Ignition can do and the work that automation can do.

54:09
Speaker 1
Thank you for choosing Ignition. The application looks great by the way. We’ve got, we’ve got some screenshots, we’ve got a little bit of what the architecture is. So maybe it’s to recap the solution you mentioned, Phoenix Contact around at the moment around just over 7,000 tags, 35 screens, 10 clients, 100 logs, and a couple of fairly standard protocols that you’ve used. The SQL Bridge, which, of course, handles the integration and data exchange, and then you’ve got perspective. And I was quite excited when I saw the app screenshot. I think it was specifically for the, for the curing processes. Very, very. I’m going to use the word sexy because that is really a sexy screen. Very, very nice view that on the mobile. And maybe the functional requirements will kind of explain itself when we look at some of the screens.

55:09
Speaker 1
But maybe let’s start with the architecture. The architecture is fairly basic. I want to call it what we call a basic architecture. I think what you had to do on your side was some network redundancy and custom scripting?

55:26
Speaker 4
Yes, that’s correct. Unfortunately, I have all the info regarding our architecture and all that, and I obviously stepped in for a polygon mine. But yeah, so basically we offer redundancies to make sure that if something goes off nothing else in the facility is affected by this. To make sure that everything runs smoothly and there’s no interruptions should there be an error or something with one PLC or whichever that it’s lost connection or is faulty.

55:59
Speaker 1
Yeah. And I do know you also opted for redundant technician OPC fail or at least ready for an OPC failover and that at least gives you some of that uninterrupted operation. So, truly standard architecture, looking at Some of the screens, this is the overview screen you mentioned. One of the requirements was seamless control and monitoring. I think the user interface is very interesting. The visualization is always a very personal thing. You know, there are considerations for situational awareness. There’s a consideration for ease of understanding and reading and distraction and colour use. But you designed this to ultimately adapt to different screen sizes, making sure that it’s clear and consistent on different views, whether it’s a touchscreen, HMI or whether it’s a cell phone. You had to design with that in mind.

57:04
Speaker 4
Yes, definitely. So obviously, the other additional screenshot that we shared, mostly like our receivable line, like gantry lines and all that would see that we use maximized and minimized type of use for this because usually our HMIs range from anything from 15 inches to 7 inches. We’re trying to opt away from the 7 inches because it’s a bit tiny and, you know, sometimes, you know, the finger just doesn’t want to press the right button. So we don’t want to, you know, want to take away the human error that could even occur in such occurrence. So we’re trying to go for the 15 inches. But currently, I think that was also really something that just could showcase what we can do with Ignition to show that there are two different things that you can do.

57:48
Speaker 4
You can maximize and minimize the views and still show enough detail to do everything that you want the system to do.

58:00
Speaker 1
I’m guessing that you have some kind of navigation breadcrumb paint throughout the views. That’s the little on the top left-hand side, the little selection there. Okay. All right, cool. The multi-stage. So there’s some batching involved. I don’t know if you were personally involved in some of this batching that’s involved with data. I don’t know if you can add any context to that.

58:34
Speaker 4
Yes. So the batching, basically it continues evolving. So we started off as simple as possible, adding so much more detail regarding it. So unfortunately I can’t remember if I sent that with the screenshots, but if there are certain aspects where if you press on it, there’s a batching pop-up that comes in where you can just include client information, bin information, all the additional information that you as a client or as the integrator wants to add to the system, you can enter into that batching system and you can submit it and it will be submitted through the whole system and then pull through to the databases and all the requirements that you needed to do.

59:13
Speaker 1
I’ve noticed that there are some elements of material tracking. There’s also some waste tracking that you’re doing. So it’s a little bit more than just batch. It’s actually quite a lot that you ultimately scripted; I would imagine, inside of the Ignition without utilizing some of the out-of-the-box type MES modules that you would typically need.

59:35
Speaker 4
Yes, definitely.

59:36
Speaker 1
Somebody did a lot of typing obviously.

59:38
Speaker 4
Sorry. Obviously very followed by and experienced regarding all of this and it’s super awesome to see where this thing starts and to actually see the final product regarding all the notes and the crypt notes and everything that you would see on the desk and everything to get it to this point and to get it to work the way that you need it and wanted to work.

59:58
Speaker 1
Yeah, absolutely. I know Gary has a question about whether you had the green and red conversation.

01:00:07
Speaker 3
Everybody always have.

01:00:09
Speaker 1
Every project there’s a red and green conversation that has to be had before it kicks off. This is the curing, and what I really didn’t realize about the curing; I only saw it afterwards, where it was obviously weather-driven. You know, I know very little about Agria and this kind of environment, but obviously, it’s weather-driven. So, you need the ability to have these weather driven curing adjustments. And I think you actually integrated with a weather API to get the real-time weather data that enabled some automated adjustments to the curing room conditions. I mean that’s really, really cool.

01:00:51
Speaker 4
Yeah, so definitely I think it was awesome to integrate into that. Mostly we can’t teach it on our app, but Wide Bay is still be. Like I said, it’s very evolving. This is still stage one of stage, like four stages that this project is consistent of. So the more we evolve and the more we go into the next stages of this product and the next stages of the facility, the overviews and everything might even change because we evolved into our next facilities into a better navigation system as well as adding the weather API. But you could see that weather API on the app specifically, which is awesome.

01:01:31
Speaker 4
So yeah, real-time weather data was integrated into the API, which allows us to automate the adjustment for the curing conditions, especially the real-time curing conditions. As you all know, the curing process is heavily influenced by external weather conditions, so it’s really necessary to integrate real-time weather data for the optimal curing result.

01:01:54
Speaker 1
Absolutely. And that’s ultimately what affects the overall quality of your product and the shelf life and various other things. Really, really cool. I didn’t realize this was in the application. Very, very nice. Power monitoring, that’s naturally a fairly large component of this type of facility considering the potential the energy and the utilities that are involved. So power monitoring was a requirement from the beginning. Are you integrating with any? Any kind of metering type system, or is it? Is it pretty much hardware on-site?

01:02:29
Speaker 4
There is hardware on site here, and there might be additional stuff that comes along the way, but it’s basically hardware on-site and just the communication between the PLTs and visual Ignition to showcase all this data and the trend.

01:02:42
Speaker 3
Okay.

01:02:42
Speaker 1
And you’ve got some real-time training that you can. I see you’ve currently got it set up for eight hours, which is pretty much the last shift. But you can actually, with this view you can, select that period to be pretty much anything. Yes. But you’ve got it set up for that. It’s a really nice layout. I like that. Yeah.

01:03:02
Speaker 4
Specifically. Sorry. Specifically, power monitoring again is also a view that has advanced since submitting it. We are working on a different view as well, including all these trains and then a few pie charts and stuff like that, including extra additional information that might not be listed here. So, obviously, you see the trends, but you missed some of the information. So it. You know the power monitoring page has evolved even since the submission. So it’s kind of cool to see the new pages like evolving and seeing what new information you can add and how you can edit other than using training.

01:03:39
Speaker 1
Fantastic. There are lots of trends. I imagine it’s a very trend-heavy page, or couple of pages. I know there’s also the. You’re also utilizing the. I don’t think I’ve included any screenshots of that. But you also use the reporting. I know you’ve got a Postgres database in the background. You also use the Ignition reporting module, where you have some weekly and some monthly reports, specifically around the batching and the power monitoring.

01:04:17
Speaker 4
Yes. So if you go through the whole chain and you select from there, you go to the reporting pages, which basically a personalized report that pulls up personalized reports. Again you can filter this from start date, finish date time, whichever way the client needs it to be submitted or recorded. Yeah. So basically it’s the same. So and. And it’s easy navigation if you actually use the system. So you can actually go directly from the trends to this reporting and just see the overall view of what you need to see and how you would see it.

01:04:50
Speaker 1
Lovely. I mean, are you distributing? Are you Emailing those reports at the moment?

01:04:56
Speaker 4
No, luckily not. I have enough on my plate as is. But yeah, so this is obviously easy for not only internal use, but definitely external for the client as well. So yeah, hopefully, they have a system in place and someone in place that can do it all. So.

01:05:12
Speaker 1
But yeah, okay. And then just a final screen here, which is the alarms. Your. Your typical alarm view. Alarm philosophies have become quite a. Quite an interesting alarm rationalization and philosophies have become quite an interesting talking point. I’m guessing there was no. Any. Any kind of special alarm strategy that you implemented. You’re making use of the kind of standard functionality with the relevant criteria for notification and acknowledgement and shelving and all of those things using the native functionality inside of Ignition.

01:05:53
Speaker 4
Yes, definitely. So using everything regarding this. So every video normalized factory alarms, just saying, listen, an E stop was pressed or something has tripped. One of the motors has tripped off on Bayer has tripped. So it’s basically just getting that feedback from the PLC and just integrating it into ignition so we can just get the normal typical factory alarm.

01:06:15
Speaker 1
Yep. We’re really excited about the WhatsApp module. I think the WhatsApp module is going to add a cohesive teamwork environment to alarming, which is typically missing. You know, it’s very one direction. Well, it’s bi-directional, but it’s very specific to a person or a group of people. But it’s kind of linear, I think. I think the WhatsApp module is going to add that ability to troubleshoot an alarm as a team of people. So we’re really excited about that one. It’s coming with 8.3.

01:06:46
Speaker 4
Yeah, definitely. So, currently, for our alarming system, we use Telegram to receive all our alarms. We also agree that WhatsApp integration is something we’re keen to explore, but it’s also something WhatsApp isn’t all internationally used, so it’s a bit typical. But you know, Telegram is a great backup for that. But local users in South Africa, you know, we know WhatsApp, we love WhatsApp.

01:07:15
Speaker 1
Yeah, yeah.

01:07:17
Speaker 4
So we’re definitely keen to explore that. But yeah, so. It also gives us the ability to now basically quote and build a quote client-specific or factory-specific, which is an added flexibility and possibly a welcoming one from, I think, most industries.

01:07:37
Speaker 1
Yep. There’s a cool tech note, by the way, for Telegram. Not for you, Therese. You Guys have done it. You, you’re the experts. But for those of you online that’s wondering, we do have a quite a easy to follow guide for Telegram.

01:07:52
Speaker 2
Yeah, we’ll make it. We’ll make a WhatsApp one when it comes up. But not now.

01:07:58
Speaker 1
Yeah, yeah. Clarice, well done to you and the team. I think it’s, I know it’s not complete. Be careful of the. It will never be complete because then it’s perfect or it will never be perfect because then it’s complete. But I know it’s still a life project. It’s really impressive. It looks good so far. We’re going to share this information. I know you’ve given us permission to share it with everybody online. Maybe from your side, a final, you know, there’s sometimes a unique insight or some profoundness through a project like that the team has discovered. Is there, is there anything that you like to share?

01:08:36
Speaker 4
So basically I had this discussion last night with our, basically our team leader on this regarding the program side and I can’t exactly explain the whole situation, but when he talked to me, I had this dumbfounded look on my face like, okay, how the hell would you actually do this to not to make it work the way it works. So we had like a problem with the valve bank and getting it to, you know, communicate directly. Yeah. With the valve bank and, you know, then we had to run it through our bagging system, and then all that stuff to just basically get it to communicate directly with the first system that we needed is it to communicate with. But he had this all setup, and I’m like I said, I was dumbfounded when you saw the whole situation.

01:09:16
Speaker 4
Like I, if I have to explain, it would take me an hour just because I would go from, you know, top to finish and then go back to the middle because, like, I don’t know how to make sense of the system the way he does.

01:09:29
Speaker 1
Well, yeah, definitely a team effort and it shows. Thank you. Thank you very much for taking the time to share with us today. We’ll kind of contextualize and compact this into something a little bit more user-friendly that we can share with everybody. But thank you for joining us and sharing the information. We really appreciate it.

01:09:52
Speaker 4
Thank you for having me and thank you for having Systeco automation.

01:09:56
Speaker 1
Absolutely. Good people. Any questions for Clarice from anybody online? No, nothing yet. No questions for Therese. That is the end of our Elevate. I have Elevate Geez. I’m thinking of Elevate. If there are any other questions for this DLF Live section, please, you don’t have to let us know right now in the Q and A. You can always let us know afterwards. We will be sharing the dates for Elevate later this year, which will again be in October. And just to again highlight that we will be visiting Durban this year. We have spoken about KZN for two years now and we’ve neglected Kwazulu Natal. We will be doing an Elevate event in Kwazulu Natal this year. Yeah, absolutely. So we’ll share those dates with you as well as pretty much everything that was in this webinar. We’ll, we’ll share afterwards with the relevant links.

01:10:55
Speaker 1
But thank you very much for joining us. Are there any last words from anybody? I know we’re over time. It’s 30 minutes, as always.

01:11:02
Speaker 3
Getting better.

01:11:03
Speaker 1
We can. 20 minutes. Yeah.

01:11:07
Speaker 3
Thank you, everybody, for taking Time out of your day. Do you share this time with us? We really do appreciate it.

01:11:14
Speaker 1
Yeah, I hope it was valuable. We’ll definitely share more information about everything that we just touched on today. It’s very difficult to cover the details in an hour, but let us know how we did. We’ll be sending out a survey, and we will chat to you again as the DLF Live in another three months. Thank you very much for joining.