Network Manager Electric digital-as-builds demo series. 

Network Manager Electric enables field users with access to designs for crews in the field to perform as-belts during the construction phase of a project. Today, we will show some simple updates during an as-belt workflow where we will make changes to the location of the proposed assets to their real-world location. Specifically, we'll follow the as-belt red lines that were performed previously and then perform the changes to the design that's shown above. So here, we have on the left, our single pane of glass where a user can come in and turn off design markups. Since we already have the information telling us that the meter was moved to the side of the building facing the road, we will make an edit to the connection. We will make an edit to the connected network since this meter is connected based off of the connection in the geographic topology of our Network Manager Electric Data Model. So specifically, we will go in and turn off the design markup feature so we don't have to interact with them. We will click on the building and edit the location of said building. We will zoom out. We will zoom out. We will then move it to the side of the building. And then click save. As we zoom out, we can tell that the network snapping pulls that change of the conductor to the location of where the meter is. That way we don't have to update each individual asset in the field. From here, when we're making these edits, IQGL's Anywhere application, which is cross-platform with iOS, Android, and Windows, enables users with GPS-enabled devices and third-party GPS receivers to locate these assets in their rural location. So when you're editing said features, typically when this little tag up at the top where it shows a little arrow pointing kind of northeast will give us the ability to locate and enable GPS on the device. And then from there, whenever we do the update location, there's a little button that shows up with a little, I would say, bullseye or kind of targeting symbol to kind of target the location of where the asset's going to be. So from here, we will cover the fact that this feature has been moved. And then next, what's specific about this is that during the staking process in the field or the location of where this meter is being connected, we could also show how we're able to enable the use of CUs to drive some of the attribution that was used. And if we needed to update specific CUs or compatible units, in other words, on an asset in the field, and if that were to have changed and we needed to update the asset with a different compatible unit, we could do so just by using this design tab that it just switched over on. And then I could go in, click on the little radio button, like assign CUs. And then it gives me the capability of being able to look at what's currently on there, which I could also go through and scroll through and look at what's available too. Since we have the correct pole compatible unit assigned to this structure, we will leave it as is. But this also shows the granularity of how many features were added. So we started it from this pole symbol over here on the very far left and then drew it all the way out to the end of where the meter is. That network needed to be expanded so that we can build in connectivity and build in a larger section of the network for a section of the area that's being built up. From here, as mentioned, those compatible units can drive capabilities within the features and pull over applicable attribution. Following the changes that we typically make during an as-built workflow, we're also going to have assigned tickets that are performed for the work that's being done in the field. So from here, we have a little blue dot in the middle of the actual location of the building. We'll click on that, which gives us the access of the location of where the ticket is based, which is going to be based at the residence house. So from here, we have access to looking at all the information on this ticket. But this ticket has actually been updated and assigned to someone else on the team. Me, representing as an actual crew representative or crew lead, I would go in and I would edit the ticket. Typically, the field user would go in and perform the work. Now, this is on feeder, what we would call feeder 274. And we, in this scenario, installed a new meter. From here, we know it's a residential location. The notes that are specific to this workflow was that the meter was different as far as the orientation for the design. So we can say meter location was changed. From here, we don't need any follow-up work, no additional comments. In this workflow, we also know that this was phase B. It is accessible. That is a meter number. We have specified that this is a 240. And for example, for a reading in this scenario, we could assume that, you know, we came back to the reading and say it's 0.23 kilowatts. And then here is where we could click to add attachments, specifically in a workflow where we wanted to go in and say we wanted to add either photos or any other tech documentation that might be required. That allows us to continue on with assigning this back to the crew that if changes needed to be made, given follow-on work might have been required in this scenario, we don't need it. So we'll set it to no, like we previously mentioned. And then we could send this through the back office and complete the ticket. So from here, we'll click save. Notice that the field will tell you if something is available or not. So we could say 2.3 for the field value. Click save. In those forms, it will also show that if something is not possible, we need to show that the form will allow you to say this is not a valid input. So from here, we will go back and we will also specify that the ticket update needs to be made. So the assignment of the ticket at this point, we were on site. It's field complete. Once it's field complete, it's updated in our workflow manager application and then triggers on the back side of the office from the field users point of view to be notified in the office so that QC can be performed. And now that that's performed from the device, the fact that we can pull extracts offline gives us the capability of pushing these changes to the field. I press this little orange dot. Sending the arrow up, that's pushing our changes from the device back to the office. And that's where quality control will be performed before the changes to this are now published from the design to the real world representation of the data, the parent version of the database.