Tel.

- 26967840,42,45,26967900,26868681
OE Fax - 26865206, 26567341
E-Mail : nrebops@yahoo.com

Northern Regional Power Committee

18-A, Shaheed Jeet Singh Marg,
Katwaria Sarai, New Delhi-110016.
No. NRPC/ SE(O)/USMG/24//2009

Dated 17.08.09

Subject: 24th Meeting of ULDC Scheme Monitoring Group (USMG).

The Agenda for the 24th meeting of USMG is enclosed herewith. The Agenda is also
available on NRPCs Website at http://nrpc.gov.in. The meeting shall be held at New
Delhi at 11:00 hrs on 24.08.09 at NRPC.
Kindly make it convenient to attend the meeting.

- sd(A K Rajput)
S.E. (Operations) & Member Convener USMG
Sr.
No.

All members of USMG

Organization
Names of Officers & Designation
S/Shri

1.

BBMB

Director (PR)

2.

DTL

GM (SLDC); DGM;

3.

HVPNL

SE/PPM, HPGCL, Panchkula, / SE (SLDC) Panipat; EE, Panipat

4.

HPSEB

SE(SLDC)

5.

J&K

CE (C&S), Jammu;

6.

PSEB

CE (SLDC); DD (SLDC)

7.

RVPN

CE (C&LD); EE (SLDC)

8.

UPPCL

GM(US);Fax:0522-2287880 , DGM, 220kV Agra, Fax 0562 2605465

9.

PTCUL

DGM (LD), EE (T&C), Roorkee-Fax No. 01332-265767

10.

UJVNL

General Manager-GV

11.

PowerGrid, NR-I

GM (O&M); Ch Manager

12.

THDC

AGM, (Electrical design), Pragatipuram, Rishikesh.

13.

PowerGrid, NR-II

DGM

14.

CEA

Dir (LD&T)

15

NRLDC

CM (CS); CM (TS)

16

NRPC

SE (Operations); EE (O-I)

NORTHERN REGIONAL POWER COMMITTEE

