Minutes of the Special SCADA/communication meeting held on 21.03.2016 … · 2016. 3. 24. · Minutes of the Special SCADA/communication meeting held on 21.03.2016 Page 2 issue within

Minutes of the Special SCADA/communication meeting held on 21.03.2016 Page 1

SRPC, Bengaluru Minutes of the Special SCADA/Communication Meeting held on 21st March 2016

Introduction

A Special SCADA/Communication Meeting was held on 21st March 2016 in SRPC, Bengaluru. The

List of participants is given at Annexure-I.

Shri S.R. Bhat, Member Secretary, SRPC welcomed all the participants to the Meeting. He stated

that as the participants were aware, of late, a number of SCADA/communication related issues were

being raised by the States which also had operational and commercial implications. This issue was also

deliberated in the recent SRPC meeting in which Chairperson; SRPC had expressed concern and directed

to furnish a report in this regard in a month’s time. He suggested that these persistent SCADA/data

related issues would best be resolved amicably in this forum only. He requested the concerned to

deliberate on the issues with an open mind in order to find the solution. He stated that a road

map/action plan needs to be firmed up in this regard.

PGCIL informed that the ULDC Scheme envisaged in 1999-2000 was now obsolete. The second

ULDC project which was underway would bring about improvement in SCADA system. Presently,

transition phase is going through and there were some teething problems. However, there would be

significant improvement in SCADA/communication system in the coming days. In respect of SR laying of

optical fibre cable for about 11,000 KMs had been completed and only around 1,600 km was pending.

225 wide band nodes had also been established. The Communication project would be completed in 5-6

months.

PGCIL explained that earlier RTUs used to report to SRLDC directly thru FEP installed at SRLDC on

IEC 101 protocol. In new system, a set of RTUs are reporting to DCPC through IEC 101 protocol & DCPC

in turn is reporting to SRLDC Control Centre on IEC 104 protocol. DCPC is used for conversion of data

from IEC101 to IEC104 for transmitting data to SRLDC using mostly optical fibre cables. PGCIL stated that

at times DCPCs were not stable and were reportedly giving problems. PGCIL felt that these issues of

DCPCs were needed to be addressed.

SCADA/Communication issues addressing procedure

SCADA/communication issue observed by any of the entities would be reported to

SRLDC/PGCIL/User. SRLDC would look into any issue of SCADA system at their end in coordination with

M/s Alstom. Similarly, User would address the issue at their end. PGCIL in co-ordination with their

contractor (M/s Tejas) would look into communication issues. All agencies would interact to resolve the


issue within three hours. In case the issue is not resolved within 24 hours, physical involvement of OEM

(M/s Alstom and M/S Tejas) through effective co-ordination by PGCIL/SRLDC/User would be ensured to

address the issue. PGCIL Nodal Officers Shri V K Khare, GM, SR-II & Shri P Ranga Rao, AGM SR-I would be

appraised of the issue. In case of hardware replacement/rectification / problems associated with DCPC,

the same would be completed within 72 hours. All agencies shall ensure to maintain adequate spares at

geographically diversified locations such that above timeline are met always. In case the issue is not

resolved, a contingency group comprising members from SRLDC(M/s Alstom), PGCIL (M/s Tejas) and

User would be formed to address the issue on emergency basis. Similarly, all other regional entities like

IPPs etc., shall make necessary contractual arrangement through their OEM for resolution of any data

issues on the same timelines indicated above.

Once the project moves into maintenance phase, a web group would be formed on which the

issues would be posted which would ensure proactive corrective action/information sharing at other

locations. Details of FPRs and FSRs could also be posted in the webgroup.

All users would be trained / aware of handling minor SCADA/communication issues. However,

they would assist under intimation to SRLDC(M/s Alstom) & PGCIL (M/s Tejas). It was pointed out that

responsibility of healthiness rested with respective OEM. Training/awareness programme for users

would be arranged by SRLDC (M/s Alstom) & PGCIL (M/s Tejas).

