Turn Ignition Into A Complete Energy Management System

00:00:15.000 –> 00:00:17.000

Good morning.

00:00:17.000 –> 00:00:21.000

Morning, Markus. Morning.

00:00:21.000 –> 00:00:33.000

And, uh, good morning to everybody, or good day, or good afternoon, from wherever you’re joining us, um, for our live demo. It’s not often that we do live demos. No. It’s, uh…

00:00:33.000 –> 00:00:48.000

It’s reserved for events and proper testing only, but we’ll see how it goes. Good morning and welcome, and thank you for joining us for the Building What’s Next in Energy Management webinar. My name is Jaco from Element8. With me, I have.

00:00:48.000 –> 00:00:52.000

We have Markus Oosthuizen, Solution Engineer.

00:00:52.000 –> 00:01:08.000

And Luan Taute, who is managing all our webinars, but especially today, behind the scenes. Luan, welcome. Luan will also be checking for any questions in the chat. I see we still have people joining us.

00:01:08.000 –> 00:01:27.000

Yeah, there’s still a couple of more people coming on. Okay. All right. Fantastic. Well, I don’t think we’re going to wait too long. We should probably get started. But if you do have any questions, please let us know. It’s always difficult speaking to an audience that can’t speak back.

00:01:27.000 –> 00:01:37.000

Uh, so we always appreciate any questions, and we answer them immediately as they come in. Uh, but yeah, if you have any questions, please, uh, you’re welcome to put them in the chat.

00:01:37.000 –> 00:01:43.000

So today, we’re going to cover something a little bit different if you are familiar with what we’ve done in the past.

00:01:43.000 –> 00:01:58.000

We typically talk about the universal aspects of Ignition. We cover specific functionality like reporting and historian capability, but it’s not often that we delve into a very specific.

00:01:58.000 –> 00:02:13.000

plant functional area. And we’re really, really excited about energy monitoring, or specifically the energy monitoring module. That is a third-party module that was developed by LIDT Technologies, but really, really nice in terms of.

00:02:13.000 –> 00:02:30.000

Really taking the existing tag data that you already have, maybe connecting a couple of additional PLCs and meters and really turning that into consumption numbers, real-time consumption numbers with time of use schedules and associated costs.

00:02:30.000 –> 00:02:33.000

Really, really cool module.

00:02:33.000 –> 00:02:49.000

And we’re going to get into that. But before we do that, who we are is Element8. If you’re not familiar, we are the sole Sub-Saharan Africa distributor of the Ignition Industrial Automation Platform, Sepasoft MES, which is built for Ignition and the Canary Data Historian.

00:02:49.000 –> 00:03:05.000

No nonsense Canary Data Historian. So why we exist as a business is to ensure a data-driven and flourishing future for the industry. Our guiding principles are to humbly serve our community and industry. We’re not experts. We may be specialists, but we’re not experts.

00:03:05.000 –> 00:03:11.000

We learn every day, and whatever we learn, we share with our community.

00:03:11.000 –> 00:03:27.000

And what we provide is intuitive and scalable industrial technologies that break down the barriers of cost and complexity. Before we get into the module, though, we will be covering some aspects of the module as well as many other live topics.

00:03:27.000 –> 00:03:35.000

demos and specifically what is next at our ELEV8 Roadshow.

00:03:35.000 –> 00:03:50.000

Um, at the end of October. It is in South Africa. We’ll be covering KwaZulu-Natal. Uh, we will be going directly after that, on Wednesday, 28 October. We’ll be heading to Stellenbosch, and we will finish on Friday, 30 October.

00:03:50.000 –> 00:04:01.000

at the Irene Country Lodge in Centurion. So ELEV8 is our annual gathering, our annual community event. We have our customers, system integrators.

00:04:01.000 –> 00:04:16.000

Anybody who’s new, who wants to learn more, we get together, and we talk about some of the fundamentals just to set the scene. But then we get into some of the really exciting innovations and things that are coming up next.

00:04:16.000 –> 00:04:33.000

And I think for this one specifically, I’m really excited about Ignition 27. Ignition 2027, which was announced a couple of weeks ago at the Ignition Community Conference. Some really exciting features that we’ll maybe allude to or touch on.

00:04:33.000 –> 00:04:48.000

Yeah, we’ll drop some bombs. But we’ll get into that one specifically as well as SepaIQ at the ELEV8 conference. So if you would like to register, check out element8.co.za for the details.

00:04:48.000 –> 00:05:04.000

I think Luan is probably hearing a lot. I’ll share the link in the chat. Just fantastic, Luan. We would love to host you at ELEV8. Tickets are selling fast, so if you’re thinking of joining or you would like to join, register now, sooner rather than later.

00:05:04.000 –> 00:05:08.000

Any questions so far? No questions so far. Okay, good.

00:05:08.000 –> 00:05:26.000

I think it’s all understood so far. All right. So our webinar today is, as we mentioned, focused on energy management. But the exciting bit is that it’s a module, third party module that is not free in this case. No.

00:05:26.000 –> 00:05:41.000

It adds a lot of value that is built for Ignition, but the exciting part is that it utilizes all of the amazing benefits and features that we have within Ignition. It exposes that and uses that inside of the module. Yes, yes, I mean, this is…

00:05:41.000 –> 00:06:00.000

for anyone that’s… that’s… that’s ever done energy management, power management, anything of the sort, um, there’s always been limitations, because the focus has always been on energy or power. What would those be, for example? Limited number of… Limitations… I mean, I’m gonna mention a few limitations now, and it might not seem as a limitation at the time.

00:06:01.000 –> 00:06:11.000

Until you start thinking of Ignition, then everything seems like a limitation, right? Gotcha. So, for example, a lot of the time, a lot of the.

00:06:11.000 –> 00:06:26.000

The other platforms would only include maybe one or two protocols that you could use. And with time, they maybe added another one. Building energy management systems. Communication protocols. Communication protocols, drivers. Let’s call it device drivers like Modbus TCP, Modbus RTU.

00:06:26.000 –> 00:06:44.000

I think a few of them for the new craze started doing MQTT. But still, some way or another, you either had to do some sort of conversion in the field or some device to do something for you to get the data if it didn’t speak that proprietary protocol or that specific protocol.

00:06:44.000 –> 00:07:00.000

Building energy management on Ignition, we now have the option of all the device drivers that comes with Ignition, some of them being PLC drivers, right? So what this opens for us is we can now connect serial meters.

00:07:00.000 –> 00:07:20.000

water meters, gas meters, power meters, flow meters, anything that we want, we can, whether it’s serial, I mean, doesn’t matter the protocol, IO-Link, ASIN, connect that to the PLC, connect our PLC to Ignition, and still do our energy management like we would have wanted to. And you’re not limited to the number of devices. And you’re not limited to the number of device connections. Makes sense.

00:07:21.000 –> 00:07:24.000

Cool thing that you can also do.

00:07:24.000 –> 00:07:40.000

is we’ve got redundancy, something that’s never been a need, I guess, in energy management or power management. Well, if you’re billing, you don’t have the ability to produce a decent, accurate billing report because you’re.

00:07:40.000 –> 00:07:55.000

your system was down, then it’s a problem. So, um, and now it comes the first bomb for 2027. So, yes, we’ve got redundancy, and that’s cool. Ignition’s always had redundancy. We’ve got nice failover cross-platform. You’re going to failover from Windows to Linux. We all know that.

00:07:55.000 –> 00:08:03.000

One subtle thing they mentioned, and it’s in the tech, the small, I think they call it a one-pager for 2027 that you can read, is…

00:08:03.000 –> 00:08:12.000

They… we don’t know how it’s gonna work, they’ll show it, but there’s multi-failover now. N+. N+. So you can now failover to multiple.

00:08:12.000 –> 00:08:17.000

servers with Ignition 2027. So another.

00:08:21.000 –> 00:08:30.000

get this new add-on benefit. 2027 beta is expected end of October? Yeah, they told us November.

00:08:30.000 –> 00:08:31.000

No one…

00:08:32.000 –> 00:08:49.000

Well, we know November. Okay, so Beta’s expected October slash November, and they are aiming for a January, February launch of Ignition 2027. But again, we will at ELEV8, we will.

00:08:49.000 –> 00:09:06.000

Get a live view. Travis Cox from Inductive Automation CTO will take us through a live demonstration of Ignition 2027 with, of course, the really exciting thing that we haven’t even spoken about, the artificial intelligence module.