Agenda for 24th Meeting of
ULDC Scheme Monitoring Group (USMG) of Northern Region
Date: 24.08.2009
Time: 11:00 Hrs
Venue: NRPC, New Delhi
1.0 Confirmation of Minutes of 23rd USMG meeting
Summary Record of the 23rd meeting of the USMG held on 27.04.2009 was circulated
vide NRPC/SE (O)/USMG/23/2009Dated 11.04.2009. (USMG Agenda and minutes are
now also available on NRPC website at http://nrpc.gov.in).
HPSEB has requested that the following point should to be added at the end of para 6.0
( Commissioning of Telemetry System Between Baspa HEP and HPSEB by M/S

PGCIL) :
It was also deliberated and decided that till such time the above link is commissioned,
the temporary link provided during 11/2008 for HPSEB between Baspa-II and SLDC
Shimla is to be made functional by POWERGRID. This temporary link is non functional
since Jan. 2009.
USMG may like to confirm the minutes.
2.0 NMS of Digital Microwave System:

In the last meeting POWERGRID had stated that for the monitoring of communication
equipment installed under ULDC scheme, Network Monitoring System (NMS) has been
installed at Regional System Control and Coordination (RSCC) Center. With the help of
NMS, healthiness of communication equipment (Card level) and healthiness of DC/AC
power supply etc are monitored on 24x7 basis. NMS is vital part of communication
network and in absence of NMS it would be very difficult to maintain the system as
maintenance engineer would be running in blind alley. Matter was taken up with NOKIA
and they had informed that their present NOKIA NMS software can not run on any other
OS, however they have developed new software NETVIEWER which operates on
windows based system. They have indicated that total financial implication for changing
2

present NMS system with new one would be approx. Rs 1.3 Crores. Formal offer shall be
submitted by NOKIA or their authorized representative after survey at all SLDC/RSCC.
However, AMC contractor of wideband had proposed that they would replace the NMS
at RSCC only, without any cost implication to POWERGRID. If NMS is to be replaced
at all SLDCs charges shall be as per NOKIAs offer.
POWERGRID in the last meeting had indicated that there are two parts of NMS viz. (i)
NMS for Fibre Optic; and (ii) NMS for Microwave system. For the above mentioned
microwave system, cost wise Radio Communication System constitutes about 20% and
remaining 80% cost component is that of Multiplexers (Muxs). The Radio portion is
being phased out gradually and Optical Fibre Cable (OPFC) is being installed in its
place. Multiplexers will still remain in the system.

Constituents and MS , NRPC suggested that possibility of buy back of the released
obsolete equipment from existing system should be explored. POWERGRID stated
that this could form part of the negotiations for awarding AMC.
USMG also decided that POWERGRID would send proposal to each constituent
indicating total cost implications of the scheme, as well as the cost to be borne by each
constituent, in turn the constituents would take up the matter with their management and
would revert back in the matter, before the next meeting.

PSEB has given consents to the proposal of PGCIL for replacement of NMS system
at PSEB SLDC & the charges, Rs.15.47 Lac( including BBMB share) as worked out
by PGCIL. as per CERC orders, shall be paid by them.
HPSEB has intimated that necessary approval for replacement of existing Microwave
NMS with new NMS has been conveyed to POWERGRID.
Other constituents may like to update.
Members may like to deliberate.

3.0 Updating and replacement of obsolete systems and RTUs:

In order to identify the updating requirement, its necessary to know the capacity and
expandability of the system and with present capacity of ULDC scheme, NRLDC can

add up to 120 additional RTUs/substations, provided there were no constraints on the

application related parameters. However, RTUs to be implemented would be prioritized
after discussions with the constituents. Also in order to standardize RTU specifications,
facilitate procurement and mitigate integration issues, it was decided to constitute a sub
committee comprising of members from HPSEB, PSEB, and POWERGRID & NRLDC.
This committee would submit its report within two months.
The following will be the members of the sub committee:
i. Superintending Engineer (O), NRPC;
ii. Sh Y. K. Dixit, Chief Manager, PowerGrid iii. Sh. S. P. Singh, EE, PSEB;
iv. Sh. N. P. Gupta, Sr EE, HPSEB;
v. Sh. R. K. Kaushik, EE, HVPNL;
vi. Sh. Naveen Gupta, DD, BBMB; and

vii.Smt.Vineeta Aggarwal, Chief Manager, NRLDC -Member Convener;

The sub group has submitted its draft report, given at annexure
Constituents may like to deliberate on the issue.

4.0 Procurement of spare RTUs and AMC of RTU s

Constituents had informed that their existing spares are nearing exhaustion. In view of
above modality to maintain RTUs by cannibalizing from existing RTUs after replacing
some RTUs with a new make/model may be deliberated for smooth running of system.

In the last meeting POWERGRID had intimated that M/S AREVA had phased out S900 RTUs and the cost of spare cards of these RTUs as per rates quoted by M/S
AREVA were on higher side. Constituents had discussed the issue and decided that
as discussed in the 8th NRPC meeting, constituents might go ahead and procure the
RTUs themselves. The AMC contract would be negotiated in October, 2009 and
AMC related issues would be discussed in the next USMG meeting.
Members may like to deliberate

5.0 Replacement of SCADA/EMS vis--vis cost comparison with

reference to Present AMC cost and new SCADA system excluding EMS
(Agenda by HPSEB).
4

HPSEB is presently paying approximately Rs. 100 lac (approximately) towards AMC
of SCADA/EMS system installed at SLDC Shimla and-LDCs at Kunihar and
Hamirpur including service charges & overhead charges etc. The total cost of the
installed system (H/W & S/W) for which AMC has been awarded is around Rs. 5.6
crore. Presently, EMS packages such as Load Forecasting (Forecasting available on
1 hour basis against requirement of 15 minutes basis), Operation Scheduling are not
being used in the entire NR Control Centres for one reason of the other. Also, State
Estimator, Contingency Analysis, Security Enhancement and Load Flow Analysis
packages are being used only to some extent owing to common NR model and older
version packages. Only SCADA data, HDR data and to some extent HIM data is
being utilized for monitoring and report generation. HPSEB has proposed that
whenever the present system is upgraded, SCADA portion (HW / S/W) of the
system including OAG (Open Access Gateway) should be installed by the central
agency i.e PGCIL, for all the constituents having provision for the integration of
EMS packages for uniformity.

Also for EMS packages, guidelines may be

finalized. It is apprehended that the new system cost may not be commensurate
with AMC cost owing to the warranty to be given by the vendor for the new system .
Members may like to deliberate
6.0 Changing the Isolator and Breaker Numbers in ULDC SCADA System as per
field conventions:
BBMB had earlier stated that the Isolator and Breaker numbers defined in the ULDC
SCADA System are different from the actual numbers given to these devices in the field.
This necessitates frequent references to physical drawings as the device numbers
indicated on SCADA Displays and Logs do not match with the field drawings and
reports. This makes the operations and reporting in control centre difficult and prone to
errors. Efforts have been made by BBMB to implement the naming conventions of
ULDC SCADA System in the field but the same has been viewed with apprehension by
our field organizations. This is due to the fact that the existing numbering scheme is
being used for a long time and departure from the same may lead to confusion. Hence in

order to bring in much needed consistency in the numbering, BBMB proposed

to

implement field numbering scheme in the SCADA System. BBMB opined that the

changes outside of BBMB System would be minimal but the exercise would be quite
fruitful in the long run.
USMG had opined that it might be done on one or two stations on sample basis for
the time being and share the experience with others. BBMB may like to update on
the issue.
Members may like to deliberate.
7.0 EXPANSION OF NR UNIFIED LOAD DESPATCH AND COMMUNICATION SCHEME of
NR (PHASE-II)

During the 8th NRPC meeting, held at Udaipur on 25th April 2008, it was decided that
constituents may go ahead independently for the expansion of their respective parts of the
ULDC scheme (Phase-II). The USMG would decide a minimum standard requirement
indicating which data should flow to RLDC and SLDC so as to ensure the proper
integration of ULDC expansion in the northern region.
The matter was discussed in detail during the last USMG meeting. During discussion,

constituents expressed their concern about the requirement of common philosophy

and approach for expansion/replacement of the present SCADA/EMS systems.
USMG decided that a High Level Sub-Committee might be constituted to form the
specifications/philosophy after identifying the requirement of expansion of the system
for next 7-10 years. After deliberations, USMG decided to constitute a SubCommittee comprising the following members :
1. Sh. Niraj Gulati, Chief Engineer (SO), HVPNL;
2. Sh.V. K.Agrawal, GM, NRLDC;
3. Sh. D. K. Jain, Director, LD&T, CEA;
4. Sh Suneel Grover, Director, (PR), HPSEB;
5. Sh.A. S. Kushwaha, AGM (LD&C), POWERGRID; and
6. Superintending Engineer (Operations) NRPC-Member Convener
POWERGRID and all other constituents were requested to submit the base paper

for consideration of the committee. The proposed committee would come out with a
common approach paper and recommendations for implementation of ULDC-phase II
scheme The Committee would submit its report within two months time.
The report of the sub committee is under deliberation among the members of the sub
group. The draft report is enclosed at annexure.

Meanwhile PSEB has stated that since all the states would have to arrange funds /
consultants/ global tendering individually and the constituents shall have to pay for
PGCIL/ BBMB share also , these duplication of work may prove costly for the
constituents. Moreover at least

region wise uniformity may be maintained to

decrease inventory of spares/ cost of AMCs. PSEB is considering to re- open the
decision taken during 8th NRPC meeting. PSEB has requested that members may
deliberate accordingly , so that the SLDCs may be upgraded in a cost effective
manner , under unified approach.
Members may like to deliberate.
8.0 Commissioning of telemetry system between Baspa HEP and HPSEB by
M/S PGCIL
It was decided that POWERGRID would install PLCC Link from Nathpa JhakriAbdullapur-Bawana Line for providing reliable telemetry of Baspa HEP at the expense of
HPSEB and HPSEB would take care of its maintenance aspects. It was also agreed that
till the permanent link was established, the temporary link provided by POWERGRID
would be made available.
HPSEB has stated that POWERGRID has not taken any action for restoration of
temporary link which is down since Jan. 2009. This link need to be restored immediately
without any further delay as already three months have elapsed ever since POWERGRID
agreed to do the same during 23rd USMG meeting. Further, action taken for installation
of new PLCC link from Jhakri-Abdullapur-Bawana line for providing reliable telemetry
of

Baspa HEP with SLDC Control Centres of

HPSEB, may be indicated by

POWERGRID.
HPSEB has requested that necessary directions in this regard are required to be issued to
POWERGRID to take immediate action.
POWERGRID/HPSEB may like to update.
7

9.0 Non reporting of data by RTUs

NRLDC in its presentation in 41st OCC meetings on 07.08.09 has stated that about 25
RTUS are not reporting and about 34 sub stations are without RTUSs. (status as on 11-809 is enclosed at Annexure )
Constituents may update.
10.0 Formation of core group for SCADA/EMS applications (Agenda by PSEB)

PSEB has requested that a core group considering one member from each
constituent and one member from NRLDC/ PGCIL may be formed for making all
the EMS applications functional.
Members may like to deliberate.
110

Non availability of Real time data at NRLDC/PGCIL Websites

PSEB has stated that NRLDC has withdrawn real time data of few important system
parameters from the website. These real time values/status of various RTUs was quite
useful for system operation/monitoring. PGCIL/ NRLDC may issue some password to
constituents to access this real time data on internet, if the same has been withdrawn due
to some security constraints. The original feature of web sites may please be re-stored.
Member may like to deliberate.

12.0 Maintenance Related Agenda of the Constituents

12.1 Poor performance of AMC vendor for Power supplies (Agenda by
PSEB)
PSEB has stated that the AMC vender for UPS/ DC Power Supplies selected by PGCIL
is not responding to PGCIL/Constituents and is not adhering to commitments made
during various MR&M meetings. The 48V DC power supply Banks at ALDC Jamsher,
and few cells at ALDC Lalton are faulty since 7/3/2009. Such a vital equipment should
have been attended by the firm on priority & as per response timings of the contract .
PGCIL may be asked to get the cells replaced at the earliest.

Members may like to deliberate.

12.2
Replacement of defective battery cells of UPS installed under ULDC
Scheme ( Agenda by BBMB)
Various cells of the battery banks of UPS System installed under ULDC Scheme at
various Sub-LDCs and SLDCs are lying defective since last many months. The matter
has been discussed at various Monthly Review Meetings and the AMC vendor of UPS,
M/s Emerson, has given various deadlines since last many months, but the firm is just
using dilatory approach and have not replaced the cells till date. The details of cells lying
defective at BBMB Sub-LDCs is as under:
Station

Cell Nos

Defective Since

Charkhi Dadri

Cell No 72

13.03.2008

Cell nos. 7, 66, 94, 148, 183

15.04.2009

Cell Nos 185, 186, 106

28.07.2009

Jamalpur

Besides this, many battery cells at BBMB Sub-LDCs and SLDC Chandigarh have been
found to be weak. POWERGRID may be requested to take immediate necessary steps to
get the cells replaced.
POWERGRID/ BBMB may like to update.
13.0 ANY ADDITIONAL AGENDA POINT
14.0 DATE, TIME AND PLACE OF NEXT MEETING
The Group may decide the date and venue of the next meeting.

List of Substations Without RT Us

Sl No.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21

Utility
DTL
HPSEB
HVPNL
HVPNL
HVPNL
HVPNL
HVPNL
HVPNL
HVPNL
PDD , J & K
PSEB
PSEB
PSEB
PSEB
PSEB
PSEB
PSEB
PSEB
PSEB
PTCUL
PTCUL

kV Level
220
220
220
220
220
220
220
220
220
400
220
220
220
220
220
220
220
220
220
400
220

Station
DSIDC
Larji
Cheeka
Daulatabad
IMT Manesar
Jorian
Nilokheri
Palli
Tepla
Baglihar
Bajakhana
Botiawala
Derabassi
Dhuri
Hambran
Khasa
Kotli Suratmali
Patran
Rajla
Kashipur
Haldwani

22
23
24
25
26
27
28
29
30
31
32
33
34
35

PTCUL
PTCUL
RRVPNL
RRVPNL
RRVPNL
UPPCL
UPPCL
UPPCL
UPPCL
UPPCL
UPPCL
UPPCL
PGCIL
PGCIL

220
220
220
220
220
400
221
220
220
220
220
220
400
220

Pantnagar
Roorkee
Barsingsar
Dholpur
Jallore
Greater Noida
Orai
Almoh
Attrauli
Chibra Mau
Dohna
RPH
Roorkee
Sitarganj

Sl No.

Utility

kV Level

Remarks
RTU was to be installed.Not integrated yet.

RTU Shifted from Haldwani .Not yet

integrated.

RTU installed. Not Integrated

RTU installed. Not integrated

RTU installed. Not Integrated
RTU installed. Not Integrated
SAS of ABB installed but not integrated.
Integrated

RT Us with T elemetry Problem

1
2
3
4
5
6
7
8
9

HPSEB
HPSEB
HVPNL
PDD , J &
PDD , J &
PDD , J &
PDD , J &
PDD , J &
PDD , J &

K
K
K
K
K
K

Station

400
132
220
220
220
220
132
132
132

Baspa
Andhra
Fatehabad
Chenani
Hiranagar
Pampore
Lower Jhelum
MiranSahib
Upper Sindh

Remarks
RTU Integrated but some configuration
problem.Data not available at NRLDC
PLCC problem

10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27

POWERGRID
PTCUL
RRVPNL
RRVPNL
RRVPNL
UJVNL
UJVNL
UPPCL
UPPCL
UPPCL
UPPCL
UPPCL
UPPCL
UPPCL
PGCIL
PGCIL
PGCIL
PGCIL

400
220
400
220
220
220
220
220
220
220
220
220
220
220
400
400
400
400

Kankrauli
Maneribhali
Jodhpur
Flodi
Bhilwara
Chibro
Ramganga(H)
Agra-II
Allahabad Cant
Badaun
Basti
Noida
Saharanpur
Sahibabad
Patiala
Dulhasti
Bareily
Uri

28
29
30
31

PGCIL
PGCIL
PGCIL
DTL

400
220
400
220

Balia
Raibareily
Gorakhpur
Kashmeri Gate

PLCC Link problem.

PLCC Link problem.
PLCC Link problem.
PLCC Link problem.
PLCC Link problem.
PLCC Link problem.
Siemens SAS , integrated on 29/05.Link
intermittent. Some elements still not
w ired.
ABB RTUS at Site Not integrated yet.
ABB RTUS at Site Not integrated yet.
CPU card problem.
PLCC Link problem.
Restored
Restored

Data intermittent
Data intermittent
Data intermittent
Not available since 23.07.09
Data highly intermittent
Data incorrect-ABB SAS problem
Not available since 11.07.09
Not available since 18-01-09-ABB SAS
problrm.
Data not available since 30.07.09
Data intermittent
Restored

REMOTE TERMINAL UNIT

(RTU)
SPECIFICATION

1GENERAL
This document describes the specifications for the Remote Terminal Unit (RTU). The
Contractor shall supply RTU, associated equipment and required number of panels for
housing of all the hardware envisaged for the RTU and system interface cubicle (SIC).
The contractor shall be responsible for supplying all the hardware, software, and
installation, cabling and field implementation for RTU as defined in this Specification. The
contractor shall also provide complete documentation, training and testing to fully support
the hardware and software provided. The RTU shall be used for real-time supervision
and control of substation/ power plant through a SCADA system at Remote Control
Centre (RCC). The RCC is also referred to as Master station or SCADA system. Strict
compliance to standards, scalability, modular and open architecture.
The owner may not initially use all capabilities of the RTU specified in this document.
However, regardless of the RTU configuration purchased, the RTU shall be capable of all
functions specified herein. The optional functions, if any specified in the specifications,
may be implemented with the addition of necessary hardware and software modules in
the field as and when required by the owner without any additional financial implications
except for |hardware cost if any.
(Commercial)
It is Owner's intent that the Contractor uses as much standard hardware and software as
possible; however, all of the functional requirements of this Specification must be
satisfied. The use of the Contractor's standard hardware and software may cause the
Contractor to conclude that there is a need for additional items not specifically mentioned
in this Specification. The Contractor shall supply all such items and provide a complete
RTU design that meets all of the Owner's functional requirements defined in this
Specification.
(Commercial):

1.1 REMOTE TERMINAL UNIT REQUIREMENTS

The RTU shall have all functional capabilities described herein even if a function is not
initially implemented.
i.
ii.
iii.
iv.

v.
vi.
vii.
viii.
ix.

Collecting, processing and transmitting status changes, accumulated values and analog
values.
Receiving and processing digital commands from the master station(s).
Accepting polling messages from at least two master station(s) simultaneously using
partitioned databases for each master station.
At least six serial communication ports (4 x RS232 + 2 x RS485) with the provision of
adding at least additional 4 serial communication ports by way of addition of required
hardware. The RS 232 ports shall be configurable for data transmission rates from 200 to
19200 bits per second. The RS232 (Unbalanced) communication ports shall use CCITT
V.24 and V.28 signal specifications and RS485 (Balanced) communication ports shall
use V.11 or V.35 signal specifications to interface with other equipment.
Support multiple concurrent protocols in each CPU including the following :
Local/Remote Host Communication Protocols
IEC 60870-5-101
IEC 60870-5-104
DNP 3.0 (Serial & TCP/IP)

x. Communication with slave RTUs/SAS while acting as Data Concentrator

xi. IEC 60870-5-101
xii. IEC 60870-5-104
xiii.
xiv. Local IEDs/Multifunction Meters Communication Protocols
xv. IEC 60870-5-103
xvi. MODBUS
xvii. DNP 3.0 (Serial & TCPIP)
xviii.
xix. At least one Ethernet port supporting IEC 60870-5-104 & DNP 3.0 (IP) protocol in each
CPU.
xx. Accepting RTU database (configuration settings) downloads from the Master station
(RCC) at remote location.
xxi. Redundant Central Processing unit and Power supply unit.
xxii. RTU should be capable of being configured into point to point, party-line and as a data
concentrator

1.1.1 Redundancy in CPU and Power supply for communication with RCC.
The RTU shall be provided with redundant CPUs and Power supply unit so that the RTU
can communicate with the Remote Control Centre even when one of the redundant units
fails. A failover process shall cause the assignment of all the functions of the failed unit to
the healthy unit. The failover between the two redundant units shall be transparent and
shall not require any manual intervention.
The failover process of the power supply units shall not cause any interruption in the
functioning of the RTU.
The failover of process of the CPU shall be completed within 30 seconds of the failure of
the primary CPU. All the functions in the RTU shall be operational within 30 seconds of
the failover operation i.e. one minute from the time of failure.

1.1.2 Communication Interface

The RTU shall provide appropriate communication ports/interfaces to provide following
functionality:
a)

Simultaneous connectivity to two master stations or one master station in dual

redundant mode.

b)

Dual Connectivity to existing RTU while acting as a Data Concentrator (required

only if existing RTU is being provided by the Employer).
(a)
Connectivity to future SCADA system for Local Data Acquisition
and Monitoring.
(b)
At least two serial communication ports for communicating with
IEDs or Multifunction Meters using MODBUS, IEC 60870-5-103 or DNP 3.0
(Serial) protocols.
(c)
Connectivity for RTU configuration and maintenance tools
without interrupting the flow of real time data.

