2011 Reff2020

Free Standard provided by BIS via BSB Edge Private Limited to Saurabh Mr -
Chennai(saurabh.idse@gmail.com) 117.206.122.192 [for non-commercial use only].

(Reaffirmed 2015)
IS 15953 : 2011
(Reaffirmed 2014)
(Reaffirmed 2017)
Hkkjrh; ekud (Reaffirmed 2020)
(Reaffirmed
ikou ra=k vuqiz;ksxksa ds fy, i;Zosf{kd fu;a=k.k vkSj 2013)
vkadM+k vtZu ¼LdkMk½ iz.kkyh
(Reaffirmed 2012)
Indian Standard
SUPERVISORY CONTROL AND DATA ACQUISITION
(Reaffirmed 2011)
(SCADA) SYSTEM FOR POWER SYSTEM
APPLICATIONS (Reaffirmed 2010)
ICS 33.040.60;33.200 (Reaffirmed 2009)
(Reaffirmed 2008)
(Reaffirmed 2007)
(Reaffirmed 2006)
(Reaffirmed 2005)
© BIS 2011
BUREAU OF INDIAN STANDARDS
MANAK BHAVAN, 9 BAHADUR SHAH ZAFAR MARG
NEW DELHI 110002
October 2011 Price Group 11

Power System Control and Associated Communications Sectional Committee, LITD 10
FOREWORD
This Indian Standard was adopted by the Bureau of Indian Standards, after the draft finalized by the Power
System Control and Associated Communications Sectional Committee had been approved by the Electronics and
Information Technology Division Council.
The Committee responsible for the formulation of this standard has reviewed the provisions of the following
International publications and has decided that these may be used in conjunction with this standard till Indian
Standards on these subjects are published:
IEC 60068 series Environmental testing
IEC 60870-2-1 : 1995 Telecontrol equipment and systems — Part 2: Operating conditions — Section 1:
Power supply and electromagnetic compatibility
IEC 60870-5-101 : 2003 Telecontrol equipment and systems — Part 5-101: Transmission protocols —
Companion standard for basic telecontrol tasks
IEC 60870-5-104 : 2006 Telecontrol equipment and systems — Part 5-104: Transmission protocols —
Network access for IEC 60870-5-101 using standard transport profiles
IEC 61131-3 : 2003 Programmable controllers — Part 3: Programming languages
IEC 61850 Communication networks and systems in substations
IEEE Green book standard 142 : 1991 IEEE Recommended practices for grounding of industrial and
commercial power systems
The composition of the Committee responsible for the formulation of this standard is given in Annex D.
For the purpose of deciding whether a particular requirement of this standard is complied with, the final value,
observed or calculated, expressing the result of a test or analysis, shall be rounded off in accordance with IS 2 : 1960
‘Rules for rounding off numerical values (revised)’. The number of significant places retained in the rounded off
value should be the same as that of the specified value in this standard.
IS 15953 : 2011
Indian Standard
SUPERVISORY CONTROL AND DATA ACQUISITION
(SCADA) SYSTEM FOR POWER SYSTEM
APPLICATIONS
1 SCOPE in IS 12746 (Part 1/Sec 3), IS 1885 (Part 50) and
IS 1885 (Part 52/All sections) shall apply.
The SCADA system specifies facilities for monitoring
and control functions of distributed process from a 4 FUNCTIONAL CHARACTERISTICS
central location. The SCADA system described here
are meant for operation of the transmission and A SCADA system comprises of a controlling system
distribution power system network. This standard referred to as control centre and a controlled system
provides definition and guidelines for the specification, referred to as RCCI. A SCADA system ranges in size
performance analysis and application of supervisory and complexity from a single control centre with a non-
control and data acquisition (SCADA) systems for use redundant work station to a hierarchical control centre
in electrical utilities. These can also be used for remote setup with redundant multiple servers. The control
operation of a sub-station. centres are sometimes duplicated with a backup control
centre for critical systems. The controlled system may
The SCADA systems typically use computer systems comprise of a single RCCI or hundreds of RCCIs
consisting of servers, workstations and front end distributed over a wide geographical area, just like the
processors at a central location, referred as the control power system network, communicating over a diverse
centre and a data acquisition and supervisory control set of communication mediums. Also, the SCADA
device or a group of devices, generally referred as system governed by this standard may perform some
remote communication and control interface (RCCI), or all of the functions identified in this standard.
located in the sub-stations/power stations. In this
standard the term RCCI denotes any data acquisition The term Control Centre and Master station have been
and supervisory control device, for example intelligent used interchangeably in this standard depending upon
electronic devices, programmable logic controller, bay the context. However, in a modern day control centre,
control modules, remote terminal unit, etc, that directly the term Master station refers to an entity which
communicate to a remote control centre. The present generally does the communication with the field
day sub-stations are adopting new technologies like devices (like RCCIs) using a communication protocol.
sub-station automation systems which perform the data Similarly the term RCCI has been used to refer to all
acquisition and supervisory control functions similar intelligent devices which are installed in the filed sites
to a RCCI but in more detail. The sub-station for the purpose of data acquisition from the process.
automation systems generally have gateways for Figure 1 Illustrates the possible types of data and
communicating with the computer systems at the control flow between a master station and a RCCI.
control centres. This standard does not cover the
requirements of sub-station automation systems. 4.1 Typical Equipment Functional Diagrams
SCADA system is deployed as an integrated component The typical equipments in a control centre and a RCCI
of energy management systems/distribution are illustrated using functional diagrams.
management systems in present day control centres.
4.1.1 Control Centre Functional Components
This standard does not cover the details/functioning
of the advanced applications (like EMS/DMS) and only The functional components of a control centre are
a reference is given. illustrated in Fig. 2. A redundant system with dual
server in hot standby configuration is illustrated in
2 REFERENCES Fig. 2; however, a single server configuration may be
The standards listed in Annex A are necessary adjuncts adequate for some non-critical applications.
to this standard. A user needs to specify the requirement of redundancy
in the functional components depending upon
3 TERMINOLOGY
complexity and criticality of his application. In some
For the purpose of this standard the definitions given cases it may be required to have a backup control
1
IS 15953 : 2011
Supervisory Control:
a) Trip/Close
C
b) Raise/Lower
c) Open/Close O
d) Stop/Start M
Computer servers e) Set point values M RCCI
and work stations Parameter Download: U
a) Control Programs1) Co N
Communication Interface
Interface
b) Instructions m I See Fig. 4 for
download1) mu
C details
c) Database changes nic
ati A
download1)
See Fig. 2 for d) Alarm parameters on T
details download1) I
Communication
Int O
erf N
Standard Time Signal ace
S
Analog Data Y
Accumulator Data S
Digital Data T
a) Status E
b) Alarm M
c) Sequence of Events
Serial data (pass through)
Master Station Communication Field Site(s)

(Control Centre) System
1)
Optional feature
FIG. 1 M ASTER STATION AND RCCI FUNCTIONAL DATA/C ONTROL FLOW
FW/IDS Intranet/
Internet
1)
Video
Primary 1) 1) 2) 1) 2) 1) 2) Time
Wall Backup
Server Synch.
Server in History Appli- WEB 1)
Server -cation Server facility Remote
Hot
(GPS) Workstations
Standby Server
FW/IDS
Local Area Network

Router 1)2)
1)2) User Interface

Comm. Controller
Communication
Printer Work Stations
Interface
1)
Comm. Interfaces Local
RCCIs 1)
RCCIs IEDs
1)
Optional feature
2)
Can be redundant
FIG. 2 CONTROL CENTRE FUNCTIONAL BLOCK DIAGRAM
2
IS 15953 : 2011
centre, at a distant geographic location to cater to server and peripheral devices like local area network
emergency situations leading to loss of primary control switches, routers, printers, time reference such as a GPS
centre due to natural calamities, fire, flood, etc. (global positioning satellite) based time synchroni-
zation equipment, external storage devices, etc. The
A backup control centre (BUCC) adds to reliability
GPS is used as a standard time reference for keeping
and may be considered whenever there is credible threat
the time of the control centre computer systems and
to control centre from accident, natural disaster, or
the RCCIs synchronized.
attack (physical or cyber) or wherever underlying
system are unmanned or are critically required to be The control centre may act as a source of real-time
operational continuously (24 × 7 × 52). The minimum and historical information about the power system and
requirement for a backup control centre shall include a utility may require this data to be made available to
data acquisition from underlying RCCIs/control other users within the organization and to outside
centre(s) as well as peer control centres. The agencies like energy traders, customers, regulatory
communication lines/equipment shall not be dependent commissions, government agencies, etc. It is preferable
upon existence of the main control centre. The backup to have a separate WEB enabled system to address these
control centre shall have a communication link of needs so that the realtime information about the power
adequate capacity to main control centre for carrying system can be viewed using simple web browsers on
data as per the specified requirement. This normally intranet or internet. The WEB enabled system shall also
includes data exchange like telemetred data, operator have adequate information security measures like
entered data, schedules data, historical data, reports, firewalls, intrusion detection system/intrusion
source code, database model data, display files, system prevention system, encrypted communication, etc, in
monitoring and health check data, etc, between main addition to normal security measures like user
and backup control centre whose volume depends upon authentication and authorization.
the design of the SCADA system and the operating
A utility may also need the ability to operate the power
philosophy of the utility. The operation philosophy for
system from sites other than the control centre. Use of
backup control centre may be of hot standby, cold
remote operator workstation is preferable in this case.
standby or independent modes of operations.
Sometimes a hierarchical set-up of control centres may
Regardless of the level of sophistication of the BUCC,
be required, to match the organizational needs of a
the most important considerations when implementing
utility/power system. The organization of control
a BUCC is the availability of both voice and data
centres in multiple hierarchical levels like area load
communication facilities and the time to make it
dispatch centres, state load dispatch centres, regional
operational in case of failure of main control centre.
load dispatch centres and a National Load Dispatch
The user shall specify the requirement of remotely
centre is one such example. The control centres in a
monitoring and maintaining the backup control centre,
hierarchical set-up typically exchange real-time data
if desired.
and other information among them. Use of the inter
The control centre may have different application control centre communication protocol (ICCP) can be
servers like SCADA servers, EMS servers, front end specified in all such cases to ensure interoperability. A
processor, ICCP servers, historical data server, web hierarchical set-up of control centres is shown Fig. 3.
National Control Centre
RCCIs
RCCIs
Regional Control Centre Regional Control Centre
State level Control Centre State level Control Centre State level Control Centre
RCCIs RCCIs
Area level Control Centre Area level Control Centre
RCCIs RCCIs RCCIs RCCIs
FIG. 3 HIERARCHICAL S ET-UP OF C ONTROL CENTRES

3
IS 15953 : 2011
4.1.2 RCCI Functional Components the application for which the SCADA system is used,
the quantum and frequency of data to be exchanged,
The functional components of an RCCI are given in
geographical spread of the control system and
Fig. 4. Various interconnections of master station(s)
economy. In power utilities dedicated communication
and RCCI(s) are illustrated in Annex B.
links are preferred as the availability of communication
4.2 SCADA System Functional Characteristics link determines the reliability of the SCADA system.
However, if only acquisition of data is envisaged at
This clause provides guidance for both users and long intervals (like an hour) and no real time control
suppliers to jointly define the functional capabilities operation is to be performed in that case a dial-up line
that may be required in a SCADA system. can also be used.
Each generic function is described in terms of the The communication protocols typically used requires
minimum features or characteristics that shall be a master station to initiate a message transaction. In
addressed to adequately define the function. some cases the RCCI can initiate a communication
When the feature or characteristic is fixed by the design message. The requirements of the communication
of the equipment, the burden of definition rests on the protocol for communicating between the master
supplier (for example number of inputs/outputs per station(s) and the RCCI(s) shall be defined and a
card). However, variable features (for example, range standard communication protocol shall be utilised.
of inputs, scaling resistors, switch settings, and A control centre (master station) shall implement all
software) shall be defined by the user. the features of the standard communication protocol
4.2.1 Communication Capabilities with RCCI such that minimum integration effort is required for
integrating a RCCI in future. The communication
The communication links between a master station(s) protocol attributes to be specified may include,
and RCCI(s) and between a sub-master RCCI and its
slave RCCIs, can be on any suitable communication a) Protocols to be supported;
media like a twisted pair copper cable, PLCC, radio, b) Protocol messages to be supported;
fibre optic, VSAT, leased line, dial-up, GSM or CDMA, c) Protocol applications services to be
etc. The choice of communication media depends upon supported;
Master Station Links Local User Interface1)
Slave RCCIs/ 2)
Power
IEDs Control Supply
processing module
2)
Self 1)
Communication Database GPS
Data Diagnostics
Interface maintenance module
Processing
tool
Analog Input Digital Input Analog Output Digital Output Serial

Modules Modules Modules Modules Interface
Module
Transducer Pulse Contact Controllers Contact to IEDs