00:09:06.000 –> 00:09:24.000

Ignition Catalyst module, which will really be focused on the use of AI, not only natively inside of the designer, for example, but also Agentic in terms of other modules and agents that you can create. So, we’ll definitely, as we go through the module, we’ll definitely.

00:09:24.000 –> 00:09:26.000

Point at some features.

00:09:26.000 –> 00:09:35.000

that 2027 will enhance, or add, or… but you would need to come to ELEV8 to really see the power of Catalyst. I think me and Jaco.

00:09:35.000 –> 00:09:50.000

spent a day just processing what we saw. It is gonna be. It’s gonna blow your mind. And then another cool thing that Ignition gives us is the option to connect to multiple databases.

00:09:50.000 –> 00:10:03.000

And the multiple databases now gives you, you know, whatever your preference would be, and also unlimited, again, you know? Just limited by resources. So, we talk about Ignition, we talk about a platform.

00:10:03.000 –> 00:10:05.000

Right? Not a product.

00:10:05.000 –> 00:10:13.000

Ignition is our platform, and what we want to get to is to build an energy management system.

00:10:14.000 –> 00:10:33.000

product, we need the Ignition platform and the energy monitoring module. So the module that was developed by LIDT Technologies, so it’s a third-party module, but naturally, it needs to be vetted, approved by Inductive Automation. So what Inductive does, um, is they…

00:10:33.000 –> 00:10:46.000

provide you with an SDK, it’s a public SDK, module SDK, software development kit, which you can then go through, you can start developing your own features, add-ons, modules for Ignition. You can then use it.

00:10:46.000 –> 00:10:49.000

If you want to then, um…

00:10:49.000 –> 00:11:03.000

upload the module to the third-party showcase, that is where Travis Cox himself actually approves it and goes through the module to check it. I didn’t realize Travis does that. Travis is the one that approves all of that.

00:11:03.000 –> 00:11:20.000

spends his nights. So that is what that that’s how we position ignition platform plus specific modules gives us the solution. We’ve always done this perspective gives us visualizations, historian gives us trending. And then this module gives us.

00:11:20.000 –> 00:11:28.000

SQL Bridge gives us transaction group transfers. So this is just another one of it. So energy monitoring module.

00:11:28.000 –> 00:11:40.000

Um, it’s a purpose-built Ignition module for metering, tariff management, and energy billing. There is some few extra things there that we’ll go through when we go through the dashboards. Um, but you configure your meters.

00:11:40.000 –> 00:11:44.000

you. Actually, the module was built so that.

00:11:44.000 –> 00:11:58.000

when you’re… if you’re comfortable with Ignition, you’ll be comfortable using the module. It was built to use and utilize all the benefits and functionality Ignition already provides you, and just give you some small tick boxes to add.

00:11:58.000 –> 00:12:12.000

to enable the energy monitoring for you. Okay, so that’s an important point. If you have an existing Ignition Gateway, if you’re not familiar with Ignition, you have an existing platform, gateway slash platform, with various modules. This is a module that you can simply.

00:12:12.000 –> 00:12:27.000

plug on top of the existing gateway. If your scale and your scope is a little bit more serious, potentially you would want to have it separate from your, for example, your SCADA gateway, and you would want to have another instance, another gateway.

00:12:27.000 –> 00:12:36.000

Uh, with the modules running as a separate energy monitoring system. System, yes. Um, or if not, it could…

00:12:36.000 –> 00:12:50.000

purely serve the purpose as an energy monitoring system, standalone, on its own gateway. And that’s exactly where the power comes in. For anyone that’s already got an Ignition server running, the only thing this module needs is tags.

00:12:50.000 –> 00:13:01.000

and history. That’s right. So as long as you’ve been historizing your data, you would install the module, map the UDTs to the configured variables for the module itself.

00:13:01.000 –> 00:13:06.000

and energy management is there. If you’ve already got history, you can actually install the module now.

00:13:06.000 –> 00:13:24.000

If you’ve already got history, you already can go back six months and already do some energy monitoring management for you. And if something doesn’t look right in terms of gaps or spikes, then the history, the data editor could probably help with that. Yeah. So it’s called an historian data editor. It’s a manual data editor. It does have an audit trail.

00:13:24.000 –> 00:13:41.000

So it’s not like someone’s going to change values and then you won’t know what happened or who did it or what happened. And it’s very authorization. You can lock it down. Role specific, yes. You can set the authorization roles, group roles, security roles that can actually change.

00:13:41.000 –> 00:13:44.000

or edit manual data.

00:13:44.000 –> 00:13:49.000

And it comes with an audit trail so you can see who edited it, when they edited it, why they edited it.

00:13:49.000 –> 00:14:11.000

So we’ve got, we can build hierarchies, we can do time of use schedules. We’ve got built in reports because we know, we all know Ignition’s reporting module. We love the reporting module. Just take some time from you to get that fantastic report. But I will spend a little bit of time maybe later on to show you a cool data source that almost no one utilizes in the reporting module. So you can quickly go through that.

00:14:11.000 –> 00:14:16.000

And then the billing engine, which is part of the reporting module.

00:14:16.000 –> 00:14:25.000

And there’s a number of built-in reports. There’s a few, I think there’s 66. That’s amazing. I think any kind of…

00:14:25.000 –> 00:14:44.000

power slash energy kind of a report that you… that you have in mind, and… and a lot of them are kind of standard, in the sense that most people would expect that type of report, but there’s also some additional ones, but yeah, 60-something reports is fantastic. Yeah, that’s… I think it’s a good starting point, and they do provide you with, uh…

00:14:44.000 –> 00:14:59.000

If you download the module, they do provide you with a backup demo project to get started. That’s actually the one we’ll be sharing now. Just to see how did they do this? How did they get these results? How did they get these charts? How did they get these values?

00:14:59.000 –> 00:15:05.000

And… geez, I’m not even sure how many, but they do provide you with… like we said, the module was built.

00:15:06.000 –> 00:15:18.000

to work with Ignition, so it also provides you with scripting functions. We all know Ignition’s got fantastic scripting functions, system.util.whatever, so it’s system.energymonitor.

00:15:19.000 –> 00:15:21.000

a million functions.

00:15:21.000 –> 00:15:29.000

The site hierarchy, so the ability to identify areas, buildings, and floors.

00:15:29.000 –> 00:15:40.000

cost centres, that they would… UDTs would play a part in that. Yes. So, how it works is that the module works with Bring Your Own UDT. Yes. So, Bring Your Own UDT means.

00:15:40.000 –> 00:15:44.000

User-defined type, sorry? Yes, I’m…

00:15:44.000 –> 00:15:59.000

Assuming everyone knows what I’m talking about. I think most do, but I don’t want to assume. So you bring your own UDT user-defined type. The module does come in the in the the backup project. They do provide you with.

00:15:59.000 –> 00:16:20.000

their UDTs, just to give you an idea of how to map them. But if you’ve got your own power meter, PM8000, whichever power meter you’ve got, Logix, whatever, power logic meter, you already have that inside of Ignition, you don’t want to rebuild it and connect it to these other UDTs, that’s fine. The only thing you have to do, and we’ll show it quickly, is.

00:16:20.000 –> 00:16:34.000

on, for example, current A, map it to the module’s current A. That’s the only thing. If it’s called C, that’s fine, it connects to current A, and then the module knows, in this UDT.

00:16:34.000 –> 00:16:45.000

this is the member I need to look for in the UDT that is current day. And the user-defined data types is something you create once? Once. And that’s… that’s actually the powerful part.

00:16:45.000 –> 00:17:00.000

is you create the UDT. Once you map it to the energy monitoring module. The only thing you need to do after that is, if you add more meters, you create an instance of that which is Ignition. Give it a new name, point it to the path that you connected it to.

00:17:00.000 –> 00:17:07.000

And then you can either just assign the time of use schedule to it, if you don’t want to put it in the hierarchy. If you do put it in the hierarchy.

00:17:07.000 –> 00:17:16.000

there’s already a time of use schedule assigned to it, and it just becomes part of the system. If it’s part of the system, everything just… it just flows out from there.

00:17:16.000 –> 00:17:27.000

and then a billing engine as well. Yes, the billing engine is part of the reporting. I mean, it’s just billing. But it’s a billing report. Yes, lovely. So this is what we spoke about.

