Meet SFG20 Mobiliser:The Fast Track Way to Mobilise Contracts in Moments

Paul Bullard: Hello everyone, and welcome to meet SFG20 Mobiliser. It's great you've all joined us here today, and we are really excited about showing you some of the functionality we've created under this new product. We really believe it's going to be a big help for industry, for a challenge that we're all very aware of.

Just to give you a bit of background first, though: SFG20 and where did it come from? So back in 1990, the Heating and Ventilation Contractors Association decided that there was a need to introduce some standards for their sector, and to do so, the Services and Facilities Group of the HVCA created the 20th publication.

This was the standard for maintenance of heating and ventilation equipment that became SFG20. As the standard evolved from that book into a PDF, which was stored on CD-ROM, the content then was published onto the internet back in 2007, and that was just a means of accessing the content through the web.

Then in 2012, SFG20 released its first application around its content, and that enabled people to start working with that content within their organisation through an online application. Then in 2024, SFG20 released Facilities-iQ, and this was the first true digitalisation of the content, providing you with some functionality that really enables your organisation to make use of that standard for them.

So you are working with the content and you are getting the most out of it. Now, SFG20 for many years has been known for their schedules. The schedules form part of the book, and now they're part of our digital transformation. So what is an SFG20 schedule? Now, SFG20 schedules are ultimately defined by their asset types and their codes. So if we start with asset type here, you can see this is a PV system. It's a specific type of asset, and that's where SFG20 goes down to – in terms of we're actually looking not at a particular manufacturer, but an overall type of asset for which we need to carry out maintenance.

That particular type of asset also has a code, and these codes are well known in industry. So where a specific code, in this occasion it's 4311, that references a specific schedule of SFG20. Each of these schedules also has tasks, and those tasks – you can see here, this is a circuit breaker switch, disconnectors – this is a specific task within an SFG20 schedule. Each schedule is made up of multiple tasks, and each of those tasks has some specific information around it. So, for example, if we look at the criticality, this particular task has been encoded amber. And if you look at SFG20, and the other thing for which we're well known, it's the traffic light system around maintenance.

So here we have an amber criticality. So this is something as a business we should do. This is an operational type of criticality, in that if we want to get the best out of our asset and prolong its life, we should be looking at carrying out this maintenance. We also have a red criticality for statutory and a green criticality for those discretionary maintenance items.

Each of these tasks also has a specific timing, so the timing will tell us an estimation of how long this would take us to carry out this particular piece of work. I think it's important that the timing doesn't include the specifics of an individual site – it's actually an estimation of the actual work that needs to be carried out.

There are many different variances in terms of travel time, accessibility, all those things that are unique to your own specific sites. But we're providing you here with an estimation of effort. Then we have the frequency, and this is how often you carry out this task. So the one you can see on the screen is a 12-monthly task.

We have to carry this out on an annual basis. Now this could be weekly, daily, monthly – however often that particular task is required. We also have a competency element. So this is really identifying who needs to do this work, and here we have an E – an E for electrical. So this is an electrician required to undertake this particular task we're looking at.

Each of the tasks also has a set of actions below it. So we have an SFG20 schedule. Each of the schedules has tasks, and each of those tasks has a set of actions. And really this is the instructions or checklist that you'd be providing to your engineer who carries out that work. So this is the detail of actually what we're going to do.

And you can see here that the particular effort that's gone in the last few years in turning SFG20 from a book into digital content is that information's now broken down in a lot more granular form so that it's easily consumed by your downstream operational systems, such as CAFM or CMMS. Those systems can now easily ingest this content, so that it's easily then transferable to your engineers, perhaps through their mobile devices.

We also on the right have compliance, and this is where we're identifying exactly why SFG20 says you need to do this particular piece of work. We're identifying those references so that we know which British standard this is part of, which legislation this refers to – maybe another code of practice where we've got some specific industry information around that particular type of asset that defines why we've said this is something that should be done.

One of the key stats that came out of the SFG20 State of FM survey for 2025 was what you're seeing on screen now: 9% of organisations have an accurate, up-to-date asset register. I think that's very true. If we look at how industry's evolved over the years, how those asset registers have been built, how the completeness or correctness or consistency of those registers has maybe drifted over time.

The challenge is if we as building owners or occupiers, if we're looking to have our buildings maintained, to engage in bidding processes, asking – putting out tenders, if we're asking people to come and do work – if we want to be sure that the buildings we're looking after are correctly maintained, we need to start with our assets.