inputs, PTs, CTs Inputs from Relays/Switches/
switching Control devices,
devices, etc.
etc
1)
Optional feature.
2)
Can be redundant.
FIG. 4 REMOTE CONTROL AND COMMUNICATION FUNCTIONAL BLOCK DIAGRAM
4
IS 15953 : 2011
d) Report-by-exception polling; 4.2.2.1 RCCI data acquisition

e) Channel monitoring (main and backup); The capacity (total number of input points) and rate of
f) Communication error reporting, failure acquisition (inputs per second/millisecond) for field
criteria, and recovery; data interfaced to the RCCI equipment shall be defined
g) Automatic channel switching between main for all applicable data types.
and backup channels;
The analog inputs to the RCCI are generally through
h) Channel diagnostic/test provisions; transducers (see IS 14570) and in some cases directly
j) Type of communication equipment interfaces; through CT/PT connections. The inputs from a
k) Type of communication channels/media; transducer can be scanned every 1 sec and from CT/PT
m) Number of masters to which a RCCI is inputs can be sampled at least half the frequency of
required to report; and the a.c. supply that is 25 Hz. The following shall be
n) Number of RCCIs per channel and/or specified for analog input characteristics of the RCCI:
channels per RCCI. a) Ranges of analog input signal (in mA, mV,
4.2.2 Data Acquisition V, A);
b) Analogue to digital converter resolution of
Data acquisition is the process of collection of data by 16 bits (see IS 14570);
the RCCI from the field and by the master station from
c) Accuracy of measurement for transducers/
the RCCI. The type of data to be acquired, its
RCCI card;
periodicity, the update requirements and ultimate point
counts need to be specified by the user. Systems with d) Input overload protection;
report-by-exception functions shall have the capability e) Input impedance/output impedance;
to report all data for initialization and periodic integrity f) Temperature coefficient of accuracy; and
checks. g) Residual current.
As a general rule, not all the data available in a When multiple parameters of a feeder are required then
sub-station may be required by the RCCI/SCADA a multi-function transducer can be used.
system. The data required by SCADA system shall be
governed by a data acquisition principle of the user, The status input to the RCCI is measured by discrete
which shall identify the minimum data which is states of the signal such as the presence or absence of
required for monitoring of the substation for the desired a voltage, current, or a contact in the open or closed
applications at the control centre. position. The status inputs are generally scanned every
1 millisecond by the RCCI. The following shall be
The process data in an electrical utility can be mainly specified for input characteristics of the RCCI:
categorized into the following types:
a) Wet or dry contact status inputs;
a) Analog inputs — Continuously varying b) Sensing voltage for contact wetting;
parameters like voltage, current, power, power
c) Current limiting;
factor, transformer tap position indication,
temperature. d) Isolation between sensing voltage and power
supply;
b) Digital inputs — Switchgear (Isolator/
breaker/earth switch) status, alarm status, SOE e) Optical isolation;
inputs, relay indications. f) Debounce filtering (in 4 to 25 millisecond
c) Pulse accumulator value — Energy values, range);
rainfall. g) Buffer for storage of status inputs for short
d) Digital outputs — Control of switchgear, communication problems;
raise/lower control of tap position of h) Double status input or single status input for
transformers, reset of relays. monitoring;
e) Analog outputs — Set point controls for j) Time stamping with accuracy of
generators, HVDC controller. 1 millisecond; and
k) Time stamping resolution of 1 millisecond.
The characteristics for each type of data shall be defined
individually. These shall include ranges of data input, The RCCI may also acquire data from slave RCCIs or
scale factors, acquisition rates, and data update IEDs using a communication protocol like MODBUS.
requirements as applicable. The RCCI in such a case acts as a sub-master. If
5
IS 15953 : 2011
required, these features shall also be specified. The sources such as another control centre through a
master station functions allocated to such sub-master communication protocol like ICCP. This protocol is
RCCI shall be defined using the applicable preceding used for data exchange between different control
sub-clauses. This is the responsibility of both the user centres in a hierarchical setup or between control
and supplier. The user shall define the applicable centers of two different utilities.
characteristics as follows:
4.2.3 Other Communications between SCADA and
a) Data acquisition methodology; RCCI
b) Communication protocol; In addition to acquisition of data from the RCCI, the
c) Number of points; SCADA system shall also be capable of exchanging
d) Scan interval; the following information.
e) Downloading characteristics; and 4.2.3.1 RCCI database download
f) Data pass through/processed in the sub-master
RCCI. Typical utility scenario involves changes in the
electrical network such as addition/deletion of devices,
The RCCI shall be capable of sending data to the changes in the CT/PT ratios. The RCCI database
SCADA system either periodically through a scan configuration needs to be modified to match these
group or through report by exception mechanism as changes. The RCCI shall support download of its
per the desired communication protocol to the control database configuration files from the control centre
centre. The RCCI shall be capable of sending data preferably in the framework of the communication
spontaneously (balanced communication) which protocol being used. This will facilitate the changing
reduces data traffic on the communication channel of settings and downloading a new database in the
however when multiple RCCIs are connected to a RCCI remotely from the control centre location without
master station on the same communication channel the making a visit to the remote site. Necessary tools
unbalanced mode is used. required to generate the RCCI database configuration
4.2.2.2 Control centre (master station) data acquisition files are often installed on a standalone system.
The data acquisition capability for SCADA system 4.2.3.2 RCCI test mode
shall be defined in terms of the following The SCADA system shall support a ‘test mode’ which
characteristics: allows the RCCI interface/database to be tested/
a) Type of data to be acquired; calibrated remotely from the control centre. In this
b) Scan groups — A scan group is a set of data mode, the data acquired from the RCCI is not to be
which is grouped together for the purpose of used by the SCADA system but is directed to a test
acquisition from the master station. Number display. The test display shows the actual values being
of scan groups, size of each scan group and received from the RCCI in the test mode. The real-
the points in each scan group are to be defined; time database of the SCADA system retains the
previous value from the points collected via the RCCI
c) Scan cycle — Number of scan cycles (A scan
before it was placed in the test mode.
cycle is the time to complete the acquisition
of a scan group from a RCCI). The scan cycle 4.2.3.3 RCCI time synchronization
may vary from 1 s to 1 h;
Each RCCI shall have a real-time clock which will be
d) Capability to acquire data by periodic polling
used by the RCCI for time stamping of sequence of
and by exception polling shall be defined;
events. The stability of this clock shall be specified
e) Capability for executing demand scan of the based on the accuracy requirement of the SOE and the
RCCI that is polling the RCCI on events such time synchronization method used. The RCCI clock
as supervisory control, RCCI initialization shall be synchronized either from the master station
and on user demand shall be specified; using the communication protocol or from a time
f) The capacity (total number of input points) source like GPS receiver.
and rate of acquisition (inputs per second)
from RCCI for each data type; and The RCCI real-time clock shall be backed-up with a
suitable secondary source of power like a lithium
g) Provision for future expansion and addition
battery so that the real time clock continues to function
of other type of data.
even when RCCI is disconnected from its primary
The data acquisition process in the control centre shall source of power supply in cases where RCCI is not
also be capable of acquiring data from non-RCCI synchronized from local/remote master station/GPS.
6
IS 15953 : 2011
4.2.4 Data Processing c) Data processing-by-exception may be a