DCPC Issues

SR-I informed that there were some problems of DCPCs like getting hanged, installed without

UPS, frequent software updates, frequently restarts, reloading of data base etc. Gazuwaka, Vijayawada,

& Hyderabad had faced these issues.

M/s Alstom (SRLDC) stated that the DCPCs at Vijayawada and Gazuwaka were running without

UPS hence some hardware problems were observed. Hard disk had also been replaced at Gazuwaka

Hanging issue had come down drastically. In Feb 2016 month, DCPC at Gazuwaka only hanged once.

DCPCs are being monitored continuously by control centres and daily checks were in vogue. In case of

physical issues and persistent problems they are being attended at site.

PGCIL reiterated that any technical problem in DCPCs should be attended by M/s Alstom

(SRLDC). On many occasions, there was no communication problem but frequent data interruption was

observed due to DCPC issues. At times, M/s Alstom (SRLDC) was restarting and programming the DCPCs

from remote end without informing PGCIL and lot of time is wasted in sorting out communication issues.

PGCIL pointed out that recently data from Gooty DCPC was down while M/s Alstom (SRLDC) was


working on data base remotely. PGCIL requested M/s Alstom (SRLDC) to please inform concerned

(station/SRLDC) whenever any remote operation is being undertaken. Sriperumbudur RTU was not

reporting in last month due to some configuration/programming errors.

On a query about the AMC of DCPCs, M/s Alstom informed that once the project is completed it

would move into maintenance phase. PGCIL insisted that AMC of DCPCs should be taken up immediately

as many data interruptions were due to DCPCs.

Time synchronization of DCPC: PGCIL informed that they had faced difficulty during validation of

SOE from Nagarjunasagar at Hyderabad DCPC. The issue was set right after updating patch at Hyderabad

DCPC. PGCIL enquired that whether the latest patches has been updated on all DCPCs by M/s Alstom.

It was informed that as on date, all DCPCs in the region had been updated with the latest patch.

DCPC Dead band settting : PGCIL informed that dead band set on some of the DCPCs could be a

cause for discrepancy in SCADA data. AP informed that in the case of DCPC at Chittoor after making the

dead band to zero, data was found to be reporting correctly.

SRLDC stated that generally the dead band setting was kept between 0 to 10% to control

spurious signals. The settings were to be required to be set between 0 to 10% on a case to case basis

and it cannot be generalized.

It was noted that there are main DCPC and Stand by DCPC and data base is common both

DCPCs. Alstom was requested to update the databases of DCPCs alternately on main and stand by but

not simultaneously to avoid data interruptions. Main and stand by DCPCs should always be in service all

the time. All DCPCs should be equipped with UPS to avoid any hardware issues.

It was noted that different indications for Tx, Rx etc. are being used in DCPC by M/s. Alstom at

different locations. It was suggested that uniform configuration needed to be adopted.

ALSTOM mentioned that many times they got stuck in investigation of problems due to change

in baud rate / configuration / ports etc., by user sites without proper notice to SRLDC which led to delay

in trouble shooting in DCPC locations / SCADA end.

After deliberations, the following was agreed:

Major activities on DCPCs requiring complete shutdown of one of the parallel DCPCs, Data base

updation etc would be informed by concerned entity to PGCIL/SRLDC.

It would be ensured that during patch updation, time synchronization etc would be carried out

all DCPCs.

It was agreed that the dead-band settings would be made to “zero” and the situation would be

reviewed subsequently.

UPS availability at all DCPCs would be ensured.


Problem with cabling at SRLDC

PGCIL informed that there were some cabling issues at SRLDC viz between MUX and DCPC and

requested SRLDC to identify and resolve the local problems. It was felt that proper cable dressing with

labeling had to be carried out at SRLDC Telecom Room. PGCIL also requested SRLDC to have spare cards

and cables.

SRLDC stated that cabling works pertaining to SRLDC DCPC has already completed after