And as SFG20, we realise this is a challenge for industry. So we've developed SFG20 Mobiliser as a means of helping the industry better understand your assets. Perhaps asking questions you didn't know to ask and helping you correctly identify the maintenance for those assets. Once we understand what's actually in our buildings, so SFG20 Mobiliser has been built on the premise of let's look at how do we take our information that we have available and make best use of it.

So SFG20 Mobiliser was originally conceived by the principle that we have information about assets, but we have it in many different forms. The amount of asset registers, the different types of asset we have in our facility, the complication of all of that information and bringing it together is a real challenge.

Sometimes we'll have it on different systems. Sometimes it'll be held in different formats. It might be – some might be in our CAFM system, some might be in Excel spreadsheets, some might be in physical documentation. So then we look at the actual type of information. This is where we're getting quite granular in terms of there's so much variance in what an asset register is, and I think we may – even the same organisation might have five, six different spreadsheets completely formatted in different ways, all used for different purposes. We need to bring that information together and help, and then identify the correct maintenance to apply to those asset registers, and that's when it becomes a challenge.

We also have the situation where if our asset registers are incomplete, inconsistent, how do we actually know the questions to ask about those assets or even to look for those assets? In a sense, we don't know what we don't know, so we need the system to help us identify those gaps, identify those pieces of information that are missing, and help us with the questions we need to ask to understand that information.

And that's where we've built SFG20 Mobiliser – something that will intrinsically help your organisation make sense of that asset data whilst allocating the correct maintenance against each asset. So let's have a look at SFG20 Mobiliser. Right. So now I've got Mike Talbert with me. Mike Talbert's the CTO of SFG20.

Mike, you're going to take us through some of the functionality of SFG20 Mobiliser.

Mike Talbot: Yes, I am. Let's do that. So really, SFG20 Mobiliser starts with a principle of creating an asset register and then importing some data into it. So I'm going to make a new asset register for Myco Limited here, whose data I've got.

They supplied me with an Excel file, so I'm going to add assets from that. Three ways of adding assets: either using an Excel file in any format where we'll do some mapping – more on that in a second – or a COBie file, which is an Excel file in a specific format used or exported from a BIM tool, or via the API, where your CAFM system or asset management system can just push those assets directly into SFG20 Mobiliser.

Paul Bullard: So just to clarify, mate, you said any format on the Excel file – that means I don't have to use a specific template?

Mike Talbot: No, you don't have to use a specific template. Part of the import process is mapping your file to our format, so you can use Excel files that contain formulae and lookups and all those kinds of things, and we will import that. So it can be anything from a simple list to something slightly more complicated.

So I've chosen the file here, and that file's got two sheets in it: AR3 and AR3 Mini. I'm just going to choose the Mini one for this demo. And what the tool then does is it shows me a preview of this sheet of that workbook and the data in it. And the columns I've got look okay. So I'm going to continue. Then I need to choose which of these rows contains the names of the columns – so the first one. So that's it. Your Excel file's got to have a row with column names in it, and then it's got to have the data. We continue.

So what this screen says now is this is the bit where we map what SFG20 can use to what's in that Excel spreadsheet. And it only requires two bits of information. It requires a way of identifying an asset, an ID for that asset. In this case, we've got this thing called Asset Code, which is its unique ID, so I'm just going to choose that, and that's that part.

And next, what it needs to know is what type of asset this is. And normally that's described in an asset register, right? So here we've got a thing called Asset Type. We can select one or more columns, which when put together represent the type of this asset. Then we've got all these other columns that we could map.

So some of the important ones – let's start with where these assets are in a building. And that's important because we use the information about assets being in the same place as each other to help understand what they are. So we've got a column called Facility. And in this dataset, it looks like Building is probably the best match for that.

We've then got a thing called Floor, and indeed this data has a Floor in it. And then we have Space, which is kind of room. And in this dataset that looks like Location – it's got store room, meeting room, office area, and external in it. So let's have Location for that one.

Now what we want to do is we want to do things where we might want to make selections about the kind of maintenance we did. So asset criticality might be important for that. So you can see down here we've got Criticality. By the way, I can sort these in order of name as well, or just type a search if I want to. I don't have to keep going in the order the spreadsheet was defined in, but that might be easier – might be the format you recognise. So Criticality for that.

I've got a Condition here. I can put that in there. And then finally, what I'm going to do is I'm going to take Manufacturer and Model Number.

Paul Bullard: So you've filled in a few fields here, Mike. How important is it to fill in as many as you can?

