FLISR Status Disappears From Workspace Status Bar When SCADA Enables the Global FLISR Point
(Doc ID 2866424.1)
Last updated on MAY 02, 2022
Applies to:
Oracle Network Management for Utilities - DMS - Version 2.5.0.1.0 to 2.5.0.2.0 [Release 2.5] Information in this document applies to any platform.
Symptoms
On : 2.5.0.1.0 version,
FLISR status disappears from Workspace status bar when SCADA enables the global FLISR point
Customer has a SCADA point configured to globally disable FLISR (Load Shed).
When the SCADA point is 1, FLISR is enabled - when 0, FLISR is to be disabled.
Based on the write-up for this rule, it would seem we need to invert processing - but that doesn't work - we need to have rule_value_integer_1 set to 0.
We had them start with FLISR in Manual mode. When they set the SCADA point to 0, we saw the Workspace status bar update to read: FLISR: Disabled (Load Shed) Then, when they set the SCADA point to 1, sometimes the workspace updates correctly and sometimes the FLISR status disappears.
When FLISR is globally disabled, the JBOT_REPORT showed: ,DS_MENU_BAR_DEFAULT ,,#global:filter_name,,java.lang.String,None ,,ANMS_MODE,,java.lang.String,0 ,,DMS_STUDY_MODE_PERMISSION,,java.lang.Boolean,false ,,FLISR_MODE,,java.lang.String,3 ,,FLM_STATUS,,java.lang.String,1 ,,GLOBAL_FLISR_MODE_ENABLED,,java.lang.String,0 ,,PROTECTION_SCHEMES_MODE,,java.lang.String,2 ,,SHOW_SW_PF_COLUMNS,,java.lang.String,N ,,VVO_MODE,,java.lang.String,1
Then, when they enable FLISR and the status disappears, the JBOT_REPORT showed: ,DS_MENU_BAR_DEFAULT ,,#global:filter_name,,java.lang.String,None ,,ANMS_MODE,,java.lang.String,0 ,,DMS_STUDY_MODE_PERMISSION,,java.lang.Boolean,false ,,FLISR_MODE,,java.lang.String,3 ,,FLM_STATUS,,java.lang.String,1 ,,GLOBAL_FLISR_MODE_ENABLED,,java.lang.String,1 ,,PROTECTION_SCHEMES_MODE,,java.lang.String,2 ,,SHOW_SW_PF_COLUMNS,,java.lang.String,N ,,VVO_MODE,,java.lang.String,1
The GLOBAL_FLISR_MODE_ENABLED flag changed from 0 to 1, but the FLISR_MODE value stayed at 3 (there is no label defined for this combination).
There were no PFService log entries to indicate that FLISR was in Manual mode.
FLISR status should not change unexpectedly.
The issue can be reproduced at will with the following steps:
Set the FLISR mode to automatic
Set the global status point to disabled
Set the global status point to disabled with invalid quality
Change the FLISR mode to manual
Set the global status point to enabled with good quality
Observe that the FLISR status can disappear from the GUI
Changes
Cause
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!