00:17:27.000 –> 00:17:35.000

I should have gone here when we spoke about it, eh? Oh, it’s fine. So we talk about virtual meters here.

00:17:35.000 –> 00:17:49.000

I am going to show it. I think you should show it. I think it’s easy to show it. It’s pretty powerful. Because we’ve got two things called logic meters and virtual meters. It’s pretty powerful, yeah. And there’s quite the difference between the two. So we’ll go through it.

00:17:50.000 –> 00:17:57.000

This is just an example of time of use schedule. You’ll see when we do the demos, there’s different ways of showing them. You can create…

00:17:57.000 –> 00:18:14.000

about the as many as you want. So you can create as many as you want. What there also is is there’s 2 things. There’s a time of use schedule. And then there’s a tariff plan. Now, the reason why there’s 2 a tariff plan.

00:18:14.000 –> 00:18:27.000

It’s sort of like your rules determining which time of use schedule to use. So if you exceed a certain consumption rate or you exceed a certain demand, your schedule might change.

00:18:27.000 –> 00:18:41.000

And that you determine in the tariff plan. Now, the cool thing about the tariff plan is you can just assign a tariff plan to a hierarchy as well, and then it would follow the tariff plan to determine which time of use schedule to use based on your consumption and your demand. So.

00:18:41.000 –> 00:18:46.000

And the tariff plan is also, I’m excited to see what people build because there’s a lot of things in there.

00:18:46.000 –> 00:18:59.000

Um, people that I’m sure… don’t ask me too much difficult questions on this thing. I’m not an energy specialist. Um, we focus on ignition, we want… this provides a solution for ignition.

00:18:59.000 –> 00:19:19.000

But I’m excited to see what people build with it. It’s going to be, I think I’ve seen some of the knowledge out there and I think people can do powerful things. Yeah, absolutely. And especially, so the rates are version controlled for historical accuracy. So you have that backup, that understanding of what was relevant at that time. And the time of use schedule has got version control.

00:19:19.000 –> 00:19:30.000

So, if you know, in 3 months, or 4 months, or next year, the time of use schedule, your rates will be changing, you can already do it now. You can make the changes now and say, effective from this date.

00:19:30.000 –> 00:19:43.000

And then, from that date, it will start using the new one, but when you query or you do your reports, it will still look at the version control and know which time of use schedule to use for your reporting to make sure it uses the correct rates.

00:19:44.000 –> 00:19:45.000

Okay.

00:19:45.000 –> 00:19:56.000

This is the one we spoke about, the Historian Data Editor. So there’s a few options here when you fill gaps. Um, it can either be comms failures, or there it tells you it’s got a current transformer glitch.

00:19:56.000 –> 00:20:12.000

Um, so we can do linear interpolation, we can do just an average, or we can do your own formula. So, you can do all of that, I mean, if you want your own nice little formula in between it, you can do that. Um, it does bring an audit trail, um.

00:20:13.000 –> 00:20:16.000

And you can select a big time range to do it through.

00:20:16.000 –> 00:20:31.000

But this is really more people that don’t know where they would use this, don’t use it. Correct. There’s people that know how to use this and there’s people that just don’t. So it’s just not. And again, especially if you’re billing, you wouldn’t want to use this. Yes, that’s the thing. If you’re going to be billing someone.

00:20:31.000 –> 00:20:40.000

Yeah, then it. And luckily there is an audit trail. So you can see you change data. But I mean, I guess that’s true for anything. Yeah.

00:20:42.000 –> 00:21:04.000

We’ll probably go through the. Yes, I don’t want to go through. This is just. This is just a drop in the bucket. I think we can share this afterwards. We can share the slides afterwards. It’s just a it’s just some of the feature overview of the features. We like to go through this before we. Yes, the cool thing about the billing engine. I’m saying it’s a billing engine. It’s not a billing engine. It’s the Ignition reporting module.

00:21:04.000 –> 00:21:21.000

But the reason that what’s automated at least. It’s automated at least. Yeah. So the cool thing about this is you create the billing data source inside the reporting module. And then the module just utilizes everything from the reporting module. It can.

00:21:21.000 –> 00:21:42.000

Everything here, the approval workflow, the export and integration, this is all built into Ignition, right? We could have always done automated reports, and we could have always exported to CSV. We can send it wherever we want. We can do PDFs, we can do text. I mean, this is Ignition, using the power of Ignition, full on.

00:21:43.000 –> 00:21:47.000

Once again, come to ELEV8 2026.

00:21:47.000 –> 00:22:05.000

you can… with Catalyst, you can now automate some of that exporting using the Agentic Catalyst. Not gonna say how, because I’m not even sure myself, but I know you can, because I’ve seen it. So without getting into too much technical detail around architecture, you.

00:22:05.000 –> 00:22:17.000

you pretty much, fundamentally, if you have your Ignition platform, you have a historian, you have the reporting module, you naturally have your device connectivity that’s provided with the gateway and the platform.

00:22:17.000 –> 00:22:22.000

And you potentially have perspective.

00:22:22.000 –> 00:22:38.000

Um, uh, perspective running from, from a client, from a client facing that, that’s your Ignition platform layer. Underneath that, you obviously have your field devices, your meters, your, uh, BMS controllers, building management, uh, controllers that would typically be BACnet, I think.

00:22:38.000 –> 00:22:43.000

Yeah, a lot for building. The energy module.

00:22:43.000 –> 00:22:57.000

sits on top? So the energy module sits on top of Ignition, um, provides the data for the visualization layer, pulls everything from the Ignition platform that it provides. So the cool thing is, any device that connects to Ignition.

00:22:57.000 –> 00:23:10.000

goes through its internal OPC UA server. Yes. So the only thing the energy module does… It’s exposed. It’s exposed, so we pull it into tags or UDTs, and then the energy module gets mapped to the energy module, and it’s got access to all of them. And this is where it becomes cool, I.

00:23:10.000 –> 00:23:31.000

You can, there is, I don’t want to say unlimited, but I’m going to say unlimited ways to get data into Ignition, right? We’ve got MQTT, we’ve got APIs, we’ve got, you can put in little PLCs already, we can put in almost everything from plant data and then we can start contextualizing everything. So I mean having, knowing when your power went up is one thing.

00:23:31.000 –> 00:23:46.000

But knowing it went up every time this recipe runs or this part of the plant runs or this time of the plant runs, that’s when we start getting contextualized data knowing, but it’s when these processes run, it’s when this happens during this process or this time of the day or this time of the week. And that’s where I think Ignition.

00:23:46.000 –> 00:23:48.000

provides the.

00:23:48.000 –> 00:24:06.000

massive difference yeah cool so from a uh install point of view it’s uh it’s it’s the mod file it’s the module file it’s the normal module file installs in sec on a Mac it would install in seconds on a Windows on a Windows it installs in many seconds.

00:24:06.000 –> 00:24:29.000

It is required to restart the gateway naturally. At 8.3. Yeah. So because so it’s only available in 8.3. It’s not available. 8.1. Just because of the the massive difference between 8.1 and 8.3. 8.3 was a fundamental year. Yes, 8.3 just provides a lot of benefit, to be honest, and 8.3 provides the platform for 2027 as well. Yes, it provides the the ground base.

00:24:29.000 –> 00:24:34.000

So I do advise anyone that’s not on 8.3 yet.

00:24:34.000 –> 00:24:47.000

it will change your life. It’s a massive difference, and if you think 8.3 is going to change your life, come to ELEV8. It will definitely change the way that engineers, developers.

00:24:47.000 –> 00:25:00.000

utilize, build troubleshoot and maintain your Ignition gateway. If you have, if you’re on 8.1, you’re not sure if you have.

00:25:00.000 –> 00:25:17.000

8.3, or access to an 8.3 license, let us know. We can easily check that for you. We can provide the details around the licensing if you’re not sure if you have access to 8.3. That’s an easy and quick check. So should we… should we get into it? I think I want to start sharing. Yeah, let me…

00:25:18.000 –> 00:25:19.000

Sheila.

00:25:19.000 –> 00:25:21.000

the compulsory.

00:25:21.000 –> 00:25:26.000

PowerPoint slides which we’ve done now. We always prefer to show the.

00:25:28.000 –> 00:25:29.000

Share.

00:25:33.000 –> 00:25:35.000

Okay.

00:25:35.000 –> 00:25:37.000

My screen.

00:25:37.000 –> 00:25:46.000

I’m not sharing anymore. Am I? No. No. Okay, good. Cool. Okay. So we’ll start with the dashboard just to.

00:25:46.000 –> 00:25:49.000

grab everyone’s attention again before they doze off.

00:25:49.000 –> 00:26:01.000

done with PowerPoint. So what we’ve got here, we’ve got our… this is our public demo, energydemo.element8.co.za. This is the same demo gateway backup file that you get with.

00:26:01.000 –> 00:26:03.000

the module download.

00:26:03.000 –> 00:26:15.000

So this is what you’ll be getting when you download the module and restore the Gateway backup. So what we’ve got is we’ve got 3 sites. We’ve got a residential site with 4 floors, 2 flats per floor.

00:26:15.000 –> 00:26:23.000

We’ve got a manufacturing site called 8CAIC, and then we’ve got a nice little data center situated in Paris.

00:26:23.000 –> 00:26:38.000

That, uh… Data center in Paris. A data center in Paris. Extremely accurate. This is not Paris, Paris. I don’t think there are any DCs in Paris, but I like the idea of it. Uh, we wanted to keep it local.

00:26:38.000 –> 00:26:45.000

1. Hello, Brian. Sorry, I forgot to say hello to Brian this morning. Brian from Zoom.

00:26:45.000 –> 00:26:49.000

Welcome. Happy to have you join us, Brian. Sorry, I wanted to say hello.

00:26:50.000 –> 00:26:52.000

Um…

00:26:52.000 –> 00:27:08.000

So what we’ve got is this is the 8K dashboard. As you can see, we’ve got a few nicer looking charts that you might usually have in Ignition. This is just an open library called OpenCharts. It’s Apache charts. It’s got Apex charts.

00:27:08.000 –> 00:27:14.000

free library that you can use for charts. Um, you do need that module as well, too.

00:27:14.000 –> 00:27:36.000

restore the gateway but it’s it’s a free one once again 2027 new charting components yes Apache charts I think there’s 16 new charts yes and and it can do everything you see on here they’ve got in there I think there’s a Sankey chart there’s a knowledge graph yeah so uh the new charting component is actually something I’m I’m very excited about.

00:27:36.000 –> 00:27:54.000

So come to ELEV8. Okay, so we’ve got Sankey chart. This is our solar forecast versus actual. As you can see, my days run perfect every day. So this is definitely a simulator. So just a quick thing on the Sankey chart. So I think the, the value of the visual value of the Sankey chart is always understanding the.

00:27:54.000 –> 00:28:01.000

the bulk of the… of the value where it’s flowing, so naturally through the hierarchy that we’ve built.

00:28:02.000 –> 00:28:10.000

Uh, you have the ability to understand where the flow within the Sankey chart is… Yes. …going per either area or…

00:28:10.000 –> 00:28:20.000

or, uh, depending on how you set up the hierarchy of your operation or your facility. Yes. Very nice. So this is very cool. And then there’s a different type where you can actually…

00:28:20.000 –> 00:28:27.000

You can see it in this way, where it starts from the main, goes through the first floor, and then it splits it.

00:28:27.000 –> 00:28:35.000

And you can actually follow it as it goes through. Depending on the granularity that you’ve defined and set up. I love that. And this is our R quadrant. This is all…

00:28:36.000 –> 00:28:44.000

So, the nice features, the nice look and feel you see here, that’s Ignition. The data you see, that’s the module.

00:28:44.000 –> 00:28:52.000

Okay, so here we can just click on different ones. We see different values. I was still on the on the the main dashboard.

00:28:53.000 –> 00:28:57.000

Sorry for for for each one. Just the the over.

00:29:00.000 –> 00:29:10.000

I see you’ve added water and gas. So the module is energy? Yes. Right, so energy… Any utility… Any utility. Could be used. Um…

00:29:10.000 –> 00:29:15.000

So there is different ones. As you can see here, we also do the similar sand gears in the heights.

00:29:15.000 –> 00:29:20.000

Where you will start with a pipe plant and then the water will show you where it flows.

00:29:20.000 –> 00:29:22.000

And you’ve also got usage.

00:29:22.000 –> 00:29:41.000

And then we’ve got our consumption ranking, usage. I like that. That’s a great idea. And then gas would be the same. And as far as KPIs go, you would want to understand primarily consumption and cost. Those would be, I would imagine, the two top… That would be your two top, but like, again, it’s Ignition.

00:29:42.000 –> 00:29:57.000

You build what you want. But I like it. I like the view standard. Data center looks — Is this included in the — Everything included. Even the simulation program is included. So you get the same data.

00:29:57.000 –> 00:30:00.000

Just to start tasting.

00:30:00.000 –> 00:30:02.000

So this is the data center.

00:30:02.000 –> 00:30:04.000

Then we’ve got the whole…

00:30:04.000 –> 00:30:14.000

just to see the different graphs for each power trend. And then we do include like a small thing where you can just open them up one by one. Very nice.

00:30:15.000 –> 00:30:17.000

And then we’ve got heat maps.

00:30:19.000 –> 00:30:21.000

Oh, heat maps always nice.

00:30:22.000 –> 00:30:25.000

I mean, you guys can…

00:30:25.000 –> 00:30:39.000

I’ve seen people play. So… Slower. Before… yeah, I see, this one’s a bit slower than here. Um, okay, so before we go any deeper, this is the dashboard, like I said, dashboard’s perspective, data’s the module.

00:30:39.000 –> 00:30:41.000

Okay, so…

00:30:41.000 –> 00:30:46.000

Before we go any further, one thing people ask, this is, um…

00:30:46.000 –> 00:30:58.000

Definitely an energy monitoring module. But the first thing we get asked is power quality. Power quality, yeah. Right. So it’s not a power quality module.

00:30:58.000 –> 00:31:10.000

It’s not gonna provide you with deep insights into power quality. Because a lot of the vendors they, I wanna say, lock down their power, power, quality data through.

00:31:11.000 –> 00:31:24.000

through their proprietary. Yeah, it is proprietary. But, uh, there is an IEC standard, which I can’t remember the name of, where they have to store the COMTRADE files, I think it stands for Common…

00:31:24.000 –> 00:31:42.000

transient data exchange. Common transient data exchange. So we can get access to those files. And those files you can access from the meter itself, you can plug in USB, copy it over. So it’s like a small FTP file transfer protocol server that lives on the meter. So what we did in the module was…

00:31:42.000 –> 00:31:51.000

create an automated FTP client. So, here you would have your module, as you see there, it says it’s installed here in Energy Monitoring.

00:31:51.000 –> 00:31:57.000

This one is activated just so that everyone knows we’ve got a documentation option.

00:31:57.000 –> 00:32:15.000

Where if you click on documentation, brings you the user manual. Oh. The entire module. So this is offline, so it’s built into the module. That’s convenient. Yeah. So you can access the entire user manual on site without having to download anything as long as it’s installed. Really, really comprehensive documentation, which is nice.

00:32:15.000 –> 00:32:29.000

It’s always nice. You always have to keep up with Inductive and with those things. Yeah, documentation is generally top class. So this is the dashboard, uh, that you get when the module’s installed. It just shows you everything that’s been, um.

00:32:29.000 –> 00:32:44.000

everything that’s been configured inside of your system. So this is our project. So it is project based. The module is project based. So you can assign one tag provider per project, and that’s the tag provided with use for that project.

00:32:44.000 –> 00:32:50.000

Because if you’ve got the same UDT over different projects, you don’t want it to become.

00:32:50.000 –> 00:32:55.000

They don’t, you want them to start cashing with each other. So, COMTRADE sources.

00:32:55.000 –> 00:33:07.000

this one’s now obviously failed, but this would be the automated FTP client, where you can say the… the name of the… there’s a few pre-configured ones, where you know the order. Will you fetch the…

00:33:07.000 –> 00:33:25.000

This is where you fetch the COMTRADE files. You can put in the host and the port. These are the more popular ones available, I would imagine. Yes, yes. This is the ones we could actually test with. And then you can choose custom, and then you would just need to specify the folder name and format, comma separated.

00:33:25.000 –> 00:33:30.000

And then you save, use TLS, everyone I’m sure that will do this knows this.

00:33:30.000 –> 00:33:47.000

Oh, no. Cancel. And then you can access the waveforms. Okay. And then if you’re someone that knows power quality, there’s waveforms. Which I certainly am not. Yeah, no. I’m sure these waveforms mean something to you. They don’t mean anything to me.

00:33:47.000 –> 00:33:53.000

Lovely. Um, but you can access them, you can interact with them, and this is all available.

00:33:53.000 –> 00:33:54.000

on the…

00:33:55.000 –> 00:34:03.000

front end as well. So, all the power quality meters are here as well, and you can assign the power quality meter to a meter in the tag.

00:34:03.000 –> 00:34:20.000

browser as well. Yeah. So then, when it does power quality report, it will use the power quality data provided from the COMTRADE files. Very nice. This is it. I’m sure it will improve in the future. Any other files that might be stored on meters, I know they do some offline logging, maybe in the future, if it’s disconnected, this will be something.

00:34:20.000 –> 00:34:25.000

For now, this is it, and I think this is a good starting point. Once again.

00:34:25.000 –> 00:34:29.000

Ignition 2027, a page like this.

00:34:29.000 –> 00:34:41.000

can easily be analyzed through something like AI, and if you get your hands on Ignition 2027, it would be awesome to test it. It will be, yeah. So…

00:34:41.000 –> 00:34:48.000

I think we can dive into the designer now. We’ve seen all the nice front-end things. Just gonna… I don’t wanna…

00:34:48.000 –> 00:34:52.000

I think it’s a good overview, and it’s a good comprehensive overview, and probably…

00:34:53.000 –> 00:35:01.000

a popular layout to, I think, what would serve most people, so it is nice that it’s provided.

00:35:01.000 –> 00:35:03.000

And you can customize it.

00:35:03.000 –> 00:35:08.000

I see we’ve got a question. Yeah, I’ve got a question.

00:35:08.000 –> 00:35:23.000

Good day all and thank you for this amazing feature. I would like to know if there is a trial version of the energy monitoring module just to practice from Ivan Rubo. So Ivan is asking. Yes.

00:35:23.000 –> 00:35:35.000

if there’s a trial version of the energy monitoring module, just to practice. Thank you for the question, Arvind. Yes. So, Arvind, while you’re asked, let’s quickly go through it. You go onto Inductive’s website.

00:35:35.000 –> 00:35:42.000

Right, everyone, I’m hoping, knows this website. As you can see, even they starting, it’s Ignition 2027.

00:35:42.000 –> 00:35:47.000

We go to Product, and then you go Third Party Module Showcase.

00:35:47.000 –> 00:35:52.000

On the third-party module showcase, you can either search…

00:35:52.000 –> 00:35:56.000

Where you can, like me, go down, energy monitoring.

00:35:57.000 –> 00:36:01.000

When you say buy, it’s actually going to take you to download.

00:36:01.000 –> 00:36:05.000

Okay, and then you can download the module there.

00:36:05.000 –> 00:36:20.000

and it gives you the normal 2-hour access that you would have with normal Ignition. You can test as much as you want with it, gives you the backup, and you can… you can build everything. Once again, only buy the license when you’re ready for production. Fantastic. Thank you.

00:36:22.000 –> 00:36:37.000

So when we install the module, we open the designer. This is how it looks. Not all the question marks, not all the exclamation warnings. You get a new project resource called Energy Monitoring. Lovely. Available in the tree. In the tree.

00:36:37.000 –> 00:36:51.000

Nice. Built-in. So… In the project browser, it stays visible, blast. So this would be your UDTs. For me, uh, this is the UDTs that come with the module. So, I’m just gonna open one to show you quickly how you would map it. It’s really simple.

00:36:51.000 –> 00:37:05.000

This section gets added when you install the module, so up until here, energy monitoring, this is all still part of Ignition. Correct. So, like I said, it fits into Ignition quite easily, it looks like the rest of Ignition, works like the rest of Ignition.

00:37:05.000 –> 00:37:16.000

the only thing you need to do is say, yes, energy monitoring, I want it part of energy monitoring. So if you don’t want an energy… a UDT part of energy monitoring, this needs to be false. And it’s…

00:37:16.000 –> 00:37:18.000

By default. By default, false.

00:37:18.000 –> 00:37:28.000

So then you choose your utility type power, water, gas. You give it a name most of the time. It’s easier just to map it to the name of this.

00:37:28.000 –> 00:37:35.000

thing of your UDT, and then you can give it a role. Okay, consumption, generation, storage, credit, time, storage.

00:37:35.000 –> 00:37:52.000

There’s battery generation generators or solar wind. Okay, and grid inside is when we’ve got connected to a grid. We’ve got solar coming in. So that will be our inter time. And of course, consumption. Yeah. And then consumption would probably be the one that’s.

00:37:52.000 –> 00:37:56.000

Which most and that’s why it’s probably the default.

00:37:56.000 –> 00:38:07.000

Then… okay, mine’s easy. Mine’s called Current, okay, so it’s a very easy one to map. So, I’ll go down, and you’ll say Variable Assignment is Current A.

00:38:07.000 –> 00:38:18.000

So yours might be called C or CUR, or maybe it’s a weird name you would drop down and assign it to.

00:38:19.000 –> 00:38:26.000

So if this is power, you would assign it to active power. Single phase, we always assign to A, but…

00:38:26.000 –> 00:38:35.000

Once again, people that do power, I hope they know. They know. I’m sure they know. Okay? And then, as you know, energy active.

00:38:35.000 –> 00:38:50.000

and delivered or net. You can say for my in my case this one resets every day, because my simulators reset every day. Most of the time it is a cumulative total.

00:38:50.000 –> 00:39:01.000

meter energy active. Um, so you would put it on lifetime, and then it would just count, count, count. The module actually already, if…

00:39:01.000 –> 00:39:16.000

The value, okay, totalizes, totalizes. At some point, there might be a point where it resets because the register in the meters, it does account for that. So it takes the last known biggest value and then adds the new ones to it. So it’s done. It does that for you.

00:39:16.000 –> 00:39:21.000

Okay, so this is the UDT, right? We configure the UDT, we do everything in here.

00:39:21.000 –> 00:39:23.000

Now…

00:39:23.000 –> 00:39:35.000

for history and tag groups. I’m gonna say a few things. Now, this is based on Ignition. If you only want this thing to pull data from the OPC server every 15 min.

00:39:35.000 –> 00:39:42.000

You can do that. Create a tag group for it. This is normal Ignition based practice. If you want it to be.

00:39:42.000 –> 00:39:48.000

every, like, this is the default tag group, so it’s gonna pull quite often. Then…

00:39:48.000 –> 00:39:55.000

history. Right? So we save this data. We need to save all the data. That’s the only way we can do our reporting.

00:39:55.000 –> 00:39:57.000

You can…

00:39:57.000 –> 00:40:08.000

choose everything that’s inside of Ignition. So we’ve got our deadband modes. Okay, absolute percent or off. And then we’ve got our deadband style, analog or discrete.

00:40:08.000 –> 00:40:11.000

Now, once again, something like…

00:40:11.000 –> 00:40:26.000

voltage. Let’s say 3 phase voltage. That’s 380. You would maybe only want to historize that value when it shoots up by maybe more than 10 volts or drops below 10 volts. But you wouldn’t want it to historize when it goes.

00:40:26.000 –> 00:40:36.000

the 380.01, 380.02, 380.01. And this is where deadband styling and setting up your deadbands is very important, and not just for energy.

00:40:36.000 –> 00:40:40.000

for Ignition. It’s best practice in Ignition.

00:40:40.000 –> 00:40:49.000

So, but there’s a lot of options. You can do the sample mode on change, you can do it periodic, or you can do it on the tag group if you’ve already set up a tag group.

00:40:49.000 –> 00:40:58.000

So periodic means every few minutes on change for something that’s maybe more important. When it changes, we want to historize. And then the date bands is important as well.

00:40:58.000 –> 00:40:59.000

Okay.

00:40:59.000 –> 00:41:06.000

So this is the… the UDTs, and then all we do is we create instances of those meters.

00:41:07.000 –> 00:41:13.000

For me, I created my hierarchies here as well. It’s easy to follow, you know where they are.

00:41:13.000 –> 00:41:20.000

Now, we’ll quickly go into the logic meter and virtual meter, because it’s a quite important one. Okay.

00:41:20.000 –> 00:41:22.000

Logic meter.

00:41:23.000 –> 00:41:34.000

