TE 002222 MOP 002 OMS Operation Manual

Schneider Electric DMS NS
OMS (Outage Management System)
Operation Manual
Last update: September, 2014

Table of Contents
1. REVISION HISTORY ................................................................................................
................................ ..................................... 1
2. DEFINITIONS AND ABBREVIATIONS
ABBR ................................................................
........................................ 2
3. OUTAGE MANAGEMENT ................................................................

............................................................. 4
3.1. Incident Browser ................................................................................................
.................................. 5
3.1.1. Incident Management ................................................................

............................................... 9
3.1.1.1. Incident
Incid ................................................................
.................................................... 16
3.1.1.2. Devices ................................................................
.................................................... 18
3.1.1.3. Crews ................................................................
....................................................... 20
3.1.1.4. Calls ................................................................
......................................................... 23
3.1.1.5. Problems ................................................................
.................................................. 23
3.1.1.6. Switching Operations ..............................................................
................................ 25
3.1.1.7. Incident
In Location ................................................................
..................................... 27
3.1.1.8. Nested/Coupled Incidents .......................................................
................................ 28
3.1.1.9. Customers................................................................
................................................ 29
3.1.1.10. Resolution ................................................................
................................................ 30
3.1.1.11. Service Transformers ..............................................................
................................ 31
3.2. Incident Historical Browser ................................................................
.............................................. 31
3.2.1. Incident Historical Management .............................................................

................................ 33
3.3. Incident Overview ................................................................
.............................................................. 34
3.4. Incident Coloring

oring ................................................................
............................................................... 36
3.5. Problem Browser ................................................................
............................................................... 37
3.6. Problem Overview ................................................................

.............................................................. 38
3.7. Call Browser ................................................................................................
................................ ....................................... 39
3.7.1. Trouble Event Management ................................................................

................................... 42
3.8. Callback Browser ................................................................
............................................................... 44
3.8.1. Callback Management ................................................................

............................................ 46
3.9. Smart Meter Event Browser................................................................
Browser .............................................. 48
3.10. Smart Meter Request Browser ................................................................

......................................... 51
3.11. Crew Browser ................................................................................................
................................ ..................................... 52
I Operation Manual
3.11.1. Crew Properties ................................................................

...................................................... 54
3.11.2. Crew Management ................................................................
................................................. 57
3.12. Crew Member Browser ................................................................
...................................................... 61
3.13. Crew Vehicle Browser ................................................................

....................................................... 63
3.14. Customer
tomer Browser ................................................................
............................................................. 65
3.14.1. Customer List ................................................................

.......................................................... 68
3.15. Customer Historical Browser ................................................................
........................................... 71
3.15.1. Customer Historical Management ..........................................................

................................ 72
3.16. Incident Global Options ................................................................
.................................................... 74
3.17. Smart Meter Global Options ................................................................

............................................. 76
3.18. OMS Profile Library ................................................................
........................................................... 78
3.18.1. Prediction Profiles ................................................................

................................................... 79
3.18.2. Callback Profiles ................................................................
..................................................... 87
3.18.3. Profile Schedules ................................................................
.................................................... 89
3.19. OMS Profile Assignments Editor ................................................................
..................................... 90
II Operation Manual
Table of Figures
Figure 3.1 Incident Browser window ................................................................
............................................... 5
Figure 3.2 Incident Mergedialog
Merge ................................................................
...................................................... 6
Figure 3.3 Incident Browser window Cancel, Field Complete and Damage
Assessed buttons available ................................................................
................................................................. 7
Figure 3.4 Incident Validation Result message .............................................................
................................ 7
Figure 3.5 Incident Status Change
Ch dialog ................................................................
...................................... 8
Figure 3.6 Status change reason dialog ................................................................
......................................... 8
Figure 3.7 Filtering incidents................................................................
.............................................................. 9
Figure 3.8 IncidentManagement window ................................................................
...................................... 10
Figure 3.9 Incident Event Log window ................................................................
.......................................... 11
Figure 3.10 Event
vent Details dialog ................................................................
.................................................... 11
Figure 3.11 Incident symbol in network view ................................................................
.................................. 12
Figure 3.12 Incident Properties dialog ................................................................
.......................................... 13
Figure 3.13 Incident Management window Incident detail ........................................
................................ 14
Figure 3.14 Incident Management window Incident assigned ..................................
................................ 15
Figure 3.15 Switch Options dialog ................................................................
................................................ 19
Figure 3.16 Devices area ................................................................................................
................................ 20
Figure 3.17 Crews area ................................................................................................
................................ ................................... 20
Figure 3.18 Crew Assignmentdialog
Assignment ................................................................
............................................. 22
Figure 3.19 Crew assignment symbol in network view...................................................
................................ 22
Figure 3.20 Calls area ................................................................................................
................................ ..................................... 23
Figure 3.21 Problems area ................................................................
............................................................. 24
Figure 3.22 Problem representation
resentation in network view .....................................................
................................ 24
Figure 3.23 Problem Properties dialog ................................................................
......................................... 25
Figure 3.24 Switching operations area ................................................................
........................................ 25
Figure 3.25 Free Text Instruction Window ................................................................
.................................. 26
Figure 3.26 Changesets Summary dialog ................................................................
....................................... 27
Figure 3.27 Incident location area ................................................................
................................................ 28
Figure 3.28 Nested/Coupled
ted/Coupled incidentsarea
incidents ................................................................
................................. 29
Figure 3.29 Customersarea
area................................................................
............................................................ 29
Figure 3.30 Feedback reasondialog
reason ................................................................
.............................................. 30
Figure 3.31 Resolution area ................................................................
........................................................... 31
Figure 3.32 Service transformersarea
transformers ................................................................
.......................................... 31
Figure 3.33 Incident Historical Browser window .........................................................
................................ 32
Figure 3.34 Incident Historical Summary Report .......................................................
................................ 33
III Operation Manual

Figure 3.35 Incident Historical Browser Filter area ....................................................

................................ 33
Figure 3.36 Incident Historical Management window .................................................
................................ 34
Figure 3.37 Incident Overview window ................................................................
......................................... 35
Figure 3.38 Examples of charts with numeric values presented ....................................
................................ 36
Figure 3.39 Coloring by incident status ................................................................
........................................... 37
Figure 3.40 Problem Browserwindow
Browser ................................................................
........................................... 37
Figure 3.41 ProblemManagementwindow................................................................
ProblemManagement ..................................... 38
Figure 3.42 ProblemOverviewwindow
ProblemOverview ................................................................
........................................... 39
Figure 3.43 Call Browser window ................................................................
.................................................. 39
Figure 3.44 Trouble
Trouble Event Management window for creating new location based call
................................................................
................................................................................................
............................................. 41
Figure 3.45 Located device as a result of Locate Call action ....................................................................... 42
Figure 3.46 Call browser filter area................................................................
............................................... 42
Figure 3.47 Trouble Event Management window.........................................................
................................ 43
Figure 3.48 Callback Browser window ................................................................
.......................................... 45
Figure 3.49 Callback browser filter area ................................................................
...................................... 46
Figure 3.50 Callback Management window ................................................................
.................................. 47
Figure 3.51 Smart Meter Event Browserwindow
Browser ................................
.......................................................... 49
Figure 3.52 Trouble Event Managementwindow
Management AMI event .....................................
................................ 50
Figure 7.53 AMI
AMI event in network view ................................................................
............................................ 50
Figure 3.54 Smart
art Meter Event List dialog ................................................................
.................................... 51
Figure 3.55 Smart Meter Request Browserwindow
Browser ................................
..................................................... 51
Figure 3.56 Crew Browser window ................................................................
................................................ 52
Figure 3.57 Edit Types dialog ................................................................
......................................................... 54
Figure 3.58 Filter area ................................................................................................
................................ ...................................... 54
Figure 3.59 Crew Properties dialog ................................................................
................................................ 56
Figure 3.60 Crew Properties dialog Members area ..................................................
................................ 57
Figure 3.61 Crew Properties dialog Vehicles area ...................................................
................................ 57
Figure 3.62 Crew Properties dialog Skills area .........................................................
................................ 57
Figure 3.63 Crew details in the Crew Management window .........................................
................................ 58
Figure 3.64 Crew member details in the Crew Management window .......................... 60
Figure 3.65 Crew vehicle details in the Crew Management window ............................ 60
Figure 3.66 Crew Member Browser window ................................................................
................................. 61
Figure 3.67 Crew Management window Creating crew member............................... 62
Figure 3.68 All Skills dialog ................................................................
............................................................ 63
Figure 3.69 Edit Skill dialog ................................................................
............................................................ 63
Figure 3.70 Crew Vehicle Browser window ................................................................
.................................. 64
IV Operation Manual
Figure 3.71 Crew Management window creating crew vehicle................................

.................................. 65
Figure 3.72 Customer Browser window ................................................................
........................................ 66
Figure 3.73 Trouble Event Management window.........................................................
................................ 68
Figure 3.74 Customer listdialog
list ................................................................
..................................................... 70
Figure 3.75 Customer Historical Browser window ......................................................
................................ 71
Figure 3.76 Customer historical browser filter area...................................................
................................ 72
Figure 3.77 Customer Historical Managementwindow
Management ................................
............................................... 73
Figure 3.78 Incident Global Options dialog ................................................................
.................................. 74
Figure 3.79 Smart Meter Global Options dialog ..........................................................
................................ 77
Figure 3.80 OMS Profile Library window ................................................................
...................................... 78
Figure 3.81 Prediction Profile Editor dialog ................................................................
................................. 80
Figure 3.82 Prediction Profile Editor dialog Editing an existing profile .................... 84
Figure 3.83 Priority Profile Editor dialog ................................................................
...................................... 85
Figure 3.84 NewPriority dialog ................................................................
....................................................... 86
Figure 3.85 Priority
y Editor dialog ................................................................
................................................... 87
Figure 3.86 Callback Profile Editor dialog ................................................................
.................................... 88
Figure 3.87 Profile Schedule Editor dialog ................................................................
................................... 90
Figure 3.88 OMS Profile Assignments Editor window ................................................
................................ 90
Figure 3.89 Set feeder profilesdialog
profiles ................................................................
............................................ 91
V Operation Manual
1. REVISION HISTORY
Version Authors Date Comments

