0% found this document useful (0 votes)
48 views1 page

SCADA Project Guide - 05

The document discusses the technical specifications for a SCADA/DMS system. It outlines how energy values will be collected from RTUs and FRUTs periodically and stored. It also describes how the system will handle telemetry failures by marking failed points and generating alarms.

Uploaded by

renv
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
48 views1 page

SCADA Project Guide - 05

The document discusses the technical specifications for a SCADA/DMS system. It outlines how energy values will be collected from RTUs and FRUTs periodically and stored. It also describes how the system will handle telemetry failures by marking failed points and generating alarms.

Uploaded by

renv
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Power Finance Corporation

SCADA/DMS, system under Part A –R-APDRP


Model Technical specification
MGVCL/RAPDRP/SIA/1140

Energy values of 15 minute blocks shall be collected periodically from the RTU,
FRTU at scan rate of 15 minute/1 hour (configurable upto 24 hours). Alternatively,
the energy values shall be calculated for each 15 minute/1 hour blocks at SCADA
level from the acquired energy values of MFTs through RTU & FRTU.

The contractor must asses & take the network delay into consideration while
designing the system so that the update time in normal & peak level of activities
are met.

The SCADA/DMS computer system shall also be able to collect any and all analog
& digital data from its RTUs/FRTU/FPI on demand. Apart from the periodic integrity
scan, the integrity scan shall also be initiated automatically for an RTU/ FRTU/ FPI
whenever the following situations arise:

i. Upon start up of the system


ii. RTU/ FRTU/ FPI status change is detected such as RTU/ FRTU/ FPI
restart, Communication Link restoration
iii. On demand by SCADA/DMS functions
iv. On request by the user

The TCP/IP Communication for RTU,FRTU,FPI on public network shall be


encrypted over SSL Security / VPN & the equipment should take control
command from designated Master IP address only and no other IP. The
RTU, FRTU, FPI & all TCP/IP devices that are on Public Network shall form a
private VPN network with the SCADA Front End, through which encrypted
data gets exchanged.

1.2.2.2 Telemetry Failure

If data is not received from an RTU/FRTU/ FPI after a user-adjustable number of


retries, each affected point in the SCADA system shall be marked with a
‘telemetry failure quality code’ and an alarm shall be generated. Telemetry
failure of data can be due to failure of communication link, failure of complete RTU/
,FRTU/FPI or RTU/ FRTU module or MFT etc. Only a single alarm shall be
generated if an entire RTU/ FRTU or its communication channel fails.

In the event of telemetry failure, the last good value/status shall be retained in the
database for each affected point. When telemetry returns to normal, the associated
SCADA system shall automatically resume updating the database with the
scanned data.

The user shall be able to substitute a value in the database for any point that is
experiencing telemetry failure which shall be marked with ‘manual replaced’
quality code in addition to the ‘telemetry failure’ quality code. The user shall
also be able to delete any point (or entire RTU/FRTU/FPI) from scan processing.
All deleted points shall be marked with a ‘delete-from-scan’ quality code.
SECTION-2, CHAPTER-1 : SCADA FUNCTIONS page 5 of 17

You might also like