Disclosure to Promote the Right To Information

Whereas the Parliament of India has set out to provide a practical regime of right to information for citizens to secure access to information under the control of public authorities, in order to promote transparency and accountability in the working of every public authority, and whereas the attached publication of the Bureau of Indian Standards is of particular interest to the public, particularly disadvantaged communities and those engaged in the pursuit of education and knowledge, the attached public safety standard is made available to promote the timely dissemination of this information in an accurate manner to the public.

इंटरनेट मानक

“!ान $ एक न' भारत का +नम-ण”Satyanarayan Gangaram Pitroda

“Invent a New India Using Knowledge”

“प0रा1 को छोड न' 5 तरफ”Jawaharlal Nehru

“Step Out From the Old to the New”

“जान1 का अ+धकार, जी1 का अ+धकार”Mazdoor Kisan Shakti Sangathan

“The Right to Information, The Right to Live”

“!ान एक ऐसा खजाना > जो कभी च0राया नहB जा सकता है”Bhartṛhari—Nītiśatakam

“Knowledge is such a treasure which cannot be stolen”

“Invent a New India Using Knowledge”

है”ह”ह

IS 15654 (2006): Supervisory control and data acquisition(SCADA) system for oil and gas pipeline [LITD 10: PowerSystem Control and Associated Communications]

IS 15654:2006

WV(7%Tqllm

* * h W+-kll{ fi & raqWi*f%mJT*&l-imq*(wmT)m

Indian Standard

SUPERVISORY CONTROL AND DATA ACQUISITION

(SCADA) SYSTEM FOR OIL AND GAS PIPELmE

ICS 33.200; 75.200

0 BIS 2006

BUREAU OF INDIAN STANDARDSMANAK BHAVAN, 9 BAHADUR SHAH ZAFAR MARG

NEW DELHI 110002

April 2006 Price Group 11

Power System Control and Associated Communications Sectional Committee, LTD 25

FOREWORD

This Indian Standard was adopted by the Bureau of Indian Standards, after the draft finalized by the PowerSystem Control and Associated Communications Sectional Cornrnittee had been approved by the Electronicsand Information Technology Division Council.

This standard on SCADA system (Supervisory Control and Data Acquisition) provides guidelines for theperformance analysis and application systems used for supervisory control and data acquisition for oil and gaspipelines covering natural gas, LPG, crude oil, multiproduct, etc, in attended or unattended stations like terminals,sectionalizing valve stations, compressor and pump stations. The system covered by this standard typically useservers, workstations, front end processors in the master stations and in Remote Terminal Units (RTUs)/IntelligentElectronic Devices (IEDs) at the remote stations. The SCADA provides facilities for incorporating monitoringand control finctions in the system installed.

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 withIS 2:1960 ‘Rules for the rounding off numerical values (revisec$’. Tbmunber of significant places retained inthe rounded off value should be the same as that of the specified value in this standard.

IS 15654:2006

Indian Standard

“ SUPERVISORY CONTROL AND DATA ACQUISITION(SCADA) SYSTEM FOR OIL AND GAS PIPELINE

1 SCOPE

1.1 This standard provides guidelines for the definition,specification, performance analysis, and application ofsystems used for supervisory control and dataacquisition for oil and gas pipe lines, in attended orunattended stations like terminals, sectionalizing valvestations, including those associated with compressorstations/pump stations. Systems covered by thisstandard typically use servers, workstations, front endprocessor in the master station and RTU (RemoteTerminal Unit), IEDs (Intelligent Electronic Devices)at the remote stations. Such a system provide facilitiesfor incorporating monitoring and control functions,after the system is installed.

1.2 The oil and gas pipe line include pipelines fornatural gas, LPG, crude oil, multiproduct, etc.

2 REFERENCES

The standards listed in Annex A are necessary adjunctsto this standard.

3 TERMINOLOGY

The definitions of various terms used in this standardshall be as given in IS 12746 (Part l/See 3), IS 1885(Part 50) and all sections of IS 1885 (Part 52).

4 FUNCTIONAL CHARACTERISTICS

The control and data acquisition equipment governedby this standard maybe arranged in various configura-tions, and may perform some or all of the functionsidentified in this clause.

Typically, control and data acquisition equipmentcompose a system with at least one master station andone or more Remote Terminal Units/intelligentElectronic Devices (RTUs/IEDs). Figure 1 illustratesthe possible data and control flow between a masterstation and one or more RTUs/JEDs.

4.1 Typical Equipment Functional Diagrams

Functional diagrams of typical RTU and master stationequipment and configurations are described below:

The links between the master station(s) and RTUS, andbetween the sub-m-aster RTU and its slave RTUS, canbe any suitable communication media but in case of across-country pipeline the same is recommended to

be OFC (Optical Fibre Cable) based dedicatedcommunication system. In case the OFC baseddedicated system is not practical then lease linecommunication network or any other communicationnetwork such as satellite based communication, -radiocommunication, etc, are recommended to be used forcontrol functionality. However if only monitoring ofdata is envisaged at intervals (not in real time) and noreal time control operation is to be performed in thatcase dial-up line can also be used. The communicationprotocol typically used requires a master station toinitiate message transactions. In some cases the RTUcan initiate the communication messages. Foradditional communications protocol information, seeIEC 60870-5-101, IEC 60870-5-104 or DNP 3.0, etc.

The functional components of a master station areillustrated in Fig. 2. A dual server with hot standbymaster station is illustrated in Fig. 2, however, a singleserver master station may be adequate for someapplications. In case of a cross-country pipeline it isrecommended to .go for dual master stations withemergency master station at some different locationto cater to emecgency like fire, etc. However, usermay decide requirement of dual master stationdepending upon complexity and criticality of thepipeline network.

There may be different master stations (regional)collecting data from different pipeline network and acentral master station which is updated with data fromall the other regional master stations so that the entiredata is available at a central place as illustrated inFig. 3.

If the data is required to be viewed from different sitesit is preferable to have WEB enabled system so thatdata can be viewed using intranet. The WEB enabledsystem should have the information security featureslike firewalls, intrusion detection system, etc. Also ifthe control functions need to be executed from differentsites provision should be there for extending remoteworkstations. Separate historyserver may be used forhistorical data recording. Separate application servermay be kept for running different pipeline applications.Auxiliary storage devices may be kept for routinebackup of the system.

If required, a network time server (GPS) can beinstalled to synchronize entire network.

IS 15654:2006

.

~.-.-.----- --------------,1

11

11

Supervisory Controls# 1! Trip/Close

1I 11 Raise/Lower I c1 I1 Open/Close I o1 I1 stop/start I M

Computer (31 :1

Setpoint Values 1 MServers and n : Parameter Download I

CIWork Stations ;t ,

u on REMOTE● Control Programmed 1 N mt TERMINAL

me -+ Instructions Download -+ur : I + me UNIT

nf I● Database Changes 1

1 c ur

ia Download# 1

1 Anf

cc 1ia

● AlarmParameters 1 TSee Fig. 4

ae : Download t ccfor Typical I/O

See Fig. 2 t I1 I aeI

i I1 0

tI

o I i1

nN

. Standard Time Signal +o

1 n1 11 I

I s

4Analog DataI Y

t Accumulator Data I AI 1 sI Digital Data I1 8 T# Status I8 1 Et Alarm 11 I M

Sequence of Events1 11 Serial Data

11 11 Abnormalities

1

:11

,--------------------_--- !

t’-M~ter Station ~ Com&$ion

--i

● Optional feature

FIG. 1 MASTER/RTUFUNCTIONALDATA/CONTROLFLOW

F in’rmetI

# # # # # NetworkPrimary HotServer

History Application WEB TimeStandby Server Server Server ServerServer (GPS)

—

# RemoteWork Stations

* Local Area Network,

A*bxK-1

~ Userj Interface

# * Comm. Controller I

I

Iv

I Work StationsComm. IInterface

I

# Comm. Interfaces

# Optional featureI

● Can be redundantRTUS

FIG. 2 MASTERSTATIONFUNCTIONALBLOCKDIAGRAM

2

IS 15654:2006

I * Central Master ~ Local R’~US/IEDSI Station I

IA

J

v

b Communication Network 4 1

0Regional Master

Q

Regional MasterSTN 1 —.—. — ._ ._. _ ._ ._. _ ._ ._. _ ._ ._. _ STN n

Local RTUs/lEDs LocalRTUsflEDs

FIG. 3 (%wwwzm MASTERSTATIONwml OTHERREGIONALMASTERBLOCKDIAGRAM

The functional components of an RTU are illustratedin Fig. 4. Various interconnections of master station(s)and RTU(S) are illustrated in Annex B.

4.2 System Functional Characteristics

This clause provides guidance for helping both usersand suppliers jointly define the fi.mctional capabilitiesthat may be in a system.

Each generic function is described in terms of theminimum features or characteristics that shall beaddressed to adequately define the function.

When the feature or characteristic is fixed by the designof the equipment, the burden of definition rests on thesupplier (for example, number of inputs/outputs percard). However, variable features (for example, scalingresistors, switch settings, and software) shall be jointlydefined by the user and the supplier.

4.2.1 Communication Management

The requirements to commrmicate between the masterstation(s) and the RTUS shall be -welldefined. See IEC60870-5-101, IEC 60870-5-104 or DNP 3.0 for anexample of the definition of a communication protocol.The topics to be defined include:

a)

b)

c)

d)

e)

Message protocol;

Number of channels;

Channel considerations;

Channel switching;

Number of RTUs per channel and/or channelsper RTU;

-f)

@

h)

j)k)

m)

# Optional feature* Can be redundant

STATIONS

Communication error reporting, failurecriteria, and recovery;

Channel quality monitoring (normal andbackup);

Channel diagnosticltest provisions;

Equipment interfaces;

Report-by-exception pollrng; and

Point scan/RTU scan on demand.

4.2.2 Data Acquisition

The characteristics for each data type shall be defined.Ranges of data input, scale factors, rates, and accuracyshall be defined for the data types to be supportedsuch as:

a)

b)

c)

d)

e)

9

Analog inputs,

Status inputs — two stateStatus inputs — more than two state (morethan two state status inputs are accomplishedby using multiple two state status inputs),

Status inputs — with memory,

Accumulator pulse inputs,

Sequence-of-events inputs, and

BCD inputs-multi-bit.

The data acquisition capability for each data type shallbe defined in terms of the following characteristics:

a) Scan groups — Number of scan groups sizeof each group, points in each group.

b) Scan cycle — Time to complete the acquisitionof a scan group from all remotes on the

3

IS 15654:2006

&

Master Station Links

* CommunicationInterface

Slave RTUS

mm

# User Interface Data Self # Local(Local) Processing Diagnostics 9 orage

I I I + + *PTs, TTs Pulse Contact Controllers Contactto IEDs

4.2.2.1

Inputs fromSwitches