removing old FEP and Y cables. However there were some cables which are not laid properly/hanging

etc. belonging to other entities. For those cables PGCIL/POWERTEL/USERs needed to rectify the issues.

It was agreed that PGCIL/POWERTEL/USERs would ensure proper dressing of the cables along

with labeling, proper ferruling etc.

Works are to be carried out in consultation with SRLDC.

Transducer Scaling

PGCIL informed that there were some discrepancies in the telemetered values being received at

SCADA because of improper scaling/wrong detail of transducer. Specific examples of scaling issues for

MW value at Kadapa for Kadapah-Kolar line were brought to attention.

SRLDC informed that when the transition from GE system to Alstom SCADA system was

happening, they had addressed mails to both SR-I & SR-II for correct information but there was limited

response. SRLDC stated that proper scaling can be done at SRLDC SCADA when correct transducer detail

from site is known. PGCIL agreed to provide transducer detail for the telemetered values where

differences have been observed in SCADA value w.r.t. site values.

It is decided that both PGCIL & SRLDC would jointly to take up Transducer scaling issues on

mutually agreed date and complete the same by end of March 2016.

PGCIL agreed to provide transducer detail for the telemetered values where higher differences

has been observed in SCADA value w.r.t. site values.

ICCP link between RTAMC & SRLDC

PGCIL informed that RTAMC/NTAMC were to be linked to RLDCs through ICCP link as per their

contract. It was also pointed out that by doing so, redundant data would be available to SRLDC and the

same could be used as per requirement.


SRLDC stated that the provision for ICCP link integration is there in SCADA contract to possibly

link it with 15 new control centres. However, decision to link it with RTAMC/NTAMC was yet to be

decided by POSOCO Management.

It was noted that existing scheme of providing data through dual communication channels from

the RTU shall continue. However, in case of integration, if it is decided at appropriate level, it

would be additional source of data which can be used as per requirement.

PGCIL was requested to approach Higher Management of POSOCO. SRLDC was also suggested

to appraise their management in this regard.

RE-ROUTING OF COMMUNICATION CHANNELS

SR-I & SR-II were requested to communicate to SRLDC, as and when any change in the

communication path / route and also furnish updated communication routing diagrams to SRLDC on a

monthly basis.

SRLDC requested that the communication routing diagram as on date could be furnished.

COMMUNICATION ISSUES Details of dual communication channel not provided for RTU to DCPCs is at Annexure-II

APTRANSCO & KSEBL informed that many times they were restarting the SDH equipment under

the advice of POWERGRID’s contractor M/s. Tejas.

It was noted that it was taking around 20-30 minutes for the restart and during that time there

was no communication availability. During that time entire batch of data through the particular channel

becomes non-available.

After deliberations the following was agreed: All communication problems / issues would be reported to PGCIL who in turn would

immediately take-up with their contractor / site engineer.

All issues would be addressed remotely including the restart. Locally, restarts would be

undertaken only under advice of M/s.PGCIL (through their contractor M/s. Tejas) and in

emergent cases only. It was noted that there was redundant system in the same

equipment and as far as possible, only one at a time would be restarted.

Loop back test to ensure channel healthiness would be carried out within 10-15

minutes of complaint received.

POWERGRID was requested to monitor and maintain healthiness of communication

channels. SRLDC was also requested to inform as and when any one of the

communication channel failure gets noticed so that the same could be rectified by

POWERGRID while the other channel is in healthy condition itself. SRLDC agreed for the

same.

Software updates (patch), if any, would be carried out in all the SDH equipment under

intimation to PGCIL/SRLDC.


Protocol for SCADA integration for directly reporting RTUs/SAS SRLDC pointed out that the time line communicated vide letter dated 8th October 2015

(Annexure-III) was not being followed and last minute request were coming up like recently in the case

of NLRPS-NCC lines

SRLDC pointed out that they had faced difficulty recently in Suryapet data integration since

