Technical Specification for Interface Energy Meters ...wrpc.nic.in/ccm/DRAFT_AMR_SPEC_2017.pdf ·...

POWER SYSTEM OPERATION CORPORATION, WRLDC

Technical Specification for

Interface Energy Meters,

Automated Meter

Reading System and

Meter Data Processing

for Western Region

5/1/2017

ContentsContentsContentsContents

GLOSSARY ................................................................................................................................... 5

STANDARDS TO BE COMPLIED WITH ........................................................................................... 6

1. SCOPE .............................................................................................................................. 6

Part-I: Technical Specifications of Interface Energy Meters .......................................................... 7

2. BASIC FEATURES OF INTERFACE ENERGY METERS ............................................................ 7

3. MEASUREMENT ............................................................................................................. 10

4. MEMORY/ STORAGE ...................................................................................................... 12

5. DISPLAY ......................................................................................................................... 13

6. COMMUNICATION ......................................................................................................... 13

7. QUALITY ASSURANCE ..................................................................................................... 16

8. TESTING ......................................................................................................................... 16

9. TYPE TESTS .................................................................................................................... 17

10. INSTALLATION AND COMMISSIONING ....................................................................... 17

11. WARRANTY ................................................................................................................ 18

12. GENERAL ................................................................................................................... 18

Part-II: Automatic Meter Data Reading (AMR) System ............................................................... 20

13. INTENT OF AMR ......................................................................................................... 20

13.1 Energy Meters ........................................................................................................... 20

13.2 Data Collection Unit ................................................................................................... 21

13.3 Central Data Collection System .................................................................................. 21

13.4 Communication System .............................................................................................. 21

14. SCOPE OF WORK ........................................................................................................ 22

15. FUNCTIONAL REQUIREMENTS .................................................................................... 23

16. GENERAL REQUIREMENTS .......................................................................................... 28

17. SYSTEM SIZING AND PERFORMANCE REQUIREMENTS ................................................ 30

18. GENERAL SOFTWARE REQUIREMENTS ....................................................................... 32

19. GENERAL HARDWARE REQUIREMENTS ...................................................................... 34

20. DOCUMENTATION REQUIREMENTS ........................................................................... 34

21. TESTING REQUIREMENTS ........................................................................................... 35

21.1 Acceptance Test Plans and Procedures ....................................................................... 35

21.2 Factory Acceptance Test (FAT) .................................................................................... 36

21.3 Site Acceptance Test (SAT) ......................................................................................... 37

21.3.1 Commissioning Test................................................................................................ 37

21.3.2 Site Functional and Performance Test ..................................................................... 38

21.3.3 Site Cyber Security Audit ........................................................................................ 38

21.3.4 Test Approval ......................................................................................................... 38

22. TRAINING REQUIREMENTS ......................................................................................... 38

23. SUPPORT AND MAINTENANCE REQUIREMENTS ......................................................... 39

23.1 Scope of AMC ............................................................................................................ 39

23.2 On-site support and maintenance .............................................................................. 39

23.3 Remote support and maintenance ............................................................................. 40

23.4 Up gradation and patches .......................................................................................... 40

23.5 Maintenance and support of brought out items .......................................................... 40

23.6 Maintenance and Support for Communication channels ............................................. 40

Part-III: Technical Specifications of Meter Data Processing (MDP), Energy Accounting (EA) and . 41

Deviation Settlement Mechanism (DSM) Accounting ................................................................. 41

24. INTENT OF MDP, EA & DSM ACCOUNTING ................................................................. 41

25. COLLECTION, PROCESSING AND COMPUTATION OF METER ....................................... 41

25.1 Meter Data Collection from Different Location .......................................................... 42

25.2 Storing of Raw Data in a particular location ................................................................ 42

25.3 Converting Raw encrypted data into readable text file. ............................................... 42

25.4 Viewing of .NPC file/Structure of .NPC file .................................................................. 43

25.5 Modification/Editing in Text file.................................................................................. 45

25.6 Appending data files into a single file .......................................................................... 45

26. Concept of Master Meter file ..................................................................................... 47

27. Concept of Master Frequency Meter ......................................................................... 47

28. Concept of Fictitious Meter & Configuration File ........................................................ 48

29. Concept of PAIRS.DAT File .......................................................................................... 49

30. REA2006 .................................................................................................................... 50

30.1 Init ............................................................................................................................. 51

30.2 View .......................................................................................................................... 56

30.2.1 WH Day Data ......................................................................................................... 57

30.2.2 MWH Day Data ...................................................................................................... 57

30.2.3 FICT MWH Day Data ............................................................................................... 58

30.3 Check ......................................................................................................................... 59

30.3.1 Voltage Problem .................................................................................................... 59

30.3.2 Time Correction ..................................................................................................... 60

30.3.3 Prev. Week Data .................................................................................................... 61

30.3.4 Watt Hr Problem .................................................................................................... 62

30.3.5 Algebraic Sum ........................................................................................................ 63

30.3.6 All Check ................................................................................................................ 64

30.3.7 Compute ................................................................................................................ 64

30.3.8 Compute Energy .................................................................................................... 65

30.3.9 Pair Check .............................................................................................................. 66

30.3.9.1 Compute Fict. Meters ......................................................................................... 67

30.4 Account ..................................................................................................................... 69

30.5 MWH Output ............................................................................................................. 69

30.5.1 MVARH Output ...................................................................................................... 71

30.5.2 Load Curve ............................................................................................................. 72

30.5.3 Total Energy: .......................................................................................................... 74

30.5.4 All Check Report Gen .............................................................................................. 74

30.5.5 Pair Check Report Gen ............................................................................................ 75

30.6 Options ...................................................................................................................... 75

30.6.1 All Pair Blocks ......................................................................................................... 76

30.6.2 Pair Analysis ........................................................................................................... 76

30.6.3 Data Availability ..................................................................................................... 76

30.6.4 Auto Replacement ................................................................................................. 76

30.7 New functionalities .................................................................................................... 76

30.7.1 Pair Check Facility .................................................................................................. 77

30.7.2 Time Drift Check Facility ......................................................................................... 77

30.7.3 Net Bus Check Facility ............................................................................................ 77

30.7.4 Voltage failure Check facility .................................................................................. 78

30.7.5 Algebraic Sum Check Facility .................................................................................. 78

30.7.6 Reverse Energy Flow Check .................................................................................... 78

30.7.7 Meter History Report Facility ................................................................................. 78

30.7.8 File Set Archival Facility .......................................................................................... 78

30.7.9 Report on energy flow............................................................................................ 78

31. Conversion of data from 5-min to 15-min in AMR and MDP for DSM accounting........ 79

32. DSM Accounting S/W Module .................................................................................... 79

32.1 SCOPE ........................................................................................................................ 79

33. SUPPORT AND MAINTENANCE REQUIREMENTS FOR MDP, EA & DSM ACCOUNTING

S/W 80

33.1 Scope of AMC ............................................................................................................ 80

33.2 On-site support and maintenance .............................................................................. 80

33.3 Remote support and maintenance ............................................................................. 81

33.4 Up gradation and patches .......................................................................................... 81

33.5 Maintenance and support of brought out items .......................................................... 81

I. Station wise bifurcation of SEMs in WR .......................................................................... 81

II. Station owner wise bifurcation of SEMs in WR ............................................................... 85

III. Make wise bifurcation of SEMs in WR ........................................................................ 86

GLOSSARY

S.No Acronym Definition

1 WRLDC Western Regional Load Despatch Center

2 CTU Central Transmission Utility

3 ISTS Inter State Transmission Network

4 IEM Interface Energy Meter

5 IS Indian Standard

IEC International Electro-technical Commission

6 HES Head End Systems

7 EHV Extra High Voltage

8 RMS Root Mean Square

9 IEEE Institute of Electrical and Electronics Engineers

10 AMR Automated Meter Reading

11 DCU Data Collection Unit

12 CDCS Central Data Collection System

13 GSM Global System of Mobile

14 GPRS General Packet Radio Service

15 IP Ingress Protection

16 HHU Hand Held Unit

17 CMRI Common Meter Reading Instrument

18 LAN Local Area Network

19 WAN Wide Area Network

20 MDP Meter Data Processing

21 EA Energy Accounting

22 DSM Deviation Settlement Mechanism

STANDARDS TO BE COMPLIED WITH

S.No Reference

Detail

Reference Title

1 IS-15959:2011 Data Exchange for Electricity Meter Reading Tariff &

Load Control – Companion Specification

2 IS-14697:1999 Specifications for AC Static Transformer operated

Watt Hour & VAR-Hour meters, class of 0.2S and 0.5S

1. SCOPE Western region comprises of the states of Gujarat, Maharashtra, Madhya Pradesh,

Chhattisgarh, Goa and Union Territories of Daman & Diu and Dadra & Nagar Haveli.

As on 31.03.2017 there are 1409 energy meters in total located at various interface points

in the Inter State Transmission System (ISTS). The existing distribution of Interface

energy meter (IEM) in Western Region (State wise) is as below:

State No. of IEM installed

Gujarat 326

Maharashtra 268

MP 375

Chhattisgarh 385

DD 19

DNH 25

GOA 11

TOTAL 1409

The detailed list is enclosed as Annex-I

The present project envisages to replace the existing fleet of Special Energy Meters

(SEMs) in the inter State Transmission System in the Western Region. The project

also envisages to put in place a system of Automated Meter Data Reading (AMR) along

with the associated hardware and software system for meter data validation and

processing at Western Regional Load Despatch Centre.

The successful bidder shall be responsible for supply and installation of hardware and

software at respective locations and also for ensuring reliable communication

infrastructure between the IEM and WRLDC for seamless transfer of meter data from

substation to WRLDC.

The technical specifications are in three parts. The first part of the specifications

covers the design, manufacturing, testing, supply and delivery of AC 3 ph, 4 wire

Interface Energy Meter (IEM) and. The meter shall incorporate suitable

communication features to communicate with DCU (Data Concentrator Unit) which

shall further be able to communicate with HES (High End System) for remote data

transfer. The second part covers the Automated Meter Reading system for data

collection in the Inter State Transmission System of Western Region. The third part

covers Meter Data Processing (MDP) and Energy Accounting (EA) at WRLDC.

Part-I: Technical Specifications of Interface Energy Meters

2. BASIC FEATURES OF INTERFACE ENERGY METERS a. The energy metering system specified herein shall be used for tariff metering for bulk,

inter-utility power flows, in different States of India. Draw out type, Static composite

meter shall be installed at interface points as a self-contained device for measurement of

Voltage (V), frequency (f) and energy (Wh, VArh) exchanged in each successive 5 min

time block. All meters shall be compliant to IS 15959 and its latest amendments.

b. Each meter shall have a unique identification code, which shall be marked permanently

on its front, as well as in its memory. All meters supplied to as per this specification shall

have their identification code starting with “IEM”, which shall not be used for any other

supplies. “IEM” shall be followed by a dash and an eight digit running serial number,

further followed by a dash and “A” and “B” for the use with CT secondaries of 1 A and

5 A respectively. This shall be mutually agreed between the buyer and the supplier.

c. The meters shall be suitable for communication with external device like modem, DCU,

etc. which shall be able to communicate with HES for local/remote data transfer. The

meter shall compulsorily have at least 1 optical port for taking reading through Hand Held

Unit (HHU).

d. The meters shall normally operate with the power drawn from AC/DC (DC supply is

preferable) auxiliary power supply to reduce the Voltage Transformer (VT) burden. In

addition, there shall be provision to operate the meter from the Voltage Transformer (VT)

secondary circuit having a rated secondary line-to-line voltage of 110V, and to current

transformers (CTs) having a rated secondary current of 1 A or 5A. Any further

transformers/ transactions/ transducers required for their functioning shall be in-built in

the meters. Necessary isolation and/or suppression shall also be built-in, for protecting

the meters from surges and voltage spikes that occur in the VT and CT circuits of extra

high voltage switchyards. The reference frequency shall be 50Hz.

e. The meters shall safely withstand the usual fluctuations arising during faults etc. In

particular, VT secondary voltages 115% of Vref applied continuously and 190% of Vref

for 3.0 seconds, and CT secondary current 150% of Iref applied continuously and 30 times

of Iref applied for 0.5 seconds shall not cause any damage to or maloperation of the

meters.

f. The meters shall continue to function for the remaining healthy phase(s), in case one or

two phases of VT supply fails. In case of a complete VT supply failure, the computation

of average frequency shall be done only for the period during which the VT supply was

available in the 5-minute block. Any time block contraction or elongation for clock

correction shall also be duly accounted for.

g. The total burden imposed by a meter for measurement and operation shall be defined as

per IS 14697. An automatic backup for continued operation of the meter’s calendar-clock,

and for retaining all data stored in its memory, shall be provided through a long-life

battery, which shall be capable of supplying the required power for at least 2 years. The

meters shall be supplied duly fitted with the batteries, which shall not require to be changed

for at least 10 years, as long as total VT supply interruption does not exceed two years.

The battery mounting shall be designed to facilitate easy battery replacement without

affecting PCB of the meter.

h. The meters shall fully comply with all stipulations in IS 14697 except those specifically

modified by this specification. The reference ambient temperature shall be 27° C.

i. Each meter shall have a test output device (visual), as per clause 6.11 of IS 14697.1999,

for checking the accuracy of active energy (Wh) measurement. The preferred pulsing rate

is twenty (20) per Wh for CT sec-1A and four (4) per Wh for CT sec –5A. It shall be

possible to couple this device to suitable testing equipment also.

j. Exception Management- The three line-to-neutral voltage shall be continuously

monitored and in case any of these falls below defined threshold (70% of Vref), meter

shall have suitable indication on LED/ LCD. The meter shall also have provision for low

voltage event logging in meter memory in case of any phase voltage going below a defined

threshold. The time blocks in which such a voltage failure occurs/persists shall also be

recorded in the meter’s memory with a symbol“*” If 3 Phase RMS voltage applied to the

IEM is in between 5% to 70% of Vref and if Voltage is less than 5% of Vref, meter should

record Zero voltage symbol "Z".

k. Time Accuracy - Each meter shall have a built-in calendar and clock, having an accuracy

of 10 seconds per month or better. The calendar and clock shall be correctly set at the

manufacturer’s works. The date (year-month-day) and time (hour-min.-sec.) shall be

displayed on the meter front (when VT supply has been connected), on demand. Meter

shall have the intelligence to synchronize the time with GPS signal and through a single

click from the software itself while connecting the meter with local or remote server.

Limited time synchronization through meter communication port shall be possible at site.

When an advance or retard command is given, twelve subsequent time blocks shall be

contracted or elongated by five seconds each. All clock corrections shall be registered in

the meter’s memory and suitably shown on print out of collected data.

l. A touch key or push button shall be provided on the meter front for switching on the

display and for changing from one indication to the next. (The display shall switch off

automatically about one minute after the last operation of touch key/push button). When

the display is switched on, the parameter last displayed shall be displayed again, duly

updated.

m. The whole system shall be such as to provide a print out (both from the local PC, and

from remote central computer) of the following form:

IEM-12345678-A 12345678.8 0123456.5 00123456.8 20-04-2017

00 49.99 +14.72 -16.5 108.25 50.79 +99.72 -77.25 109.21---------------------------------

02 49.99 +14.72 -16.25 108.25 50.79 +99.72 -77.25 109.21---------------------------------

│

│

22 49.99 +14.72 -16.25 108.25 50.79 +99.72 -77.25 109.21---------------------------------

24 49.99 +14.72 -16.25 108.25 50.79 +99.72 -77.25 109.21---------------------------------

Frequency

in HZ

Active Energy

in WH

Reactive Energy

in VARh

Voltage in V

Commented [vp1]: Possibility of SMS, Alarm ???

Commented [T2]:

Commented [T3R2]:

Commented [T4R2]:

The above data shall be available in text file format (file extension as per IEEE standard/.txt)

exportable to Excel. Indication of time retard or advance to be provided without disturbing

the proposed format. Each 5-min block data consists of Frequency(in HZ), Active energy(in

Wh), Reactive energy(in VARh) and Voltage(in V)

n. The portable hand held unit (HHU)/ Common meter reading instrument (CMRI)/ Data

Collecting Device (DCD) shall be having IS-15959:2011 compatibility for standardized

parameters. The optical coupler for tapping data stored in the SEMs memory shall be

compatible universally across different make of SEMs.

o. Constructional Features

(i) The meters shall be supplied housed in compact and sturdy, metallic or molded cases

of non-rusting construction and/or finish. The cases shall be designed for simple

