We have spoken frequently of our long-term relationship with MTEMC — including in articles such as MTEMC Makes Data-Driven Transformer Installation & Repair Decisions, State Zero Lets MTEMC Perform Maintenance, 10.2.1 Upgrade Sets MTEMC Up for Successful Roadmap, among many others. Most recently, we have been engaged with MTEMC on a large-scale and very complex effort to integrate Schneider Electric's Designer™ graphic work design application with some new systems being implemented there. Over the next several articles, we will talk about a lot of the cool new things we have designed and developed as part of this project.
In the article below, we will describe the steps to create a new Meter Panel with many individual service points contained within. The Meter Panel is a new feature class polygon that we have created for MTEMC. This feature class has a one-to-many relationship to service points. We manage the panel and service points within it.
In the screenshot below, I have selected a service point and underground secondary -- then opened an edit session.
Right-clicking on the underground secondary record brings up the option to add a Meter Panel.
Select "Add Meter Panel" to bring up the panel form.
I can add a number between 1 and 50, then hit the "Create" button. (Note that this limit of 50 is guided / restricted by a configuration file.)
After I click the "Create" button, four additional service points are added, each with a new Object ID and each taking on the same attributes as the original service point (Phase Designation, Energized Status, Board District, etc.). Fields that will change for the new service points include creation user, date created, and the LAT / LONG fields.
In addition, five new bus bars are created.
Note that the service points are related to the panel:
If I right-click the newly formed Meter Panel, I can add additional service points to the group I just created. The panels automatically adjust the layout of the Service Points, and the size of the Meter Panel is automatically adjusted to the optimal size for the Service Points within it.
Remember that for MTEMC the maximum number of service points on any single panel is 50. We have already added four service points to the existing one, for a total of five. Now if we try to add 50 more, we will get an error message that the maximum number we can add is only 45.
If we add two more service points, however, the same process occurs: the new service points – seven total now – are related to the panel.
Going to a different point on the map, I have selected a Service Point (OID 100) and an UG Secondary Line (OID 17717).
First thing I’m going to do is add three service points to the Meter Panel.
Now, reselecting features, I see I have a Meter Panel (OID 18418). Note how the panel ties to the service points just created and, similarly, how the service points are tied back to the Meter Panel OID.
We can rotate the Meter Panel by using the Esri Rotate tool on the "Editor" toolbar. Before this is done, take note of the LAT and LONG fields on one of the service points.
To do this, we select the Meter Panel, click the "Rotate Tool," and rotate the panel to the right.
The LAT / Long fields are updated as well. It’s not a huge change – note the last few decimal points – but each of the service point locations change as the Meter Panel is shifted.
If we add 15 more service points to the Meter Panel, it will look like this:
I can delete one of the Service Points by right-clicking on the Service Point, then clicking "Delete." Note that it also deletes the associated "Bus Bar."
It also deletes the Service Point from the Meter Panel on the map:
If we now click on Organize Meter Panel ...
... it will realign the service points within the Meter Panel:
For example, if you had seven service points in a 3x3 grid -- but then deleted one, it will automatically become a 3x2 grid since there are only six service points now.
Below is an example of several Meter Panels that have been placed:
As mentioned briefly above, creating this panel was the foundation for the big work to come: migrating MTEMC's existing data. We will talk more about that in our next article.