Scope For

Outage Management System Request for Information (RFI)

Document Type

Revision 1

Revision Date

Total Pages 22

CONTROLLED DISCLOSURE Page 1 of 22

Scope

For

Outage Management System

Request for Information (RFI)

Part 1

PROJECT MANAGER : John Hope-Sotherton

PROGRAMME MANAGER : John Hope-Sotherton

BUSINESS SPONSOR :

CONTROLLED DISCLOSURE Page 2 of 22

DOCUMENT CONTROL INFORMATION DOCUMENT REVISION HISTORY

Revision Date Author Reason for change

0 27/10/2016 Jason Haken / John Hope-Sotherton / Johan Jonker

Draft

1 02/12/2016 Jason Haken First Issue

CONTROLLED DISCLOSURE Page 3 of 22

CONTENTS

PREAMBLE ................................................................................................................................... 4

1. INTRODUCTION............................................................................................................... 7

1.1 DOCUMENT SCOPE ........................................................................................................ 7 1.2 RELATED DOCUMENTS AND STANDARDS ................................................................. 8 1.3 BACKGROUND ................................................................................................................ 8

1.3.1 GENERAL ........................................................................................................... 8 1.3.2 IT ENVIRONMENT .............................................................................................. 9 1.3.3 BUSINESS ENVIRONMENT (DISTRIBUTION DIVISION) ................................ 13

2. RFI APROACH (PROCESS) AND TIMELINES .............................................................. 14

3. SCOPE ........................................................................................................................... 16

3.1 SCOPE OVERVIEW ....................................................................................................... 16 3.2 VENDOR PROFILE ........................................................................................................ 16 3.3 PRODUCT ARCHITECTURE AND FUNCTIONALITY ................................................... 16 3.4 PRODUCT LICENSING MODEL AND PRICING ............................................................ 20 3.5 IMPLEMENTATION ARCHITECTURE ........................................................................... 20 3.6 MAINTENANCE AND SUPPORT ARRANGEMENTS .................................................... 21 3.7 PRODUCT ROADMAP ................................................................................................... 21

4. GENERAL REQUIREMENTS ......................................................................................... 22

4.1 INDICATIVE PRICING .................................................................................................... 22 4.2 RETURNABLE FORMATS ............................................................................................. 22 TABLE OF FIGURES Figure 1: Conceptual Landscape (As-Is) ....................................................................................... 9 Figure 2: Conceptual Landscape (Future) .................................................................................. 11 Figure 3 Conceptual Mobile OMS Apps ...................................................................................... 11 Figure 4 Deployment Pattern ....................................................................................................... 12 Figure 4: Approach ....................................................................................................................... 14 TABLE OF TABLES Table 1: ABBREVIATIONS Table 2: GLOSSARY OF TERMS Table 3: ESKOM REFERENCES

CONTROLLED DISCLOSURE Page 4 of 22

Request For Information (RFI) regarding industry standard Commercially off-the-Shelf (COTS) Outage Management Systems (OMS) solutions and vendors and related Advanced DMS solution. PREAMBLE

Eskom is exploring the feasibility of replacing its existing Outage Management System solution, utilised within the Eskom Distribution Division. An RFI for an industry standard Commercially off-the-Shelf (COTS) solution will involve the following steps:

Item

RFI issued.

Respondent E-mail acknowledgement form to Eskom.

Clarifications closing date (Respondent queries).

RFI closing date & submissions.

Eskom review period & clarification request/s.

Respondent responses to Eskom requests for clarification

The following diagram provides an overview of the RFI process:

CONTROLLED DISCLOSURE Page 5 of 22

ABBREVIATIONS

Abbreviation Explanation

ADMS Advanced Distribution Management System

ADR Architectural Design Review

COTS Commercially off-the-Shelf

DMS Distribution Management System

DSLI Distribution Supply Loss Index (i.e. HV SLI)

EHPUM Eskom High Performance Utility Model

FLISR Fault Location Isolation and Service Restoration

FMS Fault Management System

HV High Voltage

IT Information Technology

KPI Key Performance Indicator

LV Low Voltage

MV Medium Voltage

NERSA National Energy Regulator of South Africa

OEM Original Equipment Manufacturer

OMO Operating, Maintenance & Outages

OMS Outage Management System

OOTB Out-of-the-Box

QA Quality Assurance

RMC Resource Management Centre

RFI Request for Information

RFP Request for Proposal

RSLI Reticulation Supply Loss Index (i.e. MV SLI)

SAIDI System Average Interruption Duration Index

SAIFI System Average Interruption Frequency Index