Maja Novkovi,
Novkovi Milica
0.1 15-May-2014 Initial version created
oki
1 Operation Manual
2. DEFINITIONS AND ABBREVIATIONS
Definition/Abbreviation Description
AD LDS Active Directory Lightweight Directory Service
AMI Advanced Metering Infrastructure
ANSI A
American National Standards Institute
AOR Area of Responsibility
ATR Actual Time of Restoration
AVR Automatic Voltage Regulators
CAIDI Customer Average Interruption Duration Index
CAIFI Customer Average Interruption Frequency Index
DGM Distributed Generator Monitoring
Dynamic Mimic Diagram graphical user interface for DMS
System. It is responsible for all interactions with the user, e.g.
displaying the current device state, control actions, presenting
DMD
alarms and handling alarm acknowledgement, trending.
t DMD
interacts with DMS Services to generate current views of the
network and to send commands.
DMS Distribution Management System
DSDR Distribution System Demand Response
DOM Device Operations Monitoring
ECC Energy Control Center
ENSI Energy Not Supplied Index
ETR Estimated Time of Restoration
FC Fault Calculation
FL Fault Location
FLL Fault Localization
GIS Geographic Information System
HV High Voltage
ICCP InterControl Center Communications
2 Operation Manual
LF Load Flow
LTC Load Tap Changer
LV Low Voltage
MAIFI Momentary Average Interruption Frequency Index
M&C Monitoring & Control
MTR Maximum Time of Restoraion
MV Middle Voltage
NO Normally Open
NR Network Reconfiguration
OCP Optimal Capacitor Placement
ODBC Open Database Connectivity
OMS Outage Management System
OMS RA Outage Management System Reliability Analysis
PDF Portable Document Format
PI Performance Indices
RTDB Real Time Data Base
RTU Remote Terminal Unit
SAIFI System Average Interruption Frequency Index
SAIDI System Average
ge Interruption Duration Index
SCADA Supervisory Control and Data Acquisition
SDP Service Delivery Point
SE State Estimation
SQL Structured Query Language
SR Supply Restoration
STLF Short Term Load Forecast
TA Topology Analyzer
EVR Emergency Voltage Reduction
VVO Volt VAr Optimization
3 Operation Manual
3. OUTAGE MANAGEMENT
The main components of the Outage Management System (OMS) functionality within
DMS are as follows:
Incident Management The key component of the OMS responsible for assisting
system operators in efficient
ef dispatching of outages, non-outage
outage problems and all
other planned works. Incident Management is responsible for tracking the
information about power disturbances in network and organizing the response to
the disturbance into a user-friendly,
user efficient
ent and safe workflow. The disturbances
themselves, together with the information necessary to complete the business
processes around them, are grouped into objects named incidents.
incident The incident
models all problems in distribution system such as unplanned outage, problem
existence, non-outage
outage problems like lights flickering, planned outage and planned
work.Incident
Incident Management is tightly integrated with DMS outage processing
proce and
work order management.
Call Management Responsible
R for recording trouble calls and events received
from AMI (Advanced Metering Infrastructure) meters, Power Up and Power Down
events.. It keeps the real-time
real time image of the currently active calls,
c AMI events, and
callbacks. This component of OMS manages the configuration of valid values for
call and callback
back types, reasons and results. The Call Management component
keeps and processes a large number of trouble calls in order to support high activity
scenarios, without affecting the system performances
performances of the DMS environment.
Customer Data Management Customer data is the main set of input data to any
OMS, sinceit presents
present the main information for connection to trouble call and
identification off affected part of network. In DMS-OMSOMS environment customer data
is stored in the Customer database.
databa This data is initially migrated from CIS and after
initial migration only incrementally updated via appropriate interface. Customer
database contains private customer data (non-electrical)
electrical) from CIS.
CIS Electrical data of
the network is stored in unique network
ne model instance of the system. In order to
visualize customers information and customers trouble calls, every customer in
customer database has a SDP (Service Delivery Point) identification which presents
connection between non-electrical
non customer data
ata and electrical data of the network.
Service delivery point presents the object of the network model.
model
Crew Management This component performs all actions related to crews required
by OMS user.. Crew Management stores information necessary to track crews,
crew
contact them and assign them to work. Crew Management is responsible for
4 Operation Manual
tracking the information about crew locations, crew availability, crew members,
crew vehicles, and efficient assistance to the user for optimal assignment of crews
to planned or unplanned
planned work in the network.
network
3.1. Incident Browser
The Incident Browser window (Figure

( 3.1) contains a list of all active incidentsin
incidents the
system. It can be reached by selecting OperationsIncident Browser from the main
menu. Once the incident has been created, it can be viewed in the Incident
Browserwindow.This
This window is automatically refreshed in real-time,
real time, as soon as there is
a change of information detected for any of the incidents.
Figure 3.1 Incident Browser window
The following buttons are available in the Incident Browser toolbar:
New Incident ( ) Opens the Incident Management window with blank Incident
Detail form (Figure 3..8). When the incident is created
ted in this way, the userneeds to
draga device (a line segment, transformer or a switching device)to the Devices
area of the Incident Management window (Figure 3.16),
Open Incident ( ) Opens the detailed view of the incident within

wit the Incident
Management window (Figure 3.13),
Delete ( ) Removes the incident,
Locate Affected Network ( ) Locates part of the networkaffected by the

incident in network view,
Print ( ) Initiates printing of the incident data,
Export to Csv File ( ) Exports data to csv file,
Add New Switching Plan ( ) Opens the Switching Plan window for creating a
new switching plan,
5 Operation Manual
Mark as Unread( ) Marks the incident as unread (bolds

olds the incident browser
data),
Clearr Update Notification ( ) Clears
Clears update notifications related to incidents,
Incidents to be merged ( ) Opens the Incident Merge dialog (Figure 3.2),
where incidents
ncidents can be manually merged. Incidents selected to be merged and
incident
ident (or a device) to which the merge is to be performed are placed within this
dialog. Selecting appropriate incidents in the Incident Browser window and
clicking the Incidents to be merged button ( ) opens the Incident Merge dialog
containing selected incidents
i in the Incidents to be merged area. In addition,
incidents to be merged can be selected by dragging incident symbols from network
view to the Incidents to be merged area.
Figure 3.2 Incident Mergedialog
Merge to ( ) This button is enabled when the Incident Merge dialog is

opened. Upon selecting the incident to which the merge should be perfomed in the
Incident Browser window and clicking the Merge to button ( ), the selected
incident appears within the Merge to area of the Incident Merge dialog. In addition,
the incident to which the merge is to be performed
perfo med can be selected by dragging a
6 Operation Manual
device or an incident symbol (only one item) from network view to the Marge to
area,
Takeover ( ) Assigns the incident to the current

urrent user.
user After assigning
incident to the user by clicking this button, the button changes to Release (
).
The incident status can be changed by using the buttons which become active for the
selected incident in the Incident Browser toolbar upon assigning
ng the incident to the user
(by clicking the Takeover button). These buttons are in accordance with the incident
lifecycle. When there is a new, assigned incident in the browser it can be dispatched by
clicking the Dispatch button. If an incident is dispatched,
dispatched, it can be completed (when the
work on the incident is finished)
finished by clicking the Field Complete button (Figure
( 3.3). If the
damage caused by a particular outage has been evaluated, the Damage Assessed
button should be clicked.. Upon clicking, the button disappears.
Figure 3.3 Incident Browser window Cancel, Field Complete and Damage Assessed buttons
available
When the Cancel or Field Complete button is clicked, the validation is performed. If the
validation has failed, appropriate message appears (Figure
( 3.4).
Figure 3.4 Incident Validation Result message
7 Operation Manual
When the Field Complete button is clicked, the Incident Status Change dialog appears
(Figure 3.5).
). In this dialog, it is possible to perform additional actions for the selected
incident.
Figure 3.5 Incident Status Change dialog
When the Cancel button (used when no work on the incident is to be performed)
performed is
clicked, the Status change reason dialog appears (Figure 3.66) where reason for
changing status of the incident can be selected.
Figure 3.6 Status change reason dialog
8 Operation Manual
When the incident status is changed, the Close button appears within the Incident
Browser window. Upon clicking this button, the Archive button appears in the browser.
After clicking one of these buttons, the incident is no longer in the active incident
inciden store.
The Incident Browserwindowwindow supports advanced filtering. In the Incident browser
filter area it is possible to filter incidents by different criteria (Figure
(Figure 3.7).The Incident
Browserwindow
window also supports sorting based on the he selected column, e.g. it can be
filtered based on region and incident status, and sorted by priority and creation time.
Figure 3.7 Filtering incidents
The list of incidents in the browser is automatically refreshed. The list can also be sorted
by any of incident properties.Filter is applied as user type keys in the search field. Filter
can be saved by clicking the Save filter button ( ) and removed by clicking Delete
filter ( ). An existing filter can be loaded by clicking

clicki the Load filter button ( ).
It is possible to reorder columns in the Incident Browser window,, to sort them, as well
as to change their visibility.
ibility. Upon right clicking on the column headers,
headers column visibility
can be set.
3.1.1. Incident Management
TheIncident Management
anagement window (Figure 3.8) can be reached by clicking the New
Incident button ( )or the Open Incident button ( )in the Incident Browser window.
The Incident Management window can also be opened by double-clicking
double on the row
with
h the selected incident in the Incident Browser window. In addition, an incident can
be created by selecting the Create Incident option from the context menu which appears
9 Operation Manual
upon right-clicking
clicking on an element in the network. Selecting the Create Incident option
opens the blank Incident Management window (Figure 3.8).
Figure 3.8 IncidentManagement window
The following buttons are available in the Incident Management window:
New Incident ( ) Opens a new incident,
Save Incident ( ) Saves the incident data. Incident data can also be saved by
using the keyboard shortcut <Ctrl+S>,
<Ctrl+S
Locate Incident ( ) Locates incident in network view,
10 Operation Manual
Print ( ) Initiates
iates printing of incident data,
Incident Event Log ( ) Opens the Incident Event Log window (Figure 3.9)
containing the system generated events for the selected incident.
incident These events are
auto-generated
generated based on actions performed for the incident. Events provide
information regarding
ng all changes to the incident from its detection to the
completion,
Figure 3.9 Incident Event Log window
Upon clicking the button ( ) in the Message column of the Incident Event Log
window, the Event Details dialog appears (Figure 3.10)) providing additional details
regarding the selected event.
Figure 3.10 Event Details dialog
Add New Switching Plan ( ) Opens the Switching Plan window for creating a
new switching plan,
11 Operation Manual
Merge ( ) Opens
Opens the Incident Merge dialog (Figure 3.2)) for manual merging of
the incident to another incident or device. The incident is placed within the
Incidents to be merged area of the Incident Merge dialog,
Merge Others to This
his ( ) Opens the Incident Merge dialog for selecting
incidents which need to be merged to the opened one. The opened incident is
placed within the Merge to area of the Incident Merge dialog.
After the user opens an existing incident from the Incident
ident Browser,
Browser the most important
information about the incident is shown in a detailed view of the Incident Management
window (Figure 3.13).
In addition, the incidents which are not closed are presented in network view. The device
having the incident (predicted or confirmed) is indicated with a triangle symbol and ID of
the incident (Figure 3.11).
Figure 3.11 Incident symbol in network view
After right-clicking
clicking on the incident symbol in network view, a context menu appears
containing the following options:
Open Opens the Incident Management window containing details of the

incident,
Merge Selecting this option performs the same action as clicking the Merge
button ( ) within
ithin the IncidentManagement window (Figure 3.8),
3
Merge Others to This Selecting this option performs the same action as clicking
the MergeOthers
Others to This button ( ) within the IncidentManagement window
(Figure 3.8),
Properties Selecting the Properties option opens the Incident Properties dialog
(Figure 3.12)) containing main information regarding the incident. In addition,
buttons for takeover/release, lifecycle

lif buttons, the Incident
cident Event Log ( ), Add
12 Operation Manual
New Switching Plan ( ), Roll Up ( ) and Roll Down ( ) buttons are