Mike Talbot: Well, as many as you can. But I mean, you know, don't go inventing data or trying to pull data from too many places. The more data we have, we use all of it to help make the best possible choice. I think that the ones I've filled in here – very important for working out what an asset is and which code, which SFG20 code it should use – are things like the Facility, Floor and Space, and the Manufacturer and Model. And then often when you're making decisions about the kind of maintenance you want to do, trying to reduce over-maintaining – Criticality and Condition can be very important for those.

So this is a good set, but you know, whatever you can – we only need these two in order to do the work.

Paul Bullard: So effectively this is going to make the best out of whatever information we have available, and then that takes us to the next stage where we start helping fill in those gaps.

Mike Talbot: Yes, absolutely. That's right. I mean, yeah, good example here. For instance, I haven't filled in the Description column. It does have an Asset Description. You know, we can use that. It may help – it will probably help. So, you know, you fill in what you can, but we will be able to work without anything. We only need these first two. Anything else is optional, but will improve the quality of the matching.

Paul Bullard: So you've just gone through and helped our system understand the customer spreadsheet and their columns. If I'm using the same set of data all the time, maybe I'm mobilising 10 buildings on a sequential basis, do I have to do that identification of what Facilities-iQ field is what column in the spreadsheet each time?

Mike Talbot: We can make a template for that. So if I make a template here and let's call it Myco Limited Template, I can then save this template now, and it will be able to call that back. It will give me a list of templates and match the file. And I can just choose that and not have to do all those extra steps. It makes it very much quicker.

I'll click on Import now, and that's imported the 279 rows from that spreadsheet into our system. And as you can see here, it is in the table view. We've got the asset's unique ID here, information on the type, and then there are other columns we mapped and obviously not the ones we didn't. We can go and click on an individual asset and, you know, see all of its data there.

So this is a poor condition asset in the car park and so on and so forth. What we really want to do, though, is associate the correct SFG20 code with these assets. So what I'll do is I'll click on the SFG20 ER tab here, and I'll go and make some settings. So, for instance, I could here choose to say I only want to use English legislation or Scottish legislation.

I could identify that this was a healthcare facility, and I'd probably want HTM-aligned schedules where I could, or if I was mothballing or reactivating a facility, I'd choose these. If I don't choose any, then it's just going to use general stuff. It won't do any mothballing or reactivation, but it will use things that apply to any law.

If I click on Apply Settings, its next job is to first of all go through all of those assets and identify the unique combinations of manufacturers and models, and to go and look up basically what those manufacturers make. So, you know, if it's Otis and they make lift equipment, if it's Siemens, they make everything, so you can't really tell. They'll look up individual models, and it'll use that to try and determine what the type of asset is. At each step of the way, it will then group them together by those locations, like the provided locations, and it will try and use that information to help define, you know, what is in this space.

So if it's a boiler room, you know, we're going to find these kinds of pumps and things to do with boilers. If it's a lift, we'll find all those kinds of things to do with lifts and lift motors, rope grippers – all of those kinds of things are likely to be in the lift control room.

Once it's done that, as it has now done, it's identified that for our 279 assets, it's identified 42 different types of asset, which are listed here. And you can see with the little spinner next to each one, what the system is now doing is going through each of those types of asset, taking the example assets of that type here. So this is a number of them – 10 building management system controllers, 8 CCTV cameras. It's taking all of that information, and it's using that to rank the 1,500 SFG20 schedules in order of which are the most likely ones to match this particular type of asset.

And then as it goes through that process and determines that, it will come up with that list in the order it thinks is best. It will try to break any ties or disambiguate the top matching schedules by working out what questions you'd need to ask, either of a person or of the data, to say, "Okay, well, I'm sure this is a tungsten filament light. I'm sure this is a dry powder fire extinguisher."

And then it tries to answer those questions if it can, or it leaves it up to us to change the answers to those questions or to ask someone else if we can't determine the best possible choices. So you can see as it's going through, it's slowly beginning to fill out the individual elements.

So we can see this access control reader – it's decided that's an access control schedule. We can see it's got an air compressor. It's mapped through. It's doing an air conditioning unit. You can see that it's not really been able to work out what this building management system controller is. It's still spinning, but it's still not mapped. It's not convinced what this CCTV camera is. And we'll go and have a look at those to see how these individual questions then help us.

So CCTV cameras then – it's decided that we want to know whether or not the camera uses analytics or those kinds of things. So I'm going to click on Don't Know for that. It's decided, are they installed around the external boundaries or site perimeter? We could say yes. And as we do these things, we can see it's selecting Perimeter Monitoring Systems.

