Last updated on OCTOBER 25, 2016
Applies to:Oracle Utilities Meter Data Management - Version 18.104.22.168 and later
Information in this document applies to any platform.
Outage activities created in Meter Data Management (MDM) 2.1 SP 1 through the user interface are displaying the wrong start/end date time in SP3.
Outage activities created in MDM 2.1 SP 3 from device events have their start and end date/times set without adjusting for DST (as activity date/times are stored adjusted for DST).
Please note: since these outage activities are used as an input into the periodic estimation process to identify which intervals should be set with an outage condition code and the interval VEE estimation rules use the outage condition to temper estimations this data error may have impacted estimations made. As such some analysis may be required to identify if there are were any impacts to estimations made during outage periods. In general there should only be an impact to the last hour of the outage and those estimated intervals that fall within that hour. This issue will only have existed during the DST period subsequent to applying MDM 2.1 SP3.
For these Outage Activities that were created subsequent to MDM 2.1 SP3 via device event processing during a DST period will have start and end date/times that are 1 hour behind what they would have been prior to MDM 2.1 SP3. As part of this solution the code for a batch control has been provided that will cycle through all Outage Activity with Duration activities and detect those whose date/time has been set incorrectly and correct them. This will only impact those activities that meet the following criteria:
- They have date/times that fall within the DST period
- They have an initiating device event and or terminating device event
- The start date/time (for initiating device events) or end date/time (for terminating device events) are not equal to the associated device events event date/time when adjusted for DST.
- For example, if a power down device event had an event date/time that was stored in standard as 4/15/2016 12:00PM (-08:00UTC) and the associated Outage Activity with Duration start date/time was also stored as 4/15/2016 12:00PM (-08:00UTC) then this process would adjust the start date/time for DST making the start date/time 4/14/2016 1:00PM (-07:00UTC)
Steps To Recreate
- Create Device, Device Configuration, Measuring Component, Service Point and Install event.
- Initiate the outage activity for device in DST and verify start date/time in activity page
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms