eRespond Event Management

1
eRespondEvent Management
2
What is an Event ?

• An Event is the eRespond representation of a
  fault or potential fault, usually - but not
  exclusively on a network
• An event can be
• An individual trouble ticket from a premise
• An outage or fault impacting multiple premises
• A maintenance event not yet impacting customers
  - but may if not fixed
• A planned outage with premises affected
  requiring notification
• A number of events that represent alternative
  symptoms of the same underlying fault may be
  grouped together under a parent event
• Usually done automatically as part of eRespond
  inferencing
• Can be manually grouped
• A grouped event may consist of an overall outage
  parent event, a SCADA operation and/or trip, and
  a number of trouble tickets
• An event can be progressed to various states to
  represent the current status of the real world
  fault e.g. pending closure, closed

3
Access the Event Management Module

• To access the Event Management module, select the
  Events menu from the main eRespond menu, and
  select List
• The Event List Screen is displayed

4
Searching for Events

• The Event List Search Pane allows the user to
  search for Events using criteria in 3 different
  tabs

Further relevant Event attributes
Address and Location attributes, e.g. search by
Street and Town
General Event attributes
5
View Event Details

• The Event details can be viewed in 2 ways
• Via the tabbed Event Details area in the List
  Display
• Via the Right-click menu in the Event List
  display

6
View Event Details (cont.)

• Viewing Event details on tabbed area of Event
  List

Summary Event Information, including Summary
information, Trouble tickets grouped to event,
eRespond alarms associated with event, Switching
Steps associated with event, any telemetry
(SCADA) events associated with event, the list of
faulted devices associated with event, free text
note updates, and Planned Outage details (Planned
Outages only)
7
View Event Details (cont.)
The Edit Event Details wizard allows the user to
not only view the event details but, unlike the
tabbed area update some of the values (see
Creating Events for full step-through of Event
Details Wizard)
8
Creating Events

• eRespond allows the user to manually create
  events, for example in response to feedback from
  field, or creating a Planned Outage
• The user can create one of 3 types of event
• An Outage a no supply event that may affect
  multiple premises
• A Planned Outage a planned no-supply event that
  may affect multiple premises
• A Maintenance Event - an unplanned event that
  will require urgent attention but which has no
  immediate impact on premises
• Once created an outage or maintenance event has
  the same behaviour as if created automatically
  via an interface or as the result of inferencing
• To create an event select Create Event from the
  right-click menu on the event list (or in the
  case of an Outage, from the device tree view or
  schematic)

9
Create Event (cont.)
Select and event type and then click on Next
10
Create Event (cont.)
Search for a device that represents the root
device for the outage or maintenance event,
select the device, and click on Next
11
Create Event (cont.)
Confirm or update event address
12
Create Event (cont.)
Associate Event Conditions (or Trouble Codes)
with the event
13
Create Event (cont.)
Supply Start Time (mandatory, and optional
additional milestones)
Update reason for event, priority, severity if
known. Update Certainty Status (Suspect/Confirmed)
, and associate event with a Guaranteed Standard
if appropriate)
At this point the user can complete the dialogue
and the new event is created otherwise continue
to provide more information
14
Create Event (cont.)
Add free text memo to event
15
Create Event (cont.)
Final summary screen, Click on Finish to create
event
16
Updating Events

• There are a number of elements of an event that
  can be updated
• The basic event details (as covered in View
  Event Details/ Create Event)
• The scale of the event (updating the number of
  devices faulted in the outage)
• Restoration status of the event either complete
  or partial
• Updating milestones on an event
• The Status of the event (see Progressing Events)

17
Updating the Scale of an Event

• To update the scale of an event, select the
  appropriate event in the event list, then
• Select the Faulted Devices tab

To add a device to the outage
18
Updating the Scale of an Event (cont.)
Search for the device to add, select the device,
and click on Next
19
Updating the Scale of an Event (cont.)
Select the Include Downstream Devices checkbox,
supply an interruption date and time, and click
on Finish
20
Updating the Scale of an Event (cont.)
Current customers affected is updated to reflect
the increased scale of the event
Devices have been added to faulted devices tab
21
Updating the Scale of an Event (cont.)

• To reduce the scale of an event
• The Faulted Devices tab is updated, and the
  selected devices (and any downstream devices are
  removed)
• The number of customers affected on the event is
  also updated

Select devices to remove, and select Remove
Devices Only or Remove Downstream Devices
22
Restoring Devices on an Event

• To restore device on an event, select the
  appropriate event in the event list, then
• Select the Faulted Devices tab

Select the devices to be restored, and select
Restore Selected Devices only, or selected and
downstream devices
23
Restoring Devices on an Event (cont.)
Supply a restoration date and time for the
devices (defaults to current date and time)
24
Restoring Devices on an Event (cont.)

• The restored devices are removed from the Faulted
  Devices tab
• The current customers affected column for the
  event is updated to reflect the current scale of
  the event
• A restoration stage is created on the associated
  Event Report

25
Updating Milestones on an Event

• Milestones are significant work and event dates
  and times that are updated to provide visibility
  to the operations centre and customers on
  progress from the field.
