kenya electricity modernization project … volume 2- part 2 employer%27s... · 10.3.3 factory...

THE KENYA POWER AND LIGHTING COMPANY LIMITED

KENYA ELECTRICITY MODERNIZATION PROJECT BIDDING DOCUMENT FOR

PROCUREMENT OF DESIGN, SUPPLY, AND INSTALLATION OF ADVANCED METERING INFRASTRUCTURE (AMI) SYSTEMS TO SUPPORT REVENUE RECOVERY AND PROTECTION PROGRAMS

ICB No. KPI/6A.1/PT/13/16/A58

6th January, 2017

Volume 2 Technical Specifications and Drawings

Part 1 Instructions to Bidders and Conditions of Contract

Volume I Instructions to Bidders and Conditions of Contract

1 of 157

Employer’s Requirements for Advanced Metering

Infrastructure (AMI) systems to support revenue

recovery and protection programs

.................................................................................................................

2 of 157

1 Index 1 Index ............................................................................................................................... 2 1 GENERAL SYSTEM REQUIREMENTS ..................................................................... 5

1.1 CONCEPT .......................................................................................................... 5 1.2 SYSTEM STRUCTURE .................................................................................... 5

1.2.1 AMI .................................................................................................................... 5 1.2.2 METER DATA MANAGEMENT SYSTEM .................................................... 6

1.3 SYSTEM ARCHITECTURE ............................................................................. 6 2 FUNCTIONAL REQUIREMENTS AND CAPACITIES OF COMMUNICATION

NETWORK COMPONENTS ............................................................................................... 7 2.1 TECHNICAL REQUIREMENTS AND MAIN FUNCTIONALITIES OF THE

COMMUNICATION NETWORK FOR A RESIDENTIAL CUSTOMERS ................... 7 2.1.1 SCOPE OF THE SUPPLIES .............................................................................. 7 2.1.2 SYSTEM PERFORMANCE (DATA COMMUNICATION) ........................... 8 2.1.3 SYSTEM PERFORMANCE WARRANTY (DATA COMMUNICATION) ... 8 2.1.4 GENERAL REQUIREMENTS FOR COMMUNICATION MODULES ........ 9 2.1.5 ADDITIONAL REQUIREMENTS OF COMMUNICATION MODULE ....... 9 2.1.6 IMPLEMENTATION SPECIFICATION .......................................................... 9 2.1.7 MAINTENANCE AND OPERATION TASKS .............................................. 10

3 MANAGEMENT READING SYSTEM (MRS) ......................................................... 10 3.1 OBJECTIVE ..................................................................................................... 10 3.2 DESCRIPTION ................................................................................................ 10 3.3 SPECIFICATION OF THE MRS ENVIRONMENT ...................................... 10

3.3.1 TECHNICAL CHARACTERISTICS .............................................................. 10 3.3.2 ARCHITECTURE AND SYSTEM REQUIREMENTS ................................. 11 3.3.3 SCOPE OF THE SUPPLY ............................................................................... 11

3.4 MANAGEMENT READING SYSTEM ......................................................... 13 3.4.1 GENERAL FEATURES OF THE MRS .......................................................... 13 3.4.2 Generation of Reports / Charts ......................................................................... 17 3.4.3 MRS ADMINISTRATION FUNCTION ......................................................... 17 3.4.4 MRS REPORTING CAPABILITIES .............................................................. 18

3.4.4.1 Analysis of statuses and alarms .............................................................. 18 3.4.4.2 Reports on electricity quality .................................................................. 18 3.4.4.3 Communication reports ........................................................................... 18

3.5 USER AND OPERATOR INTERFACE ......................................................... 18 3.6 DATA MANAGEMENT ................................................................................. 18

3.6.1 DATA GROUPING ......................................................................................... 19 3.6.2 DATA AND INFORMATION EXCHANGE FUNCTIONS WITH MDM

SYSTEM AND OTHER INFORMATION SYSTEM OF ELECTRIC UTILITY ...... 19 3.6.3 DATA ENTRY INTO MRS SYSTEM ............................................................ 19 3.6.4 DATA SUBMITTED TO BILLING SYSTEM ............................................... 19 3.6.5 DATA SUBMITTED TO MDM SYSTEM ..................................................... 19 3.6.6 VOLTAGE VARIATIONS .............................................................................. 19

4 METERING CONTROL CENTER FUNCTIONALITY AND CAPABILITY. ........ 20 4.1 DESCRIPTION AND GENERAL REQUIREMENTS FOR METERING

CONTROL CENTER ...................................................................................................... 20 4.2 METERING CONTROL CENTER (MCC) FUNCTIONS ............................. 20

4.2.1 SYSTEM COMPONENTS ADMINISTRATION .......................................... 20 4.2.2 DATA COLLECTION/READING AND MONITORING. ............................ 21 4.2.3 MONITORING THE DATA TRANSFER PROCESS .................................... 21 4.2.4 REPORT GENERATION AND DATA ANALYSIS ..................................... 22

5 SPECIFICATIONS FOR SMART SINGLE PHASE STATIC METERS FOR

ACTIVE ENERGY ............................................................................................................. 23 5.1 SCOPE .............................................................................................................. 23

3 of 157

5.2 NORMATIVE REFERENCES ........................................................................ 23 5.3 TERMS AND DEFINITIONS ......................................................................... 24 5.4 REQUIREMENTS ........................................................................................... 24 5.5 DESIGN AND CONSTRUCTION REQUIREMENTS .................................. 25

5.3.8 Real time clock and memory ............................................................................ 28 5.3.9 Load control and management ......................................................................... 29 5.3.11 Energy measurements .................................................................................. 30 5.3.12 Demand measurements ................................................................................ 30 5.3.13 Instrumentation data measurements ............................................................ 31 5.3.14 Load profiling .............................................................................................. 31 5.3.15 Power Quality Analysis ............................................................................... 31 5.3.16 Security features .......................................................................................... 31

5.8 Samples ............................................................................................................ 34 6 SPECIFICATIONS FOR SMART METERSTHREE PHASE WHOLE CURRENT

STATIC METERS FOR ACTIVE ENERGY .................................................................... 39 8 ADDITIONAL FUNCTIONS ...................................................................................... 63

8.1 COMMUNICATION WITH THE METER .................................................... 63 8.2 PROFILES OF METERED AND REGISTERED VALUES .......................... 63 8.3 Load Profile ...................................................................................................... 64 8.4 Event Log ......................................................................................................... 64 8.5 LIMITING OF PERMITTED MAXIMUM POWER ..................................... 64 8.6 REMOTE DISCONNECTION/CONNECTION OF THE CUSTOMER

(ELECTRICITY SUPPLY INTERRUPTION) ............................................................... 64 8.7 SWITCHING MODULE (BISTABILE SWITCH) ......................................... 65 8.8 Conditional Switch Reclosing Operation Regime ............................................ 65 8.9 Automatic Switch Reclosing Operation Regime .............................................. 65 8.10 TIME OF USE (TOU) ...................................................................................... 65 8.11 FIXED TIME OF USE (TOU) ......................................................................... 65 8.12 ELECTRICITY METERING QUALITY ........................................................ 65

8.12.1 SUPPLY INTERRUPTION REGISTRATION .......................................... 65 8.13 DATA SECURITY .......................................................................................... 66 8.14 SELF-CHECK .................................................................................................. 66

8.4.4 Data storage, management and maintenance ................................................... 71 8.4.5 Scalability in terms of full integration with other Information Systems .......... 71 8.4.6 Revision of changed data ................................................................................. 71 KPLC is responsible for the supply of the LAN network ............................................ 88

9.2 DOCUMENTATION ................................................................................................ 92 9.3 TRAINING ................................................................................................................ 92 9.4 SHIPMENT, INSTALLATION AND COMMISSIONING .................................... 93 10 ADDITIONAL INFORMATION & GENERAL SCOPE OF WORKS .................. 95

10.1 General ............................................................................................................. 95 10.1.1 Overview of the Kenya Power and Lighting Metering infrastructure ......... 96

10.1.1.1 Status of Advanced Metering Infrastructure (AMI) ............................... 96 10.1.1.2 Technical characteristics of existing AMI system .................................. 96

10.2 The Project Scope of works .............................................................................. 97 10.2.1 Installations Works ...................................................................................... 98

10.3 Training and FAT (factory acceptance tests) ................................................... 99 10.3.1 MDMS and Equipment Training (in the country of manufacture) (RPP 408)

99 10.3.2 Local Training (RPP 409) ............................................................................ 99 10.3.3 Factory Acceptance Test (RPP 401) ............................................................ 99

10.4 Site Acceptance testing .................................................................................. 100 10.5 Test Equipment to be supplied (TS –101,102) ............................................... 100 10.6 Final documentation ....................................................................................... 100

4 of 157

10.7 Site Offices (RPP 410) ................................................................................... 100 10.8 List of Goods .................................................................................................. 106 10.9 List of Related services .................................................................................. 106 ANNEX 1: TECHNICAL GAURANTEE SCHEDULE FOR SINGLE PHASE SMART

METERS .......................................................................................................................... 98 ANNEX 2: TECHNICAL GAURANTEE SCHEDULE FOR THREE PHASE SMART

METERS .................................................................................................................. 116114

ANNEX 3: TECHNICAL GAURANTEE SCHEDULE FOR METER DATA

CONCENTRATORS ……………………………………………………………… .127

ANNEX 4: DISTRIBUTION OF CUSTOMERS ....................................................... 1345

ANNEX 5: SCHEDULE OF SYSTEM REQUIREMENTS ……………………………139

ANNEX 5: SCHEDULE OF SYSTEM REQUIREMENTS …………………136 to

------------------------------------------------

Kenya Power and Lighting Company VI 4Revenue Protection Project (RPP)

Kenya Electricity Modernization Project Scope or Works

5 of 157

1 GENERAL SYSTEM REQUIREMENTS

1.1 CONCEPT

Advanced systems for metering and management of electricity consumption, reading of electricity

meters, data processing and storage include the advanced metering infrastructure (AMI) and meter

data management system (MDMS). Hereinafter, the set of all three components together is

referred to as ‘the System’.

AMI is the set of infrastructure under which data stored in meters identified by exact date and time

are periodically collected remotely and transferred to the computer located inside the Metering

Control Center (MCC), where the centralized MDM system is installed.

MDMS provides joint infrastructure for data reception of metered consumption from the

implemented AMI system within one electric utility, it potentially calculates consumed electricity

(i.e. provides data necessary to the system for calculation and collection of electricity), preserves

and manages data and also provides access to data to all interested parties.

Fig 1: System Architecture

1.2 SYSTEM STRUCTURE

General description of the main components of the System follows.

1.2.1 AMI

The AMI consists of the following components:

a) Multifunctional electronic meters



6 of 157

b) Communication network components (CNC)

c) Management Reading System (MRS) (one or more Data Acquisition Software (DAS))

d) Metering Control Center (MCC)

Functional requirements for each of those components are presented in detail in the following sections:

Functional Requirements of Meters, Functional Requirements and capacities of Communication

Network Components, Functional Requirements of MRS and Functional Requirements of Metering

Control Center.

1.2.2 Meter Data Management System

The MDM system shall provide, but not limited to:

Receipt and upload of data on metered consumption and other electric parameters and alarms taken

by the AMI System;

Receipt and upload of data sent by the CIF (Customer Information File) System, primarily related

to commercial activities like historical consumption data, service order, etc.

Receipt and upload of data sent by the other internal utility system, primarily related to voltage

drops and deviations, indication of supply outages and various warnings;

Validation, editing and assessment of data on metered consumption;

Data storage, management and maintenance;

Analysis of energy balance as well as generation of corresponding reports

Other necessary reporting functions;

Expandability in terms of full implementation of advanced metering;

Revision of all altered data, modifications and configurations;

Data traceability within the entire MDM system;

Security in access management of all functions and data;

Calculation of consumed electricity for each delivery point based on different price structures,

including hourly and other specified period of tariff rates;

Data based on previously defined schedule or on request;

Customers Data Access across Web interface;

Manage Meter events

Support Work Management System field order generation

Filter, group outage and restoration events for OMS

Support GIS integration.

1.2.3 SYSTEM ARCHITECTURE

The System shall operate in Centralized architecture model. There shall be only One Main MCC that will

be doing AMI and MDM administration and the others in specified regions shall only be for monitoring

and analyzing the data.



7 of 157

2 FUNCTIONAL REQUIREMENTS AND CAPACITIES OF

COMMUNICATION NETWORK COMPONENTS

The Communication Components must guarantee the reliable and fast bidirectional data transfer between

AMI components. Technical solution for data transfer shall be such as to have a capacity sufficient for AMI

components to perform all the set tasks within specified times. Also, shall provide a corresponding code

protection of transferring data (e.g. Protection against unauthorized reading, unauthorized command

generation, ill-intentioned submission of false data, etc.).

2.1 TECHNICAL REQUIREMENTS AND MAIN FUNCTIONALITIES OF THE

COMMUNICATION NETWORK FOR A RESIDENTIAL CUSTOMERS

There are three models of network that shall be deployed: Network based on RF technology, Network

based on PLC technology and Network based on a mixed RF-PLC technology. The following section will

describe the general requirements to be met by any of them.

GPRS communication shall be limited to data concentrators and the central station.

2.1.1 Scope of the Supplies

The Supplier shall be responsible for providing the communication services between the

meter and the MCC.

The installation and configuration of the routers or any other communication equipment

shall be the sole responsibility of the SUPPLIER;

All the equipment to be installed at the customer premises shall be located inside a Meter

Box. In case an existing Meter Box needs to be changed, the Supplier is responsible for all

cost of the box change.

All equipment that will be installed across the communication path (from meter to MCC),

such as routers, modems and interface converters shall be installed by the supplier in a

secure way and it is responsible for all cost associated with this installation.



8 of 157

All equipment that will be installed in the Utility Computer Center must be mountable

inside of customer Racks. If the customer does not have space available the supplier must

supply a RACK of the same characteristic of those that Purchaser already have.

The Communication Infrastructure must be scalable. The designed features of the

communication infrastructure shall take into consideration future expansion of the remote

meter points. The MRS shall ensure the scalability to incorporate all utility low

consumption customers. The Supplier must indicate the additional costs for a utility full

deployment of the solution.

Adaptation to network topology changes has to be supported. Electric power and

communication network are not static, whereby the protocol or the system have to provide

the routing function adapted to network changes.

Communication route with the meter shall be registered and must be able to be requested

at any moment from MRS.

Communication function with meters needs to support a fully automated repetition

procedure and finding of the optimal communication path.

Communication function has to offer information online quality such as signal/noise ratio,

attenuation and data loss statistics for all its components in SI Units. Also trace routes for

RF.

2.1.2 System Performance (Data Communication)

The system must be in the capacity to provide a minimum of the following characteristics:

Reading success of metered (registered) value in given time frames:

The System must be capable of providing daily alarms, active and reactive energy (kWh

and kVARh), peak active power (kW) and voltage for the utility’s total installed AMI

meters in the project with a minimum of a 99% daily success rate for schedule reads and

‘on demand’ reads’ within a normal interval between 12 am. and 8 am. Schedule reads

contain register and interval data and all meter events.

AMI meter data shall be loaded into the MDM on daily basis, the % of successful reads

will be determined by the number of ‘full data meter read packets’ that are available for

loading into the MDM.

The system shall support up to 4 channels of interval data for singlephase meters and 8

channels for polyphase meters.

2.1.3 System Performance Warranty (Data Communication)

In complete production and operation, the System must guarantee the following efficiencies:

99% success rate for all ‘full’ meter reading packets (interval and register data, and meter

events)

The system availability must be at least 99.5%



9 of 157

4 hours maximum recover time if a catastrophic failure is corrected

The Supplier is responsible for all the investments for these requirements.

2.1.4 General requirements for Communication Modules

Communication module must support dynamic addressing of modem and/or APNs service.

Communication module should have a built-in protection against unwanted access. Access

from which communication is allowed; which is entered as a parameter in the

communication module.

The external communication module shall have the same electrical characteristic as the

meter.

The external communication module should not depend logically of the factory number of

the meter, i.e. Replacement of old and installation of new modem is reduced to simple

physical replacement, while software at the Meter Control Centre (MCC) executes the

logical replacement.

The communication module has to be equipped with a function to maintain the

communication channel active even if the equipment has not been used for a longer time

(this time represents a parameter).

All communication parameters located in the modem at the time of modem reset must

remain saved.

The communication module shall send encrypted data of no less than 128 AES.

The communication module shall support secure firmware upgrades over the air.

2.1.5 Additional requirements of Communication Module

The Meter shall be able to communicate with a remote central system (AMI Head End) using a

plug in modem/module, through the PLC, RF Mesh, RF point to point, or 3G networks.

2.1.6 Implementation Specification

All meter installation will include a Point of Service inspection acceptable to KPCL.

All meter must be sealed successfully.

All Meter Boxes must be installed successfully and sealed

All meter must be installed successfully and sealed.

Any change of the Meter Box due to equipment size must be approved by the Project

Manager.

Adaptation to electric network topology changes have to be supported for the

communication network.

All installations shall be checked for theft and proper measurement in accordance with

KPLC instructions.



10 of 157

2.1.7 Maintenance and Operation Tasks

The Supplier shall specify all maintenance tasks of the infrastructure and the costs associated.

Must include the annually schedule of maintenance with the associated costs and the quantities

estimated of unscheduled maintenance with the associated costs.

The Supplier shall specify all annually operation cost of the infrastructure. Supplier must include

a budget of the fixed costs, like rent of communication lines, and the costs of data transmission if

they are variables.

3 MANAGEMENT READING SYSTEM (MRS)

3.1 OBJECTIVE

The main goal of this specification is to present the requirements to be accomplished by the software (one

or more) responsible for the Data Acquisition and administration of the communication network, as well

as the additional services necessary for its deployment and technical support.

The MRS must be placed in a Server computer and be available to the MCC.

3.2 DESCRIPTION

The MRS is a software management platform that allows the MCC to perform remote

measurement operations, upload of files, analyze, process and exchange data with the Information

Systems to read meters and reduce commercial losses. The MRS must be a shelf - ready and fully

operational product (1 or more), not including any development service, exception made for the

integration with other Information Systems of the Utility, for the adaptations to the their IT

environments or for the new features later required by the Utility.

MRS must be an application independent from the MDM supplied, interfacing between them with

an open architecture (SOA-service-oriented architecture and Common Information Model)

allowing the future AMI infrastructure expansion (other MRS, if required, uploading the MDM)

and for interfacing with KPLC systems.

3.3 SPECIFICATION OF THE MRS ENVIRONMENT

3.3.1 Technical Characteristics

The utility IT Department must understand the operating system. In other case, the supplier must

include an operating system training course.

All the hardware environment of the central subsystem shall be compatible with the current

platform of the Utility;

The system shall operate using an ORACLE database. The Supplier shall furnish all the Manuals

for the operation, administration and maintenance of all the applications involved in the solution

during their initial supply and at every new update of the systems that will imply in modification

thereof. It shall be included in this documentation at least the following technical documents in the

system: Installation and Implementation Manual, User manual, Reference Manual, the Software

Design and a DER - Diagram of Entities and Relationships;

The complete system documentation shall be delivered in ENGLISH.



11 of 157

3.3.2 Architecture and System Requirements

The system must have at least the following layers bounded by independent programs: application

server, communication server and database server; all with its corresponding redundancy.

The GUI interface shall be integrated in such a manner that the same data entry can be used in all

operations of the system, in order to avoid duplication of work;

The messages and screens of the system shall be exhibited in the national language of the country;

during the phase of acceptance test they may be exhibited in English or Spanish, but the final

delivery must be in the national language of the country;

The MRS must have the resources of auditing trail and recording of transactions that were made:

who made, when and where they were made;

Capacity of increase of the hardware components as required for the improvement of performance

(horizontal scalability);

Ability to migrate to a hardware platform for better performance (vertical scalability);

Scalability of the components considering the following aspects:

o Processing Capacity;

o Data storage;

o Increase in the number of simultaneous clients without loss of performance;

It shall allow "hot standby" for:

o Application servers;

o Communication servers;

o Database servers

The system interfaces shall be Windows friendly;

It shall have capacity for remote operation, through access from a local network or through the

Internet in safe environments, enabling configurations, programming and control of the

applications.

3.3.3 Scope of The Supply

The MRS shall be supplied completely with all the required applications, databases and

other items necessary for its perfect operation;

The Supplier shall be responsible for the execution of all the installation services and all

the interfaces required with the KPLC systems (e.g ICS, SAP, IMS Outage Management

system, ITRON,C&I,GIS and EBM Energy Balance Module) and supply of all the

equipment needed to make operable the Management Reading System "MRS" specified

in this document.

The Bidder shall include in its proposal all the applications and licenses to implement the

MRS, with all the characteristics and features defined in this specification. The licenses

must be for the perpetual use of KPLC;

The MRS shall be scalable and will allow the use of multiple instances provided they

could be integrated into a single database.



12 of 157

The Supplier must indicate the additional costs for the utility to be incurred in the system

expansion (hardware, software licenses, etc.)

With the implementation of the MRS and the required interfaces, KPLC will be to

remotely collect data from the meters for:

o Billing

o Fraud detection

o Establish new tariff structures

o Improve the service quality index

o Eliminate operational costs of commercial procedures

o Control and management of costumers loads

o Resources in the field (transformers, cables among others)

o Improve network expansion planning.

o Energy Balance

The Supplier shall include the supplies and activities necessary and mandatory for MRS

to be fully operational, including:

o Supply of the system application software and of the hardware;

o Configuration of the database;

o Implementation of the system including assistance in the installation of hardware,

software and commissioning;

o Implementation of the interfaces with KPLC main systems including but not

limited to ICS (Billing system), SAP, C&I, EBM (Energy Balance Module) and

IMS (Outage Management System).

o Implementation of the System Acceptance Test (defined in this document in a

later section);

o Provision of instruction manuals for the System, for Production and for Technical

Support;

o Initial training of the KPLC’s specialists, who will be responsible for the

production activities, technical support and users of the features and tools of the

MRS.

The Supplier shall provide a Maintenance and Support Agreement. It will include the

following activities:

o Implementation of the patches and corrections provided by the manufacturers of

the software that compose the environment of MRS;

o Installation of new versions and releases, including their analysis, their suitability

for the use in the processes adopted by the KPLC, their installation and follow up

of the support activities, object of the contracts of maintenance of the mentioned

software;

o Troubleshooting of hardware, software, network, and other operating systems for

servers and workstations that may be related with the MRS;



13 of 157

o Help Desk support for the MRS and any other components made available to the

users, which includes: Support, preparation of scripts, description and systematic

record of the problems, their immediate solution or deferral of these problems to

teams in charge of work, installation and configuration of the associated software,

creation and maintenance of users and evaluation of the processes.

3.4 MANAGEMENT READING SYSTEM

Data collection and memorizing function collects data automatically in an efficient and reliable manner

from the meter and memorizes (archive) them in a corresponding database or performs instant reading of

the meter upon user request.

3.4.1 General Features of the MRS

The system shall support the following data collection and functionality:Extraction of all data in

the meter including:

o Full read packets for scheduled and ‘on demand’ reads. A full packet includes

register and interval data, and all meter events.

o Bidirectional Real and Reactive energy

o 15 minute interval data – 4 channels for singlephase meters, 8 for polyphase

meters

o Net metering data

o Voltage (register and interval data)

o Per phase current, voltage, energy and demand on polyphase meters

o Meter events for all meter diagnostics, such as an under voltage alert or an outage

or restoration message

o Ability to send a ‘last gasp’ outage event when the meter losses power

o Demand metering;

o Remote demand resets;

o On-request reads;

Shall permit the customer data entry and update;

Entry, update and monitoring of data on installation and replacement of meters;

Allow for GIS coordinates acquisition for the meter;

Real time clock synchronization;

Set up and change of approved mean power limit;

Change of voltage thresholds related to electricity quality;

Setup, change, review and synchronization of reading programs/sequence;

Setup, change, review and synchronization of programs/sequence execution priorities;

Setup, change, review and automatic update of communication route;



14 of 157

Setup and management of grouping of meter reading;

Activation of function keys on the meter (e.g. conditional reconnection);

Any programmable or not programmable command can be sent individually or to any

group of any level; Shall automatically provide the available data from each consumer

unit starting from its selection;

Shall allow the exportation of all meter data from the system to ASCII, TXT, XML, CSV

or Excel files;

Shall allow the allocation of consumer units for analysis groups and relocate them, when

necessary;

Shall generate summaries of the events with information about power, current and

voltage, alarms, etc.;

Shall have features that will allow performing the activities related to the management of

the measurement and actions related to the protection of the revenue;

Shall have features that will allow performing the activities related to the disconnection

and reconnection;

Shall generate graphical reports and statistics related to active energy, reactive energy,

demands and quality parameters;

Shall generate statistics of periodic events (frequency and duration) per measurement

points, per occurrences;

The system shall generate histories of all the parameters per measuring point;

The System shall have functionalities that will allow the setting for a scheduled electric

energy meter readings, in addition to allow on-demand access, at any time, to these same

points of measurement;

The MRS system shall be able to monitor/read meter data during data processing. Shall

report the status of the reading process, percentage of advance, etc.;

Shall permit to define a Calendar with holidays;

Shall permit to define and schedule automatically reading according to the reading

routine;

Shall show the Consumption charts (Hourly, daily, weekly, monthly) of active energy of

the measurement point, with at least the following features and characteristics:

o The period, under the initial conditions of implementation, shall automatically

present the available reading period;

o Line type chart or bar type chart, with different colors for each type of quantities;

o Meter parameters entry and update

o Daylight saving time changes

o 15 minutes or less of interval data per channel

o Tariff programmed change

o Change of display value period on meter display



15 of 157

o Change of sequence and selection of registers for display on meter display

o Change of electric power integration period

o Controllable output management

o Change of registers within profile framework.

o Change of profile periods

o Change of voltage thresholds related to electricity quality

o Meter software change and Meter Firmware Update

o Software shall be able to read any meters that provide a standard communication

interface

It shall allow the visualization of the register and interval data of the parameters of each

metered and calculated value, with, at least the following information:

Note: The visualization of data is the ability to view register and interval data.

o Meter’s identification number

o Meter’s firmware version

o Meter’s program

o Inductive (Lagging) PF (power factor) and capacitive (Leading) PF

o Multiple channels of data at the same time.

o Battery status

o Composition of the measurement channels used to calculate billing determinats

such as the PF

o The interval range of mass memory storage – the start and stop time and dates

o Integration interval – interval used for calculating demand (KW or KVAR or

KVA) from energy values

It shall allow the visualization of the data from all available channels on the meter in daily,

weekly or monthly segmentation, for initial / final specified periods (day / month / year)

in intervals of lowest resolution recorded, such as 5, 15 (default), 30 or 60 minutes, with

exportation for, at least, the Excel format or CSV;

It shall allow the visualization of the meter values derived from interval data, from every

meter with the following information where some values must be calculated from the total

interval data values:

Note: Time periods such as off-peak are defined by KPLC and can be easily adjusted by

KPLC.