mounting on a plane, vertical surface such as a control/relay panel front. All terminals

for CT and VT connections shall be arranged in a row along the meter’s lower side.

Terminals shall have a suitable construction with barriers and cover, to provide a

secure and safe connection of CTs and VTs leads through stranded copper conductors

of 2.5 sq. mm. size.

(ii) All meters of the same model shall be totally identical in all respects except for their

unique identification codes. They shall also be properly sealed and tamper evident,

with no possibility of any adjustment at site, except for transactions allowed in IS

15959.

(iii) The meters shall safely withstand, without any damage or mal operation, reasonable

mechanical shocks, earthquake forces, ambient temperature variations, relative

humidity etc. They shall have an IP-51 category dust-tight construction, and shall be

capable of satisfactory operation in an indoor, non-air conditioned installation.

(iv) Either the meters shall have built-in facility (eg. test links in their terminals) for in-situ

testing, or a separate test block shall be provided for each meter.

3. MEASUREMENT a. The active energy (Wh) measurement shall be carried out on 3-phase, 4-wire principle,

with an accuracy as per class 0.2S of IS 14697. The principal unit of measured values

shall be kilowatt-hour (kWh) or Megawatt-hour (MWh). The meter shall compute the

net active energy (Wh) sent out from the substation bus bars during each successive 5

min block, and store it in its memory up to second decimal with plus sign if there is net

Wh export and with a minus sign if there is net Wh import .

b. The meter shall count the number of cycles in VT output during each successive 5 min

block, and divide the same by 300 (60 sec/min x 5min) to arrive at the average

frequency. This shall be stored in the meter’s memory in Hertz up to second decimal.

c. The meter shall continuously compute the average of the RMS values of the three line-

to-neutral VT secondary voltages as a percentage of 63.51 V, and display the same on

demand. The accuracy of the voltage measurement/computation shall be at least 0.5%,

a better accuracy such as 0.2% in the 95-105% range being desirable.

d. The Reactive energy (VARh) measurement shall be carried out on 3-phase, 4-wire

principle, with an accuracy of 0.5S as specified in IS 14697. The meter shall compute

the net Reactive energy (VARh) sent out from the substation bus bars during each

successive 5 min block, and store it in its memory up to second decimal with plus sign

if there is net VARh export and with a minus sign if there is net VARh import. It shall

also display on demand the net VARh sent out during the previous 5 min block.

e. The meter shall also integrate the reactive energy (VARh) algebraically into two separate

registers, one for the period for which the average RMS voltage is above 103.0%, and

the other for the period for which the average RMS voltage is below 97.0 %. The current

reactive power (VAR), with a minus sign if negative, and cumulative reactive energy

(VARh) readings of the two registers (>103% and <97%) shall be displayed on demand.

The readings of the two registers at each midnight shall also be stored in the meter’s

memory. When reactive power is being sent out from substation bus bars, VAR display

shall have a plus sign or no sign and VARh registers shall move forward. When reactive

power flow is in the reverse direction, VAR display shall have negative sign and VARh

registers shall move backwards.

f. For CT secondary rating of 5A, all computations, displays and memory storage shall be

similar except that all figures shall be one fifth of the actual, worked out from CT and

VT secondary quantities.

g. Further, the meter shall continuously integrate and display on demand the net

cumulative active energy sent out from the substation bus bars up to that time. The

Commented [vp5]: Shall we change the sign convention ??

Commented [vp6]: Shall we change the sign convention?

Commented [vp7]: Sign convention

cumulative Wh reading at each midnight shall be stored in the meter’s memory. The

register shall move backwards when active power flows back to substation bus bars.

h. Errors for different power factors shall be as defined in IS14697.

i. For reactive power (VAR) and reactive energy (VARh) measurements, IS14697 shall be

complied with. The accuracy of measurement of reactive energy shall be as per class

0.5S.

j. No rounding off to the next higher last decimal shall be done for voltage and frequency

displays. All 5 min Wh and VArh figures shall however be rounded off to the nearest

last decimal.

k. The harmonics shall be filtered out while measuring Wh, V and VARh, and only

fundamental frequency quantities shall be measured/computed.

l. Data security shall be ensured as per IS 15959 (three layers of security).

4. MEMORY/ STORAGE a. Each meter shall have a non-volatile memory in which the following shall be

automatically stored:

i. Average frequency for each successive 5 min block, in Hertz up to second

decimals.

ii. Net Wh transmittal during each successive 5 min block, up to second decimal,

with plus sign if there is net Wh export and with a minus sign if there is net

Wh import

iii. Net VARh transmittal during each successive 5 min block, up to second

decimal, with plus sign if there is net VARh export and with a minus sign if

there is net MVARh import.

iv. Cumulative Wh transmittal at each midnight, in eight digits including one

decimal.

v. Cumulative VARh transmittal for voltage high condition, at each midnight in

eight digits including one decimal.

vi. Cumulative VARh transmittal for voltage low condition, at each midnight, in

eight digits including one decimal.

vii. Average RMS voltage for each successive 5min block.

viii. Date and time blocks of failure of VT supply on any phase, as a star (*)/ (Z)

mark.

Commented [vp8]: Why not round off to second decimal ?

b. The meters shall store all the above listed data in their memories for a period of fifteen

(15) days. The data older than fifteen (15) days shall get erased automatically.

c. The software provided at HES, i.e. WRLDC, will manage all functionalities of

collection of data through DCUs, validate the data, store the data in a database, and

manage the complete system. Software will also have a scheduler for scheduling the

task of collection of data periodically.

5. DISPLAY Each meter shall have digital display for indication of the following (one at a time), on

demand:

i) Meter serial no. and model : IEM12345678A

ii) Date (year month day) : 20160311 d

iii) Time ( hour min. sec. ) : 195527 t

iv) Cumulative Wh reading : 12345678.6 C

v) Average frequency of the previous block : 49.89 F

vi) Net Wh transmittal during the previous block: - 28.75 E

vii) Net VARh transmittal during the previous block: - 18.75 R

viii) Average % voltage : 99.2 U

ix) Reactive power (VAR) : 106.5 r

x) Voltage - high VARh register reading : 01234567.5 H

xi) Voltage - low VARh register reading : 00123456.4 L

xii) Low battery indication

Any other better or more informative mechanism to display the above shall be preferred.

The above shall be mutually agreed between the meter buyer and supplier.

6. COMMUNICATION a. Each meter must have an optical port on its front for tapping all data stored in its

memory through HHU. In addition to the above each meter shall also be provided with

a RS-485, Ethernet port and USB port on one of its sides, from where all the data stored

in the meter's memory can also be transferred to HES, local computer and pen drive.

The overall intention is to tap the data stored in the meter’s memories at a scheduled

time from any of the above mentioned ports or any other means and transmit the same

to a remote central computer using suitable means of communication.

Commented [vp9]: Watt is not recorded so why is VAR being

recorded

b. All meters should be compatible with Optical port, RS-485 port, Ethernet port and USB

all together at a time and communicate independently. It shall also be possible to obtain

a print out (hard copy) of all data collected from the meters, using the local PC. Data

collection from any local laptop/PC should be possible by installing data collection

software.

c. The bidder may design appropriate architecture for providing end to end metering

solution. He is free to decide upon the best solution out of all the available options to

ensure that data from all IEMs in WR are available at Western Regional Load Despatch

Centre by the scheduled time. However, the entire responsibility of fully functional end

to end metering system shall rest with the bidder in order to meet the performance

levels as given in this document. The communication provider may adopt Optic Fiber/

PLCC/4G communication technology or a combination of these technologies as per

the site requirement adopting best available technology in the proposed area of

implementation. The successful bidder shall be responsible for proper data exchange

among IEM, DCU, HES, MDP and other operational/requisite software as part of fully

functional metering system.

d. The bidder shall adhere to the appropriate security algorithm for encryption and

decryption.

e. The bidder shall design a reliable, interference free & robust communication network

keeping in view the site conditions. It shall be flexible in terms of providing

communication in variable terrain & urban density. The bidder shall design the network

architecture keeping in view the existing and planned infrastructure of the utility. During

designing, suitable consideration shall be kept for future expansion as per requirement

of Utility. Before designing the communication network, the bidder shall do the site

survey and would provide the most efficient communication infrastructure. The entire

infrastructure & associated civil works required for installation & commissioning of

equipment/devices like DCUs, repeaters, routers & access points etc. shall be in the

scope of bidder. The operational testing of all the network elements has to be

demonstrated by the bidder to the satisfaction of the utility.

f. The Bidder shall provide the necessary software which would enable a local PC/ HES

to:

i) Accept the data from the Optical/RS-485 port/WAN and store it in its memory

in text file format (file extension as per IEEE standard/.txt) in a user-defined file

name (file name format must be ddmmyysubstation name-utility name).

ii) Polling feature along with a task scheduler to run the data downloading software

at a pre-designated date and time repeatedly or by manually selecting a meter. File

naming for such downloaded data should also be in user-defined format. A

detailed activity log shall also be available for each downloading operation,

iii) Upload/Import meter data (binary files) in the software for further processing.

While uploading, there shall be provision to upload all selected files with single

key-stroke

iv) Convert the binary file(s) to text file(s).There should be provision to select multiple

files based on filename, convert all selected files with single key-stroke and store

the text files in the same location where binary files are stored.

v) Display the collected data on PC’s screen in text format, with forward/backward

rolling.

vi) Print out in text format the data collected from one or more meters, starting from

a certain date and time, as per operator’s instructions.

vii) Transmit the collected data, in binary format, through an appropriate

communication link to the central computer, starting from a certain date and time,

as per operator’s instructions, and

viii) Store the collected data in binary format, on a CD/Pen Device. In addition to

above, in general the software should be able to convert IEMs data to existing

format as well as in tabular (.csv) format as applicable.

g. The above software shall further ensure that absolutely no tampering (except total

erasures) of the collected metering data is possible during its handling by the PC. The

software shall be suitable for the commonly available PCs, and shall be supplied to

Owner in a compatible form to enable its easy loading into the PCs available (or to be

installed by the Owner/others) at the various substations.

h. The bidder shall ensure data integrity checks on all metered data received from data

collection systems.

i. The quality of installation of the various equipment & power supply wiring to all field

equipment shall be as per standards/ regulations/prevailing practices of the utility. The

supply of electricity needed for operation and maintenance of entire Metering system

shall be provided by the utility free of cost.

j. A suitable network management system (NMS) shall be provided to monitor the

performance of the communication network round the clock. The NMS shall provide

viewing of all the networking elements deployed at site and enable configuration &

parameterization of the networking devices and the nodes.

k. Performance levels for collection of meter readings

All interval data from 99.99% of meters shall be reported to HES within 24 hours after

the scheduled hour. Otherwise day wise compounding penalty action will be initiated

as per the contractual terms to the successful bidder.

l. Performance levels for meter loss of supply and outage detection.

Alarms to be received within 10 min for 90% of meters.

7. QUALITY ASSURANCE The quality control procedure to be adopted during manufacture of the specified

equipment shall be mutually discussed and finalized in due course, generally based on

the established and proven practices of the manufacturer. The software shall be user

friendly which can be easily installed in any PC/Laptop irrespective of operating system

of the PC/Laptop, and shall be certified for ensuring data handling capabilities. The

same should be demonstrated by party during technical evaluation only. During

demonstration standard meter to be brought by party Therefore software shall be

offered for technical compatibility before taking up further necessary action in the

procurement process.

8. TESTING a. All equipment, after final assembly and before dispatch from manufacturer’s works,

shall be duly tested to verify that is suitable for supply to the Owner. Routine and

acceptance tests shall be carried out on the meters in line with IS 14697.

b. Any meter which fails to fully comply with the specification requirements shall be

liable to be rejected by the Owner. However, the Owner may purchase such meters

at a reduced price in case of marginal non-compliance, at his sole discretion.

c. Acceptance Tests for PC Software and data down loading using meter

communication ports

All IEMs after final assembly and before despatch from Bidder’s/Manufacturer’s

works shall be duly tested to verify that they are suitable for downloading data using

meter communication ports shall be subjected to the following acceptance test:

i) Downloading Meter Data from the Meter(s) to PC

ii) Compatibility with PC Software

iii) Functioning of advance and retard time commands

iv) Per meter downloading time verification.

9. TYPE TESTS a. One (1) out of every hundred (100) meters shall be subjected to the complete range of

type tests as per IS14697 and IS15959, after final assembly. In case of any failure to

pass all specified tests, the bidder shall arrange to carry out the requisite

modifications/replacements in the entire lot of meters at his own cost. After any such

modifications and final assembly, two (2) meters selected out of the lot by the Owner’s

representative shall be subjected to the full range of type tests. The lot shall be

accepted by the Owner only after successful type testing.

b. The meters used for type testing shall be separately identified, duly marked, and

supplied to the Owner in case they are fully functional and as good as other (new)

meters, after necessary touching up/refurbishing. In case this is not possible, the

bidder shall provide their replacements at no extra cost to Owner.

c. The Bidder shall arrange all type testing specified above, and bear all expenses for the

same.

10. INSTALLATION AND COMMISSIONING The static energy meters specified above shall be installed at various EHV substations

owned by the Owner, DISCOMs and other agencies, throughout India. The exact

location and time-table for installation shall be finalized by the Owner in due course, and

advised to the bidder, such that bidder’s responsibility in this respect ends within twelve (

12) months of completion of all supplies.

a. The Bidder shall be responsible for total installation and commissioning of the

meters (along with test blocks, if supplied separately) as per Owner’s advice, including

unpacking and inspection on receipt at site, mounting the meters on existing control

and relay panels at an appropriate viewing height, connection of CT and VT circuits

including any required rewiring, functional testing, commissioning and handing over.

The Bidder’s personnel shall procure/carry the necessary tools, equipment, materials

and consumables (including insulated wires, lugs, ferrules, hardware etc.)

b. As a part of commissioning of DCDs the Bidder shall load the software specified in

clause 6(F) into the PCs at the respective substations, and fully commission the total

meter reading scheme. He shall also impart the necessary instructions to substation

engineers.

c. Following technical information shall be furnished by the Bidders in their offers:

i) Foreseen dimensions of proposed meter.

ii) Expected weight of proposed meter.

iii) Dimensions and weight of the test block, if supplied separately.

d. At the time of commissioning, the meters lying in stores shall be time synchronized

through GPS signal before installation in the panel to avoid the large time mismatch.

11. WARRANTY a. 60 months for the Meter and meter testing after 5 years. Support and maintenance

during 5 years extended period after expiry of warranty period

b. The warranty would include repair, replacement , part material replacement cost and

one way (return) transportation cost (including insurance of transit)

c. Meter software, if upgraded by OEM should be supplied free of cost with initiation

taken from party. Remote service person name to be indicated during bidding

d. Meters which are found defective/inoperative at the time of installation or become

inoperative/defective within the warranty period, these defective/inoperative meters

shall be replaced within one month of receipt of report for such

defective/inoperative meters.

12. GENERAL a. The meter shall be supplied with latest/compatible software (should be compatible

with old & new meters data download handling). Any new software as required to be

installed within warranty period are to be done by party or through remote support

to client.

b. The total arrangement shall be such that one (1) operation ( click on “data down load

from meter” button on software ) can carry out the whole operation in about five (5)

minutes per meter or preferably faster.

c. The layout of software front end/user interface has to be approved by bidder during

technical evaluation/demonstration. However a standard template sheet will be

provided along with bid for ref.

d. Software for windows/office/antivirus to be supplied. Antivirus should not slow

down processes and same will be demonstrated during technical demonstration.

e. Above spec. is minimum only, any higher standard required for the purpose intended

(meter data handling) would be assessed by vendor and would be supplied

accordingly. The DRS should be approved during drawing approval stage.

f. Meter shall accommodate in existing C&R panel of standard size (Alstom/

ER/ABB/Siemens) in kiosk or C&R panel with door closed. If required before

bidding, bidder may collect necessary data or else the scope is deemed to be included.

g. Step by Step procedure (on screen shot type or desktop video capture) for

i. Installation/Re-installation of Database handling software in to Laptop / PC

ii. Meter maintenance/site-testing procedure as per relevant IS/IEC standard.

iii. Procedure for data downloading from Meter by Laptop/Desktop PC.

h. As on date of delivery, the supplied meters shall comply with all statutory regulation

as required under CERC/CEA/IEGC as applicable and the same should be declared

by the supplier during delivery along with warranty certificate.

i. Bidder is responsible for dismantling of old special energy meters and to purchase

on buy back basis on successful installation of interface energy meters.

