Select to view content in your preferred language

Ability to Export features not within a Subnetwork to JSON

165
3
Monday
LindseyStone
Frequent Contributor

This is regarding the Electric Utility Network. I'm required to export by subnetworks to JSON files in order to import them into our Outage Management System. This is the file format that is required by this vendor. I utilize the export subnetwork tool and have no issues with the export of each of our 54 subnetworks. In this situation with this vendor the GIS is the normal state of the our Distribution System and then within the OMS software they can temporarily open/close switches in the event an system/feeder outage or maintenance and their maps update accordingly to show the LIVE status of lines. So in reality the GIS is the normal state but the OMS could be showing a different state of LIVE.
The situation that I have is in places we have lines sitting between two OPEN switches in the GIS which is the normal state. So when I run the update network tool no subnetwork is applied to these lines because it stops at the OPEN switches which is exactly as I would expect. However, since no subnetwork is applied to this these lines, when I run the Export Subnetwork to export the subnetworks to JSON these lines are then left out of all my exports. The issue with this is, in the event of a LIVE situation of an outage or maintenance they may CLOSE these two switches in the field making this line LIVE. However in the OMS, this line will not even be on their maps because it didn't export with the rest of the subnetworks because it has none in the normal state of GIS, giving them an inaccurate map.
My question/suggestion is there needs to be a way to export these "Dead" lines to a JSON in the exact format as my subnetworks so I can import them into our OMS so they can be utilized as part of their maps.

3 Comments
RobertKrisher
MikeMillerGIS
Status changed to: Needs Clarification

We added a new switch state called Open-Traceable.  This switch state is a condition barrier for the subnetwork definition.  In your scenario, one Tie Switch would be set to Open, and one set to Open-Traceable.  When you run Export Subnetwork, you override the Subnetwork Definition and remove this condition barrier.  The de-energized section is included in the subnetwork that the Open Traceable tie switches subnetwork.  The phase information of that section is still reported as De-energized, as result of propagation is not recalculated on Export Subnetwork.

 

JohnAlsup

OpenTraceable.jpg