etc.

FIG.4 REMOTETERMINALUNIT

communication channel. The communicationhardware related performance capabilities usedin the calculation of scan cycle shallbe defined.

RTU data

The capacity (total inputs) and rate of acquisition(inputs per second) for field data interfaced to the RTUequipment shall be defined for all applicable data types(see 5.4).

The modularity (for example, minimum number ofinputs per card) of each data type shall also bespecified.

4.2.2.2 Master station data

The capacity (total inputs) and rate of acquisition(inputs per second) for local or RTU data interfaced tomaster station equipment shall be defined for allapplicable data types (see 5.4).’

4.2.3 Data Processing

Data processing capabilities shall be defined for eachequipment item and all applicable data types. Systemswith report-by-exception functions shall have thecapability to report all data for initialization andperiodic update purposes.

4.2.3.1 Analog data

Analog data is used to describe a physical quantity (that

Switches/Controldevices etc.

# Optional feature* Can be redundaot

FUNCTIONALBLOCKDIAGRAM

is, pressure, temperature, flow density, specific gravity,etc) that normally varies in a continuous manner.

The analog data processing options to be supportedat both the master station and the RTU shall bedefined. This is the responsibility of both the userand supplier. Particular attention shall be given toinput data validity processing (for example, thevalidity of the data) and to the interface between thesupervisory control function and the analog dataprocessing fi.mction.

a) Data input scaling shall give adequateconsideration to off-normal operation of thesystem (for example, pressure out of range).

b) Data change detection may be a functionincluded as an alternative to processing everyinput on every scan. Data change detection isaccomplished by testing to see if the newvalue for each input is within N digital counts(for example, dead band) of the last storedvalue for that input. The new value shallreplace the last stored value only if thedead band was exceeded and then the inputwill be flwther processed as defined below.When the data change detection function isincluded, the following characteristics shallbe defined:

Location of processing, RTU or masterstation, .or both.

c)

d)

e)

f)

g)

4.2.3.2

Data filtering may be required to smooth databefore it is used by other fimctions. When thisfimction is included, the equation used shallbe defined and the time delay, introduced bythe filtering, specified.

Data limit checking is typically included todetermine if other downstream functions,such as alarm detection, or fin-therprocessingare required. The number of high or low limitsaccommodated and associated return-to-norrnal dead band processing shall be defined.Specific attention shall be given to theprocedure for user specification and revisionof limit and dead band values.

The data r~port-by-exception fimction is usedto eliminate communication of unchangeddata from the RTU(S) to the master station.Its input is received from the change detectionfhnction. When the analog data report-by-exception fiction is included the fo}lowingcharacteristics shall be defined:

1) Percent of analog changes per scan thatresults in the channel load associated withreporting all analog points horn the RTU.

2) Description of logic in the master stationthat can be used to select between usingthe analog data report-by-exceptionfunction or report-all-analog datafunctions when acquiring analog datafrom each RTU.

Data conversion to engineering units istypically required before analog data is usedby other software, printed, or displayed asoutput. The mathematical equation(s) used toconvert analog values represented by digitalcounts into the corresponding engineeringunits shall be defined. Specific attention shallbe given to sensor and transducer scale factorsthat may be provided by the user.

Bad data techniques shall be defined that areused to:

1) Detect an open input to an analogchannel,

2) Identi@ reasonable values,

3) Detect a drifted or faulty AiD converter,and

4) Automatically calibrate an analogchannel.

Status data

Status data is used to describe a physical quantity (forexample, device position) that has various possiblecombinations of discrete states. The informationcontent of a digital signal is expressed by discrete states

IS 15654:2006

of the signal such as the presence or absence of avoltage, current, or a contact in the open or closedposition.

The status data processing options to be supported atthe master station and the RTU shall be defined. Thisis the responsibility of both the user and supplier.Particular attention shall be given to input data validityprocessing, and to the interface between thesupervisory control function and the status dataprocessing fiction:

a)

b)

c)

Data change detection may be a functionincluded as an alternative to processing everyinput on every scan. Data change detection isperformed by testing to see if the current stateis the same as the last stored state for thatinput. Changed data shall replace the laststored value and the point, or group of inputs,shall be routed to other fhnctions such as datareport-by-exception, alarm processing, orboth. When the data change detection functionis included, the following characteristics shallbe defined:

1) Location of processing (RTU or masterstation),

2) Quantity of data reported when a singleinput changes,

3) Minimum signal duration to beconsidered a change, and

4) Security agarnst loss of change data.

Data report-by-exception fhnction is used toeliminate unnecessary communication ofunchanged data fi-omthe RTU(S) to the masterstation. Its input is received from the changedetection furrction. When the status datareport-by-exception function is included, thefollowing characteristics shall be defined:

1)

2)

Percent of status point changes per scanthat result in the channel load associatedwith reporting all status points fi-om theRTU.

Description of logic in the master stationor RTU that can be used to select betweenusing the status report-by-exception orthe report all status data function whenacquiring status data fi-omeach RTU.

Statu# with memory may be a functionimplemented in the RTU. When this functionis included, the number of status changesaccommodated and legal bit combinationssupported by the design shall be defined.

4.2.3.3 Accumulator data

The following characteristics shall be defined when

5

IS 15654:2006

pulse accumulation and/or accumulator data processingis included:

a)

b)

c)

d)

e)

f)

g)

Input circuit (two or three terminal arid howinput circuit operates);

Sources of freeze comand, if any (intematiexternal);

Ranges of values (RTU and master station);

Nominal and maximum counting rates;

Source of memory power;

Input voltage, if externally powered; and

Reset command (if any).

4.2.3.4 Sequence-of-events {SOE) data

The following characteristics shall be defined whenSOE data acquisition capability is included:

a)

b)

c)

d)

e)

o

g)

h)

~)

k)

Time resolution at RTUS;

Method of system time s~ckonization;

Time accuracy between any two RTUS;

Number of SOE inputs per RTU;

Size of buffers (number of SOE events thatcan be stored) per RTU;

Time (minimum/maximum) betweensuccessive change(s) of an input

Method of indicating that SOE data isavailable at the RTU;

Data filter time constant and accuracy (forexample, contact de-bounce);

Data time skew (introduced by de-bouncefilters); and

Number of SOE events that can be transferredto the master station in one communicationstransaction.

4.2.3.5 Computed data

The followhg characteristics shall be defined whenthe capability of computing data (which are not directlymeasured) is included:

a) Location (RTU or master station);

b) Equations supported;

c) Resulting data types (numeric or logical, orboth); and

d) Downstream functions (for example, limitchecking).

4.2.3.6 Alarm data

The following characteristics shall be defined whenthe capability to process and report alarm conditionsis included:

a)

b)

Conditions reported as alarms;

Methods of acknowledgment (single orgroups);

6

c)

d)

e)

f.)

!3)

h)

Methods of highlighting alarms (for example,flash, tone, etc);

Information in alarm messages;

Hierarchy of alarms (priority level);

Size of alarm queue(s}

Queue management (for example, timeordered} and

Alarm lfiit(s).

4.2.3.7 Digital fault data

The RTU(S)and their micmcompu&rs are sop~lsticatdenough that they can monitor variations in data at sucha rate as to be able to record data for pre-fault, fault,and post-fault analysis. The following characteristicsshall be defined when the capability to process andreport digital fault data is inchided

a) Samples,

b) Number of data points per fault,

c) Maximum buffer size (total samples to bestored),

d) Sample triggers,

e) Number of faults to be reported and stored,and

f) Means of reporting digital fault data.

4.2.4 Supervisory Contro[ Characteristics

When the capability to remotely control externaldevices and processes is provided, the characteristicsof such a control capability shall be defined (see 5.4).Definition of characteristics common to all control’interfaces shall include following and a time out alarmalso in case control is not executed:

a)

b)

c)

d)

e)

f.)

Control sequence description,

Type of checklsack messageencoded),

Security of control sequences,

Immediate operate controls,

Broadcast controls, and

Time out alarm.

(echo or re-

4.2.4.1 Equipment control with relay interface

Control using a relay output shall be defined as follows:

a)

b)

4.2.4.2

Dwell time of relay contacts; and

Number of relays that can be simultaneouslyenergized in each type of”RTU processingactions (for example, logging and alarmsuppression),

Equipment control with setpoint interface

ControI using a setpoint output shall be defined asfollows:

a) Resolution of setpoint value;

b) Duration of output value;

c) Processing actions (for example, limit check,equation, and alarms); and

d) Electrical interface.

4.2.4.3 Equipment/Process control with electronicinterface

Control using an electronic interface shall be definedas follows:

a) Timing diagram of signals;

b) Interface communication protocol;

c) Processing actions associated with control;and

d) Physical interface.

4.2.5 Automatic Control Functions

When the capability to automatically control externaldevices provided the characteristics of such controlcapabilities shall be defined as follows:

a)

b)

c)

d)

e)

f)

g)

Location of automatic control logic (RTU ormaster station);

Control equation(s);

Feedback value and accuracy, if closedloop,

Frequency of execution;

User alterable control parameters;

Associated logging or alarming; and

Method of altering control logic.

4.2.6 User Interface Characteristics

User interface functions shall be defined when thecapability to support operating or maintenancepersonnel at the master station. The interface fictionsshall be defined-in 4.2.6.1 to 4.2.6.4.

4.2.6.1 Control of equipment fimctions

When operator controllable functions are included theapplicable characteristics shall be defined for theincluded fimctions, such as:

a) Control output options

1) Enable/disable,

2) Tagging (types and uses),

3) Local/remote, and

4) Open (off)/.c1ose (on).

b) Control of data acquisition

1) Enable/disable scan (inputs or stations),

2) Enable/disable processing,

3) Manual entry of data,

4) Change scan frequency by group, and

IS 15654:2006

5) Assignhe-assign data to a group.

c) Control of data processing

1)

2)

3)

4)

5)

6)

Setting date and time,

Setting input change limits,

Defining formats,

Defining conversion data,

Defining operator override values, and

Defining normal/abnormal status/dataquality status.

d) Control of alarm processing

1)

2)

3)

4)

5)

6)

7)

8)

9)

10)

Enable/disable individual alarms,

Enter/edit alarm limit value(s),

Enter/edit alarm dead band value(s),

Enter/edit return-to-normal criteria,

Enter/edit alarm assignment to area ofresponsibility,

Enter/edit alarm priority,

Acknowledge alarmspage),

Silence audible alarm,

Inhibit alarms, and

Override invalid alarms.

[“individual/

e) Control offunction checks

1) Enable/disable, and

2) Change fi-equency.

i) Control ofautomatic control functions

1) Enable/disable,

2) Modify criteria,

3) Ad&delete control fimctions, and

4) Reset to reference level or position.

4.2.6.2 Display functions

The applicable characteristics shall be defined whenthe following formats are included:

a) Generation of display formats

