"FLISR Demand Scan" Does Not Take in to Account For Missing or Delayed SCADA Measurements

(Doc ID 2347327.1)

Last updated on JANUARY 16, 2018

Applies to:

Oracle Utilities Network Management System - Version 1.12.0.3 to 2.3.0.1.0 [Release 1.12 to 2.3]
Oracle Network Management for Utilities - DMS - Version 1.12.0.3 to 2.3.0.1.0 [Release 1.12 to 2.3]
Information in this document applies to any platform.

Symptoms

A system had a couple of FLISR events in production where FLISR came up with wrong plan and tried to close into a fault.

Further investigation of this issue indicated that FLISR plan was incorrect due to the unavailability of some downstream fault indications during FLISR Demand Scan.
Those Fault indications came in after 2 minutes and FLISR did not consider them in its processing.

FLISR should consider indication from RTUs when they complete a success poll cycle.  This particular system had SCADA points to indicate if an RTU has successfully completed its poll cycle.

FLISR must consider missing or delayed scada measurements when determining the plan.


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms