Enhance your fiber network operations and time to value with more accurate, predictive data.

Hello everyone and thank you for joining us for today's Fiber Broadband Association Association webinar. My name is David Norris. I'm the webinar producer here at FBA and we appreciate you taking time to join us today. Today's webinar is using accurate predictive data to reduce faults and increase wins and this is being brought to us today by IQGeo. Before we begin, I just have a couple of very quick housekeeping items. First, everybody is in listen only mode today, but we'd still like you to submit your questions, so please do so. You can use the questions tool which is located in the upper right corner to type your questions and we will be having a Q&A session near the end of today's presentation. Also, this webinar will be available on demand. It's usually there within 24 to 48 hours after the live broadcast and you can access that through the FBA website under the events tab. So check that out. And finally, we'll have a survey at the end of today's presentation. The survey is very brief, but your responses do help us understand what's most valuable to you. So please do take a moment to complete that survey. We appreciate your feedback. And with that, let's go ahead and we'll get started here. So today we are joined by Stefan Schneider, the Telecom Product Manager at IQGeo and also Jonas Verstuyft, the Product Manager of Sales Enablement at IQGeo. And they're going to be talking about discussing how having a deeper understanding of your infrastructure and predictive analysis can really help fiber operators reduce faults and increase their wins, do things like validate tests even as you're rolling out your network incrementally, and then use these same tools to keep the for maintenance with the network as well. And so with that, I will go ahead and I'm going to hand things over to Stefan to get us started. So Stefan, take it away. Thank you so much, David. All right. So we wanted to talk, you know, about how to use your asset data, you know, to improve your sales and operations, be more predictive, you know, being able to capture faults before, you know, before they happen and capture opportunities as they arise. So next slide. I'll do a quick intro about IQGeo. So we're a software company headquartered out in Cambridge in the UK. We have a lot of customers between telecoms and utility, about 100k plus global users, 280 staff and growing. We produce software that helps with asset management and geospatial mapping of those assets. And we've extended our software to actually cover for more, you know, operational and sales enablement use cases, as opposed to your traditional just asset on map view of the world. Next slide. So let's talk about predictive operations using our network manager telecom tool. So the old way has always been you have a physical asset inventory, right? You have assets on a map, you might know that you have accurate assets, you have pretty accurate location of those assets, you don't necessarily know on that information what is the asset state? Is it built? Is it ready? Is it damaged? Is it, you know, operational, which customer sits there. And you have very limited integration of those, you know, of that data with your other tools in your OSS and VSS stack. So essentially, what you end up having is that your operations and sales people cannot effectively use the tools to actually determine where either faults are existing, or, you know, potential sales opportunities might happen. Next slide. This basically creates lots of, you know, manual swivel chair workflows, where you have to go from one tool to the next. And out of that tool, get data, put tool back in and just figure out where things go. So that usually ends up with frustrated engineers. We don't know the source of that picture. But, you know, that tends to be how most people tend to react to the manual swivel chair workflows that most people have to deal with. Next slide. So we'll we'll do a quick poll. And, you know, want to ask the audience, what percentage of faults you think they can proactively discover in your network, if you have the right systems in place, the options are less than 5%, 5 to 25%, 25 to 50%, 50 to 25%, or over 75% will give you a few seconds to respond. And we're still getting a few responses in, but it looks like we have everybody. All right. Excellent. And it's interesting, because when we've spoken to folks that are less operationally driven, they tend to think that they can actually predict less faults, right in the lower range. But the reality is, if you have very accurate, you know, data, and you can actually map and understand the impact of your services on physical infrastructure, you can actually catch a lot of faults, either because you have more accurate, you know, pinpointing of where the root of the problem is, or because you're actually mixing and matching data to actually help you predict where those where those events might happen. So it does map what we're actually seeing from folks, you know, it's more than 50%. And the, you know, the idea is that by being much more accurate with that data that's underlying, you know, your network, you should be able to predict much more faults. So let's close the poll and continue with the presentation. So what we're looking for, it's basically a new way of doing things. So no more, you know, having a map and assets on the map that sit independently from the rest of your OSS and BSS stack. But instead going for a fully integrated physical asset operations management model, where you can have configurable models for all the technologies that you have in your network, you have ease integration through your OSS stack. So your fault management, performance management, event management, ticket management, etc, can actually interact with the assets on the map. You have workflows that can be extensible. So you're not necessarily close to specific workflows that are predefined in the product, you can actually mix and match and make sure that they adapt to the way that you operate, have rich metadata on the map. So not just the asset, but asset status and asset information that you can use to query and enrich information in other systems and very extensive API support. No asset management system should be an island and it should actually allow you to get that data in and out of systems so you can make your life easier. And you know, that can help you with things like OTDR network tracing. And we'll talk about that in a second or, you know, enhancing your break-fix tickets. So as an example, right, enriching this fault, you know, tickets with location, right, having the asset on the map, having a fault management system query the map to determine the location of the fault based on an OTDR trace or, you know, another trace or fault finding API can allow you to actually add that information to your ticket. So an item embed the URL of the application. So when you're sending a ticket to your field engineers or your field crew, you're not necessarily having to like PDF a map or give them some, you know, coordinates that may or may not be accurate or give them an address, which in some cases and in some locations might actually not be accurate at all. You give them access to the application, you know, the ability to open, you know, the fault on the map and see exactly, you know, what the equipment and, you know, what features sit on a specific location for a fault and send them to the right location, you know, helping them get to root cause faster or fix faster. Next slide. The other thing that you can do, it's obviously this is not going to be very useful if you're not thinking ahead. So while you're doing your provisioning and your resource reservation, you can start using metadata so you can, you know, easily identify assets with services that you're providing to the customer, different, you know, metadata attributes that you might use to identify, you know, specific crew information or specific, you know, information that sits in other systems. So you can actually reference this a lot easier between multiple systems. What makes it like really powerful is the idea that by adding metadata, you actually add breadcrumbs that you can use between your systems to actually reference those assets and make it super easy to find them in the language that your other system understands. So you're not having to do a lot of translations. If you have a multitude of, say, service IDs because your provisioning system uses one, your logical inventory system uses another, and then your physical inventory system uses another convention, you can actually add those three as, you know, service IDs and metadata and be able to actually reference that across multiple systems. So for example, you can create a circuit between, you know, two points to create a reserve path and then use those metadata attributes to, you know, give it operational status, right? You have your circuit, you can say, for example, attributes as whether or not, you know, there's any, you know, faults or defects on the fiber or, you know, on the ports, give it a service ID, a wavelength, give it multiple service IDs if that's the way that you work and be able to reference that via API or specifically on the map. Next slide. So that's all well and good. And that those are things that we're doing today with the application, right? But the idea is that the more that we move into this idea of having metadata, of more integration, you have deeper integration, your automation can be extended away from just simply provisioning or, you know, ticket generation into having more contextual interfaces and more context in the information that you're passing between the different applications. So having that richer information available, right, can lead into more efficient teams. As an example of where we want to go with this, next slide. Right. You can have a copilot that says, hey, I detected a network fault near a specific location. It looks like a cable's being cut and automatically create the work orders, you know, dispatch the crews, send out notifications to specific customers that, you know, match a specific outage subscription, suggest a repair strategy. Like, say, for example, in this case, a cable's been cut, suggest a splice or replacement cable and calculate based on the information that you have from your other tools, what a resolution time would look like. Next slide. So you start with, you know, test head detecting the faults, notifying IQGEO that fault is calculated so you can actually take the data inside IQGEO and enrich your ticket. Generate restoration options, you know, from other systems. While the crew is en route. So say, for example, I have capacity for splicing. I don't have capacity for splicing. You need to reroute and, you know, add that to the ticket. Have the crews on site select the restoration option that makes sense based on available capacity and, you know, equipment on the truck. Complete the work, update the data in real time. And then that's it. You're done. You have a much faster, you know, fault resolution. With network changes that can then propagate to other systems in real time. And that's where we're intending to go in the next couple of years with our products. So with that, I'll head over to Jonas. Right. Thanks, Stefan. Okay. What I want to talk about is how, yeah, that predictability and using those insights can help you with sales of, you know, new opportunities, new connections on your network, making smarter network extensions. So imagine a situation where you have your current assets already in a particular area. So you're already serving customers from these assets. See the green lines here on the map. And you have a new connection request coming in this location here. Yeah. Typically for this new connection request, you will need to build some new network. You will need to extend your existing assets and find a new bot to get that customer or prospect connected. Just looking at the map and looking at our workflow, you would go into your inventory system, check where you have possible locations to connect that customer up. These two might seem reasonable. But yeah, you need to deep dig a bit deeper to the network to know, do I have capacity running up to that location? Is that location actually suitable to get a connection? I'm going to get a fiber connected to. And then you have a lot more questions to for the new builds that needs to be done. So is this street actually accessible to have utility poles in this area? That I that I could be using or do I need to do an underground build? Is there anything that can influence the cost of this underground build? And the surface information I need to be aware of or subsurface information like rock areas that might hinder my my deployment? Maybe you cannot get the right of way for for some of these streets. So a lot of questions that come up and that you need to resolve before you can get the right of way for some of these streets. Or you can get back to the customer with an accurate quote. Or seeing with with that old way of working, there's a lot of negative outcomes that you can have for such a simple connection request. First one and the most common one that we see is when you get back to them, they moved on. They've gone with one of the competitors. Definitely. If you have a very manual workflow with a lot of steps and a lot of people in between, you need to have your sales sales engineer, fiber engineer, look at it. They all have a backlog of work. You need to get approval from finance. And by the time you get back after a couple of weeks, they actually moved on. They don't need a connection anymore. So that's the most common thing that we see. Second one is that if you have built something into your workflow to be able to go faster, but you want to mitigate that risk, you might create your estimates a lot more costly. You build in, make sure that you can mitigate that risk. So the estimate I come up with to make that connection is too high and scare them and scare them away. Third option is the other way around. So you're maybe actually cutting corners. You don't have you don't take the time to really look at the area. You don't engage with with a fiber engineer and you don't foresee all of the issues that only are coming up during construction. So you might come up with a very competitive quote. But when once you start building the network, there's all these things that that cost a lot more services or obstacles that you haven't foreseen. So you end up losing money on the opportunity. And the fourth one is you might not even get get a get approval from finance. So you're only looking at that single connection request. You calculate the cost very accurately, accurately to make that connection. And the business case is just not there because you have that single location. It's just too far. And you're not looking into other potential other prospects. In the area that you might be able to connect. And that's something I want to talk about and also ask the audience in the second poll question. How certain are you that you know all potential customers in a service area? So if you're looking at an area that you servicing, can you can you tell how certain are you so very certain, somewhat certain, not very certain or not certain at all that you know, all the potential locations that you might be able to connect? See folks coming in. All right, it looks like our results are in. Give me just another minute here. Okay. Okay, see that around half is is not very certain that they know all potential customers in a service area. So I need Yeah, that's, that's a lot of potential for Yeah, making future connections or these potential customers are very interesting to take into account when you're creating a business a case for a single connection. And that's something that we want to discuss and show how we can help with discovering those opportunities and taking those into account to become more predictive and increase the return on investment for your connections. So what's the new way? So what we want to do with with IQG Solution Network Revenue Optimizer is help with assessing the cost for making these connections. So determine what is now the actual cost most cost effective route to make the connection. And remember, the example from earlier, I identified this location here, maybe this location. But looking at your existing assets, and knowing how can you how you can make a connection to your network. So considering for example, only splice closures or cable slack locations, and locations that have sufficient capacity to serve my new connection request, system comes up with this location here. And routes then all the way back to here, considering the costs for the new build any sweet dump and the existing assets that can be reused, give you a cost give you total distance. And I think what's what's most important is also showing you what other prospects are you passing with this new build that you're doing, show you pay for every location here, give you the information of the location of those locations. So that you know, okay, we can maybe win a couple of these, when we're building this out. So we're not only need to consider that single location here. But all these other prospects have a winning win rate, certain win rates, certain revenue attached to it. And that can help with with this opportunity. And so what we want to do is we want to empower sales sales engineering team to optimize their performance, make sure that they can get estimates out quickly, and accurately. The first way that we want to do is is by integrating the workflow. So making sure that the asset information that you have, so or your existing network assets are fully available for the sales workflow. So when you're doing these estimates, when you're assessing the viability of an effort connection, you need to know where you have your capacity, where your existing assets are located, so that you know how to make a good connection and to determine that where you want to connect, you need smart routing, you need to be able to take into account all of the cost information for new builds, any obstacles, any, anything that influences the routing and needs to be considered to tie the the the mall point of the building back to tie point on your existing existing network. And then what you want to do is you want to also need what we also offer is dynamic routing control and editing. So we have our smart routing that does things in an automated way. But as a user as a sales engineer or fiber engineer, you will have local information, you have information on the area, more insights, you might not have all the data available that can feed the algorithms in the system. And then we can offer editing capabilities to efficiently make changes to the routes to come with come up with a more accurate estimate, so that you can be assured that you can build a network, build out a connection in what was calculated. And lastly, it's the opportunity management. So allowing you to identify all the potential customers that you can, that you could be able to connect when you're assessing the opportunity, or also giving you the I mean, with this automation of the system, allowing you to run these estimates involved for any potential customer in your in your area, give you insights in the cost to to connect every single one of those. And benefits with this is first one is improving conversion rates. So what we saw is the key factor to do winning these is being able to come back with an answer quickly. So with the automation, and the integration, we want to help to reduce the time and improve the conversion rate. Make sure that they you avoid the Yeah, we have moved on. And so yeah, from from your customer conversation. And then second one is, we want to enhance the return on investment. So our smart routing algorithms taken into account more costs, you get get accurate costs insights. And with the routing control that you have, you can even fine tune the estimates very easily, so that you have good insights in your calls going into the project going to the sale going into construction, and don't get any any surprises. And then lastly, it's the proactive opportunity management. So getting a view on all the potential customers when you're doing a doing an estimate, and being able to do that large scale analysis. So moving you from more inbound and not having time to do that analysis, due to automation and those prospect information, move that to more proactive approach and more outbound approach. Now, what about the future? So again, more like a copilot way of working, asking the system to create a quote, to provide a connection to a particular location. So moving away from manual steps there, as well, and making sure that you have a fully integrated workflow with minimal interaction. So requests that's that's coming in. Received by the CRM system can optimize the route come up with a quote, taking into account all sorts of data surface data, your existing network asset data, other imagery or like a lighter data sources can be taken into account. And then I still be a vision, a future where you still have a sales engineer who's going to be able to approve the estimates still, yeah, decision to be made whether you want to go and send out a crew to make that connection and make sure that's worthwhile. But yeah, optimize the workflow as much as an ultimate workflow as much as possible. So once it's approved, make sure that you can issue permits, schedule the work, send out a crew. And again, like what Stefan covered, make sure that yeah, it's commissioned, and then the data gets updated automatically back into the system. This is more for our inbound approach again, so connection coming in. And then what we're seeing more from an outbound perspective, or taking into account more data is yeah, world where you get warned about things that come up for the estimate. So looking at a building that's requiring a connection, we have our network here come up with the shortest path, but system warning you, okay, there's some problems that you need to know on this route, taking aerial, but we have insights in our assets. And there's, yeah, an upgrade that needs to happen to polls in the area. So take into account that cost. There's special sort of tiling that's in this area here. So make sure that you foresee cost premium to make that connection. But moving into a more predictive state is knowing that there might be some additional prospects like what I covered, or maybe buildings that are being built. So there might be some new office buildings coming into the area and being aware of that, take that into account, to come up with a different path to make that connection. Because it's just more worthwhile. So you will have a longer connection, the more expensive connection, but considering all the potential of these new buildings that are coming in, that needs to be considered for the building. And that's, that's where we'll get in a very nice state. Another example is looking at same sort of layout. Imagine that a network is being built already. So you have a cable going in, you have a plan being done. So construction is being planned in the next couple of weeks to extend the network, lay a new cable, then to become predictive in your sales, should be aware that this cable is being built, and it's passing a couple of prospects that's shown interest in the past, or that you know are good candidates. So you want to engage your sales team to reach out to these customers and see whether they're interested in a connection. Imagine that they are interested, you should be aware that the cable that was foreseen might not be sufficient to provide that connection. Make sure that you have sufficient free duct capacity to make those connections in the future. So that interaction back from your sales to your actual construction, that might already be in motion. That's something that should be able to cover. Also indicate already, okay, small adjustment to the plan, make sure that there's a structure here in this location to serve those customers in the future more easily. So engage from sales back to proof or for other projects that are ongoing. And then when it becomes interesting as well is if you have a good view on your prospect information, all the potential customers in the area, want to highlight, okay, this building right here, before this network was being built, this was not that interesting as well, was a bit far from our network, was difficult to reach, the business case doesn't make sense. But when this network is coming in here, this is now becoming an interesting opportunity. So again, engage your sales to reach out to these customers and get them to see whether there's a connection that can be done in the future. There's some key parts to make all of this work, which I want to highlight. First one is good data. So the same garbage in, garbage out, or maybe there's no data and all that that can be leveraged. Then it's very difficult to get into a predictive sales stage. So you need good insights about the area, competitive information, and all of the data on prospects or buildings that's coming into the area need to be known. Anything that influences the costs, like surface information, subsurface information, poll data, also information on your existing assets and things that are happening on your network. So make sure you have up-to-date information available about available capacity, information about frequent cable breaks or fibers that you're leasing, projects that are under construction. All of that can be considered to become more predictive in your sales. And then lastly is also good cost information or information about how long permitting takes or how long it takes to complete the network build. All of that is good to have to make this work. And secondly, you need the functionality in your product, strong algorithms to leverage that data and give you actionable insights. And then lastly, it's make sure that everything is integrated. So minimize the amount of manual interactions that you need to avoid making mistakes and wasting time. And yeah, you need to be able to, you need to make sure that the data that you're using is staying up to date. So this data can come from different systems. So to make sure that everything's working together data-wise, but also in terms of applications. So you might have a CRM for your sales, you have your inventory solution, workflow system for construction, marketing systems, your OSS. So everything needs to be integrated to work well together. And with that, I'm gonna hand it over to Stefan again to wrap up the session with some key takeaways. Thanks, Jonas. So basically there's, you know, there's a lot of takeaways and a lot of conversation that we can have about, you know, using, you know, better data to make better decisions. But, you know, if we weren't to summarize this for operations, if you have really good asset inventory data, you can help your systems, you know, proactively understand fault location and impact. So not just where the fault is, but what sits behind the fault point and how it's how many customers can get up, you know, impacted by a fault. And with that, you can actually help reduce customer turn and frustration because you're not having outages that last, you know, too long or cannot be, you know, quickly resolved or outages that go in and your customers are not aware of. So that helps a lot with keeping your customers, you know, from, you know, from jumping ship just because there's, you know, there's operational issues. And from a sales perspective, right, using automation and integration with this, you know, data can help make sure that you're winning more opportunities, right? Because you're capturing opportunities that might be hidden. You're looking at locations that, you know, might be underserved. And with that, you can discover new opportunities and, you know, increase your revenue with predictive sales. So in short, with better data, you have more ROI and you end up with happier customers. And with that, I'm going to open the floor for questions. Great. Thank you both very much. This is David again. And we do have some questions that came in. So we will go through some of those here. Just to start things off. Someone is asking, are there best practices available around how to integrate physical asset management with other OSS platforms? Yeah, so that's a really good question. This is, you know, fairly early in the industry. So a lot of best practices have started to, you know, kind of like form and evolve. But the three key things that we can talk about that is a making sure that attributes and metadata are actually consistent across systems. So you understand, even if there's differences in like naming conventions or attribute names, that you're replicating that from, you know, from ordering all the way to deployment. So you have that consistency of visibility. The second part is making sure that you're at API level and trying to avoid as much as possible proprietary formats or file integrations or things like that. APIs are king. It makes integration a lot easier and a lot faster and a lot more scalable. And then the last one is don't be afraid to ask your vendors for integration capabilities. You'd be surprised how many vendors are actually jumping at the opportunity to integrate with the physical asset management. One great example is your test and turn up and fiber testing vendors, which, you know, used to have their own systems, their own maps. And now they're realizing that there's a great opportunity in terms of having that outside plant and inside plant model integrate with their systems because we get more accurate visibility and they get to pretty much like just run a closed loop cycle between the sign, building the infrastructure so it can be tested during test and turn up that test and turn up automation and storing the results and making sure that that data is consistently being kept across both systems without, you know, any potential gaps. Got it. Thank you. Let's see. Moving on to the next one here. And as a reminder for our attendees, just if you do have a question, you can type those into the questions tool, which is located in the upper right hand corner. So next we have how can you manage workflows from an end user perspective? Yeah, I'll take that one as well. You basically have to think about the end user right off the off the application. You know, if you're building this primarily to assist operations, right, your workflows need to be operations first. So that means that you need to inform your operators about when services go up and be able to pass that data and make that data visible to them when the service goes up and goes live and make sure that the data is then being passed through network management systems. So when there's a fault or when there's an event or a customer call in, they can actually reference that, you know, first and foremost. So building those workflows has to be done from an end user perspective first and thinking not so much the the data architect or your traditional like OSS engineer, but more like, you know, the person that's actually going to be picking up the phone and looking at the call, what data do they need to see? If they're turning up a service, what data is required to make that test and turn up like really quick? If they're commissioning a customer, what data is required? And just build that workflow from that perspective. Great. Let's see. So along the same lines, what data can I use for predictive sales? Yeah, I'll I'll take that one. So, yeah, basically, I covered it a bit in presentation as well. But basically, any data that can can have a impact on the cost of your estimate or the both, I think your your cost and OPEX cost of of an estimate. But and also anything that can have an impact on potential revenue of the estimate. So getting insights in all of the potential locations is is key. So having data that shows you where are these locations, but also like, yeah, what competitor is serving this area or any demographic information on the area. Is is very interesting to have and can be used for for predictive sales. But basically, yeah, any data for the area that you're serving can be of meaning if you have the right algorithms to to consider them. And again, along the same lines, somebody else is asking what kind of information is needed to run estimates? Yeah, I think I think that's that's that's asking about, OK, for what's the minimum requirements to run estimates with with our solution? So at the least, you need information about your existing assets, right? So you need to know where to connect that that new customer up to and then the cost information about about the area. You can do a shorter spot calculation only for a new connection. But you have to really assess get to to an estimate, get to a quote. You need some some cost information as well. So you need to know, OK, for a new build, a new underground build or new aerial build. What's my cost per foot? And also for existing builds, if I want to reuse existing underground infrastructure, aerial infrastructure again, what's my cost per foot there? Are there any particular permit costs that I need to to consider, for example, for a railroad crossing or when using using a bridge or maybe some some some other aspects? So basic cost information and insights in your existing assets. That's that's basically what you need to to get started to run estimates and get get some some some quotes out of the system. All right. Great. Let's see here. Once again, if you do have questions, just type them into the question box. But we have one more in the queue right now. And this question is, can you support both aerial and underground networks? Yeah, from from a sales perspective. Yeah, definitely. So like I said, if you're if you have aerial assets, then we can use them. If you know the cost for using aerial information, we can use them. And also for for underground, we can we can use them. We can run quotes for new underground builds or you using existing underground assets. So, Stefan, if you want to add anything there. Yeah. From from an operational perspective, we support pretty much any network modeling that you can think of. So we can support, you know, overground and underground, you know, fiber cable so we can do aerials, we can do micro ducts, we can do regular ducts, trenches, you know, street levels, everything that you can model, you can model and we can do hybrid technology as well. So if you're doing fiber to a location and then a different technology for your drops, we can support that. So that actually wraps up questions that we've received so far. So thank you for submitting those. But thank you, Jonas and Stefan, for joining us today and for sharing this information and your expertise with us. We appreciate it. And thank you, everybody, for joining as well. Just a couple of brief announcements. I'll turn the floor back over to Stefan and Jonas to see if there's any sort of final words or wrap up that you wanted to add here. Yeah, I'll do a quick wrap up. So, you know, just keep in mind, as we talked about this idea of using, you know, your data and making your operations and your cells more predictive. This all starts with the idea that you have a, you know, robust system of record that can be queried by every application that you have in your OSS and BSS, you know, stack. So it's about breaking the silos that, you know, most operators create around data and making sure that that data becomes actionable for, you know, folks that may not be the target audience about it. So as you start thinking or walk away and think about, you know, what things can you do with your data? A lot of this data you already have. You just need to, like, set it free and make sure that it's integratable with other systems in your stack. Got it. And Jonas, anything else to add there? No, I think, yeah, what Stefan said is very true. Also for sales, I mean, you can have a lot of good insights in all the potential customers that you could be able to connect within your area. And a lot of information about, yes, surfaces and subsurfaces. Make sure that, I mean, know where rock barriers are. But if you don't have good data, good quality data about your existing assets, then, yeah, although the quotes that come out, yeah, you cannot trust the information that comes out of the system. So you need a good system that's easily to maintain, easily to keep up to date. Make sure that you have all the information there about your available capacity and can trust what is in there and make sure that what is in your system is actually the situation that it is in the field. And that's where it all starts. Perfect. And again, I just want to thank you both once again for taking time. Thank you to IQGEO for today's webinar. And with that, we just have a couple of quick announcements here to wrap things up. First of all, we do have our OpticPath program. If you want to find out how you can volunteer and help contribute to that program, this is our program that trains the future fiber technicians from the FBA. So please do, if you're interested in that program, please do. Please follow that QR code and have a look. There'll also be a link in the chat here. And with that, just a quick reminder that to go out to the FBA website, check out what upcoming webinars we have. Every Wednesday, we also have our Fiber for Breakfast webinar featuring Gary Bolton, our CEO and president here at FBA. So you can actually subscribe to attend all of those if you like. So go out to our website, check it out. We appreciate it. And we appreciate everybody's time and interest today and look forward to seeing you on the next one. Thanks, everyone. Bye.