1)

2)

3)

4)

5)

6)

Format definition capabilities,

Use of colours,

Use of special features (flash, reversevideo, etc),

Control level of detail (declutter),

Display call-up time, and

Use of features (pan, zoom, windowing,etc).

b) Standard formats

1)

2)

3)

4)

5)

Index formats,

System formats,

Communication channel format,

Summary of inhibited alarms,

Input point profile formats,

7

IS 15654:2006

6) Alarm SUIIUIWJJ,

7) Tag summary,

8) Abnormal summary,

9) “Override summary, and

10) Station notes format.

c) Control of cursor

1) Cursor operation,

2) Selection of formats,

3) Response time,

4) Update cycle (from database),

5) Paging of multi-page formats, and

6) Selection of declutter (zoom) levels.

4.2.6.3 Digital and analog display functions

When such display devices are supported the applicablecharacteristics shall be defined as follows:

a) Digital displays

1) Numeric range with decimal, and

2) Update frequency.

b) Analog displays

1) Ranges, and

2) Update frequency.

4.2.6.4 Hard copyjimctions

When support of hard copy devices is required suchas logger-s, video copiers, etc, the applicablecharacteristics shall be defined as follows:

a) Device assignments

1) Initial,

2) Automatic re-assignment, and

3) Manual re-assignment.

b) Generation of log formats

1) On-line/batch capabilities,

2) Symbols supported, and

3) Spooling capabilities.

c) Demand logs

1) Standard/Customised formats, and

2) Time for response.

d) Logged activities

1) Alarms;

2) Standard events (for example, user anddevice actions);

3) System events (for example, equipmentfailover and communication failure); and

4) Output ii-em diagnostic routines.

e) Device performance

1) Print speed (characters/second),

2) Print quality (dots/inch), and

3) Colour requirements.

4.2.7 Sub-master RTU

An RTU can act as a master station with respect toother slave RTU(S) and Intelligent Electronic Device(s)[IED(s)]. The master station functions allocated to suchsub-master RTU shall be defined using the applicablepreceding subclauses. This is the responsibility of boththe user and supplier. The user shall define theapplicable characteristics as follows:

a)

b)

c)

d)

e)

f.)

Database,

Communication protocol,

Point configuration,

Scan interval,

Downloading characteristics, and

Other characteristics defined in this standardthat may be applicable.

4.2.8 Backup and Failover

It is common practice today to failoyer a system byswitching peripherals or the total computer subsystemin order to recover from a peripheral or computerfailure. In a distributed computer implementation,functions may be re-allocated to recover from ahardware failure. The applicable characteristics shallbe defined when both primary and backup facilitiesare provided as follows:

a) Database backup

1) Data residency (bulk or main memory),

2) Frequency of backup (by data type), and

3) Other uses of backup facilitie-s.

b) Database update

1) Data residency (bulk or main memory),

2) Frequency of update (by data type), and

3) Other uses of update facilities.

c) Failure monitoring

1) Method of failure detection,

2) Response time for detection, and

3) Effect on a programme or task in progresswhen fail over occurs.

d) Failover

1)

2)

3)

4)

5)

Method of failover,

Time required for failover,

User interface response followingfailover,

User actions following failover, and

Effect on a programme or task in progresswhen failover occurs.

4.2.9 Historical Data

The appropriate characteristics shall be define whenthe capability for historical data archiving and retrievalis included as follows:

8

a)

b)

c)

d)

e)

o

g)

Data quantities,

Data intervals,

Number of data intervals,

Method of file management,

Method of data archiving,

Method of data retrieval, and

Data usage (for example, displays, reports,applications, etc).

4.2.10 Local Networks

Local area networks may be used to provide dataexchange capability between the different fimctionsat a site (for example, IEDs, RTUS, etc), When thecapability of a local area network is included, thecharacteristics of such communication capability shallbe defined as follows:

a)

b)

c)

d)

e)

o

g)

Bit rate,

Electrical interface (for examule. 10/100 BaseT, RS-232, RS-485; etc), ‘ ‘

Equipment to be interconnected,

Transfer rate (bytes per second),

Protocols (for example, Ethernet,etc),

Redundancy, and

TCP/IP,

Reliability (for example, sectionalizing forisolating failures).

4.2.11 Third Party Interface

The system should be compliant with user defined openinterface like ODBC (Open Data Base Connect), -etcfor the integration of third party softwarehrdware.

ElectricalPowerInterfaces(see 5.3)

User Interfaces(see 5.6)

IS 15654:2006

5 INTERFACES

The control and data acquisition equipment shall haveinterfaces as described in this clause. The interfacesdescribed crmsist of those illustrated in Fig. 5.

5.1 Mechanical

5.1.1 Enclosures

Equipment enclosures shall be suitable for the proposed. .environment. Enclosures should therefore conform tothe relevant “1PClassification tests as per IS 13947(Part 1).

5.1.2 Electromagnetic Compatibility (EA4C) andSpecial Requirements

The location of access doors, enclosure mountingrequirements, temperature/ventilation requirements,terminal-block type and location, cable entry locations,and special cabling and connector requirements shouldbe specified for individual applications.

Electromagnetic Interference (EMI) and RadioFrequency Interference (RFI) characteristics ofenclosures should be determined in conformancewith IEC 60870-2-1 (1995) for minimum level 2requirements.

5.2 Grounding

Control and data acquisition equipment shall notground a floating power source. Care shall be exercisedto ensure ground compatibility when grounded powersources are used. The code of practice for earthing maybe referred as given in IS 3043 and IEEE Green BookStandard 142:1991.

GroundingInterfaces(see5.2)

CONTROL ANDDATA ACQUISITION

EQUIPMENT

1

Data.andControlInterfaces(see5.4)

CommunicationInterfaces(see 5.5)

1- MechanicalInterfaces(see 5.1)

FIG. 5 MANUALANDSUPERVIS13RYCONTROLEQUIPMENTINTERFACEBLOCKDIAGRAM

9

IS 15654:2006

5.2.1 Safety or Equipment Ground

The safety or equipment ground protects personnelfrom injuries caused by live or hot conductors comingin contact with the equipment cabinet or enclosure.The ground conductor shall be bundled with the powerconductors, but be insulated from the power conductorsand from other equipment and conduit. The groundconductor is usually terminated in the cabinetenclosure, and grounded only at the same point thatthe electrical service or UPS neutral is grounded. Allcabinets andlor enclosures comprising any control ordata acquisition equipment shall be grounded togetherby means of a ground cable or strap.

Any buildings or allied structures for keeping allcabinets and/or enclosures comprising any control ordata acquisition equipment shall be protected fi-omlightening and code of practice for protection againstlightening may be referred as given in IS 2309.

Additionally, metal decking or other electrical pathsshould be grounded only at the same point that theelectrical service or UPS is grounded. Safety orequipment grounds shall be established in accordancewith SP 30.

5.2.2 Signal or Instrumentation Circuit Ground

The signal or instrumentation circuit ground shall beconnected to an external ground at a single point sothat ground loop conditions are minimized. Theshielded wire, drain wire, and/or ground wire of input/output cables shall be terminated at one ground pointin each cabinet. These ground points shall beconnected together and connected to the facilityground. Caution shall be used to prevent inadvertentground paths from devices such as convenienceout lets, conduit, structural metal, test equipment, andexternal interfaces.

A special caution on filtering is worth noting. If thenoise is shunted to the signal ground, then it becomesanother source of signal reference corruption.Sometimes separate power, noise, digital, and analogground buses are necessary. However, the NECrequirement for a single point safety grounding sourceshall always be met. Avery important design rule istokeep all signal reference voltages, at all frequencies ofoperation, as close to zero as possible (that is, at zerovoltage signal reference):

5.2.3 Electrical Ground

The station power source shall be grounded inaccordance with the NEC.

5.3 Electrical Power

The electric power interfaces to control and data

acquisition equipment shall meet the followingrequirements:

a)

b)

The alternating current source defined belowmay originate directly from the station sourceor from a regulatinghminterruptible powersupply.

Equipment operating on direct current shallnot sustain damage if the input voltagedeclines below the lower limit specified-or isreversed in polarity.

5.3.1 Master Station

Master station equipment shall be capable of operatingwithout error or damage with one or more of thefollowing source voltage ranges:

a) 230 V ac single phase or three phase +10percent at 50 Hz +3 percent,

b) 21 to 29 V dc (24 V dc nominal), and

c) 42 to 58 V dc (48 V dc nominal).

5.3.2 Remote Station

Remote station equipment shall be capable of operatingwithout error or damage with one or more of thefollowing source voltage ranges:

a) 230 V ac single phase +0 percent at 50 Hz*3 percent,

b) 21 to 29 V dc (24 V dc nominal),

c) 42 to 58 V dc (48 V dc nominal), and

d) 10to 16 V dc (12 V dcnominal).

5.3.3 Power Quali~

Station power shall be of such quality (freefkom noise,spikes, etc) to be suitable for use as a source to elec-tronic equipment. The user and supplier shall both beresponsible for conditioning (as required) the electricpower for use by SCADA equipment. The one end ofac power supply to master station for SCADA systemshould be grounded with isolating transformer.

5.3.4 Internal Noise

The control and data acquisition dquipment internallygenerated electrical noise, ffom 1000 to 10.000 Hz,appearing on the power source terminals shall be lessthan 1.5 percent (peak to peak) of the external powersource voltage. This is measured into an external powersource impedance of 0.1 cominimum.

5.4 Data and Control Interfaces

Data and control interfaces consist of electricalinterconnections between control and data acquisitionequipment and the device being monitored andcontrolled. Two types of signal paths are defined asfollows:

10

IS 15654:2006

a) Data paths — Inputs to data acquisition orsupervisory control equipment, and

b) Control paths — Outputs from dataacquisition or supervisory control equipment.

For each input (data) or output (control) path, varioussignal characteristics shall be defined to speci~ theinterfaces between equipment.

Data and control signal cabling, which are external tocontrol and data acquisition equipment, are not specified.

5.5 Communication

5.5.1 Master StatiotiRTU Links

Communication interfaces consist of functional,mechanical, and electrical interconnections betweencontrol and data acquisition equipment and thecommunication apparatus. Any specific applicationrequires one of the two following types of generalsignal interfaces.

Signal interfaces between the control and dataacquisition equipment and the data communicationequipment (for example, a data modem) occurwhenever the data communication equipment is notpackaged as an integral part of the control and dataacquisition equipment, as illustrated in Fig. 6.

Signal interfaces between the control and dataacquisition equipment and a communication channelare illustrated in Fig. 7.

Subsequent clause define specific signal characteristicsfor these mentioned interfaces. However, one of thecharacteristics is common to both types of interfacesand shall be measured regardless of the configurationutilized. This characteristics is;

