What Are The Codes That Appear In The ERT SRC Column In WorkAgenda

(Doc ID 887911.1)

Last updated on DECEMBER 14, 2017

Applies to:

Oracle Utilities Network Management System - Version 1.7.5 and later
Oracle Network Management for Utilities - DMS - Version 1.7.5 and later
Information in this document applies to any platform.

Goal

There are several different codes that appear in the ERT SRC column in Work Agenda.  Where do these come from and how are they determined?

N = None - no ERT assigned,
I = Initial (default) comes from Storm Lite,
C = Crew provided - Manually entered
O = Onsite (crew is on-site reported more accurate ERT projection ).  A crew has gone en route or arrived onsite. This event is now the active event for a crew, and the ERT can be calculated by adding the travel time to the crew's en route time (if crew still en route) + repair time, or just adding the repair time to the crew's onsite time.
S = Storm Management Calculated
D = ERT Delay, not commonly used flavor of ERT override. It is similar to the ERT override (G) but calculated by adding delay value to the outage start time.
G
= Global Published ERT - Override value for all outages in a particular area (from Storm management GUI)
P = (non)Published Global ERT - (ERT will be blank - controlled from Storm Management GUI)
M = Used to indicate that ERT calculated by NMS exceeded maximum allowed value (configured view 'stormmanMaximumERT' rule) and was blanked out.
m = Used to indicate that the ERT calculated by NMS does not meet the minimum allowed value (configured by 'minimumERT' rule) and was blanked out.  But if the subsequent ERT recalculating results in an acceptable value then 'm' would be replaced by the actual source value (S, G, I, etc).

 

 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms