Building Better Networks at Connected Britain. 

Hi, my name is James Wheatley and I'm the Head of Product Management at IQGeo. I'm joined by my colleague Gustav Janssens who's the Chief Solutions Architect in Europe. We're here at Connected Britain and we're demonstrating our IQGeo Integrated Network Solution which provides capability right across the plan, design, build, operate and maintain network lifecycle for all of your physical inventory related to your fiber network. One of the key things that we see within that network lifecycle is the ability to connect the different processes and those different workflows and as a key component of that is our Workflow Manager product. We've just released a new version of that and we've been showing that at the show yesterday and today. So Gustav, what kind of feedback have you had from folks who saw the system yesterday? Well James, one of the things that people were asking was they're interested in the ticketing solution. So when they send field technicians out in the field, they need to assign tickets to the crews. But one of the key concerns that they had was of course as they're doing work on those tickets is that that work happens on the network. And so that information needs to be captured on the network data. So one particularly powerful feature that we're then able to show is the fact that since we combine both that network inventory piece and the ticketing piece is that as a tech if I have this ticket assigned to me is that that ticket is linked to a map view here and the underlying network data as well. So that as part of this ticket, I can go ahead and look at my network data directly. And as I do work on that tickets and capture information about my work, so be that the survey, be that construction work, is that that data can then be linked directly to that network feature. So it's not the case that the data sits in a ticketing solution, whilst you have your network data in another solution and you need to build an integration or data gets lost. That data gets directly stored on the feature itself. Okay. Now does that linkage, how does that linkage happen? Is that a manual process or an automatic process? What's the... Indeed. So the way that we do it is that if you have for instance a design area where you need to do construction work, is that you can create one ticket automatically for each feature and the associated work that he's doing. For instance a route needs to be dug, so there's a digging ticket, a specific closure needs to be installed, splicing needs to happen. So those tickets get created automatically based on the network features, which means of course that the ticket knows about the feature and we have that link as part of the ticket as it gets created. So there's no manual interaction needed there and all these things are automatically linked. Which also means that as the user updates for instance a ticket, closing it out, some attribute information on the underlying network feature gets updated automatically. Say for instance it's a construction project, the ticket gets closed, automatically we'll update an as-built attribute on the data, to say that it's now inbuilt and for instance then we could also capture an installation date, setting it to the current date. So that is not a manual thing that needs to be done anymore. And so the team out in the field doing the network construction or whatever the process may be, they're using that on a tablet device and then people in the office are in kind of real time nearly being able to see the progress of how that work is progressing in the field. Yeah, exactly. And that's one of the key questions that we get is as well, how do I digest that information? One simple example that we then are able to show is for instance using some thematic layers is that as network data gets, as the data gets, the network gets built. For instance, simply lines and points turn green on the map and the others are part of red. So you can really see your network getting built and expanding out. Another thing which we added in a recent release is to also add some dashboarding where at a glance you can see per project that you have going on, whether your tickets are progressing through the stages, right? Tickets are assigned, they're then being worked on, they're then completed out. So also through some simple dashboarding, you can then visually see that information. We've also then have clients who really build more advanced dashboards and business intelligence solutions. But this already gives people a quick and easy view right within the solution itself on this. And I guess that gives them the ability to see progress, but also identify issues where things aren't moving through the process and need to take corrective action to go and result. Exactly right. Yeah. And then they can check for instance with the field crews, if there is a problem with the data or, and that allows a much quicker resolution of officials as well. Yeah. Yeah. And we talked about construction, but I guess the concept and the approach of connecting the network asset to work that's being done can be applied to lots of different processes. Yes. Yes. They can go anywhere from construction, but equally survey for design to, for instance, maintenance tasks where you need to create a maintenance ticket per pole to, for instance, do pruning of vegetation. So yeah, it's pretty flexible in that regard. That's great. All right. Thanks very much. Thanks. You too. Thanks. Thanks.