these stations were affecting drawal computations. Data needs to be integrated at least three days in

advance and testing also should be completed. Delay in COD, if any, due to non-integration of data and

not complying with the time lines would rest on respective entity.

After deliberations, it was agreed to adhere to time schedules in the procedure finalised in OCC.

All entities agreed that efforts would be made to complete all activities regarding data validation

including checking / testing at least 3 day before charging the element.

It was noted that integration of new element or any change in SCADA database would be

undertaken at SRLDC only during week days and between 9 A.M. to 5 P.M. as changes have to

be made at various places like NLDC.

Computation/availability issues SRLDC informed that availability is being computed generally on quality flag of Analog data

(sample). Points are being selected after ensuring its healthiness. It was clarified that no status inputs

were being considered for availability computation. Below availability of 90%, the RTU was being

considered as intermittent in report to Hon’ble CERC. It was also clarified by SRLDC that the RTU / data

outage duration is computed after excluding DCPC outage / problem period. However, SRLDC also

requested POWERGRID to carry out similar exercise such that the same can be re-conciled before

reporting to CERC.

PGCIL pointed out that there were various other parameters which were available and thus

taking two samples for availability computations was not correctly reflecting the availability values.

During the outage of one element, the availability figures were susceptible. Issues in DCPCs affected the

availability of 5-6 RTUs. Since this was being reported to Regulatory authorities, only non-availability

linked to communication issues needs to be reported. It was suggested by PGCIL that all parameters

could be considered for availability computations. Other issues for which PGCIL is not accountable

needed to be segregated and if not possible the figures should be with qualifying remarks.

SRLDC stated that it is essential to ensure all data from the RTU is made available in view of critical

role played by the data during real time system operation. From Grid operation point of view, even one

wrong value could have adverse impact on Grid security and there by the aggregation methodology


being suggested by PGCIL was not appropriate. Accordingly, the present method of sample availability

computations would be continued by SRLDC. However,they would try to change the sample parameters

for each RTU. PGCIL could furnish their availability computations based on communication

link/healthiness.

After deliberations it was agreed that SRLDC would continue the present methodology for

availability computations and indicate the details of computation to PGCIL for validation with

their own computation. PGCIL was suggested to take up this issue further, if so desired,

appropriately.

RTU availability

SRLDC presented the availability of RTU for the period of December 2015 to February 2016.

(Annexure- IV). SRLDC expressed concern since availability of many RTUSs was less than 90 %.

PGCIL pointed out that real time data availability to SRLDC was also affected, at times, due to loose

connection, nonstandard connection at the end equipment, connector etc.

It was agreed by all that PGCIL would take all necessary steps to improve RTU availability and

reduce down time.

Data validation SRLDC informed that at around 1,000 points discrepancy has been observed. The details of

these points are at Annexure-V SRLDC communication dated 19.01.2016 in this regard is at Annexure-VI

Many times data at Thiruvalam was getting frozen. It was stated that incorrect data reporting at SCADA

gives a false picture and could result in wrong action by grid operator. Attempt should be made by

PGCIL/User to send correct data as close as real time values.

PGCIL pointed out that the errors could be due to accuracy class of CT, PT, Transducer etc.

.

It was agreed that all analog discrepancies would be bilaterally discussed (tested with primary

injection wherever possible) and issues settled before 30th April’16. The schedule would be

mutually agreed by PGCIL/User and SRLDC with intimation to SRPC. Status points would be

immediately attended preferably before the month end.

Data base on lining For data base changes, across control centre, each control centre was carrying out the same on

its own requirement. Due to this, sometime data interruption happens, especially when data transfer is

happening thru ICCP. This problem has to seen with reference of SCADA data availability/visibility during

first time charging throughout SR Grid.


SRLDC informed that they generally carry out data base onlining once in a week i.e. on Thursday.

Control center where new element is being integrated wouldcoordinate with other control centers.

SOE issue in Alstom SCADA