Part-II: Automatic Meter Data Reading (AMR) System This section describes the envisaged system architecture of Automated Meter-data Reading in Western Region.

13. INTENT OF AMR

The intent of AMR scheme proposed in this document is to automate the task of data

collection from each meter/location to the Central Data Collection System (CDCS)

followed by validation, processing and generation of customized reports. The data shall be

stored in ORACLE database located at Western Regional Load Despatch Centre, Mumbai.

The communication system for data transfer from IEM to WRLDC shall also be in the

scope of the bidder. Concept diagram of the indented AMR is given below:-

13.1 Energy Meters

Energy Meters to be covered under proposed AMR system are I n t e r f a c e Energy

Meters (IEMs) manufactured as per Technical Specification i l lustrated in this

document.

13.2 Data Collection Unit

A Data Collecting Unit (DCU) installed at each location will act as interface between

Central Data Collection System (CDCS) at WRLDC and IEMs installed at that location.

DCU shall collect data from energy meters and sent the same to CDCS at WRLDC.

DCU shall also report diagnostic information of the energy meters to CDCS.DCU shall

have following functions:-

• Acquiring energy data and status from energy meters.

• Providing energy data and status to CDCS.

• Providing energy data and status to local computer.

• Intelligence to synchronise IEMs clock with GPS clock located at Station/RLDC.

Each meter has a unique identification number and each meter location has unique

identification code. DCU shall collect data from a single or group of meters based on

meter number or meter location code. DCUs shall collect data from energy meters and

transfer the same to CDCS. DCUs should provide a RS-485/LAN/USB port for

communication with local personal computer or terminal.

13.3 Central Data Collection System

A Central Data Collecting system provided at WRLDC will manage all functionalities of

collection of data through DCUs, validation of the data, storage of the data in ORACLE

database and management of the complete AMR system. Software will also have a scheduler

for scheduling the task of collection of data periodically. Provision of extracting data

from the database in the text files as per existing format for all or selected meters for

further processing by Energy Accounting software is also to be built in data collection

software.

13.4 Communication System

Communication system to be used for transfer of data from DCU to CDCS may be

O p t i c F i b e r / P LCC / 4G. Bidder is free to suggest alternative communication media

if it is more efficient and cost effective.

14. SCOPE OF WORK

This section provides detailed scope of work included in the bidder’s scope, excluded from the bidder’s scope, facilities to be arranged by bidder and facilities to be provided by station owner.

14.1 Bidder’s Scope of Work The scope of work in complete conformity with subsequent sections of the specification shall

include site survey, planning, design, engineering, manufacturing/integration, testing, supply,

transportation & insurance, delivery at site, storage, installation, commissioning, demonstration

for acceptance, training and documentation of AMR system including: • Design Document for complete AMR System. • Software Requirements Specifications for CDCS and DCU. • Server System and Central Data Collection System (CDCS) at WRLDC. • Data Collection Unit (DCU). • Connection and interfacing of meters with DCU. • GSM /PSTN Modems. • Communication channels between each DCU and CDCS. • All cabling, wiring, terminations and interconnections of the equipment. • Database development, Displays and Reports. • Standard database (RDMS) for storage of data at WRLDC. • Archival and retrieval of data through Oracle database at WRLDC.

• Decoded text files in existing format at WRLDC • Training of personnel (Substation, SLDC, RLDC, RPC) • Warranty for 5 years and support and maintenance during 5 years extended period after

expiry of warranty period.

• To maintain extra 20% quantity of AMR equipment as backup and for future requirement.

Any other work which is not identified here or in the specification but is required for

completion of the project within the intent of this specification shall also be in the scope of

the Bidder without any extra cost.

14.2 Exclusions from Bidder's Scope of Work Followings are not included in the scope of the bidder and shall be provided by local station without any extra cost to bidder:-

• Space for installation of IEMs, DCU, CDCS at respective locations

• Auxiliary Power Supply for IEMs, DCU at each location and server system at CDCS. • Provision of static IP and internet connection at WRLDC • Building, air conditioning systems and other infrastructures.

• PC required for data downloading at each location with connector. Local site shall

arrange for the same.

15. FUNCTIONAL REQUIREMENTS

Major components of the AMR System to be implemented under the scope of this specification

document are Data Collection Unit, Central Data Collection System and communication

channel. This section enumerates the functional requirements of each component.

15.1 Data Collection Unit Data Collection Unit (DCU) is to function as gateway between Central Data Collection System (CDCS) and energy meters installed at DCU location. DCU shall have following functions:-

• Acquiring energy data and status from energy meters.

• Providing energy data and status to CDCS. • Providing energy data and status to local computer.

15.1.1 Acquiring energy and status data from energy meters

DCUs are to be connected with local energy meters in multi drop connection to RS-485 port.

Connection to the local energy meters should be firm and secure from any unintended

disconnection. DCU should implement SEM protocols. Protocols for the energy meters will

be provided by CTU/ Meter manufacturer. It should be possible to change/update the energy

meter protocol driver from CDCS. DCUs should not send any command other than the

command to read the energy data and status data and GPS clock synchronization of IEM clock.

15.1.2 Providing Energy Data and Status to CDCS DCUs shall be provided with suitable SIM/modem etc in order to have connectivity over O p t i c F i b e r / P LCC / 4G with WRLDC. All communication between DCU and CDCS should be on secure VPN.

DCU shall accept following commands from CDCS/GPS Clock and should function as per the command:

• Energy data collection from energy meters. • Acquiring status and alarm from energy meters.

• Modification of DCU Configuration

• IEM clock synchronization with GPS clock.

15.1.2.1 Energy Data Collection. DCUs shall query energy data and transfer the same to CDCS based on the command received

from CDCS. Command may be for one time demand of data or it may be on cyclic basis. DCU

should be able to query data from all or selected energy meters for the selected period based

on the command from CDCS. DCUs should be able to read energy data from all make of

energy meters available in the market like L&T, Secure, and Elster etc.

Each meter has a unique identification number and each meter location has unique identification code. DCU shall collect data from a single or group of meters based on meter number or meter location code. DCUs shall collect data from energy meters and transfer the same to CDCS. As DCU functions

on read and forward philosophy for energy meter data, no storage is envisaged in the DCUs

for energy data. However, if vendor thinks that provision of storage in DCUs may be required

to meet the requirements of the AMR system, storage may be provided. However, such storage

should take care of currency of data while responding to commands from CDCS.

15.1.2.2 Status Data Collection. DCUs shall query periodically all energy meters connected to it for status or any alarm etc. Any change in status or alarm shall be reported to CDCS immediately. DCUs shall acquire connected energy meter details like meter identification number, make, CT/PT ratio etc periodically as well as whenever it’s powered on. Any meter change activity like meter number, change in CT ratio etc should reported to CDCS immediately

DCUs shall be self-monitoring for alarm like power failure, communication disconnection, and disconnection from energy meters and report the same to CDCS immediately. DCUs should have nonvolatile memory for storing status data of energy meters duly time stamped, details of connected meters like make, meter number, status change. Nonvolatile memory should be able to store such data for at least one month in round FIFO buffer.

15.1.2.3 DCU Configurations change. Each DCU shall have a unique identification number normally not required to alter at site. DCUs should accept and respond command for making configuration changes in DCU like

periodicity of energy data/status data collection/GPS clock signal for IEM clock

synchronization. For each configuration change, DCU should respond with task successful or

failure message to CDCS. Configuration commands from CDCS may be in the form of single

command or multiple commands in a command file. DCU should accept and make changes in

configuration through SMS from CDCS as well as data on O p t i c F i b e r / P LCC / 4G.

DCU should receive the configuration command from WRLDC on same channel used for

transfer of data to WRLDC.

DCUs should store all configuration data locally in a separate non-volatile memory. All changes

to configuration should take place first to this memory. Only after receiving a specific command

from CDCS, the saved configurations should come into effect. However, any other

functionality should not get affected during accepting and responding to configuration

commands from CDCS. DCUs are not required to store history of configuration changes as all

history shall be maintained in CDCS.

15.1.2.4 IEM clock synchronization with GPS clock

DCU should have the intelligence to synchronize the IEM clock time with GPS clock time.

Input GPS clock signal to DCU will be from station GPS clock. If GPS clock is not available

at station level, DCU will get GPS clock reference from CDCS, WRLDC. DCU will

synchronize IEM clock with GPS clock in a single command on every schedule of data

downloading from that particular IEM.

15.1.3 Providing energy data to local computer. DCUs should provide a RS-232/LAN/USB port for communication with local personal computer or terminal. DCU shall provide meters status, alarm etc and energy data to local personal computer. PC should be able to query energy data from selected or all energy meter by using web browser and institutive user interface. No special software should be required to be installed at local computer for this communication. All communication with local computer should be password protected. PC for data downloading at each DCU location shall be arranged by respective site / utility.

15.2 Central Data Collection System A central data collection system (CDCS) shall be provided at WRLDC for collection and processing of data from DCUs installed at remote locations. CDCS shall perform following functions:-

• Communication with DCUs. • Collection of energy data from DCUs. • Collection of status data form DCUs • Remote Configuration of DCUs

• GPS clock signal to DCU • Processing of energy data. • Storing of data. • Providing data to energy accounting software. • Reporting functions. • Monitoring and Alarming. • Audit trail and logging. • Meter management.

15.2.1 Communication with DCUs The CDCS shall have a dedicated Communication Server – This shall manage the VPN

Connections, DCU Communication, Alarm management, Logging, DCU Configurations as

well as GPS clock signal to DCU. The Interface of the Communication Server, shall be

standards based, such that, upgradation of either Communication System or Application Server

will not need a commensurate replacement of the other. The CDCS shall have a Network

Management Interface that provides a Dash Board of the DCU's and their status / Alarms and

Meter's that are not communicating.

15.2.2 Collection of energy data from DCUs CDCS shall collect data from energy meters through DCU for selected/configured meter location periodically or on demand at any time. CDCS should have a scheduler software which shall issue command to concerned DCU and shall collect the required energy meter data. 15.2.3 Collection of status data form DCUs CDCS should have DCU monitoring module. This module shall monitor each and every DCU for its working status, parameters and any alarm etc. The monitoring data should be collected periodically or on demand at any time from all or selected DCUs.

15.2.4 Remote Configuration of DCUs CDCS should be provided with software module for remote configuration of selected or batch

of DCUs. Remote DCU configuration module should be able to configure each and every

parameter of DCU individually or in batch mode. It shall be possible to download the following

changes to the remote device in addition to other required changes: • Poll cycle for collection of energy data. • Fixed public IP of CDCS server of the Control Centre • Changes in meter protocol driver.

15.2.5 GPS clock signal to DCU CDCS should generate GPS clock time signal to selected DCUs to synchronize IEM clock time with GPS clock time. DCUs gets GPS clock reference signal from station GPS itself. If GPS clock is not available in any station, CDCS should generate GPS clock time signal to DCU to time synchronize the IEMs connected to that DCU. 15.2.6 Processing of energy data Collected energy meter data should be provided to data processing module. This module shall check the data for its completeness, any error etc. If data collected is not found usable, data should be collected again.

15.2.7 Storing of data. If collected data found usable, it should be provided to data storage module. Data storage module perform the loading the collected energy data to database as per its structure. Archival of data should be through Oracle data base.

15.2.8 Providing data to energy accounting software CDCS should have software module for providing energy meter data from the database to the energy accounting software. The data output shall be in the form of text file (as per WRLDC standard text file format) or as query based output.

15.2.9 Reporting CDCS should have data reporting capability implemented through a separate dedicated module. Reporting module should be able to give report output on screen, in pdf or in XLS/csv form. Reports may be based on pre-configured criteria or based on adhoc query.

15.2.10 Monitoring and Alarm CDCS at WRLD shall provide DCU monitoring and self-monitoring functions to monitor the operating conditions and the performance of the system.

Any detected problems shall be reported through local display, built-in event logging and to remote console or printer. Severe problems, such as loss of communication, shall generate alarms locally and e-mail notifications to configured e-mail address. User shall be able to enable and disable alarms individually.

CDCS shall generate an alarm whenever “data not received” occurs for one or more times for one or more DCU/SEM data. The alarm shall indicate which DCU/SEM has the problem.

CDCS shall generate an alarm when “data not received in time” occurred to a DCU/SEM data

for more than a preset number of times during a specified period. The number of times that

“data not received in time” occurs shall be configurable from 1 to 1,000 with a step of 1.

15.2.11 Audit trail and logging CDCS should have audit and logging function for each and every activities either completed successfully or failed should be logged. The system shall provide audit trail of user and system activities that enables data changes to be tracked and reported, including changes made by the system administrator. For editing of energy meter data, the system shall record the following information in a log and store it for a minimum of 12 months: � User ID � Date and Time of Change User shall be prompted to input a reason for editing using either a standard reason code or a

freeform text field. In addition to data stored in the edit log each interval containing edited data

shall be marked with a status to indicate that the data has been edited. The pre-edited value

shall be stored in the database as a previous version which can be retrieved using “as-off” date

functionality.

Changes to configuration data by users shall be logged by date, time, and user ID and such logs shall be stored for a minimum of 12 months. Critical changes relating to measuring parameters (pulse multipliers, transformer ratios, etc.) and formulae change shall be stored indefinitely as a previous version. For regular system tasks, such as meter communication, task processing, validation, etc the information will be kept for minimum one month.

Full data and system audit ability such as version controls and retrieving data according the date and time. Additionally, all versions of meter data shall be stored and retrievable by “as-off” date so that users may inspect data.

15.3 Communication System Entire project has to be based on Optic Fiber, however in case Optic Fiber is not available at

any location than any available communication service P L CC / 4G may be used for the same.

Bidder should quote considering following percentage distribution of the locations. This is for

bringing all the bids on common platform. However the selected agency will have to conduct

detailed survey regarding availability of the particular service for all locations. The estimated

break up of locations based on telecommunication methods is given below: � 90 % Optic Fiber � 10% PLCC/4G

16. GENERAL REQUIREMENTS Components of AMR system should meet following physical requirements:

16.1 DCU

16.1.1 General Construction • DCU shall be a self-contained, stand alone, temper proof sealed box with necessary ports

for external connection. It should be flush mounted or surface mounted without requirement of a separate panel.

• DCU should not have any moving parts such as a hard disk, to ensure smooth and reliable

operation for long term. • All components inside DCU shall be easily accessible for testing. Similarly all bays and bay-

panel wiring shall be easily accessible. . The plug in units, whose removal or insertion, when in operation might endanger the reliability or performance of the unit, shall have suitable protection.

• Each sub-assembly inside DCU shall be clearly marked to show its function, schematic

reference so that they are identifiable from the component layout diagram in the handbook. • All external connections to DCU should be secure so as to avoid accidental disconnection. • Each meter shall have a unique identification code, which shall be marked permanently on

its front, as well as in its memory. • The DCU shall be normally powered from the station battery backup supply rated at 230V

AC, single phase. • DCU should have protection against entry of dust, lizards etc. • Substantial EMI (Electro Magnetic Interference) and ESD (Electro Static Discharge) will

be present at DCU site, effect of which shall be duly considered while designing the system.

Performance of the overall system shall not be hampered by such interferences. EMI /

EMC tolerance shall comply with IEC 61850-3 standard. Alternately specify an isolation

level of 3kV or more. • DCU should be able to operate in environment with temp upto 50ºC and humidity up to

90% without any significant effect on its performance. • The mechanical design and construction of each unit sub-assembly shall be inherently

robust and rigid under various conditions of operation, adjustment, replacement, storage and transport.

• DCUs shall also withstand without any damage or maloperation reasonable mechanical

shocks, earthquake forces, ambient temperature variations, relative humidity etc. They shall have an IP-51 category dust-tight construction, and shall be capable of satisfactory operation in an indoor, non-air conditioned installation.

16.1.2 Local Display A local display for status like power on, communication activity etc and alarm like power failure communication fault etc should be provided on the face of DCU. A web based display of DCU dash board displaying all status, logs of activities, logs of alarm etc should be provided which shall be accessible from local PC as well as on CDCS.

16.2 CDCS • DotNET or equivalent architecture such as Java based technologies should be used for

development of CDCS software. • System should support entry / modification of data manually by an authenticated user. • Uploading meter data files manually to the AMR system by an authenticated user should

also be supported. • System under this project should be complete in all respect including software, hardware,

servers, LAN equipment’s, cabling, modems, server racks etc. • The servers or computer system should be in redundant mode in main and standby

configuration. In case of failure of main standby should take over the work of data collection.

• Data collection system should use multi-tier architecture having separate tier for database,

application server and client. • Application tier should utilize Web based architecture based on Microsoft .NET

