Quickly deploy their fiber and capture maximum market share.

Thank you for joining us today and welcome to our webinar on delivering innovative fiber network management for a competitive market. I am Samaya Price, Digital Marketing Specialist at IQGeo and I'll be helping with some of the logistics for today's webinar. Just before we get started, I wanted to let you know that we'll be taking some questions at the end, so please type them into the question box throughout the webinar. We will try to get through as many as we can, but if we don't get to yours today, we will follow up with you afterwards. I will now hand over to our host, so over to you James and Matt. James Wheatley, Manager, Hi everyone, good to see you. Good morning or good afternoon depending on where you're joining us from. So we're all about building better networks. So what Matt and I are going to take you through today is to just give you a flavor in the time available of what we can do with our Network Manager telecom solution. So first to set a bit of context. So some of the challenges that you as operators face that we see quite commonly in the market. So we're all expected to do more with less. The days of endless budgets are long gone behind us. So we are all challenged to try and to drive more across all sorts of processes. So that's a very common theme that we see. We also see that a real challenge is that information still remains in a number of different silos. And so in that scenario, it's very hard to bring that information together and make informed decisions about how to drive the business forward. When that information is stuck either in someone's head or in different databases in different departments. Things are getting harder, not simpler. You know, no one predicted COVID coming along and that threw everyone a proverbial curveball. And so things are much more complicated. And and to solve some of those problems, you need to make things as simple as possible while still dealing with that complexity. So that that complexity is a key thing that everyone has to live and deal with. But we look to find ways to to solve that. And we're all familiar with that network lifecycle. I'll talk a little bit more about that in the next slide as well. But one of the key things that we see is the challenges that you as operators face in moving between the different stages of that lifecycle and how information data flows through that process. So that's another key area that we look at how we can help addressing some of those challenges. And then finally, you know, that change in in worker demographics. So there's obviously a group of individuals who are sort of towards the end of their careers, perhaps loads and loads of experience, been doing it for, you know, probably decades in some cases. And, you know, there's no problem that they can't solve sort of thing. But then at the other end of the spectrum, there's all the new folks that are joining the start in their careers. And they have very different expectations on their experience, particularly from a digital perspective. They expect their work life to operate in the same kind of seamless and dynamic way that their personal life does as well, as I'm continually being told by my teenage kids. And so achieving success against the backdrop of these challenges, it needs both process and technology change. You can't do it just, you know, by throwing software at a problem. That's not going to do it. You need to be able to look at processes as well. And importantly, therefore, it's how those software can help you enable those processes. So we talked about the network lifecycle. So IQGO is one of our key tenancies that we're able to provide capabilities across that network lifecycle from a product perspective. So I'll just touch on that and some of the key capabilities there. So underlying this is the concept that it's a single platform for every team. We're not talking about multiple different systems here. This is one platform that's underpinning the whole different aspects of the lifecycle. So if you look at sales and marketing, you build a network to sell it. That's the fundamental premise of that. So how can you maximize the revenue on that network? When you're looking at planning and designing a network, we've seen a huge growth in fiber. That shows no let up in the amount of fiber that's being installed. How can you accelerate that time from that, you know, first starting that design to actually getting that network in the ground and operational? And that design phase can be quite a considerable part of that overall process. How can you accelerate that? When you get to construction, obviously, you know, you want to be able to respond to the changes that are happening as quickly as possible. You want to be able to understand that something's been constructed in the field and is actually available to be able to offer service that that information flows back to back office systems. And you can turn up those services very quickly. You're not waiting until the end of the whole build out for a whole area to be able to to offer service. And then from an operations point of view, naturally, things go wrong. That's always going to be the case. Unforeseen things happen. How can you most effectively deal with those situations and make sure that that impact on the network is is minimized? And also from a customer services perspective, you know, being being proactive, everyone is very familiar with that situation. If we're unhappy with service, we tend to vote with our wallets. Everyone wants to avoid customer churn. So how can you proactively improve customer satisfaction? So that, as I said, that platform is underpinned by all that network documentation, the information about your network, where it is, how it's connected. That underpins all of these different processes. And that's what Network Manager provides for us. So if I just drill into some of these in a little bit more detail. So, again, going back to the sort of sales and marketing now, I touched on these at high level. Let's look at step by step each one. So you've got the network. How do you target particular high value customers to add on to the network? That's a great example. What do you do when a customer makes a request for service? You want to be able to very quickly respond to that request for service. You certainly don't want to have to roll a truck. There's great associated costs with that. You need to be fast at providing that response because your competitors may be faster than you. And speed is the name of the game at this stage of the process. But you need to be able to make sure that the estimate you provide, you're confident in that, at least to a reasonable percentage for a first pass. And you need to filter out those requests that are actually just simply not financially viable. And you don't want your teams wasting time and effort on those. You want the software to be able to help you filter those out. And being able to look at that historic data, being able to have different cost models for different areas, whether that be rural, urban, that kind of thing. And being able to support those front office sales guys with that ability based on that network data, again, is a key part of the solutions that are available. If we look at planning and design, as I said, you really want to accelerate that design part of the process. So automating the design wherever possible, making it as quick as you can, streamlining those processes. But also, if it warrants it to optimize that design in the sense of minimizing the amount of infrastructure that you're actually installing, because you can minimize the amount of infrastructure required. That obviously has a benefit from a cost perspective of the actual equipment, but also from a time to deploy perspective as well. If you've got teams doing less work in the field, that's the bulk of the cost. So being able to automate and optimize in that planning and design phase, again, is a good way to be able to maximize your return on investment. And of course, once we get to construction, that example I highlighted there around being able to very quickly turn around information from the field. There's a number of different aspects there. One in particular is obviously the network never gets built as it was designed. And we'd all like to think it would, but there's always some sort of variations. Making sure those variations get back into the network documentation as quickly and as seamlessly as possible is really fundamental. So that you ensure that when it comes to deliver service on that network, you can deliver that successfully. And around, you know, the management of the contractors. So it's very, very common. Most operators will be outsourcing construction and making sure that those contractors are part of this overall process, not separate to, but integrated into that process in a managed way, of course, with appropriate access to the information, but then being able for those contractors to be able to update information, have access to that, communicate with the, you know, with the owning teams, the supervisors, etc., to progress along those construction activities and have clear visibility of what's expected of them. So very much a digital workflow. And then as we transition into operations and maintenance, having that single view, being able to bring in data from a wide range of sources so that you've got that view of not just the network, but how the network is performing and how various pieces of equipment are operating to be able to identify, if you like, hotspots in the network where you've got some particular problems, perhaps from a perspective of emergency response. So being able in a disaster situation to be able to quickly understand what parts of the network have been impacted and where you should prioritize crews to be able to effectively respond to that. And of course, simple processes like inspection, lots of different, you know, might be just a simple pole inspection, regulatory requirements to do that in many countries and being able to digitize that process and make it as efficient as possible. It goes back to the, you know, do more with less mantra that we talked about at the beginning. And then finally, that customer service perspective, making sure that the teams dealing with customers actually have access to the information they need to be able to effectively communicate with those customers and give them that feedback of what's actually happening. And the same for the field teams that are actually dealing with these situations. So they've got common visibility. You've not got wasted effort as two teams are trying to solve the same problem. Those sort of simple things all underpinned by having the visibility of that network documentation. So at this point, I'd like to just throw up a poll question. So you can fingers on mice ready to click the button. So the question is, which area of your network lifecycle currently represents your greatest operational challenge? I don't get a vote, clearly. So I'll just give you a sec to click some buttons. Hopefully a few of you have done that. We've got a chance to take a look at the results. There we go. So the greatest operational challenge, planning and design. Excellent. Well, that's certainly an area that we believe we can help with. The other thing I think is that, you know, at the moment in the market, definitely seeing a huge focus on planning and design back to the point of, you know, putting a lot of network going into the ground. We're also seeing as well increasing feedback from operators that, you know, the next step in the process, construction processes are going to be the next area of significant focus. And ultimately, obviously, operations and maintenance and the sales and marketing point of view is equally going to be become important because once those networks are there, they need to be operated and sold. But that's really interesting feedback that at the moment, from your perspectives, that's the biggest challenge. And actually, that handover between the areas is coming a close second. So thanks very much for that feedback. That's really helpful. So what I'm going to do here, just briefly introduce Network Manager. Network Manager underpins the IQGO solution from a network documentation perspective and also is the sort of platform for doing, you know, when you've got some network design to do as well. So this is underpinning that is tackling some of those business challenges about providing users the ability to work anywhere online or offline. Different scenarios require different situations. And as I mentioned, being able to integrate contractors into the process. And then finally, you know, something that we see quite often is the complexity of deployment and the complexity of integration to be able to enable those flows. As we saw from the previous response, the handover between those different stages of the lifecycle is a key area of challenge. So I'm not going to talk too much about the actual capabilities solution because Matt's going to demonstrate that. But hopefully you'll see through Matt's presentation some of the benefits that you'll be able to realise around design management, around how you can model the network in a very simple, configurable way, being able to capture information quickly and very easily. And then the different views that you can present of the network. So at that point, I'll hand over to Matt. Matt. In a office application and give you an overview of Network Manager and how we model a fiber network. So I'm in the application. I've got my structures layer turned on so we can see the structural features on the map, where they're located. And if I select one of these features and I'll start with an aerial feature, in this case a pole, I can see what is attached to that pole. In this case a closure. And I can see that there are two splitters contained within this closure. And when you hover over a piece of equipment in Network Manager, parts of cables that are, you know, where fibers on those cables are interacting with that equipment are highlighted on the map. And this is a containment data model whereby our structures can contain equipment and equipment in turn can contain other equipment. And this helps us in regards to data storage, as well as you'll see a little bit later, makes it easier to update and modify the network. Going to select an underground asset here. So, in this case a manhole and that contains a closure with a number of trays. And on those trays we have splices recording. And as we expand out those splices, we can see the actual fiber to fiber connections that are taking place at that particular location. To further help with understanding connectivity, we have connectivity reports. So, think of these as splice reports or splice schedules. And these can be exported to various different formats including PDF, HTML, CSV, etc. And you can also include any circuit information on that report as well. Touching on circuits very quickly. We're also able to record where a customer has circuits. So, if I expand out some of these splices, I can see that over some of the splices we have circuits running over those fibers that are participating in the splice. In this case there's seven circuits that are running over these fibers that are interacting with this splice. And if I choose to show those circuits, I can see information about them. And selecting one, I can see details of a particular circuit. And the circuit in this case is the physical path of connectivity to serve this customer. And it has details of the customer as well as links to various things including the serving equipment and the terminating equipment. As well as the customer details and an address record for that particular customer. And wherever you are on the network, this circuit information is presented. So, if we go back to our pole here, for example, and expand out this splitter. Both the inside and the outside. We can see that there's circuits running over particular fibers. Whilst I've got this pole selected, I'm going to have a quick look at our Street View view. So, Street View and other Google services are available out of the box. And when I select a feature, the nearest Street View image is offered up to me to understand what's going on without having to send a crew out. So, getting a bit of information about the situation on the ground. And we can overlay whatever network asset you wish onto the Street View. In this case, we've got some underground route information as well as manholes and poles called out on this Street View image. Other Google services include the base maps. So, I can toggle on the satellite imagery, for example. A hybrid view where we get the labels and the satellite imagery. Or back to this cartographic representation. If you have your own Kedasta mapping or any other background mapping you want to leverage. As long as it's in an understandable geospatial format or provided as a web service. Then we'll be able to load that in. And your users will be able to access that as a base map, as a backdrop. To better understand the network data. One other thing in regards to the Google integration. If I do a search for a pole here. Then you can see we're also getting search results from Google. So, we can find specific addresses from the Google Gazetteer of addresses. As well as searching our own data. So, if I wanted to search for the poles in the current window. I can view all of that information. I can pull it up as a table. Export it out to various different formats. If I get a subset of information. As well as do further searches here. If I knew the specific ID of a pole, for example. I could start typing to zero in on what I was interested in. And then it would take me to that record. So, there's a number of data interrogation features within the IQGA platform. That your users can leverage. So, moving on to, again, talk about the fibre level connectivity and understanding that. I want to take a quick look at an MDU. And explain how we represent kind of the hierarchy of equipment. Via our containment view. As well as the fibre level connectivity via a schematic view. So, in this case I've selected an MDU. And on the left hand side I can see we've recorded some floors. Some rooms. And we've recorded where in the building particular pieces of equipment are. So, this containment view here. You think of as the hierarchy of where things are in the building. And then if I pull up the schematic. Then we have information about the connectivity. So, in this case we can see some internal cables. We can see some patch panels. We can see our ONTs. And as we hover over we get additional information about the fibres on particular cables that are connected to ports on equipment. And if I expand out an ONT in this case and then hover over it. Again, we can see on the schematic where this ONT is. And then therefore understand the connectivity within the building for that particular ONT. And from a kind of the fibre level. Whenever we have access to fibre level information in the product. You can right click and pull up a kind of set of options for running traces. And better understanding the network of that particular location. So, in this case I want to do a trace upstream. So, if I do that it's going to kind of run that trace. And I get the results for this particular trace. And I can have a look at my schematic. And maybe tweak it to have a vertical alignment. Zoom in to get more information about that. And it's basically a straight line diagram showing me the result of that particular trace. And then if I collapse that down a little bit I also get the map view. And all these views interact. So, if I was interested for example in a particular fibre splice. I could see where that is on the map. As well as where that is on this more logical representation here via the schematic. If I select my hub here. Again, all of the connectivity is presented to me via a schematic. And to get a bit more of an interesting straight line diagram. If I expand out one of these patch panels. And just select maybe the first four ports. And then do a trace downstream. That's going to run. And it will give me again all of the kind of physical connectivity information. From where I initiated my trace. And in this case it's also going to present me with that schematic. So I can understand. Better understand that connectivity from that location. If I go back to my previous trace. Where I ran from this ONT. Then one other thing to mention is we can pull up a report. Based on any kind of set of trace results. That will provide us with information about that trace. As well as some individual and cumulative estimated loss. So during the planning phase. If you are checking estimated loss information. Or you want to compare it to an actual set of test results you've received. You can run a trace and then pull up this report. And if I had the schematic open. Then I could pull up the report. And it would include the schematic. And all of these reports. As with the connectivity report. Can be exported to various different formats. I'd like to move on now. To just show some of the planning and design tools quickly. So I'm going to start by creating a new design. And a design is something that we use to contain any network edits. Updates or new areas that we're connecting potentially. All of that design information will be contained within this particular design. And it means we can try things out without committing them to the network. And damaging the as built network. So I'm going to open up this design. And this gives me access to some palettes. To create new features. And this can be set up to an individual user's needs. Or as an administrator. Someone can set this up with the common feature types. And it allows us to quickly place assets on the map. To start designing network. We have the concept of specifications. Whereby you can choose a specification. And it will auto populate particular fields. In this case the specification also populates the labour costs. But I can cancel that off. And choose other labour items. That are required for this particular manhole install for example. So we have costs associated with all of our feature types. So in this case this manhole. This spec here does have a cost. And now we've added some labour to that as well. They also have costs. So when we look at the bill of materials at the end. That's going to have both material and labour costs. So that's how you place a simple structural feature. But typically our customers will want to set up models. Or assemblies as we call them. Whereby they can place a structural feature. And it will have a whole raft of equipment within it. And they can place that in one operation. So I've set one up here. An underground secondary node. And I'm just going to pop that down here. And what it's done is it's got my labour costs. It's got the spec of manhole that I want to place. But also it's got a closure. With a splice tray and a splitter on that splice tray. So it's got that hierarchy already set up. And you can set up as many of these assemblies as you wish. To allow users to quickly place features. And have all of the equipment placed automatically. That's the same now for linear features. So we recently added the ability to have linear assemblies. So if I was to create a trench layout A for example. Then that's going to place an underground route. But it's also going to place conduits and cables within that route. So I can see everything that's been created here. And if I take a look at that route. Then I can see I've got a conduit. With three subconduits. And then two cables in two of the conduits. And it's very very easy to create new assemblies. Be it linear or structural. For linear for example. We just select a route. And I'm just going to check what this route has. So this route has a cable and some blown fibre bundles. And if I right click here. And choose add assembly. Then that's going to add that new assembly. And I can give it a name. And then start placing it. And every time I place it. It's going to create this hierarchy. In regards to linear features. That are contained within that assembly. We also have the concept of productivity tools. So some ship with the product. Like being able to lay out strand. To place overhead poles and routes. And we have a similar one for underground. Connect customers allows you to quickly create the infrastructure. To serve new customers. And then typically our customers may come to us. And request additional productivity tools. Which you can think of like macros. To make it faster for you to complete common design tasks. So I've created some network here. One other thing I want to show you. Is just how we route cables. So in regards to routing cables. If I want to place a new cable. I will choose my equipment palette. And I'll place a cable maybe between that cabinet and that manhole. If I preview that. It's going to route the shortest distance. I could force it to take a different route. By adding control points. But that's fine. I can then choose a specification of cable. Save that. And it's going to place that cable. Within those. Within the routes. Between these two features. And then just to show you. The kind of the connect cables interface. If I right click and choose connect cables. I can choose from. And to. In regards to. What I want to splice between. And I could pick maybe the green bundle. In this case. Select the entirety of the green bundle. And connect that to the blue bundle. On my new cable. Hit connect. And it's going to record that splice there. So it's very easy to connect up. Both. Fibres to fibres via splicing. And also. Fibres to. To ports on equipment. So having a look at my design. If I pull up the bullet materials. We can see that I've done a number of things here. We have material and labour costs. Where they're provided. And then we have a total. Cost as well. For the overall. Design. And what we can do. Is we can export this out. Again to various different formats. And use it as we need to. If I close out this design. One other thing I want to show. Is how users can understand what's coming. In regards to. The network. So I'm going to toggle on. My designs layer. And first off. This will show me boundaries. So this will show me where people are working. If I toggle on the structures layer. Then this will show me. Not only where people are working. But also. What's coming. So here we can see my new extension to the network. We can also see in orange. Anything that's been touched. In regards to existing network modifications. So this future view is very useful. For understanding what's coming. And we have a similar one for cables. Where you can toggle that on. To understand what new cables are being placed. Or what cables are being modified. It's also possible to understand. What's coming. At the kind of the fiber level. So if I select this cabinet here. I can see. I've got my closure. Various splices. And also a number of cables. That are kind of passing through. This particular cabinet. And if I turn on proposed objects. Then I can see new cables that are proposed. And the design they're proposed in. As well as new splices. So if I wanted to understand. What fibers are being used. On what cables. Then I can check that out. Before. You know. Trying to make use of those. Of those fibers. If they've already effectively been reserved. So I'm going to. Come back to this. And what I'd like to do next. Is jump out to a bit of a. Field use case. So here I am in a mobile app. It's a tablet. We have native apps. For iOS. Windows and Android. Everything I've just shown you. Is available. To our users. Via those native apps. Whether online or offline. In this case. I'm going to be working. Online. But equally. Everything I'm going to show you again. Would be available for our users. Whether online or offline. And as soon as they have internet connectivity. They get any changes. That have. Need to be. Brought down from the server. And anything they've captured. Will be synchronized back. So in this use case. We're in the construction phase. And we want to record the fact. That. Something has been built. Different to the plan. And we want to provide. Some supporting information as well. I've created a design. For this purpose. The type is field data correction. I've already opened it up. So I can start. Making modifications to the network. And this. This manhole here. I want to record the fact. That it's been built. The other side of the street. Due to the existence of a tree. With a tree preservation order. In the proposed location. Having selected the manhole. I can move it. To where it was actually constructed. And then I can also select the route. And modify that. Based on. What we actually had to build. To avoid this tree. I could use my location. To help me inform. More accurately. The actual route. If I was in the field. In this case. I'm just going to move it. As such. And what's nice is. If I select this cable here. You'll see the path of the cable. Has also been updated. So the containment model. Means that anything contained. Within our linear routes. Or equipment contained. Within our structures. Is updated. When the top level feature. Is modified. So I've moved. My manhole. And tidied up the route. I'm now going to provide. Some supplementary information. For the folks in the office. Via the markup palette. We can create points. Lines. Polygons. Markup text. And also add photos. Like with the assemblies. I showed you earlier. You can configure up. Certain configurations. Of these different pieces. Of markup. And add them as objects. Into our palette here. So you can easily place them. If it's something you're doing. On a regular basis. And that's what I've done. For a tree. With a TPO. Piece of text. It's been associated. With the underground route. That I had selected. When I created it. And then everything else. I've already configured up. So the colour. The text content. The fact I want to lead a line. And then I'm just going to pop down. Where I want that to be recorded. So that's great. I've now created. That little note. And the next thing I'm going to do. Is add a markup photo. And I'm going to pop that down here. And in this case. I want to. I want to have that associated. With a network object. So I can choose. To have that associated. In this case. Let's associate it. With the manhole. You can go okay. And that's now placed. That photo. Object for me. And I can now add. The actual photos. If I was in the field. I could take a photo. Or I could add a photo here. And we can add multiple photos. To this particular. Kind of markup object. And view them here. Via. Via this photo wall. So having completed that. I've now created my markup photo. And I've got my markup text. And then this would find its way. Back to the folks in the office. Who could review it. View that supplementary information. And ultimately. They could. Publish. The kind of. The proposed changes. So that we have an accurate. As built. At the end of the construction process. Another couple of things. I want to quickly show. First is the bulk update. So we've had a lot of requests. To be able to update. Multiple features in one go. So in this case. Perhaps you want to update. The build status. For a number of manholes. So I can select a result set. So I've got 13 manholes selected. Can now hit edit. And any shared attributes. Can be updated. By our users in the office. Or field. And you can configure. Which attributes you want to participate. In this bulk update. So if it was just the. The built checkbox. For example. Then all these other fields. Wouldn't appear. And then we could save that. And all of those objects. Would be updated. With the status of built. Next I'd like to quickly. Just show you the bulk. The bulk move tool. So again. This was something. That was requested. When you've got. For example. All of the assets. On one side of the street. And you actually built them. On the other side of the street. Then. You know. Maybe you would want to. Move those in one operation. So I've selected. A couple of manholes. A couple of poles. And an underground route. And if I choose the bulk move. Then it's going to check with me. That you want to move. And all the features. You've got selected. And then you can move that to. In this case. The other side of the street. Save that. And it's going to update. All those objects. And what's nice is. As per the containment model. Everything. Everything contained. Within anything there. So the routes. Any cables and conduits. The manholes and poles. Any equipment. Are also going to be. Updated. And with that. I'll bring this. Demonstration to a close. All right. Thanks very much Matt. So I just wanted to. To close with a couple of slides. Just to quickly talk over. Some of the advantages. That we see. So model anything. So you saw. The ability there. That Matt had an extensive model. To be able to document. The telecommunications network. And we see a very common need. To be able to extend that. As well often. And that's all possible. All through configuration. So there's no complicated. Data model upgrades. There's no. Operational downtime. And you make these changes. It's all configuration driven. You don't need to come to IQgeo. To do that. You can do that yourself. And you can extend that. To be able to build that. That digital twin. Of your network. And also you saw. The specifications in there as well. You saw at the end of Matt's presentation. The use of. Anywhere product. That allows you to be able to work. Online. Offline. Wherever you need to be able to. To do the work. And that's a key fundamental. Approach for IQgeo. That's something that we bake in. Right from the very beginning. And you're using the same capability. So hopefully you saw from the demonstration. That that wasn't anything different. Running in the tablet. That was the same capability. Matt had available. When he was running in a web browser. It was just optimized. To be able to use. In a tablet. And to be able to use. Offline as well. And the ability to integrate everything. I'll touch on that in a little. In a moment as well. Just to reinforce that message. But bringing all that information together. To be able to underpin. All of the various processes. That we talked about. At the outset of the webinar. And then finally. We're always looking to innovate. So some of the capabilities. That Matt showed you at the end. There are part of our most recent release. And we've got a very vibrant roadmap. That we're building out. You know for the rest of the year. Into next year and onwards. And we're continually looking at ways. That we can improve our capability. Integrate with other solutions. To give you know you guys. As customers. And the operators out in the field. A real value added capability. To solve some of the tricky business challenges. That you face. So this concept. If you like. The single plane of glass. That supports that overall life cycle. So you can bring data in. From many different places. You know we saw Google there. But you can use all the data sources as well. And particularly from an operational context. You're able to bring information in. And that can be from our system. But also from other typical GIS's. That you might have. Esri. The G Small World Solution. Hexagon. You might have acquired those. Through acquisition or whatever. And we can be able to provide that. That ability. Either complementary to. Or instead of. Those sorts of things. And bring them in. And talked about. How you can deal with that in the field. And you saw. You know field data capture there. And also. You know integration. So the typical kind of. Three letter acronyms. That are very common in the telecoms world. Whether that be your ERP. Your CRM systems. OSS or VSS. Being able to integrate. Information about the network. Is fundamental to be able to support. Effective operations. So that really. That's kind of. The conclusion. We've looked at the. Really the capability. That underpins. All of the different processes. You know. We have product capabilities. In each of these different areas. And we've looked at. What underpins. The majority of those. We could drill into more detail. In each of those. You know. In future sessions. I think one of the key things. There really is that. It's a single platform. For every team. And that's every team. That needs to use that. So you know. You've got access control. In their role based. You know. Enablers. So. So you're not struggling. With different systems. For different members of the team. You know. Whether they be. Employed by yourself. Or whether they be contractors. You've got. You know. A wide range of flexibility. In your control. To be able to. To manage that. So. At that point. Open it up. To questions. Thank you Matt. And James. They. We do actually have. Quite a few questions. That have come through. From the audience. So yeah. Let's pick out a few. We've got one here. That says. Is this product. Independent. Of any other. Of any other product. Or dependent. Like Esri. And network engineer. Okay. Yeah. So. So no. It's independent. Of any other. GIS platforms. Such as. Such as Esri. Or indeed. Network engineer. So yeah. You don't need. Esri. We can. Coexist. With those sorts of. Platforms. If that's. Required. But what Matt. Demonstrated there. That's. That's all our own software. Based on a lot of. Standard. Off the shelf. Technologies. So Postgres. Database. For example. So yeah. We're not dependent. On anything else. Okay. Great. We've got another one here. That says. Is this a physical network. Inventory tool. Product. Or planning tool. Only. It's a physical network. Inventory tool. That can do planning. So yeah. You can certainly. We've got a number of customers. That. They are using this. For purely for their. Their physical network. Inventory. And obviously. You need that capability. To be able to update. And modify the data. As part of. You know. Keeping the. The documentation. Up to date. Okay. And how do you determine. The most cost. Optimized number. Of connections. Per DP. So. So I can. I can. Take that one. So. So in regards. To the. The planning. Process. There's a number of. Things that you can do. So I showed. And I touched on. Some of the. Kind of manual design tools. For. For that kind of thing. If you want. Kind of. Cost optimized. Maybe automated design. There's options there. We have a fully integrated. Fiber planning tool. Which is when you're. Kind of doing. Medium to large. Volumes of. Of demand points. That you want to. Design a network for. More of an FTT. Kind of X scenario. We do have another module. That's more for. Estimating. So that. That's more about. Providing a number of. Demand points. Could be as few as one. Could be as many. As maybe. 50 or 60. For a new neighborhood. And again. It would. Kind of cost out. What's required. To serve those. Those customers. And give you some. Some routes. And some equipment. That you could then. Take forward. So when it does. Come to automation. With. There are some options. In the product. There's also some. Partnerships. We have. With. Some. Companies like. Cetix. And Comsoff. Who do. Automated planning. And we have tools. For loading data. From those systems. Whereby you have. A cost optimized. Kind of. High to. High level. To. Detailed design. Depending on. Which module. You're using. And what comes in. So that they're the options. If you want to make sure. That you're building. Kind of a cost optimized network. What I showed. Is if you're doing. More manual design. There are tools. In there. To check. You know. What is the cost. Of doing it this way. Maybe you have another design. Where you do a different. Design. And you compare. The bill of materials. Or a different way. To connect those premises. And then there's tools. In the product. For checking. Checking calculated loss. Or running other design rules. Against your design. To make sure. They're satisfying. Your criteria. So be it. Fully manual. A bit productive. Or automated. There's options. When you use us. As your. Kind of network. Documentation tool. We're getting quite a few questions. Coming through now. Next one is. How open is the data model? How can I communicate. With other software? So I can grab that one. As well. So. We do have a published. Format. That we call it. The comms data. Interchange format. That is documented. It's. Data is exportable. In that format. And that. That's kind of. Everything that. That we showed. So it. Includes structural features. It includes. Equipment. Cables. Conduits. The fiber level. Connectivity. That's fully documented. So. One option. For an integration. Is to. Kind of. Take that format. And leverage it. To. Inform other systems. About the physical. Kind of network. Inventory. We can also. Load data. In that format. Natively. So. In that sense. It's open. And documented. And because we have. These top level. Feature types. So. Structure. Equipment. Conduit. Cable. Etc. Everything you model. Falls into one of those categories. So you can have. You know. Like James said. You can model anything. And it will fall into that category. And it will be. Exportable. And loadable. In this. In this format. We appreciate. That that's not always possible. So we can. Develop loaders. From other. Formats. You know. Comsoft. And Cetix. And Biari. A good examples. Of what we've done so far. Where we interpret that data. And then load it. And then other options. For integrations. Are. You know. We have a REST API. We have mechanisms. For loading. Exporting. Just. Raw. Simple data. As CSV. Or shapefile. Etc. And those kind of bulk update. Capabilities. So. So really. We. We have a conversation. With the customer. To understand. What is the integration. You're looking for. And then. You know. Target the most appropriate approach. For delivering on that. That integration. Okay. And we've got another one here. It says. I like being able to see. The proposed changes. Made by others. On the off chance. The design needs to be cancelled. Is there a way. To revert changes. Or view values. Before they were changed. So we. We do have. Certainly. If your design is in flight. I. You're still working. In that design. And you haven't published it. You can compare. The kind of before. And after. There's also a conflict. Checking mechanism. Which will flag up. If for example. Someone else has modified. A specific asset. That you're then looking to leverage. Before completing. That publish operation. It will flag up. And say. Hey. The point. At which you created. This design. This object. Was. You know. In this location. With these attributes. Now. It's actually changed. And you want to publish. Are you okay. With. You know. Making. Additional changes. To this. That may wipe out. The other changes. So there is a mechanism. That users are notified. In regards to reverting. That. That is something. We're currently. Exploring. Both in regards. To. Kind of an audit history. On every object. So you know. The change over time. But also. An undo capability. So at the moment. When you've published that. If you did want to revert. You would need to create. A new. New design. To kind of. Work things back. To how they were before. But we're certainly. Exploring. Ways in which we can. Understand change. And potentially. Roll back. If needed. So whoever asked that question. I'd be very interested. In getting. Kind of the exact requirements. There. Because we'd happily. Take them. And look to inform. Our planning. On that point. And I guess. That's. A question. From someone. Using Small World. Perhaps. So I. I. You know. I've a lot of experience. With Small World. The mechanism. Used. Within Network Manager. To telecoms. Is. Is slightly. Different. To what Small World does. So it. It gives you. A bit more flexibility. And then. Then perhaps. You're. You're able to achieve. With. With Small World. Great. Another one here. How can we generate. Complete schematic. Of whole exchange. Or BOQ. In one go. In brackets. By selecting the exchange. Yes. That's another good question. So at the moment. That the schematics engine. Is. It's quite flexible. So. The. The. The two implementations. Of it. That I demonstrated. One is. I've run a trace. I want to view a schematic. Of the results. Of that trace. The other is. I've selected a structure. I want to view a schematic. Of that structure. So what we're looking to do. Is. Is exactly what was just described. Is. Is almost. Extend that schematic. To support other use cases. And one of those. Maybe like you just mentioned. Selecting an exchange. And. You know. Everything. Kind of within that area. Or downstream of that. Exchange building. Could then. Be. Presented in that schematic. To do that today. We'd need to select. A set of ports. On equipment. Run a trace. And then pull that up. And in your scenario. I don't think that would work. But we're certainly looking. To extend the. The schematic. For that. In regards to the bill. Of quantities. Again. You know. At the moment. It's implemented. It's implemented. On a design basis. But we're looking. To make that more flexible. So you can. Select a service area. An exchange area. Hit the button. And it's going to go away. And present you. With the. The bill of materials. For. For that area. So again. Things we're. Things we're looking into. But the products. Architected and built in a way. That we can add these things. Relatively easily. Because we've got that. Fundamental schematics engine. That bill of materials. And that. That kind of report. Format. We just need to. Kind of tweak the data. That's fed into those things. So for the exchange. Just need to make sure. We're. Kind of seeding the schematic. With the right data. And for the bill of materials. Exactly the same. We're seeding that bill of materials. Report with. With the right data. At the moment. It's from a design. But it could be from. You know. The contents of a service area. Or just the window extent. We've had that request. As well. That we're looking at. You know. Show me the cost of everything. In the current. Window. Okay. And another one here. Our network. Is a combination of. FTTX. And legacy. HFC. Which has been upgraded. To FTTX. Is there support. For designing. HFC. Networks. Yeah. So at the moment. The simple answer is. No. Not at the moment. But that's certainly. Something on our. Our roadmap. That we're looking at. Providing support for. Next year. So. Fibre is fully supported. And you can. We've got a number of customers. That have got HFC networks. And they are documented. In another GIS. And we can bring that information in. From a. You know. That single pane of glass. That I talked about. So you then can overlay that. With all the operational information. And that kind of thing. So you can. Provide a lot of benefit. To. To the field users. Are using the not. That kind of thing. But yeah. Network. Actual sort of network. Documentation. And design. Related to. To HFC. Is something that's on the roadmap. For next year. Great. We'll go through. Just a couple more questions. And I think we'll have to wrap it up then. So how can we allocate. Each fibre or circuit. Booked for a potential. Commercial customer. Do you want to. Pick that up Matt. Sure. So via the. The kind of the circuit management. We can record. Circuits. Or you know. Services. The workflow. For doing that. Can be. You can generate them. Within the product. So there's a mechanism. For creating a circuit. And you actually start. At the terminating equipment. You specify. The terminating equipment. The port on that equipment. And it will do a trace upstream. So it does. Require. The physical connectivity. Is complete. For that circuit. To be realised. And circuits are. Configured to have. To start on. A piece of. Originating. And then terminate. On a piece of terminating equipment. And you configure. What that is. For different circuit types. So you could have. You know. Backbone circuits. FTTH circuits. You could have. You know. Whatever circuit types you want. And you just specify. The kind of the rules for that. And you could create them. Alternatively. They can be created programmatically. If you have another system. That you want to load. That information from. Then again. As long as. That is storing. I don't know. The A and the B sides. For example. That has that. Reference to. You know. What is. Originating. And what is terminating. In regards to the equipment. That participate in that circuit. That could be loaded. From. Another system. We are also looking at. More enhanced. Route reservation capabilities. To further support. Our story. In regards to circuit management. Brilliant. Okay. We'll go for one more question. This is about data migration. How. How will existing GIS. Data get migrated. Into this. If they don't have the same properties. Currently. Precept. Default values. Maybe. So. Yeah. Sure. So. We. We have a loading framework. Whereby. You can configure mappings. Between. A feature type. Your source data. And a feature type. In the network manager model. So you can map. Fields. That. Don't have the same name. You can map. Feature types. That. That don't have the same name. You can apply filters. During that process. So basically. The first step. Is to configure. Up. What you want to map. From your source data. Onto the target model. Which will be. Whatever you've configured. Up in network manager. Now. There's kind of various levels. To. Migration and data loading. At the simplest level. It could be. I just want to know. Where things are. So you've just loaded the data. And then you can kind of. Toggle those layers. On and off. Now. Everything I just showed you. You know. That has another couple of levels. Of detail. So it has containment. Not only knowing. Where things are. But knowing. What they're in. So for example. You know. Knowing that this closure. Is. You know. Attached to this pole. Or contained within this manhole. Or this cables in. This duct. And this duct. Is in this root. So typically. What we do is. You know. After that. Configuration exercise. Of saying. Right. This feature type. Maps to this feature type. We would. Try and understand. Well. How do we build. That. Containment. From your source data. To our. To our model. And we have some. Sample loaders. That I've talked about. Previously. That we can use. As a starting point. We've also bought. Built some custom loaders. For customers. That. Build that. That containment. And that could be. Based on. Kind of geometric. Coincidence. So assuming. That if a cable. Runs. Kind of. The same. Kind of. Linear route. As another cable. Then they're. In the same trench. Or it could be. The source data model. Includes references. To. You know. This cable. Is contained. Within this duct. Maybe there's references. That we can use. So that's kind of. The next step. We could. We could build some logic. And use some of the knowledge. We already have. From other. Migrations. And data loading. Exercises. To build the containment. And then the final piece. Is if you've got. Kind of fiber level. Connectivity. In your source data. It's understanding. Well how is that recorded. So that we can take that. And as part of the load. Of bring that across. So it's not. A manual exercise. To build the connectivity. At the end. Maybe you don't have. That. That level of detail. If you're coming from. Maybe a pure. GIS system. Like an Esri. Or something. That doesn't have that concept. Of a telecoms model. Maybe some of this is moot. And you would have to. To use some of the tools. That I showed you earlier. To build that connectivity. But certainly. If it is there. Then. You know. We've got experience. Working with multiple. Different types of system. To perhaps. Build that connectivity. Automatically. So that. You know. You can. Use our front end. To. Provide the data. To field workers. Or migrate. From your. Existing system. To. To the IQ. Geo platform. Brilliant. Thank you guys. So much. For your questions. That's all. We've got time. For today. Thank you. For joining us. On this webinar. And thank you. To James. And Matt. A recorded version. Of this webinar. Will be available. For you to view. On demand. And we'll be sending out. A link shortly. Many thanks. Bye. Thanks. Bye. Bye now.