Loss of Voltage (LoV) Should Recheck the Device Status After Voltage Loss Delay During Processing (Doc ID 3063225.1)

Last updated on DECEMBER 19, 2024

Applies to:

Symptoms

On : 2.5.0.2.0 version, PFService

ACTUAL BEHAVIOR
---------------
Fault Location/Isolation/Service Restoration (FLISR) - Loss of Voltage (LoV) should recheck the device status after the voltage loss delay during processing


FLISR LoV processing begins once the NMS detects voltage measurements below the threshold value. Then it checks for any known upstream device outages or momentary outages. If no such outages are detected, it waits for the voltage loss threshold delay and then rechecks for voltage loss. If voltage loss persists, it proceeds with the solution. However, it seems the device status and its quality are not being verified after the voltage loss threshold delay which is causing FLISR LoV to trigger incorrectly in some scenarios.

For example, there are FLISR LoV events that get generated due to device switching communication delay:

1. Device open command sent from SCADA
2. It opens in the field (downstream devices detect loss of voltage),
3. But open command completion status gets delayed due to possibly some communications delay
4. Result is FLISR event triggers.

EXPECTED BEHAVIOR
The FLISR LoV should verify the device status and its quality after resuming processing, following the voltage loss threshold delay. The solution should be aborted if

• the device is open or
• if the device status quality is suspect.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.