o Presentation Mode (pulses and magnitudes and energy values)

o Grand total usage, such as KWH, KVARH Lag, KVARH Lead, etc.

o Total at the direct peak

o Total at the reverse peak,



16 of 157

o Total off-direct peak

o Total off-reverse peak

o Total direct reserved

o Total reverse reserved

o Previous peak demand prior to most recent demand reset.

o Maximum peak demand

o Maximum off-peak demand

o Maximum reserved demand

o Accumulated reserved demand

o Reactive Energy Billing Value

o Reactive Power at Maximum Peak Demand

o Reactive Power at Accumulated demand at the peak

o Total exceeding reactive energy

According to the capacity of the meter, it shall be possible to extract archives from all

meters channels.

It must have a screen for visualization of at least the last ten power outages (greater than

predefined duration - e.g. 5 minutes), with date and time of the start of the outage, date

and time of the end of power restoration and detailed duration in days, hours, minutes

and seconds;

It shall allow KPLC to make the following changes in parameters:

o Date;

o Range of demand;

o National holidays;

o Multiplication constants;

o Time segments;

o Condition of reserved time;

o Method of demand calculation;

o Automatic replacement of demand;

o Summer time;

o Method of calculation of the quantity of energy corresponding to the reactive

energy surplus;

o Visualization of the display codes;

o Condition of the serial output of the user;

o Presentation format of the display quantities;

o Micro-adjustment of the clock;

o Reading;



17 of 157

The MRS system shall show the endpoint registers voltage variations in accordance with

the meter parameterization or MRS configuration.

MRS system must interface with the KPLC Outage Management System (OMS) uploading outage

and restoration events from the AMI System.

3.4.2 Generation of Reports / Charts

It shall allow the generation of graphs of the measuring point, with at least the following

characteristics:

Zoom functionality (increasing and decreasing), making possible amplifications for detailing

specific areas of the graph and subsequent return to the initial conditions sizing;

The system shall allow for graphing of register, interval, and calculated values over a period of

time, such as:

Power factor graph: it shall have as a central reference on the horizontal axis the value of

power factor equal to one or other adjusted value based on the available data. Values in

the lower part of the chart shall correspond to inductive power factors and in the upper part

to capacitive power factors.

Graph of the load curve (daily, weekly, monthly) from the point of measurement and from

the available channels, with at least the following features and characteristics:

o Option to view the data recorded in any of the channels (as available in the meters);

o Possibility of choice of the date and of the time of the start and of the end of the

analysis;

o Line chart or bar chart types, with different colors for each type of quantity;

o Ability to export data;

o Ability to draw phasor (vector) diagrams from per phase voltage, current, and

power factor values.

3.4.3 MRS Administration Function

The MRS shall support the following functionalities:

Defining of roles and users/user groups

Access control to System components

Administration of reporting functions

Execute a regular backup of all data at the desired time.

Defining of user/user group rights

Manage dynamically the server infrastructure (Application, Communication and Data

Base servers status)



18 of 157

MRS system shall provide such data access and target functionality that should ensure that only

authorized users could use the system, within the scope of their authorizations according to the

security level. Records must be kept about the users having system access, with specification of

privileges for each user, as well as system access records (identification of successful and

unsuccessful attempts).

When user privileges are changed, MRS system must register the security level change, time of

the change and who executed the change.

MRS system should implement a security procedure on all access levels through the usage of

users, groups of user, as well as their roles. Security procedure shall support the possibility of

allocating users within specific or standard groups, whereby; roles are defined in the way enabling

the application to individuals or groups of users.

3.4.4 MRS Reporting Capabilities

3.4.4.1 Analysis of statuses and alarms

The MRS must be able to report the number of meters (and AMI communication network device) with

any type of a meter event. It must also report meter counts by AMI status. KPLC will be able to use the

MRS to view all related meter identification and location data for each meter.

Result of such reports should be the daily, i.e. periodical report on the state clearly showing all alarms,

statuses and events and on which meters, representing the basis for further action on these meters.

3.4.4.2 Reports on electricity quality

The MRS will report and tabulate all meter events associated with a under or over voltage threshold event.

KPLC will be able to use the MRS to view all related meter identification and location data for each meter.

In this way, the function would indicate poor voltage circumstances with one or a group of customers and

it would represent the reason for the crews to go out into the field.

3.4.4.3 Communication reports

Statistics of communication between system elements represents a special whole within the reporting

functions.

3.4.5.4 General

All reports must be capable to be downloaded to Excel, CSV, ASCII and TXT file.

Print/Print Preview option is mandatory with every report automatically generated in the form of PDF

file.

3.5 USER AND OPERATOR INTERFACE

It is desirable that administrator and client GUI (Graphical User Interface) is realized on the latest

computer platform not requiring special software installation.

3.6 DATA MANAGEMENT



19 of 157

3.6.1 Data Grouping

Key information of MRS systems is grouping of gathered meter data for the following purposes:

billing, reporting and analysis.

3.6.2 Data and Information Exchange Functions with MDM System and Other

Information System of Electric Utility

This section identifies elements that need to be transferred to and from the MDM system. Data

transfer request should be executed consistently to and from MDM system, information

subsystems within electric utility and other interested parties.

3.6.3 Data Entry Into MRS System

Data entered into MRS system include:

Data from Customer Information System

Information related to reading Cycle and routes

Data on network resources on which End Point have been implemented

3.6.4 DATA SUBMITTED TO BILLING SYSTEM

The type of information transferred between MRS and Billing System:

Automated data on electricity accounting collected by MRS

Data on metered consumption and reports from AMI system

In the defining of the requirements in terms of automated data transfer between systems, it is necessary to

anticipate submission of grouped accounting according to an accounting period, in accordance with the

operation technology of electric utility.

All data on electricity accounting to be submitted to the Billing System will be archived by the System.

3.6.5 Data submitted to MDM System

An example of information transferred between MRS and MDM System:

o Data on metered consumption for Industrial Customers, at a daily level; data on

consumption must be transferred at the end of every day.

o Data on metered consumption for industrial customers; data on consumption must

be transferred on the lowest measured resolution such as 5, 15, 30 or 60-minute

data at the end of the every day.

The type of information transferred between OMS (Outage Management System) and

MDM System must managed in the MDM for VEE and fraud detection processes.

3.6.6 Voltage Variations

The MRS system must display meter events for over voltage or under voltage meter events detected by the

meter.



20 of 157

4 METERING CONTROL CENTER FUNCTIONALITY AND

CAPABILITY.

4.1 DESCRIPTION AND GENERAL REQUIREMENTS FOR METERING CONTROL

CENTER

Meter Control Centre (MCC) is based on AMM (Automated Meter Management) concept

implying remote reading and simultaneous efficient supervision and management of other AMI

components (Advanced Metering Infrastructure), high data processing speed in a multiuser

environment (Client/Server architecture), connection with other information systems (Billing

system, Customer Information System, etc.) and data transfer into MDM System.

Meter Control Centre (MCC) is based on a corresponding computer and telecommunication infrastructure

enabling its continual and efficient operation - (systems provide the required redundancy, disturbance-free

operation in case of power supply outage and the likes). Servers and clients of the Main Meter Control

Centre (MMCC) have a corresponding system and application software installed enabling execution of all

specific functions. Users of Regional Meter control Center (RMCC) have a corresponding System and

application software installed enabling execution of all specific functions. Meter Control Centre (MCC)

needs to function under the conditions of existing computer and telecommunication organization of electric

utility. The supplier is responsible to provide all elements and services to install and operate the system.

4.2 METERING CONTROL CENTER (MCC) FUNCTIONS

Metering controlCenter (MCC) functions will be supported with one or more computer programs.

The quantities and distribution of MCC must be determined in attention to the characteristic of each project

and according to one of the architecture definition at the point 1.6 of this document.

The following function must be present in at least one Main Metering controlCenter. The Supplier must

provide all skill to make possible that the Main Metering controlCenter (MMCC) executes the following

functions:

Administration of the System Components (AMI Infrastructure, MDMS)

Monitoring the Data Collection process

Monitoring the Data Transfer Process

Report Generation and Data Analysis to detect possible Anomalies in the Endpoint.

4.2.1 System Components Administration

Manage all software (versions of application software and firmware) and all the settings of the AMI system.

Administration of System components enables:

4.2.1.1 Meter Management.

Meter Management consists of the following function among others.

Meter data entry and update

Meter parameters entry and update

Entry, update and monitoring of data on installation and replacement of meters

Real time clock synchronization

Meter software change



21 of 157

4.2.1.2 Communication Equipment Management.

The Network Managment system at the MCC shall be supplied for the following communication

equipments: GPRS Modems, Protocol Converter, Concentrator or any other equipment installed as

Endpoint.

4.2.1.2 Security Management

The following task must be executed by MCC:

Defining of roles and users/user groups

Defining of user/user group rights needs to be defined in relation to:

o Entry and update of data and parameters

o Defining of possibilities for command execution

4.2.2 Data Collection/ Reading and Monitoring

The MCC team must be able to define and monitor the execution of the following tasks:

4.2.2.1 Data collection execution Process:

o Reading of individual meter – On Demand -;

o Reading of the group of meters – Scheduled;

o Automated reading according to the scheduler;

o Reading on request;

o Special reading on request;

4.2.2.2 Data collection monitoring Process:

Monitoring the run level of the readings that have been programmed and the On-demand

commands that have been required

o Meters already read, pending, failed, etc.

o Command already executed, pending, failed, etc.

4.2.2.3 Alarm Monitoring Process:

The MCC team should be able to do analysis, interpretation and identifaction of tamper case.

The MCC team should be able to profile alerts as critical/high priority and low priority

The Team should be able to assign and escalation for execution.

The MCC team should be able to monitor and ascertain resolution

4.2.3 Monitoring the Data Transfer Process

The MCC team must be able to define and monitoring the execution of the following tasks:

4.2.3.1 Data Transfer execution process:

Main Metering controlCenter (MMCC) should support push and pull procedure of data

submission on metered consumption and other data to MDM system and to Billing System.

Metering controlCenter (MCC) should be able to enable the sending of all data on metered

consumption every day for the previous daily reading period.



22 of 157

4.2.3.2 Data collection monitoring Process:

A validation process will be defined to maintain the data integration during all transfer

process.

4.2.4 Report Generation and Data Analysis

The MCC team must be able to obtain the following reports for the system to enable team field operation.

4.2.4.1 Reports with analysis of statuses and alarms

This type of reporting functions processes alarms and statuses of meters/concentrators, event logs, with the

making of corresponding reports after finding corresponding alarms, statuses and events.

These functions would minimally process events and alarms related to the disruption of meter integrity, as

well as attempt or disruption of data integrity in meters or concentrators (e.g. meter reprogramming

attempt).

The result of such reports should be daily, i.e. periodical report on the state clearly showing all alarms,

statuses and events and on which meters, representing the basis for further action on these meters.

4.2.4.2 Reports on electricity quality

This reporting function would execute an analysis of voltage circumstances on the meters themselves since

there are corresponding records in the electricity quality log recording voltage drop/overvoltage

below/above defined voltage thresholds and supply interruptions. In this way, the function would indicate

poor voltage circumstances with one or a group of customers and it would represent the reason for the

crews to go out into the field.

4.2.4.3 Communication reports

Successfulness statistics of communication between system elements represents a special whole within the

reporting functions.

4.2.4.4 Other Reports

The list of reports is not final since it is not possible at this moment to anticipate all necessary types of

reports. In addition to those mentioned before some other report for controls of some operation like

connect/disconnect customers, meter parameterization changes, etc. will be required.

4.2.4.5 Reports General requirements

The reports may be sorted according to all parameters. Moreover, search function needs to have the

possibility of search according to all System element attributes.

Print/Print Preview option is mandatory. Download to XLS, ASCII, CSV and TXT file is mandatory.

Optional, but recommended, every report could be automatically generated in the form of PDF files.



23 of 157

5 SPECIFICATIONS FOR SMART SINGLE PHASE STATIC METERS

FOR ACTIVE ENERGY

5.1 SCOPE

5.1.1 This specification is for newly manufactured Smart single-phase electric meters for

measurement of alternating current active energy in 230 V, 50 Hz networks.

5.1.2 The meters are for use in Advanced Metering Infrastructure (AMI) system. The Meter shall

be able to communicate with a data concentrator, relay or collector through RF technology,

PLC technology or a mixed RF-PLC technology.

5.1.3 The modem shall support meter communication protocols as per DLMS/COSEM

standards

5.2 NORMATIVE REFERENCES

The following documents were referred to during the preparation of this specification:

[1] IEC 60529:1989. Degrees of protection provided by enclosures (IP Code)

[2] IEC 62052-11:2003, Electricity Metering equipment (a.c.) – General Requirements, Tests

and Test Conditions - PART 11: Metering equipment

[3] IEC 62053-21:2003, Electricity metering equipment (a.c.) – Particular Requirements - Part

21: Static meters for active energy (Classes 1 and 2).

[4] IEC 62054-21:2004: Electricity metering (a.c) – Tariff and Load Control- part 21:

Particular requirements for time switches

[5] IEC 62055-21:2005, Electricity metering – Payment systems – Part 11: Framework for

Standardization

[6] IEC 62055-31:2005, Electricity metering – Payment systems – Part 31: Particular

requirements – Static payment meters for active energy (classes 1 and 2).

[7] IEC 62055-41, Electricity metering-Payment systems-Part 41: Standard transfer

specification (STS) - Application layer protocol for one - way token carrier systems

[8] IEC 62056-21:2003, Electricity Metering – Data exchange for meter reading, tariff, and

load control – Part 21: Direct local data exchange.

[9] IEC 62056-46:2006, Electricity metering – Data exchange for meter reading, tariff and

load control – Part 46: Data link layer using HDLC protocol



24 of 157


load control – Part 53: COSEM Application layer


load control – Part 61: OBIS object identification system


load control – Part 62: Interface classes

In case of conflict, the requirements of this specification take precedence.

5.3 TERMS AND DEFINITIONS

In addition to terms and definitions given in IEC standards referred in section 2 above, the

following terms shall apply:

CIU: Customer Interface Unit

COSEM: Companion Specification for Energy Metering

DLMS: Device Language Message Specification

EDIS: Energy Data Identification System

EMC: Electromagnetic Compatibility

GPRS: General Packets Radio Service

GSM: Global System for Mobile communications

Ib: Basic current of an electric meter

Imax: Maximum current of an electricity meter

In: Nominal current of a transformer coupled electricity meter

IEC: International Electro-technical Commission

ISO: International Organization for Standardization

LED: Light Emitting Diode

LCD: Liquid Crystal Display

KP: Kenya Power (use interchangeably with KPLC)

KPLC: Kenya Power and Lighting Company Limited

PLC: Power Line Carrier

RF: Radio Frequency

TCP/IP: Transmission Control Protocol/Internet Protocol

TMR: Energy Tele-Meter Reading system

5.4 REQUIREMENTS

In addition to the requirements in IEC standards highlighted in section 5.2 above, the meters shall

fulfill the following requirements:



25 of 157

5.4.1 The meters shall be suitable for operation in tropical climate where temperatures may

vary from -1 to +60 degrees Celsius.

5.4.2 Relative humidity reaching 95 % and altitude of up to 2,600 m.

5.4.3 The meters shall be used for measurement of active energy for domestic loads under

tropical climate conditions.

5.5 DESIGN AND CONSTRUCTION REQUIREMENTS

5.5.1 General

The design and construction requirements given in 5.3 [1] shall apply.

5.5.2 Meter Cover, base and terminals

5.5.2.1 The meters shall be constructed as 1 phase 2-wire meters.

5.5.2.2 The meters shall have terminals with bottom entry for cables and the arrangement shall

be L: N: N: L (Live In: Neutral In: Neutral Out: Live out respectively).

5.5.2.3 The meter base and cover shall be of non-metallic, non-hygroscopic, flame retardant,

polished material having high impact-resilience and low dirt absorption properties.

5.5.2.4 The front cover may be of translucent material but shall have a window (clear glass or

polycarbonate) for reading the display and for observation.

5.5.2.5 The meters shall conform to the degree of protection of at least IP 54 as given in IEC

60529:1989.



26 of 157

5.5.2.6 The material of which the terminal block is made shall be capable of passing the tests

given in ISO 75.

5.5.2.7 The meters shall be for front projection mounting.

5.5.2.8 The meters shall have sealing provisions for the meter body, meter cover and terminal

cover

5.5.2.9 The meters shall be equipped with lockable/sealable push buttons where such buttons are

used to change some meter parameters.

5.5.2.10 The potential link of the meters shall be internal (inside the sealed part of the meter).

5.5.2.11 The meters shall have a sealing provision for terminal cover.

5.5.2.12 The meter terminal cover shall be such that it will not be possible to access meter

installation screws without breaking the meter cover seal(s).

5.5.2.13 Terminal holes shall be of sufficient size to accommodate the cables of at least 8 -mm

diameter.

5.5.2.14 The meters terminal holes and screws shall be made of brass or nickel-plated brass for

high strength and good conductivity.

5.5.3 Communication

5.5.3.1 The meters shall have LED indicators for testing and indication of kWh and kvarh-

measurement.

5.5.3.2 The meters shall be equipped with an infrared optical port compliant with the IEC 62056-

21 standard for meter programming and data downloading.

5.5.3.3 The meters shall support two-way communication.

5.5.3.4 The Smart Meters shall have a modular design and support a range of different

communication options including but not limited to: Power Line Communication (PLC),

Serial RS485, RF, mobile data (dual standard GPRS/3G, and Ethernet. The Meter shall

be able to communicate with a remote central system using a plug in modem/module,

through the 3G networks.

5.5.3.5 The RS485 communication interface should include at least a 4 digital outputs, isolated

from all other meter circuits with fail-safe circuitry able to withstand AC 230V for 2

minutes without damage.



27 of 157

5.5.3.6 The meters shall be compliant with the DLMS/COSEM or equivalent communication

protocol.

5.5.3.7 The meter shall have provision for an IP-based WAN/LAN option to include Fiber

Optics, Ethernet (WIFI) and GPRS.

5.5.3.8 The smart meters should feature a hot swappable, field replaceable, plug in

communications module inside the Smart Meter casing plug and play flexibility with the

options of PLC, RF, GPRS, RF/Zigbee and LAN communications, without dismantling

the meter and without the need to upgrade the Smart Meter firmware. It should be

possible for authorized personnel to remove and replace communications module

contained within the Smart Meter without de-energizing the Smart Meter. The

communication module can be replaced at site without power off the meter. The



28 of 157

communication module shall have the DC power output +13V to support the power to

UIU.

5.5.3.9 Meter’s firmware shall be upgradable remotely and locally. Upgrading of firmware shall

not stop and affect meter's metrology.

5.5.3.10 Meter shall support external UIU or external IHD and meter information can be achieved

via UIU or IHD.

5.5.3.11 The communication module shall support both SMS and GPRS modem and support the

mode of: on line and on-demand on line.

5.5.3.12 The communication module shall support USSD, CSD communication.

5.5.3.13 Meter should send a ‘last gasp’ power outage response when it loses power and a

restoration message when power is restored?

5.5.3.14 The meter shall have, depending on physical communication constraints, a last gasp

mechanism to inform the system of outages.

5.5.3.15 The meter shall support manual meter reading in case of loss of communication to the

meter.

5.5.4 Meter display

5.5.4.1 The meters shall have a backlight seven-segment Liquid Crystal Display (LCD) for

displaying parameters and measured values.

5.5.4.2 The meter LCD shall have at least seven (7)-numerical characters comprising of

selectable integers and NO decimals points for energy measurement. The minimum

character height shall be eight (8) mm.

5.5.4.3 The meters LCD shall have at least 4-digit ID codes.

5.5.4.4 The meters LCD shall be capable of displaying the current state of the disconnector

control unit via symbols.

5.5.4.5 The meters LCD shall be capable of displaying various tampering conditions of the

meter.

5.5.4.6 The display parameters shall be configurable by software action.

5.5.4.7 The LCD display shall operate in at least two modes, namely, basic and extended data

list display using push buttons on meter front

5.5.4.8 The meters shall have provision for scrolling through the display parameters.

5.5.5 Real time clock and memory

5.5.5.1 The meters shall have a real-time clock controlled by a quartz crystal oscillator. It shall

be possible to reset the clock without loss of billing data.

5.5.5.2 The accuracy of the clock shall be ≤ 0.5s and shall meet the requirements of IEC 62054-

21.

5.5.5.3 The meters shall have remote and local synchronization capability.



29 of 157

5.5.5.4 The Clock shall have a configurable calendar type either as MMDDYY, DDMMYY or

YYMMDD.

5.5.5.5 The meters shall have a back-up power supply-Lithium Battery- to support display

reading data when there is no main supply.

5.5.5.6 If the backup supply is by means of Lithium battery, it shall have a shelf life of ten (10)

years and a carryover life of 1 year.

5.5.5.7 The meters shall have a non-volatile memory capable of data storage and with long-term

data retention for the certified life of the meter or fifteen (15) years, whichever is greater

without an electrical supply being supplied to the meter.

5.5.6 Load control and management

5.5.6.1 The meters shall be capable of disconnecting/ reconnecting load remotely.

5.5.6.2 The meters shall have a facility to enable automatic disconnection of whole of customer

load when the set/authorized demand is exceeded.

5.5.6.3 The meters shall have a facility to enable automatic disconnection of part(s) of customer

load when the set/authorized demand is exceeded.

5.5.6.4 The meters shall be configurable as post payment or prepayment meters remotely.

5.5.6.5 The meters shall have provision for keying in credit tokens when meters are operated in

the prepayment mode.

5.5.6.6 In prepayment mode, the meters shall support Offline prepayment (STS) and online

prepayment

5.5.6.7 The load disconnect switch shall have the following characteristics:

a) Mechanical life at maximum power, PF=1: At least 3,000 cycles

b) Maximum switching current: At least 80 A

c) Maximum overload current: At least 96 A (30 min)

d) Maximum switching voltage: At least 265 V AC

e) Short circuit < 3mS: 3,000 A

f) Insulation strength (4kV, 50 Hz, 1 min):

Contact to contact: 2 kV

Coil to contact: 4 kV

g) Impulse strength (1.2 / 50μS to IEC 62052-11):

Contact to contact: > 4 kV

Coil to contact: > 8 kV



30 of 157

5.5.7 Time-of-use tariff measurements

5.5.7.1 The meters shall be capable of measuring and displaying time-of-day active and reactive

energy consumption up to four tariff registers.

5.5.7.2 The meters shall be capable of measuring and displaying time-of-day demand (kW and/or

kVA) consumption up to four tariff registers.

5.5.7.3 Each tariff register shall be set to operate over defined time periods during a 24-hour day.

5.5.7.4 The meters shall have at least two seasons and four day types namely weekday, Saturday,

Sunday and Special/Holiday with switching times set independently.

5.5.7.5 The meters shall have at least forty (40) special days to take care of national holidays,

world days and Easter holidays.

5.5.8 Energy measurements

5.5.8.1 The meters shall be capable of measuring and displaying active, reactive and apparent

energy consumption in both import and export modes.

5.5.8.2 The meters’ principal unit for the measured values shall be the kilowatt-hour (kWh).

5.5.8.3 The meters shall be capable of recording of active energy in all 4 quadrants with up to 4

tariffs.

5.5.8.4 The meter shall allow KPLC to select measurement of KVARH and KVAH to include

or not to include harmonics in the measurement. Thus, chosing vector (phasor), artimretic

apparent, or apparent power.

5.5.8.5 The meter shall have at least four (4) registers for energy.

5.5.8.6 The meters shall be capable of measuring energy in security mode and also record

reversed units.

5.5.8.7 Meters shall have a facility to indicate reverse energy consumption.

5.5.8.8 The meters shall have capability of closing end of billing period on any selected date of

the month selectable by software.

5.5.8.9 The meter’s billing registers shall NOT be re-settable to zero readings without being

reprogrammed.

5.5.8.10 The meters shall have at least twelve (12) billing historical data stored in memory and

retrievable by software action.

5.5.9 Demand measurements


demand consumption in both import and export modes.

5.5.9.2 The meters shall display demand values and their time and date stamps.

5.5.9.3 The meters shall measure demand correctly even when the phase rotation/sequence is

incorrect.

5.5.9.4 The meter shall have at least four (4) registers for demand.



31 of 157

5.5.9.5 The meters shall have a capability of closing end of billing period on any selected date

of the month selectable by software.


retrievable by software action. The current and billing/historical data shall be available

on meter display for reading and billing purposes.

5.5.9.7 The meter shall support local or remote demand reset.

5.5.10 Instrumentation data measurements

5.5.10.1 The meters shall be capable of displaying instrumentation data namely instantaneous

phase voltages and currents, phase angles, and power factor.

5.5.10.2 The meters shall be capable of measuring and displaying instantaneous power (active,

reactive and apparent).

5.5.10.3 The meters shall be capable of continuous display of the presence or absence of

individual phase voltages.

5.5.11 Load profiling

5.5.11.1 The meters shall be capable of profiling multiple channels of energy, demand (KVA,

KW, KVAr), voltage, current, power factor, harmonics, for a period of at least six (6)

months for 60 minutes data intervals.

5.5.11.2 The load profile integration period shall be programmable between 1 minute up to a

maximum of Sixty (60) minutes.

5.5.12 Power Quality Analysis

5.5.12.1 The meter shall collect and record basic power quality information – overcurrent, total

no. of alarms, power outages, voltage and current, average power factor and line

frequency, temperature, etc.

5.5.12.2 The meters shall provide Total Harmonic Distortion (THD) event detection at least up to

the 10th harmonic with analysis for unusual system conditions.

5.5.13 Security features

5.5.13.1 The meters shall be capable of event recording and communication, which shall include

but not be limited to the following:

a) Power ups and power downs with date and time stamp;

b) Individual phase failure, with date and time stamps;

c) Over- and under-voltages based on a pre-set threshold with date & time stamp;

d) Battery voltage status, (if applicable);

e) Memory status;

f) Meter errors;

g) Date and time of last programming/parameterization;

h) Date and time of the last end of billing period.



32 of 157

i) Firmware upgrades

j) Prepayment events

k) Terminal cover removal, even during a power failure

l) Main meter cover removal, even during a power failure

m) Communications removal

n) Magnetic detection, at least 0.5 mT

o) Bypassing neutral

p) Interchanging incoming and outgoing leads

5.5.13.2 The LCD shall display events that have occurred. The events displayed shall include but

not be limited to the following:

a) Meter errors;

b) Phase failures;

c) Battery voltage status, if applicable;

d) Alarms (Meter Diagnostics)

e) Warning messages;

f) Prepayment mode;

g) Terminal cover removal

h) Communications status removal;

i) Magnetic detection, at least 0.5 mT.

5.5.13.3 The meters shall have the relevant software for programming and reading out data.

5.5.13.4 The meter software/program shall be capable of tracking user access to the meter.

5.5.13.5 Access to meter parameters and programming information shall only be through user-

level password(s).

5.5.13.6 The meters shall have sealing provisions for meter cover, terminal cover and any other

opening whose access would compromise the meter security.

5.5.13.7 The meters shall have provision for sensing and displaying the opening of meter terminal

cover.

5.5.13.8 A laptop computer and two optical probes, (see Appendix D for the Laptop computer

specifications), for programming and down-loading the meter data shall be provided at

no extra cost.

5.6 Electrical requirements

5.6.1 The meters shall be operated from mains with reference values of: -

230 V, 50 Hz.



33 of 157

5.6.2 The meters shall be operated from mains with reference values of 230V, 50 Hz, with a

switching voltage range from 0.4Un to 1.3Un.

5.6.3 The meters shall be connectable for single phase two wire systems, drawing of which

shall be indicated on the terminal cover or on the meter base (stickers will not be

acceptable).

5.6.4 The meter shall have reference standard currents of: -

Ib = 5 A; Imax ≥ 80 A.

5.6.5 Power consumption

The requirement of 5.2[2] applies.

5.6.6 Influence of short-time over-currents


5.6.7 Influence of self-heating


5.6.8 AC voltage test


5.6.9 EMC Tests


Requirements 5.6.4 to 5.6.9 shall form part of the type test approval to be issued by an

international / national (of the country of manufacture) meter certifying body.

5.7 Accuracy requirements

Tests and test conditions given in 5.2[1] shall apply.

5.7.1 The meter’s accuracy shall be Class 1 for active energy and class 2 for reactive energy

measurements as per accuracy requirements given in 2[2] and 2[3] respectively.

5.7.2 Limits of errors due to variation of the current.

The requirement of 5.2[2] and 5.2[3] apply.

5.7.3 Limits of error due to influence quantities


5.7.4 Test of starting and no-load condition


5.7.5 Meter constant


5.7.6 Accuracy test conditions


5.7.7 Meter Life test Certification

Meter Life test certification for a lifetime of 15 years from an accredited laboratory for the

type of meters offered is a requirement. Life Test Cetrification shall be submitted.



34 of 157

Requirements of clause 5.7 shall form part of the type test approval to be issued by an international

/ national (of the country of manufacture) meter certifying body.

5.8 Instructions and marking

5.8.1 In addition to nameplate requirements, each meter shall be marked legibly and indelibly

with the following information:

a) Name or trade mark of the manufacturer;

b) Country of origin;

c) Type/model;

d) Meter number up to ten digits;

e) Bar code with meter number information

f) The inscription “Property of K.P. &. L. Co Ltd.”

g) Standard to which the meter complies;

h) Year of manufacture.

All markings to be written in English and with at least 4 mm figure height.

Every meter shall be indelibly marked with diagrams of connections and phase sequence

for which the meter is intended.

5.8.2 In addition, the following drawings and information shall be required with the

tender:

(a) Meter drawing giving all the relevant dimensions;

(b) Wiring diagrams;

(c) Description leaflet including details of programming of the meters;

(d) User’s and service manuals.

5.9 INFORMATION AND WARRANTY (In case of tender award)

5.9.1 Drawings and technical details shall be submitted to Kenya Power (KP) for approval

before manufacture of the meters commences. KP undertakes to submit their comments or

approval for the drawings within three weeks of receiving the draft copies.

5.9.2 Original software, software manuals and operation manuals shall be submitted in 3 copies.

Description leaflets (brochures) shall be submitted in copies of 100 for each meter type.

5.9.3 The manufacturer shall make a commitment in writing on the availability of essential

spares and other consumables for the certified life of the meter.

5.9.4 KP Engineers will inspect meter-manufacturing facilities intending to supply meters to the

company for the first time at no extra cost, excepting the cost of the engineers’

transportation to the nearest major airport. Such inspection shall not in any way prejudice

the purchaser’s rights and privileges.

5.9.5 Samples

The Laws of Kenya require that the Kenya Bureau of Standards must approve any new

meter being introduced in the country. The Kenya Bureau of Standards address is:



35 of 157

The Managing Director

Kenya Bureau of Standards,

P.O. Box 54974, 00200 Nairobi, Kenya.

Tel: (+254 020) 605490, 602350

Fax: (+254 020) 604031

Email: [email protected]

Web:http://www.kebs.org

5.9.6 The meters shall be packaged in such a manner as to minimize damage and entry of

moisture during transportation and handling.

5.9.7 The meters shall be packed in suitable groups and / or batches with consecutive serial

numbers provided by KP. The range of meter serial numbers shall be indicated on the

outside of the packaging material.

5.9.8 The supplier shall indicate the delivery time versus quantities of each type of meter and

his production capacity.

5.9.9 Where test and/or calibration certificates/reports are issued by a laboratory other than the

International/National Meter Certification Authority, a copy of accreditation certificate

shall be attached together with the tender documents.

mailto:[email protected]



36 of 157

5.9.10 The manufacturer shall provide current e-mail addresses, fax and telephone numbers of

the national/international testing/calibration laboratories and meter certification bodies to

facilitate confirmation of the submitted test reports & certificates.

5.10 SCHEDULE OF TECHNICAL DATA SINGLE PHASE METERS

Standard and type tests

General requirements, tests and test

conditions

IEC 62052-11:2003

Particular requirements for static meters for

active energy

IEC 62053-21:2003

Power consumption and voltage

requirements

IEC 62053-21:2003

Shock test IEC 62052-11:2003

Plastic-determination of temperature

deflection under load

IEC 62052-11:2003

EMC Tests IEC 61000-4-3; EN 55014/55022

Degree of protection IP54

Measurement Base Active

Network type 2-wire

Connection type Direct

Accuracy kWh class 1.0 (IEC 62053-21:2003) and kvarh

class 2.0 (IEC 62053-23:2003) Humidity: Up to 95%

Altitude Up to 2,600m

Temperature range (operating) -1 to +60 0 C

Voltage measurement (Un) 230 V 50 Hz

Voltage range 0.4 Un to 1.3Un

Voltage circuit burden ≤ 2 W and 10 VA

Burst test 4 kV

Impulse voltage 6 kV, 1.2/50 µs

Current measurement Ib = 5 A; Imax = 80 A

Short circuit current 30 Imax

Starting current 0.004Ib

Current circuit burden ≤ 4 VA

LCD display At least 6 digits, Nil decimals

Dielectric strength 4 kV, 50 Hz., 1 min

Terminal entry diameter 8.0 mm

Communication to Central System GSM/GPRS

Local interface Optical (IEC 62053-21)

Disconnector 2-pole disconnector (live only)



37 of 157

5.10.1 STATEMENT OF COMPLIANCE WITH THE REQUIREMENTS OF THE

SCHEDULE OF TECHNICAL DATA –(shall be filled and signed and stamped by

the meter manufacturer)

I………………………………………………on behalf of……………………………………

declare that the above specifications matrix conforms to a typical tender meter,

type…………………………………………………………………………… being offered for

this tender.

Signature………………………………………………….

Date…………………… Stamp/Seal ………………………….



38 of 157

LIST OF ID CODE REGISTERS FOR BASIC AND EXTENDED DISPLAY

LIST OF REGISTERS TO BE DISPLAYED ON BASIC (AUTO SCROLL) DISPLAY

MODE

0.0.0 Display check

F: Meter’s warning Codes (logging event Flags)

E: Meter’s Error Codes (Flags)

1.8.0 Total active import energy, kWh (Current)

2.8.0 Total active export energy, kWh (Current)

LIST OF REGISTERS TO BE DISPLAYED ON EXTENDED (ALTERNATE) DISPLAY

MODE

0.9.1 Current time

0.9.2 Current date


1.8.0.1 Total active import energy, kWh (Historical)

1.8.1 Total active import energy, Tariff 1, kWh (Current)

1.8.1.1 Total active import energy, Tariff 1, kWh (Historical)



9.6.0 Maximum Demand kVA & date and time stamp (Current)

9.6.0.1 Maximum Demand kVA & date and time stamp (Historical)

9.6.1 Maximum Demand kVA & date and time stamp (Current), Tariff 1

9.6.1.1 Maximum Demand kVA & date and time stamp (Historical), Tariff 1



1.5.0 Coincidental Maximum Demand kW & date and time stamp (Current)

1.5.0.1 Coincidental Maximum Demand kW & date and time stamp (Historical)

1.5.1 Coincidental Maximum Demand kW & date and time stamp (Current), Tariff 1

1.5.1.1 Coincidental Maximum Demand kW & date and time stamp (Historical), Tariff 1




2.8.0.1 Total active export energy, kWh (Historical)

32.7.0 Phase voltage



39 of 157

31.7.0 Phase Current

6 SPECIFICATIONS FOR SMART METERS THREE PHASE WHOLE

CURRENT STATIC METERS FOR ACTIVE ENERGY

6.1 SCOPE

6.1.1 This specification is for newly manufactured Three-phase static smart meters for

measurement of alternating current active energy in 3 x 230/400 V, 50 Hz networks.

6.1.2 The meters are for use in Advanced Metering Infrastructure (AMI) system. The Meter shall

be able to communicate with a data concentrator through RF technology, PLC technology

or a mixed RF-PLC technology.

6.1.3 The modem shall support meter communication protocols as per DLMS/COSEM

standards


The following documents were referred to during the preparation of this specification; in

case of conflict, the requirements of this specification take precedence.

[1] IEC 60529:1989. Degrees of protection provided by enclosures (IP Code)

[2] IEC 62052-11:2003, Electricity Metering equipment (a.c.) – General

Requirements, Tests and Test Conditions - PART 11: Metering equipment

[3] IEC 62053-21:2003, Electricity metering equipment (a.c.) – Particular

Requirements - Part 21: Static meters for active energy (Classes 1 and 2).

[4] IEC 62054-21:2004: Electricity metering (a.c) – Tariff and Load Control- part 21:

Particular requirements for time switches

[5] IEC 62055-21:2005, Electricity metering – Payment systems – Part 11: Framework

for Standardization

[6] IEC 62055-31:2005, Electricity metering – Payment systems – Part 31: Particular

requirements – Static payment meters for active energy (classes 1 and 2).

[7] IEC 62055-41, Electricity metering-Payment systems-Part 41: Standard transfer

specification (STS) - Application layer protocol for one - way token carrier systems

[8] IEC 62056-21:2003, Electricity Metering – Data exchange for meter reading, tariff,

and load control – Part 21: Direct local data exchange.

[9] IEC 62056-46:2006, Electricity metering – Data exchange for meter reading, tariff

and load control – Part 46: Data link layer using HDLC protocol


and load control – Part 53: COSEM Application layer


and load control – Part 61: OBIS object identification system



40 of 157


and load control – Part 62: Interface classes

[13] IEC1901.2 standard for high speed (up to 500 Mbit/s at the physical layer)

communication devices via electric power lines.

In case of conflict, the requirements of this specification take precedence.


The definitions given in the above standards shall apply

GTP: Guaranteed Technical Particulars

GPRS: General Packet Radio Service

IEC: International Electro technical Commission

LCD: Liquid Crystal Display

PLC: Power Line Carrier

RF: Radio Frequency

In addition to the requirements in IEC standards in Section 2 above, the smart meters shall fulfill

the following requirements.

6.4 REQUIREMENTS

6.4.1 Operating conditions requirements

6.4.1.1 The meters shall be suitable for operation in tropical climate where temperatures may

vary from -1 to + 60 degrees Celsius.

6.4.1.2 Average annual relative humidity reaching 90 % and altitude of up to 2,600 m above sea

level.

6.4.2 Design and construction requirements

6.4.2.1 General

The design and construction requirements given in 6.4.1 shall apply.



41 of 157

6.4.2.2 Meter cover, base and terminals

6.4.2.2.1 The meters shall be constructed as 3 phase 4-wire meters.

6.4.2.2.2 The meters shall be of British Standard (BS) 5685-foot print for standardized

mounting for asymmetrical (BS) wiring.

6.4.2.2.3 The meters shall be for front projection mounting.

6.4.2.2.4 The meters shall have terminals with bottom entry for cables and the arrangement

shall be L1L1: L2L2: L3L3: NN for 3 phase 4-wire meters.

6.4.2.2.5 The meter’s front cover may be of translucent material but shall have a window (clear

glass or polycarbonate) for reading the display and for observation.

6.4.2.2.6 The meter shall be ultrasonically sealed for life and there should be no screws on the

body except for the termination of cables.

6.4.2.2.7 The meters shall be equipped with lockable/sealable push buttons where such buttons

are used to change some meter parameters.

6.4.2.2.8 The meter terminal cover shall be of the long type with cable entry knock-offs.

6.4.2.2.9 The meter potential links shall be inside the meter body and CAN ONLY be accessed

by opening meter body cover.

6.4.2.2.10 Terminal holes shall be of sufficient size to accommodate the cables of at least 10mm

diameter and depth of 15mm

6.4.2.2.11 The meters terminal holes and screws shall be of moving-cage type made of brass or

nickel-plated brass for high conductivity and corrosion resistance

6.4.2.2.12 The meters shall have a sealing provision for terminal cover that is sealable with

utility wire seals. The meter shall have terminal cover open detection. Once the

terminal cover is opened, the load shall be disconnected.

6.4.2.2.13 The meters shall conform to the degree of protection of at least IP 54

6.4.2.2.14 The meter body dimensions shall not exceed: Height = 250mm; Width = 170mm; and

Depth = 90 mm;

6.4.2.3 Communications

6.4.2.3.1 The meters shall have LED indicators for testing and indication of kWh and Kvarh-

measurement.

6.4.2.3.2 The meters shall be compliant with the DLMS/COSEM or equivalent communication

protocol

6.4.2.3.3 The meters shall be configurable as post payment or prepayment meters manually.

The meters shall have provision for entering credit tokens when meters are operated

in the prepayment mode



42 of 157

6.4.2.3.4 The meters shall have an optical communication port and a RS485 port compliant to

DLMS/COSEM as per IEC62056-21 for accessing information stored inside the

meter.

6.4.2.3.5 The meters shall support two-way communication

6.4.2.3.6 The Meter shall be able to communicate with a remote central system featuring

multiple communication technologies including but not limited to the GSM/GPRS..

6.4.2.3.7 It shall be possible for authorized personnel to remove and replace communications

module contained within the Smart Meter without de-energizing the Smart Meter. The

communication module shall have the DC power output +13V to support the power to

UIU.

6.4.2.3.8 The communication module shall support USSD, CSD communication

6.4.2.3.9 The meter shall report to system when it is power on or off.

6.4.2.3.10 The meters shall have the relevant software for programming and reading out data.

6.4.2.3.11 The meter software/program shall be capable of tracking user access to the meter.

6.4.2.3.12 Access to meter parameters and programming information shall only be through user-

level password(s).

6.4.2.3.13 A laptop computer and two optical probes, (see Appendix C for the Laptop computer

specifications), for programming and down-loading the meter data shall be provided

at no extra cost.

6.4.3 Meter display

6.4.3.1 The meters shall have a backlight seven-segment Liquid Crystal Display (LCD) for

displaying parameters and measured values.

6.4.3.2 The meter LCD shall have at least seven (7)-numerical characters comprising of

selectable integers and NO decimals points for energy measurement. The minimum

character height shall be eight (8) mm.

6.4.3.3 The meters LCD shall have at least 4-digit ID codes (see appendix A).

6.4.3.4 The meters LCD shall be capable of displaying the current state of the relay via symbols.

6.4.3.5 The meters LCD shall be capable of displaying various tampering conditions of the

meter.

6.4.3.6 The display parameters shall be configurable by software action.

6.4.3.7 The LCD display shall operate in at least two modes, namely, basic and extended data

list display using push buttons on meter front.

6.4.3.8 Meters shall have provision for reading the meter at site even when mains power supply

fails.

6.4.4 Real Time Clock and memory



43 of 157

6.4.4.1 The meters shall have a real-time clock controlled by a quartz crystal oscillator. It shall

be possible to reset the clock without loss of billing data.

6.4.4.2 The accuracy of the clock shall be ≤ 0.5s and shall meet the requirements of IEC 62054-

21.

6.4.4.3 The meters shall have remote and local synchronization capability.

6.4.4.4 The Clock shall have a configurable calendar type either as MMDDYY, DDMMYY or

YYMMDD.

6.4.4.5 The meters shall have a back-up power supply to support display reading data when there

is no mails supply.

6.4.4.6 The backup supply is by means of battery, it shall have a shelf life of upto 15 Years (15)

years.

6.4.4.7 The meters shall have a non-volatile memory capable of data storage and with long-term

data retention for the certified life of the meter or fifteen (15) years, whichever is greater

without an electrical supply being supplied to the meter .

6.4.5 Functionality and Load control

6.4.5.1 The self-contained meters shall have a load switch 120A (relay) to enable disconnection

and reconnection of customer load when the set/authorized demand is exceeded and on

the expiry of credit balance when meters are operated on prepaid mode.

6.4.5.2 The load disconnect switches (relay) shall be fitted on both the Live and Neutral circuits.

These relays shall operate simultaneously. In case there is an imbalance between the Live

circuit and the Neutral circuit, the meter will take it as a tamper event and record it. The

meter will measure on the higher current without disconnecting the loading switch.


6.4.5.4 The meters shall have provision for entering credit tokens when meters are operated in

the prepayment mode.

6.4.5.5 In prepayment mode, the meters shall support Offline prepayment (STS) and online

prepayment



b) Maximum switching current per phase: At least 100 A

c) Maximum overload current per phase: 120 A (30 min)

d) Maximum switching voltage per phase: At least 265 V AC

h) Short circuit < 3mS: 3,000 A

i) Insulation strength (4kV, 50 Hz, 1 min):





44 of 157

j) Impulse strength (1.2 / 50μS to IEC 62052-11):





45 of 157

6.4.5.7 The meters shall detect significant reverse energy (SRE) when the line and load wires are

swapped.

6.4.5.8 The meters shall continue to operate correctly and record in forward register during SRE

detection.


6.4.6.1 The meters shall be capable of measuring and displaying time-of-day active and reactive

energy consumption up to four tariff registers.

6.4.6.2 The meters shall be capable of measuring and displaying time-of-day demand (kW and

kVA) consumption up to four tariff registers.

6.4.6.3 Each tariff register shall be set to operate over defined time periods during a 24-hour day.

6.4.6.4 The meters shall have at least two seasons and four day types namely weekday, Saturday,

Sunday and Special/Holiday with switching times set independently.

6.4.6.5 The meters shall have at least forty (40) special days to take care of national holidays,

world days and Easter holidays.



energy consumption in both import and export modes.

6.4.7.2 The meters shall be capable of profiling multiple channels of energy, demand (KVA,

KW, KVAr), voltage, current, power factor, harmonics, for a period of at least six (6)

months for60 minutes data intervals.

6.4.7.3 The meters’ principal unit for the measured values shall be the kilowatt-hour (kWh).

6.4.7.4 The meters shall measure Energy correctly even when the phase rotation/sequence is

incorrect.

6.4.7.5 The meters shall be capable of recording of active and reactive energy in all four (4)

quadrants with up to four (4) tariffs.

6.4.7.6 The meter shall have at least four (4) registers for energy.

6.4.7.7 The meters shall be capable of measuring energy in security mode and also record

reversed units.

6.4.7.8 Meters shall have a facility to indicate reverse energy consumption.

6.4.7.9 The meters shall have capability of closing end of billing period on any selected date of

the month selectable by software.

6.4.7.10 The meter’s billing registers shall NOT be re-settable to zero readings without

reprogramming the meter.


retrievable by software action.




46 of 157


demand consumption in both import and export modes.

6.4.8.2 The meters shall display demand values and their time and date stamps.

6.4.8.3 The meters shall measure demand correctly even when the phase rotation/sequence is

incorrect.

6.4.8.4 The meter shall have at least four (4) registers for demand.

6.4.8.5 The meters shall have a capability of closing end of billing period on any selected date

of the month selectable by software.


retrievable by software action. The current and billing/historical data shall be available

on meter display for reading and billing purposes.


6.4.9.1 The meters shall be capable of displaying instrumentation data namely instantaneous

phase voltages and currents, phase angles, and power factor.

6.4.9.2 The meters shall be capable of measuring and displaying instantaneous power (active,

reactive and apparent).

6.4.9.3 The meters shall be capable of measuring and displaying average power factor for the

current and the previous billing months.

6.4.9.4 The meters shall be capable of continuous display of the presence or absence of

individual phase voltages.

6.4.9.5 The meter shall have diagnostics to alert of any abnormal three phase power condition,

such as: over/under voltage, missing voltage, missing current, improper meter vectors for

service, reverse power flow, etc.


6.4.10.1 The meters shall be capable of profiling multiple channels of energy, demand (kVA, kW,

kVAr), voltage, current, power factor, harmonics, for a period of at least six (6) months

for 60 minute intervals.

6.4.10.2 The load profile integration period shall be programmable from one (1) minute up to a

maximum of sixty (60) minutes.


6.4.11.1 The meter shall collect and record basic power quality information – overcurrent, total

no. of alarms, power outages, voltage and current, average power factor and line

frequency, etc.

6.4.11.2 The meter shall be able to provide voltage sag and swell detection.

6.4.11.3 The meters shall provide Total Harmonic Distortion (THD) event detection at least up to

the 10th harmonic with analysis for unusual system conditions.




47 of 157

6.4.12.1 The meters shall be capable of event recording and communication, which shall include

but not be limited to the following:

a) Power ups and power downs with date and time stamp;

b) Individual phase failure, with date and time stamps;

c) Over- and under-voltages based on a pre-set threshold with date & time

stamp;

d) Battery voltage status (if applicable);

e) Memory status;

f) Meter errors,

g) Date and time of last programming/parameterization;

h) Date and time of the last end of billing period;



k) Terminal cover removal, even during a power failure

l) Main meter cover removal, even during a power failure



o) Bypassing neutral

p) Interchanging incoming and outgoing leads

6.4.12.2 The LCD shall display events that have occurred. The events displayed shall include but

not be limited to the following:

a) Meter errors

b) Phase failures

c) Battery voltage status (if applicable)

d) Alarms

e) Warning messages

f) Prepayment mode

g) Terminal cover removal

h) Communications removal

i) Magnetic detection, at least 0.5 mT


6.5.1 The meters shall be operated from mains supply with reference values of: -

3 x 230/400 V at 50 Hz.



48 of 157

6.5.2 The meters shall be connectable for three phase four wire systems, drawing of which

shall be printed on the terminal cover or on the meter front cover.

6.5.3 The meter shall have reference standard currents of: -

Ib= 10 A; Imax ≥ 100 A for the operating conditions stated in Clause 6.4.1.

6.5.4 Power consumption

The requirement of 6.2 [3] applies

6.5.5 Influence of short-time over-currents


6.5.6 Influence of self-heating


6.5.7 AC voltage test


6.5.8 EMC Tests

The requirement of 6.2 [3] applies.

Requirements 6.5.4 to 6.3.8 shall form part of the type test approval to be issued by an

international/ national (of the country of manufacture) meter certifying body.


Tests and test conditions given in 6.2[1] shall apply.

6.6.1 The meter’s accuracy shall be Class 1 for active energy and Class 2 for reactive energy

measurements as per accuracy requirements given in 6.2 [2] and 6.2 [4] respectively.

6.6.2 Limits of errors due to variation of the current.