Channel bit error rate is measured between datacommunication equipment and control and dataacquisition equipment. Due to the variety ofchannel and modem qualities available and in use,an average value of 1 bit error in 10s bit isrecommended for design and analysis purposes.

5.5.2 Sub-master/Slave RTU Links

The sub-master/slave RTU links shall consist of at leastone communication link to a master station as well asat least one additional link to slave RTUS, or a link toa distributed RTU module of the same RTU, or a linkto an Intelligent Electronic Device (IED).

5.5.2.1 Sub-master RTUS

The communications link(s) to the master station(s) is.,identical to that described’ in 5.5.1.

DATACONTROL AND DATA COMMUNICATION COMMUNICATION

ACQUISITION EQUIPMENT (2) CHANNEL (3)EQUIPMENT (1) (data modem)

NOTESI This equipment is called data terminal equipment (DTE) in the standards referenced.

2 This equipment is commonly called a data modem, but called data communication equipment (DCE) in referenced standards.

3 Channel includes microwave, radio, cable, fiber optic types, etc.

FIG. 6 SIGNALINTERFACESBETWEENCONTROLANDDATAACQUISITIONEQUIPMENTAND DATA COMMUNICATIONEQUIPMENT

CONTROL AND DATAACQUISITION

COMMUNICATION

EQUIPMENT (1) CHANNEL (2)

NOTES1 Data modem is packaged as an integral part of this equipment.

2 Channel includes microwave, radio, cable, fiber optic types etc.

FIG. 7 SIGNAL INTERFACESBETWEENCONTROLAND DATA ACQUISITIONEQUIPMENT

AND COMMUNICATIONCHANNEL

11

IS 15654:2006

5.5.2.2 Remote terminal units

The communication links to slave RTUS is similar tothat described in 5.5.1, except that the role of the masterstation is assumed by the sub-master RTU.

5.5.2.3 IEDs

The interface described in 5.5.1 is typical. Theseinterfaces vary among IED suppliers and thereforecoordination and specific definitions may be requiredwhen interfacing with IEDs. Further, the user iscautioned that the master station RTU protocol maynot-support the-acquisition-of datr.fiom,and thecontrolof, the IEDs.

5.6 User Interface (UI)

The user interface is defined as the user contact withthe control and data acquisition equipment.

The user interface for operation concerns standardsand recommendations for information displays, controlcapabilities, colours, and user interaction with theequipment and is given below.

5.6.1 Information Displays

Characters used by printers, loggers, and illuminateddisplays shall have unique codes so that their displaymay be electrically initiated. The alphanumericcharacters and their corresponding codes as defined inIS 10315 shall be used to represent alphanumeric dataat the user interface. A set of graphic symbols shall bepart of the system. The capability to create additionalgraphic symbol and graphics by the user is to beprovided.

5.6.2 Control Capabilities

The capabilities provided for operator inputs at the userinterface are defhed as the control capabilities. Thecontrol capabilities may include a combination of thefollowing:

a)

b)

c)

d)

e)

Keys and switches (alphanumeric or fimction,or both);

Cursor (mouse, trackball, joy stick, or keycontrolled);

Light pen;

Poke points (defined monitor displayedcontrol selection fields); and

Pull down or pop upmenus.

The user’s input to the UI equipment shall berecognized and acknowledged (valid or invalid) to theoperator within 0.5s. The UI equipment shall confirmcontrol actions using the reencoded checkback messagefrom the RTU within 2 s.

When labelled fbnction push buttons are included in

12

control and data acquisition equipment, the labels shallbe legible from a distanceof approximately 1 m in theuser specified environment. When lighted push buttonsare included, the significance of the state of the light(on, off, blinking) shall be clearly defined and shall beconsistent throughout the system.

Control push buttons (for example raise, lower, trip,open, and close) shall be within convenient viewingdistance of the information display that will be usedduring the control operation.

5.6.3 Colour Codes

The standard meanings for colours (for example,monitor displays, status lights) used at the UI tohighlight the condition of device monitored andcontrolled through control and data acquisitionequipment shall be defined by users.

The significance of colours shall be consistentthroughout the system.

The color status of a device under operator control shallonly change to its new state (may include attributessuch as CO1OWand shape change, flashing, etc) aflerthe status of the device has changed.

5.6.4 Interactive Dialogue

The activity at the UI during operational use of controland data acquisition equipment shall be clearly describedand shall be consistent throughout the system.

5.6.5 Alarms

When alarm conditions detected by control and dataacquisition equipment are first interfaced to the user,both an audible (voice, tone, or bell) -and visual(flashing light or symbol) annunciation shall bepresented. It shall be possible to silence the audiblealarm without affecting the visual annunciation. Thevisual indication of each alarm condition shall remainas long as the alarm condition exists.

5.6.6 Dialogue During Control

The selection of a point for a user control action shallresult in a visual feedback at the user interface. Thispositive feedback to the user shall signifi that thecontrol and data acquisition equipment is ready toaccept a control action. The results of the control action(check-before-operate or direct operate) shall bedisplayed only after a status change has been receivedfrom the RTU equipment.

6 ENVIRONMENTAL CONDITIONS

This clause contains a definition of the environmentin which control and data acquisition equipment isrequired to operate.

IS 15654:2006

There are unusual conditions that, where they exist,shall receive special consideration. Such conditionsshall be brought to the attention of those responsiblefor the application, manufacture, and operation of theequipment. Devices for use in such cases may requirespecial construction or protection. The user shouldspeci& those special physical requirements that applyto specific locations. Examples are:

a)

b)

c)

d)

e)

o

i%)h)

j)

k)

Damaging fumes or vapours, excessive orabrasive dust, explosive mixtures of dust orgases, steam, salt spray, excessive moisture,or dripping water;

Abnormal vibration, shocks, or tilting;

Radiant or conducted heat sources;

Special transportation or storage conditions;

Unusual space limitations;

Unusual power limitations;

Unusual communication limitations;

Unusual operating duty, frequency of operation,difficulty in maintenance;

Altitude of the operating locations in excessof 1000 m,

Abnormal electromagnetic interference; and

m) Abnormal exposure to ultraviolet light.

6.1 Environment

6. L 1 Ambient Temperature and Humidi~ Conditions

Ambient temperature and humidity are defined as theconditions of the air surrounding the enclosure of theequipment (or the equipment itself, if it uses open rackconstruction) even if this enclosure is contained inanother enclosure or room.

For temperature and humidity parameters by operatinglocation, see Table 1. This table is a guideline toestablish five equipment classification groups.Equipment designated to “be in a specific group shallmeet all conditions set forth in that group.

Equipment subjected to temperature and humidityvariations outside of the first four group classificationslisted in Table 1 will require special consideration.Methods to resolve these problems include thefollowing:

a)

b)

c)

d)

e)

Low temperature — A thermostaticallycontrolled heater strip should be used in thecabinet enclosure or use wide temperaturerange equipment.

High temperature — A sun shield, some othercooling method, or wide temperature rangeequipment should be used.

High hurnidi~ — Heater strips or specialshelters should be used.

Low humidip — A humidifier should be usedto maintain acceptable humidity levels.

“Temperature.restrictions — If it is necessaryto use heating/cooling equipment to meet theparameters set forth in Table 1, the equipmentshould be so marked by a warning sign anda warning statement in the associateddocumentation.

6.1.2 Dust, Chemical Gas and Moisture

Suppliers shall be made aware of the presence ofatmospheric pollutants so that special provisions forprotection can be made where necessary.

Tabte 1 Operating Temperature and Humidity by Location

(Clause 6.1. 1)

S1 Equipment TypicalLocationofthe HumidityOperating Temperature AllowableRateofNo. Group Equipment Range(percent OperatingRange ChangeofTemperature

RelativeHumidity) ‘JC Ocnr

(1) (2) (3) (4) (5) (6)

O (l)(a) Ina buildingwithair-conditioned 40-60 +20to+23 5areas

ii) (1)(b) In a building with air-conditioned 30-70 +15to +30 10areas

iii) (2) In a building with heating or 10-90 +5 to +40 10cooling but without full air- without condensationconditioning

iv) (3) In a building or other sheltered 10-95 0 to +55 20area without special without condensationenvironmental control

v) (4) Outdoors or location with wide 10-95 -25 to +60 20temperature variations without condensation

vi) (5) Extremes outside the above User to specify User to specifi User to specifj(see 6.1.1) (see 6.1.1) (see 6.1.1)

13

IS 15654:2006

In groups(l), (2), and(3) of Table l, all equipmentcabinets that are vented shall have dust filters. Ingroups (3) and (4), equipment that is exposed tomoisture, corrosive and explosive gases, or otherunusual environmental conditions shall have a specialenclosure. Available types of enclosures for variousconditions are specified in IS 13947 (Part 1).

Consideration should be given to possiblecontamination inside the enclosure during storage andtransit, and also when the enclosure is opened formaintenance or repairs.

6.1.3 Altitude

The equipment shall be suitable for operation ataltitudes up to at least 1000 m.

6.1.4 Ultraviolet (UV) Light Exposure

Suppliers shall be made aware of the expected level ofexposure to ultraviolet radiation attributable to sun-light where equipment is to be installed outdoors.Equipment cabinets, paint finishes, and jacket materialof any exposed cabling shall be sufficiently treated toresist damage or degradation due to UV exposure. Theuser shall supply information pertaining to altitudeabove mean sea level and the anticipated average dailyhours of direct exposure to sunlight.

6.2 Lightning and Switching Surge Protection

The purpose of this subclause is to describe designcriteria and recommend practices that will minimizethe adverse consequences of exposure to lightningdischarges and switching surges. Effective protectioncan only be accomplished through a combination ofadequate design and proper installation and should bein conformance with IEC 60870-2-1 for minimumlevel 2 requirements.

6.2.1 Design Criteria

The basic design goal for achieving protection fi-omlightning and switching surges shall be that of keepingany abnormal voltage or current, or both, out of theequipment cabinets.

6.2.1.1 Voltage surges

Voltage surges can enter the cabinet and cause damage.Equipment failures resulting fkomsuch damage shouldbe fail-safe. Logic designs should be such as tominimize the possibility of false or improper operationof field devices. Partial failures that do not disable theequipment but can reduce or eliminate securityfeatures, such as error checking in communication cir-cuits, shall be detected and cause the blocking ofcontrol outputs to prevent false operations of fielddevices.

6.2.2 Installation Criteria

The basic installation goal for achieving protectionfrom lightning and switching surges shall be tominimize the exposure of all connecting wires andcables.

6.2.2.1 Power, signal and communication circuits

Power, signal, and communication circuits provide apath through which lightning and switching surgesenter equipment. Circuits totally within a protectedbuilding can generally be installed without regard tothese external effects. These circuits may still besubjected to transients generated by the operation ofsolenoids and control relays. Circuits that are connectedto, or are part o~ circuits not within a protected buildingshould be installed in a manner that will minimizeexposure.

6.2.2.2 Installation constraints

When installation constraints result “ina high degreeof exposure to lightning or switching surges, supple-rnentaryprotection such as spark gaps orsurge limitersshould be considered.

6.3 Electromagnetic Interference (EMI) andElectromagnetic Compatibility (EMC)

Manufacturers shall design and test their equipmentto ensure that EMI limits are not exceeded, and usersshall design and test locations (environments) to ensurethat EMC limits are not exceeded and should be inconformance with IEC 60870-2-1 for minimum level 2requirements.

Computer and microcomputer-based equipment areexpected to perform their intended functions insubstations even when exposed to transientelectromagnetic interference. The user should be awareof EMI in control rooms/substations, metering stations,etc and either specify the EMI level for guaranteeingproper operation or accept the risk of misoperation inthe presence of EMI.

6.3.1 EMI Limits

Control and data acquisition equipment shall notgenerate radiated emissions-in excess of (1 V/m)/MHzas measured 1 m from the enclosure. Manufacturersshall mechanically and electrically design equipmentsfor emission limits by employing attenuationtechniques such as isolation, shielding, grounding,gasketing, filtering, and bonding.

6.3.2 EMC Limits

Control and data acquisition equipment shall becapable of operating in radiated fields as specified bythe user. Information available to date indicates that

14

IS 15654:2006

the average field strength may run in the order of(1 V/m)/MH~. The specified value of (1 V/M)/MHzrefers to broadband radiated fields due to stationenvironment, resulting from such things as corona andswitching transients. This requirement is not intendedto cover narrowband radiated field sources such aselectronic test equipment or portable radio transmitters(walkie-talkies). Where such equipment may be used,the field strength is properly expressed as volts permeter at a specified frequency, and different EMClimits may be required.

7 CHARACTERISTICS

This clause defines and discusses generalcharacteristic-s that are required of the control and dataacquisition equipment. These characteristics includereliability, maintainability, availability, security,expandability, and changeability.

7.1 Reliability

Mathematically, reliability is the probability that a unitor system will perform its intended function underspecified conditions during a specified period of time.For complex equipment, failures will occur on theaverage at a constant rate throughout the usefid life ofthe equipment. This allows the manufacturer to char-acterize equipment reliability with a simple figure ofmerit called mean-time-between-failure (MTBF).

The exceptions to this constant failure rate area higher,decreasing failure rate, early in the equipment’s life,called ‘infant mortality’, and a higher, increasingfailure rate, thatsignals the onset of ‘end-of-life’. Thesephenomena give a typical plot of failure rate versustime, a shape known as a ‘bathtub curve’.

The failure modes of equipment, andthe effects of thesefailures shall be formally analyzed by the supplier. Theresults of these failure modes and effect analysis(FMEA) shall be available for review upon request.

Failure distribution versus time data for equipmentwhile in the possession of the supplier, and for thosefield units for which data are available from the users,shall be documented and available upon request.

7.2 Maintainability

Control and data acquisition equipment shall bemaintainable on-site by trained personnel accordingto the maintenance strategy specified by the user.Requirements for training, documentation, spares, etc,shall take the user’s organization and geography intoaccount.

The most common repair strategy is for the supplier totrain the user’s personnel to identi~ and replace failedmodules on-site.from the user’s stock of spare modules.

These may then be either returned to the supplier forrepakor repaired to the component level at the user’smaintenance facility. If on-site service by the supplieris necessary, it is most likely to be required for failuresof complex com_puterequipment.

The supplier shall, upon request, be required to provideas part of the system proposal, a list of test equipmentand quantities of spare parts calculated to.be necessaryto meet the specified availability and maintainabilityrequirements. In establishing the quantities of spareparts, the supplier shall consider the time required toreturn a failed component (field and/or factory service)to a serviceable condition.

The maintainability of equipment is reflected in a figureof merit called mean-time-to-repair “(MTTR). TheMTTR values used in the supplier’s availabilitycomputations shall be based to the maximum extentpossible upon maintenance experience.

MTTR is the sum of .administrative, transport, andrepair time. Administrative time is the time intervalbetween detection of a failure and a call for service.Transport time is the time interval between the call forservice and on-site arrival of a technician and thenecessary replacement parts. Repair time is the timerequired by a trained technician, having thereplacement parts and the recommended test equipmenton-site, to restore nominal operation of the failedequipment.

Unless otherwise specified by the user, the followingvalues shall be used in availability calculations:

Administrative time 0.0 h

Transport time 0.5 h

7.3 Availability

Availability is defined in the following as the ratio ofuptime to total time (uptime + downtime):

A = uptime/(uptime + downtime)

and is normally expressed as a percent (of total time).

Downtime normally includes corrective and preventivemaintenance. When system expansion activitiescompromise the user’s ability to operate device via thesystem, this may also be included in downtime.

Typical availabilities achievable by non-redundantcommercial grade equipment range from 99.99percent, for simple devices, to approximately 97percent for complex, computer-based sub-systems.Proper use of redundant configurations with automaticfail over can provide an overall availability of primarysystem functions of 99.9 percent.

The availability level required, and the plannedmaintenance strategy, shall be specified by the user,

15

1S 15654:2006

requiring suppliers to provide supporting predictedavailability calculations in their proposals.

An availability test of from 30 to 90 days is oftenspecified prior to acceptance of a system. Operatingand maintenance records shall be kept and used toprove the predicted, and to support the achievedavailability computations (see 9.6).

For design analysis, and to determine the predictionof availability for sub-assemblies and units, the follow-ing equation utilizing MTBF and MTTR shall be used:

/4, = MTBF/(MTBF + MTTR)

where AP is predicted availability.

Equations for modeling complex designs shall beformulated by the supplier. Use of the equationsassociated with parallel redundant components (or sub-systems) are valid under the following conditions:

a) Failure of parallel elements are independent.Component failures do not propagate failuresof other components.

b) Sufficient repair turnaround and standbyreplacement parts are available to handlemultiple simultaneous failures.

The impact of the outage of each system element orfunction on the availability of the total system shall bemutually agreed upon between the user and thesupplier.

Availability test results shall be calculated separatelyfor major system components (for example, Serversystem versus RTUS). Since these components mayhave a varying impact on the usefulness of the systemas a whole, different definitions of downtime areapplicable.

Major component downtime shall be definedto reflectthe proportional significance of the equipment that isdown. For example, downtime for the data acquisitionsystem could be defined as the sum of the downtimefor all RTUS divided by the total number of RTUs. Atthe master station, downtime should not includemalfunctions in peripheral devices that do not detractfrom the functional capabilities of the master stationas a whole (for example, printers and tape units).

7.4 System Security

System security (of operation) is defined as the abilityto recognize an inappropriate or undesirable operationor condition in such a fashion that causes an appropriatealarm, a non-operation, or both.

Security of operation considerations are divided intothe following three areas:

a) Operating practice and procedures,

b) Communication security, and

c) Hardware and software design.

7.4.1 Operations Security Features

Security features comprising operating practice andprocedures include the use of function and operatingchecks (manual and/or automatic). Function andoperating checks may include:

a)

b)

c)

d)

e)

f-i

g)h)

j)

k)

m)

Analog reference points (Oand 90 percent),

Control function check (loop-back),

Scan function check (loop-back),

Poll function check,

Logging function check,

Queue overflow alarms,

Diagnostic aids,

Calibration checks,

Logging of all operator actions, includingwhether the equipment completed therequested action,

Tagging of out-of-service control points at theuser interface, and

Use of an RTU local/remote switch, withfeedback to a status point, to disable allcontrol actuators while an RTU is beingserviced.

Equipment designed for remote control of valve shalluse both a select-before-execute user interface (UI)sequenceand a checkback-before-operatecommunicationsequence for control operations.

The UI sequence shall provide visual feedback of theselection to the user, so the user can verifi that thesystem has interpreted the selection correctly beforeexecuting the control function.

The communication sequence checkback message shallbe derived from the RTU’S point selection hardware,and not be just a simple echoing of the received selectmessage. This allows the master station to verify rrotonly that the communication was error free, but alsothat the RTU’S 1/0 hardware and software acted corr-ectly in interpreting the selection.

In order to provide maximum security against randomchannel noise being interpreted as a selectlexecutesequence at an RTU, the following safeguards shouldbe incorporated:

a)

b)

c)

The communications protocol shall have avery effective redundancy check code .(thisis necessary, but not sufficient, security);

There shall be a relatively short timeoutbetween the select and operate steps;

The next master station message.following theselect shall be the execute;

16

d)

e)

o

The complete point identification shall -becontained in the select, checkback, andexecute messages, which shall be fullycompared before the control operation isexecuted;

If any of the above checks fail, the controlsequence shall be re-set immediately, and anew select message shall be required to restartit; and

Both the master station and RTU shall enforcethe above rules.

The communication checkback sequence may beperformed either concurrently with the controlselection sequence at the UI, or after the selectionsequence has been completed. When performedconcurrently, the selection of a point for control shallcause the select message to be transmitted to the RTU.Upon successfid receipt, the RTU shall arm itself forcontrol, generate the checkback message, and transmitit back to the master station. A valid checkbackmessage shall result in visual selection feedback to theuser, who can then choose to either execute or cancelthe control fimction.

This type of operation requires a longer selectlexecutetimeout at the RTU, and will either violate the execute-next rule, or will stop scanning on that channel untilthe user responds with an execution or cancellation.

When the UI sequence and communication sequenceare performed sequentially, the selection of a point forcontrol should cause the master station to display avisual indication of that selection for verification.

In this type of operation, the user’s verification ofselection does not come fi-omthe RTU, but all othersecurity features may be fidly implemented.

The user may then execute the control fimction. Statusand data scanning should then be interrupted, and aselect message sent to the RTU.

The RTU shall then arm the control function and returna checkback message. The checkback message shallbe checked by the master station, and an executemessage sent automatically to the RTU. If this executemessage is received as valid, the RTU shall executethe command and return an acknowledgment that thefunction has been performed.

“7.4.2 Communication Message Securi@

Communication security features include:

a)

b)

The design goal that an error in a message shallnot result in a critical failure of the system.

Alarming the failure of an RTU to respond toa message within a specified number ofautomatic retries.

c)

d)

e)

f)

g)

IS 15654:2006

Ensuring that communication channel errorcontrol, in concert with the communicationprotocol and line discipline, reduce theprobability of acceptance of messagesreceived with error rate to less than 10-’2whenthe channel bit error rate is 104.

Verification of the proper operation ofcommunication channels on a regular basis.

Counting, and periodically logging,communication errors on a per-channel basis.

Ensuring that no two RTUS with the sameaddress share the same party line or switchedcommunication channel.

Ensuring that each RTU communicationchannel(s) supportsonly one communicationprotocol.

7.4.3 Hardware/Sojiiare Securi& Features

Security features comprising hardwat’e and softwaredesign include the following:

a)

b)

c)

d)

e)

f)

g)

Power supply protection — over current,over/under voltage,

Automatic initialization and restart,

Equipment self-check with alarm,

Watchdog timer(s) with alarm,

Automatic failover with alarm,

Fail-safe operation, and

Non-volatile station address retention inRTUS.

7.5 Expandabili@

Expandability is the ease with which new RTU, newpoints andlor fimctions, or both, can be added to thesystem, and the amount of downtime required.

Expansion point types are defined as spare point, wiredpoint, and space-only. Spare point equipment isequipment that is not being utilized but is filly wiredand equipped. Wired point is the capacity -for whichall common equipment, wiring, and space are provided,but no plug-in point hardware is provided. Space-onlypoint is the capacity for which cabinet-space-only isprovided for fiture addition of equipment and wiring.

Expandability limitations may include, but are notrestricted to, the following:

a)

b)

c)

d)

e)

f)

Available physical space;

Power supply capacity;

Heat dissipation;

Processor throughput and number ofprocessors;

Memory capacity of all types;

Point limits of hardware, sotlware, or protocol;

17

IS 15654:2006

g) Buslength, loading, and traffic;

h) Limitations onroutines, addresses, labels, orbuffers: and

j) Unacceptable extension of scan times byincreased data (given bit rate and protocolefficiency).

7.6 Changeability

Changeability is defined as the ease with which system,RTU, and point data base parameters maybe changedat both the master station and RTU. Parameters thatshall be emy to change include the following:

a) Operating parameters, and

b) Configuration and setup parameters.

The supplier’s documentation (see 10.3.2)contain the step-by-step process as given into 7.-6.3.

7.6.1 Operating Parameters .

shall7.6.1

Operating parameters must be easily changed by thesystem user. They include, but are not limited to thefollowing:

a) RTU on/off-scan,

b) Point on/off scan,

c) Point tags on/off,

d) Manually entered values,

e) Point alarm limits,

~ Point deadband values, and

g) lED parameters.

7.6.2 Configuration and Setup Parameters

Configuration and setup parameters must be easilychanged by an authorized system engineer, but shallbe protected against being changed by the users. Theyinclude the following:

a)

b)

c)

d)

e)

f)

@

h)

j)

k)

Configuration password,

Major/minor alarm conditions and actions,

User-definable calculations,

Definition of a new RTU,

Communication port and/or station addressassignments of RTUS,

Addition and/or rearrangement of an RTU’Spoints,

Correspondence of status points to controlpoints,

Point and state descriptions, for presentationto the system user,

Point scaling factors, for conversion of datato engineering units, and

Output relay dwell times.

7.6.3 Changeability Limitations

Changeability limitations may result tlom, but are notlimited to the following:

a)

b)

c)

d)

e)

o

g)

Inability to make master station and RTU database changes on-line from the master station,

Storage of parameters in memory (forexample ROM) that is not modifiable in-circuit,

Restrictions caused by data base structure,

Hardware/software compatibility,

Hardware limitations,

Software operating system limitations, and

Restrictions caused by use of IEDs.

7.7 Spare Capacity

Spare capacity is defined as the additional capacity thatcan be added to the master station.

7.7.1 Main Memory

A requirement of no less than 50 percent unused mainmemory initially will allow enough expansion for newfunctions, enhancement of existing functions, andgrowth of the power system and the equipment thatneeds to be monitored. Computer documentation shallalso be consulted to determine how much mainmemory capacity can be expanded over and above thecapacity initially installed. As a minimum, it shall bepossible to double the initial capacity with the additionof memory modules.

7.7.2 Auxiliary Memory

A requirement of no less than 50 percent spare diskcapacity initially will allow for moderate expansion.Computer documentation shall also be consulted todetermine how much disk capacity can be expandedover and above the capacity initially installed. As aminimum, it shall be possible .to double the initialcapacity with the addition of disk units.

8 MARKING

The control and data acquisition equipment and majorsub-assemblies shall be suitably marked as necessaryfor safety and identification.

8.1 Identification

Each type of equipment shall be identified so that itcan be easily correlated with the documentation. Themeans of identification shall be uniform throughoutthe system, and it may include colour coding, labelling,and part number. The identification mark shall bepermanently affixed to the part that it identifies.Consideration shall be given to using bar code labelsto identi~ the equipment and sub-assemblies.

18

IS 15654:2006

8.2 Nameplates

Each separate unit of the system shall be iimished withnameplates bearing relevant information.

Nameplates shall be legible at a distance ofapproximately 1 m.

8.3 Warning

“Warning signs or safety instructions shall be appliedwhere there is a need for general instructions relativeto safety measures (for example, supply circuit).

9 TESTS AND INSPECTIONS

The purpose of-this clause is to describe the tests andinspections recommended to ensure that control anddata acquisition equipment will perform reliably andcorrectly according to the user’s technical specifica-tions. Users shall specifi all tests to be performed. Testrequirements shall cover, as a minimum, all criticalportions of the specification, especially tinctional anddesign requirements. Tests shall be required to beconducted by user and supplier. Test results and alldeviations from test plans shall be required to bedocumented.

9.1 Stages of Tests and Inspection

The test and inspection process requires that variousfimctions of the equipment be tested or verified duringone or more stages in the production and installationcycle of the equipment. These stages and appropriatetests are illustrated in Table 2.

Across the top of the table are shown the four majorclasses of tests and inspections, being interface, envi-ronmental, functional, and performance. The threestages of testing and inspections, being certified design,

factory and field, are shown along the left-hand edgeof the table. The specific tests and inspections in eachclass are listed in the body of the table, below the classheading. Tests listed without notation are recom-mended for all applications at the stage they can bemost economically performed.

Tests marked with an asterisk are optional and areperformed only when specified by the user. Certifieddesign tests on equipment can be accepted at the wser’sdiscretion.

9.1.1 Certfied.Design Tests

These are tests performed by the supplier on specimensof a generic type of production model equipment toestablish conformance with its design standard. Theconditions and results of these tests shall be fi.dlydocu-mented and certified.

9.1.2 Factory Tests and Inspections

This stage includes the inspection and approval ofinterface drawings prior to fabrication of the equipmentand all functional tests and inspections performed onthe actual equipment to be supplied to the user prior tothe shipment of that equipment from th& supplier’sfacilities. The factory tests shall be a highly structuredprocedure designed to demonstrate, as completely aspossible, that the equipment will perform correctly andreliably in its intended application. Factory tests mayalso include tests to verify some or all of the results ofthe certified design tests.

9.1.3 Field Tests and Inspections

Field tests and inspections are performed on theequipment after it has been shipped tlom the supplier’sfacilities. These include pre-installation inspections and

Table 2 Test Stages and CIasses of Tests

(Clause 9.1)

sl TestStages ClassesofTestsNo. -/ \

Interface Tests Environmental Tests Functional Tests Performance Testsand Inspections and Inspections and Inspections and Inspections

(1) (2) (3) (4) (5) (6)

O Certified design tests Power input* Temperature Humidity .

ii) Factory tests and Mechanicalpower Temperature” 1/0 point checkoutinspections source* Humidity* Communications

Dust* User interfaceSpecial functions

iii) Field tests and — 1/0 point checkoutinspections Communications

User interfaceSpecial functions

—

LoadingData acquisition controlUser interfaceComputer and dkk stability”Maintainability*Expandability*

Availability*

* Optional tests performed only when specified by the user.

19

E 15654:2006

tests to ensure the equipment has not been damagedduring shipment and post-installation tests to verifythe equipment performs its functions reliably andcorrectly.

9.2 Interface Tests and Inspections

These tests are designed to demonstrate that the variousmechanical and electrical interfaces to the equipmentare in accordance with applicable portions of 5,together with other applicable parameters called outin the user’s specifications. For the most part, theseinterface parameters can either be demonstrated dur-ing factory tests or accepted on the basis of certifieddesign tests.

9.2.1 Mechanical

Mechanical characteristics (for example materials,workmanship, dimensions, fabrication techniques, andfinishes) shall be verified through visual inspectionsand comparisons with applicable drawings.

9.2.2 Electrical

These tests include all those to be_performedon electricalinterfaces to the equipment, with the exception of thoserelated to the fictional performance of the equipment.

9.2.2.1 Power source

The equipment shall be tested to demonstrate the properoperation of the equipment throughout the range ofspecified power source parameters.

9.3 Environmental Tests

These tests are designed to demonstrate that theequipment will perform correctly and reliably whileexposed to the applicable environmental parametersdescribed in 6, together with other applicableparameters called out in the user’s specifications. Theresults of certified design tests are usually sufficientto demonstrate that the equipment will operate reliablyand correctly within a specified environment. The usermay require the supplier to perform factory tests onthe equipment to demonstrate that it will indeedperform correctly under the specified environmentalconditions. Equipment in environmental tests shouldbe operating with realistic inputs and outputs.

The environmental parameters and testingrequirements specified by the user should be limitedto the worst case conditions that can be realisticallyanticipated in the location where the equipment willultimately be installed. Refer IS 9000 series or IEC60068 series for various environmental tests.

9.3.1 Physical

The equipment shall be tested to verifi that it operates

correctly in the following physical environmentsdescribed in 9.3.1.1 to 9.3.1.3.

9.3.1.1 Temperature

To test the equipment within the specified temperaturerange (see 6.1. 1), it shall be placed in an environmen-tal test chamber where it can be operated for a specifiedperiod at both the low and high ends of the range, andcycled between them. Calibration and accuracy checksshall be made throughout the range.

9.3.1.2 Humidity

Humidity tests (without condensation) shall beperformed in conjunction with the temperature test(see 9.3.1.1). Humidity test data shall include thehumidity ranges tested at each temperature.

9.3.1.3 Dust

Testing shall consist of inspection to determine whetheror not the equipment is properly sealed to preventintrusion of dust.

9.4 Functional Tests

Functional tests shall be designed to ensure that theequipment performs its functions reliably and correctly.They are performed during the factory, or field teststages, or both. ‘Preliminary testing should beperformed by the supplier before verification by theuser. For many applications and types of equipment,successful factory tests will be a sufllcient basis foracceptance of the system by the user. For more complexapplications or systems, additional tests in the fieldmay be required to fully veri~ correct and reliableperformance.

The following fictional tests should be carried out:

a)

b)

c)

d)

e)

-f)

Interface of RTUS with IEDs;

Database and alarms validation;

Remote workstation testing;

Checking of various reports, archiving andtrending functions;

Clock synchronization between the nodes ofmaster station and RTUS; and

Security/Passwords testing.

9.4.1 1/0 Equipment Checkout

All 1/0 equipment to be supplied shall be tested duringfactory tests to demonstrate that it performs itsfimctions correctly, accurately, and reliably. These testsshall be performed with equipment that simulates theactual equipment to be monitored or controlled.