function included as an alternative to
Data processing capabilities of the SCADA system and
processing every input on every scan as it
the RCCI shall be defined for each applicable data
reduces the requirement of computing power
types. A processing applicable to all the data types is
without affecting the accuracy of the
the data quality processing in the SCADA system. The
measurements. A dead band (1 percent to
data quality indicates to the user the attributes of the
5 percent) is to be specified which shall be
data such as the accuracy and dependability on the data.
used for determining change. This processing
The following data quality codes are generally
can be done either in the RCCI or in the master
required:
station or in both.
a) Non-updated — Data is not being acquired d) Data filtering may be required to smooth data
from the source and the value being displayed before it is used by other functions. When this
is old. function is included, the equation used shall
b) Manually replaced — Data is manually be defined and the time delay, introduced by
entered by the user. the filtering, specified.
c) Scan inhibit — Data has been inhibited from e) Data limit checking is typically included to
being updated from the source by the user. determine, if the value of an analog point is
d) Alarm inhibit — Alarming process for the data within the safe and operational limits. The
has been inhibited so that alarms will not be number of high or low limits accommodated
indicated to the user. and associated return-to-normal deadband
e) Limit override — Limit on analog value has processing shall be defined. Specific attention
been overridden with new limit values. shall be given to the procedure for revision of
limits and deadband values by the user. The
f) Unreasonable — The value reported by the
user may specify the requirement of different
RCCI is not within the defined range.
Alarm limit sets for the different seasons like
g) Questionable — The value is questionable summer limits and winter limits. The method
because of factors like A/D drift or fault. of invoking a alarm limit set shall also be
4.2.4.1 Analog data specified.
f) Sign conversion — Convert the sign of the
The analog data processing capabilities to be supported
analog values as per convention.
at both the SCADA system and the RCCI shall be
defined. Particular attention shall be given to input data The following analog data processing is
validity processing (for example the validity of the generally done in RCCIs:
data) and to the interface between the supervisory
1) Detect an open input to an analog
control function and the analog data processing
channel;
function.
2) Identify unreasonable values (out of
The following analog data processing is generally done range inputs);
in a SCADA system: 3) Detect a drifted or faulty A/D converter
a) Reasonability processing check shall be made RCCI card (Applicable only when the
to see that the data being received from the RCCI does not have auto correction
RCCI falls within a range of values feature for A/D converter); and
(reasonability limits). The reasonability check 4) Validity of time stamp.
takes care of wrong CT/PT ratio in database Further the conversion of analogue data to engineering
and malfunction of transducers. Further units [see (b)] may also be specified as part of RCCI
processing of the data takes place only when capability.
the value is considered to be reasonable.
4.2.4.2 Status data
b) Data conversion to engineering units is
typically required before analog data is used Status data is used to describe a physical quantity (for
by other software, printed or displayed as example switchgear position) that has various possible
output. The mathematical equation(s) used to combinations of discrete states. The status data
convert analog values represented by raw processing options to be supported at the SCADA
counts into the corresponding engineering system and the RCCI shall be defined by the user.
units shall be user definable. Specific attention
The status data processing generally done in RCCI
shall be given to sensor and transducer scale
includes time stamping to required resolution,
factors that may be provided by the user.
7
IS 15953 : 2011
capturing multiple changes of an input for onward a) Location (RCCI or control centre or both);
transmission, value inversion, chatter filtering, change b) Mathematical/logical/statistical functions
detection (including comparing complimentary points required;
with adequate delay to suppress reporting of c) Resulting data types (numeric or logical, or
intermediate position), data report by exception.
both);
The status data processing generally done in control d) Data quality inheritance;
centre includes, e) Number of arguments in a calculation;
a) conversion to engineering values; f) Type of data to be used in calculation; and
b) inversion; g) Calculations required on realtime data and on
c) detection of abnormal state definition; historical data.
d) multiple state change detection — open, 4.2.4.6 Alarm data
closed, transit; and
e) change detection and alarm processing. Alarms are conditions in the process or in the SCADA
system that require user notification when detected.
4.2.4.3 Accumulator data The following characteristics shall be defined when
The following characteristics shall be defined when the capability to process and report alarm conditions
pulse accumulation and/or accumulator data processing is included:
is included:
a) Conditions reported as alarms;
a) Input circuit (two or three terminal and how b) Methods of acknowledgment (single or
input circuit operates); selection or groups);
b) Sources of freeze command, if any (internal/ c) Methods of highlighting alarms (for example
external); flash, audible tone, etc);
c) Reset command (if any); d) Information in alarm messages (time, event/
d) Ranges of values (RCCI and master station); device identification, Operation/action);
e) Nominal and maximum counting rates; e) Priority of alarms (up to 8);
f) Source of memory power; and f) Size of alarm queue(s);
g) Input voltage if externally powered. g) Queue management (for example time
4.2.4.4 Sequence-of-events (SOE) data ordered);
h) Destination of alarms — alarm summary
Sequence of events (SOE) data are RCCI events with
displays, loggers, history database;
time stamps. It shall be possible to define any or all
the digital inputs of the RCCI as SOE data. j) Alarm inhibit feature;
k) Advanced alarm management functions for
The following characteristics shall be defined when intelligent processing of alarms; and
SOE data acquisition capability is included:
m) Alarm sorting/analysis/organization.
a) Time resolution of time stamping at RCCI;
4.2.4.7 Topology processing
b) Time accuracy between any two RCCI;
c) Number of SOE inputs per RCCI; The SCADA system topology processing function,
d) Size of buffers (number of SOE events that shall be capable of analyzing the open/close status of
can be stored) per RCCI per master; switching devices in order to identify the energized/
e) Time (minimum/maximum) between de-energized condition of a power system equipment.
successive change(s) of an input; and This information about the state of the power system
devices is visualized by a operator on a single line
f) Method of indicating that SOE data is
diagram or a network diagram. The visualization shall
available at the RCCI.
be capable of colouring topology to indicate voltage
4.2.4.5 Calculated data level and/or identify the source of feed.
Calculated data is derived after performing 4.2.5 Supervisory Control Characteristics
computations on data acquired from the RCCIs and
other sources. Generally, the calculations are performed Supervisory control enables controlling of devices from
in the SCADA system but may be required at the RCCI remote. The devices to be controlled include
also. The following characteristics shall be defined switchgear, transformer tap position, capacitor bank
when the capability of computing data (which are not switching, AGC of generators etc. The characteristics
directly measured) is included: of such a control capability shall be defined definition
8
IS 15953 : 2011
of characteristics common to all control interfaces shall capacitors based on reactive power compensation
include following: requirements. When the capability to automatically
control external devices is required, the characteristics
a) Type of control command (Digital/analog,
of such control capabilities shall be defined as follows:
momentary, persistent, variable pulse);
b) Operator actions (Select once-operate once/ a) Location of automatic control logic (RCCI or
Select once-operate many) and system control centre);
response; b) Control equation(s);
c) Control sequence (Direct or select check c) Feedback value and accuracy, if closed loop;
before operate); d) Frequency of execution;
d) Security of control sequences operation e) User alterable control parameters;
(Checks for tagging/RCCI telemetry failure/ f) Associated logging or alarming;
user defined software interlocks);
g) Method of altering control logic; and
e) Control command feedback;
h) Use of standardized programming language.
f) Group control (One command to control
multiple devices); 4.2.6 Use Interface Characteristics
g) Sequential switching plans; and User interface is the application through which a user
h) Control possibility by other applications. interacts with the SCADA system at the control centre
and with the RCCI. The design and implementation of
4.2.5.1 Equipment control with relay interface
user interface shall be intuitive and user friendly. The
Control using a relay output shall be defined as follows: user interface shall support full graphics user interface
features and utilize a windows based environment. The
a) Dwell time of relay contacts;
user shall be able to perform all the activities by
b) Number of relays that can be simultaneously invoking simple menus and shall not be required to
energized in each type of RCCI processing type commands. Short cut keys shall be definable so
actions (for example logging and alarm that advanced users can navigate quickly. User interface
suppression); and shall be uniform and have common look and feel for
c) Relay contact ratings (voltage/current/ac or the various applications in the SCADA system and for
dc). performing different activities like operation,
programming and development, etc.
4.2.5.2 Equipment control with set point interface
The RCCIs generally does not require a elaborate user
Control using a set point output shall be defined as
interface. However most modern RCCIs are provided
follows:
with a simple text based user interface. Some RCCIs
a) Resolution of set point value; have inbuilt web server, which allows a user to interact
b) Duration of output value; with the RCCI using a web-browser. The requirement
c) Processing actions (for example limit check, of a web-based user interface for the RCCI shall be
equation, and alarms); and specified by the user, if required. The RCCI can also
be connected to a logger for printing of sequence of
d) Electrical interface.
events/alarms. The RCCI can optionally have a GUI
4.2.5.3 Equipment/process control with IEDs display, for example LCD for displaying information
and allowing user interaction. RCCIs shall have
Control using an electronic interface shall be defined
indication, for example LEDs to report the status of
as follows:
the input-output (I/O) cards and each of its channels.
a) Timing diagram of signals, The indication for individual channels of an analog
b) Interface communication protocol, input card is generally not provided by all the vendors.
c) Processing actions associated with control, and The user interface functions characteristics shall be
d) Physical interface. defined according to the following sections.
4.2.5.4 Automatic control functions 4.2.6.1 Types of user
Automatic control functions can be used for executing There are different activities like operation,
controls based on certain system conditions. Some of management, maintenance, development, study etc, to
the applications where this can be utilised is load shed be performed by different users of SCADA system.
based on frequency, transformer tap position change The SCADA system shall have a provision for having
for controlling voltage profile, taking in service of different user modes to support the working
9
IS 15953 : 2011
environment required for the different activities. The a) Number of display windows;
following user modes may be specified: b) Number of saved layout of displays/windows
a) Dispatcher/Operator — Users who use the for each user login wise;
SCADA system for operation of the power c) Number of layers;
system. d) Number of declutter levels;
b) Supervisor — Users responsible for e) Support for overlays, pan, zoom;
operations management of the SCADA f) Number of steps in pan/zoom;
system. g) Data presentation in different type of displays;
c) Engineer — Users responsible for operations and
support and maintenance activities who have h) Display requests mechanism-selection from
access to certain SCADA/EMS/DMS system menu, cursor target selection, alarm/event
functions. selection, entry of display name or number in
d) Programmer — Persons responsible for a display selection field, forward and reverse
continuing development and maintenance of paging through series of display, zooming
the SCADA/EMS/DMS systems. from an overview display to an area of interest
4.2.6.2 Function and data access security within the display.
A mechanism for defining and controlling user access 4.2.6.4 Display design
to the SCADA system at each console shall be The SCADA system comprises of many displays of
provided. Password security shall at least be provided which the displays which represent the power system
for access to the system, its operating system, its layered (Single line diagram and the network diagram) are to
products and other applications. be customized as per the requirements of the user.
Also access to the SCADA/EMS functions, displays, The standard meanings for colours (for example
reports and database elements shall be restricted by monitor displays, status lights) used at the UI to
pre-assigned operating jurisdictions. These operating highlight the condition of device monitored and
area assignments are made when the function, display, controlled through control and data acquisition
report, or database element is being defined. equipment shall be defined by users. The significance
An operator console shall be assigned one or more of colours shall be consistent throughout the system.
operating jurisdictions and each time a user attempts a The following may be specified for the power system
console action such as calling a display, entering a displays:
display data, executing a supervisory control action,
managing an alarm, etc, the console’s assigned a) Colours for equipments at various voltage
operating jurisdiction is to be compared against the levels;
operating jurisdictions assigned to the function, display, b) Symbol to be used for denoting various
report, or database element. devices. A set of graphic symbols shall be part
of the system. The capability to create
In a control centre with multiple servers, the user additional graphic symbol and graphics by the
authentication and authorization shall be performed user is to be provided;
such that a user of the SCADA system is required to
c) Device highlighting in case of alarmed/
enter his credentials only once. The user shall then be
abnormal state;
allowed to have access to the SCADA system resource
on any of the server seamlessly. d) Presentation format of measurement (Unit,
decimal places, directional arrow, colour);
User authentication and authorization shall be specified e) Presentation of alarm (priority identification,
for the management of all the peripheral devices also. colour, acknowledgement);
The RCCI local user interface shall also have a user f) Information required in each layer of a
authentication and authorization check for executing display;
a supervisory control, reading the status of RCCI g) Organization of display; and
inputs, modification of database, etc. h) Information available on each display.
4.2.6.3 Graphical user interface features 4.2.6.5 Type of displays
The following features of the GUI required shall be The types of displays required in the SCADA system
specified by the user: are to be specified. The content and organization of
10
IS 15953 : 2011
the display shall conform to the users operation 4.2.6.6.1 Interactive dialogue
philosophy. The following are the type of displays that
exist in the power utility system environment: The activity at the UI during interaction with the
SCADA system shall be clearly described and shall be
a) Power system displays: consistent throughout the system.
1) Single line diagram;
The selection of a point for a user control action shall
2) Network display;
result in a visual feedback at the user interface. This
3) Station tabular display; and positive feedback to the user shall signify that the
4) Equipment/Transmission line display. SCADA system is ready to accept a control action. The
b) Computer system displays: results of the control action shall be displayed only
after the actual change has taken place. The following
1) System configuration display; and
control actions may be specified:
2) System performance monitoring display.
a) Control output options:
c) Communication display:
1) Enable/Disable;
1) RCCI communication display;
2) Tagging (types and uses);
2) Control centre communication display;
3) Local/Remote; and
3) Communication equipment display; and
4) Open (off)/close (on).
4) Communication network monitoring
display. b) Control of data acquisition:
d) User interface displays: 1) Enable/Disable scan (inputs or stations);
1) Navigation displays; 2) Enable/Disable processing;
2) Directory display; 3) Manual entry of data;
3) Alarm displays; 4) Change scan frequency by group;
4) Event displays; 5) Assign/Reassign data to a group; and
5) Exception displays; 6) User defined interlocks.
6) Summary displays — Alarm/Event/ c) Control of data processing:
Manual override/Off-normal/Out-of
1) Setting date and time;
scan/Alarm inhibit/Tag/Trending/
Operator notes; 2) Setting input change limits;
7) Reports and forms display; and 3) Defining formats;
8) Help displays. 4) Defining conversion data;
5) Defining operator override values; and
4.2.6.6 User interaction procedure
6) Defining normal/abnormal status/data
The sequential procedure for common user interactions quality status.
with the system shall be defined for each of the actions,
such as the capabilities provided for operator inputs at d) Control of alarm processing:
the user interface. 1) Enable/Disable individual alarms;
The user interaction capabilities may include a 2) Enter/Edit alarm limit value(s);
combination of the following: 3) Enter/Edit alarm deadband value(s);
4) Enter/Edit return-to-normal criteria;
a) Keys and switches (alphanumeric or function,
or both); 5) Enter/Edit alarm assignment to area of
responsibility;
b) Cursor (mouse, trackball, joy stick, or key
controlled); 6) Enter/Edit alarm priority;
c) Light pen; 7) Acknowledge alarms (individual/page);
d) Poke points (defined monitor displayed 8) Silence audible alarm;
control selection fields); and 9) Inhibit alarms; and
e) Pull down or pop up menus. 10) Override invalid alarms.
The user’s input to the UI equipment shall be e) Control of function checks:
recognized and acknowledged (valid or invalid) to the 1) Enable/Disable; and
operator within 0.5 s and confirm control actions 2) Change frequency.
within 2 s.
11
IS 15953 : 2011
f) Control of automatic control functions: various types of printers used in the control centre.
1) Enable/Disable; Logger is a dot matrix printer which prints alarms (if
2) Modify criteria; configured) as and when they occur in the system.
Colour or black and white post script printers are used
3) Add/Delete control functions; and
for printing of displays and reports. The applicable
4) Reset to reference level or position. characteristics shall be defined as follows:
4.2.6.7 Alarms a) Display printing options:
When alarm conditions are detected by the SCADA 1) Full display or the selected display;
system, both an audible (Voice, tone, or bell) and visual 2) Colour or black and white background;
(Flashing light or symbol) annunciation shall be 3) Paper orientation;
presented to the user. It shall be possible to silence the
4) Identification of the operator console,
audible alarm without affecting the visual annunciation.
user and time of printing; and
The visual indication of each alarm condition shall
remain as long as the alarm condition exists. It shall 5) Application response time for printing.
be possible to designate alarms as part of different b) Generation of log formats:
groups, priorities and categories. 1) On-line/batch capabilities, and
4.2.6.8 Trends 2) Symbols supported; and
Trending is a display of series of values of parameters 3) Spooling capabilities.
on a time axis. The SCADA system shall provide for c) Demand logs:
definition of new collection of trends online. Trends 1) Standard/Customized formats, and
can be either of graphical type or of tabular type. Trends
2) Time for response.
can be obtained from real-time data (including
calculated data) or historical data or both d) Logged activities:
simultaneously. The following attributes of the trend 1) Alarms;
shall be configurable: 2) Standard events (for example, user and
a) Number of trend display; device actions);
b) Number of parameters in a trend display; 3) System events (for example equipment
c) Source of trend data — Historical data or real- failover and communication failure) ; and
time data or both; 4) Output from diagnostic routines.
d) Number of samples of each trended data; e) Device performance:
e) Trend rate (few seconds to minutes); 1) Print speed (characters per second/pages
f) Trend duration (few hours to days); per minute);
g) Number of Y-axis required, direction of scale 2) Print quality (dots per inch); and
(unidirectional or bi-directional), Number of 3) Colour requirements.
scales, zero offset;
f) Device assignments:
h) possibility of storage of the trend data, export
to text format; 1) Initial;
j) Colour and graphical presentation (curve/ 2) Automatic reassignment;
trace/line/bar/pie chart); and 3) Manual reassignment; and
k) Graphical or tabular. 4) Redundancy and failover.
4.2.6.9 Operator notepad 4.2.6.11 Video projection system display
An operator notepad allows a user to leave messages Video projection system (VPS) sometime called video
on a SCADA system display for information of the wall is often used in a control centre to project an
other users. It shall allow entering and editing overview of the power system which provides the
messages. The presence of a message on a display is operators with a summary of the controlled power
indicated by an icon. The message can be called by system. The VPS consists of a controller which is
selecting the icon. connected to the SCADA system LAN and projects
the display on the VPS screen. The VPS loosely
4.2.6.10 Print function integrates with the SCADA system and hence the
Print function shall be specified to allow production requirements are to be clearly defined and tested. The
of hard copy of alarms, displays and reports. There are functional and performance requirements of the
12
IS 15953 : 2011
display are similar to that of an operator workstation historical data archiving and retrieval is included as
console. follows:
4.2.6.12 Digital displays a) Type of data to be stored;
Digital displays are used for projecting parameters like b) Volume of data (number of parameters);
system time, day, frequency etc. which are prominently c) Data sampling intervals;
displayed in the control centre. If digital displays are d) Number of data sampling intervals;
provided the following needs to be specified: e) Stored data review/modification;
a) Format and numeric range with decimal; f) Online data retention time for different type
b) Update frequency; of data(days/week/month/year);
c) Source of data — SCADA; g) Stored data redundancy (RAID storage);
d) Size of display characters; and h) Method of data archiving/retrieval (Tape/
Optical disk, automatic/manual );
e) Brightness.
j) File maintenance procedure;
4.2.7 Historical Data k) Data usage (for example displays, reports,
It is often felt necessary to store the real-time data applications); and
available in the SCADA system for purpose of analysis m) Type of reports/periodicity of reports/
and report generation. calculations to be performed.
The different types of historical data storage which may 4.2.8 SCADA System Redundancy
be required are:
Redundancy can be specified in both the SCADA
a) continuous recording; system and the RCCI, if high availability of the
b) data storage for report generation; and controlled system is required.
c) alarm/event/log data storage. 4.2.8.1 Redundancy in the RCCI
The requirement of storage of data in RDBMS
The redundancy in the RCCIs is generally limited to
(Relational database management) and its subsequent
the redundancy in communication ports central
retrieval is generally handled by a separate system than
processing unit (CPU) and the power supply. However,
SCADA which requires independent hardware and
if required redundancy in I/O inputs can also be
software.
specified to ensure high availability. The RCCIs
4.2.7.1 Continuous recording (CR) preferably shall have redundancy of communication
ports, power supply and CPU.
The continuous recording of data records all significant
changes in the power system data which can be used 4.2.8.2 Redundancy in the control centre computer
for future analysis. The continuous recording function system
collects and stores all the data (Analog and status
The components (hardware/software) of the SCADA
values) as and when the values received in the real-
system can be duplicated so that even if one of the
time SCADA database varies from its previous value
redundant components fails, the SCADA system shall
by a certain dead-band. The CR data can then be
remain available. In a redundant configuration of
retrieved on the SCADA system displays or exported
servers, one server is in primary mode and other in
to a RDBMS for reporting and viewing purpose.
standby or backup mode. The process of transferring
4.2.7.2 Data storage and report generation the role of a primary server to a backup server is called
failover.
Power system data can be sampled from the real time
database at different periodicities and can be stored in The following characteristics shall be defined when
a RDBMS for the purpose of report generation. redundancy in servers/facilities has been specified:
4.2.7.3 Alarm/Event/Log data storage a) Type of redundancy:
The alarm/event/log data may be stored for 1) N+1 or 1+1 redundancy in hot standby
investigating the occurrences in SCADA system. The mode.
storage shall be such that it is possible to have extensive b) Database backup:
analysis like search and sort on the stored data 1) Data residency (bulk or main memory);
including sorting on basis of time, device, device type, and
priority and event. 2) Frequency of backup (by data type)
The following shall be defined when the capability for ranges from 10 to 30 s.
13
IS 15953 : 2011
c) Database update: b) Expandability — Processors/memory/