The requirements of 6.2 [2] and 6.2 [3apply.

6.6.3 Limits of error due to influence quantities

The requirements of 6.2 [2] and 6.2 [3apply.


The requirements of 6.2 [2] and 6.2 [3 apply.


The requirement of 6.2 [2] and 6.2 [3apply.


The requirements of 6.2 [2] and 6.2 [3 apply

6.6.7 Meter Life test certification for a lifetime of 15 years from an accredited laboratory for

the type of meters offered is a requirement. Life Test Cetrification shall be submitted.

Requirements of Clause 6.6 shall form part of the type test approval to be issued by an

international/ national (of the country of manufacture) meter certifying body.



49 of 157

6.7 Instructions and marking requirements

6.7.1 In addition to IEC 62052-11:2003 nameplate requirements, each meter shall be marked

legibly and indelibly with the following information:

(a) The standard transfer specification (STS) compliant serial number, in the

preferred format known as a national meter number,

(b) The STS compliance logo,

(c) The inscription “Property of K.P. &. L. Co Ltd.”,

(d) Name or trade mark of the manufacturer;

(e) Country of origin;

(f) Type/model;

(g) Meter number;

(h) Barcode comprising of meter serial no without blank spaces;

(i) Standard(s) to which the meter complies;

(j) Year of manufacture.

All markings to be written in English and with c), d) and e) at least 4 mm figure height.

6.7.2 Every meter shall be indelibly marked with diagrams of connections for which the meter

is intended.

6.8 INFORMATION AND WARRANTY

6.8.1 Drawings and technical details shall be submitted to Kenya Power (KP) for approval

before manufacture of the meters commences. KP undertakes to submit their comments or

approval for the drawings within three weeks of receiving the draft copies.

6.8.2 Original software, software manuals and operation manuals shall be submitted in 3 copies.

6.8.3 KPLC Engineers will inspect meter-manufacturing facilities intending to supply meters to

the company for the first time at no extra cost, excepting the cost of the engineers’

transportation to the nearest major airport. Such inspection shall not in any way prejudice

the purchaser’s rights and privileges.

6.8.4 The Kenya Power shall meet the full costs of two engineers, for meter inspection and

acceptance testing at the manufacturer's facility, excepting the cost of engineers'

transportation within country of manufacture. The factory inspection and factory

acceptance tests shall run for duration of a minimum of three (3) working days each.

6.8.5 The suppier/ manufacturer shall meet the cost of the training described later in this

document.

6.8.6 The Laws of Kenya require that the Kenya Bureau of Standards must approve any new

meter being introduced in the country. The address for the Kenya Bureau of Standards is:

The Managing Director



50 of 157

Kenya Bureau of Standards,

P.O. Box 54974, 00200 Nairobi, Kenya.

Tel: (+254 020) 605490, 602350

Fax: (+254 020) 604031

Email: [email protected]

Web:http://www.kebs.org

6.8.7 The meters shall be packaged in such a manner as to minimize damage and entry of

moisture during transportation and handling.

6.8.8 The meters shall be packed in suitable groups and / or batches with consecutive serial

numbers .The range of meter serial numbers including the barcode information for each

meter shall be indicated on the outside of the packaging material.. Packaging shall be done

only after KPLC approval

6.8.9 The number of meters packaged in a group and/or batch for handling/lifting/carrying by

an operator manually shall be such that the weight does not exceed 15 kg.

6.8.10 SCHEDULE OF TECHNICAL DATA

Standard and type tests

General requirements, tests and test

conditions

IEC 62052-11:2003

Particular requirements for static meters for

active energy

IEC 62053-21:2003

Power consumption and voltage requirements IEC 62053-21:2003

Shock test IEC 62052-11:2003

Plastic-determination of temperature

deflection under load

IEC 62052-11:2003

EMC Tests IEC 61000-4-3; EN 55014/55022

Degree of protection IP54

Measurement Base Active / Reactive energy, 3 element, 4 quadrant

Network type 3 phase 4-wire

Connection type Direct connected

Accuracy kWh class 1.0 (IEC 62053-21:2003) and Kvarh

Class 2.0 (IEC 62053-23:2003)

Humidity: Up to 95%

Altitude Up to 2,600m

Temperature range (operating) -1 to +60 0 C

Voltage measurement (Un) 3x 240/415 V 50Hz, 3 phase 4-wire

Voltage range 0.4 Un to 1.3 Un

Voltage circuit burden ≤ 2 W and 10 VA

Burst test 4 kV

Impulse voltage 6 kV, 1.2/50 µs

Current measurement Ib = 10 A; Imax = 100 A

mailto:[email protected]



51 of 157

Short circuit current 30 Imax

Starting current 0.004Ib

Current circuit burden ≤ 4 VA

LCD display At least 7 digits, Nil decimals

Dielectric strength 4 kV, 50 Hz., 1 min

Terminal entry diameter 8.0 mm

System interface GSM/GPRS

Local interface Optical (IEC 62053-21)

Disconnected 1-pole disconnector (live only)

6.8.10.1 STATEMENT OF COMPLIANCE WITH REQUIREMENTS OF THE

SCHEDULE OF TECHNICAL DATA –(shall be filled and signed and stamped by

the meter manufacturer)

I ……………………………………………… on behalf of ………………………………….

declare that the above specifications matrix conforms to a typical tender meter,

type……………………………………… being offered for this tender.

Signature ………………………… Date ………………Stamp/Seal ………………………….



52 of 157

LIST OF REGISTERS TO BE DISPLAYED ON BASIC (AUTO SCROLL) DISPLAY

MODE

0.0.0 Display check

F: Meter’s warning Codes (logging event Flags)

E: Meter’s Error Codes (Flags)



LIST OF REGISTERS TO BE DISPLAYED ON EXTENDED (ALTERNATE) DISPLAY

MODE

0.9.1 Current time

0.9.2 Current date


1.8.0.1 Total active import energy, kWh (Historical)





9.8.0 Import Apparent Sum Energy (Current)

9.8.0.1 Import Apparent Sum Energy (Historical)

9.6.0 Maximum Demand kVA & date and time stamp (Current)

9.6.0.1 Maximum Demand kVA & date and time stamp (Historical)





1.5.0 Coincidental Maximum Demand kW & date and time stamp (Current)

1.5.0.1 Coincidental Maximum Demand kW & date and time stamp (Historical)






2.8.0.1 Total active export energy, kWh (Historical)



53 of 157

32.7.0 Phase A voltage

52.7.0 Phase B voltage

72.7.0 Phase C voltage

31.7.0 Phase A Current

51.7.0 Phase B Current

71.7.0 Phase C Current

13.7.0 Instantaneous PF

14.7.0 Instantaneous system frequency

1.7.0 Instantaneous import active power

3.7.0 Instantaneous import reactive power

9.7.0 Instantaneous import apparent power

13.15.0 Average power factor (Current)

6.8.10.1 Average power factor (Historical)



54 of 157

7.0 SPECIFICATIONS FOR DATA CONCENTRATORS

This specification lays down requirements for Three Phase CT connected smart data

concentrators using GSM and PLC communication. The specification is intended for

procurement of Data concentrators and does not include provision of contract.

7.1 INTRODUCTION

This specification was prepared to establish and promote uniform requirements for three- phase

CT connected smart data concentrators. The specification lays down the minimum

requirements for meters acceptable for evaluation.

7.2 SCOPE

This specification is for newly manufactured smart meter data concentrators. The concentrator

handles two-way communication between the head end system (HES) and the smart meters.

The communication between smart meters and concentrators is by the Power line carrier (PLC

while that between concentrators and HES is by GPRS/GSM dual band for operation in 3G

networks.



[1] IEC 61334-4-32: Distribution automation using distribution line carrier systems - Part 4:

Data communication protocols - Section 32: Data link layer - Logical link control (LLC).

[2] IEC 62056-21:2003, Electricity Metering – Data exchange for meter reading, tariff, and load

control – Part 21: Direct local data exchange.

[3] IEC 62052-11:2003, Electricity Metering equipment (a.c) – General Requirements, Tests

and Test Conditions- PART 11: Metering equipment.

[4] IEC 62053-22:2003, Electricity metering equipment (a.c) – Particular Requirements - Part

22: Static meters for active energy (class 0.5s).

[5] ISO/IEC 14908-2:2012: Information technology – Control network protocol – Part 2:

Twisted pair communication.

[6] ISO/IEC 14908-3:2012: Information technology – Control network protocol – Part 3: Power

line channel specification.

[7] ISO/IEC 14908-4:2012: Information technology – Control network protocol – Part 4: IP

communication.

[8] ETSI GS OSG 001(Open Smart Grid Protocol or OSGP)



55 of 157


GSM: General system of mobile communication

GPRS: General packet radio service

PLC: Power Line Communication

TCP/IP: Transmission Control Protocol/Internet Protocol

7.5 REQUIREMENTS

In addition to the requirements in IEC standards highlighted in section 2 above, the smart

meter data concentrators shall fulfill the following requirements:

7.5.1 Operating conditions requirements

7.5.1.1 The data concentrators shall be suitable for operation in tropical climate where

temperatures may vary from -1 to +60 degrees Celsius.

7.5.1.2 Average annual relative humidity reaching 90 % and altitude of up to 2,600 m above

sea level.

7.5.2 Design and construction requirements

7.5.2.1 The data concentrator cover shall be made of Polycarbonate material.

7.5.2.2 The data concentrators shall be for front projection mounting.

7.5.2.3 The data concentrators shall conform to the degree of protection of least IP 54 as

given in IEC 60529:1989 Degrees of protection provided by enclosures (IP Code)

Amendment 1:1999.

7.5.2.4 The data concentrators shall have provision for sealing the terminal covers for power

intake and interfaces, where such terminals may have negative effect on the operation

of concentrators.

7.5.3 Electrical requirements

7.5.3.1 The concentrator shall be operated from main power with reference values of:

3×57.7/100V to 230 V/400V, 3 x 1 (10) A at 50 Hz

7.5.3.2 Primary currents and voltages for the concentrator shall be programmable through the

software thus allowing primary metering of Demand and Energy.

7.5.3.3 The concentrator shall be connectable as three phase four wire systems (3phase 4wire)

7.5.3.4 The concentrator shall have connection drawing which shall be printed on the terminal

cover

7.5.3.5 The meter shall have reference standard currents of: - In= 1 A; I max = 10 A for the

operating conditions stated in clause 4.1.1.

7.5.3.6 The meters Power consumption shall meet IEC 62053-22 7.1-7.

7.5.3.7 Influence of short-time over-currents meet IEC 62053-22 7.1-7.4

7.5.3.8 Influence of self-heating meet IEC 62053-22 7.1-7.4



56 of 157

7.5.3.9 AC voltage test meet IEC 62053-22 7.1-7.4

7.5.4 Functional Requirements

7.5.4.1 The data concentrators shall automatically discover meters, providing 100% accuracy on

the assets. It should upload (tariff tables) and monitors and reports tampering. It should

have broadcast capability to enable demand response and load shedding.

7.5.4.2 The data concentrator shall have a “Last gasp” mechanism to inform the system of

outages, supported by an internal battery.

7.5.4.3 The concentrators shall have facility for local and remote configuration to suit customers’

requirements.

7.5.4.4 In case of power failure, it stores the data in the non-volatile memory, to be uploaded to

the management system.

7.5.4.5 The concentrators shall have remote and local clock synchronization capability.

7.5.4.6 The concentrators shall have capability for local and remote firmware upgrade and shall

have the following capabilities:

a) Runs automatic scheduled tasks and transfers the information to the (central station)

management system.

b) Includes digital input and outputs to read or activate external devices.

c) Capable of sending immediate alerts on meter tampering. Logs events and stores

up to 200 events.

d) Provides information on GPRS signal quality back to the control center

e) Collects and stores 30 days of data from a maximum of 1000 meters daily.

f) Stores the last 12 months of data.

g) Always on-line when power is on, the Concentrator connects to the main station

automatically. If the connection is lost, the Concentrator will re-establish the

connection.

h) Auto-discovery of smart meters, providing 100% accuracy on the assets.

i) Broadcast capability to enable demand response and load shedding.

j) Downloads tariff tables to the smart meters.

k) Includes a metering capability master and management system (Class 0.5s).

l) Should offer the freedom to choose meters from various vendors and avoid being

reliant on proprietary solutions from a single source.



57 of 157

7.5.4.7 The data concentrator shall support meter data collection compliant with international

standards IEC 62056 (DLMS) designed for interoperability with an open architecture.

7.5.4.8 The concentrator shall have Internet Protocol (IP) routing capability

7.5.4.9 The concentrator shall have remote and local web-based access for Configuration,

monitoring and diagnostics.

7.5.4.10 Should provide an IP security (IPSec) mechanism to ensure high-quality, interoperable,

and cryptology-based security for communication processes.

7.5.4.11 The concentrator shall include security mechanisms against theft and tamper with alerting

features.

7.5.4.12 The concentrator should support upto 1,000 number of meters downstream

7.5.4.13 Feeding phase monitor: The concentrator should be able to identify the feeding phase of

each meter (for single-phase meters ) and detect changing of feeding phase of meter via

PLC communication

7.5.5 Data storage and logging

a) The data concentrators shall have a non-volatile memory capable of data storage

and with long-term data retention for the certified life of the concentrator or ten

(10) years, whichever is greater without an electrical supply being supplied to the

concentrator.

b) The data concentrators shall be capable of profiling at least four channels of

energy and/or demand for a period of at least six (6) months.

c) The load profile integration period shall be programmable between 1 minute up

to a maximum of sixty (60) minutes.

d) The data concentrators shall have at least twelve (12) billing historical data stored

in memory and retrievable by software action.

e) The concentrator shall be capable to log events and store upto 100plus events.

f) The concentrator shall have configurable data logging intervals i.e. minutes, hours

and days.

7.5.6 Electromagnetic Compatibility

a) Dielectric strength: 4 kV, 50 Hz, (IEC 62052-11)

b) Electrostatic discharge: 15 kV (IEC 61000-4-2)

c) Burst: 4 kV (IEC 61000-4-4)

d) Impulse voltage: 12kV, 1,2/50 μs (IEC 62052-11)

e) Electromagnetic field: 10 V/m and 30 V/m (IEC 61000-4-3)



58 of 157

7.5.7 Accuracy requirements

7.5.7.1 Tests and test conditions given in IEC 62052-11 shall apply.

7.5.7.2 The concentrator’s accuracy shall be class 0.5s for active energy and class 2 for reactive

energy measurements as per accuracy requirements given in 2.3 and 2.4 respectively.

7.5.7.3 Limits of errors due to variation of the current.

The requirements of 7.3 [3] and 7.4 [4] apply.

7.5.7.4 Limits of error due to influence quantities

The requirements of 7.3 [3] and 7.4 [4] apply

7.5.7.5 Test of starting and no-load condition


7.5.7.6 Meter constant


7.5.7.7 Accuracy test conditions

The requirements of 2.3 and 2.4 apply

7.5.8 Communication

7.5.8.1 General

a) The concentrators shall have two -way down-link communication mode that supports

communication with the meters by PLC system,

b) In addition to the PLC system, the down-link communication mode of concentrators

shall provide local concentrator maintenance facility through the following methods:

i) RS 232 or 485 interface as per ISO-8482

ii) Infra-red optical interface as per IEC 62056-21 standard

iii) Ethernet

c) The concentrators shall have two -way up-link communication mode (WAN) that

enables communication with Head End System (HES) by using the and GPRS 3G

network and Gigabit Ethernet

d) The concentrators shall support TCP/UDP server and client mode GPRS interface.

7.5.8.2 Down link communication

The data concentrators shall have plug and play communication module with that meets

the following characteristics:

i) Operation mode: Plug and play installation

ii) Communication distance: At least one thousand (1,000) metres

iii) Maximum Response time (concentrator to meter): 10 seconds

iv) Single reading success rate: Minimum 99%

v) Topology : Mesh network support



59 of 157

7.5.8.3 Up-link communication

a) The data concentrators shall have a two-way WAN communication to the Head End

Systems through GPRS (mandatory), Electrical Ethernet (mandatory) and Optical

Ethernet for interfacing to the WAN communication systems.

7.5.8.4 Up-link communication – GPRS

a) The data concentrators shall have a GPRS modem that satisfies the requirements

below:

i. Modem: Pluggable 3G modem

ii. Operating Band: WCDMA/HSDPA/HSUPA/HSPA+:

Band 1, Band 8

GSM/GPRS/EDGE: 850 MHz/900

MHz/1800 MHz/1900 MHz

iii. GPRS multi-slot class: 10

iv. SIM-card holder : Yes

v. SIM card interface : Standard USIM (Class B and Class C)

vi. Power supply for SIM card: 1.8 V and 3 V

vii. SMA connector for the antenna : Yes

viii. SMS capability: Yes

7.5.8.5 Up-link communication – Ethernet

a) Electrical Ethernet interface that satisfies the requirements below:

i. Standard : 10Base T

ii. Data rate : Minimum 10Mbps

iii. Distance : Maximum 100m

iv. Physical interface: RJ45 copper connector

b) Optical Ethernet interface that satisfies the requirements below:

i. Standard: 100/1000Base-ZX /1000Base-LH

ii. Optical Interface : 9/125 µm Single Mode

iii. Signal Wavelength: 1550 nm

iv. Distance : Up to 70 km

7.5.9 Instructions and marking requirements

7.5.9.1 In addition to IEC 62052-11:2003 nameplate requirements, each data concentrator

shall be marked legibly and indelibly with the following information:

a) Name or trade mark of the manufacturer;

b) Country of origin;



60 of 157

c) Type/model;

d) Serial number up to ten digits;

e) Barcode comprising of serial no;

f) The inscription “Property of K.P. &. L. Co Ltd”;

g) Standard(s) to which the concentrator complies;

h) Year of manufacture.

All markings to be written in English and with c), d) and e) at least 4 mm figure height.

7.5.9.2 Every concentrator shall be indelibly marked with diagrams of connections for which

the concentrator is intended.

7.5.9.3 In addition, the following drawings and information shall be required with the tender:

(e) Concentrator drawing giving all the relevant dimensions;

(f) Wiring diagrams;

(g) Description leaflet;

(h) Service and operational manuals.

7.5.9.4 Copies of type approval certificate(s) with test and calibration results of the

concentrator being offered obtained from an international or the national concentrator

certification body shall be provided. If type approval certificate(s) is (are) from

accredited concentrator certification laboratories (and not national or

international body), then it (they) shall be accompanied with copies of certificates

of accreditation from the national or an international certification body.

7.5.9.5 Meter Life test certification for lifetime of 15 years from an accredited laboratory for

the type of meters offered is a requirement. Life Test Cetrification shall be submitted.

7.5.9.6 The Tenderer shall complete clearly, all the clauses in both columns of the schedule in

Appendix D. This shall form the basis of evaluation of the submitted tender. Failure to

complete this appendix shall render the tender non-responsive. The tenderers shall

indicate the details of their offer where it is different from these requirements. Where

the requirement is the same, they shall indicate what is offered. Insertions such as

“noted”, “agreed” etc. shall be considered as non-responsive where a specific response

is called for.

7.5.9.7 The manufacturer shall provide proof of conformance to the following International

standards:

a) ISO 9001 (2008) standard

b) ISO 14001 (2004) standard

c) ISO 17025 (2005) standard



61 of 157

7.5.9.8 The manufacturer shall provide a list of at least three previous utilities outside the

country of manufacture to which the concentrator being offered has been supplied

including addresses and contact person(s) of the utilities.

7.5.9.9 The tenderer shall give proof that the number of Data Concentrators sold and installed

in utilities outside the country of manufacture over a period of last 5 years shall not be

less than 1,000. The addresses and contact person(s) shall be provided with the tender

to facilitate confirmation of this information by the procuring entity.

7.5.10 INFORMATION AND WARRANTY (IN CASE OF TENDER AWARD)

7.5.10.1 Drawings and technical details shall be submitted to KP for approval before

manufacture of the concentrators commences. KP undertakes to submit their

comments or approval for the drawings within three weeks of receiving the draft

copies.

7.5.10.2 Original software, software manuals and operation manuals shall be submitted in 3

copies. Description leaflets (brochures) shall be submitted in copies of 100.

7.5.10.3 The concentrator shall have a warranty against any defects, which may develop due to

faulty material, calibration, transportation or workmanship for a period of thirty-six

months from the date of delivery. All defective concentrators shall be replaced at the

supplier’s cost.

7.5.10.4 The manufacturer shall make a commitment in writing on the availability of essential

spares and other consumables for the certified life of the concentrator.

7.5.10.5 KP Engineers will inspect concentrator-manufacturing facilities intending to supply

concentrators to the company for the first time at no extra cost, except the cost of the

engineers’ transportation to the nearest major airport. Such inspection shall not in any

way prejudice the purchaser’s rights and privileges.

7.5.10.6 The manufacturer shall meet the full costs of two Engineers, for concentrator

inspection and acceptance testing at the manufacturer's facility, except the cost of

Engineers' transportation from Kenya to the nearest major airport. The factory

inspection and factory acceptance tests shall run for duration of three (3) working days

each.

7.5.10.7 After delivery of concentrators to KP, the manufacturer shall conduct training for at

least 3 days for twenty people in Nairobi, Kenya. The training shall cover and not be

limited to:

a) Concentrator features;

b) Concentrator installation;

c) Concentrator software;



62 of 157

d) Concentrator communication features, etc.

7.5.10.8 The manufacturer shall meet the cost of the training described in clause (5.7).

7.5.10.9 The concentrators shall be packaged in such a manner as to minimize damage and

entry of moisture during transportation and handling.

7.5.10.10 The concentrators shall be packed in suitable groups and/or batches with consecutive

serial numbers provided by KP.

7.5.10.11 Where test and/or calibration certificates/reports are issued by a laboratory other than

the International/National Certification Authority, a copy of accreditation certificate

shall be attached together with the tender documents.

7.5.10.12 The manufacturer shall provide current e-mail addresses, fax and telephone numbers

of the national/international testing/calibration laboratories and concentrator

certification bodies to facilitate confirmation of the submitted test reports &

certificates.



63 of 157

8.0 ADDITIONAL FUNCTIONS

8.1 COMMUNICATION WITH THE METER

Meter shall have communication between the meter and different devices (hand

terminals, communication modules, data concentrators, etc.). Communication shall

be executed via interfaces given in the following list, with the usage of data model,

application layer and identification structure according to international standards.

o Optical port (IR Port), Communication protocol: DLMS/COSEM Physical

level: IEC 62056-21 or ANSI C.18

Optional :

o Electricity interface № 1 RS-485, Communication protocol: DLMS/COSEM

Physical level: RS-485

o Electricity interface № 2 RS-232, Communication protocol: DLMS/COSEM

Physical level: RS-232

o Electricity interface № 3 Ethernet, Communication protocol: TCP/IP

Physical level: RJ-45

Communication part of the meter is executed to enable simultaneous meter

communication via all meter interfaces, without their mutual disturbance,

especially without impact on the measuring part of the meter.

The communication shall be plug in module, hot swappable through the 3G

networks or PLC.

8.2 PROFILES OF METERED AND REGISTERED VALUES

Meter shall have the possibility to record at least 1 profile of energy or electrical

(Voltage, Current) values. Each profile must support the recording of at least 4

channels for single phase meters and 8 selected channels for three phase meter.

Change of all recordings and registering parameters of metering and registered

values may be done locally (via the optical port) and remotely (via external

communication).

Initially, meter records the following profiles:

o KWH Profile

o KVARH (Lag) – Polyphase only

o Voltage Profile – 1 for single phase, 3 for polyphase

Meter records and registers the load profile (mean active power value). Integration

period is initially 15 minutes. The corresponding time stamp is recorded in the load

profile with the corresponding block of registered active power value.



64 of 157

Total capacity for load profile storage shall enable memorizing of at least 45 days

of power metering records.

8.2.1 Load Profile

Meter records and registers the load profile (mean active power value). Integration

period is initially 15 minutes. The corresponding time stamp is recorded in the load

profile with the corresponding block of registered active power value.

8.2.2 Event Log

Meter memorizes events related to metering, adjustment and handling into the

special memory registers. A record in the memory is generated for each event

memorizing the type of event, time stamp and meter status when the event occurred.

Meter registers at least 500 events.

Events recorded in special event logs, (events related to voltage quality, metering

integrity, consumption management, alerts, etc.) are not recorded in the standard

Event Log.

Event Log is not erasable via any external intervention.

8.3 LIMITING OF PERMITTED MAXIMUM POWER

Self Contained Meter must be able:

o Set the maximum current limit allowed to the custumer

o Set the time allowed to exceeded maximum current limit (Tolerance Time)

o Set the duration time for reconnection (Penalty Time)

o Disconnect the costumer if the maximum current limit and tolerance time is

exceeded

o Reconnect the costumer if the penalty time has passed

o Register all activities in the memory

Values of power limit, permitted overload time and penalty time may be set

remotely and locally.

8.4 REMOTE DISCONNECTION/CONNECTION OF THE

CUSTOMER (ELECTRICITY SUPPLY INTERRUPTION)

Switching module for remote disconnection/connection of the customer shall be

activated via a MCC command or automatically from the MRS programmable

function.



65 of 157

8.5 SWITCHING MODULE (BISTABILE SWITCH)

Switching module is executed as a bitable switch, i.e. it has two stabile states, while

the change of the state is performed only as the result of command for

disconnection/connection and it is executed as an integral part of the meter.

Electrical and mechanical specifications of the switching module are in accordance

with IEC 62055-31 or ANSI equivalent, where maximum switching current is equal

to the maximum meter current or higher.

Switching module shall perform at least 10,000 position changes without the need

for any maintenance.

Switching shall be done only in the phase. Neutral is never disconnected.

Meter manufacturer shall submit a corresponding document (test certificates)

proving that it has met indicated standards in the switching module.

Switch reclosing is programmable.

8.5.1 Conditional Switch Reclosing Operation Regime

After receiving instructions for reconnection, it is necessary to a second command

to confirm switch reclosing.

8.5.2 Automatic Switch Reclosing Operation Regime

After receiving instructions for reconnection, the switch is automatically

reconnected.

8.6 TIME OF USE (TOU)

Allow totalized register of energy in different time blocks.

8.7 FIXED TIME OF USE (TOU)

Meter allows programmable pre-determine time blocks (up to 4)

8.8 ELECTRICITY METERING QUALITY

8.8.1 Supply Interruption Registration

Meter registers supply interruptions in accordance with IEC 50160 or ANSI

equivalent.

Meter registers the number and total duration of short-term supply interruptions

(supply interruptions shorter than 1 minutes) and long-term supply interruptions

(supply interruptions longer than 1 minutes), recorded in the electricity quality log.

Meter records corresponding codes into an electricity quality log for each supply

interruption.

Meters must time stamp all power up and power down events.



66 of 157

8.9 DATA SECURITY

Locally accessed data must be protected by access right verification with at least

three access levels.

The first protection level ensure protection against unauthorized data reading via

the optical port and it is realized through a software package installed on the

handheld device/laptop, presenting it to the meter, enabling data transfer and

reading.

The second level of protection ensures protection against unauthorized changes in

the meter parameter set. It is also realized through a software package installed on

handheld device/laptop, depending on the user type, as well as password

verification; it enables the transfer of certain parameter changes to the meter.

Parameters that can be changed at this level are time and tariff programmed.

The third protection level ensures protection against unauthorized change of meter

firmware, or other meter parameters. These actions on the meter are enabled after

verification of user type of software package installed on the handheld

device/laptop, as well as meter password.

Each change of parameters/firmware shall be registered in the standard Event Log

with the date and time of change.

Registers storing accounting data may not be changed.

Remote parameterization of the meter shall be enabled only after entering the

corresponding password, whereas, MCC software records permanently the data

about the user, time and type of action.

8.10 SELF-CHECK

Meter must have a self-check function implemented. The purpose of this function

is to verify proper execution of basic meter functions. The meter should determine

the type of service based on voltage and current vectors.

Meter performs a self - check during network connection, i.e. after every supply

restoration (power – up). In addition to this, self-check is mandatory during every

firmware upgrade.

Self – check is also executed upon the request of the authorized person, at the point

of delivery itself via handheld devices.

Self – check verifies the following:

o Memory integrity of the meter

o Meter statuses and alarms

o Meter display

o Battery status



67 of 157

In addition to these, the following checks may be performed: connection check

towards external communication module, voltage presence in all phases, etc.

Self-check results are entered into the Event Log.



68 of 157

9.0 PARTICULAR SPECIFICATION

FOR

METER DATA MANAGEMENT SYSTEM (MDMS)



69 of 157

FOREWORD

This specification has been prepared by the Energy Management, Standards and IT departments

of the Kenya Power and Lighting Company Limited and lays down requirements for a Meter Data

Management System. It is intended for design, supply and installation of a Meter Data

Management System for Revenue Protection.

INTRODUCTION

This document describes the requirements of a Metering Data Management System (MDMS) for

the Kenya Power & Lighting Company Limited (KPLC).

The purpose of the document is to familiarize the MDMS supplier with the requirements for all

System components that should assist the supplier in the defining of wholesome functional

requirements of the MDMS. The key implementation objective of the System is Revenue

protection. The goal is to have a single integrated and Centralized Solution that groups all

acquisition and management of Meter Data, avoiding the risk of having multiple systems

deployed.

9.1 SCOPE

This specification applies to design, supply and installation of a newly manufactured, Meter Data

Management System for revenue protection and covers the following:

(a) Designing, supplying and installing a MDM System including hardware and software.

(b) Connecting and integrating the metering data from existing Head End Systems (HES)

to MDM System.

(c) Migrating the existing metering data between Integrated Customer Management

Information System (CMIS) and MDM System.

(d) Interaction and data exchange between MDM System and other applications (CRM,

GIS, SCADA, etc)

(e) Configuration and building of the database for MDM System

(f) Testing and commissioning the MDM System

(g) Implementation of the System Acceptance Tests

(h) Provide training service to the KPLC staff



IEC 61968-9: Application integration at electric utilities – System Interfaces for

distribution management – Part 9: Interface for meter reading and control

IEC 62056-46:2006: Electricity Metering - Data Exchange for meter reading, tariff and load

control – Part 46: Data link layer using HDLC Protocol



70 of 157


control – Part 53: COSEM Application Layer


control – Part 61: OBIS object identification system


control – Part 62: Interface Classes


The definitions given in the above reference standards apply.

AMI Advanced Metering Infrastructure AMR Automated Meter Reading CMIS Customer Management Information System CRM Customer Relationship Management HES Head End System IEC International Electro-technical Commission IMS Incident Management System IP Internet Protocol ISO International Organization for Standardization KPLC Kenya Power & Lighting Company Limited LAN Local Area Network MDMS Metering Data Management System. MCC Metering Control Centre POSN Point of Service Number

SCADA Supervisory Control and Data Acquisition TOU Time of Use

WAN WAN Wide Area Network

9.4 Operating Conditions

9.4.1 The MDMS hardware shall be suitable for operation in tropical climate where

temperatures vary from -1 to 50 degrees Celsius; relative humidity reaching 90% and

operating altitude ranging from sea level to 2200 m above sea level.



71 of 157

9.5 Design and Construction

9.5.1 The MDM System shall provide a joint infrastructure for data receipt on metered

consumption from the implemented AMI system within KPLC.

9.5.2 The MDMS shall potentially calculate consumed electricity, preserve and manage data,

and also provide access to subject data to all interested parties.

9.5.3 The use of appropriate middleware will enable the connection of the MDM System with

other business systems.

9.5.4 MDM system is anticipated to use the available networksfor connection with all entities

within KPLC.

9.6 Functional Requirements

The MDMS shall support the following functions:

9.6.1 Data acceptance and upload on metered consumption and any other relevant data sent by

Head End System (HES).

9.6.2 Interaction and data exchange with other utilities systems such as SCADA, IMS, GIS,

CRM.

9.6.3 Data acceptance and upload on any data information sent by the Customer Management

Information System (CMIS)

9.6.4 Support web based interface for users

9.6.5 Generation of prepayment tokens and onward transmission to the smart meter

9.6.6 Validation, editing and estimation of received meter data. All functionalities related to

validation, editing and estimation (VEE) should be centralized. MDM system shall

initially be filled with all necessary data (identifiers of points of services of all

customers), in order to enable the performance of VEE analysis of connected AMR

system.

9.7 Data storage, management and maintenance

9.7.1 Scalability in terms of full integration with other Information Systems

9.7.2 Revision of changed data

9.7.2.1 Security in access management of all functions and data

9.7.2.2 Calculation of consumed electricity for each point of delivery based on different price

structures, including hourly and other specified tariff rate periods.

9.7.2.3 Data based on the sequence defined in advance or on request

9.7.2.4 Receive and manage information to support exchange between points of services,

advanced meters, electric utility and interested third parties.

9.7.2.5 Data transfer from the MDM system to the Billing System, as well as to other information

subsystems within electric utility, shall be implemented through the (push) procedure

(according to sequence) or the (pull) procedure (on request)



72 of 157

9.7.2.6 KPLC shall retain the existing interface towards electricity customers.

9.7.2.7 15 minute / 30 minute / daily / monthly load profiles (LP) specified by other information

sub-stems should be used for VEE analysis needs, in cases when there is no sufficient

data.

9.7.2.8 MDM system database shall initially be filled with all necessary historical data

(identifiers of points of services of all customers), in order to enable the performance of

VEE analysis of connected AMI system.

9.7.2.9 During initial system filling with the necessary data, the electric utility shall submit all

its historical data, necessary to fill the MDM system database.

9.7.2.10 In initial implementation phase, MDM shall receive, process and manage data on metered

electricity consumption for all customers having advanced meters installed, read by AMI

system, while data obtained from electricity customers with classical meters, read via

handheld devices or manually will be received from the Electricity Billing System, for

the purpose of using the existing interface to migrate data.

9.8 Meter Data Management System – Technical Characteristics

9.8.1 The MDMS Software Requirement and Technical Characteristics

9.8.1.1 The MDMS shall be supplied complete with all the required applications, databases and

other items necessary for its perfect operation;

9.8.1.2 The contractor shall be solely responsible for the execution of all the installation services

and supply of all the equipment needed to make operable the Meter Data Management

System "MDMS" specified in this document.

9.8.1.3 The Contractor shall include all the applications and licenses to implement the MDMS,

with all the characteristics and features defined in this specification. The licenses Shall

be for the perpetual use of KPLC

9.8.1.4 The MDMS shall be scalable and will allow the use of multiple instances provided they

be integrated into a single database.

9.8.1.5 With the implementation of the MDMS, KPLC shall be able to remotely collect data from

the meters through the AMI Head End application (MRS) for the following functions:

(a) Billing

(b) Fraud detection

(c) Establish new tariff structures

(d) Improve the service quality index

(e) Eliminate operational costs of commercial procedures

(f) Control and management of customer loads

(g) Resources in the field (transformers, cables, among others)

(h) Improve network expansion planning.



73 of 157

9.8.1.6 KPLC shall remotely collect near real time and on demand meter readings.

9.8.1.7 KPLC to remotely “ping” any individual meter

9.8.1.8 The bidder shall include the supplies and activities necessary and mandatory for MDMS

to be fully operational, including the following:

(a) Supply of the system application software and of the hardware;

(b) Configuration of the database;

(c) Implementation of the system including assistance in the installation of hardware,

software and commissioning;

(d) Implementation of the System Acceptance Test;

(e) Provision of instruction manuals for the System, for Production and for Technical

Support;

(f) Provide training to KPLC team that will be responsible for the MDMS operation.

9.8.1.9 The Contractor shall provide a Maintenance and Support Agreement. It will include the

following activities:

(a) Implementation of the patches and corrections provided by the manufacturers of

the software that compose the environment of the HES

(b) Installation of new versions and releases, including their analysis, their suitability

for the use in the processes adopted by KPLC, their installation and follow up of

the support activities, object of the contracts of maintenance of the mentioned

software;

(c) Troubleshooting of hardware, software, network, and other operating systems for

servers and workstations that may be related with the MDMS;

(d) Help Desk support for the MDMS and any other components made available to

the users, which includes: Support, preparation of scripts, description and

systematic record of the problems, their immediate solution or deferral of these

problems to teams in charge of work, installation and configuration of the

associated software, creation and maintenance of users and evaluation of the

processes.

(e) Preferably, it should be an Oracle database or alternatively MS/SQL.

(f) Shall include customizable components: adaptors, interfaces, and web services

(g) All interfaces can be configured via a standard User Interface that includes

standard adaptors allowing rapid integration and intrinsic data validation to ensure

clean data loads.

(h) Can be configured to pull in, normalize, and store data from any number of utility

systems such as SCADA, GIS, IMS, CRM, Demand Analysis and Forecast and

various AMR head-end systems (HES), weather data systems and other legacy and

middleware systems.

(i) Effectively ingest, store and process meter reads, as it adds meters to its system,

creating valuable load profile data for each meter on the distribution system

(j) Obtain meter data from existing external systems like the Customer Information

System for a more effective grouping and reporting.



74 of 157

(k) Capacity to Perform Validation, Estimation, and Editing (VEE) on all meter reads,

to ensure “clean” data with no missing gaps. Standard tests to include: Missing

Values, Zero Values, Static Values, Negative Values, Spike Check, Sum Check,

Event/Status Check

9.8.1.10 Users also shall have the ability to create their own custom VEE rules.

9.8.1.11 Standard validation – Shall provide a set of standard validation which includes referential

integrity, data version control, missing interval, negative value, zero value, static value,

spike and sum checks, which can all be configured individually.

9.8.1.12 Historical load validation – Load validation for both interval data and consumption data:

9.8.1.13 The system shall be capable of making comparisons against load profile models that are

based on historical loads using the Interval Data.

9.8.1.14 The system shall be capable to compare against historical consumption, and adjustments

are made for weather and cycle length using the Consumption Data.

9.8.1.15 The system shall provide a tool, preferable graphic that allows the business analyst to

build and maintain custom logic sets for validation purposes. It shall allow the analyst to

build unlimited logic.

9.8.1.16 Estimation shall be provided for both interval data and consumption data.

9.8.1.17 For interval data, estimation shall be performed using a sophisticated algorithm, which

allows for weather-sensitive regression, day-type, and similar-day estimations.

9.8.1.18 For consumption data, the estimate is derived from historical usage factors, and default

values are used for the new meters.

9.8.1.19 The editing function shall have a tool for analysts can view meter data in graphs or

reports. Questionable data are highlighted with a suggested estimate, and the analyst can

choose to accept the estimate, accept raw data, or input an alternative estimate.

9.8.1.20 Enable user-friendly querying and reporting using standard reporting tools.

9.8.1.21 The MDM shall support a role-based security model.

9.8.1.22 The MDM shall have a powerful scheduling, archiving, and maintenance administration

tools, robust task monitoring and error messaging.

9.8.1.23 The MDM shall Supports a role-based security model.

9.8.1.24 The System shall provide a powerful analytic tool to generate a list of suspicious accounts

or meters that require further field investigation by the revenue protection team.

9.8.1.25 The MDMS software shall allow standard validation tests; examining the results of

various combinations of validation tests provides the first level in identifying potential

energy theft.

9.8.1.26 The software shall compare and analyze customer, meter and account data to identify

individual consumption patterns and detect suspect consumption behavior. A set of logic

tests shall be loaded during the implementation.



75 of 157

9.8.1.27 It shall also allow an easy way to query and chart the data to extract business intelligence.

Business Users Shall have the ability to aggregate meters into meaningful collections,

and then build logic tests against the meter data to look for outliers and meter anomalies.

9.8.1.28 Application that uses logic tests to identify theft of service and malfunctioning meters.

To combine individual validation tests to better pinpoint suspicious accounts.

9.8.1.29 Automatically schedule and run a series of standard theft detection and logic tests to

identify theft. These include:

(a) Outage & Restoration Event management – Provides features such as the

ability to manage events from AMI meters via the AMI Head End to the OMS.

Some filtering mechanism is needed between ‘raw’ AMI outage events and the

OMS. Some OMS provide this filtering.

(b) Transformer and circuit loading through aggregation of meters

(c) Meter Data Analysis – abnormalities such as zero usage, high/low readings,

theft alerts.

(d) Field Orders – filters events based on utility field orders. Can track orders,

provide data to generate orders.

(e) AMI Deployment management – Track inventory, deployment status,

produces a schedule for installation team for meters and network equipment.

(f) Supports customer web services and demand response and efficiency

programs.

(g) Supports soft and hard disconnects. A soft disconnect is a notice to utility when

KWH usage exceeds a set value for a certain period for a certain customer.

(h) Inactive Status

(i) Pending Disconnect

(j) Tamper Flag on

(k) Reverse Rotation flag on

(l) Meter changes

(m) Repeat customer

(n) Drop in Monthly Usage

(o) Zero Usage (systematic intervals)

(p) Reverse Spike in Usage

(q) Spike in Usage

(r) Load Factor > 100%

(s) High quantity On/Off condition

(t) Abnormal Voltage Variation

(u) Abnormal voltage condition

(v) Abnormal current condition

9.8.1.30 The MDMS shall allow combinations of logic tests to refine results as well as allow the

combination of meter read checks with CIS data elements to create further tests. These

include:

(a) Zero Monthly Consumption on Active Customers



76 of 157

(b) Consumption on Inactive Customers or Disconnects

(c) Seasonal Customer Use

(d) Decrease in monthly usage

(e) High load factors

(f) Allow business users to create their own logic tests and iterative workflows

to identify theft.

9.8.1.31 The MDM System shall identify in a unique way all points in which electricity delivery

to customers is executed.

9.8.1.32 Unique POSN shall be awarded by the Commercial System and it shall represent a unique

identifier serving for identification of the point on which calculation of consumed

electricity is performed, whereas, consumption information may be collected from

several advanced meters; i.e. Points of Service in which metering is executed via meters

or calculation aimed at the substitution of the missing measurements.

9.8.2 Data Exchange between MDM System and Other Systems

9.8.2.1 Data transfer request should be executed consistently to and from the MDM System.

Data exchange between the MDM System and other systems include:

(a) Meter Data from Head End Systems (HES)

(b) Data (customer information, billing) from Customer Management Information

System (CMIS)

(c) Data exchange with other utility applications such as GIS, IMS, CRM, SCADA

(d) Information related to tariffs and price structures

(e) Data on network resources on which Points Of Service (POS) have been

implemented

9.8.3 Data Exchange between MDMS and HES

9.8.3.1 The MDMS shall be integrated with the HES(s) so that the MDMS knows via which HES

device can be accessed.

9.8.3.2 The MDMS shall support logical and physical device names, and logical device names

to customers or contracts including all their histories.

9.8.3.3 MDM system should receive and process data on metered consumption. Received meter

data to be transferred to the MDM system from each advanced metering system include

the following:

a) Data on metered consumption for households, at daily level; data on

consumption should be transferred at the end of every day.

b) Data on metered consumption for households, at hourly level; data on

consumption should be transferred at the end of every day.



77 of 157

c) Data on metered consumption for Industrial and commercial Customers, at

daily level; data on consumption should be transferred at the end of every

day.

d) Data on metered consumption for industrial customers; data on

consumption should be transferred either as 15 or 60-minute data at the end

of the every day.

e) Interval Data

f) Operation parameters, immediately data such as all events and alarms of

meters, etc.

g) Data on the network resource where the meter is connected

9.8.3.4 It may be expected that the size of data transferred by metering control computer (MCC)

is restricted to the maximum number of entries. Transfer in terms of data size shall be

restricted in terms of prevention of too long or re-emission of data during the transfer of

large data amounts containing errors.

9.8.3.5 Moreover, it is necessary for all data transferred via this data transfer method to be related

to the same calendar day.

9.8.3.6 It is expected that all of these transferred parameters, at least contain identification

information in the heading defining data upload priority for MDM System for several

subordinated devices, when simultaneous data transfer is requested.

9.8.4 Data transfer priorities

9.8.4.1 Priority should be based on time and date of meter data creation.

9.8.4.2 MDM system should be capable to enable receipt and storage of all data on metered

consumption every day for the previous daily reading period. In order to have successful

data transmission, it is necessary for all process clocks on all computers within subject

subsystems to be synchronized in terms of time.

9.8.5 Manual entry

9.8.5.1 MDM system should provide the possibility of manual entry of meter data and other

data.

9.8.5.2 Manually entered meter data shall be in the same format as the ones automatically

entered into the MDM system by AMI system, whereby, the same validation of message

content is performed, as in the case of automatically transferred messages.

9.8.6 Data validation prior to (VEE) analysis

9.8.6.1 MDM system should perform, without restrictions, the data validations uploaded into

MDM system.

9.8.6.2 During every data transfer, verify if the combination ‘POSN/Meter ID’ is valid and is

concurrent with data in the Commercial or Billing System.

9.8.7 Data Exchange between the Billing or CMIS System and MDMS



78 of 157

9.8.7.1 The system should be capable to receive and process the following transfers:

(a) New unique POSN

(b) Data on the network resource where the meter is connected

(c) Request for meter data reading

(d) Request related to data for electricity calculation.

9.8.7.2 MDM system should receive and process incremental changes of data contained in Data

Base of Customer Information or Billing System. These contain changes in various

time-dependent attributes, related to points of sale of electricity.

9.8.7.3 The MDMS shall be able to receive the master data of the device from the CMIS and

create the meters in the inventory of the MDMS. Information on the meters is

synchronized with CMIS system.

9.8.8 Data Transmitted to the Billing System (CMIS)

9.8.8.1 The data on electricity accounting shall be transferred to the billing system under the

scheduler defined in advance.

9.8.8.2 In the definition of the requirements in terms of automated data transfer between

systems, it is necessary to anticipate the submission of grouped accounting data in

addition to standardized daily sequence and submission according to an accounting

period, in accordance with the operational technology of electric utility.

9.8.8.3 All data on electricity accounting to be submitted to the Billing System will be archived

by the System.

9.8.8.4 In the course of MDM system implementation phase, it should provide accounting data

to the Billing System for each metering point containing an advanced meter and

according to the criteria defined by the utility.

9.8.8.5 In case when there is no consumption at some metering point, the MDM system will

submit a zero value for metered consumption to Billing System. It should also be noted

that zero value represents a valid consumption reading which has undergone the

validation process and that it does not represent missing data.

9.8.9 Time Flow of Data Exchange

9.8.9.1 Meter data uploaded daily into the MDM system are mainly data from the previous

daily reading period.

9.8.9.2 When for any reason meter data from the previous day shall be uploaded from AMI

system, for the purpose of efficient data transfer, missing data are usually transferred

with high priority.

9.8.9.3 In cases, when instead of missing accounting data, estimated values are sent to Billing

System, it is possible to perform missing data transfer under lower priority.

9.8.10 Data Exchange between MDMS and Other Utility Applications



79 of 157

9.8.10.1 The Suppliers shall provide a solution to data exchange between the MDMS and other

utility applications such as SCADA, IMS, CRM, and GIS.

9.8.11 Data Exchange Methods

9.8.11.1 The MDMS shall have the ability to exchange data with systems being used or will be

developed in the future. The interface can be directly (access to the database directly)

or indirectly.

9.8.11.2 The communication with other applications shall be by the following methods:

(a) Exchange by file formats: Excel, Text.

(b) Send and receive data in XML format.

(c) API function, web service compliance with standard IEC61968. The MDMS

shall have passed EPRI IEC 61968-9 interoperability tests.

(d) The system shall be able to exchange data without restriction.

(e) Direct Database link

9.8.12 Report Generation Capabilities

9.8.12.1 MDM system should automatically generate reports, whereas, it is not only limited to:

a) Confirmation of successful load data transfer by AMI System

b) Confirmation of all data changes in the database occurring due to the addition,

migration or change in any of the metering points.

c) Reports related to meter data, unsuccessful meter data upload and unsuccessful

meter data receipt.

d) Difference between the meter identifier and the identifier of POSN

e) Lack of storage capacity in the database or on disk

f) Computer network problems

9.8.13 User Interface

9.8.13.1 The MDM system operator interface shall be web-based

9.8.13.2 MDM system shall have an internal graphical profile management enabling

supervision, change and management of processes and data within the system.

9.8.13.3 If data transfer is completed unsuccessfully, MDM system will send an internal

message, if necessary, it may notify AMI system operator about the failure.

9.8.14 Customer Self Care Portal

9.8.14.1 In addition to the web-based portal, the same features shall also be available on a mobile

app having the following capabilities:

a) Read smart meter

b) Charge smart meter



80 of 157

c) View remaining credit

d) Check and view consumption history

e) View company announcements and notifications

9.8.15 Data Management

9.8.15.1 Data Grouping

a) The MDM system shall group gathered meter data for the purposes of billing,

reporting and analysis.

b) Compared to accounting data, MDM system will group confirmed meter data

according to tariff periods, established on a daily basis.

9.8.15.2 Data Versions

a) MDM system should provide access to meter data by using the corresponding

data version. Every time meter data are altered, MDM system should update

only data related to that metering point and certain date of the year.

9.8.15.3 Data Monitoring

a) MDM system shall make such information available in the form supporting the

revision process, starting from the meter data receipt to the final generation of

accounting data. It is necessary to record meter data versions used for creation of

accounting data sent to Billing System, for keeping the records on change for

revision needs.

b) MDM system should enable the usage of real meter data during revision, when they

are available in the system, instead of data replaced or estimated, used for

generation of accounting reports. All newly arriving data will be processed through

VEE analysis.

9.8.15.4 Validation, Editing and Estimation (VEE)

a) All meter data received by MDM system will be subject to VEE analysis.

Automatic process of VEE analysis should be realized within MDM system. The

VEE analysis process performs analysis of current meter data for finding possible

anomalies, and in the case that anomalies are discovered, an error report is

generated, as well as the request for data correction within the MDM System with

the estimated value.

b) In the course of VEE analysis within MDM System, it is necessary to possess the

entire documents related to algorithm implementation used for the validation and

estimation of meter data, whereas, applied algorithms have to be explained on real

examples, with clearly defined data flows and definitions. The MDM System shall

use subject algorithms for future revisions and improvement of the analysis

procedure.

c) MDM System should continuously validate meter data in search for possible

anomalies. Various rules should be enabled within the MDM system for meter data



81 of 157

validation coming from certain metering points or groups of metering points.

Applied validation algorithms should not disturb the existing business processes

within electric utility.

d) MDM system should have automated estimations techniques to complete missing

or invalid data.

e) MDM system should enable meter data change by the MDM system operator.

Review and change of meter data shall be restricted to certain metering points, for

which an identity has been identified as the primary authority for such data.

f) VEE methods shall include:

Control the continuity of the data file (if the meter data stored in format file)

Too many cycles zero

Too many cycles outage

Comparison consumption with previous month

Comparing consumption with the same month of the previous year

The data values in the range defined by the user.

Peak power compared to the previous month.

Peak power compared to the same month of the previous year.

Gap detection

Maximum and Minimum

Status flag

Support define the basic functions for authentication data (+, -, *, /

mathematical functions such as square root, log, sin …etc.)

Allows creation of formulas calculated based on the basic functions.

9.8.15.5 The authentication data should be the administrator configured based on existing law.

Data should be authenticated automatically after storage.

9.8.15.6 Non-plausible value does not need to be replaced automatically. The replacement

value can be estimated linearly between the non-plausible value immediately before

and after the value of the time series. It is also possible to use historical values or

values from the other meter.

9.8.15.7 Editing data shall include the display of data in tabular and graphs. Any type of editing

data shall be tracked.

9.8.16 Functional Requirements in Terms of Data Storage

9.8.16.1 Reference Data



82 of 157

a) MDM system shall receive and process incremental changes of metering point

data.

b) KPLC will be responsible for providing data on metering points, meters,

network topology, customer data, as well as other reference data, for the purpose

of their full synchronization.

9.8.16.2 Meter Data

MDM system shall be capable to receive notifications on the addition of the new

metering point, new meter (either classic or advanced), meter dismantling, as well as

change of information related to the metering point by any utility system.

9.8.16.3 Archive Data and Data Restoration

a) An archiving procedure should be implemented enabling efficient data storage

for the time of at least 6 years, and subsequent transfer to storage media

providing permanent storage.

b) An archiving procedure should be implemented enabling efficient data storage

for the time of at least 5 years, and subsequent transfer to storage media

providing permanent storage

9.8.16.4 Historical Data

a) MDM system should be able to store data for on-line availability. In addition to

this, MDM system has to be able to store data for off-line availability, for

providing historical reserve. MDM system should be able to provide all these

data for the purpose of submission to all interested parties.

b) On-line availability of meter data and ancillary accounting data should be

provided for at least 24 months.

c) Off-line availability will primarily be used for the purpose of revision, but also

for historical analysis of consumption trends.

9.8.16.5 Database for MDMS

a) Preferably, it should be an Oracle database or alternatively MS/SQL.

b) Database should be able to store all meter data for a minimum time of five (5)

years. The database should support data warehouse functionality including the

concept of very large database (VLDB) like partitioning of tables, indexes, etc.

c) Database should have a multi-server concept that means that one database is able

to run on several independent servers.

d) Database shall support online backup and recovery.

e) Easy backup of the original data and meter data after processing.

f) The database should support a standby database on a different location to ensure

disaster tolerant systems. All changes made in the primary database should be



83 of 157

applied to a standby database on a different location. In case of a disaster the

standby database can be activated and will operate without data losses.

g) Capability to have near zero downtime for databases.

9.8.16.6 Meter Data Storage

a) Meter data from different sources should be stored in the database in order to

guarantee correct, repeatable and auditable results. Data from this storage should

be used for all other systems connected to the MDMS.

b) The MDMS shall store all kind of meter data like interval/register data, billing

values, events, electricity parameters including all their histories in a unified

format.

c) The meter data should be stored for at least five (5) years online.

d) The MDMS shall store also the historical values in case that the meter data

changes due to validation or recalculation.

e) The MDMS shall store for every meter and for every register the following

attributes:-

i) Timestamp valid from,

ii) Timestamp valid until,

iii) Raw value,

iv) Report value (after VEE),

v) Creation timestamp,

vi) User or process who has created this value (acquisition, validation, user

name, etc.).

f) The MDMS shall store cross sums where meter data calculation or aggregation

can be stored.

g) The data should be divided into several data segments in order to provide access

to certain data segments only.

9.8.16.7 Event and Alarm Processing

a) MDMS shall be responsible to store all kind of events and alarms and initiate

actions based on events and alarms.

b) Once the alarm is registered and passed to the MDMS appropriate and

predefined actions will be processed by the workforce management system of

the MDMS. This could be issue an inspection order for the meter maintenance,

notification in the CMIS system or others.

c) Every meter type and every HES will register different events with different

codes. This may result into a big set of possible events and alarms. The Supplier

shall define the events and the alarms that should be handled within the MDMS.



84 of 157

d) The MDMS shall have the capability to define translation tables for every meter

type or HES. This should unify the events in the MDMS and ensure that same

events will have the same codes. The MDMS shall be configurable in such a

way that for every event and alarm a pre-defined action will follow.

9.8.16.8 Security

a) Encryption

i) All data transfer between MDMS and other systems shall be encrypted.

ii) Secure Sockets Layer (SSL) Protocol should be used for IP based

connection. Secured sockets should be used for Web services.

iii) Data encryption for storage, backup.

b) Authentication

i) User management, Group users, roles of users and group users respectively.

ii) MDM system should implement a security procedure on all access levels

through the usage of users, groups of users, as well as their roles.

iii) User authentication by unique identification of the user with a username

and password. Without the valid combination, access to the application

should be denied.

iv) Create multiple user access priority level software / function / module /

different data areas.

v) Records should be kept about the users having system access, with

specification of privileges for each user, as well as system access records

(identification of successful and unsuccessful attempts).

vi) The user account is locked after a number of failed login attempts. The

number of login attempts is set by the administrator on system setup.

vii) When user privileges are changed, MDM system should register the

security level change, time of the change and who executed the change.

viii) Logging of all system events. All of the system events shall be stored in the

system according to the time period required by the user (e.g. 7 days, 30

days, 365 days, etc.) to serve as an audit trail. This data can be removed

manually or automatically by the administrator.

ix) Mobile administration software shall use certificates for to authenticate

field tools

9.9 MDMS HARDWARE

9.9.1 General requirements



85 of 157

9.9.1.1 The proposed system shall be designed for an open and scalable configuration, to

ensure inter- compatibility with other systems of KPLC, the future smooth expansion

as well as easy maintainability.

9.9.1.2 The proposed hardware configuration should be extended by adding either CPU

processors /memory boards / disks etc… in delivered units or additional units for

capacity extension.

9.9.1.3 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.

9.9.1.4 The hardware architecture shall be based on open system with a very high level of

operational security and safety.

9.9.1.5 All computer equipment shall be current models from main worldwide computer

manufacturers selected for efficient operation of a real-time system.

9.9.1.6 No proprietary hardware shall be accepted for servers and workstations.

9.9.1.7 The processors shall include facilities for orderly shutdown and resumption of

processor operation upon detection of power loss and subsequent resumption of

power.

9.9.1.8 Redundancy of equipment supporting critical functions is mandatory.

9.9.1.9 The hardware shall be connected to a LAN network. The system architecture shall

ensure fast communication between servers and workstations.

9.9.1.10 The KPLC prefers the utilization of commercially-available hardware (Commercial

Off-The-Shelf; COTS) for as many of the system components as possible.

9.9.1.11 In the field performance test and prior to the end of warranty period, the Supplier

shall have all hardware inspected and certified as acceptable for service under a

maintenance contract by the local service offices representing the equipment

manufacturers.

9.9.2 Form of Hardware

9.9.2.1 To the greatest extent possible, equipment shall be supplied as rack mounted units,

unless otherwise specified.

9.9.2.2 Cabinets housing the racks shall be so fitted to ensure that at least one third (1/2) of

the cabinet is left free and available to use for future growth.

9.9.2.3 The final distribution of hardware within the enclosures shall be subject to the review

and approval of the KPLC.

9.9.2.4 The supplied model of equipment shall have redundant power supplies.

9.9.2.5 The power supplies shall incorporate automatic voltage selection and hot swap

capability. In case of failure of one of the redundant power supplies, the other one

shall support the power needs for the whole equipment.



86 of 157

9.9.2.6 The hardware shall have a minimum of two (2) 1 GB speed Network Interface Cards

(NICs) with sufficient capacity for the supplied networks. The NICs shall be

configured in a team or redundant fashion to support no single point of failure

(NSPOF).

9.9.3 Servers

9.9.3.1 The Supplier shall provide the servers that capable of handling ten (10) million

metering points.

9.9.3.2 All the servers’ items (CPU, RAM, Hard disks…) shall be dimensioned to answer

the operational system performance required for data processing to ensure that the

metering data point will be updated in period of 3 hour for one time.

9.9.3.3 The data of the system will be updated online or the system shall support the multi-

tenant architecture.

9.9.3.4 The servers shall be able to process the data in memory.

9.9.3.5 The Servers shall be implemented according to the full redundancy concept for Main

system and Backup System and shall be equipped with sufficient hard disk capacity

and main memory to hold the complete data base and to perform basic data analysis,

verification, filter and calculation functions, etc… which are required for efficient

application server sharing.

9.9.3.6 The servers shall run in redundancy replication online mechanism. The servers shall

meet the growth rate of 10 percent (10%) one year.

9.9.3.7 Each server shall be mounted in rack space, power and heat dissipation.

9.9.3.8 Each Server, running preferably under Linux or Windows™ operating system, of a

redundant set of servers shall be connected to both LANs in order to cope with the

high availability requirements.

9.9.4 Work stations

9.9.4.1 The workstation shall include all hardware necessary to facilitate optimum user

interaction with the MDMS and for efficient operational control and monitoring of

the KPLC AMI.

9.9.4.2 A workstation shall consist of the following equipment:

(a) One or more color LCD (Liquid Crystal Display) monitors.

(b) One alphanumeric keyboard.

(c) One audible alarm.

(d) One cursor control device.

(e) Processor(s).

(f) Card Reader Equipment to support (Two Factor Authentication).

9.9.4.3 If the workstation is dedicated entirely to the GUI, it shall include sufficient

capacity to satisfy the user interface performance and capacity.

9.9.4.4 If the workstation also hosts non-GUI functionality, it shall also satisfy the capacity



87 of 157

and performance requirements for servers, including main and auxiliary memory

requirements.

9.9.4.5 All workstations shall include facilities to detect the loss of input power, execute

an orderly shutdown upon loss of input power, and automatically resume operation

when power is restored.

9.9.4.6 The workstations shall support the resolution of the monitors driven by it.

9.9.5 Monitors

9.9.5.1 Each monitor will be of the flat panel (TFT) type with the following characteristics:

(a) Best video image resolution of 2560 x 1600 pixels (minimum) or higher

resolution.

(b) Minimum screen diagonal measurement of thirty two (32) inches.

(c) Anti-glare screen coating.

(d) Pixel pitch in accordance with the Resolution.

(e) Minimum viewing angle of 160 degrees (horizontal and vertical)

(f) Minimum image brightness of 300 cd/m2.

(g) Image contrast ratio of 1000:1 (typical); 500:1 (minimum) or better than Pixel

response of 8 ms or less;

(h) Colour depth 16.7 million;

(i) Video inputs: VGA Analogue, using either standard 15-pin Sub-D or dual-

purpose DVI 24 pin connector or Digital using DVI-D or HDMI.

(j) All monitors shall have buttons for contrast and brightness adjustment.

9.9.6 Other Peripheral Devices

The Supplier shall supply any other peripheral devices or equipment normally

provided for operation, software support, and maintenance of the MDMS.

9.9.7 Power Supply System

a) KPLC shall provide power supply system that includes uninterruptible power

supply system (UPS) and standby diesel generator system.

b) The Supplier shall provide a sub-distribution board for the loads. All outlets

on the sub- distribution board shall be protected by Miniature Circuit Breakers

(MCBs) of suitable ratings. All MCBs shall have auxiliary contacts suitable

for signaling purposes; one contact to signal MCB open, the other to signal

MCB trip.

c) The Supplier shall provide the power cable for the loads.



88 of 157

9.9.8 Local and Wide Area Networks

9.9.8.1 LAN Network

KPLC is responsible for the supply of the LAN network

9.9.8.2 KPLC Corporate WAN

(i) The MDMS shall interface to the KPLC’s Corporate WAN and KPLC is

responsible for the supply of the Corporate WAN.

(ii) The Supplier shall be responsible for the connections from the MDMS to the

KPLC’ Corporate WAN.

(iii) The MDMS shall connect to the Corporate WAN via a firewall to be supplied by

the Supplier. This connection shall be done by means of an Ethernet interface using

Category 6 STP cabling or better.

9.9.8.3 Control Room Design

i) The KPLC shall take responsibility for the provision of the operating room. The

Supplier responsibilities shall include:

ii) The overall layout of the room

iii) Provide all of the detailed engineering drawings (electrical, general arrangement)

required for the nominated areas of the control center.

a. TESTING

i) Test Responsibilities

1. Supplier shall be responsible for all site tests with the exception of the Availability

Test. This responsibility shall include the conduct of the tests and all record keeping

and document production.

2. The KPLC shall support the site testing by supplying staff to monitor the tests. KPLC

expects that at least two Supplier staff will be on-site during these tests.

ii) Test Documents

1. Test plans, procedures, and records shall be provided by the Supplier for all tests to

ensure that each test is comprehensive and verifies the proper performance of MDMS

elements under test.

2. The test plans and test procedures shall emphasize the testing of each functional

requirement, checking error conditions, and documenting the simulation techniques

used. The test plans and test procedures shall be modular to allow individual test

segments to be repeated as necessary.

3. All test plans and test procedures (standard, modified standard, and custom functions)

shall be submitted to KPLC for approval and shall be subject to the approval process.



89 of 157

iii) Variance Recording and Resolution

1. The Supplier shall establish a process to record and track variances.

2. Variances shall be used to record system deficiencies, including but not limited to:

(a) Documentation deficiencies.

(b) Functional deficiencies.

(c) Performance deficiencies.

(d) Procedural deficiencies.

(e) Test deficiencies (as when the system cannot satisfactorily complete a test

procedure due to a problem with the test).

(f) Security deficiencies

3. The variance process shall produce reports of all variance information and shall

produce reports of subsets of the variances based on searches of the variance

parameters singly and in combination.

4. The variance recording and tracking system shall allow the on-demand production of

reports of all variance information. Variance recording and reporting shall be available

to the KPLC at all times via the Internet subject to secure access.

5. The Supplier shall periodically distribute a variance summary that lists for each

variance the report number, a brief overview of the variance, its category, and its

priority.

iv) Test Schedule

1. The Supplier shall provide a detailed system test schedule that is consistent with

project phasing.

2. The test schedule shall cover all aspects and components of the MDMS, including

backup modes of operation, full integrated operation and engineering.

3. The detailed test schedule shall be subject to KPLC approval.

4. All equipment documentation shall be completed, reviewed and approved by the

KPLC before any testing.

v) Routine Test

1. Routine Test shall be performed on equipment (hardware and software) as set out in

the scope of supply including testing items and standards.

2. The Supplier shall supply the Routine Test before shipping.

vi) Site Acceptance Test (SAT)

1. The testing and commissioning activities shall be conducted according to the Test Plan

and Test Procedure documents and shall cover, as a minimum:



90 of 157

a) Visual Test - Verification that the system includes all required components and is

properly configured. Visual inspection shall verify acceptable workmanship and

that all equipment, including cables and connectors, are appropriately labeled.

b) Hardware Diagnostic Test - Individual tests of all system hardware. These tests

shall consist of running standard hardware diagnostic programs, plus all special

diagnostic program used by the Supplier.

c) Communications and Interfacing Test - Verification of proper operation of all

data acquisition and data management functions.

d) Implementation and tests of all connections with the HES and CMIS.

e) Implementation and tests of the connections with KPLC existing systems such as

IMS, CRM, GIS and SCADA.

f) Functional Testing - Verification that all required software functional for the

system, including the user interface and database, are included in the system and

are functioning correctly.

i) Validation, Estimation and Editing functions (under actual or simulated

metering data points).

ii) Report generations capability

iii) Event and Alarm processing

g) Performance Testing - Verification that timing and response requirements are

satisfied, Tests shall include verification of:

i) Data exchange times (upload and download)

ii) Communication response times

iii) User interface function response times

iv) Completion time for each task

v) Restoration response time for convert from the Main System to the Backup

System

h) Security Testing - Verification of secure operation and system access including:

i) Communication error detection capabilities

ii) Safe system recovery with no erroneous data generation after system restarts.

iii) Protection against unauthorized access to the system and control functions

i) Environmental Testing - Verification that:

i) The system functions correctly overly the specified temperature range

ii) The accuracy of the data remain valid over the specified temperature range.

j) The test schedule shall allow sufficient time for verification or additional

unstructured testing by the KPLC. The KPLC shall be able to schedule unstructured

testing at any time, including during structured tests.



91 of 157

k) SAT will be conducted after the system has been installed after successful start-up

of the system. The system will be subjected to a subset of the functional

performance tests. The SAT will also include any type of testing that could not be

performed in the factory. Unstructured tests will be employed by KPLC, as

necessary, to verify overall system operation under field conditions. Any defects or

design errors discovered during the SAT shall be corrected by the Supplier.

l) After the system loaded (in-service) test procedures and plans to be conveyed to

the KPLC.

i) Availability Test

- A 1440-hour (sixty days) availability test shall be conducted for the

complete system after the completion of the SAT. The test shall be

performed under actual operating conditions.

- The Contractor shall have his qualified representatives available at all

times during the test, the purpose of which is to verify the reliability of

the system hardware and software. The Supplier shall bear the

responsibility for all corrective maintenance on the system; the KPLC,

however, may correct problems under the supervision of the Supplier.

The KPLC will be responsible for the system restart, notification to the

Supplier of service requirements, and preventive maintenance.

ii) Test criteria of the availability test

m) The system shall meet an availability of at least 99.99%. This availability shall be

calculated pro- rata for the actual duration of the test.

n) System availability shall be computed using the following formula:

System _ Availability Test_ time Down _ time

*100% Test _ time

o) No more than a total of two automatic or manual failovers or restarts of the central

processors shall be permitted during the test in order to recover from problems with

the system operation. The test shall be considered to have failed if this number is

exceeded.

iii) Test completion requirements

- If the guaranteed availability cannot be demonstrated at the end of 1440

hours, the Contractor may continue the test by moving the starting time

of the test forward and continuing the test until the 1440 consecutive

hours have been accumulated. If this exceeds 3 starting times or this

period exceeds 180 days, the system shall be deemed to have failed the

test.

- If the system fails the test, the Contractor shall make all needed

hardware and software corrections, and the test shall be rerun and

repeated until successful. The Supplier shall bear all correction and test



92 of 157

rerun costs. The taking over certificate shall not be granted until this

test is satisfactorily completed.

- On successful completion of the Availability Tests, the KPLC will take

over the system and the warranty period shall begin.

b. DOCUMENTATION

i) Documentation shall be provided for all equipment and functions provided by

the Supplier as part of this procurement.

ii) All documentation shall be in English and shall be subject to review and

approval by the KPLC to guarantee an acceptable level of written English is

delivered.

iii) The documentation shall describe MDMS, including all of its hardware,

software, and interfaces and shall cover functionality, testing, configuration,

installation, system start-up, operations, and maintenance and all other

deliverables. All equipment within the scope of supply shall include

documentation

iv) Documentation shall be available in the System and this is described

elsewhere. All documentation shall have an electronic copy and shall be

suitable for integration in a web portal. All documentation shall be structured

and have a common root with indexes per subject. This shall include original

equipment manufacturer (OEM) documents as well. System shall include

documentation control tools including search, version management and update

control.

v) The intent of the documentation and the ensuing review and approval process

is to ensure that it is of a standard and coverage so that when coupled with the

delivered Training will ensure that the KPLC will be self-sufficient in

maintenance of the System. Where it is deemed by the KPLC that the

documentation fails to fulfil this intent, the Supplier shall make good and shall

deliver additional documentation as directed by the KPLC.

c. TRAINING

i) The Supplier shall prepare and deliver a comprehensive training program on

the operation and maintenance of MDMS.

ii) Database, user interface and report maintenance training shall teach KPLC

personnel the skills needed for initial database and display construction and

verification and operational system maintenance and expansion.

iii) Software training shall equip KPLC personnel with the skills required for

MDMS maintenance and expansion and for the preparation and integration of

new functions.



93 of 157

iv) The training plan shall list each course to be taken, the dates for the course,

and the expected number of students to attend.

v) Training shall be scheduled to minimise the loss of knowledge through lack of

use. Training shall be scheduled so that there will not be long periods of time

between training and the use of the training.

vi) Local Training: The training plan shall not assume that all courses may be

delivered consecutively and shall allow for a reasonable break between courses

to allow KPLC staff to maintain existing duties. The schedule for the training

plan shall allow for multiple trips by the Supplier’s training staff to complete

the full set of training courses

vii) Training at the Manufacturer’s facilities (Overseas Training): The supplier

shall provide special training for MDMS on its system architecture, meter

protocols, security, communication and applications.

d. SHIPMENT, INSTALLATION AND

COMMISSIONING

This section sets out the sequence of these activities and expands on the

responsibilities of KPLC and the Supplier for these activities being applied to

each of the two phases of implementation

i) Authorization for Shipment

a. The Supplier shall inform KPLC of the final shipping arrangements, including

appropriate tracking numbers, once the shipment has occurred.

ii) Change Control

a. The Supplier shall establish and document a methodical process of change

control and configuration management for identification, control and reporting

of any changes to MDMS software, documentation, and hardware components

after shipment to KPLC site.

b. At the conclusion of the system installation task, all MDMS documentation

(including configuration drawings), test plans, results, and sample data shall be

updated to reflect the current state of the delivered systems.

c. The final test plans will be the basis for the testing component of the change

control procedures used to test and verify changes implemented either by the

Supplier or KPLC during the life of the system.

iii) System Installation

After the equipment is delivered to site and received by KPLC, MDMS installation

activities shall commence:

a) Movement and placement of the equipment.

b) Interconnection of the equipment, including interconnection with



94 of 157

previously delivered equipment.

c) The installation test.

d) The Supplier shall be responsible for these tasks, using labour provided

by itself.

e) The Supplier shall work with the KPLC to develop an optimal installation

sequence closer to the actual delivery date.

iv) Commissioning

a) Commissioning MDMS shall start immediately after the successful

completion of the respective installation test.

b) Prior to commencing the commissioning, the Supplier shall update all

databases within MDMS so that it is synchronised with the respective

existing systems in the field.

c) Commissioning activities shall include but are not limited to the

following:

Checking the on-site operation of the MDMS.

Verification of all MDMS interfaces with KPLC-provided data

sources and systems.

Verification of all MDMS interfaces with Supplier-provided data

sources and systems.

Validation of System databases and reports using real data. This

shall include

d) Verification of the correctness of database, a successful spot check is

needed subsequent to the re-synchronization activity.

e) Refining functionalities of all applications as they apply to MDMS.

f) Validation of the output of MDMS functions using field data.

g) Supplier shall be responsible for this activity, with support from the

KPLC.

h) The Supplier shall develop in detail to the satisfaction of the KPLC, the

tasks that will be part of the commissioning of the MDMS and the

commissioning of MDMS functions as an integrated system.



95 of 157

10 ADDITIONAL INFORMATION & GENERAL SCOPE OF WORKS

10.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 Particular Technical Specifications, in which the 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.

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, and installation

and commissioning as well as having the full responsibility for all works necessary to have the

AMI system complete.

The contractor shall be responsible for providing the communication services between the meter

and the MCC.

The supply, installation, configuration and commissioning of the routers, modems or

any other communication equipment will be responsibility of the contractor;

All the equipment to be installed at the customer premises shall be installed inside a

tamper proof Meter Box. The Supplier is responsible for all cost of the meter box

change.

The meter Box shall have the following features;

o Material for the body: Plastic. Fiber-glass Reinforced Plastics (GRP),

Polyethylene terephthalate, ABS, etc., or similar materials.

o The structure of the box should be very solid, with good seal performance

and resistant to dust and water.

o Fireproof, corrosion-proof, insulated

o Concealed hinges

o Mounting screws fitted from inside

o Adequate space for meter, modem and cut-outs

o Meter box should be capable to handle external modem antenna

o Suitable for installing three phase meter box



96 of 157

o One polycarbonate window for user to check electricity consumption value

on the door.

o For internal use must be IP54 Compliant

o For external use must be IP65 compliant

All equipment to be installed across the communication path (from meter to MCC), such

as routers, modems or any other must be installed by the supplier in a secure way, being

responsible for all cost associated with this installation.

Communication function with meters needs to support a fully automated retries

procedure.

Communication function has to offer online quality information such as signal/noise

ratio, attenuation and data loss statistics for all its components.

Meters, materials and other equipment recovered from the sites during installation shall be

transported to sites designated by the employer. The recovered equipment is to be taken over by

the Employer at these sites.

10.2 Overview of the Kenya Power and Lighting Metering infrastructure

10.2.1 Status of Advanced Metering Infrastructure (AMI)

The Kenya Power and Lighting company has implemented a “Revenue Protection Program

(RPP)” based on AMI technology aimed to sustainably protect the company’s revenues from

electricity sales to its 6,000 largest customers and another 10,000 customers on pilot projects.

However, the Company has not implemented the MCCs as permanent organizational units

responsible for revenue protection. Besides, the Meter Data Management (MDM )currently used

needs to be replaced by a new software package specifically designed to enable systematic and

effective monitoring of consumption for the purpose of revenue protection.

10.2.2 Technical characteristics of existing AMI system

Remarks

Communication link Meter to DCU/Central

Station

PLC, GPRS

Meter to Central Station GPRS

Make Hexing, Inhemeter,Star

Instrument

Hexing, inhemeter and Star

instruments(GPRS/PLC)

Hexing (GPRS)

Communication Protocol DLMS/ COSEM

Database Oracle

Models of existing meters Hexing

HXT 300

HXT 310

Star Instruments

DTSY 23S

DTSY 22S

Inhemeter



97 of 157

DDZ 1513

DTZ 1513

10.3 The Project Scope of works

i. Supply, installation and commissioning of Advanced Metering Infrastructure (AMI) for

revenue protection, comprising: (i) meters at fifty five thousand (55,000) customers’

premises; (ii) equipment for communication between meters and Metering Control Center

(MCC); (iii) software to manage remotely meters readings; (iv) Meter Data Management

software (MDMS) with all functionalities for revenue protection, including permanent

licenses to manage up to 1,000,000 metering points; (v) Metering Control Center

(hardware and software)

ii. Training of KPLC staff in the operation and maintenance of the AMI system

iii. Integration to the MDMS of 16,000 customers’ metering points with smart meters as

specified in 10.1.2.2 The bidder can choose between: (i) integrate the 16,000 existing smart

meters to the MDMS based exclusively on the information in 10.1.2.2 above (KPLC reject

any proposal requiring additional information to proceed with the integration); or (ii)

replace the existing Smart meters meters by others meeting the specifications.

iv. Provision of communication services during a (2) year guarantee period, starting after

commissioning of all the items in the scope of the AMI.

From the end of the guarantee period KPLC will contract separately maintenance services for

the MDMS and other components of the AMI system (with the contractor), as well as

communication services (with a mobile phone operator). Those post-guarantee services will be

covered by the company’s operations budget

The RPP will consist of the following main components:

1. Meter Control centres

Creation of one main MCC (Meter Control Centre) in Electricity house Nairobi for administration

of Advance metering Infrastructure. The other Metering control centres shall be located in the

regional headquarters (Nairobi, Nyeri, Mombasa, Kisumu, Eldoret and Nakuru) and will only

work for monitoring and analysing the data. The employer will provide the space, however the

contractor shall carryout the necessary modifications for the requirements of the MCC.

Operations of each MCC will be supported by a designated “Meter Data Management (MDM)”

software, designed to make possible the systematic monitoring of consumption of customers, and

the detection of any metering irregularities at the exact time that happens. The staff of MCC will

consist of experts that will be in charge of operating the MDM and there shall be a team of field

crew who will be inspecting and resolving anomalies detected by the MDMS system.

The MDMS shall be designed for a system sizing of 1 million metering data points.

2. Incorporation of existing 10,000 Smart meters on selected low voltage customers s and

6000 large power customers supplied medium and high voltages



98 of 157

The scope include integration of existing 6,000 smart meters for large power customers (supplied

at 433V, 11,000V 33,0000V, 66,000V and 132,000V) and another existing 10, 000 smart meters

for low voltage SME customers to the new Metering Control Centres (MCCs). The contractor

shall provide all the supplies and services to fully integrate the 16000 customers’ metering points

into the system and ensure all the functionalities and technical requirements defined in the bidding

documents are also met for those points. For that purpose, the contractor may use the existing

meters and communication devices or replace them with new ones to be supplied within the scope

of the contract.

3. Supply of 55,000 Smart Meters for customers in various parts of the country

The implementation of Advanced metering Infrastructure consisting; smart meters,

communication infrastructure, necessary enclosures, and integration to central MDMS for 55,000

new low voltage customers in various regions. The customers are distributed as follows;

Region Number of Customers

1 Nairobi North 9,220

2 Nairobi West 7,000

3 Nairobi South 8,000

4 Coast 6,500

5 Mt Kenya 6,260

6 South Nyanza 2,078

7 Central Rift 6,412

8 West Kenya 4,755

9 North Rift 3,500

10 North Eastern 1,275

Total 55,000

A more detailed table for distribution of customers is provided in Annex 3

10.4 Installations Works

The installation works shall cover the following tasks, but not limited to:

a) Installation of all metering enclosure equipment including earthing

b) Installation of Power cables to metering cabinet

c) Termination of Cables/Conductors from metering cabinet to customer

d) Installation of cable conduits

e) Cable trenches for underground cable where necessary.

f) Installation of underground cable

g) All required civil works in building to enable the cable installation to and from the

metering cabinets and to the customer such as wall / ceiling penetrations,

preparation of cable conduits (slots in walls) and closing of the penetrations.

Preferably, the existing cable conduits (slots) in the walls of the buildings shall be

used, only where this is not possible, new conduits (slots) shall be prepared.

KPLC will arrange for power outage to facilitate the works as necessary on request by the

contractor.



99 of 157

10.5 Training and FAT (factory acceptance tests)

10.5.1 MDMS and Equipment Training (in the country of manufacture) (RPP 408)

The manufacturer shall provide hands-on training on the smart meters and associated equipment

in the AMI system at the factory for ten (10) KPLC Engineers. The training shall cover and not

limited to the following areas:

a. Meter metrology and features;

b. Installation and Operation of the AMI system;

c. AMI Hardware and Software operation.

The training includes travel, accommodation and per diem for the 10 (ten) KPLC engineers as

well as all course material and other expenses acquired by the Contractor. The training shall be

held at the manufacturer’s Training facility. The training course shall have a minimum of 2 (two)

weeks duration.

10.5.2 Local Training (RPP 409)

The Employer shall be allowed to take part in installation, configuration and integration thus

taking part in a transfer of knowledge scheme. After delivery and installation of meters/ metering

equipment to KPLC, the manufacturer shall conduct training for at least 3 days for thirty people

in Nairobi, Kenya. The training shall cover and not be limited to:

(a) Revenue protection concept

(b) Meter metrology and features;

(c) Installation and Operation of the AMI system;

(d) AMI Hardware and Software operation;

The contractor shall also demonstrate to the field staff and management all features of the revenue

protection system before handing over the system.

10.6 Factory Acceptance Test (RPP 401)

Factory acceptance tests shall be carried out as prescribed in the technical specifications.

The Contractor shall arrange for three (3) participants from KPLC and the Project Manager to

witness tests of major equipment/systems listed below in the manufacturer’s plant. All routine

tests shall be carried out in the presence of the Employer’s representatives. The representatives

shall approve shipment of the equipment if they are satisfied that the requirements of the

specification are fully met.

The Contractor shall arrange and meet the full cost of the air tickets and local transportation

FAT shall be carried out for the following;

MDMS

Meters



100 of 157

FAT shall be carried out as prescribed in the particular technical specifications of the equipment.

The cost of per diem and accommodation shall be met by KPLC.

10.7 Site Acceptance testing

After the metering equipment has been installed on site, the supplier shall carry out pre-

commissioning tests on the metering systems under the supervision of KPLC engineers. Details

of site tests shall be agreed with KPLC and shall include:

a) All KPLC recommended tests on SMART meters

b) Visual checks of all equipment (for damage, leaks etc.).

c) Continuity of Cable Connections and Phasing tests

d) Insulation between Phases, Insulation to Earth tests

e) Testing of communication equipment and related accessories

f) All KPLC recommended tests on PTs & CTs

g) Tests on functionalities of Central system IT infrastructure and central data analysis

system

h) All other tests prescribed in the technical specifications

The supplier shall be responsible for carrying out required tests (with the exception of (a) above)

to confirm the correct operation of the metering solution

10.8 Test Equipment to be supplied (TS –101,102)

10.8.1 Test Equipment and Configuration tools to be supplied (TS –101,102)

Laptop computers: Five units set up with comprehensive software . The Laptops shall

be supplied with all the necessary accessories and ports and loaded with latest

operating system. The Laptops must be able to run all the meters and equipment

software’s supplied under the contract. The lap top specifications shall be approved

by the project manager.

Handheld (HHU) portable working standard

10.9 Final documentation

As built drawings: 5 paper copies delivered in binders

3 CD-ROM copy (all drawings in auto card )

1 set of transparencies

Operation and maintenance manuals: 2 copies per equipment

10.10 Site Offices (RPP 410)

At the location where the Contractor will establish his main site administration, an office for site

supervisors from the Project Manager with basic office furniture, internet, telephone and

access/use of fax and copier shall be provided by the contractor for the implementation period.



101 of 157

10.11 SECURITY FEATURES

Cyber Security (includes all KPLC AMI system components)

IDENTIFICATION All authorized users of AMI system components shall be uniquely identified to support individual accountability.

IDENTIFICATION AMI system components shall internally maintain the identity of all current active users.

IDENTIFICATION AMI system components shall restrict a User-ID to only one active session.

IDENTIFICATION All operations-related processes running on AMI system components shall be associated with the User-ID of the invoking user.

IDENTIFICATION

If a user-ID has not been used for a specified time interval, AMI system components shall be capable of disabling that User-ID. In addition, the security administrator shall have the capability of either automatically or manually disabling these User-IDs.

AUTHENTICATION AMI system components shall authenticate all users prior to initially allowing access.

AUTHENTICATION AMI system components shall ensure the confidentiality of all internally stored authentication data and protect it from access by unauthorized users.

AUTHENTICATION Reusable passwords transmitted across networks, including wireless or other unprotected channels, shall be encrypted.

AUTHENTICATION AMI system components shall preserve the confidentiality and integrity of stored authentication information such as passwords, PINs, and authentication tokens.

AUTHENTICATION

AMI system components shall perform the entire authentication procedure even if an invalid User-ID is entered. AMI system components shall not disclose which part of the authentication is incorrect and shall provide no information to the user other than "invalid attempt".

SYSTEM ACCESS CONTROL

AMI system components shall not allow access to users, processes, or other systems unless they are properly identified and authenticated.


All ports and interfaces of AMI system components that accept operations-related command inputs shall exercise access control. This includes ports that provide direct, dial-up, and data communications network access.


AMI system components shall not allow any session to be established via a port that is not designed to accept operations-related command inputs.


AMI system components shall not provide any default User-IDs that can permit unauthenticated system access.


AMI system components log-in procedure shall exit and end the session if the user authentication procedure is incorrectly performed a specified number of times.



102 of 157



AMI system components shall automatically disconnect a user and require re-authentication after a specified period of inactivity.


AMI system components shall end a session by means of a secure log-off procedure. The port shall be dropped immediately if the session is interrupted due to causes such as time-out, power failure, link disconnection, etc.


AMI system components shall be able to incorporate and support mechanics to grant or deny access to any user based on time-of-day, day-of-week, and calendar date.

RESOURCE ACCESS CONTROL

AMI system components shall assign and enforce levels of privilege to users, processes and other systems for restricting the use of resources.


Control of access to resources shall be based on authenticated user identification.


AMI system components shall provide a level of granularity such that for each resource controlled by AMI system components it shall be possible to: -Grant access rights to a single user, group of users, or a port. -Deny access rights to a single user, group of users, or a port.


AMI system components shall have the capability to screen access to specified resources and restrict a user's ability to perform certain designated operations on the basis of originating address/port.


Modification of the access rights to a resource shall be allowed only by the owner of that resource or by an appropriate security administrator.


AMI system components shall provide a mechanics to remove access rights to all resources for a user or a group of users.


AMI system components shall protect the data files and tables associated with the access control mechanics from unauthorized access.

DATA AND SYSTEM INTEGRITY

AMI system components shall support mechanics that ensure the integrity of the system and information stored, processed and transmitted by the system.


AMI system components shall have the capability to identify the original creator of any named or user-accessible NE resources such as data and processes.


AMI system components shall have the capability to identify the originator of any operations information received via communications networks.


AMI system components shall have the capability to protect the integrity of stored data by performing cryptographically-based integrity checks (e.g., message authentication code) and/or data updates.


AMI system components shall be designed and developed to protect data integrity by checking inputs for reasonable values.


A non-privileged user action, either deliberate or accidental, that requests AMI system components resources shall not cause denial of service of AMI system components to other users.



103 of 157



Mechanics shall be provided to allow AMI system components to recover from a failure or discontinuity without risk of compromising security.


AMI system components shall provide mechanics to preserve the integrity of data stored internally to the AMI system components.


AMI system components shall have the capability to verify the integrity of new software releases and subsequent patches.


AMI system components shall process security alarms in real-time based on indicated severity levels.

AUDIT AMI system components shall provide an audit log for investigating security relevant events.

AUDIT AMI system components shall generate logs that contain information about security relevant events. Items selected for recording shall be defined and selected by the security administrator.

AUDIT

AMI system components shall provide audit capabilities with user accountability for all significant events. The user-identification associated with any request or activity shall be maintained and passed on to any other connected systems so that the initiating user can be traceable for the lifetime of the request or activity.

AUDIT The audit log shall be protected from unauthorized access or destruction by means of access controls based on user and channel privileges.

AUDIT The audit log and audit control mechanics shall be protected from modification or destruction.

AUDIT The audit log and audit control mechanics shall survive system restarts by being maintained throughout a system restart.

AUDIT

Subject to selections made by the security administrator, the audit log shall minimally record information on the following events: -Changes to AMI system components security configuration. -Modifications of AMI system components software. -Invalid user authentication attempts. -Unauthorized attempts to access resources such as data, the password file, and transactions. -Changes to a user's security profile and attributes. For each recorded event, the audit log shall record the following: -Type of event. -Date and time of event. -User identification including associated terminal, port, network address, or communication device. -Names of the resources accessed. -Success or failure of the event.

AUDIT It shall not be possible to disable the audit log of actions taken by a security administrator.



104 of 157


AUDIT Authentication information such as passwords, PINs, and cryptographic keys shall not be recorded in the security log.

AUDIT AMI system components shall support audit analysis tools that can produce exception reports, summary reports, and detailed reports on specific data items, users, or communication facilities.

SECURITY ADMINISTRATION

AMI system components shall provide tools for managing security tasks for OAM&P systems by an authorized administrator.


AMI system components shall provide a mechanics for an authorized administrator to display all currently active users or software processes. These processes include both OAM&P and telecommunications service applications.


AMI system components shall provide a mechanics for an authorized administrator to be able to independently and selectively review the action of any one or more users, including privileged users, based on individual user identity.


AMI system components shall provide a mechanics to allow an authorized administrator to disable User-IDs after a specified period of time during which the user-ID has not been used.


AMI system components shall provide the capability to generate alarms for specifiable security events. The alarms shall be prioritized based on pre-determined criteria and routed to the security administrator. Only an authorized security administrator can deactivate an alarm.


The following security parameters shall be specifiable and adjustable by an authorized security administrator: -The period after which a password must be changed. -The interval during which an expired password shall be un-selectable as a new password by the same user. -The threshold on the number of incorrect login attempts which, when exceeded, would cause immediate notification. -The duration of channel lock-out that occurs when the threshold on the number of incorrect logins is exceeded. -A customized advisory warning banner that is displayed upon system entry regarding unauthorized use, and the possible consequences of violating the warning. -The duration of the inactivity time-out interval for an established session. -The access rights of a user to a resource. -The events that may trigger alarms (e.g., failed login attempts), the levels of alarms (e.g., critical, major, minor, etc.), the type of notification (e.g., bell and/or message), and the routing of the alarm (e.g., specific port). -Parameters for the mechanics that notifies users of the need to change passwords shall be specifiable and adjustable by an authorized administrator. This includes how far in advance users shall be notified, and the grace period for using an expired password.

DATA CONFIDENTIALITY

AMI system components shall support mechanics that ensure the confidentiality of sensitive information stored, processed and transmitted by the system.


The type of data items and structures whose confidentiality is protected shall be identified. For example, if data is transmitted, some identifier might accompany the transaction which would identify the key and related attributes needed by the receiving system.



105 of 157



The system shall have the capability of protecting the confidentiality of each individual message or selective fields of each message.


AMI system components shall support mechanics that ensure the confidentiality of communication information by encryption if the communication media cannot be protected by physical and administrative means.

NON-REPUDIATION AMI system components shall support mechanics that enable the identity of critical information to be proven (e.g., digital signatures for non-repudiation).

NON-REPUDIATION The system shall ensure non-repudiation of origin of important messages through the use of digital signatures.

NON-REPUDIATION The system shall provide non-repudiation of receipt of important messages by returning digitally signed receipt messages.

NON-REPUDIATION

The system shall be able to use cryptographic keys to protect the confidentiality of information, preserve its integrity, provide strong authentication, and support non-repudiation to enable the identity of the originator of information to be proven.

AVAILABILITY AMI system components shall support mechanics provide timely, reliable access to data and information services for authorized users.

AVAILABILITY

AMI system components shall have the capability to provide protection from attack through the use of techniques such as hardening resources by closing security gaps in operating systems, network configurations, limiting access to resources to authorized entities, and limiting an adversary's ability to manipulate or view the data flowing through and to those resources.

AVAILABILITY AMI system components shall have the capability to provide protection from unauthorized use by identifying and authenticating users of resources by providing access controls.

AVAILABILITY AMI system components shall have the capability to provide resistance to routine failures by providing for high reliability, equipment redundancy (high availability) and network connectivity to provide multiple routes.

Electric Meter Additional Security

Meter Programming Software

The software to program a meter shall have at least 3 levels of passwords with access levels that allow:

Full access to all functions including the development and modification of meter programs

Ability to program meters with existing programs

Read only access

Passwords Static meter passwords for remote access to a meter through a PC are acceptable but OTP (one time passwords) are strongly desired

Meter Optical Port

KPLC can choose to Enable, Disable, or Lock the optical port. The AMI Head End can enable or disable the optical port. A disabled or locked optical port will still provide calibration pulses if applicable. KPLC can lock the optical and open it with an optical port password.



106 of 157

10.12 List of Goods

Line

Item

No

Description of

Goods

Quantity Physical unit Final (Project Site)

Destination as specified

in BDS

1 Three Phase

Meters with

Communication

Equipment

10,826 Unit Project Site

Single Phase

Meters with

Communication

Equipment

44,174 unit Project Site

2 Meter

Enclosures and

associated

materials

55,000 Unit Project Site

3 Software for

Data Acquisition

1 Lot Project Site

4 Software for

Data

Management

1 Lot Project Site

5 Software

Licences

1 Lot Project site

6 Tools 1 Lot Project site

10.13 List of Related services Place where Services shall

be performed Service Description of Service Quantity Physical

Unit

1 Factory Acceptance tests 55,000 Service Factory

2 Meters Installation

(including Meter Box and

associated adaptation

works) for both Single

Phase and Three phase

55,000 Service Project Site

3 Local Meters

Transportation

1 Lot Service Project Site



107 of 157

Place where Services shall

be performed Service Description of Service Quantity Physical

Unit

4 Fixed Communication Cost

for 2 years.

Telecommunication rate for

bidding:

1 Service Project Site

5 Software Installation 1 Service Project Site

6 Equipment Maintenance

1 Service Final site

7 Software Maintenance 1 Service Project Site

8 Equipment Training 1 Service Project Site

9 MDMS Training 1 Service Factory

10 Local training 30 People Service Project site



108 of 157

ANNEX 1: TECHNICAL GAURANTEE SCHEDULE FOR SINGLE PHASE

SMART METERS

CLAUSE KENYA POWER REQUIREMENT MANUFACTURER’S COMPLIANCE/REMARKS

REFERENCE PAGE IN THE SUBMITTED DOCUMENTS

4.1 Operating conditions requirements

4.1.1 -1 to +60 0C (operational)

4.1.2 Humidity: Average annual reaching 95 % and altitude of up to 2,600m

4.1.3 Measurement of energy in tropical conditions

4.2 Design and Construction requirements

4.2.1 General

IEC 62052-11:2003 requirements given in 5.1 to 5.11

4.2.2 Meter cover, base and terminals

4.2.2.1 1 phase 2- wire configuration

4.2.2.2 L:N:N:L terminal configuration

4.2.2.3 Meter base and cover of non-metallic, non-hygroscopic, flame retardant, polished material

4.2.2.4 Clear glass or polycarbonate window

4.2.2.5 Degree of protection: At least IP 54

4.2.2.6 Material of Terminal block to pass tests of ISO 75

4.2.2.7 Front projection mounting

4.2.2.8 The meters shall have sealing provisions for the meter body, meter cover and terminal cover.

4.2.2.9 The meters shall be equipped with lockable/sealable push buttons where such buttons are used to change some meter parameters

4.2.2.10 Potential link of meter internal

4.2.2.11 Sealing provisions for terminal cover

4.2.2.12 Terminal cover requirement

4.2.2.13 Terminal holes to accommodate 8 mm diameter cables

4.2.2.14 Brass and Nickel plated terminal holes

4.2.3 Communications

4.2.3.1 LED indicators for testing and indication

4.2.3.2 Infra red optical port

4.2.3.3 Two way communication

4.2.3.4 DLMS/COSEM or equivalent compliant protocol



109 of 157

4.2.3.5 Wireless communication between meters and Home Area Network devices

4.2.3.6 PLC/ GPRS communication between meters and data concentrator

4.2.3.7 Scalable to other communication technologies

4.2.3.8 Provision for internal IP-based WAN/LAN option – fibre optics, Ethernet (WIFI) & GPRS

4.2.3.9 Hot swappable communication modules

4.2.3.10 Manual meter reading support

4.2.3.11 Last gasp mechanism

4.2.4 Meter display

4.2.4.1 LCD display with backlight

4.2.4.2 LCD display with at least 7 digits Nil decimals

4.2.4.3 LCD with at least 4-digit ID codes

4.2.4.4 Display of disconnector control unit status on LCD

4.2.4.5 Tampering conditions status on LCD

4.2.4.6 Display parameters configurable by software action

4.2.4.7 Provision for scrolling through display parameters

4.2.5 Consumer Interface Unit (CIU)

4.2.5.1 Ability to query the Meter by use of CIU or other devices

4.2.6 Real time clock & memory

4.2.6.1 Real-time clock quartz crystal oscillator controlled

4.2.6.2 Clock accuracy as per IEC62054-21

4.2.6.3 Remote and local clock synchronization

4.2.6.4 Clock back-up power supply

4.2.6.5 Lithium battery back-up shelf life 1 year

4.2.6.6 Non-volatile memory; data retention period equivalent to meter certified period or 15 years, whichever is longer


4.2.7.1 Remote load disconnection/reconnection

4.2.7.2 Automatic disconnection of whole customer load on exceeding set/authorized demand

4.2.7.3 Automatic disconnection of part(s) of customer load on exceeding set/authorized demand

4.2.7.4 The meters shall be configurable as post payment or prepayment meters remotely



110 of 157

4.2.7.5 The meters shall have provision for entering credit tokens when meters are operated in the prepayment mode.



b) Maximum switching current: 80 A

c) Maximum overload current: 96 A (30 min)

d) Maximum switching voltage: At least 265 V AC





g) Impulse strength (1.2/50 μS to IEC 62052-11):



4.2.7.7 Local or remote demand reset function


4.2.8.1 Measurement and display of TOU active energy

4.2.8.2 Measurement and display of TOU kW and/or kVA demand

4.2.8.3 Tariff register setting on a 24-hour period

4.2.8.4 Two seasons and four day types

4.2.8.5 At least forty (40) special days


4.2.9.1 Measurements & display of active, reactive and apparent energy in export/import modes

4.2.9.2 kWh as principal unit of measurement

4.2.9.3 The meters shall be capable of recording of active and reactive energy in all 4 quadrants with up to 4 tariffs

4.2.9.4 The meter shall have at least four (4) registers for energy

4.2.9.5 The meters shall be capable of measuring energy in security mode and also record reversed units

4.2.9.6 Meters shall have a facility to indicate reverse energy consumption

4.2.9.7 The meters shall have capability of closing end of billing period on any selected date of the month selectable by software

4.2.9.8 The meter’s billing registers shall NOT be re-settable to zero readings



111 of 157

4.2.9.9 The meters shall have at least twelve (12) billing historical data stored in memory and retrievable by software action


4.2.10.1 The meters shall be capable of measuring and displaying active, reactive and apparent demand consumption in both import and export modes

4.2.10.2 The meters shall display demand values and their time and date stamps

4.2.10.3 The meters shall measure demand correctly even when the phase rotation/sequence is incorrect

4.2.10.4 The meter shall have at least four (4) registers for demand

4.2.10.5 The meters shall have a capability of closing end of billing period on any selected date of the month selectable by software

4.2.10.6 The meters shall have at least twelve (12) billing historical data stored in memory and retrievable by software action. The current and billing/historical data shall be available on meter display for reading and billing purposes


4.2.11.1 The meters shall be capable of displaying instrumentation data namely instantaneous phase voltages and currents, phase angles, and power factor

4.2.11.2 The meters shall be capable of measuring and displaying instantaneous power (active, reactive and apparent)

4.2.11.3 The meters shall be capable of continuous display of the presence or absence of individual phase voltages


4.2.12.1 Multiple channels of energy, demand, voltage, current, etc profiling

4.2.12.2 Integration period, 1 min up to 60 mins


4.2.13.1 Collection and recording of PQ information – overcurrent, alarms, power outages, etc

4.2.13.2 Voltage sag and swell detection

4.2.13.3 THD event detection up to 10th harmonic


4.2.14.1 The meters shall be capable of event recording, which shall include but not be limited to the following:



112 of 157

1 Power ups and power downs with date and time stamp

2 Individual phase failure, with date and time stamps

3 Over- and under-voltages based on a pre-set threshold with date & time stamp

4 Battery voltage status (if applicable)

5 Memory status

6 Meter errors

7 Date and time of last programming/parameterization

8 Date and time of the last end of billing period

9 Prepayment events

10 Terminal cover removal even during power failure

11 Main meter cover removal even during power failure

12 Communications removal

13 Magnetic detection, at least 0.5 mT

14 Neutral Bypass

15 Incoming & outgoing lead interchange

4.2.14.2 The LCD shall display events that have occurred. The events displayed shall include but not be limited to the following:

1) Meter errors; 2) Phase failures; 3) Battery voltage status (if applicable) 4) Alarms; 5) Warning messages; 6) Prepayment mode; 7) Terminal cover removal 8) Communications removal; 9) Magnetic detection, at least 0.5 mT.

4.2.14.3 The meters shall have the relevant software for programming and reading out data

4.2.14.4 The meter software/program shall be capable of tracking user access to the meter

4.2.14.5 Access to meter parameters and programming information shall only be through user-level password(s)

4.2.14.6 The meters shall have sealing provisions for meter cover, terminal cover and any other opening whose access would compromise the meter security

4.2.14.7 Provision of a Laptop computer and two optical probes


4.3.1 Mains reference, 230 V, 50 Hz

4.3.2 2-wire system connection



113 of 157

4.3.3 Ib = 5 A; Imax ≥ 80 A

4.3.4 Power consumption as per IEC 62053-21:2003

4.3.5 Influence of short-time over-currents as per IEC 62053-21:2003

4.3.6 Influence of self-heating as per IEC 62053-21:2003

4.3.7 Ac voltage test as per IEC 62053-21:2003

4.3.8 EMC tests as per IEC 62053-21:2003


4.4.1 Accuracy class 1 as per IEC 62052-11:2003

4.4.2 Limits of errors due to variation of current as per IEC 62053-21:2003 and IEC 62053-23:2003

4.4.3 Limits of errors due to influence quantities as per IEC 62053-21:2003 and IEC 62053-23:2003

4.4.4 Test of starting and no-load current as per IEC 62053-21:2003 and IEC 62053-23:2003

4.4.5 Meter constant as per IEC 62053-21:2003 and IEC 62053-23:2003

4.4.6 Accuracy test conditions as per IEC 62053-21:2003 and IEC 62053-23:2003


4.5.1 Name plate marking requirements (indelibly marked in English and at least 4 mm height

(a) Manufacturer name

(b) Country of origin

(c) Model/Type of meter

(d) Meter serial number

(e) Bar code information

(f) “Property of K.P. & L. Co. Ltd” inscription

(g) Standard to which meter complies

(h) Year of manufacture

4.5.2 Indelible markings of connection diagram with phase sequence

4.5.3 Information on meter markings/wiring diagram/manuals/description leaflets

4.5.4 Type approval and calibration/test certificates

4.5.5 Compliance matrix requirements

4.5.6 Conformance to International standards:

a) ISO 9001(2008)

b) ISO 14001(2004)

c) ISO 17025(2005)

4.5.7 Meter type export details



114 of 157

ANNEX 2: TECHNICAL GAURANTEE SCHEDULE FOR THREE PHASE

SMART METERS

CLAUSE KENYA POWER REQUIREMENT MANUFACTURER’S

COMPLIANCE/REMARKS REFERENCE PAGE IN THE SUBMITTED DOCUMENTS


6.1.1 -1 to 60 0C (operational)

6.1.2 Humidity: Average annual reaching 90 % and altitude of up to 2,600m

6.2 Design and Construction requirements

6.2.1 General

IEC 62052-11:2003 requirements given in 2.2

6.2.2 Meter cover, base and terminals

6.2.2.1 3 phase 4- wire configuration

6.2.2.2 The meters shall be of British Standard (BS) 5685-foot print for standardized mounting for asymmetrical (BS) wiring

6.2.2.3 The meters shall be for front projection mounting.

6.2.2.4 The meters shall have terminals with bottom entry for cables and the arrangement shall be L1L1: L2L2: L3L3: NN for 3 phase 4-wire meters

6.2.2.5 The meter’s front cover may be of translucent material but shall have a window (clear glass or polycarbonate) for reading the display and for observation.

6.2.2.6 The meters shall have sealing provisions for the meter body, meter cover and terminal cover.

6.2.2.7 The meters shall be equipped with lockable/sealable push buttons where such buttons are used to change some meter parameters

6.2.2.8 The meter terminal cover shall be of the long type with cable entry knock-offs.

6.2.2.9 The meter potential links shall be inside the meter body and CAN ONLY be accessed by opening meter body cover



115 of 157



6.2.2.10 Terminal holes shall be of sufficient size to accommodate the cables of at least 10mm diameter and depth of 15mm

6.2.2.11 The meters terminal holes and screws shall be of moving cage type made of brass or nickel-plated brass for high strength and good conductivity

6.2.2.12 The meters shall have a sealing provision for terminal cover that is sealable with utility wire seals. The meter shall have terminal cover open detection. Once the terminal cover is opened, the load shall be disconnected.

6.2.2.13 Degree of protection IP54

6.2.2.16 The meter body dimensions shall not exceed: Height = 250mm; Width = 170mm; and Depth = 90 mm;

6.2.3 Communications

6.2.3.1 The meters shall have LED indicators for testing and indication of kWh and kvarh-measurement.

6.2.3.2 The meters shall be compliant with the DLMS/COSEM or equivalent communication protocol


6.2.3.4 The meters shall have provision for entering credit tokens when meters are operated in the prepayment mode

6.2.3.5 The meters shall have an optical and RS485 communication port, compliant to IEC62056-21 for accessing information stored inside the meter

6.2.3.6 The meters shall support two-way communication

6.2.3.7 The Meter shall be able to communicate with a remote central system using a plug in modem/module, through the



116 of 157



GSM/GPRS, dual band for operation in 3G networks.

6.2.3.8 The meter shall be designed with a plug and play communication module and shall support communication in complex environments by selecting the suitable communication module (GPRS/PLC/RF/Zigbee).

6.2.3.9 The communication module can be replaced at site without power off the meter.

6.2.3.10 The communication module shall support USSD, CSD communication

6.2.3.11 The meter shall support report to system when it is power on or off.

6.2.3.12 The meters shall have the relevant software for programming and reading out data.

6.2.3.13 The meter software/program shall be capable of tracking user access to the meter.

6.2.3.16 Access to meter parameters and programming information shall only be through user-level password(s).

6.2.3.15 A laptop computer and two optical probes, (see Appendix C for the Laptop computer specifications), for programming and down-loading the meter data shall be provided at no extra cost.

6.2.6 Meter display

6.2.6.1 LCD display with backlight

6.2.6.2 LCD display with at least 7 digits Nil decimals

6.2.6.3 LCD with at least 4-digit ID codes

6.2.6.4 Display of relay status on LCD

6.2.6.5 Tampering conditions status on LCD

6.2.6.6 Display parameters configurable by software action

6.2.6.7 Provision for scrolling through display parameters

6.2.8.8 Meters shall have provision for reading the meter at site even when mains power supply fails.

6.2.5 Real time clock & memory



117 of 157



6.2.5.1 Real-time clock quartz crystal oscillator controlled

6.2.5.2 Clock accuracy ≤ 0.5s as per IEC 62054-21

6.2.5.3 Remote and local clock synchronization

6.2.5.4 Configurable calendar type either as MMDDYY, DDMMYY or YYMMDD.

6.2.5.5 Clock back-up power supply

6.2.5.6 Lithium battery back-up shelf life 1 year

6.2.5.7 Non-volatile memory; data retention period equivalent to meter certified period or 15 years, whichever is longer


6.2.6.1 The meters shall have a load switch100A (relay) to enable disconnection and reconnection of customer load when the set/authorized demand is exceeded and on the expiry of credit balance when meters are operated on prepaid mode.

6.2.6.2 The load disconnect switches(relay) shall be fitted on both the Live and Neutral circuits. These relays shall operate simultaneously. In case there is an imbalance between the Live circuit and the Neutral circuit, the meter will take it as a tamper event and record it. The meter will measure on the higher current without disconnecting the loading switch.



b) Maximum switching current/phase: 100 A

c) Maximum overload current/phase: 120 A (30 min)

d) Maximum switching voltage/phase: 265 V AC




118 of 157






g) Impulse strength (1.2/50 μS to IEC 62052-11):



6.2.6.7 The meters shall detect significant reverse energy (SRE) when the line and load wires are swapped.

6.2.6.8 The meters shall continue to operate correctly and record in forward register during SRE detection.


6.2.7.1 Measurement and display of TOU active & reactive energy

6.2.7.2 Measurement and display of TOU kW & kVA demand

6.2.7.3 Tariff register setting on a 24-hour period

6.2.7.4 Two seasons and four day types

6.2.7.5 At least fifty (40) special days


6.2.8.1 Measurements & display of active, reactive and apparent energy in export/import modes

6.2.8.2 kWh as principal unit of measurement

6.2.8.3 Accurate energy measurements on incorrect phase rotation

6.2.8.4 The meters shall be capable of recording of active and reactive energy in all 4 quadrants with up to 4 tariffs

6.2.8.5 The meter shall have at least four (4) registers for energy

6.2.8.6 The meters shall be capable of measuring energy in security mode and also record reversed units

6.2.8.7 Meters shall have a facility to indicate reverse energy consumption

6.2.8.8 The meters shall have capability of closing end of billing period on any



119 of 157



selected date of the month selectable by software

6.2.8.9 The meter’s billing registers shall NOT be re-settable to zero readings

6.2.8.10 The meters shall have at least twelve (12) billing historical data stored in memory and retrievable by software action


6.2.9.1 The meters shall be capable of measuring and displaying active, reactive and apparent demand consumption in both import and export modes

6.2.9.2 The meters shall display demand values and their time and date stamps

6.2.9.3 The meters shall measure demand correctly even when the phase rotation/sequence is incorrect

6.2.9.4 The meter shall have at least four (4) registers for demand

6.2.9.5 The meters shall have a capability of closing end of billing period on any selected date of the month selectable by software

6.2.9.6 The meters shall have at least twelve (12) billing historical data stored in memory and retrievable by software action. The current and billing/historical data shall be available on meter display for reading and billing purposes


6.2.10.1 The meters shall be capable of displaying instrumentation data namely instantaneous phase voltages and currents, phase angles, and power factor

6.2.10.2 The meters shall be capable of measuring and displaying instantaneous power (active, reactive and apparent)

6.2.10.3 The meters shall be capable of measuring and displaying average



120 of 157



power factor for the current and the previous billing months.

6.2.10.6 The meters shall be capable of continuous display of the presence or absence of individual phase voltages


6.2.11.1 At least four (4) channels of energy and/or demand profiling

6.2.11.2 Integration period, 1 min up to 60 mins


6.2.12.1 The meters shall be capable of event recording, which shall include but not be limited to the following:

a) Power ups and power downs with date and time stamp

b) Individual phase failure, with date and time stamps

c) Over- and under-voltages based on a pre-set threshold with date & time stamp

d) Battery voltage status, if applicable

e) Memory status, if applicable.

f) Meter errors

g) Date and time of last programming/parameterization

h) Date and time of the last end of billing period.



