SCADA Operation Time Overwrites Merged Event Start Time
(Doc ID 2851395.1)
Last updated on FEBRUARY 23, 2022
Applies to:
Oracle Utilities Network Management System - Version 2.3.0.2.0 to 2.5.0.1.0 [Release 2.3 to 2.5] Oracle Network Management for Utilities - DMS - Version 2.3.0.1.0 to 2.5.0.0.0 [Release 2.3 to 2.5] Information in this document applies to any platform.
Symptoms
On : 2.3.0.2.0 version, Adapters
ACTUAL BEHAVIOR --------------- Scada operation time overwrites merged event start time
A customer has a 3rd-party client that sends device operations via multi-speak adapter to operate devices in NMS. To accommodate for that, each device in the NMS data model was changed to be a scada_point. The problem with that is, the SCADA time (time the device is opened by SCADA) overwrites the earliest call time.
EXPECTED BEHAVIOR ----------------------- There needs to be an option for scada operations to not impact the event start time.
STEPS ----------------------- 1. Call comes in at 13:00 and creates a PSO (Event 123). Event start time is 13:00 2. SCADA adapter sends an open message on an upstream Fuse at 13:05 3. Event 123 moves to the Fuse. Start time changed to 13:05
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!