1) Data residency (bulk or main memory); Auxiliary memory;
and c) Number of LAN interfaces;
2) Frequency of update (by data type) d) Co-residency of applications — separate
ranges from 10 to 30 s. servers for each function;
d) Failure monitoring: e) Resolution and size of monitors;
1) Method of failure detection (number of f) Type of removal storage/mass storage device;
failed communication attempts, g) LAN equipment shall have suitable number
watchdog etc.); of spare ports (100 percent);
2) Response time for detection — ranges h) RCCI communication equipments shall have
from 4 to 10; and spare (100 percent) interfaces;
3) Effect on a programme or task in progress j) Performance of Printers — Resolution/ppm/
when failover occurs. duty cycle;
e) Failover: k) EMI/EMC compatibility;
1) Method of failover (failover to redundant m) Environmental requirements (Temperature/
server, restart, etc); Humidity/Altitude);
2) Time required for failover (ranges from n) Power supply and earthing requirements;
30 s to 1 min — more in case of database p) Statutory requirements like for environment,
server); if any;
3) User interface response following q) Power supply redundancy in the hardware;
failover (user interface shall always be r) Mounting and erection requirements;
available);
s) Cabling requirements; and
4) User actions following fail over;
t) Noise level.
5) Effect on a programme or task in progress
when failover occurs (terminated, It shall be the objective to purchase hardware which is
resumes, restarts etc); the current industry standards so availability of spares
6) Functions which are required to failover can be guaranteed for a longer duration and also
(non-critical functions may not be support is available from the OEM.
required to failover); and 4.2.10 Third Party Interface
7) Interactions with other components in the
SCADA system. The SCADA system generally stores and processes data
in a proprietary format therefore means shall be
4.2.9 SCADA System Hardware Characteristics available to access data from the SCADA system both
The SCADA system consists of hardware like for the real-time data and historical data. The standard
computers, local area network switches, routers, interfaces like ODBC/ DDE/SQL especially for the
printers, modem, communication card, RCCI, etc. The personal computer applications shall be specified as
present trend in the SCADA industry is that except the this allows data to be imported in an environment to
RCCI, most of the hardware is a commercially available which they are more familiar and allows better
product available from third party manufacturers. utilization of the data. Also, there may be other systems
in the utility which need to exchange data with the
The choice of hardware is generally done by the SCADA system.
SCADA vendors who prefer a particular hardware
manufacturer/model based on the design of their The requirement of programmable API’s (Application
SCADA system. It is advisable to allow the SCADA programming interface) can also be specified. These
vendor to do the hardware selection but only from off API’s are published by the SCADA system vendors to
the shelf hardware products. allow their program to interface to a third party
application.
However the following characteristics of the hardware
equipments may be specified to take care of future user 4.2.11 Maintenance Facilities and Tools
requirements: The design of the SCADA system shall be such that it
a) Performance — CPU utilization/memory shall allow easy development, maintenance and
utilization under peak/normal activity operation. It is advisable to have a separate system for
condition; performing the development activities.
14
IS 15953 : 2011
The maintenance activity in the control centre includes r) Database on lining methods, time
the following: requirements, archiving of previous run-time
database; and
a) Database development and maintenance
activity; s) Tracking database changes.
b) Display development and maintenance 4.2.11.2 Display development
activity;
The displays development tool shall support the
c) Reports/Forms development and maintenance development and generation all types of displays in
activity; and the SCADA system. The following requirements for
d) Application development and maintenance the development tools may be specified:
activity.
a) Develop display elements, link display
The maintenance activity in the RCCI includes the elements to the database via symbolic names,
following: establish display element dynamics via
a) RCCI database configuration; and database linkages, combine elements and
linkages into display layers, combine display
b) RCCI diagnostics.
layers into displays;
The database and display development tools are
b) Types of display such as tabular, graphical,
generally proprietary.
multi-page, multi-layered displays, world
4.2.11.1 Database development displays;
The SCADA system has different types of database c) Definition of refresh rates, initial zoom size
such as development (modelling) databases, run-time of display, point of focus of a display;
(real-time) database and historical database. The d) Support for types of symbols, display
database development tools requirement such as the elements, user interaction fields and displays,
following may be specified: colours, fonts, formats graphical objects,
pictures, poke points;
a) Single source for modelling database of all
e) Support for static transformation of display
components of SCADA system;
elements like rotation, scaling, flipping;
b) Characteristics of source database —
f) Support for dynamic transformation like
expandable without requiring software code
flashing, reverse video, changing graphical
changes;
attributes, changing symbol based on value
c) Hierarchical control centre setup requirements of the linked database object;
like single point of source database
g) Automatic tabular generation from database;
maintenance;
and
d) Symbolic access to database;
h) Support for creating the database from
e) Resize the entire database, redefine the graphical topology. This need to be mutually
structure or any portion of the database; agreed between the user and the supplier.
f) Full graphics user interface;
4.2.11.3 Reports/Forms development
g) Import and export utility for bulk population
of database; The tools shall support all the following facilities
h) Multiple user access to database required to generate and edit reports in the SCADA
simultaneously with record level protection; system:
j) Database interactions like locate, order, a) Extensive help for guiding a user in building
retrieve, update, copy, insert and delete; a basic report;
k) Type of changes to be done online and offline; b) Defining reports parameters such as database
m) Database validation, referential integrity, linkages, report formats, report activation
reasonability and integrity checks; criterion, report destination, retention period
n) Generation of error messages for helping user/ of report;
extensive help regarding each activity; c) Capability to format reports for workstation
p) Run-time database generation-incremental/ and printers;
complete; d) Presentation format such as alphanumeric
q) Data retention — Data which is to be retained display, graphical display or alphanumeric
across database generation cycles; printer format;
15
IS 15953 : 2011
e) Processing functions applied at the time of The following requirements may be specified.
report generation such as summations and
other arithmetic functions; 5.1 Enclosures
f) Capability to edit the report, repeat the The computer and peripherals are generally mounted
inherent data calculations, saving the edited in their OEM enclosures/ventilated racks whereas the
report; RCCI is mounted in metal enclosures. The enclosures
g) Capability to modify an existing report for also provide a first level of protection against the
database linkages, modify its format and store electromagnetic disturbances. The equipment
it as a new report; enclosures, which are generally made of sheet metal,
h) Report generation periodicities; shall be suitable for the proposed environment.
j) Capability to export the report in some a) Enclosures should conform to the relevant IP
standard file format; and Classification tests as per IS 13947(Part 1);
k) Capability to publish the report on Web server, b) Enclosure mounting requirements —
if desired. Standalone/Wall mounted/ pole mounted;
4.2.11.4 Application development and maintenance c) Enclosure finishing requirements — Paint
coats, paint colour;
The user can specify the requirement of tools to develop
d) Enclosure dimension requirements;
new applications and maintain the existing applications
in the SCADA system. The following characteristics e) Location of access doors, glass doors;
may be specified: f) Temperature/ventilation requirements;
g) Humidity control requirements;
a) Code management system for documenting
and controlling revisions to all SCADA h) Terminal-block type and location and
programmes; connector requirements should be specified
for individual applications;
b) Compilers, assemblers, linkers and loaders,
j) Cable entry locations, and special cabling
symbolic debugger;
requirements;
c) System integration for adding new
k) Type of cables for each application, cable/
programmes to the set of active software;
wiring requirements;
d) System generation for generating an
executable object code of all software, m) Enclosure grounding connections; and
database, displays and reports, batch files and n) Weight constraints at site, if any.
interactive procedures for complete system
5.2 Grounding
generation;
e) Failure analysis programmes to produce The SCADA equipment shall not place a ground on a
operating system and application programme floating power source. Care shall be exercised to ensure
status data for analyzing the cause of fatal ground compatibility when grounded power sources
programme failure; are used. The code of practice for earthing may be
f) Diagnostics for trouble shooting each of the referred as given in IS 3043. The SCADA system
components of the SCADA system; vendor’s recommendation on the grounding practices
shall also be considered.
g) Auxiliary memory backup and restore facility;
and 5.2.1 Safety or Equipment Ground
h) System performance monitoring software. The safety or equipment ground protects personnel
from injuries caused by live conductors coming in
5 GENERAL CONSIDERATIONS FOR SCADA
contact with the equipment cabinet or enclosure. The
SYSTEM
ground conductor shall be bundled with the power
The SCADA system shall be placed in the utility conductors, but be insulated from the power conductors
environment and required to interface with various and from other equipment and conduit. The ground
equipments. The control centre equipments like conductor is usually terminated in the cabinet
computer and peripheral devices are generally provided enclosure, and grounded only at the same point that
a controlled environment that is the temperature, the electrical service or UPS neutral is grounded. All
humidity and purity is controlled within a specified cabinets and/or enclosures comprising any control or
range. However, the RCCIs are kept in remote locations data acquisition equipment shall be grounded together
where the environment is uncontrolled. by means of a ground cable or strap.
16
IS 15953 : 2011
Any buildings or allied structures for keeping all 5.3.1 Control Centre
cabinets and/or enclosures comprising any control or
The control centre equipment shall be capable of
data acquisition equipment shall be protected from
operating without error or damage with the following
lightening and code of practice for protection against
variation in the power supply source 230 V ac single
lightening may be referred as given in IS 2309.
phase or three phase + 10 percent and –15 percent at
Additionally, metal decking or other electrical paths 50 Hz + 3 percent.
should be grounded only at the same point that the
5.3.2 Remote Station Equipments
electrical service or UPS is grounded. Safety or
equipment grounds shall be established in accordance Remote station equipment shall be capable of operating
with SP 30. without error or damage with one or more of the fol-
lowing source voltage ranges:
5.2.2 Signal or Instrumentation Circuit Ground
a) 230 V ac single phase + 10 percent at 50 Hz
The signal or instrumentation circuit ground shall be + 3 percent; and
connected to an external ground at a single point so
b) 24/48/110/220 V dc nominal with +20 percent
that ground loop conditions are minimized. The
variation.
shielded wire, drain wire, and/or ground wire of input/
output cables shall be terminated at one ground point 5.3.3 Power Quality
in each cabinet. These ground points shall be
Station power shall be of such quality (free from noise,
connected together and connected to the facility
spikes, etc) to be suitable for use as a source to elec-
ground. Caution shall be used to prevent inadvertent
tronic equipment. The user and supplier shall both be
ground paths from devices such as convenience outlets,
responsible for conditioning (as required) the electric
conduit, structural metal, test equipment, and external
power for use by SCADA equipment. The one end of
interfaces.
ac power supply to master station for SCADA system
A special caution on filtering is worth noting. If the should be grounded with isolating transformer.
noise is shunted to the signal ground, then it becomes
5.3.4 Internal Noise
another source of signal reference corruption.
Sometimes separate power, noise, digital, and analog The control and data acquisition equipment internally
ground buses are necessary. However, the requirement generated electrical noise, from 1 000 to 10 000 Hz,
for a single point safety grounding source shall always appearing on the power source terminals shall be less
be met. A very important design rule is to keep all signal than 1.5 percent (peak to peak) of the external power
reference voltages, at all frequencies of operation, as source voltage. This is measured into an external power
close to zero as possible (that is at zero voltage signal source impedance of 0.1 Ω minimum.
reference).
5.4 Data and Control Interfaces
5.2.3 Electrical Ground
Data and control interfaces consist of electrical
The station power source shall be grounded in interconnections between control and data acquisition
accordance with the standard. equipment (RCCI) and the device being monitored and
controlled. Two types of signal paths are defined as
5.3 Electrical Power follows:
The electric power supply to SCADA equipment is to a) Data paths — Inputs to data acquisition or
be chosen from the type of power supply available in supervisory control equipment; and
the control centre and the sub-station. The control
b) Control paths — Outputs from data
centre equipments are generally powered from 230V
acquisition or supervisory control equipment.
ac power supply and are powered by a UPS
(uninterruptible power supply) to ensure regulated and For each input (data) or output (control) path, various
uninterruptible power supply. The RCCI is powered signal characteristics shall be defined to specify the
generally from the dc power supply available at the interfaces between equipment.
location.
Data and control signal cabling, which are external to
Equipment operating on direct current shall be control and data acquisition equipment (RCCI), are not
provided with protection such that these do not sustain specified.
damage if the input voltage declines below the lower
limit specified or is reversed in polarity. Also the 5.5 Communication
equipment shall have protection against the ac ripple Communication interfaces consist of functional,
superimposed on the dc power supply. mechanical, and electrical interconnections between
17
IS 15953 : 2011
the control and data acquisition equipment and the There are unusual conditions that, where they exist,
communication equipment. Generally the shall receive special consideration. Such conditions
communication interface requirement is specified in shall be brought to the attention of those responsible
the communication protocol standards and is as per for the application, manufacture, and operation of the
the expected usage. The communication channel equipment. Devices for use in such cases may require
includes PLCC, microwave, radio, copper cable, fibre special construction or protection. The user should
optic types, VSAT, etc. specify those special physical requirements that apply
to specific locations. Examples:
5.5.1 Control Centre/RCCI Links
a) Damaging fumes or vapours, excessive or
Signal interfaces between the control and data abrasive dust, explosive mixtures of dust or
acquisition equipment (RCCI) and the data gases, steam, salt spray, excessive moisture,
communication equipment (for example a data modem) or dripping water;
occur whenever the data communication equipment is
b) vibration, shocks, or tilting;
not packaged as an integral part of the control and data
acquisition equipment, as illustrated in Fig. 5. c) Radiant or conducted heat sources;
d) Special transportation or storage conditions;
Signal interfaces between the control and data e) Space limitations;
acquisition equipment (when the data modem is part
f) Power limitations;
of the control and data acquisition equipment) and a
communication channel are illustrated in Fig. 6. g) Communication limitations;
h) Operating duty, frequency of operation,
The following may be specified for the communication difficulty in maintenance access;
interface: j) Altitude of the operating locations in excess
a) Connectivity configuration such as point to of 1 000 m;
point/party line; k) electromagnetic interference; and
b) Redundant or single connectivity; m) exposure to ultraviolet light.
c) Type of communication channels; and
5.6.1 Environment
d) Channel failure recovery mechanism.
The different factors affecting equipment placed in a
5.6 Environmental Conditions specific environment are listed here.
This clause contains a definition of the environment in 5.6.1.1 Ambient temperature and humidity conditions
which the SCADA equipment is required to operate. Ambient temperature and humidity are defined as the
CONTROL AND DATA DATA MODEM