available in this dialog.
dialog
Figure 3.12 Incident Properties dialog
TheIncident Detail form (Figure

Figure 3.13) is the detailed view of the Incident Management
window. It represents the central place for managing incidents, allowing both a high-level
high
view of the most important data, as well as offering user to seek additional, detailed
information.
13 Operation Manual
Figure 3.13
13 Incident Management window Incident
ncident detail
When update notifications for incident management are enabled in the Incident
Management customization area of the Options dialog, notifications regarding incident
updates
ates appear at the top of the Incident Management window.
window For additional
information on Incident Management customization, refer to Incident Management
Customization.
TheIncident Detail form groups the most frequent actions
actions in incident dispatching
disp in a
series of buttonsplaced at the top of the form to aid the users work flow. The relevant
buttons are dynamically displayed depending on the status of the incident. Upon clicking
14 Operation Manual
Takeover, the Assigned to value at the top of the form changes.The

changes.T current user is the
only one allowed
wed to change the incident data. In addition, the ETR box for entering
estimated time of restoration in the Incident area becomes editable (Figure
( 3.14).
Figure 3.14
14 Incident Management window Incident assigned
TheDispatch button
utton offers a list of crews to be assigned to the incident within the Crew
Assignment dialog.. When the incident status is New, the Dispatch button is visible at
the top of the Incident Details form. If the incident status is of some other type, this
button is not visible. The incident is confirmed by clicking the Confirm button. The
Cancel button cancels the incident.If
incident.If an incident is dispatched, it can be completed
15 Operation Manual
(when the work on the incident is finished)

finished by clicking the Field Complete button. The
FLISR button expands the Devices area and offers a list of devices for FLISR actions.
NOTE: Names of the top row buttons,

buttons, as well as the incident statuses can be configured
by the administrator. For additional information refer toIncident
toIncident Management
Customization.
3.1.1.1. Incident
The Incident area of the Incident Management window provides the following
information:
nique incident identifier.

Incident ID A unique ntifier. This number is unique and is generated
by the system when incidentis saved for the first time,
Type Type of the incident:

incident
o Non-outage,
o Unplanned outage,
utage,
o Planned outage,
o Planned work,
o Public lighting failure All street lights under one transformer
transform on one phase
are taken into account as energy consumer of a special street light type.
When this type of incident is selected, the Number of lights box appears
within the Incident area of the Incident Management window. In this box,
number of failed lights
l can be entered,
Subtype Incident sub-type
sub type is an attribute which describes nature of incidents. The
following sub-types
types are available:
o Load shedding Incidents caused by load shedding process,
o Sustained Sustained
ustained incidents,
inciden where crew work is required,
uired,
o Momentary Incidents caused by transient fault or fuse blowing protection
scheme, but received in DMS as reclosing in the network,
Priority Incident priority (1 means the highest priority, while 5 means the lowest
priority),
Outage time Time of the first call or the first last gasp event.
event The assigned user
can manually edit this time. This time can be manually changed before confirming
the incident. Once the incident is confirmed, outage time cannot be changed,
ETR The ETRbox is used to follow the work schedule in the control room, as well
as to communicate the expected time the power supply will be returned to the
customers. The
he default value of the estimated
estimated time of restoration (ETR) is
16 Operation Manual
automatically set at the time of incident creation. The user has the ability to override
the ETR set by the software, in which case the software
software will not change the ETR
value,
Instruction A self note written by an operator who has taken the ownership of the
incident,
Calls Number of calls,
Smart meter events
s Number of smart meter events,
Created at Time of outage creation,
Created by Source of the outage,
Major Force This type of outages should be included into the system,
system but should
not be included in regulatory index calculation,
Origin Attribute
e that defines incident as internal or external (source of the
problem is outside of jurisdiction of distribution company, e.g. transmission network
problem).. Content of the Cause and Sub-cause boxes depends on this value (and
incident type).
). These boxes display only causes available for the current value of
incident origin and type,
type
Current feeder Feeder affected by the incident,
Normal feeder Name of the feeder element to which the device is connected in
the source system,
Problems Problems existing
existin within the outage,
Confirmed Information whether the incident is confirmed or not. Each incident has
an incident confirmation status:
o Unconfirmed The incident on the device is only predicted. Source
S of the
incident are calls or AMI events,
o Confirmed The incident on the device is confirmed. Source
Source of the incident is
SCADA or field crew notification, or the device is opened,
Status Status of the incidents lifecycle. The default incident statuses are:
o New The incident is detected,
o Dispatched Thehe workk on the incident has commenced. This T is the state in
which the incident
ent spends most of its lifetime,
o Damage Assessed Damage caused by the incident has been evaluated,
o Completed Thehe work
w on the incident is finished,
o Cancelled - Noo work on the incident is to be performed,
o Closed The incident is no longerr in the active incident store,
o Archived The
he incident is archived,
Power status Power status of the customers affected by the incident,
17 Operation Manual
ATR The ATR (actual time of restoration) box is not editable.

editable. If all customers are
restored, ATRis
is set to the time stamp of the last restored individual customer,
customer
Is nested Information whether the incident is nested or not,
Has nested/coupled Information whether the incident contains nested and/or
coupled incidents,
Affected Number of customers affected by the incident,
Unrestored customers Number of unrestored customers. The number of
unrestored customers indicates partial or full restoration,
Restoration verified customers Number of customers confirming the power
restoration on a callback or Power Up events received through AMI restoration
verification ping,
Total service transformer power Total amount of power of service transformers
affected by the outage,
outage
MTR Maximum time of restoration defined for
or urban and rural incidents. In case
this time is exceeded,, the alarm is generated.
3.1.1.2. Devices
The Devices area (Figure
Figure 3.16) shows the predicted or confirmed incident devices. The
following toolbar buttons are available
avai in the Devices area:
Locate Device ( ) Locates device in network view,
Edit Devices( ) Enables editing of predicted device for unconfirmed incidents