9.4.2 Communication

The communication tests shall demonstrate proper

20

operation -of all aspects of the equipment’scommunication capability, including modems, securitychecking, and message protocols. The data modemsor signaling equipment shall be exercised to verifithat they operate correctly and reliably on the type ofchannel for which they are designed. The tests shallbe conducted under conditions that duplicate as closelyas possible the specifications for the channel includingsimulated channel noise, communication failures,and recovery. Provisions shall be made to logcommunication outages and update communicationstatistic displays where these features are provided.

The communication tests shall exercise all messageprotocols and formats to which the equipment isdesigned to respond. The tests shall also demonstratethat any error detection or correction capabilities func-tion properly and that the equipment does not respondto erroneous commands.

9.4.3 User Interface (UQ

Comprehensive user interface tests shall be performedto verifi the correct fictional operation of all userinterface hardware and software. All indications anddisplays shall be verified to ensure that they correlatewith the correct 1/0 equipment, and all user controlsshall be checked to ensure that they result in only thecorrect sequence of operations.

9.4.4 Special Functions

When the equipment supplied is to perform functionstailored expressly to the user’s application (for exampleclosed loop control), these fimctions shall be checkedduring the appropriate test stage. It is often necessaryto perform these tests in the field, after the equipmenthas been adjusted to the parameters of the installation.

9.5 System Performance Tests

The performance of all critical parameters of theequipment (for example communication, peripherals,user interfaces, 1/0 processing, and CPU) shall bemeasured under various loading conditions orscenarios. System performance shall be measured asearly in a project as possible to identi~ any systemweaknesses. This will allow the user and supplier anopportunity to resolve problems in a timely manner.

The loading scenarios shall simulate the following:

a) Normal activity — initial system.

b) Heavy activity (disturbance loading definedby user) — initial system.

c) Normal activi~ — filly expanded system.

d) Heavy activity (disturbance loading definedby user) — fully expanded system.

e) Communications failures or high noise

IS 15654:2006

conditions such as high noise on an entiremicrowave system.

Loading conditions should be determined by analyzingworst case conditions experienced by the user and theworst possible condition likely to happen in the futureover the life of the system. Table 3 is provided as aguide.

The measurements for performance assume that allfimctions of the system have been individually verifiedby functional tests and that the total system is ready tobe evaluated.

If actual system inputs are not available, they shall besimulated with special hardware or software. For ameaningful test, these inputs shall include thefollowing:

a) Simulated RTU inputs (alarm contacts, analoginputs, status input, etc).

b) Simulated message data structures from theRTUS into the master station communicationinterfaces.

c) Simulated data links to other computers,specifying the amount, type and frequency ofdata to be transferred.

d) Simulated user interfaces such as wall mimic.

e) Other simulated inputs.

Table 3 System Performance TestslJ

(Clause 9.5)

S1No. Input ActivityCycle(1) (2) (3)

i) Normal Activity

Each userStatus inputAnalog inputs

ii) Heavy Activity

Each userStatus inputsAnalog inputs

1displaylequestlminute1percent changes/scan1percent of all analogs

change/scan

4 display requestiminute10percent chrmges/scan25.pereent of all analogs

change/scan

o Values given are for example only. It is recommended that theuser select values that represent the user’s.system characteristicsand operating procedures.

Manual operation sequences to be performed duringtests shall be described in detail to provide a repeatabletest scenario and a way to measure improvements inperformance (for example, five people requesting one-line diagrams and two people requesting menu displayssimultaneously). Test steps should simulate all normaluser operations.

Response performance shall be measured in seconds.All measurements shall be recorded for analysis after

21

IS 15654:2006

the tests. Software utility programmed are available tlommost system suppliers for finding CPU utilization andloading (for example, f@ure of the computer operatingsystem or a separate programme available fromcomputer manufacturer, or both) and if used by supplierthe system loading of the programs shall be provided touser with proof. Automatic measurement of other testparameters can be done by special purpose software.

9.5.1 Data Acquisition Performance

Data acquisition sub-system performance measures thefollowing:

a) The time for a status change or analog changeat the RTU to be displayed to the user at themaster station (for example, monitor, loggeror mimic).

b) The time to query all RTUS on a per channelbasis.

A cyclic status point input of 2 or more times fasterthe system RTU scan rate can be used to detect a missed’scan due to overloading. The status input simulatorshould be connected to an input of one RTU. The alarmassociated with the toggled input shall appear on thelogger with a time tag of approximately twice the scanrate. A system overload causing an extension of thescan cycle is obvious from the printout because one ormore status changes is missed.

9.5.2 Control Performance

Control performance measures the elapsed timebetween a control request by a user at the master stationand the control output contact closure at the RTU. Thistest shall also be performed in the field. The field testwill provide realistic measurements, using userinstalled RTUS and communication facilities.

9.5.3 User Interface Performance

The user interface performance is a measure of theresponse time to satis~ user requests for information.To measure display response time, measure the timeflom the instant a request is made until the result ofthe request is completely displayed on a CRT screen,printed on a logger, or shown on a mimic panel.Different classes of displays (one-line diagrams, alarmsummaries, menus, tabular, etc) may have differentdisplay response times due to the amount of data to begathered and computations required before a displayrequest can be completed.

9.5.4 Computer and Disk Performance

The computer and disk performance shall be checkedusing the supplied programmed from computermanufacturers to ascertain that CPU and Disk utilizationis within acceptable limit as specified by user.

9.5.4.1Computer link response time

Computer to computer link response times should bemeasured and evaluated during performance testsunder varied loading conditions,

9.5.4.2 Computer LANs utilization

LANs that connect application computers togethershould be measured and evaluated during performancetests under varied loading conditions.

9.5.4.3 Computer reconfiguration, power fail andrestart tests

On master stations with redundant equipment,reconfiguration tests should be performed to confirmthe ability to failover from one CPU to another(reconfigure the real-time database) and to switchperipheral equipment to the primary system, thesecondary system, or off-line (that is out-of-service).

Power fail tests measure the time to recover from acomplete or partial power failure until the system isfilly operational.

Because normal maintenance procedures andequipment failure cause downtime of the masterstation, restart tests are to assure the system will recoverin a timely manner. Existing data shall consist of allscanned and manually entered data (that is pipelinesystem tags, manual overrides, limit changes, etc).Downtime of the system or parts of the system shouldbe measured during these tests to confirm the lengthof these outages can be tolerated by the user.

The time required to load a system from mass storageand initiate operation should be measured. This timeshould be less than the acceptable system outage time.

9.6 Test Run

The user shall require an availability test to be run afterthe system is installed and placed in operation (see 7.3).An availability test takes place over a specified lengthof time during which the equipment shall operatecorrectly and reliably for at least a specified percentageof that time. The length of the test shall be sufficientto verify that the equipment can be expected to performits intended functions reliably and correctly over itsintended lifetime.

The availability test shall be run under conditionsmutually agreeable to the user and supplier. In general,the supplier shall be responsible for making thenecessary repairs. Downtime should not include delaysover which the supplier has no control.

This is followed by analyzing the number and types offailures, and their effects on system operation. The testtime should be selected so that the total number of

22

device operating hours for each type of system-criticaldevice isrepresentative of the predicted MTBF for thatdevice to obtain statistically significant failure data.Specific rules for accumulation of uptime, downtime,maintenance time, and administrative time shall beagreed upon before the test (see 7).

9.7 Maintainability Test

The user shall require a maintainability test to be runto evaluate the supplier’s design, documentation,training, and recommended spare parts. Maintainabilitywill directly affect the availability of the SCADAsystem and therefore the reliability of the system(see 7.2). Computer hardware maintenance and long-terrn repair support are ditlicult to evaluate withoutactual experience. Discussions with other utilitiesregarding their experience is one way to acquire acertain degree of knowledge about the maintainabilityof specific equipment and systems.

Software, database, and display maintainability is alsocritical to the successful operation of a SCADA system.Tests to be witnessed should include the following:

.System generation tests (measure time to complete,and amount of manual intervention required)

a) Database maintenance

1) Adding an alarm point (time to makeoperational) should be demonstrated,

2) Deleting or changing text on an alarmpoint should be demonstrated, and

3) Changing an analog scale factor shouldbe demonstrated.

b) Displ~ maintenance

1) A new one-line diagram should be addedand linked to the database (a specificexample in the specification should beprovided), and

2) A line and new devices should be addedto an existing one-line diagram includinganalogs, tags, etc.

c) Equipment maintenance

1) A monitor should be replaced,

2) A modem should’be replaced, and

3) A disk drive should be replaced.

9.8 Expandability Tests

Expansion capability of a new system shall be analyzed(see 7.5). For example

a)

b)

c)

RTU 1/0 point expansion (both hardware andsoftware changes required);

Addition of RTUS;

Master station expansion:

IS 15654:2006

1) Peripherals, diskspace, memory,

2) CPU capacity (percent utilization),

3) User interface (work station additions),and

4) Database and display expansion.

9.9 Documentation Verification

The final phase of the testing programme is to verifythat the documentation being supplied is an accuratedescription of the equipment, including all correctionsresulting-from the tests. Final issue of completed doc-umentation shall be provided as soon as practical aftershipment and acceptance of the equipment.

10 DOCUMENTATION

The documentation for control and data acquisitionequipment shall cover five basic areas as follows:

a) Design,

b) Installation,

c) Operating instructions and records,

d) Maintenance instructions and records, and

e) Test (including QA & QC test plans).

In general, all final documentation provided by asupplier shall reflect the actual equipment as acceptedby the user, and all subsequent equipment changes shallbe recorded as document revisions by the user.

If users desire to have the information on reliability asdescribed in 7, they shall collect information on failuresand repairs for all subassemblies. This data onoperating performance shall then be periodicallyprovided to the supplier.

Documentation described in 10.1 to 10.6 may besubject to user review or approval. Documentation maybe structured in alternate fashion, but shall cover allfive areas. The documentation may be supplied in oneor more.of -several forms-printed, computer stored, orelectronic media. In the latter case, the supplier shalleither identify or supply the supporting wordprocessing sothvare used to prepare the documentation.

10.1 Design Documentation

Design documentation is the responsibility of thesupplier. For example, expansion methods for addingpoints to hardware assemblies and software programmedor tables shall be described and illustrated. Blockdiagrams shall be included to describe control and dataacquisition equipment and external equipment. ‘Layoutand wiring drawings -shall also be included to defineexternal interconnection needs at each facility. Text,photographs, and illustrative material shall accompanythese drawings in sufficient detail so that functionalperformance and design may be readily understood.

23

1S 15654:2006

For example, functional block diagrams andexplanatory text shall be used to describe each majorassembly and software programme contained in theequipment configuration. A document describing thecommunication process between the master station andthe RTUS shall be provided. The supplier shall beresponsible for providing outline drawings, mountingrequirement details, customer connection details,environmental requirements, size, weight and any otherinformation need for the user to prepare installationdocumentation.