ACQUISITION (,+-) COMMUNICATION
EQUIPMENT CHANNEL
(,6-)
interface interface
DTE — Data terminal equipment DCE — Data communication equipment
FIG. 5 S IGNAL INTERFACES BETWEEN CONTROL AND D ATA ACQUISITION EQUIPMENT

AND D ATA C OMMUNICATION E QUIPMENT
CONTROL AND DATA COMMUNICATION

ACQUISITION CHANNEL
EQUIPMENT
FIG. 6 SIGNAL I NTERFACES BETWEEN CONTROL AND DATA ACQUISITION

EQUIPMENT AND COMMUNICATION CHANNEL
18
IS 15953 : 2011
conditions of the air surrounding the enclosure of the damage or degradation due to UV exposure. The user
equipment (or the equipment itself, if it uses open rack shall supply information pertaining to the anticipated
construction) even if this enclosure is contained in average daily hours of direct exposure to sunlight.
another enclosure or room.
5.6.2 Electromagnetic Interference (EMI) and
The requirements for temperature and humidity for Electromagnetic Compatibility (EMC)
different type of operating location is given in Table 1.
The SCADA equipments shall follow design criteria
Generally only two types are sufficient however
and recommend practices that will minimize the
equipment subjected to temperature and humidity
adverse consequences of exposure to EMI. Effective
variations outside of the two type classifications listed
protection can only be accomplished through a
in Table 1 will require special consideration.
combination of adequate design and proper installation.
The following measures may be taken to control the The basic design goal for achieving protection from
humidity and the temperature: EMI shall be that of keeping any abnormal voltage or
current, or both, out of the equipment cabinets.
a) Low temperature — A thermostatically
controlled heater strip should be used in the The SCADA equipment shall be designed for EMI/
cabinet enclosure or use wide temperature EMC criteria in conformance with IEC 60870-2-
range equipment. 1:19951 ) for minimum level 2 requirements for RCCI
b) High temperature — A sun shield, some other and minimum level 1 requirements for Control Centre
cooling method, or wide temperature range equipments.
equipment should be used in case of devices Equipment failures resulting from EMI damage should
placed in open. be fail-safe. Logic designs should be such as to
c) High humidity — Heater strips or special minimize the possibility of false or improper operation
shelters should be used. of field devices. Partial failures that do not disable the
d) Low humidity — A humidifier should be used equipment but can reduce or eliminate security features,
to maintain acceptable humidity levels. such as error checking in communication circuits, shall
be detected and cause the blocking of control outputs
5.6.1.2 Dust, chemical gas and moisture
to prevent false operations of field devices.
Any requirements of special provisions for protection
The basic installation goal for achieving protection
such as presence of atmospheric pollutants can be
from EMI shall be to minimize the exposure of all
made, where necessary.
connecting wires and cables. Power, signal, and
5.6.1.3 Altitude communication circuits provide a path through which
EMI enters equipment. Circuits totally within a
The SCADA equipment shall generally be suitable for
protected building can generally be installed without
operation at altitudes up to at least 1 000 m. Any
regard to these external effects. These circuits may still
requirements of special provisions need to be made,
be subjected to transients generated by the operation
where necessary.
of solenoids and control relays. Circuits that are
5.6.1.4 Ultraviolet (UV) light exposure connected to, or are part of, circuits not within a
The user shall specify the expected level of exposure
1)
to ultraviolet radiation attributable to sunlight where The current versions of the base standards of IEC 61000-4 series
which are referred in the IEC 60870-2-1(1995) standard may be
equipment is to be installed outdoors. Equipment
used on basis of mutual agreement between the User and the Vendor
cabinets, paint finishes, and jacket material of any keeping in view the location of the equipment(for example Bay
exposed cabling shall be sufficiently treated to resist RCCI).
Table 1 Operating Temperature and Humidity by Location

