Placing An Inhibit On A Device Prevents It From Being Isolated or Secured
(Doc ID 2568781.1)
Last updated on MARCH 12, 2021
Applies to:Oracle Utilities Network Management System - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 2.3 to 2.4]
Oracle Network Management for Utilities - DMS - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 2.3 to 2.4]
Information in this document applies to any platform.
On : 22.214.171.124.0 version, Web Workspace
Placing an Inhibit on a device is preventing manual operations on the device
As per the 2.3 User Guide, in SCADA summary, Inhibit sets the inhibit quality code for the selected SCADA measurement and this suppresses any new updates from SCADA. However, on testing this on a 2.3 environment, once I inhibit the SCADA device, not only does it stop the SCADA Update coming through from SCADA but it also prevents the NMS user from isolating or securing the inhibited device from the Control Tool.
You should be able to Isolate a INHIBITED device
The issue can be reproduced at will with the following steps:
1. Find an open SCADA switch, or open a closed SCADA switch
2. Inhibit the Topology Status point for the switch.
3. In the Control Tool, Isolate the switch
This will fail.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document