We can start saying that they are part of the building security system. As you can see, as I make these different choices, it's changing its mind about which of these things it is. And for each question as I hover over it, you can see how we might be able to tell what the answer to this question was if we couldn't otherwise tell. So at any point we can select the ones that we want here, and it's just ranking them and giving us the order it thinks based on the answers to these questions.

So we could go and say that is a building security system, and then we might want to go and say this one – it's already chosen as a CCTV camera, so we could go and choose this one using similar kinds of questions to identify each of these types.

Paul Bullard: Sorry, Mike. What we're really saying is when it's working out the most appropriate SFG20 schedule for this particular asset, if there just isn't enough information, it will help us by providing us with questions that we need to ask that maybe we didn't know to ask. And it's uncovering – that means it's really providing me that data, and then I can send these questions to whoever's responsible for that particular area. They can come back, and it will automatically identify the correct schedule based on my answers.

Mike Talbot: That's correct. It will, and it's already done this massive job of giving you the schedules anyway. Out of the 1,500, it's done a really good job of giving you the top-ranking ones anyway, so that you have those choices to make, which are very informed choices.

And for instance, you know, you can go into these things and you can hover over a particular thing like this and say, "Okay, we can see that this is closed-circuit television. We can see where it connects to," and you can use that in order to make our decisions. So it's really straightforward to be able to pull those kinds of things together and pull that out and get the results you want, because we can very quickly see what the schedule's about. We can quickly ask these questions. Once we've got the answers, we can determine the right one. And it's a really pretty straightforward process.

So up to 74% of them are mapped now. It's still going in the background. If I just bring this up, these are all the ones that are not mapped at the minute. So we've got these air conditioning units. It's not sure if it's the split system with gas, electric or hot water heaters, or split system heat pumps air-cooled. It's really not sure between those two.

And we can tell that it's got an outdoor sensor. So is it a self-contained room air conditioner? Yes. So it's decided now it's a DX split system, and we can see it's also told us that these ones may have certain particular things fitted, and we could just check if they are fitted or not, if we want to do that. And that will then make sure that we're not specifying over-maintenance on these DX split systems if we didn't need to.

So once we've done this, and we've got the ones mapped that we want, let's just sort those by count. So fire extinguishers – another classic. What are we doing with fire extinguishers? Is it dry powder? Yes. Okay, so we now know it's dry powder. Do we want to do – is it gas cartridge or stored pressure? None of the data told us that. So I'm going to say we want to do the extended service procedures for dry powder extinguishers.

But you can see that was a very quick thing to do, and I could very quickly determine these kinds of things. So what I'm going to do now is a classic – another one, gasified boiler. What type of boiler is it? Is it a domestic and small commercial boiler? And so on and so forth. We can just go and select one and off we go.

So with 86% of them mapped, I'm just going to show you how we now get that data back out of the system.

So firstly, what I can do is I can click on this Export Register Data over here, and if I go and open up that spreadsheet and I bring it over onto this screen, we can now see the data that – let me get a bit bigger so we can see it. You can see I've exported the data that came in. This was the SFG20 code we imported. We didn't import any, so that was blank. And then this is the code that it's mapped it to.

So we've decided that these roller shutter door power operated – 72-04 version 5 – and this is the SFG20 internal unique identifier for that, so that you can check that off. And then we've also got some 84-36s and so on and so forth. So this data has now been mapped against the register and made available back in an Excel file, very easy to import into something else.

Paul Bullard: So effectively, Mike, we've taken a spreadsheet in, and we've done all the automated mapping, and now we're able to output the same content of the spreadsheet, but this time with the correct SFG20 code allocated against it.

Mike Talbot: Absolutely. And if you already had SFG20 codes in there, you know, they may have changed for a lot of reasons. We split a bunch of schedules to try and make them more accurate again, trying to reduce over-maintenance, and, you know, that might be the case, or we might have written a new schedule that's more appropriate now.

Paul Bullard: So I can use this as a validation for my existing systems to say, "Okay, if I've already got maintenance set up, but how correct is that?" So I could take the data out of that system, run it through here, say, "This is the asset, this is the code I was using," and then it will tell us, "This is the correct code you should be using."

Mike Talbot: Absolutely. And in this view here, you'd see where it was already mapped. You'd be seeing a notification that this was what it was previously mapped to, and then you'd see if that was the same value as it now thought it was. And you could make your own determinations based on that. So yeah, absolutely we can do that.