(Clause 5.6.1.1)
Sl Type Typical Location Humidity Operating Range Temperature Allowable Rate of Change
No. of the Equipment (Percent Relative Humidity) Operating Range of Temperature
°C °C/h
(1) (2) (3) (4) (5) (6)
i) 1(a) In a building with air-conditioned areas 40 to 60 +20 to +23 5
ii) 1(b) In a building with air-conditioned areas 20 to 80 +16 to +32 5
iii) 2 In a building or other sheltered area without 10 to 95 without condensation 0 to +55 20
special environmental control
iv) 3 Extremes outside the above User to specify User to specify User to specify
19
IS 15953 : 2011
protected building should be installed in a manner that It is the degree to which the configuration minimizes
will minimize exposure. maintenance requirements and supports and easily
replaceable components. The most common repair
When installation constraints result in a high degree
strategy is for the supplier to train the user’s personnel
of exposure to EMI such as surges, supplementary
in problem isolation and replace faulty modules/
protection such as spark gaps or surge limiters should
components on-site from the user’s stock of spare
be considered.
modules. If on-site service by the supplier is necessary,
The computer and microcomputer based equipment are it is most likely to be required for failures of complex
expected to perform their intended functions in computer equipment.
substations even when exposed to transient
The supplier shall, upon request, be required to provide
electromagnetic interference.
as part of the system proposal, a list of test equipment
The user should specify the EMI level for guarantee- and quantities of spare parts calculated to be necessary
ing proper operation of the SCADA equipment. to meet the specified availability and maintainability
Annex C gives the test requirements for a typical requirements. In establishing the quantities of spare
transmission sub-station. parts, the supplier shall consider the time required to
return a faulty component (field and/or factory service
6 DESIGN CHARACTERISTICS as the case may be) to a serviceable condition.
This clause defines general characteristics that are Mean time to repair (MTTR) is the sum of
required of the control and data acquisition system. administrative, transport, and repair time.
These characteristics include reliability, Administrative time is the time interval between
maintainability, availability, security, expandability, detection of a failure and a call for service. Transport
and changeability. time is the time interval between the call for service
and on-site arrival of a technician and the necessary
6.1 Reliability
replacement parts. Repair time is the time required by
The SCADA system reliability is while impacted by a trained technician, having the replacement parts and
the configuration of the hardware but actually the recommended test equipment on-site, to restore
encompasses the broader issue of system’s capability nominal operation of the failed equipment.
to perform intended work continuously. For example,
a system can not be considered to be reliable if data 6.3 Availability
acquisition gets disturb in case of sudden burst of Availability (A) is percentage of the time during which
activity. Mathematically, reliability is the probability a system is actually available to users and is defined in
that system will perform its intended function under the following as the ratio of uptime to total time
specified conditions during a specified period of time. (Uptime + Downtime):
For individual equipment, failures will occur on the
average at a constant rate throughout the useful life A = Uptime/(Uptime + Downtime)
of the equipment. This allows the manufacturer to Downtime normally includes corrective and preventive
characterize equipment reliability with a simple maintenance. When system expansion activities
figure of merit called mean-time-between-failure compromise the user’s ability to operate device via the
(MTBF). system, this shall also be included in downtime.
The failure modes of equipment and the effects of these Proper use of redundant configurations with automatic
failures on overall system shall be formally analyzed fail over can provide an overall availability of primary
by the supplier. The results of these failure modes and system functions of 99.9 percent.
effect analysis (FMEA) shall be available for review
upon request. The availability level required and the planned
maintenance strategy shall be specified by the user,
6.2 Maintainability requiring suppliers to provide supporting predicted
availability calculations in their proposals.
Maintainability is the extent to which user’s personnel
can maintain the system both software and its hardware. An availability test of 1 000 to 3 000 h is often specified
Control and data acquisition equipment shall be prior to acceptance of a system. For design analysis,
maintainable on-site by trained personnel according and to determine the prediction of availability for
to the maintenance strategy specified by the user. subassemblies and units, the following equation
Requirements for training, documentation, spares, etc, utilizing MTBF and MTTR shall be used:
shall take the user’s organization and geography into
Ap = MTBF/(MTBF + MTTR)
account.
20
IS 15953 : 2011
Where Ap is predicted availability. Expandability limitations may include, but are not
restricted to the following:
Equations for modelling complex designs shall be part
of supplier proposal and agreed upon. The impact of a) Available physical space;
the outage of each system element or function on the b) Power supply capacity;
availability of the total system shall be mutually agreed c) Heat dissipation;
upon between the user and the supplier.
d) Processor throughput and number of processors;
Major component downtime shall be defined to reflect e) Memory capacity of all types;
the proportional significance of the equipment that is f) Point limits of software, or protocol;
down. For example, downtime for the data acquisition
g) Bus length, loading, and traffic;
system could be defined as master station downtime,
in proportion to the sum of the downtime for all RCCIs h) Limitations on routines, addresses, labels, or
divided by the total number of RCCIs. At the master buffers; and
station, downtime should not include malfunctions in j) Unacceptable level of performance (for
peripheral devices that do not detract from the example extension of scan times) by increased
functional capabilities of the master station as a whole data (given bit rate and protocol efficiency).
(for example, printers and tape units).
6.6 Changeability
6.4 System Security
Changeability is defined as the ease with which system,
System security is defined as controlled access to RCCI, and point data base parameters may be changed
system resources, such as functions, data, and at both the master station and RCCI. Parameters that
hardware. The security is based on, shall be easy to change include the following:
a) establishment of the identity and authenticity a) Operating parameters; and
of user before allowing interaction with b) Configuration and set-up parameters.
system;
The supplier’s documentation (see 8.3) shall contain
b) the access is extended based on the rights
the step-by-step process for parameter changes.
defined for the user in system;
c) data being stored/transmitted through 6.6.1 Operating Parameters
communication is protected against change; Operating parameters must be easily changed by the
and system user. They include, but are not limited to, the
d) system shall log and monitor all events following:
consequential to security.
a) RCCI on/off scan;
The security device and infrastructure deployed needs b) Point on/off scan;
to ensure that only authorize users are allowed to
c) Point tags on/off;
interact with system, there is identification and isolation
of unauthorized accesses and there shall be logging of d) Manually entered values;
all the events related to security for future analysis. e) Point alarm limits; and
f) Point dead band values.
6.5 Expandability
6.6.2 Configuration and Set-up Parameters
Expandability is the ease with which new RCCI, new
points and/or functions, or both, can be added to the Configuration and set-up parameters must be easily
system, with minimum or no downtime. changed by an authorized system engineer, but shall
be protected against being changed by the operator.
Expansion can be identified as addition of similar boxes They include the following:
to increase capacity of performing a function or
addition of component in existing boxes or adding new a) Configuration password;
devices/processor/servers to increase functionality. b) Alarm conditions and actions;
Expandability can be achieved by spare capacity, wired c) User-definable calculations;
capacity and space-only. Spare capacity is capacity that d) Definition of a new RCCI including RCCI
is not being utilized but is fully wired and equipped. database points;
Wired capacity is the capacity for which all common
e) Correspondence of status points to control
equipment, wiring and space are provided, but no plug-
points;
in point hardware is provided. Space-only capacity is
the capacity for which cabinet-space-only is provided f) Point scaling factors for conversion of data
for future addition of equipment and wiring. to engineering units; and
21
IS 15953 : 2011
g) Output relay delay times. functions of the equipment be tested or verified during
one or more stages in the production and installation
6.6.3 Changeability Limitations
cycle of the equipment. These stages and appropriate
Changeability limitations may result from, but are not tests are illustrated in Table 2.
limited to, the following:
Across the top of the table are shown the four major
a) Inability to make master station and RCCI data classes of tests and inspections, being interface, envi-
base changes on-line from the master station; ronmental, functional and performance. The three
b) Storage of parameters in memory (for stages of testing and inspections, being certified design,
example ROM) that is not modifiable in- factory and field, are shown along the left-hand edge
circuit; of the table. The specific tests and inspections in each
c) Restrictions caused by data base structure; class are listed in the body of the table, below the class
heading. Tests listed without notation are recommended
d) Hardware/software compatibility;
for all applications at the stage they can be performed.
e) Hardware limitations;
f) Software operating system limitations; and Tests marked with an asterik are optional and are
performed only when specified by the user. Certified
g) Restrictions caused by use of IEDs.
design tests on equipment can be accepted at the user’s
The supplier shall declare all these limitation upfront discretion.
as part of its proposal.
7.1.1 Certified Design Tests
6.7 Spare Memory These are tests performed by the supplier on specimens
Spare memory is defined as the additional computer of a generic type of production model equipment and
memory capacity that can be added to the master system to establish conformance with its design
station. A requirement of no less than 50 percent unused standard. The conditions and results of these tests shall
main and auxiliary memory shall be delivered to take be fully documented and certified.
care of moderate expansion of power system. As a 7.1.2 Factory Tests and Inspections
minimum, it shall be possible to double the main and
auxiliary memory delivered initially with the addition This stage includes all functional tests and inspections
of modules. performed on the actual equipment to be supplied to
the user prior to the shipment of that equipment from
6.8 Marking the supplier’s facilities. The factory tests shall be a
highly structured procedure designed to demonstrate,
The control and data acquisition equipment and major
as completely as possible, that the equipment will
sub-assemblies shall be suitably marked for safety and
perform correctly and reliably in its intended
identification. Each type of equipment shall be
application. Factory tests may also include tests to
identified so that it can be easily correlated with the
verify some of the results of the certified design tests.
documentation. The means of identification (for
example colour coding, labelling, and part number) 7.1.3 Field Tests and Inspections
shall be uniform throughout the system. The Field tests and inspections are performed on the
identification mark shall be permanently affixed to the equipment in its operating environment. These include
part that it identifies. pre-installation inspections and tests to ensure the
equipment has not been damaged during shipment and
7 TESTS AND INSPECTIONS
post-installation tests to verify the equipment performs
The purpose of this clause is to describe the tests and its functions reliably and correctly.
inspections recommended to ensure that control and
data acquisition equipment will perform reliably and 7.2 Interface Tests and Inspections
correctly according to the user’s technical specifica- These tests are designed to demonstrate that the various
tions. Test requirements shall cover, as a minimum, all physical and logical interfaces to the equipment are in
critical portions of the specification, especially accordance with applicable portions of 5, together with
functional, design, configuration, user interaction and other applicable parameters called out in the user’s
expandability requirements. Test results and all specifications with simulated communication/
deviations from test plans shall be required to be connection medium which will be agreed between
documented. owner and the supplier.
7.1 Stages of Tests and Inspection 7.2.1 Mechanical
The test and inspection process requires that various Mechanical characteristics (for example materials,
22
IS 15953 : 2011
Table 2 Test Stages and Classes of Tests

(Clause 7.1)
Sl Test Stages Classes of Tests
No.
Interface Tests and Environmental Tests and Functional Tests and Performance Tests and Inspections
Inspections Inspections Inspections
(1) (2) (3) (4) (5) (6)
i) Certified design Power input* EMI/EMC Temperature — —
tests Humidity
ii) Factory tests Mechanical Temperature* Humidity* I/O point checkout Loading Data acquisition Control
and inspections power source* Dust* communications user User interface Computer and disk
interface special functions stability* Maintainability*
Expandability*
iii) Field tests and Connectivity to — I/O point checkout Loading and availability
inspections existing system and communications user
field devices interface selected
functions
* Optional tests performed only when specified by the user.
workmanship, dimensions, fabrication techniques and equipment performs its functions reliably and correctly.
finishes) shall be verified through visual inspections They are performed during the factory, or field test
and comparisons with applicable drawings. stages, or both. Preliminary testing should be
performed by the supplier before verification by the
7.2.2 Electrical
user. For many applications and types of equipment,
These tests include all those to be performed on successful factory tests will be a sufficient basis for
electrical interfaces to the equipment, with the acceptance of the system by the user. For more complex
exception of those related to the functional applications or systems, additional tests in the field may
performance of the equipment. be required to fully verify correct and reliable
7.2.2.1 Power source performance.
The equipment shall be tested to demonstrate the proper The following functional tests should be carried out:
operation of the equipment throughout the range of a) Interface of RCCIs with IEDs;
specified power source parameters. b) End to end testing for database and alarms
7.3 Environmental Tests validation;
c) Remote workstation testing;
These tests are designed to demonstrate that the
d) Remote control testing;
equipment will perform correctly and reliably while
exposed to the applicable environmental parameters e) Checking of reports, archiving and trending
described in 5, together with other applicable functions;
parameters called out in the user’s specifications. The f) Clock synchronization between the nodes of
results of certified design tests are usually sufficient to master station and RCCIs;
demonstrate that the equipment will operate reliably g) Security/Passwords testing;
and correctly within a specified environment. The user h) Communication protocol testing; and
may require the supplier to perform factory tests on j) User interface testing.
the equipment to demonstrate that it will indeed
perform correctly under the specified environmental 7.4.1 I/O Equipment Checkout
conditions. Equipment in environmental tests should All I/O equipment being supplied shall be exhaustively
be operating with realistic inputs and outputs. tested to demonstrate its functions. These tests shall
The environmental parameters (EMI/EMC, be performed with equipment that simulates the actual
temperature, humidity and dust) and testing inputs/outputs to be monitored or controlled in case of
requirements specified by the user should be limited factory. Field environment may not always be suitable
to the worst case conditions that can be realistically for testing process outputs.
anticipated in the location where the equipment will 7.4.2 Communication
ultimately be installed. See IS 9000 series for various
environmental tests. The communication tests shall demonstrate proper
operation of the equipment’s communication
7.4 Functional Tests capability, including modems, security checking, and
Functional tests shall be designed to ensure that the message protocols. The data modems or signalling
23
IS 15953 : 2011
equipment shall be exercized to verify that they operate by functional tests and that the total system is ready to
correctly and reliably on the type of channel for which be evaluated.
they are designed, under given signal to noise ratio.
If actual system inputs are not available, they shall be
The tests shall be conducted under conditions that
simulated with special hardware or software. For a
duplicate, as closely as possible, the specifications for
meaningful test, these inputs shall include the following:
the channel including simulated channel noise,
communication failures and recovery. a) Simulated RCCI/process inputs (alarm
contacts, analog inputs, status input, etc);
The communication tests shall exercise all message
protocols and formats to which the equipment is b) Simulated message data structures from the
designed to respond. The tests shall also demonstrate RCCIs into the master station communication
that any error detection or correction capabilities func- interfaces;
tion properly and that the equipment does not respond c) Simulated data links to other computers,
to erroneous commands. specifying the amount, type and frequency of
data to be transferred;
7.4.3 User Interface (UI)
d) Simulated user interfaces such as wall mimic;
Comprehensive user interface tests shall be performed and
to verify the correct functional operation of all user e) Other simulated inputs.
interface hardware and software. All indications and
displays shall be verified to ensure that they correlate Table 3 System Performance Tests1)
with the correct I/O of field equipment, and all user (Clause 7.5)
controls shall be checked to ensure that they result in
only the correct sequence of operations. Sl No. Input Activity Cycle
(1) (2) (3)
7.4.4 Special Functions i) Normal activity:
a) Each user 1 display request/min
When the equipment supplied is to perform functions b) Status input 1 percent changes/scan
tailored expressly to the user’s application (for example c) Analog inputs 1 percent of all analogs
closed loop control), these functions shall be checked change/scan
ii) Heavy activity:
appropriately. It is often necessary to perform these a) Each user 4 display request/min
tests in the field, in addition to factory testing. b) Status inputs 10 percent changes/scan
c) Analog inputs 25 percent of all analogs
7.5 System Performance Tests change/scan
The performance parameters of all critical component 1)

