THE KENYA POWER AND LIGHTING COMPANY LIMITED

KENYA ELECTRICITY MODERNIZATION PROJECT (KEMP)

BIDDING DOCUMENTS FOR

ICB No: KP1/6A.1/PT/1/16/17/A60

Design, Supply, Installation and Commissioning of Phase 2 Nairobi

Advanced Distribution Management System (ADMS)

Date of Issue: May, 2017

Part 2 Employer’s Requirements

ii | P a g e

Preface

This bidding document has been prepared by Kenya Power as based on The World Bank

Standard Bidding Document (SBD) for Procurement of Plant Design, Supply and Installation

(April 2015) .

2-1

PART 2 –Employer’s

Requirements

2 | P a g e

Section VI. Employer’s Requirements

Contents PART A – SCOPE OF WORKS.............................................................................................5

1 GENERAL ..............................................................................................................6

2 ACRONYMS ..........................................................................................................5

3 SCOPE OF SUPPLY AND WORKS ...................................................................7

PART B: PROJECT OVERVIEW ........................................................................................9

1. PROJECT DESCRIPTION ..................................................................................9

1.1. OVERVIEW OF EXISTING SYSTEM ..............................................................9

1.2. OVERVIEW OF THE PROPOSED SYSTEM .................................................11

1.3. OBJECTIVES ...................................................... Error! Bookmark not defined.

1.4. PROJECT ASPECTS ..........................................................................................13

2. CHARACTERISTICS OF KPLC DISTRIBUTION NETWORK ........... Error!

Bookmark not defined.

2.1. TECHNICAL CONSTRAINTS ......................... Error! Bookmark not defined.

2.2. THE CONCEPT OF ADMS ...............................................................................15

2.3. ADMS FUNCTIONAL ARCHITECTURE ...... Error! Bookmark not defined.

PART C - ADMS REQUIREMENT ....................................................................................16

1 SCADA ...................................................................... Error! Bookmark not defined.

2 DISTRIBUTION MANAGEMENT SYSTEM (DMS) .....................................39

3 OUTAGE MANAGEMENT SYSTEM (OMS) .................................................56

PART D - ADMS HARDWARE & SOFTWARE DESCRIPTION & ARCHITECTURE

..................................................................................................................................................62

1 ADMS ARCHITECTURE ...................................... Error! Bookmark not defined.

2 ADMS SYSTEM SOFTWARE REQUIREMENTS ........................................74

5 GIS –ADMS INTEGRATION ............................................................................84

PART E: HARDWARE REQUIREMENTS FOR ADMS ................................................88

1 ADMS HARDWARE............................................... Error! Bookmark not defined.

2 GENERAL REQUIREMENTS FOR HARDWARE .......................................88

3 HARDWARE CONFIGURATION ...................................................................89

4 SPECIFICATIONS FOR VIDEO WALL DISPLAY ......................................93

3 | P a g e

PART F – COMMUNICATION ..........................................................................................94

1 RADIO COMMUNICATION ................................ Error! Bookmark not defined.

PART G – LOAD BREAK SWITCH/ SECTIONALISER REQUIREMENTS ...........101

1 APPLICABLE STANDARDS ..........................................................................101

2 SERVICE CONDITIONS .................................................................................101

3 SYSTEM CONDITIONS ..................................................................................102

4 LBS EQUIPMENT RATINGS .........................................................................102

5 SWITCHGEAR REQUIREMENTS ................................................................103

6 CONTROL UNITS ............................................................................................106

7 ANALOGUE MEASUREMENT REQUIREMENTS ...................................111

8 OUTAGE MEASUREMENTS .........................................................................112

9 HARMONIC ANALYSIS .................................................................................112

10 DETECTION REQUIREMENTS ....................................................................112

11 COMMUNICATIONS AND HARDWARE....................................................119

12 TYPE TESTS .....................................................................................................122

13 ROUTINE TESTS .............................................................................................124

PART H–11KV AND 33KV RECLOSER REQUIREMENTS .......................................125

1 APPLICABLE STANDARDS ..........................................................................125

2 SERVICE CONDITIONS .................................................................................125

3 SYSTEM CONDITIONS ..................................................................................126

4 RECLOSER EQUIPMENT RATINGS ...........................................................127

5 SWITCHGEAR REQUIREMENTS ................................................................128

6 CONTROL UNITS ............................................................................................132

7 TYPE TESTS .....................................................................................................152

8 ROUTINE TESTS .............................................................................................154

PART I – REMOTE TERMINAL UNIT (RTU) ..............................................................155

1 GENERAL REQUIREMENTS ........................................................................155

2 SPECIFICATIONS OF REMOTE TERMINAL UNIT (RTU) ....................155

PART J – 11kV RING MAIN UNITS (RMUs) .................................................................165

1 SCOPE ................................................................................................................166

2 REFERENCES ...................................................................................................167

3 TERMS AND DEFINITIONS ..........................................................................167

4 | P a g e

4 REQUIREMENTS .............................................................................................167

5 TESTS AND INSPECTION .............................................................................173

6 MARKING, LABELLING AND PACKING ..................................................174

7 DOCUMENTATION .........................................................................................175

8 INSTRUMENT TRANSFORMERS AND MEASUREMENTS ...................175

PART K – SPARE PARTS .................................................................................................183

PART L –TRAINING..........................................................................................................184

1 GENERAL ..........................................................................................................184

PART M – MAINTENANCE CONTRACT .....................................................................192

PART N–QUALITY ASSURANCE ...................................................................................193

APPENDIX 2 11KV AND 33KV LOAD BREAK SWITCH REMOTE CONTROLS AND

INDICATIONS ....................................................................................................................207

APPENDIX 3 11KV AND 33KV RECLOSER LOCAL CONTROLS AND INDICATIONS

................................................................................................................................................209

APPENDIX 4 11KV AND 33KV RECLOSER REMOTE CONTROLS AND

INDICATIONS ....................................................................................................................211

APPENDIX 5: 11KV AND 33KV LOAD BREAK SWITCHES AND 11kV RING MAIN

UNITS ...................................................................................................................................213

APPENDIX 6: SPECIFICATIONS FOR CONCRETE POLES ....................................222

APPENDIX 7: SPECIFICATIONS FOR LV FUSE PANELS .......................................237

APPENDIX 8 : SPECIFICATIONS FOR CONDUCTOR JOINTS ..............................249

APPENDIX 9: INDUCTIVE VOLTAGE TRANSFORMER .........................................259

APPENDIX 10: PROJECT MANAGEMENT, QUALITY ASSURANCE AND

DOCUMENTATION ...........................................................................................................260

APPENDIX 11: TESTING & DOCUMENTATION .......................................................269

APPENDIX 12: SPECIFICATION FOR THE 15.5KV CIRCUIT BREAKER FOR THE

RING MAIN UNIT EQUIPMENT ....................................................................................277

APPENDIX 13: SPECIFICATIONS ON VARIOUS TOOLS ........................................282

APPENDIX 14: REFURBISHMENT OF RING MAIN UNITS ROOMS .....................291

APPENDIX 15: MOBILE WORKFORCE MANAGEMENT TECHNICAL

SPECIFICATION ................................................................................................................292

APPENDIX 16: FURNITURE SPECIFICATIONS .........................................................308

APPENDIX 17: QUESTIONNAIRE........................................ Error! Bookmark not defined.

5 | P a g e

ACRONYMS

ADMS Advanced Distribution Management System (SCADA / DMS / OMS)

AMI Automatic Metering Infrastructure

CAIDI Customer Average Interruption Duration Index

CAIFI Customer Average Interruption Frequency Index

CIM Common Information Model

CIS Customer Information System

CNC Communication network components

CPE Customer Premises Equipment

DER Distributed Energy Resources

DG Distributed Generation

DMS Distribution Management System

DNP Distributed Network Protocol

ERP Enterprise Resource Planning

FPI Fault Passage Indicator

FPE Front-end Processing Environment

FRTU Feeder RTU (small one box solution RTU , including FPI)

GID Generic Interface Definition

GIS Geographic Information System

HDB Historical Database ICCP Inter Control Centre Communications Protocol

IEC International Electro-technical Commission

IT Information Technology

LBS Load Break Switch

LV Low Voltage

MCC Metering Control Center

MDM Meter Data Management

MRS Management Reading System

MV Medium Voltage

ODB Operational Database

OLTC On Load Tap Changer

OMS Outage Management System

RTDB Real Time Database

RTU Remote Terminal Unit

SAIDI System Average Interruption Duration Index

SAIFI System Average Interruption Frequency Index

SAP Systems, Applications and Products for data processing (developed by SAP AG)

SCADA Supervisory Control And Data Acquisition

SOA Service Oriented Architecture

STS-PDU Static transfer switch with integrated power distribution unit

XML Extensible Markup Language

6 | P a g e

1 SCOPE OF WORKS 1.1 GENERAL

The Bidder shall examine the scope of works in this section in close connection with the other

documents and particulars forming these Bidding Documents.

Special attention shall be paid to General Specifications and Particular Technical Specifications,

in which the general technical requirements are specified. The drawings enclosed in are for bidding

purposes only.

If the Specifications and/or Drawings do not contain particulars of materials or goods, which are

necessary for the proper and safe completion, operation, and maintenance of the equipment in

question, all such materials shall be deemed to be included in the supply.

In the event of any conflict between the Drawings and the Specifications, the latter shall prevail.

Should the Bidder find discrepancies in or omissions from these Specifications or from the other

Documents, or should he be in doubt as to their meaning, he should immediately contact the Project

Manager for interpretation, clarification or correction thereof before submitting his Bid. Such

action shall, however, in no case be considered as a cause for altering the closing date of the Bid.

The scope of work for equipment shall cover engineering design, manufacture, testing before

shipment and packing sea-worthy or otherwise as required, delivery CIP site, of all equipment as

specified in the preceding chapters.

The contractor shall be responsible for design, material supply, transport, erection, installation and

commissioning as well as design and construction of H-pole structures for Load Break Switches

(LBS) and adaptation works for the RMU rooms.

Equipment to be dismantled shall be recovered by the Contractor and deposited at sites to be

advised by the Project Engineer. The equipment include Oil insulated-Ring Main Units and

associated accessories. The recovered equipment is to be taken over by the Employer at these sites.

7 | P a g e

1.2 BRIEF SCOPE OF SUPPLY AND WORKS

The works shall involve Supply, installation, integration, training, commissioning and handover

of a complete Advanced Distribution Management System (ADMS).

The scope of works is summarized as follows:

# Works Details

a. Central system

Shall include:

a1. Application servers and associated software- (SCADA /DMS

/OMS and Development Servers as detailed in the tender document.

They shall be mounted on 42U standard cabinets with dual power

supplies by use of STSs and PDUs.

a2. Communications servers (CFE, FPE etc.)

a3. Necessary furniture to allow long working hours

b. Pole mounted

switchgear

b1. New Pole mounted load break switches - involving erection of

H-structures on concrete poles, dressing, necessary metal works,

necessary civil works, earthing, terminations to the HT lines,

erection of Load break switches, installation of RTUs, radios,

antennae and any other fittings and accessories necessary to make

the LBS fully functional in the new ADMS system.

b2. New Pole mounted auto-reclosers - involving erection of H-

structures on concrete poles, necessary metal works, necessary civil

works, earthing, terminations to the HT lines, erection of auto-

reclosers, installation of RTUs, radios, antennae and any other

fittings and accessories necessary to make the auto-reclosers fully

functional in the new ADMS system.

c Ground mounted

switchgear

c1. New ground mounted RMUs - involving supply of new Ring Main

Units (RMUs), dismantling the old RMUs, installing the new RMUs,

terminating HT, installing the RTUs, radio and any other

fittings/accessories necessary to make the RMUs fully functional in

the new ADMS system.

c2. New ground mounted RMUs – involving installations of RMUs

supplied by the employer. The contractor shall pick the RMUs from

a KPLC Nairobi stores, transport them to site, dismantle the existing

RMUs, install new RMUs, terminate HT, install the RTUs, radio and

any other accessories/fittings necessary to make the RMUs fully

functional in the new ADMS system.

c3. Existing ground mounted RMUs – involving automating of the

manually operated Ring Main Units installed but operated manually.

The contractor shall only install the RTUs, radio and any other

accessories and fittings necessary to make the RMUs fully functional

in the new ADMS system.

d Telecommunications

systems d1. This shall involve designs of an N-1 telecommunication system,

installation of the system, transmission of data from an excess of

2000No. RTU sites to the Control Centre.

8 | P a g e

This shall be achieved by optimum location of repeater sites,

backhauling of the data from the repeater sites to the control centre

via an existing fibre network, setting up redundant/backup

communication link and integrating the existing 200 sites on VHF to

the new platform.

e Training e1. This shall be conducted to the project team both locally and

abroad on all facets of the system including operations, repairs and

maintenance, upgrades, modifications etc.

The proposed syllabus in the tender document is for guidance

purposes only. The supplier is expected to modify the proposed

syllabus which shall form part of the contract.

f Integration to the

new advanced

distribution

management

system

Integration of the following systems shall be as follows:

f1. Integrating the existing Motorola ACE 3600 RTUs to the ADMS

so as to work seamlessly.

f2. Integrating the existing substations ABB Network Manager to the

ADMS system for exchange of real time data to aid in the

management of the distribution system. This shall be done via a

standard ICCP link. The proposed ADMS shall be able to monitor,

extract data and control all the 11kV and 33kV breakers in the

primary substations. It shall be quoted separately.

f3. Laying a foundation for a future link to the other six major towns

in the country which shall work as clients to the NACC.

The towns shall only run the real time applications e.g. SCADA but

shall have capability to exchange offline data with the NACC for

DMS and OMS applications.

f4. Integration with the existing GIS system, smart metering and call

manager.

f5. Integration of existing Pole mounted load break switches

f6. Integration of existing Pole mounted auto-reclosers – ensure

existing auto-reclosers are fully integrated into the proposed ADMS.

F7. Integration of the existing ground mounted RMUs – ensure the

automated RMUs are integrated into the proposed ADMS system.

g Necessary

adaptation works

g1. This shall involve all necessary works for secure and safe

installation of RMUs. This is as detailed in appendix 16.

The project shall be delivered on a turn-key basis with the vendor taking responsibility for

end-to-end delivery of the entire project scope outlined above.

9 | P a g e

1.3 PROJECT OVERVIEW

1.3.1 PROJECT DESCRIPTION

Electrical distribution networks shall transition to next generation technology in order to

face the challenges of modern grid applications, such as growing energy demand and tight

constraints on operational expenditure. Deployment of network control shall address these

challenges in order to boost efficiency and improve customer satisfaction. Efficient control

and monitoring solutions shall improve power availability, voltage management and asset

management.

The proposed ADMS project shall be a grid modernization project intended to enhance

system practices. The project will cover the design, manufacture, supply, installation and

commissioning of hardware/software equipment and training on a turnkey basis.

Through a combination of SCADA, OMS and DMS techniques, KPLC hopes to achieve

improved performance and reliability of its existing underground and overhead networks

measured quantitatively by industry-accepted Key Performance Indicators (KPI)

automatically derived from the system.

The system shall interface with the existing SCADA (Transmission Grid), via an existing

ICCP link to enable the new system to acquire data from the primary substations.

To ensure timely project execution, evidence of local delivery capacity and organisation

shall be adduced in addition to the proposed solution. Expected coverage region shall be

the Nairobi metropolitan area to start with and later extended to six (6) other major towns.

1.3.1.1 Improved energy efficiency

This shall include:

(a) Reducing impact of network outages (incidents); minimise the number of customers

affected & accelerate supply restoration of the ones that can be re-energized

(b) Reducing technical & commercial losses in the grid

(c) Maintain quality of energy for all consumers (voltage & frequency level)

(d) Balance locally the supply & demand

1.3.2 OVERVIEW OF EXISTING SYSTEM

The system uses DNP3.0 protocol in all its communications while it uses Motorola Data

Link Communications (MDLC) protocol to communicate between the central system and

the front-ends.

The system components in the SCADA are as below:

Load break switches: There exists 150No. Load break switches whose manufacturer is

Delta systems which are remotely controlled from the Nairobi Region control centre

(NRCC).

Ring Main Units: There exists 17No. Lucy Electric RMUs which are controlled from the

NRCC.

Central system: The central system is a PC based Motorola central system running on

Control Maestro.

10 | P a g e

Radio system: There exists a Motorola VHF radio system operating on Tx 172MHz, Rx

176MHz with a 25 kHz bandwidth. The system has a single repeater site in Electricity

House at the heart of the city.

Field RTUs: There exists Motorola ACE 3600 RTUs per node in the circuit.

The layout of the existing SCADA system is as below:

Nairobi area control centre

Repeater at Electricity House

RMU site

RMU site

LBS site

LBS site

LBS site

LBS site

LBS site

LBS site

CENTRAL SYSTEM

Fig: 1: schematic representation of the existing distribution automation system in Nairobi

11 | P a g e

1.3.3 PROPOSED ADMS SYSTEM

The proposed ADMS system shall have the architecture as in fig 2 below. Some functions will be

done immediately while others will be done in future depending on the need and availability of

funds. The system shall be a combination of the SCADA, DMS and the OMS systems with a lot

of dependence on the data from GIS, CIS, distribution SCADA, transmission SCADA and AMI.

Fig: 2: block diagram showing the expected ADMS system

Existing system

Proposed system

Network

Planners

GIS (FDB)

CIS (ICS)

TRANSMISSION

SCADA

SCADA/DMS/OMS

DISTRIBUTION

SCADA

AMI

Energy Aggregators

Others

Field

devices

Field

devices

Field

devices

Field

Crew

Network

Operators

Field

devices

12 | P a g e

The hardware arrangement of the central system and the SCADA system shall be as in fig 3 below:

NMS SERVERS APPLICATION SERVERS

COMMUNICATIONS SERVERS

DTS SERVERICCP SERVERS

B/W LASER PRINTER A3 COLOUR PRINTER

DISPLAY

LAN 1

LAN 2

FEP SERVERS

DISPLAY

Repeater siteLBS site

RMU site

Fig: 3: schematic representation of the Proposed distribution management system in Nairobi

13 | P a g e

2 PROJECT ASPECTS 2.1 Main components

2.1.1 SCADA/ADMS building

The control building is existing and in a good condition. There shall be minimal

adaptation works. However, this shall involve all the necessary works for secure and safe

installation of RMUs as stipulated in appendix 14.

2.1.2 SCADA/DMS System

The System shall include functions ranging from conventional SCADA to elaborated

DMS functions allowing an efficient management of the distribution grid.

The SCADA will monitor & control:

(a) MV feeders

(b) Pole mounted Load Break switches/sectionalizers

(c) Ground mounted Ring Main Units

(d) Auto - reclosers

The proposed ADMS system servers shall be fully-redundant, partially decentralised

and rack-mounted on 42U cabinet (s). The proposed package shall be a well proven

software for industrial and electricity utility applications. The offer shall allow for:-

(i) Real time data collection, database management, real time dynamic data display

(ii) Secure operator supervisory control

(iii)Alarm, event sequence of event management

(iv) Historic collection with real time and historic trending graphs

(v) User based security

(vi) Online configuration

(vii) Single operator station (master) in a secure cubicle

(viii) Configuration of screens and databases

(ix) Software licenses for all pre-installed software and a bootable copy of the same in

DVDs

(x) System integration in the supplier’s country

(xi) Factory acceptance test in the supplier’s country

(xii) Commissioning of all the RTUs and all other field devices

(xiii) Documentation

2.1.3 Telecommunications system

There exists a VHF telecommunications system where the repeater site is centrally

located (Electricity House, Nairobi). The proposal is to have the system run on the

lower UHF frequency band to be advised and especially in the band 400-500MHz.

however bidders are not bound by the existing telecommunications infrastructure.

There also exists a Motorola Astro system (APCO 25) which is currently being used for

radio trunking (voice) which has a capability of carrying data. Its utilization shall be

possible since it has a country-wide footprint. However, bidders shall not be bound to

14 | P a g e

this, and in that case, separate purpose-designed 19” rack mounted data radio

equipment shall be offered for base/repeater station applications.

All the proposed repeater sites shall be fully redundant (N-1).

For the success of this project and due to its intended coverage, tenderers are informed

that there exists at least eight radio towers in the larger Nairobi metropolitan. These

are: Ngong Hills, Nairobi west, Kilome, Ruaraka complex, Mua Hills, Ol Donyo

Sabuk, Roysambu and Babadogo. The masts are between 30m and 50m high.

The communication system shall enhance distributed data acquisition, monitoring and

control system functions. The approach here is to have a core communication controller

in the Nairobi Area Control Centre that can support diverse choices of communication

media e.g. wireless and cable (UTP or fibre optic). This open approach shall facilitate

cost effective implementation.

The Communication controller shall:

i) Have a cross-platform portability

ii) Support functions for communications network management

iii) Permit LAN, Internet, and Intranet connectivity through Ethernet.

All command communication functions shall be invoked through GUI of automation

software. Data transfer between the Control Centre and the RTUs shall support

Distributed Network Protocol (DNP 3.0), and IEC 60870-5-101/104 which are the

industry standard open protocols. Any bidder who proposes a protocol which is not

open shall be automatically disqualified.

UHF/VHF Radio shall be used for communication between the RTUS and the repeater

sites. The data shall then be transferred to the control centre through the same media

or, where applicable, backhauled through fibre optics. The units shall feature excellent

electrical performance providing large signal coverage areas and fast remote unit

polling.

The specifications are as given in the detailed technical specifications.

The typical system shall be based on a Master Station located at the control centre and

at the remote sites which shall be installed inside the RTU enclosures.

2.1.4 Automation Equipment

There exists approximately 200No. ACE 3600 RTUs which shall be part of integration

in the ADMS project. The bidder shall be required to supply additional RTUs for the

pole mounted and Ground mounted switches as specified in the scope of supply.

15 | P a g e

2.1.5 Overhead Load Break Switch/ Sectionalizers

The bidder shall be required to supply about 1,000 Load break switches suitable for use

as points of isolation on the network. These shall be mounted on H-pole structures. If

required, O/H conductor joining shall be done by use of compression sleeves

(specifications given in appendix) so as to avoid introduction of hot spots in the

network. No other forms of joining shall be acceptable.

2.1.6 Integration works

Integration of the existing motorised LBSs and RMUs from phase 1 relevant to the

proposed control system and also integration with the existing systems (GIS system,

smart metering, call manager and transmission SCADA) shall be part of the scope.

2.2 The concept of ADMS

KPLC is modernizing its energy delivery networks and is looking for a solution that

will serve as the "brain" and "nerve centre" governing all aspects of the distribution

network management.

This solution shall be named Advanced Distribution management System (ADMS).

KPLC has progressively started deploying smart meters and ADMS shall fully capture

the benefits of those investments. ADMS shall then offer a wide range of capabilities

that shall support critical business processes during normal and disturbed conditions.

To sum up, the target of this ADMS project is, by using latest digital/information

technologies, to make the grid smart enough to meet the following key goals:

(a) Optimize assets and operate efficiently, reducing the losses and improving the

Key Performance Indicators (SAIDI, SAIFI, ENS, CAIDI etc.)

(b) Anticipate and respond to system disturbances in an efficient manner

(c) Provide the power quality for the range of needs in a more digital economy

(d) Accommodate all future generation options

(e) Enable active customer participation in the future

(f) Operate resiliently against physical and cyber-attack and natural disasters

(g) Enable new products, services and markets

16 | P a g e

3 ADMS REQUIREMENT

The proposed ADMS shall include the real time network monitoring and control of the MV

electrical network portion that is motorized and/or monitored.

All SCADA functionalities shall be available from ADMS user interface. This environment shall

control all aspects of data collection and monitoring, including field device polling, remote

controls and alarm processing.

The SCADA shall contain a full description of telecommunication paths, protocols and

individual device characteristics to enable retrieval, alarm processing and commanding of the

various field devices.

DMS & OMS bricks will be tightly integrated with the SCADA system.

3.1 SCADA

3.1.1 SCADA FUNCTIONAL DESCRIPTION

3.1.1.1 General requirements

This section describes the functions to be performed by the SCADA applications for distribution

system for the project area. Bidders are encouraged to supply standard, proven and tested products

that meet or exceed the Specification requirements. This chapter describes the requirements of

Information Storage and Retrieval (ISR) functions also. Unless specified as optional functions/

features all functions/ features are mandatory for the project area.

3.1.1.2 Design requirements

The software shall be modular in nature. The software shall be able to work platform based on

minimum 64-bit architecture. All the variable parameters of SCADA/DMS applications, which

require adjustment from time-to-time, shall be defined in the database and shall be adjustable by

system personnel. All periodicities and time intervals contained in the Specification that define

these parameters shall be considered as initial values to be used for performance purposes. The

adjustments made to parameters by the user or programmer shall become effective without having

to reassemble or recompile programs or regenerate all or portions of the database. The specific

requirements for output results are described along with the other requirements of each function.

However, all results that the user deems to be important shall be stored in a form accessible for

display and printing, whether or not explicitly specified in the particular subsection.

17 | P a g e

3.1.1.3 SCADA/DMS Function Access

Various application functions shall be designated as single user/ multi-user. For a single-

user function, the user with access to the function shall relinquish access to it before access

can be granted to another user. For a multi-user function any number of users, up to the

maximum designated for the function, may have access to the function simultaneously. All

such actions shall be recorded as events in the event log.

3.1.1.4 Critical and non critical functions

The functions defined in this specification shall be classified as Critical or as Non-critical.

Every critical function shall be supported by sufficient hardware and software redundancy

to ensure that no single hardware and /or software failure will interrupt the availability of

the functions for a period exceeding the automatic transfer time defined in the specification.

Non-critical functions may not be supported by hardware and software redundancy and can

be suspended in case of non-availability of corresponding hardware.

Generally the following shall be classified as Critical functions

(a) All SCADA applications

(b) Information Storage and Retrieval (ISR)

(c) All DMS applications

(d) Data exchange among the contractor supplied SCADA/DMS system

(e) Web server applications , Security applications

(f) Network Management system (NMS)

(g) Data recovery function (DR)

The following shall be Non-Critical functions

(a) Dispatcher Training Simulator (DTS)

(b) Database modification and generation

(c) Display modification and generation

(d) Report modification and creation

(e) Data exchange with Remote VDUs ,if any

3.1.1.5 SCADA Functions

The following SCADA functions are envisaged under this specification.

(a) Data Acquisition from RTUs at S/S , FRTUs at RMUs /Load break switches and FPIs

(b) Time synchronization of RTUs,, FRTUs and FPIs (if time synch is supported in FPI)

(c) Data Exchange among the contractor supplied SCADA/DMS system

(d) Data Processing

(e) Continuous real-time data storage and playback

(f) Sequence of event processing

(g) Supervisory Control

(h) Failsoft capability

(i) Remote database downloading ,diagnostics and configuration

(j) Information Storage and Retrieval (ISR)

(k) Data recovery (DR)

18 | P a g e

3.1.1.6 The System Design Parameters of SCADA functions

The power system sizing, Performance requirements for complete SCADA/DMS system are

specified in DESIGN PARAMETERS AND PERFORMANCE given in appendix 10.

The SCADA system shall have capability to accept data from the following sources:

(a) Telemetered data received from RTUs, FRTUs and FPIs

(b) Data received from the existing KPLC IT system

(c) Data exchange

(d) Calculated data

(e) Pseudo-data (Manually entered data)

All input data and parameters, whether collected automatically or entered by a user, shall be

checked for reasonability and rejected if they are unreasonable. All intermediate and final shall be

checked to prevent unreasonable data from being propagated or displayed to the user.

When unreasonable input data or results are detected, diagnostic messages, clearly describing the

problem, shall be generated. All programs and all computer systems shall continue to operate in

the presence of unreasonable data.

Each of the SCADA functions is described below.

3.1.1.7 Communication protocol.

The SCADA system shall use the following protocols to communicate:

(a) For RTU - IEC 870-5-104 protocol also 101 to communicate when acting as data

concentrator with slave devices.

(b) For FRTU- IEC 870-5-101 /104 protocol

(c) For FPIs - IEC 870-5-101 /104 protocol

(d) For MFTs – MODBUS

(e) For DR and Other any other SCADA system - ICCP/TASE.2 in specified format (OPC /

CIM-XML / ICCP / ODBC Format) Model

(f) For KPLC IT Systems - (in specified format (OPC / CIM-XML / ODBC Format)

(g) The existing Motorola system uses DNP3.0 protocol, the same shall be used for

integration of existing RTUs.

The protocol considerations shall be made in accordance to the system/ device to be interfaced.

However, system shall have capability to interface using all necessary protocols as specified above

for the devices that may be interfaced in future

19 | P a g e

3.1.1.8 Data Acquisition

SCADA system shall acquire data from Remote Terminal Units (RTUs), FRTUs and FPIs

a) RTU and FRTU The type of data to be acquired through RTUs, FRTUs shall include analog values, digital

status data (Double point and single point indications) and SOE data from the substation,

RMUs etc. Analog values like P, Q, F, each phase V, each phase I, each phase pf, and energy

values (Export/Import KWh and KVARh) shall be collected by the RTU, FRTUs from the

MFTs. Analog values such as RTU battery voltage, etc. shall also be acquired through RTU

using analog input modules and suitable transducer

b) FPIs

Digital status in the form of Fault protection indication namely: Overcurrent and Earth fault

and in case also analog data such as Fault settings are remotely. The actual point counts and

type of data acquired are given in the RTU, FRTU specification.

3.1.1.9 Polling method

Digital status data from RTU shall be reported by exception and shall be updated and

displayed within 4 seconds. Digital status data from FRTU and FPI shall also be reported

by exception and shall be updated and displayed within 6 seconds.

Digital status data shall have higher priority than the Analog data. The system shall have

dead band for data by exception. All analog values except energy values shall be reported

by exception from the RTU, FRTU and FPI. The analog value, when reported by exception,

shall be updated and displayed within 5sec from Substation and 10sec from

RMU/Sectionalizer locations at the control centre. An integrity scan of all status and

Analog values shall also be made every 10 minutes (configurable). The provision shall also

be made to report analog values and status data periodically at every 10sec (user

configurable), if required by the user.

The time skew at SCADA/DMS control centre, substations, RMU, FPI shall not be more

than 0.1sec at each location and latency shall not be more than 0.5sec for status. For analog

data the time skew shall not be more than 1sec and latency shall not be more than 1sec for

analog as per IEEE C37.1.

Energy values of 15 minute blocks shall be collected periodically from the RTU, FRTU at

scan rate of 15 minute/1 hour (configurable up to 24 hours). Alternatively, the energy

values shall be calculated for each 15 minute/1 hour blocks at SCADA level from the

acquired energy values of MFTs through RTU and FRTU. The contractor shall assess and

take the network delay into consideration while designing the system so that the update

time in normal and peak level of activities are met.

The SCADA/DMS computer system shall also be able to collect any and all analog and

digital data from its RTUs/FRTU/FPI on demand. Apart from the periodic integrity scan,

the integrity scan shall also be initiated automatically for an RTU/ FRTU/ FPI whenever

the following situations arise:

20 | P a g e

(i) Upon start-up of the system

(ii) RTU/ FRTU/ FPI status change is detected such as RTU/ FRTU/ FPI restart,

Communication Link restoration etc.

(iii)On demand by SCADA/DMS functions

(iv) On request by the user

The TCP/IP Communication for RTU, FRTU and FPI on public network shall be encrypted

over SSL Security / VPN and the equipment shall take control command from designated

Master IP address only and no other IP. The RTU, FRTU, FPI and all TCP/IP devices that

are on Public Network shall form a private VPN network with the SCADA Front End,

through which encrypted data gets exchanged.

3.1.1.10 Telemetry Failure

If data is not received from an RTU/FRTU/ FPI after a user-adjustable number of retries,

each affected point in the SCADA system shall be marked with a ‘telemetry failure

quality code’ and an alarm shall be generated. Telemetry failure of data can be due to

failure of communication link, failure of complete RTU/ FRTU/FPI or RTU/ FRTU

module or MFT etc. Only a single alarm shall be generated if an entire RTU/ FRTU or its

communication channel fails. In the event of telemetry failure, the last good value/status

shall be retained in the database for each affected point.

When telemetry returns to normal, the associated SCADA system shall automatically

resume updating the database with the scanned data. The user shall be able to substitute a

value in the database for any point that is experiencing telemetry failure which shall be

marked with ‘manual replaced’ quality code in addition to the ‘telemetry failure’

quality code. The user shall also be able to delete any point (or entire RTU/FRTU/FPI)

from scan processing. All deleted points shall be marked with a ‘delete-from-scan’ quality

code.

Acquisition Modes The following modes of data acquisition shall be supported:

a) Enable

When RTU/FRTU/FPI is enabled, the data is scanned in normal fashion and control

command execution is allowed.

b) Disable

When RTU/FRTU/FPI is disabled, the data scanning and control execution is disabled.

This is equivalent to” delete from scan “of complete RTU.

c) Test /Maintenance

Placing an RTU/ FRTU in test mode shall generate an appropriate event message.

When an RTU/FRTU is in the test mode, the real-time database shall retain the last

value from all points collected via the RTU/FRTU before it was placed in the test mode.

The points shall be marked in the database with a quality code indicating that their

source RTU/FRTU is in the test mode.

21 | P a g e

All system displays, programs, data links, and other devices shall use this value.

Supervisory control of points that are in the test mode shall not be permitted. When

an RTU/FRTU is removed from the test mode, a message shall be generated, the

test mode quality code shall be removed from all points assigned to the RTU/FRTU,

the database values shall resume updating on each scan, and any controls for the

RTU/FRTU shall be enabled.

3.1.1.11 Time synchronization of RTUs

The SCADA/DMS system will be synchronized from the GPS based Time and frequency

system. The SCADA system shall synchronize the time of all connected RTUs/FRTUs/

FPI every 15 minutes (user configurable from 5 minutes to 24hrs ) using time

synchronization message in the IEC 870-5-104/101 protocol /NTP/SNTP.

The servers /Workstations at SCADA/DMS control centre shall be synchronized using

NTP/SNTP. The time of DR centre shall also be synchronized from the GPS based system

which shall be installed in the SCADA/DMS control centre in the Juja road.

3.1.1.12 Data Exchange

3.1.1.12.1 SCADA/DMS system with IT system

The SCADA/DMS System shall exchange data with ISR System and ISR System

shall be the nodal interface with all IT System. The Data Center and other facilities

under the KPLC IT System, shall exchange data with the ISR System, using Open

Standards.

Direct SQL/ODBC interfaces shall continue to be supported for report generation

and ad-hoc queries. Since KPLC has GIS/ billing/customer system, then interfaces

may be selected accordingly namely ODBC/DDE etc. using ASCII files.

However, they shall provide system in compliance of the data exchange

requirement specified in this para. Data to be exchanged with IT system is defined

in ISR section.

3.1.1.12.2 Data Processing

The SCADA/DMS system shall prepare all data that they acquire for use by the power

system operations and other applications. The data processing requirements shall apply to

data collected from all specified sources.

Data acquired from RTUs/FRTUs/FPI/IT system, as well as data received from the DMS

and the existing control centers (and future), shall be processed and placed in the Real-

Time Database as soon as it is received. Data processing involves a value which has been

converted to internal form and analyzed for violations of limits. The data processing shall

set various data attributes depending on the results of the checks and shall trigger any

additional processing or calculation.

22 | P a g e

The SCADA /DMS system shall prepare all the acquired data for use by the power system

applications. The SCADA system shall have capability to accept data from the following

sources:

(a) Real-time (also referred as telemetered) data received from the control Centres /IT

system (data centre, customer care, DR centre (future) and RTUs/FRTU/FPI etc.)

(b) Calculated data

(c) Manually entered data

(d) Sequence of events data

(e) Alternate data sources

3.1.1.12.3 Analog Data Processing

Analog data processing shall be performed according to the requirements listed

below:

(i) Conversion to Engineering Units

Analog points that are transmitted to SCADA system in raw data format shall

be converted to engineering units before being stored in the database. This

conversion function shall include, as a minimum, the capability to perform the

following conversion algorithm:

Value = (A * scanned valued) + B, Where: A and B are programmer-adjustable constants assignable as database

attributes on a per point basis.

(ii) Zero dead band processing

The SCADA system at control centre shall process each analog input for dead

band zone processing. The acquired value, if falls between the dead band range

around zero then it shall be considered as clamped zero value else the actual

value shall be considered.

(iii) Reasonability Limit Check

The reasonability limits shall represent the extremes of valid measurements for

the point's value. All analog values shall be compared against defined high and

low reasonability limits. The comparisons shall be performed at the scan rates

of the analog values. An alarm shall be generated the first time a reasonability

limit violation is detected. The last valid value of the variable shall be

maintained in the database and marked with a quality code indicating the

‘reasonability limit violation’. When data returns to a reasonable value, the

new value shall be accepted and a return-to-normal message shall be generated.

(iv) Limit Monitoring

For bi-directional quantities (positive or negative) there shall be a set of three

limits for each direction. For unidirectional quantities there shall be a set of

three limits in one direction. These limits will represent increasing levels of

concern and shall be named as "Operational", "Alarm" and "Emergency"

limits. These three limits shall be set within the boundaries of reasonability

23 | P a g e

limit. Generally, any alarm can be assigned as audible alarm but emergency

limit shall necessarily be assigned as audible alarm.

All telemetered and calculated analog point shall be compared against above

sets of high and low limits each time the value is scanned or calculated.

Whenever a monitored point crosses a limit in the undesirable direction a limit

violation alarm message shall be generated.

Whenever a monitored point crosses a limit in the desirable direction, an exit

alarm message shall be generated. If multiple limits have been crossed since the

last check, each limit crossed shall be reported. All limit monitoring shall

preclude annunciation of multiple alarms when a value oscillates about an alarm

limit by utilizing a programmer-adjustable alarm dead-band for each point. The

user shall be able to temporarily override any of the above limits (which are in

use) by entering a new value.

When the user overrides a limit, it shall be marked with a ’limit override

quality code’ on all displays. The override value shall be recognized, and any

display, report, or log containing the value of the overridden limit shall include

it as such. An override value shall be used instead of the permanent value until

the user removes the override condition or system is re-initialized. Any change

in alarm states resulting from a change in limit value shall be reported.

Contractor shall finalize and take approval from utility for limit values.

(v) Rate of change /Gradient

All telemetered and calculated analog points shall be also processed for rate of

change of / gradient processing, if defined that point for such processing in the

database. An Alarm for over shoot and event message for return to normal shall

be generated.

The rate of change shall be calculated periodically for each assigned point, by

dividing the point’s values at the beginning and the end of the period into the

length of the period. Filtering shall be applied so that single scan excursions do

not cause an alarm. The result shall be saved as a non-telemetered database

point. All the requirements that apply to calculated points, such as limit

checking, alarming and availability for display and processing shall apply to the

ROC points. There shall be a positive limit and a negative limit to catch

excessive rises in the analog value.

(vi) Sign Conventions

The sign conventions for the display, data entry and reporting of active and

reactive power flow shall be used universally by all SCADA/DMS functions.

All imports to bus bars shall be represented with +ve sign and all exports from

bus bars shall be with –ve sign.

24 | P a g e

(vii) Accumulator Processing

The system shall be able to store accumulator history. Storing accumulator

history shall be provided with a method in which that stores data only once per

hour and in other method that stores data each time new data enters the system.

It shall be possible to use the two methods concurrently for any pulse

accumulator, making it possible to maintain two records for data that are read

more than once an hour.

3.1.1.12.4 Digital Input Data processing

Each state of a digital input point shall be associated with the state of an actual device. The

number of bits that will be used to define the state of a device is defined in the RTU/FRTU

Specification. A status point shall be defined as being either legal or illegal, and normal or

abnormal.

Illegal state: The first check on a new input to a digital status point is the legality check.

If the new state is illegal, then the old value shall be left in the database and marked old

with relevant quality code such as telemetry failure etc.

Abnormal state: If the new state is legal, it shall be checked to see if it is among the

normal states defined for the point. If not, the status point shall be marked as abnormal.

While abnormal, it shall appear in the summary display of abnormal conditions/ off-

normal summary.

Alarm checking: Each new value shall be checked to see if transitions into that state are

to be alarmed. If so, and if no control action is pending on the status point, then an alarm

action shall be triggered.

The following digital input data types shall be accommodated as a minimum:

(a) Two-state points The following pairs of state names shall be provided as minimum:

(i) Open/Closed

(ii) Tripped/Closed

(iii)Alarm/Normal

(iv) On/Off

(v) Auto/Manual

(vi) Remote/Local

(vii) On Control/Off Control

(b) Three-state points

Any of the state combinations listed in (a) above shall be supported with a third,

typically, in-transit state which is the case for slow operating devices such as isolator.

If a device remains in this state for a period more than a threshold value, the same shall

be alarmed.

(c) Momentary change Detection (MCD)

The input to capture the states of fast acting devices such as auto recloser. Commanded

changes initiated by supervisory control shall not be alarmed but shall generate an event

25 | P a g e

message. All other status changes in the state of telemetered, calculated digital input

points and un-commanded changes shall be alarmed. Each Circuit Breaker (CB),

isolator switching device etc. shall have normal and off-normal positions states defined.

In the event of off-normal positions, the same shall be reflected in the off-normal

summary list

3.1.1.12.5 Calculated Data processing

SCADA system shall be capable of performing calculations and storing the result in the

database as calculated data available for display. The database variables to be used for

arguments and the mathematical/statistical/logical functions to be used as operations shall

be definable interactively at a console as well as by the programmer using database creation

and maintenance procedures. Calculated analog values shall use database points as the

arguments and mathematical and statistical functions as the operations. Functions such as

addition, subtraction, multiplication, division, maximum value, minimum value and

average value, count, integration, square root extraction, exponentiation, trigonometric

functions, logarithms and logical and comparative operators etc. shall be provided. It shall

be possible to calculate running maximum value, minimum value and average value over

a time interval (time interval configurable from 5 minutes to 60 minutes). The value shall

be reset after the elapse of defined time interval. These values shall be stored with time of

occurrence for maxima and minima and the time for averaging.

Calculated status values shall use database points as arguments and combinational logic

functions that include the logical, comparative operators such as AND, inclusive OR,

exclusive OR, NOT, Less Than, Greater Than, Less Than or Equal To, Greater Than or

Equal To, and Equal To ,If , else if etc. Suitable rules or operators (such as multi-level

parentheses) shall be provided to indicate the sequence of operations in the calculation.

3.1.1.12.6 Substation Topology Processing

The SCADA /DMS system shall be provided with a Substation topology processor

function. This function shall be capable of analyzing the open/closed status of switching

devices, such as breakers and disconnectors, in order to define the configuration of the

substation for display. The energization of lines, transformers, bus sections and generating

units shall be determined so that the associated displays may correctly show the status of

these power system elements. The configuration shall be re-evaluated and updated

whenever a switching device status change and analog value change beyond dead-band is

detected.

3.1.1.12.7 Alternate source for data:

The system shall have capability to accept multiple data sources by defining as main and

secondary. Normally, data from normal source will be considered. In the event of non

availability of primary source, data from secondary source shall be considered and once

primary source is healthy, it shall switch back to primary source. There shall be an

indication for primary /secondary source in displays, reports etc. Suitable alarm shall be

generated in the event to change from primary to secondary and vice versa. Alternate

source of data can be defined for certain critical points in the database.

26 | P a g e

3.1.1.12.8 Quality Codes

Quality codes indicate the presence of one or more factors that affect the validity of a data

value. All quality codes that apply to a data value shall be maintained in the database for

that data value. The quality of the calculated value shall be the quality of its "worst"

component of its arguments. The presence of a quality code on any of the component data

values shall not disrupt the calculation using that value. Results of calculations that are

manually overridden by the user shall be denoted with a quality code that can be

differentiated from the propagation of a manual replaced quality code from one of its

component values. At least the following data quality codes preferably as the following

single letter code shall be provided. However, distinct symbols /shapes after approval from

employer may also be used.

Quality code Code Reason

Telemetry Failure (RTU Link) T Telemetry has failed

Manual Replaced M Manual update

Delete from Scan (RTU/point) D User disabled the scan of the data/point

Questionable data Q Analog values of the de-energized elements

Calculated C Calculated data

Primary /secondary source P/S Primary or secondary source

Alarm Inhibit A Alarm processing is inhibited

Test or maintenance mode X Point is in test /maintenance mode

3.1.1.13 Continuous Real-time data storage and playback

All real-time data (Analog and status) shall be continuously stored in auxiliary memory for

at least two weeks as and when it is received in the SCADA database from the RTUs.

It shall be possible to playback above stored data on single line diagram and network

diagram for a time window of at least 10 minutes (configurable in seconds /minutes) by

defining Start and End date and time. It shall be possible to have tabular and graphical

trends of the stored data. It shall be possible to set a different sampling rate for playback

than the sampling rate for data storage. The users shall be able to select the time window

of interest for archival of data in the ISR system for future retrieval and playback in

SCADA system. This archived data shall be transferable in RDBMS database tables of ISR

system for generation of tabular displays and reports.

27 | P a g e

3.1.1.14 Sequence-of-Events data

Sequence-of-events (SOE) data shall be chronological listings of “status change events

with time stamp” acquired from RTUs /FRTUs/FPIs. The SOE data shall be collected from

all RTUs/FRTU/FPI either in normal polling or periodically/on demand. SOE data

collection shall have lower priority than supervisory control actions and normal data

acquisition. The SOE data collected from different RTUs/FRTU/FPI shall be merged for

chronological listings and stored for subsequent review. At least latest 1000 SOE data shall

be available for display.

The SOE resolution of RTU/FRTU is defined in respective sections for RTU/FRTU.

SCADA/DMS system at control centre shall have 1ms SOE resolution. However, as SOE

time stamping is done at RTU/FRTU/FPI level, the same shall be in line with resolution

defined for RTU/FRTU/FPI. All SOE data collected from all RTU/ FRTU/FPIs shall be

stored in daily RDBMS database of ISR system.

3.1.1.15 SCADA language

The SCADA system shall have capability to write various programs using IEC 61131-3

SCADA language or C/C++ or any nonproprietary language. It will facilitate user

(programmer) to write various programs/ logics using points defined in the database.

3.1.1.16 Supervisory Control

The operator shall be able to request digital status control, set-point control and raise/lower

control on selected points and analogs using Select check before operate (SCBO)

Sequence. Supervisory control shall allow the SCADA system to remotely control

switching devices.

A control action shall require a confirmation-of-selection-prior-to-execution response.

Initiation of the control execute step shall occur after the dispatcher confirms that the

correct point and control action have been selected. After the dispatcher/DMS function

initiates control execution, the RTU/FRTU shall be addressed for verification that the

correct point has been selected at the RTU/FRTU and then the control action shall be

executed. It shall also be possible to reset the flag in FPI through a command.

It shall be possible to issue control commands as a group control from SCADA where

switching devices pertaining to different RTUs/FRTU or a RTU/FRTU may be controlled

as a group. The SCADA system shall send the control commands sequentially (without

dispatcher intervention), if the commands pertain to switching devices in the same

RTU/FRTU, using the Selection Check before operate (SCBO) of prior–to-execution. The

control commands pertaining to different RTUs /FRTUs may be executed in parallel. If,

after selecting a point, the user does not execute the control action within a programmer-

adjustable time-out period, or if the user performs any action other than completing the

control action, the selection shall be cancelled and the user be informed.

If the communication to the RTU /FRTU is not available, the control command shall be

rejected and shall not remain in queue.

The user shall not be prevented from requesting other displays, performing a different

supervisory control action, or performing any other user interface operation while the

28 | P a g e

SCADA/DMS system waits for a report-back on previously executed control actions. The

system shall process supervisory control commands with a higher priority than requests for

data from the RTU /FRTU /FPI data acquisition function.

Functional requirements for the various types of supervisory control are given below. A

supervisory control request shall be sent from control centre only after the controlled point

was checked for proper conditions.

The request shall be rejected by the System if:

(i) The requested control operation is inhibited by a tag placed on the device;

(ii) The device or S/S in local manual control mode

(iii)An Uninitialized, Telemetry failure, delete from scan, manual replaced ,

Test/maintenance, or Manually Entered data quality indicator is shown for the device

(iv) The Operating Mode/ user permission of the workstation/console attempting control

does not permit supervisory control

(v) The device is already selected for control request or control execution is from another

workstation / user/window /console or control request is progressing

(vi) Time out after selection

(vii) The device is not subject to supervisory control of the type being attempted

Rejection of a control request from control centre shall occur before any transmission is

made for control purposes. A control rejection message shall be displayed for the

Dispatcher.

3.1.1.17 Digital Status Control

A digital control output results in the activation of an output relay in a RTU. Different

commands shall be possible for these digital status controls. Successful completion of the

control request shall be recorded as an event. Failures to complete shall be handled as

specified in UI section. Control requests shall be canceled and the selection of the point

shall be terminated when the user cancels a request, does not perform the next step of the

control procedure within the selection time-out period from the previous step of the

procedure, or the request is rejected.

a) Breakers

The user shall be able to select and operate the two state controllable switching

device i.e. Circuit breakers/ isolators (in case of RMUs).

b) Capacitor Banks

The user shall be able to control capacitor devices. The procedure for controlling

these devices shall be the same as that of a switching device except that any

supervisory control action shall be inhibited for a programmer-adjustable time

period after the capacitor/ reactor device has been operated. A message shall appear

if an attempt is made to operate the device prior to expiration of that time period

and dispatcher is required to give command after expiration of inhibited time

period.

29 | P a g e

c) Tap Changing Transformers

SCADA system shall have the capability to raise and lower the on load tap position

of the transformers from SCADA control centre through supervisory commands.

Depending on system conditions, the user may raise or lower the tap positions of

On Load Tap Changing (OLTC) transformers. OLTC's tap position need to be

monitored if supervisory control action is to be exercised. OLTC tap position input

shall be acquired as an analog value. Tap excursions beyond user-specified high

and low limits shall cause the master station to generate an alarm. Supervisory

control of OLTCs shall only be permitted when the transformer's control mode is

Supervisory. All attempted invalid control actions shall be rejected. For supervisory

operations, the initial selection and control of the transformer for a raise/lower

operation shall follow the (SCBO) Sequence. Upon receipt of the raise/lower

command, the RTU will immediately execute the control action. It shall not be

necessary for the user to re-select the transformer for additional raise/lower

operations; the user shall only have to repeat the desired number of raise/lower

commands, which shall be executed immediately. Normal scanning functions shall

not be suspended between the times that repeated raise/lower commands are issued.

The user shall be able to cancel the operation or have it automatically cancelled by

the master station after a programmer-adjustable time period elapses after the last

raise/lower command.

This multi-step procedure as described below:

(i) The RAISE and LOWER pushbuttons shall be displayed.

(ii) The command shall be launched as soon as RAISE or LOWER is selected.

The Raise and Lower buttons shall not be replaced by a single Execute button.

The RAISE/LOWER pushbuttons shall continue to be displayed, and it shall

be possible to initiate these controls repeatedly without reselection of the

controlled point, provided that the execution of the previous control command

has successfully been completed.

(iii)The RAISE/LOWER pushbuttons shall remain available until either (a) the

dispatcher clicks the CANCEL button or (b) the control times out due to

inaction by the dispatcher.

(iv) A separate timeout period, adjustable in the range of upto 120 seconds, shall

be provided for incremental control. The timer shall be reset and start

counting again whenever a RAISE or LOWER command is issued.

Successful completion of incremental control shall be recorded as an event.

However failure of incremental control, including failure to achieve the intended

result, shall be alarmed.

d) Set point Control

The SCADA/DMS shall provide the capability to issue set point control using

SCBO procedure to field equipment The SCADA/DMS shall transmit a numerical

value to the device being controlled, to indicate the desired operational setting of

the device.

30 | P a g e

e) Auto execution sequence /Group control

The Auto execution sequence function shall permit multiple supervisory control

commands to be programmed for automatic execution in a predefined sequence.

The dispatcher shall be able to execute this sequence. Commands to be supported

shall include:

(i) Time delayed

(ii) Pause and until a user commanded restart or step execution

(iii)Jump to other sequence on certain conditional logic

(iv) Manual Entry.

After executing a supervisory control action, the SCADA/DMS shall pause to obtain an

indication of a successful control completion check. If the control completion check is not

received, or does not have the expected value, the SCADA/DMS shall terminate the

execution of the sequence and shall declare an alarm. Apart from waiting for control

completion checks, and unless there is an explicit command for a delay, such as a “Pause”

or “Stop” command, the SCADA/DMS shall not introduce any other delays in the

execution of an sequence. No limit shall be placed on the number of Auto execution

sequences, which may execute in parallel. At any time during the execution of a list, the

user shall be able to stop further execution through a CANCEL feature.

f) Control Inhibit Tag

A user shall be able to inhibit or enable supervisory control on any device. A tag symbol

indicating the control inhibit conditions shall be displayed next to the device on all displays

where the device is presented. The programmer shall be able to define up to 4 tag types with

the following attributes for each:

(i) Type of controls that shall be inhibited by the tag (e.g., open only (Green tag) close only

(Yellow tag), open and close (Red tag), or information only - no control inhibit (White

tag). Tags shall be preferably identified by colours. However, distinct symbols /shapes

after approval from employer may also be used.

(ii) Tag priority Further the user shall be able to place at least 4 tags per device. Only the

highest priority tag shall be displayed. Any combination of tags shall be supported,

including multiple tags of the same type. The combined effect of multiple tags shall be to

inhibit a type of control if it is inhibited by any of the tags. When a tag is placed on a

device, the user shall be prompted to enter tag number and comment. An event message

shall be generated each time a control inhibit tag is placed or removed with information

on user ID, type of tag, time of placement or removal of tags.

g) Control Permissive interlocks

It shall be possible to define the interlocks at SCADA level as necessary for control

actions. It shall also be possible for operator to bypass the interlock which shall be

recorded as an event message with user ID information.

h) Control Action Monitor

The response to all control actions shall be verified by monitoring the appropriate

feedback variable. A report-back timer (the duration dependent on the type of

device) shall be initiated when the command is issued. At least ten timer periods of

31 | P a g e

1 to 60 seconds (adjustable in steps of one second) shall be supported, any of which

may be assigned to any device. The user shall be provided with an indication that a

control action is in progress and, subsequently, a report of the result. If the control

was unsuccessful, an alarm shall be generated that states:

(i) The control message exchange was not completed successfully,

(ii) The device failed to operate, or

(iii)The device operated but failed to achieve the desired result (e.g., following

a close control action, a three-state device operates from the open state,

but remains in the transition state).

If the control was successful, an event message shall be generated. For commands

issued as part of a group control, DMS applications etc., the successful completion

of all device control actions shall be reported via a single message. If the operation

is unsuccessful, the user shall be informed of those devices in the group that failed

to operate.

3.1.1.18 Fail-soft capability

The SCADA system shall be able to manage and prevent system from total shutdown /

crash etc. in the event of system crosses mark of peak loading requirements through

graceful de-gradation of non–critical functions and also relaxing periodicity / update rate

of display refresh and critical functions by 50%.

3.1.1.19 Remote database downloading, diagnostics and configuration:

The SCADA/DMS system shall be able to download database run diagnostics and

create/modify /delete configuration/ parameterization from centralized control centre

locations to RTU/FRTU/FPI etc. using ASDU/ messages of respective protocols or file

transfer.

3.1.1.20 IEC61850, SMART GRID interface, requirements

SCADA/DMS Vendors shall provide IEC, ICCP, OPC or ODBC standard interfaces for

their SCADA System for data and model exchange with IT Systems.

Further, system shall be able to interface with IEC61850 (GOOSE and GSSE Models) and

provide an Independent 3rd Party modeling tool that can support multiple vendor IEC 61850

IED's and create IEC 61850 SCD files.

To enable to Migrate to Smart Grid, the SCADA/DMS Systems shall support the

following:

(i) Security – The SCADA/RTU/FRTU Network has to be secure over SSL secure

layer and should be implemented as a VPN. Secure adapters between end nodes

on public networks should be considered with IPSec or VPN.

(ii) Interface to AMI/AMR System where-by DSM can be implemented over

CIM/XML Interfaces

32 | P a g e

(iii)The SCADA CFE should be able to integrate with Smart Grid gateway that

support ICCP / IEC 61850 / IEC 60870-5-101/104/ DNP3, DLMS and ANSI

C12.18/21 and IEEE C37.118.

3.1.2 Information Storage and Retrieval (ISR)

Information Storage and Retrieval (ISR) function shall allow collection of data from real-

time SCADA/DMS system and storing it periodically in a Relational database

management system (RDBMS) database as historical information (HI) data.

This includes storing of data such as SOE, status data, Analog values, calculated values,

Energy values etc. Programmer shall also be able to set storage mode as by exception in

place of periodic storage. Subsequently, the data shall be retrieved for analysis, display,

trending and report generation.

All stored data shall be accessible from any time period regardless of changes made to

the database after storage of that data (e.g. it shall be possible to retrieve stored data for a

variable that no longer exists in the SCADA/DMS computer system through backups on

storage medias namely tapes etc. and initialize study-mode DMS functions with stored

data on the corresponding power system model).

The addition, deletion, or modification of data to be collected and processed shall not

result in loss of any previously stored data during the transition of data collection and

processing to the revised database. It should be able to compress data, and should have

100% retrieval accuracy. However, the retrieval of compressed historical streams should

be of the same performance levels as normal SCADA retrieval.

The ISR shall be able to interface over OPC, ODBC and CIM/XML to external systems

for analytics. The ISR system shall act as the real interface between SCADA and IT

System, where-by the real-time operational system is not affected with a transaction

processing system like IT, and the IT Integration efforts will not in any way effect the

real-time operationally of SCADA/DMS System.

ISR shall also support ad-hoc queries and define display and report formats for selected

data through interactive procedures from operator workstations. Formatted reports and

responses to user queries shall be presented in alphanumeric or graphical format on either

operator workstations or printers at the option of the user. Procedure definition facilities

shall be provided for activities that will be frequently performed.

SQL-based language shall be used for selecting, retrieving, editing, sorting, analyzing, and

reporting ISR data stored. The selection and sorting criteria shall include time tags and

ranges, station names, point names, equipment types, status values, text string matches on

selected data fields etc. and combinations of these criteria. It shall be possible to reload any

ISR archival media that has been removed from ISR and access the archived data without

disturbing the collection, storage, and retrieval of ISR data in real-time.

33 | P a g e

The ISR system shall also be used for mass storage of data/files such as DMS application

save-cases, Output results of DMS applications, Continuous real-time data of selected

time window etc.

3.1.3 Circuit breaker status Table

The ISR function shall maintain a table in RDBMS database where real-time status

of all Circuit breakers, in case of RMU isolators also along with the associated

quality codes shall be stored. The change of status of any breaker shall be updated

in this table as soon as the change is detected by the SCADA system.

This table shall contain additional information such as date and time of tripping,

cause of tripping, expected duration of outage etc. Some of the causes of tripping

could be Supervisory control by user, Protection tripping, Tripping / closing by

DMS applications. Information on expected duration of outage shall be taken from

schedules for DMS application such as Load shed application etc. For expected

duration of outages due to protection tripping, the same shall be user enterable field.

Such daily tables for two months duration shall be stored on auxiliary memory.

Tables for the previous day shall be backed up to Magnetic tape by the user at

1000hrs daily.

The ISR function shall transfer the information available in the "Circuit breaker

status table" as defined above, to the Contact Centre over CIM/XML Models or

ODBC Adapters / Interfaces.

The complete Circuit Breaker Information shall be transferred to Contact centre on

demand and by exception along with the associated quality codes and additional

information associated with the CB.

3.1.4 Real-time Database Snapshot Tables

At the end of each 5minutes, the following real time snapshot data shall be stored

in RDBMS in Real-time Database Snapshot tables:

a) All telemetered analog values and Calculated values for all tele-metered

analog points (at least maxima and minima with associated time and average

values). Energy values are not envisaged for storage in Data snapshot tables.

b) All status values with time stamp

All the above values as specified above in (a) and (b) shall be stored along with

their associated quality code. The periodicity of the snapshot shall be user

adjustable to include 5, 15, 30, and 60 minutes. Data Snapshot tables shall be

created on daily basis. Such daily tables for two months duration shall be stored on

auxiliary memory. Tables for the previous day shall be backed up to Magnetic tape

by the user at 10AM of every day. The ISR function shall prompt the user through

a pop-up window to inform the user for taking the backup. The pop-up window

shall persist till user acknowledges the same. In addition to that data can be stored

34 | P a g e

on offline storage device. The user shall also be able to initialize the study-mode

power system analysis functions from stored snapshot data.

3.1.5 Hourly Data tables

At the end of each hour information as defined below shall be included in the hourly

data tables, in RDBMS database form:

a) Selected analog values along with their associated quality codes

b) Selected status values along with their associated quality codes

c) Results of hourly calculations for selected analog points (at least maxima and

minima with associated time and average) along with their associated quality

codes.

d) In addition to above a separate hourly energy data table exclusively for energy

values (Export and Import Active and reactive Energy values for each feeder)

shall be created in ISR along with their associated quality codes.

Hourly data tables shall be created on daily basis. Such daily tables for two months

duration shall be stored on auxiliary memory. Hourly data table for the previous

month shall be backed up to Magnetic tape by the user on the 10th of every month.

The ISR function shall prompt the user through a pop-up window to remind the

user for taking the backup. The pop-up window shall persist till user acknowledges

the same.

3.1.6 Missed Hourly Data Storage

The programmer shall be able to independently assign any one of the

following processing for each hourly value to be executed when the value

is missed and cannot be acquired prior to the storage of hourly values.

a) Store zero and a telemetry failure quality code for each missed hour.

b) Store the last good data value, with a questionable data quality code,

for each missed hour.

c) Temporarily store zero with a telemetry failure code for each missed

hour. When the next good hourly value is obtained, divide that value

by the number of hours since the last good value was obtained and

insert this value, with a questionable data quality code, for all hours

with missed data and the first hour that good data was obtained as is

the case for energy values.

3.1.7 Hourly Data Calculations

The programmer shall be able to define calculated values using stored

hourly data and constants as operands. The calculations shall allow the

carry-forward of data from one day, week, or month to the next. The results

of all calculations shall include quality codes derived from the quality codes

of the operands.

The following calculations shall be provided:

(a) Addition, subtraction, multiplication, and division

(b) Summation of an hourly value by day, week, and month: The running

total of the summation for the current day, week, and month shall be updated

each hour and made available for display.

35 | P a g e

(c) Maximum and minimum of a value over a programmer-definable time

period, and the time the maximum or minimum occurred

(d) Average of a value over a programmer-definable time period

3.1.8 Daily Energy Data table

The daily energy data table shall be generated for storage of daily energy values for

15 minute blocks / one hour blocks of a day and shall be stored for each feeder on

daily basis along with quality codes. This daily energy data shall be exchanged with

the Billing system in the KPLC Data centre and DR on daily basis and on demand.

This table shall be created on daily basis.

Such daily tables for two months duration shall be stored on auxiliary memory.

Daily Energy data table for the previous month shall be backed up to Magnetic tape

by the user on the 10th of every month.

3.1.9 Load priority table

ISR system shall maintain a Load priority table. The table information shall be used

by various DMS applications.

3.1.10 SOE data table

ISR system shall maintain SOE data table which shall store the SOE data for

complete distribution system. It shall be possible to sort the table by Time, Date,

Substation name/, feeder/line name, device name etc. using SQL commands. This

table shall be made on daily basis. Such daily tables for two months duration shall

be stored on auxiliary memory. For the purpose of sizing of table, daily four (4)

changes per SOE point may be considered. All CBs, protection and alarm contacts

shall be considered as SOE. Tables for the previous day shall be backed up to

Magnetic tape by the user at 1000hrs of every day.

3.1.11 Data Exchange with Contact centre System

The ISR function shall transfer the information available in the "Circuit breaker

status table" as defined in this chapter, to the Contact centre over CIM/XML

Models, or CIM/XML/ODBC Adapters / Interfaces. The complete Circuit Breaker

Information shall be transferred to the Contact centre on demand or Changed

Information shall be sent along with the quality codes and additional information

associated with the CB.

3.1.12 Data Exchange with GIS system

SCADA/DMS will have model aware adapters to read from GIS network model

repository, and update its own models. The system shall utilize GIS standard or an

IEC 61970 and IEC 61968 compliant interface. Data exchange shall be over

model neutral messaging services and CIM/XML data exchange for real-time or

RDBMS will be used.

The following standards as applicable shall be used to achieve the above

requirements:

36 | P a g e

(i) The Graphic data import from a GIS systems shall support native formats of

GIS systems which shall be potentially used for data import. All

Technological addresses (TAs) shall be automatically assigned within the

system to the tags linking the graphic data to the attribute data in the GIS, the

attribute data shall be loaded into the SCADA data base and the display

diagrams shall be generated.

Suitable GIS interface adaptor to enable the compatibility with GIS software/

data format /model shall be provided. The Graphic data import from a GIS

systems shall support native formats of GIS systems which shall be potentially

used for data import. The data shall be transferred on global and incremental

basis on manual request and automatically, once in a day.

The DMS shall automatically move elements that overlap one another in

congested areas so that the operator can clearly see each segment of the

network in the geographic view. In addition, the system shall automatically

move and scale annotation text that come from GIS so that it is visible in the

user's current display SCADA/DMS in the geographic view.

The system shall include tools to edit annotations /text and symbology

placements in geo–referenced displays, substation and distribution network. It

shall be possible to import related reference layers such as streets, buildings,

poles etc. and other background information.

All Technological addresses (TAs) shall be automatically assigned within the

system to the tags linking the graphic data to the attribute data in the GIS, the

attribute data shall be loaded into the SCADA /DMS database and the data /text

shall be displayed on SCADA/DMS diagrams if viewed in GIS mode shall

display GIS in background with zoom, pan, scaling and UI navigation

techniques in synch with SCADA/DMS system displays.

The GIS Network Model shall be exported to the IT and SCADA/DMS Systems

over CIM/XML Models using open GIS standard (shape file format). This

model repository will be the single model authority for the entire Utility

network to be used by both IT and SCADA/DMS Systems. This repository is

maintained by the GIS System, and will be used by SCADA/DMS and other IT

Systems for getting network information, customer and interconnection

information.

3.1.13 Historical Information (HI) Data Retrieval

The data stored in the ISR system shall support the following retrieval

capabilities:

(a) The user shall be able to view and edit HI data on displays/Forms and

reports. The user shall be able to edit HI data, request recalculation of all

37 | P a g e

derived values, and regenerate and print any daily, weekly or monthly HI

report for the current and previous month.

(b) The user shall be able to view tabular trend and graphical trend of multiple

data points simultaneously by specifying the start date and time, the end

date and time, and the time period between displayed samples. The

duration of viewable tabular trend and graphical trend could be upto 24

hours. The features of Tabular/graphic trend is mentioned in the

specification for User interface.

(c) The HI retrieval shall expose the ISR Data over ODBC Interfaces /

Adapters.

(d) The retrieval shall provide 100% accuracy and fidelity of data

3.1.14 System Message Log Storage and Retrieval

System message log, which shall consist of the chronological listing of the

SCADA/DMS computer system alarm messages, event messages and user

messages shall be stored for archival and analysis.

Each entry shall consist of time tag and a text containing user and device

identification as displayed on the Alarm Summary or Event Summary displays. The

System message log data storage shall be sized for up to 20,000 entries per month.

System message log data shall be stored in daily tables and shall be available for

minimum two months on auxiliary memory. System message log data for previous

months shall be backed up on Magnetic tapes by the user for which ISR function

shall prompt the user every hour with suitable message to remind user for taking

the backup on the 10th of every month. This message shall be disabled once the

backup is taken.

Facilities to sort and selectively display and print the contents of the system

message log shall be provided. The user shall be able to select the display of system

message log entries based upon Alarm type, Events, User generated messages,

Device, and Time period.

3.1.15 Mass storage of data/files

The ISR system shall be sized for mass storage of data/files for at least the

following:

a) 10 save-cases for each DMS application

b) 10 Output results of each DMS applications

3.1.16 Data recovery function (DR)

The DR function shall be a repository of system buildup of the SCADA/DMS software to

be installed. Six months online backup shall be available with all the data i.e. system

buildups shall be available so that the same can be utilized upon setting up newer system

after disaster. The data related to network model of SCADA/DMS control centre shall be

38 | P a g e

sent to the DR servers periodically once a day and upon user request. The data shall be

configured to be sent globally and incremental.

All logs, data model etc. and necessary interfaces that are essential for complete system

build up shall be stored at DR servers. All requisite data which is to be used to build the

system from scratch shall be transferred to the DR servers. An alarm shall be generated

and sent to SCADA/DMS control centre upon attaining user defined threshold e.g. 80%

for storage at the DR servers.

39 | P a g e

3.2 DISTRIBUTION MANAGEMENT SYSTEM (DMS)

3.2.1 DMS Core Functions

All DMS applications shall be developed on the basis of algorithms specialized for

distribution networks that will enable performing both analysis and optimization of operation

and development of the KPLC distribution network.

The system shall be based on a Network Model, and shall consist of a number of mutually

compatible applications, organized as modular libraries. Such organization shall provide

simple individual upgrading, extension with new applications and adjustment to any future

requirement.

The DMS system shall have a minimum set of functions that is the base for all other ADMS

functions, including the following modules:

(i) Network Model

(ii) Topology Analyzer

(iii)State Estimation

(iv) Load Flow

3.2.1.1 Network Model

Network Model shall contain all data about network topology, connectivity and electrical

definitions of all network elements.

It shall provide on-line mode for execution of functions in real-time in connection with

SCADA system, and off-line mode for execution of functions in simulation mode for

testing and analysis. Network Model shall be based on CIM (Common Information Model).

The Network Model shall have at least the following features:

(i) Single-phase and three-phase presentation of distribution network

(ii) Balanced and unbalanced distribution network support

(iii)Analysis of all voltage levels of the distribution network

(iv) Analysis of topology and generation of the graph of the distribution network on

the basis of switches statuses.

(v) Temporary elements support, such as a cut on a feeder section, adding a jumper,

removing a jumper, adding grounding, adding mobile generators and/or

transformers.

(vi) Simulation of addition of new substations, capacitors, lines, etc. for study case

analysis

40 | P a g e

3.2.1.2 Topology Analyzer

Topology Analyser, based on network connectivity and switchgear statuses, shall

provide actual topology of the network (normal or disturbed) to be used in other

applications.

The main features of topology analysis to be provided shall be:

(a) Locating and marking supply paths of network elements (all sources and flow

directions that supply a point)

(b) Locating and marking all network elements downstream from a selected element

(c) Determining and marking the status of network elements (making distinction

among energized and de-energized network elements, switchgear statuses, etc.)

(d) Locating and marking networks loops

(e) Colouring by voltage level

(f) Colouring grounded parts of the network

(g) Colouring by active phases (energized status of phases)

(h) Colouring according to the rated current of elements

The function shall be available in both on-line and simulation mode.

3.2.1.3 State Estimation

State Estimation shall estimate the overall network state considering remotely

monitored data and historical data about loads.

State Estimation shall give accurate results for all nodes of the network, including

the ones that are not remotely monitored, i.e. not covered by the SCADA.

As a Distribution State Estimation, it shall consist of the following steps:

(i) Measurement processing, including detection of measurement and

network topology conflicts.

(ii) Pre-estimation – Load Flow calculation is performed for initial root

voltage, loads, generator injection, motor consumption, capacitor status

and set point of voltage regulator.

(iii)Load calibration – Calibration of the estimated total load value of an area

to all customers included in it (in accordance with historical customer load

data), Voltage measurements verification and correction.

(iv) Load Flow calculation – Load Flow calculation for initial or estimated

root voltage, loads and generator injection.

State Estimation (SE) shall be available in real-time and simulation mode. In real–

time mode, SE calculation shall be executed periodically with user–defined period

of time (e.g., every 15minutes) or upon user’s request.

41 | P a g e

3.2.1.4 Load Flow

Load Flow application shall be used for calculating steady states of MV power grids

(networks), as well as state of secondary LV power grids. Load Flow calculation

shall support LV meshed network, so that voltage limit violation and overloaded

elements can be detected in real-time and in “what-if” studies. Load Flow shall

determine the network state variables of unbalanced and balanced networks on the

basis of known root voltage and data regarding consumption (load) of all nodes.

Load Flow is the last step in State Estimation process.

Load flow shall be triggered:

(i) after topology change

(ii) upon user’s request

(iii)periodically

(iv) on set point value change

In order to provide accurate results, load flow shall support:

(i) PQ generators,

(ii) PV generators,

(iii)Local automation and capacitors and HV/MV transformers’ tap changers,

(iv) Consumers’ loads that are voltage dependent,

(v) Transformers’ connections including open connections and Scott

connection, as well as transformers working in parallel

(vi) Transformers with automatic regulation

Load Flow results shall be possible to display next to each network element. Load

Flow report shall also show the quality of the results.

Main outputs of Load Flow application shall be:

(a) Voltage magnitudes and phase angles for all nodes (state vector),

(b) Phase values of current magnitudes and power factors for all sections and

transformers,

(c) Real, reactive and apparent power flows of all sections, transformers,

current transformers, shunts (consumers, generators, motors, and

capacitors) and switching devices,

(d) Losses of real and reactive powers of all network elements,

(e) Voltage drops of all sections in the system,

(f) Estimated statuses (on/off) and generation of capacitors with local control,

(g) Estimated tap changer position of voltage regulating transformers with

local control,

(h) Neutral current of sections,

(i) Maximal current, total real, reactive and apparent power flows and power

factor of transformer banks for transformers and service transformers,

(j) Voltage imbalance on consumers.

42 | P a g e

3.2.2 REAL TIME ADMS FUNCTIONS

3.2.2.1 Network Operation

The proposed system shall provide at least the following functionality to help improve

network operation:

(a) Performance Indices

(b) Temporary Elements

(c) Tracing

(d) Switching Order Management

(e) Work Order Management

(f) Fault Location

(g) Fault Localization

(h) Element Isolation

(i) Supply Restoration

(j) Return to Normal State

(k) Fault Management (FLISR: Fault Location, Isolation, and Supply Restoration)

– automated and non-automated

(l) Large Area Restoration

3.2.2.2 Network Optimization

The proposed system shall help optimize utility assets utilization, maximizing technical

& economical efficiency of the network:

List of required function:

(a) Network Reconfiguration

3.2.3 OFF-LINE ADMS FUNCTIONS

3.2.3.1 Network Analysis

The system shall allow the distribution operators to analyse off-line performance

of the network and the past behaviour of the network in any condition.

List of required functions:

(a) Energy losses

(b) Reliability Analysis

(c) Operational Losses

(d) Fault Calculation among other functions

43 | P a g e

3.2.3.2 Network Planning

One important aspect that the proposed system shall cover is assisting the

distribution operators in the future network development, providing them with data

& tools for optimizing the investments in the network.

List of required functions:

(a) Network Automation

(b) Network planning

3.2.4 DMS FUNCTIONS DETAILED REQUIREMENTS

3.2.4.1 Network Operation

3.2.4.1.1 Network Performance Indices

This functionality shall provide insight into network state and shall offer objective

assessment about the network behaviour, making it easy to determine the potential

changes that may improve network operation.

Performance Indices shall provide a summary of Load Flow results per circuit –

feeder, substation, etc. as well as indication of operational problems (violations of

operational limits – voltage and current) for the considered network state.

In order to facilitate navigation, the results shall be organized by hierarchy, both

electrical (network, supply substation, MV transformer, feeder) and regional

(network, geographic region, geographic sub-region, substation, transformer,

feeder).

Performance Indices shall have capability to run in study mode and in real time

mode.

3.2.4.1.2 Temporary Elements

Temporary elements allow the operator to introduce a limited set of changes to the

electrical model for the purpose of temporarily altering its connectivity. They can

isolate a part of the network being repaired, or re-energize consumers whose supply

cannot be restored by other means (such as executing a switching procedure).

Temporary elements shall be:

a) Temporary cut, which completely or partially (only certain phases) cuts an

overhead line section

b) Temporary jumper, which connects two nodes

c) Temporary grounding, which connects one or more phases of a node to

ground

44 | P a g e

Temporary elements shall be supported in online and simulation mode. The

System shall automatically recognize the topology change upon introducing a

temporary element without need of operator intervention (Topology Analyzer

automatically recognizes topology change, Load Flow automatically

recalculates the part of network where the temporary element is introduced).

3.2.4.1.3 Tracing

Tracing shall provide a visual identification (colouring) of trajectory from certain

point in the network to the supply point (trace up) or downstream to the ends of

feeder (trace down). Additionally, it shall be possible to make trace up towards a

specific device (e.g. breaker) or to an adjacent feeder. This functionality shall be

supported in online and simulation mode.

3.2.4.1.4 Switching Order Management

In order to manage the complex network operations better, the system shall have a

set of tools for creation, display, modification, maintenance, validation, execution

and printing of lists of switching actions, including temporary elements. The

Switching Order will represent an official document, with all necessary information

needed for performing required switching, no matter it is tele-controlled or

manually issued by a crew in the field. The result of a switching order shall

previously be validated by the system before its execution (avoiding limits

violations in the network).

Validations shall be done for each switching (including moving a transformer tap

changer and introducing a temporary element) and could raise a warning or

blocking message.

The status of the different Switching Orders need to be tracked by the user (e.g.

created, pending and partially completed).

3.2.4.1.5 Work Plans

Work plans are created as a response to a work request, either in the control room

or in the field. A work plan shall contain all information related to any work to be

performed in the distribution network in order to satisfy a particular Work Request.

Work plans shall be available in online and simulation mode so it shall be possible

to simulate the work before deciding that the switching plan is good enough to be

executed in the field.

Creation of work plans needs to be possible both:

45 | P a g e

(i) By initiating a new work plan

(ii) By copying an existing work plan

Work plans shall have the following lifecycle states:

a) ‘Planning’ – This is the initial state, meaning that work plan is in process of

creation.

b) ‘Approved’ – Once the work plan is created, it needs to be approved. Work Plan

can be approved even if the switching orders it contains are not approved yet.

Approving a work plan shall automatically run validation.

c) ‘Active’ – After approved, work plan can be activated. This state indicated that

work plan has started and is in progress. Activating Work Plan will trigger

validation automatically.

d) ‘Cancelled’ – This state denotes that work plan is cancelled.

e) ‘Complete’ – Work plan is completed when equipment and devices are returned

to normal state.

3.2.4.1.6 Fault Location

In order to help operators find a fault, the system shall support Fault Location

functionality. It shall determine the smallest possible part of the feeder that contains

the faulty section using appropriate methods.

The proposed system shall support at least the following methods and any

combination of them:

(i) Fault indicator method. The result shall be based on the fault current flow

provided by fault indicators installed in MV network.

(ii) Current method – The result shall be based on the fault type and fault current

measurement reported by relays.

The following information regarding fault location shall be provided as a table and

as a graphical information on single line network view and geographic network

view.

3.2.4.1.7 Number of faulty elements

Faulty element – element with greatest fault location possibility. Element name

with the loop for displaying element position in the network, fault location

possibility, as well as length from the beginning of the section to the position of the

fault are provided.

3.2.4.1.8 Fault Localisation

This shall be provided for determining the minimum area (set of sections) where

the fault has occurred by suggesting sequence of switching operations (executed by

user or automatically) which iteratively leads to the minimum area containing the

fault. Fault Localization can also be used after executing the Fault Location

46 | P a g e

application to additionally reduce the set of fault candidates (if Fault Location result

contains more than one element marked as faulty).

3.2.4.1.9 Element Isolation

The system shall provide an Element Isolation functionality to determine which

switching actions are needed for isolating a selected element.

The function shall give the possibility to isolate one or more elements in the

network (line, busbar, transformer, load, and any disconnecting device such as

breaker).

Function result shall be a list of possible switching operations to isolate the desired

device. It shall be possible to export this result to the Switching Orders function.

3.2.4.1.10 Supply Restoration

The Supply Restoration functionality shall help determining an optimal plan of

switching actions for restoring the supply to a de-energized part of the distribution

network. The function shall determine all variants for an alternative supply of the

de-energized part of a feeder.

This function will be used:

(a) During a fault, i.e. after the fault is located and isolated: it determines the

optimal plan for restoration of the healthy part of the network which has been

de-energized after the isolation of the fault.

(b) During planned maintenance: it determines the most appropriate temporary

radial configuration of the network when certain elements are under

maintenance.

The main output of this application shall be a set of switching actions (variants can

be proposed) to re-energize the de–energized part of the network. All variants

which do not produce violations (overloads and other predefined violations) shall

be suggested as a solution.

If none of the adjacent sources has enough capacity to take over the entire load, the

function shall try supplying from two or more adjacent sources and splitting the

island. The first variant which passes the violations check shall be suggested as the

solution (complex variant).

If supplying from two or more adjacent sources (Island splitting) does not result in

variant without violations either, the function shall propose switching action for

transferring the load up to two sources away.

47 | P a g e

If a full restoration cannot be achieved, the function shall suggest partial restoration

which involves dropping of loads according to predefined criteria. The best variant

shall be suggested as the solution.

All possible variants to resupply de-energized part of the network shall be ranked

by user–defined criteria (weighting factors will be available to use multi-criteria

ranking). The final variant to be applied shall be selected by the user.

The following criteria shall be considered in the calculation procedure:

(a) Critical reserve in loading lines,

(b) Critical reserve in loading supply transformers,

(c) Voltage quality.

This function shall have the capability to be executed in study mode and in real

time mode.

The Result of this function, as list of switching operations, could be exported to the

“Switching order” function.

3.2.4.1.11 Return to Normal State

The system shall provide tools in order to determine an optimal plan for returning

a part of the network (e.g. feeder) to its normal state. Normal state can be defined

as:

(a) State during regular network conditions,

(b) State which preceded the planned or unplanned outage.

The User shall be able to select to which state the network shall return. Return to

normal state shall be activated on user's request or automatically when a fault is

cleared or a maintenance work completed.

3.2.4.1.12 Fault Location, Isolation and Supply restoration (FLISR) - non

automated

Fault Location, Isolation and Supply Restoration (FLISR) application shall provide

the optimal action plan in case of a fault on a feeder in distribution networks, in

order to detect, locate, and isolate the fault and restore the supply to the healthy part

of the faulty feeder.

The following functions shall be part of FLISR application:

(a) Fault Location with Fault Localization

(b) Element Isolation

(c) Supply Restoration

(d) Return to Normal State

48 | P a g e

Using this application, it shall be possible to efficiently use all existing equipment

installed in the field in order to minimize the duration of the outage and undelivered

energy and thus improve reliability indices for different feeder configurations with

various levels of protection and automation.

The initial step of FLISR shall be detection of the fault. FLISR shall be able to

detect permanent faults caused by un-commanded breaker/recloser opening.

These can be: phase-to-ground, two-phase, two-phase-to-ground and three-phase-

to-ground short circuits.

FLISR shall encompass the following sub-functions:

(a) Location of the part of the feeder with the faulty network element (e.g. faulty

cable or overhead section) using appropriate methods. These methods shall take

into account all deployed equipment in the distribution system for fault

detection and location.

(b) Isolation of the faulty element from the remaining part of the feeder.

(c) Re-supply of healthy de-energized parts of the faulty feeder.

(d) Return of the network to the state before the fault.

The Result of this function is a list of switching operations which can be exported

to Switching Order function.

This function shall be available in study mode and in real time mode.

3.2.4.1.13 Fault Location, Isolation and Supply restoration (FLISR) –

Automated

The system shall have the capability of executing Fault Location, Isolation and

Supply Restoration (FLISR) in automated mode without need of operator

intervention.

Fault Location, Element Isolation and Supply Restoration shall be executed in

sequence, without user interaction.

The User shall have the capability to select FLISR mode (auto or manual) per MV

feeder. Automatic mode can be applied only on feeders with appropriate remotely

controlled devices for fault location and remotely controlled circuit breaker, re-

closer and other switching devices.

In this mode FLISR automatically executes the required switching operations to

find the fault, isolate the faulty part of the network and resupply the part of the

network which can be safely resupplied, all this without operator’s intervention. In

case of emergency, it is possible to stop the execution of all active automatic

FLISRs.

49 | P a g e

When automatic FLISRs are stopped, their mode changes to manual.

3.2.4.1.14 Large Area Restoration

The system shall provide tools to determine the plan for restoration of large parts

of the distribution network, which remained de-energized after a fault on a supply

transformer or busbar in HV/MV substation.

The function shall provide the list of necessary switching operations for re-

supplying the de-energized parts of network and enable the dispatcher to take role

in restoration process.

The re-supplying shall be performed taking into account the priority of consumers.

Important consumers shall be supplied first and, consequently, the total cost of non-

delivered power/energy is reduced.

This function shall take into account the following criteria in the entire restoration

procedure:

(a) Voltage/current limits.

(b) Status of switchgear (in/out of order).

(c) Remotely controlled equipment.

(d) Priority of consumers.

3.2.4.1.15 Load Shedding

Load Shedding is used for disconnecting loads in the network in case of emergency

situations and different types of disturbances which can occur due to a lack of

generation or due to overload.

The loads to be shed and their priorities shall be entered and modified through

application’s options. Load shedding is meant to increase network reliability by

preventing total network collapse during emergency situations when load exceeds

generation.

Load Shedding shall have the capability to restore loads that have been

disconnected using this function, once the cause for shedding has disappeared.

Load Shedding shall support the fixed mode of operation where the load

disconnection of a group of customers is performed until restoration is requested

by the user.

The defined remotely controlled switches which are not tagged, manually

overridden, or switched to local control shall represent a candidate for shedding

purposes.

The main output of this function shall be a prioritized (according to combined listed

criteria) list of groups of candidates for shedding. The selected option shall generate

a switching order which can be exported to the Switching Orders function.

50 | P a g e

3.2.4.1.16 Integration with a smart metering system – AMI

The information from smart meters is near real time information that will improve

estimation of the real state in the field. In particular, the consumption data received

from these devices will be used off-line by the Load Profile Updater tool, which

will connect to the AMI database on the AMI server, in order to update and improve

the accuracy of the MV/LV substations load profile curves.

These updated load profile curves will enhance the accuracy of the ADMS

functions, such as State Estimation, Load Flow and all other functions derived from

these ones.

The integration of AMI data to ADMS will also bring the following benefits:

(a) The synchronization of accurate consumption data (i.e. load profiles) with

power measurements and power flow calculations will accelerate theft

detection.

(b) AMI will be used by OMS to get status on customer side in real-time (if

supported by AMI); this will facilitate the fault area localization and then

minimize the outages duration.

The integration to the AMI shall be as the figure below whereby the DMS/OMS

shall be integrated through the head-end. Bidders are advised that the Metering

Data Management System (MDMS) is not in place and is in the tendering

process thus provisions for the integration shall be made as well as the

requirements together with the cost. It is expected that by the time OMS is being

commissioned, the MDMS sill already be in place and ready for integration.

The bidder is advised to allow an appropriate open protocol.

51 | P a g e

Fig 3: proposed AMI system architecture

3.2.4.1.17 Integration with a Geographical Information System – GIS

Integration with an external GIS (Indra) shall use open GIS or CIM standard and shall

require a specific adapter and GIS Importer. These shall receive network data model

from the GIS and translate it into the DMS data model. The solution shall be capable

of receiving the whole data model from the GIS (for bulk data import), as well as

incremental model changes in order to provide better performances in everyday

operations. The integration shall be able to import:

i) GIS data and electrical network model available

ii) ADMS Electrical network model approach data quality tests and data

verification

iii) ADMS Electrical network model validation

In case of temporary unavailability of the GIS, a simplified GIS built-in function of

ADMS shall enable to maintain and manage the electrical network model, without

the external GIS.

52 | P a g e

3.2.4.1.18 Network Optimisation

a) Optimal Network Reconfiguration

Optimal Network Reconfiguration (ONR) shall be used for determining the optimal

configuration of the distribution network, i.e. the appropriate location of the MV (11kV &

33kV) switches to be kept open (“Normally Open” switches).

The optimal configuration shall be achieved in accordance with selected optimization

objectives. ONR shall be able to use a single objective or a user definable combination of

objectives. Each objective shall be freely weighted by the user, and it shall be applied on a

user-definable part of a network.

This application shall enable the selection of only the most important switching actions i.e.

the switching actions that bring the highest benefit to the optimization objective.

Selecting only important switching actions shall simplify the changing of the network

configuration and maximise benefits.

Initial conditions for the application of network reconfiguration shall be:

(a) Actual network load

The Objectives shall be selected or combined from the following list:

(i) Minimal active power losses

(ii) Eliminate overloaded parts of network

Optimization procedure shall be constrained with:

(a) Feasibility of switching operations,

(b) Voltage limits,

(c) Current (loading) limits.

The type of switching devices to be included in optimization shall be selectable:

(i) All switching devices.

(ii) Switching devices which can be operated on load.

(iii)Only remotely controlled.

Result of this function is list of switching steps which can be exported to Switching Order

function.

53 | P a g e

3.2.5 OFF-LINE ADMS FUNCTIONS

3.2.5.1 Network Analysis

3.2.5.1.1 Energy losses

Energy Losses (EL) shall provide the overview of realized operational energy

losses in the entire distribution network, or its parts, for network state and

configuration in a selected past time period. EL shall provide total active/reactive

energy injection, active/reactive energy losses, active/reactive energy generation

and active/reactive energy consumption in the selected time period.

Total energy losses are defined as difference between purchased and sold energy.

Energy losses can be divided into technical (copper and iron) and non-technical

(theft, bad metering).

The function shall provide overview of technical losses by:

(a) Entire network,

(b) Supply substations,

(c) HV/MV transformers,

(d) Feeders

3.2.5.1.2 Reliability Analysis

Reliability Analysis shall provide an assessment of network performance in relation

to planned and unplanned outages. The following basic reliability indices shall be

provided:

(a) Load point average failure rate (1/year),

(b) Average outage duration r (h),

(c) Annual unavailability U,

(d) Energy Not Supplied Index – ENSI (equivalent to Expected Energy Not Served

– EENS),

(e) System Average Interruption Frequency Index – SAIFI,

(f) System Average Interruption Duration Index – SAIDI,

(g) Customer Average Interruption Frequency Index – CAIFI,

(h) Momentary Average Interruption Frequency Index – MAIFI,

(i) Customer Average Interruption Duration Index – CAIDI,

(j) Customers Experiencing Multiple Interruptions – CEMI.

3.2.5.1.3 Fault calculation

Fault Calculation (FC) shall be used for calculation of distribution network state

with fault(s) for a specified network configuration. Quasi-stationary state of the

network, Sub transient and transient periods, as well as steady state shall be

supported.

Considered network topology can be the current one or any topology that is of

interest (especially so called ‘critical topology’ where values of fault current are

maximal). Checking different scenarios shall also be available.

54 | P a g e

Fault Calculation shall be able to calculate the network state for a specified fault at

fault location, as well as along the fault path. It shall also identify the main fault

current trajectory. For a given fault location, all trajectories to the transmission

network shall be marked, as well as trajectories toward distributed generators.

Generator trajectories shall be marked differently from the ones toward

transmission network.

Calculation shall be performed in phase, as well as in sequence domain.

The following types of faults shall be supported in FC:

(i) Phase–to–ground short circuit,

(ii) Phase–to–phase short circuit,

(iii) 2–phase–to–ground short circuit,

(iv) 3–phase–(to–ground) short circuit,

(v) Calculation of maximum and minimum short circuit current.

The following FC outputs shall be provided:

(a) Currents on the fault location,

(b) Voltages on the fault location,

(c) Thevenin equivalent seen from the fault location (optional),

(d) Voltages for all buses in the distribution network part affected by the fault,

(e) Currents for all elements (sections, transformers, distributed generators etc.) in

the distribution network part affected by the fault,

(f) Identification of main and secondary fault current path(s):

(g) Main path presents the path from the fault location to one or more supply points

from the transmission network,

(h) Secondary path presents the path from the fault location to the distributed

generator(s) (in the presence of distributed generation).

3.2.5.1.4 Historian analysis/reports

The ADMS historical system (ADMS historical server and the corresponding

historical database) shall provide the insight in the activities and events of the

electrical network in the past. The time stamp and the user (i.e. an operator or a

SCADA device) shall be recorded for every activity or event in the ADMS system.

The ADMS historical system shall keep track of all data changes in the ADMS

system. ADMS Historical System shall be used in On-line mode, where the current

network topology and state are stored, and in Simulation-mode for analysis.

Historical system shall be based on SQL solution with ODBC (Open Database

Connectivity).

55 | P a g e

It shall store network model data changes history, events, saved cases and switching

sequences.

Historical events playback shall be possible.

3.2.5.2 Network planning

3.2.5.2.1 Network Automation

Network Automation (NA) application shall be used for simulation of adding new

elements in MV distribution network:

(a) Remotely controlled switches (breakers, reclosers, load break switches),

(b) Fault passage indicators (FPIs)

(c) Fault recorders

(d) Fuses.

The analysis shall include Network Reliability and total cost.

Automation equipment shall be placed on feeders and substations.

The input data of NA shall be the equipment that will be automated. Automation

analysis is performed by adding these equipment in network.

The main output of NA shall be a combination of equipment which have to be

located in the network, depending on a selected scenario. All the variants will be

suggested as solution with Reliability Analysis results and cost of equipment per

combination.

The variants shall be prioritized by user-defined criteria.

56 | P a g e

3.3 OUTAGE MANAGEMENT SYSTEM (OMS)

Outage Management System (OMS) shall be part of the scope of this tender. The OMS system

shall be integrated into the same real-time SCADA/DMS platform.

3.3.1 OVERVIEW OF OMS

Outage Management System (OMS) shall be a set of tools and analytical functions which

network operators (dispatchers) will use to manage network outages (incidents and planned

outages), including trouble call, fault detection, fault location, isolation and supply restoration,

crew management and outage reporting. All operations and comments which occur in this

process are documented in the database.

The OMS shall be designed to support operators at all stages of the outage life cycle.

Records of all outages shall be maintained, providing a convenient central repository of

distribution outage information that could be used to support historical analysis, the calculation

of outage reliability indices, and current real-time operations, such as responding to trouble

calls and interacting with field crews. This information shall form the basis for the statistics

that can be used for planning the repair works and detecting poor functionality of the

Distribution Network elements.

OMS shall provide standard functionality required for resolution of outages, including ADMS

functions and interfaces to other IT systems.

In case of an outage an appropriate outage record shall be created. After closure of the outage

all data shall be stored in a database and available for later outage reports:

(a) Outage Reports: “all outages” or “per outage type” : incidents, scheduled work, load

shedding, operations

(b) Outage Statistics: • SAIFI, CAIDI, CAIFI, CEMI, MAIFI, MSAIFI, ASAI - Average

Service Availability Index, ACI – Average Customers Interrupted, Energy not supplied

(ENS), interrupted customers

OMS shall include:

(i) Network model;

(ii) Real-time topological model with tracing functionality;

(iii) Outage tracking functionality;

(iv) Set of ADMS applications with near-term response in a scalable high-performance

cluster environment;

(v) Incident (job) management, providing flexible workflows matching the utilities'

business procedures for planned and unplanned work, including safety

management/hazards;

57 | P a g e

(vi) Call management, tracking customer trouble calls and utility call-backs, integrating

with a variety of call sources and using calls to predict the outage cause;

(vii) Customer data management, storing the customer personal data used by call

management and directly by the operators, designed specifically for a secure

storage of a large amount of sensitive textual data and providing high performance

research tools;

(viii) Crew management, tracking the mobile crews and providing workflows around

their dispatching, integrating with job/incident management and 3rd party mobile

workforce and GPS navigation systems as an option;

Following permissions shall exist in the OMS:

a. Manage customer data,

b. View customer data,

c. Configure calls,

d. Manage calls,

e. View calls,

f. Configure incidents,

g. Manage incidents,

h. View incidents,

i. Configure crews,

j. Manage crews,

k. View crews.

The following user roles shall exist within the OMS system:

(i) OMS User,

(ii) OMS Operator,

(iii)OMS Administrator,

(iv) OMS Customer Service Representative.

Within the OMS system, the following types of outages shall be maintained and they shall

be treated differently:

I. Unplanned outages,

II. Planned outages,

III. Forced outages,

IV. Load shedding outages.

OMS shall include different network colouring in accordance with different criteria

58 | P a g e

3.3.2 DETAILED DESCRIPTION OF OMS REQUIRED FUNCTIONS

The main components of the Outage Management System (OMS) functionality shall

be:

3.3.2.1 Incident Management

This key component of OMS is responsible for assisting system operators in

efficient dispatching of outages, non-outage problems and all other planned works.

Incident Management shall track the information about power disturbances in the

network and organize the response to the disturbance into a user-friendly, efficient

and safe workflow. The disturbances themselves, together with the information

necessary to complete the business processes around them, will be grouped into

objects named incidents. The incident shall model all problems in distribution

system such as unplanned outage, problem existence, non-outage problems like

lights flickering, planned outage and planned work. Incident Management shall be

tightly integrated with DMS outage processing and work order management,

3.3.2.2 Incident management functions

The list of all active incidents shall be available to the user.

The list of all closed incidents in previous period retrieved from historical database

shall be available in the system.

In incident overview, data regarding incidents in the entire network shall be available.

For supervisors and shift managers in the control room, or even managers accessing

from the corporate environment, incident overview will offer a dashboard of the OMS

aspects of the current state of the distribution system.

It shall be possible to colour part of the network affected by incident by different

criteria:

a. Incident confirmation,

b. Problem existence,

c. Incident type,

d. Incident subtype,

e. Outage time range,

f. Incident status,

g. Incident priority,

h. Nested incident.

Prediction results shall be presented with the upstream protection device which shall

be a candidate for the outage cause, as well as the network part affected by that device,

59 | P a g e

containing a full list of customers. Further candidate devices shall be also stored and

used in case of merging the incidents based on the incoming calls.

3.3.2.3 Call Management

Shall record trouble calls and meter AMI “last gasp” event data. It will keep the

real-time image of the currently active calls, AMI events, and call-backs; manage

the configuration of valid values for call and call-back types, reasons and results;

and archive the closed calls into the historical database. Call Management shall keep

and process a large number of trouble calls in order to support high activity

scenarios, without affecting the performance of the DMS. Processing trouble calls

shall be realized with optimal processing where every single trouble call is not

individually processed, in order to avoid system loading with unnecessary actions.

a) Call management functions

The List of all active customer calls in the system containing the information

important for identifying the problem shall be available. When a call is created

or removed, the list of calls shall be updated automatically.

Call Management shall keep any customer call related data. It shall keep the

real–time image of the currently active calls and call-backs, manage the

configuration of valid values for call and call-back types, reasons and results,

and archive the closed calls into the historical database.

The List of all call-backs created in OMS will be available in the system.

OMS shall process AMI “last gasp” events from smart meters, and shall act

upon the new AMI last gasp events in the configured way (known as stewing),

by starting a workflow which may consist creating a new incident or triggering

a prediction.

3.3.2.4 Customer Data Management

Customer data shall be the main set of inputs to the OMS, since it presents the main

information for connection to trouble call and identification of affected part of the

network. In DMS-OMS environment customer data shall be stored in the Customer

database. This data will be initially migrated from CIS and after initial migration only

incrementally updated via appropriate interface. Customer database shall contain

private customer (non-electrical) data from CIS. Electrical data of the network shall

be stored in the unique network model instance of the system. In order to visualize

customers’ information and customers’ trouble calls, every customer in customer

database will have a SDP (Service Delivery Point) identification which presents

connection between non-electrical customer data and electrical data of the network.

SDP shall present the object of the network model that is linked to.

60 | P a g e

a) Customer data management functions

Complete information about all customers fed from any given point in the

network shall be available in the system as well as a list of all customers with

data about interruptions in the previous period.

Customer data shall be restricted to the users with special permissions to access

it (normally permissions are managed by authorized utility personnel).

Typically these permissions shall be given to call centre users, as well as some

(though not necessarily all) of the operators.

The information stored as part of the customer data management shall include,

but shall not be limited to:

(i) Account ID,

(ii) Account type,

(iii)Additional reference IDs (may include AMI meter ID, or IDs into other

external systems), name (first name in case of persons, company name in

case of businesses) and last name (where applicable),

(iv) Additional contact name (sometimes applicable for businesses),

(v) address (street address, postal code, city, additional location information),

(vi) Contact information (multiple phone numbers, mobile number, fax, email

etc.),

(vii) Contract details

(viii) Connection status (non–payment, etc.)

The Customer Historical Browser shall contain a list of all customers with data

about interruptions in the previous period. The browser shall list affected customers

with appropriate statistic about incidents where those customers were included.

3.3.2.5 Crew Management

This component shall perform all actions related to crews required by OMS user.

Crew Management will store information necessary to track crews, contact them

and assign them to work. Creating and assigning crew profiles (member

qualification, type of truck, etc.) shall be available.

61 | P a g e

a) Crew management functions

i. List of all crews shall be available in the system.

ii. Crew management shall track the information about crew locations, crew

availability, crew members, crew vehicles, and efficiently assist the user for

optimal assignment of crews to planned or unplanned works.

iii. Representation of each crew member shall be associated with his domain

account; therefore field client shall be able to automatically filter each crew

member’s data after his authentication.

iv. List of all crew members shall be available in the system, as well as a

possibility to create a new crew member and define his specific skills.

v. List of all crews shall be presented. Dispatcher shall have quality indicator

displayed together with the GPS coordinates, in order to a have clear

information that the vehicle is not in GPS coverage, or GPS device is

broken, or automatic vehicle location (AVL) service or its integration

adapter is down and see the symbol as stale

More details on crew management and the service suite shall be as detailed

in appendix 17.

62 | P a g e

4 ADMS HARDWARE & SOFTWARE DESCRIPTION &

ARCHITECTURE

4.1 INTRODUCTION

ADMS Software, described within this document, shall provide tools for complete operation,

monitoring and control of distribution networks, operation analysis, optimization and

improvement, maintenance and long-term development together with powerful technical

database and layered architecture.

ADMS Software shall be based on the service oriented architecture (SOA) and shall enable

very simple integration with other standard software and hardware equipment applied in the

environment of electricity distribution (GIS, MDM/AMI, equipment automation, etc.).

The ADMS Software architecture shall follow open architecture standards, applied in the most

industry automation real-time IT systems, as well as in business corporate IT solutions.

4.2 SYSTEM ARCHITECTURE

ADMS Software shall consist of the three different subsystems:

(a) User Interface,

(b) Application (calculation) and

(c) Database subsystems.

4.2.1 User Interface subsystem

This shall contain main user applications which shall be used for command issuing,

calculation requests, running of changes in the model and on the top, to be used for retrieving

data for presentation purposes.

4.2.2 Application subsystem

This shall include different software services (which shall interact among themselves) and

respond to both user requests and field device changes.

4.2.3 Database subsystem

This shall be consisted of a relational database (RDB) server and a high speed time-series

data server.

The system architecture shall be consisted of distinct environment which shall be dedicated

to real-time, network model building and testing, off-line analysis and planning purposes and

a training simulator.

A demilitarized zone (DMZ) shall be used as a perimeter network segment logically placed

between two security zones, with the aim to prevent network traffic from passing directly

between the corporate and operational network. ADMS DMZ architecture shall use firewalls

63 | P a g e

placed between two networks to disable external users to directly access the operational

environment. Web servers to provide access to web users shall be placed in this zone.

All critical servers shall be redundant in hot/standby configuration. These are Production

zone servers (domain controllers, SCADA/DMS/OMS, Historian) and DMZ zone servers

(domain controllers, SCADA/DMS/OMS, Historian, WEB servers).

4.3 IDENTITY AND ACCESS MANAGEMENT

The ADMS shall integrate with the Microsoft’s Active Directory Domain Service (AD DS) to

provide a scalable, centralized and secure infrastructure for user and access management.

Active Directory enables the ADMS to merge customer business processes, security policies

and technologies to manage digital identities and control resource access.

The ADMS leverages several AD features.

(a) User and group provisioning refers to the creation and management of user accounts

and ADMS specific authorities (security groups),

(b) Account and password policies enable centralized management that are consistently

applied to all computers and users across the whole environment,

(c) LDAP-based data store enables the ADMS to be compatible with any other LDAP-

based security provisioning system,

(d) Mutual authentication is provided through the integrated windows authentication

mechanisms, where the Domain Controller (DC) holds the role of the mutually trusted

third party,

(e) Single-sign on improves user experience, allowing users to access the ADMS

application after login to the domain without the need to re-enter their username and

password,

(f) Role-based access control model enables flexible user rights configuration that can be

adapted to a customer’s organizational role structure.

4.3.1 Area of responsibility

Area of Responsibility (AOR) is a concept introduced to control user access based on

network regions. To build this access control schema, the ADMS shall define entities called

AOR Area and AOR Group. AOR information of the network objects comes from GIS

system:

(a) AOR Group represents a logical set of closely-related assets or features of assets

(e.g. all equipment in substation that need to be controlled or viewed together.

(b) AOR Areas are used to provide user access rights (view, edit, and control) for a set

of AOR Groups.

64 | P a g e

4.3.2 Real-time (production) environment

This environment shall contain components which will be necessary to provide real-time

information and control of the network. Servers located in this environment shall enable

connection with external real-time systems. Also, real-time calculation and control servers

shall be redundant configured to work in high availability cluster. In that configuration two

identical server nodes shall exist, one being hot and serving the clients and the other being

standby, ready to become hot if the other node fails. The data shall be kept consistent on

both nodes.

4.3.3 Environment for off-line analysis - DMZ

This environment shall contain “near-real time” data provided to parties outside the real-

time environment. Inside this zone shall be ADMS simulation servers for off-line analysis

and planning purposes. One of these servers shall contain replicated state from the real-

time server in the real-time zone. Here could be located the RCS server, which shall be

used for view only access by field crews, and to be connected to the ADMS “power users”

outside of the control room to the ADMS simulation servers.

Besides, here shall be located a Web server, used for thin client application access.

4.3.4 Network model building and testing environment

The environment shall be used for making of all the changes in the model and shall contain

servers for integration with external systems, such as GIS. Besides, here shall be located

servers for model testing and for simulation of operations.

4.3.5 Training simulator environment

Environment for training of new operators. It will be an independent environment with

dedicated servers for training. It will have same user interface as real time zone system.

Trainer will have one workstation on which scenarios for training are being prepared and

saved. Several trainee workstations will be supported. Bidder to state how many can be

supported.

4.3.6 List of Active Users

The ADMS administration shall provide the service to list all users currently logged into

the system (logon time, machine name, client name, organization unit, user account). The

list of active users shall be dynamically updated in real time.

4.3.7 User consoles

Individual users could be attached to specific workstations in the system. It shall be

enabled to specify, for one user, from which workstation will be allowed to login in to

ADMS subsystem.

65 | P a g e

4.3.8 User interface (UI)

User interface applications within ADMS environment have to serve a variety of tasks,

such as data editing, network visualization in form of single-line, logical or geographical

schemes, summary reports and printing, performing complex analyses, etc.

4.3.8.1 Master Interface as a Multi-Windows system

This application shall be a multi-windows system with combination of dynamic mimic

views and text based windows. The displays shall provide information coming from

both real-time measurements and results of ADMS power calculations. Other group of

windows shall be only ADMS related as functionality or interface to specific ADMS

power applications. The last group shall have SCADA related windows that will

provide communications with the SCADA part of the system.

The system configuration shall enable positioning a set of predefined windows and

adjustment of their sizes, saving of such an arrangement and restoring of previously

saved windows arrangement. It will be allowed to make and store different windows

arrangements, and set the default windows arrangement for a group of users. When a

user logs in, the windows arrangement associated to him/her shall be applied.

4.3.8.2 Basic functionalities of the master interface

Main features of the master interface application shall be expressed through the:

Basic UI functionality,

Management of Dynamic Data and

Integration of ADMS Power Functions System.

a) Basic UI functionality

This shall consist of:

(i) Toolbar and menu for access of various options, status bar which displays the

basic data about the currently selected object, and tool tips on the diagram.

(ii) Continuous and dynamic zooming from 10% to 2000%.

(iii)Continuous scrolling and panning of the diagram.

(iv) Selection of the entire network, substation area or a group of feeders. Possibility

to save the selection in a form of a use Favourite.

(v) Selection of different layouts pre-created by the Network Visualiser (for

example, two separate e.g. 33 kV and 11 kV network diagrams).

(vi) Different colouring of the network diagram.

(vii) On-line mode (real-time monitoring and dispatching) and Simulation mode

(off-line analyses of states from saved cases or forecasted states).

(viii) Overview of details (schematic schemes and parameters) of all network

elements.

(ix) Alarming

(x) Finding element by name or ID.

66 | P a g e

(xi) Printing of the diagram (including export into metafile format) or reports.

(xii) Customization of the interface.

b) Management of Dynamic Data

This shall consist of:

(i) Manual updating switches statuses.

(ii) Manual editing measurement values and properties.

(iii)Connection with SCADA sub-system with on-line updating statuses of remotely

controlled switches and values of telemetered measurements.

(iv) Saved cases management.

(v) Time management.

(vi) Action/Event Log including filter possibility, various colours and blinking effects

for alarm/events according to presentation needs

(vii) Printouts with following requirements :

printout of alarms and status changes,

printout of equipment status changes by operator’s action,

Printout on request.

c) Integration of ADMS Power Functions System

This shall consist of:

(i) Editing various options for power functions.

(ii) Mouse-selectable inputs (such as selection of faulted feeder).

(iii)Execution of power functions.

(iv) Displaying results in a user-friendly way, using different colours, numerical

presentation, tags, diagrams etc.

(v) Summary of results in form of reports.

d) Additional Flags, User Notes and Tagging

Additional flags shall be used to enable detailed information about the network

status. They will be shown as symbols in views near to network elements. A user

will be able to assign an additional flag to any network element to denote an outage

or an on-going maintenance for example. Also, notification of severe operating or

service problems, repair assignments etc. could be appropriately displayed by this

way.

Types of additional flags shall be configurable.

User notes (or remarks) and tags on elements shall enable a user to set or amend a

note and associate it with a network element. There would be a possibility to show

all active notes and tags.

67 | P a g e

4.3.9 ADMS Software Reports

ADMS Software shall have comprehensive reporting tool covering all the distribution

network data as well as ADMS functions' calculation results. The pre-set reports shall

include:

(a) single element detailed reports (including or discarding its basic, catalogue,

dynamic and other data),

(b) substation and other objects' reports (including the single-line schematic and

the object's data),

(c) global network reports (including the full logical or geographic diagram),

(d) Function result reports (with table or chart representation of the results).

(e) standard tabular reports

Furthermore, the system shall employ an open database architecture, which will

allow users to access the database through appropriate third-party reporting tool.

Each dynamic change requested from the system (e.g. opening of a switching

device) shall start validation which shall contain different, pre-defined validation

rules.

4.3.10 Schematic/Geographical view

Master interface shall provide both types of distribution network presentation views:

schematic and geographical network views, as well as single line view of all substations,

feeders and all technical data of elements. Multi-layered view will combine functionality

of network display with ADMS Power Functions System, real-time operation and GIS.

The system shall have a rich support for navigation, searching, and selection of network

parts of interest. Practically, with just two mouse clicks, user shall be able to reach even

data about a specific switch from geographic map of the city. Schematic, Geographical and

single line views shall be simultaneously available in different windows. All active views

shall be simultaneously refreshed.

In Geographical view, electric objects shall be drawn on geographical background of the

city area. Geographical view could be used in the same way as schematic view, with

additional advantage to see more information at the screen. Results of all ADMS Power

functions will be available on both geographical and schematic views.

The user-defined bookmarks shall provide easy navigation on the view.

Background objects on the scheme could be organized into the layers. (e.g. "streets",

"houses", "yards" etc.) From the Layers panel, user will be able to show/hide or adjust the

intensity of layers of the scheme. Also, zoom level where the layers appear could be

adjusted. In this way, user will be able to give focus to the area of interest, while still

68 | P a g e

keeping the other objects visible (but pale) for reference. The intensity of colours shall be

transmitted to paper as well when the scheme is printed.

4.3.11 Editing Network Views

4.3.11.1 Creating New View

Geographical network manager shall support tools for creating new network views.

Creating views of all following types shall be supported:

(a) Composite (schematic graphic diagram of parts of the network (by region, by

substation) and the entire electric distribution network)

(b) Geographic (complete graphical diagram of electrical distribution network)

(c) Substation (graphical diagram of a distribution substation, and information

regarding devices within the substation)

(d) Single Circuit (display of the single circuit only)

(e) Internal (view of details, interior view of a feeder object)

(f) Transmission (schematic graphic diagram of electric transmission network)

It shall be possible to link the view to the appropriate substation.

4.3.11.2 Copy View

Geographical network manager shall support copying of the existing network

views. A copied view shall represent a new view with the copies of all electrical

elements from the original views. Copies of electrical elements shall not be linked

to the original elements (they shall represent new electrical objects).

4.3.11.3 Deleting View

It shall be possible to delete a network view in the Geographical network manager.

4.3.11.4 Editing tool

A tool for adding new elements shall be provided. In this window, a list of all

elements for adding shall be presented. The editing tool shall be user-friendly and

support the user in efficient managing of the new elements.

In addition, the editing tool shall support:

(a) electrical editing – editing of the electrical connectivity of network elements

(e.g. adding/removing of electrical objects in the network model)

(b) graphical editing – editing of the existing objects’ graphics (e.g. various views

have the same electrical object presented in different ways – they are all linked

to the same electrical element in the network model)

It shall be clearly indicated to the user which editing is active at any given moment.

69 | P a g e

4.3.11.5 Graphical Properties

Graphical properties shall be assigned to every element. They shall define the

graphical presentation of the element on the network view. The user shall be able

to alter graphical properties of any element at any given time.

In the Graphical Properties the following can be set at the minimum: Size, Angle,

and Symbol.

Graphical Properties shall have a common feel-like look.

4.3.11.6 Electrical Properties

Electrical properties shall be assigned to every element. At minimum, the electrical

properties of all electrical elements shall contain an option to set a catalogue for the

given element. A catalogue shall define the technical data of the element on the

network view. These data shall be used for all the calculations in ADMS system.

The user shall be able to alter electrical properties of any element at any given time.

Electrical Properties shall be characteristic for every element type, however,

electrical properties of all elements shall have a common feel-like look.

4.3.11.7 Managing the elements’ position on the view

Geographical network manager shall support user-friendly tools for managing the

elements’ position on the view:

(a) Rotating

(b) Flipping

(c) Selecting

(d) Moving

(e) Copying

(f) Cutting

(g) Pasting

(h) Deleting

(i) Enlarging/reducing

All of these functionalities shall be available with a single action with a mouse

/toolbar shortcut.

The Geographical network manager shall provide undo and redo features. It shall

be possible to undo any number of changes from the last saving. It shall also be

possible to redo all the changes undone. These actions shall be available with a

single action with a mouse/ toolbar shortcut.

70 | P a g e

4.3.11.8 Committing Changes

The option to commit changes shall be available after any change that has been

made. Prior to saving, all changes shall be validated. It shall not be possible to

commit changes that are electrically incorrect (e.g. adding of the elements on the

view that are not connected to any other elements, connecting element of the lower

nominal voltage level than the supplying transformer upstream, etc.)

After a commit fails, the list of error messages shall be displayed to the user. The

error messages shall not be coded and shall be easily understandable.

4.3.11.9 Adding Remote Points

It shall be possible to manually add or remove signals and remote points for the

selected equipment. For large networks with large number of equipment and

signals, remote points and signals shall be imported automatically.

4.3.11.10 Adding New Elements and their Connectivity

It shall be possible to add new elements using the editing tool.

When the element from the list of available elements is selected, it shall be possible

to edit its graphical and electrical properties.

After an element has been selected and at minimum a catalogue has been assigned

to it, adding of the element on the desired position on the network view shall not

demand more than one action with mouse.

It shall not be possible to add an element on the network view to which a catalogue

(containing necessary technical data about the element) has not been set.

4.3.11.11 Catalogue Editor

Geographical network manager shall support a Catalogue Editor tool for editing of

elements’ catalogues. This tool shall be used for defining electrical properties of

equipment and network basic data. In the Catalogue Editor, a list of all equipment

which contains catalogue data shall be presented, as well as list of basic data

catalogues.

The following equipment shall contain catalogue data:

a) Jumper,

b) Disconnector,

c) Load Break Device,

d) Fuse,

e) Breaker,

f) Sectionaliser,

g) Capacitor,

h) Cable,

71 | P a g e

i) Wire,

j) Line Geometry,

k) Transformer 2W,

l) Transformer 3W,

m) Current Transformer,

n) Potential Transformer,

o) Fault Indicator,

p) Meter,

q) Tag,

r) Note,

s) Remote Unit,

t) Curve.

Basic data shall be defined as the following:

i. Base Voltage

ii. Consumer Contract

iii. Load Group

iv. Message Mapping

v. Custom Type

vi. Line Rating Schedule

vii. Transformer Rating Schedule.

Upon double–clicking on the type of equipment or basic data type, catalogue list

for selected type shall appear.

4.3.11.12 Editing Catalogues

Modifying catalogue data shall be performed by changing values of properties in

the list of available details for the selected catalogue. Five types of these properties

shall be available at minimum:

(a) Properties that consist of strings. These properties shall not affect electrical

calculations (Name, Custom ID, and Alias),

(b) Electrical properties that can be set by checking or un-checking equipment

properties (e.g. fuse is cut-out/fuse is not cut-out),

(c) Electrical properties that can be set by selecting some of the offered values in

the drop down menu (e.g. fuse type),

(d) Electrical properties that are numeric value, and they can be edited by entering

number value, or by gradual decreasing and increasing value (e.g. Rated

Current, Rated Voltage)

(e) Curves – Properties which graphically represent mutual dependence between 2

electrical properties or dependence of some electrical property from time.

It shall not be possible to delete catalogues which are currently used in

Geographical network manager.

72 | P a g e

Catalogue of every element type shall contain the information appropriate for that

element.

The Geographical network manager shall provide tools that disable entering of

wrong information (e.g. if the user specifies the number of phases ‘4’ – the saving

of the given catalogue shall be prohibited). In such case the user shall be presented

with a hint of what information that is entered is wrong and what are the expected

values.

4.3.11.13 Basic Data

Basic data of the network shall also be entered and edited through Catalogue Editor.

Basic Data shall at minimum be organized into following categories:

(a) Base voltages – Values of voltage levels that exist in particular network, with

values of high and low voltage limit, as well as information regarding voltage

level purpose (sub transmission, distribution, or low voltage),

(b) Day type – Type of days classified in groups according to similar daily load

patterns,

(c) Season – Specified time period of the year (e.g., Spring, Summer, Fall, Winter)

in which daily load patterns are similar,

(d) Consumer contract – Provides information regarding consumer priority and

values of high and low voltage levels,

(e) Load group – Consumers which have identical behaviour concerning the shape

(though not necessarily size) of a daily load pattern, load–voltage dependency

and cold pick up characteristic belong to the same group. Consumers which do

not share these properties with others (non–conforming loads) are also assigned

a load group, although they may be the only instance of that group,

(f) Message mapping – Represents a mapping of discrete numerical values to string

values. This is used for explanation of custom signal types,

(g) Custom type – Provides creating of custom types for every type of entity in

model,

(h) Line rating schedule – Represent optional annual schedule of normal and

emergency limits for same type of conductor,

(i) Transformer rating schedule – Represent optional annual schedule of normal

and emergency limits for different type of transformer.

4.3.11.14 Symbol Editor

Geographical network manager shall provide tool for creating and editing of all the

elements’ symbols. A list of all elements shall be provided. List of symbols which

are available for a specific element shall become available after selecting any of the

elements from the list.

Renaming or deleting an existing symbols shall be supported.

73 | P a g e

4.3.11.15 Editing Symbols

The possibility to create a new symbol of any of the elements from the list shall be

provided. It shall not demand more than one action with a mouse / toolbar shortcut.

4.3.11.16 Types of Shapes

Symbol Editor shall support creating of different types of shapes. Appropriate

toolbar shortcuts shall be provided.

4.3.11.17 Managing of the symbol parts’ position

Following tools for managing of the symbol parts shall be supported:

(a) Cut

(b) Copy & paste

(c) Flip

(d) Rotate

(e) Raise/lower of the symbol’s layers

(f) Align symbol parts

(g) Centre

These actions shall not demand more than one action with a mouse / toolbar

shortcut.

Geographical network manager shall support user-friendly tools for setting of the

different shapes’ presentation depending on the state of the element (e.g. blinking

of the symbol of the element that is under an alarm, change of the colour of the

breaker depending on its switch state, etc.)

4.3.11.18 Symbol Profiles

Also, it shall be possible to define different types of symbols for the same type of

equipment, within the same type of view, depending on values of equipment

properties. Therefore, all equipment, depending on which type of view is drawn

and what is the value of its properties, is automatically represented with a specific

symbol.

4.3.11.19 Help

(a) Geographical network manager shall support Help section which describes

included functionality.

(b) Help window shall be opened in a separate window and shall contain a list of

available topics and contents.

(c) It shall be possible to search the Help window by typing a part of relevant

title/text. The Help window shall then jump to the relevant topic.

(d) Help window shall include relevant software screenshots.

74 | P a g e

4.4 ADMS SYSTEM SOFTWARE REQUIREMENTS

General This section describes the characteristics of system software such as Operating system,

RDBMS and support software (programming language compilers, database development and

maintenance, display development, network services, report generation, diagnostics and

backup utilities) to be provided by Contractor and the original software manufacturer as

necessary to support the ADMS applications. This section also describes the standards to be

followed for all supplied software.

4.4.1 Software Standards

All ADMS software provided by the Contractor, including the Operating system, RDBMS

and support software, shall comply with the industry-accepted software standards produced

by national and international organizations, such as ANSI, ISO, IEC, IEEE, ECMA in order

to facilitate maintenance and enhancement of the ADMS systems being supplied.

The Contractor shall commit to meet the "open systems" objective promoted by industry

standards groups by using software products that are based on open standards.

4.4.2 Design and Coding Standards for ADMS applications

All ADMS applications shall be maintainable by the Employer using the supplied software

utilities and documentation. The ADMS software design and coding standards shall also

address the following:

a) Expansion/ scalability: software shall be dimensioned to accommodate the ultimate

size of ADMS system envisaged.

b) Modularity: software shall be modular to minimize the time and complexity involved

in making a change to a program.

c) User-Directed Termination: Functions taking long execution times shall recognize and

process user requests to abort the processing.

d) Programming languages: The software shall be written using ISO or ANSI or ECMA

standard programming languages like FORTRAN, C, C++, and SQL and for Unix

based systems the APIs shall be POSIX-conforming.

e) SOA architecture: Software shall conform to SOA.

f) Portability & Interoperability: The software shall be designed for hardware

independence and operation in a network environment that includes dissimilar

hardware platforms to the extent possible. The use of system services software shall be

built on Open standards

4.4.3 Operating System

The contractor shall use UNIX / Linux / Microsoft Windows™ operating system servers.

The servers based on Unix OS, shall generally comply with the evolving set of POSIX

standards defined by the IEEE.

75 | P a g e

4.4.4 Time and Calendar Maintenance

The ADMS system shall maintain Time and date for use by various software applications.

The GPS based time receiver shall be used for synchronising the ADMS system time. All

Servers and Operator workstation clocks shall be synchronised within the accuracy of +/-

100 milliseconds. The ADMS system shall not be dependent on a particular server for time

/calendar maintenance.

The ADMS shall include two redundant time and frequency standards. Failure of the online

unit shall result in automatic switching to the redundant unit. The ADMS shall periodically

check if the backup unit is operational and failure of either unit shall be alarmed. The

frequency reading shall be accessible by ADMS applications with three post-decimal digits

resolution.

The system shall support communication protocols such as NTP and SNTP. The time and

frequency standard unit shall support a common time code output format such as IRIG-B.

A surge protection system shall be included to prevent the time and frequency standard

equipment from lightning.

4.4.5 Network Software

The network software for ADMS system shall include software for network

communication, security and services.

4.4.5.1 Network Communication

Users and various applications shall be able to communicate within the ADMS local

area network and operate as described in this Specification. The network

communications software shall use a standard network protocol such as TCP/IP. The

software shall link dissimilar hardware nodes, including local and remote workstations,

application servers, communication servers, and various peripherals (such as printers)

into a common data communication network allowing communications among these

devices.

4.4.5.2 Network Security

A user authentication scheme consisting at least of a user identification and password

shall be required for the user to request a connection to any network node.

4.4.5.3 Network services

The following network services shall be provided for the users of ADMS system:

a) Network file management and transfer, for files containing text, data, and/or

graphics information

b) Network printing management

c) Network time synchronization

d) Network backup over LAN

e) Task-to-task communications to external computers

f) LAN global naming facilities.

g) Remote procedure call

h) Remote terminal session

76 | P a g e

4.4.6 Security Services

The security solution shall comprise of comprehensive solution for secured zone Firewalls

i.e. LAN Firewall & Gateway Firewall, intrusion Detection system (IDS) & Strong

Authentication (multi layered), LDAP, Encryption mechanism. The contractor shall

provide a tightly integrated intrusion detection system to detect and prevent intrusion

The following are the functional requirement from the security system:

(a) The system shall have Multilayer (at least network, application layer) firewall

which shall protect the complete system network from unwanted users. Further the

separate firewall shall be provided to take care of the security of all the servers &

shall have High Availability architecture with No Single Point of Failure (NSPOF).

(b) The Gateway Firewall shall be capable of load balancing multiple links from

different service providers.

(c) LAN Firewall shall provide isolation/security services between the subsystems

installed

(d) Firewalls deployed shall not become a bottleneck. It shall be Robust, Secure,

Scalable and future-proof with Centralized Management.

(e) IDS shall be deployed with minimum hardware & they shall not go blind in peak

traffics.

(f) IDS shall have hybrid technology to detect attacks. It shall detect through a

combination of Protocol Anomaly and Signature matching.

(g) Shall have Gateway antivirus which will protect from inflow of virus from the

Internet and other WAN locations at the gateway itself with content filtering

without any lag in data transmission.

(h) Shall have strong authentication containing user name and passwords which shall

be very difficult to compromise.

(i) SSL over VPN to provide secured link over public network such as with

RTU/FRTU/FPI

4.4.6.1 Features

The following shall be the minimum features expected specific to each component of

security system:

i. Firewall

The Firewall shall be hardware box Firewall system with following features.

(a) Firewall speed >250 Mbps

(b) Data encryption supported DES (56bits) 3DES (168bits) and hashing

algorithm like MD5,AES SHA and SHA-1

(c) Encryption to offload the main CPU

(d) It shall have minimum 8 Ethernet 10/100 /1000 ports (4ports for

connectivity to two web servers & 4 Ports for connectivity to LAN

77 | P a g e

(e) Support NAT and PAT

(f) Capability of working in Load sharing and hot standby mode

(g) Denial of service prevention.

(h) DNS guard features

(i) JAVA and ActiveX blocking

(j) Radius integration

(k) Web based management interface

(l) Stateful inspection for web, mail, SQL application etc.

(m) Detailed system logging and accounting feature

(n) No. of concurrent TCP Sessions supported shall be more than 5000.

ii. Intrusion Detection System (IDS)

The bidder shall provide a tightly integrated intrusion detection system capable

for detecting an intrusion attempt that may take place and intrusion in progress

and any that has taken place.

Network based shall have centralized Management Console system which will

be either the application server with NMS or any of the workstation.

The Centralized management console shall have integrated event database &

reporting system & it shall be able to create and deploy new policies, collect

and archive audit log for post event analysis. The system shall have Integrated

Event Database & Reporting System.

Automated Update of the signature for two years shall be provided and there

shall be provision for creating customized signature

iii. Intrusion Detection System (Network Based)

(a) After detecting any intrusion attempt there shall be provision to configure

to perform the following functions:

(b) Capability for Detecting the intrusion attempt that may take place, intrusion

in progress and the intrusion that has taken place

(c) Beep or play a .WAV file

(d) Send an SNMP Trap datagram to the management console. The NMS server

envisaged under the specification shall be used as management console

also.

(e) Send an event to the event log.

(f) Send E-mail to an administrator to notify of the attack.

(g) Save the attack information (Timestamp, intruder IP address, victim IP

address/port, protocol information).

(h) Save a trace file of the raw packets for later analysis

(i) Detect multiple forms of illicit network activity: -Attempted

(j) Vulnerability Exploits -Worms -Trojans -Network Scans -Malformed

Traffic -Login Activity

(k) The System shall support monitoring of multiple networks. The system

shall also support the monitoring of additions or changes to addresses of

devices on the network.

78 | P a g e

The system shall have detection rules for monitoring faults, dangerous and

malicious activity related to IP based protocols. The Contractor shall also apply its

power control and security experience to enhance these detection rules for specific

issues within the system.

iv. Antivirus Server

This shall be used for scanning of viruses. Antivirus shall have Centralized-user

Administration which will communicate directly with centralized user

directories such as LDAP. It shall have all the essential/standard features of

Latest version of Gateway antivirus, some of the features are as follows:

(a) It shall have Policy-based URL filtering and Dynamic Document Review

(DDR).

(b) It shall protect web traffic with high-performance, integrated virus scanning

and web content filtering at the gateway

(c) It shall ensure protection by combining list-based prevention with heuristic

content analysis for both virus protection and web content filtering

(d) It shall eliminate unwanted content and malicious code & Scan all incoming

and outgoing HTTP and FTP traffic etc.

The Security System shall use the best practices to prevent the System itself

from being a source of security compromise. The System shall be hardened,

patched, tested, and designed with security as a primary objective.

Communication with (GUI and notifications) and within (agent reporting and

updates) the System shall use encryption and authentication.

v. Other aspects of security

a) Application Security Monitoring

The standard operating system shall support the monitoring of security on

host installed applications. The system shall support or allow the creation

of monitoring for:

i. Application Software Error Conditions

ii. Application Software Performance Issues

iii. Application Configuration Changes

iv. Application Logins, etc.

b) Security Alarms

The system shall be capable of annunciation, to include audible and visual

alarms whenever a security event takes place and shall support the

following:

i. Instant notification through email or text

ii. Logical grouping of security events by time, location, and device,

etc.

iii. Interactive dashboard window for viewing and acknowledgement

79 | P a g e

c) Analysis and Reports

The system with the stored information, shall be able to produce analyses

and reports to meet security compliance requirements. The system shall be

equipped with best practices ad-hoc reports widely used in the industry. The

employer’s personnel shall be trained to be capable of creating new custom

analysis and reports, and revising existing, without requiring external

consultation.

d) Log Archiving

The security system shall archive, record, and store all security related

events in raw form for at least one year. As a minimum, the event logger

shall record all security related events from the perimeter security devices

and the host IPS. Graphical trend displays of each event shall be available

along with specific information on the type of intrusion, the area affected

and the source via IP address.

e) Data Access through intranet

The Web server at Control Centre is to function as source of information on

the distribution network. It will be accessed by utility intranet user. Any

additional client software, if required, at external clients/users ends, the

same shall be made dynamically available from Web server for its

downloading by these external clients. There shall not be any restriction to

the number of clients downloading this software (i.e. Unlimited number of

client downloads shall be provided). The external users shall be licensed

users of the employer. The following features are required:

(i) The Web servers shall be sized to support at least 50 concurrent external

intranet clients/users for providing access to real-time data.

(ii) External intranet clients/users shall be connected to the web servers

through secure authentication such as VPN access. These users shall be

denied direct access to the ADMS protected LAN.

(iii)Internal ADMS users shall not have any dependency on the availability

of the Web servers.

(iv) For the purpose of transfer of data/displays/ from the ADMS system to

the Web server system, the ADMS system shall initiate a session with

the Web server and any attempt to initiate a session by the Web server

shall be terminated by the Firewall in ADMS system LAN. Interface

between Web server and ADMS zone shall preclude the possibility of

external clients defining new data/Report/Displays. For any sessions

initiating from the DMZ LAN into the protected LAN, the servers shall

be located in a separate DMZ LAN that will be isolated from common

applications connected directly to ISP such as email. The Access to

80 | P a g e

these servers from the external web will be through authorization of

Virtual Private Network.

(v) The web server shall provide access to allowable real time data and

displays, at defined periodicity, for viewing by external clients/users.

The access to each display shall be definable on per user type basis. It

shall be possible to define up to 100 users. Further the ADMS system

administrator shall exercise control over the real-time displays which

can be accessed through the Web server.

(vi) The Web server at Control Centre shall also facilitate exchange of email

messages from ISP (Internet Service Provider) and other mail servers

supporting SMTP.

(vii) Suitable load balancing shall be provided among the web servers

where each shall serve proportionate number of clients. However in case

of failure of one of the servers, all the clients shall automatically switch

to the other web server(s).

Typical displays/pages for Intranet access shall be same as that on the

SCADA/ADMS. Real time SCADA data on web server shall be

refreshed every minute The access to Web server/site shall be controlled

through User ID and password to be maintained /granted by a system

administrator. Further, different pages/data access shall be limited by

user type (i.e. cmd, Mgmt., user, in-charge etc.). The access mechanism

shall identify and allow configuration of priority access to selected

users. Further, tools shall be provided for maintaining the website, web

server configuration, E-mail configuration, FTP configuration, Mailing

lists setup and customer support. Latest protections against viruses shall

be provided.

f) Signature Updating Requirements

The system shall be able to accept timely updates. The updates shall keep

the threat signatures current, providing the latest detection and protection.

The updates shall also incorporate the latest security enhancements into the

Security Management System. These enhancements shall increase security

and functionality, without requiring redesign or reengineering efforts.

g) Network Management system (NMS)

A network monitoring and administration tool shall be provided. The

interface of this tool shall show the ADMS hardware configuration in form

of a map. The network-monitoring tool shall automatically discover the

equipment to construct the map.

It shall support management of multi-Vendor network hardware, printers,

servers and workstations. It shall support remote administration of network

devices, management of thresholds for monitoring performance and

81 | P a g e

generation of alarm and event notifications. It shall be possible to send these

notifications to maintenance personnel through e-mail.

The Network management system shall manage the interfaces to the ADMS

servers, workstations, devices, communication interface equipment, and all

ADMS gateways and routers, switches etc.

The network management software shall be based on the Simple Network

Management Protocol (SNMP-Internet RFC 1157) over TCP/IP (CMOT),

with additional proxy software extensions as needed to manage ADMS

resources.

The NMS software shall provide the following network management

capabilities:

(a) Configuration management

(b) Fault management

(c) Performance monitoring.

The network management software shall:

(i) Maintain performance, resource usage, and error statistics for all of the

above interfaces (i.e. servers, workstation consoles, devices, telephone

circuit interface equipment, and all ADMS gateways, routers etc.) and

present this information via displays, periodic reports, and on-demand

reports. The above information shall be collected and stored at user

configurable periodicities i.e. upto 60 minutes. The Network

Management System (NMS) shall be capable of storing the above data

for a period of one year at periodicity of 5 minutes.

(ii) Maintain a graphical display of network connectivity to the remote end

routers

(iii)Maintain a graphical display for connectivity and status of servers and

peripheral devices for local area network.

(iv) Issue alarms when error conditions or resource usage problems occur.

(v) Provide facilities to add and delete addresses and links, control data

blocks, and set data transmission and reception parameters.

(vi) Provide facilities for path and routing control and queue space control.

4.4.7 Database structure

The ADMS RTDB (Real Time Database) shall be an active process model. i.e. it

shall initiate actions or events based on the input it receives. The RTDB shall

describe the state of the power system at a given point in time and the events that

move the system to a new state at the next point in time. This database is required

to support the data access to real time information and to allow efficient integration

and update.

82 | P a g e

For example, a network model update to introduce a new substation shall not

interrupt the ability to perform supervisory control actions or receive telemetry to

view the network state.

It shall be possible for changes, local or imported, to be placed online either

automatically or under manual control with proper validation. It shall be possible

to easily revert to an earlier database version, again without undue interruption to

network operations. The capability to import & export the CIM compliant network

model data including the corresponding telemetry and ICCP data reference in XML

format to send it to other parties shall be provided.

The capability to import the CIM compliant network model data from other parties

in XML format shall also be provided. The ADMS shall provide a consistent

interface to accept XML format data for updates from other database applications;

and provide a consistent interface to import & export data in XML format.

4.4.8 Software Maintenance and Configuration Tools

General requirements

A set of software shall be provided to enable maintenance of ADMS network model

and system configuration. The following tools shall be available:

a) Report Generation Software

The ADMS system shall include report generation software to generate new report

formats for ADMS and edit existing report formats. The user shall be guided in

defining the basic parameters of the report, such as the report database linkages as

symbolic point names, the report format, the report activation criteria, the report

destination (workstation, printer, or text file), and the retention period for the report

data.

The user shall be able to construct periodic reports and ad-hoc queries via

interactive procedures. The capability to format reports for workstations and

printers shall be provided.

The user shall be able to specify the presentation format for periodic reports and

ad-hoc query reports as alphanumeric display format, graphical display format, or

alphanumeric printer format. The user shall be able to specify that processing

functions, such as summations and other arithmetic functions, be applied to

portions of the report data when the report is processed for display, printing, or file

storage.

The software shall provide for generation of reports that are the full character width

of the printers and that use all of the printer's capabilities, such as font sizes and

styles and print orientation.

83 | P a g e

For report data editing, the user shall be able to obtain the data from a retained

report, modify the data, repeat the inherent data calculations, reprint the report, and

save it in a report retention file on auxiliary memory without destroying the original

report. The user shall also be able to access a retained report, modify its point

linkages to the database, modify its format, and save it in a report retention file on

auxiliary memory as a new report without destroying the original report. Executing

the report generating functions shall not interfere in any server of the system with

the on-line ADMS functions.

b) System backup and restore

The contractor shall provide the complete backup of the ADMS system in

electronic media such as tapes, CDs, etc. Employer personnel shall be able to

restore the ADMS system at site by using above backup tapes/CDs etc. The

contractor shall provide the procedures necessary to restore the system from the

backup tapes/CDs etc. The DR system shall always have the most updated system

build synchronized with the one in the control centre.

c) File Management Utility

File management utilities shall be provided that allocate, create, modify, copy,

search, list, compress, expand, sort, merge, and delete program files, display files,

and data files on auxiliary memory and archive storage.

d) Auxiliary Memory Backup Utility

A utility to backup auxiliary memory of server and workstation files onto a user-

selected auxiliary memory or archive device shall be supplied. The backup utility

shall allow for user selection of the files to be saved based on:

i) Server and workstation

ii) File names (including directory and wildcard designations)

iii) File creation or modification date and time

iv) Whether or not the file was modified since the last backup. A backup

utility that can back up all server and workstation auxiliary memories on

to a single target auxiliary memory or archive device shall be provided.

The backup utility shall ensure that the source auxiliary memory files are

captured properly regardless of caching activity.

e) Failure Analysis Utility

Failure analysis Utility shall be provided to produce operating system and

application program status data for analysing the cause of a fatal program failure.

The failure information shall be presented in a condensed, user-oriented format to

help the user find the source of the failure. The information shall be presented on

displays and recorded for historical records and user-requested printed reports.

84 | P a g e

f) Diagnostic Utility

The system shall have suitable auto-diagnostic feature, online & offline diagnostic

Utility for on-line and off-line monitoring for equipment of ADMS system shall be

provided.

g) System utilisation Monitoring Utility

Software utility shall be provided in each server and workstation to monitor

hardware and software resource utilisation continuously and gather statistics. The

monitoring shall occur in real-time with a minimum of interference to the normal

ADMS functions. The period over which the statistics are gathered shall be

adjustable by the user, and the accumulated statistics shall be reset at the start of

each period. The statistics shall be available for printout and display after each

period and on demand during the period.

h) Other Utility Services

On line access to user and system manuals for all software/Hardware products (e.g.

Operating System and Relational Database Software/hardware) and ADMS

applications shall be provided with computer system.

4.5 GIS –ADMS INTEGRATION

4.5.1 Introduction

Geographical Information System (GIS System) shall manage the geographical

information of the electrical transmission and distribution assets and their circuit

connectivity. The GIS system shall thus be the master from where all electrical network

data, including connectivity and geo-location, will be made available to other systems.

As data is the most critical part of this integration, it needs to be correct and consistent

throughout the different systems. Static data (network) needs to be complete, with all

required fields and connectivity needs to be electrically correct. In this sense the GIS export

tool shall have mechanisms to verify the correctness of GIS data, warning the user in the

cases it is not.

An interface shall be implemented to the GIS system where the master Electrical Network

Model data is maintained to ensure that the integrity of the network data in the ADMS is

maintained. In addition, an interface to other systems that may contain part of the

information needed for the electrical network model shall also be implemented.

Field updates will be made in GIS model first and then have those updates sent as

incremental updates to the ADMS model. Those incremental changes shall be loaded into

a Q&A system to verify the correctness of the new model. Once they are verified they will

be transferred to the operational system so that they are ready to be applied and energized

with an ad-hoc switching plan.

Although the Electrical Network Model will be maintained outside the ADMS, it is

envisaged that additional attributes could be added and maintained inside the system.

85 | P a g e

All modules of the ADMS shall utilize a centrally maintained Electrical Network Model

that shall be CIM-compliant and be able to model HV, MV and LV voltage levels.

There shall be a unique identifier as the key reference point between the two databases

when updating modified, added or deleted equipment. This unique identifier shall be used

in each model to specifically label the same object across each model.

In order to avoid exchanging multiple copies of the same information, all network devices

shall be cataloged, so only a reference to the catalogue shall be sent to provide electrical

parameters of the device.

4.5.2 Network Model mapping

During the GIS – ADMS export / import process, there will be a transformation from one

network model (GIS) to another (ADMS). The export mechanism shall be flexible so it can

handle the differences between both network models mapping network features from one

model to the other.

It is envisaged that the network transformation tool shall be source independent, in a way

that it shall be able to map the network model residing in GIS to a CIM standard network

model.

The vendor shall provide a configuration tool that could allow the user to make

modifications to the network model mapping so that the GIS network model could be

changed and keep the export / import process working.

4.5.3 Information to be exchanged

In order to have a complete and consistent network model in ADMS that can support

network analysis, the system shall be able to import the following information:

(a) Electrical network extracts.

(b) Customer and delivery sites data: The XML export file shall contain the point of

service that shall later be linked to a customer. Customer data and the link to a point

of service will be imported from the Customer database.

(c) Landbase maps: The system shall be able to import landbase maps. The landbase

importer shall be able to generate layers of vector-based maps according to a pre-

defined configuration. The system shall also be able to import raster images as

background maps. Since this data is independent from network model, this step shall

be done independently.

4.5.4 Network Patches

Though integration relying on feeder or circuit extracts can satisfy typical integration of

distribution network model, Planning and Work Order Management may require multiple

changes on different parts of the same MV feeder being prepared weeks ahead and waiting

to be applied in production in near real-time.

The system shall have the ability to import network patches. Network patches are defined

as differences files and their relation with previous model versions.

86 | P a g e

The system shall support at least the following use-cases without a need of configuration:

(a) Attribute update of existing feeder equipment

(b) Adding secondary substation (feeder object) to existing MV feeder

(c) Adding secondary substation (feeder object) at the beginning of the existing MV

feeder (patch is affecting stitching point)

(d) Normal state of two switches is changed such that set of equipment between two

feeders is moved from one feeder to another (load transferring)

(e) A new cable connection is added between stations (feeder objects) and normal state

of a switch is changed

(f) Replacing transformer in station (MV/LV)

(g) Moving feeder to a different feeder head

Network patches changes shall always be applied completely. If a project consists of a

number of patches, those patches shall be applied in the same sequence as they are

energized in the field. The sequence of patch validations shall protect network model

consistency. After a network patch is energized, the affected feeders shall be exported from

the source system in order to guarantee that both systems are aligned.

4.5.5 Default and Missing Values

The system shall have a tool that can default all attributes defined in the CIM circuit profile,

which were not exported in CIM/XML export file. This tool shall reside in the Q&A zone.

Only necessary attributes in ADMS shall be set to default. The vendor shall expect most

of the attributes on the GIS side.

The tool that updates default and missing values shall be able to save its default

configuration to an XML file. It shall enable loading the current configuration and saving

edited configuration, listing the default value rules and viewing/editing the particular

default value rules.

4.5.6 Primary substations model

As the primary substations model are not maintained in GIS with all the details that are

needed for operation, the ADMS system shall have a tool to edit the primary substations

model based on SCADA Single Line Diagrams (in the same way as operators in control

room will expect to see substations).

4.5.7 Model validations and error reporting

The system shall perform different validations in the export/import process from GIS to

ADMS:

a) Electrical model validation:

(i) Whether the XML file is well formed

(ii) Whether the export file is in accordance with the CIM profile, i.e. whether all the

types, attributes and enumeration values are defined in CIM profile

87 | P a g e

(iii) The reference integrity of the file, i.e. whether all references in the file are valid

(iv) If the CIM model validation does not pass, the import shall be aborted and the

user shall be informed.

b) Semantic validation. Check whether the imported data is complete and valid for the

ADMS system

(i) List of all errors with a detailed description shall be provided.

(ii) These errors report shall help data engineers to find and fix them in GIS.

c) ADMS validations (during manual Quality Assurance)

(i) User is responsible for this validation. Load flow and other analysis

convergence validation shall be performed.

In each of those validation points, detailed error reporting shall be provided.

4.5.8 Model promotion

The ADMS system shall provide and implement a process through which changes to the

network data, based on changes to the GIS master data shall be updated in the ADMS

through a controlled and risk-free manner, without any custom code development.

The interface shall support multiple versions of the network model.

Model Promotion (as the process to update the network model in the control room

environment) shall be done in a secure and controlled way, with minimal user interruption.

Model Promotion shall be based on change-sets, allowing for:

a) Multiple users to independently make changes

b) Independent validation of changes

c) Independent promotion of changes

d) Establishing dependency between change-sets as required

e) Rollback of changes in each environment (including Production)

f) Systems to be kept in sync at all times

g) Audit trail kept for each change-set (user, timestamp, description)

4.5.9 Communication mechanism between GIS and ADMS

The communication between GIS and ADMS shall be a one-way communication that shall

be implementable in a point to point communication.

This way, both systems (GIS and ADMS) shall be kept in sync by exchanging error

messages and confirmation of promoted changes. The vendor shall state all the

requirements from GIS provider to make the interface successful.

88 | P a g e

4.6 HARDWARE REQUIREMENTS FOR ADMS

4.6.1 INTRODUCTION

This section articulates the hardware requirements for the ADMS system. The bidders are

encouraged to optimize the hardware for servers where ADMS applications can be

combined or distributed in any combination with adequate redundancy.

However, quantity of servers shall be as per detailed bill of quantities for ADMS. Bidder

shall assess the adequacy of hardware specified in the bill of quantities and if any additional

hardware is required to meet all the requirements of the technical specifications, the same

shall also be included in the offer.

The Bidder shall offer the minimum hardware configuration as specified here for various

equipment, however if required, higher end hardware configurations shall be offered to

meet all the requirements of the technical specification.

The redundant hardware such as servers (Except DTS, development server), CFE, etc. shall

work in hot standby manner.

4.6.2 GENERAL REQUIREMENTS FOR HARDWARE

All hardware shall be manufactured, fabricated, assembled, finished, and documented with

workmanship of the highest production quality and shall conform to all applicable quality

control standards of the original manufacturer and the bidder.

All hardware components shall be new and suitable for the purposes specified. All

hardware such as computers, computer peripherals/accessories etc. and networking

products proposed and implemented shall conform to latest products based on industry

standard. All hardware shall be of reputed make. All servers and workstations shall include

self-diagnostic features. On interruption of power they shall resume operation when power

is restored without corruption of any applications.

The hardware shall be CE/FCC or equivalent international standard compliance. The

specification contains minimum hardware requirement. However, the contractor shall

provide hardware with configuration equal or above to meet the technical functional &

performance requirement. Any hardware /software that is required to meet functional,

performance & availability requirement shall be provided by bidder and the same shall be

mentioned in the BOQ at the time of bid. If not mentioned at the time of bid, contractor

shall provide the same without any additional cost to the Client.

The proposed system shall be designed for an open & scalable configuration, to ensure the

inter-compatibility with other systems of the Utility, the future smooth expansion to other

major towns as well as the easy maintainability. The proposed hardware configuration shall

be extended by adding either CPU processors / memory boards / disks etc. in delivered

89 | P a g e

units or additional units for capacity extension. The configuration of the ADMS shall

comprise a distributed computing environment with an open systems architecture.

The system architecture shall be open internally and externally to hardware or application

software additions, whether supplied by the original supplier of the ADMS or obtained

from third party vendors, both for capacity expansion and for upgrading functionality,

without affecting existing ADMS components or operation.

To be recognized as a true open computer system, all internal communications among the

ADMS Servers and all external communications between the ADMS and other computer

systems shall be based on widely accepted and published international or industry

standards which are appropriate and relevant to the open systems concept or shall have a

field proven acceptance among utilities.

This applies to the operating system, database management system, and display

management system, as well as to APIs providing standardized interfacing between System

software and application software. The bidder shall ensure that at the time of final approval

of hardware configuration/BoQ, all the above hardware are current industry standard

models and that the equipment manufacturer has not established a date for termination of

its production for said products.

Any hardware changes proposed after contract agreement shall be subject to the following:

a) Such changes/updates shall be proposed and approval obtained from Employer along

with the approval of Drawings/documents.

b) The proposed equipment shall be equivalent or with better features than the equipment

offered in the Contract.

c) Complete justification along with a comparative statement showing the original and the

proposed hardware features/parameters including technical brochures shall be

submitted to the Employer for review and approval.

d) Changes/updates proposed will be at no additional cost to the Employer.

4.6.3 HARDWARE CONFIGURATION

In this technical specification, all hardware has been broadly classified as server and

Peripheral device. The term "server" is defined as any general-purpose computing facility

used for hosting ADMS application functions as defined in the specification. The servers

typically serve as the centralized source of data, displays and reports.

The term “Peripheral Device” is used for all equipment other than servers. Peripheral

device includes Operator Workstations, WAN router, LAN, Printer, Time and Frequency

90 | P a g e

system, External Auto loader, External Cartridge Magnetic tape drive, VPS, RTU/FRTU

etc.

4.6.3.1 Servers

The Original equipment manufacturer (OEM) of servers shall be member of

TPC/SPECMARK and can be broadly classified into the following categories:

a) Application servers

ADMS servers

SCADA servers and

OMS servers

Integration server

b) Communication servers

Front End Processor (FEP) server/ Communication Front End (CFE) server

Integration server - Inter control centre communication (ICCP) server.

c) Training & Development system server

Training and Development server

The minimum hardware configuration of the servers shall enable them to process:

(i) Customer data of 8 million customers and above

(ii) Individual points (switches) in excess of 2,000

(iii) Smart meters in excess of 1,000,000

All the servers shall be RISC (Reduced Instruction Set for Computation) or Non RISC e.g.

EPIC/CISC etc.

The bidder shall provide cubicle mounted servers.

The main & standby servers shall be provided with separate cubicles where each cubicle

can be provided with one set of at least a 21” TFT monitor, keyboard and mouse through

a keyboard, video and mouse (KVM) switch with retractable tray.

4.6.3.1.1 Application servers

Redundant ADMS servers shall house ADMS application. Redundant application

shall be provided with common external memory for mass historical data storage

and retrieval. The external memory shall comprise of multiple hot-pluggable type

hard disks configured in RAID configuration. (Except RAID-0).

The external memory shall be connected either directly to the ISR server through

SCSI /SAS interface or directly on the LAN (Network Attached Storage).

91 | P a g e

Alternatively, the bidder may offer RAID with each server to meet the mass storage

requirement in place of common external memory.

The SCADA shall include historical ADMS data storage configured to store

historical data at the storage rates, for at least three years.

Redundant Web / Active Directory Services Server shall host Web Applications for

ADMS LAN and the DNS configuration.

Redundant NMS server shall be provided to host NMS application.

4.6.3.1.2 Communication Servers

The redundant FEP server shall be a functional unit that offloads the task of

communication & pre-processing between RTUs/FRTUS/FPIs & ADMS servers.

All RTUs/FRTUs/FPIs shall be connected to CFE through IEC 60870-5-104/101

link. For the existing RTUs/FRTU/FPI that are to be integrated, interface shall be

available to use the existing protocols.

Free slots shall be made available inside the FEP server, so that additional

communication boards can be plugged-in to meet the network future expansion.

Each channel shall be assigned a different protocol and the Front-End shall be able

to manage several protocols in parallel.

The redundancy of Front-End servers shall allow handling of RTUs/FRTUs/FPIs

connected either through single channel or redundant channels. In both cases, one

FEP server shall be able to take control of all RTUs/FRTUs/FPIs channels.

In order to meet the network’s expansion behind the full capacity of a pair of Front

end servers, it shall be possible to connect additional Front end servers’ pairs to the

LANs. Each communication line shall be able to support its own communication

protocol.

The CFE shall comply with VPN / SSL based security for connecting with IEC

60870-5-104 &101 nodes on public networks. Further, the nodes and CFE shall be

self-certified by manufacturers as NERC/CIP compliant to comply with future

smart grid requirements.

All FEPs shall not have open ports other than needed for protocol traffic / SCADA

traffic, and shall have an audit trace of all login attempts/connection attempts. This

FEP shall exchange data through secured SSL/VPN and encryption of protocol

traffic whether it is a public network or a dedicated one.

The equipment shall take control command from designated Master IP address only

and no other IP. All RTU/FRTU/FPI shall be connected to the ADMS Control

Centre. RTU Communication Card / Module shall support VPN / SSL Security /

Encryption of data coming to it through Public network, and then send over private

& secure Utility network to the SCADA Control Centre. The Communication

92 | P a g e

Servers shall be able to process time- stamped data and can be directly connected

to GPS device for time synchronization

4.6.3.1.3 Inter-Control Centre Communication Protocol (ICCP server)

Depending on the protocol i.e. ICCP used as permissible as per this specification

for, the server shall be called as ICCP or inter control centre communication server.

The redundant ICCP/inter control centre communication server servers shall be

installed in the ADMS control Centre and shall be used to retrieve, transmit and

process data to and from remote sources i.e. remote control Centres.

Data retrieved and processed from remote sources may be stored in communication

servers, which then distributes the data to other servers periodically or on demand.

The server may also be used by utility to exchange data with the other regional

control centres (RCCs).

4.6.3.1.4 Network Management System (NMS) servers

Redundant NMS servers shall be used for configuration management, fault

management & performance monitoring of servers, workstations, routers & LAN

equipment etc. Part of the above functions may be performed by other servers as

per the standard design of offered product.

4.6.3.1.5 Development & Training system (DTS) server

A non - redundant server to host both Developmental applications and Training

applications shall be provided to impart the training.

4.6.3.2 Operator Workstations

The operator Workstation console shall be used as a Man Machine Interface (MMI)

by the despatcher for interacting with all ADMS systems. Operator Workstation

consoles shall also be used as development consoles to take up developmental/

maintenance activities such as generation/updating of database, displays etc. and to

impart training through DTS workstation consoles. Each workstation shall consist

of four monitors & single keyboard and a cursor positioning device/mouse.

Workstation consoles for development system shall also be available with dual TFT

monitor. Operator workstation shall consist of a console driving quad/dual monitors

as defined in the Bills of quantities. The user shall be able to switch the keyboard

and cursor-positioning device as a unit between both monitors of console.

4.6.3.3 Firewall and LAN Network Equipment

The Supplier shall be responsible for providing and configuring 2No. firewalls and

their redundancies as well as data switches plus their redundancies.

93 | P a g e

4.6.3.4 Printers

The Supplier shall be responsible for providing and configuring the 2No. Printers.

These shall be a black and white printer as well as an A3 colour printer. They shall

be accompanied by at least 3No. Cartridges as spares per printer.

4.7 SPECIFICATIONS FOR VIDEO WALL DISPLAY

It shall be an easy to operate, self-contained LCD video wall display for network monitoring.

The video wall shall employ ultra-thin bezel commercial LCD displays with LED back

lighting. This LCD video wall display shall be expandable to grow as KPLC’s requirements

grow.

It shall be easy to assign an individual image to fill each screen, assign multiple images to each

screen, or enlarge an image across the entire screen matrix, or part of the screen matrix.

It shall be possible to build the LCD video wall display with as many screens as space shall

allow.

The video wall shall be accompanied with a video wall cabinetry which shall be designed to

provide easy equipment access while shifting the weight of the displays from the wall to the

floor. It shall be a 2x3 65” LCD Video-wall.

The video wall cabinetry shall be both attached to the wall and also rest on the floor. This shall

be of critical importance because the walls of the existing control building are not constructed

to support the weight of multiple large displays. The base of the cabinet shall be the conduit

for cabling and the storage space for racked electronics. The cabinetry shall be modular,

expandable and easy to relocate.

The LCD video wall shall have the following:

High-definition direct view LCD panels with video processor (controller) and optional

sound settings.

Windows software with wireless keyboard and mouse operation; touch panel control

optional.

Simultaneously display internet, network applications, individual computers, cameras and

TV sources.

Size and move images across the entire video wall matrix with the click of a mouse.

Image processing compensates for bezels; no information is lost.

Modular, expandable and customized to ceiling height and wall space.

Installation and training to the technical staff in the control centre.

94 | P a g e

5 RADIO COMMUNICATION

5.1 APPLICABLE STANDARDS

(i) Radio parameters ETSI EN 300 113-2 V 1.4.1, FCC part 90, RSS119

(ii) EN 301 489-1 V1.9.2 (EMC)

(iii)EN 60950-1:2006/AC:2011 (Safety)

(iv) EN 50385:2002 (Exposure to electromagnetic fields)

(v) EMC (Electromagnetic compatibility) ETSI EN 301 489-5 V 1.3.1

(vi) Electrical safety CENELEC EN 60 950:2001

5.2 GENERAL DESCRIPTION

This shall enable distributed data acquisition, monitoring and control system functions. The

approach here is to have a core communication controller in the Control Centre in Juja road

that can support diverse choices of communication media e.g. wireless and cable (UTP or fibre

optic). This open approach shall facilitate cost effective implementation.

The Communication controller shall have cross-platform portability, shall support functions

for communications network management, and shall permit LAN, Internet, and Intranet

connectivity through Ethernet. All command communication functions shall be invoked

through GUI of automation software. Data transfer from/to RTUs shall support industry

standard data links.

Data transfer between the Control Centre and the RTUs shall support Distributed Network

Protocol (DNP3.0), and IEC 60870-5-101/104 which are the industry standard open protocols.

5.3 RADIO SYSTEM

Radio shall be used for communication between the switches and the repeater sites. Then all

the data shall be transferred to the Control Centre through the same media. The successful

bidder is notified that they will be the ones to advise on the required bandwidth so as to

amicably operate and monitor an excess of 4000 Switches without delay.

They shall also propose the frequency band they shall require to enable KPLC get license from

the Communications Authority of Kenya. The units shall feature excellent electrical

performance providing large signal coverage areas and fast remote unit polling.

The data radio system shall be able to present a transparent data path between a control center

and switches, located at remote sites.

The offered data radio equipment shall be configurable to operate in either Point to Point (PTP)

or Point to Multi-Point (PTMP) modes.

The offered data radio equipment shall comprise fully integrated, all-digital data radio

transceiver, digital data modem and digital data multiplexer functions inside the one unit.

95 | P a g e

Combinations of radio transceivers from one supplier and modems from other suppliers shall

not be permitted.

The offered remote data radio equipment shall be capable of simplex and half duplex operation

with alternate transmission and reception of data.

The offered remote data radio equipment shall be capable of simplex and half duplex operation

with alternate transmission and reception of data. The remote data radio equipment shall also

be configurable for use as a simplex and half duplex store and forward repeater.

In both PTMP and PTP configurations, the base/repeater stations shall be able to operate in

full duplex mode with simultaneous transmission and reception of data.

All radio equipment operating in full duplex mode shall be capable of continuous transmission

(100% transmitter duty cycle) at the maximum power setting and at maximum specified

operating ambient temperature.

The operating temperature range of all offered radio equipment shall be - 40°C to 70°C (-40°F

to 158°F) ambient.

The system shall be 'all digital' with the wireless data modems using highly reliable, full digital

modulation.

The system shall include a collision avoidance mechanism to facilitate multiple remote radios

that require access to the channel. The collision avoidance shall inhibit any remote from

transmitting to the master once the master has commenced receiving data from another remote.

The collision avoidance mechanism will allow a remote site to transmit data to the master while

the master is transmitting data to another remote site.

The collision avoidance shall feature a random delay re-transmission mechanism which avoids

multiple remotes from attempting to transmit simultaneously once another remote has ceased

to transmit data to the master. The system shall include an automatic retry recovery (ARQ)

mechanism which detects a packet lost due to collision or corruption from interference and

resends the packet. The number of retry attempts for the resend shall be user configurable.

The offered data radio equipment shall permit the use of both Carrier Sense (CS) as well as

Carrier and Data Sensing Multiple Access (CDSMA) user selectable collision avoidance

mechanisms.

All data radio equipment offered shall be capable of being configured in a Layer-2 Ethernet

Bridge mode or a Layer-3 IP Router mode. Offers that only include Layer-2 Ethernet mode of

operation will not be accepted.

All offered data radio equipment shall include an embedded MODBUS/TCP gateway that can

be connected on either serial port. External gateway devices are not allowed.

96 | P a g e

Each data radio shall feature, as standard (with no external adaptor), user enabled/disabled

AES 256 bit Encryption with user selectable password/key to avoid unauthorized reception

and subsequent decoding of transmitted data.

The transmitter in all radio equipment shall include a power control circuit with an automatic

power reduction facility to prevent over-heating of the transmitter in the event that the ambient

temperature exceeds the specified maximum.

The automatic power reduction facility shall also be used to protect the radio against damage

due to excessive reflected power (high VSWR).

Each data radio shall be capable of being firmware updated both locally (wire connection) and

remotely (over the radio channel).

a) The over-the-air firmware update feature shall provide a separate software based tool

for managing the update process to ensure that only user selected target radios are

updated.

b) The over-the-air firmware update feature shall be speed limited to prevent RF channel

Congestion. The over-the-air firmware update feature shall broadcast the firmware

update to all of the radios within a system so that radios can be upgraded

simultaneously (multicasting).

c) The over-the-air firmware update feature shall allow for the updating of a single

target radio or all radios in the system.

d) The over-the-air firmware update feature shall update target radios by sending a

firmware patch file where only the difference between the current and target firmware

is transmitted over the air to reduce the over the air transmission of firmware traffic.

e) The over-the-air firmware update feature shall include a security password protection

mechanism to prevent un-authorized firmware updates.

f) The over-the-air firmware update feature shall only update the offline (alternative)

firmware image so that normal radio operation remains in place during the transfer of

new firmware

The offered radio equipment shall have built-in SNTP server & client with user configurable

date/time override.

The system shall include the ability to change data transmission rates dynamically based on the

quality of the radio channel between any two radios.

The dynamic speed operation shall be dynamically variable for each remote radio depending on

the quality of the radio channel at any particular point in time.

The dynamic speed operation shall adapt to how the radio channel changes over time changes the

data transmission speed automatically to ensure that the fastest possible data speed is being

utilized.

All traffic shall be compressed before transmission over the air. Compression level shall be user

configurable to allow a trade-off between latency and compression level. All data radio equipment

97 | P a g e

offered shall include two embedded terminal servers that support the transport of serial traffic from

the two serial ports. The terminal servers shall support UDP & TCP modes.

The data radio equipment shall also include an embedded MODBUS/TCP gateway that can be

connected on either serial port.

External gateway devices are not allowed. IP Address allocation shall include manual and DHCP

modes of operation.

The proposed radio system shall be 100% compatible with the proposed load break switches.

Bidders shall prove this compatibility by a formal letter from vendors assuring the full-

compatibility between the load break switches and radio models proposed.

The typical system shall be based on a Master Station located at the SCADA distribution control

Centre and remote sites which are installed inside the RTU enclosures.

5.3.1 RADIO SYSTEM RATINGS

# Radio features Minimum features Required

BIDDER'S

OFFER

1

General

Configuration Modes PTP and PTMP

Transmission Modes Simplex and Duplex

Level of performance Tx 100% of duty cycle at max

power at max temperature

Collision avoidance

mechanism

Carrier Sense (CS) and Carrier

and Data Sensing Multiple

Access (CDSMA) selectable by

user

Number of retry attempts Configurable by the user

Channel Spacing 12.5kHz and 25kHz user

selectable by software

Frequency Stability 0.5ppm from -40ºC to 70ºC

ambient

Frequency aging <= 1ppm/annum

TX output power 0.05W to 10W configurable by

software

TX Protection Over-temperature and high

VSWQ fold back

TX timeout timer From 0 to 255 seconds

configurable

TX spurious output <= -37dBm

98 | P a g e

RX Mute fully user (software) configurable

digital mute

Data Integrity 16 bit CRC error checking

Data Modulation Rate

Ch

Bandwidth

Data

Rate

10E-6 BER

Sensitivity

12.5kHz 8kbps -113

12.5kHz 16kbps -110

12.5kHz 24kbps -107

12.5kHz 32kbps -100

25kHz 14kbps -111

25kHz 28kbps -109

25kHz 42kbps -106

25kHz 56kbps -99

Modulation Narrow band 2,4,8 and 16-level

continuous phase modulation

Emission type 11K2F1D and 20K0F1D

Diagnostics Tools Web, Telnet, SNMP, external

software

Error Testing In built packet error rate testing

Event Logs In built event log recording

time/date of all critical events

Statistics In built recording of radio

statistics

2

Remote

Radio

Units

Enclosure / Housing Rugged alloy metal

DIN railing mounting As an option

Dimensions 115 x 34 x 164mm

Operating Temperature

range -40ºC to 70ºC ambient

Indicator panel

Visible multimode LED

indicators for DC power,

transmit, receive, synchronized

data, serial interface 1 & 2

transmit & receive data, Ethernet

1 & 2 transmit & receive data.

Nr of Ethernet ports 2

Ethernet type 10/100Mbps

Filtering methods

User configurable: No Filtering /

Unicast Traffic & ARP Only /

Unicast Traffic Only /

List of approved MAC addresses

99 | P a g e

Time server

Built in SNTP server & client

with user configurable date/time

override

Nr of RS232 serial data port

(not external converters

permitted)

2

Nr of serial port operating in

RS485 1

Signal Connector Industry standard TNC female

Power Connector 2-pin industry standard polarized

type

Operating power supply

voltage range

between +10Vdc and +30Vdc

(13.8Vdc nominal / negative

ground)

Typical Tx power

consumption

24 W @ 30 dBm, 37 W

@ 37 dBm, and 54 W @ 40 dBm

transmitter output power

Typical RX power

consumption 5W

3

Repeater /

Base

Enclosure / Housing 1 RU Metal 19" rack mounted

Base/Repeater format 19” rack

Dimensions 483 x 45 x 410mm (1 RU)

Base/repeater redundancy Hot-standby

Signal Connector

Dual industry standard N female

for separate Tx and Rx

connection

Power Connector Multi-pin industry standard

Operating power supply

range

Between +11Vdc

and +30Vdc (13.8Vdc nominal /

negative ground)

Typical TX power

consumption

55 W @ 30 dBm, 71 W @ 37

dBm, and

85 W @ 40 dBm transmitter

output power

Typical RX power

consumption 14W

Digital I/O Multi way locking screw terminal

connector

Weight < = 5kg

4

Network

Management

and Remote

Diagnostics

Minimum of parameters to

be reported by radios

Transmit Power (dBm)

Received Signal Strength (dBm)

Internal Temperature (degrees

Celsius)

100 | P a g e

External DC Power Supply

(Volts)

Received frequency offset (Hz)

Reverse Antenna Power (VSWR)

Diagnostics Protocols SNMP V1,V2c and RFC 1213-

compliance

Firmware updating method Both: locally (wire connection)

and remotely (over the air)

101 | P a g e

6 LOAD BREAK SWITCHES/ SECTIONALISERS

ANNEX A: Guaranteed Technical Particulars (to be filled and signed by the Manufacturer and

submitted together with catalogues, brochures, drawings, technical data, sales

records and certified true copies of type test certificates and type test reports for

tender evaluation)

6.1 APPLICABLE STANDARDS

IEC 60044.1 Instrument Transformers – Current Transformers

IEC 60071-1 Insulation Co-ordination

IEC 61000 Electromagnetic Compatibility (EMC) – Parts 1,2,3,4 & 6

IEC 60815 Selection and dimensioning of high-voltage insulators intended for use

in polluted conditions

IEC 62271.103 High Voltage Switchgear & Control Gear – Switches for rated voltage

from 1kV to 52kV.

IEC 62271.200 High Voltage Switchgear & Control Gear-A.C. Metal-Enclosed

Switchgear and Control gear for Rated Voltages above 1kV and

including 52kV

IEC 62351-3 Security of Profiles including TCP/IP

IEC 62351-5 Security of Protocols

IEEE 1815 Standard for Electric Power Systems Communications - Distributed

Network Protocol (DNP3)

ISO 1461 Hot dip galvanized coatings on fabricated iron and steel articles

6.2 SERVICE CONDITIONS

Parameters Units Value Elevation above sea level m ≤1000

Maximum ambient air temperature ◦C 50

Minimum ambient air temperature ◦C -20+

Maximum solar radiation level W/m2 1100

Maximum humidity % 100

Wind velocity-steady Km/h 80

Wind velocity-Gusts Km/h 160

Maximum Salt deposits per month mg/m2 30

102 | P a g e

6.3 SYSTEM CONDITIONS

Parameters Unit 11Kv 33Kv

Rated System Voltage kV 11 33

Maximum System Voltage kV 12 36

Phases 3 3

Frequency Hz 50 50

Lightning Impulse Withstand Common

Value

kV 95 170

Lightning Impulse Withstand across

isolating gap

kV 110 195

Power Frequency Voltage Withstand

Common Value

kV 28 70

Power Frequency Voltage Withstand

across isolating gap

kV 32 80

Short Circuit Level kA 16 16

Short Circuit Duration s 3 3

6.4 LBS EQUIPMENT RATINGS

Parameters Unit 11Kv 33Kv

Nominal Voltage kV 11 33

Maximum Voltage kV 12 36

Phases 3 3

Frequency Hz 50 50

Rated Current A 630 630

Short Circuit Level kA 16 16

Fault Make Capacity kA (RMS) 16 16

Fault Make Peak (50Hz) kA 40 40

Rated Short Time Current s 3 3

Lightning Impulse Withstand Common Value kV 95 170

Lightning Impulse Withstand across isolating gap kV 110 195

Power Frequency Voltage Withstand Common

Value

kV 28 70

Power Frequency Voltage Withstand across

isolating gap

kV 32 80

Breaking Capacity Mainly Active (0.7pf) A 630 630

Breaking Capacity Cable Charging A 20 20

Breaking Capacity Line Charging A 2 2

Mechanical Operations No. 5,000 5,000

Full Load Operations No. 400 400

103 | P a g e

6.5 SWITCHGEAR REQUIREMENTS

6.5.1 General Requirements

6.5.1.1 The switchgear shall be fully enclosed and gas insulated.

6.5.1.2 The switchgear shall be suitable for use as a disconnector and shall comply

with the requirements of IEC62271-103

6.5.1.3 The switchgear shall be capable withstanding throughput of rated fault current

for 3s.

6.5.1.4 Provision shall be made for local manual opening and closing of the

switchgear. The speed of opening and closing of the contacts shall be operator

independent.

6.5.1.5 Provision shall be made for local electrical opening and closing of the

switchgear.

6.5.1.6 Electrical operation of the switchgear shall be independent of the status of the

HV supply and shall be via low voltage AC or DC source.

6.5.1.7 The switchgear shall be capable of closing onto a fault up to its specified fault

rating.

6.5.1.8 Clear and unambiguous mechanical indication shall be provided to an operator

standing on the ground as to the status of the switchgear main contacts.

6.5.1.9 The switchgear indicator shall be mechanically linked to the switching

mechanism of the switchgear.

6.5.1.10 The switchgear shall be provided with facilities to be mechanically locked.

The status of the mechanical lock shall be clearly visible.

6.5.2 Disconnector Function

6.5.2.1 The switchgear shall be suitable for use as a disconnector providing a fully

rated point of isolation suitable to allow the application of temporary earth

conductors to enable work on the line to be effected safely. The switchgear

shall comply with the requirements of IEC62271-103 (dielectric) tests:

(IEC62271-1 Clause 6.2)

6.5.3 Material & Finish

6.5.3.1 All exposed metal components of the switchgear (excluding the bushing

terminals and mounting bracket) shall be manufactured from either an

aluminium casting or stainless steel of grades 304 or 316. Strong preference

will be given to items manufactured from 316 grade stainless steel.

6.5.3.2 All support structures (i.e. mounting brackets for the circuit-breaker, surge

arresters, external voltage sensors, etc.) shall be made of stainless steel, or as a

minimum be hot-dip galvanized in accordance with ISO1461

6.5.3.3 Bolts and nuts associated with the support structures shall be hot-dip

galvanized in accordance with ISO1461

104 | P a g e

6.5.4 Switchgear

6.5.4.1 The equipment shall be suitable for both single-pole and H-pole mounting.

6.5.4.2 The interface between the pole and the mounting bracket shall have two M20

mounting holes.

6.5.4.3 The mounting holes shall be designed such that it will be possible to slide the

circuit-breaker into position without having to remove the nuts and washers

from the threaded rods

6.5.4.4 All the required mounting hardware shall be supplied with the switchgear

6.5.4.5 Bolts nuts and washers shall be hot dipped galvanized

6.5.4.6 Adequately rated lifting eyes shall be provided to allow the completely

assembled switchgear (fitted with surge arresters and external voltage sensors

(if applicable)) to be lifted without recourse to a sling spreader. The inside

diameter of the lifting eyes shall be a minimum of 25mm.

6.5.5 Earthing arrangement

6.5.5.1 An M8 or larger earth stud welded to main tank shall be provided in an

accessible position.

6.5.6 Switchgear Terminations

6.5.6.1 A fully insulated termination shall be provided by design or via the use of

appropriate insulation guards

6.5.7 Terminals

6.5.7.1 The terminals shall be suitable to accept aluminium or copper conductors

6.5.8 Bushings

6.5.8.1 Details of the external insulation material shall be provided in the tender

documentation. Preference will be for bushings manufactured of a composite

material such as cycloaliphatic epoxy.

6.5.9 Creepage

6.5.9.1 The switchgear shall be suitable for application in areas with very heavy

pollution levels as defined by IEC 60815.

6.5.9.2 Minimum creepage will be 31mm / kV

6.5.10 Profile

6.5.10.1 Bushing profile characteristics shall comply with the guidelines of annex

D of IEC 60815.

6.5.10.2 Details of the critical dimensions and ratios, as defined in annex D of IEC

60815, shall be provided in the tender documentation.

6.5.11 Surge Arrester Mounting

6.5.11.1 Mounting brackets for surge arresters shall be provided on the source and

load side of the switchgear, adjacent to the bushings.

105 | P a g e

6.5.12 Current Transformers

6.5.12.1 The switchgear shall be supplied with three (one per phase) current

transformers.

6.5.12.2 The current transformers with a minimum class of class 5P15 as defined in

IEC 60044 shall be preferred.

6.5.13 Voltage Sensors

6.5.13.1 The switchgear shall be supplied with six voltage sensors (e.g. VTs,

CVTs, etc.), one per phase on the source and the load side.

6.5.13.2 It is preferable that the voltage sensors are an integral part of the

switchgear.

6.5.13.3 The accuracy of the total voltage measurement system shall not exceed

3%

6.5.14 Control Cable

6.5.14.1 An ultraviolet resistant cable, minimum 7m long, shall be provided to

connect the switchgear to the control unit.

6.5.14.2 Robust, multi-pin, weatherproof connectors shall be provided on both ends

of the control cable.

6.5.15 Rating Plate

6.5.15.1 Each switch shall bear a rating plate of an intrinsically corrosion-resistant

material, indelibly marked with the sea-level rating for which the equipment

has been type tested. The rating plate shall be indelibly marked with:

i) the manufacturer's name;

ii) the equipment type designation and serial number of the LBS;

iii) the mass, in kilograms;

iv) the date of manufacture; and

v) Frequency, f

vi) Rated Voltage, Ur

vii) Lightning Impulse Withstand Voltage, Up

viii) Rated Current, Ir

ix) Rated Breaking Current, Isc

x) Rated Making Current, Ima

xi) Rated Short Time Withstand Current, Ik

xii) Rated Duration of Short Circuit, tk

106 | P a g e

6.5.16 Maintenance & Inspection

6.5.16.1 Tenderers shall provide all information regarding the inspection, testing,

and maintenance required. Preference will be given to low maintenance

solutions. Tenderers shall state required maintenance intervals and provide list

of spare parts necessary for maintenance activities.

6.5.16.2 The equipment shall incorporate a system that provides indication of the

approximate remaining life of the interrupters. This information shall also be

available via SCADA for maintenance planning purposes

6.5.16.3 Switchgear containing SF6 shall have gas pressure measurement and

indication. The switchgear shall not be able to be opened / tripped or closed

when SF6 gas pressure is below the safe level for operation.

6.5.16.4 It shall be possible to disconnect the control cable at the control unit while

the switchgear is energised, live, and carrying load, without causing damage

or mal-operation. Removing or connecting the control cable while the

switchgear is in service shall not result in the switchgear changing

open/closed state. The system shall also be such that it ensures that CTs are

not open-circuited.

6.5.17 Test sets / tank simulators

6.5.17.1 All devices with electronic controllers shall have a suitable tank simulator

for testing and commissioning.

6.5.17.2 Tank simulators shall be supplied with all required cables for connection

to switchgear.

6.5.17.3 Tank simulators shall be supplied with open/close contacts for switchgear

status.

6.5.17.4 Tank simulators shall be capable of secondary injection from a separate

piece of test equipment via banana plug fittings. Tanks simulators shall be

capable of simultaneous injection via 3 current inputs and 6 voltage inputs to

simulate 3 phase network events.

6.5.17.5 Preference will be given to equipment that can simulate voltages and

currents in the simulator / switchgear to reduce or avoid the requirement for

secondary injection

6.5.18 CONTROL UNITS

The Control unit shall be a microprocessor-based electronic device that interfaces the

power equipment to a control system. It shall include all the functions required to monitor

and control the switchgear. It shall include an RTU for SCADA communications.

6.5.18.1 Material & Finish

a. The control cabinet shall be manufactured from stainless steel of grades 304 or 316.

Strong preference will be given to items manufactured from 316 grade stainless

steel.

107 | P a g e

b. The mounting bracket shall be made stainless steel of grades 304 or 316.

6.5.18.2 Mounting Arrangement

a. The control cabinet shall be easily removable for workshop repair purposes.

b. The cabinet shall be supplied with a mounting bracket.

c. The mounting bracket shall have at least two, vertically spaced, mounting holes.

The holes shall be designed such that it will be possible to slide the cabinet into

position without having to remove the pole mounting bolts (or coach screws).

d. The mounting bracket shall have at least two sets of, vertically spaced, slots for

temporary mounting by means of straps.

6.5.18.3 Earthing Arrangement

a. Control cabinets shall be provided with an M8 or larger earth stud.

6.5.18.4 Construction

(a) The control cabinet shall be separate from the switchgear (i.e. the switchgear and

control unit shall not be integrated into a single device)

(b) Cabinets shall be protected from dust and water ingress to achieve an IP rating of

IP 55 or better as per IEC 60529

(c) The main electronics compartment shall be protected from dust and water ingress

to achieve an IP rating of IP 65 or better as per IEC 60529.

(d) Cabinets shall be designed and internally treated to prevent moisture condensation.

(e) All metal components of the control cabinet shall be electrically bonded.

(f) Provision shall be made in the cabinet to mount the user’s data communication

equipment.

(g) The layout of the cabinet shall ensure easy accessibility to the user’s

communications equipment.

6.5.18.5 Door

(a) The cabinet shall have a hinged door.

(b) The door shall be fitted with a robust fastening arrangement which can be locked

with a padlock that has a shackle of 8 mm diameter.

(c) The door shall be provided with three point locking.

(d) Means shall be provided to either secure the door in a fully open position (90° or

more), or to easily remove (without the use of tools) the door completely during

maintenance or similar activities.

(e) Good electrical contact shall be maintained between the door and the rest of the

cabinet at all times (excluding the condition when the door is completely removed).

(f) The cubicle shall be alarmed such that when the door is opened a SCADA alarm

will be generated.

108 | P a g e

6.5.18.6 Cable Entry

(a) The cabinet shall make provision for bottom entry of at least three cables.

(b) A suitable arrangement shall be provided to earth the gland plate.

(c) The holes in the blanking plate shall be blanked off with blanking plugs that are

bolted or screwed in to position.

(d) The control cabinet shall be fitted with external antenna connectors.

6.5.18.7 Power Supply

(a) The control unit shall have an integral power supply.

(b) The capacity of the power supply shall be rated to power all the electronic modules,

operate the switchgear (tripping/opening and closing) and power the data

communication equipment.

(c) Steps shall be taken to minimise the device’s power consumption.

(d) Adequately rated miniature circuit-breakers shall be provided for individually

isolating the control from the following:

(i) Auxiliary Supply

(ii) Battery Supply

(iii)Power Supply Input

(iv) The auxiliary supply will be derived from an external power source.

The required supply shall be one of the following:

(a) 110 V (±10%) AC at a frequency of 50 Hz;

(b) 240 V (±10%) AC at a frequency of 50 Hz;

(c) The device shall provide a visual indication, on the control panel and in the event

log, of the status of the auxiliary supply.

(d) An auxiliary supply fail function shall be provided; it shall operate an alarm output.

(e) Loss or restoration of the auxiliary supply voltage, and under-voltage conditions in

the auxiliary supply shall not result in damage or spurious operation of the

equipment.

6.5.18.8 Power Supply Protection

(a) The power supply shall include the necessary over-current protection to protect the

supply from current excursions.

(b) The use of fuses for over-current protection on the auxiliary input circuit(s) is not

acceptable.

(c) The power supply shall include the necessary surge arresters and/or voltage limiting

devices to inhibit damage due to voltage surges. (Surge protected up to 20kV, in

compliance with IEC60255-5)

109 | P a g e

6.5.18.9 Battery Backup Supply

(a) A battery backup supply consisting of batteries and a constant voltage battery

charger, with current limiting, shall be provided with the control unit.

(b) The Battery standby time shall be a minimum of 24h, allowing for the

following:

(i) Ten switchgear operations;

(ii) 3Ah for the communications device

(iii)The battery charger shall be capable of recharging the battery from flat to

80% of its capacity within 15 hours

(c) The switchgear shall be prevented from operating if the battery does not have

enough stored energy to complete the operation.

(d) Batteries shall be automatically disconnected at the manufacturer’s specified

minimum voltage and automatically reconnected when auxiliary power is

restored.

(e) The minimum operational battery life expectancy (to 80% of rated capacity at

–10˚C) shall exceed 3 years.

(f) Provision shall be made for an orderly shutdown when the battery voltage

reaches the manufacturer’s specified minimum limit.

6.5.18.10 Self-Monitoring

(a) The battery charging system shall be temperature compensated

(b) The battery system shall incorporate a battery test facility. During the test the

auxiliary power supply will be disconnected and a load placed on the battery,

rate of voltage drop and voltage recovery time etc. shall be analysed to

determine the health of the battery. The battery test shall be configurable to

occur periodically and shall be delayed during an operation or when the

auxiliary supply has failed.

(c) The power system shall incorporate means to prevent deep discharge of the

batteries

(d) The power supply shall deliver the following status to the SCADA.

(i) Battery disconnected;

(ii) Absence of power input /Auxiliary Supply Fail

(iii)Battery Low volts

(iv) Battery Low Capacity (Low Power Mode)

(v) Battery End of Life (Battery Test Fail)

Electronic modules shall perform continuous diagnostic monitoring and shall

contain hardware and software watchdog checking.

110 | P a g e

6.5.18.11 Cyber security

The load break switches/sectionalizers control units shall be provided to respect the

same cyber security requirements as the RTUs described in 2.8 of “Part 1 for ground

mounted substations remote terminal units”.

6.5.18.12 EMC

EMC testing shall be effected as per the Type Test Requirements detailed in Type Test

Clause below.

6.5.18.13 Interoperability

Preference will be given to providers whose control unit is common between reclosers

and LBS and which do not require alternative firmware to be loaded in the controller,

rather the controller shall automatically detect the switchgear type and display the

appropriate settings and configuration screens.

6.5.18.14 Configuration Software & Engineering Access

(a) The switchgear shall be fully configurable from a PC, utilising the configuration

software.

(b) A configuration port shall be provided to facilitate remote configuration via

standard Data Communication Equipment.

(c) The configuration port shall be an EIA-232 port, a USB port or an Ethernet port.

(d) The configuration software shall be compatible with Microsoft Windows Operating

System 7 or equivalent.

(e) Configuration software is regarded as an integral part of the offer and shall be

provided at no additional charge.

(f) It shall be possible to perform future controller firmware upgrades via the local

communication ports.

(g) Engineering access shall be possible locally and remotely using appropriate

communications media

(h) Units shall support both engineering and SCADA access on a single Ethernet port.

Neither communication shall interfere with the other

(i) It shall be possible to change settings by discreet functions for example it shall be

possible to write all detection settings without affecting telemetry settings or

operator settings etc.

6.5.18.15 Human Machine Interface

(a) The operator interface shall be designed for ease of operation to minimise training

and avoid operator error.

(b) Engineering access to all configuration parameters shall be possible via an easy to

use menu with dedicated menu navigation buttons.

111 | P a g e

(c) Operator access to all status indicators, operator controls and logged data will be

possible via the operator interface.

(d) The operator interface shall provide a facility to electrically disable any electrical

operation of the switchgear. Disabling circuits shall be by physically disconnecting

the circuit from the close energy source.

(e) Trip/Open operation shall be via a dedicated green button. This button shall also

include status indication. (See Appendix 1)

(f) Close operation shall be via a dedicated red button. This button shall also include

status indication.

6.5.18.16 Local Controls & Indications

A customer configuration utility will be provided to allow customisation of status

indications and command buttons on the HMI. The configuration utility will allow

modification of the lamp and button text labels, lamp colours and logic functions

driving the lamp output. It will also be possible to assign different functions to the

command buttons.

6.5.19 ANALOGUE MEASUREMENT REQUIREMENTS

(a) Measurement shall be done with one of the following methods:

(b) three-phase-3-wire method; and

(c) or the three-phase-4-wire method

Quantities to be measured/calculated with specified accuracy are:

r.m.s. phase-to-phase and phase-to-ground voltage of all

three phases

±2.5%;

Positive phase sequence voltage ±2.5%;

Negative phase sequence voltage ±2.5%;

Zero phase sequence voltage ±2.5%;

r.m.s current per phase (within rated current range) ±2.5%;

Earth Current ±2.5%;

Positive phase sequence current ±2.5%;

Negative phase sequence current ±2.5%;

three phase active power in kW ± 5%;

three phase reactive power in kVar ± 5%;

total three-phase active energy in kWh ± 5%;

Power factor ± 5%;

Maximum demand ± 5%;

The real power energy and maximum demand measurement shall be integrated with respect to

time. Energy values shall be calculated with selectable time integration periods of 5 min, 15

min, 30 min or 60 min. The data buffer shall work on the FIFO principle and a minimum size

for the data buffer shall store values for a minimum of 4 months on the 30 minutes integration

period.

112 | P a g e

6.5.20 OUTAGE MEASUREMENTS

The switchgear and Control element shall have the facilities to record the cumulative

number and duration of outages. The information shall be assessable locally or remotely

via telemetry messaging to a SCADA system. The following parameters shall be recorded:

(a) Cumulative total number of outages;

(b) Cumulative total outage duration; and

(c) Time and duration of each outage in the form of an event log.

6.5.21 HARMONIC ANALYSIS

Harmonics to the16 and the Total Harmonic Distortion (THD) shall be provided for the

phase currents, source side voltages and load side voltages. The captured harmonics shall

be available via PC for off line display and analysis.

The magnitude and the phase angle between the corresponding voltages and currents of the

analogues listed shall be displayed:

a) Positive phase sequence voltage,

b) Negative phase sequence voltage,

c) Zero phase sequence voltage,

d) Positive phase sequence current,

e) Negative phase sequence current, and

f) Zero phase sequence current.

6.5.22 DETECTION REQUIREMENTS

6.5.22.1 General Requirements

The control unit shall provide the following Detection features.

Phase over current

(a) Earth Fault current

(b) Sensitive Earth Fault current

(c) Negative Phase Sequence current

(d) Directional Phase over current

(e) Directional Earth Fault current

(f) Directional Sensitive Earth Fault current

(g) Directional Negative Phase Sequence current

(h) Broken Conductor

(i) Under voltage

(j) Over voltage

(k) Loss of Phase

113 | P a g e

6.5.22.2 Phase over Current Detection Requirements

(a) The minimum setting range for Pickup shall be 20-800A

(b) The Pickup setting range shall be user selectable in steps of 5A or less

(c) Phase Overcurrent shall support a definite time characteristic.

(d) The minimum Setting Range for the Definite Time element shall be 0.02s- 10s

(e) The Definite Time Setting Range shall be user selectable in steps of 20ms or

less

(f) An Instantaneous characteristic shall be provided.

(g) An instantaneous characteristic shall be selectable either as the only curve for

the selected trip or as an overlay on a definite time characteristic

6.5.22.3 Earth over Current Detection Requirements

(a) The minimum setting range for Pickup shall be 20-800A

(b) The Pickup setting range shall be user selectable in steps of 5A or less

(c) Earth Overcurrent shall support a definite time characteristic.

(d) The minimum Setting Range for the Definite Time element shall be 0.02s- 10s

(e) The Definite Time Setting Range shall be user selectable in steps of 20ms or

less

(f) An Instantaneous characteristic shall be provided.

(g) An instantaneous characteristic shall be selectable either as the only curve for

the selected trip or as an overlay on a definite time characteristic

6.5.22.4 Negative Phase Sequence (NPS) over Current Detection Requirements

(a) The minimum pickup setting range shall be 2-800A

(b) The pickup setting range shall be user selectable in steps of 1A.

(c) NPS Overcurrent shall support a definite time characteristic.

(d) The minimum Setting Range for the Definite Time element shall be 0.02s- 10s

(e) The Definite Time Setting Range shall be user selectable in steps of 20ms or

less

(f) An Instantaneous characteristic shall be provided.

(g) An instantaneous characteristic shall be selectable either as the only curve for

the selected trip or as an overlay on a definite time characteristic.

6.5.22.5 Sensitive Earth Fault (SEF) Detection Requirements

(a) The SEF element shall support a definite time characteristic.

(b) The SEF element shall support IDMT characteristics.

(c) The SEF function shall be equipped with harmonic filtering to prevent operation

when harmonics are present in the primary residual earth currents. A low-pass

filter shall be supplied, with:

2nd harmonic rejection > 6: 1;

114 | P a g e

3rd harmonic rejection > 50: 1.

The SEF shall be settable from 4-20A in 1A steps.

The minimum Setting Range for the Definite Time element shall be 0.1s-

30s

The Definite Time Setting Range shall be user selectable in steps of

100ms or less

6.5.22.6 Broken Conductor Detection

Broken conductor detection shall be current based and shall be able to detect a broken

conductor downstream (in the direction of the power flow).

a) A Broken Conductor shall be detected by comparing the ratio of negative phase

sequence current to positive phase sequence current.

b) The Broken Conductor element shall support a definite time characteristic.

c) The minimum Setting Range for the Definite Time element shall be 0.2s- 120s

d) The Definite Time Setting Range shall be user selectable in steps of 100ms or less

e) The detection setting (Inps / Ipps) shall be settable over the range 0.1 – 1.

f) The Broken Conductor setting ratio shall be selectable in steps of 0.1 or less.

6.5.22.7 IDMT Overcurrent Characteristics

The Phase, Earth Fault and NPS elements shall support IDMT characteristics.

Further preference will be given to units where the SEF characteristic also supports use

of an IDMT characteristic.

Where IDMT characteristics are supported, the following IDMT characteristics shall

be supported:

a) Normal inverse (NI),

b) Very inverse (VI) and

c) Extremely inverse (EI) in accordance with IEC 60255, standard moderately

inverse, very inverse and extremely inverse in accordance with IEEE C37.112.

d) It is preferable that the relay also supports traditional TCC curves.

Where IDMT characteristics are supported;

i) A threshold or pick up multiplier shall be provided.

ii) The minimum setting range for the Pick Up Multiplier shall be 1.0-5.0

iii) The Pick-up Multiplier setting range shall be user selectable in steps of 0.1 or less

iv) The minimum setting range for the IDMT characteristic Time Multiplier shall be

0.1 –2A wider range is preferred

v) The IDMT characteristic Time Multiplier setting range shall be user selectable in

steps 0.05 or less.

115 | P a g e

vi) An Instantaneous characteristic shall be provided.

vii) An instantaneous characteristic shall be selectable either as the only curve for the

selected trip or as an overlay on an inverse time curve

viii) The IDMT characteristics shall be configurable with a Minimum Time

Modifier.

ix) The minimum setting range for the Minimum Time Modifier shall be 0 – 2s

x) The Minimum Time Modifier setting range shall be user selectable in steps of 0.

05s or less.

xi) The IDMT characteristics shall be configurable with a Maximum Time modifier.

xii) The minimum setting range for the Maximum Time Modifier shall be 0.2 – 10s

xiii) The Maximum Time Modifier setting range shall be user selectable in

steps of 0.1s or less.

xiv) The IDMT characteristics shall be configurable with an Additional Time

Modifier.

xv) the minimum setting range for the Additional Time Modifier shall be 0 – 2s

xvi) The Additional Time Modifier setting range shall be user selectable in

steps of 0.05s or less.

6.5.22.8 Detection Reset

a) Drop off current shall be a maximum of 95% of the Pickup Current and a

minimum of 85% of the Pickup Current for all Detection functions.

b) A definite time characteristic shall be provided for the reset time.

c) The minimum setting range for the Fault Reset Time shall be 10ms to 10s.

d) The Fault Reset Time shall be configurable in steps of 50ms or less.

e) Once pickup has occurred, shall the measured current fall below the Pickup

threshold but remain above the reset threshold the detection timing will be

paused and re-started if the current once again exceeds the Pick-up.

6.5.22.9 Inrush Restraint

a) A harmonic current inrush restraint function shall be supplied. Transformer

magnetising current is characterised by a significant percentage of second for

the inrush restraint fee trigger order harmonic current relative to the

fundamental current. The trigger for the inrush restraint feature shall not be

zero amps current but rather a user configurable percentage of second order

harmonic current relative to the fundamental current.

b) The minimum range for the restraint period, the Inrush Restraint Time, shall

be 50ms to 30s

c) The Inrush Restraint Time shall be user selectable in steps of 10ms or less

d) The minimum range for the Inrush Restraint Multiplier shall be 1 to 30

e) The Inrush Restraint Multiplier shall be user selectable in steps of 0.1 or less

116 | P a g e

f) The minimum range for the percentage of second order harmonic relative to

the fundamental, the Inrush Restraint Threshold, shall be 20% to 200%

g) The Inrush Restraint Threshold shall be user selectable in steps of 1% or less

6.5.22.10 Cold Load

a) A cold load pick-up (CLP) feature shall be provided that allows user

selectable modification of protection element characteristics under conditions

of system power restoration.

b) The elements to be modified by the cold load function shall be selectable.

c) This CLP feature shall allow the Pick Up current of the selected elements to

be raised to a user configured multiple of the Pick Up current, (Cold Load

Multiplier), in a linear fashion over a user selectable time (Cold Load Time)

d) The minimum setting range for the Cold Load Time shall be 5 - 60 minutes

e) The Cold Load Time shall be user configurable in steps of 5 minutes or less.

f) The minimum setting range for the Cold Load Multiplier shall be 1 -4.

g) The Cold Load Multiplier shall be user configurable in steps of 0.1.

h) The vendor may propose an alternative arrangement for consideration by the

purchaser.

6.5.22.11 Voltage Detection Requirements

a) The over voltage detection function shall detect voltages above the nominal

phase to earth system operating voltage.

b) The minimum setting range for the Overvoltage Alarm Threshold shall be

110% - 180%,

c) The Overvoltage Alarm Threshold shall be user configurable in steps 5%, or

less.

d) The Over Voltage detection function shall use a Definite Time Characteristic.

e) The minimum setting range Over Voltage Alarm Delay Time shall be 0.2s -

60s.

f) The Over Voltage Alarm Delay Time shall be user configurable in steps of

100ms or less.

g) It shall be possible to configure the over voltage detection function to detect

under voltage on a single phase, all three phases or the average of all three

phases.

h) The under voltage Detection function shall detect voltages below the nominal

phase to earth system operating voltage.

i) The minimum setting range for the Under Voltage Alarm Threshold shall be

50% - 90%,

j) The Under Voltage Alarm Threshold shall be user configurable in steps 5%,

or less.

117 | P a g e

k) The Under Voltage detection function shall use a Definite Time

Characteristic.

l) The minimum setting range Under Voltage Alarm Delay Time shall be 0.2s -

60s.

m) The Under Voltage Alarm Delay Time shall be user configurable in steps of

100ms or less.

n) It shall be possible to configure the under voltage detection function to detect

under voltage on a single phase, all three phases or the average of all three

phases.

o) It shall be possible to separately enable / disable the Over and Under Voltage

Detection functions.

6.5.22.12 Directional Detection

a) A Directional Detection feature shall be provided.

b) The minimum time to determine fault direction for Phase Overcurrent, Earth

Fault and NPS shall not exceed 50ms

c) The relay minimum time to determine fault direction for SEF shall not exceed

500ms

d) The relay shall have independent settings for each element for the following

quantities:

i. Characteristic Fault Angle

ii. Forward Sector Width

iii. Reverse Sector Width

iv. Low Polarising Voltage Threshold

v. Low Polarising Voltage Action

e) The minimum setting range for the Characteristic Fault Angle shall be-

179˚to180˚

f) The Characteristic Fault Angle shall be user configurable in steps of 1˚

g) The minimum setting range for the for Forward and Reverse Sector Widths

shall be 45˚- 90˚

h) The Forward and Reverse Sector Widths shall be user configurable in steps of

1˚

i) The minimum setting range for the Low Polarising Voltage Threshold shall be

300-15,000 Volts

118 | P a g e

6.5.22.13 Sectionalizing Function

a) It shall be possible to use the LBS as an automatic Sectionaliser when the LBS

is used in conjunction with an upstream Automatic Circuit Recloser. (ACR)

b) If a fault is detected and both the measured current and voltage drop to zero

the LBS shall count one ACR operation and register a count of 1 in an

interruption counter register.

c) Subsequent faults detected followed by both the measured current and voltage

dropping to zero the LBS shall further increment the interruption counter.

d) When a predetermined count is reached the LBS shall automatically open to

isolate the faulty circuit while the ACR is in the open position. The ACR can

then restore power to the healthy part of the system.

e) The minimum setting range for the Interruption Counter shall be 1-3.

f) If the fault is of temporary nature and is cleared before the LBS count reaches

the predetermined number, the LBS shall remain closed and shall reset to its

pre-fault condition after the reset time is expired.

g) The minimum setting range for Sequence Reset Time shall be selectable from

3s to 120s

h) The Sequence Reset Time shall be configurable in steps of 1 s or less.

6.5.22.14 Fault Locator

All units shall be provided with a function that calculates the distance to fault following

detection of a fault. Details of the proposed system shall be provided.

119 | P a g e

6.5.23 COMMUNICATIONS AND HARDWARE

6.5.23.1 Remote Terminal Unit RTU

(a) The Control unit shall include a Remote Terminal Unit RTU

(b) The RTU shall support telemetry messaging using the DNP3 protocol. Preference

will be given to equipment which also supports IEC 870-5-104 IEC 870-5-101

6.5.23.2 Telemetry Communications Ports

(a) An RS-232 port shall be provided for telemetry communications

(b) A 10Base-T or 100Base-T Ethernet port shall be provided for telemetry

communications

(c) Preference will be given to equipment which provides additional RS232, RS485,

Ethernet or V23 modem ports.

6.5.23.3 Communications Equipment

(a) Provision will be made to mount communications equipment to include modems or

radios in the control box. The available space to mount equipment will be detailed.

(b) Provision shall be made in the bottom entry gland plate for at least two keyed holes

for the external antenna connections.

6.5.23.4 Communications Equipment Power Supply

(a) A user programmable communications equipment power supply shall be provided.

(b) The minimum setting range for the Communications Equipment Power Supply

shall be 10-15V dc

(c) The Communications Equipment Power Supply shall be configurable in steps of

not more than 1V.

(d) The communications equipment power supply shall have a continuous rating of at

least 30W

6.5.23.5 Remote Controls & Indications

(a) The required remote controls, indications and analogues are detailed in Appendix

2

(b) The I/O map shall be user configurable to add or delete points

120 | P a g e

6.5.23.6 Indications

(a) Each indication shall be configurable to provide time stamping of status changes

with an accuracy of 10ms or better.

(b) Status changes shall be reported and recorded in the event log in the sequence in

which they occur

(c) A facility shall be provided to invert the status of indications

(d) An event buffer to store all changes in configured SCADA points as time-stamped

events shall be provided. The buffer shall have a capacity of at least 250 events.

6.5.23.7 Controls

(a) The control output sub-system shall support both Direct-Operate and Select-

Before-Operate controls. The selection of type will be made at the master station.

(b) Failure of any one component shall not result in an undesired control output

(c) It shall be possible to test the control subsystem by issuing a “dummy” control

6.5.23.8 11.8 Counters

(a) At least two counters shall be provided (minimum 16 bits).

(b) Counters shall be stored in non-volatile memory

(c) It shall be possible to assign the counters to count different points in the device

(d) The counters shall have a user configurable report facility (time referenced to the

hour or count based). If the counter’s capacity is exceeded then the accumulator

shall operate in a rollover fashion. It shall be possible to configure jitter, reporting

and other settings per counter.

6.5.23.9 Analogues

(a) All analogues shall have a resolution of at least 16 bits.

(b) A dead band facility shall be provided to report analogue changes on the

transgression of a configurable setting range

(c) A facility to report the transgression of high and low analogue values as digital

alarms shall be provided.

121 | P a g e

6.5.23.10 Time Synchronization Management

(a) The control shall be equipped with a battery backed real time clock with leap year

support.

(b) It shall be possible to set the clock via the configuration software and via a DNP3

master to within 1ms of the synchronisation clock.

(c) The accuracy of the clock shall be better than 12 (twelve) parts per million

(d) The precision of the clock shall be 1 millisecond or better

(e) The real time clock battery, or other power source, shall provide at least 20 days of

total standby time. The power source shall not need replacing more often than every

ten years.

6.5.23.11 Custom Logic Functionality

6.5.23.11.1Custom Logic inputs and operations

(a) The control system shall provide a CLF (custom logic functionality) to allow

the creation of unique logic status monitoring functions.

(b) It shall be possible to monitor the status of:

(i) Digital control data (Switchgear and controller status, Operator control

settings, Protection events, External Inputs & Outputs, and protocol

triggers)

(ii) Analogue signals (Line Current and Voltage measurement, Counters and

Timers)

a) It shall be possible to create logic expressions using Boolean Logic

operands such as AND, OR, NOT to evaluate the status of digital and

analogue database values.

b) It shall be possible to create multiple logic expressions.

6.5.23.11.2 Utilisation of the Custom Logic functions

(a) The results of the logic expressions shall be available via protocol for additional

indication back to the control centre.

(b) It shall also be possible to display the results of these logic expressions via

LEDs located on the operator interface.

(c) Furthermore the results of the logic expressions shall be available to perform

automatic actions (turn features on/off) and control external equipment.

122 | P a g e

6.5.24 TYPE TESTS

All switchgear shall be type tested for the following and the appropriate values shall be

stated in the tender documentation:

6.5.24.1 Insulation (dielectric) tests: (IEC62271-103 Clause 6.2)

a) power frequency withstand voltage test (Wet & Dry)

b) Lightning impulse withstand voltage test.

6.5.24.2 Measurement of the resistance of the main circuit (IEC62271-103 Clause

6.4)

6.5.24.3 Temperature Rise (IEC62271-103 Clause 6.5)

6.5.24.4 Short-time withstand current & peak withstand current (IEC62271-103

Clause 6.6)

6.5.24.5 Verification of protection (IEC62271-1/60529 Clause 6.7)

6.5.24.6 Tightness test (IEC62271-103 Clause 6.8)

6.5.24.7 EMC test (IEC62271-103 Clause 6.9)

6.5.24.8 Additional tests on auxiliary and control circuits (IEC62271-103 Clause

6.10)

6.5.24.9 Making and breaking tests: (IEC62271-103 Clause 6.101)

a) Mainly Active

b) Closed Loop

c) Cable charging

d) Line charging

e) Short circuit making

f) Earth Fault Current switching

6.5.24.10 Mechanical and environmental tests:

a) Mechanical Endurance Test (IEC62271-103 Clause 6.102.2)

b) Operation at Minimum Ambient temperature (IEC62271-103 Clause 6.102.3)

c) Operation at Maximum Ambient temperature (IEC62271-103 Clause 6.102.3)

d) Tests to verify the proper functioning of the position indicating device

(IEC62271-103 Clause 6.102.6

6.5.24.11 Internal Arc (IEC62271-200, Sub-clause 6.107 and Annex A)

6.5.24.12 Mechanical Impact (IEC62271-200, Sub-clause 6.7.)

6.5.24.13 Control Element Surge Withstand Test (IEC62271-111 Clause 6.13)

6.5.24.14 EMC Testing as per the table below:

123 | P a g e

Standard Description Test Level

IEC 61000-4-2 Electrostatic Discharge +/- 8kV

+/- 15kV

IEC 61000-4-3 Radiated

Electromagnetic Field

10V/m, 80 MHz - 1000 MHz

3V/m, 1000 MHz - 2700 MHz

10V/m, 1000 MHz - 2700 MHz

IEC 61000-4-4 Fast Transient

+/- 4kV

+/- 4kV

+/- 4kV

+/- 4kV

+/- 4kV

+/- 4kV

+/- 4kV

IEC 61000-4-5 Surge

+/- 4kV line-to-earth, +/- 2kV line-to-line,

1.25/50usec

+/- 4kV, 1.25/50usec

+/- 4kV, 10/700usec

+/- 4kV, 10/700usec

+/- 4kV, 1.25/50usec

+/- 4kV, 1.25/50usec

+/- 4kV, 1.25/50usec

IEC 61000-4-6 Conduced Disturbances

10V RMS

10V RMS

10V RMS

10V RMS

10V RMS

10V RMS

10V RMS

IEC 61000-4-8

Power Frequency

Magnetic Field 100A/m continuous, 1000A/m for 1s

IEC 61000-4-11 Voltage Dips and

Interruptions

Voltage dips - 0% 1 cycle, 40% for 10 cycles,

70% for 25 cycles, 80% for 250 cycles

Voltage interruptions - 0% for 250 cycles

IEC 61000-4-16

Conducted Common

mode disturbances 0-

150kHz

30V continuous, 300V 1 sec, 50/60Hz

30V continuous, 300V 1 sec, 50/60Hz

IEC 61000-4-18 Damped Oscillatory

Wave

2.5kV Common mode, 1kV diff. @ 100kHz

and 1MHz

2.5kV common mode @ 100kHz and 1MHz

124 | P a g e

6.5.25 ROUTINE TESTS

All switchgear shall be tested for the following and the appropriate values shall be stated

in the tender documentation:

6.5.25.1 Calibration

6.5.25.2 Control, secondary wiring

6.5.25.3 Dielectric withstand test; 1-min. dry power-frequency

6.5.25.4 Partial discharge test

6.5.25.5 No load mechanical operation test

6.5.25.6 Gas leak test where applicable

125 | P a g e

7 11KV AND 33KV RECLOSER REQUIREMENTS 7.1 APPLICABLE STANDARDS

IEC 60044.1 Instrument Transformers – Current Transformers

IEC 60071-1 Insulation Co-Ordination

IEC 61000 Electromagnetic Compatibility (EMC) – Parts 1,2,3,4 & 6

IEC 60815 Selection and dimensioning of high-voltage insulators intended for use

in polluted conditions

IEC 62271.100 High Voltage Switchgear and Control gear – High Voltage Alternating

Current Circuit Breakers

IEC62271-111

(ANSI/IEEE

C37.60)

High voltage switchgear and control gear – Part 111: Overhead, Pad

Mounted, Dry Vault, and Submersible Automatic Circuit Re-closers

and Fault Interrupters for AC Systems.

IEC 62271.200 High Voltage Switchgear & Control Gear-A.C. Metal-Enclosed

Switchgear and Control gear for Rated Voltages above 1kV and

including 52kV

IEC 62351-3 Security of Profiles including TCP/IP

IEC 62351-5 Security of Protocols

IEEE 1815 Standard for Electric Power Systems Communications - Distributed

Network Protocol (DNP3)

ISO 1461 Hot dip galvanized coatings on fabricated iron and steel articles

7.2 SERVICE CONDITIONS

Parameters Units Value

Elevation above sea level m ≤1000

Maximum ambient air temperature ◦C 50

Minimum ambient air temperature ◦C -20+

Maximum solar radiation level W/m2 1100

Maximum humidity % 100

Wind velocity-steady Km/h 80

Wind velocity-Gusts Km/h 160

Maximum Salt deposits per month mg/m2 30

126 | P a g e

7.3 SYSTEM CONDITIONS

Parameters Unit 11Kv 33Kv

Rated System Voltage kV 11 33

Maximum System Voltage kV 12 36

Phases 3 3

Frequency Hz 50 50

Lightning Impulse Withstand Common

Value (Load Break Switch & recloser)

kV 95 170

Lightning Impulse Withstand across

isolating gap (Load Break Switch)

kV 110 195

Lightning Impulse Withstand across

isolating gap (Recloser)

kV 95 170

Power Frequency Voltage Withstand

Common Value (Load Break Switch

&Recloser)

kV 28 70

Power Frequency Voltage Withstand

across isolating gap (Load Break Switch)

kV 32 80

Power Frequency Voltage Withstand

across isolating gap (Recloser)

kV 28 70

Short Circuit Level kA 16 16

Short Circuit Duration s 1 1

127 | P a g e

7.4 RECLOSER EQUIPMENT RATINGS

Parameters Unit 11Kv 33Kv

Nominal Voltage kV 11 33

Maximum Voltage kV 12 36

Phases No. 3 3

Frequency Hz 50 50

Rated Current A 630 630

Short Circuit Level kA 16 16

Fault Break Capacity kA (RMS) 16 16

Fault Make Capacity kA (RMS) 16 16

Fault Make Peak (50Hz) kA 40 40

Rated Short Time Current s 3 3

Lightning Impulse Withstand Common

Value

kV 95 170

Lightning Impulse Withstand across

isolating gap

kV 95 170

Power Frequency Voltage Withstand

Common Value

kV 28 70

Power Frequency Voltage Withstand across

isolating gap

kV 28 70

Breaking Capacity Mainly Active (0.7pf) A 630 630 Breaking Capacity Cable Charging A 25 40

Breaking Capacity Line Charging A 5 5

Breaking Capacity Transformer Magnetising A 22 22

Mechanical Operations No 10,000 10,000

Full Load Operations No 10,000 10,000

Opening Time ms <50 <50

Interrupting Time ms <60 <60

Fault Clearing Time Instantaneous

Protection

ms <80 <80

128 | P a g e

7.5 SWITCHGEAR REQUIREMENTS

7.5.1 General Requirements

7.5.1.1 The switchgear shall use vacuum as the medium for interruption.

7.5.1.2 The switchgear insulation medium shall be either gas insulated or utilise a

solid dielectric insulation medium.

7.5.1.3 The switchgear shall be capable to withstand throughput of rated fault current

for 3s.

7.5.1.4 Provision shall be made to manually trip the switchgear. The speed of opening

of the contacts shall be operator independent.

7.5.1.5 Provision shall be made to locally electrically trip and close the switchgear.

7.5.1.6 Electrical Operation of the switchgear shall be independent of the status of the

HV supply and shall be via low voltage solenoid or by low voltage magnetic

actuator.

7.5.1.7 The switchgear shall be capable of breaking fault current up to its specified

fault rating.

7.5.1.8 The switchgear shall be capable of closing onto a fault up to its specified fault

rating.

7.5.1.9 Clear and unambiguous mechanical indication shall be provided to an operator

standing on the ground as to the status of the switchgear main contacts.

7.5.1.10 The switchgear indicator shall be mechanically linked to the switching

mechanism of the switchgear.

7.5.2 Material & Finish

7.5.2.1 All exposed metal components of the switchgear (excluding the bushing

terminals and mounting bracket) shall be manufactured from either an

aluminium casting or stainless steel of grades 304 or 316. Strong preference

will be given to items manufactured from 316 grade stainless steel.

7.5.2.2 All support structures (i.e. mounting brackets for the circuit-breaker, surge

arresters, external voltage sensors, etc.) shall be made of stainless steel, or as a

minimum be hot-dip galvanized in accordance with ISO1461

7.5.2.3 Bolts and nuts associated with the support structures shall be hot-dip

galvanized in accordance with ISO1461

129 | P a g e

7.5.3 Switchgear Mounting Arrangement

7.5.3.1 The equipment shall be suitable for both single-pole and H-pole mounting.

7.5.3.2 The interface between the pole and the mounting bracket shall have two M20

mounting holes.

7.5.3.3 The mounting holes shall be designed such that it will be possible to slide the

Load break switch into position without having to remove the nuts and

washers from the threaded rods

7.5.3.4 All the required mounting hardware shall be supplied with the switchgear

7.5.3.5 Bolts nuts and washers shall be hot dipped galvanized

7.5.3.6 Adequately rated lifting eyes shall be provided to allow the completely

assembled switchgear (fitted with surge arresters and external voltage sensors

(if applicable)) to be lifted without recourse to a sling spreader. The inside

diameter of the lifting eyes shall be a minimum of 25mm.

7.5.4 Earthing Arrangement

7.5.4.1 An M8 or larger earth stud welded to main tank shall be provided in an

accessible position.

7.5.5 Switchgear Terminations

7.5.5.1 Terminations

A fully insulated termination shall be provided by design or via the use of

appropriate insulation guards

7.5.6 Terminals

7.5.6.1 The terminals shall be suitable to accept aluminium or copper conductors

7.5.7 Bushings

7.5.7.1 Material

Details of the external insulation material shall be provided in the tender

documentation. Preference will be for bushings manufactured of a composite

material such as cycloaliphatic epoxy.

7.5.7.2 Creepage

The switchgear .shall be suitable for application in areas with very heavy pollution

levels as defined by IEC 60815.

Minimum creepage will be 31mm / kV

7.5.7.3 Profile

(a) Bushing profile characteristics shall comply with the guidelines of annex D of

IEC 60815.

(b) Details of the critical dimensions and ratios, as defined in annex D of IEC

60815, shall be provided in the tender documentation.

130 | P a g e

7.5.8 Surge Arrester Mounting

7.5.8.1 Mounting brackets for surge arresters shall be provided on the source and load

side of the recloser, adjacent to the bushings.

7.5.9 Current Transformers

7.5.9.1 The switchgear shall be supplied with three (one per phase) current

transformers.

7.5.9.2 The current transformers with a minimum class of class 5P15 as defined in

IEC 60044 shall be preferred.

7.5.10 Voltage Sensors

7.5.10.1 The switchgear shall be supplied with six voltage sensors (e.g. VTs,

CVTs, etc.), one per phase on the source and the load side.

7.5.10.2 It is preferable that the voltage sensors are an integral part of the

switchgear.

7.5.10.3 The accuracy of the total voltage measurement system shall not exceed

3%

7.5.11 Control Cable

7.5.11.1 An ultraviolet resistant cable, minimum 7m long, shall be provided to

connect the switchgear to the control unit.

7.5.11.2 Robust, multi-pin, weatherproof connectors shall be provided on both ends

of the control cable.

7.5.12 Rating Plate

7.5.12.1 Each switch shall bear a rating plate of an intrinsically corrosion-resistant

material, indelibly marked with the sea-level rating for which the equipment

has been type tested. The rating plate shall be indelibly marked with:

(a) the manufacturer's name;

(b) the equipment type designation and serial number of the auto-recloser;

(c) the mass, in kilograms;

(d) the date of manufacture; and

(e) Frequency

(f) Rated Voltage Ur

(g) Lightning Impulse Withstand Voltage Up

(h) Rated Current Ir

(i) Rated Breaking Current Isc

(j) Rated Making Current Ima

(k) Rated Short Time Withstand Current Ik

(l) Rated Duration of Short Circuit tk

131 | P a g e

7.5.13 Maintenance & Inspection

7.5.13.1 Tenderers shall provide all information regarding the inspection, testing,

and maintenance required. Preference will be given to low maintenance

solutions. Tenderers shall state required maintenance intervals and provide list

of spare parts necessary for maintenance activities.

7.5.13.2 The equipment shall incorporate a system that provides indication of the

approximate remaining life of the interrupters. This information shall also be

available via SCADA for maintenance planning purposes

7.5.13.3 Switchgear containing SF6 shall have gas pressure measurement and

indication. The switchgear shall not be able to be opened / tripped or closed

when SF6 gas pressure is below the safe level for operation.

7.5.13.4 It shall be possible to disconnect the control cable at the control unit while

the switchgear is energised, live, and carrying load, without causing damage

or mal-operation. Removing or connecting the control cable while the

switchgear is in service shall not result in the switchgear changing

open/closed state. The system shall also be such that it ensures that CTs are

not open-circuited.

7.5.14 Test Sets / Tank Simulators

7.5.14.1 All devices with electronic controllers shall have a suitable tank simulator

for testing and commissioning.

7.5.14.2 Tank simulators shall be supplied with all required cables for connection

to switchgear.

7.5.14.3 Tank simulators shall be supplied with open/close contacts for switchgear

status.

7.5.14.4 Tank simulators shall be capable of secondary injection from a separate

piece of test equipment via banana plug fittings. Tanks simulators shall be

capable of simultaneous injection via 3 current inputs and 6 voltage inputs to

simulate 3 phase network events.

7.5.14.5 Preference will be given to equipment that can simulate voltages and

currents in the simulator / switchgear to reduce or avoid the requirement for

secondary injection.

132 | P a g e

7.5.15 Control units

The Control unit shall be a microprocessor-based electronic device that interfaces the

power equipment to a control system. It shall include all the functions required to monitor

and control the switchgear. It shall include an RTU for SCADA communications.

7.5.15.1 Material & Finish

a) The control cabinet shall be manufactured from stainless steel of grades

304 or 316. Strong preference will be given to items manufactured from

316 grade stainless steel.

b) The mounting bracket shall be made stainless steel of grades 304 or 316.

133 | P a g e

7.5.16 Mounting Arrangement

7.5.16.1 The control cabinet shall be easily removable for workshop repair

purposes.

7.5.16.2 The cabinet shall be supplied with a mounting bracket.

7.5.16.3 The mounting bracket shall have at least two, vertically spaced, mounting

holes. The holes shall be designed such that it will be possible to slide the

cabinet into position without having to remove the pole mounting bolts (or

coach screws).

7.5.16.4 The mounting bracket shall have at least two sets of, vertically spaced,

slots for temporary mounting by means of straps.

7.5.17 Earthing Arrangement

7.5.17.1 Control cabinets shall be provided with an M8 or larger earth stud.

7.5.18 Construction

7.5.18.1 The control cabinet shall be separate from the switchgear (i.e. the

switchgear and control unit shall not be integrated into a single device)

7.5.18.2 Cabinets shall be protected from dust and water ingress to achieve an IP

rating of IP 65 or better as per IEC 60529

7.5.18.3 The main electronics compartment shall be protected from dust and water

ingress to achieve an IP rating of IP 65 or better as per IEC 60529.

7.5.18.4 Cabinets shall be designed and internally treated to prevent moisture

condensation.

7.5.18.5 All metal components of the control cabinet shall be electrically bonded.

7.5.18.6 Provision shall be made in the cabinet to mount the user’s data

communication equipment.

7.5.18.7 The layout of the cabinet shall ensure easy accessibility to the user’s

communications equipment.

7.5.19 Door

7.5.19.1 The cabinet shall have a hinged door.

7.5.19.2 The door shall be fitted with a robust fastening arrangement which can be

locked with a padlock that has a shackle of 8 mm diameter.

7.5.19.3 The door shall be provided with three point locking.

7.5.19.4 Means shall be provided to either secure the door in a fully open position

(90° or more), or to easily remove (without the use of tools) the door

completely during maintenance or similar activities.

7.5.19.5 Good electrical contact shall be maintained between the door and the rest

of the cabinet at all times (excluding the condition when the door is

completely removed).

7.5.19.6 The cubicle shall be alarmed such that when the door is opened a SCADA

alarm will be generated.

134 | P a g e

7.5.20 Cable Entry

7.5.20.1 The cabinet shall make provision for bottom entry of at least three cables.

7.5.20.2 A suitable arrangement shall be provided to earth the gland plate.

7.5.20.3 6.6.3 The holes in the blanking plate shall be blanked off with blanking

plugs that are bolted or screwed in to position.

7.5.20.4 The control cabinet shall be fitted with external antenna connectors.

135 | P a g e

7.5.21 Power Supply

7.5.21.1 The control unit shall have an integral power supply.

7.5.21.2 The capacity of the power supply shall be rated to power all the electronic

modules, operate the switchgear (tripping/opening and closing) and power the

data communication equipment.

7.5.21.3 Steps shall be taken to minimise the device’s power consumption.

7.5.21.4 Adequately rated miniature circuit-breakers shall be provided for

individually isolating the control from the following:

7.5.21.5 Auxiliary Supply

7.5.21.6 Battery Supply

7.5.22 Power Supply Input

7.5.22.1 The auxiliary supply will be derived from an external power source.

7.5.22.2 The required supply shall be one of the following:

7.5.22.3 110 V (±10%) AC at a frequency of 50 Hz;

7.5.22.4 240 V (±10%) AC at a frequency of 50 Hz;

7.5.22.5 The device shall provide a visual indication, on the control panel and in

the event log, of the status of the auxiliary supply.

7.5.22.6 An auxiliary supply fail function shall be provided; it shall operate an

alarm output.

7.5.22.7 Loss or restoration of the auxiliary supply voltage, and under-voltage

conditions in the auxiliary supply shall not result in damage or spurious

operation of the equipment.

7.5.23 Power Supply Protection

7.5.23.1 The power supply shall include the necessary over-current protection to

protect the supply from current excursions.

7.5.23.2 The use of fuses for over-current protection on the auxiliary input

circuit(s) is not acceptable.

7.5.23.3 The power supply shall include the necessary surge arresters and/or

voltage limiting devices to inhibit damage due to voltage surges. (Surge

protected up to 20kV, in compliance with IEC60255-5)

7.5.24 Battery Backup Supply

7.5.24.1 A battery backup supply consisting of batteries and a constant voltage

battery charger, with current limiting, shall be provided with the control unit.

7.5.24.2 The Battery standby time shall be a minimum of 24h, allowing for the

following:

(a) Ten switchgear operations;

(b) 3Ah for the communications device

136 | P a g e

7.5.24.3 The battery charger shall be capable of recharging the battery from flat to

80% of its capacity within 15 hours

7.5.24.4 The switchgear shall be prevented from operating if the system does not

have enough stored energy to complete the operation. Close operations will

also be prevented if the system does not have enough stored and complete the

close operation an immediate trip operation.

7.5.24.5 Batteries shall be automatically disconnected at the manufacturer’s

specified minimum voltage and automatically reconnected when auxiliary

power is restored.

7.5.24.6 The minimum operational battery life expectancy (to 80% of rated

capacity at –10˚C) shall exceed 3 years.

7.5.24.7 Provision shall be made for an orderly shutdown when the battery voltage

reaches the manufacturer’s specified minimum limit.

7.5.25 Self-Monitoring

7.5.25.1 The battery charging system shall be temperature compensated

7.5.25.2 The battery system shall incorporate a battery test facility. During the test

the auxiliary power supply will be disconnected and a load placed on the

battery, rate of voltage drop and voltage recovery time etc. shall be analysed

to determine the health of the battery. The battery test shall be configurable to

occur periodically and shall be delayed during an operation or when the

auxiliary supply has failed.

7.5.25.3 The power system shall incorporate means to prevent deep discharge of

the batteries

7.5.25.4 The power supply shall deliver the following status to the SCADA.

7.5.25.5 Battery disconnected;

7.5.25.6 Absence of power input / Auxiliary Supply Fail

7.5.25.7 Battery Low volts

7.5.25.8 Battery Low Capacity (Low Power Mode)

7.5.25.9 Battery End of Life (Battery Test Fail)

7.5.25.10 Electronic modules shall perform continuous diagnostic monitoring and

shall contain hardware and software watchdog checking.

7.5.26 EMC

7.5.26.1 EMC testing shall be effected as per the Type Test Requirements detailed

below.

137 | P a g e

7.5.27 Cyber security

7.5.27.1 The load break switches/sectionalizers control units shall be provided to

respect the same cyber security requirements as the RTUs described in 2.8 of

“Part 1 for ground mounted substations remote terminal units”.

7.5.28 Interoperability

7.5.28.1 Preference will be given to providers whose control unit is common

between reclosers and LBS and which do not require alternative firmware to

be loaded in the controller, rather the controller shall automatically detect the

switchgear type and display the appropriate settings and configuration screens.

7.5.29 Configuration Software & Engineering Access

7.5.29.1 The switchgear shall be fully configurable from a PC, utilising the

configuration software.

7.5.29.2 A configuration port shall be provided to facilitate remote configuration

via standard Data Communication Equipment.

7.5.29.3 The configuration port shall be an EIA-232 port, a USB port or an

Ethernet port.

7.5.29.4 The configuration software shall be compatible with Microsoft Windows

Operating System 7

7.5.29.5 Configuration software is regarded as an integral part of the offer and shall

be provided at no additional charge.

7.5.29.6 It shall be possible to perform future controller firmware upgrades via the

local communication ports.

7.5.29.7 Engineering access shall be possible locally and remotely using

appropriate communications media

7.5.29.8 Units shall support both engineering and SCADA access on a single

Ethernet port. Neither communication shall interfere with the other

7.5.29.9 It shall be possible to change settings by discreet functions for example it

shall be possible to write all protection settings without affecting telemetry

settings or operator settings etc.

138 | P a g e

7.5.30 Human Machine Interface

7.5.30.1 The operator interface shall be designed for ease of operation to minimise

training and avoid operator error.

7.5.30.2 Engineering access to all configuration parameters shall be possible via an

easy to use menu with dedicated menu navigation buttons. Operator access to

all status indicators, operator controls and logged data will be possible via the

operator interface.

7.5.30.3 The operator interface shall provide a facility to electrically disable any

electrical operation of the switchgear. Disabling circuits shall be by physically

disconnecting the circuit from the close energy source.

7.5.30.4 Trip/Open operation shall be via a dedicated green button. This button

shall also include status indication. (See Appendix 1)

7.5.30.5 Close operation shall be via a dedicated red button. This button shall also

include status indication. (See Appendix 1)

7.5.30.6 Local Controls & Indications

7.5.30.7 Appendix 1 details the minimum requirements

7.5.30.8 A customer configuration utility will be provided to allow customisation

of status indications and command buttons on the HMI. The configuration

utility will allow modification of the lamp and button text labels, lamp colours

and logic functions driving the lamp output. It will also be possible to assign

different functions to the command buttons.

7.5.31 Analogue measurement requirements

7.5.31.1 Measurement shall be done with one of the following methods:

(a) three-phase-3-wire method; and

(b) or the three-phase-4-wire method

Quantities to be measured/calculated with specified accuracy are:

r.m.s. phase-to-phase and phase-to-ground voltage

of all three phases

±2.5%;

Positive phase sequence voltage ±2.5%;

Negative phase sequence voltage ±2.5%;

Zero phase sequence voltage ±2.5%;

r.m.s current per phase (within rated current range) ±2.5%;

Earth Current ±2.5%;

Positive phase sequence current ±2.5%;

Negative phase sequence current ±2.5%;

Three phase active power in kW ± 5%;

Three phase reactive power in kVARs ± 5%;

Total three-phase active energy in kWh ± 5%;

Power factor ± 5%;

Maximum demand ± 5%;

139 | P a g e

7.5.31.2 The real power energy and maximum demand measurement shall be

integrated with respect to time. Energy values shall be calculated with

selectable time integration periods of 5 min, 15 min, 30 min or 60 min. The

data buffer shall work on the FIFO principle and a minimum size for the data

buffer shall store values for a minimum of 4 months on the 30 minutes

integration period.

7.5.31.3 The switchgear and Control element shall have the facilities to record the

cumulative number and duration of outages. The information shall be

assessable locally or remotely via telemetry messaging to a SCADA system.

The following parameters shall be recorded:

(a) Cumulative total number of outages;

(b) Cumulative total outage duration; and

(c) Time and duration of each outage in the form of an event log.

7.5.31.4 A Waveform Capture feature shall be provided. Triggered when the

recloser trips or closes, the control element shall capture the source side phase

voltages, load side phase voltages, phase currents and earth current. The

captured waveforms shall include pre-trigger and post-trigger data. The

captured data shall be available via PC for off line display and analysis.

7.5.31.5 Harmonics to the 16 and the Total Harmonic Distortion (THD) shall be

provided for the phase currents, source side voltages and load side voltages.

The captured harmonics shall be available via PC for off line display and

analysis.

7.5.31.6 The magnitude and the phase angle between the corresponding voltages

and currents of the analogues listed shall be displayed:

(a) Positive phase sequence voltage,

(a) Negative phase sequence voltage,

(b) Zero phase sequence voltage,

(c) Positive phase sequence current,

(d) Negative phase sequence current, and

(e) Zero phase sequence current.

7.5.32 Protection requirements

7.5.32.1 General Requirements

The control unit shall provide the following protection features.

(a) Phase over current

(b) Earth Fault

(c) Sensitive Earth Fault

(d) Negative Phase Sequence

(e) Directional Phase over current

(f) Directional Earth Fault

(g) Directional Sensitive Earth Fault

140 | P a g e

(h) Directional Negative Phase Sequence

(i) Under voltage

(j) Over voltage

(k) Under Frequency

(l) Over Frequency

(m) Loss of Phase

7.5.32.2 Phase Over Current Protection Requirements

(a) The minimum setting range for Pickup shall be 20-800A

(b) The Pickup setting range shall be user selectable in steps of 5A or less

(c) Phase Overcurrent shall support both definite time and IDMT characteristics.

(d) The minimum Setting Range for the Definite Time element shall be 0.02s-10s.

(e) The Definite Time Setting Range shall be user selectable in steps of 20ms or

less

(f) An Instantaneous characteristic shall be provided.

(g) An instantaneous characteristic shall be selectable either as the only curve for

the selected trip or as an overlay on a definite time characteristic

(h) The following IDMT characteristics shall be supported: normal inverse (NI),

very inverse (VI) and extremely inverse (EI) in accordance with IEC 60255,

standard moderately inverse, very inverse and extremely inverse in accordance

with IEEE C37.112. It is preferable that the relay also supports traditional TCC

curves.

(i) The minimum setting range for Pickup shall be 20-800A.

(j) The pickup setting range shall be user selectable in steps of 5A or less

(k) A threshold or pick up multiplier shall be provided.

(l) The minimum setting range for the Pick Up Multiplier shall be 1.0-5.0

(m) The Pick Up Multiplier setting range shall be user selectable in steps of 0.1 or

less

(n) The minimum setting range for the IDMT characteristic Time Multiplier shall

be 0.1 –2. A wider range is preferable.

(o) The IDMT characteristic Time Multiplier setting range shall be user selectable

in steps 0.05 or less.

(p) An instantaneous characteristic shall be selectable either as the only curve for

the selected trip or as an overlay on an inverse time curve.

(q) IDMT characteristics shall be configurable with a Minimum Time Modifier.

The minimum setting range for the Minimum Time Modifier shall be 0 – 2s

(r) The Minimum Time Modifier setting range shall be user selectable in steps of

0.05s or less.

(s) IDMT characteristics shall be configurable with a Maximum Time modifier.

(t) The minimum setting range for the Maximum Time Modifier shall be 0.2 – 10s.

(u) The Maximum Time Modifier setting range shall be user selectable in steps of

0.1s or less.

(v) IDMT characteristics shall be configurable with an Additional Time Modifier.

(w) The minimum setting range for the Additional Time Modifier shall be 0 – 2s

141 | P a g e

(x) The Additional Time Modifier setting range shall be user selectable in steps of

0.05s or less.

(y) An Additional Time modifier shall also be supported.

(z) Additional time shall be selectable over the range 0 – 2s with a 0.01s resolution.

7.5.32.3 Earth Over Current Protection Requirements

(a) The minimum setting range for Pickup shall be 20-800A

(b) The Pickup setting range shall be user selectable in steps of 5A or less

(c) Earth Overcurrent shall support both definite time and IDMT characteristics.

(d) The minimum Setting Range for the Definite Time element shall be 0.02s - 10s

(e) The Definite Time Setting Range shall be user selectable in steps of 20ms or

less

(f) An Instantaneous characteristic shall be provided.

(g) An instantaneous characteristic shall be selectable either as the only curve for

the selected trip or as an overlay on a definite time characteristic

(h) The following IDMT characteristics shall be supported: normal inverse (NI),

very inverse (VI) and extremely inverse (EI) in accordance with IEC 60255,

standard moderately inverse, very inverse and extremely inverse in accordance

with IEEE C37.112. It is preferable that the relay also supports traditional TCC

curves.

(i) A threshold or pick up multiplier shall be provided.

(j) The minimum setting range for the Pick Up Multiplier shall be 1.0-5.0

(k) The Pick Up Multiplier setting range shall be user selectable in steps of 0.1 or

less

(l) The minimum setting range for the IDMT characteristic Time Multiplier shall

be 0.1 –2. A wider range is preferable.

(m) The IDMT characteristic Time Multiplier setting range shall be user selectable

in steps 0.05 or less.

(n) An instantaneous characteristic shall be selectable either as the only curve for

the selected trip or as an overlay on an inverse time curve

(o) IDMT characteristics shall be configurable with a Minimum Time Modifier.

(p) The minimum setting range for the Minimum Time Modifier shall be 0 – 2s

(q) The Minimum Time Modifier setting range shall be user selectable in steps of

0.05s or less.

(r) IDMT characteristics shall be configurable with a Maximum Time modifier.

(s) The minimum setting range for the Maximum Time Modifier shall be 0.2 – 10s

(t) The Maximum Time Modifier setting range shall be user selectable in steps of

0.1s or less.

(u) IDMT characteristics shall be configurable with an Additional Time Modifier.

(v) The minimum setting range for the Additional Time Modifier shall be 0 – 2s

(w) The Additional Time Modifier setting range shall be user selectable in steps of

0.05s or less.

(x) An Additional Time modifier shall also be supported. Additional time shall be

selectable over the range 0 – 2s with a 0.01s resolution.

142 | P a g e

7.5.32.4 NPS Over Current Protection Requirements

(a) The minimum setting range for Pickup shall be 2-800A

(b) The Pickup setting range shall be user selectable in steps of 1A.

(c) NPS Overcurrent shall support both definite time and IDMT characteristics.

(d) The minimum Setting Range for the Definite Time element shall be 0.02s- 10s

(e) The Definite Time Setting Range shall be user selectable in steps of 20ms or

less

(f) An Instantaneous characteristic shall be provided.

(g) An instantaneous characteristic shall be selectable either as the only curve for

the selected trip or as an overlay on a definite time characteristic

(h) The following IDMT characteristics shall be supported: normal inverse (NI),

very inverse (VI) and extremely inverse (EI) in accordance with IEC 60255,

standard moderately inverse, very inverse and extremely inverse in accordance

with IEEE C37.112. It is preferable that the relay also supports traditional TCC

curves.

(i) A threshold or pick up multiplier shall be provided.

(j) The minimum setting range for the Pick Up Multiplier shall be 1.0-5.0

(k) The Pick Up Multiplier setting range shall be user selectable in steps of 0.1 or

less

(l) The minimum setting range for the IDMT characteristic Time Multiplier shall

be 0.1 –2. A wider range is preferable

(m) The IDMT characteristic Time Multiplier setting range shall be user selectable

in steps 0.05 or less.

(n) An instantaneous characteristic shall be selectable either as the only curve for

the selected trip or as an overlay on an inverse time curve

(o) IDMT characteristics shall be configurable with a Minimum Time Modifier.

(p) The minimum setting range for the Minimum Time Modifier shall be 0 – 2s

(q) The Minimum Time Modifier setting range shall be user selectable in steps of

0.05s or less.

(r) IDMT characteristics shall be configurable with a Maximum Time modifier.

(s) The minimum setting range for the Maximum Time Modifier shall be 0.2 – 10s

(t) The Maximum Time Modifier setting range shall be user selectable in steps of

0.1s or less.

(u) IDMT characteristics shall be configurable with an Additional Time Modifier.

(v) The minimum setting range for the Additional Time Modifier shall be 0 – 2s

(w) The Additional Time Modifier setting range shall be user selectable in steps of

0.05s or less.

7.5.32.5 User Defined Curves

Relays will be equipped with a function to create at least 3 user defined IDMT

curves.

7.5.32.6 SEF Protection Requirements

(a) The SEF element shall support a definite time characteristic.

143 | P a g e

(b) The SEF element shall support IDMT characteristics.

(c) The SEF function shall be equipped with harmonic filtering to prevent operation

when harmonics are present in the primary residual earth currents. A low-pass

filter shall be supplied, with:

(d) 2nd harmonic rejection > 6: 1;

(e) 3rd harmonic rejection > 50: 1.

(f) The SEF shall be settable from 4-20A in 1A steps.

(g) The minimum Setting Range for the Definite Time element shall be 0.1s- 30s

(h) The Definite Time Setting Range shall be user selectable in steps of 100ms or

less

(i) The SEF element shall support an IDMT characteristic

(j) Where IDMT characteristics are supported, the following IDMT characteristics

shall be supported: normal inverse (NI), very inverse (VI) and extremely

inverse (EI) in accordance with IEC 60255, standard moderately inverse, very

inverse and extremely inverse in accordance with IEEE C37.112. It is preferable

that the relay also supports traditional TCC curves.

(k) Where IDMT characteristics are supported, a threshold or pick up multiplier

shall be provided.

(l) Where IDMT characteristics are supported, the minimum setting range for the

Pick Up Multiplier shall be 1.0-5.0

(m) Where IDMT characteristics are supported, the Pick Up Multiplier setting range

shall be user selectable in steps of 0.1 or less

(n) Where IDMT characteristics are supported, the minimum setting range for the

IDMT characteristic Time Multiplier shall be 0.1 –2. A wider range is

preferable

(o) Where IDMT characteristics are supported, the IDMT characteristic Time

Multiplier setting range shall be user selectable in steps 0.05 or less.

(p) Where IDMT characteristics are supported, an Instantaneous characteristic

shall be provided.

(q) Where IDMT characteristics are supported, an instantaneous characteristic shall

be selectable either as the only curve for the selected trip or as an overlay on an

inverse time curve

(r) Where IDMT characteristics are supported, the IDMT characteristics shall be

configurable with a Minimum Time Modifier.

(s) Where IDMT characteristics are supported, the minimum setting range for the

Minimum Time Modifier shall be 0 – 2s

(t) Where IDMT characteristics are supported, the Minimum Time Modifier

setting range shall be user selectable in steps of 50ms or less.

(u) Where IDMT characteristics are supported, the IDMT characteristics shall be

configurable with a Maximum Time modifier.

(v) Where IDMT characteristics are supported, the minimum setting range for the

Maximum Time Modifier shall be 0.2 – 10s

(w) Where IDMT characteristics are supported, the Maximum Time Modifier

setting range shall be user selectable in steps of 0.1s or less.

(x) Where IDMT characteristics are supported, the IDMT characteristics shall be

configurable with an Additional Time Modifier.

144 | P a g e

(y) Where IDMT characteristics are supported, the minimum setting range for the

Additional Time Modifier shall be 0 – 2s

(z) Where IDMT characteristics are supported, the Additional Time Modifier

setting range shall be user selectable in steps of 0.05s or less.

7.5.32.7 Broken Conductor Protection

(a) Broken conductor protection shall be current based and shall be able to detect a

broken conductor downstream (in the direction of the power flow). A Broken

Conductor shall be detected by comparing the ratio of negative phase sequence

current to positive phase sequence current.

(b) The Broken Conductor element shall support a definite time characteristic.

(c) The minimum Setting Range for the Definite Time element shall be 0.2s- 120s

(d) The Definite Time Setting Range shall be user selectable in steps of 100ms or

less

(e) The detection setting (Inps / Ipps) shall be settable over the range 0.1 – 1.

(f) The Broken Conductor setting ratio shall be selectable in steps of 0.1 or less.

7.5.32.8 Protection Reset

It is preferable that the drop off current is less than the Pick Up current.

(a) The Reset Threshold shall be configurable in the range 10%-100% in steps of

1%.

(b) Where the reset threshold is not configurable the ratio of drop-off current to

pick-up current shall be a maximum of 95 % and a minimum of 85% for all

protection functions.

(c) Once pick up has occurred, shall the measured current fall below the Pick Up

Threshold but remain above the reset threshold the protection timing will be

paused and re-started if the current once again exceeds the Pick Up.

(d) A configurable protection reset time or time characteristic shall be provided.

(e) As a minimum definite characteristic configurable in 10ms steps from 10ms to

10s shall be provided.

(f) Preference will be given to devices which simulate the reset time of an

electromechanical protection relay. The preferred method of disk reset shall be

according to IEC 60255-4 Class A, Class B, Class C, Long-time inverse and

Short-time inverse reset curves

7.5.32.9 Inrush Restraint

(a) A harmonic current inrush restraint function shall be supplied. Transformer

magnetising current is characterised by a significant percentage of second for

the inrush restraint fee trigger order harmonic current relative to the

fundamental current. The trigger for the inrush restraint feature shall not be zero

amps current but rather a user configurable percentage of second order

harmonic current relative to the fundamental current.

145 | P a g e

(b) The minimum range for the restraint period, the Inrush Restraint Time, shall be

50ms to 30s

(c) The Inrush Restraint Time shall be user selectable in steps of 10ms or less

(d) The minimum range for the Inrush Restraint Multiplier shall be 1 to 30

(e) The Inrush Restraint Multiplier shall be user selectable in steps of 0.1 or less

(f) The minimum range for the percentage of second order harmonic relative to the

fundamental, the Inrush Restraint Threshold, shall be 20% to 200%

(g) The Inrush Restraint Threshold shall be user selectable in steps of 1% or less

7.5.32.10 Cold Load

(a) A cold load pick-up (CLP) feature shall be provided that allows user selectable

modification of protection element characteristics under conditions of system

power restoration.

(b) The elements to be modified by the cold load function shall be selectable.

(c) This CLP feature shall allow the Pick Up current of the selected elements to be

raised to a user configured multiple of the Pick Up current, (Cold Load

Multiplier), in a linear fashion over a user selectable time (Cold Load Time)

(d) The minimum setting range for the Cold Load Time shall be 5 -60 minutes

(e) The Cold Load Time shall be user configurable in steps of 5 minutes or less.

(f) The minimum setting range for the Cold Load Multiplier shall be 1 -4.

(g) The Cold Load Multiplier shall be user configurable in steps of 0.1.

(h) The vendor may propose an alternative arrangement for consideration by the

purchaser.

7.5.32.11 Directional Protection

(a) A Directional Protection feature shall be provided.

(b) The minimum time to determine fault direction for Phase Overcurrent, Earth

Fault and NPS shall not exceed 50ms

(c) The relay minimum time to determine fault direction for SEF shall not exceed

500ms

(d) The relay shall have independent settings for each element for the following

quantities

i. Characteristic Fault Angle

ii. Forward Sector Width

iii. Reverse Sector Width

iv. Low Polarising Voltage Threshold

v. Low Polarising Voltage Action

(e) The minimum setting range for the Characteristic Fault Angle shall be -179˚ to

180 ˚

i. The Characteristic Fault Angle shall be user configurable in steps of

1˚

ii. The minimum setting range for the for Forward and Reverse Sector

iii. Widths shall be 45˚-90˚

iv. The Forward and Reverse Sector Widths shall be user configurable

in steps of 1˚

146 | P a g e

v. The minimum setting range for the Low Polarising Voltage

Threshold shall be 300-15000 volts

7.5.32.12 High Current Lockout

(a) A feature to lockout the recloser to prevent reclosing on high energy faults

shall be provided. This feature will allow the user to configure a maximum

fault current level which if exceeded will cause the recloser to lockout after

the trip event.

7.5.32.13 Auto-reclose operation parameters

(a) The number of sequential trips to reach lockout shall be selectable to be 1,

2, 3 or 4.

(b) The minimum setting range for Sequence Reset Time shall be selectable

from 3s to 120s

(c) The Sequence Reset Time shall be configurable in steps of 1 s or less.

(d) Dead times shall ideally be individually selectable for SEF, NPS and the

combination of over-current and earth fault functions.

(e) The minimum setting range for the first dead time shall be 0.5s to 180s

(f) The minimum setting range for subsequent dead times shall be 2s to 180s.

(g) Dead times shall be configurable in steps of 0.5s or less.

(h) An operator close command initiated locally or remotely during a dead time

shall result in lockout if a fault is present upon closure.

(i) A user selectable Dead Lockout feature shall be provided to prevent a

reclose attempt when the source and load side terminals of the recloser are

dead.

7.5.32.14 Sequence Co-Ordination

(a) A Sequence co-ordination feature shall be provided to ensure trip-close

sequence coordination for combinations of rapid and delayed protection

operations applied to Auto-reclosers in series. The Sequence co-ordination

functionality shall be such that:

i. The sequence co-ordination feature shall be independently

selectable for each protection setting group.

ii. The sequence co-ordination feature will cause the circuit breaker to

step to the next count in the reclose sequence on reset of all

protection elements whether or not the recloser tripped

iii. For multiple pick up excursions, the recloser shall advance

sequentially to the last programmed trip and this characteristic shall

remain the active until the sequence resets.

147 | P a g e

7.5.32.15 Non-Auto Mode

(a) When the Auto-Reclosing function is OFF or disabled a separate protection

characteristic, Non-Auto or Single Shot Mode, will be selected for all over

current elements. This characteristic will be fully configurable as per trips

1-4

7.5.32.16 Operator Close Mode

(a) An operator close, whether effected locally or remotely, shall always select

the Non-Auto or Single Shot Mode Characteristic.

(b) This characteristic will remain active (Auto reclose will be prevented) for a

user configurable time, the Non-Auto or Single Shot Timer.

(c) The minimum setting range for the Non-Auto or Single Shot Timer shall be

0 -60s

(d) If 0 is selected, and Auto Reclose Mode is ON and if a fault exists on the

line the recloser will execute the full configured Auto Reclose sequence

(e) The Non-Auto or Single Shot Timer shall be user configurable in steps of

1s or less.

7.5.32.17 Frequency Protection Requirements

(a) The over frequency protection function shall detect frequencies above the

normal system frequency.

(b) The minimum setting range for the Over Frequency Trip Threshold shall be

from the nominal system frequency to the nominal system frequency plus

5Hz.

(c) The Over Frequency Trip Threshold shall be user configurable in steps not

greater than of 0.1Hz.

(d) The Over Frequency protection function shall use a Definite Time

Characteristic.

(e) The minimum setting range Over Frequency Trip Delay Time shall be 40ms

-3s or 2 cycles – 150cycles.

(f) The Over Frequency Trip Delay Time shall be user configurable in steps of

20ms or less.

(g) The Under Frequency protection function shall detect frequencies below the

normal system frequency.

(h) The minimum setting range for the Under Frequency Trip Threshold shall

be from the nominal system frequency minus 5Hz to the nominal system

frequency.

(i) The Under Frequency Trip Threshold shall be user configurable in steps not

greater than of 0.1Hz.

(j) The Under Frequency protection function shall use a Definite Time

Characteristic.

(k) The minimum setting range Under Frequency Trip Delay Time shall be

40ms -3s or 2 cycles – 150cycles.

148 | P a g e

(l) The Over Frequency Trip Delay Time shall be user configurable in steps of

20ms or less.

(m) It shall be possible to separately enable / disable the Over and Under

Frequency protection functions.

(n) An Auto close function shall be provided to enable the auto-recloser to close

once the frequency returns to normal.

(o) The minimum setting range for the Auto Close Delay Time shall be 1s –

300s

(p) The Auto-Close Delay Time shall be user configurable in steps of 1s or less.

7.5.32.18 Voltage Protection Requirements

(a) The over voltage protection function shall detect voltages above the

nominal phase to earth system operating voltage.

(b) The minimum setting range for the Overvoltage Trip Threshold shall be

110% - 180%,

(c) The Overvoltage Trip Threshold shall be user configurable in steps 5%, or

less.

(d) The Over Voltage protection function shall use a Definite Time

Characteristic.

(e) The minimum setting range Over Voltage Trip Delay Time shall be 0.2s -

60s.

(f) The Over Voltage Trip Delay Time shall be user configurable in steps of

100ms or less.

(g) It shall be possible to configure the over voltage protection function to

protect for over voltage on a single phase, all three phases or the average of

all three phases.

(h) The under voltage protection function shall detect voltages below the

nominal phase to earth system operating voltage.

(i) The minimum setting range for the Under Voltage Trip Threshold shall be

50% - 90%,

(j) The Under Voltage Trip Threshold shall be user configurable in steps 5%,

or less.

(k) The Under Voltage protection function shall use a Definite Time

Characteristic.

(l) The minimum setting range Under Voltage Trip Delay Time shall be 0.2s -

60s.

(m) The Under Voltage Trip Delay Time shall be user configurable in steps of

100ms or less.

(n) It shall be possible to configure the under voltage protection function to

protect for low voltage on a single phase, all three phases or the average of

all three phases.

(o) It shall be possible to separately enable / disable the Over and Under

Voltage Detection functions.

(p) An Auto close function shall be provided to enable the auto-recloser to close

once the voltage returns to normal.

149 | P a g e

(q) The minimum setting range for the Auto Close Delay Time shall be 1s –

300s

(r) The Auto Close Delay Time shall be user configurable in steps of 1s or less.

7.5.32.19 Loss of Phase Protection Requirements

(a) The relay shall be capable of detecting an open circuit upstream. This

feature is typically referred to as Loss of Phase (LOP) Protection.

(b) The recloser shall be configurable to Trip or alarm for a loss of phase

condition.

(c) Loss of voltage on all three phases shall not generate a LOP alarm or LOP

protection trip.

(d) The minimum setting range Loss of Phase Voltage threshold shall be 2000

- 15000V

(e) The Loss of Phase Voltage Threshold shall be configurable in steps of 100V

or less.

(f) When configured to Trip the recloser shall trip to lockout if there is a loss

of voltage on one phase upstream of the recloser.

(g) The Loss of Phase protection function shall use a Definite Time

Characteristic.

(h) The minimum setting range Loss of Phase Time shall be 0.2s -60s.

(i) The loss of Phase Trip Delay Time shall be user configurable in steps of

500ms or less.

(j) Information about LOP operation shall be recorded to include details of the

affected phase(s).

7.5.32.20 Synchronism Check Requirements

(a) The system shall check voltage magnitude, frequency, and voltage phase

angle.

(b) The minimum setting range for the allowed Voltage Magnitude Difference

between terminals of the same phase shall be 0.02PU to 0.3 PU

(c) The Voltage Magnitude Difference shall be configurable in steps not greater

than 0.01 PU

(d) The minimum setting range for the allowed Frequency Variation between

terminals shall be selectable in the range 0.04Hz to 0.12Hz

(e) The allowed Frequency Variation shall be selectable in steps of 0.01Hz

(f) The minimum setting range for the allowed Phase angle variation shall be

selectable in the 6˚ to 45˚

(g) The allowed Phase angle variation shall be configurable in steps of 1˚ or

less.

(h) The relay shall provide a means to compensate for the potential for phase

angle difference between the two sources to alter between the time of

request and the actual time when the contacts first touch. Essentially the

system shall allow for the change in phase angle that may occur during the

mechanism operation time.

150 | P a g e

(i) A close retry time period shall be allowed during which if the sources come

in to sync the switchgear will automatically close.

(j) The minimum setting range for Close Retry Time Period shall be 1s – 300s

(k) The Close Retry Time Period shall be selectable in steps of not greater than

1s

7.5.32.21 Fault Locator

(a) Preference will be given to relays with a function that calculates the distance

to fault following detection of a fault. Details of the proposed system shall

be provided.

7.5.32.22 Circuit Breaker Fail

(a) A Circuit Breaker Fail Alarm feature shall be provided to alert the operator

if the switchgear fails to break all phase currents after a protection trip

operation.

7.5.33 Communications and hardware

7.5.33.1 Remote Terminal Unit RTU

(a) The Control unit shall include a Remote Terminal Unit RTU

(b) The RTU will support telemetry messaging using the DNP3 protocol.

Preference will be given to equipment which also supports IEC 60870-5-

104 IEC 60870-5-101

7.5.33.2 Telemetry Communications Ports

An RS-232 port shall be provided for telemetry communications

(a) A 10Base-T or 100Base-T Ethernet port shall be provided for telemetry

communications

(b) Preference will be given to equipment which provides additional RS232,

RS485, Ethernet or V23 modem ports.

7.5.34 Communications Equipment

7.5.34.1 Provision will be made to mount communications equipment to include

modems or radios in the control box. The available space to mount equipment

will be detailed.

7.5.34.2 Provision shall be made in the bottom entry gland plate for at least two

keyed holes for the external antenna connections.

7.5.34.3 Communications Equipment Power Supply

(a) A user programmable communications equipment power supply shall be

provided.

151 | P a g e

(b) The minimum setting range for the Communications Equipment Power Supply

shall be 10-15V dc

(c) The Communications Equipment Power Supply shall be configurable in steps

of not more than 1V.

(d) The communications equipment power supply shall have a continuous rating of

at least 30W

7.5.35 Remote Controls & Indications

7.5.35.1 The required remote controls, indications and analogues are detailed in

Appendix4

7.5.35.2 The I/O map shall be user configurable to add or delete points

7.5.36 Indications

(a) Each indication shall be configurable to provide time stamping of status

changes with an accuracy of 10ms or better.

(b) Status changes shall be reported and recorded in the event log in the sequence

in which they occur

(c) A facility shall be provided to invert the status of indications

(d) An event buffer to store all changes in configured SCADA points as time-

stamped events shall be provided. The buffer shall have a capacity of at least

250 events.

7.5.37 Controls

(a) The control output sub-system shall support both Direct-Operate and Select-

Before-Operate controls. The selection of type will be made at the master

station.

(b) Failure of any one component shall not result in an undesired control output

(c) It shall be possible to test the control subsystem by issuing a “dummy” control

7.5.38 Counters

(a) At least two counters shall be provided (minimum 16 bits).

(b) Counters shall be stored in non-volatile memory

(c) It shall be possible to assign the counters to count different points in the device

(d) The counters shall have a user configurable report facility (time referenced to

the hour or count based). If the counter’s capacity is exceeded then the

accumulator shall operate in a rollover fashion. It shall be possible to configure

jitter, reporting and other settings per counter.

7.5.39 Analogues

(a) All analogues shall have a resolution of at least 16 bits.

(b) A dead band facility shall be provided to report analogue changes on the

transgression of a configurable setting range

(c) A facility to report the transgression of high and low analogue values as digital

alarms shall be provided.

152 | P a g e

7.5.40 Time Synchronisation Management

7.5.40.1 The control shall be equipped with a battery backed real time clock with

leap year support.

7.5.40.2 It shall be possible to set the clock via the configuration software and via a

DNP3 master to within 1ms of the synchronisation clock.

7.5.40.3 The accuracy of the clock shall be better than 12 (twelve) parts per million

7.5.40.4 The precision of the clock shall be 1 millisecond or better

7.5.40.5 The real time clock battery, or other power source, shall provide at least

20 days of total standby time. The power source shall not need replacing more

often than every ten years.

7.5.41 Custom Logic Functionality

7.5.41.1 Custom Logic inputs and operations

(a) The control system shall provide a CLF (custom logic functionality) to allow

the creation of unique logic status monitoring functions.

(b) It shall be possible to monitor the status of:

i) Digital control data (Switchgear and controller status, Operator control

settings, Protection events, External Inputs & Outputs, and protocol triggers)

ii) Analogue signals (Line Current and Voltage measurement, Counters and

Timers)

(c) It shall be possible to create logic expressions using Boolean Logic operands

such as AND, OR, NOT to evaluate the status of digital and analogue database

values.

(d) It shall be possible to create multiple logic expressions.

7.5.41.2 Utilisation of the Custom Logic functions

(a) The results of the logic expressions shall be available via protocol for additional

indication back to the control centre.

(b) It shall also be possible to display the results of these logic expressions via

LEDs located on the operator interface.

(c) Furthermore the results of the logic expressions shall be available to perform

automatic actions (turn features on/off) and control external equipment.

7.6 TYPE TESTS

All switchgear shall be type tested for the following and the appropriate values shall be stated

in the tender documentation, further details are as appendix 12:

7.6.1 Insulation (dielectric) tests: (IEC62271-111 Clause 6.2)

a) power frequency withstand voltage test

b) Lightning impulse withstand voltage test.

153 | P a g e

7.6.2 Measurement of the resistance of the main circuit (IEC62271-111 Clause 6.4)

7.6.3 Temperature Rise (IEC62271-111 Clause 6.5)

7.6.4 Short-time withstand current & peak withstand current (IEC62271-111 Clause

6.6)

7.6.5 Verification of protection (IEC62271-111 Clause 6.7)

7.6.6 Tightness test (IEC62271-111 Clause 6.8)

7.6.7 EMC test (IEC62271-111 Clause 6.9)

7.6.8 Switching Tests: (IEC62271-111 Clause 6.101)

a) Line charging current

b) Cable charging Current

7.6.9 Making Current Capability: (IEC62271-111 Clause 6.102)

7.6.10 Rated symmetrical interrupting current tests (IEC62271-111 Clause 6.103)

7.6.11 Critical current tests (IEC62271-111 Clause 6.104)

7.6.12 Partial discharge (IEC62271-111 Clause 6.106)

7.6.13 Surge Current Tests (IEC62271-111 Clause 6.107)

7.6.14 Mechanical Duty Test: (IEC62271-111 Clause 6.109)

7.6.15 Ice Loading Test: (IEC62271-111 Clause 6.110)

7.6.16 Internal Arc (IEC62271-200, Sub-clause 6.107. and Annex A)

7.6.17 Mechanical Impact (IEC62271-200, Sub-clause 6.7.)

7.6.18 Control electronic elements surge withstand capability (SWC) tests (IEC62271-

111

7.6.19 Clause 6.111)

7.6.20 EMC Testing as per the table below:

Standard Description Test Level

IEC 61000-4-2 Electrostatic

Discharge

+/- 8kV

+/- 15kV

IEC 61000-4-3 Radiated

Electromagnetic Field

10V/m, 80 MHz - 1000 MHz

3V/m, 1000 MHz - 2700 MHz

10V/m, 1000 MHz - 2700 MHz

IEC 61000-4-4 Fast Transient

+/- 4kV

+/- 4kV

+/- 4kV

+/- 4kV

+/- 4kV

+/- 4kV

+/- 4kV

IEC 61000-4-5 Surge

+/- 4kV line-to-earth, +/- 2kV line-to-

line, 1.25/50usec

+/- 4kV, 1.25/50usec

+/- 4kV, 10/700usec

+/- 4kV, 10/700usec

154 | P a g e

+/- 4kV, 1.25/50usec

+/- 4kV, 1.25/50usec

+/- 4kV, 1.25/50usec

IEC 61000-4-6 Conduced

Disturbances

10V RMS

10V RMS

10V RMS

10V RMS

10V RMS

10V RMS

10V RMS

IEC 61000-4-8

Power Frequency

Magnetic Field 100A/m continuous, 1000A/m for 1s

IEC 61000-4-11 Voltage Dips and

Interruptions

Voltage dips - 0% 1 cycle, 40% for 10

cycles, 70% for 25 cycles, 80% for 250

cycles

Voltage interruptions - 0% for 250 cycles

IEC 61000-4-16

Conducted Common

mode disturbances 0-

150kHz

30V continuous, 300V 1 sec, 50/60Hz

30V continuous, 300V 1 sec, 50/60Hz

IEC 61000-4-18 Damped Oscillatory

Wave

2.5kV Common mode, 1kV diff. @

100kHz and 1MHz

2.5kV common mode @ 100kHz and

1MHz

7.7 ROUTINE TESTS

All switchgear shall be tested for the following and the appropriate values shall be stated in the

tender documentation:

7.7.1 Calibration

7.7.2 Control, secondary wiring

7.7.3 Dielectric withstand test; 1-min. dry power-frequency

7.7.4 Partial discharge test

7.7.5 No load mechanical operation test

7.7.6 Gas leak test where applicable

155 | P a g e

8 REMOTE TERMINAL UNIT (RTU)

8.1 GENERAL REQUIREMENTS

The RTU will allow for the remote control and monitoring of the ground mounted switchgear.

8.2 Scope

The unit shall comprise:

a) Distribution Control Unit with wireless communication to be installed in Medium

voltage distribution substations

b) Fault detection systems with wireless communication (or not) to be installed on

Medium Voltage Overhead Electric networks, as specified in this document,

c) Application software to display the information from these Fault passage indicators or

Distribution control Unit.

8.3 Quality Assurance

The Bidder shall supply documentary proof that the manufacturer possesses ISO 9001

and ISO 14001 Quality insurance certification, from an independent internationally

recognized body, for the design, manufacture and testing of Fault Indicators and remote

monitoring and control equipment for medium voltage lines.

8.4 SPECIFICATIONS OF REMOTE TERMINAL UNIT (RTU)

RTU shall be a microprocessor-based electronic device that interface power equipment to a

control system. It shall include all the functions required to monitor and control MV switchgear

in the MV/LV feeders.

8.5 General characteristics

Dielectric compatibility: IEC60255-5 Insulation: 10kV, surge: 20kV

Electrostatic discharge: IEC6100-4-2 level 4: 15kV in air; 8kV at contact

RF fields: IEC61000-4-3 Level 4: 30V/m

Fast transient: IEC 61000-4-4 Level 3 : ±2kV (5kHz to 100kHz)

Surge: IEC61000-4-5 Level 3 (CM): 2kV

Conducted RF disturbance: IEC61000-4-6 Level 3: 10V (150 kHz to 80MHz)

Power frequency magnetic field: IEC61000-4-8 Level 5: 100 A/m

Pulse magnetic field: IEC61000-4-9 Level 5: 1000 A/m

Damped oscillatory wave: IEC61000-4-12 Level 3 (CM): ±2.5 kV

156 | P a g e

Operating temperature: IEC610068 -40°, to +70°C

Damp heat steady state: IEC610068-2-78 93%, 56 days

Damp heat cycles: IEC60068-2-30 95%, 144h

Salt spray test: IEC60068-2-11 168h

Protection: IEC60529 IP3x (cabinet)

Robustness: IEC62262 IK07 (Cabinet)

8.6 RTU arrangement

The RTU shall be built on a modular flexible architecture.

The RTU shall include:

(a) A main communication unit that supports communication with the SCADA,

communication with devices located in the substations and communication with interfaces

with the switchgears.

(b) One interface and treatment unit per Load break switch in the substation.

(c) A power supply which integrates a 12Vdc battery charger and provides 24Vdc/48Vdc for

the motorisation, 12Vdc for the electronic devices and 12Vdc for the transmission systems.

(d) The RTU shall be expandable by adding modules, the number of modules shall not be

limited and not based on a rack design.

(e) The RTU consumption shall be limited to 10W per substation

8.7 Configuration and maintenance

(a) The RTU shall be configurable locally or/and remotely.

(b) A configuration tool, based on PC, shall be provided for configuration of the RTU. This

tool shall be connected locally or remotely to download and upload the configuration into

the RTUs.

(c) A web server shall be integrated into the RTU communication unit and shall provide

facilities for maintenance, settings including cyber security settings, and historical logs

display. This Web server shall be accessible locally and remotely, by mean of a standard

laptop PC.

(d) Locally, the maintenance tool shall be connected to the RTU by a Wi-Fi or Ethernet

communication port.

(e) The firmware shall be updated either locally or from the central system.

157 | P a g e

8.8 Extension

Optionally the RTU shall be able to provide future extension such as additional I/O, monitoring

and control of LV feeders. Wireless links with these extensions shall be considered as

preferable.

8.9 Functions

8.9.1 Monitoring and control of medium voltage switchgears.

Each medium voltage switchgear along the feeders shall be monitored and controlled by

an interface and treatment unit. It shall be possible to extend the number of monitored and

controlled switchgears by adding one interface modules per switchgear.

The interface with the switchgear shall provide at least:

(a) Switch position (Dual input)

(b) Earth switch position (single or dual input)

(c) Interlocking status (optional input)

(d) Voltage presence ( direct input or calculated by the RTU)

(e) 2 spare inputs

(f) Switch position control (Dual output)

In addition to these direct interfaces with the switchgear, the number of operations shall be

transmitted to the SCADA

The interface shall control the switch motorisation through a dual output which shall

provide the 24Vdc / 48Vdc voltage to the interface relay located into the switchgear.

The control operation shall be secured by a select before execute procedure. The 24Vdc/

48Vdc power supply to the motor shall be activated only during the execute phase.

8.9.2 Fault current detection

Each of the interface and treatment unit shall integrate a fault detection.

Fault current shall be detected according to ANSI standard detection curves:

(a) ANSI 50/51 for phase overcurrent fault detection

(b) ANSI 50N/51N for phase to earth fault detection

(c) ANSI 67 for directional phase overcurrent fault detection

(d) ANSI 67N for directional phase to earth overcurrent fault detection

(e) ANSI 47 for negative sequence overvoltage used to detect broken conductors.

For each detection 2 groups of settings shall be provided.

Permanent, semi-permanent and transient type of fault shall be discriminated and

transmitted to SCADA. The fault detection shall be validated by the absence of voltage on

the MV network.

158 | P a g e

Settings range:

(a) 2 settings shall be possible in each group of settings

(b) Overcurrent from 0,02In to 4 In (DT)

(c) Earth fault : from 0,02In to 1,6 In (DT)

(d) Sensing time : from 50ms to 300s

(e) Setting curves shall comply with DT and IDMT.

The inrush current shall be detected by evaluating the ratio of second harmonic. A delay

applied on the detection sensing time on power recovery is not acceptable.

The fault detector shall be reset by various configurable means:

(a) By a timer delay

(b) On voltage recovery

(c) Manually either from the RTU front panel or from the SCADA

When a fault is detected and validated, it shall be indicated simultaneously by a LED on

the RTU front panel, showing clearly the corresponding feeder, by an event sent to the

SCADA and on an external lamp connected to a dedicated relay output of the RTU

8.9.3 Measurement

The RTU shall provide phase currents and voltage measurement.

Three phase current sensors and one residual current sensor shall be connected to the RTU

interface and treatment unit.

Three phase Low Power Voltage Transformer (LPVT) voltage sensors for voltage

measurement shall be connected to the RTU interface and treatment unit.

All measurement including the calculated active power, reactive power and energy, in the

four quadrants, per feeder shall be compliant with IEC 61557-12.

Accuracy shall be 0.5% for Current and voltage inputs and 1% for power and energy

calculated measurement.

The power shall be delivered as a signed value.

The RTU shall be able to memorise the value of current and voltage before fault detection

or a switch opening.

A 3-wire PT100 sensor input shall be provided in order to measure temperatures such as

ambient air.

159 | P a g e

8.9.4 Power quality

The RTU shall monitor, according to IEC 61000-4-30 class S, harmonics, voltage dip and

swell, voltage interruption and voltage unbalance.

8.9.5 Archives

Events and measurements shall be archived in logs.

Events shall be stored in the archive logs with a time resolution of 1ms, and a

discrimination of 10ms.

The capacity of the logs shall be up to 500,000 events and measurement

All the logs shall be available from a maintenance tool connected to the RTU or sent on

request to the SCADA. The container of the logs shall be configurable and the name of the

logs sent to the SCADA shall be configurable. It shall be formatted as a .csv file.

8.9.6 Automation

For each feeder a Sectionaliser automated function shall be provided. It shall open the

switch automatically during the absence of voltage during recloser cycles. The number of

faults and the cycle duration shall be configurable.

In addition, a general purpose automation language shall be integrated and shall be

compliant with IEC 61131-3 standard.

8.9.7 Local MMI

a) Front panel MMI

On the front panel of RTU, LEDs and push buttons shall provide the following

statuses and controls:

(a) Status of all communication ports

(b) Switch position status

(c) Switch position control. The switch position control shall be validated by

pressing simultaneously two buttons in order to avoid unexpected manual

control orders.

(d) Earth switch position

(e) Fault current detection

(f) Battery and power supplies status

(g) Local/Remote status

(h) Local/Remote control push button

(i) Automation status and control push button

(j) Fault detection reset control push button

The control and status related to each of the switchgear shall be presented in a clear

and ergonomic way, assuming that for each switchgear a clear area is dedicated to

each switchgear on the front panel.

160 | P a g e

b) Other local MMI

Locally, a Web Server interface shall be provided for connection of a laptop PC, a

tablet or a Smartphone in order to access to more details data such as alarms log,

statuses and position, and measurement.

8.9.8 Communication

8.9.8.1 Communication with SCADA

The RTU shall be able to communicate with the SCADA on two channels. In case of

redundancy the SCADA will activate the backup communication channel. The RTU

shall be able to initiate also a communication on the backup channel in case of detection

of inactivity on the main channel.

The RTU shall accept communication with two SCADA systems simultaneously.

8.9.8.2 Protocol

The RTU shall comply with IEC 870-5-104, IEC 870-5-101, and DNP3.0 standard

protocol. The RTU shall support Secure Authentication according to IEC 62351-5.

8.9.8.3 Transmission

The communication system shall be based on UHF radio. The RTU power supply shall

be sized to supply the communication modem.

8.9.8.4 Transmitted data

The RTU shall transmit to the SCADA all the status and measurement. Each data shall

be individually configurable to be sent or not to the SCADA.

The measurement shall be spontaneously sent to SCADA according to configuration

of:

(a) Threshold

(b) Dead band

8.9.8.5 Wi-Fi

A Wi-Fi communication port shall be offered to access locally to the RTU. It shall be

secured by means of

(a) Activation/deactivation from the SCADA

(b) SSID visibility configurable

(c) Passphrase

(d) Automatic disconnection by timeout

161 | P a g e

8.9.8.6 Communication LAN for other devices

In order to ensure that future needs shall be covered, the RTU shall be able to provide

additional communication ports:

(a) Ethernet port

(b) RS232/RS485 port

8.9.9 Power supply

The RTU shall include a power supply which integrates a 12Vdc battery charger.

The battery charger shall be compensated in temperature and protected against deep

discharge and overvoltage. It shall be protected against surge currents by use of for instance

an isolation transformer. A single 12Vdc battery is mandatory in order to limit the

maintenance constraints.

In case of absence of the battery, the power supply shall be able to supply at least the RTU.

The power supply, from the battery voltage, shall provide the following:

(a) 24Vdc/ 48Vdc ± 10% for the motorisation. This voltage shall be connected only

in execute phase.

(b) 12Vdc for the transmission devices.

(c) 12Vdc for the RTU modules.

8.9.9.1 Power supply input

Input voltage: 110Vac/ 230Vac ± 10%

The power supply shall be insulated to 10kV and surge protected up to 20kV, in

compliance with IEC60255-5.

8.9.9.2 Battery

(a) The battery capacity shall maintain a backup time of at least 10 hours for all the

voltage outputs and shall permit 10No. Open/Close cycles of the switchgear.

(b) The single 12Vdc battery shall be periodically checked, and a battery fault shall

be transmitted to the SCADA.

(c) The maximum battery charging time shall be 24hours

8.9.9.3 Monitoring

The power supply shall deliver the following statuses to the SCADA

(a) End of life detection

(b) Battery disconnected

(c) Absence of power input

162 | P a g e

(d) Voltage output faults

(e) Battery fault

(f) Any other data shall be available through a serial link communication.

8.9.10 Cyber security

8.9.10.1 Future proof design

8.9.10.1.1 Remote firmware update

The RTU shall support remote firmware updates

8.9.10.1.2 Centralised RBAC management

The RTU shall be evolutive in order to be compatible with a full centralised

RBAC management in compliance with IEC 62351-9

a) Hardening

(i) Device hardening

Disabled or unused functionality shall not compromise security.

Unnecessary services and programs shall be removed. If removal is not

possible, the unnecessary services and programs shall be disabled.

b) Interface minimization

i) Each interface shall support only the data types and protocols needed to

meet the functional requirements.

ii) Unused interfaces and ports shall be removed. If removal is not possible,

the unused interfaces and ports shall be disabled.

iii) A complete list of supported data types and supported communication

protocols per interface shall be provided.

iv) All hardware interfaces that are used for programming or debugging

shall be completely removed after production.

c) Account hardening

i) The RTU shall not contain active default, guest and anonymous

accounts.

ii) All remote access to root accounts on the RTU shall be disabled.

iii) All Vendor-owned accounts where feasible shall be removed.

iv) The list of all accounts on the RTU shall be provided.

d) Compliance to security standards

The RTU shall follow the IEC 62351 standards and at least:

i) IEC 62351-5: 2013

ii) IEC 62351-8

e) Communication security

The RTU shall support network and transport layer encryption using IPsec.

163 | P a g e

f) Configuration

Access to the RTU by configuration tool shall be possible only through secured

connection: HTTPS for Web server and SSH for console and configuration tool.

g) Access control

i. Role-based Access Control (RBAC)

(a) The RTU shall support the implementation of Role-based Access

Control in compliance with IEC 62351-8.

(b) It shall be possible to configure the privileges of individual roles. It

shall be possible to carry out changes by configuration files

through a secure way.

(c) It shall be possible to define more roles for future applications.

(d) It shall be possible to assign each role individual security

credentials.

(e) It shall be possible to bind roles to individual user accounts on the

RTU.

The minimum following function and data shall be controlled through

RBAC:

(i) Configuration files

(ii) Software update

(iii) User management

(iv) Executing program or shell command

(v) I/O on local maintenance access

(vi) A specific tool shall permit to configure the security policy, role and

password.

ii. Management of Security passwords

(a) The RTU service application shall support individual user

passwords.

(b) Passwords shall be stored together with a salt using an allowed

cryptographic hash function.

(c) The RTU service application shall enforce a high complexity of

passwords.

(d) The RTU shall lock the access after several password error.

iii. User Authentication

(a) The RTU shall authenticate the communication parties on the WAN

interface using a challenge-response protocol based on message

authentication codes The RTU shall terminate the connection if the

user authentication fails.

(b) The RTU shall authenticate the communication parties on the Local

Maintenance interface.

164 | P a g e

(c) It shall be possible to configure the RTU so that it blocks

authentication requests, either temporarily or permanently, from an

account after a number of failed login attempts. The number of

failed login attempts and the time the account is blocked shall be

configurable.

iv. Central management of user account

The RTU shall allow to manage user authentication through a Radius server.

v. Security Log

(a) The RTU shall provide a local audit trail for all security events that

occur.

(b) Log files shall be produced in Syslog format.

(c) Security events shall be logged locally in a dedicated security log

or/and on a SYSLOG server.

vi. Security testing

The RTU shall comply with ACHILLE Level1

8.9.10.1.3 Documentation

i. Secured Versioning

a. All released versions (hardware, firmware, software) of a device or

product shall be uniquely identifiable.

b. Exchangeable hardware modules shall be versioned separately.

ii. Design Documentation

a. The Protocol Implementation Conformance Statement as in IEC 62351

and IEC 60870-5-7 shall be provided on request.

165 | P a g e

9 11kV RING MAIN UNITS (RMUs) There exists RMUs in the KPLC network. These RMUs are modern and have been manufactured

by M/s Lucy Electric, the models are VRN2a.

A number of them have been automated under phase 1 using Motorola RTUs.

The bidder is notified on the need to retrofit the RMUs so as to be able to pick all the indications,

alarms, voltages and currents for all the phases. Modifications may be required to be able to pick

the EFI (earth fault indicator) alarms which are not connected currently but provisioned.

Since the required coverage of the automated RMUs do not coincide with the installed ones, there

is need for supply and installation of 11No. Extra RMUs. The minimum specifications are as

below. The list of RMUs to be covered in this scope is as attached in appendix 2 with special

requirements for some sites as below.

The RMU rooms also require rehabilitation. This shall involve all necessary works for secure and

safe installation of the RMUs.

.

166 | P a g e

SPECIFICATIONS FOR RING MAIN UNIT

ANNEX A: Guaranteed Technical Particulars (to be filled and signed by the Manufacturer and

submitted together with catalogues, brochures, drawings, technical data, sales

records and certified true copies of type test certificates and type test reports for

tender evaluation)

9.1 SCOPE

9.1.1 This specification is for newly manufactured factory-assembled Ring Main Unit

(RMU) for KPLC 11kV, 50Hz system.

9.1.2 The ring main unit shall be extensible type (both sides) and shall have cable

connections for feeders and Transformers. The RMU shall comprise two main

functional units, the feeder panel and the transformer panel – the number of

functional units per RMU type is specified in the table below. The feeder panel

shall be equipped with automatically operated vacuum/SF6 type load-break

switch and the transformer Panel shall be equipped with vacuum circuit breaker.

The RMU shall be fully automated and shall be prepared for remote control

operation.

The configurations of the RMU type shall be as follows;

# Type Configuration Quantity Location

(a) Type I

RMU

3 - Feeder panels and 1

Transformer Panels

6 pieces Boulevard, Longonot, Old

Govt Press, ICDC,

Rahimtulla, Hilton

(b) Type II

RMU

4 - Feeder panels and 1

Transformer Panels

coupled with metering

CB

1 piece KICC

(c) Type III

RMU

2 - Feeder panels and 2

Transformer Panels

2 pieces MISC,E-HSE

(d) Type IV

RMU

2 - Feeder panels and 1

Transformer Panels,

coupled with 1MVA

Transformer

1 pieces IPS

(e) Type V

RMU

4 - Feeder panels and 1

Transformer Panels

1 piece Nation Centre

The medium of insulation shall either be;

(a) Solid material (epoxy resin) with encapsulated units assemble in dry air or

(b) SF6 gas Insulated.

The later (b) if offered shall be full gas insulated (SF6 GIS) while the former (a)

shall be SF6 Free.

167 | P a g e

The specification also covers inspection and test of the Ring Main Unit as well as schedule

of Guaranteed Technical Particulars to be filled, signed by the manufacturer and submitted

for tender evaluation.

The specification stipulates the minimum requirements for Ring Main Unit acceptable for

use in the company and it shall be the responsibility of the Manufacturer to ensure adequacy

of the design, good workmanship and good engineering practice in the manufacture of the

Ring Main Unit for KPLC.

9.2 REFERENCES

The following standards contain provisions which, through reference in this text constitute

provisions of this specification. Unless otherwise stated, the latest editions (including

amendments) apply.

IEC 62271-100: High-voltage switchgear and control gear - Part 100: High-voltage

alternating-current circuit-breakers.

IEC 62271-103: High-voltage switchgear and control gear - Part 102: Switches for rated

voltages above 1kV and less than 52kV

IEC 62271-200: High-voltage switchgear and control gear - Part 200: A.C. metal-enclosed

switchgear and control gear for rated voltages above 1 kV and up to and

including 52 kV.

IEC 60044-1: Instrument transformers - Part 1: Current transformers.

IEC 60376: Specification for SF6 gas

IEC 60255: Electrical Relays.

IEC 60529: Degrees of protection provided by enclosures (IP Code).

BS 381C: Specification for colours for identification, coding and special purposes.

9.3 TERMS AND DEFINITIONS

The definitions given in the reference standards shall apply.

9.4 REQUIREMENTS

9.4.1 Service Conditions

The equipment shall be suitable for continuous operation outdoors in tropical areas at

altitudes of up to 2200m above sea level, humidity of up to 95%, average ambient

temperature of +30ºC with a minimum of -1ºC and a maximum of +40ºC, heavy saline

conditions along the coast and isokeraunic levels of up to 180 thunderstorm days per year.

168 | P a g e

9.4.2 Design and Construction

9.4.2.1 The Ring Main Unit shall be free-standing metal-enclosed designed and

constructed in accordance with IEC 62271-200 and the requirements of this

specification. Load-break Switches and circuit breakers shall comply with IEC

62271-103 and IEC 62271-100 respectively.

9.4.2.2 The Ring Main Unit shall be floor mounting type suitable for outdoor and

indoor use. The floor fixing shall allow for mounting on a simple plinth with

a flat surface.

9.4.2.3 The unit shall incorporate combinations of SF6/Vacuum Load break switches

(three phase) that shall be capable of being operated independently. Each

switch shall have integral earthing facility and three operating positions –

“ON”, “OFF” and “EARTH” and capable of being operated remotely.

9.4.2.4 The Earth Switch shall be able to carry the rated short circuit current. The

RMU switches shall be capable of making and breaking the rated load current.

9.4.2.5 The Ring Main Unit shall be complete with Auxiliary switches for remote

control and supervisory status indication of the switches.

9.4.2.6 For SF6 Free units, the Busbars shall be encapsulated in epoxy resin or an

equivalent insulation material - not SF6 or Oil.

9.4.2.7 The unit shall also have a tee-off circuit (three phase) controlled by means of

vacuum circuit breaker with trip-all phase mechanism complete with integral

earthing facilities. The design of the tee-off chamber shall be such that it can

be electrically isolated from the ring main switches to facilitate maintenance

and or testing of the transformer without opening the Ring Main. The tee-off

shall have integral earthing facility for the cable.

9.4.2.8 The ring circuits shall have Earth Fault indicators to indicate whether fault

current has passed through the switch. The indicator shall have an electrically-

reset flag and shall be prepared for remote monitoring. The RMU shall have

accessories for indicating voltage presence.

9.4.2.9 The tee-off shall have overcurrent and earth fault protection with standard IEC

IDMT Time-Current characteristic curves as per IEC 60255. The protection

relay shall be connected to a current transformer of ratio 300-200-100-50/5A,

to allow effective protection of transformers rated at 315kVA, 630kVA and

1000kVA and Loads of 2MVA, 3 MVA and 4MVA and powered from within

the RMU

9.4.2.10 Detailed information shall be submitted to facilitate technical evaluation

of the protection scheme.

9.4.2.11 The relay software and all the necessary tools for configuration and

settings shall be supplied to KPLC including the connection cables (PC –

relay).

169 | P a g e

9.4.2.12 The tee-off shall have three operating positions “ON”, “OFF” and

“EARTH”.

9.4.2.13 Access to handles for operation and access for viewing of indication and

instruction labels shall be on one side only.

9.4.2.14 Test facilities for applied high voltage (15kV) shall be provided for the

ring cables (connected to earth switch) by means of a one piece three-phase

test probe or by a three-phase integral device with connections external to the

switch equipment. The probe shall be applied only when the switch is in

“Earth” position. In addition there shall be capacitive voltage indicators on

each circuit.

9.4.2.15 Each equipment shall be provided with a main earth bar of not less than 25

x 3 mm H. D. H. C. copper strip or equivalent cross-section. The earth bar

shall be bolted to the main frame and located so as to provide convenient

facilities for earthing cable sheaths and earthing devices. Earth connections to

cable glands shall be provided.

9.4.2.16 Each equipment shall be provided with lifting facilities and shall be

marked to indicate its weight. The ring main unit shall be complete with all

necessary components and accessories.

9.4.2.17 Padlocking facilities shall be provided to prevent unauthorized access and

operation. The facilities shall be suitable for padlocks with shanks of 8mm

diameter.

9.4.2.18 The switchgear enclosure shall be dry painted to Dark Admiralty Grey

Colour No. 632 as per BS 381C.

9.4.2.19 The RMUs offered shall be virtually maintenance free.

9.4.2.20 The Ring Main unit shall have provision for remote operation. Auxiliary

switches for remote and supervisory status indication of the ring switches

shall be provided. It shall have terminals brought out to a terminal block that

will facilitate wiring of REMOTE CLOSE and REMOTE TRIP by KPLC.

Detailed information on this shall be submitted with the tender. KPLC shall

provide the Remote Terminal Unit and Communication Network.

Compatibility requirements/limitations of the RMU offered shall be stated in

the bid. The RMU shall be equipped with appropriate 24/48V DC auxiliary

power supply for operation of the switches and circuit breakers. The auxiliary

supply shall have a backup battery system adequate for operations of all the

switches in the event that the power supply is unavailable for at least 8 hours.

The auxiliary supply shall be prepared for connection to 240V ac supply that

will be made available in the switchgear room. The auxiliary supply unit shall

have protection for overvoltage.

170 | P a g e

9.4.2.21 Provision for remote operation and measurements requires that the

terminals are brought out to the terminal block to facilitate wiring of

measurands, REMOTE CLOSE and REMOTE TRIP by KPLC. Where serial

communication is possible the required protocol is IEC 60870-5-101.

Compatibility requirements/limitations shall be indicated in the bid

9.4.2.22 The equipment shall have internal Arc Fault safety of 20kA in 1sec

9.4.2.23 The RMU plinths exist since the proposed RMUs shall be a replacement

of the existing ones.

9.4.3 Operating Mechanism

9.4.3.1 The operating mechanisms of the switches shall be spring-operated devices

designed so that energy stored in the initial part of each operation shall be

used to complete the making, circuit earthing or opening from circuit earth

operations as the case may be, independently of the operator. Slow making or

breaking shall not be possible. For remote operation, each of the two switches

shall be equipped with a motorized switch actuator with option for manual

operation shall be provided. The motor shall be rated 24/48V DC.

9.4.3.2 It shall not be possible for the operating mechanism(s) to be left in such a

condition that any energy stored in the initial part of an incomplete operation

remains in the spring when the switch is in the “ON”, “OFF” or “EARTH”

positions.

9.4.3.3 For the tee-off, the operation of the protective device shall cause the opening

of all three phases.

9.4.3.4 Means shall be provided for manual tripping from “ON” to “OFF”.

9.4.3.5 It shall be possible to lock the operating mechanism(s) in any operating

position and independently to lock off the “EARTH” and “ON” position by

use of padlock.

9.4.3.6 It shall be necessary before it is possible to operate from “OFF” to “EARTH”,

to move a captive device which can be padlocked and which shall be labeled

“REMOVE to EARTH”

9.4.3.7 Mechanical indication of the operating positions of the switch shall be

provided with indicators in both directions so as to show whether the switch

contacts are in the “ON”, “OFF” or “EARTH” positions. The positions shall

be clearly indicated and the indicators shall be inscribed “ON” in white letters

on a red background, “OFF” in white letters on a green background and

“EARTH” in black letters on a yellow background.

9.4.3.8 Operating handles shall be arranged to operate in a vertical plane and

downward movement shall complete the making and earthing operations.

171 | P a g e

9.4.3.9 Interlocks shall be provided to prevent any operation that threatens safety. In

addition interlocks shall prevent the following operations:

a) Inadvertent operation of any Ring Main Switch and Tee-off Switch direct

from the “ON” position to “EARTH” position or vice versa.

b) Operation of any switch to “ON” position from any position with the access

cover opened.

c) Test facility (probes or plugs) being inserted or withdrawn unless the relevant

switch is at the “EARTH” position.

d) Operation of any switch from “EARTH” to “OFF” position unless the

associated access cover is closed or test plugs inserted.

9.4.3.10 Operating procedures and interlocks shall be clearly inscribed on the

operations side of the unit.

9.4.3.11 Physical position of the disconnector contacts shall be visible through a

window of weather resistant transparent glass for safety of operations

9.4.4 Cable Termination

9.4.4.1 The unit shall be complete with cable boxes and terminals suitable for three

core XLPE copper and aluminum cables of up to 300sq mm. The unit shall be

supplied with two complete sets of cable terminations (one for immediate

connection and the other for spare).

9.4.4.2 The cable boxes shall be air insulated suitable for dry type cable terminations,

bottom entry. Compound filled cable boxes are not accepted.

9.4.4.3 The cable boxes shall be equipped with glands to facilitate cable terminations.

9.4.5 Vacuum Circuit Breaker and Vacuum Ring Switch

9.4.5.1 The bidder shall state period of experience of the manufacturer of vacuum

interrupters and vacuum switches used in the switchgear. Evidence of the

suitability of the vacuum bottle shall be provided in the form of type test

reports and certificates from the relevant International Independent testing

laboratory or an ISO/IEC 17025 accredited National Testing/Standards

Authority.

9.4.5.2 The vacuum breakers shall have a service life of at least twenty five (25)

years.

9.4.5.3 Where replacement of the bottles shall be required before the expiry of the

warranty period, the supplier shall render a service to recover and replace the

bottles at no cost to KPLC (supplier to provide clear and sufficient details in

his offer).

9.4.5.4 The units shall be sealed for life.

9.4.5.5 More details on the technical requirements of the circuit breaker and the Ring

switch are in appendix 14.

172 | P a g e

9.4.6 SF6 Gas

9.4.6.1 The Gas Insulated Ring Main Unit shall be supplied filled with new SF6 gas

complying with IEC 60376. The gas in each chamber shall be independent of

the gas in the other chambers.

9.4.6.2 The switchgear shall be factory sealed so as not to require any routine gas

replenishment in normal service. The design, construction and sealing of gas

compartments shall be such that the period to replenishment of gas is not less

than twenty five (25) years. In addition the manufacturer shall confirm that the

maximum leakage rate is lower than 0.1% per year. Each RMU shall be sealed

for life and proof of the same given.

9.4.6.3 The unit shall be complete with a device for checking the SF6 gas pressure on

each tank in service with indication of minimum permissible pressure level for

safe operation.

9.4.6.4 The gas enclosure and switchgear housing shall be designed such that in the

event of an internal arc fault, the operator shall be safe. Internal arc resistance

rating required is 20kA for 1sec.

9.4.7 Ratings

The Ring Main Unit (RMU) shall be of the following ratings:

Nominal System Voltage 11kV

Highest System Voltage 15.5kV

Equipment Class => 15kV

Frequency 50Hz

Impulse-voltage withstand level, peak (1.2/50µs dry) 95kV

Power Frequency Withstand Voltage, rms (50Hz 60se wet ) 38kV

Ring main switch rated current (temperature rise within IEC) 630A

Ring main, main and earth switches rated short time current (3 sec) 25kA

Circuit Breaker rated short time current (3 sec) 25kA

Tee-off circuit rated current 200A

Control Voltage 24/48V

DC

Opening Time of the circuit breaker <80ms

Load breaking current 200A

9.4.8 Circuit Labels

The front shall include a clear mimic diagram which indicates the different functions. The

position indicators shall give a true reflection of the position of the main contacts and shall

be clearly visible to the operator. All labels and diagrams shall be suitable for outdoor

service and shall have non-fading properties.

Physical position of the disconnector contacts shall be visible through a window of weather

resistant transparent glass for safety operations.

173 | P a g e

9.4.9 TESTS AND INSPECTION

9.4.9.1 The Ring Main Unit and its components shall be inspected and tested in

accordance with the requirement of IEC 62271- 200 and this specification. It

shall be the responsibility of the manufacturer to perform or to have

performed all the tests specified.

9.4.9.2 Circuit breakers shall be inspected and tested in accordance with the

requirement of IEC 62271-100 and this specification.

9.4.9.3 Switches shall be inspected and tested in accordance with the requirement of

IEC 62271-103 and this specification.

9.4.9.4 Current transformers shall be inspected and tested in accordance with the

requirement of IEC 60044-1 and this specification.

9.4.9.5 Relays shall be inspected and tested in accordance with the requirement of

IEC 60255 and this specification.

9.4.9.6 The equipment shall be subject to acceptance tests at the manufactures’ works

before dispatch. Acceptance tests will be witnessed by two Engineers

appointed by Kenya Power and Lighting Company Limited (KPLC). The

acceptance tests shall include the following routine tests:

a) Visual inspections

b) Conformity with drawings and diagrams,

c) Measurement of closing and opening speeds,

d) Measurement of operating torque,

e) Checking of filling pressure,

f) Checking of gas-tightness,

g) Dielectric testing and main circuit resistance measurement.

h) Power frequency voltage

i) Resistance test for the circuit

j) Mechanical operation tests.

9.4.9.7 Type Tests- In addition to the routine tests, the supplier shall include in its bid

type test certificates issued from an internationally recognized independent

testing laboratory. In case of the tests having been conducted by a National

Testing Laboratory/Standards Authority, a copy of the accreditation certificate

for the laboratory/standards authority shall also be submitted in accordance

with IEC17025 requirements. The type results shall include:

a) Short time current withstand test and peak current withstand test.

b) Lightening Impulse voltage with-stand test

c) Temperature rise test.

d) Short Circuit current making and breaking tests.

e) Power frequency voltage withstand test (dry).

f) Capacitive current switching test

174 | P a g e

g) Mechanical operation test.

h) Measurement of the resistance of the main circuit.

i) Degree of protection of main tank and outer enclosure

j) Switch, circuit breaker, earthing switch making capacity.

k) Switch, circuit breaker breaking capacity.

l) Internal arc withstand.

m) Checking of partial discharge on complete unit

In addition, for switches, test reports on rated breaking and making capacity shall be

supplied. For earthing switches, test reports on making capacity, short-time withstand

current and peak short-circuit current shall be supplied.

9.4.9.8 In addition to FAT, KPLC will inspect the equipment on receipt and may

perform or have performed any of the relevant tests in order to verify

compliance with the specification. The manufacturer shall replace without

charge to KPLC, equipment which upon examination, test or use fail to meet

any or all of the requirements in the specification.

9.4.10 MARKING, LABELLING AND PACKING

9.4.10.1 The Ring Main Unit and associated components shall be packed in a

manner as to protect it from any damage in transportation and handling.

9.4.10.2 Each assembly and package of items associated with the switchgear shall

be suitably marked.

9.4.10.3 In addition to markings required elsewhere in the specification, each panel

and component shall be marked in accordance with the relevant IEC standard

and shall include the following marking:

a) Name of manufacturer and country

b) Type/Model reference number and Standard of Manufacture

c) Ratings: rated normal current and temperature rise, rated short time

current and duration, rated voltage, rated frequency, rated lightning

impulse withstand voltage, rated power frequency withstand voltage, rated

short circuit making current.

d) Serial number

e) The words ”Property of KPLC”

175 | P a g e

9.4.11 DOCUMENTATION

9.4.11.1 Two hard copies and a soft copy of operational manuals and drawings

detailing dimensions, panel layout, Wiring and schematic shall be submitted

to KPLC. Industry standard documentation on use of SF6 gas shall be

submitted to support the offer. The operational documentation shall include

information related to Maintenance, Commissioning, Installation, Testing

Configuration and Programming of the relay and all other.

9.4.11.2 Software for configuration, setting and programming and for downloading

and analysis of relay data shall be provided including all the necessary cables

for connecting to a Laptop computer.

9.4.11.3 Specialized erecting tools and gauges peculiar to the equipment shall be

supplied together with the equipment.

9.4.11.4 All documentation shall be in English Language.

9.4.12 INSTRUMENT TRANSFORMERS AND MEASUREMENTS

The outputs of the measuring transformers for measuring and protection purposes shall be

determined according to the technical requirements, but shall not be less than 125% of the

overall computed (design) burden of the connected apparatus and conductors. However,

the transformer shall not be loaded less than 60 % of rated burden. The transformers will

be connected to the transducers provided in the RTU equipment.

a) Power frequency test voltage on secondary windings, 1 min. 2.5 kV

b) Overvoltage inter-turn test, 1 min. 3.5 kV

Current transformers for measurements shall be of class 0.5, 15VA and shall be prepared

for connection to transducers in the RTU.

176 | P a g e

ANNEX A: Guaranteed Technical Particulars (to be filled and signed by the Manufacturer

and submitted together with copies of manufacture’s catalogues, brochures, drawings, technical

data and certified true copies of previous test reports & certificates for tender evaluation)

TENDER NO……………………………

Item Particulars Unit Guar. Fig. Tolerance

Type & Model Number

Name of Manufacturer & Country of Origin of

equipment being offered

Nominal System Voltage

Equipment Voltage Class

Frequency

Ring Main Switch Rated Current (temperature rise

within IEC requirements)

Ring Main rated short time current (3 seconds)

Tee-off rated current

Service Conditions

a.1 Cubicles

Manufacturer

Metal Clad type

- Rated Voltage kV

- Maximum service voltage kV

- Rated frequency Hz

- Rated continuous bus bar current A

- One minute power frequency withstand

voltage, dry and wet

- to earth kV rms

- Impulse withstand voltage 1.2/50 ms

- to earth kV peak

- Permissible 1 second short-time current kA rms

- Dynamic short-time current kA peak

Arch tested in accordance with IEC 60280

amendment 2

Yes/No

a.2 Circuit Breakers (Type __________)

177 | P a g e

Breaking Medium /Vacuum

Manufacturer

- Rated voltage kV

- Maximum service voltage kV

- Rated frequency Hz

- Rated continuous current A

- One minute power frequency withstand

voltage, dry and wet

- to earth kV rms

- across open breaker pole kV rms

- Impulse withstand voltage 1.2/50 ms

- to earth kV peak

- across open breaker

- Breaking capacity at rated voltage

- symmetrical kA rms

- asymmetrical kA rms

- Making capacity kA peak

- Breaking capacity of capacitive current A

- Overvoltage factor for disconnection of

unloaded transformers (without voltage

limitation by lightning arresters)

- Rated inductive current switching capacity A

- Permissible 1 second short-time current kA rms

- Dynamic short-time current kA peak

- Opening time, interval of time between the

instant of application of tripping impulse to the

instant when the main contacts have separated

in all poles

m.sec.

- Make time, interval of time between the

initiation of closing operation and the instant

when the current begins to flow in the main

circuit

m.sec.

- Total break time, interval of time between the

instant of application of tripping impulse to the

instant of final arc extinction in all pole

- at 100% breaking capacity m.sec.

178 | P a g e

- under phase opposition m.sec.

- Rate of rise of recovery voltage (RRRV) at

100% short circuit current

- 3-phase kV/msec

- 1-phase

- RRRV out of phase duty kV/msec

- Minimum temperature rise at rated current of

main contact

°C

- Vacuum in break chamber torr

Tripping Coil

Continuous Rating for 0.5sec A

Pick up current A

Drop off Current A

Earthing Switches

- Rated short-time current 1 sec. kA rms

- Rated dynamic short-circuit current

- Making Capacity

a.4 Current Transformers

Manufacturer

- Rated voltage kV

- Maximum service voltage kV

- Rated frequency Hz

- One-minute power frequency test voltage of

- primary winding kV rms

- secondary winding kV rms

- Lightning impulse withstand voltage kV peak

- Rated primary currents A

- Rated secondary current A

- Short-time thermal rating

- 1 second kA rms

- Short-time dynamic rating kA peak

- Burden and accuracy class of

- measuring core

179 | P a g e

- protection core

- Instrument security factor of the measuring

core

- Accuracy limit factor of the

- protection core

a.5 Load break Switches

Breaking Medium

Manufacturer

- Rated voltage KV

- Maximum service voltage KV

- Rated frequency HZ

- Rated continuous current A

- One minute power frequency withstand

voltage, dry and wet

- to earth

- across open switch

- Impulse withstand voltage 1.2/50 ms

- to earth

- across open breaker

- Making capacity A

- Breaking capacity of capacitive current A

- Minimum temperature rise at rated current of

main contact

°C

Breaking capacity - Load current

- Vacuum in break chamber torr

a.6 Manufacturers and their country of origin

- Cubicles

- Vacuum interrupters

- Current transformers

- Load Break Switches

Protection Relays

To be copied and filled in for each type of relay as

applicable

- Accuracy of the adjustable tripping time sec.

- Min. possible tripping time ms

- Drop out ratio %

180 | P a g e

- Max. admissible current during 0.5 sec. %.IN

- Max. admissible current continuously %.IN

- Limit value of the adjustable tripping current

(O.C.R.)

%.IN

- Limit value of the instantaneous tripping

current (O.C.R.)

%.IN

- Accuracy of the adjustable tripping time sec.

………………………………………………………………………………………….

Manufacturer’s Name, Signature, Stamp and Date

Note: This schedule does not in any way substitute for detailed information required elsewhere

in the specification.

181 | P a g e

ANNEX B: Informative Data.

Description Informative data /

reference

1. RMU Make

2. Type

3. Design standards complied with

4. Current breaker and switch arrangement

5. Operating Mechanism of the switches

6. Available Interlocks

7. Type of Cable box

8. Size, type and rating of cable terminals

9. Equipment service life

10. No of years to first SF6 replenishment

11. Internal Arc fault design safety

12. Current Transformer & Ratio provided

13. Relay Type provided (Attach relay manual with Technical

data and manufacturer’s experience & details)

14. Auxiliary supply

a) Make of the main components or the complete unit

b) Input Voltage (AC)

c) Output Voltage (DC)

d) Capacity (Ah)

e) Service Life (years)

f) Maximum current rating

15. Earthing Switches

- Reference standard

- Type of isolating switch

- Min. creepage distance (live parts to earth)

- Min. isolating distance (clearance between open

contacts)

- Material of contact surface

- Total contact pressure

- Type of operating device

- weight of earthing switch

16. Current Transformers

- Reference standard

- Type designation

- Overall dimensions

- Total weight of one current transformer

- Type of insulation

182 | P a g e

17. Load Break Switches

Reference standard

- Type of isolating switch

- Min. creepage distance (live parts to earth)

- Min. isolating distance (clearance between open

contacts)

- Material of contact surface

………………………………………………………………………………………

Manufacturer’s Name, Signature, Stamp and Date

Note: This schedule does not in any way substitute for detailed information required elsewhere

in the specification.

183 | P a g e

10 SPARE PARTS The bidder shall as a SHALL provide a list of recommended spares if different from the one given

in the Bills of quantities.

184 | P a g e

11 TRAINING

This section describes general requirements that apply to all training courses. The Contractor shall

submit the training proposal along with the bid. The training content, schedule and location shall

be finalized during project execution.

Training of the system controllers, SCADA and Telecommunications staff, Operation and

Maintenance personnel for the new distribution automation system’s hardware and software, new

RTUs, switchgear, as well as the new communication network to be implemented under the project

is crucial for the success of the project for safeguarding the investment and to obtain the benefits

of the new distribution automation system to KPLC and the Kenyan economy.

11.1 GENERAL

(a) Training will be conducted by Contractors personnel, who are experienced

instructors and speak understandable English.

(b) All necessary training materials shall be provided by the Contractor. Each trainee

shall receive individual copies of all technical manuals and all other documents

used for training.

(c) Class materials, including the documents sent before the training courses as well

as class hand-outs, shall become the property of owner. Employer/owner reserves

the right to copy such materials, but for in-house training and use only.

(d) Hands-on training shall utilize equipment similar to that being supplied under the

contract.

(e) For all training courses, the travel and per-diem expenses will be borne by the

Employer.

(f) The Contractor shall quote training prices under project management cost & shall

be included in the bid

(g) The schedule, location, and detailed contents of each course will be finalized

during employer and Contractor discussions shortly after placement of the award.

The Employer shall review and approve the contents of the overview training

prior to the start of the training.

(h) The contractor shall provide a 4x4 double cabin pick-up for use by the project

manager from the Employer’s side and his team. The item shall constitute regular

maintenance and service to the vehicle as well as fixed monthly fuelling. Need for

a dedicated driver will be finalized during employer and Contractor discussions

shortly after placement of the award.

185 | P a g e

11.2 Training Course Requirements

Employer's training course requirements are described below in terms of the

contents of each course to be provided. Training shall be provided on actual

database for the application software course and the associate training courses.

11.2.1 Database, Display Building & Report generation Course

The database and display building course shall be the first course to be given in the

overall training sequence. It shall be a hands-on course using the hardware and

software to be supplied by the contractor. The course shall be designed to train

owner personnel in how to develop the databases, displays, reports, and logs for the

offered system. Course objectives shall include:

a. How to set up a database & display development system

b. How to identify database fields, entries, records, tables, and contents

c. How to structure RTU /FRTU table definitions

d. How to build tables, arrays, and report formats and displays.

e. How to perform database maintenance

f. How to generate the database from source information

g. How to maintain symbol libraries, display colour groups, and display

string lists.

On course completion, all participants shall be able to prepare the necessary input

data to define the system operating environment, build the system database and

displays, and prepare the database administrator to maintain and modify the

database and its structures.

11.2.2 Computer System Hardware & Software Course

The computer system hardware & Software course shall be offered, at the system

level only. The training course shall be designed to give owner hardware &

software personnel sufficient knowledge of the overall design and operation of the

system so that they can correct obvious problems, configure the hardware, perform

preventive maintenance, run diagnostic programs.

The following subjects shall be covered:

(a) System Hardware Overview: Configuration of the system hardware.

(b) Operating System: Including the user aspects of the operating system,

such as program loading and integrating procedures; scheduling,

management service, and utility functions; and system expansion

techniques and procedures

(c) System Initialization and Fail over: Including design, theory of operation,

and practice

186 | P a g e

(d) Equipment Maintenance: Basic theory of operation, maintenance

techniques and diagnostic procedures for each element of the computer

system, e.g., processors, auxiliary memories, LANs, routers and printers.

Configuration of all the hardware equipment.

(e) Diagnostics: Including the execution of diagnostic procedures and the

interpretation of diagnostic outputs,

(f) System Expansion: Techniques and procedures to expand and add

equipment such as loggers, monitors, and communication channels.

(g) System Maintenance: Theory of operation and maintenance of the

hardware configuration, fail over of redundant hardware etc.

(h) Operational Training: Practical training on preventive and corrective

maintenance of all equipment, including use of testing tools.

11.2.3 Application Software Course

The Contractor shall provide training on Application software courses covering all

applications other than those already covered above. The training shall include:

(a) Overview: Block diagrams of the application software and data flows.

Programming standards and program interface conventions.

(b) Application Functions: Overview of Functional capabilities, design, and

algorithms. Associated maintenance and expansion techniques.

(c) System Programming: An introduction to software architecture, Effect of

tuning parameters (OS software, Network software, database software and

Application Software etc.) on the performance of the system. Administration

of Database (both real-time and RDBMS),

(d) Software Documentation: Orientation in the organization and use of system

software and Application software documentation.

(e) Hands-on Training: shall be provided with allocated computer time for trainee

performance of unstructured exercises and with the course instructor available

for assistance as necessary.

11.2.4 RTU/FRTU Course

The Contractor shall provide an RTU/FRTU course that covers the following

subjects as a minimum:

(a) Theory of operation of all RTU/FRTU functions

(b) Operational procedures for various modes of operation, including diagnostic

tests and interpretation of the associated test results

(c) Implementing and maintaining multiple communication ports

(d) Converting an RTU/FRTU from one protocol to a different protocol

(e) Demonstration of complete RTU/FRTU test set use, including test set

connection and set up for all possible modes of operation, all operational

187 | P a g e

procedures, the exercise of each command or feature associated with each

mode of operation, the interpretation of results, and how to use the test set to

diagnose and isolate RTU problems

(f) Disconnection and replacement of all RTU/FRTU equipment, including all

modules within the RTU/FRTU

11.2.5 Operator Training Course

This training course shall provide training to Owner’s operators on ADMS and

Billing & Customer Care Systems so that operators can manage the system

effectively. The training shall include:

(a) System Overview: Configuration of the system, a functional overview, and an

overview of system capabilities and performance.

(b) General Operating Procedures: Hierarchical structure of displays, display

capabilities and features, user procedures, log-on and user access restrictions,

and error messages.

(c) System Applications: Theory of operation, capabilities, and operating

procedures for each application function.

(d) Handling of Equipment: Minor maintenance operations, such as removal of

stuck paper in printers etc., which do not require spares/specialised skills.

(e) Operator Documentation: Orientation in the organization and application of

all user documentation for Operator and verification of the information

contained therein. The course shall focus on hands-on training on the system.

The trainees shall perform instructor-defined procedures with the help of the

dispatcher documentation. In addition there shall be training for Instructor to

use DTS.

11.2.6 Communication System Training

The training shall focus on critical aspects associated with installation, testing &

commissioning of fibre optic system and radio.

This shall include the state-of-the art techniques employed in laying, splicing &

testing of fibre optic cable & terminal equipment etc. The owner’s personnel shall

be trained in such a way that the basic maintenance of terminal equipment & cable

etc. can be carried out effectively.

11.2.7 Auxiliary Power Supply Training

The training shall cover various aspects covering installation, testing &

commissioning of DC power supply, & UPS system. Proper emphasis of the

training shall be for effective operation & maintenance of Auxiliary Power Supply

System on routine/emergency basis by the owner’s personnel.

188 | P a g e

11.2.8 Development system training

ADMS training needed for efficient use of the development system shall be

scheduled to an early stage of project execution. It shall be held at the Contractor's

premises and be continued in Kenya after field acceptance of the development

system. This includes, but may not be limited to database, display, and report

generation training courses.

11.3 TRAINING PLAN

Training for personnel for the distribution automation system shall be divided into two (2)

types of training with different tasks, that is:

11.3.1 Operators’ training

This is to acquaint the operators to the system and its functions. Only when the

operators utilize the functions provided by the new distribution automation system

then all possible benefits will be realized.

a) It is recommended that the bidder proposes an option where six (6) KPLC staff

are trained to be able to interrogate the SCADA system, configure new switches

into the SCADA system, and be able to migrate the switches from one point to

the other in respect to the existing one on the ground. The bidder will propose

the cost and the syllabus and the time required to implement all the switches

(RMUs and LBSs) in to the SCADA. The training is proposed to take 3 weeks.

11.3.2 Maintenance training

This is to safeguard the investment by keeping it fully operational and by

adopting/extending the distribution automation system to the ever growing

network. This includes the PC based SCADA system, Load Break Switches, RTUs,

configuration of the databases and setting up of the communication parameters. The

training is proposed to take two (2) weeks and to six (6) engineers.

A thorough international and local training for the operations and maintenance

engineers is to be conducted where the staff are supposed to successfully set up a

new site from scratch to testing commissioning in the SCADA system. International

training shall be two week while local training shall be as long as deemed necessary.

The bidder will propose the cost, the syllabus and the time required to implement

all the switches (RMUs and LBSs) into the SCADA.

Engineers nominated by the employer shall be trained at the contractor’s home

office, manufacturer’s premises and at site. The tenderer shall include a description

of the his proposed organization and administration for implementation of the

training program, indicating the responsibility for training within the Tenderer’s

189 | P a g e

proposed site organization and home office organization indicating the staff

responsible for the various components of the training.

11.3.3 Data engineering

The tenderer shall propose as an option a training programme for the

implementation of the training to the KPLC staff. The plan shall describe the

sequencing, time, duration and resources involved in implementation of each of the

Tenderer’s proposed training activities. The training shall be such that once the staff

are trained, they will be the ones to carry out the entire data engineering in Kenya

for the entire project with supervision by the tenderer.

The responsibility of the data engineering and its quality shall be on the bidders.

The plan has been provided somewhere in this document. This shall be finalized

during employer and Contractor discussions shortly after placement of the award.

11.3.4 Training expectations

The operators’ trainees shall be able to do the following as a minimum:

(a) Draw an LBS/RMU/RTU on the ADMS system and give all the required

parameters and details

(b) Change the physical and geographical position of the LBS/RMU/RTU.

(c) Modify a LBS/RMU/RTU

(d) Set up a repeater/remote site

(e) Troubleshoot a repeater/remote site

(f) Upgrade SCADA/ADMS software

(g) Conduct Daily /weekly backup

(h) Test the batteries on the repeater/remote site

(i) Measure the radio signal strength

The operators’ trainees shall be able to:

(i) Hoist a switch and install

(ii) Connect and terminate a switch/RMU

(iii)Troubleshoot/test a switch/RMU

(iv) Detect SF6 leak, diagnose and refill SF6

(v) Operate (local, manual, remote) the switch

(vi) Maintain the LBS switch

The training programme shall be as below. The bidder is advised to give a detailed training

programme for discussion purposes. The programme shall form part of the tender.

190 | P a g e

11.3.5 TRAINING PROGRAM PROPOSAL – ADVANCED DISTRIBUTION

MANAGEMENT SYSTEM PROJECT KENYA POWER

# Areas to be covered Target Group Proposed

Duration (Days)

1 ADMS KPIs GMs, Managers 1

2 ADMSoperations and the best way to

utilize the information retrieved by the

system

Control/O&M Engineers 1

3 Integration to other systems (Geographic

Information System (GIS), SCADA,

dispatch, Advanced Metering

Infrastructure (AMI), Outage

Management System (OMS) in a cost

effective manner.

Telecoms/Control/O&M

Engineers

2

4 Creating field-reproducible DA schemes Telecoms/Control/O&M

Engineers

2

5 Providing hands-on system

configuration and integration services

that include independent third-party site

acceptance testing (SAT)

Telecoms/Control/O&M

Engineers

2

6 Reliability analysis and creating

reliability models.

Distribution

Planning/O&M Engineers

4

7 Creation of new Switch onto the

database, configuration files for a

particular switch for and uploading in the

RTU

Telecoms/Control

Engineers

1

8 Creation of configuration files for radios Telecoms Engineers 0.5

9 Uploading/editing of Single Line

Diagrams in the database.

Control/Telecoms

Engineers

1

10 Server Back up and total emergency

recovery

Telecom/O&M/ Control

Engineers/IT

0.5

12 Modelling of radio repeaters in the power

system network

Telecom Engineers 1

13 RTU Trouble -shooting Telecom Engineers 1

14 RTU configurations for the RMU Telecom/ E Plant/O&M

Engineers

0.5

15 RMU & GX SF6 recovery and leakage

detection techniques

E Plant /O&M Engineers 1

16 Radio maintenance Telecom Engineers 1

17 System data analysis and interpretation Control/O&M/ Telecom

Engineers

1

18 Report writing and presentations Distribution

Planning/O&M

Engineers/Control

1

191 | P a g e

19 Developing load management program

designs

Distribution

Planning/O&M Engineers

1

11.4 MAINTENANCE KIT

The tenderer is expected to provide 6No. Tool kits to conduct a thorough preventive maintenance

to the switchgear, the central system and the radio system, a list of all the tools in the kit and

manufacturer shall be given by the bidder. In addition to that the following shall be provided: 1No.

Hotspots and SF6 gas detector and filler (FOC gas handling equipment), 3No. Ladders

(specifications provided), earth loop impedance tester (earth tester), live line tester and 4No.

Laptops pre-installed with the development and maintenance software.

Details of the proposed tools and equipment shall be presented as below:

# Equipment Model no. Country of origin

1

2

3

192 | P a g e

12 MAINTENANCE CONTRACT

The contractor shall provide, as an annex and as a SHALL, to his offer a maintenance contract

covering Level 2 & 3 support to all the provided equipment and software programs. This contract

may come to effect after expiry of the warranty period.

193 | P a g e

13 QUALITY ASSURANCE 13.1 Requirements for Quality Management System

13.1.1 The supplier shall have a fully documented, implemented and maintained quality

system, which complies with the requirements of ISO 9001-2000. This

management system shall carry valid certification from an appropriate QMS

certification body.

13.1.2 Where products and / or substantial sub-assemblies are acquired from 3rd party

organisations such organisations shall also have a fully documented, implemented

and maintained quality system, which complies with the requirements of

ISO9001-2000

13.1.3 Quality Management System Certification

Proof of certification relating to an organisation’s Quality Management System,

shall be submitted for evaluation and acceptance “Certificates of conformity”,

issued by a QMS certification body, shall only be recognised and accepted, when

such body has been accredited by a full member through being a current signatory

to a Multilateral Agreement or Mutual Recognition Agreement (MLA or MRA),

of the International Accreditation Forum (IAF) or, has been accredited by a full

member, of a regional member of the IAF.

13.1.4 The supplier shall furnish full particulars regarding its own organisation’s quality

management regime, including that of its sub-contractors.

13.2 Quality Planning

The supplier shall prepare and implement a Quality Assurance Plan (QAP), and Quality

Control Plans (QCP), relative to the products tendered.

13.2.1 All Quality Plans Shall:

a) Have its scope defined, incl. Specific exclusions, and conditions of validity.

b) Be based on the supplier’s documented quality management system (QMS).

c) Show the interface with the supplier’s documented QMS, and how the related

documents are applied, peculiar to the product(s) in question.

d) Cover each distinct stage of work to be performed / undertaken.

e) Indicate directly, or by reference to appropriate documented procedures or other

documents, how the required activities are to be carried out.

f) Be internally reviewed, and formally approved. Quality Plans therefore, shall be

formally controlled documents.

g) Provide for the customer’s viz. The Purchaser’s formal approval.

194 | P a g e

h) Upon revision, be subjected to review and approval by all parties previously

responsible, prior to implementation.

i) May be in any format deemed most suitable i.e. text, diagrammatic, matrix etc.

13.2.2 The Quality Assurance Plan (QAP) shall identify/indicate/define/reflect the

following in respect of the supplier, as applicable:

a) The organizational structure, depicting the current management hierarchy. The

structure shall extend from the policy maker, down to the supervisory level,

within each of the different production facilities/operations. The structure shall

clearly show lines of responsibility and shall reflect both the names of the

appointed persons, and their respective designations/position.

b) The management representative, having overall responsibility for quality.

c) Other key personnel having responsibility for Engineering/Design, Production,

Sales/Orders etc.

d) Personnel having responsibility for performing Q.C., inspection and testing

activities, and their relationship within the management structure.

e) Personnel responsible for the initiation and approval of corrective and

preventative actions, in the event of non-conforming product.

f) Communication channels between supplier and the purchaser’s representatives

g) Person specifically responsible for the handling of customer complaints, field

failures, warranty returns or non-conformance reports, relating to goods already

delivered, i.e. information receipt, work coordination, customer liaison, etc.

h) Work to be performed by 3rd party organizations and/or sub-contractors (the

exact nature, extent, and by which organization).

i) Specific quality monitoring/verification activities, to be undertaken on sub-

contractors.

j) Different physical locations, where supplier’s work will be performed, the

nature/extent thereof including work to be performed by sub-contractors.

k) The various production processes involved/to be undertaken, and their

relationship to each other e.g. by way of process flow charts.

l) Production processes requiring special controls.

m) Relevant Quality Control Plans (QCP) applicable, by reference number.

195 | P a g e

n) Quality records to be retained, specific to the product, including the language,

format and retention periods that will apply.

o) Quality records to be supplied to the Purchaser, by when and what means.

p) Documents to be submitted for the Purchaser’s approval, to whom, and by when.

q) Measures for the preservation of product quality after manufacture, during

delivery, and offloading.

13.2.3 The Quality Control Plan (QCP) addresses those planned arrangements specific to

the production process (es), which will ensure that the resulting product fully

meets all specified technical and quality requirements. It therefore identifies the

associated verification resources, including how, by whom, and when they will be

applied by the supplier. The exact scope and contents of the Quality Control Plan

(QCP) will be determined by nature and extent of work/processes involved.

The Quality Control Plan (QCP) shall identify/indicate/define/reflect the following as

applicable:

a) The applicable item, component, or product.

b) Various production operations or activities, relating to the different phases of

production, with due regard to the supplier’s scope of responsibility i.e.:

i. Engineering/Design & Development Validation.

ii. Procurement/Goods Receipt.

iii. Work to be sub-contracted to 3rd party organizations.

iv. Bought out materials & components under specification (finished/semi-

finished)

v. Customer supplied material.

vi. In-process product quality verification (Inspection & Testing).

vii. Special processes.

viii. Final product quality verification (Inspection & Testing).

ix. Packing/Protection/Delivery.

x. Erection/Installation.

xi. Commissioning.

c) Sequence of production operations/activities.

d) Appropriate in-process Q.C. activities to be applied i.e. Inspection and Test

points.

e) Relevant acceptance criteria for each Q.C. activity, with reference to the

applicable procedure, drawing, specification, parameter etc.

f) Relevant Quality Records to be generated, resulting from each Q.C. activity.

g) Customer interventions nominated i.e. hold and witness points.

196 | P a g e

h) Separate Quality Control Plans (QCP’s) are to be prepared for each

unique/different product type. However, variations by size/rating may be

accommodated by one generic plan where practicable.

13.2.4 Quality Control Plans (QCP’s) shall be reviewed by the purchaser or its

inspection authority/agency for acceptability, and shall allow for the insertion of

specific requirements, including hold and witness points as required.

13.2.5 Subsequent changes to the approved plans shall require the agreement of the

purchaser or its inspection authority/agency prior to the commencement of work

involving an activity affected by such changes.

13.3 Control of Records

13.3.1 Index of quality assurance/quality control and inspection and test records

The supplier shall prepare and submit an index of QA/QC and inspection and test

records, when so requested. The retention period and location shall be indicated

against each record type. The purchaser shall have the right to select which

documents shall be submitted to The Purchaser during the acceptance validity

period. The Purchaser will review the index and may request amendments. Once

this index has been accepted, it shall be adhered to by the contractor.

A copy of the approved data package shall be sent with every shipment of items or

equipment to the required delivery destination, or handed over to the Purchaser on

site, on completion of the activity concerned.

13.3.2 Discarding of quality records

No quality records shall be destroyed or discarded by the supplier, without prior

written consent.

13.3.3 Contractor’s Proprietary Documentation

Whenever the Purchaser and the supplier mutually agree that the supplier retains

quality records & documentation that the supplier considers proprietary

information, the supplier shall ensure that:

(i) Such records and documentation are kept suitably protected against

deterioration and/or damage for an agreed period;

(ii) The Purchaser is granted due access to such records and documentation, on

request; and

(iii)Such records and documentation are properly indexed and readily retrievable at

all times.

197 | P a g e

13.3.4 Access to Premises, Facilities, Documentation & Information

13.3.4.1 The Purchaser shall be afforded access to all areas of the supplier’s and

sub-contractors’ premises and facilities, to conduct quality audits, surveillance

or inspections to verify compliance with agreed requirements. The level of the

Purchaser monitoring may vary during the acceptance period, depending on

the supplier’s demonstrated performance and the degree of confidence

instilled.

13.3.4.2 All quality system documentation, records, reports etc. shall be made

available for review when requested by the Purchaser.

13.3.4.3 The supplier shall provide suitable facilities to the Purchaser and shall

supply any assistance necessary for the performance of any audit, surveillance

and/or inspection activities to be conducted.

13.3.5 Supplier’s Inspection & Testing

13.3.5.1 The supplier shall continually ensure that all work associated with product

has been fully inspected, tested in accordance with the specified technical

requirements, and formally accepted prior to dispatch. The supplier shall

compile, or acquire valid inspection records/test certificates, in respect of each

batch of product to be consigned. Inspection records/test certification shall be

held on file at the premises of the supplier. Copies of test certificates are to be

sent with every consignment of product, as required by the relevant technical

specification(s).

13.3.5.2 The supplier shall assess all inspection/tests results obtained, to determine

absolute compliance with the Purchaser’s specified technical requirements in

total. A certificate of conformance shall be drafted and issued, and shall

accompany every batch of product upon consignment.

198 | P a g e

13.3.6 Audit, Surveillance & product release inspection

13.3.6.1 The Purchaser reserves the right to audit quality management systems, and

verify all goods for conformance during any stage of production, immediately

prior to, or after delivery. The Purchaser or its inspection authority/agency

will conduct routine random product, process and or quality management

systems audits/inspections at the supplier’s or sub-contractor’s works, the

Purchaser storage facilities and construction sites, for the purpose of verifying

the continued compliance of product with the requirements of the applicable

specifications. These audits/surveillances/inspections may be performed

without any prior notification to the supplier or its sub-contractors.

13.3.6.2 No item of equipment requiring an the Purchaser inspection and release,

may be despatched to the required delivery destination, unless it has been

released by the Purchaser or the Purchaser’s authority/agency through a

Purchaser or the Purchaser’s authority/agency product release note, unless

otherwise agreed to by the Purchaser in writing. The supplier shall ensure that

one copy of the product release note is shipped with the equipment to site.

13.3.6.3 If components or materials, the manufacture of which was monitored ,

inspected and rejected by the Purchaser or the Purchaser’s appointed

inspection authority, are to be replaced by components not previously

monitored, inspected and released by the Purchaser or its appointed inspection

authority/agency, such substitution shall be the subject to a re-inspection by

the Purchaser or its appointed inspection authority/agency

13.3.6.4 Inspection, or the waiving of required inspections by the Purchaser or its

representative, shall in no way relieve the supplier from its obligation to

supply material that fully complies with all specified requirements, neither

shall it be construed as the Purchaser’s acceptance of any non-conforming

material.

199 | P a g e

13.3.7 Non-conforming materials, parts, workmanship or documentation

13.3.7.1 Supplier’s Non-Conformance Reports (NCR’s)

6Non-conformance reports shall be prepared by the supplier, in terms of

non-conforming materials, parts, workmanship, systems or documentation

and shall form part of the supplier’s permanent quality records.

13.3.7.1.1 All non-conformities that affect product form, fit, function,

interchangeability or maintenance as specified in the relevant reference

standard, technical specifications, the Purchaser approved drawings,

procedures and quality plans, shall be reported to the Purchaser.

13.3.7.1.2 Suppliers are not required to report to the Purchaser those non-

conformities that can be made to conform by REWORK by the

supplier/sub-contractor, providing the REWORK is part of the normal

practice during manufacture and where the relevant REWORK

procedures have been accepted by the Purchaser or its appointed

inspection authority/agency.

13.3.7.1.3 If the process of REWORK/REPAIR involves new special processes

i.e. welding, heat treatment, non-destructive examination procedures

that have not yet been approved by the Purchaser or the Purchaser’s

inspection authority/agency, or will have an effect on form, fit or

function of other acceptable materials, components, equipment,

structures or systems, then such non-conformances shall be reported to

the Purchaser or the Purchaser’s appointed inspection

authority/agency.

13.3.8 Purchaser non-conformance & inspection reject reports (NCR’s)

Non-conformance reports raised by the Purchaser and issued against the supplier, shall be

investigated by the supplier as a matter of urgency, in order to determine the root cause,

corrective action required and implementation timeframe.

13.3.8.1 A formal response shall be prepared in respect of the defined criteria, and

submitted to the Purchaser for review, evaluation and acceptance, within a

maximum of fourteen (14) calendar days from the date of issue of the NCR.

The Purchaser may at its discretion request a response sooner, and in any case

before proceeding with any pending/further intervention as may be required

from the Purchaser.

200 | P a g e

13.3.8.2 Supplier’s Non-Conformance Reports (NCR’s)

6 Non-conformance reports shall be prepared by the supplier, in terms of non-

conforming materials, parts, workmanship, systems or documentation and

shall form part of the supplier’s permanent quality records.

13.3.8.3 All non-conformities that affect product form, fit, function,

interchangeability or maintenance as specified in the relevant reference

standard, technical specifications, the Purchaser approved drawings,

procedures and quality plans, shall be reported to the Purchaser.

13.3.8.4 Suppliers are not required to report to the Purchaser those non-

conformities that can be made to conform by REWORK by the supplier/sub-

contractor, providing the REWORK is part of the normal practice during

manufacture and where the relevant REWORK procedures have been

accepted by the Purchaser or its appointed inspection authority/agency.

13.3.8.5 If the process of REWORK/REPAIR involves new special processes i.e.

welding, heat treatment, non-destructive examination procedures that have not

yet been approved by the Purchaser or the Purchaser’s inspection

authority/agency, or will have an effect on form, fit or function of other

acceptable materials, components, equipment, structures or systems, then such

non-conformances shall be reported to the Purchaser or the Purchaser’s

appointed inspection authority/agency.

13.3.9 Purchaser non-conformance & inspection reject reports (NCR’s)

13.3.9.1 Non-conformance reports raised by the Purchaser and issued against the

supplier, shall be investigated by the supplier as a matter of urgency, in order

to determine the root cause, corrective action required and implementation

timeframe.

13.3.9.2 A formal response shall be prepared in respect of the defined criteria, and

submitted to the Purchaser for review, evaluation and acceptance, within a

maximum of fourteen (14) calendar days from the date of issue of the NCR.

13.3.9.3 The Purchaser may at its discretion request a response sooner, and in any

case before proceeding with any pending/further intervention as may be

required from the Purchaser.

201 | P a g e

13.3.9.4 Shall the Purchaser or its inspection authority/agency identify any non-

conforming products during the conduct of its audits / surveillances /

inspections, the supplier shall be deemed to be in breach of the agreement, and

shall be held liable for any repair, rework and/or associated replacement costs.

The contractor may in such instances also be held liable for the full costs

associated with the conduct of follow-up audits / surveillances / inspections.

13.3.9.5 The nature, magnitude and or frequency of non-conformance and

inspection rejection reports raised by the Purchaser or its appointed inspection

authority/agency, shall form the basis of action to rescind the supplier’s

qualification status.

13.3.10 Cease delivery order

The Purchaser shall be authorized to stop any pending deliveries, and issue a

general cease delivery order, at any time for any portion of the work or service that

is not being executed in accordance with the specified/agreed requirements. When

such an order is issued, the supplier shall immediately stop all deliveries to all

destinations, and shall not resume until written authorization is again given by the

Purchaser.

202 | P a g e

13.3.11 Application for concession/production permit

a) Non-conforming materials, parts, workmanship when rejected by the supplier,

the Purchaser, or the Purchaser’s inspection authority/agency, may in certain

cases, be considered suitable for use “as is”, without the need for any

repair/rework. Non-conforming materials, parts or workmanship, shall be the

subject of a formal concession/production permit application. Such

application shall be prepared in the prescribed format, and submitted

electronically to the Purchaser, or the Purchaser’s inspection authority/agency

for consideration and processing.

b) The electronic application form to be used, shall be requested from the

Purchaser each time it is required.

c) A reportable non-conformance that cannot be REWORKED, and which the

supplier believes could be acceptable “as is”, shall be the subject of a

concession application.

d) A reportable non-conformance that can only be REPAIRED, shall be the

subject of a concession application.

e) If granted, concessions and production permits shall apply to specified

material, components or products, and be for a limited period/quantity only as

determined by the Purchaser. Concessions and production permits when

granted, shall never mean general acceptance.

f) Material deviations due to non-availability, mechanical properties, chemical

composition or similar problems, shall be the subject of a production permit

before any production commences.

13.3.12 Preservation of product quality and delivery

Preservation of product quality shall be in accordance with the requirements of the

ISO 9001:2000.

Specific requirements of this standard are as follows:

a) The supplier shall specify at the time of delivery any special

requirements for safe handling, storage, protection from environmental

degradation, shelf life and utilization.

b) Confirmation of receipt of quality related items by the Purchaser

personnel, by signing the delivery note, shall not be interpreted as

acceptance of the items.

c) Items shall be accepted or rejected only after receipt inspection that

involves inspection of the items and review of the quality assurance

data package to verify their conformance to requirements.

203 | P a g e

13.3.13 Quality documentation submissions to the Purchaser

13.3.13.1 Invitation stage.

The following documents shall be submitted to the Purchaser in response to a

formal invitation:

i. An uncontrolled copy of the supplier’s quality manual (not required if

proof of quality system certification is submitted)

ii. A controlled copy of the supplier’s Quality Assurance Plan (QAP)

iii. A controlled copy of the supplier’s Quality Control Plan(s) (QCP’s)

iv. Controlled copies of sub-contractor’s Quality Control Plan(s)

v. Copies of all formal agreements currently being held in respect of product

liability viz. “Manufacturing Licence”, “Agency”, “Consortium”, “Joint

Venture”, etc. where applicable

vi. An uncontrolled copy of the supplier’s current internal QMS audit

schedule

vii. Copies of both the supplier’s and sub-contractor’s QMS certification (as

applicable)

204 | P a g e

NOTE: Evaluation and acceptance of the supplier’s and respective sub-contractor’s

quality assurance capabilities, will be based on submissions in respect of the above

information, and an on-location verification/assessment.

The Purchaser’s record of past supplier/product performance will also be taken into

account where deemed relevant/necessary.

13.3.14 Post qualification/contract award

The following documents shall be maintained for the duration of the

qualification/contract validity period, and shall be submitted to the Purchaser or its

inspection authority/agency upon request:

(i) Approved Quality Assurance & Quality Control Plans (QAP & QCP’s)

(ii) An index of all relevant supplier QA/QC inspection and test records

(iii)Details of qualifications/certification of inspection and test staff and staff

performing special processes

(iv) Authorized concessions/production permits

(v) An index of the supplier’s purchase order numbers placed on sub-contractors,

including quantity, date, a description of items/equipment purchased, and

associated amendments

(vi) All supplier raised non-conformance reports in respect of non-conforming

materials, parts, workmanship, systems or documentation

(vii) All corrective actions taken as a result of non-conformances raised by the

supplier itself, or by the Purchaser.

13.3.15 On purchase order completion.

The following documents shall be submitted to the Purchaser on completion of each

purchase order, and shall be in the form of a data package accompanying the goods to the

required delivery destination. The data package contents shall be indexed, and contain the

following:

(a) All inspection and test reports identified in the relevant technical specifications, and

Quality Control Plans where indicated

(b) A certificate of conformance verifying that all specified technical and QA/QC

requirements have been satisfactorily complied with

(c) All material certificates as required

(d) the Purchaser approved concessions and

(e) the Purchaser inspection release reports.

205 | P a g e

14 APPENDICES

APPENDIX 1: 11KV AND 33KV LOAD BREAK SWITCH LOCAL CONTROLS AND

INDICATIONS

Function Feature Comment

Close Control &

Indication

A dedicated Red Button with associated status indication

shall be provided

Trip / Open Control &

Indication

A dedicated Green Button with associated status

indication shall be provided

Local / Remote Control &

Indication

A dedicated switch or Key Pad Button with associated

Status LED shall be provided or shall be configurable

Earth Fault in / out Control &

Indication

A dedicated switch or Key Pad Button with associated

Status LED shall be provided or shall be configurable

Sensitive Earth

Fault in / out

Control &

Indication

A dedicated switch or Key Pad Button with associated

Status LED shall be provided or shall be configurable

Auto Sectionalise

On / Off

Control &

Indication

A dedicated switch or Key Pad Button with associated

Status LED shall be provided or shall be configurable

Setting Group

Selection

Control &

Indication

Menu field and / or programmable switch or Key Pad

Button with associated Status LED

Detection Group A Control &

Indication

Menu field and / or programmable switch or Key Pad

Button with associated Status LED

Detection Group B Control &

Indication

Menu field and / or programmable switch or Key Pad

Button with associated Status LED

Detection Group C Control &

Indication

Menu field and / or programmable switch or Key Pad

Button with associated Status LED

Detection Group D Control &

Indication

Menu field and / or programmable switch or Key Pad

Button with associated Status LED

Detection Group E Control &

Indication

Menu field and / or programmable switch or Key Pad

Button with associated Status LED

Detection Group F Control &

Indication

Menu field and / or programmable switch or Key Pad

Button with associated Status LED

Detection Group G Control &

Indication

Menu field and / or programmable switch or Key Pad

Button with associated Status LED

Detection Group H Control &

Indication

Menu field and / or programmable switch or Key Pad

Button with associated Status LED

Detection Group I Control &

Indication

Menu field and / or programmable switch or Key Pad

Button with associated Status LED

Detection Group J Control &

Indication

Menu field and / or programmable switch or Key Pad

Button with associated Status LED

Phase A Live Indication Menu field and / or Dedicated or Programmable LED

Phase B Live Indication Menu field and / or Dedicated or Programmable LED

206 | P a g e

Phase C Live Indication Menu field and / or Dedicated or Programmable LED

Load Current On Indication Menu field and / or Dedicated or Programmable LED

A Phase OC Fault Indication Menu field and / or Dedicated or Programmable LED

B Phase OC Fault Indication Menu field and / or Dedicated or Programmable LED

C Phase OC Fault Indication Menu field and / or Dedicated or Programmable LED

Earth Fault Indication Menu field and / or Dedicated or Programmable LED

Sensitive Earth Fault Indication Menu field and / or Dedicated or Programmable LED

Negative Phase

Sequence Fault

Indication Menu field and / or Dedicated or Programmable LED

Under Voltage Fault Indication Menu field and / or Dedicated or Programmable LED

Over Voltage Fault Indication Menu field and / or Dedicated or Programmable LED

Operator Trip Indication Menu field and / or Dedicated or Programmable LED

Maintenance

Required

Indication Menu field and / or Dedicated or Programmable LED

Auxiliary Supply

Fail

Indication Menu field and / or Dedicated or Programmable LED

Battery disconnected Indication Menu field and / or Dedicated or Programmable LED

Battery Volts Low Indication Menu field and / or Dedicated or Programmable LED

Battery Low

Capacity (Low

Power Mode)

Indication Menu field and / or Dedicated or Programmable LED

Battery End of Life

(Battery Test Fail)

Indication Menu field and / or Dedicated or Programmable LED

Switchgear Locked Indication Menu field and / or Dedicated or Programmable LED

Contact Life Low Indication Menu field and / or Dedicated or Programmable LED

Close circuit

Isolated

Indication Menu field and / or Dedicated or Programmable LED

Trip Circuit Isolated Indication Menu field and / or Dedicated or Programmable LED

Dummy Circuit

Breaker Closed

Indication Menu field and / or Dedicated or Programmable LED

A Phase Current Analogue Menu field

B Phase Current Analogue Menu field

C Phase Current Analogue Menu field

A Phase Voltage Analogue Menu field

B Phase Voltage Analogue Menu field

C Phase Voltage Analogue Menu field

kWatts Analogue Menu field

kVars Analogue Menu field

Power Factor Analogue Menu field

Maximum Demand Analogue Menu field

207 | P a g e

APPENDIX 2 11KV AND 33KV LOAD BREAK SWITCH REMOTE CONTROLS AND

INDICATIONS

Function Feature

Close Control & Indication

Trip / Open Control & Indication

Earth Fault in / out Control & Indication

Sensitive Earth Fault in / out Control & Indication

Auto Sectionalise On / Off Control & Indication

Setting Group Selection Control & Indication

Detection Group A Control & Indication

Detection Group B Control & Indication

Detection Group C Control & Indication

Detection Group D Control & Indication

Detection Group E Control & Indication

Detection Group F Control & Indication

Detection Group G Control & Indication

Detection Group H Control & Indication

Detection Group I Control & Indication

Detection Group J Control & Indication

Local / Remote Indication

Phase A Live Indication

Phase B Live Indication

Phase C Live Indication

Load Current On Indication

A Phase OC Fault Indication

B Phase OC Fault Indication

C Phase OC Fault Indication

Earth Fault Indication

Sensitive Earth Fault Indication

Negative Phase Sequence Fault Indication

Under Frequency Fault Indication

Over Frequency Fault Indication

Under Voltage Fault Indication

Over Voltage Fault Indication

High Current Lockout Indication

Lockout Indication

Operator Trip Indication

Maintenance Required Indication

Auxiliary Supply Fai Indication

Battery disconnected Indication

Battery Volts Low Indication

Battery Low Capacity (Low Power Mode) Indication

Battery End of Life (Battery Test Fail) Indication

Switchgear Locked Indication

208 | P a g e

Contact Life Low Indication

Close circuit Isolated Indication

Trip Circuit Isolated Indication

Dummy Circuit Breaker Closed Indication

A Phase Current Analogue

B Phase Current Analogue

C Phase Current Analogue

A Phase Voltage Analogue

B Phase Voltage Analogue

C Phase Voltage Analogue

kWatts Analogue

kVars Analogue

Power Factor Analogue

Maximum Demand Analogue

209 | P a g e

APPENDIX 3 11KV AND 33KV RECLOSER LOCAL CONTROLS AND INDICATIONS

# Function Feature Comment

1 Close

Control &

Indication

A dedicated Red Button with associated

status indication shall be provided

2 Trip / Open

Control &

Indication

A dedicated Green Button with associated

status indication shall be provided

3

Local / Remote Control &

Indication

A dedicated switch or Key Pad Button

with associated Status LED shall be

provided or shall be configurable

4

Earth Fault in / out Control &

Indication

A dedicated switch or Key Pad Button

with associated Status LED shall be

provided or shall be configurable

5

Sensitive Earth Fault in

/ out

Control &

Indication

A dedicated switch or Key Pad Button

with associated Status LED shall be

provided or shall be configurable

6

Auto Reclose On / Off Control &

Indication

A dedicated switch or Key Pad Button

with associated Status LED shall be

provided or shall be configurable

7

Setting Group

Selection

Control &

Indication

Menu field and / or programmable switch

or Key Pad Button with associated Status

LED

8 Protection Group A

Control &

Indication

Menu field and / or programmable switch

or Key Pad Button with associated Status

LED

9 Protection Group B

Control &

Indication

Menu field and / or programmable switch

or Key Pad Button with associated Status

LED

10 Protection Group C

Control &

Indication

Menu field and / or programmable switch

or Key Pad Button with associated Status

LED

11 Protection Group D

Control &

Indication

Menu field and / or programmable switch

or Key Pad Button with associated Status

LED

12 Protection Group E

Control &

Indication

Menu field and / or programmable switch

or Key Pad Button with associated Status

LED

13 Protection Group F

Control &

Indication

Menu field and / or programmable switch

or Key Pad Button with associated Status

LED

14 Protection Group G

Control &

Indication

Menu field and / or programmable switch

or Key Pad Button with associated Status

LED

210 | P a g e

15 Protection Group H

Control &

Indication

Menu field and / or programmable switch

or Key Pad Button with associated Status

LED

16 Protection Group I

Control &

Indication

Menu field and / or programmable switch

or Key Pad Button with associated Status

LED

17 Protection Group J

Control &

Indication

Menu field and / or programmable switch

or Key Pad Button with associated Status

LED

18 Phase A Live Indication

Menu field and / or Dedicated or

Programmable LED

19 Phase B Live Indication

Menu field and / or Dedicated or

Programmable LED

20 Phase C Live Indication

Menu field and / or Dedicated or

Programmable LED

21 Load Current On Indication

Menu field and / or Dedicated or

Programmable LED

22 A Phase OC Fault Indication

Menu field and / or Dedicated or

Programmable LED

23 B Phase OC Fault Indication

Menu field and / or Dedicated or

Programmable LED

24 C Phase OC Fault Indication

Menu field and / or Dedicated or

Programmable LED

25 Earth Fault Indication

Menu field and / or Dedicated or

Programmable LED

26 Sensitive Earth Fault Indication

Menu field and / or Dedicated or

Programmable LED

27

Negative Phase

Sequence Fault Indication

Menu field and / or Dedicated or

Programmable LED

28 Under Frequency Fault Indication

Menu field and / or Dedicated or

Programmable LED

29 Over Frequency Fault Indication

Menu field and / or Dedicated or

Programmable LED

30 Under Voltage Fault Indication

Menu field and / or Dedicated or

Programmable LED

31 Over Voltage Fault Indication

Menu field and / or Dedicated or

Programmable LED

32 High Current Lockout Indication

Menu field and / or Dedicated or

Programmable LED 33

34 Lockout Indication

Menu field and / or Dedicated or

Programmable LED

211 | P a g e

35 Operator Trip Indication

Menu field and / or Dedicated or

Programmable LED

36 Maintenance Required Indication

Menu field and / or Dedicated or

Programmable LED

37 Auxiliary Supply Fail Indication

Menu field and / or Dedicated or

Programmable LED

38 Battery disconnected Indication

Menu field and / or Dedicated or

Programmable LED

39 Battery Volts Low Indication

Menu field and / or Dedicated or

Programmable LED

40

Battery Low Capacity

(Low Power Mode) Indication

Menu field and / or Dedicated or

Programmable LED

41

Battery End of Life

(Battery Test Fail) Indication

Menu field and / or Dedicated or

Programmable LED

42 Switchgear Locked Indication

Menu field and / or Dedicated or

Programmable LED

43 Contact Life Low Indication

Menu field and / or Dedicated or

Programmable LED

44 Close circuit Isolated Indication

Menu field and / or Dedicated or

Programmable LED

45 Trip Circuit Isolated Indication

Menu field and / or Dedicated or

Programmable LED

46

Dummy Circuit

Breaker Closed Indication

Menu field and / or Dedicated or

Programmable LED

47 A Phase Current Analogue Menu field

48 B Phase Current Analogue Menu field

49 C Phase Current Analogue Menu field

50 A Phase Voltage Analogue Menu field

51 B Phase Voltage Analogue Menu field

52 C Phase Voltage Analogue Menu field

53 kWatts Analogue Menu field

54 kVars Analogue Menu field

55 Power Factor Analogue Menu field

56 Maximum Demand Analogue Menu field

APPENDIX 4 11KV AND 33KV RECLOSER REMOTE CONTROLS AND

INDICATIONS

# Function Feature

212 | P a g e

1 Close Control & Indication

2 Trip / Open Control & Indication

3 Earth Fault in / out Control & Indication

4 Sensitive Earth Fault in / out Control & Indication

5 Auto Reclose On / Off Control & Indication

6 Auto Sectionalise On / Off Control & Indication

7 Setting Group Selection Control & Indication

8 Protection Group A Control & Indication

9 Protection Group B Control & Indication

10 Protection Group C Control & Indication

11 Protection Group D Control & Indication

12 Protection Group E Control & Indication

13 Protection Group F Control & Indication

14 Protection Group G Control & Indication

15 Protection Group H Control & Indication

16 Protection Group I Control & Indication

17 Protection Group J Control & Indication

18 Local / Remote Indication

19 Phase A Live Indication

20 Phase B Live Indication

21 Phase C Live Indication

22 Load Current On Indication

23 A Phase OC Fault Indication

24 B Phase OC Fault Indication

25 C Phase OC Fault Indication

26 Earth Fault Indication

27 Sensitive Earth Fault Indication

28 Negative Phase Sequence Fault Indication

29 Under Frequency Fault Indication

30 Over Frequency Fault Indication

31 Under Voltage Fault Indication

32 Over Voltage Fault Indication

33 High Current Lockout Indication

34 Lockout Indication

35 Operator Trip Indication

36 Maintenance Required Indication

37 Auxiliary Supply Fail Indication

38 Battery disconnected Indication

39 Battery Volts Low Indication

40 Battery Low Capacity (Low Power

Mode) Indication

213 | P a g e

41 Battery End of Life (Battery Test Fail) Indication

42 Switchgear Locked Indication

43 Contact Life Low Indication

44 Close circuit Isolated Indication

45 Trip Circuit Isolated Indication

46 Dummy Circuit Breaker Closed Indication

47 A Phase Current Analogue

48 B Phase Current Analogue

49 C Phase Current Analogue

50 A Phase Voltage Analogue

51 B Phase Voltage Analogue

52 C Phase Voltage Analogue

53 kWatts Analogue

54 kVars Analogue

55 Power Factor Analogue

56 Maximum Demand Analogue

APPENDIX 5: LIST OF 11KV AND 33KV LOAD BREAK SWITCHES AND 11kV RING

MAIN UNITS

RING MAIN UNITS

214 | P a g e

Nairobi North

No.

Primary Sub-Stations

Fdr #.

Feeder Name Existing RMUs

Proposed new RMUs

Proposed new install

Proposed Automation only

Proposed integration

1 Baba Dogo 66/11kV

1 Baba Dogo Dawa (2) 1

2 Brewery Central Glass(2) 1

2 Eastleigh 66/11kV 1 Moi Airbase MAB (2) 1

3 Parklands 66/11kV

1

Kirinyaga

Garden Plaza(2) – A

Asili (2)

1

1

2 Capitol Arrow (2) 1

3 Stima Plaza Stima Plaza(2)-A 1

4 Westlands Sankara (2) 1

5 Welbeck Westgate(2) 1

6 Riverside Villa Rosa(2) 1

7 University Way Boulevard(3)* 1

8 Lower Kabete Swaminarayan(2) 1

9

Norfolk

UON - Eng.(2)

Longonot (3)* National Theatre(2) UON - Main(2)

3

4 Jeevanjee 66/11kV

1

Gwasi

Gwasi(3)

1

2 City Hall Mwalimu (2) City Hall(4)

Leone Casino(2) Supreme Court(2)

2

1 1

3

Development Hse

Development Hse (3) Kenya Poly(2)

Afya (2) Old Gov't Press(3)* New Gov't Press(2)

3

1

4 KPCU

Co-op Hse (2)-A Bakery (2) -A NHC (2) KU Plaza (2)

Kenbanco (2) Post Office(2) Canon(2) CBK (2)

4

2

2

5 Cathedral Times Towers(2) -A Vigilance Hse(2) 1 1

6

Temple Rd

Temple Rd(3) Kencom (3) Jubilee(2) I.L. Hse (2)

Rahimtula (3)* Re-Insurance(2) ICDC (3)* Auto Silo(2) Hilton(3)*

5

4

0

7

City Square

City Square(3,2) Kenya Cinema(2) –A BP Shell(2)-A OP(2)-A

Info Hse(2) Elec. Hse (2) Bima (2) Treasury(2)

6

3

215 | P a g e

Jogoo House (2) Intercon(2) KICC(4,1)

5 Capitol 11kV 1

Union Towers

Corner Hse(2) Stanley Hotel(2)

IPS(2) Lonrho (2) Rehema(2) 3

2 Kimathi Kimathi Hse(2) Contrust Hse(2) Pioneer(2) 2

3

Rupsons

Marble Arc (2) Tom Mboya(3) Bidco(2)

Odeon(2) Imenti(2) Mithoo(2) Lyric Hse(2)

4

6

University Way 11kV

1

Lilian Towers

Consolidated(2) –A

Summit(2) Nakumatt Towers(2) Nginyo(2), Four Ways(2)

4

1

7

Cathedral 66/11kV

1

GPO

Bruce Hse(2)

Orange Telcom(2) Cardinal Otunga(2) 680 Hotel(2) Fedha Towers(2)

4

1

2

PC HQ

PC HQ (2) -A KNA (2) National Assembly(2) –A

Harambee Sacco(2) Continental Hse (2)

2

1

2

3

KTDC

Hazina(2) -A

Nyati (2) KTDC (2) View Park (2) AM Bank (2) Posta Sacco(2)

5

1

4 Market

Virani(2) City Mkt(2)

Finance(2) HFCK(2) Macmillan(2) Soko Reality(2) Nation Centre (4)

5

2

8 Muthurwa 66/11kV 1 Gikomba Nacico (2) -A 0

1

2 Muthurwa Mkt

Interfina(2) Muthurwa Mkt(2) Ronald Ngala (2) 1

2

9

Ruaraka 132/66/11kV 1

Central Glass MISC (2/2) 1

10 Donholm 11kV 2

Commercial Street Numerical (2)

1

Nairobi West

No.

Primary Sub-Stations

Feeder No.

Feeder Name Existing RMUs Proposed RMUs

Proposed new install

Proposed Automation only

Proposed integration

216 | P a g e

2

Nairobi West 66/11Kv 1 Ngong Rd KCB Hse (2) 1

2 Lower Hill NIC(2) Nyayo Stadium(2) 1

3 Ngong Rd 66/11Kv 1 Kilimani Yaya (2) 1

2 DOD Equity/DOD(2) 1

13 Ragati 66/11Kv 1 Upperhill BHC(2)

Upperhill Rd(3), City Bank(2) 2

2 Milimani NSSF(2) Integrity (2) 1

3 Mara World Bank(2) 1

4 Britam NHIF(2) 1

Cathedral 66/11Kv Hill 1

Serena(2), Alico (2) 2

Nairobi South

No.

Primary Sub-Stations

Fdr#

Feeder Name Existing RMUs Proposed RMUs

Proposed new install

Proposed Automation only

Proposed integration

1

Nairobi South 66/11Kv 1 Kampala2 BAT(2) 1

2 Nairobi South 1

Nairobi South 1 Sera Coating(2) 1

2 Nairobi South 2 House of Maji(2) 1

3 Dara 1 Rubber & Plastics(2) 1

4 Villa franca Tetra(2) 1

5 EAO BOC(2) 1

6 Mombasa Rd Panari(2) 1

8 Dara 11Kv 1 Railway B Commercial Street(2) 1

Nairobi West 66/11Kv 2 Dara 2 Dara(2)* 0

TOTAL 83 18 15

LOAD BREAK SWITCHES Nairobi North

No. Primary Sub-Stations

Feeder No. Feeder Name Existing LBSs Proposed LBSs

Proposed TOTAL

1 Baba Dogo 66/11kV 1 Dandora Y3076, Y398, Y3192 3

2 Indigo Y3189 1

217 | P a g e

3 Baba Dogo Y336, Y3179, Y3181, Y337, Y304 5

4 Kenafric Y3178 1

5 Kariobangi Y3094 1

6 Brewery Y307, Y3176 2

7 Kasarani Y3082, Y3112, Y2025, Y2026, Y2075, Y3078, Y2128 7

8 Lucky Summer Y3193 1

2 Kitisuru 66/11kV 1 Unep Y443, Y5070, Y201 Y2064, Y4150 2

2 Runda Y290, Y245, Y286, Y2100, Y2006

Y284, Y285, Y7266, Y2106, Y2107, Y7263 6

3 Spring Valley Y4146, Y430, Y433, Y412, Y2014, Y200 Y2037, Y2088 2

4 Kihara Y435 Y4080, Y4076, Y417, Y444 4

3 Lower Kabete 66/11kV 1 Farasi Lane Y459, Y460 2

2 King'eero Y472 1

4 Gigiri 66/11kV 1 Thigiri Y2080

2 ICRAF Y207, Y208 Y292 1

3 Whispers Y296, Y2038 2

4 Village Market Y294, Y7265 2

5 Ridgeways 66/11kV 1 Rock City Y7274, Y2058, Y301, Y7186 4

2 Windsor Y2048, Y2049 2

3 Garden Estate Y7273 1

4 Mimosa Y7264 1

5 Evergreen Y2022

6 Eastleigh 66/11kV 1 Mathare North Y333, Y2077, Y3188 3

2 Light Industries Y316, Y3095 2

3 Kamunde rd

4 Kiamaiko

5 Juja Rd Y319, Y2044, Y2043, Y323, Y318 5

6

Pioneer

Y350, Y3092, Y3084, Y3088, Y3089, Y3020 6

7 Kariobangi South Y368 1

7 Parklands 66/11kV 1 Kirinyaga Y315, Y4134 2

2 Eastleigh Y603, Y4126, Y322, Y3074, Y325, Y3098 6

3 Kabete Y400 Y4162, Y4074, Y4075 3

4 Muthaiga Y206, Y210, Y208, Y209, Y3184 Y414 1

5 Westlands Y495, Y409 Y2090, Y496, Y402, Y401 4

6 Welbeck Y4096, Y4007 Y2036, Y455, Y456, Y5124 4

7 Riverside Y4102 Y426 1

8 University Way 0

9 Lower Kabete Y4097 Y5117, Y439 2

10 Gwasi Y391, Y3097 Y6178, Y602,Y3170 3

11 Pangani Y4133, Y300, Y3211, Y341 4

8 Komarock 66/11kV 1 Saika Y3005 1

2 Mowlem Y3086 1

9 Ruai 66/11kV 1 Njiru Y3002* Y399, Y3141 3

10 Westlands 66/11kV 1 Waiyaki Way Y405* Y410, Y419, Y406, Y447 5

2 Sarit Y4149,Y404 Y4155, Y4160 2

3 Raphta Y4156, Y7228, Y432, Y416 4

4 Peponi Y413, Y4161 Y482 1

5 Highridge Y438, Y4106 2

6 Kyuna Y4117 Y415, Y446, Y4173, Y492, Y2068, Y4168, Y4167 7

218 | P a g e

16 Muthurwa 66/11kV 1 Gikomba Y3096 1

2 OTC Y3213 1

17 Kimathi 66/11kV 1 Airforce Y2129, Y2042 2

2 1st Avenue Y611, Y3143, Y4139, Y3180, Y320 5

3 Bahati Y644, Y362 Y687, Y361, Y6195 3

4 Buruburu Y2039, Y2037, Y355, Y667, Y623, Y705, Y359 7

5 Harambee Y2038 1

18 Ruaraka 132/66/11kV 1

Sports Complex Y3111 1

2 Breweries 1 Y2069, Y305, Y3053, Y3156, Y3158 5

3 Breweries 2 Y2082, Y389 2

4 Ridgeways Y2053 Y317, Y2091, Y311, Y312, Y2067 5

5 Githurai Y8081, Y3000, Y7258, Y8053, Y826, Y8049, Y3010 7

6 Kiambu Y3119, Y3122, Y2051, Y326 4

7 Sietco Y7251, Y2057 2

8 Kahawa Y2033, Y3007, Y4072, Y2052, 4

9 Roysambu Y3050 1

10 Sukari Y4130, Y3082, Y3083, Y2029, Y2030, Y8074 6

Donholm 11kV 2 Commercial Street Y604 Y7182, Y7170, Y7036 3

3 Loresho Y420, Y462, Y4077 3

Kabete 66/11kV 5 Kanyariri Y491, Y4128, Y4125 3

TOTAL 188

Nairobi West

No. Primary Sub-Stations

Feeder No. Feeder Name Existing LBSs Proposed LBSs

Proposed TOTAL

1 Kileleshwa 66/11Kv 1 State house Y5048, Y5049, Y5047

Y4163, Y505, Y5154, Y5120, Y5155 5

2 Hurlingham

Y500, Y506, Y5045, Y522, Y5022, Y535, Y5022, Y509, Y5062 9

3 Riverside Y4094, Y4095, Y418, Y4101, Y442 5

4 Kenya High Y403, Y431 2

5 Lavington Y5030, Y551, Y5081, Y5114, Y5000, Y518, Y514, Y110 8

6 Kawangware Y5074, Y5197, Y5228, Y5113, Y537, Y5098, Y5063, Y5064 8

7 Elgeyo Marakwet Y5196, Y521, Y507 3

8 Kangemi Y536, Y5009, Y461, Y557, Y515, Y5095, Y407 7

2 Nairobi West 66/11Kv 1 Lang'ata

Y542, Y559, Y558, Y159, Y121, Y543, Y181, Y145, Y168 4

2 South C Y574, Y7034, Y5085, Y5089 2

3 Dam Y186, Y169, Y195 Y5172, Y5149, Y5151, Y1120 4

4 Hurlingham Y560 Y5184, Y555, Y529, Y561, Y5183 5

5 Ngong Rd Y5185, Y5072, Y530 3

6 Lower Hill Y540 Y5077, Y5232 2

3 Ngong Rd 66/11Kv 1 Government Hill

Y534, Y5007, Y5079, Y5008 Y528, Y5006, Y5150 3

2 Nairobi Hospital Y526, Y516, Y5053 Y2098, Y517, Y5159 3

3 Kibera Y563 Y5054 1

4 Kilimani Y5165, Y533 2

219 | P a g e

4 Karen 66/11Kv 1 Dagoretti Y107, Y106, Y109, Y133, Y148, Y5205, Y149, Y5207, Y4030 9

2 Lang'ata Y170, Y104 2

3

Kiserian

Y155, Y173, Y129, Y139, Y164, Y103, Y102, Y105, Y117, Y115, Y132 11

4 VOK Y1115, Y125, Y126, Y171, Y131 5

5 Lavington Y158, Y112, Y160, Y114, Y7208 5

6 Ngong Rd Y136, Y5060, Y116, Y154, Y123, Y538, Y5050, Y5179 6

5 Matasia 66/11Kv 1 Ngong Hills Y189, Y128, Y127 3

2 Lower Matasia Y1102, Y5131, Y5088, Y182, Y196, Y5066, Y5191, Y5067 8

3 Kiserian Y163, Y1112, Y1119, Y192, Y199, Y1000 6

4 Nkoroi Y5091, Y1114, Y172 3

5 Ongata Rongai Y162, Y1110 2

7 Kabete 66/11Kv 1 Waithaka Y5110, Y4147, Y4121, Y5181, Y4123, Y4023, Y5101, Y4009 8

2 Riruta Y5109, Y5082, Y120, Y123 4

3 Mt. View Y4078, Y5105, 2

8 Ngong Town 66/11Kv 1 Kahara Y1124, Y161, Y1128, Y1127 4

2 Ololua Y179, Y108, Y5084 3

3 Ngong Vet Y1131, Y140 2

4 Kibiku Y1117, Y1109, Y1125, Y1130 4

9 Lang'ata 66/11Kv 1 Hardy Y1103, Y1104, Y101, Y113 Y146, Y1118 2

2 Karen Hospital Y119 Y122, Y1113 2

3 Magadi Rd Y100, Y143, Y137, Y2011 4

10 Kajiado 33/11kV 1 Namanga 33kV Line X115, X116, X118, X119, X121 5

2 Town Y673 1

11 EPZ 66/11Kv 1 Kajiado 33kV line X110, X111, X112, X123 4

2 Apex Y6210 1

3 Kitengela Y7211, Y7212 2

4 Interconnector Y666 1

5 EPZ 1 Y6116, Y7066, Y6117, Y6118, Y6119 5

12 Loitoktok 33/11kV 1 Loitoktok 1 Y724, Y725, Y5219, Y5214, Y5216 5

13 Ragati 66/11kV 1 Upperhill Y513 Y5078 1

2 Bishops Rd Y525 Y5157, Y5156 2

3 Delamere Y502, Y544 2

4 Community Y5158, Y5038 2

5 Mara Y5090, Y5057, Y512 Y511 1

6 Britam Y5145, Y5061, Y5233 3

Cathedral 66/11Kv 1 Hill 1 Y5051 Y501, Y503, Y504 3

2 State house Y552, Y523, Y5047 Y5076, Y5239 2

University Way 11kV 3 University Halls Y552, Y554

TOTAL 211

Nairobi South

No. Primary Sub-Stations

Feeder No. Feeder Name Existing LBS Proposed LBSs

Proposed TOTAL

1 Nairobi South 66/11kV 1 Mogadishu Y7191, Y690, Y682 Y706, Y681, Y6215 3

2 Airport Y378, Y728, Y6216, Y3169 4

220 | P a g e

3 Outering Rd Y352, Y3031, Y363, Y3190 4

4 Kampala 1 Y674 Y744 1

5 Kampala 2 Y743 1

6 Donholm 1 Y700, Y712, Y660, Y606, Y610 Y7197, Y6225, Y615 3

7 Donholm 2 Y683* Y7153, Y7194 3

8 GM Y7206 Y783, Y7208, Y7207 3

9 Industrial 1 Y7162 1

10 Industrial 2 Y7136 Y6145, Y9370 2

11 Athi Y7211 Y7198, Y7186 2

12 Wundanyi Y7135 Y9365 1

13 Raiply Y9362, Y9366, Y6246, Y9303, Y9344 5

2 Industrial 66/11kV 1 Nairobi South 2 Y7199 Y9351, Y601, Y617, Y7180, Y9305 5

2 Dara 1 Y647, Y648*, Y670, Y663 Y656, Y731, 3

3 Dara 2 Y612, Y608 Y613, Y614, 2

4 Villafranca Y7006, Y7203 Y775, Y6316 2

5 Kampala Rd Y6254 1

6 Rollmills Y# Y7175 1

7 Mombasa Rd Y7108, Y7028 Y7126 1

8 Kencell Y7125 Y7178, Y7179 2

3 Mombasa Rd 66/11kV 1 Nation Printers Y6194, Y6165 Y6189 1

2 Airport Y631, Y6263 2

3 Imara Daima Y7107, Y7210 Y7189 1

4 Mombasa Rd Y7194, Y7023 Y7026, Y7030 2

5 Maasai Y7215 1

6 Lab & Allied Y7202, Y7177 2

4 Athi 66/33/11kV 1 Machakos 33kV line

X707, X708, X22, X23, X236, X28, X24, X220, 8

2 Apex Y6137, Y6211 2

3 Katani Y6284, Y6285, Y624, Y640 4

4 KMC 1 Y618, Y621, Y9120, Y627, Y9121, Y620 6

5 KMC 2 Y695, Y632 2

6 Devki Steel Y7063 1

7 Arvind Y9345 1

5 NSSF 66/11kV 1 Airport Y7114, Y7183, Y7181, Y6215, Y7188 5

2 Coca-Cola Y7199, Y7185, Y622, Y676 4

3 Fedha Y630 Y7197, Y6075, Y6076 3

6 New Airport 66/11kV 1 Imara Daima Y6167

Y9321, Y6133, Y6168, Y6234, Y6238, Y6262, Y6204 7

2 Athi Y7192, Y766, Y9315, Y6260, Y9316, Y688 6

3 Nice & Lovely Y625 Y7193, Y9314, Y6166, Y6223 4

4 Oserian Y9321 1

7 Syokimau 66/11kV 1 Mlolongo Y6025, Y6074, Y6247, Y6026 2

2 Quarry Y# Y6248, Y9346 2

3 Katani Y6273 1

8 Dara 11kV 1 Railway B Y754, Y#, Y675 Y646, Y753, 2

9 Donholm 11kV 1 Lusaka Y714, Y7012, Y7173 Y715, Y713 2

10 Machakos 33/11Kv 1 Masii 33kV line X11, X13, X112, X1109, X1106, X111, X16, X19 8

2 Town Y6230, Y6024, Y655, Y654, Y6089 5

3 Athi Y6083, Y6137, Y629, Y628, Y6213 5

221 | P a g e

4 Kathiani Y9338, Y6009, Y6157 3

11 Kiboko 132/33kV 1 Wote 33kV line

X9318, X20, X235, X31, X35, X37, X33, X230, X36, X229, X223, X225 12

2 Kibwezi 33kV line X8, X9, X11, X12, X13 5

12 Ruai 66/11kV 1 Joska Y3021, Y3003, Y9320 3

2 Utawala Y7191, Y3093 2

3 Kibiku Y3210 1

4 Sewage Y3216 1

13 Lukenya 66/11kV 1 Sabaki Y9348 1

2 Kinanie Y9333 1

14 Villa Franca 1 Mukuru Y7209 Y9373 1

2 Plot 10 Y7137, Y6214 2

3 Riara Y6217 Y726 1

15 Nairobi West 66/11Kv 9 South B

Y6100, Y7174, Y7115, Y637 Y7207, Y6253, Y697 3

10 Industrial Y665, Y758, Y663, Y609, Y607, Y605, Y642 Y7176, Y9312, Y643 3

16 Komarock 66/11Kv 8 Mihang'o Y3040 Y3016, Y3171 2

9 Umoja Y3150, Y3151, Y3107, Y3168, Y3199, Y3172, Y3087 7

10 Greenspan Y3090, Y3198, Y3196, Y3197 4

TOTAL 190

North Eastern Region

No. Primary Sub-Stations

Feeder No. Feeder Name Existing LBSs Proposed LBSs

Proposed TOTAL

1 Ruiru 66/33/11Kv 1 Town Y8077, Y819, Y8007, Y856, Y859 5

2 Kenyatta University

Y2115, Y820, Y821, Y822, Y340, Y2033, Y2059 7

3 Kiambu Y8033, Y2111 2

4 Brookside Y2096, Y3195, Y8069 3

5 Nyaga 33kV X113, X213 2

2 Nyaga 33/11Kv 1 Githunguri Y8004, Y997, Y8012 3

2 Ruiru Y845, Y854, Y2112, Y857, Y816, Y832, Y813, Y814 8

3 Kikuyu 66/11Kv 1 Uthiru Y4115, Y422, Y480, Y4017, Y5189, Y4031 6

2 Kabete Y4008, Y470, Y4003 3

3 Muguga Y423, Y478, Y441, Y297, Y5121 5

4 Town Y4122 1

4 Cianda 66/11Kv 1 Muthaiga Y265, Y250, Y7206, Y4166, Y8013, Y2021, Y8015 7

2 Kiambu Y268, Y295, Y3194, Y393, Y324, Y346, Y2019 7

3 Ridgeways Y215, Y214, Y2102 3

4 Redhill Y217, Y233, Y216, Y218, Y2094, Y203, Y222, Y249 8

5 Limuru 66/11Kv 1 Bata Y262, Y2010, Y234, Y223 4

2 Town Y241, Y236, Y298 3

3 Welbeck Y205, Y225, Y204, Y436, Y5135 5

4 Muthaiga Y227, Y279, Y280, Y7184, Y8014, Y220, Y270 7

5 Uplands Y239, Y246, Y5168, Y257, Y5087 5

6 Mai Mahiu 66/11Kv 1 Kijabe Y243 1

7 Rironi 66/11Kv 1 Kiambaa Y686, Y5152 2

222 | P a g e

2 Rironi Y425 1

3 Nduma Y5134 1

4 Kerwa Y5069 1

Lower Kabete 66/11Kv 3 Ndumboini Y4126 1

4 Wangige Y2118 1

Ridgeways 66/11Kv 6 Kigwa

Y331, Y212, Y2018, Y232, Y217, Y313, Y394, Y330, Y3070, Y3072 10

Kitisuru 66/11Kv 5 Redhill Y2040 Y238, Y473, Y202, Y287, Y2113, Y2079 6

6 Ngecha Y288, Y2117, Y499 3

TOTAL 121

APPENDIX 6: SPECIFICATIONS FOR CONCRETE POLES

223 | P a g e

224 | P a g e

225 | P a g e

226 | P a g e

227 | P a g e

228 | P a g e

229 | P a g e

230 | P a g e

231 | P a g e

232 | P a g e

233 | P a g e

234 | P a g e

235 | P a g e

236 | P a g e

237 | P a g e

APPENDIX 7: SPECIFICATIONS FOR LV FUSE PANELS

238 | P a g e

239 | P a g e

240 | P a g e

241 | P a g e

242 | P a g e

243 | P a g e

244 | P a g e

245 | P a g e

246 | P a g e

247 | P a g e

248 | P a g e

249 | P a g e

APPENDIX 8 : SPECIFICATIONS FOR CONDUCTOR JOINTS

250 | P a g e

251 | P a g e

252 | P a g e

253 | P a g e

254 | P a g e

255 | P a g e

256 | P a g e

257 | P a g e

258 | P a g e

259 | P a g e

APPENDIX 9: INDUCTIVE VOLTAGE TRANSFORMER GUARANTEED TECHNICAL DATA

# UNIT EMPLOYER’S BIDDER’S

1 MANUFACTURER

2 TYPE

3 STANDARDS APPLIED - IEC 60044-2

4 SERVICE CONDITIONS - OUTDOOR

5 RATED SYSTEM VOLTAGE kV 11

6 HIGHEST SYSTEM

VOLTAGE

kV 12

7 RATED FREQUENCY Hz 50

8 RATED PRIMARY VOLTAGE

kV 11

9 WINDING 1

RATED SECONDARY

VOLTAGE ACCURACY

CLASS

RATED BURDEN

V

-

VA

230

3

200

10 RATIO kV 11 : 0.23

11 VOLTAGE FACTOR - 1.2 continuous

12 RATED POWER FR.

WITHSTAND VOLTAGE

(PRIMARY, DRY)

kV rms 28

13 RATED POWER FR.

WITHSTAND VOLTAGE

(SECONDARY)

kV rms 3

14 IMPULSE WITHSTAND

VOLTAGE (1.2 / 50 μ sec.)

kV peak 75

15 INSULATING MEDIUM EPOXY RESIN

16 CREEPAGE DISTANCE mm 840

260 | P a g e

APPENDIX 10: PROJECT MANAGEMENT, QUALITY ASSURANCE AND

DOCUMENTATION

This section describes the project management, schedule and quality assurance and documentation

requirements for the project.

10.1 Project Management

The Contractor shall assign a project manager with the authority to make commitments and

decisions that are binding on the Contractor. Employer will designate a project manager to

coordinate all Employer project activities. All communications between Employer and the

Contractor shall be coordinated through the project managers. The project managers shall also be

responsible for all communications between other members of the project staffs. Bidder shall

submit the manpower deployment plan along with the bids, describing the key roles of each

persons.

10.2 Project Schedule

The project implementation schedule shall be not exceed 24 months from the date of award. Based

upon this schedule, the bidder shall submit a preliminary implementation plan along with the bid.

The detailed project implementation schedule shall be submitted by the contractor after award for

Employer’s approval, which shall include at least the following activities:

(a) Site Survey

(b) Documents submission and approval schedule

(c) Factory & Site Testing Schedule

(d) Database development schedule

(e) Hardware purchase & Manufacturing, Software development & integration schedule

(f) Dispatch Schedule

(g) Installation / commissioning schedule

(h) Training schedule

The project schedule shall include the estimated period for completion of and its linkage with other

activities.

10.2.1 Progress Report:

A progress report shall be prepared by the Contractor each month against the activities listed in

the project schedule. The report shall be made available to Employer on a monthly basis, e.g., the

10th of each month. The progress report shall include all the completed, ongoing and scheduled

activities.

10.3 Transmittals

Every document, letter, progress report, change order, and any other written transmissions

exchanged between the Contractor and Employer shall be assigned a unique transmittal number.

The Contractor shall maintain a correspondence index and assign transmittal numbers

consecutively for all Contractor documents.

261 | P a g e

Employer will maintain a similar correspondence numbering scheme identifying documents and

correspondence that Employer initiates.

10.4 Quality Assurance & Testing

All materials and parts of the system / sub-system to be supplied under the project shall be of

current manufacture from a supplier regularly engaged in the production of such equipment.

10.4.1 Quality Assurance and Quality Control Program

The Contractor shall maintain a Quality Assurance/Quality Control (QA/QC) program that

provides that equipment, materials and services under this specification whether manufactured,

designed or performed within the Contractor's plant, in the field, or at any sub-contractor source

shall be controlled at all points necessary to assure conformance to contractual requirements. The

program shall provide for prevention and ready detection of discrepancies and for timely and

positive corrective action. The Contractor shall make objective evidence of quality conformance

readily available to the Owner. Instructions and records for quality assurance shall be controlled

and maintained at the system levels. The Contractor shall describe his QA/QC program in the

Technical Proposal, (along with samples from his QA/QC manual) and shall submit his QA/QC

Manual for review and acceptance by the Owner. Such QA/QC program shall be outlined by the

Contractor and shall be finally accepted by Owner after discussions before the award of Contract.

A Quality Assurance Program of the Contractor shall generally cover but not be limited to the

following:

a) The organization structure for the management and implementation of the proposed

Quality Assurance Program.

b) Documentation control system.

c) Qualification data for key personnel.

d) The procedure for purchase of materials, parts/components and selection of sub-

contractor's services including vendor analysis, source inspection, incoming raw material

inspection, verification of material purchases, etc.

e) System for shop manufacturing including process controls.

f) Control of non-conforming items and system for corrective action.

g) Control of calibration and testing of measuring and testing equipment.

h) Inspection and test procedure for manufacture.

i) System for indication and appraisal of inspection status.

j) System for quality audits.

k) System for authorizing release of manufactured product to utility.

262 | P a g e

l) System for maintenance of records.

m) System for handling, storage and delivery.

n) A Quality Plan detailing out the specific quality control procedure adopted for controlling

the quality characteristics of the product.

The Quality Plan shall be mutually discussed and approved by the Employer after incorporating

necessary corrections by the Contractor as may be required.

Neither the enforcement of QA/QC procedures nor the correction of work mandated by those

procedures shall be cause for an excusable delay. An effective Quality Assurance and Quality

Control organization shall be maintained by the Contractor for at least the duration of this Contract.

The personnel performing QA/QC functions shall have well-defined responsibility, authority, and

organizational freedom to identify and evaluate quality problems and to initiate, recommend, or

provide solutions during all phases of the Contract. The QA/QC organization of the Contractor

shall be an independent administrative and functional structure reporting via its manager to the

Contractor's top management. The QA/QC manager(s) shall have the authority within the

delegated areas of responsibility to resolve all matters pertaining to quality to the satisfaction of

Employer when actual quality deviates from that stated in the Work Statement.

The Contractor shall be required to submit all the Quality Assurance Documents as stipulated in

the Quality Plan at the time of Employer’s inspection of equipment/materials.

The Employer or his duly authorized representative reserves the right to carry out Quality Audit

and Quality Surveillance of the systems and procedures of the Contractor's/his vendor's Quality

Management and Control Activities.

The scope of the duties of the Employer, pursuant to the Contract, will include but not be limited

to the following:

a) Review of all the Contractor's drawings, engineering data etc.

b) Witness or authorize his representative to witness tests at the manufacturer's works or at

site, or at any place where work is performed under the Contract.

c) Inspect, accept or reject any equipment, material and work under the Contract in

accordance with the specifications.

d) Issue certificate of acceptance and/or progressive payment and final payment certificate

e) Review and suggest modification and improvement in completion schedules from time to

time; and

f) Monitor the Quality Assurance program implementation at all stages of the works.

263 | P a g e

10.4.2 Inspection

The Contractor shall give the Employer /Inspector two weeks in case of domestic supplies and six

weeks in case of foreign supplies written notice of any material being ready for testing. Such tests

shall be to the Contractor's account except for the expenses of the Inspector. The Employer

/Inspector, unless witnessing of the tests is waived, will attend such tests on the scheduled date for

which Employer /Inspector has been so notified or on a mutually agreed alternative date. If

Employer /Inspector fails to attend the testing on the mutually agreed date, Contractor may proceed

with the test which shall be deemed to have been made in the Inspector's presence and Contractor

shall forthwith forward to the Inspector, duly certified copies of the test results in triplicate.

The Employer /Inspector shall, within fourteen (14) days from the date of inspection as defined

herein, give notice in writing to the Contractor of any objection to any drawings and all or any

equipment and workmanship which in his opinion is not in accordance with the Contract. The

Contractor shall give due consideration to such objections and shall make the modifications that

may be necessary to meet said objections. When the factory tests have been completed at the

Contractor's or Sub-contractor's works, the Employer /Inspector shall issue a certificate to this

effect within fourteen (14) days after completion of tests but if the tests are not witnessed by the

Employer /Inspector, the certificate shall be issued within fourteen (14) days of receipt of the

Contractor's Test Certificate by the Employer /Inspector. The completion of these tests or the issue

of the certificates shall not bind the Employer to accept the equipment should it, on further tests

after erection, be found not to comply with the Contract.

In cases where the Contract provides for tests, whether at the premises or works of the Contractor

or of any Sub-contractor, the Contractor except where otherwise specified shall provide free of

charge items such as labour, materials, electricity, fuel, water stores, apparatus and instruments, as

may be reasonably demanded by the Employer /Inspector or his authorized representative to carry

out effectively such tests of the equipment in accordance with the Contract and shall provide

facilities to the Employer /Inspector or his authorized representative to accomplish testing.

The inspection by Employer and issue of Inspection Certificate thereon, shall in no way limit the

liabilities and responsibilities of the Contractor in respect of the agreed Quality Assurance Program

forming a part of the Contract.

The Contractor shall keep the Employer informed in advance of the time of starting of the progress

of manufacture of material in its various stages so that arrangements can be made for inspection.

Record of routine test reports shall be maintained by the Contractor at his works for periodic

inspection by the Employer’s representative.

Certificates of manufacturing tests shall be maintained by the Contractor and produced for

verification as and when desired by the Employer. No material shall be dispatched from its point

of manufacture until it has been satisfactorily inspected and tested. Testing shall always be carried

out while the inspection may be waived off by the Employer in writing only.

264 | P a g e

However, such inspection by the Employer’s representative(s) shall not relieve the Contractor from

the responsibility for furnishing material, software, and equipment to conform to the requirements

of the Contract; nor invalidate any claim which the Employer may make because of defective or

unsatisfactory material, software or equipment.

Access to the Contractor's facilities while manufacturing and testing are taking place, and to any

facility where hardware/software is being produced for Employer shall be available to Employer

representatives. The Contractor shall provide to Employer representatives sufficient facilities,

equipment, and documentation necessary to complete all inspections and to verify that the

equipment is being fabricated and maintained in accordance with the Specification. Inspection

rights shall apply to the Contractor's facilities and to subcontractor facilities where equipment is

being manufactured.

Inspections will be performed by Employer, which will include visual examination of hardware,

enclosure cable dressings, and equipment and cable labeling. Contractor documentation will also

be examined to verify that it adequately identifies and describes all wiring, hardware and spare

parts. Access to inspect the Contractor's hardware quality assurance standards, procedures, and

records that are applicable to the facilities shall be provided to Employer.

10.4.3 Inspection and Test

All materials furnished and all work performed under this Specification shall be inspected and

tested. Deliverables shall not be shipped until all required inspections and tests have been

completed, all deficiencies have been corrected to Employer’s satisfaction, and the equipment has

been approved for shipment by Employer.

Should any inspections or tests indicate that specific hardware, software or documentation does

not meet the Specification requirements, the appropriate items shall be replaced, upgraded, or

added by the Contractor as necessary to correct the noted deficiencies. After correction of a

deficiency, all necessary retests shall be performed to verify the effectiveness of the corrective

action.

The test shall be considered complete when (a) when all variances have been resolved (b) all the

test records have been submitted (c) Employer acknowledges in writing the successful completion

of the test.

10.4.3.1 Test Plans & Procedures

Test plans for both factory and field tests shall be provided by the Contractor to ensure that each

test is comprehensive and verifies all the features of the equipment are tested. The test plans for

factory and field tests shall be submitted for Employer approval before the start of testing.

The contractor shall prepare detail testing procedure in line to specification and submit for

Employer’s approval. The procedure shall be modular to the extent possible, which shall facilitate

the completion of the testing in the least possible time.

265 | P a g e

10.4.3.2 Test Records

The complete record of all factory and field acceptance tests results shall be maintained by the

Contractor. The records shall be maintained in a logical form and shall contain all the relevant

information. The test reports shall be signed by the testing engineer and the engineer witnessing

the tests.

10.4.3.3 Reporting of variances

A variance report shall be prepared by either Employer or Contractor personnel each time a

deviation from specification requirements is detected during inspection or testing. All such

variances shall be closed in mutually agreed manner.

However, at any stage if Employer feels that quality of variances calls for suspension of the testing

the testing shall be halted till satisfactory resolution of variances, which may involve retesting also.

10.4.3.4 Factory Test

The factory tests shall be conducted on all the equipment and shall include, but not be limited to

the following, appropriate to the equipment being tested:

(a) Verification of all functional characteristics and requirements specified

(b) Inspection and verification of all construction, wiring, labeling, documentation and

completeness of the hardware.

Before the start of factory testing, the Contractor shall verify that all changes applicable to the

equipment have been implemented. As a part of the factory tests, unstructured testing shall be

performed for SCADA/DMS/OMS system to allow Employer representatives to verify proper

operation of the equipment under conditions not specifically tested in the above structured

performance test. The Contractor's test representative shall be present and the Contractor's

technical staff members shall be available for consultation with Employer personnel during

unstructured test periods.

All special test facilities used during the structured performance test shall be made available for

Employer’s use during unstructured testing. Unless otherwise specified in the relevant sections of

the specification and except for SCADA/DMS/OMS Hardware, Software, RTUs, the sampling

size for FAT is 10% and in case any selected sample fails during the test, the failed samples shall

be rejected and 20% of the samples from the balance quantity shall be tested. If any failures are

observed, the entire lot shall be rejected.

10.4.3.5 Field Performance Test

After the equipment has been installed, the Contractor shall start-up and check the performance of

the equipment of field locations.

266 | P a g e

All hardware shall be aligned and adjusted, interfaces to all inputs and outputs installed, operation

verified, and all test readings recorded in accordance with the Contractor's recommended

procedures.

The field performance test shall exhibit generally all functions of the equipment and duplicate

factory test.

All variances shall be corrected prior to the start of the field performance test. The list of final tests

to be carried out in the field shall be listed in the site-testing document in line to the requirements

specified in the relevant sections of this volume.

10.5 Type Testing

The equipment being supplied shall conform to type tests as per technical specification and shall

be subjected to routine tests in accordance with requirements stipulated under respective sections.

The type test shall be conducted on the equipment if it is specifically mentioned in the relevant

section, for other equipment, the type test report shall be submitted.

Employer reserves the right to witness any or all the type tests. The Contractor shall intimate the

Employer the detailed program about the tests at least three (3) weeks in advance in case of

domestic supplies and six (6) weeks in advance in case of foreign supplies. The reports for all type

tests as per technical specification shall be furnished by the Contractor along with equipment /

material drawings.

The type tests conducted earlier should have either been conducted in accredited laboratory

(accredited based on ISO / IEC Guide 25 / 17025 or EN 45001 by KEBS or any other a national

accreditation body of the country where laboratory is located) or witnessed by the representative

(s) of KPLC. However, type test reports shall not be more than five years older than the date of

bid opening.

In the event of any discrepancy in the test reports, i.e. any test report not acceptable due to any

design / manufacturing changes or due to non-compliance with the requirement stipulated in the

Technical Specification or the type test(s) not carried out, same shall be carried out without any

additional cost implication to the Employer .

In case of failure during any type test, the Supplier at his own expenses shall modify the equipment

and repeat all type tests successfully at his own cost and within the project time schedule. Wherever

the make of the items is indicated in the technical specification, the type test reports are not

required to be submitted for the makes, indicated in the specification. For the new makes (other

than those indicated in the technical specification), type test reports as per relevant standard shall

be submitted for Employer’s approval.

10.6 Documentation

To ensure that the proposed systems conform to the specific provisions and general intent of the

Specification, the Contractor shall submit documentation describing the systems to Employer for

review and approval. Further, the contractor shall also submit the drawings/documents for all the

267 | P a g e

hardware & software required for site installation, testing and commissioning and thereafter

operation of the system.

The contractor shall obtain approval of Employer for the relevant document at each stage before

proceeding for manufacturing, system development, factory testing, site testing, training etc. The

schedule for submission/approval of each document shall be finalized during the discussions

before placement of the contract, this schedule shall be in line to overall project schedule.

Each document shall be identified by a Contractor document number, the Employer document

number and the Employer purchase order number. Where a document is revised for any reason,

each revision shall be indicated by a number, date, and description in a revision block along with

an indication of official approval by the Contractor's project manager. Each revision of a document

shall highlight all changes made since the previous revision.

The contractor shall submit two copies of each document/drawing for Employer’s review and

approval. After approval, five sets of all the documents shall be submitted as final documentation,

however, for site specific documents two sets of documents shall be provided for each site.

Any changes observed during field implementation shall be incorporated in the as-built drawing

and required sets of the same shall be submitted to Employer /owner. In addition to paper copies,

all the documents shall also be provided on electronic media in two copies.

In case any documentation requirement is specified in the relevant section the same shall apply for

the equipment /system defined in that section. The contractor shall also supply five sets of User

manuals/guides/O &M manuals/manufacturer’s catalogues for all the hardware & software

supplied under the contract which shall be in addition to the one set each at all the locations where

the System has been installed. The user manual shall at the minimum include the principle of

operation, block diagrams, troubleshooting and diagnostic and maintenance procedures.

Considering all the components of the project briefly the following documents/drawings shall be

required under the project.

(a) System Description Documents (Overview)

(b) Data Requirement sheets

(c) Software Requirements Specification

(d) Data base Documents

(e) Drawings/Documents for manufacturing/Assembly of the equipment/system

(f) Drawings/Documents for installation of the equipment/system at site

(g) Software description/design documents for each software module

(h) Testing Procedures and reports

(i) Manuals for each equipment/hardware/test equipment

(j) Bill of Quantities

(k) Site Testing documents

(l) Training documents

(m)System Administrator Documents

(n) User guide for Despatcher

268 | P a g e

However, all the above type of documents may not be required for each sub-system of the project

e.g. item (n) above may not be required for auxiliary power supply system, therefore, the contractor

shall submit a comprehensive list of the document as applicable for the offered system for

Employer’s approval immediately after signing of the contract and the documents shall be finalized

as per the approved list. In regard to Data requirement sheets (DRS) for these will be duly filled in

by the bidder & submitted along with the bid.

During detailed engineering, the Contractor will be required to submit detailed DRS to include all

technical parameters of the equipment to ensure that the offered equipment meets all the technical

specification requirements.

269 | P a g e

APPENDIX 11: TESTING & DOCUMENTATION

This section describes the specific requirements for testing and documentation of the

SCADA/DMS/OMS system. The general requirements of testing and documentation are covered

in appendix 11

11.1 Type testing

All equipment being supplied shall conform to type tests including additional type tests as per

technical specification and shall be subject to routine tests in accordance with requirements

stipulated under respective sections.

The reports for all type tests and additional type tests as per technical specification shall be

furnished by the bidder along with equipment / material drawings. The type tests conducted

earlier should have been conducted in accredited laboratory based on ISO / IEC Guide 25 /

17025 and the test reports submitted shall be of the tests conducted within last 5 (five) years

prior to the date of bid opening (unless specially agreed with the purchaser)".

In case, the submitted reports are not as per specification, the type tests shall be conducted

without any cost implication to employer.

11.2 Factory Acceptance Tests (FAT)

The SCADA/DMS/OMS system including DR servers shall be tested at the Contractor's facility.

All hardware and software associated with the SCADA/DMS/OMS system and at least two

RTUs along-with , ADMS and ten FRTUs and all Remote VDUs, shall be staged for the factory

testing and all remaining RTUs /FRTUs/FPIs shall be simulated for the complete point counts

(ultimate size). The requirements for exchanging data with other computer systems shall also be simulated. Each

of the factory tests described below (i.e. the hardware integration test, the functional performance

test, integrated system test and unstructured tests) shall be carried out under factory test for the

SCADA/DMS/OMS system. The factory tests, requiring site environment, shall be carried out

during the Field Tests after mutual agreement for the same from owner.

11.2.1 Hardware Integration Test The hardware integration test shall be performed to ensure that the offered computer hardware,

conforms to this Specification requirements and the Contractor-supplied hardware

documentation. All the SCADA/DMS/OMS system hardware shall be integrated and staged for testing.

Applicable hardware diagnostics shall be used to verify the hardware configuration of each

equipment. The complete hardware and software bill of quantity including software licenses and

deliverables on electronic media shall also be verified.

270 | P a g e

11.2.2 System Build test

After completion of hardware integration test, the SCADA/DMS/OMS system shall be built

from the backup software on electronic media (CDs/Magnetic Tapes) to check the completeness

of backup media for restoration of system in case of its crashing/failure. The software

deliverables shall include one copy of backup software on electronic media.

11.2.3 Functional Performance Test

The functional performance test shall verify all features of the SCADA/DMS/OMS hardware and

software. As a minimum, the following tests shall be included in the functional performance test:

(a) Testing of the proper functioning of all SCADA/DMS & other software application

software in line with the requirements of various sections of technical specification. (b) Simulation of field inputs (through RTU/FRTU/FPI) from test panels that allow sample

inputs to be varied over the entire input range (c) Simulation of field input error and failure conditions (d) Simulation of all type of sample control outputs (e) Verification of RTU /FRTU/FPI communication Protocol IEC-60870-5-104 /101 etc. (f) Verification of MFT communication Protocol MODBUS etc. (g) Verification of compliance of supporting interfaces such as IEC61850, IEC60870-5-103

etc. (h) Verification of CIM compliance (i) Verification of Security & Encryption using SSL for all FRTU/FPI connectivity. (j) Verification of Data Integration from SCADA/DMS/OMS system with other systems

namely IT Systems etc. over Open Standards over CIM/XML, IEC 61968 Series Standards, OPC, ICCP etc.,

(k) Verification of Integration between GIS / SCADA/DMS System over OAG, CIM/XML

or tight Native Integration, that enables updates within GIS to percolate over ESB / SOA

to IT Systems (l) Verification of data exchange with other systems. (m) Verification of interoperability profile of all profiles of all protocols being used. (n) Verification of RTU /FRTU/FPI communication interfaces (o) Verification of LAN and WAN interfaces with other computer systems (p) Testing of all user interface functions, including random tests to verify correct database

linkages (q) Simulation of hardware failures and input power failures to verify the reaction of the

system to processor and device failure (r) Demonstration of all features of the database, display, and report generation and all other

software maintenance features on both the primary and backup servers. Online database

editing shall also be tested on primary server. (s) Demonstration of the software utilities, libraries, and development tools. (t) Verification that the SCADA/DMS computer system meets or exceeds employer's

performance requirements (u) Verification of Design parameters as defined in the specification. (v) Verification that ultimate expansion requirements are met. (w) Verification that ultimate expansion requirements are met. (x) Verification of DTS

271 | P a g e

(y) Verification of Development system (z) Verification of data transfer of main to back up SCADA/DMS/OMS system. (aa) Functions of DR system. (bb) Unstructured testing of the SCADA/DMS system by employer. The unstructured

tests shall include the test, which are not in the approved test procedures and may be

required to verify the compliance to the specification. (Max 20% of total testing)

11.2.4 Continuous operation Test (48 hours)

This test shall verify the stability of the SCADA/DMS/OMS hardware and software after the

functional performance test has been successfully completed. During the test, all

SCADA/DMS/OMS functions shall run concurrently and all Contractor supplied equipment

shall operate for a continuous 48 (forty eight) hour period with simulated exchange with other interconnected system. The test procedure shall include periodic repetitions of the normal and peak loading scenarios

defined. These activities to be tested may include, but shall not be limited to, database, display,

and report modifications, configuration changes (including user-commanded processor and

device failover), switching off of a primary server and the execution of any function described in

this Specification. During the tests, un-commanded functional restarts or server/device failovers are not allowed; in

case the problems are observed, the Contractor shall rectify the problem and repeat the test.

11.3 Field Tests (Site Acceptance tests -SAT)

The SCADA/DMS/OMS system shall be tested at the site. All hardware and software associated

with the SCADA/DMS/OMS system along with all RTUs/FRTUs/FPIs along with all field

devices including MFTs connected shall be tested under the field tests.

11.3.1 Field Installation Tests The equipment which has undergone the factory testing shall be installed at site and integrated

with the RTUs /FRTU/FPI and other computer systems though the communication medium. The

field installation test shall include the following:

(a) Proper installation of all delivered hardware as per approved layout.

(b) Interconnection of all hardware

(c) Interconnection with communication equipment (d) Interconnection with power supply

(e) Diagnostic tests to verify the operation of all hardware

(f) Random checking of SCADA/DMS software basic functions

The Contractor shall be responsible for performing the field installation tests and Employer may

witness these tests

272 | P a g e

11.3.2 End-to-End Test After the field installation tests, the Contractor shall carry out end-to-end test to verify: (a) the communication of RTUs/FRTUS/FPIs/MFTs with SCADA/DMS system (b) the RTU /FRTU/FPI communication channel monitoring in the SCADA/DMS system (c) the mapping of SCADA database with RTU /FRTU/FPI database for all RTU /FRTU/FPI

points (d) the mapping of SCADA database with displays and reports. The Contractor shall provide the

details of all the variances observed and corrections carried out during end to end test.

11.3.3 Field Performance Test

The field performance test shall concentrate on areas of SCADA/DMS/OMS operations that

were simulated or only partially tested in the factory (e.g., system timing and loading while

communicating with a full complement of RTUs/FRTU/FPI and data links and system reaction

to actual field measurements and field conditions). Further, the validity of factory test results determined by calculation or extrapolation shall be

examined. After the end to end test, the Contractor shall conduct the field performance test to

verify the functional performance of the system in line with the technical specification which

includes the following:

(a) the communication of other system i.e. KPLC IT , DR system with SCADA/DMS system (b) Mapping of SCADA/ISR database with other system database viz KPLC IT, DR system. (c) Verify that all the variances observed during the Factory test are fixed and

implemented. (d) Conduction of the Factory tests deferred (tests requiring site environment) (e) Functional tests of SCADA/DMS/OMS system (f) Verify the execution rates of all SCADA/DMS/OMS application (g) Verify update rate & time for data update & control command execution as per

specification requirements (h) Verify the response time of all SCADA/DMS/OMS applications. (i) Verify the response time for User interface requirements (j) Testing of all features of the database, display, and report generation and all other

software maintenance features on both the primary and backup servers. Online database

editing shall also be tested on primary server. (k) Conduction of unstructured tests as decided by the Employer

11.4 System Availability Test (360 hours)

The Contractor shall provide and approve theoretical and practical figures used for this

calculation at the time of detailed engineering. The calculation shall entail reliability of each

individual unit of the System in terms of Mean Time Between Failures (MTBF and a Mean time

to Repair (MTTR) as stated by OEM. Reliability figures of existing equipment shall be supported by evidence from operational

experience at similar types of installation / figure given by OEM. From those data, the

unavailability of each sub-system shall be calculated taking in account each item redundancy.

273 | P a g e

The global availability shall then be calculated from those different unavailability data. This

calculation shall lead to the failure probability and equivalent global MTBF data for the control

center system. The overall assessment of System availability shall be provided in the form of an

overall System block diagram with each main item shown, complete with its reliability data. The

calculation of overall availability shall be provided with this diagram.

System availability tests shall be conducted after completion of the field tests. The system

availability test shall apply to the SCADA/DMS/OMS system (hardware and software)

integrated with its RTUs/FRTU/FPIs and KPLC’s IT system. However, the non-availability of

RTUs/Data Concentrators/ FRTU/FPI, KPLC’s IT system etc. and Communication System shall

not be considered for calculating system availability. However, RTU/FRTU, communication equipment, Auxiliary power supply shall be tested as

per the provisions given in their chapters. The SCADA/DMS/OMS system (hardware and

software systems) shall be available for 99.5% of the time during the 360hours (15 days) test

period. However, there shall not be any outage /downtime during last 85 Hours of the test duration. In

case the system availability falls short of 99.5%, the contractor shall be allowed to repeat the

system availability test after fixing the problem, failing which the system shall be upgraded by

the contractor to meet the availability criteria without any additional cost implication to the

owner. Availability tests of RTUs/FRTUs shall be conducted along with System availability test for 360hours. Each RTU/FRTUs shall exhibit minimum availability of 98%. In case the RTU/FRTU

availability falls short of 98%, the contractor shall be allowed to repeat the RTU/FRTU

availability test (for failed RTU/FRTU only) after fixing the problem, failing which the

equipment shall be upgraded by the contractor to meet the availability criteria without any

additional cost implication to the owner. In the event of unsuccessful reruns of the availability test, employer may invoke the default

provisions described in the General Conditions of Contract. The system availability tests will be

performed by the owner by using the SCADA/DMS/OMS system and RTUs/FRTU/FPI for

operation, control and monitoring of distribution system and using Contractor supplied

documentation. The owner will also be required to generate daily, weekly and monthly reports. The supplied

system shall be operated round the clock. The SCADA/DMS/OMS system shall be considered as available if:

(a) One of the redundant hardware is available so that all the SCADA/DMS/OMS

applications are functional to ensure the design & performance requirement as envisaged

in the specification (b) At least one of the operator console is available (c) At least one of the printers is available (off-lining of printers for change of ribbon,

cartridge, loading of paper, paper jam shall not be considered as downtime) (d) All SCADA applications are available

274 | P a g e

(e) All DMS applications are available (f) All SCADA/DMS/OMS functions described in the specification are executed at

periodicities specified in the specification. without degradation in the response times (g) Requests from available Operator Consoles & VPS are processed (h) Information Storage and Retrieval applications are available (i) Data exchange with the other systems is available

However each device, including servers, shall individually exhibit a minimum availability of

98%. The non-availability of following Non-Critical functions shall not be considered for

calculations of system availability; however these functions should be available for 98% of the

time.

a) Database modification and generation

b) Display modification and generation

c) Report modification and creation

d) DTS

During the availability test period, the Employer reserves the right to modify the databases,

displays, reports, and application software. Such modifications will be described to the Contractor at least 48hours in advance of implementation to allow their impact on the

availability test to be assessed, except where such changes are necessary to maintain control of

the power system. The successful completion of system availability test at site shall be considered as “operational

acceptance” of the system.

11.4.1 Downtime Downtime occurs whenever the criteria for successful operation are not satisfied. During the test

period, owner shall inform the Contractor for any failure observed. For attending the problem

the contractor shall be given a reasonable travel time of 8 hours. This service response time shall be treated as hold-time and the test duration shall be extended by such hold-time. The downtime shall be measured from the instant, the contractor

starts the investigation into the system and shall continue till the problem is fixed. In the event of multiple failures, the total elapsed time for repair of all problems (regardless of

the number of maintenance personnel available) shall be counted as downtime. Contractor shall

be allowed to use mandatory spares (on replenishment basis) during commissioning and availability test period. However it is the Contractor’s responsibility to maintain any additional

spares as may be required to maintain the required system availability individual device/

equipment availability. All outage time will first be counted but if it is proven to be caused by hardware or software not

of Contractor’s scope, it will then be deducted.

275 | P a g e

11.4.2 Hold-time During the availability test, certain contingencies may occur that are beyond the control of either

the Employer or the Contractor. These contingencies may prevent successful operation of the

system, but are not necessarily valid for the purpose of measuring SCADA/DMS/OMS

availability. Such periods of unsuccessful operation may be declared "hold-time" by mutual

agreement of the Employer and the Contractor. Specific instances of hold-time contingencies could be Scheduled shutdown of an equipment,

Power failure to the equipment or Communication link failure.

11.5 Documentation

The complete documentation of the systems shall be provided by the Contractor. Each revision of

a document shall highlight all changes made since the previous revision. The Employer's intent

is to ensure that the Contractor supplied documentation thoroughly and accurately describes the

system hardware and software. The contractor shall submit the paper copy of all necessary standard and customized documents

for SCADA/DMS/OMS in two sets for review/approval by the Employer for necessary

reference which includes the following:

a) System overview document b) Cross Reference Document c) Functional design document d) Standard design documents e) Design document for customization f) System Administration documents- software utilities, diagnostic programs etc. g) Software description documents h) Bill of Quantity & List of software and hardware deliverable i) Protocol implementation documents j) Point address document k) IP addressing plan document l) Software User document for dispatchers m) Software Maintenance document n) Training documents o) Real time & RDBMS documents p) Database settings, Displays and Reports to be implemented in the system q) Test procedures r) Test reports s) Hardware description documents t) Hardware User documents u) Hardware Maintenance documents v) Data Requirement Sheet (DRS) of all Hardware w) Site specific Layout, Installation, GA, BoQ, schematics and cabling details

drawings/documents x) SCADA & IT Integration Plan Document using CIM/XML Adapters & Messaging

Interfaces.

276 | P a g e

y) Cyber Security Plan & Mitigation document for the system if Public Networks are used. z) Interoperability profiles/ Tables

After approval two sets of all the above documents as final documents shall be delivered to site

by the Contractor. In case some modifications/corrections are carried out at site, the contractor shall again submit as

built site specific drawings in three sets after incorporating all such corrections as noticed during

commissioning. Any software modifications/updates made at site shall also be documented and

submitted in three sets to site and one set to Employer.

In addition to paper copies, two sets of final documentation shall be supplied on Electronic

media to employer. The contractor shall also submit two sets of the standard documentation of Operating system and

Databases in electronic media. Paper copies of these may be submitted, if the same are available from the OEM as a standard

part of delivery. One copy of the software packages used for accessing & editing the final

documentation in electronic media shall also be provided. After successful completion of System availability test, the contractor shall take the software

backup of complete SCADA/DMS/OMS system on electronic media and two copies of these

backup software shall be submitted to the owner.

277 | P a g e

APPENDIX 12: SPECIFICATION FOR THE 15.5KV CIRCUIT BREAKER FOR THE

RING MAIN UNIT EQUIPMENT

12.1. General

These specifications apply to factory built metal enclosed RMUs and derivatives utilising SF6 for

insulation only and being suitable for indoor and outdoor use. The equipment may be installed in

situations unprotected from the environment and may be subject to solar exposure.

The equipment to be supplied shall come in the form of an Extensible Ring

Main Units and derivatives and shall meet the following requirements:

easy to install

safe and easy to operate

compact

low maintenance

The supplier shall be capable of proving that he has a broad experience in the area of MV

switchgear and particularly Ring Main Unit equipment and shall provide proof that he has already

supplied equipment to the same type which has been in operation for at least 5 years in similar

operating circumstances.

12.2. Standards

In order to be accepted, the switchgear shall comply with the requirements stated in the latest

editions of the following recommendations, standards and specifications:

All units shall comply to IEC 62271 standards and those standards below only apply where 62271

is in draft or does not apply;

IEC 62271-100 Circuit breaker

IEC 62271-102 Ring earth switch

IEC 62271-103 Ring switch

IEC 62271-200 Enclosure

IEC 62271-206 VPIS

IEC60255 Relays

IEC62271-1 Common specification for switchgear

12.3. Rated voltage and short time withstand currents

The switchgear shall be appropriate for 15.5kV operation in a 3-phase system, at 50Hz

The rated voltage shall be at least 15.5 kV

The short time withstand current shall be 20kA 3s ( 21kA for 1s)

All of the switchgear shall be capable of withstanding the current without any damage

being caused in accordance with the recommendations of IEC 62271– 100/101 and 200.

278 | P a g e

12.4. Insulation level

The switchgear shall have an insulation level in accordance with the IEC recommendations and

the chart below:

Insulation level

50 (60) Hz 1 minute (kV rms) insulation

28/38 (38) kV

1.5/50 µs (kV peak) insulation

75/95 (95) kVp

12.5. Design Criteria

12.5.1 Introduction

The equipment shall meet the criteria for compact; metal enclosed outdoor switchgear in

accordance with IEC 62271-200.

The RMU shall typically include, within the same gas tank, a combination of two ring switches

and one tee-off circuit breaker enabling additional ring switches and circuit breakers to be added

to an existing installation at a later date via a busbar connection chamber.

12.5.2 Construction

The switchgear and busbars shall be contained in stainless steel enclosures, these enclosures for

circuit breaker or switching functions shall use SF6 as an insulating medium at pressure of no more

than 0.40 bar relative pressure to ensure the insulation and breaking and making functions. The

unit shall be sealed and meet the sealed pressure system criteria in accordance with IEC 62271.

It shall provide full insulation protecting the switchgear against the environment including

temporary flooding (to an agreed height), high humidity and high temperature in accordance with

the recommendations IEC 60529 14.2.7

The assembled switchgear and the active parts of the switchgear shall require minimum

maintenance.

The enclosures of the Ring Main Units shall be protected to IP54. The construction of the

switchgear tank shall be of stainless steel (3mm) minimum thickness to guarantee rust free

protection for an extended period. The outer protective steelwork shall be finished in such a way

as to maintain the unit in a fully protected condition.

The Ring Main Units and derivatives shall be suitable for mounting over a trench or base or for

direct transformer coupling. Each circuit shall be identified by appropriately sized labels, which

clearly indicate the function of the units and their electrical characteristics. The equipment shall

be designed so that the position of the different devices is visible to the operator at the front of the

units.

In accordance with the standards in effect, the equipment shall be designed so as to prevent access

to all live parts during the operation without the use of tools.

279 | P a g e

12.5.3 Earthing

There shall be continuity between the metallic parts of the switchgear and cables so that there is

no electric field pattern in the surrounding air, thereby ensuring the safety of people.

12.5.4 Operations

Ring switches, whether separately mounted or as part of a RMU shall incorporate a switch or

switches which enable the outgoing feeder to be: ON (connected to the busbars), OFF (isolated in

the tank) or EARTHED (connected to the earthing system of the switchgear) Circuit breakers,

whether separately mounted or part of a RMU and of the transformer feeder type shall incorporate

a manually operated earth switch between the busbar and the circuit breaker. This switch shall be

capable of being operated between the ON position (busbar connected to circuit breaker) and the

EARTH position (cable connected to earth via the circuit breaker). It shall not be possible to

operate this isolator switch unless the circuit breaker is in the OFF position. Earthing should be

achieved via the circuit breaker.

Clear indication should be given that the earth switch is in the closed position.

Mechanical interlocking system shall prevent access to the operating shaft.

All switches shall be of the independent manual type.

Each ring switch shall have the provision to be fitted with an electrical operating mechanism in an

especially reserved location.

The ring switches and the earthing switch operating mechanism shall have a mechanism endurance

of at least 5000 operations.

12.5.5 Transformer protection The circuit breakers shall be maintenance free, low pressure SF6 insulated type, using vacuum

interrupters for fault interruption. The use of SF6 circuit breakers is not permitted. The position of

the circuit breaker shall be clearly indicated as open, closed or earthed and shall be constructed in

such a way that interlocks prevent all unauthorised operations.

An operating mechanism should be used to manually close the circuit breaker and charge the

mechanism in a single movement.

It shall be fitted with a local system for manual tripping by integral button or lever. There will be

no automatic reclosing.

The circuit breaker shall be tripped under fault conditions by self-powered relays operated by dual

ratio toroidal current transformers incorporated on the transformer tee-off bushings, by local

manual trip button and by remote tripping signal (multi voltage).

The rated current of the circuit breaker shall be either 250 Amps or 630 Amps with a short circuit

breaking capacity of 20KA at 12kV.

12.5.6 Cable boxes

Cable boxes shall be suitable for terminating cable of up to 500 sq. mm.

Appropriate glands should be supplied.

Cables should be connected from the sides and rear. Cables connected from front are not

acceptable.

280 | P a g e

12.5.7 Padlocking and interlocking devices

The circuit breakers and earthing switches need to have the facility to be locked in the ‘open’ or

‘closed’ position by 1 to 3 padlocks, 6 to 8mm diameter.

Following interlocking shall be provided:

operation of load breaking switch cannot be performed when ‘ON’

when the earthing switch is in the ‘closed’ position

operation of the earthing switch cannot be performed when the load break ring switch is

in the ‘closed’ position

12.5.8 Operator Safety

In order to protect the operator at all times in switching functions, there will be no front connections

facing the operator. All connections are to be at the side and rear of the units at all times.

Any accidental over-pressure inside the sealed container is to be limited by the opening of a

pressure limiting device in the lower part of the enclosure.

Gas will be released to the rear of the switchgear. Evidence of internal arcing tests in accordance

with IEC 62271. All tests shall have been for a 1-second duration at 21kA.

12.5.9 Operating handles

A mechanism on the operation shall prevent any attempts to re-open immediately after closing of

the ring switch or earthing switch.

All manual operations to be carried out from the front of the switchgear using the same handle.

12.5.10 Front Plate

The front plate shall have an IP2XC degree of protection. The front shall include a mimic diagram,

which indicates the different functions.

The position indicators shall give a true reflection of the position of the contacts and shall be visible

to the operator. The operating direction of the handle shall be clearly indicated.

The manufacturer’s plate shall include the main electrical characteristics.

12.5.11 Cable insulation testing

The network cable insulation shall be tested phase by phase after the earthing switch is closed and

the fully interlocked earth bar is disconnected.

It shall not be necessary to gain access to the cable compartments to carryout cable testing.

12.5.12 Earth fault indicator

An automatic resetting type earth fault indicator with C/T’s shall be supplied where required. The

indicator will be mounted outside the housing to IP54 specification (minimum) so it is clearly

visible when the main door is closed.

12.5.13 Finishing

The device shall be fully designed for use in hot, humid temperature and shall require minimal

maintenance. All metallic parts shall have rust protection.

The colour shall be RAL 7033.

Lifting rings shall be installed on the top of the switchboards for handling.

281 | P a g e

12.6. Type and routine tests

According to the composition of the equipment, various type test certificates should be supplied:

impulse withstand test

dielectric strength at power frequency test

temperature rise test

short time withstand current test

mechanical operation test

degree of protection

ring switch and earthing switch making capacity

circuit breaker breaking capacity

In addition, the routine test carried out by the manufacturer shall be backed by test reports signed

by the factory’s Quality Control Department. They shall confirm the following:

conformity with drawings and diagrams

measurement of closing and opening speeds

measurement of operating torque

checking of filling pressure

checking of gas tightness

checking of partial discharge

dielectric testing

12.7. Quality

The supplier shall provide proof that he has quality procedure in accordance with ISO 9001

certification.

282 | P a g e

APPENDIX 13: SPECIFICATIONS ON VARIOUS TOOLS

13.1 SF6 DETECTION AND ELECTRICAL INSPECTIONS INFRARED CAMERA

The infrared camera shall rapidly scan large areas and pinpoint leaks and hotspots in real time.

This shall reduce repair downtime and provide verification of the process. Above all it shall be

exceptionally safe, allowing potentially dangerous leaks and hotspots to be monitored from

several meters away.

The infrared camera shall embed GPS data into the image allowing workers to pinpoint the

location of the leak or hot spot.

The infrared camera shall detect and visualize SF6 (Sulfur Hexafluoride) and other harmful

gases and hotspots quickly from a safe distance and without the need for a power outage.

The infrared camera shall be able to:

i) Visualize gas leaks in real time

ii) Be fully calibrated for temperature measurement applications

iii) Have an embedded GPS data in reporting

iv) Inspect without interruption of process

v) Considerably reduce inspection time

vi) Trace leaks to source

vii) Spot leaks and hotspots close by or meters away

viii) Make Reporting Easy

ix) Shall be dual-use systems to detect SF6 and temperatures - The thermo-graphic function

on the Optical Gas Imaging (OGI) camera shall help to determine the background

temperature/energy the gas is absorbing.

x) The gas imaging camera shall be a quick, non-contact measuring instrument that shall

also be used in hard-to-access locations. It shall detect small leaks from several meters

away and big leaks from hundreds of meters away

xi) It shall incorporate High Sensitivity Mode (HSM)

xii) Images from the infrared cameras shall be recordable to any off-the-shelf video recorder

for easy archiving and documentation.

283 | P a g e

Features Minimum specifications bidder’s offer

Model various

Detector Type Cooled QWIP

Spectral Response 10.3 – 10.7 μm

Resolution 320 × 240

Total Pixels 76,800

Thermal Sensitivity <15 mK @ +30°C (+86°F)

Accuracy

±1°C (±1.8°F) for temperature range 0°C

to +100°C (+32°F to +212°F) or ±2% of

reading for temperature range >+100°C

(>+212°F)

Temperature Range - 40°C to 500°C (-40°F to 932°F)

High Temp Option bidder to advise

Lens Options Standard 14.5° × 10.8°; Optional: 24°

Zoom 1 – 8× continuous digital

Focus Auto & Manual

Color LCD 4.3” ; 800 × 480 Pixels

Adjustable Viewfinder Tiltable OLED, 800 × 480 pixels

Video Camera w/Lamp 3.2 MP

Laser Spot Yes

Video Out HDMI

Spot-meters 10

Area Boxes 5 (min./max./avg.)

Profiles 1 live line (horiz. or vert.)

Delta T Yes

GPS Yes

284 | P a g e

13.2 Optical Gas Imaging Training

The supplier shall conduct training on the optical gas imaging camera.

(a) Students shall learn how to set up and operate optical gas imaging cameras.

(b) They shall learn how to optimally adjust their cameras for varying environmental

conditions to find gas leaks.

(c) Students shall learn under what environmental conditions gas leaks are most easily found,

somewhat easy to find and difficult to find.

(d) This class shall teach students which gases can be found with optical gas imaging cameras

and leak size limitations. Some basic infrared theory and heat transfer concepts shall be

introduced to build a strong foundation.

(e) Lab and/or field practice in finding leaks shall be a key part of this class. Students shall

learn by doing and by observing numerous videos of leaks and what to look for including

thermal contrast, gas plume motion, distance limitations etc. Basic inspection procedures

shall be covered including equipment checkout, route planning, permitting requirements,

safety practices/equipment and reporting concepts.

(f) Upon successful completion of the course, students shall receive a training certification for

optical gas imaging camera usage

Course Objectives

i. Explain the regulatory framework for optical gas imaging

ii. Describe the OGI certification process

iii. Demonstrate proper operation of infrared camera

iv. Create a movie indicating a gas leak using FLIR Video Report software

v. Explain the basics of thermal science

vi. Explain how optical gas imaging is a combination of art, science, technique and

interpretive skills

vii. List the basic safety practices for doing an OGI inspection

The Training shall be geared to the new infrared camera user and shall focus on how

thermography is used for a variety of condition monitoring / predictive maintenance

applications.

After the training, the students shall have the following benefits:

They shall have a comprehensive, hands-on introduction to thermal imaging and

measurement systems for predictive maintenance applications.

They shall have a knowledge on how to collect quality data, accurate temperature

readings, and account for measurement effects such as distance and emissivity

using infrared cameras.

They shall be able to interpret thermo-grams and make informed decisions using

heat transfer concepts to analyze thermal images, and see the latest in infrared

inspection report generation and database software.

285 | P a g e

They shall be able to avoid costly mistakes - learn to distinguish between hot

spots and reflections, direct vs. indirect readings and qualitative vs. quantitative

thermography.

They shall be able to challenge themselves with field applications labs that closely

simulate real-world infrared applications.

13.3 SF6 gas refilling device

The refilling device shall be portable in a case with rubber hose and couplings with

diameter nominal 8 and 20 (DN8 and DN20)

The device shall be handy to allow filling of electrical equipment with SF6 gas directly

from the bottle by overpressure. The primary gauge of the pressure reducer shall display

the bottle pressure in bar.

The secondary gauge shall indicate the desired filling pressure to be set easily by means of

the handle.

It shall be possible to reduce the bottle pressure to the desired filling pressure by the

integrated pressure reducer.

Self-closing couplings for emission-free gas handling shall be made available as

accessories for the most commonly used bottle connections.

13.4 Non-conductive Folding Multipurpose ladders specifications

a. The ladders shall be made of fibre glass and electrically insulated for safety around

electrical installations.

b. They shall be sturdy Glass-reinforced plastic (GRP) stiles and square alloy rungs.

c. They shall be 4-ladder sections hinged together with heavy-duty plated hinges

d. They shall be of brilliant versatility i.e. one ladder can be used as:

i. Straight Leaning Ladder

ii. Free-Standing Stepladder

iii. Platform Ladder (with decking added by user)

iv. Compact closed ladder for storage and transport.

e. They shall be German standard (GS) or equivalent and TUV approved to EN131

for Trade use – with a maximum safe load of 150kg

f. They shall be fitted with at least a 780mm wide alloy stabilizer bar at both ends for

improved stability and extra safety.

Closed & Platform

Height

Stepladder

Height

Extended Ladder

Height

No. of

Rungs

0.99m / 3' 3" 1.75m / 5' 9" 3.54m / 11' 7" 4x3

286 | P a g e

13.5 True RMS Power Analyzer Datalogger

The equipment shall have the following minimum specifications:

4 LCD Displays (Watts, Power Factor/VA, Voltage/Hz, Amps)

True RMS Voltage and Current Measurements of Sine, Square, Triangular and Distorted

Wave Forms with a Crest Factor <5

Datalogger shall store a minimum of 1,012 readings with single record storage or

continuous datalogging capability

It shall have Battery and AC Adapter Power Supply Options

It shall be able to export Data through Software

The supply shall include Built-in Carrying Case, 230 VAC Adaptor, Power Cord and

adaptor, a Software and a USB cable

3-Phase Power Analyzer Specifications

Watt

Range: 200/2000W

Accuracy: ±0.9% +4d @ 50Hz

Resolution: 0.1/1W

Input Signal Range: 300V, 20A,40-400Hz

Power Factor

Range: 0.5 to 1.0

Accuracy: Based on W, V, A

Resolution: 0.001

Input Signal Range: 250V, 20A,50Hz

Voltage

Range: 200.0/750V

Accuracy:±0.5%

Resolution: 0.1/1V

Input Signal Range: 750VAC

Current

Range: 2/220A via Terminals, 2/15A via Sockets

Input Signal Range: Fuse Protection

Accuracy: ±0.5%

Frequency

Range: 40Hz to 20kHz

Accuracy: ±0.5%

Resolution: 1Hz to 10Hz

Operating Conditions Temperature: 32°F to 122°F (0°C to 40°C)

Humidity: Less than 80%

Display 200 Count LCD Displays

Memory Size 1012 x4 Readings (Non-Volatile)

Memory Life 100,000 Memory Writes

Over Range Indication ‘OL' or otherwise Displayed on LCD

Sampling Rate 2.5 Samples per Second

287 | P a g e

13.6 Specifications for Earth Ground Tester

Display: 1999 digit LCD Display with special symbols, digit height 25 mm, fluorescent

backlight

User interface

Instant measurement through TURN and START one button

concept. The only operating elements are rotary switch and START

button

Robust, water and dust

resistant

Instrument is designed for tough environmental conditions (rubber

protective cover, IP56)

Memory Internal memory storage up to 1500 records accessible via USB port

Temperature Range

Operating temperature -10 °C to 50 °C (14 °F to 122 °F)

Storage temperature -30 °C to 60 °C (-22 °F to 140 °F)

Temperature coefficient ± 0.1 % of reading/°C <18 °C >28 °C

Intrinsic error Refers to the reference temperature range and is guaranteed for 1

year

Operating error Refers to the operating temperature range and is guaranteed for 1

year

Climatic class C1 (IEC 654-1), -5 °C to +45 °C (23° to +115° F), 5 % to 95 % RH

Protective type IP56 for case, IP40 for battery door according to EN60529

Safety Protection by double and/or reinforced insulation. max. 50 V to

earth. IEC61010-1: 300V CAT II, Pollution degree 2

EMC (emission

immunity) IEC61326-1: Portable

Quality system Developed, designed and manufactured according to DIN ISO 9001

External voltage V ext, max = 24 V (dc, ac < 400 Hz), measurement inhibited for

higher values

V ext rejection > 120 dB (162⁄3, 50, 60, 400 Hz)

Measuring time Typical 6 seconds

Max. overload 250 V rms (pertains to misuse)

Auxiliary power 6 x 1.5 V Alkaline (type AA LR6)

Battery life span Typical > 3,000 measurements

288 | P a g e

Dimensions (WxHxD) 250 mm x 133 mm x 187 mm (9.75 in x 5.25 in x 7.35 in)

Weight

1.1 kg (2.43 lb) including batteries

7.6 kg (16.8 lb) incl. accessories and batteries in carrying case

RA 3-Pole Ground Resistance Measurement (IEC 1557-5)

Switch position RA 3-pole

Resolution 0.001 Ω to 10 Ω

Measuring range 0.020 Ω to 19.99 kΩ

Accuracy ± (2 % rdg + 3 d)

Operating error ± (5 % rdg + 3 d)

Measuring Principle: Current/Voltage Measurement

Measuring voltage Vm = 48 V ac

Short-circuit current > 50 mA

Measure frequency 128 Hz

Probe resistance (RS) Max 100 kΩ

Auxiliary earth electrode

resistance (RH) Max 100 kΩ

Additional error from RH

and RS RH[kΩ]RS[kΩ]/RA[Ω]0.2 %

Monitoring of RS and RH with error indicator.

Automatic range selection.

Measurement is not performed if the current through the current clamp is too low.

RA 4-Pole Ground Resistance Measurement (IEC 1557-5)

Switch position RA 4-pole

Resolution 0.001 Ω to 10 Ω

Measuring range 0.020 Ω to 19.99 kΩ

Accuracy ± (2 % rdg + 3 d)

Operating error ± (5 % rdg + 3 d)

Measuring Principle: Current/Voltage Measurement

Measuring voltage Vm = 48 V ac

Short-circuit current > 50 mA

Measure frequency 128 Hz

Probe resistance (RS +

RES) Max 100 kΩ

Auxiliary earth electrode

resistance (RH) Max 100 kΩ

289 | P a g e

Additional error from RH

and RS RH[kΩ]RS[kΩ]/RA[Ω]0.2 %

Monitoring of RS and RH with error indicator.

Automatic range selection.

RA 3-Pole Selective Ground Resistance Measurement with Current Clamp (RA with Clamp )

Switch position RA 3-pole with clamp

Resolution 0.001 Ω to 10 Ω

Measuring range 0.020 Ω to 19.99 kΩ

Accuracy ± (7 % rdg + 3 d)

Operating error ± (10 % rdg + 5 d)

Measuring Principle: Current/Voltage Measurement (with External Current Clamp)

Measuring voltage Vm = 48 V ac

Short-circuit current > 50 mA

Measure frequency 128 Hz

Probe resistance (RS) Max 100 kΩ

Auxiliary earth electrode

resistance (RH) Max 100 kΩ

Monitoring of RS and RH with error indicator.

Automatic range selection.

Measurement is not performed if the current through the current clamp is too low.

RA 4-Pole Selective Ground Resistance Measurement with Current Clamp (RA with Clamp )

Switch position RA 4-pole with clamp

Resolution 0.001 Ω to 10 Ω

Measuring range 0.020 Ω to 19.99 kΩ

Accuracy ± (7 % rdg + 3 d)

Operating error ± (10 % rdg + 5 d)

Measuring Principle: Current/Voltage Measurement (with External Current Clamp)

Measuring voltage Vm = 48 V ac

Short-circuit current > 50 mA

Measure frequency 128 Hz

Probe resistance (RS) Max 100 kΩ

Auxiliary earth electrode

resistance (RH) Max 100 kΩ

Monitoring of RS and RH with error indicator.

Automatic range selection.

Measurement is not performed if the current through the current clamp is too low.

Stakeless Ground Loop Measurement (2 Clamps )

Switch position RA 4-pole 2 clamps

290 | P a g e

Resolution 0.001 Ω to 10 Ω

Measuring range 0.020 Ω to 19.99 kΩ

Accuracy ± (7 % rdg + 3 d)

Operating error ± (10 % rdg + 5 d)

Measuring Principle: Stakeless Measurement of Resistance in Closed Loops Using Two Current

Transformers

Measuring voltage Vm = 48 V ac

Measure frequency 128 Hz

Noise current (IEXT) Max. IEXT = 10 A (ac) (RA < 20 Ω)

Max. IEXT = 2 A (ac) (RA > 20 Ω)

Automatic range selection.

291 | P a g e

APPENDIX 14: REFURBISHMENT OF RING MAIN UNITS ROOMS

ITEM DESCRIPTION UNIT QTY RATE AMOUNT

Element No. 1-Painting

Prepare surfaces; apply two coats

First grade Silk vinyl emulsion

paint, cream ; on painted plaster

surfaces to:

A Walls SM 45

Ceiling

Prepare surfaces; apply two coats

First grade emulsion paint,

brilliant white ; on

B Painted ceiling surfaces SM 24

Doors and Windows

Prepare surfaces; apply two coats

First grade super-gloss paint, red ;

on

C Painted metal surfaces SM 15

Element No. 2 - Cable Trench cover

D Supply and install 6mm chequer

plate; primed and painted to approval SM 2

Element No.3 - Provisional Sum

E Allow Provisional Sum for keeping

rooms aerated and dust free and for

refurbishment of electrical facilities ITEM ITEM 10,000.00

D SUBTOTAL

E ADD 16% VAT

F TOTAL CONTRACT SUM

292 | P a g e

APPENDIX 15: MOBILE WORKFORCE MANAGEMENT TECHNICAL

SPECIFICATION

1.0 Introduction

1.1 Service Suite The Service Suite shall help KPLC to provide efficient and reliable services to customers by

supporting the effective management of service calls. The Service Suite system shall consist of a

Central server, a number of workstations, mobile devices and associated peripherals. The system

shall interface to the host and the wireless network.

This is illustrated in the following diagram.

This document specifies the hardware, software, and interface requirements for the following:

Service Suite server.

Street Level Routing server.

Workstations.

Mobile devices.

Mobile data network.

Local Area Network (LAN).

Interfaces with the host.

Auxiliary devices.

293 | P a g e

1.2 Operating System Support Level For each operating system supported for use with Service Suite, the bidder shall maintain support

up to the latest patch release. With each release of Service Suite, the bidder shall specify the

minimum supported O/S patch level but will support subsequent patches.

1.3 Oracle support level

For Oracle Enterprise server and client, the bidder shall provide full support up to the latest

security patch level. For all other Oracle patches, the bidder shall provide support on a case-by-

case basis and will evaluate support for upcoming releases.

2.0 Server

The server shall interface with the host and the following applications:

Mobile Application (MA)

Service Suite Mobile

Dispatch Application (DA)

System Administration (SA)

Workforce Availability (WA)

Compose

System Monitor

Forecasting

Operations Notice Board

The MA shall be connected over a wireless communications network, but need not be.

The server shall consist of the Service Suite application software and one or more database

servers. Physical resources shall be replicated if there is a requirement to maintain system

availability after the failure of a hardware component. The server may either be manually

installed or deployed as an appliance virtual machine provided by the bidder.

However, the following features shall be available in Service Suite Appliance environments:

The Capacity Administrator

The Operations Notice Board

The DA’s Order View summary window

Service Suite Mobile’s Self Dispatch feature

The scheduling algorithm’s Street Level Mapping feature

The following table summarizes the hardware and software requirements for the Service Suite

server environment.

For the primary server components, the bidder shall have the option of either manually installing

a Service Suite Server environment or of deploying a Service Suite Appliance virtual machine.

A detailed description of these requirements is provided in Section 2.1, Hardware and Software

for the Service Suite Server and Section 2.2, Hardware and Software for the Service Suite

Appliance, respectively.

294 | P a g e

Feature

Server Requirements

Service Suite Server (Manual Install)

Basic Functionality

Computer with UNIX operating system

Oracle Oracle Tuxedo

Perl Oracle WebLogic Server

TCP/IP network

IBM Power Series Platform Specific Requirements

JDK BOS fileset

X86 architecture Platform Specific Requirements

JDK

High Availability IBM HACMP Red Hat Cluster Suite

Authentication Authentication directory software

External Directory Server

Connection to Microsoft Active Directory

Version Control Software

Subversion

System Monitor Personal computer, Web browser

Customer Support

Remote access

Service Suite Appliance

Basic Functionality

VMWare VSphere

Oracle TCP/IP network

NTP Server

Web browser

Customer Support

Remote access

Street Level Routing

Street Level Routing

Microsoft Windows operating system

Computer system

Microsoft .NET Framework

Streets data

Note: The requirements for the Street Level Routing (SLR) server shall be described in Section

2.3, Hardware and Software for the Street Level Routing Server.

295 | P a g e

2.1 Hardware and Software for the Service Suite Server

The standard Service Suite server platforms are:

a) x86 architecture running Red Hat Enterprise Linux 7.2+.

b) the Linux server shall be a VMWare virtual machine. The virtualized environment shall

be certified for use with RedHat Enterprise Linux 7.2.

The Service Suite system shall be required to have:

i) Oracle 12c Release 1 (12.1.0.2) Enterprise Edition (installed, configured, and with patch

levels). - Each Service Suite system shall require dedicated database instances for the

Operational Database (ODB) and Historical Database (HDB).

ii) Oracle 12c Release 1 (12.1.0.2) 64-bit Client Software for the selected server platform.

iii) Oracle Tuxedo 12cR2 (12.1.3),

iv) Perl 5.10 with the Oracle DBI and DBD modules compiled

v) Version 12c (12.1.3) of the Oracle WebLogic Server Enterprise Edition with required

patches.

vi) If the server platform is Red Hat Enterprise Linux:

a) Oracle Java SE Development Kit 7 64-bit (update 80).

vii) If hardware high availability is deployed:

On Red Hat Enterprise Linux platforms, the Red Hat Cluster Suite application or the

Veritas Cluster Server.

If an external directory server is being used for authentication, one of the following

connections shall be required:

Connection to Microsoft Windows Server 2008 R2 Active Directory, using port 636

only. The external directory server shall be configured so that Service Suite is able to

search its repository of users for authentication purposes.

Subversion software at the time that Service Suite is installed.

A UTF8 character set.

viii) The physical network used to interconnect the Service Suite server and the

workstations shall be required to support the TCP/IP protocol and 100Mbps or better

connectivity.

If deploying Service Suite Mobile, on the firewall, port 443 shall be opened for all

messages from *servicebus.Windows.net. This is to enable push notifications to your

Mobile devices through a 3rd party push notification service.

Workstations on which System Monitor reports are to be displayed require:

A personal computer with Microsoft Internet Explorer 11.0 or higher.

To fulfill contractual commitments for customer support, the bidder personnel shall

require remote access to Service Suite. The remote access requirements are determined

on a case-by-case basis.

296 | P a g e

2.1.1 Service Suite Server Sizing Service Suite server sizing shall be carried out by the bidder. Information on users, order

volumes, and options is as below:

Parameter Size

Maximum number of concurrent dispatchers 15

Maximum number of concurrent technicians 210

Maximum number of orders completed per day 2,500

Maximum number of orders stored in ODB 25,000

It is expected that a production system shall be implemented using separate hardware servers for

the Service Suite server software, the ODB database and the HDB database. The sizing specified

below assume that the average size of an order is 4KB and that the HDB is required to retain a

record of the operational activities for one year.

Sizing for the System on Red Hat Enterprise Linux (RHEL)

Parameter Service Suite Server ODB Server HDB Server

Number of x86 64-bit CPU cores 8 6 2

CPU speed 3.0 GHz 3.0 GHz 3.0 GHz

Memory 24 GB 20 GB 6 GB

Disk 60 GB 100 GB 500 GB

2.2 Hardware and Software for the Service Suite Appliance

The Service Suite Appliance shall be deployed using the VMWare VSphere 5.5 update 3

(or later) virtualization platform.

The computer hosting the VMWare vSphere virtualization platform shall meet the

following minimum hardware requirements:

3 GHz or higher Intel multi-core 64-bit processor

The Service Suite Appliance shall require access to database instances managed using

Oracle 12c Release 1 (12.1.0.2) Enterprise Edition (installed, configured and with patch

levels).

The physical network to be used to interconnect the Service Suite Appliance and the

workstations shall be required to support the TCP/IP protocol and 100Base-T or better

connectivity.

o To deploy Service Suite Mobile, on the firewall, port 443 shall be opened for all

messages from *servicebus.Windows.net. This is to enable push notifications to

Mobile devices through a 3rd party push notification service.

The Service Suite Appliance shall require access to a Network Time Protocol (NTP)

server to ensure that work remains time-synchronized.

If an external directory server is being used for authentication, one of the following

connections shall be required:

o Connection to Microsoft Windows Server 2008 R2 Active Directory, using port

636 only.

297 | P a g e

Connection to Microsoft Windows Server 2012 R2 Active Directory, using port 636 only.

The external directory server shall be configured so that Service Suite is able to search its

repository of users for authentication purposes.

In order to access the Service Suite Management Console interface used to configure the

Service Suite Appliance, users shall require a copy of one of the following Web

browsers:

Google Chrome

Mozilla Firefox

In order to access the System Monitor Hyperic HQ Web interface used to monitor

Service Suite activity and performance, users shall require any Web browser supported

by Hyperic HQ 5.0.

In order to access the Operations Notice Board, users shall require Microsoft Internet

Explorer 10.0 or higher.

In order to access the Capacity Administrator, users shall require Microsoft Internet

Explorer 10.0 or higher.

Domain Name Server (DNS) for the network environment in which the Service Suite

Appliance is hosted.

To fulfill contractual commitments for customer support, the bidder’s personnel shall

require remote access to Service Suite. The remote access requirements shall be

determined on a case-by-case basis.

2.2.1 Service Suite Appliance VM Sizing The Service Suite Appliance shall support the required size as given below:

Parameter Size

Maximum number of concurrent dispatchers 15

Maximum number of concurrent technicians 210

Maximum number of orders completed per day 2,500

Maximum number of orders stored in ODB 25,000

The following table summarizes the minimum resource requirements for hosting each of the

components required by a single instance of Service Suite in a VMWare Server environment.

Component # CPU Cores Memory (GB) Storage (GB)

Service Suite Appliance 8 24* 2 x 40 GB + 25 GB swap partition

System Monitor VM 2 4* 20

* The memory requirements determined for this environment shall be permanently allocated to

the virtual machine as reserved resources.

High Availability Consideration VMWare vSphere shall provide solutions to ensure high levels of availability:

VMware vMotion and Storage vMotion shall provide capabilities to move virtual machines to

different physical servers and storage without service interruption.

VMWare HA, VMWare Distributed Resource Scheduler and Fault Tolerance features shall

reduce unplanned downtime by providing rapid recovery and continuous availability

298 | P a g e

The following shall be the minimum configuration:

a) A VMWare cluster with two hosts shall be used for Service Suite.

b) vSphere HA shall be turned on with host monitoring enabled.

A common storage accessible by either host shall be used as a datastore for Service Suite.

2.3 Hardware and Software for the Street Level Routing (SLR) Server SLR shall be used to sequence a mobile user’s orders within his shift. SLR shall use its

knowledge of the underlying street network on which the mobile user shall drive to determine an

optimal route.

a) The SLR server shall require one of the following operating systems:

Microsoft Windows Server 2012 R2.

The minimum hardware configuration for the SLR server is a computer system

with:

o Your SLR server can be a physical computer or a VMWare virtual

machine. All hardware specifications in this document are equally

applicable to both scenarios.

o A 3 GHz or higher Intel x86 quad-core processor.

o 8 GB RAM.

o A LAN interface card.

o A minimum of 30 GB available space on the hard drive for application

and scratch.

b) The SLR server shall require:

Microsoft .NET Framework 3.5 SP1.

A Network Dataset.

An Address.

Streets data that conforms to the following specifications shall be installed on the

SLR server:

o The data shall provide geographic coverage of the territory in which routes

are to be generated.

o The data shall be in one of the following formats:

Smart Data Compression (SDC) 2 (2012) format.

FileGDB dataset.

3.0: Workstation

Workstations shall be used to run the DA, SA, WA and Compose applications.

The DA is a dispatching tool used to view order summaries and order details, dispatch orders,

monitor the fleet, and communicate with supervisors, technicians, and crews.

The SA is used to create and manage system level information such as user profiles.

The WA is used to create and manage mobile user schedules.

The Compose application is a configuration tool used to change the features of the summary

windows and forms in the DA and MA and the content of host uplink messages.

299 | P a g e

The following table summarizes the workstation requirements. A detailed description of these

requirements is provided in Section 3.1, Hardware and Software for the Workstation and Section

3.2, Dispatch Mapping.

Feature

Workstation Requirements

Basic Functionality Microsoft Windows operating system

Microsoft .NET Framework

Mouse and keyboard

LAN card

DA, SA, and WA Personal Computer Oracle client software with ODP.NET client

DA Order Details Printing Local or network printer

Compose Personal Computer Oracle client software with ODP.NET client

Dispatch Mapping Additional space on the hard drive

Personal Computer Streets data

3.1 Hardware and Software for the Workstation

a) The DA, SA, WA, and Compose applications require one of the following

operating systems:

Microsoft Windows 10 build 10586 (TH2 November Update) or later

Microsoft Windows 8.1 Update 1 (32 or 64 bit).

Microsoft Windows 7 (with or without Service Pack 1) (32 or 64 bit)

Enterprise Edition, Professional Edition, or Ultimate Edition.

b) The minimum configuration for workstations running the DA, SA, WA, or

Compose application is as follows:

Your workstations can be physical computers or VMWare virtual machines.

All hardware specifications in this document are equally applicable to both

scenarios.

Workstations running the DA, SA, or WA require the following minimum

hardware specifications:

o 2.0 GHz or higher Intel x86 dual-core processor

o 2.5 GB RAM

o 1 GB hard drive space

Workstations running Compose require the following minimum hardware

specifications:

o 2.0 GHz or higher Intel x86 dual-core processor

o 3GB RAM

o 3 GB hard drive space

o Workstations running the Compose application shall be equipped with

monitors whose resolution is equal to or better than the resolutions of

the workstations and mobile devices for which forms are being

configured.

A Microsoft compatible mouse and keyboard.

300 | P a g e

For DA order details printing, a local or network printer with the appropriate

printer drivers.

A LAN interface card with 100Base-T or better.

Microsoft .NET Framework 4.5 or higher.

The installers shall download and install the correct version of Microsoft

.NET Framework if it is not already installed and if the workstation has an

Internet connection.

Oracle 12c (12.1.0.2) Instant Client Software (32-bit only).

c) Workstations using the Data Loader to import Service Suite data require

Microsoft Excel 2010.

d) Other applications, including the Notebook Edition of the MA, are permitted to

run on the workstation in parallel with the Service Suite workstation applications.

3.2 Dispatch Mapping i) Workstations running Dispatch Mapping require:

Additional space on the hard drive for storage of the streets data. Storage

requirements are determined by the geographic area covered by the data and the level

of detail contained in the data.

A Network Dataset.

If there is need to use local data for the DA’s Address Search feature, an Address

Locator shall be required.

3.2.1 Streets Data Dispatch Mapping shall require streets data to serve as a backdrop. The data format and

content shall be equivalent to TeleAtlas data.

DA dispatch mapping shall support the following formats for map data:

ArcGIS Online Maps, including their World Street Map, World Imagery, and

World Topographic Maps. Other online maps shall be evaluated on a case-by-case

basis.

Shapefile format.

Smart Data Compression (SDC) 2 format.

FileGDB dataset.

4: Mobile Device

Mobile devices shall run the MA and Service Suite Mobile, which shall be used by technicians,

supervisors, and crews to access Service Suite.

The following table summarizes the requirements for mobile devices. A detailed description of

these requirements is provided in Section 4.1–Hardware and Software for the Notebook Edition

of the MA and Section 4.2–Hardware and Software for Service Suite Mobile.

301 | P a g e

Feature Device Requirements

Notebook Edition of MA Microsoft Windows operating system

Personal Computer Microsoft .NET Framework

Mobile Printing on Notebook Edition Using Network Printer

Configured network printer

Mobile Printing on Notebook Edition Using Local Printer

Configured local printer

Separate port

GPS with NMEA device NMEA0183 compliant device

Separate port

GPS with Trimble Trimble GPS device Separate port

Barcode Scanning for Notebook Edition

Scanner Decoder Keyboard wedge software

Wireless Connectivity for Notebook Edition

Wireless modem

Radio Network Radio Network

Mixed Fleet Mixed Fleet

Notebook Edition Using Mobile Mapping

Personal Computer with RAM

Additional space on the hard drive [830.6.3]

Streets data

Service Suite Mobile Apple iOS 10.x Google Android 5.x Windows 10 build10586

4.1 Hardware and software for the Notebook Edition of the MA The Notebook Edition of the MA is intended for use on devices such as laptops, pen-based tablet

computers, and desktop computers, running the Microsoft Windows operating system.

The Notebook Edition of the MA shall be most suitable for users who require the complete set of

mobile user capabilities; for whom the size and cost of Microsoft Windows devices are

appropriate; who require connectivities only supported by the Notebook Edition; and who need

to use other software that runs in the Microsoft Windows environment.

The Notebook Edition of the MA shall require one of the following operating systems:

Microsoft Windows 10 build 10586 or later

Microsoft Windows 8.1 Update 1 (32 or 64 bit).

The 32-bit or 64-bit version of Microsoft Windows 7 (with or without Service Pack 1)

Enterprise Edition, Professional Edition, or Ultimate Edition.

The minimum configuration for mobile devices using the Notebook Edition of the MA is as

follows:

Mobile devices running the Notebook Edition of the MA can be physical computers or

VMWare virtual machines. All hardware specifications in this document are equally

applicable to both scenarios.

Mobile devices running the Notebook Edition of the MA require the following minimum

hardware specifications:

o 2 GHz or higher Intel x86 dual-core processor

o 2 GB RAM

302 | P a g e

o 1 GB hard drive space

Microsoft .NET Framework 4.5 or higher with hotfix rollups 3064711 and 3064715.

The installer shall download and install the correct version of Microsoft .NET

Framework if it is not already installed and if the mobile device has an Internet

connection.

Peripheral ports and/or device adapters to support wireless modems, printers, and GPS

devices. A separate port is required for each device.

If mobile printing is deployed, a printer with appropriate printer drivers.

If the GPS feature is deployed, one of the following GPS devices:

o A National Marine Electronics Association (NMEA) 0183 Version 2.3 or earlier

compliant device, configured to output GGA messages.

o A Trimble device supporting the Trimble ASCII Interface Protocol (TAIP),

configured to output PV messages.

o A wireless modem that supports the NMEA message or TAIP message in the

payload of a UDP/IP packet. The device vendor shall provide a transparent access

of the wireless network through the wireless modem via supplied NDIS driver.

If barcode scanning is used to enter data:

o A barcode scanner or other RFID device (provided the device is capable of

transferring data via keyboard wedge software) connected to the mobile device.

o A decoder that is compatible with the scanner.

The decoder is typically built into the device.

o Keyboard wedge software that is compatible with the decoder.

If wireless connectivity is required, a wirelesss modem.

If using the Mobile Companion application:

o The Mobile Companion can be installed on any Apple iPhone device meeting the

following requirements:

running Apple iOS 10.x

1GB RAM

o On the device running the MA Notebook, Apple Bonjour 2.0.2 or higher

(optional)

A radio network that supports UDP/IP and allows bidirectional UDP traffic on specific

UDP ports in the 1024-65535 range.

If the attachments feature is deployed, a radio network that supports TCP/IP.

More than one radio network can be configured. However, each individual mobile device

is limited to a single radio network, and that network shall be selected when the mobile

device is configured.

Support for other connectivities (both IP-based and otherwise) and for roaming (that is,

the use of more than one wireless network on a single mobile device) may require

additional hardware and software.

The power save settings on devices using the Notebook Edition of the MA shall be set so

that the hard disk(s) are never turned off while the MA is running.

Mixed fleets of different Notebook devices shall be supported.

303 | P a g e

4.1.1 Mobile Mapping In addition to the requirements, mobile devices running Mobile Mapping require:

3 GB RAM. This replaces requirement in Section 4.1, Hardware and Software for the

Notebook Edition of the MA.

Additional space on the hard drive for storage of the streets and additional layer data.

Storage requirements are determined by the geographic area covered by the data and the

level of detail contained in the data.

A Network Dataset.

an Address Locator

The requirements for the streets and additional layer data are specified below.

4.1.1.1 Streets and GIS Data

Mobile Mapping shall require streets data to serve as a backdrop. The data format and

content shall be equivalent to TeleAtlas data.

Mobile mapping supports the following formats for map data:

o Shapefile format.

o Smart Data Compression (SDC) 2 format.

o FileGDB dataset.

o Additional GIS layers in shapefile format shall be added to the map.

4.2 Hardware and Software for Service Suite Mobile Service Suite Mobile is intended for use on tablet devices running the Android, iOS, or Windows

operating systems. Appearance and navigation within Service Suite Mobile are different from the

MA Notebook.

However, the core mobile user capabilities are supported, including full order progression, host

forms, supervisor functions, and mobile user conditions. The requirements in this section apply

to both the Mobile and Supervisor apps.

Service Suite Mobile is most suitable for users for whom the core mobile user capabilities

provided by Service Suite Mobile are sufficient; who require a small and light tablet device,

which can be easily carried; and who need to use other software that runs in the Android, iOS, or

Windows environment.

Service Suite Mobile requires the following operating systems:

Apple iOS 10.x

Google Android 5.x

Windows 10 build 10586 or later

The minimum configuration for Android tablet devices using Service Suite Mobile is as

follows:

Hardware specifications comparable to a Samsung Galaxy Tab A 8.0

5Megapixel primary camera (if using barcode scanning)

The minimum configuration for Android phones using Service Suite Mobile is as

follows:

304 | P a g e

Hardware specifications comparable to a Samsung Galaxy Grand Prime

5 megapixel primary camera (if using barcode scanning)

The minimum configuration for iOS tablet devices using Service Suite Mobile is

as follows:

1GB RAM

5Megapixel primary camera (if using barcode scanning)

The minimum configuration for Windows tablet devices using Service Suite

Mobile is as follows:

2GHz i3 CPU

2GB RAM

GPS capability

5Megapixel primary camera (if using barcode scanning)

Service Suite Mobile shall support the baseline Google, Windows, or Apple iOS

Keyboards

Service Suite Mobile’s barcode scanning feature shall support the following barcode

standards on each mobile device operating system:

Android iOS Windows

AZTEC X

CODABAR X X

CODE_128 X X X

CODE_39 X X X

CODE_93 X X

DATA_MATRIX X X X

EAN_8 X X X

EAN_13 X X X

ITF X X X

MSI X

PDF417 X X

QR_CODE X X X

RSS14 X X

RSS_EXPANDED X

UPC_A X X X

UPC_E X X X

305 | P a g e

Mobile Application Capabilities

FieldWorker Classic

FieldWorker Tablet

FieldWorker Phone

MAPPING

Display street maps √ √ √

Includes MapQuest street maps - √ √

View assets on map √ - -

View maps while offline/disconnected √ √ √

View future orders on map √ - -

Request ad-hoc routes √ - -

Re-sequence a route √ - -

View driving directions to an order √ √ √

Hear audible driving directions - √ √

View SLR route manifest √ - -

View current location on a map √ √ √

DEVICE

Seamlessly move in and out of coverage √ √ √

Offline/disconnected mode √ - -

Localization and regionalization √ √ √

Orders pushed to the device √ √ √

Order notifications (e.g. rescheduled, removed, modified)

√ √ √

Audible alerts √ √ √

Pick list updates in the background √ √ √

SECURITY AND NETWORKING

Extended fields on login and log off forms √ √ √

Remote force logoff √ √ √

Change password from device 6 √ √ √

Preserve local data on device power off √ √ √

Compressed network activity √ - -

Encrypted network activity √ √ √

Encrypted local storage √ √ √

MOBILE USER

Mobile user details √ - -

Inform dispatch of availability √ √ √

Indicate emergency situation √ √ √

Out of coverage automatically detected and indicated on Dispatch Application

√ - -

Override crew composition √ - -

View and update current equipment √ - -

306 | P a g e

Field Worker Classic

Field Worker Tablet

Field Worker Phone

COMMUNICATIONS

Maintain personal contacts in Mobile Application address book

√ - -

Text message a device, user, supervisor, or dispatch

√ - -

Text message templates √ - -

Exchange messages with host systems √ √ √

ORDER ACTIVITIES

Mobile userself-dispatch - √ -

Host validation √ - -

Signature capture √ - -

Barcode reader √ √ √

Report estimated time to completion √ √ √

Print forms √ - -

Initiate call ahead messages √ - -

WORKER SAFETY

Lone worker protection √ - -

Track worker location √ √ √

Share location with dispatch on order status change

√ √ √

ORDER WORKFLOW

Order in jeopardy √ - -

Suspend √ √ √

Reject (refer) √ √ √

Acknowledge √ √ √

En-route, on-site, complete √ √ √

Indicate on Dispatch Application orders received by device

√ √ √

ORDER SUMMARY

View dispatched orders √ √ √

Manually re-sequence orders √ - -

View future orders √ - -

Indicate emergency orders √ √ √

Indicate complex orders √ - -

External interface √ - -

ORDER DETAILS

View pictures, maps, and other attachments √ √ √

Attach files, pictures, and other attachments to update form

√ √ √

List of attachments √ √ √

307 | P a g e

Field Worker Classic

Field Worker Tablet

Field Worker Phone

Hyperlinks in order details √ √ √

Configurable validation rules √ √ √

Repeating groups √ √ √

Orders with multiple activities √ √ -

View work history √ - -

View dependencies on complex orders √ - -

Emergency orders √ √ √

Capture geo-location on a form √ √ √

SUPERVISOR

View fleet status √ √ √

View fleet members’ orders √ √ √

TIMESHEET

Submit timesheet √ - -

Request, modify, and approve timesheets √ - -

Note: all the field worker shall be supplied with rugged covers. The field worker tablets shall also be supplied with accessories to fix them to the cars.

Mobile Device Management shall be included to bring central operations and enhanced IT security

for field mobile devices. This is in case they are stolen or misused.

308 | P a g e

APPENDIX 16: FURNITURE SPECIFICATIONS

16.1 Control room chairs

The chairs shall be Ergonomic, high Back All Fabric Task Chair with the following features:

Comfort Headrest

Height Adjustable Armrests

5-Way Syncro-Control

Large Cloth Seat

Heavy Duty Pneumatic Shock

Heavy Duty 5-Star Base

Dual Wheel Casters

Compliance with ANSI/BIFMA

16.2 Warranty

Lifetime Warranty on Frame

5-Year Warranty on All Structural Components

3-Year Warranty on Covers and Foam

The chairs shall:

have Roll Back Adjustable Height Arm

be black in colour

Be manufactured as 24 hour chairs engineered to withstand the demanding environments

of control and dispatch centers.

Feature the latest ergonomic designs and commercial grade components.

16.3 Control room desk

The control room desk shall have the following:

The desk shall:

Have a basic platform with expandable possibilities

Have an adjustable light and always centered above workplace

Be able to hold monitor holders for best alignment of monitors as described earlier in

detail.

have a number of shelves to keep computers off the floor and reduce cabling problems

with height adjustment

have a motorized base frame design to allow height adjustment of the whole desk or work

and monitor board separately

have protective back panels in noise reducing material

Shall be 1960mm long and 1060mm wide as shown in figure below

Be ergonomic compliant with ISO 11064 & EEMUA 201 with a motorized frame

309 | P a g e

Fig: details of the control room desk

16.4 Dual Monitor Stand

Product Type Mounting kit - desk-mountable

Recommended Use 2 LCD displays

Recommended Display Size 30"

Flat Panel Mount Interface Yes

General Color Black, silver

AV Furniture Type Mounting kit

Placing / Mounting Desk-mountable

Flat Panel Mount Interface Yes

Adjustments Pan, tilt

Manufacturer Warranty 5 years

16.5 Quad-Monitor Desk Stand

Product Type Stand

Tilt Yes

Recommended Use Quad flat panel

Recommended Display Size Up to 30"

Material Aluminum, steel

Color Black, silver

Manufacturer Warranty 5 years warranty

General Material Aluminum, steel

Color Black, silver

AV Furniture Type Stand

Flat Panel Mount Interface 100 x 100 mm, 75mm x 75 mm

Cable Management Cable Management System (CMS)

Features Rotating, portrait to landscape movement

Manufacturer Warranty 5 years