Auto Throw-Over Switch Configuration (ATO)
Oracle Utilities Network Management System supports the modeling and visualization of Auto Throw-Over (ATO) devices. Critical customers such as hospitals, manufacturing, financial and emergency services, require higher level of power quality and reliability. These customers are normally provided with a primary and backup source of power to improve the reliability. Utilities deploy automatic throw over devices to switch the load to backup source when the primary source is not available. Often these devices have automatic restoration feature where the load is fed by the primary source when primary source is energized after an outage.
Model Requirements for ATOs
In order to configure ATOs in the Oracle Utilities Network Management System, the Model Build process needs to know what two devices are controlled by the ATO controller. One device must be identified as the primary or preferred feed, which would be normally closed, and the other device would be the secondary or alternate feed, which would be normally open. These relationships and control behaviors are modeled in the ATO_CONTROLLERS table, as shown below:
Summary Object Configuration
Summary Objects are objects in one world (for example, Geographic World) that reflect events or conditions in another world (for example, Substation World). For example, a substation fence in the geographic world may display the conditions existing on objects within the substation in the internal world view of the substation (like an outage on a breaker in the substation would be reflected on the fence in the geographic world).
To configure this functionality, you need to configure three areas of the model:
1. Verify that summaryobjects is on the DDService in the $NMS_HOME/etc/system.dat file.
2. Verify that nms_srs_rules.sql has a config rule for summaryObject set to "yes".
3. Verify that all object classes you wish to have summary events reflected on are in the project condition rules file (for example, substation_fences).
4. Substation fences, when build, must define a location in the .mb file. For example:
ADD substation_fence 2 {
LOCATION = <10210.2>;
ALIAS[OPS] = "SUB_Lake";
DIAGRAM[1022] (1022) = {
SYMBOLOGY = 101;
HEIGHT = 500.000000;
GEOMETRY = {
(2270311.397232,460321.122269),
(2270311.397232,459286.466476),
(2271217.293103,459286.466476),
(2271217.293103,460321.122269),
(2270311.397232,460321.122269)
};
};
ATTRIBUTE[Latitude]=" 40.92498";
ATTRIBUTE[Longitude]=" -81.40776";
};
ADD LOCATION <10210.2> {
NAME = "SUB_Lake";
DESC = "Lake Substation";
REFERENCE = (2270311.397232,460321.122269);
};
5. All objects in the substation partition that you want the events and conditions reflected on the substation fence must belong to the same location. For example:
ADD rack_circuit_br 1500 {
PHYSICAL_PROPERTY = SUB;
VOLTAGE = 13800;
NCG = 63;
PHASES = 7;
LOCATION = <10210.2>;
PORT_A = <444.2523.2>;
PORT_B = <444.2522.2>;
ALIAS[GIS] = "Circuit Breaker.270";
ALIAS[OPS] = "BR241XFM";
DIAGRAM[1094] (1094) = {
RANK = 65544;
SYMBOLOGY = 10507;
HEIGHT = 500.000000;
GEOMETRY = {
(205.811207,412.902928),
(205.811207,391.655951)
};
};
ATTRIBUTE[gmd_location] = "Lake Substation";
ATTRIBUTE[gmd_comment] = "0.0000";
To use LatLong to convert coordinates from parameters instead on files, use the -script option. Here are examples:
Convert x,y coordinate to lat,long:
$ LatLong OH83-NF LL -script 2270808.750654 461097.566511
-81.40592405 40.92709161
Convert long,lat to x,y:
$ LatLong LL OH83-NF -script -81.40592405 40.92709161
2270808.75152434 461097.56670991
Adding Latitude and Longitude Attributes to Objects in the Model Build Process
The NMS LatLong tool will populate latitude and longitude attributes to objects in a given model import (.mb) file.
The format of the command to add Latitude and Longitude attributes to objects is:
LatLong {src_proj} {dest_proj} {infile} {outfile} [{precision}]
Where:
src_proj = projection name * (for example, CO-N CO-S GA83-GeorgiaPwr CT MN-S UTM-15N)
dest_proj = projection name * (for example, LL)
infile = input file name for the .mb file
outfile = output file name for the .mb file
precision = optional number of digits to the right of the decimal (def = 8)
Notes:
• See the $OMS_PREFIX/data/MAPPING/coordsys.asc file for supported projections.
• Objects with __GEO_REF_X and __GEO_REF_Y attributes will be used for the coordinates to transform to the dest_proj instead of the GEOMETRY COORDs on the object.
To just convert a single coordinate, use the -script option:
LatLong {src_proj} {dest_proj} -script {x or longitude} {y or latitude} [{precision}]
To update the coordinate on objects, use the -updateObjectCoordinates option:
LatLong {src_proj} {dest_proj} -updateObjectCoords {infile} {outfile} [{precision}]
The call to this program is typically added to the [project]‑build‑map script:
_echo "Preprocessor complete, doing latlong..." ${logdir}/${mapPrefix}.log
LatLong \
OH83-NF LL \
${OPERATIONS_MODELS}/patches/${mapPrefix}.mb \
${OPERATIONS_MODELS}/patches/${mapPrefix}.mbll \
>> ${logdir}/${mapPrefix}.log 2>&1
if [[ ! -f ${OPERATIONS_MODELS}/patches/${mapPrefix}.mbll ]]
then
_echo "WARNING:Unable to add lat/long to MP to ${mapPrefix}.mb"\
${logdir}/${mapPrefix}.log
else
mv ${OPERATIONS_MODELS}/patches/${mapPrefix}.mbll \
${OPERATIONS_MODELS}/patches/${mapPrefix}.mb
_echo "Finished converting MP file $mapPrefix to ${mapPrefix}.mb"\
${logdir}/${mapPrefix}.log
fi