NOTE: 1) TWO MODEMS IN THE RTU AND TWO STANDALONE MODEMS FOR REMOTE END SHALL BE
SUPPLIED.

1.1.3 Master Station Communication Interface

The communication medium used between the RTU and the SCADA system at RCC is
defined separately; however, use of dedicated and/or party-lined communication
channels shall be supported by the RTU.
The communication interface to the master station(s) shall allow scanning and control of
defined points within the RTU independently for each master station using a separate
logical database in the RTU. It shall be possible to pick points from the RTU database
randomly and assign it for reporting to a Master station.
Further, the RTU shall support the use of a different communication data exchange rate
(bits per second), scanning cycle, and/or communication protocol to each master station.

1.1.4 Modems (for PLCC)

If identified in the BOQ, the Contractor shall supply modems at RTU locations suitable for
interface with PLCC communication equipments for communicating with the master
station. The modems at RCC shall also be supplied by the contractor as specified in the
BOQ. The modems at RCC shall be stand alone type which include power supply module
for modem and mounting rack as required.
The modems shall meet the following requirements:
(a)Use CCITT Standards including V.24, V.28.
(b)Use frequency shift keying (FSK) modulation.
(c)Communicate at data rates of 200, 300, 600 and 1200bps.
(d)Use CCITT R.38a and R.38b standard tones for the selected RTU data rate.
(e)Use both 2-wire and 4-wire communication lines.
(f) Receive level adjustable from 0 to - 40 dBm @ 600 ohms.
(g)Transmit level adjustable from 0 to - 24 dBm @ 600 ohms.
(h)PLCC modem shall use bandwidth up to 4 kHz and shall accommodate multiple data
channels over and above voice channels. It shall conform to CCITT-38 standards.
Modem Power supply shall be suitable for 48V DC (nominal)

1.1.5 Modems (Others)

If identified in the BOQ, the Contractor shall supply modems suitable for cable as
communication medium between RTU & SCADA master station. Modems are to be
supplied for the RTU end as well as the SCADA Master station as specified in the BOQ.
The modems shall support the following technical features:
1.
2.
3.
4.

Supporting speed upto 33.6kbps

Protocol support: ITU-T V.34, ITU-T V.32, ITU-T V.32bis
Error control: ITU-T V.42, MNP 2-4
Data compression: ITU-TV.42bis, MNP5

5.
6.
7.
8.
9.

Hardware interface support: V.24/V.28, RJ11

Mode: Asynchronous
Power supply Input voltage: 48 V DC (Nominal)
Supporting Dial-Up and 2 & 4 wire leased line
Provided with suitable arrangement for mounting inside RTU panel and near SCADA
system / at intermediate wideband location
Note:Modems for other medium(VSAT,GPRS/GSM/CDMA etc) shall be suitably
supplied by the Vendor

1.1.6 Master Station Communication Protocol

The Contractor shall provide a communication protocol for communicating with SCADA
master stations using the IEC 60870-5-101 and IEC 60870-5-104 communication
protocol standard. The communication protocol shall support all the requirements of this
standard. The communication protocol shall be non-proprietary and the Contractor shall
provide complete description and documentation of the protocol to Owner.
The RTU shall perform as a slave to SCADA system when using the IEC 60870-5-101
protocol. All communication shall be initiated by the SCADA system master stations. RTU
must notify the master stations of unusual conditions at the RTU (such as a power
fail/restoration or RTU malfunction), the transfer of changed data etc. All the notifications
shall be accomplished within the framework of the periodic data acquisition exchanges.
The RTU shall process the various messages/commands for communication to the
Master station using the following priority.
a) Control command
b) Status data by exception
c) Analog data by exception
d) Analog data periodic
e) Status data integrity scans

1.1.6.1 Exception Reporting

The RTU communication protocol shall report status changes by exception. The
communication protocol shall also support an integrity scan of all status data by master
stations regardless of the lack of any change data. The integrity scan will report the
status of all RTU data assigned to the scan group.
The Analog data shall normally be scanned periodically from the master station.
However, analog data reporting by exception on change of value by more than 20%
(configurable from 1% to 20% in the RTU) than its previous scanned value shall also be
implemented to update the analog values quickly in the RCC.
1.1.6.2 Scan Groups
Analog and digital input points (including points reported by exception) shall be
assignable to scan groups. A scan group shall be a specified set of data points within the
RTU's central database which will be communicated to a master station when requested
by a specific (addressed) scan request. A scan group size shall only be limited by the
communication protocol message length. Any RTU input point shall be assignable to any
scan group. The RTU shall support one scan group for all Analog value, one for all status
values and at least four additional scan groups. The Contractor shall provide a
convenient and flexible scheme for assigning points in the RTU to scan groups.

1.1.6.3 Control Security

Normally RTU shall operate in remote control mode i.e. Supervisory Control shall be
exercised through SCADA master station. However when RTU is configured in local
control mode the control can be exercised through local control panel. The operation of
control outputs shall use a true select-check-before-execute command sequence
between the RTU and the SCADA system master station.
The RTU shall reset its control logic upon any error in the sequence or if the execute
message is not received within a set time (user adjustable from 2 - 30 seconds) after the
command message is received at the RTU.
1.1.7 Data Concentrator Communication Protocol
The RTU shall act as an IEC 60870-5-101 and IEC 60870-5-104 protocol master and
collect data and also perform supervisory control from/on the existing RTUs (if provided
by the Employer) and communicate it to the SCADA system at RCC.
The Master protocol implementation shall be such that the data polling requirements
mentioned in Interoperability document(Annexure-) is at least accomplished.
The Contractor is responsible for making any necessary modification in his
implementation of the communication protocol, if required, for the successful integration
of the existing RTU. The detail of the protocol implementation of the existing RTU is
provided in Interoperability document.

1.2 Analog Inputs

The RTU shall accommodate analog current inputs which are isolated, unipolar or
bipolar, 2-wire ungrounded differential signals with full resolution as follows:
(a) +4 to +20 mA
(b) 0 to +10 mA
(c) -10 to +10 mA.
The analog input accuracy shall be 99.8% or better at 25 deg C ambient temperature.
Mean accuracy shall drift no more than 0.002% per deg C within the temperature range
of -5 to +50 deg. C. Determination of accuracy shall be made while the analog
multiplexer is operating at rated speed. The analog-to-digital converter shall have a
minimum resolution of 2048 counts (sign plus 11 data bits).
Each input shall have surge protection and filtering to provide protection against voltage
spikes and residual current at 50 Hz, 0.1 mA (peak-to-peak). Overload of up to 50% of
the input shall not sustain any failures to the input.
The RTU shall make all appropriate signal level conversion and conditioning to allow full
utilization of analog inputs and meaningful reasonability checking. Including signal
conditioning components, the input impedance shall not be greater than 250 (for 4-20
mA current range).
1.3 Digital Status Inputs
The digital status input interface shall be capable of accepting isolated wet or dry contact
status inputs. The Contractor shall supply necessary sensing voltage, current limiting,
optical isolation, and de-bounce filtering independently for each digital status input. The

sensing voltage shall not exceed 48 Vdc. The sensing voltage source shall be isolated
from that of the RTU logic power such that any noise or a short circuit across the sensing
supply's output terminals would not disrupt the RTU operation other than the shorted
digital status input.
The RTU shall store all status changes detected for retrieval by the master stations. For
communication delays or short-term failure of communications with a master station, the
RTU shall store a minimum of 300 status change events. The RTU shall report any
overflow of this status change buffer to the master stations.
1.3.1 Two-State Devices
All switching devices (breakers, isolators etc) shall be supported by a dual-contact status
indication. Breakers with re-closing capability shall also be supported with momentary
change detection (MCD). All other status indications shall be two-state single-contact
status inputs without MCD.
Single-contact two-state status point inputs will be from a single normally-open (NO) or
normally-closed (NC) contact. Dual-contact two state status point inputs will be from two
complementary contacts (one NO and one NC). A switching device status is valid only
when one contact is closed and the other contact is open. Invalid states shall be reported
when both contacts are open or both contacts are closed. The state definition shall be set
by Owner for each contact position.
The RTU shall be set to capture contact operations of 20 ms or more duration.
Operations of less than 20 ms duration shall be considered no change (contact bounce).
The duration used to determine change versus bounce shall be adjustable from 4 to 25
ms.

1.3.2 Momentary Change Detection

Two-state status input points with momentary change detection shall be used by Owner
for points where multiple operations (changes of state) can occur between RTU scans
(e.g., breakers with re-closing devices that operate faster than the scan rate). The RTU
shall capture and maintain all of the momentary changes, up to 4 per MCD digital status
point. The MCD status input points shall be set to capture operations of greater than 20
ms duration. Operation of less than 20 ms shall be considered no change (contact
bounce). The capture duration shall be adjustable between 4 and 25 ms. alternatively,
the RTU can store and report the multiple state changes of a digital input as discrete
events. It shall be ensured that all the changes are reported to the Master station in the
sequence in which they occur in the RTU.
1.3.3 Pulse Accumulators
The RTU shall be capable of counting and storing the number of contact closures
generated by a metering device external to the RTU. The device will supply either an
isolated Form A normally open or Form C contact. The accumulator shall be incremented
one count for each cycle of the input (operation of the normally open and normally closed
contact of the Form C contact). Each accumulator shall have a 24-bit counter for counting
input operations before rolling over. The accumulator shall be capable of accepting
counts at a rate of ten counts per second. The count shall be "frozen" (transferred to a
buffer register) when commanded by the master station
1.3.4 Sequence of Events (SOE) Collection

The RTU shall collect digital status input data and time-of-operation from fast-operating
devices. The RTU shall time-stamp the data using its internal clock with a time resolution
of one millisecond. The time resolution will enable Owner's personnel to determine the
sequential operation of device state changes. Any digital status input data point in the
RTU shall be assignable by Owner as an SOE point. Each time a SOE status indication
point changes state, the RTU shall time-tag the change and store the change (open,
close) and the time-tag of the event in SOE buffers within the RTU. The SOE buffer shall
be sized for at least 1000 events.

When requested from a SCADA system master station, the RTU shall transmit the SOE
data stored in its buffer corresponding to that master station. An acknowledgement of
receipt by the master station shall be made prior to the loss of any data in the RTU SOE
buffer. Data not received at the master station shall be retransmitted. An indication that
SOE storage at an RTU is approaching capacity (at 80%) shall be transmitted to the
master station in the normal periodic scan so that a priority scan can be sent by the
master station to retrieve the SOE data. An additional indication shall provide the status
of RTU SOE data buffer overflow.

1.4 Digital Control Outputs

The RTU shall provide the capability for a master station to select and change the state
of digital control output points. Device control will be used by Owner to control power
system devices including:
(a) Two-state Devices:
Circuit breakers, motor-operated switches, auto/manual switches, relay
disable/enable and other two-state devices
(b) Variable Output Devices:
Raise/lower pulse output for transformer On load-tap-changers (OLTC) control
and other variable output devices control.
The RTU shall have the capability for control outputs as described below:
1.4.1 Two-State device Control
For control of two state devices, a pair of outputs (open/close) contacts shall be supplied
that drive control output relays. . Upon command from a master station using the checkbefore-execute sequence, the appropriate control output shall be operated for a preset
(momentary) time period. The operation period shall be adjustable for each point from 0.1
to 2 seconds.
The contacts of control output relays shall be used for initiating heavy duty CB/ isolator
close /open relays.
1.4.2 Raise/Lower Pulse Outputs
The RTU shall provide the capability to generate raise/lower pulse outputs which will be
used for transformer tap position settings. A pair of outputs (raise/lower) pulse contacts
shall be supplied that drive control output relays.