is a meter that, for all intents and purposes, doesn’t exist on your plant, but in Ignition, it will exist as an actual physical meter.

00:41:34.000 –> 00:41:45.000

Okay, which means when you create that logic meter, which will be technically an expression tag meter for Ignition, we just make it a lot easier.

00:41:45.000 –> 00:41:50.000

You, it would get historized, it would be part of the system.

00:41:50.000 –> 00:41:55.000

Okay, so you create a logic meter, use the UDT type.

00:41:55.000 –> 00:42:02.000

sum, difference, average, max. Custom means there’s an expression editor, and you can just express.

00:42:02.000 –> 00:42:08.000

then we’ve got tags, and you can choose the tags you want to add on the song, okay? It would then add…

00:42:08.000 –> 00:42:24.000

Those tax free together. We keep to Ohm’s law so voltage won’t get added together. Hopefully not. If you add five meters, it’s not going to, it’s not going to add everything together for you and have a thousand volts on three phase.

00:42:24.000 –> 00:42:26.000

But…

00:42:26.000 –> 00:42:27.000

um…

00:42:27.000 –> 00:42:33.000

Keeps to the laws, but the nice thing about the logic meter is if you don’t have a meter.

00:42:33.000 –> 00:42:50.000

that is over maybe 3 parallel meters. Yes. It’s there, and you can… it can get historized, and maybe you want to do it in the future, um, but for now, it’s not there, the expansion’s not there. Or you can also split, partition it, and say, you know what, this is our main meter, I know for a fact.

00:42:50.000 –> 00:42:59.000

In this side of the plant, it’s 30% of this meter, and you can create that for you, even if it’s just to test. Very nice. It is cool.

00:42:59.000 –> 00:43:14.000

So it’s a logical meter. It’s technically virtual, but it’s virtual in your plant. It’s real in Ignition. It gets a meter ID that gets assigned to it, meaning if you change the path, the meter ID stays static. Meter IDs are always unique. It’s unique meter IDs.

00:43:14.000 –> 00:43:26.000

move them around… So if you move them around in Tag Browser, when we query, it looks at the meter ID, finds all the instance paths for that meter ID, and it uses them for the… That’s very nice.

00:43:26.000 –> 00:43:33.000

Then in energy monitoring, now we’ve got a virtual meter, as if the logic meter wasn’t confusing enough.

00:43:33.000 –> 00:43:36.000

So we’ve got a virtual meter that…

00:43:36.000 –> 00:43:42.000

acts the same, but nothing ever gets stored in the historian ever. Okay.

00:43:42.000 –> 00:43:58.000

So the only time this virtual meter gets executed is when it’s part of an equation or calculation or a reporting request. So what this means is if I create a virtual meter now and I say you are the sum of these two meters.

00:43:58.000 –> 00:44:00.000

And I go 6 months back.

00:44:00.000 –> 00:44:17.000

It can give me the entire sum of those two meters for six months back. If next week I say, okay, listen, but you are the sum of these three meters, it will still go six months back and add the sum of those three meters. So this is also nice to validate against the meter if you’ve got a very important meter running.

00:44:17.000 –> 00:44:37.000

You can create a virtual meter that you know this meter in the plant is the sum of these three meters. So I’m creating a virtual meter that’s also the sum of those three meters. That would probably be the most popular use case. It is probably a popular one. And you would actually see when they discriminate quite against each other. And you would say, okay, now there’s discrepancies. I need to see what’s going on. Maybe the CTs are blown. Easy to throw.

00:44:37.000 –> 00:44:48.000

and throw in a virtual meter. And it’s… and it’s also, if something’s faulted, you can quickly create a virtual meter, just so you can even maybe do your billing. And something like… and something like…

00:44:48.000 –> 00:45:05.000

spikes. I almost want to call it anomalies, anomalies, but pick it up the discrepancies, and you can easily see it. If you trend them, you would see a big difference between the 2. Of course. Once again you can trend them manually, or you can get Ignition 2027. Get an agent to trend it for you.

00:45:06.000 –> 00:45:18.000

It’s gonna be different, guys. It’s gonna be different. Okay, so this is our meter instances. We can enable, disable here. If it’s a power quality meter, we can tick the box and then assign it to a power quality device.

00:45:18.000 –> 00:45:28.000

Here, we can already assign it to time of use schedules. If you don’t want to put it in a hierarchy or a tariff plan, you only want time of use schedule for this meter, you can assign them here.

00:45:29.000 –> 00:45:34.000

Then, this is where we do our tariff plans and time of use schedules.

00:45:34.000 –> 00:45:40.000

Looking forward to see what you guys do with this. We’ve got… this one doesn’t have inputs, just got rules.

00:45:40.000 –> 00:45:45.000

Where we just split between the rates as it goes or it becomes more.

00:45:45.000 –> 00:45:51.000

the… the cool one, I think it’s the capacity, yes. So if the capacity contracted.

00:45:51.000 –> 00:45:54.000

And we look at kVA.

00:45:54.000 –> 00:45:59.000

If it is greater or equal to 1,000, we use this tariff.

00:45:59.000 –> 00:46:09.000

We for standard supply. We always use this tariff and then excess capacity. So these are add ons. We need to do a report. It would add service charge, excess capacity and peak demand charge.

00:46:09.000 –> 00:46:21.000

So, looking forward to people using this, telling us how it can be improved, maybe. Maybe there’s a few things that can get added, can get removed, can be easier. I know people that work with these things every day.

00:46:21.000 –> 00:46:27.000

Their minds look very far into the future. So it’s very cool.

00:46:27.000 –> 00:46:29.000

And then we’ve got time of use schedules.

00:46:29.000 –> 00:46:49.000

Yes. We’ve been spoken… we’ve been speaking a lot about that. We can have any number of schedules. Any number of schedules, you can have… we’ve got 2 seasons, you can create 20 seasons, um, you assign your season start dates and end dates, and then your period start dates, end dates, and then the rates. Lovely.

00:46:49.000 –> 00:46:55.000

You can also say demand charge on… it’s really… it’s not meant to be confusing, I hope.

00:46:56.000 –> 00:47:01.000

Water gas, it’s really, it’s quite easy. You can export the JSON, import the JSON.

00:47:01.000 –> 00:47:07.000

Once again, everything here script based, so we can say system.

00:47:10.000 –> 00:47:17.000

Ah, there we go, all available. So you can also get your time of use schedule from here, if you want to show it on the…

00:47:17.000 –> 00:47:19.000

perspective side.

00:47:19.000 –> 00:47:22.000

So everything, everything, everything is here.

00:47:22.000 –> 00:47:27.000

There’s our TOU rates, our total cost TOU versions.

00:47:27.000 –> 00:47:30.000

So everything is in the script. And again, this is…

00:47:31.000 –> 00:47:37.000

It’s versioned and… Versioned as well, that’s where this change effective from gets stored in a small SQLite database.

00:47:37.000 –> 00:47:44.000

and then internal on the gateway itself. Then you put in your holidays and now you bill your holidays.

00:47:44.000 –> 00:47:49.000

Where they get the holiday day or. You wouldn’t need more than this.

00:47:49.000 –> 00:47:51.000

Then…

00:47:51.000 –> 00:47:55.000

We can look at the historian editor quickly.

00:47:55.000 –> 00:47:59.000

So you saw an editor where we are questioning the quality.

00:47:59.000 –> 00:48:18.000

quality gaps, you know, uh, comms failures, um, maybe device failures, um, there’s a lot you can do, maybe one CT failed in the… this is now actually where the virtual meter can actually assist you, right? So you had the virtual meter, it was running, a CT failed on the, on the device. Immediately you’ll see. Now.

00:48:18.000 –> 00:48:33.000

our historian data is… let’s call it corrupted, but wrong. Yeah. Not corrupted, but… Not corrupted, but… but it’s wrong. Um, now we can use the virtual meters data, and assign that to this meter, and… and we know… now we’ve got data that we can work with. Yeah.

00:48:33.000 –> 00:48:38.000

I just want to minimize this. So if we select, let’s say this was empty.

00:48:38.000 –> 00:48:47.000

We would say full selection, and there’s your options, interpolation, average of the top and bottom one, or formula.

00:48:47.000 –> 00:48:54.000

Where they tell you V1 and V2 is the top and bottom anchor values, T is the time position, I is the point index.

00:48:54.000 –> 00:49:11.000