Values given are for example only. It is recommended that the
of the system (for example communication, user select values that represent the user’s system characteristics
peripherals, user interfaces, I/O processing, and CPU) and operating procedures.
Manual operation sequences to be performed during tests shall be
shall be measured under various loading conditions or
described in detail to provide a repeatable test scenario and a way
scenarios. System performance shall be measured as to measure improvements in performance (for example five people
early as possible in a project to identify any system requesting one-line diagrams and two people requesting menu
weakness. This will allow the user and supplier an displays simultaneously). Test steps should simulate all normal
user operations.
opportunity to resolve problems in a timely manner.
Response performance shall be measured in seconds. All
The loading scenarios shall simulate the following: measurements shall be recorded for analysis after the tests.
Software utility programmes are available from most system
a) Normal activity — Initial system; suppliers for finding CPU utilization and loading (for example,
feature of the computer operating system or a separate programme
b) Heavy activity (disturbance loading defined
available from computer manufacturer, or both) and if used by
by user) — Initial system; and supplier the system loading of the programs shall be provided to
c) Communications failures or high noise user with proof. Automatic measurement of other test parameters
can be done by special purpose software.
conditions such as high noise on an entire
microwave system.
7.5.1 Data Acquisition Performance
Loading conditions should be determined by analyzing
worst case conditions experienced by the user and the Data acquisition sub-system performance measures the
worst possible condition likely to happen in the future following:
over the life of the system. Table 3 is provided as a a) The time for a status change or analog change
guide. at the RCCI to be displayed to the user at the
The measurements for performance assume that all master station (for example, monitor, logger
functions of the system have been individually verified or mimic); and
24
IS 15953 : 2011
b) The time to query all RCCIs on a channel. peripheral equipment to the primary system, the
secondary system, or off-line (that is out-of-service).
A cyclic status point input of 2 or more times faster
than the system RCCI scan rate can be used to detect a Power fail tests measure the time to recover from a
missed scan due to overloading. The status input complete or partial power failure until the system is
simulator should be connected to an input of one RCCI. fully operational.
The alarm associated with the toggled input shall
Restart tests are to assure the system will recover in
appear on the logger with a time tag of approximately
specified time from failures. Existing data shall consist
twice the scan rate. A system overload causing an
of all scanned and manually entered data (that is values,
extension of the scan cycle is obvious from the printout
system tags, manual overrides, limit changes, etc).
because one or more status changes are missed.
The time required to load a system from mass storage
7.5.2 Control Performance
and initiate operation should be measured (cold start).
Control performance measures the elapsed time
between a control request by a user at the master station 7.6 Test Run/Availability Test
and the control output contact closure at the RCCI. An availability test takes place over a specified length
This test shall also be performed in the field. The field of time during which the equipment shall operate
test will provide realistic measurements, using user correctly and reliably for at least a specified percentage
installed RCCIs and communication facilities. of that time. The length of the test shall be mutually
7.5.3 User Interface Performance agreed to between the supplier and the user.
The user interface performance is a measure of the The availability test shall be run under conditions
response time to satisfy user requests for information. mutually agreeable to the user and the supplier. In
To measure display response time, measure the time general, the supplier shall be responsible for making
from the instant a request is made until the result of the necessary repairs. Downtime should not include
the request is completely displayed on a UI screen, delays over which the supplier has no control.
printed on a logger, or shown on a mimic panel.
This is followed by analyzing the number and types of
Different classes of displays (one-line diagrams, alarm
failures, and their effects on system operation. The test
summaries, menus, tabular, etc) may have different
time should be selected so that the total number of
display response times due to the amount of data to be
device operating hours for each type of system-critical
gathered and computations required before a display
device is representative of the predicted MTBF for that
request can be completed.
device to obtain statistically significant failure data.
7.5.4 Computer and Disk Performance Specific rules for accumulation of uptime, downtime,
maintenance time, and administrative time shall be
The computer and disk performance shall be checked
agreed upon before the test (see 6).
against the user specified limits using the supplied
programs from computer manufacturers to ascertain 7.7 Maintainability Test
that CPU and disk utilization is within acceptable limit
as specified by user. The user shall require a maintainability test to be run
to evaluate the supplier’s design, documentation, train-
7.5.4.1 Computer link response time ing, and recommended spare parts. Maintainability will
Computer to computer link response times should be directly affect the availability of the SCADA system
measured and evaluated during performance tests under and therefore the reliability of the system (see 6.2).
varied loading conditions. Computer hardware maintenance and long term repair
support are difficult to evaluate without actual
7.5.4.2 Computer LANs utilization experience. Discussion with other users regarding their
Loading on LANs that connect application computers experience is one way to acquire a certain degree of
together should be measured and evaluated during knowledge about the maintainability of specific
performance tests. equipment and systems.
7.5.4.3 Equipment reconfiguration, power fail and Software, database, and display maintainability is also
restart tests critical to the successful operation of a SCADA sys-
tem. Tests to be witnessed may include the following:
On systems with redundant equipment, reconfiguration
tests should be performed to confirm the ability to System generation tests (measure time to
failover from one CPU/power supply to another completely install system, and type/quantum of
(reconfigure the real-time database) and to switch manual intervention required)
25
IS 15953 : 2011
a) Database maintenance test shall include: d) Maintenance instructions and records; and
1) Adding an alarm point; e) Test (including quality assurance and quality
2) Deleting or changing text on an alarm control test plans).
point; and In general, all final documentation provided by a
3) Changing an analog scale factor. supplier shall reflect the actual equipment as accepted
by the user, and all subsequent equipment changes shall
b) Display maintenance: be recorded as document revisions by the user.
1) A new one-line diagram should be added
and linked to the database (a specific If users desire to have the information on reliability as
example in the specification should be described in 6, they shall collect information on failures
provided); and and repairs for all sub-assemblies. This data on
operating performance shall then be periodically
2) A line and new devices should be added
provided to the supplier and can be basis for future
to an existing one-line diagram including
product/solution evaluation.
analogs, tags, etc.
Documentation described in 8.1 through 8.5 may be
c) Equipment maintenance with spares being
subject to user review or approval. Documentation may
supplied as part of project for example
be structured in alternate fashion, but shall cover all
1) A monitor should be replaced; five areas. The documentation may be supplied in one
2) A modem should be replaced; or more of several forms-printed, computer stored, or
3) A disk drive should be replaced; electronic media. In the latter case, the supplier shall
4) A printer should be defines/added; and either identify or supply the supporting word
5) One card of each type shall be replaced processing software used to prepare the documentation.
and/or added.
8.1 Design Documentation
7.8 Expandability Tests
Design documentation is the responsibility of the
Expansion capability of a new system shall be supplier. Block diagrams shall be included to describe
demonstrated during testing as specified (see 6.5). For control and data acquisition equipment and external
example: equipment. Layout and wiring drawings shall also be
included to define external interconnection needs at
a) RCCI I/O point expansion (both hardware and
each facility. Text, photographs, and illustrative
software changes required);
material shall accompany these drawings in sufficient
b) Addition of RCCIs; and detail so that functional performance and design may
c) Master station expansion: be readily understood. For example, functional block
1) Peripherals, disk space, memory; diagrams and explanatory text shall be used to describe
2) CPU capacity (percent utilization); each major assembly and software programme
3) User interface (work station additions); contained in the equipment configuration. A document
and describing the communication process between the
master station and the RCCIs shall be provided. The
4) Database and display expansion.
supplier shall be responsible for providing outline
7.9 Documentation Verification drawings, mounting requirement details, customer
connection details, environmental requirements, size,
The final phase of the testing programme is to verify weight, and any other information needed for the user
that the documentation being supplied is an accurate to prepare for installation.
description of the equipment, including all corrections
resulting from the tests. Final issue of completed 8.2 Installation Documentation
documentation shall be provided as soon as possible
Installation documentation is the responsibility of both
after shipment and acceptance of the equipment.
the supplier and the user shall define the following:
8 DOCUMENTATION a) Electrical power, data, control and
The documentation for control and data acquisition communications interface wiring procedures;
equipment shall cover five basic areas as follows: b) Floor, rack and shelf mounting, drilling, and
bolting methods necessary to secure the
a) Design;
equipment in place;
b) Installation;
c) Safety precautions or guards;
c) Operating instructions and records; d) Grounding and bonding procedures;
26
IS 15953 : 2011
e) Clearances for access and ventilation; programmes shall be described and illustrated by
f) Testing and alignment methods; functional block diagrams. Detailed logic diagrams and
g) Weather proofing, dust proofing and other flowcharts shall also be provided as necessary for
environmental procedures; and trouble shooting analysis and field-repair actions.
h) Other procedures needed to properly install 8.4.2 Preventive Maintenance Instructions
the equipment.
These instructions shall include all applicable visual
8.3 Operating Instructions and Records examinations, software and hardware test and diagnos-
tic routines, and resultant adjustments necessary for
Instruction information shall be developed for periodic maintenance of control equipment.
operating personnel who use the control and data Instructions on how to load and use any test and
acquisition equipment. diagnostic programme, and any special or standard test
8.3.1 Operating Instructions equipment shall be an integral part of these procedures.
The supplier shall publish instructional information 8.4.3 Corrective Maintenance Instructions
defining the equipment and how it shall be operated. These instructions shall include guides for locating
The information shall consist of a general description malfunctions down to the spare parts replacement or
of the equipment configuration provided and shall state field-repair level. These guides shall include adequate
its intended use and its major performance details for quickly and efficiently locating the cause
characteristics. Whenever a user interface such as a of an equipment malfunction, and shall state the
console, indicating/control panel or printing device is probable source(s) of trouble, the symptoms, probable
involved, the operational documentation shall detail cause, and instructions for correcting the malfunction.
step required to use these interface devices. Adequate These guides shall explain how to use any on-line test
illustrative material shall be included to identify and and diagnostic programme and any special test
locate all control indications. equipment, if applicable.
Procedural instructions, that state routine and Corrective maintenance instructions shall also include
emergency procedures, safety precautions, and explanations for the repair, adjustment, or replacement
quantitative and qualitative limits to be observed in of all items. Schematic diagrams of electrical,
the starting, running, stopping, switching, and shutting mechanical, and electronic circuits; parts location illus-
down of equipment, shall be included. Whenever trations, or other methods of parts location
operating procedures or adjustments are to be information; and photographs, and exploded and
performed in a specific sequence, step-by-step instruc- sectional views giving details of mechanical
tions should be stated. assemblies shall be provided as necessary to repair or
8.3.2 Records replace equipment. Information on the loading and use
of special off-line diagnostic programmes, tools, and
Records shall be prepared by both operating and test equipment, and any cautions or warnings which
maintenance personnel to support the availability/ shall be observed to protect personnel and equipment
reliability calculation defined. shall also be included.
8.4 Maintenance Instructions and Records 8.4.4 Parts Information
Maintenance documentation for skilled personnel as This information shall include the identification of each
per agreed maintenance philosophy shall be developed replaceable or field repairable module. Parts shall be
and provided by the supplier, and shall include the identified on a list or drawing in sufficient detail for
following information listed in 8.4.1 through 8.4.4. procurement of any repairable or replaceable part.
These parts shall be identified by their industrial,
8.4.1 Performance Information
generic part numbers and shall have second source
This information shall include a condensed description referencing, whenever possible.
of how the equipment operates (derived from 8.1) and
a block diagram illustrating each major assembly and 8.5 Test Documentation
software programme in the configuration. Message Test documentation by the supplier shall consist of a
sequences, including data and security formats for each system test plan, test procedures and certified test
type of message, shall be included in the condensed reports on tests described in 7. The test plan shall state
description and illustrated whenever such messages are what equipment configuration will be tested, when it
used between stations or locally at a station. The will be tested, which tests will be run, and who will
operational sequence of major assemblies and conduct and witness the tests. The test procedures shall
27
IS 15953 : 2011
define the operating steps and expected results. The SCADA equipments. Hence, long-term agreements
test report shall record all test results. with the supplier for the SCADA system can be made
either for supply of spare parts for the expected life of
9 SCADA SYSTEM IMPLEMENTATION ISSUES the SCADA system or for maintenance of system.
There are certain issues which require a great deal of Also with time, the SCADA system keeps on growing
attention while implementing a SCADA system: to accommodate the growing power system. However,
as explained above, the components for achieving this
9.1 Integration with Existing System
expansion are not available even though provisions for
The utility may have existing set of equipments like expandability are made in the system. Hence, it is
RCCIs or even a control centre. The requirements of advisable to have an estimate of the ultimate system
integrating these equipments shall be specified. A sizing requirement and equip the SCADA system with
techno-commercial analysis has to be done beforehand all necessary components for this ultimate size. The
so that the pros and cons of integrating the existing performance testing of the SCADA system can be done
equipment can be worked out. Often it is felt that by removing these additional components.
integrating an existing system requires lot of effort.
This is especially more the case when the system to be 9.4 Maintenance of the SCADA System
integrated is a proprietary system with no support for
The SCADA system is an advanced, complex and
standard communication protocols.
proprietary information technology (IT) system which
9.2 Training requires knowledge and skills of software, hardware,
standards etc. Generally the utilities do not have
The personnel who are to operate and maintain the personnel of high level of knowledge and skills in IT
SCADA system shall be identified and involved in the domain. Also there are issues like obsolescence.
implementation of the SCADA system from the initial Utilities have to decide whether they wish to take up
stages. This provides an opportunity for the personnel the maintenance activity of the SCADA system
to become familiar with the system and hence to use it themselves or will enter into a long-term agreement
more effectively. with the SCADA vendor for maintenance and upgrade
These personnel shall be provided extensive training of the system to maintain an evergreen SCADA system.
about the system. Generally the training requirements If the maintenance is to be done through the SCADA
can be classified as following: vendor, this requirement shall be specified.
a) RCCI; 9.5 Customized Product versus SCADA Vendor

b) Computer system hardware; Product
c) Computer system software; and The utility shall specify only the functional
d) SCADA application software. requirements and shall refrain from specifying specific
technology or procedures unless it is very critical to
9.3 Spare Availability and Expandability
their interest. Any customization requires an additional
The SCADA equipments keep evolving with the development effort on the part of SCADA vendors
innovations in technologies. This causes obsolescence which may not be carried over to the next version of
of the equipments and the newer generation of the the SCADA system. Hence customizations become
hardware may not be compatible with the existing costly to implement and maintain.
ANNEX A
(Clause 2)
LIST OF REFERRED INDIAN STANDARDS
IS No. Title IS No. Title

1885 Electrotechnical vocabulary: 2309 : 1989 Code of practice for the protection
(Part 50) : 1985 Telecontrol of buildings and allied structures
(Part 52) : 1980 Data processing against lightning (second revision)
28
IS 15953 : 2011
IS No. Title IS No. Title

3043 : 1987 Code of practice for earthing 14570 : 1998 Electrical measuring transducers for
9000 : 1977 Basic environmental testing converting ac electrical quantities to
procedures for electronic and analogue or digital signals
electrical items 60947 (Part 1) : Low voltage switchgear and
12746 Telecontrol equipment and systems: 2004 controlgear: Part 1 General rules
(Part 1/Sec 3) : Part 1 General considerations, SP 30 : 1985 National Electrical Code
1993 Section 3 Glossary
ANNEX B
(Clause 4.1.2)
MASTER STATION/RCCI INTER-CONNECTIONS
B-1 The following Fig. 7 to 16 are informatory in