SCADA Supervisory Control and Data Acquisition

VAT Visual Analysis Tool

Table 1: ABBREVIATIONS

GLOSSARY OF TERMS

Term Explanation

Advanced Distribution Management System (ADMS)

An advanced distribution management system (ADMS) is the software platform that supports the full suite of network management, grid optimization and outage management. An ADMS includes functions that automate outage restoration and optimize the performance of the distribution grid. ADMS functions being developed for electric utilities include fault location, isolation and restoration; volt/volt-ampere reactive optimization; conservation through voltage reduction; peak demand management; and support for microgrids and electric vehicles. [Source: Gartner]

CONTROLLED DISCLOSURE Page 6 of 22

Term Explanation

Distribution Division To avoid confusion between the voltage level and the Eskom Division, the terms “Distribution Division” and ”Distribution business” will be used whenever referring to Eskom Distribution Division. The Eskom Distribution Division encompasses the networks widely referred to as “sub-transmission” and “distribution” i.e. HV, MV and LV networks.

Distribution network Distribution system

In Eskom this refers to all wires networks up to and including 33kV (to be qualified wherever necessary as MV networks, or LV networks if not referring to both)

Eskom Eskom Holdings Limited.

High Voltage Nominal voltages from 132kV to 44kV (inclusive)

Low Voltage Nominal voltages below 1kV

Medium Voltage Nominal voltage from 33kV to 1kV (inclusive)

Outage Unavailability of a portion of the sub-transmission and/or distribution network, either due to:

Planned outage to perform planned activities, or

Forced (unplanned) outage as a result of an incident.

Outage Management System (OMS)

An outage management system (OMS) is a utility network management software application that models network topology for safe, efficient field operations related to outage restoration. OMSs tightly integrate with call centers to provide timely, accurate, customer-specific outage information, as well as supervisory control and data acquisition (SCADA) systems for real-time-confirmed switching and breaker operations. These systems track, group and display outages to safely and efficiently manage service restoration activities. [Source: Gartner]

Power Delivery The end-to-end transmission of electrical power, from a generating source, to a consumer.

Respondent Entity who responded to this invitation; Prospective Consultant

Transmission Refers to the AC power network at voltages of 220kV through 765kV, and the high voltage DC power network.

Turnkey Turnkey means “ready to use.” It means that the service provider completes all the work required to deliver a finished, operational and usable product.

Vendor Supplier (seller) of software.

Wires Refers to Eskom’s Transmission and Distribution Divisions

Working day Week days from Monday to Friday from 08h00 to 17h00, excluding South African public holidays.

Working week Week days from Monday to Friday, excluding the period from 17 December to 1 January.

Table 2: GLOSSARY OF TERMS

CONTROLLED DISCLOSURE Page 7 of 22

1. INTRODUCTION

1.1 DOCUMENT SCOPE

Eskom has initiated the Outage Management System (OMS) Replacement Project to explore the feasibility of replacing its existing in-house OMS solution with an industry standard commercially off-the-shelf (COTS) OMS solution. The primary drivers for this strategic step change is a drastic reduction in the SAIDI and SAIFI KPIs as per NERSA requirements, and obsolescence of components of the existing solution. At the same time, Eskom wants to increase information velocity and improve operational visibility by ensuring operational reporting at sub 15 min intervals. The objectives of the Request for Information (RFI) associated with this document are: To develop an understanding of the vendors / technology / products available,

specifically with reference to addressing the strategic requirement described above.

Obtain indicative pricing for budgetary purposes:

Product cost based on licensing models. Implementation cost. Support/Maintenance cost for a 5 year period and lifecycle cost.

An OMS solution can be a component of an ADMS solution. This RFI also includes a section related to ADMS in order to understand the Respondent’s full integrated offering (refer to Part 2). The Eskom OMS Replacement Project, however only includes the OMS scope. This document contains Eskom’s scope pertaining to Part 1 of the RFI. The document is divided into the following main sections: Introduction and Background

Approach and Timelines

Scope

General Requirements

CONTROLLED DISCLOSURE Page 8 of 22

1.2 RELATED DOCUMENTS AND STANDARDS

This document forms an integral part of the Request for Information (RFI) documentation, and shall be read in conjunction with other documents in the package. Refer to the cover letter for details. Where any conflict is perceived to exist between documents, the Respondent shall approach Eskom for resolution.

1.3 BACKGROUND

1.3.1 GENERAL