PGCIL pointed out that for few stations SoE is coming correctly from RTU but not getting

reflected in SCADA. PGCIL pointed out in case of Narendra RTU, SoE received in SCADA was having one

hour difference. Another issue of difference in year in SoE timimgs was pointed out at Raichur where it

was getting truncated to last two figures

SRLDC informed that the same has been taken up with M/s ALSTOM and got resolved for the

above cases. Cooperation was requested from all for simulation/testing.

PGCIL requested to share detail of HEX code in case of SoE mismatch. SRLDC agreed for the

same.

SCADA vs SEM and drawal computations SRLDC informed that the Committee had proposed the following recommendations (report copy

at Annexure-VII) to ensure values of SEM and SCADA measurements used in AP grid drawl computations

are accurate and matching:

(a) L.Sileru & KTPS RTUs need to be checked and configured for sending continuous real time field

data to SCADA systems in AP, TS & SRLDC.

AP & TS confirmed that the issue had been resolved.

(b) High difference in alternate ends of lines mentioned above in point (ii) sub-points (a) to (f) of

the report need to be cross checked and verified with field data

It was noted that all the inter-state lines between AP & TS are equipped with main meter only

and there were no check meters. It was also noted that there were no SEMs & RTUs at one

end on some of the inter-state lines. AP informed that the procurements of RTUs were under

way as commercial bids were opened and who take around 3-4 months. TS informed that

technical bids are opened for RTUs procurement. Forum requested to expedite the action by

both AP and TS

PGCIL informed that Kadapa, Kolar, Ghanapur and Nagarjunasagar issues had been resolved.

SRLDC pointed out Ghanapur and Nagarjunasagar issues were yet to be resolved and

requested for necessary action.

(c) Loss factor for negative schedules needs to be quantified and subtracted in real time from AP

grid drawl computation

SRLDC informed that this would be reviewed in consultation with APTRANSCO.


(d) SEM meters on lines mentioned under the heading “Verification of SEM data” need to be

checked for time drift.

The issue was being addressed.

APTRANSCO,TANTRANSCO & TSTRANSCO expressed concern over the mismatch in the SCADA

verses SEM value and requested for waiver of penalty in deviation.

SRLDC informed that deviation between SCADA & SEM in the case of AP were more since around

70 elements/points are involved. In case of other States, around 20 points are considered. The

deviations are also depending on the loading and availability of those elements.

It was a noted that SEMs were to be provided at both ends of inter-state lines between AP &

Telangana. AP & Telangana were suggested to take appropriate action.

SRLDC informed that report in respect of Andhra Pradesh has been modified keeping in view the

suggestions of SRPC/TCC like manual entries etc. Telangana report has been finalized and would be

brought out shortly. In the first fortnight of April, similar exercise for Tamil Nadu and in second fortnight

exercise for Kerala would be taken up. Exercise for Karnataka would be taken up in the first fortnight of

May.

SRLDC also emphasized that real time grid operation shall be based on the data available to SRLDC

SCADA and co-operation of AP & TS was requested to improve the quality of data available and adhere

the instructions of SRLDC strictly so as there will not be any dispute during real time grid operation.

Other issues: SR-II PGCIL informed that there were some issues in the cable size provided for DCPC to Crone

module. M/s Alstom agreed to look into the matter.

It was agreed that SR-I PGCIL, (along with M/s. Tejas), SRLDC (along with ALSTOM) and

Bhadravathi (PGCIL) would jointly work and address the Bhadravathi data availability issues on

priority. Necessary lead for the joint visiting / testing will be ensured by SRTS-I.

MEPL informed that they have entered into AMC for SCADA issues with M/s ABB. For

communication issues M/s MROTek was not coming forward for AMC and communication issues

were being addressed on call basis. They assured full cooperation in this regard.

Coastal Energen stated that they would enter into AMC for communication/SCADA . All the

pending issues would be addressed.

TPCIL agreed that they would communicate the NCC related issues to NCC. It was assured that all

