SOM - Create FA IMD Completion Event Creating IMD’s Shifted An Additional Hour During DST
(Doc ID 2540393.1)
Last updated on AUGUST 02, 2019
Applies to:Oracle Utilities Customer to Meter Base - Version 184.108.40.206.0 and later
Oracle Utilities Meter Data Management - Version 220.127.116.11.0 and later
Oracle Utilities Service and Measurement Data Foundation - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
Create FA IMD Completion Event is shifting reads taken in from an Inbound Communication from MWM, which causes issues if a VEE Rule is in place that looks for usage against a uninstalled or disconnected device. When a read is taken before removal, the system thinks that read is one hour in the future, where is considers it uninstalled. This pushes the IMD into the Exception status.
In slightly more detail:
IMD created as a result of Inbound Communication (Field Activity) from MWM has measurement date time shifted an extra hour during DST. For example, an Inbound Communication that shows 17:55 for the reading time. We know this is already in daylight time because it matches what is in MWM and MWM is labeled as daylight time in customer screens. It gets sent in the I/B Communication as time "2018-03-20T16:55:00-5:00". Note the -05:00 in the timestamp indicating standard time (16:55 EST = 17:55 EDT), that is, it cannot be disputed that the intended time is 16:55 EST (standard time) / 17:55 (wall-time). The IMD that is created as a result of the inbound communication is shifted an extra hour during DST and has a end date of 17:55 EST.
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