Within Eskom, power delivery is realised through the Wires business, comprising of a Transmission Division and a Distribution Division. The Transmission Division encompasses voltage levels above 132kV while the Distribution Division encompasses voltage levels of 132kV and lower. The Distribution Division consists of 9 Operating Units (OUs). Each OU is operationally divided in a number of Zones and Sectors, served by Customer Network Centres (CNCs). An important operational aspect related to the maintenance of the transmission and distribution networks is the management of outages (planned and unplanned). Various software applications/systems are used within Eskom Distribution to manage outages. Collectively these applications are referred to as the Outage Management System (OMS) solution. The OMS solution interfaces to various other business systems. Refer to Figure 1 for an overview of the current solution.

CONTROLLED DISCLOSURE Page 9 of 22

1.3.2 IT ENVIRONMENT

Current IT Environment:

Figure 1: Conceptual Landscape (As-Is)

The existing Solution comprises of the following components: 1. FMS:

1.1 Unplanned Event/Outage Management

1.2 Network Tracing /Analysis:

Outage Impact Analysis (# Customers, MVA Hours lost) Fault Location Grouping

2. OMS:

2.1 Planned Event/Outage Management

2.2 Network Tracing /Analysis:

Outage Impact Analysis (# Customers, MVA Hours lost)

CONTROLLED DISCLOSURE Page 10 of 22

2.3 Load Shedding Event/Outage Scenarios

2.4 Customer Fire/Burn Management (E.g. Sugarcane)

3. VAT Dispatching

3.1 Planned / Unplanned Outages Management

3.2 Crew Management

4. NEPS

4.1 QA: Outage Impact Analysis post Event/Outage

4.2 Investigations:

4.3 KPI calculation

4.4 KPI Target Setting & Forecasting

5. CNL:

5.1 Customer Network Link

6. CPPM

6.1 Control Plant Performance Management

CONTROLLED DISCLOSURE Page 11 of 22

Future IT Environment:

Figure 2: Conceptual Landscape (Future)

Figure 3 Conceptual Mobile OMS Apps

Outage Management

Work

ManagementE-Operator Log

Permits &

Authorisation

Real-Time

Operational

Analytics

Live

SchematicsOMS

CONTROLLED DISCLOSURE Page 12 of 22

Deployment

Eskom’s key systems deployment is depicted in Figure 4. It highlights the intent to have a centralised OMS deployment. It also indicates that the DMS (SCADA) is decentralised and the CRM, Billing and Work Management (EAM) systems are centralised.

Figure 4 Deployment Pattern

CONTROLLED DISCLOSURE Page 13 of 22

1.3.3 BUSINESS ENVIRONMENT (DISTRIBUTION DIVISION)

Function and purpose of the RMC The RMCs must ensure all unplanned work (with the primary focus on forced

outages) is completed within the time mandated by NERSA in NRS 047.

This is done by :

Scrutinizing work orders to ensure only valid work orders are dispatched. Optimal work order assignment: Prioritizing work orders in order of FMS, Multiple and Single customer (SAIDI

Impact). Grouping of work orders related to the same problem. Dispatching correctly authorized, available resource, closest to fault location. Extracting timeous feedback from technicians. Requesting additional resources when required. Escalating when: Management involvement is required. Scenarios occur when stakeholders needs to be informed. Ensuring timeous restoration of supply.

Number of RMC’s 7

Number of consoles/users. There are 190 users, working on a 24 hour, 3 shift cycle.

RMC Total Dispatch

Staff complement Maximum consoles utilized

during session shift

ECOU 25 6

KZNOU 41 10

MOU 34 9

FSOU 25 6

GOU 46 12

LOU 34 9

WCOU 19 5

Number of Faults per year.

Work order Type Number Description

Individual 1 038 608 Single Service request linked to work order

Network 291 185 Normally multiple service requests linked to work order

Grand Total 1 329 793

CONTROLLED DISCLOSURE Page 14 of 22

2. RFI APROACH (PROCESS) AND TIMELINES

Refer to the RFI Cover letter for information regarding contact persons, timeline dates, etc. The following diagram provides an overview of the RFI process:

Figure 5: Approach 2.1.1 Eskom Issues RFI

The RFI associated with this Scope.

2.1.2 Clarification Period (Respondent Queries to Eskom)

During this time, prospective Respondents may approach Eskom for any clarification required. Refer to the RFI Cover letter for information regarding the clarification closing date.

2.1.3 RFI Closing Date - Submission of RFI

Respondents will submit responses according to the requirements prescribed in the RFI cover letter:

By the deadline indicated.

CONTROLLED DISCLOSURE Page 15 of 22

In the format prescribed. Via the channel prescribed.

2.1.4 Eskom Review & Clarification Request/s

Eskom will study the responses for a period of 3 weeks and then request further information / clarification from specific Respondents where necessary.

2.1.5 Respondent Responses to Eskom Requests for Clarification

Respondents will submit final responses within 2 weeks of receiving request for clarification from Eskom.

CONTROLLED DISCLOSURE Page 16 of 22

3. SCOPE

3.1 SCOPE OVERVIEW

3.1.1 The Scope pertains to an OMS solution for Eskom’s Wires business (Transmission Division and Distribution Division, but primarily Distribution Disvision).

3.1.2 The information required includes:

Vendor profile. Product architecture and functionality. Product licensing model and pricing. Implementation architecture and pricing. Product roadmap Support arrangements and pricing. Training Migration

3.1.3 The list of questions below is not meant to be exhaustive, but as an outline of

information required. The Respondent is requested to provide all information deemed essential to address a specific topic. Eskom will study the response for a period of 3 weeks (excluding the period 16/12/2016 to 06/01/2017) and then request further information / clarification where necessary.

The rest of this Section defines the Scope in more detail:

3.2 VENDOR PROFILE

The objective is to determine:

The long-term viability of the product / Vendor.

Ability of the Vendor to implement a solution of a scale similar to Eskom’s requirement.

RETURNABLE PART 1 SECTION 3.2: 3.2.1 Provide an overview of your company and its history.

3.2.2 Provide a description of your company organisational structure.

3.2.3 Provide a list of your primary customers, with contact details of customer

representatives that may be contacted.

3.2.4 Describe the nature of representation in South Africa, both in terms of

implementations and support.

3.3 PRODUCT ARCHITECTURE AND FUNCTIONALITY

The objective is to determine:

CONTROLLED DISCLOSURE Page 17 of 22

The ability of the offered solution to meet Eskom’s functional / technical

requirements.

The ability of the solution to integrate to Eskom business systems.

The alignment of the Vendor supported platforms (hardware, OS, dBMS, etc) with Eskom’s standards.

RETURNABLE PART 1 SECTION 3.3: 3.3.1 Overview

Describe your OMS solution in context to Figure 1 and Figure 2. 3.3.1.1Provide an overview diagram showing all components as well as integrations (information flow). Indicate what is OOTB (Out-of-the-box), Customised OOTB, Full Customisation, Not Available.

3.3.2 Business Architecture:

For Outage Management NERSA KPIs (SAIDI, SAIFI, RSLI, DSLI), 3.3.2.1identify how your system address/supports each and identify the data dependencies for each?

Please describe how your solution can enable Service Oriented 3.3.2.2Outage Management (not SOA)?

3.3.3 Information and Data Architecture

Describe your data structures (models) that are required to support 3.3.3.1your solution.

Indicate what is OOTB and what is customized.

Please list and describe the solution data dependencies? 3.3.3.2

Indicate if you think there are gaps in Eskom’s data. Describe

these gaps.

How extendable is your data model for configuration and 3.3.3.3customisation, how is this done?

List and describe the expected changes.

Please describe how your solution composes and makes use of the 3.3.3.4Customer to Network Link.

How would you ensure synchronization with the other CNL

information sources?

CONTROLLED DISCLOSURE Page 18 of 22

Describe how the solution caters for HV, MV and LV. 3.3.3.5

3.3.4 Application Architecture

With reference to the Gartner definition of what should be in an OMS, 3.3.4.1indicate which of the following are: Out-of-the-Box (OOTB), Customised OOTB, Full Customisation, Not Available:

FLISR - FLISR

Outage Management - Trouble call processing

Outage Management - Outage analysis

Outage Management - Outage event summary

Outage Management - An outage analysis engine

Outage Management - Outage reporting

Switch Order Management - Switch order management

Switch Order Management - Switch planning

Switch Order Management - Autogenerated switch plans

Dispatch and Crew management - Resource needs prediction

Dispatch and Crew management - Crew management

Performance Management - Reliability performance indexes

Performance Management - Reliability reporting

Network Visualisation - Schematic system views

Network Model and Power Flow - A distribution network model

Weather Intelligence - Storm replay analysis

In your solution, how will the functions described in Section 3.3.4.1 3.3.4.2align to and replace the legacy applications in Error! Reference source not found. ?

Describe in detail the functionality of each component of the

solution.

Provide a mapping to the list above and identify any gaps or

additional capabilities.

Provide a decomposition of application layer components and 3.3.4.3technologies and associated licenses, including Integration.

With regards to Schematics, how would you go about addressing the 3.3.4.4various views of the network throughout the Asset Lifecycle: As Designed, As Operated (Asset) and As Energized etc?

How would you ensure a consistent view between Field Services

and Network Control as described in Operating Regulations for High Voltage Systems?

CONTROLLED DISCLOSURE Page 19 of 22

How are you going to address the Outage Analysis requirements (i.e. 3.3.4.5Network Tracing):

What are the Outage Analysis data dependencies and how are you

going to incorporate the smart meter state in this analysis?

Do you have any DMS (Grid Optimisation application)

dependencies in your Outage Analysis? Please describe?

Do you have any SCADA dependencies in your Outage Analysis?

Please describe?

Have you implemented a OMS on a Primary Plant as well as Control 3.3.4.6Plant (Secondary Plant / Telecoms)?

Provide customer list.

How do you handle control plant induced outages and how do you

account for them in the KPIs?

How does your OMS solution fit into your ADMS solution? 3.3.4.7

Please provide a solution decomposition diagram and describe

each component?

3.3.5 Technlogy Architecture

Please describe your preferred deployment model: centralized, 3.3.5.1decentralized?

Identify the challenges expected with this approach?

Can your solution be deployed in the cloud, be it On Premise, Public or 3.3.5.2Private. Explain?

Can your solution provide High Availability (99.999%)? 3.3.5.3

Please provide a technology deployment diagram and explain how

this architecture enables high availability?

Which operating systems do your mobile applications support? 3.3.5.4

What dependencies are there for your mobile solutions (e.g. EMM,

ECM)

Does your mobile solution work in both online and offline node?

Describe the technologies supported by your solution for the following? 3.3.5.5

Desktop

Servers

Databases

Storage

Network

Security

CONTROLLED DISCLOSURE Page 20 of 22

3.3.6 Integration Architecture

Eskom’s architectural intent is to make use of loose coupling between systems with finely grained services.

Describe how integration will be provided to each of the other systems 3.3.6.1in Figure 2.

In detail, describe integration between the OMS and SCADA/DMS 3.3.6.2systems.

3.3.7 Security

Provide an overview of how you address system security across all 3.3.7.1layers of the solution.

3.3.8 Other

Provide a list of 5 reference OMS customers. For each provide: 3.3.8.1

Customer name

Named contact

Named contact telephone number.

Name Contact email address

3.4 PRODUCT LICENSING MODEL AND PRICING

The objective is to determine: The cost to Eskom.

RETURNABLE PART 1 SECTION 3.4: 3.4.1 Describe the product license model/s. Describe various options, e.g. cost per

unit, Enterprise licensing, etc.

3.4.2 Provide costing. Clearly indicate any volume discounts and other relevant

information.

3.4.3 Provide a high-level implementation plan

3.5 IMPLEMENTATION ARCHITECTURE

The objective is to determine: The ability of the product to meet Eskom’s implementation requirements.

The cost to Eskom.

RETURNABLE PART 1 SECTION 3.5: 3.5.1 Based on the information provided in Section 1.3 (Deployment), provide a high

level proposal for a system architecture that will meet Eskom’s requirement.

CONTROLLED DISCLOSURE Page 21 of 22

Clearly indicate a specification for the hardware platform (server, OS and third party software specifications).

3.5.2 Provide a cost estimate for implementing above proposed architecture.

Distinguish between licensing cost and engineering cost. Include the integration design and implementation cost estimate.

3.6 MAINTENANCE AND SUPPORT ARRANGEMENTS

The objective is to determine: The long term viability of a product / Vendor.

Lifecycle cost.

RETURNABLE PART 1 SECTION 3.6: 3.6.1 Describe the maintenance and support options available:

Software maintenance options, e.g. Greenfields, etc., as well as 3.6.1.1related costing for a 5 year period.

What is the requirement regarding versions of software that are

supported?

Support options and related costing for a 5 year period. 3.6.1.2

3.7 PRODUCT ROADMAP

The objective is to determine: The long term viability of a product / Vendor.

RETURNABLE PART 1 SECTION 3.7: 3.7.1 Provide a roadmap of the solution for the next 3-5 years.

3.7.2 Describe the product development approach, including the involvement of user

groups.

CONTROLLED DISCLOSURE Page 22 of 22

4. GENERAL REQUIREMENTS

4.1 INDICATIVE PRICING

All costing / pricing should be provided in ZAR, excluding VAT. Distinguish between local and foreign currency components, and clearly indicate the exchange rate used for foreign currency components.

4.2 RETURNABLE FORMATS

All returnable must be provided in PDF file format. Refer to the cover letter for further details.