So that's one way of getting data out – very useful way. But what I really want to do is I want to show you how we can make a maintenance regime. So I am going to go and create a maintenance regime for Myco here.

And what I'm going to do is I'm going to go and get that asset register that we just had there, and I'm going to click on it and choose it to be part of our maintenance regime and synchronise it.

And so what we now have is we have that building mapped into an SFG20 Facilities-iQ maintenance regime, which immediately gives us some very useful bits of data. So we can see up here, we can already see how many working days we're spending on critical tasks, red tasks, how many days we're spending on amber tasks, how many – in this case hours – are we spending on green tasks for this whole place.

And we can continue that down. So if you are interested in just the main building, we can click on that. And you can see, we can see 31 working days on red tasks, 54 working days on amber tasks. You can see with these little pie charts where all that effort's going. So a lot of work in the basement, because in the basement, I think we've got some cooling towers and things like that that are accessed off the basement.

You can very quickly get that view. You can also see what visits you need to perform in this area. So you can see we've got daily tasks, weekly tasks, monthly tasks. You can see the annual effort of those tasks, up to five-yearly tasks in here. And then you can look at the individual skills you need to deploy to perform these tasks.

So we can see a significant number of competent person and M&E, you know, a small amount of electrical – 18 hours a year – 18 hours a year for the building trade. So it's a really good way of quickly getting an Excel spreadsheet and turning it into an understanding of effort that's looking at this from the perspective of what skills, what tasks need to be done across the piece.

And obviously we can go into here, we can go into the first floor, we can go into this server room, and we can go and look at this power generation standby generator.

And what we can see is for this generator, we've got – we've got the actual asset. So we can go and view that asset, where it is. We can now see its location and the maintenance regime it's in. We can see what it is, and then we can see all of the different tasks associated with it that are going to be required for it and pull those through.

So that's one very useful way of looking at this. You've basically got the book for the building with the assets associated with each space, and in each space, which schedules are appropriate for that. We can also view this in terms of the assets, so that's just for this location. Let's go back to the main building and view the assets there.

So these are now all of the assets in that main building, and we can see the details of those assets here and use this system to filter them. So we can see we've got – there's 86 working days for the main building. Let's go and have a look at how much time we're spending on low-criticality assets. I'll just set this filter to Low.

We can see we're still spending 44 working days on low-criticality assets. So maybe what we want to do is find where we have got things where we could not do the amber tasks. So what I'm going to do is I'm going to select everything with a red task and with an amber task. And what I'm going to do is select all of these things in here and then tailor it so we don't do the amber tasks.

I can't not do the red tasks here, but I can say I don't want to do the amber tasks for these things, and then apply to all of that. And that's then going to take off all of those amber tasks for those particular assets. And it's reduced us down now to only 45 working days rather than the 86 we had before.

So that's a really powerful way of making sure that you're using asset data to drive the maintenance in the building and make sure that you are not over-maintaining things which are not important to the operation of the business.

Paul Bullard: So this really ties in with the whole principle of optimised maintenance. So where we're looking at our building and we're saying, "Actually, what are the assets that are critical to the function of this building?" So of course we need to do our statutory maintenance, but if we look at optimising the building, we're going to look at those key assets that are really important to us and maybe say some of the other assets we don't need to put as much emphasis on.

So that way, by taking out – if we remove the ambers and the greens for those assets that aren't as critical, we're actually removing cost from our maintenance operations, and that leaves us to actually have time to spend on those things that are really key for our facilities.

Mike Talbot: Definitely. Yeah, that's the power of this platform. The ability to go from a raw spreadsheet, ensure you've got the right maintenance specified, then make choices about the kind of maintenance that's appropriate, and to get that information output driven directly into a CAFM, either using our API or by exporting the data. It's very powerful.

Paul Bullard: Well, I hope you enjoyed that as much as I did. So now we're actually going to ask a quick question. If you'd like to find out anything more about what you've just seen, then we're going to put a quick poll up now, and if you could just respond to that please, and then we'll have a look at some questions from the audience.

Okay, and welcome back, Mike. We've – I've been going through all the questions from the audience. We've got quite a lot in. We've got some trends, though. First question I've got for you is from the asset registers we were looking at: is there a maximum number of assets or a size of spreadsheet that we should be looking at?

Mike Talbot: No, not really. I mean, we can support many millions of assets for sure. I mean, obviously there's a limit somewhere, but I mean, it's a very, very large limit. And those spreadsheets, they could contain, you know, one row for every asset, or you might have one of those cases where, you know, you've got a row in your asset register that says they've got 20 of these and 5 of those.