When commanded from the master station, the appropriate raise or lower output shall be
operated for the selected time interval. The raise/lower output for each point shall operate
over a range of 0.1 to 4 seconds.

1.4.3 Control Output Relays

Control output relays shall be supplied by the Contractor for each control output
described above. Each control output relay shall consist of at least one changeover
output contact. The output contacts shall be rated for 5 Amps at 220 Vdc, and shall
provide arc suppression to permit interruptions of an inductive load. Relay coils shall be
shunted with diodes to suppress inductive transients associated with energizing and deenergizing of the relay coils. The relays shall conform to the IEC 60255-1-00 and IEC
60255-5 requirements.

1.4.4 Dummy breaker relay

The Contractor shall provide a latching relay to be used to simulate and test supervisory
control from the RTU. The simulation relay shall accept the control signals to open and
close from the RTU and shall provide the correct indication response through a single
contact indication input point.
1.4.5 RTU Control Security and Safety Requirements
The RTU shall include the following security and safety features as a minimum:
1.

Select-check-operate sequence for control output. The verification message for check
before-operate control sequences shall be obtained by re-encoding the verification
message directly from the control point selection lines. Thus, a simple reflection of the
received message is not acceptable.
2.
Partitioned database for each master station and control point shall be selectable only
from one master station. A Control point in the RTU once selected by a Master station
shall not be operable from another Master station.
3.
4.
No more than one control point shall be selected at any given time in the RTU. A
detection and lockout method shall be provided that prevents a control operation if more
than one control point has been selected.
5.
6.
The control selection shall be automatically cancelled if after receiving the "control
selection" message, the "operate" command is not received within the set time period.
7.
8.
No false output shall result during power up or power down. No false output shall
result from inadvertent connections to a circuit card.
9.
10. All control output connections shall have protective covers.

1.4.6 Control Disable (Local/Remote switch)

A manual Local/Remote switch shall be provided for each RTU to disable all control
output relays by breaking its power supply connection. When in the "Local" position, the

Local/Remote switch shall allow testing of the control outputs without activating the
control output relays.

A status input indication shall be provided for the Local/Remote switch to allow the
SCADA system to monitor the position of the switch.
1.5 Time Synchronization
The RTU shall maintain real-time clock and shall have an internal RTU time base with a
stability of 1 ppm i.e. 3.6 milliseconds per hour or better. The RTU shall maintain the realtime clock information even when the auxiliary power to the RTU is switched OFF.
The accuracy of the internal clock for shall be maintained by protocol messages from the
master station. The RTU time will be set from time synchronization messages received
from master station at every 10 minutes when using the IEC 60870-5-101/IEC 60870-5104 communication protocol over dedicated lines. The RTU shall be provided with
suitable hardware and software for accepting time synchronisation from a GPS using
IRIG -B/ASCII time messages/1 pps signals.
Any hardware required for multiplication of the ports of the GPS shall also be supplied by
the Contractor.
1.6 Power Supply
The RTU power supply module shall have following characteristics:
1.
2.
3.
4.
5.

Suitable for operating at nominal 48 V DC with voltage variation from 41 to 58 V DC.

Suitable for positive DC earth system.
Have reverse polarity protection.
The Contractor shall supply any hardware as required to convert input voltage to the
required internal voltages for the RTU hardware. The RTU shall operate with grounded
input power from Owner. The RTU shall not place additional ground on the input power.

6.
7. Each RTU shall have the capability of automatic start-up and initialisation following
restoration of power after an outage without need of master station intervention. All
restarts shall be reported to the connected master stations.
8.
9. Secondary power shall be provided to the RTU at 230 Vac, 50 Hz, single-phase for noncritical auxiliary equipment including heaters, internal lighting, and internal maintenance
outlets.
1.6.1 Power Supply Protection
Over voltage and under voltage protection shall be provided to the input and output of the
power supply in addition to output over current protection to safeguard the RTU internal
logic from being damaged as a result of a component failure in the power supply and to
prevent the RTU internal logic from becoming unstable and causing mal-operation as a
result of voltage fluctuations.
1.6.2 Power Supply Failure Indicators
The RTU shall have a status point which shall be set if the power to the RTU has been
cycled (off-on) for any reason (including maintenance). The successful transfer of this
indication to master station shall reset the power fail status point.

1.7 RTU/SIC Panel Construction

The Contractor shall provide simplex type panel for the RTU/SIC. The constructional
features and internal wiring of the panel shall be similar to the construction features
defined for Control and Relay Panels specifications as per Annexure-. (ULDC)
1.7.1 Interconnections
The Contractor shall be responsible for laying and termination of all cables at both ends
required under the project which includes interconnections among contractor supplied
equipment and their interconnection with owner's panels. Testing and commissioning of
these interconnections shall also be done by the contractor.
All power and control cables shall be as per owners technical specifications for the
same.(ULDC) The signals cables for communication, I/O points shall be shielded type to
provide suitable protection against noise and electromagnetic interference. All the cables
shall be suitably sized to meet the functional requirements.
1.7.2 Terminal Blocks
Terminal blocks shall be screw-type/ stud type/ cage clamp type/ self stripping/ spring
type having provision for disconnection (isolation), with full-depth insulating barriers made
from moulded self-extinguishing material. Rust-proofing of metallic components shall be
provided by means of the metal used or a suitable coating. Terminal blocks shall be
appropriately sized and rated for the electrical capacity of the circuit and wire used.
1.7.3 Assembly and Components Identification
Each assembly (to the level of printed circuit cards) shall be clearly marked with the
manufacturer's part number, serial number, and the revision level of the component.
Changes to assemblies shall be indicated by an unambiguous change to the marked
revision level.
All electronic parts (such as capacitors, resistors, and integrated circuits) shall be marked
either with the characteristics of the part or with an industry standard part
number. Where custom parts are provided (such as read-only memories), the part
shall be marked such as to specifically identify the part when similar parts may exist.

All printed circuit card cages and all slots within the cages shall be clearly labelled.
Printed-circuit cards shall be keyed for proper insertion. It is desirable that printed-circuit
cards be keyed to prevent insertion into incorrect locations.
All circuit protection breakers shall be of the manually operated, moulded-case type, and
shall provide thermal over-current and instantaneous short-circuit protection in each pole.
1.7.4 Noise Level
The audible noise generated by the RTU equipment shall not exceed 50 dbA measured
at one meter from the enclosure.

1.8 Environmental Requirements

The RTU will be installed inside buildings without temperature or humidity control. The
RTU shall be capable of operating in ambient temperatures from 0 to +50 deg C with rate
of temperature change of 20 deg C/hour and relative humidity up to 95% non-condensing
at 40 C.
1.9 Availability Requirements
The RTU will perform data acquisition and control of important equipment necessary for
the operation of Owner's power system. Any failure of an RTU to perform its functions will
adversely affect power system operations. An availability of at least 99% is required
excluding communication and power source. The failure of any RTU function and
hardware shall be considered as unavailability of the RTU. The methodology to calculate
the availability is defined in section "SCADA specification ".
1.10 RTU Size and Expandability
The RTU shall be supplied for the sizing as per Appendix IA (BOQ). The RTU shall
contain alteast 20% spare capacity for every I/O point type, as wired spare capacity
which can be used without any hardware additions in the RTU/SIC Panels including TBs,
wiring etc. In addition to the above, the RTU shall have the capacity to add additional I/O
modules to expand the overall point count of the RTU by a minimum of 50% of the
supplied capacity. All the I/O points available in the modules/cards supplied in the RTU
shall be wired to TBs.
1.11 RTU design & Maintainability
The RTU design shall facilitate isolation and correction of all failures. The following
features which promote rapid problem isolation and replacement of failed components
shall be provided:

Self-diagnostic capabilities within each RTU which can be initiated at the RTU site
On-line error detection capabilities within the RTU and detailed reporting to the
connected master stations of detected errors

1.12 RTU Tests

The contractor shall supply a type tested RTU. The bidder shall submit RTU type test
reports along with the bid for same make & model of RTU. The type test report shall
include the tests indicated in Table 1 & 2. Type test reports as per other equivalent
standards are also acceptable provided they meet or exceed the minimum requirements
specified in this specification. In case the RTU type test reports do not meet specification
requirements, relevant type test shall be performed without extra cost to POWERGRID.
Routine test to be performed in the factory & field tests to be performed at site on
RTU/SIC panels are indicated in Table-1.

SAT/End to End Testing Requirement and Procedure

The Contractor shall be responsible for providing field installation and

testing. All hardware will be installed, configured and adjusted. Interfaces to all
field inputs and outputs established and their operation shall be verified and all
test readings shall be recorded. Upon completion, a field performance test shall
be performed to exercise all functions of the RTUs and duplicate selected factory
2

acceptance tests to the extent possible. This testing will include, but not be
limited to the following test :

RTU initialization

Proper functioning of hardware and software by exercising of

selected RTU functions using the master plan

Proper RTU communications interface.

Test operation of all diagnostic software and confirm

issuance of meaningful messages for all types of error conditions.

Test time synchronization and accuracy of the RTU from the

master plan.

RTU database verification including point-to-point operation

and scaling accuracy using the master station.

The detailed test procedures shall be submitted by the contractor at least

4 weeks prior to installation of RTUs at site..

1.13 RTU Test tools

The Contractor shall supply the following RTU test tools/equipment. These test
equipment shall be used for RTU configuration & maintenance purposes in addition to
other testing as mentioned here.
a) RTU database configuration & generation tool
b) Master station-cum-RTU simulator
c) Laptop for above software tools along with interfacing cables & connectors
a) RTU database Configuration & generation tool
The RTU database configuration & generation software tool shall be provided along with
all software and hardware needed to configure, modify, compile, and download the
database of the RTU. The configuration tool shall also provide for documentation and
printout of the RTU database in a well organised form.
b) Master station-cum-RTU simulator & protocol analyser software tool

Master station-cum-RTU simulator tool

The master station-cum-RTU simulator tool shall be capable of simulating the messages
of both the Master station and the RTU for the IEC 60870-5-101 and IEC 60870-5-104
protocol. It shall be used to monitor and test the RTUs/Master station operation and
communication interfaces.
The simulator tool shall be capable of transmitting and receiving single and repeated
messages using the communication protocol. Each received message shall be checked
for validity, including the check code. It shall maintain and display error counters so that
the number of errors during a period of unattended testing can be accurately determined.
It shall be capable of formatting and transmitting, both as one-time and periodic
transmissions, any master station-to-RTU command. It shall also be possible to prepare
illegal messages, such as messages having invalid check codes, for transmission. The
simulator shall be programmable to transmit and acknowledge a set of messages. It shall
be capable of capturing the communication traffic for storage and analysis.

c) Laptop PC
A Pentium-IV or better laptop PC shall be used for the above mentioned software tools.
The laptop PC shall be provided with all hardware accessories including cables,
connectors etc. required for interfacing with Master station and RTU. A carrying case and
a suitable power adaptor (input 230VAC, 50Hz) for laptop PC shall also be supplied.

(To be taken from latest powergrid specifications).

After Sales Support

Warranty Two years after acceptance of end to end testing.
Post Warranty Annual Maintenance for 10 years

1.14 DOCUMENTATION
The Contractor shall submit hardware and software documentation in three sets for
RTU/SIC to Owner for review and approval. After approval four set of all the documents
shall be submitted as final documentation. Any changes observed during field
implementation shall be incorporated in the as-build drawing and four sets of same shall
be submitted to owner.