communication on SCADA issues would be addressed on priority.

It was noted that data from Simhadri Stage II is not coming to SRLDC on second channel. PGCIL

confirmed that the link was healthy which was vetted by testing. It was noted that NTPC as an

user had earlier been advised to coordinate with its OEM and make available data in the requisite


format of PGCIL before end of March’16. As an user the responsibility of ensuring data to SRLDC

rested with NTPC.

PGCIL informed that they were working on Warangal data for secondary channel and the same

would be made through by Mar’16.

SRLDC pointed out that NTPL data was not reporting since four days. NTPL / PGCIL shall co-

ordinate and make the data availability with in three days.

TSTRANSCO informed that sometimes due to wrong data received from Ramagundam, the

demand of Telangana was being computed erratic and they had addressed a letter to NTPC in this

regard. SRLDC has also been informed via mail. NTPC was suggested to address this issue.

SRLDC informed that MW Transducers at Ramagundam were having range of -600 to

+600 MW. Any MW flow beyond this limit gets frozen to 600MW. It was noted that issue

could be transducer, CT saturation etc and NTPC was suggested to revert back with

details. It was agreed that a Group with members from NTPC, POWERGRID, SRLDC, SRPC,

State Utilities could be formed to look into the issue.

Back up ICCP link of AP had been made through.

Kaiga data was being routed through Narendra DCPC and second channel for the same needs to

be provided at Narendra DCPC. PGCIL agreed to furnish the details.

For back up ICCP link of Kerala, KSEBL requested PGCIL for separate routing through E-1 Port. It

was noted that the issue would be addressed by month end in coordination with KSEBL, PGCIL

(Tejas) and SRLDC (Alstom).

Difference in the drawl values in SCADA shown at RLDC and SLDC of Kerala and its computational

methodology was raised by Kerala. Methodology adopted by SRLDC for Kerala was shown to

Kerala and found to be OK

KSEBL requested that for allocating separate LOGIN for KSEBL SCADA in the Regional LD SCADA

system for data verification (both ICCP and real time) and for updating of user interface displays

in SLDC with that of SRLDC, so that display data on the operational user interface displays will be

matching. SRLDC informed that web based login had already been assigned to the utilities and

the requirements could be made available for them to make it available in the web based

programme.

KSEBL stated that EMS studies on National level grid were required for constituents. SRLDC

pointed out that Kerala could carry out studies by configuring all the required data.

KSEBL requested SRLDC regarding updating the relevant data and displays like power map in

constituents SCADA with that in SRLDC system as and when modifications occur. SRLDC agreed to

inform the changes in network on regular basis.

KSEBL suggested discussion on mail configuration of SCADA for exclusive mail transaction

between the constituents and the RLDCs and establishing a separate communication channel for

the mail server connectivity. SRLDC pointed out that such provision was not available in the

SCADA at present.

KSEBL had suggested that discussion on AMC cost of Alstom SCADA price adjustment based on

Indian field labour index. KSEBL was suggested to take up the issue separately with their

contractor / consultant.


KSEBL requested for visibility of all lines and elements in Western and Eastern region having

impact to SR such as Wardha-Parli, Aurangabad-Sholapur etc. SRLDC stated that already available

data has been provided. Any further requirement may be communicated to SRLDC.

TANTRANSCO requested SRLDC to display real time frequency and deviation in SRLDC website for

all the blocks. TN was requested to create this display locally.

Agenda points submitted by KSEBL are at Annexure-VIII. It was noted that communication

related issues would be discussed between KSEBL& PGCIL.

Member Secretary, SRPC thanked the participants for their valuable contribution. He again

requested that all entities may kindly ensure that works within their scope are completed and

maintained.

*******

Documents

Minutes of the Special SCADA/communication meeting held on 21.03.2016 … · 2016. 3. 24. · Minutes of the Special SCADA/communication meeting held on 21.03.2016 Page 2 issue within