and manual merge of incidents. Incidents will be merged if they have same outage
device. Therefore,, in order to manually merge incident A to incident B, outage
device of incident that is being merged (incident A) should be set to the outage
device of the incident to which the merge is performed (incident B),
Open( ) / Close ( ) Upon confirmation from the field crew that the device is
actually open, clicking the Open button ( ) updates the switch status in DMS real-
real
time model to open.. After the Open button ( ) is clicked and the device opened,
the button changes to Close ( ). After clicking the Open( )/Close ( ) button,
the Switch Options dialog appears (Figure
( 3.15)) where time of opening/closing the
device can be set. In case the outage device is service location or SDP (service
delivery point), the Confirm Outage
O and Restore buttons are available instead of
Openand Close.. The Confirm Outage button confirms the incident and sets all
affected customers to be unrestored. Upon clicking Confirm Outage,
Outage the button
18 Operation Manual
changes to Restore.
Restore Clicking the Restore button restores customers (sets
(
restoration time and returns number of unrestored customers to 0).
0
Figure 3.15 Switch Options dialog
Roll Up ( ) Re-triggers
triggers the prediction process. The device is confirmed closed
and the next device is suggested as probably
p tripped. The next probable tripped
device is based on all available information in that moment,
moment, such as the incident
subtype, information whether the upstream device is a telemetered device or not,
the data quality of the telemetered device, etc. The
The roll up does not need to result in
predicting the immediate next upstream device,
Roll Down ( ) Rolls down the predicted outage device to the next downstream
protection devices or to the service location where trouble calls
call and/or last gasp
events exist. This functionality enables the operator to roll down the incident, in
case a mistake is made with the manual roll up, or the prediction
predic engine predicted
too fast. The device to roll down depends on whether the downstream device is a
telemetered device orr not, the data quality of the telemetered device, etc.
Split ( ) This
This functionality enables the operator to split the incident in case the
operator has made any mistake in merging 2 confirmed outage incidents. In such a
case, the operator can split the single
s incident with 2 devices into 2 separate
incidents as they were prior to merging.
merging
NOTE: Roll Up and Roll Downactions
Downactions are allowed for unconfirmed outage incidents
only.
In the Devices area, it is possible to execute FLISR application for the selected outage.
FLISR application controls are integrated into the Incident Detail to allow the user to run
the applications and observe their results. The equipment lists which represent input data
for the applications are automatically populated by Incident Management to minimize
input from the user. For additional information on running FLISR application, refer to
Fault Location, Isolation and Supply Restoration.
Restoration
19 Operation Manual
Figure 3.16 Devices area
3.1.1.3. Crews
Crews assigned to the incident are available in the Crews area (Figure
Figure 3.17).
Figure 3.17 Crews area
The following buttons are available in the Crews area:
Add Crew ( ) Opens the Crew Assignment dialog (Figure

Figure 3.18),
Edit Selected Crew ( ) Enables changing crew data,

Delete Crew ( ) Removes the selected crew,
Open Crew ( ) Opens the Crew Management window (Figure

Figure 3.63),
Locate Crew ( ) Locates crew in network view,
Locate Vehicle ( ) Locates crew vehicle in network view.
20 Operation Manual
Upon clicking the Add Crew

rew button ( ), the Crew Assignment dialog appears showing
available crews
ews in the list as presented in Figure 3.18.
Additional
ditional data for the selected crew is available in the Members,
Members Vehicles,
Assignments and Skills areas. Crews can be filtered in the Filter area. To assign
selected crew to an incident, the check box in the Selected column needs to be checked
and theAssign button in the bottom right part of the dialog clicked.
ed. After clicking this
button status of the incident changes to Dispatched and in the Crews area of the
Incident Management window the crew that was previously selected is added.
NOTE: Crews in the Crew Assignment

Assig dialog are sorted according to their optimal
index. Optimal index depends on the number of the crew assignments, as well
as on the distance of the crew from the incident. When crew is assigned to an
incident its optimal index changes to the higher one one and the crew is sent to the
back of the list. As long as availability of the crew is Available, the crew is listed
in the Crew Assignment dialog for incidents and can be assigned to more than
one incident at a time.
21 Operation Manual
Figure 3.18 Crew Assignmentdialog
When crew is assigned to an incident the status of the crew is changed to Assigned.
Upon assigning crew to an incident, a crew assignment symbol appears in network view
next to the device for which the incident was created. Crew assignment symbol is
connected to device with white line (Figure
( 3.19).
Figure 3.19 Crew assignment symbol in network view
22 Operation Manual
Upon right clicking on the crew symbol, a context menu appears. The following options
are available:
Locate in other views Opens the dialog for selecting network view in case the
crew is visible in some other network view,
Properties Opens
pens the Crew Properties dialog (Figure 3.59
59) showing details of
the crew. For additional information on crew properties refer toCrew
to Properties.
3.1.1.4. Calls
The Calls area contains a list of all calls grouped to the incident (Figure 3.20). This
includes customer er information related to the user who took the call, as well as the time
the call is received, call reason, hazard existence, the time when the call was performed,
etc. For calls
alls that have additional information
information submitted (comment or hazard), an
exclamation sign ( ) is presented in the first column of the table.
The following toolbar buttons are available:
Locate Call ( ) Locates the selected call in network view,
Open Call ( ) Opens the Trouble Event Management window containing

details of the selected
d call,
Cut Calls ( ) Cuts selected calls,
Paste Calls ( ) Pastes cut calls to the Calls area.
Figure 3.20 Calls area
3.1.1.5. Problems
The Problems area (Figure
Figure 3.21) contains a list of problems and faults
f that have been
recorded in the area of the incident or related to the incident.
incident
The following buttons are available in the Problems area:
Add New Problem ( ) Enables creating new problem,
Edit Selected Problem

roblem ( ) Enables changing data of the selected
sel problem,
23 Operation Manual
Delete Selected Problem

roblem ( ) Removes the selected problem,
Locate Problem ( ) Locates the problem in network view.
Figure 3.21 Problems area
A problem is any condition not modeled electrically in DMS which h must be tracked in the
software for safety purposes and for the purposes of organizing work, e.g. a wire on the
ground, a transformer on fire or a flooded manhole. This area allows adding
add and deleting
problems, or completing their lifecycle (problem
( lifecycle
cycle is configurable).
configurable Problems are
also shown in network view (Figure
( 3.22). Upon hovering with the mouse over the
problem symbol in network view, a tooltip containing problem comment appears.
NOTE: Problems reported by call are also referred as hazards.
Figure 3.22 Problem representation in network view
24 Operation Manual
After right-clicking
clicking on the problem symbol in network view, a context menu appears
containing the Open Incident and Properties options. Selecting the Properties option
opens the Problem Properties dialog containing main information regarding the problem
(Figure 3.23).
Figure 3.23 Problem Properties dialog
3.1.1.6. Switching Operations

The Switching operations
ations area (Figure 3.24) contains the instructions related
rela to the
particular incident. This area is usedfor the unplanned work,, which in most cases will not
be followed by any official document (work plan), but the list of switching switch actions
performed on a particular
cular incident is still needed for the dispatching process,
process as well as
for the appropriate
te historical reporting.
reporting
In addition, switching plans related to the incident are available within the Switching
plans area. It is possible

ble to add new switching plan ( ), to remove an existing plan ( ),
as well as to open selected plan ( ).
Figure 3.24 Switching operations area
25 Operation Manual
The following buttons for managing switching operations are available in the Switching
operations area:
Add Text Instruction ( ) By clicking this button, the Free Text Instruction
Window appears (Error!
Error! No se encuentra el origen de la
la referencia.)
referencia. in which
free text instruction can be entered to switching plan as a step,
Figure 3.25 Free Text Instruction Window
Temporary Cut ( ) Opens the Temporary Cut Instruction Window for

placing temporary cut. Upon entering appropriate data in this dialog and clicking the
OK button, the temporary cut instruction
inst is added to the list of instructions,
instructions
Temporary Jumper ( ) Opens the Temporary Jumper Instruction Window

for placing temporary jumper. Upon entering appropriate data in this dialog and
clicking the OK button, the temporary jumper instruction is added
a to the list of
instructions,
Temporary Grounding ( ) Opens the Temporary Grounding Instruction

Window for placing temporary grounding. Upon entering appropriate data in this
dialog and clicking the OK button, the temporary grounding instruction is added
a to
the list of instructions,,
Temporary Generator ( ) Opens the Temporary Generator Instruction

Window for placing temporary generator.. Upon entering appropriate data in this
dialog and clicking the OK button, the instruction for establishing temporary
generator is added to the list of instructions,
Add changeset ( ) This button is used for adding

networkpatches(changesets)toswitchingplan,inordertocaptureeverystepwhichneedst
obeperformedinthefield. By clicking the Add changeset button, the Changesets
Summary dialog appears (Figure
( 3.26). Bydouble-clickingonachangeset
clickingonachangeset in the list
orselectingitandclicking
orselectingitandclickingOK,anewchangesetinstructionisaddedtoswitchingplan.
anewchangesetinstructionisaddedtoswitchingplan.
26 Operation Manual
Figure 3.26 Changesets Summary dialog
Paste from clipboard ( ) Pastes copied switching steps from clipboard,
Create Safety Document ( ) Creates new safety document within the Safety
Document window.When
.When the safety document is created and saved, it is
automatically added to the list of instructions as a single step.
step For additional
information on the Safety Document window, refer to Safety Document,
Document
Select Safety Document ( ) Allows adding already created safety document to

the list of instructions
tructions from the Safety Document Browser window. The safety
document can be added by dragging it from the browser to the list of instructions.
For additional information on the Safety Document Browserwindow,
Browser refer to
Switching Plan Browser,
Browser
Validate ( ) Used to validate steps in the instruction list.

list The steps are
automatically validated one by one, in
in order they appear in the list,
Remove ( ) Removes
emoves the selected entry from the list of instructions,
instructions
Remove All ( ) Clears all instructions,
Stop execution of all issued instructions ( ) Cancels the execution of all
issued instructions.
3.1.1.7. Incident Location
An operator in the control center can receive location based incidents, which means the
location is not linked
ed to any electrical device. The location of such incident can be
entered in the Incident location
ocation area (Figure 3.27).). As keys are typed in the appropriate
fields for entering intersection within the Incident location area, items containing typed
string are being suggested.
27 Operation Manual
Figure 3.27 Incident location area
3.1.1.8. Nested/Coupled Incidents

The Nested/Coupled incidents
ncidents area (Figure 3.28) lists nested and coupled incidents
related to the selected incident. Nested incidents are caused by multiple faults, multiple
multi
trips with the same fault, etc. The Is potential check box refers only to manually created
nested incidents and indicates whether the incident is nested or potentially nested.
Separate incident that is created above or bellow an existing incident and does not
satisfy rules for nested incident is marked as coupled incident.
The following buttons are available in the Nested/Coupled incidents area:
Promote to Nested
ested Incident ( ) Promotes potentially nested incident to nested
incident,
Add New Nested Incident ( ) Enables adding new nested incident,
Edit Selected Nested Incident ( ) Enables editing nested incident,

Delete Selected Nested Incident ( ) Removes
es the selected nested incident,
Open Selected Nested Incident ( ) Opens the details of the selected incident,
Locate Incident ( ) Locates incident in network view.
28 Operation Manual
Figure 3.28 Nested/Coupled incidentsarea
3.1.1.9. Customers
Affected individual customers are presented in the Customers area (Figure
( 3.29). This
area presents the number ofunrestored and affected customers and power, meter ping
statistics, as well as the list of all individual customers affected by the incident.
Figure 3.29 Customersarea
Upon clicking the Create Callback button ( ), the Feedback reason eason dialog appears
(Figure 3.30).). After selecting reason for callback and clicking the Create button, the
callback is created and can be viewed in the Callback Browser window (Figure
( 3.48).
29 Operation Manual
Figure 3.30 Feedback reasondialog
The Create meter ping request button ( ) is used for creating meter ping request for
individual customer, while the Create meter ping for all customers button ( ) creates
meter ping request for all listed customers.
By clicking the Create meter poll request button ( ), smart meter poll (checkingthe
(check
voltage level of the meter) is performed in order
er to verify the calls such as Low Voltage
and Light Flickering.

lickering. The Create meter pollfor all customers button ( ) creates
smart meter poll request for all customers.
customer
3.1.1.10. Resolution
In the Resolution area (Figure
Figure 3.31)) the user is able to enter information regarding the
incident such as cause and subcause which are important for historical tracking of
incidents that can be useful for further analysis.
ana Details of the problem and actions taken
for reparation can be defined in the Problem details and Repair actions list boxes. In
addition, it is possible to enter comment regardingthe incident by clicking the Add
Comment button ( ). The user enters comments based on information from the field,
and based on their own decisions.
30 Operation Manual
Figure 3.31 Resolution area
3.1.1.11. Service Transformers

The Service transformers area (Figure 3.32) contains a list of service transformers
affected by the incident. For each transformer in the list, name,
n custom ID and nominal
power (ratedS from catalog) are presented.
presented
Figure 3.32 Service transformersarea
3.2. Incident Historical Browser
TheIncident
Incident Historical Browserwindow
Browser represents a list of all closed incidents in
previous period retrieved from historical database (Figure 3.33).
). The browser can be
reached by selecting OperationsIncident Historical Browser from the main menu.
31 Operation Manual
Figure 3.33 Incident Historical Browser window
This window is identical to the Incident Browserwindow

window in terms of the
informationprovided. However
owever, it always needs to be filtered based on a time interval
from the past. The Incident Historical Browserwindow
Browser is used by users responsible for
reporting to create various set of reports for regulatory and company management. In
addition,, this window is used by system supervisors to retrieve information about
archived incidents, as well as to additionally edit such incidents.
User is able to reorder columns, sort them and change visibility. Upon right clicking on
the column header, column visibility can be set.
set
TheIncident
dent Historical Browser toolbar provides the following buttons:
buttons
Refresh ( ) Refreshes data in the list,
Open Incident ( ) Opens the Incident Historical Management window

(Figure 3.36) containing details for the selected incident,
Locate Affected Network ( )Locates
Locates affected incident area in network view,
Print ( ) Initiatess printing of the incident data,
Export Page to Csv ( ) Exports

Exports data in the current page to csv file,
Export All Pages to Csv ( ) Exports all data to csv file,
Reliability Analysis Function ( ) Initiates OMS Reliability

eliability Analysis calculation,
Incident Historical Summary Report ( ) Opens the Incident Historical

Summary Report tab (Figure 3.34) within the Incident Historical
Hi Browser
window.
32 Operation Manual
Figure 3.34 Incident Historical Summary Report
In the Incident Historical Browser Filter area it is possible to filter incidents by different
criteria (Figure 3.35). TheStart
Start Time and End Timeboxes are available for defining the
time frame in the past in order to retrieve the list of incidents.
incidents. When expander is clicked,
first column is added automatically in the filter query. User can specify type of query for
each column depending on column type (date, string, number etc.). Filter is applied as
user types in
n the search field. The Execute button executes the filter.
The list of incidents in the browser is automatically refreshed. The list can also be sorted
by any of incident properties.Filter is applied as user type keys in the search field. Filter
can be saved by clicking the Save filter button ( ) and removed by clicking Delete
filter ( ). An existing filter can be loaded by clicking the Load filter button ( ).
Figure 3.35 Incident Historical Browser Filter area
3.2.1. Incident Historical Management

TheIncident
Incident Historical Management window (Figure 3.36)) can be reached by clicking
the Open Incident button ( )in the Incident Historical Browser window. The
Incident Historical Management window can also be opened by double-clicking
double on the
row with the selected incident in the Incident Historical Browser window.
33 Operation Manual
Figure 3.36 Incident Historical Management window
After the user opens the incident from Incident Historical Browser,
Browser the most important
information about the incident is shown in a detailed view of the Incident Historical
Management window.
3.3. Incident Overview
The Incident Overview window (Figure 3.37)) can be reached by selecting

OperationsIncident Overview from the main menu. In this window, data regarding
incidents in the entire network is available. For supervisors and shift managers in the
control room, or even managers accessing from the corporate environment, Incident
34 Operation Manual
Overview offers a dashboard type of view into the OMS aspects of the current state of
the distribution system.
Figure 3.37 Incident Overview window
Table in theIncident
Incident Overviewwindow
Overview window shows the number of incidents in different states
of the incident lifecycle (New, Cancelled, Closed, Field Completed, Dispatched, Damage
Assessed), as well as the total number of incidents in the system. The table also shows
the global indices such as the highest priority incidents, number of customers and
customer power affected by incidents, unsecured problems etc. In addition, indices
i are
presented in form of charts. When hovering with the mouse over charts, a tooltip
containing additional numerical values appear (Figure
( 3.38).
35 Operation Manual
Figure 3.38
38 Examples of charts with numeric values presented
ented
3.4. Incident Coloring
When many incidents exist in the network, the user is able to see the incidents in
network view by using incident coloring of network view.
view It is possible to color part of the
network affected by incident (Figure
( 3.39) by different criteria:
Incident confirmation,
Problem existence,
Incident type,
Incident subtype,
Outage time range,
Incident status,
Incident priority,
Nested incident.
36 Operation Manual
Figure 3.39 Coloring by incident status
Coloring incidents in network view is configurable. For additional information refer

toIncident
Incident Management Customization.
Customization
3.5. Problem Browser
The Problem Browserwindow

window (Figure 3.40) represents a list of all active problems
(hazards) in the system containing the information important for identifying
identify the problem.
This browser can be reached from the main menu by selecting OperationsAdvanced
Incident ManagementProblem Browser.
Figure 3.40 Problem Browserwindow
In the Problem Browser toolbar, the following buttons are available:
37 Operation Manual
Open Problem ( ) Opens the detailed view of the problem within the
ProblemManagement
ProblemManagementwindow (Figure 3.41).
). In this window, it is possible to set the
same data regarding the problem as in the Problems area of the Incident
Management window (Figure
( 3.21),
Locate Problem( ) Opens network view and highlights the device containing
the problem,
Print ( ) Initiates printing of the problem data,
Export to Csv File ( ) Exports data to csv file.
Figure 3.41 ProblemManagementwindow
3.6. Problem Overview
The ProblemOverviewwindow
window (Figure 3.42) can be reached from the main menu by
selecting OperationsAdvanced Incident ManagementProblemOverview.
ProblemOverview In this
window, data regarding problems in the entire network is available.
38 Operation Manual
Figure 3.42 ProblemOverviewwindow
3.7. Call Browser
TheCall Browserwindow (Figure

Figure 3.43) represents a list of all active customer calls in the
system containing the information important for identifying the problem.
problem This browser can
be reached from the main menu by selecting OperationsAdvanced Incident
ManagementCall Browser.
Browser
Figure 3.43 Call Browser window
Calls
alls that have additional information submitted (comment or hazard) have different
representation. For such calls, an exclamation sign ( ) is presented in the first column
of the Call Browser window.
39 Operation Manual
When a new call is created or removed, the list of calls is updated automatically. User is
able to reorder
er columns, sort them, and change visibility. Upon right-clicking
right on the
column header, a menu appears where columns to be visible can be selected.
selected
In the Call Browser toolbar, the following buttons are available:
New Location Based Call ( ) Opens the Trouble Event Management window
for creating new location based call (Figure
( 3.44).
). Location based calls are calls
with no electrical connection to the network
net (no service delivery point detected),
Open Call ( ) Upon selecting a call

call in the browser, clicking this button opens
the Trouble Event Management window (Figure 3.47)) containing
containin details of the
selected call,
Delete ( ) Removes the call,
Locate Call ( ) Opens network view and locates the call,
Open Incident ( ) Opens Incident Details of the incident for which the
selected call is added after creation,
Print ( ) Initiates
ates printing of the call data.
40 Operation Manual
Figure 3.44 Trouble

Trouble Event Management window for creating new location based call
Upon clicking the Locate Call(

Call ) button, the call is located in network view (Figure
(
3.45). Hovering with the mouse over the call symbol in network
network view shows a tooltip
containing information regarding hazard existence, type of hazard and comment.
41 Operation Manual
Figure 3.45
45 Located device as a result of Locate Call action
In the Call browser filterarea

area user can search through calls (Figure
Figure 3.46). Type of query
for each column depending on the column type (date, string, number) can be specified.
Filter is applied as userr type keys in the search field. Filter can be saved by clicking the
Save filter button ( ) and removed by clicking Delete filter ( ). An existing filter
can be loaded by clicking the Load filter button ( ).
Figure 3.46 Call browser filter area
3.7.1. Trouble Event Management
The Trouble Event Management window (Figure 3.47) appears upon clicking the Open
Call button ( )for the selected call in the Call Browser window. TheTrouble Event
Managementwindow
window contains details of the selected call.
call. This window can also be
reached by double-clicking
clicking on a row with the selected call in the Call Browser window.
42 Operation Manual
Figure 3.47 Trouble Event Management window
In the Trouble Event Management window toolbar, the following buttons

bu are available:
New Location Based Call ( ) Opens the Trouble Event Management window
for creating new call,
Submit Call ( ) Submits call,

Locate Call ( ) Locates the call in network view,
view
43 Operation Manual
Open Incident ( ) Opens Incident Details of the incident

nt to whichthe trouble
call belongs,
Print ( ) Initiates printing of the call data.

The Call area contains the main information regarding the call. The call reason can be
one of the following:
ustomer is out of supply,

No power Customer
Hazard existence Customer
C is supplied but observes hazards (wire down, arcing
wire etc.) and calls to submit hazard presence and other useful information
info
regarding the hazard,
Flick light Customer
ustomer is supplied but observes lights flickering usually caused by
reclosing and/or circuit breaker operations,
operations
Power restored Customer
ustomer calls to report that the power is restored,
Partial power Customer
ustomer is partially supplied which makes
makes sense with 3-phase
(generally speaking multiple) supplied customers,
Voltage problem.
In the Comment area, the user can enter or view additional comments from the
customer.
The Hazard area shows the problems related to the incident. The user is able to enter or
view multiple hazards reported by the customer.
NOTE: Adding comments and multiple hazards is possible
possible only during trouble call
creation process.
The Customer area presents the information about the customer who performed the
call, while the Caller data area presents the main information regarding the person who
reported the call.
3.8. Callback Browser
TheCallback Browserwindow
window (Figure 3.48) represents a list of all callbacks created in

OMS. This browser can be reached from the main menu by selecting Operations
Advanced Incident Management Callback Browser.
44 Operation Manual
Figure 3.48 Callback Browser window
When a new callback is created or removed, the list of callbacks is updated

automatically. User is able to reorder columns, sort them, as well as to change visibility.
Upon right-clicking on the column header, columns visibility can be set.
set
In the Callback Browser toolbar, the following buttons are available:
Open Callback ( ) Opens the Callback Management window (Figure

( 3.50)
containing details for the selected callback,
cal
Delete ( ) Deletes callback from the list and closes opened callback from
Callback Management if that callback was opened,
Locate Callback ( ) Opens network
ork view and highlights device,
callback is created,
Print ( ) Initiatess printing of the callback data,
Takeover ( ) Enables
Enables users to assign callbacks to themselves, thus marking
the ones which are not to be processed by the call center personnel, but instead will
be performed directly by the user. After clicking this button, the button changes to
Release ( ).
In theCallback browser filter

ilterarea, the user can search through callbacks (Figure
( 3.49).
Upon clicking the expander, first column is automatically added in the Callback browser
filter query. Type
ype of query can be specified for each column depending on the column
type (date, string, number). Filter is applied as user type keys in the search field.
fiel
45 Operation Manual
Filter can be saved by clicking the Save filter button ( ) and removed by clicking
Delete filter ( ). An existing filter can be loaded by clicking the Load filter button (
).
Figure 3.49 Callback browser filter area
3.8.1. Callback Management
TheCallback
Callback Management window appears upon clicking the Open Callback button (
)for the selected callback in the Callback Browser window. TheCallback

Management window contains details of the selected callback (Figure
( 3.50). This
window can also be reached by double-clicking
double clicking on the row with the selected callback in
the Callback Browser window.
46 Operation Manual
Figure 3.50 Callback Management window
In the Callback
k Management toolbar, the following buttons are available:
Save Callback ( ) Saves callback data,

Locate Callback ( ) Opens network view and highlights device,
47 Operation Manual
selected callback iss created,
Print ( ) Initiates printing of the callback data.

The Takeover button assigns callback to the current user. Upon clicking this button, it
changes to Release and the user is allowed to change the callback data.
In the Callback area of the Callback Managementwindow the time when the callback
should be performed can be set in theOrdered
the time box. It is possible to set Feedback
result (status of callback restored, successful etc.) and Feedback reason
r (work
started,, power restored, etc.).
The Caller data area contains the main information regarding the person who submitted
the call, while the Customer information
i area presents details of the customer who
performed the call.
In the Comment area it is possible to enter the comment regarding callback.
callback
The Callback attempts area lists previous callback attempts. Comments regarding the
customer call are listed in the Call comments area.
3.9. Smart Meter Event Browser
OMS processes AMI last gasp events created and published from smart
s meters. The
Smart Meter Event Browserwindow
Browser (Figure 3.51) represents a list of all active smart
meter events in the system containing the information important for identifying the
problem.. This browser can be reached from the main menu by selecting
OperationsAdvanced Incident ManagementSmart Meter Event Browser.
48 Operation Manual
Figure 3.51 Smart Meter Event Browserwindow
Smart meters are able to automatically generate Power down (presented

(presented as No Power
in the Reason column
olumn of the Smart Meter Event Browserwindow)) and Power up events
(presented as Power Restored in the Reason column of the Smart Meter Event
Browserwindow).). OMS processes those events in order to detect outages and to verify
restoration of particular customers.
custo Smart meters send instantaneous notification when
they lose power
wer and these eventss are treated in the same way as No power calls. Smart
meters generate Power up message when they are restored. If DMS has detected
det that
customer is restored ed based on Power up message, that customer is marked as
Restoration verified.
In the Smart Meter Event Browser toolbar, the following buttons are available:
Open smart meter(

meter ) Opens the Trouble Event Managementwindow
Management
containing details of the selected event (Figure
( 3.52),
Delete ( ) Removes the event,
Locate ( ) Locates the event in network view (Figure
( 3.53)),
selected
d event is added after creation,
Print ( ) Initiates
ates printing of the event data.
The Call area of the Trouble Event Managementwindow
Management representing AMI event
contains the main information regarding the event, while the Customer
Custom area presents
customer location information.
49 Operation Manual
Figure 3.52
52 Trouble Event Managementwindow AMI event
Figure 3.53 depicts AMI event representation in network view.
Figure 3.53 AMI event in network view
Upon right-clicking
clicking on the AMI symbol in network view, a context menu appears
containing 2 options: Properties and Open Incident.. Selecting the Properties option
opens the list of smart meter events (Figure 3.54).
). For listed AMI events, it is possible to
open details of the event ( ), as well as the incident related to the event ( ).
50 Operation Manual
Figure 3.54 Smart Meter Event List dialog
3.10. Smart Meter Request Browser
The Smart Meter Request Browserwindow (Figure 3.55)) represents a list of all smart
meter requests (ping and poll requests) in the system.
system. This browser can be reached from
the main menu u by selecting OperationsAdvanced Incident ManagementSmart
Meter Request Browser.
Figure 3.55 Smart Meter Request Browserwindow
In the Smart Meter Request Browser toolbar, the following buttons are available:
ava
Locate ( ) Locates the pinged customer in network view,

view
Delete ( ) Removes the selected request,
Delete all ( ) Removes all requests,
Open Incident ( ) Opens Incident Details of the incident within the Incident
Management window,
51 Operation Manual
Print ( ) Initiates
ates printing of the request data.
3.11. Crew Browser
TheCrew Browserwindow
window represents a list of all crews in the system (Figure
( 3.56). The
Crew Browser window can be reached by selecting
s OperationsCrew Browser from
the main menu.
Figure 3.56 Crew Browser window
Each crew in the system has its crew properties such as skills, assignments, members
and vehicles. When these properties
properties are modified, they get automatically updated in the
Crew Properties dialog (Figure 3.59).). For additional information on crew properties,
refer to Crew Properties.
It is possible to reorder and sort

s columns, ass well as to change visibility of columns.
The following buttons are available in the Crew Browser toolbar:
Refresh ( ) Refreshes data in the browser,
Properties ( ) Opens
Opens the Crew Properties dialog (Figure
Figure 3.59),
Locate ( ) When the crew is assigned to a device, this button opens network
view and locates the crew,
New ( ) Opens the Crew Management window for creating new crew,
52 Operation Manual
Open ( ) Opens pens the Crew Management window (Figure Figure 3.63) containing
details ofthe selected crew. For additional information on Crew Management,
Management refer
to Crew Management,
Management
Delete ( ) Removes the selected crew,
Edit by Type ( ) Provides menu for editing an existing crew,

crew vehicle and
crew member type as well as editing crew companies and regions,
Print ( ) Initiates printing of the crew data.
Upon clicking the Edit by Type

T button ( ), a menu appears containing the following
options:
Crew Companies,
Crew Member Types,
Types
Crew Types,
Crew Vehicle Types,,
Regions.
Upon selecting any of these options, the Edit Types dialogappears
appears (Figure
( 3.57). In this
dialog, it is possible to add, edit or remove companies, crew members, crews, crew
vehicles and regions.
53 Operation Manual
Figure 3.57 Edit Types dialog
In the Filterarea, the user can search through crews (Figure

( 3.58
58). Upon clicking the
expander, first column in the Filter query is automatically added. User can specify type
of query for each column depending on the column type (date, string, number). Filter is
applied as user type keys in the search field. Filter can be saved by clicking the Save
filter button ( ) and removed

rem by clicking Delete filter ( ). An existing filter can
be loaded by clicking the Load filter button ( ).
Figure 3.58 Filter area
3.11.1. Crew Properties
In the Crew Properties dialog (Figure

( 3.59)) it is possible to set the availability of the
crew (off work, available, out on mutual aid, on break) by using the Availability list box
and clicking the Submit button afterwards. Additional comments can be added by
entering text in the Comment
Comme box and clicking the Submit button.
In the Assignments area of the Crew Properties dialog, incidents and switching plans
assigned to the crew are presented. The following buttons are available:
54 Operation Manual
Open assignment ( ) Opens the details of the selected assignment

ass (incident
within the Incident Management window, or switching plan within the Switching
Plan window),
Locate ( ) Locates the incident in network view,
Change status for selected assignment ( ) Changes status of the crew

for the selected assignment.
assignment. The following crew statuses are available:
o Arrived,
o Assigned,
o Working,
o En route,
o Completed,
Remove ( ) Removes assignment from the list of crew assignments,
Move to Top ( ) Places the selected assignment at the top of the list,
Move Up ( ) Moves the selected assignment up in the list,
Move Down ( ) Moves the selected assignment down in the list,

Move to Bottom ( ) Places the selected assignment at the end of the list,
Turn on/off incident auto-order

auto ( ) Incidents are automatically ordered by
priority, and if priority is the same, then by distance (straight--line distance, not the
route distance). Switching
tching plans for that crew will not be ordered specially and
a will
have lesser priority than
tha the incidents. By clicking the Turn on/off incident auto-
au
order button,this
this automatic ordering can be turned ed on and off. If auto order is
turned on, it will override any manual order if such exists. Only assigned incidents
are ordered. Reordering is triggered by adding new incident to assignments for that
crew or by updating priority for an existing incident.
55 Operation Manual
Figure 3.59 Crew Properties dialog
In addition, information regarding crew members, vehicles and skills can be viewed in the
Members (Figure 3.60),Vehicles
Vehicles(Figure 3.61) and Skills (Figure
Figure 3.62) areas of the
Crew Properties dialog.
Clicking the Open button ( ) in the Members area opens the details regarding
selected crew member within
thin the Crew Management window.
56 Operation Manual
Figure 3.60 Crew Properties dialog Members area
Upon clicking the Open button ( ) in the Vehicles area, details regarding selected
crew vehicle appear within the Crew Management window. The Locate button ( )
locates selected vehicle in network view.
Figure 3.61 Crew Properties dialog Vehicles area
Skills of the selected crew are presented within the Skills area of the Crew Properties
dialog.
Figure 3.62 Crew Properties dialog Skills area
3.11.2. Crew Management
Upon double clicking on the selected crew in the Crew Browser window or clicking the
Open Crew button ( ), the Crew Management window appears (Figure

( 3.63). This
windowcontains details of the selected crew.
57 Operation Manual
Figure 3.63
63 Crew details in the Crew Management window
The following buttons are available

avail in the Crew Managementtoolbar
toolbar:
Refresh ( ) Refreshes data in the Crew Managementwindow

window,
New Crew ( ) Opens the New Crew tab within the Crew Management window
for creating new crew,
58 Operation Manual
New Member ( ) Opens the New Member tab within the Crew Management
window for creating new crew member,
New Vehicle ( ) Opens the New Vehicle tab within the Crew Management
window for creating new crew vehicle,
Duplicate Crew ( ) Creates a copy of the selected crew,
Delete ( ) Removes the crew, crew member, or crew
crew vehicle,
Save ( ) Saves
Saves changes made in the Crew Management window.
The availability of the crew can be changed at any moment.. The crew availability is an
important attribute of each crew, allowing user to mark a crew inactive (off work, on
break, out onn mutual aid) and consequently, these crews will not be suggested for
assignment on an incident. After changing availability status in the Availability list box,
the Save button in the toolbar should be clicked to save changes. By updating this field,
user specifies whether the crew can be assigned to an incident or not. The following
default crew statuses are available in the Availability list box:
Off work,
Available,
Out on mutual aid,
On break.
After clicking the Save button to save changes, the status of the crew is updated in the
Availability column of theCrew
Crew Browserwindow.
Browser
In the Members area, a list of all members of the crew with additional data such as name
or phone number is available. Clicking the Open button ( ) in this area opens the
details off the selected crew member (Figure
( 3.64).
59 Operation Manual
Figure 3.64 Crew member details in the Crew Management window
In the Vehicles area, a list of vehicles used by crew containing additional

additiona data (name,
radio ID, etc.) is available. Clicking the Open button ( ) in this area opens the details of
the selected crew vehicle (Figure
Figure 3.65).
Figure 3.65 Crew vehicle details in the Crew Management window
60 Operation Manual
Crew skills are presented in the Skills area of the Crew Management window.
3.12. Crew Member Browser
TheCrew Member Browserwindow

Browser represents list of members of crews that are
available in the system (Figure
Figure 3.66). The Crew Member Browser window can be
reached by selecting OperationsAdvanced Crew Managementanagement Crew Member
Browser from the main menu.
Figure 3.66 Crew Member Browser window
The following buttons are available in the toolbar:

New ( ) Opens the Crew Management window for creating new crew member
(Figure 3.67),
Open ( ) Opens
pens the Crew Management window containing details of the
selected crew member (Figure
( 3.64),
Delete ( ) Removes crew member,
Print ( ) Initiates printing of the crew member data.
61 Operation Manual
Figure 3.67 Crew Management window Creating crew member
In the Skills area of the Crew Management window for the selected crew member, the
following buttons are available:
Edit ( ) Opens the All Skills dialog (Figure 3.68),

Remove( ) Removes the selected skill,
Remove All ( ) Removes
Removes all skills.
62 Operation Manual
Figure 3.68 All Skills dialog
The All Skills dialog contains available skills. Clicking the New button ( ) opens the
Edit Skill dialog (Figure 3.69

69) for adding new skill. The Open button ( ) opens the Edit
Skill dialog for changing data of the existing skill.
Figure 3.69 Edit Skill dialog
Upon selecting skill in the list and clicking the Add Skill to button at the bottom of the All
Skills dialog, the skill is added to the selected crew member.
3.13. Crew Vehicle Browser
TheCrew Vehicle Browserwindow

Browser represents a list of crew vehicles that are available in
the system (Figure 3.70).
). The
T Crew Vehicle Browser window can be reached by
63 Operation Manual
selecting OperationsAdvanced Crew Management Crew Vehicle Browser from

the main menu.
Figure 3.70 Crew Vehicle Browser window
The following buttons are available

a in the toolbar:

Locate ( ) Locates crew vehicle in network view,
New ( ) Opens the Crew Management window for creating new crew vehicle
(Figure 3.71),
Open ( ) Opens
pens the Crew Management window containing details of the
selected crew vehicle (Figure
( 3.65),
Delete ( ) Removes crew vehicle,
Print ( ) Initiates printing of the crew vehicle data.
64 Operation Manual
Figure 3.71 Crew Management window creating crew vehicle
3.14. Customer Browser
TheCustomer Browserwindow
window (Figure 3.72)) contains a list of customers that are
present in the Customer Database. This browser can be reached
reached from the main menu by
Advanced Incident Management Customer Browser.
selecting Operations Browser
65 Operation Manual
Figure 3.72 Customer Browser window
The Customer Browser window provides a quick summary access to the customers
customer
and filtering/sorting capabilities. The user has a possibility to sort columns in ascending
or descending order, or to reorder columns. The Customer List Filterarea F provides
filtering by all available columns.
Refresh ( ) Refresh
efreshes customer list in the browser,
Locate Customer ( ) Locates customers in network view,
Print ( ) Initiates
Initiates printing of the browser data,
Export page to csv file(

file ) Exports
Export all to csv file(( ) Exports all data to csv file,
66 Operation Manual
Create Calls ( ) Opens the Trouble Event Management window (Figure 3.73)
for creating call by the selected customer. Call location information in the Customer
area within the Trouble EventManagement
Event window is automatically populated.
Call person information in the Caller data area is populated with default data
(customer location information), but the user is able to
o manually override this data,
Create meter ping request ( ) Creates meter ping

ing request for individual
customer,
Create meter poll request ( ) Creates meter poll request (checkingthe voltage
level of the meter) for individual customer.
Upon clicking the Submit Call ( ) button in the Trouble Event Management window,
the call is saved
aved and becomes available in the Call Browser window(Figure
window 3.43). In
addition, it is possible to create multiple calls by holding down <Ctrl> key, selecting
appropriate customers and clicking the Create Calls button ( ). After a call is
enteredfrom DMD, it automatically creates an incident. Those trouble calls are not
treated with stewing time, and prediction engine is automatically started.
67 Operation Manual
Figure 3.73 Trouble Event Management window
3.14.1. Customer List
When performing a switching operation, the user often needs to know the exact
customers which are going to be affected by the switching. Complete information about
68 Operation Manual
all customers fed from any given point in the network is

i available in the Customer list
dialog (Figure 3.74).
The Customer list dialog can be reached by selecting the Customer List option from
the context menu which appears upon right clicking on an element in network view. The
Customer list dialog provides all service delivery points which are traced downstream
from the selected device, and all personal customer information related to those service
delivery points.
The Customer list dialog contains a list of all customers that are attached
att to the
selected network element. The following toolbar buttons are available:
Print ( ) Initiates printing of the customer data,
Export page to csv file ( ) Exports data in the current page to csv file,
Export all to csv file ( ) Exports all customer

stomer data to csv file,
Create Calls ( ) Opens the Trouble Event Management window for creating
call by the selected customer. This action can also be performed by right-clicking
right on
a customer in the list and selecting the Create Calls option. It is possible
pos to create
multiple calls by holding down <Ctrl> key, selecting appropriate customers and
clicking the Create Calls

alls ( ) button,
Create meter ping request ( ) Creates meter ping request for individual
customer,
Create meter ping for all customers ( ) Creates meter ping requests for all
customers,
Create meter poll request ( ) Creates meter poll request (checkingthe voltage
level of the meter) for individual customer,
Create meter poll for all customers ( ) Creates meter poll request for all
customers.
69 Operation Manual
Figure 3.74 Customer listdialog
70 Operation Manual
In the Summary area of the Customer list dialog, total and critical number of
customers, as well as number of customers per phases of the selected element is
presented.
The Customer List Filter area provides filtering customers by different criteria.
Detailed customer information is displayed in the Customer details area. This area is
automatically expanded upon double clicking on a customer in the customer list.
Information
rmation regarding customers smart meter is provided in the Meter details area.
3.15. Customer Historical Browser
The Customer Historical Browserwindow

Browser contains a list of all customerswith data
about interruptions
nterruptions in the previous period (Figure 3.75).
). The browser lists affected
customers with appropriate statistic about incidents where those customers were
included. The browser can be reached by selecting OperationsCustomer Historical
Browser from the main menu.
Figure 3.75 Customer Historical Browser window
Refresh ( ) Refresh
efreshes customer list in the browser,
Open Customer ( ) Opens the Customer Historical Management

windowcontaining customer
cust details (Figure 3.77),
Locate Customer ( ) Locates customers in network view,
Print ( ) Initiates
Initiates printing of the browser data,
Export Page to Csv ( ) Exports

Export All
ll Pages to Csv ( ) Exports all data to csv file.
71 Operation Manual
User is able to reorder columns, sort them and change visibility. Upon right clicking on
the column header, column visibility can be set.
set
Customer details are opened by double-clicking
double clicking on the appropriate row
r in the list.
In the Customer historical browser filterf area it is possible to filter customers by
different criteria (Figure 3..76). TheStart Time and End Timeboxes
boxes are available for
defining the time frame in the past in order to retrieve the list of customers. When
expander is clicked, the first column is added automatically in the filter query. User can
specify type of query for each column depending on column type (date, string, number
etc.). Filter is applied as user types in the search field. The Execute button executes the
filter.
Figure 3.76 Customer historical browser filter area
The list of customers in the browser is automatically refreshed. The list can also be
sorted by any of customer properties.Filter is applied as user type keys in the search
field. Filter can be saved by clicking the Save filter button ( ) and removed by
clicking Delete filter ( ). An existing filter can be loaded by clicking the Load filter
button ( ).
3.15.1. Customer Historical Management
The Customer Historical Management window (Figure 3.77)) can be reached by
clicking the Open Customer button ( )in the Customer Historical Browser window.
The Customer Historical Management window dow can also be opened
opene by double-clicking
on the row with the selected customer in the Customer Historical Browser window.
72 Operation Manual
Figure 3.77
3 Customer Historical Managementwindow
window
Historicaldataof the selected customer

cu is shown in the Customer History area of the
Customer Historical Management window.
The Incidents area presents details about incidents where particular customer was
involved. The Open Incident button ( ) in the Incidents area opens the Incident
Historical Management window.
In addition, calls, smart meter events and meter pings are available in the Customer
Historical Management window within respective areas of the Customer Historical
Management window.
73 Operation Manual
3.16. Incident Global Options
ionsAdvanced Incident Management Incident Global

Upon selecting Operations
Options from the main menu, the Incident Global Options dialog appears (Figure
(
3.78).
Figure 3.78 Incident Global Options dialog
74 Operation Manual
In this dialog, it is possible to set maximum number of characters for comment entering
(Max.
Max. characters allowed in Comment field), field), as well as maximum number of
notifications (Maximum
Maximum notifications count).
count
In the Incident area of the Incident Global Options dialog, it is possible to set the
following options:
Merge non-outage with upstream outage incident If this option is checked,

non-outage
outage calls/incidents which are in the area of the confirmed outage incident
are merged to that incident,
Confirm unconfirmed
nfirmed incident on closure If this option is checked, state of an
unconfirmed incident automatically changes to confirmed upon closing the incident,
Delete empty incidents Delete unconfirmed incident if all calls are removed
from it,
Reassign crew on
n roll down When a roll down of an incident results in creation
of new incidents, crews are automatically reassigned to those incidents,
Reassign crew on device change When
When incident device is changed, assigned
crews are automatically reassigned to a new device,
Roll up to substation device Enable/disable auto roll up to devices in HV/MV
substations above feeder head breakers,
Time offset for creation of separate incident [min] Calls with event time that is
earlier than the outage time (and this offset)
offset) of a confirmed upstream incident will
not be assigned to that incident, but a separate one will be created,
Time offset of momentary outage time [min] If No power calls are received in
the area of the confirmed momentary incident with the event time defined by this
option, nested incident for that momentary incident will be created.
created Otherwise, a
separate incident will be created below the momentary incident,
Incident phase split When incident on non-gang
gang device is split by phases,
complementary incident
ident will share predicted device with the initial incident.
In the Call area, the following can be set:
Location based calls merge time Location based calls that are received from
the same landbase location in this time offset will be associated with the
th same
incident,
Service location customers Limit for number of SDPs on one service location
which designates this service location as residential building. In this case, incident
will be rolled up to service location only after configurable number of calls is
received under it,
75 Operation Manual
Calls to roll up to service location Number of calls needed for roll up to service
location in case when service location customers limit is met,
Meter events to roll up to service location Number of smart meter events
neededd for roll up to service location in case when service location customers limit
is met.
In the Crews area, the following can be set:
Auto arrive crew on incident confirmation Crew status is automatically

changed to Arrived when the incident is confirmed,
confirme
Default arrived status Status that will be set for arrived crew (arrived or
working).
3.17. Smart Meter Global Options
Upon selecting OperationsAdvanced Incident Management Smart Meter Global

Options from the main menu, the Smart Meter Global Options dialog
dial appears (Figure
3.79).
76 Operation Manual
Figure 3.79 Smart Meter Global Options dialog
In the Options area,, the following can be set:
Enable ping/poll Turns on/off possibility to ping/poll smart

sm meters from the
system,
Enable power up Turns on/off receiving smart meter Power Up events,
Enable power down Turns on/off receiving smart meter Power Down events,
Request retries Number of request retries in case of timeout,
Retry interval [min] Interval between 2 request retries,
Active request limit Limit for number of pending meter requests in the system. If
the limit is exceeded, a warning message appears.
In addition, it is possible to set minimum and maximum number of active requests

request for
small, medium and large load, as well as their appropriate timeouts.
77 Operation Manual
3.18. OMS Profile Library
DMS introduces the concept of profiles, where a profile is a set of run-time

run configuration
parameters active at one point in time on a given part of the network.The
network. main feature of
the profile concept is the possibility to assign a profile to a network part (feeder,
transformer area, substation,
tation, sub-region,
sub and region).
The concept of profiles in the OMS is used for the prediction analysis configuration,
callback configuration, priority and ETR configuration. Profile schedules provide an
additional flexibility in the OMS configuration. Generally, a profile schedule provides the
ability for a privileged user to assign a specific set of parameters (a profile) to certain
cert
circuits (network parts) for a specific time
ti frame (day, time).
All OMS profiles and profile schedules are visible and editable by privileged users in the
OMS Profile Librarywindow
window (Figure
( 3.80)) which can be reached
re by selecting
OperationsAdvanced Incident Management OMS Profile Library from the main
menu. This window allows user to create new profiles, as well as to edit
ed or delete existing
profiles. Profiles are stored in folder structure.
s
Figure 3.80 OMS Profile Library window
78 Operation Manual
New profile or schedule can be added by right-clicking

right clicking on a folder in the window and
selecting theAdd
Add New Profile or Add New Schedule optionfrom from the context menu. In
addition, existing
g profiles and schedules can be edited or removed by selecting theEdit
or Remove options from the context menu which appears upon right-clicking
right on these
existing profiles and schedules.
3.18.1. Prediction Profiles
Based on trouble calls and smart meter events, system

system predicts the incident (creates
predicted, i.e. unconfirmed incident). Prediction analysis in DMS is performed based on
prediction configuration which is stored in prediction profile.
profile Upon right-clicking
right on the
Prediction Profiles folder in the OMS Profile Library window and selecting the Add
New Profile option, the Prediction Profile Editor dialog appears where a new
prediction profile can be defined (Figure
( 3.81).
79 Operation Manual
Figure 3.81 Prediction Profile Editor dialog
User can specify profile name and description in the Basic data area.
area
In the Automatic roll up area, the following can be set:
Events to roll up to first protective device:

device
o Trouble calls Number of service locations affected
affected with trouble calls required
for roll up to first protective device,
o Momentary calls Number of service locations affected with calls with
momentary semantic required for roll up to first protective device,
Roll up to next upstream device:

device
o Enable Checking
hecking this option enables roll up to next upstream device,
80 Operation Manual
o Affected protection devices [%] In thisbox

box it is possible to enter percentage
of predicted devices in relation to total number of protection devices below the
common protection device upstream.
upstrea When this number is exceeded, all
incidents will automatically be merged (rolled up) to one, with that common
device as predicted,
predicted
o Skip first upstream device If this option is enabled (low call rate fast roll-
up), when
hen the calculation of percentage of protective devices is performed
from an upstream device (say, a line fuse) for an auto roll-up
roll action, a
downstream transformer fuse will be taken into account even if it does not
have a prediction on itself, but any of its SDPs or SLs are predicted to be
under outage. Only transformer fuse can be skipped providing the way for an
upstream device to be predicted. If the Skipfirst
first upstream device option is
disabled (high call rate slow roll-up), only hierarchical roll up is possible
among SL, transformer fuse
f and line fuse.
use. No skipping of transformer fuse is
allowed during auto
au roll-up,
o Slow down phase-wise
phase This option is relevant for 3 phase non-gang
non devices.
When
hen this option is disabled (low call rate fast roll-up),
roll the immediate
downstream devices across
ac all the phases are collectively counted and
percentage of predicted protective devices is calculated. All the phases having
outage incidents will be predicted at non-gang fuse level.level When the
Slowdown
down phase-wise
phase option is enabled (high call rate slow roll-up), an
incident is rolled up to a particular phase of anon-gang
gang device only
onl when it
meets the configured percentage of predicted protectiveive devices from the
same phase.
SCADA quality analog measurement:

measurement
o Measurement When the None option is selected,
d, prediction function will not
consider analog measurements. If the Questionable option is selected,
prediction function will consider analog measuremets with questionable and
good validity. When the Good option is selected, prediction function will
consider
der only measurements with good validity,
SCADA quality incident status:

status
o 1st Predicted device status When the None option is selected, prediction
function will consider all devices as candidates for predicted device,
regardless of SCADA quality of the status
status signals. When the Questionable
option is selected, prediction function will not consider telemetered devices
81 Operation Manual
with good and questionable quality of status signal as candidates (only

devices with bad quality are considered). When the Good option is selected,
prediction function will not consider telemetered devices with good quality of
status signal as candidates (only devices with questionable and bad quality
are considered),
o 2nd Predicted device status When the None option is selected, prediction
function
ction will consider all devices as candidates for predicted device,
regardless of SCADA quality of the status signals. When the Questionable
option is selected, prediction function will not consider telemetered devices
with good and questionable quality of status signal as candidates (only
devices with bad quality are considered). When the Good option is selected,
prediction function will not consider telemetered devices with good quality of
status signal as candidates (only devices with questionable and bad
ba quality
are considered).
In the Nested incidents roll up area, the following can be set:
Trouble calls Number of service locations affected with trouble calls required for
roll up of nested incident to first protective device,
Enable Checking this option

option enables roll up of nested incident to next upstream
device,
Affected protection devices [%] In thisbox

box it is possible to enter percentage of
predicted devices in relation to total number of protection devices below the
common protection device upstream.
upstr m. When this number is exceeded, all incidents
will automatically be merged (rolled up) to one, with that common device as
predicted,
Skip first upstream device If this option is enabled (low call rate fast roll-up),
when
hen the calculation of percentage of protective devices is performed from an
upstream device (say, a line fuse) for an auto roll-up roll up action, a downstream
transformer fuse will be taken into account even if it does not have a prediction on
itself, but any of its SDPs or SLs are predicted to
o be under outage. Only transformer
fuse can be skipped providing the way for an upstream device to be predicted. If the
Skipfirst
first upstream device option is disabled (high call rate slow roll-up), only
hierarchical roll up is possible among SL, transformer
transformer fuse and line fuse.
f No
skipping of transformer fuse is allowed during auto
au roll-up,
82 Operation Manual
Slow down phase-wise

wiseThis option is relevant for 3 phase non-gang
non devices.
When
hen this option is disabled (low call rate fast roll-up),, the immediate downstream
devices across all the phases are collectively counted and percentage of predicted
protective devices is calculated. All the phases having outage incidents will be
predicted at non-gang
gang fuse level. When the Slowdown down phase-wise
phase option is
enabled (high call rate slow roll-up), an
n incident is rolled up to a particular phase
of anon-gang
gang device only
only when it meets the configured percentage of predicted
protective
ive devices from the same phase.
In the ETR area, fixed estimated restoration time can be defined by checking the Is ETR
fixed check box and setting the time in the Fixed ETR time box. This ETR will be
assigned to all incidents regardless of their time of report.
A call should not be processed before so called stew time expires since it can be false
or momentary,, or more calls can come shortly. Waiting time before processing calls,
smart meter events, momentary calls and emergency calls can be defined in the Call
processing delay area.
If several location based calls (calls that are connected to lanbase location rather to any
electrical device) are submitted within close geographical area, they are joined to the
same incident as this can mean that the reason for all calls is the same. Radius for this
geographical proximity can be defined by entering appropriate value
value (in meters) in the
Grouping calls [m] box within the Location based calls area.
After setting appropriate values, the OK button should be clicked to save changes.
Upon right clicking on a prediction profile in the list of profiles in the OMS Profile Library
window and selecting the Edit option, the Prediction Profile Editor dialog for editing
profiles appears (Figure 3.82
82).
83 Operation Manual
Figure 3.82 Prediction Profile Editor dialog Editing

ng an existing profile
In the Prediction Profile Editor dialog opened for editing of the selected profile, an
additional area exists the Last update area. This area shows name of the user who
was the last to perform update of the profile, as well as time of the last update.
In addition, when the Prediction Profile Editor dialog is opened for an existing profile in
the library, the Priorities button at the bottom of the dialog is active. Upon clicking the
Priorities button, the Priority Profile Editor dialog
dial appears (Figure 3.83
83).
Priority profiles are used to determine
determine priority of an incident. Incident priority is defined
based on the following parameters:
parameters
84 Operation Manual
Number of affected customers,

customers
Number of affected critical customers,
customers
Affected customer power,
power
Affected critical customer power,
power
Minimum outage time.
Based on these conditions, appropriate priority is assigned to every incident. If conditions

change, priorities
riorities change automatically. Estimated time of restoration (ETR) for an
incident
ent is set based on the priority.
Figure 3.83 Priority Profile Editor dialog
In this dialog, 5 different profiles with different values of each property are presented. By
clicking the AddNew
New Prioritybutton
Priority ( ), the New Priority dialog appears (Figure
( 3.84),
where a new priority can be added.
85 Operation Manual
Figure 3.84 NewPriority dialog
By clicking the EditPriority

Prioritybutton ( ), the Priority Editor dialog appears (Figure
( 3.85)
where data for the selected priority can be changed. The Remove Prioritybutton
Priority ( ) is
used for removing priorities.
86 Operation Manual
Figure 3.85 Priority Editor dialog
3.18.2. Callback Profiles

Upon right-clicking
clicking on the Callback Profiles folder in the OMS Profile Library window
and selecting the Add New Profile option, the Callback Profile Editor dialog appears
(Figure 3.86). In thiss dialog, data for a new callback profile can be defined.
87 Operation Manual
Figure 3.86 Callback Profile Editor dialog
Upon right-clicking
clicking on an existing callback profile in OMS Profile Library and selecting
the Edit optionn from the context menu, callback profile data can be changed in the
Callback Profile Editor dialog. User is able to change all profile data, except the profile
name.
Three
hree different groups of customers which are involved in automatic callback creation
are available in the Customer calls area of the Callback Profile Editor dialog:
Affected customers Considering all affected customers in automatic callback

creationregardless of whether they submitted call or not,
88 Operation Manual
Calling customers Considering customers who

ho submitted calls in automatic
callback creation regardless of whether they explicitly
icitly required callback or not,
Customers with callback required Considering only customers who explicitly
required callbackin automatic callback creation.
creation
Three different trigger types for automatic callback creations are available in the
Customer calls area:
Incident being worked on Creating callback when crew is dispatched to a new

incident,
ETR updated Creating ETR whenever ETR is updated in order to keep the
customer informed,
Restored Creating callback when customers are restored/re-energized.
restored/re
The Incident being worked on,

on ETR updated and Restored sliders provide possibility
to define callbacks creation for customers of different priorities. For example,
example one type of
callback can be created (being worked on, ETR changed, power restored) only for critical
customers, and another type of callback can be created
created for all other customers. Slider
position represents the minimum customer priority
priority for creating a callback. Zero
Z position
of slider means that callbacks will not be created for the selected group of customer for
the selected trigger.
Automatic callback creation for unlocated calls can be defined by checking appropriate
check boxes in the Unlocated calls area of the Callback Profile Editor dialog.
If callback
ck is not performed to customer after a number of retries set in the Call retries
box, such callback is removed. In the Retry after [min] box,the period between 2
successive callbacks can be set. Maximum assigned period for callback in minutes can
be set in the Max assigned period [min] box. By checking the Non
Non-outage callbacks
checkbox, it is possible to provide callbacks
callback for the non-outage
outage incidents.
incidents By checking
the Special caller PD/FD check box, it is possible to provide callbacks
callback for special callers
(police and fire department).
After setting appropriate values, the OK button should be clicked to save changes.
3.18.3. Profile Schedules

Upon right-clicking on the Profile Schedules folder in the OMS Profile Library window
and selecting the Add New Schedule option, the Profile Schedule Editor dialog
appears (Figure 3.87). ). In this dialog, profile schedule data can be defined.A
defined. profile
schedule enables assigning ing a specific set of parameters (a profile)
ile) to certain circuits
(network parts) for a specific time frame (day, time).
89 Operation Manual
The user defines a profile schedule by defining

defining name of the schedule,
schedule the time frame for
which the schedule is going
oing to be active,
active relevant
vant day types for the schedule and the
profile
rofile which has to be active in the given time frame.
Figure 3.87 Profile Schedule Editor dialog
3.19. OMS Profile Assignments Editor
The OMS Profile Assignments Editor window (Figure 3.88)) can be reached by
selecting OperationsAdvanced
Advanced Incident ManagementOMS
Management OMS Profile Assignment
Editor from the main menu.
Figure 3.88
3 OMS Profile Assignments Editor window
90 Operation Manual
In the left part of this window, a tree-view

tree view containing all feeders in the system is
presented. Upon expanding the tree and selecting appropriate feeder, assignment of
prediction and callback profiles, as well as schedule assignment can be viewed. It is
possible to search
rch for specific network element by using the Search text box.
After selecting feeder and clicking the Set Profile button ( ), the Set feeder profiles
dialog appears (Figure 3.89
89).
). This dialog can also be reached by right-clicking
right on the
appropriate feeder and selecting the Edit Assignment option from the context menu.
Figure 3.89 Set feeder profilesdialog
In the Set feeder profiles dialog, desired prediction and callback profiles,
profiles as well as
profile schedule assignment can be set. Upon setting profile values and clicking OK, the
values in the OMS Profile Assignments Editor window change accordingly.
91 Operation Manual

TE 002222 MOP 002 OMS Operation Manual

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

TE 002222 MOP 002 OMS Operation Manual

Загружено:

Авторское право:

Доступные форматы

Schneider Electric DMS NS

OMS (Outage Management System)

Last update: September, 2014

3. OUTAGE MANAGEMENT ................................................................

3.1.1. Incident Management ................................................................

3.2.1. Incident Historical Management .............................................................

3.4. Incident Coloring

3.6. Problem Overview ................................................................

3.7.1. Trouble Event Management ................................................................

3.8.1. Callback Management ................................................................

3.10. Smart Meter Request Browser ................................................................

3.11.1. Crew Properties ................................................................

3.13. Crew Vehicle Browser ................................................................

3.14.1. Customer List ................................................................

3.15.1. Customer Historical Management ..........................................................

3.17. Smart Meter Global Options ................................................................

3.18.1. Prediction Profiles ................................................................

III Operation Manual

Figure 3.35 Incident Historical Browser Filter area ....................................................

Figure 3.71 Crew Management window creating crew vehicle................................

Version Authors Date Comments

2. DEFINITIONS AND ABBREVIATIONS

3.1. Incident Browser

The Incident Browser window (Figure

Figure 3.1 Incident Browser window

The following buttons are available in the Incident Browser toolbar:

Open Incident ( ) Opens the detailed view of the incident within

Locate Affected Network ( ) Locates part of the networkaffected by the

Print ( ) Initiates printing of the incident data,

Export to Csv File ( ) Exports data to csv file,

Mark as Unread( ) Marks the incident as unread (bolds

Figure 3.2 Incident Mergedialog

Merge to ( ) This button is enabled when the Incident Merge dialog is

Takeover ( ) Assigns the incident to the current

Figure 3.4 Incident Validation Result message

Figure 3.5 Incident Status Change dialog

Figure 3.6 Status change reason dialog

Figure 3.7 Filtering incidents

filter ( ). An existing filter can be loaded by clicking

3.1.1. Incident Management

Figure 3.8 IncidentManagement window

The following buttons are available in the Incident Management window:

New Incident ( ) Opens a new incident,

Locate Incident ( ) Locates incident in network view,

Figure 3.9 Incident Event Log window

Figure 3.10 Event Details dialog

Figure 3.11 Incident symbol in network view

Open Opens the Incident Management window containing details of the

buttons for takeover/release, lifecycle

New Switching Plan ( ), Roll Up ( ) and Roll Down ( ) buttons are

Figure 3.12 Incident Properties dialog

TheIncident Detail form (Figure

Takeover, the Assigned to value at the top of the form changes.The

(when the work on the incident is finished)

NOTE: Names of the top row buttons,

nique incident identifier.

Type Type of the incident:

Power status Power status of the customers affected by the incident,

ATR The ATR (actual time of restoration) box is not editable.

Locate Device ( ) Locates device in network view,

Edit Devices( ) Enables editing of predicted device for unconfirmed incidents

Figure 3.15 Switch Options dialog

Figure 3.16 Devices area

Figure 3.17 Crews area