framework. • Client tier should be any Internet Explorer like MSIE, Firefox etc. • All human machine interface with software system should be web-based. • The Application shall be secured with password protected access. It should be multiuser

with role based security. • CDCS should be implemented by using server machines. Two machines shall be used for

hosting software and DBMs in main and standby mode. One server shall be used as communication front end for all communication with DSUs as well as clients. Suggested configuration of servers may be:- � 6GB main memory � 3x300 GB hot pluggable, HDD configured as RAID5 � DVD RW drive � USB ports � 10/100/1000 mbps dual Ethernet card � Hardware should may be desktop based with keyboard, mouse and monitor etc.

16.3 Communication System • All modem/SIM should be securely and firmly mounted on DCU itself. • Mounting or un-mounting of modem/SIM should be accessible from front of DCU. • It should be possible to change modem/SIM without uninstalling DCU. • Mounting of modem/SIM should be sealable. • The Modem shall meet the following environmental specifications, IP55 housing, Storage

Temperature: -20 degrees to +70 degree Celsius, Operating Temperature: - 10 degrees to +60 degree Celsius, Humidity:- 95% RH ( Non - Condensing).

17. SYSTEM SIZING AND PERFORMANCE REQUIREMENTS

AMR System shall meet the following system sizing and performance requirements. The system

sizing and performance requirements are specified for main subsystem. Standby subsystem

shall have the same sizing and performance requirements. The Acceptance of the product shall

be based on the WRLDC approved test protocols/ schedules to be submitted in advance by

the Bidder ahead of factory/site inspection

17.1 System Sizing The system sizing for AMR System is only specified for initial sizing. The delivered system shall be expandable as the input and output requirements grow. Supplier is required to demonstrate their system’s expandability in FAT.

17.1.1 CDCS CDCS should meet following sizing requirements: 17.1.1.1 Population of Energy Meters CDCS shall receive data from 170 DCUs at the minimum data collection interval from up to

25 energy meters connected per DCU initially. However, CDCS should be able to handle data

collection from up to 1000 DCUs and up to 5000 energy meters without any significant

degradation of performance.

17.1.1.2 Data Storage CDCS shall provide online storage for storing, as a minimum, 5 years collected data, processed data and output data.

CDCS event archive data storage historian shall provide, as a minimum, a data storage that is capable of storing 5 years of event data, assuming event will not be more than 20% of the total time.

17.1.1.3 Clients CDCS shall be capable of supporting minimum 5 clients for providing collected data. Each client output shall be individually configurable by users. 17.1.2 DCU Each DCU shall be presently connected with up to 25 energy meters, however it should be able to handle up to 35 energy meters without any significant degradation of performance.

17.2 Data Handling Performance Requirements CDCS shall meet the following performance requirements for data collection and data processing.

17.2.1 Performance requirements for CDCS CDCS shall be able to complete all data receiving, data processing, data storing from all DCUs

within specified time as guaranteed by the supplier excluding the waiting time for data arrival.

This performance requirement shall be met under the maximum number of input DCUs and

maximum number of SEMs with the maximum number of data points as specified for the

delivered as-build or expanded system.

17.2.2 Performance requirements for DCU DCU shall be able to complete all data receiving form energy meters and sending the same to

CDCS within specified time guaranteed by the supplier. This performance requirement shall be

met under the maximum number of SEMs as specified for the delivered as-build or expanded

system.

17.3 System Availability Requirements AMR system and its subsystems and system components shall meet the following availability requirements.

The CDCS shall have a measured availability of 99% or better during the availability test. The

CDCS software shall be considered available when all of the functions described in this

Specification, except as noted are operating as specified, at their scheduled periodicity, and

within the execution time parameters, at the same time all hardware is available as specified.

The CDCS shall continue to operate without interruption under any single point of failure

condition. That is, there shall be no hardware or software element that, as a result of its failure,

renders the CDCS unavailable. This requirement shall specifically include all hardware, the

interconnections among hardware, power supplies, and enclosures of the OP or PT

subsystems.

17.3.1 System components Individual system components, such as server hardware, storage devices, shall each exhibit an availability of better than 98%.

18. GENERAL SOFTWARE REQUIREMENTS AMR System shall meet the following general software requirements.

18.1 Upgradability All software kernel/OS and application programs supplied shall be fully upgradable through firmware upgrade and/or other software upgrade methods. The firmware/software upgrade may include

• General software upgrade such as kernel/OS upgrade

• Adding new features and functionalities, such as supporting new data format and communication protocols

• Fixing bugs and deficiencies The Supplier shall keep POWERGRID/WRLDC informed of the latest software updates of revisions available after the system is shipped.

Users shall be able to perform the necessary software upgrade in the field.

18.1.1 Software security requirements at delivery Software at delivery shall meet following requirements in accordance with general software security assurance practices.

18.1.2 Security Tested and Configured All software and associated application software modules shall be the most secure version of the software available at the time of start of the Factory Acceptance Test. The delivered software shall to be tested to ensure the followings:

• Free of computer viruses, worms, Trojan horses, and other software contaminants

• Unused services are disabled/removed, this includes • Device drivers for devices not included in the hardware • Unused networking protocols

• Unused administrative utilities, diagnostics, network management, or system

management functions

• Administrative utilities, diagnostics, network management, or system management functions or workstations unused by administrators

• Backups of files, databases, and programs, used during system installation/upgrade but

not needed in the operational system

• Accounts that are not End-User Administrator created shall be removed, this include

• Any guest accounts (with and without passwords) or default administrator or maintenance accounts other than the initial system administrator account for Procurement Entity

• Any guest accounts or default administrator or maintenance accounts for any third

party software

18.1.3 Maximum Initial Security Settings The software shall be shipped with all security settings at their maximum setting. All software shall be delivered with all the latest relevant patches installed.

All security-related parameters and options shall be placed at their most restrictive settings at

the delivery, i.e. affording the access and execution privileges to the smallest class of users

consistent with meeting the functional specifications, and restricting their rights to the

narrowest range of privileges.

18.1.4 No Automatic Downloading and Execution of Executable Code It shall not be possible to download any executable code into the CDCS or DCU and execute

the downloaded software code automatically without system administrator’s approval. All

software shall be removed that would otherwise make it possible to execute a scripting language

(such as ActiveX, Java, Java scripts, etc.), including software in the browser and e-mail

processor, where applicable.

18.1.5 File Access Control The CDCS and DCU software shall support controlled access privileges for files on, including

at least access, read, write, execute, and combinations of these. The access privileges for each

user can only be assigned by system administrator of CDCS or DCU as the case may be, and

shall be assigned on an individual user account basis.

The default access privileges for each new user account shall be no access to any file on the system at all.

No user, including system administrator, shall be given the privilege of modifying operating

system files and other files that are never supposed to change while the system is running.

18.1.6 Free of “Electronic Self-Help” Enabled Software It shall be strictly prohibited for delivered software to contain embedded faults or back-door

mechanisms that allow the software manufacturer to remotely disable some or all of the

functions of the software, or affect their performance, or in any way degrade its operation (so-

called “electronic self-help” in the terms of the Uniform Computer Information Transactions Act). The software shall not contain any mechanism that automatically disables some of all of its functions or degrades their operation on a certain date or upon the occurrence of a specific event.

19. GENERAL HARDWARE REQUIREMENTS AMR System shall meet the following hardware requirements.

19.1 Operating environment AMR system hardware shall be supplied that is suitable to operate in environment with temp up to 50ºC and humidity up to 90% without any significant effect on its performance.

19.2 Security Requirements AMR System hardware and packaging design shall meet physical security requirements like measures to prevent unauthorized access to certain AMR system hardware components.

20. DOCUMENTATION REQUIREMENTS

Documentation of AMR system should meet following requirements. All documents should be supplied in hard copies as well as computer readable soft version:-

20.1 Design Documents Before starting the manufacturing of the AMR system components a design document should be submitted. The design document must essentially (but not limited to) included:-

• System Overview. • Functional diagram. • Flow diagram. • Functions of each major component. • Physical details of each major component. • Overall networking scheme. • System configurations.

20.2 Software Requirement Specifications Document After approval of Design document a software requirements specifications (SRS) document

for the application software for CDCS and DCU should be prepared and submitted for

approval. This SRS should be prepared as per IEEE standard 830 of latest version for

recommended practice for software requirements specifications. Software should be designed

as per approved SRS.

20.3 User Manuals Following user manuals should be prepared and supplied for the system:- 20.3.1 User Manual for central site User manual for central site i.e location where CDCS shall be installed and where all data

collection activities shall be taken up, should contains all user instructions, block diagrams, user

screens etc in order to make itself contain complete document required for operation of

complete AMR system including each and every component of AMR system.

20.3.2 User Manual for DCU site Separate user manual shall be provided which shall be used by the users located at DCUs site.

This user manual should contain details of external connections to DCU, ICU, communication

system, block diagram of system at DCU site, instructions of using DCU system, trouble

shooting of DCU system etc. This user manual should be self-contain and does not require any

external reference document in order to use and trouble shoot DCU system.

20.3.3 Training Documents Training document to be used during training of site personals should contain major functional details of overall AMR system, its features and major instructions of understanding the overall working of the AMR system.

20.3.4 Testing Documents Testing documents shall be prepared and submitted as per Testing Requirements clause of this specification. 21. TESTING REQUIREMENTS

All equipment, materials and software for AMR System shall be subject to both Factory

Acceptance Testing (FAT) and Site Acceptance Testing (SAT). The purpose of Acceptance

Testing is to determine compliance to this specification in every respect in regard to the

delivered and installed system.

21.1 Acceptance Test Plans and Procedures

The Supplier shall develop and document proposed Test Procedures and Test Plans for Factory

Acceptance Testing (FAT) and Site Acceptance Testing (SAT) of the delivered and

commissioned system and its components. Supplier shall finalize the proposed FAT and SAT

acceptance test plans and procedures. The final Test Procedures and Test Plans shall be subject

to review and approval prior to testing.

The Acceptance Test Plans (ATP) shall enable WRLDC to verify the ability of the delivered and commissioned system and its components to individually and simultaneously fulfil all functional and performance requirements of the system set forth in the contract through a series of mutually agreed to structured tests.

All system documentations shall be completed, reviewed and approved by the WRLDC before any testing.

The ATP shall include, but not be limited to, functional tests that demonstrate compliance of the functional, performance, software, hardware, communication, interface, and operational aspects of the delivered and installed system.

21.2 Factory Acceptance Test (FAT)

The Supplier shall perform a preliminary FAT (Pre-FAT) prior to the FAT. The pre-FAT shall

be a complete dry run of the FAT, following the test plans and procedures. The intent is for

the Supplier to detect and correct most design, integration, and database, display, and

performance problems prior to the FAT. The POWERGRID representative shall have the

right to witness all or parts of pre-FAT for which Supplier shall intimate the POWERGRID

sufficient advance.

Test results (including documentations and certifications) for tests conducted by Supplier or

third parties that are not included in the FAT test plan and procedures shall be furnished to

POWERGRID prior to FAT for review and evaluation. Supplier and/or third parties

conducted tests deemed inadequate shall be repeated until accepted by POWERGRID

Supplier's project manager shall sign off each test of Pre-FAT. The completed test results shall

be sent to POWERGRID for review before POWERGRID’s representative travel to the

Supplier's facilities for the FAT. All tests shall be conducted using the contract-specified

databases unless the POWERGRID authorizes the Supplier to use a test database.

The FAT shall be conducted according to the FAT Test Plan and Test Procedure documents approved by POWERGRID shall cover, as a minimum:

• Visual Inspection – To verify that the system to be delivered has all required components and is properly configured. Visual inspection shall verify acceptable

workmanship and that all equipment, including cables and connectors, are appropriately labeled

• Hardware Diagnostic Test – Individual tests of all system hardware. These tests shall

consist of running standard hardware diagnostic programs, plus all special diagnostic programs used by the Supplier

• Communications and Interfacing Test – Verify that all interconnected system components, such as data acquisition, control, monitoring, and data management

functions are operating properly when correctly connected

• Software Development Tools – Verify that all required software development tools, utilities, software diagnostics, and debugging tools for the system, including the UI and database, are included in the system and are functioning correctly

• Functionality verification – Verify that all system functions are working normally as set

forth in the contract

• Performance Testing – Verify that the system throughput, timing and response time requirements are satisfied. Tests shall include verification of: � Data exchange times � Local and remote request response times � Communication latency � UI function response time

• Security Testing – Verify that the system meet the software at delivery security

requirements and other aspects of secure operation and system access including: � Communication error detection capabilities

� Correct operation of system configuration, control, maintenance, and management

procedures

� Safe system recovery with no erroneous data or control operation generation after system restarts

� Protection against unauthorized access to the system and control functions • Environmental Testing – Verify that

� All system functions shall operate correctly over the specified temperature range

� The accuracy of the inputs and outputs remain valid over the specified temperature

range. The test schedule shall allow sufficient time for verification and/or additional unstructured testing by the POWERGRID’s representative, who shall be able to schedule unstructured testing at any time, including during structured tests.

21.3 Site Acceptance Test (SAT)

The SAT will be conducted by the POWERGRID with support as required from the Supplier

after the system has been installed and commissioned. The system will be subjected to a subset

of the functional and 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 the

POWERGRID’s representative, 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. The SAT includes the commissioning test, the functional and performance test, and

the cyber security audit after the installation of the delivered system.

21.3.1 Commissioning Test The commissioning tests shall be conducted by the Supplier and include:

• The same visual inspection and verification as in FAT

• Loading of the software and starting the system. At the option of the POWERGRID, all software shall be recompiled from the source or distribution media

• Interface of the AMR System to communications facilities for all data sources and other

systems that interface with the AMR System • Initialization and preliminary tuning of application software as needed

21.3.2 Site Functional and Performance Test

The site functional and performance test (“site test”) shall be comprised of a subset of the

functional and performance tests conducted in FAT. The tests to be performed shall be

proposed by the Contractor and approved by the POWERGRID. These tests shall be extended

as necessary to test functions simulated during the FAT, such as communications with all field

devices and all other systems that interface with the CDCS.

21.3.3 Site Cyber Security Audit The site cyber security audit shall repeat the audit performed during factory testing.

21.3.4 Test Approval

The Supplier shall maintain a complete computer record of all test results with variance

reporting and processing procedures for approval by POWERGRID. In the event that the

AMR System does not successfully pass any portion of the Acceptance Testing, the Supplier

shall notify the POWERGRID of the specific deficiency. The Supplier shall promptly correct

the specified deficiency, which will then be re-tested until successful.

22. TRAINING REQUIREMENTS

Comprehensive training programs shall be provided to enable the efficient and effective use and operation of the deployed AMR system by users of the system, and to develop a self-sufficient hardware and software support team within the POWERGRID.

Training shall include, where appropriate, a combination of formal training classes, workshops, as well as continuous (informal) knowledge transfer from the Supplier’s technical specialists to the personnel of POWERGRID and its constituents during the deployment process and after the commission of the AMR System. In-person training sessions could be offered at Supplier’s location or at the POWERGRID’s own facilities or any other locations of choice by both parties.

Training programs for system users shall include, but not limited to:

• System overview including system functionalities and features • System configuration and operations oriented training • System alarms handling

• Local/Remote configuration procedures • Engineering oriented training for development/testing

Training programs for system hardware and software support team members shall include:

• System overview including system design and detailed as-built system configuration information

• System software maintenance • System hardware maintenance • Engineering oriented training for development/testing

• System diagnose and troubleshooting oriented training for engineers and technicians

The Supplier shall prepare and provide a description of the proposed training programs with

course content, duration, and technical level of the instruction for review and approval by the

Procurement Entity at the beginning of the deployment, and shall work with the

POWERGRID to schedule, organize and execute the approved training programs.

23. SUPPORT AND MAINTENANCE REQUIREMENTS

Supplier should provide onsite as well as remote support in order to keep system operational with system functionalities and performance in accordance with the specifications.

23.1 Scope of AMC

During warranty / AMC period, supplier is responsible for repair/ replacement/ modify/ rectify all times i.e. software, hardware either manufactured or bought out, updation of software used in AMR scheme without any extra charges to POWERGRID.

23.2 On-site support and maintenance

Supplier should maintain a team of skilled personals having sufficient knowledge of the system

in order to diagnose and set right any problem in AMR system in minimum time. Since, the

locations of DCUs under this AMR system is geographically spread across entire Western

Region, the supplier should locate its supporting personals so as any problem may be attended

within next working day or reporting.

Supplier should maintain a help desk operated from 0900 hrs to 1800 hrs on all days except

