SCADAInterface Does not Ignore Stale Device Operation Times
(Doc ID 2865778.1)
Last updated on MAY 03, 2022
Oracle Utilities Network Management System - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 2.4 to 2.5] Oracle Network Management for Utilities - DMS - Version 126.96.36.199.0 to 188.8.131.52.0 [Release 2.4 to 2.5] Information in this document applies to any platform.
On : 184.108.40.206.0 version, Web Workspace
ACTUAL BEHAVIOR --------------- SCADAInterface does not appear to honor timeStamp for device operation times
The Multispeak SCADAInterface does not appear to be honoring the timeStamp in a SCADAStatusChangedNotification or GetAllSCADAStatusResponse message.
Customer has seen and then test/verified that if a device is operated at time X and sends that in a SCADAStatusChangedNotification and then for whatever reason the SCADAInterface then receives a new message for that same device at time X-y (ie an older status), the SCADAInterface/NMS is simply applying the new message state regardless of the operation actually being older.
Occasionally during testing, an operator opened a device and then via SoapUI sent in reversing that operation/closed with a timestamp from a month ago and NMS simply applied both state changes.
The system should be ignoring any stale scada messages.
The issue can be reproduced at will with the following steps:
1. Submit device open operation with current timestamp for a status point with TELEMETERED flag set to 'N'. 2. Device is opened in NMS with the provided timestamp. 3. Submit device close operation for the same status point with timestamp earlier than previous open operation (step 1). 4. Device is not operated in NMS and an error 'Ignoring obsolete status update' is returned by the adapter. 5. Submit device close operation for the same status point with current timestamp. 6. Device is closed in NMS with the provided timestamp.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!