Confirm Outages Breaks a PSO Trouble Call from a Damage Assessment Associated with the PSO Into a New Job

(Doc ID 1967292.1)

Last updated on DECEMBER 05, 2017

Applies to:

Oracle Network Management for Utilities - DMS - Version 1.11.0 to 1.12.0.1 [Release 1.11 to 1.12]
Oracle Utilities Network Management System - Version 1.11.0 to 1.12.0.1 [Release 1.11 to 1.12]
Information in this document applies to any platform.

Symptoms

Confirm Outages breaks a PSO trouble call from a Damage Assessment associated with the PSO into a new job.

If a PSO has a Damage Assessment and the Confirm Service Outage function is used to confirm the call associated with the PSO, the PSO is broken out into a new PSO job separate from the Damage Assessment.

It is not desired functionality to have the Confirm Service outage create a new event in these scenarios and have the DA left with the original event.

STEPS
-----------------------
A PSO is Acknowledged and an order is sent to mobile
At some point, a field report including damage info (not affecting load) is sent from mobile
The job now has two calls and still one out
The NMS operator now confirms the service outage
The original trouble call is broken out into a new ACK event and a new mobile order is created
The Damage Assessment (DA) stays with the original job

If the DA is sent with load affected it is essentially the same except you have a job with 2 calls and 2 out reported in Work Agenda before the confirm takes place.

Changes

 

Cause

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