Sundays and national holidays. Supplier should maintain an online web based help desk system

for logging complaints and checking the resolution status. Help desk should be accessible by

the user through browser via Internet. Separate username and password shall be provided with

separate privileges for users of central site as well as DCUs site. DCUs site user should be able

view logs of complaints and status logged by that user only. However, user of central site should

be able to view of logged complaints and their status irrespective the initiator of compliant.

Any complaint shall remain open until and unless approved its closure by the central site user.

All logs should be suitably time stamped.

Supplier should post a resident engineer to central site (WRLDC, Mumbai) throughout the

warranty and AMC period in order to diagnose and set right any problem in AMR system in

minimum time. Resident engineer shall be provided with mobile phone for communication in

odd hours or for escalation of complaint. Supplier should maintain this Mobile phone live and

should maintain same number throughout the contract period. All expenditure on this phone

shall be borne by the supplier.

23.3 Remote support and maintenance No remote login is permitted.

23.4 Up gradation and patches

Supplier should keep updated all supplied software kernel/OS and application software with all latest patch and upgrade. 23.5 Maintenance and support of brought out items

Supplier should take back-to-back support from manufactures of brought out items like servers, printers and like items. However, supplier shall be responsible for all coordination work form OEM for all types of support and maintenance.

23.6 Maintenance and Support for Communication channels

Suppliers should be responsible for all coordination with communication channel service

provider like availability of channels, utilisation, data volume certification etc. Billing and

payment of monthly and/or yearly bills will also be settled by the supplier to communication

services provider. Channel utilisation charges and rental charges of communication channels as

billed by communication service provider shall be reimbursable to the supplier by

POWERGRID against original documents. Bidder should estimate the optimum plan of

service provider for each location & submit to POWERGRID before taking any connection.

Part-III: Technical Specifications of Meter Data Processing

(MDP), Energy Accounting (EA) and

Deviation Settlement Mechanism (DSM) Accounting

This section describes the envisaged system architecture of Meter data processing and Energy accounting in Western Region.

24. INTENT OF MDP, EA & DSM ACCOUNTING

The intent of MDP & EA is to provide the requirement details of Oracle Database oriented

Meter Data Processing Software having compatibility to exchange and share data / information

with similar Database systems that may be used by other RLDC / NLDC with a view to meet

requirements of Data Warehousing and Business Intelligence systems etc. The Client Interface

should be Browser based and report formats should be in user defined multiple formats like

PDF, MS Excel, CSV, Text etc. The Software is intended to meet the regional energy

accounting requirements for the commercial mechanism adopted in respect of bulk power

supplies and inter-State exchanges within and across a Region. The software will also have a

module for DSM accounting which is settled at pool level. This document also describes in

details of various functions like meter data - collection, formatting /conversion and facilities of

existing software (which is to be replaced with the new proposed database oriented software)

and proposed solution for meter data processing.

25. COLLECTION, PROCESSING AND COMPUTATION OF

METER

The respective constituents/agencies, in whose premises the energy meters are installed,

normally down-load the metered data from each of the meters on a weekly basis or as and when

requested by WRLDC. The respective constituent/agency ensures that the metered data from

each meter is downloaded and transmitted to WRLDC as per specified time schedule, in

accordance with relevant provisions of Indian Electricity Grid Code (IEGC) amended from

time to time. If complete meter data is not received from any location then the concerned

location is requested to send the relevant meter data. Moreover, each constituent/agency shall

also ensure the security of the metered data up to its delivery to WRLDC. All constituents shall

provide the required assistance/co-operation to WRLDC in this regard. Each station is also

requested to systematically keep back up of all data that are sent to WRLDC. Entire process is

divided into following steps:

25.1 Meter Data Collection from Different Location

At each metering location data is to be collected from the SEMs once every week. With one

data collecting device (DCD), data from about ten SEMs can be collected sequentially and

thereafter the collective set of meter data file is dumped into the local PC. For dumping meter

data from DCD to PC proprietary software given by respective suppliers of SEMs has to be

used. After downloading the meter data from each meter location, the respective

constituent/agency sends the data files normally through e-mail to WRLDC. These weekly data

should reach WRLDC latest by Tuesday noon as per relevant provisions of IEGC. Presently

special energy meters in use are supplied by three vendors (L&T, Secure & Elster). The raw

meter data files are non-readable and non-editable, thereby are naturally tamperproof. Raw

meter data files collected from SML make meters have *.MRI format, L&T make meters have

*.DAT format and Elster make meters have *.RM3 formats. Since these files are non-readable,

so these have to be first converted to *.NPC file (text format) as the first step in data processing

so that the meter data can be rendered readable and editable. It is better and also the general

practice to make NPC files at RLDCs to ensure data security and reduce human error.

25.2 Storing of Raw Data in a particular location

At WRLDC, data files are downloaded from emails and stored in computer in a folder (e.g.

ddmmyy). Since these data files are in *.MRI or *.DAT or *.RM3 file formats these files need

to be first converted into text (*.NPC) files (although some locations send *.NPC files along

with *.MRI, *.DAT and *.RM3 files, but NPC files sent from sites are generally not considered

and all *.MRI, *.DAT & *.RM3 files are converted into *.NPC files at WRLDC. After

converting into *.NPC files, these are stored in the same folder where the raw data files were

downloaded, i.e., ‘ddmmyy’.

Each file (*.MRI/*.DAT/*.RM3) contains one or more than one meter data from a particular

location. While saving these data files in ddmmyy folder, the following naming convention is

adopted:

“DDMMXXXN”.DAT e.g. 1306ARA.DAT, 1306ARA1.DAT, 1306ARA2.DAT etc.

Here DD => represents the day of a starting week i.e. Monday of a particular week irrespective

of the day on which meter data was actually collected; MM => represents months in number

format; XXX => First 3 letter of a particular location from where meter reading is being sent;

N => incremental no to represent more than one file sent from the same location.

Each file can contain more than one meter reading. Size of each file containing one meter

reading is generally about 15KB.

25.3 Converting Raw encrypted data into readable text file.

After receiving the *.MRI/*.DAT/*.RM3 files, they are converted into TEXT files, i.e., *.NPC

files. This conversion is done with the help of respective meter manufacturer’s proprietary

software. *.MRI files are converted into *.NPC files through SMARTGRID software supplied

by SML and *.DAT/*.MDT files are converted into *.NPC files with the help of

VINCOM/VINPLUS software provided by L&T and *.RM3 files are converted into *.NPC

files through RM3conversion Software provided by Elster.

25.3.1 SECURE Meters

Encrypted Secure meters data is converted using SMARTGRID software at WRLDC. All

*.MRI files are transferred to ddmmyy folder in D: drive before converting to text files (i.e.

*.NPC files) and get converted to *.npc files, stored in same location where *.MRI files are

stored.

25.3.2 L&T Meters

Encrypted L&T meters data is converted using VINCOM/VINPLUS Software at WRLDC.

L&T has developed a new application software – VINPLUS and have discontinued the

earlier VINCOM software. VINPLUS is compatible with both old batch of L&T SEMs

(already installed at various locations) as well as new SEMs. However, with VINPLUS raw

meter data files are created with the extension .DAT. All *.DAT files are transferred to

ddmmyy folder in D: drive before converting to text files (i.e. *.NPC files). During

conversion of the *.DAT files to text files using VINCOM the *.NPC files can be created in

the same folder where the *.DAT files reside. But in case of VINPLUS the *.NPC files are

created in a different folder and has to be manually shifted from the temporary folder to the

ddmmyy folder where the corresponding *.DAT files reside.

25.3.3 ELSTER Meters

Encrypted Elster meters data is converted using RM3 conversion Software at WRLDC. All

*.RM3 files are converted to text files (i.e *.NPC files) and can be saved at defined location.

25.4 Viewing of .NPC file/Structure of .NPC file

After conversion, all the *.MRI/*.DAT/*.RM3 files along with the corresponding *.NPC files

are transferred into relevant ddmmyy folder in D: drive. Data will be considered as valid data

only if it contains data of the relevant week period starting from Monday(previous week) to

Sunday (current week), i.e. at least 7 days data starting from Monday of the previous week.

Every *.NPC file has a week header for each meter data which gives the start date and end date

for which data is available, e.g.

WEEK FROM 0000 HRS OF 12-10-07 TO 1230 HRS OF 22-10-07

• For every day data there is a header section that gives METER NO, three cumulative register readings recorded at at 0000 HRS of the day and date of the day, e.g. NP-4201-A 63895.0 97845.8 74358.6 12-10-07

• Three cumulative registers are (i) WH register (ii) VAR register at high voltage (>103%) (iii) VAR register at low voltage (<97%).

• METER NO is of 9 characters, usually starting with NP (e.g. NP-0139-A). Character A or B depending upon whether the meter is connected with 1 AMP CT or 5 Amp CT secondary configuration.

• One day data consists of 96 blocks one for every 15 minute interval and is is organised in 6 rows, e.g.


NP-6269-A 78283.6 85180.4 00033.5 07-04-17

00 48 +21.86 47 +21.81 48 +21.62 50 +21.38 51--

04 50 +21.41 48 +21.69 50 +21.77 48 +21.81 50--

08 52 +22.28 48 +22.14 46 +21.62 48 +21.42 52--

12 50 +21.75 48 +22.05 49 +22.02 46 +21.99 49--

16 48 +22.70 46 +22.47 51 +21.93 51 +21.16 49--

20 51 +20.46 53 +20.20 51 +20.48 49 +20.54 49--

• Each row contains 16 blocks i.e. data for 4 hours.

• Each row begins with a 2 digit code indicating the time in HOURS, followed by 16 blocks of data.

• Each block represents 15 min. average data and consists of 2 data – 1st one is frequency code and 2nd one is active power flow in WH.

• Relation between frequency and frequency code is given below:

Freq (in Hz) = 49.5 + 0.01 X (FC)

Freq code consists of 2 digits ranging from 00 to 99 to indicate frequency from 49.50

Hz to 51.50 Hz with a resolution of 0.01 Hz.

(Please note that the above formula and frequency range is subject to existing provisions

of IEGC)

• In between frequency code and WH there may be a “*” mark preceding the active energy flow data if there is any voltage problem (V<70% during any instant in the particular 15 min. time interval).

• If any correction is done during the 15 min, there may be “aa” or “rr” marks corresponding to advance or retard of the clock appearing before the active energy flow data. There may also be a case of voltage problem as well as time correction occurring in the same 15 min block.

• At the end of 96 blocks the algebraic SUM of WH of all blocks is also given.

25.5 Modification/Editing in Text file

During conversion into text files (NPC files) every file has been converted into corresponding

text file as “DDMMXXXN.NPC” where DD and MM correspond to the Monday subsequent

to the week for which data is being processed. Extra meter readings, multiple readings of the

same meter and readings for the period not relevant to the week under consideration are deleted

from the text file. If some correction of date etc is required it is done in the text file and saved

into corresponding folder where data were initially downloaded.

25.6 Appending data files into a single file

After receiving weekly SEM data from all locations, they are converted into TEXT files and

thereafter combined to make a single file. Once all *.DAT/*.MRI/*.RM3 files are converted

into .NPC files they are available in the folder ddmmyy. One NPC file may consist of data for

one meter or more than one meter. Subsequently all the text files are merged into a single large

file which contains meter data for the relevant period for all meters installed across the region.

The appended file is named as “DDMMSREA.NPC”. A program APPEND.EXE is used for

this purpose. The appended file is then copied into the “SEMAZE1” folder for further

processing.

APPEND.EXE: APPEND.EXE simply combines all *.NPC files starting with the same

“DDMM”. The combined file name is “DDMMSREA.NPC”. It is better to make a single file

“DDMMSREA.NPC” which includes all the data for one week. This can be given as the input

to the data processing program. (REA2006 at the create DATA base option) This appended

file can also be stored easily as a backup file.

Database Format:

For each meter data,

• 1st header line contains the period for which meter data is available.

• 2nd line contains the meter serial number (NP-xxxx-A or NP-xxxx-B) followed by 3 (three) cumulative register data for active energy, recative energy (High) and reactive energy (Low) recorded at the beginning of the day and then the date.

• The 3rd line is a blank line

Contents of 4th line to 9th line represents active energy data arranged in 16 columns X

6 rows for each 15 minute time block.

• First field of 4th – 9th line indicats the staring hour in a 2-digit code say 00,04,08, …,20.

• Each 15 minute block data consists of 2-digit average frequency and active energy arranged as +xx.xx or –xx.xx, i.e either export(+ve) or import(-ve) figure in 2-digit integer upto 2 decimal.

• In line 9 after block data, the algebraic summation of energy data of all blocks are given..

• The 10th line contains the same data as the 2nd header line but for the beginning of immediate next day.

• Thereafter, format repeats from 3rd line to 10th line with data being that for the subsequent day(s).

A sample format for the meter data after conversion to text file is reproduced below:


NP-6850-A 30620.6 75393.4 04173.3 20-08-11

00 44 -11.00 39 -10.84 47 -10.85 50 -10.82 …………………… 48 -10.63 52 -10.50

04 54 -10.58 48 -10.51 48 -10.50 43 -10.33 …………………… 48 -10.49 48 -08.82

……..

……..

20 21 -12.33 28 -11.74 13 -11.68 24 -11.71 …………………… 48 -10.49 48 -08.82

NP-6850-A 29688.2 75353.1 04173.3 21-08-11

Limitation – Presently, while processing weekly SEM data, date wise folders of all meter data

present in SREA file are generated and previous date folder contents created earlier are

overwritten. Users need to manually edit the SREA file to delete unnecessary records to avoid

the above mentioned limitation. Moreover, there is no check to identify presence of multiple

instances of meter data.

Desired Functionality for Collection and Computation of Meter Data:

As the end to end metering system is supplied by a single successful bidder and all meters data

will be available at CDCS through AMR system, database creation in MDP S/W and

computation of meter data shall be done in a single click by designing a suitable interface

between MDP and CSCS at WRLDC.

While creating data base it should automatically discard all records for dates outside the desired

date range and shouldn’t repeat creation of old dated folders or create folders for dates

succeeding the last date of the desired date range.

It should retain single record for meter data thereby eliminate multiple instances of meter data.

As new Interface Energy Meters are designed for 5-min compatibility, all meter data

computations (Active energy, Reactive energy and Voltage) in MDP shall be done in 5-min

block wise only.

26. Concept of Master Meter file

This file contains the list of - all meters installed at different locations across the region, all

relevant meters installed in adjacent region for inter-regional tie-lines and all relevant meters

considered for frequency data by the synchronously inter-connected electrical regions. This file

is named as ‘master.dat’ which contains multiple records. Each record corresponds to a

particular meter and has 5(five) fields, viz.,

1. LOC_ID Location Identity

2. METER NO. Meter serial number

3. CTR Current Transformer Ratio

4. PTR Potential Transformer Ratio

5. Status Main/Check/Standby

6. PLACE OF INSTALLATION Feeder where meter is installed

Meter records are listed in this file in a tabular format in following manner –

LOC_ID METER NO. CTR PTR Status PLACE OF INSTALLATION

KO-01 NP-0430-A 500 3636.3636 M 400 KV SIDE OF KORBA GT-1

KO-02 NP-0599-A 500 3636.3636 C 400 KV SIDE OF KORBA GT-2

KO-03 NP-0432-A 500 3636.3636 S 400 KV SIDE OF KORBA GT-3

Desired:

The new master file format would be as mentioned below.

Utility Name

Station Name

Location Description Meter No

Meter Type

HV Voltage

LV Voltage

HV current

LV current

There should also be provision to add new rows to master file to incorporate new meter details.

27. Concept of Master Frequency Meter

The frequency recorded by Special Energy Meter which is used for DSM accounting by all

regions (i.e. WR, NR, NER, ER and SR) is called as Master Frequency Meter. Master Frequency

Meter(NP-2657-A) is installed at Korba(NTPC) in WR on 400KV Korba-Mahan line. Weekly

metered data of this meter is regularly sent by WRLDC to every other RLDC.

Moreover, NP-8804-A and NP-8803-A installed at Durgapur sub-station of ER are used as 1st

back up Master Freq Meter and 2nd back up Master Freq Meter respectively in case data for

any block, any day or any week was not recorded by NP-2657-A installed at Korba due to any

reason such as opening of line or meter failure etc.

28. Concept of Fictitious Meter & Configuration File

Sometimes it is required for convenience in simplifying the calculation process to treat a

combination of meters as a single entity. e.g.

(i) Total drawal of a State

(ii) Total relief from a generating station

(iii) Total transaction of energy between two regions.

In such cases, each combination of meters can be treated just like a SEM and is referred as

FICTITIOUS METER (FICTMTRS). A file named “FICTMTRS.DAT” lists all fictitious

meters and consists of multiple records. Each record corresponds to a fictitious meter and has

3(three) fields, viz.,

1. LOC_ID Fictitious meter Identity

2. FICTMTRS_NO Coded description of fictitious meter

3. DESCRIPTION Complete description of fictitious meter

Fictitious meter records are listed in this file in a tabular format in following manners –

LOC_ID FICT_METER_NO Description

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

KO-91 KO-TOT-LN FARAKKA NET GENERATION (LINES & ATR)

KO-93 KO-TOT-CL FARAKKA NET GENERATION (LINES & ATR CHK)

KO-94 KO-U6_NET FARAKKA UNIT 6 NET GENERATION

KO-92 KO_STG_1 FARAKKA NET GENERATION EXLUDING UNIT 6

Every fictitious meter is the summation of a combination of two or more physical meters and

one or more fictitious meters. Physical meters are the actual meters which are installed at

different locations and store the energy data. The formula to calculate energy against a fictitious

meter power based on the above concept is specified accordingly in a configuration file named

“FICTMTRS.CFG” in following manner –

START

01 (KO-91) M9

+(KO-08) +(KO-09) +(KO-10) +(KO-11)

+(KO-12) +(KO-13) +(KO-17) +(KO-15) +(KO-16)

02 (KO-93) M9

+(KO-15) +(KO-22) +(KO-23) +(KO-24)

+(KO-25) +(KO-26) +(KO-27) +(KO-28) +(KO-29)

03 (KO-94) M2

(KO-30) -(KO-31)

04 (KO-92) M2

(KO-91) -(KO-94)

Here the first line consists of Fictitious meter ID and number of real and fictitious meters (if

any) involved. Second line contains the formula used to compute the energy corresponding to

the fictitious meter mentioned in the first line. Please note that, the formula might as well

contain one or more fictitious meters other than itself.

For any particular calculation, if Main meter reading is not available then check meter/standby

meter reading is accordingly used as substitute in relevant section of FICTMTRS.CFG file.

29. Concept of PAIRS.DAT File

This file gives the location ID of main meter and standby meter and the permitted pair tolerance

for each pair. Main meters are those which are connected on 400 kV side of ICT or generator

side of power station or sending end of interstate lines. The standby/check meters are on the

other end. Standby meters are connected in reverse polarity so that sum of both MWh is zero

in ideal condition. Suppose the power flow is from main meter to standby meter, the main

meter gives a +ve value and standby meter gives a –ve value and vice versa. Tolerance value in

MWh for a 15 min block in +ve direction & -ve direction is given in this PAIRS.DAT,

depending upon transformer /Line loses & CT/PT errors.

The given tolerance value towards +ve side is called X value. The tolerance value towards –ve

side is called Y value.

All such pairs are created/listed in a file named “PAIRS.DAT” as multiple records. Each record

corresponds to a pair of meter and consists of 5(five) fields, viz.,

1.MAIN Location ID of main meter

2.STANDBY Location ID of standby meter

3.X Tolerance value in +ve direction

4.Y Tolerance value in -ve direction

5.DECSRIPTION Description of the pair

Paired meter records are listed in this file in a tabular format in following manners –

MAIN STANDBY X Y LINE DETAILS

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

WR-01 ER-01 2.0 1.5 Raigarh-Budipadar-1



Limitations: Absolute tolerance values are often misleading in case of low quantum of energy

flow across the electrical element.

Desired: The tolerance values should be in percentage so as to overcome the above limitation.

There should also be provision to replace the main meters with standby/check meters having

tolerance values beyond the defined tolerance limit automatically/as and when required.

30. REA2006

This is an application software (s/w) currently being used by WRLDC to process meter data

contained in “DDMMSREA.NPC” file.

Limitation:

This s/w becomes non responsive when any other key is pressed apart from enter key.

This s/w is menu based and has following functionalities – (Current Functionality)

Menu

=>

Init View Check Compute Account Option Help

Data

Correctness

WH Day

Data

Voltage

Problem

Compute

Energy

MWH

Output

Previous Set

up

About

Create Data

Base

MWH

Day Data

Time

Correctio

n

Pair

Check

MVARH

Output

Frequency

Tolerance

SEM

Data

Data

Received

FICT

MWH

Day Data

Prev.

Week

Data

Gen

Schedule

Load

Curve

All Pair

Blocks

Program

Brief

Data Not

Received

Any File Frequenc

y Problem

Drawal

Schedule

Utility

Curve

Pair Analysis Config

Files

View Raw

Data

Watt

Hour

Problem

Compute

FICTMT

RS

Total

Energy

DOS Shell Regional

Account

Algebric

Sum

Energy

Account

(REA)

Data

Availability

Warnings

All Check All Check

Report

Gen

Auto

Replacement

Pair

Check

Report

Gen

Prep Adj

Column

Value

Description of each menu item and corresponding sub-menu items is given in the following

sections along with limitations (if any) and desired functionality.

30.1 Init

Under this menu, following sub-menu items are listed as per existing sequence –

Data Correctness

Create Database

Data Received

Data Not Received

View Raw Data

Limitations: NIL

Desired Functionality: NIL

30.1.1 Data Correctness

REA2006 processes the appended text file (DDMMSREA.NPC file) containing all SEM data

for completeness, correctness and computation. This ‘DDMMSREA.NPC’ file generally

contains data for all meters of the region, however, data from a few meters may not be available

due to force majeure conditions.

On executing data correctness feature of the s/w, status regarding data correctness is available

in a corresponding file named ‘DDMMSREA.CHK’. In this file if criteria for data correctness

is satisfied, then “Status OK” is marked against the particular SEM for the relevant period else

an error is logged against the particular SEM. In case error is detected in data correction stage,

then corresponding section of DDMMSREA.NPC file is edited to eliminate the error.

Data correctness may contain following checking procedures –

Syntax error checking e.g. wrong naming or meters, unwanted characters present in the file,

data is not properly formatted within data block, absence of meter data – sometimes one or

more block of data might get missing from input files for particular days.

The log file “DDMMSREA.CHK” file thus created is simultaneously displayed/scrolled on the

PC monitor till the end whenever data correction facility is executed.

Log File: A log file by name ‘DDMMSREA.CHK’ gets created whenever this process is

executed and stored under ‘D:\SEMAZE1\’ folder . It has following format –

Meter NP-5819-A from 19-08-11 to 29-08-11 Status OK

Meter NP-6892-B from 19-08-11 to 29-08-11 Status OK

Meter NP-6875-A from 19-08-11 to 29-08-11 Status OK

Meter NP-6860-A from 18-08-11 to 29-08-11

Error Suspected in Line 16313 Column 114


It also shows error logs against the particular SEM if data correctness check fails., say for eg.,

Meter NP-6860-A from 18-08-11 to 29-08-11


Error messages corresponding to different criteria involved during data correction need to be

collected for effective reporting and troubleshooting by users.

Limitations: NIL


30.1.2 Create Data Base

After successful error elimination at data correction stage, relevant database is created through

the ‘Create Data Base’ facility. Database is created day wise for all the days whose data is

available in ‘DDMMSREA.NPC’ file wherein the meter wise data files are created/stored for

further processing.

Similar to data correction facility here too the creation of data base is simultaneously

displayed/scrolled on the PC monitor each time this facility is executed.

Limitations: NIL


30.1.3 Data Received

This functionality is used to check for the locations from where data has been received. This

checking is done by comparing meter data available in ‘DDMMSREA.NPC’ file and Master

meter data records. It shows the list of meters whose data is present in ‘DDMMSREA.NPC’

file. It generates and overwrites corresponding log files ‘DDMMSREA.RXD’ and by name

‘DDMMSREA.RX_’ each time this facility is executed.

Log File:

A log file ‘DDMMSREA.RXD’ created whenever this process is executed is stored under

‘D:\SEMAZE1\’ folder. It has following format –

Locations where from Data Received

FK-08 NP-5202-A .3636 400 KV FARAKKA (NTPC)-KAHALGAON (NTPC)-1

FK-09 NP-5200-A .3636 400 KV FARAKKA (NTPC)-KAHALGAON (NTPC)-2

FK-10 NP-5228-A .3636 400 KV FARAKKA (NTPC)-DURGAPUR (PG)-1

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

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

NO OF LOCATIONS - DATA RECEIVED – 420

The other log file ‘DDMMSREA.RX_’ also created simultaneously whenever this process is

executed is stored under ‘D:\SEMAZE1\’ folder. It has following format –

NP-6850-A

NP-6851-A

NP-6876-A

………………

………………

NP-6878-A

Limitations: The log file ‘DDMMSREA.RXD’ currently lists out the records from Master

meter data records for those meter data which are present in the ‘DDMMSREA.NPC’ file w.r.t

Master meter data records irrespective of whether data for the relevant date range for the

intended week is available or not. Moreover, it creates another log file by the name

‘DDMMSREA.RX_’ which lists only those meters as per serial no. whose data is present in

‘DDMMSREA.NPC’ file. These log files are of not much value/use to conclude whether data

for relevant date range is available or not.

Desired Functionality:

The log file ‘DDMMSREA.RXD’ should rather list out only those records from Master meter

data records for which meter data for desired date range sorted on the basis of meter data

header information is available in ‘DDMMSREA.NPC’ file.

30.1.4 Data Not Received

In addition to the ‘Data Received’ facility, there is another facility to ascertain the meters whose

data has not been received. This checking is done based on a comparision of

‘DDMMSREA.NPC’ file and Master meter data records. It shows the list of meters whose data

is not present in ‘DDMMSREA.NPC’ file. It also generates/overwrites a corresponding log file

‘DDMMSREA.NRX’ each time this process is requested.

Limitations: The log file ‘DDMMSREA.NRX’ currently lists out the records from Master

meter data records for those meters whose data are not present in the ‘DDMMSREA.NPC’

file w.r.t Master meter data records. This file will however fail to list a meter even if data for

that meter for any date (may not be the desired dates) exist in the file. So there is no way to

ascertain that particular meter data for relevant dates are missing in ‘DDMMSREA.NPC’ file.

These log files are of not much value/use to conclude whether data for relevant date range is

missing or not.


The log file ‘DDMMSREA.NRX’ should rather list out only those records from Master meter

data records for which meter data for desired date range sorted on the basis of meter data

header information are not present in ‘DDMMSREA.NPC’ file. Same change for log file.

Log File:

The log file ‘DDMMSREA. NRX’ created whenever this process is executed is stored under

under ‘D:\SEMAZE1\’ folder. It has following format –

Locations where from Data Not Received

KO-01 NP-0430-A .3636 400 KV SIDE OF KORBA GT-1



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

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

NO OF LOCATIONS - DATA NOT RECEIVED – 76

30.1.5 View Raw Data

This functionality is used to view meter data for all date range using this software based on

SREA file data.

Limitation: Currently this option is unable to show huge amount of data and declares ‘out of

memory’ exception.


It should show all meter data for entire date range and should not have memory

limitation/exception.

30.2 View


WH Day Data

MWH Day Data

FICT MWH Day Data

Any File

30.2.1 WH Day Data

This functionality is used to view Watt Hour data for selected meters for a particular date range.

Whenever this menu option is clicked, a user interface comes up with following options:

Master Meter List - single/multiple meter can be selected from the meter list

Date Range Calendar - desired date range can be selected from the calendar dates

Once these inputs are provided, this software will try to find all the available data from different

folder location those are created after ‘Create Data base’ process.


Data needs to be shown as per original sequence of master meter list in master.dat file.

30.2.2 MWH Day Data

This functionality is used to view Mega Watt Hour (MWH) data for selected meters for a

particular date range.




Once these inputs are provided, this software will try to find all the available data from .MWH

files under different date folder location those are created after ‘Compute Energy’ process. Here

only Mega Watt Hour calculation is shown to the users by removing frequency information

from those files. MWH is calculated in following manner –

MWH = (WH * CT * PT) / 10e6

Where WH means watt hour reading and CT and PT represents current transformer ration and

voltage transformer ratio taken from the master.dat file for a particular meter for which MWH

is being calculated.


Data needs to be shown as per original sequence of master meter list in master.dat file.

Frequency code needs to be removed from MWH files.

Adding validation of voltage problem on MWH files.

30.2.3 FICT MWH Day Data

This functionality is used to view Mega Watt Hour (MWH) data for selected fictitious meters

for a particular date range.


Fictitious Meter master List - single/multiple meter can be selected from the meter list


Once these inputs are provided, this software will try to find all the available data for fictitious

meters from .MWH files under different date folder location those are created after ‘Compute

Fict. Energy’ process. Here only Mega Watt Hour calculation is shown to the users by removing

frequency information from those files.


Data needs to be shown as per original sequence of fictitious meter master list in

FICTMTRS.dat file.

Frequency code needs to be removed from MWH files.

Adding validation of voltage problem on fictitious meter MWH files.

30.3 Check


Voltage Problem

Time Correction

Prev. Week Data

Frequency Problem

Watt Hr Problem

Algebric Sum

All Check

30.3.1 Voltage Problem

This functionality is used to view voltage related problem in recorded data. It also generates log

files each time this request is processed.





folder location those are created after ‘Create Data base’ process. It will record voltage problem

if it finds any voltage record preceded by ‘*’ marks. This ‘*’ marks indicates that there is a

problem in Voltage supply either no voltage or failure of voltage supply.

Message Shown:

In case, if no data present at all for the selected meter and date range –

Data is not available on 13-06-11 for FK-01 NP-0430-A


In case, if there is voltage problem for a particular meter data –

Voltage problem in Meter FK-14 NP-5211-A on 13-06-11 Hour 8 Block 3

Voltage problem in Meter FK-14 NP-5211-A on 13-06-11 Hour 9 Block 0


Currently it shows only an error message stating that “voltage problem in...” It’s currently not

showing the exact nature of the problem like failure of voltage supply or no voltage at all.

Proper error message needs to be shown to the user. The logic is if any records showing 0.0

with “Z” mark, it means there is no voltage at all for 5minute duration. But if a record shows

certain value with “*” mark, it means there was a temporary Voltage supply failure within the

5 minute.

Log file Name: A log file by extension will be created under “Readings\SEMBASE\CHK”

folder. This is a simple text file with .VPR extension.

Log file Naming format -> DDMMYY(DD + date range) + (if possible adding time in order

to avoid file override)

30.3.2 Time Correction

This functionality is used to view whether any time adjustment has been done in recorded data.

It also generates log files each time this request is processed.





folder location those are created after ‘Create Data base’ process. It will record the time

adjustment if it finds any meter data record preceded by either ‘aa’ or ‘rr’ marks. If any

correction is done during the15 min, there may be “aa” or “rr” corresponding to time advance

or time retard execution.

Message Shown:

In case, if any time correction is done, it will show following message –

Time Adjustment in Meter KH-21 NP-5259-A on 13-06-11 Hour 11 Block 0

Time Adjustment in Meter KH-21 NP-5259-A on 13-06-11 Hour 11 Block 1


Currently it shows only an error message stating that ‘Time adjustment in..’. It’s currently not

showing whether the time adjustment is corresponding to advance or retard of the clock.

Proper error message needs to be shown to the user. The logic is to explicitly mention whether

the time adjustment has been done by advancing or retarding the clock depending on ‘aa’ or

‘rr’ marks.


folder. This is a simple text file with .TCR extension.



30.3.3 Prev. Week Data

This functionality is used to view whether any previous records exist in the current data or not.

It might be possible that some old data is sent along with current data.





folder location those are created after ‘Create Data base’ process. It will show old records if it

finds any.


folder. This is a simple text file with .PWK extension.



30.3.4 Watt Hr Problem

This functionality is used to view whether there are any zero voltage problems. That means no

current flows across the wire which results in a zero voltage data recorded my meter.




Once these input are provided, this software will try to find all the available data from different

folder location those are created after ‘Create Data base’ process. It will show zero voltage

problems for those meters which have recorded 0.0 in any particular time block.

Message Shown:

In case, if any zero voltage problem occurs, it will show following message

No Flow in Meter KG-02 NP-5852-A on 13-06-11 Hour 14 Block 1

No Flow in Meter KG-02 NP-5852-A on 13-06-11 Hour 14 Block 2

Log file Name: A log file by extension will be created under “Readings\SEMBAS\CHK”

folder. This is a simple text file with .WHR extension.



30.3.5 Algebraic Sum

This functionality is used to check whether the summation of all 96 block energy readings for

a particular day is equal to the difference of 2 consecutive days active energy cumulative register

readings.




Once these inputs are provided, this software will try to find all the differences in the algebraic

sum as mentioned above.

Message Shown:

In case data is not available –




In case if there is any difference in algebraic sum –

Algebraic sum is Not Correct for Meter EM-02 NP-6027-A on 13-06-11 -> 9.72





The right most decimal numbers are found by subtracting sum of 96 block power readings

from the difference of active energy cumulative register for 2 consecutive days. It should be

ideally 0 if every data is correctly recorded.


There should be some option for considering a certain tolerance if any difference is detected

as per the above functionality so that if the difference is within tolerance level, it should not

show error message.

Log file Name: A log file by extension will be created under “Readings\SEMBAS\CHK”

folder. This is a simple text file with .ASM extension.



30.3.6 All Check

This functionality is used to view all problems mentioned above at one place. Here all log files

would be generated separately under “Readings\SEMBASE\CHK”. But all those problems

will be shown to users at a single place.

30.3.7 Compute


Compute Energy

Pair Check

Gen Schedule

Drawal Schedule

Compute Fict. Meters

30.3.8 Compute Energy

This functionality is used to calculate the actual amount of power drawn in Mega Watt Hour

(MWH) for selected meters for a particular date range.




Once these inputs are provided, this software will try to find all the available .NPD (WH) output

files generated after ‘Create Database’ process for selected meters and date range. If data is

available for particular meters and date range, actual power is calculated in Mega Watt-hour and

corresponding .MWH files under different date folder location (in same location of .NPD file)

are created. Here only Mega Watt Hour calculation is shown to the users by removing frequency

information from those files. MWH is calculated in following manner –

MWH = (WH * CT * PT) / 10e6

Where WH means watt hour reading and CT and PT represents current transformer ratio and

voltage transformer ratio taken from master.dat file for a particular meter for which MWH is

being calculated.


Compute energy functionality shall be performed by MDP automatically when data is imported

by MDP from CDCS.

When data is imported to MDP, all 5-min block wise Active energy, Reactive energy and voltage

values are to be get multiplied by suitable multiplication factors taking the inputs from master

file.

All computations in data processing S/W shall be dine in 5-min block wise only.

30.3.9 Pair Check

This functionality is used to calculate tolerance level of main meters and their corresponding

standby meters for a particular date range.


Main meter-Standby meter List - single/multiple pairs can be selected. (main– standby

format)


Once these inputs are provided, this software will try to calculate tolerance level of main meter

and its standby meters in “Pairs.dat” based on .MWH output files generated after ‘Compute

Energy’ process. If system finds the tolerance level out of range which is defined in “Pairs.dat”,

it should show error message to the users and generate log files as well.


folder. This is a simple text file with .PIR extension.


to avoid file override).

Message format is shown below:

Main BI-01 NP-5841-A on 28-06-11 at 16:45 block is not matching

with that of standby ER-01 NP-6063-A reading -30.96 28.82 -

> -2.14



> -2.32

DAY TOTAL on 27-06-11 of BI-02 NP-5840-A is not matching with

that of ER-02 NP-6069-A -> -4327.34 4476.69



> 2.09



> 2.20


It should calculate tolerance level based on percentage difference in power reading of main

meter and standby meters. But for that percentage tolerance level needs to be provided in

“Pairs.dat” file instead of actual tolerance level. If percentage difference is greater than a

predefined limit, main meter should automatically/by user acceptance be replaced with

check/standby meter in energy computation.

30.3.9.1 Compute Fict. Meters

This functionality is used to calculate the fictitious meter power reading in Mega Watt Hour

(MWH) for selected fictitious meters for a particular date range.


Fictitious Meters Master List - single/multiple meters can be selected


Once these inputs are provided, this software will try to find all the available .MWH output

files generated after ‘Compute Energy’ process for selected meters and date range. If data is

available for particular meters and date range, fictitious meter power is calculated in Mega Watt

Hour based on the formula listed in ‘FICTMTRS.CFG’ file and stored as corresponding .MWH

files under different date folder location (in same location of .NPD file) are created. Here only

Mega Watt-hour. For example,

Fictitious meters are listed in Master Fictitious Meter file (FICTMTRS.DAT) as –

LOC_ID FICT_METER_NO Description

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

FK-91 FKK-TOT-LN FARAKKA NET GENERATION (LINES & ATR)

Now, the formula to calculate the power for that fictitious meter is written down in

“FICTMTRS.CFG” in following manner –

START

01 (FK-91) M9

+(FK-08) +(FK-09) +(FK-10) +(FK-11) +(FK-12) +(FK-13) +(FK-

17) +(FK-15) +(FK-16)

Here the power of FK-91 fictitious meter is calculated by summing up power of all 9 meters

mentioned in the formula. A file by name ‘FKKTOTLN.MWH’ will be generated in the same

location of .NPD files in same format as other .MWH files are generated for actual meters

installed in various locations.

Limitation: Currently users are handicapped by the restrictions in the number of fictitious

meters that can be included in fictitious meter master list “FICTMTRS.DAT”. If they want to

introduce additional fictitious meters, they need to delete some existing fictitious meters to

accommodate the new ones. Moreover, currently only addition (+) and subtraction (-)

operation is supported by the program to compute fictitious meters.


Showing voltage problem on MWH files by putting */Z marks if any of real meter reading

involved in the computation of the fictitious meter has voltage problem.

It should additionally support multiplication and division operation while calculating fictitious

meter using the formula mentioned in configuration file.

It should generate log files to let users know what are the files generated during computation

process and unavailability of data as well (if there is any). Message will be something like –

Computing energy in MWH on 13-06-11 for FK-91 FKK-TOT-LN

If data is not available it should show error message something like -

File\SEMBASE\...MWH not found

Data is unavailable for on 13-06-11 for FK-91 FKK-TOT-LN

30.4 Account


MWH Output

MVARH Output

Load Curve

Utility Curve

Total Energy

Energy Account (Regional)

All Check Report Gen

Pair Check Report Gen

30.5 MWH Output

This functionality is used to view desired active MWH power output in a customized and more

user-friendly format. The MWH output is calculated based on real meter MWH output and

fictitious meter MWH output.

There is a configuration file named “out_mwh.dat” where items and their corresponding file

names are listed. This is totally user defined and customizable.

SL_NO ITEM CONFIG_FILE_NAME

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

1 REG_MWH RGN_MWH.CFG

2 FK1_MWH FK1_MWH.CFG

3 FK2_MWH FK2_MWH.CFG

Against each item the corresponding configuration file is defined as per desired

format/structure and resides in the same folder as rea2006 so as to create and store the desired

output files, i.e., DDMMYY.xxx, where xxx is a three character alpha code designated to the

particular entity.


List of output MWH items - single/multiple MWH items can be selected


While process files, it will show following type of message to the users –

Output MWH option of TALA-MWH

Active energy accounting for date 13-06-2011


folder location those are created after ‘Create Energy’ and ‘Create Fict. Energy’ process.

Calculation will be done based on real meter and fictitious meter MWH power and report will

be generated in a pre-defined format under “\SEMBASE\MWH” folder.

All report MWH output files will be created as per “DDMMYY.XXX” format where DD

represents date, MM represents month, YY represents year and XXX represents the three

character alpha code designated to the particular entity corresponding to each configuration file

name for each item listed in “out_mwh.dat” file.

Limitation: Currently only 45 items can be included in the configuration file “out_mwh.dat”

and can be processed. Current system is incapable of handling more no of items in

configuration file. Moreover the alpha codes are restricted to 3(three) characters only.


Currently it shows and process only 45 no of items which is a handicap. S/w should be capable

of handling more items. Limitation of using 3(three) character alpha codes for the entities

should also be addressed suitably.

Software shall have user option for generation of reports either in 15-min or 5-min whereas

entire computations in S/W are in 5-min block wise only. If user selects 15-min option, S/W

should generate the output file for selected constituents in existing 15-min formats by averaging

each three 5-min block values to 15-min average values.

30.5.1 MVARH Output

This functionality is used to view desired reactive MVARH power output in a customized and

more user-friendly format. The reactive MVARH output is calculated based on real meter

reactive MVARH power output and fictitious meter reactive MVARH power output.

Similar to the requirements for MWH output, there is a configuration file named

“out_mvar.dat” where items and their corresponding file names are listed. This is totally user

defined and customizable.

SL_NO ITEM CONFIG_FILE_NAME

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

01 BSISTMVAR BS3_MVAR.CFG

02 GCISTMVAR GC3_MVAR.CFG

03 WBISTMVAR WB3_MVAR.CFG

Accordingly, against each item the corresponding configuration file is defined as per desired

format/structure and resides in the same folder as rea2006 so as to create and store the desired

output files, i.e., DDMMYY.xxx, where xxx is a three character alpha code designated to the

particular entity.

Whenever this menu option is clicked, a user interface comes up with following options to

select:

List of reactive output MWH items - single/multiple MWH items can be selected


While process files, it will show following type of message to the users –

Output MWH option of BSISTMVAR

Reactive energy accounting for date 13-06-2011


folder location those are created after ‘Create Energy’ and ‘Create Fict. Energy’ process.

Calculation will be done based on real meter and fictitious meter reactive MVARH power and

report will be generated in a pre-defined format under “\SEMBASE\ MVARH” folder.

All MVARH output files will be created as per “DDMMYY.XXX” format where DD

represents date, MM represents month, YY represents year and XXX represents the three

character alpha code designated to the particular entity corresponding to each configuration file

name for each item listed in “out_mvar.dat” file.

Limitation: Though not confirmed, currently only 45 items can be included in the

configuration file “out_mvar.dat” and can be processed. Current system is incapable of

handling more no of items in configuration file. Moreover the alpha codes are restricted to

3(three) characters only.


Current limitation of number of files that can be defined in “out_mvar.dat” and 3(three)

character alpha codes for the entities should be addressed suitably.

Show mvar calculation block wise if possible when meters with such capability (presently VAR

data is recorded day-wise and not block-wise in respective cumulative registers under voltage

high and voltage low conditions) are introduced in the grid.

30.5.2 Load Curve

This functionality is used to display graphical reports based on meter output data.

Similar to the requirements for MWH output, there is a configuration file named

“LOADCURV.DAT” where items and their corresponding file names are listed. This is totally

user defined and customizable. The items are usually selected from the master meter list

“MASTER>DAT” or the fictitious meter list “FICTMTRS.DAT”.

LOC_ID NAME Description

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

AS-11 NP-0359-A UMTRU-KAHELIPARA FDR-I

AS-12 NP-0360-A UMTRU-KAHELIPARA FDR-II

TR-51 TRI-DRWL TOTAL DRAWAL BY TRIPURA


Master Item List - single/multiple items can be selected


Once these inputs are provided, graphical report will be displayed on the desktop one after one.

Graphical reports will have following format for display -

Load Curve of Total Injection for Farakka

Location Id: FK-01 Date – 13-06-2011

Power

in MWH

(plotted on

Primary axes)

Time

Limitation: Current there is no way to save this graphical report and print them as well if

necessary.


Frequency In

Hz

(plotted on

Secondary axis)

Save this graphical report in user defined file formats (image file/pdf files) in pre-defined

location. Both x-axis and y-axis should be customizable and scalable. The time scale should be

selectable in time blocks or hours

30.5.3 Total Energy:

This functionality is used to view total active MWH power output for a particular date range

and time range.


Enter start date and end date

Enter start time and end time

Location Id of a meter

Once these inputs are provided, system will try to find out all available meter data for that

selected date range and time range. It will generate a file with .TOT extension under

“SEMBASE\TENGY\ddmmd1d1m1m1” folder where dd and mm represent starting date

and month and d1d1 and m1m1 represent end date and end time block respectively.

30.5.4 All Check Report Gen

This functionality is used to generate a formatted report based on all problems detected in

meter output files during “Check” process as mentioned above.


Master Meter List - single/multiple meter can be selected

Date Range Calendar - desired date range can be selected from calendar dates

A report file of .REP extension would be generated separately under

“Readings\SEMBAS\CHK”. The name of the file would be of type “ddmmyyd1d1” where

dd, mm, yy represent date, month and year respectively and d1d1 represents end date in a

selected date range.

The report would be generated in the following format –

Date Loc-ID Meter No NO Flow Watt hour Freqency Voltage Time Correction Algebraic Sum Previous

Week

27-06-11 FK-08 NP-5202-A NO NO YES NO NO NO NO



30.5.5 Pair Check Report Gen

This functionality is used to generate a formatted report based on all problems detected during

pair meter checks.


Pair Meter (main - standby) List - single/multiple pairs can be selected

Date Range Calendar - desired date range can be selected from calendar dates

A report file of .PRE extension would be generated separately under

“Readings\SEMBAS\CHK”. The name of the file would be of type “ddmmyyd1d1” where

dd, mm, yy represent date, month and year respectively and d1d1 represents end date in a

selected date range.

The report would be generated in the following format –

Date Main Meter Stand by Meter Block no. M.Met Reading S.Met Reading Difference

28-06-11 NP-5841-A (BI-01 ) NP-6063-A (ER-01) 16:45 -30.96 28.82 -2.14

03-07-11 NP-5841-A (BI-01 ) NP-6063-A (ER-01) 12:30 -29.35 27.04 -2.32

27-06-11 NP-5840-A (BI-02 ) NP-6069-A (ER-02) Day total -4327.34 4476.69 149.35

30.6 Options

30.6.1 All Pair Blocks

This is a duplicate functionality of “Pair Check” under “Compute” menu. This a pair checking

process (main meter – standby meter) for all listed meter pairs in “Pairs.Dat”.

30.6.2 Pair Analysis

This is a duplicate functionality of “Pair Check” under “Compute” menu. This a pair checking

process (main meter – standby meter) for selected meter pairs in “Pairs.Dat”.


• To remove all duplicate functionality.

• To remove pair check functionality from “Compute” menu and put it here. This check will be done at a single place by giving user option to either select all pair meters or selected pair meters.

• Should include time block while processing.

30.6.3 Data Availability

This is again a duplicate functionality of “Data Received” under “View” menu.


- To remove all duplicate functionality.

30.6.4 Auto Replacement

Exact functionality is not clear here.


30.7 New functionalities

These are required in view of various post processing validation of meter data which if built

into the s/w will result in quick, timely and effective intervention at RLDC stage in context of

meter data.

30.7.1 Pair Check Facility

• Provision for tolerance in %age should be separately configurable for every pair or user can select same %age tolerance for all pairs.

• Composition of individual pairs should be configurable with provisions for multiple meters against each component of the pair.

• Report when breach of tolerance is reported shall be of the following format:

DATE BLOCK END1_METER END2_METER ERROR(%)

(NAME OF FEEDER)

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

• Each pair whose data is available has to be listed in a master report for archival and future reference in a similar format as given above.

• If meter data is not available same shall not be listed in either of the above reports.

30.7.2 Time Drift Check Facility

• Generate Master Report having block wise freq codes of Master Frequency Meter vs. Individual Meter

• Allowable tolerance for time drift report should be configurable

• Time advanced and time retarded meters wrt Master Frequency Meter to be listed seperately

• Time correction activated, i.e., ‘aa’ or ‘rr’ detected report

30.7.3 Net Bus Check Facility

• Configuration for net bus and allowable tolerance shall be user defined

• Listing of each bus in a master report

• In case net bus for a particular bus is beyond tolerance, generate report, say,

DATE BLOCK NAME OF BUS ERROR(%)

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

• Complete block wise report for desired bus with all feeder, generator terminal, station transformer, ICT etc data should be available.

30.7.4 Voltage failure Check facility

• Report meters blockwise on detected of loss of voltage,i.e., ‘*’ detection in meter data

30.7.5 Algebraic Sum Check Facility

• Report all meters where sum of 96 block active energy data does not tally with total active energy recorded against each meter

30.7.6 Reverse Energy Flow Check

• Generate block wise report comprising of � Generators whose net metering shows “Drawal” � States whose net metering shows “Injection” � Report format may be as follows

DATE BLOCK NAME OF UTILITY REVERSE ENERGY(MWH)

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

30.7.7 Meter History Report Facility

• Facility to retrieve meter history details shall be provided for reporting and analysis, say to

list how many times the meter was reported faulty, when was it taken out of service, when

it was repaired, nature of fault, reinstallation date, etc.

30.7.8 File Set Archival Facility

• Day wise archival of complete File-Set comprising of Regional data file

(DDMMSREA.NPC), Master data files (MASTER.DAT, FICTMTRS.DAT,

LOADCURV.DAT), configuration files (*MWH.CFG, *MVAR.CFG, FICTMTRS.CFG)

so that all associated files can be recalled in case data processing has to be repeated at a

later date.

30.7.9 Report on energy flow

• A report on energy exchange through a particular meter / fictitious meter / group of

meters & fictitious meters during user defined period.

31. Conversion of data from 5-min to 15-min in AMR and MDP for DSM

accounting

Presently Scheduling and Settlement at ISTS level is done in 15-min block wise only. Special

Energy Meters data is used for computation of injection/drawal of all entities which are under

the jurisdiction of WRLDC. Injection/drawal computed from SEMs data is used in DSM

accounting which is settled at pool level in 15-min block wise. As the Interface energy meters

shall be designed for storing of data in 5-min block wise and same 5-min data will get processed

in data processing S/W, there would be necessity for converting 5-min processed data to 15-

min data for DSM accounting. For smooth conversion of 5-min data to 15-min data, following

issues are to be well addressed in AMR and MDP software.

• AMR system shall have the options to generate raw text files of IEMs in 15/5-min at

CDCS. Format of the raw text (*.npc) file in 15-min shall be exactly same as the existing

format.

• In existing 15-min raw text file, frequency is stored in terms of codes from 00 to 99.This

can be addressed in new AMR system by converting frequency to codes at WRLDC

end(CDCS) for compatibility in existing MDP S/W.

• Existing SEMs have 7 character unique serial number where as new IEMs shall have 12

character serial number. This can also be addressed by properly converting 15 character

serial number to 7 character serial number by neglecting first 4 digits in 8 digit serial

number at WRLDC while extracting data from AMR system.

• As the input raw data to new MDP S/W is in 5-min block wise, all computations in new

data processing software shall be done in 5-min only.

• While reports generation, data Processing Software shall have two options to generate

processed data reports in 15/5-min depending upon the user requirement.

• The format of the 15-min processed data reports shall be exactly same as existing 15-min

processed data reports in text files for compatibility at WRPC end.

32. DSM Accounting S/W Module

This module is for computation of deviation of actual injection/drawal against its schedule,

calculation of total deviation charge for all entities in 15-min block wise and reports

generation for all entities. Inputs for DSM calculation are mainly block-wise actual Injection

/ Drawal based on SEM data and corresponding block-wise Final Implemented Schedule

(Injection / Drawal).

32.1 SCOPE

This section provides detailed scope of work included in the bidder’s scope, facilities to be arranged by bidder.

14.3 Bidder’s Scope of Work

• S/W module for DSM Accounting in accordance with existing IEGC & DSM

Regulations and may be modified in future which includes:-

� Calculation of Normal UI charges based on CERC Regulations

� Calculation of Additional UI charges based on CERC Regulations

� Calculation of Capped UI charges based on CERC Regulations

� Preparation of entity wise DSM reports and overall DSM weekly summary report

etc.

� Bidder shall refer relevant CERC DSM regulations for exact computations and

necessary applications to be implemented.

(Relevant CERC Regulations and WRPC weekly DSM summary reports are attached in Annexure-II

for reference)

• Server System at WRPC and WRLDC.

• Archival and retrieval of data through Oracle database at WRPC and WRLDC

• Computations and Applications to be implemented shall be user definable so that any

amendments in DSM computations by competent authority or by RPC forums can be

implemented in the software.

• As on date of delivery, the supplied S/W shall comply with all statutory regulation as

required under CERC/IEGC as applicable and the same should be declared by the

supplier during delivery along with warranty certificate.

• Warranty for 5 years and support and maintenance during 5 years extended period after

expiry of warranty period.

33. SUPPORT AND MAINTENANCE REQUIREMENTS FOR

MDP, EA & DSM ACCOUNTING S/W Supplier should provide onsite as well as remote support in order to keep system operational with system functionalities and performance in accordance with the specifications.

33.1 Scope of AMC During warranty / AMC period, supplier is responsible for repair/ replacement/ modify/ rectify all times i.e. software, hardware either manufactured or bought out, updation of software used in MDP, EA & DSM Accounting S/W without any extra charges to WRLDC/WRPC.

33.2 On-site support and maintenance Supplier should maintain a team of skilled personals having sufficient knowledge of the system

in order to diagnose and set right any problem in in MDP, EA & DSM Accounting S/W system

in minimum time.

Supplier should maintain a help desk operated from 0900 hrs to 1800 hrs on all days except

Sundays and national holidays. Supplier should maintain an online web based help desk system

for logging complaints and checking the resolution status. Help desk should be accessible by

the user through browser via Internet. Any complaint shall remain open until and unless

approved its closure by WRLDC/WRPC. All logs should be suitably time stamped.

Supplier should post two skilled resident engineers to WRLDC/WRPC (One for maintenance

of MDP & EA S/W and other for DSM S/W) throughout the warranty and AMC period in

order to diagnose and set right any problem in MDP, EA & DSM Accounting S/W in minimum

time. Resident engineer shall be provided with mobile phone for communication in odd hours

or for escalation of complaint. Supplier should maintain this Mobile phone live and should

maintain same number throughout the contract period. All expenditure on this phone shall be

borne by the supplier.

33.3 Remote support and maintenance No remote login is permitted.

33.4 Up gradation and patches Supplier should keep updated all supplied software kernel/OS and application software with all latest patch and upgrade. 33.5 Maintenance and support of brought out items Supplier should take back-to-back support from manufactures of brought out items like servers, printers and like items. However, supplier shall be responsible for all coordination work form OEM for all types of support and maintenance.

Annexure-I

I. Station wise bifurcation of SEMs in WR

TS-Transmission Station, GS-Generating Station

S.No GS/ Substation name No. of meters Location type Station owner State

1 Korba 39 GS NTPC Chattisgarh

2 Vindhyachal (NTPC) 70 GS NTPC MP

3 Kawas 24 GS NTPC Gujarat

4 Gandhar 22 GS NTPC Gujarat

5 Sipat 27 GS NTPC Chattisgarh

6 LANCO 10 GS LANCO Chattisgarh


7 Jindal 29 GS JPL Chattisgarh

8 KAPS 16 GS NPCIL Gujarat

9 TAPS 1 &2 20 GS NPCIL Maharashtra

10 TAPS 3 &4 16 GS NPCIL Maharashtra

11 PENCH 8 GS MPGCL MP

12 SSP 15 GS SSP Gujarat

13 Rajgarh 12 TS PGCIL MP

14 Raipur 27 TS PGCIL Chattisgarh

15 Bhatapara 6 TS PGCIL Chattisgarh

16 Raigarh 10 TS PGCIL Chattisgarh

17 Bhilai 17 TS CSPTCL Chattisgarh

18 Korba (W) 2 TS CSPTCL Chattisgarh

19 Korba E 2 TS CSPTCL Chattisgarh

20 Kotmikala 2 TS CSPTCL Chattisgarh

21 Raigarh(CSEB) 1 TS CSPTCL Chattisgarh

22 Dongargarh 1 TS CSPTCL Chattisgarh

23 Vapi 18 TS PGCIL Gujarat

24 Asoj 4 TS GETCO Gujarat

25 GPEC 1 TS GETCO Gujarat

26 Kasor 3 TS GETCO Gujarat

27 Dehgam 8 TS PGCIL Gujarat

28 Haldarwa 6 TS GETCO Gujarat

29 Icchapur 2 TS GETCO Gujarat

30 Navsari (PG) 10 TS PGCIL Gujarat

31 Navsari (Getco) 4 TS GETCO Gujarat

32 Vapi (GETCO) 8 TS GETCO Gujarat

33 Vav 4 TS GETCO Gujarat

34 Bhilad 7 TS GETCO Gujarat

35 Una, Diu 1 TS DD DD

36 Dhokadwa, Diu 1 TS DD DD

37 Zerda 4 TS GETCO Gujarat

38 Magarwada (DD) 2 TS DD DD

39 Dabhel, Daman 2 TS DD DD

40 Dalwada 1 TS DD DD

41 Kharadpada, DNH 4 TS DNH DNH

42 Kharadpada (new), DNH 2 TS DNH DNH

43 Jabalpur 6 TS PGCIL MP

44 Satna 9 TS PGCIL MP

45 Khandwa 14 TS PGCIL MP

46 Itarsi 13 TS PGCIL MP

47 Indore 4 TS MPPTCL MP


48 Bina (MP) 2 TS MPPTCL MP

49 Satpura 3 TS MPPTCL MP

50 Bhopal 4 TS MPPTCL MP

51 Nagda 6 TS MPPTCL MP

52 Bina (PGCIL) 13 TS PGCIL MP

53 Gwalior 18 TS PGCIL MP

54 Seoni 17 TS PGCIL MP

55 Pandurna 1 TS MPPTCL MP

56 Malanpur 1 TS MPPTCL MP

57 Mehgaon 1 TS MPPTCL MP

58 Ujjain 2 TS MPPTCL MP

59 Amarkantak 3 TS MPPTCL MP

60 Balaghat 1 TS MPPTCL MP

61 Damoh 12 TS PGCIL MP

62 Chandrapur 4 TS MSETCL Maharashtra

63 Bhadravathi 6 TS PGCIL Maharashtra

64 Wardha 26 TS PGCIL Maharashtra

65 Akola 4 TS MSETCL Maharashtra

66 Aurangabad (MSEB) 2 TS MSETCL Maharashtra

67 Bhadravathi 15 TS PGCIL Maharashtra

68 Dhule 6 TS MSETCL Maharashtra

69 Koradi 2 TS MSETCL Maharashtra

70 Padghe 4 TS MSETCL Maharashtra

71 Kolhapur (telangada) 2 TS MSETCL Maharashtra

72 Nasik 2 TS MSETCL Maharashtra

73 Kalmeshwar 1 TS MSETCL Maharashtra

74 Boisar 8 TS PGCIL Maharashtra

75 Mapusa, Goa 6 TS PGCIL Goa

76 Amona, Goa 2 TS Goa Goa

77 Sugen 33 TS GETCO Gujarat

78 Rajghat (MP) 1 TS MPPTCL MP

79 Khadoli 3 TS DNH DNH

80 Sayali 2 TS DNH DNH

81 Pirana (PG) 13 TS PGCIL Gujarat

82 NSPCL 20 GS NSPCL Chattisgarh

83 Parli (MSEB) 2 TS MSETCL Maharashtra

84 Shujalpur (PG) 8 TS PGCIL MP

85 RGPPL 19 GS RGPPL Maharashtra

86 Solapur 16 TS PGCIL Maharashtra

87 ACBIL 19 GS ACBIL Chattisgarh

88 Bhachau 12 TS GETCO Gujarat


89 BALCO 11 GS BALCO Chattisgarh

90 CGPL Mundra 17 GS CGPL Gujarat

91 DCPP 4 GS JPL Chattisgarh

92 Tamnar 1 TS PGCIL Chattisgarh

93 Ranchhodpura 6 TS GETCO Gujarat

94 Limbdi 5 TS GETCO Gujarat

95 Mahan (ESSAR) 6 GS ESSAR MP

96 Bina (PG) 9 TS PGCIL MP

97 Birsingpur 4 TS MPPTCL MP

98 Mouda (NTPC) 18 GS NTPC Maharashtra

99 KSK Mahanadi 9 GS KSK Chattisgarh

100 Jetpur 2 TS GETCO Gujarat

101 Sasan 25 GS SASAN MP

102 Vindhyachal (PS) 9 TS PGCIL MP

103 Bilaspur 12 TS PGCIL Chattisgarh

104 Vandana 7 GS VANDANA Chattisgarh

105 GMR EMCO 6 GS GMR EMCO Maharashtra

106 KWPCL 6 GS KWPCL Chattisgarh

107 Jaypee nigri 8 GS JAYPEE NIGRI MP

108 DB Power 8 GS DB POWER Chattisgarh

109 RAIGARH(KOTRA) 2 TS PGCIL Chattisgarh

110 ESSAR HAZIRA 6 TS ESSAR HAZIRA Gujarat

111 Indore (PG) 5 TS PGCIL MP

112 Pune (PG) 28 TS PGCIL Maharashtra

113 Solapur 12 TS PGCIL Maharashtra

114 Aurangabad (PG) 15 TS PGCIL Maharashtra

115 APL Mundra 27 GS APL Gujarat

116 Raipur (PS) 8 TS PGCIL Chattisgarh

117 Tamnar (PS) 14 TS PGCIL Chattisgarh

118 Dharamjaygarh 12 TS PGCIL Chattisgarh

119 Dhariwal 6 GS DIL Maharashtra

120 GMR Chattisgarh 8 GS GMR CHATTISGARH Chattisgarh

121 BDTCL Bhopal 10 TS BDTCL MP

122 Jabalpur (PS) 2 TS PGCIL MP

123 Bhopal (MP) 2 TS MPPTCL MP

124 DGEN 13 GS DGEN Gujarat

125 Diu 2 TS DD DD

126 Dadra 2 TS DNH DD

127 Silvassa 2 TS DNH DNH

128 Pithampura 3 TS MPPTCL MP

129 Mushtungi 2 TS GOA GOA


130 Tillari 1 TS GOA GOA

131 Pirana (TPL) 2 TS GETCO Gujarat

132 RKM Power 7 GS RKM Chattisgarh

133 Kotra 2 TS PGCIL Chattisgarh

134 Satna (PG) 15 TS PGCIL MP

135 Parli (PG) 10 TS PGCIL Maharashtra

136 Kala (PG) 12 TS PGCIL DNH

137 Jabalpur (PS) 14 TS PGCIL MP

138 Kotra (PS) 19 TS PGCIL Chattisgarh

139 Jaypee bina TPP 6 GS MPPTCL MP

140 Mundra 16 GS CGPL Gujarat

141 Indore (PG) 8 TS PGCIL MP

142 Magarwada (PG) 8 TS PGCIL DD

143 Varsana (GETCO) 2 TS GETCO Gujarat

144 DHULE (BDTCL) 8 TS BDTCL Maharashtra

145 Mansar (GETCO) 2 TS GETCO Gujarat

146 MB Power 7 GS MB POWER MP

147 MCCPL 6 GS ACBIL Chattisgarh

148 Jhabua Power 6 GS JHABUA POWER MP

149 SKS Power 6 GS SKS Chattisgarh

150 Kotra PG 2 TS PGCIL Chattisgarh

151 Vadodara (PG) 12 TS PGCIL Gujarat

152 TRN Energy 7 GS TRN Chattisgarh

153 Kolhapur (PG) 10 TS PGCIL Maharashtra

154 Bhanpura 1 TS MPPTCL MP

155 Kosamba 1 TS GETCO Gujarat

156 Ukai 1 TS GETCO Gujarat

157 Champa (PG) 17 TS PGCIL Chattisgarh

158 Lara 5 GS NTPC Chattisgarh

159 Betul GIS 6 TS PGCIL MP

Total 1409

Station type No. of meters

Transmission Station 810

Generating Station 599

TOTAL 1409

II. Station owner wise bifurcation of SEMs in WR

S.No Station owner No. of meters S.No Station owner No. of meters

1 PGCIL 555 20 LANCO 10

2 NTPC 205 21 DD 9

3 GETCO 109 22 KSK 9

4 MPPTCL 53 23 DB POWER 8

5 NPCIL 52 24 GMR CHHATTISGARH 8

6 CGPL 33 25 JAYPEE NIGRIE 8

7 JPL 33 26 MB POWER 7

8 MSETCL 29 27 RKM POWER 7

9 APL 27 28 TRN ENERGY 7

10 ACBIL 25 29 VANDANA 7

11 CSPTCL 25 30 DIL 6

12 SASAN 25 31 ESSAR MAHAN 6

13 NSPCL 20 32 ESSAR HAZIRA 6

14 RGPPL 19 33 GMR EMCO 6

15 BDTCL 18 34 JHABUA 6

16 DNH 15 35 KWPCL 6

17 SSP 15 36 SKS 6

18 DGEN 13 37 GOA 5

19 BALCO 11 TOTAL 1409

III. Make wise bifurcation of SEMs in WR

S.No SEM Make No. of meters

1 SML 642

2 L&T 577

3 ELSTER 190

TOTAL 1409

Annexure-II

DSM Regulations and sample WRLC DSM Account to be included after

conversion to PDF.

Technical Specification for Interface Energy Meters ...wrpc.nic.in/ccm/DRAFT_AMR_SPEC_2017.pdf ·...

Documents

Transcript of Technical Specification for Interface Energy Meters ...wrpc.nic.in/ccm/DRAFT_AMR_SPEC_2017.pdf ·...