k) Terminal cover removal

l) Main meter cover removal



o) Neutral Bypass

p) Incoming & outgoing lead interchange

6.2.13.2

The LCD shall display events that have occurred. The events displayed shall include but not be limited to the following: a) Meter errors; b) Phase failures; c) Battery voltage status, if applicable. d) Alarms;



121 of 157



e) Warning messages; f) Prepayment mode; g) Terminal cover removal h) Communications removal; i) Magnetic detection, at least 0.5 mT


6.3.1 Mains reference, 3 x 230/400 V, 50 Hz

6.3.2 Three phase 4-wire system connection

6.3.3 Ib = 10 A; Imax ≥ 100 A

6.3.4 Power consumption as per IEC 62053-21:2003

6.3.5 Influence of short-time over-currents as per IEC 62053-21:2003

6.3.6 Influence of self-heating as per IEC 62053-21:2003

6.3.7 Ac voltage test as per IEC 62053-21:2003

6.3.8 EMC tests as per IEC 62053-21:2003


6.6.1 Accuracy Class 1 as per IEC 62052-11:2003

6.6.2 Limits of errors due to variation of current as per 2.2 and 2.3

6.6.3 Limits of errors due to influence quantities as per 2.2 and 2.3

6.6.4 Test of starting and no-load current as per 2.2 and 2.3

6.6.5 Meter constant as per 2.2 and 2.3

6.6.6 Accuracy test conditions as per 2.2 and 2.3


6.5.1 Name plate marking requirements (indelibly marked in English and at least 4 mm height

(a) The standard transfer specification (STS) compliant serial number, in the preferred format known as a national meter number,

(b) The STS compliance logo,

(c) The inscription “Property of K.P. &. L. Co Ltd.”,

(d) Name or trade mark of the manufacturer;



122 of 157



(e) Country of origin;

(f) Type/model;

(g) Meter number;

(h) Barcode comprising of meter serial no without blank spaces;

(i) Standard(s) to which the meter complies;

(j) Year of manufacture

6.5.2 Indelible markings of connection diagram with phase sequence

6.5.3 Information on meter markings/wiring diagram/manuals/description leaflets

6.5.4 Type approval and calibration/test certificates

6.5.5 Compliance matrix requirements

6.5.6 The tenderer shall submit with the tender, a sample meter, meter software, operating manual(s), and an optical interface for interrogating the meter.

6.5.7 Conformance to International standards:

a) ISO 9001(2008)

b) ISO 14001(2004)

c) ISO 17025(2005)

6.5.8 The manufacturer shall provide a list of at least three previous utilities outside the country of manufacture to which the meter being offered has been supplied including addresses and contact person(s) of the utilities.

6.5.9 The tenderer shall give proof that the number of smart meters using GPRS technology (single and three phase) sold and installed in utilities outside the country of manufacture over a period of last 5 years shall not be less than 50,000 meters. The addresses and contact person(s) shall be provided with the tender to facilitate confirmation of this information by the procuring entity.

6.6 Drawings and technical details shall be submitted to KP for



123 of 157



approval before manufacture of the meters commences. KP undertakes to submit their comments or approval for the drawings within three weeks of receiving the draft copies.

6.7 Original software, software manuals and operation manuals shall be submitted in 3 copies. Description leaflets (brochures) shall be submitted in copies of 100 for each meter type.

6.8 The meter shall have a warranty against any defects, which may develop due to faulty material, calibration, transportation or workmanship for a period of twelve months from the date of delivery. All defective meters shall be replaced at the supplier’s cost.

6.9 KPLC Engineers will inspect meter-manufacturing facilities intending to supply meters to the company for the first time at no extra cost, excepting the cost of the engineers’ transportation to the nearest major airport. Such inspection shall not in any way prejudice the purchaser’s rights and privileges.

6.10 The Kenya power shall meet the full costs of two engineers, for meter inspection and acceptance testing at the manufacturer's facility, excepting the cost of engineers' transportation within country of manufacture. The factory inspection and factory acceptance tests shall run for duration of a minimum of three (3) working days each.

6.11 After delivery of meters to KPLC, the manufacturer shall conduct training for at least 3 days for twenty people in Nairobi, Kenya.



124 of 157



6.12 The manufacturer shall meet the cost of the training described in Clause 5.6

6.13 Bidders are advised that the Laws of Kenya require that the Kenya Bureau of Standards must approve any new meter being introduced in the country. To this end Bidders shall furnish the Bureau with 4 (four) samples of each meter type to be supplied. Bidders may communicate directly with the Kenya Bureau of Standards on this matter.

6.14 The meters shall be packaged in such a manner as to minimize damage and entry of moisture during transportation and handling.

6.15 The meters shall be packed in suitable groups and / or batches with consecutive serial numbers. The range of meter serial numbers including the barcode information for each meter shall be indicated on the outside of the packaging material.

6.16 The number of meters packaged in a group and/or batch for handling/lifting/carrying by an operator manually shall be such that their weight does not exceed 15 kg.



125 of 157

ANNEX 3: TECHNICAL GAURANTEE SCHEDULE FOR METER DATA

CONCENTRATORS



7.0 Requirements

In addition to the requirements in IEC standards highlighted in section 2 above, the smart meter data concentrators shall fulfill the following requirements.


7.1.1 The data concentrators shall be suitable for operation in tropical climate where temperatures may vary from -1 to +60 degrees Celsius.

7.1.2 Average annual relative humidity reaching 90 % and altitude of up to 2,600 m above sea level.

7.2 Design and construction requirements

7.2.1 The data concentrator cover shall be made of Polycarbonate material.

7.2.2 The data concentrators shall be for front projection mounting

7.2.3 The data concentrators shall conform to the degree of protection of least IP 54 as given in IEC 60529:1989 Degrees of protection provided by enclosures (IP Code) Amendment 1:1999.

7.2.4 The data concentrators shall have provision for sealing the terminal covers for power intake and interfaces, where such terminals may have negative effect on the operation of concentrators.

7.2.5 The data concentrators shall automatically discover meters, providing 100% accuracy on the assets. It should upload (tariff tables) and monitors and reports tampering. It should have broadcast capability to enable demand response and load shedding.

7.2.6 The concentrator shall have, depending on physical communication constraints, a ‘last gasp’ mechanism to inform the system of outages.




126 of 157



7.3.1 The concentrator shall be operated from main power with reference values of: - 3×57.7/100V to 230 V/400V, 3 x 1 (10) A at 50 Hz

7.3.2 Primary currents and voltages for the concentrator shall be programmable through the software thus allowing primary metering of Demand and Energy.

7.3.3 The concentrator shall be connectable as three phase four wire systems

7.3.4 The concentrator shall connection drawing which shall be printed on the terminal cover

7.3.5 The meter shall have reference standard currents of: - In= 1 A; I max = 10 A for the operating conditions stated in clause.

7.3.6 The meters Power consumption shall meet IEC 62053-22 7.1-7.

7.3.7 1Influence of short-time over-currents meet IEC 62053-22 7.1-7.4

7.3.8 Influence of self-heating meet IEC 62053-22 7.1-7.4

7.3.9 1AC voltage test meet IEC 62053-22 7.1-7.4

7.4

Accuracy requirements

Tests and test conditions given in 2.3 shall apply.

7.4.1 The concentrator’s accuracy shall be class 0.5S for active energy and class 2 for reactive energy measurements as per accuracy requirements given in 2.3 and 2.4 respectively.

7.4.2 Limits of errors due to variation of the current. The requirements of 2.3 and 2.4 apply

7.4.3 Limits of error due to influence quantities The requirements of 2.3 and 2.4 apply.


The requirements of 2.3 and 2.4 apply.



127 of 157




The requirement of 2.3 and 2.4 apply.


The requirements of 2.3 and 2.4 apply

7.5 Communication

7.5.1 General

a The concentrators shall have two -way down-link communication mode that supports communication with the meters by PLC system,

b In addition to the PLC system, the down-link communication mode of concentrators shall provide local concentrator maintenance facility through the following methods:

i) RS 232 or 485 interface;

iv) Infra-red optical interface as per IEC 62056-21 standard;

v) Ethernet.

c The concentrators shall have two -way up-link communication mode (WAN) that enables communication with Head End System (HES) by using the and GPRS 3G network and Gigabit Ethernet

d The concentrators shall support TCP/IP server and client mode

e The concentrators shall have facility for local and remote configuration to suit customers’ requirements.

F The concentrators shall have remote and local clock synchronization capability

G The concentrators shall have capability for local and remote firmware upgrade.

h Should offer the freedom to choose meters from various vendors and avoid being reliant on proprietary solutions from a single source.

i The data concentrator shall support meter data collection compliant with international standards IEC 62056 (DLMS) designed for interoperability with an open architecture.

j The concentrator shall have Internet Protocol (IP) routing capability

k The concentrator shall have remote and local web-based access for Configuration, monitoring and diagnostics.



128 of 157



l Should provide an IP security (IPSec) mechanism to ensure high-quality, interoperable, and cryptology-based security for communication processes.

m The concentrator shall include security mechanisms against theft and tamper with alerting features.

n The concentrator should support upto 1000 number of meters downstream

o Feeding phase monitor:The concentrator should be able to identify the feeding phase of each meter (for single-phase meters )and detect changing of feeding phase of meter via PLC communication

7.5.2 Down link communication

The data concentrators shall have a communication module that satisfies the requirements below:

Operation layer: IEC 62056 (DLMS)

Operation mode: Plug and play installation

Reading success rate: Minimum 99%

Communication distance: At least one thousand (1,000) metres

Maximum Response time (concentrator to meter): 10 seconds

Topology : Mesh network support

7.5.3 Up-link communication

The data concentrators shall have a two-way WAN communication to the Head End Systems through GPRS (mandatory), Electrical Ethernet (mandatory) and Optical Ethernet for interfacing to the WAN communication systems.

7.5.3.1 Up-link communication – GPRS

i GPRS modem that satisfies the requirements below:

ii Modem: pluggable 3G modem

iii Operating Band:WCDMA/HSDPA/HSUPA/HSPA+: Band 1, Band 8 M/GPRS/EDGE: 850 MHz/900 MHz/1800 MHz/1900 MHz

iv GPRS multi-slot class: 10

v SIM-card holder : Yes

vi SIM card interface : standard USIM (Class B and Class C)

vii Power supply for SIM card: 1.8 V and 3 V



129 of 157



viii SMA connector for the antenna : Yes

ix SMS capability: Yes

7.5.3.2 Up-link communication – Ethernet

1 Electrical Ethernet interface that satisfies the requirements below:

i Standard : 10Base T

ii Data rate : Minimum 10Mbps

iii Distance : Maximum 100m

iv Physical interface: RJ45 copper connector

2 Optical Ethernet interface that satisfies the requirements below

i. Standard : 100/1000Base-ZX /1000Base-LH

ii Optical Interface : 9/125 µm Single Mode

iii. Signal Wavelength : 1550 nm

iv. Distance : Up to 70 km

7.5.4 Data storage and logging

a) The data concentrators shall have a non-volatile memory capable of data storage and with long-term data retention for the certified life of the concentrator or ten (10) years, whichever is greater without an electrical supply being supplied to the concentrator.

b) The data concentrators shall be capable of profiling at least four channels of energy and/or demand for a period of at least six (6) months.

c) The load profile integration period shall be programmable between 1 minute up to a maximum of sixty (60) minutes.

d) The data concentrators shall have at least twelve (12) billing historical data stored in memory and retrievable by software action.

e) The concentrator shall be capable to log events and store upto 100 plus events.

f) The concentrator shall have configurable data logging intervals i;e minutes, hours and days.,

7.5.5 Electromagnetic Compatibility

A Dielectric strength: 4 kV, 50 Hz, (IEC 62052-11)

B Electrostatic discharge: 15 kV (IEC 61000-4-2)

C Burst: 4 kV (IEC 61000-4-4)

D Impulse voltage: 12kV, 1,2/50 μs (IEC 62052-11)

E Electromagnetic field: 10 V/m and 30 V/m (IEC 61000-4-3)

7.6 Instructions and marking requirements



130 of 157



7.6.1 In addition to IEC 62052-11:2003 nameplate requirements, each data concentrator shall be marked legibly and indelibly with the following information:

A Name or trade mark of the manufacturer;

B Country of origin;

C Type/model;

D Serial number up to ten digits;

E Barcode comprising of serial no;

F The inscription “Property of K.P. &. L. Co Ltd”;

G Standard(s) to which the concentrator complies;

h Year of manufacture.

7.6.2 Every concentrator shall be indelibly marked with diagrams of connections for which the concentrator is intended.

7.6.3 In addition, the following drawings and information shall be required with the tender: a)Concentrator drawing giving all the relevant dimensions; b)Wiring diagrams; c)Description leaflet; d)Service and operational manuals.

7.6.4 Copies of type approval certificate(s) with test and calibration results of the concentrator being offered obtained from an international or the national concentrator certification body shall be provided. If type approval certificate(s) is (are) from accredited concentrator certification laboratories (and not national or international body), then it (they) shall be accompanied with copies of certificates of accreditation from the national or an international certification body.

7.6.5 Meter Life test certification for a lifetime

of 15 years from an accredited laboratory

for the type of meters offered is a

requirement. Life Test Cetrification shall

be submitted.



131 of 157



7.6.6 The Tenderer shall complete clearly, all the clauses in both columns of the schedule in Appendix D. This shall form the basis of evaluation of the submitted tender. Failure to complete this appendix shall render the tender non-responsive. The tenderers shall indicate the details of their offer where it is different from these requirements. Where the requirement is the same, they shall indicate what is offered. Insertions such as “noted”, “agreed” etc. shall be considered as non-responsive where a specific response is called for.

7.6.7 The tenderer shall submit with the tender, a sample concentrator, concentrator software (if any), operating manual(s), and appropriate interface for interrogating the concentrator.

7.6.8 The manufacturer shall provide proof of conformance to the following International standards: ISO 9001 (2008) standard ISO 14001 (2004) standard ISO 17025 (2005) standard

7.6.9 The manufacturer shall provide a list of at least three previous utilities outside the country of manufacture to which the concentrator being offered has been supplied including addresses and contact person(s) of the utilities.

7.6.10 The tenderer shall give proof that the number of Data Concentrators sold and installed in utilities outside the country of manufacture over a period of last 5 years shall not be less than 1,000. The addresses and contact person(s) shall be provided with the tender to facilitate confirmation of this information by the procuring entity.

7.7 Information and warranty (In case of tender award)

7.7.1 Drawings and technical details shall be submitted to KP for approval before manufacture of the concentrators commences. KP undertakes to submit their comments or approval for the drawings within three weeks of receiving the draft copies.



132 of 157



7.7.2 Original software, software manuals and operation manuals shall be submitted in 3 copies. Description leaflets (brochures) shall be submitted in copies of 100.

7.7.3 The concentrator shall have a warranty against any defects, which may develop due to faulty material, calibration, transportation or workmanship for a period of thirty-six months from the date of delivery. All defective concentrators shall be replaced at the supplier’s cost.

7.7.4 The manufacturer shall make a commitment in writing on the availability of essential spares and other consumables for the certified life of the concentrator.

7.7.5 KP Engineers will inspect concentrator-manufacturing facilities intending to supply concentrators to the company for the first time at no extra cost, except the cost of the engineers’ transportation to the nearest major airport. Such inspection shall not in any way prejudice the purchaser’s rights and privileges.

7.7.6 KPLC shall meet the full costs of two Engineers, for concentrator inspection and acceptance testing at the manufacturer's facility, except the cost of Engineers' transportation from Kenya to the nearest major airport. The factory inspection and factory acceptance tests shall run for duration of three (3) working days each.

7.7.7 After delivery of concentrators to KP, the manufacturer shall conduct training for at least 3 days for twenty people in Nairobi, Kenya. The training shall cover and not be limited to:

1) Concentrator features; 2) Concentrator installation; 3) Concentrator software; 4) Concentrator communication

features, etc.

7.7.8 The manufacturer shall meet the cost of the training described above

7.7.9 The concentrators shall be packaged in such a manner as to minimize damage and entry of moisture during transportation and handling.



133 of 157



7.7.10 The concentrators shall be packed in suitable groups and/or batches with consecutive serial numbers provided by KP.

7.7.11 Where test and/or calibration certificates/reports are issued by a laboratory other than the International/National Certification Authority, a copy of accreditation certificate shall be attached together with the tender documents.

7.7.12 The manufacturer shall provide current e-mail addresses, fax and telephone numbers of the national/international testing/calibration laboratories and concentrator certification bodies to facilitate confirmation of the submitted test reports & certificates.

I ……………………………………………… on behalf of …………………………………….

declare that the above specifications matrix conforms to a typical tender concentrator,

type……………………………………… being offered for this tender.

Signature ………………………… Date ………………Stamp/Seal ………………………….



134 of 157

ANNEX 4: DISTRIBUTION OF CUSTOMERS

No REGION TYPE OF CONNECTIONS (QUANTIES IN NUMBERS)

NAME SPECIFIC AREAS/ZONES SINGLE PHASES METERS

THREE PHASE METERS

GRAND TOTAL SMART METERS

1 NAIROBI NORTH REGION

GIKOMBA_PUMWANI AREA

2323 221 2544

LORESHO RESIDENTIAL AREA

2837 351 3188

NAIROBI CBD 2597 891 3488

Sub-Total 7757 1463 9220

2 NAIROBI WEST

REGION

NGONG ROAD_NAIROBI 761 290 1051

KERARAPON RESIDENTIAL

1310 190 1500

MOUNTAIN VIEW ESTATE

1009 128 1137

NAIROBI WEST SHOPPING CENTRE & WILSON AIRPORT

2508 258 2766

UPPER HILL_NAIROBI AREA

476 70 546

Sub-Total 6064 936 7,000

3 NAIROBI SOUTH REGION

INDUSTRIAL AREA_LUSAKA RD_ & SOUTH B AREA

1281 305 1586

UNDUSTRIAL AREA_NAIROBI

1482 525 2007

HARAMBEE_DONHOLM ESTATE AREA

2232 274 2506

MLOLONGO_ATHI RIVER AREA

1559 342 1901

Sub-Total 6554 1446 8,000



135 of 157

No REGION AREAS TYPE OF CONNECTIONS (QUANTITIES IN NUMBERS)

SINGLE PHASES THREE PAHSES GRAND TOTAL SMART METERS

7 CENTRAL RIFT REGION

KERICHO 918 82 1000

NAIVASHA 764 236 1000

NAKURU 2826 586 3412

NYANDARUA_FLYOVER AREA

906 94 1000

5414 998 6,412

8 WEST KENYA REGION

BUNGOMA 606 144 750

BUSIA 537 113 650

KAKAMEGA 439 141 580

KISUMU 1451 317 1768

VIHIGA 375 44 419

SIAYA 196 54 250

BONDO 293 45 338

3897 858 4755

9 NORTH RIFT REGION

ELDORET 1673 329 2002

KITALE 1276 222 1498

2949 551 3,500

No REGION TYPE OF CONNECTIONS (QUANTITIES IN NUMBERS)

NAME SPECIFIC AREAS/ZONES SINGLE PHASES THREE PHASES GRAND TOTAL_SMART

METERS

4 COAST REGION

NYALI_RESIDENTIALS 93 407 500

MTWAPA_KIKAMBALA 674 326 1000

MOMBASA CBD_ENVIRONS

2326 1174 3500

CHANGAMWE_PORTREIZ 1305 195 1500

Sub-Total 4398 2102 6,500

5 MT KENYA REGION

EMBU_KAMBURU 796 204 1000

MERU_MAUA 931 269 1200

MURANGA_KENOL 1279 221 1500

MWEA AREA 896 164 1060

NYERI CBD AND ENVIRONS 1329 171 1500

Sub-Total 5231 1029 6,260

6 SOUTH NYANZA

KISII AREA 413 516 929

NYAMIRA AREA 228 291 519

HOMA BAY AREA 108 203 311

MIGORI AREA 129 190 319

878 1200 2,078



136 of 157

10 NORTH EASTERN REGION

THIKA/JUJA/RUIRU AREAS

1032

243

1275

GRAND TOTALS 44,174 10,826 55,000

ANNEX 5: DEMARCATION OF AREAS/ZONES TARGETED FOR SMART

METERING PER REGION (NOT TO SCALE)

5.1.0 nairobi north REGION_areas/zones TARgeted

for smart metering

5.1.1 NAIROBI CBD_ZONE MAP_TARGETED FOR SMART METERING_RPP



137 of 157

5.1.2 GIKOMBA_PUMWANI AREA ZONE MAP_TARGETED FOR SMART METERING_RPP

5.1.3 LORESHO ZONE MAP_TARGETED FOR SMART METERING_RPP



138 of 157

5.2.0 nairobi west REGION CASES_demarcation maps

5.2.1 UPPER HILL_NAIROBI ZONE MAP_TARGETED FOR SMART METERING_RPP

5.2.2 NAIROBI WEST BUSINESS CENTRE AND WILSON AIRPORT_AREAS

MAP_TARGETED FOR SMART METERING_RPP



139 of 157

5.2.3 NGONG ROAD_NAIROBI_AREA MAP_TARGETED FOR SMART

METERING_RPP

5.2.4 KERARAPON RESIDENTIAL _AREA MAP_TARGETED FOR SMART

METERING_RPP



140 of 157

5.2.5 MOUNTAIN VIEW RESIDENTIAL _AREA MAP_TARGETED FOR SMART

METERING_RPP

5.3.0 nairobi SOUTH REGION CASES_demarcation maps



141 of 157

5.3.1 INDUSTRIAL AREA NAIROBI_LUSAKA RD & SOUTH B ESTATES_AREAS MAP

5.3.2 INDUSTRIAL AREA NAIROBI_ENTERPRISE ROAD_MAP OF AREAS

TARGETED FOR SMART METERING_RPP



142 of 157

5.3.3 HARAMBEE_DONHOLM ESTATES_MAP OF AREAS TARGETED FOR SMART METERING_RPP

5.3.4 MLOLONGO_ATHI RIVER_MAP OF AREAS TARGETED FOR SMART

METERING_RPP



143 of 157

5.4.0 COAST REGION_areas/zones TARgeted for smart

metering

5.4.1 NYALI RESIDENTIAL AREA MAP_TARGETED FOR SMART METERING_RPP

5.4.2 MTWAPA_KIKAMBALA_MAP OF AREAS TARGETED FOR SMART

METERING_RPP



144 of 157

5.4.3 MOMBASA CBD AND ENVIRONS_MAP OF AREAS TARGETED FOR SMART METERING_RPP

5.4.4 CHANGAMWE_PORTREIZ _MAP OF AREAS TARGETED FOR SMART METERING_RPP



145 of 157

5.5.0 mt. kenya region_areas/zones TARgeted for

smart metering

5.1 EMBU_KAMBURU MAP OF AREAS_TARGETED FOR SMART METERING_RPP

5.5.2 MERU_MAUA MAP OF AREAS_TARGETED FOR SMART

METERING_RPP



146 of 157

5.5.3 MURANGÁ_KENOL MAP OF AREAS_TARGETED FOR SMART METERING_RPP

5.5.4 MWEA AREA MAP OF AREAS_TARGETED FOR SMART

METERING_RPP



147 of 157

5.5.5 NYERI CBD & ENVIRONS MAP OF AREAS_TARGETED FOR SMART METERING_RPP

5.6.0 SOUTH NYANZA region_areas/zones TARgeted

for smart metering

5.6.1 KISII ZONE MAP OF AREAS_TARGETED FOR SMART METERING_RPP



148 of 157

5.6.2 NYAMIRA ZONE MAP OF AREAS_TARGETED FOR SMART METERING_RPP

5.6.3 HOMA BAY ZONE MAP OF AREAS_TARGETED FOR SMART

METERING_RPP



149 of 157

5.6.4 MIGORI ZONE MAP OF AREAS_TARGETED FOR SMART METERING_RPP

5.7.0 SOUTH NYANZA region_areas/zones TARgeted

for smart metering

7.1 KERICHO ZONE MAP OF AREAS_TARGETED FOR SMART METERING_RPP



150 of 157

5.7.2 NAIVASHA ZONE MAP OF AREAS_TARGETED FOR SMART METERING_RPP

5.7.3 NYANDARUA_FLYOVER CENTRE-MAP OF AREAS_TARGETED FOR SMART METERING_RPP



151 of 157

5.8.0 WEST KENYA REGION TARGETED ZONES MAPS

5.8.1 BUNGOMA ZONE MAP_AREAS TARGETED FOR SMART METERING_RPP (SPREAD WHOLE COUNTY)

5.8.2 BUSIA ZONE MAP_AREAS TARGETED FOR SMART METERING_RPP (SPREAD WHOLE COUNTY)



152 of 157

5.8.3 KAKAMEGA ZONE MAP_AREAS TARGETED FOR SMART METERING_RPP (SPREAD WHOLE COUNTY)

5.8.4 KISUMU CBD AND SURBURBS_ MAP_AREAS TARGETED FOR SMART METERING_RPP



153 of 157

5.8.5 VIHIGA ZONE MAP_AREAS TARGETED FOR SMART METERING_RPP (SPREAD WHOLE COUNTY)

5.8.6 SIAYA TOWN AND ENVIRONS- MAP OF_AREAS TARGETED FOR SMART METERING_RPP (SPREAD WHOLE COUNTY)



154 of 157

5.8.7 BONDO_RARIEDA MAP OF_AREAS TARGETED FOR SMART METERING_RPP (SPREAD WHOLE COUNTY)

5.9.0 NORTH RIFT REGION TARGETED ZONES MAPS

5.9.1 ELDORET MAP (CBD, INDUSTRIAL UPTO LANGAS AREAS)_RPP PROJECT DEMARCATION



155 of 157

9.2 KITALE MAP (CBD AND SUBURBS)_RPP PROJECT DEMARCATION

5.10.0 NORTH EASTERN REGION TARGETED ZONES MAPS

5.10.1 THIKA_JUJA_RUIRU MAP OF AREAS TARGETED FOR SMART METERING_RPP PROJECT



156 of 157

ANNEX 6: SCHEDULE OF SYSTEM REQUIREMENTS

CLAUSE KENYA POWER

REQUIREMENT

MANUFACTURER’S

COMPLIANCE/REMARKS

REFERENCE

PAGE IN THE

SUBMITTED

DOCUMENTS

1. Interoperability and Open

Protocols. Confirm Data

Acquisition from Different

Vendors Equipment

2. Scalability.

The Bidder shall simulate the

system with 10 million metering

points

3. System Failure Rate.

3 total system failures per year

4. Restoration Time.

4 hours maximum recover time

when the failure is corrected

5. Failure Intensity

(Communication). 0.25%

Communication component

failure rate per year

GAURANTEED COMMUNICATION DESIGN PARAMETERS & MAINTENANCE

RATES

REQUIREMENT GAURANTEED VALUE AS

PER THE OFFER

REFERENCE

DOCUMENT

1 Number of points of the AMI

system (customers’ meters,

concentrators, etc.) connected

to the mobile phone network

2 Annual price of maintenance

services and other recurrent

costs to be paid by KPLC

following the end of the

guarantee period