The following minimum documents are envisaged for submission:

1.
2.
3.
4.
5.
6.

Detailed engineering drawing of RTU/SIC panels

Details of RTU database for all point counts
Details of hardware to be supplied
Details of software to be supplied
RTU Functional Design & Specification
I/O list for all points

7. RTU Hardware, maintenance and operation manuals.

8. RTU FAT/SAT documents

Further contractor shall provide documents in soft copy as well (CD media) in two
sets. 2 sets of CD/Floppy for system back up shall also be provided to restore the
complete system including RTU database in case of system crash due to unforeseen
reasons.

TABLE 1
List of Tests on RTU/SIC
Test
Nos

DESCRIPTION OF THE TEST

Check for BOQ, Technical details, Construction & Wiring as per RTU/SIC
drawings

Type
test

Routine
test

Field
test

17
18
19

Check for RTU database & configuration settings

Check the operation of all Analog inputs, Status input & Control output points
of RTU/SIC
Check operation of all communication ports of RTU
Check for communication with multiple master stations using partitioned
databases
Check for auto restoration of RTU on DC power recovery after its failure
Test for RTU self diagnostic feature
Test for RTU time synchronization from Master and GPS
Test for RTU SOE feature
Test for down loading of RTU data base from master station
End to end test (between RTU & Master station) for all I/O points
RTU Analog accuracy test for Analog inputs
Test for RTU operation with DC power supply voltage variation
Test for RTU internal Clock stability
Test for RTU Noise level measurement
Test for IEC 60870-5 -101 & IEC 60870-5-104 protocol implemented and matching with
protocol profile of existing RTU
Test for Control Security and Safety for Control outputs
Other functional tests as per technical specification requirements.
Test for RTU as Data concentrator for IEC 60870-5-101 and 60870-5-104 protocol.

20

Test for operation of redundant CPU and Power supply unit

2
3
4
5
6
7
8
9
10
11
12
13
14
15
16

Test for Modems

21

EMI/EMC IMMUNITY TESTS FOR RTU

22
23
24
25
26
27
28

Surge Immunity Test as per IEC 60870-2-1

Electrical Fast Transient Burst Test as per IEC-60870-2-1
Damped Oscillatory Wave Test as per IEC 60870-2-1
Electrostatic Discharge test as per IEC 60870-2-1
Radiated Electromagnetic Field Test as per IEC 60870-2-1
Damped Oscillatory magnetic Field Test as per IEC-60870-2-1
Power Frequency magnetic Field Test as per IEC-60870-2-1
INSULATION TEST FOR RTU

29

Power frequency voltage withstand Test as per IEC 60870-2-1

30
31

1.2/50 s Impulse voltage withstand Test as per IEC 60870-2-1

Insulation resistance test

ENVIRONMENTAL TEST FOR RTU

32
33

Dry heat test as per IEC60068-2-2

Damp heat test as per IEC60068-2-3

TABLE 2 RTU TYPE TEST REQUIREMENTS

Test
Nos.
1
2
3
4
5
6
7
8

Test Name
Surge Immunity Test
Electrical Fast
Transient Burst Test
Damped Oscillatory
Wave Test
Electrostatic
Discharge Test
Radiated
Electromagnetic Field
Test
Damped Oscillatory
Magnetic Field Test
Power frequency
magnetic field
Power frequency
voltage withstand

EUT
status
on

Level-3

Power Supply points

CM
DM
2kV
1kV

on

Level-3

2kV

1kV

on

Level-3

2.5kV

1kV

2.5kV

on

Level-3

+/- 6 kV in Contact discharge mode or +/- 8

kV in Air
discharge mode

on

Level-3

10 V/m electric field strength

on

Level-3

30 A/m at 1MHz of magnetic field strength

on

Level-3

30 A/m of magnetic field strength

(Continuous duration
sine wave)

off

1 KVrms for 1 minute

off

2 kVp

Test Level

1.2/50s impulse
voltage withstand

10

Insulation Resistance
Test

off

11
12

Dry heat test

Damp heat test

on
on

I/O points
CM
2kV

Measure Insulation resistance using 500V DC

Megger
before & after Power Freq & Impulse voltage
withstand
tests
Continuous operation at 550 C for 16 hrs
at 95% RH and 400 C

Note:1. EUT - Equipment under Test

2. CM - Common Mode; DM - Differential mode
3. I/O pints do not include Communication ports
4. Passing Criteria
0 - no failure: normal performance within the specified limits
A: minor failure: temporary degradation or loss of function or performance which is selfrecoverable

Passing Criteria
A

No break down
or flashover
shall occur
No break down
or flashover
shall occur
As per
manufacturer
standard
0
0

Committee Draft

Report on Minimum Standard requirements for

ULDC Scheme (phase-II) in respect of the constituents of Northern

region.

Committee Report on Minimum Standard requirements for ULDC Scheme (phase-II)

in respect of the constituents of Northern region.

Background: Load dispatch & communication facilities presently available in Northern

Region at NRLDC, SLDCs and Sub-LDCs were commissioned beginning 2002 under
Unified Load dispatch and communication (ULDC) scheme and were put in commercial
operation in August 2002. The ULDC Scheme of Northern Region was established by
POWERGRID in closed coordination with all the constituents of the region. The
maintenance of the various components of the ULDC scheme is also being carried out on
regional basis with support of the suppliers in various degrees. The periodic review of the
maintenance activities is carried out by USMG (Unified Scheme Maintenance Group) at
NRPC level. The utility of these facilities has been appreciated by all the users of the
system. At the time

of project formulation for ULDC scheme, based upon various

considerations only critical component of the Northern Region were included in the
project. Subsequent to commissioning of ULDC Scheme the expansion of Power System
has taken place at considerable pace, parallelly organizational, regulatory and
technological changes have also taken place, the constituents have felt the need for
expansion of ULDC system by inclusion of more component of the Grid for monitoring.
The need and implementation methodology for expansion of ULDC scheme of northern
region was discussed by the constituents in various forums. Finally during 8th NRPC
meeting after deliberations it was agreed in principle that the expansion of ULDC scheme
shall be taken up by the constituents independently. It was also decided that the
communication parameters, minimum standards and time frame would be finalized.
POWERGRID help may also be sought by the constituents for up gradation/expansion of
the ULDC scheme. As a follow up the issue was deliberated in the 23rd USMG meeting
held on 25th April 2009 at NRPC. The relevant portion of the NRPC and USMG MOM are
enclosed at annexure-I. Accordingly NRPC has constituted a Sub-Committee comprising
of

the

following

members

vide

their

letter

of

reference

(o)/NRPC/USMG/2009/419-26 dated 18.03.2009.

1. Sh.Niraj Gulati, Chief Engineer (SO), HVPNL

2 Sh. V. K. Aggarwal, GM, NRLDC
3. Sh. D.K. Jain, Director, LD&T, CEA
4. Sh. Suneel Grover, Director, PR, HPSEB
5.Sh. A.S. Kushwaha, AGM (LD&C), POWERGRID and
6. Superintending Engineer (Operations), NRPC-Member Convener

NO.

SE

The terms of reference of the committee are as follows:

(i) Framing of guidelines for the specifications to be finalized by the constituents for
expansion/replacement of SCADA/EMS system for grid operation;
(ii) Framing of Guidelines for integration of new substations/power plants to the control
centers;
(iii)Framing of guidelines for finalizing specifications for inter control centre (LDCs)
connectivity for data exchange; and
(iv) Design criteria for communication system for LDC facilities.

Major components of the Northern Region ULDC Scheme are EMS/SCADA system, RTUs
and Microwave (MW), Fiber Optic (FO), PLCC based communication system along with
auxiliary power supply system. The SCADA/EMS system has been installed at Northern
Regional Load Despatch Centre (NRLDC) under central sector and at SLDCs/Sub-LDCs in
the state sector. The RTUs and communication equipment are installed at substations and
power plants in the states as well as in the central sector. Under ULDC Project
communication systems comprising of Power Line Carrier Communication (PLCC),
Microwave and Fiber Optic based communication were established. PLCC is being used to
transfer data from RTU locations to the nearest wide band / control center locations.
Wideband communication system comprising of Microwave and Fiber Optics is being used
for data transfer between control centers and from substations located on wideband nodes.
Microwave links have been established with 8 Mbps capacity, whereas fiber optic links are
established with STM-1 (155 Mbps) capacity. As regards functionality at various control
centers, it may be mentioned that SCADA and EMS have been provided at NRLDC as well
as at all the SLDCs with almost identical functionality whereas at Sub-LDCs only SCADA
facility has been provided with storage of data for limited period.

The ULDC scheme which has been in operation since 2002 was conceptualized in late
1990s, the specifications were framed around 1995-96 and orders were placed by 1998.
Subsequent to commissioning, during the last around seven years the users have gained
wide experience on the system, at the same time several changes have taken place within
and outside organizations in a very short span of timed, the power system is growing at a
very fast speed, the technology changes in the field of communication and information
technologies have also taken at equal pace.

With the above background, in order to meet the growing demand of the users due to
structural and regulatory changes, expansion of power system requirements and technical
obsolesce

the

committee

has

examined

the

various

aspects

of

ULDC

upgradation/expansion within the purview of Terms of reference of the committee. The

detail discussion is provided below.

The Details of Existing System:

Hierarchical System: Hierarchical concept has been adopted in ULDC scheme

of all the regions. Accordingly Northern Region ULDC scheme has been
established in the hierarchical order which includes Northern Regional Load
Despatch center (NRLDC) at the apex level and the Remote Terminal Units
(RTUs) at Power Station/Sub station at the lowest level. In between there are Sub
Load Despatch Centers (Sub LDC) and State Load Despatch Centers (SLDC).
The control centers are NRLDC, nine no of SLDCs and 23 no of Sub-LDCs. The
RTUs acquire and forward parameters like voltage, frequency, MW, MVAR,
Breaker and Isolator Positions etc. to Sub-LDC/SLDC/NRLDC in real time. The
central sector data is directly transmitted to NRLDC and the state sector data is
transmitted to either Sub-LDC or to the SLDC. The data flows in the hierarchy as
shown in the diagram below. The state sector/BBMB data reaches to NRLDC via
SLDCs. For data exchange between control centers ICCP protocol has been used.
All the RTUs commissioned are communicating on IEC-60870-5-101 protocol.
This hierarchy has been adopted in line to power system operational philosophy
being followed in each state at the time of the project was conceived, the no of
sub LDCs were decided by the constituents as per the area of responsibility
prevailing in the respective states.
RSCC Delhi

SLDC
UPSEB

Sub-LDC
(RTUs)

SLDC
HVPNL

Sub-LDC
(RTUs)

RTUs - 36

SLDC
PSEB

Sub-LDC
(RTUs)

Moradabad
(17)

Panipat
(12)

Patiala
(12)

Panki
(13)

Narwana
(15)

Jalandhar II
(20)

Rishikesh
(27)

Dadri
(14)

Lalton
Kalan
(8)

Sultanpur

SLDC
RVPNL

Sub-LDC
(RTUs)

3
Heerapura
( 12)
Bhilwara
(29)
Kota
(11)
Ratangarh
(12)

SLDC
J&K

SLDC
BBMB

SLDC
HPSEB

SLDC
DVB

Sub-LDC
(RTUs)

Sub-LDC
(RTUs)

Sub-LDC
(RTUs)

Sub-LDC
(RTUs)

Gladini
(8)

Dadri
(5)

Hamirpur
(8)

Bawana
(5)

Bemina
(8)

Ganguwal
(6)

Kunihar
(8)

Bamanauli
(12)

Jalandhar I
(4)

Gazipur
(8)

Panipat

Gopalpur

CPCC
Kanpur

