I'm mapping our electric data to the Utility Network Foundation v.1.
I have the whole group of fields below that I'm unable to match in the model.
Our electrical engineer thought it odd that there are not matches in the model.
I'm mapping our Breaker/Recloser features to Electric Devices to:
26- Med Voltage Circuit Breakers
and to 41 Medium Voltage Recloser.
I'm having trouble matching these fields:
Has anyone had any experience with matching data like these?
FAST_PHASE_CURVE | FAST PHASE CURVE | String |
FAST_PHASE_SHOTS_TO_LO | FAST PHASE SHOTS TO L.O. | Double |
FAST_PHASE_PU | FAST PHASE P.U. | Integer |
SLOW_PHASE_CURVE | SLOW PHASE CURVE | String |
SLOW_PHASE_SHOTS_TO_LO | SLOW PHASE SHOTS TO L.O. | Double |
SLOW_PHASE_PU | SLOW PHASE P.U. | Integer |
FAST_GROUND_CURVE | FAST GROUND CURVE | String |
FAST_GROUND_SHOTS_TO_LO | FAST gROUND SHOTS TO L.O. | Double |
FAST_GROUND_PU | FAST_GROUND_PU | Integer |
SLOW_GROUND_CURVE | SLOW_GROUND_CURVE | String |
SLOW_GROUND_SHOTS_TO_LO | SLOW_GROUND_SHOTS_TO_LO | Double |
SLOW_GROUND_PU | SLOW_GROUND_PU | Integer |
FAST_PHASE_MULT | FAST_PHASE_MULT | Double |
FAST_PHASE_ADDER | FAST_PHASE_ADDER | Double |
SLOW_PHASE_MULT | FAST_PHASE_MULT | Double |
SLOW_PHASE_ADDER | FAST_PHASE_ADDER | Double |
FAST_GROUND_MULT | FAST_GROUND_MULT | Double |
FAST_GROUND_ADDER | FAST_GROUND_ADDER | Double |
SLOW_GROUND_MULT | SLOW_GROUND_MULT | Double |
SLOW_GROUND_ADDER | SLOW_GROUND_ADDER | Double |
Solved! Go to Solution.
Hi Bryan
The Electric Foundations are really just a starting point. There is risk in adding too many attributes to any single class. It could impact performance and other areas of the system if too many attributes are added. With that said, we included the attributes most popular with various analysis packages, like CYME, OpenDSS, Siemans, Schenieder, etc. We tried to limit to fields that are unique to the specific equipment. Things like fuse curves are typically specific to a model and could be obtained from reference tables.
Dear @BryanMay531
I would wait for feedback from Esri Solutions... In the meantime, keep in mind that unless a feature class attribute was assigned some Network Attribute, its presence or absence in your model does not affect at all the OOTB Network Management behavior.
Therefore, if you are having difficulty mapping your fields to those of the Foundation, you should not have any issues bringing YOUR fields into YOUR (Foundations derived) model. Remember that, as Esri Solutions has documented time and time again, Electric Foundations is a reference that you can use to immensely help on an early adoption of the UN. Yet, it is not a written-in-stone schema; rather, it is versatile, extendable and scalable to fit your needs without compromising OOTB functionality.
Additional note: one advantage of bringing some fields form your legacy model as-is is that any integration with external systems that rely on those fields is minimally impacted.
Makes sense. Thanks!!!
Hi Bryan
The Electric Foundations are really just a starting point. There is risk in adding too many attributes to any single class. It could impact performance and other areas of the system if too many attributes are added. With that said, we included the attributes most popular with various analysis packages, like CYME, OpenDSS, Siemans, Schenieder, etc. We tried to limit to fields that are unique to the specific equipment. Things like fuse curves are typically specific to a model and could be obtained from reference tables.
Got it. Thank You!