nature: RCCI 1
Master
Station 1
Master
Station RCCI
RCCI 2
Master
Station 2
FIG. 7 SINGLE MASTER STATION, SINGLE RCCI
RCCI
N
RCCI 1
FIG. 10 D UAL M ASTER STATIONS , M ULTIPLE RCCI(S),
LOOPED PARTY LINE
Master
Station RCCI 2 Master
Station 1
RCCI
Master
RCCI Station 2
N
FIG. 8 SINGLE MASTER STATION, MULTIPLE RCCI(S ), FIG. 11 DUAL MASTER STATIONS , SINGLE DUAL
RADIAL CIRCUIT PORTED RCCI, RADIAL CIRCUIT
RCCI 1
M aster
RCCI 1 Station 1
RCCI
N
Master
Station RCCI 2
RCCI 1
M aster
Station M
RCCI RCCI
N M
FIG. 9 SINGLE MASTER STATION, MULTIPLE RCCI(S ), FIG. 12 DUAL M ASTER STATIONS, MULTIPLE RCCI(S)
PARTY-L INE C IRCUIT [S INGLE PORTED RCCI(S)]
29
IS 15953 : 2011
RCCI 1 RCCI 1
Sub-Master
Master Station 1
Station 1
RCCI N
RCCI N
Master
Station 1
RCCI 1
RCCI 1 Sub-Master
Station N
Master
Station M RCCI N
RCCI M
Sub-master stations could communicate with one another.
FIG. 15 S INGLE M ASTER STATION, M ULTIPLE

FIG. 13 D UAL M ASTER STATIONS, M ULTIPLE RCCI(S) S UB-MASTER STATIONS MULTIPLE RCCI(S)
[DUAL PORTED RCCI(S)]
End Station
RCCI 1
Sub-Master
Station
Master
RCCI N
Station
Master
Station 1
RCCI 1
RCCI 1 RCCI N
RCCI M
FIG. 16 S INGLE MASTER STATION, RCCI(S) AND

FIG. 14 SINGLE MASTER STATION, SINGLE
END STATION LINK
SUB-MASTER STATION MULTIPLE RCCI(S )
ANNEX C
(Clause 5.6.2)
TEST REQUIREMENTS FOR A TYPICAL TRANSMISSION SUB-STATION
C-1 EMI/EMC AND ENVIRONMENT TEST LEVELS OF A TYPICAL TRANSMISSION SUB-STATION
Sl No. Test Name Passing Criteria

i) Surge Immunity Test (1.2/50µs) IEC 61255-22-5
ii) Electrical Fast Transient Burst Test IEC 60255-22-4
iii) Damped Oscillatory Wave Test IEC 61000-4-12
iv) Electrostatic Discharge Test IEC 60255-22-2
v) Radiated Electro-magnetic Field Test IEC 61000-4-3
vi) Damped Oscillatory Magnetic Field Test IEC 61000-4-10
vii) Power Frequency Magnetic Field IEC 61000-4-8
viii) Power Frequency Voltage Withstand IEC 60255-5
ix) 1.2/50µs Impulse Voltage Withstand IEC 60255-5
x) Insulation Resistance Test IEC 60255-5
xi) Dry Heat Test IEC 60068-2-2
xii) Damp Heat Test IEC 60068-2-3
NOTE — The IEC 61000-4-3: 2006 can be referred as base standard keeping in view location of RCCI.
30
IS 15953 : 2011
ANNEX D
(Foreword)
COMMITTEE COMPOSITION
Power System Control and Associated Communications Sectional Committee, LITD 10
Organization Representative(s)
Power Grid Corporation of India Limited, Gurgaon SHRI R. N. NAYAK (Chairman)
SHRI R. P. SASMAL (Alternate)
Areva T&D India Ltd, Noida SHRI SUDESH KUMAR NEHRU
SHRI VINAYAK NAYAK (Alternate)
ABB Ltd, Bangalore SHRI RAJIV KRISHNAN
SHRI S. R. VIJAYAN (Alternate)
Bharat Heavy Electricals Ltd, Hyderabad SHRI G. V. BANAKAR
SHRI B. K. CHATTAR (Alternate)
Central Electricity Authority, New Delhi SHRI D. K. JAIN
SHRI D. K. MALIK (Alternate)
Central Power Research Institute, Bangalore SHRI V. ARUNACHALAM
SHRI V. SHIVAKUMAR (Alternate)
Electronics Regional Test Laboratory (North), New Delhi SHRI ASHOK KUMAR
SHRIMATI MANJULA BHATI (Alternate)
GAIL (India) Ltd, New Delhi SHRI R. C HOUDHURY
SHRI TAPAN D. PARIDA (Alternate)
Gujarat Electricity Board, Vadodara REPRESENTATIVE
Kalki Communication Technologies Pvt Ltd, Bangalore SHRI PRASANTH GOPALAKRISHNAN
SHRI VINOO S. WARRIER (Alternate)
National Thermal Power Corporation Ltd, New Delhi SHRI ABIJIT S EN
Reliance Energy Limited, Mumbai SHRI HARSH S HARMA
SHRI BHUSHAN CHAUDHARI (Alternate)
Secure Meters Limited, Udaipur SHRI KAUSHIK GHOSH
SHRI SUNIL KUMAR SINGHVI (Alternate)
Siemens Ltd, Gurgaon SHRI VIKRAM GANDOTRA
SHRI GIRISH MULEY (Alternate)
Society for Applied Microwave Electronics Engg & Research, SHRI R. SIVARAMAKRISHNAN
Chennai DR B. SUBBARAO (Alternate)
TCE Consulting Engineers Ltd, Bangalore SHRI N. MURUGESAN
MS ANITA J OSHI (Alternate)
The Tata Power Company Limited, Mumbai SHRI JACOB J OSEPH
SHRI P. A. J AYAKUMAR (Alternate)
Transmission Corporation of Andhra Pradesh Ltd, Hyderabad SHRI M. GOPAL R AO
SHRI K. RAJAMANNAR (Alternate)
Wireless Planning & Coordination Wing, New Delhi REPRESENTATIVE
BIS Directorate General SHRI NARENDRA SINGH, Scientist ‘E’ and Head (LITD)
[Representing Director General (Ex-officio)]
Member Secretary
SHRI JITENDER KUMAR
Scientist ‘C’(LITD), BIS
31
IS 15953 : 2011
SCADA Working Group for Power Sector under LITD 10

Organization Representative(s)
Power Grid Corporation of India Limited, New Delhi SHRI ARUN KUMAR MISHRA (Convener)
SHRI ARUN KUMAR SINGH (Alternate)
ABB Limited, Bangalore SHRI RAJIV KRISHNAN
SHRI S. R. VIJAYAN (Alternate)
Central Electricity Authority, New Delhi SHRI D. K. JAIN
SHRI D. K. MALIK (Alternate)
Central Power Research Institute, Bangalore SHRI V. ARUNACHALAM
SHRI V. SHIVAKUMAR (Alternate)
Electronics Regional Test Laboratory (North), New Delhi SHRI ASHOK KUMAR
SHRIMATI MANJULA BHATI (Alternate)
Kalki Communication Technologies Pvt Ltd, Bangalore SHRI PRASANTH GOPALAKRISHNAN
SHRI JOSE THOMAS (Alternate)
Reliance Energy Limited, New Delhi SHRI HARSH S HARMA
SHRI BHUSHAN CHAUDHARI (Alternate)
Siemens Ltd, Gurgaon SHRI VIKRAM GANDOTRA
SHRI GIRISH MULEY (Alternate)
TCE Consulting Engineers Ltd, Bangalore SHRI N. MURUGESAN
Transmission Corporation of Andhra Pradesh Ltd, Hyderabad SHRI M. GOPAL R AO
SHRI K. RAJAMANNAR (Alternate)
32
Bureau of Indian Standards
BIS is a statutory institution established under the Bureau of Indian Standards Act, 1986 to promote
harmonious development of the activities of standardization, marking and quality certification of goods
and attending to connected matters in the country.
Copyright
BIS has the copyright of all its publications. No part of these publications may be reproduced in any form
without the prior permission in writing of BIS. This does not preclude the free use, in the course of
implementing the standard, of necessary details, such as symbols and sizes, type or grade designations.
Enquiries relating to copyright be addressed to the Director (Publications), BIS.
Review of Indian Standards
Amendments are issued to standards as the need arises on the basis of comments. Standards are also reviewed
periodically; a standard along with amendments is reaffirmed when such review indicates that no changes are
needed; if the review indicates that changes are needed, it is taken up for revision. Users of Indian Standards
should ascertain that they are in possession of the latest amendments or edition by referring to the latest issue of
‘BIS Catalogue’ and ‘Standards : Monthly Additions’.
This Indian Standard has been developed from Doc No.: LITD 10 (3061).
Amendments Issued Since Publication
Amend No. Date of Issue Text Affected
BUREAU OF INDIAN STANDARDS

Headquarters:
Manak Bhavan, 9 Bahadur Shah Zafar Marg, New Delhi 110002
Telephones : 2323 0131, 2323 3375, 2323 9402 Website: www.bis.org.in
Regional Offices: Telephones

Central : Manak Bhavan, 9 Bahadur Shah Zafar Marg
NEW DELHI 110002 { 2323 7617
2323 3841
Eastern : 1/14 C.I.T. Scheme VII M, V. I. P. Road, Kankurgachi
KOLKATA 700054 { 2337 8499, 2337 8561
2337 8626, 2337 9120
Northern : SCO 335-336, Sector 34-A, CHANDIGARH 160022
{ 60 3843
60 9285
Southern : C.I.T. Campus, IV Cross Road, CHENNAI 600113
{ 2254 1216, 2254 1442
2254 2519, 2254 2315
Western : Manakalaya, E9 MIDC, Marol, Andheri (East)
MUMBAI 400093 { 2832 9295, 2832 7858
2832 7891, 2832 7892
Branches: AHMEDABAD. BANGALORE. BHOPAL. BHUBANESHWAR. COIMBATORE. DEHRADUN.
FARIDABAD. GHAZIABAD. GUWAHATI. HYDERABAD. JAIPUR. KANPUR. LUCKNOW.
NAGPUR. PARWANOO. PATNA. PUNE. RAJKOT. THIRUVANANTHAPURAM.
VISAKHAPATNAM.
Published by BIS, New Delhi

2011 Reff2020

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

2011 Reff2020

Uploaded by

Copyright:

Available Formats

Free Standard provided by BIS via BSB Edge Private Limited to Saurabh Mr -

Chennai(saurabh.idse@gmail.com) 117.206.122.192 [for non-commercial use only].

ICS 33.040.60;33.200 (Reaffirmed 2009)

October 2011 Price Group 11

Power System Control and Associated Communications Sectional Committee, LITD 10

Master Station Communication Field Site(s)

FIG. 1 M ASTER STATION AND RCCI FUNCTIONAL DATA/C ONTROL FLOW

Local Area Network 

1)2) User Interface

FIG. 2 CONTROL CENTRE FUNCTIONAL BLOCK DIAGRAM

National Control Centre

Regional Control Centre Regional Control Centre

RCCIs RCCIs RCCIs RCCIs

FIG. 3 HIERARCHICAL S ET-UP OF C ONTROL CENTRES

Master Station Links Local User Interface1)

Analog Input Digital Input Analog Output Digital Output Serial

Transducer Pulse Contact Controllers Contact to IEDs

FIG. 4 REMOTE CONTROL AND COMMUNICATION FUNCTIONAL BLOCK DIAGRAM

d) Report-by-exception polling; 4.2.2.1 RCCI data acquisition

4.2.4 Data Processing c) Data processing-by-exception may be a

c) Database update: b) Expandability — Processors/memory/

CONTROL AND DATA DATA MODEM

DTE — Data terminal equipment DCE — Data communication equipment

FIG. 5 S IGNAL INTERFACES BETWEEN CONTROL AND D ATA ACQUISITION EQUIPMENT

CONTROL AND DATA COMMUNICATION

FIG. 6 SIGNAL I NTERFACES BETWEEN CONTROL AND DATA ACQUISITION

Table 1 Operating Temperature and Humidity by Location

Table 2 Test Stages and Classes of Tests

The performance parameters of all critical component 1)

a) RCCI; 9.5 Customized Product versus SCADA Vendor

IS No. Title IS No. Title

IS No. Title IS No. Title

B-1 The following Fig. 7 to 16 are informatory in

FIG. 15 S INGLE M ASTER STATION, M ULTIPLE

FIG. 16 S INGLE MASTER STATION, RCCI(S) AND

C-1 EMI/EMC AND ENVIRONMENT TEST LEVELS OF A TYPICAL TRANSMISSION SUB-STATION

Sl No. Test Name Passing Criteria

SCADA Working Group for Power Sector under LITD 10

Bureau of Indian Standards

Review of Indian Standards

Amendments Issued Since Publication

Amend No. Date of Issue Text Affected

BUREAU OF INDIAN STANDARDS

Regional Offices: Telephones

You might also like

Local Area Network