RTUs - 6

Hardware Architecture
The distributed hardware configuration of the existing SCADA/EMS system includes the following
subsystems:
SCADA/EMS servers
support the functions of SCADA, Real-time Dispatching, Power System Analysis and
Operation Scheduling functions.
Operate in a primary-standby relationship for redundancy purposes.
Consist of two high performance Digital 64-bit RISC based AXP machines
(Alphaservers) in a dual redundant configuration (Primary and Stand-by)
Communication Front-ends(CFEs) that drives the serial communication lines connected to the
RTUs.
ICCP (Inter-Control centres Communications Protocol)

servers

that

support

inter-site

exchanges from Sub-LDC to SLDC and between SLDCs and NRLDC.

ISR server for Information Storage and Retrieval functions (operate in a primary-standby
redundancy). This is available only at RLDC and SLDC. This is used for retrieval of Old data
and Creation of Reports .
DTS (Dispatcher Training Simulator) server and its associated DTS operator consoles that
provides the dispatchers training capability. This is being used for the training purpose and is
available at NRLDC only.
Development Server and its associated development console that provide software utilities
used to develop and maintain the SCADA/EMS software, displays and databases.
Operator consoles that handle the man-machine interface for system control and supervision
operations.
Network

Management

Console

that

provide

the

Configuration

management,

fault

management and performance monitoring capabilities.

WAN routers, in a redundant configuration, that allow several connections with the other
Northern Region control centres (SLDCs and CPCC) and with the Remote VDU (Video
Display Unit) .
Peripheral equipment such as printers, Video projector, satellite time receiver system,
CD/ROM servers.

SCADA/EMS
Servers

Communication
Front-end

ISR
Servers

DTS
Server

ICCP
Servers

Operator
Consoles
(*)

DTS
Operator
Consoles

WAN
Routers

Development
Server

Development
Console

Network
Management
Console

Peripheral
Equipment

To
SLDCs,
To RTUs

Remote
VDUs

Headquarters

(*) Five 2-CRT consoles, two 1-CRT consoles and one Operations Scheduling Console

Design Criteria
The design criteria adopted for ULDC scheme was constrained with the available technology and
organisational set up prevailing at that time, these aspects have gone through several changes.
Due to organisational and regulatory changes in the power sector the functional requirements of
the constituents have also undergone change. With the availability of advance cost effective,
techno-economic products, we are now in a better position to meet these requirements. In the
following paragraphs the design considerations which need changes especially in respect of
integration of various components have been elaborated.

RTU interface to primary devices: -- In the existing system, separate transducers

have been provided for each function i.e. MW, MVAR, Frequency & voltage. Analog transducers
converts 1A/5A Secondary current and 110 V secondary voltage into 4-20 mA signal which
means one analog quantity is converted into another analog quantity of lower magnitude suitable
to the RTU as input quantity. The status signals are wired to the RTUs either directly or through
the contact multiplying relays. Individual transducers increase the wiring as well as the no of
components in the system.

Now in stead of conventional transducers , Multi function transducers (MFTs) are also available
which gives the output in Modbus protocol in digital format for all types of values being acquired
under ULDC, the MFTs can also provide no of additional parameters

such as each phase

current, phase voltage, energy values etc. At the same time the wiring in the panels is also
reduced. As MFTs provide digital output it is directly connected to the communication port of the
RTUs removing the requirement of analog input card in the RTUs, this will effectively reduce the
cost of RTUs as well wiring the panels. Therefore, it would be better option to adopt MFTs in
stead of individual transducers. The diagram below indicts the existing as well the proposed
arrangement.

4 -2 0 m

M W

T
M

4 -2 0 m

4 -2 0 m

4 - 2 0 m

V A r

V o lt

P T
F r e q

Existing Arrangement
T r a n s d u c e r

CT

M O D B US/

M u ll ti F u n c ti o n
T ra n sd u ce r

PT
Proposed Arrangement
3

IE C 60 87 0- 51 03

RTU Design:The analog data is acquired by the RTU through the transducers as explained above. The digital
data is directly wired to the RTUs. The design of existing RTUs is robust and flexible. The RTUs
are operating in uncontrolled environment. The analog and digital I/O can be added by addition
for electronic cards. However, there is no back up to Power Supply and CPU of RTUs which is
available in present day RTUs. The back ups to Power Supply and CPU would make RTU more
reliable. Further non availability of spares at reasonable price making it difficult to expand the
existing RTUs.

RTU to Communication Front End (CFE):- Around 350 RTUs were installed in the ULDC project
in various constituents which reports to the Sub-LDC or SLDC. The Central Sector RTUs are
reporting directly to NRLDC. The protocol adopted for RTU data to control centre is IEC 60870-5101. As IEC-60870-5-101 protocol has been used for RTU data communication, one serial port is
required in the CFE for each RTU. This has its limitations in management for number of spares,
expandability due to interdependency between hardware and software ,obsolescence and OEM
dependency.

With the introduction of IEC 60870-5-104 protocol ,the dependency on the hardware and software
has reduced. In this protocol the communication between RTU and CFE is IP based instead of
serial connection, thus removing the serial interface card and hardware dependency on the
OEM.

With the emergence of Substation Automation System (SAS)

technology , the conventional

Control panels is being replaced by Intelligent Electronic Devices (IEDs) and the Protocol IEC
61850 is being adopted for the communication among different equipments of the substation.
However IEC 61850 protocol is presently limited to within substation itself and the protocol IEC
61870-5-101/104 is still followed for communication between SAS and control centre

Control centre

Substation/Plant
IEC 60870-5-101

IEC
3

01
-5-1
0
8
60

Serial
Serial

Serial

SAS

GATEWAY

IED

IEC 61850

RTU

Serial

Transducer

4-20mA

CFE

Existing Arrangement

CFE

IP

SAS

C
IE

4
-10
5
0
87
60

IP

RTU

GATEWAY

IED

IEC 61850

Control centre

IEC 60870-5-104
IP

Substation/Plant
MFT/
MODBUS
Energy
Meter

Current Practice
The usage of IEC 60870-5-104 protocol has its implication on the design of communication
network also. Presently most of the RTUs are reporting on PLCC at least on first half. IEC
60870-5-104 protocol works on IP based communication, analog Communication can not meet
this requirement. Therefore IEC 60870-5-104 protocol can be adopted selectively only as long as
practice of usage of analog PLCC is continued. This aspect of communication design has been
discussed in detail in the subsequent Para.

Database Model:The database modeling concept being followed in Northern Region is based on Common
Regional Model both for content as well as tools/process. In the present procedure for data base
modification the excel sheet of data base is made by the constituents which is forwarded to
NRLDC. The changes in database are incorporated in SCADA System at NRLDC which are then
propagated to other control centers. The procedure being followed is described in the diagram
given below. Non timely updating of data modeling results into poor visualization of the Network.
Therefore, if any constituent is not able to update its ICCP database due to any reason its
implication is reflected on the usage of functions by the other constituents also therefore

interdependency of the constituents is quite high as far as data base modeling is concerned this
as of data base model needs review.

Further at the time of ULDC implementation the electrical boundaries of the region were very
clearly defined, now Northern Region has been interconnected with other regions through several
synchronized links which are planned to increase in future, the regional electrical boundaries
have become multiple and are difficult to manage without regular data update in sync with other
regions.

Consequently the interregional exchange of power is increasing.

Northern Region

constituents make the commitment for purchasing power in the power plants installed in other
regions or even in other countries. This may necessitate the model and data exchange between
different vendors and various regions at RLDC level. The complications in electrical network
modeling due to increased interconnections between the regions, regional level modeling would
not be adequate. Further under ULDC Scheme SCADA/EMS system in region is from a single
supplier. For expansion/upgradation requirement SCADA/EMS system of a single vendor in a
region would not help due to increased interconnection among regions. Keeping all this in view it
is suggested that each constituent take the responsibility of modeling of the network under its
jurisdiction and exchange the electrical model with other constituents. At NRLDC level regional
model up to a certain voltage level would only be required. The model and data exchange
between constituents and NRLDC may be required, this shall be possible only when the common
standard is followed by all the constituents.

Co m m o n D A TA
B ase M o d el

S te p 4

S te p 3

ep

S te p 2

St

S te p 1

RLDC END

S te p 3

ep

M e rg e a t
RSCC
End

D BB Tool
4
ep
t
S
St

Step 5

DBB
M a s te r
F ile s ( E x c e l)

DBB
M a s te r
F ile s
In c re m e n ta l
DBB
F ile s

SLDC END

Co m m o n D A TA
B ase M o d el
DBB Tool
e
St

C o p y o f M a s te r D B B f ile s a n d M a s te r D a ta B a s e
m o d e l to A L L S L D C s b y R L D C
I n c r e m e n ta l C h a n g e s b y S L D C fo r th e ir A r e a s in
D B B file s , im p o r t in to M a s te r D a ta b a s e M o d e l
a n d v a lid a tio n .
C o p y o f v a lid a t e d in c r e m e n ta l D B B file s fr o m
3
S L D C to R L D C
I m p o r t o f In c r e m e n ta l D B B file s o f S L D C a n d
R L D C in t o m a s t e r d a t a b a s e m o d e l a n d v a lid a t io n
a n d c r e a t io n o f fin a l C o m m o n d a ta b a s e m o d e l a t
RLD C end

The standard for CIM (common information model) data modeling for EMS applications (IEC
61970) has been published to take care of the above issue. The database handling can be
harmonized by standardizing the data model using CIM in Indian Context. Hence it is important to
develop the CIM model content applicable to our system

DATA exchange between Control centers:-

The protocol adopted for control

centre to control centre communication is ICCP. The central sector data and data of other
constituents is acquired by the all the constituents from the NRLDC. Now since the constituents
are purchasing power from other power plants installed in other regions also, the generation data
of these plants would be required at the SLDC level. Presently NRLDC is acquiring the data of
other regions through NLDC which can be shared with constituents also.

The implementation and configuration setting for ICCP exchange requires support from the
original contractor. The support of Siemens for Integration of Maharashtra SLDC with WRLDC
and support of GE for integration of WRLDC& SRLDC with NLDC were taken. In Uttrakhand
case, the services of AREVA has also been envisaged for modification at NRLDC end. The
requirement of such support services would increase if the SSCADA systems of different venders
are installed in various constituents, timing of installation would also be an issue.

Apart from above , Secured ICCP protocol and WAN routers with Firewalls need to be deployed
for enhancing the security of system. However secure ICCP can not be unilaterally implemented
at one node as it will need matching support from remote node also.

Time Synchronization:- In the NR ULDC system, A GPS clock is available at each Control
centre which synchronizes the CFE. The RTUs are being time synchronized from the CFE using
the feature of IEC 60870-5-101 protocol. With the adopted methodology of time synchronization
inter RTU time accuracy of around 10 milliseconds is expected. When IEC 60870-5-104 protocol
is used for

RTUs, the accuracy of 10 milliseconds would not be possible. Therefore it is

suggested that each RTU is provided with GPS for time synchronization as the cost of GPS is not
very high.

The events are being time stamped at RTU and maintained in file system which is transferred to
control centre either on demand or periodically. Further these files are being merged at SLDC
and NRLDC through a script.

Recently while integrating the SAS system it has been observed that time stamped events are not
being maintained in the file system but it is being transferred as an event with time stamp
message to the control centre as part of IEC 60870-5-101 protocol implementation.
Accordingly another script was written to merge the file system and SOE time stamped message
into the separate file.
The ICCP protocol implementation has also the feature to transfer the events with time stamp.
However its deployment need overall change in SOE handling and a switch to making all SOE as
part of ISR is recommended.

