Changes In SCADA Values/quality Are Not Written To Database Reserve_value/quality When Inhibit Set
(Doc ID 2707747.1)
Last updated on SEPTEMBER 03, 2020
Oracle Network Management for Utilities - DMS - Version 22.214.171.124.0 to 126.96.36.199.0 [Release 2.4] Information in this document applies to any platform.
On : 188.8.131.52.0 version,
ACTUAL BEHAVIOR --------------- Changes in SCADA values/quality are not written to database reserve_value/quality when inhibit set
When SCADA points are first introduced into the project configuration they are set to have an 'unmapped' SCADA quality (262144) and also have an NMS inhibit (16) placed on them (until a point checkout has been performed at which time the user will remove the inhibit).
When a SCADA point is mapped and the value is sent to NMS, it is supposed to update the SCADA quality which will get rid of the 'unmapped' quality.
E.g. if an analog measurement has a value of 0 and a quality of 262160 (262144 + 16) and a value of 100 is sent from SCADA with no quality - We would expect the reserve value and quality to be updated in the analog_measurements table - The reserve_quality and reserve_value do not update while the NMS inhibit is in place.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!