Setting new speed and optimization industry benchmarks for network design and management.

Good morning or good afternoon depending on where you are joining us from today. Welcome and thank you for taking the time to attend our webinar on the fastest telecom network management solution. I'm Kelly Barford, Digital Marketing Director at IQGeo and I will be helping with some of the logistics for today's session. Just before we get started, I wanted to let you know that we will be taking some questions at the end. So please type them into the question box which can be found on your GoToWebinar side panel. We will try to get through as many as we can and if we don't get to yours during today's live webinar, we will follow up with you afterwards. I will now hand over to our hosts. So over to you Jay and Chad. Thank you Kelly and welcome to the presentation today. My name is Jake Adman. I'm one of the co-founders of IQGeo and I run the enterprise group at IQGeo. I'm joined by Chad Smith. Chad has a long history in the telecommunications marketplace working with a broad array of different customers and Chad will be doing the most of the presentation today giving you a live demonstration of our telecom network management. As Kelly said, please type questions into the chat and we'll take those questions at the end. What we're going to cover today is obviously just a piece of the telecom network life cycle. So we're going to focus on the planning and design aspect of the whole network life cycle. We do have solutions that cover the sales and marketing, managing construction, knock and operations and even customer service. But we have a limited time today so the focus will absolutely be on the planning and design aspects. So we get a lot of comments about just the simplicity of calling our solution fast. But we believe fast covers many different aspects of what you're trying to do. So it's not just the operation of the solution being fast. It's faster deploy. How do you get people up and running and roll out across an organization? It's faster train people because it's simple to use. And obviously it's fast to operate and we'll hope to show you that today. So what we're attempting to do for organizations is accelerate the planning and high level design or working in conjunction with partners on that. Produce low level designs as quickly as possible. We're going to do a seamless transition into field walkouts and transmit those updates back to the office in real time. And this all has a positive impact on them going out and doing construction and ultimately data quality, which leads to improved network maintenance. And so the solution that we deliver is built from the ground up from telecom for telecom companies. We're not trying to adapt a solution built for another industry. We're absolutely focused on network infrastructure. It is cloud native and mobile first, which we believe is basically table stakes now in the industry to produce a solution. We try and deliver real time access to data across the organization. So not just siloed. Everyone should have access to this information. And we package up workflows that are specifically designed for telecom operators, which you can use out of the box or you can adapt and configure to your mode of operation. And our customers can leverage over 100 different telecom integrations that we've done to other major systems that we see in our customer base. And, you know, the proof we feel of this isn't as telling you that it's really that we're managing to onboard over a customer a week onto our platform currently. And that's kind of what we see is that we're working to improve our processes to increase that as demand for the solution increases. So some of the will show a lot of different functionality today, but some of the areas of acceleration we wanted to highlight design assistance. So these are tools that enable you to design and lay out your network quicker. We have an integrated inside and outside plant model, which is very simple to use and navigate. We allow users to build on the fly assemblies. So if they create an object which has many different facets to it and they can want to use that again and again, either in their session or over the long time in their designs, they can just save that to the right-hand area of our solution and just click and use that ongoing. Embedded Google Maps and Street View, if you've seen our solutions before, you'll be able to identify that that's a common use with our customers. Easy identification of port and strand fiber availability is again, obviously something that's very, very necessary once you're trying to sell your network and design additional capabilities within your network. We allow an instant view of the planned network and this helps with collaboration across your organization to make sure that people know exactly what's going on and what's being designed at any point in time. And then we'll show some flexibility in terms of the visualization. So different people work in different ways. We'll show tree views of your network, schematic views and geospatial network views all integrated together. And then this obviously comes with a seamless online and offline mobility as so much of this work now happens in the field. And that's one of the biggest slowdown areas if you don't have a seamless mobility solution. So with that, I'm going to hand over to Chad and Chad's going to take you through a demonstration. And as we said earlier, please, please ask questions. We will take them at the end and answer as many as we can. Thanks, Jay. Let me get my screen share here. Let me know if everybody, Jay, can you see the screen all right? I'll assume that's a yes. Yes. Yes. We can see it now, Chad. Thanks, Kelly. So thank you all for attending and I'm very happy to be presenting this to you. I think what Jay mentioned early on is very, very relevant to the points being made in that we did develop a platform mobility first. And for those of you who have seen the platform before IQGO, you'll see that the screen, this application looks very similar to what you've seen in platform and our capture products and other products that we've had on the platform. And it's just been extended to perform network modeling and design. So it's got the same ease of use that you've grown familiar with, those of you who use it in the mobility side that you will have for network modeling and planning. And for those of you who haven't seen it, I'll just give a quick anatomy of what we have on the screen here. So we will start over on the left where we've got all of our different objects and layers that you can turn on in the network. And these can be fed from third parties. And in fact, we're connected to one of our other products, Network Revenue Optimizer here, where we can bring in the layers from the automated route planning into our network manager platform. And then we also have a list of the available structures that you see on the screen in our containerized database model. And all of the network equipment that's been extended into the platform thus far. The details pane, when we get down to individual object information, we'll see that show up in the details. And this is a very powerful one box search tool that we have in the platform for navigating the GIS, either by Google-based address information or other information you might have in your system that you'd like to query, or asset information that you can create index and create queries and searches against in our system. Just through configuration. There's an array of tools at the top. So we have the ones we'll primarily be focused on today will be the schematic view, which comes in handy quite a bit. We'll be in and out of schematic view quite a bit. The tools palette, which is where we have some of our semi-automation and some of our efficiency tools located and our specs interface. The structure palette, where all of the civil structure, which is what you're seeing here loaded on the right currently. These are favorites. These are assemblies that were created of objects that are typically placed with certain attributes that are saved here simply by right-click and add object and add assembly once you've populated it the way you like. And similarly, you'll see us get into the equipment palette, which is all of our fiber cabling and network objects for fiber network modeling. So we also want to stress the flexibility of the platform. So if I jump back here real quick, we have a configuration dashboard. And in the configuration dashboard, this is where all of the work is done to extend the network model, to create new features, and apply things to different layers, bring in other data sources, and upload data. It's a very simple, easy-to-use dashboard and UI. And you have the ability to extend your network model with new types of equipment, with new types of behaviors, just through configuration. So if we come back over to our GIS context again, we'll go ahead and take a look at some of the design that's been done. We have, in this view, we have a large number of fiber distribution polygons. These are for specific distribution points in a 1 by 16 splitter ratio. And we also have a couple of projects in progress. So we do design state modeling in the platform. So, you know, what we've got here, for instance, is a flex map design scenario that's in a designing state. So we have a full state model that's configurable by the user through the same configuration pane that I just showed. And then we also have an area over here that is more standard distribution that's in a designing state as well, which is just 1 by 16 splitters attached to splice trays within splice closures. And then we also have an area here that is constructed. We'll take a look at what this data looks like as it's built. And then we'll also build some data further into the demo. So the first thing you'll notice is in the layers pane under equipment, what we're doing is we're rendering where... We'll see what that looks like from the Google Aerial View. And we'll go back to the cleaner view so everyone can see this better. But we have splitter locations. We have a splice closure. And we have slack. And that is what's shown here on the equipment list. And that's what you're seeing here rendered above. And now if I select on a manhole location, in this case, it's actually a pedestal. So we see the information about that pedestal. We see any images that are associated with it that were attached and stored within the model. And then we've also got inside that we have our splice tray configuration. We also have our splitter location attached to the splice tray, all of our in and output ports. And one thing you'll notice is that as I interact with the detail pane, you'll see information highlight on the screen for that object. So that's one of the context views that we have. And I think it's very, very important to be able to see your data in multiple contexts. So if we do the same thing again, we've now opened up a schematic view showing us the connectivity at this point where we have our splitter location. You'll see that highlight on the GIS context. And we also have an input cable. And we have two cables that are patched through downline to two other splice locations. And we have all of our feeder cable or all of our drop cable, excuse me, connected up. And if you mouse over the splitter itself, it shows you the direction on the input and output sides of that. So you're seeing your data in multiple contexts here, which makes it very easy not to get lost in deep fiber modeling and fiber connectivity. One of the other things we have the ability to do, we have some drag and drop in the interface for ease of use. So this is one location here where I have a drop, a single one-inch drop conduit that's coming from this location. And it hasn't been assigned to a conduit yet. And I can simply drag and drop those into the appropriate conduits. So it's creating that relationship that the model is trying to drop again. Brought in from the whole philosophy of mobile first and ease of use for users. What we will look at now is how this connectivity model looks from a tracing view. So if I come in and start looking for cabinets. And I'll come to a location where I found the cabinet that I want to be able to trace from. What we also see is not only do we display the planned work on the GIS pane, where you can see the routes and cables and structures and things like that that are in planned state that were highlighted in yellow. But we also see these down at the structure model within the containerized model as well. So I see that there's a planned cable coming into this case from this particular design job as well as a patch panel that was inserted to house or to terminate cables for that design job. So what I'm interested in doing right now is first coming in and looking at all of the ports that are terminated on that panel. I can come in here. I can view any circuit information that's on those ports. So we can see here we've got a number of circuits coming in on a few different strands. And I can also trace this out and get a schematic representation of all of the fibers from this panel and their terminations. In the details pane, you see a tree in branch view. So if I look at branches, these are specific legs off of a splice or split. I can look at one branch. I can scroll down and we can see other branches. And if I zoom in on the GIS side, we can look and see where those branches go in the highlight view. So it's a nice way to interact with your network trace. And then we can also bring out that schematic view of this as well. I can turn on labels for this. So we can see where we have all of our ONT terminations and the total length of connection from that trace at the panel. We have our splice points, or excuse me, our splitter points, and then the ONTs. And again, you can navigate from either the list pane or you can navigate from the schematic views. So if I need to come down and investigate a bit about that splitter location, I can navigate the GIS through the schematic or through the detail pane. Or obviously through the GIS context. So we also have this ability to place assemblies. So I'll come in here and place one that was somewhat complex. I think anyone in the HFC world understands where you have a lot of HFC nodes, where they could be packed with two, four, six, or eight, maybe even more now, nodes, optical receivers. So if I select this manhole location right now, and I look at my pane, which is my equipment toolbar, equipment palette, these are saved assemblies. So these are ones that I had built one time and wanted to see placed over and over again in a specific configuration. So from there, I can grab this assembly. I can choose to populate some of the information there. We'll say this is an underground pet or vault. And this is all extendable attribute information through that configuration pane I started off by showing you. And if I hit save, we now see that we've got our HFC node closure. We have all of our HFC nodes with their input ports and output ports, receives and transmits. And we also have our splitter in here for splitting up all of the different, and this could be a D-box or this could be a split. But we have the splitter device mounted inside the closure to feed all of the input output ports on the nodes. So that's just one example of an assembly. We also have others. So if I come over here, I'll show you one more that was more relevant to my fiber to the home. If I come in and place this splice closure. And we'll see here, it's a splice closure that contains six trays and also a 1 by 16 split mounted on a specific tray within that closure. That's something that I place very regularly when I was doing my fiber design network. So, you know, how do we build these specs? The spec entry is quite simple. And I will show that. So if I come over to our tools palette and I select our spec manager, we can see what we have currently available. So if I look at structures, we have our manhole. And this is entirely extendable. I've added, I think, a few new objects to this data model over the last week. Small cells and Wi-Fi units and fiber map points for FlexTab. But if I come in and look at, let's say, let's look at the HFC node spec. And I think there's only one we see. There's an HFC node spec and the information that I captured from the manufacturer's specs. If I come over and look at cable. So, yeah, I have an extensive cable list now. But you can enter specs through the UI one at a time. Or if you have a large number of specs to bring in, you can export this out to the CSV. Make changes within that CSV. And simply import it back in to populate a large number of specs all in one go. And I can do that with... I have a few specs that I'd like to add. Drag and drop to the interface. We know that we're bringing in two new specs. And we were also updating 54. There was a new column added. And now we've got our new specs in the device catalog. So, now I do want to jump out and show you some of the other architectures we can support with the platform. So, it's very flexible for modeling different types of fiber architectures and extending the network model to provide more objects and add behaviors to objects. So, if I come up and start, I want to show where we have our long-haul network. So, if I search for all the objects that I have matching long-haul and I zoom to them, I've got a 103-mile long-haul fiber network that comes down from Houston, Texas up to Lufkin, Texas. And we'll be going to Lufkin here in a moment. You can see here that the cable specifications, we can navigate to them from the individual cable segments. We know that that's a 5,100-foot cable length for long-haul. It's a 96-kilometer fiber. And we have all the specification information and slack points along the way that are captured and so on. We can also look for different things in that long -haul model by searching for indexed information. So, I have a building hut for an EDFA location. And we can navigate to that from the one-box search. And we can look at a schematic view of what the connectivity looks like in that building. And we'll look at schematics in a bit more detail when we go to our knock location. And we can also take a look at the photo image that was captured there at that hut point. And we have our light amplifiers in there. And we have our patching in and out of the hut. And we also have noticed some information about the hut, that it's air-conditioned, heated, has backup generator. It is fence and even the access code to get into that location for a technician that might be using this in the field. We'll now take a real quick look at the dock location that's feeding this long-haul network. So, again, using that one-box search and looking at the indexed information in there, we can easily navigate from Arizona to Texas to all around the world. I can come down and select the knock. And we see in here it's not heavily populated, but we do have a lot of OLTs, patches, and fiber distribution panels here that are sending information out onto that 96-count fiber. So, the first thing I can do is look at the schematic of the building. And if I zoom in a bit, we can see more information appear based on the zoom ratio inside the schematic view. We can see that we have our OLT. We have our internal cable jumpers. We have our patch bays. And then we also have our distribution panels with a cable and a patch side. And then we can also see where that schematic leaves the building on the 96-count fiber. We can review that fiber cable just by selecting it from the schematic and looking at information about that. If we had to update any information about this, measured length, starting and ending meter mark, job ID, information that you can update on the cable if you want. So, now we're going to concentrate on some new design work. So, I'm actually going to head on over to Lufkin, Texas, which is about 105 miles north of us. Oh, specifically the overpass. We'll start there. So, one of the things to look at as far as the mobility side of this, and if you're a technician in the field and you want to understand a bit more context about what you're seeing in this GIS, one of the nice things, so if I go ahead and pop open this Google View, I can see where I have this pole location. I have my little Google Street View walker that's standing on the road that's looking at this object, and I can look and see where my trench is located in the field. So, if a technician's out there at night and they're having trouble understanding where they have their network and where the trenches are located, we can visualize where the trenches and where the pole locations are and things like that through this street view on their tablet in the field. And we'll look at more field use of this here in a moment. But what I do want to do, we're going to go to a specific location here, and we're going to do some aerial network and connect up a new commercial customer just to show you how the tools work. So, I've got a location right here, which is the Lufkin Daily News, and I want to provide them with a commercial fiber drop. I have an existing splice closure at this point. I know that I have 144-count cable coming to that splice, 36 fibers of which are occupied, so I have availability there. And I want to pull a new four-count drop from this location to where the Lufkin Daily News is. But I'm going to do this with the field tools. First, I'm going to, though, work through a bit of a design state model. So, I will come to design. Create an area. Now, the area does not confine you to designing within this area. It's more of a graphical marker of where design is located, but you can design outside of the polygon extents. So, we'll call this LDN. We'll say it's a network build project type and that this is a new project. Now, for those of you that have been involved with design state modeling in the past, we know that, you know, these different state models can trigger different actions in the system or they can be fed by other systems to create triggers or to trigger things within the state model. So, we can jump forward and say that a technician has been informed that they have a design to do. There's been some details given to them within the design project that they are to go out here and perform this drop in the aerial environment to this customer. So, I think Jay is going to speak for a moment while I get my tablet shared with everyone. Jay, Jay. Yeah. Yeah. I hope just to emphasize, because sometimes we forget this, everything Chad has done so far has been in a browser environment. So, no installation required at all. All works within a browser. And then the application that Chad's going to show now is more of a mobility application, but it's exactly the same code base. So, configurations, data, and any code that has been used to customize the system are all synced dynamically down to the mobile application. And it's just, as we said, the same code. So, it's very easy to deploy the system, and we feel that falls into the kind of fast area that we're trying to demonstrate to you. I'm going to hand it back to you, Chad. Thanks, Jay. Well, perfect timing. So, I did get the application connected up through my Safari browser on my iPad. So, nothing special about the iPad or anything, and we're just using the connected application. Now, there is an offline application that is app-based that uses extracts of the data for going into the field where you won't have cellular or Wi-Fi connectivity. We're focusing on the connected application through the Windows browser, excuse me, through the Safari browser on my tablet. And you can see down, and I'll use my mouse to highlight this, where we have a couple of different things down here where we can say we can enable touch styles, which pops out dialogues for the user if you prefer that. I don't prefer that. And then we also have the keyboard, and we can also turn on location. Now, I won't be turning on location because I'm not named Lufkin. So, what I will do, however, is I'm going to search for that new design that was created. So, if I just type in LDN, we'll see there was a design called LDN. That's what I'm searching for. And from here, you know, I would read the details about what's supposed to be performed, and really, it would be very simple. It would be that I'm providing a commercial drop, find a route, and perform a commercial drop engineer route to Lufkin Daily News. What I will do now is change it from a new state, which is not an editable state, to a designing state. And I'll open that design for editing. So, what you'll see down at the bottom of the screen, once I remove my keyboard, what you'll see down at the bottom of the screen is that it says designing LDN. And that is, lets me know that I'm connected and editable within that design project. And I'm going to go ahead and zoom in and start working now. So, you'll notice there's very little difference between using this on a tablet versus the desktop browser, which was a Chrome browser. What I will do first is I'm going to design an Arial route extension. Now, I can do that in a number of ways. I accidentally tapped the wrong thing there. Makes a difference when you're using a stylus versus your fingers. There we are. So, now, what I will do is I'll come in and use one of our efficiency tools, which is a layout strand tool. So, I can come in now and I'll say that we're going to have a 22-foot pole height. And we're also going to, in design at least, hope to only have a maximum spacing between poles of 200 feet. So, I can move this box out of the way with my stylus. And I can come in and pick a start point. So, we're placing poles. And you see we're getting the measurements where we place these. So, I've got my single pole location there. I can also add these through the structure palette, so individually. So, we can use the efficiency tool or we can use the tool just to place individual pole information with whatever details we'd like to capture about the pole. So, you can say that if that has a riser or not anchoring, we can fetch photos. And we can place a new pole location. I can come down and select a new point at this intersection. We'll do the same. And we'll place one more pole to where we're going to enter the building. So, with that, I can now start placing my aerial strand. And just tap all the way through to where we're going to enter the building. Or attach to the building, I should say. Now, I can come in. Also, if I want to capture a bit more information about how I'm connecting this aerial, I'm going to say that this is actually a building facade attachment, which it would be because that's where power entered the building. And now, I've got my pole line connected up and my structured network connected up. But I also see, hey, I may have missed a pole right there. I can easily come back in. Snap a pole to that location and insert it into the structure. So, now the next step would be to go ahead and add an ONT location at this building. So, I'll come into the utility closet. Using pressure on the stylus, I come in and I select my ONT that I want to put in that utility closet. Select the ONT type. I can also do some barcode scanning. So, again, an extension of what we've done with mobility so far. But if I want to do a barcode scan, we can scan data into the system through the mobility tool. So, I can use the voice tools, the narration tools on the device. I can use the location of the device. I can use all of the internal equipment on the device like the cameras and so on. So, what I've done there is just capture in some information about that ONT that I could scan on the ONT itself. So, the next step would be to go ahead and pull my drop. So, if I come over to my equipment palette, I have a list of tables that I place pretty regularly that I've saved on the right-hand pane with certain attribute information in them. And I'm going to select my four-count commercial drop and pick a start point and an end point for pulling that cable. And by hitting preview, it's going to show where on the structure route you're about to fill that cable. So, I'm pulling it from where that existing splice location is all the way to where I just placed my new ONT through my new aerial network. And then I'll hit save. So, when it's saved, we'll see a red arrow showing you the direction of the cable, where it was pulled from and to, and where it starts and terminates. From here, I can start doing some splice work. So, select the ONT, connect one or more ports at that location. So, if I just come down to connect, we have our four-count cable that we've placed, and we splice that into the, or connect that, create our connector and connect that at the ONT. I'll do the same at the existing splice closure. So, in the splice closure, I notice that I see that there is a number of splice trays there. They all look occupied. I can expand to see what the splicing looks like in any one of those locations. So, I can see I've got 12 fibers already spliced on a number of these trays. So, what I can do is add a new tray to the closure. I'll give that tray an ID or a number in this case. And now, I've got a new splice tray within that enclosure that I'm going to use to connect this customer. And if I go to connect cables, I'll look at my 144 that's coming into the splice location. And I'll scroll down to find myself a nice empty buffer. You can see there's a lot of existing fibers connected with circuits. And I will connect the white-blue to the blue fiber at that location. And now, if I go down and look, I can see the splice that exists at that location now that I just made. So, from here, what I would do is just to make sure I don't have a lot more splice work to do, I'll come in and select that location and I'll perform a trace. So, and I'll trace this upstream to see what more splicing needs to be done for this job. Now, I won't complete this all the way back to my hub, but I think everyone understands the ability they would have in here to splice their fiber in all the way through as part of this design job. And when I say that, we have a completed design here now as part of this that was state modeled in here and waiting for approval. And we can also do some design quality checks. And we can do a number of other things at the design level here for doing quality check and evaluation. We can also do OTDR tracing. So, if I ever needed to come out and measure from this point, I can say OTDR upstream. And we can key in the distance that we've gotten from our meter in the field. I'll just say it's 1,500. And we can see where that occurrence might be. So, it'll be right near where we have our Lufkin ISD building. We can look at the street view there and we can see what that environment might look like. And we can even see where we have our mid-span attachments to a building right there where we may have some interference or we may have a problem with our drop. One thing to add in, as Chad demonstrates, is we're seeing an increasing trend for outside design houses to use this in conjunction with their customers. A couple of reasons for that. Firstly, is the speed, which you can capture, is obviously the faster you can do designs, the better from a design contractor status. But also, the seamless way data gets transmitted to and from the customer's central database and the approval mechanisms, which Chad showed, and how they're triggered. So, we're finding a lot of benefits from that in speeding up, not transferring CAD files around, going through ETLs, but just using one seamless environment all the way from the sale, all the way through the construction into the maintenance. And we can come in and have a look now at this design that was completed in the field. So, I kind of stepped around the state modeling as an administrator and put this in directly at the as-built level of the database. But we can also adhere to the design workflow to have this go through approval processes and so on. Lastly, I'll say that we do have the ability within the platform of a mobile site. So, we've gotten very famous, I think, for the mobility and form data collection. Forms can absolutely be a part of the design workflow in the field. So, as part of a pre-construction survey, let's say, you may have to place different types of forms for form data collection about poll audit or poll information that you need for maybe a new attachment. I have a couple of examples here for a go-95 form for poll auditing, which can be done inside the same UI. And they can be captured as part of a design project. So, if it's my task to come out and work and do capture more information about this poll while in the field, we can create forms with lots of drop-downs, ownership, the inspection type, pictures that can be added to this. We also have the ability to do barcode scanning, like I showed, link documents. So, like in all of our circuit detail, I have linked customer SLA information. But, you know, we have the ability to create this type of a form. You can do that on the mobile UI. You can use it in mobile UI, or you can use that inside of the design application on the desktop and capture information like what you see here. And group them together for easy viewing. And that can all be included as part of your network modeling scenarios and your design workflows in the field. But I think that's about what I had to show, Jay, unless you think there's anything else you'd like me to focus on. No, I think that's great. I think we'll flip it back to me and I'll summarize. Okay. So, just to summarize, I hope we've shown you some of the capabilities that we have within the platform. They're obviously expanding all of the time. We can, as you can probably tell, Chad can demonstrate this for days as there's an awful lot of functionality within there. We are producing more design assistance all the time with feedback from our customers. Our goal is to provide a software platform that you don't need to call us up all the time to come and maintain. We are a software provider. So, we want to provide things like the specs and ways to extend the model as you require so that you can maintain them. Our business analyst can maintain that you don't need to be a coder and you don't need to call up some specialized consultancy from there. We hope we've been able to demonstrate the ease of use from it. It's an obsession of IQgeo to make things as easy to use as possible. And that's why we're very much focused on the browser-based solutions that are easy to deploy, but also the mobility solutions. As we feel the best way to help and maintain your network is to give the tools for the people who have stood in front of your network out in the field the best way to capture it and transmit that data back. I did want to mention we will be having some follow-up webinars on the other areas of our network lifecycle. So, our solution network revenue optimizer that assists in building both individual quotes and bulk RFPs, many different types of architectures, and integrates many different types of data into our solution to produce quotes in minutes that might take, you know, otherwise days of analysis. Our construction management solution takes designs that are produced and loaded into our network manager solution and allows you to automatically create tasks, assign tasks, manage contractors and employees, check performance as construction is going on, and manage the inspections and closeouts, and then transition that over into sales. And then our NOC solutions, which basically integrates what the people in the NOC is seeing and pushes that out to the field to allow more localized decisions to be made, proactive network maintenance, management of tickets, and a lot of real-time integrations with the intelligent devices in the field. So, we'll announce those, and we hope to see you all attend some of those sessions. And now I think we'll throw it out to some questions. I think Kelly, you're going to ask the questions. Kelly Cervantes Yes, thanks Jay and Chad. That was great. We've started to have quite a few questions come in, so I'll start going through a few of those. Okay, so first question, how is the data obtained, read from an existing database or via inquiry and location visit? Yeah, good question. The answer is all of the above. So, many of our customers are moving from an existing system of record solutions. So, we have data loading and ETLs for all of the standard solutions from, you know, Esri, Schneider, 3GIS, Hexagon, SpatialNet, SmallWorld. And we can read that data into our solution. We ingest many public different public data sets, as Chad was showing, Google, Bing, other types of publicly available. And then we have data loaders for a lot of the standard design types of solutions. So, ingesting from CAD systems, but also from some of the automated design solutions, such as BRI and CommSoft, which we know are growing in market presence. So, and then obviously you can capture your data yourselves. Or we do offer services to ingest data and do manual capture of data as well. Thanks, Jay. Okay, next question. How would I get started with this platform? I love what I'm seeing. I love that question. Yeah. Yeah, I think the first way is to contact us and we'll get one of our solutions architects. We have a number of people that understand a set of checklists. The quickest way to start is with our cloud-based solution. And that takes about a day to get up and running. And the training, you know, can be done in about a day as well. So, it's very quick to get up and running. For more enterprise clients, we have a series of very experienced consultants who handle those types of deployments across very large organizations. And, you know, at that stage, you need to have a more comprehensive plan than just getting up and running quickly. Okay, thanks, Jay. Next question. If I have multiple contractors working for me, can I control what information they see? Yes, again, it's very important. A lot of our customers want to separate what the contract is as a different contract companies are seeing. And so, you can segregate in any type of filtering way. So, you can segregate geographically. You can segregate just by who owns that particular contract. And you can go down to very granular levels. So, even down to the object level if required. Once those are set up, they automatically run. So, you can – it's easy to manage in an ongoing process. So, it's a great deal of flexibility there. Thanks, Jay. I've got time for a few more questions before we wrap up. So, the next one. Can you define design manager workflows from the office to the field and back? I'm going to let Chad answer this because I keep talking. Yes. Now, in the demo, I kind of subverted it a bit at the end. I started working at the top level of the database since I'm an administrator. But we have workflows that I started showing in the initial design setup where we had different state models. So, very easily we could have state models that were only editable by a certain user class that is maybe a field user. Where an initial design may get set up and assigned to a user and that they would have that new state model transition of that design in the field to make it editable for them for the job they have to do. And then upon a state model change from them, kick it back to somewhat notify someone in the office that now has to approve or run a design quality check costing and so on. So, yes, absolutely. So, we're going to do a lot of integration with the same application in the office or in the field. Yeah. And just to add to that, we do a lot of integrations with solutions such as SiteTracker and other project management, program management types of solutions as well. So, to automatically notify those solutions if you're using that to manage sign offs and financials and other areas. Thanks, guys. Okay, next question. Can we build entirely new network objects through configuration? Yes. So, that's something I've been doing over the last couple of weeks in particular where I built up new HFC node objects and Wi-Fi and small cell equipment and behaviors. So, you can, through configuration, define apparently new network model objects, configure their behaviors within the network, and make them available in the matter of 10 to 15 minutes to add a new object to the database and the data model. Yeah, we do feel we offer one of the most comprehensive models as a starting point. But obviously, the telecommunications industry is changing so quickly and the complexity of the networks is kind of exponential that you do need the ability to simply add new objects, fields, and things that pertain only to your organization into the system. All right. Thank you. Okay. Next question. How would I get trained on the IQgeo solution? We offer online training. Obviously, with these past crazy 18 months, everything has been moved to online, including kind of implementation. So, yeah, we offer online training, standardized training, or we can get some of our solutions, architects such as Chad, to go through particular scenarios. So, yeah, we're going to be able to do particular scenarios that pertain to your network architecture and your environment as well. Okay, great. Thank you. We'll take one more question. If I outsource my design. If I outsource my design, can my contractors design directly in your platform. Yeah. Yeah. And lots of conversations going on that. And we see a huge ROI in that. Once you get really into the depth of how do the contractors do this, I think we're working with many design houses now because they see a really quick way to do that. And the seamless transfer in a single system from design through into the source organization is just causing more and more benefits. And I don't even think we've really got our heads around what the full ROI of that is yet. I think we're just scratching the surface. Okay, thanks, Jay. We have had a couple of people that's asking about pricing and wanting to delve into a bit more detail on some of the things that Chad showed in his demo. So we will make sure that we follow up with you after this session. Thank you all for joining us. Thank you for Jay and Chad for hosting. We have recorded the session and we'll make sure that you will get the link to that shortly. As Jay mentioned, we have got more webinars coming up over the next few months and we'll make sure that you get the invite to those and keep an eye on our webinar page on the website. Thank you, everyone.