Number Of Control Centers:- In NR-ULDC scheme the number of Sub-LDCs were chosen by
each constituents as per area of responsibility. Sub-LDC can observe the network of their area
only. If one Sub-LDC desires to check the Status of neighboring area of their State it is not
feasible in the present format. After Electricity Act 2003, SLDC is the apex body for the operation
within its jurisdiction. The responsibility has increased and accordingly the work load in the
system. Operators would need enhanced visibility of the system. The underlying control centers
of the discom would also need exchange of data with state load dispatch centers. Further with the
growing importance of control centers for Power system Operations and enhanced security threat
, it has become the need of the hour to create a backup Control centre. It is suggested that the
back up SLDC can be created at one of the Sub-LDCs. But the constituents who do not have any
Sub-LDC and NRLDC would need to determine the location for backup SLDC. The data flow from
both the RTUs to both SLDCs (Main and backup) would be directly from the RTUs preferably. In
case this is not possible due to communication constraints, some of the RTUs can be converted
as Data concentrator which can communicate to both the SLDCs (Main and Back Up) Other SubLDCs can be provided with the operator console of SLDC. The main and backup Control Centre
would provide no of advantages over the existing arrangements. A Comparison chart for the
comparison of backup Control centre vs SubLDC is given in the table below:-

S.No.

Subject

Main and Backup SLDC

SLDC and Sub-LDC Concept

In
case
of
Emergency
at
Main
SLDC
Control centre

All the functionality and

data will be available at
Backup SLDC and SubLDC will be getting their
data from Backup SLDC
on the remote console

Sub-LDC will be getting the data

of their area only. The data of
other Sub-LDC will not be
available.

Database
Maintenance

The database and displays

will be centralized and
automatically backup at
backup SLDC. So it is
easy to maintain.

The database and displays needs

to be maintained at SLDC as well
as Sub-LDCs. The process is
complex to maintain.

Manpower

The Manpower required to

maintain the system will be more
in case of more than one sub LDC
and also proportionally more in
case the focus/process/database
& displays are different

Communication
channel rerouting

The Manpower required to

maintain the system will be
less as only two control
centre need to be
maintained and some
services are only
replicated
WB RTU channel routing
to both Main and Backup
SLDC, but on
implementation of TEC60870-5-104 protocol the
communication channels
would not be an issue.

WB RTU channel routing as per

point 5 above.

Existing Sub-LDC Concept

ICCP
CFE
ICCP

NRLDC

SLDC
3

ICCP
WB Location

RTU
MUX

CFE

CFE

Sub
LDC

Sub
LDC

NRLDC

ICCP
CFE

Main
SLDC

Rem
ote
CFE

ICCP

101

SLDC

CFE

CFE

Remote CFE

Backup

Remote
Console

WB Location

RTU
cum DC

MUX

RTU

RTU

RTU

RTU

RTU

Main and Back up SLDC

RTU
Energy Management system:-

In the NR ULDC scheme following EMS have been provided:

3.0

Real Time Function:

Load Generation Balance
-Monitoring of operations
-Automatic generation control
-Load shed support
-Production statistics

RTU

RTU

4.0

Power System Analysis

-Power system model update
-State estimation
-Bus load forecasting
-Contingency Analysis

5.0

Pre Despatch function:

- Load forecasting
-Inflow forecasting
-Unit commitment
-Hydro scheduling
-Hydro thermal coordination
-Interchange scheduling
-Interchange transaction evaluation

After that following regulatory changes has taken place:-

Decentralized Scheduling & Frequency Band Regime- ABT

Electricity Act 2003
1. Traders introduced
2. Open access in transmission.
3. Granting of Short Term Open Access (STOA) is responsibility of
RLDC/SLDC.
4. RLDC to declaration Available Transfer Capacity (Smilar need may arise at
SLDCs in case of intra state ABT)
5. Power Exchange schedules need integration in UI and other monitoring
calculation e.g. STOA

These will necessitate in the development of applications for the following applications in the
Indian Context:A.

Scheduling Application

B.

Open Access Application

C.

Metering and settlement Application

D.

Power Exchange Application

E.

Integrated Data Base Management System for Business solution.

The Transmission capacity has to be declared by each SLDC and RLDC for open Access
Applications and Power exchange. This will need the modeling of RLDC and SLDC separately as
per their jurisdiction. The modeling of the boundary area or the equivalency and data exchange
criteria for Power flow Applications will need to be taken care during design of the Power flow
Applications.

Communication System:In NR ULDC scheme, the communication System from RTU to first wide band node/ Control
centre is mostly on PLCC and Communication between control centers is on Wideband
communication

having combination of Micro Wave and Fiber Optic. After commissioning of

ULDC system, for redundancy of the communication network between control centers the
communication system was strengthened by providing backup bandwidth from POWERGRID
telecom Network. The wide band communication diagram is attached at Appendix-I. Now DOT
has decided to allocate the Micro Wave frequency band to other service providers therefore now
MW links are to be replaced with FO based communication system. As the Power System is
expanding very fast, the need for wide band expansion also needs to be followed in similar
fashion. As per revised grid code any utility who wants to connect to the CTU system has to
provide the data and communication system up to CTU data collection Point. The relevant para
after amendment has been reproduced below. (The CERC order is attached at Annexure-II)

4.10 Data and Communication Facilities

Reliable and efficient speech and data communication systems shall be provided to
facilitate necessary communication and data exchange, and supervision/control of the
grid by the RLDC, under normal and abnormal conditions. All agencies shall provide
Systems to telemeter power system parameter such as flow, voltage and status of
switches/transformer taps etc. in line with interface requirements and other guideline
made available by RLDC. The associated communication system to facilitate data flow up
to appropriate data collection point on CTUs system, shall also be established by the
concerned agency as specified by CTU in connection agreement. All agencies in
coordination with CTU shall provide the required facilities at their respective ends as
specified in the connection agreement.

Similar provision may come from SERC for any applicant who want to connect to STU system. In
view of this the data collection point has to be defined as the wide band node. These nodes need
to be expanded and upgraded in line with the Transmission System Planning. In other words the
transmission planning and communication system planning should be in tandem. In case the
communication network is not expanded the new agencies may be forced to go for lease lines
between their substations/generating stations and RLDC/SLDC. Several Leased lines at control
centre could create unmanageable problems due to following reasons:5.0 Low bandwidth (less than E1) would not be available in the times to come especially for point
to point application as the commercial communication technology is gradually evolving
towards IP based network.
6.0 If low bandwidth network is not available, primary multiplexers may be required by each
agency. Several primary multiplexers at the control centre would create logistic as well as
integration problem at the control centers.

7.0 The leased lines can not be monitored by the control centers and may not be as reliable as
our captive communication network especially when the Power plants/Substations are at
remote locations.

Now the technology for Digital PLCC is also available and can be considered for the
communication planning for some standalone bandwidth requirement at RTU node. The digital
PLCC is also suitable for IEC- 60870-5-14 protocol usage.

Security Issues:- In the SCADA/EMS system design, the provision of availability of real-time
data was limited mainly to the operators only. For management the provison of Remote VDU was
provided on the SCADA/EMS LAN only. After restructuring of Power sector the number of stake
holders has increased and it has become now necessary to share the real time data on the public
domain. Accordingly the data was shared on public domain with firewall provision. The typical
Architecture being followed at NRLDC is given below:-

All Boxes with

Host IDS
SSH
Encryp
ted
login

External
External
user
user
side
side

CICSO
firewall

DMZ
ZONE
web & email
server

SCADA
system
Router
POWERGRID
intranet

Similar interface has also been done by HVPNL,DTL, HPSEB, RRVPNL and
the data is shared on public domain . Since the system is integrated the cyber security
requirement may need strengthening.
The available SCADA/EMS system in NR in working on VMS operating system. Open VMS in an
old operating system, the virus penetration probability to this old operating system is
comparatively less, therefore the operating system is acting as shield to virus threat up to some
extent but this situation would not continue for long as the software developers have already
switched over to other operating systems. Presently the suppliers are providing the ICCP on
window based operating system, other applications are either already available on LINUX or in
the proceeds of switching over to LINUX operating system. It is also proposed in subsequent
paras that web system is to be provided with SCADA System to provide data to users other than
control room staff. This further necessitates the comprehensive cyber security systems.

So a policy needs to be framed in line with NERC for cyber security for all the stakeholders. The
security design needs regular auditing for threat perceptions by third Party. The cyber security
threat to the power system is a burning issue. Govt of India is also setting up a special cell for
countering cyber attacks and cyber terrorism which will entrust the responsibility of uniform
security measures to a particular organization for each sector/sub sector.

Training Simulator:- Continuous training is a necessity for control room operators and other
supporting engineers. Under ULDC Project a Digital simulator has been provided at NRLDC
which is to used for training of all the constituents engineers. Since common data base model
was adopted, training at one location for all the constituents was a very good idea as the trainees
can visualize the various power system situations at regional basis as well as at State level.
The operation business for State Load dispatch center operation is becoming different than that
of Regional Load dispatch operation and each SLDC has its own peculiarities and issues . The
need of training simulator is a need of the hour at SLDC also.

O&M: - In NR ULDC SCADA/EMS project provision was made for One Year Maintenance
contract during Warranty period and 2 Years maintenance contract after Warranty period. After
the completion of the maintenance period, AMC was awarded to original supplier on single tender
basis resulting into high O&M cost. It would be better to include the life time maintenance cost as
part of the original contract also so that AMC cost also becomes the part of the competitive price.

Tariff Mechanism and Life time:- The investment made by POWERGRID under ULDC project
is being recovered as tariff over a period of 15 years as the commercial life of the project has
been considered accordingly. However, the Pradhan Committee report and the Task force for
implementation of the report have recommended that life of computer Hardware and Software
should be 7 to 10 years. The draft regulations of CERC for tariff and charges of LDC facilities
also recommends the depreciation of computer hardware in 7 years and software in 3 years.

Recommendation:- Based on the above discussions the committee recommends the following
issues to be considered:2.0

All new RTUs and Substation Automation System for Generating Stations and
Substations to be procured with IEC 60870-5-101 protocol as well as IEC 60870-5-104
protocol. Once the IEC- 60870-5-104 protocol is implemented at the reporting control
center and IP based communication system is extended to the substation to be
integrated, the RTUs/SAS would require IEC-60870-5-104 protocol only. It should be
aimed to switch over to IEC60870-5-104 protocol as early as possible.

3.0

RTUs protocol interoperability profile to be followed both for RTU as well as control
centre is attached at Annexure-II.

4.0

All new RTUs to be procured should have feature of DATA Concentrator redundant
Power Supply and Redundant CPU.

5.0

All new RTUs to be procured with GPS system. A possibility of exploring the interface
with existing GPS of Substation need to be explored.

6.0

The communication protocol to be adopted for communication between MFT/energy

Meter and RTU should be MODBUS.

7.0

Procurement of new RTU should be made the part of Substation Package/generating

station Package. In the Substation Package MFT/Energy Meter should have provision to
give output on MODBUS protocol for RTU.

8.0

For some time control centre shall operate on both IEC 60870-5-101 as well as IEC
60870-5-104 protocol with ultimate intent to switchover to IEC 60870-5-104 protocol. New
CFE should be procured accordingly.

9.0

The communication protocol to be adopted between control centers would be ICCP.

ICCP protocol interoperability profile is also attached.

10.0

One of the Existing Sub_LDC should be converted as Back UP SLDC. CFE of existing
Sub-LDC should be made as Remote CFE of existing SLDC.

11.0

Database modeling should be Constituent specific and IEC 61970-CIM for EMS system
is to be adopted.

12.0

EMS applications should be based on the requirement of the individual constituents.

13.0

The scheduling Application, Open Access Applications, Meter Applications, etc. in

