An introduction to Confirm™ Arboriculture

Give you a little bit about myself. My name is Roger Leverett, and I joined Brightly back in August twenty twenty one. Don't panic because prior to that, I spent twenty one years working in local government, managing trees, developing our dieback plans and tree strategies, developing parks and open spaces, playgrounds, street cleansing, and anything else that's sort of green or litter based. Most recently, I was working for the unitary authorities of Telford in Shropshire and the city of Stoke on Trent in Staffordshire. And I'm currently a qualified highways inspector. Okay. So what we've done with Confirm Agriculture is redesign it. And if you've used Confirm Arboriculture before, you're definitely gonna see something new today. So I'm gonna be showing you what we're gonna class as the new standard arbor cultural configuration. But please bear in mind that confirm is highly configurable, and you'll be able to choose the elements that you need and switch things in and out as your business needs later on. Just to let you know that, within this proposed build, any data that you already have, can be reconfigured to allow the new standard build functions to work. So there's no need to worry about having to work from scratch and collecting all the data from scratch again. Just to make you aware, I'm going to be showing dashboards and screenshots from confirm web. For those of you who haven't seen confirm web, it's the new non Citrix based web version of confirm. For most users at the moment, it's got all the functionality that you're gonna need. So it's got jobs, inquiries, and defects in there. And with each new release, the new functionality is added. For those that attended the Illuminate conference, this won't be new news, but, back at the conference in April, Brightly announced that within two years, so two years from April, this year that the vast majority of the functionality that's currently in Confirm Host is gonna be transferred into Confirm Web. So Confirm Web will become the access portal for the vast majority of users very, very quickly. But, hopefully, you're gonna see that Confirmware is a lot more user act user interactive and a lot friendlier and faster. That's great. So so as users of Confirm, hopefully, we're all familiar with the process of managing inquiries, raising defects, jobs, and the process of inspections within Confirm. We will be touching upon parts of those, but, predominantly, we're going to be focusing on in this webinar how we can manage risk within Confirm, how we can quantify the value. So here we're looking at methodologies such as and quantifying the carbon and the price of that carbon stored within the tree stand, and how we can use confirm and our other platforms to engage communities. So when we talk about engaging communities, we're talking about how we can get data out to the community on our operations, how the community can become involved in potentially obtaining those assets instead of doing the original asset collection for you, and monitoring sort of pests and diseases as well as fulfilling our new duty to consult that's been brought in through the Environment Act. So key benefits of using Confirm. For risk management, it provides all your data in one place, providing a fully auditable record of tree maintenance and management, which will help to fulfill any tree risk management plan that you need to populate or maintain, and this also helps should the worst happen with an insurance claim. We can plot risk zones and inspection planning through confirm. And through the repeating jobs agent, we can have the system automatically generate on a frequency as you require, tree maintenance jobs. So for example, that could be pollarding, that could be annual or biannual, or it could be something like epicormic growth or tree watering. And that's different than the cyclic management within confirm, which you may have heard of, which requires, an officer to go in and physically release those jobs to the contractor, whereas repeating jobs doesn't. You'll be able to see that we can use confirm to monitor pests and disease, and we can if required, confirm can be set up to alert you when a relevant pest has been selected by an inspector if that needs to be identified and reported through to DEFRA. From October this year, we're gonna be using a QTRA tree risk assessment API. So if you prefer to use Quattro for your tree risk assessments, that's gonna be possible within Confirm as well. But we will be showing a similar way within Confirm as well this afternoon. So in order to quantify the value of trees, we're going to be looking at the quick cover methodology. We're going to be using the DBH predominantly for caveats and for the calculation for the stored carbon and data from the UK carbon trading scheme to put a monetary value on that stored carbon. And to confirm, we'll undertake this calculation subject to the DBH and the CAVAC categories being fulfilled for all individual trees automatically within confirm. Okay so as we know the Environment Act has brought in a duty to consult for street tree felling whilst the UK government hasn't yet set out the exact parameters of what that consultation requirements will be, we have already set up a potential option for you that can be adopted straight away, and that's linked direct to specific trees. And as the regulations become known, we will, update the system to comply with that. We have a new project called Community Central, which we'll touch on later on, which provides a portal for the community to become involved. And we can use confirm to reply to FOI requests. As we know, we all get multiple FOI requests generally with the same questions. So using the report functionality within confirm, that can be either automatically emailed out or held within the dashboard for the public to view as required. Within confirm where a suitable API exists, we can transfer the TPO records from a regulatory planning software into confirm so that all the records and applications and certificates for those TPOs can be viewable within confirm and also with the tree inspectors and contractors out in the field. And through the data that's within Confirm, you'll be able to engage with the community on the environmental benefits of the tree management. That could be through the incorporation of additional maps such as flood risk maps, but you'll be also able to push out data returning, pruning information, planting information, any trees that have been felled, and the locations and reasons for those. Okay. Well, just quick summary of how Confirm helps to, manage the asset life cycle. So we've we've got the community on the left, and then we've got the asset life cycle on the right. Both interact with each other. So we're going to be looking at the full asset register and QTRA, move that into a risk zone and inspection planning, how we look at monitoring pests and diseases, how Confirm helps with the maintenance and management, which links nicely into the repeating jobs. And where needed, we can externalize and use APIs such as the QTRA and the I Tree interface for further data analysis. Using confirm, we can schedule work. We can have a cost capture. And then, as we've said, we can use the caveat and some data within Carbon. So So caveat and Carbon doesn't really use any new data that you won't be already collecting, and then we can use that with the duty to consult and bounce all that information back out through to the community. K. So we'll start with risk management. And for QTRA, this is an example of some of the data, that can be obtained. So if we look at the dashboard on the top left, we've utilized the standard I Tree classifications. We've got the life stage of the tree. We've got some target occupancy data, and then we've got a widget just to show where the highest target occupancy trees are. So if we delve into that a little bit, so if you'll we've got the land classification. As I say, these are eye tree categories. So we've got commercial and industrial. In this example, forest and woodland, not recorded, part residential and transportation. They're probably gonna be the main ones as local authorities and land managers you may, come across, but all the categories are within the system. If we look at the tree life stage, this aligns with the individual tree data standard and the I Tree recording. So So as you can see, we've got the categories of ancient and veteran, early mature, late mature and mature, and not recorded. And we've got the information on the target occupancy. So this is a simplified version of QTRA just to say what is the target occupancy around that particular tree. There's no complicated calculation around that. But if you did need the more, scientific version and the more detailed information, then we've got the API link with QTRA. Just to show how that information looks on a map in terms of helping to risk plan, we can see that, the circles indicate the target occupancy. And if you zoomed in more where we have a number ten, for example, that would split out to show the individual trees. One of the other things as authorities we know we've got to look at quite closely is ash dieback. Some authorities, have ash dieback plans already. So what we're doing showing in this particular widget is through a dedicated ash dieback question, which could have been picked up through an ash dieback inspection or ad hoc inspections. We've got the standard ash dieback categories, and we're showing the mapping of those on the right. So we've got the twenty five percent or less, the twenty five to fifty percent, the fifty to seventy five, and the seventy five percent plus along with the no sign. On the widget that doesn't show very much information at the moment, which is what it's designed to do, is when the next inspections appear for the trees above, this will start to populate to show whether the tree has got worse, better, or stayed the same in terms of ash dieback. So we're able to start to plot and see visually those trees which are recovering, certainly, those trees that do require, some works. We've taken the time to, populate the most likely pests and diseases for trees, in the UK, and this does include a number of those pests and diseases of char knocking on the door, shall we say, but not quite here yet. And, again, with these being a standard form and a standard pick down list rather than the text box, then we can report on these and start to show exactly what conditions we've got and what fungus and diseases are affecting our tree stock as we go forward and keep that data live. And for each of those, we can map the exact locations of those as well, which will help to show us fidgetally where those hot spots, are for particular pest diseases and fungus. That's quite key because we know for some, pests in particular, it requires wholesale felling within a set given area. And for others, it's much more limited to what we have to do. And through those dashboards, we can click into any of the the bars to to identify the individual tree or trees that are being affected by those pests and diseases. Quite nicely with risk but also into maintenance management is the inspections, which we can manage through confirm. Now inspections can either be, routine inspections which are done upon a schedule. Those schedules are normally undertaken upon the risk zones, which we quantified either via using the target occupancy, the QTRA, or how we've defined the features to start with. So so here we've got a number of inspections. This are showing overdue being in red. So we have an annual inspection. The ad hoc, we've got some ash dieback monitoring inspections, which are overdue. If it's green, that's showing that the inspections are currently on target and in time. And then we split those up by officer so we can see the worst performing officer. Unfortunately, that appears to be me in this particular dashboard. And we've got a list below in dashboard to show those inspections which are upcoming but not yet due. So that just helps in terms of planning for the inspectors. In terms of maintenance management, it's probably something you're all quite familiar with already. But just to show, we've got a dashboard specifically for maintenance management and jobs. So we have a widget in the top left to show the outstanding jobs, and the next widget is the outstanding jobs by type. And those all those can be mapped as you can see on the right. What's new to the build? Wasn't it dropped out. Apologies, wasn't it? Just to check, can everybody still see that screen? Because it's not showing as shared online. Yes. See main maintenance management? Yep. That's fine. That's brilliant. Then what's happening with my screen then? So we've got options then for if there's any particular follow on works. So that could be, for example, any stump treatment that's required, such as herbicide or stump grinding, whether there's any grass restoration required after works, whether there's any timber extraction required. That just helps and enables the management of the jobs throughout the process and stops jobs that are, for example, paused or closed, but still needs dump grinding works from disappearing out of the system. And then on the bottom line, we've just got some defect widgets to show defects by type and the number. In this example, we've got a defect for touching property. We've got a number of defects in the middle widgets at the bottom showing those defects which have been raised but are uncommitted, so there's no job committed against those. And then we're showing the defects that have been raised by the officer, which are also uncommitted so that we can easily pick out as a individual officer which particular defects we need to work on and commit. If we switch over to Confirm Connect, we know we can use Confirm Connect to log and respond to inquiries. We know we can carry out inspections within Confirm Connect. We know we can create and edit features within ConfirmConnect. We can raise defects, undertake jobs, and we can also carry out risk assessments for on-site works. So here we see the standard screen. So we're just clicking into a job where we've got all the normal job information with the map, and we're scrolling down to where we're looking at the job attributes. You can see here that there are a number of job attributes that have the red icon attached, which means they're mandatory, so we need to select. And depending upon the option that we select, depends upon whether there's any further questions to answer as part of the risk assessment. We could still see here is the large risk assessment now as we start getting into the business of the day. And, again, depending upon the answer that's given will depend upon whether there is any additional questions asked further on. So if we look towards the traffic management and if there was a mute required, we can see that it's populated some new questions to answer because we've selected yes for those options. Once we've, completed those mandatory attributes, we're gonna be able to take the mandatory photograph, and then we can start the job. Once we've completed the job, we can see we've got a final photograph and mandatory attributes to take. So this is where the contractor recorded what work is required. So it's adding a second photograph to complete those works and then just completing the job. And we can see in the top right, the transfers is sending that back through to the main system. Now you'll notice in that example that we did complete the job on that particular process. There is the option to not complete the job and use statuses to progress those jobs to show which jobs require stump grinding or grass frustration, for example. Difficulty there is if there's multiple options that need to be undertaken after those works, then statuses, unfortunately, will only normally allow one description, and one action attached to those. So it is possible to close the jobs but still keep visibility of those additional works that are required. So we talk about risk management then. We've got all the data in one place for that auditable system. So how did that link back before? So we've we've captured the assets, whether that be within Connect or imported those or or the external surveys. We've managed to undertake some form of risk assessment and put those into a risk zone through the planning. So those risk zones could be based just upon the occupancy and or the road speed and condition of the tree. We're able to plot and dissect and investigate how our tree stock is responding to pests, diseases, and fungus, and that will then help to adjust those risk zones. We can follow any defects on into the maintenance management regime, whether that be to raise ad hoc jobs or to raise repeating jobs if we've got pollards, as I say, that need to be done undertaken on a cycle, or if we've got work such as crown lifting or epicormet or any other sort of form of repeating job you wish. That work can be scheduled. That can either be scheduled through WorkZone or in the case of repeating jobs. That will only be pushed out at a specific time and date as it's has has been set up within the repeating jobs functionality. Should we need to, we can capture the cost of that particular job, and, obviously, we'll always capture the work completion. So the cost for a job could be the monetary value, but it could also be the type of equipment that's been used and the mileage traveled along with any travel time or nonproductive time. So we've got QTRA in our new build, risk zones, and inspection planning. We're monitoring pest and disease and repeating jobs. Quantifying the value. This is probably quite key to probably everybody on the call, really, in the section of how do we value trees and try and justify our ever declining maintenance budgets, but yet we try and request more from our members and our management team. How can we go about doing that? There's two ways to go about doing that. One is using cover. Now in the past, quite often, cover's calculated on an individual basis. What we're proposing here is that we can calculate calabat for individual trees very simply using the quick method during the initial asset survey or at any point. Moving forward, so we can see a map on the left hand side which has got the showing a heat map of where the highest value trees are in those concentrations with the red being the highest. And on the right, we can see a bar chart by species showing the accumulated value through cover of the species within the system. We can delve into that information, and we can look at how that's calculated. So we can go by the site and the asset. And if we look at the end, we've got some final tree values on the bottom too. And on the top one, we're not showing a tree value, and that's just showing that that's not showing a value because one of the survey observation values hasn't been been entered. As we know, DBH is a key measurement within KAVA. That measurement can either be an exact measurement if that's your survey process or that can be undertaken within a banding policy. And we just set the middle of the band as the average and that allows that functionality to run forward for every single tree that's created. One of the key things that everybody's talking about at the moment quite rightly, especially after the last few days, is, climate change and how we can not only try and roll back towards net zero, but also how do we start to calculate what does net zero look like and how much carbon have we actually got stored within our tree stock. Apologies. So this dashboard within confirm is showing the stored c o two in kilograms by species. This is showing the top twenty species. The report will show everything. On the right hand side, we can show where the highest, concentration of that carbon store is, and we have just a simple counter widget showing the total for all trees, and we have a c o two market value for those particular trees. And we've projected through using the standard growth rates, which were captured during the initial tree survey, how that growth in c o two store is is potentially going to loop moving forward. The beauty with the projection is that as a tree is marked dead, that projection will also change along with all the other figures within those widgets. So if you start to look at the widgets in turn, if you look at the species composition and as I say, we're using the botanical name in this example, but that could be the common name. And we've got, the figures for the kilograms for all species that have been assessed. If we look at the data behind there, we've got what you'd expect to see. We've got the site. We've got the asset details. We've got the feature type. We've got the geography. We know the DBH converted to a circumference and then equally to its dry weight and c o two store. And then from the c o two store, we're using the last auction value price of a ton of carbon on the UK trading scheme to calculate a monetary value of that stored carbon. Now we know that authorities don't have to buy c o two credits. This is just to provide another metric to start to value how important that tree stock is that you're managing, which also helps to justify any budget requests. Closer look at the heat map. Heat map's quite good in terms of its visual aspects as well as the data that goes behind there. And this is also quite useful in terms of any planning developments that may be coming forward because this also helps to provide you with another metric and value for any compensatory provision that that may be needed due to any particular loss or, as we'd rather prefer, help to justify any retention of those particular trees. And then zoom in on the other two widgets. We've got the total store, and we've got the total market value. So should we have had to buy all that carbon for the trees that we've got in the system, we've got a value of what that would have been. Apologies. But I also should have mentioned that linked within the carbon and the c o two and the net zero through a separate piece of work and functionality within confirm, we can also calculate the net emissions of tree maintenance undertaken. So that would includes the travel time, the equipment. So the whole cycle of the maintenance of the trees can be captured to calculate whether we're overall in net zero. We need to add in some contributions to, soak up that extra carbon or whether we've got some credits we can work with in the future. So within confirm, we can record and track tree data. We can also record capital asset value, and we can start to put some monetary value on the c o two storage. And most importantly, it gives us that ability to justify our budgets and any maintenance requests. We've also, we'll be linking within Itree. If you need all that additional information that Itree can provide, Itree have now got an API. However, it is a paid for API. I think Itree is charging two cents per tree at the moment. So engaging our community is one of the key things that we need to do particularly as local authorities. We know that everybody loves a tree but not those necessarily particularly love living right underneath it in some cases. So how can we help to cut down those inquiries at the first point of contact to allow us to carry on with our key job? So we can have inquiries mapped by consult by subject type. We can also map all the trees within the system, whether that be an individual tree or a group tree. So that helps the reporting functionality. And, potentially, if tree isn't owned by yourselves, then that would prevent the inquiry coming through to yourself. So if we looked at an inquiry's dashboard, for example, we can show the inquiries by type. We've mapped those. We can show them at the inquiry status, and we can show those inquiries by type and officer. And at the moment, these are all allocated to the arboricultural team. So if you do a bit of a dive into the this felling consultation response inquiry, within confirm, we can map a particular tree within a web form so that all consultation inquiries are linked to a particular tree. So that pulls all the data together. That allows us to stop double handling any potential data and record all those results within the confirmed system. So we've got the historical record of any consultations that have taken place within Confirm, which also will then help us to not undertake multiple consultations month after month. So we've got a couple of, questions we've proposed here as part of the consultation into whether a tree should be felled. We've got a simple question on, does the resident or responder agree with the filing proposal? We've got no in red and yes in green. You'll see here we've got two consultations running at the moment. One in Abbey Barnes Court and one in Croxton Road. So you can have multiple inquiries, consultations running together. We've got a question of whether if that person's against the removal, why are they against the removal? And we've got options such as, they prefer an alternative management option. They've not answered the question not known, or the tree poses no problem. Those questions and answers can be changed as required. We've got whether there should be a replacement tree at the particular location where the tree is felled and whether the person responding is directly felled by the particular tree. We look at the table behind it, for example. So here we're looking at the questions that have been answered before those that are against removal. So we know this coming as a filing consultation response, and we have the answers to those questions behind all in one form, which can be exported into Excel as well. And then through that table, we can look at the inquiry. This is, in the inquiries within confirm web. So we've got all the standard features we'd expect to see on the inquiry from the subject to the site, the location, and we can see the individual answers to that particular consultation for the tree. Through that, we can also, look at a dashboard to show where we have, undertaken tree felling and the job type or the reason for that felling. So we have in this example four trees that were actually felled through a deadwood tree job, and that would be within the information behind there because the condition had deteriorated to the point where it wasn't worth, undertaking that those particular operation of deadwooding. And we've mapped those tree felling locations. Again, this starts to link back into the FOI information that can be exported and the information for the public. Down at the bottom, we're just tracking the number of trees planted by financial year. And we have now have a widget for canopy cover in square meters. So this takes the either the measured figure or the estimated canopy, size from the asset data and converts that to a square meterage for, for example, the borough of Stoke on Trent. And then we have a calculation based upon the average tree size of a fully grown tree, the same extent of its canopy, to generate some information on the number of trees that need to be required to be planted in order to meet the district's canopy cover requirement. Worthwhile adding in here that if you have any lidar data, particularly with canopy coverage, that can be imported into confirm and that the data would then start to populate you with a district wide square meterage cover rather than just the amount of cover from the assets that were in within the system. Looking back to the environment, we've got the Community Central project, which we have. So this enables users to optimize the process for providing access to data in multiple fashions. It's a partnership between Brightly and JeDoo. It provides seamless integration between Confirm and the front facing CRM platform. It provides real time information to communities about works and consultations in their area, and it helps to reduce cost to the service and improve efficiency and reduce costs. K. So in terms of the engaging community, we've got community engagement always happening forward and backwards, whether that be through members, senior managers, portfolio holders, customers, residents, businesses. You name it. They're all part of the community engagement. We have the solution to fulfill the duty to consult and respond to those duty to consult requests and maintain that information again all in one place as that auditable record, and we can automatically pull the data through to answer those FOI requests that generally happen quite frequently. So the the duty to consult will be edited as and when the regulations are issued. FOI requests can be set up and altered at any particular point, and those FOI requests can either be directed straight to a website portal. So there's even no interaction with officers to issue that data. Or once the request comes in, that information can just be issued out at the push of a button. Where there's an API, we can manage that TPO process and allow those documents to be viewable in the field and by officers. And that information can be pushed out into the mapping layers for the public as well. And through Community Central, all of that can be linked together in one easy portal. So if we go back to the start, we want to engage our communities, but we also need to manage that that particular risk posed by those trees. And when we talk about management of risk, that's exactly what we're talking about. We can't unfortunately, manage the decisions that are made elsewhere by external bodies, but what we can do is pull the data from the asset register, any risk assessment or QTRA, to pull that information into a risk management plan and risk zones to plan our inspections. We can track and monitor the spread of any pests and diseases that are recorded through those standard pick lists, and we can create maintenance management operation and repeating jobs to ensure that that risk is managed correctly. We can capture additional information from from the works to help us reach net zero. So we can capture the stored carbon, any lost carbon for where trees are felled, and any carbon that's generated as part of the management. We can provide a capital asset value for trees for all single trees within the system or individual trees, and we can value the quantity in terms of its weight and its monetary value for stored carbon. We link all that together. That helps to us to generate additional rationale behind any contributions for loss of trees due to planning, but it also helps to quantify and justify any ongoing works that are required for trees, say, through ash dieback or for any future maintenance budgets requests. And then we have all that information potentially available to push out various dashboards and FOI requests, and we're also linking that duty to consult back into the asset directly. So we complete the circle all within one system. I'll quickly just touch on this, although we probably already know that the information we would be trying to get out to the public and the benefits of trees is around air quality and pollution. So we can do that by linking the data running through the API portal for I Tree. And any, air quality sensors can also have that data imported into the system and show on a map layer. So that will then start to show us whether we need to do any maintenance on trees, if there's any canyoning effect, or if there are potential opportunities to increase the tree and vegetation covering that area to try and capture some of this pollution. We can get some sound measurements on how we are performing towards carbon neutral for our climate change action plans. We can start to work towards improved biodiversity by knowing the species composition, whether that be through its species, its life cycle points, its age, the size of particular trees. We can start to look at how we can reduce the temperature in our towns and cities. So we can use either specified temperature sensors or where we've got other sensors such as smart gullies, which record temperatures. We can link that data into confirm, visually display that to show where we might have opportunities to reduce those urban heat island effects. We all know that trees help to reduce flooding, not only by intercepting and delaying the amount of rain that goes into those gutters, but also by reducing the amount of surface runoff by holding that soil water in the soil. Again, we can start to overlay any mapping data from flood maps with our tree data. Maps within confirm start to look at the best places for planting trees and the best species. And we can quantify how much the plan maintenance that we've got within the system is going to cost and how long that will take us to undertake and also value any maintenance that needs to be required through a specific pest such as ash dieback. And through all of that, it helps us with our mental health because we know through studies that at least five to ten minutes with just looking or interacting with a tree out in the field improves everybody's mental health and keeps our dogs cool. So that was brightly confirm arboriculture, making your assets work smarter for those sustainable communities. I appreciate it's probably going to be lots of questions and answers, at the end, which is fantastic. And if you need access or would like to subscribe to confirm learn, please email training at brightly software dot com. But that information will also be sent out to all participants as well. Thank you very much. Thank you for taking us through that, Roger. I've seen some questions coming in, on the chat. Some of the team have, have already been answering some of them. But, Rob Bell, if you are, there, did you wanna take us through any of the questions that haven't been answered, and we can pose them to Roger now? Yes. I've got those. So, I think this one wasn't answered. So from Kenneth is it Bradshaw from Howies England, I think it is, or National Highways, I should say. Is it possible for QTRA to calculate the target occupancy for the m one, etcetera? Does that make sense? Yes it does. There's there is set criteria within the QTRA formulation regarding the potential number of vehicles that will be going past a particular tree at a particular time and then that would then calculate the potential risk value of that tree. So as long as you've got some data on the, number of cars going across that underneath that tree's path within the day or a set period of time potentially in hours or half an hour, then, yes, it can calculate the risk based on that for the m one. Brilliant. Kenneth, does that answer your question? Might be on mute. There was another one there from I think, Nick answered it, but Katrina Burrows from Stockport. She was interested just to see, on the consultation. I know we store those those answers as attributes, but is it can you show that in a in a in a screenshot there, Roger? Yes. Definitely. And it yeah. And there's a similar one, which I'll I'll follow-up with with from Simon Eastwood. So this is the batch of the consultation filing, dashboard. And if we look at, clicking back in, So we do have, all of the attributes. So this is back to how those attributes would look on the inquiry. Sorry, Rob. The rest of the question? I think Kate was just interested in just seeing the where the all the information is stored. That's right. Yeah. I guess So we've Yeah. Yeah. So we've set these up as an inquiry attribute. They can be set up in other other fashions. For those that I think are using a CRM system that, doesn't have inquiry attribute functionality. It we can still undertake that together. What we would have is then on the web form or as the inquiry is populated, you'd have the drop down boxes for those specific answers so that we could have that text dropped into the description box, and then we can pull the data from the description. But without an inquiry attribute, that's the process to do it because we need the text to all be the same to pull that report through. Cool. And Simon Eastwood equally interested in just seeing, the, tree attributes that are held. So if we can maybe just see a a tree asset with those record held and also the conditions that are being recorded during an inspection. Yep. Great question. So I'll just create a new feature within connect. Lay area. We'll pretend that's where we're mapping. So if we scroll down, we fill in the site, start date, which can be in the past or the future. In terms of the attributes, now this is a list of what you may wish to record. Obviously, they are not fixed in stone, so you could substitute ones for your your own or take things out altogether. So for new trees, we put date planted in really to look at any sort of development sites coming forward or new planting that comes forward. Its original height, whether there's tree tag number, what sort of stakes it has. So we've got signal double or triple at the moment. We've got the common name, all prefixed as an attribute in this particular case. And the reason we've undertaken the attribute as a the species is because it allows us to put the I Tree code behind there, and then we run the reports through the feature type, which is more about the location because it's the location that carries the first bit of risk information for us, so whether it's on a thirty mile an hour road. But if you do prefer to have species as the feature type, then that can be switched as well. We have standard growth rates as the attribute, And we've got so in order for the functionality to work, we would need growth rate within there. And we have a potential canopy type. Again, this is more linked to the individual tree data standard. Stem type, single, double, triple, or other. Start to look at what's at the base of the tree, so whether it's compacted ground, it's concrete, grass, paving. Soil. So this information is quite useful in terms of, if there's any highway repairs that are needed potentially. We've got the size planted, so we're using the standard sort of nursery sizes. And then we do have some questions about whether they're actually adjacent to any street lights, traffic lights, or adjacent utilities. This just helps to start to bring forward any potential routine works that may be required such as pruning around street lights or traffic lights, but in particular around the adjacent utilities where we've got electricity, and gas and BT. Once one of those is selected, it will actually pop a warning up, for whenever a job or activity is raised just to make sure that you've got the correct permissions to work around that particular utility. So we've got the target occupancy, which is is the basic criteria from, QTRA for not running the API. So we've got the constant frequent and the infrequent, whether it's a TPO tree and its number. We've got the CTI value, so we would prefix that with the one for, the particular authority or area that the work is in, but we've got the full list within here. We have a carbon price per ton. So without this figure, it just won't give the value for the price of the carbon, but it will still give you the amount of stored carbon. So here we've got the information up until the ninth of February. The last thing is behind there. Land classification, let's use the eye tree. And then if there's any root barriers, It's got a watering tube. If it's a memorial tree, what sort of replacement period, no one manages tied into in terms of memorial trees. I know some authorities say, well, if it dies within the first three years, we'll replace it, but after that, they won't. So that's useful information to be captured. And we've added in a tree removed attribute, and we've added this in so that this attribute will update through two ways. One, if a you've allowed the contractor or your internal works to interact with feature attributes. If this feat was set to tree removed yes, then when that job is completed, it will add the dead flag to the particular tree that's been filed or removed. The other way, confirm works to automatically dead a tree is through the SOR. So if an SOR was was applied, to file a tree, once that work's completed and the payment process has gone through, then the attribute of tree removed would be updated to yes, which would then apply the dead function. So we can add a tree to an inspection re so we could add a tree direct to an ash dieback inspection. And then the conditions So we have two conditions for cover because we've recorded the DBH already. This is the oh, one. So the life expectancy. And then we've got additional information on the conditions. So we're looking really at the conditions. We're looking at anything that may change as a tree grows or changes from year to year. So so we've got the number of stems. We've got some criteria for first branch height if you're undertaking a British standard survey. So we've got the crown height, the overall condition. We've got the DBH as a condition so that that can be changed. As we said, this could be an individual number or a band. We've got the height. I think, obviously, that's gonna be estimated. And then using the tree data standard, we've got the tree life stage, whether the crown's symmetrical, the size of the crown's spread, so that starts to populate the canopy coverage information, whether there's any previous reductions, for example. It's dead wood amount. And you can see with the I button, we can put some further information about what large deadwood, could be. Epicorbic growth, unions, any surface roots, cavities, the ash dieback question, which would be set to, not applicable if we're using the species as the as an attribute, the pest and disease list, standard list of fungus. It's tree status, so whether it's fallen alive, fallen dead, removed, standing, etcetera, an overall condition. And then we can see there's another British standard category at the bottom and the British standard retention category. So this does appear to be quite a big list of attributes and conditions there. I'd just go back to say that you don't have to fill all of those in if you have them all on the first survey, and you certainly don't have to have all of them if you're not going to be using them in the future. It's very much a sort of pick and mix approach, but the only ones that are needed in terms of the carbon and the CAVAT, obviously, the the DBH, the CAVAT specific questions, and if you're after that pound value on carbon, the carbon trading price. Alright. Cool. Thanks, Roger. Another question here from Phil Clark is, can the system contain woodland management criteria for groups of trees, I e woodland plots? Yes. It can. You could put those into the system as a tree group, which would show on the map, and then those would effectively be the woodland plots. So within those woodland plots, you could then have as attributes a management criteria, that you're tied into with the management plan. And then within that management, that feature, you could also update the upload the documents of the, management plan itself or any spreadsheet relating to the, particular metrics that are required for that management plan. Cool. Next one is from Helen at Telford. With duty to consult, can confirm digitally recognize which addresses the tree filling is by and subsequently send the letters out on our behalf? Good question. In so I would a couple of things that would be needed there. One would be the, property address is being picked up from the front end web form, and then the other one would be a what what the radius of the properties are within that. And then we could write some SQL that would, pull those properties that need to be updated, through and that although necessarily send a letter out, but we could certainly have an email sent out to those people either directly through Confirm or through the CRM system itself. Or you may just simply wish to update everybody that comes through as a consultation response automatically at the end of, that consultation, what the outcome was. K. So it very much depends upon some of those criteria and the CRM platform that's being used. Okay. Great. Might be similar question or along the same veins, but one from Kat is, how are you automating FOI requests? Great question. So the FOI request can be automated through the setup of the initial report. If we just go back to the dashboard. Some inquiries, wasn't it? So, so with all the information that we're collating, whether it be through the inquiry or the job information, we can pull that through into very specific report for, freedom of information. I would imagine that's going to be number of trees planted and felled by year. Reason for that felling species felled and replanted, potentially size of that. So that can be automated, through the report that will be written in the background, and that can either be automated to be pushed out to a web facing dashboard or exported simply to answer that question via email. Does that answer the question on the FOI one? It's a bit difficult to and I know some people get slightly different, questions asked. But that's fine. Thanks. I think we get a we get a a a a lot of variety in what we get. So I think it's it's just not standard enough to be able to do that. But Right. The the other function that you would that you could do is, build the report yourself within confirm web potentially, if you've got the information set up. Don't know if you've seen confirm web's reporting. And then you would use the confirm web reporting functionality just to select the information that you, wanted. For example I think you're underestimating the wide variety of weird questions that people ask us. We've got we've got standard reports, obviously, but the issue is, you know, somebody will always come along and go, you know, I need x from y at at zed, and it's like Yeah. I work. Yeah. No. That's fine. The the functionality you're talking about is all stuff we're aware of. I I was just wondering if there was anything new, that we could, like, kinda standardize and automate things with, but I think it's just reliant on what they ask. Yeah. It's a bit difficult one, isn't it? Because like you say, they do ask things in different ways and almost not sometimes know what they want. But, yeah, I think I would probably say to that is if you can group your FOI sort of questions into the most asked, questions and fields, then we can sort of see how we can track that through to create a specific automated report for that. No. That's great. Thank you. K. I've just scrolled down a little bit further. I hope apologies if I've missed anyone, but I've got one here from, Mike by Cronin. We're looking at introducing tree pits as a separate asset type, ideally to share with Highway's colleagues. What particular pros and cons would you foresee in the management of this? Following that, I don't know if it's related. Are the Cabat calculations automated on the individual trees using attributes? I think there's two separate questions there. Yes. I'll start the the Cabat one. Yes. They are all done undertaken on the attributes, and that's the automation process. So if one of those attributes wasn't filled in, then it wouldn't calculate the cover up value. In terms of tree pits second question. So with tree pit feature, we have, form set up. So here, we're potentially looking at number automatically populated as one or could be two. It depends on how you record those systems in this, pits in the system. Tree pit type, so we populate that with root cell, root space, strata, and other, whether there's a barrier within that pit as well, whether it's part of a wider Sud scheme, the surface of that tree pit, and whether there's a water tube. In terms of difficulties, I can't really see off the top of my head why there would be any difficulty sharing that information with highways, without being set up as a individual, feature type in itself, because they won't be able to alter the asset data for the the trees themselves. In fact, there's probably a great deal of benefit for that because you'll be able to then start to upload from highways the any sort of documentation or specification from those tree pits and where they link into. Okay. What else we got here? I think Mike's Mike's happy with that. That's a good one. Another one from, from Donovan. Can the system be used to carry out initial asset survey? I think we've lost Roger. I think he's going to sort the dogs out. Have we lost him? That's it that we have. Let's, let's let's let me take that one offline and, and and and come back to come back to them. The the answer to that's gonna be yes, isn't it? Yes. Yes. So, Donovan, you could, set up confirm with all the standard configuration for your tree in terms of your feature yeah. Tree type, species types, and all the attributes. And then you could just use that with confirm connect to go out and use that to capture your tree stock. Roger, you're back, and you're on mute. Apologies. The, the dog pulled out the Internet cable. Brilliant. Alright. Last question I can see here is from Claire at Harangay. How would the attribute attribute data we enter within confirm link with I Tree data and Kavat to give values, carbon and pound value? Okay. So the let's just say so we got it's a caveat value. I'll go back into the tree. So the caveat value is gonna be based upon the, the attributes. So we're picking up the DBH, and then we're picking up the CTI value and the functional value and the life expectancy. So once those four have an answer in, then the system automatically creates the value for that. In terms of I Tree, the API will extract the relevant data out of the system. If you wish to we've shown the basic sort of general information such as the land classification, the DBH, canopy size, species, etcetera. So the API will extract that. It will then run the report to calculate it, and then the API then will push that data back into the system with specific field because it can calculate it for each individual tree, or you can just have the report on mass generated. So it's still quite early days with the API. It's sort of still in a what they're calling a soft release. So they may need to make some tweaks to the functionality of that, but that's how it should be working. Great. I think I've got got all the outstanding questions. Of course, if I've missed anyone. If I have missed anything and and you still want to raise your hand, please do shout out. Mhmm. Kat? Yes. Of course. It's me. Thank you. Just I mean, you're I'm I'm here on behalf of my tree guy who couldn't be here because there's only him at the moment. So apologies if this is a question that that I should know the answer to. But, when you're talking about the attributes of the trees, we've got so you're talking about the deviation, all these kind of values. We're storing those in a condition survey. When you say attribute, does it have to be stored as a fixed attribute on the feature, or does it matter where that data's coming from? Because we're storing it as obviously in the current condition survey because the values change on a periodic basis? Yeah. Ultimately, it doesn't matter whether it is an attribute or a condition survey. We in the in the demonstration that we've shown, we're actually proposing that that's best suited as a condition, like you say, because it does change. And that just allows us some separate separation between the asset attributes and the condition of the tree. So we may only wish to allow an external tree inspector, for example, to access the condition data and not the feature data. So we would propose it's best it's as a, condition, but it can can work as both. That's fine. It's just we've our tree guys are only they've only just gone live on confirm in the last few weeks, and that's what I told them. So I'm glad you said that because I made them put it all in condition survey because it can change and because we wanna keep that separation. Yeah. So, no. That's fine. It just means that they can they can still do all of this regardless of where the data is. Thank you. Okay. Any further questions from anybody? I'm not seeing any hands raising or anything come on the chat. So so Roger and Sarah, I think we'll hand over hand it back to you. Perfect. Any closing comments, Roger? Only that really that, I hope you've liked what you've seen and you liked the way that Confirm Web looks. I think if you want a bit more information on how to access confirm web, if you're already a user online for us, then drop us a line. And if there's any further questions you think of later on, just drop a line to us, and we'll we'll get back to you on that. Perfect. Thank you, everybody. I will be sending out a follow-up, email. And when the recording is available in Confirm Learn, we've spoken to a few on the of you on the chat. But as soon as it's available, we'll be letting you know. And that will be within the, the free area where the Optimize and Confirmed sessions are held within ConfirmLearn. And as I say, we'll send you out a link for that one. Any questions that you have post session, feel free to reach out to your account manager or to Roger or to anyone of the team. If you don't have a contact, email address for anybody, feel free to use the UK dash marketing email address, and we can, divert that to the right person. But thanks very much for your time, and I hope you found it all informative. Brilliant. Thank you, Roger. Much appreciated. Thank you. Thanks, guys. Thanks very well.