If this doesn’t… if this looks confusing, I hope it doesn’t. This is normal, linear… I think linear interpolation is probably… But a lot of people would probably use it. What you would use by default. And then you can say whether it should override the rows that already have data, or only use the ones that have no data. No data. That’s probably the…

00:49:11.000 –> 00:49:28.000

Better option to tick. Then you can save. When you save, there’s an audit trail. So the audit trail would say edited at, edited by, which instance, the variable, data stamp, old value, new value, the type, the reason. So it’s a very big audit trail that gets saved as well.

00:49:29.000 –> 00:49:31.000

OK and then.

00:49:31.000 –> 00:49:36.000

This is it for what you can set up. Sorry, no, we’ve got our favorite one.

00:49:36.000 –> 00:49:38.000

Oh, yes, the hierarchies, yeah.

00:49:38.000 –> 00:49:55.000

So the hierarchies is the fun part. You can actually… you would probably set this up similar to your tag browser, I hope. Unless in your tag browser, you would do it a different way. But here, you can put it exactly how it is in the plant, and then your node types would be meter, site, area, building. This is more…

00:49:55.000 –> 00:49:59.000

This is more just for you to see.

00:49:59.000 –> 00:50:17.000

So I see we’ve got a question. Yes, we do have a question. So Hansel, bit of an oddball question. No such thing as an oddball question. For EPCs, energy performance certificates for offices and government buildings since 1544.

00:50:17.000 –> 00:50:24.000

now being a legal requirement, sometimes there is a need to run sub-metering data collection projects.

00:50:24.000 –> 00:50:39.000

for a year, which is they could be moved to another site. They could be moved to another site. Wouldn’t ignition basic plus energy be feasible? Yeah, sure. I mean, the only thing the energy module needs from Ignition is one the platform.

00:50:39.000 –> 00:50:55.000

the most important part, and then, depending on the functionality you want. The historian is is the most important one, because we need history. And then from there we need a visualization tool and the reporting tool. And it would be.

00:50:55.000 –> 00:51:07.000

mobile, kind of a roaming… For you, it would probably be you’d install it on a… I would call… I would probably call it a portable server. Yeah. And then connect your meters to that, and sure, it’s definitely feasible, in fact… And you have the history…

00:51:07.000 –> 00:51:14.000

it might be, it might actually be a very cool project. Yeah, sounds really cool. Nice application case. Didn’t think about that. Definitely.

00:51:14.000 –> 00:51:17.000

Thanks, Hansel. Thanks, Hansel.

00:51:17.000 –> 00:51:32.000

So yeah, we’ve got our node types. Like we said, it doesn’t really do anything to the calculations or reporting. You can just see whether the node is a site area building. This is more from a readability point of view. And obviously the granularity that you want.

00:51:32.000 –> 00:51:34.000

Yes. Yeah.

00:51:34.000 –> 00:51:38.000

So and then you can select your meter here.

00:51:38.000 –> 00:51:41.000

It’s split up by the UDT type.

00:51:41.000 –> 00:51:47.000

And then you can say time of use schedule if it’s a different one, otherwise default for everything would be…

00:51:47.000 –> 00:51:52.000

Whichever one you choose, you’re on top. And then you can also use your tariff plan.

00:51:52.000 –> 00:51:56.000

You can add nodes, rename, remove, go crazy.

00:51:56.000 –> 00:51:59.000

Okay, so this is everything you can set up in the designer.

00:51:59.000 –> 00:52:09.000

Then from here, we get to the fun part, where we want to create reports. So in the backup, we’ve got multiple reports.

00:52:09.000 –> 00:52:14.000

As you can see here, this is the energy monitor example, so I’m going to delete this one.

00:52:14.000 –> 00:52:24.000

So again, native, under reporting, under reporting. Built into Ignition. You would probably never want to create all of these reports. Wow.

00:52:24.000 –> 00:52:33.000

Uh, so what you would rather want to do is… there’s a new tab at the top called Energy Monitor when you install the module. Say, add examples.

00:52:33.000 –> 00:52:38.000

And you can click. Well, okay, 66 reports. So this is.

00:52:38.000 –> 00:52:45.000

Pretty much from the most popular common that you would come across to some really, I see there’s even some.

00:52:45.000 –> 00:52:57.000

KPI by time of use reports. Yes. Relating to a specific asset, I would think, for example. Jeez, okay.

00:52:57.000 –> 00:53:03.000

So there’s really, there’s a few. I don’t even know what some of those acronyms mean, Markus. Yeah, yeah.

00:53:03.000 –> 00:53:06.000

But I’m not a Pi expert.

00:53:06.000 –> 00:53:09.000

So, this is really, um…

00:53:09.000 –> 00:53:13.000

It’s meant to make development easier.

00:53:13.000 –> 00:53:20.000

So, you can choose billing report, you can say… oh, let me just quickly show… I do like, uh…

00:53:23.000 –> 00:53:40.000

People would like to see it. If people are prepared to share or request, I mean, they are welcome to. Hansel, yes, we will be sharing a recording of the webinar. Was there a couple of links? And a couple of links. A lot of links.

00:53:40.000 –> 00:53:44.000

Oh, we have another question. Let’s quickly cover that one.

00:53:44.000 –> 00:53:56.000

uh, via… I have joined… is it possible to schedule another meeting where I have a recorded meeting? Yes, we will absolutely, um, share a recording, and I do see you have some…

00:53:56.000 –> 00:54:02.000

Additional questions. Yes, it will require on-site on-prem.

00:54:02.000 –> 00:54:04.000

Um…

00:54:04.000 –> 00:54:22.000

Can we use the device platform for data logging consumption against the City of Tshwane? Absolutely. You can configure that accordingly. So we can share recording and we can schedule a meeting. We can do both share recording. Yes, to your questions of I/O. And we could probably set up some time with you to go through some of the some of the detail.

00:54:22.000 –> 00:54:24.000

Thank you.

00:54:24.000 –> 00:54:38.000

So a lot of people, so you get your native PDF reports, which are nice, right? We didn’t even show them. Yeah, you can schedule email. Yeah, I mean, so this is the reporting tool by Ignition.

00:54:38.000 –> 00:54:41.000

There’s the report viewer.

00:54:41.000 –> 00:54:51.000

Uh, this is how the reports look. I mean, this is, this is what we, this is what we know in Ignition. This is our reporting tool. Okay, PDF reports, you can download, schedule, send emails, send wherever you want.

00:54:51.000 –> 00:55:02.000

A lot of people like the new HTML based reporting and startup perspective. I mean, we like working with web. So you can choose both. You want the billing report and the reports.

00:55:03.000 –> 00:55:16.000

And I want the billing report in perspective. That is very nice. So we’ve got both. So we’ve got them in reports and we’ve got them in perspective. So you can say add two to project and it tells you both has been added. So if you look on the reports. Show us.

00:55:16.000 –> 00:55:18.000

Now I have a billing report.

00:55:19.000 –> 00:55:23.000

which has already been pre-configured.

00:55:23.000 –> 00:55:34.000

Okay, so this is the data source now for billing. As you can see, those that do use Ignition, everything that’s not EM you would have never seen before, this is not part of the module.

00:55:34.000 –> 00:55:41.000

So these are just a few extra data sources that make it easy for you to build reports using them.

00:55:41.000 –> 00:55:45.000

And then you’ve got the design that’s been pre-built for you. Billing report.

00:55:45.000 –> 00:55:52.000

And you can just go. Same with perspective. Under views, energy monitor examples, we now have a billing report.

00:55:53.000 –> 00:55:58.000

So, this is the billing report. My… I’m always in dark mode.

00:55:58.000 –> 00:56:00.000

Okay.

00:56:00.000 –> 00:56:01.000

Let’s do light.

00:56:02.000 –> 00:56:16.000

This is the billing report. If I would want to see the billing of, for example, this room or this flat, I would just say copy path.

00:56:17.000 –> 00:56:19.000

Paste the meter.

00:56:20.000 –> 00:56:26.000

Okay, they’ve got billing. So because the time of use schedule has been assigned to the meter, it uses that.

00:56:26.000 –> 00:56:35.000

I want to use a different time of use schedule on this report for the meter, not the one that’s always used for it. You can copy a path of a different one. Yeah.

00:56:35.000 –> 00:56:39.000

Go back to where we were. Any other schedule, yeah.