INDIAN CONTEXT need to be kept out of the EMS/SCADA specifications and these
packages may be implemented separately by other IT vendors.

14.0

Data and communication System Planning should be made part of the transmission
system planning.

15.0

Security policy guideline and regular audit etc. is to be adopted by the agency identified
by GOI task force for countering cyber terrorism and cyber attacks.

16.0

DTS should be made available at Each SLDC.

17.0

Life time of the new SCADA/EMS hardware/Software should be as per Pradhan

Committee report i.e. 7 Years and the entire life time AMC should be made part of the
specification requirement.

18.0

The time line of the above implementation by all SLDCs should be matching with
termination of running AMC contract.

Annexure-I

Annexure-II
INTEROPERABILITY PROFILE of IEC 60870-5-101 protocol
This companion standard presents sets of parameters and alternatives from which subsets have to be
selected to implement particular telecontrol systems. Certain parameter values, such as the number of octets
in the COMMON ADDRESS of ASDUs represent mutually exclusive alternatives. This means that only
one value of the defined parameters is admitted per system. Other parameters, such as the listed set of
different process information in command and in monitor direction allow the specification of the complete
set or subsets, as appropriate for given applications. This clause summarizes the parameters of the previous
clauses to facilitate a suitable selection for a specific application. If a system is composed of equipment
stemming from different manufacturers it is necessary that all partners agree on the selected parameters.
The selected parameters should be marked in the white boxes as follows:

Function of ASDU is not used

Function or ASDU is used as standardized (default)

Note :

In addition, the full specification of a system may require individual selection of certain
parameters for certain parts of the system, such as the individual selection of scaling factors for
individually addressable measured values.

SYSTEM OR DEVICE
(System-specific parameter, indicate the definition of a system or a device by marking one of the following
with an

System definition
Controlling station definition (master)
Controlled station definition (Slave)

NETWORK CONFIGURATION

(Network-specific parameter, all configurations that are used are to be marked with )

Point-to-point
Multiple point-to-point

Multipoint-party line
Multipoint-star

PHYSICAL LAYER (Network-specific parameter )

Transmission speed (control direction) :
Unbalanced interchange
circuit V.24/V.28
Standard

Unbalanced interchange
circuit V.24/V.28
Recommended if >1 200 bit/s

Balanced interchange
circuit X.24/X.27

100 bit/s
200 bit/s
300 bit/s

2 400 bit/s
4 800 bit/s
9 600 bit/s

600 bit/s
1 200 bit/s
(for unbalanced transmission only)

2 400 bit/s
4 800 bit/s
9 600 bit/s
19 200 bit/s
38 400 bit/s
56 000 bit/s
64 000 bit/s

Transmission speed (monitor direction) :

Unbalanced interchange
circuit V.24/V.28
Standard

Unbalanced interchange
circuit V.24/V.28
Recommended if >1 200 bit/s

Balanced interchange
circuit X.24/X.27

100 bit/s

2 400 bit/s

2 400 bit/s

200 bit/s
300 bit/s

4 800 bit/s
9 600 bit/s

600 bit/s
1 200 bit/s
(for unbalanced transmission only)

4 800 bit/s
9 600 bit/s
19 200 bit/s
38 400 bit/s
56 000 bit/s
64 000 bit/s

LINK LAYER (Network-specific parameter)

Frame format FT 1.2, single character 1 and the fixed time out interval are used exclusively in this
companion standard.
Link transmission procedure

Address field of the link

Balanced transmission
Unbalanced transmission

Not present (balanced transmission only)

One octet
Two octets
Structured
Unstructured

Frame length
255 Maximum length L (number of octets)
APPLICATION LAYER
Transmission mode for application data
Mode 1 (Least significant octet first), as defined in clause 4.10 of IEC 870-5-4, is used exclusively in this
companion standard.
Common address of ASDU
(system-specific parameter)

One octet

Two octets

Information object address

(system-specific parameter)

Two octets

Three octets

One octet

Structured
Unstructured

Cause of transmission

(system-specific parameter)

One octet

Two octets (with originator address)

Selection of standard ASDUs

(station-specific parameter)

Single-point information

Single-point information with time tag

Double-point information

Double-point information with time tag

Step position information

Step position information with time tag

Bitstring of 32 bit

Bitstring of 32 bit with time tag

Measured value, normalized value

Measured value, normalized value with time tag

Measured value, scaled value

Measured value, scaled value with time tag

Measured value, short floating point value

Measured value, short floating point value with time tag

Integrated totals

Integrated totals with time tag

Event of protection equipment with time tag

<1> :=
M_SP_NA_1
<2> :=
M_SP_TA_1
<3> :=
M_DP_NA_1
<4> :=
M_DP_TA_1
<5> :=
M_ST_NA_1
<6> :=
M_ST_TA_1
<7> :=
M_BO_NA_1
<8> :=
M_BO_TA_1
<9> :=
M_ME_NA_1
<10> :=
M_ME_TA_1
<11> :=
M_ME_NB_1
<12> :=
M_ME_TB_1
<13> :=
M_ME_NC_1
<14> :=
M_ME_TC_1
<15> :=
M_IT_NA_1
<16> :=
M_IT_TA_1
<17> :=
M_EP_TA_1

<18> :=
M_EP_TB_1

<19> :=

Packed start events of protection equipment with time tag

Packed output circuit information of protection equipment with
time tag

M_EP_TC_1

Packed single-point information with status change detection

Measured value, normalized value without quality descriptor

<20> :=
M_PS_NA_1
<21> :=
M_ME_ND_1

Process information in control direction

(station-specific parameter)

Single command

Double command

Regulating step command

Set point command, normalized value

Set point command, scaled value(required only for analog output command)*

Set point command, short floating point value

Bitstring of 32 bit

<45> :=
C_SC_NA_1
<46> :=
C_DC_NA_1
<47> :=
C_RC_NA_1
<48> :=
C_SE_NA_1

<49> :=
C_SE_NB_1
<50> :=
C_SE_NC_1
<51> :=
C_BO_NA_1

System information in monitor direction

(station-specific parameter)

<70> :=
M_EI_NA_1

End of initialization

System information in control direction

(station-specific parameter)

Interrogation command

Counter interrogation command

Read command

<100> :=
C_IC_NA_1

<101> :=
C_CI_NA_1
<102> :=
C_RD_NA_1

<103> :=
C_CS_NA_1

Clock synchronization command

(optional, if GPS is used for time synch. of the RTU)*

Test command

Reset process command

Delay acquisition command

<104> :=
C_TS_NA_1
<105> :=
C_RP_NA_1
<106> :=
C_CD_NA_1

(optional, if GPS is used for time synch. of the RTU)*

Parameter in control direction

(station-specific parameter)

Parameter of measured value, normalized value

Parameter of measured value, scaled value

Parameter of measured value, short floating point value

Parameter activation

<110> :=
P_ME_NA_1
<111> :=
P_ME_NB_1
<112> :=
P_ME_NC_1
<113> :=
P_AC_NA_1

File transfer (may not be required)*

(station-specific parameter)

File ready

Section ready

Call directory, select file, call file, call section

Last section, last segment

Ack file, ack section

Segment

Directory

<120> :=
F_FR_NA_1
<121> :=
F_SR_NA_1
<122> :=
F_SC_NA_1
<123> :=
F_LS_NA_1
<124> :=
F_AF_NA_1
<125> :=
F_SG_NA_1
<126> :=
F_DR_TA_1
Special use
(private range)

<137> :=
C_RC_NB_1

Regulating delay command

(for Raise/Lower command of OLTC .May not be required)*

BASIC APPLICATION FUNCTIONS

Station initialization
(station-specific parameter)

Remote initialization

General interrogation
(system or station-specific parameter)

Global
Group 1
Group 2
Group 3
Group 4
Group 5
Group 6

Group 7
Group 8
Group 9
Group 10

Group 13
Group 14
Group 15
Group 16

Group 11
Group 12

Addresses per group have to be defined

Clock synchronization
(station-specific parameter)

Clock synchronization (optional, if GPS is used for time synch. of the RTU)*

Command transmission (Required only when control command is envisaged)*

(object-specific parameter)

Direct command transmission

Direct set point command transmission

command

Select and execute command

Select and execute set point
C_SE ACTTERM used

No additional definition
Short pulse duration (duration determined by a system parameter in the outstation)
Long pulse duration (duration determined by a system parameter in the outstation)
Persistent output

Transmission of integrated totals

(station or object-specific parameter)

Counter request

General request counter

Counter freeze without reset

Counter freeze with reset
Counter reset

Request counter group 1

Request counter group 2
Request counter group 3
Request counter group 4

Addresses per group have to be defined

Parameter loading
(object-specific parameter)

Threshold value
Smoothing factor
Low limit for transmission of measured value
High limit for transmission of measured value

Parameter activation
(object-specific parameter)

Act/deact of persistent cyclic or periodic transmission of the addressed object

Additional Information on IEC 60870-5-101 for NRLDC

7.0 Telemetred Data and ASDU mapping
The following table explains the type of the telemetered data and corresponding ASDUs used to transmit
this data as per IEC 60870-5-101 protocol. These are same for all the above three RLDCs.
Type of Data
Analog inputs (P,Q, V,
f, OLTC tap position)
Digital inputs Single
status (Isolators,
Protection signals)
A single status object uses
the same IOA address when
being sent as ASDU-1 or
ASDU-2 or as a file transfer

Digital inputs Double

status (Circuit
breakers)

Data Unit
type as per
IEC
ASDU-11
ASDU-1

ASDU- 2
ASDU-3

Description as
per IEC

Data polling
method

Measured value
scaled value
Single point
information

As cyclic data on
Class 2 polls
By exception
(spontaneous)
and on periodic
Group scan
By exception
(spontaneous)

Single point
information with
time tag
Double point
information

A double status object uses

the same IOA address when
being sent as ASDU-3 or
ASDU-4 or as a file transfer

ASDU-4

Double point
information with
time tag

Pulse accumulators

ASDU-15

Integrated totals

Interroga
tion
group

Transmitted
after Class-X
request
Class 2

Info Obj.
Address
range
8448-

Group-1

Class 1 on
exception,
Class 1 after
Group 1 scan
Class 1 on
exception

376-

Class 1 on
exception,
Class 1 after
Group 1 scan
Class 1 on
exception

256-

Class 2

12544-

By exception
(spontaneous)
and on periodic
Group scan
By exception
(spontaneous)

Group-1

By periodic
counter
interrogation

Group-1
(counter
interrogati
on)

376-

256-

Analog Outputs
(Setpoint)

ASDU-48

Digital Control
command (CB
Trip/Close)

ASDU 46

Set point
command
Normalized
value
Double
command

B. Data polling method

3.

4.
5.
6.
7.

The RTU shall respond to the Master stations request for the at least the following commands as
per the protocol:
- Status of Link
- Reset of Link
- Delay acquisition command *
- Clock synchronization command *
- General interrogation command
- Interrogation of Scan group 1 command (all status data)
- Interrogation of Scan group 2 command (all analog data)
- Class 1/2 data polling
If supervisory control commands are envisaged, then SBO procedure is to be used.
RTU shall send all Analog and status data in response to the General interrogation command.
All digital inputs are to be assigned to Scan group-1.
Analogs are defined as periodic data and are sent to RLDC on Class 2 request. The periodicity
varies from 10 seconds to 15 seconds depending upon the quantity of data and available
bandwidth.
Digital input state changes are to be reported spontaneously by RTU as Class 1 data. The Digital
input data have higher priority than Analog values. An integrity scan is performed for all the
digital inputs using Scan group-1 at every 10 minutes interval.

* These features may not be required

37120

33024-