Powerflow Uses Incorrect Conductor Length if the Conductors Do Not Exist in a Geographic Map
(Doc ID 2519822.1)
Last updated on DECEMBER 03, 2019
Applies to:Oracle Utilities Network Management System - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 2.3 to 2.4]
Oracle Network Management for Utilities - DMS - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 2.3 to 2.4]
Information in this document applies to any platform.
The length of conductors is for powerflow solutions is critical to determining the correct impedances. However, PFService uses the length based on internal world coordinates which would not be as accurate if the GIS holds the actual lengths as an attribute.
There appears to be no way for projects to override the way in which the network_components.length as this appears to be set from the coordinates of the primary partition by MBService when writing the patch, ignoring whether the primary partition is geographic or not. In general, internal world coordinates cannot be used as representative of actual conductor lengths as they are schematic - if the GIS held the actual lengths as attributes, there is no way to set this via the model build
PFService should be able to actual length attributes, if available, for calculating conductor lengths
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document