10.2 Installation Documentation

Installation documentation is the responsibility ofboththe supplier and user and shall define the following:

a)

b)

c)

d)

e)

8

~)

h)

Electrical power, data, control, andcommunications interface wiring procedures;

Floor, rack and shelf mounting, drilling, andbolting methods necessary to secure theequipment in place;

Safety precautions or guards;

Grounding and bonding procedures;

Clearances for access and ventilation;

Testing and alignment methods;

Weather proofing, dustproofing, and otherenvironmental procedures; and

Other procedures needed to properly installthe equipment.

10.3 Operating Instructions and Records

Instruction information shall be developed foroperating personnel who use the control and dataacquisition equipment.

10.3.1 Supplier Operating Instructions

The supplier shall publish instructional informationdefining the equipment and how it shall be operated.This instructional information-shall consist of a generaldescription of the equipment configuration providedand shall state its intended use and its majorperformance characteristics. Whenever a user interfacesuch as a console, indicating/control panel, or printingdevice is involved~the operational documentation shalldetail in step-by-step fashion the operational sequencesrequired to use these interface devices. AdequateiIllustrative material shall be included to identi~ andlocate all control and indicating devices.

10.3.2 User operating instructions and records

The equipment supplier shall publish operatingprocedures defining the system and include userdetailed instructions and responsibilities. These userinstructions shall be based on the supplier’s

instructional information and the nature of the systembeing monitored and controlled. Proceduralinstructions, that state routine and emergencyprocedures, safety precautions, and quantitative andqualitative limits to be observed in the starting, running,stopping, switching, and shutting down of controlequipment, shall be included. Whenever operatingprocedures or adjustments are to be performed in aspecific sequence, step-by-step instructions should bestated.

10.3.3 Records

Records shall be prepared by both operating andmaintenance personnel to support the availability/reliability calculation defined in 7.1 to 7.3.

10.4 Maintenance Instructions and Records

Maintenance documentation for personnel skilled atthe electronic technician level shall be developed andprovided by the supplier, and shall include thefollowing information listed in “1O.4Ato 10.4.4.

10.4.1 Performance Information

This information shall include a condensed descriptionof how the equipment operates (derived from 10.1)

and a block diagram illustrating each major assemblyand software programme in the configuration. Messagesequences, including data and security formats for eachtype of message, shall be included in the condenseddescription and illustrated whenever such messages areused between stations, or locally at a station. Theoperational sequence of major assemblies andprogrammed shall be described and illustrated byfictional block diagrams. Detailed logic diagrams andflowcharts shall also be provided as necessary fortroubleshooting analysis and field-repair actions.

10.4.2 Preventive Maintenance Instructions

These instructions shall include all applicable visualexaminations, software and hardware test anddiagnostic routines, and resultant adjustmentsnecessary for periodic maintenance of controlequipment. Instructions on how to load and use anytest and diagnostic programme, and any special orstandard test equipment shall bean integral part of theseprocedures.

10.4.3 Corrective Maintenance Instructions

These instructions shall include guides for locatingmalfunctions down to the spare parts replacement orfield-repair level. These guides shall include adequatedetails for quickly and efficiently locating the causeof an equipment malfunction, and shall state theprobable source(s) of trouble, thesymptoms, probablecause, and instructions for correcting the malfunction.

24

These guides shall explain how to use any on-line testand diagnostic program and any special test equipmentif applicable.

Corrective maintenance instructions shall also includeexplanations for the repair, adjustment, or replacementof all items. Schematic diagrams of electrical,mechanical, and electronic circuits; parts location illus-trations, or other methods of parts location information;and photographs, and exploded and sectional viewsgiving details of mechanical assemblies shall beprovided as necessary to repair or replace equipment.Information on the loading and use of special off-linediagnostic-programmed, tools, and test equipment, andany cautions or warnings which shall be observed toprotect personnel and equipment, shall also be included.

10.4.4 Parts Information

This information shall include the identification of eachreplaceable or field repairable module. Parts shall be

1S 15654:2006

identified on a list or drawing in sufficient detail forprocurement of any repairable or replaceable part.These parts shall be identified by their industrial,generic part numbers, and shall have second sourcereferencing whenever possible.

10.5 Test Documentation

Test documentation by the supplier shall consist of asystem test plan, test procedures, and certified testreports on tests described in 9. The test plan shall statewhat equipment configuration will be tested, when itwill be tested, which tests will be run, and who willconduct and witness the tests. The test procedures shalldefine the operating steps and expected results. Thetest report shall record all test results.

10.6 Channel Loading Calculation

The vendor should provide channel loadingcalculations.

ANNEX A

(Clause 2)

LIST OF REFERRED STANDARDS

SP 30:1985 National Electrical Code (NEC)

IS 1885 (Part 50) :1985 Electrotechnical vocabulary: Part 50 Telecontrol

IS 1885 (Part 52) :1980 Electrotechnical vocabulary: Part 52 Data processing

IS 2309:1989 Code of practice for the protection of buildings and allied structures against lightning

IS 3043:1987 Code of practice for earthing

IS 9000 Series Basic environmental testing procedures for electronic and electrical items

IS 10315:19977 bit coded character set for information interchange

IS 1274-6 (Part l/See 3) : 1993 Telecontrol equipment and systems: Part 1 General considerations,Section 3 Glossary

IS 13947 (Part 1) :1993 Specification for low-voltage switchgear and controlgear: Part 1 General rules

IEC 60068 Series Environmental testing

IEC 60870-2-1 (1995) Telecontrol equipment and systems — Part 2: Operating conditions — Section 1 : Powersupply and electromagnetic compatibility

IEC 60870-5-101 (2003) Telecontro! equipment and systems — Part 5-101: Transmission protocols — Companionstandard for basic telecontrol tasks

IEC 60870-5-104 (2000) Telecontrol equipment and systems — Part 5-104: Transmission protocols — Networkaccess for IEC 60870-5-101 using standard transport profiles

IEEE Green Book Standard 142:1991 IEEE Recommended practices for grounding of industrial and commercialpower systems

25

IS 15654:2006

ANNEX B

(Clause 4.1)

MASTER STATION/RTU INTERCONNECTIONS

B-l SINGLE MAISTER STATION

E!Et-=FIG. 8 SINGLEMASTERSTATION,SINGLERTU

MASTEl? 4 bSTATION

RTU 2

RTU NI I

FIG. 9 SINGLEMASTER STATION,MULTIPLERTU(S), RADIAL CIRCUIT

~ RTU 1

MASTER*

STATIONRTU 2

b RTU N

FIG. 10 SINGLEMASTER STATION,MULTIPLERTU(S), PARTY-LINE CIRCUIT

26

1S-15654:2006

B-2 MULTIPLE MASTER STATIONS

dI MASTER I

+ R’TU 1 I

zRTU 2

RTU ~

FIG. 11 DUAL MASTER STATIONS,MLJLTIPLERTU(S), LOOPEDPARTY LINE

MASTER

STATION 1

RTU

MASTER

STATION 2

FIG. 12 DUALMASTERSTATIONS,SINGLEDUAL PORTEDRTU, RADJAL CIRCUIT

B-3 MULTIPLE MASTER STATIONS, MULTIPLE RTU(S)

MASTER

STATION 1

●

●

●

9

MASTER

ST-ATION M

FIG. 13 DUALMASTERSTATIONS,MULTIPLERTU(S) [SINGMPORTEDRTU(S)]

27

IS 15654:2006

I I

MASTER

STATION 1

●

c

o

●

MASTER

STATION M

I I

.

FIG. 14 DUALMASTERSTATIONS,MULTIPLERTU(S)[DUALPORTEDRTU(S)]

B-4 COMBINATION SYSTEMS

RTU 1SUB-MASTER

STATION

RTU N

MASTER

STATION 1 +

FIG. 15 SINGLEMASTERSTATION,SINGLESUB-MASTERSTATION

MULTIPLERTU(S)

28

IS 15654:2006

RTU 1SUB-MASTER

STATION 1

●

o

MASTER ●

STATION 1 ●

RTU 1SUB-MASTER

STATION M

RTU M

NOTE — Sub-master stations could communicate with one another

FIG. 16 SINGLEMASTERSTATION,MULTIPLESUB-MASTERSTATIONSMULTIPLERTU(S)

MASTER

STATION

RTU 1 @no RTU N

FIG. 17 SINGLEMASTERSTATION,RTU(S) AND END STATIONLINK

29

Bureau of Indian Standards

BIS is a statutory institution established under the Bureau of Indian Standards Act, 1986 to promoteharmonious development of the activities of standardization, marking and quality certification of goods andattending to connected matters in the country.

Copyright

B]S has the copyright of all its publications. No part of these publications may”be reproduced in any formwithout the prior permission in writing of BIS. This does not preclude the free use, in the course of implementingthe standard, of necessary details, such as symbols and sizes, type or grade designations. Enquiries relating tocopyright 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 reviewedperiodically; a standard along with amendments is reaffirmed when such review indicates that no changes areneeded; if the review indicates that changes are needed, it is taken up for revision. Users of Indian Standardsshould ascertain that they are in possession of the latest amendments or edition by referring to the latest issue of‘BIS !2atalogue’ and ‘Standards: Monthly Additions’.

This Indian Standard has been developed from Dot: No. LTD 25 (2059).

Amendments Issued Sisrce Publication

Amend No. Date of Issue Text Affected

BUREAU OF INDIAN STANDARDS

Headquarters:

Manak Bhavan, 9 Bahadur Shah Zafar Marg, New Delhi 110002Telephones: 2323 Cl131, 23-233373,23239402 website: www.bis.org.in

Regional Offices: Telephones

Central : Manak Bhavan, 9 Bahadur Shah Zafar Marg-{

23237617NEW DELHI 110002 23233841

Eastern : 1/14 C.I.T. Scheme. VII M, V.I.P. Road, Kankurgachi{

23378499,23378561KOLKATA 700054 23378626,23379120

Northern : SCO 335-336, Sector 34-A, CHANDIGARH 160022{

26038432609285

Southern : C.I.T. Campus, IV Cross Road, CHENNAI 600113{

22541216,2254144222542519,22542315

Western : Manakalaya, E9 MIDC, Marol, Andheri (East){

28329295,28327858MUMBAI 400093 28327891,28327892

Branches : AHMEDABAD. BANGALORE. BHOPAL. BHUBANESHWAR. COIMBATORJ3. FARIDABAD.GHAZIABAD. GUWAHATI. HYDERABAD. JAIPUR. KANPUR. LUCKNOW. NAGPUR.NALAGARH. PATNA. PUNE. RAJKOT. THIRUVANANTHAPURAM. VISAKHAPATNAM.

Printed at Simco Printing Press, Delhi