• Examples include
• Estimated/Actual Time of Restoration (ETR/ATR)
• Estimated/Actual Time of Arrival (on site)
  (ETA/ATA)
• Estimated/Actual Time of Completion (of work)
  (ETC/ATC)

26
Updating Milestones on an Event (cont.)

• The current milestone status on an event is shown
  in the Summary tab of event details
• To update a milestone on an event
• Select Edit Event Details from the right-click
  menu on the event list
• Click twice on Next in the wizard until you
  reach the page with the Add Milestones section

27
Updating Milestones on an Event (cont.)
Where multiple updates, for example to
restoration time, are supplied by the user -
only the latest update is displayed
Select a Milestone Type from the drop down list,
and supply an estimated date and time. When you
click Add it is added to the list of milestones
28
Progressing Events

• Progressing events is the eRespond term for
  changing the Status of an event
• An event in eRespond can have the following
  status
• Created Default status for newly created events
• Open Event has been confirmed as real event
• In Progress Event has been assigned resources
  and work is ongoing
• Deferred Work has been delayed on this event
  until a later date
• Cancelled Event has been cancelled
• Pending Closure Restoration work has been
  completed but awaiting confirmation all
  supplies have been restored
• Closed All work has been completed - and
  supply restoration confirmed
• Proposed Planned outage created with proposed
  dates and time
• Approved Planned outage start and end dates and
  times approved
• Notified Customers affected by planned outage
  have been notified

29
Progressing Events (cont.)

• An event can only be progressed to certain states
  from a restricted list of the other states,
  represented in the matrix below
• Read the table as status in first column can be
  progressed to status in first row

30
Progressing Events (cont.)

• To progress an event, right-click on the event in
  the event list and select
• If an event progression is not valid under the
  configured business rules, a warning dialogue box
  will be presented to the user
• The event list can be filtered by one or more
  selected event statuses

31
Group Events

• If you believe that two events that have not been
  automatically grouped by eRespond are in fact
  related then you have the option of manually
  grouping them
• To manually group 2 or more events, select (via
  Ctrl-click) the events to be grouped, and
  right-click and select

32
Group Events (cont.)

• The resulting dialogue box asks you to identify
  a Parent Event, and confirm the grouping
• Confirming the grouping results in the Parent
  Event remaining in the event list with the other
  events grouped under it

33
Group Events (cont.)

• The grouping can be confirmed by selecting the
  tree tab from the event list

34
Group Events (cont.)

• The following rules apply for manually grouping
  events

35
Ungroup Events

• To ungroup an event from a parent event
• Select the parent event in the event list
• Select the tree view tab
• Right-click on the event to be ungrouped from the
  Parent event, and select Ungroup Event
• The ungrouped event will re-appear in the event
  list

36
Manually Create Work Orders

• eRespond has certain internal business rules that
  will result in Work Orders being created
  automatically on an event however you can also
  manually create a WO on an event
• Right-click on the event in the event list and
  select Create Work Order
• A WO will be created, associated with the event
  and the WO details will be visible on the WM tab
  of the event list (the status of the event will
  also be progressed to In Progress

37
View Premises Affected by Planned Outages

• For Planned Outages you can view the list of
  premises affected/ or proposed to be affected by
  the outage
• Right-click on the planned outage in the event
  list and select
• This takes you to a filtered Premise List showing
  the premises affected

38
View linked eRespond objects from Events Module

• Where an event has some associated objects in
  other eRespond modules, e.g. Work Orders,
  Premises, Devices, they can be reached directly
  from the event list without first having to go to
  the relevant module

• The associated objects are displayed in a
  filtered list, with details displayed in tabbed
  area
• To return to the Event List, select the Back
  arrow

39
View Event Audit Trail

• To view the audit trail (history) for an event
• Right click on the event
• Select
• This will bring up the event audit trail display

40
eRespond Inferencing and Auto-Call Grouping

• eRespond Inferencing and automatic call grouping
  is based on the connectivity of devices as
  represented by the Network Model, and a level of
  configuration in terms of inferencing thresholds.
• There are 2 principal means of grouping
  troubletickets and outages
• By triggering the creation of outages as the
  result of troubletickets being created in
  eRespond and tracing upstream to locate any
  common immediate upstream device
• As the result of the creation of an upstream
  outage (e.g. as the result of a SCADA breaker
  trip) and then sweeping any downstream (as in
  network model) outages and troubletickets into
  the newly created outage
• Troubleticket inferencing is controlled by a
  series of configurable thresholds which determine
  the number of downstream faulted devices before
  the common upstream device is faulted. E.g.
• Need 2 calls downstream of an LV fuse device
  before the LV fuse is marked as faulted
• Need 3 LV fuses faulted before a MV/LV
  transformer is marked as faulted

41
Summary

• In the Events Management module we have covered
• Searching for events
• Viewing events details
• Creating events
• Updating events
• Restoring devices
• Progress events
• Manually group events
• Manually create work orders from the event list
• View premises affected by planned outages
• View associated objects such as work orders,
  devices, and outage reports from the event list
• How eRespond Inferencing and automatic call
  grouping work