00:56:39.000 –> 00:56:45.000

and then in the time of use. Note paste it, and.

00:56:45.000 –> 00:56:46.000

different results.

00:56:47.000 –> 00:57:01.000

Yeah, different result. It is different, yes. Yes. So we can take it out. It’s different, but it is different, yes. And then you can see it changes in values. Very nice. So this is the billing report. That’s useful, that’s useful. We can save… yes, see.

00:57:01.000 –> 00:57:04.000

I’m going to go here. Sorry.

00:57:05.000 –> 00:57:10.000

That is now because I’m editing over networks.

00:57:10.000 –> 00:57:12.000

Uh, we can launch…

00:57:13.000 –> 00:57:17.000

And when we launch, this is now in perspective. Lovely.

00:57:17.000 –> 00:57:21.000

I think a live screen is definitely…

00:57:23.000 –> 00:57:30.000

Definitely. But still a very big requirement to have PDFs received on email, for example.

00:57:30.000 –> 00:57:41.000

or something delivered on email, which is pretty, which is a daily, a weekly, it’s consistent, it’s there, but the live HTML always looks nicer, doesn’t it? They are running.

00:57:41.000 –> 00:57:49.000

of time. So I quickly want to show everyone how this can look in a plant feature. We’ve shown you a nice dashboard.

00:57:49.000 –> 00:57:52.000

Now we’ll show you hopefully a nice.

00:57:52.000 –> 00:58:04.000

Cool. This is a mining application. So this is now a copper mine. If you’re a mining expert. I won’t take any criticism.

00:58:04.000 –> 00:58:20.000

I’m not a mining expert, so I won’t even listen to it. But this is we were just trying to show you. So we’ve got a mine running, crushing and screening, milling. We’ve got some utilities coming in. We’ve got a flotation section, thickening and dewatering. So typical.

00:58:20.000 –> 00:58:32.000

You can view the areas, this is just a nice way of viewing them. We can click, you know, we try to make it as practical as possible. Then we can go to energy.

00:58:32.000 –> 00:58:42.000

And what we’ve got another question from another question, does it have capabilities to integrate with solar PV. And that is.

00:58:42.000 –> 00:58:44.000

Yes.

00:58:44.000 –> 00:59:01.000

It can. Yes, if you’ve already got battery backup skaters, different skaters. It can connect to whichever OPC server they’re connected to as well, because when Ignition Ignition can pull data from other OPC servers and pull data into here as well, and then work with that data.

00:59:01.000 –> 00:59:19.000

probably, if we… if we… we can do it, uh, in the next 3 minutes, uh, we could probably share the link with the Solar and BESS… I’m not sure if the BESS is in the… BESS is not on yet. We could probably share a link with the Solar PV demo. The nice thing about the demo is that it’s production ready, and it’s downloadable.

00:59:19.000 –> 00:59:28.000

you could probably download that, possibly download the module, and integrate then. So you can actually see from this demo.

00:59:28.000 –> 00:59:34.000

We’ve got a small PV plant running. So the PV plant is…

00:59:34.000 –> 00:59:50.000

Not the biggest part of this. But here you can see what’s using the most in the plant all the way down. To which pump an ICC to an asset level. So this is the same type. So this is KPIs. Like I said, we’ve got Ignition and now the module just adds.

00:59:50.000 –> 00:59:54.000

some extra value to that. Got a small heat map here at the bottom.

00:59:54.000 –> 00:59:58.000

We can open the single line diagram.

00:59:58.000 –> 01:00:04.000

Once again, I’m sure for some people this is nice, for some people this is overwhelming. No, of course, of course.

01:00:04.000 –> 01:00:08.000

But you can see everything you want to see here from the single line diagram.

01:00:08.000 –> 01:00:11.000

Then we’ve got an energy explorer from the module.

01:00:11.000 –> 01:00:21.000

And click on different sections of the plant, see the demand and consumption, the child nodes. So you can get a very good view of consumption.

01:00:21.000 –> 01:00:38.000

percentages per asset per plant area where there’s potentially… And this would be the tariff and billing, if you want to put it on perspective. And then, once again, remember, when Ignition, you don’t want an operator to see this, they don’t have to see it, right? It can be…

01:00:38.000 –> 01:00:40.000

Security based, access based.

01:00:40.000 –> 01:00:50.000

And then just a nice little, because we can in Ignition, solar plant. Beautiful. Got a solar plant.

01:00:50.000 –> 01:00:57.000

Uh, PV plant running with all the inverters. As you can see, this inverter is giving us an issue. Once again, simulated.

01:00:57.000 –> 01:00:58.000

don’t…

01:00:58.000 –> 01:01:12.000

slaughter me if it’s wrong. Lovely. I see the position of your, of your sun is live. It’s live, it’s 11. If this demo is ever live, you’ll see when it’s 4 o’clock, remember, uh, South Africa time, it will be…

01:01:13.000 –> 01:01:33.000

Closer, it moves around. Very nice. Okay. I mean, this is just, I think I’ve literally touched on a drop in the bucket, what’s possible. We can also have an alarm analysis. And this also brings in from, there you can see power fact, low power factor. Yes. Looking at inverters. So we can do alarming on the UDTs as well. We didn’t even speak about alarming.

01:01:33.000 –> 01:01:49.000

Because you can build your entire. Let’s assume everyone knows it’s part of Ignition. You can build your entire alarming pipeline around certain energy and power numbers. Exactly. And, for example, a page like this, the alarm analysis page that gives you an alarm health score.

01:01:49.000 –> 01:01:53.000

Comes directly from the Ignition Exchange, so it’s free.

01:01:53.000 –> 01:01:57.000

Very nice. And that is energy.

01:01:57.000 –> 01:02:02.000

nutshell. In a nutshell. Two minutes over. Well done. Two minutes. Yeah. Pushing to.

01:02:02.000 –> 01:02:10.000

get it down. Any any other questions, maybe from anyone on the call. Do you have any other questions?

01:02:11.000 –> 01:02:14.000

I think, Luan, thank you very much for sharing. I see you’ve shared all the…

01:02:16.000 –> 01:02:21.000

All the relevant things we spoke about. As we talk about it, you’ve shared it. Thank you.

01:02:21.000 –> 01:02:25.000

I don’t see any other questions.

01:02:26.000 –> 01:02:30.000

I’m gonna stop sharing for now. Yes.

01:02:30.000 –> 01:02:32.000

And I think we’ve got…

01:02:33.000 –> 01:02:37.000

It’s probably not necessary to share the slides.

01:02:37.000 –> 01:02:42.000

We can share. I think there is a summary there that we want to.

01:02:42.000 –> 01:02:44.000

Let me just open it up again.

01:02:59.000 –> 01:03:18.000

As soon as I can find it. So I hope this was valuable to anyone. Anyone that wants a session with us, more details on Ignition, on energy, on anything except Ignition 2027. We’ll only give you more information on Ignition 2027 at ELEV8. Yeah.

01:03:18.000 –> 01:03:25.000

But that will really change everything that you know, everything that you know about SCADAs and this industry.

01:03:25.000 –> 01:03:28.000

will become, will change, but it will…

01:03:28.000 –> 01:03:44.000

It’s going to be mind blowing. Yeah, it’s really going to be fantastic. There is a sneak right up about what you can expect in Ignition 2027. I think some of the live ICC demo videos. Yeah, there’s a few here and there.

01:03:44.000 –> 01:03:56.000

We’re really looking forward to sharing it with you at ELEV8 at the end of the month. But yes, this is energy and utilities management or energy monitoring. It’s a really nice purpose built application.

01:03:56.000 –> 01:04:08.000

maximizing and using all the capabilities that you have native inside of Ignition. That’s what’s really cool about it. Third-party module, we will, um… I think we’ve already shared where it is available and how you can.

01:04:08.000 –> 01:04:19.000

how you can get access to it, but we’d love to get your thoughts. We really like it, we’re really excited about it. Please share any thoughts or feedback once you’ve downloaded it, and I’m looking at some of our.

01:04:19.000 –> 01:04:34.000

experienced, um, Ignition users and customers, uh, to maybe download it and try it out. We would love to… to hear your thoughts on it. Definitely. And then the only other thing that I think we have left to share… is there anything else we have left to share?

01:04:35.000 –> 01:04:40.000

We’re really over time. And now I’m wasting more time. No, that was it. I think it was.