We handle both of those just fine. And you can handle millions of rows of those, even if they had quantities on them. So, yeah, not a big restriction.

Paul Bullard: Okay. I've just got one here which I'll answer, if that's okay. So someone's written and asked us if they don't have an asset register and they are starting from scratch, can we help them?

And the answer is yes, we can. If you contact us after the webinar, our professional services team – we're helping people, we're aligning a template asset register to FMS 002, so the government standard for creating your asset register, and we're using that as a template. But as we said before and really emphasise this: you do not need a template to carry out this piece of work.

This has been designed so that you can have asset registers in any format in Excel, and we'll bring them into Facilities-iQ and correctly identify that SFG20 schedule. So if I go back to you, Mike – sorry, the next question I've got is we saw the majority of assets being mapped in your demo. Some of them weren't. How does the system help you get to that end goal?

Mike Talbot: Well, so yes. I mean, what it does is it ranks all of our schedules in order, and then if it can pick one because it's suitably different and it's obviously the right choice, it will. But if it can't, what it does is it creates those questions and gives you all the information you need to be able to answer those questions to get a much clearer view.

But yeah, it's going to massively reduce the time because it's focusing it down on a minimum set that are the ones which are applicable.

Paul Bullard: Okay. Thank you. Next we've got – can I add multiple schedules to a single asset?

Mike Talbot: Oh yeah, for sure. I mean, that makes a lot of sense with some things. I mean, quite a few types of asset – emergency lighting, that often needs – you just select more than one schedule. So yeah, you are very welcome. You'll be presented with all the things which are applicable for emergency lighting, and you just choose the ones that you wanted to apply. That would be straightforward.

Paul Bullard: Okay. If we – we've got a question here, and it's about, say, a Facilities-iQ user. They've built their own library from deriving some schedules. So they've taken a standard SFG20 schedule and they've customised them for their specific organisation, probably doing what you were talking about earlier, where we're looking at the optimised maintenance, looking at the reds and ambers and taking away the maintenance that wasn't necessarily appropriate for that site.

But what they've asked is does SFG20 Mobiliser just use the standard SFG20 schedule set, or can it look at their version, their customised SFG20 schedules?

Mike Talbot: No, it'll absolutely use their custom schedules as well. So custom schedules or schedules derived from SFG20 schedules are all considered by SFG20 Mobiliser as part of that process. So when I say it looks at 1,500 schedules, that's the SFG20 library, but it also looks at any custom ones you've built yourself or derived ones.

Paul Bullard: So, Mike, our final question we've got is we've had a customer ask – they saw you create a maintenance regime within Facilities-iQ from that asset data. It was presenting all of that timing. So we saw how much effort was required for all your red tasks, your amber tasks, or the individual skills. What would they actually use that for? What could they use that for?

Mike Talbot: Well, I think, uh, building owner-occupier, they'd be able to use that when they were going out looking for tenders for their maintenance to understand what they would expect people to be quoting on, to make sure they're able to compare multiple tenders against each other, to see if there seem to be some areas where things are missing, to get that kind of feeling of the scale of the job, which is not going to be very difficult. So it basically empowers them to have more knowledge about what they should expect from their service providers.

Paul Bullard: I suppose they could also use it for budgeting purposes. If they need to understand the effort required to maintain their facility – for one of these, it would be from an asset register. They now have that information. They now know exactly what work needs to be done, exactly how long that work should take. That could help them in actually their internal planning as well.

Mike Talbot: Yeah, it definitely could. And certainly when it comes down to user and operator tasks, things which you probably wouldn't be going to a service provider for, understanding what the real impact on your business that those kinds of tasks are – very, very helpful.

Paul Bullard: And that's another way of pulling that cost out of the maintenance budget, because you're not asking – you are not paying someone to do it. You are using people already on the ground.

Mike Talbot: Absolutely.

Paul Bullard: Well, thank you, Mike, and we're now coming to the end of our webinar timeslot. So if you've asked a question and we haven't been able to answer it, don't worry. We will be responding to you, so you'll have an answer shortly.

The webinar recording is going to be made available to yourselves. There is an e-guide around this subject that we'd love you all to download. There will be a QR code coming up in a second on the screen, but otherwise you will be emailed it.

I'd like to thank you all for watching today. It's really exciting for us to let you all know about this functionality that we are releasing to market, and we hope you enjoyed it as much as we did. Thank you very much.